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

1.5.2 The wormhole jump are duplicated by the character. #822

Closed
integral0 opened this issue Jul 23, 2019 · 8 comments
Closed

1.5.2 The wormhole jump are duplicated by the character. #822

integral0 opened this issue Jul 23, 2019 · 8 comments
Assignees
Milestone

Comments

@integral0
Copy link

Bug?

chrome_2019-07-23_11-44-05

@mrurb
Copy link

mrurb commented Jul 23, 2019

We have the same problem on our 1.5.2, it seems like each user gets logged every 5 seconds for about 7-10 minutes

@exodus4d
Copy link
Owner

hmmm interesting I´ll check asap

@mrurb
Copy link

mrurb commented Jul 23, 2019

Yer this is me jumping once furth and back on the public pathfinder and just leaving it.
image

@exodus4d
Copy link
Owner

OK, looks like I can quick hotfix this by just replacing a single PHP file, this might also fix some issues (dublicate connections from #820). Ill do some tests...

@exodus4d
Copy link
Owner

@integral0 @mrurb I hot fixed the production server with the commit above (had to change 2 PHP files). Coud you please check if the error is gone. (I had to delete all recorded mass logs, since they are useless )

@mrurb
Copy link

mrurb commented Jul 23, 2019

@exodus4d from what i can tell this fixed the problem and also fixed the #820 problem. I'll play around with it some more, but everything seems good now.

@integral0
Copy link
Author

@integral0 @mrurb I hot fixed the production server with the commit above (had to change 2 PHP files). Coud you please check if the error is gone. (I had to delete all recorded mass logs, since they are useless )

The problem does not repeat. Thank you.

exodus4d added a commit that referenced this issue Jul 27, 2019
- Fixed issue where systems can not be deleted, closed #820
- Fixed duplicate jump mass records, closed  #822
@exodus4d
Copy link
Owner

I replaced the ugly hotfix (9da2a78) with a proper solution.
The checked state for historic "jump records", for new system/connection that should be added, is no longer a timestamp stored with the user SESSION.
The checked state is now stored with the "jump record" data in cache:

  • The cronjob now has access to it

There will be a new Hotfix release v1.5.3 available, today

@exodus4d exodus4d self-assigned this Jul 27, 2019
@exodus4d exodus4d added this to the v1.5.3 milestone Jul 27, 2019
@exodus4d exodus4d mentioned this issue Jul 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants