App has been syncing for a long time after multiple edits, many image attachments

[anon88882136]

I’m rebuilding my notes using the markdown importer at the moment - after this is complete I will see if the process happens again.

Originally I was copy-pasting from another web-based notes app, I wonder if some unexpected characters or tags were introduced that caused a problem?

[craftzdog (Takuya Matsuyama)]

Thanks and sorry for the trouble!
I guess so but I haven’t ever encountered such problem.
The connection hangs up if it took over 10 minutes.
I need to know why a particular note causes timeout…
I guess it is just taking too long time to encrypt because there is no exceptions thrown.

[craftzdog (Takuya Matsuyama)]

Now you have 51 notes and the sync looks working fine.

[anon88882136]

I seem to have just triggered it again while re-creating notes? I was adding the images back into a markdown import and now the syncing is taking longer.

[craftzdog (Takuya Matsuyama)]

Yep, the error occurred again!

[craftzdog (Takuya Matsuyama)]

Do you get any errors in console?

[craftzdog (Takuya Matsuyama)]

On another topic

I tried deleting some recently added images, and then deleted all notes in the sub-notebook that I was working in when the error started occurring. The sync is currently stuck again, and the console output currently looks like:

  app:error Failed to load image: { [not_found: missing]
  status: 404,
  name: 'not_found',
  message: 'missing',
  error: true,
  reason: 'missing',
  docId: 'file:GVJYgUGf' } +0ms
  app:error Failed to load image: { [not_found: missing]
  status: 404,
  name: 'not_found',
  message: 'missing',
  error: true,
  reason: 'missing',
  docId: 'file:ELCbSpbD' } +7s
(node:12346) UnhandledPromiseRejectionWarning: ReferenceError: logger is not defined
at /usr/lib/inkdrop/resources/app.asar/main.js:1:40546
(node:12346) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 5)
(node:12346) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I hope this helps!

You inserted the image with id file:GVJYgUGf but the app says not found? That’s strange…
I added some debug logs on the server to investigate.
Could you try it again?

[craftzdog (Takuya Matsuyama)]

I’m afraid that I couldn’t get any additional information from the server.
Would you mind sending me a suspected image file via email?

[anon88882136]

Sorry, the forum blocked me from posting too frequently again and I had to wait until today. I have the app running again now - it is still trying to sync without success, no errors in the console.

I could zip together a collection of suspect images, I wasn’t able to isolate it to just one - after removing all of the notes in the notebook where the issue started, the sync still seems to be stuck even though they are gone (a cache corruption or similar?).

Unfortunately I cannot test this any further for now - my plan was to migrate to inkdrop over the weekend and then subscribe, but the week has started again and I’ve had to cancel for the time being! Apologies for not being able to solve this!

[craftzdog (Takuya Matsuyama)]

Hi. I’ll check the configuration of Discourse.

Seems like the app is stuck to send data for some reason. The server does not process any data from your client.
So I guess the bug resides in the client app.

I’m not sure what’s going wrong. I have to look into your data to reproduce the problem in my environment.

Sure, I completely understand. Thank you for your all cooperations!
Could you stop the app for now? Thanks!

[anon88882136]

Hmm, now I am too curious. Thinking of the content that is there, and your stance and respect for privacy - what if I were to zip the .config directory and share with you privately? Given how much if your time I’ve taken I would like to help resolve the actual issue.

It sounds like the only practical way to get to the root cause of this.

[craftzdog (Takuya Matsuyama)]

It’s totally ok if you don’t feel like sending your private data to me.
I will use it only for debugging.

If you set up your own CouchDB, you can reproduce it on your server. (See here).
If it’s the Inkdrop server-side issue, you should be able to sync without the problem.

[anon88882136]

No, let’s do it! I will zip the data and send you a link on your email address if that is ok?

[craftzdog (Takuya Matsuyama)]

Yes, please!

[anon88882136]

Ok, sent.

[craftzdog (Takuya Matsuyama)]

Reproduced!

[anon88882136]

I hope I didn’t break anything too badly

[craftzdog (Takuya Matsuyama)]

Ah, it was due to the batch size (Request too big error). I changed it as well and the sync finished with my dev server. Strange.
Needs more time to investigate.

[anon88882136]

That’s odd - when I changed it the first time it didn’t seem to resolve, although it may be different now after edits and re-imports of the notes, or I didn’t give it enough time to finish syncing?

[craftzdog (Takuya Matsuyama)]

Not sure. I will try it also on production tomorrow.