-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package contents cannot have a node named 'file' #314
Comments
Resolved: Individual files cannot be named |
Good catch! Actually, that is a real bug - you should be free to use the name |
file.{extenstion}
@dimaryaz Renamed issue for better tracking. Good luck! |
file.{extenstion}
Actually, this isn't a bug. Perhaps the design needs changing, but it's by design. It's not a file named 'file.xyz' that is the problem, it's having a node named 'file'. Also, the error occurs during build, not push. That error is really a beast, though, and it's very obscure to users what is actually happening. At the very least, we should change the error message, and perhaps we should change the quilt build file format. So, for example: # this package fails with the reported (obscure and unhelpful) error
contents:
file:
file: baz.tif # this package succeeds
contents:
file_: # note the underscore
file: file.tif This is because I'm going to have a conversation with some others about this, and do some checks in the code to ensure that the issue doesn't cause problems elsewhere. As long as that comes up clean, we could potentially be able to determine that it's being used as a keyword or not by the data it contains. |
Yep, I realized the issue a little while ago. Definitely a mistake on my part not following build manifest spec. |
True, but we've decided to allow this behaviour, so in the future you should be able to have packages which use keywords as node names, at least to some extent (including the case you have here). |
- Handle files named 'file.*' - Support arbitrary node names, including reserved ones, e.g. file, kwargs etc. Currently, node parser fails in case there is a file called 'file.*'. I believe it's related to the #314 issue.
Partially tackled in #414 and will improve with planned syntax checking for |
Attempting to push a package in python on 2.8.4 fails with traceback:
Code:
Python: 3.6.3
OS: Dockerized Linux (base jupyter/minimal-notebook)
Note: Without README.md file it still terminates the package push.
Package Build.yml:
Any help and info would be appreciated.
The text was updated successfully, but these errors were encountered: