Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-76339

Recording are "dismissed" when they cannot be fetched from the server

    XMLWordPrintable

Details

    • MOODLE_400_STABLE, MOODLE_401_STABLE
    • MOODLE_400_STABLE, MOODLE_401_STABLE
    • MDL-76339-401
    • MDL-76339-master
    • Hide

      The scheduled task are now PHP unit tested.

       

      To test the new command line you need to be able to access you database and change some fields.

      • Create a new BigbluebuttonBN activity
      • Join the meeting
      • Record for a couple of seconds
      • End  the meeting
      • Wait for a minute
      • Run the cron to refresh the data regarding the recordings
      • Ensure that the recording is displayed in the activity page

      Go to your database and find your recording in the bigbluebuttonbn_recordings table.

      • Change its status to 1 (dismissed)
      • Ensure that the recording is not displayed in the activity page
      • Run the script  'php mod/bigbluebuttonbn/cli/update_dismissed_recordings.php'
      • Ensure that a message similar to this one is displayed:

      Processing BigbluebButton Recording(id:XX), in course Recording course(id:YY)....
              -> Recording data found for Recording ID:XXXXXXX

      • Ensure that the recording is not displayed in the activity page
      • Run the script  'php mod/bigbluebuttonbn/cli/update_dismissed_recordings.php --run' (the --run option will do the modifications)
      • Ensure that the recording is now displayed in the activity page
      •  
      Show
      The scheduled task are now PHP unit tested.   To test the new command line you need to be able to access you database and change some fields. Create a new BigbluebuttonBN activity Join the meeting Record for a couple of seconds End  the meeting Wait for a minute Run the cron to refresh the data regarding the recordings Ensure that the recording is displayed in the activity page Go to your database and find your recording in the bigbluebuttonbn_recordings table. Change its status to 1 (dismissed) Ensure that the recording is not displayed in the activity page Run the script  'php mod/bigbluebuttonbn/cli/update_dismissed_recordings.php' Ensure that a message similar to this one is displayed: Processing BigbluebButton Recording(id:XX), in course Recording course(id:YY)....       -> Recording data found for Recording ID:XXXXXXX Ensure that the recording is not displayed in the activity page Run the script  'php mod/bigbluebuttonbn/cli/update_dismissed_recordings.php --run' (the --run option will do the modifications) Ensure that the recording is now displayed in the activity page  

    Description

      Following up MC-5523, I think there might be an explanation to why some recording have disappeared. I am not yet sure about the validity of some hypothesis, but by looking at the status of the recording (1 = RECORDING_DISMISSED), it might be because the recording was not reachable at some point, and set as dismissed:

      https://github.com/moodle/moodle/blob/master/mod/bigbluebuttonbn/classes/recording.php#L719

      I am trying to figure out what is the exact nature of this change but might have a patch that would resolve this problem attached to the ticket.

      Attachments

        Activity

          People

            lmdavid Laurent DAVID
            lmdavid Laurent DAVID
            Shamiso Jaravaza Shamiso Jaravaza
            Paul Holden Paul Holden
            Kim Jared Lucas Kim Jared Lucas
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 2 hours, 38 minutes
                1d 2h 38m

                Clockify

                  Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.