PalisadoesFoundation / talawa-admin

Admin portal for the Talawa Mobile App. Click on the link below to see our documentation
https://docs.talawa.io/
GNU General Public License v3.0
142 stars 589 forks source link

Video Post Creation - DOMException: The play() request was interrupted by a call to pause() #1713

Closed krishna619 closed 1 week ago

krishna619 commented 8 months ago

Describe the bug When creating a post with a video upload and subsequently viewing the post, the following error occurs in the console: "Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause()."

To Reproduce Steps to reproduce the behavior:

  1. Create a post with a video upload.
  2. View the created post.
  3. Open the browser console.

Expected behavior The video should play without any interruptions or errors when viewing the post.

Screenshots image

Additional details Add any other context or screenshots about the feature request here.

Potential internship candidates Please read this if you are planning to apply for a Palisadoes Foundation internship https://github.com/PalisadoesFoundation/talawa/issues/359

Shreyas2309 commented 8 months ago

I think we're not handling the video play Promise in our code that's why the error message appears

Assign this issue to me I want to work on it.

krishna619 commented 8 months ago

I think we're not handling the video play Promise in our code that's why the error message appears

Assign this issue to me I want to work on it.

yes, it is due to the asynchronous function.

Shreyas2309 commented 7 months ago

Hi ! I have raised a PR for this issue. Please review it .

Shreyas2309 commented 7 months ago

1727

ALOK9442 commented 7 months ago

hello @dhanagopu, can i work on this issue if no one is working?

Cioppolo14 commented 7 months ago

@ALOK9442 If the issue has already been assigned, please don't ask to be assigned. We want everyone to get a chance.

github-actions[bot] commented 7 months ago

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

palisadoes commented 7 months ago

unassigning as the PR seems abandoned

Shreyas2309 commented 7 months ago

Hello , I want to work on this please assign this to me.

ALOK9442 commented 7 months ago

unassigning as the PR seems abandoned

Hello sir, I would like to work on this issue

Cioppolo14 commented 7 months ago

@ALOK9442 If someone is assigned, please do not ask to be assigned.

github-actions[bot] commented 7 months ago

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

palisadoes commented 7 months ago

Unassigning, inactivity

github-actions[bot] commented 6 months ago

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

AnshulKahar2729 commented 2 months ago

Unassigning, inactivity

@palisadoes @Cioppolo14 @varshith257 assign me this.

palisadoes commented 2 months ago

@AnshulKahar2729

Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

github-actions[bot] commented 1 week ago

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.