K8SPXC-257 Pod specific serviceAccount

GKE cluster shall be created with --local-ssd-count option for
this test

Test name
Status

storage
failed

recreate
failed

big-data
passed

init-deploy
failed

scaling
failed

restore-to-encrypted-cluster
passed

scaling-proxysql
passed

limits
passed

self-healing
failed

upgrade
passed

demand-backup
passed

self-healing-advanced
passed

monitoring
passed

upgrade-consistency
passed

security-context
passed

operator-self-healing
passed

monitoring-2-0
passed

affinity
passed

scheduled-backup
failed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

storage
passed

big-data
failed

scaling
passed

init-deploy
failed

recreate
failed

limits
passed

scaling-proxysql
passed

monitoring
failed

restore-to-encrypted-cluster
passed

monitoring-2-0
failed

affinity
passed

self-healing
passed

one-pod
failed

upgrade
passed

auto-tuning
passed

demand-backup
passed

self-healing-advanced
passed

proxysql-sidecar-res-limits
passed

upgrade-consistency
passed

security-context
passed

operator-self-healing
passed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

recreate
passed

scaling
failed

init-deploy
passed

big-data
passed

storage
passed

self-healing
passed

scaling-proxysql
passed

limits
passed

restore-to-encrypted-cluster
passed

monitoring
passed

upgrade
passed

self-healing-advanced
passed

upgrade-consistency
passed

operator-self-healing
passed

monitoring-2-0
passed

demand-backup
failed

security-context
failed

affinity
passed

one-pod
passed

scheduled-backup
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

recreate
passed

affinity
passed

restore-to-encrypted-cluster
passed

one-pod
passed

demand-backup
failed

auto-tuning
passed

scaling
failed

proxysql-sidecar-res-limits
passed

big-data
passed

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
failed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

scaling
passed

storage
passed

recreate
passed

self-healing
passed

restore-to-encrypted-cluster
passed

self-healing-advanced
passed

demand-backup
passed

operator-self-healing
passed

big-data
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
failed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

storage
passed

self-healing
passed

scaling
passed

self-healing-advanced
passed

scaling-proxysql
passed

operator-self-healing
passed

upgrade
passed

recreate
passed

big-data
passed

upgrade-consistency
passed

restore-to-encrypted-cluster
passed

security-context
failed

demand-backup
passed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

storage
passed

self-healing
failed

recreate
failed

big-data
failed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

init-deploy
passed

limits
passed

monitoring
passed

restore-to-encrypted-cluster
failed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

self-healing-advanced
passed

operator-self-healing
passed

demand-backup
passed

scheduled-backup
failed

demand-backup-encrypted-with-tls
passed

Test name
Status

recreate
passed

init-deploy
passed

big-data
passed

scaling
passed

storage
passed

self-healing
passed

limits
passed

scaling-proxysql
passed

monitoring
passed

restore-to-encrypted-cluster
passed

upgrade
passed

monitoring-2-0
failed

self-healing-advanced
passed

upgrade-consistency
failed

affinity
passed

security-context
passed

demand-backup
passed

operator-self-healing
passed

one-pod
failed

auto-tuning
passed

scheduled-backup
failed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

storage
passed

init-deploy
failed

scaling
failed

big-data
failed

recreate
failed

limits
passed

self-healing
passed

restore-to-encrypted-cluster
failed

monitoring
passed

self-healing-advanced
passed

monitoring-2-0
failed

demand-backup
passed

scaling-proxysql
failed

affinity
passed

operator-self-healing
passed

one-pod
passed

upgrade
passed

upgrade-consistency
failed

auto-tuning
passed

security-context
passed

scheduled-backup
failed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

recreate
passed

scaling
passed

big-data
passed

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

init-deploy
passed

scaling-proxysql
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

restore-to-encrypted-cluster
failed

demand-backup
passed

scheduled-backup
failed

upgrade
passed

upgrade-consistency
failed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

security-context
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

recreate
passed

big-data
passed

init-deploy
failed

scaling
passed

storage
passed

limits
passed

monitoring
passed

self-healing
failed

scaling-proxysql
passed

restore-to-encrypted-cluster
passed

self-healing-advanced
failed

upgrade
passed

monitoring-2-0
passed

affinity
passed

operator-self-healing
passed

upgrade-consistency
passed

demand-backup
failed

security-context
failed

one-pod
failed

scheduled-backup
failed

auto-tuning
passed

demand-backup-encrypted-with-tls
failed

proxysql-sidecar-res-limits
passed

Test name
Status

storage
passed

self-healing
failed

recreate
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

demand-backup
failed

big-data
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

self-healing-advanced
failed

scheduled-backup
failed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

demand-backup-encrypted-with-tls
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

operator-self-healing
passed

Test name
Status

storage
passed

self-healing
failed

big-data
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

self-healing-advanced
failed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

operator-self-healing
passed

scheduled-backup
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
passed

demand-backup-encrypted-with-tls
passed

storage
passed

self-healing
failed

scaling
passed

big-data
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

self-healing-advanced
failed

operator-self-healing
passed

Test name
Status

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

recreate
passed

proxysql-sidecar-res-limits
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
passed

demand-backup-encrypted-with-tls
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

big-data
passed

storage
passed

self-healing
failed

self-healing-advanced
passed

operator-self-healing
passed

Test name
Status

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
passed

demand-backup-encrypted-with-tls
passed

big-data
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

storage
passed

affinity
passed

self-healing
failed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

self-healing-advanced
passed

operator-self-healing
passed

Test name
Status

storage
passed

recreate
passed

scaling
passed

init-deploy
passed

big-data
failed

self-healing
failed

scaling-proxysql
passed

limits
passed

self-healing-advanced
failed

restore-to-encrypted-cluster
passed

upgrade
passed

monitoring
passed

upgrade-consistency
passed

operator-self-healing
failed

monitoring-2-0
passed

security-context
failed

demand-backup
passed

affinity
passed

one-pod
passed

scheduled-backup
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

storage
passed

self-healing
passed

recreate
passed

restore-to-encrypted-cluster
passed

scaling
passed

demand-backup
passed

scaling-proxysql
passed

scheduled-backup
failed

upgrade
passed

upgrade-consistency
passed

security-context
failed

big-data
failed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

self-healing-advanced
passed

operator-self-healing
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

recreate
passed

big-data
failed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

storage
passed

init-deploy
passed

self-healing
passed

limits
passed

self-healing-advanced
passed

monitoring
passed

operator-self-healing
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
failed

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

big-data
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

scaling
passed

scaling-proxysql
passed

big-data
failed

upgrade
passed

upgrade-consistency
passed

security-context
failed

init-deploy
passed

storage
passed

limits
passed

self-healing
passed

monitoring
passed

self-healing-advanced
passed

monitoring-2-0
passed

operator-self-healing
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

demand-backup-encrypted-with-tls
passed

Test name
Status

scaling
passed

init-deploy
passed

scaling-proxysql
passed

limits
passed

upgrade
passed

monitoring
passed

upgrade-consistency
passed

monitoring-2-0
passed

security-context
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

storage
passed

big-data
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

demand-backup-encrypted-with-tls
passed

Test name
Status

init-deploy
passed

limits
passed

monitoring
passed

recreate
passed

monitoring-2-0
passed

restore-to-encrypted-cluster
passed

affinity
passed

demand-backup
passed

one-pod
passed

scheduled-backup
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

storage
passed

self-healing
passed

big-data
passed

self-healing-advanced
passed

operator-self-healing
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

init-deploy
passed

scaling
passed

limits
passed

scaling-proxysql
passed

monitoring
passed

upgrade
passed

monitoring-2-0
passed

upgrade-consistency
passed

affinity
passed

security-context
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

big-data
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

big-data
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

big-data
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

recreate
passed

proxysql-sidecar-res-limits
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

storage
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

demand-backup-encrypted-with-tls
passed

PXC operator docker - perconalab/percona-xtradb-cluster-operator:PR-417-aefc4ce0

Test name
Status

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

storage
passed

recreate
passed

self-healing
passed

restore-to-encrypted-cluster
passed

self-healing-advanced
passed

demand-backup
passed

operator-self-healing
passed

scheduled-backup
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

big-data
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

init-deploy
passed

storage
failed

scaling
passed

big-data
passed

recreate
failed

self-healing
failed

limits
passed

scaling-proxysql
passed

self-healing-advanced
passed

monitoring
passed

upgrade
passed

operator-self-healing
passed

restore-to-encrypted-cluster
passed

monitoring-2-0
passed

upgrade-consistency
passed

security-context
passed

affinity
passed

demand-backup
passed

one-pod
passed

auto-tuning
passed

scheduled-backup
failed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

recreate
passed

storage
passed

big-data
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

self-healing
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
failed

self-healing-advanced
passed

operator-self-healing
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

storage
passed

big-data
passed

scheduled-backup
failed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

init-deploy
passed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

demand-backup-encrypted-with-tls
passed

Test name
Status

recreate
passed

init-deploy
passed

limits
passed

restore-to-encrypted-cluster
passed

monitoring
passed

demand-backup
passed

monitoring-2-0
passed

scheduled-backup
failed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

storage
passed

security-context
passed

self-healing
passed

