-
Notifications
You must be signed in to change notification settings - Fork 594
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
fix(sql-backend): change stream node type from json to binary to fix stack overflow #15040
Conversation
Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: dependabot[bot] <dependabot[bot]@users.noreply.github.com> Co-authored-by: Richard Chien <[email protected]>
) Signed-off-by: Bugen Zhao <[email protected]>
… with high barrier latency (#15011)
serde = { version = "1", features = ["derive"] } | ||
serde_json = "1" | ||
serde = { version = "1.0.196", features = ["derive"] } | ||
serde_json = "1.0.113" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we revert the rest of the version upgrade as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The previous version was a bit outdated. The bump should have no harm, and it might be helpful for debugging stack overflow issue later. 🤔 I prefer to keep it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The best practice should be only to bump the version in Cargo.lock
through cargo update -p ..
, instead of making it a constraint in Cargo.toml
.
BTW, the major motivation for introducing code owner for Cargo.lock
is to avoid bumping dependency in a PR for other purposes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bump should have no harm
This is hard to say. Developers would review the change logs in the PRs opened by the dependency bot.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed. I see, I should bump the version in a separate PR using cargo update -p
instead of messing it with other logics.
The bump should have no harm
This is hard to say. Developers would review the change logs in the PRs opened by the dependency bot.
I have checked the change logs in sea-orm in order to find some clues to identify the issue. So it might be ok, since sea-orm is only used in meta and under testing. Won't do it next time. 😢
Btw, shall we remove all constraint in Cargo.toml
and let them managed by Cargo.lock
in a unified manner.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we confirm that the issue only gets fixed after a minor version, then specifying the version as a requirement looks good. For serde
, it would be more suitable to keep the version as 1
since it is a regular bump. 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rubber stamp for Cargo.lock
…stack overflow (#15040) Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: Bugen Zhao <[email protected]> Co-authored-by: yezizp2012 <[email protected]> Co-authored-by: Li0k <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: dependabot[bot] <dependabot[bot]@users.noreply.github.com> Co-authored-by: Richard Chien <[email protected]> Co-authored-by: Bugen Zhao <[email protected]> Co-authored-by: Dylan <[email protected]> Co-authored-by: Noel Kwan <[email protected]>
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
As title. The stack overflow issue is caused accidentally when sea-orm is trying to deserialize column
stream_node
from tablefragment
. But when I tried deserializing the problematic data manually usingserde_json
, it did't show up. At present, it seems that only changing the type of this column can temporarily fix it.stream_node
type from json to binary to avoid some deserialization issues inside sea-orm.Checklist
./risedev check
(or alias,./risedev c
)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.