pick-2.0 support force set replicate allocation for olap tables (#32916)

Add a config to force set replication allocation for all OLAP tables and partitions.
cherry-pick #32916 to 2.0
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Fixed dockerfiles and updated runtime/README

I kept the docker image deploy which could also be used to run planner as a docker container.

@hectorj2f  What was the reasoning for adding the GPG keys to the repo? To increase speed or avoid problems with key-servers?

@kwk I kept them as they were before. This operation is also performed by the nodejs container at this moment.


Enable shared library build

configure should be called with --enable-shared to build the libpython .so/.dylib/.dll
Without this, VSCode cannot use its debugger and pretty-printer for Rust (which requires specifying the .dylib)

This was fixed in 7e7aa97 (PR #117). Closing.


Would you please provide a link to download detect_provided?

As is stated in the README, a detect_provided folder which contains detections and Re-ID features should be put in the dataset path. However there is no link for downloading this. Would you please fix it and provide a link? Thank you very much and regards!

we have provided a google drive link in data preparation. Thank you for your attention

we have provided a google drive link in data preparation. Thank you for your attention

Thank you for your kindness. Great idea of crosszone filtering and great job implementing the algorithm


when i use this package, the tsconfig.json has occur 2 errors like this image,as follow, how to solve it,is this packages called tsconfig's issue?

and this is Unknown compiler option 'verbatimModuleSyntax,  ts's version, i'm use ^4.7.0

@Henrycheheng Try using ^5.1.6

OK thank you. I'll try this.

I'm having same issue, updating typescript with 5.1.6 not resolving this issue for me.


Exporting scan result, vulnerable, overview in PDF, Excel, CSV file

The only reason for us stopping from kubeclarity is export option, if you can provide an option to export the vulnerabilities into a pdf or some other format, it would be great.

Same for me, very interesting project but lack of ability to export results either using integration or simply to a file in standard format, is a "deal breaker".

bump

Same for me. It should at least be able to export a text file, but it doesn't


Shaft Coupler -

Problem
There is sometimes slippage in the attachment between the shaft coupler and the motor shaft

(this image shows socket head cap screws, which have been switched to button head screws for more clearance)
Even with the de-coupling of the two clamping forces across the coupler it still sometimes does not grab onto the motor shaft well enough to hold the entire torque seen on the corners.
Solution
In order to keep the JPL open source rover up and running I've simply epoxied the couplers to the motor shafts, however for a hobby level project where one might want to change or reuse the motors this wouldn't be ideal.
Instead a coupler that can appropriately grab onto the 4mm motor shaft would be idea. This could potentially include a redesign of the scheme of attaching the motor so that you can get increased length of motor shaft to attach to as well.

Has anyone considered this? https://www.amazon.com/Stainless-Steel-Screw-Shaft-Coupler/dp/B00KQRRVHM

@davidadkins1 we used shaft couplers that were extremely similar to those ones in our first design of the rover.  We found that no matter how hard we torqued down those set screws, they would always back themselves out and lose grip on the shafts.

Initially we were using almost the exact part, however the torque seen on the corner system was higher than what the set screw was able to hold, and inevitably the set screws would loosen and back themselves out. Even with loctite this was the case eventually

On a semi-related note, I know some roboticists use motors hex drive shafts.  Without doing much digging, I found these... http://www.revrobotics.com/rev-41-1301/.  If we found a way to mount a motor with a hex drive shaft, we might be able to solve the shaft coupler problem.

I'm working on a potential 3D printed solution to this. I have designed and done a very quick test using an ABS based material, with good initial results.
Proposed Solution

Motor Mounting Hub:

Mounts the motor slightly higher up, but gives a more convenient access to the two screws that bolt into the motor. Instead of having to disassemble the entire coupler-standoff system to get to them the whole motor mount just uses the 4 bolting holes used for the pillow bearing standoffs as well.
Shaft Coupler:

This coupler takes advantage of the D-profile on both of the shafts, which will be the mating face for torque transmission. In addition with the decrease in outside diameter the upper half of the coupler can be extended to the entire length of the 4mm motor shaft, giving increased contact area. Set screws with heat set inserts will be added to handle axial loads only.
I'm going to test with ABS first and then afterwards test with Poly-Carbonate ABS well for increased hardness on the coupler.

Based on this discussion, the discussion and eventual solution on the OSR forum at https://www.tapatalk.com/groups/jpl_opensource_rover/shaft-coupler-solutions-discussion-t69.html, and @kevincloutier's pushed solution (9b407a6), I am closing this issue as solved.  Thanks everyone for the input and the design improvement!


Add api: jerry_get_value

It is used to get the reference value from a error value
Related issue #2080
If the input value is an error, then the api will return the acquired its reference value. If the input value is not an error, the api will return the acquired input value. So the caller need to release the return value.
It is a necessary supplement for jerry_value_clear_error_flag, because the jerry_value_clear_error_flag will change the input value directly and release the error-box automatically, which maybe not what developers expect.
@zherczeg @martijnthe
JerryScript-DCO-1.0-Signed-off-by: Zidong Jiang<EMAIL_ADDRESS>

I will add the doc if the reviewers are OK with the api's signature and semantic

@akosthekiss @zherczeg what do you think?

@zherczeg any further comments?

Updated
@zherczeg

Can this be merged? @zherczeg @akosthekiss
Thanks!

Yes, from my side.

@zherczeg Sorry that I missed your last comments. Updated.

@zherczeg could you take a look again? Thank you!

I'm neutral with this change, but is this still needed after #2131?

Yes, I think it is still needed. Because in our case, we just want to get the error value, we dont want to change the ref_count of the error-box.

I will merge it since @zherczeg  already gives LGTM.


WFLY-12310 Added Second Level Cache Tests

JIRA issue: https://issues.jboss.org/browse/WFLY-12310

I looked at the Linux JDK 8 failures yesterday and they don't appear related to this change.

@scottmarlow is there anything I forgot do to make this PR ready to be merged?

retest this please

how to do the retest?

@tommaso-borgato "retest this please" is the signal for CI bot to rerun tests on this PR, all passed

I'm fine with this change getting merged, I was going to look more closely but no need to block on me.  Thanks for improving the 2lc tests!

@scottmarlow  hi, @tommaso-borgato is on 2 week PTO and I'm reviewing RFEs after him. Based on the coments above this one is ok to merge, right?

Retest this please

@mnovak1 yes, it just needs to pass tests which shouldn't be a problem as it passed locally for me.

@scottmarlow  @kabir  great, thanks


[CI][MATLAB][Packaging] Add support for MATLAB R2024a in CI and crossbow packaging workflows

Describe the enhancement requested
MATLAB R2024a is the latest available version of MATLAB as of April 2024.
We are currently building against MATLAB R2023a in CI and for the crossbow packaging workflow.
We should update the version of MATLAB we support to the latest available version.
We previously created an issue to use R2023b (#37809). However, R2024a has become publicly available since then.
We may want to consider building and packaging against multiple versions of MATLAB in parallel, rather than just the latest. This would require some more thought on how many releases back to support over time, however.
Component(s)
Continuous Integration, MATLAB, Packaging

Issue resolved by pull request 41504
https://github.com/apache/arrow/pull/41504


Win/border router

I haven't even looked at the diff, I am just making this so it's here and I can look at it later.
I'm 100% sure there are somehow changes I don't want in here. I'll go through it later. If you're going to look at this I would just look at the obviously new (my) files.

Codecov Report

Merging #24 into master will increase coverage by 0.12%.
The diff coverage is 53.33%.

@@            Coverage Diff             @@
##           master      #24      +/-   ##
==========================================
+ Coverage   69.74%   69.87%   +0.12%
==========================================
  Files         172      172
  Lines       26976    26977       +1
  Branches     3368     3368
==========================================
+ Hits        18815    18850      +35
+ Misses       6749     6708      -41
- Partials     1412     1419       +7

Impacted Files
Coverage Δ

src/core/net/netif.cpp
62.37% <ø> (ø)
:white_check_mark:

tests/unit/test_toolchain.cpp
100% <ø> (ø)
:white_check_mark:

src/core/meshcop/joiner.cpp
87.64% <ø> (ø)
:white_check_mark:

src/cli/cli_server.hpp
100% <ø> (ø)
:white_check_mark:

tests/unit/test_diag.cpp
65.21% <ø> (ø)
:white_check_mark:

src/core/thread/link_quality.cpp
88.37% <ø> (ø)
:white_check_mark:

src/ncp/ncp_uart.cpp
78.04% <ø> (ø)
:white_check_mark:

src/cli/cli_uart.cpp
82.27% <ø> (ø)
:white_check_mark:

src/core/openthread.cpp
45.86% <100%> (-0.29%)
:x:

src/cli/cli_dataset.cpp
42.9% <50%> (ø)
:white_check_mark:

... and 17 more

Continue to review full report at Codecov.

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


Turning the Charger on/off does not work anymore through the integration

The problem
I have an automation that uses the switch.easee_charger_enabled to start / stop charging. But now when I use that to turn my charger on or off it does nothing.
Version of Easee integration having the issue?
0.9.59
Version of Home Assistant Core having the issue?
2024.9.1
Anything in the logs that might be useful for us?
2024-09-15 12:53:36.941 ERROR (MainThread) [custom_components.easee.switch] Forbidden turn_on on switch is_enabled

Additional information
Last Friday I also noticed that when I wanted to do that same through the official app, I also got a 403 Forbidden error. That seems to work now, but doing it through the integration still seems broken. I also tried removing and re-installing to force myself to login again, but that didn't work.

Easee has changed their sw. I had the same and made a changes via the easee web interface. My Interface is in Dutch but I think the translation is Access Control and then Access Level to Open
It's now working but I still get sometimes "Forbidden turn_on on switch is_enabled".

I have the same issue with the Easee charger. It won’t stol and start anymore.
What is the current workaround for this problem?

I can turn it off with the official app or in the web interface. Just not yet through Home Assistant. I suspect that they changed something in the API and the plugin needs te be updated?

I am experiencing the same issue.

This error originated from a custom integration.
Logger: custom_components.easee.switch
Source: custom_components/easee/switch.py:49
integration: Easee EV charger (documentation, issues)
First occurred: 15:54:11 (1 occurrences)
Last logged: 15:54:11
Forbidden turn_off on switch is_enabled

Same here.

Plus 1 for this problem

Plus 1 for this problem

There is a problem with the API at Easee's end. It is beeing investigated. Please don't fill this issue with more-of-the-same unless you have any new information.

It seems to be working again. So I assume the changed the API and not fixes need to be implemented. If it works for others I can close the ticket.

Same here it work again

On/Off is working but the Sensor information Power, Status are not updated.

Everything works as it expected again at my sites.


Upgrade HTTP to HTTPS instead of returning 426

What's other people's opinion on adding the option to redirect HTTP connections to HTTPS instead of simply returning 426 with a message to use HTTPS?

redirecting is slow and makes users lazy (they are getting away with doing nothing). Imo it is better to be strict and force usage of https by failing hard.
Only as a temporary solution while migrating from http to https a redirect makes sense to me.

I agree with the principle to be strict and force usage. But in case you cannot, here is what I did to resolve this in my case:
I created a template very similar to what is discussed in https://getkong.org/docs/0.9.x/configuration/#custom-nginx-configuration
I added the following to it which worked in my case:
    server {
        listen 80 default_server;
        listen [::]:80 default_server;
        server_name _;
        return 301 https://$host$request_uri;
    }

Then just as discussed at https://getkong.org/docs/0.9.x/configuration/#custom-nginx-configuration
you run your kong instance with kong start --nginx-conf custom_nginx.template
Kong will then use your server block rules in nginx

@samrose thx for sharing!

this work for me, thx @samrose :)

Closing, thanks @samrose for the snippet!

Just as a side note to all of you involved in this discussion, if you are indeed using a custom Nginx template for this reason (or another), I strongly suggest that you check out #2355, which makes configuring Nginx easier, and invite you to your thoughts on it. We're actively looking for feedback. Thanks!

Thanks for the snippet  @samrose - works great. I was also wondering if there is a way to perform a redirect from www to non-www while also doing an https upgrade? I'm fairly new to Nginx so I'm having trouble doing the redirect.
Basically, I want to upgrade HTTP to HTTPS and redirect www.example.com to example.com so:
http://www.example.com -> https://example.com
https://www.example.com -> https://example.com
http://example.com -> https://example.com

@andy9775 see this:
https://stackoverflow.com/a/7958540/996156
Best practice for nginx is to define a separate server for www the first example there would work if you just include 'https'

@samrose doesn't seem to be working for me. Here's my template file
worker_processes ${{NGINX_WORKER_PROCESSES}}; # can be set by kong.conf
daemon ${{NGINX_DAEMON}};                     # can be set by kong.conf

pid pids/nginx.pid;                      # this setting is mandatory
error_log logs/error.log ${{LOG_LEVEL}}; # can be set by kong.conf

events {
    use epoll;
    multi_accept on;
}

http {
    # include default Kong Nginx config
    include 'nginx-kong.conf';

    # upgrade all requests to https
    server {
        listen 8000 default_server;
        listen [::]:8000 default_server;
        server_name _;
        return 301 https://$host$request_uri;
    }

    server {
        listen 8000;
        server_name www.example.com;
        return 301 https://example.com$request_uri;
    }
}

I'm also using Docker.

@andy9775 yes, your requests are always going to get picked up by the first server block with that config. You will need to change it to something more like what is in the https://stackoverflow.com/a/7958540/996156 and drop the generic redirect from my original example. I am low on time to be able to layout a working example, but there is one at the SO link

@samrose no worries. I think I get what you're saying now. Thanks!

Shot in the dark, but has anyone been able to accomplish this on Heroku?  Imo it is better to be strict and force usage of https by failing hard.

I agree this is good if you use Kong only for internal stuff. It gives you quick feedback and you see immediately what's wrong. I don't agree when it comes to end users. Most people don't know even what https is. So they are going to see a message. Please use https.
We're Kong power users and we have some internal stuff configured in it, but also some public websites. And we love it. But we're facing an issue that we can't force SSL.
We can't use the nginx redirect to HTTPS template as some of our internal stuff doesn't work over https, and it also forces the server certificate, not the ones in Kong. The template is an all or nothing solution. I guess we need some more granular option, to redirect some public websites.

I'm in a similar situation to @vinceve , though would definitely prefer to not change our applications as a workaround. One thought was to create a plugin that redirects to HTTPS, but can be installed on routes and services. Would anyone know if this is the kind of thing you can do with a custom plugin? Is there a repo of community-supported custom plugins somewhere? I've found a few random one-offs, but imagine this isn't the most uncommon use case. Would love direction on any of these things. Thanks! (btw if I end up creating this plugin, will be open-sourcing).

 I'm hoping my company can open-source our solution, but until then this repo would be a good jumping off point for someone trying to do something similar: https://github.com/jicong/kong-aliyun-http-filter (thanks for @coopr , found this in that lua rocks search you linked)

Another option is to use the pre-function plugin with the following function attached to a route or a service
local scheme = kong.request.get_scheme()
if scheme == "http" then
  local host = kong.request.get_host()
  local query = kong.request.get_path_with_query()
  return kong.response.exit(302,"https://" .. host ..query)
end

To share an update here, with https://github.com/Kong/kong/pull/4424 merged in, Kong 1.2 comes with support for sending HTTPS redirect out of the box in Kong.


Add tasks description and information about the project

Suggestion
I suggest adding detailed descriptions of the project's tasks provided by ALX, either in a separate Markdown file or within the existing README.md. I see this addition will enhance the clarity of the tasks completed within this repository, helps viewers in understanding the purpose and scope of each task and recognizing the contributions of team members more clearly.
Proposed Structure
Table of Contents

Task 1: Name (Contributor Name)
Task 2: Name (Contributor Name)
Task 3: Name (Contributor Name)

Task 1: Name (Contributor Name)
Detailed description of Task 1 provided by ALX.
Task 2: Name (Contributor Name)
Detailed description of Task 2 provided by ALX.
Task 3: Name (Contributor Name)
Detailed description of Task 3 provided by ALX.

I completely agree with your suggestion. Additionally, we could reference the issues and To-Do list for each task or feature. Let's focus on completing the mandatory tasks first to save time. After that, we can update the README.md file, as it currently contains incorrect details about our project and file structure. Depending on the size of the updated README, we can decide whether to include the task descriptions in the same file or in a new Markdown file.

[ ] Complete mandatory tasks
[ ] Update README file
[ ] Add tasks detailed descriptions

We have to update the README file too.

Add a link to the task details file.
Update the README file to fill the template with our project details.


fswatch: 1.11.2 -> 1.11.3

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/fswatch/versions.
These checks were done:

built on NixOS
ran ‘/nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3/bin/fswatch -h’ got 0 exit code
ran ‘/nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3/bin/fswatch --help’ got 0 exit code
found 1.11.3 with grep in /nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3
directory tree listing: https://gist.github.com/cc22e26348bfd98159c6519a470d3bdb

cc @pSub for review

Success on x86_64-linux (full log)
Attempted: fswatch
Partial log (click to expand)
make[1]: Leaving directory '/build/source'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3
shrinking /nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3/bin/fswatch
shrinking /nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3/lib/libfswatch.so.9.1.0
gzipping man pages under /nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3/share/man/
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3/lib  /nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3/bin
patching script interpreter paths in /nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3
checking for references to /build in /nix/store/c05hlqp57zslb3imjx6m5dary3ak601d-fswatch-1.11.3...

Success on x86_64-darwin (full log)
Attempted: fswatch
Partial log (click to expand)
 /nix/store/5lkrw9dnsgy62qm1ampvww1c5n1pdm4b-coreutils-8.29/bin/mkdir -p '/nix/store/s4wzbfzk02jg0ar8jms1sjfbxkqc0wwg-fswatch-1.11.3/share/man/man7'
 /nix/store/5lkrw9dnsgy62qm1ampvww1c5n1pdm4b-coreutils-8.29/bin/install -c -m 644 man/fswatch.7 '/nix/store/s4wzbfzk02jg0ar8jms1sjfbxkqc0wwg-fswatch-1.11.3/share/man/man7'
make[2]: Leaving directory '/private/tmp/nix-build-fswatch-1.11.3.drv-0/source'
make[1]: Leaving directory '/private/tmp/nix-build-fswatch-1.11.3.drv-0/source'
post-installation fixup
gzipping man pages under /nix/store/s4wzbfzk02jg0ar8jms1sjfbxkqc0wwg-fswatch-1.11.3/share/man/
strip is /nix/store/kdff2gim6417493yha769kh00n63lnrw-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/s4wzbfzk02jg0ar8jms1sjfbxkqc0wwg-fswatch-1.11.3/lib  /nix/store/s4wzbfzk02jg0ar8jms1sjfbxkqc0wwg-fswatch-1.11.3/bin
patching script interpreter paths in /nix/store/s4wzbfzk02jg0ar8jms1sjfbxkqc0wwg-fswatch-1.11.3
/nix/store/s4wzbfzk02jg0ar8jms1sjfbxkqc0wwg-fswatch-1.11.3

Success on aarch64-linux (full log)
Attempted: fswatch
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/r8axpvhxsc1wrvqlzfwyyziq45zwv7wd-fswatch-1.11.3
shrinking /nix/store/r8axpvhxsc1wrvqlzfwyyziq45zwv7wd-fswatch-1.11.3/bin/fswatch
shrinking /nix/store/r8axpvhxsc1wrvqlzfwyyziq45zwv7wd-fswatch-1.11.3/lib/libfswatch.so.9.1.0
gzipping man pages under /nix/store/r8axpvhxsc1wrvqlzfwyyziq45zwv7wd-fswatch-1.11.3/share/man/
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/r8axpvhxsc1wrvqlzfwyyziq45zwv7wd-fswatch-1.11.3/lib  /nix/store/r8axpvhxsc1wrvqlzfwyyziq45zwv7wd-fswatch-1.11.3/bin
patching script interpreter paths in /nix/store/r8axpvhxsc1wrvqlzfwyyziq45zwv7wd-fswatch-1.11.3
checking for references to /build in /nix/store/r8axpvhxsc1wrvqlzfwyyziq45zwv7wd-fswatch-1.11.3...
/nix/store/r8axpvhxsc1wrvqlzfwyyziq45zwv7wd-fswatch-1.11.3


Initiate site quality and SEO work on www.surveilr.com

@shanil-sasikumar @geovlazar please use the new site quality pattern to run all the tests on www.surveilr.com on each commit / push. Remember that because www.surveilr.com is a static Astro site, its contents will be available in dist by default and can be ingested by surveilr and site quality patterns can be run as part of the normal build process.
Please see https://github.com/lycheeverse/lychee for the Site Quality Explorer (SQE) pattern. We might want to use that to help with link checking as a capturable executable in case internal link checking withing surveilr does not work.

@shah-iq Please update the progress of your SEO-related work in this ticket.

Sharing an update on the on-page SEO issues we've addressed in Surveilr.

Keyword research and analysis - WIP.
Fixed broken internal images issue.
Added Google Search Console and GA4 property.
Added OG tags.
Added meta content to the blog pages.
Added meta content to the homepage.
Added schema to all pages
Collated a list of 404 pages and shared it with Temiye for him to address the URL breaks.
Removed references of ScrewFast.
Performed a full site audit to find and resolve errors and issues.

We are still working on remaining issues and on page content SEO. I’ll keep everyone updated as we progress.
cc: @shah

Just wanted to share a quick update on the SEO tasks for Opsfolio and Surveilr this week in addition to the content preparation:

Search Console audit, key metrics review and identifying issues with indexing and visibility (such as 404 errors, no-index exclusion, missing links, dummy links, alternate page with proper canonical tags, broken and outdated links etc). Identified issues were fixed.
Off-page activity, assessing backlinks, referring domains, and overall authority signals.
Webmaster review
Schema audit for accuracy and completeness of the structured data, with proper markup for rich snippets
Fixed the breadcrumb markup issue

cc: @shah

@shanil-sasikumar @geovlazar please use the new site quality pattern to run all the tests on www.surveilr.com on each commit / push. Remember that because www.surveilr.com is a static Astro site, its contents will be available in dist by default and can be ingested by surveilr and site quality patterns can be run as part of the normal build process.

@geovlazar @shanil-sasikumar please see https://github.com/lycheeverse/lychee for the Site Quality Explorer (SQE) pattern. We might want to use that to help with link checking as a capturable executable in case internal link checking withing surveilr does not work.

@geovlazar @arunqa @ajaykumaran please coordinate to fit this pattern in with the Qualityfolio service integrated into BLOaC as a global strategy. See https://github.com/strategy-coach/bloac/issues/2 and please discuss with me what you come up with.


Suggestion: Name Stealer / Changer

it would be nice to have this option in Fedoraware ( ͡° ͜ʖ ͡°)

There is already a name changer, but not a stealer.

You can use the name command in console

Yeah that will be awesome with the follow bots, damn no one will know where's the legit player

This is an open source cheat, I have no personal interest in adding more features for followbotters to use, not to mention name stealing is almost entirely useless now as you have to rejoin the server to steal a players name (2 minute vote cooldown upon joining), and the person you stole the name of can just call the vote (or anyone can call the vote using console).
Locking, if you want this as a feature, add it to your own build.


⚠ Processors has degraded performance

In e65cdf2, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 85 ms

Resolved: Processors performance has improved in 54cbc53.


Feature Request: Extract Subset move/remove subset

I would like to request the ability to move/remove files from the input folder of the Extract Subset function. That way I can choose to separate certain image subsets from the input folder. Lets say I wanted to separate monochrome images from the rest of them, the current state of the tool only allows me to copy that subset of images filtered by that tag to an output folder.
Thank you for your hard work!

Can you clarify on this? I tried my absolute best to not do ANY destructive operations. That's the reason why you always end up with a copy of the images when doing pretty much any kind of processing.
Extract subset one for example will make a COPY of the filtered images to a different folder while keeping the original intact.
Same for all other features, it always makes a copy even when processing the data like resizing or cropping.
As far as I remember (I haven't worked in the tools for 4 months) you can do some filtering in the extract subset page like:
"monochrome AND grayscale, !dog" to copy all images that have BOTH "monochrome" and "grayscale" but NOT "dog".
The reason why the tools aren't doing ANY type of destructive operations is because I personally lost 200 images from a dataset with 570 images in the early stages of the tools. And I don't want anyone else to experience that... I lost days of work.

Can you clarify on this? I tried my absolute best to not do ANY destructive operations. That's the reason why you always end up with a copy of the images when doing pretty much any kind of processing. Extract subset one for example will make a COPY of the filtered images to a different folder while keeping the original intact. Same for all other features, it always makes a copy even when processing the data like resizing or cropping.
As far as I remember (I haven't worked in the tools for 4 months) you can do some filtering in the extract subset page like: "monochrome AND grayscale, !dog" to copy all images that have BOTH "monochrome" and "grayscale" but NOT "dog".
The reason why the tools aren't doing ANY type of destructive operations is because I personally lost 200 images from a dataset with 570 images in the early stages of the tools. And I don't want anyone else to experience that... I lost days of work.
I just don't feel comfortable at all with deleting or removing files for the user.

I think that's understandable. Mainly I wanted to exclude particular tags from having to be handled as I needed to go and manually remove many images (I've probably deleted hundreds of thousands of images by now). I've been using the tool with some success to tag images and remove styles I didn't like by cutting the extracted images and pasting them into the source folder, then replacing the duplicate file names, and since they're automatically selected I can easily move them to the trash.
With that said, just being able to move extracted images would save some steps for handling things in bulk, but I understand if you don't want to cause any issues.


[BUG] URL Not Centered

Describe the problem
I didn't see anything about this but it looks like the URL is off center for me, either lining up w/the left or right edge of the notch depending on how I have the toolbar setup. I tried adding the flexible spaces in the tool bar but it just pushes it further to one side or the other. Even removing all the flexible space its still off (I attached the picture comparing it to safari and you can see how it is compared to the center line between the tabs). Is there a way to better center it?
Version
1.5.5
OS
MacOS 14.5
Firefox Version
128.0.2
Install Options
none
Colour Theme
none
Additional info

Please tick the boxes

[X] You are using a current version of the theme. (check the date associated with the version)
[X] You've checked that this issue hasn't already been raised

Hi @amcottre, thanks for raising this bug.
Something to note with the alignment are two items:

The URL tries to center based on the container it is given, which means between the padlock on the left, and the star on the right. I may look into removing the tracking protection icon container with the shield as an install option to make it cleaner. It could differ based on your extensions, but i see the appeal on it being centered all the time.
FYI, this is what I see when debugging the browser to check alignments.

It's a bit of a visual difference, as Safari omits the protocol i.e. https when looking at the URL. There is a hidden config item under browser.urlbar.trimHttps in about:config that you can change to true to display like the below. (i'm not a fan as it doesn't show the entire URL)

I'll rename this as a feature to add the option to better center it.
Please let me know if this doesn't fix the centering on your device

Appreciate the super quick reply. It look like it might be the positioning of the entire URL bar and not the URL itself. I did the 2nd option which I do prefer, but it's still shifted right. I think the URL bar is being centered between the right end of the close buttons space and the far right side instead of the far left/right sides. It seems like adding the sidebar button to the left is what mostly causes it. I took a rough "measurement" of the right side and put it over the left below


FIX: Disallow voting and hide actions on posts and comments for archived or closed topics

Disabled the voting buttons on posts and comments, and also returns an error properly if the frontend is bypassed.
https://meta.discourse.org/t/archiving-a-post-voting-topic-does-not-freeze-voting/253485/4

Thank you @CvX and @pmusaraj !

Any chance this could be "backported" for the stable 3.1 branch?


Migrate to container-based infraestructure

Laravel is currently running in the TravisCI legacy infraestructure. Migrating to container-based infraestructure has some interesting advantages. Also, It doesn't affect the tests in any negative way (tests are passing).
(More information)

Laravel is already running on container-based infra, see https://github.com/laravel/framework/blob/5.4/.travis.yml#L20 😄


Removed a lot of unnecesary string copies.

Replaced most of function signatures with string const& since we're
not modifying the input of these strings, and we don't need to create a
copy every time we call these functions.

Thanks!


ui/node Fix typo

Fix minor typo

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


fw-ectool: init at unstable-2022-12-03

Description of changes

new package
Things done

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)
[ ] Tested, as applicable:

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

[ ] 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
[x] 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.

The repo https://github.com/DHowett/framework-ec was last updated Dec 3, 2022 and on the creator's website he says

A fork of the Chromium project’s ectool ( DHowett/fw-ectool ), which implements the MEC LPC protocol. It only works on Linux. Discontinued.
An upstream pull request to Framework that adds that same support to their build of ectool

This sounds to me like the repo used in this package is discontinued and all the forked changes were merged upstream, but I'm not 100% sure.

The repo https://github.com/DHowett/framework-ec was last updated Dec 3, 2022 and on the creator's website he says

A fork of the Chromium project’s ectool ( DHowett/fw-ectool ), which implements the MEC LPC protocol. It only works on Linux. Discontinued.
An upstream pull request to Framework that adds that same support to their build of ectool

This sounds to me like the repo used in this package is discontinued and all the forked changes were merged upstream, but I'm not 100% sure.

https://github.com/DHowett/FrameworkHacksPkg/releases
There this now, which supports AMD frameworks too.


Fix property registrations for ItemsPresenter

What does the pull request do?

What is the current behavior?

What is the updated/expected behavior with this PR?

How was the solution implemented (if it's not obvious)?

Checklist

[ ] Added unit tests (if possible)?
[ ] Added XML documentation to any related classes?
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes

Obsoletions / Deprecations

Fixed issues

You can test this PR using the following package version. 11.0.999-cibuild0029586-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-all/nuget/v3/index.json) [PRBUILDID]


Update all dependencies

Except ActiveSupport, because 7.1 adds even more dependencies (including some that shadow Ruby 3.1 stdlib gems) and to be honest I'd rather we direct that effort towards #16190 over kicking that down the road even more by inheriting new features. Unlike other gems, we already configured Dependabot to skip 7.x anyway so this isn't a problem.

CI will be fixed by tomorrow morning's daily sorbet-runtime update: https://github.com/sorbet/sorbet/pull/7536


dc.BeginDialogAsync( ... ) "Value cannot be null.\nParameter name: options"

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
What package version of the SDK are you using.
Describe the bug
Give a clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Give a clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
It used to work before. I chanced something, which I don't remember what it was, and it stopped working giving me this error. I've run this in Visual Studio for Mac and in VS Code but it gives the same error in both.
[bug]

Sorry, I see most of what I wrote was lost. Re-creating this issue.


DTSConfig Files are not deployed

Either that, or placing them in the packages directory with a Content type of Content and Copy of Copy Always is not enough.

I figured it out. There's an additional call you can create:
<EMAIL_ADDRESS>As long as the config file is there and set as Content and Copy Always, it will deploy it.


Imageoptim appears to have frozen

I am building a website with a lot of images. For each image I am using imager to create several transforms. I am storing all imager generated files on S3, which works fine.
Recently I have decided to also upload the original images to S3. After changing all asset sources to S3 and manually uploading the files to the bucket my craftCms seems to go crazy.
Frontend is not responsive anymore and the control panel shows the process 'Optimizing images with optipng' running forever.
Screenshot: https://www.evernote.com/l/ACWeRHp1luFDu4oNGrpVZsk0gtLaIGral-EB/image.png
Any idea what is happening here?
Addition:
I have put the asset sources back to local storage and the site is accessible again. But the processes are still frozen. I am a little worried -.-
Addition 2:
I have deployed the database and code to a staging server and it immediately started to do those background tasks. What is causing this?

If you moved files from a local source to an external one, all asset transforms will be recreated the next time the transforms are requested. To Imager, these are now new files.
If you have post-optimizations enabled, what happends now is:
– The original asset is downloaded from S3.
– It's transformed and saved in the local imager path.
– It's uploaded to S3 (to make it instantly accessible)
– A task is created and triggered, which 1) optimizes the image, and 2) uploads the new, optimized file again to S3.
This will take alot of resources and time. As with all tasks in Craft, if a task runs too long and reaches the execution timeout in PHP, or any of the timeouts in the webserver (nginx has one, PHP-FPM has one or two), the task will get stuck (see https://craftcms.com/support/stuck-tasks).
So, everything you describe is completely natural. That's no help of course, but there's not really a simple solution to this, the underlying problem is that web servers isn't suitable for transforming huge amounts of images. I suggest incerasing the max_execution_timeout in PHP as much as possible, increase or disable the timeout settings in the webserver, and just work your way through all the pages on the site, until all the transforms are created.

@aelvan  Thank you very much for explaining all this. It certainly helped me understand what happens and how to get rid of those stuck tasks.
I have found another potential reason for all this:
The way I configured Imager it creates some sort of folder inside of a folder inside of a folder loop (screenshot). It seems plausible that this is what happened when my local server wasn't accessible.
Could you maybe have a look at my config and tell me what I am doing wrong here:
  'imagerSystemPath' => $_SERVER['DOCUMENT_ROOT'] . '/imager/',
  'imagerUrl' => 'https://s3-us-west-1.amazonaws.com/bucket-name/imager/',
  [...]
  'awsEnabled' => true,
  'awsAccessKey' => '*******',
  'awsSecretAccessKey' => '***********',
  'awsBucket' => 'bucket-name',
  'awsFolder' => 'imager/',

Huh, interesting. I'll have a look. Does it happen if you call the aws folder something other than imager?

I have tried to change the aws folder and it did what it was supposed to. Then I have removed the looping folders on S3 and they are gone now. Imager seems to work fine!
I am not sure what happened. I am sure it was my fault since I did not fully understand imager

It might actually be a bug in Imager that happends if a folder inside the bucket is used, and has the same name as the imager system path folder. I'll have a look at that. But as I understand it, you've got everything working now?

There is something weird happening now.
Screenshot.
Imager seems to create the folder in my bucket from the system root ?

That is so weird. What's your template code like, what are you passing in to Imager?

{% if image %}

	{% if not image.altText %}
		{% set altText = image.title %}
	{% else %}
		{% set altText = image.altText %}
	{% endif %}

	{# Settings #}
	{% set settings = {
		format: 'jpg',
		allowUpscale: false,
		mode: 'crop',
		jpegQuality: 80,
		position: image.focusPctX ~ '% ' ~ image.focusPctY ~ '%',
		interlace: true
	} %}

	{# Mobile: #}
	{% set mobileImages = craft.imager.transformImage(image,
		[
			{ width: 562, ratio: 1/2 },
			{ width: 1152, ratio: 8/5 },
			{ width: 1536, ratio: 64/75 },
			{ width: 1536, ratio: 1024/700 }
		], settings
	) %}

	{# Desktop: #}
	{% set desktopImages = craft.imager.transformImage(image,
		[
			{ width: 2160, ratio: 1440/900 },
			{ width: 3840, ratio: 2560/1250 }
		], settings
	) %}

	<picture>
		<source srcset="{{ desktopImages[1].url }}" media="(min-width: 1920px)">
		<source srcset="{{ desktopImages[0].url }}" media="(min-width: 1200px)">
		<source srcset="{{ mobileImages[3].url }}" media="(min-width: 1024px)">
		<source srcset="{{ mobileImages[2].url }}" media="(min-width: 768px)">
		<source srcset="{{ mobileImages[1].url }}" media="(min-width: 576px)">
		<img src="{{ mobileImages[0].url }}"
			alt="{{ altText }}"
			class="{{ class }} object-fit">
	</picture>

{% endif %}

@aelvan
I did a simple test:
First I changed the awsFolder to
'awsFolder' => 'tranforms',
Then I forced one image to reupload. After that I checked my S3 bucket:

2017-02-01 20:50:16     306482 tranforms/content/full-width/498/Hero_Cirro_Desktop_4b9e9c361ac6156ff035daf9442bd809.jpg
2017-02-01 20:50:16     197367 tranforms/content/full-width/498/Hero_Cirro_Desktop_79fc4f3a7ca1e3f31531ace0dd04ee10.jpg
2017-02-01 20:50:15      84187 tranforms/content/full-width/499/Hero_Cirro_Mobile_bade8f928c85b412a0bb9eb5855db509.jpg
2017-02-01 20:50:16      90012 tranforms/content/full-width/500/Hero_Cirro_Mobile_Landscape_4f804f9a5eaafffb5c6822e3c4e855d8.jpg
2017-02-01 20:50:16     194669 tranforms/content/full-width/501/Hero_Cirro_Tablet_c0731ad006930df48e5ba572950150e6.jpg
2017-02-01 20:50:16     209820 tranforms/content/full-width/502/Hero_Cirro_Tablet_Landscape_9dce6e2ff7f941f7e38f8ec8b743736e.jpg
2017-02-01 20:47:39     306482 tranforms/var/www/shared/public/imager/content/full-width/498/Hero_Cirro_Desktop_4b9e9c361ac6156ff035daf9442bd809.jpg
2017-02-01 20:47:39     197367 tranforms/var/www/shared/public/imager/content/full-width/498/Hero_Cirro_Desktop_79fc4f3a7ca1e3f31531ace0dd04ee10.jpg
2017-02-01 20:47:32      84187 tranforms/var/www/shared/public/imager/content/full-width/499/Hero_Cirro_Mobile_bade8f928c85b412a0bb9eb5855db509.jpg
2017-02-01 20:47:32      90012 tranforms/var/www/shared/public/imager/content/full-width/500/Hero_Cirro_Mobile_Landscape_4f804f9a5eaafffb5c6822e3c4e855d8.jpg
2017-02-01 20:47:33     194669 tranforms/var/www/shared/public/imager/content/full-width/501/Hero_Cirro_Tablet_c0731ad006930df48e5ba572950150e6.jpg
2017-02-01 20:47:35     209820 tranforms/var/www/shared/public/imager/content/full-width/502/Hero_Cirro_Tablet_Landscape_9dce6e2ff7f941f7e38f8ec8b743736e.jpg

As you can see it uploads every asset twice. Do you have any idea what causes this?
(I am now using aws CLI since the web interface and transmit seem to be very unreiable.)

SOLVED IT!
This is bad:
'imagerSystemPath' => $_SERVER['DOCUMENT_ROOT'] . '/imager/',
This is good:
'imagerSystemPath' => $_SERVER['DOCUMENT_ROOT'] . '/imager',
You might want to check the way you build the paths, so there are no whites paces and no trailing slashes.

That trailing slash should not be needed. I've tested loads of different setups now, and it works with or without trailing slash. I've also tested with original assets on S3 and local, with upload to S3 and not, and with and without various post-optimizing tools. All combinations work as they should.
This is either a matter of something being configured wrong, something weird in your server setup, or just a misunderstanding as to how Imager works.
I notice that between those to sets of images (the one with the local path added to it and the ones that appear to be correct), there's a 3 minute gap in the files timestamp. Are you running any post-optimizations on jpeg files? You mentioned optipng but that isn't being run in this case where the files are jpegs. If you turn off any such tools what happends then? Or could it be that you changed your configuration and ran the transforms twice? Did you ensure that the bucket was empty before running your last test?
Can you also try to output $_SERVER['DOCUMENT_ROOT'] and confirm that it actually points to the correct public root folder? Do you use some kind of symlinks somewhere in your paths?

One thing that might help here is that it only happens on the server. I tested it on an amazon-linux + apache and on an ubuntu + nginx server. Both create those weird folders. It worked fine on my local machine.
I am realising now that I haven't intalled jpegoptim on the server. I can't reproduce it anymore.
There for sure is some misconfiguration from my side. I will test more tomorrow. Getting late here.


Adjust special operations SetCreatedBy and SetTenant

The ~SpecialOperations/SetCreatedBy and ~SpecialOperations/SetTenant actions will change in next release. Instead of passing EntityKindId in json body EntitySet has to be part of the json body
Example
POST http://localhost:53422/api/Core/SpecialOperations/SetTenant HTTP/1.1
Content-Type: application/json
Content-Length: 151

{
  "EntitySet": "biz.dfch.CS.Appclusive.Core.OdataServices.Core.Node",
  "TenantId": "11111111-1111-1111-1111-111111111111",
  "EntityId": "1"
}

POST http://localhost:53422/api/Core/SpecialOperations/SetCreatedBy HTTP/1.1
Content-Type: application/json
Content-Length: 132

{
  "EntitySet": "biz.dfch.CS.Appclusive.Core.OdataServices.Core.Node",
  "CreatedById": "1",
  "EntityId": "1"
}

Please adjust UI accordingly so that it's ready for next release of Appclusive API.

[x] SetCreatedBy
[x] SetTenant

not tested yet

@ChrEggenberger server is now at newest release


Run highlighted statement in ACS RSS

Feature request:
Would it be difficult to make this extension see source selection and then use the run in ACS RSS option?
the plugin parameter would be [/SQL=<file>].  Its says file but you can put a quoted SQL statement there.
Plus, it would be optimal to have the [/AUTORUN=<0,1>] be a feature of this request.  Not of the main product feature though, IMO.
Thanks, Matt

Great idea Matt
fre. 7. okt. 2022 kl. 19.21 skrev Matt @.***>:

Feature request:
Would it be difficult to make this extension see source selection and then
use the run in ACS RSS option?
the plugin parameter would be [/SQL=]. Its says file but you can
put a quoted SQL statement there.
Plus, it would be optimal to have the [/AUTORUN=<0,1>] be a feature of
this request. Not of the main product feature though, IMO.
Thanks, Matt
—
Reply to this email directly, view it on GitHub
https://github.com/NielsLiisberg/vscode-ibm-i-run-sql-with-acs/issues/6,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVIPHTREYAJVB37YHK34ZLWCBLZRANCNFSM6AAAAAAQ7Y2HAQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


[Consensus] EpochManager as a single SoT for epoch information

The problem.
Current architecture is as follows:

NetworkTask keeps the current epoch metadata (epoch, validators) in its state: it's responsible for filtering the messages based on this epoch metadata.
NetworkTask updates the epoch metadata synchronously (right away) upon receiving EpochChange message that passes the proof verification.
EpochManager is held by ChainedBFTSMR: it is generating a new EventProcessor on demand when the SMR learns about the EpochChange event.

The metadata about the epoch is thus kept by both NetworkTask and EpochManager, which is suboptimal. One problem it creates is that there is a time window between  NetworkTask that has already migrated to the new epoch, but the SMR still keeping the  EventProcessor of the old epoch (until its select chooses to pick an EpochChange event from the corresponding receiver). As a result, today the messages of epoch n+1 pass the verification of NetworkTask (which is already in that epoch), and can arrive to EventProcessor of epoch n (which has not been replaced yet).
Proposal.
We can change the EpochManager to be the single source of truth for epoch metadata:

EpochManager is accessed both by NetworkTask and ChainedBftSMR via Arc<RwLock<EpochManager>>.
EpochManager is keeping Arc<RwLock<EpochState>>, which keeps both the information about the current epoch and the EventProcessor corresponding to that epoch.
Epoch transitioning is now executed in a synchronous manner: NetworkTask is directly invoking EpochManager::start_new_epoch().

I hope this architecture could be easier to reason about because there is going to be a single source of truth and a single serialization point for the epoch transitioning.

in general I'm not a fan of RwLock, if the goal here is to synchronize the epoch change between network task and main loop, we could send a one-shot channel and blocked until start_new_epoch finishes.

The goal is two-fold: 1) synchronize the epoch change, and 2) simplify the architecture via making sure that there is a single source of truth for the epoch information (i.e., EpochManager).
I don't think we should worry about the perf implications of a RwLock here: we're going to use the WriteLock only for reconfiguration, while all the other requests are going through a ReadLock, which cost is negligible in comparison to the other operations.

Conceptually this seems closer to the shared state model that we have talked about in the past.  As a minor detail, I would prefer to hide the RwLock inside of the EpochManager and just have Arc if we are heading down this path.

Resposting this from a discussion in https://github.com/libra/libra/pull/2402 so it doesn't get among the numerous commments in that PR:
I think the below is an accurate description of a current problem with the epoch/message queuing logic. It appears to me that the description at the beginning of this issues is either outdated(perhaps the lock around EpochInfo was added and this issue left open?), or inaccurate(it seems to me that it's the EpochManager that writes to EpochInfo, not NetworkTask, perhaps this was also changed since this issue was opened).
Consider the following:

A proposal message comes in over the network, at about the same time as we're changing the epoch.
NetworkTask reads the current epoch at https://github.com/libra/libra/blob/dae20021ab2cb806c1daf7a62c06c28ac60ea6f9/consensus/src/chained_bft/network.rs#L418
Since the epoch hasn't changed yet, it doesn't queue the message to different_epoch_tx.
EpochManager writes to the current epoch at https://github.com/libra/libra/blob/dae20021ab2cb806c1daf7a62c06c28ac60ea6f9/consensus/src/chained_bft/epoch_manager.rs#L214. called into from https://github.com/libra/libra/blob/dae20021ab2cb806c1daf7a62c06c28ac60ea6f9/consensus/src/chained_bft/chained_bft_smr.rs#L125
EpochManager clears the queue, removing the currently enqueued proposal messages at https://github.com/libra/libra/blob/dae20021ab2cb806c1daf7a62c06c28ac60ea6f9/consensus/src/chained_bft/chained_bft_smr.rs#L127
NetworkTask queues the proposal msg that came in at 1, yet it doesn't check the epoch again, so it's going to go to the queue for the current epoch at https://github.com/libra/libra/blob/dae20021ab2cb806c1daf7a62c06c28ac60ea6f9/consensus/src/chained_bft/network.rs#L432
Select wakes up, and the event-processor of the new epoch handles the message queued a 5, which is actually for the old epoch, at https://github.com/libra/libra/blob/dae20021ab2cb806c1daf7a62c06c28ac60ea6f9/consensus/src/chained_bft/chained_bft_smr.rs#L104

This condition is hard to reproduce, since sometimes, maybe most of the time, 5 will happen before 4, and the message will be first queued, and then cleared.
This could be fixed by simply holding the lock around EpochInfo for the duration of each call to one of the process_ methods in NetworkTask, which would prevent the epoch from changing in between the initial != self.epoch() check, and the actual queueing of the message to one of the channel, and that If the epoch changes after the message has been queued, it's not a problem since the queue will be cleared.
I do think that even if this were to be fixed like this, it's only a matter of time before another similar problems emerges, so I prefer to "larger" solution of https://github.com/libra/libra/pull/2402 which doesn't require accurate locking acrobatics from developers going forward.


Cognitive Services docstrings state that uploads can be used, but library doesn't actually support it

Expected result
The Cognitive Services docstrings state that uploads can be sent to the endpoint.
E.g.
https://github.com/Azure/azure-sdk-for-python/blob/decd1a4f9220146f0e6e263a65938cadb3d6c527/sdk/cognitiveservices/azure-cognitiveservices-vision-computervision/azure/cognitiveservices/vision/computervision/operations/_computer_vision_client_operations.py#L19-L26
Note this line:
Two input methods are supported -- (1) Uploading an image or (2) specifying an image URL.

Actual result
In reality, the code doesn't actually support uploads. E.g. for the analyze_image() function, only a publicly reachable url of an image can be used.
Next steps
Update the docstrings to reflect how the library's functions should be used in reality.

Worth noting that this still works:
image = open('./test.jpg', 'rb')
results = computervision_client.analyze_image_in_stream(image)

so this is indeed only docstrings issue.

Closing this issue, since we will not re-ship version of this pakage anymore (new versions are coming in a different package name), and the issue was documentation only, with behavior ok (thanks @suside for the snippet :)).


jigsaw init crashes if path exists

Warning: mkdir(): File exists in C:\Users\Simon\Documents\GitHub\jigsaw\vendor\illuminate\filesystem\Filesystem.php on line 337

If you run jigsaw init twice it will crash due to mkdir failing.

When you do jigsaw init, jigsaw tries to create new  directory. In your case jigsaw tried to dir with same name twice.
Try jigsaw init

Accidentally fixed by https://github.com/tightenco/jigsaw/commit/4247902341ff0c9416b3e22b5beac6d27f4f7c56 :)


Consolidate Example: simplify_udwf_expression.rs into advanced_udwf.rs #13842

Is your feature request related to a problem or challenge?

Part of https://github.com/apache/datafusion/issues/11172

The large number of small examples in DataFusion leads to multiple problems:

Unnecessarily large amounts of temporary disk space (each example binary takes 100+ MB)
Larger cargo t time (each binary must be linked / created)
Makes it harder to find the relevant examples

Thus I think the fewer examples we have the

faster our dev experience will be
easier it will be to find the relevant examples

Describe the solution you'd like

Consolidate the contents of the window function example simplify_udwf_expression
Into advanced_udwf.rs

Then update the readme page:

https://github.com/apache/datafusion/blob/main/datafusion-examples/README.md

Describe alternatives you've considered
No response
Additional context
I think this is a good first issue as the task is straightforward and doesn't require deep understanding of the DataFusion codebase

I'd like to take this if nobody is working on it

take


Create requirements

I started drafting cqs.csv so we can add the rationale for our classes and properties

I already filled the cqs.csv a bit a while back, does this agree with what you had in mind?

Yes. I think the rationale bit needs a little iteration. Let me have a look and come back to this issue with my questions

closing this one, as I raised questions in separate issues


fix AsyncSerialSampler import

The sampler import failed. Was the file name changed and the example was forgotten to be updated?

Codecov Report

Merging #172 into master will decrease coverage by 0.17%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #172      +/-   ##
==========================================
- Coverage   22.53%   22.35%   -0.18%
==========================================
  Files         128      128
  Lines        8002     8002
==========================================
- Hits         1803     1789      -14
- Misses       6199     6213      +14

Flag
Coverage Δ

#unittests
22.35% <ø> (-0.18%)
:arrow_down:

Impacted Files
Coverage Δ

rlpyt/utils/buffer.py
50.00% <0.00%> (-10.00%)
:arrow_down:

rlpyt/runners/minibatch_rl.py
42.78% <0.00%> (-1.00%)
:arrow_down:

Continue to review full report at Codecov.

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

OK this looks good!  Could you please make the same change to spaces/gym_space_schema.py?  And then I'll merge.  :)

I have done that. I have also found another wrong async sampler import

Thanks for that!!


Improve support for Move doc comments

Motivation
Annoying to write doc strings
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Ran the extension locally

side note: can you guys switch to Prettier or move all formatting to ESLint? tsfmt is pretty rare

Ping on this PR. @awelc is this correctly routed to you?

Ping on this PR. @awelc is this correctly routed to you?

I am sorry I missed it. It's related to VSCode extension which is why it was routed to me I suppose, though my main contributions there are on the language server (Rust) side.
Still, it seems like I am now the owner/maintainer here unless @vgao1996 wants to (re)claim the title :-)


Nightly unavailable on FreeBSD: clippy, rustfmt and rls

Apologies if this isn't the correct place to post this issue....
I haven't been able to update nightly on FreeBSD for a while due to the unavailability of rustfmt, clippy and rls: it'd be awesome if miri built, as well. :-) It's been about two months since the last successful update. I'm not sure if some automated process somewhere needs a nudge? Thanks!

Same for Windows

Nightly makes no guarantees about all the components or indeed architectures being available in any given nightly release.  If you're having problems with particular platforms or components, then looking to see if those component/platform teams could use help is the best thing you can do.  There's nothing rustup itself can do to make it more likely that these components are available nightly-to-nightly.  Sorry.

The problem seems to exist in Rust v1.37 on FreeBSD and NetBSD. Should I open new issue?

vagrant@freebsd:~ % rustup default 1.36.0
info: using existing install for '1.36.0-x86_64-unknown-freebsd'
info: default toolchain set to '1.36.0-x86_64-unknown-freebsd'

  1.36.0-x86_64-unknown-freebsd unchanged - rustc 1.36.0 (a53f9df32 2019-07-03)

vagrant@freebsd:~ % rustup component list | grep rls
rls-x86_64-unknown-freebsd

vagrant@freebsd:~ % rustup default 1.37.0
info: using existing install for '1.37.0-x86_64-unknown-freebsd'
info: default toolchain set to '1.37.0-x86_64-unknown-freebsd'

  1.37.0-x86_64-unknown-freebsd unchanged - rustc 1.37.0 (eae3437df 2019-08-13)

vagrant@freebsd:~ % rustup component list | grep rls
vagrant@freebsd:~ %

@iquiw If you want to open an issue on rust not here on rustup then sure.  This kind of component issue is not rustup's domain of concern since those platforms are not tier one and thus there's no guarantee they'll be available anyway.

@kinnison OK, thanks.
I have another problem about rustup itself. Its latest version is still 1.11.0 on NetBSD. I will open a new issue.

For the record, the original issue seems already reported.
https://github.com/rust-lang/rust/issues/62558


Remove misleading mention of composing env variables that only works via .env files

Update: See problem in https://github.com/prisma/docs/issues/2835#issuecomment-1026293087
Discussed in https://github.com/prisma/prisma/discussions/11453

Originally posted by yannickgloster January 27, 2022
Following prisma/prisma#1673, I converted the SSL Certificate that I needed from here Azure Database for MySQL into base64 to store it in as an environment variable that I can then load in into the tmp folder on the serverless function.
I do this when I create my prisma client:
/lib/prisma.js
import { PrismaClient } from "@prisma/client";

const fs = require("fs");
const path = "/tmp";

try {
  if (fs.existsSync(`${path}/BaltimoreCyberTrustRoot.crt.pem`)) {
    // do nothing
  } else {
    // creates crt.pem file from ENV

    fs.mkdirSync(path, { recursive: true });

    fs.writeFileSync(
      `${path}/BaltimoreCyberTrustRoot.crt.pem`,
      Buffer.from(process.env.CRT_PEM, "base64").toString("ascii")
    );
  }
} catch (err) {
  console.error(err);
}

const prisma = global.prisma || new PrismaClient();

if (process.env.NODE_ENV === "development") global.prisma = prisma;

export default prisma;

Locally this works as expected, and when I check on the API endpoint, the file exists correctly
import fs from "fs";

export default async function handler(req, res) {
  const files = fs.readFileSync(`/tmp/BaltimoreCyberTrustRoot.crt.pem`);

  res.status(200).json({ files: files.toString() });
}

My environment variables look like this:
SSL_CERT_PATH=/tmp/BaltimoreCyberTrustRoot.crt.pem
DATABASE_URL=mysql://user:pass@lserverip:3306/registration?sslcert=${SSL_CERT_PATH}&connect_timeout=300
CRT_PEM=longbase64string

I'm able to successfully connect to the DB when I use those variables locally, but when deployed I get the following error when I go to make a request to the DB.
2022-01-27T23:22:08.847Z	c63d91bb-ae49-40c3-95dd-c20a224d3f4d	ERROR	PrismaClientInitializationError: Can't reach database server at `IP OF SERVER`:`3306`
Please make sure your database server is running at `IP OF SERVER`:`3306`.
    at cb (/var/task/node_modules/@prisma/client/runtime/index.js:38697:17)
    at async handler (/var/task/.next/server/pages/api/tournaments.js:60:25)
    at async Object.apiResolver (/var/task/node_modules/next/dist/server/api-utils.js:102:9)
    at async NextNodeServer.handleApiRequest (/var/task/node_modules/next/dist/server/base-server.js:1076:9)
    at async Object.fn (/var/task/node_modules/next/dist/server/base-server.js:963:37)
    at async Router.execute (/var/task/node_modules/next/dist/server/router.js:222:32)
    at async NextNodeServer.run (/var/task/node_modules/next/dist/server/base-server.js:1103:29)
    at async NextNodeServer.handleRequest (/var/task/node_modules/next/dist/server/base-server.js:319:20)
    at async Server.<anonymous> (/var/task/___next_launcher.js:32:9) {
  clientVersion: '3.8.1',
  errorCode: undefined
}
2022-01-27T23:22:08.847Z	c63d91bb-ae49-40c3-95dd-c20a224d3f4d	ERROR	PrismaClientInitializationError: Can't reach database server at `IP OF SERVER`:`3306`
Please make sure your database server is running at `IP OF SERVER`:`3306`.
    at cb (/var/task/node_modules/@prisma/client/runtime/index.js:38697:17)
    at async handler (/var/task/.next/server/pages/api/tournaments.js:60:25)
    at async Object.apiResolver (/var/task/node_modules/next/dist/server/api-utils.js:102:9)
    at async NextNodeServer.handleApiRequest (/var/task/node_modules/next/dist/server/base-server.js:1076:9)
    at async Object.fn (/var/task/node_modules/next/dist/server/base-server.js:963:37)
    at async Router.execute (/var/task/node_modules/next/dist/server/router.js:222:32)
    at async NextNodeServer.run (/var/task/node_modules/next/dist/server/base-server.js:1103:29)
    at async NextNodeServer.handleRequest (/var/task/node_modules/next/dist/server/base-server.js:319:20)
    at async Server.<anonymous> (/var/task/___next_launcher.js:32:9) {
  clientVersion: '3.8.1',
  errorCode: undefined
}
RequestId: c63d91bb-ae49-40c3-95dd-c20a224d3f4d Error: Runtime exited with error: exit status 1
Runtime.ExitError

If I remove the SSL information from my DB connection string, I get an error stating that I need to provide SSL information to continue.
Server error: `ERROR 28000 (9002): SSL connection is required. Please specify SSL options and retry.\u0000'
Is there something I'm doing wrong here?
Thanks in advance
The reason I'm moving this to an issue is that due to the nature error, I believe this may be a bug.

I just found this thread and I am so confused. How am I su

I set the composed environment variables following what was written in the docs: https://www.prisma.io/docs/concepts/components/prisma-schema#accessing-environment-variables-from-the-schema
And they were uploaded to vercel using their UI that was documented here: https://vercel.com/docs/concepts/projects/environment-variables

so how am I supposed to set the env for vercel?  I found this thread but still lost on what to do instead

Depends on what you want to to.
If you want to set a static env var: Use the Vercel instructions at the second link.
If you want to compose a new env var value out of other bits and pieces you have available: Use an .env file that just composes things together, use the first link.

I tried setting it static in Vercel UI. But I get: ENOENT: no such file or directory, open '/var/task/schema.prisma' undefined on my data in deployment. And my data obv undefined too.
Since it works locally, my first thought was something was wrong with my variant variable and this thread is the only thing i stumbled upon

That is completely unrelated to the env var problem and is probably related to the bundler you are using or something like that. Please open a new bug report issues in prisma/prisma about this if you can reproduce this. Thanks.

https://www.prisma.io/docs/guides/development-environment/environment-variables#expanding-variables
Clearly state

Variables stored in .env files can be expanded using the format specified by dotenv-expand.

But https://www.prisma.io/docs/concepts/components/prisma-schema#accessing-environment-variables-from-the-schema

In version 2.7.0 and later, you can expand variables using the format specified by dotenv-expand. This is useful when dealing with PaaS or similar products. such as Heroku):

TODO: Could be improved, the fact that it only work with the .env file is implicit

I created a PR for the misleading text at https://github.com/prisma/docs/pull/4189

The misleading text was removed in https://github.com/prisma/docs/pull/4189
from https://www.prisma.io/docs/concepts/components/prisma-schema#accessing-environment-variables-from-the-schema


[gh-511] add ripemd-160 support for hashs.

Resolves #511 and closes #482.

This PR is ready for review.

Need to rebase and regenerate the genesis.

Regenerated.


fix NPE for rspec reports & added extra check to fail the build of no…

… tests are run

Codecov Report

Merging #76 into master will decrease coverage by -0.34%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##             master   #76      +/-   ##
=========================================
- Coverage     71.33%   71%   -0.34%
- Complexity        0   188     +188
=========================================
  Files            26    26
  Lines           635   638       +3
  Branches         89    77      -12
=========================================
  Hits            453   453
- Misses          149   152       +3
  Partials         33    33

Impacted Files
Coverage Δ
Complexity Δ

...iu/reporting/junit/builder/JUnitReportBuilder.java
41.25% <ø> (-1.61%)
8 <ø> (+8)

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 a7ca4e0...cd4970a. Read the comment docs.


[BUG] Field.IsReadOnly does not work properly on lookup attributes

Bug Report
Issues should only be created for items related to covered functionality.
Not covered functionality, feature requests, and questions should use the Feature Request or Question templates.
EasyRepro Version

[ ] Microsoft Dynamics 365 Online Version 8.2 (8.2.x) (DB 8.2.x) online
[ ] Microsoft Dynamics 365 Online Version 9.0 (9.0.x) (DB 9.0.x) online
[ ] Microsoft Dynamics 365 Online Version 9.0.2 (9.0.2) (DB 9.0.2) online
[X] Microsoft Dynamics 365 Online Version 9.1 (9.1.x) (DB 9.1.x) online

UCI or Classic Web

[X] UCI (XrmApp)
[ ] Classic Web (XrmBrowser)

Online or On Premise

[X] Online
[ ] On Premise

Browser

[X] Chrome
[ ] Firefox
[ ] IE
[ ] Edge

Describe the bug
Some attributes should become (non-)mandatory/readonly/writeable depending of another field.
After clearing the initiating field all of them should switch back to their previous state.
Our UI test should check both situations but the Field.IsReadOnly property always returns false.
The form is displaying the expected state correctly.
Special formatting / display
none
Code to reproduce
            //Set ProductCode and check if Business Unit and Operating Unit were locked
            this.SetLookupValue(Metadata.Lead.ProductCode, "1A Ammonia");
            //wraps App.Entity.SetValue(new LookupItem ...

            this.ClearFocus();
            App.ThinkTime(2000);

            IsFieldReadOnly(Metadata.Lead.BusinessUnit, true); // does not work properly
            IsFieldReadOnly(Metadata.Lead.OperatingUnit, true); // does not work properly

...

        public void IsFieldReadOnly(string attributeName, bool expectedValue)
        {
            this.TestContext.WriteLine("IsFieldReadOnly: {0}", attributeName);
            Field field = this.App.Entity.GetField(attributeName);

            if (expectedValue)
            {
                Assert.IsTrue(field.IsReadOnly);
            }
            else
            {
                Assert.IsFalse(field.IsReadOnly);
            }
        }

Expected behavior
Field.IsReadOnly (also IsRequired and IsVisible) should return the current state that is displayed on the form.
Screenshots
Previous state

After setting "Product Code"

Result of Assert

Additional context
In this case it occurs on lookup fields only. The depending field is the "Product Code", that should lock both fields above if set.

In another case a lookup is initially readonly. The first request of Field.IsReadOnly works fine. After switching to writeable and back to readonly Field.IsReadOnly does not return the correct state for the lookup. All other fields that are not of type lookup are working fine.


"engines" is not defined in package.json

Defining this allows older version of Node to not download and accept new versions of the lib. In reality, the major 2 release should have defined this, as it targets 4.x and above directly.
https://docs.npmjs.com/files/package.json#engines
I am not totally sure what a good retroactive solution to this would be, but still... something to think about.

I am not worried about the resolution of renaming / bumping versions as they are technically compatible with what they are relative to support. So adding these flags will just make it safer from hurting one's self. So yes 2.0 should work with node >= 4.X  and 1.X should be >= 0.10.X . Feel free to PR.

The issue here is that you know 2.0 supports Node 4.x, but NPM doesn't know that, and it will install the new version on old Node anyway. So if I am using Node 0.12 and run npm install gulp-sourcemaps, it will install the latest 2.x version. With engines, it will know better and pull down the latest 1.x instead.
A problem with doing this now is that even if engines is included in the next release (2.1.2), NPM will still think 2.1.1 is fine and install it.

Ok, so what is your resolution? I don't see worrying about the past versions being that big of a deal.  Make a PR and we can move forward in the right direction.
So are you suggesting bumping versions to 2.2 and 1.9? Is there a dilemma that there is not more version space where 1.X would ideally be bumped to 2, and 2 to 3?
I am trying to figure out why were dwelling on the issue here and not just issuing a PR.

master:
https://github.com/floridoo/gulp-sourcemaps/commit/ec9b51d0bb88746e16f85479f12f8cfbd7ed159a
1.X:
https://github.com/floridoo/gulp-sourcemaps/commit/02908271ef2e9c04c2a322f9d629a5264f88c794


Incorrect description in the navigator for connections with an SSH profile

Description
The decription in the navigator that shows the host for the connection is incorrect after restart
DBeaver Version
24.3.0
Operating System
Any
Database and driver
Any
Steps to reproduce

Open connection settings or start creating a new connection
On SSH tab select any profile with a remote host
Save th connection
Check that remote host is correctly shown in the navigator
Restart DBeaver
Check connection in the navigator again

Expected: The host is the same in the navigator
Actual: Host is replaced with localhost from the Main tab of the settings. It will change to correct again only after opening settings, switching to SSH tab and saving.
Additional context
Correct SSH credentials are still used, only the discription in the navigator is incorrect

verified


Enhancement: Adding a point from a geocode adds Name, too

The ability to add a point to a dataset directly from a search box geocode is groovy. It would be more groovy if it also added the placename to the Name field.

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


make: Add ineffassign as a part of precheck

Fixes #3609
Signed-off-by: Michal Rostecki<EMAIL_ADDRESS>

This change is

^ Same for the PrefixString() bug, that should go into 1.1 as well.

test-me-please

@aanm @joestringer PTAL
I added a wrapper script which ignores an error if a line contains // ineffassign: ignore comment.

Looks like the build failure is relevant, the new dependency also needs to be added to the vagrant files for the tests:
08:43:53     runtime: contrib/scripts/check-ineffassign.sh: line 6: ineffassign: command not found
08:43:53     runtime: Makefile:212: recipe for target 'ineffassign' failed
08:43:53     runtime: make: *** [ineffassign] Error 1
08:43:53 The SSH command responded with a non-zero exit status. Vagrant
08:43:53 assumes that this means the command failed. The output for this command
08:43:53 should be in the log above. Please read the output to determine what
08:43:53 went wrong.
08:43:53
08:43:53         ===================== ERROR - VM PROVISION FAILED =====================
08:43:53
08:43:53         Unable to provision and start VM "runtime": exit status 1", vm, err
08:43:53
08:43:53         =======================================================================

@joestringer @raybejjani
#4501
#4502

I did a rebase, but we also need ineffassign in Vagrant box https://github.com/cilium/packer-ci-build/pull/67

test-me-please

test-me-please

Weird, we don't seem to have ineffassign in the CI?
09:51:40 contrib/scripts/check-ineffassign.sh
09:51:40 ++ git rev-parse --show-toplevel
09:51:40 + TOPDIR=/go/src/github.com/cilium/cilium
09:51:40 + ineffassign /go/src/github.com/cilium/cilium
09:51:40 contrib/scripts/check-ineffassign.sh: line 7: ineffassign: command not found

@joestringer That's indeed weird. Do we have any CI tests running outside Vagrant? Vagrant box for sure has ineffassign.
Dev VM:
 mrostecki   ineffassign  …  github.com  cilium  cilium  vagrant ssh
[...]
vagrant@runtime1:~/go/src/github.com/cilium/cilium$ which ineffassign
/home/vagrant/go/bin/ineffassign

Ginkgo VM:
 mrostecki   ineffassign  …  cilium  cilium  test  3  vagrant ssh runtime
[...]
vagrant@runtime:~$ which ineffassign
/home/vagrant/go/bin/ineffassign

@mrostecki Good point, it's in the precheck stage:
https://jenkins.cilium.io/view/PR/job/Cilium-PR-Ginkgo-Tests-Validated/5732/flowGraphTable/
Maybe we need to put this somewhere else in the Jenkins scripts or something. @eloycoto / @ianvernon ?

We need to wait for https://github.com/cilium/cilium/pull/5245 and new cilium-builder image

test-me-please

test-me-please

Seems unrelated
11:16:11 [K8s-1.8] • Failure in Spec Setup (BeforeEach) [434.414 seconds]
11:16:11 [K8s-1.8] K8sKafkaPolicyTest
11:16:11 [K8s-1.8] /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:344
11:16:11 [K8s-1.8]   Kafka Policy Tests
11:16:11 [K8s-1.8]   /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:344
11:16:11 [K8s-1.8]     KafkaPolicies [BeforeEach]
11:16:11 [K8s-1.8]     /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:376
11:16:11 [K8s-1.8]
11:16:11 [K8s-1.8]     Kafka Pods are not ready after timeout
11:16:11 [K8s-1.8]     Expected
11:16:11 [K8s-1.8]         <*errors.errorString | 0xc420676120>: {
11:16:11 [K8s-1.8]             s: "Timeout reached: timed out waiting for pods with filter -l zgroup=kafkaTestApp to be ready",
11:16:11 [K8s-1.8]         }
11:16:11 [K8s-1.8]     to be nil
11:16:11 [K8s-1.8]
11:16:11 [K8s-1.8]     /home/jenkins/workspace/Cilium-PR-Ginkgo-Tests-Validated/src/github.com/cilium/cilium/test/k8sT/KafkaPolicies.go:133

test-me-please


Deployment editor no longer opens in Papyrus 4.6

Issue and tracking information
The deployment editor does not open in the latest Papyrus version.
Steps to reproduce:

Install Papyrus 4.6
Open BasicPubSub model and try to open the deployment plan.

Papyrus bug#:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=561870
Developer's time Estimated effort to fix (hours):
Developer's Actual time spent on fix (hours)
Issue reporter to provide a detailed description of the issue in the space below

This issue is fixed and tested using Papyrus 4.8. We should be able to move to a newer version if required.

Do we think this issue can be closed now?

Yes, I will close this issue.


If my last selected private registry is deactivated, it still shows up in the drop down as a selected option when it's not listed in the drop down list.

Version v0.13.0
If I use my private registry (test.io) to create a container and then go to deactivate the private registry, the 'Add Container' page will still show (test.io) as a selected item, when the item doesn't exist in my drop down.
Steps to Reproduce:

Create a private registry
Go to Add Container and set the private registry to the newly created one.
Go to the private registry page and deactivate the private registry.
Go back to the 'Add Container' page

Result: The dropdown for image is still selecting your private registry even though it's not an option.
Expected Result: The dropdown should reset (probably to DockerHub).
In my image, the test.io private registry is not in the dropdown anymore because it's inactive.

There is no longer a registry or credential picker in the UI as of rancherio/ui#152.

v0.20.1
Verified fixed


Create crypto providers from JWK and other refactorings

Supports the ability to create .NET crypto providers from JWKs, converts the Keys' enumerations to structures (other KV libraries will receive similar treatment), and contains related refactorings.
This also starts building tests for net47 because ECParameters and friends (basically, everything EC* except ECDsa) are in netstandard2.0 but not in net461. We decided, given the usage numbers for .NET Framework versions, it's more acceptable to fail if people use EC-related methods rather than multi-target, which we don't do for any other libraries in track 2. Care was taken to avoid TypeLoadExceptions, which is why we target net461, net47, and netcoreapp2.1 for Keys.Tests.
Also adds me as a code owner for sdk/keyvault.

I've fixed the failure, which is because macOS doesn't support P-256K using OID <IP_ADDRESS>.10.

/azp run net - keyvault - ci


I guess we're making a semi-blessed JS TOML parser for the website!

Following up on this:

@workingjubilee Yes please! haha I hadn't figured out how to actually do that yet, but I found this site: https://toolkit.site/format.html so I knew it was possible.
@mojombo had a good point that some types aren't directly translatable, like native datetimes. What do we do in those cases? Maybe just output a string version of the datetime? Or replace the content with a comment (even though it isn't technically legal in JSON)? Likewise do you take a datetime string in JSON and try and covert it to native datetime for TOML?

Originally posted by @cannikin in https://github.com/toml-lang/toml.io/issues/1#issuecomment-526330420
We can do "lossy data, but structural match" or "lossy structure, but data match" translation across JSON : TOML, the data-lossless one involving type annotations embedded in the JSON structure. By default, we can favor the first, cleanest translation (where JSON and TOML are 1 to 1), but when the translation would involve loss of type data like that, we can display an error state or perhaps a "warning state" I guess and point the user to an option to enable alternative translations. After all, we already have to intelligently handle JSON literals ("Uh, Ma'am, this is a hash table").
I think recognizing JSON strings that are exact matches for the subsets of the RFC3339 format that TOML supports and casting them to TOML datetimes is a sane default, because it's lossless as a result, but not if they are off by even a single whitespace(!), and that a similar logic of Maximal Strictness would serve well on all type casts. No guessing and no magic, really, just return to user and comment on the results, maybe offer choices if we can. And I think that's going to be easiest.
Edited: I'm so sorry, I was mid-way through my coffee when I first posted this.

Or... We can drop that section. 🙃
I'm ambivalent to whatever we do here.

haha That's a possibility too. The reason I added it was when I start comping I wanted to include the TOML vs JSON vs YAML examples. I found a converter (first or second result in google for "toml converter") and I thought "the first result should be toml.io, not some random site". But that was probably my vanity speaking, not the pragmatic/lazy programmer speaking. ;)

I wouldn't mind dropping that section. If we're pitching a human-readable, human-writable format (and we are), then letting people see what they can do, and letting it tumble around in their head for a bit, is what's important. The rest of the site can point them to the latest spec, solid implementations, and maybe live demos.

Aw, OK! It is definitely more of a nice-to-have.
Though, of nice-to-haves, maybe "an automatic TOML validator" would come first, which is really just folding instaparse.mojombo.com into toml.io.

Closing, since we've dropped that section. :)


doc K8s doc modify catalog and add helm doc 2.0

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Israel 1992 Start Date all soldiers POP located in Tel Aviv

All soldiers pops for Israel in 1992 start are located in Tel Aviv. Creating issue with only allowing serial creations of troops and losing brigades support faster due to localizing all causalities on a single POP pool.

Israel is one region (state). Soldiers are state pops, not province pops. This is if performance reasons.


internationalization produces local files

Tests related to internationalization produce temporary files in the local home directory, which are not deleted afterwards.

@ArneBinder has an idea how to solve the issue. Please implement and test it.

The first try to fix the issue was not succesful. Maybe this issue is related to https://github.com/freme-project/FREMECommon/issues/22


Symlink any /boot/Image* to /boot/vmlinuz

The jetson produces /boot/Image which wasn't caught by the previous mechanism
fixes #2461

tested manually, this tests dont' run on pr so merging


Run tempest test in serial mode

Did you try more than one run to ensure this is not just a chance?

Did you try more than one run to ensure this is not just a chance?

nope, will run it locally to test that.

lets retrigger the CI job as well

There have been 3 failed rebuilds on this PR. The problems seem to be unrelated to the change:

Invalid repository
Failure on terraform apply
time out while deploying kube-system-ingress

I tried locally as well. Several tests were failing, only one with 503 error, but also several failing due to timeouts trying to reach compute.openstack.svc.cluster.local which I think it's related to those 503s.
So, this is an improvement over the previous situation but it doesn't solve all problems.


Add argon2 password strategy + spec

I wanted to add argon2 strategy for a project I'm using.

Using ruby-argon2.
I'm still digging in, would love another set of eyes.
EDIT: See the contributing guide, fixing the spec.
EDIT 2: Done!

Not sure if this is due to my edit:
>> BUNDLE_GEMFILE=/Users/herbertjoseph/Webdev/open_source/clearance/gemfiles/rails50.gemfile bundle exec rake rake aborted! NoMethodError: undefined method last_comment' for #Rake::Application:0x007f8172dd15f8
/Users/herbertjoseph/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.5.0.beta1/lib/rspec/core/rake_task.rb:91:in define' /Users/herbertjoseph/.rvm/gems/ruby-2.3.0/gems/rspec-core-3.5.0.beta1/lib/rspec/core/rake_task.rb:71:in initialize'
/Users/herbertjoseph/Webdev/open_source/clearance/Rakefile:14:in new' /Users/herbertjoseph/Webdev/open_source/clearance/Rakefile:14:in <top (required)>'
/Users/herbertjoseph/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in eval' /Users/herbertjoseph/.rvm/gems/ruby-2.3.0/bin/ruby_executable_hooks:15:in `

Hello @Copywright. Thanks for preparing this. Argon2 has been on my list of things to investigate for Clearance 2.0, but I haven't had the time to do it. I was excited to see this come across.
I've given some feedback on the code, but ultimately I don't think I can accept this into clearance directly at the moment. There are a few reasons:

I don't want to add a dependency on argon2 while most users of the library are likely to be using bcrypt.

I prefer, at least for now, to ship a single password strategy that we recommend. We currently have some other password strategies in the repo, but they are deprecated.

I'd actually like to change the implementation of PW strategies for Clearance 2. Right now, they get mixed into your User object directly but I really don't want to to do that anymore if we can help it.

I like what you've done here, though. What I'd suggest is extracting the work you've done here into a gem, clearance-argon2, that depends on Clearance 1.x. Then you'll be able to use argon2 and we can monitor how it's working for people as we decide how to move forward with strategies in Clearance 2. It's possible that we'll pull this in for 2.0 in some form, but I'm just not sure yet.
If you need assistance in how you would go about setting up the stand-alone gem, you can take a peek at clearance-deprecated_password_strategies to see how we pulled out the earlier strategies. If you need more help, let me know.

@derekprior I understand, I'll do just that and make a gem abstraction


Update image ghcr.io/zoriya/kyoo_migrations to 016fa82

