[Beta 64-bit build] Bug reports

No idea if this is an actual 64 bit RW issue or not, but since it became an issue after I updated here goes.

I have been working with a tablet and RW for some offline. Since I was intending only working off this system (an SP4) cloud sync after each session was not important. But when the new version came I downloaded and stuck it on a USB stick to install on this system. Continued to work and test the new build, and didn't run into any issue that were not already there (highlight a word for color or bold and it randomly applies that change to random text in the topic being one I have had since day 1).

So, move ahead and It was time to sync my realm. This is where the problem began, I am unable to complete the sync. I have to delete server data in lieu of this SP4 realm sync, my fault made a change on my desktop RW install and sync'd it(duh), but I was aware of this. But it gets about 2/3rds or 3/4s along the sync status bar and errors our with network error.

I have sync'd on the SP4 on an enterprise network, fails same way.
I have then tried on a Rogers Cable internet on same SP4, fails same way.
I have used my G7 over LTE Hotspot and fails same at on SP4.

So I backed up my realm, imported on my desktop RW install, and it fails sync same way.

I am pretty sure it is not a network error, I doubt my Enterprise, Rogers, LTE and Bell DSL all have exactly the same issue.

Has anyone recently had to delete cloud data and sync up local data recently? this is not the first time I have done this, but I have not done it in sometime, and it worked fine before.

If you delete a realm from the cloud you can't sync. The realm is gone. I'm not sure what you were doing in the past but it wasn't that.

kbs666 said:

If you delete a realm from the cloud you can't sync. The realm is gone. I'm not sure what you were doing in the past but it wasn't that.

Click to expand...

When you have a cloud realm that does not match your local realm, you are presented with the option to delete the cloud server version, and take the local data, or delete the local data and accept the cloud server data.

I am choosing to delete the cloud data and sync (keep) my local data. The device has been working offline for some time, but along the way with out thinking I remembered a change I wanted to make and did it on my desktop and sync'd it. My fault, but when I realized what I did, I knew this option would pop up, and was prepared, I made the change on the SP4 so it would be all good when the time came to sync.

This caused a mismatch, as it should. So the option appears for me to make a choice, keep the local or keep the server.

I am choosing to keep the local, but it fails sync no matter what system or what ISP I use.

Exmortis said:

When you have a cloud realm that does not match your local realm, you are presented with the option to delete the cloud server version, and take the local data, or delete the local data and accept the cloud server data.

Click to expand...

Uhm.. this is where kbs666 is getting confused. I don't have the screen in front of me, but I am pretty sure the wording for the options does not include "delete the cloud data". I am pretty sure both options talk about which to keep, meaning the other is overwritten.

I say this because the word DELETE is used carefully due to "deleting the could data" (i.e., deleting the entire Realm) is a one-time permanent change.

I think that's where the confusion here is coming from.

Obviously, I could be wrong if the wording actually is "delete the cloud data", but I am pretty sure it is phrased as which to keep.

Silveras said:

Uhm.. this is where kbs666 is getting confused. I don't have the screen in front of me, but I am pretty sure the wording for the options does not include "delete the cloud data". I am pretty sure both options talk about which to keep, meaning the other is overwritten.

I say this because the word DELETE is used carefully due to "deleting the could data" (i.e., deleting the entire Realm) is a one-time permanent change.

I think that's where the confusion here is coming from.

Obviously, I could be wrong if the wording actually is "delete the cloud data", but I am pretty sure it is phrased as which to keep.

Click to expand...

The actual wording is "Discard". doesn't change it won't sync once I have chosen to "Discard the server data and keep the local data".

However since I am back from family visits and travels I have just updated the client to the latest build and will see if it works.

if the GUID was removed from the server, you are probably out of luck without some kind of intervention from LWD staff. It won't matter what version of the client you have.

Viking2054 said:

if the GUID was removed from the server, you are probably out of luck without some kind of intervention from LWD staff. It won't matter what version of the client you have.

Click to expand...

well it still shows up every time I look at my realms, it has not gone away.

Newer version did not solve it. So I will submit a bug report.

Right now, on the machine where you have the latest copy of your realm:
1. Backup the database.
2. Do a full export of your realm.
3. Import the realm into a new realm to make sure it's a good export.

Worst case scenario:
1. You now have a backup-realm in case anything happens.
2. You have the export to fall back on if anything else goes wrong.

