Skip to content

Issue 6321 - lib389 get_db_lib function may returns the wrong db type #6322

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

Merged
merged 2 commits into from
Sep 10, 2024

Conversation

progier389
Copy link
Contributor

@progier389 progier389 commented Sep 6, 2024

get_db_lib returns the default db type instead of the configured one because of caught exceptions
Fix the import issue if instance is online
Fix the DSEldif parameter for the offline case

Issue: #6321

Reviewed by: @tbordaz (Thanks!)

@progier389 progier389 linked an issue Sep 6, 2024 that may be closed by this pull request
@progier389
Copy link
Contributor Author

Added a test case and realized that there was also a problem in the off line case.

@progier389 progier389 added the work in progress Work in Progress - can be reviewed, but not ready for merge. label Sep 6, 2024
@progier389
Copy link
Contributor Author

Hum,
At firts, have I chosen to havoid parametrization to avoid too many restart by I realized that I have to test both offline and online results so the server is restarted at every steps anyway. I think I should better use a parmetrized fixture to set the db type in dse.ldif and the server state.

Copy link
Contributor

@tbordaz tbordaz left a comment

Choose a reason for hiding this comment

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

LGTM

@progier389 progier389 removed the work in progress Work in Progress - can be reviewed, but not ready for merge. label Sep 9, 2024
@progier389
Copy link
Contributor Author

Commited new version with parametrized test (which is indeed simpler)

@progier389 progier389 merged commit 4b1fd46 into 389ds:main Sep 10, 2024
197 checks passed
vashirov pushed a commit that referenced this pull request Apr 23, 2025
…#6322)

* Issue 6321 - lib389 get_db_lib function may returns the wrong db type

get_db_lib returns the default db type instead of the configured one because of caught exceptions
Fix the import issue if instance is online
Fix the DSEldif parameter for the offline case

Issue: #6321

Reviewed by: @tbordaz (Thanks!)
vashirov pushed a commit that referenced this pull request Apr 23, 2025
…#6322)

* Issue 6321 - lib389 get_db_lib function may returns the wrong db type

get_db_lib returns the default db type instead of the configured one because of caught exceptions
Fix the import issue if instance is online
Fix the DSEldif parameter for the offline case

Issue: #6321

Reviewed by: @tbordaz (Thanks!)
vashirov pushed a commit that referenced this pull request Apr 23, 2025
…#6322)

* Issue 6321 - lib389 get_db_lib function may returns the wrong db type

get_db_lib returns the default db type instead of the configured one because of caught exceptions
Fix the import issue if instance is online
Fix the DSEldif parameter for the offline case

Issue: #6321

Reviewed by: @tbordaz (Thanks!)
@progier389 progier389 deleted the i6321 branch May 20, 2025 13:05
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.

lib389 get_db_lib function may returns the wrong db type
2 participants