juspay/xyne-spaces

Summary The agents service logs Failed to upload file to GCS: File buffer is empty or invalid about 5,400 times a day. It happens when an empty buffer is passed to the storage layer. This is expected when there's nothing to write, but it's logged as an error, which clutters the error logs and alerts. Code path apps/xyne-claw/src/storage.ts:337 (the debug-index write, gcsPutDebugIndex) → packages/storage/src/gcsService.ts:277 Expected If the buffer is empty, the upload is skipped with a debug-level log. No GCS call is made and no error is logged. Actual Every empty buffer is sent to the GCS service, which rejects it and logs an error. Where to start Add a guard in apps/xyne-claw/src/storage.ts before the call to gcsService: if the buffer is missing or has length 0, return early with a debug log. Acceptance criteria An empty or missing buffer is skipped before the GCS call, with a debug log. Non-empty buffers upload exactly as before. A unit test covers the empty-buffer case. Plea

Summary The Activity feed's "All" tab fetches every activity row. Each row is rendered by a switch on actorAction in ActivityItem.tsx, and any action that has no case falls through to default: return null. That leaves a blank gap about 12px high. ticket_status_v2 is by far the most common, but other actions have the same problem, including missed_call and workflow_question. Steps to reproduce Get an activity of one of these types, for example a ticket status change that isn't grouped with other activity. Open Activity → All. Expected Every activity type renders as a readable row. Actual The row is blank or collapsed. Unhandled actions found so far ticket_status_v2, ticket_merged, ticket_merged_target, ticket_unmerged, ticket_unmerged_target, ticket_stage_eta, workflow_question, missed_call, delayed_message_cancelled, delayed_message_failed, and the channel actions created, archived and visibility_changed. Where to start apps/dashboard/src/components/Activity/ActivityItem.tsx: the

Summary When you open an old recording whose media is no longer available, the player shows a loading spinner that never stops, instead of telling you the recording can't be played. Steps to reproduce Open an old call or recording whose media is no longer available. Try to play it. Expected After the load fails or times out, the player shows a clear "Recording not available" message. Actual The spinner keeps going and never stops. Where to start The recording player component in apps/dashboard. Handle the failed or empty media response, and the error or timeout state, instead of staying in loading. Acceptance criteria Missing or expired media shows a "Recording not available" state. Network errors or timeouts end the loading state. Recordings that are available still play as before. Please comment before starting so we can assign it to you.

Summary The "Create canvas" action shows nothing while the request is in progress. If users click again because it looks like nothing happened, several canvases get created. Steps to reproduce Click "Create canvas". Click it again quickly two or three times before the first canvas opens. Expected Only one canvas is created. The button shows a loading state and is disabled until the request finishes. Actual One canvas is created for every click. Where to start The create-canvas button and its handler in apps/dashboard. Acceptance criteria The button shows a spinner or loading state and is disabled while the request is in progress. Rapid clicks create exactly one canvas. On error, the button is enabled again and the user sees an error message. Please comment before starting so we can assign it to you.

Summary The Windows build of the desktop app shows the default Electron icon in the taskbar, the window title bar and the installer, instead of the Xyne icon. Steps to reproduce Install the Windows build of the desktop app. Look at the taskbar, the window icon, the Start menu shortcut and the installer. Expected The Xyne icon is shown everywhere. Actual The default Electron icon is shown. Where to start The Electron build and packaging config for Windows. Look at the icon setting for the win target and the .ico asset. Also check the BrowserWindow icon option. Acceptance criteria The Windows build shows the Xyne icon in the taskbar, the window, the shortcut and the installer. A multi-resolution .ico is added (16, 32, 48 and 256px). macOS and Linux icons don't change. Please comment before starting so we can assign it to you.