Make Formik dependency optional

Currently Formik is required as FormikGroup and FormikGroupE depend on it. This is not ideal as if a consumer wants to use React Hook Form, they will still have to install Formik.
One solution discussed was to move Formik-related bits to a separate package.
Split from #2769.

Also note that withFormik is a candidate for rework.


[fix][broker] Avoid block markDeletePosition forward when skip lost entries

Motivation
The configuration autoSkipNonRecoverableData is designed to turn this feature on if we can accept partial data loss. When some entries is lost, the broker will still work. cursor.readPosition will move to next position for skip these positions.
But now we have this problem: cursor.readPosition can move to next positition, but the cursor.markDeletePosition can not forward.
for example:

topic-1 has some entries:  [1:1],[1:2],[1:3],[1:4],[1:5],[1:6],[1:7],[1:8]
entry [1,4] and [1,5] lost
cursor read entry from ledger, then send message [1:1],[1:2],[1:3],[1:6],[1:7],[1:8] to consumer. (Current: readPosition=[1:8], markDeletePosition=[1:1])
consumer individual ack [1:1],[1:2],[1:3],[1:6],[1:7],[1:8]  (Current: readPosition=[1:8], markDeletePosition=[1:3])
markDeletePosition will stay at [1:3], can not move forward to [1:8]

The root cause is: When entries lost, lost entries not be delete from cursor.
Modifications
When skip lost entries, delete these entries from cursor.
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

/pulsarbot rerun-failure-checks


ReUse general translations

we should reuse general termes more often!
found dubble strings in locale_en-US.ini :
issues.dependency.cancel = Cancel
issues.dependency.remove = Remove
delete_key = Remove
settings.delete_collaborator = Remove
members.remove = Remove
[settings] cancel = Cancel
editor.cancel_lower = Cancel
editor.cancel = Cancel
issues.cancel = Cancel
issues.add_time_cancel = Cancel
issues.cancel_tracking = Cancel
milestones.cancel = Cancel
release.cancel = Cancel

and there are more ...

We should check case by case. In some language families it's possible to use the same word for different concepts or in different context, while in other families you need different words. For example, "day" in English can mean "jour" and "journée" in French and they mean different things. Or in Spanish you need to match the adjective "gender" (feminine/masculine) with the noun.

@guillep2k I'll close this issue (cleanup my issue list)


make search mixin more generic

mixinSummaryHandler is used by FFX repo to implement O365 search contract by providing search content for components. There are cases where component may wish not to implement search contract nd rely on ODSP search parser to have alternative logic to extract text, or might have not text at all to push to search. For such cases we will allow it to return undefined, which will not add a blob to summary.

Had tried this in FFX code, works fine in our use case. Thanks.

Not sure what is change is doing / solving. @vladsud Can you add a description?

Not sure what is change is doing / solving. @vladsud Can you add a description?

Added description


Fix typo in doc of SignatureCheckerUpgradeable

Fix typo in doc of SignatureCheckerUpgradeable:
- sigantures
+ signatures

PR Checklist

[ ] Tests
[x] Documentation
[ ] Changelog entry

Hello @NicolasMahe, I see you submitted a similar PR to the non-upgradeable contracts.
This one is not needed  since fixing it there will also be applied it next time transpilation happens.
Thank you anyway for your contribution!


Track work needed to migrate upstream Windows tests from aks-engine to CAPZ

Blocking

[x] Taint master / linux nodes when running upstream e2etest
[x] Get GMSA tests running with CAPZ clusters

[x] Add post kubeadm task to configure GMSA?

[x] k/k PR job support

[x] Use Windows node binaries built from PR branch
[x] Use control plane components (kube-apiserver, scheduler etc, built from PR branch)

[x] Determine where to host cluster configs (kubernetes-sigs/windows-testing?)
[x] Decide if we want to regularly publish VHDs to help cluster provisioning times

[x] Stick with current cadence (every K8s patch release)

[x] containerd support in capz

[x] ~Post kubeadm action to configure CNI on the node~ used hostprocess containers

[x] Decide which CNIs / configurations we should use for upstream test (Calico to gain DSR and network policy support??)
[x] Ensure log collection scripts work with CAPZ/Windows nodes during upstream tests
[x] csi proxy tests
[x] move release jobs to capz

Non-Blocking

[x] Windows billing extension for CAPZ
[x] Transfer ownership of signed provisioning scripts to AKS team

@jsturtevant

Related: https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/1119

@jsturtevant @marosset what's the status on gmsa tests? can this be closed?

They are ready to merge here: https://github.com/kubernetes-sigs/windows-testing/pull/328

we are fully moved off aks-engine to capz at this point 🤖


<EMAIL_ADDRESS>not working

<EMAIL_ADDRESS>command no longer works
Is there anyone who has experienced the same problem

hi @brunosoaresds  can u type the right code to creat a new group ?


Ability to choose between two or more hosted environments for a service as well as non-hosted.

Feature Description
I would like the ability to be able to choose between multiple "hosted" environments for a single service as well as non-hosted environments.
Motivation and Context
Zulip has two hosted environments:
*https://chat.zulip.org
*https://{teamid}.zulipchat.com
Zulip also allows users to have their own non-hosted environments as well so this is also required at the same time as the above two hosted environments.
Currently this isn't available in Franz.

@adlk is this getting done at some point? Thanks

+1 to have this feature

Closing. You can do this now.


Can't click into image or link input fields

Version:
1.0.52
Browser:
Chrome based, Safari, Firefox
OS:
Mac OS 10.15.5, haven't tested on others so far
Expected behavior:
To be able to click into the image url and link url fields
Actual behavior:
I canny do it cap'n !
https://giphy.com/gifs/YMRW9PR2LHzZvtGGCe

have the same thing too

try to delete tabindex property in the parent component

try to delete tabindex property in the parent component

are you seriously?) It looks like kinda crutch.
What about my case:

I have material-ui Dialog that contains jodit
dialog container and jodit popup container render at same level in DOM
only one way to enable click on input field is to delete tabindex attribute from nested (!) div of dialog container. And unfortunately I can't remove this tabindex from component, because material-ui build this component inside itself without any way to customize tabindex attribute.

https://gfycat.com/ru/prestigiousfrenchindianspinyloach

probably the same in my case too, I'm getting:

I have narrowed the problem down - we are using a chakra-ui modal to contain the editor component, and the styling in the portal which contains the modal is causing the z-index conflict here I think. Investigating further ....

zIndex sounds like it would be the case, but I'm not having any luck with it... I have my Material-UI Dialog set with a zIndex of 9999 and I found that the popup (.jodit-popup .jodit-popup_strategy_leftbottom) for the link has a zIndex of 10000001, which should be sitting right on top of the dialog.
When I removed the tabIndex from the Material-UI dialog, the problem went away, but there's no solution readily available to do that... I'll look into the Material-UI tabIndex and see if there's a way to strip it out.
  I'm having the same issue. I can manually remove (i.e. in the browser) the tabindex from a react Modal to get it to work.  But I have no way to make a fix. In my code I've tried to remove tabindex, but react always sets it to something.
Thanks!

try set disableEnforceFocus={true} to the Material-UI dialog, it work for me

thanks @alfred-risb for solution, this worked for me too,
 <Dialog disableEnforceFocus={true} ></Dialog>

For chakra-ui this worked for me
 <Modal isOpen={isOpen} onClose={onClose} size="6xl" trapFocus={false} autoFocus={false}></Modal>

I'm using react-bootstrap and no such props to help me


OSCAL helper commands

Lula as an OSCAL native tool will be performing various activities using OSCAL models as a point of input/output.
As we develop with OSCAL further, it will be good to identify automation/validation and other OSCAL workflows that are painful for human-operators to conduct or require deep understanding of OSCAL knowledge.
This issue can be used initially to track possible additions or helper commands for operating on oscal.
Current targets:

Updating OSCAL files from one version to the next
Checking OSCAL files for validity

Closing this as we implement lula tools functionality and the validation logic in go-oscal


Fix sending/receiving surface bits command.

Pass on proper command type to application
On send let the server implementation decide to send
<IP_ADDRESS>.1 Set Surface Bits Command (TS_SURFCMD_SET_SURF_BITS) or
<IP_ADDRESS>.2 Stream Surface Bits Command (TS_SURFCMD_STREAM_SURF_BITS)
Thank you @viniciusjarina for pointing out the issue.

@akallabeth any ETA to merge this one? 😊

@viniciusjarina whenever other devs approve ;)
Currently a bit busy as you can imagine.

No worries. Thank you @akallabeth

@bmiklautz @mfleisz @hardening anyone time for review/merge?

I feel like it's gonna break compatibility, isn't it ?

@hardening if it was used broken like we did then yes. can add a fallback to current behaviour if the wrong command value is set?

@hardening ok, now it is just like it was except the correct command is supplied.

I guess that updated version will output a lot of warnings in weston and in ogon, but it can be easily fixed.

damn, merged to early:
See:
MSRDPRFX <IP_ADDRESS>.1 Encode Message Sequencing

The sequence of encode messages is encapsulated inside an Extended Bitmap Data structure ([MS-RDPBCGR] section <IP_ADDRESS>.1.1), which is encapsulated in a Stream Surface Bits Surface Command

MS-RDPNSC 1.3 Protocol Overview

NSCodec-compressed bitmaps that cannot be cached are sent encapsulated in Set Surface Bits Surface Commands

We need another PR that changes the shadow sample to use CMDTYPE_SET_SURFACE_BITSfor nscodec and CMDTYPE_STREAM_SURFACE_BITS for rfx


fix: Externallogin on existing session

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


PIN screen bypass [Keine Kamishirasawa]

This one's a rather minor bug, but if you download something, force the app to close using the app drawer, resume the download and view the file when completed, you can bypass the app lock and enter the app without a pin
I'm on 1.2.9

Needs a redesign before fixing

This issue was moved to avluis/Hentoid#207


Layer Operations

The ATT&CK Navigator defines a layer format which can be used to describe annotations on ATT&CK matrixes in JSON format. The principal functionality of the ATT&CK Navigator is viewing and editing these matrixes, but it also includes the ability to merge (combine) the annotations from multiple layers. Unfortunately, these layer operations are only available in the GUI and therefore unsuited to scripting.
This issue proposes the creation of a layer-operations script to handling merging of layer annotations. It would allow complex manipulations of scores, comments, enabled/disabled states, colors, and metadata.
The script would feature two interfaces, and evaluation of the technique annotations would be performed by passing functions as named arguments.
list interface
In this interface, the layers would be provided in a list. The annotation-evaluation function would then be passed a list of that annotation in the same order as the layers specified. For example, to average the scores of three layers:
avglayer = layerops([layer1, layer2, layer3], score=lambda t: sum(t)/len(t))

To double the score of a single input layer:
doublelayer = layerops([layer1], score=lambda t: t[0] * 2)

To combine the comments of three layers:
commentlayer = layerops([layer1, layer2, layer3], comment=lambda t: ", ".join(t))

Another example where both score and enabled are set
layer = layerops([layer1, layer2], score=lambda t: t[0] * t[1], enabled=lambda t: t[0] or t[1])

dict interface
In the case where the user is working with complex formulas, remembering the index of a layer may be difficult. In this case, the user could provide a dict of layers as input. The input to the annotation-evaluation function would therefore also be a dict:
layer = layerops({a: layer1, b: layer2, c: layer3}, score=lambda t: (t["a"] + t["b"]) / t["c"])

layer = layerops({a: layer1, b: layer2}, comment=lambda t: "comment for layer1 is {a}, comment for layer2 is {b}".replace("{a}", t["a"]).replace("{b}", t["b"]))

WIP in #15

Looking forward to this!

@beerMT this script is now released on the master branch.


tag anchor platform docker images pushed to dockerhub with 'latest tag'

as a partner I would like to be able to pull the latest dockerhub anchor platform image using latest tag.


Enable TIFF write of 'half' pixels, if "tiff:half" attribute is nonzero.

Enable TIFF write of 'half' pixels, if "tiff:half" attribute is nonzero.
Set up a global OIIO attribute "tiff:half" that sets the default globally,    and also have the ImageOutput for TIFF recognize a per-file "tiff:half"    override. The default in both cases is 0, meaning that requests for    half pixel float files in the absence this attribute nonzero will be    automatically be upgraded to float, which is more widely read.
The reason for this is that nearly every non-OIIO-based reader fails to    correctly recognize half-valued pixels in TIFF files, including    PhotoShop and Nuke 9. So you are urged not to write half tiff, unless    you are sure that the only consumer of those files uses OIIO (which can    read them properly), or have verified that other consumers in your    pipeline get it right.
Here is the Adobe tech report describing this TIFF extension:     http://chriscox.org/TIFFTN3d1.pdf
A typical OIIO use of this would be to create a half TIFF texture file:
    maketx in.tif -attrib tiff:half 1 -d half -o half.tx

Why would you do this? Because in my benchmarks, texture access of    a half TIFF texture file is nearly twice the raw read performance of    the equivalent OpenEXR half texture.
Along the way, I added the missing get_int_attribute, get_float_attribute, and get_string_attribute equivalents to the global OIIO::getattribute, to match how we have done it for the versions that are methods of ImageSpec, TextureSystem, and a number of other classes.

LGTM


Implement trait Default for ApplicationFlags

See https://github.com/gtk-rs/examples/pull/199#issuecomment-432971480,
add "magic " to creating application
--- a/src/bin/basic.rs
+++ b/src/bin/basic.rs
@@ -34,7 +36,7 @@ fn build_ui(application: &gtk::Application) {

 fn main() {
     let application = gtk::Application::new("com.github.gtk-rs.examples.basic",
-                                            gio::ApplicationFlags::empty())
+                                            Default::default())
                                        .expect("Initialization failed...");

     application.connect_activate(|app| {

As it don't help removing use gio::prelude::*; completely
as at minimum two use gio::ApplicationExtXXX; needed,
I not sure now that this really needed.
cc @GuillaumeGomez, @sdroege

Awesome, thanks!

Perfect


list 'explainmagnitude' total does not sum all projects for mag+RAC

In the debug window, command 'list explainmagnitude' gives an output for individual projects followed by a 'Total' mag and RAC at the bottom which should be the sum of the projects (?) however it appears to only be the total for the last project listed. Another in the GRC chatroom confirmed this. Am wondering whether its a bug that affects anything else or if it's a standalone issue (and easily fixed).
Cheers,
Bren

can you post the complete output? (leave out your cpid)
normally, each line shows the cumulative addition to the previous line:

perhaps that awakes the impression that "however it appears to only be the total for the last project listed." ?

Make sure you are looking at the right column and not at "cumulative mag", which is a sum of that and all previous projects' magnitude.

It's definitely the cumulative on each line I was looking at! Sorry all! Nothing to see here...


Use official solarized themes

Fixes #20873

This change sources the solarized themes from the official, newer https://github.com/deplorableword/textmate-solarized repository, rather than from https://github.com/Colorsublime/Colorsublime-Themes
The official themes looks a lot better in general, with a notable regression I found being that it doesn't color types which was added in 5926ba029f433ff515454d8b92b7ecb2b3e6ea4e. We should probably work instead to upstream that and if it's not accepted due to inactivity, fork the repo so we can easily track the changes.
Comparisons (left old, right new):
XML

CSS

TS

Bash

Python

Ruby

Java

See my comment here. I'd rather not start any theme discussions. It's always a sensitive issue and causes a of emotions. In the worst case we end up maintaining two variants (see our default themes). Let's rather encourage users to create and publish their own themes.


The rv-each-* binder stops functioning after unbind()

Hi. I'm coming across a really confusing issue when calling View.unbind() and then later on building another view using rivets.bind() on the same element; everything is working except the rv-each-* blocks; the items are no longer bound.
I suspect that rivets is applying an irreversible modification to the DOM element that prevents it from correctly parsing/building it on successive bind calls.
The behavior is reproducible as can be seen in this JSFiddle. It starts out with a dropdown of 3 currencies, a model that references a single currency (USD), and then another that references another (EUR) - all is working great. Yet once the view is unbound and another is bound to the same element, the dropdown option[value] are all empty!
The only workaround that I found is to never unbind the view... but that's not really nice, as the component could sit in the background for a long time and its bindings are needless then.
PS: thank you for the awesome library, I've been using rivets for three days now and it's really enjoyable (maybe except for the lack of documentation, but perhaps I can contribute once I get over the confusion!)

Closing as this appears to have been resolved


Enable E2E test data generator

What was changed

Enabled to E2E  canary test data generator back
Why?

it was disabled as it was triggering SLA
Checklist

Closes

How was this tested:

GHA run

Any docs updates needed?

We no longer run e2e tests here.


Add pre: and post: action for cleaning up

Description
This pr will add pre: and post: action for cleaning up to solve the issue #383 and #374.
The pre: and post: action run at the start and the end of a job respectively, instead of running cleaning up azure accounts at the beginning of the main: action. This enables users to switch active azure accounts logged in by azure/login within the job, see scenario in #383. Meanwhile, it ensures a more clean and secure environment for login, see https://github.com/Azure/login/pull/376#issue-2011802278.
Release tests:
https://github.com/Azure/azclitools-actions-test/actions/runs/7345677123
https://github.com/Azure/azclitools-actions-test/actions/runs/7345708979
Example:

Since setting environment variable for agent is required in current process, there is no need to use core.exportVariable. See https://github.com/actions/toolkit/blob/main/packages/core/README.md#exporting-variables, core.exportVariable is used to add environment variable to this step and future steps environment blocks.

Got the following errors from a self-deployed github action runner:
Error: Login cleanup failed with Error: Unable to locate executable file: az. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.. Make sure 'az' is installed on the runner. If 'enable-AzPSSession' is true, make sure 'pwsh' is installed on the runner together with Azure PowerShell module.

Wonder how to prepare az tool in the workflow files to fix this error.

Hi @will-beta-clique, have you installed azure-cli on your self-deployed runner? You can refer to https://learn.microsoft.com/en-us/cli/azure/install-azure-cli.

Got the following errors from a self-deployed github action runner:
Error: Login cleanup failed with Error: Unable to locate executable file: az. Please verify either the file path exists or the file can be found within a directory specified by the PATH environment variable. Also check the file mode to verify the file is executable.. Make sure 'az' is installed on the runner. If 'enable-AzPSSession' is true, make sure 'pwsh' is installed on the runner together with Azure PowerShell module.

Wonder how to prepare az tool in the workflow files to fix this error.

We are seeing the same issue. Previously we installed the azure cli as a separate step in the workflow before the login.

As this happens in a PRE step this is causing any workflows running on runners without az pre-installed to fail even if we have a step for installing az. I would revert this PR and make a new release frankly.

Yup nice for breaking all workflow running self hosted runners. The pre step don't even let you any chance to install az cli :/

Bug issue: https://github.com/Azure/login/issues/403

Hi @will-beta-clique @szberes @opdude @benjamin-rousseau-shift @kristeey, please first pin the version to v1.5.1. We will prepare a fix by skipping cleanup if az is not installed. And Let's track the issue in #403.

Having another issue with this release this morning. Can no longer use dynamically retrieved output values for credentials using the github actions JSON tooling, since the function is executed before the pipeline can populate it:
name: Login to Azure
uses: azure/login@v1
with:
  creds: |
    {
      "clientId":"${{ secrets.gh_clientid }}",
      "clientSecret":"${{ secrets.gh_clientsecret }}",
      "subscriptionId":"${{ fromJSON(steps.subscriptions.outputs.result).targetId }}",
      "tenantId":"${{ secrets.tenantid }}"
    }
  enable-AzPSSession: true

Results in Error reading JToken from JsonReader. Path '', line 0, position 0. during the pre step.

i see the same issue when we use secrets to be fetched from previous step of the workflow 'fromJSON(steps.xyz)'
(Line: 246, Col: 18): Error reading JToken from JsonReader. Path '', line 0, position 0.

Bug issue: Issue 405


Documentation Typo: "Install blobfuse driver on a kubernetes cluster" for 1.7 and 1.8

What happened:
The documentation for the command to use on Kubernetes 1.7 and 1.8 has a typo.
What you expected to happen:
The command provided for 1.7 & 1.8 should work.
How to reproduce it:
Review the steps under "for version v1.8 & v1.7" in https://github.com/Azure/kubernetes-volume-drivers/blob/master/flexvolume/blobfuse/README.md#2-install-blobfuse-driver-on-every-agent-vm.
Anything else we need to know?:

This command:
kubectl apply -f https://raw.githubusercontent.com/Azure/kubernetes-volume-drivers/master/flexvolume/blobfuse/deployment/blobfuse-> flexvol-installer-1.8.yaml

should probably be:
kubectl apply -f https://raw.githubusercontent.com/Azure/kubernetes-volume-drivers/master/flexvolume/blobfuse/deployment/blobfuse-flexvol-installer-1.8.yaml

The formatting for the "for version v1.8 & v1.7" section should also be fixed to be consistent with the formatting of the section for 1.9.

thanks, I have corrected the typo

@andyzhangx what about my second bullet point?

The formatting for the "for version v1.8 & v1.7" section should also be fixed to be consistent with the formatting of the section for 1.9.

Sorry; I know that's kind of a separate issue that I sneaked in. 😅

I set the format "for version v1.8 & v1.7" section like that mainly because 1.7 & 1.8 are  deprecated in AKS version now:
az aks get-versions --location eastus2 -o table
KubernetesVersion    Upgrades
-------------------  ------------------------
1.12.7               None available
1.12.6               1.12.7
1.11.9               1.12.6, 1.12.7
1.11.8               1.11.9, 1.12.6, 1.12.7
1.10.13              1.11.8, 1.11.9
1.10.12              1.10.13, 1.11.8, 1.11.9
1.9.11               1.10.12, 1.10.13
1.9.10               1.9.11, 1.10.12, 1.10.13


Pipe problem when running app (not app-simple) and including app.js

Error below:
Uncaught TypeError: change_detection_1.Pipes.extend is not a functionwebpackJsonp.273 @ pipes.ts:15__webpack_require__ @ bootstrap ec2d90a06f7e26d96c5f:71webpackJsonp.256 @ app.ts:21__webpack_require__ @ bootstrap ec2d90a06f7e26d96c5f:71webpackJsonp.255 @ bootstrap.ts:43__webpack_require__ @ bootstrap ec2d90a06f7e26d96c5f:71webpackJsonp.0 @ app.js:8__webpack_require__ @ bootstrap ec2d90a06f7e26d96c5f:71webpackJsonpCallback @ bootstrap ec2d90a06f7e26d96c5f:42(anonymous function) @ app.js:2
client?cd17:36 [WDS] Warnings while compiling.

Pipes.append has been renamed into Pipes.extend in alpha 32.

the repo doesn't have to include it's own |json Pipe anymore. If you wanted to do so then you would need to use
Pipes.extend({
  'somepipe': SomePipe
})

either the hostInjector or viewInjector in the App component rather than app bindings in
bootstrap(app: Component, appInjector?: Array<Binding>, errorReporter?: Function): Promise


Add validation for RabbitMQ dynamic credentials

@kdubb I'm surprised it doesn't require https://github.com/quarkusio/quarkus/pull/21897 to pass?

Yeah this only tests that VaultDynamicCredentialsManager is working with RabbitMQ; same thing it was already doing for database credentials.
VaultCredentialsProvider is a simple wrapper around VaultDynamicCredentialsManager to request configured credentials.

LGTM. needs some squash.

Squashed.


Release Google.Cloud.BigQuery.DataExchange.V1Beta1 version 2.0.0-beta03

Changes in this release:
No API surface changes; just dependency updates.

Created release for Google.Cloud.BigQuery.DataExchange.V1Beta1-2.0.0-beta03


Adds SuperTokens as an auth provider

I rebased with 0.47 and looking good!

Ok, I pushed changes but don't see them ...
To https://github.com/redwoodjs/playground-auth.git
 + df3c8c1...2fa034f supertokens/main -> supertokens/main (forced update)

Am closing and replacing with https://github.com/redwoodjs/playground-auth/pull/101 to merge


AddtoCart is Not Working..

Its really an awesome plugin but add to cart is not working.. im getting this error :-
Exception has occurred.
_Exception (Exception: WooCommerce Error!
code: woocommerce_rest_missing_nonce
message: Missing the X-WC-Store-API-Nonce header. This endpoint requires a valid nonce.
status: 401)

and make your documentation well... its not clear how to use this... Thanks

Thank you. This was a known issue and  fixed in the most recent version 0.9.5. I am also considering writing detailed articles, once I make time and would appreciate such from the community as well.

You will be appreciated once you have detailed information. because it makes clear how to use and features and all that stuff.. good luck👍
waiting for documentation eagerly.


Public _RandomApplyTransform class

🚀 The feature
Make _RandomApplyTransform public for custom random apply transforms.
https://github.com/pytorch/vision/blob/9ebf10af02aeb882bd8d7782149e21b48528d562/torchvision/transforms/v2/_transform.py#L139
The main change is to refactor _RandomApplyTransform to RandomApplyTransform, add it to the available classes in torchvision.transforms.v2.
https://github.com/pytorch/vision/blob/9ebf10af02aeb882bd8d7782149e21b48528d562/torchvision/transforms/v2/__init__.py#L5
Motivation, pitch
This class might be beneficial for custom transformations that should have Random behaviour. We are currently playing with non-standard augmentation pipelines that needs this.
I will submit a PR with this refactoring.
Alternatives
No response
Additional context
No response

Thanks for the request @priba. Could you clarify what exactly you are trying to do? We already have a public RandomApply transform:
https://github.com/pytorch/vision/blob/bf03f4edfe8fd7543e98ed9a3771b01ab6c6f062/torchvision/transforms/v2/_container.py#L102-L110
Imagine you want to randomly apply a rotation. You can do
from torchvision.transforms import v2 as transforms

transform = transforms.RandomApply(
    [
        transforms.RandomRotation(degrees=30)
    ],
    p=0.7,
)

The one you linked so far is just an internal helper for classes that still have the p argument on them directly. Our vision for the future is to not write such transforms again, but rather wrap into RandomApply if we need such a behavior.

Hi @pmeier , thanks for the reply.
Indeed, I can have the same behaviour with RandomApply. For me, it felt more natural to define it as the class rather than wrapping each one of the augmentations with the RandomApply (if I want to have different probabilities for each one).
My idea was to make this internal helper class public to be able to follow the same implementation and functionalities.

My idea was to make this internal helper class public to be able to follow the same implementation and functionalities.

As mentioned above, we only have _RandomApplyTransform for BC and will likely not implement any new transformations based on it. Paired with the fact that we have a public RandomApply that a potential RandomApplyTransform would compete with, I don't see a good reason to go for that.

Not sure if technically possible due to jit etc, but ideally we should let RandomApply accept a single transform instead of a list?
emphasis mine below:

For me, it felt more natural to define it as the class rather than wrapping each one of the augmentations with the RandomApply (if I want to have different probabilities for each one).

@priba you won't be able to do that neither with RandomApply nor with _RandomApplyTransform. We don't have anything that allows that right now other than wrapping each transform.


Add a note about the Cedar stack and required databases

Minor, but might affect someone.

Thanks Ben!


Add "ssh" command

Describe how ssh command works and some of the flags and how they are useful.

Added by @The-Sundance-Kid in f98988d. Nice work


attachments not working?

I'm doing attachments: [ { path: 'path to file' } ] in the options and it does not work.  If I take that out the email gets sent.  With it in, I see nothing.  It also does not error out.  Is there some size limit?  Attachments are about 2.5 meg.  Is this just happening all async and the attachments are on their way out?

Here's an example script how to send attachments: https://github.com/andris9/Nodemailer/blob/master/examples/full.js (assuming you are using Nodemailer version 1.x and not 0.x). Check the error and info arguments of the sendMail callback, you can find the information about the status of the message from these variables.

Actually the issue turned out to be that if the smtp  server needs auth and it is empty then it  fails silently and the callback was never called.  Then no error was thrown.  I ended up putting in a console log to see what the communication was.  I'm on 1.0.
Also how does one know when the mail had been sent? Is there an event to listen to? I'm doing a video email thing and I end up with to many emails at once and need to que then up.  Having an event that I can identify when mail is sent would let me add that in.

Ok, nevermind.  It's just taking forever to send the attachments because of my uplink speed and size of attachments.


feat: Add Konbini

DRAFT do not merge

https://paper.dropbox.com/doc/Konbini-Hosted-Payment-Instructions-page-dogfooding--BFMfg~E_OLqgRh5n0e3fBVojAg-mqbwJUjRLMXBZdkoBBtW4

@cjavilla-stripe
I may can takeover this task.
But unfortunately, I'm not good at Swift.
How do you think about creating a new branch to add the example of Konbini payment?
I think I can create a example of JavaScript(Node) and PHP.

No need to add swift. The servers should already be done. We should only need the html and react client implementations.
If you like, we can pair and review the task together.

Resolved the conflicts.

@hibariya @cjavilla-stripe
Could you tell me the way to execute the E2E test in my local environment?
I got a several CI error in the actions, so I'd like to reproduce the error and wanna fix it.
Thanks!

Examples that I added or I confirmed
Custom Payment Flow

[x] [Client] react-cra
[x] [Client] html
[x] [Server] node
[x] [Server] node-typescript

@hideokamoto-stripe If you have Docker in your local environment, you can run on Docker containers with stripe-samples/sample-ci.
Step 1: make sure you have exported the following environment variables with export or other tools like direnv.

STRIPE_PUBLISHABLE_KEY
STRIPE_SECRET_KEY
STRIPE_SECRET_KEY

Step2: place a .env file that contains the following entries at the root of the repository so that containers can read them as environment variables.
DOMAIN=http://web:4242
SERVER_URL=http://web:4242
PRICE=price_xxxx # the price ID you have

Step3: clone stripe-samples/sample-ci and set up Docker containers.
$ git clone<EMAIL_ADDRESS>$ ./sample-ci/setup_development_environment custom-payment-flow node ../../client/html
$ docker-compose up

:memo: After docker-compose up, probably the runner container takes 2-30 seconds to install its dependencies.
Step4: Run the tests.
$ docker-compose exec runner bundle exec rspec spec/custom_payment_flow_server_spec.rb

Let me know if you find any hiccups :pray:

@hibariya
Sorry for delay the reply!
I've executed the E2E test in my local, and I've reproduce it.
$ docker-compose exec runner bundle exec rspec spec/custom_payment_flow_server_spec.rb
...FF.

Failures:

  1) custom-payment-flow integration /create-payment-intent Creates a payment intent for acss_debit with CAD currency
     Failure/Error: expect(status).to eq(200)

       expected: 200
            got: 400

       (compared using ==)
     # ./spec/custom_payment_flow_server_spec.rb:24:in `block (5 levels) in <top (required)>'

  2) custom-payment-flow integration /create-payment-intent sets the payment method options for ACSS
     Failure/Error: expect(status).to eq(200), resp.to_s
       {"error"=>{"message"=>"The payment method type provided: acss_debit is invalid. This payment method is available to Stripe accounts in CA and US and your Stripe account is in JP."}}
     # ./spec/custom_payment_flow_server_spec.rb:39:in `block (3 levels) in <top (required)>'

Finished in 3.1 seconds (files took 0.39723 seconds to load)
6 examples, 2 failures

Failed examples:

rspec './spec/custom_payment_flow_server_spec.rb[1:3:2]' # custom-payment-flow integration /create-payment-intent Creates a payment intent for acss_debit with CAD currency
rspec ./spec/custom_payment_flow_server_spec.rb:34 # custom-payment-flow integration /create-payment-intent sets the payment method options for ACSS

But once the container restart, the test does not work by the following errors.
$ docker-compose down
$ docker-compose up -d
$ docker-compose exec runner bundle exec rspec spec/custom_payment_flow_server_spec.rb
FFResponse:
nil
FResponse:
nil
FResponse:
nil
FResponse:
nil
F

Failures:

  1) custom-payment-flow integration fetches the index route
     Failure/Error: RestClient.get("#{SERVER_URL}#{path}", *args, **kwargs)

     Errno::ECONNREFUSED:
       Failed to open TCP connection to web:4242 (Connection refused - connect(2) for "web" port 4242)
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:163:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:63:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient.rb:66:in `get'
     # ./spec/spec_helper.rb:121:in `get'
     # ./spec/custom_payment_flow_server_spec.rb:6:in `block (2 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  2) custom-payment-flow integration served config as expected
     Failure/Error: response = RestClient.get("#{SERVER_URL}#{path}", *args, **kwargs)

     Errno::ECONNREFUSED:
       Failed to open TCP connection to web:4242 (Connection refused - connect(2) for "web" port 4242)
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:163:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:63:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient.rb:66:in `get'
     # ./spec/spec_helper.rb:125:in `get_json'
     # ./spec/custom_payment_flow_server_spec.rb:11:in `block (2 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  3) custom-payment-flow integration /create-payment-intent Creates a payment intent for card with USD currency
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:20:in `block (5 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  4) custom-payment-flow integration /create-payment-intent Creates a payment intent for acss_debit with CAD currency
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:20:in `block (5 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  5) custom-payment-flow integration /create-payment-intent sets the payment method options for ACSS
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:35:in `block (3 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  6) custom-payment-flow integration /create-payment-intent fails gracefully if missmatched currency and payment method type
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:47:in `block (3 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

Finished in 0.01407 seconds (files took 0.41406 seconds to load)
6 examples, 6 failures

Failed examples:

rspec ./spec/custom_payment_flow_server_spec.rb:4 # custom-payment-flow integration fetches the index route
rspec ./spec/custom_payment_flow_server_spec.rb:10 # custom-payment-flow integration served config as expected
rspec './spec/custom_payment_flow_server_spec.rb[1:3:1]' # custom-payment-flow integration /create-payment-intent Creates a payment intent for card with USD currency
rspec './spec/custom_payment_flow_server_spec.rb[1:3:2]' # custom-payment-flow integration /create-payment-intent Creates a payment intent for acss_debit with CAD currency
rspec ./spec/custom_payment_flow_server_spec.rb:34 # custom-payment-flow integration /create-payment-intent sets the payment method options for ACSS
rspec ./spec/custom_payment_flow_server_spec.rb:46 # custom-payment-flow integration /create-payment-intent fails gracefully if missmatched currency and payment method type

Do you know how can we resolve it?
Thanks!

And @cjavilla-stripe
I've checked the CI errors deeply.
I think the errors are comes from the beta flag.
Example error message:
"we currently require your account to have a bank account in one of the following currencies: aud" in "home\nBECS Direct Debit\nTry a test number:\n000-000 (Test BSB)\n000123456\n900123456\nName\nEmail Address\nBank Account\nPay\nBy providing your bank account details and confirming this payment, you agree to this Direct Debit Request and theDirect Debit Request service agreement, and authorise Stripe Payments Australia Pty Ltd ACN 160 180 343 Direct Debit User ID number 507156 (“Stripe”) to debit your account through the Bulk Electronic Clearing System (BECS) on behalf ofINSERT YOUR BUSINESS NAME HERE (the "Merchant") for any amounts separately communicated to you by the Merchant. You certify that you are either an account holder or an authorised signatory on the account listed above.\nInvalid Stripe API version: 2020-08-27; konbini_beta=v1. You do not have permission to pass this beta header: konbini_beta. If you have any questions, we can help at https://support.stripe.com/."
https://github.com/stripe-samples/accept-a-payment/runs/4979532741?check_suite_focus=true
Should we request to the dev team to enable the beta flag before merge it?
I think we can merge this PR after resolved this CI errors.

But once the container restart, the test does not work by the following errors.

According to the error messages, I think probably the web container is not running for some reason. Are there any suspicious error messages in the output of docker-compose logs web?

Thanks! @hibariya
I've open 3 terminal window, and run these commands.
window1
$ docker-compose up
accept-a-payment_runner_1 is up-to-date
accept-a-payment_stripe_1 is up-to-date
accept-a-payment_web_1 is up-to-date
Attaching to accept-a-payment_runner_1, accept-a-payment_stripe_1, accept-a-payment_web_1
stripe_1    | Checking for new versions...
stripe_1    | Getting ready...
stripe_1    |
stripe_1    | A newer version of the Stripe CLI is available, please update to: v1.7.12
stripe_1    | Ready! Your webhook signing secret is whsec_4977c209da5410dc194d566a97fc0dff479a2de0ceecd6b748d4d5a418fb073c (^C to quit)
runner_1    | Using public_suffix 4.0.6
runner_1    | Using addressable 2.8.0
runner_1    | Using bundler 2.2.32
runner_1    | Using byebug 11.1.3
runner_1    | Using matrix 0.4.2
runner_1    | Using mini_mime 1.1.2
runner_1    | Using mini_portile2 2.7.1
runner_1    | Using racc 1.6.0
runner_1    | Using nokogiri 1.13.1 (x86_64-linux)
runner_1    | Using rack 2.2.3
runner_1    | Using rack-test 1.1.0
runner_1    | Using regexp_parser 2.2.0
runner_1    | Using xpath 3.2.0
runner_1    | Using capybara 3.36.0
runner_1    | Using launchy 2.5.0
runner_1    | Using capybara-screenshot 1.0.26
runner_1    | Using childprocess 4.1.0
runner_1    | Using diff-lcs 1.5.0
runner_1    | Using unf_ext 0.0.8
runner_1    | Using unf 0.1.4
runner_1    | Using domain_name 0.5.20190701
runner_1    | Using dotenv 2.7.6
runner_1    | Using http-accept 1.7.0
runner_1    | Using http-cookie 1.0.4
runner_1    | Using mime-types-data 3.2022.0105
runner_1    | Using mime-types 3.4.1
runner_1    | Using netrc 0.11.0
runner_1    | Using rest-client 2.1.0
runner_1    | Using rexml 3.2.5
runner_1    | Using rspec-support 3.10.3
runner_1    | Using rspec-core 3.10.2
runner_1    | Using rspec-expectations 3.10.2
runner_1    | Using rspec-mocks 3.10.2
runner_1    | Using rspec 3.10.0
runner_1    | Using rspec-github 2.3.1
runner_1    | Using rubyzip 2.3.2
runner_1    | Using selenium-webdriver 4.1.0
runner_1    | Using stripe 5.43.0
runner_1    | Bundle complete! 9 Gemfile dependencies, 38 gems now installed.
runner_1    | Use `bundle info [gemname]` to see where a bundled gem is installed.
web_1       | npm WARN<EMAIL_ADDRESS>No repository field.
web_1       |
web_1       | audited 53 packages in 1.381s
web_1       |
web_1       | 2 packages are looking for funding
web_1       |   run `npm fund` for details
web_1       |
web_1       | found 0 vulnerabilities
web_1       |
web_1       |
web_1       | ><EMAIL_ADDRESS>start /work/custom-payment-flow/server/node
web_1       | > node server.js
web_1       |
web_1       | Node server listening at http://localhost:4242

window2
$ docker-compose exec runner bundle exec rspec spec/custom_payment_flow_server_spec.rb
...

Finished in 0.01474 seconds (files took 0.40399 seconds to load)
6 examples, 6 failures

Failed examples:

rspec ./spec/custom_payment_flow_server_spec.rb:4 # custom-payment-flow integration fetches the index route
rspec ./spec/custom_payment_flow_server_spec.rb:10 # custom-payment-flow integration served config as expected
rspec './spec/custom_payment_flow_server_spec.rb[1:3:1]' # custom-payment-flow integration /create-payment-intent Creates a payment intent for card with USD currency
rspec './spec/custom_payment_flow_server_spec.rb[1:3:2]' # custom-payment-flow integration /create-payment-intent Creates a payment intent for acss_debit with CAD currency
rspec ./spec/custom_payment_flow_server_spec.rb:34 # custom-payment-flow integration /create-payment-intent sets the payment method options for ACSS
rspec ./spec/custom_payment_flow_server_spec.rb:46 # custom-payment-flow integration /create-payment-intent fails gracefully if missmatched currency and payment method type

st-hideokamoto1:accept-a-payment hideokamoto$ docker-compose exec runner bundle exec rspec spec/custom_payment_flow_server_spec.rb
FFResponse:
nil
FResponse:
nil
FResponse:
nil
FResponse:
nil
F

Failures:

  1) custom-payment-flow integration fetches the index route
     Failure/Error: RestClient.get("#{SERVER_URL}#{path}", *args, **kwargs)

     Errno::ECONNREFUSED:
       Failed to open TCP connection to web:4242 (Connection refused - connect(2) for "web" port 4242)
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:163:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:63:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient.rb:66:in `get'
     # ./spec/spec_helper.rb:121:in `get'
     # ./spec/custom_payment_flow_server_spec.rb:6:in `block (2 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  2) custom-payment-flow integration served config as expected
     Failure/Error: response = RestClient.get("#{SERVER_URL}#{path}", *args, **kwargs)

     Errno::ECONNREFUSED:
       Failed to open TCP connection to web:4242 (Connection refused - connect(2) for "web" port 4242)
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:163:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:63:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient.rb:66:in `get'
     # ./spec/spec_helper.rb:125:in `get_json'
     # ./spec/custom_payment_flow_server_spec.rb:11:in `block (2 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  3) custom-payment-flow integration /create-payment-intent Creates a payment intent for card with USD currency
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:20:in `block (5 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  4) custom-payment-flow integration /create-payment-intent Creates a payment intent for acss_debit with CAD currency
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:20:in `block (5 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  5) custom-payment-flow integration /create-payment-intent sets the payment method options for ACSS
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:35:in `block (3 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  6) custom-payment-flow integration /create-payment-intent fails gracefully if missmatched currency and payment method type
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:47:in `block (3 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

Finished in 0.01407 seconds (files took 0.41406 seconds to load)
6 examples, 6 failures

Failed examples:

rspec ./spec/custom_payment_flow_server_spec.rb:4 # custom-payment-flow integration fetches the index route
rspec ./spec/custom_payment_flow_server_spec.rb:10 # custom-payment-flow integration served config as expected
rspec './spec/custom_payment_flow_server_spec.rb[1:3:1]' # custom-payment-flow integration /create-payment-intent Creates a payment intent for card with USD currency
rspec './spec/custom_payment_flow_server_spec.rb[1:3:2]' # custom-payment-flow integration /create-payment-intent Creates a payment intent for acss_debit with CAD currency
rspec ./spec/custom_payment_flow_server_spec.rb:34 # custom-payment-flow integration /create-payment-intent sets the payment method options for ACSS
rspec ./spec/custom_payment_flow_server_spec.rb:46 # custom-payment-flow integration /create-payment-intent fails gracefully if missmatched currency and payment method type

st-hideokamoto1:accept-a-payment hideokamoto$ docker-compose exec runner bundle exec rspec spec/custom_payment_flow_server_spec.rb
FFResponse:
nil
FResponse:
nil
FResponse:
nil
FResponse:
nil
F

Failures:

  1) custom-payment-flow integration fetches the index route
     Failure/Error: RestClient.get("#{SERVER_URL}#{path}", *args, **kwargs)

     Errno::ECONNREFUSED:
       Failed to open TCP connection to web:4242 (Connection refused - connect(2) for "web" port 4242)
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:163:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:63:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient.rb:66:in `get'
     # ./spec/spec_helper.rb:121:in `get'
     # ./spec/custom_payment_flow_server_spec.rb:6:in `block (2 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  2) custom-payment-flow integration served config as expected
     Failure/Error: response = RestClient.get("#{SERVER_URL}#{path}", *args, **kwargs)

     Errno::ECONNREFUSED:
       Failed to open TCP connection to web:4242 (Connection refused - connect(2) for "web" port 4242)
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:163:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:63:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient.rb:66:in `get'
     # ./spec/spec_helper.rb:125:in `get_json'
     # ./spec/custom_payment_flow_server_spec.rb:11:in `block (2 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  3) custom-payment-flow integration /create-payment-intent Creates a payment intent for card with USD currency
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:20:in `block (5 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  4) custom-payment-flow integration /create-payment-intent Creates a payment intent for acss_debit with CAD currency
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:20:in `block (5 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  5) custom-payment-flow integration /create-payment-intent sets the payment method options for ACSS
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:35:in `block (3 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  6) custom-payment-flow integration /create-payment-intent fails gracefully if missmatched currency and payment method type
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:47:in `block (3 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

Finished in 0.01752 seconds (files took 0.41411 seconds to load)
6 examples, 6 failures

Failed examples:

rspec ./spec/custom_payment_flow_server_spec.rb:4 # custom-payment-flow integration fetches the index route
rspec ./spec/custom_payment_flow_server_spec.rb:10 # custom-payment-flow integration served config as expected
rspec './spec/custom_payment_flow_server_spec.rb[1:3:1]' # custom-payment-flow integration /create-payment-intent Creates a payment intent for card with USD currency
rspec './spec/custom_payment_flow_server_spec.rb[1:3:2]' # custom-payment-flow integration /create-payment-intent Creates a payment intent for acss_debit with CAD currency
rspec ./spec/custom_payment_flow_server_spec.rb:34 # custom-payment-flow integration /create-payment-intent sets the payment method options for ACSS
rspec ./spec/custom_payment_flow_server_spec.rb:46 # custom-payment-flow integration /create-payment-intent fails gracefully if missmatched currency and payment method type

st-hideokamoto1:accept-a-payment hideokamoto$ docker-compose exec runner bundle exec rspec spec/custom_payment_flow_server_spec.rb
FFResponse:
nil
FResponse:
nil
FResponse:
nil
FResponse:
nil
F

Failures:

  1) custom-payment-flow integration fetches the index route
     Failure/Error: RestClient.get("#{SERVER_URL}#{path}", *args, **kwargs)

     Errno::ECONNREFUSED:
       Failed to open TCP connection to web:4242 (Connection refused - connect(2) for "web" port 4242)
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:163:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:63:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient.rb:66:in `get'
     # ./spec/spec_helper.rb:121:in `get'
     # ./spec/custom_payment_flow_server_spec.rb:6:in `block (2 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  2) custom-payment-flow integration served config as expected
     Failure/Error: response = RestClient.get("#{SERVER_URL}#{path}", *args, **kwargs)

     Errno::ECONNREFUSED:
       Failed to open TCP connection to web:4242 (Connection refused - connect(2) for "web" port 4242)
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:163:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:63:in `execute'
     # /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient.rb:66:in `get'
     # ./spec/spec_helper.rb:125:in `get_json'
     # ./spec/custom_payment_flow_server_spec.rb:11:in `block (2 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  3) custom-payment-flow integration /create-payment-intent Creates a payment intent for card with USD currency
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:20:in `block (5 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  4) custom-payment-flow integration /create-payment-intent Creates a payment intent for acss_debit with CAD currency
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:20:in `block (5 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  5) custom-payment-flow integration /create-payment-intent sets the payment method options for ACSS
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:35:in `block (3 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSED:
     #   Connection refused - connect(2) for "web" port 4242
     #   /usr/local/bundle/gems/rest-client-2.1.0/lib/restclient/request.rb:727:in `transmit'

  6) custom-payment-flow integration /create-payment-intent fails gracefully if missmatched currency and payment method type
     Failure/Error: throw "Failed to parse failed response"

     UncaughtThrowError:
       uncaught throw "Failed to parse failed response"
     # ./spec/spec_helper.rb:143:in `throw'
     # ./spec/spec_helper.rb:143:in `rescue in rescue in post_json'
     # ./spec/spec_helper.rb:138:in `rescue in post_json'
     # ./spec/spec_helper.rb:129:in `post_json'
     # ./spec/custom_payment_flow_server_spec.rb:47:in `block (3 levels) in <top (required)>'
     # ------------------
     # --- Caused by: ---
     # Errno::ECONNREFUSE

Window3
$ docker-compose logs web
Attaching to accept-a-payment_web_1
web_1       | npm WARN<EMAIL_ADDRESS>No repository field.
web_1       |
web_1       | audited 53 packages in 1.381s
web_1       |
web_1       | 2 packages are looking for funding
web_1       |   run `npm fund` for details
web_1       |
web_1       | found 0 vulnerabilities
web_1       |
web_1       |
web_1       | ><EMAIL_ADDRESS>start /work/custom-payment-flow/server/node
web_1       | > node server.js
web_1       |
web_1       | Node server listening at http://localhost:4242

===
I think the node server may be running.

@hideokamoto-stripe Thanks for the information! Sorry for the late reply :pray:
As you said, the logs look good. Could you hit docker-compose ps when the RSpec fails with Errno::ECONNREFUSED? Maybe the container had exited without error logs..  Is the web container's state "Up"?
According to the error Errno::ECONNREFUSED, probably it's because either the server on the web container is not running or the test runner is not able to reach the right host/port. Since it says Connection refused - connect(2) for "web" port 4242, the host/port seems correct and I think the former is likely the case.

Thanks @hibariya -san!
This is the execution logs of the docker-compose ps
$ docker-compose ps          Name                        Command             State             Ports
--------------------------------------------------------------------------------------------
accept-a-payment_runner_1   /work/sample-ci/docker/run    Up
                            ...
accept-a-payment_stripe_1   /bin/ash -c /bin/stripe --    Up
                            ...
accept-a-payment_web_1      /work/sample-ci/docker/nod    Up      <IP_ADDRESS>:4242->4242/tcp,:::
                            ...                                   4242->4242/tcp

All process works well...?
🙇

@hideokamoto-stripe Thanks :pray: It seems working... :joy:
Could you do over the steps here from the beginning? Right after that (before running docker-compose down), do the tests work again without errors (Errno::ECONNREFUSED)?

@hibariya
I've tried to re-clone the repo in my local and run the step again. The E2E test worked well and was able to reproduce the CI error too.
main branch(works well)
$ docker-compose exec runner bundle exec rspec spec/custom_payment_flow_server_spec.rb
......

Finished in 3.58 seconds (files took 0.43957 seconds to load)
6 examples, 0 failures

Konbini branch(reproduce the error)
$ docker-compose exec runner bundle exec rspec spec/custom_payment_flow_server_spec.rb
..FFFF

Failures:

  1) custom-payment-flow integration /create-payment-intent Creates a payment intent for card with USD currency
     Failure/Error: expect(status).to eq(200)

       expected: 200
            got: 400

       (compared using ==)
     # ./spec/custom_payment_flow_server_spec.rb:24:in `block (5 levels) in <top (required)>'

