Does Not Accept Elliptic Curve CA Signed Server Certificate

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[X] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
Importing a CA signed elliptic curve certificate to OpnSense results in "The certificate modulus does not match the signing request modulus."
To Reproduce
Steps to reproduce the behavior:

Go to 'System > Trust > Certificates'
Click on '+' to create a new certificate.
At the 'Method' drop-down select 'Create a Certificate Signing Request'
At the 'Key Type' drop-down select 'Elliptic Curve'
Enter a 'Common Name'
Click 'Save'
Click on 'update csr' and copy the CSR from the 'Signing request data' box.
Submit the CA (EJBCA) for signing.
Paste signed certificate into the 'Final certificate data' box.
Click 'Update' and notice the error message: "The certificate modulus does not match the signing request modulus."

Expected behavior
Certificate should be accepted.
Describe alternatives you considered
During step 4 above, select 'RSA' instead of 'Elliptic Curve'.  The generated certificate is now accepted.
Relevant log files
Found nothing in the logs sadly.
Additional context
Saving both the CSR and certificate to a file and running them through openssl ..... -pubkey results in the same public key being displayed.
Environment
Software version:
OPNsense 24.1.4 (amd64).
Intel(R) Core(TM) i5-7400T CPU @ 2.40GHz (4 cores, 4 threads)

The legacy version doesn't offer key type selection, the new version which will be released in 24.7 (and 24.10 for the business edition) should be better in that regard. Closing this ticket as the code on the master branch contains the new code.


FancyZone Resizing

When removing a window from the FancyZone, I would like it to return to the original size of the window. Much like currently happens when using the built in W10 'zones'. This saves having to resize the window to the size it was originally.

@Ajonymous
this option will be available in 0.20.
Closing as duplicate of https://github.com/microsoft/PowerToys/issues/166
Thanks.


Tighten a SILVerifier check: there should be at most one debug variable defined per function argument

This is a follow-up on https://github.com/apple/swift/pull/7508

@swift-ci please smoke test

@adrian-prantl Adrian, is this what you had in mind?

@swift-ci please smoke test

@swift-ci please smoke test

@adrian-prantl Adrian, I think I covered all the change requests you had. Please have a look.

@adrian-prantl Fixed! :-)

@swift-ci please test and merge

@swift-ci please test and merge

@swift-ci please smoke test and merge

@swift-ci please test and merge

The OS X test failure is unrelated as it happens outside of the verifier.


RPM measurement would fulfil this to a perfect device

Hi,
first of all thanks for this great project. I have no use for single sensors due to the lack of communication ports on the Rx so I am working with the OXS sensor project but this one seems to be a bit easier to handle and since I am only using Jeti the usage is more focussed.
The only thing I am missing at the moment is a RPM measurement by using the RPM-Signal (usually a TTL-signal) coming from most ESCs.
Maybe there is a chance to implement that if the resources on the ProMini and your resources may allow that. The only setup parameter required is a division parameter to adress motor poles / gears.
Regards and thanks again for your efforts
Onki

Please look for example at VarioGPS or OpenXsensor . I have no plans to make combination-sensors.


tutorial for mass endpoint

@jessfraz, I think there might be an issue with the sdk for the mass and volume, either that or I'm not using it correctly.
I added get_volume.py and get_mass.py and functions for the new endpoints return very similar errors.
Error(error_code=<kittycad.types.Unset object at 0x7f4791aa6d90>, message='unable to parse query string: missing field `src_format`', request_id='96a9e6f1-bb24-4be0-827d-176251cde478', additional_properties={})

and
Error(error_code=<kittycad.types.Unset object at 0x7fe68ec4beb0>, message='unable to parse query string: missing field `src_format`', request_id='073782d6-4c1e-42c8-95e5-03eb6181ae77', additional_properties={})

respectively.
Might the SDK not be adding the query param?
see #32.

Edit: looks like it's putting the format into the path not the query?
https://github.com/KittyCAD/kittycad.py/blob/main/kittycad/api/file/create_file_volume.py#L17

oh it very well could be! i can try and fix tomorrow

its likely somewhere around here: https://github.com/KittyCAD/kittycad.py/blob/main/generate/generate.py#L234
if you get to it before me

I fixed the go one

Ah thanks!
I've started looking at the python one, and I think I was wrong with my original guess about it being put into the path. Not sure where the problem is.

oh thats it tho! It needs a check for if its in the query or the path, essentially its trying to add it to the path but failing since there are no more vars!

this is a dumb diff i have so far but its not adding the query yet:
+    in_query = []
     if 'parameters' in endpoint:
         parameters = endpoint['parameters']
         for parameter in parameters:
@@ -246,12 +247,16 @@ response: Response[""" + success_type + """] = await """ + fn_name + """.asyncio
             else:
                 print("  parameter: ", parameter)
                 raise Exception("Unknown parameter type")
-            f.write(
-                ", " +
-                parameter_name +
-                "=" +
-                camel_to_snake(parameter_name))
+            if parameter['in'] == 'path'
+                f.write(
+                    ", " +
+                    parameter_name +
+                    "=" +
+                    camel_to_snake(parameter_name))
+            elif parameter['in'] == 'query'
+                in_query.push(parameter)
     f.write(")\n")
+    # Now we add the parameters to the query if there are any.
     f.write("\n")
     f.write("\theaders: Dict[str, Any] = client.get_headers()\n")

maybe that helps
also the makefile has some nice commands like make generate and make shell to pop you into a container w all the deps

Ah okay
Thanks for the makefile tip, mostly trying to grok the repo at this point.
This is mostly likely useful context for when I get around to making the JS SDK.

It’s one gigantic printf lolOn Jun 13, 2022, at 8:29 PM, Kurt Hutten @.***> wrote:
Ah okay
Thanks for the makefile tip, mostly trying to grok the repo at this point.
This is mostly likely useful context for when I get around to making the JS SDK.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Hot tip: don't create a virtual python environment in the python SDK repo and expect make generate to still work 🤦
and yeah for sure, is this how code gen is normally done? tbh I was expecting AST related code, but I haven't every written openAPI code-gen, only used existing ones.

im sure the AST people are like WTF lol

Thank you!
And yeah fair enough. From memory the names for everything in AST land are not the most intuitive to say the least.


STM32 USB serial example fails to compile on L476RG

The code tries to use USB-synced HSI48:
https://github.com/embassy-rs/embassy/blob/0b015bd727547d1eade5cd12c8b6a1b77483e6db/examples/stm32l4/src/bin/usb_serial.rs#L26
which triggers not-found errors on both hsi48 field and Hsi48Config struct in HAL, presumably because this board lacks hardware support.
I have copied the CubeMX solution, namely to use PLLSAI1_Q, and it seems to work, though I don't know if this is an optimal one:
   config.rcc.clk48_src = Clk48Src::PLLSAI1_Q;
   config.rcc.pllsai1 = Some(Pll {
        source: PLLSource::HSI,
        prediv: PllPreDiv::DIV1,
        mul: PllMul::MUL12,
        divp: None,
        divq: Some(PllQDiv::DIV4), // 16/1*12/4=48
        divr: None,
    });
    config.vbus_detection = false; //VBUS is not connected on my board

