Selection and with selection; action(s)

We want to make the visualization of graph data useful for a data analyst.
They may come for the beauty, but making things useful will help them stay.
I imagine, as they explore the galaxies of their data, they'll spot something interesting or curious, and want to ask further questions to the data. For this, they'll want to be able to select one or many nodes (and/or links) and do stuff with them: Drill into the information associated with the selection, of course, but much more.
Here are a few considerations to think of.
With selection; actions
It's important that the selection and action concerns be as separated as possible.
Here's a list of possibilities, off the top of my head (but we should extend this list):

view information (may be different whether the selection has a single, a few, or many items)
produce some selection specification data (node ids, links -- whatever can allow a user to then recreate the selection within the same context) that can subsequently be;

downloaded
saved
copied

add information (tag, label, comment, etc.)
apply some analysis function to it (could be a function that produces the data of the subgraph, which can also be used to re-render)

How is a selection made?
Let's emulate whatever are the most common means of selection, such as (off the top of my head -- this is not verified to be the most common):

click
Ctrl+click to add an additional item to the selection
click and drag to make a rectangular selection (i.e. all items within the rectangle). Problem with click and drag is that it is already used for controlling position/perspective, so we may need to add a keypress for selection (or the current use of click+drag)
Shift+click to add an additional rectangular selections to the on going selection

The above is relevant to keyboard+mouse "manual" selection.
There's also "logical selectors": Some criteria, or formula, that can be applied to the dataset (or view, or selection) to determine what items should be selected.
What is being selected?
We'll need to figure out rules on how the relationship between node and link selection works. Are we selecting nodes through links or links through nodes. And in the latter case, when a node is selected, are all the links it's involved in selected to? Only the outgoing links? Only the incoming links? Neither? The user should probably be able to chose (again, the right choice might depend on the context).

This is its best future


Avoid to upload unused XML files to storage

For #45

@0crat refuse

@0crat refuse (here)

@g4s8 Job gh:artipie/rpm-adapter#46 is not assigned, can't get performer

Job gh:artipie/rpm-adapter#46 doesn't exist in WBS, can't create order

Job gh:artipie/rpm-adapter#46 is not assigned, can't get performer


Not able to run YOLO

I am unable to get the boundary boxes during the live image streaming

Please provide some more information: which node are you running, have you chosen the correct weight and model in the settings (in case you are using the GUI) or launch file and which topic are you displaying as your image? Additionally you should provide the output of the terminal to look at errors.

Hi Jonas,
There was glitch in the gui so i installed the autoware.ai through docker.
My issue is while connecting my camera.I have a point grey Blackfly camera FLIR Camera.When I try launch it from the runtime manager i get a error.i have attached the screenshot

Unfortunately, I am not familiar with the docker installation. As the error suggest there seems to be an issue with the spinnaker driver not being installed or not being found. I would suggest that you try to run the autoware_pointgrey_drivers from terminal  in the docker to verify if it doesnt work at all. ( roslaunch autoware_pointgrey_drivers spinnaker.launch). Alternatively you should probably ask this question again on answers.ros.org/ with autoware.ai tag as there may be more support available.

Hello Jonas,
Thank you for the response


fix: Keep profile form save button enabled

The type of this PR is: Bugfix

This PR resolves CX-2376
Description
Keep profile form save button enabled whenever the user edits an input.
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against 2430b7ca0c295497ad84adbfc27b437eb91f1aa6

#squashongreen


HAPO FHIR + Spring Boot 3.2x Native Image Compilation

When trying to compile latest HAPI FHIR 7.0.2 to a Native Image,
the AOT Processor will bail out immediately:
--- cut ---
Exception in thread "main" org.springframework.boot.context.properties.bind.MissingParametersCompilerArgumentException: Constructor binding in a native image requires compilation with -parameters but the following classes were compiled without it:
ca.uhn.fhir.rest.server.method.BaseMethodBinding
at org.springframework.boot.context.properties.bind.BindableRuntimeHintsRegistrar.registerHints(BindableRuntimeHintsRegistrar.java:100)
--- cut ---
Though I have 2 years experience with Native Image, I've never seen an exception like this before.
Then again it's pretty explicit.
The -parameters could be configured with the maven or gradle compiler plugin.
For maven compiler plugin it might me something in the veins of:

-parameters

---
Any chance to compile with this with the new version ?

I don't actually use native image, so I have no real way of testing this... Would you be able to try adding the -parameters argument to the compiler args section of the pom here and then testing against a locally built version of HAPI with that change?
If this works, please feel free to file a PR.

@jamesagnew
Thanks for your reply.
I could eventually investigate that and Create a PR


bug: price inversion fails on call to toReversed

During review of #125, I observed a logged error relating to use of the toReversed() function:
Failed to generate cache key for https://testnet.plinfra.net/penumbra.core.component.dex.v1.QueryService/CandlestickData
Failed to generate cache key for https://testnet.plinfra.net/penumbra.core.component.dex.v1.QueryService/CandlestickData
 ⨯ TypeError: s.toReversed is not a function
    at em (/app/.next/server/app/api/book/route.js:1:26002)
    at eA (/app/.next/server/app/api/book/route.js:1:27380)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:36932
    at async eC.execute (/app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:27548)
    at async eC.handle (/app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:38186)
    at async doRender (/app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/base-server.js:1359:42)
    at async cacheEntry.responseCache.get.routeKind (/app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/base-server.js:1581:28)
    at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/base-server.js:1489:28)
    at async NextNodeServer.renderPageComponent (/app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/base-server.js:1913:24)

The relevant code is here: https://github.com/penumbra-zone/dex-explorer/blob/2f3633d19b7ea2218e475ed36c95ac520246b169/src/shared/api/server/book/helpers.ts#L121-L131 and blame reports last changed in 22b313e0f0fb410b974942bc8e0c7bd09cc70c19. Not sure whether those two calls to toReversed are both necessary; perhaps the problem will go away once we straighten out the db, cf. #126.

This error is still occurring on the testnet deployment, as of today.

Still happening. When I load this route: https://dex-explorer.testnet.plinfra.net/api/book?baseAsset=UM&quoteAsset=GN I see the following error:
 ⨯ TypeError: a.toReversed is not a function
    at sT (/app/.next/server/app/api/book/route.js:1:194778)
    at fb (/app/.next/server/app/api/book/route.js:1:494089)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:36932
    at async eC.execute (/app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:27548)
    at async eC.handle (/app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/compiled/next-server/app-route.runtime.prod.js:6:38186)
    at async doRender (/app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/base-server.js:1359:42)
    at async cacheEntry.responseCache.get.routeKind (/app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/base-server.js:1581:28)
    at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/base-server.js:1489:28)
    at async NextNodeServer.renderPageComponent (/app/node_modules/.pnpm/next@14.2.9_@babel+core@7.25.2_react-dom@18.3.1_react@18.3.1__react@18.3.1/node_modules/next/dist/server/base-server.js:1913:24)
-- [2024-11-19T16:23:30.254Z] 0.967 GET /api/book?baseAsset=UM&quoteAsset=GN

It looks like there is an unexpected type causes a runtime error 🤔 . It's strange that this only occurs in the live deployment and not locally. My guess is that the request to the SimulationService may be failing (?). This is quite tough to tell. Is the next best option to debug adding a ton of console logs and re-deploying?

Confirmed fixed after merge/deploy of #138:


Update loop between latest and specified tags when muiltiple tags for the same image are defined

Describe the bug
When multiple tags for the same image are defined with the digest strategy there's an update loop between the specified tags and latest while the digest remains the same.
To Reproduce
argocd-image-updater.argoproj.io/image-list: track=[...]/track:develop,track-chromium=[...]/track:develop-chromium
argocd-image-updater.argoproj.io/track.update-strategy: digest
argocd-image-updater.argoproj.io/track-chromium.update-strategy: digest

Diff:
[...]/track:develop-chromium@sha256:96a6edfcf1d1b5102893da3300ce01f6510e6f88cecc4d72201f6bc138cb0ebb -> [...]/track:latest@sha256:96a6edfcf1d1b5102893da3300ce01f6510e6f88cecc4d72201f6bc138cb0ebb

[...]/track:latest@sha256:7f2b1668c172e08fb5170ad593530f7d79a7c2d229d968315937577d36f638a8 -> [..]/track:develop@sha256:7f2b1668c172e08fb5170ad593530f7d79a7c2d229d968315937577d36f638a8

If I were to apply this diff then a few minutes later they'd be reversed, moving from latest to develop-chromium and develop to latest respectively.
Expected behavior
The specified tags are retained and a difference is picked up only when the digest behind the tags change.
Additional context
The feature works as expected with only one image/tag defined.
Version
ArgoCD: 2.3.3
Image updater: 0.12.0
Logs
level=info msg="Starting image update cycle, considering 23 annotated application(s) for update"
level=info msg="Setting new image to [...]/track@sha256:7f2b1668c172e08fb5170ad593530f7d79a7c2d229d968315937577d36f638a8" alias=track application=track-bv-dev image_name=track image_tag="sha256:96a6edfcf1d1b5102893da3300ce01f6510e6f88cecc4d72201f6bc138cb0ebb" registry=[...]
level=info msg="Successfully updated image [...]/track@sha256:96a6edfcf1d1b5102893da3300ce01f6510e6f88cecc4d72201f6bc138cb0ebb to [...]/track@sha256:7f2b1668c172e08fb5170ad593530f7d79a7c2d229d968315937577d36f638a8' but pending spec update (dry run=false)" alias=track application=track-bv-dev image_name=track image_tag="sha256:96a6edfcf1d1b5102893da3300ce01f6510e6f88cecc4d72201f6bc138cb0ebb" registry=[...]

Based on the logs and the outcome my suspicion is that using the same image with different tags is the source of the issue?

I have a similar problem but with different images and same tag:
argocd-image-updater.argoproj.io/image-list: alias1=registry1/image1:dev, alias2=registry2/image2:dev
argocd-image-updater.argoproj.io/alias1.update-strategy: digest
argocd-image-updater.argoproj.io/alias2.update-strategy: digest

If a new image1 with dev tag is pushed:
image1:dev@sha --> image1:dev@new_sha
BUT
image2:dev@sha --> image2:latest@same_sha.
The same happens in reverse.
News about this bug?

I have something similar (using helm), seemingly randomly in .argocd-source-myapp-develop.yaml file one of the image tags - also seems random to me which image - gets changed to or from latest when it should stay develop

