Support for Multiple Kibana Services in Compose

I have docker running in AWS and I have been using the official from Docker Hub until version 5.6.1 which I am in the middle of updating to. I need to run Multiple Kibana's to deal with Instance specific .kibana index's. I know xpack was added to this kibana and I am running these against My Elastic Cloud which does have xpack "b7be70" cluster ID.
`version: "3"
services:
kibanatest1:
image: docker.elastic.co/kibana/kibana:5.6.1
container_name: test
deploy:
restart_policy:
condition: on-failure
delay: 5s
max_attempts: 3
window: 120s
volumes:
- ./plugins/kibana-time-plugin:/usr/share/kibana/plugins/kibana-time-plugin:rw
environment:
ELASTICSEARCH_URL: https://......
ELASTICSEARCH_USERNAME: ......
ELASTICSEARCH_PASSWORD: .......
KIBANA_INDEX: .kibana-1
SERVER_DEFAULTROUTE: /app/kibana#/dashboard/7bdc16b0-702d-11e7-88dc-0d54ae3f1f7e?embed=true
ports:
- "9999:5601"
kibanatest2:
image: docker.elastic.co/kibana/kibana:5.6.1
container_name: hvms-bi
deploy:
restart_policy:
condition: on-failure
delay: 5s
max_attempts: 3
window: 120s
volumes:
- ./plugins/kibana-time-plugin:/usr/share/kibana/plugins/kibana-time-plugin:rw
environment:
ELASTICSEARCH_URL: https://......
ELASTICSEARCH_USERNAME: ......
ELASTICSEARCH_PASSWORD: .......
KIBANA_INDEX: .kibana-2
SERVER_DEFAULTROUTE: /app/kibana#/dashboard/7bdc16b0-702d-11e7-88dc-0d54ae3f1f7e?embed=true
ports:
- "10001:5601"`
For some reason the xpack will only load successfully on the 1st service. On the kibanatest2 xpack will not load and results in an error on the login screen saying that "Login is currently disabled because the license could not be determined. Please check that Elasticsearch has the X-Pack plugin installed and is reachable, then refresh this page."
Probably due to the errors.
{"type":"log","@timestamp":"2017-09-26T03:16:28Z","tags":["info","optimize"],"pid":1,"message":"Optimization of bundles for graph, monitoring, ml, kibana, stateSessionStorageRedirect, timelion, login, logout and status_page complete in 206.84 seconds"} {"type":"log","@timestamp":"2017-09-26T03:16:29Z","tags":["status","plugin:kibana@5.6.1","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:29Z","tags":["status","plugin:elasticsearch@5.6.1","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:29Z","tags":["status","plugin:xpack_main@5.6.1","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:29Z","tags":["status","plugin:graph@5.6.1","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:29Z","tags":["status","plugin:monitoring@5.6.1","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:29Z","tags":["reporting","warning"],"pid":1,"message":"Generating a random key for xpack.reporting.encryptionKey. To prevent pending reports from failing on restart, please set xpack.reporting.encryptionKey in kibana.yml"} {"type":"log","@timestamp":"2017-09-26T03:16:29Z","tags":["status","plugin:reporting@5.6.1","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:30Z","tags":["info","elasticsearch"],"pid":1,"typeName":"graph-workspace","typeMapping":{"properties":{"description":{"type":"text"},"kibanaSavedObjectMeta":{"properties":{"searchSourceJSON":{"type":"text"}}},"numLinks":{"type":"integer"},"numVertices":{"type":"integer"},"title":{"type":"text"},"version":{"type":"integer"},"wsState":{"type":"text"}}},"message":"Adding mappings to kibana index for SavedObject type \"graph-workspace\""} {"type":"log","@timestamp":"2017-09-26T03:16:30Z","tags":["status","plugin:xpack_main@5.6.1","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [remote_transport_exception] [tiebreaker-0000000014][<IP_ADDRESS>:19672][indices:admin/mapping/put]","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2017-09-26T03:16:30Z","tags":["status","plugin:graph@5.6.1","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [remote_transport_exception] [tiebreaker-0000000014][<IP_ADDRESS>:19672][indices:admin/mapping/put]","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2017-09-26T03:16:30Z","tags":["status","plugin:reporting@5.6.1","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [remote_transport_exception] [tiebreaker-0000000014][<IP_ADDRESS>:19672][indices:admin/mapping/put]","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2017-09-26T03:16:30Z","tags":["status","plugin:elasticsearch@5.6.1","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - [remote_transport_exception] [tiebreaker-0000000014][<IP_ADDRESS>:19672][indices:admin/mapping/put]","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2017-09-26T03:16:33Z","tags":["info","elasticsearch"],"pid":1,"typeName":"graph-workspace","typeMapping":{"properties":{"description":{"type":"text"},"kibanaSavedObjectMeta":{"properties":{"searchSourceJSON":{"type":"text"}}},"numLinks":{"type":"integer"},"numVertices":{"type":"integer"},"title":{"type":"text"},"version":{"type":"integer"},"wsState":{"type":"text"}}},"message":"Adding mappings to kibana index for SavedObject type \"graph-workspace\""} {"type":"log","@timestamp":"2017-09-26T03:16:37Z","tags":["info","elasticsearch"],"pid":1,"typeName":"graph-workspace","typeMapping":{"properties":{"description":{"type":"text"},"kibanaSavedObjectMeta":{"properties":{"searchSourceJSON":{"type":"text"}}},"numLinks":{"type":"integer"},"numVertices":{"type":"integer"},"title":{"type":"text"},"version":{"type":"integer"},"wsState":{"type":"text"}}},"message":"Adding mappings to kibana index for SavedObject type \"graph-workspace\""} {"type":"log","@timestamp":"2017-09-26T03:16:40Z","tags":["info","elasticsearch"],"pid":1,"typeName":"graph-workspace","typeMapping":{"properties":{"description":{"type":"text"},"kibanaSavedObjectMeta":{"properties":{"searchSourceJSON":{"type":"text"}}},"numLinks":{"type":"integer"},"numVertices":{"type":"integer"},"title":{"type":"text"},"version":{"type":"integer"},"wsState":{"type":"text"}}},"message":"Adding mappings to kibana index for SavedObject type \"graph-workspace\""} {"type":"log","@timestamp":"2017-09-26T03:16:42Z","tags":["status","plugin:security@5.6.1","error"],"pid":1,"state":"red","message":"Status changed from uninitialized to red - [remote_transport_exception] [tiebreaker-0000000014][<IP_ADDRESS>:19672][indices:admin/mapping/put]","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:42Z","tags":["security","warning"],"pid":1,"message":"Generating a random key for xpack.security.encryptionKey. To prevent sessions from being invalidated on restart, please set xpack.security.encryptionKey in kibana.yml"} {"type":"log","@timestamp":"2017-09-26T03:16:42Z","tags":["security","warning"],"pid":1,"message":"Session cookies will be transmitted over insecure connections. This is not recommended."} {"type":"log","@timestamp":"2017-09-26T03:16:42Z","tags":["status","plugin:searchprofiler@5.6.1","error"],"pid":1,"state":"red","message":"Status changed from uninitialized to red - [remote_transport_exception] [tiebreaker-0000000014][<IP_ADDRESS>:19672][indices:admin/mapping/put]","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:42Z","tags":["status","plugin:ml@5.6.1","error"],"pid":1,"state":"red","message":"Status changed from uninitialized to red - [remote_transport_exception] [tiebreaker-0000000014][<IP_ADDRESS>:19672][indices:admin/mapping/put]","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:43Z","tags":["status","plugin:ml@5.6.1","info"],"pid":1,"state":"yellow","message":"Status changed from red to yellow - Waiting for Elasticsearch","prevState":"red","prevMsg":"[remote_transport_exception] [tiebreaker-0000000014][<IP_ADDRESS>:19672][indices:admin/mapping/put]"} {"type":"log","@timestamp":"2017-09-26T03:16:43Z","tags":["status","plugin:tilemap@5.6.1","error"],"pid":1,"state":"red","message":"Status changed from uninitialized to red - [remote_transport_exception] [tiebreaker-0000000014][<IP_ADDRESS>:19672][indices:admin/mapping/put]","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:43Z","tags":["status","plugin:watcher@5.6.1","error"],"pid":1,"state":"red","message":"Status changed from uninitialized to red - [remote_transport_exception] [tiebreaker-0000000014][<IP_ADDRESS>:19672][indices:admin/mapping/put]","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:43Z","tags":["status","plugin:grokdebugger@5.6.1","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:43Z","tags":["status","plugin:upgrade@5.6.1","error"],"pid":1,"state":"red","message":"Status changed from uninitialized to red - [remote_transport_exception] [tiebreaker-0000000014][<IP_ADDRESS>:19672][indices:admin/mapping/put]","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:43Z","tags":["status","plugin:ml@5.6.1","info"],"pid":1,"state":"green","message":"Status changed from yellow to green - Ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"log","@timestamp":"2017-09-26T03:16:43Z","tags":["status","plugin:console@5.6.1","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:43Z","tags":["status","plugin:metrics@5.6.1","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:43Z","tags":["status","plugin:timelion@5.6.1","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"} {"type":"log","@timestamp":"2017-09-26T03:16:43Z","tags":["listening","info"],"pid":1,"message":"Server running at http://0:5601"} {"type":"log","@timestamp":"2017-09-26T03:16:43Z","tags":["status","ui settings","error"],"pid":1,"state":"red","message":"Status changed from uninitialized to red - Elasticsearch plugin is red","prevState":"uninitialized","prevMsg":"uninitialized"}
On kibanatest1 I do not receive these errors XPack loads fine and I can login with out issues.
I've even tried removing xpack
command: [ "/bin/bash", "-c", "/usr/share/kibana/bin/kibana-plugin remove x-pack; /usr/local/bin/kibana-docker" ]
but I get a error
<EMAIL_ADDRESS>| [remote_transport_exception] [tiebreaker-0000000014][<IP_ADDRESS>:19672][indices:admin/mapping/put]

This is not specific to docker-compose i get the same results when creating the containers using individual docker run commands.

Is this even Docker related? Have you tried a standalone Kibana instances? They will need to have X-Pack installed.
I might be reading this wrong, but tiebreaker-0000000014 sounds to me like you are trying to talk to the tiebreaker node instead of one of your Elasticsearch nodes. You probably have a setup with 2AZs and there is a tiebreaker to ensure that there is a majority, but you cannot read or write to that node.

Is this even Docker related? Have you tried a standalone Kibana instances? It will need to have X-Pack installed.

All my other instances are Docker Images 5.4.2 from your previous DockerHub official location. These do not have the Xpack Plugin and as working just fine against the upgraded ElacticCloud instance "b7be70" cluster ID.

I might be reading this wrong, but tiebreaker-0000000014 sounds to me like you are trying to talk to the tiebreaker node instead of one of your Elasticsearch nodes. You probably have a setup with 2AZs and there is a tiebreaker to ensure that there is a majority, but you cannot read or write to that node.

If the 5.6.1 Docker Contianer is talking to the tiebreaker node this is an issue on your end because I am using the same ELASTICSEARCH_URL: https:// link that is provided on the https://cloud.elastic.co/#clusters/us-west-2 endpoint and is used by all my other docker containers, as well as kibanatest1 which is working in this example. It's only kibanatest2 that is resulting in the issues which makes no sense since the only difference is that it is using a different Port(10001) and KIBANA_INDEX: it's the exact same image and ELASTICSEARCH_ Environment variables.

I believe I figured it out but I don't know where to go from here.
I found that it has to do with the KIBANA_INDEX: if I point my index to .kibana-hvms on my cluster it works fine with the docker 5.6.1 w/XPACK installed but if I point to .kibana-hvms-live it doesn't.  My .kibana index in the cluster also works with the docker 5.6.1 w/XPACK installed.

Yep I figured it out.
It had to do with the mapping in the .kibana indexes I created like this.
POST /_reindex {   "source": {     "index": ".kibana-hvms"   },   "dest": {     "index": ".kibana-hvms-test"   } }
I was creating a copy of the index I had already setup and then making changes to those dashboards for the new Kibana instance.
What happened was the above only took certain mappings from the source. There were some missing in the dest that caused this issue.
So the resolution was to copy the mapping from the source that were missing in dest.
put .kibana-hvms-test/_mapping/graph-workspace     {         "properties": {           "description": {             "type": "text"           },           "kibanaSavedObjectMeta": {             "properties": {               "searchSourceJSON": {                 "type": "text"               }             }           },           "numLinks": {             "type": "integer"           },           "numVertices": {             "type": "integer"           },           "title": {             "type": "text"           },           "version": {             "type": "long"           },           "wsState": {             "type": "text"           }         }       } put .kibana-hvms-test/_mapping/url {         "properties": {           "accessCount": {             "type": "long"           },           "accessDate": {             "type": "date"           },           "createDate": {             "type": "date"           },           "url": {             "type": "text",             "fields": {               "keyword": {                 "type": "keyword",                 "ignore_above": 256               }             }           }         } } put .kibana-hvms-test/_mapping/timelion-sheet {         "properties": {           "description": {             "type": "text"           },           "hits": {             "type": "long"           },           "kibanaSavedObjectMeta": {             "properties": {               "searchSourceJSON": {                 "type": "text"               }             }           },           "timelion_chart_height": {             "type": "integer"           },           "timelion_columns": {             "type": "integer"           },           "timelion_interval": {             "type": "text"           },           "timelion_other_interval": {             "type": "text"           },           "timelion_rows": {             "type": "integer"           },           "timelion_sheet": {             "type": "text"           },           "title": {             "type": "text"           },           "version": {             "type": "long"           }         } } put .kibana-hvms-test/_mapping/index-pattern {         "properties": {           "intervalName": {             "type": "text"           },           "sourceFilters": {             "type": "text"           }         }       }
I am not sure if this was a result of the Kibana Docker starting a trial for the xpack items in Platinum.
Or if the post _reindex has issues with bringing the mapping with it from the Source to the Dest.
This can be closed.

Glad you figured it out and thanks for reporting back :)


More LaTeX docstring formatting + fix typo for :SecondOrder

@glwagner so in the docs in a few places there were terms like R₁₀₀ * Θ or R₀₁₀ * Sᴬ while from what I understand they should be R₀₁₀ * Θ and R₁₀₀ * Sᴬ, since the first subscript of R refers to S and second to Θ. I fixed them. But I'm wondering if the mistakes are in the code as well...

@glwagner so in the docs in a few places there were terms like R₁₀₀ * Θ or R₀₁₀ * Sᴬ while from what I understand they should be R₀₁₀ * Θ and R₁₀₀ * Sᴬ, since the first subscript of R refers to S and second to Θ. I fixed them. But I'm wondering if the mistakes are in the code as well...

From what I see the code is ok.

Another question: is Θ expected in degrees C or degrees K?

Another question: is Θ expected in degrees C or degrees K?

I believe C

@glwagner so in the docs in a few places there were terms like R₁₀₀ * Θ or R₀₁₀ * Sᴬ while from what I understand they should be R₀₁₀ * Θ and R₁₀₀ * Sᴬ, since the first subscript of R refers to S and second to Θ. I fixed them. But I'm wondering if the mistakes are in the code as well...

From what I see the code is ok.

Oh! I can't remember the system but yes, there is a system defined in the Roquet paper and we should follow that


Search results title and search button problem

When I search for an item I get a list of results
The only indication about the search parameters is the still filled in search field itself
My problem was, that sometimes I search for something new after a search, and the search button itself does not react on first clicking, because it is still active with closing the field with the search item. Then I am never sure, if the results belong to the previous or the actual search.
I would wish for 2 adaptations:

please add a title row above the  search results with the search terms for the results
please make the search button technically independent of the search term field so they dont interact

OPTIONAL: Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem (drag-and-drop the image directly here).
Desktop (please complete the following information):

OS: Windows 10 Pro N, 1903 - 18362.418

Browser Google Chrome, 78.0.3904.87

Version Knora App, 1.6.2

Additional context
Add any other context about the problem here.

The same problem I have with advanced search: When I navigate e.g. to the help page and back: The results are still displayed, but the search parameters are nowhere to be found again. If written as plain text as a title, this would help a lot.

Same problem with expert search: Titel with general Information to the search itself should be visible

this issue has been moved to YouTrack: DSP-310


Pub/Sub Documentation warnings

We get the following warnings when generating the documentation. All of them look to be due to use of a generic templating syntax that needs to be escaped. For example, consider the following documentation:
# @param name [String]
#   The data source in the form:
#   +projects/{project_id}/dataSources/{data_source_id}+
The text "{project_id}" is a YARD directive. To be valid YARD documentation it needs to be escaped, as "\{project_id}".

Here are the warnings:
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':290: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':290: Cannot resolve link to topic from text:
	...{topic}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':290: Cannot resolve link to topic from text:
	...{topic}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':572: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':572: Cannot resolve link to topic from text:
	...{topic}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':653: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':431: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':431: Cannot resolve link to topic from text:
	...{topic}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':517: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':517: Cannot resolve link to topic from text:
	...{topic}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':462: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':389: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':389: Cannot resolve link to topic from text:
	...{topic}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':608: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/publisher_client.rb':687: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':685: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':685: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':936: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':936: Cannot resolve link to snap from text:
	...{snap}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':940: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':940: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':353: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':353: Cannot resolve link to subscription from text:
	...{subscription}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':353: Cannot resolve link to subscription from text:
	...{subscription}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':353: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':353: Cannot resolve link to topic from text:
	...{topic}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':1046: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':1046: Cannot resolve link to snap from text:
	...{snap}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':595: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':595: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':1186: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':465: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':465: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':875: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':540: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':630: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':630: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':825: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':825: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':730: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':730: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':1085: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':1085: Cannot resolve link to snap from text:
	...{snap}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':1141: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/subscriber_client.rb':1220: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/policy.rb':9: Cannot resolve link to emailid from text:
	...{emailid}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/policy.rb':9: Cannot resolve link to emailid from text:
	...{emailid}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/policy.rb':9: Cannot resolve link to emailid from text:
	...{emailid}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/policy.rb':15: Cannot resolve link to domain from text:
	...{domain}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/policy.rb':9: Cannot resolve link to emailid from text:
	...{emailid}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/policy.rb':9: Cannot resolve link to emailid from text:
	...{emailid}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/policy.rb':9: Cannot resolve link to emailid from text:
	...{emailid}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/policy.rb':15: Cannot resolve link to domain from text:
	...{domain}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to topic from text:
	...{topic}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to topic from text:
	...{topic}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to topic from text:
	...{topic}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to topic from text:
	...{topic}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to subscription from text:
	...{subscription}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to subscription from text:
	...{subscription}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to subscription from text:
	...{subscription}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to subscription from text:
	...{subscription}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':4: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':4: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':4: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':4: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':5: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':5: Cannot resolve link to snap from text:
	...{snap}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':5: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':5: Cannot resolve link to snap from text:
	...{snap}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':9: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':9: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':9: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':9: Cannot resolve link to sub from text:
	...{sub}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to snap from text:
	...{snap}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to snap from text:
	...{snap}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to snap from text:
	...{snap}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':2: Cannot resolve link to snap from text:
	...{snap}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':3: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':3: Cannot resolve link to snap from text:
	...{snap}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':3: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/pubsub/v1/pubsub.rb':3: Cannot resolve link to snap from text:
	...{snap}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/iam_policy.rb':3: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/iam_policy.rb':3: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/iam_policy.rb':3: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/iam_policy.rb':3: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/iam_policy.rb':3: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/iam/v1/iam_policy.rb':3: Cannot resolve link to project from text:
	...{project}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to year from text:
	...{year}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to month from text:
	...{month}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to day from text:
	...{day}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to hour from text:
	...{hour}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to min from text:
	...{min}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to sec from text:
	...{sec}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to frac_sec from text:
	...{frac_sec}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to year from text:
	...{year}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to month from text:
	...{month}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to day from text:
	...{day}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to hour from text:
	...{hour}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to min from text:
	...{min}...
[warn]: In file `lib/google/cloud/pubsub/v1/doc/google/protobuf/timestamp.rb':79: Cannot resolve link to sec from text:
	...{sec}...

Fixed by https://github.com/GoogleCloudPlatform/google-cloud-ruby/pull/2320


Fix AAD B2C cannot complete well know metadata acquisition through issuer.

Fix this well-known endpoint bug.

/azp run java - spring - tests

Tests passed so I will override the check-enforcer now.
/check-enforcer override

@ZhuXiaoBing-cn could you please create another PR to update the changelog of azure-spring-boot and azure-spring-boot-starter-aad-b2c.

@ZhuXiaoBing-cn could you please create another PR to update the changelog of azure-spring-boot and azure-spring-boot-starter-aad-b2c?

okay，I'm going to create it.

AAD B2C related changelog. #21428


adding contabo30.toml

Description
If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging to draft

[x] Only one toml is added in this PR
[x] The file being added is indeed a .toml file
[x] The toml being added is to the correct folder, and only to the correct folder
[x] The eth_hot_key and eth_cold_key are present

This PR has been automatically closed because it does not follow the correct procedure for updating the genesis file.
Not a namada-public-testnet-11 file

This PR has been automatically closed because it does not follow the correct procedure for updating the genesis file.
Not a namada-public-testnet-11 file

Please reopen for the correct testnet folder


Fix compatibility issues

Fixing issues mentioned by @piotr1212 in review for #793

/cc @piotr1212 @postwait
Piotr, you also mentioned that TCP Keepalive disabled for SSL connections, but I didn't find that in the code. Could you please elaborate?

https://github.com/graphite-project/carbon/blob/65b102ce761fa629b5769b3a06857e55bb93b265/lib/carbon/util.py#L50-L67
So if it is an SSL connection, the keepalive flags are not set. I don't see a particular reason why not to enable keepalive with SSL, maybe it is is implicitly set somewhere in twisted or I'm just missing some reason.

Ah, OK. But it's disabled explicitly, so, OK for now, I think


FR: Volvo Trucks Configurator Embed to website

Oct 11th: We still have some minor tweaks before we can provide an example for the embedding of VTNA, but attached is a similar file to use for testing - a pure html file with a few lines. This shows what you need to add to the page where you want the configurator to live.
It will look almost identical to how we already are doing it for VTG (global) - https://www.volvotrucks.co.uk/en-gb/tools/truck-builder.html#/en-gb
Nov 13th:
Below the zip file contains the build of the configurator for you to test with. It includes an HTML file which you can use as reference for how to link to the files. The configurator will render into an element with the id #configurator. It relies on its parent having a height of 100% so that it fits the full viewport.
Right now, there are a handful of CSS classes which are defined in the global scope – let me know if this causes styling conflicts on the development and Rapid Images team will try to scope them. If there’s any questions let’s take a short call.
VTNA Configurator.zip

@manuel-vara Please share discovery for Volvo Group's solution for their configurator. We'd like to repurpose the same code in a component block.

@manuel-vara Please go back to the global AEM team and repurpose what's being done for Volvo Trucks in EU with Configurator. Please advise next steps.

We will need to create a custom block enabling js framework apps.
FYI @cogniSyb

Agile Requirement
As a user, I want to configure a truck to my liking to see how it would look before making the purchase.
Description
Create a new custom block called "Truck Configurator" that allows editors to add a route to the HTML in a JS Framework (React/Angular) developed app page.
Acceptance Criteria

Communication throughout the sprint will be needed with the application development agency (Rapid Images) to make design adjustments.

Reopening and sending back to In Progress due to the two Major bugs logged
Bug - Major - iPhone - Volvo Truck Configurator - X close window button is out of view in the Compare models pop-up
https://github.com/Netcentric/vg-volvotrucks-us-rd/issues/311
Bug - Major - Mobile - Volvo Trucks Configurator - User is not able to scroll down in landscape view #312
https://github.com/Netcentric/vg-volvotrucks-us-rd/issues/312

confirmed as done as per the two bugs above


Investigate issue introduced by npm version bump

flagged by @PaulKinlan

https://github.com/breadboard-ai/breadboard/commit/5678fbd48bcbbccb10aa5ec6d8f51678cc07e9ec
https://github.com/breadboard-ai/breadboard/actions/runs/8105305518/job/22153432192#step:6:274

Ok. It's coming from the pack:install command which runs npm install -g $(npm pack)

running npm install -g $(npm pack) as a package script also produces the error. which makes me think this is actually an error introduced by NPM itself

interesting. haven't yet managed to confirm my hunch on the MRE https://github.com/Mearman/npm-pack-install-mre/actions/runs/8108916703

I have a fix. But I'm not happy as I haven't yet definitively determined the cause.


How can I search a column for specific data?

@sirshurf I'm not sure if this is something that the Google Spreadsheets API provides. If you find anything let me know though, and I'll be sure to surface that functionality in this library's API.
At any rate, a DIY approach here should be pretty straightforward. You'd request chunks of the spreadsheet (if it's large) using GoogleSpreadsheets.rows(), then iterate through the results and drop any rows whose columns don't match your criteria.


deinit tcpip_adapter_init and esp_event_loop_init to free resources (IDFGH-246)

Environment

Development Kit:    [none]
Core (if using chip or module): [ESP-WROOM32]
IDF version 358c822d
Development Env:		[Eclipse]
Operating System:		[Ubuntu]
Power Supply:         [Battery]

Problem Description
I'm trying to deinit tcp adapter to free some memory. I can't find deinit function for tcpip_adapter_init to delete LwIP core task and de-initialize LwIP-related work as they are no longer needed. Also, I can't find deinit function for  esp_event_loop_init to delete system Event task and de-initialize an application event's callback function as they are no longer needed.
These functions allocate resources and my application doesn't want WiFi all the time so I have to deinit all its related resources and be able to re-init it again later when needed
Expected Behavior
deinit tcpip_adapter_init and esp_event_loop_init
Actual Behavior
no functions for that

@my-abousamra yes, IDF currently doesn't support tcpip adapter and event deinit, we will consider it in the future.

I hope it would be soon

I hope it would be soon

I hope this issue to be labelled with "to be implemented"

Hello,
I'm having the same problem with the tcip_adapter_init() function. Did you find any solution ?
Thank you

2019 year. Still nothing?
Such "deinit" functions is highly desirable

Hi @my-abousamra
We already have functions to deinitilalize both esp_event and esp_netif (successor of the tcpip_adapter), so we will close the issue.
As mentioned in https://github.com/espressif/esp-idf/issues/4628 we are still not able to uninitialize the TCP/IP stack itself. In case you need to free resources or reduce power consumption, please check the methods described in the referenced issue, or possibly suspend and delete the lwip thread. We'd like to address this issue correctly in the longrun, but would need to implement these uninits in lwip first and that won't happen in any near future.

Thanks for reporting, feel free to reopen.


Traversable holes

Thanks for the blog comment and this pull request. I need to swap these ideas back in after all this time, and then I'll respond to the PR. I've been meaning to resurrect these ideas anyway for another project I'm keen on, so the timing is good.
Back in touch soon.

This will generally be less efficient than a custom-written or algebra-based solution, but not horribly so. The reason for the inefficiency is that the altered copies of the argument can (often) share a lot of structure with each other, but cannot share any with the argument itself.


feat: add support to luau-lang?

luau doesn't allow you to do many things for sandbox reasons, but perhaps basic support could allow for better code lint.
i can runned bootstrapped CLI run by completely mocking io and removing require

https://luau.org
https://luau.org/sandbox
https://luau.org/compatibility

luau-analyzer is being used as a linter, using it as a toolchain will not be possible due to the sandbox/open-to-box blocking issue, perhaps I can look at this again in the future.


[Backup] GA az backup and some bug fixes

Description

Making the az backup module GA by removing the preview tag

Disabling CRR after enabling it bug fix

az backup protection enable-for-vm/update-for-vm simultanous disk inclusion-exclusion bug fix

Added support for specifying  --target-storage-account in different RG using the ARM id  in az backup restore restore-azurefiles/restore-azurefileshare command

az backup container show bug fix when providing IaaSVM container native name.

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Backup


Add 'orig_ch_names' to Raw._raw_extras for EDF, BDF, GDF, and apply _unique_channel_names before checking include/exclude channels

What does this implement/fix?
This pull request addresses an issue with handling EDF/BDF/GDF files that contain channels with duplicate names. Previously, channels with duplicate names were assigned a suffix (-N) after the process of including/excluding channels, which made it impossible to selectively include or exclude specific instances of these channels.
The proposed solution is to apply the _unique_channel_names function before the inclusion/exclusion process. Additionally, the original channel names (orig_ch_names) are now stored in Raw._raw_extras. This inclusion is particularly useful as it allows users to determine whether channel names have been modified and facilitates a more detailed examination of the raw data alongside other contents of _raw_extras.
Additional information
This modification could impact existing workflows. For instance, consider an EDF file with channels named ["A", "A", "B", "C"]. If a user attempts to exclude channels "A" and "C" using the following code:
raw = mne.io.read_raw_edf("my.edf", exclude=["A", "C"])

The behavior will differ pre and post-PR:

Before PR: ch_names = ["B"]
After PR: ch_names = ["A-0", "A-1", "B"]

If a channel is excluded using a string (interpreted as a regex), the outcome remains unchanged:
raw = mne.io.read_raw_edf("my.edf", exclude="A")

Both before and after PR: ch_names = ["B", "C"]

This modification could impact existing workflows.

This is a bit dangerous. Could we instead exclude before and after renaming? Then old code would work as would the new code you want.

Additionally, the original channel names (orig_ch_names) are now stored in Raw._raw_extras. This inclusion is particularly useful as it allows users to determine whether channel names have been modified and facilitates a more detailed examination of the raw data alongside other contents of _raw_extras.

Users should never make use of private attributes (those with a leading underscore) and we shouldn't facilitate them doing so. They can change at any time with no warning. So -1 on including them in _raw_extras. Along these lines, we should also remove any mention of private attributes in the changelog, and just talk about the behavior of exclude being improved to support excluding channels based on their post-renaming names in addition to their pre-renaming names.

@larsoner
Thank you for comments.

Could we instead exclude before and after renaming? Then old code would work as would the new code you want.

exclude_after_unique (default False) parameter is added to read_raw_edf and etc.
This keeps backward compatibility and able to choose one of duplicated channel by exclude_after_unique=True.
How is this?

Users should never make use of private attributes (those with a leading underscore) and we shouldn't facilitate them doing so. They can change at any time with no warning. So -1 on including them in _raw_extras. Along these lines, we should also remove any mention of private attributes in the changelog, and just talk about the behavior of exclude being improved to support excluding channels based on their post-renaming names in addition to their pre-renaming names.

I understand.
orig_ch_names is removed from this PR.
On the other hand, sometimes I actually need these information.
Is it ok to make another PR to add orig_ch_names?

On the other hand, sometimes I actually need these information. Is it ok to make another PR to add orig_ch_names?

Sure but we should think about how. Ideally it could live in raw.info somewhere but I can't think of a good place. So instead maybe a little utility function like mne.io.edf.read_channel_names(...) that extracts just the original channel names or something would work?

So instead maybe a little utility function like mne.io.edf.read_channel_names(...) that extracts just the original channel names or something would work?

It sounds good.
I also always use n_samps and record_length in _raw_extras to calculate original frequencies.
These values are taken by using the private function _read_raw_header directly because I would like to know before making Raw object to divide into same frequency channels to keep the frequency.
I will try to make functions to read these information directly in another PR.

Just a couple if minor comments otherwise LGTM!

The doc for exclude_after_unique was updated and moved into mne/utils/docs.py.

Failures unrelated and comments addressed, in it goes, thanks @rcmdnk !


major ui update

add a cool sidebar, redesign ui, improve responsiveness,
customizable theme + mode!
remove old svg, redundant comments

Maybe shift the pink theme color button to the right of the red (between red and yellow). Just so it has a rainbow feel

Maybe shift the pink theme color button to the right of the red (between red and yellow). Just so it has a rainbow feel

done

Once the broken links are resolved I think we can merge this pull request. I have also completed the custom countdown in #39 with that sorta animated countdown so the pencil icon part can start working once we merge the two. Hopefully no breaking changes

about the broken links, do you mean until those features are implemented?

about the broken links, do you mean until those features are implemented?

You could remove those links before you merge into master so that only the implemented/working ones are on the live site

moved the pink ico in between red and yellow

where can't see it on my side

clear cache and try again :)

You could remove those links before you merge into master so that only the implemented/working ones are on the live site

@RDjarbeng
No, if it must be done, then there shall be no merging until it's complete!
sidenote: I'm not going to accept a version other v2 after all this, cos these are significant updates.

implement #41

About the custom backgrounds I think we can set some default backgrounds for the user to use and nit rely in user uploading one. This is also good incase the user's background is not showing correctly.
Change the 'upload... Background' to 'set background'

Date time picker, Set the date time picker so dates that are less than the next day (the day after the countdown, tomorrow) are invalid. Otherwise the user will see a static clock with zeros. Also the current day is not allowed because only dates are selected, default is midnight. This will remain until the user can set their own time

Fixed it myself

Will use this pull request as a final launch pad for v2.0.0 once #46 is done

Everything's set! :1st_place_medal:

Not on  the service worker it ain't

At long last


Handle undefined chargingWatts (DC charging)

Admittedly not tested (no longer near a DC charger), but should handle the case where chargingWatts is undefined, which appears to be the case during DC fast charging. Figured displaying “DC” is better than “undefined”

Hmm, I have seen proper watts values from the API also during DC charging.


Default example doesn't work on windows machine.

Thanks for the great tool there !
When I install mocha, and run the default example, it doesn't work on my windows machine,
In order for it to work I had to do the 2 things.

Get the Electron Path
Also add the default path to my Electron App as a First Argument.

Shouldn't  the default example include that ?
i.e
var Application = require('spectron').Application;
var assert      = require('assert');
var path        = require('path');

describe('application launch', ()=> {
	this.timeout(10000)

	beforeEach(()=> {
		this.app = new Application({
			path: getElectronPath(),
			args: [path.join(__dirname, '..')]
		})
		return this.app.start();
	});

	afterEach(()=> {
		if (this.app && this.app.isRunning()) {
			return this.app.stop()
		}
	})

	it('shows an initial window', ()=> {
		return this.app.client.getWindowCount().then(function (count) {
			assert.equal(count, 1)
		});
	})

	function getElectronPath() {
		let electronPath = path.join(__dirname, '..', 'node_modules', '.bin', 'electron');
		if (process.platform === 'win32')  electronPath += '.cmd';
		return electronPath;
	}
});

I would gladly do a PR if  you agree necessary

I agree that it's necessary. This post ended about 3-4 hours of head scratching.

There is a better way: https://github.com/electron/spectron/issues/86

let electronPath = require('electron')
....

    this.app = new Application({
      path: electronPath,
      args: [
        path.join(__dirname, '..', 'app')
      ]
    })

That is indeed a better way. Either way, something should be added to the docs.

@etiennejcharles please do submit a PR!

OH god, thanks for this... I was about to throw my debugger in the trash.

@etiennejcharles by the way, your sample code has a bug: using an arrow function makes you lose the mocha context this.timeout
describe('application launch', function () {     this.timeout(10000) ...

Hi! When I try to run this example, test failing with error:

Error: timeout of 10000ms exceeded. Ensure the done() callback is being called in this test.

Application was started, but test hasn't been executed. How fix it?
My code:
`const Application = require('spectron').Application;
const assert = require('assert');
const electronPath = require('electron-prebuilt');
const path = require('path');
describe('application launch', function () {
this.timeout(10000);
beforeEach(function () {
    this.app = new Application({
        path: electronPath,
        args: [
            path.join(__dirname, '..', 'app')
        ]
    });
    return this.app.start();
});

afterEach(function () {
    if (this.app && this.app.isRunning()) {
        return this.app.stop()
    }
});

it('shows an initial window', function () {
    console.log(this.app.client.getWindowCount());
    return this.app.client.getWindowCount().then(function (count) {
        assert.equal(count, 1)
    })
})

});
`

Thanks for the comment @JohnBerlin  Il do a pull ASAP!

Pull request created ;) https://github.com/electron/spectron/pull/141


Show fiat value for combined balances in account header

We show in the accounts picker:

But not in the account header:

https://www.figma.com/file/OSQocEEJnfcMkniEl8u3U8/%231483---Initial-Bitcoin-support?node-id=259%3A59330&t=issirqQ7YBDFryGY-4

Thanks! Though I think we want to preserve the two options to copy BTC and STX addresses per https://github.com/hirosystems/stacks-wallet-web/issues/3115 ?

This ticket seems to be the same or conflicting #3132
Solution on the ticket above


Hook an external listener

In order to link side effects with actions, we're introducing a new option listener (I'm not good at naming, so any other suggestions are welcome).
Here's how it would work for history (assuming that the location is changed with CHANGE_LOCATION action, otherwise we could compare, for example, an action payload key):
let historyIdx = 0;
let historyIndexes = [historyIdx];

const listener = (liftedState, liftedAction) => {
  if (liftedAction.type === 'PERFORM_ACTION') {
    if (liftedAction.action.type === 'CHANGE_LOCATION') historyIdx++;
    // or: if (liftedAction.action.router !== undefined) historyIdx++;
    historyIndexes.push(historyIdx);
    return;
  }

  if (liftedAction.type === 'JUMP_TO_ACTION') { // time travelling
    history.go(historyIndexes[liftedAction.actionId]);
  }
  else if (liftedAction.type === 'JUMP_TO_STATE') { // legacy - we'll deprecate this action
    const id = liftedState.stagedActionIds[liftedAction.index];
    if (historyIndexes[id]) history.go(historyIndexes[id]);
  }

  // Replace the location if the corresponding state changed during hmr, persisting, importing...
  const currentState = liftedState.computedStates[liftedState.currentStateIndex];
  const locationInStore = currentState.router.location.pathname;
  if (history.location.pathname !== locationInStore) {
    history.replace(locationInStore);
  }
}

const store = createStore(rootReducer, window.__REDUX_DEVTOOLS_EXTENSION__({ listener }));
// or const store = createStore(rootReducer, DevTools.instrument({ listener }));

Instead of accumulated historyIndexes we could generate them from liftedState.actionsById, but it's more declarative and, anyway, it's intended only for development or when window.__REDUX_DEVTOOLS_EXTENSION__ is defined.
We could also use it for other cases when need to link side effects, as, for example, for redux saga devtools.
\cc @mjackson @ryanflorence @supasate @timdorr @taion @gaearon

Is the idea here that developers can provide listeners to users for cases where custom integration with Redux dev tools is required?

@taion exactly. It can be composable and used like:
import { reduxDevToolsListener } from 'react-router-redux';

const store = createStore(rootReducer, DevTools.instrument({
  listener: reduxDevToolsListener
}));

Or we could add an additional argument:
const store = createStore(rootReducer, DevTools.instrument({ /* options */ }, listener));

Regarding react-router, there's also connected-react-router.  @supasate did a great job, but it has 2 issues now:

we don't want extra operations when not needed: https://github.com/supasate/connected-react-router/pull/15#issuecomment-269646077
we don't want to push a new url in the history when time travelling: https://github.com/supasate/connected-react-router/issues/36

Basically, we could make a "hackable" middleware which will do the same as my listener example does:
const routerMiddleware = (history) => {
  let historyIdx = 0;
  let historyIndexes = [historyIdx];

  return store => next => action => {
    if (store.liftedStore) { // is `redux-devtools-instrument` applied
      const liftedState = store.liftedStore.getState();
      const currentId = liftedState.nextActionId - 1;
      if (!historyIndexes[currentId]) { // is 'PERFORM_ACTION'
        if (liftedState.actionsById[currentId].action.type === 'CHANGE_LOCATION') {
          historyIdx++;
        }
        historyIndexes.push(historyIdx);
        return next(action)
      }

      if (liftedState.currentStateIndex !== liftedState.stagedActionIds.length - 1) {
        // time travelling
        history.go(
          historyIndexes[liftedState.stagedActionIds[liftedState.currentStateIndex]]
        );
      }

      // Replace the location if the corresponding state changed during hmr, toggling actions...
      const currentState = liftedState.computedStates[liftedState.currentStateIndex];
      const locationInStore = currentState.router.location.pathname;
      if (history.location.pathname !== locationInStore) {
        history.replace(locationInStore);
      }

      return next(action)
    }
  }
}

The only issue here is importing. In the listeners example we have the liftedAction and can address it.

Sounds very good! I don't know about liftedState and liftedAction yet but I'll check them out.
About time travelling, at history.go(n), we might need to subtract the target position with the current position because n is the relative position to the current history position (in the browser history stack) (ref).

Eh, sounds good if it's useful.
FWIW I think pretty fundamentally that this isn't the right approach for integrating routing with Redux, and that you'd be better off if you followed either:

React Navigation's pattern of updating the URL as a side effect of navigation that primarily takes place within Redux, or
Farce's approach of making the Redux store the full state of truth for the current location

But whatever – this seems generic enough.

@supasate, yes, we can use history.go(historyIndexes[liftedAction.actionId] - historyIdx). I've updated the snippets.
@taion, this is a POC for @mjackson's tweet of what we can do from Redux DevTools part. For the extension we had also a way to check if a state update is the result of time travelling, hot reloading..., but it was even worse.

Right, this is an adequate workaround for history's quirks.
Really the right way to handle this would be something like the way React Navigation deals with things per https://github.com/react-community/react-navigation/blob/v1.0.0-beta.5/website/src/BrowserAppContainer.js#L22-L39 (but perhaps in a store enhancer or subscriber), and then dev tools stuff just wouldn't be a special case any more.

I agree with @taion that doing it in a store enhancer or subscriber would is better. However, we still need a way to figure out whether a state was updated due to a client action or from a DevTools monitor (and if the latter we should handle that action accordingly). That aims to be solved in #16. So, the example above would become:
let historyIdx = 0;
let historyIndexes = [historyIdx];

if (store.liftedStore) { // subscribe only if devtools instrumentation applied
  store.subscribe(() => {
    const liftedState = store.liftedStore.getState();
    const liftedAction = store.liftedStore.getState().liftedAction;

    if (liftedAction.type === 'PERFORM_ACTION') {
      if (liftedAction.action.type === 'CHANGE_LOCATION') historyIdx++;
      // or: if (liftedAction.action.router !== undefined) historyIdx++;
      historyIndexes.push(historyIdx);
      return;
    }

    if (liftedAction.type === 'JUMP_TO_ACTION') { // time travelling
      history.go(historyIndexes[liftedAction.actionId] - historyIdx);
    }
    else if (liftedAction.type === 'JUMP_TO_STATE') { // legacy - we'll deprecate this action
      const id = liftedState.stagedActionIds[liftedAction.index];
      if (historyIndexes[id]) history.go(historyIndexes[id]);
    }

    // Replace the location if the corresponding state changed during hmr, persisting, importing...
    const currentState = liftedState.computedStates[liftedState.currentStateIndex];
    const locationInStore = currentState.router.location.pathname;
    if (history.location.pathname !== locationInStore) {
      history.replace(locationInStore);
    }
  });
}

It should work for a connected component like in https://github.com/ReactTraining/react-router/pull/4717 just fine. In case of a store enhancer we should either check store.liftedStore inside store.subscribe or execute in the next tick, since the enhancer will be applied before devtools instrumentation. It will not work for middlewares, since they have access only to store.getState and store.dispatch.

Closing in favour of #16.


Logout button issue fixed

I have done what I thought was necessary. Please let me know if there is any mistake so that I can try and fix it.

You can close a particular issue automatically from a pull request. The issue will get closed the moment @drimpact accepts your pull request.  You can do so by including something like "Closes #91" in the description. See this for more info.


transfer of account?

Hi,
Will you be willing to give me this github id? If you look at my profile you can see that I've a project with this name and it would be nice to have nanopy as the username. Your public profile doesn't show that much activity and I thought may be I'll ask.

If you are willing, you just have to change your username and let me know. It'll become available for me to claim.


Add lint to PR template

Pull Request Test Coverage Report for Build 110

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 11.068%

Totals

Change from base Build 107:
0.0%

Covered Lines:
106

Relevant Lines:
717

💛  - Coveralls

Pull Request Test Coverage Report for Build 110

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 11.068%

Totals

Change from base Build 107:
0.0%

Covered Lines:
106

Relevant Lines:
717

💛  - Coveralls

Pull Request Test Coverage Report for Build 110

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 11.068%

Totals

Change from base Build 107:
0.0%

Covered Lines:
106

Relevant Lines:
717

💛  - Coveralls

Pull Request Test Coverage Report for Build 110

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 11.068%

Totals

Change from base Build 107:
0.0%

Covered Lines:
106

Relevant Lines:
717

💛  - Coveralls

Pull Request Test Coverage Report for Build 110

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 11.068%

Totals

Change from base Build 107:
0.0%

Covered Lines:
106

Relevant Lines:
717

💛  - Coveralls

Pull Request Test Coverage Report for Build 110

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 11.068%

Totals

Change from base Build 107:
0.0%

Covered Lines:
106

Relevant Lines:
717

💛  - Coveralls

Why is Coveralls running 6 times?

Not sure, I think maybe it is just commenting 6 times? We could turn it off altogether.


remove multiple enumeration in TryGetOptionArgumentList

and:

fix nullability
cache the trimmed value

Restarting the build as I don't get any issue locally.

Issues:
Unhandled exception. System.InvalidOperationException: 'internal-testhostcontroller-pid' not found in the command line
   at Microsoft.Testing.Platform.TestHostControllers.TestHostControllerInfo.GetTestHostControllerPID(Boolean throwIfMissing) in /_/src/Platform/Microsoft.Testing.Platform/TestHostControllers/TestHostControllerInfo.cs:line 18
   at Microsoft.Testing.Platform.OutputDevice.ConsoleOutputDevice..ctor(ITestApplicationCancellationTokenSource testApplicationCancellationTokenSource, IConsole console, ITestApplicationModuleInfo testApplicationModuleInfo, ITestHostControllerInfo testHostControllerInfo, IAsyncMonitor asyncMonitor, IRuntimeFeature runtimeFeature, IEnvironment environment, IProcessHandler process, Boolean isVSTestMode, Boolean isListTests, Boolean isServerMode, Int32 minimumExpectedTest, FileLoggerProvider fileLoggerProvider) in /_/src/Platform/Microsoft.Testing.Platform/OutputDevice/ConsoleDisplayService.cs:line 83
   at Microsoft.Testing.Platform.OutputDevice.PlatformOutputDeviceManager.BuildAsync(ServiceProvider serviceProvider, ApplicationLoggingState loggingState) in /_/src/Platform/Microsoft.Testing.Platform/OutputDevice/OutputDeviceManager.cs:line 35
   at Microsoft.Testing.Platform.Hosts.TestHostBuilder.BuildAsync(String[] args, ApplicationLoggingState loggingState, TestApplicationOptions testApplicationOptions, IUnhandledExceptionsHandler unhandledExceptionsHandler, DateTimeOffset createBuilderStart) in /_/src/Platform/Microsoft.Testing.Platform/Hosts/TestHostBuilder.cs:line 188
   at Microsoft.Testing.Platform.Builder.TestApplicationBuilder.BuildAsync() in /_/src/Platform/Microsoft.Testing.Platform/Builder/TestApplicationBuilder.cs:line 113
   at Program.<Main>$(String[] args) in /_/test/UnitTests/Microsoft.Testing.Platform.UnitTests/Program.cs:line 34
   at Program.<Main>(String[] args)
Unhandled exception. System.OperationCanceledException: The operation was canceled.
   at System.Threading.CancellationToken.ThrowOperationCanceledException()
   at System.Threading.CancellationToken.ThrowIfCancellationRequested()
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
   at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource<System.Net.Sockets.Socket>.GetResult(Int16 token)
   at System.IO.Pipes.NamedPipeServerStream.<>c__DisplayClass25_0.<<WaitForConnectionAsync>g__WaitForConnectionAsyncCore|0>d.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.Testing.Platform.IPC.NamedPipeServer.WaitConnectionAsync(CancellationToken cancellationToken) in /_/src/Platform/Microsoft.Testing.Platform/IPC/NamedPipeServer.cs:line 81
   at Microsoft.Testing.Platform.Hosts.TestHostControllersTestHost.InternalRunAsync() in /_/src/Platform/Microsoft.Testing.Platform/Hosts/TestHostControllersTestHost.cs:line 229
   at Microsoft.Testing.Platform.Hosts.TestHostControllersTestHost.InternalRunAsync() in /_/src/Platform/Microsoft.Testing.Platform/Hosts/TestHostControllersTestHost.cs:line 309
   at Microsoft.Testing.Platform.Hosts.CommonTestHost.RunAsync() in /_/src/Platform/Microsoft.Testing.Platform/Hosts/CommonTestHost.cs:line 38
   at Microsoft.Testing.Platform.Hosts.CommonTestHost.RunAsync() in /_/src/Platform/Microsoft.Testing.Platform/Hosts/CommonTestHost.cs:line 58
   at Microsoft.Testing.Platform.Builder.TestApplication.RunAsync() in /_/src/Platform/Microsoft.Testing.Platform/Builder/TestApplication.cs:line 251
   at Program.<Main>$(String[] args) in /_/test/UnitTests/Microsoft.Testing.Platform.UnitTests/Program.cs:line 35
   at Program.<Main>(String[] args)

and
Unhandled exception. System.InvalidOperationException: This program location is thought to be unreachable. File='/_/src/Microsoft.Testing.Extensions.Retry/RetryOrchestrator.cs' Line=61
   at Microsoft.Testing.Extensions.Policy.RetryOrchestrator.OrchestrateTestHostExecutionAsync() in /_/src/Microsoft.Testing.Extensions.Retry/RetryOrchestrator.cs:line 61
   at Microsoft.Testing.Platform.Hosts.TestHostOrchestratorHost.RunAsync() in /_/src/Platform/Microsoft.Testing.Platform/Hosts/TestHostOchestratorHost.cs:line 30
   at Microsoft.Testing.Platform.Builder.TestApplication.RunAsync() in /_/src/Platform/Microsoft.Testing.Platform/Builder/TestApplication.cs:line 251
   at Program.<Main>$(String[] args) in /_/test/IntegrationTests/Microsoft.Testing.Platform.Acceptance.IntegrationTests/Program.cs:line 36
   at Program.<Main>(String[] args)

I am not sure how it relates to your changes. I will need to investigate but will probably be a little short today.

I will probably not have time to look at the issues of this PR before tomorrow.

@SimonCropp I am back from holidays and will look at the remaining PRs.


[Bug]: provider organization_name and account_name when you only have an account locator

Terraform CLI Version
v1.9.1
Terraform Provider Version
v0.98.0
Company Name
No response
Terraform Configuration
provider "snowflake" {
  account       = "XYZ12345.us-east-1"
  ...
}

Category
category:resource
Object type(s)
Provider connection config, no specific resource.
Expected Behavior
With the account attribute of the provider config now deprecated, and with account locators continuing to be supported, it should be clear how to migrate to the new configuration when the old configuration only uses an account locator and doesn't use the ORGNAME-ACCOUNTNAME convention.
Actual Behavior
With the account attribute of the provider config now deprecated, and with account locators continuing to be supported, it is not clear how to migrate to the new configuration when the old configuration only uses an account locator and doesn't use the ORGNAME-ACCOUNTNAME convention.
Steps to Reproduce
Try to migrate the above HCL to the new provider configuration which requires an organization_name and an account_name, but with an account that only has an account locator.
For us, this happens with reader accounts (which aren't managed as properly named snowflake_account resources). And also with our ORGADMIN account, which, since it's only job is to manage other accounts, it never got a name itself.
How much impact is this issue causing?
Low
Logs
No response
Additional Information
https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/MIGRATION_GUIDE.md#behavior-change-deprecated-fields
https://github.com/Snowflake-Labs/terraform-provider-snowflake/pull/3166
Would you like to implement a fix?

[ ] Yeah, I'll take it 😎

Hi @jrobison-sb 👋
We'll add the link to the docs in our migration guide. I just want to confirm: are you able to use the new fields with reader and orgadmin accounts? I can't see that they have any limitations with the account name format.

@sfc-gh-jmichalak thanks for taking a look.

We'll add the link to the docs in our migration guide.

There's already a link here (where it says "Read more in the docs").

are you able to use the new fields with reader and orgadmin accounts?

I have not been able to do so, though I'm not entirely sure if it's user error on my part or something else. I tried it like this:
# The old way before the deprecation
provider "snowflake" {
  account       = "XYZ12345.us-east-1"
  ...
}

# My failed attempt at fixing the deprecation
provider "snowflake" {
	organization_name = "MY_ORG_NAME"
	account_name    = "XYZ12345"
}

My failed attempt at fixing the migration crashed a terraform plan like this:
Error: open snowflake connection: 261004 (08004): failed to auth for unknown reason. HTTP: 404, URL: https://MY_ORG_NAME-XYZ12345.snowflakecomputing.com:443/...

If this is a case of user error and I need to try some other format or something, I'm happy to try whatever...
Thanks.

Yup, we have a link, but I think we should be more explicit here and at least mention the other account format.
I think your config is slightly incorrect. In our environments, the account name (in Format 1) does not match the account locator (in Format 2). Please make sure you use values from https://docs.snowflake.com/en/user-guide/admin-account-identifier#finding-the-organization-and-account-name-for-an-account or check them with
SELECT CURRENT_ORGANIZATION_NAME(), CURRENT_ACCOUNT_NAME();

These values should match organization_name and account_name in the config, respectively.

Thanks @sfc-gh-jmichalak, that unblocked me and I'm all good now. Thanks for taking the time to set me straight on this.
I'll leave this issue open in case there's a desire to use this issue to update the docs. Or if not, feel free to close this, I have no further questions.
Thanks.

I'm also facing an issue with this, even when using the proper org and account name as derived from above mentioned queries.
Old config (working in 0.97):
provider "snowflake" {
  user                   = myuser
  account                = "${myaccount}.${myregion}"
  role                   = "myrole"
  private_key            = base64decode(mykey)
  private_key_passphrase = mypassphrase
  authenticator          = "JWT"
}

New config:
provider "snowflake" {
  user                   = myuser
  organization_name      = myorg
  account_name           = myaccount
  role                   = myrole
  private_key            = base64decode(mykey)
  private_key_passphrase = mypassphrase
  authenticator          = "SNOWFLAKE_JWT"
}

I also tried to revert back to JWT with the new config but this did not work.
The error I get, after a few minutes, is:
Error: open snowflake connection: Post "https://MYORG-MYACCOUNT.snowflakecomputing.com:443/session/v1/login-request?requestId=&request_guid=&roleName=myrole": EOF

The above error was caused by firewall whitelisting on our end, which is pretty obvious in hindsight. But if people are reading this: please realize the URL is changed, so if you had specific whitelisting based on the old URL this will have to be amended/expanded.

Good pointer @maxnsdia. We will add it to the migration guide!

Hey @waffleshop. Do you mean account locators? If so, then pls read https://docs.snowflake.com/en/user-guide/admin-account-identifier, short extract from it:
The preferred account identifier consists of the name of the account prefixed by its organization
(e.g. myorg-account123). You can also use the Snowflake-assigned locator as the account identifier;
however, the use of this legacy format is discouraged.

Yes. This is aligned with the link (and extract) provided above.


Progress stream changes

Depending on this:

https://github.com/ForloopAI/forloop_platform/pull/788

Dependencies:

https://github.com/ForloopAI/forloop_common_structures/pull/4

Introduces:

Added size/type to Result

Are you sure, this is the correct branch to be merged? I dont see any code changes that are related to streaming Otherwise - I have the same comments as for the PR: https://github.com/ForloopAI/forloop_common_structures/pull/4

No changes in forloop_common_structures were necessary specifically for streaming changes.
Changes for Result update were necessary, and this update is a part of the corresponding forloop_platform PR.


Support for getting cluster agent token

From what I can tell, there's no way to retrieve the token value as a data source for a cluster agent token resource. Having the ability to retrieve the token value would be needed to avoid hard-coding this in the TF config for cluster queues after the cluster has been created.

Thats correct. For security reasons, retrieving the token value from the API after creation is not supported. The token value is only accessible upon creation. This makes a datasource for cluster agent token quite not very useful so we haven't implemented it


Surface corresponding onOpen/onClose callbacks for Collapsible

The collapsible plug-in offers onOpen/onClose callbacks. It would be most useful if the Aurelia control surfaced those and/or fired events through the event aggregator.

Just looked into doing this work in a PR and realized the materialize.js implementation being used is 0.97.7 and the onOpen/onClosed callbacks were implemented in 0.97.8. I would not feel comfortable upgrading the dependency as part of just my work and would rather see it upgraded as a standalone PR.
I will postpone my work until there is guidance provided on moving to this newer version.

Thanks for pointing out onOpen/onClose - I didn't see that addition.
May I ask where did you get the impression that the materialize.js implementation being used is 0.97.7? I may be unclear somewhere and I'd like to be more explicit in that case.
This is interesting as I've been using 0.97.8 for quite a while.
Technically, #307 is completed. I left it open for some reason I don't remember.
Don't let that stop you from creating a PR. 😃

@Thanood Well I was just going by the fact when I cloned the project and did npm install and jspm_install I ended up with version 0.97.*7* in the root jspm_packages. However, I see now that the samples/jspm_packages is 0.97.*8*. The cause of the root of the project being .7 is because that's the version that the root config.js specifies. In fact there are two entries for the materialize lib in the map section.
Also note that both the project and the samples include materialize as a dependency in package.json, but both are calling for 0.9*7.5* which is obviously quite behind, but it really doesn't matter since JSPM is being used here. Additionally note that the version listed for peerDependencies in package.json is 0.9*7.6*.
So, clearly there's a little bit of confusion within the project itself. Is it worth entering a separate issue and corresponding PR to address these versioning issues? That's how I'd choose to do it, I just wanted to get your thoughts.

Thank you for clarifying.
The Materialize versions relevant for a jspm installation are all at ^0.97.5 (see here and here). I thought with the semver ^ modifier the most current in 0.x range is used. Is that not correct? I'm actally unsure because I have done some semver related mistakes in the past. 😃
Btw. this entry in config.js lists the direct jspm dependencies of<EMAIL_ADDRESS>Just for completeness if that's the second entry you meant.
This entry (which is at ^0.97.6) is actually used in npm based installations, so webpack or aurelia-cli.
It's only a peerDependency to allow for using forks. In fact this bridge does not depend directly on Materialize at all. It just expects that it's there.
To be honest, I don't always update the root to the latest Materialize version since it seemed not so relevant for me. The sample, on the other hand, needs the most recent version because that is the version actually used at runtime.

Is it worth entering a separate issue and corresponding PR to address these versioning issues?

If you'd like to do it (I don't think that you actually need to) you can just place it in the same PR. 😃


Reservoir data scraper not working anymore

No errors, but the html scraper we wrote for water levels doesn't pull in the new data.

It is erroring, it is just being hidden by a tryCatch
  tryCatch({
    data = scrape_ca_storage(sites$ID[i])

    write.table(data, paste0('../storage_data/', sites$ID[i], '.csv'), sep=',', row.names=FALSE)

    #png(paste0('../storage_plots/', sites$ID[i], '.png'))
    #plot(data[,1], data[,2], main=sites$ID[i], ylab='Storage(acre-feet)', xlab='')
    #dev.off()
  }, error=function(err){})

Looks like this is back as an issue. Didn't dig into it.

this seems to be working now


Bringing this standard in sync with global privacy and openness best practices

Excuse me if I open an issue on a broader comment, rather than on a specific item. I work for a European company which is a global leader in email software and services for ISPs (including a couple among the biggest US players). We believe in free software and an open Internet, and we have been trying for quite a while to push a similar concept named "Trusted Internet Services", so we are very happy to discover this commendable effort to design a standard for trustable, user-centric Internet services.
However, we think that this draft could be made better on a number of dimensions - especially, seen from a European perspective, this standard would actually fall short of the minimum set of privacy protections that Europeans already enjoy by law (as well as citizens of about 120 countries which adopted similar privacy laws). Specifically, I could not find anywhere the basic principle of data protection, "consent" - i.e., "I can freely decide which pieces of information I want to share with the company". It has been replaced by a weird "data benefit" principle which I never heard of in global privacy discussions; even if you would benefit by sharing some data, you should still be free to decide not to do so. The same for third party tracking: it is not enough if the company discloses what it does, I must be free to disallow it altogether if I want.
There are some other shortcomings, for example in terms of openness. Open source is not enough: companies should follow open and public standards, rather than making their own proprietary ones, and support open data formats. "Interoperability" with "complementary products" is not enough; you should enjoy freedom of choice, e.g. be able to switch to competing services/products without artificial barriers. This is why ownership should also include data ownership: you must be free to retrieve all the data that you stored in a service, in a standard format, and move them to another similar service - or even, thanks to the use of open source and open standards, host it on your own.
There are also a few minor technical observations - for example, encryption is fine but should also include recipient authentication (in non-anonymous communication), to prevent you from sending finely encrypted data to a wrong/malicious recipient.
However, first of all I would like to understand whether additions in this regard would be welcome or not - it will take some time to write them down inside this platform, and I would rather not waste it, or spend it just to be told that I have to wait for a couple of months and see :-) So it would be good if I could get preliminary feedback on these points, or even discuss them directly with someone from the project.
Thanks!

Thanks --- yes, suggested changes would be welcome, please feel free to suggested any wording changes you think are appropriate. We put this out on GitHub for this very reason.
On the issue of consent specifically, we try to address this concept with the section on control --- the standard currently provides:
I can see and control everything the company knows about me.
And for "indicators," the standard further provides:
The definition of 'user information' includes information collected from third-parties.
Users can control the collection of their information.
Users can delete their information.
Users can control how their information is used to target advertising.
I think the notion of "control" is designed to address both opt-in and opt-out --- either of which may be appropriate depending on the circumstances.  However, the standard could be more clear about that.  If you have ideas for how to make that more explicit, please suggest language.


Tex text not the correct size

Describe the error
When running the code, the size doesn't match the one expected (and quite a bit)
Code and Error
Code:
#Made by JsonV on the Manim Discord
class NumGenerator(Scene):
    def construct(self):
        num_gen_tex = Tex("Number Generator: ").to_edge(UL)
        self.play(Write(num_gen_tex))

        i = 0
        nums = []
        animations = []
        for k in range(10):
            a = np.random.normal(loc=100, scale=15)
            num = DecimalNumber(num_decimal_places=0).set_value(a)
            num.next_to(num_gen_tex, RIGHT)
            nums.append(num)
            animations.append(Write(num))
            animations.append(num.animate.to_edge(DL).shift(RIGHT*i))
            i += 1.3

        for animation in animations:
            self.play(animation)
        for num in nums:
            num.set_fill(ORANGE)
        nums[0].set_fill(BLUE)

        self.wait()

Output
Result Expected
https://user-images.githubusercontent.com/73761711/121065729-62826a00-c7c9-11eb-92c2-ee10d007166f.mp4
Result Get
https://user-images.githubusercontent.com/73761711/121065787-6f06c280-c7c9-11eb-8ae9-69710c64889d.mp4
Environment
OS System: Windows 10
manim version: master
python version: 3.9.5

I will annoy you again but this is not resolved.
I installed the new version of manim (this one, with the branch merged), launch the code and it still has numbers oversized. I can't manage to understand what is wrong:

I will annoy you again but this is not resolved.
I installed the new version of manim (this one, with the branch merged), launch the code and it still has numbers oversized. I can't manage to understand what is wrong:

Try #1555

I tried, it didn't work. This issue is certainly linked with the DecimalNumber Class, more specifically with set_submobjects_from_number() that is called by set_value(), in which we try to scale the numbers (either with self.arrange() line 44 or with string_to_mob() line 35)

I had a look at it. This issue is not linked with DecimalNumber. It is just because that Text is still a little larger than TexText and Tex. TEXT_MOB_SCALE_FACTOR = 0.0076 works well for me, so do you think I should modify TEXT_MOB_SCALE_FACTOR to 0.0076?

I looked at it too and yes, I think that 0.0076 is better

But now I have a bigger problem. The text in the example OpeningManimExample is, for a lack of better words, broken:
https://user-images.githubusercontent.com/73761711/122640896-296bc300-d102-11eb-8fbf-5df02c0bc376.mp4

But it works fine with me.
https://user-images.githubusercontent.com/44120331/122641263-c9dbda80-d136-11eb-8ae4-6a4d7f9fa221.mp4
My command:
gh pr checkout 1555        # GitHub CLI
python -m manimlib example_scenes.py OpeningManimExample -wo

I will look into the camera problem another time, thanks for trying. Do you have an idea why complex_map_words = TexText("""Or thinking of the plane as $\\mathds{C}$, this is the map $z \\rightarrow z^2$""") write just the LaTeX syntax ?

Maybe you can find it in issues page. I remember that I have seen it before.

I will search, thanks


IOS erros start

Running pod install...
CocoaPods' output:
↳
Preparing
Analyzing dependencies

Inspecting targets to integrate
  Using `ARCHS` setting to build architectures of target `Pods-Runner`: (``)

Finding Podfile changes
  A pusher_channels_flutter
  - Flutter
  - flutter_localization
  - geocoding_ios
  - geolocator_apple
  - shared_preferences_foundation
  - sqflite

Fetching external sources
-> Fetching podspec for `Flutter` from `Flutter`
-> Fetching podspec for `flutter_localization` from `.symlinks/plugins/flutter_localization/ios`
-> Fetching podspec for `geocoding_ios` from `.symlinks/plugins/geocoding_ios/ios`
-> Fetching podspec for `geolocator_apple` from `.symlinks/plugins/geolocator_apple/ios`
-> Fetching podspec for `pusher_channels_flutter` from `.symlinks/plugins/pusher_channels_flutter/ios`
-> Fetching podspec for `shared_preferences_foundation` from `.symlinks/plugins/shared_preferences_foundation/ios`
-> Fetching podspec for `sqflite` from `.symlinks/plugins/sqflite/ios`

Resolving dependencies of `Podfile`
  CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is only performed in repo update
[!] CocoaPods could not find compatible versions for pod "pusher_channels_flutter":
  In Podfile:
    pusher_channels_flutter (from `.symlinks/plugins/pusher_channels_flutter/ios`)

Specs satisfying the `pusher_channels_flutter (from `.symlinks/plugins/pusher_channels_flutter/ios`)` dependency were found, but they required a higher minimum deployment target.

/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:317:in `raise_error_unless_state'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:299:in `block in unwind_for_conflict'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:297:in `tap'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:297:in `unwind_for_conflict'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:682:in `attempt_to_activate'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:254:in `process_topmost_state'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolution.rb:182:in `resolve'
/Library/Ruby/Gems/2.6.0/gems/molinillo-0.8.0/lib/molinillo/resolver.rb:43:in `resolve'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/lib/cocoapods/resolver.rb:94:in `resolve'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/lib/cocoapods/installer/analyzer.rb:1082:in `block in resolve_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/lib/cocoapods/user_interface.rb:64:in `section'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/lib/cocoapods/installer/analyzer.rb:1080:in `resolve_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/lib/cocoapods/installer/analyzer.rb:125:in `analyze'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/lib/cocoapods/installer.rb:422:in `analyze'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/lib/cocoapods/installer.rb:244:in `block in resolve_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/lib/cocoapods/user_interface.rb:64:in `section'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/lib/cocoapods/installer.rb:243:in `resolve_dependencies'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/lib/cocoapods/installer.rb:162:in `install!'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/lib/cocoapods/command/install.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/claide-1.1.0/lib/claide/command.rb:334:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/lib/cocoapods/command.rb:52:in `run'
/Library/Ruby/Gems/2.6.0/gems/cocoapods-1.12.0/bin/pod:55:in `<top (required)>'
/usr/local/bin/pod:23:in `load'
/usr/local/bin/pod:23:in `<main>'

Error output from CocoaPods:
↳
[!] Automatically assigning platform `iOS` with version `12.0` on target `Runner` because no platform was specified. Please specify a platform for this target in your Podfile. See `https://guides.cocoapods.org/syntax/podfile.html#platform`.

Error running pod install
Error launching application on iPhone 14 Pro Max.

You might need to run pod repo update to ensure the cocoapods repo is up to date.
Have you tried to specify a higher iOS platform as per the error message instructions?

Yes, i tried specify higher iOS, but dont work , i try using pod repo updatebut still has the error using podfileplatform :ios, '12.0'`

Docs says that the ios deployment target should be 13.0 and above.