Elasticsearch keeps restarting

Elasticsearch keeps restarting, despite being in a ready state
Chart version:
$ helm search repo elasticsearch

elastic/elasticsearch           7.17.3

Kubernetes version:
$ k version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-17T15:48:33Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"ba58f86b00f6b0f0b7694a75464aa7806f8bf6fc", GitTreeState:"clean", BuildDate:"2022-03-30T23:40:46Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes provider: E.g. GKE (Google Kubernetes Engine)
AKS
Helm Version:
$ helm version
version.BuildInfo{Version:"v3.7.1", GitCommit:"1d11fcb5d3f3bf00dbe6fe31b8412839a96b3dc4", GitTreeState:"clean", GoVersion:"go1.16.9"}

Describe the bug:
If I install using the details provided above (without any values file) then elasticsearch fails after a short period of being ready.
Steps to reproduce:
$ helm install elasticsearch elastic/elasticsearch

Expected behaviour:
Elasticsearch should be stable
Provide logs and/or server output (if relevant):
$ k get pods -l app=elasticsearch-master -w
NAME                     READY   STATUS     RESTARTS   AGE
elasticsearch-master-0   0/1     Init:0/1   0          27s
elasticsearch-master-1   0/1     Running    0          27s
elasticsearch-master-2   0/1     Init:0/1   0          27s
elasticsearch-master-2   0/1     Init:0/1   0          48s
elasticsearch-master-2   0/1     PodInitializing   0          51s
elasticsearch-master-2   0/1     Running           0          52s
elasticsearch-master-0   0/1     PodInitializing   0          66s
elasticsearch-master-0   0/1     Running           0          67s
elasticsearch-master-0   1/1     Running           0          2m
elasticsearch-master-1   1/1     Running           0          2m
elasticsearch-master-2   1/1     Running           0          2m3s
elasticsearch-master-1   1/1     Terminating       0          2m24s
elasticsearch-master-1   0/1     Terminating       0          2m25s
elasticsearch-master-1   0/1     Terminating       0          2m25s
elasticsearch-master-1   0/1     Terminating       0          2m25s
elasticsearch-master-1   0/1     Pending           0          0s
elasticsearch-master-1   0/1     Pending           0          0s
elasticsearch-master-1   0/1     Init:0/1          0          0s
elasticsearch-master-1   0/1     PodInitializing   0          5s
elasticsearch-master-1   0/1     Running           0          6s
elasticsearch-master-1   1/1     Running           0          60s

