Files
reflector/server
Mathieu Virbel f3ae187274 fix: waveform can generate NaN in json database (#481)
* refactor: fixes transcript duration type, NaN in waveform, and prepare for postgres migration

* fix: ensure we don't have NaN in waveform

* fix: missing assertionerror

Co-authored-by: pr-agent-monadical[bot] <198624643+pr-agent-monadical[bot]@users.noreply.github.com>

* fix: potential empty array

---------

Co-authored-by: pr-agent-monadical[bot] <198624643+pr-agent-monadical[bot]@users.noreply.github.com>
2025-07-15 20:46:19 -06:00
..
2023-08-10 14:37:39 +05:30
2025-03-25 11:09:01 +01:00
2025-02-03 16:11:01 +01:00
2023-07-26 15:13:46 +07:00
2023-08-03 12:28:22 +05:30
2025-06-17 16:30:23 -04:00
2025-02-28 13:00:22 +01:00
2023-12-18 20:22:15 +07:00
2023-08-29 10:58:27 +02:00
2025-02-03 16:11:01 +01:00
2024-08-12 12:22:21 +02:00
2025-06-17 12:18:41 -04:00
2023-10-15 17:38:13 +01:00
2025-03-11 15:12:25 +01:00

AWS S3/SQS usage clarification

Whereby.com uploads recordings directly to our S3 bucket when meetings end.

SQS Queue (AWS_PROCESS_RECORDING_QUEUE_URL)

Filled by: AWS S3 Event Notifications

The S3 bucket is configured to send notifications to our SQS queue when new objects are created. This is standard AWS infrastructure - not in our codebase.

AWS S3 → SQS Event Configuration:

  • Event Type: s3:ObjectCreated:*
  • Filter: *.mp4 files
  • Destination: Our SQS queue

Our System's Role

Polls SQS every 60 seconds via /server/reflector/worker/process.py:24-62:

Every 60 seconds, check for new recordings

sqs = boto3.client("sqs", ...) response = sqs.receive_message(QueueUrl=queue_url, ...)