-
Notifications
You must be signed in to change notification settings - Fork 555
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
[Bug][lake] can not edit scope config #8281
Comments
@tim-goto Hello there! I'm here to help you with bug fixes, answer questions, and guide you to become a contributor. Let's squash those bugs together! 🤖 I found a similar closed issue titled "[Bug][Config UI] Errors when update project connection's scopes](#6097)" which was resolved by a pull request that reset the scope API to differentiate plugins [1]. The error you're encountering seems to be related to an SQL syntax issue, specifically with casting a column to If the issue persists, reviewing the changes made in the pull request that resolved the similar issue might provide insights into how to address the current problem. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
This looks related to the fix I submitted. Yet I did test this against a MySQL database. |
Thanks for getting back to me, I am using |
Hey @kostas-petrakis did you get a chance to look into this? And thank you for your help :) |
Hello @tim-goto unfortunately I didn't find the time past weeks due to workload, I plan to check it this Friday, together with another issue I am experiencing. |
Ran into the same error when attempting edit the scope config, using
|
Search before asking
What happened
error when clicking on 'edit scope config'
lake logs
What do you expect to happen
no error, I can edit the scope config
How to reproduce
click on 'edit scope config'
Anything else
No response
Version
release-v1.0_250120_1118_6e14cfa
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: