Skip to content

Intended behavior of check_nosync with local_first and sync_list #3284

Answered by MattofBum
MattofBum asked this question in Q&A
Discussion options

You must be logged in to vote

Well, I found my issue and it was a problem with my config file. I had included an extra quote on my check_nosync line:
check_nosync = "true""

It seems like most of the other configure options are verified in some way, so perhaps bools should be too.

I’m not sure my case in particular should be treated as a malformed line or an invalid value.

It matches the configRegex, so if you want it as a malformed line modifying the regex from ctRegex!(^(\w+)\s*=\s*"(.*)"\s*$) to ctRegex!(^(\w+)\s*=\s*"([^"]*)"\s*$) should do the trick.

Verifying that the value of a bool is either “true” or “false” would be useful. Right now, the code just checks for “true”:
setValueBool(key, c.front.dup == "true" ? …

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by abraunegg
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants