clipboard fix in send money page

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/29441
PROPOSAL: https://github.com/Expensify/App/issues/29441#issuecomment-1760133523
Tests

[x] Verify that no errors appear in the JS console

Same as QA Steps
Offline tests

Same as QA Steps
QA Steps

[x] Verify that no errors appear in the JS console

Go to App
Go to + > Send money
Send money to any user
Click on the IOU preview to open report page
Click on the avatar on the header
Right click on the IOU card and select Copy to clipboard
Paste it in the composer

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/57568571/6f174b7b-2758-4b21-a4ae-6fd11ff4a0fe

MacOS: Desktop
Uploading Screen Recording 2023-10-31 at 7.37.23 PM.mov…

Go to staging.new.expensify.com

It's definitely not a correct part of the "Testing" block, which is for developer testing
A fool-proof layout of testing blocks which work for 90% of Expensify issues is:
Tests
Same as QA Steps (unless the issue needs some betas, manual code adjustments; rare but happens)
Offline tests
Same as QA Steps (unless the issue is offline-sensitive)
QA Steps
(actual steps, but don't mention "staging"; if you must, say "the App" or "NewDot")

You can actually write "Same as QA Steps"

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

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

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/2590174/0fcaf908-61c3-4b0a-96a8-b839fb1ac96c

Mobile Web - Chrome
https://github.com/Expensify/App/assets/2590174/25e36e08-7607-4d63-9182-38ddc753b9e1

Mobile Web - Safari
https://github.com/Expensify/App/assets/2590174/f26dd6d9-0589-4540-b1a3-803b343d4075

Desktop

iOS
https://github.com/Expensify/App/assets/2590174/bd1f617d-7368-43fa-958a-5a4a1c5a1d0d

Android
https://github.com/Expensify/App/assets/2590174/246936e8-ec56-4b8d-bcc0-e6e17de8e92f

Paste it in the composer

Ensure that the pasted text contains the correct user's name and amount

@saranshbalyan-1234
What happened here?


Identifiers validation failed for dataset Actualización de la taxonomía y distribución de los anfibios y reptiles de San Luis Potosí

Identifier validation failed for the dataset Actualización de la taxonomía y distribución de los anfibios y reptiles de San Luis Potosí:

Crawler attempt: 285
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 759
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 63%, total records count 758, absent records count 479
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3073307/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Actualización de la taxonomía y distribución de los anfibios y reptiles de San Luis Potosí : https://doi.org/10.15468/pm8rlt.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Actualización de la taxonomía y distribución de los anfibios y reptiles de San Luis Potosí:

Crawler attempt: 288
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 759
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 758, absent records count 758
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3094203/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Actualización de la taxonomía y distribución de los anfibios y reptiles de San Luis Potosí : https://doi.org/10.15468/pm8rlt.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


Add a stack resource

Today, custom builders are configured with a baseBuilderImage which is essentially an empty builder. It would be convenient for users to be able to reference a stack such as those available on pack suggest-stacks.
A stack resource would allow custom builders to be configured with a reference to a stack. This will allow updates to stack to fan out to all builders. This enables images to be rebased when used with custom builders.

With this change baseBuilderImage would no longer be a field on CustomBuilder.
apiVersion: experimental.kpack.pivotal.io/v1alpha1
kind: CustomBuilder
metadata:
  name: my-custom-builder
  namespace: default
spec:
  serviceAccount: default
  tag: sample/custom-builder
  stack: bionic
  store:
    image: cloudfoundry/cnb:bionic
  order:
  - group:
    - id: org.cloudfoundry.node-engine
    - id: org.cloudfoundry.yarn
  - group:
    - id: org.cloudfoundry.node-engine
    - id: org.cloudfoundry.npm

apiVersion: experimental.kpack.pivotal.io/v1alpha1
kind: Stack
metadata:
  name: bionic
spec:
  baseImage:
    image: cf/cf
  runImage:
    image:  cf/cf

Stack resource added in https://github.com/pivotal/kpack/pull/256 & https://github.com/pivotal/kpack/pull/259. Closing.


Js.t {..} now incorrectly formats to {..}

Following #1404, we now format Js.t {.. foo: bar} into {.. "foo": bar}. But we forgot to handle the case of an empty Js.t object.
Likewise for Js.t {.}

Fixed by #1502


Crash with Error Code 5 after latest MacOS and VS Code update

It's unclear yet what it produces. It does not seem to be tight to a specific action. Just idling or without focus and it crashed.
Version: 1.86.0 (Universal)
Commit: 05047486b6df5eb8d44b2ecd70ea3bdf775fd937
Date: 2024-01-31T10:29:15.765Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.3.0
I started to collect a dump as per the doc.
vscode.zip

Crash when workbench is running out of memory. Can you see if an extension is triggering the crash, from command palette run Help: Start Extension Bisect

I am not seeing this anymore after executing the following command:
rm -rf ~/Library/Application\ Support/Code/Backups/*

I found this tip in one of the other open issues with similar reports.

I see, thanks for narrowing it down. If you see this issue again please report back without deleting backups folder, it would help us capture relevant traces.
/cc @bpasero seems there is a memory leak in backups code path.


Feat(web): Introduce Card component #DS-1397

Description

Additional context

Issue reference
https://jira.almacareer.tech/browse/DS-1397
https://jira.almacareer.tech/browse/DS-1560

❤

Horizontal cards do not find on mobile screen :(

Horizontal cards do not fit on mobile screen :(

I added a separate set of media sizes for horizontal cards but we still need to get back to this.

Horizontal cards do not fit on mobile screen :(

I added a separate set of media sizes for horizontal cards but we still need to get back to this.

I tweaked the media subcomponent so nothing is overflowing now.


Shift Double-click in tmux select words from differnet panes

Windows Terminal version
1.20.11215.0
Windows build number
10.0.22631
Other Software
Tmux in WSL with multiple panes
Steps to reproduce
Consider a tmux session with multiple panes as shown in below pic.

When i try to "shift double-click" on the word "siballa", Terminal also selects the pane delimiter line from other pane because it thinks its complete word.
Another example below where in which i tried to select the file permission string "lrwxrwxrw". It selected the "yankrink_hi" from the other pane

Expected Behavior
In tmux enviroment, Double-click should select words only from current pane
Actual Behavior
In tmux enviroment, Double-click should select words only from multiple panes.
This may not be bug but atleast there should be a option to prevent selection of words across multiple lines. I use tmux with multiple panes and encounter this issue often.

Thanks for filing! We're having trouble reproducing this. Would you be able to write up the steps required to get in this state /? This'll help us take a closer look 😊

@carlos-zamora Below is another screen shot where we can reproduce it -
Open a terminal - adjust the width to say 80 or less. Width shouldn't matter here but it makes easy to repro
Start a tmux session with two vertical split panes
Type some lengthy strings in both panes.
Now shift-doubleclick on a string on one pane - terminal will expand the selectoin to other pane.

My word delimiters are set to  "()"',;<>~!@#$%^&*|+[]{}~?│"

Does this repro on Windows Terminal Canary?

Yes, just download (ver:1.22.1631.0) it and i can see the issue there also

We think this should be fixed by a combination of #15602 and some of the recent ConPTY work we've been doing. We're going to move the info over from that issue over here though since this has a nice test for it.
From what I understand, a row should only be marked as force-wrapped if we actually wrote past the last column, which naturally occurs already in the AdaptDispatch::_DoLineFeed call.
Removing the SetWrapForced call however breaks these unit tests:
ConptyOutputTests::InvalidateUntilOneBeforeEnd
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet0
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet1
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet2
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet3
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet4
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet5
TerminalCoreUnitTests::ConptyRoundtripTests::BreakLinesOnCursorMovement#metadataSet6
TerminalCoreUnitTests::ConptyRoundtripTests::ResizeRepaintVimExeBuffer
TerminalCoreUnitTests::ConptyRoundtripTests::WrapNewLineAtBottom#metadataSet6
TerminalCoreUnitTests::ConptyRoundtripTests::WrapNewLineAtBottom#metadataSet7
TerminalCoreUnitTests::ConptyRoundtripTests::WrapNewLineAtBottom#metadataSet8
TerminalCoreUnitTests::ConptyRoundtripTests::WrapNewLineAtBottomLikeMSYS#metadataSet6
TerminalCoreUnitTests::ConptyRoundtripTests::WrapNewLineAtBottomLikeMSYS#metadataSet7
TerminalCoreUnitTests::ConptyRoundtripTests::WrapNewLineAtBottomLikeMSYS#metadataSet8

They break because when a ROW is not marked as force-wrapped the output behavior of the VtEngine and its output changes. We need to investigate why they break, what the correct behavior should be and how we can fix it. Presumably most unit tests simply assert the wrong behavior, but it's also possible that VtEngine::_PaintUtf8BufferLine and its removeSpaces variable may have to be updated.


Make use of new dart api for compute

Get rid of a lot of code by using a newer Dart API. Also fix some unrelated issues on the v6 branch.
This targets the v6 branch

Pretty neat to get rid of the custom handling but can we actually raise to Dart 3.0.0? I am all for it :)

Pretty neat to get rid of the custom handling but can we actually raise to Dart 3.0.0? I am all for it :)

Technically, this change only needs Dart 2.19. But given, the ecosystem is quite good at being up to date, I would say it's okay.

I would be excited to see records and patterns in our packages if we use 3.0 😮. However, if we do so, we might need to consider maintaining separate branches given the fact that thousands (on GitHub) of projects are using Dio 4.0.

I reduced the Dart version down to 2.19. That's still higher than the current, but it should be acceptable.


Cannot validate request with no content-type if body is not required.

Describe the bug
Request validator does not properly handle requestBody with required: false.
To Reproduce
Steps to reproduce the behavior:

Schema has an optional body:

    requestBody:
      content:
        application/json:
          schema:
            $ref: '#/whatever'
      required: false

Try and validate request with no body (thus no Content-Type header).

ValidationException is thrown:

Invalid request.
Validation error(s) :
Content type 'null' is not allowed for body content. (code: 203)

Expected behavior
No exception thrown.

If required field is omitted, does it work?

If there is a content-type header, then validation works. However, it should work with no header and no body.

This should be fixed in 1.0.3-SNAPSHOT.
Are you able to validate the changes ?

Hi! I just tested with 1.0.5 and the issue is still present. I have a POST with an optional body that only works without a body if content-type header is set. Thanks for looking into this!


i printed hello world

What does the program do ?
---display hello world
In what programming language it is written? C programming language

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


Ability to use a custom yolov5 model

Added the ability to use a custom yolov5 model when running inference. e.g. a model trained for specific species or md_v5b.0.0.  Currently this needs to be done each time - may be worth saving this to a preference file, then could a have a drop down for various models?  We may need to add the ability to use custom classes for when using models trained for a specific speices.

also only tested on M1 mac os ventura

Thanks for collaborating! Good idea to add the option to choose for MDv5b and a custom model. I continued your code and made a dropdown menu. What do you think of this? I tested it on MacOS (intel) and Windows 11. Could you test it on MacOS (M1)?

Not sure what you mean with the ability to use custom classes for when using models trained for a specific species. How does that work?

Not sure what you mean with the ability to use custom classes for when using models trained for a specific species. How does that work?

for example by default megadetector has 3 classes: animal, person, vehicle. I have trained a custom model using transfer learning to find only quokkas, magpies, ravens, humans. To make it work I have been changing the code in cameratraps run_detector.py
# Label mapping for MegaDetector
DEFAULT_DETECTOR_LABEL_MAP = {
    '1': 'animal',
    '2': 'person',
    '3': 'vehicle'  # available in megadetector v4+
}

and separate_detections_into_folders.py
friendly_folder_names = {'animal':'animals','person':'people','vehicle':'vehicles'}
A bit of a hack, but it works.
I haven't looked into how your code handles this yet, but I might be possible to use a config file to store these variables so they are loaded at runtime. Then they could be customised as needed. It may be better to add this change to https://github.com/microsoft/CameraTraps though, not here? And then it should just work in EcoAssist with no extra changes?
Let me know your thoughts. I happy to add something to CameraTraps if that's the way to go.

I'm getting an error on Windows 10 using my custom model. It works fine on my M1 mac and using the cameratrap run_detector_batch.py script on windows 10. So it's strange.

Any ideas?

I'm getting an error on Windows 10 using my custom model. It works fine on my M1 mac and using the cameratrap run_detector_batch.py script on windows 10. So it's strange.  Any ideas?

Thanks for testing. That is weird... The error message you're seeing means that the MegaDetector output is not as expected (so probably an error from MD). In the hidden folder C:\ProgramData\EcoAssist_files\EcoAssist\logfiles you'll find session_log.txt. This is the log for the last runtime session. Here you'll find the MegaDetector output and will probably point you in the right direction. Here you can see the batch_command. Do you see anything here that is wrong? Do the MDv5a and MDv5b models work properly?

You can upload it or email to<EMAIL_ADDRESS>if you want me to have a look at session_log.txt

You can upload it or email to<EMAIL_ADDRESS>if you want me to have a look at session_log.txt

ok, I found the problem/difference. On windows (and maybe intel Mac?) the install script clones and older version of the Yolov5 code, while m1 is the newer version.  I use the newer version with camertraps on windows too, which is why it works. I used the one in the ecoassist directory and it crashed.
The difference is there is a new class name in https://github.com/ultralytics/yolov5/blob/master/models/yolo.py (line 165: class DetectionModel(BaseModel)), so it can't find it and crashes.
I've had no issues running cameratraps with new versions of yolov5 over 100,000s of images (209be932dec9e89b902f0ac2975fa599e9bc676f installed at the moment), so maybe just use a newer version by default?

Great work! The only reason I checkout the gits is because I don't know whether everything will still work with future commits.
Definable, if the newer version of yolov5 works, let's change the default.
I don't have time to do it today, but could have a look at it tomorrow. Or if you have some time and want to go ahead and change the checkout to a new version in the install files, that would be great!
Thanks


Error in running NeuroNER

I got the following error when running NeuroNER Mac OS X. Does anybody know what is wrong? Thanks.
~/NeuroNER/src$ python3 main.py
NeuroNER version: 1.0-dev
TensorFlow version: 1.4.0
Traceback (most recent call last):
  File "main.py", line 250, in <module>
    main()
  File "main.py", line 245, in main
    nn = NeuroNER(**arguments)
  File "/xxx/NeuroNER/src/neuroner.py", line 257, in __init__
    parameters, conf_parameters = self._load_parameters(arguments['parameters_filepath'], arguments=arguments)
  File "/xxx/NeuroNER/src/neuroner.py", line 118, in _load_parameters
    parameters[k] = distutils.util.strtobool(v)
AttributeError: module 'distutils' has no attribute 'util'
Exception ignored in: <bound method NeuroNER.__del__ of <neuroner.NeuroNER object at 0x102268c18>>
Traceback (most recent call last):
  File "/xxx/NeuroNER/src/neuroner.py", line 489, in __del__
    self.sess.close()
AttributeError: 'NeuroNER' object has no attribute 'sess'

Asked & answered in #75.

OK. Problem solved.
How to close the issue?


FHEM Integration

Hi,
I would like to ask for bthome integration in FHEM. It is a very big home automation platform and it would be great to have bthome there too.
Regards

Hi, BTHome is an open source Bluetooth format, so, it's free to use for anyone who want to use it.
The bthome-ble package that is hosted on this github repo is mainly meant to parse the Bluetooth data and translate that to sensor/event data. The main implementation of this repo is to feed Home Assistant with the necessary info.
I won't be going to develop an BTHome integration for FHEM, mainly due to time limitations and the fact that I don't use FHEM myself. But, as said, you are free to copy or adjust code to create an FHEM implementation. I'll leave the issue open for others who are willing to invest time in your request.

Found a solution:
https://forum.fhem.de/index.php?topic=137277.msg1305259#msg1305259


Upgrade ruby and gems

Faraday was pinned to under v1, but v1 is out and stable, and hasn't broken anything. So allow upgrades.
Default ruby for dev to old stable version (2.5.7)
Update travis file to support testing for current stable (2.7.0) and old stable (2.5.7)

Tests :heavy_check_mark: at https://travis-ci.org/trammel/slack-poster/builds/659010138

Thanks @trammel


pheniqs module optimization

@hukai916
In correct_barcode_pehniqs ,
line 53, ```{sh}
barcode_length=$(awk 'FNR==1 {print length($(NF-1))}' valid_barcode_pool.txt)

can be changed to the following line for better performance

 ```{sh}
    barcode_length=\$(awk 'NR==1 {print length(\$(NF-1)); exit}' valid_barcode_pool.txt)

Thx, updated.


App Engine asset deployment (dos, cron etc.) should be available for flex as well

we enabled it for standard, but we should allow it for flex as well

Before we can do this properly we'll have to give the user the option of
specifying the App Engine configuration directory rather than just a path
to the app.yaml
On Thu, Apr 20, 2017 at 1:59 PM, Etan Shaul<EMAIL_ADDRESS>wrote:

we enabled it for standard, but we should allow it for flex as well
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/issues/1373,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5Ha59y2XP6w3Q3TY_j9boNz2nUZIQks5rx50TgaJpZM4NDX70
.

ah yes. good point. my PR for this was a bit premature.

is there a "standard" place for putting these that we can look as a first step? or is it completely up to the user.

by default maven and gradle look in src/main/appengine, but it's also
configurable.
On Thu, Apr 20, 2017 at 2:03 PM, Etan Shaul<EMAIL_ADDRESS>wrote:

is there a "standard" place for putting these that we can look as a first
step? or is it completely up to the user.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/issues/1373#issuecomment-295836731,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HZJnBJSzHm_NJov1zhVSUCNdhgyqks5rx53YgaJpZM4NDX70
.

ok cool. this needs a bit more thought then. like where we specify this (is it a path selector next to the asset checkbox, does it belong in the facet, etc.)

@patflynn
My thinking is that belongs in the flex facet, together with the app.yaml and Dockerfile configuration. This will require additional validation in the deploy config to ensure that the path was specified in the facet when the user chooses to deploy these configs (or it could just attempt to find them in src/main/appengine directory if none was specified).
This config deploy feature, however, was added to 17.2 before the flex facet was added. So unless you can think of another strategy, I think we'll need to wait until we release the flex updates for this change to get released. In the meantime, the users will be able to specify these configs for standard only.

That's OK. We can hold off on adding this to flex for now.
On Thu, Apr 20, 2017 at 2:31 PM, Etan Shaul<EMAIL_ADDRESS>wrote:

@patflynn https://github.com/patflynn
My thinking is that belongs in the flex facet, together with the app.yaml
and Dockerfile configuration. This will require additional validation in
the deploy config to ensure that the path was specified in the facet when
the user chooses to deploy these configs (or it could just attempt to find
them in src/main/appengine directory if none was specified).
This config deploy feature, however, was added to 17.2 before the flex
facet was added. So unless you can think of another strategy, I think we'll
need to wait until we release the flex updates for this change to get
released. In the meantime, the users will be able to specify these configs
for standard only.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/issues/1373#issuecomment-295847742,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HZlLTHrpNAIe5wi6gC-arM6ZjUUDks5rx6RvgaJpZM4NDX70
.

@patflynn I'm finishing up this issue and was wondering:
For standard, the additional assets get staged into WEB-INF/appengine-generated/ at the root of the staging directory. We then look for them here if the user selects to deploy all configs.
I'm wondering if for flex, we should also stage these files. As I see it there are 2 options:

We don't stage the files, and if the user selected to deploy all configs then, at deploy time, we find these files in the app engine config folder (see #1497)
At the flex stage step, we copy the files from the appengine config folder into the staging directory (either at the root together with the app.yaml and the artifact, or in some subdirectory) and then pull these assets from here at deploy time.

Wanted to get your opinion on these. And if 2 makes more sense, is there a preferred place to put these assets in the staging directory?
My thought on this is that it doesn't really matter and that option 1 is fine (since the staging directory is temporary), but wanted your opinion in case I'm overlooking something.

Don't stage the files. It's not meaningful/necessary in the same way the
app.yaml relates to the project artifacts in the deployment directory, and
it creates a risk that the user will accidentally include the files in
their serving path.
On Wed, Jun 14, 2017 at 12:56 PM, Etan Shaul<EMAIL_ADDRESS>wrote:

@patflynn https://github.com/patflynn I'm finishing up this issue and
was wondering:
For standard, the additional assets get staged into
WEB-INF/appengine-generated/ at the root of the staging directory. We
then look for them here if the user selects to deploy all configs.
I'm wondering if for flex, we should also stage these files. As I see it
there are 2 options:

We don't stage the files, and if the user selected to deploy all
configs then, at deploy time, we find these files in the app engine config
folder (see #1497
https://github.com/GoogleCloudPlatform/google-cloud-intellij/pull/1497
)
At the flex stage step, we copy the files from the appengine config
folder into the staging directory (either at the root together with the
app.yaml and the artifact, or in some subdirectory) and then pull these
assets from here at deploy time.

Wanted to get your opinion on these. And if 2 makes more sense, is there a
preferred place to put these assets in the staging directory?
My thought on this is that it doesn't really matter and that option 1 is
fine (since the staging directory is temporary), but wanted your opinion in
case I'm overlooking something.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-intellij/issues/1373#issuecomment-308540716,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHf5HdoMnD93Oh07jPtFXLC8epyBzS8Dks5sEDsAgaJpZM4NDX70
.

Cool, thanks for confirming.

closed as "won't fix" due to limited enhancements for ae flex


adding support for alert-channels

adding support for alert-channels api

@kjda It looks good in general. There is a test failing, you can fix that and I can approve it afterwards


Should automatically set source property to "Segment"

A customer has inquired about how to filter their incoming events in PostHog by whether or not they were ingested from Segment. Since none of their incoming events have a source property, it would be nice to add it by default here.

I guess the $lib property would be most appropriate here?


Add a filter box in dataset detail page

add filters in the dataset detail page so that users can filter the columns in the table.

done


Are there have some risc-v crypto-vector prototype？

Useful, thanks. I wonder if there are any open source/announced hardware prototypes for test.

I am not aware of any such open source RTL for vector crypto. Hopefully someone will develop these and let the community know.


Map calls onRegionChange on init with wrong region after it's correctly set

So, I have a map as follows:
// render
<MapView
  region={this.state.region}
  onRegionChange={this.handleRegionChange}
  style={styles.map}
  showsUserLocation={false}
  showsTraffic={true}
  showsIndoors={false}
  rotateEnabled={false}
>
  {this.renderMapMarker()}
</MapView>

// renderMapMarker
<MapView.Marker.Animated
  coordinate={this.state.userLocation}
  title="I'm here"
>
  <View style={styles.marker} />
</MapView.Marker.Animated>

On componentDidMount() I get user's location, set it on this.state.userLocation and change this.state.region to match the location coordinates. After initializing, the component keeps calling onRegionChange until it stops with the value:
{
  latitude: -14.36687999999999,
  latitudeDelta: 48.71334786739263,
  longitude: -54.49218800000002,
  longitudeDelta: 40.60546966557548,
}

BUT the map renders fine and the region seems to be ok, however, if I need to go to another screen OR render another <View /> instead of the map on that same screen, it tries to retrieve this.state.region again which is wrong and just keep on it.
These are the logs that I put on onRegionChange to see what was happening (I only set this.state.userLocation ONCE):

Edit: if I render map without setting any location, only with this.state.region with random coordinates, it still calls onRegionChange with those same values mentioned above.
react-native: 0.39.2
react-native-maps: 0.12.2
OS: iOS

Seems to be the same problem of #919 and #846, solved it by switching onRegionChanged to onRegionChangeComplete, really weird thing.
I'll close this since it appears to be fixed.

I have wrong region (big deltas) for both handlers on map init, but correct map visible part.

same experience as max-mykhailenko: "I have wrong region (big deltas) for both handlers on map init, but correct map visible part." Please reopen.

I am experiencing this same behavior. The delta is very large (~60), but when I manually pan the map, even just a little, the delta goes back to the correct value (~0.4 in this case).

onRegionChange is called 4 times, once with the initialRegion, then two more with the a different region then before but equal to each other, then one last one in kansas. MapView displays correctly.


Reorganized C++ File Structure

Reorganized the file structure so that both full and lite sdk are stored under the same cpp directory.
Fixed CMake build to reflect these changes.
Changed the VSCode workspace to reflect changes

cpp-lite sdk is now built using:
cmake -G Ninja -DBUILD_LITE=ON ..

duplicates work in refactor-for-lite


Put proper padding to the end of list in side event list

Idea Description
Please put more padding to the screen end.
Reference images and links

Likely line to modify:
https://github.com/DroidKaigi/conference-app-2023/blob/4f4e26c3f072d7203a9b6b717c95c3ce0145a047/feature/floor-map/src/main/java/io/github/droidkaigi/confsched2023/floormap/FloorMapScreen.kt#L139

May I handle this issue?✋

Sure! Go ahead!


Update onnx environment file with packages needed to build onnxruntim…

…e for cuda variant
Checklist before submitting

[x] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Add packages that are needed for building onnx-env with cuda support.
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

@jayfurmanek - Somehow this PR got missed from the merge in 1.3. We need to get this in to get onnxruntime compile on x86 and re-tag 1.3

No need to retag. We'll just pick this one up in 1.3.2.


Skipping too many files that can be compressed

I used Compactor on genshin impact because why not and It seems like it skips alot of files that could be compressed, I tried Compactgui instead and it Compressed it much better then compactor. Can you add a setting to allow us to change this so it compresses every file?

Aye, that's issue #3, about time I got to it.

ah, alright thanks for all your hard work :)


Non3gpp UE does not have internet access

Describe the bug
Non3gpp UE does not have internet access
To Reproduce
Reproducing is a bit involved. I used multipass to set up two vms with a bridge in between. Install the free5gc core on both vms. The vm being used as the core needs the n3iwfcfg.yaml modified. The IKEBindAddress needs set to the ip of the vm. Also add the test UE used in the non3gpp test through the webconsole. On the other, I simplified the test.sh to only use the non3gpp test and modified the var declaration at the top of the non3gpp_test.go. Specifically the n3iwfInfo_IPSecIfaceAddr, n3ueInfo_IPSecIfaceAddr, and n3ueInfo_IPSecIfaceName to the corresponding values of the vms. Running the test passes but if you make the UE stay alive by adding a sleep at the end of the test go file and turn off livenessCheck in the n3iwfcfg.yaml on the core vm, you only have access to things on the core vm such as the test address <IP_ADDRESS>. ping google.com does not work. Note, during setup, the UE does not update the SQN on any connection attempt so you will need to modify in the webconsole or in the test data on the ue side.
Expected behavior
I should be able to ping or curl or wget things on the web
Environment (please complete the following information):

free5GC Version: v3.3.0
OS: Ubuntu 20.04 Server
Kernel version: 5.4.x
go version: go1.17

I actually fixed this myself. When setting up the core, I had the wrong dn_interface in this step sudo iptables -t nat -A POSTROUTING -o <dn_interface> -j MASQUERADE


unstable nightly-only API that has now been removed

Use std::arch instead of x86intrin

Oops sorry @namuyan I just saw this... It is fixed in this commit.

Thank you for response.
I will wait for your project complete!


pipeline not working with redisearch comands

so I was trying to use pipelining with redisearch, like so
await redis.pipeline([['ft.search', 'my_index', '*']]).exec();
but all I got is
TypeError: Cannot read property 'apply' of undefined

This damn bot closing every issues makes ioredis looks well maintained but in fact is not, this issue and many more are still there :-1:

up

Solution: https://github.com/luin/ioredis/issues/1313#issuecomment-809402608


klarna_reference missing from CheckoutOrder

CheckoutOrder does not map "klarna_response"
https://github.com/klarna/kco_rest_dotnet/blob/v3.x/Klarna.Rest/Klarna.Rest.Core/Model/CheckoutOrder.cs
https://developers.klarna.com/api/#order-management-api-get-order

Hi @kwestground
Thanks for the feedback.
You are right, the CheckoutOrder has no such field and actually it should not by two reasons:

The Klarna Checkout service differs from the Klarna Order Management service. You can consider them as two separated services, so they can have a different Order models
The most important part is, the field itself:

klarna_reference A Klarna generated reference that is shorter than the Klarna Order Id and is used as a customer friendly reference. It is most often used as a reference when Klarna is communicating with the customer with regard to payment statuses.
So this is a "friendly representation" of the created order. Since the checkout processes an order and it is not placed yet by customer, you cannot have such field (you can consider the order like "does not exist yet") and that's why the CheckoutOrder model has no such field. But after the order is placed - this reference will be generated and then you can use it.
Klarna Checkout says, that after placing an order use the Order Management to get the details. So using the Order Management you can finally get the klarna_reference.
By the way, thanks for pointing us to the models, we actualized them by adding missing fields (not related to the klarna_reference but still important).
Thanks!

Fixed in https://www.nuget.org/packages/Klarna.Rest.Core/3.1.4


don't html-escape collection names (bug 1142301)

names for apps etc are all TranslatedField; since this needs to be used in <title> elements etc then we should avoid the cleaned version here too.

r+


Reorganize noblox.js API endpoints, add Datastore Open Cloud, improve unit tests

Updates endpoints for some using www. to their respective subdomain (if available)
Improve test cases by adding more specificity and more functions
Uses Date objects for created and updated properties
Delete follow and getStatus
getIdFromUsername can now return multiple IDs if provided multiple usernames (backward compatible)
Correct a typo on postinstall
Updated typings
Adds datastore open cloud functions (#473) and API key support

The one thing I am unsure about is the whole setting an API key. Does anyone have any clue if there's a way to test if it's valid? Right now, all the setAPIKey function is doing is just setting it–no checking or anything whatsoever.

What's the status on this PR? Does it just need a review or is there work to be done?


The style scoped can not work when I import css file and run serve.

Version
3.0.1
Node and OS info
Node v8.11.3/ npm 6.4.0/MacOS 10.13
Steps to reproduce

What is expected?
section[data-v-1eed3935] {
padding: 8rem 0;
}
What is actually happening?
section {
padding: 8rem 0;
}

Try <style scoped src="../../css/creative.css"></style>


CPackDeb: Debian package requires a package version

When trying to build the SDK, I'm getting the following error:
Run CPack packaging tool...
CPack: Create package using DEB
CPack: Install projects
CPack: - Run preinstall target for: sawtooth
CPack: - Install project: sawtooth
CPack: Create package
CMake Error at /usr/share/cmake-3.5/Modules/CPackDeb.cmake:577 (message):
  CPackDeb: Debian package requires a package version
Call Stack (most recent call first):
  /usr/share/cmake-3.5/Modules/CPackDeb.cmake:778 (cpack_deb_prepare_package_vars)

CPack Error: Error while execution CPackDeb.cmake
CPack Error: Problem compressing the directory
CPack Error: Error when generating package: sawtooth-cxx-sdk
make: *** [package] Error 1
Makefile:94: recipe for target 'package' failed

Attempting to build using Github Actions: https://github.com/gluwa/sawtooth-sdk-cxx/actions
Workflow file is below:
name: C/C++ CI

on:
  push:
    branches: [ master, feature/build ]
  pull_request:
    branches: [ master, feature/build ]

jobs:
  build:

    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2
    - uses: docker/build-push-action@v2
      with:
        tags: sawtooth-sdk-cxx-local:latest
        push: false
    - uses: addnab/docker-run-action@v3
      with:
        image: sawtooth-sdk-cxx-local:latest
        options: -v ${{ github.workspace }}:/project/sawtooth-sdk-cxx
        run: build_cxx

Got it working with this updated action script:
name: Sawtooth SDK Cxx CI

on:
  push:
    branches: [ master, feature/build ]
  pull_request:
    branches: [ master, feature/build ]

jobs:
  build:

    runs-on: ubuntu-latest

    steps:
    - uses: actions/checkout@v2
    - uses: docker/build-push-action@v2
      with:
        tags: sawtooth-sdk-cxx-local:latest
        push: false
    - uses: addnab/docker-run-action@v3
      with:
        image: sawtooth-sdk-cxx-local:latest
        options: -v ${{ github.workspace }}:/project/sawtooth-sdk-cxx


refactor(store): optimize table libraries

changes to 2 files in store's codegen (everything else is autogenerated)
minor stuff to finish table libs
any more attempts at table optimizations likely hurt code too much: https://github.com/latticexyz/mud/pull/1286 https://github.com/latticexyz/mud/pull/1183

let's add a small changeset

a few nuances I feel like I should clarify:

I think we've decided to not do changesets for stuff that's not exported, like tests
do we need changesets for internal things (like this gas PR) that are exported but don't affect API/functionality (I guess you could consider gas costs as functionality though)?
I assume more detailed changesets for API stuff are good, but do we want details for internal changes?


simple Makefile

simple Makefile, only tested on MacOS but should work fine on other platforms

Thanks. Works for me on linux too. I have to admit I have never learned make so this is very useful.


Great Expectations integration doesn't work in Google Cloud Composer

The current implementation of the OL integration doesn’t work in Cloud Composer. It’s likely that it doesn’t work with any installation of Airflow using the CeleryExecutor. The current implementation relies on the ability to wrap the execute method of the GreatExpectationsOperator and to capture the returned result before it is passed to the Airflow DAG. For whatever reason, this “monkey-patching” doesn’t work in Cloud Composer. It does work correctly when running Airflow locally on a single host. I haven't been able to verify that it works in the existing airflow integration test (GreatExpectations functionality is not exercised in the test).
Possible Solutions
XCom
Fortunately, the GreatExpecationsOperator does publish validation results into Airflow’s cross-communication mechanism (XCom), meaning we can fetch the results from the worker host at runtime. The response from the worker host is a json blob that we need to parse. The existing code already navigates this structure. However, the existing solution requires users to call a static set_dataset_info method on the GreatExpectationsExtractor class, passing in the instance of the GreatExpectationsOperator. The operator is then monkey-patched with the additional information. It is unclear whether this method of naming the dataset will work in Cloud Composer.
Alternatively, we can look at the JSON returned from the operator at runtime to determine the dataset name. Unfortunately, the arguments passed to the operator aren’t guaranteed to give an easily parseable dataset name. Two example JSON blobs are below- one for BigQuery and one for GCS:
BigQuery
"meta": {
 "great_expectations_version": "0.13.26",
 "expectation_suite_name": "orders_suite",
 "run_id": {
   "run_name": "20210818T051320.186669Z",
   "run_time": "2021-08-18T05:13:20.186669+00:00"
 },
 "batch_kwargs": {
   "project": "bq-project",
   "table": "orders",
   "dataset": "bq_dataset",
   "datasource": "food_delivery_db"
 },
 "batch_markers": {
   "ge_load_time": "20210818T051320.055448Z"
 },
 "batch_parameters": null,
 "validation_time": "20210818T051320.192586Z",
 "expectation_suite_meta": {
   "BasicSuiteBuilderProfiler": {
     "batch_kwargs": {
       "bigquery_temp_table": "bq-project.bq_dataset.ge_tmp",
       "data_asset_name": "orders",
       "datasource": "food_delivery_db",
       "limit": 1000,
       "schema": null,
       "table": "orders"
     },
     "created_at":<PHONE_NUMBER>.4953547,
     "created_by": "BasicSuiteBuilderProfiler"
   },
   "citations": [
     {
       "batch_kwargs": {
         "bigquery_temp_table": "bq-project.bq_dataset.ge_orders_tmp",
         "data_asset_name": "orders",
         "datasource": "food_delivery_db",
         "limit": 1000,
         "schema": null,
         "table": "orders"
       },
     }
   ],
   "columns": {
     "id": {
       "description": ""
     },
     "placed_on": {
       "description": ""
     },
     "menu_item_id": {
       "description": ""
     },
     "quantity": {
       "description": ""
     },
     "discount_id": {
       "description": ""
     },
     "comment": {
       "description": ""
     }
   }
 }
}

GCS
"meta": {
 "great_expectations_version": "0.13.26",
 "expectation_suite_name": "gcs_orders",
 "run_id": {
   "run_name": "20210819T191553.090700Z",
   "run_time": "2021-08-19T19:15:53.090700+00:00"
 },
 "batch_kwargs": {
   "datasource": "gcs",
   "data_asset_name": "orders_file",
   "path": "gs://the_bucket/the_data/part-00000-ef898d87-fe05-4b1b-8f31-7ec57a8682ac-c000.snappy.parquet",
   "reader_method": "read_parquet"
 },
 "batch_markers": {
   "ge_load_time": "20210819T191551.999073Z",
   "pandas_data_fingerprint": "d41d8cd98f00b204e9800998ecf8427e"
 },
 "batch_parameters": null,
 "validation_time": "20210819T191553.097890Z",
 "expectation_suite_meta": {
   "great_expectations_version": "0.13.26"
 }
}

Most of the response fields are omitted, but the fields that can identify a dataset and its composition are included. Notably, the batch_kwargs are used to specify the appropriate identifiers for each dataset. The DataContext contains specific DataSource implementations, such as a SQLAlchemyDatasource or a PandasDatasource. Each of those knows how to construct the correct Dataset implementation based on those batch_kwargs. The DataContext can return the Datasource by calling get_datasource.
One viable option is to use the DataContext to find the Datasource, then, based on the implementation of the DataSource we detect, we can parse the batch_kwargs ourselves to construct the Dataset name and any necessary facets (schema, datasource, etc.).
This is known to work in a cloud environment, but hasn’t been tested thoroughly.
Configuration required:
None. The user simply includes the OL library in their Airflow instance and our code does everything.
Coding required:
Parsing the batch_kwargs to construct the dataset name and facets. The code will live in the existing GreatExpectationsExtractor
ValidationAction
GreatExpectations also comes with a callback mechanism called ValidationActions. These actions are custom classes that are invoked by GreatExpectations after validation completes. These actions are invoked whether the validation succeeds or fails. Some example actions that ship with GreatExpectations  include Slack notifications and PagerDuty alerts.
The ValidationAction’s run method is invoked with the fully constructed Dataset (e.g., PandasDataset or SQLAlchemyDataset), which contains all of the information necessary to construct the OL Dataset, including the connection URL (SQL) or filesystem path (Pandas).
A nice property of the ValidationAction approach is that it is not Airflow-specific, so any GreatExpectations job can report Dataset facets to the OpenLineage server. This includes runs in Spark clusters as well as hosted Airflows and custom environments. It also works both locally, on a single host, as well as distributed in a cloud environment.
Configuration required:
The user needs to customize the great_expectations.yml file to specify the OpenLineageValidationAction. The user can specify OL configuration in the yml file, such as the host name, namespace, apiKey, etc.
It may be possible to programmatically modify the DataContext in Airflow to automatically add the OL ValidationAction if the user hasn’t specified it. It hasn’t been tested that this modification will be persisted across the serialization from the scheduler to the worker.
Coding required:

Create a new OpenLineageValidationAction
Collect dataset information from Dataset impl - if SqlAlchemyDataset, use the asset.engine.url. If PandasDataset, use asset.batch_kwargs.path.
There are two options for reporting lineage to OL server-
Return dataset information into the “actions_results” field of the response. Use above XCom logic to find the dataset information and report dataset information and facets. While this works well in the Airflow case, something else would need to report the lineage outside of Airflow.
Post directly from the OpenLineageValidationAction. The environment variables pointing to server location, apiKey, etc. are already present on the worker host. The runId of the task will need to be reported- it may be possible to use the lineage_run_id macro to parameterize the OpenLineageValidationAction constructed by the operator. This works in both the Airflow environment as well as any environment in which Great Expectations is running.

Great writeup @collado-mike !
If we're purely talking about current Airflow implementation, then using XCom seems to fit closer to what we want to achieve. Hovewer, batch_kwargs seems to become deprecated. It could lead to having to support two separate versions.
ValidationAction's approach seems more robust - API seems more stable; possiblity to specify OL url/apiKey in config; only three concrete datasets to get the data from. The requirement for adding OL data to great_expectations.yml doesn't seem to be big hurdle, and the fact that it can work without airflow is an added bonus.
Mini rant:
It does not help that related GreatExpectations abstractions seem to be confusing, without specifying which version they target. For example ValidationOperators are something else than ValidationActions.
I think exploring second option with cautiousness is the best option - for example, it's unclear to me if the ValidationAction receive results in the same format as current extractor based on Airflow's GreatExpectationsOperator.

I think exploring second option with cautiousness is the best option - for example, it's unclear to me if the ValidationAction receive results in the same format as current extractor based on Airflow's GreatExpectationsOperator.

I diffed the XCOM response and the output of a ValidationAction that serializes the results to JSON. The gist is that the ValidationAction is given the validation_result field of the XCOM response.

Closing as we merged https://github.com/OpenLineage/OpenLineage/pull/234


add allure environment

https://github.com/allure-framework/allure-python/issues/96
https://stackoverflow.com/questions/35264335/customize-allure-report-using-pytest-allure-adaptor

What would you like the allure environment to include?
what to do you mean by before/after all?

What would you like the allure environment to include?
what to do you mean by before/after all?

browser,
base url

Done

not yet


Some questions

Hi,
I am very interested in this project, as I don't like Relay simply because it is tied to React.
I am contemplating using your gem of a package with vuex. https://github.com/vuejs/vuex
Though, I have two concerns. If I understand correctly, lokka doesn't yet manage any kind of store locally and you mention caching and validation. I would assume that means you do plan to add a client-side store(age) capability later? Could I feasibly use the vuex store to make the two work together?
Being lazy and not looking into the code, but does lokka support the introspection feature of GraphQL? (didn't see the docs mentioning it).
And, last question (which might show my lack of JS knowledge) will lokka (or does it now) support the ability to "collect" queries in a set of components, similar to how Relay does it with React components?
Thanks for any support in advance!
Scott

Hi,
You asked the question in time. The main different with Relay and Lokka is, we don't have direct integration with the UI framework. It's all about the data store.
We already have a basic version of a cache and a Relay like declarative data fetching. I'll document it soon and do a blog post. Try our test-cases to have a look at it.
About the introspection feature: This is planned and will be available in the early next year. (Feb). With that, we could easily do validation in the client side and do more stuff in the caching layer.

Thanks for the quick reply.
The caching looks promising (hah, pun not intended).
I am also still missing how lokka puts different queries together (which might be encapsulated with components) to end up with a single request (and one of the advantages of GraphQL). Can you shortly elaborate on that possibility?
Scott

Checkout this app: https://github.com/kadira-samples/meteor-graphql-demo/tree/master/client
Both containers and components directories. It has some meteor specific stuffs. Pure JS version is coming soon. Actually it's already done.

Thanks and I see how the fragments are being defined. But, that demo is using JSX. I'd really like to avoid JSX and React, if at all possible, and why I ended up with Vue.
Anyhow, keep up the good work. I am now following this repo and looking forward to the finished caching and introspection parts. I'd love it, if lokka were to be something I could use like Vuex, with a simple API like Vuex has. So far, it looks like it is heading that way.
Scott

Lokka stuffs are not related to React and JSX anyway. You could use if with vue for sure. I'll give it a try as well.

@arunoda - hey. Any news about further developments? I noticed Meteor is also using GraphQL too now. This means more people will probably be looking at libraries like lokka for non-react/ relay solutions. I think that is good news.
Scott


Update InfoBar narrator behavior

Description

Now, the InfoBar will behave as follows:

Close button will be read as "Close infobar severity"
Should be announced as "Title Message Severity"
Default icons can be read and will be announced as "Icon severity ..."

Motivation and Context

Closes #4533 , closes #4534
How Has This Been Tested?

Tested manually.
Screenshots (if appropriate):

@gabbybilka @YuliKl  can you help define what should be announced ? "Close infobar error" sounds incorrect. Perhaps it could be
"Informational infobar close button"
"Success infobar close button"
"Warning infobar close button"
"Error infobar close button"
where the first word matches the severity enum.

Updated the wording for the close button now.

/azp run

@gabbybilka @YuliKl can you help define what should be announced ? "Close infobar error" sounds incorrect. Perhaps it could be
"Informational infobar close button"
"Success infobar close button"
"Warning infobar close button"
"Error infobar close button"
where the first word matches the severity enum.

Should there be similar text for the action button?

@chingucoding Sorry for the delayed response on this. We have been trying to reach out and get more information from accessibility experts on the correct approach for these issues. This is what we have finally landed on (which I think is simpler and gives a better accessibility experience).
•	Set AutomationProperty.IsDialog=”true” in the default style so that the InfoBar elements (Icon + Title + Message) are read when an action or close button is first focused. When focus leaves an InfoBar and returns, the InfoBar elements will be re-read. This is special behavior that Narrator has for elements with this property set to true which works pretty well for InfoBar.
•	Add Icon to the UIA tree to communicate that element as ‘Information image’, ‘Success image’, ‘Error image’, ‘Warning image’
•	When the Severity, Title, or Message has changed the InfoBar should re-raise its notification event. Note that if multiple of these change one after the other, we raise the event just once after all of them are set.
@gabbybilka  and @johnpf74 as FYI.

@chingucoding Sorry for the delayed response on this. We have been trying to reach out and get more information from accessibility experts on the correct approach for these issues. This is what we have finally landed on (which I think is simpler and gives a better accessibility experience).
• Set AutomationProperty.IsDialog=”true” in the default style so that the InfoBar elements (Icon + Title + Message) are read when an action or close button is first focused. When focus leaves an InfoBar and returns, the InfoBar elements will be re-read. This is special behavior that Narrator has for elements with this property set to true which works pretty well for InfoBar.
• Add Icon to the UIA tree to communicate that element as ‘Information image’, ‘Success image’, ‘Error image’, ‘Warning image’
• When the Severity, Title, or Message has changed the InfoBar should re-raise its notification event. Note that if multiple of these change one after the other, we raise the event just once after all of them are set.

Also, to clarify a few points.

Can you remove the resource names for the close button? Since we're setting AutomationProperty.IsDialog to true the close button (and action button) will have the appropriate context. The extra info associated with the close button would be too much.
For the InfoBarOpened notification instead of the 'Info message severity error' text for the first value, please use the text for the icon that is now added to the UIA tree.

Thanks so much!

I think the changes are implemented now @ranjeshj and @gabbybilka . The icon already was in the UIA tree. Regarding reanouncing the InfoBar, I am not sure how to implement or how to prevent consecutive changes to not overlap.

I think the changes are implemented now @ranjeshj and @gabbybilka . The icon already was in the UIA tree. Regarding reanouncing the InfoBar, I am not sure how to implement or how to prevent consecutive changes to not overlap.

One way might be to batch the changes and raise the automation event on an event that happens later, like say in a LayoutUpdated event and immediately unsubscribe from that LayoutUpdated event.

/azp run

I don't really understand why the tests now fail with the changes made. All changes are in the UIA layer, none of them touch the Visual Tree from a rendering standpoint (only thing I can think of is a reference to elements on the visual tree). But I also don't really understand how the actual asserts in the failing test https://github.com/microsoft/microsoft-ui-xaml/blob/39202578616766de6ab72c4a595959dd8255d6ad/dev/InfoBar/InteractionTests/InfoBarTests.cs#L136
or why they were designed the way they are. @teaP can you maybe help me out a bit here?

/azp run

Weird. The changes are purely accessibility related so I'm not sure why layout test is failing. @teaP @StephenLPeters any thoughts ? @chingucoding can you merge in master so we can be sure something is not stale ?
Also, lets make the UpdateLayout part a separate PR. Thanks.

/azp run

@teaP @chingucoding can you take a look visually and see if there is a difference ?  If not perhaps the test needs to be updated.

I wasn't able to find a visual difference, master branch and this PR seemed pretty much the same with the changes done in the test.

I wasn't able to find a visual difference, master branch and this PR seemed pretty much the same with the changes done in the test.

Yeah, same here. I'm trying to replace it with an API test that does the same thing now.

In this end, it was pretty simply -- I realized the test was indexing into the UIA children of InfoBar, and this change added the icon as the first child, so all the indices were 1 off. :)

/azp run

In this end, it was pretty simply -- I realized the test was indexing into the UIA children of InfoBar, and this change added the icon as the first child, so all the indices were 1 off. :)

Totally didn't think about this. Thank you so much for fixing the test @teaP !


Add check step

Solves #73

Hello @semenovDL and @GustavoCaso, I was wondering why the condition was an exact equality on true rather than a truthy evaluation of res? (excluding a Failure of course)
https://github.com/dry-rb/dry-transaction/blob/08617f7f564f4871670600665b225bdf8cd1be9d/lib/dry/transaction/step_adapters/check.rb#L11
Would you accept a small PR like:
res && !res.is_a?(Failure) ? Success(input) : Failure(input)


_deepEquals() doesn't work when a mixin implements Map

It looks like this could be triggered by a repeated field that contains protobufs that have a mixin that implements Map. It should check for GeneratedMessage first, then Map.
https://github.com/dart-lang/dart-protobuf/blob/master/lib/src/protobuf/utils.dart#L8

Should be fixed in 0.5.1


Display source code of .vue files in the Example tab

Hi guys,
Thank you for a great project! It was one of the reasons why we could make the switch from React to Vue in one of our products :)
One issue though, I am trying to provide full .vue file examples in our vue-play configuration. Like so:
import ButtonWithText from './ButtonWithText.vue'

play('Button', module)
  .add('with text', ButtonWithText)

Looking at the source code, vue-play can read the example code automatically from the template string property, or the custom example property. template doesn't really work in this case, since .vue files are processed differently. Also, I would like to display the entire .vue file source code, not just the template, like in this screenshot:

I tried using raw-loader for Webpack to put the contents of the file into the example property:
import raw from 'raw-loader!./WithText.vue';
ButtonWithText.example = raw;

... but that would just load a compiled version of the .vue file, which makes total sense since vue-loader is in the mix too.
Any tips on how to solve this?

try import raw from '!raw-loader!./WithText.vue';

Thank you, that worked perfectly!
I'm trying to think of a way to implement this directly in vue-play and create a PR - it would be cool with the example property auto-populating itself if the value property in the add function was a vue file.
Since all imports in ES6 needs to be static, I can't see how vue-play itself can load the raw contents dynamically through webpack.

it would be cool with the example property auto-populating itself if add(... value) was a vue file.

this is sure possible, look forward to your PR 😄


Run rules during unit tests in correct order

Description
With KtLintAssertThat an AssertJ style assertThat is created for a specific rule. In addition to that rule, it is possible to run additional rules. In case the rule which is to be tested has defined a VisitorModifier which requires one or more additional rules to be loaded and to be enabled, it is even mandatory that those rules are added to the unit test.
The goal is to execute the rules during unit tests in the same order as when running the CLI version of KtLint. During each unit test a dynamic RuleSet is being created for a limited set of rules (e.g. the rule for which the assertThat is created plus the additional rules specified in the unit tests). The rules in this minimized ruleSet are executed in the order as defined by the VisitorModifier as defined in the rules.

Split naming policy of rule id and rule set id. The naming policy of the latter is not changed. The naming policy of the ruleId is changed so that the ruleSetId prefix can be specified optionally. If the ruleId is not prefixed with a ruleSetId then it is assumed to be equal to "standard". For all experimental rules, the ruleSetId has been added.
Remove obsolete parameter "isUnitTestContext" from VisitorProvider
As the VisitorModifiers are now also used and checked during unit tests, it is required to run the additional rules during the lint phase as well. Some code examples in tests in which the IndentationRule is added as additional rule are changed to comply with that rule.

Checklist

[X] PR description added
[X] tests are added
[ ] CHANGELOG.md is updated

In case of adding a new rule:

[ ] README.md is updated
[ ] Rule has been applied on Ktlint itself and violations are fixed

Closed as due to incorrect merge with master the squashed commit would contain too much changes. Replaced with PR #1470


Invalid Vault URL doesn't throw exception

If we call this API with Invalid Key Vault but with a Good Service Principle it still returns a valid "azure.keyvault.secrets._client.SecretClient" object instead of throwing an exception. Please either provide an API something like isValid() or return a NULL object or any third option which suits design best.
secret_client = SecretClient(vault_url="https://abcd.vault.azure.net/", credential=credential)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 416b3381-c82f-c348-9358-59c20e9aee1f
Version Independent ID: be9b2deb-9d8c-d17e-4208-c3bb5d0ee933
Content: azure.keyvault.secrets.SecretClient class
Content Source: docs-ref-autogen/azure-keyvault-secrets/azure.keyvault.secrets.SecretClient.yml
GitHub Login: @lmazuel
Microsoft Alias: lmazuel

Thanks for the feedback, we’ll investigate asap.

Hello, thank you for creating an issue! This is expected behavior; client constructors don't check whether a given vault exists, since this would require making a call to the service. If the vault URL provided to the client is invalid, or you don't have necessary permissions, an error from azure-core will raise when you perform an operation.
>>> vault_url = "https://nonexistentvaultdoesnotexist.vault.azure.net"
>>> client = SecretClient(vault_url, DefaultAzureCredential())
>>> client.get_secret('secret_name')
Traceback (most recent call last):
...
azure.core.exceptions.ServiceRequestError: <urllib3.connection.VerifiedHTTPSConnection object at 0x000001E313946198>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed

You raise a good though -- some validation upon construction would be convenient. I can leave this issue open for now and discuss with the team whether this would be possible, and come back with an update.

Hello, thank you for creating an issue! This is expected behavior; client constructors don't check whether a given vault exists, since this would require making a call to the service. If the vault URL provided to the client is invalid, or you don't have necessary permissions, an error from azure-core will raise when you perform an operation.
>>> vault_url = "https://nonexistentvaultdoesnotexist.vault.azure.net"
>>> client = SecretClient(vault_url, DefaultAzureCredential())
>>> client.get_secret('secret_name')
Traceback (most recent call last):
...
azure.core.exceptions.ServiceRequestError: <urllib3.connection.VerifiedHTTPSConnection object at 0x000001E313946198>: Failed to establish a new connection: [Errno 11001] getaddrinfo failed

You raise a good though -- some validation upon construction would be convenient. I can leave this issue open for now and discuss with the team whether this would be possible, and come back with an update.

Hello,
I still don't think issue closed is justified because Constructor is returning a valid object even there is nothing initialized properly.
Anyhow thanks for looking into this.


Categories for Events

Motivation
At the dialogue forum, the suggestion was made to categorise events or to be able to categorise them.
Proposed Solution
Which event categories make sense? We suggest the following categories:
Ausstellungen
Bildung
Bürgerangebote & Soziales
Exkursionen & Fahrten
Festivals & Feste
Film, Kino & Theater
Konferenzen & Messen
Konzerte & Shows
Märkte
Party & Nachtleben
Religion & Spiritualität
Seminare, Kurse & Workshop
Shopping
Spielen, Quizzen & Gaming
Sport & Bewegung
Vorträge & Diskussionsrunden
Sonstiges
Alternatives

Additional Context

Design Requirements

This is literally the exact same title as #273 - please enter the issue you're about to create at least once in the search bar to prevent multiple issues for the same topic, thanks!


Added help icons to admin and management pages

Motivation and Context
This PR adds some info icons to the admin pages so admins and lecturers have easier access to the needed information.
Description
You can now hover over small "i" icons to view some information about it
Steps for Testing
Prerequisites:

1 Lecturer / Admin

Log in
Navigate to any admin or course management page
Hover over the icons

Screenshots

The help icons work perfect. I really like the design, it's clean and easy to read and reference.
Perhaps the exact wording of the help message could be double-checked before deployment, for example the documentation URL doesn't seem to be enabled at the moment.


Escape NULL characters for iOS on RN0.59

fix #51
Cc: @gaodeng
@hnq90 Maybe it also needs a patch for Windows?

Confirmed it also works properly on RN0.56.

Found that Android also needs a patch for this issue

Published 2.0.0 on beta channel


Add prompt window, reordering KEY: KID to KID: KEY

add prompt window, reordering KEY: KID to KID: KEY

Personally, I don't think prompt (or alert) is a very good idea, sorry...

sometime useful for some webdl

No problem i added it to Fork. Some sites they block the debugger or wipe the console with a simple trick, so you can't read keys without a prompt window.


Add chainer.dataset.tabular.from_data

split from #7276

jenkins, test this please

Jenkins CI test (for commit 1a532810d393ab4bfe7b5e9785069a242c23c102, target branch master) failed with status FAILURE.

jenkins, test this please

Jenkins CI test (for commit feb6a3bc28c3d814bcb0e18d936e8aa598009615, target branch master) failed with status FAILURE.

jenkins, test this please

Jenkins CI test (for commit a5ea1707b5e21a9bbe8f1996dea5cfc4bea7e1dd, target branch master) failed with status FAILURE.

@beam2d I reflected your comments. The failure of Jenkins seems not related to this PR.

Thanks, LGTM.
CIs, test this please.

Thanks, LGTM.

Jenkins CI test (for commit a5ea1707b5e21a9bbe8f1996dea5cfc4bea7e1dd, target branch master) failed with status FAILURE.


System.ArgumentOutOfRangeException: Count cannot be less than zero. exception thrown by ResolveAddressAndIdentityAsyn

We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version.

Describe the bug
Randomly hitting Aggregate exceptions while querying CosmosDB Backend resource
To Reproduce
Intermittent issue.  Stack trace is in additional information
Expected behavior
Does not throw exception
Actual behavior
Provide a description of the actual behavior observed.
Environment summary
SDK Version:  <IP_ADDRESS>-preview3 /  <IP_ADDRESS>-preview
OS Version (e.g. Windows, Linux, MacOSX) : Windows
Additional context
CosmosDBTrace Error: 0 : Exception in CosmosDB Request pipeline for account localhost and API MongoService: System.AggregateException: One or more errors occurred. ---> System.ArgumentOutOfRangeException: Count cannot be less than zero.
Parameter name: count
at System.String.CopyTo(Int32 sourceIndex, Char[] destination, Int32 destinationIndex, Int32 count)
at System.IO.StreamWriter.Write(String value)
at System.Diagnostics.TextWriterTraceListener.Write(String message)
at System.Diagnostics.TraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id)
at System.Diagnostics.TraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String format, Object[] args)
at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String format, Object[] args)
at Microsoft.Azure.Cosmos.AddressResolver.d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.AddressResolver.d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.AddressSelector.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.AddressSelector.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.StoreReader.d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.StoreReader.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.QuorumReader.d__14.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.QuorumReader.d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.ReplicatedResourceClient.<>c__DisplayClass25_0.<b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.RequestRetryUtility.d__22.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()    at Microsoft.Azure.Documents.ShouldRetryResult.ThrowIfDoneTrying(ExceptionDispatchInfo capturedException)    at Microsoft.Azure.Documents.RequestRetryUtility.<ProcessRequestAsync>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.StoreClient.d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Documents.ServerStoreModel.d__15.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Handlers.TransportHandler.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Handlers.AbstractRetryHandler.d__2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Handlers.AbstractRetryHandler.d__1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.Handlers.RequestInvokerHandler.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.Cosmos.ExecUtils.d__41.MoveNext()    --- End of inner exception stack trace ---    at System.Threading.Tasks.Task1.GetResultCore(Boolean waitCompletionNotification)
at Microsoft.Azure.Cosmos.CosmosFeedResultSetIteratorCore.b__7_0(Task1 task)    at System.Threading.Tasks.ContinuationResultTaskFromResultTask2.InnerInvoke()
at System.Threading.Tasks.Task.Execute()

Issue is understood and related to TraceListeners configured outside of SDK


no module found crypto

I have done everything but still i get no module found what can i do ?

There's a number of comments in openthread/openthread#1137
https://github.com/openthread/openthread/issues/1137 that describe how to
address this issue.
--
Jonathan Hui
On Wed, Jul 28, 2021 at 4:31 AM syrine-design @.***>
wrote:

[image: Capture]
https://user-images.githubusercontent.com/63754152/127315327-05af424f-f324-4d59-8191-87091b05edf7.PNG
I have done everything but still i get no module found what can i do ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openthread/openthread/issues/6866, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD3E7ABNAXAUUTPHE42DJMLTZ7TCNANCNFSM5BEFKFTQ
.

Closing stale issue.


Add Connection::is_draining FFI

Connection::is_draining was introduced here but was not exposed for FFI

Merged, thanks @kachayev!


Build failing on "Cloning repository" activity

Describe the bug
The builds were working just fine and suddenly started to fail in the "Cloning repository" activity.
This is the log:
2019-09-09T16:55:37.647Z [INFO]: Git SSH Key acquired
2019-09-09T16:55:37.746Z [INFO]: # Cloning repository: git@gitlab.com:xxxxxxx
2019-09-09T16:55:37.862Z [INFO]: Agent pid 70
2019-09-09T16:55:37.869Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
2019-09-09T16:55:37.922Z [INFO]: Cloning into 'vue-frontend'...
2019-09-09T16:55:38.025Z [INFO]: Warning: Permanently added the ECDSA host key for IP address 'xxx.xxx.xxx.xxx' to the list of known hosts.
2019-09-09T16:55:38.771Z [INFO]: # Checking for Git submodules at: /codebuild/output/src337110790/src/vue-frontend/.gitmodules
2019-09-09T16:55:38.800Z [INFO]: # Retrieving cache...
2019-09-09T16:55:38.846Z [INFO]: # Extracting cache...
2019-09-09T16:55:38.855Z [INFO]: # Extraction completed
2019-09-09T16:55:38.856Z [INFO]: # Retrieving environment cache...
2019-09-09T16:55:38.889Z [INFO]: # Retrieved environment cache
2019-09-09T16:55:38.968Z [WARNING]: ! Unable to patch packages...
2019-09-09T16:55:38.981Z [ERROR]: !!! TypeError: Cannot read property 'indexOf' of null
2019-09-09T16:55:38.981Z [INFO]: # Starting environment caching...
2019-09-09T16:55:38.982Z [INFO]: # Environment caching completed
Terminating logging...

To Reproduce
(Re)execute a build in the AWS Console.
Additional context

Repo is hosted on gitlab.com
Build instructions are the same with gitlab runner and does not fail (even thought, the error reported here in Amplify don't get to the build activity, but helps to discard any code related issue)
I thought the issue was caused by the detached from HEAD message (from earlier builds) but now the message is gone and keeps failing.
I deleted the app and create a new from the same repo and keeps failing.
I copied all the code to a new repo and created a new app. and it keeps failing :(

Edit1:

Changed the build environment to a clean node image (node:latest) and fails with the same log.

We're getting the exact same error on our github hosted repo.
Also the error( in the cloning repository step) is sometimes:
2019-09-10T08:51:43.646Z [ERROR]: !!! TypeError: undefined is not a function

@dobo-cc @tianmarin we are looking at this as the highest priority. Can you please share your appid? Found in App settings > General

Hey @swaminator! Thanks for looking into it. Ours is apps/d1q08he2j3wck8.

thank you @swaminator !
Our failing apps are:

d2gvdgzls8h2p
d4myvmthewkzx -> If necessary you can rebuild this one

Hey @tianmarin, are you using an amplify.yml in your repositories? If so could you please share one of them?
Thanks!

Thank you @anatonie !
I have been playing around with it since the bug was presented, this is the final version.
amplify.yml
version: 0.1
backend:
  phases:
    build:
      commands:
        - '# Execute Amplify CLI with the helper script'
        - amplifyPush --simple
frontend:
  phases:
    build:
      commands:
        - npm cache clean
        - #npm cache clean --force
        - #rm -rf node_modules && rm package-lock.json && npm install
        - #npm install --global vue-cli
        - npm install
        - npm run build
  artifacts:
    baseDirectory: dist
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

So right now you are passing null commands in the build phase:
commands:
  - # comment

This isn't a valid command, and is causing the issue, but the service isn't properly reporting the issue (we are working on this).
To fix this and retain your comments, You can format like this:
commands:
  - some command
  # - some commented command

@dobo-cc you're having a similar issue with YML formatting, you have a line that includes a colon (:). YML uses colons as an indicator so this is causing issues, and like above, the service is not properly reporting this.
You can wrap you command in quotes to correct this:
commands:
  - "some command with: a colon"
  # if you need quotes inside this command, please escape them
  - "some command with: a colon and \"quoted text\""

If you guys could please give those a try and report back that'd be much appreciated!

@anatonie you are totally correct!
once those null commands were removed the build process worked without issues.
Note that amplify.ymlmust be updated in the repo. Updating the Build settings in the console will lead to the same error.

@tianmarin I'm glad to hear that sorted it out for you!
And yes, if you have amplify.yml in your repository that takes precedence over the settings in the console.

For all the other folks here who have upvoted the issue, can you check your amplify.yml file?

@swaminator That fixed it - thanks a lot.

@anatonie , @swaminator, should I close this issue or will it be used to prevent the TypeError: Cannot read property 'indexOf' of null error?

2021-06-25T03:45:27.761Z [WARNING]: !Error: ENOENT: no such file or directory, open '/codebuild/output/src817206887/src/transiot/amplify.yml'
2021-06-25T03:45:27.785Z [INFO]: # Retrieving environment cache...
2021-06-25T03:45:27.812Z [INFO]: # Retrieved environment cache
2021-06-25T03:45:27.812Z [WARNING]: !Cannot read property 'split' of undefined
2021-06-25T03:45:27.823Z [ERROR]: !!! TypeError: undefined is not a function
2021-06-25T03:45:27.823Z [INFO]: # Starting environment caching...
2021-06-25T03:45:27.823Z [INFO]: # Environment caching completed
Terminating logging...
Added the custom header still failed


Feature/bge lc  default value validation

Critical Changes
Changes

Set Field Options obeys and validates data types of each field's default value.

Issues Closed
New Metadata
Deleted Metadata

**lurch: attach W-029454

Tracking W-029454

QA has Passed.


Add coding standards to CONTRIBUTING.md

The coding standards should be added to the CONTRIBUTING.md file so everyone knows the rules around indentation, and other parts of syntax humans moan about endlessly.

I have linked to the Google guide in the file, and we should generally do everything it says. I'll switch to 2 space indents at some point in the future when there aren't any pull requests ongoing.


Fixed code example in accessibility section of advanced page

I fixed code example in accessibility section.
Because aria-description is not read dynamically. And if you use role="alert" at initial rendering, screen reader unintended to read contents.
About role="alert"
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_alert_role
https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Techniques/Using_the_aria-invalid_attribute

This is great! you are right. <3


Dwango.nico.nair version latest

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

2024-03-08T04:58:37.4768368Z ##[error] One or more errors occurred. (The file was not found. Verify git path must match with the casing of the file in disk. Not found file on 'manifests\d\Dwango\nico\nair\latest\Dwango.nico.nair.installer.yaml') The file was not found. Verify git path must match with the casing of the file in disk. Not found file on 'manifests\d\Dwango\nico\nair\latest\Dwango.nico.nair.installer.yaml'

(Automated response - build 869.)