ethanmoffat / etheos Goto Github PK

Add an EditorConfig (.editorconfig) file to explicitly state expected file formatting parameters and to improve rendering of existing files.

Right now we have disparate scripts for building on Linux and Windows. It would be nice to unify these to a single script so we only have one thing to maintain.

Ideas for this (in order of preference):

• Powershell core
• Bash on Windows somehow (Cygwin?)
• Cake build with similar ps1/sh bootstrap scripts

Board state needs to be added to the crash dump JSON file.

Boards use the client default of '2', with 1 minute between posts, because the config file has a string mismatch with the value read in code.

Character::ShowBoard line 1421

I can't seem to find pub files in order to load the server. Any ideas?

See: ethanmoffat/EndlessClient#154

Need to implement the Autorefresh packets and rename Appear/Autorefresh to their appropriate "MapInfo" equivalents.

It would be nice if the IgnorePacketFamilies feature supported more advanced filtering options. Currently, you specify packet families to exclude from logging. It would be helpful to have negative filters, like !Login, * would only show Login family of packets.

I thought it might be worthwhile to start a discussion about a tentative release plan. Here are some points I think might be worth discussing:

1. The last release (0.7.0) was created over 3 years ago (April 2016). Do we have a list of changes that occurred in this time period so that we can provide a release note with the next release? If not, then I can start compiling this list.
2. Do we have a list of current features and bugs? I think the easiest way to allow for tracking of bugs and features is through the use of GitHub issues. The use of GitHub issues would greatly simplify the generation of release notes for future releases. I'm wondering if anyone else has an opinion on this.
3. While committing directly to the repository provides a quick-to-update workflow, it makes code review/oversight and tracking difficult. The use of branches and pull requests can be helpful for associating a collection of changes with the bug or feature they were intended to address. Again, I'm wondering if anyone else has any opinion on this.
4. Lastly, do we have any idea of when our next release will be and if it will be a major or minor version? If not, maybe we should have a discussion about our roadmap to the next release so that the community has something to look forward to and so that we have something to work towards.

@ethanmoffat here is what I’ve run to create and maintain a mirror of the eoserv source with a full commit history:

#!/usr/bin/env bash

function main()
{
  local svn_url="svn://svn.eoserv.net/eoserv"
  grep -r svn-remote .git/config &> /dev/null \
    || git svn init -s "${svn_url}"

  git svn fetch \
    && git svn rebase
}

main "$@"

Add Windows and Linux Azure CI pipelines.

See map.cpp line 761 - builder.AddChar(6); // ?. This unknown value is actually supposed to be class ID.

ethanmoffat/EndlessClient#156 (comment)

Background

• EOSERV does all of its database operations in one big transaction on the main thread.
• SQLite only supports one simultaneous write transaction.

Problem

• Since the addition of asynchronous database operations on background threads for the LoginManager, SQLite support has been broken.

Reproduction case

• Configure EOSERV to use an SQLite database
• Create an account
• Account creation will fail, and a Database_QueryFailed exception will be raised.
• The error message from SQLite is "database is locked"

See

• World::BeginDB
• SQLite: Transaction