Implement DocValueAggregator for HLL DISTINCT.

Summary of the changes / Why this improves CrateDB
Result of running ./compare_run.py --v1 branch:master --v2 branch:baur/hll-docvalueaggregator --spec specs/select/hyperloglog.toml --forks 2 --env CRATE_HEAP_SIZE=2g -s path.data=/Users/baur/benchmark-data
# Results (server side duration in ms)
V1: 4.6.0-41b3579b7049130cedd542077eabddb666ff7311
V2: 4.6.0-a40419673ac591c22d72252cea1d769b611699c3

Q: select hyperloglog_distinct("cCode") from uservisits
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |      422.632 ±  171.659 |    373.643 |    393.606 |    401.293 |   1596.161 |
|   V2    |      338.015 ±  166.400 |    300.876 |    304.461 |    314.744 |   1464.700 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -  22.25%                           -  25.54%
There is a 98.60% probability that the observed difference is not random, and the best estimate of that difference is 22.25%
The test has statistical significance

Q: select hyperloglog_distinct("visitDate") from uservisits
C: 1
| Version |         Mean ±    Stdev |        Min |     Median |         Q3 |        Max |
|   V1    |      101.696 ±   36.188 |     90.875 |     96.032 |     98.174 |    351.191 |
|   V2    |       42.695 ±   22.822 |     37.574 |     38.818 |     39.590 |    199.010 |
├---------┴-------------------------┴------------┴------------┴------------┴------------┘
|               -  81.72%                           -  84.85%
There is a 100.00% probability that the observed difference is not random, and the best estimate of that difference is 81.72%
The test has statistical significance

System/JVM Metrics (durations in ms, byte-values in MB)
    |    YOUNG GC            |       OLD GC           |      HEAP         |     ALLOC
    |  cnt      avg      max |  cnt      avg      max |  initial     used |     rate      total
 V1 |   36     2.76     1.74 |   12    39.74    37.11 |     2147       66 |     0.00          0
 V2 |    7     3.56     2.70 |    3    37.83    40.72 |     2147      101 |     0.00          0

V1 top allocation frames
  ByteBuffer.get(...):2958
  MurmurHash3.hash64(...):567
  UnicodeUtil.UTF8toUTF16(...):519
  AggregateCollector.iterate(...):507
  InputRow.get(int):440
V2 top allocation frames
  ByteBuffer.get(...):2734
  MurmurHash3.hash64(...):441
  Buffer.position(int):320
  ScopedMemoryAccess.getByteInternal(...):316
  DocValuesAggregates.getRow(...):280

Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

set default precision to 18 (maximal possible), error is still big.
cr> select count(name) from test;
+-------------+
| count(name) |
+-------------+
|      100000 |
+-------------+
SELECT 1 row in set (0.052 sec)
cr> select count(distinct name) from test;
+-------------------------------------+
| collection_count(collect_set(name)) |a
+-------------------------------------+
|                               71097 |
+-------------------------------------+
SELECT 1 row in set (0.093 sec)a
cr> select hyperloglog_distinct(name) from test;
+----------------------------+
| hyperloglog_distinct(name) |
+----------------------------+
|                      99874 |
+----------------------------+

I added benchmark results to the PR description. However, compare_py produced 2 results, I picked up the last one. Judging by logs it did the whole cycle (switching branch, building, running 2 different queries) twice - probably because of  --forks 2.
DocValueAggregation looks better,  UnicodeUtil.UTF8toUTF16 allocation frame has gone

Added DocValueAggregatr for integral types, added dedicated test case which was failing before when I had only 1 aggregator for internal + floating point numbers. Added test case with random type and values


Towards v1

Thanks to @apstndb and others' contributions, this library is more stable and compatible with GoogleSQL. Therefore, it's time to release v1 of memefish.
In doing so, we share some concerns.

How do we manage CHANGELOG or release notes? How is it standard practice in Go?
More breaking changes to ASTs will probably continue in the future. In that case, would it be convenient for users to bump the major version based on semver?

But if not, when should the major version be increased?

It is hard to release v1 as long as any changes to Spanner would cause breaking changes. We close this issue for now.

My thought:
We shouldn't release v1 because Go modules are strictly required to follow SemVer.
https://go.dev/doc/modules/version-numbers#major-version
memefish can't control Google's release, so we need more breaking changes.
It is better to develop as v0.x.y.
I think there is no blocker of v0.1.0 release.


[RL Unplugged] Is the data stored chronologically? Or how to retrive sequential data?

Hi,
Thanks for your nice work. I want to train an RNN agent with sequential data and I tested it with dm_control_suite. The paper mentioned that: "For sequence data, we also provide future states, actions, and rewards, which allows for training recurrent models for tasks requiring memory." But I can only get data with format (s,a,r,s', a') even I set sarsa=False when calling dataset() function as what you did in the dm_control_suite_crr.py, which also uses an RNN agent. Also, I printed out the data you fed into the CRRLearner, it's also in sarsa format with shape [batch_size, 2, state_size]. And I tried the data loader without calling shuffle(), the retrieved data is still shuffled.
So I want to know: 1. is the data stored chronologically? 2. can we get sequential data to train an RNN agent?
Thanks a lot!

Dunno if this helps.  I'm certain the data is not stored chronologically in atari.  Iterating in order over the non-shuffled data doesn't appear to be chronological.  Also the "discount" field doesn't appear to capture terminal states.  I checked 700,000 states of the Asterix example, and the value was always 1.0.


How this two sentence are so similar

Sentence 1" - "Airtel is a big reputed telecom company.  I would be proud to work for a company with such a long history of leadership in the telecom industry. Leaders of airtel are someone to look upto. They are highly professional and very innovative. Millions of customers are in airtel network and I want to make a necessary contribution in service. big platform with lots of opportunities. I heard about your company good culture, employee benefits.- As it is the largest telecom it will definitely help in the growth of my career. Want a career change, to reallocate, big branded company.",
Sentence 2" - "in april 2015 acquired a delhi-based mobile marketing automation firm"
Vectors are calculated using USE-large version 3
**Cosine similarity between this two sentence is ** - 0.65
Can someone tell me how this two-sentence so similar.

This two-sentence are not at all relevant to each

@dheerajiiitv,
In order to expedite the trouble-shooting process, please provide a code snippet to reproduce the issue reported here. Thanks!

@dheerajiiitv USE is mainy used to find the semantic textual similarity between the sentences. I tried to visualize the similarity between the embededding of the sentences given below here.
messages = [
# Smartphones
"I like my phone",
"My phone is not good.",
"Your cellphone looks great.",
# Weather
"Will it snow tomorrow?",
"Recently a lot of hurricanes have hit the US",
"Global warming is real",

#company1
"Airtel is a big reputed telecom company. I would be proud to work for a company with such a long history of leadership in the telecom industry. Leaders of airtel are someone to look upto. They are highly professional and very innovative. Millions of customers are in airtel network and I want to make a necessary contribution in service. big platform with lots of opportunities. I heard about your company good culture, employee benefits.- As it is the largest telecom it will definitely help in the growth of my career. Want a career change, to reallocate, big branded company."

# Food and health
"An apple a day, keeps the doctors away",
"Eating strawberries is healthy",
"Is paleo better than keto?",

# Asking about age
"How old are you?",
"what is your age?",

#company
"in april 2015 acquired a delhi-based mobile marketing automation firm"

]
You can actually see that the similarty between the two sentences mentioned is a bit high but you have to realize that the Universal sentence encoder(USE) is looking for semantics to the words in the sentence itself.
Fore example lets say if you add sentences [1] and [2]
[1]"Airtel is a big reputed telecom company. I would be proud to work for a company with such a long history of leadership in the telecom industry."
[2] "in april 2015 acquired a delhi-based mobile marketing automation firm"
the resultant sentance would be
"Airtel is a big reputed telecom company. I would be proud to work for a company with such a long history of leadership in the telecom industry. In april 2015 acquired a delhi-based mobile marketing automation firm" which does make some sense. This is how USE is coming to that conclusion.
For more indepth understanding on how it exactly  derives the embeddings,  can go through this paper.


