Closed nettnikl closed 5 months ago
Hi, I am glad that you like it. Yes, good idea. I'll add giteas error message as well.
I just added a pr for this. https://github.com/cooperspencer/gickup/pull/216/files Basically checking if it is a valid duration and if it is not it switches to the configured interval of the repository. I also added the error message from Gitea if anything happens during the change of the interval.
Please let me know if that solves your issue or if you are missing anything.
Thanks, will test it!
@nettnikl did you test it? was it ok for you?
I merged it. It will go out with the next release.
I just pushed a new release with this fix included.
Hi,
thanks for the project, very useful! Did some updates and saw it wasnt updating for some time - checking it i'm getting confusing messages. Also faced https://github.com/cooperspencer/gickup/issues/208 (had to apply a workaround to patch the system cert store) and https://github.com/cooperspencer/gickup/issues/117#issuecomment-1281532186, but those were self-explanatory. I didn't get any of those issues before for this config, so either gitea or gickup changed in some regards. I think i found the remaining issue in the logs, see below. Could we get a validation that all required values are there, a error message reporting on the 422 in the logs (instead of swallowing the underlying error message whole) or some default value for gitea sync interval?
Here the relevant code: https://github.com/cooperspencer/gickup/blob/7175ab6d17370a33fee7ec2c8828d3609062e007/gitea/gitea.go#L109C22-L109C36