self-healing-advanced
passed

operator-self-healing
passed

big-data
passed

demand-backup-encrypted-with-tls
passed

PXC operator docker - perconalab/percona-xtradb-cluster-operator:PR-417-c3b384c2

Test name
Status

big-data
passed

init-deploy
passed

storage
passed

limits
passed

self-healing
passed

monitoring
passed

self-healing-advanced
passed

monitoring-2-0
passed

operator-self-healing
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

recreate
passed

restore-to-encrypted-cluster
passed

demand-backup
passed

scheduled-backup
passed

scaling
passed

scaling-proxysql
passed

upgrade
passed

upgrade-consistency
passed

security-context
passed

demand-backup-encrypted-with-tls
passed


Redefinition of RefreshRuntime w/ Vite React app

There's an issue with this service that causes the react-refresh module to be loaded twice in Vite-based React apps, when testing with Webdriver.IO and with this service added to the configuration. It kinda seems like the preamble is being run twice. This prevents any tests reliant on the React DOM from working.
Here's an example of the broken preamble loaded into the browser:
import { createHotContext as __vite__createHotContext } from "/@vite/client";import.meta.hot = __vite__createHotContext("/src/App.tsx");import * as RefreshRuntime from "/@react-refresh";

if (!window.$RefreshReg$) throw new Error("React refresh preamble was not loaded. Something is wrong.");
const prevRefreshReg = window.$RefreshReg$;
const prevRefreshSig = window.$RefreshSig$;
window.$RefreshReg$ = RefreshRuntime.getRefreshReg("<project directory>/src/App.tsx");
window.$RefreshSig$ = RefreshRuntime.createSignatureFunctionForTransform;

var _s = $RefreshSig$();
import * as RefreshRuntime from "/@react-refresh";
if (!window.$RefreshReg$) throw new Error("React refresh preamble was not loaded. Something is wrong.");
const prevRefreshReg = window.$RefreshReg$;
const prevRefreshSig = window.$RefreshSig$;
window.$RefreshReg$ = RefreshRuntime.getRefreshReg("<project directory>/src/App.tsx");
window.$RefreshSig$ = RefreshRuntime.createSignatureFunctionForTransform;

For comparision, it should look like this:
import { createHotContext as __vite__createHotContext } from "/@vite/client";import.meta.hot = __vite__createHotContext("/src/App.tsx");import * as RefreshRuntime from "/@react-refresh";

if (!window.$RefreshReg$) throw new Error("React refresh preamble was not loaded. Something is wrong.");
const prevRefreshReg = window.$RefreshReg$;
const prevRefreshSig = window.$RefreshSig$;
window.$RefreshReg$ = RefreshRuntime.getRefreshReg("<project directory>/src/App.tsx");
window.$RefreshSig$ = RefreshRuntime.createSignatureFunctionForTransform;

I'm using Node 20.10.0, Vite 5.0.12, Webdriver.IO 8.29.7, and wdio-vite-service 1.0.6. Disabling the service in wdio.conf.ts and manually pointing the baseurl to Vite's expected port works as expected.

@WilliamImm thanks for raising the issue. Do you think it is possible to create a reproducible example of this?

@WilliamImm thanks for raising the issue. Do you think it is possible to create a reproducible example of this?

Of course. I've uploaded a reproducible build based on the Vite React TS starter. Use pnpm instead of npm, but otherwise this should be fairly straightforward to set up.
react-webdriver-test.tar.gz
The most relevant files to modify are wdio.conf.ts and e2e/test.e2e.ts, I've included an in-browser debug command too.
Hopefully this works, and if you need more information, please let me know.

@WilliamImm mind sharing this as GitHub repository?

Thanks @WilliamImm , I was able to reproduce this.
We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers!


Support Airflow 2.x operators (runtime specific components)

What changes were proposed in this pull request?
Support Airflow 2.x operators (runtime specific components)
Fixes #2124
After updating the elyra examples to have Airflow 2.x components, and register that in Elyra, I can see the airflow components and have the properties show up ok on the Pipeline Editor

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Yeah, there are still some changes necessary at component_parser_airflow, though.
Even though the GIU presence of the operators is ok, when assembling the DAG code from the values and defaults entered, e.g. from Bash operator, the assembled DAG is not correct.
https://github.com/elyra-ai/elyra/pull/3208#issuecomment-2326316000
Thank you though for making this starter-PR more complete in the other aspects here. I will see what I can find out about the inner workings of component_parser_airflow in conjunction with the new airflow operator classes.


Lack of support for testing text output produced by Schematron property elements

I've noticed that XSpec doesn't support testing the text content of Schematron properties in the output produced by an assert or report (unlike diagnostics output).
The Writing Scenarios for Schematron Wiki page has the following, which looks like property output is specifically excluded: "Starting in XSpec v3.0.3, the x:expect-assert and x:expect-report elements can also have text content that identifies an expected assert or report by its message or diagnostic."
Is there a reason for this?

The text support in XSpec v3.0.3 was a response to feature request #1634. That issue didn't mention properties and when working on the support for #1634, I didn't think about whether properties should be in scope or not.
Are you requesting support for properties/property as described in https://schematron.com/home/whyisschematrondifferent_.html#fragment-9-toc-16 ? If so, is there anything else you'd like to share about your use case that might help with the design or prioritization?
Cc: @AndrewSales

I like your idea of supporting the testing of property text in a way similar to testing diagnostic text and message text.
Possible alternative: I considered whether the support for testing properties should be different from the support for testing diagnostics. From Erik Siegel's Schematron book, I get the impression that diagnostics are like alternative messages for end users, while properties are more for arbitrary post-processing of SVRL validation results (possibly to benefit someone other than owners of the documents being validated). Maybe in properties used for post-processing, descendant elements are important and the string value isn't what's most worthwhile to test. However, after consideration, I feel inclined to keep the simple things simple (see Example 1).
XSpec users can always use x:expect to test properties in more flexible ways (see Example 2).
Example 1
If we enhance XSpec to handle properties and diagnostics in a similar manner, then a text-oriented Schematron property like
<sch:property id="prop-simple">String value of
this property</sch:property>

would be testable with a simple XSpec element that isn't fussy about whitespace.
<x:expect-assert>String value of this property</x:expect-assert>
<!-- or -->
<x:expect-assert>
  String value of this property
</x:expect-assert>

Example 2
A more data-centric Schematron property like
<sch:property id="prop-data">
    <user-data>
        <elem1 id="id1">user content</elem1>
        <elem2 id="id2">More user content</elem2>
    </user-data>
</sch:property>

is testable with <x:expect>, even without an XSpec enhancement:
<x:expect label="prop-data captured with SchXslt (Note: Fails in skeleton implementation)"
    test="//svrl:failed-assert/svrl:property-reference[@property='prop-data']"
    as="element(svrl:property-reference)">
    <svrl:property-reference property="prop-data">
        <svrl:text>
            <user-data>
                <elem1 id="id1">user content</elem1>
                <elem2 id="id2">More user content</elem2>
            </user-data>
        </svrl:text>
    </svrl:property-reference>
</x:expect>

Note that the skeleton implementation of Schematron uses different SVRL markup, and the <x:expect> element would look like this:
<x:expect label="prop-data captured with skeleton (Note: For skeleton only; fails in SchXslt)"
    test="//svrl:failed-assert/svrl:property[@id='prop-data']"
    as="element(svrl:property)">
    <svrl:property id="prop-data">
        <user-data>
            <elem1 id="id1">user content</elem1>
            <elem2 id="id2">More user content</elem2>
        </user-data>
    </svrl:property>
</x:expect>

+1 from me as well. The discrepancy between SchXslt and Skeleton is due to a different interpretation of the SVRL grammar in Annex D.
I raised https://github.com/Schematron/schematron-enhancement-proposals/issues/79 to clarify.


scroll To Index out of range

Summary
Bug report in one concise sentence
App crashed with error: scroll To Index out of range
Environment Information

Device Name: Realme 3 Pro
OS Version: Android 10
Mattermost App Version: 1.44.0
Mattermost Server Version: 5.35.0

Installed the app. Joined a community. Read some messages. Opened the app after 10 days. Saw a blue banner at the top saying "445 unread message". Clicked on it. App crashed.

@ganpa3 thanks for the report, I've submitted a fix to be included in the next release ;)


createMemo computed value always fires even though it didn't change, when wrapped in suspense.

Describe the bug
Create memo value is observed inside createEffect on every change even though computed value itself did not change. That only happens when <Routes /> is wrapped in <Suspense />
To Reproduce
Provide a code snippet and steps to reproduce the behavior:

Go to https://codesandbox.io/s/flamboyant-sea-9y52b?file=/index.js:978-1031
Click on different links
See that createEffect fires on every page change, even though computed boolean value is the same.

const usersMatch = useMatch(() => "/users/*");
const isUsersRoute = createMemo(() => Boolean(usersMatch()));
createEffect(() => {
  // Should only fire when boolean value changes,
  // but now it fires on every page change.
  console.log("is Users route", isUsersRoute());
});
<Suspense>
  <Routes />
</Suspense>

Expected behavior
createEffect only fires boolean value actually changes.
Reproduction
Reproduction
Additional context
The last working Solid version was 1.1.0, all other newer versions have this bug.

Ok should be fixed in 1.1.4. This one was tricky to notice at first and trickier to track down. But it was just an omission made to a more comprehensive bug fix I did in 1.1.1. Thanks for reporting.


Make CSWAP a bloq of its own

The cswap implementation
https://github.com/quantumlib/Qualtran/blob/3f325ce16ab44890a9e2150338e11cee0a4a8225/qualtran/bloqs/arithmetic/comparison.py#L258
should be a block of its own

we of course already have https://github.com/quantumlib/Qualtran/blob/95141395bdb1384a08b87874bba1977ddc28568a/qualtran/bloqs/basic_gates/swap.py#L107


Unity 2022.3.7f1 Error on import

Hey @Andrea332 it seems that you are missing import EosSharp
https://github.com/liquiidio/EosSharp.git#upm


support for UICollectionView with paging

Is your feature request related to a problem? Please describe.
I'm trying to implement UICollectionView with diffable data source like DifferenceKit (https://github.com/ra1028/DifferenceKit). It is suggested to use such framework with paginated data source, because when we have 20-30k elements in our database we have perfomance issues when data source is changed.
Say if we have some photos backup storage with 30k items and we downloading list of the images into our app with chunks of data by 500 items, and save them to CoreData or Realm and we should display them like in google photos app. So if we already have 10k items and we periodically adding items our app freezes.
Describe the solution you'd like
So target is to display say 1000 items and load from core data when user scrolling down
But we need FastScroll to work across ALL (maybe 20-30k) stored items
Is it possible?

Did you ever resolve this?  We also have to page the results in and this solution doesn't work for us.


v1.10.1: What is happening with Common Pb?

