You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The only way to establish whether Link encountered a problem is to do a text analysis of the result. So far, it appeared that I could rely on looking for the string "ERRORS ENCOUNTERED" in the result returned by Link's Create function, but that is not quite true.
I got <Unknown Debug options in "/path/2/.linkconfig": NOTIFY> despite the fact that no Link was established.
It should use "ERRORS ENCOUNTERED". Even better would be the return of proper numeric return codes indicating success (0) or failure (any positive integer).
The only way to establish whether Link encountered a problem is to do a text analysis of the result. So far, it appeared that I could rely on looking for the string "ERRORS ENCOUNTERED" in the result returned by Link's
Create
function, but that is not quite true.I got <Unknown Debug options in "/path/2/.linkconfig": NOTIFY> despite the fact that no Link was established.
It should use "ERRORS ENCOUNTERED". Even better would be the return of proper numeric return codes indicating success (0) or failure (any positive integer).
To Reproduce
I accidentally hat a file
.linkconfig
that reads:That stops Cider from working properly.
I am on:
The text was updated successfully, but these errors were encountered: