📑 Feature Request: Adding infinite scroll to the issues of a repository (see image)

IMPORTANT TO CHECK BEFORE ISSUE

[X] You check that same issue is not present in the repository
[X] You have read contribution guidelines and rules

Please describe your feature request related to a problem?
So what i want is i want that there will be a infinite scroll feature in the place where all the issues are shown means if the issues are so many then it will not be optimal to load all the issues at a single time.
Describe your solution to problem
Insted what we should do is that we need to create a infinite scroll in which as the user moves down just before going to the end more issues will load just like in the instagram or other infinite post apps in which list is so long or infinite and it is usefull here because issues of a repo can be so many if it is a large repo and many people are contributing to it.
Describe alternatives you have considered
No response
Additional context
@rahulsainlll Assign this to me under gssoc 2024 ext and hacktoberfest i will work on this issue.
Add Relevant Screenshot (if available)

@tarunkumar2005, can you assign me?


Cluster analysis

Please maintain seperate branch for different fetures.

I forgot to create a new branch. I will keep that in mind for further tasks.

Fix the conflicts!!


feat: allow for custom io_service (#390)

Fixes #390

Hi @mscofield0 thanks for your contribution. This looks but it's a backwards incompatible change. Could you add a second constructor of the clientI() class without parameters that just creates the default options?

Thanks for your contribution @mscofield0 ! The build fail seems to be an outdated catch library issue so everything good 😊


Wip sockmap v3

work-in-progress: sockmap v3... try again with a couple fixes.

This change is

test-me-please

v4 out


Documentation integration

Having seen Seb's recent JS's Date bindings, they look great.
However something I feel is missing is a way of generating links to documentation so that ocamldoc'd mlis have direct links to the documentation of the bound function (see e.g. the documentation of functions in tgls, automatically generated, or tsdl, manually done with a lot of query-replace-regexp). These are small touches but they have a huge productivity impact when you are working with the binding.
Most of the time it is sufficient to be able to define an URI pattern where a variable is substituted by the bound method name (and the ability to override in case of exceptions). Now one of the problem is that you don't generate the mlis. If your eventual goal is to generate mli's from other descriptions then this could actually be done at that time, otherwise you might consider generating mli's aswell from the annotated mlis and provide support for automatically generating doc strings.
The other problem is to find a good and reliable source of documentation for the browser APIs, directly linking on the standards may be a little bit dry. I tend to use mozilla's developer documentation which has links to the standards and information about browser support. See e.g. the Date documentation.

This is a very good point.
In the medium term (once codoc take over ocamldoc), documentation comments will be extract from comments, and one could very well use gen_js_api as a ppx mapper on .mli interfaces that will insert extra docstrings obtained from generic heuristics.


Switch from python-jose to pyjwt

Is there a plan to migrate from python-jose to pyjwt? Python-jose isn't maintained any more and contains some known vulnerabilities.
I noticed that there was some effort done in #41 , but not sure what happened to it. As an intermediate solution, we could perhaps move to python-jose[cryptography] which is already recommended above the default python-jose (with Python backend)?

@siebediels i just tested locally these modifications in #41 and they just work out-of-the-box. i'd just merge that one PR and go ahead

if needed - i can make a PR. for now i have a working local version of code

aaight... lezz do this https://github.com/dorinclisu/fastapi-auth0/pull/43

i've made some updates and some more fixes to the PR. enforced some verifications by default, unless a developer overrides them explicitly.
now - i like it. lets wait for the @dorinclisu to come back to us
additionally, i'd like to remove the email namespace parsing. to get the email you need to call Auth0Management API directly. i think. also this is private data leak if one includes the email in tokens (so be careful)

bump.
unfortunately, no activity on my PR :(


New Version 2021-06-01 for Azure Site Recovery.

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[x] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[x] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[x] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[x] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@ArcturusZhang/@chunyu3 Please review

{

this file has become too large to review properly (github won't even show the diff). In the next PR for this service please split these APIs up into separate swagger specs

Refers to: specification/recoveryservicessiterecovery/resource-manager/Microsoft.RecoveryServices/stable/2021-06-01/service.json:1 in aa7e4f7. [](commit_id = aa7e4f74ba0fa8c7714a1fa1de3801eb3bc5559a, deletion_comment = False)

This PR should not go in until https://github.com/Azure/azure-rest-api-specs/pull/14930 goes in as that is an older API version and touches the same spec with overlapping changes.  Comments in that PR need to be addressed and applied to this PR as well

/azp run

@chunyu3 , Apologies for the las minute update, but it seems we had missed out on a commit in this PR. Would it be appropriate to add it here?

@chunyu3, we will let you know once we are ready to merge this PR.

@imshashwataggarwal asked not to merge this PR now until manifest deployment was completed.

@imshashwataggarwal asked not to merge this PR now until manifest deployment was completed.

@chunyu3, can you please merge the PR now.


Add recovery id calculation when signing ethereum call transactions

Problem
Currently there is no way to calculate recovery id (v) when we sign ethereum transactions from go SDK.
Solution
The recovery ID is an index from 0 to 3, which indicates which of the 4 possible public keys is the correct one. Because the key recovery operation yields multiple potential public keys, the correct key must either be stored alongside the signature or you must be willing to try each recovery ID in turn until you find one that outputs the key you are expecting.
Recovery operation is described in SEC1v2, section 4.1.6.
Alternatives
No response

Moving to backlog for now.


Rename biosample_category_enum to follow naming standards

@turbomam I'd appreciate your green signal for the changes to biosample_category_enum before I make changes to other enums. I have touched many different files while renaming - is that okay or should I stick to just nmdc.yaml? Also, is nmdc.owl.ttl autogenerated or do I need to rename the enum in this file as well?

The files in project/ are also always regenerated by make all

So it's good that you run make all as part of your testing. Just don't commit any YAML or JSON files in nmdc_schema/ or anything in project/

I'm going to merge but you can continue to work out of this branch and make more PRs


Break the changes to modular.css

Related Issue
Broken down the changes of globals.css to modular.css
Closes: #194
Description of Changes

Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] I have included comments in areas that may be difficult to understand.
[x] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots

Original
Updated

Please provide any necessary screenshots to illustrate the changes made.

Please resolve conflicts and check vercel deployment

Nice changes! Well done... But yess Needs more refactoring.. Some class names are not good. Please see needs more modularity and change the class name so it is understandable what does it do

Okay alright. I will make the changes

There is an error! I checked on local many CSS properties altered. I am worry!!

deployment shows error here @anmode is it?


Woo-commerce Currency Position Set Dynamically.

Hi Anisur,
maybe communicated not clear enough. Sorry, my bad.
Please use https://github.com/bootscore/bootscore/tree/v6.0.0-beta1 branch for changes and pull requests. This is the branch where your previous changes are merged. Creating PR's from main branch leads into issues.
It's just about the total items currency symbol in the mini-cart. Please check here https://dev.bootscore.me/shop/
I used following settings in Woo dashboard:

If a product is added to the cart, the totals price currency symbol is not displayed correctly. When changing the quantity, currency symbol is displayed correctly:

After adding to the cart
After changing quantity

Thank you


Is there a way to insert header section that will automatically be included on all pages?

If you're on Firefox, you can use display:fixed for this purpose. But for Chrome/Safari, there's no solution AFAIK.


Update to allow releases from Block account

<developers>
    <developer>
      <id>Block</id>
      <name>Block, Inc.</name>
<EMAIL_ADDRESS><!-- TODO Update this to Block, Issue #1) -->
    </developer>
  </developers>

Dependencies:

https://block.atlassian.net/browse/CAE-8460
The create the email/group
Set this up as a GH Account much like tbd-releases
Create a personal access token we can use for releases
Set that PAT in GitHub Actions config

Done via linked commits. Note that we are not going to release using a system account as we did for TBD w/ the TBD Release Manager. Instead, we have write permissions using the embedded GITHUB_TOKEN to push to git, and those commits then are associated with a bot account with name block-release-manager[bot]. For instance see f6276d43fc1e881fc4971f45c0552782bc5664dc for an example of this type of commit.


nxos-bootstrap backtrace when NXOS fails to respond

When nxos-bootstrap is in the "AWAIT-ONLINE" state, and the device never comes online, the nxos-bootrap program raises:
2016-12-05 14:37:32,384:ERROR:<IP_ADDRESS>:stderr=Traceback (most recent call last):
  File "/opt/aeonztps/bin/nxos-bootstrap", line 403, in <module>
    main()
  File "/opt/aeonztps/bin/nxos-bootstrap", line 392, in main
    dev = wait_for_device(countdown=g_cli_args.reload_delay, poll_delay=10)
  File "/opt/aeonztps/bin/nxos-bootstrap", line 161, in wait_for_device
    message='Failed to probe target %s within reload countdown' % target))
  File "/opt/aeonztps/bin/nxos-bootstrap", line 116, in exit_results
    post_device_status(dev=dev, target=target, state='FAILED', message=results['message'])
  File "/opt/aeonztps/bin/nxos-bootstrap", line 217, in post_device_status
    ip_addr=target or dev.target,
AttributeError: 'NoneType' object has no attribute 'target'

The bug here on line 217 is to not do this:
dev.target

I have a simple fix for this issue, but the root cause is that sometimes it fails in the do_push_config1 function for this reason
2017-02-05 09:17:03,066:INFO:<IP_ADDRESS>:pushing all config to device
2017-02-05 09:17:07,857:CRITICAL:<IP_ADDRESS>:unable to push config: % Invalid command
the 'all.conf' config has simply 'service unsupported-transceiver'.

Submitted the fix in PR#153


update address generation

What this PR resolves:
https://github.com/threefoldtech/jumpscale_lib/issues/88

Oh crap!

updated


Support for elevation or a building level planned?

How can an extension of open location code look with the elevation or a building level included?
E.g. if you want to meet it would be nice to know the building level of the room or if it is under or on a bridge :)

