-
Notifications
You must be signed in to change notification settings - Fork 21
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
wrong path for pbjs and pbts in our sample app #402
Comments
Hi @octonato , I heard that you made a change recently? Will releasing your change to |
I have the same problem when kickstarting a project using: |
So I used your solution 1 but also had to add it to |
Hi @pvlugter , Do you have any suggestion how to fix this problem? |
It's awkward that grpc-js changed its dependencies in a patch version. Otherwise it would be fine. The SDK dependencies for grpc-js and proto-loader were already changed to pinned versions in #401. So I think it should just require a release of the SDK with that change. |
Released version 1.0.1, which should work now. |
Quickstart downloads may be cached for a while, so check that it's the latest with SDK 1.0.1. |
I have updated to 1.0.1 and when I do
|
FYI |
Ok, so that's the docker build. We'll need to look at the build for the linux codegen binary. We must have a mismatch between the machine image used in CI for building this, and the base docker image. |
Is there any timeline for this? Tnx |
I update the PR #403 to fix this problem. I feel that we need to set the new path for pbts and pbjs. anyone want to review it |
@katsutoxin, the dependency issue should be fixed.
I'll look at aligning these builds and publish another release today. |
@aklikic released 1.0.2 with a newly built codegen binary for linux, for the docker build. Works for me now. |
Customer reported that they got some error when following the quick start guide
Here are steps to reproduce the problem....
We will see the following errors
There are two possible solutions:
solution 1:
Add
protobufjs@6.11.3
as devDependencies in in https://github.com/lightbend/kalix-javascript-sdk/blob/main/samples/js/js-customer-registry-quickstart/package.jsonsolution 2:
Modify the
pbjs
path in kalix-script.js to./node_modules/@grpc/proto-loader/node_modules/.bin/pbjs
, and the similar topbts
https://github.com/lightbend/kalix-javascript-sdk/blob/main/npm-js/kalix-scripts/bin/kalix-scripts.js#L103-L115
One thing I feel confused is that, in https://github.com/lightbend/kalix-javascript-sdk/blob/main/samples/js/js-customer-registry-quickstart/package.json It uses
kalix-script
in build. However, in https://github.com/lightbend/kalix-javascript-sdk/blob/main/samples/js/js-customer-registry/package.json , it usescompile-descriptor
for build instead ofkalix-script
, why are they different???@jroper and @octonato , I know you are working on this area recently , especially the issue #398 Any comment on this issue?
The text was updated successfully, but these errors were encountered: