Add Tuya TZE204_pcdmj88b and _TZE204_g2ki0ejr TRV support

Proposed change
This PR add support of device _TZE204_pcdmj88b and device _TZE204_g2ki0ejr.
Fixes https://github.com/zigpy/zha-device-handlers/issues/2706
Checklist

[X] The changes are tested and work correctly
[ ] pre-commit checks pass / the code has been formatted using Black
[ ] Tests have been added to verify that the new code works

Hi,
I have started to use and test this quirk.
First of all, thanks for your work and contribution.
Secondly, I do have couple of issues here. So the device does not expose the entity that could be used just to set the temperature.
What it actually expose is pair of values - current and target temperature (screenshot attached).

I think, there should be just two separate entities/fields that could be single numbers that represent those values.
Why would I need it? I wanted to build automation, where I set target temperature to be 22C starting 8:00AM. Right now, I think, I cannot do it, because I cannot just set 22C via the automation.
Another issue, that I think would be worth to tackle is ability to "partially" open the valve. Right now, I think, when too low temp is detected, the thermostat is just opened to the max position.
But maybe, both of these issues could be tackled within separate pull request. I could try to play around with it (based on your work) and maybe find a way for both of these. However, I am newbie in ZHA quirks, so I can't promise, I will deliver it soon :/.
Last issue is with mode switch  - I have no idea, what it should do...but it looks like it does not work. Whenever I am switching it, after few seconds it gets back to the previous value. In the device log, I do not see any event related to that change neither.

Hello @psikorski,
The quirks is integrated like it should be because it's a "thermostat"... not 2 devices, so it's normal to have this representation in Home Assistant.
Now, for my home, i have setup the scheduler for Home Assitant in order to change temperature (week-end or work-day).
You can found more information at this link: https://community.home-assistant.io/t/scheduler-card-custom-component/217458
I hope it will help you :)

@Teka101 , thanks - it works. Now I understand the reasoning and a way of controling the temperature.
What about the valve opening? I undestand, that this is not part of climate.thermostat API....That means, that I would need to somehow extend this API, if I need it.
And what about this switch marked? what is it and how should it work?

@psikorski for both hardware there is no valve reporting, it's only "open" or "closed".
In home assistant, you should see "idle" or "heating" for your thermostats.
The switch is for "boost mode" but i don't known if it's working or not (i just turn off few second avec turn on...)

And what about this switch marked? what is it and how should it work?

There are two switch entities. The first one is for the heat lock (which lasts ~5'), the second one is the "window check" feature.

Hey there,
also HUGE thanks from me for this contribution / work!! I was able to add these thermostats here from AliExpress using this custom quirk: https://www.aliexpress.com/item/1005006092397271.html
That's how it shows up for me in HA:

And that's (just for completion) is the device's signature:
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4417, 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=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": "0x0104",
      "device_type": "0x0301",
      "input_clusters": [
        "0x0000",
        "0x0001",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x000d",
        "0x0201",
        "0x0204",
        "0xef00"
      ],
      "output_clusters": [
        "0x000a",
        "0x0019"
      ]
    },
    "2": {
      "profile_id": "0x0104",
      "device_type": "0x0007",
      "input_clusters": [
        "0x0006"
      ],
      "output_clusters": []
    }
  },
  "manufacturer": "_TZE204_pcdmj88b",
  "model": "TS0601",
  "class": "ts0601_trv_tze204.PcdmTrv"
}

Generally, it works and I can set the temperature, it reports the temperature and the switches do "something" (at least don't throw an error).
However. I do have one issue to report though:
If I try to set values for the "min/max heat setpoint", I get the below error:

Not sure if the device actually supports this (and it's broken), or if it doesn't and therefore the controls should not be shown.
Can I do something else for testing? You need some debug or other support for this PR? Happy to help!
Greetings,
Andy!

Hello @ezcGman

If I try to set values for the "min/max heat setpoint", I get the below error:

Theses values come from technical specs of this devices, so it's readonly :)

Hello @ezcGman

If I try to set values for the "min/max heat setpoint", I get the below error:

Theses values come from technical specs of this devices, so it's readonly :)

Right, but then they shouldn't be rendered as input fields. Is that a task/bug for HA? Sorry for the maybe dumb question :)

Right, but then they shouldn't be rendered as input fields. Is that a task/bug for HA? Sorry for the maybe dumb question :)

Huuu good question, it's a new feature from HomeAssistant (v2014.1.5 don't expose limit on my installation), so i don't know if it's okay to have "readonly" here ...


feat: Add API v2 finding samples

Description
Fixes #https://buganizer.corp.google.com/issues/333521328
Note: Before submitting a pull request, please open an issue for discussion if you are not associated with Google.
Checklist

[x] I have followed Sample Format Guide
[ ] pom.xml parent set to latest shared-configuration
[ ] Appropriate changes to README are included in PR
[ ] These samples need a new API enabled in testing projects to pass (let us know which ones)
[ ] These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
[x] Tests pass:   mvn clean verify required
[x] Lint  passes: mvn -P lint checkstyle:check required
[ ] Static Analysis:  mvn -P lint clean compile pmd:cpd-check spotbugs:check advisory only
[ ] This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
[ ] This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
[ ] Please merge this PR for me once it is approved

@rafaelMurata PTAL

@Sita04
done

gcbrun

@Sita04
please run kokoro again. Thanks.


Remove outdated externs

According to https://developers.google.com/gadgets/docs/basic,
writing OAuth gadgets is no longer supported.
According to https://developers.google.com/maps/articles/v2tov3,
Version 2 of the Google Maps JavaScript API is no longer available.

The oauth file is still needed. Working on deleting the other one internally.


UN Dataset preprocessed request

Thanks for the awesome repo. I just want to request the preprocessed UN General Debates dataset for  the dynamic topic modeling problem.
Thanks in advance!

Hi, the UN dataset has been uploaded.

Thanks


uucore/perms: correct some error messages

prevent duplicate errors from both us and walkdir by instructing `walkdir'
to skip directories we failed to read metadata for.
don't directly display walkdir's errors, but format them ourselves to
match gnu's format

I expect this to pass one more gnu test for chgrp.

Indeed
Warning: Changes from master: PASS +1 / FAIL -1 / ERROR +0 / SKIP +0


renode-dts2repl: 0-unstable-2024-09-20 -> 0-unstable-2024-09-27

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for renode-dts2repl is: Tool for converting device tree sources into Renode's .repl files
meta.homepage for renode-dts2repl is: https://github.com/antmicro/dts2repl
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0-unstable-2024-09-27 in filename of file in /nix/store/szqikhcsr6alyxbvzv64vb7c8a8bg26q-renode-dts2repl-0-unstable-2024-09-27

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

renode-dts2repl

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/szqikhcsr6alyxbvzv64vb7c8a8bg26q-renode-dts2repl-0-unstable-2024-09-27 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/cb805349a7a12ac1096f4b470cdfe0d122d2ffb1#renode-dts2repl

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/szqikhcsr6alyxbvzv64vb7c8a8bg26q-renode-dts2repl-0-unstable-2024-09-27
ls -la /nix/store/szqikhcsr6alyxbvzv64vb7c8a8bg26q-renode-dts2repl-0-unstable-2024-09-27/bin

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

2 packages built:

renode-dts2repl
renode-dts2repl.dist

Maintainer pings
cc @otavio for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

@NixOS/nixpkgs-merge-bot merge


[wip]Notification Subscription

这个 PR 实现什么功能/修复什么问题:

[x] 功能、bugfix描述
[x] 冒烟测试

是否需要 backport 到之前的 release 分支:

release/3.7

/area notify cloudcommon region glance

/area notify region

/area notify region

Codecov Report

Merging #9904 (d7a49cc) into master (53651de) will increase coverage by 2.10%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #9904       +/-   ##
==========================================
+ Coverage    5.97%   8.07%    +2.10%
==========================================
  Files         849     107      -742
  Lines      132172   12993   -119179
==========================================
- Hits         7895    1049     -6846
+ Misses     123576   11824   -111752
+ Partials      701     120      -581

Flag
Coverage Δ

aFlag
8.07% <100.00%> (+2.10%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/util/bitmap/bitmap.go
38.23% <100.00%> (+3.86%)
:arrow_up:

pkg/compute/models/groupguests.go

pkg/util/rbacutils/policygroup.go

pkg/mcclient/options/schedtags.go

pkg/mcclient/options/k8s/storageclass.go

pkg/multicloud/aws/securitygroup.go

pkg/cloudcommon/validators/validators_string.go

pkg/multicloud/aws/loadbalancerbackend.go

pkg/compute/models/helper.go

pkg/monitor/tsdb/models.go

... and 724 more

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 53651de...d7a49cc. Read the comment docs.

Codecov Report

Merging #9904 (d7a49cc) into master (53651de) will increase coverage by 2.10%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master   #9904       +/-   ##
==========================================
+ Coverage    5.97%   8.07%    +2.10%
==========================================
  Files         849     107      -742
  Lines      132172   12993   -119179
==========================================
- Hits         7895    1049     -6846
+ Misses     123576   11824   -111752
+ Partials      701     120      -581

Flag
Coverage Δ

aFlag
8.07% <100.00%> (+2.10%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/util/bitmap/bitmap.go
38.23% <100.00%> (+3.86%)
:arrow_up:

pkg/compute/models/groupguests.go

pkg/util/rbacutils/policygroup.go

pkg/mcclient/options/schedtags.go

pkg/mcclient/options/k8s/storageclass.go

pkg/multicloud/aws/securitygroup.go

pkg/cloudcommon/validators/validators_string.go

pkg/multicloud/aws/loadbalancerbackend.go

pkg/compute/models/helper.go

pkg/monitor/tsdb/models.go

... and 724 more

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 53651de...d7a49cc. Read the comment docs.


Add required, science and search commands and edit minor details of the UG

-Added Required, Science and Search commands into the feature list, features and command summary portion.
-Edited some words and phrasings to make the language of the UG more consistent.
NOTE
Have not added supporting images for the Required, Science and Search commands so as to maintain image consistency throughout the UG.
You can view the updated UG over here:
https://github.com/yan-soon/tp/blob/update-ug/add-required-and-search-command/docs/UserGuide.md

Codecov Report

Merging #117 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #117   +/-   ##
=========================================
  Coverage     74.12%   74.12%
  Complexity      487      487
=========================================
  Files            83       83
  Lines          1461     1461
  Branches        152      152
=========================================
  Hits           1083     1083
  Misses          306      306
  Partials         72       72

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 ab673a3...3dcd53d. Read the comment docs.


Exit server if port is not bindable

For comparison I also looked at the python version which also exits if it cannot bind the port.
There are probably more cases where an Exit is more appropriate than a return. However this is the one that causes me problems right now.

I've cherry-picked your modification into current develop branch.


Maximum call stack size exceeded with Watchify

I've been stumped on this error for a long time. I've pasted my browserify config below for reference.
Replication:
When I start the task, the bundle is compiled initially. In the browser, it loads nicely, clean of errors. After I save a watched file, however, it rebundles successfully, but Maximum call stack size exceeded error appears in the console and none of my changes appear.
If I disable the watch: true option, it works correctly. I think the issue is with Watchify adding some of the required files twice, causing the error.
 browserify: {
      front_js: {
        files: {
          'public/js/build/bundle.js': ['public/js/src/**/*.jsx']
        },
        options: {
          bare: true,
          alias: [
            './public/js/lib/react/react-with-addons.js:react',
            './public/js/lib/flux/index.js:flux',
            './public/js/lib/react-router/dist/react-router.js:react-router',
            './public/js/lib/lodash/lodash.js:lodash'
          ],
          transform: [ require('grunt-react').browserify ],
          watch: true,
          keepAlive: true
        }
      }
    }

Any ideas?

Hmm.. Never had this issue before, even with big projects.
I don't see anything incorrect in your config...
Could you give us more info?

I have the same issue. The behaviour is exactly as derek-duncan described in Replication paragraph.
The difference is i am using gulp.
There is one more thing that could possible cause the issue. I have gulp tasks defined in ./tasks path relative to gulpfile.js.

I created a repo with clean reproduction using gulp, browserify, watchify.
There are two branches:

one, where tasks are defined within gulpfile.
other, where tasks defined in separate folder.

In fact it occured that it does not matter. The last commit in each branch introduces the error.
To be precise browserify.require causes the error.
One more thing, there is difference in bundle.js file after running gulp task and after rebundle. Seems it can tell much about origin of the issue. The difference is in several latter bundle.js lines.
Bundle.js tail after  first run
<...>
exports.is = {
  number: isNumber
};

},{}]},{},["./src/main.js"]);

Bundle.js tail after rebundle
<...>
exports.is = {
  number: isNumber
};

},{}],"utils":[function(require,module,exports){
arguments[4]["utils"][0].apply(exports,arguments)
},{}]},{},["./src/main.js"]);

i included common exports.is = ... part to give little more context to snippets.

I understand that it is grunt-browserify thread and i am sorry for interrupting with my gulpish code.
And i understand that issue can be caused by mistreatment of browserify/watchify, i mean call order or some options could be wrong.
But the issue still throws sand in the wheels! So any help would be much appreciated! :pray:

Looked through watchify issues.
Seems these could be correlated. All of these issues are about watchify + .require.
substack/watchify#72
substack/watchify#74
substack/watchify#130
substack/watchify#148
It seems that watchify does not play well with .require and .external. I did not find the solution though. :disappointed:

@ggarek I am seeing the exact same issue using Gulp and Watchify. Works fine first build, then after a change triggers a rebuild via watchify, I get the maximum call stack size exceeded error. I am working around the issue by just not using watchify and triggering a rebuild with gulp-watch, but this is obviously much slower. Did you make any headway?

It seems to be a bug with watchify then.

I was able to avoid this issue with two bundles: main and vendor. Put all of your dependancies inside the vendor bundle and do not run watchify on it (sometimes double inserts when required). You should rarely be changing the vendor dependencies, so just rebuild it when you do.

@derek-duncan
Yeah, this will work for vendor libs, but it wont work with your own libs that are logically external for main package.
E.g. i have single repo with client and server packages and there are several shared libs, so while working on client for example i might need to fix a shared lib.. you see.
@tleunen yeah it is, and it seems there is no work on this issue going on.
@jslatts i ended up with same gulp-watch slowiiish approach, that`s sad. :disappointed:

+1.
Faced the same issue using dialog-component and component-tip in the project. The components use stringify and html-browserify transforms to precompile templates.
First time I launch watchify it compiles the whole project correctly, and if I change anything within the nested requirement (feedback.js), I get Maximum call stack size exceeded.
The structure of dependencies looks like:
index.js
- component-tip
- ./feedback.js
  - dialog-component

I've come up with watch 'npm run build' '.' --wait=1 command, using watch, and it seems to be a nice workaround.

We ran into this problem a while back after our build had more than 200+ files.
The fix was:
echo 'kern.maxfiles=20480' | sudo tee -a /etc/sysctl.conf && echo -e 'limit maxfiles 8192 20480\nlimit maxproc 1000 2000' | sudo tee -a /etc/launchd.conf && echo 'ulimit -n 4096' | sudo tee -a /etc/profile


Replace CLI link with a link to the Mintlayer CLI

To the actual code?

To the actual code?

Nope, just to the documentation, when it becomes existent.


Fix object nesting for selectQueryOrMutationField option on openAPI handler

Description
Currently, the OpenAPI handler uses loadsh to build the object for selectQueryOrMutationField option to be passed to openapi-to-graphql.
The problem is that loadsh's set has a nesting behavior which, for example, nests fields splitting by a “dot” character.
When you have a configuration like this:
        selectQueryOrMutationField:
          - title: "Weather Service v1.0"
            path: /weather/current
            method: post
            type: Query
          - title: "Weather Service v1.0"
            path: /weather/forecast
            method: get
            type: Mutation

It gets currently parsed by lodash like this:
  "selectQueryOrMutationField": {
    "Weather Service v1": [
      {
        "/weather/current": {
          "post": 0
        },
        "/weather/forecast": {
          "get": 1
        }
      }
    ]
  },

Whilst it should be parsed as follow:
  "selectQueryOrMutationField": {
    "Weather Service v1.0": {
      "/weather/current": {
        "post": 0
      },
      "/weather/forecast": {
        "get": 1
      }
    }
  },

As you can see loadsh nests the OAS title into an array of objects, rather than just an object with "paths" as keys.
It does this because the title contains a dot.
As you can also notice the ".0" is also removed from the title.
This means that the config is not passed correctly to openapi-to-graphql and so it won't work.
My fix addresses this by removing lodash dependency and merging objects in "reduce" with plain javascript, using spread.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] I have followed the CONTRIBUTING doc and the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] ~I have commented my code, particularly in hard-to-understand areas~
[ ] ~I have made corresponding changes to the documentation~
[x] My changes generate no new warnings
[ ] ~I have added tests that prove my fix is effective or that my feature works~
[x] New and existing unit tests and linter rules pass locally with my changes
[ ] ~Any dependent changes have been merged and published in downstream modules~

Thank you @santino !


fix typos

src/Development/Ninja/Type.hs
src/Development/Shake/Database.hs
src/Development/Shake/Internal/Args.hs
src/Development/Shake/Internal/Core/Database.hs
src/Development/Shake/Internal/Rules/Files.hs
src/General/Extra.hs
src/Test/BuiltinOverride.hs

@ndmitchell
src/Test/BuiltinOverride.hs
seems like a newline was added in the commit

Thanks! I'm fine with a trailing newline (in fact, I'd prefer it)


Improve in_app detection

Currently it marks all frames as in application in many conditions.
For example, one app their entire code has absolute paths that are all like /app/foo/XXX/...
The solution is likely to add in a source root configuration option, and when that is set prepend the app detect with that path.
(We should also remove the absolute detection in in_app, and only check for relative app/* etc paths)

I'm pretty satisfied with this behavior r/n.


Try mixins strategy for backends

Once the refactor is done, backends will be just simple wrappers for connecting with the underlying clients like aioredis, aiomcached, dict, etc.
Try to think of a mixins approach in order be able to call the client commands as if you were using it straightforward.

Closing this since #72 is a good enough design for now


Preferred Bulgarian language missing in iOS

Hello,
Since you don't have an official email I can submit mu feature/bug request I am forced to done it here.
For some reason in Google Maps Bulgarian language missing as a preferred option.
Are you able to add it ?
If this  is not the right place please reroute the ticket to the rights and responsible persons for this!
Thank you in advance.

If you would like to upvote the priority of this issue, please comment below or react with :+1: so we can see what is popular when we triage.
@Arkadietz Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
Open a support case - Get 1:1 support in Cloud Console.
Discord - chat with other developers
StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.

If you would like to upvote the priority of this issue, please comment below or react with 👍 so we can see what is popular when we triage.
@Arkadietz Thank you for opening this issue. 🙏 Please check out these other resources that might help you get to a resolution in the meantime:
* [Check the issue tracker](https://developers.google.com/maps/support/#issue_tracker) - bugs and feature requests for Google Maps Platform APIs and SDKs

* [Open a support case](https://developers.google.com/maps/support#contact-maps-support) - Get 1:1 support in Cloud Console.

* [Discord](https://discord.gg/fHTDmZe9En) - chat with other developers

* [StackOverflow](http://stackoverflow.com/questions/tagged/google-maps) - use the `google-maps` tag

This is an automated message, feel free to ignore.

It's already done this.
https://issuetracker.google.com/issues/284710962

@Arkadietz Please submit your feedback about preferred language support in Google Maps using these instructions: https://support.google.com/maps/answer/3094045?hl=en&co=GENIE.Platform%3DiOS&oco=1


Crash during sync in color-spantrace due to an incorrect local path

Dec 02 10:47:56.383  INFO {zebrad="0f3760ff"}:peer{addr=<IP_ADDRESS>:3233}:msg_as_req{msg=getheaders}:inbound:state: zebra_state::service: responding to peer GetBlocks or GetHeaders final_height=Height(77486) response_len=160 chain_tip_height=Height(78896) stop_height=None intersection_height=Some(Height(77326))
Dec 02 10:47:56.635  INFO {zebrad="0f3760ff"}:peer{addr=<IP_ADDRESS>:8233}:msg_as_req{msg=getheaders}:inbound:state: zebra_state::service: responding to peer GetBlocks or GetHeaders final_height=Height(49973) response_len=160 chain_tip_height=Height(78896) stop_height=None intersection_height=Some(Height(49813))
Dec 02 10:47:56.812  INFO {zebrad="0f3760ff"}:peer{addr=<IP_ADDRESS>:8233}:msg_as_req{msg=getheaders}:inbound:state: zebra_state::service: responding to peer GetBlocks or GetHeaders final_height=Height(40053) response_len=160 chain_tip_height=Height(78896) stop_height=None intersection_height=Some(Height(39893))
Dec 02 10:47:56.980  INFO {zebrad="0f3760ff"}:peer{addr=<IP_ADDRESS>:8233}:msg_as_req{msg=getheaders}:inbound:state: zebra_state::service: responding to peer GetBlocks or GetHeaders final_height=Height(73006) response_len=160 chain_tip_height=Height(78896) stop_height=None intersection_height=Some(Height(72846))
Dec 02 10:47:57.281  INFO {zebrad="0f3760ff"}:peer{addr=[2a02:c207:2022:9236::1]:8233}:msg_as_req{msg=getheaders}:inbound:state: zebra_state::service: responding to peer GetBlocks or GetHeaders final_height=Height(77806) response_len=160 chain_tip_height=Height(78896) stop_height=None intersection_height=Some(Height(77646))

Error
called `Result::unwrap()` on an `Err` value: Os { code: 20, kind: Other, message: "Not a directory" }

Metadata

key
value

version
3.0.0-alpha.0

git commit
0f3760ff

location
/Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/color-spantrace-0.1.4/src/lib.rs:207:29

Backtrace

Backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.54/src/backtrace/libunwind.rs:90:5
      backtrace::backtrace::trace_unsynchronized
             at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.54/src/backtrace/mod.rs:66:5
   1: backtrace::backtrace::trace
             at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.54/src/backtrace/mod.rs:53:14
   2: backtrace::capture::Backtrace::create
             at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.54/src/capture.rs:176:9
   3: backtrace::capture::Backtrace::new
             at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.54/src/capture.rs:140:22
   4: color_eyre::config::PanicHook::panic_report
             at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/color-eyre-0.5.8/src/config.rs:773:18
   5: color_eyre::config::PanicHook::into_panic_hook::{{closure}}
             at /Users/rex/.cargo/registry/src/github.com-1ecc6299db9ec823/color-eyre-0.5.8/src/config.rs:752:29
   6: std::panicking::rust_panic_with_hook
             at /rustc/1c389ffeff814726dec325f0f2b0c99107df2673/library/std/src/panicking.rs:595:17
   7: std::panicking::begin_panic_handler::{{closure}}
             at /rustc/1c389ffeff814726dec325f0f2b0c99107df2673/library/std/src/panicking.rs:497:13
   8: std::sys_common::backtrace::__rust_end_short_backtrace
             at /rustc/1c389ffeff814726dec325f0f2b0c99107df2673/library/std/src/sys_common/backtrace.rs:141:18
   9: rust_begin_unwind
             at /rustc/1c389ffeff814726dec325f0f2b0c99107df2673/library/std/src/panicking.rs:493:5
  10: core::panicking::panic_fmt
             at /rustc/1c389ffeff814726dec325f0f2b0c99107df2673/library/core/src/panicking.rs:92:14
  11: core::option::expect_none_failed
             at /rustc/1c389ffeff814726dec325f0f2b0c99107df2673/library/core/src/option.rs:1268:5
  12: core::result::Result<T,E>::unwrap
             at /Users/rex/.rustup/toolchains/nightly-x86_64-apple-darwin/lib/rustlib/src/rust/library/core/src/result.rs:973:23

@yaahc it looks like something's wrong with the backtraces here, since the backtrace has no information about the caller of unwrap.

@yaahc it looks like something's wrong with the backtraces here, since the backtrace has no information about the caller of unwrap.

This is just a raw backtrace so it shouldn't be discarding information, don't know what is going on there.
The location in the metadata at least caught it. The culprit is color-spantrace trying to resolve source files to include when printing a SpanTrace. This is an error that I haven't encountered before but it seems fine. I already had an error case to handle when a file isn't found. Apparently when one of the directory components of a path other than the final file doesn't exist std::io::Error in all of its wisdom returns an entirely different error kind. Just need to patch color-spantrace to have this extra branch for ignoring errors when resolving files:
        let file = match File::open(filename) {
            Ok(file) => file,
            Err(ref e) if e.kind() == ErrorKind::NotFound => return Ok(()),
            Err(ref e) if e.kind() == ErrorKind::Other && e.raw_os_error() == Some(20) => {
                return Ok(())
            }
            e @ Err(_) => e.unwrap(),
        };

actually, nvm, I'm just gonna blanket ignore errors here, I don't think there are any io errors we could encounter here that we actually care about.

actually, nvm, I'm just gonna blanket ignore errors here, I don't think there are any io errors we could encounter here that we actually care about.

Good idea, different OSes might also return different errors for the same underlying filesystem issue.


Update Idefics2Config with processor_kwargs

The Idefics2Config class has been updated to include a new attribute processor_kwargs which allows for additional keyword arguments to be passed to the processor. This change enables more flexibility in configuring the processor for the model.
The parameter do_image_splitting is removed from the Idefics2Config since it can be set through processor_kwargs as well.

This looks good to me. I have not tested with any app and is assuming the tests is already covering it.


fix(examples): package-lock.json might have been generated with node@16 breaking node@14 user build

Bug description
See https://github.com/awslabs/aws-lambda-powertools-typescript/pull/326#issuecomment-1018930741
Expected Behavior
TBD
Current Behavior
TBD
Possible Solution
TBD
Steps to Reproduce
TBD
Environment

Powertools version used: 0.4.0
Packaging format (Layers, npm): npm
Debugging logs: TBD

Related issues, RFCs
#326
https://github.com/awslabs/aws-lambda-powertools-typescript/pull/501

Were you able to reproduce? Same user who reported opened a PR which then he closed after installing<EMAIL_ADDRESS>like the contributions docs say.

Nope, indeed. closing.


Hey, i really wanna help with this cuz i get on everysingle cheat and i dont even understand what it is

the problem is coming from std
Filename = exempel chams.cpp
Problem:Filename is not a member of std
or something like that
and something else is sin and other stuff like that
so if someone could help me it would be awesome

Share source?

it has std you need to disinfect it

dude it actually has a std you need to disinfect it

i dont acctuly know what disinfect can you guys explain really sorry


Relax Ruby required version to support Ruby 3.0+

This PR removes Ruby version upper limit in gemspec to make the gem work with Ruby 3.0

One little thing to point out (or maybe new PR?) is to bump the Solidus version in the gemspec to not be <3 so this works on Solidus master (3.0.0.beta) as well.
https://github.com/solidusio/solidus_auth_devise/compare/master...peterberkenbosch:ruby-3-support

One little thing to point out (or maybe new PR?) is to bump the Solidus version in the gemspec to not be <3 so this works on Solidus master (3.0.0.beta) as well.
https://github.com/solidusio/solidus_auth_devise/compare/master...peterberkenbosch:ruby-3-support

add Solidus 3 support here #205

add Solidus 3 support here #205


Support BGP Route Deletion

RedistributeDel non-connected routes from RIB to ZAPI clients.
Delete routes from RIB when ZAPI RouteDelete message is received.

The lint error is very strange because WildcardQuery has a PathStruct() method. Let's see if this continues.


MCHBAR PL1 is not set correctly by Throttled under Debian Bullseye on Lenovo Thinkpad L14 Gen 2

I am using Debian Bullseye on a Lenovo Thinkpad L14 Gen 2. Throttled is not changing the MCHBAR PL1 settings. This can be confirmed via sysfs:
root@smithsonian:/home/fangfufu# cat /sys/devices/virtual/powercap/intel-rapl-mmio/intel-rapl-mmio:0/constraint_0_power_limit_uw
20000000

I have set it to 60W in /etc/throttled.conf.
I can increase the limit by running the following in the background:
watch -n 1 'echo 60000000 > /sys/devices/virtual/powercap/intel-rapl-mmio/intel-rapl-mmio:0/constraint_0_power_limit_uw'

It would be nice if throttled does this in the background for me.
I am running Debian Bullseye using the kernel from the backport:
fangfufu@smithsonian:~$ uname -a
Linux smithsonian 5.14.0-0.bpo.2-amd64 #1 SMP Debian 5.14.9-2~bpo11+1 (2021-10-10) x86_64 GNU/Linux

I can confirm that throttled is working correctly:
fangfufu@smithsonian:~$ sudo systemctl status throttled
[sudo] password for fangfufu:
● throttled.service - Stop Intel throttling
     Loaded: loaded (/etc/systemd/system/throttled.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-01-16 02:10:10 GMT; 33min ago
   Main PID: 115699 (python3)
      Tasks: 2 (limit: 76701)
     Memory: 11.7M
        CPU: 441ms
     CGroup: /system.slice/throttled.service
             └─115699 /opt/throttled/venv/bin/python3 /opt/throttled/throttled.py

Jan 16 02:10:10 smithsonian systemd[1]: Started Stop Intel throttling.
Jan 16 02:10:10 smithsonian python3[115699]: [I] Detected CPU architecture: Intel TigerLake
Jan 16 02:10:10 smithsonian python3[115699]: [I] Trying to unlock MSR allow_writes.
Jan 16 02:10:10 smithsonian python3[115699]: [I] Testing if undervolt is supported...
Jan 16 02:10:10 smithsonian python3[115699]: [I] Testing if HWP is supported...
Jan 16 02:10:10 smithsonian python3[115699]: [I] Loading config file.
Jan 16 02:10:10 smithsonian python3[115699]: [I] Starting main loop.

I set the power properly at /etc/throttled.conf
[GENERAL]
# Enable or disable the script execution
Enabled: True
# SYSFS path for checking if the system is running on AC power
Sysfs_Power_Path: /sys/class/power_supply/AC*/online
# Auto reload config on changes
Autoreload: True

## Settings to apply while connected to Battery power
[BATTERY]
# Update the registers every this many seconds
Update_Rate_s: 30
# Max package power for time window #1
PL1_Tdp_W: 60
# Time window #1 duration
PL1_Duration_s: 28
# Max package power for time window #2
PL2_Tdp_W: 60
# Time window #2 duration
PL2_Duration_S: 0.002
# Max allowed temperature before throttling
Trip_Temp_C: 85
# Set cTDP to normal=0, down=1 or up=2 (EXPERIMENTAL)
cTDP: 0
# Disable BDPROCHOT (EXPERIMENTAL)
Disable_BDPROCHOT: False

## Settings to apply while connected to AC power
[AC]
# Update the registers every this many seconds
Update_Rate_s: 5
# Max package power for time window #1
PL1_Tdp_W: 60
# Time window #1 duration
PL1_Duration_s: 28
# Max package power for time window #2
PL2_Tdp_W: 60
# Time window #2 duration
PL2_Duration_S: 0.002
# Max allowed temperature before throttling
Trip_Temp_C: 95
# Set HWP energy performance hints to 'performance' on high load (EXPERIMENTAL)
# Uncomment only if you really want to use it
# HWP_Mode: False
# Set cTDP to normal=0, down=1 or up=2 (EXPERIMENTAL)
cTDP: 2
# Disable BDPROCHOT (EXPERIMENTAL)
Disable_BDPROCHOT: False

Possibly already mentioned earlier somewhere else (maybe it's helpful here in this thread):
My workaround is to press the keyboard shortcut FN+h once after each restart.
Even though not (well?) documented for L14 Gen2, this activates the high performance CPU profile and prevents the CPU throttling under load - until the next restart, though.
I've been doing this for the past year as soon as I notice the unwanted CPU throttling kicks under load.
Still the CPU scales down when idle, as expected.
So far I haven't noticed any negative side effects.
With shortcuts FN+m, FN+l one can switch back to medium or low profile if needed.

@cor3000 , where did you find out about this information?

I am confirming that this is fixed via https://github.com/erpalma/throttled/pull/310

@cor3000 , where did you find out about this information? FN+m doesn't seem to do anything for me, but FN+h and FN+l both do.

I don't remember how I eventually put the clues together... however that's what I found in the Lenovo User Manual for L14 Gen2

Intelligent cooling
The Intelligent Cooling feature helps you adjust fan speed, computer temperature and performance. This feature works in auto mode by default. Press Fn+T to switch between manual mode and auto mode.

https://download.lenovo.com/pccbbs/pubs/l14_gen2_l15_gen2/html_en/index.html#t=en%2FIntelligent_cooling_(topic)_T0000783576.html&rhsearch=FN&rhhlterm=FN&rhsyns=
However this FN+t shortcut didn't have any (noticeable) effect on my side.
Then I came across the other shortcuts (FN+h/m/l) documented for other Thinkpad Models, and just "gave it a try"
Maybe from here: https://wiki.archlinux.org/title/Lenovo_ThinkPad_X1_Carbon_(Gen_10)#Performance_modes (even though the model doesn't match, the shortcuts seem to work, maybe not the FN+m (as you noticed), which I don't use anyway)
IIRC: I also saw this in one of the Thinkpad user Guides for an older Model, but as of today I can't find it anymore.
If I knew how to trigger these FN shortcuts from command line, that would give me a chance to automate these during startup.
Maybe that could even give a simpler fix for the underlying problem than polling/updating a configuration file in an endless loop.

also this gives the same hint: FN+H (something about a "Lap Detection System", amazing what kind of weird features companies have to come up with, due to 'regulation' protecting people from burning themselves, similar to ... "don't put a cat into a microwave")
https://www.reddit.com/r/thinkpad/comments/i4x8i8/tip_for_x1c7_and_perhaps_other_recent_models/


Update README.md for v2

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


Create Token without expiry (ExpiresIn=0) not possible (token is issued with default expiry)

Currently its not possible to create a token without expiry over the api. The reason is this code:
https://github.com/jfrog/jfrog-client-go/blob/74b10e4efa5cfc819f061cbf3bbba99d6f7cb6b6/artifactory/services/security.go#L139
=> If you specify "0" the expires_in is not send to the server and the default is used.

Thanks for reporting this @markuslackner.
Feel free to create a pull request to change this behaviour.


[Storage] following guideline for Logging

[non breaking]
Redact sensitive data from logging

[x] need to sanitize SAS in URL
[ ] need to sanitize auth info in headers
[ ] maybe some general way to turn on/off the above (low pri)

Track 2.

Already logging safe URL and response status in LoggingPolicy


std.process unit test sometimes fails

snarwin+bugzilla (@pbackus) reported this on 2021-10-02T21:09:54Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=22350
CC List

johan_forsberg_86

Description
Running the unit tests for std.process on FreeBSD sometimes fails, with the following message:

---
core.exception.AssertError@std/process.d(1645): Assertion failure
---

The assertion in question is here:

---
 // last resort, try lsof (not available on all Posix)
 TestScript lsof = "lsof -p$$";
 auto lsofRes = execute(lsof.path, null);
 if (lsofRes.status == 0)
 {
     assert(!lsofRes.output.canFind(path));
     // line 1645
     assert(execute(lsof.path, null, Config.inheritFDs).output.canFind(path));
     return;
 }
---

This failure was observed in the auto-tester results for Phobos PR #8259 [1]. Restarting the auto-tester caused the test to pass.

[1] https://github.com/dlang/phobos/pull/8259

snarwin+bugzilla commented on 2021-10-22T20:30:46Z
Spotted again here:

https://github.com/dlang/druntime/pull/3595
https://auto-tester.puremagic.com/show-run.ghtml?projectid=1&runid=5019269&isPull=true

This time the failure occured on Darwin_64_64, not FreeBSD.

snarwin+bugzilla commented on 2021-10-19T14:14:23Z
Spotted again here:

https://github.com/dlang/druntime/pull/3593
https://auto-tester.puremagic.com/show-run.ghtml?projectid=1&runid=5016811&isPull=true

johan_forsberg_86 commented on 2021-10-24T22:59:05Z
Maybe fixed by https://github.com/dlang/dmd/pull/13210

snarwin+bugzilla commented on 2021-10-03T22:38:15Z
This may have been fixed by Phobos PR #8261 [1].

[1] https://github.com/dlang/phobos/pull/8261


Extension development: improve experience for testing extension APIs

I am working on adding an API to my extension, so that other extensions can build on top of what mine offers.  As part of this, I need to test the API and develop samples.
My current workflow for this is:

Update the API
Build a VSIX of my extension (the "API provider")
Uninstall any existing version of my extension
Reload or/and restart (because sometimes if I install the updated VSIX I get the old version instead unless I rev package.json/version every time)
Install the API provider extension from VSIX
Reload the window where I'm working on my test/sample project
Run my test/sample project in the extension development host

As you can imagine, this gets a bit slow and fiddly, as the install/uninstall/reload/install cycle can be a bit slow!  It's also a bit painful for debugging as I can't debug the installed-from-VSIX API provider extension; I have to add console.log statements and then do the rebuild/uninstall/reload/install dance again.
Could you provide a way to load two extensions simultaneously into the Extension Development Host, so that I can run my API provider and API test/sample alongside each other?  Alternatively, could you make it so that if I debug my API provider in the Extension Development Host, and then from within the EDH debug my API tester (launching a second EDH), the API provider propagates to the second EDH?  Thanks!

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


MudDatagird has an issue with RowStyleFunc when using ServerData

Bug type
Component
Component name
MudDatagird
What happened?
when I use ServerData and I want to select a row with single select every thing is fine but when I go to another page and come back I lost the select background color!.
if you look at the video you could know that I don't lose the select only I lose the style!.
https://github.com/MudBlazor/MudBlazor/assets/96167344/b6b8cd29-dadf-43aa-b6db-8c5147ac1b65
Expected behavior
when I use ServerData and I want to select a row with single select every thing is fine but when I go to another page and come back I lose the selected row background color!.
if you look at the video you could know that I don't lose the selected. row data I only lose the style!.
https://github.com/MudBlazor/MudBlazor/assets/96167344/0122e78c-0fed-4566-a382-eea56bf96e62
some of the codes :
private Func<TEntity, string> _cellStyleFunc => x =>
    {
        if (IsEntityPickup)
        {
            if (x == SelectedItem)
            {
                return "color: white !important;";
            }
        }

        return "";
    };
    private Func<TEntity, int, string> _rowStyleFunc => (x, i) =>
    {
        if (IsEntityPickup)
        {
            if (x == SelectedItem)
            {
                return "background-color: #1E88E5 !important;";
            }
        }

        return "";
    };

<MudDataGrid T="TEntity" @ref="_table" MultiSelection="@(!IsEntityPickup)" ServerData="@ServerReload"
             ShowMenuIcon="false" FixedHeader="true" Hideable="true" SortMode="SortMode.Single"
             ShowColumnOptions="false" ColumnsPanelReordering="true"
             @bind-SelectedItems="_selectedItems" Dense="true" Loading="@(IsLoading || _OrderedColumns is null)"
<EMAIL_ADDRESS>Height="@(IsEntityPickup ? "355px" :"460px")" Hover="true"
             Filterable="@(!IsEntityPickup)" FilterMode="DataGridFilterMode.ColumnFilterMenu"
             FilterDefinitions="@(new List<IFilterDefinition<TEntity>>() { })"
             SelectOnRowClick="true" RowsPerPage="@(IsEntityPickup ? 5 :7)" Outlined="@IsEntityPickup"
             RowClass="@(IsEntityPickup ? "cursor-pointer" : "")"
             SelectedItemChanged="@SelectedItemChange" RowStyleFunc="@_rowStyleFunc">

Reproduction link
try.mudblazor.com
Reproduction steps

...
Relevant log output
No response
Version (bug)
7.0.0
Version (working)
No response
What browsers are you seeing the problem on?
Safari
On which operating systems are you experiencing the issue?
macOS
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

@henon do you think this just happened in v7.x.x ? or same for all versions? and just to be more clear I used custom pagination however it is MudPaginator with some custom styling.
<PagerContent>         <CustomDataGridPaginator TEntity="TEntity" _table="@_table"/>     </PagerContent>

or same for all versions?

That would be nice if you could find this out. My guess it's the same for all version, there were no commits in v7 that could influence that.

there were no commits in v7 that could influence that.

So it doesn't need to check I guess.
is this could be fix in my code or I have to wait for another updated version of mudblazor?

I have to wait for another updated version of mudblazor?

Probably wait until someone fixes it. You could try a workaround to reset the selection and then restore it when switching pages, if there is such an event in the pager, which I'm not sure about.

I have to wait for another updated version of mudblazor?

Probably wait until someone fixes it. You could try a workaround to reset the selection and then restore it when switching pages, if there is such an event in the pager, which I'm not sure about.

shall I look at it and if I found the solution then make a PR?

shall I look at it and if I found the solution then make a PR?

sure

I found that the problem is not the pager because it works fine if I use Items instead of ServerData !.
so the problem is ServerData when you change the page it would invoke the ServerData method and I couldn't  find why it wouldn't render the style again because I looked at the MudDatagrid code it should render it again. But idk why wouldn't .

A reproduction in try.mudblazor.com (without all your app's complexity) would help here

Here you are

@sardar97 Here is your fix: https://try.mudblazor.com/snippet/wYceYhaHTJxABgNp

@sardar97 Here is your fix: https://try.mudblazor.com/snippet/wYceYhaHTJxABgNp

thank u very much. Could you check the Single Selection as well because it still same!
https://github.com/MudBlazor/MudBlazor/assets/96167344/31c3acd2-7835-4e32-8bd4-f9bedfd5d102

Here you go: https://try.mudblazor.com/snippet/GYcokhadJpiqwAlq

Here you go: https://try.mudblazor.com/snippet/GYcokhadJpiqwAlq

awesome henon, much appreciate . ❤

Here you go: https://try.mudblazor.com/snippet/GYcokhadJpiqwAlq

That actually makes sense. I don't know how it didn't come to mind. Since there is no cache mechanism, clicking the first page again treats it as if there were new items.


[WIP] feat(shared): Expose stable mutate + replace unstable__mutate

Description

Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated
Will do

Type of change

[ ] 🐛 Bug fix
[x] 🌟 New feature
[ ] 🔨 Breaking change
[x] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[x] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

!snapshot

!snapshot

!snapshot

Hey @panteliselef - the snapshot version command generated the following package versions:

Package
Version

@clerk/backend
0.29.1-snapshot.3ef2f60

@clerk/chrome-extension
0.4.0-snapshot.3ef2f60

@clerk/clerk-js
4.58.0-snapshot.3ef2f60

@clerk/clerk-expo
0.19.2-snapshot.3ef2f60

@clerk/fastify
0.6.7-snapshot.3ef2f60

gatsby-plugin-clerk
4.4.8-snapshot.3ef2f60

@clerk/localizations
1.26.0-snapshot.3ef2f60

@clerk/nextjs
4.24.0-snapshot.3ef2f60

@clerk/clerk-react
4.25.0-snapshot.3ef2f60

@clerk/remix
2.10.3-snapshot.3ef2f60

@clerk/clerk-sdk-node
4.12.6-snapshot.3ef2f60

@clerk/shared
0.22.1-snapshot.3ef2f60

@clerk/types
3.52.0-snapshot.3ef2f60

Tip: use the snippet copy button below to quickly install the required packages.
# @clerk/backend
npm i<EMAIL_ADDRESS>
# @clerk/chrome-extension
npm i<EMAIL_ADDRESS>
# @clerk/clerk-js
npm i<EMAIL_ADDRESS>
# @clerk/clerk-expo
npm i<EMAIL_ADDRESS>
# @clerk/fastify
npm i<EMAIL_ADDRESS>
# gatsby-plugin-clerk
npm i<EMAIL_ADDRESS>
# @clerk/localizations
npm i<EMAIL_ADDRESS>
# @clerk/nextjs
npm i<EMAIL_ADDRESS>
# @clerk/clerk-react
npm i<EMAIL_ADDRESS>
# @clerk/remix
npm i<EMAIL_ADDRESS>
# @clerk/clerk-sdk-node
npm i<EMAIL_ADDRESS>
# @clerk/shared
npm i<EMAIL_ADDRESS>
# @clerk/types
npm i<EMAIL_ADDRESS>

@panteliselef can you please elaborate on this? So far we have been using SWR internally for our own convenience. Did customers ask for this? In Clerk the preferred way to do mutations is via the Clerk models that hold all the mutating methods.

@panteliselef can you please elaborate on this? So far we have been using SWR internally for our own convenience. Did customers ask for this? In Clerk the preferred way to do mutations is via the Clerk models that hold all the mutating methods.

Yes, there were customer requests, I'll share more internally.
I see SWR mutate as a way to force a revalidation or manually populate the cache for the collection of data.
This does not change the way someone will call the mutation methods that update a resource. On the contrary those 2 mechanism will work together, let me give an example:

I see. Let's take it offline. We should be able to support this use case using the Clerk hooks API surface.

@panteliselef We have changed the process of the v4 hotfixing. Please rebase this PR with main as the base branch and after it's closed, use the backport script to open a hotfix from main-v4.
Also if something that it's not related a fixing an issue in v4 and it can wait until v5, merge it in main and don't backport it.


Fix clippy warn

This patch indeed seems to fix the clippy issues; but @stjepang and I have been talking over the past week, and a lot of the clippy lints are starting to feel a bit tedious. In addition to that things seem to be breaking fairly regularly on the clippy side, which made us question if we should even keep it.
@k-nasa how do you feel about clippy?

umm.  This problem is difficult.
Certainly working with code conventions is tedious.
The problems I have fixed now are most that don't have to be fixed.
However, clippy sometimes displays important warnings.
For example this: https://rust-lang.github.io/rust-clippy/master/index.html#redundant_clone
So I think it is difficult to ignore it completely.
In addition, it is cumbersome to choose which items to fix and which to ignore.
I don't have conclution for this problem.
but, I think someone needs to face clippy and make the appropriate corrections.
I'm interested in what you and @stjepang  think.


Update README.md

Added bare-metal ubuntu getting started guide.
@jainvipin may I list you as a community supporter for bare-metal ubuntu?
described the Config Management for one of the  for the non-saltstack non-ansible version of vagrant+Fedora.
@eparis is there a better name for this thing?

@erictune - should be okay

Eric, can you rebase so I can merge cleanly?

have we made a decision to start doing that?  It seems like a lot of busywork just to make the commit logs pretty.

Here again this branch was created in the upstream project so anyone doing git fetch from it will end up receiving this branch... It should have been created on your personal project instead. (Don't worry, you're not the first one to do this, it's fairly common, apparently the GitHub mobile app makes it really easy to make this mistake.) Please avoid creating new work branches on the upstream project in the future.


ENH: Use macos-13 now to avoid disruption when macos-12 is retired

The macOS 12 runner image will be removed by December 3rd, 2024. To raise awareness of the upcoming removal, jobs using macOS 12 will temporarily fail during scheduled time periods defined below:
November 4, 9:00 AM - 7:00 PM EST
November 11, 9:00 AM - 7:00 PM EST
November 18, 9:00 AM - 7:00 PM EST
November 25, 9:00 AM - 7:00 PM EST
What you need to do
Jobs using the macos-12 YAML workflow label should be updated to macos-15, macos-14, macos-13, or macos-latest. You can always get up-to-date information on our tools by reading about the software in the runner images repository. Please contact GitHub Support if you run into any problems or need help.

I already tested this here: https://github.com/InsightSoftwareConsortium/ITKIOOMEZarrNGFF/pull/75


Update managedserviceidentity type enum

Enum is currently missing the ua + sa combination + "none" type. We do support those values in our API and as such need the swagger to reflect that.
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/5668
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/5668/commits/089877dd4db9d93259d8733d745e742ecf157ee6

Automation for azure-sdk-for-java


Windows - Cannot open developer tools

Testing #107466
Developer tools is not working in the vscode build with vscode-file protocol. Running the command Developer: Toggle Developer Tools is not showing anything.

It seems the zip I downloaded and extracted is in wrong location (in Mac). It works now when I moved this to windows drive.


UI: updating imported cluster omits localCluserAuthEndpoint, causing it to be nil

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

create imported cluster
edit cluster by adding a description

Result:
Cluster request is sent with a cluster state that is missing the outter localClusterAuthEndpoint.
Expected:
Cluster request should contain a localClusterAuthEndpoint.

@deniseschannon we're planning to not "fix" this one.
After investigating this issue I found the following:

localClusterAuthEndpoint is being purposefully deleted when the cluster is not RKE. This seems to be due to the fact that this feature is supposed to be an RKE only feature. (https://github.com/rancher/rancher/issues/16486)
Currently there isn't a good way to detect if an imported cluster is RKE or not.
Even though it looks like we could actually prevent the deletion without any adverse effects, we're not 100% certain. We'd like to avoid the possibility of introducing a new regression.
Lastly https://github.com/rancher/rancher/issues/23783 is being resolved in such a way that the side effects of our deletion won't cause a problem.

Please resolve this if you're comfortable with the above.

Since the panic is resolved in the backend and it seems the frontend is working as expected. We'll close this.


Permit local configuration of Django LOGGING

It would be useful to permit local configuration of the Django LOGGING setting. Currently if custom LOGGING is desired, it must be configured in settings.py, but this is part of the distribution. Simple change, as the facility to import local settings is already there.
diff --git a/netbox/netbox/settings.py b/netbox/netbox/settings.py
index ae81d26..c1daf42 100644
--- a/netbox/netbox/settings.py
+++ b/netbox/netbox/settings.py
@@ -15,7 +15,7 @@ except ImportError:
 VERSION = '1.9.3'

 # Import local configuration
-for setting in ['ALLOWED_HOSTS', 'DATABASE', 'SECRET_KEY']:
+for setting in ['ALLOWED_HOSTS', 'DATABASE', 'SECRET_KEY', 'LOGGING']:
     try:
         globals()[setting] = getattr(configuration, setting)
     except AttributeError:

FYI the code above would make LOGGING a mandatory setting, which is not what we want.


some minor fix on mapquest and add environment variable to retrieve key

I modified get_tweet_json.py:

to allow geocoding as false
to ensure the url sent to mapquest api is encoded.
use list for location dictionary for tweets with duplicate locations
Also modified tweet_credentials in which the hard-coded api key/secret is replaced by os environment variable.
Thanks for your time to review this.

Gosh! I'm sorry I didn't get back to you. Pull requests are a new thing for me and I just noticed.
The screen says
This branch has conflicts that must be resolved
Use the command line to resolve conflicts before continuing.
I'd love to review what you did but I'm afraid I can't. Do you think you could try again?
George


Send notification to staff-users if a certificate which is in-use is expiring

Discussed with @sjoerdie
Currently we have external (Uptimerobot) monitoring of our web-facing certificates. However for our DigiD/eHerkenning certificates we don't have additional monitoring in place.
It would be useful to automatically send a notification to staff-users if a certificate which is in-use is expiring within 30 days. This would be a weekly check (so you get bothered at most 4x).
This could be a management command or via some other mechanism, as long as it is easily automated.

How would you detect that a certificate is "in use"?

How about we skip the 'in use' checking and simply notify if there is a certificate that is expiring? It is then up to the admin to determine if the certificate is in use and needs to be replaced, or if the certificate is no longer in use and can be removed


Station Shadowlands [WIP]

About the PR

A little experiment. A system that generates an alternative, shadowy underside of the station, full of dangers and loot
Why / Balance

At the moment I have no idea how to use it, but it looks nice and interesting. I'm doing this PR to discuss the possibilities of using this mechanic.
Here are a few of the ideas considered:

The shadow anomaly is a portal to the shadow dimension, and given that anomalies can unstably explode or be removed by scientists, this is a temporary portal. We need to add the ability to return to the normal dimension on its own if the portal has closed. Perhaps in the shadow dimension there are portals in ray places that teleport to the same point on the map in the real dimension.
The shadow anomaly core along with some T2 or T3 technology allows you to create stable portals to the shadow dimension. You get an interesting synergy between RnD and Salvage, where the scientists provide unique gameplay for finding resources.
Something more global? A separate game mode where shadowlings live on the shadow side, and having the ability to penetrate the real world through the shadow dimension, must take over the station and plunge it into darkness?

Technical details

Currently, the shadow dimension is generated by an asynchronous function, scanning the largest station grid, recreating its shape, and populating it with entities based on the tagged objects in the main station. Thus, for example, all walls in the real station are replaced by chasm in the shadow dimension. And all consoles and machines are replaced with valuable loot.
I'm not sure if it's a good idea to generate another big grid with a bunch of entities at the beginning of the map in parallel with the main station, I'd consult sloth here.
Media
https://github.com/user-attachments/assets/f69ba4d9-46a7-47c8-985e-c3153e1559e4
Requirements

[x] I have read and am following the Pull Request and Changelog Guidelines.
[x] I have added media to this PR or it does not require an ingame showcase.

Changelog

nothing right now

Should totally be a research that allows entry, this could make for a fun thing antags could travel through to get into places as well as a place for salvage to loot (though, it might need a bit more loot)

Z-levels are real!

No way
Bleach TYBW reference

chasms in an area that dark seems a bit cruel

https://github.com/user-attachments/assets/4bd2be99-4b40-402a-a2bd-f378abcbcde2

Ed coming in with another banger. Hopefully people will call Salvage to come in these and loot them for people. I pray for any salv buff. We are DYING.

Should totally be a research that allows entry, this could make for a fun thing antags could travel through to get into places as well as a place for salvage to loot (though, it might need a bit more loot)

I mean SS13 has Telescience this could be reworked into that instead. It's already extremely close to it as it is now anyway.

What happens if a portion of the station is detached while you are in that portion's shadow realm

i reopen a new PR for it

What happens if a portion of the station is detached while you are in that portion's shadow realm

nothing. Shadow Dimension makes a copy of the station from the beginning of the round


SplitButton does not respect GroupStyle

SplitButton extents ItemsCollection, which allows me to specify a GroupStyle (useful in configurations where I want to supply a set of standard static colors and a set of theme colors).
The "PART_ListBox" needs to bind the "GroupStyle" collection in SplitButton to the ListBox.GroupStyle collection.  The short term work around was to subclass the SplitButton and override the OnApplyTemplate() call.
public override void OnApplyTemplate()
{
    base.OnApplyTemplate();

    // Can't use the EnforceType<ListBox> method in the base class because it's private.
    ListBox listBox = GetTemplateChild("PART_ListBox") as ListBox;

    if(listBox == null) { return; }

    foreach(GroupStyle style in GroupStyle)
    {
        listBox.GroupStyle.Add(style);
    }
}

Addendum, I also had to bind the ItemsPanel property:
BindingOperations.SetBinding(listBox, ItemsPanelProperty, new Binding
{
    Source = this,
    Path = new PropertyPath(ItemsPanelProperty)
});

'GroupStyle' property is read-only and cannot be set from markup.

I'll add the template binding for the ItemsPanel.


axby doesn't work with mis-matched array types

The axpy wrapper converts X and Y to the requested data type but does not check on the out array. If the out array is a different type this is not handled. I would suggest we use the out array dtype and over-ride, or not allow the user flag.
The relevant code is here

Maybe we should think whether to adhere to a BLAS implementation, like from MKL or OpenBLAS.
See https://github.com/UCL/STIR/issues/560#issuecomment-640230352


Add vektorcloud image collection

Thanks @bcicen for the dockerfiles. Could you please move this to the below section ## Dockerfile? Thanks!

Hi @bcicen I'm closing this PR as I added this for you under the ## Dockerfiles menu. Thanks for the submission.

Thanks @vegasbrianc!


[Jira] Find tickets without using ticket number prefixes

Extension
https://www.raycast.com/raycast/jira
Description
Right now it's not possible to find Jira tickets by searching for the number. You need to type the full ticket number (with the project prefix) in order to find a story.
So PROJ-12345 works, but 12345 doesn't.
It would be nice if the prefix can be omitted.
Who will benefit from this feature?
All Jira users that share ticket numbers without the prefix.
Anything else?
No response

Thanks for the feature request. Would you like to work on it? I can provide some guidance on how to contribute to this extension so that you can open a pull request. You can contact me here or in the Slack community if you need further help.
Note that opening up a PR and having it merged will earn you some credits as we want to reward contributions. You’ll then be able to exchange them in a swag store that we’ll launch soon!

Actually, it appears that this is a duplicate of issue #7951, so I'll mark it as such.


improve performance and reduce LOC

Using np.add to add two lists

Hello Maintainers, would you kindly consider reviewing this pull request?


build: enforce sudo mode in order to prevent Operation not permitted spams

To increase the overall UX, maybe enforcing and checking sudo mode in the first phase would better. Otherwise we ended up something like the following:
Nov 21 11:14:09.404 [INFO] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] running: /sbin/apk fix --root /tmp/apko-2078361064 --no-scripts --no-cache --update-cache --arch x86_64
Nov 21 11:14:09.410 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] fetch https://packages.wolfi.dev/os/x86_64/APKINDEX.tar.gz
Nov 21 11:14:09.953 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] (1/28) Installing glibc-locale-posix (2.36-r3)
Nov 21 11:14:10.834 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/lib/locale/C.utf8/.apk.49891d2f0983cb7df73dbc8f0f0db66204db0940ce003247: Operation not permitted
Nov 21 11:14:10.834 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/lib/locale/C.utf8/.apk.d07454acb13bebc6b8cea5cc205646a896e646f727295067: Operation not permitted
Nov 21 11:14:10.835 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/lib/locale/C.utf8/.apk.f7b8d3872190d1f89bf8d1872ccb8c7c448b1aba71c171d9: Operation not permitted
Nov 21 11:14:10.836 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/lib/locale/C.utf8/.apk.f1fd10d7f95d01661d11fdcccca4c470f94d4e1a3314577e: Operation not permitted
Nov 21 11:14:10.836 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/lib/locale/C.utf8/.apk.5f57c16f47a7ecb58ea0762dccc0c849a8f2fb80c787d195: Operation not permitted
Nov 21 11:14:10.837 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/lib/locale/C.utf8/LC_MESSAGES/.apk.c19ad216c563b1653020076ef6b3694f100652dac783a4ad: Operation not permitted
Nov 21 11:14:10.837 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/lib/locale/C.utf8/.apk.b5c0e8e6a911c41703bc3161b848ec32a2a87f414882d099: Operation not permitted
Nov 21 11:14:10.837 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/lib/locale/C.utf8/.apk.94813668423964e4d5b457d12bd064f9b0bc00bfa32f37df: Operation not permitted
Nov 21 11:14:10.837 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/lib/locale/C.utf8/.apk.9a18e6489d845f3e73dc659f6188a3978c263c926bd802be: Operation not permitted
Nov 21 11:14:10.837 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/lib/locale/C.utf8/.apk.024cb2d30ee7e8935bce0c4dc9e23d9a7a33f05abea5c5d8: Operation not permitted
Nov 21 11:14:10.837 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/lib/locale/C.utf8/.apk.cc753dc5baddc3d33fec3872781043dce8482f10ad57df56: Operation not permitted
Nov 21 11:14:10.837 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/lib/locale/C.utf8/.apk.a63602a47a328489271ea9c52e42c018dd207ebfc4fa1f7e: Operation not permitted
Nov 21 11:14:10.839 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] (2/28) Installing wolfi-baselayout (20221104-r0)
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.8a2baa2e28396c9087c2b3ee6a1d0778a0a4173cc5842992: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.0959c3e0af2d1a502f64a6d55ed42b4adb17610db927b39e: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.ec14d6d41cc8cc324e641927ce94e8d1d7d6551804868bd9: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.31558c7218ceeee73f66d7835dd30ca9d27a1d2355f49b49: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.04f961702857605827301f98034fd8c8067461867c263ea7: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.689df64adcbf481096ee8eb0c9939506aa6116fc5dbff02d: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.2d99ed5e72ea9348f4e1f7f36c8b93bc8faa63eb0868a291: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.13549a865d426bbf83442ae8e20392f76847e69a1d073287: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/profile.d/.apk.f8f73dcb21a074cc87d08407e40f4cdd1ccc85078a2e9980: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.2f1d585fd01e79fbe5c2e6daae73d9ca386c3b573c1d1f47: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/secfixes.d/.apk.f3e56394b6bd395f1541db48dc58d141a97f2f82e4d463b8: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.59dc48c578fa5c56185d3e03f4dacbd8c20f4fbc263a95a0: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.3625be60bca236d3e4835c19cd1e5a6e6942b15a0502cbb6: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.5fb8ff9b2731ae1fc8e58480287da6bc9696b0390de208dd: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on .apk.8c5316ac82a84b939a2a3a8be5cdc401508899a847da55b2: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/.apk.54291f3457b235ebd63ebdbc485ebfdab80768bb04c03d7a: Operation not permitted
Nov 21 11:14:11.616 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/local/.apk.d9ef385ba3b4dd95a5a1d04342db1f7d38c0aeb69081fd02: Operation not permitted
Nov 21 11:14:11.618 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on var/spool/cron/.apk.d381425141bb1314a24fea0a48e44884283d5ecdb6c79248: Operation not permitted
Nov 21 11:14:11.618 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on var/spool/.apk.14733b10e279aff9b895d3700110628766ee9d80cb3ba788: Operation not permitted
Nov 21 11:14:11.619 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] (3/28) Installing glibc (2.36-r3)
Nov 21 11:14:12.592 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.6f1fd5a76d7a81912d000f834ad70b2761e67de0327fc43e: Operation not permitted
Nov 21 11:14:12.593 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on etc/.apk.ca409f3ed95d0245d226f793046b0e8b9fb9e687a20f67ab: Operation not permitted
Nov 21 11:14:12.594 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.99a0ed552bf2dda933724ad748bf32766ab99f280f83461a: Operation not permitted
Nov 21 11:14:12.647 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.7011ca73627946d0bc5674788872e9e208bf56d810a41597: Operation not permitted
Nov 21 11:14:12.648 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.cff9356eb015197ed98072b1da56583d2526ae02313be804: Operation not permitted
Nov 21 11:14:12.785 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.83b895bfc094998119256d76ab1094c47aa97c05f2e99421: Operation not permitted
Nov 21 11:14:12.785 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.183d84932c8ca825d81e97c95b551151477ea75315fe515d: Operation not permitted
Nov 21 11:14:12.786 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.8c89845544ccc5f50d2cacf472b1bacc20260e8bbb62b519: Operation not permitted
Nov 21 11:14:12.786 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.902eb80d48c925c836ee8ab455412a7badd7378a532fe68e: Operation not permitted
Nov 21 11:14:12.982 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.6de101e8ae34602656432b7668a1a5089e5495c9f77bb1c1: Operation not permitted
Nov 21 11:14:12.982 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.d07c26613e3be0432e6e6bf30801942e4183eda834582825: Operation not permitted
Nov 21 11:14:12.991 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.fef9f9afb360e34b405d34fdfe8da249ca1ba72a4ea51b01: Operation not permitted
Nov 21 11:14:12.992 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.001d2a733de3cb4e22f692213c10b30f8ea0833361d5fa99: Operation not permitted
Nov 21 11:14:13.066 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.9c6ce75cb4e406754396892eeed8429f651d1c12a6cf1176: Operation not permitted
Nov 21 11:14:13.066 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.f873037417407e8016ab4498835679490ce049a50357dea3: Operation not permitted
Nov 21 11:14:13.066 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.fd867656f95c2370f9105a83a94fd15ea0742587eb48ab38: Operation not permitted
Nov 21 11:14:13.066 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.8e096d1943e86a038ec560a9935840ff3d8cc65157d7da86: Operation not permitted
Nov 21 11:14:13.067 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.b11cecb53d64a8943d67a8700d4824bc78e34f5d338dbcb0: Operation not permitted
Nov 21 11:14:13.068 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.e80d380aee20021561226670142658932542e66e83330f4f: Operation not permitted
Nov 21 11:14:13.069 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.35acfcbecf57b94b3add30ab1ee37e558af21e798b8c3725: Operation not permitted
Nov 21 11:14:13.069 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on lib64/.apk.a76e4a22890991a6429f5150f4de461d9317e2974838350d: Operation not permitted
Nov 21 11:14:13.250 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on sbin/.apk.0fb617949268a3cd97e912320cdfaaa36e305651e4b07c52: Operation not permitted
Nov 21 11:14:13.250 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/bin/.apk.03b7730999fba73ce71323d1cb7b7a24395d5e97daec0d58: Operation not permitted
Nov 21 11:14:13.253 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] (4/28) Installing binutils (2.39-r3)
Nov 21 11:14:14.413 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/bin/.apk.a285a4de33ad7fe5ccfc0ed9c3bf7e4e872dcfa2d08df170: Operation not permitted
Nov 21 11:14:14.623 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/bin/.apk.da08b2e558f46a503114bd1dd80920e2b4d29cf437493fad: Operation not permitted
Nov 21 11:14:14.683 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/bin/.apk.09d09f063efae006b1b5cb569f8130cf7621ebb8e569b2ee: Operation not permitted
Nov 21 11:14:14.764 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/bin/.apk.7db5fa91e9dbd189720acb7baae5385d6bf5770236bc9051: Operation not permitted
Nov 21 11:14:14.779 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/bin/.apk.1e623a84198bda1c7473aa0d068089851b7fa060faa0fd08: Operation not permitted
Nov 21 11:14:14.923 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/bin/.apk.97f06c55bdf7aa50476291aafc37a0fd650b3b209c0c62f3: Operation not permitted
Nov 21 11:14:14.952 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/bin/.apk.c86adac419ecc7ac1bd13a960cb6329a1503e4c674f28fbc: Operation not permitted
Nov 21 11:14:14.958 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:false] [use-qemu:] ERROR: Failed to set ownership on usr/bin/.apk.616ee3c7854012d188f084692bdd18b515f4e81211438be6: Operation not permitted

