Missing dependency: python-configparser is required

The python-openqa_review package is installed by zypper command on my openSUSE Tumbleweed:
~> sudo zypper in python-openqa_review

~> openqa-review --help
Traceback (most recent call last):
  File "/usr/bin/openqa-review", line 6, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2991, in <module>
    @_call_aside
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2977, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3004, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 662, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 970, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 856, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'configparser' distribution was not found and is required by openqa-review

After installing python-configparser:
~> sudo zypper in python-configparser
~> openqa-review --help
Traceback (most recent call last):
  File "/usr/bin/openqa-review", line 11, in <module>
    load_entry_point('openqa-review===.-0.0.0-', 'console_scripts', 'openqa-review')()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 567, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2604, in load_entry_point
    return ep.load()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2264, in load
    return self.resolve()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2270, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python2.7/site-packages/openqa_review/openqa_review.py", line 105, in <module>
    from configparser import ConfigParser, NoSectionError, NoOptionError  # isort:skip can not make isort happy here
  File "/usr/lib/python2.7/site-packages/configparser.py", line 12, in <module>
    from backports.configparser import (
ImportError: No module named backports.configparser

The issue can be workaround by install configparser via pip
~> sudo pip install configparser
~> openqa-review --help

Also packages python-pika and python-certifi are missing from dependencies for openSUSE.

fix is in https://build.opensuse.org/request/show/457127, waiting for accept

https://build.opensuse.org/request/show/458707 was replacement, accepted into Factory

It happens to me for Leap 42.2
mansilla@copland:/var/log/apache2$ openqa-review                                                                                [58/58]
Traceback (most recent call last):
  File "/usr/bin/openqa-review", line 5, in <module>
    from pkg_resources import load_entry_point
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3084, in <module>
    @_call_aside
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3070, in _call_aside
    f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 3097, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 651, in _build_master
    ws.require(__requires__)
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 952, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 839, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'configparser' distribution was not found and is required by openqa-review
mansilla@copland:/var/log/apache2$


working example?

You can try my version, the example should work as expected. :) https://github.com/fel1xw/react-pusher-hoc

The readme has an example


bump to k9

Saw in another issue that this guide is made for K7, explaining the errors from running npm install and begs the question, why are we absorbing K7 while learning fundamentals? Perhaps there's a good reason, else as this is a guide for newcomers, it's sensible to align with K9. Please consider addressing the differences or fork for an updated doc. Continuity is benign.

hey,
thanks, please check last ~50 commits.
it is still work in progress, but 90% of prose and 99% of code is now k9.
i'm gonna close this one.

i've gotten errors on about half of the code as of yesterday

"that's why we call it a beta - it is beta than nothing" :)
1/2 sounds pretty bad, but i don't think so. there are about 30 people
looking at hackmd draft as we speak (world-writable), please feel free to
join  / pullreq / openissue (if you really found a lot, cumulative also
works)
please always include the banner.
cheers
k.
On Sun, 4 Apr 2021 at 19:28, 34r7h @.***> wrote:

i've gotten errors on about half of the code as of yesterday
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/kparc/kcc/issues/16#issuecomment-813069463, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AALVXXTKTHC7W7PG7AOW4G3THCOVTANCNFSM42KBEMDA
.

--
k.
Sent from my Imperial Star Destroyer

i reopened the issue until we get less than "50%"
thanks!

also, i just realized you could be looking at kcc.kparc.io version, which is bad news - that one is a blast from 2019
please use one on gh

yea thought it was the same content or i should have mentioned using kcc.kparc.io, thanks. i'll fux w it

sorry for the confusion - i removed the stale kcc.kparc.io from the project
front page, it now points to the working draft on hackmd (which is synched
to github on roughly daily basis)
On Sun, 4 Apr 2021 at 19:40, 34r7h @.***> wrote:

yea thought it was the same content or i should have mentioned using
kcc.kparc.io, thanks. i'll fux w it
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/kparc/kcc/issues/16#issuecomment-813071071, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AALVXXWJXNFRSX752BID7HLTHCP7VANCNFSM42KBEMDA
.

--
k.
Sent from my Imperial Star Destroyer

thanks kelas, you rock


[CLOSED] Add script to publish all draft AAIB reports.

 Issue by kalleth
Thursday 16 October 2014 at 15:47 GMT
Originally opened as https://github.com/alphagov/specialist-publisher/pull/282

Trello ticket
This script uses $stdout.flush and $stdout.sync = true liberally in
order to make sure the console output is legible and useful for whoever
in 2nd-line ends up running this script.
It takes around a second a time to run but is idempotent so can be run again and again.

kalleth included the following code: https://github.com/alphagov/specialist-publisher/pull/282/commits

 Comment by kalleth
Monday 20 October 2014 at 13:07 GMT

@Themitchell I've updated the PR to take that into account :)

 Comment by kalleth
Monday 20 October 2014 at 11:24 GMT

@Themitchell Excellent spot, made all the more embarrassing by knowing I've mentioned this to you before on another PR. Ho hum, I'll change :)


Fix a typo in README.pt-BR

Thanks for taking the time to contribute this localization pull request. However, we are not able to accept contributions to this historical reference repository at this time.


Intake driver (or some other way) to handle csv with filenames and metadata

E.g. https://github.com/miquelmassot/squidle_scivision/blob/main/Squidle example.ipynb

Duplicated of #251


[Field Group] Table 308 "No. Series"

Hi,
please add field group to Table 308 "No. Series" so DropDown can be extended with more fields from extensions.
Code to be added after Keys section:
    fieldgroups
    {
        fieldgroup(DropDown; Code, Description) { }
        fieldgroup(Brick; Code, Description) { }
    }

Thanks!

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


Exif data is getting lost when opening an image from the photo library

Bug Report
Problem
Exif data is getting lost when opening an image from the photo library on an android device.
This is in continue to #329.
Related to an issue reported by our users:
https://github.com/IsraelHikingMap/Site/issues/932
What is expected to happen?
Exif data should be kept
What does actually happen?
Exif data is getting lost
Information
I've just tested the code using the instructions #415 and I still see an issue with exif data getting lost when getting images from the photo library on android device.
The code I'm using is the following:
navigator.camera.getPicture(() => ..., { destinationType: Camera.DestinationType.DATA_URL, sourceType: Camera.PictureSourceType.PHOTOLIBRARY, saveToPhotoAlbum: false}).
Code can be seen here:
https://github.com/IsraelHikingMap/Site/blob/d81cfdfd339060aab9b512352741b5af00c8a214/IsraelHiking.Web/sources/application/directives/image-capture.directive.ts#L41
Command or Code

Environment, Platform, Device
Android, N2G47H 7.1.2, xiomi redmi 4
Version information
Can be seen here:
https://github.com/IsraelHikingMap/Site/blob/master/IsraelHiking.Web/package.json
https://github.com/IsraelHikingMap/Site/blob/master/IsraelHiking.Web/config.xml
Checklist

[x] I searched for existing GitHub issues
[ ] I updated all Cordova tooling to most recent version - I can't, latest cordova doesn't run on my windows 10 machine. the plugin is up-to-date though...
[x] I included all the necessary information above

Any updates on this? It's open for a while now...

I created a pull request with @ryaa 's working changes and missing commits from master:
https://github.com/apache/cordova-plugin-camera/pull/712
You can use the plugin in your code by running the following commands:
  cordova plugin remove cordova-plugin-camera
  cordova plugin add https://github.com/codeconsole/cordova-plugin-camera.git#ryaa

