Skip to content

Conversation

@casparvl
Copy link
Contributor

Fix index out of range error by making sure that request_bot_build_issue_comments always returns a status table with vectors of equal size

Fixes #343

@casparvl casparvl marked this pull request as ready for review August 27, 2025 14:57
@casparvl
Copy link
Contributor Author

Proven to work in casparvl/software-layer#4 (comment)

@casparvl
Copy link
Contributor Author

Also, this is what you now get when the only build for a given arch is unfinished: casparvl/software-layer#4 (comment)

I think that's an improvement over what we had. Note that the regular bot:status command will also show builds-in-progress now:

casparvl/software-layer#4 (comment)

Comment on lines +1336 to +1340
elif (
row['job status'] == 'submitted'
or row['job status'] == 'received'
or row['job status'] == 'running'
):
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
elif (
row['job status'] == 'submitted'
or row['job status'] == 'received'
or row['job status'] == 'running'
):
elif row['job status'] in ['submitted', 'received', 'running']:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bot:status last_build throwing an index out of range

2 participants