[TW5] Constant messages from discarded drafts

[James Knight]

Hey everyone, Love using TW5.

I'm on Tiddllywiki 5 5.0.14-beta Node.js installed through npm on an AMR system running a version of Debian
(Cubian on my Cubie truck to be specific)

I am consistently having the following error messages popups:

Sync error while processing 'Draft of 'Networking setup: Error: ENOENT, unlink '/ssd/html/tiddly/tiddlers/Draft of 'Networking setup'.tid'

and

 Sync error while processing 'Draft of 'New Tiddler 1: Error: ENOENT, unlink '/ssd/html/tiddly/tiddlers/Draft of 'New Tiddler 1'.tid'

I've had these pop up in the past with previous versions and my solution has always been to download a copy, wipe the server files then re-import my wiki (after clearing the error message on my local copy). I have just atempted to start completely clean and rebuild from scratch but now these messages are back.

Clearly not ideal. has anyone else had experiences with fixing this? or is there any simple way to just disable these messages as everything seems to work just fine it's just annoying to have to dismiss these dialog boxes every time I open my wiki.

[Jeremy Ruston]

Hi James

I'm sorry you've been having problems. Do these messages popup in the browser or in the server terminal? You mention dismissing the dialog boxes when you open the wiki in the browser, which makes it sound like the messages are appearing in the browser.

The error message means that the server side is trying to delete files corresponding to two different tiddlers, and in each case the deletion is failing because the file doesn't exist.

The thing that's very strange is that you're seeing these messages at startup, which presumably means that the deletion attempts were not caused by user interaction. I don't quite see how that could happen.

Best wishes

Jeremy

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

--
Jeremy Ruston
mailto:jeremy...@gmail.com

[Xavier Cazin]

Hi Jeremy,

I had the same experience several times, although it is difficult to tell when it exactly takes place.

I believe it happens when network connection between node and the browser is lost for a while, so that you are not sure whether changes have been fully processed.

In these situations, draft tiddlers actually get deleted on the server once the edited tiddler is saved, but TW5 seems to think they still exist and thus try to open them in vain on reload. Just restarting node on the same repository is enough to get everything in place again.

Sorry to not be more precise. If it still confusing, I'll try to take note more closely next time.

Xavier Cazin.

-- Xavier Cazin

[James Knight]

Jeremy,

Its the built in tiddlywiki alert. You can delete the dialogue but it will regenerate every time you load up the wiki.

Xavier,

That sounds exactly like what I'm experiencing as I tend to keep my wiki page open on my work browser all day.

But not that you mentioned restarting the node I realise I haven't done that (although I think it might persist through reboots, but I can't be sure).

I've done another clean wipe so I'll keep an eye on it.

[James Knight]

Ok so I have experienced this issue again.

It defiantly appears to be when I loose connection with the server. Our unstable internet at work blinked out momentarily and when I added a note in my tiddly it saved fine but popped up the error about the draft again. I attempted to have this error occur when refreshing or closing the browser but it apears to handle those situations fine.

As a quick work around I have set up a Cron job to shutdown my tiddlywiki then start it again as this seems to fix it.

[Jeremy Ruston]

Thanks James, that's helpful. I'm investigating,

Best wishes

Jeremy

[Oleg]

I can confirm this is still happening in 5.1.7. Is there a way to just disable drafts altogether?

Oleg

[Jeremy Ruston]

> Is there a way to just disable drafts altogether?

Not really, the draft mechanism is deeply tied into the editing and navigation mechanism. But I think that would be treating the symptom; drafts are just ordinary tiddlers, and what we appear to have here is a problem that may impact data integrity for any tiddler.

I've spent some time again trying to duplicate this problem. I've managed to trigger the same error once, but not been able to duplicate it since. I'd really appreciate some help with reproducing it.

Best wishes

Jeremy.

[Nicola Worthington]

On Thursday, 12 March 2015 20:13:24 UTC, Jeremy Ruston wrote:

> Is there a way to just disable drafts altogether?

Not really, the draft mechanism is deeply tied into the editing and navigation mechanism. But I think that would be treating the symptom; drafts are just ordinary tiddlers, and what we appear to have here is a problem that may impact data integrity for any tiddler.

I've spent some time again trying to duplicate this problem. I've managed to trigger the same error once, but not been able to duplicate it since. I'd really appreciate some help with reproducing it.

I'm seeing this quite frequently as well. I think it might be happening when I have more than one browser window open to my TW at a time. (Although I'm not editing in both at the same time).

This is just a hunch though.

I'll try and work out when it's happening and report back with what I find out. 

[Mark Brown]

Also been experiencing this in 5.1.7 soon after installing the node js edition on a vps

Also get the errors on page load. In case the errors are informative a screen shot is attached

I've been playing with having new tiddlers created by setting the title field of a template tid to a new unique title. Could this be the reason?

[Stefan Szekeres]

I'm experiencing this error also, (running from node.js) can we edit something to remove this alert ?

[Stefan Szekeres]

Done, just created the two missing files (the drafts) manually in the folder then rebooted the server. Don't really know if the creation was necessary but the alerts are gone. 

[Stefan Szekeres]

syncer-server: Dispatching 'delete' task: This

FileSystem: Deleted file C:\Users\user\Desktop\tiddlywikiroot\mynewwiki\tiddle

rs\This.tid

syncer-server: Dispatching 'save' task: 102_1612.JPG

$:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:116

