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