fix keyboard shortcut table row

Details

Fix text is going out of border in keyboard shortcut table
Fixed Issues

$ https://github.com/Expensify/App/issues/11411
Tests

Go to settings > Preferences
Change language to español
Go back > About > Keyboard shortcuts

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

PR Review Checklist

Contributor (PR Author) Checklist

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

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

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

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

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

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that 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 was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] 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] Any functional components have the displayName property
[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 a new CSS style is added I verified that:

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

[x] If the PR modifies 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] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

PR Reviewer Checklist
The Contributor+ will copy/paste it into a new comment and complete it after the author checklist is completed

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

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

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

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

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

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product was added in all src/languages/* files
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified 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)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

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

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

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

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

QA Steps

Go to settings > Preferences
Change language to español
Go back > About > Keyboard shortcuts

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

Screenshots

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@gadhiyamanan Can you please add screenshots for native devices and mWeb as well just to confirm the changes made don't crash or produce any console error.

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

@gadhiyamanan Can you please add screenshots for native devices and mWeb as well just to confirm the changes made don't crash or produce any console error.

@sobitneupane which screenshots do i have add for native devices ?

@sobitneupane which screenshots do i have add for native devices ?

You can add screenshots of Settings > About Page.

@sobitneupane screenshots added.
cc: @Julesssss

@gadhiyamanan Can you please add 4th Step in Test and QA Section mentioning what is to be verified by QA tester. For example: Verify that text doesn't overlap with borders of the table.

recheck

Hey @gadhiyamanan, sorry to be a pain, but it's not possible to merge this PR until your commits are signed. You can find out how to do this here: https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

Ah that's annoying. But yeah, please do that. I'll be around all day to review it

created new PR , closing this


[Question] does playright-java support recording and generating code like playright-python?

Playwright-python can record user interactions in a browser and generate code，so does playwright-java support this feature？

Not yet but stay tuned we'll add it once the java API is more stable (we're going to change the way waitForEvent() is handled).

Not yet but stay tuned we'll add it once the java API is more stable (we're going to change the way waitForEvent() is handled).

Not yet but stay tuned we'll add it once the java API is more stable (we're going to change the way waitForEvent() is handled).

By the way, what are the correct steps to start playwright-java usage?
In the readme just say that user need to add maven dependency, I did it but got an error as below in idea:
Exception in thread "main" java.lang.RuntimeException: Failed to find playwright-cli

And then, I installed drivers successful by executing download_driver_for_all_platforms.sh , but got an error as below when executed install_local_driver.sh:
Downloading driver for macOS
Downloading driver for mac to /Users/ivanli/Documents/mt/fromGit/qa/waimai/ui/play-ui-java/src/main/resources/driver/mac
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   215  100   215    0     0     84      0  0:00:02  0:00:02 --:--:--    84
Archive:  playwright-cli-1.8.0-next-1610046700000-mac.zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of playwright-cli-1.8.0-next-1610046700000-mac.zip or
        playwright-cli-1.8.0-next-1610046700000-mac.zip.zip, and cannot find playwright-cli-1.8.0-next-1610046700000-mac.zip.ZIP, period.

So, what are the correct steps to start playwright-java usage? I am a bit confused now how to get started.
And, I also want to know what is the difference between driver and playwright-cli.

Not yet but stay tuned we'll add it once the java API is more stable (we're going to change the way waitForEvent() is handled).

By the way, what are the correct steps to start playwright-java usage?
In the readme just say that user need to add maven dependency, I did it but got an error as below in idea:
Exception in thread "main" java.lang.RuntimeException: Failed to find playwright-cli

And then, I installed drivers successful by executing download_driver_for_all_platforms.sh , but got an error as below when executed install_local_driver.sh:
Downloading driver for macOS
Downloading driver for mac to /Users/ivanli/Documents/mt/fromGit/qa/waimai/ui/play-ui-java/src/main/resources/driver/mac
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   215  100   215    0     0     84      0  0:00:02  0:00:02 --:--:--    84
Archive:  playwright-cli-1.8.0-next-1610046700000-mac.zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of playwright-cli-1.8.0-next-1610046700000-mac.zip or
        playwright-cli-1.8.0-next-1610046700000-mac.zip.zip, and cannot find playwright-cli-1.8.0-next-1610046700000-mac.zip.ZIP, period.

So, what are the correct steps to start playwright-java usage? I am a bit confused now how to get started.
And, I also want to know what is the difference between driver and playwright-cli.

Not yet but stay tuned we'll add it once the java API is more stable (we're going to change the way waitForEvent() is handled).

By the way, what are the correct steps to start playwright-java usage?
In the readme just say that user need to add maven dependency, I did it but got an error as below in idea:
Exception in thread "main" java.lang.RuntimeException: Failed to find playwright-cli

And then, I installed drivers successful by executing download_driver_for_all_platforms.sh , but got an error as below when executed install_local_driver.sh:
Downloading driver for macOS
Downloading driver for mac to /Users/ivanli/Documents/mt/fromGit/qa/waimai/ui/play-ui-java/src/main/resources/driver/mac
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   215  100   215    0     0     84      0  0:00:02  0:00:02 --:--:--    84
Archive:  playwright-cli-1.8.0-next-1610046700000-mac.zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of playwright-cli-1.8.0-next-1610046700000-mac.zip or
        playwright-cli-1.8.0-next-1610046700000-mac.zip.zip, and cannot find playwright-cli-1.8.0-next-1610046700000-mac.zip.ZIP, period.

So, what are the correct steps to start playwright-java usage? I am a bit confused now how to get started.
And, I also want to know what is the difference between driver and playwright-cli.

Update, it works now after I execute download_driver_for_all_platforms.sh, but playwright starts very slowly, it takes about 40s from startup to running, and some error is printed as below:
(node:91725) UnhandledPromiseRejectionWarning: Error: Lock file is already being held
    at /snapshot/playwright-cli/node_modules/proper-lockfile/lib/lockfile.js:68:47
    at callback (/snapshot/playwright-cli/node_modules/graceful-fs/polyfills.js:295:20)
    at FSReqCallback.oncomplete (fs.js:168:5)
(node:91725) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:91725) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

How to fix this error? and does the slow startup time related to this error?

Not yet but stay tuned we'll add it once the java API is more stable (we're going to change the way waitForEvent() is handled).

By the way, what are the correct steps to start playwright-java usage?
In the readme just say that user need to add maven dependency, I did it but got an error as below in idea:
Exception in thread "main" java.lang.RuntimeException: Failed to find playwright-cli

And then, I installed drivers successful by executing download_driver_for_all_platforms.sh , but got an error as below when executed install_local_driver.sh:
Downloading driver for macOS
Downloading driver for mac to /Users/ivanli/Documents/mt/fromGit/qa/waimai/ui/play-ui-java/src/main/resources/driver/mac
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   215  100   215    0     0     84      0  0:00:02  0:00:02 --:--:--    84
Archive:  playwright-cli-1.8.0-next-1610046700000-mac.zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of playwright-cli-1.8.0-next-1610046700000-mac.zip or
        playwright-cli-1.8.0-next-1610046700000-mac.zip.zip, and cannot find playwright-cli-1.8.0-next-1610046700000-mac.zip.ZIP, period.

So, what are the correct steps to start playwright-java usage? I am a bit confused now how to get started.
And, I also want to know what is the difference between driver and playwright-cli.

Update, it works now after I execute download_driver_for_all_platforms.sh, but playwright starts very slowly, it takes about 40s from startup to running, and some error is printed as below:
(node:91725) UnhandledPromiseRejectionWarning: Error: Lock file is already being held
    at /snapshot/playwright-cli/node_modules/proper-lockfile/lib/lockfile.js:68:47
    at callback (/snapshot/playwright-cli/node_modules/graceful-fs/polyfills.js:295:20)
    at FSReqCallback.oncomplete (fs.js:168:5)
(node:91725) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:91725) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

How to fix this error? and does the slow startup time related to this error?

So, what are the correct steps to start playwright-java usage? I am a bit confused now how to get started.

Did you follow the steps from this page? Look at the example project you need something like that.

And, I also want to know what is the difference between driver and playwright-cli.

These are roughly two names for the same thing .

Update, it works now after I execute download_driver_for_all_platforms.sh, but playwright starts very slowly, it takes about 40s from startup to running, and some error is printed as below:

You should not need to use download_driver_for_all_platforms.sh at all unless you are developing playwright. If you set up your Maven project correctly it will download the driver automatically.

How to fix this error? and does the slow startup time related to this error?

You are running two playright-cli at the same time and they are competing for a lockfile. First time you launch playwright it will download browser binaries for you platform which may take some time. Next run should be faster as the binaries will be picked up from cache.

So, what are the correct steps to start playwright-java usage? I am a bit confused now how to get started.

Did you follow the steps from this page? Look at the example project you need something like that.

And, I also want to know what is the difference between driver and playwright-cli.

These are roughly two names for the same thing .

Update, it works now after I execute download_driver_for_all_platforms.sh, but playwright starts very slowly, it takes about 40s from startup to running, and some error is printed as below:

You should not need to use download_driver_for_all_platforms.sh at all unless you are developing playwright. If you set up your Maven project correctly it will download the driver automatically.

How to fix this error? and does the slow startup time related to this error?

You are running two playright-cli at the same time and they are competing for a lockfile. First time you launch playwright it will download browser binaries for you platform which may take some time. Next run should be faster as the binaries will be picked up from cache.

@yury-s hi, thx reply

You are running two playright-cli at the same time and they are competing for a lockfile. First time you launch playwright it will download browser binaries for you platform which may take some time. Next run should be faster as the binaries will be picked up from cache.

I still don't quite understand why I am running two playright-cli at the same time. I just ran the example project  once in IDEA or terminal(as shown in the example readme), then error happened:
(node:91725) UnhandledPromiseRejectionWarning: Error: Lock file is already being held

@yury-s hi, thx reply

You are running two playright-cli at the same time and they are competing for a lockfile. First time you launch playwright it will download browser binaries for you platform which may take some time. Next run should be faster as the binaries will be picked up from cache.

I still don't quite understand why I am running two playright-cli at the same time. I just ran the example project  once in IDEA or terminal(as shown in the example readme), then error happened:
(node:91725) UnhandledPromiseRejectionWarning: Error: Lock file is already being held

@yury-s Hi, thx reply. I found browsers were installed in driver-bundle-x.jar by executing playwright-cli install, then I have 2 questions:

Can I just install a single specific browser not all browsers? e.g., just chromium
Every time running will execute playwright-cli to install the browser, and if remote browser version updated, the next running will down and install again the latest browser but not using the older in local cache? If so it, how to avoid? I only want the browser to be installed once whether the version is updated or not.

@yury-s Hi, thx reply. I found browsers were installed in driver-bundle-x.jar by executing playwright-cli install, then I have 2 questions:

Can I just install a single specific browser not all browsers? e.g., just chromium
Every time running will execute playwright-cli to install the browser, and if remote browser version updated, the next running will down and install again the latest browser but not using the older in local cache? If so it, how to avoid? I only want the browser to be installed once whether the version is updated or not.

Can I just install a single specific browser not all browsers? e.g., just chromium.
No, there is no such option at the moment.

Every time running will execute playwright-cli to install the browser, and if remote browser version updated, the next running will down and install again the latest browser but not using the older in local cache? If so it, how to avoid? I only want the browser to be installed once whether the version is updated or not.

Each version of playwright-java comes with a fixed version of playwright-cli which in turn comes with a fixed version of the browsers. So it will be downloaded only once.
Closing this issue as it strayed too far from the original topic. Feel free to file a separate feature request for java codegen but in any case it's already on our roadmap.

Can I just install a single specific browser not all browsers? e.g., just chromium.
No, there is no such option at the moment.

Every time running will execute playwright-cli to install the browser, and if remote browser version updated, the next running will down and install again the latest browser but not using the older in local cache? If so it, how to avoid? I only want the browser to be installed once whether the version is updated or not.

Each version of playwright-java comes with a fixed version of playwright-cli which in turn comes with a fixed version of the browsers. So it will be downloaded only once.
Closing this issue as it strayed too far from the original topic. Feel free to file a separate feature request for java codegen but in any case it's already on our roadmap.


docs: pm: System power management diagram

Add a diagram for system power management.
Signed-off-by: Flavio Ceolin<EMAIL_ADDRESS>

please fix the typo


Depthed lookups fail when program duplicator runs

  it('GH-926: Depths and de-dupe', function() {
    var context = {
      name: 'foo',
      data: [
        1
      ],
      notData: [
        1
      ]
    };

    var template = CompilerContext.compile('{{#if dater}}{{#each data}}{{../name}}{{/each}}{{else}}{{#each notData}}{{../name}}{{/each}}{{/if}}');

    var result = template(context);
    equals(result, 'foo');
  });

Fails due to throw:
     TypeError: Cannot read property '1' of undefined
      at Object.2 (eval at safeEval (/Users/kpdecker/dev/kpdecker/handlebars.js/spec/env/runtime.js:43:36), <anonymous>:8:41)
      at prog (dist/handlebars.runtime.js:563:17)
      at Object.<anonymous> (dist/handlebars.runtime.js:288:25)
      at Object.4 (eval at safeEval (/Users/kpdecker/dev/kpdecker/handlebars.js/spec/env/runtime.js:43:36), <anonymous>:11:25)
      at Object.prog [as inverse] (dist/handlebars.runtime.js:563:17)
      at Object.<anonymous> (dist/handlebars.runtime.js:323:24)
      at Object.main (eval at safeEval (/Users/kpdecker/dev/kpdecker/handlebars.js/spec/env/runtime.js:43:36), <anonymous>:16:26)
      at ret (dist/handlebars.runtime.js:532:32)
      at Context.<anonymous> (/Users/kpdecker/dev/kpdecker/handlebars.js/spec/regressions.js:162:18)
      at callFn (/Users/kpdecker/dev/kpdecker/handlebars.js/node_modules/mocha/lib/runnable.js:223:21)

It appears that the inverse block is generating a deduped function call that does not pass the depths parameter and causes things to blow up on execution.

Released in 3.0.0


svue grades not working

i don't know much, if at all, about python. i was wondering if you know anything about my issue.
i pip3 installed studentvue_cli and ran through the setup of username, password, and district.
running "svue schedule" worked, but "svue grades" failed.
'''
Traceback (most recent call last):
File "/usr/local/bin/svue", line 11, in
load_entry_point('studentvue-cli==0.7', 'console_scripts', 'svue')()
File "/usr/local/lib/python3.7/dist-packages/studentvue_cli-0.7-py3.7.egg/studentvue_cli/studentvue_cli.py", line 150, in main
fire.Fire(SVInfo)
File "/usr/local/lib/python3.7/dist-packages/fire-0.4.0-py3.7.egg/fire/core.py", line 141, in Fire
component_trace = _Fire(component, args, parsed_flag_args, context, name)
File "/usr/local/lib/python3.7/dist-packages/fire-0.4.0-py3.7.egg/fire/core.py", line 471, in _Fire
target=component.name)
File "/usr/local/lib/python3.7/dist-packages/fire-0.4.0-py3.7.egg/fire/core.py", line 681, in _CallAndUpdateTrace
component = fn(*varargs, **kwargs)
File "/usr/local/lib/python3.7/dist-packages/studentvue_cli-0.7-py3.7.egg/studentvue_cli/studentvue_cli.py", line 41, in grades
c.get("Marks").get("Mark").get("Assignments").get("Assignment")
AttributeError: 'NoneType' object has no attribute 'get'
'''
any way you could fix this?

I just released a new version of the package (install with pip install studentvue-cli==0.8), let me know if that fixes the issue. If not, let me know what the output of svue grades is

its fixed now, just had to run it as root. tysm! didn't think you would respond lol

the output is the grades, and it matches up with the web version too


cli: don't quote Postgres configs in instance creation

@vrmiguel I'm gonna merge it and make changes on top of this since it does remove the quotes. It doesn't fix the issue but it's still better than it was previously.


chore: build issue fix

PR summary
build issue fix
Fixes: <! -- link to issue -->
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[x] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?
build is failing with npm version
What is the new behavior?
updated npm to npm@9
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

:tada: This PR is included in version 0.3.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Rancher Desktop Intermittently Hangs on Ventura 13.1

Description
Hello I am from a developer experience team in my company. We have been getting devs to use Rancher Desktop since November 2022. It has been working well but when our IT team released Ventura 13.1 macOS update a lot of developers have since been experiencing Rancher Desktop hanging while running commands.
We determined it was not related to our security tools as we have shutdown them down and replicated the issue. We also enabled debug logging in Rancher Desktop and looked at the RD and Lima logs and did not see anything obvious.
Rancher Desktop version: 1.70
MacOS: Ventura 13.1
We have people on x86 and ARM laptops that experienced the freezing/hanging. How can we troubleshoot this issue or provide some better information when people are running into this issue? We would like to help figure it out and fix it.

Doh wrong repo.


[BUG] Uncaught Error: Extension context invalidated.

What happened?
A bug happened! So many errors. I don't know why.
background.ts
import browser from 'webextension-polyfill'

browser.contextMenus.removeAll();
browser.contextMenus.create({
    id: 'test',
    title: "test",
    contexts: [
        "image",
    ]
});

browser.contextMenus.onClicked.addListener(function(info, tab) {
   // TODO
   browser.tabs.sendMessage(tab.id, {...});
});

content.ts
import browser from 'webextension-polyfill'

browser.runtime.onMessage.addListener(function(request, sender, sendResponse) {
    // Do some thing with promise.
    fetch('/api').then((res) => {
             // TODO
    }).catch();

    return true;
});

errors in file content.480c00a3.js:328

Version
Latest
What OS are you seeing the problem on?
No response
What browsers are you seeing the problem on?
No response
Relevant log output
No response
(OPTIONAL) Contribution

[ ] I would like to fix this BUG via a PR

Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

I faced the same issue while add content script. I followed everything written in documentation and still get the error :

Basically, I just added a console.log to check if the script is getting loaded or not. But, here is the hack. The script loads successfully its just that I was looking into the wrong console.
When you load the script, all the updates will be visible in Tabs Console not in the Extension's Console. Please check the Tabs console. I have just ignored the error. Everything is working fine.

the same issue +1

the same issue +1

the same issue +1

same

+1


Notification failures metric doesn't increase when templating fails

What did you do?
I wrote an invalid Go template in my alertmanager config, and upon trying to send the alert notification, alertmanager produced errors in it's logs like so:
level=error ts=2020-06-16T17:03:01.483Z caller=dispatch.go:301 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="cancelling notify retry for \"pagerduty\" due to unrecoverable error: failed to template PagerDuty v2 message: template: :2: unexpected \")\" in input"

What did you expect to see?
I expected these logs, and the alertmanager_notifications_failed_total metric to be incremented.
What did you see instead? Under which circumstances?
The alertmanager_notifications_failed_total is 0 for all integrations/instances.
Environment

Alertmanager version:

v0.20.0

Prometheus version:

This was using Grafana to send alerts to Alertmanager, but how the alert is sent shouldn't matter much.

Alertmanager configuration file:

templates:
  - '*.tmpl'
global:
  resolve_timeout: 5m
route:
  group_interval: 5m
  group_wait: 30s
  repeat_interval: 12h

  receiver: test

receivers:
  - name: "test"
    pagerduty_configs:
      - send_resolved: true
        routing_key: $(INFRA_PAGERDUTY_ROUTING_KEY)
        url: https://events.pagerduty.com/v2/enqueue
        details:
          # this had a few mistakes, eg the extra unmatched )
          test: '{{ if (index .Alerts.Firing 0).Annotations.image) }} {{ (index .Alerts.Firing 0).Annotations.image) }} {{ end }}'

Logs:

level=error ts=2020-06-16T17:02:46.842Z caller=notify.go:372 component=dispatcher msg="Error on notify" err="cancelling notify retry for \"pagerduty\" due to unrecoverable error: failed to template PagerDuty v2 message: template: :2: unexpected \")\" in input" context_err=null
level=error ts=2020-06-16T17:02:46.842Z caller=dispatch.go:301 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="cancelling notify retry for \"pagerduty\" due to unrecoverable error: failed to template PagerDuty v2 message: template: :2: unexpected \")\" in input"
level=error ts=2020-06-16T17:03:01.483Z caller=notify.go:372 component=dispatcher msg="Error on notify" err="cancelling notify retry for \"pagerduty\" due to unrecoverable error: failed to template PagerDuty v2 message: template: :2: unexpected \")\" in input" context_err=null
level=error ts=2020-06-16T17:03:01.483Z caller=dispatch.go:301 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="cancelling notify retry for \"pagerduty\" due to unrecoverable error: failed to template PagerDuty v2 message: template: :2: unexpected \")\" in input"

I'm not sure how this isn't working since after reading the code, it seems like the metric is incremented immediately preceding the error message cancelling notify retry for \"pagerduty\"

Anddd I realized when I was testing the prometheus query I had the wrong Prometheus selected in Grafana.


adding the ability to output the dataset

Hello Sergey, Alex,
I just realized I had made one more update to .mapped() in which I am adding the ability to output the dataset. I need it to remove batch effects in my model like scGPT does.
Let me know if that is ok. Once this is updated I can use this version :)

Thanks @jkobject! @Koncopd could you take a look at this so that it gets into the new release?

Hm, maybe return this by default without any additional arguments? As we return a dict now, it is not a problem if we add some additinal keys.

Sounds like the right thing, Sergei!

@jkobject are you fine with the suggestion?

Works with me!

done here https://github.com/laminlabs/lamindb/pull/1504


[Event Request] - OnBeforeGetPurchAccount in Codeunit 90 "Purch.-Post"

Hello, please consider adding the following event to Codeunit 90 "Purch.-Post"
    [IntegrationEvent(false, false)]
    local procedure OnBeforeGetPurchAccount(var PurchHeader: Record "Purchase Header"; var PurchLine: Record "Purchase Line"; var GenPostingSetup: Record "General Posting Setup"; var PurchAccount: Code[20]; var IsHandled: Boolean)
    begin
    end;

and call it accordingly inside the "FillInvoicePostBuffer" procedure:
...
...
        if not IsHandled then
            if PurchLine."VAT Calculation Type" = PurchLine."VAT Calculation Type"::"Reverse Charge VAT" then begin
                if PurchLine."Deferral Code" <> '' then
                    InvoicePostBuffer.SetAmounts(
                        TotalVAT, TotalVATACY, TotalAmount, TotalAmountACY, PurchLine."VAT Difference", TotalVATBase, TotalVATBaseACY)
                else
                    InvoicePostBuffer.SetAmountsNoVAT(TotalAmount, TotalAmountACY, PurchLine."VAT Difference")
            end else
                if (not PurchLine."Use Tax") or (PurchLine."VAT Calculation Type" <> PurchLine."VAT Calculation Type"::"Sales Tax") then
                    InvoicePostBuffer.SetAmounts(
                        TotalVAT, TotalVATACY, TotalAmount, TotalAmountACY, PurchLine."VAT Difference", TotalVATBase, TotalVATBaseACY)
                else
                    InvoicePostBuffer.SetAmountsNoVAT(TotalAmount, TotalAmountACY, PurchLine."VAT Difference");

        if PurchLine."VAT Calculation Type" = PurchLine."VAT Calculation Type"::"Sales Tax" then
            InvoicePostBuffer.SetSalesTaxForPurchLine(PurchLine);

        **OnBeforeGetPurchAccount(PurchHeader, PurchLine, GenPostingSetup, PurchAccount, IsHandled);
        if not IsHandled then begin**

            if (PurchLine.Type = PurchLine.Type::"G/L Account") or (PurchLine.Type = PurchLine.Type::"Fixed Asset") then
                PurchAccount := PurchLine."No."
            else
                if PurchLine.IsCreditDocType() then
                    PurchAccount := GenPostingSetup.GetPurchCrMemoAccount()
                else
                    PurchAccount := GenPostingSetup.GetPurchAccount();

        **end;**

        OnFillInvoicePostingBufferOnBeforeSetAccount(PurchHeader, PurchLine, PurchAccount, GenJnlLineDocNo);

        InvoicePostBuffer.SetAccount(PurchAccount, TotalVAT, TotalVATACY, TotalAmount, TotalAmountACY);
        InvoicePostBuffer.UpdateVATBase(TotalVATBase, TotalVATBaseACY);
        InvoicePostBuffer."Deferral Code" := PurchLine."Deferral Code";
        OnAfterFillInvoicePostBuffer(InvoicePostBuffer, PurchLine, TempInvoicePostBuffer, SuppressCommit, PurchHeader, GenJnlLineDocNo, GenJnlPostLine);
        UpdateInvoicePostBuffer(InvoicePostBuffer);
...
...

Thank you !

Cannot add new event in obsoleted code, can you use this one?
OnFillInvoicePostingBufferOnBeforeSetAccount(PurchHeader, PurchLine, PurchAccount, GenJnlLineDocNo);

Well, yes, i can use
OnFillInvoicePostingBufferOnBeforeSetAccount(PurchHeader, PurchLine, PurchAccount, GenJnlLineDocNo);
even if is marked as obsolete ...
Da: Alexander Yakunin @.>
Inviato: domenica 18 dicembre 2022 17:03
A: microsoft/ALAppExtensions @.>
Cc: oldmat @.>; Author @.>
Oggetto: Re: [microsoft/ALAppExtensions] [Event Request] - OnBeforeGetPurchAccount in Codeunit 90 "Purch.-Post" (Issue #21372)
Cannot add new event in obsoleted code, can you use this one?
OnFillInvoicePostingBufferOnBeforeSetAccount(PurchHeader, PurchLine, PurchAccount, GenJnlLineDocNo);

Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FALAppExtensions%2Fissues%2F21372%23issuecomment-1356827666&data=05|01||078dac0a375943476dd808dae1115e00|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638069761946632894|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=tXbH0ix0wYVzreIBcE1e5p2t%2B6KY%2B0Wf7ZddrxxHHKA%3D&reserved=0, or unsubscribehttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAOCTISXGPJCBXBOWATJGRJLWN4YUDANCNFSM6AAAAAASZPS4TU&data=05|01||078dac0a375943476dd808dae1115e00|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638069761946788652|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=VOvLBGTYlwGESlMegNIGAwHlQopjNxbLfp1X66AISrg%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


GCIRCLE doesn't work

GCIRCLE doesn't work.
Other draw functions seem to work (like GLINE for example)

Implemented GCIRCLE.


Update ansible collections for 1.10

Description of the change:
Motivation for the change:
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

/retitle Bug 1999879:  Update ansible collections for 1.10


updating travis schema

Addressing #15

This PR may be good to go now for the adoption of the new Travis CI testing procedure. The method for specifying the language and version seems a bit alien to me and also raises questions about how to implement this process with the need for allow_failures as will be the case with spaghetti when I start with pysal/spaghetti#299. However, all this is a bit conjecture at the moment because we aren't actually running any tests yet...

superseded by #20

We moved to pytest so closing ths.


Support "parts of speech"

See https://github.com/metanorma/metanorma-standoc/issues/249

Basically designations are now hashes and accept everything, including "part of speech". I'm going to replace them with dedicated classes, and they'll have "parts_of_speech" attribute, as well as the other grammar ones.

Ping @skalee we need to move ahead here...

Thanks, closing this.


Can't take screenshot

[x] I have searched open and closed issues for duplicates
[x] I am submitting a bug report for existing functionality that does not work as intended
[x] This isn't a feature/enhancement request or a discussion topic

Bug description
Cannot take screenshot of region using hotkey
Steps to reproduce the bug

This does not reproduce the bug, but rather describes what I was doing prior to the bug occurring.
I took a screenshot and pressed "Save to File"
I was messing around with the "Save as type" drop down in the "Save As" windows (changing between "png" and "all files" out of curiosity). I had done this several times previously and had no issue.
I switched between windows to do something else and found myself unable to take a screenshot. I do not recall if I saved the image or not.
It occurred to me that maybe the "Save As" window was still open, but I could not find it.
I ended up closing shotr from the tray and starting it again. This is the second time I've experienced this issue.

Version info
Shotr Version: 3.0.9

It turns out that the "Save As" window was still open. I am accustomed to having an icon for the "Save As" window on the task bar, which is not the case for Shotr.


Primary link attribute?

Many apps provide a primary link (e.g. PhpMyAdmin, WordPress admin, IP address) that is the user's main destination. It looks like this link is typically put into "infoItems" array. Would it be useful to define an attribute for 'primaryLink', so it is easier to identify and highlight in a UI?

For long term flexibility, I'd prefer this be convention rather than anything directly in the schema. Apps can have multiple "primary" endpoints.

That makes sense Jimmy. Any suggestions on how to promote this convention? How would users/UI developers be able to identify these links?

A convention that might be somewhat intuitive: take the first "link" in the info items list, which might be a URL string, or a reference to a Secret or Ingress.


dynamic calls to object members on null don't work

From @jmesserly on June 21, 2016 16:47
null should support Object members (e.g. null.toString(), null.hashCode should work). If it ends up as a dcall, then we don't find the method correctly.
This may not be a dynamic helper bug ... it may be that we shouldn't have generated this call as a dynamic call. In my case it was an explicit nSM call: dynamic d; Invocation i; d.noSuchMethod(i); ... that call was generated as dsend(d, 'noSuchMethod', i) which seems wrong.
Copied from original issue: dart-lang/dev_compiler#594

From @leafpetersen on June 21, 2016 17:1
We had code that looked for object methods and made sure that they didn't end up as dynamic invocations.  I wonder if it rotted?

Yeah, that was my guess too. I thought this problem was fixed at least for things like hashCode and toString (if it's not, we'd see more breakage?). So it might be a problem with noSuchMethod, or it could be that we regressed in some other way.
As I understood it, Analyzer was not supposed to mark these as dynamic calls (because they aren't dynamic--every object in Dart supports nSM including null), and then DDC was not supposed to generate them that way. But I know we have some special code paths for Object members (to correctly handle JS null/undefined), so it could be a bug on the DDC side.
// Copyright (c) 2016, the Dart project authors.  Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.
// Dart test program testing that NoSuchMethod is properly called.

import "package:expect/expect.dart";

Invocation invocation;

class C {
  noSuchMethod(Invocation i) {
    invocation = i;
    return 42;
  }
}

// NOTE: with "Object d" here it will work correctly.
expectNSME(dynamic d) {
  try {
    d.noSuchMethod(invocation);
  } on NoSuchMethodError catch (e) {
    Expect.isTrue(e.toString().contains('foobar'));
  }
}

main() {
  dynamic c = new C();
  Expect.equals(42, c.foobar(123));
  Expect.equals(invocation.memberName, #foobar);
  Expect.listEquals(invocation.positionalArguments, [123]);
  expectNSME(null);
  expectNSME(777);
  expectNSME('hello');
  // These fail because of https://github.com/dart-lang/dev_compiler/issues/592.
  // expectNSME([]);
  // expectNSME(['a', 'b', 'c']);
}

From @leafpetersen on June 21, 2016 17:48
In lib/src/task/checker.dart we check for object methods.  I wonder if the analyzer doesn't treat NSM as a normal method?

these should all be fixed now


[JIRA] Can't select an epic while creating a ticket

Extension
https://www.raycast.com/raycast/jira
Description
Could we have a way to add an epic to a ticket when one is being created?
Who will benefit from this feature?
No response
Anything else?
No response

Isn't this already possible? There is an Epic field in the Create Issue command if the selected task type is not a subtask.

I don't see an Epic field on any of my issue types, but it's there on the JIRA web ui

Is it the case for each Jira project?

Now that I look it only happens with the EN project


Add enum classes

Summary: This change adds support for enum classes (both abstract and regular)
to the parser. These differ quite a bit from ordinary enums and each-other; so
new rules have been written for each.
Fixes #43
Test Plan:
tree-sitter test succeeds
Requirements (place an x in each [ ])

[x] I've added tests for any new code and ran npm run test-corpus to make sure all tests pass.
[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

Not sure why the validate test is failing. It seems to be running bin/generate-corpus and checking for new changes, but I cannot verify this on my end as there are no changes locally after running bin/generate-corpus.

The validate task is failing because of the changes to expressions.txt. Generally, the sort order should be stable (sort should sort alphabetically by default) but your diff indicates otherwise. It may be an issue with whitespace/hyphens in the name, and could be probably be fixed by updating
https://github.com/slackhq/tree-sitter-hack/blob/330470222a9abbaeaa09d2e7964aeb16b90b7a34/bin/generate-corpus#L18
to use the -d flag with sort. However, any insight into why your machine is using a different sort order than ubuntu and macos (where our tests run)?

ugh, I was thinking that this might be the case after that file changed. I'm using sort (GNU coreutils) 8.32 on Fedora. Will try to make it match the test machines.... somehow.

well, i fixed the issues on my end by setting LC_ALL="C". Not sure what's going on with the checks (is it also using my new LC_ALL="C" version of the script?)

The error is coming from the change that adds TSStateId *primary_state_ids - you must be running a more recent version of tree-sitter. Our package.json entry implies that we are compatible with the 0.20.X versions but perhaps we should be using ~ instead of ^. I can also try to upgrade to the more recent version.


Go back to setting page after editing category/tag name

Details

Go back to setting page after editing category/tag name
Fixed Issues

$ https://github.com/Expensify/App/issues/41339
PROPOSAL: https://github.com/Expensify/App/issues/41339#issuecomment-2092474147
Tests

Go to Settings > Workspaces and select a workspace > Categories
Tap on a category to open the setting page
Edit the category name
Verify that after editing the category name, we go back to the setting page and the category name is updated
Click on back button and verify that RHP is dismissed
Do the same steps 2-5 for tag

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

Offline tests

Same as above
QA Steps

Go to Settings > Workspaces and select a workspace > Categories
Tap on a category to open the setting page
Edit the category name
Verify that after editing the category name, we go back to the setting page and the category name is updated
Click on back button and verify that RHP is dismissed
Do the same steps 2-5 for tag

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

PR Author Checklist

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

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

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

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

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

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

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

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is 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 followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If 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.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/161821005/f26b9cde-c740-4014-8e92-4a3abade730a

Android: mWeb Chrome
https://github.com/Expensify/App/assets/161821005/a7b3bfea-168b-4926-99e1-6a5ba1d7277b

iOS: Native
https://github.com/Expensify/App/assets/161821005/343c22da-75f9-4b78-8545-9421cc384cf2

iOS: mWeb Safari
https://github.com/Expensify/App/assets/161821005/00d919b6-1718-40ba-9a3a-8131a279592c

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/161821005/154ccf7c-7309-49fa-ad6c-9e71a02ab919

MacOS: Desktop
https://github.com/Expensify/App/assets/161821005/887a4ee6-77fe-4506-9fa8-89335e538bc7

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

Android: Native
https://github.com/Expensify/App/assets/4160319/90772067-28a6-44bc-a34f-839e15e0a26d

Android: mWeb Chrome
https://github.com/Expensify/App/assets/4160319/64081b8e-89c9-4e33-bf3c-688eb66422ae

iOS: Native
https://github.com/Expensify/App/assets/4160319/779f62d9-8ea5-4103-9ead-ec6190248f01

iOS: mWeb Safari
https://github.com/Expensify/App/assets/4160319/c531634e-0b27-4c06-868b-4a51f7c5c10b

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/4160319/10770d57-86ff-4d7a-9641-8275e1fda64e

MacOS: Desktop
https://github.com/Expensify/App/assets/4160319/abf75ad1-f2e4-4bb4-8eab-f3b25a86006c

: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/blimpich in version: 1.4.74-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/chiragsalian in version: 1.4.74-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Minor Logs enhancement

Added log_relay_request config option to add relay request payload under validation error of it. This will allow mesh users to help PNI debug an ongoing issue with the stuck session height 100589.
Removed jump lines \n on the errors provided by the pocket core code. This difficult the usage of tooling like Loki that will collect a line of text before the jump line as an entry.

Close in favor of https://github.com/pokt-scan/pocket-core/pull/10 because branch name RC-0.4.1 was colliding with an old tag from pocket core


Adds basic grid functionality

Adds grid functionality and accompanying genotypic coloring/IDs to Hare, which also modifies dead behavior in the simulation. The simulation will now keep dead hares alive until they're replaced at the beginning of a new generation.

 Evo: Give hares genotypic coloring

 Evo: Tab: Hare grid generation


[SCSS] move _media-query into component partials

We need all the media query stuff move into each component or global. The media queries need to be at the bottom of each component file.

Closing for https://github.com/zurb/foundation-emails/issues/218


Migrate to Go Modules and update Travis CI pipeline accordingly

Migrating to Go Modules avoids the infamous GOPATH problem when doing forks on other username/organizations, and also it's the de-facto standard for modern Go projects. The Travis matrix has been updated starting Go Version 1.11 and release has been dropped as well.

Please @tyler-smith coudl you review this? Thanks

@tiero Sorry for the delay, it's been a busy time. I really appreciate the contribution!


SSR (Server Side Rendering)

how to use your plugin with SSR?
at the moment this is not possible, because I get the error
ReferenceError: window is not defined

Your information is not enough to know what are you doing.

@wffranco to get this error, connect the component enough

The same problem. I use nuxt with CoreUI theme.
When I try import
import navbar from './Navbar'
import { dropdown } from 'vue-strap'

export default {
  name: 'header',
  components: {
    navbar,
    dropdown
  },
  methods: {
    click () {
      // do nothing
    },
    sidebarToggle (e) {
      e.preventDefault()
      document.body.classList.toggle('sidebar-hidden')
    },
    mobileSidebarToggle (e) {
      e.preventDefault()
      document.body.classList.toggle('sidebar-mobile-show')
    },
    asideToggle (e) {
      e.preventDefault()
      document.body.classList.toggle('aside-menu-hidden')
    }
  }
}

I get error
ReferenceError: self is not defined
    at Object.defineProperty.value (/home/alex/LinWin/Develop/fb-scaner/node_modules/vue-strap/dist/vue-strap.js:1773:20)
    at __webpack_require__ (/home/alex/LinWin/Develop/fb-scaner/node_modules/vue-strap/dist/vue-strap.js:30:30)
    at Object.<anonymous> (/home/alex/LinWin/Develop/fb-scaner/node_modules/vue-strap/dist/vue-strap.js:265:2)
    at __webpack_require__ (/home/alex/LinWin/Develop/fb-scaner/node_modules/vue-strap/dist/vue-strap.js:30:30)
    at Object.defineProperty.value (/home/alex/LinWin/Develop/fb-scaner/node_modules/vue-strap/dist/vue-strap.js:59:18)
    at __webpack_require__ (/home/alex/LinWin/Develop/fb-scaner/node_modules/vue-strap/dist/vue-strap.js:30:30)
    at /home/alex/LinWin/Develop/fb-scaner/node_modules/vue-strap/dist/vue-strap.js:50:18
    at /home/alex/LinWin/Develop/fb-scaner/node_modules/vue-strap/dist/vue-strap.js:53:10
    at webpackUniversalModuleDefinition (/home/alex/LinWin/Develop/fb-scaner/node_modules/vue-strap/dist/vue-strap.js:3:20)
    at Object.<anonymous> (/home/alex/LinWin/Develop/fb-scaner/node_modules/vue-strap/dist/vue-strap.js:10:3)

:+1:  Same problem here, some components can't be rendered with SSR

@PierreRambaud Hi friend, I get the same problem, but I don't know how to solve it, can you said some details. Thanks

Vote up for issue. It is still here.

Getting the exact same error as the dropdown one above. Is there any update on this issue?
Any plans for SSR support?

Not working ssr
error during render : /
ReferenceError: window is not defined


Set path thickness

Is your feature request related to a problem? Please describe.
Path defaults to one thickness
Describe the solution you'd like
Public method to set path thickness: setThickness(value: Float)
Version
1.0.0

Closed by #10


Replace lapack with linalg

[WIP]
This PR replaces lapack usage with linalg in LinearRidgeRegression and MahalanobisDistance.
A unit test of MahalanobisDistance is added (reference computed with Matlab)

Could you pls split the PR into two: one for regression and one for the distance.
You still haven't checked whether shogun compiles with the guard remove and no lapack installed.
Pls don't remove guards without checking whether things still work: https://ci.appveyor.com/project/vigsterkr/shogun/build/1873#L6478

@karlnapf Created a new PR for LinearRidgeRegression (#4149 ). I will wait until #4130 be merged before I can continue with the refactor of MahalanobisDistance

yep, you can just force update this one now

But you will need to fix the "inverse" problem (see above) first.

@karlnapf could you plz take a look


Opening a new screen takes more time with FluidNavigator than with StackNavigator

I am experiencing a white screen which shows for roughly 2 seconds when navigating to a FluidNavigator from another screen embedded inside a StackNavigator.
If this is the incorrect way to use the library, please could you explain how I can change the code in the Snack below so that it functions without the white screen?
https://snack.expo.io/B1ZDrVbZ7

Could it be that you are doing some work in componentWillMount that causes the delay?

@chrfalch If you check the Snack you'll see it's mostly the same code from Examples/src/FlatList.js, I've just changed it so that it's embedded in a StackNavigator and the FluidNavigator is that one that is navigated to.

And thats exactly the same we're doing in the example as well. Would it be possible to use the style parameter for the fluid navigator? You can see how this is done in the ShoeShop example:
const Navigator = FluidNavigator({
  screen1: { screen: Screen1 },
  screen2: { screen: Screen2 },
}, {
  style: { backgroundColor: '#C14534' },
  navigationOptions: {
    gesturesEnabled: true,
  },
});

Not sure I'm following you exactly but I've just tried setting the background on the Snack and it doesn't seem to change anything

I'm not sure if the issue I'm seeing is a real issue ;-) Even the example app has a slight delay after clicking on the example buttons?

The library works fantastically well in terms of the the actual transitions etc, but a two second delay before the FluidNavigator loads won't be acceptable in our app at the moment. It looks like something has gone wrong with the app. If it was just a flicker/0.5 seconds it might be acceptable but it's a noticeable pause.

Ok, in the Snack provided I get around 0,5 secs, is this on Android or iOS?

I've only be able to test on iOS so far. This is a gif taken from the simulator:

It looks like it takes approx 0.5 secs? Same as I experienced running the Snack.

If I change FluidNavigator to StackNavigator I see that the speed is much better. I'll take a look and see, always happy to try to optimize the library!

Ok, well unfortunately that's still too long for our app. Thanks for your help anyway. If performance ever improves do let me know and we'll revisit the library.

(See last comment)

Thanks - it's truly a great library, am keen to use it if you manage to optimise this.

@chrfalch  any solution to this? Am also navigating to a fluidNavigator from a stack and getting a white flash.

Although it seems the code execution seems to call _interactionDonePromiseDone, the TransitionOverlayView keeps staying for 500ms before showing the screen.

Same issue here, no matter how i optimize my code. Any click wait about 0.5s animation start. The animation looks good, but why must wait 0.5s ???

In the example it looks like this is solved for the latest releases, could you check and see? @roytan883, @jskidd3, @Jonovono

in the version 0.2.74 ，I don't think this problem has been solved

in ImageListScreen.js  ，I set  image max size is 100 , click will wait about 1.5s animation start,but set image max size is 3 ,click is normal

Could be related to the fact that when you use react-navigation, screens don't unmount when you navigate away from them, but stay mounted somehow in the background until you return to them. It doesn't seem like fluid-transitions does that optimization.

Is there any update about the performance of the waiting time before the transition starts? This library is very helpful with very interesting transitions that we can implement in our production app.

@jskidd3  did you find any solution for this?
i am also facing same issue when navigating to a FluidNavigator from another screen embedded inside a StackNavigator


changelog for new release.

Prep for new release for windows support for the work @peterbom has done. Thanks heaps. ❤🙏☕

Codecov Report

Merging #177 (88964af) into master (517dcfc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #177   +/-   ##
=======================================
  Coverage   80.88%   80.88%
=======================================
  Files          11       11
  Lines         408      408
=======================================
  Hits          330      330
  Misses         50       50
  Partials       28       28

Continue to review full report at Codecov.

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


Feature request: Library size/depot estimate

While going through the grueling process of migrating my steam library to a new hard drive this morning, and trying to figure out whether or not i finally had enough room to install my whole library, I realized that a potentially useful feature for the SteamDB calculator would be something that calculates the depot size and from that, the necessary disk space for the games in your library.
With this feature, one could easily look up their library, and figure out (amongst many other findings,) whether or not they need to dedicate an entire hard drive to their video games. I realize that this would be easy for smaller, single-platform, single-language, and indie games (which have less depots in the list), but that a challenge is posed by games with multiple depots that arent used by every user. Depots that would be commonly unused are ones for other platforms (since windows, osx, and linux depots are listed separately), and ones for other languages. To prevent calculating depots that are unused, If this feature is added, choices similar to the currency type choice involving OS/platform and language should be used so that viewers can read the size of just what they need. these choices should only affect the size calculations, as one might still want to know the price of all games, but only know the size of what they can install on linux, for example. Additionally, It would probably need a disclaimer that such a feature only calculates install size, not any addons, since commonly modified games such as Garry's Mod and Skyrim can obviously grow well past their install size.

You're also forgetting DLC depots, and depots that are only owned by certain packages. So doing this in calculator won't work, we would need to get your owned packages and work it out from there, but it's not worth the effort.


Submodules with the same folder name are indistinguishable in the source control view

VSCode Version: 1.25.1
OS Version: Windows 10.0.17134.165 x64

Steps to Reproduce:

Execute:

#!/bin/bash
set -xe

git init submod-a
cd submod-a
echo "Hello, World!" > hello.txt
git add hello.txt
git commit -m "Initial Commit"
cd ..

git init submod-b
cd submod-b
echo "Hello, World!" > hello.txt
git add hello.txt
git commit -m "Initial Commit"
cd ..

git init main
cd main
mkdir a b
git submodule add ../submod-a a/submod
git submodule add ../submod-b b/submod

Open in VS Code and look at the Source Control view, you will see two entries named "submod" indistinguishable from one another.

Does this issue occur when all extensions are disabled?: Yes
Screenshot:

/duplicate #40548


Issues/consistent name changes

These changes area a result of running the new checkstyle rule from this PR.
I did not want to pollute the other issue with all these name changes.

Can you add suppression rules to ignore files in implementation packages or test packages? We can keep the PR small to start with and focus on public API only.

Can one of the admins verify this patch?

Sounds good. I'll close this one and re-run it.


Fixed naming convention

Description
Corrected naming convention by adding StepFunctions to all headers
Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

@davsclaus Opened this PR to use camel standard naming convention as suggested here: https://github.com/apache/camel/pull/11053#issuecomment-1670826751

I added a file to main branch
docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_1.adoc
Can you add a new section to this page
=== camel-aws2-step-functions

Write something here about header names changed to be following Camel naming convention.
Maybe we a little example


#122 Added an index for announcements

Added an index to #122

Index has been added by @amiedavis


ClearHistoryAndReset action crashes Contour if status line is on

Contour Terminal version
0.3.8-master-2fe41bba
Installer source
Github: source code cloned
Operating System
Devuan Linux (Ceres)
Architecture
x86-64
Other Software
No response
Steps to reproduce

add  - { mods: [Control],        key: L,             action: ClearHistoryAndReset } to config
press Control+Alt+.
press Control+L

Expected Behavior
Don't crash.
Actual Behavior
Contour crashes.
Additional notes
No response

Wiow. nice. Thanks.

What is this Control+Alt+. combo in the reproduction steps?

ok i get it. it's the default binding to toggle the statusline.

[2022-12-13 17:00:40.808269] [gui.input] Character press event received: Control L
[2022-12-13 17:00:40.808291] [gui.session] executeAction: UNKNOWN ACTION
[2022-12-13 17:00:40.808295] [gui.session] Clearing history and perform terminal hard reset
[2022-12-13 17:00:40.808314] [vt.grid] resize 80x23 -> 80x24 (cursor (0, 0))
[/home/runner/work/contour/contour/src/terminal/Grid.cpp:454] Precondition failed. 0 <= *_margin.vertical.from && *_margin.vertical.to < *pageSize_.lines
[2]    83255 abort      contour debug '*'

It crashes  on void Terminal::hardReset() call at this line
https://github.com/contour-terminal/contour/blob/9093500f1a443e150b5c943e1a3a2fad130e2fd4/src/vtbackend/Terminal.cpp#L1626
It caused by the fact that status line is deleted from the lines and  validation of margins  *_margin.vertical.to < *pageSize_.lines fails.
If i will comment out   hostWritableStatusLineScreen_.clearScreen();  and then few times repeat
press Control+Alt+.
press Control+L

I will end up with the following situation

where some lines on the bottom not accessible anymore

After #914.
Repeat several times:

press Control+Alt+.
press Control+L

The height decreases each time.

I am still getting this crash.

I am still getting this crash.

Interesting. Let me check.

I think we can now finally close this, right?

I have only one question: why does this action turn off the status line?

I have only one question: why does this action turn off the status line?

Not on master. And not anymore. Reset is actually a hard reset. Check the discussion board.

Not on master.

Yes, on master.

Not on master.

Yes, on master.

Sorry, than it's not configured to be initially visible in your configuration file, can that be? Because RIS is resetting back to that.
I'm trying to mostly obey to what https://vt100.net/docs/vt510-rm/RIS.html is mandating, at least as much as possible and as much as we've actually implemented the features that need to be reset.

I meant after pressing Control+Alt+. and Control+L the status line should be stay on.

I meant after pressing Control+Alt+. and Control+L the status line should be stay on.

That's exactly the point. ClearHistoryAndReset is currently doing a hard reset, and therfore also resetting the statusline state to its initial state. Hiding it then is therefore intentionally for the RIS at least. If ClearHistoryAndReset is not meant to do a hard reset, then we must redesign this action. That's what I was trying to induce over at #921.

Can we close it ?

I suppose I can close it now


Nuxt js Require help to do unit test using mocha, chai and karma

Nuxt js Require help to do unit test using mocha, chai and karma

This question is available on Nuxt.js community (#c1624)

why is this issue closed ?
is there a way to do unit test !? It is impossible to find any documentation. how can i use the framework  which has no unit test support to run a production programe ?