Stale PR cleanup (2026-10): verify closed vs reopen
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
Direzione di ricerca
Review the linked PRs listed in the checklist, starting with their current status and the last-activity dates provided. For each unchecked item, determine whether it is correctly closed or should be reopened; comment here or reopen it, then tick the box once confirmed. The task is done when every checklist item is resolved.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Open PRs with no activity for 6+ months were closed on 2026-10-17 as part of a repo cleanup. Their commits stay available, and each PR can be reopened (with its branch restored) in one click.
If one of these is still relevant to you, comment here or reopen it. Each box is ticked once the PR is confirmed as correctly closed (or has been reopened).
- #369 Publishing to conda (@Blanderbuss, last active 2022-07-18)
- #462 docs(stubgen): wip for feeding GPT docs (@lmeyerov, last active 2023-04-30)
- #449 fix: Embed predict_links cuda (@tanmoyio, last active 2023-06-15)
- #490 Dev/dendrogram (@silkspace, last active 2023-06-19)
- #508 fix(saving without an index present) (@silkspace, last active 2023-11-04)
- #489 fix: Umap duplicate index (@tanmoyio, last active 2023-11-30)
- #501 Feature/gnn (@silkspace, last active 2024-02-28)
- #541 Dev/switch org api (@vaimdev, last active 2024-04-03)
- #536 fix(readme): added chain + fixed hop malformat (@dess890, last active 2024-04-09)
- #511 smart dependency manager (@dcolinmorgan, last active 2024-05-27)
- #569 coerce float if string or tuple (@dcolinmorgan, last active 2024-06-13)
- #560 Data synth (@webcoderz, last active 2024-06-17)
- #486 Cucat Featurization base (@tanmoyio, last active 2024-07-10)
- #517 Dev/depman gpufeat (@dcolinmorgan, last active 2024-07-15)
- #509 add bio gpu demos (@dcolinmorgan, last active 2024-07-16)
- #559 cleaned up notebooks added to gfql demo folder, readme update (@dcolinmorgan, last active 2024-08-07)
- #578 smart dep_manager (@dcolinmorgan, last active 2024-10-18)
- #608 Dev/sso login ux (@vaimdev, last active 2025-02-19)
- #652 269 fea validator - add validator code. (@SinsBre, last active 2025-04-08)
- #720 fix(demos): Fix Splunk integration in Corelight notebook (@SinsBre, last active 2025-07-30)
- #849 fix(layout): preserve user-set play URL parameter in ring layouts (@dess890, last active 2025-11-28)
- #743 Feature/sentinel kql (@SinsBre, last active 2026-01-06)
- #901 chore: add detect-secrets scanning (@lmeyerov, last active 2026-01-25)
- #907 chore: add trailing newline to trigger CI (copilot bot, last active 2026-01-27)
- #923 feat: add g.to_file() / graphistry.from_file() for Plottable serialization (@exrhizo, last active 2026-02-28)
- #935 add sso state ttl (@vaimdevs, last active 2026-03-09)
- #991 Investigate RAPIDS string-ID cuGraph build regression (@lmeyerov, last active 2026-03-31)
- #869 add new (maps) demos (@mj3cheun, last active 2026-04-07)
- #1109 docs(policy): add AI contribution policy (@lmeyerov, last active 2026-04-09)
- #852 ci(alloy): add model checks and caching (stacked) (@lmeyerov, last active 2026-10-17)
🤖 Generated with Claude Code
- Lingua principale
- Python
- Stelle
- 2.6k
- Fork
- 229
- Merge medio
- 1g 5h
- PR unite (30g)
- 100
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di graphistry/pygraphistry
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
graphistry/pygraphistry#2171 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
graphistry/pygraphistry#1965 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
graphistry/pygraphistry#1208 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
graphistry/pygraphistry#966 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
graphistry/pygraphistry#824 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di graphistry/pygraphistry
Issue simili
-
area:scripts area:tests bug priority:later
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
Ikalus1988/MisakaNet#4358 ·
I maintainer di solito rispondono entro 1 giorno
-
Discovered ports from service discovery are never propagated to modules in Module.load()Forse già presa @vishalmore90 l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
OWASP/Nettacker#1828 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
aws-samples/sample-per-model-bedrock#708 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
[Performance] Bound resolve_api_hashes raw fallback reads to the 1 MiB region actually scannedAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
sjkim1127/Reversecore_MCP#365 ·
I maintainer di solito rispondono entro 1 giorno