V1 libray worker

Author: hallvictoria

.artifactignore

@@ -49,4 +49,4 @@ omit =
     # Removing the imported libraries that might show up in this.
     */azure/functions/*
     */azure/*
-    */azure_functions_worker/_thirdparty/*
+    */azure_functions_worker_v1/_thirdparty/*

.ci/e2e_integration_test/start-e2e.ps1

@@ -6,10 +6,9 @@
 ignore = W503,E402,E731
 
 exclude = .git, __pycache__, build, dist, .eggs, .github, .local, docs/,
-          Samples, azure_functions_worker/protos/,
-          azure_functions_worker/_thirdparty/typing_inspect.py,
-          tests/unittests/test_typing_inspect.py,
-          tests/unittests/broken_functions/syntax_error/main.py,
+          Samples, azure_functions_worker_v1/protos/,
+          azure_functions_worker_v1/utils/typing_inspect.py,
+          tests/protos/,
           .env*, .vscode, venv*, *.venv*
 
 max-line-length = 88

.coveragerc

@@ -0,0 +1,78 @@
+# Contributing to Azure Functions Python Worker
+First, thank you for contributing to Azure Functions Python Worker repository!
+
+## Basics
+If you would like to become an active contributor to this project, please follow the instructions provided in [Microsoft Azure Projects Contribution Guidelines](http://azure.github.io/guidelines/).
+
+## Table of Contents
+[Before starting](#before-starting)
+- [GitHub basics](#github-basics)
+- [Code of Conduct](#code-of-conduct)
+
+[Making Changes](#making-changes)
+- [Pull Requests](#pull-requests)
+- [Pull Request Guidelines](#pull-request-guidelines)
+    - [Cleaning up commits](#cleaning-up-commits)
+    - [General guidelines](#general-guidelines)
+    - [Testing guidelines](#testing-guidelines)
+
+## Before starting
+
+### GitHub basics
+
+#### GitHub workflow
+
+If you don't have experience with Git and GitHub, some of the terminology and process can be confusing. [Here's a guide to understanding GitHub](https://guides.github.com/introduction/flow/).
+
+#### Forking the Azure/Azure-Functions-Python-Worker repository
+
+If you don't have contributor [`Azure/Azure-Functions-Python-Worker`](https://github.com/Azure/azure-functions-python-worker/) repository, we ask that you fork the repository and submit your Pull Request from there. We block PRs from forks to go through E2E tests, however, we will cherry-picked PRs once they pass unit tests to validate the E2E tests. [Here's a guide to forks in GitHub](https://guides.github.com/activities/forking/).
+
+### Code of Conduct
+
+This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.
+
+## Making Changes
+
+### Pull Requests
+
+You can find all of the pull requests that have been opened in the [Pull Request](https://github.com/Azure/azure-functions-python-worker/pulls) section of the repository.
+
+To open your own pull request, click [here](https://github.com/Azure/azure-functions-python-worker/compare). When creating a pull request, keep the following in mind:
+- Make sure you are pointing to the fork and branch that your changes were made in (if working from a different fork).
+- Choose the correct branch you want your pull request to be merged into.
+- The pull request template that is provided **should be filled out**; this is not something that should just be deleted or ignored when the pull request is created
+    - Deleting or ignoring this template will elongate the time it takes for your pull request to be reviewed
+<!-- - The SLA for reviewing pull requests is **three business days** -->
+
+### Pull Request Guidelines
+
+A pull request template will automatically be included as a part of your PR. Please fill out the checklist as specified. Pull requests **will not be reviewed** unless they include a properly completed checklist.
+
+#### Cleaning up Commits
+
+If you are thinking about making a large change, **break up the change into small, logical, testable chunks, and organize your pull requests accordingly**.
+
+Often when a pull request is created with a large number of files changed and/or a large number of lines of code added and/or removed, GitHub will have a difficult time opening up the changes on their site. This forces the Azure Azure-Functions-Python-Worker team to use separate software to do a code review on the pull request.
+
+If you find yourself creating a pull request and are unable to see all the changes on GitHub, we recommend **splitting the pull request into multiple pull requests that are able to be reviewed on GitHub**.
+
+If splitting up the pull request is not an option, we recommend **creating individual commits for different parts of the pull request, which can be reviewed individually on GitHub**.
+
+For more information on cleaning up the commits in a pull request, such as how to rebase, squash, and cherry-pick, click [here](https://github.com/Azure/azure-powershell/blob/dev/documentation/cleaning-up-commits.md).
+
+#### General guidelines
+
+The following guidelines must be followed in **EVERY** pull request that is opened.
+
+- Title of the pull request is clear and informative
+- There are a small number of commits that each have an informative message
+- A description of the changes the pull request makes is included, and a reference to the issue being resolved, if the change address any
+- All files have the Microsoft copyright header
+
+#### Testing Guidelines
+
+The following guidelines must be followed in **EVERY** pull request that is opened.
+
+- Pull request includes test coverage for the included changes
+- Changes would not be merged until all the CI scenarios pass.

.devcontainer/Dockerfile

@@ -0,0 +1,69 @@
+title: "[Survey] "
+labels: ["Survey"]
+body:
+  - type: checkboxes
+    attributes:
+      label: What stack do you primarily use?
+      options:
+        - label: Python
+        - label: Node
+        - label: PowerShell
+        - label: .NET
+        - label: Java
+        - label: Go
+        - label: Other (Please specify below)
+  - type: textarea
+    id: role
+    attributes:
+      label: What is your current role in which you use Azure Functions?
+      description: Software Developer, Machine Learning Engineer, Full Stack Engineer, etc.
+      render: bash
+    validations:
+      required: false
+  - type: textarea
+    id: scenarios
+    attributes:
+      label: What are the use cases and scenarios in which you use Azure Functions today?
+      description: Describe how you are using Azure Functions, and expected end goals. 
+      render: bash
+    validations:
+      required: false
+  - type: textarea
+    id: pain-points
+    attributes:
+      label: What are the pain points you have experienced using Azure Functions?
+      render: bash
+    validations:
+      required: false
+  - type: textarea
+    id: improvements
+    attributes:
+      label: Please share any suggestions for product improvements.
+      render: bash
+    validations:
+      required: false
+  - type: textarea
+    id: tooling
+    attributes:
+      label: What developer tools do you use? 
+      description: Visual Studio Code, Command Line, etc.
+      render: bash
+    validations:
+      required: false
+  - type: checkboxes
+    attributes:
+      label: Would you be interested in meeting with the Azure Functions team to provide additional feedback?
+      options:
+        - label: "Yes"
+        - label: "No"
+  - type: textarea
+    id: comments
+    attributes:
+      label: Please provide any other comments or feedback here, as well as your email if you indicated 'Yes' to being contacted from the Azure Functions team.
+      render: bash
+    validations:
+      required: false
+  - type: markdown
+    attributes:
+      value: |
+        "Thank you for your feedback! For any specific questions or to report a bug, please create an issue [here](https://github.com/Azure/azure-functions-python-worker/issues)."