Open vsoch opened 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:
create-sibling-github
)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.
And it's probably not the error you thought it was because I hacked it together :)
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?
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 ## configurationgenerated by HelpMe HelpMe Github Issue: purple-rabbit-1122