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.

Sign up for GitHub

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

Jump to bottom

error when viewing device details on fresh installation #2686

Closed
indirectlylit opened this issue Nov 24, 2017 · 3 comments
Closed

error when viewing device details on fresh installation #2686

indirectlylit opened this issue Nov 24, 2017 · 3 comments
Assignees
@indirectlylit
Labels
bug Behavior is wrong or broken P0 - critical Priority: Release blocker or regression
Milestone
0.7.0

Comments

@indirectlylit
Copy link
Contributor

indirectlylit commented Nov 24, 2017 •
edited by mrpau-richard
Loading

Observed behavior

reported by @mrpau-richard:

tested this in the latest Pre-release of Kolibri Windows installer at https://github.com/learningequality/kolibri/releases

I have this error referring to screenshot below:
screen shot 2017-11-24 at 3 02 37 pm

Expected behavior

device details page should show without error

User-facing consequences

broken experience

Errors and logs

...

Steps to reproduce

That error can be reproduced in the fresh installation. After the user created an admin account and navigate to the device info page.

Context

  • Kolibri version: 0.7
  • Operating system: Windows 7 32 bit.
  • Browser: Google chrome Version 62.0.3202.94 (Official Build) (32-bit)
  • Server log file: server.log
@indirectlylit indirectlylit added the bug Behavior is wrong or broken label Nov 24, 2017
@indirectlylit indirectlylit added this to the 0.7.0 milestone Nov 24, 2017
@indirectlylit indirectlylit mentioned this issue Nov 24, 2017
Closed
@indirectlylit
Copy link
Contributor Author

indirectlylit commented Nov 24, 2017 •
edited
Loading

@mrpau-richard would you mind sharing the OS you're testing on, and any server logs? (feel free to edit the issue description directly)

@mrpau-richard
Copy link
Contributor

@indirectlylit I added the OS and the log file I used to reproduce this issue.

@indirectlylit indirectlylit added the P0 - critical Priority: Release blocker or regression label Nov 27, 2017
@indirectlylit indirectlylit self-assigned this Nov 27, 2017
@indirectlylit
Copy link
Contributor Author

should have been addressed with #2713

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@indirectlylit indirectlylit

Labels
bug Behavior is wrong or broken P0 - critical Priority: Release blocker or regression
Projects
None yet
Milestone
0.7.0
Development

No branches or pull requests
2 participants
@indirectlylit @mrpau-richard