Fix for styles in press summaries

This is a very small change to the HTML transform, allowing it to find the CSS class definitions in the metadata of a press summary.
In press summaries, the parser adds the string '#main' before the name of the Word style. For example, style 'Paragraph1' might be '#main .Paragraph1 { font-style: bold }' in the Akmoa Ntoso metadata.
This differs from a judgment, in which the main styles are preceded by '#judgment'.
I just forgot to update the HTML transform for press summaries. This fix should do that.

 Bold styling not coming through in press summaries


more robust encoding fallback

Description
A more robust mechanism for selecting an encoding to use for token counting when the mapping is not present in langchain / tiktoken.
https://dimagi.sentry.io/share/issue/d71c6aceb9f14f2e8707a5cdaf821792/

With OpenAI's fine tuning, yes, their naming scheme appears to be:
f"ft:{openai_model_name}:{organization_name}:{optional_custom_name}:{hash}"

When that optional_custom_name is omitted, we get the double ::.


HTTP Redirect https://enola.dev/... "logical" IRIs to documentation

For this (or this) it would be cool if e.g. https://enola.dev/datatypes would redirect to e.g. https://docs.enola.dev/models/enola.dev/datatypes - kind of thing.
Note that GitHub pages redirects drops the path, e.g. https://enola.dev/concepts/uri/ => https://enola.dev/ but not https://docs.enola.dev/concepts/uri/.
It perhaps could even take the request headers into account and redirect a GET on https://enola.dev/emoji with Content-Type for Turtle (or whatever) to https://docs.enola.dev/models/enola.dev/emoji.ttl (note the .ttl extension which would be automagically added).
The simplest may be to hack a small web server e.g. in Go and have it running on something like Cloud Run?
Maybe this could be called tools/spielberg, as in, the (re)director... 🎦

Note that GitHub pages redirects drops the path, e.g. https://enola.dev/concepts/uri/ => https://enola.dev/ but not https://docs.enola.dev/concepts/uri/.

This isn't GitHub pages' doing, but an HTTP Redirector's; currently that's Google Domains's. It had "Path Forwarding" switched off. I've just enabled it.
Right now (just 1' after enabling it), https://enola.dev/concepts/uri/ still redirects to https://enola.dev/ instead of https://docs.enola.dev/concepts/uri/, like before; but perhaps Google Domains needs a moment to dig this?

Right now (just 1' after enabling it), https://enola.dev/concepts/uri/ still redirects to https://enola.dev/ instead of https://docs.enola.dev/concepts/uri/, like before; but perhaps Google Domains needs a moment to dig this?

This works now, but... that won't cut it.
What we need is https://enola.dev/emoji => https://docs.enola.dev/models/enola.dev/emoji/


adding SQL feature support matrix

This change is

Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion.

sql-feature-support.md, line 60 [r1] (raw file):

| Component | Supported | Type | Details |
|-----------|-----------|------|---------|
| `INNER JOIN` | ✓ | Standard | [`JOIN` blog post](https://www.cockroachlabs.com/blog/cockroachdbs-first-join/) |

Given our current implementation, we should mark these with a footnote instead of a full "check". The footnote can say that these operations are supported only for small data sets. @knz what do you think?

Comments from Reviewable

Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion.

sql-feature-support.md, line 60 [r1] (raw file):
Previously, RaduBerinde wrote…
> Given our current implementation, we should mark these with a footnote instead of a full "check". The footnote can say that these operations are supported only for small data sets. @knz what do you think?

Yes I agree with you. Let's make it a yellow checkmark or a round blue info icon. At least avoid green.

Comments from Reviewable

Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion.

sql-feature-support.md, line 60 [r1] (raw file):
Previously, knz (kena) wrote…
> Yes I agree with you. Let's make it a yellow checkmark or a round blue info icon. At least avoid green.

Done. Moved this to the __Statements__ section since all of the `JOIN` types are supported and had the same info and lengthy note. Avoided obfuscating the info by changing the "Supported" column from ✓ to Functional, with the specification about small data sets in the "Details" column.

Comments from Reviewable

Very nice, thank you!

Review status: 0 of 2 files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Excellent work, @sploiselle! LGTM.
@nvanbenschoten, should introspection be added? If so, can you suggest an approach?

Reviewed 2 of 2 files at r1.
Review status: 1 of 2 files reviewed at latest revision, 3 unresolved discussions.

sql-feature-support.md, line 7 [r1] (raw file):

## Overview
Making CockroachDB easy to use was a top priority for us, so we chose to implement SQL. However, even though SQL has a standard, no database implements all of it, nor do any of them have standard implementations of all features.

Let's continue this priority until the end of time: "...easy to use is a top priority for us..."

sql-feature-support.md, line 11 [r1] (raw file):

To understand which standard SQL features we support (as well as common extensions to the standard), use the table below.

- __Component__ lists the components that are commonly considered part of SQL.

nit: Would you mind using **Component** as the markdown for bold, for consistency with other pages?

Comments from Reviewable

@jseldess We could add a section for supported methods of introspection, but I foresee a page/section like https://www.postgresql.org/docs/9.5/static/information-schema.html being more immediately useful. Each subsection would provide a brief overview of a supported introspection table, along with it's schema.

Thanks, @nvanbenschoten. Noted.


2022/09/22 16:24:42 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:24:42 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:24:42 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:24:42 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: error applying plan -- check rancher-system-agent.service logs on node for more information, failure while applying plan
2022/09/22 16:24:42 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: error applying plan -- check rancher-system-agent.service logs on node for more information, failure while applying plan
2022/09/22 16:24:42 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:24:42 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:24:42 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:24:42 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: error applying plan -- check rancher-system-agent.service logs on node for more information, failure while applying plan
2022/09/22 16:24:42 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: error applying plan -- check rancher-system-agent.service logs on node for more information, failure while applying plan
2022/09/22 16:24:42 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: error applying plan -- check rancher-system-agent.service logs on node for more information, failure while applying plan
2022/09/22 16:24:42 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
2022/09/22 16:24:42 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: error applying plan -- check rancher-system-agent.service logs on node for more information, failure while applying plan
2022/09/22 16:24:43 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
2022/09/22 16:25:16 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: error applying plan -- check rancher-system-agent.service logs on node for more information, failure while applying plan
2022/09/22 16:25:47 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: error applying plan -- check rancher-system-agent.service logs on node for more information, failure while applying plan
2022/09/22 16:25:52 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:25:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:25:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:26:19 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: error applying plan -- check rancher-system-agent.service logs on node for more information, failure while applying plan
W0922 16:26:38.315561      33 transport.go:288] Unable to cancel request for *client.addQuery
2022/09/22 16:26:51 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: error applying plan -- check rancher-system-agent.service logs on node for more information, failure while applying plan
2022/09/22 16:27:19 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: error applying plan -- check rancher-system-agent.service logs on node for more information, failure while applying plan
2022/09/22 16:27:20 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:27:20 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:27:20 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:27:20 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for plan to be applied
2022/09/22 16:27:20 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for plan to be applied
2022/09/22 16:27:20 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for plan to be applied
2022/09/22 16:27:20 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:27:20 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:27:20 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:27:20 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for plan to be applied
2022/09/22 16:27:20 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
2022/09/22 16:27:20 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
2022/09/22 16:27:34 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for probes: kubelet
2022/09/22 16:27:34 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for probes: kubelet
2022/09/22 16:27:34 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:27:34 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:27:34 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:27:34 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for probes: kubelet
2022/09/22 16:27:34 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for probes: kubelet
2022/09/22 16:27:34 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for probes: kubelet
2022/09/22 16:27:34 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
2022/09/22 16:27:44 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: main-cluster-cp-pool-1-fd5bb6b66-vcgk4
2022/09/22 16:27:44 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 16:27:44 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:27:44 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:27:44 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 16:27:44 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:27:44 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 16:27:44 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 16:27:44 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 16:27:44 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 16:27:44 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
2022/09/22 16:27:44 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 16:27:52 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:27:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:27:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:28:40 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
2022/09/22 16:29:52 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:29:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:29:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:30:12 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:30:12 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:30:12 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:31:52 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:31:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:31:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:32:46 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:32:46 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:32:46 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:33:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:33:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:33:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:35:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:35:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:35:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:37:22 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 16:37:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:37:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:37:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:39:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:39:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:39:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
W0922 16:41:30.374754      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:41:38.353059      33 transport.go:288] Unable to cancel request for *client.addQuery
2022/09/22 16:41:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:41:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:41:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:43:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:43:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:43:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:45:21 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
2022/09/22 16:45:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:45:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:45:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:46:52 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:46:52 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:46:52 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:47:24 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 16:47:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:47:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:47:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
W0922 16:48:22.144684      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:23.150700      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:23.150832      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:23.150864      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:23.150900      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:24.142922      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:24.142987      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:24.143029      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:24.143037      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:24.143065      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:36.140232      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:36.140328      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:36.140371      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:36.140453      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:36.140547      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:39.142024      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 16:48:39.142101      33 transport.go:288] Unable to cancel request for *client.addQuery
2022/09/22 16:49:26 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:49:26 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:49:26 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 16:49:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:49:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:49:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:51:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:51:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:51:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:53:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:53:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:53:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:55:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:55:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:55:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
W0922 16:56:45.121892      33 transport.go:288] Unable to cancel request for *client.addQuery
2022/09/22 16:57:27 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 16:57:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:57:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:57:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:59:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:59:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 16:59:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:00:55 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 17:00:55 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for plan to be applied
2022/09/22 17:00:55 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for plan to be applied
2022/09/22 17:00:55 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:00:55 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:00:55 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:00:56 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for plan to be applied
2022/09/22 17:00:56 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for plan to be applied
2022/09/22 17:00:56 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for plan to be applied
2022/09/22 17:00:56 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
2022/09/22 17:01:04 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for probes: kubelet
2022/09/22 17:01:05 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for probes: kubelet
2022/09/22 17:01:05 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:01:05 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:01:05 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:01:05 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for probes: kubelet
2022/09/22 17:01:05 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for probes: kubelet
2022/09/22 17:01:05 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for probes: kubelet
2022/09/22 17:01:05 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: configuring bootstrap node(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4: waiting for probes: kubelet
2022/09/22 17:01:05 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
2022/09/22 17:01:19 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: main-cluster-cp-pool-1-fd5bb6b66-vcgk4
2022/09/22 17:01:20 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 17:01:20 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:01:20 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:01:20 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:01:20 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 17:01:20 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 17:01:20 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 17:01:20 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 17:01:20 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 17:01:20 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
2022/09/22 17:01:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:01:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:01:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:02:01 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
W0922 17:03:18.367678      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 17:03:18.392734      33 transport.go:288] Unable to cancel request for *client.addQuery
2022/09/22 17:03:32 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:03:32 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:03:32 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:03:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:03:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:03:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:05:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:05:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:05:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:06:06 [ERROR] [CAPI] error creating remote cluster cache: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:06:06 [ERROR] [CAPI] Failed to reconcile MachineHealthCheck: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:06:06 [ERROR] [CAPI] Reconciler error: error creating client and cache for remote cluster: failed to index field spec.providerID: no matches for kind "Node" in version "v1"
2022/09/22 17:07:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:07:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:07:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:09:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:09:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:09:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:10:57 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
W0922 17:11:36.074612      33 transport.go:288] Unable to cancel request for *client.addQuery
W0922 17:11:44.072247      33 transport.go:288] Unable to cancel request for *client.addQuery
2022/09/22 17:11:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:11:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:11:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:13:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:13:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:13:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:15:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:15:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:15:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:17:53 [ERROR] error syncing 'p-4vrfr/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:17:53 [ERROR] error syncing 'p-kknts/creator-project-owner': handler mgmt-auth-prtb-controller: users.management.cattle.io "system:admin" not found, requeuing
2022/09/22 17:17:53 [ERROR] error syncing 'c-m-zcbk2f8d/creator-cluster-owner': handler mgmt-auth-crtb-controller: users.management.cattle.io "system:admin" not found, requeuing

Rancher Log:
2022/09/22 22:52:06 [ERROR] [CAPI] Reconciler error: retrieved empty Spec.ProviderID from infrastructure provider for Machine "main-cluster-cp-pool-1-fd5bb6b66-vcgk4" in namespace "fleet-default"
2022/09/22 22:52:30 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node
2022/09/22 23:02:33 [INFO] [planner] rkecluster fleet-default/main-cluster: waiting: non-ready bootstrap machine(s) main-cluster-cp-pool-1-fd5bb6b66-vcgk4 and join url to be available on bootstrap node

Node Yaml
It seems to me that spec.providerID also exists.
apiVersion: v1
kind: Node
metadata:
  annotations:
    etcd.rke2.cattle.io/node-address: <IP_ADDRESS>
    etcd.rke2.cattle.io/node-name: m-acbe7a43-a7e0-478a-a73a-00d44e46661f-83960e34
    management.cattle.io/pod-limits: '{"cpu":"200m","memory":"192Mi"}'
    management.cattle.io/pod-requests: '{"cpu":"1125m","memory":"144Mi","pods":"13"}'
    node.alpha.kubernetes.io/ttl: "0"
    projectcalico.org/IPv4Address: <IP_ADDRESS>/19
    projectcalico.org/IPv4VXLANTunnelAddr: <IP_ADDRESS>
    rke2.io/encryption-config-hash: start-4d3179ea83cc241869b23e48ab51d550961fd68b708c01c5a59aa67175596f2e
    rke2.io/hostname: m-acbe7a43-a7e0-478a-a73a-00d44e46661f
    rke2.io/internal-ip: <IP_ADDRESS>
    rke2.io/node-args: '["server","--agent-token","********","--cni","calico","--etcd-snapshot-retention","5","--etcd-snapshot-schedule-cron","0
      0 0 1/1 *","--kube-controller-manager-arg","cert-dir=/var/lib/rancher/rke2/server/tls/kube-controller-manager","--kube-controller-manager-arg","secure-port=10257","--kube-controller-manager-extra-mount","/var/lib/rancher/rke2/server/tls/kube-controller-manager:/var/lib/rancher/rke2/server/tls/kube-controller-manager","--kube-scheduler-arg","cert-dir=/var/lib/rancher/rke2/server/tls/kube-scheduler","--kube-scheduler-arg","secure-port=10259","--kube-scheduler-extra-mount","/var/lib/rancher/rke2/server/tls/kube-scheduler:/var/lib/rancher/rke2/server/tls/kube-scheduler","--node-label","rke.cattle.io/machine=36df3e29-fc3c-49d9-939c-91d467d9e757","--node-taint","node-role.kubernetes.io/control-plane:NoSchedule","--node-taint","node-role.kubernetes.io/etcd:NoExecute","--private-registry","/etc/rancher/rke2/registries.yaml","--token","********","--node-name","m-acbe7a43-a7e0-478a-a73a-00d44e46661f"]'
    rke2.io/node-config-hash: MTDR5MQ7QSMM3ICYPZAQFQS3SRJAGFSBQGNU35SG6S4JMAO7VWAQ====
    rke2.io/node-env: '{}'
    volumes.kubernetes.io/controller-managed-attach-detach: "true"
  creationTimestamp: "2022-09-22T14:31:09Z"
  finalizers:
  - wrangler.cattle.io/node
  - wrangler.cattle.io/managed-etcd-controller
  labels:
    beta.kubernetes.io/arch: amd64
    beta.kubernetes.io/instance-type: rke2
    beta.kubernetes.io/os: linux
    egress.rke2.io/cluster: "true"
    kubernetes.io/arch: amd64
    kubernetes.io/hostname: m-acbe7a43-a7e0-478a-a73a-00d44e46661f
    kubernetes.io/os: linux
    node-role.kubernetes.io/control-plane: "true"
    node-role.kubernetes.io/etcd: "true"
    node-role.kubernetes.io/master: "true"
    node.kubernetes.io/instance-type: rke2
    rke.cattle.io/machine: 36df3e29-fc3c-49d9-939c-91d467d9e757
  name: m-acbe7a43-a7e0-478a-a73a-00d44e46661f
  resourceVersion: "231199"
  uid: b0b90b50-7a66-4a01-8bf1-46eb2b999378
spec:
  podCIDR: <IP_ADDRESS>/24
  podCIDRs:
  - <IP_ADDRESS>/24
  providerID: rke2://m-acbe7a43-a7e0-478a-a73a-00d44e46661f
  taints:
  - effect: NoSchedule
    key: node-role.kubernetes.io/control-plane
  - effect: NoExecute
    key: node-role.kubernetes.io/etcd
status:
  addresses:
  - address: <IP_ADDRESS>
    type: InternalIP
  - address: m-acbe7a43-a7e0-478a-a73a-00d44e46661f
    type: Hostname
  allocatable:
    cpu: "8"
    ephemeral-storage: "8809268218"
    hugepages-2Mi: "0"
    memory: 8092740Ki
    pods: "110"
  capacity:
    cpu: "8"
    ephemeral-storage: 9055580Ki
    hugepages-2Mi: "0"
    memory: 8092740Ki
    pods: "110"
  conditions:
  - lastHeartbeatTime: "2022-09-22T14:32:56Z"
    lastTransitionTime: "2022-09-22T14:32:56Z"
    message: Calico is running on this node
    reason: CalicoIsUp
    status: "False"
    type: NetworkUnavailable
  - lastHeartbeatTime: "2022-09-23T05:52:49Z"
    lastTransitionTime: "2022-09-22T14:31:08Z"
    message: kubelet has sufficient memory available
    reason: KubeletHasSufficientMemory
    status: "False"
    type: MemoryPressure
  - lastHeartbeatTime: "2022-09-23T05:52:49Z"
    lastTransitionTime: "2022-09-22T14:31:08Z"
    message: kubelet has no disk pressure
    reason: KubeletHasNoDiskPressure
    status: "False"
    type: DiskPressure
  - lastHeartbeatTime: "2022-09-23T05:52:49Z"
    lastTransitionTime: "2022-09-22T14:31:08Z"
    message: kubelet has sufficient PID available
    reason: KubeletHasSufficientPID
    status: "False"
    type: PIDPressure
  - lastHeartbeatTime: "2022-09-23T05:52:49Z"
    lastTransitionTime: "2022-09-22T17:01:16Z"
    message: kubelet is posting ready status. AppArmor enabled
    reason: KubeletReady
    status: "True"
    type: Ready
  daemonEndpoints:
    kubeletEndpoint:
      Port: 10250
  images:
  - names:
    - docker.io/rancher/hardened-kubernetes@sha256:d6c5d65193666aab39a3a0c8f9df4d19be4ff1d230c3b619193c41e8fb348837
    - docker.io/rancher/hardened-kubernetes:v1.23.8-rke2r1-build20220616
    sizeBytes: 222771272
  - names:
    - docker.io/rancher/rancher-agent@sha256:022f073312c9b678ff690af501639ebf6b8fe8c3244a7d28eec76d783d8d854f
    - docker.io/rancher/rancher-agent:v2.6.8
    sizeBytes: 212583346
  - names:
    - docker.io/rancher/mirrored-calico-cni@sha256:f1382e8aa0cba04ecbee68ac24033fde4a5df2313e9ec80351e36d54dbd13613
    - docker.io/rancher/mirrored-calico-cni:v3.23.1
    sizeBytes: 110500114
  - names:
    - docker.io/rancher/klipper-helm@sha256:6a8e819402e3fdd5ff9ec576174b6c0013870b9c0627a05fa0ab17374b5cf189
    - docker.io/rancher/klipper-helm:v0.7.3-build20220613
    sizeBytes: 82983731
  - names:
    - docker.io/rancher/mirrored-calico-node@sha256:4e4643c2a04cfb7c664eff97c3db3806d8c379a72b61f79e3744e85b8abac14d
    - docker.io/rancher/mirrored-calico-node:v3.23.1
    sizeBytes: 76574164
  - names:
    - docker.io/rancher/mirrored-calico-operator@sha256:9e26653eb5bcf7b93e916a0e13beaf9f87776a30e5178225d8f35831228202fd
    - docker.io/rancher/mirrored-calico-operator:v1.27.1
    sizeBytes: 60267159
  - names:
    - docker.io/rancher/mirrored-calico-kube-controllers@sha256:67c9d74d1fbf6ba7a5a9dde03bafe528e7ffb94cf58fdae18deb705674576c7f
    - docker.io/rancher/mirrored-calico-kube-controllers:v3.23.1
    sizeBytes: 56361543
  - names:
    - docker.io/rancher/mirrored-calico-typha@sha256:7c7f45957c0f3366924442898c93fe635aacfbbc3557115fd87987879ce12b9c
    - docker.io/rancher/mirrored-calico-typha:v3.23.1
    sizeBytes: 54002928
  - names:
    - docker.io/rancher/rke2-cloud-provider@sha256:a3fe814abb2f4cdb41583a5175453ec63667cce9e653a7b1a821d2c96a278c52
    - docker.io/rancher/rke2-cloud-provider:v0.0.3-build20211118
    sizeBytes: 49490620
  - names:
    - docker.io/rancher/hardened-etcd@sha256:146775f007a4b322485a7f1705424c2c799a4fccc1451484edecbdba0d07847f
    - docker.io/rancher/hardened-etcd:v3.5.4-k3s1-build20220504
    sizeBytes: 49072950
  - names:
    - docker.io/rancher/hardened-coredns@sha256:0ff19d19385acdfad644792531ac4c108c73cf021c755b08b7c6dfbef053a043
    - docker.io/rancher/hardened-coredns:v1.9.3-build20220613
    sizeBytes: 48334303
  - names:
    - docker.io/rancher/hardened-cluster-autoscaler@sha256:7cc3ec1030240a8b69d1185611c1f89cf357cddae642e8cc082e1a49ebc3611d
    - docker.io/rancher/hardened-cluster-autoscaler:v1.8.5-build20211119
    sizeBytes: 43568033
  - names:
    - docker.io/rancher/mirrored-calico-pod2daemon-flexvol@sha256:5d963529a8da48ef1f810e78c042600d91d276a6fc8958759d48297f106c604a
    - docker.io/rancher/mirrored-calico-pod2daemon-flexvol:v3.23.1
    sizeBytes: 8671290
  - names:
    - docker.io/rancher/pause@sha256:036d575e82945c112ef84e4585caff3648322a2f9ed4c3a6ce409dd10abc4f34
    - docker.io/rancher/pause:3.6
    sizeBytes: 299396
  nodeInfo:
    architecture: amd64
    bootID: cafa2360-58e2-428a-ad2d-01291f84df65
    containerRuntimeVersion: containerd://1.5.13-k3s1
    kernelVersion: 5.14.21-150400.24.21-default
    kubeProxyVersion: v1.23.8+rke2r1
    kubeletVersion: v1.23.8+rke2r1
    machineID: f7d979b5ce30cfc4cd8fd04a632c7145
    operatingSystem: linux
    osImage: SUSE Linux Enterprise Micro for Rancher 5.3
    systemUUID: acbe7a43-a7e0-478a-a73a-00d44e46661f

When I install the worker node, it says provisioned.


Update rulinalg Github description

The description of rulinalg's Github repo currently says:

A linear algebra library in Rust designed for machine learning

Although rulinalg was originally extracted from rusty-machine, there's little to no functionality in rulinalg that is specific to machine learning.
Perhaps we should update the description so that potential users don't get discouraged if they don't intend to use it for machine learning?

Yes I think you're right.
I'll update this now (feel free to post here if you have any suggestions for what this should read instead).

I think the new description is sufficient :) I'll close this now!

Thanks for pointing this out!


Assignment to array element

Repro is with Zed commit 63d6b29. This variation was actually first called out in https://github.com/brimdata/zed/issues/4651#issuecomment-1622343020.
Here's an example of something that's easy in Python, which might be familiar to our data-centric users due to how Python is often used with Pandas et al.
$ python3
Python 3.11.5 (main, Aug 24 2023, 15:18:16) [Clang 14.0.3 (clang-14<IP_ADDRESS>.1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> numbers = [4,5,6]
>>> numbers[0]=1
>>> print(numbers)
[1, 5, 6]

Attempting the same using Zed with what I'd think of as the equivalent straightforward syntax:
$ zq -version
Version: v1.10.0-5-g63d6b299

$ echo '{numbers:[4,5,6]}' | zq -z 'numbers[0]:=1' -
illegal left-hand side of assignment

It's been pointed out that it's possible to get there today if the user is familiar with slices & spread:
$ echo '{numbers:[4,5,6]}' | zq -z 'cut numbers:=[1,...numbers[1:]]' -
{numbers:[1,5,6]}

However, given how the simple reference to the element on the left-hand side is common in other languages, it seems like it would be convenient to the user if it worked similarly in Zed.
FWIW, I tried to make use of this syntax in https://github.com/brimdata/challenges/blob/aace23e1ef85b7f411323d776977afc4cfa9935e/ames-shaping/shaper.zed#L3-L23.

I happened to revisit this issue just to see if the changes in #4795 affected what's described here, and it turns out this did indeed happen. Starting with Zed commit ef9695f which is associated with the changes in #4795, the simple repro shown in the opening of this issue no longer results in the illegal left-hand side of assignment error, but instead does this:
$ zq -version
Version: v1.10.0-16-gef9695f2

$ echo '{numbers:[4,5,6]}' | zq -z 'numbers[0]:=1' -
{numbers:{"0":1}}

I guess it's doing something like converting the 0 to a string value and then treating this as a valid left-hand side indexing reference to a field in a record, hence dropping the array formerly known as numbers and replacing it with a newly-constructed record. But given the Python example shown above and how many other languages treat bare numeric references in contexts like this as indexing into arrays, I'm guessing this may not be what most users would expect to have happen. That might boost the priority of addressing this issue.


update Debian package requirements

pkg-config libcurl4-openssl-dev libssl-dev are not necessary anymore (since https://github.com/ZerBea/hcxdumptool/commit/d1f23265349bae552659e964cfb7f2953548d93a and https://github.com/ZerBea/hcxdumptool/commit/311e09325d70a0774d25f687b285c3af26ca7519), zlib1g-dev has never been required, I think it was just copied from hcxtools, so lets remove them.

Thanks.
I'm not sure if refacterd hcxdumptool will find its way to Bookworm (which is in freeze), but good to have a notice here.
I haven't removed this, because I thought it is possible to add this features to hcxdumptool, too.
Unfortunately it doesn't work as expected and I dropped it.
From the lessons learned:
It is not feasible  to recover PSKs on the fly (e.g like aircrack-ng wep).
It is not feasible to gzip the dum file on the fly.
It is not feasible to upload the pcapng file to wpa-sec on the fly.
It is not feasible to hold a BT or WLAN or SSH connection while running hcxdumptool.
Because hcxdumptool is an interactive tool that must(!) respond to a target within a precisely defined time.
Regarding features, we have a ranking. This ranking must be strictly observed:
time response behavior
cpu cycles of a Raspberry Pi
In other words:
form follows function
keep it small and simple
do one thing and do it well


Add a shortcut for --dry-run as -d

Command
generate
Description
Right now i can run a dry run for generation components/services/etc. with the following command
ng g c mytestcomponent --dry-run
Describe the solution you'd like
i want to generate stuff with a shortcut -d to have a shorter version of it.
(I think in older angular versions it was possible)
Describe alternatives you've considered
No response

I would love to work on this

Feel free to drop a PR !


Visual Studio 2019 has now been replaced with Visual Studio 2022

We've been using Visual Studio 2019 for a while now. I'm following the build instructions. By following the link here, it's a bit hard & annoying to actually find Visual Studio 2019: https://docs.ros.org/en/rolling/Installation/Windows-Development-Setup.html#install-visual-studio. The website tries real hard to get you to install the 2022 release. I had to login with a Microsoft account to get Visual Studio Community 2019.
So I'm wondering:

should we switch to Visual Studio 2022? Do we expect it to just work?
or should we mention having to find Visual Studio 2019, at least in the meantime?

* should we switch to Visual Studio 2022? Do we expect it to just work?

Generally, that has not been our experience in the past.  Likely we'll have to do some code changes.  Even if we do get it to work, we are also going to need to fix up https://ci.ros2.org to use the new version.  I think that is something we should do before Humble, but it will take some dedicated time.

or should we mention having to find Visual Studio 2019, at least in the meantime?

Yeah, I think we'll have to do this for now.  A direct link to that version would be best, if we can find it.

Yeah, I think we'll have to do this for now. A direct link to that version would be best, if we can find it.

This is the link I got: https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16&src=myvs&utm_medium=microsoft&utm_source=my.visualstudio.com&utm_campaign=download&utm_content=vs+community+2019. Seems like you don't actually need to be logged in or anything.

This is the link I got: https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16&src=myvs&utm_medium=microsoft&utm_source=my.visualstudio.com&utm_campaign=download&utm_content=vs+community+2019.

This link works for me too.


            The format of each row is as follows:
            x1, y1, w, h, x_re, y_re, x_le, y_le, x_nt, y_nt,
            x_rcm, y_rcm, x_lcm, y_lcm,
            where x1, y1, w, h are the top-left coordinates, width and height of
            the face bounding box,
            {x, y}_{re, le, nt, rcm, lcm} stands for the coordinates of right eye,
            left eye, nose tip, the right corner and left corner of the mouth respectively.
            """
            (x, y, w, h, x_re, y_re, x_le, y_le) = list(map(int, face[:8]))
            left_eye = (x_re, y_re)
            right_eye = (x_le, y_le)

            # Yunet returns negative coordinates if it thinks part of
            # the detected face is outside the frame.
            # We set the coordinate to 0 if they are negative.
            x = max(x, 0)
            y = max(y, 0)
            if resized:
                img = original_image
                x, y, w, h = int(x / r), int(y / r), int(w / r), int(h / r)
                x_re, y_re, x_le, y_le = (
                    int(x_re / r),
                    int(y_re / r),
                    int(x_le / r),
                    int(y_le / r),
                )
            confidence = float(face[-1])

            facial_area = FacialAreaRegion(
                x=x,
                y=y,
                w=w,
                h=h,
                confidence=confidence,
                left_eye=left_eye,
                right_eye=right_eye,
            )
            resp.append(facial_area)

If you check the flow here you see left_eye and right_eye are valued as tuple from (x_re, y_re) and (x_le, y_le) respectively but in case of resized image are not recomputed: yes the coordinates are recomputed but not reassigned to left_eye and right_eye which are the vars effectively copied into FacialAreaRegion.
This has an implication on face alignement (which is done elsewhere) based on the coordinates of the wyes

I'd say this is a bug not an enhancement

A bug is also a wrong result.
Sum(3,5) == 9
Is not blocking but is an error

okay made it bug

Closed with PR - https://github.com/serengil/deepface/pull/1103


Add nested Classes

Code CleanUp and Description Update

internal_worker() && internal_worker_parent_obj()
PROS:

Alows to make nested classes like: $CI->Users->Auth->is_logged_in(); (User and Auth are diferent classes that complement each other, one of many examples)
Cons:
Does not have yet an error handler like the normal does

and it is tested, on :  7.0.15-0ubuntu<IP_ADDRESS>

This doesn't belong in the CI core, sorry.


Search SDK: Merging upstream changes from master to search-v2-preview-dev

I am purposefully not squashing this because when I did that on my branch in azure-sdk-for-net, it created big merge conflicts later. I will rebase all our changes before the final merge back to the AutoRest branch.
FYI @chaosrealm @seansaleh @Yahnoosh @mhko

No modification for Python

 https://github.com/Azure/azure-sdk-for-node/pull/1823

No modification for NodeJS

No modification for Python


CI

Using GitHub Actions we need to configure some CI, which will build the project and run tests. Other features like options check on push, etc. should been consider on the 'meeting' haha.

When is the next 'meeting' haha?

When is the next 'meeting' haha?

Don't worry)
This issue is more for me or @c71n93


Small format improvements

Fix indentation in the meson.build file.
Use consistent args passing in start-stop-daemon.

thx!


feature: Add --force-with-lease option on branch push.

Did you check the docs?

[X] I have read all the LazyVim docs

Is your feature request related to a problem? Please describe.
When pushing a branch, if the local branch history deviates from the remote, which is common after a rebase, a popup is shown asking the user if they would like to push with the --force flag. This is potentially harmful, as you may not have changes locally that others have added to the remote. By force pushing, there is a high risk of blindly overwriting others changes. 99 times out of 100, I am force pushing after a rebase. I do not intend to overwrite others commits that I may not have.
Describe the solution you'd like
In the case described above, I would like two things:

The pop-up shows the user multiple push options. --force-with-lease and --force.
The default action suggested to the user in the list of options is --force-with-lease, a flag on git push that fails the push if there are commits on the remote not present on local. Reference.

Describe alternatives you've considered
Not sure i would suggest an alternative here, but it's a required field in this ticket form. An alternative would be that push no longer has a pop up if it fails to push to local and remote differing. Instead there would be a menu option for push, force push, and force push safe (git push --force-with-lease).
I wouldn't suggest this over the other option as it puts more options in front of the user than they need most of the time, but it feels like it still aligns with the general approach of the lazygit ui.
Additional context
No response

LazyVim doesn't do any lazygit configuration. Maybe you would like to redirect your feature request to the lazygit repo instead? It doesn't have to do anything with LazyVim this kind of request in this repo.

Whoops! Completely created this ticket in the wrong tab. Sorry! I'll move this over to lazygit.
Thanks @dpetka2001


add component to idf

hello,
I need to add some components to "sys-idf". how can I do it?
I tested this way.

clone sys-idf-hal
add esp-littlfs to components
add esp-littlefs to binding.h
build it.

but I think this is not right.

Duplicate, see https://github.com/esp-rs/esp-idf-sys/issues/116#issuecomment-1214329068


Unwrap pkg_config result in build script

Currently the build.rs script from coin_cbc_sys looks like this (I've added type annotations to clarify):
use pkg_config::{Error, Library};

fn main() {
    let _: Result<Library, Error> = pkg_config::probe_library("cbc");
}

The failure condition of the probe is being completely ignored! This means that a failure to find the library is only reported as confusing linking errors at the end of the build process:
[...] = note: LINK : fatal error LNK1181: cannot open input file 'CbcSolver.lib'

I think the build script should be changed to unwrap() the Result instead, which would cause cargo to show this more helpful error message, much sooner during the build process:
   --- stderr
  thread 'main' panicked at coin_cbc_sys\build.rs:5:38:
  called `Result::unwrap()` on an `Err` value: `"pkg-config" "--libs" "--cflags" "cbc"` did not exit successfully: exit code: 1
  error: could not find system library 'cbc' required by the 'coin_cbc_sys' crate

  --- stderr
  Package clp was not found in the pkg-config search path.
  Perhaps you should add the directory containing `clp.pc'
  to the PKG_CONFIG_PATH environment variable
  Package 'clp', required by 'cbc', not found

That’s a feature. If pkg-config is not installed, it can still work with some other manual configuration. With unwrap, it would fail the build.
https://github.com/KardinalAI/coin_cbc/commit/5487a824e8f986bb98c7ff1615eddc4d3d6ce14e
I don’t really know if that’s good or not.


Missing operating system (Windows XP)

I've created a Windows XP installation in QEMU with FAT32, but when I try to boot it in v86 the BIOS simply says "Missing operating system" and doesn't boot. What should I do? I've already disabled ACPI in Device Manager, so I don't think that's the issue.

Did you create a raw image? If not, you can convert it using qemu-img convert -O raw.

I did make a raw image, but I'll try reconverting it just in case

@copy No success... should I try installing the VM on a qcow2 image, then converting to raw?

No, that shouldn't make a difference. Did you check that the image boots in qemu (with -hda …)?

Yes, QEMU boots the image just fine.

@copy I'd also like to mention that the VM didn't work when I used NTFS, also.

Just to confirm, do you get this issue when you open debug.html, use the xp image as a hard drive and increase the memory size to 256MB or more? Could you post a log from the browser console?

@copy I did it in debug.html with the XP image as a hard drive, the memory set to 1024 MB, and the video memory set to 256 MB. Here is the log: https://pastebin.com/9vPxymHf

It's a weird issue, so I'm guessing a bit in the dark here. Can you:

Try with a lower memory size
Let me know the size of the image, and if it isn't a small multiple of 1GB, retry with 8GB or so?
Try qemu with -no-acpi -cpu pentium
Post the complete qemu command line of the installation and when running it?
Try this commit: cc073388edcf3f67a8de839734d11b80d8cbd93f (Run git checkout cc07338, then make and open debug.html)

Alright, I’ll try it as soon as I can.


Remove prefixes [breaking]

We should add first-party prefix support like such:
// OLD, to remove
await store.keys(filter?: string);

// NEW example with no prefix and with prefix
await store.keys();
await store.prefix(filter: string).keys();

This is the main external-facing change, which affects .keys(), .values(), .entries() and should also be included in .clear() (basically, the group methods). Support for others like .get() remains as it is now.
Internally, it'd be a good idea to allow for first-party support for those libraries that can do it. Probably something like this:
// Normal methods
store.keys(...options?)
store.values(...options?)
...

// Prefixed methods
store.prefixKeys(prefix, ...options?)
store.prefixValues(prefix, ...options?)
...

That way if there's no e.g. .prefixKeys(), it will be polyfilled as it is currently ((await store.keys()).filter() basically), but if there is first party library support then call that method instead. This should NOT affect normal methods like .get(), since for that the difference between first-party .prefixGet(prefix, id) support would be virtually the same as the current .get(prefix + id) (note the , vs +).

Done 👍


Provide realtime feedback of Invoke-External commands

Pull Request Template
📲 What
Provide realtime feedback of Invoke-External commands
🤔 Why
Without this you have to wait until the command has finished before you see the output.
Now when running a command e.g. terraform apply, you can see the progress.
🛠 How
Removed the code that puts the output of Invoke-External into a variable
👀 Evidence

@balpurewal I have modified this to use the Tee-Object command so that we can capture and stream the data at the same time.


WIP trailing newlines

aims to fix #160

Requirements

[ ] Entry in CHANGELOG.md was created
[ ] Link to documentation on https://yaml.org/ is provided in the PR description
[ ] Functionality is covered by newly created tests

oops - recreated PR see #164


[Canary] shortcuts not working

[x] I am on the latest Hyper.app version

[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: MacOS Sierra

Hyper.app version: 2.0.4 (Canary)

Link of a Gist with the contents of your .hyper.js: https://gist.github.com/patrik-piskay/94385f24014c0fed1c65bd3fed68469c

Relevant information from devtools: N/A

The issue is reproducible in vanilla Hyper.app: Is Vanilla

Issue
Video: https://cl.ly/1P2l2K1j3009
Shortcuts are not working for me, it's not very clear on the video as there is no visible indicator of keys pressed but after creating 4 tabs and trying to switch between them with cmd+1/2/3/4, nothing happens. Also after typing some characters, trying to alt+backspace or cmd+backspace should remove the whole string but only native backspace behaviour happens (deleting only one char).
Thanks!

There is existing ticket for this https://github.com/zeit/hyper/issues/2279, it also mentions that as a workaround right now you can use CMD + SHIFT + [ or ]


Inconsistent http error responses

Issue
Our error responses are inconsistent. I would propose a uniform approach so our users always know which attribute to access when looking for an error message.
Background
I listed some reproducible examples below using Postman and a Dummy config local Weaviate and sending the specified queries to the /graphql extension (note: this issue is not endpoint-specific). The actual requests/responses are not of interest here, my point is about the response type.

Unprocessable query

This query returns a 400 (bad request) in the header and a JSON Body
Request body:
[]

To: /graphql
Response:
{
    "code": 400,
    "message": "parsing body body from \"\" failed, because json: cannot unmarshal object into Go value of type models.GraphQLQuery"
}

Empty query

Only returns a 422 (unprocessable entity) code in the header
Request body:
{}

To: /graphql
Response:
{}

Valid GQL query asking for attribute of a class that has no instances in the database

Returns a nested JSON error in the body and a 200 in the header.
*Note that this request returns a 200 because the request itself is valid.
Request body:
{"query":"{\n  Local {\n    Get {\n      Things {\n        TestThing {\n          uuid\n        }\n      }\n    }\n  }\n}\n","variables":null,"operationName":null}

To: /graphql
Response:
{
    "data": {
        "Local": null
    },
    "errors": [
        {
            "locations": [
                {
                    "column": 3,
                    "line": 2
                }
            ],
            "message": "runtime error: invalid memory address or nil pointer dereference",
            "path": [
                "Local"
            ]
        }
    ]
}

Three queries resulting in an error, three different types of output.
Questions

Do we want to standardize error output?
Assuming standardisation is preferred, which return value do we want to use?
Any of the options in the example?
Something else entirely?

cc: @moretea @bobvanluijt

Note that the third example returns a 200 because the request is valid, it returns an error because it cannot find anything in the database matching the query.
Returning error codes for a request in the header only is somewhat of a problem for batch requests too, as a batch request can contain multiple failed requests.
I'd prefer returning a nested error like in the third example. I like the consistency with successful request responses, and this format is easy to use. The locations and path fields would be optional. This would also solve the issue with returning batched request errors.

To me only the first error does not make sense. Could you link to the implementation source code on github here?
The second field is missing the query property. So yes, not acceptable request. We could extend the error message a bit.
The third case is correct. We accept the query, it's "valid" (syntax wise), but resolving fails because we did not implement the resolvers yet.

Yes indeed.
We have the REST errors (as described in the open API specs) and the GQL based errors.
What I don’t know is if a proper request to the GQL endpoint should also return a 200.

it's located here. I did correct a mistake in the error response above, should have been models.GraphQLQuery

That makes sense. Because that endpoint handler is accepting just one query at a time. It does not support batching. Did you link the correct handler?
Or do we now want to use just one HTTP endpoint for both normal GraphQL queries, and batched queries?

@moretea my point is not about the response (or the request) itself but about the structure of the JSON response body. We're still using separate endpoints, I should have clarified that!
@general The first example (return nothing, only a header) does pose a problem to batch request handling. I can't use the header for errors for individual requests in a batch.

Yes you can. You could collect the results, and then see if one fails. Then you return a HTTP error. To do this, you'd probably need to introduce a intermediate data structure, which would not only store a GraphQueryResult, but also a bool to denote if it's a fatal error or not.
api.handler = func (http params) http.Middleware {

  struct batchResult {
    result *graphql.GraphqlResponse
    isFatal bool
  }

 /// loop over everything

/// in goroutine:
go func() {
  response_channel <- batchResult { .... }
}

/// Then collect
var graphlResponses []models.GraphQLQueryResultSomethingModel
for _, response in response_channel {
   if response.isFatal {
      return graphql.SomeFatalErrorResponse().WithPayload(error)
  } else {
    // append to graphqlResponses
  }
}
payload := graphqlResponses
return graphql.NewGraphQlOKResponse().WithPayload(payload)

}

IMHO you should do that in any case for "fatal" errors (the ones that cause a return graphql.SomeErrorState in the current handler).

I'm afraid that wouldn't work, I can't let an entire batch fail because one or more of the requests it contains fails (well I can, but I really shouldn't). Say we put requests A and B in a single batch request. The only relation request A has to request B is that they're both wrapped in the same request. Request A wouldn't fail if it and request B were sent separately, the same should hold true when they're batched.
I view it as taking the bus to work with random people; whether they're late for their jobs or not does not and should not impact you.

I agree with you @JeroenStravers1. Besides this, the error is part of the GQL response. It is a correct REST response (therefore 200) but an incorrect GQL result (therefore the error is in the response).
@dljcollette this (⬆) is correct, right?

In retrospect I should have omitted the graphql case, as that is indeed a different case than when a request itself produces an error. If we ignore the third case, are the first and second case behaving as expected?
It's the second case, the one that returns nothing, that has me worried. How should I handle such a response as part of a batch? I can't set the header of the batch request to the response code of any single batched request (the rest of them have headers too!), and I don't have a response body to work with.

Well, per bullet.

This is correct. It can't model models.GraphQLQuery based on an array. Are you sure that the HTTP-response is a 400 and not 200 but that graphql sends a 400? There is nothing in the code that generates a 400, only 200, 401, 403 and 422.
This is correct
This is correct too.

There is another route you can take too. That might be way easier and faster to implement which I outlined here.

What is the status of this issue @JeroenStravers1?

Currently the GQL batch endpoint returns batched request errors that would normally be returned as a header status code (say a 422) by using the field that errors caused by GraphQL query errors would inhabit:
[
  {
    "errors": [
      {
        "message": "error message"
      }
    ]
  },
  ... other responses
]

The batch create endpoints produce a similar response, but the error message is nested deeper:
[
  {
    "result": {
      "errors": {
        "error": [
          {
            "message": "error message"
          }
        ]
      }
    }
  },
    ... other responses
]

The "result" field also has a property that contains either "SUCCESS", "PENDING" or "FAILED", depending on the request result, so it has some added value.
The above implementation works. We could keep it like this, or we could streamline the batch create endpoint error responses to match the batch GQL endpoint error responses (meaning eliminating the "result" and "errors" layers, and renaming the "error" layer to errors).

If this is acceptable, then yes :) I'll update the batching doc to reflect this.

Closing as discussed


perf: improve comparison of $Proxy and GeneratedConstructorAccessor

We do not go through all classes in the index to match the checksum. Instead, we name each Proxy class as Proxy_<interface it implements>. This makes the checksum lookup much faster.

[NOT ALLOWLISTED]: com/sun/proxy/jdk/proxy1/$Proxy8
[MODIFIED]: com/sun/proxy/$Proxy9
[NOT ALLOWLISTED]: com/sun/proxy/$Proxy11
[NOT ALLOWLISTED]: com/sun/proxy/$Proxy12
[NOT ALLOWLISTED]: com/sun/proxy/$Proxy13
[NOT ALLOWLISTED]: com/sun/proxy/$Proxy14
[NOT ALLOWLISTED]: java/lang/invoke/BoundMethodHandle$Species_LLLLLI
[NOT ALLOWLISTED]: java/lang/invoke/BoundMethodHandle$Species_LLLLLII
[MODIFIED]: jdk/internal/reflect/GeneratedConstructorAccessor7
[NOT ALLOWLISTED]: org/slf4j/MarkerFactory
[NOT ALLOWLISTED]: org/slf4j/helpers/BasicMarker
[NOT ALLOWLISTED]: org/slf4j/spi/LocationAwareLogger
[MODIFIED]: jdk/internal/reflect/GeneratedConstructorAccessor8
[MODIFIED]: jdk/internal/reflect/GeneratedConstructorAccessor10
[MODIFIED]: jdk/internal/reflect/GeneratedConstructorAccessor11

The modified Proxy is due to random order of fields in $Proxy9

When rewriting with ASM, the UTF8 constants are only changed for the entity and not for the entire classfile. For example, if a field name is renamed, the modified classfile has a new UTF8 entry with the new name. But that entry is not referred to anywhere. This is wrong because ideally old names for fields exist as UTF8 entries. Only they should be renamed and the rest of the classfile needs no change.

This PR does a lot of things:

increases performance of lookups
add all submodules for runtime indexing
rewrite Field ref and SourceFile attribute
include only content of constant pool for hashing

Some issues remaining:

GCA and org/example/Main in log4shell
check how classes with same names and packages in different modules are handled
include all opcode for hashing

The JDK indexer also seems to be really slow now.


[ABW-2609] Update detection of main babylon seed phrase recovery

Description
Right now, if you skip babylon seed recovery, there is new BDFS that will be marked as main. If user will remove security settings of device and we lose encryption key to decrypt mnemonics, we delete them and expect recovery of main one (used for account/persona creation - otherwise app will crash if we try to create new entity). But the logic for detecting main one was not updated in BDFS skip changes, so we would restore wrong one (not used for entity creation)
How to test

Restore app from backup, skip BDFS recovery
Remove device security screen and addd it again
Open app - you will see mandatory recovery that is now skippable - also a bug.
4a. Enter seed phrase, try to create account/persona - app crashes.
4b. Skip recovery - we have wallet without main BDFS mnemonic.

This PR aims to fix this
PR submission checklist

[x] I have tested main BDFS recovery after device security removal

@jakub-rdx Isn't this PR solving the same question here https://github.com/radixdlt/babylon-wallet-android/pull/649#discussion_r1399098290 ?

@jakub-rdx Isn't this PR solving the same question here #649 (comment) ?

Yes, isBabylon was no longer enough to use in MainViewModel + recovery of MANDATORY mnemonic should not be skippable

@jakub-rdx Isn't this PR solving the same question here #649 (comment) ?

Yes, isBabylon was no longer enough to use in MainViewModel + recovery of MANDATORY mnemonic should not be skippable

@jakub-rdx But does that mean we want to change the condition in the place where @micbakos-rdx point to exactly i.e. babylonDeviceFactorSourceExist ?

@jakub-rdx Isn't this PR solving the same question here #649 (comment) ?

Yes, isBabylon was no longer enough to use in MainViewModel + recovery of MANDATORY mnemonic should not be skippable

@jakub-rdx But does that mean we want to change the condition in the place where @micbakos-rdx point to exactly i.e. babylonDeviceFactorSourceExist ?

I was asking about the same thing, it works now.


Fix and improve channel handling

jenkins/images: find channel from base channel variable
Using the tags on the branch is not enough to find the channel we want
to be the dev build be related to.
Use the base channel variable which was introduced for this.
ci-automation: set the channel from the git tag
For now we had only "developer" images in the new pipeline.
Based on the git tag like "alpha-1234.0.0" set the channel (group) for
the image and also use this logic when finding the channel in the QEMU
update test.

How to use
Port to all channels
The first change fixes the package-diff comparison that sometimes failed (for dev builds and for release builds). The second is for being able to build a release image in the new pipeline (a first step towards making releases from it).
Testing done
ongoing for jenkins/images.sh
ongoing for ci-automation group setting and qemu update test

I failed to rerun the test with the updated branch here and would have to rebuild everything again, will just merge


Fixing a small code readability issue reported by ebert using credo.

Fixing a small code readability issue reported by ebert using credo.

Thank you!

Credo is wrong on this one. The proposed change is changing the precedence of the code. In this case the parens are not wrapping if/do but two checks. Maybe Credo should check if the parentheses also finish before do. In /cc @rrrene

Sorry, I shouldn't merge so early in the morning. I confused the and with a do.

I guess the failing test was a sign, but it didn't seem relevant to the change...


Use let instead of var

The previous ('getting started') section contains some of the same example code using let instead of var. So, to keep consistency, and also to use the latest JavaScript, this PR changes the use of var to let.

Hi @mrseanbaines
There are already similar PRs:
https://github.com/webpack/webpack.js.org/pull/2768/files
https://github.com/webpack/webpack.js.org/pull/2614/files
My call is - support open PRs vs open new PRs on the same change. Unless you don't agree, i suggest closing this one