[#7971] Disable send if only backticks/whitespace

Details
Messages containing only backticks and whitespace are not properly handled on both the front end and back end. So this change does not allow the user to send these problematic (and effectively empty) messages.
Previously, the send button was disabled when a message contained only whitespace. This change makes things a little more strict and disables the send button if the message contains only whitespace and backticks.
Fixed Issues
$ https://github.com/Expensify/App/issues/7971
Tests

Start chat session
Verify that message field is empty and that send button is disabled
Enter a short message (e.g. test)
Verify that the send button is enabled
Enter message with correctly formatted backticks and some text - for example

`test`

Verify that the send button is enabled
Send the message
Verify that message was sent and displays correctly
Go to a different chat session and return the the original chat session
Verify that most recent message (the backtick message) is still there
Enter message with only backticks and whitespace - for example

`    `

Verify that send button is disabled

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

PR Review Checklist

Contributor (PR Author) Checklist

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

[ ] I added steps for local testing in the Tests section
[ ] I added steps for Staging and/or Production testing in the QA steps section
[ ] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] 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)

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

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

[ ] 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)
[ ] I followed proper code patterns (see Reviewing the code)

[ ] 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)
[ ] I verified that comments were added to code that is not self explanatory
[ ] 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.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[ ] 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.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I followed the guidelines as stated in the Review Guidelines
[ ] 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)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] 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
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] Any functional components have the displayName property
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] 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)
[ ] 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)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose and it is

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

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

[ ] 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)
[ ] 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.

PR Reviewer Checklist

[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] 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)
[ ] 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)

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

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

[ ] 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)
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] 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).
[ ] I verified that comments were added to code that is not self explanatory
[ ] 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.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[ ] 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.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] 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
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] Any functional components have the displayName property
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] 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)
[ ] 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)
[ ] All JSX used for rendering exists in the render method
[ ] 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

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

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

[ ] 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)
[ ] 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.

QA Steps

Start chat session
Verify that message field is empty and that send button is disabled
Enter a short message (e.g. test)
Verify that the send button is enabled
Enter message with correctly formatted backticks and some text - for example

`test`

Verify that the send button is enabled
Send the message
Verify that message was sent and displays correctly
Go to a different chat session and return the the original chat session
Verify that most recent message (the backtick message) is still there
Enter message with only backticks and whitespace - for example

`    `

Verify that send button is disabled

[ ] Verify that no errors appear in the JS console

Screenshots
Web

Mobile Web

Desktop

iOS

Android

I have read the CLA Document and I hereby sign the CLA.

@AndrewGable can you initiate the workflows

@frenkield can you try signing again for CLA

I have read the CLA Document and I hereby sign the CLA

@AndrewGable I'm not sure why CLA is failing.

Checks are passing now ✅

So sorry, @Santhosh-Sellavel, I don't understand. At the end of the video there are only backticks and whitespace in the message. So the send button is correctly disabled.
For a moment in the video there's also a period in the message. So at that point the send button is correctly enabled. But then the period disappears. Does pressing enter make the period disappear?

Sorry, @Santhosh-Sellavel! I just deleted a pointless comment.
I see the issue. I'll fix it. Thanks!

@AndrewGable Can you help start workflow again?

PR Reviewer Checklist

[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] 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)
[ ] 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)

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

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

[ ] 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)
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] 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).
[ ] I verified that comments were added to code that is not self explanatory
[ ] 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.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[ ] 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.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] 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
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] Any functional components have the displayName property
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] 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)
[ ] 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)
[ ] All JSX used for rendering exists in the render method
[ ] 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

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

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

[ ] 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)
[ ] 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.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Cherry-picked to staging by @sketchydroide in version: 1.1.57-8 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @chiragsalian in version: 1.1.57-17 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


feat: add accordion to decision box to list instalments (hl-1497)

Description :sparkles:
Continued from #3498.

Implement "Instalments" accordion into decision box

Lists both instalments

Add validation to Instalment serializer
Make instalment patch endpoint change application to archived if second instalment is cancelled
Cancelling 2nd instalment from ApplicationListForInstalments now uses popup
Other minor details changed for ApplicationListForInstalments

APPLICANT branch is deployed to platta: https://helsinkilisa-ui-pr3515.dev.hel.ninja :rocket::rocket::rocket:

API branch is deployed to platta: https://helsinkilisa-pr3515.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

TestCafe result is success for https://helsinkilisa-ui-handler-pr3515.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe result is success for https://helsinkilisa-ui-pr3515.dev.hel.ninja :laughing::tada::tada::tada:


Adding KV templates

@SnehaGunda,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@vikasnav did you had a chance to look at this PR?


"Deep linking" disparate documentation resources together

What is your issue?
Our docs have a general issue with having lots of related resources that are not necessarily linked together in a useful way. This results in users (including myself!) getting "stuck" in one part of the docs and being unaware of material that would help them solve their specific issue.
To give a concrete example, if a user wants to know about coarsen, there is relevant material:

In the coarsen class docstring
On the reshaping page
On the computations page
On the "how do I?" page
On the tutorial repository

Different types of material are great, but only some of these resources are linked to others. Coarsen is actually pretty well covered overall, but for other functions there might be no useful linking at all, or no examples in the docstrings.

The biggest missed opportunity here is the way all the great content on the tutorial.xarray.dev repository is not linked from anywhere on the main documentation site (I believe). To address that we could either (a) integrate the tutorial.xarray.dev material into the main site or (b) add a lot more cross-linking between the two sites.
Identifying sections that could be linked and adding links would be a great task for new contributors.

Another concrete example that came up at today's office hours (#8220) was content related to apply_ufunc.


Special filters

So. The Client currently filters by
active=True & active=False, which now reflects things in a window. I like that pattern actually...so I decided I'd let the backend handle this rather than update the client atm

@MichaelButkovic @mparent61

LGTM

I like re-using the active filter, simplifies client interaction

Otherwise :+1:


dts: arm: nxp: lpc55s1x: add ctimer nodes

Add CTimer devicetree nodes for the NXP LPC55S1x.
Signed-off-by: Henrik Brix Andersen<EMAIL_ADDRESS>

*** Booting Zephyr OS build v3.7.0-rc2-46-g866fa6ad69e5 ***
Running TESTSUITE counter_basic
===================================================================
START - test_all_channels
Testing ctimer@8000
Testing ctimer@9000
Testing ctimer@28000
Testing ctimer@29000
Testing ctimer@2A000
 PASS - test_all_channels in 0.661 seconds
===================================================================
START - test_cancelled_alarm_does_not_expire
Skipped for ctimer@8000
Skipped for ctimer@9000
Skipped for ctimer@28000
Skipped for ctimer@29000
Skipped for ctimer@2A000
 SKIP - test_cancelled_alarm_does_not_expire in 0.512 seconds
===================================================================
START - test_late_alarm
Skipped for ctimer@8000
Skipped for ctimer@9000
Skipped for ctimer@28000
Skipped for ctimer@29000
Skipped for ctimer@2A000
 SKIP - test_late_alarm in 0.512 seconds
===================================================================
START - test_late_alarm_error
Skipped for ctimer@8000
Skipped for ctimer@9000
Skipped for ctimer@28000
Skipped for ctimer@29000
Skipped for ctimer@2A000
 SKIP - test_late_alarm_error in 0.512 seconds
===================================================================
START - test_multiple_alarms
Testing ctimer@8000
Testing ctimer@9000
Testing ctimer@28000
Testing ctimer@29000
Testing ctimer@2A000
 PASS - test_multiple_alarms in 0.780 seconds
===================================================================
START - test_set_top_value_with_alarm
Testing ctimer@8000
Testing ctimer@9000
Testing ctimer@28000
Testing ctimer@29000
Testing ctimer@2A000
 PASS - test_set_top_value_with_alarm in 1.055 seconds
===================================================================
START - test_short_relative_alarm
Skipped for ctimer@8000
Skipped for ctimer@9000
Skipped for ctimer@28000
Skipped for ctimer@29000
Skipped for ctimer@2A000
 SKIP - test_short_relative_alarm in 0.517 seconds
===================================================================
START - test_single_shot_alarm_notop
Testing ctimer@8000
Testing ctimer@9000
Testing ctimer@28000
Testing ctimer@29000
Testing ctimer@2A000
 PASS - test_single_shot_alarm_notop in 0.860 seconds
===================================================================
START - test_single_shot_alarm_top
Testing ctimer@8000
Testing ctimer@9000
Testing ctimer@28000
Testing ctimer@29000
Testing ctimer@2A000
 PASS - test_single_shot_alarm_top in 0.860 seconds
===================================================================
TESTSUITE counter_basic succeeded
Running TESTSUITE counter_no_callback
===================================================================
START - test_set_top_value_without_alarm
Testing ctimer@8000
Testing ctimer@9000
Testing ctimer@28000
Testing ctimer@29000
Testing ctimer@2A000
 PASS - test_set_top_value_without_alarm in 0.536 seconds
===================================================================
TESTSUITE counter_no_callback succeeded

------ TESTSUITE SUMMARY START ------

SUITE PASS - 100.00% [counter_basic]: pass = 5, fail = 0, skip = 4, total = 9 duration = 6.269 seconds
 - PASS - [counter_basic.test_all_channels] duration = 0.661 seconds
 - SKIP - [counter_basic.test_cancelled_alarm_does_not_expire] duration = 0.512 seconds
 - SKIP - [counter_basic.test_late_alarm] duration = 0.512 seconds
 - SKIP - [counter_basic.test_late_alarm_error] duration = 0.512 seconds
 - PASS - [counter_basic.test_multiple_alarms] duration = 0.780 seconds
 - PASS - [counter_basic.test_set_top_value_with_alarm] duration = 1.055 seconds
 - SKIP - [counter_basic.test_short_relative_alarm] duration = 0.517 seconds
 - PASS - [counter_basic.test_single_shot_alarm_notop] duration = 0.860 seconds
 - PASS - [counter_basic.test_single_shot_alarm_top] duration = 0.860 seconds

SUITE PASS - 100.00% [counter_no_callback]: pass = 1, fail = 0, skip = 0, total = 1 duration = 0.536 seconds
 - PASS - [counter_no_callback.test_set_top_value_without_alarm] duration = 0.536 seconds

------ TESTSUITE SUMMARY END ------

===================================================================
PROJECT EXECUTION SUCCESSFUL

@henrikbrixandersen 4.0?

@henrikbrixandersen 4.0?

It's only touching the LPC55S1x SoC family and one associated board and all tests pass. The same nodes are present in other LPC55xxx family SoC devicetrees, so the risk of something breaking is very low.
I'd like to see it in v3.7.0, but won't push for it.

@henrikbrixandersen 4.0?

It's only touching the LPC55S1x SoC family and one associated board and all tests pass. The same nodes are present in other LPC55xxx family SoC devicetrees, so the risk of something breaking is very low.
I'd like to see it in v3.7.0, but won't push for it.

I'm fine with it for 3.7.


Word StartTime & EndTime should be changed by reference kaldi nnet3 code.

Thank you for your effort and achievement.
I have studied Kaldi (Speech-Recognition Tool) for years.
If you read the below Kaldi code,
the word's start_time and end_time is not same between below code and 'decoder.hpp' code.
Kaldi code : https://github.com/kaldi-asr/kaldi/blob/master/src/online2bin/online2-tcp-nnet3-decode-faster.cc#L324
In 'decoder.hpp' code, 'frame_subsampling' is missed.
could you check the decoder's word's start_time and end_time.
Thank you.

@pskrunner14 i am assuming you might have better view on this?


Ingress to access Vault

I have been deployed the vault example, but dont can configure ingress to access externally
Vault
apiVersion: "vault.security.coreos.com/v1alpha1"
kind: "VaultService"
metadata:
  name: "example"
spec:
  nodes: 1
  version: "0.10.4"

Ingress
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.class: nginx
  generation: 6
  labels:
    app: vault
  name: kube-vault
  namespace: vault-production
spec:
  rules:
  - host: secret.devops.agilitynetworks.com.br
    http:
      paths:
      - backend:
          serviceName: example
          servicePort: 8200
        path: /
  tls:
  - hosts:
    - secret.devops.agilitynetworks.com.br
    secretName: tls-secret-wildcard

Secret
kubectl get secret tls-secret-wildcard
NAME                  TYPE                DATA      AGE
tls-secret-wildcard   kubernetes.io/tls   2         5d

Fix after insert annotations below:
annotations:
kubernetes.io/ingress.class: nginx
ingress.kubernetes.io/secure-backends: "true"
ingress.kubernetes.io/ssl-passthrough: "true"


Automatic Number plate Recognition System for visually impaired

Feature Request: Automatic Number Plate Recognition System for Visually Impaired
Problem: People who are visually impaired struggle to identify vehicles, especially their license plates. This can be a challenge in various situations.
Solution: An Automatic Number Plate Recognition (ANPR) system designed specifically for visually impaired users. This system would leverage the power of computer vision libraries to achieve its functionality.

Technical Implementation: The Automatic Number Plate Recognition (ANPR) System in this project utilizes OpenCV, Python EasyOCR, and Imutils.

OpenCV: An open-source library for computer vision tasks, providing image processing and analysis functionalities.
Python EasyOCR: A user-friendly library specifically designed for Optical Character Recognition (OCR) tasks, making it easy to extract text from images like license plates.
Imutils: A collection of utility functions built on top of OpenCV, simplifying common image processing operations.

These libraries will be used to:

Capture an image of a vehicle's license plate using a smartphone camera or a smart assistant device with a camera.
Detect the presence of a license plate in the captured image.
Perform OCR on the detected license plate to read the characters.

This approach offers a  powerful and user-friendly solution for visually impaired users, thanks to the capabilities of these computer vision libraries.
@TAHIR0110 pls assign me this issue under GSSoC '24

@Atharv714 why did you close the issue ?


doc(readme): improve the beauty of it <3

Coverage remained the same at 98.175% when pulling f278420b29ad2c1d8c1c8ce5277c8637980330e2 on RomainForks:develop into 46d1437b3fc08ed5d3316fe1e10a27bdd50232cd on adonisjs:develop.

Coverage remained the same at 98.175% when pulling 7fdbb8fb130034016fae370720eb7d6f030d0542 on RomainForks:develop into 46d1437b3fc08ed5d3316fe1e10a27bdd50232cd on adonisjs:develop.

Coverage remained the same at 98.175% when pulling 7fdbb8fb130034016fae370720eb7d6f030d0542 on RomainForks:develop into 46d1437b3fc08ed5d3316fe1e10a27bdd50232cd on adonisjs:develop.

Coverage remained the same at 98.175% when pulling 5a38c828ddf5779bf860b1e12c626bb09b54395d on RomainForks:develop into 46d1437b3fc08ed5d3316fe1e10a27bdd50232cd on adonisjs:develop.

Coverage remained the same at 98.175% when pulling 2f580da3f9edcb432d30cd01d0d905129558cbb2 on RomainForks:develop into 46d1437b3fc08ed5d3316fe1e10a27bdd50232cd on adonisjs:develop.

Coverage remained the same at 98.175% when pulling 2f580da3f9edcb432d30cd01d0d905129558cbb2 on RomainForks:develop into 46d1437b3fc08ed5d3316fe1e10a27bdd50232cd on adonisjs:develop.

Coverage remained the same at 98.175% when pulling 2f580da3f9edcb432d30cd01d0d905129558cbb2 on RomainForks:develop into 46d1437b3fc08ed5d3316fe1e10a27bdd50232cd on adonisjs:develop.

Coverage remained the same at 98.175% when pulling 2f580da3f9edcb432d30cd01d0d905129558cbb2 on RomainForks:develop into 46d1437b3fc08ed5d3316fe1e10a27bdd50232cd on adonisjs:develop.

Thanks @coveralls! We are now sure that the coverage remained the same! 🎉

Coverage remained the same at 98.175% when pulling 2f580da3f9edcb432d30cd01d0d905129558cbb2 on RomainForks:develop into 46d1437b3fc08ed5d3316fe1e10a27bdd50232cd on adonisjs:develop.


reports match when no match exists

let re = Regex::new("^-[a-z]").unwrap();
assert!(!re.is_match("r-f")); // fails
assert!(re.find("r-f").is_none()); // panics

I think the issue here is that we are incorrectly combining the results of a prefix scan (for -) with the anchor.

Reported via https://github.com/docopt/docopt.rs/issues/172


Involt dynamic elements buffer overload

Rangeslider and knob-send have issue with (I guess) buffer overload from hardware side. When they have to send high amount of values when scrolling - for example scrolling from 0 to 255 and then back to 0 will in most cases cause some kind of overload at some point (sending PxVxxx string x255 twice) and we will not return to 0 even if in app it's selected.
If I don't find a solution soon it's going to be depreciated. If so, the values will be send on release event only. It's better to have something that works correctly than having something nice which is far from perfect (and it's bad visually when controlling LEDs and user see how imperfect this solution is)
Maybe these elements should include .fluid parameter that will trigger the element type.

The send-on-release thing is now completed and adding to these elements .fluid class will trigger the previous behaviour.
Technically, the issue is still not fixed.


Declaring a unary function type alias reduces type safety

No error:
type UnaryFn<I, O> = I => 0

type Tap = <P>() => UnaryFn<P, P>

declare var tap: Tap

const foo: number = tap()('foo')

Error, as expected:
type Tap = <P>() => (P => P)

declare var tap: Tap

const foo: number = tap()('foo')

You have a typo in your example without the error. You probably mean to have UnaryFn return O, but you wrote 0 (the number), which is why Foo can be a number.


[stable/airflow] Google Cloud Platform Credentials Error

Hi Currently getting the following error in airflow using airflow HELM.
Any ideas on this?
The private_key argument is deprecated. Construct a credentials object, instead, by using the google.oauth2.service_account.Credentials.from_service_account_file or google.oauth2.service_account.Credentials.from_service_account_info class method from the google-auth package.

This is not related to the airflow chart.


Pass the graphQLApiUrl for useBlockPreview through the IFrameBridge

Description
When the site uses block loaders they are normally rendered on the server side - except when used for the block-preview. This use cases normally requires a different (publicly available) api url, which is sometimes hard to provide on the client side.
This PR passes the api url through the iframebrigde and therefore makes defining the public api url in the site obsolete.
Changeset

[X] I have verified if my change requires a changeset
Do we need a migration guide to remove the public api url from the site?

Related tasks and documents
https://vivid-planet.atlassian.net/browse/COM-1284

Do we need a migration guide to remove the public api url from the site?

This is only possible if everything is done through BFFs. Can we assume this?

I don't understand. What does this have to do with BFF?

There are projects that load data directly from the GraphQL Api using the public Api Url. If devs would remove the environment variable, those requests wouldn't work any longer.


String formatting in Wren

Hi, I was wondering if Wren provides any formatting of strings. Either that be printf like formatting, etc.

Just string interpolation for now! e.g "string %(wren expression)".
(A good minimal string format function would be nice to have in the near future).

There is a fmt module provided by PureFox48 (https://github.com/NinjasCL-labs/wren-rosetta/blob/main/src/fmt.wren).

fmt looks pretty good, but not having a minimal string format function sounds extremely lacking in terms of a std library.

fmt looks pretty good, but not having a minimal string format function sounds extremely lacking in terms of a std library.


add user id to be show in the user page in the system console

Summary
Adds the user id information in the system console -> user page
As a mattermost system administrator some tasks i need to know the userid, either to fill this info in some plugin config or to do any other task
And the only way to get that is using the dev tools (too hacky) or using the CLI which I need to have access to the server (too bad)

Ticket Link
jira:  https://mattermost.atlassian.net/browse/MM-18153

Love this idea! Is there a ticket for this?

@lindalumitchell no but i will create :)

@lindalumitchell jira: https://mattermost.atlassian.net/browse/MM-18153

Thanks @cpanato! My only nit is that I think this should be a story rather than a task, as it affects end-user functionality, and UI tests (and docs?) will need to be run through and updated, etc. :)

@lindalumitchell update the jira ticket

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-3565.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Test server destroyed


Roll Engine from 9ce1e5c5c7e7 to 1a8349888e97 (69 revisions)

Roll Engine from 9ce1e5c5c7e7 to 1a8349888e97 (69 revisions)
https://github.com/flutter/engine/compare/9ce1e5c5c7e7...1a8349888e97
2020-05-26<EMAIL_ADDRESS>Revert "Update CanvasKit to 0.15.0 (#18570)" (flutter/engine#18600)
2020-05-26<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from TSEOq... to hr-HZ... (flutter/engine#18594)
2020-05-26<EMAIL_ADDRESS>Roll Dart SDK from 65113fd73dec to 9e3b0289197d (2 revisions) (flutter/engine#18593)
2020-05-26<EMAIL_ADDRESS>Roll Skia from b6d158aaf3dd to e4b4ca1050b9 (1 revision) (flutter/engine#18592)
2020-05-26<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from DzG49... to pLp67... (flutter/engine#18591)
2020-05-24<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from Oz016... to TSEOq... (flutter/engine#18590)
2020-05-23<EMAIL_ADDRESS>Roll Skia from afd8a6c6ae87 to b6d158aaf3dd (3 revisions) (flutter/engine#18588)
2020-05-22<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from 99Z4_... to Oz016... (flutter/engine#18582)
2020-05-22<EMAIL_ADDRESS>Roll Skia from ec31488ace66 to afd8a6c6ae87 (1 revision) (flutter/engine#18581)
2020-05-22<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from Kvwlr... to DzG49... (flutter/engine#18580)
2020-05-22<EMAIL_ADDRESS>Roll Skia from 80abb89c3632 to ec31488ace66 (1 revision) (flutter/engine#18579)
2020-05-22<EMAIL_ADDRESS>Roll Skia from da90c3765908 to 80abb89c3632 (4 revisions) (flutter/engine#18577)
2020-05-22<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from zNmv... to 99Z4... (flutter/engine#18576)
2020-05-22<EMAIL_ADDRESS>Roll Skia from 317dce5c81c0 to da90c3765908 (1 revision) (flutter/engine#18575)
2020-05-22<EMAIL_ADDRESS>Roll Dart SDK from 4ee57c08e0a6 to 65113fd73dec (3 revisions) (flutter/engine#18574)
2020-05-22<EMAIL_ADDRESS>Roll Skia from 67e21a19259b to 317dce5c81c0 (3 revisions) (flutter/engine#18573)
2020-05-22<EMAIL_ADDRESS>Update CanvasKit to 0.15.0 (flutter/engine#18570)
2020-05-21<EMAIL_ADDRESS>Roll Skia from 3d52abc84667 to 67e21a19259b (1 revision) (flutter/engine#18568)
2020-05-21<EMAIL_ADDRESS>Roll Dart SDK from 396b5fb7a97d to 4ee57c08e0a6 (6 revisions) (flutter/engine#18567)
2020-05-21<EMAIL_ADDRESS>Add fl_value_to_string (flutter/engine#18540)
2020-05-21<EMAIL_ADDRESS>Roll Skia from 1e63279156d6 to 3d52abc84667 (5 revisions) (flutter/engine#18566)
2020-05-21<EMAIL_ADDRESS>null-annotate semantics.dart (flutter/engine#18553)
2020-05-21<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from ciqRH... to Kvwlr... (flutter/engine#18565)
2020-05-21<EMAIL_ADDRESS>Roll Skia from b37105ea6cca to 1e63279156d6 (9 revisions) (flutter/engine#18564)
2020-05-21<EMAIL_ADDRESS>Implement WriteAtomically using write/fsync on all platforms, and enable (flutter/engine#18320)
2020-05-21<EMAIL_ADDRESS>Roll Dart SDK from ecce58c1e354 to 396b5fb7a97d (2 revisions) (flutter/engine#18560)
2020-05-21<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from RNByJ... to _zNmv... (flutter/engine#18558)
2020-05-21<EMAIL_ADDRESS>[profiling] Memory Profiling support for iOS (flutter/engine#18516)
2020-05-21<EMAIL_ADDRESS>Roll Skia from 22636205ce92 to b37105ea6cca (2 revisions) (flutter/engine#18557)
2020-05-21<EMAIL_ADDRESS>Roll Dart SDK from d551980ac9fc to ecce58c1e354 (2 revisions) (flutter/engine#18556)
2020-05-21<EMAIL_ADDRESS>Roll Dart SDK from bf7e9d13d730 to d551980ac9fc (6 revisions) (flutter/engine#18551)
2020-05-21<EMAIL_ADDRESS>Roll Skia from 4c0578632217 to 22636205ce92 (4 revisions) (flutter/engine#18550)
2020-05-21<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from ThMeW... to ciqRH... (flutter/engine#18549)
2020-05-21<EMAIL_ADDRESS>Roll Skia from 67ff541ac116 to 4c0578632217 (1 revision) (flutter/engine#18547)
2020-05-21<EMAIL_ADDRESS>Let run_tests.py just stream output (flutter/engine#18534)
2020-05-21<EMAIL_ADDRESS>Add FlKeyEventPlugin (flutter/engine#18313)
2020-05-21<EMAIL_ADDRESS>Add tests for StandardMethodCodec (flutter/engine#18521)
2020-05-21<EMAIL_ADDRESS>Roll Skia from f83baf230c69 to 67ff541ac116 (1 revision) (flutter/engine#18545)
2020-05-21<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from 3o9aQ... to RNByJ... (flutter/engine#18543)
2020-05-21<EMAIL_ADDRESS>fuchsia: Fix runtime_tests and shell_tests (flutter/engine#18492)
2020-05-21<EMAIL_ADDRESS>Roll Skia from d2dc8ddcdf5e to f83baf230c69 (2 revisions) (flutter/engine#18539)
2020-05-21<EMAIL_ADDRESS>Roll Dart SDK from 7aa8656d1dd8 to bf7e9d13d730 (21 revisions) (flutter/engine#18538)
2020-05-21<EMAIL_ADDRESS>Add FlMethodChannel, FlMethodCodec, FlStandardMethodCodec and FlJsonMethodCodec (flutter/engine#18220)
2020-05-20<EMAIL_ADDRESS>[web] Fix arc rendering when it starts a new sub path. (flutter/engine#18535)
2020-05-20<EMAIL_ADDRESS>Send platformResolvedLocale from iOS embedder (flutter/engine#18519)
2020-05-20<EMAIL_ADDRESS>System mouse cursor: macOS (flutter/engine#18131)
...

AutoRoller is stopped; closing the active roll.


Allow user to choose different underlying platforms to provision tenant master

abstract Create/Delete Virtualcluster functions, and encapsulate
them into a new interface MasterProvisioner
adapt existing minikube implementation to MasterProvisioner interface
add template of MasterProvisionerAliyun

/hold

/ok-to-test

/hold cancel

/lgtm
/approve

fixes: #324


For long-lived grpc streaming messages, can we add parameters for ocgrpc to control the number of MessageEvents in a single span?

Is your feature request related to a problem? Please describe.
https://github.com/dgraph-io/dgraph/issues/3032
Describe the solution you'd like
We add parameters to ocgrpc to control the number of MessageEvents in a single span.
Describe alternatives you've considered
Additional context

Sorry, I see that the latest version is already supported.
const (
	// DefaultMaxAnnotationEventsPerSpan is default max number of annotation events per span
	DefaultMaxAnnotationEventsPerSpan = 32

	// DefaultMaxMessageEventsPerSpan is default max number of message events per span
	DefaultMaxMessageEventsPerSpan = 128

	// DefaultMaxAttributesPerSpan is default max number of attributes per span
	DefaultMaxAttributesPerSpan = 32

	// DefaultMaxLinksPerSpan is default max number of links per span
	DefaultMaxLinksPerSpan = 32
)

4baeb63 Add option to configure limits for attributes, annotations, message events and links. (#1015)

@chuerxiao Does #1015 resolve your issue?

Consider resolved, feel free to reopen if you have follow-up questions.

We made the dgraph version using the latest opencensus version. The dgraph was run for about two weeks and did not find that the dgraph had a memory leak associated with the trace function.


Troubles using with recent versions

Hi,  thanks for the work, but currently the library's monkey patch does not work out of the box, because JAX now unified all arrays to be of one type (source link). Hence, this issue is addressed to fix this

To reproduce:

Install latest jax jaxlib versions
Install lovely-jax
Try executing lovely-jax.monkey_patch()

Expected behaviour:
Arrays are patched and working well
Actual behaviour:
AttributeError: module 'jax._src.array' has no attribute 'DeviceArray'

Related PR: https://github.com/xl0/lovely-jax/pull/5


UA.3.4 Leave the Game:  As a user, I want to be able to quit the game and inform the other user, such that everyone is aware of what is happening.

Acceptance Criteria

[x] A user should be able to leave the game.
[x] The game communicates this to all other players.
[x] The game should be canceled after a single player left the game.

Task List

[x] sopra-fs22-group-11/SoPra22-group11-TheGame-Client#44
[ ] sopra-fs22-group-11/SoPra22-group11-TheGame-Client#45
[x] #123

This task has been finished on the day with posted SHA comment, in the interest of correctly closing the issue (and us having to first learn how to), it has been closed a while after the finishing of the task.


add color for district pages

@kisram please feel free to merge; I assigend you as reviewer as you currently working on districts. but i think this PR shouldn't do much harm

I merged main into the branch before making the changes to district, so should be up to date

Should be fine since I was only working on the .js, not the templates


General OAuth2 support?

This looks great! I'm looking for authenticating with other OAuth2 services and was wondering if you plan to support that in the future.
Thanks,
Alex

Alex, Azure AD has a feature called "B2C" which lets you bring your own identity from things like Google, Facebook, LinkedIn and MSA. I'm close to add support to that into AuthBot which would open many scenarios at once without having to custom code each one. Somebody else is also adding Visual Studio Online support to it. So we're slowly getting there

Thanks!


Clean up VSCode extension activation events

Fixes #1509. VSCode has gotten pretty pushy about removing these--showing warnings even when package.json isn't open--so I'm just going to deal with it now. VSCode 1.74.0 has been out for about two months now and by the time we release this version of the extension, it'll have been closer to three months.

VSCode Extension Installation Instructions

Download the extension at https://azuresdkreleasepreview.blob.core.windows.net/azd/vscode/pr/1510/azure-dev-0.4.0-alpha.1.vsix
Extract the extension from the compressed file
In vscode
a. Open "Extensions" (Ctrl+Shift+X)
b. Click the ...\ menu at top of Extensions sidebar
c. Click "Install from VSIX"
d. Select location of downloaded file


Allow setting remoteServiceName with TracingKafkaClientSupplier

I'm trying to set the remoteServiceName when creating an instance of TracingKafkaClientSupplier.  At the moment, there is no way to do this.
Feature:
Add an override to KafkaStreamsTracing.kafkaClientSupplier that takes KafkaTracing as an argument.
Rational
Enables people to use a customised KakfaTracing obect when creating a KafkaClientSupplier.
This will likely be of use in one or both of the following Spring Cloud Sleuth issues:

https://github.com/spring-cloud/spring-cloud-sleuth/issues/1480
https://github.com/spring-cloud/spring-cloud-sleuth/issues/1481

I think line 55  is the better option. the field saved should be
KafkaTracing not Tracing. so add a second static factory method iotw.

@adriancole sounds good

wanna raise the PR?


Cannot declare Props type for components with children

It's not possible to declare Props type of Components that use children.
Just two little examples with trying to declare Props typing:
type Props = {
  some: string
}
//The same like this:
//class Test extends Component<void, Props, void> {
class Test extends Component {
  props: Props;
  render(): React$Element {
    return
{this.props.some}{this.props.children}

  }
}
class Another extends Component {
  render(): React$Element {
    return <Test some="string">
asffas
</Test>
  }
}

You will receive:
 13:     return
{this.props.some}{this.props.children}

                                                                   ^^^^^^^^ property `children`. Property not found in
 13:     return
{this.props.some}{this.props.children}

                                                        ^^^^^^^^^^ object type

But if you will try to define children in Props type:
type Props = {
  some: string,
  children: React$Element
}
class Test extends Component {
  props: Props;
  render(): React$Element {
    return
{this.props.some}{this.props.children}

  }
}
class Another extends Component {
  render() {
    return <Test some="string">
asffas
</Test>
  }
}

You will receive:
 10:   props: Props;
              ^^^^^ property `children`. Property not found in
 18:     return <Test some="string">
asffas
</Test>
                ^^^^^^^^^^^^^^^^^^^^ props of React element `Test`

I found one solution, but it doesn't looks good:
type Props = {
  some: string,
  children?: React$Element
}

But in code I need to do checks that children is defined, so checks for this code will fail:
render(): React$Element {
  return this.props.children
}

As I understand this is because React assign original props with children (third parameter of React.createElement), so PropsType of Component != PropsType of React.createElement.
So this situation can be fixed if flow will split PropsType of Component to two parts:

Props of React.createElement
Children of React.createElement

Duplicate
#1355 #892


Banner: link to candidate-list and election posts

Following through from #1863

Preview:

Homepage for the banner: https://deploy-preview-1864--opentelemetry.netlify.app
Posts with their paths and titles normalized to be consistent 2021 posts (we don't need the year in the file name since each post is in a folder for a given year):

https://deploy-preview-1864--opentelemetry.netlify.app/ ....

/cc @jpkrohling

Screenshot

@jpkrohling - can you confirm that you saw the post path changes (see the opening comment for details).
Oh, and I need to fix one of the aliases, which is why I put this in draft mode.

Alias fixed. Ready for final review.

Do you want to wait for @jpkrohling's feedback or merge this now @cartermp? I'll let you merge when you think it's time to do so.

then let's merge :-)


Release 2.11

Enhancements and new features:

* New export plugin: standard and configurable Restfull exporter (issue #1129)
* Add a JSON export module (issue #1130)
* [WIP] Refactoring of the WebUI

Bugs corrected:

* Installing GPU plugin crashes entire Glances (issue #1102)
* Potential memory leak in Windows WebUI (issue #1056)
* glances_network `OSError: [Errno 19] No such device` (issue #1106)
* GPU plugin. <class 'TypeError'>: ... not JSON serializable"> (issue #1112)
* PermissionError on macOS (issue #1120)
* Cant move up or down in glances --browser (issue #1113)
* Unable to give aliases to or hide network interfaces and disks (issue #1126)
* `UnicodeDecodeError` on mountpoints with non-breaking spaces (issue #1128)

Installation:

* Create a Snap of Glances (issue #1101)

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Identify App Attestation Performance/Speed bottlenecks

identify bottlenecks: create private keys, validating app attestation, issuing/accepting credential

Future work:

pre-request app attestation credential when app startup

I've texted dozens of times triggering attestation from Traction via a test script causing both the prod and a dev version to fetch an attestation credential. It usually completes in ~10 seconds.

Some test data has been collected and formatted now that logging has been updated. Sheet located here: https://docs.google.com/spreadsheets/d/1jIHR3WvOiJFfxKjcJ8rWiS_sFeniOFzGIOBaVmGM4xQ/edit?usp=sharing


Mod flexiblelogin (FlexibleLogin) requires [griefprevention@[4.3.0,)

The 1.10.2 version of GriefPrevention is

4.3.0 is only for 1.12.2

The dependency is optional


Finish GUI/HTTP

See PR #23.
Get the NodeJS ready for remote/persistent hosting.

Wow. That was fast. Basically just imported the repo back into Glitch, and updated the env variables there.
Live at https://tom-title-suggestion-monitor.glitch.me/


Without using the config is there an event on the player I can use to change the hls source as soon as the player is ready?

I understand I can use the source tag and the hls config callbacks however dude to some rendering between php and javascript I need to run a javascript after I have instantiated the player with:
var myPlayer = fluidPlayer('player', myConfig));

Past that moment is there a way to run hls.loadSource("my source to load"); as soon as the player is ready?
I couldn't find an event that lets me get an instance of the hls, I understand I can create a new instance by doing:
var hls = new myPlayer.hlsInstance();

And from there call the loadSource but for that to work I need and event that I can use that would give me a moment after the player is ready to receive a new source.
I thou that using the video onloadstart would be a good location but apparently it can still fail at that point, so maybe some one here would know if the player instance it self have an event I can use that would be more appropriate for this.

Hi @tekinomikata, if you want the internal instance of hls.js you can get it through the onBeforeInitHls callback, here is the docs. Does this helps with the issue?

Hi @tekinomikata, if you want the internal instance of hls.js you can get it through the onBeforeInitHls callback, here is the docs. Does this helps with the issue?

Thanks for the reply, can that only be used within the modules arg? can I not use it from say:
var myPlayer = fluidPlayer('player', config);
myPlayer.onBeforeInitHls...

Due to how I am handing the config to the player I am unable to add the event on it, so I had to resort to a separated approach.

Closing the ticket due to a lack of feedback over an extended period. Please feel free to reopen if you have further input or require additional assistance. Thank you.


Json array and xml.toJson()

Well, I'm new to Ballerina but this sounds like a bug to me.
Description:
In case of an array the json generated by xml.toJson() is improperly recognized as map intead of json
Steps to reproduce:
The code below works as expected
public function main() {
    json person = {"person":{"name":"David"}};
    json persons = [person];
    persons[1] = person;

    io:println("persons: ", persons);
}

But if you replace the json literal assigned to person with the json generated by the xml conversion below you get the error incompatible types: expected 'json', found 'map'.
public function main() {
    xml xmlPerson = xml `<person><name>David</name></person>`;
    json person = xmlPerson.toJSON({});
    json persons = [person];       // <-- error
    persons[1] = person;           // <-- error

    io:println("persons: ", persons);
}

Not even casting person to <json>  makes it work. 😞
Affected Versions:
Ballerina 0.983.0
OS, DB, other environment details and versions:
Windows 10

This was fixed by PR #12020 and will be available in the next release.

Thanks!


Eating up the memory

Hello! I used your library with my Pico to my alarm project. I used the LCD to type in the PIN needed to arm and disarm the alarm. My code utilises a while loop to await input from the keypad and then print a typed number on the LCD. I noticed that with every character printed a lot of memory of my Pico is being consumed. Apart from printstr() function I also noticed that lcd.clear() consumes a lot of memory too. When it's executed in a loop it takes all the memory from my Pico and the microcontroller freezes. I got rid of lcd.clear() function in my loop, but eveytime I printed a character on the LCD it still took memory. What I did was adding GarbageCollector library and adding a line with gc.collect() at the end of every function in pico_i2c_lcd.py. This really helped! Now any function from your library barely takes any memory off my microcontroller. I think you should add those lines to your code.
`import utime
from lcd_api import LcdApi
from machine import I2C
import gc
MASK_RS = 0x01
MASK_RW = 0x02
MASK_E  = 0x04
SHIFT_BACKLIGHT = 3
SHIFT_DATA      = 4
class I2cLcd(LcdApi):
def __init__(self, i2c, i2c_addr, num_lines, num_columns):
    self.i2c = i2c
    self.i2c_addr = i2c_addr
    self.i2c.writeto(self.i2c_addr, bytes([0]))
    utime.sleep_ms(20)   # Allow LCD time to powerup
    self.hal_write_init_nibble(self.LCD_FUNCTION_RESET)
    utime.sleep_ms(5)    # Need to delay at least 4.1 msec
    self.hal_write_init_nibble(self.LCD_FUNCTION_RESET)
    utime.sleep_ms(1)
    self.hal_write_init_nibble(self.LCD_FUNCTION_RESET)
    utime.sleep_ms(1)
    self.hal_write_init_nibble(self.LCD_FUNCTION)
    utime.sleep_ms(1)
    LcdApi.__init__(self, num_lines, num_columns)
    cmd = self.LCD_FUNCTION
    if num_lines > 1:
        cmd |= self.LCD_FUNCTION_2LINES
    self.hal_write_command(cmd)
    gc.collect()

def hal_write_init_nibble(self, nibble):
    byte = ((nibble >> 4) & 0x0f) << SHIFT_DATA
    self.i2c.writeto(self.i2c_addr, bytes([byte | MASK_E]))
    self.i2c.writeto(self.i2c_addr, bytes([byte]))
    gc.collect()

def hal_backlight_on(self):
    self.i2c.writeto(self.i2c_addr, bytes([1 << SHIFT_BACKLIGHT]))
    gc.collect()

def hal_backlight_off(self):
    self.i2c.writeto(self.i2c_addr, bytes([0]))
    gc.collect()

def hal_write_command(self, cmd):
    byte = ((self.backlight << SHIFT_BACKLIGHT) |
            (((cmd >> 4) & 0x0f) << SHIFT_DATA))
    self.i2c.writeto(self.i2c_addr, bytes([byte | MASK_E]))
    self.i2c.writeto(self.i2c_addr, bytes([byte]))
    byte = ((self.backlight << SHIFT_BACKLIGHT) |
            ((cmd & 0x0f) << SHIFT_DATA))
    self.i2c.writeto(self.i2c_addr, bytes([byte | MASK_E]))
    self.i2c.writeto(self.i2c_addr, bytes([byte]))
    if cmd <= 3:
        utime.sleep_ms(5)
    gc.collect()

def hal_write_data(self, data):
    byte = (MASK_RS |
            (self.backlight << SHIFT_BACKLIGHT) |
            (((data >> 4) & 0x0f) << SHIFT_DATA))
    self.i2c.writeto(self.i2c_addr, bytes([byte | MASK_E]))
    self.i2c.writeto(self.i2c_addr, bytes([byte]))
    byte = (MASK_RS |
            (self.backlight << SHIFT_BACKLIGHT) |
            ((data & 0x0f) << SHIFT_DATA))
    self.i2c.writeto(self.i2c_addr, bytes([byte | MASK_E]))
    self.i2c.writeto(self.i2c_addr, bytes([byte]))
    gc.collect()

`

Please submit this as a pull request so I can merge and keep track of code changes

Very good work by the way!

Very good work by the way!

 I'm sorry but I'm new to GitHub and don't know how to create that Pull request. Could you help?


activating terminal profile keeps closing combo boxes

Issue Type: Bug
I know it is a little weird, but when I define a terminal profile using:
"terminal.integrated.profiles.windows": {
        "cmder": {
            "path": "C:/WINDOWS/System32/cmd.exe",
            "args": ["/K", "C:/tools/cmdermini/vendor/init.bat"]
        }
    },`

and later on use this profile as default by:
"terminal.integrated.defaultProfile.windows": "cmder",

Then, whenever I open a combo box (lithe the bombo box at the Output window, allowing me to choose which output to check, the combo box gets closed even if I am still navigating it.
VS Code version: Code 1.59.0 (379476f0e13988d90fab105c5c19e7abc8b1dea8, 2021-08-04T23:13:12.822Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6600 CPU @ 3.30GHz (4 x 3312)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
7.94GB (2.27GB free)

Process Argv
--crash-reporter-id f55e9b6a-a451-44ae-9a30-50322c5bd48b

Screen Reader
no

VM
0%

Extensions: none

please include a gif of this happening with screencast mode enabled

also what does that script you are passing in as an argument do?

please include a gif of this happening with screencast mode enabled

Here it follows:

also what does that script you are passing in as an argument do?

I haven't checked, I use cmder as my terminal tool and I have found these instructions on VSCode documentation here.
Here follows the file: init.txt

strange. @Tyriar, thoughts?

Thanks for the gif and info. I still can't reproduce it.

The cause is all the panel actions are getting rebuilt when the terminal setting changes

@sbatten is this by design that changing an action item on one panel would rebuild all actions on all other panels?

if a context that affects the actions in the visible panel changes, then yes the whole thing is rebuilt. could you specify what context changes? "changing an action item on one panel" << which panel in this case?

We refresh the terminal config registrations so the settings editor auto complete gets updated:
https://github.com/Microsoft/vscode/blob/44129daac8b9f17ffdf741206b7f603ea082ed16/src/vs/platform/terminal/common/terminalPlatformConfiguration.ts#L393-L401
Plus re-create the commands:
https://github.com/Microsoft/vscode/blob/08069da0075f86f8feafcaa249021080bcfc56a2/src/vs/workbench/contrib/terminal/browser/terminalActions.ts#L2015-L2015
Not aware of context key value changes

@sbatten let us know if you need anything from us

After investigation, it seems this is caused by the configuration updates here which eventually trigger a whole slew of contex tkey changes https://github.com/microsoft/vscode/blob/9f7309348f4139404cc1e339216a017bc49884f2/src/vs/workbench/services/configuration/browser/configurationService.ts#L668

@sandy081 this comes back to a more performant option for updating config schemas https://github.com/microsoft/vscode/issues/120940

I see, will try to add this in this milestone.


eatonBlue[500] !== Eaton's Blue

Describe the bug
eatonBlue500 === #005EAB
What is the expected behavior?
Eaton's Blue, according to Eaton.com, is #005EB8
Anything else to add?
Discovered during A11y research

This sounds like it'll be grouped into the a11y refactor discussions we have scheduled.

no it is unrelated. EatonBlue is a branding color.

Whenever you say it's a branding color, would this mean our branding palette would have be updated?

Correct. It belongs to the colors-branding package. Our accessibility discussion only deals with the colors package.

Unless we ended up making "Eaton's blue" to be our new blue500... Can do, although not my favorite.

Will be fixed with the new colors package / theme


Are v4 fees thoroughly tested? If no, do it

Is your feature request related to a problem? Please describe.
V4 fees are considerably more complex than v3.

so that marketplaces etc have more opportunities to earn, and more flexibility in setting fees.
Plus there can now be third party providers,

This is important to get right so that the community can monetize - we need to make sure that we have tested in thoroughly. It can and should be tested in contracts; but since these also affect data science flows, we should also have thorough testing in ocean.py.
I'm pretty sure that the fees are not well tested yet, especially not in ocean.py. Why: there was churn in fees in the last few weeks, yet I saw no signs of any updates to ocean.py to reflect this. And from what I gather, most of the tests so far have mostly zero fees.
Describe the solution you'd like

Test all fees, in happy path, with nonzero values. Including for 3rd party providers.
Test for extremes of fees
Test for unhappy paths. Truly try to break it! Eg is there some combination of fees where someone can make an (unfair) killing? Eg are there ways that a malicious marketplace can essentially steal from people?

I believe I must test:

[ ] providerFee
[ ]  consumeMarketFee
[ ]  publishingMarketFee
[ ]  swapOceanFee
[ ]  swapNonOceanFee
[ ]  OPC Fee (Ocean Protocol Community)

If I'm missing anything please let me know.

There's more than the six fees given.
A full list is in V4 Fees - Base doc, table in section 2.
There are about 15 rows. You should test each row at least once for nonzero values. Including in end-to-end flows for steps of publish, swap (fixed-rate), swap (pool), and consume.

In today's Daily stand-up @trentmc shared a blog post draft that @jamiehewitt15 is writing which describes the fees in more detail: https://docs.google.com/document/d/1TEjEn5hhzwC5PaRlyY0ISZjyXDbZxxkYBNQwgOnBSco/edit

Note to self: consider also adding a test for the allowed_swapper argument used when creating fixed-rate exchanges. Currently all unit tests set this to ZERO_ADDRESS

The v4 fees are documented at https://github.com/oceanprotocol/docs/blob/main/content/concepts/fees.md


BHBC-1115_2

adjusted schema biohub_dapi_v1 to be owned by role biohub_api

Overview
Links to jira tickets

BHBC-1115

This PR contains the following changes

adjusted schema biohub_dapi_v1 to be owned by role biohub_api

This PR contains the following types of changes

[ ] New feature (change which adds functionality)
[x] Enhancement (improvements to existing functionality)
[ ] Bug fix (change which fixes an issue)
[ ] Misc cleanup / Refactoring / Documentation
[ ] Version change

Checklist
A list of items that are good to consider when making any changes.
Note: this list is not exhaustive, and not all items are always applicable.
General

[x] I have performed a self-review of my own code

Code

[x] New files/classes/functions have appropriately descriptive names and comment blocks to describe their use/behaviour
[x] I have avoided duplicating code when possible, moving re-usable pieces into functions
[x] I have avoided hard-coding values where possible and moved any re-usable constants to a constants file
[x] My code is as flat as possible (avoids deeply nested if/else blocks, promise chains, etc)
[x] My code changes account for null/undefined values and handle errors appropriately
[x] My code uses types/interfaces to help describe values/parameters/etc, help ensure type safety, and improve readability

Style

[x] My code follows the established style conventions
[x] My code uses native material-ui components/icons/conventions when possible

Documentation

[x] I have commented my code sufficiently, such that an unfamiliar developer could understand my code
[x] I have added/updated README's and related documentation, as needed

Tests

[ ] I have added/updated unit tests for any code I've added/updated
[ ] I have added/updated the Postman requests/tests to account for any API endpoints I've added/updated

Linting/Formatting

[ ] I have run the linter and fixed any issues, as needed
See the lint commands in package.json
[ ] I have run the formatter and fixed any issues, as needed
See the format commands in package.json

SonarCloud

[ ] I have addressed all SonarCloud Bugs, Vulnerabilities, Security Hotspots, and Code Smells

How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Screenshots
Please add any relevant UI screenshots, if applicable.

adjusted api schema to be used by api user. schema security still seems to work!

Closing this PR as I went the wrong direction with it, fixed it in a new pr 1115_3


Fix the typo

- What I did
Change ErrSwarmCertificatesExipred
####to ErrSwarmCertificatesExpired
- How I did it
- How to verify it
- Description for the changelog

- A picture of a cute animal (not mandatory but encouraged)
Signed-off-by: yupeng<EMAIL_ADDRESS>

LGTM


Power measurement in Sonoff SPM

Hi,
To read out Sonoff SPM power measurement, one has to set the device in DIY mode.
When having done this, the parameters do not show up in the SonoffLAN.å In fact, very little is retrieved.
Can this be added ?
Jan

#658


Beta challenge sequence problem.

Challenge title-case-a-sentence has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
In the "basic algorithm scripting"sequence of the beta course, there is in between "Tile Case a Sentence" and "Falsy Bouncer", the first page of "object oriented programming". Seems totally out of place, and Ctrl-enter will not take you to "Falsy Bouncer" but to "Object Oriented Programming: Create a Basic JavaScript Object"

Looking in the code base, Slice and Splice challenge should be here.  It is marked true for beta, and I am looking a little into it.

Upon further research, it seems that this affects beta challenges.  Both current beta challenges do not appear properly, which may be related to the isBeta boolean on the object.

Thanks for reporting and looking into this issue! This was recently doubly fixed (https://github.com/freeCodeCamp/freeCodeCamp/pull/12989), so I'm closing this issue.
Happy coding!


Update to version 0.5.1 to fix BOM table error

due to the changes in the lifecycle and chainging BOM table config, a release with version 0.5.1 would be great to prevent errors such as:
"ERROR: failed to build: bom table isn't supported in this buildpack api version. The BOM should be written to .sbom., launch.sbom., or build.sbom."

https://github.com/vmware-tanzu/community-edition/pull/3228


Hi @Extarys, yeah that might not be a bad idea. I'll close the issue since the main list is located in https://github.com/sqids/sqids-blocklist, but if you'd like to submit a PR there, feel free to do that.
Looks like we already have "sucker", but if we shorten it to what you suggested, it will cover both of these words: https://github.com/sqids/sqids-blocklist/blob/next/data/en.json#L46


v1.7.1 needs to depend json.net v8

On https://github.com/elastic/elasticsearch-net/blob/1.7.1/paket.lock  I can see that you depend on json.net v7 range. I happen to use v8. Is it possible to do a 1.7.2 release with upgraded dependencies?

duplicate of #1781


build(builder): pin base image version to debian:buster

What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
Currently, the publishing of the builder image is broken (see the failing test on the master branch).
So, this PR introduces a simple workaround to make the builder image work again.
The root issue is due to debian:stable which recently moved forward and removed clang7. So we just pin the last working version, which is debian:buster. We already did the same thing on Falco, see https://github.com/falcosecurity/falco/pull/1719.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Upgrading to a newer clang version is out-of-scope for this PR. The intent is just to make the tool work again shortly.
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: leogr
To complete the pull request process, please assign leodido after the PR has been reviewed.
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

Sorry, I did not realize this is a dup of #109 :/
So,
/close

@leogr: Closed this PR.

In response to this:

Sorry, I did not realize this is a dup of #109 :/
So,
/close

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


SimpleIndexer crashes permanently after docs with invalid embeddings are indexed

In an attempt to address #28 and as discussed in the same issue, we have re-introduced the issue of SimpleIndexer crashing permanently after docs with invalid embeddings are indexed.

As discussed in Hub Alignment, this is not something we will tackle with something from the Indexer itself. It's up to the upstream to filter out invalid docs at the earliest stage.

I think filtering from upstream is a good practice but does not really fix this issue, as there is really no guarantee that (all) users will not index docs with invalid embeddings. If it's possible to add docs with invalid embeddings to the index, that means it is still an issue. I propose we keep this issue open to keep track of things instead of dismissing it as something we have already fixed.

Let's move this discussion to slack

We decide to not check this in the SimpleIndexer


How do you run this locally inside a NextJs/React app ? keep getting usestate error in development (npm link only, not when published)

Current Behavior

I keep getting this error in development only (when using yarn link), but in production (when published) everything is ok
Unhandled Runtime Error
TypeError: Cannot read properties of null (reading 'useState')

Expected behavior
it should work no problems like it does in production

Step to reproduce

create a blank react app
create a blank tsdx app
create a functional component in tsdx and use a hook example useState
run yarn build in tsdx folder
run yarn link in tsdx folder
on your react app >> run yarn link "The Name of your tsdx library which you link"
on your react app >> import a component from tsdx
on your react app >> run yarn start
blank page? check console log

Suggested solution(s)

run this in tsdx folder npm link ../${YOUR_NEXTJS_OR_REACT_FOLDER}/node_modules/react/
base on https://github.com/jaredpalmer/tsdx/issues/950#issuecomment-766730420
maybe we can add this in How to or update the app when using hooks

Additional context
-its working when i publish to npm then use that import

problem is when i try to npm link in development or my local using next/cra i get this error

Your environment

  System:
    OS: Linux 5.17 Arch Linux
    CPU: (12) x64 Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
    Memory: 3.56 GB / 15.47 GB
    Container: Yes
    Shell: 5.8.1 - /usr/bin/zsh
  Binaries:
    Node: 14.17.0 - ~/.nvm/versions/node/v14.17.0/bin/node
    Yarn: 1.22.18 - ~/.nvm/versions/node/v14.17.0/bin/yarn
    npm: 6.14.13 - ~/.nvm/versions/node/v14.17.0/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Firefox: 99.0.1

-->

@agilgur5
added steps to reproduce

I just stumbled across this issue while googling same problem for other library. No idea why this is happening, but if you include your lib as file dependency in package.json it works. (And maybe you'll need to remove react from dev deps of your library)
  "dependencies": {
    "react-local-toast": "file:../../react-local-toast"
  },

My guess is:
Since you have react in dev deps of your library (probably), your library uses their installation of react, instead of one from parent project. For some reason Next shows only Cannot read properties of null (reading 'useState') but if you check console, there will be probably error saying that you did something wrong with hooks, and maybe you have two different react running.
I couldn't get it working with link unfortunately. Even if I remove react from node_modules of lib, I get different error. Switching to file dependency solved this problem

Also use npm link with url to react used in other library
The one thing that helped me:
[https://stackoverflow.com/questions/56663785/invalid-hook-call-hooks-can-only-be-called-inside-of-the-body-of-a-function-com](stackoverflow url)

I was able to solve this by hard coding the path to react and react dom in webpack via next.config.js
  const nextConfig = {
    webpack: (config, { dev }) => {
      config.resolve.alias = {
        ...config.resolve.alias,
        ...(dev && {
          react: `${config.context}/node_modules/react`,
          "react-dom": `${config.context}/node_modules/react-dom`,
        }),
    };

    return config;
  }
};

THE DEFINITIVE SOLUTION TO THIS PROBLEM IS THIS -> https://iws.io/2022/invalid-hook-multiple-react-instances


dfrft(x_data, alpha).abs()，What does that mean?

Question：
Hi, Dear Author.
After doing some experimentation with your code, it feels very interesting. When I try to write the following code:  dfrft(x_data, alpha).abs() . I wonder what that means? Is this similar to the amplitude in FFT?
Since I don't know much about the signal processing field, I kindly ask you to tell me why this happens. Looking forward to your answer very much！
Your fans.

First, assuming x_data is a torch.Tensor and alpha is a float, the dfrft(x_data, alpha) returns the discrete fractional Fourier transform (DFRFT) of the vectors along the last dimension of the tensor since the function has default dim=-1. The result is also torch.Tensor and has the same dimensionality as x_data.
Second, similar to DFT (FFT), the DFRFT generally returns complex valued results. Taking .abs() of the resulting DFRFT results in absolute magnitudes (or amplitudes in your words). Since most activation functions do not accept ComplexDouble, especially in machine learning applications, such as training the optimal transform order, it needs some real conversion. Taking the absolute value, real part, imaginary part, or applying operations to real and imaginary parts jointly can be some other approaches. In signal processing, taking the magnitude is usually more meaningful than just the real part, but each may provide better results.

Thank you very much for your detailed answer!


[WIP] Add cloudfront

THIS IS FOR REVIEW ONLY - PLEASE DO NOT MERGE YET
This introduces a basic and not-yet-ready-for-prime-time stack for
configuring the API in CloudFront. This is not ready for prime time
because CloudFront talks to Beanstalk over HTTP. In order to have have
CloudFront talk to Beanstalk over SSL we need to serve Beanstalk over a
domain name that we can generate an SSL certificate for. We can do this
without managing DNS in Route53 but it means the only way we're wiring
the CloudFront configuration up to a Beanstalk instance is through DNS
that is managed elsewhere which seems non-obvious.
Other things of note:

The S3 template has been renamed to be more generic.
This introduces a new output to the API template.
The domain names follow the convention covered in the Google Doc shared
within the team.
All logs for a stage are stored in the same bucket with different
prefixes.
The IAM certificate is generated separately and must be provided.
The root domain is configurable to allow the different accounts to be
on different root domains as discussed.

Closing in favour of getting the Route53 changes merged separately first.


add simple client tests

Getting the initial rev of the test app into our repo, this isn't yet connected to our CCI suite in any capacity, but I'd like to treat that as a separate review, and get this merged effectively in isolation.
Description of changes
Taken From README
Using this test app
This test app has capabilities to deploy a backend amplify project, tear down said project, and execute a ui test suite against the running app using the full backend.
To facilitate easier dev/test cycles, the test there are 4 test lifecycles defined with custom targets to make it easier to develop.
npm run test will execute all of these lifecycles.
npm run test:setup will strictly setup the amplify app in your DEFAULT aws profile.
npm run test:teardown will execute an amplify delete on the project.
npm run test:execute will start the webapp, and run the cypress suite against it.
npm run test:watch will start the app, and open a cypress watch against it.
In addition to these targets, npm start can still be used to run the app locally (recommended after npm run test:setup to develop new test pages/cases), and npx cypress open can be used to interactively run/re-run the cypress suite, this is probably preferable to using just npm run test:watch but I don't have a strong opinion on that yet.
Test Structure
Both the amplify app setup, and basic CRUD+List+Observe functionality rely on test harnesses to reduce the per-test load of creating a UI that uses our API/DataStore clients, and managing basic lifecycle concerns like app setup, teardown, invoking cypress, etc.
Cypress suites are still written by hand in the cypress directory, though we could build helpers given the consistent structure of the UI due to these harnesses.
Backend setup code is available at api.test.ts, and top-level app pages can be found in the pages directory.
CLI Interactions
This project uses a stripped down version of the amplify-e2e-core shims for shelling out to Amplify. This is expected to be shortly refactored back to a shared lib, but the reason we don't use that directly is due to the large dep-tree it invokes, including the actual CLI source code, which causes issues with jest. This is also potentially mitigable, but while I was under the hood, I simplified the API a bit as well, which I'm happy with. The refactored bits list in the __tests__/utils directory, in addition to the test harness package, which is expected to be re-used across apps for consistency.
Issue #, if available
N/A
Description of how you validated changes
Tests running locally on a windows + mac laptop.
Checklist

[x] PR description included
[x] yarn test passes
[x] Tests are changed or added
[x] Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

LGTM! One suggestion I have is to rename the app or directory structure to reflect that this is a "React" App.

That's a good callout, it's a react app, not necessarily just a JS app.


After installing latest WSL, get Wsl/E_ACCESSDENIED when trying to start/use WSL

Windows Version
Microsoft Windows 10 Enterprise 19044.2728
WSL Version
Store version - tying to run wsl.exe gives error
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
same error using wsl.exe
Distro Version
Ubuntu 20.04.5 LTS
Other Software
N/A
Repro Steps
Enable Windows Subsystem for Linux feature and restart
Use admin command prompt...
wsl --set-default-version 2
wsl --install -d Ubuntu
All good so far
wsl --update (or install latest from microsoft store)
After install completes, any further interactions give error...
Error code: Wsl/E_ACCESSDENIED
or
Invalid value for registry
Error code: Wsl/0x80040153
If command actioned from admin console.
Similarly selecting WSL from start menu gives ACCESSDENIED error
Expected Behavior
WSL commands to be executed correctly
Actual Behavior

Diagnostic Logs
WslLogs-2023-03-23_10-04-05.zip

Thank you for reporting this @AnthonyHayes72. Can you share the output of wsl.exe --version ?

Thank you for reporting this @AnthonyHayes72. Can you share the output of wsl.exe --version ?

I cannot run wsl --exe when in this state, I get the same errors in the report for any wsl command.

Can you also share a screen shot of HKEY_LOCAL_MACHINE\Software\Classes\Interface\\46f3c96d-ffa3-42f0-b052-52f5e7ecbb08} ? I wonder if that key is in a bad state

Can you also share a screen shot of HKEY_LOCAL_MACHINE\Software\Classes\Interface\\46f3c96d-ffa3-42f0-b052-52f5e7ecbb08} ? I wonder if that key is in a bad state

Thanks for looking into this - here's the reg key...

Interesting. Can you capture logs for wsl.exe --version ? I wonder if it would be easier to root cause the error from there

Can you also share a screen shot of HKEY_LOCAL_MACHINE\Software\Classes\Interface\\46f3c96d-ffa3-42f0-b052-52f5e7ecbb08} ? I wonder if that key is in a bad state

Thanks for looking into this - here's the reg key...

Interesting. Can you capture logs for wsl.exe --version ? I wonder if it would be easier to root cause the error from there

Image shows workflow - wsl working until I do wsl --update
After update wsl --version produces error.
Log files attached for wsl -- version execution
Thank you,

WslLogs-2023-03-24_16-49-26.zip

Thank @AnthonyHayes72. Looking at the logs it's pretty clear that there's one registry key with an unexpected value that's confusing WSL.
Given that wsl --version is failing as well, I think it's probably HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion
Can you share a screenshot of that key ?

Here's the reg key - again thanks for your help...

I had the same issue. This is what helped me:

Remove WSL from windows store.
Install WSL2 Linux kernel update package for x64 machines from Step 4 in https://learn.microsoft.com/en-us/windows/wsl/install-manual

Fixed with https://github.com/microsoft/WSL/releases/tag/1.1.7.

seems like nothing has changed
PS C:\tools> wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22000.1696

PS C:\tools> wsl --list
Invalid value for registry
Error code: Wsl/0x80040153

@d0zer11st: Can you share /logs ?

@d0zer11st: Can you share /logs ?

Sure.
WslLogs-2023-04-05_20-40-30.zip

I have same issue

i have the same issue, can you help me @OneBlue ? i dont really understand with these log (0x80040153)

Thank you for reporting this @nikolaikopernik. Can you share logs when you see this error ?

Sure
WslLogs-2023-10-05_09-14-14.zip

Sure WslLogs-2023-10-05_09-14-14.zip

Thank you @nikolaikopernik. Do you get the same result if you run the command in an elevated prompt ?

Yes, run it as an admin - same result

Yes, ran it as an admin - same result

Interesting. Do you see the same issue if you manually download and install the latest build of WSL ?

I am having the same issue. Tried with Administrator and also tried the latest build of WSL
2.0.4
PS C:\Users\user> wsl --update --pre-release
Checking for updates.
Updating Windows Subsystem for Linux to version: 2.0.4.
PS C:\Users\user>
PS C:\Users\user> wsl --install  -d Debian
Installing: Debian GNU/Linux
Access is denied.           0.0%                           ]
Error code: Wsl/InstallDistro/E_ACCESSDENIED

Hey @OneBlue
I have error trying to install your build

@OneBlue
After installing the latest version from MSI, I don't have the issue of updating WSL (but honestly I cannot update it as it's the latest version atm). I will wait for another version to be released and will check it then.

Hello! Can you guys help-me?


Tweak deployment groups metrics

Always include the full deployment group in all events.
For event that either fail or succeed, indicate the result via a
numeric "success" field.
Include a "machine readable" error code for failed tasks.

@rohansingh @davidxia

helios-services/src/main/java/com/spotify/helios/master/ZooKeeperMasterModel.java:812:12: WhitespaceAround: 'catch' is not followed by whitespace.

@matslina

:+1:


Need help on parsing PDF table data - use keyboard step and clipboard()

Hi Ken,
I am using TagUI to read contents from a pdf file which has data in tabular format, and facing issues in reading the contents in correct format.
Following is my script,
dclick testPdf.png
wait 30
read page.png to text_on_screen
wait 30
echo text_on_screen
On CLI I don't see the output in correct text format. Please check attached image.

I need a help on following,

How can I retrieve the text (from PDF table) in correct format ?
2 Or, how can I execute command from other OCR library such as tesseract?

Please advice.
Thanks!
Regards,
Mandar.

Hi Mandar, I have not come across this issue or other users mention this issue before with OCR.
To use other OCR library such as Tesseract, you can use the run step to run the tesseract command in your screenshot above. That should give you the best result, as you can do different settings with the tesseract command line tool.
Alternatively, in the cutting edge version, there is now a clipboard() helper function. You can tell TagUI to open the PDF file, then use keyboard step to send [ctrl]a and then [ctrl]c to copy all the PDF text. After that you can do result = clipboard(); to retrieve the text directly from clipboard. Finally you can using JavaScript string manipulation functions to extract the info you want.
Details on installing the cutting edge version here -
https://github.com/kelaberetiv/TagUI#set-up

Hi Ken,
keyboard [ctrl]a + keyboard [ctrl]c worked for me.
I need have a further query. Is it possible to store tables rows into an array and use it further ?
currently, when I echo clipboard, I see every cell is printed on new row in CLI.
Thanks!
Regards,
Mandar.

I see.. I'm afraid what you copy to clipboard will be what is available to TagUI. Depending on the text information, you may be able to use JavaScript string manipulation to split and parse it into an array for usage or storage later. But this method will be tricky and not easy to do.
You can explore if there are other solutions out there which can process OCR rows, from what I heard, native OCR and Tesseract is still not good at recognising and retrieve text in table form. Providers such as Microsoft would be able to provide computer vision and OCR services for that.

Closing the issue for now, but let me know if you have other inputs!


Calling App.message() will overwrite the previous App.message()

example:
App app = new App();
app.message("pattern1", (event, ctx) -> {
    // block1
});
app.message("pattern2", (event, ctx) -> {
    // block2
});

As shown in the above code, "pattern1" will be overwritten by "pattern2" and become invalid.

Hi @Arxing, thanks for taking the time to report this issue plus sharing a possible solution for it! Regarding the implementation, I may come up with a bit different approach but either way, the issue needs to be fixed in the next release.


Response not showing in JSON format

It has been reported that with some specific queries, the response is not formatted as a JSON. This happens when the query has $top or $skip .
The expected behaviour is for every response to be formatted in JSON.

I'm unable to reproduce this. Is this still happening @RabebOthmani ?

Closing that as we are unable to reproduce


WIP: PERF: Use ImageBufferRange in ImageKernelOperator GenerateCoefficients()

Improved the performance of ImageKernelOperator::GenerateCoefficients(),
by replacing its local ImageRegionConstIterator variable by an
Experimental::ImageBufferRange.
In general, when a function iterates over an entire image buffer,
ImageBufferRange is significantly faster than
ImageRegionConstIterator.

Merge when CI passes.

@ntustison For your information,  with this pull request I hope to present a small performance improvement to a contribution of yours. You may have a look, if you want to  😃

Merge when CI passes.

Thanks @dzenanz I believe this pull request is ready. If you would like to merge it, please do! (I prefer not to merge it myself, as I would like to share the responsibility 😃.)

Thanks @N-Dekker .  This is great.


The maximal number of devices that can connect simultaneously

I'm using the BLE plugin to connect with Polar verity sense, which works perfectly.
but I have a  problem with the number of devices that can connect simultaneously to the phone.
I want to connect more than 20 devices but when I reach to 10 devices it shows me an error.
"BtGatt.GattService      com.android.bluetooth                E  App 'app' has registered too much clientif"
so did someone face this issue and overcome it?
if it's the case for anyone please give me some information and thanks.

Hello, thank you for using this plugin.
I have never tested connecting more than 5 devices. However there is nothing in the plugin that limits the number of connected devices. Therefore I assume this limitation comes directly from Android. Maybe you'll find more information in Android forums.
Have you tested several Android devices? What Android version are you using?


SQLight package dependency upgrade.

Is your feature request related to a problem? Please describe.
Can you update the SQLight dependency to rely on the latest release? 0.13.2?
https://github.com/stephencelis/SQLite.swift/releases
I'm running into an irresolvable package graph as the latest version of the Apollo library requires version 14.
Dependencies could not be resolved because root depends on 'apollo-ios' 0.51.0..<1.0.0 and root depends on 'amplify-ios' 1.22.0..<2.0.0.
'amplify-ios' is incompatible with 'apollo-ios'.
'amplify-ios' >= 1.22.0 practically depends on 'sqlite.swift' 0.12.2 because no versions of 'amplify-ios' match the requirement 1.22.1..<2.0.0 and 'amplify-ios' 1.22.0 depends on 'sqlite.swift' 0.12.2.
'apollo-ios' >= 0.51.0 practically depends on 'sqlite.swift' 0.13.1..<0.14.0 because 'apollo-ios' 0.51.0 depends on 'sqlite.swift' 0.13.1..<0.14.0 and 'apollo-ios' 0.51.1 depends on 'sqlite.swift' 0.13.1..<0.14.0.
'apollo-ios' {0.51.0, 0.51.2..<1.0.0} practically depends on 'sqlite.swift' 0.13.1..<0.14.0 because no versions of 'apollo-ios' match the requirement 0.51.2..<1.0.0 and 'apollo-ios' 0.51.0 depends on 'sqlite.swift' 0.13.1..<0.14.0.

Describe the solution you'd like
Update SQLight dependency to the latest.
Describe alternatives you've considered
I've considered forking the repo and specifying the latest version myself.
Is the feature request related to any of the existing Amplify categories?
No response
Additional context
No response

Thanks for reporting this. We will investigate and update here if we could update the sqlite dependency. We are currently using 0.12.2 - https://github.com/aws-amplify/amplify-ios/blob/75953e68487a1752bc2e3b458d8f7879bc011610/Package.swift#L39
And the latest version is - 0.13.2.

I'm having a problem with the updated SQLite dependency.
My project depends on
pod 'Amplify', '1.19.1'
pod 'AWSAppSync', '3.6.1'
If I try to upgrade Amplify to a version higher than 1.22.2, I get the following error
[!] CocoaPods could not find compatible versions for pod "SQLite.swift":
  In snapshot (Podfile.lock):
    SQLite.swift (= 0.12.2, ~> 0.12.2)

  In Podfile:
    AWSAppSync (= 3.6.1) was resolved to 3.6.1, which depends on
      SQLite.swift (~> 0.12.2)

    AmplifyPlugins/AWSDataStorePlugin (= 1.24.0) was resolved to 1.24.0, which depends on
      SQLite.swift (= 0.13.2)

Basically,
AWSAppSync depends on SQLite.swift = 0.12.2
AmplifyPlugins depends on SQLite.swift = 0.13.2
So Pods dependency resolution fails.
Should I open a ticket for AWSAppSync to upgrade SQLite.swift? Is there another solution?
Thank you for your help!


S3Reader.read_lines_from_keys is retrying but isn't idempotent

The current implementation of S3Reader.read_lines_from_keys isn't idempotent (it uses a bunch of state) and it's doing retries -- which can hide errors and yield incorrect results (duplicated items, or even skip).

We removed the retry, so it will at least fail fast.
More discussion on reliability of S3Reader in https://github.com/scrapinghub/exporters/issues/322


Is it possible to use ML.NET to implement the AI part?

Wow, that's a great suggestion. We haven't explored that path yet. Do you have suggested methods to make it work using ML.net?

I'm not clearly,but I think it's a good idea

ML.NET doesn't handle CNNs to do object detection per-say but might be possible using a RNN or just NN .. doubtful tho..

Yes, this needs more in-depth analysis and we can comment further based on that. Stay tuned!


Entity limit of 124

GeoOps can only seem to support up to 124 entities, if i increase the entity limit to 125 the map breaks, we need this limit increased to 10,000.
Below is an example of a map with 4 workloads attached, that have between them 124 entities, the map loads fine and no problems:

After adding one more entity the form no longer loads:

Steps to Reproduce
Expected Behaviour
Relevant Logs / Console output
Your Environment

NR1 CLI version used:
Browser name and version:
Operating System and version:

Additional context

@amarbarot thanks for this issue. I/we'll look into it this week. cc: @ricegi

@amarbarot follow up: your screenshot makes me think that this was run against an older version of the app. As of version 1.5.1, we've made a number of performance improvements, including moving the loading of underlying entities to the Detail screen. I've tested it against some significantly workloads and not generated errors. Could you verify which version of the application you're running. The current New Relic One Catalog version is Version 1.5.1 released on August 27, 2020.

@tangollama ah!, The version I am running is the one we deployed to originally fix the issue in July, i think 1.1.7

So 1.5.1 fixes this issue, do you know if we have an entity limit with 1.5.1, can it load hundreds/thousands of entities without breaking?

@tangollama Ive downloaded 1.5.1 and its working a lot better, im going to attach 15 accounts worth of workloads and see how it performs, if we have no issues ill close this ticket.
I'm so happy :), the business value of these tool is very high.

Ok, GeoOps is performing fine. Im happy and closing the ticket.

Awesome. Thanks @amarbarot.


Speeding up writes

Communication goals (e.g. detailed howto vs orientation)
Sometimes people are unaware of the precautions they should take in order to get the write performance shown in our Real-Time Inserts section.
Good locations for content in docs structure
Add a new section in that page, "Why don't I see similar insert rates?"
How does this work? (devs)
Techniques for increasing insert speed:

Increase co-ordinator size (Add more CPU cores)
Increase thread-count for ingesting application.

Also note that different data types can have different impacts on performance. e.g.: Big JSON blobs vs ints.
@saicitus do you have any tips I should include?

Possibly include instructions for parallel ingest in Rails if it's short enough to show it.


Release Automation Fails to Build Helm Charts

What version of eunomia are you using?
eunomia version: v0.0.4
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (kubectl version)?
n/a
What did you do?

After creating the Eunomia v0.0.4 release the helm chart build automation that is executed by Travis CI failed to completed successfully.
What did you expect to see?
I expected the helm charts for the eunomia v0.0.4 release to be pushed to the gh-pages branch.
What did you see instead?
Here is the relevant output from the Travis CI log. The full log are be found here, https://api.travis-ci.com/v3/job/259263304/log.txt.
./scripts/build/publish-chart-repo.sh
+mkdir -p /tmp/helm/publish
+git -C /tmp/helm/publish clone -b gh-pages git@github.com:KohlsTechnology/eunomia.git .
Cloning into '.'...
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.

+version=v0.0.4
+envsubst
+helm lint deploy/helm/eunomia-operator
2019/11/21 22:44:59 found symbolic link in path: /home/travis/gopath/src/github.com/KohlsTechnology/eunomia/deploy/helm/eunomia-operator/crds resolves to /home/travis/gopath/src/github.com/KohlsTechnology/eunomia/deploy/crds
==> Linting deploy/helm/eunomia-operator
[INFO] Chart.yaml: icon is recommended

1 chart(s) linted, no failures
++basename deploy/helm/eunomia-operator
+chart_dest=/tmp/helm/publish/eunomia-operator
+mkdir -p /tmp/helm/publish/eunomia-operator
+helm package -d /tmp/helm/publish/eunomia-operator deploy/helm/eunomia-operator
2019/11/21 22:44:59 found symbolic link in path: /home/travis/gopath/src/github.com/KohlsTechnology/eunomia/deploy/helm/eunomia-operator/crds resolves to /home/travis/gopath/src/github.com/KohlsTechnology/eunomia/deploy/crds
Successfully packaged chart and saved it to: /tmp/helm/publish/eunomia-operator/eunomia-operator-v0.0.4.tgz
Error: stat /home/travis/.helm/repository/local: no such file or directory
Makefile:70: recipe for target 'publish-chart-repo' failed
make: *** [publish-chart-repo] Error 1
Script failed with status 2

travis_fold:end:dpl.3
failed to deploy

Latest errors when releasing v0.0.5 ...
./scripts/build/publish-chart-repo.sh
+mkdir -p /tmp/helm/publish
+git -C /tmp/helm/publish clone -b gh-pages git@github.com:KohlsTechnology/eunomia.git .
Cloning into '.'...
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
+version=v0.0.5
+envsubst
+helm lint deploy/helm/eunomia-operator
2019/12/05 19:19:19 found symbolic link in path: /home/travis/gopath/src/github.com/KohlsTechnology/eunomia/deploy/helm/eunomia-operator/crds resolves to /home/travis/gopath/src/github.com/KohlsTechnology/eunomia/deploy/crds
==> Linting deploy/helm/eunomia-operator
[INFO] Chart.yaml: icon is recommended
1 chart(s) linted, no failures
++basename deploy/helm/eunomia-operator
+chart_dest=/tmp/helm/publish/eunomia-operator
+mkdir -p /tmp/helm/publish/eunomia-operator
+helm package -d /tmp/helm/publish/eunomia-operator deploy/helm/eunomia-operator
2019/12/05 19:19:20 found symbolic link in path: /home/travis/gopath/src/github.com/KohlsTechnology/eunomia/deploy/helm/eunomia-operator/crds resolves to /home/travis/gopath/src/github.com/KohlsTechnology/eunomia/deploy/crds
Successfully packaged chart and saved it to: /tmp/helm/publish/eunomia-operator/eunomia-operator-v0.0.5.tgz
Error: stat /home/travis/.helm/repository/local: no such file or directory
Makefile:68: recipe for target 'publish-chart-repo' failed
make: *** [publish-chart-repo] Error 1
Script failed with status 2
failed to deploy