This PR contains the following updates:

Package
Update
Change

ghcr.io/zoriya/kyoo_migrations
digest
627bbb5 -> 016fa82

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Action chain test improvements

Fix exception error message
Add some additional asserts which make sure we are testing the right case and that the tests return expected error message

+1
Thanks!


DUPLO-25900 TF Doc: Add example usage for duplocloud_user_tenant_access resource

Overview
Changed Example File name for user tenant access
Summary of changes
changed example filename
This PR does the following:

...
...

Testing performed

[ ] Using unit tests
[ ✓] Manually, on my local system
[ ] Manually, on a remote test system

Describe any breaking changes

...

Task linked: DUPLO-25900 TF Doc: Add example usage for duplocloud_user_tenant_access resource


Allow to disable "static" using TM_STATIC macro

Not supported on all platforms/ports. Specifically the mpy_ld.py linker for MicroPython dynamic native modules. Fixes #75

Thank you for quick review and merge!


Refresh codebase for dfx 0.13.1

Simplifies the repository's configuration, CI, etc. by switching to MOPS.

Thank you @rvanasa!


Bundle products do not allow configurable products to be added

Describe the bug
It is in the latest version not possible to add configurable products to a configurable products.
I am not sure if this is a bug or intentional, but in my current shop nearly all products are configurable products, so not being able to add configurable products would make the bundle option unusable.
To Reproduce
Steps to reproduce the behavior:

Create new bundle product
Click on "Add product" in the "Group Products" section
The configurable products are not listed whatever the search query

Expected behavior
The configurable products should be able to be added
Additional context
I'm using version 2.1.1 but the issue is also present in the current Bagisto Demo

Please note that only simple products are eligible for addition to the configuration, bundle, and grouped product types.

Is this a feature which is going to be add in the future?