Errors in Firefox console during import of channel
See original GitHub issueObserved behavior
When importing a channel, some errors show in the Firefox’s console.
On the side, I don’t know if the above error causes this “131% progress” error coz I cannot reproduce this consistently. But during import the progress bar moves back and forth and the values indicate … 20%, 50%, 25%, 65%,… 90%, 131%, 93%, 100% in order.
I managed to capture this screenshot.
Try 2 When I tried again, it showed the errors but the progress bar is ok:
Try 3 Re-tried again and this time the import did not proceed and showed a “Something went wrong!” page:
This is the console error:
21:17:31.263 TypeError: An id must be specified api-resource.js:752
Here’s the log: console-export-2020-6-12_21-21-4.txt
Expected behavior
No errors must show during content import.
User-facing consequences
Import functionality may be broken due to those errors.
Errors and logs
Try 1 and 2 debug.txt kolibri.txt console-export-2020-6-12_21-2-48.txt
Steps to reproduce
- Delete the
~/.kolibri/
folder - make a backup if needed. - Checkout
release-v0.14.x
. - Follow the Setting up Kolibri for Development.
- Make sure to show the Firefox Console window to notice the errors.
- Do a Quick Setup of Kolibri, then import Kolibri QA Channel from Studio using the token
nakav-mafak
. You can also do the usual import by selecting resources. - Notice the errors shown in the Firefox console.
Context
- Kolibri version:
release-v0.14.x
branch - Operating system: macOS v10.14.6 Mojave
- Browser: Firefox v77.0.1
- Python: v3.7.7
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (11 by maintainers)
Top GitHub Comments
Note the main error here is actual the final one in the second screenshot
TypeError: id must be defined
- here an actual error is occurring as the frontend code is asking the API resource layer to fetch an object with idundefined
.@indirectlylit Sure. Here are the issues: #7197, #7196 (Could you please add labels? I am not sure what priority are they) and a PR containing 404 logging as it was faster than opening a new issue 😃