text:
DOCS: Second new folder, article rewrites, article renaming, redirects, and new articles

Details

Fixed Issues

$https://github.com/Expensify/App/issues/36581
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

[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 / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

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

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

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

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

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

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes

[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)

[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

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

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

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

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

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

Screenshots/Videosundefined

Resolved conflicts

@rushatgabhane can you grab the checklist?

This one has conflicts now - do you think you can get that settled @ren-jones and we can fix this one up! Just waiting on that and the reviewer checklist too (if you can handle that @rushatgabhane)

Conflicts resolved! @dangrous @rushatgabhane

Reviewer Checklist

[ ] 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 included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] 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 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
[ ] 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 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 */
[ ] 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 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.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

🚀 Deployed to staging by https://github.com/dangrous in version: 9.0.7-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Cherry-picked to staging by https://github.com/thienlnam in version: 9.0.7-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

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

🚀 Deployed to production by https://github.com/thienlnam in version: 9.0.7-8 🚀

platform
result

🤖 android 🤖
failure ❌

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 9.0.8-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

authors: OSBotify dangrous ren-jones


text:
Update Custom-Templates.md

Details

Adding FAQ and a common question
Fixed Issues

$
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

[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 / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

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

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

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

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

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

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes

[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)

[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

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

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

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

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

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

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

A preview of your ExpensifyHelp changes have been deployed to https://03ded1f9.helpdot.pages.dev ⚡

looks good

https://03ded1f9.helpdot.pages.dev/articles/expensify-classic/spending-insights/Custom-Templates

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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

🚀 Deployed to staging by https://github.com/bondydaa in version: 9.0.40-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

source: gharchive/pull-request

authors: OSBotify bondydaa sonialiap

repo: Expensify/App

license: MIT

license_type: permissive

license_source: github-api


text:
[No QA] Update remaining e.cash usages w/ New Expensify

Details
While investigating Firebase logs for another issue, I noticed that we're still using e.cash when logging for the ErrorBoundary component, so I went through and updated the remaining usages in the codebase.
Tests/QA
None, this just updates readme and comments

: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 production by @roryabraham in version: 1.0.92-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


text:
Update logback-classic to 1.4.5

Updates ch.qos.logback:logback-classic from 1.2.11 to 1.4.5.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.qos.logback", artifactId = "logback-classic" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "ch.qos.logback", artifactId = "logback-classic" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #634.

repo: ExposuresProvider/cam-kp-api


text:
Bug Fix Background Removal Nullability crash

Hello I fixed some of bugs. Especially BackgroundRemoval class line 39 give us crash. So I replaced all of the force unwraps with guard lets and making optional some of code.

Thanks for your contribution, looks good


text:
Error: Cannot find module '../utils'

ithome 也是打包错误，
Error: Cannot find module '../utils'

这个修复过了，还没发版本

已发布 v0.1.8

source: gharchive/issue

authors: F-loat appbest

repo: F-loat/mpvue-packager


text:
catalog-editor generates invalid WGS84 bbox

(original discussion here)
Original bbox:
      "x": {
        "axis": "x",
        "extent": [
          900000,
          7400000
        ],
        "reference_system": "3035",
        "type": "spatial",
        "unit": "metre",
        "step": 10
      },
      "y": {
        "axis": "y",
        "extent": [
          900000,
          5500000
        ],
        "reference_system": "3035",
        "type": "spatial",
        "unit": "metre",
        "step": -10
      },

The catalog editor generates a max lat coordinate 58.95275, but the correct one is 72.66. This is likely because it transforms individual coordinates which is incorrect. This can be verified with gdaltransform:
$ gdaltransform -s_srs EPSG:3035 -t_srs EPSG:4326
Enter X Y [Z [T]] values separated by space, and press Return.
7400000 5500000
72.906136759009 58.9527510923263 0

It gives 58.952 like the catalog-editor and not 72.66.
The correct way is to transform the whole bbox, e.g. with gdalwarp:

Create a bbox_epsg3035.vrt file with content

<VRTDataset rasterXSize="650000" rasterYSize="460000">
  <SRS>EPSG:3035</SRS>
  <GeoTransform>900000, 10, 0, 5500000, 0, -10</GeoTransform>
  <VRTRasterBand dataType="Byte" band="1">
    <NoDataValue>0</NoDataValue>
    <SimpleSource>
      <SourceFilename relativeToVRT="1">dummy.tif</SourceFilename>
      <SourceBand>1</SourceBand>
      <SourceProperties RasterXSize="1" RasterYSize="1" DataType="Byte" BlockXSize="1" BlockYSize="1"/>
      <SrcRect xOff="0" yOff="0" xSize="1" ySize="1"/>
      <DstRect xOff="0" yOff="0" xSize="1" ySize="1"/>
    </SimpleSource>
  </VRTRasterBand>
</VRTDataset>

put whatever dummy.tif file in the same directory, it's irrelevant because all information is in the VRT file, but it's required.
check the bbox with gdalinfo:

Origin = (900000.000000000000000,5500000.000000000000000)
Pixel Size = (10.000000000000000,-10.000000000000000)
Corner Coordinates:
Upper Left  (  900000.000, 5500000.000) ( 56d30'18.51"W, 56d29' 4.75"N)
Lower Left  (  900000.000,  900000.000) ( 23d49'33.58"W, 24d17' 3.04"N)
Upper Right ( 7400000.000, 5500000.000) ( 72d54'22.09"E, 58d57' 9.90"N)
Lower Right ( 7400000.000,  900000.000) ( 40d39'45.75"E, 25d32'40.96"N)

reproject the file:

gdalwarp -t_srs EPSG:4326 -of VRT bbox_epsg3035.vrt bbox_epsg4326.vrt

check the result bbox with gdalinfo bbox_epsg4326.vrt:

Origin = (-56.505141901704370,72.663269668344356)
Pixel Size = (0.000128060211603,-0.000128060211603)
Corner Coordinates:
Upper Left  ( -56.5051419,  72.6632697) ( 56d30'18.51"W, 72d39'47.77"N)
Lower Left  ( -56.5051419,  24.2841707) ( 56d30'18.51"W, 24d17' 3.01"N)
Upper Right (  72.9061049,  72.6632697) ( 72d54'21.98"E, 72d39'47.77"N)
Lower Right (  72.9061049,  24.2841707) ( 72d54'21.98"E, 24d17' 3.01"N)

The reprojection is done on the client side, using a library reproject-bbox which is using proj4 as it's dependecy.
I'm aware with the distortion related shift in coordinates near (lat 60, -60) from/to WGS84, I tested some wms samples ( in our backend case, and it was fine).
I'll do  more invistigation and see what it is can be done in this case.

Any updates?

Hi @baloola, any update on this issue? I have pushed a couple of md records that use the Austrian projection, but the leaflet map shows something else:

authors: KathiSchleidt baloola mari-s4e misev

repo: FAIRiCUBE/catalog


text:
UnhandledPromiseRejectionWarning

Node: 8.9.1
When doing a commit on my local instance, the flow server returned back this error.
yarn run v1.1.0
$ yarn lint && flow && jest --coverage

Launching Flow server for /home/daniel/Development/F3C_Website
Spawned flow server (pid=14983)

Logs will go to /tmp/flow/zShomezSdanielzSDevelopmentzSF3C_Website.log
No errors!
No errors!
(node:15179) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Cannot find module '/home/daniel/Development/F3C_Website/node_modules/jest-cli'
(node:15179) [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.
Done in 34.82s.

We may want to nip this in the butt and make sure we're handling the returned promises

@DanStockham is this bug still present?

license: mit

license_source: bigquery


text:
ARGOS and GlyGen DB Updates: Advanced search for targeted searching

From Jeet
This advanced option will allow to search based on categories. E.g A word can be searched in the dataset name/BCO name or in the content of the dataset/bco. It can have a option to select an organism or a file format.(having and / or operators) For eg. search the keyword glycohydrolase in human (9606). The advanced targeted search can be similar to the one implemented in GlyGen Protein Advanced Search - https://www.glygen.org/protein-search/, having multiple fields to narrow down search. We can few fields and or categories to begin with.

This is a lot of work, and the need for it has to be justified --> meaning, you have to come up with a use case that cannot be achieved by what we have now. One can search for "glycohydrolase" and use the "human" filter to achieve the use case mentioned here.

@rykahsay I will backlog this and leave it as an item to discuss for ARGOS at a later date with Raja.

authors: rykahsay steph-sing


text:
Add Flu section to the paper

A section of the paper will highlight the flu orgs that are included in ARGOS. Highlight how our QC metrics can. be further applied to other emerging pathogens. Apply our QC metrics and understand the quality of the assembly will be needed to be done before writing the paragraph

Flu section has been updated. Adding more information on how the assemblies were chosen and why.

Section has been added and updated. Will continue to work on the paper


text:
Add Instructions for updating the Robot Controller version for Android Studio users.

The current page for updating the RC app (https://ftc-docs.firstinspires.org/ftc_sdk/updating/rc_app/Updating-the-RC-App.html) includes instructions for both OnBot Java and Blocks, but has no instructions for Android Studio.
It is mentioned that the steps shown are not for Android Studio users, and that teams should ensure their projects are up to date with the main SDK repository. However, there are no actual instructions or resources given to accomplishing that. Certainly, some teams will have members skilled enough in Git and VCS to accomplish it on their own, but those aren't the students who are reading these guides. Aside from community resources, there is no easy way for a team to find help on this process.
With that being said, it is hard to give concise instructions for updating the SDK version given that each user's circumstances may vary. However, even a simple guide, such as using a couple very simple Git commands, or using the Github Desktop GUI, would go a long way to making Android Studio easier to use for more teams.

Thanks for the feedback. A guide to updating the RC for Android Studios users is certainly something that we would like to add.

Craig added a guide a few months back, but I realize it might not be 100% clear that the guide exists. I changed some of the wording on the "Updating-the-RC-app.html" page to better clarify that the guide exists, and that users of Android Studio should check it out for its intended use. I'm hoping this helps out, please let me know if you feel it is still lacking. We agree that it's impossible to give concise instructions because of the different configurations and user circumstances, but I feel like the guide provides education and a quick-start that should help the vast majority of teams who "take it seriously."
#180 should resolve this issue.

Sorry for leaving this dormant; linking to that guide is great! I wasn't fully aware of its existence before either.
As a side question, I've personally made my own team's repos both with forking it and also cloning the SDK, with my personal preference being towards cloning since that makes the project more isolated (although updating the SDK version requires some extra Git commands). For example, people accidentally submitting PRs to the official SDK repo is not as easy.
Is there a reason why the forking method is preferred here? I don't have any problems with it; both methods are similar amounts of steps and achieve basically the same outcome, but I was wondering the ethos behind that.

The Forking method is vastly preferred because a clone is generally not sharable within a team - cloning makes a local copy of the repository, NOT your team's own copy. If there are multiple remote users (users who are not sitting at the single computer) who will collaborate with you on writing your team's code, you cannot do that from within a clone of a repository. Clones of a repository are just for you. Clones are beneficial if you're planning on contributing to the repository, but since teams ARE NOT ALLOWED to push changes back up to the FtcRobotController repository, this benefit is of no use. It's true that clones are specifically linked to the repository, whereas Forks are not, but we provide instructions on how to set the upstream remote so that you can sync from the FtcRobotController repository from a clone of your forked repository. There is no way to "save" a local repository, if someone deletes the local clone or the computer is lost or trashed, you lose all of your work (clones are only managed locally, not from GitHub or similar). The only real "backup" of your code is from a forked repository.
For FTC teams, each team should have their own forked repository owned by a GitHub account managed by the team. Each collaborator within the team should clone the team's forked repository using their own accounts, work on code, and commit/push back to the team's repository. When updating the team's repository with changes from the FtcRobotController, that should be managed from a clone of the team's repository and submitted back to the team's repository via a PR. In this way, multiple users can collaborate on code AND the result of that collaboration is actually stored/saved in the cloud. When the laptop is reformatted or the main programmer graduates, the code doesn't disappear.

I may have spoke a bit weirdly regarding the cloning method. That method involves making a local clone (either through cloning the SDK repo directly or downloading as a ZIP) and then changing the "remote origin" URL to a repository of your creation. Example from my GitHub desktop of 1002's PowerPlay project.

rough process:

Clone the official SDK (download zip or git clone)
Create a repository on github
Change the remote origin to the URL of your newly created repository
Push to the new repository.

This leaves no connection back to the official SDK, except when you need to add it as a remote upstream location in order to merge from for SDK updates (in the same way used for forks). This is the method me and lots of other teams use instead of forking.

Oh, I see. Yeah, that's one way to create a clean "copy" that guarantees that you don't accidentally push back to the FtcRobotController repo. But this is only a workaround to GitHub's inability to provide a reasonable solution.
For instance, it would be awesome if we could create a template repo that can be updated with changes, OR if we could specify (like Gitea does) that nobody (without administrator access) is allowed to submit PRs. But unfortunately GitHub is dumb like that.
One cool alternative that GitHub has come up with is called Detaching/Extracting a Fork. They've created a fun little chatbot that can help you detach/extract a fork, so that it removes the fork from the repo network and puts it into a new one. This really should be a Git command, but alas I understand Git saying, "no, not my perfect little princess!" But, with this tool you can go ahead and create the fork like we say, and then use the Detach feature to "pluck" it from the network and keep your safety/sanity. But I wouldn't recommend this to a casual user - but you seem like you can handle it.

authors: Lunerwalker2 texasdiaz uvidyadharan

repo: FIRST-Tech-Challenge/ftcdocs


text:
区块同步失败

问题：三个共识节点中有一个始终低一个块，无法同步到
BCOS版本：2.8.0
节点：三个共识节点
信息：10.244.228.88:30300 为高度低的节点
warning|2024-01-30 14:12:21.547667|[NETWORK][Session][drop] shutdown failed ,errorValue=9,message=Bad file descriptor
info|2024-01-30 14:12:24.937780|[NETWORK][Host]Connecting to node,endpoint=tsca-oms.sf-express.com:30300
info|2024-01-30 14:12:24.937868|[P2P][Service] heartBeat,connected count=1
info|2024-01-30 14:12:24.940362|[NETWORK][ASIO]asyncResolveConnect,endpoint=10.244.228.88:30300
info|2024-01-30 14:12:24.953370|[NETWORK][Host]handshakeClient succ,local endpoint=10.244.228.89:18956
info|2024-01-30 14:12:24.953410|[NETWORK][Host]startPeerSession, Remote=10.244.228.88:30300,local endpoint=10.244.228.89:18956,nodeID=cea6583a...
info|2024-01-30 14:12:24.953488|[P2P][Service] Connection established,nodeID=cea6583a...,endpoint=tsca-oms.sf-express.com:30300
info|2024-01-30 14:12:24.954391|[NETWORK][Session]Received topic: [222  _block_notify_70        _block_notify_72] from cea6583a6694e439d34164d0d524c22fad133b58a6816f478b43ba9f4423064a55af8aa0434b4cdab0d7832921e119b19aebb82262ec40e06db0797645c83352
info|2024-01-30 14:12:30.975312|[NETWORK][Host]P2P Recv Connect, From=10.244.228.88:18644
info|2024-01-30 14:12:30.975448|[NETWORK][Host]P2P StartAccept,Host=0.0.0.0:30300
info|2024-01-30 14:12:30.986731|[NETWORK][Host]handshakeServer succ,remote endpoint=10.244.228.88:18644
info|2024-01-30 14:12:30.986794|[NETWORK][Host]startPeerSession, Remote=10.244.228.88:18644,local endpoint=10.244.228.89:30300,nodeID=cea6583a...
info|2024-01-30 14:12:32.355885|[g:72] [SYNC][id:34d598dd...][Download][Request]Receive block request,peer=cea6583a...,from=26541,to=26541
info|2024-01-30 14:12:32.906455|[g:72][SYNC][id:34d598dd...][Download][Request][BlockSync]Batch blocks for sending,blockSize=324008736,number=26541,peer=cea6583a...,timeCost=550
info|2024-01-30 14:12:34.728326|[g:72][g:72] [SYNC][id:cea6583a...][Rcv][Send][Download]Block back,peer=cea6583a...,blocks=1,bytes(B)=324008747
warning|2024-01-30 14:12:34.730295|[NETWORK][Session]onWrite error sending,message=Broken pipe,endpoint=tsca-oms.sf-express.com:30300
info|2024-01-30 14:12:34.730334|[NETWORK][Session]drop, call and erase all callbackFunc in this session!,endpoint=tsca-oms.sf-express.com:30300
warning|2024-01-30 14:12:34.730350|[NETWORK][Session][drop] closing remote 0.0.0.0:0,reason=Low-level TCP communication error.,endpoint=tsca-oms.sf-express.com:30300
warning|2024-01-30 14:12:34.730424|[P2P][Service] disconnect error P2PSession,nodeID=cea6583a...,endpoint=tsca-oms.sf-express.com:30300,errorCode=3,what=Disconnect
warning|2024-01-30 14:12:34.730466|[P2P][Service] onDisconnect,errorCode=3,what=Dynamic exception type: dev::network::NetworkException
std::exception::what: Disconnect

怀疑应该是区块太大导致，但是如何恢复正常？

出现：warning|2024-01-30 14:51:56.446276|[NETWORK][Session]Illegal p2p message packet,length=227179746,maxLen=104857600
error|2024-01-30 14:51:56.446307|[NETWORK][Session]Decode message error,result=-1

怀疑应该是区块太大导致，但是如何恢复正常？

warning|2024-01-30 14:51:56.446276|[NETWORK][Session]Illegal p2p message packet,length=227179746,maxLen=104857600
error|2024-01-30 14:51:56.446307|[NETWORK][Session]Decode message error,result=-1

Batch blocks for sending,blockSize=324008736,number=26541,peer=cea6583a...,timeCost=550

从日志的这句来看区块26541有324MB，而P2P发送的消息包限制100MB，可以修改MAX_MESSAGE_LENGTH这个常量为300MB，之后编译一个节点二进制

怀疑应该是区块太大导致，但是如何恢复正常？

warning|2024-01-30 14:51:56.446276|[NETWORK][Session]Illegal p2p message packet,length=227179746,maxLen=104857600
error|2024-01-30 14:51:56.446307|[NETWORK][Session]Decode message error,result=-1

Batch blocks for sending,blockSize=324008736,number=26541,peer=cea6583a...,timeCost=550

从日志的这句来看区块26541有324MB，而P2P发送的消息包限制100MB，可以修改MAX_MESSAGE_LENGTH这个常量为300MB，之后编译一个节点二进制

ok，我试试，谢谢

已解决，谢谢

repo: FISCO-BCOS/FISCO-BCOS


text:
Update configModal.tsx

Remove extra parentheses

@txtwork Is this required? I'm not understanding the purpose.

@txtwork Is this required? I'm not understanding the purpose.

haha, it will appear here

@txtwork Whoops thank you!!


text:
FLAMEGPU on ShARC docs: no mention that libxslt is dependency but not installed

See http://docs.hpc.shef.ac.uk/en/latest/sharc/software/libs/FLAMEGPU.html
Also, should these docs recommend using a particular git tag rather than the HEAD of master?

It appears libxslt is installed on Iceberg but not ShARC, so I assume these instructions are based on previous instructions for Iceberg?  ( @mondus )
The HEAD of master represents our latest release, with other branches / tags generally being WIPs.
The next major version which we are currently working on (1.5.0) will include improved linux support, although xsltproc and therefore libxslt will still be required.
On windows we ship xlstproc.exe with FLAME GPU (see the tools directory) but had found that xsltproc has typically been available by default on desktop linux distributions.

@willfurnass How do you suggest we resolve this? Do we request that xsltproc is made available on ShARC (as it is on icerberg) or do we simply update the documentation to point users to a compatible source of xsltproc to transfer to ShARC
We will also want to update the docs.hpc.shef.ac.uk site to reflect the instructions for building and using on sharc.

Having discussed this with Will, a request is being made for xsltproc to be installed on ShARC, as it is on iceberg.

The libxslt RPM, which provides xsltproc, will be rolled out across ShARC's worker nodes over the next hour or so.

Cheers @willfurnass.
I have now verified that FLAME GPU examples can be built from the release-1.5 branch via:
module load dev/gcc/4.9.4
module load libs/CUDA/8.0.44/binary

git clone git@github.com:flamegpu/flamegpu.git
cd flamegpu
git checkout release-1.5
cd examples/GameOfLife
make console

I have not tested the EXE runs, as no GPUs are currently available, but I am confident it will work.
I'll close this issue, and add updating that document to the post-1.5 release tasks issue.

authors: ptheywood willfurnass

repo: FLAMEGPU/FLAMEGPU


text:
XML Output does not contain the environment variables

When an XML output state is written is does not write environment variables. Not sure if it should. It might depend on if they were specified within the original input file or set at run-time by an init function. I suspect that these should be output to make the whole simulation process stateful.

This needs to include support for vector types from #160.
A new feature branch can now be created from release-1.5 to implement this.

authors: mondus ptheywood


text:
Adding of Fosscu calendar in the navbar

I have added the Calendar of Fosscu community in the Navbar which can be now easily accessible by all.. @Mr-Sunglasses
https://user-images.githubusercontent.com/108119109/236628463-c26ec178-87c9-474f-9be1-0ddd853f7133.mp4

@Bharadwajshivam28 Hi there! There are quite a few sections to the navbar, and it's starting to look a bit cluttered. Have you considered using a dropdown menu in the sidebar instead? This would allow you to add additional sections without cluttering the navbar, and it would also make it easier for users to find the sections they're looking for.

@Bharadwajshivam28 Hi there! There are quite a few sections to the navbar, and it's starting to look a bit cluttered. Have you considered using a dropdown menu in the navbar instead? This would allow you to add additional sections without cluttering the navbar, and it would also make it easier for users to find the sections they're looking for.

Yes I also think that we should have a dropdown for the other items in the navbar, It'll Improve the Overall UI of the Website.

@anshika0987 fixed it so I'm closing the PR

repo: FOSS-Community/website-fossc


text:
[Feature Request] Configuration generator for web servers

We could create a basic web app that generates minimal configuration files for different web servers. I've seen many people being confused while setting up FOSSBilling on their nginx servers, so this might help them a lot.
I also made a mockup:

Current example config should be fine:
https://github.com/FOSSBilling/FOSSBilling/blob/0a1523b06fd108d154260a729e6d36211f53f5cd/data/nginx.conf#L23
How ever this line of code should be changed why the user

It's a nice idea.
Are you thinking about just nginx or adding other servers as well?

Likely others too

Since this is now up at https://config.fossbilling.org/ - can this issue be closed? @evrifaessa

Since this is now up at https://config.fossbilling.org/ - can this issue be closed? @evrifaessa

yes, of course. thanks for the reminder :)

authors: John-S4 evrifaessa jaapmarcus

repo: FOSSBilling/FOSSBilling


text:
Update requirements.txt

Add codetext parsers into dependencies

LGTM!


text:
Dropper Limit Switch

Dropper limit switch will be ready for use today (Mar20), so we can add it to the tele-op and auto
Tele-op so that when you press RB, it will collect (placer to store and dropper to collect) until the limit switch is pressed, then move back to the brace state and stop intaking.
Pressing RB again during this will cancel the action and return to brace
Adding it to the auto so that it collects until the switch is pressed would also be a good idea

What happens if the limit switch doesn't get pressed?  Does the dropper spin forever?

Duplicate #23


text:
Ping System

Since K9 has been removed we could use a replacement for its ping system.
As a reminder, the ping system for k9 was essentially that you could register an arbitrary regex, which k9 would run on every message and if it matched send you a DM with a link to the message that triggered it.
I would recommend the following restrictions, compared to what k9 had:

Only works in channels that the user (maybe even @everyone just to be safe?) can read
Pings are essentially just input.toLowerCase().contains(ping.toLowerCase()), no regex involved
Pings should have a minimum length and/or a maximum amount of triggers per unit of time, to avoid situations where someone wants a ping any time the letters e or t are used in a message, or is otherwise burdening the bot.

This is actually a fairly decent idea, honestly. I was going to use RE2 for safer regexes, but that'd still be fairly burdensome — and it's pretty much only a niche requirement.
This will have to come after the database rewrite, though.

To be honest, I disagree with the restrictions proposed. A regex expression has proven to work with the previous bot, even if people set ridiculous pings such as /./. Also, although a cool-off period may seem appealing, it would have to be configurable by users, but that that point its easier to just send every message through. I'd rather have 7 pings overnight and reply to each one, than only get 2 and miss the other 5

I dont think we really need this feature, feel free to disagree with me, but I feel like it was used to "alert" people to possible drama/whatever so they can chime in their view.

Most people has pings for their names, or projects they worked on.

In this extract of the original pings dump, there's only two which looks kind of suspicious, but nothing drama related

My intention wasn't for only getting two pings if your project was
mentioned a bunch, but instead as a filter to avoid abuse. The idea is that
to 95% of the users it feels exactly the same
On Tue, Nov 17, 2020, 2:25 PM ramidzkh notifications@github.com wrote:

Most people has pings for their names, or projects they worked on.
[image: image]
https://user-images.githubusercontent.com/19631324/99443356-d1ec5580-296e-11eb-86d9-ba33e5898b00.png
In this extract of the original pings dump, there's only two which looks
kind of suspicious, but nothing drama related
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/FabricMC/fabric-discord-bot/issues/21#issuecomment-729181116,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEU6AEAQUMK5ALOCRBAAXQ3SQLL4XANCNFSM4TXO4MIA
.

The main possible issue I see with it is that inconsistent spacing may mean you miss out on someone mentioning something
If I have project A B-C but someone says AB-C, I don't receive a ping, and trying to build the "simple" system to accommodate all the possible variations is bound to lead to issues
With a regex based system I can simply match 0 or more spaces and not miss any messages that should ping, or similar misspellings

I agree with ramid, the system has the most use in knowing when projects you work on are being discussed - like if a user has a question about something. Fabric isn't so small everyone knows who did what project and can send a ping their way when they are needed.
If the fear is drama, you could make it more curated, but I see no reason to increase the moderation burden and place a barrier to the system.

repo: FabricMC/fabric-discord-bot


text:
Fix

Fixed #1

no thooo


text:
Company Import - Genius ITR

sample sheet

Name => Company Name
PAN => Required
AADHAAR => Company Custom Field
GSTIN => add if possible
DOB/DOI => Company Custom Field
Address => Company Address
Mobile => Contact Mobile
Email => Contact Email
Salary => Not sure what to do
Form No => ITR-Return Service Link
Covered under Tax Audit => if "Yes" Tax-Audit Service Link

Ignore row if PAN is Missing

All Software Imports are just for adding new Company, Editing existing companies are not supported
Verified / Approved over phone with @vinpahilwani / @sureshsirvi

for all Software Import
Discussed behavior
Company =>
if GST is provided =>
Save PAN and GST both
append pan if not present
create new if gst pan not matching / gst is different
1st priority check of gst
2nd pan
3rd name
Contact =>
create new if
Phone or email not matching
1. check phone
2. check email
3. check exact name

Fresh import working correctly, all done

When there is number in company name, then contact name will be firstname lastname

authors: Avinash-ecb mitulpanch

repo: Fammeo/EasyCloudBooks


text:
Account Page - Save Date range in Detail Page

save date range to page variable
by @ashokbhurani

agar koi account ke details pe daterange set koya to save rahega
dusre account pe close karke kholne pe wahi date range continue rahega
page reload pe refresh ho jayega


text:
Feature request: force days per row

Right now, week-planner-card seems to base the number of days shown on available width. It would be useful to force n days per row, for times when I want it to always display, say, exactly one week.

good idea, for now here is workaround
card_mod:
  style: |
    .container {
      flex-wrap: nowrap !important;
      justify-content: space-around;
    }

The reason it's done using the available width is because if there's not enough space it won't look right. I'd rather not add a configuration to enable this. It can already be achieved using card_mod, which makes sure only people who know the risks will do this.

authors: FamousWolf sparky-vision tasiotas

repo: FamousWolf/week-planner-card


text:
PoS balances store

Merkle trie StateDB for PoS balances storing (adapted implementation from go-ethereum).
If OK, next steps will be:

PoS balances changing by internal transactions;
PoS balances using to detect majority;

This pull request has copied a lot of code from go-ethereum project, so it should be corrected to use it as imports instead of copying it.

repo: Fantom-foundation/go-lachesis


text:
Unnecessary dependencies

Hi
Your component lists two dependencies (react, mathjax). I belive you should remove both dependencies, as MathJax is available via the script import (and so doesn't require any local files) and react is already listed as peer dependency, which is the better choice.
I removed those dependencies and your component still works perfectly, as long as there is react in the project (as peer).

@poiuqwer78 sorry for delay,
should be solved now


text:
The autocomplete list doesn't appear

Please help me.
I can't see the autocomplete list that appears when I enter a search.

@mnurulhuda Please follow the issue template to show the code you are using or link to a snack.

I tried to use basic example with a configuration that I have adjusted, but cannot display autocomplete

@mnurulhuda Please follow the issue template to show the code you are using or link to a snack.

👆

React Native Google Places Autocomplete not loading auto complete list
Steps:

Create a fresh project using react-native init
add react-native-google-places-autocomplete
used following example
Added API_KEY
Search bar appears, But nothing happens when you search

@sacmii when I follow your steps it works fine for me.
Can you try using this snack, or link to your own?
Check the console there to see if there are any errors with your key.

@sacmii when I follow your steps it works fine for me.
Can you try using this snack, or link to your own?
Check the console there to see if there are any errors with your key.

No errors are logged

@sacmii can you provide a link to a snack so I can try and reproduce?

can you provide a link to a snack or a repository so I can try and reproduce?
I just tried on the example provided by you https://snack.expo.io/@sbell/react-native-google-places-autocomplete and filled in my API key wich I created like specified here https://developers.google.com/places/web-service/get-api-key and got no suggestions at all. Am I missing something?

@JakubOrsula without a fully reproducible example, I have no way of knowing.
If something is not working for someone, please provide all the code you are using or link to a snack.
The GitHub issues should really be for bug reports, not for support. That being said, if someone is having an issue using the library (no a bug in the library), I don't mind helping out, but I have to have the information needed to help (a proper repoducible example).
This is an open source library, not a commercial project with a support team.

please provide all the code you are using or link to a snack.

@bell-steven This is the link to the snack. https://snack.expo.io/@sbell/react-native-google-places-autocomplete
I just set GOOGLE_PLACES_API_KEY to my api key. Upon typing in search bar in the preview on the right no suggestions come up.
I do believe that this is a bug since it affects multiple people and is reproducible.

@JakubOrsula that is my snack.  I just tied my API key with it and it works without any issues.  I also use it in an app in production without issues.
I'm going to close this because it is not a reproduble bug.  If someone wants to open a new issue and follow the issue template, I would be glad to take a look.

Hello,
I'm sorry the problem was on my end.
@mnurulhuda maybe this can help you.
For future reference the steps I've taken to narrow down the problem:

I tested just the key like described here https://developers.google.com/places/web-service/get-api-key#add_key
There were some problems like browser auto-inserting url-encoded '\n' characters making google return 404
When I finally got meaningful response (Billing not set up go to ...) I just enabled billing.
And that was it! The core problem was that billing was not enabled.

@JakubOrsula that is my snack (bell-steven = sbell 😉 ). I just tried 2 API keys with it and it works without any issues. I also use it in an app in production without issues.

I do believe that this is a bug since it affects multiple people and is reproducible.

That may very well be true. Or perhaps it has to do with the API key and nothing to do with the library. Maybe people aren't following the instructions properly. Maybe the docs need to be more clear. Saying "it doesn't work" isn't very helpful.
I'm going to close this because it is not a reproducible bug or usage issue. If someone wants to open a new issue and follow the issue template, I would be glad to take a look.

My API key doesn't work. i follow the instructions carefully. What do i missing ?

any update why google key is not working , i already enabled the Places API ...

can try another api key and check whether the billing is enabled or not
On Wed, Nov 11, 2020 at 9:53 PM Salman Memon notifications@github.com
wrote:

any update why google key is not working , i already enabled the Places
API ...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/FaridSafi/react-native-google-places-autocomplete/issues/588#issuecomment-725435202,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFJBJR2KXWQRRV2CDO6W2ODSPKJLZANCNFSM4OXI6X4A
.

--
Thanks and Regards,
MUHAMAD KHAIRUL FILHAN BIN NUSI
Co-founder / Fullstack Developer
KukuBytes Solution

Yes I find out that my account billing was not active thanks

To all who face this issue in the future:
Make sure you have flex: 1 on the parent container and it is not cropping autocomplete

authors: JakubOrsula Salman98 bell-steven kukuandroid mnurulhuda sacmii sasha240100


text:
Which Google Places API to use? Places API or Places API (New) ?

Describe the problem
I'm using this library for the first time, and enabling Google Places API for the first time in the Google Cloud Console.
I see two APIs for Google Places : Places API and Places API (New), I'm not sure which one I should enable to work with react-native-google-places-autocomplete
Reproduction - (required - issue will be closed without this)
In Google Cloud Console, under APIs & Services there is two Places API that can be enabled : Places API and Places API (New)
Additional context

Library Version: [e.g. 1.4.2] Not installed yet

React Native Version: ["0.73.6"]

[x] iOS

[x] Android

[ ] Web

If you are using expo please indicate here:

[ ] I am using expo

Add any other context about the problem here, screenshots etc

@LagoonProject My understanding is that both will work. On my latest project i have opted to using the new places API and can confirm it works.

After further use, it seems this library makes a request to https://maps.googleapis.com/maps/api/place/details/json
which corresponds to the legacy Places API.
      request.open(
        'GET',
        `${url}/place/details/json?` +
          Qs.stringify({
            key: props.query.key,
            placeid: rowData.place_id,
            language: props.query.language,
            ...props.GooglePlacesDetailsQuery,
          }),
      );

The Places API (New) uses https://places.googleapis.com/v1/places/
As per the docs : https://developers.google.com/maps/documentation/places/web-service/overview#places-api-new
So from my understanding, the Places API (New) is not used. But maybe I missed something.

Yep you are right, if you use the Google Places New API key it will still return values but will return the values from the old endpoint. If i get time i might work on a fork to push the option to use the new one but got a lot of work to finish.

From my understanding, if you enable legacy Google Places API in Google Maps Platform, this library will work.
But if you disable it, and enable Google Places API (New) instead, it will throw an error This API project is not authorized to use this API
The API key can be used for both, it's just that the library doesn't make the request to the right endpoint which should be https://places.googleapis.com/v1/places/

authors: LagoonProject brandonzalcman


text:
Megadb.net

Domain
https://megadb.net
Link
https://megadb.net/download
Version
0.2159.0
What browsers are you seeing the problem on?
Chrome
What OS are you seeing the problem on?
Windows
Anything else?
https://user-images.githubusercontent.com/49567056/224113905-827d935a-cea0-4901-9f9f-998e33e0107a.mp4

Duplicate of #610

Duplicate of #610

repo: FastForwardTeam/FastForward

license: Unlicense


text:
Will using this method result in inconsistent output results?

Is the results using Medusa different with the result using greedy decoding ?

In most cases, no. But there is a very tricky bug that we don't know is due to float16 or something else that if it will output inconsistent results after error accumulation (very rare, but it exists).

Thanks for you reply. According to my understanding, if the calculation error is ignored (for example, using fp32), the output result should be the same as greedy decoding.

Hi,
I love your work and thank you for sharing the code. I was wondering whether Medusa gives the same results to the original model (e.g., Vicuna) in sampling mode. Please let me know!

Hi Junyoung, we will release a new version soon and it should contain the sampling method consistent with the original model's distribution. If you want to implement it yourself, it is super easy.
Let's say you have a medusa head's prediction x_{hat} (top-k) from medusa logits p. When you perform the verification using the model's output p, sample x from p and if x matches x_{hat} then accept x_{hat} else reject. The distribution should be the same as the original and you will get a slightly low acceleration rate.

Thank you for the reply. I will stay tuned for the new release!

If you want to check it out first, you can switch to the v1.0 branch and it should be compatible with the previous version (almost done, only the new weight hasn't been released yet.). Let me know if you encounter any issues :)

This thread seems to be quiet for a while. Let me close it for now, and feel free to reopen it :)

@leeyeehoo the medusa no penalty when process logits compare with base model, may be also the reason?

authors: Junyoungpark ctlllll leeyeehoo niyunsheng zhoujian-z

repo: FasterDecoding/Medusa


text:
No puedo crear scripts de batalla

Preparation

[X] I tested the latest release
[X] I looked at other issues (even the closed ones)
[X] I read the Troubleshooting Guide

FGO server
NA
FGA build number
1611
Describe the bug
Cuando entro en la sección para crear el script y apretar en el +, se congela la pantalla, me aparece un mensaje que dice "la app dejó de funcionar" y solo puedo cerrar para volver a usarla.
Video
https://youtu.be/aRt0d7jws9Y
Device model
Huawei Y9s
Android version
10
Screen size
No response
RAM
4Gb

Why did you duplicate your issue in Spanish?

Because I forgot to check the last one and my brother don't understand English haha

repo: Fate-Grand-Automata/FGA


text:
Empezar a usar ofertahoraria.fi.uba.ar

Al parecer la fiuba hizo en el 2018 una pagina que tiene los horarios del siu... si le pegas directamente a la api, te ahorras lo de pedirle a cada alumnno los htmls.
La lista de materias por carrera se pierde acá, pero se puede conseguir del fiuba map
Ejemplos de api

https://ofertahoraria.fi.uba.ar/api/departamento/61

https://ofertahoraria.fi.uba.ar/api/materia/6103

Después, solo habría que chequear alguna manera de confirmar que los datos siguen vigentes... supongo que un cronjob dando vueltas en algun lado que le pegue una vez por dia (ojo con tirarlo abajo...) y se fije si agregaron/sacaron/cambiaron cursos

b086cd0b55793f2bd4f32a88ceb0e40f84582a30

repo: FdelMazo/FIUBA-Plan


text:
🛑 Economy API Endpoint is down

In 5f730bc, Economy API Endpoint (https://economy.roblox.com) was down:

HTTP code: 404
Response time: 57 ms

Resolved: Economy API Endpoint is back up in 965b910 after 5 minutes.

repo: FearedFusionX/Ro-Status


text:
🛑 Game Join API Endpoint is down

In 27592ed, Game Join API Endpoint (http://gamejoin.roblox.com/) was down:

HTTP code: 404
Response time: 92 ms

Resolved: Game Join API Endpoint is back up in 820f976 after 17 minutes.


text:
Testing updates

Updating some testing requirements and adding a step to upgrade pip to the CI tests

Codecov check doesn't seem to be working but that can be a separate issue

repo: FeatureLabs/autonormalize


text:
Update primitive compatibility flags and get_function

Fixes #1128 and #1132

Update primitive compatibility from separate flags to a list of additional compatible libraries
Add argument to get_function for aggregation primitives to return the correct aggregation for the given library
Remove get_dask_aggregation from aggregation primitives

Do we want pandas compatibility to be implicit for all primitives?

authors: frances-h rwedge

repo: FeatureLabs/featuretools


text:
update version

@JuliaRegistrator register()

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/56710
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.3.0 -m "<description of version>" 781a361d6386b27db598501583cf78bb2256ef2a
git push origin v0.3.0

authors: FedeClaudi JuliaRegistrator


text:
v2.0 pre-release issues

Noting problems while testing initial release of v2.0

[ ] intermitted error message display
[ ] progress bar with :detailed columns too wide.
[ ] logging doesnt show array size and doesn't trim stuff. Tuples have weird shape
[ ] MethodError: no method matching frame_module(::Tuple) when rendering errors
[ ] improvements to progress bar styling: https://github.com/FedeClaudi/Term.jl/issues/202  and docstrings

@FedeClaudi Any idea if its possible to change the file link here to the actual (full) filename, instead of relative filename?

thanks for getting in touch. Yeah, I was trying to save some terminal real-estate with these shortened links but it might be better to have the full thing.

@FedeClaudi I meant, you can keep the display name as ./reduce.jl 95, but clicking on it should point to the full path of reduce.jl

Kind like this, this is from another CLI program.
I believe Link is being used to do this?

oh I see. In theory the stacktrace is using Link but it doesn't seem to be working. I'll look into it. It also seems like not all terminals support ANSI link syntax.

All changes listed above have been implemented. https://github.com/FedeClaudi/Term.jl/pull/204 will close this.

authors: FedeClaudi VarLad


text:
Opening an instance details in icognito mode, thows up 4 errors

it seems it's trying to pull something from the API that doesn't exist, but I'm not sure what

It's been already fixed #139.

repo: Fediseer/FediseerGUI


text:
🛑 FeedsBoard RSS.do is down

In bdaa5c8, FeedsBoard RSS.do (https://rss.do) was down:

HTTP code: 520
Response time: 5208 ms

Resolved: FeedsBoard RSS.do is back up in ddad763.


text:
application of Heat Transfer Transient Analysis code

Can the Heat Transfer Transient Analysis calculate the case of a sphere inside the bulk material? I see many similar settings for that.

Hi, the application is based on equations assuming a fluid surrounding a solid. The main implication of this is that the environment remains unchanged. In the case of a sphere inside the bulk material it may work "as is" only if the conductivity constant of the surrounding material is very high. Otherwise, we have a situation in which the immediate surroundings of the sphere don't dissipate heat fast enough and the model wouldn't be an accurate representation of reality. I will leave the issue open and impliment it if I find or deduce a better model for this case.

authors: FernandoLavarreda lianyichuan

repo: FernandoLavarreda/HeatTransfer


text:
Fix dot notation negative index errors

Description
Closes #2050.

Readiness checklist

[ ] I added/updated unit tests.
[x] I added/updated integration/compatibility tests.
[ ] I added/updated comments and checked rendering.
[ ] I made spot refactorings.
[ ] I updated user documentation.
[ ] I ran task all, and it passed.
[x] I ensured that PR title is good enough for the changelog.
[x] (for maintainers only) I set Reviewers (@FerretDB/core), Assignee, Labels, Project and project's Sprint fields.
[x] I marked all done items in this checklist.

TestAggregateCompatGroupDocDotNotation fails, and seems to be a genuine failure

https://github.com/FerretDB/FerretDB/actions/runs/4550452790/jobs/8023489900
I see why, array [42] and non array 42 are the same in comparison order. So sorting can be different between compat and target. This can't be used in $group operators, which was the reason it was introduced initially. Unfortunately I think we need to delete this provider.
2023-03-29T05:30:52.0700205Z                 	Error:      	Not equal:
2023-03-29T05:30:52.0700475Z                 	            	expected: [
2023-03-29T05:30:52.0700686Z                 	            	  {
2023-03-29T05:30:52.0700940Z                 	            	    "$k": [
2023-03-29T05:30:52.0701318Z                 	            	      "_id"
2023-03-29T05:30:52.0701558Z                 	            	    ],
2023-03-29T05:30:52.0701844Z                 	            	    "_id": 42
2023-03-29T05:30:52.0702059Z                 	            	  },
2023-03-29T05:30:52.0702271Z                 	            	  {
2023-03-29T05:30:52.0702545Z                 	            	    "$k": [
2023-03-29T05:30:52.0702830Z                 	            	      "_id"
2023-03-29T05:30:52.0703163Z                 	            	    ],
2023-03-29T05:30:52.0703555Z                 	            	    "_id": [
2023-03-29T05:30:52.0703908Z                 	            	      42
2023-03-29T05:30:52.0704240Z                 	            	    ]
2023-03-29T05:30:52.0704461Z                 	            	  }
2023-03-29T05:30:52.0704644Z                 	            	]
2023-03-29T05:30:52.0704910Z                 	            	actual  : [
2023-03-29T05:30:52.0705119Z                 	            	  {
2023-03-29T05:30:52.0705386Z                 	            	    "$k": [
2023-03-29T05:30:52.0705664Z                 	            	      "_id"
2023-03-29T05:30:52.0705896Z                 	            	    ],
2023-03-29T05:30:52.0706174Z                 	            	    "_id": [
2023-03-29T05:30:52.0706422Z                 	            	      42
2023-03-29T05:30:52.0706651Z                 	            	    ]
2023-03-29T05:30:52.0706865Z                 	            	  },
2023-03-29T05:30:52.0707076Z                 	            	  {
2023-03-29T05:30:52.0707342Z                 	            	    "$k": [
2023-03-29T05:30:52.0707617Z                 	            	      "_id"
2023-03-29T05:30:52.0707857Z                 	            	    ],
2023-03-29T05:30:52.0708129Z                 	            	    "_id": 42
2023-03-29T05:30:52.0708338Z                 	            	  }
2023-03-29T05:30:52.0708531Z                 	            	]
2023-03-29T05:30:52.0708902Z                 	            	--- expected
2023-03-29T05:30:52.0709161Z                 	            	+++ actual
2023-03-29T05:30:52.0709506Z                 	            	@@ -1,8 +1,2 @@
2023-03-29T05:30:52.0709710Z                 	            	 [
2023-03-29T05:30:52.0709962Z                 	            	-  {
2023-03-29T05:30:52.0710272Z                 	            	-    "$k": [
2023-03-29T05:30:52.0710578Z                 	            	-      "_id"
2023-03-29T05:30:52.0710856Z                 	            	-    ],
2023-03-29T05:30:52.0711184Z                 	            	-    "_id": 42
2023-03-29T05:30:52.0711443Z                 	            	-  },
2023-03-29T05:30:52.0711645Z                 	            	   {
2023-03-29T05:30:52.0711988Z                 	            	@@ -14,2 +8,8 @@
2023-03-29T05:30:52.0712223Z                 	            	     ]
2023-03-29T05:30:52.0712444Z                 	            	+  },
2023-03-29T05:30:52.0712655Z                 	            	+  {
2023-03-29T05:30:52.0712924Z                 	            	+    "$k": [
2023-03-29T05:30:52.0713187Z                 	            	+      "_id"
2023-03-29T05:30:52.0713424Z                 	            	+    ],
2023-03-29T05:30:52.0713707Z                 	            	+    "_id": 42
2023-03-29T05:30:52.0713921Z                 	            	   }
2023-03-29T05:30:52.0714708Z                 	Test:       	TestAggregateCompatGroupDocDotNotation/DocDotNotation/TestAggregateCompatGroupDocDotNotation_ArrayAndDocuments

repo: FerretDB/FerretDB


text:
tjson: Check how we support binary and object_id

Description
This PR closes #900.

Readiness checklist

[ ] I added tests for new functionality or bugfixes.
[ ] I ran task all, and it passed.
[ ] I added/updated comments for both exported and unexported top-level declarations (functions, types, etc).
[ ] I checked comments rendering with task godocs.
[ ] (for maintainers only) I set Reviewers, Assignee, Labels, Project and project's Sprint fields.
[ ] I marked all done items in this checklist.

I close this draft as it was split into smaller PRs.


text:
Popper won't flip correctly on IE

CodePen demo
http://codepen.io/claudiobmgrtnr/pen/grBrmV
Steps to reproduce the problem
NOTE: The bug will only appear in IE10 or IE11. Edge works fine.

Open any popper whose boundary element is "viewport"
Apply "overflow-y: auto" to the body
Scroll until the popper should flip to prevent itself exiting the viewport

What is the expected behavior?
The popper should flip to the correct position following the order of the desired flip behavior.
What went wrong?
The popper exits the viewport. There seems to be a problem in IE where scrolltop of the body will always be 0 if its "overflow-y" css property is set to "auto". This causes wrong calculation results of the boundaries. Removing the overflow-y property should fix it.
Any other comments?
I didn't test it in IE9

I don't see the popper at all in your demo..

there should be a button in between of the text that says "click me" that toggles the popper.

Am 06.08.2016 um 23:04 schrieb Federico Zivolo notifications@github.com:
I don't see the popper at all in your demo..
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Ok I reproduced the problem on IE11...
Seems like we have to use:
document.documentElement && document.documentElement.scrollTop

To properly get the scrollTop value on IE11 and below.

We already do this kind of check because it was needed for Firefox compatibility.. I'm investigating why it doesn't work..

Seems like I patched it, here a demo:
http://codepen.io/FezVrasta/pen/XKxLkz
I'm going to create a PR to see if the tests still pass and if so I'll merge the fix

Fixed on 0.5.3, released right now

authors: FezVrasta claudiobmgrtnr


text:
New Quarkus version

Hi @novoj
It is some time I am not running your benchmark with latest quarkus version, let me know if you can give it a shot, so I can verify if I found anything strange

I will give it a shot

Original results based on Quarkus 3.0.4.Final (baseline):
Benchmark                                                      Mode  Cnt      Score      Error  Units
ServersThroughputBenchmark.graphQLApiEchoQuery_QuarkusServer  thrpt    5  21830.819 ± 1492.236  ops/s
ServersLatencyBenchmark.graphQLApiEchoQuery_QuarkusServer      avgt    5    281.107 ±   20.137  us/op

Native Quarkus:
Benchmark                                                      Mode  Cnt      Score     Error  Units
ServersThroughputBenchmark.graphQLApiEchoQuery_QuarkusServer  thrpt    5  15720.155 ± 799.392  ops/s
ServersLatencyBenchmark.graphQLApiEchoQuery_QuarkusServer      avgt    5    392.781 ±  38.727  us/op

New results with version 3.8.1:
Benchmark                                                      Mode  Cnt      Score      Error  Units
ServersThroughputBenchmark.graphQLApiEchoQuery_QuarkusServer  thrpt    5  22147.961 ± 1692.798  ops/s
ServersLatencyBenchmark.graphQLApiEchoQuery_QuarkusServer      avgt    5    281.611 ±   19.583  us/op

Native Quarkus:
Benchmark                                                      Mode  Cnt      Score      Error  Units
ServersThroughputBenchmark.graphQLApiEchoQuery_QuarkusServer  thrpt    5  14901.192 ± 2034.417  ops/s
ServersLatencyBenchmark.graphQLApiEchoQuery_QuarkusServer      avgt    5    412.826 ±   29.148  us/op

I think the difference is negligible.

Tests were run as follows:
java -jar performance_tests/target/benchmarks.jar .*Quarkus.* -wi 1 -i 5 -f 1

Yep, thanks! I need to check what's going on with the graphQL lib at this point; the fact that native is not half of the performance of JVM mode is sign of reflective operations which are likely better behaving in native mode (which is expected) - but it still means there are lot of hanging fruits there

repo: FgForrest/HttpServerEvaluationTest


text:
Path does not stay filled in file dialog between opening

This happened to me a few times but it seems to have stayed for a month now.

authors: Figglewatts KVRX

repo: Figglewatts/LSDView


text:
Split BaseViewModel into mixin and concrete implementation

This allows more flexibility using the view model in existing class hierarchies.
Also added a method to see if any keys have an error and simplified some code paths:

simplified busy check in skeletonData
return rather than store and return in runBusyFuture

This PR doesn't fall in line with what Stacked wants to offer as a developer experience.

authors: FilledStacks safarmer

repo: FilledStacks/stacked


text:
Unable to install with composer due to stability level

My fresh installation of yii2-advanced does not accept the current stability level of this package:
composer require --prefer-dist filsh/yii2-oauth2-server "*"

does not work. Instead I used:
composer require --prefer-dist filsh/yii2-oauth2-server "@dev"

and with that it worked whitout doing anything else? i got it runnig, but i got the error i posted some minutes ago :(

authors: eborned rollwhistler


text:
com.squareup.moshi.LinkedHashTreeMap cannot be cast to io.finnhub.api.models.StockSymbol

This error occurred after I upgraded to version 2.0.6
Function call that caused the error: apiClient.stockSymbols(exchange.code, "", "", "")
where exchange is of type StockExchange

Hi there,
This should be fixed in 2.0.7 which will be released in a few hours on Maven.
Apologies for the inconvenience.

Thank you. What about my comment on this  commit?
Isn't it better for quote to be of type JsonObject?

authors: finnhubio shervinkoushan

repo: Finnhub-Stock-API/finnhub-kotlin


text:
FirebaseAuth failing on iOS after upgrade to flutter v1.7.8+hotfix.3 and firebase_auth: ^0.11.1+3 (the same with v1.9.1+hotfix.2)

Errors:
Use of undeclared identifier 'FIRAuthErrorUserInfoNameKey'
Property 'providerID' not found on object of type '__strong id'
(and then many more errors).
Was working before the upgrade, and still works on Android.
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.7.8+hotfix.3, on Mac OS X 10.14.5 18F132, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] Xcode - develop for iOS and macOS (Xcode 10.2.1)
Note: Just adding firebase_auth to the pubspec.yaml of the default created app
dependencies:
  flutter:
    sdk: flutter
  firebase_auth: ^0.11.1+3

causes the same issue.

@agreensh
The issue at https://github.com/flutter/flutter/issues/36676 has been closed and moved here. Future collaboration on this issue will be done here.

@agreensh Basing on https://github.com/flutter/flutter/issues/36676#issuecomment-540890533 I think it's safe to close the issue. Please comment if you don't agree, I will re-open it right away.

authors: BondarenkoStas kroikie

repo: FirebaseExtended/flutterfire