breaking changes after "upgrade" - problems with "run --local"? | Community
Skip to main content
Urs_Boller
Community Advisor
Urs_BollerCommunity Advisor
Community Advisor
September 23, 2020
Solved

breaking changes after "upgrade" - problems with "run --local"?

  • September 23, 2020
  • 1 reply
  • 1756 views

I just realized a strange behaviour - let's assume the problem is sitting in front of the desktop ...

nevertheless, maybe someone else has the same issue. What happened? I just upgraded npm packages and aio to latest versions and tried the "aio app run --local" as usual. What I see looks as if there is some deployment similar to "aio app deploy" for some of the files, especially the "manifest.yml". not only takes it a lot longer to build my local files, it also looks quite different than before. did something change in the build process?

But the most confusing part: I had an app up and running in the same environment (I used "aio app deploy" before) with a schedule to run every hour. after the uprade the hourly scheduled stopped working ... I checked the "aio runtime activation list" without seeing any error. I assume that the last "aio app run -- local" uploaded the manifest.yml and stopped the trigger ...

happy to provide more information and get response if somebody has similar issues...

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by sarahxxu

Hi @urs_boller 

Could you provide a bit more information to help us debug? How can we try to reproduce this?

 

Sarah

1 reply

sarahxxu
Adobe Employee
sarahxxuAdobe EmployeeAccepted solution
Adobe Employee
September 24, 2020

Hi @urs_boller 

Could you provide a bit more information to help us debug? How can we try to reproduce this?

 

Sarah

Urs_Boller
Community Advisor
Urs_BollerCommunity AdvisorAuthor
Community Advisor
September 25, 2020

@duynguyen_adobethanks a lot for the hint! I finally found out what was made me think something has broken: the console entries for 'aio app run --local' have changed (they look now very simialar to aio app deploy). using the --verbose shows some of the old console entries (and a lot more). Here are just some of the entries now hidden in --verbose:

The main problem I see in 'aio app run --local' (without --verbose) is he fact that it takes a long time until the first entry appears. It would be great if you could add a short message like 'starting local environment ...' at the beginning just to show that it started ...

however, I will close this question since I think everything works fine it was just me making false assumtions. thanks for the support

Terms & ConditionsAccessibility statement

Loading footer...