I'm not sure why the old one does not work well, but maybe depends on the .env file that placed in the project dir (like custom-payment-flow/server/node/.env)
Thanks for helping!
And I'd like to add the docs to summarize about how can we run the E2E test in our local.
Docs: How to run the E2E test in the local env. #583

@hideokamoto-stripe Super! I cannot reproduce the problem on my laptop yet, and I don't have any clear idea of what was going on. I think maybe there's a possibility that docker-compose down has some relevance with the problem. To stop containers, I usually use docker-compose stop instead of that one since we don't have to remove networks and volumes. If you have any chance, I'd love to know if the problem sticks even with docker-compose stop.
Also, thanks for documenting! :+1: :+1:

I found a several conflicts in this PR.
But it's hard to resolve the Swift issue for me.
So I made a new PR instead of this one.
https://github.com/stripe-samples/accept-a-payment/pull/639


Mini-canaloplasty

137760 GLAUCOMA, PRIMARY OPEN ANGLE; POAG
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC2813598/
This method was introduced by Rękas et al. and involves a mini-incision technique for accessing the Schlemm’s canal without the need to prepare the classical TDM and having to close sutures. The main difference of this variation is the size of the flaps created, the superficial flap having a diameter of 4.0 x 1.5 mm, and the deep flap 1.0 x 1.0 mm. After locating Schlemm’s canal, the ostium can be probed with iTrack and an OVD is injected at every 2 hours on removal. The tensioning suture is placed in the same way as in conventional canaloplasty. Finally, without the removal of the deep scleral flap or dissection of the intrascleral lake or the TDM, the conjunctiva is closed with diathermy. As there is no intrascleral lake, the hypotensive effect will only be induced thorough the tensioning suture in the Schlemm’s canal.

Is this a child of MAXO_0000959 canaloplasty?

Yes, this technique appears to be a variation of canaloplasty, which is represented by MAXO_0000959 in the Medical Actions Ontology (MAXO). It is essentially a modified canaloplasty procedure, with some key differences in the method of accessing Schlemm’s canal and the size of the flaps created. Therefore, it can be considered a 'child' or a specific type of the 'parent' procedure, canaloplasty.

added


TeX doesn't render

On pages like this one, there is use of LaTeX syntax for math, but it does not render correctly. It's probably missing a MathJax script?

Great catch! Thanks for pointing it out. I'll take a look


[cmake]: added cmake builds for benchmark, crypto, and libyuv

Summary

added cmake builds for benchmark, crypto, and libyuv
upstream fix some issues in cmake build process

Impact
Testing
CI

still some build errors :-(

still some build errors :-(

fixed 👨💻


GraphQL: search legal entities by address.area and address.settlement

Coverage increased (+0.05%) to 90.181% when pulling 917f36521c86cee7f0144fd26f0750e88d74e9ee on le-list into 26735b0e098074d87b92ab61ced71614a6013513 on develop.


Update README.md with a note for Impermanence Users

A note was added to the "Setting a user's password" part of the Read-me to help people avoid a serious pitfall. Warns Impermanence Users to link to they keyfile through there persist instead of the normal way.

I think there is a stright way to solve it.
Just set attr  program.openssh.hostKeys by self, make sure the each hostKeys path are storage in you persist path.
(This also can let ssh key static, not change after reboot because of data clear.)
And everything is ok, sops-nix will auto use it by default.
Like this:
{
  program.openssh.hostKeys = [
    {
        bits = 4096;
        path = "/persist/etc/ssh/ssh_host_rsa_key";
        type = "rsa";
      }
      {
        path = "/persist/etc/ssh/ssh_host_ed25519_key";
        type = "ed25519";
      }
  ];
}

That might be a good additional thing to add, but it is essentially the same point except with ssh instead of key files. Moving the key files to the persist directory so they are available at boot time before impermanence has run.

If you are sure this works

Yes, it is work. I build nixos and set user password with hashedPasswordFile with sops-nix.
That is my config

@mergify queue


JDK 18 Support

Fixes #19283
JaCoCo needs to be updated to 0.8.8 (not released yet) for some tests.
Spock needs to be updated to 2.2 (not released yet) for some tests.
Many tests involving Unicode and System.out capture are disabled due to #20267.
In my opinion, none of the above are blockers on this being merged.
@blindpirate I added you as reviewer, I wanted to make sure it was okay to merge the change I made to make this run Java 18 instead of Java 17 on CI. Perhaps we wish to test both 17 and 18? Not sure.

@bot-gradle test and merge

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

Pre-tested commit build failed.

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

Your PR is queued. See the queue page for details.

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

Pre-tested commit build failed.

@bot-gradle test and merge

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

Pre-tested commit build failed.

@bot-gradle test and merge

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


Added All Poloniex USDT Pairs

I've added all the USDT pairs for Poloniex. I'm working on getting Poloniex live trading implemented but it still needs a lot of testing since there is no 'market' price option in the Poloniex API and while I've been able to connect and place orders I am running into trouble getting the orders to actually fill instead of just placing an order and hoping it gets filled. If the buy/sell query doesn't completely fill orders and just sits there it will cause zenbot to only see the remaining balance (5% of total balance with zenbot's 95% trade defaults or whatever balance is remaining). I will probably end up having to tweak some things and have the trade logic look at the orderbooks and modify sitting orders.
I'm currently testing the 'fillOrKill', 'immediateOrCancel', and 'postOnly' parameters to figure out the most reliable method. I am also running into some errors with the nonce value (probably due to async) that Poloniex API requires but I should be able to figure that out.
Any suggestions would be much appreciated :)

very interesting, I didn't know Poloniex lacked the market option. It would certainly come in handy to have a trade strategy (alternate logic file) for using the order book instead of market flag. Hopefully we can convert it later into an abstraction for order books, so will be portable to other exchanges.

worth noting that i'm currently doing some refactoring to the default_logic.js for 3.5.0. the ROI went down to 1.1 at some point (when i added the fee calc probably) so i've been optimizing it back into 1.8 territory today

If the order book were to be used the balance/volume to be traded would need to be checked to make sure is below the amount of volume for that order price; if it was over, a couple of prices may have to be bought though (and total trade cost would need to take that into account), if that makes any sense?

@xangma yes, the market depth ideally would be tracked to calculate slippage
current default_logic.js just simulates the trade price (then if using the "run" command, syncs the real balance later and recalculates the ROI). this is handy for simulations but if you're trading large volumes on a real exchange you'd need more accurate price quotes.


Dl 5046

Hi @jgrath, I've closed this PR as it needs to be a PR merged into DL-4921-April-21 and not master


unittest: Add more files from Google

They were provided by Jeff Breidenbach<EMAIL_ADDRESS>Signed-off-by: Stefan Weil<EMAIL_ADDRESS>

@amitdo, yes, I should have suppressed the CI tests. :-(
Until next time ...

Some of the tests should be disabled when the legacy engine is disabled at compile time.


Unable to install daft on M2 Pro mac

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
> python -m pip install -U getdaft
> python -c "import daft";                                                                                04/30/2024 05:06:12 PM
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/Users/me/Development/daft-example/.venv/lib/python3.11/site-packages/daft/__init__.py", line 26, in <module>
    from daft.daft import build_type as _build_type
ImportError: dlopen(/Users/me/Development/daft-example/.venv/lib/python3.11/site-packages/daft/daft.abi3.so, 0x0002): Library not loaded: /opt/homebrew/opt/xz/lib/liblzma.5.dylib
  Referenced from: <C63B9E6D-3659-33B8-8821-FB3C4AFFE625> /Users/me/Development/daft-example/.venv/lib/python3.11/site-packages/daft/daft.abi3.so
  Reason: tried: '/opt/homebrew/opt/xz/lib/liblzma.5.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64')), '/System/Volumes/Preboot/Cryptexes/OS/opt/homebrew/opt/xz/lib/liblzma.5.dylib' (no such file), '/opt/homebrew/opt/xz/lib/liblzma.5.dylib' (mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e' or 'arm64'))

Expected behavior
doesn't panic on import
Additional context
we can statically link liblzma to avoid this all together.
I previously opened up some issues in various repos for similar issues

lancedb
datafusion
glaredb

@universalmind303 Yeah that would be great if you can push up a PR for this. I didn't realize we dynamically link to liblzma. on Linux we don't seem to have it
	linux-vdso.so.1 (0x00007ffca55ad000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f80f8ee3000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f80f8dfc000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f80f8bd3000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f8100b61000)

@samster25 feel free to assign to me and I can get a PR together pretty quick


fix matching of package versions on debian, ubuntu, and raspbian

relates to https://github.com/docker/docker-ce-packaging/pull/818

The version-format of the packages changed in the docker-ce-packaging repo; https://github.com/docker/docker-ce-packaging/commit/39772a761dfdf810cc23a1ec6084ea3100e6abf0
Which caused the script to fail when specifying a version:
INFO: Searching repository for VERSION '23.0.0-rc.2'
INFO: apt-cache madison 'docker-ce' | grep '23.0.0.*rc.2.*-0~debian' | head -1 | awk '{$1=$1};1' | cut -d' ' -f 3

ERROR: '23.0.0-rc.2' not found amongst apt-cache madison results

Looking at that search, it seemed like it was overly strict;

matching the distro (debian, ubuntu, or raspbian), which should not be needed, assuming the package repository has been set up correctly (which the script does in earlier steps).
matching the "0" prefix, which was intended to be used a package-revision (so to allow for packaging-only releases). That part definitely shouldn't be done, as it would not match later revisions (1, 2, 3)

This patch simplifies the matching, and only searches for the package name, and the version specified, which should satisfy the requirement;
apt-cache madison 'docker-ce' | grep '23.0.0.*rc.2' | head -1 | awk '{$1=$1};1' | cut -d' ' -f 3
5:23.0.0~rc.2-1~ubuntu.22.04~jammy

apt-cache madison 'docker-ce-cli' | grep '23.0.0.*rc.2' | head -1 | awk '{$1=$1};1' | cut -d' ' -f 3
5:23.0.0~rc.2-1~ubuntu.22.04~jammy

With this patch applied, the installation succeeds:
cat install.sh | DOWNLOAD_URL=https://download-stage.docker.com CHANNEL=test VERSION=23.0.0-rc.2 REPO_FILE=docker-ce-staging.repo sh
...
INFO: Searching repository for VERSION '23.0.0-rc.2'
INFO: apt-cache madison 'docker-ce' | grep '23.0.0.*rc.2' | head -1 | awk '{$1=$1};1' | cut -d' ' -f 3
INFO: apt-cache madison 'docker-ce-cli' | grep '23.0.0.*rc.2' | head -1 | awk '{$1=$1};1' | cut -d' ' -f 3
+ sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq --no-install-recommends docker-ce=5:23.0.0~rc.2-1~ubuntu.22.04~jammy docker-ce-cli=5:23.0.0~rc.2-1~ubuntu.22.04~jammy containerd.io docker-compose-plugin docker-scan-plugin docker-buildx-plugin >/dev/null

thx! bringing this one in, and I'll trigger a deploy of the script


Support for the error "array must be initialized with a brace-enclosed initializer"

Respected developers of the package
While building the package I encountered the error "array must be initialized with a brace-enclosed initializer, array must be initialized with a brace-enclosed initializer error_t error_{0, 0}; "
In the file
cslibs_math/cslibs_math_3d/include/cslibs_math_3d/algorithms/bresenham.hpp:130:22:
Can you address this issue and let me know how this can be solved.. Can it be compiler issue ?

Could you try replacing error_t error_{0, 0}; in exactly that line by the following?
error_t error_{{0, 0}};

This error might depend on the compiler you are using or its version.


refactor: add examples

Add standalone examples to the documentation as well as two examples at the top displaying how to type everything into a text box and how to print everything being said for quick start examples

Great, thanks a lot.


Update W2L for continuous processing

Includes a w2l file that listens directly to the microphone as well as one that listens to the audio topic (as apposed to the talking topic).

This got subsumed by the dialogue pattern branch


No war content at all in the generated image

Hi,
I use jib-maven-plugin for many war/jar projects and find it really useful.
But I came across a case of a war project where it doesn't work and I can't tell why. Everything seems to work as the image is correctly sent to the container registry. But the war content (exploded or not) is totally missing from the image (not even any class file). No log to tell what happened (even with -X and -Djib.serialize=true). The same occurs with another image or with jetty default image. And if I change the final name in the maven-war-plugin configuration (without packaging again), I get as expected an error saying that jib cannot find the war, so I guess jib can find the war and the error occurs later in the build. I use jib-maven-plugin 3.4.3 and maven-war-plugin 3.4.0. But it seemed to be the same with previous versions. Any idea ? How can I get more log otherwise ?
Thanks
Florent

Thanks for reaching out. Do you mind providing a minimum reproducible sample so we can better understand your problem?
Otherwise, our readme has a section on war project that might be helplful. And you could also check if your case falls into any of these cases that's not supported yet: https://github.com/GoogleContainerTools/jib/issues/1857

Thanks for the reply. I finally found out what was wrong on our project. But I still cannot explain the whole thing.
Our project was created with jhipster 6.10.5 (by cloning https://github.com/jhipster/jhipster-sample-app/tree/v6.10.5 one can get a project quite similar to ours) ... and it turns out that someone had changed the packaging type from war to jar (don't know why). By changing it back to jar everything works fine.
I tried to change the packaging type to war in the jhipster-sample-app but unfortunately it was not enough to reproduce (jib could package the war). There must be something else that has changed (another breaking action or maybe just a dependency update). This could be explored a little further. Uunfortunately I won't be able to provide a minimum reproducible sample due to lack of time. There is surely still work to do on this topic at least to make the log more relevant.


Can I use this on an already installed Windows OS?

Hey Freeman, I would like to know if I can setup tiered storage on my SSD (which has windows on it) and hook it up to my HDD (which has my games on it) without losing any data. Sort of like StoreMI, however I am on an Intel CPU.
Thanks!

You cant


Hover tool support

Because datashader produces an image rather than a collection of glyphs, there is no direct information available to the plotting program about the precise numerical values of plotted data.  This information can be made available separately from the image, in a way that a plotting program (e.g. Bokeh) can display using the "hover" or "tooltips" mechanism, revealing values corresponding to the current mouse pointer location.  At a minimum this information could just be the numerical value of that pixel, but it can be expanded to include counts and minimum/maximum values (if e.g. average or total values are being plotted), various statistical measures, etc.
It may be useful to bin this information on a grid coarser than the aggregation grid, which simply involves a pass over the aggregate grid to merge adjacent cells' data.  In this case, it would be helpful if the hover tool showed the outline of the grid cell whose data is being shown, for clarity.
Tasks (may need to be expanded):

[x] Implement fixed example of making information visible by hovering
[ ] Decide on an API for making the information available from the pipeline in general
[ ] Extend InteractiveImage to make use of data other than the image itself, perhaps by optionally accepting a dictionary or tuple, and grabbing the image key's value in that dictionary
[x] Update some of the examples to include hover information

Some of this implementation may overlap with the support for color keys/legends in issue #90, in that it requires the underlying library to make information available about the data shown in an image.

I'm not too much into the project's code, but I can help if you want.

@apaytuvi, thanks!  We'll certainly need testers, in any case, and would love to have feedback!

Has this been implemented? I'm happy to be a tester.


Forced sub syntax

Looked around but didn't see any mention of forced subs since 2013.
MKV:h264,dts5.1,subrip+forced
This is a fairly standard file, with the exception that it has a forced sub track.  Renaming the file output from movie.eng.srt -> movie.eng.forced.srt allows Plex to properly force the subs.
Would it be possible to handle these when splitting into external files, so that they are named movie.lan.forced.srt?

With plex your can easily tell it to automatically select the subs based on the language of the audio track:
Settings -> Server -> Languages:
Select [x] Automatically select audio and subtitle tracks.
Prefer Audio: [your language]
Subtitle Mode: Show with foreign audio (Alternatively you can just select "Always show subtitles regardless of audio language)
Prefer Subtitles: [your language]
Note in the transformers settings, you can specify to which language it should tag the audio track if there is no metadata for that track.

Feature added, please update


50 API specification changes

@thomose I'd merge both #52 and this one(#51) now. Do you have any objections?
I'd create a new branch with the new folder structure afterwards for the pending changes.

Summary of desired changes from the last meeting:
* [ ]  extend `components/schemas/Run` by [`mlflow/runs/get` response](https://www.mlflow.org/docs/latest/rest-api.html#get-run)

* [ ]  rework `components/schemas/ModelRepository`: rename,  compare with [`mlflow/registered-model/get` response](https://www.mlflow.org/docs/latest/rest-api.html#get-registeredmodel), decide whether to point to stored model or only code + commit depending on use cases

* [x]  Note down [use cases](https://docs.google.com/document/d/18g-OURZAC0Um7la8T3bzTLUh921MpswoNVc-K_CIh84/edit) in this repo

@DanielWeidinger who does what from this list? Please add further tasks in case I forgot something

@DanielWeidinger so the two open tasks in this comment are promoted to a new issue?

Summary of desired changes from the last meeting:
* [ ]  extend `components/schemas/Run` by [`mlflow/runs/get` response](https://www.mlflow.org/docs/latest/rest-api.html#get-run)

* [ ]  rework `components/schemas/ModelRepository`: rename,  compare with [`mlflow/registered-model/get` response](https://www.mlflow.org/docs/latest/rest-api.html#get-registeredmodel), decide whether to point to stored model or only code + commit depending on use cases

* [x]  Note down [use cases](https://docs.google.com/document/d/18g-OURZAC0Um7la8T3bzTLUh921MpswoNVc-K_CIh84/edit) in this repo

@DanielWeidinger who does what from this list? Please add further tasks in case I forgot something

@DanielWeidinger so the two open tasks in this comment are promoted to a new issue?

I would implement those under the same issue but new branch. Because I reckon it would be much easier to do them in the new folder structure.


Fix buttons with old props and new imports

We had a few instances where we imported the new button component but had the old props in place (variant instead of type). This resulted in buttons having the wrong styles.
I did a search for the new imports and replaced the wrong instances. Hopefully that should cover it all.

Coverage remained the same at 26.547% when pulling 83b2399bfbd2060cb7dbed44bcf5f18a37f9f8e8 on alioso:fix-buttons-with-old-props-and-new-imports into 0075d90ac5b47c603b0fb6628be1a08f32aa6dfb on linode:develop.

Looks good to me too


Email City Camp teams about registering for ATO

Done! I've gotten three responses already that teams will register.  If anyone has contacts with City Camp teams, please encourage them to sign up.


Added a program to calculate roots of a quadratic equation

Can you please check it again? This file is already in the Algorithms/Python folder

No, it's in algorithms/python.
Note the capitalization of folder names.

No, it's in algorithms/python. Note the capitalization of folder names.

And also change the filename format to camelCase.

Hey! Is it ok now?

Hey! Is it ok now?

Yes, it is okay now. Nice work, and thanks for the contribution.
Make sure to give me a follow on github.


Tab bar for desktop/desktop 974

@keybase/react-hackers
This adds the tab bar to the main app.

Todo

Figure out why the dumb sheet makes the desktop app fail without a filter ''

Add correct icon for search

Rebuild fonts (While rebasing before pushing I got a merge conflict with the kb.ttf)

Small cleanups

Let's walk through the font stuff
On Thursday, May 5, 2016, Marco Munizaga<EMAIL_ADDRESS>wrote:

@keybase/react-hackers
https://github.com/orgs/keybase/teams/react-hackers
This adds the tab bar to the main app.
[image: screen shot 2016-05-05 at 6 30 58 pm]
https://cloud.githubusercontent.com/assets/594035/15062032/e267e8fa-12f0-11e6-827f-1520d93e70b1.png
[image: screen shot 2016-05-05 at 6 41 30 pm]
https://cloud.githubusercontent.com/assets/594035/15062040/fff23cea-12f0-11e6-8bce-b086ce380cce.png
[image: screen shot 2016-05-05 at 6 42 02 pm]
https://cloud.githubusercontent.com/assets/594035/15062048/1a9d1bf0-12f1-11e6-9cfc-d163b1bae178.png
Todo

Figure out why the dumb sheet makes the desktop app fail without a
filter ''
Add correct icon for search
Rebuild fonts (While rebasing before pushing I got a merge conflict
with the kb.ttf)
Small cleanups

You can view, comment on, or merge this pull request online at:
https://github.com/keybase/client/pull/2782
Commit Summary

Add Desktop version of App's tab bar
Hook up TabBar to be used
Add new icons
Get click style and clean up
Temp fix for dumb-sheet

File Changes

M desktop/renderer/fonticon.css
https://github.com/keybase/client/pull/2782/files#diff-0 (21)
M desktop/renderer/fonts/kb.ttf
https://github.com/keybase/client/pull/2782/files#diff-1 (0)
M shared/common-adapters/avatar.js.flow
https://github.com/keybase/client/pull/2782/files#diff-2 (4)
M shared/common-adapters/dumb.desktop.js
https://github.com/keybase/client/pull/2782/files#diff-3 (94)
M shared/common-adapters/icon.js.flow
https://github.com/keybase/client/pull/2782/files#diff-4 (1)
M shared/common-adapters/icon.paths.native.js
https://github.com/keybase/client/pull/2782/files#diff-5 (9)
M shared/common-adapters/index.desktop.js
https://github.com/keybase/client/pull/2782/files#diff-6 (1)
A shared/common-adapters/tab-bar.desktop.js
https://github.com/keybase/client/pull/2782/files#diff-7 (163)
M shared/common-adapters/tab-bar.js.flow
https://github.com/keybase/client/pull/2782/files#diff-8 (2)
M shared/common-adapters/text.desktop.js
https://github.com/keybase/client/pull/2782/files#diff-9 (9)
A shared/images/icons/svgs/custom-main-nav-devices.svg
https://github.com/keybase/client/pull/2782/files#diff-10 (16)
A shared/images/icons/svgs/custom-main-nav-folders.svg
https://github.com/keybase/client/pull/2782/files#diff-11 (16)
A shared/images/icons/svgs/custom-main-nav-people.svg
https://github.com/keybase/client/pull/2782/files#diff-12 (16)
A shared/images/icons/svgs/custom-main-nav-settings.svg
https://github.com/keybase/client/pull/2782/files#diff-13 (16)
M shared/local-debug.desktop.js
https://github.com/keybase/client/pull/2782/files#diff-14 (5)
M shared/more/dumb-sheet.render.desktop.js
https://github.com/keybase/client/pull/2782/files#diff-15 (4)
M shared/nav.desktop.js
https://github.com/keybase/client/pull/2782/files#diff-16 (57)
A shared/tab-bar/dumb.desktop.js
https://github.com/keybase/client/pull/2782/files#diff-17 (52)
A shared/tab-bar/index.render.desktop.js
https://github.com/keybase/client/pull/2782/files#diff-18 (156)
M shared/tab-bar/index.render.js.flow
https://github.com/keybase/client/pull/2782/files#diff-19 (2)
M shared/tab-bar/index.render.native.js
https://github.com/keybase/client/pull/2782/files#diff-20 (2)

Patch Links:

https://github.com/keybase/client/pull/2782.patch
https://github.com/keybase/client/pull/2782.diff

—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly or view it on GitHub
https://github.com/keybase/client/pull/2782

👍

:+1:


Ore finder does not work in 1.20.1

When using the ore vein finder, it comes up with the chunk coords but does not say what vein it has found or where it has found it.

Please post your minecraft log

Most likely a hammerlib incompatibility like #61, fixed in the latest version


[GLITCH] Almost unusable after latest update.

I did a post on Reddit about this a few minutes ago, and seems like the right path is to report this glitch here too.
Saying it again, seems like some things broke after the latest beta update(99.0b2), maybe this glitch is on stable too.
List of things that broke are:

All three window control buttons are all glitched up.
The order is now back to default (minimize, maximize and close. it was inverted before the update).
The tab bar now got a darker spacing and don't auto-hide when there's a single tab anymore.
The favorite icon is stretched, and the back and forward buttons are just gone.

Plus some minor glitches that can be noticed on the screenshot attached.

Specs are: Windows 11 Laptop, using MyDockFinder for a Mac Style, Firefox Beta 99.0b2.
Please, fix this as soon as possible, as I love this theme a lot.
Thanks in advance.

Hi, it seems this theme bundles my theme inside it.
There are multiple fixes released since the version bundled that you can find here:
https://github.com/AdamXweb/WhiteSurFirefoxThemeMacOS/releases/tag/v1.4.2
Note, the file under chrome/WhiteSur/parts/windows.css has the update you're looking for


Added Creator in mock data

Added Creator in mock data
For already created WI's we need Creator to be assigned , so added that !

Can one of the admins verify this patch?

Current coverage is 52.64% (diff: 100%)

Merging #803 into master will not change coverage

@@             master       #803   diff @@
==========================================
  Files            42         42
  Lines          2234       2234
  Methods         428        428
  Messages          0          0
  Branches        441        441
==========================================
  Hits           1176       1176
  Misses         1058       1058
  Partials          0          0

Powered by Codecov. Last update cde3013...6a34b98


How to allow custom headers in Nginx Ingress controller

I have a nginx ingress controller running in AKS. One of my application is accessed using POSTMAN, in which I pass some custom headers and their values. The problem is that those custom header values are null when i see in the application.
What configuration should I do in my ingress controller to allow those header values to pass to my application. My ingress controller is sitting behind the Azure Network load balancer.

The scope for these doc issues is to help identify gaps and issues with the documentation. Is there something in any specific Azure AKS doc you are looking to have updated or are having issues with?
If yes, please provide us with the link to the documentation you are referring to so we can better assist.
Else, if you are looking for help with debugging issues I would suggest reaching out to the MSDN and Stack Overflow communities. Our team will help you there.

Is there any update? Please share the link to the doc you are following.

We will now close this issue. Please share the details or open a new issue on the particular document you have questions on.


New Release?

Hi there,
After the recent QOL changes, I was wondering when a new release might be tagged?
All the best,

Oh, sorry, completely forgot to release it.
6.5 is live now, thank you for your contributions!

I'm using the new release from conda ... but conda-forge build complains about the version number of pymetalink:
https://github.com/conda-forge/rooki-feedstock/pull/2
import: 'rooki'
+ pip check
rooki 0.6.3 has requirement pymetalink>=6.2, but you have pymetalink 0.
WARNING: Tests failed for rooki-0.6.3-pyhd8ed1ab_0.conda - moving package to /home/conda/feedstock_root/build_artifacts/broken
TESTS FAILED: rooki-0.6.3-pyhd8ed1ab_0.conda

The version number is "0":
https://github.com/metalink-dev/pymetalink/blob/ba74f9152d22b24e622a09b1d89a0f74631f0d12/pyproject.toml#L7

Hmm... This might be an issue from the conda packaging.

See #28


Get-DbaDiskSpace doesn't work with clusters

Is this a feature OR bug:
bug
Get-DbaDiskSpace doesn't work with FCI clusters -- they don't allow ipaddr connections
here's some code where i started working on it
https://github.com/sqlcollaborative/dbatools/commit/780a4d16cf26afa5731d71b106854d5086ace817

This will be resolved with @FriedrichWeinmann's fixes 💃

Wait, this is already fixed :D Nice work everyone!


chore: removed pytz from dependencies as it's not needed anymore

closes #6

This is actually a bit more complicated, we need to figure out where to get this data which currently comes from (private) pytz properties, without using pytz.

I investigated this further and decided not to remove pytz anymore: https://github.com/leonoverweel/tz-canary/issues/6#issuecomment-2460363922.