New Issue

/notifications internal server error (after deleting a blog and an article) #759

Open

opened by deckname · 2 comments

deckname commented (Migrated from github.com)

On a different account I can still view the /notifications url and receive notifications.

Plume 0.4.0-alpha-4

Operating system: Debian 9
Web Browser: Firefox and Chromium

I have two accounts. On one account I posted an article in a blog, then deleted the blog and article and made a new blog and article. Before /notifications worked on this account, now it doesn't, when I click the bell it doesn't load and when I go to the URL directly as well. It gives a 500 internal server error. On a different account I can still view the /notifications url and receive notifications. Plume 0.4.0-alpha-4 - **Operating system:** Debian 9 - **Web Browser:** Firefox and Chromium

Amolith commented (Migrated from github.com)

I don't know if the root cause is the same but I'm experiencing the same issue and so is another of my users. I checked the logs for what happens directly after clicking the Notifications button and this is all that was output.

May 23 15:06:33 de1.nixnet.xyz plume[22621]: thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Db(NotFound)', src/libcore/result.rs:997:5

I have it running with systemd so the command I ran to check logs was journalctl -eu plume. If there's another log location with more verbosity, I'm happy to provide output from there as well!

I don't know if the root cause is the same but I'm experiencing the same issue and so is [another of my users](https://mastodon.social/@vasia/104210752525853977). I checked the logs for what happens directly after clicking the `Notifications` button and this is all that was output. ``` May 23 15:06:33 de1.nixnet.xyz plume[22621]: thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Db(NotFound)', src/libcore/result.rs:997:5 ``` I have it running with systemd so the command I ran to check logs was `journalctl -eu plume`. If there's another log location with more verbosity, I'm happy to provide output from there as well!

elegaanz commented (Migrated from github.com)

You can add RUST_BACTRACE=1 to the environment to get a full backtrace next time, which may help.

You can add `RUST_BACTRACE=1` to the environment to get a full backtrace next time, which may help.

No Milestone

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Loading…

There is no content yet.

Labels Milestones

/notifications internal server error (after deleting a blog and an article) #759