Skip to content

fix: correct Windows netstat command and add browser label for cache clearing #442

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.

Sign up for GitHub

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

Open
ygd58 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: correct Windows netstat command and add browser label for cache clearing #442

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions pages/developers/intelligent-contracts/tools/genlayer-studio/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ The frontend may not load correctly due to caching issues or an outdated version

### 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.

@coderabbitai coderabbitai Bot Jul 10, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 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 -n

Repository: 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:

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


import Image from 'next/image'

Expand All @@ -37,7 +37,7 @@ The Studio may fail to start if some ports required for its operation are alread
```
- **Windows:**
```cmd copy
netstat -aon | find <PORT_NUMBER>
netstat -aon | findstr <PORT_NUMBER>
```
2. Use the following command to kill the process using the port. Replace `<PID>` with the Process ID obtained from the previous step.
- **Linux / MacOS:**
Expand Down