#17 config_from_file in INI parser does not throw an error on missing or inaccessible file
Closed: Fixed None Opened 15 years ago by sgallagh.

If the config file to be parsed does not exist, config_from_file should return ENOENT and leave it up to the calling function whether this should be treated as an error.

Currently, config_from_file returns an empty collection instead.


Addendum: the returned error_list should also report that the file was not found if print_file_parsing_errors is called.

Addendum: the returned error_list should also report that the file was not found if print_file_parsing_errors is called.

Addendum: the returned error_list should also report that the file was not found if print_file_parsing_errors is called.

Fields changed

status: new => assigned

Fields changed

status: new => assigned

Fields changed

status: new => assigned

I do not agree with the addendum: this is not a file parsing error. It should not be a part of the error list.

I do not agree with the addendum: this is not a file parsing error. It should not be a part of the error list.

I do not agree with the addendum: this is not a file parsing error. It should not be a part of the error list.

The main issue was fixed. [[BR]]
Steve agreed that the requirement mentioned in the addendum is not the right expectation.

resolution: => fixed
status: assigned => closed

The main issue was fixed. [[BR]]
Steve agreed that the requirement mentioned in the addendum is not the right expectation.

resolution: => fixed
status: assigned => closed

The main issue was fixed. [[BR]]
Steve agreed that the requirement mentioned in the addendum is not the right expectation.

resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

Fields changed

rhbz: => 0

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to dpal
- Issue set to the milestone: Iteration 3

7 years ago

Metadata Update from @sgallagh:
- Issue set to the milestone: void (was: Iteration 3)

7 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/1059

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata