Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

bug: Initial deployment fails due to unresolved dependencies #467

Closed
nickbpadilla opened this issue Apr 5, 2022 · 8 comments
Closed

bug: Initial deployment fails due to unresolved dependencies #467

nickbpadilla opened this issue Apr 5, 2022 · 8 comments
Milestone
v3.2.0

Comments

@nickbpadilla
Copy link

lambda_codebase/initial_commit fails build due to unresolved dependencies MarkupSafe 2.1.1

<html><body>
<!--StartFragment--><span><span>

Building codeuri: lambda_codebase/initial_commit runtime: python3.8 metadata: {} functions: ['InitialCommitHandler']
--


</span></span><span><span>Error: PythonPipBuilder:ResolveDependencies - {markupsafe==2.1.1(wheel)}</span></span><!--EndFragment-->
</body>
</html>
@gkudikala
Copy link

I have the same issue, Running bootstrapping pipelines gives me errors, I tried to add install wheel or marketplace doesn't solve the problem

`

Running PythonPipBuilder:ResolveDependencies

110 |  
111 | Build Failed
112 | Error: PythonPipBuilder:ResolveDependencies - {markupsafe==2.1.1(wheel)}
113 |  
114 | [Container] 2022/04/06 12:11:32 Command did not exit successfully sam build -t adf-bootstrap/deployment/global.yml exit status 1
115 | [Container] 2022/04/06 12:11:32 Phase complete: BUILD State: FAILED
116 | [Container] 2022/04/06 12:11:32 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: sam build -t adf-bootstrap/deployment/global.yml. Reason: exit status 1

`

@javydekoning
Copy link
Contributor

I think this will be solved by #457

@whuber
Copy link

whuber commented Apr 13, 2022

When can we expect any solution on this. We have the same problem with our ADF.

@whuber
Copy link

whuber commented Apr 15, 2022

I also tried to deploy a fresh ADF in a new Organisation account - same error. So the ADF seems to be currently unusable even for new installations on version 3.1.2!?

@javydekoning any idea how I can do a quickfix here? Your changes in pull request #454 are based on master branch which has not the same status as tag v3.1.2

@deltagarrett
Copy link

Until we release a new version I strongly suggest to pull the 3.1.2, update requirements.txt as describe in #439 and deploy ADF through a sam build. I have done this a couple of time in the last weeks, it works properly.

@whuber
Copy link

whuber commented Apr 15, 2022

@deltagarrett thanks for your quick reply. This works for me as well!

@deltagarrett deltagarrett pinned this issue Apr 15, 2022
@deltagarrett
Copy link

Let me pin this until we release a next version. ; ) Thanks for the feedback @whuber !

@sbkok sbkok added this to the v3.2.0 milestone Aug 26, 2022
@sbkok
Copy link
Collaborator

sbkok commented Jan 24, 2023

Thank you for your patience. I am happy to inform you that this issue has been resolved in our latest release v3.2.0 just now.
I'm hereby closing this issue. Please open a new issue if you are experiencing any issues with the latest release.

@sbkok sbkok closed this as completed Jan 24, 2023
@StewartW StewartW unpinned this issue Jan 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v3.2.0
Development

No branches or pull requests
6 participants
@deltagarrett @whuber @sbkok @javydekoning @nickbpadilla @gkudikala