name: myapp.image.tag
value: develop@sha256:a3f06c6dd00c1b5...
to
name: myapp.image.tag
value: latest@sha256:a3f06c6dd00c1b5...

Also sometimes when the digest is changing when it is supposed to the tag is also changing to or from latest, instead of staying develop that triggers an unnecessary rolling update.
my config in Applications is:
annotations:
  argocd-image-updater.argoproj.io/image-list: myapp1=myregistry/myapp1:develop, myapp1=myregistry/myapp2:develop

  argocd-image-updater.argoproj.io/myapp1.helm.image-name: myapp1.image.name
  argocd-image-updater.argoproj.io/myapp1.helm.image-tag: myapp1.image.tag
  argocd-image-updater.argoproj.io/myapp1.update-strategy: digest

  argocd-image-updater.argoproj.io/myapp2.helm.image-name: myapp2.image.name
  argocd-image-updater.argoproj.io/myapp2.helm.image-tag: myapp2.image.tag
  argocd-image-updater.argoproj.io/myapp2.update-strategy: digest

  argocd-image-updater.argoproj.io/write-back-method: git
  argocd-image-updater.argoproj.io/git-branch: main

Version
ArgoCD: 2.3.3
Image updater: 0.12.0

Same issue here, image tag set as latest if we use 2+ image from same repo, but their tag is different
Any updates about this issue?
Version:

ArgoCD v2.4.15+05acf7a
Image Updater v0.12.0

Workaround for me was to use <image_alias>.helm.image-spec instead of <image_alias>.helm.image-name and <image_alias>.helm.image-tag. This annotation is described in https://argocd-image-updater.readthedocs.io/en/stable/configuration/images/#specifying-helm-parameter-names
It uses different code which doesn't have the issue that @ggerogery pointed to.
https://github.com/argoproj-labs/argocd-image-updater/blob/202f6bf966566f8a7f9186dced962e517ceb4a3f/pkg/image/image.go#L89-L107


Running multiple Minio server on single host

We need to document steps and provide examples on running multiple instance of Minio servers on different ports on single host.

done closing it


feat: Automatically count the number of sectors needed

Fix issue #18

Hey thanks for taking care of this! I never got a notification for this PR, sorry it took me so long to get around to it. I'm working on evaluating it now, and assuming everything works I'll go ahead and merge it in!


agent etcd launcher might update_membership even though etcd is still running

If the agent Kontena::Launchers::Etcd#create_container determines that the local kontena-etcd Docker container does not exist, it will run update_membership to determine if the etcd cluster needs to be reconfigured to accept the new container that it is about to create. If update_membership determines that a node with the same 10.81.0.x overlay IP already exists in the cluster, it it assumed to be a prior initial node that was removed (kontena node rm) after failing, and being replaced by this node. The etcd cluster will be reconfigured to remove that node, re-add the same node, and then create a new kontena-etcd container to join the existing cluster.
I, [2017-06-21T08:24:28.711601 #1] INFO -- Kontena::Agent: initializing agent (version 1.3.1)
I, [2017-06-21T08:24:28.732384 #1] INFO -- Kontena::Launchers::Etcd: initialized
I, [2017-06-21T08:24:32.451755 #1] INFO -- Kontena::Launchers::Etcd: checking if etcd previous membership needs to be updated
I, [2017-06-21T08:24:32.452526 #1] INFO -- Kontena::Launchers::Etcd: connecting to existing etcd at http://<IP_ADDRESS>:2379/v2/members
I, [2017-06-21T08:24:32.610367 #1] INFO -- Kontena::Launchers::Etcd: Removing existing etcd membership info with id e443fb807a098cc3
I, [2017-06-21T08:24:33.791392 #1] INFO -- Kontena::Launchers::Etcd: Adding new etcd membership info with peer URL http://<IP_ADDRESS>:2380
I, [2017-06-21T08:24:34.984753 #1] INFO -- Kontena::Launchers::Etcd: starting etcd service as a cluster member with initial state: existing
I, [2017-06-21T08:24:34.985953 #1] INFO -- Kontena::Launchers::Etcd: cluster members: node-1=http://<IP_ADDRESS>:2380,node-2=http://<IP_ADDRESS>:2380,node-3=http://<IP_ADDRESS>:2380,node-4=http://<IP_ADDRESS>:2380,node-5=http://<IP_ADDRESS>:2380
I, [2017-06-21T08:24:35.223833 #1] INFO -- Kontena::Launchers::Etcd: started etcd service

However, it turns out that this reconfiguration logic can get run by the agent even though the kontena-etcd container exists and is actually still running (on node-3):
[node-1 kontena-etcd] 2017-06-21 08:23:02.986861 W | rafthttp: the connection to peer e443fb807a098cc3 is unhealthy
[node-2 kontena-etcd] 2017-06-21 08:23:07.820372 W | rafthttp: the connection to peer e443fb807a098cc3 is unhealthy
[node-4 kontena-etcd] 2017-06-21 08:23:13.326850 W | rafthttp: the connection to peer e443fb807a098cc3 is unhealthy
[node-1 kontena-etcd] 2017-06-21 08:23:32.987051 W | rafthttp: the connection to peer e443fb807a098cc3 is unhealthy
[node-2 kontena-etcd] 2017-06-21 08:23:37.820556 W | rafthttp: the connection to peer e443fb807a098cc3 is unhealthy
[node-4 kontena-etcd] 2017-06-21 08:23:43.327230 W | rafthttp: the connection to peer e443fb807a098cc3 is unhealthy
[node-1 kontena-etcd] 2017-06-21 08:24:02.987264 W | rafthttp: the connection to peer e443fb807a098cc3 is unhealthy
[node-2 kontena-etcd] 2017-06-21 08:24:07.820735 W | rafthttp: the connection to peer e443fb807a098cc3 is unhealthy
[node-4 kontena-etcd] 2017-06-21 08:24:13.327491 W | rafthttp: the connection to peer e443fb807a098cc3 is unhealthy
[node-2 kontena-etcd] 2017-06-21 08:24:32.782277 N | etcdserver: removed member e443fb807a098cc3 from cluster 1408077d393bb9fc
[node-1 kontena-etcd] 2017-06-21 08:24:32.795588 N | etcdserver: removed member e443fb807a098cc3 from cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 08:24:32.638228 N | etcdserver: removed member e443fb807a098cc3 from cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 08:24:33.775229 N | etcdserver: added member a76e19ee4f28d8b7 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc
[node-2 kontena-etcd] 2017-06-21 08:24:33.977924 N | etcdserver: added member a76e19ee4f28d8b7 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc
[node-1 kontena-etcd] 2017-06-21 08:24:33.992300 N | etcdserver: added member a76e19ee4f28d8b7 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc
[node-2 kontena-etcd] 2017-06-21 08:24:35.513985 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-1 kontena-etcd] 2017-06-21 08:24:35.520792 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-1 kontena-etcd] 2017-06-21 08:24:35.522007 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-2 kontena-etcd] 2017-06-21 08:24:35.531744 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-4 kontena-etcd] 2017-06-21 08:24:35.383757 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-4 kontena-etcd] 2017-06-21 08:24:35.385837 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-3 kontena-etcd] 2017-06-21 08:24:35.482792 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:35.483133 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:35.484663 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:35.484933 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:35.486100 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:35.486345 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:35.487126 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:35.487342 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:35.527964 E | etcdserver: the member has been permanently removed from the cluster
[node-3 kontena-etcd] 2017-06-21 08:24:35.528247 I | etcdserver: the data-dir used by this member must be removed.

The most likely explanation for this happening is that the Docker::Container.get('kontena-etcd') fails with some sporadic Docker API error. The agent etcd launcher code uses rescue nil to recover from the expected Docker::Error::NotFound case, but this style of error handling means that any other unrelated errors will also cause the agent to assume that the local etcd node is gone, and perform these undesired cluster reconfigurations.

The result of this kind of spurious etcd reconfiguration can vary, it seems to be possible for the etcd service to recover from being removed and re-added to the cluster at runtime, or as in this case, it may not:
[node-3 kontena-etcd] 2017-06-21 08:24:35.530738 W | rafthttp: failed to process raft message (raft: stopped)
[node-1 kontena-etcd] 2017-06-21 08:24:36.148458 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-1 kontena-etcd] 2017-06-21 08:24:36.153343 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-4 kontena-etcd] 2017-06-21 08:24:36.899025 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-4 kontena-etcd] 2017-06-21 08:24:36.900765 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-3 kontena-etcd] 2017-06-21 08:24:36.150007 E | etcdserver: the member has been permanently removed from the cluster
[node-3 kontena-etcd] 2017-06-21 08:24:36.150051 I | etcdserver: the data-dir used by this member must be removed.
[node-3 kontena-etcd] 2017-06-21 08:24:36.181222 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.184966 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.186211 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.187507 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.188376 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.189327 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.190433 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.191895 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.193814 E | etcdhttp: got unexpected response error (etcdserver: server stopped)

