Error correction (Thread 'main' panicked ... postgres)#412
Open
solaryssky wants to merge 14 commits intoroapi:mainfrom
Open
Error correction (Thread 'main' panicked ... postgres)#412solaryssky wants to merge 14 commits intoroapi:mainfrom
solaryssky wants to merge 14 commits intoroapi:mainfrom
Conversation
houqp
reviewed
Nov 27, 2025
| let theme = egui_extras::syntax_highlighting::CodeTheme::from_memory(ctx, ui.style()); | ||
|
|
||
| let mut layouter = |ui: &egui::Ui, string: &str, wrap_width: f32| { | ||
| // ИЗМЕНЕНО: второй аргумент closure теперь &dyn egui::TextBuffer |
Member
There was a problem hiding this comment.
these comments don't seem to related to the change
houqp
reviewed
Nov 27, 2025
Member
|
thanks for the fix @solaryssky , could you also fix the CI? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Error correction #389
The Can't start a runtime from within a runtime occurs because inside the already running Tokio runtime (your #[tokio::main]), the connectorx library tries to call the blocking block_on via the synchronous Postgres driver (postgres crate) (creates/uses a single-threaded runtime). This is a conflict: a blocking call inside the tokyo workflow.