text:
fix: 24420 Timezone message for assignee disappears

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/24420
PROPOSAL: https://github.com/Expensify/App/issues/24420#issuecomment-1675656171
Tests

Go to staging.new.expensify.com
Assign a task to User A and select User B as Share somewhere destination
Open the task detail page
Tap on Assignee and change assignee to User C
Verify that the time zone message for task assignee above composer will update with the new assignee

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

Offline tests

Same as above
QA Steps

Go to staging.new.expensify.com
Assign a task to User A and select User B as Share somewhere destination
Open the task detail page
Tap on Assignee and change assignee to User C
Verify that the time zone message for task assignee above composer will update with the new assignee

[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 / 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] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

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

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

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

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

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

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/113963320/7c845c24-321b-43dd-bf02-1c354e8cdb9b

Mobile Web - Chrome

https://github.com/Expensify/App/assets/113963320/3d158430-3637-4bb5-900f-256bd9d6a4fc

Mobile Web - Safari

https://github.com/Expensify/App/assets/113963320/b0856713-3b99-4197-be06-3342a123c5e7

Desktop

https://github.com/Expensify/App/assets/113963320/9ada1ab4-c179-4fd8-a471-9a036efcdfb5

iOS

https://github.com/Expensify/App/assets/113963320/e2cb8961-e5be-4db8-834a-b43cdef353eb

Android

@tienifr Even the username in the timezone message (incase of same timezone on the attached video) is not being changed. Can we update to change the username?

@youssef-lr If you are around, Can you please have a look and merge this PR.

LGTM! But we have conflicts.

: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/youssef-lr in version: 1.3.62-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.62-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Not sure why the label got applied, but all checks had passed.

authors: OSBotify sobitneupane tienifr youssef-lr


text:
[No QA] [TS migration] Migrate 'NumberUtilsTest.js' test to TypeScript

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/25271
PROPOSAL: N/A
Tests

Check if tests passed in the pipeline or run them locally with npm run test tests/unit/NumberUtilsTest

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

Offline tests

N/A
QA Steps

N/A

