Skip to content

docker: bump python from 3.12-slim to 3.14-slim - #1

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker/python-3.14-slim
Open

docker: bump python from 3.12-slim to 3.14-slim#1
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/docker/python-3.14-slim

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 9, 2026

Copy link
Copy Markdown
Contributor

Bumps python from 3.12-slim to 3.14-slim.

@dependabot @github

dependabot Bot commented on behalf of github Jul 9, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies, docker. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot
dependabot Bot force-pushed the dependabot/docker/python-3.14-slim branch 2 times, most recently from 417060d to 6a314e4 Compare July 16, 2026 08:26
@dependabot
dependabot Bot force-pushed the dependabot/docker/python-3.14-slim branch from 6a314e4 to 9de8846 Compare July 22, 2026 13:07
Bumps python from 3.12-slim to 3.14-slim.

---
updated-dependencies:
- dependency-name: python
  dependency-version: 3.14-slim
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/docker/python-3.14-slim branch from 9de8846 to ba01749 Compare July 23, 2026 02:18
ebrandi added a commit that referenced this pull request Jul 31, 2026
…tically

leaderboards() only accepts its own fixed window keys and silently clamps anything else to
30d, so a contest window has to build from Window directly — the historical-months path in
aggregation.py already does exactly this. build_boards gains a limit kwarg, defaulting to
the display top-10 every existing caller wants.

Three differences from the killboard's own boards, all deliberate:

Only contest-eligible accounts are ranked. A pilot who never enrolled, or whose token has
lapsed, cannot win anything, so they are not on the board and the places are computed among
the pilots actually competing. The raffle's "top killer" can therefore differ from the
killboard's, which is correct — the raffle only knows pilots who connected a token — and it
means place #1 is the pilot who gets paid rather than "#2 who happens to be eligible".

Rollup is by ACCOUNT, not by mains_for. core.pilots.mains_for maps a linked character whose
account has no is_main flagged to itself, so rolling up by main leaves such an account as
two rows: one person holding two places on one board, collecting the same fixed prize
twice. Keying on user_id cannot do that, because the account is the thing being paid.

Ties break on the lower character id. leaderboards._rank sorts with Python's stable sort
over a GROUP BY carrying no ORDER BY, so tied pilots can swap places between two runs of
the same query. Harmless on a display board; unacceptable when the place decides a payout.

Boards are ranked 200 deep but displayed 10, so a pilot sitting 14th can still be told they
are 14th and what closing one place costs — which is the job the board exists to do. A tie
is reported as level rather than as a gap of zero.

All eight boards build in one pass and cache together. A contest board's cost is
independent of the window width — _kill_rows starts from KillmailParticipant, whose index
carries no time column — and every contest is its own cache key, so the killboard's warmed
windows buy nothing here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants