update to bevy 0.14

As far as I can tell this crate is going to have a hard time to upgrade to bevy 0.14.
When impl-ing WorldQuery we're currently relying on the fact that we get world acces in init_state and get_state to init/get the trait registry internally and get the relevant data. The API of WorldQuery changed to only ComponentInitializer or Components respectively.
I'm not seeing any easy way of resolving this, hence I wanted to open this issue for discussion here. Ideas are welcome. I'll try hacking around a bit now 🔧

Here's some thread I could trace a bit on discord. Let's try to establish a bit of transparency here:

WrongShoe
It's because systems can have active borrows on more than one query. To be clear I don't think this usage would cause UB, but we probably shouldn't violate our own safety constraints internally in the engine. Can you make get_state take Components instead of &World?
That's how I had it in my original PR

Victoron
I see. Looking at all get_state() impls in the engine, it either only accesses Components via component_id(), or doesn't use world at all, so it would be doable. Though since get_state() is a trait method on WorldQuery, I wonder if any user impls use more aspects of World?

Giooschi
bevy-trait-query appears to fetch a Resource with it

WrongShoe
I don't think this is safe. What if you transmute a trait query and have a ResMut<TraitImplRegistry> in the system?
That would have a mutable reference and a shared referece to the reource live at the same time.

Giooschi
Well, from the point of view of bevy-trait-query it gets a &World so it's perfectly safe to access that resource.

WrongShoe
It's ub, so our api's are incorrect.

Looks like they didn't change init_state, but still changed get_state.

I think you can just use the patched version here:
https://github.com/Azorlogh/bevy-trait-query/tree/bevy-0.14
It just doesn't make use of the state. I just ran the benchmarks again and here is the comparison with respect to bevy 0.13.
after bevy update:
All<> - 1 match         time:   [57.837 µs 57.853 µs 57.870 µs]
                        change: [-27.393% -27.221% -27.096%] (p = 0.00 < 0.05)
                        Performance has improved.

All<> - 2 matches       time:   [85.118 µs 85.131 µs 85.145 µs]
                        change: [-20.515% -20.122% -19.877%] (p = 0.00 < 0.05)
                        Performance has improved.

All<> - 1-2 matches     time:   [70.975 µs 70.988 µs 71.001 µs]
                        change: [-22.902% -22.789% -22.689%] (p = 0.00 < 0.05)
                        Performance has improved.

concrete - 1 match      time:   [8.4276 µs 8.4304 µs 8.4332 µs]
                        change: [+1.3473% +1.5102% +1.6452%] (p = 0.00 < 0.05)
                        Performance has regressed.

concrete - 2 matches    time:   [7.9414 µs 7.9477 µs 7.9600 µs]
                        change: [-10.657% -10.239% -9.9041%] (p = 0.00 < 0.05)
                        Performance has improved.

concrete - fragmented   time:   [1.3871 µs 1.3910 µs 1.3958 µs]
                        change: [-4.3640% -3.4317% -2.8527%] (p = 0.00 < 0.05)
                        Performance has improved.

One<> - fragmented      time:   [2.5235 ns 2.5237 ns 2.5240 ns]
                        change: [-14.045% -13.461% -12.906%] (p = 0.00 < 0.05)
                        Performance has improved.

All<> - fragmented      time:   [6.1596 µs 6.1926 µs 6.2526 µs]
                        change: [-2.2789% -1.7270% -1.1198%] (p = 0.00 < 0.05)
                        Performance has improved.

One<>                   time:   [32.187 µs 32.189 µs 32.192 µs]
                        change: [+13.082% +13.191% +13.298%] (p = 0.00 < 0.05)
                        Performance has regressed.

One<> - filtering       time:   [16.730 µs 16.740 µs 16.754 µs]
                        change: [+18.165% +18.335% +18.607%] (p = 0.00 < 0.05)
                        Performance has regressed.

Can you submit a PR for that fork? I'm not the maintainer, but it would be nice to have increased visibility.

AFAIK there are still unresolved issues since transmute won't work with this implementation on those queries and will actually panic (?). I'll add a test and some notes somewhere to showcase that. I'm not sure if we can prevent users from trying to transmute those queries in a good way other than through docs :/
But yeah, at least it's working somehow :)

Would it be possible to have an rc version with this change for crates that depend on bevy trait query?

Would it be possible to have an rc version with this change for crates that depend on bevy trait query, just so they can migrate to 0.14?

You can just add
[patch.crates-io]
bevy-trait-query = { git = "https://github.com/RobWalt/bevy-trait-query.git", branch = "bevy-0.14-partial-update" }

to your Cargo.toml until the PR is merged. Or is that no option for you?

That works for me. Thanks.

Would it be possible to have an rc version with this change for crates that depend on bevy trait query, just so they can migrate to 0.14?

You can just add
[patch.crates-io]
bevy-trait-query = { git = "https://github.com/RobWalt/bevy-trait-query.git", branch = "bevy-0.14-partial-update" }

to your Cargo.toml until the PR is merged. Or is that no option for you?

You can't use this if you're releasing your crate on crates.io. I would appreciate a RC release as well as I'd like to get my crate published.

I just released the new version of the crate! Thanks for staying patient. Please let me know if you find some rough edges in the new version or hit performance regressions!


fix module dependency

Purpose
Command hugo server fails with Error: module "github.com/wowchemy/wowchemy-hugo-modules/wowchemy/v5" not found; either add it as a Hugo Module or store it in "/Users/georgiana/code/revamped/tekkie.ro/themes".: module does not exist due to a rename.
Documentation
Use proper module includes to address the above issue.

The Go module name is ...wowchemy-hugo-modules. If you need support, consider asking on the Discord channel with a link to your repo.


fiv-loading-content problem with overflow-x scroll

Hello,
Congratulations to all involved for the excellent work!
I'm finding some problems with the component 'fiv-loading-content', in my app I have a box with overflow-x: scroll, the component left this box unusable ie the user can not drag the box anymore because the component is by above, I tried to put z-index in the component and box but without success.
I believe the component should not check horizontal events

Hi @paulovargatt ,
thank you for your feedback! :)
I'm not super happy with the implementation of the refresher right now. (It's also kind of buggy on ios). I've planned to change it up for version 1.0.0 to better match the api of the ion-refresher. Hopefully this will fix your problem too.
If you have an idea to improve the component feel free to submit a PR. For now you could share a repo with you implementation of the fiv-loading-content so that i can understand your problem better.
Cheers,
Gary

Ok @garygrossgarten ,
Sorry for the delay in responding.
repository by illustrating the problem

Hey @paulovargatt sorry for letting you wait so long.
I just sent you a PR for your test repo updating the @fivethree/coredependency to the latest release. I marked all the touch handlers for the pull down as passive. This should fix the problem but please test it out yourself and report here.
Cheers

thank you,
For my need (Android) worked well!
I still need to see it on IOS ...
Thanks for the work;)

Hello @garygrossgarten,
in tests in the browser the animation has the correct operation, except when scrolling on the page because the content rolls even with the active "pull" animation.
In tests on the android device, the animation seems very slow, perhaps because of the page scroll event happen as well.


Automated cherry pick of #5583: Fix data race in FQDN ruleSyncTracker

Cherry pick of #5583 on release-1.13.
#5583: Fix data race in FQDN ruleSyncTracker
For details on the cherry pick process, see the cherry pick requests page.

/skip-all

/skip-all

/skip-all


Security: Should use secure random number generation

This library should use crypto.randomBytes() instead of Math.random()
From MDN:

Note: Math.random() does not provide cryptographically secure random numbers. Do not use them for anything related to security.

Using Math.random allows this library to be used in the browser. There are plenty of other options available that use crypto.

Then in the browser it should use the browser crypto API:
> window.crypto.getRandomValues(new Uint8Array(32))
[99, 90, 133, 158, 86, 205, 60, 237, 180, 186, 145, 12, 228, 101, 94, 204, 38, 68, 194, 74, 143, 93, 150, 242, 4, 145, 33, 1, 163, 138, 215, 28]

(browser support)
If this library doesn't intend to be cryptographically secure, it should advertise that fact loudly in the readme like this:

WARNING: This library does not use a cryptographically sound RNG. Do not use this library to generate secure passwords or passphrases.

I bring this up because I've see this used for password generation, where its (obviously) unsafe.

I'd be fine with browser-friendly crypto or a giant warning. I don't need it to be secure, but I do need it to work in Node and browsers.


Add FAQ content to Kanso (New UI) doc

Purpose of this pull request
Add FAQ content to New UI doc

Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions, .clabot
[x] Update Content - Revisions, updating sections
[x] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Perfect, @kimsauce.

thank you for the quick review!


Formatting Transactional Email

I'm using the SparkPost plugin for wordpress and find the need to format transactional emails by replacing CR/LF with <br/>. Would it be possible to enhance the plugin to perform this simple task or can someone provide guidance on the creation of a wordpress filter to do it?
Right now I'm modifying line 96 in mailer.http.class.php to run the php command nl2br.
Thank you ...... Rick