[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 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 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 form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label 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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

FYI @JKobrynski is OOO from Feb 12th to Feb 16th.

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 approved by marketing by adding the Waiting for Copy label for a copy review 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 */
[ ] 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 form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label 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/neil-marcellini in version: 1.4.44-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.44-13 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

source: gharchive/pull-request

authors: JKobrynski OSBotify fabioh8010 jjcoffee

repo: Expensify/App

license: MIT

license_type: permissive

license_source: github-api


text:
Revert "Search suffix tree implementation"

Reverts Expensify/App#51954
Trying to revert to see if this caused https://github.com/Expensify/App/issues/54632
Context https://expensify.slack.com/archives/C01GTK53T8Q/p1735334248201239

Closing https://expensify.slack.com/archives/C01GTK53T8Q/p1735585632267219?thread_ts=1735334248.201239&cid=C01GTK53T8Q


text:
🍒 Cherry pick PR #7112 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/7112 to staging 🍒

🚀 Cherry-picked to staging by @OSBotify in version: 1.1.27-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

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

🚀 Deployed to production by @roryabraham in version: 1.1.27-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to staging by @OSBotify in version: 1.1.27-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


text:
[HOLD Web-E #34307] Refactor get PolicySummaryList in App

Details
Hold on prod deploy - https://github.com/Expensify/Web-Expensify/pull/34307
Fixed Issues
$ https://github.com/Expensify/Expensify/issues/213887
Tests

Open your browser console
Sign in to the App
Verify that there are no calls to Get and returnValueList=policySummaryList
Verify that OpenApp returns an Onyx update object, i.e. key: policy_<POLICY_ID> for each policy in your test account
Disable internet connect and enable it again
Verify that ReconnectApp returns an Onyx update object, i.e. key: policy_<POLICY_ID> for each policy in your test account
Edit this line from explode(',', $clientPolicyIDList), to

[...explode(',', $clientPolicyIDList), 'fakePolicyID'],

Refresh the App and verify that OpenApp returns an Onyx update object for key: fakePolicyID with value: null

[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

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

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

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified 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

[ ] Verify that no errors appear in the JS console

Screenshots

Web
https://user-images.githubusercontent.com/22219519/179117866-8d2ec976-70b9-4b77-babd-bedf62503efd.mov
Mobile Web

Desktop

iOS

Android

Web-E PR is in prod. Removing hold and merging!

: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 @luacmartins in version: 1.1.86-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Hi guys! QA reported this issue, does someone know if this issue is either N/A or an uncovered edge case?

Left a comment here

🚀 Deployed to production by @yuwenmemon in version: 1.1.86-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

authors: OSBotify luacmartins marcochavezf


text:
train was killed

i have a question when I use this command
python3 main.py --cfg /root/autodl-tmp/TCAF-GZSL/config/best/best_cls/best_anet.yaml  --root_dir avgzsl_benchmark_non_averaged_datasets/UCF --log_dir networks/activitynet_cls --dataset_name ActivityNet --run all
it turns out that my program was killed because memory is full even 80G.it just don't use GPU's memory at all

I do not understand. Was your previous error due to a different numpy library? Did you fix that? If so, then please respond so that we can close that issue.
And afterwards you get the memory issue? All these datasets are loaded in RAM and then, the batches are loaded in GPU memory. You get this error because the RAM memory is probably full. You need around 80GB RAM if i remember correctly for ActivityNet, and much less for the other 2 datasets, as we load all the features in memory at once. ActivityNet has long videos, which consumes a lot of memory. We are aware of this issue, but for our setup when we did the project, it was desirable to load everything in memory. However, you can try to change this if it is not suitable for you.

source: gharchive/issue

authors: MerceaOtniel xiaoxinning

repo: ExplainableML/TCAF-GZSL


text:
Timeline refactoring

A part of the new timeline was already merged in dev-1. These commits now complete the timeline behavior in terms of the following usability characteristics:

Changing the route and changing back to Visualization won't reset the timeline , so that the previously loaded points are gone.
A route change will not reset the selection status.
Now, the pause button only applies to the rendering, not to the timeline.
The plot won't reset its "sliding window" if the user hovers or drags the plot.

@czirkelbach Can you verify the functionality and report back?

Successfully merged into branch dev-1.

authors: Alexander-Krause czirkelbach

repo: ExplorViz/explorviz-frontend


text:
Ticket example

Describe the problem
Provide app.log file from %userprofile%/appdata/local/MercuryTrade folder.

Problem concerns the new Overseer functionality.
Upon making 2 icons for flasks I found the following problem:
When you press a button down (1) then press another button down (2) then release the first button (1) and then the second button (2) - the second icon timer starts, as it should, but the first one doesn't.
As I understand it the trigger for the icon timer starts upon a release of a button. Apparently pressing another one before releasing the first deletes it.

repo: Exslims/MercuryTrade

license: mit

license_source: bigquery


text:
Sentiment scores of arguments and chunks don't align to each other

It's clear that this is caused by way of normalization of sentiment scores of arguments. Should find a way to have the scores normalized to reflect the actual sentiment.

To fix this I changed the way of normalizing the argument sentiment score as this: norm(x) = (x + 1) / 2.
Also, to have coherence scores that make more sense, I choose to use the Gaussian activation function with a deviation equals to 0.2.


text:
V/2.0.0

Release 2.0.0

coverage: 100.0%. remained the same
when pulling 45058ed34f672df2bf4c12c15f85192f1a7082a2 on v/2.0.0
into 6637e2f9507898d4540b569f53f8f7c22fb8f4a2 on main.

authors: Galtozzy coveralls

repo: EzyGang/py-cachify


text:
Allows definition of custom HDF proxy through SWIG and small bug fixes

What does this implement/fix? Explain your changes.
Allows definition of custom HDF proxy through SWIG
Also:

add custom HDF proxy example in C#
fix an issue that occurs when receiving a PutDataArrays in the ETP server example
fix an issue that occurs when providing a nullptr proxy parameter in WellboreTrajectoryRepresentation::setGeometry

Does this close any currently open issues?
No.
Any relevant logs, error output, etc?
No.
Any other comments?
No.
Where has this been tested?
Operating System: Windows 10 64bits
Platform: Visual Studio Community 2019

Thank you for the review as well as for the encouraging comment.


text:
Adds coveralls badge to repo

Issues:
Fixes #547
Problem:
The f5-sdk codebase can run coverage tests, but there is no easy reporting
of these results.
Analysis:
The Coveralls.io service has been setup for the f5-common-python test. This
change to the README is to add the badge for coveralls so that developers
can easily see what the coverage tests currently result in
Tests:
None

@pjbreaux @zancas I think this is now ready to go live

Do you think there's any value in seeing how much coverage we have of a particular test file? Might be interesting, as shawn said in slack, to see if a test file has been configured to skip half of its tests.

I originally had the tests in there, but shawn suggested I exclude them. I can add them back if that's what we want

Let's exclude them as suggested, then we'll just add them back in if we ever want. I bet we never will.


text:
run a tool as root with certain env variables tempest_v2driver_install.sh must be run as root

This mean  we don't need sudo invocations in the file.
Also, add | xargs to trim whitespace in the variable extractions scripts.

This has been fixed by PR #322 .


text:
Feature.implement pool methods 9

@mattgreene
Fixes: #9
This code was necessary for the test of pool creation and deletion in the f5-openstack-lbaasv2-driver repo.   Please run the tests in that repo to see the new utility code in this repo in action.

Close the other PR first, if this is merged both will close.


text:
🛑 Repositorio is down

In 20828fd, Repositorio (https://repositorio.aden.org/) was down:

HTTP code: 403
Response time: 221 ms

Resolved: Repositorio is back up in b621076.

repo: FAD-Desarollo/upptime


text:
ARGOS HIVE2 Review the HIVE2 living draft protocols

I reviewed and ran through the HIVE2 protocols per Stephanie's request. I have left comments on issues/format that I have found within the documents.
https://drive.google.com/drive/folders/1-ZoDCBrYc2qlvx7MSWFXvvmVzJDyApMX

Finished reviewing the protocols and now working on a presentation for Keeney


text:
Usage Examples?

Hi
Would you be able to add some examples of how to use this?
Also, what's the difference between Active and Passive mode, and are the SET and RESET pins required? Hard to find out as the datasheet for the A003 is only in Chinese!
Thanks

Hi Daniel ,
You can find examples how of to use it in test.py test_passive.py and test_passive_sleep.py.
test.py
This uses active mode.  In this case the PM sensors sends data over the serial port whenever it has a reading available and the code just has to listen to receive it.
test_passive.py
This uses passive mode, which means that the device only sends readings when explicitly asked.  So the method called does the following to take a reading
self.serial.flush()  # Make sure tx buffer is completely sent
ret = self.read(False)

test_passive_sleep.py
Is the same as test_passive.py but also demonstrates how to turn the fan of the sensor off to reduce power consumption
No the SET and RESET pins are not required.
At the time of posting an English version of the datasheet for the A003 can be found at http://m.eleparts.co.kr/data/goods_old/data/PMSA003.pdf.
Hope that helps.

@pjb304 so does pulling low on the SET pin to "sleep" do the same thing as the "sleep" command used in test_passive_sleep.py? I've read it's important to sleep the device when it doesn't need to be reading to significantly lengthen the lifespan of the sensor, but I'm not sure if both of these "sleep" functions really to the same thing. The use I have in mind (monitoring air quality when 3D printing) really requires very infrequent readings (maybe once every 15 minutes or so for several days in very long prints).

I'm afraid I don't know.  We use active mode 24/7 in our sensors some of which have been running continuously for 2 years.
The passive mode and sleep code has been contributed by others, while we've tested it works briefly I do not know all the details of how it works, and our sensors are just connected using TX, RX and GND.  Reading the datasheet I would assume that the sleep mode is the same if you enter it using the s/w or the SET line, but I have not tested this.

Hi,
Further to Phil comments, we already had a discussion about the sleep mode earlier in this pull request: https://github.com/FEEprojects/plantower/pull/3#pullrequestreview-345829048
But as Phil said, we only use the active mode. The performance of the sensor did not degrade over a year long period and we have been running the sensors for more than two years (but we have not yet checked whether the performances degrade on the second year).
I hope that helps.

Something isn't quite right in the usage examples..
I followed test_passive.py, and got nonsensical results. Changing to active mode immediately gave more realistic-looking results.
>>> PLANTOWER = plantower.Plantower(port="COM3")
>>> PLANTOWER.mode_change(plantower.PMS_PASSIVE_MODE) #change into passive mode
>>> PLANTOWER.set_to_wakeup() #spin up the fan
>>> time.sleep(30)
>>> RESULT = PLANTOWER.read_in_passive()
>>> print(RESULT)
2020-05-02 17:03:22,0,0,0,0,0,0,135,42,3,0,0,0,
>>> RESULT = PLANTOWER.read_in_passive()
>>> print(RESULT)
2020-05-02 17:04:42,0,0,0,0,0,0,102,34,3,0,0,0,
>>> RESULT = PLANTOWER.read_in_passive()
>>> print(RESULT)
2020-05-02 17:07:35,0,0,0,0,0,0,63,21,0,0,0,0,
>>> RESULT = PLANTOWER.read_in_passive()
>>> print(RESULT)
2020-05-02 17:07:46,0,0,0,0,0,0,129,37,0,0,0,0,
>>> RESULT = PLANTOWER.read_in_passive()
>>> print(RESULT)
2020-05-02 17:08:52,0,0,0,0,0,0,99,30,0,0,0,0,
>>> RESULT = PLANTOWER.read_in_passive()
>>> print(RESULT)
2020-05-02 17:10:29,0,0,0,0,0,0,159,47,3,0,0,0,
>>> PLANTOWER.mode_change(plantower.PMS_ACTIVE_MODE)
>>> PLANTOWER.set_to_wakeup()
>>> print(PLANTOWER.read())
2020-05-02 17:12:17,1,1,10,10,14,14,0,0,0,0,0,0,
>>> print(PLANTOWER.read())
2020-05-02 17:12:22,1,1,11,11,16,16,423,141,43,33,3,3,
>>> print(PLANTOWER.read())
2020-05-02 17:12:29,1,1,11,11,12,12,387,129,36,30,0,0,
>>> print(PLANTOWER.read())
2020-05-02 17:12:34,1,1,10,10,11,11,282,94,24,21,0,0,
>>> print(PLANTOWER.read())
2020-05-02 17:12:36,1,1,10,10,11,11,294,98,27,18,0,0,
>>> print(PLANTOWER.read())
2020-05-02 17:12:41,1,1,8,8,10,10,243,81,18,9,0,0,

Have I done something wrong here?

I'm afraid I'm not sure what's going on there.  I have just run the same commands as you in an interactive shell and it is working for me.  As I can't repeat the issue I'm afraid I can't offer any fixes.
pi@puffin:~/plantower $ ipython3
Python 3.7.3 (default, Dec 20 2019, 18:57:59)
Type "copyright", "credits" or "license" for more information.

IPython 5.8.0 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: import plantower, time

In [2]: PLANTOWER = plantower.Plantower("/dev/ttyUSB0")

In [3]: PLANTOWER.mode_change(plantower.PMS_PASSIVE_MODE)

In [4]: PLANTOWER.set_to_wakeup()

In [5]: time.sleep(30)

In [6]: print(PLANTOWER.read_in_passive())
2020-05-04 13:49:33,7,7,9,9,11,11,1326,367,58,4,2,2,

In [7]: print(PLANTOWER.read_in_passive())
2020-05-04 13:50:08,7,7,10,10,10,10,1386,385,56,4,0,0,

In [8]: print(PLANTOWER.read_in_passive())
2020-05-04 13:50:13,8,8,11,11,11,11,1404,390,60,6,0,0,

In [9]: print(PLANTOWER.read_in_passive())
2020-05-04 13:50:15,8,8,11,11,11,11,1386,380,58,6,0,0,

It also works when called using the script:
pi@puffin:~/plantower $ ./test_passive.py /dev/ttyUSB0
Setting sensor into passive mode. Please wait.
2020-05-04 13:57:01,6,6,9,9,9,9,1266,356,52,2,0,0,

@pjb304 so does pulling low on the SET pin to "sleep" do the same thing as the "sleep" command used in test_passive_sleep.py? I've read it's important to sleep the device when it doesn't need to be reading to significantly lengthen the lifespan of the sensor, but I'm not sure if both of these "sleep" functions really to the same thing. The use I have in mind (monitoring air quality when 3D printing) really requires very infrequent readings (maybe once every 15 minutes or so for several days in very long prints).

From my PMS7003 power consumption test on my board, "pulling low on the SET pin to "sleep" do the same thing as the "sleep" command".
It had the same power consumption.
My reading was 4.81mA @ VCC 5.6V
It was quite higher than the datasheet value(0.2mA @5V), but still very lower than active current though.
I could do something wrong on my measurement, but on my environment SET pin and sleep command was same.

Thanks for the update, it's good to know that set low and the sleep command seem to do the same thing.

authors: FlorentinBulotUoS pjb304 serunis stantond

repo: FEEprojects/plantower


text:
Hudson 远程ssh执行脚本报错

/Library/Ruby/Site/2.0.0/rubygems.rb:271:in find_spec_for_exe': can't find gem fir-cli (>= 0.a) (Gem::GemNotFoundException) 	from /Library/Ruby/Site/2.0.0/rubygems.rb:299:in activate_bin_path'
from /Users/yanghy/.rvm/rubies/ruby-2.4.0/bin/fir:23:in <main>' 	from /Users/yanghy/.rvm/rubies/ruby-2.4.0/bin/ruby_executable_hooks:15:in eval'
from /Users/yanghy/.rvm/rubies/ruby-2.4.0/bin/ruby_executable_hooks:15:in <main>' /Library/Ruby/Site/2.0.0/rubygems.rb:271:in find_spec_for_exe': can't find gem fir-cli (>= 0.a) (Gem::GemNotFoundException)
from /Library/Ruby/Site/2.0.0/rubygems.rb:299:in activate_bin_path' 	from /Users/yanghy/.rvm/rubies/ruby-2.4.0/bin/fir:23:in '
from /Users/yanghy/.rvm/rubies/ruby-2.4.0/bin/ruby_executable_hooks:15:in eval' 	from /Users/yanghy/.rvm/rubies/ruby-2.4.0/bin/ruby_executable_hooks:15:in '
报这个错如何解决？
命令行手动执行没问题

哥们用了rvm 安装了吧
https://42ways.de/blog/tags/jenkins/

哥们用了rvm 安装了吧
https://42ways.de/blog/tags/jenkins/

我也报了这个错，具体怎么操作呢?

repo: FIRHQ/fir-cli


text:
上传完成后获取下载地址

 fir --version
✈ fir-cli 2.0.14

调用 fir publish 后，只在 log 中看到了下载地址，好像没有显式返回或者设置为某个环境变量？
找了文档也没有找到相关说明。还是说只能从 log 中截取呢？
辛苦解惑，谢谢～

grep 截取输出吧

目前直接 grep Published succeed 那一行了。
egrep '(Published succeed: )\S+' grep_text.txt | egrep -o '(https?):\/\/[-A-Za-z0-9+&@#/%?=~_|!:,.;]+[-A-Za-z0-9+&@#/%=~_|]'


text:
Prathi/liftcode

Fixing lift code

looks good.

looks good.

repo: FIRST-Tech-Challenge/FtcRobotController


text:
Skalieren der Leitlinienbilder auf der Startseite

Größe der Website bisher ca. 50 MB (viel zu groß).
Leitlinienbilder unter
/themes/tenderfoot_uos/images/
verkleinern auf die Auflösung 365x182px

traumhaft, ist eingebaut und läuft. Dabei ist uns aufgefallen das die Bilder nicht ordentlich angeordnet sind (wahrscheinlich alter css fix überschrieben).
Ich hänge das an ein anderes Ticket damit wir dieses hier schließen können.

authors: dofeldsc manschwa

repo: FISvirtUOS/VIVO


text:
Integration examples

[ ] Cloudflare workers
[ ] React
[ ] Electron
[ ] Tauri

@FL33TW00D can you please specify a bit more what do you need?

@FL33TW00D can you please specify a bit more what do you need?

Hi David,
It would be great to have an examples folder using whisper-turbo in an electron app or similar.
Just something so people can get started with it.
The code for the playground isn't top notch, so some out of the box examples + the new docs would be great!
I'm releasing 0.10.0 tomorrow which should nail down the public API (it's the same as OpenAI here), the examples should be stable after that).
Appreciate you asking!

It would be great to have an examples folder using whisper-turbo in an electron app or similar.

I can do that. Another idea could be expose whisper-turbo via rest api accessing the WebGPU with electron. I have a project never released that do that with LLMs

It would be great to have an examples folder using whisper-turbo in an electron app or similar.

I can do that. Another idea could be expose whisper-turbo via rest api accessing the WebGPU with electron. I have a project never released that do that with LLMs

Awesome that sounds great!

Im attacking this on fri. Sorry for the delay, so many things 😢

Would you consider to have a monorepo having multiple packages? I think is more clean than having an examples folder

Would you consider to have a monorepo having multiple packages? I think is more clean than having an examples folder

Good idea! No rush on implementing anything, still a fair few bugs in WT to work out!

Just a vanilla JS example would also be great :-)

@flatsiedatsie You can check out examples on the updated version: https://github.com/FL33TW00D/ratchet/tree/master/examples/ratchet-whisper

authors: DavidGOrtega FL33TW00D flatsiedatsie


text:
How does image loading work in haxeflixel, more specifically this engine

because the spritesheet images are 8k images how are they loaded without taking 200mb PER image?!??!?

I'm also interested in this, if its because of optimizations to the flixel fork CE uses the devs should definitely consider creating a PR to actual flixel

This feature is called Gpu Textures, it basically offloads the texture to the gpu. The code in in funkin/backend/system/OptimizedBitmapData.hx

authors: ACrazyTown NeeEoo rayanmargham

repo: FNF-CNE-Devs/CodenameEngine


text:
add faq page

Adding an FAQ page to the project website would definitely improve the user experience by providing quick answers to common questions :smile:
I would love to work on it . Sir, could you please assign this task to me.

#110

authors: Mr-Sunglasses codecShivam

repo: FOSS-Community/website-fossc


text:
Contextual behaviour of triggers (and --z3refresh)

This issue is closely related to #1208.
The following code has the weird behaviour that the toplevel definition p_5 only verify if p_2 is defined beforehand.
module Mini

assume val p: int -> prop
assume val q: int -> prop

let p_2 () : Lemma (requires (forall x . p x /\ q x)) =
  admit ()

let p_5 () : Lemma (requires (forall x . {:pattern q x} (p x /\ q x))) =
  assert ((p 0 /\ q 0) ==> (p 0 /\ q 0));
  admit ()

Moreover, using z3 4.5.0, p_5 verifies the first time it is checked in interactive mode but not the second as is shown by the following transcript :
{"query-id":"1","query":"push","args":{"kind":"full","code":"module Mini\n","line":1,"column":0}}
{"query-id":"2","query":"push","args":{"kind":"full","code":"\nassume val p: int -> prop\nassume val q: int -> prop\n","line":2,"column":0}}
{"query-id":"3","query":"push","args":{"kind":"full","code":"\nlet p_2 () : Lemma (requires (forall x . p x /\\ q x)) =\n  admit ()\n","line":5,"column":0}}
{"query-id":"4","query":"push","args":{"kind":"full","code":"\nlet p_5 () : Lemma (requires (forall x . {:pattern q x} (p x /\\ q x))) =\n  assert ((p 0 /\\ q 0) ==> (p 0 /\\ q 0));\n  admit ()\n","line":8,"column":0}}
{"query-id":"5","query":"pop","args":{"dummy":null}}
{"query-id":"6","query":"push","args":{"kind":"full","code":"\nlet p_5 () : Lemma (requires (forall x . {:pattern q x} (p x /\\ q x))) =\n  assert ((p 0 /\\ q 0) ==> (p 0 /\\ q 0));\n  admit ()\n","line":8,"column":0}}

This behaviour is not present in z3 4.5.1, and the code always verifies. Any idea where this could come up from @wintersteiger ?
Another weirdness is created by the option --z3refresh which makes the verificationof p_5 always fail with both versions of z3.

On the Z3 side, the short answer is that the search goes down a different path, due to various changes since 4.5.0 (and indeed your changes to the order of constraints). One problem that has always existed in Z3 is that quantifier instances are not kept during backtracking, so after swapping the order of decisions, it ends up with a different set of instances that may or may not be sufficient to prove the goal.
(The main reason for this is that Z3 doesn't track the dependencies of quantifier instances, which, incidentally, is also the main reason for hints not replaying. There's a quick and dirty fix, but it kills the performance; I'm working on fixes for this and related problems, but no ETA at this point in time.)

Thanks Christoph. But does that that also explain why things verify once, then fail on the second attempt in 4.5.0? And does it explain why things always fail with --z3refresh?

Probably. I didn't look into this particular one yet, but in incremental mode it's very well possible that it will behave differently in the second run (e.g. the first push/pop that Z3 encounters, makes it switch from a non-incremental solver to an incremental one, which is frequently a source of confusion for our users).
--z3refresh changes the way the queries look, so yes, it can make it behave differently than non-z3refresh ones. There is no guarantee that Z3 will exhibit "similar" behavior on "similar" queries, this is an inherent property of search-based algorithms, and taking any amount of unpredictability out of the process usually incurs a significant performance penalty, so it's a fine line to walk.

The problem here was that Lemma (requires x) was parsed as Lemma (ensures x)

(That issue was fixed by @nikswamy recently; the error message is much better now)

authors: cpitclaudel kyoDralliam wintersteiger

repo: FStarLang/FStar


text:
Replacing type by provably propositionally equal type breaks typechecking

The example below shows a case where type checking fails after replacing a type defined transparently in another module by a type that is provably propositionally equal. Moreover, when redefining the problematic type locally, the code typechecks.
module M

open FStar.UInt
(*
In FStar.UInt:
type uint_t (n:pos) = x:int{size x n}

In FStar.UInt64:
val v        : t -> Tot (uint_t n)
val uint_to_t: uint_t n -> Pure t
*)

let n:pos = 32

val uint64_to_uint32: m:UInt64.t{fits (UInt64.v m) n} -> Tot FStar.UInt32.t
let uint64_to_uint32 m =
  let m': x:int{size x n} = UInt64.v m in
  UInt32.uint_to_t m'

//With this uncommented, uint64_to_uint32' below typechecks
//type uint_t (n:pos) = x:int{size x n}

val uint64_to_uint32': m:UInt64.t{fits (UInt64.v m) n} -> Tot FStar.UInt32.t
let uint64_to_uint32' m =
  cut (uint_t n == x:int{size x n});
  cut (forall (p:uint_t n). p:(x:int{size x n}));
  let m':uint_t n = UInt64.v m in // This fails, even if the above is provable
  UInt32.uint_to_t m'

Labelling this as a bug, but remove the label if you believe this is expected (and please explain why!).

Sorry Santiago ... this looks painful. It is a bug, but it's a bit delicate to fix ... but I really should fix it. I think it's a duplicate of another you had to suffer through, but I'm having trouble finding that issue now.
Here's what's happening:

This file fails even --lax checking. The error is raised by the type inference algorithm and is unrelated to the verification conditions.

The problem is that in the 2nd last line, we have a type inference problem of the form t n <: t m, i.e., a rigid-rigid subtyping. In this case, it seems we try directly to unify n=m, which fails in this case. The unification algorithm has support for backtracking, but, it in this case, it doesn't seem to be backtracking as expected.

When you add the intervening type abbreviation, the inference problem becomes of the form s n <: t m, which triggers some unfolding first and then ends up generating a verification condition relating the sizes of the integers, which Z3 can prove.

Same problem appeared in printf implementation, but Nik found a quick workaround (4ff8a23).

@R1kM ran into this today, which seems to have been made more frequent after my changes to the unfolding logic for refinements in the unifier. I added a file examples/micro-benchmarks/UnifyRefs.fst with various instances of this so we keep it tracked. Failing tests have a @fail attached, so we'll know if they happen to be fortuitously fixed.
I can try to improve the unifier next week. For reference, this is the current test file and status. The first 8 tests fail.
[@fail]
let nat32_to_nat64'0 (n:nat32) : nat64 = n

[@fail]
let nat32_to_nat64'1 (n:natN pow2_32) : nat64 = n

[@fail]
let nat32_to_nat64'2 (n:nat32) : natN pow2_64 = n

[@fail]
let nat32_to_nat64'3 (n:natN pow2_32) : natN pow2_64 = n

[@fail]
let nat64_to_nat32'0 (n:nat64 {n < pow2_32}) : nat32 = n

[@fail]
let nat64_to_nat32'1 (n:nat64 {n < pow2_32}) : natN pow2_32 = n

[@fail]
let nat64_to_nat32'2 (n:natN pow2_64 {n < pow2_32}) : nat32 = n

[@fail]
let nat64_to_nat32'3 (n:natN pow2_64 {n < pow2_32}) : natN pow2_32 = n

(* Unfolding manually causes the unifier to do more work, and succeed *)

let nat32_to_nat64'4 (n:nat{n < pow2_32}) : natN pow2_64 = n

let nat32_to_nat64'5 (n:nat32) : (x:nat{x < pow2_64}) = n

let nat64_to_nat32'4 (n:(x:nat{x < pow2_64}) {n < pow2_32}) : nat32 = n

let nat64_to_nat32'5 (n:nat64 {n < pow2_32}) : (n:nat{n < pow2_32}) = n

Some progress in nik_606 ... trying to land this in master

authors: catalin-hritcu mtzguido nikswamy s-zanella


text:
Neuroglancer volume fetching

Allow overriding maximum bytes to download when fetching high-resolution volumes by setting env var SIIBRA_MAX_FETCH_SIZE_GIB. Also, use max_bytes to override the specific request. (fixes #451 )
Reintroduce desired color channel to be fetched using channel kwarg.

Codecov Report
Attention: 1299 lines in your changes are missing coverage. Please review.

Comparison is base (5a0e6b3) 36.81% compared to head (3dd6153) 53.36%.
Report is 381 commits behind head on main.

Files
Patch %
Lines

siibra/features/feature.py
48.55%
125 Missing :warning:

siibra/volumes/volume.py
44.85%
118 Missing :warning:

siibra/core/region.py
56.75%
112 Missing :warning:

siibra/volumes/parcellationmap.py
18.97%
111 Missing :warning:

siibra/explorer/url.py
0.00%
107 Missing :warning:

...bra/features/connectivity/regional_connectivity.py
33.33%
56 Missing :warning:

siibra/retrieval/datasets.py
49.53%
54 Missing :warning:

siibra/explorer/util.py
0.00%
51 Missing :warning:

...a/features/tabular/receptor_density_fingerprint.py
4.54%
42 Missing :warning:

...a/features/tabular/regional_timeseries_activity.py
39.13%
42 Missing :warning:

... and 36 more

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##             main     #549       +/-   ##
===========================================
+ Coverage   36.81%   53.36%   +16.54%
===========================================
  Files          61       69        +8
  Lines        5421     6636     +1215
===========================================
+ Hits         1996     3541     +1545
+ Misses       3425     3095      -330

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: AhmetNSimsek codecov-commenter


text:
Add possibility to use raw PDO stuff notice

Make the user aware of the possibility to use raw PDO stuff.

:+1:

authors: FaaPz ismnoiet

repo: FaaPz/Slim-PDO


text:
Fix bulk and interrupt buffer size definitions for usb-device-serial

Bulk_Buffer_Size was also used for the interrupt endpoint.

Thanks @ThyMYthOS

authors: Fabien-Chouteau ThyMYthOS


text:
rename DamageUtil methods

getDamageLeft ->applyArmorDamageReduction
getInflictedDamage -> applyProtectionDamageReduction

Or, for consistency with LivingEntity method names, these could be called applyArmorToDamage and applyProtectionToDamage. In any case, the current names aren't particularly descriptive.

repo: FabricMC/yarn


text:
我见过的最垃圾的demo，根本不像是你们公司自己做出来的

我见过的最垃圾的demo

+1

能描述一下具体问题么？是指 demo 编译不了，还是 demo 无法运行或是会崩溃，还是 demo 的功能或是界面做的不好用？

我从github下载的工程，然后用了官网上下载的.a文件，现在运行后使用实时视频检测检测人脸和使用单张图片时控制台信息：初始化失败，modelData 与 SDK 不匹配！，请检查后重试！errorCode:103

￼

这两个按钮点进去都是初始化失败，modelData 与 SDK 不匹配！，请检查后重试！errorCode:103

errorCode 103 可以查到对应的错误码为 MG_RETCODE_INVALID_LICENSE。
在上面的界面中显示，您使用的 SDK 需要进行联网授权，可以参看 wiki 中的介绍 运行一个-Demo 配置正确的 key, secret。

替换了key和secret之后可以了，多谢

请问如果要做刷脸登录的功能的话，按照github demo里的实时视频检测从视频流里检测到人脸之后要怎么处理？要生成一张图片进行对比吗

SDK 中没有提供比对两个人脸的能力，所以要做刷脸登录的话，需要用到云 API 里的 compare 功能。建议去官网的云 API 部分看看。

我现在想在视频流里检测到人脸后导出一张图片，然后去做对比，现在不知道如何导出图片

获得的视频流数据（UIImage）可以保存成 jpg，上传到官网的 API 上用作比对。

有这方面的demo么，github里的工程里没有

这方面的 demo 确实没有。

authors: engebei moon5ckq zziazm

repo: FacePlusPlus/MegviiFacepp-iOS-SDK


text:
fix(token): implement vault token precendence logic

The following token precedence is applied (from highest to lowest):

VKV_TOKEN
VKV_LOGIN_COMMAND
Vault Token Helper, where the token will be written to ~/.vault-token.

If vkv detects more than one possible token source, warnings are shown as the following, indicating which token source will be used:
$> vkv export -p secret
[WARN] More than one token source configured (either VAULT_TOKEN, VKV_LOGIN_COMMAND or ~/.vault-token).
[WARN] See https://falcosuessgott.github.io/vkv/authentication/#token-precedence for vkv's token precedence logic. Disable these warnings with VKV_DISABLE_WARNING.
[INFO] Using VAULT_TOKEN.

secret/ [desc=key/value secret storage] [type=kv2]
└── secret [v=1]
    └── key=*****

As described, one can disable these warning by setting VKV_DISABLE_WARNING to any value.
fixes #305.

FYI @emielkuiper coming with v0.8.2

repo: FalcoSuessgott/vkv


text:
networked_multiplayer_peer.h not found

networked_multiplayer_peer.h has moved from io to core/io so compile fails

in fact, there's a whole lot of issues compiling against master at the moment

repo: Faless/godot-enet-better


text:
Input will hide behind other inputs

Describe the bug
The input will hide behind other inputs and the list wont show up at all
Reproduction - (required - issue will be closed without this)
Here is the snack link snack
Please provide a FULLY REPRODUCIBLE example.

Click to expand!

  import * as React from 'react';
import { View, StyleSheet, TextInput } from 'react-native';
import Constants from 'expo-constants';
import { GooglePlacesAutocomplete } from 'react-native-google-places-autocomplete';

const GOOGLE_PLACES_API_KEY = ''; // never save your real api key in a snack!

const App = () => {
return (
  <View style={styles.container}>
    <View style={{ height: 100 }}>
      <TextInput
        style={{ height: 40, borderColor: 'gray', borderWidth: 1 }}
      />
      <GooglePlacesAutocomplete
        query={{
          key: GOOGLE_PLACES_API_KEY,
          language: 'en', // language of the results
        }}
        onPress={(data, details = null) => console.log(data)}
        onFail={(error) => console.error(error)}
        requestUrl={{
          url:
            'https://cors-anywhere.herokuapp.com/https://maps.googleapis.com/maps/api',
          useOnPlatform: 'web',
        }} // this in only required for use on the web. See https://git.io/JflFv more for details.
        styles={{
          textInputContainer: {
            backgroundColor: 'rgba(0,0,0,0)',
            borderTopWidth: 0,
            borderBottomWidth: 0,
          },
          textInput: {
            marginLeft: 0,
            marginRight: 0,
            height: 38,
            color: '#5d5d5d',
            fontSize: 16,
          },
          predefinedPlacesDescription: {
            color: '#1faadb',
          },
        }}
      />
      <TextInput
        style={{ height: 40, borderColor: 'gray', borderWidth: 1 }}
      />
    </View>
  </View>
);
};

const styles = StyleSheet.create({
container: {
  flex: 1,
  justifyContent: 'center',
  paddingTop: Constants.statusBarHeight,
  backgroundColor: '#ecf0f1',
  padding: 8,
},
});

export default App;

Additional context

Library Version: latest

React Native Version: 0.62

[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
https://i.imgur.com/zeFDWKL.png

Because you are limiting the height of the component, it is hiding the list view.  I don't think this is a library bug.  You can leave the component enough space to render the listview, or wrap the component in a view that will overlay the other components.

yeah but why doesnt the autocomplete input component behave like other input compotnents?

The input component is fine, it is the listview which is being 'hidden', which is arguably expected behavior.
You can pass in a custom input component into textInputProps:
textInputProps={{
InputComp: <Input />
}}

Well then first off
InputComp is not documented anywhere, in this library, or the docs for TextInput
secondly, if you check https://snack.expo.io/137s9pPUO on android and ios
going with the most basic setup,  no height styles.
<TextInput style={{ borderWidth: 1 }} />
<TextInput style={{ borderWidth: 1 }} />
<GooglePlacesAutocomplete />
<TextInput style={{ borderWidth: 1 }} />
<TextInput style={{ borderWidth: 1 }} />

this is the result

You can't tell me that that is expected behavior

And here I managed to dial in on the zIndexing issue when using position: absolute on the list style
https://snack.expo.io/Y!lipqP0R
Firstly, it just looks wrong

And any View component behind the results list, will be ontop, sort of, and pressable instead of the result row

First off, thank you for taking the time to reproduce this and dig into it.
Just so other people reading this know, the correct way to solve this (currently) is to set the zIndex in the container style and position: absolute or fixed in the listView style.

Example
import * as React from 'react';
import { View, StyleSheet, TextInput, TouchableOpacity } from 'react-native';
import Constants from 'expo-constants';
import { GooglePlacesAutocomplete } from 'react-native-google-places-autocomplete';

const GOOGLE_PLACES_API_KEY = ''; // never save your real api key in a snack!

const App = () => {
  return (
    <View style={styles.container}>
      <View>
        <TextInput style={{ borderWidth: 1, height: 40 }} />
        <GooglePlacesAutocomplete
          query={{
            key: GOOGLE_PLACES_API_KEY,
            language: 'en', // language of the results
          }}
          onPress={(data, details = null) => console.log(data)}
          onFail={(error) => console.error(error)}
          requestUrl={{
            url:
              'https://cors-anywhere.herokuapp.com/https://maps.googleapis.com/maps/api',
            useOnPlatform: 'web',
          }} // this in only required for use on the web. See https://git.io/JflFv more for details.
          styles={{
            container: {
              zIndex: 99,
            },
            listView: {
              backgroundColor: 'white',
              position: 'absolute',
              marginTop: 40,
            },
          }}
        />
        <TouchableOpacity onPress={() => alert('taco')}>
          <TextInput
            placeholder="Press here and you wil get an alert"
            style={{ borderWidth: 1, borderColor: 'red', height: 40 }}
          />
        </TouchableOpacity>
        <View style={{ height: 30, backgroundColor: 'orange' }} />
        <TextInput style={{ borderWidth: 1, height: 40 }} />
      </View>
    </View>
  );
};

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    paddingTop: Constants.statusBarHeight,
    backgroundColor: '#ecf0f1',
    padding: 8,
  },
});

export default App;

Well then first off
InputComp is not documented anywhere, in this library, or the docs for TextInput, its also not in the d.ts file

You are right.  Feel free to put in a PR

You can't tell me that that is expected behavior...

If you take out all the styles it would have fit in the box.
If you feel there is a better approach to this (or anything), I would be more than happy to discuss and/or review/merge a PR.

There is a simple solution to this, Jus create a separate view and put the Googleautocomplete tag inside the view.

When I do that, the suggestions don't appear at all.

authors: arulp3 bell-steven dakkafex diklou


text:
[WIP] Dep upgrades: Major version bumps

What's New?

Upgrade Blueprintjs (and update breaking changes going from 1.x to 2.x)
Add react-transition-group to fix popover stuff.
Upgrade Typescript
Upgrade typings and other minor things

Still fixing a CSS issue, but should be ready to merge thereafter:
(weird tooltip placement after BlueprintJS cSS update)

Coverage decreased (-0.01%) to 91.007% when pulling c769977d312735fb0230cd3ea52c95a959a5becb on RickCarlino:dep_upgrades into 308df42953b7177b236da311fb1f7ec8989e5c86 on FarmBot:staging.

authors: RickCarlino coveralls

repo: FarmBot/Farmbot-Web-App


text:
clicksfly.com and shrinkearn.com bypass broken

Domain
clicksfly.com
shrinkearn.com
Link
https://clicksfly.com/st?api=9a5ce7425d5bcd40f9fa14870c4184e9cb63a31d&url=http://mwpaste.com/index.php?v=jPX
https://shrinkearn.com/st?api=e504d153c7a3baa895093ff41aa947915db0b6e2&url=http://mwpaste.com/index.php?v=jPX
Version
0.2161.0
What browsers are you seeing the problem on?
Brave
What OS are you seeing the problem on?
Windows
Anything else?
these web pages redirect to web pages that have a lot of captchas and countdowns
https://user-images.githubusercontent.com/83554130/235057645-d0f5147e-5e5d-4a20-8021-a450de4c8b07.mp4

We do not currently bypass this site based on this list, please read https://github.com/FastForwardTeam/FastForward/issues/656 for more details.
Once we have finished with the project, you are free to reopen the issue.

echo "aHR0cHM6Ly9tZWdhLm56L2ZpbGUvWmRoeEJSaEojVUVZU1dSQXdRclJhZm93ckFDM2lKRDlKVVlKU1dJZ3RJcDFlOHliZ20xcw==" | base64 -s    base64: invalid option -- 's'                                     Try 'base64 --help' for more information.
   ~ echo "aHR0cHM6Ly9tZWdhLm56L2ZpbGUvWmRoeEJSaEojVUVZU1dSQXdRclJhZm93ckFDM2lKRDlKVVlKU1dJZ3RJcDFlOHliZ20xcw==" | base64 -d
https://mega.nz/file/ZdhxBRhJ#UEYSWRAwQrRafowrAC3iJD9JUYJSWIgtIp1e8ybgm1s%                                                             ~ https://shrinkearn.com/full?api=00ca8e6e4054c7078d72481fc3b69790035f9b86&url=aHR0cHM6Ly9tZWdhLm56L2ZpbGUvWmRoeEJSaEojVUVZU1dSQXdRclJhZm93ckFDM2lKRDlKVVlKU1dJZ3RJcDFlOHliZ20xcw==&type=2

authors: 0xc60f artiomborovinskii zekecarter

repo: FastForwardTeam/FastForward

license: Unlicense


text:
Generation from an annotation processor

I have a use case of metadata generation from a self-implemented annotation processor. My idea was to generate the json schema from the same point, but the problem is, you might know, at this point, there is no "Class/Type" available because it is on the build step. There is another group of interfaces (TypeMirror/Element) with a similar level of information but is not compatible with the generator.
So my question is if there is some way to adapt it or maybe another similar project aiming at the annotation processor. Of course, let me know if I'm missing something or looking from the wrong perspective.
In details:
I have some classes being created by the developers on some projects. These projects have a self-developed annotation processor (which I mentioned) extracting some metadata from them. So my idea is also to generate the JSON schema from these classes, which are POJOs with some annotations.
My point is that the JsonSchemaGeneratoraccepts a "Type" reference, while in the annotation processor I just have "TypeMirror", so it is not possible to use the "conventional" way calling JsonSchemaGenerator.generateSchema(type).

This module is not being actively developed (and will be dropped from Jackson 3.0).
You probably want to find another project; and/or ask on jackson-user mailing list.

@cowtowncoder sure, thank you for replying.

authors: cowtowncoder marceloavan

repo: FasterXML/jackson-module-jsonSchema


text:
Create Version Release Numbers(Tags)

Due to composer minimum stability constraints which in my case I prefer stable, the devmaster as the only installation tag breaks, please create release tags(numbers) like 1.0, 1.2 etc to allow for easy installation and specificity in referencing the package in composer.

Would also like to see this and know if this is going to be updated for Laravel 5?

repo: FbF/Laravel-Youtube


text:
no stdout in precomp

Changed _precompilation.jl to avoid having to redirect stdout and to precompile more things.

@andreasnoack this should fix https://github.com/FedeClaudi/Term.jl/issues/190.
I can't be sure because I never encountered that issue in the first place, but I've removed the need for stdout re-direct alltogether based on suggestions in: https://github.com/timholy/SnoopCompile.jl/issues/308#issuecomment-1373496879
Please not that this is being merged in master which currently holds code for the next big release of Term.jl for version 2.0 which introduces many new features and improvements. As such, it might be premature to grab the code from here as there's many not yet documented changes. However if you do want to do that, I'd be very happy to see how you like the new Term!

Just tried this PR on the same machine where I experienced the deadlock and I can confirm that this PR fixes the issue.

awesome thanks for checking it out!

It would actually be helpful if you could backport this fix to a 1.x release. Otherwise it might take a while before we can precompile our package again.

Doing this here: https://github.com/FedeClaudi/Term.jl/pull/194/
I've removed the pre-compilation code alltogether. Once v2.0 drops I strongly recomend switching to it. There shouldn't be major breaking changes but lots of improvements and new functionality.

Please disregard the previous message and other notifications. It seems that I've messed up the commit history badly enough such that backporting those changes is actually not a great idea.
If that works for you I can make a v2.0 release without the precompilation code now. Some of the new features are not fully finished yet but the rest of the code should be just the same as before, except the pre-compilation wouldn't bother you.

Thanks for giving it a try. I'm fine with 2.0 but our project only pulls in Term as an indirect dependency so the upgrade is not under our direct control. We might be forced to stay of 1.x for a bit.

Got it. Sorry I couldn't be of more help, let me know if there's anything I can do!

Took a closer a look. Usually, it's easier to make such a release from a dedicated release branch, i.e. I think it might be sufficient to make a branch similar to this one https://github.com/andreasnoack/Term.jl/tree/release-1.1 from my fork and then make a 1.1.1 from that one. (Or a similar release-1.2 if you prefer 1.2.0.)

yeah so the problem is that I merged a bunch of commits for v2.0 into the master branch (not a great idea) so to grab code that doesn't have this and make a new release without the newer features I would have to revert to a previous commit: 4dda6677e3aa89d1b8edc12b2a7e05da53f1f05a
I can't figure out a way to do that in a way where I can then make a PR without having to grab the most recent code from master.

I can't figure out a way to do that in a way where I can then make a PR without having to grab the most recent code from master.

What I did, was to create the release branch, set it to v1.1.0, and revert the precompile commit, i.e.
git checkout -b release-1.1
git reset --hard v1.1.0
git revert e54f4d2a7a20c0a1698be1286bfa8590cbb87473

There is a very small conflict in the docs project but that's it. Then it could be possible to change the version on that branch and make the release from that branch and leave master as it is.

So I followed those steps and I have a branch with the new code, but I'm not sure how to release it without mergin the PR.  Normally I trigger the bot from an issue (https://github.com/FedeClaudi/Term.jl/issues/170) but I'm not sure how to tell it to pull it from a branch?

You can trigger the release by commenting on the relevant commit, i.e. https://github.com/FedeClaudi/Term.jl/commit/18ede5119b14c4a2de68cc189b8ccd31230f0e5a

The new release should be coming out: https://github.com/FedeClaudi/Term.jl/issues/36#issuecomment-1387068215
I hope it fixes your issues!

authors: FedeClaudi andreasnoack


text:
Suggestion for the part of Resolver/Playerlist

Making keybinds to change the enemy's pitch and yaw with the resolver, so it's more practical than opening the menu and clicking on the playerlist
Like this: https://i.imgur.com/nl9qk5l.png

I've had this idea for a little bit but it would be on the closest enemy to your FOV.

authors: lGabryl xxmyn

repo: Fedoraware/Fedoraware

license: WTFPL


text:
Update to 1.20.4 & Try to Fix #19

Update to 1.20.4
Add a PNGConverter to fix #19

咕了很久了 准备更新了

authors: FengLiuFeseliud GLDYM

repo: FengLiuFeseliud/CloudMusic-Mod


text:
Can i execute SD Graph in runtime mode?

Hi FernRP!
Can i execute SD Graph in runtime mode?
I tried this code, no errors, no reaction from the a1111 terminal.
Thanks for answer!
using System.Collections;
using System.Collections.Generic;
using UnityEngine;
using FernNPRCore;
using FernNPRCore.SDNodeGraph;
using UnityEngine.SceneManagement;

public class SDGTest : MonoBehaviour
{
    public StableDiffusionGraph sd;

    void Start()
    {
        sd.LinkToScene(SceneManager.GetActiveScene());

	SDStartNode ss;
	sd.nodes.ForEach((n) =>
        {
            if (n != null && n is SDStartNode)
            {
                ss = n as SDStartNode;
				ss.OnExecute();
	    } else { return; }
        });
   }
}

Theoretically it should be runtime capable, but I haven't tested it yet, I'll test the following in a few days and try to support runtime.

repo: FernRP/FernSDGraph


text:
[Question] Internet explorer 9 support status

Hello,
Just a quick question. I work in a company that still has to support IE9, I love your library and want to use it in our components library but it has to be IE9 compatible.
I see that your tests run on IE 10, what is the status of IE9 ? "might work but don't count on it", or "forget it we use features that will never work on IE9" ?
Thanks in advance and thanks for the great work on this library. If it's not right now, we will definitelyuse your library when we finally drop IE 9 support :)

Hi, in the past the library worked on IE9 but I then dropped the support because it required a lot of hacks and specific code to make it work properly and the time needed wasn't worth it.
You may try to run the test suite against IE9 and see how many of them fail to get an idea of what's the status is.

authors: FezVrasta onigoetz


text:
Refactor tests to use pom and add Readme file

Tests were refactor to use POM.
Please review and decide if we go with this option. You can compare with existing tests from staging branch.
Please review Readme and add your suggestions.

[x] I have checked that no one else is working on similar changes.
[x] I have read the latest README and understand the development workflow.
[x] The name of this branch is: feature/<branch_name>, or hotfix/<branch_name> if this is a hotfix. The branch is created in a cloned version of this repo, not a forked repo.
[x] This branch is rebased/merged with the latest staging (or the latest production if it is a hotfix).
[x] There are no merge conflicts.
[x] There are no console warnings and errors.
[x] On the right hand side of this PR, I have linked the appropriate issue(s) under "Issues" and added a project progress under "Projects".

Tests look good, just some minor comments.

Just approved it as well.

@idjevm
Can you merge my PR? I see a message that I'm not authorised to merge.

authors: galeza jessica-lau

repo: FightPandemics/FightPandemics


text:
🛑 logs.zzls.xyz is down

In 2c245cd, logs.zzls.xyz (https://logs.zzls.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: logs.zzls.xyz is back up in 1d20a15.

repo: Fijxu/justlog-instances-uptime


text:
🛑 logs.zzls.xyz is down

In 13acc26, logs.zzls.xyz (https://logs.zzls.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: logs.zzls.xyz is back up in 79881e5.


text:
🛑 logs.lucas19961.de is down

In 91a2099, logs.lucas19961.de (https://logs.lucas19961.de/) was down:

HTTP code: 502
Response time: 762 ms

Resolved: logs.lucas19961.de is back up in d428042 after 12 minutes.


text:
🛑 Hacker News is down

In 9d14be5, Hacker News (https://news.ycombinator.com) was down:

HTTP code: 502
Response time: 190 ms

Resolved: Hacker News is back up in beb86c9.

repo: FilipHeremans/status


text:
Declaration of m140501_075311_add_oauth2_server::primaryKey($columns) should be compatible with yii\db\Migration::primaryKey($length = NULL)

The command
./yii migrate/up --migrationPath=@vendor/filsh/yii2-oauth2-server/migrations

Throws with ErrorException with the message "Declaration of m140501_075311_add_oauth2_server::primaryKey($columns) should be compatible with yii\db\Migration::primaryKey($length = NULL)" when using yii 2.0.10-dev
To solve this I propose to create a new method instead of using the existing one.
public function primaryKeyColumns(array $columns)
{

}

and use that instead.

@Faryshta Hi, if you empty this method -- you have no any pimary keys on tables and need to add them manually. Check this PR with fix your issue.

found just fixed @master branch

thanks @brutto sadly the jwt support in the master branch seem to have derrailed the entire repo. It doesn't run at master anymore, i had to fork this and probably will have to fully fork it soon if things doesn't improve

public function primaryKey($columns=null) {
    return 'PRIMARY KEY (' . $this->db->getQueryBuilder()->buildColumns($columns) . ')';
}

Parameters need default values
primaryKey($columns=null)

authors: Faryshta brutto windhoney


text:
Update CREDITS.txt

Credited myself

I am not sure if this is the right way, or if I only need to Press “Commit changes” after editing.

This should really be part of the other pull request, but don't worry, I'll accept it anyway

authors: FinalForEach maralnor

repo: FinalForEach/Cosmic-Reach-Localization


text:
ie11 - Object doesn't support property or method 'entries'

This page uses a few es5/es6 array prototype, but really nothing crazy. I'm only having this issue on a single page, and I'm fairly certain this issue is new (but it's difficult to know for certain when this issue came up because only a few clients use ie11)

Hi @jwerardi , it looks like you've got an error in your website that you've tracked down to the code you're loading from the polyfill service. It would be really useful if you could follow these steps.

Create a test case using an online tool like JSBin, which loads only the polyfill service script, and then includes inline any code required to trigger the problem (which should be no more than a few lines).
Raise a new issue on our issue tracker, and include:

A description of the problem (what you expected, what actually happened)
A link to your test case on JSBin (or jsfiddle/codepen/whatever)
The exact name and version number of the browser you're testing in
If relevant, the console output or a screenshot of the problem

We ask for a JSBin demo because often these kinds of errors are actually errors in the host website's code, and even if they are a problem in the polyfill, we don't have the resources to debug your application.  Please also make sure you disable any browser plugins when you are testing in JSBin, so you are certain that you are only running the test code.

Sure no problem! Makes sense, thanks for the timely response. I'll create a new issue after following your steps.
Thanks for the product by the way, it's a real life saver.

authors: JakeChampion jwerardi

repo: Financial-Times/polyfill-service


text:
How to use Finbuckle with Identity and EntityFramework in Asp.net

Please provide some example to do this as I am finding this doc  at this url:
https://github.com/Finbuckle/Finbuckle.MultiTenant/tree/main/samples/ASP.NET Core 3/IdentityDataIsolationSample
quite messy.
please help

hi @shreya-groot
I agree the sample isn't a good as it could be -- it tries to show a few different things.
Let me ask you a few questions and I'll give you some specific advice:

are you using a shared database or separate databases per tenant?
which multitenant strategy are you using?
are you using the default Identity UI?
do you have multiple db context classes? 1 for Identity and 1 for the rest of the app? Or do you have a single shared db context?

Any other specific problems you are running into?

Hello Andrew,
I am having problem to implement Finbuckle
as I am having following specifications in it:

I am using Identity in Asp.Net
2.I am having one database that has be shared among all tenenat
I need to filter data corresponding to particular tenant by queries

Please guide me
Thanks & Regards
Shreya
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Andrew @.>
Sent: 20 April 2021 08:55
To: @.>
Cc: @.>; @.>
Subject: Re: [Finbuckle/Finbuckle.MultiTenant] How to use Finbuckle with Identity and EntityFramework in Asp.net (#418)
hi @shreya-groothttps://github.com/shreya-groot
I agree the sample isn't a good as it could be -- it tries to show a few different things.
Let me ask you a few questions and I'll give you some specific advice:

are you using a shared database or separate databases per tenant?
which multitenant strategy are you using?
are you using the default Identity UI?
do you have multiple db context classes? 1 for Identity and 1 for the rest of the app? Or do you have a single shared db context?

Any other specific problems you are running into?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Finbuckle/Finbuckle.MultiTenant/issues/418#issuecomment-822944988, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASHXH4YVWH4LCXRB6L476LDTJTXY7ANCNFSM43CQO4OQ.

@shreya-groot
in your app how do you detect the tenant? Does each tenant have a different url or hostname or do you do something completely different?
Before getting into the Identity MultiTenant Sample do you understand these samples?

RouteStrategySample
DataIsolationSample (not the Identity one -- this one shows the basics that Identity builds on)

Actually I am allowing the user to login and I will use his  AspNetUserId from that which I assume to be same as tenant id which has been inserted in tenant table while registering the user
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Andrew @.>
Sent: 20 April 2021 09:23
To: @.>
Cc: @.>; @.>
Subject: Re: [Finbuckle/Finbuckle.MultiTenant] How to use Finbuckle with Identity and EntityFramework in Asp.net (#418)
@shreya-groothttps://github.com/shreya-groot
in your app how do you detect the tenant? Does each tenant have a different url or hostname or do you do something completely different?
Before getting into the Identity MultiTenant Sample do you understand these samples?

RouteStrategySample
DataIsolationSample (not the Identity one -- this one shows the basics that Identity builds on)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Finbuckle/Finbuckle.MultiTenant/issues/418#issuecomment-822953789, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASHXH445IRYIAQ2AHUFBF7LTJT3DPANCNFSM43CQO4OQ.

And Also I don’t want to put tenant configuration in appSetting.json file as done in these two strategies
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Andrew @.>
Sent: 20 April 2021 09:23
To: @.>
Cc: @.>; @.>
Subject: Re: [Finbuckle/Finbuckle.MultiTenant] How to use Finbuckle with Identity and EntityFramework in Asp.net (#418)
@shreya-groothttps://github.com/shreya-groot
in your app how do you detect the tenant? Does each tenant have a different url or hostname or do you do something completely different?
Before getting into the Identity MultiTenant Sample do you understand these samples?

RouteStrategySample
DataIsolationSample (not the Identity one -- this one shows the basics that Identity builds on)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Finbuckle/Finbuckle.MultiTenant/issues/418#issuecomment-822953789, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASHXH445IRYIAQ2AHUFBF7LTJT3DPANCNFSM43CQO4OQ.

Please help me to create a Tenant when I am using Identity to let the user login inside my ASP.Net Core app

@shreya-groot  I'm sorry for the slow responses
You want to create a a tenant when a new user registers? Will your tenants have multiple users or will it be one user per one tenant?
You can create a new tenant by using the IMultiTenantStore<T>.TryAddAsync method which requires a TenantInfo object of type T. Not all of the stores implement this method though so you might have to create your own store.
Then when you need to create a new tenant you just create a new tenant object instance as required then call the TryAddAsync method on your IMultiTenantStore<T> store instance which you can get the store from the DI system in most cases.

My tenant will have multiple users further.
First of all I want to know which strategy I should use out of so many as I only want to create Tenant with so many users under him
In Asp.net core I have created all the users who can sign in into my application, but I want to make them specific to tenant, means I want to associate one tenant with each user without working on any routing.
please give me some example relateed to that.
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10
From: Andrew @.>
Sent: 28 April 2021 08:43
To: @.>
Cc: @.>; @.>
Subject: Re: [Finbuckle/Finbuckle.MultiTenant] How to use Finbuckle with Identity and EntityFramework in Asp.net (#418)
@shreya-groothttps://github.com/shreya-groot I'm sorry for the slow responses
You want to create a a tenant when a new user registers? Will your tenants have multiple users or will it be one user per one tenant?
You can create a new tenant by using the IMultiTenantStore.TryAddAsync method which requires a TenantInfo object of type T. Not all of the stores implement this method though so you might have to create your own store.
Then when you need to create a new tenant you just create a new tenant object instance as required then call the TryAddAsync method on your IMultiTenantStore store instance which you can get the store from the DI system in most cases.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Finbuckle/Finbuckle.MultiTenant/issues/418#issuecomment-828109651, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASHXH45KYFFAMHPQM5NEZQTTK54OHANCNFSM43CQO4OQ.

@shreya-groot it sounds like you are not using isolated Identity databases for each tenant and prefer to have a single Identity database where the tenant is associated with each user. In that case take a look at the "Shared Login" sample. It is ASP.NET 2.1 but the basic idea should still work. It will have a user login, check which tenant that user is, then use that tenant for all requests for that authorized user. No route or anything like that is needed.

@shreya-groot
I too have similar requirement .. did you got any solution for it ?

I have same requirements :) Would love to see some solutions for this :)

authors: AndrewTriesToCode StefanRadosavljevic shreya-groot vasanth32


text:
S3 Upload Failure when chunks > 10000

Bug - Maybe Feature Request?
S3
Version: 5.11.9
Chrome, maybe others
Mac OS X, maybe others

Select a file greater than 50GB
Set chunk size to 5MB (Default)
Upload

Failure will always happen at the first chunk > 10000.  We receive a Bad Request from S3 Server.
Looks like this is a limit of Amazon S3: http://docs.aws.amazon.com/AmazonS3/latest/dev/qfacts.html that doesn't seem to be documented in fineuploader anywhere.
The uploader should know this limit and warn or change chunk size to accommodate the limit.
Workaround would be to set chunk size to 10.5MB to allow files up to 100GB...but that would not get us to the 5TB limit of which would require a chunk size of 525MB.  Is chunk size stored with the resume data?  Could chunk size be set on a per file basis?

Chunk size is only configurable for all files as an initial config option. The best option would be to limit the upload size based on your configured chunk size.

Another option would involve updating the codebase to expose an option that automatically adjusts the chunk size to an optimal setting before the upload begins, taking into account the file size.

The optimal solution from my perspective would be to have a setting be for minimum/default chunk size that is used for all files, unless that would cause more than 10000 parts to be created, then the chunk size would be file size / 10000.  The chunk size would get stored locally for resume.  This would be very similar to your second suggestion.

Yes, that sounds like a good approach. I think a change at https://github.com/FineUploader/fine-uploader/blob/c1b4954f21381dbd664e379abf571c988e2265c0/client/js/upload-handler/xhr.upload.handler.js#L222 may be all that is needed. But unit tests would need to be added as well.

I took a look through that code, but not familiar enough with it to make code changes.  Seems like the tricky part would be to deal with chunk size in the persisted state.
Simple unit test would attempt to transfer a 1MB file to Amazon S3 with minimum part size set to 100 bytes, which should break up into a little over 10000 chunks.

Unfortunately there are no simple changes in a codebase of this age and complexity. This has the potential to break any chunked uploads that are waiting to be resumed from localStorage. So that will need to be accounted for.

I assume any config change to partSize would break uploads waiting to be resumed.  Technically a modification like this wouldn't change partSize from the global configuration unless it was specified differently in localstorage for that specific file.
Thinking this through,any destination could have a maximum part limit, so each extension of XhrUploadHandler should define this someplace and _getChunkData should use that limit to determine # of parts and actual chunk size if larger than maximum parts.

Long time coming, but I expect to address this in #1916. Probably will allow a function to be returned from chunking.partSize. The function would be invoked by Fine Uploader with the file ID. Integrators could determine the optimal partSize, and this would not be S3-specific.

authors: EZWrighter rnicholus

repo: FineUploader/fine-uploader


text:
Add Consecutive Forcing w/ Toggle

Add support for consecutive forcing of notes in the same lane(s).

Hi there, would you be able to explain what is meant by "consecutive forcing" is in this context? I'm not entirely sure of the intended behaviour based on that description.

What it does is when active, it removes the restriction for forcing consecutive notes in the same lane
as shown in the following image: (Ignore the display windows in the top left, those are something I added to my own personal version)

This is a restriction that many people (myself included) install older versions of Moonscraper to use bugs to circumvent, however, having worked with it being outright removed instead of a toggle in my own personal build, it can interrupt some workflow habits so I made it a toggle.
As for the confusing phrasing, I had initially wanted to phrase it as "Enable Consecutive Same-Lane Forcing:" but just ran out of space.

Oh so this removing the sequential HOPO restriction. What's the intended use-case for doing this? This behaviour will result in what would be considered broken charts on games that do not manually correct this behaviour, e.g. this will result in broken HOPO behaviour on GH3.

Clone Hero and YARG are the intended use cases. I was unaware of the issues it would cause in GH3 but if that's the case, then I don't see why a compatibility warning can't be added (like with offset time signature markers for CH)