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

Fix BLOCKSTRETCHACTION situation after handles #1054

Conversation

michal-josef-spacek
Copy link
Contributor

@michal-josef-spacek michal-josef-spacek commented Dec 3, 2024

Last fix was wrong. Each handle could have zero, one or more indexes.

Fixes GH#1053

@rurban rurban self-assigned this Dec 3, 2024
@rurban
Copy link
Contributor

rurban commented Dec 3, 2024

No, the name of the num field must be the same as the array, just with the num_ prefix. There's special dynapi logic there

@michal-josef-spacek
Copy link
Contributor Author

Yes, I see errors in JSON conversions :-)

@michal-josef-spacek
Copy link
Contributor Author

@rurban better?

Last fix was wrong. Each handle could have zero, one or more indexes.

Fixes GH#1053
@michal-josef-spacek michal-josef-spacek changed the title WIP: Fix BLOCKSTRETCHACTION situation after handles Fix BLOCKSTRETCHACTION situation after handles Dec 4, 2024
@michal-josef-spacek
Copy link
Contributor Author

@rurban PR is fine from my side :-)

Copy link
Contributor

@rurban rurban left a comment

Choose a reason for hiding this comment

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

Almost. Just indexes[].index to indexes[] as simple BL vector. I have more time on Friday

@michal-josef-spacek
Copy link
Contributor Author

Almost. Just indexes[].index to indexes[] as simple BL vector. I have more time on Friday

I prepared alternative: #1055

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.

2 participants