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

script page elements are duplicated when log output is paginated and browsed #16756

Open
FliesLikeABrick opened this issue Jun 27, 2024 · 0 comments
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@FliesLikeABrick
Copy link

FliesLikeABrick commented Jun 27, 2024

Deployment Type

Self-hosted

NetBox Version

4.0.5

Python Version

3.11

Steps to Reproduce

Create a custom script that logs at least 500 messages, such as the attached:

from extras.scripts import *
class CreateMessagesScript(Script):
    class Meta:
        name = "Show Message Pagination"
        description = "Generate over 500 messages"
    def run(self, data, commit):
        for i in range(1,555):
            self.log_success(i)
        output=[]
        return '\n'.join(output)

Execute the script

Page through the output. For each page that is viewed, rendered page elements around the log table are duplicated.

Expected Behavior

Paging through logs should not impact static page elements surrounding the output table

Observed Behavior

The "output" box is duplicated

image

and so are elements above the log table, such as the script status, runtime, etc
image

@FliesLikeABrick FliesLikeABrick added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Jun 27, 2024
@arthanson arthanson added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Jun 28, 2024
@arthanson arthanson removed their assignment Jun 28, 2024
@arthanson arthanson self-assigned this Jul 8, 2024
@arthanson arthanson added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants