Failed to Push Verse Update

General Issues and Bug Reporting
, , ,
41

We are continuing to have extremely slow push verse updates, same as others in this post what was 10 seconds is now 3+ minutes and often fails, video attached.

This is making code iteration extremely frustrating.

1 Like
42

Thank you

43

Hi folks:

As an update, we’re unfortunately still investigating what’s going wrong here.

Could you help us out? If you’re running into this issue, could you try the following:

  • Create a new UEFN project from a blank template. Add some trivial Verse code (Like a simple Print statement).

  • Publish one version of that project.

  • Now close the UEFN editor, re-open the project, make some new trivial Verse code changes, launch a session, and attempt to [Push Verse Changes].

  • If you hit the same issue, please capture your UEFN editor logs at that point and post them here (or DM it directly to me).

Thanks!

44

Hi all:

As another update, we’ve made a fix for this issue that you’re seeing that will be released in an upcoming patch.

4 Likes
45

Hey Sonictke

Does this also fix the slow verse push speeds ? and the normal push speeds? there was other threads but they got closed as dupes even though they seem like 2 separate issues ?

46

Hey @AtAshTag:

This should fix the main delay that we’re seeing being reported in this thread, which, from the logs, indicates a failure to download the previously-published version’s artifacts for performing local backwards compatibility checking against.

We did close some other threads as they were duplicates of this issue. If you found a thread that was mistakenly closed and indicates a different issue, please post the link to that thread so that I can confirm and re-open it if necessary.

47

Thankyou for the confirmation

What i mean is this current post we are in is for a “Failed to push verse update” caused by an error whereas the slow push changes is not technically an error as it passes checks and doesn’t fault its just slow.

The ones i had seen closed were in regards of the slow push which i why i asked as this post as the title implies is about a failed verse push update(Not slow speeds).

It sounds like the issue will be resolved if not already so thankyou for you assistance in fixing this issue yourself and the team sure made alot of devs happy :slight_smile:

48

Hi there @AtAshTag:

Understood. I should clarify that there are some classes of issues that were being investigated, and of which one was fixed:

  • There are failed [Push Verse Changes] operations due to the changes being made just being straight-up not supported by that workflow at the moment. The Verse team is aware of this and we have not solved that problem. For now, only the back-up dialog that shows up to prompt you to [Push Changes] if the hot-reload fails should indicate such a case.

  • There are failed [Push Verse Changes] that fail when they should succeed, regardless of the timeout issues caused by trying to download the previously-published versions for local backwards compatibility checking purposes. We are still investigating the issues that we’ve seen in these cases; it’s slow because thus far these have been all separate issues.

  • There are failed/slow [Push Verse Changes]/[Push Changes] operations due to the repeated timeouts of trying to download the previously-published version for local backwards compatibility checking. A fix for this issue will be deployed in an upcoming patch.

5 Likes