symblai / symbl-powered-agora-rte-app Goto Github PK

some elements are rendered using DOM which might result the data being inconsistent

Contact Details

No response

Anything else?

No response

Issue: Unable to identify the person who is sharing the screen

Solution: The idea is to Identify and mark the attendee in the side panel who is sharing the screen so that users know who is sharing the screen.

Sometimes even when a user mutes himself the transcription still continues and the voice is still processed by audio context

Contact Details

[email protected]

Anything else?

I tried it on Vivaldi and it was almost running well.

Contact Details

[email protected]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

what is happening is that, when I am clicking on the share screen, it is not working properly at once. The screen once gets blacked out and then it reloads and then again I have to click on the button. I tried it again and again but all in vain 😢

Expected Behavior

No response

Steps To Reproduce

Please optimize it for Vivaldi browser

Environment

- OS:
- Node:
- npm:

What browsers are you seeing the problem on?

No response

Anything else?

No response

Issue: Once a user shares his screen and he cancels it, the button still shows the behavior - that it is still on.

The question, follow_up and action_item items found inside the insight label tab need to be updated with better formatting.

Suggestion: Question, Follow Up and Action Item.

Issue: When the video is turned off, it only stops displaying the video stream. The camera is still on.

Issue: The screen sharing functionality splits the meeting as another user.

Description: As of now, turning screen sharing on adds the shared screen as another user. If the participants are shown in the grid view, the screen is visible only as another small box.

Expected/Desired Behaviour: Fix this to allow proper screen sharing. Participants might still be visible in the meeting.
The view changes automatically to the Highlight view, and pins the shared screen. The other participants are seen in a single column of up to 4 rows, i.e. <= 4 cells, on the right side of the pinned video. If there are more than 4 participants (5 total including shared screen), then there should be a button to show the next 4 participants.
Notes: As of now, this view shift can be done manually by a participant not sharing their screen, but we want this to be the default to ensure a better user experience.

Contact Details

[email protected]

Description

Contact Details

No response

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The tab selection UI is not consistent. Only Transcript has the selection shown properly. For the Insights and Topics tab, the selection is shoddy.

Expected Behavior

Tab selection should be shown in the same way for all tabs.

Steps To Reproduce

No response

Environment

- OS:
- Node:
- npm:

What browsers are you seeing the problem on?

No response

Anything else?

No response

Token generation and handling should be moved to backend , right now it is stored on local storage it should be moved to backend along with agora token .

Issue: The tab selection UI is not consistent. Only Transcript tab has the selection shown properly. For the Insights and Topics tab, the selection is shoddy.

Expected behaviour: Tab selection is shown in the same way for all three tabs. Some generic UI logic needs to be implemented for the tab selection.

Contact Details

[email protected]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When running the npm run web in the front end the following error occurs .

npm ERR! info sharp Using cached /home/rajeshrajamani/.npm/_libvips/libvips-8.8.1-linux-x64.tar.gz
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp info using [email protected]
npm ERR! gyp info using [email protected] | linux | x64
npm ERR! gyp info find Python using Python version 3.10.6 found at "/usr/bin/python3"
npm ERR! gyp ERR! UNCAUGHT EXCEPTION
npm ERR! gyp ERR! stack TypeError: Cannot assign to read only property 'cflags' of object '#'
npm ERR! gyp ERR! stack at createConfigFile (/home/rajeshrajamani/Desktop/projects/agora/Symbl-powered-Agora-RTE-app/Symbl-Powered-Agora-master/node_modules/node-gyp/lib/configure.js:117:21)
npm ERR! gyp ERR! stack at /home/rajeshrajamani/Desktop/projects/agora/Symbl-powered-Agora-RTE-app/Symbl-Powered-Agora-master/node_modules/node-gyp/lib/configure.js:84:9
npm ERR! gyp ERR! stack at FSReqCallback.oncomplete (node:fs:185:23)
npm ERR! gyp ERR! System Linux 5.19.0-41-generic
npm ERR! gyp ERR! command "/home/rajeshrajamani/.nvm/versions/node/v19.8.1/bin/node" "/home/rajeshrajamani/Desktop/projects/agora/Symbl-powered-Agora-RTE-app/Symbl-Powered-Agora-master/node_modules/.bin/node-gyp" "rebuild"
npm ERR! gyp ERR! cwd /home/rajeshrajamani/Desktop/projects/agora/Symbl-powered-Agora-RTE-app/Symbl-Powered-Agora-master/node_modules/sharp
npm ERR! gyp ERR! node -v v19.8.1
npm ERR! gyp ERR! node-gyp -v v7.1.2
npm ERR! gyp ERR! Node-gyp failed to build your package.
npm ERR! gyp ERR! Try to update npm and/or node-gyp and if it does not help file an issue with the package author.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/rajeshrajamani/.npm/_logs/2023-05-04T11_59_56_418Z-debug-0.log

Expected Behavior

Front end should start

Steps To Reproduce

No response

Environment

- OS: Ubuntu 22.04
- Node:v19.8.1
- npm:9.6.2

What browsers are you seeing the problem on?

Chrome

Anything else?

No response