L476RG doesn't have HSI48 nor CRS (needed for sync_from_usb).
The solution is to use PLL, yes.  (HSI48 with CRS can sync to USB to get accuracy, but the regular HSI can't)


Evaluate metadata management services for integrating with the data platform

User Story

As a data platform owner I want to be able to provide a single location for discovering, documenting, and understanding the lineage of data
As a data platform consumer I want to be able to find data relevant to my needs and understand its context

Description/Context

In order to provide a cohesive view of our data platform and the various data sets that are available we want to implement a cross-cutting metadata platform. This will provide visibility into the full lineage graph of a given data asset (e.g. database table, dashboard report, report export delivered via Dagster, etc.). There are numerous open source and commercial options available, so the purpose of this issue is to establish a set of evaluation criteria and select a solution that we would like to implement.
Acceptance Criteria

[ ] Integrations are available for consuming metadata from our various platform components

[ ] Dagster
[ ] Trino
[ ] dbt
[ ] Superset

[ ] Supports column level lineage
[ ] Has search/discovery functionality for data sets
[ ] Provides a means of documenting data sets
[ ] Supports tagging and tag propagation based on lineage (e.g. tag a column in raw with pii and propagate to mart tables/dashboards)

Plan/Design

Review relevant documentation and pricing information available for each platform. Perform a simple proof of concept implementation of the top contenders.

Products to be considered:

OpenMetadata - https://docs.open-metadata.org/v1.2.x
Egeria - https://egeria-project.org/
Truedat - https://www.truedat.io/#

We ultimately selected and deployed Open Metadata. Integration work is being tracked in #1355


netbox: 3.5.6 -> 3.5.7 + migration fixes + upgrade NixOS test

Description of changes
Changelog: https://github.com/netbox-community/netbox/releases/tag/v3.5.7
Some other fixes:
Move migrations into the preStart of netbox.service, and run the reindex command, to allow searches. These migrations are now only run on upgrade/downgrade, or on first run since application of this PR.
Add a netbox-upgrade test to test that the upgrade from NetBox 3.3 -> netbox 3.5 works fine. This test can be reused later for other major upgrades.
Things done
All NetBox-related tests pass (netbox, netbox_3_3, netbox-upgrade)

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
made sure NixOS tests are linked to the relevant packages

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

1 package blacklisted:

nixos-install-tools

1 package built:

netbox

cc @RaitoBezarius & @n0emis
Let me know if either of you want to be added as maintainer of the netbox-upgrade test.

@n0emis what did you have in mind for error handling? I'm more inclined to let the preStart script as-is, instead of "silently succeeding" if there's an issue.


[Fix-7349][Dolphinscheduler] Fix Dolphinscheduler/pom.xml remove redundant parameters [zookeeper.version]

Purpose of the pull request
fix Dolphinscheduler/pom.xml remove redundant parameters [zookeeper.version]
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

Codecov Report

Merging #7486 (d452082) into dev (2f7a406) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##                dev    #7486   +/-   ##
=========================================
  Coverage     41.26%   41.26%
  Complexity     3661     3661
=========================================
  Files           636      636
  Lines         26444    26444
  Branches       2960     2960
=========================================
  Hits          10911    10911
  Misses        14508    14508
  Partials       1025     1025

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 2f7a406...d452082. Read the comment docs.


✨ [Feature] 给所有facades都加上接口注释

Before feedback (在反馈之前)

[X] There are no features that I want to submit in Issues (当前 Issues 中没有我将要提交的新功能)

Describe Feature (描述功能)
类似这样，方便开发的时候能直接看到不用频繁去翻文档：

像carbon这样双语的感觉不错？

I suggest that we only use English in the code for now ~


Bad display when block is long

https://github.com/Endle/fireSeqSearch/releases/tag/0.0.16
Deficient
If the block is very long, for example, you clipped a long article into logseq, then the summary would be hard (or useless) to read. That's why there is a "Hide Summary" button.

What about trying a flexbox multi-column layout? I could give the design a go

What about trying a flexbox multi-column layout?

Thank you for your suggestion. Currently, I consider it as a server side issue, as a long paragraph will be entirely included in the summary


Socket mode and proxy not working

(Filling out the following details about bugs will help us solve your issue sooner.)
Reproducible in:
The Slack SDK version
slack-bolt==1.3.0
slack-sdk==3.3.0
slackclient==2.9.3
slackeventsapi==2.2.1
Python runtime version
Python 3.8.6
OS info
Windows 10
Microsoft Windows [Version 10.0.19041.746]
Steps to reproduce:
client = WebClient(token=config.SLACK_BOT_TOKEN,
                   proxy="http://myproxy:8080"
                   )
app = App(client=client)

Expected result:
Application working
Actual result:
DEBUG:slack_sdk.web.base_client:Sending a request - url: https://www.slack.com/api/auth.test, query_params: {}, body_params: {}, files: {}, json_body: {}, headers: {'Content-Type': 'application/json;charset=utf-8', 'Authorization': '(redacted)', 'User-Agent': 'Python/3.8.6 slackclient/3.3.0 Windows/10'}
DEBUG:slack_sdk.web.slack_response:Received the following response - status: 200, headers: {...}, body: {'ok': True, 'url': 'https://....com/', 'team': '...', 'user': '...', 'team_id': '...', 'user_id': '...', 'bot_id': '...', 'is_enterprise_install': False}
DEBUG:slack_sdk.web.base_client:Sending a request - url: https://www.slack.com/api/apps.connections.open, query_params: {}, body_params: {}, files: {}, json_body: None, headers: {}
DEBUG:slack_sdk.web.slack_response:Received the following response - status: 200, headers: ..., body: {'ok': True, 'url': 'wss://wss-primary.slack.com/link/?ticket=...}
INFO:slack_bolt.App:Using non-ssl socket to connect (MYPROXY:8080)
WARNING:slack_bolt.App:Received an unexpected response for handshake (status: 400, response: HTTP/1.1 400 Bad Request
Cache-Control: no-cache
Pragma: no-cache
Content-Type: text/html; charset=utf-8
Proxy-Connection: close
Connection: close
Content-Length: 716, session id: ...)

I checked the proxy logs and got the following:
GET <invalid request url>

failed because: Scheme was not delimited by '://'

Hey @franco-martin,
I believe this is a duplicate of https://github.com/slackapi/python-slack-sdk/issues/948. We have an open PR for this in #951

hey @stevengill thank your for the quick response, I dont think so. That user is getting timeouts and the issue is for because its ignoring the HTTP proxy. Im using an HTTPS proxy and getting bad request errors. My app is connecting but sending incorrect data. Does that make sense?
This is why im suspicious of the following
 INFO:slack_bolt.App:Using non-ssl socket to connect (MYPROXY:8080)

I think It should be using an ssl socket

@franco-martin Although the error you're facing is a bit different from the one in that issue, the pull request should resolve this issue. The current implementation is just incomplete.


Error

how can i solve this? I'm running right?

I went to check the code and the error log is already activated
http://prntscr.com/p2bag3

its not activated yet.
change error_reporting(0); to error_reporting(E_ALL);
and change false to true on both ini_set()

I think I already know the error, I am using vps and is blocking my access, I will download it on my computer and warn you, then I will test on cpanel
http://prntscr.com/p2bfeq
(changed false to true now)

okay. let me know if it works or not.

http://prntscr.com/p2bo0f
ok it worked perfectly thank you so much for your support

you cant run it using your browser. you need to run it using the terminal

yes, it was just a test, I prefer to use in the browser, I will adapt the code to use via form with $ _POST if you allow
one question, can you tell me if this cron is correct?

php -q / home / habbosho / public_html / run

sure you can modify what you want 👍
about your question:
i would use like this: php -f /path/to/run

ok congratulations on your work you are awesome


Never brought to the Field Mapping page

Click on the Save and continue to be taken to the field mapping screen

After clicking this the page refreshes and gives me a "Feed saved" notice at the top of the screen with no other errors or messages.
Working on a fresh install of:

Craft CMS 2.6.2780 Personal License
Feed Me 1.4.9

Hi - are you able to submit your feed info through the Help page for Feed Me?

Sent! Thanks.


Fix loading spinner stuck issue

The loading spinner by default is rendered as svg element with animations which will get stuck when large dom manipulation, e.g., let's say it takes 10 seconds to insert elements to the document, the spinner will get stuck in 10 seconds, i.e., no animation.
Add a property useDiv to force px-spinner render as div element.
Add demo and test case.
Update px-spinner version.

@joshsylvester @evanjd @MichaelZaporozhets @sheela-svmx @benjaminliugang pls help review.

cc @shao @inothings

Here is a simple way to reproduce this stuck issue.

Open https://www.predix-ui.com/#/elements/px-spinner
Open Chrome Developer Tools and go to Console Tab.
run below codes.

const ed = new Date(new Date().getTime() + 1000 * 10)
while(new Date() < ed) {
}

You'll see the spinner animation gets stuck for 10 seconds.
With the fix, i.e., set useDiv=true, animation will be still running.

@evanjd pls help review again. Also did some clean code for old test case.

Thank you for your pull request. We require contributors to sign our Contributor License Agreement here.

@evanjd Looks can't sign the CLA, after click "I Accept", it just redirects me to the https://www.predix-ui.com/#/develop/cla again. (We are from ServiceMax, do we still need to sign the CLA. :))

v2.3.0 has been released with your change: https://github.com/predixdesignsystem/px-spinner/releases/tag/v2.3.0
It should be visible on the predix-ui component page in 5-10 minutes.

@evanjd Awesome! Thanks.


Fix declaration/assignment order

This PR makes sure builtin-ops is declared before assigning it to default.ops

Hey @hollinwilkins, this change resulted from an issue that seems to present itself when you use something other than sbt/sbt-assembly to produce a fat JAR.  We're exploring using bazel as a build for some of our projects and our resulting fat JAR failed to load this config properly because these lines were out of order.


[QUESTION] Are you going to make a logo for scratchattach?

Are you going to make a logo for scratchattach?

if you have to uch time, you always can make a tutorial how to use scratchrequest (my library) :D

UMm

Idk I would rather make a tutorial for scratchattach because a lot of people are having a hard time using scratchattach

Are you going to make a logo for scratchattach?

maybe

Because I am going to make a tutorial of how to use scratchattach

sounds interesting, I'm sure it will help people who are new to python

Ok and thx

I am bad at logo design but I am going to try tho

@mas6y6 FelixCodeur (on scratch) made one. Idk if it's still shared, but maybe you can use that.

I'll try making a logo too. I have a neat idea that I think you might like.

I'll try making a logo too. I have a neat idea that I think you might like.

Can you send my a message or comment on my scratch if it's done or say me where i can find it when it's done?

I'll try making a logo too. I have a neat idea that I think you might like.

Can you send my a message or comment on my scratch if it's done or say me where i can find it when it's done?

When it's done, I'll send the svg file here. I recommend using boxy svg to export the image to whatever size you need. It is a payed program, but I like it a lot, and on linux it's free. (Don't use scratch to export an image of it, please use an actual svg program.)

This will be the scratchattach logo for now:

If you have ideas for a better logo, feel free to post them here :)

This will be the scratchattach logo for now:

If you have ideas for a better logo, feel free to post them here :)

Alright. That's actually literally what I was doing, but you did it way better.

Maybe you can add something scratchy?

Maybe you can add something scratchy?

Like this?

Awesome!!!


Richest Customer Wealth

I want to add code for richest customer wealth , leetcode problem.
Please assign it to me for hacktoberfest.

PR added, please merge


<urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:727)>

<!--

######################################################################
  2020-03-15 06:34:01] Starting new import 81251006
[2020-03-15 06:34:01] Starting import thread 1
[2020-03-15 06:35:01] 100% done

[Thread  1] [2020-03-15 06:34:01] Started import 81251006
[Thread  1] [2020-03-15 06:34:01] Started line #1
[Thread  1] [2020-03-15 06:34:01] Grabbing gallery https://xhamster.com/videos/amazing-asian-teen-virgin-gets-fucked-hd-9559203...
[Thread  1] [2020-03-15 06:34:01] Using grabber xhamster.com
[Thread  1] [2020-03-15 06:34:07]
ERROR: Unable to download webpage: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:727)> (caused by URLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:727)'),))
[Thread  1] [2020-03-15 06:34:07] ERROR: video page gives unexpected error:Empty response from youtube-dl
[Thread  1] [2020-03-15 06:34:07] Finished

2020-03-15 06:34:01] Starting new import 81251006
[2020-03-15 06:34:01] Starting import thread 1
[2020-03-15 06:35:01] 100% done
[Thread  1] [2020-03-15 06:34:01] Started import 81251006
[Thread  1] [2020-03-15 06:34:01] Started line #1
[Thread  1] [2020-03-15 06:34:01] Grabbing gallery https://xhamster.com/videos/amazing-asian-teen-virgin-gets-fucked-hd-9559203...
[Thread  1] [2020-03-15 06:34:01] Using grabber xhamster.com
[Thread  1] [2020-03-15 06:34:07]
ERROR: Unable to download webpage: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:727)> (caused by URLError(SSLError(1, u'[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:727)'),))
[Thread  1] [2020-03-15 06:34:07] ERROR: video page gives unexpected error:Empty response from youtube-dl
[Thread  1] [2020-03-15 06:34:07] Finished


307 temporary redirect issue .. caused by npm/<EMAIL_ADDRESS>

Preliminary Checks

[X] I have reviewed the documentation: https://clerk.com/docs

[X] I have searched for existing issues: https://github.com/clerk/javascript/issues

[X] I have not already reached out to Clerk support via email or Discord (if you have, no need to open an issue here)

[X] This issue is not a question, general help request, or anything other than a bug report directly related to Clerk. Please ask questions in our Discord community: https://clerk.com/discord.

Reproduction
https://www.ekksite.com
Publishable key
pk_test_YXdha2UtYWlyZWRhbGUtNzAuY2xlcmsuYWNjb3VudHMuZGV2JA
Description

  |
-- | --
GET |
scheme | https
host | awake-airedale-70.clerk.accounts.dev
filename | /npm/<EMAIL_ADDRESS>
Address | [2606:4700:8392:f8f1:aa39:50d:3478:6a32]:443
GET
scheme
https
host
awake-airedale-70.clerk.accounts.dev
filename
/npm/<EMAIL_ADDRESS>Address
[2606:4700:8392:f8f1:aa39:50d:3478:6a32]:443
Status
307
VersionHTTP/3
Transferred73 kB (264.89 kB size)
Referrer Policystrict-origin-when-cross-origin
DNS ResolutionSystem
access-control-allow-origin
*
alt-svc
h3=":443"; ma=86400
cache-control
private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0
cf-ray
8ef829ba19aea788-DEL
content-length
0
date
Mon, 09 Dec 2024 21:42:05 GMT
location
https://awake-airedale-70.clerk.accounts.dev/npm/<EMAIL_ADDRESS>priority
u=3,i=?0
server
cloudflare
server-timing
cfExtPri
set-cookie
__cf_bm=T_wBz9PRripnSPIETUhD76zIdHZ6zEckwLxYTr0LyLg-1733780525-<IP_ADDRESS>-OzMJBHkbn2WJJyLkoDNQc9_dNr9lUtlV7MgjlV0HzGmgM5dgQzMb9QTvZ1TJDtJykiI4mfg6IAGQbYJoTVObDQ; path=/; expires=Mon, 09-Dec-24 22:12:05 GMT; domain=.awake-airedale-70.clerk.accounts.dev; HttpOnly; Secure; SameSite=None
set-cookie
_cfuvid=nG1Do3QXv7DQ5fW9nGY5tMXvtTCeyDMsKp05tcmAQyo-1733780525150-<IP_ADDRESS>-604800000; path=/; domain=.awake-airedale-70.clerk.accounts.dev; HttpOnly; Secure; SameSite=None
vary
Accept-Encoding
Accept
/
Accept-Encoding
gzip, deflate, br, zstd
Accept-Language
en-US,en;q=0.5
Connection
keep-alive
Host
awake-airedale-70.clerk.accounts.dev
Origin
http://localhost:3000/
Referer
http://localhost:3000/
Sec-Fetch-Dest
script
Sec-Fetch-Mode
cors
Sec-Fetch-Site
cross-site
User-Agent
Mozilla/5.0 (M
Environment
npm
nextjs app router

Hello, thanks for the issue. Since you didn't leave any description of what your issue is or what you expect to happen I assume you mean the redirect. That is totally fine and working as expected.


Examples use older version of lib

For example:
https://github.com/asfktz/autodll-webpack-plugin/blob/master/examples/recommended/package.json#L11
This can be used either with "autodll-webpack-plugin": "latest" or "autodll-webpack-plugin": "file:../../" as used in the minification exmaple.
Personally, I feel using a latest published version in the examples might be better. But using the file version would handle API changes(if any, in the future) better.

I prefer latest because as a user it might be confusing to try to run the examples and see them fails if you don't know that you must build the project first.
In the contribution guide, we can explain that it is possible to test the examples using npm link
What do you think?

@asfktz that sounds perfect.

done.


Presentation: Load built-in rulesets as code rather than separately delivered assets

imodel-native: https://github.com/iTwin/imodel-native/pull/467

/azp run iTwin.js


Use CocoaLumberjack 2.0 API

RestKit currently uses deprecated CocoaLumberjacks 1.9.x legacy macros.
It should be updated to use the new API from CocoaLumberjack 2.0

A PR would be welcome!

@segiddins Will try to find the time for it ;)


[BUG] - Loading of serizalized MixerType broken

Describe the bug
Loading a serialized experiment with a defined MixerType fails with:
ValueError: 'IQ' is not a valid MixerType
The serializer tries to instantiate the class with mapped_class(val), which is only valid for const arguments for the definition of the MixerType as introduced in 2.10, MixerType["IQ"] has to be called instead of MixerType("IQ").
To Reproduce
Try to load, for example, the following compiled experiment:
compiledexperiment.zip
Expected behavior
SerializedObject should still be able to load
Code & Screenshots
Versions used:

laboneq: 2.10
zhinst-core
others

Context

[ ] Do you know a workaround for the issue? If yes, please provide a short description.
[ ] Does the issue block your experiments?

Hi @GlaserN, thanks for this. We're looking into it.

Hi @GlaserN , this fix is included in the 2.12 release so I'm closing this issue.


[Feature Request] exportstealthaddress

importstealthaddress <scan_secret> <spend_secret> [label]
Apparently we have import, yet we can't export?
We need.
exportstealthaddress
returns {"scan_secret":"xxx", "spend_secret":"xxx"}

thats a solid idea. alot of solid ideas coming from you past few days =]

Thanks <3, tearing through the RPC endlessly.

i see that lol

Also implemented a new RPC command for exporting single stealth addresses with the following standard:
{ "scan_secret":"xxx", "spend_secret":"xxx", "label": "xxx" }

merged in


Backend: get_aliased_box should not create boxes

The semantics of the initializer of a mutable field in NewObjE is that
it should alias the value; this is needed for async/await.
To be aliased, that variable must be put in the heap, as a HeapInd.
Previously, if that was not the case, we’d simply create a new box. But
that breaks the semantics! (I don’t think this could be observed in
source, though).
Better if get_aliased_box fails if it doesn’t find the value allocated
on the heap. And to make sure it always is on the heap, we have to treat
the initializer in NewObjE a bit like a mutable variable captured by a
lambda. And then it seems to work.

I couldn't run the tests locally (something wrong with wasmtime). Will have to investigate the CI failures.

Ok, this seems to work now.
@ggreif, this simplifies your work, right?

Oh, I think this can be improved, and the Code Smell be fixed:
If we have a mutable variable on the top level that’s used in a record, then we can still allocate it statically, and put the pointer to that static location into the record!

Ok, this is prettier

and it will work out nicely.

I suspect that is not enough. A mutable cell is still being created (with bogus content: 0, then the original mutbox pointer)
let e = { e = 42 in c };  // base c has a `c` field

    i32.const 2
    call $alloc_words            -- mutbox
    local.tee $heap_object
    i32.const 9
    i32.store offset=1
    local.get $heap_object
    i32.const 0                    -- WUT?
    i32.store offset=5
    local.get $heap_object
    local.set $$c/6
    local.get $c
    local.tee $$base/17
    i32.const 99
    call $obj_idx<0>
    i32.load offset=1        -- mutbox pointer from `c`
    local.set $new_val.1
    local.get $$c/6
    local.get $new_val.1
    i32.store offset=5        -- another store into the mutbox
    i32.const 5
    call $alloc_words         -- alloc of `e`
    local.tee $obj
    i32.const 1
    i32.store offset=1
    local.get $obj
    i32.const 2
    i32.store offset=5
    local.get $obj
    i32.const 65747
    i32.store offset=9
    local.get $obj
    i32.const 84            -- `42`
    i32.store offset=17  -- store of field `e`
    local.get $obj
    local.get $$c/6
    i32.store offset=13  --  store of field `c`
    local.get $obj
    local.set $e


xsa files

Xilinx transitioned from xilinx SDK to vitis in vivado 2019.2.
In this transition, they obsoleted their "hardware description file" (.hdf) format and replaced it with a new file format (.xsa).
Unfortunately, the commands for generating this new format are different.
Either a function needs to be added to support generation of (.xsa) files, or the previous function needs to be modified to detect the version of vivado (or add an option to the function for the caller to choose) and generate the appropriate output accordingly

I don't want to download a newer version of vivado to deal with this.
I've abandoned development of this project, and don't think I have many users (or know of any that require this feature).
I just wanted to document this as a known issue.

if someone uses this project, and needs to generate the xsa file, comment on here to let me know, and I'll try to work with you on it.


Included a my following Blogs category

What is the change?
I have made another category for user dashboard named "My following Blogs"
Related issue?
close: #719
How was it tested?
It was tested on my local machine
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelines while contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Did you lint your code before making the Pull Request?
[x] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.
[x] Have you tested the code before submission?

Screenshots or Video:
https://user-images.githubusercontent.com/61948033/118625504-b52ebe80-b7e7-11eb-8384-77a47b1c2d62.mp4

@all-contributors please add @tend2infinity for code


Import data with Entries Fieldtypes

Hello,
I would like to use the add-on to import several collections. They are linked with multiple Entries Relationships between them.
The issue is that the import writes the title in the md file, which leads to an "ID not found" error on the control panel. IT happens with relationships between collections (entry fields) as well as taxonomies.
Is there any way to get the import to actually create the related entry, if not already found the same title on the related collection?
Thanks a lot!
Collection photographer:
--- id: 4d57d874-43ac-457a-a1bd-be5b0ce21671 blueprint: fotografen title: 'Eugéne Atget' ---
Collection Books:
`---
id: be8816fb-5927-47fb-bdb2-b0441b139f78
blueprint: buecher
title: 'Atget Eugène'
herausgeber:

'Martinez Romeo'
fotografie:
'Eugéne Atget'
verlage:
Electa
updated_by: e44e1a4c-15f3-4cb4-bdcd-d6e6bb5a8a8d
updated_at:<PHONE_NUMBER>
---`

I have found one possibility to fix it after importing the main collection with this script. I will look up all entries and create new ones in the related collection and correct the link to ID. It uses the title to match.
You need to empty the cache afterwards as the entries appear duplicated in the CP, but they are not.
<?php

use Statamic\Facades\Entry;
use Statamic\Facades\YAML;

function findOrCreateEntry($collection, $title) {
    $title = trim($title);
    $entry = Entry::query()
        ->where('collection', $collection)
        ->where('title', $title)
        ->first();

    if (!$entry) {
        $entry = Entry::make()
            ->collection($collection)
            ->slug(strtolower(str_replace(' ', '-', $title)))
            ->data(['title' => $title]);
        $entry->save();
        echo "Created new entry in {$collection}: " . $title . "\n";
    }

    return $entry->id();
}

function updateEntries($sourceCollection, $targetCollection, $fieldToUpdate) {
    $entries = Entry::query()->where('collection', $sourceCollection)->get();
    $updatedCount = 0;

    foreach ($entries as $entry) {
        $data = $entry->data()->toArray();
        $updated = false;

        if (isset($data[$fieldToUpdate]) && is_array($data[$fieldToUpdate])) {
            $updatedField = [];
            foreach ($data[$fieldToUpdate] as $value) {
                if (!is_string($value)) {
                    $updatedField[] = $value; // Keep non-string values as-is
                    continue;
                }
                $targetId = findOrCreateEntry($targetCollection, $value);
                $updatedField[] = $targetId;
                $updated = true;
            }
            $data[$fieldToUpdate] = $updatedField;
        }

        if ($updated) {
            // Update the entry in place without creating a new one
            $entry->data($data)->save();

            // Update the markdown file
            $path = $entry->path();
            $content = YAML::dumpFrontMatter($data) . "---\n";
            file_put_contents($path, $content);

            echo "Updated entry in {$sourceCollection}: " . $entry->get('title') . "\n";
            $updatedCount++;
        } else {
            echo "No update needed for entry in {$sourceCollection}: " . $entry->get('title') . "\n";
        }
    }

    echo "Finished updating entries in {$sourceCollection}. Total updated: " . $updatedCount . "\n";
}

// Example usage (to be called from Tinker):
// updateEntries('buecher', 'fotografen', 'fotografie');
// updateEntries('$sourceCollection', '$targetCollection', '$fieldToUpdate');


kubectl help sometimes does not line wrap properly

e.g. the first line of kubectl proxy -h; this is due to using h4 for this line, which (user-agent default) does not line wrap.

Desired:

Side comment: I notice poor contrast in the copy widget for this theme.


feat(types): Include new organization role guest_member

Type of change

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

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[x] @clerk/types
[ ] @clerk/clerk-expo
[ ] @clerk/backend-core
[ ] @clerk/clerk-sdk-node
[ ] @clerk/edge
[ ] build/tooling/chore

Description

[ ] npm test runs as expected.
[ ] npm run build runs as expected.

This PR includes the new organization role guest_member.

I've just noticed that we've exposed two different constants for the membership role. It's also here: https://github.com/clerkinc/javascript/blob/a4439a08c16e3e424a9a0d0f7aa62ac59fea55b4/packages/backend-core/src/types/jwt.ts#L49

I believe we should refactor the one in jwt.ts to use the enum value.

@gkats It feels weird to have a package called types which would depend on a package called resources.
I would expect it to be the other way around, i.e. have all the types declared in Enums to be in the types package instead.
Anyway, I'm modifying these two types to include the extra role but I will avoid removing the JWT type at this point. Let's take this offline and have another PR to tackle it.


feat: Match size of the input images

Description
Can you put some parameter to make images that do not have the same size be paired and obtain the same width or height?
Requirements

[ ] be able to match the size of input images

Additional Context

can you provide the images here? @kei-kusanagi
I'll try to have a look
But maybe you can use the itemXBuilder and some kind of IntrinsicHeight

Sorry for the delay, here are the two images in their respective sizes

Ok, no problem, it is not something that important, since usually when comparing images they tend to have the same size, but I had a doubt about what would happen if they had minimal differences, that's why I looked for similar images but of such different sizes. :P, thank you again for your answers and sorry for my bad English, I'm still learning it just like Flutter (I've been learning it for about 6 months).

Your English is quite good, so don't worry!
Also don't hesitate to write me if any question comes to your mind 😊 @kei-kusanagi


(PUP-11934) Use String#each_codepoint instead of deprecated String#codepoints

Does codepoints produce the wrong results in newer JRuby?

No, but it prints a deprecation message to the log when it's called.
In MRI that usage was marked as deprecated in a previous version of Ruby and the documentation for it has been removed: https://ruby-doc.org/3.2.2/String.html#method-i-codepoints

@justinstoller will this need to target 7.x too? We think we're testing against 9.3 there, but we weren't sure if it issues the same deprecation warning?

It can target 7.x, but it's only problematic in 8.x. (at least so far) JRuby started warning in 9.4.3 not 9.3.x. I don't know if they plan to backport that warning. Lemme know if you'd like it cherrypicked.

Rebased onto 7.x

Closing and reopening to rekick checks


Hide the Border Control HUD Button

Hello!
I was hoping if it might be possible to have a checkbox to hide the border control button on the Token HUD.
This mod is fantastic, thank you so much for your work!

Yup, perfectly possible


More Issues templates to organise Issues

As more people contribute to your project, the issue tracker can start to feel hectic.
When someone opens a new issue in your project, you can now prompt them to choose from multiple issue types.

Awesome, thank you 👍


Ignore a warning in kubectl apply when namespace is already created.

Fix: https://github.com/istio/istio/issues/18948

In response to a cherrypick label: new pull request created: #624


Ec2MetadataRegionProvider being used even when use-default-aws-region-chain is set to true in application.yml

Type: Bug
Component:
"SQS"
Describe the bug
Version of Spring Cloud:
org.springframework.cloud:spring-cloud-dependencies:Hoxton.SR9
Which resolves to spring cloud aws version 2.2.5.RELEASE
spring-cloud-starter-aws-messaging 2.2.5.RELEASE
Our spring boot application is running in ECS Fargate and uses spring-cloud-starter-aws-messaging to access SQS. When the application starts up I see the following error in our logs:
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [com.amazonaws.services.sqs.buffered.AmazonSQSBufferedAsyncClient]: Factory method 'amazonSQS' threw exception; nested exception is java.lang.IllegalStateException: There is no EC2 meta data available, because the application is not running in the EC2 environment. Region detection is only possible if the application is running on a EC2 instance
--
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:185)
at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:650)
... 56 common frames omitted
Caused by: java.lang.IllegalStateException: There is no EC2 meta data available, because the application is not running in the EC2 environment. Region detection is only possible if the application is running on a EC2 instance
at org.springframework.util.Assert.state(Assert.java:76)
at org.springframework.cloud.aws.core.region.Ec2MetadataRegionProvider.getRegion(Ec2MetadataRegionProvider.java:40)
at org.springframework.cloud.aws.core.config.AmazonWebserviceClientFactoryBean.createInstance(AmazonWebserviceClientFactoryBean.java:110)
at org.springframework.cloud.aws.core.config.AmazonWebserviceClientFactoryBean.createInstance(AmazonWebserviceClientFactoryBean.java:49)
at org.springframework.beans.factory.config.AbstractFactoryBean.afterPropertiesSet(AbstractFactoryBean.java:142)
at org.springframework.cloud.aws.messaging.config.annotation.SqsClientConfiguration.amazonSQS(SqsClientConfiguration.java:52)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)

Sample
I have already set the following in my application.yml:
cloud:
  aws:
    region:
      auto: true
      use-default-aws-region-chain: true
    credentials:
      use-default-aws-credentials-chain: true

As described in PR: #559
This should cause the framework code to use a different region provider but as you can see from the stack trace above this does not seem to work in this case.

I am not able to reproduce this issue. Does this happen only when application runs on ECS or locally too?
Can you provide a minimal sample that suffers from the same problem?

My apologies. This was a misconfiguration error on my part. Closing now.

No worries 👍


Fix parsing "double precision" of wallfilter in PostgreSQL

在PostgreSQL数据库中, WallFilter解析双精度数据类型(Double Precision)时只读取Double而忽略了precision, 会错误的报解析错误.
尝试着解决了一下, 并增加了单元测试, 请指正.

[Current coverage][cc-pull] is 72.87%