The logs are rather long, so here's just the ending bit:
{"type": "server", "timestamp": "2022-05-18T08:34:01,977Z", "level": "INFO", "component": "o.e.c.r.DelayedAllocationService", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "scheduling reroute for delayed shards in [59.9s] (1 delayed shards)", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:34:02,154Z", "level": "INFO", "component": "o.e.i.g.GeoIpDownloader", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "updating geoip databases", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:34:02,155Z", "level": "INFO", "component": "o.e.i.g.GeoIpDownloader", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "fetching geoip databases overview from [https://geoip.elastic.co/v1/database?elastic_geoip_service_tos=agree]", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:34:02,812Z", "level": "INFO", "component": "o.e.i.g.GeoIpDownloader", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "geoip database [GeoLite2-ASN.mmdb] is up to date, updated timestamp", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:34:02,882Z", "level": "INFO", "component": "o.e.i.g.GeoIpDownloader", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "geoip database [GeoLite2-City.mmdb] is up to date, updated timestamp", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:34:02,954Z", "level": "INFO", "component": "o.e.i.g.GeoIpDownloader", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "geoip database [GeoLite2-Country.mmdb] is up to date, updated timestamp", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:34:41,440Z", "level": "INFO", "component": "o.e.c.s.MasterService", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "node-join[{elasticsearch-master-0}{6yeN9JukTkKW2q5-NoBAYQ}{GDkulEhxQCW9Ek_qgGPijQ}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{cdfhilmrstw} join existing leader], term: 5, version: 80, delta: added {{elasticsearch-master-0}{6yeN9JukTkKW2q5-NoBAYQ}{GDkulEhxQCW9Ek_qgGPijQ}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{cdfhilmrstw}}", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:34:42,462Z", "level": "INFO", "component": "o.e.c.s.ClusterApplierService", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "added {{elasticsearch-master-0}{6yeN9JukTkKW2q5-NoBAYQ}{GDkulEhxQCW9Ek_qgGPijQ}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{cdfhilmrstw}}, term: 5, version: 80, reason: Publication{term=5, version=80}", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:34:43,552Z", "level": "INFO", "component": "o.e.c.r.a.AllocationService", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.geoip_databases][0]]]).", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:36:01,684Z", "level": "INFO", "component": "o.e.t.ClusterConnectionManager", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "transport connection to [{elasticsearch-master-0}{6yeN9JukTkKW2q5-NoBAYQ}{GDkulEhxQCW9Ek_qgGPijQ}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{cdfhilmrstw}] closed by remote", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:36:01,686Z", "level": "INFO", "component": "o.e.c.r.a.AllocationService", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "Cluster health status changed from [GREEN] to [YELLOW] (reason: [{elasticsearch-master-0}{6yeN9JukTkKW2q5-NoBAYQ}{GDkulEhxQCW9Ek_qgGPijQ}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{cdfhilmrstw} reason: disconnected]).", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:36:01,687Z", "level": "INFO", "component": "o.e.c.s.MasterService", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "node-left[{elasticsearch-master-0}{6yeN9JukTkKW2q5-NoBAYQ}{GDkulEhxQCW9Ek_qgGPijQ}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{cdfhilmrstw} reason: disconnected], term: 5, version: 83, delta: removed {{elasticsearch-master-0}{6yeN9JukTkKW2q5-NoBAYQ}{GDkulEhxQCW9Ek_qgGPijQ}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{cdfhilmrstw}}", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:36:01,703Z", "level": "INFO", "component": "o.e.c.s.ClusterApplierService", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "removed {{elasticsearch-master-0}{6yeN9JukTkKW2q5-NoBAYQ}{GDkulEhxQCW9Ek_qgGPijQ}{<IP_ADDRESS>}{<IP_ADDRESS>:9300}{cdfhilmrstw}}, term: 5, version: 83, reason: Publication{term=5, version=83}", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }
{"type": "server", "timestamp": "2022-05-18T08:36:01,713Z", "level": "INFO", "component": "o.e.c.r.DelayedAllocationService", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-2", "message": "scheduling reroute for delayed shards in [59.9s] (1 delayed shards)", "cluster.uuid": "5rm76qDXRfmfn4ZzfOuHfQ", "node.id": "jJY1CYS7ReiQdY0fSgRUiQ"  }

Any additional context:
There is a stacktrace or two in the logs. I think they're harmless, but here's the first few lines of one:
{"type": "server", "timestamp": "2022-05-18T08:36:41,818Z", "level": "INFO", "component": "o.e.i.g.DatabaseNodeService", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-0", "message": "retrieve geoip database [GeoLite2-ASN.mmdb] from [.geoip_databases] to [/tmp/elasticsearch-10444144470664545833/geoip-databases/6yeN9JukTkKW2q5-NoBAYQ/GeoLite2-ASN.mmdb.tmp.gz]" }
{"type": "server", "timestamp": "2022-05-18T08:36:41,815Z", "level": "ERROR", "component": "o.e.i.g.DatabaseNodeService", "cluster.name": "elasticsearch", "node.name": "elasticsearch-master-0", "message": "failed to retrieve database [GeoLite2-City.mmdb]",
"stacktrace": ["org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];",
"at org.elasticsearch.cluster.block.ClusterBlocks.globalBlockedException(ClusterBlocks.java:179) ~[elasticsearch-7.17.3.jar:7.17.3]",
"at org.elasticsearch.cluster.block.ClusterBlocks.globalBlockedRaiseException(ClusterBlocks.java:165) ~[elasticsearch-7.17.3.jar:7.17.3]",
"at org.elasticsearch.action.search.TransportSearchAction.executeSearch(TransportSearchAction.java:929) ~[elasticsearch-7.17.3.jar:7.17.3]",
"at org.elasticsearch.action.search.TransportSearchAction.executeLocalSearch(TransportSearchAction.java:763) ~[elasticsearch-7.17.3.jar:7.17.3]",
"at org.elasticsearch.action.search.TransportSearchAction.lambda$executeRequest$6(TransportSearchAction.java:399) ~[elasticsearch-7.17.3.jar:7.17.3]",
"at org.elasticsearch.action.ActionListener$1.onResponse(ActionListener.java:136) ~[elasticsearch-7.17.3.jar:7.17.3]",

The others complain about different GeoLite2 databases.

hello @BryanDollery , it doesn't seems to be a bug/error with the helm-chart itself, please raise your question in our discuss, https://discuss.elastic.co


Address logger todo

Summary
See TODO

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

@colin-axner can I work on this issue?

Thank you, @chandiniv1! I think a submodule name like packetserver would work for now.

Closed by #7196


Patching global test env var to test with Dapr Runtime v1.11.0-rc.2

Description
Patching global test env var to test with Dapr Runtime v1.11.0-rc.2
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[x] The quickstart code compiles correctly
[x] You've tested new builds of the quickstart if you changed quickstart code
[x] You've updated the quickstart's README if necessary
[x] If you have changed the steps for a quickstart be sure that you have updated the automated validation accordingly. All of our quickstarts have annotations that allow them to be executed automatically as code. For more information see mechanical-markdown. For user guide with examples see Examples.

merging to get 1.11 release going.  notified @msfussell


Storage chains: Tracking issue

Substrate should support a kind of blockchain optimized for storing arbitrary data. The data would be stored not in the state trie, but rather off the chain as extrinsics. The state only contains a merkle trie root for all the block extrinsics.

[x] Implement blockchain-pruning, so that after a certain period, transactions are thrown out from the database. (#7868)
[x] Implement IPFS p2p protocol for substrate, so substrate could appear as an IPFS node. it would only need to index and serve transactions contained in the chain (#7963).
[ ] Publish transactions on IPFS DHT
[x] Storage renewal. A special kind of extrinsic that references an existing extrinsic and prevents it from being pruned.
[ ] Offchain worker API for grabbing and/or hashing/merklising stored/indexed transactions
[x] Write a runtime module.
[x] Fast/warp sync support

Closing as this has reached ready status for standalone deployment.


chore(main): release megaparse 0.0.34

:robot: I have created a release beep boop
0.0.34 (2024-11-07)
Features

megaparse-sdk-cherry (#105) (ad44aa3)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/QuivrHQ/MegaParse/releases/tag/megaparse-v0.0.34 :sunflower:


Design spike for embedded/importing/referencing Swagger/Markdown/WIKI/Pages

Investigate ways that we might create more uniformity with external guides for APIs.
Existing guides that clients (and our own) have created:

https://api.gov.bc.ca/ds/api/v2/console/
https://bcgov.github.io/aps-infra-platform/
https://github.com/bcgov/moh-hnclient-v2/wiki/HNS-Client-User-Journey
https://bcgov.github.io/common-service-showcase/services/cdogs.html
https://bcgov.github.io/common-service-showcase/services/ches.html
https://bcgov.github.io/common-service-showcase/onboarding/aps.html

Documentation elements that we should consider standardizing:

API Endpoints
OpenAPI spec links and viewer
"Try It" console (i.e./ Swagger Console)
Table of Contents for a Developer Guide
Authentication / Authorization
Onboarding Steps

Examples:

https://apistore.nrs.gov.bc.ca/store/apis/info?name=ccsc-api&version=v2&provider=admin#tab0
https://api.gov.au/assets/APIs/api-example.html


Pull Schrodinger-based solvation analysis into clean branch

I contaminated your other PR with other things I was working on so I made a clean branch

Generally looks good to me. Did a bit of refactoring to unclutter the main solvation_shell_extract.py file.


Errors when translating rst substitutions to MyST-flavoured markdown

Describe the problem
The way rst2myst translates rst substitutions to Markdown does not seem to work properly.
So far 2 inconsistencies have been identified:

rst2myst relies on MyST ability to use Jinja2 for substitutions. However Jinja2 requires a valid identifier (i.e., valid Python variable names), which is a much more restrictive condition, and therefore not compatible with rst (e.g. rst accepts strings with spaces)

rst2myst fails on translating links with substitutions (e.g. |ref|_), which are a very common use case when writing rst (e.g. for creating links with bold, italic or monospaced text elements)

This issue was first identified in pyscaffold/pyscaffoldext-markdown#25. A simplified description of the problem and steps to reproduce it can be found in this gist.
Link to your repository or website
https://gist.github.com/abravalheri/a9cdfa09f2809182fccca659b413da4a
Steps to reproduce
The following is a simplified example to reproduce the problem:

Assuming I have the following (example) in ReStructuredText:#. To avoid any problems with your installed Python packages, consider using |virtual environments|_

#. If everything works fine, push your local branch to |the repository service| with::

    git push -u origin my-feature

#. Go to the web page of your fork and click |contribute button| to send your changes for review.

.. |virtual environments| replace:: ``virtualenv``
.. |the repository service| replace:: GitHub
.. |contribute button| replace:: "Create pull request"
.. _virtual environments: https://virtualenv.pypa.io/en/stable/

When I try to convert it using the CLI (rst2myst stream original.rst > converted.md), I obtain the following MyST-flavoured markdown:---
substitutions:
  contribute button: '"Create pull request"'
  the repository service: GitHub
  virtual environments: '`virtualenv`'
---

1. To avoid any problems with your installed Python packages, consider using [virtual environments]

2. If everything works fine, push your local branch to {{ the repository service }} with:

   ```
   git push -u origin my-feature
   ```

3. Go to the web page of your fork and click {{ contribute button }} to send your changes for review.

[virtual environments]: https://virtualenv.pypa.io/en/stable/

As we can see, converted markdown contains invalid Jinja2 syntax, e.g. {{ the repository service }}, and the original link with substitution was converted to a simple link, without a substitution.
The version of Python you're using
3.8.0
Your operating system
Ubuntu 18.04.5 LTS
Versions of your packages
Direct installation:
myst-parser==0.15.2
rst-to-myst[sphinx]==0.3.2
Sphinx==4.1.2

The remaining packages where installed as dependencies of those 3 in an empty virtual environment created with:
$ virtualenv -p py38 .venv
$ source .venv/bin/activate
$ pip install sphinx myst-parser 'rst-to-myst[sphinx]'

Expected output
Two different behaviours could be expected from rst2myst:

The "rst substitution key" could be pre-processed to produce a valid Python identifier and in turn, that identifier could be used in Jinja2.
This include replacing or removing invalid characters, e.g. |the repository service| could be translated to
{{ the_repository_service }}.
This approach in shown in expected_option1 bellow.
The "rst substitution key" could be nested inside a dict value with an arbitrary name (e.g. __),
e.g. |the repository service| could be translated to {{ __["the repository service"] }}.
This approach in shown in expected_option2 bellow

Regarding links with substitutions, CommonMark's full reference links in combination with Jinja2 seem to be a good alternative, e.g. |ref|_ could be translated to [{{ ref }}][ref]. This approach is shown in both expected_option1 and expected_option2.
expected_option1
---
substitutions:
  contribute_button: '"Create pull request"'
  the_repository_service: GitHub
  virtual_environments: '`virtualenv`'
---

1. To avoid any problems with your installed Python packages, consider using [{{ virtual_environments }}][virtual environments]

2. If everything works fine, push your local branch to {{ the_repository_service }} with:

   `git push -u origin my-feature`

3. Go to the web page of your fork and click {{ contribute_button }} to send your changes for review.

[virtual environments]: https://virtualenv.pypa.io/en/stable/

expected_option2
---
substitutions:
  "__":
    contribute button: '"Create pull request"'
    the repository service: GitHub
    virtual environments: '`virtualenv`'
---

1. To avoid any problems with your installed Python packages, consider using [{{ __["virtual environments"] }}][virtual environments]

2. If everything works fine, push your local branch to {{ __["the repository service"] }} with:

   `git push -u origin my-feature`

3. Go to the web page of your fork and click {{ __["contribute button"] }} to send your changes for review.

[virtual environments]: https://virtualenv.pypa.io/en/stable/

In expected_option2, instead of using a nested dict __ inside of substitutions, the substititions dict itself could also be directly assigned to __ in the Jinja2 template context, this would allow users using any substitution key directly if they are valid identifiers and invalid identifiers via the __ helper.

(code blocks around git push ... in expected_option1|2 omitted due to GitHub's inability of dealing with nested code blocks)

Heya, yeh I have to admit, I hadn't noticed the "links with substitutions" syntax before, and never used it in my own work.
Your proposed solutions both seem viable, thanks.
Maybe I would lean towards expected_option1, as you end up with less verbose Markdown. But probably I would err towards replacing space with __ rather than _, just to make it slightly less likely there would be key clashes.
I can't say I have time right now to do this myself 😬 but would certainly welcome any PRs
Also interested to have a look at pyscaffold!

Thank you very much @chrisjsewell.
I am more or less in the same boat here in terms of time for contributing 😝, but in the future if I manage to get my hands on rst-to-myst, do you have any tips from where to start for this issue? (I am not familiar with the codebase...)

I have been using PyScaffold for years in a row now and I am really satisfied on how it helps me to creates Python packages (so much that I became one of the maintainers).
Lately I have been trying to integrate rst-to-myst so we can provide a out-of-the-box experience for people that want to write documentation in Markdown. The idea is to have an extension that translate our default .rst templates to MyST-markdown.
Let me know if you want to some information about PyScaffold, I am more than happy to chat about it 😄


Add Log query features to kubelet config

Description
What problem are you trying to solve?
Configuring kubelet to enable log query feature gates.
It seems that most of the kubelet configuration settings we support are focused on resource utilization and eviction. Do we have any plans to extend that to other kubelet settings?
The kubelet settings I would like are:

NodeLogQuery
enableSystemLogHandler
enableSystemLogQuery

NodeLogQuery is currently an alpha feature in 1.27 which is why I wanted to start a discussion about future plans for kubelet configuration for these types of settings. I'm assuming for alpha settings they would only be exposed in user-data but GA features might be easier to manage declaratively in the CRD
How important is this feature to you?
Medium important because this can be done via user-data, but it would be cleaner to have as part of the kubelet configuration.

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Closing this one for AWS in favor of https://github.com/aws/karpenter-provider-aws/issues/5833


LCFS - Rework Generic Organization Seeds and User Profiles

Title: LCFS - Rework Generic Organization Seeds and User Profiles
Describe the Task:
Rework existing database seed scripts to create more generic organizations and user profiles. This involves modifying the current seeding process to ensure that the generated organizations and user profiles are non-specific and generic, suitable for various testing and development scenarios.
Purpose:
The primary purpose of this task is to enhance the flexibility and relevance of the test data across different development and testing environments. By creating more generic organizations and user profiles, developers and testers can more effectively simulate a diverse range of real-world scenarios, leading to more robust and versatile software.
Acceptance Criteria:

[ ] The seed script generates a range of generic organizations that do not resemble any specific real-world entities.
[ ] User profiles created by the seed script are generic and diverse, representing a wide range of potential users.
[ ] The seeded data should be suitable for use in various development and testing scenarios, ensuring broad applicability.

Additional Context:

Ensuring data privacy and avoiding any resemblance to real organizations or individuals is critical in this rework.
Collaboration with the QA team might be beneficial to understand the range of scenarios needed for effective testing.

Nothing for PO/SME to test


Type theme via TS module augmentation.

Purpose
Currently our custom themes have no type support and the dark theme is essentially copy/paste of the light theme with colors updated. This PR adds complete typing to the theme (and every use of it in the codebase) and the dark theme now extends the default (light) theme.
themes.ts
Themes are now contained in a single file. The light theme only requires a name since it takes all the defaults. The dark theme has many overrides to adjust the colors.

[x] @alioso can you look into how we can style the TableHead without using overrides? It is not listed as a typed override (even in the latest version of MUI). I think it might just be a specialized TableRow.

themeFactory.ts
The themeFactory exports a function that accepts the overrides, and recursively merges them with the default theme (light theme), and then creates an MUI theme with the final object.
types/index.ts
The Linode.Theme has been removed as it's no longer necessary. The other 246 file changes are updates to accommodate this change and you can safely ignore them.
cc @asauber

Coverage decreased (-0.004%) to 27.067% when pulling 6c759a883f50c70ca8244c7cae554a944a3d2421 on rjstires:theme-typing into 36c877a8f417839e28b61195aa358316d076f72a on linode:develop.

Noticed when viewing Linode Listing on list view, the selected row (far left) appears black on default theme:
Production:

This branch:

Just the minor above issue was discovered on my pass testing this. Everything else (on both themes) looks solid. 👍

Great find @patthiel, Im on it.


EC2 machine very slow to stop and reboot

RancherOS Version: (ros os version)
Rancher 0.5.0
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
AWS
From AWS UI, I want to stop the machine, usually this takes some secondes, here with RancherOS some minutes, why?
Many thanks.

Just a thought, but it might be a long shutdown process because of the use of user-docker, system-docker, mounted volumes, and etc. I bet the graceful shutdown of so many services takes time.

Good to know!
It takes time but it stops well. Thanks you
Le 9 sept. 2016 6:32 PM, "Adam White"<EMAIL_ADDRESS>a écrit :

Just a thought, but it might be a long shutdown process because of the use
of user-docker, system-docker, mounted volumes, and etc. I bet the graceful
shutdown of so many services takes time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rancher/os/issues/1222#issuecomment-245966523, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABKc6cQR9PubZqqRKJQXvmryNitMyOuyks5qoYo6gaJpZM4J5MCj
.

RancherOS shuts down as quickly as most other distros I've tried, so I'm thinking this is something specific to AWS.

closing as anwsered


Serialize characters excluded in XML specs

For example serializing the following values raises an exception from within LINQ to XML:
TestString = "ab\u0003c",
TestCharArray = new [] { 'a', 'b', '\u0003', 'c'}

This issue has been reported by Robert Baron through email.

Is it verified already that we don't follow  the definition Text in the XML specification?
"Control characters" seems to be a too general description?

It’s impossible to safely serialize .net strings as-is in XML. Even XML-1.1, which allows control characters, doesn’t support the null character (\0). And using XML-1.1 isn’t recommended.
It’s OK to serialize your strings directly as XML content only if your data model itself disallows control characters in content. I.e., you should be throwing errors before trying to serialize to XML if you are going to do this because you should just overall not support them if serializing your strings to XML in this way is a requirement.
If you need to support transporting unconstrained .net string data via XML, your only option is to encode it in something protective like base64 as part of serializing.
The right thing for YAXLib to do is to make sure it throws when asked to serialize characters in an unsupported way.

Fully agree, @binki, thanks.
Currently, illegal characters throw e.g.
System.ArgumentException : '\ufffe', hexadecimal value 0xFFFE, is an invalid character.
in YAXSerializer
public string Serialize(object obj)
{
    // System.Xml.Linq.XNode.ToString()
    return SerializeXDocument(obj).ToString();
}

@304NotModified @NKnusperer - What does this mean:

Issue https://github.com/YAXLib/YAXLib/issues/2#issue-5638248 is not bug, but the consequence of following the XML specification
The exception thrown is correct
I like @binki's suggestion to offer Convert.ToBase64String() by creating e.g. YAXBase64StringAttribute
In case of (3) the BUG label should become ENHANCEMENT, otherwise the issue should be closed

What do you think?

@304NotModified
Looks like there's a rather simple way to de/serialize string fields/properties as CData or Base64-encoded.
I'm considering a YAXStringEmbeddingAttribute which allows for StringEmbedding.None | StringEmbedding.CData | StringEmbedding.Base64.
What do you think? (Also not sure about a good term for this attribute and enum)

Looks like there's a rather simple way to de/serialize string fields/properties as CData or Base64-encoded.
I'm considering a YAXStringEmbeddingAttribute which allows for StringEmbedding.None | StringEmbedding.CData | StringEmbedding.Base64.

Sounds good!

What do you think? (Also not sure about a good term for this attribute and enum)
Maybe YAXStringEncodingAttribute?  Or YAxTextEncodingAttribute or just YAXEncodingAttribute?

there should be way to just remove the illegal characters like \u0003

Agree. In it's simplest form all values would have to undergo a RegEx.Replace or maybe better stripped like
var input = "abc\u0003def";
var validXmlString = new string(input.Where(XmlConvert.IsXmlChar).ToArray())

If we're lucky, all values are anyway retrieved using XMLUtils.ToXmlValue(this object? self, CultureInfo culture) and the clean-up could be added there ;-)  Then, maybe we could introduce YAXSerializationOptions.StripInvalidXmlChars or alike.
But then this is a new issue?

YAXSerializationOptions.StripInvalidXmlChars

I like that one :)

Implementing YAXTextEmbeddingAttribute is done. YAXTextEmbedding.CData will always strip invalid chars. If this is undesired, the alternative YAXTextEmbedding.Base64 is there.
Will post a new PR after #203 is merged.

Resolved with release v4.0.0


Fix a11y warnings

What: Fixes a11y warnings identified in the Web Console.

Why: It helps clean up the noise logs in the console.

How: Changes made in accordance with a11y best practice.

Checklist:

[x] Tests
[x] Ready to be merged

Codecov Report

Merging #69 into master will not change coverage.
The diff coverage is 66.66%.

@@           Coverage Diff           @@
##           master      #69   +/-   ##
=======================================
  Coverage   94.84%   94.84%
=======================================
  Files          20       20
  Lines         291      291
  Branches       55       55
=======================================
  Hits          276      276
  Misses         15       15


Added display screenShare Docs

Fixes :

Added screenshare display docs

@Decoder07 Add display screenShare as a section below in the existing Screenshare page


Update PR

This is an update from the previous pull request #30
This uses the ternary operator to simplify the code and removes most redundancies as it checks only after the note is created

I think it is good.

Thank you @Aspireve.


Vane control issue

Hi,
I just wanted to say thanks for all your hard work on this project. It's been a lifesaver.
I have successfully connected an esp controller on tiny hardware to ARNU09GSBL2 wall unit. This is one of 4 units (3 wall + 1 ducted) connected to MultiV.
All seems to work good, except for vane control. When unit turns on the vane is at topmost position. I can turn the swing mode, but can't set the static angle. None of 4 available settings (although there is only one vane) changes anything.
Here is the C9 message C9.84.EA.1F.<IP_ADDRESS>.<IP_ADDRESS>.DA
It seems there are some bytes set that are 'unknown' in protocol.md
And here is a log for vane position change attempts (first to pos5, then to pos1)
[21:42:19][D][lg-controller:1305]: update
[21:42:19][D][lg-controller:905]: received A<IP_ADDRESS>.00.01.0C.<IP_ADDRESS>.00.84 (13)
[21:42:19][D][lg-controller:921]: verified send
[21:42:20][D][climate:011]: 'LG AC Office' - Setting
[21:42:20][D][climate:015]:   Mode: COOL
[21:42:20][D][climate:396]: 'LG AC Office' - Sending state:
[21:42:20][D][climate:399]:   Mode: COOL
[21:42:20][D][climate:404]:   Fan Mode: LOW
[21:42:20][D][climate:416]:   Swing Mode: OFF
[21:42:20][D][climate:419]:   Current Temperature: 25.50°C
[21:42:21][D][climate:425]:   Target Temperature: 27.50°C
[21:42:25][D][lg-controller:1305]: update
[21:42:26][D][lg-controller:814]: sending A<IP_ADDRESS>.00.01.0C.<IP_ADDRESS>.00.99 (13)
[21:42:26][W][component:237]: Component <unknown> took a long time for an operation (516 ms).
[21:42:26][W][component:238]: Components should block for at most 30 ms.
[21:42:30][D][esp32.preferences:114]: Saving 1 preferences to flash...
[21:42:30][D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[21:42:30][D][sensor:094]: 'Uptime': Sending state 1316.33704 s with 0 decimals of accuracy
[21:42:31][D][lg-controller:1305]: update
[21:42:31][D][lg-controller:905]: received A<IP_ADDRESS>.00.01.0C.<IP_ADDRESS>.00.99 (13)
[21:42:31][D][lg-controller:921]: verified send
[21:42:37][D][lg-controller:1305]: update
[21:42:40][D][select:062]: 'Airflow 1 Up/Down' - Setting
[21:42:40][D][select:115]: 'Airflow 1 Up/Down' - Set selected option to: 5
[21:42:40][D][select:015]: 'Airflow 1 Up/Down': Sending state 5 (index 5)
[21:42:40][D][lg-controller:513]: Setting vane 1 position: 5
[21:42:43][D][lg-controller:1305]: update
[21:42:43][D][lg-controller:905]: received C<IP_ADDRESS>.00.01.0C.5F.<IP_ADDRESS>.62 (13)
[21:42:43][D][sensor:094]: 'Error Code': Sending state 0.00000  with 0 decimals of accuracy
[21:42:43][D][climate:396]: 'LG AC Office' - Sending state:
[21:42:43][D][climate:399]:   Mode: COOL
[21:42:43][D][climate:404]:   Fan Mode: LOW
[21:42:43][D][climate:416]:   Swing Mode: OFF
[21:42:43][D][climate:419]:   Current Temperature: 25.50°C
[21:42:43][D][climate:425]:   Target Temperature: 27.50°C
[21:42:43][D][lg-controller:905]: received C<IP_ADDRESS>.00.01.0C.5F.<IP_ADDRESS>.62 (13)
[21:42:43][D][sensor:094]: 'Error Code': Sending state 0.00000  with 0 decimals of accuracy
[21:42:43][D][climate:396]: 'LG AC Office' - Sending state:
[21:42:43][D][climate:399]:   Mode: COOL
[21:42:43][D][climate:404]:   Fan Mode: LOW
[21:42:43][D][climate:416]:   Swing Mode: OFF
[21:42:43][D][climate:419]:   Current Temperature: 25.50°C
[21:42:43][D][climate:425]:   Target Temperature: 27.50°C
[21:42:43][D][lg-controller:905]: received C<IP_ADDRESS>.00.01.0C.1F.<IP_ADDRESS>.A2 (13)
[21:42:43][D][sensor:094]: 'Error Code': Sending state 0.00000  with 0 decimals of accuracy
[21:42:43][D][climate:396]: 'LG AC Office' - Sending state:
[21:42:43][D][climate:399]:   Mode: COOL
[21:42:43][D][climate:404]:   Fan Mode: LOW
[21:42:43][D][climate:416]:   Swing Mode: OFF
[21:42:43][D][climate:419]:   Current Temperature: 25.50°C
[21:42:43][D][climate:425]:   Target Temperature: 27.50°C
[21:42:43][D][lg-controller:905]: received C<IP_ADDRESS>.00.01.0C.1F.<IP_ADDRESS>.A2 (13)
[21:42:43][D][sensor:094]: 'Error Code': Sending state 0.00000  with 0 decimals of accuracy
[21:42:43][D][climate:396]: 'LG AC Office' - Sending state:
[21:42:43][D][climate:399]:   Mode: COOL
[21:42:43][D][climate:404]:   Fan Mode: LOW
[21:42:43][D][climate:416]:   Swing Mode: OFF
[21:42:43][D][climate:419]:   Current Temperature: 25.50°C
[21:42:43][D][climate:425]:   Target Temperature: 27.50°C
[21:42:44][D][lg-controller:861]: sending AA.<IP_ADDRESS>.<IP_ADDRESS>.02.F1.21.96 (13)
[21:42:44][W][component:237]: Component <unknown> took a long time for an operation (714 ms).
[21:42:44][W][component:238]: Components should block for at most 30 ms.
[21:42:49][D][lg-controller:1305]: update
[21:42:49][D][lg-controller:905]: received AA.<IP_ADDRESS>.<IP_ADDRESS>.02.F1.21.96 (13)
[21:42:49][D][lg-controller:921]: verified send
[21:42:50][D][lg-controller:814]: sending A<IP_ADDRESS>.00.01.0C.<IP_ADDRESS>.00.9E (13)
[21:42:50][W][component:237]: Component <unknown> took a long time for an operation (521 ms).
[21:42:50][W][component:238]: Components should block for at most 30 ms.
[21:42:55][D][lg-controller:1305]: update
[21:42:55][D][lg-controller:905]: received A<IP_ADDRESS>.00.01.0C.<IP_ADDRESS>.00.9E (13)
[21:42:55][D][lg-controller:921]: verified send
[21:42:56][D][select:062]: 'Airflow 1 Up/Down' - Setting
[21:42:56][D][select:115]: 'Airflow 1 Up/Down' - Set selected option to: 1 (Up)
[21:42:56][D][select:015]: 'Airflow 1 Up/Down': Sending state 1 (Up) (index 1)
[21:42:56][D][lg-controller:513]: Setting vane 1 position: 1
[21:43:01][D][lg-controller:1305]: update
[21:43:02][D][lg-controller:861]: sending AA.<IP_ADDRESS>.<IP_ADDRESS>.02.F1.21.EA (13)
[21:43:02][W][component:237]: Component <unknown> took a long time for an operation (517 ms).
[21:43:02][W][component:238]: Components should block for at most 30 ms.
[21:43:07][D][lg-controller:1305]: update
[21:43:07][D][lg-controller:905]: received AA.<IP_ADDRESS>.<IP_ADDRESS>.02.F1.21.EA (13)
[21:43:07][D][lg-controller:921]: verified send
[21:43:11][D][api.connection:197]: ESPHome Logs 2024.4.0 (<IP_ADDRESS>) requested disconnected

Any ideas on how to fix this? Your help would be awesome.
Thanks again for everything!
P.S. the red led on the esp is lit when connected to AC, is this ok?

What happens if you change the vane position using ThinQ or the wireless remote? What messages does the wired controller receive then?

P.S. the red led on the esp is lit when connected to AC, is this ok?

In my case that only happens when connected to USB (or maybe any 5V power source) but not when connected to the AC. Which ESP32 board are you using?

Here is the C9 message C9.84.EA.1F.<IP_ADDRESS>.<IP_ADDRESS>.DA

It looks like your unit doesn't support vertical vane control (low bit of byte 4, byte 4 is 0x80 for this unit). We don't check this currently in the code though. The code also assumes that if the two high bits of byte 5 are both zero we have 4 vanes, but maybe that's only the case if the "vane control" bit is set.

What happens if you change the vane position using ThinQ or the wireless remote? What messages does the wired controller receive then?

It looks like your unit doesn't support vertical vane control (low bit of byte 4, byte 4 is 0x80 for this unit). We don't check this currently in the code though. The code also assumes that if the two high bits of byte 5 are both zero we have 4 vanes, but maybe that's only the case if the "vane control" bit is set.

I don't have ThinQ dongle, but checked with wireless remote and the unit even doesn't beep when I push the button and no messages are received. So I think you are correct, no vertical vane control for this unit.
My only option is to enable swing and try to stop it at wanted angle. With wireless remote this works great, but with controller it has some delay before the command is received, thus the angle is random.
Maybe there is a way to time the swing on/off commands to achieve some sort of vane control? But not sure if it possible on single wire

P.S. the red led on the esp is lit when connected to AC, is this ok?

In my case that only happens when connected to USB (or maybe any 5V power source) but not when connected to the AC. Which ESP32 board are you using?

I use eps32 devkitc v4. Checked rrooggiieerr installation pictures, and on last pic it looks like led is lit as well. Weird as the board docs state it should turn on when the USB or an external 5V power supply is connected to the board

What happens if you change the vane position using ThinQ or the wireless remote? What messages does the wired controller receive then?

It looks like your unit doesn't support vertical vane control (low bit of byte 4, byte 4 is 0x80 for this unit). We don't check this currently in the code though. The code also assumes that if the two high bits of byte 5 are both zero we have 4 vanes, but maybe that's only the case if the "vane control" bit is set.

I don't have ThinQ dongle, but checked with wireless remote and the unit even doesn't beep when I push the button and no messages are received. So I think you are correct, no vertical vane control for this unit. My only option is to enable swing and try to stop it at wanted angle. With wireless remote this works great, but with controller it has some delay before the command is received, thus the angle is random. Maybe there is a way to time the swing on/off commands to achieve some sort of vane control? But not sure if it possible on single wire

P.S. the red led on the esp is lit when connected to AC, is this ok?

In my case that only happens when connected to USB (or maybe any 5V power source) but not when connected to the AC. Which ESP32 board are you using?

I use eps32 devkitc v4. Checked rrooggiieerr installation pictures, and on last pic it looks like led is lit as well. Weird as the board docs state it should turn on when the USB or an external 5V power supply is connected to the board

Maybe that's why https://esp32.com/viewtopic.php?t=13504

@sergeipr I just made a change that should fix this (it should now detect 0 vanes instead of 4). Let me know if this works.

Works like a charm! No vane entities exposed to HA.
Can confirm successful installation on 2 models - ARNU12GSBL2 and ARNU09GSBL2
Thank you for your hard work! 🙏🏼


Release v0.25.8

Adds

Adds embedCode prop to VideoPlayer component.
Adds export statements for ProgressIndicatorSizes and ProgressIndicatorTypes enums to index.ts.
Adds ExtraSmall and ExtraExtraSmall size variants to the Image component.
Adds ExtraSmall and ExtraExtraSmall size variants for CardImage in the Card component.
Adds AlertNotificationImportant icon to Icon component.
Adds Toggle component.
Adds xxxs (2px) spacing option to DS design tokens.
Adds external variant to Link component.

Changes

Changes category for Table component from Basic Elements to Page Layout.
Updates the background color for the Locations variant in the Breadcrumbs component from section.locations.secondary to section.locations.primary.
Updates the Notification component to show the AlertNotificationImportant icon for the Standard variant.
Reduces the bottom margin on labels and legends for form components from "16px" to "8px", or "s" to "sx" in Chakra-theme variables.
Updates docs for Chakra Grid component to use theme object values rather than CSS variables.
Updates the spacing in the Notification component to improve the alignment of the icon and text elements.
Updates the Notification component to optionally display/hide the Icon in the heading or content area.

Fixes

Fixes two bugs in the Slider: (1) unable to call the onChange function when it is not passed, and (2) fixing the default array value for the range slider so it mounts properly.
Updates the Select component's controlled state so that an initial empty value prop is acceptable.

Tugboat has finished building the preview for this pull request!
Link:

https://pr832-djuu34x02qgrdyulmpj95y2bku8slh5p.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/61d70b775f46ed13d8d642a1


Timespan shown in PDF even if not enabled in the theme config since v1.12

Describe the bug
Starting with v1.12, the time span is added in the "Experience" section of the generated PDF, even if it's not enabled in the YAML.

Before: Jan 2023 – present
After: Jan 2023 – present 1 year 7 months

To Reproduce
Comment or remove the show_timespan_in field from the YAML file, then generate the CV and look at the "Experience" section dates in the generated PDF.
Screenshots

Hi, I updated the default version to an empty list in v1.12. Do you think having the default value ["Experience"] was better?

I'm not sure I understand why it's now displayed based on your comment, but on my end, I'd suggest not showing it unless it's enabled in the configuration.

Oh, I thought you meant the opposite (not showing the timespan after v1.12)
Interestingly, the behavior is actually meant to be the opposite. Before v1.12, it should have shown time spans in the "Experience" section; after v1.12, the intention was not to show anything. I just tested it, and you're right. This is broken and not tested properly. I will fix it in the next release.

This issue has been fixed with v1.13.


What is the "name" in layers.py

File "/home/he/projects/EfficientDet-master/layers.py", line 43, in build
dtype=tf.float32)
TypeError: add_weight() missing 1 required positional argument: 'name'
I want to run the "./eval/coco.py",but there have be a error

Could you upgrade tf to 1.15.0?


ion-range doesn't display unless within ion-item (as a custom component)

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/driftyco/ionic-v1)
[ ] 2.x
[X ] 3.x
I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
I'm creating a custom component that has a special handling for ion-range, but when nested inside a component it won't display unless I include the ion-item to surround the ion-range.
Expected behavior:
I expected that I could include a ion-range like a button, or ion-card inside a component without needing a special item to wrap/contain the ion-range - this means my implementation of the component needs to not be inside a ion-item when I use my component (which is odd compared to other ion-xyz items)
Steps to reproduce:
Bit involved to include a plunker type snippet - how would I do that for component bugs??
Related code:
none

Other information:
none
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
global packages:

    @ionic/cli-utils : 1.1.2
    Ionic CLI        : 3.1.2

local packages:

    @ionic/app-scripts              : 1.3.7
    @ionic/cli-plugin-ionic-angular : 1.1.2
    Ionic Framework                 : ionic-angular 3.2.1

System:

    Node       : v6.9.2
    OS         : macOS Sierra
    Xcode      : Xcode 8.3.2 Build version 8E2002
    ios-deploy : 1.9.1
    ios-sim    : 5.0.13

might be related to this bug #10599

this bug/issue seems almost exactly related, but not sure ?? #9080

Hello, thanks for using Ionic! I am going to close this issue as a duplicate of https://github.com/driftyco/ionic/issues/10599.


Will it be released to a NuGet package?

Or I have to copy the code from here in order to use this?

its already avalable,
Refractored.MvvmHelpers

This was just an example of it working basically :)


add new icons

hi all I add new icons

I don't know if you considered reading the README, but the maintainer of this project doesn't accept pull requests for adding icons.

NOTE: To keep icons consistent and to ensure browser support, we don't accept pull requests for icon submissions. If you would like an icon added, please open an issue.

And plus, you provided the Postgres logo in your PR, which already exists as an icon. As the above message suggests, you should open issues for icons you want to add.


bug: infinite loop doesn't revert

Bug Report
Kakarot version:
Current behavior:
Infinite loop executes successfully rather than reverting, and the gas cost is higher than the gas provided.
Expected behavior:
Expected reverted transaction with an error message indicating running out of gas.
Steps to reproduce:

Run a Katana RPC locally using Docker
Deploy the contract with Remix using the "Injected Provider - Metamask" environment
Call the infiniteLoop function in Remix on the deployed contract instance

 function infiniteLoop() public {
        while(true) {
            count++;
        }
    }

Other information:

Environment: Katana, using Remix for testing
Solidity version: 0.8.0

Awesome issue:)! Thanks @richwarner
Adding here reproducing steps:

Go to Remix
Write a Loop contract:

// SPDX-License-Identifier: MIT

pragma solidity >=0.7.0 <0.9.0;

contract Loop {
function infiniteLoop() pure public {
    uint256 count = 0;
        while(true) {
            count++;
        }
    }
}

Compile, Deploy the contract, and run the function. The error should be:

call to Loop.infiniteLoop
CALL
[call]from: 0x5B38Da6a701c568545dCfcB03FcB875f56beddC4to: Loop.infiniteLoop()data: 0x1db...f353d
call to Loop.infiniteLoop errored: VM error: out of gas.

out of gas
	The transaction ran out of gas. Please increase the Gas Limit.

Debug the transaction to get more information.

doesn't it throw an error on katana? does it stay stuck then?

I'm seeing this error in the Madara logs:

Remix is showing a successful transaction:

This issue is a mix of gas accounting and RPC/Katana not returning failure when it was failing.
For gas accounting, there is a whole epic that needs to be handled at some point. For RPC/Katana, we can close this.


No module named 'mlperf_loadgen'

Anaconda:
            shell level : 2
          conda version : 4.12.0
    conda-build version : 3.21.8
         python version : 3.9.12.final.0
       virtual packages : __cuda=11.5=0
                          __linux=5.4.0=0
                          __glibc=2.31=0
                          __unix=0=0
                          __archspec=1=x86_64

In the virtual environment Python is 3.8.13
pip install onnxruntime_olive==0.5.0 --extra-index-url https://olivewheels.azureedge.net/oaas
In the notebook:
from olive.optimization_config import OptimizationConfig
from olive.optimize import optimize

----> 2 from olive.optimize import optimize

File .../lib/python3.8/site-packages/olive/optimize.py:10
      8 from .optimization.optimize_quantization import quantization_optimize
      9 from .optimization.optimize_transformer import transformer_optimize
---> 10 from .optimization.tuning_process import tune_onnx_model, get_benchmark
     11 import logging
     13 logging.basicConfig(level=logging.INFO, format='%(asctime)s - %(name)s - %(levelname)s - %(message)s')

File .../lib/python3.8/site-packages/olive/optimization/tuning_process.py:13
     10 from packaging import version
     12 from .mlperf_dataset import Dataset
---> 13 from .server_runner import ServerRunner
     14 from ..constants import SUB_PROCESS_NAME_PREFIX, ONNX_TO_NP_TYPE_MAP
     16 logging.basicConfig(level=logging.INFO, format='%(asctime)s - %(name)s - %(levelname)s - %(message)s')

File .../lib/python3.8/site-packages/olive/optimization/server_runner.py:6
      3 import time
      4 import array
----> 6 import mlperf_loadgen as lg
      7 import numpy as np
      9 from ..constants import QUERY_COUNT, NANO_SEC, MILLI_SEC

ModuleNotFoundError: No module named 'mlperf_loadgen'

mlperf_loadgen should be automitically installed when olive optimize command be used.
In the notebook senario, it can be installed by pip install --extra-index-url https://olivewheels.azureedge.net/oaas mlperf-loadgen
This will be updated in the tutorial. Thanks for reporting this issue.

Had same issue, that command helped

So u should remove this deprecated tutorial https://github.com/microsoft/OLive/blob/master/notebook-tutorial/Optimize_ONNX_Models_Latency_with_OLive.ipynb

The notebook has been updated with mlperf-loadgen installation link.


Run integration tests in parallel

WIP
CC: @kennknowles

Interesting. I had thought that nonzero parallelism was the default. Is this not true? It certainly does look like this might have sped Jenkins up a bit, though it might just be usual variance.

LGTM & I'd ignore Travis failure.

Though you wrote "WIP" I'd merge ASAP and revise in follow-ups if needed.


updated copyright disclaimer

All rights reserved

What does this do? Not exactly familiar with licences and such, but the MIT license doesn't have this included in the template.

You might need something like this because you are using the LEGO brand. I am not entirely sure how it works that being said, and I don’t think “All rights reserved” is enough in any case.

@HugoGiraudel Yeah, I know nothing about licenses and stuff like this, so I would need to look it up.

sure, why not


Added Carthage support

Separated HCSStarRatingView.{h|m} to framework project, and added to sample project as dependency. Cocoapods will continue working as is.

Hi @almassapargali! Thanks for your PR adding support for Carthage.
I looked around and it seems ok. I just had one request: could you please remove the tests target and files, since they're not required in this library?
If you don't have time it's ok, I can remove it after merging.
Thanks again!

Yep, sure.

On Jul 11, 2015, at 8:50 PM, Hugo Sousa<EMAIL_ADDRESS>wrote:
Hi @almassapargali! Thanks for your PR adding support for Carthage.
I looked around and it seems ok. I just had one request: could you please remove the tests target and files, since they're not required in this library?
If you don't have time it's ok, I can remove it after merging.
Thanks again!
—
Reply to this email directly or view it on GitHub.

Done.

Hi @almassapargali! I tested your solution and the only thing missing is what I wrote in the comment above.
If you want I can merge the PR and make the change afterwards.
Thanks for spotting the bug and helping out with the fix! :+1:


Upgrade to Ralph 4.0

Draft PR until Ralph 4 comes out of beta. Will need further cleanup and testing, as well as these prs to land first:

https://github.com/openedx/aspects-dbt/pull/41
https://github.com/openedx/xapi-db-load/pull/81
https://github.com/openedx/tutor-contrib-aspects/pull/550

This PR is still a WIP, once the related dbt and xapi-db-load PRs land I'll pick it back up. It may require more work in the Superset datasets, I'm not sure yet. cc @SoryRawyer for context.


Cannot find runtime 'next' on PATH. Make sure to have 'next' installed.

This is concerning the next.js recipe, on the next:node mode.

Also, the "official sample app" url doesn't work : git@github.com:now-examples/nextgram.git

Launch.json is literally the one from the readme.
The next:chrome debugger works but only if I start the application myself too, while I would assume it should start it up.

@Blanen not sure if you have resolved that issue of not able to find runtime 'next', but there are two ways to resolve it.

Install next, react and react-dom globally, such that next binary can be found
change your runtimeExecutable parameter to the following:
"runtimeExecutable": "${workspaceFolder}/node_modules/next/dist/bin/next",

Hey there, I created a PR on Next.js docs to have Next.js debugging working in either Chrome DevTools or VSCode, appreciate any feedback you have when trying it out on the PR: https://github.com/zeit/next.js/pull/10807/files?short_path=bfcc096#diff-bfcc096377efef455dd348d059704209
I choosed to only attach to the debugger from VSCode instead of trying to completely launch next from VSCode because in many occasions your Next.js application might be loaded by docker/overmind/foreman/heroku local... Let me know what you think!

I can confirm that following the tutorial at https://github.com/Microsoft/vscode-recipes/tree/master/Next-js doesn't work, I get Cannot find runtime 'next' on PATH. Make sure to have 'next' installed. .
Following above advice and using "runtimeExecutable": "${workspaceFolder}/node_modules/next/dist/bin/next", doesn't work either.
Here is what I get when running 'Next: Node' configuration (or hit F5)
 /Users/vadorequest/dev/next-right-now/node_modules/next/dist/bin/next --inspect

 vadorequest@Ambroises-MBP-001  ~/dev/next-right-now   vscode ● ? ⍟33 
 ✔   /Users/vadorequest/dev/next-right-now/node_modules/next/dist/bin/next --inspect
/Users/vadorequest/dev/next-right-now/node_modules/next/dist/bin/next:25
  `);process.exit(0);}const command=foundCommand?args._[0]:defaultCommand;const forwardedArgs=foundCommand?args._.slice(1):args._;if(args['--inspect'])throw new Error(`--inspect flag is deprecated. Use env variable NODE_OPTIONS instead: NODE_OPTIONS='--inspect' next ${command}`);// Make sure the `next <subcommand> --help` case is covered
                                                                                ^

Error: --inspect flag is deprecated. Use env variable NODE_OPTIONS instead: NODE_OPTIONS='--inspect' next dev
    at Object.<anonymous> (/Users/vadorequest/dev/next-right-now/node_modules/next/dist/bin/next:25:158)
    at Module._compile (internal/modules/cjs/loader.js:1200:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1220:10)
    at Module.load (internal/modules/cjs/loader.js:1049:32)
    at Function.Module._load (internal/modules/cjs/loader.js:937:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
    at internal/main/run_main_module.js:17:47

Shortly followed by

Following the doc at https://github.com/vercel/next.js/pull/10807/files, the process attaches correctly to the running Node.js instance, but it ignores all breakpoints set on TS files (.ts/.tsx)

Next.js recipe has been updated


Space as button key

Hello, I am trying to set space bar as the mouse button. Adding buttons: m , . Space to my config gives an error message ERROR: Space is not a valid key name. Using a lower case space does not throw an error message. However in grid mode pressing space ends grid mode and goes into normal mode but does not perform a click. In normal mode space also does not perform a click but, when on a browser window scrolls. When the config line is not present pressing space does nothing.
Is this expected?

You have an extraneous comma. Key names should be separate by spaces, so you want buttons: m . space. Also note that you've mapped space to right click.

I did take the buttons: m , . straight from the --list-options. I did however not properly read it as I didn't get that this was a mapping of all mouse buttons. I expected it to be just a list of keys I wanted to map to left click. This makes more sense now. With buttons: space , . it works exactly as intended. Thank you!


Add ability to include other files into a jobspec

This is a feature request for a method for including other files into a jobspec.
I would like to deploy a number of services into a single job, and each one requires a static configuration file to run.  I could use heredocs with a template stanza to configure them, but that means putting ALL of the configuration files contents into a single file.
In addition to allowing me to put service configuration files into multiple files, it would generally allow people to split up large or complicated job specs into multiple pieces, and re-use repeated portions of a jobspec.
Example Nomad Job Template
This is an example interface for including files.  I have no attachment to the specific method names or formats for how this would work, but this would satisfy me.
variables.yml:
---
configurationVariables:
  variable: someValue

job.tpl:
job "foo" {
  ...
  group "someGroup" {
    task "someTask" {
      template {
        data = <<EOF
[[ include "configuration.yml.tpl" .configurationVariables ]]
EOF
        destination = "configuration.yml"
      }
    }
  }
}

configuration.yml.tpl:
---
some: rather
large: configuration
file: [[ .variable ]]

Output of running levant render with the above files:
job "foo" {
  ...
  group "someGroup" {
    task "someTask" {
      template {
        data = <<EOF
---
some: rather
large: configuration
file: someValue
EOF
        destination = "configuration.yml"
      }
    }
  }
}

Thanks for the request @cconstantine. The ability to have a template function which attempts to read the file and then add the contents to the section should be doable. Having those contents contain a variable required for substitution will be interesting, that depends heavy on the order of the template rendering which I will attempt to test when working on this for you.


Publish latest version to npm (0.0.4?)

Right now there's 0.0.3, which is missing a few methods that are in this repo (I'm trying to use s3.listObjectsV2).
I think (not knowing your CI setup) that you just need to run a npm publish. Would you mind doing that so I could use the new hotness? 😄

Alex,
You're likely using typings. There's nothing wrong about using typings directly against github, so thats one of the reasons I've stopped publishing to npm.
I might revise this policy, but it depends on enough power of persuasion :)

Persuasive argument: typings search aws-sdk omits your superior type definitions for the aws sdk!

Hmm. I'm actually using this via my package.json:
{
  "devDependencies": {
    "aws-sdk-typescript": "0.0.3"
  }
}

Setting it to "aws-sdk-typescript": "git://github.com/ingenieux/aws-sdk-typescript.git#8393f492", I get this error:
npm ERR! addLocal Could not install /var/folders/sw/bjnnl50n2wz6g0vf9g1cfr180000gn/T/npm-22249-e824e6be/git-cache-a8f7a12e/8393f4928eab3639896198b1ec4c8a797c7e4b45
npm ERR! Darwin 14.5.0
npm ERR! argv "/Users/aturek/.nvm/versions/node/v6.2.1/bin/node" "/Users/aturek/.nvm/versions/node/v6.2.1/bin/npm" "install"
npm ERR! node v6.2.1
npm ERR! npm  v3.9.3

npm ERR! No version provided in package.json
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

https://github.com/ingenieux/aws-sdk-typescript/issues/9 shows how to use it via typings.
There's a forked version on npm right now, which is https://github.com/djabry/aws-sdk-typescript - more updated than this one since I've stopped publishing it to npm.
My #1 concern would be about maintaining parity between AWS and NPM versions, and that would require a lot of effort to get it done right :/

Whoa, I didn't even think to see if the npm module was from a fork. I'll give the typings -> github setup a try

I meant there are two aws-sdk-typescript on npm:
https://www.google.com.co/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=aws-sdk-typescript site%3Anpmjs.com

Alright, future readers, I set up my typings.json to point to the (current latest) hash of this repo:
typings i aws-sdk=github:ingenieux/aws-sdk-typescript#8393f492 --save -G --verbose

@aldrinleal I think I'm good on this, thanks for your help!
Out of curiosity (I'm quite new to Typescript) how do you generate these types? Is this by hand from the AWS package?

Part of it was descended from the original DefinitelyTypings.
Another part was made by reading the aws-sdk json files (in fact, the aws-sdk is basically a stub to those json files)
Later, we've added extra methods: Those declared outside the json files, like S3 Signature Generation. This is made by using esprima to parse the original source files.
And finally, we've reworked the json part to add the relevant jsdoc
(and sources are at https://github.com/ingenieux/aws-sdk-typescript/tree/master/app/src)

Gotcha: You MIGHT need to add to your typings a definition for Promises (e.g. bluebird) as well.

We're already using Bluebird as a global dependency so it just worked for me. Might be necessary for anybody else who stumbles on this issue though

Feel free to donate! I'm saving for my honeymoon!
(and it includes WA)

@igrayson actually the typings registry isn't npm but flat files on github. Will revisit this, ok?
https://github.com/typings/registry/

@aldrinleal I tried to do as described in #9 but ended up with this:
typings i aws-sdk=github:ingenieux/aws-sdk-typescript --save-dev --verbose            10:21:18  ☁  master ☂ ⚡ ✭
typings WARN badlocation "github:ingenieux/aws-sdk-typescript" is a mutable location and may change, consider specifying a commit hash
typings ERR! message Unable to compile "aws-sdk", the typings are meant to be installed as ambient but attempted to be compiled as an external module

typings ERR! stack TypingsError: Unable to compile "aws-sdk", the typings are meant to be installed as ambient but attempted to be compiled as an external module

@galuszkak I'd try installing a system (specially promises) support first.
If others could outline their steps also, it would be awesome as well.

@aldrinleal I'm not quite sure how can I help and what do You mean? Do I need to do something for You?

@galuszkak it needs a definition for promises installed first

@galuszkak I installed it using the command suggested by @alexturek
typings i aws-sdk=github:ingenieux/aws-sdk-typescript#8393f492 --save -G --verbose
The error you get suggests that typings is expecting a commit hash i.e. #8393f492 along with the global flag -G

Using #HEAD also works


What's the point of c.n.h.c.RequestCollapserFactory.defaultNameCache

Doesn't seem to be used, but has a relatively obtuse comment attached.

If you look in a few other places in the codebase, AbstractCommand, HystrixCollapser, HystrixObservableCollapser, this pattern is used to safely turned a j.u.Class into a String once per-class, rather than on every command/collapser invocation.
So the pattern is valid, but I agree with you that the data structure you pointed out is unused.  Do you want to submit a PR with its removal, or shall I?  Thanks for all the cleanup efforts!


gitea / gogs support

It would be nice to have support for gitea and gogs (they share the same API afaik).
I guess another API client library like megam_gogs or a Swagger client for the exposed API would be required for that.
For others seeking dependency update support: you could use renovatebot, for now.

Happy to accept PRs for this, but the core team won't be undertaking this.

No need to close it. I'm still interested in it. 😉

Due to current resourcing, we're not accepting PRs on dependabot-core. However, we expect to accept PRs in the future and would be open to a PR to add this functionality. Closing this issue for now.

But can't you keep this issue open even if you don't accept a PR right now?
This way other users can find and track this issue as well.


please add some comments to your code

new to javascript, can't make any sense of the code. A few comments to explain what is happening where would make the code much more usable and sharable.

This is an ongoing effort via PR feedback to ensure any new code is commented. I'll be closing this now as there isn't a specific areas of ask, feel free to reopen or post a new issue and link to parts of code that you think will benefit from comments, happy to work on specific asks.


[Fix] [UI Next][V1.0.0-Alpha] Fix the pre task options missing  in dag page.

Purpose of the pull request
This pull request fixs the pre task options missing  in dag page.
Releated issues
close #8869

Codecov Report

Merging #8876 (3d77b8a) into dev (3bbca9d) will decrease coverage by 0.01%.
 Consider uploading reports for the commit 8feb493 to get more accurate results

@@             Coverage Diff              @@
##                dev    #8876      +/-   ##
============================================
- Coverage     45.30%   45.28%   -0.02%
+ Complexity     4083     4080       -3
============================================
  Files           702      702
  Lines         27177    27177
  Branches       2907     2907
============================================
- Hits          12313    12308       -5
- Misses        13704    13706       +2
- Partials       1160     1163       +3

Impacted Files
Coverage Δ

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.70% <0.00%> (-2.82%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3bbca9d...8feb493. Read the comment docs.


Runtime Error: cudaErrorInvalidDevice

Hi, there is a runtime error when executing ''python dreamplacefpga/Placer.py test/FPGA-example1.json'' whether enable GPU or not.

I build env by docker.
May I know if I can get some suggestion?
Thanks for your help.

Sorry, the error only happens when enable GPU

Closing issue for now.
Please reopen if you have issue when running on a GPU machine.


Brazilian Portuguese translation of Intermediate Algorithm Scripting

[ ] Sum All Numbers in a Range
[ ]  Diff Two Arrays
[ ]  Roman Numeral Converter
[ ]  Where art thou
[ ]  Search and Replace
[ ]  Pig Latin
[ ]  DNA Pairing
[ ]  Missing letters
[ ]  Boo who
[ ]  Sorted Union
[ ]  Convert HTML Entities
[ ]  Spinal Tap Case
[ ]  Sum All Odd Fibonacci Numbers
[ ]  Sum All Primes
[ ]  Smallest Common Multiple
[ ]  Finders Keepers
[ ]  Drop it
[ ]  Steamroller
[ ]  Binary Agents
[ ]  Everything Be True
[ ]  Arguments Optional

Working on it

Closed in favor of https://github.com/FreeCodeCamp/TranslationExpansion/issues/52


As part of user story #71 updating the README.md file

As part of user story #71 updating the README.md file

Nice job. Thanks for adding information about the key binding to the README.md file.


It's weird that futures appears (and that it appears as incompatible with Python 3)

futures is a backport of a Python 3 standard library module, so it's a bit of a special case, but its latest version says "It should not be installed on Python 3, although there should be no harm in doing so, as the standard library takes precedence over third party libraries.". Doesn't that text suggest that it shouldn't appear white in the compatibility list?
Somewhat separately: given that futures is useful on 2.7 only, should it particularly matter whether or not it is compatible with Python 3? Should it even appear in the list at all, whether in green or in white?
Does the text "Green packages support Python 3 (or has drop in replacement package which supports Python 3)" play any role for futures, given that its drop-in replacement not only exists, but is part of Python 3 itself?

This sites uses caniusepython3 to decide if something is ready:
$ caniusepython3 --projects futures
Finding and checking dependencies ...

You need 1 project to transition to Python 3.
Of that 1 project, 1 has no direct dependencies blocking its transition:

  futures

https://github.com/brettcannon/caniusepython3#how-do-you-tell-if-a-project-has-been-ported-to-python-3 says:

How do you tell if a project has been ported to Python 3?
On PyPI each project can specify various
trove classifiers
(typically in a project's setup.py through a classifier
argument to setup()).
There are various classifiers related to what version of Python a project can
run on. E.g.:
Programming Language :: Python :: 3
Programming Language :: Python :: 3.0
Programming Language :: Python :: 3.1
Programming Language :: Python :: 3.2
Programming Language :: Python :: 3.3
Programming Language :: Python :: 3.4
Programming Language :: Python :: 3.5
Programming Language :: Python :: 3.6

As long as a trove classifier for some version of Python 3 is specified then the
project is considered to support Python 3 (project owners: it is preferred you
at least specify Programming Language :: Python :: 3 as that is how you
end up listed on the Python 3 Packages list on PyPI;
you can represent Python 2 support with Programming Language :: Python).  Note
that Python 3.0 through 3.3 have reached their End Of Life.
The other way is through a manual override in
caniusepython3 itself. Projects ends up on this list because:

They are now part of Python's standard library in some release of Python 3
Their Python 3 port is under a different name
They are missing a Python 3 trove classifier but have actually been ported

If any of these various requirements are met, then a project is considered to
support Python 3 and thus will be added to the manual overrides list. You can
see the list of overrides when you use caniusepython3's CLI with verbose output
turned on.

Futures declares itself as only compatible for Python 2:
"Programming Language :: Python :: 2.6",
"Programming Language :: Python :: 2.7",
"Programming Language :: Python :: 2 :: Only"

https://pypi.org/pypi/futures/json
But it sounds like it meets caniusepython3's third requirement for going on the override list. Please file a PR or issue over there: https://github.com/brettcannon/caniusepython3#what-if-i-know-of-a-project-that-should-be-added-to-the-overrides-file

futures is in the overrides file in caniuse: https://github.com/brettcannon/caniusepython3/commit/fbf6360a5e5c487984605d543f0623b9a7058bfb it's been there for years. either the version running here is very old or something fishy is going on.

a similar issue occurs with beautifulsoup, FWIW.

@brettcannon: what was stale about futures in "Clear out stale overrides?

They probably had a trove classifier for Python 3 that they subsequently dropped.

Here's a PR to re-add futures to the overrides: https://github.com/brettcannon/caniusepython3/pull/187.

https://github.com/brettcannon/caniusepython3/pull/187 is now merged and futures is no longer a Python 3 blocker:
$ caniusepython3 --projects futures
Finding and checking dependencies ...

🎉  You have 0 projects blocking you from using Python 3!

Here's a static build of py3readiness and futures is now green:
https://hugovk.github.io/py3readiness/

...

@nathanielmanistaatgoogle This issue can now be closed, thanks for raising it!

Woohoo! Thanks much!

whoohoo! this means all 120 (120? why not 100! :) most popular packages in PyPI are now green! congratulations on everyone on making this happen!

Both python-augeas and pandocfilters support Python 3, the classifiers will be in their next releases.
https://github.com/hercules-team/python-augeas/commits/master/setup.py
https://github.com/jgm/pandocfilters/commits/master/setup.py


fix for ssh on firefox

While Math.random is not a good long-term solution, I couldn't find any other synchronous solution.

:thumbsup: (though this makes me want to cry a bit)

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from the review on Reviewable.io


Loosen rouge dependency

Rouge is locked to ~> 2, meaning anything using this gem won't be able to use the current Rouge 3.x series of releases.
The last version of Rouge in the 2.x series was released in August 2017.

Nvm, this was done with 0.1.6. Somehow I got stuck on the previous version.


Use STDIN/STDOUT if -i/-o are not specified

The command line arguments look more natural to use STDIN and STDOUT if -i and -o are not passed as arguments, respectively.

how should we handle different formats for stdin?

That's a good point. I wasn't aware that. Adding another option to specify the file format solves this, but just making the options complicated.
So, requiring -i option is ok, and please ignore my idea to use STDIN.


python312Packages.anova-wifi: 0.17.0 -> 0.17.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.anova-wifi is: Python package for reading anova sous vide api data
meta.homepage for python312Packages.anova-wifi is: https://github.com/Lash-L/anova_wifi
meta.changelog for python312Packages.anova-wifi is: https://github.com/Lash-L/anova_wifi/releases/tag/v0.17.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.17.1 with grep in /nix/store/259r0925vgda5xf3zzmi649cpam5ir0c-python3.12-anova-wifi-0.17.1
found 0.17.1 in filename of file in /nix/store/259r0925vgda5xf3zzmi649cpam5ir0c-python3.12-anova-wifi-0.17.1

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

home-assistant-component-tests.anova
python311Packages.anova-wifi
python312Packages.anova-wifi

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/259r0925vgda5xf3zzmi649cpam5ir0c-python3.12-anova-wifi-0.17.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.anova-wifi https://github.com/r-ryantm/nixpkgs/archive/c970af32c6af35b6d662a4492398909bacbbb3af.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c970af32c6af35b6d662a4492398909bacbbb3af#python312Packages.anova-wifi

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/259r0925vgda5xf3zzmi649cpam5ir0c-python3.12-anova-wifi-0.17.1
ls -la /nix/store/259r0925vgda5xf3zzmi649cpam5ir0c-python3.12-anova-wifi-0.17.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.anova
python311Packages.anova-wifi
python311Packages.anova-wifi.dist
python312Packages.anova-wifi
python312Packages.anova-wifi.dist

Maintainer pings
cc @JamieMagee for testing.

Add a :+1: reaction to pull requests you find important.

duplicate of https://github.com/NixOS/nixpkgs/pull/333095


Stratux software failed to start after upgrade

I have a Raspberry PI3 and Jessie light.
uname -a Linux raspberrypi 4.9.24-v7+ #993 SMP Wed Apr 26 18:01:23 BST 2017
I use stratux-setup for the installation and the updates. Everything was working fine.
Try to update the stratux software today by running
cd /root/stratux-setup
git pull
bash stratux-setup.sh
After the reboot, the stratux process don't start.
From the syslog
May 24 04:28:19 raspberrypi systemd[1]: Starting Stratux...
May 24 04:28:19 raspberrypi systemd[1]: Started Stratux.
May 24 04:28:19 raspberrypi gen_gdl90[4296]: 2017/05/24 04:28:19 Stratux ahrs0.5.1 (bc54533351d03c34ad5eb300c422308bbc3a1660) starting.
May 24 04:28:19 raspberrypi gen_gdl90[4296]: 2017/05/24 04:28:19 read in settings.
May 24 04:28:19 raspberrypi gen_gdl90[4296]: 2017/05/24 04:28:19 Entered uatReader() ...
May 24 04:28:19 raspberrypi gen_gdl90[4296]: panic: embd: your host ": ARMv7 Processor rev 4 (v7l)" is not supported at this moment. request support at https://github.com/kidoman/embd/issues
May 24 04:28:19 raspberrypi gen_gdl90[4296]: goroutine 1 [running]:
May 24 04:28:19 raspberrypi gen_gdl90[4296]: panic(0x4d7b80, 0x10ac4078)
May 24 04:28:19 raspberrypi gen_gdl90[4296]: /root/go/src/runtime/panic.go:500 +0x33c
May 24 04:28:19 raspberrypi gen_gdl90[4296]: github.com/kidoman/embd.NewI2CBus(0x10a67e01, 0x0, 0x0)
May 24 04:28:19 raspberrypi gen_gdl90[4296]: /root/go_path/src/github.com/kidoman/embd/i2c.go:75 +0x60
May 24 04:28:19 raspberrypi gen_gdl90[4296]: main.initI2CSensors()
May 24 04:28:19 raspberrypi gen_gdl90[4296]: /root/stratux/main/sensors.go:30 +0x1c
May 24 04:28:19 raspberrypi gen_gdl90[4296]: main.main()
May 24 04:28:19 raspberrypi gen_gdl90[4296]: /root/stratux/main/gen_gdl90.go:1437 +0xb90
May 24 04:28:19 raspberrypi systemd[1]: stratux.service: main process exited, code=exited, status=2/INVALIDARGUMENT
May 24 04:28:19 raspberrypi systemd[1]: Unit stratux.service entered failed state.
May 24 04:28:24 raspberrypi systemd[1]: stratux.service holdoff time over, scheduling restart.
May 24 04:28:24 raspberrypi systemd[1]: Stopping Stratux...
Any idea what went wrong?
Thanks

I have this problem as well.
Stratux 1.2.r2, uname -a gives:
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
It was running fine this AM, then I did a sudo apt-get upgrade and it went into the state above.  I'll have to try rolling back to a fresh burn of 1.2r2 and see if that fixes it.


Modify /bookmarks view to use icon with link to jump to message

Add icon with link to take user to the post in MM.

[x] user can right click and copy the link and use for /bookmarks add and /bookmarks remove
[x] remove bullets to free up horizontal space for title and icons.
[x] If cannot use the copied link in add and remove commands, fix, or create another issue.

for now, using :link: :link:, but might need to use an asset to ensure MM account has emojis.

commit https://github.com/jfrerich/mattermost-plugin-bookmarks/commit/1b6c78132399b828ae114c72ff63f27a17d9b10e


Volume Policy to stick the replicas to K8s node

It will be good to have the openebs replicas stick to a K8s node once they are placed due to various data gravity reasons.
Refer:

NodeSelector
PodNodeSelector Admission Controller

fixed in #1310


Marvel and Kibana Mismatch

plugin:marvel 	Marvel version 2.2.0 is not supported with Kibana 4.3.1
error on current build of the ROCK

Please test now that we've merged PR #34.  It's working in my testing.

fixed.

Fix verified by third party.


Start-Process: The parameter '-Verb' is not supported for the cmdlet 'Start-Process' on this edition of PowerShell.

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Environment data
C:\>pwsh.exe -v
PowerShell 7.2.5

### OS Data

```powershell
nanoserver-1809

Windows update log
Get-WindowsUpdateLog: The term 'Get-WindowsUpdateLog' is not recognized as a name of a cmdlet, function, script file, or
 executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Visuals
No response

The default user on nano server should have the permissions you need.  If choco is telling you need to run as admin, that code needs to special case nano.


SCRUM-3290 (update) Fix 'failed to lazily initialize a collection' error

@adamgibs @oblodgett Any idea why the UI tests are failing here.  I can't make much sense of the logs!

UI tests are passing locally

@markquintontulloch That's really, odd. I've just started them again, but they shouldn't be failing since the only changes were on the backend.

Hmm, I ran make all in src/main/cliapp, followed by npm test and now I get:
FAIL  src/containers/conditionRelationPage/__tests__/ConditionRelationTable.test.js
 ● Test suite failed to run

   Cannot find module<EMAIL_ADDRESS>from<EMAIL_ADDRESS>
   Require stack:
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>     src/containers/conditionRelationPage/__tests__/ConditionRelationTable.test.js

     at Resolver.resolveModule (node_modules/jest-resolve/build/resolver.js:324:11)
     at Object.<anonymous> (node_modules/@testing-library/user-event/dist/cjs/utils/misc/getWindow.js:5:18)

Test Suites: 1 failed, 16 passed, 17 total`

@markquintontulloch @adamgibs do these tests fail locally?

So ya these fail for me locally...
cd agr_curation/src/main/cliapp
rm -fr node_modules
rm  package-lock.json
npm install --legacy-peer-deps
npm test -- --watchAll=false -> FAIL

@oblodgett They are passing for Adam and myself locally after adding "@testing-library/dom": "^9.3.1" to src/main/cliapp/package.json


Automatically invalidate Cloudfront distribution on S3 uploads

Currently, change to the files underlying https://doc.smpte-doc.org/ag-03/main takes 15 mins or more to propagate.

Added lambda function triggered by S3 PUT


Add options for bypassing various translations

This would be useful for bypassing block-scope translation when just running ES6 code directly on node/iojs.

:+1:

:+1: very interested in this feature.

@yukulele @0x8890 How would you like to see this feature exposed?
We could have flags for each individual translation feature, or we could could have some kind of "target" argument, that would be smart about what a particular target supports.

I think that flags for individual features would be good. Build targets would be kind of a pain to maintain, though it would be more convenient.

agree with @0x8890

I just wanted to add that for Node v4.0 (or recent chromium/chrome), the only things that I would care about compiling down:

default function parameters
es6 module syntax
destructuring assignment
spread operator

I just wanted to add that for Node v4.0 (or recent chromium/chrome), the only things that I would care about transpiling:

default function parameters
es6 module syntax
destructuring assignment
spread operator

@0x8890 Node v4 supports classes in strict mode (and ES6 modules are always strict mode), and everything else except modules is currently being developed for V8.
https://www.chromestatus.com/features#category: JavaScript

oops, I read this compatibility table and just assumed that it was hiding behind a flag.


Use Math.floor to ignore mtime precision beyond ms

Round the mtime as a workaround for https://github.com/sindresorhus/gulp-changed/issues/77

For what it’s worth, I can reproduce #77 locally, and can confirm that this PR fixes the issue. Thanks, @gavinaiken!

I would use Math.round, because of:
sourceFile.stat.mtimeMs vs targetStat.mtimeMs:
1562768451079.8008 vs<PHONE_NUMBER>080


Run On Android?

I have been trying connect using android... but it only detected as standard joystick... or do I need  use specific phone?

I just found the list android compatible with HiD but my phone is not in the list? does anyone who has this model in the list has try it?
link of the list:
https://www.hidglobal.com/mobile-access-compatible-devices

The WebHID API is not launching on Android, so even if your phone would support HID access, it's not exposed to the Web browser.


Remove possibly redundant clause in loop alias

Again, I could be completely missing something here but it seems like running monitor-cgm on the left hand side isn't actually doing anything.  It would get the latest glucose entries only to have them deleted in the preflight step and then monitor-cgm would be run again inside of gather.  It's harmless I guess but possibly confusing?  Or again maybe I'm missing something.

Yes, I think you're correct here.  We also need to fix the || echo No CGM data. part: that should say something more generic like "Loop failure" or similar.  Want to make that change as well before I merge?

@scottleibrand yes I was thinking that too.  Done!


5.1: Eagerloading performance is bad for many_many relations

In this specific set up, eager loading is really really really bad for performance. ~1second page load without eager loading, execution time of 30seconds is hit and PHP times out with eager loading.
Here's what I've got running:
Edit: I've simplified this based on my findings - so long as you're using the 5 branch of framework the composer dependencies are irrelevant so I've removed that snippet entirely.
Team.php
<?php

use SilverStripe\ORM\DataObject;

class Team extends DataObject
{
    private static $db = [
        'Name' => 'Text'
    ];

    private static $many_many = [
        'Players' => Player::class
    ];
}

Player.php
<?php

use SilverStripe\ORM\DataObject;

class Player extends DataObject
{
    private static $db = [
        'Name' => 'Text',
    ];

    private static $belongs_many_many = [
        'Teams' => Team::class,
    ];
}

_config.php
<?php
// // Create fixtures - 1000 teams, 10 players per team for a total of 10,000 players
// $count = Team::get()->count();
// for ($x = $count; $x < 1000; $x++) {
//     $team = Team::create(['Name' => $x]);
//     $team->write();
//     for ($y = 0; $y < 10; $y++) {
//         $player = Player::create(['Name' => $x . '_' . $y]);
//         $player->write();
//         $team->Players()->add($player);
//     }
// }

$teams = Team::get();
$teams = $teams->eagerLoad('Players');

foreach ($teams as $team) {
   foreach ($team->Players() as $player) {
        echo ''; // just need something here to ensure PHP doesn't optimise out the loops
   }
}

PRs

https://github.com/silverstripe/silverstripe-framework/pull/10855

Linked PR has been merged


Update geo

cargo test passed; that was the extent of my validation

Thanks! Tagged and published to crates as v3.1.0


pommed_light: 1.50lw -> 1.51lw

Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:

built on NixOS
ran /nix/store/yny32js35aqyd4rff303cand5a4w2g90-pommed-light-1.51lw/bin/pommed -v and found version 1.51lw
found 1.51lw with grep in /nix/store/yny32js35aqyd4rff303cand5a4w2g90-pommed-light-1.51lw
directory tree listing: https://gist.github.com/efc712cdbd038d8f65b17ef4670992de

No attempt on x86_64-darwin
The following builds were skipped because they don't evaluate on x86_64-darwin: pommed_light
No log is available.

Failure on aarch64-linux (full log)
Attempted: pommed_light
Partial log (click to expand)
gcc -g -O2 -Wall  -I/nix/store/g5gqrmz6521r1jqcnlnx42zbwqaqhrwp-alsa-lib-1.1.5-dev/include -I/nix/store/g5gqrmz6521r1jqcnlnx42zbwqaqhrwp-alsa-lib-1.1.5-dev/include/alsa -I/nix/store/pyh2bgnf5hm4m5bjcp5ihf4gzdgli8x1-audiofile-0.3.6/include -I/nix/store/fs1qhvq55mxf46jflj8mzm87sidnmjcw-confuse-2.7/include  -I/nix/store/0p16yapigagqly3iqxxi15k2824i8v5p-pciutils-3.5.6/include   -c -o mactel/x1600_backlight.o mactel/x1600_backlight.c
mactel/x1600_backlight.c:27:10: fatal error: sys/io.h: No such file or directory
 #include <sys/io.h>
          ^~~~~~~~~~
compilation terminated.
make[1]: *** [<builtin>: mactel/x1600_backlight.o] Error 1
make[1]: Leaving directory '/build/pommed-light-1.51lw/pommed'
make: *** [Makefile:8: pommed] Error 2
builder for '/nix/store/x5ky6qa4i10xl7jzmiy9rlzyflrdz9jf-pommed-light-1.51lw.drv' failed with exit code 2
error: build of '/nix/store/x5ky6qa4i10xl7jzmiy9rlzyflrdz9jf-pommed-light-1.51lw.drv' failed

Success on x86_64-linux (full log)
Attempted: pommed_light
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/yny32js35aqyd4rff303cand5a4w2g90-pommed-light-1.51lw
shrinking /nix/store/yny32js35aqyd4rff303cand5a4w2g90-pommed-light-1.51lw/bin/pommed
gzipping man pages under /nix/store/yny32js35aqyd4rff303cand5a4w2g90-pommed-light-1.51lw/share/man/
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/yny32js35aqyd4rff303cand5a4w2g90-pommed-light-1.51lw/bin
patching script interpreter paths in /nix/store/yny32js35aqyd4rff303cand5a4w2g90-pommed-light-1.51lw
checking for references to /build in /nix/store/yny32js35aqyd4rff303cand5a4w2g90-pommed-light-1.51lw...
/nix/store/yny32js35aqyd4rff303cand5a4w2g90-pommed-light-1.51lw


fix: Fix the incorrect null joined rows for SMJ outer join with join filter

Which issue does this PR close?

Closes #10882.
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

Possibly related to https://github.com/apache/datafusion/issues/10881

Possibly related to #10881

Hmm, I don't see smj is explicitly enabled there?

Thank you @alamb @comphead. Let me resolve the conflicts before merging.

Thanks @viirya  and @comphead


TC737 - Log in to Uhuru

When trying to login to Uhuru with my ThreeFold Connect app, getting the error that the account doesn't yet exist

@ramezsaeed could we got some more info?
What env/url is this, what is the user's 3botname exactly? Any console logs/network calls? Any repro steps to trigger this?

Just checked on my end, the account dmitrialleo simply doesn't exist on TF connect, so the error is normal.
First you need to create a TF connect account before logging in. The error clearly communicates this as well.

@ken-de-moor yes, you are right,
my apologies, it's dimitrialleo,
Now I have managed to log in, will test from there on


Fix 100% CPU Usage in miner

Currently CreateNewBlock has a if/else statement to "attempt to find a coinstake", if it is PoS and there is no coinstake to be had, it will fall through to the end of the function.
The check for IsProofOfStake() && fProofOfStake will return null.
The miner thread will just loop with no sleep(100% cpu) as pblock is null.   So we are sitting at 100% cpu until we can create a coinstake.
Any amount of sleep will work, 200msec, 500msec, a second, anything that will allow the thread to sleep instead of runaway.

nice find. thank you


Include counter-signature hash algorithm into SignedData.digestAlgorithms

Hello,
RFC 5652 highly recommends to add used hash algorithms within the SignedData.digestAlgorithms field:

digestAlgorithms is a collection of message digest algorithm identifiers.
...
Implementations MAY fail to validate signatures that use a digest algorithm that is not included in this set.

and

The message digest algorithm SHOULD be among those listed in the digestAlgorithms field of the associated SignerData.

However, with BC I have a problem to fulfil this requirement when working with counter-signatures.
When I create a counter-signature with a hash algorithm different from the one used in the main signature, the produced CMSSignedData does not contain the new hash algorithm and I do not see a way to add it.
The code what I use to create a counter-signature is:
SignerInformationStore signerInformationStore = originalCMSSignedData.getSignerInfos();
List<SignerInformation> result = new LinkedList<>();
for (SignerInformation signerInformation : signerInformationStore) {
    CMSSignedDataGenerator cmsSignedDataGenerator = *build the generator*;
    SignerInformationStore counterSignatureSignerInfoStore = CMSUtils.generateCounterSigners(cmsSignedDataGenerator, signerInformation);
    result.add(SignerInformation.addCounterSigners(signerInformation, counterSignatureSignerInfoStore));
}
CMSSignedData updatedCMSSignedData = CMSSignedData.replaceSigners(originalCMSSignedData, new SignerInformationStore(result));

The resulting updatedCMSSignedData does not contain the hash algorithm used to create the counter-signature, which is stored within a SignerInformation object corresponding to the counter-signature.
The method CMSSignedData.replaceSigners(...) collects all digest algorithms from the SignerInformations, therefore it collects the algorithms in case of parallel signatures, however it does not take counter-signatures into account.
Would be nice to collect the algorithms from counter-signatures as well, especially that the code could be adapted easely:
Iterator it = signerInformationStore.getSigners().iterator();
while (it.hasNext()) {
    SignerInformation signer = (SignerInformation)it.next();
    digestAlgs.add(CMSSignedHelper.INSTANCE.fixAlgID(signer.getDigestAlgorithmID()));
    SignerInformationStore counterSignaturesStore = signerInformation.getCounterSignatures();
    Iterator<SignerInformation> counterSignatureIt = counterSignatureStore.iterator();
    while (counterSignatureIt.hasNext()) {
        SignerInformation counterSigner = counterSignatureIt.next();
        digestAlgs.add(CMSSignedHelper.INSTANCE.fixAlgID(counterSigner.getDigestAlgorithmID()));
    }
    vec.add(signer.toASN1Structure());
}

Or, as an alternative, a new method, similar to CMSSignedData.replaceCertificatesAndCRLs(...) could be added, allowed replacing the digestAlgorithms field value.
If another solution is possible, I would appreciate any help as well.
Thank you.
Best regards,
Aleksandr.

So, I've done this, as it's probably an improvement and does no harm. A word of caution though, I'm not entirely sure the interpretation is correct though as the purpose of digestAlgorithms is to allow for 1 pass processing of encapsulated signed data. This isn't required for countersignatures, but it very helpful if you have to stream your way through a gig of BER encoded data to get to the signers. For this reason I would not assume that counter signatures would be represented in the digestAlgorithms field as for large objects it will involved rewriting the start of the structure because of a change made to the end of it.
Update should appear here shortly and just made the cut for 1.69.

Thanks! Seems very good!
Regards,
Aleksandr.


Shared inteerrupts on M0 are not supported

The current code will work if one of the modules which shares the interrupt use it. However if both register the interrupt the compiler will issue an error. We need a work around eventually.

after ISR handling redesign to support multiple interrupts in one device shared interrupts should be easy in the form of an additional step in compiling the list of ISRs which accesses a traits class refined in a chip file to provide proper handling. We can also only switch on proper handling when there actually are two ISRs trying to register in the slot.


Breaking out the Frontend.hs file into bite-size chunks

Fixes #69
All new sections of the site should go in their own haskell file now.
There is one question, do people think that all of the handler haskell files should go in their own folder under the frontend folder? I thought that the paths and modules names would be too long then, but if people think it would be too cluttered, I can change that and add it to this pr.

I'm just gonna throw out that I really like this.

Don't merge this until I update the documentation related to the frontend to reflect the new changes in frontend workflow.
Still review it, though.

Okay, documentation should be all set.

Okay, documentation should be all set.


Tcpvcon to show Local and Remote Ports

Both the -c CSV and default output of tcpvcon, tcpvcon64, tcpvcon64a do not print local and remote port numbers. Please consider this as feature request.
NOTE: tcpvcon and variants V. 2.54 had this feature.

At some time in the past this utility had shown the ports (alongside the ip, conon separated) and then they have been removed.  It smells like a bug. Tcpvcon becomes pointless without the ports.