fix: correct Windows netstat command and add browser label for cache clearing#442
Conversation
…clearing (genlayerlabs#413) Two fixes in troubleshooting.mdx: 1. Windows port conflict command: 'find' -> 'findstr' The find command requires quoted strings on Windows. findstr is the correct tool for filtering netstat output by port number. 2. Cache clearing instructions: add '(Chrome/Chromium)' label and note for other browsers. The existing steps only work in Chrome/Chromium. Firefox, Brave and Safari users could not find the described UI options. Fixes genlayerlabs#413
✅ Deploy Preview for genlayer-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughThe troubleshooting page adds browser-specific localhost site-data clearing guidance and changes the Windows port lookup command to use ChangesTroubleshooting updates
Estimated code review effort: 1 (Trivial) | ~3 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@pages/developers/intelligent-contracts/tools/genlayer-studio/troubleshooting.mdx`:
- Line 14: Rename the existing “Clear Cache (Chrome/Chromium)” troubleshooting
step to “Clear localhost site data” and update its wording to describe deleting
localhost cookies and site data. Add a separate troubleshooting step explaining
how to clear cached images and files when stale frontend assets are the issue.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 8c933993-db99-44e4-9b69-da84ee76cd60
📒 Files selected for processing (1)
pages/developers/intelligent-contracts/tools/genlayer-studio/troubleshooting.mdx
| ### Solution | ||
| - **Refresh Frontend:** Simply reload the page in your browser. | ||
| - **Clear Cache:** Clear your browser's cache by clicking on the left of your address bar -> Cookies and site data -> Manage on device site data -> Delete localhost. | ||
| - **Clear Cache (Chrome/Chromium):** Clear your browser's cache by clicking on the left of your address bar -> Cookies and site data -> Manage on device site data -> Delete localhost. For other browsers (Firefox, Brave, Safari), use the browser's built-in settings to clear site data for localhost. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
file="pages/developers/intelligent-contracts/tools/genlayer-studio/troubleshooting.mdx"
echo "== File overview =="
wc -l "$file"
echo
echo "== Relevant section =="
nl -ba "$file" | sed -n '1,40p'Repository: genlayerlabs/genlayer-docs
Length of output: 333
🏁 Script executed:
#!/bin/bash
set -euo pipefail
file="pages/developers/intelligent-contracts/tools/genlayer-studio/troubleshooting.mdx"
echo "== Relevant section =="
sed -n '1,40p' "$file" | cat -nRepository: genlayerlabs/genlayer-docs
Length of output: 2115
🌐 Web query:
Chrome documentation cookies and site data versus clear cached images and files localhost site data
💡 Result:
In Chrome, the options to clear browsing data are categorized to address different types of technical issues [1][2]. Cookies and Site Data This category is intended for managing session-based and persistent state that websites use to remember you [3][2]. - Cookies: Small files used to maintain authentication (keeping you signed in), save site preferences, and track sessions [3][1][4]. Clearing these typically signs you out of websites [5][3][1]. - Site Data: Includes advanced storage mechanisms such as LocalStorage, SessionStorage, IndexedDB, and Service Worker registrations [5][2][6]. This data is often used by web applications to store complex state, offline capabilities, or local app settings [5][4][2]. Cached Images and Files This category focuses on performance and visual rendering [7][2]. - What it contains: Saved copies of page assets like images, CSS stylesheets, JavaScript files, and other static resources [4][2]. - Purpose: By storing these locally, Chrome speeds up subsequent visits to the same page [7][4][2]. - When to use: Clearing this is usually the primary step to resolve visual glitches, broken layouts, or instances where a site displays outdated content despite server-side updates [1][4][2]. Localhost Considerations Localhost data, including cookies and storage, is treated by the browser as site data associated with the origin (e.g., http://localhost:PORT) [8][9]. - Clearing "Cookies and site data" generally removes all storage (cookies, LocalStorage, IndexedDB) associated with the localhost origin [5][6]. - Note: Depending on browser behavior and specific port configurations, clearing data for "localhost" may sometimes require precision. If you are developing and need to clear data for a specific port (e.g., localhost:3000 vs localhost:8000), you can use Chrome DevTools (Application tab) to target and delete data specifically for that origin rather than performing a global clear of all browser data [9][10]. Summary - If you are experiencing login issues, session errors, or site preference glitches, clear Cookies and site data [1][4]. - If you see formatting issues, broken styles, or outdated content, clear Cached images and files [1][4][2]. - For development on localhost, you can clear data globally via the browser settings or granularly for a specific port via the DevTools Application panel [4][9].
Citations:
- 1: https://www.chromethemer.com/chrome-clear-browsing-data/
- 2: https://browser-privacy-settings.blogspot.com/2025/12/cookies-site-data-chrome-setup-guide.html
- 3: https://support.google.com/chrome/answer/95647?visit_id=638542267681483461-3764727077&rd=1
- 4: https://www.solvetechtoday.com/clear-chrome-cookies-and-cache-guide/
- 5: https://support.google.com/chrome/answer/2392709
- 6: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Clear-Site-Data
- 7: https://support.google.com/chrome/a/answer/10686330
- 8: https://bugzilla.mozilla.org/show_bug.cgi?id=1628240
- 9: https://stackoverflow.com/questions/10073168/cookies-on-localhost-in-google-chrome
- 10: https://unix.stackexchange.com/questions/239447/clearing-browsers-state-about-localhost8086
pages/developers/intelligent-contracts/tools/genlayer-studio/troubleshooting.mdx:14 — Rename this step to “Clear localhost site data.”
This clears cookies/storage for localhost, not the browser cache. Add a separate step for clearing cached images and files if stale frontend assets are the issue.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In
`@pages/developers/intelligent-contracts/tools/genlayer-studio/troubleshooting.mdx`
at line 14, Rename the existing “Clear Cache (Chrome/Chromium)” troubleshooting
step to “Clear localhost site data” and update its wording to describe deleting
localhost cookies and site data. Add a separate troubleshooting step explaining
how to clear cached images and files when stale frontend assets are the issue.
Source: MCP tools
1 participant
Summary
Two fixes in the Studio troubleshooting documentation.
Bug 1: Wrong Windows Command
The port conflict section used
findinstead offindstr:The
findcommand on Windows requires quoted search strings and behaves differently from Unixgrep.findstris the correct tool for filteringnetstatoutput by port number.Bug 2: Chrome-Only Cache Instructions Not Labeled
The cache clearing steps (
address bar -> Cookies and site data -> Manage on device site data -> Delete localhost) only work in Chrome/Chromium. Firefox, Brave, and Safari users cannot find these options.Added
(Chrome/Chromium)label and a note directing other browser users to their browser's built-in site data settings.Fixes #413
Summary by CodeRabbit