If the etcd service crashes and restarts, then it will be unable to recover, as the local etcd member ID differs from the member ID expected by the other members of the cluster:
[node-3 kontena-etcd] 2017-06-21 08:24:36.650312 W | flags: unrecognized environment variable ETCD_RELEASE=2.3.7
[node-3 kontena-etcd] 2017-06-21 08:24:36.652827 I | etcdmain: etcd Version: 2.3.7
[node-3 kontena-etcd] 2017-06-21 08:24:36.652868 I | etcdmain: Git SHA: fd17c91
[node-3 kontena-etcd] 2017-06-21 08:24:36.652883 I | etcdmain: Go Version: go1.6.2
[node-3 kontena-etcd] 2017-06-21 08:24:36.652894 I | etcdmain: Go OS/Arch: linux/amd64
[node-3 kontena-etcd] 2017-06-21 08:24:36.652906 I | etcdmain: setting maximum number of CPUs to 1, total number of available CPUs is 1
[node-3 kontena-etcd] 2017-06-21 08:24:36.652965 N | etcdmain: the server is already initialized as member before, starting as etcd member...
[node-3 kontena-etcd] 2017-06-21 08:24:36.653075 I | etcdmain: listening for peers on http://<IP_ADDRESS>:2380
[node-3 kontena-etcd] 2017-06-21 08:24:36.653417 I | etcdmain: listening for client requests on http://<IP_ADDRESS>:2379
[node-3 kontena-etcd] 2017-06-21 08:24:36.653497 I | etcdmain: listening for client requests on http://<IP_ADDRESS>:2379
[node-3 kontena-etcd] 2017-06-21 08:24:36.653575 I | etcdmain: listening for client requests on http://<IP_ADDRESS>:2379
[node-3 kontena-etcd] 2017-06-21 08:24:36.671556 I | etcdserver: recovered store from snapshot at index 2770277
[node-3 kontena-etcd] 2017-06-21 08:24:36.672788 I | etcdserver: name = node-3
[node-3 kontena-etcd] 2017-06-21 08:24:36.672827 I | etcdserver: data dir = /var/lib/etcd
[node-3 kontena-etcd] 2017-06-21 08:24:36.672844 I | etcdserver: member dir = /var/lib/etcd/member
[node-3 kontena-etcd] 2017-06-21 08:24:36.672856 I | etcdserver: heartbeat = 100ms
[node-3 kontena-etcd] 2017-06-21 08:24:36.672867 I | etcdserver: election = 1000ms
[node-3 kontena-etcd] 2017-06-21 08:24:36.672877 I | etcdserver: snapshot count = 10000
[node-3 kontena-etcd] 2017-06-21 08:24:36.672908 I | etcdserver: advertise client URLs = http://<IP_ADDRESS>:2379
[node-3 kontena-etcd] 2017-06-21 08:24:36.848392 I | etcdserver: restarting member e443fb807a098cc3 in cluster 1408077d393bb9fc at commit index 2772461
[node-3 kontena-etcd] 2017-06-21 08:24:36.851383 I | raft: e443fb807a098cc3 became follower at term 1455
[node-3 kontena-etcd] 2017-06-21 08:24:36.852294 I | raft: newRaft e443fb807a098cc3 [peers: [1196d82c110ae41d,534660f6dff019b4,7ee6bd497759c151,e443fb807a098cc3,f6605e14e1165799], term: 1455, commit: 2772461, applied: 2770277, lastindex: 2772461, lastterm: 1454]
[node-3 kontena-etcd] 2017-06-21 08:24:36.853464 I | etcdserver: added member 1196d82c110ae41d [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc from store
[node-3 kontena-etcd] 2017-06-21 08:24:36.855812 I | etcdserver: added member 534660f6dff019b4 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc from store
[node-3 kontena-etcd] 2017-06-21 08:24:36.855855 I | etcdserver: added member 7ee6bd497759c151 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc from store
[node-3 kontena-etcd] 2017-06-21 08:24:36.855874 I | etcdserver: added member e443fb807a098cc3 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc from store
[node-3 kontena-etcd] 2017-06-21 08:24:36.855887 I | etcdserver: added member f6605e14e1165799 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc from store
[node-3 kontena-etcd] 2017-06-21 08:24:36.855931 I | etcdserver: set the cluster version to 2.3 from store
[node-3 kontena-etcd] 2017-06-21 08:24:36.943649 I | etcdserver: starting server... [version: 2.3.7, cluster version: 2.3]
[node-3 kontena-etcd] 2017-06-21 08:24:36.949384 I | raft: raft.node: e443fb807a098cc3 elected leader 1196d82c110ae41d at term 1455
[node-3 kontena-etcd] 2017-06-21 08:24:36.954011 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.954429 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.954799 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.954011 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.954429 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.954799 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.955160 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.983415 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.985532 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.990937 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:36.991807 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-2 kontena-etcd] 2017-06-21 08:24:37.033044 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-1 kontena-etcd] 2017-06-21 08:24:37.043141 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-1 kontena-etcd] 2017-06-21 08:24:37.044765 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-2 kontena-etcd] 2017-06-21 08:24:37.034665 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-4 kontena-etcd] 2017-06-21 08:24:37.984683 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-4 kontena-etcd] 2017-06-21 08:24:37.986581 W | rafthttp: rejected the stream from peer e443fb807a098cc3 since it was removed
[node-3 kontena-etcd] 2017-06-21 08:24:37.056536 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:37.056642 E | rafthttp: streaming request ignored (ID mismatch got a76e19ee4f28d8b7 want e443fb807a098cc3)
[node-3 kontena-etcd] 2017-06-21 08:24:37.061801 E | etcdserver: the member has been permanently removed from the cluster
[node-3 kontena-etcd] 2017-06-21 08:24:37.061815 I | etcdserver: the data-dir used by this member must be removed.

