Eventing Function log file path nesting for every pause, edit and resume

At first, the function was created and the application log was started writing into the default path …/…/@eventing/b_<bucket_name>/s_<scope_name>/<function_name>.log

Later I paused the function, edited it and resumed. then a new log file got created in nested path like below.

…/…/@eventing/b_<bucket_name>/s_<scope_name>/b_<bucket_name>/s_<scope_name>/<function_name>.log

this nested phenomenon continues endlessly - I mean directly proportional to the number of pause,edit,resume cycles.

Actually, by the time I realized this, I could see 16 levels of nested paths got created and still going on.

not sure am I misconfigured any settings or it is a bug ?

@jon.strabala , need your help

Yes this is a bug Log in - Couchbase database it impacted 7.1.4, 7.1.0, 7.1.1, 7.1.2, 7.2.0, 7.1.3 and was fixed in 7.2.0

sorry unable to access the link - unable to find it in the 7.2.0 release notes either.

Not in the release notes as it not a functional issue the impacts production but if you like email me at Jon.Strabala@Couchbase.com and I’ll send you a PDF of the issue and the resolution.

thanks Jon, sent an email