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
v0.40.18 tries to open empty string as privilege file if not explicitly provided #3865
Comments
@jcor11599 will get on this. I think he fixed it here: #3859 But he can confirm. |
I just fixed: #3859 and that's in the newest release It appears there is a bug with persisting privileges when they are specified in a I'll start working on fixing it now. |
@jcor11599 also update the docs. |
I think these are the two places:
@Eronarn are these the out of date docs you are referring to or did you hit another one? |
Yep that's correct - hit the other bug you fixed trying the first set of steps, then hit the second bug trying to use the config file as-is. I checked out your PR which is how I found out what the "new" config vars should be; but I didn't look into the Go code deeply to figure out why it was getting an empty string :( |
Fix for this issue is merged to main and should be available next release (probably soon). There are other unrelated changes I'm close to finishing that will affect the docs, so I'll update the docs once those are done. |
I tried setting up dolt server today and ran into some hiccups with the new privilege file settings. At first because the docs are now out of date I hit #3859, but also I believe I ran into an unrelated bug:
If I have either none of these variables in the YAML and fall back to defaults:
or these two (but not
privilege_file
, by commenting it out):Then on the sql-client side, creating a user results in this this confusing error message:
The user is created and shows up in
mysql.user
, but is not persisted (disappears on startup). I got curious what was happening and investigated it with strace:So it's actually opening a string
""
which is also why theopen :
message looks odd.Explicitly providing the
privilege_file
setting worked as expected: users can be created, there is no error message, and they persist on server restart.The text was updated successfully, but these errors were encountered: