chore: re-enable test for checking pipeline logs

Description
re-enable the test after https://issues.redhat.com/browse/KFLUXBUGS-99 was fixed
Issue ticket number and link
https://issues.redhat.com/browse/KFLUXBUGS-99
Type of change

[X] re-enable test

How Has This Been Tested?
 ginkgo --focus-file tests/build/build_templates.go --v ./cmd/

Checklist:

[X] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/lgtm


feat: fetch Team Members Info

1. Objective

Migrate Team Members Info into WordPress
Source Team members info from WordPress into Gatsby

2. Description of change

N/A

3. Quality assurance

Assert that the team members info shows up on the/about-us page

4. Operations impact

N/A

5. Business impact

N/A

6. Priority of Change

Normal

@Joponpin2000 kindly point to master, the staging branch/server is down atm, and considering Gatsby gives us preview links, we should be able to survive without it for now. You might have also forgotten to add me as a reviewer


Create Single-Shot Ridge Regression Computation inside Docker

Should interface with COINSTAC pipeline.

➤ JingMing commented:
20 story points for this project


Error:  Cannot read property 'replace' of undefined

This could be a symptom of something wrong on my end, but this page:
https://bahrus.github.io/api-viewer/index.html?npmPackage=xtal-frappe-chart&jsPath=xtal-frappe-chart-example1.js
gives error
Error:  Cannot read property 'replace' of undefined
when clicking on the demo option.

Thanks for the issue. Fixed by ef7537c12a3a5ea9485645385f05fae2a55c722e and released as 0.3.4


Ability to inspect the inspector

Working on UI with the inspector is great. But now I’m spoiled and on working UI without it (aka working on the inspector itself) is painful.
I want a dogfood icon that lets me open up another inspector to inspect the inspector.

Icon acquired but... probably a bit of a technical challenge...

Icon improved, but uhh... I'm still not in the mood for the refactor...

Inspector should be able to inspect any top level juce component. For plugins it's mostly fine to only inspect one component, but the applications I work on have multiple desktop components and I should be able to inspect any of them.


Use IConnectionEndPointFeature to get IMqttChannelAdapter.Endpoint in aspnetcore31

In aspnet core, the connection(except websocket connection) is handle by MqttConnectionHandler, so the HttpContext instance allway is null, we should get Endpoint from IConnectionEndPointFeature.

this will fix #346

@xljiulang can you check if we can use the RemoteEndPoint on the connectioncontext mentioned in  #346

@JanEggers Could you do the requested change in order go get this done?

@Jane ping...

sry was busy will try to look at it in evening

@JanEggers Please let me know when this is done.

it is done the tests are still not wrking but that seems unrelated

@JanEggers You mean the new tests in this PR or the ones which are still failing. I have to check them. But I am wondering because they work fine on my machine even 10 times in a row. They fail only at the CI.