Can be verified working by running the following:
% cordova --version
10.0.0

  git clone https://github.com/codeconsole/exiftest
  cd exiftest
  cordova prepare
  cordova plugin remove cordova-plugin-camera
  cordova plugin add https://github.com/codeconsole/cordova-plugin-camera.git#ryaa
  cordova run ios

Choose a photo and notice all the exif information is there.

Actually, I opened this bug for android, didn't know there was an issue with iOS...
I also think that largest version is working fine for android, but it's worth fixing this if iOS experience this issue...

yes, you are correct. Using my test app exiftest, I verified that the latest version 5.0.1 works on android.  It does not work on ios.


fixed amda multidimensional data download, column names

Small fix for downloading multidimensional data from AMDA

Can you add a test here https://github.com/SciQLop/speasy/blob/main/tests/test_amda.py#L53 ? I feel like we could easily forget this and introduce some regressions later.

Can you add a test here https://github.com/SciQLop/speasy/blob/main/tests/test_amda.py#L53 ? I feel like we could easily forget this and introduce some regressions later.

will do


Fix X7 HIPOWER enabled state

Fix X7 GPS power enable

Does this modification meet the requirements

Thanks @CUAVcaijie, this helps avoid future confusion.


Improve wiki page.

Currently, there is nothing in our wiki page. Adding some docs and Rules and regulation to this project would be appreciable.

@rishidyno i am interested to work on this issue can you please assign it to me

Assigned to you @Smarshal21.

@rishidyno how can i create a PR to the changed wiki . Im unable to do it, could you please help me with that


why changed so much,doesn't have detailed api change list?

$response = $client->post('http://httpbin.org/post', [
'body' => [
'field_name' => 'abc',
'other_field' => '123'
]
]);
why can't post an array?
where is form_fields ?
why changed so much,but there is no detailed change log of api?
if I use guzzle put data to server,how can I get it ,$_GET,$_POST,$_REQUEST all don't work,what should I do and why?

Body can't be an array anymore. Look at the docs.

@GrahamCampbell why? It's convenient.

@argb I don't know. I didn't do it. I'm just telling you why this isn't an issue.

@GrahamCampbell Thank you haha good man!

Sending POST requests with an array as the body parameter has been removed. Using the body parameter to support both application/x-www-form-urlencoded and multipart/form-data resulted in a confusing API that did not support sending multipart/form-data requests that did not contain files, you had to specify the POST file name twice, and other issues. You should now use form_params and multipart.
This is in the upgrading guide here: https://github.com/guzzle/guzzle/blob/master/UPGRADING.md#post-requests

if I use guzzle put data to server,how can I get it ,$_GET,$_POST,$_REQUEST all don't work,what should I do and why?

I think this question is better suited for stackoverflow.

@mtdowling Thank you very much!


Upgrade to Prisma 4

This PR upgrades prisma version to 4 for upcoming meiliNG 0.9.0.

Testing is still required. therefore this PR will not be merged at the moment.

Working properly. seems not to be failing with internal infrastructure. merging.


Opportunity list view enhancements

Can you please make the following changes?

I want to be able to see at a glance what the next step is for every opportunity.

Next task is?
Look thru relationship to Activity where TaskInd =1 and Completed<>1?

I've added the relationship

OK, adjusted the anchors and logged in Build.


Use FOTA library's currentFwVersion

The Azure FOTA library has its own version string schema, so this should be used instead of the string in the dev object.
"reported": {
      "firmware": {
        "fwUpdateStatus": "current",
        "currentFwVersion": "0.0.0-dev",
        "pendingFwVersion": ""
      }
}

In the "dev" object?

Yes:
https://github.com/bifravst/bifravst/blob/9cfa7329df3049875da99b64378b43271ee78b21/docs/firmware/state.schema.json#L209-L214

This has been implemented in the documentation, web app and Azure implementation itself.
@simensrostad can you take care of removing the appV from the dev object for the Azure firmware?

This has been implemented in the documentation, web app and Azure implementation itself.
@simensrostad can you take care of removing the appV from the dev object for the Azure firmware?

Yes. Entry removed from azure_iot_hub_codec.c in the branch that adds azure support.


Upgrade TunnelBear.app to v2.5.1

Thank you for the contribution. It was merged directly as 2e6e774b797935eb029e7a0cbbfd45ffe61a82b4 to keep commit history cleaner. Your contribution is still credited to you.


Update Preview to new app

MDATP Android Deploy Page:
Update text from Microsoft Defender ATP Preview to Microsoft Defender ATP
Update all screenshots from Preview app to new app.

Will merge on Sept 21.

Hello, @mjcaparas This PR has been tagged as going to be merged by 21st of Sept. Is there any updates? Thank you.


Docusaurus 2 is not detected by netlify dev

Describe the bug
netlify dev can detect Docusaurus 1 sites, but does not detect Docusaurus 2 sites and treats them like static sites.
To Reproduce

npx @docusaurus/init@next init my-website classic
cd my-website
netlify dev

Configuration
  System:
    OS: macOS 10.15.6
    CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
    Memory: 167.68 MB / 8.00 GB
    Shell: 3.1.2 - /usr/local/bin/fish
  Binaries:
    Node: 14.9.0 - /usr/local/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 6.14.8 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  npmGlobalPackages:
    netlify-cli: 2.61.1

Expected behavior
Docusaurus 2 sites should be detected like Docusaurus 1 sites. This could be achieved either by adding 2 support to the existing detector with dynamic commands or adding a new detector for only 2 support.
CLI Output
◈ Netlify Dev ◈
◈ No app server detected and no "command" specified
◈ Running static server from "cli/site/dist"

Additional context
It seems like docusaurus-start has changed to docusaurus start.

I've just made a PR for this issue: https://github.com/netlify/cli/pull/1228


updating homepage URL in TOC

Hi @DuncanmaMSFT, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;


Removing utils-auth.R AQCU-976

deleting any sig file parts where examples of fetching via authenticated URL
deleting the URL methods from sig files
removing the getJSON function and httr dependency
moved getLogo to utils-shared out of utils-web (?)

:clap:

@lindsaycarr or @thongsav-usgs i deleted utils-web.R because getJSON and getLogo were the only functions in there, and actually didn't see getLogo until I merged was still used (oops)..  but recovered getLogo() and i put it into utils-shared.R
At least it's working again and we can decide Monday where it should go from there?

Coverage increased (+2.2%) to 92.268% when pulling fb3a7ff66f8f8141ad47665695d1093abab2204f on mhines-usgs:master into 071a3bbd1e122998eea7bff10384d66da053e64f on USGS-R:master.

Coverage increased (+2.2%) to 92.268% when pulling fb3a7ff66f8f8141ad47665695d1093abab2204f on mhines-usgs:master into 071a3bbd1e122998eea7bff10384d66da053e64f on USGS-R:master.

Coverage increased (+2.2%) to 92.268% when pulling fb3a7ff66f8f8141ad47665695d1093abab2204f on mhines-usgs:master into 071a3bbd1e122998eea7bff10384d66da053e64f on USGS-R:master.


allow ^0.14.7, tests pass

I reran the tests using 0.14.7  (adjusted the dev dependencies) all passed.

@mjackson any interest in this?

