fix(app): avoid logging daemon URLs with query tokens#70
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
f205ca2 to
7dcbe32
Compare
Motivation
?token=query parameters.Description
HYPERCOLOR_URLvalue at startup by removing the structuredurl = %daemon_urlfield from the startup log and keeping a generic launch message (tracing::info!("launching Hypercolor app shell")).scheme,host, andportinstead of the entireurl(tracing::info!(scheme = %url.scheme(), host = ?url.host_str(), port = ?url.port_or_known_default(), "creating webview window")).Connected to daemon WebSocketlog and emit a non-URL connection message (info!("Connected to daemon WebSocket")).Testing
just test-crate hypercolor-app, butjustis not available in the environment so the command could not be executed.cargo test -p hypercolor-app, but the build failed due to a missing system dependency (glib-2.0) required byglib-sysin this container, preventing the test suite from completing.Codex Task