Hey @interceptclients! I would suggest opening an issue in our wordpress plugin repo to get some eyes on this.

Thank you, SparkPost support suggested posting here.
Rick Barron
Chief Rain Dancer
513-201-7891
Schedule a Meeting with Me [http://schedulerick.com/]
On 10/26/2016 1:48:13 PM, Avi Goldman<EMAIL_ADDRESS>wrote:
Closed #155 [https://github.com/SparkPost/php-sparkpost/issues/155].
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub [https://github.com/SparkPost/php-sparkpost/issues/155#event-837444815], or mute the thread [https://github.com/notifications/unsubscribe-auth/AWA3vofcmiQDG7bYZ-gi7NeMj1QzN9kiks5q35JXgaJpZM4KhdEZ].

Sorry about the confusion.


Browse directive, how it should behave?

Hello to all.
I have successfully built Caddy with S3 proxy plugin. Working fine out of the box.
I am having issues to figure out how the browse directive should work.
Trying to curl to a "folder" curl localhost/combined-dragen/ but I'm getting error 500.
If I try to access a file I successfully get a response.
It is not critical for my use case but I wanted to understand it anyways.
Error message:
2021/10/11 15:47:52.365 ERROR   http.log.error  template: default_listing:5:26: executing "default_listing" at <.PageObj>: can't evaluate field PageObj in type caddys3proxy.PageObj       {"request": {"remote_addr": "<IP_ADDRESS>:39072", "proto": "HTTP/1.1", "method": "GET", "host": "localhost", "uri": "/combined-dragen/", "headers": {"User-Agent": ["curl/7.76.1"], "Accept": ["*/*"]}}, "duration": 0.037100034, "status": 500, "err_id": "fnstkc6nm", "err_trace": "caddy-s3-proxy.convertToCaddyError (errors.go:118)"}
2021/10/11 15:47:52.365 ERROR   http.log.access handled request {"request": {"remote_addr": "<IP_ADDRESS>:39072", "proto": "HTTP/1.1", "method": "GET", "host": "localhost", "uri": "/combined-dragen/", "headers": {"User-Agent": ["curl/7.76.1"], "Accept": ["*/*"]}}, "common_log": "<IP_ADDRESS> - - [11/Oct/2021:15:47:52 +0000] \"GET /combined-dragen/ HTTP/1.1\" 500 0", "user_id": "", "duration": 0.037100034, "size": 0, "status": 500, "resp_headers": {"Server": ["Caddy"]}}

This is my Caddyfile
{
        order s3proxy last
        debug
}
:80 {
        log
        s3proxy /* {
                region "eu-central-1"
                bucket "bucket-name"
                #index index.html
                browse
                force_path_style
        }
}

I'm having the same issue, how did you fix?


docs: Simplify React Native sidebar navigation

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on refactoring the sidebar structure in the sidebar.tsx file for a React Native application. It simplifies the sidebar by removing several sections and reorganizing links.
Detailed summary

Removed several sections including "Core", "Wallets", "Social API", "Pay", and "Blockchain API".
Added a new section for "Differences from React".
Renamed "TypeScript docs" to "React docs".
Updated "Full Reference" to "API Reference".

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#5800  👈 (View in Graphite)
main

How to use the Graphite Merge Queue
Add either label to this PR to merge it via the merge queue:

merge-queue - adds this PR to the back of the merge queue
hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.


evm:status displays all columns by default

Overview
rake evm:status has a lot of data to display.
Too much data causes the output to wrap, making the output hard to read.
The columns with duplicate values were collapsed and displayed as a summary below.
This feature was added in #17087
But some users are not expecting those columns to be displayed below, they want them all inline.
before:
Columns with duplicate values were collapsed and displayed below in a summary section
after:
All columns (with a value) are displayed in the table by default.
The condensed view is still available, but with a flag:
rake evm:status_full -- --collapse

https://bugzilla.redhat.com/show_bug.cgi?id=1651256
full output reference
rake evm:status_full

Checking EVM status...
 Region | Zone          | Server   | Status  |   PID |  SPID | Workers | Version | Started    | Heartbeat  | MB Usage | Roles
--------+---------------+----------+---------+-------+-------+---------+---------+------------+------------+----------+------------------------------------------------------------------------------
     10 | staging-01 wk | srvr-01* | started |  1503 |  1912 |      24 | <IP_ADDRESS> | 2018-11-14 | 2018-11-19 |      349 | automate:database_operations:smartstate:user_interface:web_services:websocket
     10 | staging-02    | srvr-02  | started |  1640 |  5030 |      13 | <IP_ADDRESS> | 2018-11-14 | 2018-11-19 |      348 | automate:ems_inventory:ems_operations:event:user_interface:web_services:websocket

* marks a master appliance

 Region | Zone          | Type                                      | Status  |   PID | SPID  | Server  | Queue                                           | Started    | Heartbeat  | MB Usage
--------+---------------+-------------------------------------------+---------+-------+-------+---------+-------------------------------------------------+------------+------------+----------
     10 | staging-01 wk | EmbeddedAnsible                           | started |       | 2195  | srvr-01 |                                                 | 2018-11-14 | 2018-11-19 |
     10 | staging-01 wk | EmbeddedAnsible::Automation::EventCatcher | started |  3538 | 3553  | srvr-01 | ems_10000000000004                              | 2018-11-14 | 2018-11-19 | 237/2048
     10 | staging-01 wk | EmbeddedAnsible::Automation::Refresh      | started | 31950 | 31982 | srvr-01 | ems_10000000000004                              | 2018-11-19 | 2018-11-19 | 216/2048
     10 | staging-01 wk | EmsMetricsProcessor                       | started |  2081 | 2115  | srvr-01 | ems_metrics_processor                           | 2018-11-14 | 2018-11-19 | 151/600
     10 | staging-01 wk | EmsMetricsProcessor                       | started |  2089 | 2114  | srvr-01 | ems_metrics_processor                           | 2018-11-14 | 2018-11-19 | 151/600
     10 | staging-01 wk | EmsRefreshCore                            | started |  2099 | 2139  | srvr-01 | ems_10000000000001                              | 2018-11-14 | 2018-11-19 | 225/400
     10 | staging-01 wk | EventHandler                              | started |  2205 | 2256  | srvr-01 | ems                                             | 2018-11-14 | 2018-11-19 | 203/500
     10 | staging-01 wk | Generic                                   | started |  1996 | 2042  | srvr-01 | generic                                         | 2018-11-14 | 2018-11-19 | 431/500
     10 | staging-01 wk | Generic                                   | started |  2003 | 2044  | srvr-01 | generic                                         | 2018-11-14 | 2018-11-19 | 422/500
     10 | staging-01 wk | Priority                                  | started |  2014 | 2048  | srvr-01 | generic                                         | 2018-11-14 | 2018-11-19 | 264/600
     10 | staging-01 wk | Priority                                  | started |  2022 | 2049  | srvr-01 | generic                                         | 2018-11-14 | 2018-11-19 | 247/600
     10 | staging-01 wk | Reporting                                 | started |  2250 | 2493  | srvr-01 | reporting                                       | 2018-11-14 | 2018-11-19 | 336/500
     10 | staging-01 wk | Reporting                                 | started |  2272 | 2516  | srvr-01 | reporting                                       | 2018-11-14 | 2018-11-19 | 339/500
     10 | staging-01 wk | Schedule                                  | started |  2032 | 2052  | srvr-01 |                                                 | 2018-11-14 | 2018-11-19 | 204/500
     10 | staging-01 wk | SmartProxy                                | started | 49979 | 49998 | srvr-01 | smartproxy                                      | 2018-11-19 | 2018-11-19 | 150/1024
     10 | staging-01 wk | SmartProxy                                | started | 49988 | 50002 | srvr-01 | smartproxy                                      | 2018-11-19 | 2018-11-19 | 150/1024
     10 | staging-01 wk | Ui                                        | started |  2539 |       | srvr-01 | http:3000                                       | 2018-11-14 | 2018-11-19 | 379/1024
     10 | staging-01 wk | VimBroker                                 | started |  2548 | 2844  | srvr-01 | drbunix:///tmp/MiqVimBroker20181114-2548-1566ii | 2018-11-14 | 2018-11-19 | 242/2048
     10 | staging-01 wk | Vmware::Infra::EventCatcher               | started |  2183 | 2204  | srvr-01 | ems_10000000000001                              | 2018-11-14 | 2018-11-19 | 168/2048
     10 | staging-01 wk | Vmware::Infra::MetricsCollector           | started |  2063 | 2104  | srvr-01 | vmware                                          | 2018-11-14 | 2018-11-19 | 150/400
     10 | staging-01 wk | Vmware::Infra::MetricsCollector           | started |  2071 | 2110  | srvr-01 | vmware                                          | 2018-11-14 | 2018-11-19 | 149/400
     10 | staging-01 wk | Vmware::Infra::Refresh                    | started | 31744 | 31765 | srvr-01 | ems_10000000000001                              | 2018-11-19 | 2018-11-19 | 190/2048
     10 | staging-01 wk | WebService                                | started |  2558 |       | srvr-01 | http:4000                                       | 2018-11-14 | 2018-11-19 | 312/1024
     10 | staging-01 wk | Websocket                                 | started | 11817 |       | srvr-01 | http:5000                                       | 2018-11-15 | 2018-11-19 | 189/1024
     10 | staging-02    | EmsRefreshCore                            | started |  1995 | 5378  | srvr-02 | ems_10000000000002                              | 2018-11-14 | 2018-11-19 | 240/400
     10 | staging-02    | EventHandler                              | started |  2034 | 5383  | srvr-02 | ems                                             | 2018-11-14 | 2018-11-19 | 269/500
     10 | staging-02    | Generic                                   | started |  1877 | 5090  | srvr-02 | generic                                         | 2018-11-14 | 2018-11-19 | 321/500
     10 | staging-02    | Generic                                   | started |  1884 | 5091  | srvr-02 | generic                                         | 2018-11-14 | 2018-11-19 | 325/500
     10 | staging-02    | Priority                                  | started |  1893 | 5088  | srvr-02 | generic                                         | 2018-11-14 | 2018-11-19 | 332/600
     10 | staging-02    | Priority                                  | started |  1901 | 5089  | srvr-02 | generic                                         | 2018-11-14 | 2018-11-19 | 346/600
     10 | staging-02    | Schedule                                  | started |  1909 | 5094  | srvr-02 |                                                 | 2018-11-14 | 2018-11-19 | 203/500
     10 | staging-02    | Ui                                        | started |  2078 |       | srvr-02 | http:3000                                       | 2018-11-14 | 2018-11-19 | 152/1024
     10 | staging-02    | VimBroker                                 | started |  2089 | 5450  | srvr-02 | drbunix:///tmp/MiqVimBroker20181114-2089-1jjs4o | 2018-11-14 | 2018-11-19 | 338/2048
     10 | staging-02    | Vmware::Infra::EventCatcher               | started |  2021 | 5387  | srvr-02 | ems_10000000000002                              | 2018-11-14 | 2018-11-19 | 222/2048
     10 | staging-02    | Vmware::Infra::Refresh                    | started | 16215 | 35469 | srvr-02 | ems_10000000000002                              | 2018-11-19 | 2018-11-19 | 288/2048
     10 | staging-02    | WebService                                | started |  2101 |       | srvr-02 | http:4000                                       | 2018-11-14 | 2018-11-19 | 154/1024
     10 | staging-02    | Websocket                                 | started |  2066 |       | srvr-02 | http:5000                                       | 2018-11-14 | 2018-11-19 | 152/1024

Condensed output reference
rake evm:status_full --collapse # also the default before this PR

Checking EVM status...
 Zone          | Server   |   PID |  SPID | Workers | MB Usage | Roles
---------------+----------+-------+-------+---------+----------+----------------------------------------------------------------------------------
 staging-01 wk | srvr-01* |  1503 |  1912 |      24 |      349 | automate:database_operations:smartstate:user_interface:web_services:websocket
 staging-02    | srvr-02  |  1640 |  5030 |      13 |      348 | automate:ems_inventory:ems_operations:event:user_interface:web_services:websocket

For all rows: Region=10, Status=started, Version=<IP_ADDRESS>, Started=2018-11-14, Heartbeat=2018-11-19
* marks a master appliance

 Zone          | Type                                      |   PID | SPID  | Server  | Queue                                           | Started    | MB Usage
---------------+-------------------------------------------+-------+-------+---------+-------------------------------------------------+------------+----------
 staging-01 wk | EmbeddedAnsible                           |       | 2195  | srvr-01 |                                                 | 2018-11-14 |
 staging-01 wk | EmbeddedAnsible::Automation::EventCatcher |  3538 | 3553  | srvr-01 | ems_10000000000004                              | 2018-11-14 | 237/2048
 staging-01 wk | EmbeddedAnsible::Automation::Refresh      | 31950 | 31982 | srvr-01 | ems_10000000000004                              | 2018-11-19 | 216/2048
 staging-01 wk | EmsMetricsProcessor                       |  2081 | 2115  | srvr-01 | ems_metrics_processor                           | 2018-11-14 | 151/600
 staging-01 wk | EmsMetricsProcessor                       |  2089 | 2114  | srvr-01 | ems_metrics_processor                           | 2018-11-14 | 151/600
 staging-01 wk | EmsRefreshCore                            |  2099 | 2139  | srvr-01 | ems_10000000000001                              | 2018-11-14 | 225/400
 staging-01 wk | EventHandler                              |  2205 | 2256  | srvr-01 | ems                                             | 2018-11-14 | 203/500
 staging-01 wk | Generic                                   |  1996 | 2042  | srvr-01 | generic                                         | 2018-11-14 | 431/500
 staging-01 wk | Generic                                   |  2003 | 2044  | srvr-01 | generic                                         | 2018-11-14 | 422/500
 staging-01 wk | Priority                                  |  2014 | 2048  | srvr-01 | generic                                         | 2018-11-14 | 264/600
 staging-01 wk | Priority                                  |  2022 | 2049  | srvr-01 | generic                                         | 2018-11-14 | 247/600
 staging-01 wk | Reporting                                 |  2250 | 2493  | srvr-01 | reporting                                       | 2018-11-14 | 336/500
 staging-01 wk | Reporting                                 |  2272 | 2516  | srvr-01 | reporting                                       | 2018-11-14 | 339/500
 staging-01 wk | Schedule                                  |  2032 | 2052  | srvr-01 |                                                 | 2018-11-14 | 204/500
 staging-01 wk | SmartProxy                                | 49979 | 49998 | srvr-01 | smartproxy                                      | 2018-11-19 | 150/1024
 staging-01 wk | SmartProxy                                | 49988 | 50002 | srvr-01 | smartproxy                                      | 2018-11-19 | 150/1024
 staging-01 wk | Ui                                        |  2539 |       | srvr-01 | http:3000                                       | 2018-11-14 | 379/1024
 staging-01 wk | VimBroker                                 |  2548 | 2844  | srvr-01 | drbunix:///tmp/MiqVimBroker20181114-2548-1566ii | 2018-11-14 | 242/2048
 staging-01 wk | Vmware::Infra::EventCatcher               |  2183 | 2204  | srvr-01 | ems_10000000000001                              | 2018-11-14 | 168/2048
 staging-01 wk | Vmware::Infra::MetricsCollector           |  2063 | 2104  | srvr-01 | vmware                                          | 2018-11-14 | 150/400
 staging-01 wk | Vmware::Infra::MetricsCollector           |  2071 | 2110  | srvr-01 | vmware                                          | 2018-11-14 | 149/400
 staging-01 wk | Vmware::Infra::Refresh                    | 31744 | 31765 | srvr-01 | ems_10000000000001                              | 2018-11-19 | 190/2048
 staging-01 wk | WebService                                |  2558 |       | srvr-01 | http:4000                                       | 2018-11-14 | 312/1024
 staging-01 wk | Websocket                                 | 11817 |       | srvr-01 | http:5000                                       | 2018-11-15 | 189/1024
 staging-02    | EmsRefreshCore                            |  1995 | 5378  | srvr-02 | ems_10000000000002                              | 2018-11-14 | 240/400
 staging-02    | EventHandler                              |  2034 | 5383  | srvr-02 | ems                                             | 2018-11-14 | 269/500
 staging-02    | Generic                                   |  1877 | 5090  | srvr-02 | generic                                         | 2018-11-14 | 321/500
 staging-02    | Generic                                   |  1884 | 5091  | srvr-02 | generic                                         | 2018-11-14 | 325/500
 staging-02    | Priority                                  |  1893 | 5088  | srvr-02 | generic                                         | 2018-11-14 | 332/600
 staging-02    | Priority                                  |  1901 | 5089  | srvr-02 | generic                                         | 2018-11-14 | 346/600
 staging-02    | Schedule                                  |  1909 | 5094  | srvr-02 |                                                 | 2018-11-14 | 203/500
 staging-02    | Ui                                        |  2078 |       | srvr-02 | http:3000                                       | 2018-11-14 | 152/1024
 staging-02    | VimBroker                                 |  2089 | 5450  | srvr-02 | drbunix:///tmp/MiqVimBroker20181114-2089-1jjs4o | 2018-11-14 | 338/2048
 staging-02    | Vmware::Infra::EventCatcher               |  2021 | 5387  | srvr-02 | ems_10000000000002                              | 2018-11-14 | 222/2048
 staging-02    | Vmware::Infra::Refresh                    | 16215 | 35469 | srvr-02 | ems_10000000000002                              | 2018-11-19 | 288/2048
 staging-02    | WebService                                |  2101 |       | srvr-02 | http:4000                                       | 2018-11-14 | 154/1024
 staging-02    | Websocket                                 |  2066 |       | srvr-02 | http:5000                                       | 2018-11-14 | 152/1024

For all rows: Region=10, Status=started, Heartbeat=2018-11-19

rubocop response - to line up the output, we pad spaces inside #{} -- otherwise it would be too hard to read the spec

@miq-bot add_label blocker

#18248 was merged instead


linux background colour is reset when reloading config

congrats on the 1.0 release! here's something small I ran into:

I set my background colour (and the rest of my colourscheme) using escape codes (using this script)
I reload ghostty's configuration with Ctrl+Shift+,
the background colour is reset to what I guess is the default background colour. The other colours in the colourscheme stay the same, it's just the background colour that changes

This is from

ghostty at commit 35b9ceee2116331b83c0c86269394e2545070b0f, compiled from source
with the default config
It only happens on Linux, not on Mac OS

Duplicate of https://github.com/ghostty-org/ghostty/issues/2795


Add QArmory

Created as a branch of the repo to allow others to edit if needed and delete once merged.

LGTM.


Add regex built-ins

eg. first match, all matches, return groups, ...

Regex features (stolen from python's re library):

Search => return first index of pattern match
Match => return the portion of the string that pattern matches
Matches Fully => return whether the entire string matches the pattern
Split => Split a string on a pattern
Find All => find all non-overlapping matches of pattern in string
Find All overlapping => Find all but more painful to implement
Substitute => Replace instances of pattern with string/function taking match as input
Sub and Count => Sub but also return number of replacements
Escape => Take a string and escape it
Groups => Return a list of all groups of a match
Span => Return the start and end position of a match


add indexes for sections in docs and other fix

add indexes for sections
add blank space between English and Chinese character
change some punctuations

@fleeto please review

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: rootsongjc
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
Assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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

Hi @rootsongjc. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

lgtm

@geeknoid Can you merge it, please?


Added Hackerrank solution to Java and C languages

_ No description provided. _

@TheDarkLord100 Great, Please add your name in readme.md file


Wrong flake8 configuration

After the release of Flake 6.0.0 it is invalid to have inline comments in the ignore part of the configuration file, see this issue: https://github.com/PyCQA/flake8/issues/1750
To avoid errors in the future we can easily fix this by not using inline comments to describe the error codes.
The current pattern we are using is the following:
[flake8]
ignore =
   E501  # comment about this error code

This can be fixed by doing this instead:
[flake8]
ignore =
   # comment about this error code
   E501,
   # another comment
   E502

we are on 6.1.0 now, this issue is probably solved


Preserve current translation until new (extended) translation arrives, when merging

Translating multiple consecutive words keeps on emptying the translation bubble and filling it up with the newer translation, which in turn makes the text move left and right, behavior which could become annoying. Thus we might want to preserve the current translation text until the new one arrives. This will ensure that text only expands, to the right.

niiice!


Issues in the lecture "A Problem that Stumped Milton Friedman"

Some packages that are not used are imported.

from scipy.stats import beta
import quantecon as qe

Typos in the explanation of Bellman Equation.

In the equation, minimum is taken in outside the integral, but we should take it inside.
In addition, we have to replace f_0(z') with f(z').

In the function Q in operator_factory, using parallel computing is hard-coded.

def operator_factory(wf, parallel_flag=True):

 ...

 @njit(parallel=True)
 def Q(h):
     h_new = np.empty_like(π_grid)
     h_func = lambda p: interp(π_grid, h, p)

 ...

However, if there is no intention in this hard coding, we should rewrite
 @njit(parallel=parallel_flag)
 def Q(h):

Thanks @Yuya-Furusawa !
All good points.
@shizejin Would you mind to make those adjustments?  I prefer that parallelization is optional.

Thanks @Yuya-Furusawa .
Regarding the second point, since we believe z' follows fπ, I guess we should replace f0(z') with fπ(z') rather than f(z'). What do you think?

@shizejin Exactly. fπ(z') is suitable because z follows fπ from the decision maker's point of view.


Kernel opening should be provable on auxiliary

User Story
As a validator
I want to prove a kernel opening on auxiliary
Because I want to advance the meta-blockchain.
Info
The logic, as per the whitepaper, is as follows:

(a new kernel opens on origin)
(the origin state root that includes the new, open kernel is reported and finalized on auxiliary)
anyone makes a Merkle proof of the open kernel in the KernelGateway
in the success case, the AuxiliaryBlockStore is informed that a new kernel opening was proven
and the PollingPlace is informed about the future change in the set of validators
(when the auxiliary dynasty increases the second time (d+2), the AuxiliaryBlockStore confirms the kernel opening)
(the AuxiliaryBlockStore confirms on the PollingPlace, the polling place increases the meta-block height (e.g. updates validator set).)

⚠ The points in parentheses are not part of this ticket.
⚠ Rename MetaBlockGateway to KernelGateway.
Contracts:

KernelGateway
AuxiliaryBlockStore

The KernelGateway should inform the PollingPlace about the change in the set of validators from the kernel opening proof.
The AuxiliaryBlockStore should only track that at dynasty d a kernel opening was proven so that the AuxBlockStore can inform the PollingPlace about the new meta-block increase. The polling place then already knows the change in validators at the new height from the KernelGateway.

The polling place's update in set of validators is part of #408 and not here.


added schema creation pattern for routing to lead node

The sql for creating schema is now routed to lead node.
Otherwise what happens is that if a schema is created via jdbc client & not table is yet created in schema, the hive catalog  does not have entry of that schema.
And so dropping of the schema  throws exception.
Patch testing
added bug test
Is precheckin with -Pstore clean?
ReleaseNotes changes
(Does this change require an entry in ReleaseNotes? If yes, has it been added to it?)
Other PRs
bug test

@dshirish @kneeraj @sumwale @suranjan @ashetkar : pls review...


Added support for	'Customize Task Description Template' in 'Delivery Pipeline Plugin'

PR is about adding one more parameter to deliveryPipelineConfiguration (Delivery Pipeline Plugin) which is descriptionTemplate (Customize Task Description Template).

@daspilker Could you please take a look?

This is already supported by the Dynamic DSL:
job('example') {
  properties {
    pipelineProperty {
      taskName('task')
      stageName('stage')
      descriptionTemplate('template')
    }
  }
}


Cypress Testrunner Pass Job on  GitLab Pipeline

🐛 Bug Report
Working with Cypress Toolkit on GitLab, the Pipeline is completed as a Job succeeded when there are some Tests with failures.

There are some Tests with failures:

The Job is passed

Could you please add the image and saucectl version you were using?

image: saucelabs/stt-cypress-mocha-node
saucectl version 0.16.0
(build 2c43a17a2032b9ed6a2473f10e951a3a209b1236)

Hi @arevaloignacio !
This is now fixed in saucelabs/stt-cypress-mocha-node:v<IP_ADDRESS> !

I tried with saucelabs/stt-cypress-mocha-node:v<IP_ADDRESS>, but it reopens the Ticket #58
Now the Test execution stops after the first failed test.

Thanks for your feedback !
I'll take a look on #58 !
If you have more input, please add it to #58.


Switch to more reliable OpenSearch Lucene snapshot location

Description
Switch to more reliable OpenSearch Lucene snapshot location
Issues Resolved

Related https://github.com/opensearch-project/opensearch-build/issues/3874
Related https://github.com/opensearch-project/OpenSearch/pull/11728

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@dbwiddis Could you take a look?

@owaiskazi19 @saratvemulapalli  Looks like there is an unrelated build break can you let me know how this should move forward?
/home/runner/work/opensearch-sdk-java/opensearch-sdk-java/src/test/java/org/opensearch/sdk/TestExtensionInterfaces.java:175: error: constructor Parameters in class Parameters cannot be applied to given types;
        Processor.Parameters parameters = new Processor.Parameters(null, null, null, null, null, null, null, null, null);
                                          ^

@owaiskazi19 @saratvemulapalli Looks like there is an unrelated build break can you let me know how this should move forward?

Should be fixed by https://github.com/opensearch-project/opensearch-sdk-java/pull/979.

@owaiskazi19 Looks like there are still issues with the PR checks, I've created a issue:

https://github.com/opensearch-project/opensearch-sdk-java/issues/981

@peternied here is the fix https://github.com/opensearch-project/opensearch-sdk-java/pull/982
Please rebase after the changes are merged.


building fails on Mac OS

I'm trying to build this on Mac OS and it fails.
cmake output:
$ cmake -DOpenCV_DIR=/usr/<EMAIL_ADDRESS>-DAFFDEX_DIR=$HOME/affdex-sdk $HOME/sdk-samples
-- The C compiler identification is AppleClang <IP_ADDRESS>00042
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00042
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Setting up compiler warnings
-- Updating compiler to make use of C++14
-- Bitness detected: 64
--
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- Boost version: 1.59.0
-- Found the following Boost libraries:
--   system
--   filesystem
--   date_time
--   regex
--   thread
--   timer
--   chrono
--   serialization
--   log
--   log_setup
--   program_options
--   atomic
--
-- ------- SUMMARY -------
-- Boost version found   = 1.59.0 (105900)
--   - system<EMAIL_ADDRESS>--   - filesystem<EMAIL_ADDRESS>--   - date_time<EMAIL_ADDRESS>--   - regex<EMAIL_ADDRESS>--   - thread<EMAIL_ADDRESS>--   - timer<EMAIL_ADDRESS>--   - chrono<EMAIL_ADDRESS>--   - serialization<EMAIL_ADDRESS>--   - log<EMAIL_ADDRESS>--   - log_setup<EMAIL_ADDRESS>--   - program_options
--<EMAIL_ADDRESS>--
-- Affdex
-- /Users/jprall/affdex-sdk/lib/libaffdex-native.dylib
--
-- OpenCV version found   = 2.4.13 (<IP_ADDRESS>)
-- OpenCV_LIB_DIR         = /usr/local/share/OpenCV/lib
--   - objdetect      opencv_objdetect
--   - ml             opencv_ml
--   - imgproc        opencv_imgproc
--   - highgui        opencv_highgui
--   - core           opencv_core
--
-- Apps identified for building:
--    - opencv-webcam-demo
--    - video-demo
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/jprall/build

make output:
$ make
Scanning dependencies of target opencv-webcam-demo
[ 25%] Building CXX object opencv-webcam-demo/CMakeFiles/opencv-webcam-demo.dir/opencv-webcam-demo.cpp.o
In file included from /Users/jprall/sdk-samples/opencv-webcam-demo/opencv-webcam-demo.cpp:10:
In file included from /Users/jprall/affdex-sdk/include/Frame.h:4:
/Users/jprall/affdex-sdk/include/typedefs.h:55:10: warning: scoped enumerations are a C++11 extension [-Wc++11-extensions]
    enum class FaceDetectorMode
         ^
In file included from /Users/jprall/sdk-samples/opencv-webcam-demo/opencv-webcam-demo.cpp:10:
/Users/jprall/affdex-sdk/include/Frame.h:24:14: warning: scoped enumerations are a C++11 extension [-Wc++11-extensions]
        enum class COLOR_FORMAT
             ^
In file included from /Users/jprall/sdk-samples/opencv-webcam-demo/opencv-webcam-demo.cpp:11:
/Users/jprall/affdex-sdk/include/Face.h:186:10: warning: scoped enumerations are a C++11 extension [-Wc++11-extensions]
    enum class Gender {
         ^
/Users/jprall/affdex-sdk/include/Face.h:196:10: warning: scoped enumerations are a C++11 extension [-Wc++11-extensions]
    enum class Glasses {
         ^
/Users/jprall/affdex-sdk/include/Face.h:320:10: warning: scoped enumerations are a C++11 extension [-Wc++11-extensions]
    enum class Emoji {
         ^
/Users/jprall/affdex-sdk/include/Face.h:344:18: warning: use of enumeration in a nested name specifier is a C++11 extension [-Wc++11-extensions]
            case Emoji::Relaxed:
                 ^
/Users/jprall/affdex-sdk/include/Face.h:344:18: error: expression is not an integral constant expression
            case Emoji::Relaxed:
                 ^~~~~~~~~~~~~~

Note that I used this to workaround the issue.  @umangmehta12 has a better fix.
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 179a120..ba12b73 100755
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -33,6 +33,7 @@ endif()

 if(CMAKE_CXX_COMPILER_ID MATCHES "Clang")
     status("Updating compiler to make use of C++14")
+    set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11")
     set(CMAKE_XCODE_ATTRIBUTE_CLANG_CXX_LANGUAGE_STANDARD "c++14")
     set(CMAKE_XCODE_ATTRIBUTE_CLANG_CXX_LIBRARY "libc++")
 endif()

I am assigning this to @ahamino, if he agrees then we can merge this in, else I will close the issue.

Sorry if there is an obvious answer to this question hidden somewhere, but what libraries are you using to compile on Mac OS? The only Affdex libraries I've seen that are compiled for Mac OS are inside the Affdex.framework, which is not compatible with the cmake build as far as I can tell. Is libaffdex-native.dylib extracted from the Unity package?

+1

@ahmedalmoraly @adennie any ideas on this?

At the moment, we don't provide a C++ library for macOS. We only have AffdexSDK on cocopods which is an Objective-C framework.


Make every API that needs OCaml/Rust async instead of awaiting at the top level

The web version of o1js still has a fairly large unavoidable import time (~0.5s). This used to happen in the first asynchronous microtask (and leaked to users through await isReady) and is now happening immediately with top-level await.
To enable quicker loading as well as prepare for https://github.com/o1-labs/o1js/issues/1192, the big async task should be awaited inside the functions that need it, not at the top level. There are just a few of those functions which aren't already async:

Provable.runAndCheck() and runUnchecked() -- mostly used as part of Mina.transaction() which is already async
SmartContract.analyzeMethods()
Provable.constraintSystem() -- mostly used in analyzeMethods()
Mina.LocalBlockchain()

The change to async APIs will be a natural side effect of #735, after which this issue is no longer breaking

Update: all of the APIs above, except Mina.LocalBlockchain, are async now.
We should make LocalBlockchain async, and move the top level await away from the top level and into functions that depend on it. That might also allow us to simplify Integration with legacy web bundlers like webpack, see #1575


[@shopify/react-html] Let consumer add inline style in the head

Description
You can now add inline style in the head of the document with @shopify/react-html
This will still render a <link /> element.
<Style href='foo.css' />

This will now render a <style /> element.
<Style>.foo {color: red;}</Style>

Type of change

[x] @shopify/react-html Minor: New feature (non-breaking change which adds functionality)expected)

Checklist

[x] I have added a changelog entry, prefixed by the type of change noted above (Documentation fix and Test update does not need a changelog as we do not publish new version)

@michenly you can stop reviewing this PR. @clauderic found a mistake in my code. I want the

After some discussion with @lemonmade, I changed the approach a little bit. The PR is now ready to be reviewed.


Update Robinhood Library For PyPI Release

After using this library thanks to @gregoberfield, we wanted to make it easier to distribute, more reliable, and easier to update going forward.
Attached is a proposed v1.0.0 release

automated py2/py3 coverage
added testing suite
added docstrings for explaining expected behavior
PEP-ified calls for easier readability
added logout method (c/o @gregoberfeild)
added positions endpoints (c/o @gregoberfield)
added request.raise_for_status() for better error checking
(largely) retained api behavior from existing version
started work toward more feature reliability

custom exceptions collection
enums for feeds where applicable
test framework for auth and un-auth endpoints

created a docs/ directory for documentation

moved example.py to docs
added info on testing

Fixed markdown in README
Added names to CONTRIBUTORS

There is still a lot of work to do, but this should make the Robinhood library friendlier for many more developers going forward!

Note:
covers both #21 and #20 issues directly

Great work!!! Merging

Might be a good idea to tag release here on github, so it's easy to pick out in the future


fixed mobile view

fixed mobile view

@priyanka9634 do the changes only required - other changes are not required here. Closing this PR without merging into main!


update all repos' README

Improve our READMEs with these new specifications.
Make sure all projects are well documented and have these sections:

Prerequisites
Installation
Quickstart
Code Style (eslint)
Testing ????
Build
License
Code of conduct

of course, not all are required. Just use what makes sense, if something is missing just share it on this issue.
Also this page: https://github.com/Aletheia-Data

Great Job!
Let's now add it to all our repos:

[ ] App
[ ] API
[ ] ADMIN
[ ] Search
[ ] Landing
[ ] Hep
[ ] Map
[ ] Cors
[ ] NFT storage strapi plugin
[ ] Web3 storage strapi plugin

hi @natachadelarosa any news on this? Do you have any blockers?

Nice work @natachadelarosa 💪🏽


Global Admin Breadcrumb On Agency Dashboard

When a global admin clicks on Dashboards -> Agencies and then on an agency's name - it takes them to the agency dashboard (with compliance rate etc.).
On that page - /agency_charts/AgencyName - just above the agency name should be breadcrumbs.
The text 'Dashboard/Agencies' - which links back to the Agencies Dashboard (same page as going to Dashboard->Agencies).
Design as per https://mongodb.invisionapp.com/share/MYXRXC2T2H3#/422348696_Global_Admin-Dashboard-Agency
The current page looks like this, without a breadcrumb.

Hi! Thanks for the great kickoff event, @Sheeri! I'm new to contributing to open source and am interested in taking on this issue

Hi @SEGH ! It was great to have you on the call. I just realized that I labeled this issue incorrectly - it's global admin, so I added the 'needs own instance' issue - I've assigned you the issue. If you don't want to build your own foundation now, that's understandable, just let me know and I can unassign you.
Otherwise, the build docs are at https://wildaid.github.io/build/ and I'm happy to help with any questions you have!

Thanks, @Sheeri, that link was helpful! I took a go at it; let me know if I need to revise anything.


[BUG] Python > group_by > examples

group_by(['one', 'two', 'three'], 'length') should be group_by(['one', 'two', 'three'], len)

Feel free to open a PR for this, I would be glad to merge it.


import tensorflow command gives error

C:\Users\Prasad>python
Python 3.12.4 (tags/v3.12.4:8e8a4ba, Jun  6 2024, 19:30:16) [MSC v.1940 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import tensorflow
Traceback (most recent call last):
File "C:\Users\Prasad\AppData\Local\Programs\Python\Python312\Lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 70, in
from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\Prasad\AppData\Local\Programs\Python\Python312\Lib\site-packages\tensorflow_init_.py", line 38, in
from tensorflow.python import pywrap_tensorflow as _pywrap_tensorflow  # pylint: disable=unused-import
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\Prasad\AppData\Local\Programs\Python\Python312\Lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 85, in
raise ImportError(
ImportError: Traceback (most recent call last):
File "C:\Users\Prasad\AppData\Local\Programs\Python\Python312\Lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 70, in
from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.
Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/errors for some common causes and solutions.
If you need help, create an issue at https://github.com/tensorflow/tensorflow/issues and include the entire stack trace above this error message.

@prasad-mali07,
Could you please provide the tensorflow and the compatible version which you are trying to install. Also there are at least 3 possible scenarios:
- You need to install the MSVC 2019 redistributable
- Your CPU does not support AVX2 instructions
- Your CPU/Python is on 32 bits
- There is a library that is in a different location/not installed on your system that cannot be loaded.

https://github.com/tensorflow/tensorflow/issues/61887
Thank you!

It seems that my CPU doesn't support AVX1 or AVX2. However my msvcp140_1.dll plugin was in a wrong directory as well. But apparently there are certain TF wheel files to install for CPU without AVX support. I appreciate your help in realizing my CPU issue.

Duplicate of #36167


chore: print io err kind

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#594  👈 (View in Graphite)
#593
#592
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 4, 6:20 PM EST: A user started a stack merge that includes this pull request via Graphite.


[Feature Request] Instrumentation for Spring Async Framework

I use non-spring boot application with spring version 4.3 and I would like to add tracing to Spring Async framework. I see that there is an instrumentation available in sleuth https://github.com/spring-cloud/spring-cloud-sleuth/tree/master/spring-cloud-sleuth-core/src/main/java/org/springframework/cloud/sleuth/instrument/async. Add I have a hard time leveraging it for my non spring boot application.
I would be better if we get this feature down to brave and this would be really helpful for every one who wants to trace spring async annotated calls in non spring boot applications.

if you can customize the ExecutorService that Spring's @Async  is using you could do this perhaps https://github.com/openzipkin/brave/tree/master/brave#setting-a-span-in-scope-via-custom-executors

Has there been any progress on this feature?
Do we already have a method to bypass it safely?
I need it for a project.


chore: update CODEOWNERS

I think that flagd and OFO are at the size and complexity that we need more CODEOWNERS. I think there's simply too many issues for a single person to keep up with.
I think 3 is a good number. It means that even if one CODEOWNER is away, there is one other person who can approve.
Relates to: https://github.com/open-feature/flagd/pull/228

Codecov Report

Merging #265 (edb1592) into main (063c9fb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #265   +/-   ##
=======================================
  Coverage   56.18%   56.18%
=======================================
  Files           3        3
  Lines         388      388
=======================================
  Hits          218      218
  Misses        156      156
  Partials       14       14

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


noExternal

Clear and concise description of the problem
As a developer migrating to tsdown, I'd like to be able to bundle internal packages from a monorepo into the published package.
(I'd be happy to PR if desired, though I imagine it'd be less effort to add this yourself than to review whatever nonsense I come up with 🙃)
Suggested solution
Wire up Rolldown's existing noExternal support into tsdown. Should just be a bit of parameter drilling?
Alternative
Keep using tsup
Additional context
Getting another package tsdown-ified :)
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I'm happy to accept this feature! Feel free to open a PR. Ultimately, I want to support as many tsup features as possible.

Brief update: I looked into it a bit, and it looks like I was wrong that Rolldown supports noExternal.
I do still plan on getting around to this, but I've got some other work that's higher priority.


create table explorer (%sqlcmd explore)

context: https://github.com/ploomber/jupysql/pull/146#issuecomment-1457489061
cc @idomic
--
Executing %sqlcmd explore --table table --schema schema should display an HTML view of the table, users should be able to sort each column by clicking on the header and control the number of displayed items (e.g., 10, 20, 30) and move to the next set of images. Pretty much like this, except we won't include the search field in this iteration.
Interacting with the table (e.g., sorting a column) should trigger the execution of a SQL query, results should be fetched and the table must be updated. In other words, no processing should happen locally, everything should be computed in the SQL engine.
The feature should be complemented with a tutorial in the documentation. Most likely, the interactive component won't be visible from the tutorial so we should tell users to open it on Binder to see it in action.

Updated the top comment with the acceptance criteria.


Report code coverage using Codecov

I'd expect CodeCov to report back the coverage result into the comments. Isn't this the case?

I'd expect CodeCov to report back the coverage result into the comments. Isn't this the case?

Yes, It should report back. Since currently there are no references to compare. This need to be merged and then I'd expect next PR onwards we should see the comment with coverage.


Reconnect fails if branch policy does not allow push

I was recently trying to change my branch name using az staticwebapp disconnect and az staticwebapp reconnect. On trying to reconnect, I kept getting the error 'Operation returned an invalid status 'Internal Server Error' after the authorization step. I figured out that this was because the branch I was attempting to link to required PRs to merge changes (no direct push). An error message indicating this, or at least a note in the docs, would have been helpful.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e683c181-f005-a6c8-cb11-74ce557e51f8
Version Independent ID: 860411b7-f2f1-af2b-b5e2-7d67e1b8e028
Content: az staticwebapp
Content Source: latest/docs-ref-autogen/staticwebapp.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

route to service team


Maya: Look allow referenced materials publish

 We should allow publishing a look that has referenced materials loaded from a material library (ground, water, fire, etc)
This material wouldn't be in the lookdev scene originally but in matlib.
[PYPE-375] created by admin
[cuID:OP-1217]

The look extractor would "import" the reference in the publish already and thus does allow using a lookdev from matlib in a lookdev. However, it'd transfer and copy the (potentially processed files, like e.g. through maketx) into the publish folder. I think that'll always be needed to correctly support sitesync (if e.g. the site only that this project available, etc.)
As such, I believe it should already be possible to use looks from the matlib - although likely at first publish it will report invalid ids which I think you can regenerate, if not.. then that's the issue that'd need to be solved.
What's the particular tweak you feel need to be done to make this more appropriate for using materials from matlib?

You're right this is technically already possible and didn't get any interest since it was created ages ago. Closing.


Remove unused references

I don't think this is doable. I am closing it, if anyone finds a way to do it we can reopen it.
BTW, the compiler already removes unused references from the resulting assembly.


docker:Sign docker images without keys and push to ghcr.io

Sign docker images without keys and push to ghcr.io
Sign docker containers without using keys. This uses GitHub as an OIDC provider and signs the image.https://github.com/sigstore/cosign/blob/main/KEYLESS.md, when there aren't keys like https://github.com/lightningnetwork/lnd/blob/c43b9e4fe716f084ff135cf658897fb056e075a0/.github/workflows/docker.yml#L30  then it is not likely to be compromised. Though that in the code is using for it being pushed into the registry.
This solves https://github.com/lightningnetwork/lnd/issues/5728
Docker Image validated
These images are signed which means they can be validated.  This can potentially replace verify-install #5780
Here is the validation of the signature.
COSIGN_EXPERIMENTAL=1 cosign verify ghcr.io/naveensrinivasan/lnd
No TUF root installed, using embedded CA certificate.
No TUF root installed, using embedded rekor key

Verification for ghcr.io/naveensrinivasan/lnd:latest --
The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - Existence of the claims in the transparency log was verified offline
  - Any certificates were verified against the Fulcio roots.

[
   {
      "critical":{
         "identity":{
            "docker-reference":"ghcr.io/naveensrinivasan/lnd"
         },
         "image":{
            "docker-manifest-digest":"sha256:fcc31d459fddc0986570ae51236c7532693fa32006ad704751499a90ca9ca743"
         },
         "type":"cosign container image signature"
      },
      "optional":{
         "Bundle":{
            "SignedEntryTimestamp":"MEQCIDzQLsa9UcMxqnuVxm+eX6/URZvjqcOLyITik3vIsl13AiA3aj8MflSiCVHerFUGViXGqs9tiNEneox/qihtKun8qg==",
            "Payload":{
               "body":"eyJhcGlWZXJzaW9uIjoiMC4wLjEiLCJzcGVjIjp7ImRhdGEiOnsiaGFzaCI6eyJhbGdvcml0aG0iOiJzaGEyNTYiLCJ2YWx1ZSI6IjU0YzFkNGViMTBkODMyNDUzYmY3YTE0MjkzZTgxNTMwYjlmM2Q2M2UzYzI0NTYzNjVjNTQ5YWU2YzdkOWIyYzkifX0sInNpZ25hdHVyZSI6eyJjb250ZW50IjoiTUVVQ0lGQkYycG50bkpGRFc4NHVjSDhtbEtCRXVrYTNRNm5nVWhOV0VqQUhMT1pZQWlFQThOc2FzL2JjWTBDZHl3NDhXZGllcWZ1VXBZbFF1ZXNNeTRjRkpqdlRxeUE9IiwiZm9ybWF0IjoieDUwOSIsInB1YmxpY0tleSI6eyJjb250ZW50IjoiTFMwdExTMUNSVWRKVGlCRFJWSlVTVVpKUTBGVVJTMHRMUzB0Q2sxSlNVTjNha05EUVd0bFowRjNTVUpCWjBsVlFVcExXVUZhVGtVdk1rbFlRMUJLZEVVM2RVMDJObEpRZUhSSmQwTm5XVWxMYjFwSmVtb3dSVUYzVFhjS1MycEZWazFDVFVkQk1WVkZRMmhOVFdNeWJHNWpNMUoyWTIxVmRWcEhWakpOVWtWM1JIZFpSRlpSVVVSRmQyaDZZVmRrZW1SSE9YbGFWRUZsUm5jd2VRcE5WRVYzVFVSSmQwMVVTWGhPVkU1aFJuY3dlVTFVUlhkTlJFbDNUVlJSZUU1VVNtRk5RVUYzVjFSQlZFSm5ZM0ZvYTJwUFVGRkpRa0puWjNGb2EycFBDbEJSVFVKQ2QwNURRVUZSVlZaNGVFWjFhWFpJV1VOeEx6Sm1kR1ZNZGt0VGJVaDBPRWszZVhKbWRrMXpUamhqYUd4d2NFaHpPV3hrWVhOR1pIRXhXallLVEVsb1prRkdlWEZvYUVwbFlrczBXR3AxVURSclRHcFZhVzFzVW5KMFVtZHZORWxDWTNwRFEwRlhPSGRFWjFsRVZsSXdVRUZSU0M5Q1FWRkVRV2RsUVFwTlFrMUhRVEZWWkVwUlVVMU5RVzlIUTBOelIwRlJWVVpDZDAxRVRVRjNSMEV4VldSRmQwVkNMM2RSUTAxQlFYZElVVmxFVmxJd1QwSkNXVVZHVFdGcUNtSlBVMjEyY21SalFUUm5jRGQ1Uldod2VUSjZSbGN5VGsxQ09FZEJNVlZrU1hkUldVMUNZVUZHVFdwR1NGRkNRbTFwVVhCTmJFVnJObmN5ZFZOMU1Vc0tRblJRYzAxSlIwNUNaMmR5UW1kRlJrSlJZMEpCVVZOQ1owUkNLMDFJZDBkRFEzTkhRVkZWUmtKNlFVTm9ia0p2WkVoU2QwOXBPSFpqU0Vwd1pHMUdNQXBhVjA1b1RGZE9kbUp1VW14aWJsRjBUbXBCZWxwdFZUTmFWR04wVFVSQmQwMURNSGxOYWtrelRGZEtiVTU2VlhSYWFsSnRUbGRWTkUxSFVYbFBWRlV3Q2t4dVRqQmlNMHBvV2pKVmRWb3lPWFphTW5oc1dWaENjR041TldwaU1qQjJXVEpGZWs1dFJYaGFWR3N5VFdwUmVWbHFiRzFaTWtsNFRrUlpkbGt5UlhVS1dUTktNRTFIYjBkQk1WVmtSVkZGUWk5M1VtZE5SalpIV0Vkb01HUklRbnBQYVRoMldqSnNNR0ZJVm1sTWJVNTJZbE01ZFZsWVdteGFWelY2WTIxc2RRcGhXRnBvWXpKR2RVd3llSFZhUXpoMVdqSnNNR0ZJVm1sTU0yUjJZMjEwYldKSE9UTmplVGxyWWpKT2NscFlTWFJqTW14dVltazFOV0pYZUVGamJWWnRDbU41T1hka1YzaHpUSHBGTkV3eU1XeGpiV1JzVFVGdlIwTkRjVWRUVFRRNVFrRk5SRUV5YTBGTlIxbERUVkZEUm1KSVVqVlpTQ3RoUVdFcmIyNDBhVFFLTWtFNFNGVnJURU5aVW1KRVJFRllRVkJqVEU5QldYTkRhVWRpUlU4d1RETTBPVkk0WVVOdWNVTndUVTkyZEUxRFRWRkVPR1V4YWtSdmNFTnRSWGN5VmdvM2JFTlViWGRNTDJwMlJGQjBTemxsZHpOb1dHdEVOVEF3VERsU1dGUnpXRTlyUmtwVFVVeEVaRGxNVW1sVk5VdERkVms5Q2kwdExTMHRSVTVFSUVORlVsUkpSa2xEUVZSRkxTMHRMUzBLIn19fSwia2luZCI6InJla29yZCJ9",
               "integratedTime":1633137714,
               "logIndex":729517,
               "logID":"c0d23d6ad406973f9559f3ba2d1ca01f84147d8ffc5b8445c224f98b9591801d"
            }
         },
         "Subject":"https://github.com/naveensrinivasan/lnd/.github/workflows/docker-sign.yml@refs/pull/18/merge"
      }
   }
]

What is cosign and Sigstore?
https://www.sigstore.dev
Sigstore trusts
https://github.com/sigstore/root-signing
How it works
https://www.sigstore.dev/how-it-works
Can I run my own transparency log?
Yes, https://github.com/sigstore/rekor

Here is the docker image from my push https://github.com/naveensrinivasan/lnd/pkgs/container/lnd

Not including the release notes as this one is not yet decided.

@naveensrinivasan, remember to re-request review from reviewers for your latest update

@naveensrinivasan, remember to re-request review from reviewers for your latest update

@naveensrinivasan, remember to re-request review from reviewers for your latest update

@naveensrinivasan, remember to re-request review from reviewers when ready

@guggero Friendly Ping.

Thanks for the PR. I took a quick look at the keyless signing with cosign. From what I understand this doesn't really improve the security of the generated images.
Sure, it proves that the images were built by GitHub and not modified after the build. But the verification we are looking for is that the build is legitimate (more than one team member signed off on it, a single bad actor cannot arrive at more than one signature of the required 5) and reproducible (everyone can arrive at the same digest of the binaries on their own machine).
If instead we could all build the images locally, sign the digest and upload that signature to GitHub in a way that cosign could verify them, that would be great. But I'm not sure that's currently possible? Also we'd want to re-use our RSA keys for signing the images.
Perhaps for now we can just add an action to .github/workflows/docker.yml that additionally uploads the generated images to ghcr.io.

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

https://twitter.com/kelseyhightower/status/1502112834120937477
Also, some interesting things are coming out of SLSA with build provenance https://github.com/slsa-framework/slsa https://github.com/gossts/slsa-provenance, there soon be a blog post on this along with a white paper on generating build-provenance and signing within the GitHub workflow

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

Closing due to inactivity

Closing due to inactivity

Closing due to inactivity

Realized after grokking the btcd version of this PR, that it's actually pretty useful.

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

@naveensrinivasan, remember to re-request review from reviewers when ready

Closing due to inactivity

Closing due to inactivity

Closing due to inactivity

Closing due to inactivity

Closing due to inactivity

Closing due to inactivity

Closing due to inactivity

Closing due to inactivity

!lightninglabs-deploy mute


Fix/small corrections

[x] fixed: Not need to reload the page to see the new badges added to the list
[x] fixed: Wrong message when checked-out user tries to send a bedge

Can you update your branch please @RafaDSan ?

Can you update your branch please @RafaDSan ?

Updated! @0xneves


Add domainID to keyserver

Wait for #845 to be merged first

Codecov Report

Merging #851 into master will decrease coverage by 0.38%.
The diff coverage is 4.76%.

@@            Coverage Diff             @@
##           master     #851      +/-   ##
==========================================
- Coverage   46.52%   46.13%   -0.39%
==========================================
  Files          36       36
  Lines        2917     2935      +18
==========================================
- Hits         1357     1354       -3
- Misses       1343     1366      +23
+ Partials      217      215       -2

Impacted Files
Coverage Δ

core/keyserver/keyserver.go
0% <0%> (ø)
:arrow_up:

core/client/kt/requests.go
0% <0%> (ø)
:arrow_up:

integration/testutil.go
63.88% <100%> (+2.35%)
:arrow_up:

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 ca57ac6...b9c775e. Read the comment docs.


Add DropLeft And Right #44 #45

#44 #45
I added DropLeft And Right it as an option of drop.
please check and review it.

@mentol310 awesom job as always!


Multiple initial PDP announcements [6379]

With this PR a participant will send 1 additional quick announcement (spaced 500ms) when starting. This should improve discovery when several participants are started at the same time.
The user can configure this new feature both on code and XML

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

Build status:

Linux
Mac
Windows

Liveliness tests seem to be also failing on base branch (1.8.x). See this manual run

Build status:

Linux
Mac
Windows


Terraform fails to init while using a module.

This is a followup to https://github.com/jfrog/terraform-provider-artifactory/issues/26
I created a git repo with code example - https://github.com/KrystianMarek/bug-terraform-artifactory-provider
As described in the readme, when a module is used https://github.com/KrystianMarek/bug-terraform-artifactory-provider/blob/main/main.tf#L13 terraform init fails.

I believe you need to

Define the artfactory provider again in the module where the provider is actually used:
.../modules/core/main.tf:
terraform {
required_providers {
artifactory = {
source = "jfrog/artifactory"
version = "2.2.5"
}
}
}

Pass in the authenticated artifactory provider from main.tf as its not inherited (only default providers are inherited - dont ask as I havnt looked :) ).  You dont need another 'provider "artifactory" {}' in sub-modules (iirc TF doesnt like this & complains).

.../main.tf:
module "core" {
source = "./modules/core"
providers {
artifactory = artifactory
}
}
The good news is that you only have to auth once into the .../main.tf provider & then reuse as above as needed.
The above worked for me, but I'm sure some kind person can correct if this is the wrong approach...

Hi @hammopau, thanks, indeed terraform init worked, I just had to update /main.tf with
module "core" {
  source = "./modules/core"
  providers = {
    artifactory = artifactory
  }
}
``` in order to make the `terraform plan` work as well

@KrystianMarek - based on your most recent comment, am I am to assume you've resolved your issue?

I would consider it more like a workaround, it works for me with the updates suggested by @hammopau . I leave it up to you @chb0github if you want to fix it or ignore it.

What happens if no module is used and this is added. Does it break? If not we can merge, otherwise this should be up to the person who decided to use the additional feature of Terraform modules.

I just upgraded to 0.14.6 (from 0.14.5) and the problem of the provider not being passed as expected between parent & child modules appears to have been resolved in this release (or so I thought - see below).  I now have both modules declaring artifactory as required_plugin, but only configuring "provider artifactory {}" in the parent, and all is working ok.
I also tested with 0.13.6 & its also ok with the 'correct' config.  To try and figure out where the problem was, I tested with 0.14.5 again (as used when I first figured out passing the provider fixed the issue), just to see if it was a TF issue & thats also working now, whereas it was not previously...
...confused_dot_com...


Can you make a compound button do 2-3 thigns at once like hold button and swap analog sticks?

I am playing fable 3 and aiming is with the left stick like this is the late 90s where many games still have bad to unintivute looking/aiming(between my OCD and dyslexia I process things backwards and forwards a couple time so it takes forever for me to adjust to simple things like this).
So I want to have the left bumper used as the left bumper but also swap the analog sticks while its depressed.
I suppose I just give up and switch back to KB and mouse I mean it dose not use that many buttons and is not that time sensitive like souls or batman is. But since I am using my PS4 pad on the PC these days(shame the Xbox one controller has horrid dpad)  but I really like strange esoteric button layouts and compound button fckatory, just how crazy dose DS4windows get with over the top customization?

Not sure if it is possible but you can ask the guys over on the Ryochan7 version of DS4Windows: https://github.com/Ryochan7/DS4Windows/issues
I'm not sure which version of DS4Windows you are using, but you are posting in the old no-longer-maintained DS4Windows repository (Jay2Kings). Ryochan7's is the current defacto now.
Also, the main developer and volunteers there are really responsive. They can give you a really good answer. They may even consider adding such a feature if it doesn't exist yet.
The closest solution I can think of is to make 2 profiles. One profile has the normal left stick/right stick mappings. The other profile has the left stick mapped to the right X/Y axis and right stick mapped to the left X/Y axis. L1 will function as L1 but with additional special action to load the swapped profile when you're on the normal profile (and vice versa). I'm not sure if there's a way to get this to work only when you have L1 held.
Anyway, check out Ryochan7's repository, I'm sure you'll get a much better answer there.


When building from tag, use tag as application version

Inject tag into Cargo.toml.
Inject tag into artifact file names.

Done!
Build from a tag like v1.2.7 results in build version 1.2.7, and is published as a release.
Build with a different tag - or without any tag - results in build version 0.0.(travis_build_number), and is not published as a release.


Validation: description-missing fixes.

Added missing descriptions to fix validation errors.

Docs Build status updates of commit e26ff91:
:warning: Validation status: warnings

File
Status
Preview URL
Details

BingMaps/v8-web-control/map-control-concepts/rest-services-examples/index.md
:warning:Warning
View
Details

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/basic-polyline-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/polygon-events.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/polygons-with-holes-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/polyline-events.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/creating-custom-modules.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/implementing-modules.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/module-loading-methods.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/point-compression-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/anchoring-pushpins.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/changing-the-color-of-the-default-pushpin.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-base64-image-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-canvas-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-image-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-inline-svg-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-svg-file-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/default-pushpin-with-text-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/dynamically-create-svg-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/font-based-pushpins.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/image-and-canvas-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/pushpin-events-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/pushpin-hover-style.md
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.

BingMaps/v8-web-control/map-control-concepts/rest-services-examples/index.md

Line 235, Column 1: [Warning: sensitive-language-wl - See documentation] Term 'white list' is sensitive and should not be used in content or code. Usage: 'Angular 1.6 has changed how it handles JSONP. First off you need to white list the Bing Maps REST Services in your app config. Additionally, instead of using success and error fu'

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8d0f885:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/basic-polyline-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/polygon-events.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/polygons-with-holes-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/polyline-events.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/creating-custom-modules.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/implementing-modules.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/module-loading-methods.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/point-compression-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/anchoring-pushpins.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/changing-the-color-of-the-default-pushpin.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-base64-image-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-canvas-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-image-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-inline-svg-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-svg-file-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/default-pushpin-with-text-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/dynamically-create-svg-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/font-based-pushpins.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/image-and-canvas-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/pushpin-events-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/pushpin-hover-style.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/rest-services-examples/elevation-profiles.md
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 0a79a6d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/basic-polyline-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/polygon-events.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/polygons-with-holes-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/polyline-events.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/creating-custom-modules.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/implementing-modules.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/module-loading-methods.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/point-compression-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/anchoring-pushpins.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/changing-the-color-of-the-default-pushpin.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-base64-image-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-canvas-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-image-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-inline-svg-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-svg-file-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/default-pushpin-with-text-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/dynamically-create-svg-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/font-based-pushpins.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/image-and-canvas-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/pushpin-events-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/pushpin-hover-style.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/rest-services-examples/elevation-profiles.md
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@stevemunk @rbrundritt
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you’d like to see. Thank you!

Docs Build status updates of commit 01cc073:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/basic-polyline-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/polygon-events.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/polygons-with-holes-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/map-shapes-polylines-and-polygons/polyline-events.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/creating-custom-modules.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/implementing-modules.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/modular-framework/module-loading-methods.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/point-compression-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/anchoring-pushpins.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/changing-the-color-of-the-default-pushpin.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-base64-image-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-canvas-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-image-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-inline-svg-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/custom-svg-file-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/default-pushpin-with-text-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/dynamically-create-svg-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/font-based-pushpins.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/image-and-canvas-pushpin-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/index.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/pushpin-events-example.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/pushpins/pushpin-hover-style.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/map-control-concepts/rest-services-examples/elevation-profiles.md
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@stevemunk
I've implemented the requested changes. Please let me know if there are any other issues preventing approval and merge. Thank you, and have a great day!


Question: How to initially show Multiselect with Nuxt 3?

Hey, I'm using Multiselect with Nuxt 3. It's working fine, but the multiselect is popping up after a few seconds after the page has loaded. Is there a way to show it initially? I'm not sure if this belongs here or is rather a Nuxt question.
I'm using it like this:
multiselect.ts
import Multiselect from '@vueform/multiselect'
import<EMAIL_ADDRESS>
export default defineNuxtPlugin((nuxtApp) => {
    nuxtApp.vueApp.component("Multiselect", Multiselect)
})

<Multiselect
    v-model="selectedGoals"
    :options="goals"
    mode="tags"
    placeholder="Placeholder..."
    :close-on-select="false"
/>

Thankful for any help!

It's not a plugin, you just need to include it as a component:
<template>
  <div>
    <Multiselect v-model="value" v-bind="options" />
  </div>
</template>

<script>
import Multiselect from<EMAIL_ADDRESS>import<EMAIL_ADDRESS>
export default {
  components: {
    Multiselect,
  },
  data: () => ({
    value: null,
    options: {
      options: [1,2,3]
    }
  }),
}
</script>


Drop angular-language-server package

we need to wait for https://tracker.nixos.c3d2.de/?pr=350257

That was fast ;D


Operation not permitted when installing SASS

When installing SASS on my macbook, I keep a permission denied error. Example output:
Installing sass...
sudo gem install sass

ERROR:  While executing gem ... (Errno::EPERM)
    Operation not permitted - /usr/bin/sass

Hi @Paradoxis,
Thanks for reporting this issue.
It has been resolved in the following commit: https://github.com/guarinogabriel/Mac-CLI/commit/4033b5892e2f14cfc4ccb4ac637515c7ff50dfa7

Sweet, thanks