-
Notifications
You must be signed in to change notification settings - Fork 23
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
Project name of "deepkit" changes nested directory behavior #12
Comments
@planetceres thanks for the detailed description. Could you also please post your deepkit.yml content? I wonder if |
While the example I showed above is a private project, this same behavior happens with the default examples in this repo and the deepkit python-sdk. The only difference is that I've had to replace
|
this results always in I don't understand your example to be honest. You have shown two screenshots of different configurations. |
But you showed a screenshot of this configuration, so Deepkit found it. I really don't get that bug. You said Deepkit doesnt find the configuration, yet you created a screenshot of this very configuration in the GUI. What exactly do you mean with "Deepkit can't seem to find it"? |
A logical name to keep DeepKit configuration files within a project would be nested in a subdirectory called
deepkit
. However, using this convention on a DeepKit server causes inconsistency withdeepkit.yml
config values.Server Example
For example, say we're training a model in a parent repo of https://github.com/username/MyNetwork.git
If we create a directory ./deepkit and put deepkit.yml there, DeepKit can't seem to find the configuration. Notice the [object Object] placeholder value.
But if we duplicate the same
deepkit.yml
file and nest it under./deepkit/train
, DeepKit is able to find the configGUI Example
This also happens when using the GUI on localhost to manage a Project - but it is affected one level higher in the directory structure (so that the
[object Object]
placeholder value appears if./deepkit.yml
is in the root of the project:Summary
One solution is to make sure that DeepKit configuration files are not organized under a directory named
deepkit
. However, unless the directory namedeepkit
needs to be reserved, it might cause less confusion to correct this behavior so that experiments are not affected by this.The text was updated successfully, but these errors were encountered: