Skip to content

v1.13.2 - The Bot Says What It's Doing

Choose a tag to compare

View all tags
@Ninja-FSE Ninja-FSE released this 28 Sep 19:02
· 18 commits to main since this release
v1.13.2
12e5661
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

21 changes since v1.13.1, dominated by the debug channel and console feed becoming visible when something is quietly wrong, and the DCCore Chat peer sidebar finally clearing correctly.

  • Fixed: clearing the debug channel from the dashboard now leaves it right away, and asks first. Whenever the bot does stay behind (any other way of clearing it), it now says so in the debug channel and admin console too, not just its own log.
  • Fixed: the dccore.mrc window now says why it only shows "STATUS" and nothing else. A new checkbox/menu item (consolefeed on|off) turns the rest of the feed back on. Update dccore.mrc (now 1.7).
  • Fixed: a DCCore Chat peer's sidebar could show the same nick repeated many times over, because clearing it before redrawing silently did nothing.
  • Fixed: a DCCore bot reconnecting could take up to 10 minutes to reappear in the DCCore Chat sidebar - now within moments.
  • Fixed: a mass rejoin in a big channel no longer makes the bot stall.
  • Fixed: a list rebuild is no longer reported as failed when only the saved track lengths could not be written.
  • Fixed: adding or removing a second list no longer throws away the saved track lengths and quality.
  • Fixed: after a restart, downloads from a bot you were queued at no longer stall for up to 12 hours.
  • Fixed: removing a download that another bot has queued no longer warns that a downloaded file will be deleted.
  • Fixed: the dashboard's version line and Library cards now change straight away when you switch language.
  • Fixed: "Online only" in the List Browser no longer hides a bot that came back under a new nick.
  • Fixed: another bot's answer could be applied to the wrong download, when one file's name is the end of another's.
  • Fixed: a track that could not be read once no longer loses its length and quality for good.
  • Fixed: a file asked for from another DCCore bot while it was reloading its settings was turned away when it arrived.
  • Fixed: on Windows, a list rebuild could fail because someone was downloading the list by its file name.
  • Fixed: a download added at just the wrong moment could skip a pause or the low-disk check.
  • Fixed: one user can no longer make the bot answer "busy" to everyone else.
  • Fixed: a list rebuild reading track lengths from a network drive that stops answering no longer hangs for ever.
  • Fixed: automatic list grabbing no longer gives up on bots it never asked.
  • Fixed: with automatic list refresh on, old lists from bots that have left no longer block the refresh of everyone else's.
  • Fixed: downloads waiting from before a restart or a reconnect no longer fail as "no response".
  • Fixed: a download bigger than your free disk space no longer fills the disk over and over.
  • Fixed: a folder or list download that had to be asked for again asked for the wrong thing.
  • Fixed (security): a crafted private message could freeze the bot. Update if you run v1.13.1.
  • Fixed: a request could be sent a different file with the same name.

Full changelog: docs/UPDATES.md in this PR's branch.

Extracted per docs/PUBLIC-REPO-WORKFLOW.md's checklist from dccore-dev at a90396d: dev-only tooling and its dedicated tests stripped, changelog swapped, links rewritten. Full suite run in the extracted tree itself: 7021 tests, OK.

🤖 Generated with Claude Code

Assets 2
Loading