see #25

Thanks @mprins !


server: Export more container metadata for VM containers

VM base container runtimes (e.g. Clear Containers) will run each pod
in a VM and will create containers within that pod VM. Unfortunately
those runtimes will get called by ocid with the same commands
(create and start) for both the pause containers and subsequent
containers to be added to the pod namespace. Unless they work around
that by e.g. infering that a container which rootfs is under
"/pause" would represent a pod, they have no way to decide if they
need to create/start a VM or if they need to add a container to an
already running VM pod.
This patch tries to formalize this difference through pod
annotations. When starting a container or a sandbox, we now add 2
annotations for the container type (Infrastructure or not) and the
sandbox name. This will allow VM based container runtimes to handle 2
things:

Decide if they need to create a pod VM or not.
Keep track of which pod ID runs in a given VM, so that they
know to which sandbox they have to add containers.

Signed-off-by: Samuel Ortiz<EMAIL_ADDRESS>

Adding @laijs and @mcastelino.

Are you sure that you don't want this to be done inside the config.json with a VM configuration option? I get that it's a bit of a niche thing, but since Linux has namespace paths this is something that should be handled inside the spec IMO.

LGTM

@cyphar You mean something along those lines ? This might be a cleaner long term solution, although this PR itself would not be enough (It would need additional information to let us know if a container is going to be running on an existing VM or if there's a need for creating one).
Given that the current PR has not been merged for the past 6 months, that at least one key OCI spec contributor NACK'ed it, and that we would need an extension to it, I do not see it as a viable short term solution for now.

Yeah, I disagree with their points. :wink: But in that case, I don't really mind all that much -- we can just pass annotations as a "temporary" hack anyway (we lose nothing from it).

Yeah, I disagree with their points. :wink:

I guessed that much :) Let's see if this PR ever makes it to the spec and we can support it from CRI-O when that happens.