Still open the case with LWD and seek their help, but do these other things as well. Backup, backup, backup!

EightBitz said:

Right now, on the machine where you have the latest copy of your realm:
1. Backup the database.
2. Do a full export of your realm.
3. Import the realm into a new realm to make sure it's a good export.

Worst case scenario:
1. You now have a backup-realm in case anything happens.
2. You have the export to fall back on if anything else goes wrong.

Still open the case with LWD and seek their help, but do these other things as well. Backup, backup, backup!

Click to expand...

I have a back up, but have not exported the realm and tried to import, not a bad idea. Will try that tonight.

Circling back on this topic. I had an "index out of bounds" error during the holidays so I reverted to a known good backup, reinstalled an older version and pressed on. Now that we're in the new year (and I have a solid backup) I've updated to the most recent. No problems encountered (knock on faux wood).

These index out of bounds errors seem very odd. They're not happening after an import operation correct? It just doesn't seem like this sort of thing should be happening outside of bulk processing operations.

kbs666 said:

These index out of bounds errors seem very odd. They're not happening after an import operation correct? It just doesn't seem like this sort of thing should be happening outside of bulk processing operations.

Click to expand...

The error was tied to new logic used for sorting names. The "natural" sort logic splits up names into pieces that treat numbers as numbers for comparison so that "abc34" appears before "abc123". That's a simple example, and the logic handles lots of very complicated situations, including the use of commas and periods (e.g. "10,000,000bc" is treated as "10000000bc" for comparison).

There were some edge cases in the logic that crapped out when dealing with situations that were clearly typos in the names assigned to topics. That's why it only impacted three realms out of everyone. Those needed to be fixed so that the realms could load.

EightBitz said:

Right now, on the machine where you have the latest copy of your realm:
1. Backup the database.
2. Do a full export of your realm.
3. Import the realm into a new realm to make sure it's a good export.

Worst case scenario:
1. You now have a backup-realm in case anything happens.
2. You have the export to fall back on if anything else goes wrong.

Still open the case with LWD and seek their help, but do these other things as well. Backup, backup, backup!

Click to expand...

Was a good idea, but alas, it was not to be. I was able to index, do the content fix up, and export and import into a "testie" Telon realm (created just to do the import). All went perfect..until...

Interestingly I decided to try and convert the (both old and new) Telon realm from other to pathfinder (was no such animal when I began Telon). It failed on both the old and newly imported realm. I submitted a report back in 2017 with regard to this and was told it was identified and would be fixed in an upcoming update.

I tried to sync the newly imported "testie" Telon realm and it failed just the like the old version. I compacted my realm and it fell by almost 400mb in size, but alas, it is still borked and I am still unable to sync even a new version or the old version of it.

So it isn't related to the discarding and re sync action. Troubleshooting is 99% finding out what isn't the issue. I also know it isn't related to the conversion fails, as that have been around for over a year. Nor is it due to content issues, and it exports and imports fine. Index also completes, as does compacting. Every other realm, and I have more then a few, sync with out issue.

I suspect I will have to submit my Master Realm for analysis to see what nasty worm has invaded my Telon unbeknownst to King Horus Targonor Furth!

rob said:

The error was tied to new logic used for sorting names. The "natural" sort logic splits up names into pieces that treat numbers as numbers for comparison so that "abc34" appears before "abc123". That's a simple example, and the logic handles lots of very complicated situations, including the use of commas and periods (e.g. "10,000,000bc" is treated as "10000000bc" for comparison).

There were some edge cases in the logic that crapped out when dealing with situations that were clearly typos in the names assigned to topics. That's why it only impacted three realms out of everyone. Those needed to be fixed so that the realms could load.

Click to expand...

Does that mean I can now saely upgrade from 245 version to the latest one without destroying my realm? Would be quite some work to copy everything to word and then re-paste into the most recent RW version.

@McGray: If you were affected by this issue, I'd say yes. I was one of the edge cases and all is working perfectly after upgrading. Make a backup just in case for peace of mind but you won't need it.

AEIOU said:

@McGray: If you were affected by this issue, I'd say yes. I was one of the edge cases and all is working perfectly after upgrading. Make a backup just in case for peace of mind but you won't need it.

Click to expand...

Thanks for the reply. Tried it and now everything works as intended! Yay!