question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Python publish fails while parsing build_summary

See original GitHub issue

A change is rolling out in Azure that causes the following error when deploying with func azure functionapp publish. This happens for apps using remote build on Linux, which is only Python apps by default.

Unexpected character encountered while parsing value {. Path ‘[0].build_summary’, line 1, position 609.

Full logs
> func azure functionapp publish <app name>
Getting site publishing info...
Creating archive for current directory...
Performing remote build for functions project.
Deleting the old .python_packages directory
Uploading 1.61 KB [###############################################################################]
Remote build in progress, please wait...
Unexpected character encountered while parsing value: {. Path '[0].build_summary', line 1, position 612.

Workaround

The best workaround is to simply ignore the error. The deploy should have continued regardless and you can check the status in the portal by going to your function app, the “Deployment Center” section, and finally the “Logs” tab.

The issue was fixed in core tools by #3015 and #3021. We are releasing this fix soon and I will update this issue once a new version is ready. We hope to finish the core tools release before most users are impacted by the Azure rollout.

Issue Analytics

  • State:open
  • Created a year ago
  • Reactions:6
  • Comments:5 (1 by maintainers)

github_iconTop GitHub Comments

7reactions
qTipTipcommented, May 6, 2022

Hello!

We are also getting this error. Trying to install az-functions-core-tools-3 on a Debian-10 image. However, it seems like the releases are not available. Doing an apt search yields the following:

> apt search azure-functions-core-tools
Sorting... Done
Full Text Search... Done
azure-functions-core-tools/buster 4.0.4483-1 amd64
  Azure Function Core Tools v3

azure-functions-core-tools-2/buster 2.7.3188-1 amd64
  Azure Function Core Tools v2

azure-functions-core-tools-3/buster,now 3.0.3904-1 amd64 [installed]
  Azure Function Core Tools v3

azure-functions-core-tools-4/buster 4.0.3971-1 amd64
  Azure Function Core Tools v4

Seems like 3.0.3904 is the latest version available on debian. How can we resolve this as quickly as possible?

0reactions
mbassettcommented, May 6, 2022

For Ubuntu, @staritjari grab it out of the Microsoft repository. https://packages.microsoft.com/ubuntu/18.04/prod/pool/main/a/azure-functions-core-tools-4/

Debian 10, @qTipTip https://packages.microsoft.com/debian/10/prod/pool/main/a/azure-functions-core-tools-4/

https://docs.microsoft.com/en-us/windows-server/administration/linux-package-repository-for-microsoft-software

On Fri, May 6, 2022, 11:32 AM Michael Peng @.***> wrote:

@qTipTip https://github.com/qTipTip Could you try running apt install azure-functions-core-tools=3.0.4502-1? @staritjari https://github.com/staritjari, could you try installing azure-functions-core-tools rather than azure-functions-core-tools-4? Also, what regions are your apps in?

— Reply to this email directly, view it on GitHub https://github.com/Azure/azure-functions-core-tools/issues/3025#issuecomment-1119885971, or unsubscribe https://github.com/notifications/unsubscribe-auth/AARFPHTUKPDRQPBPIH4KCDLVIVQVNANCNFSM5TIE5ZEQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

Read more comments on GitHub >

github_iconTop Results From Across the Web

asp.net - 'Publish failed' but build succeeded?
When using Visual Studio 2008, when I "Publish Web Site", the application builds correctly, but then I get a "Publish failed" message:.
Read more >
Troubleshoot pipeline runs - Azure DevOps
When you run a server job or deploy to a deployment group using release pipelines, you don't consume any parallel jobs.
Read more >
Publish code coverage results v1 task
Publish Cobertura or JaCoCo code coverage results from a build. ... Fail when code coverage results are missing. Default: false.
Read more >
Build Summary
Description: Provides details about any build specified by build identifier (name + number). Security: Requires a valid user with "Read" permission.
Read more >
Changelog
Fail testing when any Python warnings are emitted. Migrate remaining unittest.TestCase style test functions to pytest style.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found