You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ellativity brought up earlier that she received a notification for "Today's podcasts" in her feed with a DevNews episode, but when clicking it, it sends a 404. (see image below)
I also wouldn't expect for a notification to go out for a podcast episode that isn't live.
Screenshots
Additional context
This happened previously. Our feed reader was reading a previous episode of DEVDiscuss and blocking a newer one that was trying to come in — I think because their naming conventions were similar?
The text was updated successfully, but these errors were encountered:
Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you.
Feature requests that require more discussion may be closed. Read more about our feature request process on forem.dev.
To our amazing contributors: issues labeled type: bug are always up for grabs, but for feature requests, please wait until we add a ready for dev before starting to work on it.
To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem/oss. The OSS Community Manager or the engineers on OSS rotation will follow up.
For full info on how to contribute, please check out our contributors guide.
It appears as if the episode is set as reachable = false in the DB. Maybe it was reachable but then modified to not-reachable but it appears as cached?
Describe the bug
@ellativity brought up earlier that she received a notification for "Today's podcasts" in her feed with a DevNews episode, but when clicking it, it sends a 404. (see image below)
Expected behavior
When I go to https://dev.to/devnews/s4-e1-platforms-as-utilities-archiving-yahoo-answers-and-companies-rescinding-accepted-offers I expect to see season 4, episode one. And navigating here - https://dev.to/devnews the podcast episode should appear at the top of the list.
I also wouldn't expect for a notification to go out for a podcast episode that isn't live.
Screenshots
Additional context
This happened previously. Our feed reader was reading a previous episode of DEVDiscuss and blocking a newer one that was trying to come in — I think because their naming conventions were similar?
The text was updated successfully, but these errors were encountered: