mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #218] Error: path isundefined #208
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#208
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bernd-wechner on GitHub (Dec 27, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/218
Wow, another error. Cryptic message alas. Was synching fine, but today I updated my Bookmarks app on Nextcloud to 0.15.1 as per a notification request, and the NextCloud itself to NexCloudPi v0.67.8 and NextCloud 14.0.4.2. And Now I see this error:
I checked the debug log but I can't see an obvious answer, the term "Path is" appears nowhere, and "undefined" is all over the log. I can as ever send one along by email for diagnosis but don't know of a way to send personal info along to a developer without it going public - I noticed recently GitLab supports confidential issues that can only be seen by the submitter and project members. Neat.
@bernd-wechner commented on GitHub (Dec 27, 2018):
More info I have:
Conclusion is something was broken with the Firefox Cache .... how that happened and why it correlated so well with my NextCloud upgrades is a mystery. I sent the log file by email, maybe it lends a clue. Maybe not worth pursuing.
@marcelklehr commented on GitHub (Dec 27, 2018):
Mh. Weird. 👍 for sending the log -- it seems I didn't get your email, though :/
@marcelklehr commented on GitHub (Dec 30, 2018):
Yeah, that's a good idea.
@marcelklehr commented on GitHub (Jan 12, 2019):
@bernd-wechner ?
@bernd-wechner commented on GitHub (Jan 13, 2019):
Marcel the problem is gone, but I did send the log by email to: mklehr@gmx.net at Thu, 27 Dec 2018 22:09:44 +1100.
I did just forward it to:
- mail address redacted -
as that is the ReplyTo address on an email I got from you via github once and so might reach you.
@marcelklehr commented on GitHub (Jan 13, 2019):
This mail created a new comment over here, but didn't carry on the attachment :D Could you try the normal address again? 😄 🙈
@bernd-wechner commented on GitHub (Jan 22, 2019):
I did resend it a few days ago. No luck getting it? Low priority given it works again, but I imagine I'd be curious what caused it if I had more time ;-).
@marcelklehr commented on GitHub (Feb 7, 2019):
No luck. I did sort out some mail issues recently, so hopefully I'm reachable again :/
Anyway, closing this for now.
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.