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

Issue with Allocated parts counter #5477

Closed
1 of 4 tasks
templeofhead opened this issue Aug 25, 2023 · 6 comments
Closed
1 of 4 tasks

Issue with Allocated parts counter #5477

templeofhead opened this issue Aug 25, 2023 · 6 comments
Labels
bug Identifies a bug which needs to be addressed inactive Indicates lack of activity question This is a question

Comments

@templeofhead
Copy link

Please verify that this bug has NOT been raised before.

  • I checked and didn't find a similar issue

Describe the bug*

Hello. Recently i've updated my inventree packaged install from 0.11 to 0.12.3 and when i was done with the update, i went to check if everything was present and found an interesting thing: in the build order tab, when i open\create new build order, the spinner after allocated parts keeps spinning indefinitely instead of showing how many of the parts total isnt allocated.
It was working on 0.11 alright, but not on the newer version.

Same behaviour was present when i exported database and imported it on the fresh vm, same is as with updating current installation. Screenshot is below, for reference.
spinner

Steps to Reproduce

  1. Either update from older version or export database and import into the new one.
  2. Open "build order" tab, navigate to "build order details"
  3. In the details submenu, the loading spinner that indicates the amount of allocated parts keeps spinning as if loading of parts amount is in the loop.

Expected behaviour

After brief loading (amount of allocatable parts arent that big) the counter should display the actual amount (from 0 to 20)

Deployment Method

  • Docker
  • Bare metal

Version Information

Version Information:

InvenTree-Version: 0.12.3
Django Version: 3.2.19
Commit Hash: 1f3a49b
Commit Date: None
Commit Branch: stable
Database: sqlite3
Debug-Mode: False
Deployed using Docker: False
Platform: Linux-5.4.0-156-generic-x86_64-with-glibc2.31
Installer: PKG
Target: ubuntu:20.04
Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.0.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}]

Please verify if you can reproduce this bug on the demo site.

  • I can reproduce this bug on the demo site.

Relevant log output

No response

@templeofhead templeofhead added bug Identifies a bug which needs to be addressed question This is a question triage:not-checked Item was not checked by the core team labels Aug 25, 2023
@wolflu05
Copy link
Contributor

wolflu05 commented Aug 25, 2023

@templeofhead
Copy link
Author

Yeah, i did hard refresh, multiple browsers as well - didn't work.

@wolflu05
Copy link
Contributor

Have you also checked the browser console if there is any log or errors? Also the network tab?

@SchrodingersGat
Copy link
Member

@templeofhead I think that this is a bug due to the way that the required data is loaded. This might not get addressed before our move to react (see #5212)

@templeofhead
Copy link
Author

templeofhead commented Aug 25, 2023

If its just some script bug and not the db problem, and it wouldnt impede anything on the long run (at least until you alleviate it in future versions) think it can be considered a minor inconvenience.

In browser console i get this:

DevTools failed to load source map: Could not load content for https://inventree.xx/static/script/chartjs-adapter-moment.min.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
DevTools failed to load source map: Could not load content for https://inventree.xx/sm/ac6ca6e51d8435fbb492538442f7060550b81bb0c2505d4048856d957213e3a8.map: Unexpected token '<', ..."


<!DOCTYPE "... is not valid JSON

@github-actions
Copy link
Contributor

This issue seems stale. Please react to show this is still important.

@github-actions github-actions bot added the inactive Indicates lack of activity label Oct 25, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 1, 2023
@matmair matmair removed the triage:not-checked Item was not checked by the core team label Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Identifies a bug which needs to be addressed inactive Indicates lack of activity question This is a question
Projects
None yet
Development

No branches or pull requests

4 participants