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

[BUG] Unexpected behaviour on bash 3.x #21

Closed
Tracked by #77
jgabaut opened this issue Jun 5, 2023 · 1 comment · Fixed by #88
Closed
Tracked by #77

[BUG] Unexpected behaviour on bash 3.x #21

jgabaut opened this issue Jun 5, 2023 · 1 comment · Fixed by #88
Assignees
Labels
bug Something isn't working help wanted Extra attention is needed invalid This doesn't seem right

Comments

@jgabaut
Copy link
Owner

jgabaut commented Jun 5, 2023

I tested the repo on a M1 Macbook (I think it had bash 3.x) and many errors happened during operation.

Will need further investigation on last version, and I suspect the added git submodule update --init after a switch - may break stuff.
1.4.6 should not have this problem, while still having colliding filenames for the test folder...

@jgabaut jgabaut added bug Something isn't working invalid This doesn't seem right help wanted Extra attention is needed labels Jun 5, 2023
@jgabaut
Copy link
Owner Author

jgabaut commented Nov 14, 2023

Version 1.7.0 added a check to quit early if current bash version is <4.

Since most likely 1.8.x will use associative arrays, this issue could be closed with no fix for now.

@jgabaut jgabaut changed the title Unexpected behaviour on bash 3.x [BUG] Unexpected behaviour on bash 3.x Dec 18, 2023
@jgabaut jgabaut self-assigned this Dec 23, 2023
@github-project-automation github-project-automation bot moved this from Todo to Done in Port amboso to Rust Dec 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed invalid This doesn't seem right
Projects
Development

Successfully merging a pull request may close this issue.

1 participant