@rharriso Wanna finish this up? Or should we close?

@mjackson oh sorry, this got buried in my notifications.

@mjackson updated from your feedback

Thanks @rharriso! :D

Released in version 1.4.0

@mjackson thanks!
Also, I just realized I met your partner @ryanflorence at a training session last week. It was really enjoyable!


Check ability to enter 0000-00-00 00:00:00 as timestamp

This showed up in the Wild Ride database. Not sure exactly how it was set to this.

Confirmed you can enter "0000" in timestamp field in the elements dashboard. This stores "0000-01-01 00:00:00" in the database which is not the same as "0000-00-00 00:00:00", but does still cause the same error. Value and timestamp validation checks in the elements and event frames dashboards need some scrutiny.

moment allows year 0000

See "NO_ZERO_IN_DATE" and "NO_ZERO_DATE" here. Consider disabling both of these.

Looks like this is isolated to just the Elements Dashboard.

Finally able to replicate in the Elements Dashboard. After setting a value, put a char (like 'a' or '1') at the end of the timestamp and that will produce a timestamp of "0000-00-00 00:00:00".

Doh! See String + Format 1.0.0+. Specifically "As of version 2.3.0, you may specify a boolean for the last argument to make Moment use strict parsing. Strict parsing requires that the format and input match exactly, including delimeters."


Fix Webpack error: "Cannot resolve module 'fs'" #25

This change (sorry, it's a trick) should fix the error. I tested it on my project and the error has gone.

I've found an issue with this PR. Please do not merge.

Mike, I've changed the trick used to bypass Webpack require at compile time and now it should work.


chore(packages): replace repository field with npm-friendly link

Summary
This PR replaces git+ssh links in repository field with https form for all of the packages. As a consequence, npm will display a link to github on packages sites. See https://github.com/smooth-code/svgr/issues/246 for more details.
Test plan
The result of a Github badge will be visible in npm pages of the packages.

Thanks!


Error creating issue: issue type is required

From: https://github.com/coreos/issue-sync/issues/31

Hello, I just installed and run issue-sync and got this error message:
root@jira:/usr/lib/go-1.7/src/github.com/coreos/issue-sync# bin/issue-sync --config ./config.json -u admin -p <REDACTED>
INFO[0000] config file loaded                            file="./config.json"
INFO[0000] log level set                                 app=issue-sync log-level=debug
DEBU[0000] Checking config variables...                  app=issue-sync
DEBU[0000] Using HTTP Basic Authentication               app=issue-sync
DEBU[0000] All config variables are valid!               app=issue-sync
DEBU[0000] JIRA clients initialized                      app=issue-sync
DEBU[0000] Collecting field IDs.                         app=issue-sync
DEBU[0000] All fields have been checked.                 app=issue-sync
DEBU[0000] Successfully connected to GitHub.             app=issue-sync
DEBU[0000] Collecting issues                             app=issue-sync
DEBU[0004] Collected all GitHub issues                   app=issue-sync
DEBU[0004] Collected all JIRA issues                     app=issue-sync
DEBU[0004] Creating JIRA issue based on GitHub issue #36  app=issue-sync
ERRO[0004] Error performing operation; retrying in 507ms: Request failed. Please analyze the request body for more details. Status code: 400  app=issue-sync
...
ERRO[0076] Error creating JIRA issue: Request failed. Please analyze the request body for more details. Status code: 400  app=issue-sync
DEBU[0076] Error body: {"errorMessages":[],"errors":{"issuetype":"issue type is required"}}  app=issue-sync
ERRO[0076] Error creating issue for #36. Error: {"errorMessages":[],"errors":{"issuetype":"issue type is required"}}  app=issue-sync
DEBU[0076] Creating JIRA issue based on GitHub issue #37  app=issue-sync
ERRO[0076] Error performing operation; retrying in 389ms: Request failed. Please analyze the request body for more details. Status code: 400  app=issue-sync

I created a new Jira project and configure Jira with:
* all required fields

* new field configuration

* new field configuration scheme

* new screen

* new screen scheme

* new issue type screen scheme
  The issue type screen scheme and field configuration scheme are applied to the new project.
  We are using Jira 7.5.0
  I have no idea, where this error comes from :-/

Hmm the underlying error here is
{"errorMessages":[],"errors":{"issuetype":"issue type is required"}}

Thanks for reporting this. Will investigate.

Thank you for your fast response! And if it helps, these are the projects metadata: curl ... https://ticketsystem.schul-cloud.org/rest/api/2/issue/createmeta
{
   "expand":"projects",
   "projects":[
      {
         "self":"https://ticketsystem.schul-cloud.org/rest/api/2/project/10100",
         "id":"10100",
         "key":"MT",
         "name":"MW TEST",
         "avatarUrls":{
            "48x48":"https://ticketsystem.schul-cloud.org/secure/projectavatar?avatarId=10324",
            "24x24":"https://ticketsystem.schul-cloud.org/secure/projectavatar?size=small&avatarId=10324",
            "16x16":"https://ticketsystem.schul-cloud.org/secure/projectavatar?size=xsmall&avatarId=10324",
            "32x32":"https://ticketsystem.schul-cloud.org/secure/projectavatar?size=medium&avatarId=10324"
         },
         "issuetypes":[
            {
               "self":"https://ticketsystem.schul-cloud.org/rest/api/2/issuetype/10202",
               "id":"10202",
               "description":"",
               "iconUrl":"https://ticketsystem.schul-cloud.org/secure/viewavatar?size=xsmall&avatarId=10300&avatarType=issuetype",
               "name":"GitHub Issue",
               "subtask":false
            }
         ]
      },

So there is a default issue type. And I have not seen an option to explicitly set the issue type.

I have not seen this issue while testing locally and the issue type appears to be covered by https://github.com/uwu-tools/gh-jira-issue-sync/blob/679e06c6de021437f731ed10d6d6e162cf7d8e72/jira/issue/issue.go#L260-L262.
Closing, but feel free to reopen if you run into this!


Some camera-space UI elements still broken

All of these need to be made world-space and moved to somewhere that makes sense.

Menu that can be opened from the space suit in the ship
More?

Idea: Find all Canvas elements and move them all to world positioning, but first check if they're not already being projected somewhere. Like that projection video in Timber Heart.
Needs more investigating to check all UI elements.

There shouldn't be any screen-space canvas elements anymore, except ones created after the mod starts.


Error "FirebaseAuthentication" plugin is not implemented on android

I already added all the necessary libraries in my project gradle, and module gradle in android. But I am still getting this error. Is there something I missed?

Plugin version:

^0.3.12

Platform(s):

Android

Current behavior:
Everything is setup properly and there are no console error, no build errors either. But when I clicked the button that invokes the main signing method:
const result = await FirebaseAuthentication.signInWithGoogle();

I am getting the toast message that says: "FirebaseAuthentication" plugin is not implemented on android
Expected behavior:
When I click the signin button, a prompt will appear or something?
Steps to reproduce:

Related code:
Vue component:
import { FirebaseAuthentication } from '@robingenz/capacitor-firebase-authentication';
...
const result = await FirebaseAuthentication.signInWithGoogle();

capacitor.config.json
{
  "appId": "org.my.app",
  "appName": "My App",
  "bundledWebRuntime": false,
  "npmClient": "yarn",
  "webDir": "www",
  "plugins": {
    "FirebaseAuthentication": {
      "skipNativeAuth": false,
      "providers": [
        "google.com"
      ]
    }
  }
}

Capacitor doctor:
Latest Dependencies:

  @capacitor/cli: 3.3.2
  @capacitor/core: 3.3.2
  @capacitor/android: 3.3.2
  @capacitor/ios: 3.3.2

Installed Dependencies:

  @capacitor/android: not installed
  @capacitor/cli: 3.3.2
  @capacitor/core: 3.3.2
  @capacitor/ios: 3.3.2

This message usually appears when the installation instructions have not been followed correctly.
Please make sure you follow each step correctly.
If you have recently updated from Capacitor 2, make sure that the plugin is not registered in the MainActivity.java.

Hi, @robingenz thanks for the reply. I will double-check everything. Yes, I am currently using Capacitor 3, I will check that as well. I'll give feedback the soonest.

@robingenz after re-following the setup guide it's still not working. To give you a summary of what I have done.
Context: I updated manually from cap 2 to cap 3, seems to be no issue as I can build successfully.
1. Properly installed required packages

2. Add firebase to android setup
google-services.json

File present

root-level build.gradle
// Top-level build file where you can add configuration options common to all sub-projects/modules.

buildscript {

    repositories {
        jcenter()
+        google()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:3.6.1'
+        classpath 'com.google.gms:google-services:4.3.10'

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

apply from: "variables.gradle"

allprojects {
    repositories {
        jcenter()
+        google()
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

app-level app/gradle.build
apply plugin: 'com.android.application'
+ apply plugin: 'com.google.gms.google-services'

android {
    compileSdkVersion rootProject.ext.compileSdkVersion
    defaultConfig {
        applicationId "org.axie.account.tracker"
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
}

repositories {
    flatDir{
        dirs '../capacitor-cordova-android-plugins/src/main/libs', 'libs'
    }
}

dependencies {
    androidTestImplementation "androidx.test.espresso:espresso-core:$androidxEspressoCoreVersion"
    androidTestImplementation "androidx.test.ext:junit:$androidxJunitVersion"
+    implementation platform('com.google.firebase:firebase-bom:29.0.0')
+    implementation 'com.google.firebase:firebase-analytics'
+    implementation 'com.google.firebase:firebase-auth'
    implementation "androidx.appcompat:appcompat:$androidxAppCompatVersion"
    implementation fileTree(include: ['*.jar'], dir: 'libs')
    implementation project(':capacitor-android')
    implementation project(':capacitor-cordova-android-plugins')
    testImplementation "junit:junit:$junitVersion"
}

apply from: 'capacitor.build.gradle'
apply plugin: 'com.google.gms.google-services'

3. App's SHA-1 setup done, and Auth Stragegy enabled already
4. Implementation
src-capacitor/capacitor.config.json
{
  "appId": "org.axie.account.tracker",
  "appName": "Axie Dashboard",
  "bundledWebRuntime": false,
  "npmClient": "yarn",
  "webDir": "www",
  "plugins": {
    "SplashScreen": {
      "launchShowDuration": 0,
      "launchAutoHide": false,
      "backgroundColor": "#ffffff"
    },
    "PushNotifications": {
      "presentationOptions": [
        "badge",
        "sound",
        "alert"
      ]
    },
    "FirebaseAuthentication": {
      "skipNativeAuth": false,
      "providers": [
        "google.com"
      ]
    }
  }
}

SignInPage.vue
// simply
const result = await FirebaseAuthentication.signInWithGoogle();

For future readers

Hi @robingenz you can close this now, It seems I have duplicated the importation of apply plugin: 'com.google.gms.google-services' in the app-level gradle.build as you can see above, it's in the top and in the bottom.

Sorry for closing, I verified it's still not working.

For future readers

I think I figured it out. I forgot to import the @robingenz/capacitor-firebase-authentication in src-capacitor/package.json. Will close this now. Thank you.

@jofftiquez Hey, I have exactly the same issue, what do you mean in "src-capacitor/package.json"
What is this package.json? Do mean the normal package.json in the root? If yes the error you get should be a different

No, not the package.json in the root. I meant the package.json in src-capacitory/package.json.


Resources required?

Hello,
Exciting project. Could you please share the minimum resource requirements to train this model?
I am getting memory errors training 500,000 256x256 images on 4 40GB A100 GPU's. Also my CPU memory is 128GB.
I tensorflow/stream_executor/stream.cc:1990] [stream=0x5570d9fd4600,impl=0x5570d9fd2050] did not wait for [stream=0x5570d9fd40a0,impl=0x5570d9fd2940] 2021-05-26 01:09:18.033272: I tensorflow/stream_executor/stream.cc:4925] [stream=0x5570d9fd4600,impl=0x5570d9fd2050] did not memcpy device-to-host; source: 0x2ac3e5d41a00 2021-05-26 01:09:18.033313: F tensorflow/core/common_runtime/gpu/gpu_util.cc:293] GPU->CPU Memcpy failed /hpc/users/marxg01/.lsbatch/1622001386.34151325.shell: line 23: 389547 Aborted                 (core dumped)

I cannot find out the problem from this error. Did you strictly follow all the steps in README.md? Or what modification did you make? Maybe try CUDA_VISIBLE_DEVICES=0,1 python ... to just use two GPUs.

My submission argument was: CUDA_VISIBLE_DEVICES=0,1,2,3 python train.py --img_dir /sc/arion/projects/tauomics/NFT_GAN/tiles --experiment_name NFT2

Are the other steps the same as README.md including enviroment?

Yes I setup the environment according to the README.md but I am using my own dataset. "--img_dir" is pointing to a directory of +500,000 256x256 .png's

Ok, I will check the code. If possible, by the way, I suggest using the dataset of this code to check whether the error only happens with your own data. And maybe try CUDA_VISIBLE_DEVICES=0,1 to use fewer GPUs, using all GPUs of a device may cause an error (I don't know why).

The problem was fixed by deprecating my Cuda version from 11.1 to 7.0.28
Appreciate the help!


Create graphics component

At first, it should be a place to load graphic image from geoserver.

Shouldn't we wait the response from #144 first?

@barbier added dependency of issue #144


Next step

Hello!
Is there any event for next and back buttons?

Hi,
You can use change emit. Change emit returns to you currentIndex and oldIndex parameters.

Hi, I can't use emit change its not working when I when change the tab


Push all to remote

This uses the lfs.ScanRefsMode scan mode when pushing if the --all flag is given. This lets you confirm that everything referenced in the given ref has been pushed to the given remote.

Other than my one comment, looks good to me :+1:

You need to update the man page too. :)
I like the concept, but I think its interpretation of --all is potentially misleading. It's "all at one ref" not "all binaries ever", which is not symmetrical with git lfs fetch --all which downloads all referenced binaries ever (for backup). I'm concerned that people will think they can perform a complete migration of their LFS files using fetch --all then push --all and they'd be done - but they won't be because as currently implemented it would actually implicitly mean push --all HEAD only.
I think git lfs push --all with no ref parameter should mean push all binaries ever i.e. using ScanAllMode. I think the behaviour in this PR i.e. ScanRefsMode should be reserved for either a different option (--all-ref?) in which case ref args should be disallowed, or alternatively ScanRefsMode should only be used when a ref is given explicitly on the command line, not implied HEAD.

Also the non-migratory version of --all might need a step like prePushCheckForMissingObjects to cope with cases where the person pushing doesn't have the entire LFS state.

I totally updated the man page, but forgot to push. Or I faked the commit times :trollface:
fetch symmetry is a better idea. :+1:
# PUSH EVERYTHING
$ git lfs push --all origin

# just master branch
$ git lfs push --all origin master

# multiple refs
$ git lfs push --all origin master feature/1 v1.0

I'll add a test case with missing objects too. Good catch.

I totally updated the man page, but forgot to push. Or I faked the commit times :troll face:

I believe you ;)

# PUSH EVERYTHING...

:+1:

The behavior matches https://github.com/github/git-lfs/pull/646#issuecomment-138901295 now. Still a couple issues:

Probably want to use lfs.ScanRefsToChan() like fetch --all does. It has its own spinner while it's scanning the entire history.

prePushCheckForMissingObjects() outputs a separate progress output.
 $ git lfs push --all origin master
 (1 of 1 files) 24.65 KB / 24.65 KB
 (0 of 3 files, 2 skipped) 0 B / 1.45 MB, 1.43 MB skipped

Basically copied a bunch of spinner code from fetchAll() to get this:
$ git lfs push --all origin
Scanning for all objects ever referenced...
✔ 3 objects found
Pushing objects...
(1 of 1 files) 24.65 KB / 24.65 KB
(0 of 3 files, 2 skipped) 0 B / 1.45 MB, 1.43 MB skipped

I removed the first progress meter by setting dryRun to true.
$ git lfs push --all origin
Scanning for all objects ever referenced...
✔ 3 objects found
Pushing objects...
(0 of 3 files, 3 skipped) 0 B / 1.45 MB, 1.45 MB skipped

It still writes the progress log if GIT_LFS_PROGRESS is passed, though.

I removed the first progress meter by setting dryRun to true.

Wow, that's entirely not what I would expect dryRun to do. I think that option should be renamed to suppressProgress instead to avoid confusion in future, because that's what it actually does - looks to me like dryRun=true does everything dryRun=false does apart from the progress output. I can imagine a time when someone fixes it to actually be a dry run option (and thus not do anything except local scanning) and for that to break this code.
Other than that and my man comment, looks good to me! :+1:

I agree about dryRun, but I want to update that in a separate PR.


"make install" target needs to install ackrc

The ackrc needs to get installed into /etc/ackrc when ack installs.
Do we need to handle the case when there's already one there and not overwrite it?

What if a user is installing ack2 into a perlbrew environment? They may not want to submit sudo permissions.

To expand upon that last point, we may have to change how config files are found.  I'm thinking of using File::ShareDir for that special case, maybe.

Define the rules for placement of /etc/ackrc on all platforms
CPAN installer has to install /etc/ackrc
ack --install-ackrc


Add arm builds and create a multi-arch docker image manifest

I would like to be able to run openebs/node-disk-operator on a mixed-arch kubernetes cluster, where I have a few amd64 and a few armv7l architectures.
To do this, it would be great to have a multi-arch docker image to utilize.
Currently, the only image I can access is quay.io/openebs/node-disk-operator-amd64:v0.4.7.
I would like to be able to pull quay.io/openebs/node-disk-operator:v0.4.7 and have it be a manifest list that references all of the supported arches.
How close are we to being able to do this?  Is arm support still in alpha?

Currently, we have arm64 docker images available only for the ci tag, which has lot of changes from the v0.4.x releases.
We will raise a PR to add arm64 docker images for the v0.4.x releases and try to include it in v0.4.8 release.
node-disk-manager (NDM) now has support for arm64 ,amd64 and ppc64le architectures. But, for some other components in openebs, auto-building arm based docker images is still a work in progress. If you want to use the NDM only, I think multiarch will be possible from next release.
I have another question on the architectures that you have mentioned. Is armv71 different from arm64? We have enabled builds only for arm64, so if it is different may need to explore on it.

PR #380 adds arm64 auto-build to v0.4.x release branch

The PR has been merged. Docker images will be pushed for arm64 from v0.4.8

@akhilerm, yes armv7l is a 32-bit arm architecture.  It corresponds to the arm arch target in golang.
Many boards are 32-bit arm, such as: ODroid XU4, Raspberry PI 2 v1.1 or earlier

Hi @joekhoobyar - would you like to contribute towards moving towards a Docker manifest  quay.io/openebs/node-disk-operator than can help with pulling different architecture images. Today we have support for amd64,  arm64 and power. If we have a setup in circle ci or github actions that can be used for building arm7l, we would love to automate it.
Would love to hear your suggestions?

I would love to contribute, sure.  I'm sure I have all of the local capabilities to build amd64 and arm arches without needing to run VM(s) and if need be, I could run software virtualized VM(s) to build arm64 arches.
What do I need to do to get started with you guys?

What standards should I be following?
How do you prefer to orchestrate your docker image builds?  Shell scripts driving docker commands that consume Dockerfile(s)?
What existing scripts for building docker image should I pick up and start modifying?

@kmova  - Did you see my above questions?
In the meantime, I will just pull the code down and play with the build, then make a fork.

@kmova  - On this branch I am able to successfully build the arm binaries using a cross-compiler.
I will move on to the testing the docker image soon, but I am about to go on a weekend trip tomorrow morning, so I need to go pack.  :)

@joekhoobyar  Is it possible to use buildx to create multi arch docker image and then create the docker manifest like openebs/node-disk-manager:v0.4.8?

How do you prefer to orchestrate your docker image builds? Shell scripts driving docker commands that consume Dockerfile(s)?

Currently we are using a combination of Makefile, shell scripts and docker files to create the image. I prefer following a similar pattern for creating the manifest also.

What existing scripts for building docker image should I pick up and start modifying?

you could refer this


Adding Python3.7 to release notes.

@aselle FYI
We will need to copy from the new release notes for the final release. But you do not need to rebuild.


Record 4 rtsp stream and concatenate them 1 file

Description
Hi, I want to record into a single file the stream of 4 IP camera working in RTSP.
 The module nvcompositor doesn't work on the coral.

Is there a problem in my command ?
Click to expand!
Issue Type
Others
Operating System
Mendel Linux
Coral Device
Dev Board
Other Devices
No response
Programming Language
Python 3.8
Relevant Log Output
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Progress: (open) Opening Stream
Progress: (open) Opening Stream
Progress: (connect) Connecting to rtsp://<IP_ADDRESS>:554/1/h264major
Progress: (connect) Connecting to rtsp://<IP_ADDRESS>:554/1/h264major
Progress: (open) Retrieving server options
Progress: (open) Retrieving server options
Progress: (open) Retrieving media info
Progress: (open) Retrieving media info
Progress: (request) SETUP stream 0
Progress: (request) SETUP stream 0
Progress: (request) SETUP stream 1
Progress: (request) SETUP stream 1
Progress: (open) Opened Stream
Setting pipeline to PLAYING ...
New clock: GstSystemClock
Progress: (request) Sending PLAY request
Progress: (request) Sending PLAY request
Progress: (open) Opened Stream
Progress: (request) Sending PLAY request
Progress: (request) Sending PLAY request
Progress: (request) Sent PLAY request
Progress: (request) Sent PLAY request
Redistribute latency...
Redistribute latency...
^Chandling interrupt.
Interrupt: Stopping pipeline ...
EOS on shutdown enabled -- Forcing EOS on the pipeline
Waiting for EOS...
^Chandling interrupt.
Interrupt: Stopping pipeline ...
Interrupt while waiting for EOS - stopping pipeline...
Execution ended after 0:00:10.422027293
Setting pipeline to PAUSED ...
Setting pipeline to READY ...

closing this as we have duplicate issue at: https://github.com/google-coral/examples-camera/issues/90


Fix 'Download Image' button animation

Fix the 'Download Image' button animation, mentioned @ #250 !

[x] Give it the same width & border-radius as the 'Copy as' buttons
[x] Use a dark green with white background

Here's the difference:
Before (Image by @dhruvkb ):

After:

This was fixed in #323
Thank you for your contribution

Thanks for fixing it, @brenoferreira !


Running clang-format over the frontend libraries.

Mostly just wanted to see what the diff looked like.

Trying a different approach.


Customize the look

Hello,
is it possible to customize the look of pulltorefresh.js? I like this library and it works very well, however I would like to have more of an Android look (see screenshot below) for a progressive web app that I am developing.

That's in our roadmap, however there's no branch for it. Maybe you contribute by starting it?

I was able to achieve the look I wanted by heavily customizing the styles and using a rotating svg element for instructionsPullToRefresh.

Additionally you can use the options getMarkup and getStyles for custom templating and such.
Both options should be functions and must return html/css respectively, I think is better than heavely override the css.
Of course, it would be helpful to know how you did it.

This is what I meant by 'overriding the css'.

I forgot to attach the image...

please share your entire code.


Change popover border radius to 16px

@Expensify/design
Details

Fixed Issues

$ https://github.com/Expensify/App/issues/42716
PROPOSAL:
Tests

[ ] Verify that no errors appear in the JS console

Offline tests

QA Steps

[ ] Verify that no errors appear in the JS console

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 the expected offline behavior in the Offline steps 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

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

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] 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 is localized by adding it to src/languages/* files and using the translation method

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

[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] 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
[ ] I verified that if a function's arguments changed that all usages have also been updated correctly
[ ] If any new file was added I verified that:

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

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

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] 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.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Can you show this screenshot here, but with the very first item in the menu (Start chat) in the :hover state?

We might need to add extra margin to the top/bottom of the list to accommodate for the larger border radius.

Just checked. Looks like there is enough padding. Does this look fine?

Technically not quite - I think it should have the same about of vertical padding as the border radius value. So it should probably be bumped from 12px to 16px padding.

So it should probably be bumped from 12px to 16px padding.

Sounds good to me!

I have pushed the changes. There are 2 notes to cover:

The attachment modal is now using border radius of 16px however the "padding" is 15.5px. In that modal we render the header which uses a fixed height of 72px but it also has a border of 1px width, this leaves us with 71px. The close button takes 40px. Leaving us with 31px. Since the button is vertically centered the 31px is split in half and we get 15.5px as "padding". This is not perfect but is pretty minor and not worth optimizing for

The bottom docked modal uses a different border radius (20px). Is that expected?

Ah, so I am only suggesting that you change the top/bottom padding on popovers, not the full screen modals on desktop. Can you revert that part? We only want the increased padding on popover menus like this:

The bottom docked modal uses a different border radius (20px). Is that expected?

I guess it makes sense to use 16px radius here, to better match our system. Thoughts @Expensify/design?

The bottom docked modal uses a different border radius (20px). Is that expected?

I guess it makes sense to use 16px radius here, to better match our system.

Yeah that would make sense, though it looks like we have a lot more border radius variables in code than we do in Figma:
    componentBorderRadius: 8,
    componentBorderRadiusSmall: 4,
    componentBorderRadiusMedium: 6,
    componentBorderRadiusNormal: 8,
    componentBorderRadiusLarge: 16,
    componentBorderRadiusXLarge: 28,
    componentBorderRadiusCard: 20,
    componentBorderRadiusRounded: 24,

So I suppose if it's using one of those variables it's not the end of the world. But it makes sense to give that the same border radius as all the other modals, so I'd be in favor of that change.

Nice, cleaning those up would be a good follow up project for sure.

@shawnborton

Ah, so I am only suggesting that you change the top/bottom padding on popovers, not the full screen modals on desktop. Can you revert that part?

I didn't change the padding on the full screen modal. I have only changed the border radius. There is no real padding style, what I was referring to as "padding" is the remaining space, it was always 15.5px.

Ah, no. The only change there would be for the border radius of the outer shape of the modal.

@shawnborton Regarding the bottom docked modal

I guess it makes sense to use 16px radius here, to better match our system

What about the padding? It's 12px now, should I bump this to 16px as well?

I think that makes sense, especially when the bottom-docked modal just has menu options in it.

Updated

Before
After

Looks great to me.

Reviewer Checklist

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

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

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

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

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

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

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

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

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

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

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

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

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/3004659/0737ec94-914f-430f-87a4-625f29504c2f

MacOS: Desktop
https://github.com/Expensify/App/assets/3004659/4c25ca13-9cf0-4ac7-b308-37f6468f40e0

Android: Native
https://github.com/Expensify/App/assets/3004659/648d32d0-4ff1-42ad-b6b1-86973ae7cc70

Android: mWeb Chrome
https://github.com/Expensify/App/assets/3004659/feacf13d-d541-46ca-8238-e57631cb9ec6

iOS: Native
https://github.com/Expensify/App/assets/3004659/3d186301-a212-419c-ae9d-7c10602bc738

iOS: mWeb Safari
https://github.com/Expensify/App/assets/3004659/06d8b0b8-037e-47d9-88b5-6a3dc6354992

For that onboarding modal, can you confirm that the border radius in question is the outer border radius of the entire modal, or the inner border radius of the video? I think what we have there is working fine though, so I would also opt to just leave it alone.

For that onboarding modal, can you confirm that the border radius in question is the outer border radius of the entire modal, or the inner border radius of the video? I think what we have there is working fine though, so I would also opt to just leave it alone.

That's the border radius of the video player as seen here and has nothing to do with the border radius of the entire modal. So leaving it alone seems to be the consensus here.

Code changes make sense to me, will leave it to @shawnborton to confirm that the style changes are as expected.

Going to run a test build now to make sure everything looks good.

Cool, going to merge this!

Why do we have this marked as NoQA though? This should be QA'd.

Going to change the PR title.

: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.

🚀 Deployed to staging by https://github.com/shawnborton in version: 9.0.1-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/yuwenmemon in version: 9.0.1-19 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Extracting basic Aadhaar information

Possible solutions:

Dynamic Array Extraction (most promising): the index of each value could be different for each user. We need to know each step for several values. Some value acts (#) as the delimiter.
ZK-Regex (maybe not needed)

Goal of extracting fields:

Name
Aadhaar Number
Date of Birth

Nullifier in #132

Merged on #139


MXNET_CUDNN_AUTOTUNE_DEFAULT problems

When I set MXNET_CUDNN_AUTOTUNE_DEFAULT =1, it won't stop.WTF~
[12:39:44] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:40:03] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:40:18] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:40:23] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:40:33] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:40:39] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:40:45] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:40:52] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:40:59] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:41:05] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:41:14] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:41:19] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:41:26] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:41:31] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:41:38] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:41:45] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:41:53] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:41:59] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:42:07] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:42:12] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:42:17] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:42:17] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:104: If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable cudnn tuning.
[12:42:27] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:42:30] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:42:37] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:42:42] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:42:47] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:42:55] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:43:01] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:43:07] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:43:16] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:43:21] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:43:28] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:43:39] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:43:43] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:43:53] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:44:00] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:44:07] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:44:13] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:44:21] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:44:29] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:44:33] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:44:41] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:44:46] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:44:57] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:45:04] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:45:08] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:45:18] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:45:22] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:45:28] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:45:33] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:45:37] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:45:47] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:45:51] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:45:58] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:46:03] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:46:12] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:46:17] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:46:26] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:46:33] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:46:39] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:46:46] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:46:52] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:47:00] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:47:06] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:47:14] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:47:23] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:47:31] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:47:40] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:47:47] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:47:53] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:47:59] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:48:07] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:48:11] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:48:20] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:48:26] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:48:33] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:48:43] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:48:51] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:48:56] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:49:01] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:49:12] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:49:20] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)
[12:49:27] /root/lilw/mxnet/src/operator/nn/./cudnn/./cudnn_algoreg-inl.h:97: Running performance tests to find the best convolution algorithm, this can take a while... (set the environment variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable)

...
Never stop.
this can take a while...

@mxnet-label-bot  add [Cuda, Bug]

@mxnet-label-bot remove [Bug]

Hello @intgogo,
I experienced a similar problem during training of a CNN-model with multiple output heads.
Are you using the Gluon or MXNet python interface for training your model?
The problem appeared for me more often in cases where I increased the number of layers of the same model architecture.
In my case the CUDNN optimization appeared before every call of:
for _, (data, value_label, policy_label) in enumerate(train_data):

when I changed my training_data content.
For some models this optimization took roughly 15s causing a long delay during training, but disabling CUDNN-optimization resulted in an even longer training time.
I ended up porting the model architecture and training code to MXNet's symbol API which took me ~2 days of work, but I didn't encounter this problem anymore.
I investigated the source code a bit and it could be that the optimization isn't cached properly for all models.
cudnn_algoreg-inl.h
https://github.com/apache/incubator-mxnet/blob/3f3ba92ae1468d08de088d2291ca14e2d5dc5515/src/operator/nn/cudnn/cudnn_deconvolution-inl.h#L818
    // An algo specification by the user may be cached here, but another
    // convolution will match only if identically specified.
    // We're caching results of *Get* as well as *Find*, but these records
    // will be held distinctly because param_.cudnn_tune is part of the key
    CuDNNDeconvAlgoReg::Get()->FindOrElseRegister(...)

It might be useful for users to provide additionally an explicit call for this operation and also to save it within the model or a seperate file.
Currently, if you load the model for inference it has recompute the CUDNN optimization on the start-up of the application.

See https://github.com/apache/incubator-mxnet/issues/10567 for caching CUDNN autotune results feature request

cc @ptrendx @DickJC123, it would be good if we could fix this problem.

Sorry this issue got buried on the todo stack.  To be honest though, it may not be a bug in the convolution algo cache implementation, but more an issue with the policy of emitting warning messages.  The repeated message comes after every 50 new additions to the convolution algo cache.  At the point when there's 1000 differently-spec'd convolutions in the model, the following message appears once:
If you see this message in the middle of training, you are probably using bucketing. Consider setting env variable MXNET_CUDNN_AUTOTUNE_DEFAULT to 0 to disable cudnn tuning.

So if @intgogo still cares about this issue, maybe we can hear if the model in question is continually generating convolutions with unique parameters (shapes, strides, etc.).  Also, I wouldn't mind hearing opinions about a new algo-cache-growth warning policy.  Here are a couple of options:

Emit warning once when the 1st conv algo is added to the cache,
Emit warning once when the Xth conv algo is added to the cache, e.g. 50,
Emit warnings as the cache doubles in size, e.g. with size 50, 100, 200, 400, 800, 1600, ...

Warning only once looks good. We should also allow users to query and set the benchmarking options. Ideally we should allow tuning results to be saved and loaded so that in a deployment environment things are stable and won't cause surprises

About a year ago we discussed about adding a general interface for graph optimization to MXNet: https://github.com/apache/incubator-mxnet/issues/16173
I thought the easiest way to do this was to add a save() and a load() function to the MXNet executor class, which would create hardware-specific memory dump.
At least for MXNet-TensorRT this should be straightforward, since TensorRT already allows saving and loading an engine file from disk.


third_party: update six to 1.16

Improves compatibility with Python 3.10
@thirtytwobits Could you share your local environment setup so I can test it correctly? Nevertheless, this updates the bundled six which should theoretically solve the problem.
I'm also working on migrating pyuavcan to support numpy >= 1.20, which allows 3.10 support.

Can we please also update the CI to start testing against 3.10? See details here: https://github.com/UAVCAN/pydsdl/blob/master/CONTRIBUTING.rst#supporting-newer-versions-of-python

Yeah, working on it. The CI has borked itself (although I think I just fixed it), and appveyor python 3.10 has some complications (although it does appear to be supported).

@coderkalyan Can we please focus on this before moving on further with PyUAVCAN?

@pavel-kirienko could you take another look? After far too much fighting with the CI, everything seems to work now.


The migration error message popups need to be dismissed

Steps to reproduce:

Select a VM which cannot be migrated
Do the migration

Result:
The error message popups don't dismiss themselves, even if users turn the page forward or backward

next version fix

close as migration is currently move-out.


all the end points listed in the example have 4.1-preview.1 at the end

all the end points listed in the example have 4.1-preview.1 at the end
example
GET https://dev.azure.com/{organization}/_apis/notification/eventtypes/{eventType}?api-version=4.1-preview.1
now that final version is released, it should be GET https://dev.azure.com/{organization}/_apis/notification/eventtypes/{eventType}?api-version=4.1

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

ID: da0d7182-ea0b-a67b-cc98-bf2c5935e504
Version Independent ID: e109ebda-9ca1-244f-ddee-813fa9a97c98
Content: Event Types (VSTS Notification)
Content Source: docs-ref-autogen/4.1/notification/Event%20Types.yml
Product: devops
GitHub Login: @wnjenkin
Microsoft Alias: whjenkin

Now, Its getting redirected to Azure DevOps Services REST API 5.0 which is the latest version


[WIP] Various updates

Matrix is the preferred chat platform
Tower -> Controller
Don't use old version of Reddi

Hi @gundalow, I just now created the following PR #80  to address some changes made by you in this PR.
detailed Information on Matrix have also already been added to the List in the Meantime, and with your approval, I would like to close this WIP PR and instead merge the one I linked, if you want to resolve the Issues with your branch (conflicts and CI) we can of course merge this one instead and I will happily close mine.
Greetings.
^C

Replaced by https://github.com/ansible-community/awesome-ansible/pull/80


Enforce custom nodes to keep their original type

Replaces PR https://github.com/godotengine/godot/pull/82684 with a move away from Core/Object in favor of Scene/Main/Node metadata usage.
Closes https://github.com/godotengine/godot-proposals/issues/7905

Not sure if showing extend icon for non-custom-type scripts is a good idea:

It can show for scripts that can't be extended, and more importantly, takes space, which is very sparse in that area.

You could try using _property_can_revert() and _property_get_revert() to handle script default. It could allow removing PackedScene changes.

Script button "Extend" is now only shown when the script is a custom type script
"Clear" is only removed if resource is actually a script

I haven't found a nice way around the PackedScene changes yet. As I see it, _property_can_revert() and _property_get_revert() are virtual methods. Where would be a good place to override them to get the desired effect?

Where would be a good place to override them to get the desired effect?

In Object. Although they are part of GDClass, so not sure if it's possible. In worst case you can put some duplicate code in Node and Resource.

I was trying to avoid changes to core/ as much as possible with this PR, as this was requested in the last PR attempt. That's why I initially didn't use CoreStringNames.
Maybe I can get away with the changes in packed_scene if I add a condition in PropertyUtils::is_property_value_different as I already did in PropertyUtils::get_property_default_value.

Can you rebase to resolve conflicts?

Can you rebase to resolve conflicts?

Yes, will do this now.

Rebased.

I think I got all suggestions in place and also moved CoreStringNames to SceneStringNames.

Thanks for rebasing!
@KoBeWi @AThousandShips Does this still look good to merge to you after a few months?

So I decided to give it a last try by testing with my project and there is a critical bug 💀
If you instantiate a scene, the value of script property will always be saved (as if it couldn't determine the default value). In case of built-in scripts, they will get embedded in the parent scene.

Hi @KoBeWi, let me look into it. Can you give me minimal steps to reproduce this issue?

Create a scene
Attach any script to root node
Create another scene
Instantiate the first scene in the new scene
Save and check the tscn file

Thanks, and congratulations on your first contribution! 🎉


ES2015 refactor

Related to #13. Let's simplify the codebase and move it into a pure JS/ES2015 compatible code.

Version 1.0.0 was released and the JS/ES2015 rewrite has been completed and merged in 3c623a75a289113cde772f9fc7cdcc5ef59f8ac4


Enable atomic moves of ClusterIdentity activations between nodes

It could be very useful to be able to move activations atomically, without dead letters or the chance that the identity will be activated on another node. This supports use cases such as local affinity, targeted draining of workloads to new nodes etc.
Atomicity
The atomic move will require updating the IIdentityLookup interface with a new method to support this. Ex:
Task<PID?> MoveAsync(ClusterIdentity clusterIdentity, PID from, Member to, CancellationToken ct); ?
We will need to lock the ClusterIdentity while moving the activation, so no race conditions can occur.  This will also require new functionality in IdentityStorage.
Forwarding
In addition, if we want to prevent dead letters, we will need to have a mechanism for storing and forwarding messages while the move is in progress. This might be done with receiver middleware, or perhaps we can solve it another way. Open for suggestions here..
Ideally we would want to preserve order of messages, but that might be tricky to solve. When we update the available PID for that cluster identity, members will send their messages directly to the new activation. This might happen before the messages stored in the forwarding (old) actor have sent its messages to the new actor, and thus cause out of order processing.
This is only going to be a problem if the sender has multiple messages in-flight though, request-response style communication should work fine.
Open for suggestions of how we handle the cases where we have multiple messages in-flight.

Local affinity 2.0 merged


Fix issue with concurrent timers

This is a fix for https://github.com/dapr/dapr/issues/5978, which turned out to be a bug in how we track timer creation in the orchestration runtime state.
This PR also adds multiple test updates that would have helped identify this issue sooner.

Verified that this fixes the issue for Dapr.


Show how much time is left (app and browser)

There is right now a notification when the location-sharing-time expires, but add a Timer on how much minutes are left, for example. No need to be over-detailed (seconds) in my opinion, but sometimes useful.
In the app itself so i can see how much time is left and/or on the map for the viewer.

Good idea. I've implemented it; it will be part of the next release.

This is now included in v1.0.1. I've pushed it to the repo, but I don't know how long it takes for F-Droid to update it - shouldn't be more than a couple of days.


Create Item that takes a JSON string

Is your feature request related to a problem? Please describe.
I want to put an item in a Cosmos DB container using the SQL API.
If I already have the object in JSON string form (not a stream and not a class), why can't I create the item using the .NET SDK directly? The API expects either a class (which means deserialising) for CreateItemAsync or a stream (for me to copy the string contents into another stream) for CreateItemStreamAsync. Or am I missing something? is it because the SDK would need to copy the string into a stream too?
Describe the solution you'd like
A CreateItemAsync override that takes a string because serialization has already been done.

The string will eventually need to be converted to a stream.
It pretty unusual to just have a JSON string. If you are reading in from a file then it can be read in as a file stream. If it's from another service the network stream can be passed into the SDK. Most  JSON serializers support streams. In what scenario do you have just a string?

Adding to what @j82w mentioned.

A CreateItemAsync override that takes a string because serialization has already been done.

Serialization is not serialization to string, it means serialization to a byte stream that is sent to through the network wire.
With this definition, the SDK already supports taking content that was already serialized (Stream).

The string will eventually need to be converted to a stream.

Cosmos needing a stream for the json wasn't known to me - it makes sense, but is an implementation detail from SDK consumer point of view.

Its pretty unusual to just have a JSON string. If you are reading in from a file then it can be read in as a file stream. If it's from another service the network stream can be passed into the SDK. Most  JSON serializers support streams. In what scenario do you have just a string?

The default Cosmos serializer wasn't generating desired output for string enums. So was using Newtonsoft with StringEnumConvertor and was hoping for convenience I didn't need to copy it into another object for CreateItemAsync or stream for CreateItemStreamAsync. Seemed inefficient.
The system.text JSON serializer seems a

Adding to what @j82w mentioned.

A CreateItemAsync override that takes a string because serialization has already been done.

Serialization is not serialization to string, it means serialization to a byte stream that is sent to through the network wire.
With this definition, the SDK already supports taking content that was already serialized (Stream).

Actually I meant JSON serialization (from object to string) had already been done.  But understand what you mean.

Have you tried using a custom serializer? The default implementation is here.


Fixes: #1188 Improved the design of the contact form

Fixes: #1188
Improved the overall design of the contact form.
Now the form looks appealing and modern.

@akshitagupta15june please review and merge the pull request.
Let me know if any changes are needed. :)

please synk with current changes


Circumventing the IQ module in the pdh input of the Fabry Perot lockbox module

Hi,
I am trying to implement at PDH lock in pyrpl using an error signal already down-mixed in the detector that detects the cavity reflectivity .
I would like to use the Fabry Perot lockbox module, but the PDH input into that module automatically couples to the IQ module because it expects an AC signal to downmix into the final error signal. Since I already have a final error signal, I do not need this. I have tried to circumvent this by setting the modulation frequency to 0 and the amplitude to 1 to configure the IQ module as a "all-pass" filter for my error signal. From what I can see of the source code, the input high-pass filter is automatically set to have a cut-off freuqency of freq_mod /128, meaning setting the modulation frequency to 0 should also "disable" this highpass filter. However this does not seem to work, and the signal I get out is tiny (~1e-6 Vpp) compared to the input (almost 900 mVpp).
Is there any way of cirucmventing the IQ module in the Fabry Perot, or am I doing something wrong in configuring the IQ?

sorry I misunderstood how the IQ module is configured. The quadrature factor should be 1, the phase 90 and amplitude should be 0 in order to configure the module to be "all-pass". However, this still does not work

You need to use the Analog PDH input. It is not present by default in the Faby-Perot lockbox but it is defined in the code so if you create your own lockbox you can use it. Let me know if you need help doing that.