I have a couple of different questions, which I am binding together here because they might be related: I don't know, because I no longer understand how Squid3 treats common Pb.
My Project still has a Default Common Pb model specified in the Manage Project screen, but the Default Model values don't seem to be used anywhere. Instead, in the Expression Manager, common Pb for my Reference Materials seems to be treated exactly as if they were Unknowns. Don't understand this, definitely not what I want, and there doesn't seem to be any way to alter the behaviour (Built-in expression Com_206Pb204Pb, for example, does not seem to be editable).
I don't mind it working the way it currently does for the Unknowns, but for Ref Materials, I want Com_206Pb204Pb (for example) = DefCom_206Pb204Pb. How do I achieve this, when my Common-Pb Model is no longer being used in the Expression calculations?
Possibly related question: why are Expressions classified as "Reference Material Values" or "Parameters" not available in the Custom Report Builder? If I could select DefCom_206Pb204Pb for insertion as a column in my Ref Material template, that would help (although it wouldn't address the fact that the DefCom value is not currently being used to calculate 4cor_Com206Pb_Pct_RM, for example).
Here is a ZIP of my Project file: 170111_GA6357_Sq3-1.10.1_Perm1.zip

@sbodorkos - definitely a bug where the common lead calculations for the unknowns also were recalculating the common lead for the reference materials in some cases.  This was not caught by our current test suite since it does not cover the common lead calculations.  The new test suite that you are working on will do so.

This bug was introduced as a side-effect of changing the default common-lead scheme.  My apologies.  Next release contains fix and more ...

Expressions classified as "Reference Material Values" or "Parameters" are not spot-specific, so they were not included in spot reports.  They are included in the Summary Expressions and Values report - which needs feedback and improvement over its initial (and never updated) implementation.  Now that the bug is fixed, everything works as it did before and you can access the common lead values for reference material spots using the spot metadata fields in reports for reference materials.  New version shortly.


use plus and minus signs instead of thumbs for better readablity

@TheHippo Thank you, I tried that but didn't like the results. That plus/minus signs look too bold however thumbs up/down appear like more polite version.
/cc @qiangxue @MakoTano Could you share your opinion on that?

I get what you are saying. It kind of depends on which OS / browser you are using, but some combination do not look as good as others.


Calculate volume size

SWC is a representation of neurons composed of the radius of points and their connectivity, therefore there are various specific ways of representation. A typical method is to consider the nodes as spheres, and the connections between them as truncated cones with different radii at the top and bottom surfaces. We can at least support the volume calculation in this manner.

closed as v0.14.0(5ccb582) has been released


Added MMR experiment to main.py in server repo

closes #14

Copied MMR code from this PR to the main branch by hand to avoid conflicts.


added functional test

Runs a local cluster with tiup
Runs the python client against it

Could you add the test to ci?

@andylokandy I am not sure why it does not trigger the GH action on pull_request maybe because I forked in another repo?

Could you add the test to ci?

@andylokandy  Done -- I skipped Windows I am not sure how to start tiup in that environment in a robust way

Awesome! Thank you!


Write documentation page for local server client setup

Self signed cert and letsencrypt preferably

Arbius has a $100 AIUS bounty for this issue!
Brief: Write documentation page for local server client setup.
Please read carefully:
To begin work on a bounty, reply by saying “I claim this bounty” - you will have 48 hours to submit your PR before someone else may attempt to claim this bounty.
To complete the bounty, within 48 hours of claiming, reply with a link to your PR referencing this issue and an Ethereum address. You must comply with reviewers comments and have the PR merged to receive the bounty reward. Please be sure to focus on quality submissions to minimize the amount of time reviewers must take.


Disable P2P in just the 4000 series

What does this PR do?
My research was a bit off, the 3090's can still do P2P from what this user reports, so I adjusted the limit to only happen on 40* series.
Fixes https://github.com/huggingface/accelerate/issues/2328
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@SunMarc

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Add new partial translations for a few locales

Description
Add new partial translations for:

zh-TW
zh-CN
tr-TR
pt-PT
pt-BR
ko-KR
ja-JP
it-IT
id-ID
fr-FR
fr-CA
es-ES
es-419
de-DE

These are incomplete and the formats mimick en. Now that Intl is matured enough, we probably should drop the requirement for formats.
Check List

[ ] New locale: New issue has been opened in OpenSearch Dashboards for support.
[ ] New locale: DEVELOPER_GUIDE has been updated.
[X] Commits are signed per the DCO using --signoff

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

Thanks @Swiddis. This is great.


Merge fails depending on dtypes and npartitions

Apparently dask.dataframe.merge fails under some circumstances if the common columns have different data types while being otherwise identical. E.g. merge(df1[id1, id2, value1], df2[id1, id2, value2], on=['id1', 'id2'], how='left') would result in a table where some or all values of value2 are NaN if df1.id1.dtype is float64 and df2.id1.dtype is int64. The same merge operation would succeed if all corresponding id columns were either floats or ints. This behavior depends on the number of chunks in the dataframes.
Would it make sense to throw a warning if merge columns have different dtypes?

Example
In the example below the function test_dtype_merge produces some sample dataframes and performs a merge operation for different dtypes and npartitions. The merge has failed if any of the value columns from the right-hand table are nan. This is the case if the dtypes are different and the right table has npartitions > 1 (#NaN: 3 in the printed results below).
import dask
import numpy as np
import pandas as pd
import dask.dataframe as dd

list_dtypes = [(np.float64, np.float64, np.float64, np.float64),
               (np.float64, np.int64, np.float64, np.int64),
               (np.float64, np.float64, np.float64, np.int64),
               (np.float64, np.int64, np.float64, np.float64)]

def test_dtype_merge(npartitions_left, npartitions_right):

    print('npartitions_left=%s, npartitions_right=%s'%(npartitions_left,
                                                       npartitions_right))

    df = pd.DataFrame({'id_1': [0,1] * 3, 'id_2': [0] * 3 + [1] * 3,
                       'id_3': [0, 0, 1, 1, 2, 2], 'val_1': np.random.random(6)})

    df_join = df[['id_1', 'id_2']].drop_duplicates()
    df_join['val_2'] = np.random.random(len(df_join))

    df = dd.from_pandas(df, npartitions=npartitions_left)
    df_join = dd.from_pandas(df_join, npartitions=npartitions_right)

    on_cols = ['id_1', 'id_2']

    for t1, t2, t3, t4 in list_dtypes:

        df_join.id_1 = df_join.id_1.astype(t1)
        df_join.id_2 = df_join.id_2.astype(t2)
        df.id_1 = df.id_1.astype(t3)
        df.id_2 = df.id_2.astype(t4)

        df_result = dd.merge(df, df_join, on=on_cols,
                                         how='left').compute()

        print('#NaN: %d'%df_result.val_2.isna().sum(), t1, t2, t3, t4)

In [3]: test_dtype_merge(1, 2)
   ...:
npartitions_left=1, npartitions_right=2
#NaN: 0 <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'>
#NaN: 0 <class 'numpy.float64'> <class 'numpy.int64'> <class 'numpy.float64'> <class 'numpy.int64'>
#NaN: 3 <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.int64'>
#NaN: 3 <class 'numpy.float64'> <class 'numpy.int64'> <class 'numpy.float64'> <class 'numpy.float64'>

In [4]: test_dtype_merge(1, 1)
npartitions_left=1, npartitions_right=1
#NaN: 0 <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'>
#NaN: 0 <class 'numpy.float64'> <class 'numpy.int64'> <class 'numpy.float64'> <class 'numpy.int64'>
#NaN: 0 <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.int64'>
#NaN: 0 <class 'numpy.float64'> <class 'numpy.int64'> <class 'numpy.float64'> <class 'numpy.float64'>

In [5]: test_dtype_merge(2, 1)
npartitions_left=2, npartitions_right=1
#NaN: 0 <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'>
#NaN: 0 <class 'numpy.float64'> <class 'numpy.int64'> <class 'numpy.float64'> <class 'numpy.int64'>
#NaN: 0 <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.int64'>
#NaN: 0 <class 'numpy.float64'> <class 'numpy.int64'> <class 'numpy.float64'> <class 'numpy.float64'>

In [6]: test_dtype_merge(2, 2)
npartitions_left=2, npartitions_right=2
#NaN: 0 <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'>
#NaN: 0 <class 'numpy.float64'> <class 'numpy.int64'> <class 'numpy.float64'> <class 'numpy.int64'>
#NaN: 3 <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.int64'>
#NaN: 3 <class 'numpy.float64'> <class 'numpy.int64'> <class 'numpy.float64'> <class 'numpy.float64'>

In [7]: test_dtype_merge(3, 1)
npartitions_left=3, npartitions_right=1
#NaN: 0 <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'>
#NaN: 0 <class 'numpy.float64'> <class 'numpy.int64'> <class 'numpy.float64'> <class 'numpy.int64'>
#NaN: 0 <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.int64'>
#NaN: 0 <class 'numpy.float64'> <class 'numpy.int64'> <class 'numpy.float64'> <class 'numpy.float64'>

In [8]: test_dtype_merge(1, 3)
npartitions_left=1, npartitions_right=3
#NaN: 0 <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'>
#NaN: 0 <class 'numpy.float64'> <class 'numpy.int64'> <class 'numpy.float64'> <class 'numpy.int64'>
#NaN: 3 <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.float64'> <class 'numpy.int64'>
#NaN: 3 <class 'numpy.float64'> <class 'numpy.int64'> <class 'numpy.float64'> <class 'numpy.float64'>

Just to make sure I understand, does the following example correctly describe your issue?
In [23]: df1 = pd.DataFrame({"A": np.arange(10), "B": np.arange(10)})

In [24]: df2 = pd.DataFrame({"A": np.arange(10).astype(float), "B": np.arange(10)})

In [25]: a = dd.from_pandas(df1, 2)

In [26]: b = dd.from_pandas(df2, 2)

In [27]: dd.merge(a, b, on=['A'])
Out[27]:
Dask DataFrame Structure:
                   A    B_x    B_y
npartitions=2
               int64  int64  int64
                 ...    ...    ...
                 ...    ...    ...
Dask Name: hash-join, 34 tasks

In [28]: dd.merge(a, b, on=['A']).compute()
Out[28]:
   A  B_x  B_y
0  0    0    0
1  4    4    4
2  5    5    5
3  6    6    6
4  8    8    8

I think this comes from how we shuffle join in this case. The values we expect to be in the same partition aren't, presumably because of the dtype issue.
(Pdb) pp lhs2.get_partition(0).compute()
   A  B
1  1  1
9  9  9
(Pdb) pp rhs2.get_partition(0).compute()
     A  B
7  7.0  7
2  2.0  2
3  3.0  3

In general, pandas allows for joining on different dtypes with a cast. Typically the cast is to object (but I guess pandas has a special case for float -> int when all the floats are representable ints; I suppose you can know ahead of time that the intersection of a float and int will be an int...). I'm not sure what's best here yet.

Yes, seems to be the same issue. I modified your example a bit to reproduce the nans I got:
In [38]: df1 = pd.DataFrame({"A": list(np.arange(5).astype(float)) * 2,
    ...:                     "B": list(np.arange(5)) * 2})
    ...:

In [39]: df2 = pd.DataFrame({"A": np.arange(5), "B": np.arange(5)})

In [40]: a = dd.from_pandas(df1, 2)

In [41]: b = dd.from_pandas(df2, 2)

In [42]: dd.merge(a, b, on=['A'], how='left').compute()
Out[42]:
     A  B_x  B_y
0  2.0    2  NaN
1  3.0    3  NaN
2  2.0    2  NaN
3  3.0    3  NaN
0  0.0    0  0.0
1  1.0    1  NaN
2  4.0    4  4.0
3  0.0    0  0.0
4  1.0    1  NaN
5  4.0    4  4.0

I understand implicit type casting would be a problem in dask as compared to pandas. I do think a warning would be sufficient to address the issue. Alas, it would have in my case... :)

Yeah, a warning seems fine as a stopgap. I don’t know if pandas’s type casting rules are stable enough for us to do anything better right now.

On Mar 11, 2019, at 15:30, mcsoini<EMAIL_ADDRESS>wrote:
Yes, seems to be the same issue. I modified your example a bit to reproduce the nans I got:
In [38]: df1 = pd.DataFrame({"A": list(np.arange(5).astype(float)) * 2,
...:                     "B": list(np.arange(5)) * 2})
...:
In [39]: df2 = pd.DataFrame({"A": np.arange(5), "B": np.arange(5)})
In [40]: a = dd.from_pandas(df1, 2)
In [41]: b = dd.from_pandas(df2, 2)
In [42]: dd.merge(a, b, on=['A'], how='left').compute()
Out[42]:
A  B_x  B_y
0  2.0    2  NaN
1  3.0    3  NaN
2  2.0    2  NaN
3  3.0    3  NaN
0  0.0    0  0.0
1  1.0    1  NaN
2  4.0    4  4.0
3  0.0    0  0.0
4  1.0    1  NaN
5  4.0    4  4.0
I understand implicit type casting would be a problem in dask as compared to pandas. I do think a warning would be sufficient to address the issue. Alas, it would have in my case... :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@mcsoini do you have an interest in submitting a PR to raise a warning? Definitely no obligation though

yes, seems like to a good excuse to get more familiar with the codebase

De : James Bourbeau<EMAIL_ADDRESS>Envoyé : mercredi 17 avril 2019 04:01:04
À : dask/dask
Cc : Martin Soini; Mention
Objet : Re: [dask/dask] Merge fails depending on dtypes and npartitions (#4574)
@mcsoinihttps://github.com/mcsoini do you have an interest in submitting a PR to raise a warning? Definitely no obligation though
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dask/dask/issues/4574#issuecomment-483908079, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aflu03pWQKCiLD4vLAg2CotivpCzaR5Lks5vhoBggaJpZM4bmtgF.

Great, thanks @mcsoini!

Checking in here @mcsoini is this still something that you're interested in?  (no pressure, just figuring out if I should close this issue out or not)

Yes, still interested, just fairly busy these days.

De : Matthew Rocklin<EMAIL_ADDRESS>Envoyé : mardi 30 avril 2019 18:16:45
À : dask/dask
Cc : Martin Soini; Mention
Objet : Re: [dask/dask] Merge fails depending on dtypes and npartitions (#4574)
Checking in here @mcsoinihttps://github.com/mcsoini is this still something that you're interested in? (no pressure, just figuring out if I should close this issue out or not)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dask/dask/issues/4574#issuecomment-488016965, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AH4W5UZL5IM44XED7YD5JQDPTBWG3ANCNFSM4G423ACQ.

Fixed by @4917.


DateTime instead LocalDateTime?

why you did not implement with dart DateTime? It would be much better...

v0.2.0 no longer uses time_machine, but Dart's DateTime instead.


Update README.md

This does not appear to be an improvement?

Just a little http to https "typo", even if the http is still redirecting to the secure equivalent..

I would leave the URL in the text.


Reimplement string formatting

Currently, @Step, @Attachment, allure.createStep, etc. have incovenient formatting via %s and %d. It can be significantly improved if we switch to Handlebars.js, e.g.:
const Handlebars = require('handlebars');

// Create a new Handlebars environment and put it into Allure Runtime
const myHandlebarsInstance = Handlebars.create();

// The instance can be used for registering helpers
myHandlebarsInstance.registerHelper('percent', () => {
    // Helper implementation
});

The coolest thing about it is that if we combine it with function parsing, e.g.:
const { parseFunction } = require('parse-function')();

function wrapWithLogger(templateString, fn) {
    // Compile the Handlebars template
    const template = myHandlebarsInstance.compile(templateString);

    // Parse the provided function to get its arguments names
    const parsedFn = parseFunction.parse(fn);

    return function (...args) {
        // Create an object to map argument names to their values
        const scope = parsedFn.args.reduce((acc, arg, index) => {
            acc[arg] = args[index];
            return acc;
        }, args);

        // Use the constructed scope to populate the template and log the message
        const message = template(scope);
        console.log(message);

        // Call the original function with all its arguments
        return fn.apply(this, args);
    };
}

// Example usage
function assertSum(a, b, c) {
    return a + b === c;
}

const loggedAssertSum = log("Adding {{0}} and {{b}} = {{c percent}}", assertSum);
const result = loggedAssertSum(5, 3, 8);  // Logs: "Adding 5 and 3 = 800%"

Impact
Early adopters using:
@Step("Type text: %s")

will have to switch to this syntax:
@Step("Type text: {{0}}")

@MetodievIvaylo, could you assess how much it will impact you regarding rewriting? The reporter is still in beta, and I'm somewhat indulging in breaking some features to improve them before the stable release. If this hurts, I'll create a fallback for you.

Released in 2.0.0-beta.15.


No position transformer available for cloud

Hi, all,
I've had no problem in displaying pointclouds in rviz with the pcd files made by using Autoware (ndt_mapping). Note that this map should be based on the local coordinate. Because a map based on the global coordinate is required, I contracted one of the map data suppliers (like Aisan) and they've produced pcd files. However, pointclouds in this file could not be displayed in rviz, throwing an error called 'No position transformer available for cloud'. Note that tf.launch is as-is, which means (0, 0, 0).

@kitsukawa, Is the cause of this problem related to
https://github.com/CPFL/Autoware/issues/1127
https://github.com/CPFL/Autoware/issues/492
?
Thanks for your considerations.
Specifications

Ubuntu version: 16.04
ROS version: Kinetic
Autoware branch: Master

@wsung1 I can not tell the reason of the error unless I have a look at the PCDs.


feat(pinia-orm): add life-cycle-hooks

Thoughts
Adding local & global life cycle hooks like retrieved, creating, created, updating, updated, saving, saved, deleting, deleted.
ToDos

[x] Creating
[x] Created
[x] Updating
[x] Updated
[x] Deleting
[x] Deleted
[x] Retrieved
[x] Saving
[x] Saved
[x] Docs

Examples
    class User extends Model {
      static entity = 'users'

      @Num(0) id!: number
      @Str('') name!: string
      @Num(0) age!: number

      static updating(model: Model) {
        model.name = 'John'
      }
    }

Codecov Report

Merging #91 (6f98f81) into master (0a7b6b9) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master      #91   +/-   ##
=======================================
  Coverage   99.59%   99.59%
=======================================
  Files          51       51
  Lines        4181     4206   +25
  Branches      317      322    +5
=======================================
+ Hits         4164     4189   +25
  Misses         17       17

Impacted Files
Coverage Δ

packages/pinia-orm/src/model/Model.ts
100.00% <100.00%> (ø)

packages/pinia-orm/src/query/Query.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

would it be an idea to add find hooks as well? would make sense to complete CRUD support

@erikpols yes it would make sense. As you can see, initially I intended to have retrieve. But I reliesed that it's a bit more difficult. That's why I dropped it first.
The problem right now is that the get method is used also internally. So I would get many retrieved hooks.
But still... your right. I try to find a solution. Not just for find.

gotcha ty!
There are a few others too, for bulk updates for example. This is useful if you want to use the hooks for axios calls.


test: add tests for middleware bodies

This adds a few simple tests for handling bodies which originated from other middleware (i.e. req.body is set).
I was digging around the code to see how it works and figured i'd add these in

Greetings, and sorry for the comically late response.  If you'd be willing to rebase and make sure these still pass, happy to accept the PR!

no worries, have rebased for you 👍
thanks for ending up this deep in old PRs 😅


WM5 | Aisha_Athman_Lali | HTML-CSS-Module | Form controls | Week 2&3

Learners, PR Template
Self checklist

[ ] I have committed my files one by one, on purpose, and for a reason
[ ] I have titled my PR with COHORT_NAME | FIRST_NAME LAST_NAME | REPO_NAME | WEEK
[ ] I have tested my changes
[ ] My changes follow the style guide
[ ] My changes meet the requirements of this task

Changelist
Briefly explain your PR.
Questions
Ask any questions you have for your reviewer.

The Netlify link doesn't work.


Hacktoberfest PR First Timer

PR for the sake of Hacktoberfest.

@BMayUSA Congrats on your first PR!


Running Get-Remote more than once from same Powershell Session crashes.

Running Get-Remote Multiple times from same Powershell Session crashes.
This happens with all types Basic, Banana, Potato.
Found while running my own script multiple times in Powershell, which gave me error:
You cannot call a method on a null-valued expression.
At D:\Downloads\test.ps1:22 char:1
+ $vmr.Logout()
+ ~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull

#Test Script
Import-Module Voicemeeter
try {
    # Run the factory function for required Voicemeeter type
    $vmr = Get-RemotePotato
#Do other stuff here in my script
}
finally {
$vmr.Logout()
}

Attempts to narrow it down with try/catch blocks in Get-Remote and constructor methods were unsuccessful. It crashes the whole Powershell window.

Wrapping contents of Get-Remote function in try/catch.
Wrapping contents of Remote constructor in try/catch.

Hello, this issue arises due to the fact that Logout() is called on the vmr object in the finally block. The voicemeeter api was designed such that login is called once at the start and logout once at the end of the code. I'm not sure what your intended use with this wrapper is but perhaps you can try calling the Get-Remote function outside of a try/finally block, using the vmr object however many times you need and then manually invoking logout when you need to.
You wouldn't want to call Get-Remote functions multiple times without first logging out since that would lead to undefined behaviour. Being unable to login after logout, however, is a limitation of the API rather than this wrapper, as that is how the developer intended it be interacted with.
I hope that is helpful.

Confirmed by modifying Voicemeeter.psm1 as follows:
    [void] Setup() {
        if(Setup_DLL) {
            #Login -TYPE $this.type

            $this.button = Buttons
            $this.strip = Strips
            $this.bus = Buses
            $this.vban_in = Vban_In
            $this.vban_out = Vban_Out
            $this.command = Special
        }
        else { Exit }
    }

	[void] Login() {
        try{
            Login -TYPE $this.type
	}
	catch{
	    Write-Output $PSItem.ToString
	}
    }

This allows me to setup a Remote Object and independently call Login. Multiple calls to Login from same remote object cause the same crash. With no error thrown.
$vmr = Get-RemotePotato
$vmr.Login() #Works As Expected
$vmr.Logout() #Works As Expected
$vmr.Login() #Fails.

From VBVMR-API:

Again Login function must be called once by the user application, for all its duration life.

IMPORTANT REM: Call VBVMR_Logout()once at the end of the program.

Maybe I'm just misunderstanding this implementation. I initially thought that meant any call to VBVMR_Login() MUST have a corresponding VBVMR_Logout().
But maybe it's actually that any process loading the .dll is allowed to make only 1 total call to VBVMR_Login().  Since I can run two independent Powershell instances logging in independently with no issues.
If so that's not very clear.  If that's the case, what's the point of the Logout Function?
Shouldn't it at minimum throw an exception?
Any idea the proper channel to contact their dev team?
Thanks for the prompt response.
For my current implementation I can use try/catch/finally and check if $vmr -eq $null, which prevents the whole window from crashing, but I still have to create a new Powershell session for each test.
It was only really a problem since I was making changes to code quickly. By default, when I called my .ps1 from within a Powershell window, the instance of your wrapper is tied to my window's process. So I could not call it again from that window.
Easy fix was to either invoke a new window while testing via a helper .vbs script.
Implementation is a simple script to toggle the currently unmuted bus and display an overlay showing which bus is active on the primary display. Will share when completed in case you want to add it to the examples.

Hi again mate. Yes I do believe what you are saying is correct, that a program loading the dll is meant to login and logout a single time. I don't know why the api was developed with this limitation, the best way to contact the developer is through the voicemeeter discord. https://discord.com/invite/TF42rahAXS
I assume logout is required to ensure the connection is closed correctly, in the case as you mentioned that more than a single external program is logging in and out of the api. Perhaps they don't know about each other, so to speak.
You may check page 7 of the documentation for further explanation regarding login/logout:
https://download.vb-audio.com/Download_CABLE/VoicemeeterRemoteAPI.pdf
The login function does return a value but doesn't throw an exception I believe. If you check line 250 in base.ps1:
$retval = [Int][Voicemeeter.Remote]::VBVMR_Login()
So I think a return value could be used to generate and throw an exception object in this case, to make things more clear.
Thank you for your interest in this code and by all means feel free to share any code/examples. Pull requests are welcome.

Attached Below. It could use some cleanup, but functional for now, and good enough for my use case. Most of the code is UI stuff, relevant VM code below:
#Loops through buses included in $buses array, looking for 1st unmuted bus. Toggles mute on that bus, then unmutes the next bus in the array. If there is no next bus in the array, mute the first bus.
#Combined with a .vbs to call without a window pop-up, you can have a hotkey to "Go to Next Bus" in a subset of buses with a visual Indicator on your primary display.
# Run the factory function for required Voicemeeter type
$vmr = Get-RemotePotato
$unmutedIndex = 0
#This could be any combination of buses. e.g. (0,3; 0,1,4,5; 1,3,5)
[int32[]]$buses = 0,1,2
for(($i=0); $i -le ($buses.Length -1); $i++){
if ($vmr.bus[$buses[$i]].mute -eq $false){
	#Found 1st unmuted bus. Mute it.
	$vmr.bus[$buses[$i]].mute = $true
          $unmutedIndex = $i+1
	if ($i -lt ($buses.Length -1)){
		#Unmute the next bus.
		$vmr.bus[$buses[$i+1]].mute = $false
		#exit the loop
		break
	}
	elseif ($i -eq ($buses.Length -1)){
		#Unmute the first bus.
		$vmr.bus[0].mute = $false
              $unmutedIndex = 0
		#exit the loop
		break
	}

}

Includes the .ps1 and a helper .vbs which is useful to use with Hotkey applications since it will launch the Powershell script without opening a window/flicker like it would if opened directly.
ToggleVMDevice.zip

Ok thank you for your contribution! I'll take a look over it later. I will close this ticket for now. Feel free to open another issue if you have further questions.


fix: type ID check should run on non-skipped nodes

There is more issue with the current node.tmpl, tables field was dependent on global $.IDType, not updated after filterNodes so it generate wrong code (/workspace/ent/client.go:31:9: undeclared name: tables)
I updated this PR to fix the issue
https://github.com/ent/contrib/blob/2b75bf138815f589ede1dc72cc83ce3aa9206ebc/entgql/template/node.tmpl#L351-L357


feat: create UI for home page in webapp

Is your feature request related to a problem? Please describe.
The home tab is current using some placeholder text. this should be replaced with the actual UI
Describe the solution you'd like to see
create UI for the "home" tab based on this Figma design
Describe alternate solutions
N/A
Additional information
/pages/app/index.astro is the relevant file

Hi there, I have contacted you over discord (Dr.Klaus) You can assign this issue to me


How to disable automatic 'npm install' when package.json changes

Is it possible to disable this feature in Visual Studio?

Check out VS Update 1, which disables this behavior for Node.js projects.

I have update 1 installed, but this is not a Node.js project, it is an MVC project and this is still happening.

Please can you reopen this issue?

@mousetraps This is a WebTools issue, and not something NTVS is doing, correct?
I believe you can disable this behavior entirely using the answer here: http://stackoverflow.com/a/32891926/306149

Yes and that is what I do in fact, but then you cannot use the NPM Task Runner extension :(
If this is not the right place for this issue can you please confirm and I'll raise it somewhere else..


update contributors wording

@hone DCO is failing here.
I'm curious is DCO is necessary for non-development contributions such as this repo.
cc: @buildpacks/core-team

@jromero thanks, fixed.


OData in 6 steps tab-pane references

At "Understand OData in 6 Steps" page, the references in the tabpanes of section 2 and 3 were pointing at the section 1, so the user was not able to change the example languages. At this pull request I correted this wrong behavior.
To reproduce the error just open the bellow webpage and try to click at any tabpane of section 2 or 3.
Understand OData in 6 steps

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


Wi-Fi information is sometimes incorrect, actually it depends on driver/iwconfig output

I have several Raspberrys and the information for the Wi-Fi signal strenght and quality is only correct (in percentage) on my Raspberry Pi 2, which uses an external Edimax Wi-Fi stick.
On my Raspberry Pi 3 and on my Raspberry Pi Zero with build-in Wi-Fi, the wrong information is shown, because iwconfig, which is apparently used to get the information, delivers the strenght in dBm and the quality in x of 70.
So, if the quality is reported 70%, it is actually 100% (70/70). For the strenght, e.g. 39% is actually 39 dBm, and the following conversion should be done, to correctly display it in percentage:
https://stackoverflow.com/questions/15797920/how-to-convert-wifi-signal-strength-from-quality-percent-to-rssi-dbm

Actually signal strenght in percentage should be determined like described in this pdf:
https://www.google.de/url?sa=t&source=web&rct=j&url=http://madwifi-project.org/attachment/wiki/UserDocs/RSSI/Converting_Signal_Strength.pdf%3Fformat%3Draw&ved=2ahUKEwiAwISyrZHYAhVB2qQKHetPDiMQFjADegQIBxAB&usg=AOvVaw0y6CjUGBBjWgn8cGjva13r
My first suggestion would result in quality in percentage again, not in strenght in percentage.

So, if I understand you correctly, the values iwconfig (or /proc/net/wireless) displays, are based on the driver?
e.g. Driver A (like your Edimax Wi-Fi Stick) reports link quality in percentage, Driver B (like your Pi Zero) reports link quality in x of 70.
If thats the case, is it even possible to determine, when you have to convert the value?
Btw: Raspi Check uses the output of /proc/net/wireless (as described here)

Exactly! Please see the screenshot for comparison, left side RPI2 with an Edimax stick, right side RPI3 with built-in Wi-Fi:

I think you can only see the reference values, if you look at the output of iwconfig. You could check the value after the "/" and check if the string "dBm" is present. "x/100" means, you can just use the read value, "x/y" and "dBm" recognized means that you have to do a calculation to get the values for strenght and quality in percentage.

Thank you for the screenshot, it says more than a thousand words! 👍
I'll add this to my TODO list


2.1.1 - Issue with Holographic Friend (BLD_HOLOGEK)

BLD_HOLOGEK model represented by miniaturized cube in Blender.

I've found the attached model to be a helpful substitute.
FRE_FACE_WINDOW.zip

https://github.com/djmonkeyuk/nms-base-builder/releases/tag/v2.1.2


Make sure about and index have start-of-content anchors

I had a link for a11y the jumps to start of content (press tab within Chrome and you'll see it). Problem is, none of the pages had the corresponding anchor!

Codecov Report

Merging #304 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #304   +/-   ##
=======================================
  Coverage   83.34%   83.34%
=======================================
  Files          56       56
  Lines        2113     2113
=======================================
  Hits         1761     1761
  Misses        352      352

Continue to review full report at Codecov.

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


jxl create boot is broken for other providers

no where does it ask for the credentials, therefore it is unable to login to create the repo...
a workaround is to use jx to create git credentials in ~/.jx/gitAuth.yaml

helmboot secrets edit (jx alpha boot secrets edit) seems to have fixed this


Add macro TF_C_RETURN_IF_ERROR

@mihaimaruseac
We add this macro to tf_status.has a C version of TF_RETURN_IF_ERROR

@mihaimaruseac
It seems that Tensorflow C does not provide a logging function. As we avoid using core/platform/env/logging, should we write another logging function ?

Sorry, took a while to analyze the full impact of this.
This will increase API surface and since the plugins cannot call back TF code it won't help much.
Which means we can only fprintf(stderr (std::cerr) in here but at this point it's no better than having  the macro in every plugin that needs it.

So I will close this PR ?

Yes, I think that's best. Sorry for the wasted time and the initial misdirection.

Don't worry about it :smile:


Transformers for continous data

Hi
I know that library is focused on categorical-encoding, but I think there is a value in adding at least StandardScaler and MinMaxScaler, with such nice interface like we have in one_hot for dealing with NaNs and to have get_feature_names.
What do you think about it?

@wdm0006 ?

At first glance I'd say no that probably is out of scope for this library (but seems like a good idea in general). The universe of continuous value transformations is quite large and adding that into scope here would be quite a big addition.

Yes, there are a lot of continous transformers, but they are quite similar regarding input/output format at least for scalers. I think the easiest way to implement it is to wrap-up scikit-learn continous transformers. Basically, we need to handle missing/unknown values to use it. Additionally: invariants and feature names. Probably this functionality could be common even for categorical encoders.

closing this as I also agree that it would be out of scope


Adjust 'ANSI 8' color to be more visible against background. Fixes #180

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


Re-export ConnectionState from fluid-framework

We use connection state on the FluidContainer API but we don't re-export it for developers to consume.
add ConnectionState to the items re-exported from container-definitons in fluid-framework. FluidFramework/containerDefinitions.ts at main · microsoft/FluidFramework (github.com)

@skylerjokiel We probably need tools to detect and prevent this from happening again?


Failure modes for async reporting

The code at https://github.com/bugsnag/bugsnag-go/blob/master/notifier.go#L47 worries me a little bit. Although goroutines are pretty cheap in go, I don't think it's idiomatic to just spawn goroutines anywhere you can.
What are the failure modes for this code? If, for instance, my network connection stops working and that results in a lot of errors - but the connection to bugnag also won't work - I would expect a reasonable amount of notifications to be saved in-memory and the remainder to be discarded.
If I read this correctly, this will start spawning goroutines like crazy without any reasonable limit. Wouldn't it be better to push notifications on a channel to a single consumer that tries to push them to bugsnag (but also discards them if the backlog becomes too large)?.

Thank you for the thoughtful report, @EmielM. I think you've outlined the correct approach - a limited amount of caching, and notifying via a channel to efficiently queue reports. Looking into how we can better perform here.


younganimal

Source name
Young　animal
Source link
https://younganimal.com/
Source language
japanese
Other details
No response
Acknowledgements

[X] I have checked that the extension does not already exist by searching the extension listing and verified it does not appear there.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] I will fill out all of the requested information in this form.

Comici


Make pipeline input parameters more evident

Addresses #1301
Description

Refer to #1301

How Has This Been Tested?

Try to create run after going to Data Science Pipelines => Runs
Test Impact

Request review criteria:

[X] The commits have meaningful messages (squashes happen on merge by the bot).
[X] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.
[X] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[X] The developer has manually tested the changes and verified that the changes work
[ ] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

Not sure if we should be changing PARAMS = 'run-section-params' too

Not sure if we should be changing PARAMS = 'run-section-params' too

That's just an enum, you can change it if you want some consistency but it's still legible.


Build failing?

The build for master is currently failing. Since your last commit dates back from a few days ago, I thought maybe you hadn't noticed?
Due to that (I believe), npm still considers the previous version as the latest. Do you know when version 2.4.3 will be live?
Thanks

I am having trouble with build as well. Throwing module not available

Was just a weird Phantom issue, bumping to 2.0 fixed it. Not sure what happened w/ 2.4.3 but it's published now.


Entity creation in a system init block does not work properly

A user in Discord (Hafu) contacted me that he has a problem creating an entity in the onInit block of a system.
This function got removed in the last update but I think the problem still remains and makes sense to me because families are created together with their system and therefore if a system creates an entity in its init block then not all families will be notified at that time.
One solution could be to iterate over all entities after system creation and trigger an update for each family to correctly update them. This is a one time operation during world creation and should not be a big problem.
We also need to check the ComponentListener that they also get notified correctly during world creation.

PR is open. I will merge it tomorrow or Thursday and will publish a new version.

part of 1.1-JVM version which gets published right now!


#5980 #5982 #5995 #5996 #5997 Added support for INDEX.

still getting this

@scottdraves please check it https://github.com/twosigma/beakerx/issues/5980#issuecomment-337506823

@scottdraves in last commit i've added backwards compatibility for commands like visibile and slider_color


Input validation wrapper class initial revision

This will break a lot of things until the flags are placed... everywhere. But I'll list out some features right here:

model_encoder.py has a little bit of code for validating the inputs given to METL.

mutation position is valid and lines up with currently places amino acid
PDB file (when run in strict mode) is compared to wild type to ensure match. Strict mode is enabled by default on UUID and INDENT read, but is off for checkpoint reads
change indexing method exists, so when loading models you can decide on load if you want 0 or 1 based indexing. This changes how the errors are reported as well, so if a user is using 1 based indexing the reports for what variant is wrong will be in 1 based indexing
verify if PDB file is needed by pre-checking on load if ra.RelativeTransformerEncoder is in the model, and if it is reports later in the code that you need to add a PDB file before forward is run.
in main, params have been added to all loading methods to allow for "raw" loading which returns the old model, encoder
indexing parameter allows indexing for the model to be set, setting it to 1 will convert all variants to 1 based before feeding them into METL

I think I covered the things I added here

New API example is in the test_validation notebook I added temp for now so that
I could test. Here is a link to it:
https://github.com/gitter-lab/metl-pretrained/blob/ccccc6936fd95bd7295dc847abf81f16ff2c5b6d/notebooks/test_validation.ipynb

@John-Peters-UW is there some minimal number of updates we can make to get this ready to merge? I like the design updates and would like to have it integrated into the main branch before we resubmit the manuscript, which is still ~weeks away.

@John-Peters-UW is there some minimal number of updates we can make to get this ready to merge? I like the design updates and would like to have it integrated into the main branch before we resubmit the manuscript, which is still ~weeks away.

@agitter  Not gonna lie, I completely forgot about this 😂. I was in Boston for a conference for a week, then Madison had a conference I had to participate it which took another week and then I was in full catchup mode with courses. I have an exam tomorrow 😬, but after that we can finish this off pretty quickly and have it ready to merge after some reviews next week.
It won't take a lot of time, but after Wednesday I should have time for research now and stuff like this 🙏. I've been like 90% school work / 10% research for the last week an a half. I'll mention it in my meeting with Juan just to block off some time so that I can get this done for ya'll - He won't mind, we're going pretty slow right now and don't really have any deadlines.


Added a dependency check, loosened version requirements..

Hi there,
I'd like you to accept my pull request.
Thanks!
DK

Hi there,
The build failed because my commit is to check if websocketpp has been installed.
It seems your travis


Reference data source

Dear
I was doing some calculations with scp, when I found out that the values differ from the textbook values I have, referring back to the VDI warmeatlas (https://detector-cooling.web.cern.ch/data/Table 8-3-1.htm).
E.g., when I enter propyleen glycol into scp, at 0°C, 25%, I get:

rho :1025.8  instead of 1030
specific heat: 3872 <=> 3950
thermal conductivity: 0.449 <=> 0.47

I found this by looking at the resulting difference in Reynolds number, which was rather significant. Can you comment on this? Where does the data from scp originate from?
The code I used for the values above is:
import scp
scp.propylene_glycol.PropyleneGlycol(0.25).rho(0)
scp.propylene_glycol.PropyleneGlycol(0.25).specific_heat(0)
scp.propylene_glycol.PropyleneGlycol(0.25).conductivity(0)

Best regards,
Wouter Peere

I think the difference can be explained by mass % in scp and volume % in VDI.

The code is based on the work by Melinder, 2010. It's cited in the docs here: https://secondarycoolantprops.readthedocs.io/en/latest/fluid_melinder.html
but I'll also add a note to the README. The Melinder correlations are based on mass fraction.


Saving a page without making any changes should not create a new revision.

Describe the feature you'd like
Currently if I edit a page and save it without making any changes a new revision is created.
I think that such action shouldn't create a new revision.
Describe the benefits this feature would bring to BookStack users
This change would  make it easier to keep the page versions tidy. Currently I have to manually remove any 'empty' revisions which is time consuming and it's easy to make a mistake and delete the wrong one.
Thanks to this change in the revisions page users would only see actual changes made.
Another solution for this could be somehow marking the 'empty' revisions on the revision page.

Why not just hit the back button instead of the save button? If you have made changes, it will prompt you before actually going back.

Thanks for reporting @Rumcajsev.
There were some checks in place to prevent unrequired revisions but they were not working as intended. This has now been patched in 5323cb52245c4ec7f8735173e3057e321ff6327f, to be part of the next feature release.


v1.15.0-next.2 version bump

Backstage release v1.15.0-next.2 has been published, this Pull Request contains the changes to upgrade to this new release
Please review the changelog before approving, there may be manual changes needed to enable new features:

Changelog: v1.15.0-next.2
Upgrade Helper: From 1.14.0 to 1.15.0-next.2

Created by Version Bump<PHONE_NUMBER>

Closing in favor of v1.15.0-next.3


Breaks orthanc, with the library referenced in the orthanc.json file, it doesn't work

Unable to get to work on Debian 9 using Orthanc 1.2. Just crashes on startup when trying to register the libOE2 library in orthanc startup. Orthanc installed from the Debian repository. Currently running npm version 5.6.0 and node 8.11.3. All users have read execute privileges to the file.
I just added the load library after all the other directories had been loaded.
I cloned your code on the 4th July so should be up to date.
Thanks
James

Hello,
I installed your plugin but when I go to this link http://localhost:8042/OE2/  it redirects to _**http://localhost:8042/OE2/setup**_ and ask for Database path to create the user but I can't create it.  Can you tell me what I need to enter there please?
hint: I have installed a posgresql plugin, does it work with your plugin?
Thanks.


Save the world - Received email is not referred sender and teacher by name or email

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

Version Number: 9.0.5-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:

Navigate to https://staging.new.expensify.com/
Account settings > Save the world
Click on the "I know a teacher" button
Fill in all fields
Click on the "Let's do this!" button
Open your email app

Expected Result:
The mail should start with "Hey"
If the name of the sender and teacher is known (filled out before sending) the email should refer them by name
Actual Result:
The mail should start with "Hey"
Received email is not referred sender and teacher by name or email
Workaround:
Unknown
Platforms:

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

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/c36d2acb-1728-48bb-a7d3-5e44ea275151

View all open jobs on GitHub

@MitchExpensify  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

I replicated this but I'm not sure it fits into our roadmap right now


#598 Add file IO flush function

Solves #598
I had a little difficulty testing. This runs without bugs but doesn't write to the file when I run my bend program. Am I missing something here? I also built both bend and hvm from the main branch.
def main:
  file = IO/FS/open("file.txt", "w+")
  data = "Hello, World!"
  write = IO/FS/write(file, data)
  flush = IO/FS/flush(file)
  close = IO/FS/close(file)
  return 0

Have you run you program using bend run, bend run-c or bend run-cu?
Also, you have to rebase your PR because there's a minor conflict

I ran the program using bend run and bend run-c
Yep, I'll rebase the PR. Thanks for the feedback!

bend run doesn't have IO, only run-c and run-cu.

Thank you for your contribution!

I'll try run-c again. Of course, I am happy to contribute. I'll pick another issue after this if that works with you.

I got the script to work and flush also works as expected.
def main:
  with IO:
    fd <- IO/FS/open("file.txt", "w")
    data = [72, 101, 108, 108, 111, 44, 32, 87, 111, 114, 108, 100, 33]
    write <- IO/FS/write(fd, data)
    flush <- IO/FS/flush(fd)
    write <- IO/FS/write(fd, data)
    write <- IO/FS/write(fd, data)
    close <- IO/FS/close(fd)
    return close


Sometimes doesn't swipe: check for scrolling (isScrolling) seems broken

When I try to swipe several times repetitively, sometimes gesture is not caught and it doesn't swipe.
It can be a big problem when slides are clickable because it triggers the click event when user expected to swipe.
isScrolling seems to cause the problem as commenting out some parts around lines 1175-1190 fixes the issue for me:
            s.touches.currentX = e.type === 'touchmove' ? e.targetTouches[0].pageX : e.pageX;
            s.touches.currentY = e.type === 'touchmove' ? e.targetTouches[0].pageY : e.pageY;

            /*if (typeof isScrolling === 'undefined') {
                var touchAngle = Math.atan2(Math.abs(s.touches.currentY - s.touches.startY), Math.abs(s.touches.currentX - s.touches.startX)) * 180 / Math.PI;
                isScrolling = isH() ? touchAngle > s.params.touchAngle : (90 - touchAngle > s.params.touchAngle);
            }
            if (isScrolling) {
                s.emit('onTouchMoveOpposite', s, e);
            }*/
            if (typeof startMoving === 'undefined' && s.browser.ieTouch) {
                if (s.touches.currentX !== s.touches.startX || s.touches.currentY !== s.touches.startY) {
                    startMoving = true;
                }
            }
            if (!isTouched) return;
            /*if (isScrolling)  {
                isTouched = false;
                return;
            }*/
            if (!startMoving && s.browser.ieTouch) {
                return;
            }

Nope, you will get wrong behavior. Try to play with touchAngle parameter

Closing as no further response or discussion


add a documentation note on backslash usage in shell form of RUN

documents response given @ https://github.com/docker/docker/issues/16239#issuecomment-139613618

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "update-documentation-on-run" git@github.com:AmeBel/docker-1.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Thanks @AmeBel, as mentioned above, I think this information is good to add; it addresses the issue at hand (https://github.com/docker/docker/issues/16239). So, LGTM
This section as a whole needs a touch up, because we now have four "Notes" in a row, which is a bit awkward. Probably better to keep that for a separate PR.
/cc @moxiegirl

Thanks @AmeBel LGTM!

You are welcome, and (Thank You)^10e1000... for the awesome tool you are developing :smile:


Add support for command [JSON.DEL]

Implement [JSON.DEL] command
Delete a value
JSON.DEL key [path]
Return
JSON.DEL returns an integer reply specified as the number of paths deleted (0 or more)
refer to json.del
Add unit and integration tests

@JyotinderSingh hello, I plan to accomplish this  command for dice.  please assign it to me. thanks.

@JyotinderSingh hello, I plan to accomplish this  command for dice.  please assign it to me. thanks.

Awesome, thanks for taking this up @jujiale! Assigned to you.


Unify shard failure handling in getIterators

Shard-failure exception handling when retrieving a BatchIterator was
split across three places:

ShardCollectSource#getIterators
ShardCollectorProvider.getFutureIterator
ShardCollectorProvider.getFutureOrderedCollector

The logic in getIterators was different, adding a remote-collect
fallback.
This moves the exception handling from ShardCollectorProvider to the
ShardCollectSource, to have everything in a single place.

Rebased this, after https://github.com/crate/crate/pull/13828 the flakyness should be fixed.
I'm not entirely sure if it's worth changing.

I'm not entirely sure if it's worth changing.

I'm not very sure as well, I think I slightly prefer this new approach, maybe ask for some other opinion?


HBASE-28702 TestBackupMerge fails 100% of times on flaky dashboard

https://issues.apache.org/jira/browse/HBASE-28702

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 49s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 15s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 55s

branch-2 passed

+1 :green_heart:
compile
1m 12s

branch-2 passed

+1 :green_heart:
checkstyle
0m 25s

branch-2 passed

+1 :green_heart:
spotbugs
1m 18s

branch-2 passed

+1 :green_heart:
spotless
0m 55s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 44s

the patch passed

+1 :green_heart:
compile
1m 10s

the patch passed

+1 :green_heart:
javac
1m 10s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 13s
/results-checkstyle-hbase-mapreduce.txt
hbase-mapreduce: The patch generated 1 new + 9 unchanged - 0 fixed = 10 total (was 9)

+1 :green_heart:
spotbugs
1m 33s

the patch passed

+1 :green_heart:
hadoopcheck
18m  5s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 53s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 20s

The patch does not generate ASF License warnings.

37m 25s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6106/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6106

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux 0d807855c34b 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / b18c3d4fe1402c3b56cf8265170c861f0eda9158

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
77 (vs. ulimit of 30000)

modules
C: hbase-mapreduce hbase-backup U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6106/1/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 10s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 33s

branch-2 passed

+1 :green_heart:
compile
0m 33s

branch-2 passed

+1 :green_heart:
javadoc
0m 25s

branch-2 passed

+1 :green_heart:
shadedjars
5m 17s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 26s

the patch passed

+1 :green_heart:
compile
0m 34s

the patch passed

+1 :green_heart:
javac
0m 34s

the patch passed

+1 :green_heart:
javadoc
0m 25s

the patch passed

+1 :green_heart:
shadedjars
5m 15s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
15m 16s

hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
11m 10s

hbase-backup in the patch passed.

46m 27s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6106/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6106

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 3ed8cd8e7f8a 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / b18c3d4fe1402c3b56cf8265170c861f0eda9158

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6106/1/testReport/

Max. process+thread count
3475 (vs. ulimit of 30000)

modules
C: hbase-mapreduce hbase-backup U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6106/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 10s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 17s

branch-2 passed

+1 :green_heart:
compile
0m 40s

branch-2 passed

+1 :green_heart:
javadoc
0m 28s

branch-2 passed

+1 :green_heart:
shadedjars
5m 58s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 12s

the patch passed

+1 :green_heart:
compile
0m 40s

the patch passed

+1 :green_heart:
javac
0m 40s

the patch passed

+1 :green_heart:
javadoc
0m 27s

the patch passed

+1 :green_heart:
shadedjars
5m 59s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
14m 39s

hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
10m  9s

hbase-backup in the patch passed.

48m  7s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6106/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6106

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 569b8c6ff31f 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / b18c3d4fe1402c3b56cf8265170c861f0eda9158

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6106/1/testReport/

Max. process+thread count
3845 (vs. ulimit of 30000)

modules
C: hbase-mapreduce hbase-backup U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6106/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 44s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m  9s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m  4s

branch-2 passed

+1 :green_heart:
compile
0m 43s

branch-2 passed

+1 :green_heart:
javadoc
0m 33s

branch-2 passed

+1 :green_heart:
shadedjars
5m 34s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 19s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 59s

the patch passed

+1 :green_heart:
compile
0m 44s

the patch passed

+1 :green_heart:
javac
0m 44s

the patch passed

+1 :green_heart:
javadoc
0m 31s

the patch passed

+1 :green_heart:
shadedjars
5m 33s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
16m 49s

hbase-mapreduce in the patch passed.

+1 :green_heart:
unit
11m 16s

hbase-backup in the patch passed.

50m 28s

Subsystem
Report/Notes

Docker
ClientAPI=1.46 ServerAPI=1.46 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6106/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6106

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 269c2994bbdb 5.4.0-186-generic #206-Ubuntu SMP Fri Apr 26 12:31:10 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / b18c3d4fe1402c3b56cf8265170c861f0eda9158

Default Java
Eclipse Adoptium-11.0.23+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6106/1/testReport/

Max. process+thread count
4111 (vs. ulimit of 30000)

modules
C: hbase-mapreduce hbase-backup U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6106/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.


[Event Request] codeunit 60 "Sales-Calc. Discount" - procedure CalculateInvoiceDiscount - OnCalculateInvoiceDiscountOnBeforeSalesLine2DeleteTrue

Please add an Event OnCalculateInvoiceDiscountOnBeforeSalesLine2DeleteTrue in procedure CalculateInvoiceDiscount in codeunit 60 "Sales-Calc. Discount"
[Event Request] codeunit 60 - Sales-Calc. Discount - procedure CalculateInvoiceDiscount
    var
        TempVATAmountLine: Record "VAT Amount Line" temporary;
        SalesSetup: Record "Sales & Receivables Setup";
        TempServiceChargeLine: Record "Sales Line" temporary;
        SalesCalcDiscountByType: Codeunit "Sales - Calc Discount By Type";
        DiscountNotificationMgt: Codeunit "Discount Notification Mgt.";
        ShouldGetCustInvDisc: Boolean;
        IsHandled: Boolean;
    begin
        SalesSetup.Get();
        ...
            end else
                if TempServiceChargeLine.FindSet(false, false) then
                    repeat
                        if (TempServiceChargeLine."Shipment No." = '') and (TempServiceChargeLine."Qty. Shipped Not Invoiced" = 0) then begin
                            SalesLine2 := TempServiceChargeLine;

                            IsHandled := false;
                            OnCalculateInvoiceDiscountOnBeforeSalesLine2DeleteTrue(UpdateHeader, SalesLine2, IsHandled); // <-- NEW EVENT
                            if not IsHandled then

                                SalesLine2.Delete(true);
                        end;
                    until TempServiceChargeLine.Next() = 0;

            IsHandled := false;
            OnCalculateInvoiceDiscountOnBeforeCustInvDiscRecExists(SalesHeader, SalesLine2, UpdateHeader, InvDiscBase, ChargeBase, TempVATAmountLine, IsHandled);
            If IsHandled then
                exit;
            ...

[IntegrationEvent(false, false)]
local procedure OnCalculateInvoiceDiscountOnBeforeSalesLine2DeleteTrue(UpdateHeader: Boolean; var SalesLine2: Record "Sales Line"; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 44362.