Implement Linuxkit images for Corda Doorman

Follow instructions to create doorman image
[https://innersource.accenture.com/projects/BLOI/repos/platform-kubernetes-corda/|https://innersource.accenture.com/projects/BLOI/repos/platform-kubernetes-corda/browse/charts/doorman/templates/deployment.yaml)]
From ambassador branch
Acceptance Criteria:
Create and upload image into docker registry.
Update readme/readthedocs for building image.

Closed by #68


Web - Can pay IOU with PayPal even if the recipient has no PayPal payment method

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Precondition: User A must not have a PayPal paypal method set.

On User A, make a money request to User B
On User B, observe that the PayPal payment method is available for paying this request
On User B, pay the request via PayPal
On User B, observe that the PayPal URL is incorrect

Expected Result:
The PayPal payment method should not be available.
Actual Result:
The PayPal payment method is available.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.46-1
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/181afbe9-f88f-4291-8892-f16ca1864c26
https://github.com/Expensify/App/assets/93399543/2cdde408-0d35-4afb-b3ff-1745156724b4
Expensify/Expensify Issue URL:
Issue reported by: @samh-nl
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690565339451529
View all open jobs on GitHub

Proposal by: @samh-nl
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1690565339451529
Proposal
Please re-state the problem that we are trying to solve in this issue.
Can pay IOU with PayPal even if the recipient has no PayPal payment method
What is the root cause of that problem?
This affects two usages of the SettlementButton component.

MoneyReportHeader: The shouldShowPayPal prop is used to determine whether Paypal is a valid payment method. However, we are checking whether the sender has a PayPal.me account configured instead of the recipient.
https://github.com/Expensify/App/blob/eb020063789091eb2e3086b5b54af3ead8436645/src/components/MoneyReportHeader.js#L62

ReportPreview:  We don't show a payment options list, instead the last used payment method is taken as default.
https://github.com/Expensify/App/blob/eb020063789091eb2e3086b5b54af3ead8436645/src/components/SettlementButton.js#L111

But in the case that this is PayPal, we don't check if the recipient actually has it configured:
https://github.com/Expensify/App/blob/eb020063789091eb2e3086b5b54af3ead8436645/src/components/SettlementButton.js#L125-L128
What changes do you think we should make in order to solve the problem?

We should check whether the recipient has a PayPal.me account configured in MoneyReportHeader:

const shouldShowPaypal = Boolean(moneyRequestReport.submitterPayPalMeAddress);

In ReportPreview, we should also define and pass the shouldShowPaypal prop to the SettlementButton. Consequently, we should add a condition to the if-statement to ensure shouldShowPaypal is true, so that otherwise the fallback to the payment method 'elsewhere' is used.

To reduce code duplicity in declaring shouldShowPaypal, we can add a util function in IOUUtils.
What alternative solutions did you explore? (Optional)
N/A

I don't think this is a bug. You should be able to pay anyone with PayPal

Confirming that bug exists. NewDot redirects to www.paypal.com/paypalme/{amount}{currency}. This is a significant bug with potential security implications, as it could result in funds being sent to the wrong individual.
Here is an example: https://www.paypal.com/paypalme/12PLN
@muttmuure I'm in favour of removing the option if the recipient doesn't have a PayPal payment method.
any thoughts/ideas?

I don't think we should remove the option, we want to encourage users to add their PayPal account

@muttmuure, Where NewDot should redirect if user 'A' presses pay with PayPal to user 'B' in case user 'B' doesn't have a PayPal account? Right now it redirects to the wrong person.

Yeah, actually, I can see what you mean.
Let's remove it if user B doesn't have one

Great! @samh-nl, your proposal looks good to me then.
:ribbon: :eyes: :ribbon: C+ reviewed

We are deprecating paypal (decision here, GH here) so closing this out, thanks!


Severity: 2
Message: preg_match(): Compilation failed: regular expression is too large at offset 63858
Filename: /srv/www/log_pixel/releases/20150326203504/system/database/DB_query_builder.php
Line: 2331

Line 2331 in DB_query_builder.php is the closing parenthesis for a preg_split() call (not a preg_match() one) and its regular expression is 19 characters long. This means is that you either have a quite outdated version of the file, or you've manually modified it.
The message itself however indicates that you've passed an unusually large string to some of the query build methods, and it is not made to work with such - you're better off with using raw queries.
Also, please provide more details next time and unless you are sure you've got a valid bug report, post your questions on the forums.

Thanks @narfbg for the reply.
I am currently using CI 3.0rc3 which is different than the current head.
https://github.com/bcit-ci/CodeIgniter/blob/4ccc2f80c501d839245915d058f77dea7f1bd3f3/system/database/DB_query_builder.php#L2331
if (($op = $this->_get_operator($conditions[$ci])) === FALSE
    OR ! preg_match('/^(\(?)(.*)('.preg_quote($op, '/').')\s*(.*(?<!\)))?(\)?)$/i', $conditions[$ci], $matches))
{
    continue;
}

I solved it using array_chunk to split the query. Shall I update the system/DB_query_builder.php to the current head?


Internal Maintenance Report - April 15, 2023

some bugs will be fe related (e.g. payment fails, fe will not understand but BE wouldnt apply the order)
some bugs might be BE related (idk like maybe demoting doesnt work or something) (or deleting user doesnt delete their products)

then on top of these check for minor issues:

for FE will be if you might get confused as a user or styling inconsistencies
for BE will be too long to get information (api call time), etc

Update this description with a detailed list of Functionalities their status and etc
Status Glossary is at the bottom of the report
MVP Feature Status Report

in the Misc Notes you can reference a newly made issue and link it. that issue would have the relevant info. Sometime the feature is fully functional but UI needs more helpful feedback. @jieunkxx @mgbalant @inside1D update the status glossary together and mention me once it's done

Functionality
Status
Misc. Notes
Tested By
Date Last Tested

Create product
Functional
design could be better

Delete product
Functional

???
Needs Urgent Fix
# issue number (make new issue)

# issue number (make new issue

Bonus and Stretch Feature Status Report

included ones in briefing and our own ones

Functionality
Status
Misc. Notes
Tested By
Date Last Tested

Create product
Functional
design could be better

Delete product
Functional

???
Needs Urgent Fix
# issue number (make new issue)

multiple images
not implemented
# issue number (make new issue) - be supports it only for now

Status Glossary

Status
Description

Functional
Everything is working as expected

Not Implemented
Hasn't been implemented

Not Planned
Hasn't been planned for now (e.g. fraudulent)

Urgent
Has critical bug or bugs and needs to be looked into ASAP

Minor
Has minor bug or bugs and should be looked into

...
Add any more statuses as needed

@armintalaie did we not do this one?


Raise an exception when filters' value isn't a list.

Why are the changes needed?

What changes were proposed in this pull request?

How was this patch tested?
Setup process

Ran a remote.recent_executions() with filters using list or other types.

from flytekit.configuration import Config
from flytekit.models.filters import ValueIn, Contains
from flytekit.remote import FlyteRemote

remote = FlyteRemote(
    Config.auto(config_file="/home/nelson/.flyte/config-sandbox.yaml"),
    default_project="flytesnacks",
    default_domain="development",
)

executions = remote.recent_executions(
        project="flytesnacks",
        domain="development",
        limit=1,
        filters=[
            ValueIn("phase", "RUNNING"),
        ],
)

Screenshots

Check all the applicable boxes

[x] I updated the documentation accordingly.
[x] All new and existing tests passed.
[ ] All commits are signed-off.

Related PRs

Docs link

Can you add a unit test?

@arbaobao This is not signed off yet. You can find instructions on how to sign off here: https://github.com/flyteorg/flytekit/pull/2576/checks?check_run_id=28277359939

@arbaobao there is a linting error, could you run make lint locally and push it again?


Eliminate the notion of a "bound signature" for opaque type archetypes.

The refactoring that moved the substitution of the outer environment
into an opaque type archeptype into the generic environment eliminated
the need for the bound signature entirely, so remove it.

@swift-ci please smoke test


"Failed to parse manifest" on bootloader-0.10.0-alpha-03

Not sure what's going wrong here, cargo doc works locally. The crate doesn't show up in the web UI at all.
Feb 21 12:36:47 docsrs cratesfyi[28601]: 2021/02/21 12:36:47 [ERROR] docs_rs::build_queue: Failed to build package bootloader-0.10.0-alpha-03 from queue: failed to parse maniest
Feb 21 12:36:47 docsrs cratesfyi[28601]: Backtrace:    0: failure::backtrace::internal::InternalBacktrace::new
Feb 21 12:36:47 docsrs cratesfyi[28601]:    1: <failure::backtrace::Backtrace as core::default::Default>::default
Feb 21 12:36:47 docsrs cratesfyi[28601]:    2: rustwide::build::BuildBuilder::run
Feb 21 12:36:47 docsrs cratesfyi[28601]:    3: docs_rs::docbuilder::rustwide_builder::RustwideBuilder::build_package
Feb 21 12:36:47 docsrs cratesfyi[28601]:    4: docs_rs::build_queue::BuildQueue::process_next_crate
Feb 21 12:36:47 docsrs cratesfyi[28601]:    5: <std::panic::AssertUnwindSafe<F> as core::ops::function::FnOnce<()>>::call_once
Feb 21 12:36:47 docsrs cratesfyi[28601]:    6: docs_rs::utils::queue_builder::queue_builder
Feb 21 12:36:47 docsrs cratesfyi[28601]:    7: std::sys_common::backtrace::__rust_begin_short_backtrace
Feb 21 12:36:47 docsrs cratesfyi[28601]:    8: core::ops::function::FnOnce::call_once{{vtable.shim}}
Feb 21 12:36:47 docsrs cratesfyi[28601]:    9: <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once
Feb 21 12:36:47 docsrs cratesfyi[28601]:              at /rustc/d3fb005a39e62501b8b0b356166e515ae24e2e54/src/liballoc/boxed.rs:1076
Feb 21 12:36:47 docsrs cratesfyi[28601]:       <alloc::boxed::Box<F> as core::ops::function::FnOnce<A>>::call_once
Feb 21 12:36:47 docsrs cratesfyi[28601]:              at /rustc/d3fb005a39e62501b8b0b356166e515ae24e2e54/src/liballoc/boxed.rs:1076
Feb 21 12:36:47 docsrs cratesfyi[28601]:       std::sys::unix::thread::Thread::new::thread_start
Feb 21 12:36:47 docsrs cratesfyi[28601]:              at /rustc/d3fb005a39e62501b8b0b356166e515ae24e2e54/src/libstd/sys/unix/thread.rs:87
Feb 21 12:36:47 docsrs cratesfyi[28601]:   10: start_thread
Feb 21 12:36:47 docsrs cratesfyi[28601]:   11: __clone

This is coming from the docsrs_metadata crate:
Error: Building documentation failed

Caused by:
    failed to parse manifest

Stack backtrace:
   0: failure::backtrace::internal::InternalBacktrace::new
             at /home/joshua/.local/lib/cargo/registry/src/github.com-1ecc6299db9ec823/failure-0.1.8/src/backtrace/internal.rs:46
   1: failure::backtrace::Backtrace::new
             at /home/joshua/.local/lib/cargo/registry/src/github.com-1ecc6299db9ec823/failure-0.1.8/src/backtrace/mod.rs:121
   2: <failure::error::error_impl::ErrorImpl as core::convert::From<F>>::from
             at /home/joshua/.local/lib/cargo/registry/src/github.com-1ecc6299db9ec823/failure-0.1.8/src/error/error_impl.rs:19
   3: <failure::error::Error as core::convert::From<F>>::from
             at /home/joshua/.local/lib/cargo/registry/src/github.com-1ecc6299db9ec823/failure-0.1.8/src/error/mod.rs:36
   4: docs_rs::docbuilder::rustwide_builder::RustwideBuilder::build_package::{{closure}}
             at src/docbuilder/rustwide_builder.rs:310

https://github.com/rust-lang/docs.rs/blob/ba9364b935e2ef1c9b925f4295d42fd03b9587dd/src/docbuilder/rustwide_builder.rs#L310
There are two bugs here:

The error message should be showing the parse error as a cause. Not sure what's wrong there, the thiserror docs say that #[from] implies #[source] but that doesn't seem to be the case.
We fail to parse valid toml files:

failed to parse manifest: unexpected character found: `<` at line 3 column 1

Which is very strange because it doesn't have a < character except for an email address:

[[bin]]
name = "builder"
required-features = ["builder"]

[[bin]]
name = "runner"
required-features = ["runner"]

[[bin]]
name = "bios"
required-features = ["bios_bin"]

[[bin]]
name = "uefi"
required-features = ["uefi_bin"]
[build-dependencies.llvm-tools-build]
optional = true
package = "llvm-tools"
version = "0.1"

[build-dependencies.serde]
features = ["derive"]
optional = true
version = "1.0"

[build-dependencies.toml]
optional = true
version = "0.5.1"
[dependencies.anyhow]
optional = true
version = "1.0.32"

[dependencies.argh]
optional = true
version = "0.1.3"

[dependencies.bit_field]
optional = true
version = "0.10.0"

[dependencies.conquer-once]
default-features = false
optional = true
version = "0.2.1"

[dependencies.displaydoc]
optional = true
version = "0.1.7"

[dependencies.fatfs]
optional = true
version = "0.3.4"

[dependencies.font8x8]
default-features = false
features = ["unicode"]
optional = true
version = "0.2.5"

[dependencies.gpt]
optional = true
version = "2.0.0"

[dependencies.json]
optional = true
version = "0.12.4"

[dependencies.llvm-tools]
optional = true
version = "0.1.1"

[dependencies.log]
optional = true
version = "0.4.8"

[dependencies.rsdp]
optional = true
version = "1.0.0"

[dependencies.spinning_top]
optional = true
version = "0.2.1"

[dependencies.thiserror]
optional = true
version = "1.0.20"

[dependencies.uefi]
optional = true
version = "0.7.0"

[dependencies.usize_conversions]
optional = true
version = "0.2.0"

[dependencies.x86_64]
optional = true
version = "0.13.2"

[dependencies.xmas-elf]
optional = true
version = "0.6.2"

[features]
binary = ["llvm-tools-build", "x86_64", "toml", "xmas-elf", "usize_conversions", "log", "conquer-once", "spinning_top", "serde"]
bios_bin = ["binary", "vga_320x200", "rsdp"]
builder = ["argh", "thiserror", "displaydoc", "anyhow", "llvm-tools", "json", "fatfs", "gpt"]
default = []
map_physical_memory = []
recursive_page_table = []
runner = ["anyhow"]
uefi_bin = ["binary", "uefi", "font8x8"]
vga_320x200 = ["font8x8"]

[package]
authors = ["Philipp Oppermann<EMAIL_ADDRESS>build = "build.rs"
description = "An experimental pure-Rust x86 bootloader."
edition = "2018"
license = "MIT/Apache-2.0"
name = "bootloader"
repository = "https://github.com/rust-osdev/bootloader"
version = "0.10.0-alpha-03"
[package.metadata.bootloader]
build-std = "core"
target = "x86_64-bootloader.json"
[package.metadata.docs.rs]
default-target = "x86_64-unknown-linux-gnu"
features = ["recursive_page_table", "map_physical_memory"]

[package.metadata.release]
disable-publish = true
no-dev-version = true
pre-release-commit-message = "Release version {{version}}"

[[package.metadata.release.pre-release-replacements]]
exactly = 1
file = "Changelog.md"
replace = "# Unreleased\n\n# {{version}} – {{date}}"
search = "# Unreleased"
[profile.dev]
panic = "abort"

[profile.release]
debug = true
lto = false
overflow-checks = true
panic = "abort"

Uhhh apparently merge conflict markers got in there? Unsure if this is actually a docs.rs bug, it's strange that what it's trying to parse isn't the same as the file copied though:
2021/06/12 13:26:12 [INFO] rustwide::prepare: tweaked toml for crates.io crate bootloader 0.10.0-alpha-03 written to .workspace/builds/bootloader-0.10.0-alpha-03/source/Cargo.toml
2021/06/12 13:26:12 [INFO] rustwide::prepare: crate crates.io crate bootloader 0.10.0-alpha-03 already has a lockfile, it will not be regenerated
2021/06/12 13:26:12 [INFO] rustwide::cmd: running `Command { std: "/home/joshua/src/rust/docs.rs/.workspace/cargo-home/bin/cargo" "+nightly" "fetch" "--locked" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[crates/metadata/lib.rs:297] manifest = "[package]
name = "bootloader"
<<<<<<< HEAD
version = "0.10.0-alpha-01"
=======
version = "0.9.12"
>>>>>>> main

Apparently .orig has the conflict markers but .toml does not; seems like this might be a rustwide bug? cc @pietroalbini
Anyway, I think this can be closed on the docs.rs side as a duplicate of https://github.com/rust-lang/docs.rs/issues/797.

Huh why are we caring about the .orig? Only .toml should be parsed by Rustwide and docs.rs...

https://github.com/rust-lang/docs.rs/blob/803cebf3bebf09247d568f2671604c033d6518bf/crates/metadata/lib.rs#L169-L170
So not rustwide related, I'm not sure why we prefer the .orig here, the only difference normally is stripped dev-dependencies which don't matter for a doc build.

https://github.com/rust-lang/docs.rs/commit/8cd6725ad4ac2d84c8be648991e7b31cbc25f101
I don't see any rationale for why we do, I think it would make sense to change this to ignore the .orig file.

That seems fine, but the bug I mean is that rustwide strips conflict markers, that doesn't seem right.

Or I guess maybe it's cargo doing it? Something is fishy.

Yeah, it must have been whatever was used to publish the crate (which was likely cargo), it's in the tarball nothing to do with what we're doing on our end:
> cargo download -x bootloader==0.10.0-alpha-03 && rg '<<<<<'
INFO: cargo-download v0.1.2
INFO: Crate `bootloader==0.10.0-alpha-03` downloaded successfully
INFO: Crate content extracted to ./bootloader-0.10.0-alpha-03/
bootloader-0.10.0-alpha-03/Cargo.lock.orig
64:<<<<<<< HEAD

bootloader-0.10.0-alpha-03/Cargo.toml.orig
3:<<<<<<< HEAD
39:<<<<<<< HEAD

Disappointingly it doesn't appear that the version of cargo used to build the tarball is recorded anywhere, if I move Cargo.toml.orig over the Cargo.toml and try cargo package with current and a year-and-a-half old nightly they both fail to parse the manifest, so I have no idea how it got published.

Ok cool, I'll reopen this to track parsing Cargo.toml instead of Cargo.toml.orig.


Something is potentially cycling ?

Hi i just dont want to straightly report it as an issue, but we have some huge performance problems with sphere and yet we didnt found why. It is finally on our LIVE server.
I jsut want to collaborate or ask for any informations from your experiences...
After start, sphere is running awesome for i would say like, 10 hours minimally and more, but after for example 15 or 20 hours, the sphere start lagging pretty badly. Only restart sphere will help again for same time cycle.
The lags are in weird intervals, intervals are more and more frequent. For example 20seconds OK, then huge lag for 1-2s, then again 20 seconds nothing and again lag.
Then it is 10 seconds OK, and lag. At the end of the cycle when restart is needed, it is lagging like 5s OK and then lag.
What should we do ? We tried to stop every HC script, check if anything is cycling, check some console dumps to check but nothing special to say told whats wrong.
Thank you for any idea or suggestion.

Any clue with the profiler?

Closing, since after some tests it was more a script problem than a sphere one (even if some optimization on sphere side, regarding script parsing, is needed).


Bump bottlerocket OVA version to latest

Bump Bottlerocket version to their latest release.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve


Split code in src folder into multiple files.

@incuna/frontend
please review
for
https://incuna-pm.atlassian.net/browse/IRD-2
tests are failing as there is no travis yaml. that will come in another pr.

linting is done in another pr which passes

We'll also need to add an ngtemplates task if we are splitting the templates out so that they can be included in a JS file which still uses the $templateCache

There will be more prs to make a dist file and compile the templates.

👍


Remove variable usage from proxy_pass directive to fix resolution issues

This change addresses issues described in issue #4102, where users experienced 404 errors and misconfigurations due to dynamic URL resolution failures. By switching to static values for backend addresses, this ensures more stable and predictable behavior when routing requests through the proxy.

When this fix will be released?

@mitossoft-rd , any news when this fix will be released?

bump

@jc21, when this fix will be released?
This bug renders proxy manager useless.


Adding/enabling new tools for existing agents

Is your feature request related to a problem? Please describe.
I'm trying to use a MemGPT agent as an assistant for myself. In order to do that, I need to now start adding tools that can help it do different things such as read all the contents of a file (not just first 500 chars), delete a file etc.  I added the tool for reading all the contents of a text file (read_full_text_file) based on the docs but for some reason the agent is not able to use that tool and errors out with "Error: No function named read_full_text_file"
I even tried manually updating the function_schemas column associated with the preset that is associated with the agent in the Postgres DB but that didn't make a difference 😦
Describe the solution you'd like
A simple way to provide existing agents access to new tools that get added.

It used to be possible! Before we went all cough over-normalized db mad! ;)
Sarah, is it still possible manually? What if we edit the state, too?
Hitarth, horrible evil hack, but what I have done in a pinch is to take an existing function, conversation_search_date or something that doesn't get used much, and slam my function in there. Directly into /path/to/memgpt/memgpt/functions/function_sets/base.py. It ain't pretty and you need a smart LLM to roll with it but it does work-ish :D

Yes should be possible if you edit the dictionary inside of AgentState.state["functions"] https://github.com/cpacker/MemGPT/blob/main/memgpt/agent.py#L1055


package-dockertested: skopeo version skew breaks pre-flight checks

We install docker using the rhel7next* suite of repos, which are synced from the latest RHEL 7 Extras compose in Brew. During this process, recently we are bringing in skopeo-containers as a dependency:
$ sudo yum --disablerepo=\* --enablerepo=rhel7next\* install docker
Loaded plugins: amazon-id, rhui-lb, search-disabled-repos
Resolving Dependencies
--> Running transaction check
---> Package docker.x86_64 2:1.12.6-32.git88a4867.el7 will be installed
--> Processing Dependency: docker-client = 2:1.12.6-32.git88a4867.el7 for package: 2:docker-1.12.6-32.git88a4867.el7.x86_64
--> Processing Dependency: docker-common = 2:1.12.6-32.git88a4867.el7 for package: 2:docker-1.12.6-32.git88a4867.el7.x86_64
--> Processing Dependency: docker-rhel-push-plugin = 2:1.12.6-32.git88a4867.el7 for package: 2:docker-1.12.6-32.git88a4867.el7.x86_64
--> Processing Dependency: container-selinux >= 2:2.12-2 for package: 2:docker-1.12.6-32.git88a4867.el7.x86_64
--> Processing Dependency: oci-register-machine >= 1:0-3.10 for package: 2:docker-1.12.6-32.git88a4867.el7.x86_64
--> Processing Dependency: oci-systemd-hook >= 1:0.1.4-9 for package: 2:docker-1.12.6-32.git88a4867.el7.x86_64
--> Processing Dependency: skopeo-containers for package: 2:docker-1.12.6-32.git88a4867.el7.x86_64
--> Processing Dependency: libseccomp.so.2()(64bit) for package: 2:docker-1.12.6-32.git88a4867.el7.x86_64
--> Running transaction check
---> Package container-selinux.noarch 2:2.15-1.git583ca40.el7 will be installed
---> Package docker-client.x86_64 2:1.12.6-32.git88a4867.el7 will be installed
---> Package docker-common.x86_64 2:1.12.6-32.git88a4867.el7 will be installed
---> Package docker-rhel-push-plugin.x86_64 2:1.12.6-32.git88a4867.el7 will be installed
---> Package libseccomp.x86_64 0:2.3.1-2.el7 will be installed
---> Package oci-register-machine.x86_64 1:0-3.11.gitdd0daef.el7 will be installed
---> Package oci-systemd-hook.x86_64 1:0.1.7-4.gite533efa.el7 will be installed
--> Processing Dependency: libyajl.so.2()(64bit) for package: 1:oci-systemd-hook-0.1.7-4.gite533efa.el7.x86_64
---> Package skopeo-containers.x86_64 1:0.1.20-2.el7 will be installed
--> Running transaction check
---> Package yajl.x86_64 0:2.0.4-4.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

===================================================================================================================================================
 Package                                 Arch                   Version                                     Repository                        Size
===================================================================================================================================================
Installing:
 docker                                  x86_64                 2:1.12.6-32.git88a4867.el7                  rhel7next-extras                  14 M
Installing for dependencies:
 container-selinux                       noarch                 2:2.15-1.git583ca40.el7                     rhel7next-extras                  29 k
 docker-client                           x86_64                 2:1.12.6-32.git88a4867.el7                  rhel7next-extras                 3.3 M
 docker-common                           x86_64                 2:1.12.6-32.git88a4867.el7                  rhel7next-extras                  76 k
 docker-rhel-push-plugin                 x86_64                 2:1.12.6-32.git88a4867.el7                  rhel7next-extras                 1.5 M
 libseccomp                              x86_64                 2.3.1-2.el7                                 rhel7next                         56 k
 oci-register-machine                    x86_64                 1:0-3.11.gitdd0daef.el7                     rhel7next-extras                 1.0 M
 oci-systemd-hook                        x86_64                 1:0.1.7-4.gite533efa.el7                    rhel7next-extras                  30 k
 skopeo-containers                       x86_64                 1:0.1.20-2.el7                              rhel7next-extras                 7.9 k
 yajl                                    x86_64                 2.0.4-4.el7                                 rhel7next                         39 k

Transaction Summary
===================================================================================================================================================
Install  1 Package (+9 Dependent packages)

This means when we run pre-flight checks in the installer that try to install and use skopeo, they need to be grabbing the bleeding edge version from the rhel7next* repositories as well, otherwise they fail like so:
    Failure summary:

      1. Host:     localhost
         Play:     Verify Requirements
         Task:     openshift_health_check
         Message:  One or more checks failed
         Details:  check "docker_image_availability":
                   Some dependencies are required in order to check Docker image availability.
                   Error: Package: 1:skopeo-0.1.19-1.el7.x86_64 (oso-rhui-rhel-server-extras)
                              Requires: skopeo-containers = 1:0.1.19-1.el7
                              Installed: 1:skopeo-containers-0.1.20-2.el7.x86_64 (@rhel7next-extras)
                                  skopeo-containers = 1:0.1.20-2.el7
                              Available: 1:skopeo-containers-0.1.17-0.7.git1f655f3.el7.x86_64 (oso-rhui-rhel-server-extras)
                                  skopeo-containers = 1:0.1.17-0.7.git1f655f3.el7
                              Available: 1:skopeo-containers-0.1.17-1.el7.x86_64 (oso-rhui-rhel-server-extras)
                                  skopeo-containers = 1:0.1.17-1.el7
                              Available: 1:skopeo-containers-0.1.18-1.el7.x86_64 (oso-rhui-rhel-server-extras)
                                  skopeo-containers = 1:0.1.18-1.el7
                              Available: 1:skopeo-containers-0.1.19-1.el7.x86_64 (oso-rhui-rhel-server-extras)
                                  skopeo-containers = 1:0.1.19-1.el7

    The execution of "/usr/share/ansible/openshift-ansible/playbooks/byo/config.yml"
    includes checks designed to fail early if the requirements
    of the playbook are not met. One or more of these checks
    failed. To disregard these results, you may choose to
    disable failing checks by setting an Ansible variable:

       openshift_disable_check=docker_image_availability

    Failing check names are shown in the failure details above.
    Some checks may be configurable by variables if your requirements
    are different from the defaults; consult check documentation.
    Variables can be set in the inventory or passed on the
    command line using the -e flag to ansible-playbook.

We should probably add a oct prepare skopeo command (oct should be well-formed for this, but maybe we want a more generic oct prepare package?). Then, we need to add logic to the package-dockertested job to install skopeo from rhel7next* with the new command, as it does for docker. Furthermore, we need to update the call to the update-dockertested-repo.sh script to add to the dockertested repo the package containing skopeo. Then, we can finally update the job configuration for ami_build_origin_int_rhel_base so that new base AMIs will install the correct version of skopeo.

@sosiouxme @rhcarvalho please triage this. Today, fixing this issue is a blocker for  getting new versions of Docker into the CI stream, so if you feel like you will not have the bandwidth to tackle it this week we can just turn off the check.

I can make a PR to disable this check for now to unblock testing with rhel7next docker.
Who has been driving getting rhel7next docker into use in CI? It seems like it would be way more efficient for them to update that to pull in rhel7next skopeo as well than for me to try to figure out how to do everything @stevekuznetsov described above. And it feels like a better owner for this problem - we're just trying to consume skopeo and don't care how it gets there.

This job and the workflow above are the mechanism for getting the latest docker into our CI. We can't install from rhel7next* on the normal CI AMIs as any repo we install from we basically need to always remain on for the future, and we cannot safely rely on the latest Extras compose. This is why the package-dockertested job exists to take the bleeding edge docker, test it, and when it's safe, tag it into the tested repository for consumption by the normal CI AMIs.

What if rather than trying to chase dependencies the test job pulls from a candidate rhel7next and once tests pass it then publishes that repo to a location that's used by jobs and that repo is left enabled in the AMI? The test process would need to use an alternate location but same reponame and be sure to clear its caches before sealing the image.

You mean instead of promoting specific packages like we do today, instead promote the entire rhel7next* ecosystem all together? We have some cards to build such a system but just have not had time to think it all through yet.

We can scrum about who'll take on the CI updates. /cc @brenton
@juanvallejo feel like getting to know our CI better? :-P

@stevekuznetsov ... or mirror the repo locally to the AMI and then make the repo definition point at the local filesystem. Not sure how large the repo is or if there are any limits on the ami size.

Discussed with @sosiouxme on IRC that we can keep the docker_image_availability disabled for the dockertested job.
Unless anybody plans to work on the discussed solution involving yum repos, this issue can be closed.

@rhcarvalho the check will need to be disabled for all jobs as when we have the newer docker installed, it will have the same conflict with skopeo-containers and the check will not be able to install skopeo from non-bleeding edge repos. If you guys want this check to be running, this is a hard pre-requisite.

Actually as per this build info it looks like the %requires from Docker to skopeo-containers is not versioned, so we might be able to get away with version skew between the two packages. @lsm5 @runcom or @rhcarvalho I feel like we need to understand the dependency between these two packages better to know if we are going to be OK tolerating this skew or, as above, we are going to want to bring in skopeo from the newest compose as well


Inclusion of the new efficient algorithm for preparing uniform quantum superposition states.

What should we add?
Recently a novel efficient algorithm was proposed for preparation of uniform quantum superposition states, which was published in Quantum Information Processing journal. The algorithm tries to solve the problem of preparation of a uniform superposition state of the form
$$ | \psi> = \frac{1}{\sqrt{M}}  \sum_{j=0}^{M-1} |j>, $$
where $M$ denotes the number of distinct states in the superposition state and $2 ≤ M ≤ 2^n$ . They also show that the superposition state can be efﬁciently prepared, using a deterministic approach, with a gate complexity and circuit depth of only $O(log_2 M)$ for all $M$. This demonstrates an exponential reduction in gate complexity in comparison with other existing deterministic approaches (including qiskit's) in the literature for the general case of this problem. Another advantage of the proposed approach is that it requires only $n =\lceil log 2 M \rceil$ qubits. Furthermore, neither ancilla qubits nor any quantum gates with multiple controls are needed in their approach for creating the uniform superposition state $|\psi>$.
Below I have provided the implementation of this algorithm.
import numpy as np
from qiskit import QuantumCircuit , QuantumRegister
""" Input: A positive integer M with 2 < M < 2^n, M not equal to 2^r for any natural number r.
Output: A quantum circuit that creates the uniform superposition state:
$\frac{1}{\sqrt{M}} \sum_{j=0}^{M-1} \ket{j} $. Number of qubits: Using n = np.ceil(np.log2(M)), creates the uniform superposition state with the least number of qubits.
"""
def uniform_superposition(M, n):
    N = [int(x) for x in list(np.binary_repr(M))][::-1]
    k = len(N)
    L = [index for (index ,item) in enumerate(N) if item ==1] #Locations of '1's
    qreg = QuantumRegister(n, 'q')
    quantum_circuit = QuantumCircuit(qreg)
    quantum_circuit.x(qreg[L[1:k]])
    Mcurrent = 2**(L[0])
    theta = -2*np.arccos(np.sqrt(Mcurrent/M))
    if L[0]>0: #if M is even
        quantum_circuit.h(qreg[0:L[0]])
    quantum_circuit.ry(theta , qreg[L[1]])
    quantum_circuit.ch(qreg[L[1]], qreg[L[0]:L[1]], ctrl_state='0')
    for m in range(1,len(L) -1):
        theta = -2*np.arccos(np.sqrt (2**L[m]/ (M- Mcurrent)))
        quantum_circuit.cry(theta , qreg[L[m]], qreg[L[m+1]], ctrl_state='0')
        quantum_circuit.ch(qreg[L[m+1]], qreg[L[m]:L[m+1]], ctrl_state='0')
        Mcurrent = Mcurrent + 2**(L[m])
    return quantum_circuit

The research paper used for creating this algorithm.
-- [An efficient quantum algorithm for preparation of uniform quantum superposition states][1]
[1]: Shukla, A., Vedula, P. An efficient quantum algorithm for preparation of uniform quantum superposition states. Quantum Inf Process 23, 38 (2024). https://doi.org/10.1007/s11128-024-04258-4

Looks interesting - Qiskit has some state preparation logic eg in the circuit library here https://github.com/Qiskit/qiskit/tree/main/qiskit/circuit/library/data_preparation where perhaps it might suited to make it available via Qiskit. Maybe open an issue there to see if there's interest at that level in having something like this functionality in the circuit library.

Thanks for the suggestion, @woodsp-ibm. I'll add an issue there. Do you want me to tag you there?

Thanks, I'dd add a cross-ref the issue in Qiskit is

Qiskit/qiskit#11735

Me adding the reference will show up in the Qiskit issue so people following the link will see this conversation here.

Sounds good, thank you!

As this has been raised now on Qiskit for potential inclusion into the circuit library, where it seems more applicable I am going to close this issue here now.


polymer_expressions should support Bindable

This issue was originally filed by @jolleekin

FACTS

PathObserver uses '.' to separate path segments
PathObserver is supposed to support map indexer
PathObserver converts path segments into integer or Symbol.

PROBLEMS
    import 'package:observe/observe.dart';
    var model = new ObservableMap.from({
      '123': 'does not work as key is intepreted as a List index',
      '!@#': 'does not work as key contains invalid characters for a Symbol',
      'a.b': 'does not work as key contains "."',
      '[]=': 'does not work although key is a valid Symbol pattern (an operator)!!!',
      'abc': 'works as key a valid Symbol pattern',
      'var': 'works although key is not a valid Symbol pattern (it is a keyword)!!!'
    });
    main() {
      for (var key in model.keys) {
        var obs = new PathObserver(model, key);
        print(new Symbol(key));
        obs.changes.listen((_) {
          print('model["$key"] changed to "${obs.value}"');
        });
      }
      for (var key in model.keys) {
        model[key] = 'Dart';
      }
    }
PRODUCT VERSION

package observe v0.9.3

This issue has been moved to dart-lang/polymer-dart#493.


Update 3D&T_ALPHA.html

Ajuste de cor de fonte pra o melhor visualização no Darkmode
Changes / Comments
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


webContents: providing dom-ready event

Fixes #1504

Should the readyState of the document be interactive or complete during this event ? Coz its interactive during domcontentloaded but it will be complete here. Plus this event is equal to loading content scripts at document_end. If you need the event to be fired as soon as window.document is available then the method has to changed.
/cc @sindresorhus @zcbenz

I would like it to be interactive to match DOMContentLoaded.
Could maybe have another event for complete, to match Chrome extension's document_start and document_end.

@sindresorhus have added test and works as expected, i forgot to test with sub resources yesterday.
@zcbenz i wrote the test based on an external resource which is bad, any other option to test ? Or do i remove it.

Fixed test with local server.

Thanks!

@deepak1556 Nice work! Thanks for implementing :)


Add Product Vision Meetings

To improve focus and collaboration it would be helpful to add a recurring meeting to focus on product vision and strategy. This will help us understand what our priorities are and align our efforts.
This is from the areas we would like to improve from the Retro: April 15, 2022

Meeting Agenda & Notes (HackMD)

Meeting Link


Feature request: Automatically read library or binary from folder

Problem
Currently, the documentation states that we can provide our own path for the query engine library or binary using the environment variables:

PRISMA_QUERY_ENGINE_LIBRARY
PRISMA_QUERY_ENGINE_BINARY

But if we provide the value to these variables as a path to a location in the disk where these files are stored rather than the file itself, then Prisma is unable to ratify that and throws an UnhandledException.
Suggested solution

Prisma should check the value for the above environment variables
Determine if it is a directory or not
If it is a directory, then it should try to find one of the listed targets in the mentioned folder
If not, directly try to consume the file

Figuring out the file is not possible and far to magic.
What we can do, is to throw an error if you point to a directory instead of a file - which will surface it to you that you should point to a file and not a directory.
Can you create a feature request for that error message instead? Thanks.

I don't understand why it is not possible since the current error message anyway tells me what my current OS target is, and whether it is a library or a binary that it couldn't find.
This is simply an enhancement on it which is as simple as:
path.existsSync(config.resolvedQueryEngine)

The env var is supposed to point to a file, and that file can be named whatever you want. There is no need to follow the same naming pattern. So just assuming the name when the env var points to a folder might lead to unexpected files to be used instead of what was originally desired. As it would also be magic and behind the scenes, that would be a nightmare to debug.


I can't seem to find how to open the actual game itself

Please check for duplicates, similar issues or closed issues with the same problem, as well performing simple troubleshooting steps (such as deleting the export folder if it's an issue with compiling, reinstalling Kade Engine) before submitting an issue.
If you are playing a downloaded version of the game, what operating system are you using?
Windows (x86), Windows (x86_64), Linux, or macOS? Specify below.
What version of the game are you using? Look in the bottom left corner of the main menu.
Have you identified any steps to reproduce the bug? If so, please describe them below. Use images if possible.
Please describe your issue. Provide extensive detail and images if possible.

What is the issue?

Maybe you need to build game firstly?

This is not an issue. This is a discussion


Added more examples and explanations to the notebook

example.ipynb

About this:

One thing, it might be worth describing what's inside the query reply object; it's printed out in the notebook but users may be confused as to where the SQL version of their query is coming from.

I'm hesitant to add more text since I already feel like the notebook is crowded with explanations. Maybe that document about APIs and usage is the right place for this.


out_file: Avoid performing multi-worker check in configure()

Which issue(s) this PR fixes:
Fixes #3941
What this PR does / why we need it:
The check did not work well with `<worker 0-N>` directive for
the following reasons:

 * When Fluentd starts up, supervisor performs sanity check on
   configuration by creating actual instances of plugins.

 * This check precedes SeverModule, which prepares various assets
   for workers (lockdir, RPC endpoints and shared sockets etc.)

 * Fluent::Plugin::Base dynamically overrides `system_config.workers`
   during start-up, and leaves the value > 1 only when `<worker 0-N>`
   directive is used.

Fix this issue by avoiding faulty sanity check in `configure()`.

Signed-off-by: Fujimoto Seiji<EMAIL_ADDRESS>
Docs Changes:
N/A
Release Note:
out_file: Fix the multi-worker check with <worker 0-N> directive

@ashie Can you check this PR before the next release? If it looks good,
I want to included this in td-agent v4.4.2 along with #3939.

Fluent::Plugin::Base dynamically overrides system_config.workers
during start-up, and leaves the value > 1 only when <worker 0-N>
directive is used.

https://github.com/fluent/fluentd/blob/a7771835d65dea8e49d284a148d94cecb1abed19/lib/fluent/plugin/base.rb#L56-L62

conf.target_worker_ids is set only when <worker 0-N> is used:
https://github.com/fluent/fluentd/blob/a7771835d65dea8e49d284a148d94cecb1abed19/lib/fluent/root_agent.rb#L78-L121

When <worker 0-N> isn't specified system_config.workers is 1 on sanity check of supervisor so that this check doesn't return error.

Thanks!

Thanks for the fix!


HasKey and runtime created anon type for key

I have an application where I need to define entity types at runtime.
I have code running that creates entity types and I can build models derived from DbContext etc. and it all works to retrieve data from an Oracle database as long as I have non-composite keys.
I use reflection to create the equivalent of this in my OnMOdelCreating()
modelBuilder.Entity()
.HasKey(e => e.property);
The defintion of .HasKey is
public EntityTypeConfiguration HasKey(
Expression<Func<TEntityType, TKey>> keyExpression)
My code work fine for non-composite keys since I know the type of e.property and can use it to create the appropriate .HasKey at runtime and then invoke it with a dynamic lambda expression I have created.
I would like to use reflection to create the equivalent of this composite key:
modelBuilder.Entity()
.HasKey(e => new { e.stringProperty, e.datetimeProperty});
So in the composite case TKey is
anon {System.String. System.DateTime}
If I can find a way to use reflection to create the TKey for the anonymous type and build the appropriate lambda expression, will EF allow me to do this since my anonymous type TKey is transient and only exists while I am in OnModelCreating()?

EF Team Triage: This issue is not something that our team is planning to address in the EF6.x code base.  This does not mean that we would not consider a community contribution to address this issue.
Moving forwards, our team will be fixing bugs, implementing small improvements, and accepting community contributions to the EF6.x code base. Larger feature work and innovation will happen in the EF Core code base (https://github.com/aspnet/EntityFramework).
Closing an issue in the EF6.x project does not exclude us addressing it in EF Core. In fact, a number of popular feature requests for EF have already been implemented in EF Core (alternate keys, batching in SaveChanges, etc.).
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.

cc @anpete who has an idea for a workaround


implementation of whey

thx for releasing your code, but I have a question that in your paper, Whey Optimization is to divide noises into groups, I read your code roughly, I think your whey implementation is to divide into groups by pixel values 0 - 255, do I understand correctly?And I don't find the T1 pram settings. By the way, your whey step2, squeeze noises stochastically, I don't find the implementation in your released code.

Sorry, I've updated the code in the targeted attack. We've improved the algorithm, here is the best.

thx for releasing your code, but I have a question that in your paper, Whey Optimization is to divide noises into groups, I read your code roughly, I think your whey implementation is to divide into groups by pixel values 0 - 255, do I understand correctly?And I don't find the T1 pram settings. By the way, your whey step2, squeeze noises stochastically, I don't find the implementation in your released code.

Sorry, I've updated the code in the targeted attack. We've improved the algorithm in the grouping strategy.


Not finding Google Play services even on emulators and devices with Google Play services is installed

Having trouble getting the Pushio Manager to register the app on Android because of the below error where it can not find Google Play services.
D/PluginManager: init()
V/pushio-cordova: Initializing plugin
I/pushio: Push IO Manager - 6.47
E/pushio: PIORegM dNS Google Play services library not found.
E/pushio: PIORegM dNS This library is a required dependency as of PushIO SDK 2.11.0
W/pushio: PIORegM dNS Google Play services not found. Trying ADM.
W/pushio: PIORegM dNS ADM not found.
W/pushio: PIORegM dNS Device supports no known notification services.
Have the plugin installed in a project with the following settings:
Cordova CLI 10.0.0
Cordova Android 9.0.0
Android SDK Tools 30.0.3
minSdkVersion 22
targetSdkVersion 29
Have tested on:
Nexus 5X SDK 27
Pixel 4 SDK 30

Please try adding the following dependency in android/app/build.gradle
implementation 'com.google.firebase:firebase-messaging:17.3.0'


add tcpdump and netstat to debug base image

Jenkins job manager/presubmit passed

Jenkins job manager/presubmit passed


Doesn't work in windows cmd prompt

Documentation says "On Windows, we suggest you use an improved command line tool such as cmder or PowerShell to improve the experience."
That implies to me that it would at least work in the windows cmd prompt, I would change documentation to state the the usage of tools such as cmder or PowerShell are a necessity or change the code to make it run in windows cmd prompt as well.
The specific step that doesn't work is the shell:cleanCompiledDirectory grunt tasks because of the rm -rf app/compiled.
The equivalent in windows is rd /s /q app/compiled

We currently do not run this on any Windows machines. I apologize the implementation of the grunt tasks has grown to be specific to a Unix environment. Feel free to submit a pull request with Windows support. We would greatly appreciate the contribution. Potentially, using something like Cygwin should get you further along with getting this up and running. Thanks for the feedback!


[SpeedDial] Add a prop to change orientation of actions

So, this has been discussed in
#2851
#10288
#9539
but this specific feature is not present.  I'm happy to do a PR, but wanted to gauge interest and get feedback first.

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current/Expected Behavior
Currently, SpeedDial orients actions above the FAB; that is, when you click on or mouseover a FAB, the actions appear above the FAB.  That's great for FABs at the bottom of the page, but not so good when they are at the top.  It would be nice to be able to specify which direction the actions are oriented.
I would propose adding a prop (orientation or perhaps position) of type enum.  The value of the prop would determine which direction the actions appear relative to the FAB.
(sorry for the edit, I hit 'enter' and WHOOSH, the darn thing published :))

I'm personally not a big fan of the horizontal speed-dial from a design perspective, regardless of screen position. Do you have any examples of it being used in the wild?

Hmm...I don't have any examples of a horizontal speed-dial.
I'm much more interested in a vertical speed-dial, but with the actions below the FAB. I'd be happy to leave the horizontal question for another time.

I'm much more interested in a vertical speed-dial, but with the actions below the FAB.

Arguably that's just a drop-down menu, but perhaps a speed-dial is more mobile friendly? Do you want to work it?

I am happy to work it.  Probably a simple first contribution.
I'm getting this from the Material ui specs here (near the bottom)


Roll engine 0ec3b7d437d4..c79faed71c66 (2 commits)

https://github.com/flutter/engine/compare/0ec3b7d437d4...c79faed71c66
git log 0ec3b7d437d4..c79faed71c66 --no-merges --oneline
c79faed71 Decode UIView's creation parameters and pass them to the view factory. (flutter/engine#6715)
467ff33aa Roll src/third_party/skia 348a03729796..d7a7586b0d2f (12 commits) (flutter/engine#6714)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff, who should
be CC'd on the roll, and stop the roller if necessary.

@liyuqian : New roll has been created by https://autoroll.skia.org/r/flutter-engine-flutter-autoroll

Auto-roller completed checks. About to merge.


AIRGoogleMap setOnClick

Summary
After upgrading dependencies when going to our test react-native project we get the following error:
Exception thrown while executing UI block: -[AIRGoogleMap setOnClick:]: unrecognized selector sent to instance 0x7f89a915c400
__44-[RCTUIManager flushUIBlocksWithCompletion:]_block_invoke
RCTUIManager.m:1205
__44-[RCTUIManager flushUIBlocksWithCompletion:]_block_invoke.496
__RCTExecuteOnMainQueue_block_invoke
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_main_queue_drain
_dispatch_main_queue_callback_4CF
CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE
__CFRunLoopRun
CFRunLoopRunSpecific
GSEventRunModal
-[UIApplication _run]
UIApplicationMain
main
start_sim
0x0
Reproducible sample code
<MapView
                    showsMyLocationButton={false}
                    toolbarEnabled={false}
                    provider={PROVIDER_GOOGLE}
                    showsUserLocation={true}
                    ref={mapRef}
                    style={MapComponentStyles.map}
                    initialRegion={initialRegion}
                    customMapStyle={mapStyle}
                    removeClippedSubviews={false}
                    followsUserLocation={false}
                    onRegionChangeComplete={region => onRegionUpdateHandler(region)}
                />

Steps to reproduce
Just pod install with latest dependencies. and run iOS
Expected result
Map page to be loaded
Actual result
the attached error
React Native Maps Version
1.10.1
What platforms are you seeing the problem on?
iOS (Google Maps)
React Native Version
0.73.2
What version of Expo are you using?
Not using Expo
Device(s)
iPhone 14, emulator
Additional information
No response

It seems that the problem is thrown when map view is nested inside a <TouchableWithoutFeedback style={MapComponentStyles.touchable} onPressOut={() => { setCarouselVisible(false) }}>

@xristeas this bug seems to be outside this library .. closing, you can always wrap the MapView in a container view.


Encoding broken

Take a supercell .csv file. Decode it, then encode the .csv file you just decoded and you will see that the file that was decoded/encoded differs from the original .csv file

Hi there, seems weird to respond to a post 3 years ago but i just came across the coc resources on github. Anyways what i think is that they added some sort of signature at the start of the file which cant be decoded and so its lost when trying to encode the file back. I've only started diving in the files yesterday but I feel like the modding community is pretty dead rn so I'm trying to reach out to people who might have a better understanding of it lol.


Rope optimization part 2

Single v4-8 step time from 1.209 to 1.199 secs.
(No convergence data since it is actually bit-wise identical locally)
Optimization From Blake!

The GPU failure is
jaxlib.xla_extension.XlaRuntimeError: INTERNAL: All algorithms tried for %bitcast.220 = bf16[12,2048,8,256]{1,3,2,0} bitcast(bf16[12,8,2048,256]{2,3,1,0} %copy.130), metadata={op_name="jit(train_step)/jit(main)/transpose(jvp(Transformer))/decoder/while/body/remat/decoder/self_attention/query_rotary/convert_element_type[new_dtype=float32 weak_type=False]" source_file="/app/MaxText/layers/embeddings.py" source_line=172} failed. Falling back to default algorithm.  Per-algorithm errors:

when downcasting to bfloat16 on GPU.


OwnedProxy Testing / Deployment / Verifier

Additional owned proxy testing
Deployment code update
Verifier code update
Simulation and prover fuzzing
Payable protections
Withdrawal testing
Additional testing harness fixes

Functionality looks fine, just documentation that needs to be cleaned up.


NEXT-00000 - Fix download link mail

1. Why is this change necessary?
Download links from downloads delivery mail do not work with multiple sales channels because the domain from another sales channel is used while generating the download link.
2. What does this change do, exactly?
Change mail template to use rawUrl with sales channel domain instead of url.
3. Describe each step to reproduce the issue or behaviour.
Create a second sales channel > add a digital product > order the digital product via the second sales channel > set payment status paid > try to open download link from mail
4. Please link to the relevant issues (if any).
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[ ] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

🤖[deprecated] Generated by Copilot at be2d4c5
This pull request fixes the download link mail to use the correct sales channel domain. It changes the url function to the rawUrl function in the mail templates and adds a migration to update the existing mail templates in the database.

🤖[deprecated] Generated by Copilot at be2d4c5

Add a changelog entry for the fix of the download link mail (link)
Replace the url function with the rawUrl function in the mail templates to use the correct sales channel domain for the download link (link, link, link, link)
Create a migration class that updates the existing mail templates in the database with the new fixtures (src/Core/Migration/V6_6/Migration1701688920FixDownloadLinkMail.php, link)

Hello @lacknere,
Your changes have been imported, and the Pull Request has been merged!
Thanks a lot for your contribution!


Fix link in documentation

Fixes #21289

@bot-gradle test and merge

OK, I've already triggered a build for you.


Why both npm and yarn lock files?

Noticed you have lock files of both package managers.
Shouldn't you just stick to one of them?

Good catch. I think this was left after some testing with yarn (which I love) but I eventually just stuck with good 'ol npm lock files. I'll remove it.

Resolved in: https://github.com/darcyclarke/rawkit/commit/603519442b11b036187975ee1baa8a6b5536bf63


Test templates

This pull requests adds some utils and templates for benchmark tests.
Added a folder benchmarking-tests. In the root of the folder there is a fabfile.py and benchmark_utils.py. This contains utilities common to all tests.
Inside benchmarking-tests there will be several test folders containing a README with the steps needed to reproduce the test and possibly custom scripts for that particular test.

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

Merging [#261][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master       #261   diff @@
==========================================
  Files            19         19
  Lines          1099       1099
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            956        956
  Misses          143        143
  Partials          0          0

Powered by Codecov. Last updated by [5d78b8e...d735d67][cc-compare]
[cc-base-branch]: https://codecov.io/gh/bigchaindb/bigchaindb/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/bigchaindb/bigchaindb/compare/5d78b8edffb4464afa96e3b206f29e0cc8177c85...d735d677fd034549beba71f086b898a06715aa00
[cc-pull]: https://codecov.io/gh/bigchaindb/bigchaindb/pull/261?src=pr

I made some minor changes to the names of commands and fabfile tasks, otherwise :+1:

I just added a README file to the benchmarking-tests folder to explain what that folder is for.

I'm going to add a bit more to test1/README.md. I will push that soon.

Okay done.


The trimAutoWhitespace option should be ignored for changes from pushEditOperations

monaco-editor version: 0.20.0
Browser: Google Chrome 83.0.4103.61 (64-bit)
OS: macOS 10.15.4
Playground code that reproduces the issue:
let a = true;
if (a) {

}

When trimAutoWhitespace option is set to true, Monaco automatically removes the indentation automatically added on the empty line within if blocks in the sample code above once you make a change somewhere else in the code after that. So upon returning to that empty line after making a change somewhere else your extra whitespace/indentation is not there anymore, which is how the trimAutoWhitespace setting is supposed to work.
However, this also happens when a change is made as a result of calling pushEditOperations. So, for example, if you're automatically applying other changes while the user is typing and specifically after the user hits enter after the opening if block so that Monaco automatically inserts whitespace/indentation on the next line, the whitespace that was just added will be removed because of the trimAutoWhitespace setting, even though the change that happened was a programmatic change and wasn't caused by the user. This doesn't sound like an expected behavior since user's cursor will jump to the beginning of the line and erase the necessary indentation.
I would suggest to ignore the trimAutoWhitespace setting for changes performed via pushEditOperations so that trimAutoWhitespace is triggered only by changes made by the user directly.
To reproduce:

Write the code above in the sample in JavaScript mode, move your cursor to the immediate right of the opening { block and hit Enter. This will create automatic indentation if automatic indentation setting is enabled in Monaco (should be on by default), i.e. your cursor will jump to the next line which will have some whitespace before the cursor.
Execute pushEditOperations. One way to do it is from the browser console:

monaco.editor.getModels()[0].pushEditOperations([], [{
  range: new monaco.Range(1, 1, 1, 1),
  text: 'z',
}]);

If your focus/cursor was lost while executing the command, move your cursor back to the last position - at the end of the empty line created after the { opening block. See how the whitespace that was is gone, even though the user didn't make any changes manually.

As an alternative, you can execute step 2 with an added delay using setTimeout to have time to perform step 3 before the change is performed and additionally see how the cursor jumps to the beginning of the line once the operation is executed.
Since trimAutoWhitespace is enabled by default this behavior can lead to different issues when using pushEditOperations on code that is also editable by the user.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


Consider implementing a custom stream map

See https://github.com/apple/swift-nio-http2/pull/258

I will participate. 💪

Hi @Bue-von-hon , I talked about this with @franz1981 and was planning to start working on it in a few weeks. But if you have some time now, that's great.
Here are a couple things we discussed and that might be of interest.
Unlike swift-nio-http2, Netty already uses a "specialized" data structure to store stream state, IntObjectHashMap. So the possible performance gains, if any, may not be as important as described in https://github.com/apple/swift-nio-http2/pull/258.
The plan was to benchmark (probably using techempower plaintext scenario adapted to HTTP/2) and see whether the cost of IntObjectHashMap pops up.
Regarding possible implementations, @franz1981 pointed to his ArrayRingBuffer experiment as a starting point.

I have submitted a PR #768 PTAL 🙏


Fix QPY handling of registers

Summary
QPY previously had rather complicated logic to handle deserialisation of registers that was heavily couched in the old model of registers "owning" the bits they contained.  This is no longer the data model of the circuit, so the code was naturally complex to try and make it work.
Instead, in deserialisation now we just add the correct number of bit instances to the circuit at the start, and then build up any required registers by using the indices field.
It's not clear to me how an index ever could be negative here; it's not clear how a register could be in the circuit but its bits aren't added, so it feels like there might be the possibility of a bug I've missed.

Details and comments
Fix #9094.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.008%) to 84.544%

Files with Coverage Reduction
New Missed Lines
%

qiskit/qpy/binary_io/circuits.py
1
91.17%

qiskit/extensions/quantum_initializer/squ.py
2
79.78%

Totals

Change from base Build<PHONE_NUMBER>:
0.008%

Covered Lines:
62402

Relevant Lines:
73810

💛  - Coveralls

Sounds good - I added those new cases in 03d802ccc.

If we're nervous about the scope of the change to the logic here, we could consider holding the bugfix until 0.23.

Yeah, I think that would be wise. Or at least let it sit on main a bit longer than typically to ensure we've tested it sufficiently even if we decide to backport it eventually.


error in run_regression with default model in non-minibatch mode

Hi @yozhikoff ,
could you please look into this when you have time?
`### Creating model ### - time 0.01 min
Analysis name: RegressionGeneBackgroundCoverageTorch_122covariates_6948cells_13565genes
Training model to determine n_epochs with CV
0%
0/10000 [00:00<?, ?it/s]

RuntimeError                              Traceback (most recent call last)
 in
30                    export_args={'path': results_folder + 'regression_model/', # where to save results
31                                 'save_model': True, # save pytorch model?
---> 32                                 'run_name_suffix': ''})
33
34 reg_mod = r['mod']
/nfs/team205/vk7/sanger_projects/BayraktarLab/cell2location/cell2location/run_regression.py in run_regression(sc_data, model_name, verbose, return_all, train_args, model_kwargs, posterior_args, export_args)
196         print('### Training model to determine n_epochs with CV ###')
197     if train_args['mode'] == 'normal':
--> 198         mod.fit_advi_iterative(**fit_kwards)
199     elif train_args['mode'] == 'tracking':
200         mod.fit_advi_iterative(tracking=True, **fit_kwards)
/nfs/team205/vk7/sanger_projects/BayraktarLab/cell2location/cell2location/models/torch_model.py in fit_advi_iterative(self, n, n_type, n_iter, learning_rate, num_workers, train_proportion, l2_weight)
246                     optim.zero_grad()
247                     y_pred = self.model.forward(**extra_data_train)
--> 248                     loss = self.loss(y_pred, x_data, l2_weight=l2_weight)
249                     loss.backward()
250                     optim.step()
/nfs/team205/vk7/sanger_projects/BayraktarLab/cell2location/cell2location/models/RegressionGeneBackgroundCoverageTorch.py in loss(self, param, data, l2_weight)
260                 l2_reg = l2_reg + l2_weight['l2_weight'] * i.pow(2).sum()
261
--> 262         return -self.nb_log_prob(param, data).sum() + l2_reg
263
264     # =====================Other functions======================= #
/nfs/team205/vk7/sanger_projects/BayraktarLab/cell2location/cell2location/models/torch_model.py in nb_log_prob(param, data, eps)
134                 + torch.lgamma(data + theta)
135                 - torch.lgamma(theta)
--> 136                 - torch.lgamma(data + 1)
137         )
138
RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu!`

I think we will address this by moving the torch regression model to scVI external (either pyro or torch version)

no longer relevant due to the move to scvi-tools/pyro


Extract header and footer content to separate templates

This change makes it easier to customize the header and footer content. Before this change, the whole header and footer had to be overridden, including the meta, style and script tags.
Apart from moving the code to separate files, there are no other changes to the templates in this PR.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b63e2e0). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #4797   +/-   ##
=========================================
  Coverage          ?   20.69%
=========================================
  Files             ?      167
  Lines             ?    32388
  Branches          ?        0
=========================================
  Hits              ?     6702
  Misses            ?    24705
  Partials          ?      981

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 b63e2e0...bf20213. Read the comment docs.

There is a PR #4651 that is pending a merge that will likely require changes to be made in this PR

Thanks for letting me know. If my change is accepted, I'm happy to rebase it so that you can merge it directly. :)

@lukasbestle please resolve conflict

Done :)


Update Moderate Path Float Parsing Algorithms

There have been a few updates to the moderate path float parsing algorithms in minimal-lexical, which can either provide performance benefits or reduce the amount of static storage required, depending on your use-case. I'll summarize a list of plausible options below, and if any seem beneficial to the maintainers of serde-json, will be happy to submit a PR.
Quick Background
Just for a quick summary: the float parsing algorithm is broken into 3 parts:

A fast path algorithm, where the significant digits can be exactly represented as a native float without truncated.
A moderate path algorithm, to process all floats except near-halfway cases through an extended representation of a float.
A slow path algorithm, that discerns the proper way to round near-halfway floats using arbitrary-precision arithmetic.

The moderate path is ~66-75% faster than the slow path, and therefore improvements to it either from a performance standpoint or correctness standpoint can lead to dramatic performance gains.
Interpolate the Cached Power Exponent
Serde uses pre-computed values for the cached float exponents in cached_float80. However, we can interpolate all these exponents, since each exponent is just effectively ⌈ log2(10) * exp10 ⌉. Using a pre-computed, integral power for log2(10), we can calculate the exponent exactly from the index to the cached power.
The specific pseudo-code can be used to generate this magic number, and verify it produces the correct result over the entire range of valid exponents:
import math

def get_range(radix, max_exp, bitshift):
    den = 1 << bitshift
    num = int(math.ceil(math.log2(radix) * den))
    for exp in range(0, max_exp):
        exp2_exact = int(math.log2(radix**exp))
        exp2_guess = num * exp // den
        if exp2_exact != exp2_guess:
            raise ValueError(f'{exp}')
    return num, bitshift

>>> get_range(10, 350, 16)
(217706, 16)

See the appendix to see the full changes required to implement this change.
Pros:

Less storage required.
No discernible impact on runtime performance.

Cons:

N/A

Correctness Concerns:

N/A, can be proven the generated exponents are identical for all valid inputs.

Add the Eisel-Lemire Algorithm.
A fast algorithm for creating correct representations of floats from an extended 128-bit (or 192-bit) representation was developed and is currently in use in major Google projects like Golang and Wuffs, as well as others. The Eisel-Lemire algorithm is ~15% for a uniform distribution of randomly-generated floats over the entire float range, and catches halfway cases different than the existing extended-float algorithm.
A few examples of cases:

"9007199254740992.0" (or 1<<53): correctly classified by both.
"9007199254740992000.0e-3"(or 1<<53): only classified by extended-float only.
"9007199254740993.0" (or 1 + (1<<53`): both cannot classify.
"9007199254740994.0" (or 2 + (1<<53)`): correctly classified by both.
"9007199254740995.0" (or 3 + (1<<53)`): correctly classified by Eisel-Lemire only.
"9007199254740996.0" (or 4 + (1<<53)`): correctly classified by both.
"2.470328229206232720e-324" (near-halfway subnormal float): correctly classified by extended-float only.
"8.988465674311580536e307" (large near-halfway float): correctly classified by Eisel-Lemire only.

In short, the two combined have overlapping coverage, and can avoid delegating to the slow path algorithm, leading to major performance benefits. See minimal-lexical/lemire.rs for an example implementation of this algorithm. The general approach therefore is run Eisel-Lemire, and if the algorithm fails, delegate to the extended-float algorithm.
Pros:

Slightly faster performance than extended-float in some cases.
Can be combined with extended-float to minimize delegating to the slow path.
Can use pre-computed powers for Eisel-Lemire for extended-float too, leading to minor performance improvements.

Cons:

Increased storage required (requires an additional 1226 u64s, or ~9.8 KB).

Correctness Concerns:

Substantial, but well-established algorithm and passes all correctness tests.
It passes the curated suite of halfway cases, a large, curated suite of cases used to validate Go's parser, and Rust's extensive randomly-generated test-cases.

Replace Extended-Float with Lemire
A third option is to entirely remove the extended-float algorithm, and replace it with the Eisel-Lemire algorithm. In order to do so, we need to round-down to b so the slow algorithm can correctly differentiate between b, b+h, and b+u. Extensive comments and code samples are included in lexical-core/lemire.rs for how to implement this.
Pros:

Slightly faster performance than extended-float in some cases.

Cons:

Increased storage required (requires an additional 1226 u64s, or ~9.8 KB).
Less correct than extended-float, and therefore delegates to the slow path algorithm more often.

Correctness Concerns:

Substantial, but well-established algorithm and passes all correctness tests.
It passes the curated suite of halfway cases, a large, curated suite of cases used to validate Go's parser, and Rust's extensive randomly-generated test-cases.

Appendix
Interpolation
The full changes to interpolate the exponent are the following:
diff --git a/src/lexical/cached.rs b/src/lexical/cached.rs
index ef5a9fe..701a897 100644
--- a/src/lexical/cached.rs
+++ b/src/lexical/cached.rs
@@ -5,31 +5,8 @@
 use super::cached_float80;
 use super::float::ExtendedFloat;

-// POWERS
-
-/// Precalculated powers that uses two-separate arrays for memory-efficiency.
-#[doc(hidden)]
-pub(crate) struct ExtendedFloatArray {
-    // Pre-calculated mantissa for the powers.
-    pub mant: &'static [u64],
-    // Pre-calculated binary exponents for the powers.
-    pub exp: &'static [i32],
-}
-
-/// Allow indexing of values without bounds checking
-impl ExtendedFloatArray {
-    #[inline]
-    pub fn get_extended_float(&self, index: usize) -> ExtendedFloat {
-        let mant = self.mant[index];
-        let exp = self.exp[index];
-        ExtendedFloat { mant, exp }
-    }
-
-    #[inline]
-    pub fn len(&self) -> usize {
-        self.mant.len()
-    }
-}
+const LOG2: i64 = 217706;
+const LOG2_SHIFT: i32 = 16;

 // MODERATE PATH POWERS

@@ -37,9 +14,9 @@ impl ExtendedFloatArray {
 #[doc(hidden)]
 pub(crate) struct ModeratePathPowers {
     // Pre-calculated small powers.
-    pub small: ExtendedFloatArray,
+    pub small: &'static [u64],
     // Pre-calculated large powers.
-    pub large: ExtendedFloatArray,
+    pub large: &'static [u64],
     /// Pre-calculated small powers as 64-bit integers
     pub small_int: &'static [u64],
     // Step between large powers and number of small powers.
@@ -52,17 +29,23 @@ pub(crate) struct ModeratePathPowers {
 impl ModeratePathPowers {
     #[inline]
     pub fn get_small(&self, index: usize) -> ExtendedFloat {
-        self.small.get_extended_float(index)
+        let mant = self.small[index];
+        let exp = -63 + ((LOG2 * index as i64) >> LOG2_SHIFT);
+        ExtendedFloat {
+            mant,
+            exp: exp as i32,
+        }
     }

     #[inline]
     pub fn get_large(&self, index: usize) -> ExtendedFloat {
-        self.large.get_extended_float(index)
-    }
-
-    #[inline]
-    pub fn get_small_int(&self, index: usize) -> u64 {
-        self.small_int[index]
+        let mant = self.large[index];
+        let biased_e = index as i64 * self.step as i64 - self.bias as i64;
+        let exp = -63 + ((LOG2 * biased_e) >> LOG2_SHIFT);
+        ExtendedFloat {
+            mant,
+            exp: exp as i32,
+        }
     }
 }

diff --git a/src/lexical/cached_float80.rs b/src/lexical/cached_float80.rs
index 9beda3d..43e18e8 100644
--- a/src/lexical/cached_float80.rs
+++ b/src/lexical/cached_float80.rs
@@ -10,7 +10,7 @@
 //! integer to calculate exact extended-representation of each value.
 //! These values are all normalized.

-use super::cached::{ExtendedFloatArray, ModeratePathPowers};
+use super::cached::ExtendedFloatArray;

 // LOW-LEVEL
 // ---------
@@ -29,18 +29,6 @@ const BASE10_SMALL_MANTISSA: [u64; 10] = [
<PHONE_NUMBER>7200000000, // 10^8
<PHONE_NUMBER>4000000000, // 10^9
 ];
-const BASE10_SMALL_EXPONENT: [i32; 10] = [
-    -63, // 10^0
-    -60, // 10^1
-    -57, // 10^2
-    -54, // 10^3
-    -50, // 10^4
-    -47, // 10^5
-    -44, // 10^6
-    -40, // 10^7
-    -37, // 10^8
-    -34, // 10^9
-];
 const BASE10_LARGE_MANTISSA: [u64; 66] = [
<PHONE_NUMBER>1253852697, // 10^-350
<PHONE_NUMBER>5301367670, // 10^-340
@@ -109,74 +97,6 @@ const BASE10_LARGE_MANTISSA: [u64; 66] = [
<PHONE_NUMBER>1667747109, // 10^290
<PHONE_NUMBER>9066387756, // 10^300
 ];
-const BASE10_LARGE_EXPONENT: [i32; 66] = [
-    -1226, // 10^-350
-    -1193, // 10^-340
-    -1160, // 10^-330
-    -1127, // 10^-320
-    -1093, // 10^-310
-    -1060, // 10^-300
-    -1027, // 10^-290
-    -994,  // 10^-280
-    -960,  // 10^-270
-    -927,  // 10^-260
-    -894,  // 10^-250
-    -861,  // 10^-240
-    -828,  // 10^-230
-    -794,  // 10^-220
-    -761,  // 10^-210
-    -728,  // 10^-200
-    -695,  // 10^-190
-    -661,  // 10^-180
-    -628,  // 10^-170
-    -595,  // 10^-160
-    -562,  // 10^-150
-    -529,  // 10^-140
-    -495,  // 10^-130
-    -462,  // 10^-120
-    -429,  // 10^-110
-    -396,  // 10^-100
-    -362,  // 10^-90
-    -329,  // 10^-80
-    -296,  // 10^-70
-    -263,  // 10^-60
-    -230,  // 10^-50
-    -196,  // 10^-40
-    -163,  // 10^-30
-    -130,  // 10^-20
-    -97,   // 10^-10
-    -63,   // 10^0
-    -30,   // 10^10
-    3,     // 10^20
-    36,    // 10^30
-    69,    // 10^40
-    103,   // 10^50
-    136,   // 10^60
-    169,   // 10^70
-    202,   // 10^80
-    235,   // 10^90
-    269,   // 10^100
-    302,   // 10^110
-    335,   // 10^120
-    368,   // 10^130
-    402,   // 10^140
-    435,   // 10^150
-    468,   // 10^160
-    501,   // 10^170
-    534,   // 10^180
-    568,   // 10^190
-    601,   // 10^200
-    634,   // 10^210
-    667,   // 10^220
-    701,   // 10^230
-    734,   // 10^240
-    767,   // 10^250
-    800,   // 10^260
-    833,   // 10^270
-    867,   // 10^280
-    900,   // 10^290
-    933,   // 10^300
-];
 const BASE10_SMALL_INT_POWERS: [u64; 10] = [
     1, 10, 100, 1000, 10000, 100000, 1000000, 10000000, 100000000,<PHONE_NUMBER>,
 ];
@@ -187,14 +107,8 @@ const BASE10_BIAS: i32 = 350;
 // ----------

 const BASE10_POWERS: ModeratePathPowers = ModeratePathPowers {
-    small: ExtendedFloatArray {
-        mant: &BASE10_SMALL_MANTISSA,
-        exp: &BASE10_SMALL_EXPONENT,
-    },
-    large: ExtendedFloatArray {
-        mant: &BASE10_LARGE_MANTISSA,
-        exp: &BASE10_LARGE_EXPONENT,
-    },
+    small: &BASE10_SMALL_MANTISSA,
+    large: &BASE10_LARGE_MANTISSA,
     small_int: &BASE10_SMALL_INT_POWERS,
     step: BASE10_STEP,
     bias: BASE10_BIAS,

Thanks for the update!
Right now I don't have a great sense of what the people relying on this would prefer to optimize for (whether it's performance, binary size, etc). Absent of feedback to the effect that the current implementation is not serving people's needs, I would prefer to mostly stick with the current code.
My own priorities for the float parser in order are:

Correctness
Reasonable performance envelope (say, within 2–5× of "optimal")
Source code simplicity / auditability
Smaller compile time / binary size (there is some complicated tradeoff frontier between these two things)

The exponent interpolation change sounds well aligned with this, whereas the Eisel–Lemire change is probably not impactful for us.
I think the right workflow might be to plan to pull in batches of changes from minimal-lexical on a cadence of something like 18 months or 24 months (other than correctness fixes, which we would take immediately).


[fix] fix the typo in scripts/text_condition/gpu/sample_inpaint.sh

[fix] fix the typo in scripts/text_condition/gpu/sample_inpaint.sh : "PDNM" to "PNDM"

lgtm


'Open With' and Interactivity Issue with Encrypted 7z Archives

Description
Bug: 'Open With' and Interactivity Issue with Encrypted 7z Archives
Description:
When attempting to open an encrypted 7z archive using the 'Open With' option in the Files app, no other applications are shown, and the archive is forced to open directly with the 'Files' application. If the password is correct, the contents are visible but not interactable. This behavior occurs with both older and newer 7z archives.
Additional Context:
This issue is related to this previous issue, but differs in that the 'Open With' feature fails to show other applications, and interaction with files in the archive is not possible.
Steps To Reproduce

Right-click on an encrypted 7z archive.
Select 'Open With' from the context menu.
Observe that no other applications (like native 7z) are shown, and the file opens directly in 'Files.'
If the password is incorrect, an empty folder appears. If correct, the contents appear but cannot be interacted with.
Right-clicking and selecting 'Extract' works as expected, allowing access to the files.

Requirements
The expected behavior is that when selecting 'Open With' for an encrypted 7z archive, the application should display a list of compatible programs (such as the native 7z application) instead of defaulting to the 'Files' app. Additionally, once opened, users should be able to interact with the contents of the archive if the correct password is provided, regardless of the archive's version or creation method.
Files Version
<IP_ADDRESS>
Windows Version
10.0.19045.3803
Log File
2024-09-17 20:41:02.4652|Warning|SevenZip.SevenZipOpenFailedException: Invalid archive: open/read error! Is it encrypted and a wrong password was provided?
If your archive is an exotic one, it is possible that SevenZipSharp has no signature for its format and thus decided it is TAR by mistake.
at SevenZip.SevenZipBase.ThrowException(CallbackBase handler, Exception[] e)
at SevenZip.SevenZipExtractor.GetArchiveInfo()
at SevenZip.SevenZipExtractor.get_ArchiveFileData()
at Files.App.Utils.Storage.ZipStorageFolder.b__49_1()
at Files.App.Utils.Storage.IPasswordProtectedItem.RetryWithCredentialsAsync[TOut](Func1 func, Exception exception)    at Files.Shared.Extensions.SafetyExtensions.Wrap[TOut](Func1 inputTask, Func3 onFailed)    at Files.App.Utils.Storage.ZipStorageFolder.<>c__DisplayClass50_0.<<GetItemsAsync>b__0>d.MoveNext() --- End of stack trace from previous location ---    at Files.App.Utils.Storage.UniversalStorageEnumerator.ListEntries(BaseStorageFolder rootFolder, StorageFolderWithPath currentStorageFolder, CancellationToken cancellationToken, Int32 countLimit, Func2 intermediateAction, Dictionary2 defaultIconPairs) 2024-09-17 20:41:07.7971|Warning|SevenZip.SevenZipOpenFailedException: Invalid archive: open/read error! Is it encrypted and a wrong password was provided? If your archive is an exotic one, it is possible that SevenZipSharp has no signature for its format and thus decided it is TAR by mistake.    at SevenZip.SevenZipBase.ThrowException(CallbackBase handler, Exception[] e)    at SevenZip.SevenZipExtractor.GetArchiveInfo()    at SevenZip.SevenZipExtractor.get_ArchiveFileData()    at Files.App.Utils.Storage.ZipStorageFolder.<GetItemsAsync>b__49_1()    at Files.App.Utils.Storage.IPasswordProtectedItem.RetryWithCredentialsAsync[TOut](Func1 func, Exception exception)
at Files.Shared.Extensions.SafetyExtensions.Wrap[TOut](Func1 inputTask, Func3 onFailed)
at Files.App.Utils.Storage.ZipStorageFolder.<>c__DisplayClass50_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Files.App.Utils.Storage.UniversalStorageEnumerator.ListEntries(BaseStorageFolder rootFolder, StorageFolderWithPath currentStorageFolder, CancellationToken cancellationToken, Int32 countLimit, Func2 intermediateAction, Dictionary2 defaultIconPairs)

Can you confirm that the "Open with" menu shows 7zip when you right click in File Explorer?

Can you confirm that the "Open with" menu shows 7zip when you right click in File Explorer?

No, the 'Open With' menu does not show 7zip when right-clicking in the Files app. It opens directly with the 'Files' application, with no option to choose 7zip or any other app.

I understand about Files, can you confirm with File Explorer?

I understand about Files, can you confirm with File Explorer?

Thank you for the idea, I switched back to Windows Explorer, manually set 7z as the default 'Open With' application, and then returned to Files. After that, 7z appeared and worked as expected in Files. For your information, maybe enforcing the 'Choose Application' menu to display even when not initiated by default on Windows could help avoid this issue.
Cheers fam


documentation about MMA connection scheme and hand sensorization

documentation updated with the info about

electronics board: FT3D and FAP5
passive connector board: the MMA
cabling

hi @pattacini, you should have writing rights.

hi @pattacini, you should have writing rights.

Yep, accepted, thanks!
However, I still get the following error while pushing:
gitpod@simeoneduss-documentati-ve8cx3gyku0:/workspace/documentation$ git push
Enumerating objects: 13, done.
Counting objects: 100% (13/13), done.
Delta compression using up to 16 threads
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 172.98 KiB | 15.72 MiB/s, done.
Total 8 (delta 4), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (4/4), completed with 4 local objects.
remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: At least 1 approving review is required by reviewers with write access. Commits must have valid signatures.
To https://github.com/simeonedussoni/documentation.git
 ! [remote rejected] master -> master (protected branch hook declined)
error: failed to push some refs to 'https://github.com/simeonedussoni/documentation.git'

I'll come to you to check the configuration of your master branch.

@simeonedussoni, we should check this on your settings:
https://stackoverflow.com/a/62933851/3956237

Done! My amendments are in 619c9d1d613b56d1ee3b3c5fe32b987b86be54e7.

I've also reduced the size of a couple of images.


Where has feed meta-information gone?

I recently did an update to emacs 29, which was an ordeal I won't relate here. Anyway, my feeds are now missing the meta information in their primary display. I used to copy/yank that information as as whole to update my journals with what I've been listening to, and things like Title:, Author:, Date:, Feed:, Tags:, Link:, and Enclosure: were all valuable information. Since my upgrade, I only see the body text, and none of that meta information. I don't see any customization options about this; how can I get that display back?
I am running emacs 29.3 with the latest elfeed, 5c05a1e master branch.

https://github.com/jeetelongname/elfeed-goodies
Apparently this is all a "feature" of the package elfeed-goodies, which must not have been turned on previously. It "nicely" hides all kinds of information. Removing that plugin and now I see the headers, I have a title bar that tells me elfeed update status (when last updated, how the current update is going, etc).


feat: Add README, LICENSE and previous Releases

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-examples/blob/master/.github/CONTRIBUTING.md.
What is the current behavior?
README, LICENSE and previous release files not created/moved
Issue Number: #5 & #7
What is the new behavior?
README, LICENSE and previous release files have been added
Does this PR introduce a breaking change?

[ ] Yes
[x] No

New Imports
Are there any new imports or modules? If so, what are they used for and why?
no
Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

recheck

recheck


Cop suggestion: use of the new hash syntax, with comma

Expected behavior
I would like Rubocop to fail / autocorrect when I am using arrows for building hash objects, since a new hash syntax was introduced with Ruby 1.9.
Actual behavior
Both styles (with arrows and commas) are allowed.
Steps to reproduce the problem
{'foo => 'bar'} should be auto-corrected in {foo: 'bar'}
RuboCop version
0.47.1

You mean Style/HashSyntax? 🙂

Oh yes, thanks, I was surprised not to find that in the existing cops.
Yet I have to figure out why it doesn't apply on my project.

Before I close that issue, any idea why I don't see this cop applying on my project?
This is my .rubocop.yml file (on ruby-2.3.1):
Documentation:
  Enabled: false

Metrics/AbcSize:
  Max: 50

Metrics/BlockLength:
  Max: 400

Metrics/ClassLength:
  Max: 200

Metrics/CyclomaticComplexity:
  Max: 10

Metrics/LineLength:
  Max: 300

Metrics/MethodLength:
  Max: 40

Metrics/ModuleLength:
  Max: 400

Metrics/ParameterLists:
  Max: 10

Metrics/PerceivedComplexity:
  Max: 10

Style/AccessorMethodName:
  Enabled: false

Style/CaseIndentation:
  Enabled: false

Style/FrozenStringLiteralComment:
  Enabled: false

Style/IndentArray:
  Enabled: false

Style/IndentHash:
  Enabled: false

Style/MultilineMethodCallIndentation:
  Enabled: false

Style/SpaceInsideHashLiteralBraces:
  Enabled: false

Style/TrivialAccessors:
  Enabled: false

With Style/HashSyntax, {:foo => 'bar'} is auto-corrected in {foo: 'bar'}
However, {'foo' => 'bar'} is accepted although it could be written {foo: 'bar'} too.
What do you think about extending Style/HashSyntax for this use case?

However, {'foo' => 'bar'} is accepted although it could be written {foo: 'bar'} too.

One small thing to note is that those two hash literals are not quite equivalent.  In the above example the key in the first literal (with =>) will be of type String, whereas the key in the second literal will be of type Symbol (tested on 2.3.1).
I agree that using symbols for hash keys is preferable, but my understanding is there exists cases in which using strings for hash keys is necessary (I could be wrong!).

I agree that using symbols for hash keys is preferable, but my understanding is that there are cases in which using strings for hash keys is necessary (I could be wrong!).

Exactly. Doing the replacement suggested by @mickaeltr would result in code that's different from the original which is likely going to cause issues.

Thanks for the explanation (I'm quite new to Ruby)


convert image to pdf with searchable txt

is it possible with this wrapper?
I think tesseract cli natively supports it

https://guides.library.illinois.edu/c.php?g=347520&p=4121426
tesseract words.png out -l deu PDF

related to #302

I guess I found the related issue

what about stream support? e.g. rather than writing a file I just write to a stream in memory

You can use Ghostscript for that https://www.ghostscript.com/ocr.html

b/c of ghost script licensing I ended up using a nodejs library inside of c# to get text from an image.


Adding SST Dates to Discipline Dashboard

Who is this PR for?
Dashboard Users
What problem does this PR fix?
SST dates were not displaying in the discipline dashboard
What does this PR do?
Adds the dates!
Screenshot (if adding a client-side feature)

Checklists

[x] Author checked latest in IE - Discipline Dashboard
[ ] Reviewer checked latest in IE - Discipline Dashboard

@alexsoble forgot to fix this last night, this should take care of the merge conflicts

Looks good!


Set net.ipv4.conf.antrea-gw0.arp_announce to 1

Fix #5451
Set arp_announce to 1 on Linux platform to make the ARP requests sent on the gateway
interface always use the gateway IP as the source IP, otherwise the ARP requests would be
dropped by ARP SpoofGuard flow.

/test-flexible-ipam-e2e

/test-flexible-ipam-e2e

/test-flexible-ipam-e2e

/test-flexible-ipam-e2e
/test-all

/test-networkpolicy

@gran-vmv please backport it to 1.12-1.14


Mappings for damage type tags (& Provider) & record class

All is in the title ^^.

Currently tag providers dont have a consistent naming scheme. Some are Tag while others are Tags

I move DamageTypeTagsProvider to net.minecraft.data.server.tag (instead of net.minecraft.data.server).


Trying to install GAM in MAC OS 10.11.6 with no luck

At the end when I have:
Select the authorized scopes by entering a number.
Append an 'r' to grant read-only access or an 'a' to grant action-only access.
[]  0)  Group Directory API (supports readonly)
[]  1)  Organizational Unit Directory API (supports readonly)
[]  2)  Users Directory API (supports readonly)
[]  3)  Chrome OS Devices Directory API (supports readonly)
[]  4)  Mobile Devices Directory API (supports readonly and action)
[]  5)  Legacy Email Settings API - Delegation
[]  6)  Resource Calendar API (supports readonly)
[]  7)  Group Settings API
[]  8)  Calendar Data API (supports readonly)
[]  9)  Audit Reports API
[] 10)  Usage Reports API
[] 11)  Drive API - create report docs only
[] 12)  License Manager API
[] 13)  User Security Directory API
[] 14)  Notifications Directory API
[] 15)  Site Verification API
[] 16)  Gmail API - send report docs todrive notifications only
[] 17)  User Schema Directory API (supports readonly)
[] 18)  Classroom API - counts as 5 scopes
[] 19)  Cloud Print API
[] 20)  Data Transfer API (supports readonly)
[] 21)  Customer API (supports readonly)
[] 22)  Domains Directory API (supports readonly)
[] 23)  Roles Directory API (supports readonly)
 s)  Select all scopes
 u)  Unselect all scopes
 e)  Exit without changes
 c)  Continue to authorization

Please enter 0-23[a|r] or s|u|e|c: c
Your browser has been opened to visit:
I select s for all scopes and then c to continue and browser shows error. I use Chrome on MAC.

no matter what I use I have

That’s an error.

Error: invalid_client
The OAuth client was not found.

sprintership,
Do not select all scopes, if scope 15 is not selected, leave it unselected.
What is the URL printed?
Ross
On Tue, Dec 6, 2016 at 4:44 PM, sprintership<EMAIL_ADDRESS>wrote:

no matter what I use I have

That’s an error.

Error: invalid_client
The OAuth client was not found.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/354#issuecomment-265320751, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIU8L3MiVrH8Edn9oMtG1rKXQOpiz34wks5rFgF_gaJpZM4LGD-F
.

--
Ross Scroggs
<EMAIL_ADDRESS>

Hi Ross, You were right, I went through again all steps and now it works like charm ./gam info user
I have to figure it out how to create alias for gam instead of going to folder every time. Thank You so much!

sprintership,
Do the following:
edit ~/.bash_aliases and add a line substituting with the actual path:
alias gam="/Path/To/Gam/gam"
exit and start new shell
gam version
Ross
On Tue, Dec 6, 2016 at 5:16 PM, sprintership<EMAIL_ADDRESS>wrote:

Hi Ross, You were right, I went through again all steps and now it works
like charm ./gam info user
I have to figure it out how to create alias for gam instead of going to
folder every time. Thank You so much!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/354#issuecomment-265326099, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIU8L52OouuzmoKCZ6toOJFzw78qSdlJks5rFgjlgaJpZM4LGD-F
.

--
Ross Scroggs
<EMAIL_ADDRESS>