Test method MQTTnet.Tests.ManagedMqttClient_Tests.Subscriptions_Are_Cleared_At_Logout threw exception:
System.Exception: Client(s) had 1 errors ($[2020-04-14T17:20:06.8439151Z] [client] [16] [MqttClient] [Error]: Error while connecting with server.
MQTTnet.Exceptions.MqttCommunicationException: The operation is not allowed on non-connected sockets.
---> System.IO.IOException: The operation is not allowed on non-connected sockets.
at System.Net.Sockets.NetworkStream..ctor(Socket socket, FileAccess access, Boolean ownsSocket)
at System.Net.Sockets.NetworkStream..ctor(Socket socket, Boolean ownsSocket)
at MQTTnet.Implementations.CrossPlatformSocket.GetStream() in C:\projects\mqttnet\Source\MQTTnet\Implementations\CrossPlatformSocket.cs:line 193
at MQTTnet.Implementations.MqttTcpChannel.ConnectAsync(CancellationToken cancellationToken) in C:\projects\mqttnet\Source\MQTTnet\Implementations\MqttTcpChannel.cs:line 74
at MQTTnet.Internal.MqttTaskTimeout.WaitAsync(Func`2 action, TimeSpan timeout, CancellationToken cancellationToken) in C:\projects\mqttnet\Source\MQTTnet\Internal\MqttTaskTimeout.cs:line 32
at MQTTnet.Adapter.MqttChannelAdapter.ConnectAsync(TimeSpan timeout, CancellationToken cancellationToken) in C:\projects\mqttnet\Source\MQTTnet\Adapter\MqttChannelAdapter.cs:line 71
--- End of inner exception stack trace ---
at MQTTnet.Adapter.MqttChannelAdapter.WrapException(Exception exception) in C:\projects\mqttnet\Source\MQTTnet\Adapter\MqttChannelAdapter.cs:line 314
at MQTTnet.Adapter.MqttChannelAdapter.ConnectAsync(TimeSpan timeout, CancellationToken cancellationToken) in C:\projects\mqttnet\Source\MQTTnet\Adapter\MqttChannelAdapter.cs:line 76
at MQTTnet.Client.MqttClient.ConnectAsync(IMqttClientOptions options, CancellationToken cancellationToken) in C:\projects\mqttnet\Source\MQTTnet\Client\MqttClient.cs:line 92).
Stack Trace:
at MQTTnet.Tests.Mockups.TestEnvironment.ThrowIfLogErrors() in C:\projects\mqttnet\Tests\MQTTnet.Core.Tests\Mockups\TestEnvironment.cs:line 138
at MQTTnet.Tests.Mockups.TestEnvironment.Dispose(Boolean disposing) in C:\projects\mqttnet\Tests\MQTTnet.Core.Tests\Mockups\TestEnvironment.cs:line 156
at MQTTnet.Internal.Disposable.Dispose() in C:\projects\mqttnet\Source\MQTTnet\Internal\Disposable.cs:line 41
at MQTTnet.Tests.ManagedMqttClient_Tests.Subscriptions_Are_Cleared_At_Logout() in C:\projects\mqttnet\Tests\MQTTnet.Core.Tests\ManagedMqttClient_Tests.cs:line 331

Interesting. I will have a look. But to me it seems to be a race condition because the GetStream is called when the socket is already disconnected (or was never connected).


Method to return a sublist slice of an arbitrary Iterable

I would like something like the following method:
List<E> sublistOfIterable<E>(Iterable<E> iterable, int start, {int? end, bool growable = false}]) {
  ???
}

The method produces the same result and range errors as
iterable.toList().sublist(start, end).toList(growable: growable)

except  (1) it does not call Iterator.current on any element outside the [start, end) range, (2) does not call Iterator.current more than once on any element, and (3) avoids unnecessary allocations.
It is quite challenging to extract a properly checked [start, end) sublist of a lazy Iterable.
Naive approaches based on iterable.skip(start).take(end - start) fail to distinguish edge cases.
See https://github.com/dart-lang/sdk/issues/50253#issuecomment-1287882913.
I would suggest this for package:collection except that I want to use it in the SDK for solving #50253.
/cc @natebosch

cc @lrhn

Why?
More precisely: why start with an Iterable, where you are not supposed to know the length, and still use a method which gives errors if you guess the length wrong?
That's an unsafe combination of operations, which means it's a bad design for a single operation.
Why not return an empty or truncated list of the star/end are beyond the available values?
Or a composite result of the available values and the index of them last seen value, which is at or below end.

I wouldn't start with an Iterable, where you are not supposed to know the length, and use a method which gives errors if you guess the length wrong. That's an unsafe combination of operations, which means it's a bad design for a single operation.

This 'bad design' is the design of String.fromCharCodes.
I think that there is some path dependence in the bad design - the slice arguments were added later. If the slice arguments were in the initial signature, I suspect codePoints would have been a List, and we would not be having this discussion.
So I understand not wanting to have this sublist-of-Iterable operation to discourage similar signatures. But it does mean we have to be very inventive where we have the bad design, and each place will have complex and possibly buggy code.
At least the code in the dart: libraries has access to EfficientLengthIterable.

I'd rather just return an empty or truncated list of the start/end are beyond the available values.
Or a composite result of the available values and the index of them last seen value, which is at or below end. But probably just the empty result.
If there is a use-case which repaired the throwing, I'd look to change that instead.

I'm not sure I understand what is meant by 'repaired the throwing'.

For the fromCharCodes, just let it accept too large start and end, like a proper Iterable processor.

The documentation says "The start and end values must satisfy 0 <= start <= end <= charCodes.length.".
Generally the core library validates such requirements. The validation is part of the tests, and in this case, there are corelib tests that the validation occurs that will fail with skip/take slice.

"required". Damn mobile keyboards.
And yes, I suggest just changing the behavior of fromCharCodes. Being not permissive it's not a breaking change.

+1 to changing the other API to be more permissive over adding another restrictive API to match.


Change name of console script to match name of package

The pipx run command makes it very convenient to download a package and run a script entry point which has the same name as the package. If we want to take advantage of that convenience (and I'd say we do), we should change the name of our console script from setup-to-pyproject to setuptools-pyproject-migration. (Or at least we need to add a console script with that name, but I don't think there's any point in having two scripts that do the same thing, except for backward compatibility but we don't really have to care about that while the package is at such an early stage of development.)

@sjlongland any thoughts? I tentatively assigned this to the next milestone since if we are going to do it, we should do it ASAP (and it'll be an easy change anyway, probably a simple find-and-replace with e.g. sed), but I'm definitely not implying that this couldn't be discussed.

We can add the new name and remove the old one when we get to a 1.0 release (or maybe 0.3/0.4).
If it's a minor change, and the old one is literally just a one-line change to remove, we can defer that… it's not like it's any extra effort on our part. :-)

I suppose not wanting to pull the rug too quickly.  For certain though, we shouldn't leave it around too long.
Given the alpha status of the project, this isn't as big a problem as it could be, but still, I like to give people just a little warning of a possible breaking change.

Yeah, I agree with that, but that seems like a reason to avoid removing the existing script name for a little while, not a reason to avoid adding a new one. It would be fine to have two names for the script for a version or two. (I actually found another project that does that just today.)
In this specific case, I'm also thinking about the fact that we've only had one (non pre-)release, which was not widely advertised, and it doesn't even really work, because of #100. So the negative effects of removing the existing script name are very low compared to most other situations in which we might contemplate a change like this. (And the fact that the project has not reached version 1.0 should be an indicator to people to expect that things can change without warning.)

Well, it works, just not via the script we intended.  I'm fine either way, the fact we advertise our "major" version as 0 is reason enough to expect the occasional rug-pull.
(Heck, most of mine stay at 0.0.x for years.)
Still, I like to not get into the habit of making breaking changes even at this early stage because it then becomes a hard habit to break out of when a project matures. :-)

Still, I like to not get into the habit of making breaking changes even at this early stage because it then becomes a hard habit to break out of when a project matures. :-)

That's a fair point. I'm not worried about it though because we both agree that this change would be unusual, and not something to make a habit out of. (And if any other regular contributors were to come on board to this project, they would probably pick up on the same thing.)
And yeah, the "it" that doesn't work was the script - I was speaking imprecisely though, sorry!


Registry tool: registry delete bulk deletions require multiple passes.

When deleting large collections of APIs, I found that some APIs remained after I had run registry delete apis. Running it again, a smaller number of APIs remained, and after a few iterations, all were gone.
I believe this is occurring because the server-side pagination is using numerical offsets, and as registry delete is iterating over items to delete, it begins deleting them in concurrent workers, so by the time the offset is used to get the next page, some of the APIs that were supposed to be skipped are gone, and the offset skips APIs that haven't been listed yet.
Summarizing, the registry List APIs don't support deletion of items while paginating over them. To fix this, we might:

Client side: collect all items to be deleted before we begin deleting them. This will slightly delay the start of deletion, particularly for large collections.
Client side: build iteration into registry delete and count the deletions in each pass, looping until no deletions occur.
Server side: modify list pagination to use keys (and paginate by returning results "after" the last key returned or beginning with the "next" key) and verify that this allows deletion to occur during pagination.

I think # 2 is a good short-term solution because it keeps deletion running quickly and is easier than # 1 to undo if we decide to do # 3.
Update: # 2 is not great because subsequent iterations can return APIs before queued-up tasks have deleted them. When this happens, we try to delete the same API twice, which generates an error. So to avoid more complexity, I'll step back and use approach # 1 instead.

Fixed by #1011.


chore: Move non runtime packages to dev dependencies

I noticed these packages were bringing in some extra dependencies of their own but seem unused except for internal development.

Ah, sorry. I'm unfamiliar with pnpm I've gone ahead and run
npx<EMAIL_ADDRESS>install

And it looks like that has updated the lockfile.
I didn't see a CONTRIBUTING.md file or dev instructions in the README.
I'd be happy to open a PR with a file like that with some basic how-to's if that would be helpful. Off the top of my head I can think about:

Development setup (using pnpm)
Tests (adding tests, running tests locally, etc)
How to use changeset to describe PR

thanks for this, Nick! you're one of our first outside contributors,  sorry for that oversight, but either way I'll be sure to add a contributing.md moving forward!
looks like the install worked by the way! just one failing test now, I will check back later when i get home

👍 np! Thank you for the quick response


[desktop_webview_window] Include openDevToolsWindow

I included the possibility to open the dev tools window from webview2 for debugging

SGTM. Thanks for the contribution.


Why sometime there's no jest report in action?

Like this one:

In fact the junit.xml exists, but there is no jest junit report in action.
This is the expected:

Hi @abcfy2. It might be that the action isn’t able to find the report file. Although it should still create an empty job report instead of failing silently.
Do you have this problem on a public repo or is it something confidential?

I have no public repo. But it seems only the first build for specified branch could work.
For example. First build of branch main could see jest report, but when I triggered much more times, it cannot work.
But when I checkout a new branch dev, also only the first build could see the report.
You can find the action configure in the screenshot.


Update Release Action for Godot 4.0

Recent release action runs have been failing: https://github.com/abarichello/godot-ci/actions/runs/4473942443
Most recent fix for this issue (#104) seems to be missing the piece that would make the release action utilize the changes made. With this update we will provide the new arguments to pull the correct zip for Godot 4.0 and run it with the expected arguments mentioned in #104.
I included a check to continue supporting 3.X versions of Godot.
Of course, let me know if I need to update anything here. Thanks~

I have made a lot of updates to this PR based on testing I have been running on the fork I made to create this PR. Here is a description of some of the changes I have made:

Firstly, I updated mono.Dockerfile to support new args for Godot 4. These changes are similar to the recent changes to Dockerfile made previously in PR #104
Then we have the changes to the github workflows. For release.yml and manual_build.yml, I added build args that are utilized in the docker files. These build args are written to support Godot 3 and 4, depending on the input of the action.

For testing I setup the fork to build the docker images to dockerhub: https://hub.docker.com/r/seanmaxwell/godot-ci
I tested by running the manual build action against old tags in the repo. With this strategy I successfully built images for Godot versions: 3.5.1, 4.0, and 4.0.1. As of writing this, I haven't tested any of these images, I plan to test the 4.0.1 image in a gitlab pipeline when I find more free time for this project.
I also tested the release action by adding a tag that wasn't present in the fork, after I forked this repo. This tag was 3.5.2-stable (a maintenance build for Godot 3 added this year), you can find the image created by this release action here: https://hub.docker.com/layers/seanmaxwell/godot-ci/3.5.2/images/sha256-4c4965274d789678f409e18d209302ff0d1634a104383b414ce02b70a08588d4
Let me know if there is anything further I can provide to help getting this repo 4.0 ready. Thank you~

I have completed some tests with a gitlab pipeline deploying a 4.0.1 project using the dockerhub images I built with these changes and it works for me.

I tried a web export with @seanmaxwell 's dockerhub image (4.0.1) in a github pipeline. I had to change some arguments and the export templates path seems to have changed, but in the end I was able to make it work.

Any update on if this will become available soon!? Looking to move some of our projects to 4.x and would love to have our CI/CD pipelines available!

The Godot 4 image is still not on Docker Hub. Now that the PR is merged, is there something like a manual job to run to deploy the image ?

Does someone need to retry the failed 4.0 releases?

I saw that the manual job called "manual_build" can be used to manually build an image and push it to Docker Hub.
But for information, I created the pull request #106 with a bug fix regarding the mono Dockerfile.
If this PR looks good to the maintainers, it would be great to merge it (or at least to add a commit for the bug fix) before generating the first Docker image for Godot 4.
If someone is interested (for a quick CI test), I generated test images for Godot 4 (to test my pull request). I don't recommend using them for production CI (I might have to run tests that would make these images dysfunctional), but it allowed me to verify that the generated Godot 4 images work correctly at least for Windows and Linux exports (with my PR modifications).


feat: Add infracost hook

Put an x into the box if that apply:

[ ] This PR introduces breaking change.
[ ] This PR fixes a bug.
[x] This PR adds new functionality.
[ ] This PR enhances existing functionality.

Description of your changes
Close #206, Relates #216
How has this code been tested

Install infracost and get the API key. Docs

Add to .pre-commit-config.yaml:

- repo: git://github.com/antonbabenko/pre-commit-terraform
  rev: 01aa7f52166c8f7ef066eacaba9dfafdbeff158c
  hooks:
    - id: infracost_breakdown
      args:
        - --args=-p environment/qa
        - --hook-config=
            .totalHourlyCost >   0.1
            .totalHourlyCost <= "1"
            .projects[].diff.totalMonthlyCost!=10000
      verbose: true # Always show costs

env/dev - path to TF folder where the check should run

Run

git add -A
pre-commit run

Usage instructions in README and CONTRIBUTING
Example output:

@yermulnik rereview please


Add flynt package to linter

I'm updating the linting procedure to include flynt, which is a package that automatically searches for and replaces older-style format strings with f-strings (in most cases). This is a change we made a while ago in polaris (https://github.com/E3SM-Project/polaris/pull/74).

Checklist

[x] Testing comment in the PR documents testing used to verify the changes

Testing
I created the mache dev environment and verified that flynt was installed. Then, I created a python file with an old-style format string and ran pre-commit on that file, and it flagged and automatically fixed the format string as expected.


Kibana reported that ES is not working in EC2

Hi,
I've deployed the TF in my AWS environment and when I logged in to Kibana I found out that ES and Logstash is not working at all.
<EMAIL_ADDRESS>- Service Unavailable
<EMAIL_ADDRESS>- Elasticsearch cluster did not respond with license information
I also get multiple errors on x-pack services with the same errors on license information.
I've tested out the network from the coordinated node (aka client) to the masters and also to the data and verified that I was able to reach to ports 9300 and 9200.
What else is needed to check in order to get it working?

How this you fixed this issue?


Add Anthropic support

The plugin seems to support just openAI GPT. Would be great to support anthropic, mistral and other AI providers as well.

Right, there is currently no built-in support for other AI providers. However it is possible to configure plugin with any OpenAI-compatible API. There are currently many projects providing OpenAI compatible proxies to all kinds of LLMs, such as littlellm and other, see Custom APIs on Wiki.


Replace transparency from color if present

Thanks for offering an improvement @Flamenco.
However, I don't think that this is the right approach. y-prosemirror accepts a 6-character long hex color without transparency. There are many more edge cases that I'd have to cover if y-prosemirror accepted any kind of color (3-character hex colors, HSL colors, and so on..). It is better to keep this minimal. If you have transparent colors stored, you could transform them before you supply them to y-prosemirror.

The problem is when my color editor sets the color from tiptap's collab cursor plugin, the cursor shows but not the highlighted area.  This was traced to y-prosemirror not checking the format.  In the end a regular expression and other color formats would be best.
I'd call this a hotfix.

@dmonad I think cleaning up this edgecase is valid.  Just because you want to support other in the future is not a reason to let your code generated garbage.
If you noticed, i did not allow the opacity to go through for that very reason, and used your appended value.

At the very least, your code should validate the input, output and warning message, and your strict color format should be clearly documented.

The cursor plugin in y-prosemirror does not support transparent colors. Supporting other color formats is out of the scope of this project. I don't want to pull in another library just to do color transformations (aside from that, I'd need to maintain many more edge cases because of this choice). y-prosemirror only supports 6-digit hex colors which is a fair restriction. The user of this library can do the color transformation. Though it really would be nice if there was an error message when the user supplies an invalid color format. Is that something you'd like to work on? Happy to merge a PR that logs a warning and maybe documents the feature better.

@dmonad  I will resubmit a PR, and emit a warning, but you are still opposed to truncating the hex transparency with 8 digit hex color?

https://github.com/yjs/y-prosemirror/pull/78


Consider publishing in NPM repository

All it takes is to run npm publish  and repeating it every time new release is ready.
This will improve discoverability of your amazing project.

That's a very good suggestion, it would probably make it much more convenient to install. Here's the first release: https://www.npmjs.com/package/obsidian-typings
I've been trying to improve the experience of including the types a bit, I think the three installation methods basically cover everything? Besides that, I've also added a short guide under CONTRIBUTING.md that describes how to interface the different objects (through my lens, at least).
Thank you again for all your PR's and suggestions, I am very unfamiliar with the npm ecosystem/correct typings, so I very much appreciate all your help.

I will close this issue now as the NPM package should be fully completed now, thanks again for the suggestion!


feat(trading): copy apply referral link from code tile

Related issues 🔗
Closes #5220
Description ℹ

adds additional button next to the copy button that allows one to copy the shareable link to the apply code page

Demo 📺
https://github.com/vegaprotocol/frontend-monorepo/assets/1980305/ba5565f2-92dd-47ca-b60a-fdb18e4f2bdb
Technical 👨🔧
CopyWithTooltip accepts the tooltip's description that shows on hover.

@asiaznik I think it's fine but:
the referee also gets this copy:

I think it makes sense.


Custom-URL-scheme does not work after installing this plugin

Hello,
I have the EddyVerbruggen/Custom-URL-scheme install and working,, However, after installing  the firebase plugin the Custom-URL-scheme is not working. If I remove it then the custom url works again,,,
Can you give me some suggestion on how to resolve this issue?. I really need both plugin to work in my app,,
Thanks

Thanks for looking into this issue..

Closing for cleanup.  Please test with the latest version and reopen if it is still an issue.


Add Kotlin Template to Spring Boot Stack

Checklist:

[x] Read the Code of Conduct and Contributing Guidelines.

[x] Followed the commit message guidelines.

[x] Stack adheres to Appsody stack structure.

Modifying an existing stack:

[x] Updated the stack version in stack.yaml

Adds Kotlin compiler to the base Spring Boot 2 stack.
Adds Kotlin Template to the Spring Boot 2 stack. (Pending resolution of Issue https://github.com/appsody/appsody/issues/38 )
Note there are some gymnastics here to enable Kotlin version to be defined outside the Dockerfiles, ideally the version should also be used to generate? the parent pom, but for now the cleanest route is to just have the version defined in two places. This places an added burden on the Stack author to ensure the version remains in sync in both places, but since a human is involved, maintains a lower risk of accidentally creating multiple parent poms with the same maven coordinates (group/artifact/version) but with different content (this would be bad).
Related Issues:
Related to PR#101, but adds Kotlin to the base boot stack, with the intent of making it available as a template, rather than as a parallel stack.

@BarDweller Though its not a "must-do", the tests could be in Kotlin too. You may refer to the changes of #101


It's not using actual localStorage

I'm using a library angular2-jwt which relies on localStorage object.
After setting a @LocalStorage value, it's not actually setting anything on window.localStorage, but based on source code, if I understood correctly, it's using custom object for storing the values.
I think the name of the package is misleading, since people would assume it uses window.localStorage which I'm sure lots of libraries depend on.
This package is really great, but is it possible to use actual window.localStorage?
Thanks in advance.

Sorry, that was meant for a different repo


hello wolvan love your app

but in light of the most recent 3ds firmware update some ppl will most definitely want you to re-create a 3dsx version  as newbies can no longer get it to cia installs.

@Wolvan Please close this issue because it is "spam".


Optimize radix tree related modules

Change summary:

Use terminalNodeMap instead of stateNodeMap (target: state node -> terminal radix node)
Optimize _getRadixNodeForReading() using terminalNodeMap
Optimize copyFrom()
Immediately update state info (by calling updateStateInfo()) from StateNode.deleteChild()
Keep tree info in RadixNode
Deprecate hexLabelCache and RadixChildMap
Optimize deleteStateTreeVersion() using deleteRadixTree()
Fix and simplify updateStateInfoForAllRootPaths()

Related issues:
https://github.com/ainblockchain/ain-blockchain/issues/519
https://github.com/ainblockchain/ain-blockchain/issues/517

Addressed the comments so far~ PTAL @liayoo

Thanks for the fast review. Now merging..


UIElement.ProtectedCursor property doesn't work

Describe the bug
ProtectedCursor property doesn't change cursor type for the UIElement.
Steps to reproduce the bug

Open the attached project "Sample_SDK_0.1.0"
CursorBugSamples.zip
Run the project
Tap on the 'CursorTestButton' button
Cursor doesn't change

Expected behavior
Cursor type should be changed for UIElement after set ProtectedCursor property.
In the attached project 'Sample_0.8.0' ProtectedCursor property works as expected and cursor for the test button change.
Version Info
NuGet package version:
[Microsoft.WindowsAppSDK 0.1.0-preview1]

Windows version
Saw the problem?

Insider Build (xxxx)

Ocrober 2020 Update (19042.1110)
Yes

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

@codendone is this expected?


fixed versions for 1.0 tooling

Fixes #1974
/cc @weshaggard @terrajobst

I was slightly confused on the direction we wanted to take here so synced with @terrajobst offline before submitting the PR this afternoon. I imagine he'd be fine with this. 😄
We can always change if not.


Add support for resolve_outdated_diff_discussions in Project

The Projects API supports resolve_outdated_diff_discussions, which is missing in the current implementation.
So adding support for resolve_outdated_diff_discussions to Project, ProjectApi.createProject and ProjectApi.updateProject allows API user to adjust the value.
Also adding support for initialize_with_readme to to Project and ProjectApi.createProject

@gmessner Thanks!


shadow on colored background

The shadow is weird if it's on top of a colored background. Example:

Can you please check it?

Hi! I checked it by using a background color for list in the sample. Shadow looks good:


Using SOLR and INFRA_SOLR together is not working properply

Hi,
if you use INFRA_SOLR and SOLR at the same time you will have issues in importing the cluster template. Because both services use the same configuration.

Regards
Uli

@hadoopch  You can either use one of each Solr or Infra-solr.
Or you need to change the port and directories for solr service, both Solr and infra-solr should use different port and configurations.

Hi Muhammad, SOLR and SOLR_INFRA are two different services and should have different default configuration settings to avoid error like seen in the screenshot. By defining everything  it in the defintion.yml it works. But this should be handled by default settings
Best regards
Uli


test(config): set CORS_ORIGIN to empty string for default test

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1146

Relevant Lines:
1146

💛  - Coveralls


langchain: add RankLLM Reranker

Integrate RankLLM reranker (https://github.com/castorini/rank_llm) into LangChain
An example notebook is given in docs/docs/integrations/retrievers/rankllm-reranker.ipynb

Great work @16BitNarwhal on integrating this to Langchain. Hopefully this brings in more interest in high precision and effective listwise paradigm for reranking models like RankZephyr!

Hey @hwchase17, thanks for the feedback! Made the following changes:

Moved rankllm to community along with the integration test and updated example notebook
Imported from langchain_core instead of langchain for callbacks
Directly get openai API key from env instead of importing openai

Also, I'm a bit unsure about something. I noticed that flashrank doesn't seem to be located in community. I see they support models like RankZephyr, which was built and is maintained by RankLLM team. Would it also be more appropriate for FlashRank to be in community?

Also, I'm a bit unsure about something. I noticed that flashrank doesn't seem to be located in community. I see they support models like RankZephyr, which was built and is maintained by RankLLM team. Would it also be more appropriate for FlashRank to be in community?

Yes it should be, thanks for flagging. we will move

Sounds good. And please let me know if there's anything else I need to do to get this merged 😁

Sounds good. And please let me know if there's anything else I need to do to get this merged 😁

some test/lint issues, i can try to resolve


Adds .crypto and .zil resolution support

Extends current .eth resolution functionality to support .crypto and .zil domains

We are moving to Krystal, a new app with more features, better rates, cheaper gas and attractive prizes. You can later on create PR to Krystal


[BUG] BSS POST not returns 201 but data missing in database if hosts are not valid xnames

Describe the bug
Dear OCHAMI development team,
I am testing OCHANI through deployment-recipes repo, I can deploy OCHAMI but for some reason I am unable to store data in BSS.
To Reproduce
Steps to reproduce the behavior:

Start OCHAMI following the deployment-recipes quickstart instructions
Run command

curl --cacert cacert.pem -H "Authorization: Bearer $ACCESS_TOKEN" https://foobar.openchami.cluster:8443/boot/v1/bootparameters -v -d '{"hosts": [test1.local", "test2.local"], "macs": ["00:40:a6:82:f6:c5","a4:bf:01:3e:c0:a2","00:40:a6:82:f7:0c"], "nids": [1, 2, 3], "params": "test", "kernel": "test", "initrd": "test", "cloud-init": {"user-data": {"foo": "bar"},"meta-data": {"foo": "bar"}}}'
...
< HTTP/2 201
< bss-referral-token: bd6f0308-bb1d-4335-b802-3550b7aec5ea
< content-type: application/json; charset=UTF-8
< date: Wed, 27 Nov 2024 19:13:06 GMT
< content-length: 0
<
* Connection #0 to host foobar.openchami.cluster left intact

Run command

curl --cacert cacert.pem -H "Authorization: Bearer $ACCESS_TOKEN" https://foobar.openchami.cluster:8443/boot/v1/bootparameters -v
...
< HTTP/2 200
< content-type: application/json; charset=UTF-8
< date: Wed, 27 Nov 2024 19:15:08 GMT
< content-length: 5
<
null
* Connection #0 to host foobar.openchami.cluster left intact

Expected behavior
http post is not storing data in postgres
However, adding correct xnames works
curl --cacert cacert.pem -H "Authorization: Bearer $ACCESS_TOKEN" https://foobar.openchami.cluster:8443/boot/v1/bootparameters -v \
-d '{"hosts": ["x0c0s2b0n0", "x0c0s3b0n0"], "macs": ["00:40:a6:82:f6:c5","a4:bf:01:3e:c0:a2","00:40:a6:82:f7:0c"], "nids": [1, 2, 3], "params": "test", "kernel": "test", "initrd": "test", "cloud-init": {"user-data": {"foo": "bar"},"meta-data": {"foo": "bar"}}}'

Screenshots
NA
Desktop (please complete the following information):
cat /etc/*release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.10
DISTRIB_CODENAME=oracular
DISTRIB_DESCRIPTION="Ubuntu 24.10"
PRETTY_NAME="Ubuntu 24.10"
NAME="Ubuntu"
VERSION_ID="24.10"
VERSION="24.10 (Oracular Oriole)"
VERSION_CODENAME=oracular
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=oracular
LOGO=ubuntu-logo

Smartphone (please complete the following information):
NA
Additional context
NA

I didn't think BSS supported identifiers other than xnames.  Is that feature supported on a CSM system with BSS?

I assume it would only work with valid xnames.
However, BSS validates the mac addresses so I would assume it should also validate xnames and return a 401 error if the xnames are not valid? I think returning 201 is misleading since it tells the client the request was successful processed (new entry created) but it is not.
Also, would OCHAMI support hostnames different than xnames? myabe this last question should added to the roadmap to discuss?

Example of a request with wrong mac addresses
curl --cacert cacert.pem -H "Authorization: Bearer $ACCESS_TOKEN" https://foobar.openchami.cluster:8443/boot/v1/bootparameters -d '{"hosts": ["x0c0s2b0n0", "x0c0s3b0n0"], "macs": ["00","a4","00"], "nids": [1, 2, 3], "params": "test", "kernel": "test", "initrd": "test", "cloud-init": {"user-data": {"foo": "bar"},"meta-data": {"foo": "bar"}}}'
{"type":"about:blank","title":"Bad Request","detail":"Bad Request: invalid MAC address format: 00\n","status":400}

I would assume a similar error message if xnames are not valid

We're having a separate discussion about supporting hostnames in https://github.com/OpenCHAMI/smd/issues/43. The architecture from the HPE code uses xname as the primary key for many operations in BSS as well as SMD.
Having said that, I don't think it's unreasonable to update BSS such that it validates the xnames when creating bootparameters.  I will propose a fix in a branch.


cupy[x].scatter_add vs numpy.add.at

Discussion from https://github.com/cupy/cupy/pull/846

I followed the convention of how cupy.scatter_add is exposed (scatter_add is cupy-specific and placed directly under cupy namespace), but as you pointed out, rsqrt seems to have relatively higher risk of future conflict than scatter_add.

Is there any difference between numpy.add.at and cupyx.scatter_add? If no, it can take it place to match numpy even better.

There should be no difference between two.
I'm not sure why this is commented out. cc/ @okuta?
https://github.com/cupy/cupy/pull/1247/commits/915b1c285da5804e57040d144026682a1ee0ef77#diff-bebe923819e806ae22e9923de58e954cL1597

Maybe, we don't have test about add.at .
You can add test and comment out that lines.

Implemented in #7077.


Update 19 - Pull request guidelines

I think a few screenshots of either past PRs or a fake one to illustrate what the rules mean could help.
Aside from that, LGTM.

Hmm, let me think what I can come up with.

Let me get this to staging for the next review.

@Kryptos-FR, I have listed some fake examples here https://stride-doc-staging.azurewebsites.net/latest/en/contributors/contribution-workflow/github-pull-request-guidelines.html#examples


PMS

Might be a bit tricky to do but it would be cool if it had PMS colours too to help print producers understand a digital palette.

Hey, @custa1200, thanks for the idea!
I don't find a lot of cases where Sketch is used for printing, do you? Maybe it could be an interesting approach for the next release.

The thing is, you can only aproximate the hex to PMS color value, am I right?...

Pantone requires a Pantone printed swatch book and eye matching. Pantone is a standardized color system and computer screens are not :/
This would not work really well and would cause a lot of color inconsistency.
Get a Pantone book and match the colors by eye (in the daylight).

On second thought it might be harder than thought. Might require a lookup/mapping from Pantone and no doubt licensing.
Sent from my iPhone

On 10 Jul 2016, at 3:29 AM, Adrián Rubio<EMAIL_ADDRESS>wrote:
The thing is, you can only aproximate the hex to PMS color value, am I right?...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Yep, looks a little too complex and outside the goals of this plugin. But thanks for the idea, keep them coming!
If you don't mind, I'm gonna close this Issue ;)


Use controlplane endpoint IPs outside DHCP ranges for e2e

Issue #, if available:
Description of changes:
Currently, the tests generate random IPs for cp endpoint within the entire subnet range, which can conflict with the DHCP range. This can result in a situation where the DHCP can assign the same IP to other machines which can cause problems.
In this PR, I'm restricting the CIDR range for generating random IPs to avoid conflicts with DHCP.
CIDR x.x.128.0/17 corresponds to IP range x.x.128.0-x.x.255.255 which is outside the DHCP ranges for both networks
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: abhinavmpandey08
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [abhinavmpandey08]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: abhinavmpandey08, g-gaston
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [abhinavmpandey08,g-gaston]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Corrected various async/await code issues

This PR removes various async/await keywords in places where they are not needed and unnecessary. This also fixes the exception propagation in those methods.
Tests are fixed to capture the proper exception types, instead of "aggregate" exceptions.
This code path is quite hot, therefore it is beneficial to fix these.

Thanks for the contribution! I expect to cut a release very shortly with this included.

:tada: This PR is included in version 6.7.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Note that session host with name ending with "-0" must always be running

If the the session host whose name ends with "-0" is not running then any new VMs added will not be registered as session hosts to the host pool.

@lintFan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Closing since I created a PR in the internal docs repo instead.


Cut a new release

Which version? 0.4.x? 1.0.0?
cf. https://github.com/projecthydra-labs/linked_vocabs/pull/17#issuecomment-290467071

I'd like to switch back to a tagged version for ADRL, so maybe let's go with 0.4.0 for now?


add issue 2

This pull request add instructions for issue 2, which is focused on using the snakemake python module to read in named variables from our Snakefile.
I also added some quotes to the Snakefile code snippets in issue 1.
Let me know what you think! Does this cover all the material we need to introduce the snakemake python module?

I thought all the suggestions you made were very helpful. I'll merge this request if you think it looks ok now!


Meteor user methods

[x] Meteor.logoutOtherClients
[ ] Meteor.loginWith

Closing this as loginWith[Provider] is discussed in the issue on final 1.0.0.


Add error responses in Challenges API Contracts

Fixes #66

Also fixed the linking issue for POST /challenge/subscribe section


Streamer Radio

Quoting discord.

I'm planning on making a radio feature in ansura. I'm not planning on making full-blown music features (Ansura isn't a multipurpose bot, but a bot geared towards gaming), but a radio, that anyone with a streamer role in a server %help ssr could do something like %streamradio (%sr?) and it'd pull songs from channels like https://www.youtube.com/channel/UC_aEa8K-EOJ3D6gOs7HcyNg to play in the background while streaming.

testing devlog webhook

cant decide if https://github.com/crazygmr101/AnsuraBot/blob/master/cogs/voice.py#L21 is a good enough fix tbh


Cannot build apps using FontSource

Describe the bug
Cannot build app
When using any @fontsource font in a barebones create-react-app, the app can be run via "npm start" and the font works as intended.
However, "npm build" fails with the following error chain:
Failed to compile.
HookWebpackError: Cannot read properties of undefined (reading 'e')
-- inner error --
TypeError: Cannot read properties of undefined (reading 'e')
Generated code for C:\Users\mikes\OneDrive\Documents\Napa\vinroom\my-app-js\node_modules\css-loader\dist\cjs.js??ruleSet[1].rules[1].oneOf[5].use[1]!C:\Users\mikes\OneDrive\Documents\Napa\vinroom\my-app-js\node_modules\postcss-loader\dist\cjs.js??ruleSet[1].rules[1].oneOf[5].use[2]!C:\Users\mikes\OneDrive\Documents\Napa\vinroom\my-app-js\node_modules\source-map-loader\dist\cjs.js!C:\Users\mikes\OneDrive\Documents\Napa\vinroom\my-app-js\src\App.css
 1 | __webpack_require__.r(__webpack_exports__);
 2 | /* harmony import */ var _node_modules_css_loader_dist_runtime_sourceMaps_js__WEBPACK_IMPORTED_MODULE_0__ = __webpack_require__("C:\\Users\\mikes\\OneDrive\\Documents\\Napa\\vinroom\\my-app-js\\node_modules\\babel-loader\\lib\\index.js??ruleSet[1].rules[1].oneOf[4]!C:\\Users\\mikes\\OneDrive\\Documents\\Napa\\vinroom\\my-app-js\\node_modules\\source-map-loader\\dist\\cjs.js!C:\\Users\\mikes\\OneDrive\\Documents\\Napa\\vinroom\\my-app-js\\node_modules\\css-loader\\dist\\runtime\\sourceMaps.js");
 3 | /* harmony import */ var _node_modules_css_loader_dist_runtime_sourceMaps_js__WEBPACK_IMPORTED_MODULE_0___default = /*#__PURE__*/__webpack_require__.n(_node_modules_css_loader_dist_runtime_sourceMaps_js__WEBPACK_IMPORTED_MODULE_0__);
 4 | /* harmony import */ var _node_modules_css_loader_dist_runtime_api_js__WEBPACK_IMPORTED_MODULE_1__ = __webpack_require__("C:\\Users\\mikes\\OneDrive\\Documents\\Napa\\vinroom\\my-app-js\\node_modules\\babel-loader\\lib\\index.js??ruleSet[1].rules[1].oneOf[4]!C:\\Users\\mikes\\OneDrive\\Documents\\Napa\\vinroom\\my-app-js\\node_modules\\source-map-loader\\dist\\cjs.js!C:\\Users\\mikes\\OneDrive\\Documents\\Napa\\vinroom\\my-app-js\\node_modules\\css-loader\\dist\\runtime\\api.js");
 5 | /* harmony import */ var _node_modules_css_loader_dist_runtime_api_js__WEBPACK_IMPORTED_MODULE_1___default = /*#__PURE__*/__webpack_require__.n(_node_modules_css_loader_dist_runtime_api_js__WEBPACK_IMPORTED_MODULE_1__);
 6 | // Imports
 7 |
 8 |
 9 | var ___CSS_LOADER_EXPORT___ = _node_modules_css_loader_dist_runtime_api_js__WEBPACK_IMPORTED_MODULE_1___default()((_node_modules_css_loader_dist_runtime_sourceMaps_js__WEBPACK_IMPORTED_MODULE_0___default()));
10 | // Module
11 | ___CSS_LOADER_EXPORT___.push([module.id, ".App {\n  text-align: center;\n}\n\n.App-logo {\n  height: 40vmin;\n  pointer-events: none;\n}\n\n@media (prefers-reduced-motion: no-preference) {\n  .App-logo {\n    -webkit-animation: App-logo-spin infinite 20s linear;\n            animation: App-logo-spin infinite 20s linear;\n  }\n}\n\n.App-header {\n  background-color: #282C34;\n  min-height: 100vh;\n  display: flex;\n  flex-direction: column;\n  align-items: center;\n  justify-content: center;\n  font-size: calc(10px + 2vmin);\n  color: white;\n}\n\n.App-link {\n  color: #61DAFB;\n}\n\n@-webkit-keyframes App-logo-spin {\n  from {\n    -webkit-transform: rotate(0deg);\n            transform: rotate(0deg);\n  }\n  to {\n    -webkit-transform: rotate(360deg);\n            transform: rotate(360deg);\n  }\n}\n\n@keyframes App-logo-spin {\n  from {\n    -webkit-transform: rotate(0deg);\n            transform: rotate(0deg);\n  }\n  to {\n    -webkit-transform: rotate(360deg);\n            transform: rotate(360deg);\n  }\n}\n", "",{"version":3,"sources":["webpack://./src/App.css"],"names":[],"mappings":"AAAA;EACE,kBAAkB;AACpB;;AAEA;EACE,cAAc;EACd,oBAAoB;AACtB;;AAEA;EACE;IACE,oDAA4C;YAA5C,4CAA4C;EAC9C;AACF;;AAEA;EACE,yBAAyB;EACzB,iBAAiB;EACjB,aAAa;EACb,sBAAsB;EACtB,mBAAmB;EACnB,uBAAuB;EACvB,6BAA6B;EAC7B,YAAY;AACd;;AAEA;EACE,cAAc;AAChB;;AAEA;EACE;IACE,+BAAuB;YAAvB,uBAAuB;EACzB;EACA;IACE,iCAAyB;YAAzB,yBAAyB;EAC3B;AACF;;AAPA;EACE;IACE,+BAAuB;YAAvB,uBAAuB;EACzB;EACA;IACE,iCAAyB;YAAzB,yBAAyB;EAC3B;AACF","sourcesContent":[".App {\n  text-align: center;\n}\n\n.App-logo {\n  height: 40vmin;\n  pointer-events: none;\n}\n\n@media (prefers-reduced-motion: no-preference) {\n  .App-logo {\n    animation: App-logo-spin infinite 20s linear;\n  }\n}\n\n.App-header {\n  background-color: #282C34;\n  min-height: 100vh;\n  display: flex;\n  flex-direction: column;\n  align-items: center;\n  justify-content: center;\n  font-size: calc(10px + 2vmin);\n  color: white;\n}\n\n.App-link {\n  color: #61DAFB;\n}\n\n@keyframes App-logo-spin {\n  from {\n    transform: rotate(0deg);\n  }\n  to {\n    transform: rotate(360deg);\n  }\n}\n"],"sourceRoot":""}]);
12 | // Exports
13 | ___CSS_LOADER_EXPORT___.locals = {};
14 | /* harmony default export */ __webpack_exports__.d.e.f.a.u.l.t = (___CSS_LOADER_EXPORT___);
15 |

Steps to Reproduce

npx create-react-app test-app
cd test-app
npm install @fontsource/alegreya
npm run build

Expected behavior
No response
Version
No response
OS
No response
Browser
No response
Additional context
No response

I also just hit this issue. It seems like the issue just started happening today.

Fontsource hasn't pushed any updates for these fonts in a while. We've been on a freeze while we wrap up #590.
I wonder if Webpack may be the issue here. Have you tried downgrading recent Webpack or CSS Loader versions?

https://github.com/webpack/webpack/releases/tag/v5.83.1 - Seems like a fix has already been pushed. Please try the latest version of Webpack.

Can confirm that this is fixed with the latest webpack. Looks like it was issue https://github.com/webpack/webpack/issues/17213
You can also downgrade to 5.82.1 if needed:
Add in the package.json
"overrides": {
   "webpack":"5.82.1"
},
"resolutions": {
   "webpack":"5.82.1"
}

That fix works for now, thank you. Changing the webpack version resolved it, and thankfully didn't affect the project as far as I can tell.


How to update to a certain version?

I think I'm in need of v1.6.3 for the bug fix for Scene Recall. How does this work? Can I manually import this module on my PC? Or how can I find out in which Companion release it is included?

You can download the latest build at discourse.checkcheckonetwo.com
It may be a while before it’s added to an official release as I need to be sure there’s no new bugs.

Ah, it seems I have to register and gain some level to download. Let me try that out. Thanks!

https://i.kym-cdn.com/photos/images/newsfeed/001/653/546/4b2.jpg


[enhancement] Generating sourcemap via magic-string triples memory usage in most applications

See: https://github.com/rollup/plugins/issues/1064
@Rich-Harris is there any chance we can improve memory management in the sourcemap generation?

Maybe related: https://github.com/Rich-Harris/magic-string/issues/177


instantiate proposal was bad: Error: REQUEST_TIMEOUT

Context
Env:
2 orgs, each org has 2 peers
Steps:
Execute command "node benchmark/simple/main.js -n /home/yzapps/hyperledger/yingzi/caliper/network/fabric-v1.4-yingzi/2org2peercouchdb/fabric-node.json"
note:1.omit "-c" parameter, which means using the default "config-linear-rate.yaml" as the benchmark config file
2.The content of used fabric-node.json is as following:
fabric-node.zip
Expected Behavior
The benchmark test ran successfully and report was generated normally.
Actual Behavior
"instantiate proposal was bad: Error: REQUEST_TIMEOUT" error happened. The detailed log is attached:
benchmark_log.zip
Could you please help me figure out what is wrong here? Thank you.

@houqinghui qinghui, could you help? Thanks.

I noticed that even though the benchmark test failed, "marbles" chaincode was actually successfully instantiated in the peer:

So I am curious that why the error log also shows "warn: [e2eUtils.js]: instantiate proposal was bad: Error: REQUEST_TIMEOUT"?
Besides, I noticed that in default "config-linear-rate.yaml", actually two chaincodes are configured:
1.marbles
2.simple
So I wonder whether the error log means that "simple" chaincode was not successfully instantiated?

And I checked the docker container. Both "marbles" and "simple" chaincodes' containers are started and running:

Does docker container running means the instantiation of chaincodes is successful? Thanks.

After I remove "simple" chaincode from network config file, the issue disappeared. It seems that the instantiation of "marbles" chaincode was successful. But another error happened. And I will create another issue to track the new error. I will close this issue now.


Upgraded to Version 0.2.3-beta and lost motion binary sensors

just upgraded to the beta. everything went fine.  the new config is nice. motion sensor binary sensors and their battery sensors were missing though

@pdobrien3  I deliberately blocked those in this release. The integration doesn't get instant feedback from Alarm.com -- by default, it only checks for updates once a minute -- so I didn't think that anyone would be able to use them reliably. Do you use motion sensors in automations? Happy to add them back in.

No. That makes perfect sense. I added the motions just because they were there. While the actual binary sensors were not beneficial, the malfunction and battery ones were a welcome addition. Would it make sense to just add those back?

Interesting, that's a good idea. That'll take a bit more work, though, than adding it all back, so I'll keep this open for a future release. Thanks for the feedback!

thank you for what you are doing. also, i have a SMKTX-345 smoke detector. the high heat and smoke seem to properly report.  the battery and malfunction seem to work fine for the freeze alarm but binary_sensor.freeze_alarm reports as unknown. in prior releases it reported malfunction i think. should i make another issue or this is good?

@Valdorama My concern is that Home Assistant will never see an motion event and will therefore always mark a room as unoccupied. As an example, if a motion sensor enters a "detected" state for 5 seconds after being triggered and this integration only polls for updates once every 60 seconds, odds are that you'll never receive the trigger event. Can you tell me for how long a motion sensor reports as active after being tripped?
@pdobrien3 What's your level of technical skill? Are you comfortable downloading a Python library using pip and using the command line?

Can you tell me for how long a motion sensor reports as active after being tripped?

@elahd The motion sensors generally stay active for a while. In my experience, it seems to stay on for at least 30 minutes.

@AritroSaha10 @Valdorama Thanks. Back in it goes. I'll push another beta update later today.
@pdobrien3 No need to mess with your Home Assistant server. You can do this on your laptop/desktop.

Install python>3.9.
Open a command prompt and install pip by entering python -m ensurepip --upgrade on Mac or py -m ensurepip --upgrade on Windows.
Install pyalarmdotcomajax (the library that powers this integration) via pip: pip install pyalarmdotcomajax
Run adc -u YOUR_USERNAME -p YOUR_PASSWORD -v. Use quotation marks around your password if it contains special characters. Enter your OTP when prompted.
The CLI will return a dump of raw data organized by device type. Copy the entire JSON object in the ====[SENSORS]==== section into a JSON formatter, like jsonformatter.org.
Search for the freeze sensor object in the formatted output. (Just Ctrl+F for whatever you named the sensor on Alarm.com.) Post the sensor's JSON object here, but be sure to redact the sensor id field, any id fields in the relationships object, and the sensor's description field, if you care. You should be posting something that looks like this:

    {
      "id": "XXXXX",
      "type": "devices/sensor",
      "attributes": {
        "deviceType": 5,
        "openClosedStatus": 2,
        "state": 1,
        "isFlexIO": false,
        "deviceRole": 0,
        "displayStateText": "Not Reset",
        "isMonitoringEnabled": false,
        "sensorNamingFormat": 3,
        "managedDeviceType": 2,
        "hasState": false,
        "canBeRenamed": true,
        "canBeDeleted": false,
        "canAccessWebSettings": true,
        "canAccessAppSettings": false,
        "webSettings": 400,
        "canAccessTroubleshootingWizard": false,
        "troubleshootingWizard": null,
        "macAddress": "",
        "manufacturer": "",
        "isOAuth": false,
        "isZWave": false,
        "supportsCommandClassBasic": false,
        "isMalfunctioning": false,
        "canBeSaved": true,
        "canChangeDescription": true,
        "description": "Interconnected Smoke Detectors",
        "deviceModelId": 114,
        "canConfirmStateChange": true,
        "canReceiveCommands": false,
        "remoteCommandsEnabled": true,
        "hasPermissionToChangeState": true,
        "deviceIcon": {
          "icon": 218
        },
        "batteryLevelNull": null,
        "lowBattery": false,
        "criticalBattery": false,
        "canBeLinkedToVideoDevice": false,
        "videoDeviceLinkDeviceIds": []
      },
      "relationships": {
        "system": {
          "data": {
            "id": "XXXXX",
            "type": "systems/system"
          }
        },
        "stateInfo": {
          "data": null
        }
      }
    },

Thanks!

Looks easy enough. Hopefully I can take a shot at it on Friday or Saturday. Thanks.

Motion sensors restored in v0.2.3-beta.2.

So I worked through the steps this am.  A couple questions, if you don't mind, from a beginner.  Do you typically run the python commands from the python program itself, a command prompt, or secure shell?  Do you some how create a venv (running in windows) or just bring up a prompt and start working?
Also, I noticed this for my freeze part of the smoke detector:
"isMonitoringEnabled": false,
I logged into alarm.com and noticed that all three parts of the smoke detector, along with the firefighter, show up as N/A under device/monitoring but the only sensor that doesn't look like it is working is the freeze alarm from the smoke detector. When i get a minute I need to check "isMonitoringEnabled" on the other three sensors.
Also, I upgraded to beta 2 and all motions are back.

{
"id":,
"type": "devices/sensor",
"attributes": {
"deviceType": 8,
"openClosedStatus": 0,
"state": 0,
"isFlexIO": false,
"deviceRole": 0,
"displayStateText": "Status Unknown",
"isMonitoringEnabled": false,
"sensorNamingFormat": 3,
"managedDeviceType": 2,
"hasState": true,
"canBeRenamed": true,
"canBeDeleted": false,
"canAccessWebSettings": true,
"canAccessAppSettings": false,
"webSettings": 400,
"canAccessTroubleshootingWizard": false,
"troubleshootingWizard": null,
"macAddress": "",
"manufacturer": "",
"isOAuth": false,
"isZWave": false,
"supportsCommandClassBasic": false,
"isMalfunctioning": false,
"canBeSaved": true,
"canChangeDescription": true,
"description":
"deviceModelId": 117,
"canConfirmStateChange": true,
"canReceiveCommands": false,
"remoteCommandsEnabled": true,
"hasPermissionToChangeState": true,
"deviceIcon": {
"icon": 317
},
"batteryLevelNull": null,
"lowBattery": false,
"criticalBattery": false,
"canBeLinkedToVideoDevice": false,
"videoDeviceLinkDeviceIds": []
},
"relationships": {
"system": {
"data": {
"id": ,
"type":
}
},
"stateInfo": {
"data": null
}
}
},

Thanks, @pdobrien3. Take a look at my answer to another issue here. It may be possible that you don't have monitoring enabled for these sensors in the UI.
Also, would you mind updating to v0.2.3-beta.3 to test freeze sensors?

Right, but where the checkboxes is under devices, says N/A. I have gotten a response from my monitoring company. They said those devices are security devices  bs sensor devices
That section in Alarm.com is referencing sensor activity monitoring, not alarm monitoring. Life safety devices are either in alarm status or at rest, they are not eligible for sensor activity monitoring like door window sensors or motion detectors.
off to check beta 3 now

That's weird. This may be specific to your provider. "state": 0 maps to "unknown." Does the sensor at least show up in Home Assistant as a cold sensor in beta 3?x
I don't have any freeze sensors, but my CO and smoke detectors return state (see what I pasted in an earlier post).
They show up on the ADC website as:

Yes, it has always shown up as a freeze alarm.  I think the icon changed.  What is odd to me is that the smoke, high heat, and freeze are all one device.  The smoke and high heat seem to have a state but the freeze does not.
Have you seen if any of your alarm monitoring devices will actually change state?  According to my provider, anything with an N/A under monitoring is not meant to be monitored like a sensor although they did say battery and malfunction state was monitored. I have a firefighter that is listed as N/A. I may see if I can get the state on it to change this weekend.

Also, I was seeing multiple adc login attempts to update errors that have vanished. Not sure it that is something with the recent beta or just something on my network that has improved.
Also, I have been on a 15 sec scan interval for some time now without any issues.

Have you seen if any of your alarm monitoring devices will actually change state?

I haven't actually tested this. I can try next week. Let me know what you find on your end.

Also, I was seeing multiple adc login attempts to update errors that have vanished.

That's great. Were you seeing the errors on the ADC website or in Home Assistant?

Just a heads up.  I was planning on testing some of the security sensors today.  Before I did, I tested scan interval.  It didnt seem to make a difference if it was set to 15, 30 or 60 seconds.  I had response times from 45 seconds all the way to 1:45.  the 45 seconds was obtained when scan interval was set to 60 seconds.

Thanks! Fixed in v0.2.5.


Frontend entry point redirect (implicit port)

What does this PR do?
Turn implicit port to explicit port when evaluate the redirection.
Motivation
Fixes #2925
More

[ ] Added/updated tests

Additional Notes
The current behavior when a redirection is define from an entry point on port 80 to an entry point on 443:
http://foo:80 -> https://foo:433 -> https://foo -> https://foo:443 -> https://foo -> ...

The redirection cycle is due to the fact that 443 is an implicit port for TLS.

Not the good way. I close.


Unable to decrypt data on 3rd party wallets/providers

Cannot import keystore wallet anywhere else except for internal use with web3swift.
Using the following piece of code to generate a keystore/json wallet using { password: 'Lekker@123' }:
  @objc func getKeystore(_ password: String, callback: @escaping RCTResponseSenderBlock) -> Void {
    let keystore = try! EthereumKeystoreV3(password: password)!
    let keystoreSerialize = try! keystore.serialize()! as Data
    let JSONString = String(data: keystoreSerialize, encoding: String.Encoding.utf8)
    print("JSONString: ", JSONString as Any)
       callback([NSNull(), [
         "keystore": JSONString
       ]])
  }

produces the following json shape:
{
  "isHDWallet": false,
  "id": "ef5041dc-3adc-49eb-bd4b-69bd22fcf04f",
  "crypto": {
    "ciphertext": "f9f3151306285df30a6522557d8fae968bd2dccbf79b1234b9051e781f9f83cd",
    "cipherparams": {"iv": "0906993954cc7c11b5b84fe66421c022"},
    "kdf": "scrypt",
    "kdfparams": {
      "r": 6,
      "p": 1,
      "n": 4096,
      "dklen": 32,
      "salt": "1c935393b1c3a846e300c36a7d871d3bb2b5215f4bd33eb7d6f80da2264cac06"
    },
    "mac": "bfa8ecf765b296f8e150c0facda5f432921009c2abc92c0a426a1b019f5e657d",
    "cipher": "aes-128-cbc"
  },
  "address": "0x6db8115459ffdda63ed1f6f053c9c78b56d2926c",
  "version": 3
}

internally i can run:
    let pkData = try! keystoreManager.UNSAFE_getPrivateKeyData(password: password, account: ethereumAddress).toHexString()

to get the private key.
But on 3rd party websites like https://www.myetherwallet.com/wallet/access/software?type=keystore it produces errors "unable to decrypt data":

using ethers.js with { password: 'Lekker@123' } however creates a keystore/json wallet i can use anywhere on any platform:
{
  "address": "fd2cc291ea825c7e5356802ccbe64a3d0db8f926",
  "id": "3c250cc4-9dd7-40d8-a467-ada351494761",
  "version": 3,
  "Crypto": {
    "cipher": "aes-128-ctr",
    "cipherparams": {"iv": "1e80d5f0fdef982f32f654d69b0932ac"},
    "ciphertext": "2de8453d78026ef9141ddb7eee0b258fb74fead42cb9e63db21820c0f655de07",
    "kdf": "scrypt",
    "kdfparams": {
      "salt": "20ae4e4c50735d0b18eba633aaf06e4c3095b050e947348d1008aa9b43df2652",
      "n": 131072,
      "dklen": 32,
      "p": 1,
      "r": 8
    },
    "mac": "a1541056b3feec4c203004ab1d34f20181b70d98c5b8513e4ce8429b52bd49d7"
  },
  "x-ethers": {
    "client": "ethers.js",
    "gethFilename": "UTC--2022-03-08T12-01-19.0Z--fd2cc291ea825c7e5356802ccbe64a3d0db8f926",
    "mnemonicCounter": "ec79810275faebf9d68309ffb33a4b2e",
    "mnemonicCiphertext": "b2b096c72e01e17c293558a8298f0f16",
    "path": "m/44'/60'/0'/0/0",
    "locale": "en",
    "version": "0.1"
  }
}

ethers.js ads x-ethers key but web3.js does not, so i dont think it has to do with that. here is a sample of web3 keystore (not sure what the password for this was but i know it worked once upon a time, maybe { password: lekker123|password1 }):

Please can anyone assist with this issue or help me understand what is going on?

Cannot import keystore wallet anywhere else except for internal use with web3swift too.
other wallets keystore also cannot use in web3swift wallet.
let dataKey: Data = keyStoreStr.data(using: .utf8)
let keystore = EthereumKeystoreV3(dataKey)
keystore is nil
code in web3swift  KeystoreParams
public struct KeystoreParamsV3: AbstractKeystoreParams {
public var crypto: CryptoParamsV3
public var id: String?
public var version: Int
public var isHDWallet: Bool // other wallets keystore not have， I use CodingKeys fix，But I don't know if it will cause other problems
var address: String?
public init(address ad: String?, crypto cr: CryptoParamsV3, id i: String, version ver: Int) {
    address = ad
    self.crypto = cr
    self.id = i
    self.version = ver
    self.isHDWallet = false
}

}


test: Retry flakes one more time

@rhatdan @haircommander @umohnani8 ptal.
Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

LGTM

Link to k8s code that consumes this - https://github.com/kubernetes/kubernetes/blob/master/hack/ginkgo-e2e.sh#L130

@cevich The tests passed here but gathering facts is just stuck - https://ci.openshift.redhat.com/jenkins/job/test_pull_request_crio_e2e_rhel/2093/console

/test e2e_rhel

LGTM

@mrunalp it's been a long while since I looked at the automation behind this.  IIRC gathering logs/results is dependent on the test-subject being responsive.  Unfortunately that makes it really hard to diagnose the cause of an unresponsive system.  If the issue is reproducible, someone would need to manually run and monitor the reproducer. The only other option is testing likely theories behind the "hang", and instrumenting automation to gather logs before it occurs (to prove the theory).  Neither prospect sounds easy or quick :cry:


doc update

Thank you for your pull request but photo-gallery-icon is some kind of private element for photo-gallery so I don't want to document it, just want to keep it clean. Thanks again


Set TLS config in the client policy

Codecov Report
Attention: 81 lines in your changes are missing coverage. Please review.

Comparison is base (156a41a) 26.90% compared to head (654aedc) 25.70%.
Report is 3 commits behind head on main.

Files
Patch %
Lines

pkg/model/aerospike_cluster.go
0.00%
81 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #138      +/-   ##
==========================================
- Coverage   26.90%   25.70%   -1.21%
==========================================
  Files          35       35
  Lines        1613     1700      +87
==========================================
+ Hits          434      437       +3
- Misses       1121     1204      +83
- Partials       58       59       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Autosuggest eats buffer by ctrl+w

Given command: echo first second
I want to cut two words first second by typing CTRL+WW .
But then when I try to paste it with CTRL+Y I'm getting only one word: first.
I'm using oh-my-zsh:
plugins=(aws backup git extract knife knife_ssh mercurial mvn vagrant bundler gem rake rvm thor debian sudo kitchen docker-compose emacs berkshelf power-save terraform systemd zsh-autosuggestions)

I pushed a failing spec to fixes/kill-multiple-words
multiple words killed with `backward-kill-word`
  can be yanked back with `yank` (FAILED - 1)

Failures:

  1) multiple words killed with `backward-kill-word` can be yanked back with `yank`
     Failure/Error: wait_for { session.content }.to eq('echo first second')

       expected: "echo first second"
            got: "echo first"

       (compared using ==)
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait/handler.rb:13:in `block (2 levels) in handle_matcher'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait/handler.rb:10:in `loop'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait/handler.rb:10:in `block in handle_matcher'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait/handler.rb:9:in `handle_matcher'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait/target.rb:30:in `block in to'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait/target.rb:44:in `block in with_wait'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:28:in `with_wait'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait/target.rb:44:in `with_wait'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait/target.rb:30:in `to'
     # ./spec/integrations/kill_word_spec.rb:12:in `block (2 levels) in <top (required)>'
     # ./spec/spec_helper.rb:19:in `block (2 levels) in <top (required)>'
     # /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait.rb:46:in `block (2 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Timeout::Error:
     #   execution expired
     #   /usr/local/bundle/gems/rspec-wait-0.0.9/lib/rspec/wait/handler.rb:16:in `sleep'

Finished in 2.15 seconds (files took 0.24763 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/integrations/kill_word_spec.rb:10 # multiple words killed with `backward-kill-word` can be yanked back with `yank`

Looks like this behavior can be reproduced by simply wrapping backward-kill-word in a user-defined widget.
% my-backward-kill-word() { zle backward-kill-word }
% zle -N my-backward-kill-word
% bindkey ^W my-backward-kill-word

The functionality where cut text is concatenated to be yanked in combined form later seems to be dependent on the two cutting widgets running one directly after the other.
Some interesting places in the upstream code:

The backward-kill-word has flag ZLE_KILL which flags it as a "kill" type command.
There's functionality here that checks if the last widget executed has the ZLE_KILL flag set. If it doesn't, it will start a new buffer and thus not concatenate the text cut this time with the text cut last time.
lastcmd flags are reset to zero here when the user-defined widget finishes running.

So the flow when using my-backward-kill-word twice is something like:

backward-kill-word built in finishes: from now on lastcmd was a kill command
my-backward-kill-word widget finishes: from now on lastcmd was not a kill command
backward-kill-word built in finishes: from now on lastcmd was a kill command
my-backward-kill-word widget finishes: from now on lastcmd was not a kill command

Because the kill commands aren't coming one after another, the text is not concatenated for yanking.
Compare with the flow when using built-in backward-kill-word:

backward-kill-word built in finishes: from now on lastcmd was a kill command
backward-kill-word built in finishes: from now on lastcmd was a kill command

Not sure how this could be fixed. Next step is probably an email to the mailing list.

Also found this related issue in zsh-syntax-highlighting: https://github.com/zsh-users/zsh-syntax-highlighting/issues/150
Looks like it hasn't been merged yet, but there's a commit https://github.com/danielshahaf/zsh-syntax-highlighting/commit/bfa71c983fa6c3b43cc657276223410123d5c145 that uses zle -f (only available in zsh >=5.2) to set the "kill" flag on the user-defined widgets wrapping the builtin kill widgets.

Here is a patch based on @ericfreese comment and the solution he has linked
zsh-autosuggestions.patch.txt

I ran into this issue on and @ericfreese's hack worked for me. Would be great to get a long term fix for this merged in. Thanks for all of the great work on this plugin!

The issue with the proposed workaround is that it leaves the suggestion while this is not valid.
@macdems Maybe you could start a pull request with your suggestion? I think you need to somehow put the list of widgets into a specific variable, like this is done for  ZSH_AUTOSUGGEST_IGNORE_WIDGETS. If you don't have time, I can do that for you.

@vincentbernat I can do this, but next week the earliest (no I am almost fully offline with no access to any computer).

I have created a pull request. In my system yanking does not leave the suggestion, so it also seems to solve #526.

I have created a pull request. In my system yanking does not leave the suggestion, so it also seems to solve #526.

I tried applying this patch on top of upstream.
Ctrl-w Ctrl-y is still broken for me after that.

Has anyone gotten the normal behavior of select-word-style bash to actually work while zsh-autosuggestions is enabled?
I've been seeing broken behavior where Ctrl+w will gobble up the entire line always into the cut buffer, no matter that WORDCHARS had been set to (e.g. so as to not include spaces).  Then Ctrl+y shows what is there by "yanking" (pasting) that entire line out, not just the last word.  When I use the ZSH_AUTOSUGGEST_IGNORE_WIDGETS workaround, and disable select-word-style bash, then normal Zsh behavior for backward-kill-word is restored where one word at a time can be deleted backwards via Ctrl+w, then pasted back with Ctrl+y. Yet, then I can't set it up like bash word behavior because Zsh defaults to not include / and ' separators as "words".
I've tried out the change in PR #551, but behavior is still the same unless I add backward-kill-word, and backward-kill-word-match to the ZSH_AUTOSUGGEST_IGNORE_WIDGETS array, and disable select-word-style bash entirely.  So my choices seem to be: use zsh-autosuggestions but be forced to have Zsh default Ctrl+w word behavior, OR disable zsh-autosuggestions and then get select-word-style bash behavior working.
The only way I've been able to get normal select-word-style bash behavior is to not load zsh-autosuggestions plugin at all! 🤷

@trinitronx I just tried out PR #551 with zsh 5.9 and it works for me, though it also need a little fix for yank-pop as noted by @vincentbernat which I've added in another PR #795


Don't sanity check val phase if val set not present

close #654

Oops, that's probably coming from https://github.com/NVIDIA/DIGITS/pull/622 - my bad!


Attempt to Improve the Performance of Building Dictionaries

Pull request
Issue tracker
Fixes will automatically close the related issue
Fixes # N/A
Feature
Describe feature of pull request
This PR is a attempt to improve the performance of building dictionaries. By replacing some types or methods with more suitable ones, the speed of building dictionaries will get faster.
Unit test

[x] Done

Manual test

[x] Done

Code Review

Unit and manual test pass
GitHub Action CI pass
At least one contributor reviews and votes
Can be merged clean without conflicts
PR will be merged by rebase upstream base

Additional Info
In my test results, the speed of building dictionaries has been improved by 20-30% after improvement.
Used configurations to test: https://github.com/iDvel/rime-ice
Profiler test results are showed below:
Before

After

Thanks for the pull request. Good job.
I'll take a closer look in the hash_map cases, making sure turning them to unordered map does not affect the result.


[921] Add Publications::StatusTotalsComponent

Context
Due to the release of continuous applications, we are redesigning the monthly statistics report. This PR creates a StatusTotalsComponent which will be used to display status, summary, and figures from both cycles.
Changes proposed in this pull request

Create a StatusTotalsComponent.

Screenshot
Guidance to review

Link to Trello card

Things to check

[ ] If the code removes any existing feature flags, a data migration has also been added to delete the entry from the database
[ ] This code does not rely on migrations in the same Pull Request
[ ] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[ ] If this code adds a column to the DB, decide whether it needs to be in analytics yml file or analytics blocklist
[ ] API release notes have been updated if necessary
[ ] If it adds a significant user-facing change, is it documented in the CHANGELOG?
[ ] Required environment variables have been updated added to the Azure KeyVault

 Monthly statistics: FE: Application Status Totals Component


Various bug fixes

Addresses:
https://github.com/rancher/rancher/issues/1702
and https://github.com/rancher/rancher/issues/1815
and partially: https://github.com/rancher/rancher/issues/1741. I say partially because it will address the symptom explained in that issue (containers showing up as stopped vs deleted), but it won't address why containers' delete events are getting missed during validation tests.

I believe @alena1108 has an official trademark on "various bug fixes"  You will need to rename the PR.

You previous version failed on the build at the same place.  Do you think it's related to the change?

Wow, have I become numb to legitimate build failures?


feat(Algebra/Group/Pointwise/Set/Basic): sInter and sUnion forms of pointwise operations

Provides sInter and sUnion versions of  pointwise algebraic operations on sets.
Needed in #17029

Thanks!
bors merge


An old version of django-mptt is pinned, breaking 1.8 support. The newest django-mptt supports Django 1.8 but filer insists on an older version.

django-filer requires django-mptt<=0.6.2, a version that doesn't support Django 1.8, despite a newer version of django-mptt that does support it being available. Why does filer require an old version of mptt?

mptt has a long history of breaking compatibility (for example mptt >=0.7 breaks django CMS 3.0) and as Django 1.8 support is still not available in filer, we usually are very conservative in supported mptt versions.
We're planning to add Django 1.8 support in the next weeks which declare support for mptt >= 0.7


⚠ ClamAV has degraded performance

In 83b0bcd, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 179 ms

Resolved: ClamAV performance has improved in f7f73eb after 5 minutes.


Ability to handle uploaded files

Q
A

Is bugfix?
❌

New feature?
✔

Breaks BC?
❌

Fixed issues

Code from yii-demo
 public function contact(
        ValidatorInterface $validator,
        ServerRequestInterface $request
    ): ResponseInterface {
        $body = $request->getParsedBody();
        $form = new ContactForm();
        if (($request->getMethod() === Method::POST) && $form->load((array)$body) && $validator
                ->validate($form)
                ->isValid()) {
        $this->mailer->send($form, $request); // <<--- here checking uploaded files :(
        //...

Code from Yii2 doc

if (Yii::$app->request->isPost && $model->load(Yii::$app->request->post()) {
            $model->imageFile = UploadedFile::getInstance($model, 'imageFile');
            if ($model->upload()) { // << -- here validate :(
                // file is uploaded successfully
                return;
            }
        }
         //...

New approach

final class FilesForm extends FormModel
{
    public function __construct(
        public ?string $name = null,
        public Files $avatars = new Files([]),
        public Files $images = new Files([]),
        public Files $photos =new Files([])
    ) {
        parent::__construct();
    }
}

The most common cases in controller
public function contact(FilesFormRequest $request): ResponseInterface
{
    if ($request->serverRequest()->hasHeader('Content-Type') && $request->isValid()) {
        $this->mailer->send($request->formModel());

        return $this->responseFactory
            ->createResponse()
            ->withHeader(Header::LOCATION, $this->url->generate('site/contact'));
    }

    return $this->viewRenderer->render('form', ['form' => $request->formModel()]);
}

Or using handleRequest for upload data and files and using of desired form name
public function contact(
        ValidatorInterface $validator,
        ServerRequestInterface $request
    ): ResponseInterface {
        $form = new ContactForm();
        if ($request->hasHeader('Content-Type') && $form->handleRequest($request, 'myform') && $validator
                ->validate($form)
                ->isValid()) {
            $this->mailer->send($form, $request);

            return $this->responseFactory
                ->createResponse(Status::OK)
                ->withHeader(Header::LOCATION, $this->url->generate('site/contact'));
        }

        return $this->viewRenderer->render('form', ['form' => $form]);
    }

New features:

Files - the collection of upload files. Type of files for using in validations.
FormModel::handleRequest() - uploads files and data in form model
FormRequest - for using in most common cases

Why need FormRequest class? We don't can resolve him from container.
Seems, for use in controller we need helper only that prepare data from request.
public function myAction(ServerRequestInterface $request) {
  $form = new MyForm();
  if (
      $request->getMethod() === Method::POST
      && $form->load(RequestHelper::prepareData($request))
      && $this->validator->validate($form)->isValid()
  ) {
    ...
  }
  ...

RequestHelper::prepareData should support several strategy (maybe second parameter will be define strategy of data preparing). Need to think about implementation.

Use Yiisoft\Input\Http\Attribute\Parameter\UploadedFiles isntead of.


Fix column null migration

Provide a default value when making created_at column non-null and then populate created_at based on existing updated_at data.

Coverage remained the same at 92.952% when pulling 3e4762e8b8c06b6a751953d24b588dd8bf8b405d on fix-column-null-migration into 9dcc23b35b81e5d3ce970f8382761111785d89b5 on master.

Thanks Nathan. I was just about to hit the Merge button.


Why use this over tauri-plugin-sql?

What are the pros/cons of using this plugin vs tauri-plugin-sql with the sqlite driver?
Sorry if it's obvious, but it wasn't for me :)

I wasn't able to change file paths in tauri-plugin-sql. It was the deal breaker for me.


Put stress on the important note

Write out does not (versus doesn't) in:
(i) Important
Azure NetApp Files availability zone volume placement provides zonal placement. It does not provide proximity placement towards compute. As such, it does not provide lowest latency guarantee. VM-to-storage latencies are within the availability zone latency envelopes.

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

ID: cc1d501f-9474-0d82-da86-a265a9235e7f
Version Independent ID: 17d0d9e4-bf21-8d3e-4714-e8401cd41fe4
Content: Use availability zones for high availability in Azure NetApp Files
Content Source: articles/azure-netapp-files/use-availability-zones.md
Service: azure-netapp-files
GitHub Login: @b-hchen
Microsoft Alias: anfdocs

@gvanteylingen
Thanks for your feedback! We will investigate and update as appropriate.

Thanks @gvanteylingen - stress has been added in Use availability zones for high availability in Azure NetApp Files
#please-close


[CLI]: wandb backend process has shtdown

Describe the bug

Additional Files
No response
Environment
WandB version:
OS:
Python version:
Versions of relevant libraries:
Additional Context
No response

Hi. I ran xceptiontrain training data images for a training the neural system. The process crashed with error message: wandb backend process has shut down. Can anybody kindly inform me what can be done? Thank you

Dear Madam. Where in the program can I find the variable? Unable to find it. The runtime error I recieved was: couldn't open file mapping <torch_13560_2515634867>, error code <1455>. Can't procure more data and debug logs, as I am running the program again, and the debug data is lost currently. I was told that it ran out of memory due to a bug in the program which caused memory over consumption. each epoch run yields the weights and biases. There are an 100 epochs to be run. But the running always stops after epoch 84 and never gets to epoch 100. some unnecessary data is eating up the memory. Thank you very much for your help and very much appreciated kind efforts.


Url escape configurable

🚀 Feature Request
Relevant Package [REQUIRED]

 This feature request is for core services and device service
Description [REQUIRED]
The Url escape function should be configurable.

Add config for all services, default is false,

all-services:
    Service:
        EnableURLEscape: false

Skip the escape function if EnableURLEscape is false

Refer to https://github.com/edgexfoundry/edgex-go/issues/4053

rename to EnableNameFieldEscape and add the following comments
`// The name field escape could allow the system to use special or Chinese characters in the different name fields, including device, profile, and so on.  If the EnableNameFieldEscape is false, some special characters might cause system error.


Perform some search engine optimization for docs

Currently the documentation is hard to find on engines like google, duckgosearch, bing etc.
One has to enforce the inclusion of the term "weldx" by using quotation marks. Eventually we should somehow highlight this more.

cref #307

It seems the version number is currently not avail on RTD although the package gets installed.

good catch, I wonder why this happens..

It seems the version number is currently not avail on RTD although the package gets installed.

I one way would be to just include setuptools_scm in the docs requirement and directly run
from setuptools_scm import get_version
version = get_version(root='..', relative_to=__file__)

in conf.py

This is a good solution. Thanks!

Hold on, do we have setuptools_scm installed on RTD?

I think it arises from having weldx always imported from the sources root (where the version is undefined; it only gets defined during pip install).

I think it arises from having weldx always imported from the sources root (where the version is undefined; it only gets defined during pip install).

Ah yes that might be it. Probably because RTD doesn't pip install -e ., otherwise the version.py file would be created in the source install
see https://github.com/readthedocs/readthedocs.org/pull/4960
How about
try:
    import weldx
except ModuleNotFoundError: # fallback for local use
    sys.path.insert(0, os.path.abspath("../"))
    import weldx
except Exception as ex:
    raise

looking good https://github.com/BAMWelDX/weldx/pull/310


Add Stability Index on API

http://nodejs.org/api/documentation.html#documentation_stability_index

Not relevant anymore, closing it.


A typo in parameter.md

The last word "nrees" at L99 is a typo.
https://github.com/dmlc/xgboost/blame/24c2e41287d7fb73f99fe5e71eca1eb456a553ba/doc/parameter.md#L99

Thanks for your feedback. I've filed a PR to address it.


New Website Logo: ubet.com

Name: UBET
Homepage: http://ubet.com
Logo: http://s12.postimg.org/gy9u95bwt/ubet_mainlogo_dark.png
On a personal note, I would like to offer a special thanks to the TypeScript team.
The ubet.com team were early adopters using it in a large team on a large project and although we had some early problems with limited tool support and a mixed view from the team on whether the benefits were worth the compiling 'overhead', most members appreciated the intelisense, additional language features and compile-time error checking. I still think the TS overhead outweighed the cost of working without intelisense and compile time error checking. And these days the overhead is extremely minimal and I personally don't see myself going back to JS anytime soon.
Big thanks and keep up the good work!
Cheers,
Ben
<EMAIL_ADDRESS>

We're glad you gave us a shot! We always love hearing positive experiences, so thanks for the personal note. :smiley:

Ping :smile:

We do website logo updates in batches, so this will get picked up at the next refresh. Not sure exactly when that will be since the guy who usually did that just left the team.

Hey guys, I just got a reminder to check up on this. Is there anyone assigned to updating the website logos yet? Would be nice to close this. :)

i update them in batches. they should be updated by the time TS 1.7 ships (i need to update the download links on the site anyways).
we are also working on a better workflow here to allow partners to send us PRs instead of me being the bottle neck.


Update list of groups to bundle without

@lamont-granquist fixed!

:+1: if this is producing good ad hoc builds.

👍  looks correct

Tested in Travis. Merging!


Possible Rewrite To Prevent Locking Issues

One possible redesigned architecture is to make it so that for every dependency in the DAG, there is a channel from the dependency to the dependent node.
The advantage of this redesign is it solves a lot of the locking issues that cause bugs right now.
However, it is essential that we add more tests that test the DAG before doing this, since this has the potential to break stuff.

One section of code that could benefit from some changes:
For where it calls ProvideStageInput, look into unifying, and calling an intermediate object (interface an impl) to check if it needs change the state, and lock if it makes sense. This would be helpful if we add more step providers, since the current setup is prone to locking errors.


parent tag synching

is it not possible to tag a cluster and have the vms underneath it inherit that tag in vmware? trying to automate tagging of machines in particular clusters but it doesn't seem to be coming through unless it's a vm folder or a vm itself.
Thanks!

Hi, this is correct, only the folder tag of a VM will be read if parent tag sync is enabled.
I could add a sync_vm_cluster_tag option to enable this behavior.
But I would like to not end up with even more and more config options.
Or would there even be a better way to configure the tag syncing? Any suggestions?

The language on the existing setting is a bit ambiguous and could already imply this happens, not really sure how to proceed there. We've worked around this (crappily) in the mean though.

I guess I should rephrase the config setting then.

Hi,
I just changed the whole setting to tag syncing. Would you mind test the latest "development" branch?
https://github.com/bb-Ricardo/netbox-sync/blob/ae169125b7f48e5bbf5d7b4b45ccb61cc50050fa/settings-example.ini#L264-L275
Thank you


How to set the /etc/default/grub?

How do we make updates the the grub settings for Mariner?

I manually created the file with the following template
using the following command:
sudo nano /etc/default/grub
and then pasting the below code.
It is recommended to run grub-update afterwards
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

Additionally, one can always edit the /etc/default/grub file but YMMV when it comes to official support


databox-start fails with Docker Toolbox (i.e. Windows version < 10)

The docker-start check for docker installed fails with Docker Toolbox for Windows (Docker version 17.07.0-ce, build 8784753):
$ ./databox-start dev
[2017-09-25T11:31:51+0100 databox-start]: docker is not installed;see https://docs.docker.com/engine/installation/

This is because in Docker Toolkit (which is required for Windows <10) docker is a function not an executable:
$ command -V docker
docker is a function
docker ()
{
    MSYS_NO_PATHCONV=1 docker.exe "$@"
}

if you fix that then the next problem is the lack of ifconfig. There are probably other issues too...
Workaround currently is to create a linux VM and work entirely in that.

To my knowledge:
on windows,
- Without hyper-v (windows 7 and 10 home) the best option for databox is a full Linux VM.
- With hyper-v (windows 10 pro) then docker for windows should work although it has never been tested.
on mac,
- docker toolbox also will not work, use "docker for mac"
This should type of info should be added to the docs referencing the documentation issue as a reminder (https://github.com/me-box/databox/issues/102)


DLL Locked by Mathematica

Have searched around for an answer but haven't found anything useful, here is my problem:
While iterating between Mathematica and the IDE (VS Code in this case) I couldn't go past the first build as Mathematica locks the DLL library so the build fails with this error:
fatal error LNK1104: cannot open file 'C:\...\target\debug\deps\hello_cargo.dll'

Anyone knows of a workaround other than quitting completely out of Mathematica?
And apologies if this is not the right place..

I'm not sure I fully understand the problem, but if the issue is that Windows is preventing the file from being modified because it is open by Mathematica, it might be possible to unlock it by telling Mathematica to unload the library. You can use LibraryUnload[..] to unload the library. So in your case, something like:
LibraryUnload["hello_cargo"]

(The first argument to LibraryUnload should match the library name/path you pass to LibraryFunctionLoad.)
Let me know if that helps.

Yes that worked! Thanks so much. Closing the issue.


Nord theme not showing in android studio(Ubuntu 20.04)

I installed the theme from marketplace and restarted the IDE, plugin section shows that Nord theme is installed.. but in appearance and behaviour.. it doesn't show up. I even downloaded .jar from official website than imported.. but that doesn't help as well.

Same for me, I'm on Windows 11.


pfe-collapse should not be in storybook

Pfe-collapse should not appear in storybook because it's not intended to be used on it's own, right? And there is no preview.
https://patternfly.github.io/patternfly-elements/demo/?knob-Theme=light&knob-Count=5&selectedKind=Collapse&selectedStory=pfe-collapse&full=0&addons=1&stories=1&panelRight=1&addonPanel=storybooks%2Fstorybook-addon-knobs

@starryeyez024 - There is a preview. Just click on "Toggle Control".
I think there's merit in pfe-collapse being in the Storybook so developers see how it works.

Ohhh, that was super not-obvious to me that that text was clickable. How would you feel about changing the H3 to <button type="button">Toggle Control</button> @kylebuch8


API documentation

lack of docs:

https://persiaml.readthedocs.io/en/latest/autoapi/persia/sparse/index.html
https://persiaml.readthedocs.io/en/latest/autoapi/persia/ctx/index.html
https://persiaml.readthedocs.io/en/latest/autoapi/persia/env/index.html
https://persiaml.readthedocs.io/en/latest/autoapi/persia/logger/index.html
https://persiaml.readthedocs.io/en/latest/autoapi/persia/wrapper/index.html

some of them should be hidden, such as persia.wrapper.logger, since users are not expected to use them.

Can close the issue now?

The overall format looks fine now. The writing still needs to be improved. I will comment on the code so that we can start improving the writing.