LGTM

LGTM

LGTM


Query: Allow translations through DTO objects

DTO which are projected out, (from any level) are materialized correctly with typed projection shaper
Store member bindings for MemberInitExpression to allow binding after DTO projection
Resolves #7234

Updated.


HTTP/2 support

@buckstephenh commented on Mon Aug 29 2016
Hi, I am looking at some greenfield development and would like to make use of HTTP/2 PUSH_PROMISE.  Any idea if/when http/2 will be supported in Kitura or do I need to make a mess and try to write it?  I am seeing support in WKWebView on the IOS client side lots of server-side but would like to see it somewhere via Swift on the server side as in Kitura. https://github.com/http2/http2-spec/wiki/Implementations

@kweinmeister commented on Mon Aug 29 2016
FYI, we have not evaluated this PR yet, but you may find it of interest: https://github.com/IBM-Swift/CCurl/pull/6

@shmuelk commented on Tue Aug 30 2016
@buckstephenh Am I correct in that you are looking for HTTP/2 support on the server side of things? If so, the PR IBM-Swift/CCurl#6 is not relevant. That one is for the client side of things.

@buckstephenh commented on Tue Aug 30 2016
Yes server-side.  I think http/2 will be huge in terms of responsiveness and increased scalability of servers.  Please let me know how I can help.

On Aug 30, 2016, at 1:09 PM, Shmuel Kallner<EMAIL_ADDRESS>wrote:
@buckstephenh Am I correct in that you are looking for HTTP/2 support on the server side of things? If so, the PR IBM-Swift/CCurl#6 is not relevant. That one is for the client side of things.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@simplepanda commented on Sun Sep 04 2016
I'd point out that in the interim Kitura supports FastCGI so you can use something like Nginx ahead of Kitura to handle HTTP2/SSL/static content etc.

@buckstephenh commented on Sun Sep 04 2016
How do you propose a server push_promise via fastcgi?  I didn’t realize fastcgi was two-way.  Is it?  What normally is the slave of inbound requests can initiate outbound calls via fastcgi to the web server?

On Sep 4, 2016, at 1:30 PM, Dylan Neild<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
I'd point out that in the interim Kitura supports FastCGI so you can use something like Nginx ahead of Kitura to handle HTTP2/SSL/static content etc.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/IBM-Swift/Kitura-net/issues/86#issuecomment-244616292, or mute the thread https://github.com/notifications/unsubscribe-auth/ATg8EYdVlTmIfhVCPmZZupH9H8UA5mkNks5qmwBEgaJpZM4Jv75c.

Now Kitura has moved to Swift NIO, HTTP2 support is trivial. This issue is becoming stagnant, so is someone willing to pick this up?

Would be great to have HTTP2 support to send out Apple Push Notifications!
See https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/sending_notification_requests_to_apns


Problem during installation of Sonoma

Hello and thank you for your hard work,
I am unable to install Sonoma with the given EFI file.
I have changed the iMac model to imac19,1 via opencore and generated again the EFI via the generate EFI to desktop option(also changed the smbios via the opencore it self and inserted all necessary kext files)
My 3050 has an i5 7th gen processor
But my installation stacks on the code just before the installation wizard ,my hard disk controller is unsupported as I see but I assume it would get me atleast to the installation wizard.
Can you please assist?

I followed the guide from https://dortania.github.io/OpenCore-Install-Guide/ to create my USB installation for Ventura.
I also have 7th gen CPU.
But i just was not able to get the onboard audio to work until I found EFI by mavethee.   I compared his EFI to mine and there was section for patching something.   I copied that in and boom! audio was working.
After that... all I did was run the system os update directly from MacOS itself and I was able to update to Sonoma and all seems to work fine.
Not the exact help but I thought it may help.
By the way mavethee have a video on youtube on how he built the usb installer.   music is very annoying but still useful.

The problem that I am facing is related to installation with Sonoma
I have used the given EFI but after selecting installing Sonoma it halts at this line
Applelockdownmode -LDMShouldenforceparity) restore os check passed

I followed the guide from https://dortania.github.io/OpenCore-Install-Guide/ to create my USB installation for Ventura. I also have 7th gen CPU. But i just was not able to get the onboard audio to work until I found EFI by mavethee.

Great to hear that, my guess is you missed to setup layout-id, provided in EFI is just first from the list iirc:
https://github.com/acidanthera/AppleALC/wiki/Supported-codecs
alcid=xx in NVRAM -> [UUID] -> boot-args.

I compared his EFI to mine and there was section for patching something. I copied that in and boom! audio was working. After that... all I did was run the system os update directly from MacOS itself and I was able to update to Sonoma and all seems to work fine. Not the exact help but I thought it may help.

only "patching" present is for HDMI, this part specifically but I probably misunderstood
https://dortania.github.io/OpenCore-Post-Install/gpu-patching/intel-patching/connector.html

By the way mavethee have a video on youtube on how he built the usb installer. music is very annoying but still useful.

I don't provide any youtube guides, only one proper guide is text guide here:
https://dortania.github.io/OpenCore-Install-Guide/installer-guide/

I was finally able to install Sonoma with an EFI that was shared to be from a user in a hackinosh forum,if you are interested I can share the file.thank you very much for the valuable guidance

Good to hear that you have it installed.   Did all the onboard components work or did you had to do some post-install stuff?
Yes, please do share.  I would like to have a look at it and compare.

Hello,
From a quick look everything works out of the box
I am going to have a look these days and see if I encourage some issues.
How can I send you the EFI folder?

I was finally able to install Sonoma with an EFI that was shared to be from a user in a hackinosh forum,if you are interested I can share the file.thank you very much for the valuable guidance

Can you share this EFI with me please? I want to install Sonoma on an Optiplex 3070 mff. All the EFI's I found so far get stuck.


android.view.WindowManager$BadTokenException: Unable to add window android.view.ViewRootImpl$W@a2cf037 -- permission denied for this window type

getting this only on api 23
already added

Hi,
Couldn't replicate problem, no exception or even a log value wasn't reported with "BadTokenException". Works fine for me. Please if issue persist - create sample project to replicate it and let me know - for now I close this issue.


Enable merge queue

https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-a-merge-queue

Disabling merge queue for now as there are still a few issues with required checks, see https://github.com/orgs/community/discussions/46757.

Closing this for now. When it's out of Beta we'll give it another try.


Add a "landing pad" for the floatingAction

the floating action button will cover up content near the bottom of the page, which means that we'll need a way to create some space at the bottom of the page for the floating action to "land" in.

the height should be set to button height + some $space


Ros2 drivetrain description

This package will house the new urdf model for the rover using ros2.

closing in favor of #170


[No QA] [TS migration] Migrate 'index.js' test to TypeScript

Details

[TS migration] Migrate 'index.js' test to TypeScript
Fixed Issues

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

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

Offline tests

N/A
QA Steps

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

@hannojg Please, take a look at this PR since it relates to e2e tests 🙏

@paultsimura It would be good to get @hannojg review before merging

@paultsimura Okay, based on Hanno comment there, I think we should be good to go 👌

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/tgolen in version: 1.4.45-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

This is the error happening on AWS:
[DeviceFarm] npx ts-node e2e/testRunner.js -- --mainAppPath app-e2eRelease.apk --deltaAppPath app-e2edeltaRelease.apk
/tmp/scratchc9Cxj5.scratch/test-package6qnjUG/zip/node_modules/ts-node/src/index.ts:859
    return new TSError(diagnosticText, diagnosticCodes, diagnostics);
           ^
TSError: ⨯ Unable to compile TypeScript:
e2e/server/index.ts(3,46): error TS2307: Cannot find module '@libs/E2E/client' or its corresponding type declarations.
e2e/server/index.ts(4,48): error TS2307: Cannot find module '@libs/E2E/types' or its corresponding type declarations.

    at createTSError (/tmp/scratchc9Cxj5.scratch/test-package6qnjUG/zip/node_modules/ts-node/src/index.ts:859:12)
    at reportTSError (/tmp/scratchc9Cxj5.scratch/test-package6qnjUG/zip/node_modules/ts-node/src/index.ts:863:19)
    at getOutput (/tmp/scratchc9Cxj5.scratch/test-package6qnjUG/zip/node_modules/ts-node/src/index.ts:1077:36)
    at Object.compile (/tmp/scratchc9Cxj5.scratch/test-package6qnjUG/zip/node_modules/ts-node/src/index.ts:1433:41)
    at Module.m._compile (/tmp/scratchc9Cxj5.scratch/test-package6qnjUG/zip/node_modules/ts-node/src/index.ts:1617:30)
    at Module._extensions..js (node:internal/modules/cjs/loader:1252:10)
    at Object.require.extensions.<computed> [as .ts] (/tmp/scratchc9Cxj5.scratch/test-package6qnjUG/zip/node_modules/ts-node/src/index.ts:1621:12)
    at Module.load (node:internal/modules/cjs/loader:1076:32)
    at Function.Module._load (node:internal/modules/cjs/loader:911:12)
    at Module.require (node:internal/modules/cjs/loader:1100:19) {
  diagnosticCodes: [ 2307, 2307 ]
}

You have to keep in mind that the e2e tests on AWS are using a different tsconfig than in the app configuration (maybe that can be improved!)
The tsconfig for the e2e tests can be found here:
https://github.com/Expensify/App/blob/48b24ec69b585d4fc660e9569a59d72aeb21c637/.github/workflows/e2ePerformanceTests.yml#L181-L194

@hannojg Okay, so it looks like absolute paths are not working cause they are not in the tsconfig 😞

@hannojg I can prepare a quick follow up PR to fix it. Also I think I'll need to check my other PRs (and not only mine maybe) as well.

As discussed on slack I am putting up a PR soon that will compile the TS code for the e2e tests to JS before we send it to AWS. This way we can use the tsconfig of the main app.
This should fix the broken e2e tests!

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.45-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Cloud Workflow

Hi Team!
A client of mine considers Cloud Workflow for one of its products. As a solution architect, I've been tasked with this assessment exercise. Following the beautifully done "Pic-a-daily" workshop https://codelabs.developers.google.com/codelabs/cloud-picadaily-lab5, there are still a few topics that require clarification.

Can business users make changes to Cloud Workflows?

The impression I've got from the Pic-a-daily workshop is that putting together the workflow definition requires the technical expertise (passing state between steps, setting up error handling, retries, authN, authZ etc.) Does Cloud Workflow out-of-the-box functionality allow extracting the orchestration logic out, so that it can be manipulated by business users with little or no technical background? Think If-This-Then-That no-code approach.
2. How do OAuth2 and OIDC settings are applied in runtime?
The workflow definition example.
3. URLs as Workflow args
Workflow definition used in the workshop defines URLs of orchestrated endpoints as args. For external APIs (Google Vision in our case) this is fine, but for internal services this may be an issue. For instance COLLAGE_URL points to the following Cloud Function URL: https://collage-service-xgstcqnrla-ew.a.run.app/. Was wondering if this is the only way the workflow runtime can do the orchestration job? Or, it's also possible to hide the specific service behind an API gateway?
That's all I wanted to clarify for now :) Thanks in advance!

Hi @singulart,

You're right. Currently, you need to be technical to be able to figure out the YAML syntax and construct it yourself. We're thinking of ways to make this more visual and less technical in the future.

When you specify OAuth2/OIDC, Workflows authenticates as its associated service account. Please take a look at this doc page for more details.

We passed in URLs as runtime arguments because each URL of a service will be unique for each project. We didn't want to hardcode URLs (that will be specific to our project) or ask people to replace some placeholder URLs with real URLs from their project. It's up to you how you want to handle this. You can certainly use an API gateway URL instead, as long as that URL is accessible from Google Cloud / Workflows.

Hope this is useful.

Please re-open if you have further questions.


Add Java module system

As the adoption of Java 11 increases, we should eventually add java modules to Speedment.

Here are some projects that uses JPMS as of now:
com.spotify.futures
com.sun.xml.ws.servlet
io.helidon.tracing

net.bytebuddy
net.bytebuddy.agent

org.apache.derby.commons

org.apache.logging.log4j

org.joda.beans

org.jooq.jool

org.junit.jupiter
org.junit.jupiter.api

org.slf4j
org.slf4j.nop

When using JPMS, speedment can use multi-version JAR and be built under Java 11 but with source-level 1.8. It shall be possible to run under any Java 8 and upwards.


[SPARK-25726][SQL][TEST] Fix flaky test in SaveIntoDataSourceCommandSuite

What changes were proposed in this pull request?
SPARK-22479 adds a test case which sometimes fails because the used password string 123 matches @41230802. This PR aims to fix the flakiness.

https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/97343/consoleFull

SaveIntoDataSourceCommandSuite:
- simpleString is redacted *** FAILED ***
"SaveIntoDataSourceCommand .org.apache.spark.sql.execution.datasources.jdbc.JdbcRelationProvider@41230802, Map(password -> *********(redacted), url -> *********(redacted), driver -> mydriver), ErrorIfExists
+- Range (0, 1, step=1, splits=Some(2))
" contained "123" (SaveIntoDataSourceCommandSuite.scala:42)

How was this patch tested?
Pass the Jenkins with the updated test case

Test build #97349 has started for PR 22716 at commit 2231106.

cc @onursatici and @gatorsmile

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3950/
Test PASSed.

Thank you for review, @gatorsmile !

Thank you for review, @felixcheung . It comes from treeString. If you are asking the origin, it comes from Java toString and the value is the object hashCode. So, this happens when the hashCode value has 123.

Test build #97349 has finished for PR 22716 at commit 2231106.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/97349/
Test PASSed.

Merged to master/branch-2.4.


Xenko 3.1 Could not find a compatible version of MSBuild.

Release Type: Xenko 3.1
Version: Xenko 3.1
Platform(s): Windows 10
Describe the bug
Installer goes through perfectly - no complaints, but when trying to launch Stride, I get an error dialog with the text: Could not find a compatible version of MSBuild.
To Reproduce
Steps to reproduce the behavior:

Install Stride from here https://stride3d.net/download/
Run installer and let it complete
Try to Install Xenko 3.1, Visual Studio Plugin : Stride and Xenko
Expected behavior
I expected the Game Studio to launch.

Screenshots

Log and callstacks
If any, please attach here any log or callstack (preferably in a .txt file using GitHub drag and drop)
Logs.txt
Additional context
I have latest VS Professional 2019 installed v16.7.3, with .NET desktop development, .NET core cross-platform development workloads. also Installed <IP_ADDRESS>-beta04-1265 and it works perfectly. but my team are using <IP_ADDRESS> we don't rely on beta.

It should be fixed in <IP_ADDRESS>


Feature Request - Invert Columns and Rows in HTML Table

HI !
I just found your nice bracket extension ! There is some really interesting things with HTML :)
Maybe can you take a look to an action for Inverting Columns and Rows in HTML Table ?
I don't know how to write an extension for bracket,
but I find how it could be done in jquery here => http://jsfiddle.net/CsgK9/2/
Maybe can you take a look at this ?
It is an nice feature that I have never found in any code editor, and I think it fit very well in your extension :)
Thanks for listening, don't hesitate to tell me if you are not interested by this.

We can assess a different extension. In this regard I will make planning a blank time.
Thank you.


Protoc execute  error

grpc 测试的时候提示找不到文件，可能啥原因

This issue is stale because it has been open for 30 days with no activity.

This issue was closed because it has been inactive for 14 days since being marked as stale.


ENH: Warn when disabling adapters and bias != 'none'

As discussed internally.
For LoRA, given that bias='all' or bias='none', when doing inference with a model in the disable_adapter() context, the output will not be identical to the output of the base model. This may be surprising to users. Therefore, a warning is given. Furthermore, the docstring has been extended to reflect this fact.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


How the inverse was calculated

Hi,
I do not understand how to compute the inverse normalizing flow. Could you explain how do you compute the inverse function? Thank you.
Link:
https://github.com/VincentStimper/normalizing-flows/blob/ce86fe79d7cdc34f0362f487194d0cebb1999edc/normflows/flows/planar.py#LL66C3-L66C3
  def inverse(self, z):
        if self.act != "leaky_relu":
            raise NotImplementedError("This flow has no algebraic inverse.")
        lin = torch.sum(self.w * z, list(range(1, self.w.dim()))) + self.b
        a = (lin < 0) * (
            self.h.negative_slope - 1.0
        ) + 1.0  # absorb leakyReLU slope into u
        inner = torch.sum(self.w * self.u)
        u = self.u + (torch.log(1 + torch.exp(inner)) - 1 - inner) \
            * self.w / torch.sum(self.w ** 2)
        dims = [-1] + (u.dim() - 1) * [1]
        u = a.reshape(*dims) * u
        inner_ = torch.sum(self.w * u, list(range(1, self.w.dim())))
        z_ = z - u * (lin / (1 + inner_)).reshape(*dims)
        log_det = -torch.log(torch.abs(1 + inner_))
        return z_, log_det

Hi @jiaqingxie,
When the activation function is a leaky ReLU, the planar flow is simple a piecewise linear function and can hence be inverted like a linear map on the two sections.
Best regards,
Vincent


Time delay between heats

Add a heat_delay argument for the flank and strip pattern generators to specify a delay in seconds between igniter heats.

For the flank ignition, it would be good have it as an option to add it to the delay from walking around the unit or a flat delay. This could also be done by the user if there is a way to return the start time for each ignitor / heat, but I haven't dug around to find that.

Thanks for the idea @drosales95, this certainly lends a bit more authenticity to the time aspect of these simulations.

@frigusgulo This issue didn't get merged. See PR #100.


Add ingressClassName for LTS

Add ingressClassName for LTS

Hi @shizacat
Sadly this change cannot qualify for the LTS version as it is not a blocker.
Please use the latest version if you need this configuration

@leo-geoffroy-sonarsource ingressClassName is required for K8s 1.22 and higher. 1.22 is the oldest supported release (and is about to go out of support in a few months). I don't think the "blocker only" policy works with the concept of LTS if it prevents you from actually running a supported configuration.


Support laravel 6

Please add support laravel 6.

I have a branch and tagged version here: https://packagist.org/packages/jobzmall/lucid-laravel-console#v6.0.2
Let me know if you run into any issues. I am not putting in a PR, because this was a quick hack that removed incompatible dependencies (and some code because of that). @vanthao03596

Hello people,
You can already find support for Laravel 6 by either using the master branch or the 6.0 branch.


ClangImporter: improve ObjC-interop and enable tests

This enables additional tests for the ClangImporter.  This found a
missing piece in the -enable-objc-interop work that was done
previously.  Address that and enable the tests.  There are now two
failing tests on Linux:

sdk - depends on Foundation (not hermetic, see SR-7572)
import-mixed-with-header-twice - requires apple/swift PR#16022

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 5915fdfa1675c1389ab0749224634d65ea215666

Build failed
Swift Test OS X Platform
Git Sha - 5915fdfa1675c1389ab0749224634d65ea215666

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 7606e2b5c5db8dcef1af28d905e68014bc39a613

@swift-ci please test macOS platform
seems like an unrelated failure?

@swift-ci please test macOS platform


Init position of the widget

How to set position of the widget on create on the center of the screen?

Hi, https://pub.dev/packages/draggable_widget/versions/1.1.0
update to the latest version, it includes center position


README - Workshops 2: Installing pre-requisites lab link broken

Workshop 2 in the list of links, the link to pre-reqs:
https://github.com/IBM/openshift-on-ibm-cloud-workshops/blob/master/documentation/1-prereqs.md
returns a 404.

May thanks @timroster for all your feedback and that is even more than in that single issue. I forgot to merge your request. Sorry for that. But now it is fixed. Greetings Thomas


CSS Flash with stylus but not with CSS (FOUC)

Version
v2.8.1
Reproduction link
https://github.com/ShailenNaidoo/nuxt-fouc-reproduction
Steps to reproduce

Clone repo
Yarn install
npx nuxt build
npx nuxt start you should see FOUC in browser
Go to nuxt.config.js and comment out the app.styl file and then uncomment the vuetify.css file
npx nuxt build
npx nuxt start You should see no FOUC

What is expected ?
There should be no FOUC when using .styl files or any pre-processor but when using .css files it works perfectly like the following:

What is actually happening?
When using .styl there is a FOUC, there should not be this using any preprocessor

This bug report is available on Nuxt community (#c9462)

Step 5 of your instructions is not available as there are no css files listed in the nuxt.config

Step 5 of your instructions is not available as there are no CSS files listed in the nuxt.config

@pimlie Sorry about that, I accidentally pushed up the wrong config. Check it out now

Seems exactly like the issue i have with scss, https://cmty.app/nuxt/nuxt.js/issues/c10400


Permissioned-network: update to latest monthly

Linked: https://github.com/substrate-developer-hub/substrate-node-template/pull/265


Talkback announces wrong state on radio button selection

Reproduction
Use StackBlitz to reproduce your issue: https://stackblitz.com/fork/components-issue
Steps to reproduce:

Load https://material.angular.io/components/radio/examples on android chrome browser
Start Talkback
Select 'Autumn' option from the first example (talkback reads 'Selected')
Navigate to 'Summer' (talkback reads 'Summer radio button not selected')
Select 'Summer' (talkback reads 'Not selected')
Select 'Autumn' again (talkback reads 'Selected')

Expected Behavior
What behavior were you expecting to see?
When selecting a previous radio button, talkback should announce the correct state, 'Selected'
Actual Behavior
What behavior did you actually see?
When selected a previous radio button, talkback announces it's previous state
Environment

Angular: latest
CDK/Material: latest
Browser(s): Mobile Chrome, Android WebView
Operating System (e.g. Windows, macOS, Ubuntu): Android

Can close this for now, Issue appears to be from Android's talkback.
link to issuetracker

I just tested this on and it seems to work as expected on:
Pixel 3
Android 10
Chrome 83
Angular Material 10.0.1