v11.5.2

v11.5.2 (2024-06-15)

Fix

• fix: spansh- fix overzealous download

spansh plugin now will not download the source file if the source has not been modified more recently than the local copy downloaded previously
if the source file has been modified more recently, it is downloaded, overwriting the local copy, if any (5a8dd2a)

v11.5.1

v11.5.1 (2024-06-14)

Fix

• fix: can't change if doesn't exist yet (59512b0)

v11.5.0

v11.5.0 (2024-06-11)

Chore

• chore: fix Path error (5f5db6e)

Feature

• feat: include more tables in spansh import

Added processing spansh source for Ship, ShipVendor, Upgrade, and UpgradeVendor tables. (da1ee03)

Refactor

• refactor: correct get_timings() return hint (beeaea7)

• refactor: accurate progress bar (293c35b)

• refactor: accurate progress bar (a90a216)

• refactor: ingest_stream() -> self.ingest_stream() (0f18d10)

• refactor: correct load_known_stations return hint (0eaed90)

• refactor: output sample system json if debug

The entire galaxy_stations.json is too big and unwieldy to look at directly, so turning on debug will output only the Shinrarta Dezhra system to ./tmp/shin_dez.json, making it much easier to see the data structure, and since Jameson Memorial has all the things, we can also use it to check those things against the DB. (3688683)

• refactor: move eddblink_plug downloads to ./tmp (dee11c2)

• refactor: include system name in "updated"/"added" logs

#177 (4e403fe)

Style

• style: whitespace edits (9f6c2b6)

• style: fix white-space (c07eb91)

v11.4.0

v11.4.0 (2024-05-12)

Documentation

• docs: remove Merge line from changelog (02ac0c6)

Feature

• feat: add --maxage to sell command (ab34568)

v11.3.0

v11.3.0 (2024-05-06)

Chore

• chore: Fix linting error about collections.abc (1358479)

Feature

• feat: better eddblink progress reporting

• small tweaks to improve performance of eddblink import,
• commit batching to try and improve eddblink import speed,
• use rich progress bars to give better insight into commit rate

one interesting thing to try is to change the progress bar description around the COMMIT while importing prices:

prog.increment(description="COMMIT")
cursor.execute("COMMIT")
transaction_items = 0
cursor.execute("BEGIN TRANSACTION")
prog.increment(description="Processing")

and then adjust the batch size. when batchsize is too low, this makes the description flicker, but you can get a sense for how increasing the batch size reduces the total import time until the amount of memory/wal etc starts to make the commit time excessively long (f3af244)

• feat: database schema update

• Remove ROWID from Station table to improve performance,
• Introduce StationDemand and StationSupply tables for breaking up StationItem,
• Reduce size of station/system index, (32a7db1)

• feat: Swap out homebrew progress bars for Rich

• make bars hideable,
• polish,
• default the progress bar to visible, require show=False explicitly.
• add more bar styles,
• use some of the bars, (52bb7f4)

• feat: nicer transfer progress bars

uses the new rich-based progress bars to display download speed information etc. (bd4738a)

• feat: rich progress bars

This introduces an enhancement over the old progress bars, using rich to provide colorful, live bars. Base types for skinning them are included. (156904b)

Fix

• fix: Python version <3.9 does not support parenthesized context expressions (aab81db)

• fix: progress bar display/updates and linting

• advance progress bars properly,
• actually display the text of the progress bar, duh (ec94c0b)

Refactor

• refactor: make transfers use the rich bars properly. (ca12c5f)

• refactor: move file_line_count into fs (8a9989b)

Unknown

• • feat: add LongRunningCountBar to progress bars

Line CountingBar except it includes a TimeRemaining column (long running tasks seem to warrant this) (6f188a4)

v11.2.1

v11.2.1 (2024-05-06)

Fix

• fix: linter warnings from moving the shebang from line 1 (73d4a0d)

• fix: multiple options to --pad-size and others was no-longer working (f69dffd)

Refactor

• refactor: simplify the system-purge operation to not copy/move data and abuse the db (ab75113)

v11.2.0

v11.2.0 (2024-05-05)

Chore

• chore: additional deprecation

For #157 (93d91c9)

• chore: Mark deprecated code

For #157 (2afd5d6)

• chore: fix github actions cache warnings

I'd used an older github actions of mine as a basis for the cache blocks, and they referenced an out-of-date cache version.

contributes to #147 (fda2c26)

Documentation

• docs: fix help message for trade command (a6ca423)

Feature

• feat: enable repeat http requests over a single session

If we need to make multiple requests to a single http server, we have to repeat the overhead of connection-tear up which
can be significant for a remote https connection. 'requests' solves for this by letting you create a 'Session' object
that uses http keep-alive to send followup requests over an existing connection.

Commiting this separately from changes that make use of it. (8039aab)

• feat: add rename_file and remove_file to TradeEnv

This adds normalizing methods for removing and renaming files that will log the operation at DEBUG1,
and in the case of rename will ensure a .old backup of the existing file.

Committing separately of other work that leverages it. (778278d)

v11.1.6

v11.1.6 (2024-05-01)

Fix

• fix: typo caused buy command to error

• the code that should render the Average line at the end of
  a buy report had a typo that caused a string to become a list of
  strings, and the subsequent code could not handle that. (f016cec)

• fix: not using fdev_id for ships, as internal id is same now

Fixes #152 (38e4ac9)

v11.1.5

v11.1.5 (2024-05-01)

Documentation

• docs: correct web page (f71dca3)

Fix

• fix: parse the dates in a locale-agnostic manner

fixes #149 (1743f9f)

v11.1.4

v11.1.4 (2024-04-30)

Chore

• chore: Don't try to publish if you're not the bossmang, sassa (#145)

• chore: lint fixes

• chore: only try to publish from eyeonus repos

fixes #134

This makes the publish job dependent on being the eyeonus repository. It also moves the requirements files
into the top-level directory and organizes them into requirements, requirements-dev, and requirements-publish
which incrementally reference the previous requirements file to simplify them.

It's unusual for requirements*.txt to be in a subdirectory these days, and various tools are lazy about it,
which can make these chained-references problematic as some tools will intepret them relatively and some
won't; ergo having them in the tld together is less likely to suddenly not work one day.

---

Co-authored-by: Jonathan Jones <[email protected]> (dce2563)

Documentation

• docs: more CHANGELOG cleanup (77c54b0)

• docs: CHANGELOG.md cleanup (2885059)

Fix

• fix: fix linter errors in trade.py (f8effe4)

• fix: fix linter paths to trade.py and tradegui.py (d6f92cc)

Refactor

• refactor: use the rfc-correct Accept-Encoding (6c31521)