Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RemoteStorage error #31

Closed
entropitor opened this issue Mar 23, 2014 · 16 comments
Closed

RemoteStorage error #31

entropitor opened this issue Mar 23, 2014 · 16 comments

Comments

@entropitor
Copy link

I get next js error when trying to sync with remotestorage.

GET http://domain.com/storage/caske33/notes/ 403 (Forbidden) domain.com/storage/caske33/notes/:1
Possibly uncaught error:  
[Error]
 Error: Received faulty directory response for: /notes/
    at Object.<anonymous> (https://laverna.cc/scripts/libs/remotestorage.js:1215:25)
    at notifyConsumer (https://laverna.cc/scripts/libs/remotestorage.js:25:45)
    at https://laverna.cc/scripts/libs/remotestorage.js:71:11 remotestorage.js:68
Error happened with cloud storage API 

(domain.com is a valid domain - I just obfuscated it here).

@andtheWings
Copy link
Contributor

This may or may not be related, but I'm posting here for the sake of keeping remotestorage errors in the same place.

I and raucao on the remotestorage forums have both found that the app crashes after initially connecting to remotestorage. Both columns in the app go blank. This is solved by refreshing back to the Laverna homepage. Not a big deal, but something to iron out.

I and silverbucket on the remotestorage forums have found that the sync is not actually functioning. I am using "5apps" to currently host my remotestorage server. It registers that Laverna is connected but no space is actually used in the storage status bar. I hooked up an Internet Explorer instance of Laverna to remotestorage, but none of my notes from Firefox synced into the app in Internet Explorer.

Forum Reference - http://community.remotestorage.io/t/evernote-replacement-laverna-just-released-remotestorage-support/171/8

@entropitor
Copy link
Author

Yes, no syncing on chrome browser here either. (haven't tested on other browsers).

@silverbucket
Copy link

same issues for me, as @andtheWings described. Chiming in here to get pinged when there's an update.

@raucao
Copy link

raucao commented Mar 25, 2014

Speaking for the @remotestorage core team: thanks a lot for integrating it into your app! Looks fantastic and I can't wait to use it daily for my notes.

Let us know if we can help somehow, and please don't hesitate to ask us anything on http://community.remotestorage.io or in #remotestorage on Freenode.

FYI: the current release version has a couple of problems, and the Chrome bug might be one of them. We're releasing a beta of 0.10 this week with completely rewritten caching and sync as well as a bunch of other bug fixes. We highly recommend switching to that as soon as it's released!

wwebfor added a commit that referenced this issue Mar 25, 2014
@wwebfor
Copy link
Member

wwebfor commented Mar 25, 2014

Thanks @skddc. By the way do you have idea why @remotestorage works just fine with enabled cache, but with disabled cache we get an error, which was described in this issue by @caske33?

@raucao
Copy link

raucao commented Mar 26, 2014

Haven't seen that one yet. Would be great if you can create an issue describing the problem at https://github.com/remotestorage/remotestorage.js/issues

@raucao
Copy link

raucao commented Apr 4, 2014

Hi there,

We just released remoteStorage.js 0.10.0-beta with completely rewritten caching and sync backends (and fixing anon mode, which was broken in 0.9). Some apps are already using it in production with no problems so far (but better performance and stability). Would be great, if you could update it in Laverna as well. It might also fix errors like this on the way.

We broke the API in very few places (only removing some deprecated things), but it should be a 1-minute upgrade, in case you're using one of the old calls. The library comes with automatic migration for existing cached data, which should be transformed to the new better format without having to do anything in your app.

Check out the changelog for details.

Cheers,
Basti

P.S.: Let me know if I can help with anything. We're also hanging out in #remotestorage on Freenode.

@raucao
Copy link

raucao commented Apr 11, 2014

FYI: we just released 0.10.0-beta2, which fixes an important bug we found during testing: http://community.remotestorage.io/t/remotestorage-js-0-10-0-beta2-released/185

@andtheWings
Copy link
Contributor

Just an update, my notes sync fine now, but I still often observe the Laverna syncing button go on endless spinning cycles. Console reads {error: Object, missing: Array[0], valid: false}.

@wwebfor wwebfor added the bug label Oct 2, 2014
@raucao
Copy link

raucao commented Apr 29, 2015

remoteStorage.js hasn't been updated in quite a while it seems. We're currently at version 0.11.2.

I just checked out the repo in order to try and update it myself, but I get an error when trying to run the app from dist on master. Will create a seperate issue for that.

@wwebfor
Copy link
Member

wwebfor commented Dec 6, 2015

I'm not sure if we solved this but we tested in every browser by hand. Plus we tested it with automated tests (Nightwatch). But you can never be sure. Can any of you guys confirm that it works?

#76 #246 #255

@raucao
Copy link

raucao commented Dec 6, 2015

I just tested and synced something across browsers. Seems to work well!

@raucao
Copy link

raucao commented Dec 6, 2015

... could it be that checking off a todo item doesn't sync the note, though?

@wwebfor
Copy link
Member

wwebfor commented Dec 6, 2015

Strange it was supposed to work because after every update of data we trigger changes to RemoteStorage. I jut checked and it works. I guess there is some kind of bug.

@raucao
Copy link

raucao commented Dec 6, 2015

Alright, but definitely a smaller one. I could update a note's normal content and see it on the other end.

@wwebfor wwebfor added this to the 1. Refactor and fix bugs milestone Dec 28, 2015
@wwebfor
Copy link
Member

wwebfor commented Feb 9, 2016

I think this issue can be closed. If you have objections, we can reopen it again.

@wwebfor wwebfor closed this as completed Feb 9, 2016
4lch4 pushed a commit to 4lch4/laverna that referenced this issue Aug 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants