Open
Conversation
4 tasks
|
It is my understanding that this PR will enable Linux Premium plan running .NET6 on a V4 host to use Headless Chrome with PuppeteerSharp without using docker, in the same way this already works for Linux Consumption plan. Is that correct? And what's the status on the PR? Seems dead. |
Author
your understanding is correct. yes it is stale and dead |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This continues the work from PR #743 with the suggested changes. (limiting changes to node and dotnet only). below is the previous PR description
#333 identified that LibAppIndicator is deprecated in Bullseye Debian and needs to be replaced with a supported library. This library needs to be updated to support Chrome Headless.
This PR is building off of the work of @nyds https://github.com/Azure/azure-functions-docker/pull/738/files
Link to Debian Bug Discussion : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895037
PR information