cc @developer-guy

use-proot can help with some of this but I still ran into this after:
Dec  2 10:24:36.846 [DEBUG] [arch:x86_64] [cmd:apk] [use-proot:true] [use-qemu:] OK: 10 MiB in 25 packages
Error: failed to build layer image: failed to mutate accounts: chown(3, 4) = chown /tmp/apko-411772834/var/adm: operation not permitted
2022/12/02 10:24:36 error during command execution: failed to build layer image: failed to mutate accounts: chown(3, 4) = chown /tmp/apko-411772834/var/adm: operation not permitted


Fix concurrent sync dedup

What changes are proposed in this pull request?
The concurrent sync feature will throw exception if the locking scheme uses the constructor that takes a shouldSync boolean. This PR fixes it.
Does this PR introduce any user facing changes?
N/A

alluxio-bot, merge this please


add home and backgrounds

Well, you've added two more directories. How do they integrate with the current app? Also, please add a screenshot of what your version looks like.


manifest: warn if path of rerun-if-changed=PATH does not point to existing file

Fixes #6003

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks for the PR! I think this warning may be emitted at the wrong time though? This warning, if we want to emit it, seems like it should be printed just after the build script prints it. For example the current warning is printed in situations where no warning should be printed out at all, such as the build script depending on a file that was then deleted, requiring the build script to rerun.
Note though that this can also be used in situations that do not want a warning, such as always wanting a build script to run (by depending on a file that doesn't actually exist). I don't know how often that happens in practice though.

I'm going to close this as it's been quiet for quite some time now, but this can always be resubmitted!


push arm master image build

The last thing I believe is missing is to actually push the ARM master build.

What this PR does / why we need it:
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 #
Special notes for your reviewer (optional):

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
966

Relevant Lines:
1351

💛  - Coveralls


Cyrillic text looks bad

Probably font (used in sidebar) needs to be changed

@ivabus what font would you recommend? we can probably do a conditional font depending on which language is selected.

@getneil i would recommend “Ubuntu” font. It looks stylish (a bit but enough) and easy readable


Get a Rust-style "result.unwrap()" kind of method working

Currently, you can only use result.getOr(defaultVal) because that's the only safe version that won't crash your code.
It should be possible or the compiler to detect and allow something like:
if result.isOk() {
  return result.get().doThing()
} else {
  return result.getErr()
}

Where a default value doesn't have to be provided since it's known that branch cannot fail.

This is now tracked in #414


chore: add prettier

use npm run prettier before commit

By far the biggest reason for adopting Prettier is to stop all the on-going debates over styles.

https://prettier.io/docs/en/why-prettier.html

Single quote or double quote?

I'm fine either. as long as be consistent. 😄

Well. I always use single quote. Changing that will slow down my coding speed with 90%

Coverage decreased (-0.2%) to 89.587% when pulling f34d6307a117d45346768c8cc61493dc992ee989 on Aladdin-ADD:prettier into 7f09e3feff98a1bced12fc6b13931427492159b9 on cherow:master.

Coverage decreased (-0.2%) to 89.587% when pulling f34d6307a117d45346768c8cc61493dc992ee989 on Aladdin-ADD:prettier into 7f09e3feff98a1bced12fc6b13931427492159b9 on cherow:master.

prettier ignore can be helpful in a few cases.
another way can be considered is switch to eslint + eslint-typescript-parser. (I will try it later)

another way can be considered is switching to eslint + eslint-typescript-parser. (I will try it later)

I really like the idea of dogfooding cherow like that. We could certainly make automatic formatting work for cherow by adding some custom logic which I'm sure others will appreciate as well.
The basic idea is that simply applying the same spacing everywhere doesn't hold. Sometimes you want chains of parenthesized expressions and/or binary comparisons to be aligned by operator instead. We do that quite a lot. A linter that can natively support that would be ideal.


Region Sampler bug fixed

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.86%. Comparing base (c8bf83a) to head (c1fd218).
Report is 1 commits behind head on dev.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev      #22   +/-   ##
=======================================
  Coverage   97.86%   97.86%
=======================================
  Files           8        8
  Lines        1218     1218
=======================================
  Hits         1192     1192
  Misses         26       26

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


Extend sol plot recipe to plot velocities

https://github.com/ONSAS/StructuralDynamicsODESolvers.jl/blob/master/src/interface.jl#L221

@JuliaRegistrator register()

Error while trying to register: Register Failed
@mforets, it looks like you are not a publicly listed member/owner in the parent organization (ONSAS).
If you are a member/owner, you will need to change your membership to public. See GitHub Help

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/45436
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.2.4 -m "<description of version>" 434e16c915f19c4df864cce0e1b3127f84cda3d1
git push origin v0.2.4


feat/resource-reconcilers

Adds custom reconcilers for PodMonitor, ExternalSecret, GrafanaDashboard and ConfigMap resources to stop using operator-utils and have more control. Especially important is the reduction in the amount of logs that were generated by the periodic reconcile loops of ExternalSecret resources.
/kind feature
/priority important-longterm
/assign

/lgtm

/lgtm

/approve


Event type depends on time_interval_s

When applying hooks to read or modify events on the fly, the type passed to the function depends on time_interval_s. For any value other than zero, an event is a dict, whereas for  time_interval_s=0 the entire list of events is passed to the function.
The code below
from pycromanager import Acquisition, multi_d_acquisition_events

def hook_fn(event):
    print(event)
    return event

with Acquisition(directory='./', post_hardware_hook_fn=hook_fn) as acq:
    events = multi_d_acquisition_events(
        num_time_points=5,
        time_interval_s=1,
        )
    acq.acquire(events)

produces
{'axes': {'time': 0}, 'min_start_time': 0}
{'axes': {'time': 1}, 'min_start_time': 1}
{'axes': {'time': 2}, 'min_start_time': 2}
{'axes': {'time': 3}, 'min_start_time': 3}
{'axes': {'time': 4}, 'min_start_time': 4}

which is what I would expect. However, changing to time_interval_s=0 results in
[{'axes': {'time': 0}}, {'axes': {'time': 1}}, {'axes': {'time': 2}}, {'axes': {'time': 3}}, {'axes': {'time': 4}}]

This leads to unexpected errors.
EDIT: I noticed now that it also happens for anything lower than time_interval_s=0.001.

Ok sorry for not reading the docs carefully enough... This is because of sequencing, which is used for short time delays.


Crash - FlurryContentLoadingManager.m line 1006

SDK v8.3.1
Fatal Exception: NSGenericException
*** Collection <__NSDictionaryM: 0x174656e90> was mutated while being enumerated.

Download Crash Report

Crashing 3% of our user base. @rollinsio @abhandary Please can we get help on this
Download Crash Log

OMG Just updated to 8.3.1 and prepared for release, wondering should I click the Release button
hmm

@AndrewBarba - we have logged the crash, will have an update on the resolution next week  (am stepping in for  @rollinsio @abhandary)

it looks like we have a workaround this crash (as confirmed to @AndrewBarba ).  Please reach out to<EMAIL_ADDRESS>if you are seeing this crash for further instructions how to remedy the problem

It has to do with the sdk trying to cache image assets on device. If your app supports setting images via https:// urls then you can have Flurry Support turn off caching for your adspace and the crashes will go away without releasing a new version of the app

BUT. This still needs to be fixed in sdk. So I'm not closing the issue

What I would really appreciate is a config option in the sdk to turn off the caching myself

Does an update for this crash will be available soon as it was expected 2 weeks ago ?


CM-627: Fix expired advisory bug

Jira Ticket:
CM-627
Jira Ticket URL:
https://bcparksdigital.atlassian.net/browse/CM-627
Description:

Fix public-advisory-audit switches from "Published" to "Draft" when it's expired
Remove the corresponding public-advisory when it's expired

Closed because it's duplicated PR of https://github.com/bcgov/bcparks.ca/pull/667


Full, uncropped thumbnails

Currently, the generated thumbnails are square, and unfortunately this also cuts-off a lot of images. You can see this in the repo's own image example, where e.g. the text "Internet!" on the bottom left picture is cut off, because the image is "too tall".

I've tried fiddling with the css but then realized the generated thumbnails were just square. This is a bit inconvenient when browsing photos I've taken on my phone, since a lot of those tend to be in portrait. If I'm browsing e.g. mirror selfies, the crop will cut off at my face/show mainly my chest, which is less than ideal.
I'd like an option to generate the thumbnails without cropping, ones which show whole image, even if it doesn't neatly fit into the square, like e.g. Windows Explorer does:

Thumbnails are generated using third-party libs, but I do not know how copyparty uses them. If I'm supposed to add a config file for them instead or something I'm happy to do that, though I would appreciate some directions.
If it's up to copyparty to do this though, then I think it should provide a config flag that toggles what type of thumbnail to generate (crop to center vs fit). pyvips, for example, has a crop parameter which you can adjust. I personally think it's generally ok if e.g. it only works on pyvips, but perhaps ffmpeg/pillow also have such settings.
(I have pyvips installed, but I cannot actually tell what copyparty is using? Is there a config setting I'm expected to specify, or will it just always prefer pyvips over ffmpeg even if it finds both?)

hey o/
I believe the --th-no-crop option does what you want, so please give that a try if you haven't :>
if that doesn't work, it could be due to one of the following:

pillow is really old
there are cached thumbnails from before --th-no-crop was enabled

installing pyvips would get around the pillow issue, and clearing the thumbnail cache can be done by deleting the th folder inside the volume's .hist folder.
btw, apparently the no-crop option is currently only available as a global option -- it would be nice if it was available as a volflag as well, so I'll fix that!
regarding which library is currently in use for thumbnailing, this should get printed on startup:
18:39:38.525 thumb      decoder preference: pil, ff

...meaning that it'll try pillow first, and then fallback to ffmpeg if that fails, as I don't have pyvips installed currently.
All of these facts should definitely be better documented, so I'll see what I can do about that... always the hardest part :-p
Let me know how it goes!

I believe the --th-no-crop option does what you want, so please give that a try if you haven't :>

Oh that's brilliant, thank you! Yeah I don't think there's a mention of it in the readme (?), so please consider adding it in the thumbnails section or so
Other than that - it worked perfectly as expected c:
Some notes for future people potentially reading this issue:

The .hist folder is at the root of the copyparty volume, not in the root of the actual subfolder with your pictures (makes perfect sense, but I had to take a second to realize that).
Remember to refresh the browser cache for the page also cause it'll still re-use those thumbnails (hard-reloading works just fine)


Invalid validation IsChildOf

The method IsChildOf returns an invalid result in the following test-case:
parentDirectory = new String("D:/Foo").ToAbsoluteDirectoryPath();
m_PathString = new String("D:/Foo bar").ToAbsoluteDirectoryPath();
public bool IsChildOf(IDirectoryPath parentDirectory) {
            Debug.Assert(parentDirectory != null);
            string parentPathLowerCase = parentDirectory.ToString().ToLower();
            string thisPathLowerCase = m_PathString.ToLower();
            ...
            return thisPathLowerCase.IndexOf(parentPathLowerCase) == 0;
}

thisPathLowerCase.IndexOf(parentPathLowerCase) === 0 will result in true, but m_PathString is no child of parentDirectory.

Fixed, thanks for this feedback!
https://github.com/psmacchia/NDepend.Path/commit/63f94840e552db181ff215c9dbca62e2c418757c
Unfortunately github wasn't showing up this commit straight, so I revert it a first time, and then both commits shown up, so I reverted it again.
https://github.com/psmacchia/NDepend.Path/commit/2c18a35c63644f740671da888d1aa64203931cd0
https://github.com/psmacchia/NDepend.Path/commit/8504c6b2fa52af54a5ab2e42f88df68c0f05433f
Not sure if one needs to wait until github show a commit? Anyway I downloaded the zip and it looks like the fix is in there.


TSC 1.8.9 - TSConfig.json - Files not used by default

Additional information on Closed issue #8145 (I don't think I have permission to re-open)
TypeScript Version:
1.8.9
Thanks for investigating.
I noticed you are using tsc v1.8.10 to try to reproduce.
My globally-installed version is currently 1.8.9.
I think this version may have been installed with the recently-released VS Code 1.0.
It is with VS Code that I first encountered the issue - but it also occurs at the command line (with tsc v 1.8.9)
As an experiment, I used a local NPM install of tsc v.1.8.10.
If i then invoke the compiler thus:
.\node_modules.bin\tsc -p .
the HelloWorld.js file is generated.
So, for information:

Are you able to test this issue with tsc v1.8.9?
and/or
Is there a VS2015 tools installer for tsc v1.8.10 (which seems to resolve the problem) I can use?

I usually use this link to install the Typescript compiler and VS2015 tooling:
https://www.microsoft.com/en-us/download/details.aspx?id=48593&751be11f-ede8-5a0c-058c-2ee190a24fa6=True

looks like a duplicate of https://github.com/Microsoft/TypeScript/issues/7032.
This is a bug in tsc.exe in 1.8.* releases. it does not reproduce with node tsc.js (which .\node_modules.bin\tsc is an alias to).
To work around the issue, pass the complete path:
tsc --p c:\test\8145

instead of
tsc --p .