Similar case where the etcd node (node-4) was able to recover:
[node-5 kontena-etcd] 2017-06-21 05:37:24.183773 W | rafthttp: the connection to peer 502b6b592bf8ddb7 is unhealthy
[node-5 kontena-etcd] 2017-06-21 05:37:24.184025 W | rafthttp: the clock difference against peer 502b6b592bf8ddb7 is too high [2.267893678s > 1s]
[node-3 kontena-etcd] 2017-06-21 05:37:26.195452 W | etcdserver: failed to reach the peerURL(http://<IP_ADDRESS>:2380) of member 502b6b592bf8ddb7 (Get http://<IP_ADDRESS>:2380/version: dial tcp <IP_ADDRESS>:2380: i/o timeout)
[node-3 kontena-etcd] 2017-06-21 05:37:26.195552 W | etcdserver: cannot get the version of member 502b6b592bf8ddb7 (Get http://<IP_ADDRESS>:2380/version: dial tcp <IP_ADDRESS>:2380: i/o timeout)
[node-3 kontena-etcd] 2017-06-21 05:37:31.480803 W | etcdserver: failed to reach the peerURL(http://<IP_ADDRESS>:2380) of member 502b6b592bf8ddb7 (Get http://<IP_ADDRESS>:2380/version: dial tcp <IP_ADDRESS>:2380: i/o timeout)
[node-3 kontena-etcd] 2017-06-21 05:37:31.480897 W | etcdserver: cannot get the version of member 502b6b592bf8ddb7 (Get http://<IP_ADDRESS>:2380/version: dial tcp <IP_ADDRESS>:2380: i/o timeout)
[node-1 kontena-etcd] 2017-06-21 05:37:32.947531 W | rafthttp: the connection to peer 502b6b592bf8ddb7 is unhealthy
[node-3 kontena-etcd] 2017-06-21 05:37:36.316205 W | etcdserver: failed to reach the peerURL(http://<IP_ADDRESS>:2380) of member 502b6b592bf8ddb7 (Get http://<IP_ADDRESS>:2380/version: dial tcp <IP_ADDRESS>:2380: getsockopt: no route to host)
[node-3 kontena-etcd] 2017-06-21 05:37:36.316299 W | etcdserver: cannot get the version of member 502b6b592bf8ddb7 (Get http://<IP_ADDRESS>:2380/version: dial tcp <IP_ADDRESS>:2380: getsockopt: no route to host)
[node-3 kontena-etcd] 2017-06-21 05:37:36.316205 W | etcdserver: failed to reach the peerURL(http://<IP_ADDRESS>:2380) of member 502b6b592bf8ddb7 (Get http://<IP_ADDRESS>:2380/version: dial tcp <IP_ADDRESS>:2380: getsockopt: no route to host)
[node-3 kontena-etcd] 2017-06-21 05:37:38.690679 N | etcdserver: removed member 502b6b592bf8ddb7 from cluster 1408077d393bb9fc
[node-2 kontena-etcd] 2017-06-21 05:37:38.695056 N | etcdserver: removed member 502b6b592bf8ddb7 from cluster 1408077d393bb9fc
[node-1 kontena-etcd] 2017-06-21 05:37:38.692515 N | etcdserver: removed member 502b6b592bf8ddb7 from cluster 1408077d393bb9fc
[node-5 kontena-etcd] 2017-06-21 05:37:38.837485 N | etcdserver: removed member 502b6b592bf8ddb7 from cluster 1408077d393bb9fc
[node-2 kontena-etcd] 2017-06-21 05:37:38.695056 N | etcdserver: removed member 502b6b592bf8ddb7 from cluster 1408077d393bb9fc
[node-3 kontena-etcd] 2017-06-21 05:37:39.749662 N | etcdserver: added member 7ee6bd497759c151 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc
[node-1 kontena-etcd] 2017-06-21 05:37:39.757837 N | etcdserver: added member 7ee6bd497759c151 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc
[node-2 kontena-etcd] 2017-06-21 05:37:39.759123 N | etcdserver: added member 7ee6bd497759c151 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc
[node-5 kontena-etcd] 2017-06-21 05:37:39.917172 N | etcdserver: added member 7ee6bd497759c151 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc
[node-3 kontena-etcd] 2017-06-21 05:37:40.393799 W | etcdserver: failed to reach the peerURL(http://<IP_ADDRESS>:2380) of member 7ee6bd497759c151 (Get http://<IP_ADDRESS>:2380/version: dial tcp <IP_ADDRESS>:2380: getsockopt: connection refused)
[node-3 kontena-etcd] 2017-06-21 05:37:40.393889 W | etcdserver: cannot get the version of member 7ee6bd497759c151 (Get http://<IP_ADDRESS>:2380/version: dial tcp <IP_ADDRESS>:2380: getsockopt: connection refused)
[node-3 kontena-etcd] 2017-06-21 05:37:40.393799 W | etcdserver: failed to reach the peerURL(http://<IP_ADDRESS>:2380) of member 7ee6bd497759c151 (Get http://<IP_ADDRESS>:2380/version: dial tcp <IP_ADDRESS>:2380: getsockopt: connection refused)
[node-3 kontena-etcd] 2017-06-21 05:37:42.825944 I | rafthttp: the connection with 7ee6bd497759c151 became active
[node-5 kontena-etcd] 2017-06-21 05:37:42.942833 I | rafthttp: the connection with 7ee6bd497759c151 became active
[node-1 kontena-etcd] 2017-06-21 05:37:42.867415 I | rafthttp: the connection with 7ee6bd497759c151 became active
[node-2 kontena-etcd] 2017-06-21 05:37:42.862787 I | rafthttp: the connection with 7ee6bd497759c151 became active
[node-4 kontena-etcd] 2017-06-21 05:37:42.804420 I | raft: 7ee6bd497759c151 became follower at term 1454
[node-4 kontena-etcd] 2017-06-21 05:37:42.804504 I | raft: raft.node: 7ee6bd497759c151 elected leader e443fb807a098cc3 at term 1454
[node-4 kontena-etcd] 2017-06-21 05:37:42.837080 I | rafthttp: the connection with 1196d82c110ae41d became active
[node-4 kontena-etcd] 2017-06-21 05:37:42.838458 I | rafthttp: the connection with e443fb807a098cc3 became active
[node-4 kontena-etcd] 2017-06-21 05:37:42.840224 I | rafthttp: the connection with 534660f6dff019b4 became active
[node-4 kontena-etcd] 2017-06-21 05:37:42.841216 I | rafthttp: the connection with f6605e14e1165799 became active
[node-4 kontena-etcd] 2017-06-21 05:37:43.210318 I | raft: 7ee6bd497759c151 [commit: 0, lastindex: 0, lastterm: 0] starts to restore snapshot [index: 2750275, term: 1454]
[node-4 kontena-etcd] 2017-06-21 05:37:43.210445 I | raft: log [committed=0, applied=0, unstable.offset=1, len(unstable.Entries)=0] starts to restore snapshot [index: 2750275, term: 1454]
[node-4 kontena-etcd] 2017-06-21 05:37:43.210584 I | raft: 7ee6bd497759c151 restored progress of 1196d82c110ae41d [next = 2750276, match = 0, state = ProgressStateProbe, waiting = false, pendingSnapshot = 0]
[node-4 kontena-etcd] 2017-06-21 05:37:43.210653 I | raft: 7ee6bd497759c151 restored progress of 502b6b592bf8ddb7 [next = 2750276, match = 0, state = ProgressStateProbe, waiting = false, pendingSnapshot = 0]
[node-4 kontena-etcd] 2017-06-21 05:37:43.210832 I | raft: 7ee6bd497759c151 restored progress of 534660f6dff019b4 [next = 2750276, match = 0, state = ProgressStateProbe, waiting = false, pendingSnapshot = 0]
[node-4 kontena-etcd] 2017-06-21 05:37:43.210905 I | raft: 7ee6bd497759c151 restored progress of e443fb807a098cc3 [next = 2750276, match = 0, state = ProgressStateProbe, waiting = false, pendingSnapshot = 0]
[node-4 kontena-etcd] 2017-06-21 05:37:43.210956 I | raft: 7ee6bd497759c151 restored progress of f6605e14e1165799 [next = 2750276, match = 0, state = ProgressStateProbe, waiting = false, pendingSnapshot = 0]
[node-4 kontena-etcd] 2017-06-21 05:37:43.211036 I | raft: 7ee6bd497759c151 [commit: 2750275] restored snapshot [index: 2750275, term: 1454]
[node-4 kontena-etcd] 2017-06-21 05:37:43.219890 I | etcdserver: added member 534660f6dff019b4 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc from store
[node-4 kontena-etcd] 2017-06-21 05:37:43.220038 I | etcdserver: added member e443fb807a098cc3 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc from store
[node-4 kontena-etcd] 2017-06-21 05:37:43.220192 I | etcdserver: added member f6605e14e1165799 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc from store
[node-4 kontena-etcd] 2017-06-21 05:37:43.220276 I | etcdserver: added member 1196d82c110ae41d [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc from store
[node-4 kontena-etcd] 2017-06-21 05:37:43.220354 I | etcdserver: added member 502b6b592bf8ddb7 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc from store
[node-4 kontena-etcd] 2017-06-21 05:37:43.220424 I | etcdserver: set the cluster version to 2.3 from store
[node-4 kontena-etcd] 2017-06-21 05:37:43.222115 E | rafthttp: failed to read 534660f6dff019b4 on stream MsgApp v2 (net/http: request canceled)
[node-4 kontena-etcd] 2017-06-21 05:37:43.222260 I | rafthttp: the connection with 534660f6dff019b4 became inactive
[node-4 kontena-etcd] 2017-06-21 05:37:43.232555 E | rafthttp: failed to read e443fb807a098cc3 on stream MsgApp v2 (net/http: request canceled)
[node-4 kontena-etcd] 2017-06-21 05:37:43.232698 I | rafthttp: the connection with e443fb807a098cc3 became inactive
[node-4 kontena-etcd] 2017-06-21 05:37:43.235798 E | rafthttp: failed to read f6605e14e1165799 on stream MsgApp v2 (net/http: request canceled)
[node-4 kontena-etcd] 2017-06-21 05:37:43.235953 I | rafthttp: the connection with f6605e14e1165799 became inactive
[node-4 kontena-etcd] 2017-06-21 05:37:43.262827 I | etcdserver: recovered from incoming snapshot at index 2750275
[node-4 kontena-etcd] 2017-06-21 05:37:43.268432 E | rafthttp: failed to find member 7ee6bd497759c151 in cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 05:37:43.269548 I | rafthttp: the connection with 1196d82c110ae41d became active
[node-4 kontena-etcd] 2017-06-21 05:37:43.275611 E | rafthttp: failed to find member 7ee6bd497759c151 in cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 05:37:43.335407 I | rafthttp: the connection with f6605e14e1165799 became active
[node-4 kontena-etcd] 2017-06-21 05:37:43.363585 I | etcdserver: raft applied incoming snapshot at index 2750275
[node-4 kontena-etcd] 2017-06-21 05:37:43.366712 I | rafthttp: the connection with 534660f6dff019b4 became active
[node-4 kontena-etcd] 2017-06-21 05:37:43.428870 I | rafthttp: the connection with e443fb807a098cc3 became active
[node-4 kontena-etcd] 2017-06-21 05:37:43.440893 E | rafthttp: failed to find member 7ee6bd497759c151 in cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 05:37:43.441213 E | rafthttp: failed to find member 7ee6bd497759c151 in cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 05:37:43.544039 E | rafthttp: failed to find member 7ee6bd497759c151 in cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 05:37:43.545461 E | rafthttp: failed to find member 7ee6bd497759c151 in cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 05:37:43.647516 E | rafthttp: failed to find member 7ee6bd497759c151 in cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 05:37:43.648083 E | rafthttp: failed to find member 7ee6bd497759c151 in cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 05:37:43.749742 E | rafthttp: failed to find member 7ee6bd497759c151 in cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 05:37:43.751104 E | rafthttp: failed to find member 7ee6bd497759c151 in cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 05:37:43.935729 N | etcdserver: removed member 502b6b592bf8ddb7 from cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 05:37:43.936826 N | etcdserver: added local member 7ee6bd497759c151 [http://<IP_ADDRESS>:2380] to cluster 1408077d393bb9fc
[node-4 kontena-etcd] 2017-06-21 05:37:43.939093 I | etcdserver: published {Name:node-4 ClientURLs:[http://<IP_ADDRESS>:2379]} to cluster 1408077d393bb9fc
[node-3 kontena-etcd] 2017-06-21 06:13:38.599071 I | etcdserver: start to snapshot (applied: 2760276, lastsnap: 2750275)
[node-2 kontena-etcd] 2017-06-21 06:13:38.603561 I | etcdserver: start to snapshot (applied: 2760276, lastsnap: 2750275)

I, [2017-06-21T08:24:35.223833 #1] INFO -- Kontena::Launchers::Etcd: started etcd service

A related bug here is that the Kontena::Launchers::Etcd calls Docker::Container#start, instead of start!. This swallows any resulting Docker errors, preventing the agent from logging them:  #2134
In this case, I expect the agent would have logged an error about the kontena-etcd container already existing when trying to create it. It wouldn't have prevented the etcd cluster reconfiguration issue, but it would have made this easier to diagnose.

Tried to repro a Docker API error on the latest CoreOS stable, but didn't pick up anything:
while true; do
  curl -f -v --unix-socket /var/run/docker.sock -H "Content-Type: application/json" -X GET http:/v1.22/containers/kontena-etcd/json || break
done

A related bug here is that the Kontena::Launchers::Etcd calls Docker::Container#start, instead of start!. [...] In this case, I expect the agent would have logged an error about the kontena-etcd container already existing when trying to create it

Looking into this issue again, there must be some misunderstanding going on here on my part; the agent using start vs start! shouldn't matter, because it's the Docker::Container.create('name' => 'kontena-etcd', ...) call that would have failed with Docker::Error::ConflictError: Conflict. The name "/kontena-etcd" is already in use by container ... in case Docker::Container.get raised some error but the kontena-etcd container was actually still running. That the Docker::Container.create did not fail makes me think that the kontena-etcd container was actually legitimately gone. It's possible that I was reading the logs incorrectly, and this wasn't actually caused by Docker::Container.get failing with unknown errors while the kontena-etcd container was still running.
Based on an alternative reading of the logs in this issue, taking into account that #2731 would cause the kontena-etcd container logs at initial startup to have been truncated in the kontena grid logs output, I think it's more likely that the kontena-etcd and/or kontena-etcd-data containers had been removed manually in this case... on node-3 only the kontena-etcd container was removed and re-created with the old kontena-etcd-data container still in place, which failed with the member has been permanently removed from the cluster / the data-dir used by this member must be removed. On node-4, both the kontena-etcd and kontena-etcd-data containers would have been removed, and it was able to boot up from an empty datadir with the new 7ee6bd497759c151 member identity.
It looks like there's a separate issue for the agent etcd launcher being unable to handle the kontena-etcd container getting re-created...


Stream connection hanging forever

Describe the bug
I have a stream service in a server behind a proxy that has a timeout of 10 min and then closes the connection, when this happens I expect the async iterator to throw an exception (so I can reconnect again) but instead it just hangs forever.
I found this related issue in the grpc-js library which looks the same, but I've been able to workaround it by enabling sending keepalive pings with 'grpc.keepalive_time_ms' option, can a similar option be added to connect-node library?

Thanks for raising this, Jean Pierre. Stream termination with a proxy in between can be tricky.
To clarify, this happens with a client transport from @bufbuild/connect-node over H2?
Just hanging forever is not acceptable. Yes I'm sure we will be able to provide a fix for this.

yes I'm using @bufbuild/connect-node over http2

@jeanp413, it took a while, but this should be addressed by https://github.com/bufbuild/connect-es/pull/619. There was a straight-forward bug in the client implementation that caused connections that unexpectedly ended to hang.
We do not send HTTP/2 PING frames to keep the session alive, but it seems that your issue is likely the bug, not the keep alive.
In case you do still experience an issue after this is released, let us know.

hey @timostamm just give a quick try from sources and still can repro, but seems that the issue is not related to the proxy I mention initially, the thing is my stream service does not sent data continuously only when some event happens, so it could be that it doesn't send any data for 10 min but after that time the socket is not responsive anymore and the async iterator hangs forever, found this stackoverflow question that mentions sending keepalive pings too

Thanks for testing it, @jeanp413! I'm surprised to hear that it's still happening. Could you share some information about the server and your deployment?
I have created https://github.com/bufbuild/connect-es/issues/627 specifically for HTTP/2 PING frames, and will leave this issue closed. We're currently adding client-side deadlines, so that a timeout always aborts the request without relying on the server to close. This should also help to deal with such an issue, although I'm aware it doesn't replace actively monitoring the connection.

I forgot to mention: Talking about HTTP/2 ping to others, I've also heard about issues with especially in combination with proxies that might terminate ack the pings for your client, while your upstream connection dies due to idle. They are not a silver bullet either.

@jeanp413, we have implemented keep-alive with https://github.com/bufbuild/connect-es/pull/673. You should be able to set pingIntervalMs, which behaves very similar to grpc.keepalive_time_ms.

Awesome, will try it out early next week, thanks :tada:


Add diagrams to Quick Start

Overview
Adds new <Diagram> and <DiagramGroup> for embedding diagrams into the docs, and adds new diagrams to the Quick Start page as the initial diagrams on the beta site.
Screens
Mobile (light)

Mobile (dark)

Desktop (light)

Desktop (dark)

Any particular reason for PNG rather than SVG export?

No reason, switched to svg.

nice, this looks a lot crispier

Updated with better dark mode diagrams

WOAH

Feeling good about the latest state, will ship and iterate if needed!


Icons & text for mulit-select buttons are not aligned

Date - 12/3/19
Steps:

Go to any Resource page (Service, router, etc...)
Check the checkbox to select all resources on that page (Make sure there is more than one selected)

Results:  the Download YAML & the Delete button Icon's aren't aligned properly with the button text.  Icons are lower then the text.

date - 12/5
Verified fixed


Add new layout options in the stimulator

Is your feature request related to a problem? Please describe.
We can add different layout options so that the user can choose whatever suits them.
Describe the solution you'd like
Add different types of layout in the stimulator. This can be easily done using flex options on the layout. Some of the view options can be as follows:

Sidebar on the left and canvas right (present layout)
Sidebar on the right and canvas on the left side
A full-screen view in which the sidebar is hidden or not shown. We can also create a completely new route for this view.
(Codepen is a good example for this particular feature, they have many layout options on their site)

I am not exactly sure what the issue is ? What exactly needs to be done?

This is about various types of views like we have in codepen editor.
(https://codepen.io/pen/)

Please check https://beta.circuitverse.org/simulator


0.9.0

New features & improvements:

Introduced public room listing (getAvailableRooms) (https://github.com/gamestdio/colyseus/issues/131)
Horizontal scalability through Redis (https://github.com/gamestdio/colyseus/issues/57)
PM2 is now supported (https://github.com/gamestdio/colyseus/issues/56)
Improved how rooms are automatically locked when maxClients is reached.
If an application error occurs during onJoin - the onLeave will be triggered immediately for custom clean up. (https://github.com/gamestdio/colyseus/issues/132)
You can use clock intervals without setting the simulation interval.

Breaking changes:

The ClusterServer has been deprecated. (fixes https://github.com/gamestdio/colyseus/issues/56, https://github.com/gamestdio/colyseus/issues/74, https://github.com/gamestdio/colyseus/issues/91, https://github.com/gamestdio/colyseus/issues/125, https://github.com/gamestdio/colyseus/issues/126)
verifyClient(client, options) has been renamed to onAuth(options)
Integration with uws is now done through Server constructor.
(client-side) room.onData has been renamed to room.onMessage.  (#128)
(client-side) room.onUpdate has been renamed to room.onStateChange  (#128)
(client-side) room.data has been renamed to room.state  (#128)

Thanks for supporting! The breaking changes are documented here: http://colyseus.io/docs/migrating/#migrating-to-09x-from-06x-or-08x


Transceiver library

We need a library of functions (transceiver.c and transceiver.h) to communicate between OBC and the transceiver over UART. The protocol is based on the UHF type_II_User_Manual_and_Protocol_Rev_2.pdf document, pages 15-23.
The current general UART library assumes the microcontroller is connected to a laptop, but the same principles work for the transceiver's UART.
From the OBC's perspective:
UART TX (OBC commands to transceiver): Use the print() function. We will probably define a function called send_uart() later, but print() does the same thing.
UART RX (transceiver response to OBC): See the example here. Call register_callback() from main(), which registers the callback function you define so that the callback function will be called whenever the microcontroller receives UART and is passed the array and length of characters received. The callback function you create must return the number of characters it has "processed" and will be discarded from the UART buffer.
Here is an example of the type of command we want to encapsulate in a function:
// define this somewhere, default device address
#define TRANS_ADDR 0x22

// from p.18
void set_trans_pipe_timeout(uint8_t timeout) {
    print("ES+W%2X06000000%2X\r", TRANS_ADDR, timeout);
}

We need to figure out some equivalent of scanf() for processing the transceiver's response messages.

First iteration of the transceiver library is merged: #18 . Next is to figure out AX25 packetization.


My ExecStart

Hi, thanks for your work.
But I have to made this change to make it work.
Thanks.
#ExecStart=/home/ubuntu/.rbenv/bin/rbenv exec bundle exec rake solid_queue:start
ExecStart=/home/ubuntu/.rbenv/shims/bundle exec rake solid_queue:start

Same for me, Thanks for the tip !


[CWS] do not use event category to select parsing/serializer

What does this PR do?
Do not rely on the event category to parse or to serialize network context. The category should be only used to disable certain rules according the CWS features.
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


Compatibility and Floating Enemies when using v1.0.7

Hello! Sorry to bother you again, but I notice both "compatibility with other mods like ScanForEnemies" and "randomly floating enemies" that were supposedly fixed in v1.0.6 came back in v1.0.7

Both pictures were taken using v1.0.7
Edit: I checked v1.0.6, and it turned out that the reason both previously mentioned things were fixed was because the mod's config files weren't getting saved/loaded. (Just like you said in your Changelog)
So... when you fixed it so that it could save/load the config files again, those things also came back since they weren't actually fixed :(
Btw, there's a mod called "PestControl" which could adjust enemy spawn weights without the need of spawning fake enemies.
Sorry if that doesn't help as I don't really understand the mechanics, but I really like your mod since it provides a lot more options than the others, and it personalizes and enhances me and my friends' experience a lot :)
Again, thank you for your hard work!

Yes, I did unfortunately mess up on the 1.0.6 release and prevent any configs from being loaded, which meant nothing spawned, but nothing worked. I'm currently trying to fix this issue and will update as soon as I can. Thanks!

Yes, I did unfortunately mess up on the 1.0.6 release and prevent any configs from being loaded, which meant nothing spawned, but nothing worked. I'm currently trying to fix this issue and will update as soon as I can. Thanks!

No worries, please take your time! Thank you for bringing this mod to the community!

I tested v1.0.8 with ScanForEnemies as well, and it seems to have worked. However, ScanForEnemies does not always update correctly, especially if some enemies are not naturally spawned into the game. The spider issue still remains, which I am still investigating.


When listing resources on a stopped node, display a user-friendly error message

Observed behavior
The list commands should show a more descriptive error message when the node that is being queried is not running.
Steps to reproduce
ockam node create n
ockam service list --at n # works as expected
ockam node stop n
ockam service list --at n # throws the error below

× connection peer was not found (origin: Transport, kind: Misuse, source location: /rustc/90c541806f23a127002de5b4038be731ba1458ca/library/core/src/convert/mod.rs:727:9)

Expected behavior
The error message should be user-friendly. Something like: The node n is not running.
Ockam Version
0.89

Mind if I give this a go?

@BradLewis we'd love that. All yours


Optimised Code, Added Support, Fixed Lang

Okay, admittedly, this turned into a much larger PR than I had intended. I hope that it is okay all in one chunk. There were a number of small tweaks that I made, especially when it comes to the use of Lambda and typing clarifications. I also added support for a number of mods. Some was partial, some was complete. I tried to fit them into the appropriate categories whilst trying to follow the logic that you've laid out with other mobs.
Thanks for such an amazing mod! I cannot wait to see it continue to take off! :D
Changelog

Clarified methods and targets for mixins
Clarified typings
Converted possible code to Lambdas
Added support for the following mods:

Amethyst Imbuement
Aquamirae (partial, added bosses to blacklisted.json)
Better End
Bosses of Mass Destruction (partial, added bosses to blacklisted.json)
Clutter
Enderman Overhaul
Friends and Foes
Graveyard (partial, added bosses to blacklisted.json)
Guard Villagers
Illager Invasion (partial, added bosses to blacklisted.json)
Let's Do: Beach Party
Let's Do: Vinery
MC Dungeons Armors (added summons to blacklisted.json)
MC Dungeons Artifacts (added summons to blacklisted.json)
MC Dungeons Weapons (added summons to blacklisted.json)
Mythic Mounts (added to blacklisted.json because of crash)
Marium's Soulslike Weaponry (partial, added bosses to blacklisted.json)
Naturalist
Wildlife
Xerca Music (added unimplemented, but accessible mobs to blacklisted.json)

Added requirement check for vanilla mobs in json files since vanilla mobs can be disabled with datapacks
Added @Unique markers and prefixing to unique methods and fields
Optimised Imports
Corrected spelling error in en_us.json

@ToCraft That would be really nice! Thank you! And no problem! I was planning another PR with more abilities, but I wanted to touch base with you before I did that :P

@chronosacaria Sounds great! Could you send me your Minecraft-UUID for the list? (per Discord or here)


SSR Vue Router: The client-side rendered virtual DOM tree is not matching server-rendered content.

I receive "bundle.js:2662 [Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content. This is likely caused by incorrect HTML markup, for example nesting block-level elements inside "p", or missing "tbody". Bailing hydration and performing full client-side render." when adding the  element to my application while using Vue.js Server Side Rendering.  When I remove the  element I get no errors.

Hi, thanks for filling this issue.

This is likely caused by incorrect HTML markup, for example nesting block-level elements inside "p", or missing "tbody".

The error message has already explained the cause of the problem, please check if your template is valid html.
The error message


Add overarching "how to get involved" page

@ProjectPythia/outreach suggests we create an overarching space on the main portal highlighting How to get involved. The initial ways we expect community involvement we picture are

Technical contributions: code, notebooks, infrastructure, etc.
Feedback: using and reviewing our materials for educational feedback
Ambassadorship: sharing us! social media, in-class, at-conference, etc.

where we'd have each of these described briefly on this page and then direct people to relevant pages for elaboration, e.g. to the contributor's guide.
We then could boil this page down to a flyer for sharing over social media or in-person as necessary, with a link/QR code to "how to get involved".
We plan to bring this up at Thursday's meeting for feedback and moving forward!

Just noting here that we did indeed discuss this at today's EWG meeting and there was a strong consensus that we should do this.


Support the 4dF syntax used by Fate and Fudge

https://en.wikipedia.org/wiki/Fudge_(role-playing_game_system)#Game_mechanics
This would make it much easier to run Fate games using a Slack channel so I would appreciate it if you would consider this feature. Thanks!

A quick and dirty way to do this is Xd3-2X
You'll have to do the 2X multiplication yourself, though :)

it would still be cool to have 4dF :)
+1

@arkie Thanks for adding Fate Dice!


doc(architecture): trait section

Ref #2273

Release Note
NONE

@astefanutti @nicolaferraro I'd like your review to confirm that the document explaining traits is accurate enough. Thanks!

Thanks @astefanutti @tadayosi, I've adjusted following your suggestions. Please, have a further look.

@squakez LGTM. Thanks!


Consider automating mina sudo commands by connecting with sudo user

Instead of using reminders to tell user to manually run sudo commands, provide a sudo user variable that would then login during mina setup and do the sudo commands itself.

Finished:

Created task "post_setup" to be run after first deploy.

To-do:

Test post_setup with sudo user (get user from jason)
Update reminders - rename "after_deploy" namespace to "sudo_commands", and make it output a note that the user can run "post_setup" with a sudo_user to do these things automatically
Update documentation: https://docs.google.com/document/d/1Rx5EpBvDYfwhnPqIWa10Og4rDSqPhJUElsEpnS1AS-Q/edit


Accept object as connect's mapStateToProps argument?

We can currently call connect with an object argument for mapDispatchToProps, where each function in the object is assumed to be an actioncreator.  Could a similar option be available for mapStateToProps, where it would be assumed that each function in the object would be a selector?  This could then be used as, for example:
import { connect } from 'react-redux';
import { actionCreator1, actionCreator2 } from './ActionCreators';
import { selector1, selector2 } user from './Selectors';
import PresentationalComponent from './PresentationalComponent';

export default connect(
    {
        selector1,
        selector2
    },
    {
        actionCreator1,
        actionCreator2
    }
)( PresentationalComponent );

I am currently achieving this with the following:
import { connect } from 'react-redux';

export default (originalStateToProps, dispatchToProps) => {

    let updatedStateToProps = originalStateToProps;

    if (typeof originalStateToProps !== "function") {
        updatedStateToProps = (state, ownProps) => {
            let mappedProps = {};
            for (const key in originalStateToProps) {
                if (originalStateToProps.hasOwnProperty(key)) {
                    mappedProps[key] = originalStateToProps[key](state, ownProps);
                }
            }
            return mappedProps;
        }
    }

    return connect( updatedStateToProps, dispatchToProps );
}

See #323


[BUG] Prophet wrapper internally changing argument X (exogenous data)

Describe the bug

When fitting prophet with exogenous data, the wrapper changes the argument X resulting in some issues; you can't use the same variable X as argument twice since it'll contain the column name ds after the first run, so you need to create copies at each occurence.
It gets worse when you do a fit_predict since the X changes internally (because of fit), when fit_predict calls predict, it raises an error that you can't work around with copies.
To Reproduce
from sktime.forecasting.fbprophet import Prophet
import pandas as pd
import numpy as np

y_train = pd.Series(np.arange(1,21), index=pd.date_range(start='1/1/2021', end='20/1/2021'))
X_train = pd.DataFrame(data=np.arange(1,21), columns=['something'], index=pd.date_range(start='1/1/2021', end='20/1/2021'))

arima_forecaster = Prophet()
arima_forecaster.fit_predict(fh=y_train.index, y=y_train, X=X_train)
print(X_train)

Traceback

ValueError                                Traceback (most recent call last)
<ipython-input-4-30650cb58dc7> in <module>()
      7
      8 arima_forecaster = Prophet()
----> 9 arima_forecaster.fit_predict(fh=y_train.index, y=y_train, X=X_train)
     10 print(X_train)

3 frames
/usr/local/lib/python3.7/dist-packages/sktime/forecasting/base/adapters/_fbprophet.py in _merge_X(df, X)
    197     X.columns = X.columns.astype(str)
    198     if "ds" in X.columns:
--> 199         raise ValueError("Column name 'ds' is reserved in fbprophet")
    200     X.loc[:, "ds"] = X.index
    201     # df = df.merge(X, how="inner", on="ds", copy=False)

ValueError: Column name 'ds' is reserved in fbprophet

Expected behavior

to fit and predict without changing arguments so that it can fit_predict without error

Versions

System:
    python: 3.7.12 (default, Sep 10 2021, 00:21:48)  [GCC 7.5.0]
executable: /usr/bin/python3
   machine: Linux-5.4.104+-x86_64-with-Ubuntu-18.04-bionic
Python dependencies:
pip: 21.1.3
setuptools: 57.4.0
sklearn: 1.0.1
sktime: 0.8.1
statsmodels: 0.10.2
numpy: 1.19.5
scipy: 1.4.1
Cython: 0.29.24
pandas: 1.1.5
matplotlib: 3.2.2
joblib: 1.1.0
numba: 0.54.1
pmdarima: None
tsfresh: None

@IlyasMoutawwakil, are you positive that this is a side effect on the argument X?
That is, is the object X, after passing to the prophet estimator, differenf from when passed?
I would be surprised.
Why was this not captured by test_all_estimators/test_methods_have_no_side_effects?

ah, I can answer this myself: _make_args creates no X for forecasting.
So the test would not detect a side effect in X.

I've turned the lack of test coverage in an issue here:
https://github.com/alan-turing-institute/sktime/issues/1674

I'm pretty positive, here I created X_train dataframe with no ds column and was added to it after the call to fit.
https://colab.research.google.com/drive/1TtZJMLKIC2jJUPmWanbBAn9GobtCPJEZ?usp=sharing

Yes, I've observed the same before but forgot to raise the issue. Thanks for raising it now @IlyasMoutawwakil!

so basically we just have to add X = X.copy()? Is so, this should probably happen in the base class

@aiwalter I can't see how X = X.copy() would solve it, I guess all of the problem comes from the function _merge_X which modifies X (by adding ds to it) then merges it with df at lines 200-202 in _fbprophet.py :
X.loc[:, "ds"] = X.index
# df = df.merge(X, how="inner", on="ds", copy=False)
df = df.merge(X, how="inner", on="ds")
return df, X.drop(columns="ds")

a simple solution would be not adding ds to X and in the merging line df =  merge(X.rename({'index': 'ds'}, ...) that's if we're avoiding creating a local variable at all costs.

we also need to check whether the case that X already has a column named ds is covered properly.

so basically we just have to add X = X.copy()?

I think that would work, first thing in _fit and _predict.
Seems a simple fix, hence good first issue.

@kejsitake offered to work on this, thanks!

we also need to check whether the case that X already has a column named ds is covered properly.

Hi! I am working on this bug and wanted to check if this is referring to the tests or if we should throw an error in the base class if the X already contains a column named ds.

I think neither - it is the prophet class that needs to be fixed.
None of the forecasters should behave differently with a column ds or without.
None of the forecasters should change argument X being passed to them.
So there are two things to fix:

high-priority, the side effect of the prophet forecaster on X - the argument should not be modified
lower-priority, writing a test that would catch this (this is issue #1674)


Example Setup MySQL

Hi, i need example for config mysql server  because i still get error
/usr/local/rvm/gems/ruby-2.5.0/gems/figaro-1.1.1/lib/figaro/application.rb:84:in non_string_configuration!' : WARNING: Use strings for Figaro configuration. false was converted to "false". (StructuredWarnings::StandardWarning)Access denied for user 'root'@'localhost' (using password: NO)Please provide the root password for your MySQL installation

I can take this.

here my example
`default: &default
adapter: mysql2
encoding: utf8
pool: 5
host: <%= ENV['localhost'] %>
username: <%= ENV['root'] %>
password: <%= ENV['mypassword'] %>
development:
<<: *default
database: peatio_development
test:
<<: *default
database: peatio_test
production:
<<: *default
url: <%= ENV['localhost'] %>
pool: 10
database: peatio_production`
.___. and still get error

Hello @endofthepain
This is not an error. It opens prompt for password. Tweak your config for appropriate passwords and logins.


False Positive - Findings in the Config File itself

Describe the bug
The tool flags the rule-set defining file (.toml file) as scannable and reports findings in it
To Reproduce
Steps to reproduce the behavior:

Run the tool setting --config=PATH to be a PATH inside the repository scanned.

Expected behavior
The tool should ignore the loaded .toml file used for the rule-set
Additional context
An alternative fix would be enabling us to flag a file or directory as not-to-scan
cc @zricethezav

Good call, merged https://github.com/zricethezav/gitleaks/pull/362 to address this


Remediation readme

Added readme and input files. Removed additional docx.

Thx Raja. Will merge this now.


ValueProvider.localTime() throws DateTimeException

The current implementation
return LocalTime.ofSecondOfDay(longNumber(0, secondsPerDay));
Throws a DateTimeException when longNumber(0, secondsPerDay) returns secondsPerDay, which is out of bounds.

Hi Tobias,
thank you very much for spotting the problem and providing the fix.


clean-css-cli does not work on Windows properly

If you are on the Windows platform and the CSS file you are trying to minify is on a different drive letter, e.g.: drive F: instead of the default drive C: and you attempt to run the cleancss command with an absolute path pointing to the input file (as well as an absolute path to the output file) then clean-css-cli is trying to import something from an invalid path, see:

A directory or file name on Windows cannot contain the colon ( : ) character!
This issue is originally surfaced here: https://github.com/tssajo/Minify/issues/51
This is a regression introduced in clean-css-cli.
clean-css 3.x.x worked in the same situation worked just fine.

In addition to the above: It also causes trouble if the PATH contains spaces. As you can see on the above screenshot, the original directory was "F:\Two Bad Mice..."
So both the colon character after F is causing an invalid PATH but also the space after Two is making the path trimmed early in "C:\WINDOWS\system32/F:/Two"
IMO the current working directory cannot just be concatenated with the source file's PATH at will. At least not on Windows.

@tssajo thanks for giving it a try - I'll try it locally on Windows and get back to you.

It's actually an API issue as well. Fix is coming!

I've just released 4.0.4 fixing handling spaces in paths, see ^ issue in API. Could you reinstall clean-css-cli and give it another try? It works fine on Windows 10 and Node 7 for me.

@jakubpawlowicz I do not know why you closed this when it is definitely still broken! And I cannot even re-open... :( Please re-open this issue! Thanks!
The "spaces in path" issue was a 2nd issue, that one you fixed and that's great.
But the main issue was not with the spaces in path! The main issue occurs when you try to use cleancss on a file which is on a different driveletter than your current working directory.
For example:
You are here: C:\Windows\system32
and you issue the following command:
cleancss --skip-rebase -o "D:\Two Bad Mice\style.min.css" "D:\Two Bad Mice\style.css"
It still does not work! Please look at the result:

See how you incorrectly concatenate the path of the current working directory with the specified file's path? This is the problem:
C:/Windows/system32/D:/Two Bad Mice/style.css
Why the concatenation??? The file is NOT under the current working directory, it is under a different driveletter ( under drive D: )
BTW, this concatenated path is invalid on Windows, because a directory path cannot have a colon character in it.
This is the issue I originally reported here. Not handling spaces in paths properly was just an additional issue (maybe I should have reported that as a separate issue).

@tssajo I closed it because I tested the new version locally and it worked fine, see my local output on Node 7 and Win 10.

If it's not fixed we can reopen this issue, however, I don't see it happening anymore.

Oh, scratch that. I can see it still happens when rebasing is used via --output flag.

@jakubpawlowicz Thanks for your answer!
So it was the output ( -o ) flag then. Good to know!
I'll try your updated version of clean-css tomorrow. Thanks, again!

So this should be fixed in 4.0.5. Works fine locally with -o option.

I can confirm that the issue has been fixed with version 4.0.5
Thank you!

That's great 👍

Olá @jakubpawlowicz , I'm having problems with clean-css-li 4.1.11, use Windows 10 64 bits and my files .css not be minified. You said that the problem was fixed in version 4.0.5, but it continues. The error that occurs is the same one mentioned by tssajo. You can you help me?


Issue 1119: Added a yarn example

Fixes strongbox/strongbox#1119.

Thanks for the pull request! :)


Ember inspector erroring in factoryFor with model:mirage/models

The Ember Inspector crashes when using 0.2.0-beta.3.
Ember Inspector has errored.
This is likely a bug in the inspector itself.
You can report bugs at https://github.com/emberjs/ember-inspector.
Error message: injectedFactory.reopenClass is not a function
Stack trace: TypeError: injectedFactory.reopenClass is not a function
    at factoryFor (http://localhost:4200/assets/vendor-496907f2e898fc4eb360b50ce464b17c.js:12059:23)
    at Object.Container.lookupFactory (http://localhost:4200/assets/vendor-496907f2e898fc4eb360b50ce464b17c.js:11937:14)
    at exports.default._emberRuntimeSystemObject.default.extend._nameToClass (http://localhost:4200/assets/vendor-496907f2e898fc4eb360b50ce464b17c.js:16659:31)
    at http://localhost:4200/assets/vendor-496907f2e898fc4eb360b50ce464b17c.js:16856:25
    at Array.map (native)
    at exports.default._emberRuntimeSystemObject.default.extend.getModelTypes (http://localhost:4200/assets/vendor-496907f2e898fc4eb360b50ce464b17c.js:16854:56)
    at exports.default._emberRuntimeSystemObject.default.extend.watchModelTypes (http://localhost:4200/assets/vendor-496907f2e898fc4eb360b50ce464b17c.js:16634:29)
    at getModelTypes (<anonymous>:844:55)
    at Object.apply (http://localhost:4200/assets/vendor-496907f2e898fc4eb360b50ce464b17c.js:34201:18)
    at Object.sendEvent (http://localhost:4200/assets/vendor-496907f2e898fc4eb360b50ce464b17c.js:27753:28)

You can reproduce this by pulling down https://github.com/code-corps/code-corps-ember (you'll also need the API as index is served over redis: https://github.com/code-corps/code-corps-api). I get this error on any route I visit.
Let me know if you have trouble pulling down my project to reproduce.

With redis, the api and the Ember app, there are a lot of moving pieces here. Have you tried reproducing the bug in a fresh Ember app?

@samselikoff I haven't tried reproducing yet. I'm on OSX with Chrome.
I'm updating to beta4 and I'll see if anything changes.

@samselikoff was able to reproduce.  Definitely weird.

You'll need to click into the "data" tab to see the error, I think.

Bizarre - and thank you so much for tracking this down. I'll prioritize it against my current work.

Closing due to inactivity, perhaps this has been fixed with later updates in inspector & mirage? Please reopen if it's still an issue.

@samselikoff to be honest I had not checked since I was waiting on triage here.

Ok will re-look into this after I finish cleaning through the rest of the issues.

No worries! I think it's probably as simple as using the repo I created to reproduce and upping to latest.

Just tried to repo in latest versions of things and it seems to be fixed 👍


docs (documentation-website): Adding Auto-Translation information to CONTRIBUTING.md and page

The Pull Request is ready

[x] fixes #603
[x] all actions are passing
[x] only fixes a single issue

Overview
Update CONTRIBUTING.md and contributing page to include auto translation.
Documentation

[x] all documentation is in correct english
[x] the documentation explains used words, that are not common
[x] there are no abbreviations used

Summary by CodeRabbit

Documentation

Added a new section on language testing with auto-rebuild functionality in the contributing guidelines.
Updated the translation section in the documentation with new setup instructions, path information, and a YouTube tutorial link.
Modified the layout of the contributing page on the documentation website to include translation-related content and repositioned the YouTube tutorial for better accessibility.

Pretty good already, thank you!


Condition only functions are not listed

Functions such as Exists(...) and HasTrailingSlash(...) are not listed.
They seem to not require class prefix as opposed to property functions.
If they are not property functions, what category are they?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 82a1a083-bea0-e53e-dc9e-78f201ac1314
Version Independent ID: 904dae68-65cb-ec55-2fb3-1075ceaf6f1c
Content: Property Functions - Visual Studio
Content Source: docs/msbuild/property-functions.md
Product: visual-studio-windows
Technology: msbuild
GitHub Login: @ghogen
Microsoft Alias: ghogen

@Nirmal4G -- Nirmal, thank you for your feedback; we appreciate it. To make sure we have all the information needed to triage your issue, please provide more context around your general task.

In MSBuild, the Condition='' attribute has some built-in functions that are not necessarily the same as property/item functions. Those are what I listed above.
These are not listed anywhere in this page. They should be listed as Condition only functions and/or redirect to the conditions page.

@Nirmal4G -- Nirmal, thank you for clarifying.
@ghogen -- Gordon, please look into this issue.

@Nirmal4G These are listed here: https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuild-conditions?view=vs-2019

@ghogen Thanks. I could not find it. Only property and item functions were listed in their own pages. No reference to conditional functions.

Leaving open - this is still a discoverability issue.  Possible solutions include adding a link or moving the conditional functions into their own topic.

redirect to the conditions page

Could be one solution. on each of those pages


Make small typo fixes and make a sentence wording clearer in README.

Thanks for the wording clarifications @davidxia


[JUW-1622] Remove faulty comma.

The previous PR (#3) was actually broken.
@juwai/frontend: I’d need your help for two quick thumbs here. Thanks!

:+1:

:monkey_face:

Thanks! Merging.


HostWindows can't leave screen on linux

On Linux HostWindows behave differently than normal Windows. You can't move them outside of screen boundary which makes it hard to place them back to the main window.

It would be nice to be able to move them partially out of bounds like normal windows:

Can you try this if it has any effect:
<Style Selector="idc|HostWindow" xmlns:idc="clr-namespace:Dock.Avalonia.Controls;assembly=Dock.Avalonia">
  <Setter Property="HasSystemDecorations" Value="True" />
</Style>

Default:
https://github.com/wieslawsoltes/Dock/blob/04869d0d263abbb82617cd55ad185b36bead6ada/src/Dock.Avalonia.Themes.Default/HostWindow.xaml#L11

Not sure if this also has effect:
https://github.com/wieslawsoltes/Dock/blob/cb9c7f41e7e04de053851885741e6a57e1383a4f/src/Dock.Avalonia/Controls/HostWindow.cs#L350

Can you try this if it has any effect:
<Style Selector="idc|HostWindow" xmlns:idc="clr-namespace:Dock.Avalonia.Controls;assembly=Dock.Avalonia">
  <Setter Property="HasSystemDecorations" Value="True" />
</Style>

Default:
https://github.com/wieslawsoltes/Dock/blob/04869d0d263abbb82617cd55ad185b36bead6ada/src/Dock.Avalonia.Themes.Default/HostWindow.xaml#L11

Using this it is possible to move hostwindows out of bounds but only if you move it using the native decorations border.
I think the problem is somewhere here:
https://github.com/wieslawsoltes/Dock/blob/04869d0d263abbb82617cd55ad185b36bead6ada/src/Dock.Avalonia/Controls/HostWindow.cs#L283-L292
I will try some things later

It's all wayland

@HendrikMennen https://github.com/wieslawsoltes/Dock/pull/207


Eu acho que trocaram a URL da extensão SlimeRead

Source information
SlimeRead 1.4.14
Source language
Português Brasil - PT-BR
Source new URL
https://slimeread.com/
Other details
No response
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[x] I have written a short but informative title.
[x] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.


'Could not open the file nand.bin'

Notes to keep in mind:

Latest version of Windows, 7z and HiyaCFW installed
I'm new to all of this

Alright, so.
I successfully download HiyaCFW. I open it up, no problems there. Click the three dots, and open the nand.bin file. Now its in the thin rectangular box, and I press 'START'.
Then a pop-up tells me to find an SD card path / output folder, etc. I click Ok, and brings me to another pop-up so I can select a folder. So I select the SD card, and...
A pop-up saying status appears:
Checking NAND file...
ERROR: Could not open the file nand.bin
The only other thing I can do is close the pop-up, or minimize it. Thats it.
I've tried making other backup files (none of which worked), reinstalling the program, but none of it seems to be working.
I'm at a loss regarding what to do. Please help.
Thanks,
A Concerned Citizen

What's the message in the black window?

Hi! Thank you for responding.
I did just what you said, and the same error keeps appearing.
Checking NAND file...
ERROR: Could not open the file nand.bin
In the console, it says:
[Errno 22] Invalid argument
Nothing else appears.

Have you tried running the helper in a different computer?

Might be one (or multiple) of the following;
The drive the nand.bin file is stored on is dead or dying. If this is the SD card, reformat the card to FAT32 using Disk Management or SD Formatter and use h2testw to test the SD card for errors. If there are any, re-dump the NAND with a new card.
You are running the Helper in a temporary environment, let's say running it directly from the .zip archive and/or by opening it when downloading (It doesn't get saved to Downloads, rather some temporary cache folder which gets cleared when not in use)
Or the drive the Helper and/or nand.bin file is compressed and/or encrypted by Windows. The files and folders would be colored blue if this were the case.
Seeing this isn't closed by now implies it might be solved privately, but in the off chance it is not this is my two cents.

No follow up from reporter, closing ticket


Bug 1989741: Increase Lease Duration and Renew Deadline

to avoid leader elections timeout on OCP BareMetal clusters as was suggested by
operator-framework/operator-sdk#1813
Signed-off-by: Mohamed Mahmoud<EMAIL_ADDRESS>

lgtm

chnages didn't help with the issue reported in the above Bug


problem with duplicate package name

I typically put my demo classes n Package Z.*
in module.xml is rather similar:
src
<Resource Name="Z.PKG"/>
using the same package name in different projects caused this during installation:

ERROR #5001: Resource 'Z.PKG' is already defined as part of module 'remote-server-control'; cannot also be listed in module 'obj-dump'

is it a bug?
how can I have the same package in more than 1 project ?
in that simple case, I just renamed 1 of it.
but that's not optimal as had to change all descriptions and comments.
pls. advise !

That’s not the issue of zpm, just objectscript. In short you have to use different package names for every your different project
Look here, Evgeny already raised this
https://community.intersystems.com/post/objectscript-package-manager-naming-convention

Thanks for your quick reply.
it's acceptable for new code in new projects
for existing examples it would mean to rewrite & test a lot of code and the related documentation.
BTW is there an option to have ?

" <Resource Name=""Z.democlass.CLS.""/> "

I tried (probaly missimg something)  but i seemed not to be pleased by **Z.**name.CLS

Sure, you can define exact class, if you like
Zpm, when package module, it exports everything as described, so, if you say Z.pkg it will package all the class in the package, same for uninstalling

Thanks. That's a chance to keep my puzzles together in a common basket !!
GREAT!


customActionTrigger() throwing Cross-Origin Request error

Hi! First of all, I want to thank you so much for this awesome project. My bot should start the conversation so I've enabled customActionTrigger() from script.js and changed the action_name const with my custom action. Then, when I try ChatbotWidget it throws the following cross-origin problem:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://localhost:5055/webhook/. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
Error from bot end:  error
I've used rasa run -m models --enable-api --cors "*" --debug to run the server following the instructions so I don't know why it doesn't allow the request since I use the --cors flag

@joancipria  you need to start the action server using the below command

rasa run actions --cors "*"

Oh, I forgot the actions server! Thank you so much, it worked!


misc: use micron and dbu converters from odb

It looks to me like the antenna checker needs a wholesale conversion to DBU, because I don't see why it's using doubles right now.

@luis201420 is in the process of rewriting it so hopefully this will be better.


[FEATURE REQUEST] ISQLServerDataRecord should allow custom ordering

Is your feature request related to a problem? If so, please give a short summary of the problem and how the feature would resolve it
Implementations of ISQLServerDataRecord need to respect the order of columns in the server-side definition of the corresponding Table Valued Parameter (TVP), i.e ISQLServerDataRecord.getColumnMetaData(1) needs to return the SQLServerMetaData for the first column as per the definition of the TVP, input 2 needs to return the meta data for the second column and so forth.
This is inconvenient in the case of data which does not have this order naturally since it needs to be re-ordered.
Describe the preferred solution
Provide a possibility to dissociate order of the record and column order on the SQL side. For instance, through a mapping, similarly to what is done with SqlServerBulkCopy#addColumnMapping.
Maybe the driver could simply use  name columnName attribute of the SQLServerMetaData returned by ISQLServerDataRecord#getColumnMetaData to generate TVP insertion statements like :
INSERT INTO @p3 (col_name_1, col_name,2, ...) VALUES (val_1, val_2, ...)

instead of what it currently generates:
INSERT INTO @p3 VALUES (val_1, val_2, ...)

Best regards,
David

Thanks for submitting the feature request. We'll keep it in mind for potential future work.
Regards,
David


Remove Android wallet link

Sunsets Firo Android wallet v0.1.23.

Will be keeping download.optionmob1 because the other two would be left hanging otherwise.


Error [@RNC/AsyncStorage]: NativeModule: AsyncStorage is null

Current behaviour
Sorry, i am new in react native, i just want to run the simple apps using a device but it turns to error. it working when i run in browser that have asyncstorage
Repro steps
Steps I took are as follows:

npm cache clean --force
npm start

Environment

Async Storage version: 1.10.0
React-Native version: 0.61.4
Platform tested: Android (not simulator)
Expo version: 36.0.0

I see you're using Expo, so unfortunately, you won't be able to use this package, unless you eject (which I don't recommend for now, since you're new to RN). Keep on using AsyncStorage from Expo and don't mind warning for now.

How to run the program if there still have an error. It works when use web browser but i want to use maps so it must run on device but the error haunted me. Please help me. @Krizzu

Again, if you're using Expo, then you need to remove dependency on this Async Storage (by removing its name in your package.json and running npm install/yarn again) and use Async Storage from the core

wowww its working thank you! @Krizzu


remove content length

Hey Gil, this removes the content length requirement and with it the need to get the metadata for each object.
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Effi

resolved in https://github.com/SparkTC/stocator/pull/91


Three cherrypicks

Add tf.compat.v1.all_v2_summary_ops() for TF 2.0 legacy graph users
Leave GPU options untouched on CPU only setups
Undo failed attempts at including kissfft

Replaced by https://github.com/tensorflow/tensorflow/pull/28188


Notification about my own actions?

I don't think I need a notification about my own comments/replies to my own posts/tips?

I think the best would be to solve it on the backend side @kenodressel


Keep focus when data changes on a changed element

Currently behavior is inconsistent - focus might be lost from time to time, when you edit data in an object, if rules are run in the background. We need to make it more consistent for a smoother user experience.

This caused unrelated issues, so I'm reverting this changes


[EventRequest] Page 95 “Sales Quote Subform”, UpdateEditableOnRow [Local]

Please add a new publisher event OnAfterUpdateEditableRows as shown in the picture below in the function UpdateEditableOnRow in page 95

Please add the corresponding Integration Event In the bottom of the page soruce code

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


[FEATURE REQUEST] Add course metrics summary to course page

What feature would you like to see added?
I'd like to see metrics averages for Rating, Difficulty, Workload, and Reviews on a course detail page. For instance, looking at https://www.omscentral.com/courses/statistical-modeling-and-regression-analysis/reviews, if I wanted to know these values I could scroll down through the reviews and make an estimate or go back to https://www.omscentral.com/ and search for the course to get exact figures
Additional context
Course Page without metrics

Homepage with metrics

Fixed here thanks!


Honk mech recipe & stat buff

About the PR

Honker mech:

faster movement speed (still slower than Ripley)
removed structural damage and made dps slightly higher than ripley
recipe made much cheaper

Why / Balance

I found the Honker unusually absent from rounds despite being one of two mechs and no longer locked behind T3.
Testing confirmed outdated stats: unusually low speed compared to Ripley, slow yet high damaging melee with structural component, and being extremely expensive to fabricate. This may have to do with mechs in general being undermaintained and the Honker formerly being a T3 tech.

increased the speed to be approximately 75% of sprint speed (assuming 4.5 base sprint speed, 3.38 is equivalent to 75%). For comparison, the Ripley is faster at 3.6 sprint speed (equivalent to 80%) but much less armoured with 75% damage transfer.

decreased damage per swing from 25 to 16 and removed structrual damage, increase swing rate from 0.75 to 1 - should feel more consistent in combat

decreased the recipe cost to what seems more in-line with a T2 tech - many parts no longer require a full stack of steel each, and bananium cost is decreased as it is typically ignored by salvage.

Please keep in mind the Honker mech has a 50% damage transfer to the pilot (ignoring other stats). This may need to be adjusted for balance.
Changes overall are to increase accessibility of Honker mechs and improve interest in mech code.
Technical details

yaml changes only:

mechs.yml
mech_parts.yml

Weirdly 100 bananium in yaml material seems to be equivalent to 2/3 (0.66) bananium in-game, I haven't been able to explain why
Media

[ ] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

N/A
Changelog

:cl: Damn Feds

tweak: Honker mech is much cheaper to produce, hits slightly harder and faster overall. Honk!

Honk was locked behind tier 3? as far as I remember it's always been tier 2 civilian.
But also, I would recommend reverting the movement speed and instead adding the airtight component that the HAMTR and VIM have. The Honk is a combat mech after all.

Honk was locked behind tier 3? as far as I remember it's always been tier 2 civilian.
But also, I would recommend reverting the movement speed and instead adding the airtight component that the HAMTR and VIM have. The Honk is a combat mech after all, it doesn't need movement speed when it has ranged weapons.
(disclaimer: mech ranged weapons will never happen)

Honk horn ranged weapon :trollface:
The move speed was really slow so I'd rather keep it at that for now. The airtightness is a bit weird as I recall breathing issues for crew, as well not wanting it to go up against nukies (it's a civilian clown mech; more armoured but not more combat-worthy than a ripley exosuit)

Honk horn ranged weapon :trollface:

the horn is a glorified noisemaker right now

The airtightness is a bit weird as I recall breathing issues for crew

valid I'm pretty sure airtightness is buggy on humanoids

as well not wanting it to go up against nukies (it's a civilian clown mech; more armoured but not more combat-worthy than a ripley exosuit)

the HONK is only in civilian because clown is in service. It's designed to be a powerful combat mech with clown themed equipment in ss13. Plus, nukies should get used to fighting combat mechs anyway.

airtight is fine theres proper air filtering now

airtight is fine theres proper air filtering now

god I love hiatuses

Closed due to feature freeze May 10th-June 14th. Comment to have it reopen after this.

Reopen

The airtightness is a bit weird as I recall breathing issues for crew, as well not wanting it to go up against nukies

Now that nukies don’t have fire axe prying, spacing is much less prevalent. (Plus an emergency EVA can be worn while piloting it, negating the lack of air tightness anyway) and like delta said, crew breathing through airtight is good now

I'm a bit put off at the honker construction eating clown shoes, clown mask and needing to be 'honked' by a bike horn
I might add a clown costume crate idk

This is a buff to a feature that's basically barely functional to begin with (mechs,) and is probably only going to serve to mess up balance, especially when factoring in the lack of the all of the combat downsides they had from SS13.
Thank you for your contribution, but we're going to need more feature-complete mechs before doing this.