You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As newbie on optuna, I wrongly tried to use this call in the CLI, where db.sqlite3 is a file on my drive in the same folder.
optuna --storage db.sqlite3 study-names
This call currently gives a complicated error message about a UnicodeDecodeError that does not indicate the true mistake; I should have used the full URL sqlite:///db.sqlite3. For me it is not obvious that I have to use this URL, and I expected this simpler call to work. I propose two solutions, with preference in that order:
For user convenience, make the call above work: optuna detects that db.sqlite3 is the path to a filename and handles this call correctly.
Optuna should detect that the storage is given without an URL prefix and complain with an error message that points the user towards this issue.
The text was updated successfully, but these errors were encountered:
HDembinski
added
the
bug
Issue/PR about behavior that is broken. Not for typos/examples/CI/test but for Optuna itself.
label
Feb 13, 2024
nzw0301
added
question
Question about Optuna.
and removed
bug
Issue/PR about behavior that is broken. Not for typos/examples/CI/test but for Optuna itself.
labels
Feb 14, 2024
Thank you for the fix, the first line works. Still, I think this a UX bug. Please provide an error message for this case which points the user in the right direction or make the CLI smarter to handle the call optuna --storage db.sqlite3 study-names correctly. You should not expect that your users are familiar with the details of sqlite.
nzw0301
added
enhancement
Change that does not break compatibility and not affect public interfaces, but improves performance.
and removed
question
Question about Optuna.
labels
Feb 15, 2024
Expected behavior
As newbie on optuna, I wrongly tried to use this call in the CLI, where
db.sqlite3
is a file on my drive in the same folder.This call currently gives a complicated error message about a UnicodeDecodeError that does not indicate the true mistake; I should have used the full URL
sqlite:///db.sqlite3
. For me it is not obvious that I have to use this URL, and I expected this simpler call to work. I propose two solutions, with preference in that order:The text was updated successfully, but these errors were encountered: