fix: room name field does not automatically focus when returning from the chat option

Details
Adds the useDelayedInputFocus hook which auto focuses an input after the specified delay.
Fixed Issues
$ https://github.com/Expensify/App/issues/27607
PROPOSAL: https://github.com/Expensify/App/issues/27607#issuecomment-1722314235
Tests

Enable the policy rooms beta, or all betas
Launch Expensify
Open the global create menu and select Send message
Click on the Room tab if it is not the active tab.
Verify that the room name input field gains focus.
Click on the Chat tab.
Click on the Room tab.
Verify that the room name input field regains focus.
Repeat steps 6 through 8 a few more times.

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

Offline tests
N/A
QA Steps
Same as tests.

[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/4160319/6bdc9cfa-6f79-42c4-8990-6dbb9793d314

Mobile Web - Chrome
27607-android-chrome.webm

Mobile Web - Safari
https://github.com/Expensify/App/assets/4160319/7ea35e92-c923-482c-91d7-cc289a887859

Desktop
https://github.com/Expensify/App/assets/4160319/dea14694-0a2e-477a-85ef-c4910d00e5b8

iOS
https://github.com/Expensify/App/assets/4160319/a76e8bdc-d043-4957-8dcb-a97df8622d1d

Android
27607-android-native.webm

Kindly fix merge conflicts as well

Kindly fix merge conflicts as well

@abdulrahuman5196 Done.

Reviewer Checklist

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

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

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

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] 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
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is 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 verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

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

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

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

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

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(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.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/46707890/11736142-5567-4e04-91a9-8ea0cb2699ec

Mobile Web - Chrome

https://github.com/Expensify/App/assets/46707890/bde26707-c260-4fb9-967d-58a56e61b344

Mobile Web - Safari

https://github.com/Expensify/App/assets/46707890/45394d93-9a1b-4800-9186-20b69b8cf159

Desktop

https://github.com/Expensify/App/assets/46707890/aff7a2b8-d010-4dc7-820f-0fbe5d66c724

iOS

https://github.com/Expensify/App/assets/46707890/be1ae3e5-c7a9-4e50-a253-faeb35c2bdca

Android

https://github.com/Expensify/App/assets/46707890/bb9d1ce5-29b7-423c-b063-86cde7c340ae

: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/robertjchen in version: 1.3.79-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.79-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.79-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
cancelled 🔪

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/jasperhuangg in version: 1.3.79-5 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


Improve error handling

Remove usage of anyhow in library code, improve ImageLoaderError instead.
Cleaned up some of the image loading code and made the API a little more flexible.
Removed usages of find_images within load_images. Ideally, one should call find_images before using load_images once instead, and then load all the resulting images.

Also note that I ran cargo format, so that may have made changes to other files, I didn't bother to check for that. If it did, would be a you problem, image not running cargo format.

Removed dev container config from git history.


Enable basic functionality

Some time ago we decided to disable the operator temporarily. This PR enables the operator functionality back and does the following:

Read the supported provider list from configmap.
Install upstream CAPI operator, when we get a stable fork, it should be managed by CVO.
Create CoreProvider CR.
Create InfrastructureProvider CR based on provider list input.
Add custom versioning for CAPI components

/retest

/retest

/retest

/retest

/retest


Cannot Change Scale Adapter Error

When trying to create a new adapter device (or edit an existing device), an error is thrown:
plugin does not define method scale_type_changed

Fixed in PR #7


Adding documentation for Plugin

Add documentation to capture how data is generated and used by the API for plugins

Updated:  https://github.com/chanzuckerberg/napari-hub/wiki/Eng-Tech:-Plugin-Metadata


Editable table grid for

Make tabular data editable from the table. Perhaps with EditableGrid

While cool, the editable module for jquery data tables is a bit pricey for now. But...want to come back to it.


setmind doesn't work on ghosts?

Description

Haven't thoroughly tested but I don't think setmind is working on ghosts anymore. Expected behavior is for it to force the player to control the entity, I think what it does is reassign their body so they have to return to it manually.

AFAICT the mind transfer still succeeds. i.e., if they use the return-to-body button they go the the new entity. I guess there should just be an option to also cancel any current "visits" when transferring.

Ah nvm, thats already an option, the command just doesn't use it


chore: remove license from pull request template

Description of changes
(Give an overview. Add a technical description describing your changes.)
Pull request checklist

[ ] Addresses an existing issue: Fixes #0000
[ ] Added relevant unit test for your changes. (yarn test)
[ ] Verified code coverage for the changes made. Check coverage report at: <rootDir>/test-results/unit/coverage
[ ] Ran precheckin (yarn precheckin)

Codecov Report

Merging #31 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #31   +/-   ##
=======================================
  Coverage   95.02%   95.02%
=======================================
  Files          17       17
  Lines         342      342
  Branches       17       17
=======================================
  Hits          325      325
  Misses         17       17

Continue to review full report at Codecov.

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


Fix Placeholders

Currently the library is trying to draw placeholders twice. The empty function drawPlaceholders rewrites the placeholder to empty. This PR removes the drawing over

@saltyskip could that be why I can't set the placeholder's insets via the following methods?
override func textRect(forBounds bounds: CGRect) -> CGRect
override func editingRect(forBounds bounds: CGRect) -> CGRect
override func placeholderRect(forBounds bounds: CGRect) -> CGRect

I removed drawPlaceholder(in rect: CGRect) in a fork and now the placeholder is "doubled" in a weird way (one is at desired inset 10 and the other is at inset 0, example placeholder being YY).

Hi, the reason for drawPlaceholder to be overridden with an empty function body was what @KarlHarnois mentioned:
Without this override, the placeholder is drawn twice on the text field. When running your branch, you'll notice that some placeholders occasionally appear darker than they should due to this issue.
@KarlHarnois : In order to create leading/trailing insets for the text field content, you can use imageViewLeadingInset, imageViewTrailingInset, accessoryButtonLeadingInset, accessoryButtonTrailingInset which create some padding around the card image view and accessory button respectively.

Issue with duplicated placeholders.

@KarlHarnois Do you find any method find placeholder insets?
I am having the same issue, with above method not able to set placeholder insets


Document how to manually upgrade a CAPI cluster

Task
Document how to manually upgrade a CAPI cluster using releases. Both GitOps and non GitOps use-cases need to be considered.
Background
CAPI clusters are being used by our customers and many clusters need to be upgraded from v25.x.x to v29.x.x.
The public documentation doesn't contain any information on how to upgrade a CAPI cluster.
The kubectl gs update cluster command doesn't work for CAPI clusters.

The kubectl gs update cluster command doesn't work for CAPI clusters.

It actually does now, we fixed it 2 weeks ago.

I guess the most important would be to document how to do it in the GitOps scenario, which most CAPI customer rely on, or would the kgs command also help with that?


448 Prevent dupicate collaboration requests

Pull Request Overview

API now checks if a Collaboration request already exists between two users and if so returns that rather than creating a new one
Test added for the scenario

/rebase


Not listed yet: www.macrumors.com

The website at this url is unlisted: https://www.macrumors.com/2019/02/21/safari-ios-12-2-intelligent-tracking-prevention/

This website is now in the support list and will be in the next release of the GCM web extension on addons.mozilla.org
Thanks!


Trigger server event on input set/change

it's not just bound  choice field but ill put it as an example
ex 1:
trigger server event when choice field selected, for my case i want to use the choice field value and filter data to generate another choice field based on it
ex 2:
Trigger server event when for example input1 and input2 are present

Closing for now, I believe this is supported. Please provide a more in-depth description of your request if you think otherwise!


Topic/docker release

Closes #88
To see the PR in action you can take look at following links. As I already tested it.
github (ghrc):
https://github.com/ohdearaugustin/headscale
docker hub:
https://hub.docker.com/r/ohdearaugustin/headsacle/tags?page=1&ordering=last_updated

Should this PR Update the readme with the appropriate urls and information to make it apparent to the end user?

Small typo on dockerhub? -> ohdearaugustin/headsacle

Should this PR Update the readme with the appropriate urls and information to make it apparent to the end user?

I will add some infos to the readme.

What is the state for this PR?

@ohdearaugustin could you please send me the creds to<EMAIL_ADDRESS>?
Apologies for the delay!

@juanfont you got a mail. Added some docu.

Fantastic! Merged!


auto complate performance

a little improvement for better auto complate performance

I've updated the code and now the algorithm only calls the API when the user stops typing. I also implemented a few resources that will do something close to this. Do you think this is still necessary?


Custom handling for StructDeconstructLibfunc.

This change is

crates/cairo-lang-sierra-generator/src/store_variables/known_stack.rs line 182 at r2 (raw file):
Previously, orizi wrote…
won't keeping track of "range" instead of "index" solve this issue?
(the handling done per index would be done for the start and the end values)

Maybe, but it is a large change and I'm not sure it is worth the effort.


Persist Kademlia cache to disk

aims to close issue #673

It's failing some tests right now, so drafting this