Release docker image for arm64

The following file has been created and modified:
Added file .github/workflows/ci.yml and modified Dockerfile to build and push the image for both amd64 and arm64 platforms.
Signed-off-by: odidev<EMAIL_ADDRESS>

arm64

@odidev, thanks for the contribution. However, due to company policy, we use Azure DevOps for building docker images:
https://github.com/Azure/azure-cli/blob/6343cb6c50ac482c9e81459357e01e3e38948a9d/azure-pipelines.yml#L251-L263
You may do some research on how to do that in Azure DevOps. I will also do that when time permits.


Missing period at the end of the third sentence.

Affected page
https://www.freecodecamp.org/learn/responsive-web-design/basic-html-and-html5/create-a-bulleted-unordered-list
Your code
Copy and paste the code from the editor that you used in between the back-ticks below:

Expected behavior
There should be a period at the end of the third sentence (Finally ...).
Screenshots

System (please complete the following information):

Device: [e.g. iPhone6, Laptop]
OS: [e.g. iOS 14, Windows 10, Ubuntu 20.4]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]

Additional context
Add any other context about the problem here.

Hello there,
Thank you, for taking the time to open this issue. We can add a period (.) at the end.
Here is the file: https://github.com/freeCodeCamp/freeCodeCamp/blob/main/curriculum/challenges/english/01-responsive-web-design/basic-html-and-html5/create-a-bulleted-unordered-list.md

An issue with the help wanted or first timers only label is open for contribution. The first comprehensive PR created will be reviewed and merged. We typically do not assign issues to anyone other than long-time contributors.
If you would like to contribute, and have not read the contributors docs, please do so here: https://contribute.freecodecamp.org/#/
If you have any issues with contributing, be sure to join us on the contributors channel, or on the contributors sub-forum


Stop removing name from results: prevent vector cannot contain metrics with the same labelset

This issue was previously named as:

Identify highest DPM series via PromQL

