Sticky Consultation Note

[warpok]

Every few lines, I get the notice in the Journal that the Notes for Judges have been archived. This is the title of a note I made last year. To save server space, I have archived the notes in some books that have been consultant checked. I leave one Note in chapter one giving the link to a Google Drive where the notes are archived. But this one note keeps being resaved multiple times per day. No one is editing it!

[warpok]

Oh, but guess what! That note is not showing up in the first chapter or anywhere in the book.
That note was made in January this year.
OK, I have made a new note with the identical title to see if that will solve the problem.

[teusbenschop]

Ah, hope it resolves the problem.

Else it would help to set the filter such that the notes shows up in Bibledit Cloud, and then delete it from there.

[warpok]

I think my action did fix the problem. Thanks.

[warpok]

I am sorry to report that the VERY-Sticky Note is still there. As I said before, previously that error kept appearing, but when I went to find the note I could not find it. So I created a note with the same name on July 11th. That note does appear in the Cloud and also the Client.
BUT in the Client journal the line
16 August 2024 16:07:21 | Notes: Receiving: *Semua Notes Hakim2 sudah disimpan
is appearing every hour or so.

[teusbenschop]

The reason for this behaviour is hard to tell just now. Could I receive credentials to access the server and see its behaviour myself? Perhaps it would give a clue to start with.

[warpok]

Thanks so much, Teus! To clarify: The notes with the form like this are still appearing in the client: 16 August 2024 16:07:21 | Notes: Receiving: *Semua Notes Hakim2 sudah disimpan But I searched in the Cloud journal and didn't find the word Hakim. That note title is still being sent, even though I have changed the title that shows up in Judges/Hakim2 chapter one, and also changed the verse number for the note. The credentials: ssh ***@***.*** -p 62026 I login with pwd <removed>. Thanks for your time in researching this tiny bug in your otherwise perfect program. Phil ================ Phil Fields ***@***.*** USA and Whatsapp: +1 479-524-7005 dailybiblereading.info albata.info 303 Ryan Ct., Siloam Springs, AR 72761 One King to rule them all, One Son to find them, One Blood to cleanse them all, And from the dark unbind them. ================ Pada Kam, 22 Agu 2024 pukul 11.49 Teus Benschop ***@***.***> menulis:

…

The reason for this behaviour is hard to tell just now. Could I receive credentials to access the server and see its behaviour myself? Perhaps it would give a clue to start with. — Reply to this email directly, view it on GitHub <#950 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDSIJLAJ3UXNQCCJKNLD33ZSYJBFAVCNFSM6AAAAABKXU5SXWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBVGIYTENJVGM> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>

[teusbenschop]

Thank you for the details. I thought it was safer for you if nobody could see the password, to do this, I edited your comment and removed the password.

After logging into the server, I could locate the note, and removed it. Everything should be well now.

The note was weird, it only had the summary of "Semua Notes Hakim2 sudah disimpan", without any other details like assignees, bible, date modified, passage, severity and status and contents.

[warpok]

Thank you, Teus! Yes, oops! I forgot that my reply to you would be posted in the thread! Senior slip. So perhaps the partial note was cut somehow in a bad internet connection? Thanks so much. Phil

[teusbenschop]

... So perhaps the partial note was cut somehow in a bad internet connection? ...

It's hard to tell what the cause of the partial note was. Bad internet connection, as you say, is a likely cause, but on the other hand, the checksum would have failed in case the note was cut off. It's really hard to tell how it got there.

[teusbenschop]

Reopening this note because it would be better if this would get fixed upon note indexing. That is, if the indexer finds an incomplete note, it removes that note, and emails the managers and higher roles about the content it deleted.