Failing to link requirements.txt with poetry

[revmischa]

❯ sls deploy
Serverless: Generating requirements.txt from pyproject.toml...

  Error --------------------------------------------------

  Error: ENOENT: no such file or directory, link '/Users/cyber/dev/jb/me/myapp/backend/requirements.txt' -> '/Users/cyber/dev/jb/me/myapp/backend/.serverless/requirements.txt'
      at Object.linkSync (fs.js:934:3)
      at tryRenameSync (/Users/cyber/dev/jb/me/myapp/backend/node_modules/serverless-python-requirements/node_modules/fs-extra/lib/move-sync/index.js:40:12)
      at Object.moveSync (/Users/cyber/dev/jb/me/myapp/backend/node_modules/serverless-python-requirements/node_modules/fs-extra/lib/move-sync/index.js:22:3)
      at ServerlessPythonRequirements.pyprojectTomlToRequirements (/Users/cyber/dev/jb/me/myapp/backend/node_modules/serverless-python-requirements/lib/poetry.js:55:7)
      at ServerlessPythonRequirements.tryCatcher (/Users/cyber/dev/jb/me/myapp/backend/node_modules/bluebird/js/release/util.js:16:23)
      at Promise._settlePromiseFromHandler (/Users/cyber/dev/jb/me/myapp/backend/node_modules/bluebird/js/release/promise.js:547:31)
      at Promise._settlePromise (/Users/cyber/dev/jb/me/myapp/backend/node_modules/bluebird/js/release/promise.js:604:18)
      at Promise._settlePromise0 (/Users/cyber/dev/jb/me/myapp/backend/node_modules/bluebird/js/release/promise.js:649:10)
      at Promise._settlePromises (/Users/cyber/dev/jb/me/myapp/backend/node_modules/bluebird/js/release/promise.js:729:18)
      at _drainQueueStep (/Users/cyber/dev/jb/me/myapp/backend/node_modules/bluebird/js/release/async.js:93:12)
      at _drainQueue (/Users/cyber/dev/jb/me/myapp/backend/node_modules/bluebird/js/release/async.js:86:9)
      at Async._drainQueues (/Users/cyber/dev/jb/me/myapp/backend/node_modules/bluebird/js/release/async.js:102:5)
      at Immediate.Async.drainQueues [as _onImmediate] (/Users/cyber/dev/jb/me/myapp/backend/node_modules/bluebird/js/release/async.js:15:14)
      at runCallback (timers.js:705:18)
      at tryOnImmediate (timers.js:676:5)
      at processImmediate (timers.js:658:5)
      at process.topLevelDomainCallback (domain.js:120:23)

     For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

  Get Support --------------------------------------------
     Docs:          docs.serverless.com
     Bugs:          github.com/serverless/serverless/issues
     Issues:        forum.serverless.com

  Your Environment Information ---------------------------
     Operating System:          darwin
     Node Version:              10.14.2
     Framework Version:         1.62.0
     Plugin Version:            3.3.0
     SDK Version:               2.3.0
     Components Core Version:   1.1.2
     Components CLI Version:    1.4.0


myapp/backend on  snmpv1 [?] via 🐍 v3.7.6 (myapp-yO1yHtsL-py3.7) on ☁️  eu-west-1 took 5s
❯ poetry export --without-hashes -f requirements.txt -o requirements.txt

myapp/backend on  snmpv1 [?] via 🐍 v3.7.6 (myapp-yO1yHtsL-py3.7) on ☁️  eu-west-1 took 2s
❯ sls deploy
Serverless: Generating requirements.txt from pyproject.toml...
Serverless: Parsed requirements.txt from pyproject.toml in /Users/cyber/dev/jb/me/myapp/backend/.serverless/requirements.txt...

version 5.0.1

[amazipangu]

me too. I have same problem.

[dhosterman]

I think the fix for this has been merged in as part of: #446

I'm not sure when this will be made part of a release, but I'm hoping soon as I'm stuck with the same issue and am unable to use serverless-python-requirements without workarounds at this time.

[bsamuel-ui]

I'm hoping to get a build out shortly. 🤞 Closing this as the fix is merged.

[rapkyt]

I still have this error:

Plugin version 5.0.1
Poetry version 1.0.3

$ serverless deploy
Serverless: Generating requirements.txt from pyproject.toml...
 
  Error --------------------------------------------------
 
  Error: ENOENT: no such file or directory, link '/.......

I have to do a poetry export manually before deploying in order to fix this issue.

[revmischa]

Appears to be fixed for me

[dhosterman]

@rapkyt , try the 5.10 version.

[rapkyt]

Version 5.1.0 fix the issue, thanks!