Problem / Use-Case
As an Admin/Manager/Operator of a Prometheus instance one use-case is to understand, then manage-down the usage on the instance and the cost of running it. Sometimes there are a few metrics with very high DPM (ie. high frequency of scraping / small scrape-interval), which increase "usage" on the instance, and increase costs. For a multi-tenant project which implements PromQL (such as Mimir) this appears as a DPM overage and increase in the dollar costs for that tenant.
The Admin then needs to identify which metrics are responsible for the high DPM; which are the worst offenders. I've tried to find these with the following query:
topk(10, count_over_time({__name__!=""}[1m]))
Unfortunately this fails with:
execution: vector cannot contain metrics with the same labelset
Boiling this example down a bit, this error is present with the query count_over_time({__name__!=""}[1m]). And it's present for my small instance which only has 4,200 metrics. Google suggests to me a typical workaround for this error is to use label_replace to move the original metric-name into a temporary label. So incorporating this fix I get to this query:
topk(10, count_over_time(label_replace({__name__!=""},"name_label","$1","__name__", "(.+)")[1m:]))
But I've now introduced another problem. (Can you spot it?) I had to switch from [1m] to [1m:] ie. convert to a subquery, to avoid parse error: ranges only allowed for vector selectors. But by switching to a subquery, count_over_time no longer counting the DPM of the underlying metrics/series, but instead counts the subquery-evaluations during the interval in question!
So my question is this:
How can I identify the series that have the highest DPM via PromQL, so I can effectively manage cost and usage on my instance? (Or if it weren't via PromQL, how would we change Prometheus to better support this use-case, and how would operators of multi-tenant Prometheus services such as Mimir support their tenants to achieve the same).
Can we make changes to Prometheus to better support this use-case?
Note: I'm aware that the query I'm trying to run can be very computationally expensive, and may fail if the result-set is too big. But I'm not aware of alternatives for the case I'm describing.
Proposal / Ideas
I believe vector cannot contain metrics with the same labelset happens because Prometheus removes the metric-name when performing count_over_time. It does this for any function which changes the 'dimensions' of the metric. This is an opinionated decision taken by the project in the past - I think the opinion is that 'no metric name is better than the wrong metric name', and metrics names typically do include dimensions (such as …_seconds). But personally (as an instance admin, and as someone who builds features and supports other instance-admins) I've found myself hitting this error message a few times, and found it a barrier to learning and using Prometheus.
Some ideas then, to start some discussion:

Somehow always stop users from hitting the error vector cannot contain metrics with the same labelset, while also retaining the rule that "we mustn't show the wrong metric name".

Retain the metric name, but add a suffix "…DIMS_CHANGED" (either under __name__ or possibly a different label-key, such as original_name)

Somehow always stop users from the hitting the error parse error: ranges only allowed for vector selectors when they have been forced to use label_replace (by the metric-name being removed). ie. Have Prometheus consider label_replace not as a true part of the query which needs to be evaluated, but as a simple rename which can happen somehow differently at the start/end of the querying process...? I lack the words to describe this as I don't know the codebase, but I discussed this with @beorn7 a few months ago, and he thought it was a possibility (although maybe not until Prom v3).

Could we implement the keep_metric_names option that VictoriaMetrics has implemented?

“extend the cardinality API to cover time ranges” (Bryan Boreham’s suggestion - I think for a Mimir implementation)

Thanks, @samjewell. As you might have guessed from our personal communication, this touches two areas I have been thinking a bit about in the past, but never refined my thoughts enough to propose them in a design doc or to the dev summit. Let's take your issue as an opportunity to lay them out in their current rough form:
The first is essentially what you have proposed as your first idea above: Don't drop the name but prefix or suffix it somehow. My thought was to use a prefix that expresses the operation, and also prefix the prefix with a double underscore to mark the internal nature. In your example, the prefix would come out as something like __count_over_time:the_original_metricname.
Playing devil's advocate, here are concerns (with counter arguments in parentheses):

It's kind of verbose and clunky. And those artificial names are visible in the query results. Dashboards that use the bare labelset in the legend will now see the clunky names. (Yeah, that would render the whole idea a breaking change. A feature flag could mitigate that, though.)
Name collisions will still happen if the query is used in a recording rule because the name then changes to the name of the rule for all metrics in the result vector. (That's true, but then just don't use it in a recording rule. Further thought: Maybe  even create a placeholder syntax to fill in the original metric name when naming the output of recording rules.)
How to deal with binary operators? (Vector to vector matching requires unique labelsets anyway. Vector to scalar could be mapped into the proposed system, e.g. __2_times:prometheus_build_info.)

The second thought is about using the timestamp of the evaluation even when the operation is essentially "in place", only affecting a single sample, related to your second idea.  Maybe we would only really need to pick the evaluation timestamp when we are actually aggregating samples with different timestamps. This would be a huge change to the evaluation model and certainly only something to consider for Prometheus v3. I would also not really consider it a good solution to your problem here, but this has come up quite often in different contexts, e.g. timestamp(last_over_time(prometheus_build_info[10m])) or generally to enable range selectors on this whole class of "non-aggregating operations", avoiding sub queries there.
About the ViMe option for that: Adding a separate option and thus mental overhead for everyone reading the docs for such a niche use case would make me really sad. If that first idea of yours (and mine) flew, it would be almost invisible for the naive user. Things would "just work".

Inspired by this issue, I had added an agenda item for the dev-summit many months ago. However, it wasn't discussed so far as other agenda items were deemed more pressing.
This makes it hard to go forward with any of the more invasive approaches. However, as already discussed in the dev-summit agenda item (search for "Revisit metric name removal during PromQL evaluation" in the dev summit document, sorry, no deep linking possible), there are less invasive approaches, and I think we can go forward with one of them in the meantime, to at least have some way of addressing the problem at hand.
The idea I propose here is to only drop the metric name as the very last step, before the result is returned to the outside world. This would not change the outcome of any working query, but it would allow to apply the label_replace trick later. @samjewell's problem could be solved by writing:
topk(10, label_replace(count_over_time({__name__!=""}[1m]), "name_label", "$1", "__name__", "(.+)"))

And in cases, where the ambiguity gets aggregated away anyway, formerly broken queries would just start to work. E.g. to answer the question how many metrics have had more than 10 samples in the last minute:
count(count_over_time({__name__!=""}[1m]) > 10)

The only trick is how to track that a metric name has to be removed before returning the result. But that's an implementation detail we should be able to solve.

The Admin then needs to identify which metrics are responsible for the high DPM; which are the worst offenders. I've tried to find these with the following query:
topk(10, count_over_time({__name__!=""}[1m]))

I've since found a better way to identify the sources of high resolution metrics (high datapoints per minute per series):
Query with sort_desc(count_over_time(scrape_samples_scraped[1m])) to get the data points per minute per series by target. This works a treat in most cases.
There's an exception for metrics which weren't created from a scrape at all, for example those created by recording rules. For those we'd still benefit from the improvement requested here.

I would like to note that the concrete use case that served as an example here is by far not the only one where users run into the dreaded vector cannot contain metrics with the same labelset error. I would still like to see a solution around the "drop names as the last step" idea. (And in Prom 3.x or something, I would like to see a solution around (not) changing the timetamps to the evaluation time.)

The idea I propose here is to only drop the metric name as the very last step, before the result is returned to the outside world.

This doesn't resolve the case when metric names should be returned in the response. For example, the following query could be used for returning resident and virtual memory usage:
max_over_time({__name__=~"process_(resident|virtual)_memory_bytes"}[5m])

Unfortunately, it doesn't work in Prometheus now and will not work after the proposed idea is implemented. The keep_metric_names modifier from VictoriaMetrics elegantly resolves this issue. Note that the keep_metric_names modifier doesn't complicate queries by default. Users may add it if they really want keeping metric names in the results of some PromQL or MetricsQL function.

Unfortunately, it doesn't work in Prometheus now and will not work after the proposed idea is implemented.

If the metric name is dropped as the last thing, you can still use label_replace to move the __name__ label into a normal label.

The keep_metric_names modifier from VictoriaMetrics elegantly resolves this issue.

I don't think it's a good idea. From the dev-summit notes: "Firstly, it exposes everybody to yet another knob they have to think about, while being only relevant for very few (the use case is a niche in a niche). Secondly, it ignores the problem that motivated the name removal in the first place (you are now creating misleading metric names)."

We discussed this topic during the last dev-summit. I try to summarize the results here:
About allowing label_replace to work on range vectors
This would solve most use cases in a seemingly easy way, but at a closer look, it comes with a lot of implications:

As already discussed, it would require overloaded parameter types (label_replace would have to work on both instant vectors and range vectors).
Worse: It would also require variable return types (label_replace acting on an instant vector returns an instant vector, a future label_replace acting on a range vector would need to return a range vector).
And finally, while currently an instant vector returned by a function has the evaluation time as its timestamp, the returned range vector had to retain all its timestamps.

Each of the above is something that we can very well discuss, and it might become a new feature in Prometheus 3.x, maybe being beneficial in many different ways, not just for this one feature request. However, to just solve the feature request at hand, it feels like a PromQL change way too fundamental and invasive.
A more moderate variant would be to create a new function label_replace_range_vector. A function returning a range vector with unmodified timestamps would still be a new concept, but it would be much less invasive change to PromQL. However, this would add a new function for a use case that is in a niche of a niche, but it would add mental overhead for everyone (adds to the documentation, and is leaving many with the question "What is this function even for?"). Same concern as for the ViMe approach above.
About removing the __name__ label as the last step
Unfortunately, the discussion exposed that this would not be a transparent change. Certain "weird" queries would behave differently, so it would be technically a breaking change. Take the following query as an example:
sum by (__name__) (rate({foo="bar"}[5m]))

It is currently equivalent to sum(rate({foo="bar"}[5m])), while it would (ironically) create the vector cannot contain metrics with the same labelset error message with the proposed change. (The sum would be partitioned by the not-yet-removed __name__ label, which would then be removed, creating the labelset collision.) One might argue the query above is nonsensical, and while a human would probably never type such a query, queries are often created via some templating so that the no-op addition of by (__name__) can actually happen in practice, and we really cannot break those queries. (Especially autogenerated ones will wreak havoc in subtle ways.)
More generally, every query dealing with __name__ explicitly has the potential of behaving differently.
In that same line of thought, it should be noted that a __name__ label marked for removal has to be un-marked if it is explicitly overridden later via label_replace. This also allows to create a new meaningful name, e.g.
label_replace(rate({foo="bar"}[5m]), "__name__", "rate5m_of_$1", "__name__", "(.*)")

Overall, I don't think the caveats found kill the approach, but it has to stay behind a feature flag until the next major release after all, which reduces its elegance quite a bit. (We would have initially put it behind a feature flag anyway just to be cautious, but we could have removed the flag eventually if the change had been non-breaking.)
Pending any other new ideas or further evidence of implications, I would propose to give the "late __name__ removal" approach a try, even though it's now a bit more complicated than it appeared initially.

This may be getting out of hand in complexity, but could we detect the

aggregate by (__name__)

function that used to remove __name__

stacking in the AST and rewrite the query to drop the __name__ aggregation? Would that always be compatible? Then we could drop this compatibility shim in 3.0 without having to gate all the good effects of this change.

+1 to this issue. I ran into a similar problem where I was trying to count samples ingested broken down by a label key of interest. Specifically, I have a label aws_account which gets applied to all my time series and helps me determine which time series are being scraped from which aws_account. I then want to count the rate of samples being sent from each account so I can detect if any single account suddenly starts massively increasing the sample rate it sends (e.g., maybe someone misconfigured something).
I was thinking I could do something like sum by(aws_account) (count_over_time( {__name__ =~ ".+" } ) ) but then I ran into the same execution: vector cannot contain metrics with the same labelset issue as above.

I added this to the Prometheus 3 project, as the mild breakage caused by the proposed solution might be nicely dealt with by the major version bump.

@suntala is currently working on this.

Something came up and unfortunately won't be able to work on this anytime soon. Unassigning myself.

@beorn7 feel free to assign this to me, I will give it a try

I have two candidate implementations that I would love to get feedback on before going any further.
Both use the approach suggested by @beorn7 (mark for delete + delayed deletion), but have different tradeoffs.
https://github.com/jcreixell/prometheus/pull/1 uses a special label (__deleted__name__) to automatically propagate deletion information. This is the simplest implementation, but it isn't 100% transparent to the user (if, for example, a user sets a label with key __deleted__name__, the behavior would be undefined). This may be an edge case, but worth considering.
https://github.com/jcreixell/prometheus/pull/2 extends the Series and Sample structs with a boolean flag to track deletion information. While fully transparent to the user, it requires manual propagation of deletion information and introduces higher complexity.
Any feedback more than welcome :bow:

I think people struggle with PromQL already, so anything you can do to make it intuitive (or keep it becoming more complicated) is a good idea, so I'd develop number 2. But as was noted in our sync meeting, keep the flag on series level to avoid overhead.

https://github.com/jcreixell/prometheus/pull/1 uses a special label (deleted__name) to automatically propagate deletion information. This is the simplest implementation, but it isn't 100% transparent to the user (if, for example, a user sets a label with key deleted__name, the behavior would be undefined). This may be an edge case, but worth considering.

Just a comment on this one: label names starting with __ are already reserved for internal use (see https://prometheus.io/docs/concepts/data_model/), so I think it should be technically ok to rely on users not setting that label by themselves (or suffer the consequences if they do so). However, I guess the boolean option is just as fine.
I'm a bit less sure about the approach as a whole though, since it violates (from the user's point of view) the property that PromQL is a set of independent nested expressions that individually evaluate to some value, pass that value to their parent, and then the parent's value only depends on that as the input. Now a user seeing foo(bar) can evaluate bar individually and see its output as something different than foo would see it, breaking clean composition of functions. This is especially visible when using tools like https://demo.promlens.com/?example, where you can click on each sub-expression individually and see its value. In one sub-node, the metric name will already have disappeared from the user's POV, but evaluating a parent of it (even way higher up in the chain) could make it re-appear.
I'm not against adding this behind a feature flag for now, but I would hope we could come up with something that doesn't break the clean functional composition before marking something like it as stable.

(note that this composition is already slightly broken today for things like the timestamp() or absent() functions, but those are exceptions bundled in the form of a specific function, plus they only apply one level deep)

Could we retain the current semantics by considering the boolean field as part of the value? PromLens could show the name as "hidden" if the boolean is set, and then users could clearly follow the flow of the name disappearing and (possibly) getting resurrected again.

Could we retain the current semantics by considering the boolean field as part of the value?

Hmm, how would that work in terms of the PromQL API response? It seems that adding a boolean flag for every series wouldn't be sufficient, as you'd also have to re-add the removed metric names to the response (at least if you want to be able to show them).
The other option would be to just officially consider metric name removal no longer part of a PromQL (sub)expression, but say that it is a separate post-processing step for a query as a whole if the query does something to the value of a time series. That way we have an excuse for not making things transparent in any sub-steps.
Not sure I'm in love with either of these options yet though (not that I need to be, others can overrule my feelings)...

I was just thinking in terms of the internal representation. The API "externalizes" the results, and it would indeed be weird to add extra field there for the hidden name etc. And of course, PromLens communicates with the Prometheus server via the query API, which I blissfully ignored.
If we look at the example from above count(count_over_time({__name__!=""}[1m]) > 10), we have the case that inner parts of the query rightfully would error out if run on its own, e.g. evaluating just count_over_time({__name__!=""}[1m]) would return the error, while it is the whole point of the exercise that the complete query runs fine.
This would be the same if we created a __deleted_name__ special label, as this label would also be removed upon "externalization" through the API (before PromLens sees it).
So I guess one could say that internally, we retain "the property that PromQL is a set of independent nested expressions that individually evaluate to some value, pass that value to their parent, and then the parent's value only depends on that as the input." What we cannot do anymore is to extract those parts out of the engine via the API. (We could introduce a separate UI for that, if we really wanted, I guess…) But we should not forget that we are solving a niche use case here (which is the reason why we don't want a 1st class feature just for controlling the name removal explicitly like ViMe in the first place). So maybe it's all good. We'll see…

we have the case that inner parts of the query rightfully would error out if run on its own

Ah shit, I didn't even think about the error case, but of course 🤯 Yeah, that is kinda bad.

But we should not forget that we are solving a niche use case here (which is the reason why we don't want a 1st class feature just for controlling the name removal explicitly like ViMe in the first place). So maybe it's all good. We'll see…

Are you suggesting that we may not want to do anything at all here (which is my current feeling), or that the use case is so niche that the problem stated above won't hit many users?

I want to try out the "delayed name removal" solution as implemented in https://github.com/prometheus/prometheus/pull/14477 , accepting that you cannot return intermediate results via the API.

Ah ok. As we discussed over lunch I still have my reservations about such a change, but as long as it stays experimental it's ok to try.

It's in as an experimental feature behind --enable-feature=promql-delayed-name-removal.
Let's see how it flies.

@beorn7 am I right that we should bump to Prometheus 3.0, to get this feature?

Note: This will (obviously) be in v3.0.0, but we are also aiming to have a v2.54, so you can try this out without all the other v3 changes.
In both versions, this will still be behind a feature flag.


[FEAT] Structure Proposals

Choosing new dff structure.
Current proposals:

feat/structure-proposal-1

Working branch: #48.


Restore form data with v-model

Switched back to automatic form input restoration.

Possible, but not required - see documentation


add apidiff checking for v1 packages

Example failure:

Actually not ready: following up with @jba in email about some usage concerns. (this is using GOPATH, not actually /tmp/genproto)

Ok, nevermind, this is OK. genproto has a go.mod so the git clone stuff works.


Not able to install 16.2.8 from gitlab runner

Hey folks I'm not able to install castlabs electron version 16.2.8. Looks like it generates wrong download url, could you please point out how to specify the correct download URL?
here is error
`><EMAIL_ADDRESS>postinstall /builds/all/pix/legacy/pix-app/p3/lumiere/node_modules/electron

node install.js
HTTPError: Response code 404 (Not Found) for https://github.com/castlabs/electron-releases/releases/download/v16.2.8/electron-v16.2.8-linux-x64.zip
at EventEmitter. (/builds/all/pix/legacy/pix-app/p3/lumiere/node_modules/got/source/as-stream.js:35:24)
at EventEmitter.emit (events.js:314:20)`

and here is package.json fragment
  "electron": "https://github.com/castlabs/electron-releases#v16.2.8+wvcus",

Thanks @khwaaj changing node version it helped, however now electron-packager doesn't work with 16 version of electron
Error: rcedit.exe failed with exit code 1. wine: '/root/.wine' is a 32-bit installation

Looks like you got a 64-bit rcedit.exe and are trying to run it with 32-bit Wine? You probably need to update the Wine installation somehow, but this is not something I have a great deal of experience with. I recommend Googling it 🙂

Ok issue solved, for those who are interested:
Lastest versions of castlab electrons 16+ only installed properly with node 16 as mentioned in here
My last question is related to electron-packager usage in gitlab runner with electronuserland/builder:wine docker image, so fix could be found here  in nutshell
# Removes the original 32-bit wine prefix from the generated image
rm -rf /root/.wine
# Creates a new 64-bit one
winecfg

latter will reinitialize wine and successfully package electron app.
Anyway @khwaaj Thanks a lot!


ethernet: Add 2.5G and 5G Ethernet defines

Add required defines for 2.5G and 5G ethernet standards.
Will be used in conjunction with the xgmac driver.

Thanks for the PR! Please take a look at our commit message guidelines to find out how to format your commit messages, and at our contribution workflow to understand how to update your Pull Request.

@jukkar @carlescufi Addressed your feedback..

ping @go2sh

@jukkar Done. Sorry for the delay. Some customer topics put away from working on zephyr.


Allow using custom components in operations

What would you like?
Vitepress has the ability to define custom components which can later on be used across the documentation.
It would be nice if we could use such custom components in the generated api operations.
Why is this needed?
No response
How could it be implemented?
No response
Other information
No response

Hi @ashercoren! I don't understand at all what you specifically mean.

If you want to declare an CustomTryButton for example, and that the project uses it instead of the own library OATryButton, it may be possible, maybe just re-declaring Vue Components, but you will have to implement it as expected (just change html/css). I'd avoid this.

If you want to include some custom Vue components inside the rendered OpenAPI Spec. In this case, you can do this by using Custom Slots. You can even replace entire sections and implement them by yourself.

For example: https://stackblitz.com/edit/enzonotario-vitepress-openapi-starter-hrwwfe?file=docs%2Foperations%2F[operationId].md
These slots are not documented yet, you can see available slots in OAPath component. PRs are welcome!
Also, you can use any Markdown/Vue component before/after rendering the OpenAPI (via OAOperation or OASpec), as you can see in ArgentinaDatos. This page includes a Part File that contains Markdown and Vue components

Thanks @enzonotario. I'll look into the idea of using slots.

Nice! I'll close this issue. Feel free to re-open if needed, or to open other Issues.
Thanks!


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/911 is merged into live branch.
Auto archive content to https://github.com/huangmin-ms/docs-archive-test-target.git

Docs Build status updates of commit 9328865:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-RuningBuildFailed] Some unexpected errors happened when running build, please open a ticket in https://aka.ms/SiteHelp and include the error report for our team to troubleshoot

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Race condition in AbstractBlockingExtension

There appears to be a scenario when running with Weld SE as the backing CDI implementation (which installs its own shutdown hooks) that can result in a race condition.
I'm observing in a project that uses the microbean-jersey-container-grizzly2-http-cdi-extension project that the container comes up, the Jersey container inside it comes up, the Jersey container shuts down, the container shuts down and then blocks in the shutdown process.  I'm not sure where the problem lies but solving it will probably involve the fireBlockingEvent method.
The workaround is to try starting the container again; it will work eventually.
My hazy sense is that the Weld shutdown hook is firing, thus bringing down the container, but the AbstractExtension manages to get off its fireBlockingEvent call, which then hangs.  The result would be, if I'm right, a container that is shut down (in terms of its state), but hanging waiting for the blocking event to be processed.

Wondering if the issue is actually with HttpServerStartingExtension.  Just because that startedHttpServers field is "full" doesn't mean that every HttpServer in it is in the "started" state.

With some debugging statements, I can see that the exit is happening as a result of the container closing.  In other words, it appears that the race condition might very well be between SeContainer.close() and the fireAsync mechanism of CDI itself.  We need to block the main thread, I think—yes, the main thread—via the CountDownLatch at the tail end of fireBlockingEvent until the event receiver acknowledges receipt of the event on the separate thread.


Merge pull request #1 from ccpgames/master

Merge pull request #244 from cppctamber/master

oops :3


[Dash] Cannot create docset quicklink

Extension
https://www.raycast.com/RSO/dash
Description
Error:
Error: No enabled command 'create-quicklink' found

Steps To Reproduce

Try to add quicklink with Dash with keyword py

Current Behaviour
Errors

Expected Behaviour
No response

Can you try this again after making sure you're on the latest version of Raycast? There was a bug in yesterdays version that broke the Create Quicklink command for some users!

also works for me on the latest version of Raycast

Have the same problem. By the way, what does keyword mean? It is the word I can customize or the doc name determined by dash

Found a (slower) way to achieve this, but at least it does:
Add quick link: raycast://extensions/RSO/dash/docset?arguments=%7B%22docset%22%3A%22%22%7D
replace  by the keyword you set in Dash, for example I use py3 for python3 in dash

the keyword is here:

@fishiu what version of Raycast are you on? You can find the version in the preferences about panel.

@fishiu what version of Raycast are you on? You can find the version in the preferences about panel.

I just found that I can create quicklink successfully now.. Have no idea what was happening. Thank you anyway for this wonderful extension and your effort for maintaining it.


Create release-guide.md

This PR documents release process for releasing packages to DC/OS Universe.

@triclambert, @mohitsoni, @mgummelt.  If this is moving to the wiki, we should close this PR.

Moved this to the wiki so closing.


After minting, user does not get redirect to NFT and Error when trying to massmint on RMRK2

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Context

[x] Closes #6526

Now it redirects when creating a NFT using the classic UI
Redirect inside massmint worked for me

[x] Closes #6508

I also fixed this , since I couldn't mint tokens via massmint

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[ ] My fix has changed something on UI;

Copilot Summary

🤖 Generated by Copilot at d0045a1
This pull request enables minting NFTs without listing them for sale, and improves the compatibility and validity of the arguments for the batched minting transactions. It refactors the CreateToken component and the transactionMintRmrk composable.

🤖 Generated by Copilot at d0045a1

Sing, O Muse, of the crafty code that the heroes wrought
To mint new tokens of their art, with skill and cunning fraught
They filtered out the false and wrapped the args in system.remark
To execute a batch of transactions, swift and smooth as a shark

RMRK2
Classic minting redirection - ✔
Massmint redirection - ✔
Massmint process: ✔
https://kusama.subscan.io/tx/0x89e4c54c91b3704f553ac4900153787080a4f221374ec4f9245869a01d49fd02
massminted NFTs: https://deploy-preview-6570--koda-canary.netlify.app/ksm/collection/7EA1DCF47E98A25067-RPG
RMRK1
Classic minting redirection - ✔
Simple minting redirection - ✔
Massmint redirection - ✔
Tester account:
https://kusama.subscan.io/account/FSMdmCLv5gFZ87YerB3M8ZSQ58BGHdSnreC4J6znWpqPQK9

pay 70 usd

😍 Perfect, I’ve sent the payout
💵 $70 @ 4.98 USD/DOT ~ 14.056 $DOT
🧗 16faLfsywwNATaEfbH2ah75dn6ZmctQWpMS5G4KFhbmj5hnD
🔗 0x89b242924559dc53209c2fdf872b0ff4b1ee0a9b3edf2e5626cac82ae86097a7
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Some improvements and new/missing features

Improvements:

moved to Go Modules
replaces the custom chef API code with go-chef/chef
moved testing only code to the unit test

Features:

implemented role policies
implemented tag policies
implemented environment policies
added support for metadata mapping

implemented role policies
implemented tag policies
implemented environment policies

I had implemented these originally, but after discussion with some Chef folks it turns out you can't really use these securely because the chef client can change them arbitrarily.
I will take a look at the module conversion and metadata mapping.

I had implemented these originally, but after discussion with some Chef folks it turns out you can't really use these securely because the chef client can change them arbitrarily.

In theory, this is correct. I'm using a lightwight proxy, written in go, in front of the chef server API to disallow changes to the run_list at the moment.
I think there should be a big, fat, warning in the docs about this.
If i find time, i will make the proxy releasable.


Adds common C headers and bindgen support

[x] add environment
[x] add bindgen build
[x] add documentation
[ ] manually add padding to structs
[ ] add static size checks in C headers (req. C11)
[ ] add CI

Do we want a top level makefile or is this just going to be included as a submodule in other repos so not necessary?

I'll add one, why not

@petersonev I think I fixed most of your point, though I suspect there might be some more tweaks to the rust directory structure. Should be good to merge soon.


Make build process work with older node versions.

@darkwing stumbled over String::startsWith in #25 and there might be other references.

Please assign to me as I have a PR in


[FEATURE REQUEST] Common ORM queries

Is your feature request related to a problem? Please describe.
Consider to make automatic code generation for such ORM queries as:

Select all
Select by PK
Delete by PK
Update by PK

Describe the solution you'd like and provide pseudocode examples if you can
Do it in same manner as main functionality is done (use of text/template).
E.g. Select:
const tmpSelect = `
func (dbConn *{{ .DataBase }}) Select{{ .StructName }}() ([]*{{ .StructName }}, error) {
	ctx := context.Background()
	model := []*{{ .StructName }}{}
	err := dbConn.NewSelect().
		Model(&model).
		Scan(ctx)
	return model, err
}`

Additional context
Prepare new branch(-es) and do some testing stuff in it

Base SELECT queries aka select * from t are done


[vertical tabs]: component research

There is a request by design teams to create a list item with custom content.
Some of the use cases seem problematic from UX and accessibility points of view.
In order to reach the correct decision there are a few components that need to be researched:

Vertical tabs
List item
List box

Right now the component in the progress of research is vertical tabs.

Vertical Tabs research is here:
https://www.figma.com/file/QG5hvuw5qsfS0XYMVJ6V3L/Vivid-UI-Kit---Exploration?node-id=3945%3A78517

As I continued my research (finished writing also the list item research in the same link 👆),
I began going over the variants of the components that exist in the UI Kit).
I went over the list item only in the meantime, this is the branch:
https://www.figma.com/file/r8OYLPmRmDqfLKt6KHdJDB/branch/HGrZrrVhSiRhkwbVRONmA9/Vivid-UI-Kit---2.0?node-id=1968%3A567
I put a red background in the "List - item" section under the variants that are not list items at all by definition (based on my research), and need to go. I put the yellow background under the variants that I am not sure about. They actually didn't appear in any other design system that I looked in, but I wonder maybe we will still have use for them.
@yinonov what do you think?

as discussed, we need to focus on each individual component and role. start by defining tabs (horizontal / vertical), menu items, options.
what we're calling "list-item" is actually an abstract pattern of what the mentioned components extract anatomy from.
each component might extract a different subset as some components like option should have more than a single line text and a decorative icon
we need to give that "list-item" a more suitable name for a pattern as list-item is a reserved role within the web context.

I think that I will divide this into categories, and treat each of them as a separate component.
It kind of is now, but still needs some attention.

@yinonov
After doing some research I found that
The variants that exist in vertical tabs are:

Tab with primary text only
Tab with primary text + icon
Tab with primary text + text badge
Tab with primary text + notification - indicator only
Tab with primary text + number of notifications - number badge
Tab with primary text + Alert notification (high, moderate & low severity)

Also were variants that included more that two content components, which are:

Tab with primary text + icon + text badge
Tab with primary text + icon + number of notifications - number badge
Tab with primary text + icon + Alert notification (high, moderate & low severity)

(!) Not even once I saw a vertical tab that included:

Primary + secondary text
Checkbox
Radio button
More actions icons
I believe that this is something we should take into consideration

The variants that exist in list item (option) are:

Primary text
Bullet (ul) + primary text
Number (ol) + primary text
Primary + secondary text (Vertical & Horizontal view)
Primary text + choice icon (V)
Primary text + radio button
Primary text + checkbox
Primary text + image (information icon)

The variants that exist in menu item (option) are:

Primary text (horizontal + vertical)
Primary text + submenu action (dropdown arrow)
Primary text + badge
Primary text + subheaders (secondary text)
Primary text + icon
Primary text  + icon + choice icon (V)
Primary text + status notification icon (high, moderate & low severity)
Primary + Secondary text

In our UI Kit 2.0 there are list item variants that I think are not needed based on my research:

List item with primary text, radio button/checkbox + action (dropdown arrow/more actions icon)
List item with primary & secondary text, radio button/checkbox + action (dropdown arrow/more actions icon)

Most of the variants do need some attention and rearranging,  but also as I written in the issue 703:
https://github.com/Vonage/vivid-3/issues/703
I believe there is need to create a new slotted list component

can we have a visual representation along side this?

The research is in this link:
https://www.figma.com/file/QG5hvuw5qsfS0XYMVJ6V3L/Vivid-UI-Kit---Exploration?node-id=3945%3A78518

The new component is called tile,
and its variant are here in this link (in the meantime):
https://www.figma.com/file/QG5hvuw5qsfS0XYMVJ6V3L/Vivid-UI-Kit---Exploration?node-id=4129%3A55647

@yinonov
In the meantime the only additional request to the new components was to create an "option-item" with two lines, that also in some situations can feature a "check" icon like in this use case:

Screen reader read it this way:

First line of text
Second line of text
checkmark (was pronounced as "checked")

Also a component like that appears in multiple design systems,
these are a few examples:
https://m2.material.io/components/lists#interactive-demo
https://ant.design/components/list
https://getbootstrap.com/docs/4.3/components/list-group/#custom-content
https://developer.microsoft.com/en-us/fluentui#/controls/web/list
Based on this information I don't see a problem to provide this option item variant.


Customers editing their profile causes the company name to be deleted

PHP Version: 8.+   | Shopware Version: <IP_ADDRESS>  | Affected area / extension: Platform(Default)

Expected behaviour:
The profile change even just Mr -> Mrs. should not have any side effects!
Actual behaviour:
The profile change e.g. Mr -> Mrs. immediately deletes the company name for the customer in question. This does't make any sense...
How to reproduce:
Create a customer with a company name set. Log in as that customer and change the salutation or name.

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-39727
[created from NEXT-39727, comment 515078]

[public] We have not been able to reproduce this behaviour in the latest version of Shopware with the information available. Please create a new ticket with more information if you think this is a general behaviour. Otherwise, please contact our support team or visit the forum.
[created from NEXT-39727, comment 515494]


Added typescript typings

Closes #94

Thanks a lot @slavikdenis . Merging it!

Released in v2.10.8


Java SDK publish failure

What happened?
Alpha release encountered a failure to push Java SDK to Maven Central:
* What went wrong:
Execution failed for task ':releaseSonatypeStagingRepository'.
> Staging repository is not in desired state [released, not_found]:
StagingRepository(id=compulumi-5488, state=closed, transitioning=false). It is unexpected.
Please checkNexus logs using its web interface - it can be caused by validation rules violation. If not, please report it to https://github.com/gradle-nexus/publish-plugin/issues/ with '--info' logs

Expected Behavior
Java SDK publishes successfully.
Steps to reproduce
N/A
Output of pulumi about
N/A
Additional context
This has known to be flaky before may retry.
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Possibly an instance of https://github.com/pulumi/pulumi-java/issues/830

Attempt 2:
> Staging repository is not in desired state [released, not_found]: StagingRepository(id=compulumi-5597, state=closed, transitioning=false). It is unexpected. Please checkNexus logs using its web interface - it can be caused by validation rules violation. If not, please report it to https://github.com/gradle-nexus/publish-plugin/issues/ with '--info' logs

https://central.sonatype.com/artifact/com.pulumi/aws/6.0.2-alpha.2+9b14ba69 gives 404 not found.

ok, mvn compile can handle this dependency:
        <dependency>
            <groupId>com.pulumi</groupId>
            <artifactId>aws</artifactId>
            <version>6.0.2-alpha.2+9b14ba69</version>
        </dependency>

I think this version actually got published to Maven Central in spite of the CI marking it as failing.
I will count it as another instance of https://github.com/pulumi/pulumi-java/issues/830 and it should not affect upcoming V6 release. Closing.


Is unlearned model weights available?

Hi,
I'm interested to perform some downstream tasks on unlearned models. Will the unlearned model weights be released?
Thanks

Thanks for your interest in our work! Our full code is released. Since our methods don't require too much computational resources, we don't have a plan to release the unlearned model weights. I do have a backup of the unlearned model weights for the main experiment, if you have a special need for those model's weights, I could send it to you.

Hi there,
Thanks for your great work to community!
Can you send these models' checkpoints to me? My email is<EMAIL_ADDRESS>looking forward to your reply!

Hello @tbozhong. The total storage of all checkpoints is about 238GB. It is difficult to download those from a remote server and upload them to one cloud storage system. Could you specify which checkpoints you need? Then I could upload them to OneDrive manually and share them with you.

Thanks for your reply!
Could you upload the checkpoints according to cais/Zephyr_RMU to Hugging Face? It will be convenient for us.
Thank you for considering this request!


Install latest version of OpenSSL on Debian

How to install latest version of OPenSSL on Debian based linux ?
Please tell the steps followed

The same as on any Unix, I guess?
However, do not replace the openssl that is installed by the system.  Simply place your OpenSSL elsewhere.
The default configuration installs it under /usr/local, which is fine, that's out of the way of system installations.
Other than that, the quick build and installation guide should get you started.

You might get better help if you tell us what you've tried and what happened


flag to fail deployment if apps readiness check timeout without success

it seems there is a bug right now on trying to update app on Fermyon Cloud. I am adding a test for it and it also seems like spin cloud deploy would exit with code 0 even if readiness check timeouts.
what do you think about adding a flag to spin cloud deploy, which will make the spin command exit with error code if readiness is not established. it will be useful in CI/CD scenarios as well.

I definitely see the value for sending some sort of signal to the user that the app readiness check failed.  A non-zero exit code is one way, an error message another.  The former would probably be the friendliest to automation.

We already have a message if the app doesn't come ready.  Some nastiness with exit codes (from a previous look at an unrelated issue):

The default way of setting a non-zero exit code is to return Err(...) from main which always prints "Error: ..." _even if it's really only a heads up
The override way of setting a non-zero exit code is to do your own implementation of std::process::Termination, and this could have knock-on impacts to other parts of the codebase (because we return the same type from all the commands), so might turn out to be more work than expected

These are not a blocker to doing an exit code, but just for awareness.


Use database token on shell and inspect commands

This fixes 401 response that happens when a user logs in on a second device.

looks good!


CP-21834: NuGet package 3.6.61119.7 missing WP7,WP7.1?

From unknown CodePlex user on Sunday, 27 November 2011 23:45:59
NuGet package seems to only contain .net4 libraries.  I can't get it to work with SL 4, WP7 or WP7.1:

From the description, it sound like this should be supported.

Successfully installed 'QuickGraph 3.6.61119.7'.
Successfully uninstalled 'QuickGraph 3.6.61119.7'.
Install failed. Rolling back...
Could not install package 'QuickGraph 3.6.61119.7'. You are trying to install this package into a project that targets 'Silverlight,Version=v4.0,Profile=WindowsPhone71', but the package does not contain any assembly references that are compatible with that framework. For more information, contact the package author.

Form unknown CodePlex user on Wednesday, 21 December 2011 15:59:50
The net40 dlls in the latest package also refer to System.Core <IP_ADDRESS>, which is Silverlight.  This is breaking for us on machines without Silverlight installed.


"setDashboardTime" disables refresh interval

"setDashboardTime" was the last "case" inside switch statement. When you added "setRefreshInterval" after it you forgot to put "break" statement and execution flow continues to "setRefreshInterval" and refresh interval affected.
Another issue that reproduces itself about 50% of the time: refresh interval does not appear in globalState when you build URL for Kibana and therefore it being reset to 0.

Hi,
I don't understand the second part of the issue, can you explain?

The issue was in 6.3 and we switched to version 6.4 since in 6.3 it didn't work as expected. In 6.4.2 it works perfect.
With regard to the issues in 6.3.

Setting time interval resets refresh to 0.
Setting refresh time works 50% of time. Once works, once no. Pattern is: 1010101...
Similar issue with set interval but pattern is<PHONE_NUMBER>... (1 means that operation succeded and 0 the time interval/refresh didn't change)
We tried to implement workarounds but finally decided to switch to the version where everything works.


cannot include multiple umd build when using secondary entry points.

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Should work
What is the current behavior?
I get the following error:
Template parse errors:
More than one component matched on this element.
Make sure that only one component's selector can match a given element.
Conflicting components: MatFormField,MatFormField

What are the steps to reproduce?
https://stackblitz.com/edit/angular-material2-issue-uhapma?file=app%2Fapp.module.ts
just import input and select modules and include form-field in component template:
...
import { MatInputModule } from '@angular/material/input';
import { MatSelectModule } from '@angular/material/select';

@NgModule({
  imports: [
    MatInputModule,
    MatSelectModule,
  ]
})
export class AppModule {}

@Component({
  selector: 'material-app',
  template: `
    <mat-form-field class="example-full-width">
      <input matInput placeholder="Favorite food" value="Sushi">
    </mat-form-field>
  `
})
export class AppComponent {
  version = VERSION;
}

import { MatInputModule, MatSelectModule } from '@angular/material'; doesn't break.

Hello,
I am facing the same issue when using material 2 in angular 5.2.X , and couldn't find the solution, what I need to do to resolve this issue,.
Thanks


Multiple Scopes are not working

Scopes must be separated by + (bot+identify)

Honestly, I should probably just sunset this and recommend people use the built-in URL generator.


Input box disappears

Challenge http://www.freecodecamp.com/challenges/waypoint-create-a-form-element has an issue.

input box disappears even though challenge action is accepted.

Nevermind, box appears now when I did the waypoint again.


fix docker config folder volume

Fixes #84
Fixes #128
Mount the entire .docker folder instead the config.json file.
These fixes the error below.
read /kaniko/.docker/config.json: is a directory

Tested on the same repository where I had the initial error using my fixed action: https://github.com/marketplace/actions/kaniko-action-fork

Thank you for the contribution!


select_all() or race_all()?

The futures package has a select_all() function that races a collection of futures and returns the first resolved future's index without dropping the rest.
Is there a way to do this in async-std? I'd rather not pull in the entirety of futures just for one function call 😅 I see there's a .race() method somewhere but it's not immediately clear on how to use it for something like this, or if it will drop the "losing" future.
Thanks for any information!

Thanks for asking; that's a good question! We're working on new versions of these operations in the futures-concurrency crate, with an eye of creating primitives which we put up for inclusion in the stdlib as well. Once we're happy with the design the plan is to re-export them from async-std. Until then I can recommend using those operations directly from the futures-concurrency crate.
I hope that answers your question!

So to be clear, futures-concurrency has candidate members that will ultimately be exposed directly from async-std in the future, right?

That's the goal, indeed.

Cool! Thanks :)


test only awkward against numba 0.48

This was provided to check that awkward did work fine with Numba 0.48


Katafygio logo

Copyright details:
This image or media file contains material based on a work of a National Park Service employee, created as part of that person's official duties. As a work of the U.S. federal government, such work is in the public domain in the United States. See the NPS website and NPS copyright policy for more information.
References:
https://www.nps.gov/aboutus/disclaimer.htm
https://thenounproject.com/term/sleeping-shelter/241/
https://commons.wikimedia.org/wiki/File:Pictograms-nps-accommodations-sleeping_shelter-2.svg
https://commons.wikimedia.org/wiki/File:Pictograms-nps-accommodations-sleeping_shelter.svg

Coverage remained the same at 90.554% when pulling 16203ad5038939ed31cf7a21b1a3fc28588c5af0 on logo into a84479c4df401aa169344a40074991133932765c on master.


[Bug] [Source Http] HTTP Source read data  "params" setting is invalid

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
接口传入时间参数，去数据库查询日期大于参数的数据返回，参数类型String。
脚本运行后seatunnel发送的查询请求没有参数信息，导致查不到数据，且一直重试。
The time parameter is passed in to the interface, and the data returned by querying the database with a date greater than the parameter, the parameter type is String. After the script runs, the query request sent by seatunnel has no parameter information, so the data cannot be found, and it keeps retrying
SeaTunnel Version
2.3.1
SeaTunnel Config
env {
  execution.parallelism = 1
  job.mode = "STREAMING"
}

source {
  Http {
    result_table_name = "mq"
    url = "http://<IP_ADDRESS>:9000/test/"
    method = "POST"
    format = "json"
    params = {sync_time="2023-03-23"}
    poll_interval_ms = 3000
    retry_backoff_multiplier_ms = 1000
    retry_backoff_max_ms = 10000
    json_field = {
      id_card = "$.data[*].idCard"
      json_data = "$.data[*]"
    }
    schema = {
      fields{
        id_card = string
        json_data = string
      }
    }
  }
}

sink {
  Clickhouse {
    source_table_name = "mq"
    host = "xx:8123"
    username = "xxx"
    password = "xxx"
    database = "db2"
    table = "xx"

    # cdc options
    primary_key = "id_card"
    support_upsert = true
    allow_experimental_lightweight_delete = true
  }
}

Running Command
seatunnel.sh --config soctest.conf -e local

Error Exception
2023-04-04 14:44:31,116 ERROR org.apache.seatunnel.connectors.seatunnel.http.source.HttpSourceReader - http client execute exception, http response status code:[422], content:[{"detail":[{"loc":["query","sync_time"],"msg":"field required","type":"value_error.missing"}]}]
2023-04-04 14:44:31,118 ERROR org.apache.seatunnel.connectors.seatunnel.http.source.HttpSourceReader - http client execute exception, http response status code:[422], content:[{"detail":[{"loc":["query","sync_time"],"msg":"field required","type":"value_error.missing"}]}]
2023-04-04 14:44:31,121 ERROR org.apache.seatunnel.connectors.seatunnel.http.source.HttpSourceReader - http client execute exception, http response status code:[422], content:[{"detail":[{"loc":["query","sync_time"],"msg":"field required","type":"value_error.missing"}]}]
2023-04-04 14:44:31,123 ERROR org.apache.seatunnel.connectors.seatunnel.http.source.HttpSourceReader - http client execute exception, http response status code:[422], content:[{"detail":[{"loc":["query","sync_time"],"msg":"field required","type":"value_error.missing"}]}]
2023-04-04 14:44:31,126 ERROR org.apache.seatunnel.connectors.seatunnel.http.source.HttpSourceReader - http client execute exception, http response status code:[422], content:[{"detail":[{"loc":["query","sync_time"],"msg":"field required","type":"value_error.missing"}]}]
2023-04-04 14:44:31,129 ERROR org.apache.seatunnel.connectors.seatunnel.http.source.HttpSourceReader - http client execute exception, http response status code:[422], content:[{"detail":[{"loc":["query","sync_time"],"msg":"field required","type":"value_error.missing"}]}]
2023-04-04 14:44:31,132 ERROR org.apache.seatunnel.connectors.seatunnel.http.source.HttpSourceReader - http client execute exception, http response status code:[422], content:[{"detail":[{"loc":["query","sync_time"],"msg":"field required","type":"value_error.missing"}]}]

Flink or Spark Version

Java or Scala Version
jdk 1.8
Screenshots
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

please assign to me; thx。

+1


Delete dead/pointless code

In the process of working on some other things, I noticed some dead ST2 code.
Let's drop it. :)

drop pointless header in an otherwise empty __init__.py (keep empty unless there is code)

Delete unused fixture file st2auth/tests/fixtures/htpasswd_test
unused since 8593936b2222e3b86a2999dec440bd752659f5ca (commit from 2015)

drop obsolete mock_runner test fixture
mock_runner was used by st2common/tests/unit/test_util_loader.py
added in 52c8ff91d330e95a4f214be01acf72bc1fbc9fbb
removed in 4c27b4facc05e146730732421a44aa5e879779fc

This skip duplicate jobs thing is acting weird.


Sidecar implementation

Hi,
do you plan on implementing sidecar configuration and collectors?
API endpoints:
/sidecar
/sidecars
/sidecars/configurations
/sidecar/collectors
/sidecar/configurations

[ ] /sidecar/collectors #14

I have released v0.2.0, which supports the Sidecar Collector.
https://terraform-provider-graylog.github.io/#/resources/collector

Sorry but I'll rename graylog_collector to graylog_sidecar_collector.
#16

I have released v0.3.0, which renames graylog_collector to graylog_sidecar_collector and supports the Sidecar Configuration.
https://terraform-provider-graylog.github.io/#/resources/sidecar_configuration

I close this issue because Sidecar Collector and Sidecar Configuration have been supported.
If you have any problems, please comment or create new issues.
Thanks.

Hi sorry for the delayed answer,
I have tried it and it works perfectly for collector and configuration creation/import
one more endpoint that would be awesome to add is /sidecars/{sidecarId}
so that it would be possible to assign collector and configuration to a sidecar
API example:
"assignments": [
    {
      "collector_id": "5ddd3a4dc9e77d0012150861",
      "configuration_id": "5ebd333c48e0fb0012a68280"
    }
  ]

📝

https://docs.graylog.org/en/3.2/pages/sidecar.html
https://docs.graylog.org/en/3.2/pages/configuration/rest_api.html#creating-and-using-access-token

How to setup sidecar with Docker
# docker-compose.yaml
  sidecar:
    image: debian:10.4
    networks:
    - graylog
    tty: true
    stdin_open: true
    command: ["tail", "-f", "/dev/null"]

apt-get update
apt-get install wget
wget https://packages.graylog2.org/repo/packages/graylog-sidecar-repository_1-2_all.deb
dpkg -i graylog-sidecar-repository_1-2_all.deb
apt-get update
apt-get install graylog-sidecar
apt-get install vim

# server_url: http://graylog:9000/api/
# server_api_token: generate api token
vim /etc/graylog/sidecar/sidecar.yml  # update

graylog-sidecar  # Run sidecar

Assign configurations to sidecars
PUT /sidecars/configurations
{
  "nodes": [
    {
      "node_id": "10517347-8fad-4f25-835f-95d1943fa338",
      "assignments": [
        {
          "collector_id": "5ec661032ab79c0012267d29",
          "configuration_id": "5ec709642ab79c001226edf9"
        }
      ]
    }
  ]
}

response status code: 202
Get sidecar and assignments

#23

In my understanding, we have to manage all nodes's assignments in one Terraform resource due to the Graylog API's limitation.
There is no API to manage only one's Graylog Sidecar's assignments.
We have to use the API PUT /sidecars/configurations to manage Sidecar's assignments, and we can't specify Sidecar's ID.
Example
resource "graylog_sidecar" "test" {

}

Document: https://github.com/terraform-provider-graylog/terraform-provider-graylog.github.io/pull/10

@roiterorh
I have released v0.4.0-0 as pre release version.
About document, please see

https://github.com/terraform-provider-graylog/terraform-provider-graylog.github.io/pull/10
Data Source: sidecar
Resource: sidecars

These document isn't published to https://terraform-provider-graylog.github.io/ yet because these resources are pre release.
Please check these resources work well.
If there is no problem, I'll release v0.4.0 and the document.
Thank you.

I have released v0.4.0 and document, so I close this issue.


Spelling error in the title

I believe 'VMware fisaster' is supposed to be read as 'VMware disaster'?
D&F are near each other on a standard keyboad..

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

ID: 2cf74fea-62eb-f55e-df86-757d5a50e4b7
Version Independent ID: dda01b0f-5d24-3501-28e8-357bb8412875
Content: Overview of multi-tenant support for VMware VM disaster recovery to Azure (CSP) using Azure Site Recovery
Content Source: articles/site-recovery/vmware-azure-multi-tenant-overview.md
Service: site-recovery
GitHub Login: @mayurigupta13
Microsoft Alias: mayg

@Cuciu, We've made the corrections and the changes are reflecting in the article. Thanks once again!
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


【RCINT-3797】Set area when try to send SMS to 7-digit number before setting area code

Coverage decreased (-0.004%) to 1.201% when pulling 93c9c5fcea70ec526a16d23f9c7e38e9e5c14425 on caffffe:bugfix-setareacode into 10abf64f997ec400c8f5c638874e55c20dd84db8 on ringcentral:master.


[Layout] An unnecessary gap between the drawer and the content in landscape

Describe the bug

There will be an unnecessary gap between the drawer and the content as much as the width of the navigation bar.
Occurs under the following conditions:

3 buttons mode
A navigation bar appears on the left
large screen device (galaxy z flip3  etc.)

Expected behavior
Remove unnecessary gaps.
Screenshots

1
2

Maybe i can fix it

It's looks natural. But It's padding is probably for navigation bar, right?
Good catch!

Thanks! Assigned!


[bugfix] Fix parsing of completion time of Slurm jobs

Fixes #1349

Codecov Report

Merging #1359 into master will decrease coverage by 0.03%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master    #1359      +/-   ##
==========================================
- Coverage   91.65%   91.62%   -0.04%
==========================================
  Files          83       83
  Lines       12599    12604       +5
==========================================
  Hits        11548    11548
- Misses       1051     1056       +5

Impacted Files
Coverage Δ

reframe/core/schedulers/slurm.py
55.29% <0.00%> (-0.83%)
:arrow_down:

Continue to review full report at Codecov.

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


[SPARK-15037][SQL][MLLIB] Part2: Use SparkSession instead of SQLContext in Python TestSuites

What changes were proposed in this pull request?
Use SparkSession instead of SQLContext in Python TestSuites
How was this patch tested?
Existing tests

Test build #58330 has started for PR 13044 at commit d7361d8.

Test build #58330 has finished for PR 13044 at commit d7361d8.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58330/
Test FAILed.

Merged build finished. Test FAILed.

Test build #58354 has started for PR 13044 at commit 7101849.

Test build #58354 has finished for PR 13044 at commit 7101849.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class SparkSessionTestCase(PySparkTestCase):
class FeatureTests(SparkSessionTestCase):
class CrossValidatorTests(SparkSessionTestCase):
class TrainValidationSplitTests(SparkSessionTestCase):
class PersistenceTest(SparkSessionTestCase):
class LDATest(SparkSessionTestCase):
class TrainingSummaryTest(SparkSessionTestCase):
class OneVsRestTests(SparkSessionTestCase):
class HashingTFTest(SparkSessionTestCase):
class ALSTest(SparkSessionTestCase):

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58354/
Test FAILed.

Merged build finished. Test FAILed.

Test build #58355 has started for PR 13044 at commit a776c2e.

Test build #58355 has finished for PR 13044 at commit a776c2e.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58355/
Test FAILed.

Test build #58358 has started for PR 13044 at commit 6905326.

Test build #58358 has finished for PR 13044 at commit 6905326.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58358/
Test FAILed.

Merged build finished. Test FAILed.

Test build #58359 has started for PR 13044 at commit 0dbb2a1.

Test build #58359 has finished for PR 13044 at commit 0dbb2a1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58359/
Test PASSed.

Test build #58366 has started for PR 13044 at commit d3d4fda.

Test build #58366 has finished for PR 13044 at commit d3d4fda.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/58366/
Test PASSed.

cc: @andrewor14 @davies Can you review the PR.

LGTM,
Merging this into master and 2.0, thanks!


Add example with manual deserialization.

We should add an example with complexity analogous to the lockup example, where we don't use borsh and manually serialize/deserialize everything by implementing the various Anchor traits--and fix any issues that pop up in the process.

some example of borsh proxy of spl program could be awesome


Does the SettingsService support 'ApplicationDataCompositeValue'?

From what I can tell the SettingsService only stores simple types. Does it provide support for 'ApplicationDataCompositeValue' and if not, can we get support for this?

Post a snippet here, so I can be sure we're on the same page.

I would like to be able to save a composite value. Here is an example of what I mean: https://msdn.microsoft.com/en-us/library/windows/apps/windows.storage.applicationdatacompositevalue.aspx
Windows.Storage.ApplicationDataContainer localSettings = Windows.Storage.ApplicationData.Current.LocalSettings;

// Create a composite setting

Windows.Storage.ApplicationDataCompositeValue composite = new Windows.Storage.ApplicationDataCompositeValue();
composite["intVal"] = 1;
composite["strVal"] = "string";

localSettings.Values["exampleCompositeSetting"] = composite;

// Read data from a composite setting

Windows.Storage.ApplicationDataCompositeValue composite =
   (Windows.Storage.ApplicationDataCompositeValue)localSettings.Values["exampleCompositeSetting"];

In the latest version (in GitHub) we are using CompositeValue as the base. This means, implementing it for you is no longer really useful. Not because it is the same functionality, I realize that, but because it automatically receives the increased quota and you can now serialize your data into a simple setting your own way without using the specialized dictionary. This also means that every user of T10 gets this benefit without explaining to them why they need to use a special type. That meets with the design goals of T10. Last thing, I can't imagine why I didn't do this in the first place. Thanks for the issue.

Thanks.


SAML2 SSO Integration Support

Description
This pull request introduces the implementation of SAML2-based Single Sign-On (SSO) authentication into the skills-service application. It enables users to authenticate via an external SAML2 Identity Provider (IdP), enhancing the security and convenience of user authentication.
Key Features:
1.
  -   Configured SAML2 login flow that supports a single identity provider.

2. SAML2 Configuration:
-  Added SAML2SecurityConfiguration class annotated with @Conditional(SecurityMode.SAML2Auth) to handle SAML2 security-specific configurations.
-  Relying Party Registration and security filters are defined using RelyingPartyRegistrationRepository and PortalWebSecurityHelper.

3. Custom User Details Service:
-   Implemented CustomSAML2UserDetailsService which loads user details via UserAuthService.
-   Mapping of SAML attributes to user details and role assignments.
4. Utilities:
-  Added SAML2Utils to manage authentication conversion, providing methods to transform Saml2Authentication to Authentication and UserInfo.
-  Automatic user creation or updates upon successful SAML login.

5. Controller Updates:
-  Enhanced UserController endpoints for user existence checks and root privilege granting based on SAML2 authentication using @Conditional(SecurityMode.SAML2Auth).

6. Test Coverage:
-  Added new test cases using Spock framework for the SAML2-related components, including security configuration and utility methods.

Other Changes:

Updated project dependencies in pom.xml to support SAML2 login.

Testing & Validation:

Tested with Okta as the SAML2 IdP.

Verified authentication flow, user creation, and role assignment are functioning as expected.
Let me know for any clarifications.  Feel free to make any adjustments needed for the integration

Thank you so much for submitting the SAML2 SSO Integration Support Pull Request! We've added some suggestions below as well as inline comments to the Files Changed to help refine the implementation. Thanks again for your hard work and for helping to improve SkillTree!

Could you please rebase master branch? Recently, we have updated our GitHub Actions Continuous Integration workflows to execute on pull requests. Please ensure that all the tests are passing successfully.

Please explore implementing service tests for SAML2 support instead of unit tests. This approach will provide more comprehensive testing and ensure that SAML2 functionality doesn't regress in the future. As outlined in the Contribution Guide, we aim to write black-box integration tests and supplement with unit tests only when necessary.

SkillTree's endpoint integration tests, located in the skills.intTests package, stand up the entire skills-service application and validate endpoint responses. To test SAML2 support, we can leverage an external dependency like a SAML2 protocol provider.

Here's a proposed approach:

Use Docker to set up a SAML2-compatible service: utilize an open-source service like Keycloak (Apache License 2.0), which provides a Docker image: https://www.keycloak.org/getting-started/getting-started-docker.
Configure the service for local development and testing: can initiate the setup via command line for local development and configure it as a service in GitHub Actions CI.
Write integration tests: Create specs that end with IT, which will run in the maven-failsafe-plugin and start a separate instance of skills-service/Spring Boot. In these tests, configure SAML-specific Spring properties. There are examples in the repository, such as skills.intTests.RankingAndProgressViewsDisabledIT.

Thank you so much for submitting the SAML2 SSO Integration Support Pull Request! We've added some suggestions below as well as inline comments to the Files Changed to help refine the implementation. Thanks again for your hard work and for helping to improve SkillTree!

Could you please rebase master branch? Recently, we have updated our GitHub Actions Continuous Integration workflows to execute on pull requests. Please ensure that all the tests are passing successfully.

Please explore implementing service tests for SAML2 support instead of unit tests. This approach will provide more comprehensive testing and ensure that SAML2 functionality doesn't regress in the future. As outlined in the Contribution Guide, we aim to write black-box integration tests and supplement with unit tests only when necessary.

SkillTree's endpoint integration tests, located in the skills.intTests package, stand up the entire skills-service application and validate endpoint responses. To test SAML2 support, we can leverage an external dependency like a SAML2 protocol provider.

Here's a proposed approach:

Use Docker to set up a SAML2-compatible service: utilize an open-source service like Keycloak (Apache License 2.0), which provides a Docker image: https://www.keycloak.org/getting-started/getting-started-docker.
Configure the service for local development and testing: can initiate the setup via command line for local development and configure it as a service in GitHub Actions CI.
Write integration tests: Create specs that end with IT, which will run in the maven-failsafe-plugin and start a separate instance of skills-service/Spring Boot. In these tests, configure SAML-specific Spring properties. There are examples in the repository, such as skills.intTests.RankingAndProgressViewsDisabledIT.

Added an integration test for SAML2 using testcontainers

@sudo-may  I see lot of UI tests failing. Is it an environment issue?  I need to add below statement  @IgnoreIf({env["SPRING_PROFILES_ACTIVE"] == "pki" }) to SAML2 Integration Test

@govind4u The issue of the Cypress visual regression tests failing is now resolved on the master branch. Feel free to rebase master branch and those tests should not pass for you as well.

@sudo-may  I have made few changes to integration test case.   I see action required status on the PR.  Can you have a quick look at it once ?

Hi @govind4u, unfortunately I haven't had time to do a deep dive into the integration test updates. But looks like SAML2IntegrationIT is currently failing. Would you be kind enough to take a look at the failures? Thank you!

Hi @govind4u, unfortunately I haven't had time to do a deep dive into the integration test updates. But looks like SAML2IntegrationIT is currently failing. Would you be kind enough to take a look at the failures? Thank you!

Modified the test case a bit.  If it fails again due to environment dependencies, I need to enable screenshots for debugging the root cause on the CI instance. It's working fine my local environment.

@govind4u Debugging CI failures could be tricky. Tests just finished; looks like SAML2IntegrationIT failed with TimeoutException;
SAML2IntegrationIT.SAML2 login flow with Keycloak integration:169->getSessionCookieFromWebDriver:234 Timeout Failed to log in and find the user settings menu

Since this is a backend service test there is no screenshots as far as I know of. Were there any clues in the skills-service log (service/target/skills-service-tests.log) for that job? It can be downloaded from GitHub's Artifact section. If needed, you could then further tweak the config to enable further debugging.

@govind4u Debugging CI failures could be tricky. Tests just finished; looks like SAML2IntegrationIT failed with TimeoutException;
SAML2IntegrationIT.SAML2 login flow with Keycloak integration:169->getSessionCookieFromWebDriver:234 Timeout Failed to log in and find the user settings menu

Since this is a backend service test there is no screenshots as far as I know of. Were there any clues in the skills-service log (service/target/skills-service-tests.log) for that job? It can be downloaded from GitHub's Artifact section. If needed, you could then further tweak the config to enable further debugging.

Bumped up Selenium version to make use of selenium manager for managing webdriver downloads.  Could you re-run the test cases to check it the failure is happening again.

@sudo-may :  SAML2 login test case need chrome browser on the VM for integration test case.  Could you please check whether google chrome is installed on the ubuntu VM in azure?  Made updates to keycloak signing certificate.  Is there a possibility to get temporary access to vm to check the root cause of failure ?

Hi @govind4u, Tests are executed in GitHub Hosted Runners and there is no direct access to these underlying VMs. Configuration for these workflows can be found in .github/workflows/ directory. The main on-check-in workflow is .github/workflows/build-and-test.yml (which appears to be manually disabled on your fork). Chrome is installed on these VMs and is heavily utilized by Cypress tests so we do know it works.
One of the steps in .github/workflows/build-and-test.yml prints the version of the Chrome:
Google Chrome 131.0.6778.69

The best way to debug tests that are passing locally but failing in CI is to add/configure additional logging and then review the logs. I know that the process can be a bit frustrating unfortunately! I know that it was my suggestion but if the integration test is adding too much complexity then it would make sense to simply revert to the unit tests and remove the introduced dependencies and certificates.

@sudo-may enabled debug logs. Could you please re-run the test suite ?

@govind4u done; however, I believe you can enable the Continuous Integration workflow on your fork and run the test suite on your fork https://github.com/govind4u/skills-service/actions

@govind4u done; however, I believe you can enable the Continuous Integration workflow on your fork and run the test suite on your fork https://github.com/govind4u/skills-service/actions

@sudo-may At last I was able to run the SAML2 integration test case successfully on my fork.   Looking forward to  successful merge to the master.  Let me know if you need further details

@sudo-may :  Can you merge my PR?   I see all tests have passed

@sudo-may : Can you merge my PR? I see all tests have passed

That's wonderful progress on getting the integration test to pass. However since the integration test was not passing we didn't review the changes after the initial feedback. We'll do our best to review the changes in the near future and get back to you and provide any feedback. Thank you again for the PR.

@sudo-may: Appreciate your review on the PR.  Incorporated the feedback and ran the test suite on my fork.  Everything seems fine.  Could you please have a quick look at the changes and merge the PR ?


Got "Permission denied" without log

Here is what I got :
My actions file:https://github.com/someone120/tizen_novel/blob/main/.github/workflows/auto-build.yml

Fix after changed to latest version.

ah cool, I was checking if the file was +x chmod and it was. Glad it's working.


Java indexer: properly handle file lookups in cwd [phab:D2058]

Created by schroederc at 2017-11-28 17:55:24:
This is needed to handle automatic module-info files in Java 9.

schroederc wrote at 2017-11-28 18:41:08:
Rebase

salguarnieri accepted this revision at 2017-11-28 18:44:42

schroederc closed via commit 50c50d2bfce3660b7165d3e234812ce0c4c668ca at 2017-11-28 18:49:21


[.NET WPF] build and publish AdaptiveCards.Rendering.Wpf.Core

What platform is your feature request related to? (Delete other platforms).

.NET WPF

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I found there is https://github.com/microsoft/AdaptiveCards/tree/main/source/dotnet/Library/AdaptiveCards.Rendering.Wpf.Core but it is not built and published to nuget
Describe the solution you'd like
A clear and concise description of what you want to happen.
build and publish AdaptiveCards.Rendering.Wpf.Core
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hi @paulcam206 I saw you merged the pr. When will package AdaptiveCards.Rendering.Wpf.Core be available in nuget? Thanks!


How to show msg distance on location bassed image

Can you show the code or example how to get distance text like here?

@MilosGlisovic to get the marker and text to appear together, you need to create a compound <a-entity> containing both text and a marker as child entities (see the fina; peakfinder example in the location-based tutorial. To get the distance between the current location and another, you can use the Haversine formula, you can use the computeDistanceMeters() method of gps-camera or gps-projected-camera to calculate this. Each object passed as an argument to this method should have latitude and longitude properties.
Hope this helps.

Sorry I didn't see the message. I want someting like this: https://www.youtube.com/watch?v=biCKHVefIe8 Create a-image and a-text like child element, and in a-text value put the distanceMsg attribute, but my code dont work


Dtype concat fail

Demonstrates the issue with PPDataProxy specifying the 'wrong' dtype. The data is reinterpreted as integer and the nans, and hence the masked points, are lost.
Even if this test is adopted it should not be merged as-is, since the test_data sha will need to be changed (see https://github.com/SciTools/iris-test-data/pull/50).

@bjlittle

Test now included in https://github.com/SciTools/iris/pull/2543


Set php 8.0 as minimum, remove yaml support, added attribute support.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@ee34790). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #12   +/-   ##
=========================================
  Coverage          ?   94.81%
  Complexity        ?       93
=========================================
  Files             ?       13
  Lines             ?      193
  Branches          ?        0
=========================================
  Hits              ?      183
  Misses            ?       10
  Partials          ?        0

Continue to review full report at Codecov.

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


Organize the "How to Guides" section in our docs

The How to section should have documentation like:

How ReactPlay uses Nhost as a backend. Here is the video that helps(https://www.youtube.com/watch?v=1qfDkmtuWqg)
How to create a Play on ReactPlay? We have the md already?
How not to override the styles of other plays while building a play?
How to interact with ReactPlay data
How authentication works on ReactPlay?

Whereas,
API Endpoints
Troubleshooting Guide
Database Schema should be outside of "How to Guide"
@Sachin-chaurasiya this issue is just to organize the "How to section". Please create issues for each of the elements mentioned above, if not created already.

The How to section should have documentation like:

How ReactPlay uses Nhost as a backend. Here is the video that helps(https://www.youtube.com/watch?v=1qfDkmtuWqg)
How to create a Play on ReactPlay? We have the md already?
How not to override the styles of other plays while building a play?
How to interact with ReactPlay data
How authentication works on ReactPlay?

Whereas,
API Endpoints Troubleshooting Guide Database Schema should be outside of "How to Guide"
@Sachin-chaurasiya this issue is just to organize the "How to section". Please create issues for each of the elements mentioned above, if not created already.

Sure @atapas.

Okay so @Sachin-chaurasiya  currently I'm unassigning you it's been a few months since it opened. if anyone wants to work please comment


support roks

https://github.com/open-cluster-management/backlog/issues/11120

/retest

/retest

@marcolan018 How does klusterlet support roks? Do we follow the same way? Thanks.

/retest

@clyang82
klusterlet supports roks from 2.2, and in fact, I almost reuse their code.

@clyang82
klusterlet supports roks from 2.2, and in fact, I almost reuse their code.

I saw you have logged an issue - https://github.com/open-cluster-management/backlog/issues/11125 against 2.1. since klusterlet supports roks from 2.2, we cannot support it in 2.1 separately. right?

/lgtm

@clyang82 that's a typo. I changed to 2.2

/retest

/retest

/retest

/retest

/test all

/retest


DOCUMENTATION: Update Notion with Staking Bot Back-End Requirements

Please push Back WIP code to github now
Please write-up a Notion for the Staking Bot Back-End Script.
Please invite team to review your proposal and requirements.

Closing as complete https://www.notion.so/volumefi/EPIC-02-16-24-JUICE-LIDO-TryLSD-Staking-Bot-Back-End-d6f66f428cd84a729d31597aee19a2d9


java.lang.NoClassDefFoundError: com.googlecode.androidannotations.api.SdkVersionHelper

Hello @ealden
There was a bug posted on AndroidAnnotations : https://github.com/excilys/androidannotations/issues/98
I don't know if it's an AndroidAnnotations bug or a gradle plugin bug, but I thought it could be interesting if you could take a look :)

Thanks for letting me know @pyricau.  I've started following the issue excilys/androidannotations#98 and will try to duplicate tonight.  Congrats on the 2.4 release BTW! :)

Hello,
The bug was coming from gradle and apk building by idea (all calls to my dependency libraries were throwing the same exception).


Add Minecraft Launcher

Tested on Ubuntu VM and appears to be fully working.
Feedback would be appreciated.

Looks good but perhaps install a jvm. I know minecraft comes with one but perhaps make a variable called optdepends with a jvm inside. I will add that functionality later

This is covered, default-jre is included in the depends as it was already a dependency for the minecraft-launcher Debian package.

Awesome. Minecraft good


Difficulty using supermonad with MSFs

Hi
I have a version of a reactive framework that works ok with different kinds of effects/indexed-like monads. This is based on [1].
I'm trying to make some things work with the API provided by supermonad, and using constrained monads. I find the separation between Bind and Return appealing, and I've found the notion of indexed and graded monads useful in a specific domain.
I'm having trouble compiling this version with constrained monads, though. Hope you can tell me if I'm doing something wrong (or if something could be done better). Sample code:
The basic type just takes an input and returns, in a monadic context, an output and a continuation.
import Control.Supermonad.Constrained.Prelude

newtype MSF m a b = MSF { step :: a -> m (b, MSF m a b) }

For example, applying a transformation point-wise is straightforward.  Composition is the thing that's not working. I've commented the signature, because it does not type-check. It assumes there may be an intermediate monad n0 and an intermediate result may be of that type.
-- compM  ::  forall m1 m2 m3 a b c
--        .   ( Return m1, Return m2, Return m3, Bind m1 m2 m3, Bind m3 m3 m3, Bind m2 m2 m2, Bind m1 m1 m1, ReturnCts m3 (c, MSF m3 a c))
--        =>  MSF m1 a b
--        ->  MSF m2 b c
--        ->  MSF m3 a c
compM (MSF msf1) (MSF msf2) = MSF $ \a -> do
  (r1, msf1') <- (msf1 a)        -- :: m1 (b, MSF m1 a b)
  (r2, msf2') <- (msf2 r1)       -- :: m2 (c, MSF m2 b c)
  return (r2, compM msf1' msf2') -- :: m3 (c, MSF m3 a c)

Stupidly enough, this works in Idris, and requires (Return m3, Bind m1 m2 m3, Bind m2 m2 m2).
I'm compiling with the right flags: -fplugin Control.Supermonad.Plugin -dynamic -dcore-lint.
I suspect it may have to do with the default associativity of bind, but I'm not sure.
Do you know what may be going on here?
[1] http://github.com/ivanperez-keera/dunai

Ok... somehow this works with the signature:
compM  ::  forall m1 m2 m3 a b c
       .   ( Return m1, Return m2, Return m3, Bind m1 m2 m3, Bind m3 m3 m3, Bind m2 m2 m2, Bind m1 m1 m1
           , ReturnCts m3 (c, MSF m3 a c)
           , BindCts m1 m2 m3 (b, MSF m1 a b) (c, MSF m3 a c)
           , ReturnCts m2 (c, MSF m3 a c)
           , BindCts m2 m2 m2 (c, MSF m2 b c) (c, MSF m3 a c))
       =>  MSF m1 a b
       ->  MSF m2 b c
       ->  MSF m3 a c

I may have been doing something wrong before.


idempotent start

make the .start() and .stop() methods of EmbeddedElastic Idempotent to themselves (consecutive calls to the same method from different threads will have no effect)
fixes #64

@gaczm I'm a novice in groovy and rusty in java concurrency.
I did my best, and would appreciate review and feedback.

Thanks for your PR and sorry that it took so long :/ I've added comments, please look at them

It looks fine now :) I will release it as 2.7.1 soon


[Easydict v2.7.0] ✨ Use list tag accessory to show exam type

Description

[v2.7.0] - 2022-12-16
💎 Improvement

Improved the display of word exam collection level, use tag label display.

🐞 Fixes

Fixed the problem that the input text was not displayed when querying from arguments.

It seems Raycast API bug, if not use setTimeout, the searchText will not be updated when value is from Arguments.  Maybe you guys need to verify this problem.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

How can I test this error @tisfeng, can you give me a guide?

@pernielsentikaer If you have any other questions, please let me know.

It seems Raycast API bug, if not use setTimeout, the searchText will not be updated when value is from Arguments. Maybe you guys need to verify this problem.

Can you make me a repro guide on how to test this issue?

I've uploaded a bug test branch https://github.com/tisfeng/Raycast-Easydict/tree/easydict-bug-3917, you can run it directly and follow these steps to reproduce the bug I'm talking about

enter the query text using the arguments type, such as log, and enter.
At this point the extension has worked, but the searchText is not displayed, this is the bug.

As a comparison, you can follow the above steps, also on my PR branch https://github.com/raycast/extensions/pull/3917, because my PR branch uses a temporary fix, so it can show the searchText properly.

checking this soon

Hi @tisfeng
Sorry for the long response time; I missed my notifications on this PR
The high amount of console logs exhausts the API's internal message buffer, and that's why it's not working. We're considering increasing this buffer, however, reducing logs or maybe adding a global flag for disabling them would work in development.
I tested it by removing all console.logs and replacing:
setTimeout(() => {
           updateInputTextAndQueryText(trimQueryText, false);
         }, 20);

with
updateInputTextAndQueryText(trimQueryText, false);

@pernielsentikaer Yes, you are right, the problem was indeed caused by the console.log, and after I disabled it, there was no more problem.
Finally, I hope you can increase the API message buffer, after all, many times the console.log is still very useful in a development environment.

Actually in production we remove console.logs so it's not a problem there, it's more a problem when developing the extension and want the logs, can you add a flag in the code to fast toggle while debugging?


Support Connect Server!

Hi, Im trying to connect server run file test.js become Server Side. but when I connect to Server over 8080, i got it response error 400, How can solve my issuse! Thanks all.
Nice Project!

hi! this project is just about a decade old and I haven't maintained it at all since I uploaded it. I'm actually kind of surprised it's still getting use. Unfortunately, I'm unable to devote time to this project to bring it up to spec with modern socket.io, so I am unable to help with this particular issue. I welcome contributions to this project if anyone's interested in updating it, and would also welcome a new maintainer if someone's interested in taking a more active role in this library.


t - Time to experiation in years

Can you explain that parameter? In your expamle this value is  .1
I calculate this value so ((new Date(date)).getTime() - (new Date).getTime()) / 86400000 / 365
but in this case I get wron volatility, for example equal to 1,64, more than 1 (100%)
If I calculate this value so ((new Date(date)).getTime() - (new Date).getTime()) / 86400000 / 365 * 100 then I get more correct value of volatility, but anyway this value does not equal to volatility from http://finance.yahoo.com/q/op?s=AAPL+Options
How to calculate the volatility?
For example I have next data:
Symbol: AAPL, Exp: 7/31/2015, Call, Strike: 105
I passed next parameters to getImpliedVolatility(expectedCost, s, k, t, r, callPut, estimate)
18.3 123.575 105 0.8860913146879756 0.05 "Calls"
And have got such result as 0.6890625 but in yahoo volatility is 71.48%

The 't' parameter is the time until expiration measured in years.  This is going to differ for each person depending on how they define a year.  A calendar year is usually 365 days, but only about 252 of those are trading days.  It's a matter of preference which value you decide to use.  This has the side effect of producing a different volatility measurement than someone using a different value.
Yahoo finance might use a different value than you are, resulting in differing volatilities.  Yahoo finance is also delayed a little bit so it isn't showing real time data.
I'm not sure I understand your initial formula.  It looks like you're calculating a time delta in milliseconds, then dividing by 86400000 to convert to days, then dividing by 365 to get years.  This looks right, but I'm not sure how multiplying by 100 gave you a more accurate answer.  Multiplying by 100 will just convert from a decimal to a percent.
You might also not want to play too much with the 'estimate' parameter.  Using numbers that are too large or too small can cause the algorithm to diverge and produce an incorrect volatility.  The algorithm is essentially just a binary search type of guess and check.
Your last calculation looks right though.  Yahoo probably just uses a different denominator to calculate 't' as mentioned above.  Also, are you sure about your risk-free interest rate?  Five percent seems kind of high.  I think a one year US government bond is going for about a quarter of a percent right now.

I would just write a simple test case which iterate through all options of a given ticker (user specified ) and displays yahoo vol and our calculated vol - let's see how different the number is


Fix Dyson async_add_job

Description:
Related issue (if applicable): fixes #8097
There was a bug in dyson fan and dyson sensor entities while using async_call_job. This PR fix the bug.
It is a bug fix for version 0.47.
Checklist:
If the code communicates with devices, web services, or third-party tools:

[X ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass

Cherry-picked for 0.47.1


Support sqla 1.4

Still a draft, need to make sure all this changes will not break users in older versions of SQLA

closes #83

Thanks! Let me know once this is ready for review.

@tswast - Almost ready,
I'm debating about having SQLA 1.4 a dev requirement (for tests)
and about 1 issue of backward compatibility, which might be an issue only if someone actually passed inline to BigQueryCompiler

I'm debating about having SQLA 1.4 a dev requirement (for tests)

Ideally we'd have some test sessions for our minimum requirements as well as the latest supported. I've created https://github.com/mxmzdlv/pybigquery/issues/85 to track this.

In the meantime, I'm okay adding a dev requirement.

@alonme Apologies, but I just "blackened" all the source in this repo. It will most likely cause some conflicts.
In good news, we do now have "constraints" files in the testing/ directory which allow us to test against specific package versions for each of our test sessions. Plain ol' pytest should still work, but to use that multi-version testing, we can run with nox http://nox.thea.codes/

See: #177