The current system first fetches all shallow content, then all deep content, movies and movie scenes, before storing the data and fetching the media.
This leads to problems with memory usage, error isolation and expired media tokens. The data should probably be stored as soon as it's retrieved, however we also want to maintain good concurrency.
The current system first fetches all shallow content, then all deep content, movies and movie scenes, before storing the data and fetching the media.
This leads to problems with memory usage, error isolation and expired media tokens. The data should probably be stored as soon as it's retrieved, however we also want to maintain good concurrency.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The current system first fetches all shallow content, then all deep content, movies and movie scenes, before storing the data and fetching the media.
This leads to problems with memory usage, error isolation and expired media tokens. The data should probably be stored as soon as it's retrieved, however we also want to maintain good concurrency.