updating k8s client libraries and go version

What this PR does / why we need it:
Updating client libraries to support kubernetes 1.30 and updating go version to 1.22.2
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

/ok-to-test

/lgtm

/lgtm
/approve


azidentity - NewDefaultAzureCredential fails to get MSI credentials in GitHub Actions runner

Bug Report

import
github.com/Azure/azure-sdk-for-go/sdk/azidentity v1.0.0
output of go version
go version go1.18.3 linux/amd64

What happened?
Within a GitHub Actions workflow, running within Azapi Terraform provider the NewDefaultAzureCredential func failed to get a MSI credential from the default endpoint because MSI was not enabled. The GitHub runner must have been hosted in Azure. The error was a HTTP 400 and it prevented the NewDefaultAzureCredential from continuing and trying other methods to get credentials.

What did you expect or want to happen?
I want the NewDefaultAzureCredential func to continue if we get such an HTTP error, instead of failing.

How can we reproduce it?
Use the NewDefaultAzureCredential func within a GitHub actions public runner.

Anything we should know about your environment.
When I add an iptables rule to block access to <IP_ADDRESS>, then the NewDefaultAzureCredential func works.

Error detail

Error:      	Received unexpected error:
                                DefaultAzureCredential authentication failed
        	            	GET http://<IP_ADDRESS>/metadata/identity/oauth2/token
        	            	--------------------------------------------------------------------------------
        	            	RESPONSE [400] Bad Request
        	            	--------------------------------------------------------------------------------
        	            	{
        	            	  "error": "invalid_request",
        	            	  "error_description": "Identity not found"
        	            	}
        	            	--------------------------------------------------------------------------------

Can you double check your azidentity version? Since v0.13.0, NewDefaultAzureCredential doesn't do any I/O, making HTTP errors impossible. You could see this with an older version though.

Hey @chlowell,
Thanks for getting back to me!
The version of azidentity is v1.0.0. Of it's not azidentity doing this then it may be the policy client then that is. All I know is somewhere along the line the SDK is reaching out to get a MSI token and this fails on the public GitHub actions runners.
I've been able to work around it by putting in an iptables rule to block access to the endpoint.

If it's not azidentity doing this, then it may be the policy client then that is. All I know is somewhere along the line the SDK is reaching out to get a MSI token and this fails on the public GitHub actions runners.

I think I understand what's happening here. Before I get into that, how do you intend to authenticate? For DefaultAzureCredential, all that's left after managed identity is the Azure CLI--is that available to GitHub Actions? If you want to authenticate a service principal, you need to set the right environment variables.
As for the cause of this error, IMDS responds with the 400 you pasted above when it has no managed identity assigned. The credential considers this error non-fatal, as you want, unless the application provided a client ID for a user-assigned managed identity. The reasoning there is that the application must expect the identity it specified will be available; its unavailability then indicates a configuration error. Authenticating some other identity makes that hard to debug and can result in unexpected behavior or mysterious failures, if the other identity has different permissions. For DefaultAzureCredential, this client ID comes from AZURE_CLIENT_ID. If you aren't setting that yourself somehow, I see the Terraform provider will do so if it's configured with a client ID: https://github.com/Azure/terraform-provider-azapi/blob/3708a6e2376656691d2b31a9a2d7ded8435e2946/internal/provider/provider.go#L172.

Hi @matt-FFFFFF , @chlowell ,
Thank you so much for the investigation! Really appreciate it.
I raised a PR to fix it on the azapi side, which won't set AZURE_CLIENT_ID if it's empty.

The reasoning there is that the application must expect the identity it specified will be available; its unavailability then indicates a configuration error.

Totally agreed, but I think maybe specifying an empty client id should not be a fatal error? I'm not sure if it's a good idea to add a not-empty check on
https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/azidentity/default_azure_credential.go#L62
Thanks!

Totally agreed, but I think maybe specifying an empty client id should not be a fatal error? I'm not sure if it's a good idea to add a not-empty check on https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/azidentity/default_azure_credential.go#L62

I think we shall only set the client id when it is non empty. So instead of using os.LookupEnv(), we can simply use os.Getenv() and then check whether the client id is empty.

maybe specifying an empty client id should not be a fatal error? I'm not sure if it's a good idea to add a not-empty check

😆 I'm not sure either but here's my argument for keeping the current behavior. The SDK's only evidence of user intent is whether the variable is set. Our managed identity abstraction supports several platforms with different APIs and semantics. It's possible that in some scenario it makes sense for a user to specify an empty client ID (I don't know of one). Ignoring the empty value may mean not supporting that scenario or authenticating an unexpected identity and causing worse problems as I described above. The best the SDK can do is assume configuration is correct and allow the platform to point out problems via authentication errors.


vscode-extensions.jgclark.vscode-todo-highlight: init at 2.0.8

Description of changes
Adds https://marketplace.visualstudio.com/items?itemName=jgclark.vscode-todo-highlight

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

Congratulations for your first PR, keep them coming and... welcome to the Nix community!


[SPARK-29124][CORE] Use MurmurHash3 bytesHash(data, seed) instead of bytesHash(data)

What changes were proposed in this pull request?
This PR changes bytesHash(data) API invocation with the underlaying byteHash(data, arraySeed) invocation.
def bytesHash(data: Array[Byte]): Int = bytesHash(data, arraySeed)

Why are the changes needed?
The original API is changed between Scala versions by the following commit. From Scala 2.12.9, the semantic of the function is changed. If we use the underlying form, we are safe during Scala version migration.

https://github.com/scala/scala/commit/846ee2b1a47014c69ebd2352d91d467be74918b5#diff-ac889f851e109fc4387cd738d52ce177

Does this PR introduce any user-facing change?
No.
How was this patch tested?
This is a kind of refactoring.
Pass the Jenkins with the existing tests.

Test build #110825 has started for PR 25821 at commit a8187fe.

Merged build finished. Test PASSed.

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

cc @kiszk , @wangyum , @srowen

See https://github.com/apache/spark/pull/25404#issuecomment-532396170 -- is that the equivalent change?
But I agree that we can and should test such a change against the current build to see if it changes behavior.

This is an opposite approach. This PR makes Apache Spark independent from that Scala patch instead of matching to it. In that PR, I also suggest this approach.

to match scala/scala@846ee2b#diff-ac889f851e109fc4387cd738d52ce177 don't we need both calls to change bytesHash to arrayHash

Oh, OK. But wouldn't that probably change the behavior of Spark? I guess we'll see here in the tests.

For me, the PR itself is solid and safe, but I also believe that Jenkins will make it sure for us soon. 😄

Test build #110825 has finished for PR 25821 at commit a8187fe.

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

Merged build finished. Test PASSed.

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

Hi, @srowen , @wangyum , @kiszk .
Could you review this once more? I want to merge this first and retrigger Scala-2.12.10 PR on top of this.

Merged to master.

Thank you all!

See comment on other PR - yep I get the idea now, makes sense.

Hi, All.
Although this is a kind of improvement, I'll land this to branch-2.4.
We need this to upgrade branch-2.4 to Scala-2.12.10 and this is very safe patch.

Agree.


GPU Particles 3D: New particles not emitting with specific Lifetime + Scale Curve settings

Tested versions
Occurs in 4.3
Tested in 4.2, but can't get the specific particle system to work, in general
System information
Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated GeForce GTX 1060 6GB - Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz (12 Threads)
Issue description
The current Particle settings in the provided MRP result in no new particles being spawned.
This persists when the Lifetime settings is 16 seconds, or any value greater than that
When Lifetime is less than 16 seconds or the Scale Curve settings are altered, the system spawns new particles. Did I manage to find a perfect, broken balance or something?
Steps to reproduce
Mess with the Lifetime and Scale Curve values in the MRP.
Or other settings- perhaps something else is adding to it.
Minimal reproduction project (MRP)
mrp.zip

Also occurs when Lifetime is 10 seconds and Speed Scale is less than .7
That tells me that it may be the overall time that the particles are alive


Convenience flag to query stake distribution with drep-state query

Changelog
- description: |
    Add `--include-stake` flag to obtain the stake in the `drep-state` query
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  # - breaking       # the API has changed in a breaking way
  - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - improvement    # QoL changes e.g. refactoring
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  # - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context
This PR closes #551.
I introduce an overlap between the drep-state and drep-stake-distribution queries. With the --include-stake flag, the former now subsumes the latter. AFAICT, the queries are exposed separately because drep-stake-distribution is expensive. This makes obtaining all information associated with a DRep credential a two-command process. With the new flag, the expensive query is still guarded, but the CLI gets more user-friendly.
How to trust this PR
Highlight important bits of the PR that will make the review faster. If there are commands the reviewer can run to observe the new behavior, describe them.
Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated. See Running tests for more details
[ ] Self-reviewed the diff

looks like the current command is defaulting to --include-stake, i guess that should be false per default?
also, the generated output does not contain the keyhash anymore. looks like:
[
    {
        "anchor": {
            "dataHash": "1111111111111111111111111111111111111111111111111111111111111111",
            "url": "https://bit.ly/3zCH2HL"
        },
        "deposit": 2000000,
        "expiry": 188,
        "stake": null
    },
    {
        "anchor": null,
        "deposit": 2000000,
        "expiry": 230,
        "stake": null
    },
    {
        "anchor": null,
        "deposit": 2000000,
        "expiry": 216,
        "stake": null
    },
    {
        "anchor": {
            "dataHash": "f8f21b94aef91b0d5e7ff330889d60f665529897b5c1ae4a1aa608b6249e20e6",
            "url": "https://github.com/Mborongoma/SANCH-GOV-TESTES/blob/main/bio.txt"
        },
        "deposit": 2000000,
        "expiry": 227,
        "stake": null
    },
    {
        "anchor": {
            "dataHash": "fd1b4e7fd844a8e2805bfda173f6461fd59812fcad4ce8a69b5ab427f7226cf7",
            "url": "https://my-ip.at/test/hwdrep.json"
        },
        "deposit": 2000000,
        "expiry": 232,
        "stake": null
    }
]

looks like the current command defaults to --include-stake, i guess that should be false per default?

Well spotted, @gitmachtl! The flag is actually off by default, in the sense that the query isn't performed, but the output includes the "stake" field always. That's confusing, so I changed that behaviour in dcb4d68: Now the field should only be present when --include-stake is used.

thx! and the keyHash is missing in the output too for some reason.

hi, any plans to merge this into main soon? thx.


Create password grant tokens in testing

Laravel Version: 5.7.*
PHP Version: 7.2.9
Database Driver & Version: sqlite 7.2.9

Description:
I want to test my oauth server (with laravel/passport package).
I use unit tests, I use a memory database with PHPUnit, so I can not migrate the tables created by the package.
I would like to be able to call the following commands in my test:
$this->artisan('passport:client', ['--password' => null, '--no-interaction' => true]);
$this->artisan('passport:keys', ['--no-interaction' => true]);
But, I have this error:
Mockery\Exception\BadMethodCallException: Received Mockery_1_Illuminate_Console_OutputStyle::askQuestion(), but no expectations were specified
I'm sure this is due to the fact that I do not have a fully installed passport but I do not know how to do it.
Steps To Reproduce:
composer require laravel/passport
php artisan passport:client --password
php artisan passport:keys

I think you meant to create this issue in the laravel/passport repository


Api compatibility issue

While running the urlless sample, the app shows the following error:

The proposed fix is the PR: https://github.com/googlesamples/android-instant-apps/pull/56


Allow nested Lazy Values

Allow nested Lazy Values …
Fix #392
Fix #402

Hello @rochacbruno! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file example/issues/392_evaluate_nested_structures/app.py:

Line 19:80: E501 line too long (82 > 79 characters)
Line 21:80: E501 line too long (81 > 79 characters)
Line 22:80: E501 line too long (84 > 79 characters)
Line 23:80: E501 line too long (82 > 79 characters)


Move away from Compose YAML

After another discovery of unsupported feature by podman-compose and the reading of https://www.redhat.com/sysadmin/podman-compose-docker-compose and https://www.infoworld.com/article/3663672/what-is-podman-and-will-it-replace-docker.html, it seems to me that we should move away from Docker/Podman compose altogether.
According to the articles mentioned, the support for Compose YAML in Podman was only a afterthought and will never be the focus of the Podman team. The podman-compose project is lagging behind (the last patch was always a year ago) and misses important features of the compose specification; docker-compose doesn't work with Podman without some workarounds and some caveats. On the other hand, the support for Kubernetes was one of Podman's original goals.
Let's move away from Compose Yaml to Kubernetes and/or Podman's podman kube commands.

ask chatgpt to rewrite podman-compose recipes into podman kube ones to get started/see how it would look?  never used podman kube yet

Thanks to @mih, https://www.redhat.com/sysadmin/compose-podman-pods provides some useful info in migrating away from compose.


Allow negative push/pull/offset

Creating off page navigation and off page panels has required me to use negative positioning.
Looks like these mixins spit out classes (only?) to enable me to use @extend .push-md-2 for example.
@mixin make-col-offset($size, $columns: $grid-columns) {
  margin-left: percentage($size / $columns);
}

@mixin make-col-push($size, $columns: $grid-columns) {
  left: if($size > 0, percentage($size / $columns), auto);
}

@mixin make-col-pull($size, $columns: $grid-columns) {
  right: if($size > 0, percentage($size / $columns), auto);
}

I can use @include make-col-push(2) directly, but I'd like to specify here @include make-col-push(sm, 2) but that doesn't work. [Feature request for that]
Continuing on, I want to be able to use negative positioning, so in the same vein use @include make-col-push(sm, -2) (minus symbol), but the mixin looks at only calculating the position if it's greater than 0, otherwise making it default to 'auto'.
Now, I am able to do this using the make-col-offset mixin and multiplying by a negative grid-columns number gives me the abilty to minus things by 12/17/Whatever/48/etc columns. Mucho useful. For example:
.off-canvas {
  @include make-col-offset(-3);
}

Outputs:
.off-canvas {
  margin-left: -25%;
}

Now, the only drawback to this again is when designing for responsive views that have different column widths at different viewport sizes, so going back to that $size parameter. It would be great to be able to do the following:
.off-canvas {
  @include make-col-offset(sm, -3);
  @include make-col-offset(md, -4);
  @include make-col-offset(lg, -5);
}

Right now, I'm doing the following as a workaround:
    @include media-breakpoint-up(xs) {
      &.secondary {
        @include make-col-offset(-8);
      }
    }
    @include media-breakpoint-up(sm) {
      &.secondary {
        @include make-col-offset(-4);
      }
    }
    @include media-breakpoint-up(md) {
      &.secondary {
        @include make-col-offset(-3);
      }
    }

Thoughts welcomed,
D

I don't fully understand why this cannot be done aside from the framework itself. Personally seems as though this adds unnecessary bloat. IMO.

Well, apart from the size modifier offset works fine. And for push/pull, the $size > 0 prevents negative values otherwise that too would also work fine, again without the size modifier request.
I'm not saying I can't do it outside of the framework, but the code is pretty much already there apart from a tweak or two.

I've dropped offset, push, and pull in v4, so closing as a won't fix.

Just gonna leave "this" here for others, found this fix on the google. forces container-fluid to be full width if it's within a container
.container .container-fluid {
margin-left: calc(50% - 50vw);
margin-right: calc(50% - 50vw);
}


Frontend dennis

in The AboutUsSeciton I changed the margin top to 96 from 32
In the home page section I commented out and removed the useEffect() that was fetching calendar events as well as the imports for said events
In the events section I commented out then removed the loading conditions as well as the conditional statements and created a div to hold all the iframes that we currently have to put in manually for all the Luma events.
added const iframeStyle so you can change the height width etc of all iframes in EventsSection
Carosel event thunks and event tsx files were modified by commenting out anything relying on fetching events from the google calendar api
added EventsLuma Component for the events page
iframes are all embed links from luma

Thanks for the feedback, I will improve on it.


Issue downloading Sentinel-1 data over Gabon

Not finding any Sentinel-1 data over Gabon. Sentinel-2 data is downloading no problem. Using this config file as an input (with purposefully enlarged AOI and date range):
data_dir: ~/data/lope-sample
satellite_default:
  resolution: 10
  tile_size: 1_000  # note tile_size = tile_size * resolution
  dtype: UInt16
  composite_method: MEDIAN
  aoi:
    spatial:
      left: 330_000
      right: 480_000
      bottom: 350_000
      top: 500_000
      epsg: 5223
    temporal:
      start_date: 2017-01-01
      end_date: 2025-12-31
    country: Gabon
  gee:
    ee_project_id: geefetch
    max_tile_size: 5 # in MB
s1:
  composite_method: MEAN
s2: {}
gedi:
  format: GEOJSON

not finding any Sentinel-1 data to download. Have independently checked and Sentinel-1 data exists during this time period at this location.
Error messages look like:
Found 0 Sentinel-1 image.Check region BoundingBox(left=10.651831016503765, bottom=-1.1758636674218317, right=10.741732823692287, top=-1.0853738708499236, crs=CRS.from_epsg(4326)).

Might be because there is no ascending Sentinel-1 over Gabon ? We should check for both ascending and descending to avoid this.

looks like it

Nice, thanks, forgot about the orbit condition!
On Thu, Oct 31, 2024 at 7:32 PM Gabriel Belouze @.***>
wrote:

image.png (view on web)
https://github.com/user-attachments/assets/86e9f25a-b026-47f2-82d1-77bf1d17bc92
looks like it
—
Reply to this email directly, view it on GitHub
https://github.com/gbelouze/geefetch/issues/21#issuecomment-2450568590,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHTDKXQIH5MURCFX63ELPVDZ6JZTTAVCNFSM6AAAAABQ6WTXUWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJQGU3DQNJZGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


[Feature] Add vtable rendering to finished api

What problem does this feature solve?
Throw event when the vtable rendering is finished
What does the proposed API look like?
Add vtable rendering to finished api


Add new topic from dropdown

Branched out of #76 , finishes resolving #71

Changed v-autocomplete to v-combobox to allow entering new items
Existing items are sent as an id to Airtable, to make the link with the existing Topic record, new items are sent as the typed strings, to create new records with the string as the name (name_en)
The magic works because the Airtable call has a parameter typecast: true, that makes the best effort to identify the operation (if it's an existing id, link the record, if it's not, create a new record and then link it)
Added a small parsing logic on the payload function to make this work

Specs:

[x] Users can select existing items or type something new and press enter to add
[x] Added a persistent-hint to the Topics field, to explain how this works (it's not obvious that you can just type anything and press enter)

Limitations:

Cannot translate the topic name in English and Japanese, because the new values are just one simple string

@ann-kilzer Feel free to either merge this into PR #76 or review both separately and I can easily rebase this to point to master once #76 has been merged.

I think we need to treat these more like "tags" and just let people enter them in whatever language they want and don't try to translate them. Because we'll run into issues if most of them don't have a translation (as people will add them in only one language), they will show as "blank" options in the dropdown in other language.
If we just use one "name" field and let people enter whatever they want in whichever language, all options will show in the same dropdown and they can just choose whatever they want to associate with their profile (english tags or japanese tags or a mix of both) => This way is also simpler cause it's basically what's already implemented in this PR


Polygon layer with categories does not draw all polygons to be drawn in case categories do not cover all

IF BUG, INCLUDE THIS PART:
Steps to reproduce

Start DemoMap.exe
Load Shapefile contained in zip file attached as a new layer
Open layer properties for the layer
Select Unique values and Field "Strasse"
Apply changes
All polygons are drawn
Remove first category and apply changes
Result: Many polygons are missing, not only those of the first category that has been removed

DotSpatial version:
Expected behaviour
All polygons that fullfill the queries in the remaining categories should be drawn
Actual behaviour
See number 8 in Reproduction
0_Shapefiles.zip

DotSpatialBugPolygonLayerWithCategories.zip

I already have the bug fixed in our local DotSpatial fork, the reason ist that in MapPolygonLayer.DrawPaths in the foreach loop ofer the paths, in case category == null, the method returns instead of continueing to the next path.

Please create a pull request.

It seems to be fixed in the master branch already.
So I close this issue.


Move Track Candidate Kernels to Alpaka

New timing results. There seems to have been a speedup from the switch to Alpaka?

Validation Plots: Here

There seems to have been a speedup from the switch to Alpaka?

When you run the timing, can you run it once for the master and right after for the modified branch (or vice versa)? That would help us see the timing for both cases when the machine is in relatively the same conditions and better understand if there is a speed up or not. Thanks!

There seems to have been a speedup from the switch to Alpaka?

When you run the timing, can you run it once for the master and right after for the modified branch (or vice versa)? That would help us see the timing for both cases when the machine is in relatively the same conditions and better understand if there is a speed up or not. Thanks!

See the timing below. You can see the speedup in the TC time. This usually means that there's a bug, which is why I'm still marking this is a draft PR for now. Validation plots looked fine, but I'm going to make the comparison plots and look through them to be sure that there were no changes.
This PR Timing

Master Timing

Comparison plots look good, so I'm marking this PR as ready for review.

Converting back to draft like we discussed in the meeting to look into which kernel experiences the most speedup and to see what info the profiler gives.

This PR Timing

Validation Plots: Here
Comparison To Current Master: Here

Fixed a small bug in the commit above, not sure if it had any effect on the code though. Just in case, here is the new timing. The single stream time varies substantially (25.5-29.5 based on a couple runs), but I think the timing is relatively unchanged. The 8 stream time has much less variability between runs.

Validation Plots: Here
Comparison To Current Master: Here

The time reduction is huge for not doing anything to change the kernels. As another test, could you run the code with (I think) -v 2 so that it keeps track and prints the number of objects and compare the numbers?

I reran the code and I don't see any noticeable differences. Here is an example comparison for the one event.
Current Alpaka_Move
# of TrackCandidates produced: 2205
# of Pixel TrackCandidates produced: 2064
# of pT5 TrackCandidates produced: 808
# of pT3 TrackCandidates produced: 215
# of pLS TrackCandidates produced: 1041
# of T5 TrackCandidates produced: 141
This PR
# of TrackCandidates produced: 2209
# of Pixel TrackCandidates produced: 2066
# of pT5 TrackCandidates produced: 804
# of pT3 TrackCandidates produced: 218
# of pLS TrackCandidates produced: 1044
# of T5 TrackCandidates produced: 143


Add funding source?

@sjsrey, I have been spending a portion of the designated research time for my postdoc (paid for through NSF grant #1825768) working on spaghetti and was wondering if there were any objections to adding it to the README in a "Funding" section, like in esda and giddy?
Also, should there be any other funding sources listed for the previous incarnation, pysal.network?

Addressing in #482


Prepares Release 2.9.0

Description of changes:
Update changelog, readme, and benchmark data.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #102 (c961262) into main (09bafd3) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #102   +/-   ##
=========================================
  Coverage     65.10%   65.10%
  Complexity      193      193
=========================================
  Files            17       17
  Lines           854      854
  Branches        132      132
=========================================
  Hits            556      556
  Misses          229      229
  Partials         69       69

Continue to review full report at Codecov.

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


[SPARK-34346][CORE][TESTS][FOLLOWUP] Fix UT by removing core-site.xml

What changes were proposed in this pull request?
This is a follow-up for SPARK-34346 which causes a flakiness due to core-site.xml test resource file addition. This PR aims to remove the test resource core/src/test/resources/core-site.xml from core module.
Why are the changes needed?
Due to the test resource core-site.xml, YARN UT becomes flaky in GitHub Action and Jenkins.
$ build/sbt "yarn/testOnly *.YarnClusterSuite -- -z SPARK-16414" -Pyarn
...
[info] YarnClusterSuite:
[info] - yarn-cluster should respect conf overrides in SparkHadoopUtil (SPARK-16414, SPARK-23630) *** FAILED *** (20 seconds, 209 milliseconds)
[info]   FAILED did not equal FINISHED (stdout/stderr was not captured) (BaseYarnClusterSuite.scala:210)

To isolate more, we may use SPARK_TEST_HADOOP_CONF_DIR like yarn module's yarn/Client, but it seems an overkill in core module.
// SPARK-23630: during testing, Spark scripts filter out hadoop conf dirs so that user's
// environments do not interfere with tests. This allows a special env variable during
// tests so that custom conf dirs can be used by unit tests.
val confDirs = Seq("HADOOP_CONF_DIR", "YARN_CONF_DIR") ++
  (if (Utils.isTesting) Seq("SPARK_TEST_HADOOP_CONF_DIR") else Nil)

Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass the CIs.

Could you review this, @yaooqinn , @HyukjinKwon , @cloud-fan , @srowen ?

Test build #134993 has started for PR 31515 at commit 189cddf.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39576/

Hey guys, let me just merge this for now. I do think the test did not pass and it is broken.
@yaooqinn, can you make another followup to remove the asserts?

Merged to master, branch-3.1 and branch-3.0.

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/39576/

OK~

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

Test build #134993 has finished for PR 31515 at commit 189cddf.

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

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

Thank you, @srowen , @yaooqinn , @HyukjinKwon .


sanity fails to detect missing kernel driver

discovered by chance:
drossetti@dgx-1v-13:~/gdrcopy$ LD_LIBRARY_PATH=$PWD/src ./tests/sanity
Running suite(s): Sanity
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:181
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:218
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:276
Assertion "!((t.g) == ((void*)0))" failed at sanity.cpp:1583
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:358
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:471
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:547
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:626
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:772
Assertion "(read(read_fd, &cont, sizeof(int))) == (sizeof(int))" failed at sanity.cpp:740
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:881
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1021
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1134
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1134
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1264
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1388
Assertion "!((g) == ((void*)0))" failed at sanity.cpp:1470
100%: Checks: 15, Failures: 0, Errors: 0

The PRs has been merged. Closing the issue.

The PRs has been merged. Closing the issue.


Move Ceph RBD provisioner from in-tree to out of tree

The CEPH RBD provisioner is in-tree.  The sig-storage community is requesting that the ceph RBD provisioner move out of tree.
This issue to track the effort. There is no current owner or scheduling of the work, only the request by the community.  If anyone has requirements or wishes to sign up for design, development or review please comment here.

@cofyc @weiwei04 are you interested in working on it?

cc https://github.com/kubernetes-incubator/external-storage/issues/99

hi, @rootfs
I and @weiwei04 are interested in working on it. Currently, we are running a few k8s clusters with Ceph RBD support. Any suggestions about how to do it and collaborating with sig-storage community would be appreciated.

@cofyc thanks!
There is a cephfs provisioner under ceph. You can write a ceph/rbd provisioner, and get the Kubernetes RBD provisioner there.

@rootfs
ok, I am working on it.

@childsb Since you opened the "rewriting some bits" door, one of the issues we struggle with is passing [client] options down at mount time.
See ceph.conf examples to do things like tune rbd cache policy, writethrough, etc behavior from an rbd client perspective.
Now, forgive me as I start to enter areas of my own ignorance - the need to me is clear but its relevancy to the rbd provisioner is not. Its unclear whether the provisioning workflow would play any role here as the kubelet actually performs the rbd device hookups and mounting and it is at this point these settings would be (and are not currently) taken into account.  I imagine the goal is to also take the kubelet rbd client connectivity code also out of tree otherwise I'm confused where this is going ultimately.  In any event, I could imagine a desire to be able to control client settings such as this with provisioner specific PVC metadata to drive these client options on a per PVC basis so the kubelet could exercise them at the time it plumbs up the rbd device.  In any event, at the very least I thought it would be worth while to publicly announce this client-tuning need to those far smarter then myself to decide where it ultimately belongs.

@wongma7  I'm guessing this issue can be closed now, RBD provisioner is already in external-storage.


Added support to configure client with all JAXWS implementing libraries.

resolves #22

Codecov Report

Merging #28 into master will decrease coverage by 0.42%.
The diff coverage is 44.44%.

@@             Coverage Diff              @@
##             master      #28      +/-   ##
============================================
- Coverage     93.02%   92.59%   -0.43%
- Complexity      442      443       +1
============================================
  Files            50       50
  Lines          1047     1054       +7
  Branches         48       50       +2
============================================
+ Hits            974      976       +2
- Misses           57       60       +3
- Partials         16       18       +2

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/ee/sk/smartid/SmartIdClient.java
89.36% <0%> (-6.2%)
15 <0> (ø)

.../java/ee/sk/smartid/rest/SmartIdRestConnector.java
91.85% <66.66%> (-1.23%)
24 <3> (+1)

Continue to review full report at Codecov.

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

This can be now merged.

Can someone please merge this? 👍


deploy_to does not work in a stage config file

I place the set :deploy_to in each of the stage config files: config/deploy/production.rb and config/deploy/staging.rb
Example:
set :deploy_to, '/home/user/htdocs/app-name'

After running cap staging deploy:check --trace I can see that this value was not applied:
...
** Execute deploy:check:directories
 INFO [91f6713c] Running /usr/bin/env mkdir -pv /var/www/shared /var/www/releases on example.net
DEBUG [91f6713c] Command: /usr/bin/env mkdir -pv /var/www/shared /var/www/releases
...

I use a basic capistrano structure:
├── Capfile
├── config
│   ├── deploy
│   │   ├── production.rb
│   │   └── staging.rb
│   └── deploy.rb
└── lib
    └── capistrano
            └── tasks

I thought that those stage config files are there to define custom variables for each stage?

Still an issue :(

@sp-niemand Overriding :deploy_to in a stage file is definitely supposed to work, and indeed for my own projects it is working fine. (Capistrano 3.4.0)
My only guess is that you are using a very old version of Capistrano (v2?) that behaves differently, or perhaps you have a Capistrano plugin loaded that is breaking the default functionality. Any insights you have on this would help us troubleshoot.
Have you tried, e.g. adding a puts statement to your stage file to verify that is actually being used?


DNS Entry not correct

The problem
I am not sure how to describe the issue. I have successfully created a tunnel with cloudfare.
Let's call it example.com.  I am trying to add an additional_host, let's call it r.example.com. Here is the configuration for it:
additional_hosts:
  - hostname: r.example.com
    service: http://<IP_ADDRESS>:31

However, it creates a CNAME record in Cloudfare DNS records of r.example.com.example.com. It is adding the domain name twice. Here is a log snippet:
[08:25:58] INFO: Checking add-on config...
[08:25:59] INFO: Checking for existing certificate...
[08:25:59] INFO: Existing certificate found
[08:25:59] INFO: Checking for existing tunnel...
[08:25:59] INFO: Existing tunnel with ID xxxx-xx-xxxx-xxxxx found
[08:25:59] INFO: Checking if existing tunnel matches name given in config
[08:25:59] INFO: Existing Cloudflare Tunnel name matches config, proceeding with existing tunnel file
[08:25:59] INFO: Creating config file...
[08:26:00] INFO: Validating config file...
Validating rules from /tmp/config.json
OK
[08:26:00] INFO: Creating DNS entry r.example,com...
2024-05-31T13:26:00Z INF Added CNAME r.example.com.example.com which will route to this tunnel tunnelID= xxxx-xx-xxxx-xxxxx
[08:26:00] INFO: Finished setting up the Cloudflare Tunnel
[08:26:01] INFO: Connecting Cloudflare Tunnel...

I thought it was because I did not add in the configuration:
external_hostname: example.com

If the add-on restarts, then I get the following error:
[08:40:19] INFO: Creating DNS entry cameras.gotoalexander.com...
Failed to add route: code: 1003, reason: Failed to create record r.example.com.gotoalexanderhome.com with err An A, AAAA, or CNAME record with that host already exists. For more details, refer to <https://developers.cloudflare.com/dns/manage-dns-records/troubleshooting/records-with-same-name/>.
[08:40:20] FATAL: Failed to create DNS entry r.example.com.

I am revisiting this add-on as I have used it before and it worked flawlessly. I cannot for the life of me figure this one out.
Any ideas?
Scott
What version of Cloudflared has the issue?
5.1.10
What was the last working version of Cloudflared?
No response
What type of installation are you running?
Home Assistant OS
Add-on YAML Configuration
No response
Anything in the logs that might be useful for us?
No response
Steps to reproduce the issue
See above.
Additional information
No response

Never mind. I uninstalled and reinstalled the add-on and it works perfectly now.


Include custom tags in trace

Related issue https://linear.app/serverless/issue/SC-564/python-sdk-custom-tags-api
Description

Include custom tags in trace
Integration & unit test custom tags
Upgrade to the latest base SDK version

Testing done
Integration tested:
➜  node git:(include-custom-tags-in-trace) ✗ npx mocha test/python/aws-lambda-sdk/integration.test.js
2023-03-15T17:21:51.742Z ℹ test test uid: selcuk

  Python: integration
2023-03-15T17:21:51.836Z ℹ test Creating core resources test-python-sdk-selcuk
2023-03-15T17:22:27.777Z ℹ test Process function success-v3-8
2023-03-15T17:22:27.778Z ℹ test Process function success-v3-9
2023-03-15T17:22:27.778Z ℹ test Process function error-v3-8
2023-03-15T17:22:27.779Z ℹ test Process function error-v3-9
2023-03-15T17:22:27.779Z ℹ test Process function error_unhandled-v3-8
2023-03-15T17:22:27.779Z ℹ test Process function error_unhandled-v3-9
2023-03-15T17:22:27.780Z ℹ test Process function sdk-v3-8
2023-03-15T17:22:27.780Z ℹ test Process function sdk-v3-9
    ✔ success-v3-8 (29355ms)
    ✔ success-v3-9 (1117ms)
    ✔ error-v3-8
    ✔ error-v3-9
    ✔ error_unhandled-v3-8
    ✔ error_unhandled-v3-9
    ✔ sdk-v3-8
    ✔ sdk-v3-9 (5024ms)
2023-03-15T17:23:03.307Z ℹ test Cleanup test-python-sdk-selcuk
2023-03-15T17:23:03.651Z ℹ test Deleted 4 version of the layer test-python-sdk-selcuk-internal
2023-03-15T17:23:04.581Z ℹ test Detached IAM policy arn:aws:iam::692593327170:policy/test-python-sdk-selcuk from test-python-sdk-selcuk
2023-03-15T17:23:04.798Z ℹ test Deleted IAM role test-python-sdk-selcuk
2023-03-15T17:23:05.276Z ℹ test Deleted IAM policy arn:aws:iam::692593327170:policy/test-python-sdk-selcuk

  8 passing (1m)

@medikoo ready for review please 🙏

@selcukcihan can we follow up with a release?

@selcukcihan can we follow up with a release?

https://github.com/serverless/console/pull/533 👍


Incorrect Macro Expansions for Log and Msg of Chained Rule

Description
The MATCHED_VAR_NAME is taken from the chained rule. It should instead be taken from the rule where msg action is defined.
Variables are expanded incorrectly for Log and Msg of Rule
MATCHED_VAR expands to REQUEST_HEADERS:host i.e key but it should be attack i.e. value of MATCHED_VAR
MATCHED_VAR_NAME expands to MATCHED_VARS_NAMES:REQUEST_HEADERS:host i.e. key:value but it should be value of MATCHED_VAR_NAME
It seems the msg, data gets overridden as the chain rule gets evaluated.
Steps to reproduce
rules = `
SecRule REQUEST_HEADERS "@rx attack" \
    "id:20,\
    phase:1,\
    log,\
    msg:'Chained rule test',\
    logdata:'Found %{MATCHED_VAR} in %{MATCHED_VAR_NAME}',\
    chain"
    SecRule MATCHED_VARS_NAMES "@rx host" \
        "block"
`
waf := coraza.NewWaf()
parser, err := seclang.NewParser(waf)
if err != nil {
    fmt.Println(err)
}
err = parser.FromString(rules)
if err != nil {
    fmt.Println(err)
}
tx := waf.NewTransaction()
tx.ForceRequestBodyVariable = true
tx.AddRequestHeader("Host", "attacker")
tx.ProcessURI("/test", "POST", "HTTP/1.1")
tx.ProcessRequestHeaders()
tx.ProcessRequestBody()
fmt.Println("Interruption", tx.Interruption)
for _, match := range tx.MatchedRules {
    fmt.Println("matched Msg ", match.Message)
    fmt.Println("matched Data ", match.Data)
}

Expected result
matched Msg  Chained rule test
matched Data  Found attack in REQUEST_HEADERS:host

Actual result
matched Msg  Chained rule test
matched Data  Found REQUEST_HEADERS:host in MATCHED_VARS_NAMES:REQUEST_HEADERS:host

IMHO this would not work.
A rule like the following would require preserving the last chain. So it would be better to preserve the match message and data from the rule/subrule where the msg, logdata action are specified. I have a fix in work that solves this.
SecRule REQUEST_HEADERS "@rx attack" \
    "id:20,\
    phase:1,\
    log,\
    chain"
    SecRule MATCHED_VARS_NAMES "@rx host" \
         msg:'Chained rule test',\
         logdata:'Found %{MATCHED_VAR} in %{MATCHED_VAR_NAME}',\
        "block"

IMHO this would not work.
A rule like the following would require preserving the last chain. So it would be better to preserve the match message and data from the rule/subrule where the msg, logdata action are specified. I have a fix in work that solves this.
SecRule REQUEST_HEADERS "@rx attack" \
    "id:20,\
    phase:1,\
    log,\
    chain"
    SecRule MATCHED_VARS_NAMES "@rx host" \
         msg:'Chained rule test',\
         logdata:'Found %{MATCHED_VAR} in %{MATCHED_VAR_NAME}',\
        "block"

@piyushroshan
If there are more than one chained rules, say 3, each chained rules has its logdata. Then how we will handle this? Or this is not a valid case?

This was fixed, right @piyushroshan ?

Yes.


[Device Support Request] GLEDOPTO GL-C-002P

Hello !
I have a new GLEDOPTO controller, details are here. I was able to pair with Home-Assistant, entities are present but the controls (on/off, brightness, temperature, etc) are not working.
Thank you for your help!

Device signature
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4687, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
  "endpoints": {
    "11": {
      "profile_id": 260,
      "device_type": "0x010c",
      "in_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0008",
        "0x0300",
        "0x1000"
      ],
      "out_clusters": [
        "0x0019"
      ]
    },
    "242": {
      "profile_id": 41440,
      "device_type": "0x0061",
      "in_clusters": [],
      "out_clusters": [
        "0x0021"
      ]
    }
  },
  "manufacturer": "GLEDOPTO",
  "model": "GL-C-006P",
  "class": "zigpy.device.Device"
}

Diagnostic information
{
  "home_assistant": {
    "installation_type": "Home Assistant Container",
    "version": "2022.5.5",
    "dev": false,
    "hassio": false,
    "virtualenv": false,
    "python_version": "3.9.9",
    "docker": true,
    "arch": "aarch64",
    "timezone": "Europe/Paris",
    "os_name": "Linux",
    "os_version": "4.18.8-odroidc2",
    "run_as_root": true
  },
  "custom_components": {
    "momentary": {
      "version": "0.5.3",
      "requirements": []
    },
    "dyson_cloud": {
      "version": "0.15.0",
      "requirements": [
        "libdyson==0.8.7"
      ]
    },
    "dyson_local": {
      "version": "0.16.4-4",
      "requirements": [
        "libdyson==0.8.11"
      ]
    },
    "lifx": {
      "version": "2022.06.03",
      "requirements": [
        "aiolifx==0.8.1",
        "aiolifx_effects==0.2.2"
      ]
    }
  },
  "integration_manifest": {
    "domain": "zha",
    "name": "Zigbee Home Automation",
    "config_flow": true,
    "documentation": "https://www.home-assistant.io/integrations/zha",
    "requirements": [
      "bellows==0.29.0",
      "pyserial==3.5",
      "pyserial-asyncio==0.6",
      "zha-quirks==0.0.73",
      "zigpy-deconz==0.16.0",
      "zigpy==0.45.1",
      "zigpy-xbee==0.14.0",
      "zigpy-zigate==0.7.4",
      "zigpy-znp==0.7.0"
    ],
    "usb": [
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*2652*",
        "known_devices": [
          "slae.sh cc2652rb stick"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*zigstar*",
        "known_devices": [
          "ZigStar Coordinators"
        ]
      },
      {
        "vid": "1CF1",
        "pid": "0030",
        "description": "*conbee*",
        "known_devices": [
          "Conbee II"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8A2A",
        "description": "*zigbee*",
        "known_devices": [
          "Nortek HUSBZB-1"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8B34",
        "description": "*bv 2010/10*",
        "known_devices": [
          "Bitron Video AV2010/10"
        ]
      }
    ],
    "codeowners": [
      "@dmulcahey",
      "@adminiuga"
    ],
    "zeroconf": [
      {
        "type": "_esphomelib._tcp.local.",
        "name": "tube*"
      }
    ],
    "after_dependencies": [
      "usb",
      "zeroconf"
    ],
    "iot_class": "local_polling",
    "loggers": [
      "aiosqlite",
      "bellows",
      "crccheck",
      "pure_pcapy3",
      "zhaquirks",
      "zigpy",
      "zigpy_deconz",
      "zigpy_xbee",
      "zigpy_zigate",
      "zigpy_znp"
    ],
    "is_built_in": true
  },
  "data": {
    "ieee": "**REDACTED**",
    "nwk": 35784,
    "manufacturer": "GLEDOPTO",
    "model": "GL-C-006P",
    "name": "GLEDOPTO GL-C-006P",
    "quirk_applied": false,
    "quirk_class": "zigpy.device.Device",
    "manufacturer_code": 4687,
    "power_source": "Mains",
    "lqi": null,
    "rssi": null,
    "last_seen": "2022-06-30T12:09:57",
    "available": false,
    "device_type": "Router",
    "signature": {
      "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4687, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
      "endpoints": {
        "11": {
          "profile_id": 260,
          "device_type": "0x010c",
          "in_clusters": [
            "0x0000",
            "0x0003",
            "0x0004",
            "0x0005",
            "0x0006",
            "0x0008",
            "0x0300",
            "0x1000"
          ],
          "out_clusters": [
            "0x0019"
          ]
        },
        "242": {
          "profile_id": 41440,
          "device_type": "0x0061",
          "in_clusters": [],
          "out_clusters": [
            "0x0021"
          ]
        }
      }
    },
    "entities": [
      {
        "entity_id": "button.led_strip_identify",
        "name": "GLEDOPTO GL-C-006P"
      },
      {
        "entity_id": "light.led_strip_level_light_color_on_off",
        "name": "GLEDOPTO GL-C-006P"
      },
      {
        "entity_id": "select.led_strip_on_off_startuponoff",
        "name": "GLEDOPTO GL-C-006P"
      }
    ],
    "neighbors": [],
    "endpoint_names": [
      {
        "name": "COLOR_TEMPERATURE_LIGHT"
      },
      {
        "name": "unknown 97 device_type of 0xa1e0 profile id"
      }
    ],
    "user_given_name": "Led strip",
    "device_reg_id": "3cc1f10bb2f9fb903d97bda720ba7ba6",
    "area_id": "salon"
  }
}

Additional logs
Paste any additional debug logs here.
Don't remove the extra line breaks outside the ``` marks.

The device signature and diagnostic information you submitted seems to be for a GL-C-006P (and not a GL-C-002P).
Are you sure that you entered the correct information? (Does the controller really report itself as another model?)
Also, you could (backup and) upgrade Home Assistant to the latest release.

Yes, the model detected by ZHA is related to the mode of the device. I can switch mode (Dim, CCT, RGB, RGBW, RGBCCT) by pushing opt button. So, the device model is GL-C-002P but the software model depends of the mode.
I will upgrade and do a new pairing

Thanks for your support!
I will do it tomorrow and I keep you informed

Apparently there's a firmware bug in the device. This might be related: https://github.com/Koenkk/zigbee2mqtt/issues/11202

Oh okay, I will take a look so. Do you know how can I verify the current firmware version before doing the upgrade?

Hello @TheJulianJES
I followed the instruction given by Sunxperious, here : https://github.com/Koenkk/zigbee2mqtt/issues/11202#issuecomment-1173047823
I was able to start the upgrade but my device doesn't stay paired to the coordinator and so the upgrade stop.
2022-07-08 21:24:02 DEBUG (MainThread) [zigpy.zcl] [0xCC02:11:0x0019] OTA image_block handler for 'GLEDOPTO GL-C-008P': field_control=FieldControl.MinimumBlockPeriod, manufacturer_id=4687, image_type=5145, file_version=352399361, file_offset=5200, max_data_size=48, request_node_addr=Noneblock_request_delay=0
2022-07-08 21:24:02 DEBUG (MainThread) [zigpy.zcl] [0xCC02:11:0x0019] OTA upgrade progress: 2.4
Could you help me?
Thank you for your support!

I'm having similar issues with the  GL-C-002P. When set to RGB mode, the device reports as a GL-C-003P. However I dont get a color wheel, I only get a white temperature control slider that doesn't do anything. On/Off behaves properly but light color cant be changed at all. On the newest firmware for the device and home assistant is fully up to date.
{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4687, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
"endpoints": {
"11": {
"profile_id": 260,
"device_type": "0x0102",
"in_clusters": [
"0x0000",
"0x0003",
"0x0004",
"0x0005",
"0x0006",
"0x0008",
"0x0300",
"0x1000"
],
"out_clusters": [
"0x0019"
]
},
"242": {
"profile_id": 41440,
"device_type": "0x0061",
"in_clusters": [],
"out_clusters": [
"0x0021"
]
}
},
"manufacturer": "GLEDOPTO",
"model": "GL-C-003P",
"class": "zigpy.device.Device"
}

Hello. Please tell me if it is possible to configure the controller via z2m so that after turning off and on the electricity, the light is always OFF.
Example:

I turned on the light
the electricity in the apartment was turned off
I went to bed
they provide electricity at night! This is where it needs to be always OFF.
On controllers GL-C-001P, GL-C-002P, GL-C-008P, GL-C-008P (mini), can you make the light always OFF?
The controller will always be in mode: RGB+CCT: GL-C-008P

I think its better asking that at Z2M and not ZHA git issue

any updates?


Added links to npm #742

Added links to NPM following guidelines given in #763

@crew-guy I know you already started over before but I suggest you close this PR, create a new branch, and work on the README from a different editor, as that one is messing up the README. Also, the work between this PR and the other one are getting entangled, so please finish this one first then go back to the other one. I think this will resolve some of the confusion you are having.

@crew-guy I know you already started over before but I suggest you close this PR, create a new branch, and work on the README from a different editor, as that one is messing up the README. Also, the work between this PR and the other one are getting entangled, so please finish this one first then go back to the other one. I think this will resolve some of the confusion you are having.

Done !! Check out #781 and #782 !! I really hope I got it all right this time !


Error connecting to outlook.office365.com | failed to connect to server using any of 8 IP Addresses: dial tcp: address 2603:1036:302:415b::2:993: too many colons in address

At least two problems:

the assumption that we're working with an IPv4 formatted address

https://github.com/atc0005/check-mail/blob/8d304871400d56704af085262c92a66be8ccddef/internal/mbxs/connect.go#L55

the error message doesn't directly expose which IP Addresses were tried

This error occurred at 8 am this morning during a Nagios service check. Will hotfix quickly and deploy a prototype build to gather more information for a proper fix.


Question about PPO2 learning rate and optimizer #question

Hello,
I am training a ppo2 model, but their are some details that aren't very clear for me.
When I create the ppo2 model for the first time, I use a learning rate of 0.001
When I check the learning rate with :
print("Learning Rate: ", model.learning_rate)
It shows exactly that, but when it run for 1 full epoch, then the :
print("Learning Rate: ", model.learning_rate)
shows :
"Learning Rate:  <function constfn..func at 0x7f163c5e7158>"
So I guess the learning rate is used by an optimizer that change the learning rate automaticaly like adam.
Is their a way to show the current learning_rate from that function?
Can the learning rate increase with time, or it can only decrease ?
Because when I load a trained model from a file, its like the training is starting from the start again.
So my question is, do the learning_rate of the imported model is the same as it was when the model was saved, or do the learning_rate is reset every time the model is loaded?
Last question, how can we use a different optimizer for the ppo2
Thank you for your reading, hope someone can help me with this.
Greg

Hello,
I am training a ppo2 model, but their are some details that aren't very clear for me.
When I create the ppo2 model for the first time, I use a learning rate of 0.001
When I check the learning rate with :
print("Learning Rate: ", model.learning_rate)
It shows exactly that, but when it run for 1 full epoch, then the :
print("Learning Rate: ", model.learning_rate)
shows :
"Learning Rate: <function constfn..func at 0x7f163c5e7158>"
So I guess the learning rate is used by an optimizer that change the learning rate automaticaly like adam.
Is their a way to show the current learning_rate from that function?
Can the learning rate increase with time, or it can only decrease ?
Because when I load a trained model from a file, its like the training is starting from the start again.
So my question is, do the learning_rate of the imported model is the same as it was when the model was saved, or do the learning_rate is reset every time the model is loaded?
Last question, how can we use a different optimizer for the ppo2
Thank you for your reading, hope someone can help me with this.
Greg

ps: I tried to put a label with "question" for the last 15min but I realy didn't find how to do, sorry for that.

Hello,

Is their a way to show the current learning_rate from that function?

Answer is in the code or in the sac documenation (which uses the same type of callable):
"it can be a function of the current progress (from 1 to 0)"
so you have to call it to now the current learning rate:
current_progress = 1.0  # from 1 (start of training) to 0
print(model.learning_rate(1))  # initial learning rate

Can the learning rate increase with time, or it can only decrease ?

It is a callable, it can be anything.

do the learning_rate is reset every time the model is loaded?

It is reset for now (see #301 )

Last question, how can we use a different optimizer for the ppo2

You need to have a custom version of stable baselines.

ok thanks !


Support subfolders

Display subfolders as such along with bookmarks and open them as root on click.
Actually I'm looking for Fast Dial extension replacement where i had built quite big tree of such folders with bookmarks.

Duplicate, see #3


Verbatim credits (credits sourcing)

Intro/suggestion from Lanolin (#hsmusic-chat):

I just want to point out the way I'm sourcing from releases on multiple platforms, doubling an entry from both Bandcamp and YouTube though they're similar (but not identical), and including the Bandcamp credits blurb as originally written.
I'm not going over the thousands of tracks already on the wiki present on Bandcamp right now, but I think it would be right to always archive credits text as commentary on principle.
We can implement these commentary entries as "collapsed by default" a little later, as we add them across more pages, since they're primarily reference material and usually just duplicate stuff that's in the normal UI places.
This would include reference lists precisely as written (with wiki links applied, of course). Although it's content and not represented as data, it would help preserve where artists list their track as referencing Black instead of Liquid Negrocity (and the wiki disagrees re: our own track referencing data), for example.
They should probably go on a separate field than Commentary, also.
It doesn't make sense to tally or include them in the commentary section on an artist page, nor generally to put them in an album's commentary page.
Also, this would mean we can collapse - and expand - the whole credits section (on a track page) rather than individual credits-y commentary entries.

Our plan for this is to use almost exactly the same interface and design as Multiple Lyrics — these features are strongly related.

Must be implemented alongside hsmusic/bc-art#10, which means this is pending hsmusic/bc-art#7 and hsmusic/bc-art#8. See #hsmusic-chat for general dependency discussion.


add template hook in user div

Adds a template hook in the user menu
openslides-conversations uses that hook for adding global microphone and camera indicators

@tsiegleauq Please rebase on top of master (to fix travis).
@FinnStutzenstein Review please.

OK. Rebased it and removed the empty line.

Ok.


(maint) acceptance test: use https for package repos

this fixed all the failing tests besides centos8, which we will stop testing because it is EOL.


Allow adding basis set from string instead of file

Codecov Report

Merging #156 (b5cfa2f) into master (2d9f096) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@bennybp good to go


Allow to listen on multiple http addresses

Proposed change

This allows to configure multiple listen addresses, e.g. IPv4 and IPv6.
The first configured address will be used as base_url (if not
configured); if this is an IPv6 address, the URL will now also be
formatted correctly.
Type of change

[ ] Dependency upgrade
[X] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[X] New feature (which adds functionality to an existing integration)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Example entry for configuration.yaml:

# Example configuration.yaml
http:
  server_host: '<IP_ADDRESS>,::'

Additional information

Link to documentation pull request: https://github.com/home-assistant/home-assistant.io/pull/12155

Checklist

[X] The code change is tested and works locally.
[X] Local tests pass. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.
[X] I have followed the development checklist
[X] The code has been formatted using Black (black --fast homeassistant tests)
[X] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[X] Documentation added/updated for www.home-assistant.io

Hi @devkid,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Hi @devkid,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

This is not something I want to support. If anything, we should move HTTP configuration options out of Home Assistant, not add more. If people want to do more fancy things I recommend they use nginx in front of it.

IMHO being able to listen on multiple addresses (especially IPv4 and IPv6) is pretty basic, not a "fancy thing".

I agree with balloob here. Reverse proxies can handle this perfectly fine. Reducing the options sounds way better.

Basic thing or not, it will lead to now people wanting different certs for different ports, maybe all other options duplicated too etc. We shouldn't go there.


Fix VT mouse capture issues in Terminal and conhost

This pull request fixes capture and event generation in VT mouse mode
for both conhost and terminal.
Fixes #6401.
[1/3] Terminal: clamp mouse events to the viewport, don't throw them away
gnome-terminal (at least) sends mouse events whose x/y are at the
extreme ends of the buffer when a drag starts inside the terminal and
then exits it.
We would previously discard any mouse events that exited the borders of
the viewport. Now we will keep emitting events where X/Y=0/w/h.
[2/3] conhost: clamp VT mouse to viewport, capture pointer
This is the same as (1), but for conhost. conhost wasn't already
capturing the pointer when VT mouse mode was in use. By capturing, we
ensure that events that happen outside the screen still result in events
sent to an application (like a release after a drag)
[3/3] wpf: capture the pointer when VT mouse is enabled
This is the same as (2), but for the WPF control. Clamping is handled
in TerminalCore in (1), so we didn't need to do it in WPF.

wiffed it with the name. fixed.

Tagged @miniksa in because it touches the conhost wndproc

@msftbot merge this in 9 minutes

Looks good to me with wpf control and comments.

@msftbot merge this in 1 minutes


Scorecards workflow failing on website-cms

The workflow has been failing on that repository for a very long time.

The action workflow may now work on private repositories: https://github.com/ossf/scorecard/issues/3220

Closing as scorecards was removed from this repo.


when using log file, messages still sent to syslog

if I have the following setting in the ctrld.toml :
log_level = 'debug'
log_path = '/var/log/controld.log'

or just using the command line flag --log=/var/log/controld.log
output indeed goes to the log file but it does not stop it from going to syslog as well. it should be one or the other (or at least a way to turn off the syslog )

What OS are you running this on? What if you write it to a different directory, that's not /var/log?
You should also be able to configure syslog to not write the log data for specific programs.

Debian and Ubuntu 20.04. changing to /tmp/varlog/controld.log  didn't change anything but I was able to configure syslog to filter out the messages.
Still seems to me that ctrld shouldnt be producing the output in the first place.

@katchy3132 FYI, ctrld output to console and log file (when configured, aka --log). What's your system service manager? Is it systemd or SysV?

@katchy3132 FYI, ctrld output to console and log file (when configured, aka --log). What's your system service manager? Is it systemd or SysV?

systemd

@katchy3132 FYI, ctrld output to console and log file (when configured, aka --log). What's your system service manager? Is it systemd or SysV?

systemd

Then the systemd service file will be configured to use:
StandardOutput=file:/var/log/ctrld.out
StandardError=file:/var/log/ctrld.err

Is this the syslog you mentioned?

@katchy3132 FYI, ctrld output to console and log file (when configured, aka --log). What's your system service manager? Is it systemd or SysV?

systemd

Then the systemd service file will be configured to use:
StandardOutput=file:/var/log/ctrld.out
StandardError=file:/var/log/ctrld.err

Is this the syslog you mentioned?

Ah wait, those lines aren't set with default configuration that ctrld uses, so probably something else.

Please try the latest v1.3.0 release.


Servers down? Lots of 521s

I've noticed that shields seems very inconsistent recently; thought it was a github issue (they show up as 404 there); but this is from shields.io site directly:

You are right. One server is inaccessible on port 443 for some reason. I investigate.

I had an outdated node version. It is fixed now. Thanks for raising the issue!


⚠ Bofrost.at has degraded performance

In 405b113, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1809 ms

Resolved: Bofrost.at performance has improved in 2e8e8a6.


Renamed canRead to canSelect and canCreate to canInsert

This PR renames canRead to canSelect and canCreate to canInsert to be more close to actual ACL policies as mentioned here.
Merge Chaise PR immediately after merging this PR to avoid build problems.

I know the discussion was only about permissions. But shouldn't we change the create and read functions aswell? So we are using the same terminology all over the place.


Knowledge Agent Release 23.12 Compliance Acceptance Criteria

Release Compliance 23.12
Source in Catena-X Confluence + Expert Contacts here. (Source only accessible for Catena-X Consortia members in current transition phase)

[x] #349

Obtain approval from CX Gaia-X expert(s), prior to Gate review.
Provide info as early as possible; expect optimization loops based on feedback
=> check linked PDF summary for requirements (Source only accessible for Catena-X Consortia members in current transition phase).

Contact:

Release Mangement

[x] #350
(personal data; Data Protection & Privacy DPP)

assessment must be completed via Catena-X GDPR questionnaire (Source only accessible for Catena-X Consortia members in current transition phase.)
either the product/service doesn`t process any relevant data,
or - in case the assessment reveals potential issues - a more severe "Data Privacy Impact Assessment" shall be conducted (if applicable: robust mitigation actions must be completed)
Provide evidence for GDPR compliance prior to Gate review. Previous assessments remain valid, as long as approach to handling of personal data was not changed.

Contact:

Release Mangement

[ ] Interoperability Check
Acceptance criteria are fulfilled as described in in the following area on confluence: Interoperability Quality Gate Requirements (Source only accessible for Catena-X Consortia members in current transition phase.)

Approval will be documented centrally by Expert(s)

Obtain approval from Interoperability experts prior to Gate review.

Therefore consult the regular office hours as early as possible; expect optimization loops based on feedback. (Source only accessible for Catena-X Consortia members in current transition phase.)
Contact:

SYSTEM ARCHITECT2

[ ] Data Sovereignty Check
Acceptance criteria are fulfilled as described in in the following area on confluence:

Data Sovereignty Guardrails for Release 3.2 (Source only accessible for Catena-X Consortia members in current transition phase.)
Approval will be documented centrally by Expert(s)
Obtain approval from Data Sovereignty experts prior to Gate review: Experts will schedule a review with your team.

Expect optimization loops based on feedback.
Contact:

SYSTEM ARCHITECT3,
SYSTEM ARCHITECT4

[ ] Confirmation of published CX Standards
Product Owner confirms:

The FOSS product under review is compliant to all relevant Catena-X Standards which are already published on the Association website.
Failure to do so may ultimately make the reference implementation useless, as the mandatory CX Certification cannot be accomplished.

[ ] Verification of foreseen CX Standards
Product Owner confirms:

The content of upcoming CX Standardization Requests (STAN) has been reviewed and feedback was provided to the responsible PCA/BDA. As per current status, the FOSS product under review will be compliant as soon as the CX Standard is published. (Info here) (Source only accessible for Catena-X Consortia members in current transition phase.)
Minimum: PCA/BDA have finalized all release-relevant Standardization Requests (STAN). Those have passed the CX Association`s technical committee (TC4S) and are pre-published on the website. Opt-out period in progress.
Best case: Association Board approval available and CX Standard is published on website.

Hello  @jzbmw
Verification of foreseen CX Standards
IRS standard CX-0005 and CX-0045 is ready for review. Please confirm

No significant changes for this release. Focus for this release was on Agent KIT and new features that will not be released for 23.12

@TomBuchertTSystems kindly comment on the two points, whether you can confirm this for R23.12:

Verification of published CX Standards
Verification of foreseen CX Standards

@TomBuchertTSystems kindly reach out to @HiHenrik for the InterOp Assessment. You can prepare the CheckList: Interoperability Quality Gate Requirements

_"@TomBuchertTSystems kindly comment on the two points, whether you can confirm this for R23.12:
Verification of published CX Standards
Verification of foreseen CX Standards"_
Confirmed

@TomBuchertTSystems
For Data Sovereignty POs can do a self-declaration if products have not undergone any significant changes.
See Links (available to Consortia Members only)
2023-11-20 Stay informed & Release 23.12 & 24.03

@kelaja
Interoperability Check:
Acceptance criteria are fulfilled as described in in the following area on confluence:
https://confluence.catena-x.net/display/PL/Interoperability+Office+Hours+Backlog+-+QGate+Prep

I hereby declare that our product has not undergone any significant changes and therefore request approval for Data Sovereignty.


Install perl XML::Parser module on test machines

Since we want to update testKitGen to use standard XML parser to parse *.xml files, we need to install XML::Parser module on test machines.
XML Parser is in the Adopt Unix playbooks, but we need to make sure it is installed on all test machines. See comment from Adam:
https://github.com/eclipse/openj9/pull/499#issuecomment-438005342

I think cygwin installs this by default when also installing perl.  At least that appears to be the case on the systems that I have that are setup with the windows playbook.  /usr/lib/perl5/vendor_perl/5.26/x86_64-cygwin-threads/XML/Parser.pm is where its put.
But Strawberry perl is also a role on windows, which version is this needed under?  Which version of perl should be used for windows?

Close this issue as we are going to switch to use TKG for java soon. Perl module is no longer needed.


Support 103 Early Hints

[x] Feature Request. Start by telling us what problem you’re trying to solve. Often a solution
already exists! Don’t send pull requests to implement new features without first getting our
support. Sometimes we leave features out on purpose to keep the project small.

HTTP 103 Early Hints was just approved as a new response code. Are there any plans to offer support for it?

The programming model for early hints is substantially more complex. Rather than a single call yielding a single result it may now yield both an initial hints results and a later final result.
Building simple APIs around this will be difficult and I’m not in a particular rush to do so. If/when we do, it’ll probably take the form of some kind of extra callback.

Won't fix.

Any plans to reconsider this now that Cloudflare is rolling out support across a large chunk of the web? https://blog.cloudflare.com/early-hints/

The Cloudflare blog looks at using machine learning to automatically preload assets.  This leaves me with a couple of questions

Do we think typical mobile traffic, or really anything a Java/Android client would be fetching will follow the same patterns that are most obvious with HTML request followed by CSS, JS or Images.
Do you have a concrete example for your own clients where this will clearly improve the response rate, particularly considering that overeagerly fetching assets would cause excessive use of network bandwidth?

One thing to consider right now is that the way Cloudflare has implemented this, OkHttp errors out on the 103 request. I believe if you are using it for the sites that have it enabled, it gets stuck at response code 403 and unexpected bytes error at Exchange.kt.
I have been able to solve the reading right now, just working on making it ignore the 103 (Supporting 103 will probably be a longer process, and overly complicated at that, I believe most users would simply want their clients to work like they did before)

If anyone wants a solution that ignores 103 heres what I did
if (!(headerBlockLength != 0 && headerBlock[0].value.utf8().equals("103"))) { 		handler.headers(endStream, streamId, -1, headerBlock) }
I added that to readHeaders function, its a crude solution but it works :). I believe the idea is that the first responseCode is not the only one, and we should go off the last response code, does that make sense to anyone?

https://github.com/square/okhttp/commit/35f0dd9dbf2ae9ffcecc2b5fc86e11762a29bb4d
This is what it looks like all together, I have used this since November and had no issues, if anyone urgently needs to get past this issue I think this can be good for you. However I dont really know kotlin so I am not sure if there are any unseen implications of this,

The intent will be to support on 5.0 with clients notified of the early hints headers.
An early draft that is not 100% working https://github.com/square/okhttp/pull/7141
We should probably backport a similar approach to 4.9.x that ignores the headers.

https://datatracker.ietf.org/meeting/98/materials/slides-98-httpbis-early-hints-00

RFC 7231:
– (MUST) treat an unrecognized status code as
being equivalent to the x00 status code of
that class / the client can simply discard this
interim response (for 100 continue)
– a user agent MAY ignore unexpected 1xx
responses


Update to poetry to 1.0.10

A change in poetry 1.0.10 has changed how the git clone operation is performed. It now includes the --recurse-submodules option which wasn't there previously. This PR should superseed #2407.

This is fantastic, thanks @tomzx


Help with implementing YoloV5 and SparseML

Hello,
I have been trying to implement SparseML on YoloV5, and the Readme says there is a tutorial coming soon. Would you be able to give me some tips or a small tutorial on how to implement SparseML on YoloV5?

Would you be able to let me know know by when a sample recipe would be available?

I'm also trying to quantize a library called DeepSort, would you have any suggestions or resources I could look at to quantize it?
https://github.com/ZQPei/deep_sort_pytorch#training-the-re-id-model

Hi @PumeTu, definitely. Here are some short configs for YOLOv5L that haven't been heavily optimized for performance but should get you started in the right direction. Note, for any of the other v5 variants you'll need to adjust the params listed out in the quantization modules to add or subtract appropriately.
Quantization only, run with the fine tuning hyp:
version: 1.1.0
modifiers:
  - !EpochRangeModifier
    start_epoch: 0.0
    end_epoch: 3

  - !SetLearningRateModifier
    start_epoch: 0
    learning_rate: 0.0001

  - !SetLearningRateModifier
    start_epoch: 1
    learning_rate: 0.0032

  - !QuantizationModifier
    start_epoch: 1
    submodules:
      - model.0
      - model.1
      - model.2
      - model.3
      - model.4
      - model.5
      - model.6
      - model.7
      - model.8
      - model.9
      - model.10
      - model.11
      - model.12
      - model.13
      - model.14
      - model.15
      - model.16
      - model.17
      - model.18
      - model.19
      - model.20
      - model.21
      - model.22
      - model.23

Pruning only, run with the from scratch hyp:
version: 1.1.0
modifiers:
  - !EpochRangeModifier
    start_epoch: 0.0
    end_epoch: 240.0
  - !GMPruningModifier
    params: __ALL_PRUNABLE__
    init_sparsity: 0.25
    final_sparsity: 0.90
    update_frequency: 2.0
    start_epoch: 5.0
    end_epoch: 65.0

@PumeTu for the second question, we should be able to inject this SparseML sample code right after the creation of the optimizer here to enable recipes: https://github.com/ZQPei/deep_sort_pytorch/blob/master/deep_sort/deep/train.py#L68
from sparseml.pytorch.optim import ScheduledModifierManager

manager = ScheduledModifierManager.from_yaml(RECIPE_PATH)
optimizer = manager.modify(model, optimizer, steps_per_epoch=len(train_loader))

This will enable using the recipes for the training flows.


Loading tests and resources from archives (zip, egg, jar)

Originally submitted to Google Code by kai.hackemesser on 11 Mar 2010

Use case:
I want to use a resource file that I don't want to copy into the test
source tree as it is maintained and managed in another source repository,
another project.
Possible solution:
I could load it from a supplied zip file and add a library entry that
resolves into a zip file like Java's JarURL:
./lib/myResources.zip/!commons.html

for the python side it would be fabulous to load resources from python packages,
so one could make custom local packages and distribute them via an company internal pypi server (like devpi)

Sounds good to me. If someone is interested in working with this, I'm happy to help with design, review PRs, etc. There probably isn't enough time to get this into RF 2.9, but if there are no backwards incompatibility issues we can include it in RF 2.9.x and RF 3.0 is already planned for autumn.

i just noticed that it is already possible to do this by accident
since robotframework looks for ressources on the pythonpath, it's already possilbe to package Ressources, one simply needs to make a package with a init.py
in my oppinion the reuse of pythonpath is a bit problematic as a general design choice,
but its not clear if there is a better variant and how people should transition to it

Yes, looking resources from sys.path is not that clean solution. The fact that Python, Jython and IronPython all use different environment variables to configure it has also lead to problems like in #1983. As I commented in that issue, it would probably be a good idea to add environment variable ROBOTPATH and look resources from it instead. We probably should add its contents to sys.path, though, to be able to use that also to specify where libraries are located. That's definitely a topic for a separate issue, though.

could you create a appropriate issue for discussion of the handling of the different kinds of search path,
i'm not deep enough in the details to create a proper description

Just create an issue that makes sense from your point of view. We can update the title and even the description if needed. Or just create new one if we want something else.

Closing due to lack of interest in recent years. Can be reopened if someone actually want to implement this.

I've come to this issue looking for a way to manage test suites as versioned artifacts (zip, jar, egg) in a repository.  A workaround is to launch robot with a shell script that unpacks archives on first execution.  It would be slicker if the robot executable could run a test archive directly.  Is there an alternate best practice?


JSON Parse Error

There is a JSON Parse Error on load of directive.

Where?

I am using the plugin in my ionic project and I am getting a JSON parsing
error and a string unterminated error. I think it's in the find match
function which uses $sce.
On Tuesday, August 4, 2015, Hidenari Nozaki<EMAIL_ADDRESS>wrote:

Where?
—
Reply to this email directly or view it on GitHub
https://github.com/ghiden/angucomplete-alt/issues/220#issuecomment-127740386
.

--

Nathan
 Yeung
Coldwell Banker Apex, Realtors
®
7290 Virginia Parkway Suite 2400
McKinney, TX 75071
Cell:<PHONE_NUMBER>

JSON parsing is not part of this directive.
Please check to make sure the JSON you are getting is valid.

The JSON is valid the strict contextual evaluator runAsHtml function is
replacing the Characters in the regex expression
On Tuesday, August 4, 2015, Hidenari Nozaki<EMAIL_ADDRESS>wrote:

JSON parsing is not part of this directive.
Please check to make sure the JSON you are getting is valid.
—
Reply to this email directly or view it on GitHub
https://github.com/ghiden/angucomplete-alt/issues/220#issuecomment-127755433
.

--

Nathan
 Yeung
Coldwell Banker Apex, Realtors
®
7290 Virginia Parkway Suite 2400
McKinney, TX 75071
Cell:<PHONE_NUMBER>

Please create a jsbin or plnkr example.

How do I use the clearInput event?
On Tuesday, August 4, 2015, Hidenari Nozaki<EMAIL_ADDRESS>wrote:

Please create a jsbin or plnkr example.
—
Reply to this email directly or view it on GitHub
https://github.com/ghiden/angucomplete-alt/issues/220#issuecomment-127757430
.

--

Nathan
 Yeung
Coldwell Banker Apex, Realtors
®
7290 Virginia Parkway Suite 2400
McKinney, TX 75071
Cell:<PHONE_NUMBER>

Did you solve the issue?

The errors disappeared on our end
On Tuesday, August 11, 2015, Hidenari Nozaki<EMAIL_ADDRESS>wrote:

Did you solve the issue?
—
Reply to this email directly or view it on GitHub
https://github.com/ghiden/angucomplete-alt/issues/220#issuecomment-129985741
.

--

Nathan
 Yeung
Coldwell Banker Apex, Realtors
®
7290 Virginia Parkway Suite 2400
McKinney, TX 75071
Cell:<PHONE_NUMBER>


blockTillConversionComplete overflow when millis() is less than delms

I've had an issue using this library with an DB18B20 on the ESP8266 chipset.  It exhibits itself when you call DS18B20.requestTemperatures very soon after startup.  On the ESP8266 the millis() restarts at 0 every time you reset.  My goal is to take a reading and go back to sleep as soon as possible.  I was wondering why DS18B20.setWaitForConversion(true / false) had no effect in my code...
With reference to the code block below if millis() is less than delms I believe that there is an overflow bug.  millis() is an unsigned integer and it overflows.  millis() - delms is always greater than now and execution continues regardless of what isConversionComplete() is.
// Continue to check if the IC has responded with a temperature
void DallasTemperature::blockTillConversionComplete(uint8_t bitResolution) {
int delms = millisToWaitForConversion(bitResolution);
if (checkForConversion && !parasite) {
unsigned long now = millis();
while (!isConversionComplete() && (millis() - delms < now))
;
} else {
delay(delms);
}
}
I changed the while statement to:
while (!isConversionComplete() && (millis() - now < delms))
yield();
Note that I think (please correct me if I'm wrong) this statement change also correctly protects against millis() wrap-around.
I added the yield(); because on long 12-bit conversions circa. 750ms the ESP8266 watchdog soft-resets without it.

The wrap around of millis occurs after ~50 days  but still worth to check this issue.
suppose millis() wraps at 1000 ( to make the analysis easier) and that delms = 10
scenario
unsigned long now = millis();      // now = 995 - close near wrap around value of millis()

(millis() - delms < now)
995 - 10 = 985 < 995 => true
996 - 10 = 986 < 995 => true
997 - 10 = 987 < 995 => true
...
004 - 10 = 994 < 995 => true
005 - 10 = 995 < 995 => false	=> so fall through
006 - 10 = 996 < 995 => false	=> so fall through
...
009 - 10 = 999 < 995 => false	=> so fall through
010 - 10 = 0 < 995 => true 		=> !!!!
...
994 - 10 = 984 => true ...

(millis() - now < delms)
995 - 995 = 0 < 10 => true
996 - 995 = 1 < 10 => true
997 - 995 = 2 < 10 => true
...
004 - 995 = 9 < 10 => true
005 - 995 = 10 < 10 => false		=> so fall through
006 - 995 = 11 < 10 => false		=> so fall through
...
009 - 995 = 14 < 10 => false		=> so fall through
010 - 995 = 15 < 10 => false		=> so fall through
...
994 - 995 = 999 < 10 => false

So indeed the original code fails when we have a wrap around of millis() and the time between two subsequent calls to the test condition is so large that millis() has become larger than delms.
As delms is at least ~90 milliseconds, the chance the existing code fails is pretty low.
That said your proposed code is correct and better than the existing code.
The addition of yield() in the while loop should be no problem as far as I can see.
Can you make a pull request?

One should replace
		unsigned long now = millis();
		while (!isConversionComplete() && (millis() - delms < now))
			;

by
		unsigned long start = millis();
		while (!isConversionComplete() && (millis() - start < delms))
			;

Whether millis() overflows or not, (millis() - start) will be still calculated correctly as long as delms is not more than 49 days which is uncommon for a cable connection. ;-)
For example if start=4294967291 (which corresponds to -5 if considered as a signed integer), after 20 milliseconds millis() will give 15; 15-4294967291 = 20 (mind the overflow!) - correct value. We can always compare it with "delms".


Inaccurate claim that structs are immutable

String data type is a struct in Swift, therefore it is immutable.

This doesn't really make sense. Immutability simply depends on the use of let vs var and that has nothing to do with the String type. String even has mutating methods such as append(_:) and insert(_:atIndex:).

I think it should be value type instead of immutable. I'll check more about String type.
Thank you @timvermeulen

Fixed here https://github.com/crowdsourcebooks/theswiftbook/commit/20c31bc25d952922546ffabcdfc8488e751d58f4
Thanks for the feedback


Modbus over serial

Hi,
I understand node-red-contrib-modbus only supports modbus over TCP.
I need to deploy an application where connections are performed over a serial line.
I believe jsmodbus already supports serial connections, so the only missing part would be to add the node-red wrapper for it.
Is such a feature planned at all? If I were to implement this myself, would this be a welcome feature?
Any suggestions on how to proceed?
Thank you!

There were no more time to develop that feature and nobody asked for it until now. I'll start to develop that.

Hi,
I'm willing to contribute and I just started playing with it, though I am a newbie as far as github, node.js and node-RED are concerned.
Is there a quick way to get your feedback (in a gerrit-like workflow) without causing even more burden on your part?
Pushing draft changes to a forked github repo and issuing a pull request sounds a bit like overkill to me (especially at this stage where I'm not quite sure what I'm doing and it's very likely there's something wrong or missing...).
Thank you!

Hi, the best way is to fork this repo, develop your part, and send a pull request to my repo from your forked repo. I'll do the review of your code and some tests and then we'll release if it works ;)
start here: http://nodered.org/docs/creating-nodes/

Done! See pull request #2 .
I guess I should've mentioned the issue in the commit message.
Feel free to shoot if there's something obviously wrong (no need to be polite...). :-)

please pull again and test ...

working well on a serial modbus software server

see v0.6.0 and above


Separate routers to smaller packages

I am not so sure about this as in case of drivers, but could be a possibility too.

I don't think the routers need to moved to separate packages. For the drivers this is indeed a "natural" choice, but don't need this approach IMHO

In my opinion everything that has an external dependency should be removed from the core library. Optional dependencies destroy the whole point of having dependencies IMO and should be avoided whenever possible. In an optimal case we can have at least a few implementations of drivers and routers which does not have an external dependency, so the core library remains functional.

Most of the vendor container routers are going to be removed, so this can be closed.


[WFLY-14944] Use Phase constants for MP RM and RSO deployers

https://issues.redhat.com/browse/WFLY-14944
This needs a WFCORE version containing https://github.com/wildfly/wildfly-core/pull/4641

/retest


[SPARK-45793][CORE] Improve the built-in compression codecs

What changes were proposed in this pull request?
Currently, Spark supported many built-in compression codecs used for I/O and storage.
There are a lot of magic strings copy from built-in compression codecs. This issue lead to developers need to manually maintain its consistency. It is easy to make mistakes and reduce development efficiency.
Why are the changes needed?
Improve some code for storage compression codecs
Does this PR introduce any user-facing change?
'No'.
How was this patch tested?
N/A
Was this patch authored or co-authored using generative AI tooling?
'No'.

The GA failure is unrelated

Merged to master
@dongjoon-hyun Thank you!


[Feature] Add Scratchpad

Problem
I'd like to have one place for just random things I need to jot down and daily to-dos.
Suggested Approach
A main section of the sidebar, along with "All Notes", "Favorites" and "Trash" called "Scratchpad" that only has one note. That way, it's very easy to find this note of randomly jotted content. Name is debatable, but it's the best one I thought of so far.

I can do this

Closed in #280


Loading icons from remote URL does not work

Describe the bug
Loading icons from remote URL does not work.
To Reproduce
Icon(XIconData.fromUri("https://example.com/icon.svg"))

Expected behavior
Render remote icon
Screenshots
Desktop (please complete the following information):

OS: all
Browser: all

Smartphone (please complete the following information):

Device: all
OS: all
Browser: all

Additional context

XIcon(XIconData.fromUri(
              "https://raw.githubusercontent.com/bridgedxyz/dynamic/master/flutter/packages/x_icon/doc/remote-icon-example/twotone_brightness_auto_black_18dp.png"));

here is the working example.
more example can be found from here

https://github.com/bridgedxyz/dynamic/blob/master/flutter/packages/x_icon/example/lib/main.dart

It looks that when I use flutter_remote_icon package it does not work, I will try with x_icon

@alhafoudh  Yes, the flutter_remote_icon is not updated, we migrated the same functionality to x_icon, and will be updated on x_icon


Electron-rebuild OK, but serialport doesn't work on Win7

Summary of Problem
I'm trying to deploy my Electron app on Mac and windows. My app include node serial-port.
When I run electron-rebuild, all goes well.
After creating the .exe with this command:
electron-packager . test --arch=ia32 --platform=win32
I got this error after running the exe:
Uncaught Error<EMAIL_ADDRESS>is not a valid Win32 application.
<EMAIL_ADDRESS>at process.func (electron/js2c/asar.js:155)
at process.func [as dlopen] (electron/js2c/asar.js:155)
at Object.Module._extensions..node (internal/modules/cjs/loader.js:828)
at Object.func (electron/js2c/asar.js:155)
at Object.func [as .node] (electron/js2c/asar.js:155)
at Module.load (internal/modules/cjs/loader.js:645)
at Function.Module._load (internal/modules/cjs/loader.js:560)
at Module.require (internal/modules/cjs/loader.js:685)
at require (internal/modules/cjs/helpers.js:16)
at bindings (C:\Users\Matteo\DeskÖngs\bindings.js:112)
Versions, Operating System and Hardware

<EMAIL_ADDRESS>Node.js v?12.16.0
Windows 7 64 bit SP1 (running on VM under MacosX High Sierra

The OS is 64 bit so electron-packager seems can build only apps in 64 bit, in fact the exe run if it was builded in 64 bit.


ASTContext: Add a utility to retrieve the '+' function decl for RangeReplaceableCollection in the stdlib. NFC

@Kacper20 may need this in implementing #11944

@swift-ci please smoke test


Issue with 'relates" relation

Hello,
first of all, thank you for your job!
I'm using redmine version : 4.0.4 and the api in version <IP_ADDRESS> (nugets current version).
I think there is a bug with IssueRelation creation.
There is the payload sent by the api :
<relation> <issue_to_id>foo</issue_to_id> <relation_type>Relates</relation_type> </relation>
With that the server responds with an error (confirmed with postman).
Now with postman if I replace Relates by relates, according to the documentation --> It works.
Could you analyse this issue ?
Thanks

hi @charettemtb,
I'm experiencing the same issue and updated my PR #264.
Let's wait for @zapadi's feedback.


Add ability to create top issues dashboard on discussion discussion board

Is your feature request related to a problem? Please describe.
Currently, the top issues dashboard is placed under the issues tab. It would be great if an option allowed users to place it as a 💬 General discussion item.
Describe the solution you'd like
Adding a dashboard_location action input in which users can choose between issues and discussion would improve the action.

I decided not to implement this at the current time because I don't need it on my own repositories. However, I'm happy to review a pull request if somebody wants to tackle this 👍🏻.


Add GPU-enabled version to conda

This is a feature request to enable GPU processing in the conda version of dspsr.  This would be useful for speeding up processing, especially when working with baseband data.

I looked into this a few years ago and did not end up doing it, I don't remember why.  Possibly was just not sure if there would be much demand.  I can give it a try sometime soon.
The information here seems pretty straightforward https://conda-forge.org/docs/maintainer/knowledge_base/#cuda-builds
And I might want to split the package into two flavors (CPU-only and GPU), there is some more info about this here https://conda-forge.org/docs/maintainer/knowledge_base/#multi-output-recipes