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.
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
0.2.19 -> 0.2.20 breaks serverless offline start #127
Comments
That looks like the |
According to the plugin requirements you need a JRE (I assume accessible through your path settings in the environment). |
Not at my machine but any chance that a java related requirement could be different from 0.2.19? Latter works just fine.
… On 23 Aug 2017, at 12:44, Frank Schmid ***@***.***> wrote:
According to the plugin requirements you need a JRE (I assume accessible through your path settings in the environment).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Try running |
Randomly I get this this error. Uninstalling dynamodb and reinstalling it solves the problem. I would really like to know what the root of the problem is. |
@HyperBrain a co-worker had this same error today on his Mac, then he patch upgraded Java and that went away. He got the whole webpack->db->sls instance to start, tables seeded fine, but whenever he made a post to an endpoint it would just hang. Mine is working fine, btw. Same package-lock.json, same node-modules versions. You ever find a solution? |
@btburton42 I only commented here as maintainer of |
@btburton42 Try uninstalling some npm package and reinstalling something. Let me know if the error comes back. |
@TooSick coworker tried rm'ing and reinstalling but no luck. he is using nvm, think that might do it? |
@btburton42 do |
@TooSick thanks! will do on monday and let you know. |
@TooSick that didn't work for my colleague. I'll let him chime in when he has a moment of free time. |
Hi everyone @btburton42 @TooSick @HyperBrain , did you manage to solve the issue?
However, it works when I run it from my host pc. I tried many combination of installing/uninstalling npm packages and dynamodb local within the docker container. Many thanks in advance |
@danielesalvatore |
@TooSick thank you very much for your reply. In my case the error was generated because the Docker container used didn't have Java on it. Thank you for your support |
@danielesalvatore Step 1: install Java 🥇 |
Looks like the bin folder in Not sure why it's getting deleted, but reinstalling does temporarily fix it. I guess it's a matter of figuring out if this repo is causing the issue or if https://github.com/99xt/dynamodb-localhost is. |
This happens for me every time I add/remove new dependencies (using |
For me, when I reorganized my package, this error would not go away despite running |
For those who are stuck with this issue, the following solution worked for me npm uninstall serverless-dynamodb-local
sls dynamodb uninstall
npm install serverless-dynamodb-local@0.2.30
sls dynamodb install |
@sohailalam2 's workaround works. seemed to be broken somewhere between 0.2.36 & 0.2.31 |
Any updates on if this is fixed in the latest release? |
@salmankhann still happening. I had to lock "resolutions": {
"dynamodb-localhost": "0.0.5"
} |
Upgrading from 0.2.19 to 0.2.20 and any later release breaks the command
serverless offline start
serverless offline
still works.I'm using serverless-webpack
and versions are:
sls-offline: 3.15.3
serverless-webpack: 2.2.2 and I've tried other versions with same result.
serverless: 1.20.2
I don't see the release tags in this repo unfortunately. Also, the error is a bit unspecific:
The text was updated successfully, but these errors were encountered: