Zach P
01/31/2023, 11:19 PMgithub_event = github_context.get_github_event(project_dir)
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/builder/github_context.py", line 92, in get_github_event
return GithubEvent(project_dir)
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/builder/github_context.py", line 59, in __init__
self.timestamp = float(git_metadata["timestamp"])
ValueError: could not convert string to float: ''
Error: Failed to deploy Python Executable. Try disabling fast deploys by setting `ENABLE_FAST_DEPLOYS: 'false'` in your .github/workflows/*yml.
Error: Process completed with exit code 1.
name: Serverless Branch Deployments
on:
pull_request:
types: [opened, synchronize, reopened, closed]
paths-ignore:
- 'infrastructure/**'
concurrency:
# Cancel in-progress runs on same branch
group: ${{ github.ref }}
cancel-in-progress: true
env:
DAGSTER_CLOUD_URL: ${{ secrets.DAGSTER_CLOUD_URL }}
ENABLE_FAST_DEPLOYS: "true"
jobs:
parse_workspace:
runs-on: ubuntu-latest
outputs:
build_info: ${{ steps.parse-workspace.outputs.build_info }}
secrets_set: ${{ steps.parse-workspace.outputs.secrets_set }}
steps:
- uses: actions/checkout@v3
- name: Parse cloud workspace
id: parse-workspace
uses: dagster-io/dagster-cloud-action/actions/utils/parse_workspace@v0.1
with:
dagster_cloud_file: dagster_cloud.yaml
- name: Install Poetry
run: pipx install poetry
- uses: actions/setup-python@v4
with:
python-version: '3.8'
cache: 'poetry'
- run: poetry install
- name: Run tests
run: poetry run pytest --durations=5
dagster_cloud_build_push:
runs-on: ubuntu-latest
needs: parse_workspace
name: Dagster Serverless Deploy
strategy:
fail-fast: false
matrix:
location: ${{ fromJSON(needs.parse_workspace.outputs.build_info) }}
steps:
- name: Checkout
uses: actions/checkout@v3
with:
ref: ${{ github.sha }}
- name: Build and deploy Python executable
if: env.ENABLE_FAST_DEPLOYS == 'true'
uses: dagster-io/dagster-cloud-action/actions/build_deploy_python_executable@pex-v0.1
with:
dagster_cloud_file: "$GITHUB_WORKSPACE/dagster_cloud.yaml"
build_output_dir: "$GITHUB_WORKSPACE/build"
python_version: "3.8"
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Running ['/home/runner/work/_actions/dagster-io/dagster-cloud-action/pex-v0.1/generated/gha/builder.pex', '-m', 'builder.deploy', '/home/runner/work/company-dagster/company-dagster/dagster_cloud.yaml', '/home/runner/work/company-dagster/company-dagster/build', '--python-version=3.8', '--upload-pex', '--update-code-location', '--deps-cache-from=org/company-dagster/main', '--no-build-sdists']
/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/runpy.py:127: RuntimeWarning: 'builder.deploy' found in sys.modules after import of package 'builder', but prior to execution of 'builder.deploy'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
ERROR:root:git command failed: b''
b'fatal: bad object b3faf5142242a23a953bc672f51b6d1ca2ea2cdb\n'
ERROR:root:git command failed: b''
b'fatal: bad object b3faf5142242a23a953bc672f51b6d1ca2ea2cdb\n'
ERROR:root:git command failed: b''
b'fatal: bad object b3faf5142242a23a953bc672f51b6d1ca2ea2cdb\n'
ERROR:root:git command failed: b''
b'fatal: bad object b3faf5142242a23a953bc672f51b6d1ca2ea2cdb\n'
Traceback (most recent call last):
File "/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/runpy.py", line 194, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/__main__.py", line 103, in <module>
bootstrap_pex(__entry_point__, execute=__execute__, venv_dir=__venv_dir__)
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/.bootstrap/pex/pex_bootstrapper.py", line 599, in bootstrap_pex
pex.PEX(entry_point).execute()
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/.bootstrap/pex/pex.py", line 551, in execute
sys.exit(self._wrap_coverage(self._wrap_profiling, self._execute))
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/.bootstrap/pex/pex.py", line 458, in _wrap_coverage
return runner(*args)
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/.bootstrap/pex/pex.py", line 489, in _wrap_profiling
return runner(*args)
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/.bootstrap/pex/pex.py", line 572, in _execute
return self.execute_interpreter()
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/.bootstrap/pex/pex.py", line 657, in execute_interpreter
return self.execute_module(module)
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/.bootstrap/pex/pex.py", line 783, in execute_module
runpy.run_module(module_name, run_name="__main__", alter_sys=True)
File "/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/runpy.py", line 207, in run_module
return _run_module_code(code, init_globals, run_name, mod_spec)
File "/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/runpy.py", line 97, in _run_module_code
_run_code(code, mod_globals, init_globals,
File "/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/builder/deploy.py", line 530, in <module>
cli()
File "/home/runner/.pex/installed_wheels/78086359bc4a576338dbcaacad4a42784cdd0755b6327b984812fe0913265abf/click-8.1.3-py3-none-any.whl/click/core.py", line 1130, in __call__
return self.main(*args, **kwargs)
File "/home/runner/.pex/installed_wheels/78086359bc4a576338dbcaacad4a42784cdd0755b6327b984812fe0913265abf/click-8.1.3-py3-none-any.whl/click/core.py", line 1055, in main
rv = self.invoke(ctx)
File "/home/runner/.pex/installed_wheels/78086359bc4a576338dbcaacad4a42784cdd0755b6327b984812fe0913265abf/click-8.1.3-py3-none-any.whl/click/core.py", line 1404, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/home/runner/.pex/installed_wheels/78086359bc4a576338dbcaacad4a42784cdd0755b6327b984812fe0913265abf/click-8.1.3-py3-none-any.whl/click/core.py", line 760, in invoke
return __callback(*args, **kwargs)
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/builder/deploy.py", line 313, in cli
deploy_main(
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/builder/deploy.py", line 361, in deploy_main
load_github_event(os.path.dirname(dagster_cloud_file))
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/builder/deploy.py", line 219, in load_github_event
github_event = github_context.get_github_event(project_dir)
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/builder/github_context.py", line 92, in get_github_event
return GithubEvent(project_dir)
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/builder/github_context.py", line 59, in __init__
self.timestamp = float(git_metadata["timestamp"])
ValueError: could not convert string to float: ''
Shalabh Chaturvedi
02/01/2023, 4:58 AMgit
to get the timestamp of the latest commit in the checked out directory:
ERROR:root:git command failed: b''
b'fatal: bad object b3faf5142242a23a953bc672f51b6d1ca2ea2cdb\n'
The git command that is failing is
git -C {project_dir} log -1 --format=%cd --date=unix
I'm not sure why this fails though.
I looked at your workflow definition and it looks slightly different than our quickstart repo. Specifically the actions/checkout
for the fast deploys uses a project-repo/
subdirectory in our example. I suspect we might depend on this subdirectory even though we shouldn't.
Could you please try the following:
1. Set runs-on: ubuntu-20.04
instead of ubuntu-latest
2. If that doesn't help, add path: project-repo
to your actions/checkout
that and also adjust the dagster_cloud_file to include it.
Let me know if neither of these work.Zach P
02/01/2023, 3:53 PMproject-repo
and and using this seems to have worked. It’s also possible that I was using github.sha
instead of github.head_ref
? I swapped to sha originally while using the docker deployment method since the workflow we have for PRs often leads to head_refs being moved/deleted!
However; now the pex builds start but fail. Error here:
INFO:root:Running ['/home/runner/work/_actions/dagster-io/dagster-cloud-action/pex-v0.1/generated/gha/builder.pex', '/home/runner/work/_actions/dagster-io/dagster-cloud-action/pex-v0.1/src/create_or_update_comment.py'] in '/home/runner/work/company-dagster/company-dagster/project-repo'
Error: Some locations failed to load after being synced by the agent:
Error loading my_code_location: {'__typename': 'PythonError', 'message': 'dagster._core.errors.DagsterUserCodeUnreachableError: Could not reach user code server\n', 'stack': [' File "/dagster-cloud/dagster_cloud/workspace/user_code_launcher/user_code_launcher.py", line 1166, in _reconcile\n new_dagster_servers[to_update_key] = self._start_new_dagster_server(\n', ' File "/dagster-cloud/dagster_cloud/workspace/user_code_launcher/user_code_launcher.py", line 1440, in _start_new_dagster_server\n self._create_pex_server(deployment_name, location_name, desired_entry, multipex_server)\n', ' File "/dagster-cloud/dagster_cloud/workspace/user_code_launcher/user_code_launcher.py", line 1418, in _create_pex_server\n multipex_client.create_pex_server(\n', ' File "/dagster-cloud/dagster_cloud/pex/grpc/client.py", line 37, in create_pex_server\n res = self._query(\n', ' File "/dagster-cloud/dagster_cloud/pex/grpc/client.py", line 91, in _query\n raise DagsterUserCodeUnreachableError("Could not reach user code server") from e\n']}
ERROR:root:Error updating code location 'my_code_location'
company Traceback (most recent call last):
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/builder/deploy.py", line 508, in run_code_location_update
code_location.wait_for_load(
File "/home/runner/.pex/unzipped_pexes/2e536a00a742406eeee720e381d89289fe105add/builder/code_location.py", line 38, in wait_for_load
workspace.wait_for_load(
File "/home/runner/.pex/installed_wheels/ddcba3add552a0aa584b2d01012f144f5aa648f8d1df736ef9205acc482bd9a7/dagster_cloud_cli-1.1.9-py3-none-any.whl/dagster_cloud_cli/commands/workspace/__init__.py", line 183, in wait_for_load
raise ui.error(error_string)
click.exceptions.Exit
INFO:root:Running ['/home/runner/work/_actions/dagster-io/dagster-cloud-action/pex-v0.1/generated/gha/builder.pex', '/home/runner/work/_actions/dagster-io/dagster-cloud-action/pex-v0.1/src/create_or_update_comment.py'] in '/home/runner/work/company-dagster/company-dagster/project-repo'
Shalabh Chaturvedi
02/01/2023, 5:32 PMIt’s also possible that I was usingYes it is possible - the checkout action does a shallow clone so it's possible the latest commit was not available. I suggest you leave theinstead ofgithub.sha
?github.head_ref
ubuntu-20.04
in there because the workflows are less complex for that version.
Still - this is progress - it appears the code got built and uploaded but didn't work as expected in dagster cloud. I have a few questions:
• Zach P
02/01/2023, 6:31 PMdagster._core.errors.DagsterUserCodeUnreachableError: Could not reach user code server
File "/dagster-cloud/dagster_cloud/workspace/user_code_launcher/user_code_launcher.py", line 1166, in _reconcile
new_dagster_servers[to_update_key] = self._start_new_dagster_server(
File "/dagster-cloud/dagster_cloud/workspace/user_code_launcher/user_code_launcher.py", line 1440, in _start_new_dagster_server
self._create_pex_server(deployment_name, location_name, desired_entry, multipex_server)
File "/dagster-cloud/dagster_cloud/workspace/user_code_launcher/user_code_launcher.py", line 1418, in _create_pex_server
multipex_client.create_pex_server(
File "/dagster-cloud/dagster_cloud/pex/grpc/client.py", line 37, in create_pex_server
res = self._query(
File "/dagster-cloud/dagster_cloud/pex/grpc/client.py", line 91, in _query
raise DagsterUserCodeUnreachableError("Could not reach user code server") from e
The above exception was caused by the following exception:
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with: status = StatusCode.DEADLINE_EXCEEDED details = "Deadline Exceeded" debug_error_string = "{"created":"@1675266007.505295068","description":"Deadline Exceeded","file":"src/core/ext/filters/deadline/deadline_filter.cc","file_line":81,"grpc_status":4}" >
File "/dagster-cloud/dagster_cloud/pex/grpc/client.py", line 88, in _query
response = getattr(stub, method)(request_type(**kwargs), timeout=timeout)
File "/usr/local/lib/python3.8/site-packages/grpc/_channel.py", line 946, in __call__
return _end_unary_response_blocking(state, call, False, None)
File "/usr/local/lib/python3.8/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
raise _InactiveRpcError(state)
I just re-ran the entire GHA workflow and it successfully finish :daggy-celebrate:Shalabh Chaturvedi
02/01/2023, 6:36 PMI just re-ran the entire GHA workflow and it successfully finishExcellent! I think the earlier failure was due to the AWS task spin up taking longer than expected. Once you see a successful deployment you can ignore the earlier
Could not reach user code server
error.
You could try committing a code change to see fast re-deploys in action. Let us know if you encounter other issues with the pex deploys.Zach P
02/01/2023, 6:36 PMFile "/home/runner/work/company-dagster/company-dagster/build/.pex/venvs/b18ced93454e9fc173e35b9c997a5357c6ff5a51/d28e4f77ea23cfee2f7fe16fae92e311e742545c/lib/python3.8/site-packages/pip/_vendor/packaging/markers.py", line 215, in _get_env
raise UndefinedEnvironmentName(
pip._vendor.packaging.markers.UndefinedEnvironmentName: 'python_full_version' does not exist in evaluation environment.
Failed to resolve for platform manylinux2014_x86_64-cp-38-cp38. Resolve requires evaluation of unknown environment marker: 'python_full_version' does not exist in evaluation environment.
This seems to be a known issue with pex, a quote from there documentation reads:
Constraints: when --platform
is used the environment marker`python_full_version` will not be available if PYVER
is not given as a three component dotted version since python_full_version
is meant to have 3 digits (e.g., 3.8.10
). If a python_full_version
environment marker is encountered during a resolve, an UndefinedEnvironmentName
exception will be raised. To remedy this, either specify the full version in the platform (e.g, linux_x86_64-cp-3.8.10-cp38
) or use --complete-platform
instead.
However, as seen above our requirements.txt makes heavy use of python_full_version
. Ideally, this would continue to be supported.Shalabh Chaturvedi
02/02/2023, 6:57 PM--platform
- we're extra careful with that because it may break builds. I'm also surprised this worked in your branch. Did you have a similar requirements.txt
in your branch when you deployed? (Can poetry export with just python_version
?)Zach P
02/02/2023, 7:23 PM- repo: local
hooks:
- id: strip_extra_info_from_requirements
# Needed due to a current issue in the pex command used by dagster.
name: Strip extra info from requirements.txt
entry: .strip_extra_info_from_reqs.sh
language: script
pass_filenames: false
.strip_extra_info_from_reqs.sh:
#!/bin/bash
# Get a new requirements file
poetry export --without-hashes --format=requirements.txt -o requirements.txt
# Remove windows depenencies. we dont support windows.
grep -v "Windows" requirements.txt > requirements2.txt && mv requirements2.txt requirements.txt
# Remove 'extra info'
grep -Eo '^([^;\ ]+)' requirements.txt > requirements2.txt && mv requirements2.txt requirements.txt
(EDIT: Had to add remove windows)
Still need to deploy all of this to make sure it all works, it’s probably not the best solution but will get our pipeline working againShalabh Chaturvedi
02/02/2023, 7:25 PMubuntu-20.04
in your main branch?Zach P
02/02/2023, 7:31 PMdagster._core.errors.DagsterUserCodeUnreachableError: Could not reach user code server
error that results in failing to update code locations.
Manually reloading these code locations in dagster cloud, then manually rerunning the github actions deploy fixes the issue. I’m hoping this happens less in the future, but I’ll keep an eye on it over the next few days.Shalabh Chaturvedi
02/02/2023, 9:48 PMpython_full_version
. It might be due to ubuntu-20.04
and ubuntu-22.04
(aka ubuntu-latest
) having slightly different workflows. Basically on ubuntu-20.04
pex can fallback to the local interpreter for dependency resolution since we use --resolve-local-platforms
and that might already work with the python_full_version
.Zach P
02/03/2023, 12:18 AMShalabh Chaturvedi
02/03/2023, 2:03 AMpython_full_version
and was able to reproduce the issue on ubuntu-latest
. Switching to ubuntu-20.04
fixed the issue, so I'd say it already works. If you use ubuntu-20.04
you can remove the script to strip those markers. This also explains why the branch worked.
GitHub changed their default runner from 20.04 to 22.04 sometime in December 2022. 22.04 provides a newer Python that cannot build source dependencies for our target container, so we don't use the local python interpreter to resolve dependencies. For our workflows ubuntu-20.04
works better and we have switched our default quickstarts to 20.04 now, but your workflows were probably cloned before that change.Zach P
02/03/2023, 2:33 PMubuntu-20.04
Shalabh Chaturvedi
02/03/2023, 4:56 PMZach P
02/03/2023, 5:57 PMShalabh Chaturvedi
02/03/2023, 7:21 PMZach P
02/03/2023, 7:40 PMimport datetime
from dataclasses import dataclass
from pathlib import Path
from dagster import (
MonthlyPartitionsDefinition,
PartitionedConfig,
ResourceDefinition,
make_values_resource,
)
from dagster_aws.s3 import s3_resource
from dagster_aws.s3.io_manager import s3_pickle_io_manager
from dagster_aws.secretsmanager import secretsmanager_resource
from dagster_databricks import databricks_pyspark_step_launcher
from dagster_pyspark import pyspark_resource
from pyarrow.fs import LocalFileSystem, SubTreeFileSystem
from common.io_managers import parquet_pyarrow_iomanager
from common.io_managers.delta_spark import branching_delta_io_manager
from common.resources import ssh_resource_from_secretsmanager # type: ignore[attr-defined]
from common.utils.aws import SSMParameterBuilder
monthly_partition = MonthlyPartitionsDefinition("202208", fmt="%Y%m", end_offset=1, day_offset=8)
region = "us-east-1"
@dataclass
class DDBParameters(SSMParameterBuilder["DDBParameters"]):
KEYPAIR_NAME: str
PROD_BUCKET: str
PROD_DB_NAME: str
STAGING_BUCKET: str
STAGING_DB_NAME: str
TEMP_BUCKET: str
ssm_param_path = "/DATAENG/PROJECT_NAME"
parameters = DDBParameters.from_ssm_parameters(ssm_param_path, region)
If it would help I’d be willing to screen share some of this with you or give more specific code snippets.
We aren’t super in love with the current set up of our pipelines, but they were mainly done by me when I was very new to the project 😅Shalabh Chaturvedi
02/07/2023, 6:40 PMZach P
02/07/2023, 7:27 PMrepositories
to Definitions
, it seems to be like it’s “best practice” to use code locations for this sort of logical separation (as AFAIK and as the docs suggest you can only have one definitions
per code location). Long term, will dagster serverless & pex deployments be able to keep up with this change? Is this a serverless specific issue, and would it possibly be resolved by moving to a hybrid deployment?
We expect to 4x our number of engineers and data assets/code locations over the next year or so and need to know how we should plan some of our workflows so that they are effective and scalable.daniel
02/07/2023, 8:57 PMZach P
02/07/2023, 9:09 PMdagster._core.errors.DagsterUserCodeUnreachableError: Could not reach user code server
File "/dagster-cloud/dagster_cloud/workspace/user_code_launcher/user_code_launcher.py", line 1167, in _reconcile
new_dagster_servers[to_update_key] = self._start_new_dagster_server(
File "/dagster-cloud/dagster_cloud/workspace/user_code_launcher/user_code_launcher.py", line 1441, in _start_new_dagster_server
self._create_pex_server(deployment_name, location_name, desired_entry, multipex_server)
File "/dagster-cloud/dagster_cloud/workspace/user_code_launcher/user_code_launcher.py", line 1419, in _create_pex_server
multipex_client.create_pex_server(
File "/dagster-cloud/dagster_cloud/pex/grpc/client.py", line 37, in create_pex_server
res = self._query(
File "/dagster-cloud/dagster_cloud/pex/grpc/client.py", line 91, in _query
raise DagsterUserCodeUnreachableError("Could not reach user code server") from e
The above exception was caused by the following exception:
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with: status = StatusCode.DEADLINE_EXCEEDED details = "Deadline Exceeded" debug_error_string = "{"created":"@1675802607.414275462","description":"Deadline Exceeded","file":"src/core/ext/filters/deadline/deadline_filter.cc","file_line":81,"grpc_status":4}" >
File "/dagster-cloud/dagster_cloud/pex/grpc/client.py", line 88, in _query
response = getattr(stub, method)(request_type(**kwargs), timeout=timeout)
File "/usr/local/lib/python3.8/site-packages/grpc/_channel.py", line 946, in __call__
return _end_unary_response_blocking(state, call, False, None)
File "/usr/local/lib/python3.8/site-packages/grpc/_channel.py", line 849, in _end_unary_response_blocking
raise _InactiveRpcError(state)
Clicking “Reload” on the error message triggers an update of the code location, and this usually works (Once it failed when I clicked update on all of them).
Since changing to the workflow queue (IE: Only 4 code locations should ever be updated at a time now), the issue remains.
This issue only appears with ENABLE_FAST_DEPLOYS=true
, for the past few months we’ve been using the docker deploy with serverless without issue, but originally changed to PEX with the hope that it would reduce our github minutes usage 🙂.daniel
02/07/2023, 11:36 PMZach P
02/23/2023, 2:31 PMno module named github
in the pex builder.daniel
02/23/2023, 2:35 PMZach P
02/23/2023, 2:36 PMERROR:root:Could not update PR comment: b''
b'Traceback (most recent call last):\n File "/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/runpy.py", line 194, in _run_module_as_main\n return _run_code(code, main_globals, None,\n File "/opt/hostedtoolcache/Python/3.8.16/x64/lib/python3.8/runpy.py", line 87, in _run_code\n exec(code, run_globals)\n File "/home/runner/.pex/unzipped_pexes/6ec7c7737a35d90dd0d16f9fa346443030502884/__main__.py", line 103, in <module>\n bootstrap_pex(__entry_point__, execute=__execute__, venv_dir=__venv_dir__)\n File "/home/runner/.pex/unzipped_pexes/6ec7c7737a35d90dd0d16f9fa346443030502884/.bootstrap/pex/pex_bootstrapper.py", line 608, in bootstrap_pex\n pex.PEX(entry_point).execute()\n File "/home/runner/.pex/unzipped_pexes/6ec7c7737a35d90dd0d16f9fa346443030502884/.bootstrap/pex/pex.py", line 560, in execute\n sys.exit(self._wrap_coverage(self._wrap_profiling, self._execute))\n File "/home/runner/.pex/unzipped_pexes/6ec7c7737a35d90dd0d16f9fa346443030502884/.bootstrap/pex/pex.py", line 467, in _wrap_coverage\n return runner(*args)\n File "/home/runner/.pex/unzipped_pexes/6ec7c7737a35d90dd0d16f9fa346443030502884/.bootstrap/pex/pex.py", line 498, in _wrap_profiling\n return runner(*args)\n File "/home/runner/.pex/unzipped_pexes/6ec7c7737a35d90dd0d16f9fa346443030502884/.bootstrap/pex/pex.py", line 581, in _execute\n return self.execute_interpreter()\n File "/home/runner/.pex/unzipped_pexes/6ec7c7737a35d90dd0d16f9fa346443030502884/.bootstrap/pex/pex.py", line 681, in execute_interpreter\n return self.execute_content(arg, content)\n File "/home/runner/.pex/unzipped_pexes/6ec7c7737a35d90dd0d16f9fa346443030502884/.bootstrap/pex/pex.py", line 774, in execute_content\n return cls.execute_ast(name, program, argv0=argv0)\n File "/home/runner/.pex/unzipped_pexes/6ec7c7737a35d90dd0d16f9fa346443030502884/.bootstrap/pex/pex.py", line 792, in execute_ast\n exec_function(program, globals_map)\n File "/home/runner/.pex/installed_wheels/da7b3711d724baa7fbaf88a524c5a0e90bee8fa0db1bc973a649a1905a457ef9/pex-2.1.122-py2.py3-none-any.whl/pex/compatibility.py", line 109, in exec_function\n exec (ast, globals_map, locals_map)\n File "/home/runner/work/_actions/dagster-io/dagster-cloud-action/pex-v0.1/src/create_or_update_comment.py", line 2, in <module>\n from github import Github\nModuleNotFoundError: No module named \'github\'\n'
Shalabh Chaturvedi
02/23/2023, 4:12 PMZach P
02/23/2023, 4:14 PMFailed to deploy Python Executable. Try disabling fast deploys by setting `ENABLE_FAST_DEPLOYS: 'false'` in your .github/workflows/*yml.
That being said, it does seem to be deploying to the branch correctlyShalabh Chaturvedi
02/23/2023, 4:18 PMZach P
02/23/2023, 9:26 PM