.writeFile(fileInfo.filepath,tiddler.fields.text,{encoding: typeInfo.encoding}

                                                                    ^

TypeError: Cannot read property 'encoding' of undefined

    at $:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:116:74

    at FileSystemAdaptor.getTiddlerFileInfo ($:/plugins/tiddlywiki/filesystem/fi

lesystemadaptor.js:76:3)

    at FileSystemAdaptor.saveTiddler ($:/plugins/tiddlywiki/filesystem/filesyste

madaptor.js:105:7)

    at Syncer.dispatchTask ($:/core/modules/syncer.js:458:21)

    at Syncer.processTaskQueue ($:/core/modules/syncer.js:401:9)

    at null._onTimeout ($:/core/modules/syncer.js:380:26)

    at Timer.listOnTimeout (timers.js:110:15)

Now i get this in node.js, not sure why ?

On Wednesday, 20 August 2014 06:58:25 UTC+3, JimyKK wrote:

[Jeremy Ruston]

Hi Mark,

If you are experiencing the discarded draft sync error alerts at startup with 5.1.7 or below, you should be able to remove the alerts by locating and deleting the tiddler files corresponding to them - they would normally be in the root folder of your wiki and have filenames such as "___temp_alerts_alert.tid".

Best wishes

Jeremy.

On Mon, Mar 30, 2015 at 12:05 AM, Stefan Szekeres <stefan....@gmail.com> wrote:

C:\Users\user\Desktop\tiddlywikiroot>tiddlywiki mynewwiki --server 8080 $:/cor

e/save/all text/plain text/html "" "" 192.168.1.102

Serving on 192.168.1.102:8080

(press ctrl-C to exit)

syncer-server: Dispatching 'save' task: Draft of 'te iubesc enorm'

FileSystem: Saved file C:\Users\user\Desktop\tiddlywikiroot\mynewwiki\tiddlers

\Draft of 'te iubesc enorm'.tid

syncer-server: Dispatching 'delete' task: Draft of 'te iubesc enorm'

FileSystem: Deleted file C:\Users\user\Desktop\tiddlywikiroot\mynewwiki\tiddle

rs\Draft of 'te iubesc enorm'.tid

syncer-server: Dispatching 'delete' task: Draft of 'New Tiddler'

FileSystem: Deleted file C:\Users\user\Desktop\tiddlywikiroot\mynewwiki\tiddle

rs\Draft of 'New Tiddler 1'.tid

syncer-server: Dispatching 'delete' task: New Tiddler

FileSystem: Deleted file C:\Users\user\Desktop\tiddlywikiroot\mynewwiki\tiddle

rs\New Tiddler.tid

syncer-server: Dispatching 'delete' task: This

FileSystem: Deleted file C:\Users\user\Desktop\tiddlywikiroot\mynewwiki\tiddle

rs\This.tid

syncer-server: Dispatching 'save' task: 102_1612.JPG

$:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:116

.writeFile(fileInfo.filepath,tiddler.fields.text,{encoding: typeInfo.encoding}

                                                                    ^

TypeError: Cannot read property 'encoding' of undefined

    at $:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:116:74

    at FileSystemAdaptor.getTiddlerFileInfo ($:/plugins/tiddlywiki/filesystem/fi

lesystemadaptor.js:76:3)

    at FileSystemAdaptor.saveTiddler ($:/plugins/tiddlywiki/filesystem/filesyste

madaptor.js:105:7)

    at Syncer.dispatchTask ($:/core/modules/syncer.js:458:21)

    at Syncer.processTaskQueue ($:/core/modules/syncer.js:401:9)

    at null._onTimeout ($:/core/modules/syncer.js:380:26)

    at Timer.listOnTimeout (timers.js:110:15)

C:\Users\user\Desktop\tiddlywikiroot>tiddlywiki mynewwiki --server 8080 $:/cor

e/save/all text/plain text/html "" "" 192.168.1.102

Serving on 192.168.1.102:8080

(press ctrl-C to exit)

syncer-server: Dispatching 'save' task: 20140410_030328.jpg

FileSystem: Saved file C:\Users\user\Desktop\tiddlywikiroot\mynewwiki\tiddlers

\20140410_030328.jpg

syncer-server: Dispatching 'save' task: 20140309_121833.jpg

FileSystem: Saved file C:\Users\user\Desktop\tiddlywikiroot\mynewwiki\tiddlers

\20140309_121833.jpg

syncer-server: Dispatching 'save' task: 102_1715.JPG

$:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:116

.writeFile(fileInfo.filepath,tiddler.fields.text,{encoding: typeInfo.encoding}

                                                                    ^

TypeError: Cannot read property 'encoding' of undefined

    at $:/plugins/tiddlywiki/filesystem/filesystemadaptor.js:116:74

    at FileSystemAdaptor.getTiddlerFileInfo ($:/plugins/tiddlywiki/filesystem/fi

lesystemadaptor.js:76:3)

    at FileSystemAdaptor.saveTiddler ($:/plugins/tiddlywiki/filesystem/filesyste

madaptor.js:105:7)

    at Syncer.dispatchTask ($:/core/modules/syncer.js:458:21)

    at Syncer.processTaskQueue ($:/core/modules/syncer.js:401:9)

    at null._onTimeout ($:/core/modules/syncer.js:380:26)

    at Timer.listOnTimeout (timers.js:110:15)

Seems like this happened because my gf was also editing some page in parallel.

On Wednesday, 20 August 2014 06:58:25 UTC+3, JimyKK wrote:

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[Jeremy Ruston]

Hi Stefan

I think the problem in your case is a bug pre-5.1.8 whereby files with uppercase extensions don't work properly:

https://github.com/Jermolene/TiddlyWiki5/issues/1418

Best wishes

Jeremy

--
You received this message because you are subscribed to the Google Groups "TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[Oleg Lavrovsky]

Nevertheless Stefan's suggestion to 'touch' the files and restart the server worked for me as well.

O/