verkehrsministerium / kraftfahrstrasse Goto Github PK

At the moment, connection errors are dropped, this should be changed to give a reasonable error message.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.

The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.

If you are using Two-Factor Authentication, make configure the auth-only level is supported. semantic-release cannot publish with the default auth-and-writes level.

Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Decide whether to ship ES6 or ESnext typescript target.

ES6:

• Widely supported

• Ugly ts hacks generated
• Bundle size is larger than for esnext

ESNext:

• Readable source code

• Not yet fully supported

We need to export some more basic types to generate well-typed functions.
Example: InvocationDetails

This causes the MSGPack Serializer to import msgpack5 in the wrong way.

Allow to specify tls certificates for nodejs websocket transports

Define all classes resources which should be public, add a convenient central import point for all those resources.

Maybe utilize TSDoc or similar projects

We should provide example code for basic and advanced usages:

• Connect
• Different serializers
• TLS Client Auth
• Call
• Cancel Calls
• Retrieve progressive results
• Register
• Unregister
• Get notified when the router revokes a registration
• Return progressive results
• Get notified when a call is canceled
• Subscribe
• Get notified when a subscription is revoked
• Publish
• Disconnect from the router

In src/generic/Callee.ts at onMessage(), it seems, there is something wrong. this.regs.Handle gets called twice. Maybe this needs a clarifing comment or a fix.

onPublished does not resolve, if acknowlegde is not requested.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

During the build process of my application that utilizes the kraftfahrstrasse library, I encountered a warning with the following message: "Cannot call a namespace ('msgpackFactory')". Although the build completes successfully and the app functions as expected, this warning still appears in the build output.

Steps to reproduce the issue:

1. Create a new project using Vite and add the kraftfahrstrasse library as a dependency.
2. Configure the application to use the kraftfahrstrasse library with the JSONSerializer instead of msgpack.
3. Run npm install to install the required dependencies.
4. Run npm run build to start the Vite build process.

Expected behavior

The build process should complete without any warnings related to the msgpackFactory.

Actual behavior

The build process completes successfully, but the following warning message appears in the build output:

Cannot call a namespace ("msgpackFactory")

Environment

Operating System: macOS 13.2.1
Node.js version: v16.17.0
Vite version: v4.0.4
kraftfahrstrasse version: v0.9.0

Additional context

I am not using msgpack in my application, as I have opted to use the JSONSerializer provided by the kraftfahrstrasse library. The warning appears to be related to the msgpackFactory, but it does not seem to affect the functionality of my application.

Please let me know if you need any further information or if there's a known workaround to suppress this warning. Thank you for your attention to this matter.

Something like:

return result(obj1);
// equivalent to
return {
  args: [obj1],
  kwArgs: {},
};

Right now, we define typings for every action, e.g. Publish, Register, Subscribe and Call.

It would be a great possibility to use those typings to validate the messages, because right now, we just assume, that the message, which gets delivered to the application code, is correctly typed. This destroys almost every other typing afterwards, which uses data from a kraftfahrstrasse action.