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

Unable to create the Incomplete output in Build Order #7192

Closed
2 of 6 tasks
Jaishankar872 opened this issue May 9, 2024 · 10 comments · Fixed by #7196
Closed
2 of 6 tasks

Unable to create the Incomplete output in Build Order #7192

Jaishankar872 opened this issue May 9, 2024 · 10 comments · Fixed by #7196
Labels
bug Identifies a bug which needs to be addressed build Build orders javascript Pull requests that update Javascript code old user interface Issues with Old User interface question This is a question
Milestone

Comments

@Jaishankar872
Copy link

Please verify that this bug has NOT been raised before.

  • I checked and didn't find a similar issue

Describe the bug*

Unable to create the new build output. while click the incomplete output option site through error as Bad request 400

Steps to Reproduce

  1. Click the Build in top
  2. Select the Build Order
  3. Just click the Incomplete output

image

Expected behaviour

Unable to understand

Deployment Method

  • Docker
  • Package
  • Bare metal
  • Other - added info in Steps to Reproduce

Version Information

Version Information:

InvenTree-Version: 0.14.5
Django Version: 4.2.11
Commit Hash: b32f081
Commit Date: Apr 18 2024

Database: postgresql
Debug-Mode: False
Deployed using Docker: True
Platform: Linux-6.5.0-28-generic-x86_64-with
Installer: DOC

Active plugins: False

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

  • I can reproduce this bug on the demo site.

Relevant log output

172.18.0.1 - - [09/May/2024:15:25:55 +0000] "GET /api/notifications/?read=false HTTP/1.0" 200 2 "https://-----------/build/2/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) Gecko/20100101 Firefox/125.0"
Bad Request: /api/part/test-template/
@Jaishankar872 Jaishankar872 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 May 9, 2024
@SchrodingersGat
Copy link
Member

If you look in the "network" tab of the developer console in your browser, you should be able to see what the actual error message is for the 400 request. This will be very helpful in working out what is going on here.

@SchrodingersGat SchrodingersGat added build Build orders and removed triage:not-checked Item was not checked by the core team labels May 9, 2024
@Jaishankar872
Copy link
Author

Below refer below the logs from web browser

image

image

@SchrodingersGat
Copy link
Member

@Jaishankar872 thanks, but I do need to see the "Response" tab as shown here:

image

Please blank out any sensitive information that may be returned there.

@Jaishankar872
Copy link
Author

"Response" tab

image

@SchrodingersGat
Copy link
Member

Ok, thanks. And what data was in the "request" tab?

@Jaishankar872
Copy link
Author

Nothing in request tab

image

@SchrodingersGat
Copy link
Member

Ok..

If you navigate to /part/365/ - is this part marked as "trackable"?

@Jaishankar872
Copy link
Author

No, It is not marked as trackable
image

@SchrodingersGat SchrodingersGat added old user interface Issues with Old User interface javascript Pull requests that update Javascript code labels May 10, 2024
@SchrodingersGat SchrodingersGat added this to the 0.15.0 milestone May 10, 2024
@SchrodingersGat
Copy link
Member

Ok, then that is why the request is failing - it is trying to receive test results for a non-trackable part.

Fix incoming in #7196

@Jaishankar872
Copy link
Author

Yes, It is working now.
Thanks for your support !!!!!!!!!!

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 build Build orders javascript Pull requests that update Javascript code old user interface Issues with Old User interface question This is a question
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants