AnswerDotAI / AnswerDotAI/nbdev

`nbdev_export` exports notebooks in arbitrary order

Aperta
#1,190 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
bug
Lingua principale
Jupyter Notebook
Stelle
5.3k
Fork
513
Merge medio
2g 30m
PR unite (30g)
8

Descrizione

In my project I can't get the build-pipeline to work again. It fails with the error, that my notebooks and the library are not in sync.
I already tried:
- upgrading local nbdev (is 2.3.7.)
- running nbdev_export locally, pushing the changes (there were none)
- deleting the library dir locally, pushing that. Then run nbdev_export locally to re-generate the lib folder, pushing that
- cloning the repository into a new local folder and running nbdev_export there. Again, there are no changes when running git status
- Deleting the github-runner-cache
- Performed the exact steps done by https://github.com/actions/checkout on my local machine. Ran `nbdev_export`. Still No changes shown by git status.

To no avail. It seems that whatever version the gitlab runner pulls is different than what I see in the repo.

Here is the pipeline in question:

https://github.com/omlnaut/pymoq/actions/runs/3356523622/jobs/5561653458

Any help is appreciated :)

Update:
I figured out how to ssh into the github runner while it's executing the workflow. The issue is not that the repository is checked out incorrectly. Instead, it seems that `nbdev_export` doesn't handle the case that I have one notebook (04_...) with a `default_export` and another notebook (06_....) that has specific cells exporting to the same target. On my local machine this works as intended, but when I run `nbdev_export` via ssh on the runner, only the code from the 04_... notebook gets copied to the target file.

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Inizia esaminando il workflow GitHub Actions collegato e riproducendo `nbdev_export` con il notebook 04_... usando `default_export`, e con il notebook 06_... esportando le celle nella stessa destinazione. Confronta i risultati locali con quelli del runner; il lavoro è completato quando entrambi i notebook vengono gestiti in modo coerente e la libreria generata corrisponde ai notebook.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
jupyter-notebook, python
Ambito
build-system, tooling
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
35/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.