Error logs when Publish fails -

Developer corner
1

Hey @jptrinh - huge congrats on the new position - very excited for what you will contribute!

So … we just had a situation where our publish was failing with an error. We have resolved the issue as I will describe below - but this example leads to a “feature / support request” -

For context we have 6 or so custom components created in VUE - and will have many more as the project grows.

WeWeb support responded with:

"We can’t have the detail for now, but we think that the issue is because of one of your custom coded component Orbiterbox or Commandbar. Could you try to remove them and publish without or it’s not possible?"

So … we removed the Commandbar custom component as we had just imported that - and the publish still failed so we knew that was not the issue.

Then, we started rolling back the versions of EACH custom component one at a time - to before the first publish failure. And we were able to identify the issue was with a component called orbiterOrbits so … issue was a different component not even mentioned by WeWeb support -

So … my “feature / support request” would be that IF a build fails to publish - (and the workspace has a business seat and is using custom components) - we should be able to get the actual error logs from the build process. This would empower us to bug hunt faster on our end and puts less pressure on support. Sure seems like a win-win to me.

Thoughts??

1 Like
2

Had the same issue as you last year, I proposed the same thing, it hasn’t been implemented yet, so yeah. The best thing you can do is simply go and try to debug it yourself, there is some patterns that don’t work, I’ve seen some. But for now it’s either you have the knowledge through expensive trial and error about what to watch out for, or you need to go and try and debug this. Or of course wait for logs, which tend to be inconclusive anyway.

3

well … I am pretty damn sure these error logs could be improved … “inconclusive” is anther way to say … “this should be improved”. And I suspect that is the core issue at hand.

4

Thank you very much!
Yup, totally agree! I will poke the team about how that kind of feature would fit in the roadmap.
I know that improving the Dev documentation will be tacked around Q4, so that should also prevent some errors.

2 Likes