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

Website change - Parsing trackable slow and logs missing #15549

Closed
Lineflyer opened this issue Apr 4, 2024 · 7 comments
Closed

Website change - Parsing trackable slow and logs missing #15549

Lineflyer opened this issue Apr 4, 2024 · 7 comments
Assignees
Labels
Bug Issues classified as a bug Prio - High A significant malfunction of a feature/function. High user impact. Regression An exitsting function/feature does no longer work as expected.

Comments

@Lineflyer
Copy link
Member

Lineflyer commented Apr 4, 2024

Describe your problem!

Login was restored by #15547 but testing shows, there is more to fix (as already seen on CI tests).
Trackable parsing does not seem to work well.

How to reproduce?

Try to open any trackable via its public or secret code

Actual result after these steps?

  • c:geo is stuck on loading the trackable information for a rather long time
  • After the trackable has been loaded in c:geo the logbook tab is missing

Expected result after these steps?

Fast loading and logbook working

Reproducible

Yes

c:geo Version

2024.03.19

System information

No response

Additional Information

No response

@Lineflyer Lineflyer added Bug Issues classified as a bug Prio - High A significant malfunction of a feature/function. High user impact. Regression An exitsting function/feature does no longer work as expected. labels Apr 4, 2024
@Lineflyer
Copy link
Member Author

Not sure if someone is available today/tomorrow to dive into this problem.
If not, we should think about releasing a new bugfix release tomorrow anyway to get at least basic functionality out to users again.

@moving-bits
Copy link
Member

I can try to look into it tomorrow evening

@bekuno
Copy link
Member

bekuno commented Apr 5, 2024

Now we have no search results neither fot TB number nor tracking code.
Edit: I had a configuration problem. But the text check is really slow.

I had the chance to have a look here. The TB information has many changes.
Therefore I propose to release a new c:geo release with the login fix and fix the trackable parsing (and other problems) later on.

@moving-bits
Copy link
Member

I'm currently analyzing the changes. First findings:

  • They have strapped the data-tags invented for "spotted at" (etc.) info, breaking location/status detection! I'll write to Bryan.
  • They added aria attributes in some places (breaking our regexp). Will add those to the formula.

@Lineflyer
Copy link
Member Author

Shall we brew an "interim release" to at leat enable cachers for the weekend (fix login)?

@moving-bits
Copy link
Member

moving-bits commented Apr 5, 2024

I can build a bugfix release with current state of release branch (login fixed, TB not fixed). Will start doing so now (as fixing the regexp for TB log parsing will take some more time).

BTW: We got 50 or so tickets on support regarding the login issue, despite the note within c:geo...

Edit: Release 2024.04.05 is rolling out. It includes the login fix (as well as other minor fixes since the last release 2024.03.19), but no TB fix yet. (Will continue tomorrow trying to fix those.)

@moving-bits moving-bits self-assigned this Apr 7, 2024
@moving-bits
Copy link
Member

fixed with #15556

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues classified as a bug Prio - High A significant malfunction of a feature/function. High user impact. Regression An exitsting function/feature does no longer work as expected.
Projects
None yet
Development

No branches or pull requests

3 participants