Summary by CodeRabbit

• Bug Fixes
  • Improved file browsing reliability when some items are missing/unknown size metadata; directory listings no longer fail due to metadata lookup errors and instead proceed safely (with warnings logged).
• UI Improvements
  • Updated the file system display so file sizes are left blank when size information is unknown or not available, avoiding misleading “0 B” output for certain files.

Walkthrough

When listing files returns entries with missing size data, the backend now wraps the fs.info() call in error handling that logs a warning and defaults the size to 0 rather than breaking the listing. The frontend adjusts display logic to show a blank size for falsy values instead of "0 B", ensuring unknown sizes are not misrepresented to users.

Changes

Unknown File Size Resilience

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

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 help to get the list of available commands and usage tips.}

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[fs.ls path detail=true] --> B{for each file_info}
    B --> C{type==file AND size is None?}
    C -- No --> G[Use ls metadata as-is]
    C -- Yes --> D[fs.info file_name]
    D -- success --> E[Use enriched file_info]
    D -- Exception --> F["Log warning with exc\nSet size = 0"]
    E --> H[FileInformation]
    F --> H
    G --> H
    H --> I[Return file_list]

    subgraph Frontend
        I --> J[transformTree]
        J --> K{isFile AND node.size truthy?}
        K -- Yes --> L[formatBytes node.size]
        K -- No --> M[size = blank]
    end

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[fs.ls path detail=true] --> B{for each file_info}
    B --> C{type==file AND size is None?}
    C -- No --> G[Use ls metadata as-is]
    C -- Yes --> D[fs.info file_name]
    D -- success --> E[Use enriched file_info]
    D -- Exception --> F["Log warning with exc\nSet size = 0"]
    E --> H[FileInformation]
    F --> H
    G --> H
    H --> I[Return file_list]

    subgraph Frontend
        I --> J[transformTree]
        J --> K{isFile AND node.size truthy?}
        K -- Yes --> L[formatBytes node.size]
        K -- No --> M[size = blank]
    end

_{Reviews (5): Last reviewed commit: "UN-3578 [FIX] Show blank instead of 0 B ..." | Re-trigger Greptile}

Frontend Lint Report (Biome)

✅ All checks passed! No linting or formatting issues found.

Unstract test results

Per-group results

Critical paths

⚠️ Critical paths not yet covered

• auth-login — User can log in and obtain a session cookie. (entry: POST /api/v1/auth/login; declared coverage: no groups declared)
• adapter-register-llm — Register and validate an LLM adapter. (entry: POST /api/v1/adapter/; declared coverage: no groups declared)
• workflow-create-execute — Create a workflow, configure source+destination, execute, poll, fetch result. (entry: POST /api/v1/workflow/{id}/execute/; declared coverage: e2e-workflow)
• api-deployment-run — Deploy a workflow as an API, POST a document, receive structured JSON. (entry: POST /deployment/api/{org}/{name}/; declared coverage: e2e-api-deployment)
• prompt-studio-fetch-response — Prompt Studio: create project, add prompt, run single-pass, get response. (entry: POST /api/v1/prompt-studio/prompt-studio-tool/{id}/fetch_response/; declared coverage: e2e-prompt-studio)
• pipeline-etl-execute — Run an ETL pipeline from source connector to destination. (entry: POST /api/v1/pipeline/{id}/execute/; declared coverage: no groups declared)
• usage-token-tracking — Per-execution token usage is recorded and retrievable. (entry: GET /api/v1/usage/get_token_usage/; declared coverage: no groups declared)
• workflow-execution-fan-out — Multi-file workflow execution fans out to file-processing workers and rejoins. (entry: internal: backend → rabbitmq → workers/file_processing; declared coverage: no groups declared)
• callback-result-delivery — Async results are posted back via the callback worker. (entry: internal: workers/callback → backend /internal endpoints; declared coverage: no groups declared)

I would still recommend leaving that size field blank rather than displaying 0 B. You can't distinguish between a failed file and one that is actually 0 B

@chandrasekharan-zipstack Agreed, fixed — size now shows blank instead of 0 B for any 0/unknown value (6b32b5f), so we never assert a size we can't determine. One line in the shared browser, applies to all connectors

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud