Define the purpose of having access to non-typed tokens in the language server

The language server defines a set of capabilities that it is able to offer during initialization with the client.
The specific capabilities that we currently offer in sway-lsp are:
definition_provider,
semantic_tokens_provider,
document_symbol_provider,
hover_provider,
completion_provider,
document_highlight_provider,
document_formatting_provider,
rename_provider,
execute_command_provider, //-- this is needed for rename support

Some of the above capabilities require typed tokens and an understanding of the namespace associated with the tokens. Specifically, these are the definition, rename, highlighting, and (to a certain degree) hover, providers.
Therefore, the main reason for collecting the non-typed tokens is so we can use them for communicating back information about the completion_items, document_symbols, and semantic tokens to the client.
We could potentially also support the hover capability with non-typed tokens for printing doc comments as well as also provide information about the standard numeric types in sway on hover (see rust-analyzer for an example).
Why not just use typed AST nodes for everything?
There may be cases where a token has been collected during the parsing stage but has failed to pass type checking, thus the token is not available in the typed token list. In these cases, we can still communicate derived information about the symbol of the token back to the client. However, all other capabilities registered with the server are not available on that token as they require known type information.

This no longer needs to be an open issue. I've also added this to the internal LSP / Engineering section in Notion.


Changed documentation and fixed template

The error in the template was that it was showing:
<h1>{{title}}</h1>
This was moved to AppComponent in the first paragraph of Step 6.

I signed it!

Wow, when I was following the tutorial I was struggling with this issue too. Would be cool if this PR can be merged.

Sorry but we will not accept this. It adds a burdensome new file without compensating significant value. You saw (and deleted) the comment in the text that tells you to delete the <h1>. Neglecting to do so caused no serious harm. We do appreciate your close reading of the Tour and your readiness to help.


compile fail in xcode9

maybe should update to swift3.2

I added a PR that fixes the compile failure in Xcode 9


Encoding correction and http response correctly closing

Hi,
You did a great job with this integration of pellematic data.
I use it now and it replaces all the yaml configuration using the REST integration.
The correct encoding of the REST result for french specific characters is iso-8859-1 and not utf-8 so I corrected it.
I also implemented a close on the request in order to free ressources. It resolves these types of error after a few hour of polling without homeassistant restart :

2023-03-16 23:36:22.656 ERROR (MainThread) [custom_components.oekofen_pellematic_compact] Error reading pellematic data
Traceback (most recent call last):
File "/usr/local/lib/python3.10/urllib/request.py", line 1348, in do_open
h.request(req.get_method(), req.selector, req.data, headers,
File "/usr/local/lib/python3.10/http/client.py", line 1282, in request
self._send_request(method, url, body, headers, encode_chunked)
File "/usr/local/lib/python3.10/http/client.py", line 1328, in _send_request
self.endheaders(body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.10/http/client.py", line 1277, in endheaders
self._send_output(message_body, encode_chunked=encode_chunked)
File "/usr/local/lib/python3.10/http/client.py", line 1037, in _send_output
self.send(msg)
File "/usr/local/lib/python3.10/http/client.py", line 975, in send
self.connect()
File "/usr/local/lib/python3.10/http/client.py", line 941, in connect
self.sock = self._create_connection(
File "/usr/local/lib/python3.10/socket.py", line 845, in create_connection
raise err
File "/usr/local/lib/python3.10/socket.py", line 833, in create_connection
sock.connect(sa)
TimeoutError: [Errno 110] Operation timed out

If you can merge it in your branch, it would be great.
For information, my pellemetic version is v4.00

Hi @cnico,
thank you for the improvement 👍
Yes the encoding was incorrect.
I will test it and create a new release 🚀
Dom


UI Test Framework

Closed this with a new PR https://github.com/wso2/product-is/pull/1175

Closed this with this new PR https://github.com/wso2/product-is/pull/1175


Update URL parameter to match what's listed

Just a small fix that I was foolishly bitten by :smile:

D'oh. Thanks!


Does not compile with latest nightly

Probably due to changes in rustc/ syntex

False alarm. Was using at an old branch.


[HOW TO] parse end modify AQL string in javascript?

[HOW TO] parse end modify AQL string in javascript?
aqb library can do it?

Can you please explain in more detail what you want to do? Maybe add some pseudo code as example. I don't understand your question like this.

in javascript
list = new List("
  FOR cat IN Cats
    FILTER cat.name == 'Tom'
    RETURN cat
")

I want to create auto updating list, i want to know how props using in filter and watch this props changes.
List.watch('name', function(){
  list.update()
})

cat = List.get('Cat', {name: 'Tom'})
cat.name = 'Changed name'
cat.save()

// then list feels this change and autoupdate

i want parse list selector like this
selector = "
  FOR cat IN Cats
    FILTER cat.name == 'Tom'
    FILTER cat.removed == false
    RETURN cat
"

props = getUsedProps(selector) // ['name', 'removed']

Documents do not have a life cycle, nor are they JavaScript-like objects. You can't monitor changes to them, like if updated via arbitrary AQL queries. You could however write a Foxx service and only modify your documents through that service in order to gain control and perform some action when a change is requested via a custom endpoint.

Documents do not have a life cycle, nor are they JavaScript-like objects.
God... I'm writing ORM framework

Aha, so this is not about anything server-side. You didn't make this clear. You can do whatever you want on the client-side, that is up to you. We can't provide support for that however, if it's not somehow related to our products.
What might help you is that there's an HTTP endpoint which takes an AQL query string, parses it into an AST and returns that without executing anything. This functionality is exclusively implemented in the server; we don't provide parsers that would do the same outside of ArangoDB. You could go ahead and write one, but be aware of the complexity of such an undertaking, and that AQL may change over time, which would require maintenance work from your side.
The query validation endpoint is POST /_api/query
https://docs.arangodb.com/3.3/HTTP/AqlQuery/#parse-an-aql-query
Note that you can't predict possible runtime errors using the AST, and that some parts can be dynamic (not known at query compile time), so you can't really tell the outcome of the query in advance.

You find the parser/lexer code here: https://github.com/arangodb/arangodb/tree/devel/arangod/Aql#dbe0017c6dcb65c69058af5c4361bb45-09bca2f43bbac82d988a3b5046f39a227a5ff4ba (grammer.* and tokens.* files)


Fixes #399

A picture tells a thousand words
Before this PR

After this PR

Coverage increased (+0.1%) to 43.643% when pulling 4ac7a889dbcec275a6dd565488d90e75a234c40c on verneområdeMockupValue into 31531789e5e5937955e1bb911cea3e3ee261d10f on master.


Delete Dependency on FeaturePotentialBending

You can safely remove the dependency of "FeatureExcludedVolumeSc" in the calculation of the bending potential.
The reason: every bond is guaranteed to have a minimum length of 2 due to bond vector set. Therefore, there will be no undefined behavior as there are no bonds of length zero also in the ideal case.
https://github.com/sunprancekid/LeMonADE_StiffCyclic/blob/7166b798cbd1b6280ddd20780d7c3708d5811f36/feature/FeaturePotentialBending.h#L225-L226

This feature requirement has been removed from the bending potential feature.


Ensure timer does not pause when test loses focus

By changing our timer to use a Web Worker we should be able to prevent it from pausing when a candidate navigates away from the test.
Problem
Our timer counts down however if the user does one of the following (for example) then the timer pauses:

stops interacting with the screen (e.g. they are reading the page but not moving mouse or pressing keyboard)
clicks elsewhere on the screen (e.g. they make notes in a separate document)

This is because modern browsers and operating systems try to manage resources and throttle/pause scripts that are running on pages that are no longer in focus.
Our timer will recalculate and adjust to the correct time when the test is in focus again however this jump in time is causing some participants to believe their test has been cut short. In addition for some participants the recalculation means their test has expired and so auto-submits.
Participants have been making contact with the support desk about this issue.
Solution
In https://github.com/jac-uk/qt/issues/9 we investigated whether there is a way we can show a message to the test participant or whether the problem could be avoided entirely. We discovered that Web Workers could come to our rescue therefore this ticket is about changing our timer to use a web worker. This should mean that the timer keeps counting down even if the test window loses focus.
Here are some useful links:

Can I Use => 98% browser support
Mozilla docs
W3Schools tutorial
Example timer using a web worker
Using web workers in VueJS

Video demonstrating the problem
https://github.com/jac-uk/qt/assets/8524401/fad07cec-ccd0-4e2a-bd88-3eac988d48a0

Just adding an update here:
So the pausing of the countdown is something we added in so it can be removed. However there is still the issue with resetting of the clock on the local machine.
It appears that WebWorkers and SharedWorkers dont continue to run when the page/pages close or are refreshed.
I think the best fix is to stick with what we've got and just improve the UX by maybe not displaying the timer immediately when the user comes back to the page (having clicked away). We could display some text saying 'Recalculating time' then have it update once the data is available.

Hey team! Please add your planning poker estimate with Zenhub @tomlovesgithub @warrensearle @HalcyonJAC


Code Beautification

This section of the EncryptedMixin
        if not self.max_length:
            self.max_length = 10
        self.unencrypted_max_length = self.max_length
        self.max_length = calc_encrypted_length(self.unencrypted_max_length)

Can be written better
        self.unencrypted_max_length = self.max_length or 10
        self.max_length = calc_encrypted_length(self.unencrypted_max_length)

This saves you the if statement and reassignment.

Really, since unencrypted_max_length isn't used anywhere else, the whole thing could be:
self.max_length = calc_encrypted_length(self.max_length or 10)


Support for AWS Athena Connection via JDBC

Is your feature request related to a problem? Please describe.
Support for AWS Athena Connection via JDBC.
Describe the solution you'd like
Develop the Athena Connection Extension.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
https://docs.aws.amazon.com/athena/latest/ug/what-is.html
https://docs.aws.amazon.com/athena/latest/ug/connect-with-jdbc.html

How to Unit-Test Athena Connection

maven build whole project

metatron-discovery $ mvn clean install -DskipTests

check athena plugin in discovery-distribution

metatron-discovery $ ls -al discovery-distribution/extensions
-rw-r--r--   1 metatron  metatron  10374288 Aug  4 13:45 athena-connection-1.0.0-2.0.2-3.4.0-rc4.zip
-rw-r--r--   1 metatron  metatron   4622628 Aug  4 13:45 mssql-connection-7.3.0-3.4.0-rc4.zip

add system property(Plugin Path) in test class

  @BeforeClass
  public static void setSystemProps() {
    System.setProperty("pf4j.pluginsDir", "../discovery-distribution/extensions");
  }

When executing the test code, you can see the pluginPath specified in the debug log as shown below.

2020-08-04 15:02:08.583  INFO [-] [main] a.m.d.extensions.CustomPluginManager     : Plugin RuntimeMode :  = deployment
2020-08-04 15:02:08.583  INFO [-] [main] a.m.d.extensions.CustomPluginManager     : PluginPath : /Users/xxx/Documents/GitHub/metatron-discovery/discovery-server/../discovery-distribution/extensions


Strange behaviour of silences.expired

From the ChangeLog v0.94 :

Unsilenced alerts will now show recently expired silences if they are old enough. By default silences expired in the last 10 minutes will be shown, this can be configured by setting silences:expired option or --silences.expired flag. Setting this value to 5m will show silences if they expired in the last 5 minutes but only if the alert started firing at least 5 minutes ago.

Let's use the default config of silences.expired=10m.
10h : an alert fires
10h06 : I set a silence of 1 minute
10h07 : the silence expires
In this case I expect to see the alert re-appear with the expired silence with a label expired a few seconds ago.
The doc explains : Setting this value to 5m will show silences if they expired in the last 5 minutes but only if the alert started firing at least 5 minutes ago.. In my case, it will show only if the alert started firing at least 10 minutes ago, as far as I understand the doc.
Question/bug 1: why should the alert be older than the silences.expired duration ?
Let's continue...
10h11 : I set a new silence of 1 minute
10h12 : the silence expires
I can see now the 2 silences with the labels expired a few seconds ago and expired 5 minutes ago.
Question/bug 2: At 10h07 I could not see the 1st silence. Why can I see it now (I can see the 2 silences now) ?

Question/bug 1: why should the alert be older than the silences.expired duration ?

Because the goal is to tell you why you suddenly see an alert, and so that you know there's likely no point debugging it as this is an old issue that was silenced but the silence just expired.
Duration requirement exists to only show the silence where it's relevant - when it's something you likely don't know about, rather than show you all silences ever linked to given alert. If both alert and silence are recent then you're likely to be the one silencing and so you know about it.

Question/bug 2: At 10h07 I could not see the 1st silence. Why can I see it now (I can see the 2 silences now) ?

Because at 10h07 alert was only 7 minutes old, and that's more recent then 10 minutes required by silences.expired=10m

Thanks for your answers.
Let me give you the real use cases
Question/bug 1
In the Production environment, we are not watching Karma all the time. We have other alerting systems. But Karma is the best tool to have an overview of all the alerts.
In this context, we would not set silences.expired to 10 minutes because we would miss that label nearly all the time. Setting 24h or even 72h (for week-ends) is more relevant.
Day 1...
18h00 : an alert fires
18h20 : I set a silence of 1 hour (and I try to fix the problem)
19h00 : the alert still fires and I decided that I could go home, the problem can be fixed tomorrow. I forgot to add a new silence for the night.
19h20 : the alert comes visible again (the silence expired)
For what I understand, the label "expired" will show only at 18h20 the day after (day 2).
In that case, that label is really needed at 7 am when colleagues come to work and will see that alert.
Question/bug 2
Back to the previous example (theoric example) : if you decide to not show the label at 10h10, for what reason would you show it at 10h12 ?
Transposition in the real-case example :
At 10am the day after, I see my alert still fires and I set a new silence for 12h (will expire at 10pm)
At 7am day 3, colleagues will see that alert again, but with the labels of the 2 silences. Why was the first label hidden at day 2 and why is it showing at day 3 ?

Hello,
Any update on this ?

Hello,
I was thinking... from Changelog v0.100 :
silences:expired option no longer takes alerts age into account.

Does that mean this issue has become N/A ?
I have not had time to test yet.

The issue became N/A since a while, probably since v0.100.
It can be closed.


Semantic conventions

Getting the ball slowly rolling on moving towards Otel semantic conventions for span names and attributes
Most relevant links are

http
db
faas

TODO: testing?

Hi :wave:,
Thanks for opening this PR. I see that you're trying to push for semantic conventions, however I disagree with their usage in this case. The collected telemetry data will get more vague, and there are also some properties you lost in the conversion. I disagree that all attributes should be called db.cf.<x>, as you lose searchability by name of attribute.
A specific example: Cloudflare also has a PubSub product, entirely separate from Queues. Eventually, that will also get more API in workers, so how will you differentiate a queue trigger from a pubsub trigger, if you use the semantic "queue" trigger type for both? I think it's best to keep the attributes not-entirely-semantic, so they convey more (and more accurate) information.
With all that said, I'm not the maintainer of this project, so @evanderkoogh will have the final say.

Thanks for opening this PR. I see that you're trying to push for semantic conventions, however I disagree with their usage in this case. The collected telemetry data will get more vague, and there are also some properties you lost in the conversion. I disagree that all attributes should be called db.cf.<x>, as you lose searchability by name of attribute.

I mostly care about the fetch/Http conventions (particularly span name).
The KV and DO instrumentations are largely a best first stab.
Would using the existing SemanticAttributes for DB_NAME, DB_SYSTEM, DB_OPERATION etc with the kv.* and do.* attributes becoming e.g. cf.kv.cache_ttl ? In this case the main thing is a desire to have camelCase suffixes become snake_case following the pattern of existing semantic conventions.

A specific example: Cloudflare also has a PubSub product, entirely separate from Queues. Eventually, that will also get more API in workers, so how will you differentiate a queue trigger from a pubsub trigger, if you use the semantic "queue" trigger type for both? I think it's best to keep the attributes not-entirely-semantic, so they convey more (and more accurate) information.

The semantic conventions has a Should in there, so how about queue for queue and pubsub for pubsub?

With all that said, I'm not the maintainer of this project, so @evanderkoogh will have the final say.

Appreciate the feedback here, trying to make this better for all users, not just my specific use case 🙏

Anyways, here are some spans (I just logged them to console using a ConsoleSpanExporter I'll throw up in a separate PR)

 Spans ahead
/do hit
{"traceId":"bfb51783801c6cc6c113cff3f0d5d029","parentSpanId":"","traceState":"","name":"fetchHandler","id":"373022780407ea12","kind":1,"startTime":1694704986097,"endTime":1694704986172,"duration":75,"attributes":{"faas.trigger":"http","faas.coldstart":true,"faas.execution":"8069a112fbab3075","http.method":"GET","http.url":"https://otel-test.shopify-hackathon8867.workers.dev/favicon.ico","http.host":"otel-test.shopify-hackathon8867.workers.dev","http.scheme":"https:","http.target":"/favicon.ico","http.route":"/favicon.ico","http.user_agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36","http.request_content_length":null,"http.request_content-type":null,"http.accepts":null,"net.colo":"SEA","net.country":"US","net.request_priority":"","net.tls_cipher":"ECDHE-RSA-AES128-GCM-SHA256","net.tls_version":"TLSv1.2","net.asn":209,"net.tcp_rtt":1,"greeting":"G'day World","http.status_code":200,"http.response_content_length":null,"http.response_content-type":"text/plain;charset=UTF-8"},"status":{"code":1},"events":[],"ended":true,"links":[],"instrumentationLibrary":{"name":"@microlabs/otel-cf-workers"},"traceFlags":1,"resource":{"_attributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"asyncAttributesPending":false,"_syncAttributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"_asyncAttributesPromise":""},"droppedAttributesCount":0,"droppedEventsCount":0,"droppedLinksCount":0}
{"traceId":"bfb51783801c6cc6c113cff3f0d5d029","parentSpanId":"373022780407ea12","traceState":"","name":"fetch: workers.dev","id":"4592334286a898ec","kind":2,"startTime":1694704986172,"endTime":1694704986338,"duration":166,"attributes":{"http.method":"GET","http.url":"https://workers.dev/","http.host":"workers.dev","http.scheme":"https:","http.target":"/","http.route":"/","http.user_agent":null,"http.request_content_length":null,"http.request_content-type":null,"http.accepts":null,"http.status_code":200,"http.response_content_length":null,"http.response_content-type":"text/html; charset=utf-8"},"status":{"code":0},"events":[],"ended":true,"links":[],"instrumentationLibrary":{"name":"@microlabs/otel-cf-workers"},"traceFlags":1,"resource":{"_attributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"asyncAttributesPending":false,"_syncAttributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"_asyncAttributesPromise":""},"droppedAttributesCount":0,"droppedEventsCount":0,"droppedLinksCount":0}
{"traceId":"cb06ec7eb1661e5203ce209e917d87cc","parentSpanId":"ac55e137de49d65a","traceState":"","name":"do:storage:get","id":"01ee797c8e61613f","kind":2,"startTime":1694704986996,"endTime":1694704986996,"duration":0,"attributes":{"operation":"get","db.cf.key":"something","db.cf.hasResult":true},"status":{"code":0},"events":[],"ended":true,"links":[],"instrumentationLibrary":{"name":"@microlabs/otel-cf-workers"},"traceFlags":1,"resource":{"_attributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings-do","service.namespace":"","service.version":""},"asyncAttributesPending":false,"_syncAttributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings-do","service.namespace":"","service.version":""},"_asyncAttributesPromise":""},"droppedAttributesCount":0,"droppedEventsCount":0,"droppedLinksCount":0}
{"traceId":"cb06ec7eb1661e5203ce209e917d87cc","parentSpanId":"ac55e137de49d65a","traceState":"","name":"do:storage:get","id":"038ad99dd975f7bc","kind":2,"startTime":1694704986996,"endTime":1694704986998,"duration":2,"attributes":{"operation":"get","db.cf.key":"something_else","db.cf.hasResult":false},"status":{"code":0},"events":[],"ended":true,"links":[],"instrumentationLibrary":{"name":"@microlabs/otel-cf-workers"},"traceFlags":1,"resource":{"_attributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud
.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings-do","service.namespace":"","service.version":""},"asyncAttributesPending":false,"_syncAttributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings-do","service.namespace":"","service.version":""},"_asyncAttributesPromise":""},"droppedAttributesCount":0,"droppedEventsCount":0,"droppedLinksCount":0}
{"traceId":"cb06ec7eb1661e5203ce209e917d87cc","parentSpanId":"","traceState":"","name":"do.alarmHandler:","id":"ac55e137de49d65a","kind":0,"startTime":1694704986996,"endTime":1694704986998,"duration":2,"attributes":{"faas.coldstart":false,"do.id":"f47ae871181ef6acfb0ea8d59d7c2e256963d11ee879963506867d6c97c46e69"},"status":{"code":0},"events":[],"ended":true,"links":[],"instrumentationLibrary":{"name":"@microlabs/otel-cf-workers"},"traceFlags":1,"resource":{"_attributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings-do","service.namespace":"","service.version":""},"asyncAttributesPending":false,"_syncAttributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings-do","service.namespace":"","service.version":""},"_asyncAttributesPromise":""},"droppedAttributesCount":0,"droppedEventsCount":0,"droppedLinksCount":0}

/ classic flavor
{"traceId":"5875cfdcf96742b6b4db1625840286d5","parentSpanId":"","traceState":"","name":"fetchHandler","id":"2b37837195879ed4","kind":1,"startTime":1694704967649,"endTime":1694704967876,"duration":227,"attributes":{"faas.trigger":"http","faas.coldstart":true,"faas.execution":"8069a09faf9a3075","http.method":"GET","http.url":"https://otel-test.shopify-hackathon8867.workers.dev/","http.host":"otel-test.shopify-hackathon8867.workers.dev","http.scheme":"https:","http.target":"/","http.route":"/","http.user_agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36","http.request_content_length":null,"http.request_content-type":null,"http.accepts":null,"net.colo":"SEA","net.country":"US","net.request_priority":"","net.tls_cipher":"ECDHE-RSA-AES128-GCM-SHA256","net.tls_version":"TLSv1.2","net.asn":209,"net.tcp_rtt":1,"greeting":"G'day World","http.status_code":200,"http.response_content_length":null,"http.response_content-type":"text/plain;charset=UTF-8"},"status":{"code":1},"events":[],"ended":true,"links":[],"instrumentationLibrary":{"name":"@microlabs/otel-cf-workers"},"traceFlags":1,"resource":{"_attributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.nam
espace":"","service.version":"0.1"},"asyncAttributesPending":false,"_syncAttributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"_asyncAttributesPromise":""},"droppedAttributesCount":0,"droppedEventsCount":0,"droppedLinksCount":0}                                                                        {"traceId":"5875cfdcf96742b6b4db1625840286d5","parentSpanId":"2b37837195879ed4","traceState":"","name":"fetch: workers.dev","id":"7cd59b09883509bb","kind":2,"startTime":1694704967876,"endTime":1694704968395,"duration":519,"attributes":{"http.method":"GET","http.url":"https://workers.dev/","http.host":"workers.dev","http.scheme":"https:","http.target":"/","http.route":"/","http.user_agent":null,"http.request_content_length":null,"http.request_content-type":null,"http.accepts":null,"http.status_code":200,"http.response_content_length":null,"http.response_content-type":"text/html; charset=utf-8"},"status":{"code":0},"events":[],"ended":true,"links":[],"instrumentationLibrary":{"name":"@microlabs/otel-cf-workers"},"traceFlags":1,"resource":{"_attributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"asyncAttributesPending":false,"_sy
ncAttributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sd
k.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"_asyncAttributesPromise":""},"droppedAttributesCount":0,"droppedEventsCount":0,"droppedLinksCount":0}                                                                                {"traceId":"069a8fdc1268038aee86f34b0af3265c","parentSpanId":"5e5060b2e70fa69e","traceState":"","name":"fetch: cloudflare.com","id":"4ce598a54f600f49","kind":2,"startTime":1694704967968,"endTime":1694704968062,"duration":94,"attributes":{"http.method":"GET","http.url":"https://cloudflare.com/","http.host":"cloudflare.com","http.scheme":"https:","http.target":"/","http.route":"/","http.user_agent":null,"http.request_content_length":null,"http.request_content-type":null,"http.accepts":null,"http.status_code":200,"http.response_content_length":null,"http.response_content-type":"text/html; charset=utf-8"},"status":{"code":0},"events":[],"ended":true,"links":[],"instrumentationLibrary":{"name":"@microlabs/otel-cf-workers"},"traceFlags":1,"resource":{"_attributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.s
dk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"asyncAttributesPending":false,"_syncAttributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"_asyncAttributesPromise":""},"droppedAttributesCount":0,"
droppedEventsCount":0,"droppedLinksCount":0}                                                                                {"traceId":"069a8fdc1268038aee86f34b0af3265c","parentSpanId":"5e5060b2e70fa69e","traceState":"","name":"cache:stuff:match","id":"8ef0ad13b2ba1093","kind":2,"startTime":1694704968062,"endTime":1694704968072,"duration":10,"attributes":{"cache.name":"stuff","http.url":"https://no-exist.com/","cache.operation":"match","cache.hit":true},"status":{"code":0},"events":[],"ended":true,"links":[],"instrumentationLibrary":{"name":"@microlabs/otel-cf-workers"},"traceFlags":1,"resource":{"_attributes":{"cloud.provider":"cloudflare","cloud.platf
orm":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"asyncAttributesPending":false,"_syncAttributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"_asyncAttributesPromise":""},"droppedAttributesCount":0,"droppedEventsCount":0,"droppedLinksCount":0}                                                    {"traceId":"069a8fdc1268038aee86f34b0af3265c","parentSpanId":"5e5060b2e70fa69e","traceState":"","name":"OTEL_TEST get","id":"b073db57d8d31f31","kind":2,"startTime":1694704968062,"endTime":1694704968082,"duration":20,"attributes":{"binding_type":"KV","db.name":"OTEL_TEST","db.system":"Cloudflare KV","db.operation":"get","db.statement":"get non-existant","db.cf.key":"non-existant","db.cf.has_result":false},"status":{"code":0},"events":[],"ended":true,"links":[],"instrumentationLibrary":{"name":"@microlabs/otel-cf-workers"},"traceFlag
s":1,"resource":{"_attributes":{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScri
pt","telemetry.sdk.name":"@microlabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"asyncAttributesPending":false,"_syncAttributes":
{"cloud.provider":"cloudflare","cloud.platform":"cloudflare.workers","cloud.region":"earth","faas.max_memory":128,"telemetry.sdk.language":"JavaScript","telemetry.sdk.name":"@micr
olabs/otel-workers-sdk","service.name":"greetings","service.namespace":"","service.version":"0.1"},"_asyncAttributesPromise":""},"droppedAttributesCount":0,"droppedEventsCount":0,
"droppedLinksCount":0}

@DaniFoldi and @evanderkoogh keen to hear any feedback on this if you have any

I agree that we should fully qualify the product in the attribute keys after cf... (so db.cf.kv.foobar = 'wat'). I think this would resolve your concerns about searchability @DaniFoldi?
Here's a general pitch in favor of semantic conventions:

Adhering to semantic conventions will make it so that o11y software (OSS projects and vendors) can support Cloudflare worker trace analysis out-of-the-box. e.g. if a vendor has a generic "database performance" page with logic to perform p99s per span with db.statement calls, Cloudflare spans will be analyzeable with no modification whatsoever.
If we stabilize on some good Cloudflare semantic conventions in this repo (which will necessarily entail the db.cf... prefix), then we can submit them upstream and have them included in this page here. That will let OSS projects and vendors build custom Cloudflare trace analysis tooling on stable APIs.

Hey @plantfansam, I am certainly very interested in your opinions on this, seeing as you have a ton more experience with the spec and with integrating that with query solutions. So thanks for chipping in here.
Now I am not a big fan of db.cf.x for both the reason @DaniFoldi mentioned, but also because it would make some of those "prepared" queries completely useless if you run that over both KV and DO spans, because of the nature of the systems are so incredibly different.
But I also love to follow some of those conventions so that we can make it easier for external parties to automatically include those in their queries.
So @plantfansam, would it be better to do say db.cf.kv.key or should we do a db.cf_kv.key? Or would we expect those 3rd parties to also filter based on the dbSystem key?
And we have had some discussions about the HTTP Span Name already, but I am relatively reluctant to go with the Semantic Convention there. We have no way of knowing a route upfront. The pathname is very likely to include things like IDs, so I really wouldn't want to treat that as the route. And without route, the span name would basically be GET or POST.
Now what we could do is at the end of the span check if the user has manually set the ROUTE information and then change the span name accordingly? But I am looking forward to people's opinion on that.

And we have had some discussions about the HTTP Span Name already, but I am relatively reluctant to go with the Semantic Convention there. We have no way of knowing a route upfront.

I wonder if we performantly allow users to configure this. So on boot you pass a config option like:
{
  "restfulAction/:id": {"regex": RegExp.new("https://foobar.com/restfulAction/[d+]"), // or whatever the regex is
  "anotherRestfulAction/:id": {"regex": RegExp.new("https://foobar.com/anotherRestfulAction/[d+]")
}

If config is unset, then default to HTTP span name as host, if config object set, try to parse. Would want to benchmark this for sure...

Rather than muddy things with intermediate work, I'll wait until we have some stronger consensus on attribute names before updating this PR.

So @plantfansam, would it be better to do say db.cf.kv.key or should we do a db.cf_kv.key? Or would we expect those 3rd parties to also filter based on the dbSystem key?

I like db.cf.kv.key because it hews more closely to current semantic conventions. As an example, take the semconv attributes for aws dynamodb: aws.dynamodb.consumed_capacity, aws.dynamodb.table_names.

Following that pattern we should end up with cf.kv.key and db.system="cloudflarekv" right?

And we have had some discussions about the HTTP Span Name already, but I am relatively reluctant to go with the Semantic Convention there. We have no way of knowing a route upfront.

I wonder if we performantly allow users to configure this. So on boot you pass a config option like:
{
  "restfulAction/:id": {"regex": RegExp.new("https://foobar.com/restfulAction/[d+]"), // or whatever the regex is
  "anotherRestfulAction/:id": {"regex": RegExp.new("https://foobar.com/anotherRestfulAction/[d+]")
}

If config is unset, then default to HTTP span name as host, if config object set, try to parse. Would want to benchmark this for sure...

I see where you are going, but that means that you need to perfectly duplicate your URL parsing. Once in your otel config and once in your router. And they could use different configuration mechanics.
And if you screw that up it is going to be hard to figure that out because the thing you are relying on to find that issue is wrong.

So @plantfansam, would it be better to do say db.cf.kv.key or should we do a db.cf_kv.key? Or would we expect those 3rd parties to also filter based on the dbSystem key?

I like db.cf.kv.key because it hews more closely to current semantic conventions. As an example, take the semconv attributes for aws dynamodb: aws.dynamodb.consumed_capacity, aws.dynamodb.table_names.

So AWS doesn’t use the ‘db’ prefix for their databases?
My question more is, do we have to stick with two dots or can we have more?

So AWS doesn’t use the ‘db’ prefix for their databases?

AWS doesn't (for some reason) but basically every other one with unique attribute keys (cassandradb used as example) does

My question more is, do we have to stick with two dots or can we have more?
I prefer db.cf.kv.key, but if vendors are going to not parse that properly, but handle db.cf_kv.key properly, I would pick that.

Making some assumptions based on our own experiences and a reading of the spec, but attribute keys are just strings so we should be fine to go with db.cf.kv.key

Cool.. I am happy to go with db.cf.kv.key and db.cf.do.key etc..
How about we revert the span name for now and I'll open up an issue to further discuss that. And then we can get all the db.* one in. Want to get those in as early as possible for people to realise that they have changed before we get to a proper 1.0.0

So AWS doesn’t use the ‘db’ prefix for their databases?

Looks like no, but I think we can 😄

My question more is, do we have to stick with two dots or can we have more?

I think it's OK to have more than 2 dots. See e.g. rabbitmq's messaging.rabbitmq.destination.routing_key

And if you screw that up it is going to be hard to figure that out because the thing you are relying on to find that issue is wrong.

Yeah, I think you're right. Needs more 🤔

How about we revert the span name for now and I'll open up an issue to further discuss that. And then we can get all the db.* one in. Want to get those in as early as possible for people to realise that they have changed before we get to a proper 1.0.0

I'm happy with that 😄

So @plantfansam, would it be better to do say db.cf.kv.key or should we do a db.cf_kv.key? Or would we expect those 3rd parties to also filter based on the dbSystem key?

I like db.cf.kv.key because it hews more closely to current semantic conventions. As an example, take the semconv attributes for aws dynamodb: aws.dynamodb.consumed_capacity, aws.dynamodb.table_names.

Following that pattern we should end up with cf.kv.key and db.system="cloudflarekv" right?

Yeah, I don't think there's an established convention for whether you should use e.g. db. or messaging. before vendor-specific attributes. Rabbitmq uses messaging. while dynamodb (as you point out) uses aws.. My personal preference is to include db. in the attr name (so db.cf.kv.key), but I don't think the community has an established perspective there.

Just documenting the HTTP_ROUTE and span name behavior from upstream

they pull the route off the rpcMetadata here
and set the span name based on this (if defined) here
and here is a route they set during the test which is checked here

Gonna revert the route/span name stuff for now in the interest of having a cleaner PR here, but just wanted to document this somewhere with some links for a convenient reference point.

I put your comment in a HTTP span name issue.

 So shouldn’t be a draft anymore?
Also, please don’t take the discussion to mean I don’t appreciate the PR. I absolutely love other people getting involved and improving things for not just themselves, but the entire community.

 So shouldn’t be a draft anymore?

I think so, but let me do a quick search of our span storage to ensure we don't have any other camelCase attrs I'm missing or anything that looks funky.

Also, please don’t take the discussion to mean I don’t appreciate the PR. I absolutely love other people getting involved and improving things for not just themselves, but the entire community.

This was perfect for me, discussion is good.

There are a few more http attributes that I missed existing conventions of, and additionally for consistency I think the cf.* attributes added via gatherOutgoingCfAttributes should be cf.snake_case instead of cf.camelCase for consistency.
I'll do both of these additions as separate commits and then mark this PR as ready for review

This branch is now (finally) ready for review
A few notes here about opentelemetry-js SemanticConventions we are using that differ from spec (I'll open this as an issue here and try to update opentelemetry-js I guess)

http.request_content_length should be http.request.body.size
http.status_code should be http.response.status_code
http.scheme should be url.scheme
http.user_agent should be user-agent.original

Thanks @rdooley! I am merging this now, but might be a day or two before I have a chance to release it. Currently on PTO

Thanks @rdooley! I am merging this now, but might be a day or two before I have a chance to release it. Currently on PTO

Awesome, no rush on my end.
I'm gonna try to get a look at #61 later this week and maybe get the ball rolling on #62 if i'm feeling ambitious


oh-my-zsh: 2024-07-03 -> 2024-08-04

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for oh-my-zsh is: Framework for managing your zsh configuration
meta.homepage for oh-my-zsh is: https://ohmyz.sh/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024-07-15 in filename of file in /nix/store/x00imj0m55f901n41b105sgbpswkv9ng-oh-my-zsh-2024-07-15

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

oh-my-zsh

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/x00imj0m55f901n41b105sgbpswkv9ng-oh-my-zsh-2024-07-15 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/8c22a2b5a004140db14223efc74122e45c4fe19c#oh-my-zsh

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/x00imj0m55f901n41b105sgbpswkv9ng-oh-my-zsh-2024-07-15
ls -la /nix/store/x00imj0m55f901n41b105sgbpswkv9ng-oh-my-zsh-2024-07-15/bin

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

1 package built:

oh-my-zsh

Maintainer pings
cc @NeQuissimus for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for oh-my-zsh is: Framework for managing your zsh configuration
meta.homepage for oh-my-zsh is: https://ohmyz.sh/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024-08-04 in filename of file in /nix/store/d3gpy4shavqjg4w4q8nmpd9kwjywfmbg-oh-my-zsh-2024-08-04

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

oh-my-zsh

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/d3gpy4shavqjg4w4q8nmpd9kwjywfmbg-oh-my-zsh-2024-08-04 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/0e22efbc05108cd5d4b1ced20192987097f24a7b#oh-my-zsh

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/d3gpy4shavqjg4w4q8nmpd9kwjywfmbg-oh-my-zsh-2024-08-04
ls -la /nix/store/d3gpy4shavqjg4w4q8nmpd9kwjywfmbg-oh-my-zsh-2024-08-04/bin

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

1 package built:

oh-my-zsh

Maintainer pings
cc @NeQuissimus for testing.


Installation Build Caffe and pycaffe

Hi, author.
Can you explain how to build Caffe and pycaffe in directory caffe-oim?
when I run the command " make all -j" produces the following error :
In file included from .build_release/src/caffe/proto/caffe.pb.cc:4:0:
.build_release/src/caffe/proto/caffe.pb.h:46:51: error: \u2018AuxiliaryParseTableField\u2019 in namespace \u2018google::protobuf::internal\u2019 does not name a type
static const ::PROTOBUF_NAMESPACE_ID::internal::AuxiliaryParseTableField aux[]
^
Makefile:582: recipe for target '.build_release/src/caffe/proto/caffe.pb.o' failed
make: *** [.build_release/src/caffe/proto/caffe.pb.o] Error 1
make: *** Waiting for unfinished jobs....
and how to following the Caffe installation instructions? which protobuf version were you used?

Hi, have you solved it?

No ::>_<::


:bug: nohang service fails on Ubuntu 23.10

tried with the alpha but I found this issue already on 2.5.0
PRETTY_NAME="Ubuntu 23.10"
NAME="Ubuntu"
VERSION_ID="23.10"
VERSION="23.10 (Mantic Minotaur)"
VERSION_CODENAME=mantic
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=mantic
LOGO=ubuntu-logo
KAIROS_VERSION_ID="v3.0.0-alpha1-v1.29.0-k3s1"
KAIROS_ARTIFACT="kairos-ubuntu-23.10-standard-amd64-generic-v3.0.0-alpha1-k3sv1.29.0+k3s1"
KAIROS_FLAVOR_RELEASE="23.10"
KAIROS_MODEL="generic"
KAIROS_REGISTRY_AND_ORG="quay.io/kairos"
KAIROS_BUG_REPORT_URL="https://github.com/kairos-io/kairos/issues"
KAIROS_SOFTWARE_VERSION="v1.29.0+k3s1"
KAIROS_NAME="kairos-standard-ubuntu-23.10"
KAIROS_IMAGE_REPO="quay.io/kairos/ubuntu:23.10-standard-amd64-generic-v3.0.0-alpha1-k3sv1.29.0-k3s1"
KAIROS_RELEASE="v3.0.0-alpha1"
KAIROS_ID="kairos"
KAIROS_FLAVOR="ubuntu"
KAIROS_VARIANT="standard"
KAIROS_TARGETARCH="amd64"
KAIROS_HOME_URL="https://github.com/kairos-io/kairos"
KAIROS_SOFTWARE_VERSION_PREFIX="k3s"
KAIROS_VERSION="v3.0.0-alpha1-v1.29.0-k3s1"
KAIROS_ID_LIKE="kairos-standard-ubuntu-23.10"
KAIROS_PRETTY_NAME="kairos-standard-ubuntu-23.10 v3.0.0-alpha1-v1.29.0-k3s1"
KAIROS_IMAGE_LABEL="23.10-standard-amd64-generic-v3.0.0-alpha1-k3sv1.29.0-k3s1"
KAIROS_GITHUB_REPO="kairos-io/kairos"

nohang status
root@localhost:/home/kairos# systemctl status --failed
× nohang-desktop.service - Sophisticated low memory handler
     Loaded: loaded (/lib/systemd/system/nohang-desktop.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Tue 2024-01-30 09:18:27 UTC; 57s ago
   Duration: 140ms
       Docs: man:nohang(8)
             https://github.com/hakavlad/nohang
   Main PID: 1607 (code=exited, status=1/FAILURE)
        CPU: 137ms

Jan 30 09:18:27 localhost systemd[1]: nohang-desktop.service: Scheduled restart job, restart counter is at 5.
Jan 30 09:18:27 localhost systemd[1]: Stopped nohang-desktop.service - Sophisticated low memory handler.
Jan 30 09:18:27 localhost systemd[1]: nohang-desktop.service: Start request repeated too quickly.
Jan 30 09:18:27 localhost systemd[1]: nohang-desktop.service: Failed with result 'exit-code'.
Jan 30 09:18:27 localhost systemd[1]: Failed to start nohang-desktop.service - Sophisticated low memory handler.

Seems to be related to https://github.com/hakavlad/nohang/issues/135 so we might need to bump the version once it is released. Or maybe we can even provide it as part of the framework image like suggested here https://github.com/kairos-io/kairos/issues/1609#issuecomment-1639656091

Kevin tested this with a new cluster, and it spins up fine. I don't understand how we use nohang exactly, so not sure if it's an issue. We will only find out with a loaded cluster, or if nohang is used for something specific that needs to be tested

Indeed it is likely the same issue, upstream have a fix for this https://github.com/hakavlad/nohang/issues/135,  hope new release of nohang fix the issue.

Today, we install nohang from ppa, which might not up to date. I think would consider to install it from source, we then have the fix.


Rebase with master; Solve conflicts; Upgrade fastboot and ember-cookies

I will be sending up more pull requests to get the feature out of the door.
I hope to get this merged in so we can continue the good work!
Thanks

@josemarluedke 👍  I don't seen any issues with this. Let's see what @marcoow says about creating a feature branch on the main repo before I merge this. See https://github.com/simplabs/ember-simple-auth/pull/964#issuecomment-234362666


Remove g_glip and class GrpcLibraryInterface

This PR aims to remove the pointer g_glip and class GrpcLibraryInterface.
Details:

grpc::GrpcLibraryCodegen is moved to grpc::GrpcLibrary, and it holds the a static object of grpc::internal::GrpcLibrary to replace the need for pointer g_glip.
grpc::GrpcLibraryInterface is removed.

Just noting here: this will need an internal cherry-pick, as there are internal usages of this header.


Adopt nullability annotations for XCode 6.3 and Swift 1.2

It's a little bit early for this PR, but i'm making it anyway for the future =) Apple is introducing nullability annotations in XCode 6.3 and Swift 1.2.
These allow better interoperability with Swift, and provide nice compiler warnings for Objective-C, when API is used in non-supported way.
I tried adding annotations where they made sense from API perspective, so this stuff should be reviewed. These changes should be backwards-compatible with XCode 6.2 and 6.1, since all defines are wrapped in if __has_feature(nullability).

Thanks for the contribution! I'd rather #define them somewhere common, I'll look into this myself.


Evaluation json file

Hi, may I know what is the file used in "--gt_file"? Is it train, test or val.json of MSVD-QA?
I want to replicate the result shown in paper.
python run_inference_qa_msvd.py
--cfg-path eval_configs/MovieChat.yaml
--gpu-id 0
--num-beams 1
--temperature 1.0
--video-path /path/to/your/video
--gt_file /path/to/your/question and answer file
--output_dir /path/to/your/output
--output_name msvd-qa
--fragment-video-path src/video_fragment/output.mp4 \

I download it from this repo, https://github.com/antoyang/just-ask. It has MSVD-QA, MSRVTT-QA and ActivityNet-QA. Maybe some preprocess code need be to wtrite by your own. Thank you for attention.

Hi, may I know what is the file used in "--gt_file"? Is it train, test or val.json of MSVD-QA? I want to replicate the result shown in paper. python run_inference_qa_msvd.py --cfg-path eval_configs/MovieChat.yaml --gpu-id 0 --num-beams 1 --temperature 1.0 --video-path /path/to/your/video --gt_file /path/to/your/question and answer file --output_dir /path/to/your/output --output_name msvd-qa --fragment-video-path src/video_fragment/output.mp4 \

It is the test_qa.json of MSVD-QA, Same as MSRVTT_QA and ActivityNet-QA. All is the test split.

Hi, may I know what is the file used in "--gt_file"? Is it train, test or val.json of MSVD-QA? I want to replicate the result shown in paper. python run_inference_qa_msvd.py --cfg-path eval_configs/MovieChat.yaml --gpu-id 0 --num-beams 1 --temperature 1.0 --video-path /path/to/your/video --gt_file /path/to/your/question and answer file --output_dir /path/to/your/output --output_name msvd-qa --fragment-video-path src/video_fragment/output.mp4 \

It is the test_qa.json of MSVD-QA, Same as MSRVTT_QA and ActivityNet-QA. All is the test split.

Thank you for your help~


[App Request] Wazuh

App Information

Name: Wazuh
Short Description: Wazuh is a free and open source security platform that unifies XDR and SIEM protection for endpoints and cloud workloads.
Official Website: https://wazuh.com/
GitHub Repository: https://github.com/wazuh/wazuh-docker
Docker Image: https://hub.docker.com/u/wazuh

Why do you want this app?
As a security-conscious individual with a home lab, Wazuh would be an excellent choice to enhance my device monitoring and security. As an open-source, self-hosted solution, Wazuh provides a powerful yet cost-effective way to maintain comprehensive visibility and control over the systems in my home environment.
Additional information?

Docker install documentation
wazuh single-node docker-compose.yml

Would love to have this done as well.


Redirection of microsoft/pyjion#237

Redirection of the https://github.com/microsoft/Pyjion/pull/237 PR into this fork.

I've been loosely following this project with high hopes of seeing a JIT API PEP (or some foundations of) being accepted.
Why was the microsoft repo archived and this is the source of truth now?


Make languages & policies user-configurable

Add three configurables:

g:vue_indent_languages replaces s:languages. It can be configured
before or after loading indent/vue.vim, and can be modified on the
fly.

g:vue_indent_open_close_tags configures the policy for indenting
open/close tags. It defaults to 0 which forces open/close tags for
sections in a vue single-file component to the first column.

g:vue_indent_first_line configures the policy for indenting the
first line after an open tag. It defaults to -1 which uses the
autoindent default, i.e. the same column as the open tag. It will
also preserve existing indentation when reindenting, which means
that authors can use their preferred first line indentation without
needing any special configuration.

Additionally g:vue_indent_first_line can be overridden per-language by
specifying a value for language.first_line. We use this for the html
language configuration to defer to html.vim for indenting the first line
of an html template.
Minor changes:

Since s:get_indentexpr is called lazily, it resets indentexpr before
returning.

Use searchpair() to find the closing tag instead of a hard-coded list.

For development and debugging, it's possible to :echo GetVueIndent()
which also enables error reporting and messages that are normally
squelched when called as indentexpr. Note that although GetVueIndent()
uses getpos('.') properly if line number isn't supplied, language
indenters vary between getpos('.') and v:lnum, so this is mostly
useful for debugging vue.vim's internal operation.

By the way, I think it would make a lot of sense for g:vue_indent_languages to eventually become g:vue_languages with a common structure for configuring indent/syntax simultaneously.  I guess that raises the question of whether it's better to do that rather than merging this directly. Let me know what you think.


Add imagePullSecrets section to templates

Adds the standard imagePullSecrets section to the api, dashboard and director templates.
Closes #95
References:
https://kubernetes.io/docs/concepts/containers/images/#specifying-imagepullsecrets-on-a-pod
https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/

Can you please add some appropriate words for people to ignore in this file: https://github.com/sorry-cypress/charts/blob/main/charts/sorry-cypress/changelog.md
And as you're adding new values, the readme will need updating too I'm afraid :(

Sorry, missed that!
All done @tico24 👍🏼


View as "Epoch time"

Hello,
I'm on Dbeaver 7.3.2 and when I want to change the view of a cell (right-click > View/format > Set {column} format), I can't choose Epoch Time et no other view option translate the data of my cell into date.
My friend has Dbeaver 5.0.0 and she has "Epoch Time" option working very well.
Please help !
Thank you !

Why can't you?
It is still there and works as before:

Please write more detaisl about the problem.

Why can't you?
It is still there and works as before:

Please write more detaisl about the problem.

I don't have it...

I don't have it...

Epock time transformation is available only for numeric columns. What data type your column has?

Epock time transformation is available only for numeric columns. What data type your column has?

numeric

numeric

Exemple : I took :<PHONE_NUMBER>000

Exemple : I took :<PHONE_NUMBER>000

Could you write exact data type name? It is in the column header tooltip. Or in the Metadata panel. Or on the Properties/Columns tab.
Also what database do you use?

Could you write exact data type name? It is in the column header tooltip. Or in the Metadata panel. Or on the Properties/Columns tab.
Also what database do you use?

I'm not sure that what you ask me
but I found that

I'm not sure that what you ask me
but I found that

the database is sqlite

the database is sqlite

I found what you met.
Indeed my column is noted ABC instead of 123 as I wished it were.
How can I change that ?

I found what you met.
Indeed my column is noted ABC instead of 123 as I wished it were.
How can I change that ?

Column data type:

Column data type:

On my side, the colonne is "DATE" and date is not considered numeric so I can't change to epoch time....
Unfortunatly, I don't know how I can't change that...

On my side, the colonne is "DATE" and date is not considered numeric so I can't change to epoch time....
Unfortunatly, I don't know how I can't change that...

Indeed my column is noted ABC instead of 123 as I wished it were.
How can I change that ?

Unfortunatelly that's not easy: https://stackoverflow.com/questions/21199398/sqlite-alter-a-tables-column-type
Most likely you will need to recreate your table.

Indeed my column is noted ABC instead of 123 as I wished it were.
How can I change that ?

Unfortunatelly that's not easy: https://stackoverflow.com/questions/21199398/sqlite-alter-a-tables-column-type
Most likely you will need to recreate your table.


raise error upon missing placeholder

In the scenario of a missing single placeholder, the mod operator did
not fail as it does when having multiple placeholder
>>> Markup("foo") % 42
Markup("foo")
>>> Markup("foo") % (42, 43)
TypeError: not all arguments converted during string formatting
>>> Markup("foo") % (42,)
TypeError: not all arguments converted during string formatting

This commits unifies the behaviour with the mod operator on native
strings and fails in the three above scenario

fixes #225

Checklist:

[x] Add tests that demonstrate the correct behavior of the change. Tests should fail without the change.
[x] Add or update relevant docs, in the docs folder and in code.
[x] Add an entry in CHANGES.rst summarizing the change and linking to the issue.
[x] Add .. versionchanged:: entries in any relevant code docs.
[x] Run pre-commit hooks and fix any issues.
[x] Run pytest and tox, no tests failed.

I think that version will misbehave the other way: looking at the behaviour of PyUnicode_Format (which implements __mod__ for str), the interesting bits look to be:
    if (PyTuple_Check(args)) {
        ctx.arglen = PyTuple_Size(args);
        ctx.argidx = 0;
    }
    else {
        ctx.arglen = -1;
        ctx.argidx = -2;
    }
    ctx.args_owned = 0;
    if (PyMapping_Check(args) && !PyTuple_Check(args) && !PyUnicode_Check(args))
        ctx.dict = args;
    else
        ctx.dict = NULL;
    ctx.args = args;

with PyMapping_Check documented as

returns 1 for Python classes with a __getitem__()

which would be the source of the issue: _MarkupEscapeHelper always has a __getitem__ and will never pass PyUnicode_Check (which is essentially isinstance(x, str)), so in the previous version it would always be considered a non-unicode "mapping" for which the warning is suppressed.
The new version overcorrects, however: now any "mapping" other than dict subclasses will error, even if they should not. For instance very oddly a list should not trigger an error:
"" % ['a']
''

The new check should probably replicate the behaviour of the original more precisely: the first clause takes care of tuples so the second should be hasattr(type(arg), '__getitem__') and not isinstance(arg, str), I think that matches the semantics of PyMapping_Check(args) && !PyUnicode_Check(args). Might be worth flipping the two clauses if Markup is more often formatted using a string than a "mapping".
And maybe use this occasion to skip the _MarkupEscapeHelper for the case of str? If my reading of it is correct, the behaviour looks to be to avoid triggering a type error for "numeric" formatting (although I'm not too sure why it forcefully converts the parameters to numbers if they're not, that would also change behaviour from the base), with the probably useful side-effect of making formatting lazy for "mappings".
But I don't think string args need any of that: they're necessarily going to be formatted in (as they're essentially positional) and thus escaped.


Automatically open some MoM menus when you start FP.

Hi EdoFro, is it possible to apply the same approach as for Tool Panel addon menu, to some of the menu-o-matic solutions?  In order to have the possibility to have some of them already open when you startP FP.
Thanks.
Originally posted by @Illegit in https://github.com/freeplane/freeplane/discussions/368#discussioncomment-6620094

Hi @Illegit,
How do You imagine this feature?

It should launch automatically all the MoM nodes from a map or just some of them?

I think only some of them
for example, the ones that have a special attribute

"MoM_autoLaunch": true

It has to launch the MoM nodes from which mindMap?
Alternatives:

From the active mindMap when FP starts
From all loaded mindMaps when FP starts
Only from a map named as "MoM_myToolbox.mm" and only if it is loaded.
From a map that the user can define in FP preferences (setting the path to its file), and FP opens it headless (hidden)
a combination of them

Should this also work everytime Freeplane opens a mindMap?

I think if its MoM nodes have the attribute, then they should be launch.
we can use Macmarrun's script for this

which of this options should be present in FP Preferences dialog?

BR
edo

I think it could be even more than expected.
Nice to have them.
Thanks to think about it

Hi @Illegit,
I released a new version of the addon that has this functionality
This is a first version, and I think it should be good enough for now.

only marked customMenu nodes are automatically launched
all marked menus form all opened maps are launched when starting Freeplane
when opening a mindMap that has AutoLaunch menus, they are automatically launched

to mark a customMenu node as "AutoLaunch", you have to add the 'launch' icon to it (it's a rocket:🚀)
like this:

Hi EdoFro, it is working as expected: Nice!
Thanks

ehhhh, It throws an error when creating a new map. sorry.
I released a corrected version.

ok. I think it is done.

Got it. Confirmed. Thanks.

@Illegit,
please take a look at this topic.
thanks,
edo


Enable private field promotion in Flutter for Dart 3.2

New feature in upcoming Dart 3.2. See https://github.com/dart-lang/language/issues/2020.

FYI @stereotype441 @mit-mit

Framework migration is currently blocked on waiting for https://github.com/dart-lang/sdk/commit/1da590fc3f6af8dc505e926551c0986fc05a67b6 to roll in.
Engine migration is blocked on https://github.com/flutter/engine/pull/45722.

This is completed. Private field promotion has been enabled for all dart code in the flutter/flutter repository and the flutter/engine repository.


Add a new board: Space Cubics OBC module 1

This PR is to add our OBC as a Zephyr target board.

@henrikbrixandersen, this on-board computer is a single board based on Arm Cortex-M3 DesignStart FPGA-Xilinx edition.  Please let me know if you find anything bad.  Major difference from dev kits are

We don't use XIP.  Zephyr image is copied from flash memory by FPGA
We use HRMEM, High Reliable memory instead of TCM.  From software point of view, it just looks like SRAM

@henrikbrixandersen, sorry for the delay.  I've added doc for the board.  Please review.  Thanks.

@henrikbrixandersen, do you have any concern?  I'd like to have any feedback.

@henrikbrixandersen, Thank you for your review and Happy new year!

So, what else do I need to get this one merged? Would someone enlighten me?

So, what else do I need to get this one merged? Would someone enlighten me?

Now you wait for additional reviews and approvals. A PR requires at least two approvals before being merged into Zephyr.


Access package assignment requests via Graph API bypass approval policy

When creating an access package assignment request with the Graph API, the approval policy is consistently bypassed.
When creating a direct access package assignment in the Azure Portal, I can specify if approvals are bypassed for that request.

Screenshot from this page.
When choosing not to bypass, the requestState and requestStatus parameters of the request are PendingApproval as expected.
However, when creating an access package assignement with the Graph API, the API always seems to bypass the approval. The requestState and requestStatus are Submitted and Accepted respectively, then automatically changes to Delivered and Fulfilled.
(Endpoint used : https://graph.microsoft.com/beta/identityGovernance/entitlementManagement/accessPackageAssignmentRequests)
When checking what the payload sent by the Azure Portal looks like (i.e the request that is not bypassing the approval), I get the following:
{
  "accessPackageAssignment": {
    "target": {
      "displayName": "John Doe",
      "email"<EMAIL_ADDRESS>    },
    "accessPackageId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "assignmentPolicyId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
  },
  "justification": "testing",
  "requestType": "AdminAdd",
  "parameters": [
    {
      "name": "IsApprovalRequired",
      "value": "true"
    }
  ]
}

The problem is that even when sending the exact same payload to the Graph API, and even if the assignment policy requires approval, the approval still get bypassed.
Desktop

OS: Windows 11
Browser: Edge
Version: 120.0.2210.77

Hello @quentinmarois
This is outside the scope of Graph Explorer but you should be able to easily find help here https://aka.ms/askgraph


Are msexchuid and amurl immutable even if end user migrate Exchange Server?

Thank you for writing clear document. Our team understand definition, but let me ask one question.
Are msexchuid and amurl immutable even if end user migrate Exchange Server? For example, some end users may migrate their on-premises Exchange Server to Office 365. When they start to use Office 365, are msexchuid and amurl same?
The background is we refer this document and try to make UserId from Exchange IdToken for backend. If these parameter keep same, we want to use this logic. If these params changed to another after migration, we need to consider it for making UserId.

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

ID: 709d2fe0-b7b5-5008-218c-6e84f5565998
Version Independent ID: d2cb30ef-4ba0-1d0b-d681-74dbf35bb6d0
Content: Inside the Exchange identity token in an Outlook add-in - Outlook Developer
Content Source: docs/add-ins/inside-the-identity-token.md
Product: outlook
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@NT-D Thanks for your question. However, with the move to Office 365, you may want to consider single sign on (SSO) instead. How to implement SSO may be useful in that case.
Also, just to clarify, do you mean if the properties msexchuid and amurl are available on the Office 365 servers? If so then yes but I don't believe the values of msexchuid and amurl are guaranteed to be the same after such a migration. For one thing, msexchuid is likely autogenerated by the Exchange server and so unlikely to be the same on a new server. As for the amurl, it's based on the domain of the mail server and the location of the certificate so the property value may be different for the Office 365 server. You'll probably need to construct new ids for migrated users.
I hope this helped answer your question. Let us know if you need further clarification and we can reopen this issue.
Thanks.

Hi @ElizabethSamuel-MSFT , thank you for your quick answer. I totally understand these properties will be different and I need to generate new ids :)
Yes, I'll implement with SSO, but start with Exchange Id Token for covering on-premises server, too :)

do you mean if the properties msexchuid and amurl are available on the Office 365 servers?
No. I mean msexchuid and amurl are same or not after migration. Office 365 is one example. End users may move their old on-premises exchange server to new on-premises exchange server or Office 365.
As you mentioned msexchuild and amurl will be different, I'll create new id.

It may be beneficial for developers to write up that we need to re-generate id in the page.
https://docs.microsoft.com/en-us/outlook/add-ins/authenticate-a-user-with-an-identity-token#map-the-token-to-a-user-in-your-backend
Thanks

hi @ElizabethSamuel-MSFT
May I ask the same question here?
Based on the document : (pasted in the following)
Exchange user identity token
Exchange user identity tokens provide a way for your add-in to establish the identity of the user. By verifying the user's identity, you can then perform a one-time authentication into your back-end system, then accept the user identity token as an authorization for future requests. Use the Exchange user identity token:
When the add-in is used primarily by Exchange on-premises users.
When the add-in needs access to a non-Microsoft service that you control.
As a fallback authentication (and authorization to Microsoft Graph) when the add-in is running on a version of Office that doesn't support SSO.
the exchangeidtoken shoudl also work for on-prem users, but I want to know how could other services to validate the exchangeidtoken, since based on the document it need visit amurl to get the public key to verify the token. As the on-prem scenario, how could we access it out of the on-prem env.
thanks.

Transferring to office-js-docs-pr repo as Outlook add-ins content has been moved there.


Error Whisper formatting to srt, vtt

Hi I'm trying to transcribe a file to srt or vtt.
thats my code:

var transcription = await OpenAI.instance.audio.createTranscription(
file: File(file),
model: "whisper-1",
language: "en",
responseFormat: OpenAIAudioResponseFormat.srt
);
var transcriptionResult = transcription.text;

But it throws this error:

VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: FormatException: Unexpected character (at line 2, character 1)
00:00:00,000 --> 00:00:06,320
^
#0      _ChunkedJsonParser.fail (dart:convert-patch/convert_patch.dart:1383:5)
#1      _ChunkedJsonParser.parse (dart:convert-patch/convert_patch.dart:913:48)
#2      _parseJson (dart:convert-patch/convert_patch.dart:35:10)
#3      JsonDecoder.convert (dart:convert/json.dart:610:36)
#4      JsonCodec.decode (dart:convert/json.dart:216:41)
#5      jsonDecode (dart:convert/json.dart:155:10)
#6      OpenAINetworkingClient.decodeToMap (package:dart_openai/src/core/networking/client.dart:535:12)
#7      OpenAINetworkingClient.fileUpload (package:dart_openai/src/core/networking/client.dart:475:46)

#8      OpenAIAudio.createTranscription (package:dart_openai/src/instance/audio/audio.dart:56:12)

#9      OpenAiDataSourceImpl.transcribeFile (package:voicetotext/data/network/datasource/impl/openai_datasourc<…>

Thank you for noticing this and reaching here, this is solved and will be available on the new release.


Update node engine version and bump abacus

Coverage remained the same at 91.741% when pulling cebb51966f0d67606bec0ca959a16df73bd28c02 on SAP:update-node into 8bcf0f08fa824da9519dd64d077e134bd24a0e28 on cloudfoundry-incubator:master.

Coverage remained the same at 91.741% when pulling 2811a89af8d873e0e6d965079fdb45eac4970421 on SAP:update-node into 8bcf0f08fa824da9519dd64d077e134bd24a0e28 on cloudfoundry-incubator:master.


Fixed to Window Rescaling in Morphoview

Updated display so window rescales correctly when resized by user.
This fixes #141

This is working great on Ubuntu! I didn't get it to work on WSL though. Are there additional steps involved other than recompiling Morphoview?

Try using the command below in the morphoview directory.
sudo make -f Makefile.linux install
That is all I did on WSL, maybe that will work?

Hmm, that's what I tried, but it isn't working on the WSL. It's working awesome on my Ubuntu desktop. Perhaps the graphics forwarding is creating some issue on my end.

Ah, like most problems we have encountered on WSL, this one was also fixed after a restart. It's working now on WSL too!!


clip prepross output one same value

Hi, I use clip prepross, and find that it output the same value on the same RGB dim.
`import torch
import clip
from PIL import Image
device = "cuda:2" if torch.cuda.is_available() else "cpu" # If using GPU then use mixed precision training.
model, preprocess = clip.load("ViT-B/32",device=device,jit=False) #Must set jit=False for training
print(preprocess(Image.open("./data/self_data/meme_set/1002.jpeg")))
tensor([[[1.9303, 1.9303, 1.9303,  ..., 1.9303, 1.9303, 1.9303],
[1.9303, 1.9303, 1.9303,  ..., 1.9303, 1.9303, 1.9303],
[1.9303, 1.9303, 1.9303,  ..., 1.9303, 1.9303, 1.9303],
...,
[1.9303, 1.9303, 1.9303,  ..., 1.9303, 1.9303, 1.9303],
[1.9303, 1.9303, 1.9303,  ..., 1.9303, 1.9303, 1.9303],
[1.9303, 1.9303, 1.9303,  ..., 1.9303, 1.9303, 1.9303]],
    [[2.0749, 2.0749, 2.0749,  ..., 2.0749, 2.0749, 2.0749],
     [2.0749, 2.0749, 2.0749,  ..., 2.0749, 2.0749, 2.0749],
     [2.0749, 2.0749, 2.0749,  ..., 2.0749, 2.0749, 2.0749],
     ...,
     [2.0749, 2.0749, 2.0749,  ..., 2.0749, 2.0749, 2.0749],
     [2.0749, 2.0749, 2.0749,  ..., 2.0749, 2.0749, 2.0749],
     [2.0749, 2.0749, 2.0749,  ..., 2.0749, 2.0749, 2.0749]],

    [[2.1459, 2.1459, 2.1459,  ..., 2.1459, 2.1459, 2.1459],
     [2.1459, 2.1459, 2.1459,  ..., 2.1459, 2.1459, 2.1459],
     [2.1459, 2.1459, 2.1459,  ..., 2.1459, 2.1459, 2.1459],
     ...,
     [2.1459, 2.1459, 2.1459,  ..., 2.1459, 2.1459, 2.1459],
     [2.1459, 2.1459, 2.1459,  ..., 2.1459, 2.1459, 2.1459],
     [2.1459, 2.1459, 2.1459,  ..., 2.1459, 2.1459, 2.1459]]])

`
It make train impossible, can everybody help me? thanks.

maybe it's because my data is always with same colour


[Feature] K8s 1.30 Support

Umbrella issue for supporting K8s 1.30 in Rancher.
See preliminary research done in spike https://github.com/rancher/rancher/issues/44210
For k8s 1.30, go version needs to updated to 1.22.x and k8s.io/gengo  library is upgraded to k8s.io/gengo/v2 ref
It has a few breaking changes.

args package is removed from gengo/v2: ref
deepcopy-gen generators are moved to k8s.io/code-generator ref

gengo is dependency in following repositories:

rancher/wrangler

https://github.com/rancher/rancher/issues/45324

rancher/norman

https://github.com/rancher/rancher/issues/45301

rancher/rke
rancher/rancher

other libraries which needs dependency upgrade:

rancher/lasso

https://github.com/rancher/rancher/issues/45216

Additional areas:

[ ] https://github.com/rancher/rancher/issues/45334
[ ] https://github.com/rancher/rancher/issues/45332
[ ] https://github.com/rancher/rancher/issues/45333
[ ] https://github.com/rancher/rancher/issues/45331

Fwiw, k8s.io/apiserver/pkg/apis/config no longer exists. It's used here:

github.com/rancher/rancher/pkg/controllers/management/secretmigrator/assemblers
github.com/rancher/rancher/pkg/schemas/management.cattle.io/v3

A new shell RC v0.2.1-rc.4 has been cut ready for use with the updated helm version.

For release notes, we would like to include the following limitations:

https://github.com/rancher/rancher/issues/46132 (planned to be addressed in July RKE2 patches)
For Azure cloud provider support (https://github.com/rancher/rancher/issues/44856 / https://github.com/rancher/rancher/issues/44857) we would like to add a note about UI changes not in 2.9.0 (https://github.com/rancher/dashboard/issues/11360) so "Edit as YAML" is a workaround.

Summary of K8s v1.30 support testing checklist.

:stopwatch:  =   Not started

:clock12:  =   In progress

:no_entry:  =   Blocked

:white_check_mark:  =  PASSED :white_check_mark:

:question: =  Have Question

Local cluster checks - :white_check_mark:

Docker Install - :white_check_mark:
Docker install and Upgrade - :white_check_mark:
HA install -  :white_check_mark:
Local Cluster HA Upgrade - :white_check_mark:

OS Certification -  :white_check_mark:

Hosted Clusters testing - :white_check_mark:

KDM Testing - :white_check_mark:

Fresh Install Checks -  :white_check_mark:
Upgrade checks -  :white_check_mark:
Canal + PNI enabled - :white_check_mark:
Downstream cluster ETCD Validation - :white_check_mark:  PASS
Downstream Control Plane Validation - :white_check_mark:  PASS

ETCD Validations - :white_check_mark:

Control plane Validations - :white_check_mark:

Local cluster HA updgrade

Local cluster RKE1 HA upgrade -   :white_check_mark:
Local cluster RKE2 HA upgrade -   :white_check_mark:
Local cluster K3s HA upgrade -   :white_check_mark:

RKE checks - :white_check_mark:

Rancher CLI checks - :white_check_mark:

Windows RKE2 provisioning :white_check_mark:

RKE2 Amazon Cloud provider enabled checks. - :white_check_mark:

Any other functional check for 1.27 - Service accounts - :white_check_mark:

Airgap checks - :white_check_mark:

RKE1 cluster - custom clusters - :white_check_mark:
RKE2 clusters - custom clusters - :white_check_mark:
K3s clusters - custom clusters - :white_check_mark:

Conformance Checks - CNCF Conformance tests for RKE Kubernetes cluster

Rancher -  :white_check_mark: PR Merged
RKE - :white_check_mark:  PR Merged

RKE2 and K3s Checks - :white_check_mark:

Node Driver Cluster Provisioning - :white_check_mark:

Downstream RKE2 cluster provisioning - :white_check_mark:

Fresh install :white_check_mark:
Upgrade :white_check_mark:

Downstream k3s cluster provisioning - :white_check_mark:

Fresh install :white_check_mark:
Upgrade  :white_check_mark:

Since OS checks are still remaining, moving tickets back to Actively QAing.


can someone update Draw all backtrack Chams ?

can someone update #730 ?

Just learing C++. Then it is easy


typescript error in react concurrent mode and it doesn't  let build successfully  in electron forge

I use react concurrent mode in electron . everything is okay while I run start script but
while I want to run electron-forge package it throw errors  and does not allow to make package
is there any way to ignore these errors and run like start script in electron forge
this is the main error :
✔ Checking your system
✔ Compiling Main Process Code
⠋ Compiling Renderer TemplateStarting type checking service...
✖ Compiling Renderer Template
An unhandled error has occurred inside Forge:
Compilation errors in the renderer: Hash: c08c5c09747663f80bfa
Version: webpack 4.42.0
Time: 13643ms
ERROR in /Users//Documents/Node/electron-forge/my-app/src/App.tsx
ERROR in /Users//Documents/Node/electron-forge/my-app/src/App.tsx(22,10):
TS2339: Property 'createRoot' does not exist on type 'typeof import("/Users/****/Documents/Node/electron-forge/my-app/node_modules/@types/react-dom/index")'.
*
pm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR!
npm ERR! Failed at the app package script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
The terminal process terminated with exit code: 1
Terminal will be reused by tasks, press any key to close it.

does anyone have a solution to solve this problem ?

In the future, it would help if you could create a small, reproducible example of your problem. (And also fill out the issue template correctly.)
That being said, this doesn't sound like an Electron Forge specific issue, but rather an issue between your code and Webpack.
If you need more assistance, please use one of the community forums.


Updating readmes with confliglet.

Just running configlet generate on the repo. I verified none of the READMEs changed in meaning.
Related to #203

Thanks for doing this; looks good.


fix: Use concrete Versioned type in From impl

Changes the From impl to use the Versioned type rather than the associated type (through obake::AnyVersion). This shouldn't change anything functionally but fixes an issue we were seeing where the obake impl From<foo::Foo_v0_1_0> for <foo::Foo_v0_1_0 as obake::Versioned>::Versioned impl was conflicting with other generic impls.
You can see a small reproducible example of this issue here: https://github.com/goodSyntax808/obake-example-issue which gives the following error when trying to compile:
error[E0119]: conflicting implementations of trait `std::convert::From<foo::Foo_v0_1_0>` for type `Batz`
  --> bar\src\lib.rs:7:1
   |
7  | / impl<T> From<T> for Batz
8  | | where
9  | |     T: Into<Cow<'static, str>>,
10 | | {
...  |
13 | |     }
14 | | }
   | |_^
   |
   = note: conflicting implementation in crate `foo`:
           - impl From<foo::Foo_v0_1_0> for <foo::Foo_v0_1_0 as obake::Versioned>::Versioned;

I believe this occurs because
impl From<foo::Foo_v0_1_0> for <foo::Foo_v0_1_0 as obake::Versioned>::Versioned can technically be the same as impl<T> From<T> for Batz if <foo::Foo_v0_1_0 as obake::Versioned>::Versioned implemented Into<Cow<'static, str>>. Using the actual type, rather than the associated type, helps avoid this problem.

This is awesome -- thank you!

Thanks for the super quick turn around on this (and for pushing out a new version to crates.io already)!


Rotation size and origin

I have a problem rotating my device with an alert added to the window.
The alert is no longer centered and the background view is no longer the right size.
Same with keyboard opened when having a textField.

Hi @Bejil, Thanks for using FCAlertView and for pointing out this issue. I will look into it and let you know once it's fixed.

I don't know if it covers all cases, but for me it works for rotation with and without keyboard displayed.
[[UIDevice currentDevice] beginGeneratingDeviceOrientationNotifications];
[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(detectOrientation) name:UIDeviceOrientationDidChangeNotification object:nil];
[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(keyboardDidShowNotification:) name:UIKeyboardDidShowNotification object:nil];
[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(keyboardDidHideNotification:) name:UIKeyboardDidHideNotification object:nil];

-(void)detectOrientation{

    CGSize result = [[UIScreen mainScreen] bounds].size;

    CGRect lc_frame = self.frame;
    lc_frame.size=CGSizeMake(result.height,result.width);
    self.frame = lc_frame;

    lc_frame = _alertBackground.frame;
    lc_frame.size=CGSizeMake(result.height,result.width);
    _alertBackground.frame = lc_frame;

    alertViewContents.center=alertViewContents.superview.center;
}

-(void)keyboardDidShowNotification:(NSNotification*)aNotification{

    [UIView animateWithDuration:0.3 delay:0.0 options:UIViewAnimationOptionCurveEaseInOut animations:^{

        CGSize result = [[UIScreen mainScreen] bounds].size;

        CGRect lc_frame = self.frame;
        lc_frame.size=CGSizeMake(result.width,result.height-[[[aNotification userInfo] valueForKey:UIKeyboardFrameEndUserInfoKey] CGRectValue].size.height);
        self.frame = lc_frame;

        lc_frame = _alertBackground.frame;
        lc_frame.size=CGSizeMake(result.width,result.height);
        _alertBackground.frame = lc_frame;

        alertViewContents.center=alertViewContents.superview.center;

    } completion:nil];
}

-(void)keyboardDidHideNotification:(NSNotification*)aNotification{

    [UIView animateWithDuration:0.3 delay:0.0 options:UIViewAnimationOptionCurveEaseInOut animations:^{

	CGSize result = [[UIScreen mainScreen] bounds].size;

	CGRect lc_frame = self.frame;
	lc_frame.size=result;
	self.frame = lc_frame;

	lc_frame = _alertBackground.frame;
	lc_frame.size=result;
	_alertBackground.frame = lc_frame;

	alertViewContents.center=alertViewContents.superview.center;

    } completion:nil];
}

Interesting workaround @Bejil!

Any updates on this feature? Would be a great addition to an otherwise polished and very simple control!

Hi there, this feature is under dev and should be realsed soon!

Hi there, FCAlertView has been updated with some new features. This one is still on the radar for next release as it is a bit more trickier. Please feel free to contribute to the library if you've found a solution for it. Thanks!

i have implement in @kkristof200 given two method but my landscape  and portrait issue not resolved


Warning fixes, and general cleanup

Thank you for this library!  This PR builds on #2, commit 24819c5.  I only wrote a79a8d7.

Change size_t to int to fix signed/unsigned comparison warnings
Removed std::pow call whose value was never used
Added a message at the end of the unit tests to let the first-time reader know that the tests completed successfully
Makefile.mk, clean target: ignore errors in rm.  This way nonexistent files don't trigger an error message.
include/quaternions.h: Don't include boost/mpl/bool.hpp, since the README says Boost is only used for unit testing.  All unit tests pass on my machine even without this header.
The "Portions copyright (c) 2019 D3 Engineering, LLC" message is a condition from my employer (I'm using my work computer).  This is not a request for any change to the licensing --- no worries!

Thank you for considering this PR!

:tada: thank you!

Sorry for the delay :-/ I haven’t worked on that code for years.
Frank

On Dec 10, 2024, at 3:45 PM, Chris White @.***> wrote:
🎉 thank you!
—
Reply to this email directly, view it on GitHub https://github.com/ferd36/quaternions/pull/3#issuecomment-2533233665, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABH64Q7HYDSLZ3SQAP2LRPT2E54IPAVCNFSM6AAAAABTLRW2HOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZTGIZTGNRWGU.
You are receiving this because you modified the open/close state.


Create end_cuttoff for summer_of_love leaderboard in biologist after wich all events not affected to score.

Already took care of it - milestone_3_end in biologist.py.