nerddisco / luminave-thorium Goto Github PK

We are using webpack to bundle node modules and this is only needed, because before node 12 it was not possible to import modules using ES6.

🚨 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.

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 📦🚀

Issue description

When using the automatic-connect feature to find thorium servers in the network, luminave-thorium connects to new servers that are found, even when there is already an established connection.

Steps to reproduce

• Start luminave-thorium
• Start Thorium 1
• See that luminave-thorium connects to Thorium 1
• Start Thorium 2
• See that luminave-thorium connects to Thorium 2

Versions

1. luminave-thorium: 1.2.3

In Thorium you can have different alert levels which correspond to another HTML color that can be retrieved using the GraphQL API:

• Alert 5: #08f
• Alert 4: #0f0
• Alert 3: #ff0
• Alert 2: #f80
• Alert 1: #f00
• Alert P: rebeccapurple
• Blackout: black

It would be nice to also have these alerts in luminave so that the lights can respond to different alerts.

🚨 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.

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 📦🚀

Issue description

Whenever a sound is triggered in a simulator, the lights flicker.

Steps to reproduce

See Thorium-Sim/thorium#2417

Versions

1. luminave-thorium: 1.2.3

When the color black from Thorium (>= 1.22.0) is coming, it should create the scene color-black.

Right now it's not possible to change the IP or host of either Thorium or luminave-server from the outside without updating the code. This means that when Thorium is running production-mode, it will not work. Also we can't change the port of luminave-server.

ToDo

• Thorium: IP / port OR if the IP should be fetched automagically using bonjour
• luminave-server: IP / port
• Debug mode: Enable or disable log messages

Issue description

When the configured host is down, a EHOSTDOWN is thrown and it is not caught properly.

This also happens when luminave-server can't be reached

Steps to reproduce

• Configure HOST_THORIUM=localhost & PORT_THORIUM=1234
• Start luminave-thorium
• See that it breaks

Versions

1. luminave-thorium: 1.2.6

Issue description

The same message from Thorium is transmitted multiple times, but this is not happening all the time.

Steps to reproduce

• Start Thorium
• Start luminave-thorium
• Add the client to Thorium
• Change something in Thorium
• See that the same event is at least triggered twice, but with different data

luminave-thorium was restarted

After this messages are not duplicated anymore, so you have to

• Remove the flight from the ECS-luminave-thorium Client
• See that luminave-thorium writes No simulator selected
• Assign the flight again to the ECS-luminave-thorium Client
• Change something in Thorium
• See that every event is at least triggered twice

Versions

1. luminave-thorium: 1.2.6