Merging [#1231][cc-pull] into [master][cc-base-branch] will increase coverage by +<.01%

2 files (not in diff) in ...m/alibaba/druid/stat were modified. more

Misses -1
Partials -2
Hits +3

2 files (not in diff) in ...m/alibaba/druid/pool were modified. more

Misses -8
Partials +1
Hits +7

2 files (not in diff) in ...va/com/alibaba/druid were modified. more

Misses -1
Partials +1

@@             master      #1231   diff @@
==========================================
  Files           841        841
  Lines         63078      63082     +4
  Methods           0          0
  Messages          0          0
  Branches      11660      11662     +2
==========================================
+ Hits          45955      45966    +11
+ Misses        12826      12818     -8
- Partials       4297       4298     +1

Powered by Codecov. Last updated by [d959f35...063e381][cc-compare]
[cc-base-branch]: https://codecov.io/gh/alibaba/druid/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/alibaba/druid/compare/d959f35a94982b70305f44a513afb732853f1f8b...063e381b634f2faa5ee4e237eb455feb557cfbcf
[cc-pull]: https://codecov.io/gh/alibaba/druid/pull/1231?src=pr

谢谢反馈


Missing View.OnKeyListener binding

It seems like binding APIs for View.OnKeyListener are currently missing.
Do you guys have any plans to add it?

Pull requests are welcome for it.
On Thu, Oct 6, 2016 at 11:33 PM Hadi Satrio<EMAIL_ADDRESS>wrote:

It seems like binding APIs for View.OnKeyListener is currently missing.
Do you guys have any plans to add it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/JakeWharton/RxBinding/issues/288, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEEEXu7jZ5evWcKKGQJInk2SvC6t8w-ks5qxb2bgaJpZM4KQpUo
.

Alright, I'll try to come up with something soon.


⚠ SceneTime has degraded performance

In b4844be, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 12304 ms

Resolved: SceneTime performance has improved in 1661187 after 7 minutes.


Prepare to set this repo public

To avoid too much overhead and to make things clear for users of Itinero1 we need to:

[ ] Provide a basic roadmap and an idea about where this project is going to go.
[ ] Cleanup the readme, build processes and provide packages.
[ ] ...

migrating to routing2, is there a basic sample. Looks like a lot has changed in initialization and routing requests.


conda installation issue

Hello,
I installed optitype using the following command:
conda install -c bioconda optitype
No errors were reported. but it seems that the machine doesnt recognize the pacakge:
I executed:
which RazerS3
It didn’t return anything
I tried with python 2.7 and python 3.
What am I missing?
Thanks,
Eila

Hi Eila,
You can run which razers3 to see the RazerS3 installation. To run the pipeline itself, you can use OptiTypePipeline.py [options]


Error when setting single proxy on Windows

Hi
It's my first time using this package. I'm trying to run the example:
print(next(scholarly.search_author('Steven A. Cholewiak')))

but got an error:
MaxTriesExceededException: Cannot Fetch from Google Scholar.

I tried to set proxy for the code. I signed in Clash for Windows; set proxy as localhost:7890
from scholarly import scholarly
from scholarly import ProxyGenerator

pg = ProxyGenerator()
pg.SingleProxy(http = 'localhost:7890')
scholarly.use_proxy(pg)

but cannot pass the example. However, I can open the page py requests.get():
x = requests.get('https://scholar.google.com/citations?view_op=search_authors&hl=zh-CN&mauthors=Steven+A.+Cholewiak', proxies={"http": "localhost:7890", "https": "localhost:7890"})

Then I read the source code, and found that if I replaced the line 104 at _navigator.py:
                resp = self._session.get(pagerequest, timeout=timeout)

with:
                if (self._session.proxies):
                    resp = self._session.get(pagerequest, proxies=self._session.proxies, timeout=timeout)
                else:
                    resp = self._session.get(pagerequest, timeout=timeout)

Then the code runs well.
Hope this finding helps your development!

It seems that you only set the proxy for http, but for not https. Then you request a URL that is an HTTPS URL.


Upload failures due to locking issue

Describe the bug
In a test environment where I placed the filesystem for decomposedfs on a remote NFS volume I see quite a few locking issue when uploading a small folder hierarchy (3 levels deep, about 500MB, 550 files in 300 directories)  via the WebUI.  This seems to be caused by lock contention (like we already saw before):
[tusd] 2022/11/10 12:12:25.692423 event="ResponseOutgoing" status="500" method="PATCH" path="/d4341f00-705f-43ed-b9e0-4629f8d631ce" error="Decomposedfs: could not set extended attribute: xattrs: Can not acquire write log: unable to acquire a lock on the file" requestId=""

This was when testing with v2.0.0-rc.1 the behavior is much better when compliing against latest reva/edge (because https://github.com/cs3org/reva/pull/3397 improved the locking behavior). So it might actually be a non-issue :crossed_fingers: once we bumped reva for the next RC.
An easy way to reproduce this, seem to be to create a deep folder structure, with a couple of files at the deepest level and upload that folder via the webui (use some NFS share for ocis strorage-users):
mkdir -p $(for i in $(seq -w 1 100); do echo -n level_$i/; done)
cd  $(for i in $(seq -w 1 100); do echo -n level_$i/; done)
for i in $(seq -w 1 1000); do echo $i > file_$i; done

@rhafer Can you update this ticket with your findings?

with https://github.com/owncloud/ocis/issues/5061 we no longer calculate the dir size, which also reduces the amount of readlocks we have to create.

I can confirm that the behavior with latest master is a lot better. But I am still able getting the locking error. When uploading 1000 files (in a single directory) via the web frontend. (on an ocis server backed  by nfs storage):
tusd] 2022/11/24 14:08:09.139959 event="ResponseOutgoing" status="500" method="PATCH" path="/d6979c17-043c-4cd5-9945-7d40bbe23234" error="xattrs: Can not acquire write log: unable to acquire a lock on the file" requestId=""
{"level":"error","service":"storage-users","pkg":"rhttp","traceid":"00000000000000000000000000000000","host":"<IP_ADDRESS>","method":"PATCH","uri":"/data/tus/d6979c17-043c-4cd5-9945-7d40bbe23234","url":"/data/tus/d6979c17-043c-4cd5-9945-7d40bbe23234","proto":"HTTP/1.1","status":500,"size":72,"start":"24/Nov/2022:14:08:07 +0000","end":"24/Nov/2022:14:08:09 +0000","time_ns":1246257073,"time":"2022-11-24T14:08:09.139993501Z","message":"http"}
{"level":"error","service":"frontend","pkg":"rhttp","traceid":"00000000000000000000000000000000","host":"<IP_ADDRESS>","method":"PATCH","uri":"/data/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJyZXZhIiwiZXhwIjoxNjY5Mzg1Mjg3LCJpYXQiOjE2NjkyOTg4ODcsInRhcmdldCI6Imh0dHA6Ly9sb2NhbGhvc3Q6OTE1OC9kYXRhL3R1cy9kNjk3OWMxNy0wNDNjLTRjZDUtOTk0NS03ZDQwYmJlMjMyMzQifQ.48NOZ1qImhwFM8tM363m5Tc3XWRmQym6lKm4q_vKdc8","url":"/data/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJyZXZhIiwiZXhwIjoxNjY5Mzg1Mjg3LCJpYXQiOjE2NjkyOTg4ODcsInRhcmdldCI6Imh0dHA6Ly9sb2NhbGhvc3Q6OTE1OC9kYXRhL3R1cy9kNjk3OWMxNy0wNDNjLTRjZDUtOTk0NS03ZDQwYmJlMjMyMzQifQ.48NOZ1qImhwFM8tM363m5Tc3XWRmQym6lKm4q_vKdc8","proto":"HTTP/1.1","status":500,"size":0,"start":"24/Nov/2022:14:08:07 +0000","end":"24/Nov/2022:14:08:09 +0000","time_ns":1246850458,"time":"2022-11-24T14:08:09.140264525Z","message":"http"}

This happens a lot less often now. For rc1 I get about 50 failed uploads, for latest master it's 0-3 failed uploads.

I've been experimenting a bit with the locking timeout and retry values in https://github.com/cs3org/reva/blob/edge/pkg/storage/utils/filelocks/filelocks.go as the default of 3ms seemed a bit low. Increasing that timeout helped a lot.  I tried with 30ms (not sure if that value makes any good sense) and didn't see lock failures anymore.
It might make sense to add configuration knobs for the filelocking timeout and retries. (I assume the behavior will depend a lot on the underlying storage)

we made the lock cycle duration factor configurable and increased it in https://github.com/cs3org/reva/pull/3493


[Doc] Recaptcha configuration doc missing in the IS 7 docs

IS 6.1 doc: https://is.docs.wso2.com/en/latest/deploy/configure-recaptcha/
https://is.docs.wso2.com/en/latest/guides/login/configure-recaptcha-for-single-sign-on/#configure-single-sign-on-with-recaptcha-globally
This is not present in the IS 7 docs
This doc is present
https://is.docs.wso2.com/en/7.0.0/guides/account-configurations/login-security/bot-detection/
But a doc for deployment.toml configurations is not present

Required to set instruction for setup recpatcha keys as well.
https://is.docs.wso2.com/en/latest/deploy/configure-recaptcha/#configure-recaptcha-api-keys

This must be included too - https://is.docs.wso2.com/en/latest/deploy/configure-recaptcha/#choosing-the-type-of-recaptcha
cc - @himeshsiriwardana


feat: enforcing labels on KafaConnection

See https://github.com/redhat-developer/app-services-operator/issues/244


Add revisionHistoryLimit to deployment

Description of the feature or enhancement:
Add option to set revisionHistoryLimit .spec.revisionHistoryLimit
Use Case:
Default value of 10 replicasets will be selected and one might want to change this.
Proposed Solution:
Adding this to deploymentProps
    /**
     * Number of desired replicasets history.
     *
     * @default 10
     */
    readonly revisionHistoryLimit?: number;

Other:
N/A

[ ] :wave: I may be able to implement this feature request
[ ] :warning: This feature might incur a breaking change

This is a :rocket: Feature Request

Hi @iliapolo this PR fixes this issue. Please review this if anything is remaining. I checked the code of cli and it uses the property names as it is. So we don't need to do any more changes. Please let me know if I missed something.

Did some digging. Added more changes to the PR as required.


Refactor /SfAccordion

Related issue

Scope of work

SfAccordionItem removed props selected, contentItems for do simplest component API
removed SfAccordionItem slot falback (v-for on contentItems)
fixed just Basic story, used MenuItem and removed others stories

Screenshots of visual changes
sftabs:mobile

sfaccorion

Checklist

[x] I followed composition rules for my component
[x] I tested the component in most common device sizes (can be tested in Storybook from viewport addon in top menu)

Looks good, but what with chevron? it should be enabled by default I believe and removable with SCSS modifier

@filrak done, I forgot about that


Request: Facing Indicators

Adding facing indicators, such as that seen in the About Face mod, would be extremely helpful as well.
As of now that’s the only reason I haven’t converted over, a couple of my PCs still don’t use top down portraits and can’t handle rotation, yet I would like to know which way they are facing.

Unfortunately, this might take a while to implement. The method About Face uses to show indicators requires patching core Foundry code, which I would rather avoid if possible.
One question though - if your player's tokens don't have top-down portraits, why have them rotate? Are you using some mechanic that depends on knowing the direction a token is facing?

Yes, I am using a homebrew rule that allows Opportunity Attacks to only trigger if the creature leaving the threat range is currently the focus of the other creature (i.e. where that creature is facing). This allows “skirmisher” type fighters like Rogues to enter into melee range, attack, then retreat without triggering Opportunity Attacks. My players love this mechanic but it relies on knowing which direction a creature is facing.
It works on physical tabletop, of course, because miniatures have a facing and we can rotate the pieces. But when we play on Foundry we have to rely on memory for this. Hence, facing indicator would be helpful.
Thanks for the suggestion. Alas, rotating character portraits also look really wonky 😅.

@JLtheking2 I'm probably going to implement this as a separate module, since there are multiple uses for being able to place an underlay on a token.
(By the way, I'm curious - is the cunning action feature not allowed? That allows rogues to disengage as a bonus action)

@JLtheking2 I'm probably going to implement this as a separate module, since there are multiple uses for being able to place an underlay on a token.
(By the way, I'm curious - is the cunning action feature not allowed? That allows rogues to disengage as a bonus action)

Thanks for the update! Looking forward to it :)
For my houserule, cunning action is definitely allowed and still very useful. But the point of that houserule is to allow characters that aren’t rogues engage in that kind of hit-and-run style of play too, which I find is fun. Taking a full action to disengage is very punishing for non-Rogue characters, and this mechanic allows pieces on the board to still move around relatively freely and dynamically to take advantage of flanking bonuses and the like.
As we know in vanilla, once the melee PCs start engaging with the enemy melee characters, combat kinda just becomes kinda stale with no one having any reason to move. With flanking bonuses are involved, you often get into a ridiculous conga line situation with everyone forming up into a line and no one able to move for fear of triggering two opportunity attacks. My house rule helps out with that.

Thanks for the update! Looking forward to it :)
For my houserule, cunning action is definitely allowed and still very useful. But the point of that houserule is to allow characters that aren’t rogues engage in that kind of hit-and-run style of play too, which I find is fun. Taking a full action to disengage is very punishing for non-Rogue characters, and this mechanic allows pieces on the board to still move around relatively freely and dynamically to take advantage of flanking bonuses and the like.
As we know in vanilla, once the melee PCs start engaging with the enemy melee characters, combat kinda just becomes kinda stale with no one having any reason to move. With flanking bonuses are involved, you often get into a ridiculous conga line situation with everyone forming up into a line and no one able to move for fear of triggering two opportunity attacks. My house rule helps out with that.

This feature is very useful for GURPS gaming, especially if you are using pog-style tokens (not top-downs). I would very much like to see it implemented.

Hello,
Chipping in on the Token Facing Indicator similar to About Face, extremely useful for systems like WFRP 4e. You mentioned a separate module for this but could not find it. Can you link?
Thanks,
a.

Also interested in the facing direction functionality - for my homebrew flanking rules only the person behind a flanked enemy gets advantage on the attack. So being able to show which direction a character/enemy is facing on their turn would be extremely helpful for those of us that prefer framed tokens.

Thanks for the answers @Varriount much appreciated!

I'd be very interested in a module thatt allowed for a underlay as well.


ReactiveUI 6.5.1

What is it?
(Can't find release notes, nor related commits)

https://github.com/reactiveui/ReactiveUI/releases/tag/6.5.1

thanks.. hmm, wondering if I overlooked it, or if this just got ninja'd in :D

@sickboy it's fairly recent, yes https://github.com/reactiveui/ReactiveUI/issues/1132#issuecomment-240346193


fix for #2

and a test that recreates the issue. All tests pass if I run meteor test-packages ./packages/* with meteor 1.7.4.

Published in v1.2.2


大佬快开源，加油

We are at the final steps of code publication process. Please bear with us a little more!
Thank you for your interest!

The code is uploaded ... Thanks for waiting.


Request to upgrade to SQLCipher 4.4.2

I'm using SqLiteStudio and they don't have a version that supports 4.4.0 unfortunately. They have recently upgraded to 4.4.2 and editing anything will make the database unreadable for SqlCipher4Unity (4.4.0) Are there plans to upgrade to 4.4.2 by any chance?
Thanks

well...
I tested my https://github.com/netpyoung/SqlCipher4Unity3D/blob/f9819ce1128f1e930a78c98c8b82e8bd981fd05e/SqlCipher4Unity3D/Assets/StreamingAssets/existing.db . It can be opened.
So Is it possible share example db file which doesn't opend in sqlitestudio? I will test that.
and To catchup latest version of sqlcipher is a little hard to me (Now I don't have mac machine... and I need to buy mac machine..) to build for mac machine.
But If you really want to use latest version of sqlcipher you can build with my build script.

Thank you for testing this for me.
I decided to start a new project to doublecheck and it does indeed work fine. I must have another issue in my main project that is causing this, my apologies.


Single result page modal behavior

Description
Single result pages will be styled as modals when navigated to from the search results view, but will be full-width pages when visited server-side, direct from a shared url, for example. You can observe this behavior on Unsplash by searching for an image, viewing the result, and then refreshing the page:
https://user-images.githubusercontent.com/6351754/144637806-7b4fb2c4-96d1-41b0-a04e-de9fd89f2689.mp4
Typically, the best way to build this is by moving the search grid / search results up into a layout, and then conditionally rendering them based on if there's an active search query or not. It's a bit of challenging work!

I have been playing with different ideas, and here is the version I like most for both single result views.

Header ideas
For the header, I tried a more prominent search bar, an expanded internal menu, and hiding the search result controls (content switcher + filters) since both are content-related. But I also tried showing the openverse logo (symbol + name) as thinking of users opening an Openverse link without knowing the tool. In that scenario, adding the openverse name would help with adding more context.
That being said, the header used in mockups has a full-width grid of Modal L, as introduced in ticket #522.

Regarding Full size M audio component, I tested different widths and background colors.
Audio component versions
A full-width grid with a gray background version looks centered and balanced, but when playing it, the yellow background will look odd since it does not start from the far-left beginning.

A full-width grid with white background version looks clean and it blends greatly with the header. However, by consistency, the image single result page looks floating and empty due to white space on the sides. Plus the yellow background problem when playing the audio.

Finally, a full-page width with white background also looks beautiful by the blending effect, and it works well with showing the yellow background. But it has the consistency problem with the image single result view.

I updated the Releases file with the mockups, and the Design Library with a new variant of the header component: Header. Modal.

The simplest way to do this off the top of my head:
When navigating to a single result from the search result pages, display the single audio/image view in a modal and update the url without re-routing. When single result links are visited directly, continue the same behavior we have now of showing them as standalone pages.


should the examples work? SetPindirsConsecutive instead of SetConsuecutivePindirs???

I'm struggling to get the examples to work.  I changed line 11 in blink_pio.go to
sm.SetPindirsConsecutive(pin, 1, true)
and I got it to work.  I suspect the API morphed after the examples were written?

Whoops! Yes you are correct, that was an outdated API. Thank you for submitting this issue! Fixed in latest commit to main


Change std::list to std::deque for tuple cache

An STL implemented deque usually allocates memory in pools, which reduces calls into memory allocator. This also makes deque much more cache friendly than list.
In production, we observe 2.5x performance improvement with this change. Locally, I saw ~5% improvement.

👍

👍


Decoder

It would be nice to have a mode that decoded hex-encoded script, like bitcoin-cli decodescript but much faster. Then we could do something like:
./bitcoin-iterate -q --output=%os --start 0 --end 80000 | btcs --decode

Reminder to self: reset memory arena for each input line. This should be obvious but I don't trust my brain to remember such things.

done in 142a953fa026aa904e52e846967d5dc6af3271b9


Outdated package for urdf_parser_py present on PyPI

I am surprised we do not have this issue open, as I think we already discussed this about this in the past.
Anyhow, the current situation is that this library is (also) a ROS-independent library and it is packaged as such in conda-forge (), and is packaged with an old (and unmantained) version in PyPI: https://pypi.org/project/urdf-parser-py/
Just opening the issue to track the fact that downstream users of this parser are looking into forking it as it is not on PyPI, see for example https://github.com/dora-rs/dora/pull/704 or https://github.com/ami-iit/adam/issues/36 .
Possible solutions include:

Try to claim back the urdf_parser_py name on PyPI
Package the library under the urdfdom-py name (that is how the package is packaged in ROS) so that it can contain an updated version.

Something that I never thought is to just contact who uploaded the package to PyPI in the first place, that is https://pypi.org/user/xinsongyan/ .
@xinsongyan sorry to disturb you, just in case do you happen to be the same person that uploaded urdf_parser_py to PyPI. Whould you be interested in updating the version there or sharing the maintenance there so that a updated version is uploaded? Thanks in advance, and please ignore if you are not https://pypi.org/user/xinsongyan/ .

Hi, Silvio,
yes, I uploaded urdf_parser_py some time ago, it might be outdated. I can
update it, it this the newest version (https://github.com/ros/urdf_parser_py
)?
I can also share the maintenance with you, what is your user name on pypi?
[image: image.png]
Thanks,
Songyan
On Thu, Nov 7, 2024 at 1:19 PM Silvio Traversaro @.***>
wrote:

Something that I never thought is to just contact who uploaded the package
to PyPI in the first place, that is https://pypi.org/user/xinsongyan/ .
@xinsongyan https://github.com/xinsongyan sorry to disturb you, just in
case do you happen to be the same person that uploaded urdf_parser_py to
PyPI. Whould you be interested in updating the version there or sharing the
maintenance there so that a updated version is uploaded? Thanks in advance,
and please ignore if you are not https://pypi.org/user/xinsongyan/ .
—
Reply to this email directly, view it on GitHub
https://github.com/ros/urdf_parser_py/issues/85#issuecomment-2462222572,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABUZMOAUW43GRMEO3SKYQ6TZ7NSGTAVCNFSM6AAAAABRLFXA56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRSGIZDENJXGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks @xinsongyan, nice to meet you! Thanks a lot, the latest version is https://github.com/ros/urdf_parser_py/releases/tag/1.2.1 .

I can also share the maintenance with you, what is your user name on pypi? [image: image.png]

Thanks a lot, https://pypi.org/user/traversaro/ .

I added you as a maintainer, you can update it on your side.
Thanks,
Songyan
On Fri, Nov 8, 2024 at 4:34 PM Silvio Traversaro @.***>
wrote:

Thanks @xinsongyan https://github.com/xinsongyan, nice to meet you!
Thanks a lot, the latest version is
https://github.com/ros/urdf_parser_py/releases/tag/1.2.1 .
I can also share the maintenance with you, what is your user name on pypi?
[image: image.png]
Thanks a lot, https://pypi.org/user/traversaro/ .
—
Reply to this email directly, view it on GitHub
https://github.com/ros/urdf_parser_py/issues/85#issuecomment-2465224579,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABUZMOH7DIGJPQF6IA6FQ5DZ7TRX7AVCNFSM6AAAAABRLFXA56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRVGIZDINJXHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks a lot!

To check how to upload to pypi, I first started doing an experiment with TestPyPI, with this commands:
conda create -n testuploadurdfpy python pip twine python-build
conda activate testuploadurdfpy
git clone https://github.com/ros/urdf_parser_py
cd urdf_parser_py
git checkout 1.2.1
python -m build
twine upload --verbose -r testpypi dist/*

this currently fails with error:
Uploading urdfdom_py-1.2.1-py3-none-any.whl
100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 20.1/20.1 kB • 00:00 • 21.0 MB/s
INFO     Response from https://test.pypi.org/legacy/:
         400 Bad Request
INFO

           <title>400 'License :: OSI Approved :: BSD' is not a valid classifier. See
         https://packaging.python.org/specifications/core-metadata for more information.</title>

400 'License :: OSI Approved :: BSD' is not a valid classifier. See
         https://packaging.python.org/specifications/core-metadata for more information.

           The server could not comply with the request since it is either malformed or otherwise incorrect.

         'License :: OSI Approved :: BSD' is not a valid classifier. See
         https://packaging.python.org/specifications/core-metadata for more information.

ERROR    HTTPError: 400 Bad Request from https://test.pypi.org/legacy/
         Bad Request

After fixing this with https://github.com/ros/urdf_parser_py/pull/88, the package is now available at https://test.pypi.org/project/urdfdom-py/ . So, it seems that to upload the new package, we need nevertheless to upload it under a new name urdfdom-py. Unfortunately there is no easy way to deprecate a PyPI package and point users to a new package (see https://discuss.python.org/t/adding-a-mechanism-to-deprecate-a-published-project/13937/, https://github.com/pypa/packaging.python.org/issues/883), but we could always upload a simple metapackage to urdf_parser_py that installs the new urdfdom-py package.

Recap
Let's do a bit of recap. @clalancette if you like, feel free to ignore the rest of the conversation and just check this recap.
First of all, it is important to clarify that this repo is named urdf_parser_py, but it contains the urdfdom-py Python package that itself contains the urdf_parser_py Python module. This is a bit complicated, but it is important to point out as it means that if we want to package this library in PyPI, we need to do it under the urdfdom-py Python package name.
Problem
There is an outdated version of the urdf_parser_py python module uploaded as the urdf_parser_py uploaded on PyPI, and many users use it (~1000 downloads per day, see the OP for more description).
Possible Actions Points
Option 1: Do nothing, i.e. do not package the package on PyPI. A fair point may be "this is a ROS 2 package, and if we allow people to also download it from PyPI, this could lead to confusion of users installing it from both apt ROS 2 packages and PyPI, leading to confusing errors". However, there is already a urdf_parser_py package on PyPI, so  I am afraid that ship has already sailed.
Option 2: A third-party (i.e. different from the urdf_parser_py maintainers, for example me) upload the updated urdfdom-py to PyPI, independently from the repo itself. This in theory does not require any permission or action from urdf_parser_py maintainers (at the moment just @clalancette), but in practice I would like to make sure that the maintainers do not object this. This is a bit similar to what we did for the conda-forge packaging of this repo in https://github.com/conda-forge/staged-recipes/pull/21870 and https://github.com/conda-forge/urdfdom-py-feedstock, but the situation here is a bit more "strange" as typically PyPI uploads are managed by the library maintainers directly, not via third-party packages as it happens in most other non-language specific distros.
Option 3: We integrate PyPI upload of the urdfdom-py package via GitHub Actions in this repo. This has the advantage that new tags will be automatically uploaded to PyPI, but also requires to be fully onboard on this. If it is helpful, I would be happy to help as a maintainer of the repo in this case.
If we go for Option 2 or Option 3, we can also upload a urdf-parser-py meta-package that only installs urdfdom-py to ensure that anyone that installs urdf-parser-py gets the updated version of the urdf_parser_py python module, but that is quite orthogonal.


[Configuration]Validate configuration on launch

It would be great to validate configuration changes when the program launches to proactively catch issues

Transitioned to Jira


Support semistandard formatter

Should this package support semistandard through options?
Something like I did in linter-js-standard:

Automatically check style in package.json devDependencies.
Manual choosing the style

Yes, I think that would be a good feature. Maybe if I get some time this weekend I can take a look at getting it in there.

Just tested it, it's great :+1:
Thank you, :heart: your tool!


Release v1.1.0-beta2

cc @mwielgus

Should be merged after #1166

@k8s-bot test this please

LGTM


What th meaning of "Duration" field in xUnit tab?

As I can see in example report duration is test-after-test incremented time (next duration = all previous tests xexution times plus current) but I suppose it should be durarion for each test only.
Is this feature or bug? If it it feature, could you explain use cases?

@clicman this is probably because we're using manually created XML files for that. I would say this is caused by copy-paste in XML files.

@clicman please reopen if you consider that an issue. You could send a PR with more random start and stop timestamps to allure-core as well.

Could not reopen, but it is not copy-paste. There is a link to archive link. All of steps are sleep for 5 seconds and it is easy to calculate that problem exists.

@baev thoughts?

@clicman I see the problem. What version of maven surefire plugin are you using?

2.18

try to use 2.17 or less

problem in the following lines:
https://github.com/allure-framework/allure-core/blob/master/allure-junit-adaptor/src/main/java/ru/yandex/qatools/allure/junit/AllureRunListener.java#L42-L44

@baev

try to use 2.17 or less
I can`t. I need a parent description on testRun started

And it really fixes the problem? I was initially removed this code from cucumber-jvm adaptor, but bug here. Okay, I will try to investigate problem as soon as i have time.

Commented related PR.


Script task with DELETE request that return 204

Hi. I'm not sure that this is the proper channel for your excellent service app.effektif.com, but I'll make a try.
I have a script task that makes a DELETE call to a service. The service responds with 204 (No content) and the script task hangs!? Since I also have control over the service where the call is directed I changed the response code to 200. And now everything work fine. But it would, imho, be more proper REST if I could use 204. Is it any special reason why this doesn't work?

Hi, the correct support channel is the Send Feedback menu item in the app; I’ll pass this one on for you.
I can reproduce this, using Mocky to generate an HTTP 204 response, with the following script:
request('http://www.mocky.io/v2/556c028cc7c1599106d0e172',
	function (error, response, body) {
	    console.log(response.statusCode);
	}
);

The result of running the script test in the process editor is:

Timeout exceeded after 30 seconds
Test execution failed at 09:00:48

And for future problem you can find the feedback form right in your user menu in the upper right corner of the application.

Thank you for the swift response. I also found the user guide! The app is rather self-explanatory so I havn't needed it before, but still it's good to know. :)

@paed01 unfortunately I cannot reproduce this error. Neither locally nor on our production system. Can you maybe give me a short outline of the script your trying to run?

I have a REST-service that accepts DELETE requests.
When I make the delete call to the service from an effektif script task, like this:
var options = {
  method: 'DELETE',
  url: 'http://example.com/api/arbitary'
};

request(options, function(err, response, body) {
  // never reached - timeout
  console.log(err, response, body);
});

The REST-service reports that the call has been made and responds with statusCode 204. But the script task times out, as in hiltons comment.

I could only reproduce this behaviour when I configure an endpoint that returns a status code of 204 but does content in the response body. Can you please check that the body of your response is empty?

Good point in checking the response of the delete request, it is:
HTTP/1.1 204 No Content
Server: Cowboy
Content-Length: 0
Connection: keep-alive
Content-Type: text/html; charset=utf-8
Cache-Control: no-cache
Date: Fri, 05 Jun 2015 06:32:14 GMT
Via: 1.1 vegur

To make sure we talk about the same thing - I'm using script tasks in a process hosted at https://app.effektif.com.


[incubator][VC] add more test case to pod dws test

pod dws coverage 65.3% -> 82.3%
there are cases not covered:

client-go failure. fail to get object
operation race. such create pPod but already exists

Signed-off-by: zhuangqh<EMAIL_ADDRESS>

/approve
/lgtm


add a useSourceAsTarget option

This flag indicates if the source should be copied to target for new trans-units

Coverage increased (+0.2%) to 93.037% when pulling 911641fb1bca17e49d271df17b7ccbfa7c55ed4e on feloy:master into 401d21d930d37b23e6400367bdf2df323de4a31c on martinroob:master.


Alignment mode for cover & contain

I messed up my repo, so here another pull request for the issue.
I added support for aligning cover & contain. Currently the original image is always centered.
To not break the api, the mode is set prior cover/contain with align( bits )
Available modes are, which act as a bit mask:
Jimp.HORIZONTAL_ALIGN_LEFT
Jimp.HORIZONTAL_ALIGN_CENTER
Jimp.HORIZONTAL_ALIGN_RIGHT

Jimp.VERTICAL_ALIGN_TOP
Jimp.VERTICAL_ALIGN_MIDDLE
Jimp.VERTICAL_ALIGN_BOTTOM

Now you can i.e. align top-left, center-bottom etc.
image.align(Jimp.HORIZONTAL_ALIGN_LEFT | Jimp.VERTICAL_ALIGN_TOP);
image.cover(w, h);

image.align(Jimp.HORIZONTAL_ALIGN_CENTER | Jimp.VERTICAL_ALIGN_BOTTOM);
image.contain(w, h);

Nice. I'll integrate your code but implement it slightly different to fit with existing patterns. Something like this:
image.contain(w, h, Jimp.HORIZONTAL_ALIGN_LEFT | Jimp.VERTICAL_ALIGN_TOP);

+1

Cool! Thanks so much a lot and sorry for the big delay getting back to you. Ready to merge now – but the repos now in conflict.
I can try and resolve them but you might be quicker. If you re-subit, I'll pull in, test and release later this week.

You don't need to merge this one because I did the job here #137

LOL!  So I didn't cross check any of them.
Great stuff! Thanks for the addition! It looks great!


[Grouped Updates] Implement experimental rules for dependency types and semver limits

This branch introduces a new experiment flag: grouped_updates_experimental_rules
With this experiment enabled the follow changes happen by default:

Dependency Groups will not longer include Major version upgrades
Any Major upgrades available will be opened in a separate PR.

It also allows two new configuration rules:
# Grouping by update-type
groups:
  production-dependencies:
    patterns:
      - "*"
    update-type: "production"
  development-dependencies:
    patterns:
      - "*"
    update-type: "development"

# Custom SemVer groups
groups:
  patches:
    patterns:
      - "*"
    highest-semver-allowed: "patch"
  small-upgrades:
    patterns:
      - "*"
    highest-semver-allowed: "minor"
  big-upgrades:
    patterns:
      - "*"
    highest-semver-allowed: "major"

These rules are not final syntax, we still need to do a naming pass and also resolve how existing rules interplay with them so this may churn.
Approach
The implementation of update-type filtering is fairly trivial, Dependabot::Dependency objects implement a production? method so we do this pretty much the same way we filter on dependency name.
The trickier case is Semantic Versioning which we do by injecting ignore conditions for any versions of a Dependency outside the highest patch level allowed.
This strategy means the group does the right thing with very few snags - the tricky part is that assuming that the group(s) only cover up to minor patch levels we will then want to provide PRs for any major versions available separately.
For this spike, I've only gone so far into the logic required to do this efficiently so the heuristic is:

If any dependencies are in only groups with highest-semvar-allowed below major, attempt a separate update

This is a good enough strategy for now, but for large projects it would be crushingly slow as we'd currently call out to the package manager twice for everything when we already know the versions available.
This spike has already gotten pretty long so I'd rather put a cut line here as I'd like to test this in some real-world conditions on projects where we can control the size/tolerate the added runtime to validate the work so far.
Next Steps
The two main things that need to happen with this approach are:

Look at the global ignore conditions to determine the maximum semver the job permits for * dependencies and start using that as the cap on whether we try a separate update
Start comparing the latest_version and latest_resolvable_version to determine if there are actually any upgrades ahead of the group to further avoid double work
Look at how we can start implementing caching of the version lists we look up, this will likely need some per-ecosystem work

Dependency Groups will not longer include Major version upgrades

@brrygrdn and I had an interesting chat about this, I get the decision for this default, but I think it would be interesting to explore a way we can make this config more explicit, I could imagine it being a confusing experience otherwise. No need to block on that while this is behind a feature flag though


Scope for potential patch release r1.3 (v0.11.1/v0.1.1)

Problem description

Some smaller issues were identified with the public release r1.2 within the meta-release. It is not yet decided if and when such patch release will be created, but it has to be
Expected action

Issues to be included if a patch release will be created:

#361
#341 (PR #367)

Further issues to be addressed:

#376

documentation of expected behaviour only, API changes within patch release

#359

clarification in documentation only

#377 (with PR #382)

To be addressed when creating the patch release:

#363 (to be addressed within the release PR)

Additional context

Regarding #362

documentation of expected behaviour only, API changes within patch release

Risk here is that in absence of guidelines in current release, some early implementation had taken its own decision, and if we give now some guideline in other direction, that would make those early implementations incompatible with the new patch. On the other hand, if we keep the gap, the risk of implementations having different behaviour for the same input is also there.

A decision was not made, but it seems likely that #362 will not be included in this patch release.  This will be discussed further once a PR is available to review to impact of the change.

We need to add the changes coming from Commonalities and ICM to the scope:

error definitions
changes for (implicit) subscriptions
update of info.description texts
Concrete issues to be created when the alpha releases of Commonalities and ICM are available.

Added #377  with PR #382 to the patch release scope.


Help with a React quickstart

Your library looks incredible, Mr Maslov! Sorry for looking like a complete moron but I never worked before with wasm and I am a bit too lost trying to implement anything, just make it work with a simple create-react-app type of base. I tried to organize the React component but it looks way too much to try to adapt into a small, working, piece of component.
Would you have any small snippet on how to simply make it work with a React app? Thank you so much!

Hi Pedro, thank you! For the React example you can use this very repo. There was no point in creating a separate repo for that. In fact it is created using create-react-app.
You can check out the vanilla-js example https://github.com/maslick/koder-vanilla-js if you wish.

This repo doesn't provide a React component in the form of an npm library. Contrary, this repo is an integration example, which you can reuse while building your own QR-code scanner.
There's an npm package, however, but it only works for node.js server-side apps and Browser apps (see https://github.com/maslick/koder-vanilla-js).

If you don't want to bother much with all the integrations (WASM, Web workers, Service workers, etc.), and all your web app needs is the ability to scan QR/bar codes, take a look at Kameroon - QR/bar code scanner as a Service https://github.com/maslick/kameroon. There are two demo apps:

React app: https://github.com/maslick/kameroon-demo
Vanilla js app: https://github.com/maslick/kameroon-demo-js

Here's some description I gave on how Kameroon works: https://github.com/maslick/koder/issues/81#issuecomment-1717071941


Python setup & Fix Test error

This PR adds information about the required Python version and jep, as well as fixes some remaining errors in the testing code.

You may want to specify which python version is needed exactly (and also set this version in the GitHub runner). @maximiliankaul can help there, it is probably 3.9 or 3.10 with this CPG release version.

I checked the cpg release that is used (4.6.0) and in its README it states only 3.10 is supported


Implement template locators

To introduce new attributes:

[FindTemplate] : could be specified for control type (only once) and will contain string template of control locator
[FindParam] : could be specified for page object field/property (only once) and will contain string parameter to substitute into a template

during PageObject initialization templates will have higher priority over general [Find]

implemented #19


Avoid errors with strip option

Fixes #50

A test, please?

No test?

Did this ever get merged? Having this error in 0.3.0 still

This issue still exists in 0.3.0, any chance this will ever be merged?


Proper way to access d3 scale objects for x/y axes for manual additions?

I need to draw some additional elements on a chart, basically some fancy lines and images for various data points.  I couldn't find anything proper in the API, but I did find that I could scale my x and y coordinates (and do everything else related to d3 scales) using c3chart.internal.x(valueX) and c3chart.internal.y(valueY), and then draw around those in d3.
Is there anything better?  I assume since I'm accessing .internal that this isn't an official part of the API.  I'd be happy to code up some sort of raw d3 or scaling API if other folks think it's worthwhile.

Your way is what I intended. .internal is not documented yet, but I'm planing to do that and some part of APIs will be moved to .internal in the future.

Please let me close at the moment.


[BUG] Comments Cause Make, Wash Lint and Validate to Fail if Placed Below Attribute Tag

Describe the bug
No Error:
@n(0)
@required
fieldName

Error:
@n(0)
// comment
@required
fieldName

Error:
@n(0)
@required
// comment
fieldName

To Reproduce
Steps to reproduce the behavior:

Create an interface
Within a structure, copy one of the error blocks above.
Run Wash Lint or Make

Expected behavior
Comments should not cause an error.  If this is expected behavior, and a comment should not be placed below an attribute tag, is it documented?
**Environment (please complete the following information) **

OS: 5.15.78-1-MANJARO
Shell zsh
wash Version 0.13.0

I agree it's non-intuitive, since in rust you can mix the order of macros and doc comments.  This rule makes it easier one for the smithy parser to distinguish between general comments in the file and comments associated with an item.
The parser is working in agreement with the Smithy 1.0 specification

documentation comments MUST appear before any traits applied to the shape in order for the documentation to be applied to a shape.

While we can't easily change the smithy spec, we do want the developer experience to be good, and it should never be a requirement that every developer is intimately familiar with a detailed spec. Just as with a programming language syntax error, we would want error messages that tell the developer exactly what the problem is, so they learn the rules and can fix problems quickly.
If the error messages were incomplete or misleading we'd appreciate suggestions for improving them.

I think a clear indication that there can't be a comment below a Smithy trait would be all that was required.
Below are error messages I experienced from Wash Lint and Make. The Wash Lint error at least makes it easy to see what is wrong, but not why. If there is some way to indicate in an error that a comment can't be below a Smithy trait, that would be much more clear for these occurrences.
Wash Lint Error:
smithy error: assembling model: Error(
    Deserialization(
        "Smithy IDL",
        "pest",
        None,
    ),
    State {
        next_error: Some(
            Error {
                variant: ParsingError {
                    positives: [
                        identifier,
                        a_trait,
                    ],
                    negatives: [],
                },
                location: Pos(
                    1645,
                ),
                line_col: Pos(
                    (
                        55,
                        3,
                    ),
                ),
                path: None,
                line: "  /// indication whether the request was successful",
                continued_line: None,
            },
        ),
        backtrace: InternalBacktrace {
            backtrace: None,
        },
    },
)

Make Error:
error: failed to run custom build command for `jammin_interface_music_auth v0.1.0 (/home/stephen/Repos/Jammin_Prototype/interface/jammin_interface_music_auth/rust)`

Caused by:
  process didn't exit successfully: `/home/stephen/Repos/Jammin_Prototype/interface/jammin_interface_music_auth/rust/target/debug/build/jammin_interface_music_auth-aec7c1aa355a97e3/build-script-build` (exit status: 1)
  --- stdout
  cargo:rerun-if-changed=/home/stephen/Repos/Jammin_Prototype/interface/jammin_interface_music_auth/codegen.toml

  --- stderr
  Error: Model("assembling model: Error(\n    Deserialization(\n        \"Smithy IDL\",\n        \"pest\",\n        None,\n    ),\n    State {\n        next_error: Some(\n            Error {\n                variant: ParsingError {\n                    positives: [\n                        identifier,\n                        a_trait,\n                    ],\n                    negatives: [],\n                },\n                location: Pos(\n                    1645,\n                ),\n                line_col: Pos(\n                    (\n                        55,\n                        3,\n                    ),\n                ),\n                path: None,\n                line: \"  /// indication whether the request was successful\",\n                continued_line: None,\n            },\n        ),\n        backtrace: InternalBacktrace {\n            backtrace: None,\n        },\n    },\n)")
make: *** [interface.mk:45: all] Error 101


Homekit integration doesn't work for any of the sensors

Using a IVT, KM200 integration everything works fine in Home assistant.
Once integration with homekit is enabled, non of the sensor information is going across to apple devices. Homekit doesn't even see those entities. They are correctly added to config. Climate and water_heater are correctly working in homekit but no sensors.
This issue only hits sensor type information. Those sensors are enabled in settings, and are properly displaying on HA dashboard. I tried variety of sensors.
homekit:
filter:
include_entities:
- sensor.komfovent_outdoor_temperature_c
- sensor.bosch_outdoor_temperature
- sensor.system_pressure
- switch.komfovent_eco_mode
- climate.hc1
- climate.hc2
- water_heater.dhw1

I don't know what might be issue with homekit as I never used it.
Can you send screenshot of developer tools states of this sensor sensor.bosch_outdoor_temperature?

There you go!

ok, so I don't know. Units and device class are properly set.

@pszafer  for future reference, after removing two properties from the sensor the homekit integration correctly transfered it into apple home.
state_class: measurement and device_class temperature.

So I think it's bug in Homekit integration as documentation of HomeKit (and many integration) requires device_class temperature

state_class: measurement it's also recommended for such sensors (at least I followed developer docs 2/3 months ago when they introduced those state classes.


Annotate the learning resources on the Documentation page with terse, useful summaries

Right now the Documentation page is a wall of links with no context given. Each link should should have something of like a short summary to inform a potential reader whether a resource is worth checking out. Summaries shouldn't be too verbose as to appear busy, just a terse description about what the doc covers. An example might be:

Learn You a Haskell for Great Good:
An illustrated book that covers the core features and syntax of the language itself, but assumes you know how to program already. Doesn't cover project setup, useful libraries, or how to approach non-trivial projects in general. Freely available online. No exercises.

:+1:

That's a very good idea. As for many other things, I think we should follow the Rust website https://www.rust-lang.org/documentation.html

Based on feedback from @jwiegley and @wiz: we should also clarify the target audience/purpose of various sections. In particular, with the books, we may want to include some version of text like:

the books in this list are the ones we know haven't scared off new users too often


Rewrite metadata reducer in TypeScript and encapsulate OutdatedVersionBanner element

Description
Objectives

Improve type safety of reducers:

Replace classiccreateFetching abstraction for JavaScript with idiomatic TypeScript.

Prepare for follow-up to replace saga with thunk.
As a prerequisite to fix layout problems with banners:

Replace various data patterns with consistent encapsulation within components.
Therefore, simplify MainPage and minimize risk of re-rendering pages.

Changed files
TODO
Residue
TODO
Checklist

[ ] Investigated and inspected CI test results
[x] ~Unit test and regression tests added~

Testing Performed
TODO

/test ui-unit-tests

I think this is a big improvement.
Only negative I want to point out is reading OutdatedVersionBanner initially made me think the component itself was outdated or old but maybe thats just me.


[zh-cn] sync concepts/workloads/controllers/replicaset.md

Signed-off-by: Gao Qian<EMAIL_ADDRESS>

/approve

/lgtm
/approve


Update Set-InformationBarrierPolicy.md

added an example

Docs Build status updates of commit 2ba0f74:
:clock10: Full build: the average full build time is 13 min(s) 57 sec(s), this is based on the last 424 build(s) for this repository.

Docs Build status updates of commit 2ba0f74:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/policy-and-compliance/Set-InformationBarrierPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from  to before v4.9.291",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=ad19f7046c24f95c674fbea21870479b2b9f5bab"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "ad19f7046c24f95c674fbea21870479b2b9f5bab",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "scsi: advansys: Fix kernel pointer leak\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v4.9.291 by commit ad19f7046c24f95c674fbea21870479b2b9f5bab. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1002231


Lack of a vscode-styled-jsx-postcss plugin

We need PostCSS, and in particular nesting, for correct override of nested components styles in Next, see relevant discussion.
However at this point vscode-styled-jsx doesn't reckognize PostCSS. There are alternatives for various styling solutions like Stylus or SCSS with corresponding language server, but none for PostCSS as far as I know.

+1

+1


Expand README synopsis

This PR adds examples of the name, type and keep-going options to the synopsis which should help users of the module wanting to use these options.  Also fixed some minor typos.

Thanks a lot! :)
I now wonder if the binding in the first example should not be dropped; I think it was initially there to have a lazy list while still having a @ prefix.


C# preprocessor expressions highlighting is inconsistent

VSCode Version: 1.3.1
OS Version: OS X El Capitan

Steps to Reproduce:
#if UNIX
            // some code here
#else
            // some code here
#endif

It's very inconsistent highlighting:

# is highlighted in the first #if, but not elsewhere
ifand else highlighted (probably as a keywords), but endif not

Moved to https://github.com/OmniSharp/omnisharp-vscode/issues/630. @vors pls subscribe to the new issue.


PARQUET-909: Reduce buffer allocations (mallocs) on critical path

@wesm @xhochy, The plan here is to avoid some of the mallocs in the write path. The current implementation uses AllocateBuffer followed by Resize very frequently. I made some changes to the column/writer.cc.  I expect similar changes in  file/writer-internal.cc in next patches.
I wanted to know your concerns if any before I proceed in this path. Thanks!

@wesm @xhochy This patch is ready. Let me know your feedback. Thanks.

I tested the changes using Callgrind.
The total number of calls to Arrow::InternalMemoryPool::Reallocate and Arrow::InternalMemoryPool::Allocate reduced to 1/4 of the original number.

Thank you for the feedback.