Print Failure

Open
#13,137 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
django, docker, python
Domain
backend

Research direction

Reproduce on a Docker deployment of 1.6.3: generate the example Sales report and use the report-history download, then trace the print/download request to the endpoint that should return the generated file. Compare the redirect target with the dashboard route and check whether the report file is created before the response. Done means both actions return the report or label instead of redirecting, with a regression test around the report download endpoint.

Written by the indexing model from the issue text.

Description

not enough info question report
Please verify that this bug has NOT been raised before.
  • I checked and didn't find a similar issue
Describe the bug*

Not able to actually print reports or labels. After requesting the print job a new tab is opened in the browser that redirects to the dashboard. When trying to download reports from the report history the same behavior occurs.

Steps to Reproduce
  1. Attempt to generate report from Sales (behavior occurs with example report)
Expected behaviour

New tab opens back at instance dashboard.

Deployment Method

Docker

Version Information

1.6.3

Try to reproduce on the demo site

I tried to reproduce

Is the bug reproducible on the demo site?

Not reproducible

Relevant log output

I have reviewed this report for correctness and filled out all sections.
  • I have checked this report. I acknowledge that filing bugs via AI agents without review might lead to being blocked.
Dominant language
Python
Stars
7.7k
Forks
1.6k
Avg merge
21h 45m
Merged PRs (30d)
204

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from inventree/InvenTree

All issues in inventree/InvenTree

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.