datalad / datalad-helpme

Automated issue submission for datalad via helpme
0 stars 0 forks source link

[helpme] DataLad Cmd Error: NoDatasetFound #4

Open vsoch opened 4 years ago

vsoch commented 4 years ago

What were you trying to do?

I was breaking things.

Is there anything else you want to tell us

I broke it.


Metadata

Error Message :name_badge: This does not seem to be a dataset (no DataLad dataset ID found). 'datalad create --force /home/vanessa/Desktop/Code/datalad' can initialize this repository as a DataLad dataset [search.py:call:1262]

WTF Output :open_file_folder:

DataLad 0.10.3.1.dev3382 WTF (datalad, python, system, environment, configuration, location, extensions, metadata_extractors, dependencies, dataset) # WTF ## configuration ## datalad - full_version: 0.10.3.1.dev3382-ge7e4-dirty - version: 0.10.3.1.dev3382 ## dataset - id: None - metadata: - path: /home/vanessa/Desktop/Code/datalad - repo: GitRepo ## dependencies - appdirs: 1.4.3 - boto: 2.49.0 - cmd:annex: 7.20190819+git2-g908476a9b-1~ndall+1 - cmd:bundled-git: 2.20.1 - cmd:git: 2.20.1 - cmd:system-git: 2.23.0 - cmd:system-ssh: 7.6p1 - git: 3.1.1 - gitdb: 4.0.2 - humanize: 2.4.0 - iso8601: 0.1.12 - keyring: 21.2.1 - keyrings.alt: 3.4.0 - msgpack: 1.0.0 - requests: 2.23.0 - tqdm: 4.46.0 - wrapt: 1.12.1 ## environment - LANG: en_US.UTF-8 - PATH: /home/vanessa/anaconda3/bin:/home/vanessa/anaconda3/condabin:/home/vanessa/.rbenv/plugins/ruby-build/bin:/home/vanessa/.rbenv/shims:/home/vanessa/.rbenv/bin:/home/vanessa/anaconda3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/local/go/bin ## extensions ## location - path: /home/vanessa/Desktop/Code/datalad - type: dataset ## metadata_extractors - annex: - load_error: None - module: datalad.metadata.extractors.annex - version: None - audio: - load_error: No module named 'mutagen' [audio.py::17] - module: datalad.metadata.extractors.audio - datacite: - load_error: None - module: datalad.metadata.extractors.datacite - version: None - datalad_core: - load_error: None - module: datalad.metadata.extractors.datalad_core - version: None - datalad_rfc822: - load_error: None - module: datalad.metadata.extractors.datalad_rfc822 - version: None - exif: - load_error: No module named 'exifread' [exif.py::16] - module: datalad.metadata.extractors.exif - frictionless_datapackage: - load_error: None - module: datalad.metadata.extractors.frictionless_datapackage - version: None - image: - load_error: None - module: datalad.metadata.extractors.image - version: None - xmp: - load_error: No module named 'libxmp' [xmp.py::20] - module: datalad.metadata.extractors.xmp ## python - implementation: CPython - version: 3.7.4 ## system - distribution: debian/buster/sid - encoding: - default: utf-8 - filesystem: utf-8 - locale.prefered: UTF-8 - max_path_length: 306 - name: Linux - release: 5.3.0-51-generic - type: posix - version: #44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18 UTC 2020
## Environment - **LANG**: en_US.UTF-8 - **DISPLAY**: :0 - **USER**: vanessa - **PWD**: /home/vanessa/Desktop/Code/datalad/datalad/cmdline - **HOME**: /home/vanessa - **TERM**: xterm-256color - **SHELL**: /bin/bash - **PATH**: /home/vanessa/anaconda3/bin:/home/vanessa/anaconda3/condabin:/home/vanessa/.rbenv/plugins/ruby-build/bin:/home/vanessa/.rbenv/shims:/home/vanessa/.rbenv/bin:/home/vanessa/anaconda3/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/local/go/bin ## System ```python {'python': {'version': '3.7.4', 'implementation': 'CPython'}, 'system': {'type': 'posix', 'name': 'Linux', 'release': '5.3.0-51-generic', 'version': '#44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18 UTC 2020', 'distribution': 'debian/buster/sid', 'encoding': OrderedDict([('default', 'utf-8'), ('filesystem', 'utf-8'), ('locale.prefered', 'UTF-8')])}} ```

generated by HelpMe HelpMe Github Issue: purple-rabbit-1122

yarikoptic commented 4 years ago

Omg, this is awesome! First I wrote: It is exactly the one we need to get some matching to known issues established and pretty much strongly encourage not to file a new one whenever there is one already providing an explanation ;-) But now I am scratching my head: what had actually has happened? ;-) it is not the error I thought it was, so seems to be legit and we might want to provide more dedicated error message/exception for that:

vsoch commented 4 years ago

Oh right! And you know what, I forgot to include the unique identifier. I need to look back in our previous discussion to figure out how we supported that.

vsoch commented 4 years ago

And it's probably not the error you thought it was because I hacked it together :)

vsoch commented 4 years ago

I'm concerned that adding the full traceback is going to again hit the "request too large" browser limit - we have to be conservative with what we choose. What would you like to include?