avoid printing traceback for console script errors
@kalenkovich ci sta già lavorando.
Dal 26/9/2023.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
This error message:
Traceback (most recent call last):
File "\\?\C:\Users\evk465\AppData\Local\mambaforge-pypy3\envs\blabpy\Scripts\vihi-script.py", line 33, in <module>
sys.exit(load_entry_point('blabpy', 'console_scripts', 'vihi')())
File "C:\Users\evk465\AppData\Local\mambaforge-pypy3\envs\blabpy\lib\site-packages\click\core.py", line 1157, in __call__
return self.main(*args, **kwargs)
File "C:\Users\evk465\AppData\Local\mambaforge-pypy3\envs\blabpy\lib\site-packages\click\core.py", line 1078, in main
rv = self.invoke(ctx)
File "C:\Users\evk465\AppData\Local\mambaforge-pypy3\envs\blabpy\lib\site-packages\click\core.py", line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "C:\Users\evk465\AppData\Local\mambaforge-pypy3\envs\blabpy\lib\site-packages\click\core.py", line 1688, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "C:\Users\evk465\AppData\Local\mambaforge-pypy3\envs\blabpy\lib\site-packages\click\core.py", line 1434, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "C:\Users\evk465\AppData\Local\mambaforge-pypy3\envs\blabpy\lib\site-packages\click\core.py", line 783, in invoke
return __callback(*args, **kwargs)
File "c:\users\evk465\blab\blabpy\repo\blabpy\vihi\cli.py", line 44, in start
annotation_folder = checkout_recording_for_annotation(full_recording_id=recording_id, annotator_name=name)
File "c:\users\evk465\blab\blabpy\repo\blabpy\vihi\annotating.py", line 12, in checkout_recording_for_annotation
pn_opus_repo_path = get_lena_path()
File "c:\users\evk465\blab\blabpy\repo\blabpy\vihi\paths.py", line 36, in get_lena_path
return _get_modality_path('LENA')
File "c:\users\evk465\blab\blabpy\repo\blabpy\vihi\paths.py", line 28, in _get_modality_path
return get_subject_files_path() / modality
File "c:\users\evk465\blab\blabpy\repo\blabpy\vihi\paths.py", line 20, in get_subject_files_path
return get_vihi_path() / 'SubjectFiles'
File "c:\users\evk465\blab\blabpy\repo\blabpy\vihi\paths.py", line 12, in get_vihi_path
return get_pn_opus_path() / 'VIHI'
File "c:\users\evk465\blab\blabpy\repo\blabpy\paths.py", line 53, in get_pn_opus_path
raise _get_pn_opus_path_error(checked_paths=str_paths)
ValueError: Could not locate PN-OPUS at any of the following paths:
- /Volumes/pn-opus/, Z:\
Follow these steps:
- Check that you are connected to the Duke VPN.
- Check that PN-OPUS is mounted.
- Check that it is mounted to one of the default locations:
- /Volumes/pn-opus/, Z:\
If it is mounted elsewhere, either remount it or set an
environment variable PN_OPUS_PATH to the mount location.
would be much more readable if the traceback was removed:
ValueError: Could not locate PN-OPUS at any of the following paths:
- /Volumes/pn-opus/, Z:\
Follow these steps:
- Check that you are connected to the Duke VPN.
- Check that PN-OPUS is mounted.
- Check that it is mounted to one of the default locations:
- /Volumes/pn-opus/, Z:\
If it is mounted elsewhere, either remount it or set an
environment variable PN_OPUS_PATH to the mount location.
Ideally, there would be a --DEBUG flag that would put the traceback in.
- Lingua principale
- Python
- Stelle
- 0
- Fork
- 0
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun 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 BergelsonLab/blabpy
-
bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
BergelsonLab/blabpy#35 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
BergelsonLab/blabpy#34 · 1 commento ·
-
add `vihi annotation update-links`Forse di nuovo libera @kalenkovich l’ha presa 630 giorni fa e non c’è nessuna pull request aperta. Aperta
BergelsonLab/blabpy#32 · 1 assegnatario ·
-
good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 45/100
BergelsonLab/blabpy#31 ·
-
pandas helper: where joinForse di nuovo libera @kalenkovich l’ha presa 1375 giorni fa e non c’è nessuna pull request aperta. Aperta
BergelsonLab/blabpy#27 · 1 assegnatario ·
Tutte le issue di BergelsonLab/blabpy
Issue simili
-
mermaid_extract.py silently discards single-line state-diagram notes; sequence notes are keptAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
cathrynlavery/diagram-design#441 ·
I maintainer di solito rispondono entro 2 giorni
-
[Cleanup] Include the public header in work_split.cppForse già presa @blozano-tt l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
tenstorrent/tt-metal#60850 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
backend::sglang bug language::python observability
Difficoltà 2/5 Mezza giornata Idoneità per principianti 65/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 75/100
OpenShot/openshot-qt#6202 ·
I maintainer di solito rispondono entro 1 giorno