Receiving 401 from managed function app in centralus region only

Recieving a 401 when function has AuthorizationLevel.Function applied
We have a static web app application that utilizes a managed function app. Starting this morning (not entirely sure when but it appears to have been around 7AM Eastern) all of our centralus region static web app instances began returning 401 responses for any requests made to our /api endpoints. This doesn't appear to be occurring in our eastus2 locations and no code was deployed or changed preceding the errors. To mitigate the issue we starting routing all traffic through our eastus2 static web app resource via front door which seems to be working but our centralus resources are still experiencing the same issue going on 7 hours now.
I tested things out in one of our test environments in the centralus region and it appears that updating the authorization level for the http trigger functions in our managed function app to be Anonymous instead of Function appears to clear up the 401 responses.
These functions have been set to AuthorizationLevel.Function for over a year and haven't changed so we're not sure why this behavior appears to have changed this morning in one region only. I was hoping to confirm that AuthorizationLevel.Function is correct and supported by managed functions within an SWA and this might just be due to an Azure outage versus something we're doing incorrectly. I assume that's the case as AuthorizationLevel.Function is working in our eastus2 instances and like I said we haven't modified that setting is some time.

same thing happened to deployed APP which previously worked.
Also, the new 1.1.2 SWA cli is super buggy too which makes a frustrated diagnosis expensive.

Experiencing this issue as well.  Redeployed the swa from centralus to westus2 and had the same issue.  Only updating the authorization level for the trigger from Function to Anonymous seemed to help.

Similar thing happened to us.
Starting at Thursday 05/18 midnight EST, multiple static web apps with managed apis (c#, func v4, .net 6.0)  began reporting 401 unauthorized.   Start/stop did not fix.  Redeploy did not fix.  Hot to hotfix all apis by changing auth level from AuthorizationLevel.Function to AuthorizationLevel.Anonymous.
This incident seems to have impacted multiple customers.  Do we know if this was an isolated incident? Any root cause?  Can we set functions back to AuthorizationLevel.Function ?

@ramseytm - I don't think this was region related?  We saw the same thing as @jwoytas, the issue remained regardless of region.

any RCA for this?  shall we keep AuthorizationLevel to Anonymous?

Similar issue here. Receiving 401 from managed function app since last week.

Same issue, in west us 2.  I have tried implementing the bring your own functions as a means to fix it and no luck there either.

Whatever the change of behavior is, it appears to have been deployed to the EastUS2 region this morning. We're opening a ticket directly with Microsoft to see if we can get any answer on what change is occurring and get documentation on the supported cases for function key's in a static web app resource.

This has just affected us today in production, very frustrating.

Hi everyone. We're following up with Functions team to see if something regressed there. Meanwhile you can set the AuthorizationLevel to Anonymous to get unblocked. It's safe to set the AuthorizationLevel as Anonymous, as we have another layer of authorization checks in place so that only SWA can access the managed function endpoints.

Can I also get some details like the static web app name/url of the impacted sites. And if redeploying the app is resolving the issue, to understand the issue better. Thanks!

Hi everyone. Apologies for the inconvenience! We're following up with Functions team to see if something regressed there.
Meanwhile you can set the AuthorizationLevel to Anonymous for your functions to get unblocked. It's safe to set the AuthorizationLevel as Anonymous, as we have another layer of authorization checks in place so that only SWA can access the managed function endpoints.

What about bring your own function endpoints, are they safe to be anonymous?
I've already fixed my sites by switching them to anonymous so not sure they will be much help.

Can confirm that

Redeploying by itself does not help
Redeploying with AuthorizationLevel.Anonymous fixes the problem
This currently affects western europe

This is also affecting our Azure Static Web App with a managed function. As far as I know it's not possible to change the Auth level on a managed function app so the workaround doesn't work for our use case.

Workaround (AuthLevel='anonymous') works fine for me as well

@danbasszeti Yes, it's safe for BYOF as well.
@paulgravesnewday You can set "authLevel": "anonymous" in your function.json. For reference

My site is also down because of this. Western Europe.
Do you have an ETA for the fix?

Redeploy and start/stop did not fix.  Only changing auth level was a fix.

My Azure SWA APIs in West Europe started to get 401s 2023-06-01 11:30 CEST and are still failing, 22 hours later. I haven't tried switching to anonymous yet (reluctant to do this).

@vivekjilla Sorry, what other layers of authorization are in place to secure the managed functions endpoints? Setting the authorization level to anonymous will allow anyone to access the managed functions endpoints without providing any form of credentials, right?

@niklashaetty what you said is true for standalone function apps. But for function apps managed by/linked to SWA,  we restrict the traffic to go only via SWA and disable direct access by default.
@ramseytm Thanks for sharing the update here!

I got this issue as well in my SWA's. All my API endpoints are publicly accessible though. I was surprised to realize that indeed I had some Azure Functions with authlevel: function. They have been like this for two years now.
I don't really understand how or why authlevel: function has ever worked. This has to be something specific to SWA instead of e.g. the good old Azure App Service.
If I understood correctly, there is a fix on its way that will again enable authlevel: function API endpoints.
My question is: shouldn't those be set as authlevel: anonymous in the first place? Shouldn't authlevel: function always require the key in the URL to be able to access the endpoint?

@mikkark - I have had the same experience.  We have a swas with managed functions and all of their api endpoints are publicly accessibly.
I'd really like an answer from MS on this.  Are manged api endpoint supposed to be publicly accessible?  I actually need them to be, but I have folks saying they shouldn't be?

@mikkark, @TroyWitthoeft sorry for the confusion. There are two parts here for managed functions.

API request going to SWA endpoint: Yes, these will be publicly accessible unless you define SWA auth roles to restrict access.
Managed function is also an azure function managed by SWA: If someone gets access to that managed function name and tries to access it directly, we restrict that access.

So end user has to call your SWA endpoint to access the APIs. And SWA passes the necessary auth info when forwarding the request to managed function. This is all abstracted out to SWA users.
The regression here is, the auth flow between SWA and managed function had an issue and so we observed 401s.
Update: This issue has been now resolved. So, using authLevel: function should also work. But it's not strictly needed, as we have second layer of checks in place to handle the 2nd point above.
Hope this helps! Apologies for the confusion and inconvenience.

I'm still experiencing this issue with my managed functions even after redeployment, this issue started to occur last Wednesday.

Apologies for this. @DessNotFound Issue resolution in progress for Node/Python functions. Resolved for Dotnet functions.
Will update once it's fixed completely. Meanwhile you can use the workaround mentioned above. Thanks!

Thank you for such a fast response! Do you have an estimate on when the issue will be resolved?

We're working on rolling out the fix gradually, now. Current estimated ETA is 12 hours.

The fix has been rolled out to Node and Python apps as well and the issue should be mitigated now. In case someone is still seeing this issue, redeployment should resolve the issue. Apologies for the inconvenience.

Has this actually been resolved for dotnet? Currently have a .net 8 isolated function deployed that works with SWA SPA only when the AuthorizationLevel is set to Anonymous.

Has this actually been resolved for dotnet? Currently have a .net 8 isolated function deployed that works with SWA SPA only when the AuthorizationLevel is set to Anonymous.

This is normal behavior according to the Static Web Apps docs. If the authorization of the functions require a function key, you need to provide it or put the function to anonymous: https://learn.microsoft.com/en-us/azure/static-web-apps/functions-bring-your-own#security-constraints


[🐛] Android launchCamera not work production

Description
I'm using newest version 5.3.1
this problem happen on production mode
When I tap launchCamera on Android nothing happen
lunchCamera worked on emulator but doesn't work on real device
I tested on Samsung J7Prime
export const openCamera: () => Promise<Asset[] | null> = async () => {
  try {
    const image = await launchCamera({
      mediaType: 'photo',
      quality: 1,
      saveToPhotos: true,
    });
    if (image?.assets?.length) {
      return Promise.resolve(image.assets);
    } else {
      return Promise.reject();
    }
  } catch (e) {
    console.error('openCamera error', e);
    return Promise.reject();
  }
};

Additional Information

Image Picker version: 5.3.1
React Native version: 0.71.7
Platform: Android

Did you notice camera permission?
read this
This library does not require Manifest.permission.CAMERA, if your app declares as using this permission in manifest then you have to obtain the permission before using launchCamera.

Did you notice camera permission? read this
This library does not require Manifest.permission.CAMERA, if your app declares as using this permission in manifest then you have to obtain the permission before using launchCamera.

I didn't add Manifest.permission.CAMERA on android

@mskarimi I see saveToPhotos: true in the options, did you take the WRITE_EXTERNAL_STORAGE permission?

@mskarimi I see saveToPhotos: true in the options, did you take the WRITE_EXTERNAL_STORAGE permission?

yes I did

You have to add Manifest.permission.CAMERA on manifest file and also request permission before launchCamera or else it wont work on production

You have to add Manifest.permission.CAMERA on manifest file and also request permission before launchCamera or else it wont work on production

I did but nothing changed
I was thrown to catch, but I didn't get any message

hi @Johan-dutoit
do you have suggestion?

PermissionsAndroid.request(PermissionsAndroid.PERMISSIONS.CAMERA)
//     .then(async res => {
//       console.log('res:', res);
//       if (res === 'granted') {
//         let result = isCamera ? await launchCamera(options) : await launchImageLibrary(options);
//         // lanching camera or image library
//         console.debug('image picker result', result);
//         // …
//         uploadImageFile(result);
//       } else if (res === 'blocked') {
//         Toast.show('You need to enable camera permission from setting', Toast.LONG);
//       }
//     })
//     .catch(error => {
//       Toast.show('Unable to upload picture try again later', Toast.LONG);
//       console.log('image error android', error);
//     });

I test in HUAWEI nova Y70 and need request CAMERA permission.

No permissions should be required to open the camera in production.  See the example app for setup.


fix typo that was acccidentally typed in

Change acccidentally to accidentally
fix typo in docs/csharp/csharp-7.md

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot


haskellPackages.swarm: fix broken package

Description of changes
Unbroke haskellPackages.swarm

Things done

Jailbroke haskellPackage.swarm
Added brick 1.0 because the jailbreaking did not help with it
Jailbroke brick 1.0 because it would not build

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Why did you close?

Sorry about that. I assumed it was not really that important and since it had been a week and was clogging up the more important PRs upstream, I went ahead a closed it. Should I reopen?

Sure.


add .is-rounded class

This doesn't look right on safari.

What's this border inside the button?

It's the work of user agent stylesheet of Safari 👿
I solve it with border: none;, but I'm not sure the side effects.
Please give me time to investigate. 🙏

It's in the user agent stylesheet of Chrome as well. I dont think there should be a problem with removing the border from buttons. That's a pretty standard first step to restyling them.

It's border: none. Last time PR was there, border: none was written under. bnt and fixed a little bit of the white edge problem.     .v__v

I answered -> https://github.com/nostalgic-css/NES.css/issues/86#issuecomment-445501451
@jjspace Thanks, You are right 👍

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Workspace editor - 'Save' button is not grayed out while offline after changing the name

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open NewDot Desktop App
Turn the network off
Try to rename the WS and click on the save button

Expected Result:
The Save button and the text input is now grayed out
Actual Result:
'Save' button is not grayed out
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/196805417-9c135dee-57be-4ffc-b594-4254f9412c5c.mp4

Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Nice catch. closing then


How would i do a redirect?

Read Title

Hi @UniC7440, same as you would do it with vanilla HTTP in Node.js
...
res.statusCode = 302
res.setHeader('Location', 'https://github.com/jkyberneees/ana/issues/55')
res.end()

Regards


 It is not standardized between drivers, and doesn't guarantee any supported line widths. It's just a big gamble, and you, as the developer, have no idea of how the game will look on other machines with different GPUs and graphics drivers.
Possible solution: a custom line renderer using quads. It will be slower than drawing lines directly, but will be consistent across GPUs/drivers.

This might get moved on when I port rapid to my new GL library, aglet. It supports geometry shaders which enable this kind of thing to be done completely on the GPU.


Make StandardDetector call writer.open in prepare

The writers are currently opened in stage. This needs to be move to prepare to we can use multipliers. We also need to move multiplers into prepare.

Closed in favour of #314 .


Strange behavior with rtop.

When I use Reason's rtop, I get this weird behavior. Has anyone seen anything like this?

Could you provide steps/link to install it? 😄

I have well tested instructions for Mac OSX if you have npm3.
ExampleProject describes how to install.
git clone https://github.com/reasonml/ExampleProject.git
cd ExampleProject
npm install

Then run
npm run top

Ok I can reproduce 😅

Was this fixed? I'm having trouble reproducing the issue.

Actually, it seems it happens only at certain window resize widths.


Proof of concept for account profiles.

Some notes on this PR:

Tests have not yet been completed.
I have assumed that profiles will be a permanent part of all account requests. I.e. this information is always included in get requests.
Have only focussed on initial sign-up and session/account retrieval. So currently no profile requests have been dealt to.

To do:

[x] Code tests
[ ] Docs for hoodie-account-client
[ ] PR hoodie-account

More than happy for someone to add to this PR ;)

I have assumed that profiles will be a permanent part of all account requests. I.e. this information is always included in get requests.

No I wouldn’t do that. I’d agree with account.signUp, but for account.signIn I’d suggest to add an include argument which can be set to profile to include it in the response.
I think the account.profile methods should be fine. Only thing missing in your TODOs is updating docs

can you add a test to  hoodie-account-server/tests/integration/routes/account/put-account-test.js with payload.data.attributes.profile set to something like fullname: 'Pat Doe'? Ideally to post-accounts-test.js, too. It would be great to test that at the end the _users doc will have profile.fullname set to Pat Doe

I’d maybe add another integration test: sign-up-with-profile-test.js to make sure the behavior works and won’t break in future. Otherwise looking good 👍

@gr2m have added (server) a test here: https://github.com/hoodiehq/hoodie-account-server/pull/158/commits/f69ffa927cdea65d36b7ed2e721245dcc7d9974f
Keen on feedback before I do the PATCH test just in case :)


Add missing @ on annotation example

Pull Request Test Coverage Report for Build 97

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.079%

Totals

Change from base Build 95:
0.0%

Covered Lines:
538

Relevant Lines:
543

💛  - Coveralls


[Fix] warning: circular argument reference no_response_wrapper Use ruby2.2.0

:+1:

:+1:

+1

:+1:

+1

+1

:+1:

:+1:

:+1:

:+1:

:thumbsup:

:thumbsup:

:+1:

PR wIth some other fixes for ruby 2.2.0: https://github.com/Instagram/instagram-ruby-gem/pull/150

(y)

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:

:+1:


ASimAuditEventBarracudaWAF.yaml-2

Required items, please complete
Change(s):

Created a new file for BaracudeCEF and added BaracudaCEF parser in it. In BaracudaWAF file removed BaracudaCEF parser and in ASimAuditEvent added BaracudeCEF Parser name  and same changes have done for vim as well.

Reason for Change(s):

To Split the BaracudaWAF and BaracudaCEF parser separately

Version Updated:

yes

Testing Completed:

yes

Checked that the validations are passing and have addressed any issues that are present:

yes

Hi @Alekhya0824,
Please act on reviewer's open comments. Thanks

Hi @Alekhya0824,
I can see a few open comments from the reviewer. Please act on them.

And also, one suggestion: once you're done with the open comment change, please click on the Resolve Conversation button.

Hi @Alekhya0824,
Did you respond to the open comment below? Thanks

@microsoft-github-policy-service agree company="Microsoft"

@microsoft-github-policy-service agree company="Microsoft"


I tried running my flutter code on my android emulator but got this error.

I tried to run my flutter code on my android emulator but got this error.
Command
flutter run
And got this error
ProcessException: ProcessException: %1 is not a valid Win32 application.
Command: C:\Users\Michael Odafe\AppData\Local\Android\sdk\platform-tools\adb.exe devices -l
#0      _ProcessImpl._runAndWait (dart:io-patch/process_patch.dart:489:7)
#1      _runNonInteractiveProcessSync (dart:io-patch/process_patch.dart:634:18)
#2      Process.runSync (dart:io-patch/process_patch.dart:66:12)
#3      LocalProcessManager.runSync (package:process/src/interface/local_process_manager.dart:83:20)
#4      _runWithLoggingSync (package:flutter_tools/src/base/process.dart:343:48)
#5      runSync (package:flutter_tools/src/base/process.dart:315:10)
#6      getAdbDevices (package:flutter_tools/src/android/android_device.dart:614:12)
#7      AndroidDevices.pollingGetDevices (package:flutter_tools/src/android/android_device.dart:63:53)
<asynchronous suspension>
#8      PollingDeviceDiscovery.devices (package:flutter_tools/src/device.dart:223:52)
<asynchronous suspension>
#9      DeviceManager.getAllConnectedDevices (package:flutter_tools/src/device.dart:151:46)
<asynchronous suspension>
#10     DeviceManager.getDevices (package:flutter_tools/src/device.dart:141:11)
#11     FlutterCommand.findAllTargetDevices (package:flutter_tools/src/runner/flutter_command.dart:506:48)
<asynchronous suspension>
#12     RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:282:21)
<asynchronous suspension>
#13     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:462:11)
<asynchronous suspension>
#14     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:383:33)
<asynchronous suspension>
#15     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#16     _rootRun (dart:async/zone.dart:1124:13)
#17     _CustomZone.run (dart:async/zone.dart:1021:19)
#18     _runZoned (dart:async/zone.dart:1516:10)
#19     runZoned (dart:async/zone.dart:1463:12)
#20     AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#21     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:375:20)
#22     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
<asynchronous suspension>
#23     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:396:21)
<asynchronous suspension>
#24     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#25     _rootRun (dart:async/zone.dart:1124:13)
#26     _CustomZone.run (dart:async/zone.dart:1021:19)
#27     _runZoned (dart:async/zone.dart:1516:10)
#28     runZoned (dart:async/zone.dart:1463:12)
#29     AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#30     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:356:19)
<asynchronous suspension>
#31     CommandRunner.run.<anonymous closure> (package:args/command_runner.dart:112:25)
#32     new Future.sync (dart:async/future.dart:224:31)
#33     CommandRunner.run (package:args/command_runner.dart:112:14)
#34     FlutterCommandRunner.run (package:flutter_tools/src/runner/flutter_command_runner.dart:242:18)
#35     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:22)
<asynchronous suspension>
#36     _rootRun (dart:async/zone.dart:1124:13)
#37     _CustomZone.run (dart:async/zone.dart:1021:19)
#38     _runZoned (dart:async/zone.dart:1516:10)
#39     runZoned (dart:async/zone.dart:1500:12)
#40     run.<anonymous closure> (package:flutter_tools/runner.dart:60:18)
<asynchronous suspension>
#41     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:29)
<asynchronous suspension>
#42     _rootRun (dart:async/zone.dart:1124:13)
#43     _CustomZone.run (dart:async/zone.dart:1021:19)
#44     _runZoned (dart:async/zone.dart:1516:10)
#45     runZoned (dart:async/zone.dart:1463:12)
#46     AppContext.run (package:flutter_tools/src/base/context.dart:152:18)
<asynchronous suspension>
#47     runInContext (package:flutter_tools/src/context_runner.dart:56:24)
<asynchronous suspension>
#48     run (package:flutter_tools/runner.dart:51:10)
#49     main (package:flutter_tools/executable.dart:62:9)
<asynchronous suspension>
#50     main (file:///C:/b/s/w/ir/k/archive/flutter/packages/flutter_tools/bin/flutter_tools.dart:8:3)
#51     _startIsolate.<anonymous closure> (dart:isolate-patch/isolate_patch.dart:299:32)
#52     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:172:12)

flutter doctor
encountered exception: ProcessException: %1 is not a valid Win32 application.

Sending crash report to Google.                                                                                |CreateProcessW failed 193
Oops; flutter has exited unexpectedly.
Sending crash report to Google.
Crash report sent (report ID: c3feedc2cea52e7d)
\CreateProcessW failed 193
Unhandled exception:
ProcessException: %1 is not a valid Win32 application.

I think Dart has issues on windows when the path has a space, it seems like your username also has a space in it, therefore ADB can't be invoked.

How can I get rid of the space please?

Try moving your androidsdk install to a folder closer to the root of your disk (C:\android for example).
Renaming yourself and your user folder is either dangerous, or requires moving your entire user folder to a new user who doesn't have this issue.

Try moving your androidsdk install to a folder closer to the root of your disk (C:\android for example).
Renaming yourself and your user folder is either dangerous, or requires moving your entire user folder to a new user who doesn't have this issue.

Thank you, But a new problem popped up after doing that... After running the program on android studio it is stocked on "Initializing gradle"
The screenshot is below..

Try moving your androidsdk install to a folder closer to the root of your disk (C:\android for example).
Renaming yourself and your user folder is either dangerous, or requires moving your entire user folder to a new user who doesn't have this issue.

Thank you, But a new problem popped up after doing that... After running the program on android studio it is stocked on "Initializing gradle"
The screenshot is below..

Try moving your androidsdk install to a folder closer to the root of your disk (C:\android for example).
Renaming yourself and your user folder is either dangerous, or requires moving your entire user folder to a new user who doesn't have this issue.

Thank you, But a new problem popped up after doing that... After running the program on android studio it is stocked on "Initializing gradle"
The screenshot is below..

Try moving your androidsdk install to a folder closer to the root of your disk (C:\android for example).
Renaming yourself and your user folder is either dangerous, or requires moving your entire user folder to a new user who doesn't have this issue.

Also the same thing when I tried using Visual Studio code..
PS C:\android\flutter_app> flutter run
Using hardware rendering with device Android SDK built for x86. If you get graphics artifacts, consider enabling software rendering with
"--enable-software-rendering".
Launching lib/main.dart on Android SDK built for x86 in debug mode...
Initializing gradle...
(This is taking an unexpectedly long time.)
The screenshot below

run flutter run -v in a terminal, it should show more details.

This is what I got
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
PS C:\android\flutter_app> flutter run -v
[  +31 ms] executing: [C:\android\flutter] git log -n 1 --pretty=format:%H
[  +77 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[        ] 20e59316b8b8474554b38493b8ca888794b0234a
[        ] executing: [C:\android\flutter] git describe --match v*.. --first-parent --long --tags
[  +61 ms] Exit code 0 from: git describe --match v*.. --first-parent --long --tags
[   +1 ms] v1.7.8+hotfix.4-0-g20e59316b
[  +11 ms] executing: [C:\android\flutter] git rev-parse --abbrev-ref --symbolic @{u}
[  +62 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [C:\android\flutter] git ls-remote --get-url origin
[  +52 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +88 ms] executing: [C:\android\flutter] git rev-parse --abbrev-ref HEAD
[  +59 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[ +352 ms] executing: C:\android\Sdk\platform-tools\adb.exe devices -l
[  +52 ms] Exit code 0 from: C:\android\Sdk\platform-tools\adb.exe devices -l
[        ] List of devices attached
emulator-5554          device product:sdk_gphone_x86 model:Android_SDK_built_for_x86 device:generic_x86 transport_id:2
[  +20 ms] C:\android\Sdk\platform-tools\adb.exe -s emulator-5554 shell getprop
[  +85 ms] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +5 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[ +185 ms] ro.hardware = ranchu
[   +4 ms] Using hardware rendering with device Android SDK built for x86. If you get graphics artifacts, consider enabling software rendering with
"--enable-software-rendering".
[  +19 ms] Launching lib/main.dart on Android SDK built for x86 in debug mode...
[  +24 ms] Initializing gradle...
[   +1 ms] Using gradle from C:\android\flutter_app\android\gradlew.bat.
[ +937 ms] executing: C:\android\flutter_app\android\gradlew.bat -v

run flutter run -v in a terminal, it should show more details.

This is what I got
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.
PS C:\android\flutter_app> flutter run -v
[  +31 ms] executing: [C:\android\flutter] git log -n 1 --pretty=format:%H
[  +77 ms] Exit code 0 from: git log -n 1 --pretty=format:%H
[        ] 20e59316b8b8474554b38493b8ca888794b0234a
[        ] executing: [C:\android\flutter] git describe --match v*.. --first-parent --long --tags
[  +61 ms] Exit code 0 from: git describe --match v*.. --first-parent --long --tags
[   +1 ms] v1.7.8+hotfix.4-0-g20e59316b
[  +11 ms] executing: [C:\android\flutter] git rev-parse --abbrev-ref --symbolic @{u}
[  +62 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [C:\android\flutter] git ls-remote --get-url origin
[  +52 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +88 ms] executing: [C:\android\flutter] git rev-parse --abbrev-ref HEAD
[  +59 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[ +352 ms] executing: C:\android\Sdk\platform-tools\adb.exe devices -l
[  +52 ms] Exit code 0 from: C:\android\Sdk\platform-tools\adb.exe devices -l
[        ] List of devices attached
emulator-5554          device product:sdk_gphone_x86 model:Android_SDK_built_for_x86 device:generic_x86 transport_id:2
[  +20 ms] C:\android\Sdk\platform-tools\adb.exe -s emulator-5554 shell getprop
[  +85 ms] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +5 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[ +185 ms] ro.hardware = ranchu
[   +4 ms] Using hardware rendering with device Android SDK built for x86. If you get graphics artifacts, consider enabling software rendering with
"--enable-software-rendering".
[  +19 ms] Launching lib/main.dart on Android SDK built for x86 in debug mode...
[  +24 ms] Initializing gradle...
[   +1 ms] Using gradle from C:\android\flutter_app\android\gradlew.bat.
[ +937 ms] executing: C:\android\flutter_app\android\gradlew.bat -v
[+120322 ms] Exception in thread "main" java.lang.RuntimeException: Timeout of 120000 reached waiting for exclusive access to file: C:\Users\Michael
Odafe.gradle\wrapper\dists\gradle-4.10.2-all\9fahxiiecdb76a5g3aw9oi8rv\gradle-4.10.2-all.zip
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:61)
at org.gradle.wrapper.Install.createDist(Install.java:48)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:128)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
[  +10 ms] "flutter run" took 122,019ms.
[        ] "flutter run" took 122,019ms.
Oops; flutter has exited unexpectedly.
Sending crash report to Google.
Crash report sent (report ID: 35d281487fa62cf9)
Crash report written to C:\android\flutter_app\flutter_01.log;
please let us know at https://github.com/flutter/flutter/issues.
PS C:\android\flutter_app>

Android studio gradle finally finish processing and this is the error I got
Finished with error: ProcessException: Process "C:\android\flutter_app\android\gradlew.bat" exited abnormally:
Exception in thread "main" java.lang.RuntimeException: Timeout of 120000 reached waiting for exclusive access to file: C:\Users\Michael Odafe.gradle\wrapper\dists\gradle-4.10.2-all\9fahxiiecdb76a5g3aw9oi8rv\gradle-4.10.2-all.zip
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:61)
at org.gradle.wrapper.Install.createDist(Install.java:48)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:128)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
Command: C:\android\flutter_app\android\gradlew.bat -v


Update index.md in css/web-safe-fonts

You can also download fonts and add them to your website files. It can make the fonts more efficient.

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding.


:sparkles: Feat: Default solc to 0.8.23

Description
Make it so solc is no longer needed as peer dep
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #723

PR #724

PR #725   👈

This stack of pull requests is managed by Graphite.


Option to hide/disable the "open in new tab" icon

Basically title, I have no use for it and more often than not I keep pressing it by mistake, please add an option to hide it or disable it.

Thanks for your feedback, the latest version(v2.0.2) already supports this feature!


Removed all the dead code.

Rationale
Just trying to solve the issue to get familiar with the rust tools, the build process, and the warnings.
Simply made warnings -> errors and then removed all the dead code.  This may not have been the right thing to do and if so, def let me know what I should have done :D  I didn't really ask for clarity so totally glad to redo it with a little direction.
Testing
Ran the tests that were already present and none seemed to break after I removed all this code.
For Reviewers

[ ] Verify version bumped in Cargo.toml

Also we verify that we manually bump the version in these PRs but should we also update the edition to the current year?

Added back the unhappy function and notated it as a test.

Closes #60


Setup a Digital Ocean team account for EMW

Setup an so other EMW developers can access the server, reference this tutorial: https://www.digitalocean.com/community/tutorials/how-to-use-digitalocean-team-accounts

I realize this isn't directly related to Meza1, but this seemed like a good place to capture system admin related stuff.

Not Meza. If we need this could add to enterprisemediawiki/common issues


OpenTracing polyglot example hooked into the instrumentation test framework

https://issues.jboss.org/browse/HWKAPM-734
Test consists of two images one java which is compiled during maven compilation and other for JS node app. Node image is compiled using docker-compose.
This can be merged after https://github.com/hawkular/hawkular-apm-opentracing-javascript/pull/11 is merged and new version of JS provider is released 0.1.1.

I have released JS provider 0.1.1 so this can go in.

Instumentation-framework has been updated, now It is possible to define json path expression in both side of the expression.
"verify": {
        "jsonPath": [
          {
            "left": "$[0].traceId",
            "right": "$[1].traceId",
            "operator": "EQ"
          }, {
            "left": "$.length()",
            "right": "2",
            "operator": "EQ"
          }
        ]
      }

retest this please

@pavolloffay Thanks!


Can I use only "highly customizable menu"?

In some cases I need only top part of Parchment (show only possible options and get user choice)
Is it possible?

No, sorry this isn’t possible at the moment. But I’m planning on adding it in the next version 👍

Thank you!

Hey
" But I’m planning on adding it in the next version 👍"
Did you added this feature?

Hi @chapayGhub! No, this turned a to be a bit more work that I originally thought. I will try to get something out over the next weeks 🙂

Thanks
Good luck

If you create standalone ui component from "highly customizable menu" with delegates/callbacks
Others can implement any ui logic for user selection in it

one UITableView with different content
collection of separate view controllers like now
show/hide subviews
....

"highly customizable menu" should be really helpfull ui component!

Yeah, I totally agree 😄


Add marconi-mamba package

Todos

[x] 17e937a wire up nix
[X] 01154c469231fd9a4ec6c9dde26a13ebf3715060 where to get ChainPoint from, cli?
[X] Comment added fa13a9b5a79f46aef075122ce368c1ac342aaff6 the NetworkId parser is copy-paste from cardano-node/cardano-cli/src/Cardano/CLI/Shelley/Parsers.hs::1883, add todo to import it instead whenever it's exported?
[X] rebased this onto main, while cherry-picked the required commints from unmerged ml/plt-647 get ml/plt-647 merged prior to this one and base this PR on main instead (It's based on ml/plt-647 because that exposes the Address->Utxo indexer as a library)

Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[ ] Formatting, PNG optimization, etc. are updated

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[ ] Reference the ADR in the PR and reference the PR in the ADR (if revelant)
[x] Reviewer requested

@zeme-iohk Could you help set this up in our nix configuration?

You want to add the LICENCE and NOTICE files inside the marconi-mamba folder, or the nix build will fail.
Then you may applied my suggested commit.

This PR is now based on main and not on https://github.com/input-output-hk/plutus-apps/pull/714, just cherry-picked the commits that this branch needed  (namely the first four: cf5b91f, 11d65a9, 84634a6, 6471cc1)

@eyeinsky Also add the package in the relevant places in nix/pkgs/haskell/haskell.nix. Base on what we do with marconi`.

CI error: {UNKNOWN}: Died at /nix/store/gwfrn3w2caqdjr7a6vkkcix60r8svvy2-hydra-0.1.20220215.e49dd9c/bin/.hydra-eval-jobset-wrapped line 813. at /nix/store/7r0iilv1hr4nbcgdw2gfgm2slap9hbpk-hydra-perl-deps/lib/perl5/site_perl/5.32.1/Catalyst/Model/DBIC/Schema.pm line 526 (link)

Did you try updating the file I mentioned above?

CI now fails for the fix I added for darwin/mac minis here by not being able to create a directory under /tmp

@eyeinsky Had the same problem in this PR: https://github.com/input-output-hk/plutus-apps/pull/728
Tried re-running Hydra and see if anything changes.

@eyeinsky You can fix the conflicts and update on main, as the darwin checks have been disabled

Got this rebased onto latest main, builds locally, waiting for CI to finish.

@koslambrou this can be merged, right?

@koslambrou this can be merged, right?

Yep!


Fix links at docs of .family

I just fixed links.
river_pod is just awesome!
And FYI,
the destination for the FutureProvider in this page is not found.
https://riverpod.dev/docs/concepts/modifiers/family
the link:
https://pub.dev/documentation/riverpod/latest/riverpod/FutureProvider-class.html

Thanks!


Fix data link in README

Simple PR to fix a broken demo data link in the README.

The hospital workflow is in a different section from the paper experiments, so I believe the data is in fact different.

See issue here: https://github.com/HazyResearch/eclair-agents/issues/13


Extensions UI renders over the Problems UI

VSCode Version: 1.40.0 and the latest insiders.
OS Version: Windows.

Steps to Reproduce:

Click on some extension in the Extension view, such as C/C++, C#, or Remote - WSL (others don't repro the bug).
Make sure the Problems pane is showing.

Bug: See the screenshot. It renders incorrectly. I think it's a recent regression.

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

Possible dup of #83209


disable rate limits

Let's disable these for now, since there seem to be some more tweaks needed. Will make a patch release too.

small suggestion below:
   const middleware: RequestHandler = (req, res, next) => {
-    const allowsUnauthenticated = unauthenticatedPredicates.some(predicate =>
+    const allowsUnauthenticated = !disabled && unauthenticatedPredicates.some(predicate =>
       predicate(req.path),
     );

reverting instead https://github.com/backstage/backstage/pull/23810


fix: remove existing widget selection implementation

Description
With the new widget selection UX. This existing implementation is no longer necessary.
This PR removes it
Fixes: #33131
Automation
/ok-to-test<EMAIL_ADDRESS>:mag: Cypress test results

[!CAUTION]
🔴 🔴 🔴 Some tests have failed.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/8960841989
Commit: 4f9c6d502869db0be61cabeb0e3368100457f1f8
Cypress dashboard:  Click here!
The following are new failures, please fix them before merging the PR:
cypress/e2e/Regression/ServerSide/QueryPane/DSDocs_Spec.ts
To know the list of identified flaky tests - Refer here

Communication
Should the DevRel and Marketing teams inform users about this change?

[ ] Yes
[x] No

👍🏽


CSS problems using Nova v3.29.0

Good morning
Just trying your package (thanks for it!) with Nova 3.29.0 and I can show the dropdown on my page but when I click on it, I can't see items. It seems that there is a css problem preventing the list to be visible. I think the list appears but can't be displayed due to css restrictions and I can't find myself which one is responsible for.
I'm using the native template.
Any help will be very welcome; thanks.

Solved by running php artisan view:clear ; php artisan route:clear ; php artisan cache:clear ; php artisan clear-compiled ; php artisan optimize and removing the content of the /bootstrap folder; didn't know why...


Feature Request: Export all the constants

Expected behaviour
All the constants would be exported.
Actual behaviour
Only the VERSION constant is exported in the index.html
Environment Details

Karma version 1.3.0

Reasoning
We use gulp and we want to specify the log level via the Server constructor but it would be more reliable to use the constants defined inside karma than magic string like 'DEBUG'

This should be a trivial change. I'm more than willing to do a pull request

Sure :) PR welcome.


comment out FKs to tables that aren't included in output

For example, I included three tables here Document, DocumentFolder and DocumentLabel.

This FK to Customer is broken, so the output for this column should be

the desired output is a little different from what's pictured above. The comment should start after the data type. Don't comment out the whole column


Make quarkus.artemis.url optional

Filed here so that we do not forget about https://github.com/quarkusio/quarkus/issues/18231 and possibly take the initiative to fix it. After it is fixed in Quarkus, we should add a test (a io.quarkus.test.QuarkusUnitTest-based one should be enough) for an app configuring its custom ConnectionFactory without providing quarkus.artemis.url

I just move the upstrem quarkus issue to https://github.com/quarkiverse/quarkus-artemis/issues/36


Update training-data-format.rst

Rasa x 0.2.22 gives this warning when uploading a nlu.md file which contains lookup elements:

Lookup Tables in nlu.md will be ignored
To include lookup tables, please upload lookup table files separately. Lookup tables within nlu.md will no longer be recognized.

Proposed changes:

Add a note that Rasa X will not accept lookup tables within the nlu.md file, but rather convert the list to a separate file and remove the table from the file. Not a major issue.

Status (please check what you already did):

[ ] made PR ready for code review
[ ] added some tests for the functionality
[x] updated the documentation
[ ] updated the changelog
[ ] reformat files using black (please check Readme for instructions)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the PR, we'll give it a review as soon as possible.

Hey @Krogsager! Thanks for your contribution and apologies for the delay. Unfortunately I believe this PR no longer applies since we decided to deprecate inline lookup tables (see here), so I'll need to close this PR - but we look forward to new PRs from you.


Add more options to initgrid.f90

Not all initial open channel setups' initial conditions are covered under initgrid.f90, some of them should be added. Ideally, the type of grid stretching should not be bound to the initial condition option, but it is not bad to keep things as they are right now and just add the other setups.

See #74 .


Error with certificates

Can't compile, during the execution of PFTLoadPlugins I receive the following erros on console:
2017-05-22 18:04:40.745009 TraceUtility[11040:8689735] Pruning certificate chain to<PHONE_NUMBER>3709551615
2017-05-22 18:04:40.745070 TraceUtility[11040:8689735] Trying to add a bogus certificate
2017-05-22 18:04:40.745094 TraceUtility[11040:8689735] An error occured while inserting an untrusted certificate into the chain
2017-05-22 18:04:40.821549 TraceUtility[11040:8689735] Pruning certificate chain to<PHONE_NUMBER>3709551615
2017-05-22 18:04:40.821594 TraceUtility[11040:8689735] Trying to add a bogus certificate
2017-05-22 18:04:40.821616 TraceUtility[11040:8689735] An error occured while inserting an untrusted certificate into the chain
2017-05-22 18:04:40.949662 TraceUtility[11040:8689733] Pruning certificate chain to<PHONE_NUMBER>3709551615
2017-05-22 18:04:40.949778 TraceUtility[11040:8689733] Trying to add a bogus certificate
2017-05-22 18:04:40.950121 TraceUtility[11040:8689733] An error occured while inserting an untrusted certificate into the chain
2017-05-22 18:04:41.039007 TraceUtility[11040:8689733] Pruning certificate chain to<PHONE_NUMBER>3709551615
2017-05-22 18:04:41.039128 TraceUtility[11040:8689733] Trying to add a bogus certificate
2017-05-22 18:04:41.039157 TraceUtility[11040:8689733] An error occured while inserting an untrusted certificate into the chain
Error: Error Domain=Instruments Plug-in Error Code=-6 "Document Missing Template Error" UserInfo={NSLocalizedDescription=Document Missing Template Error}
Program ended with exit code: 1

Same problem here. Would appreciate any solution to this.

Any news on this?

@Mkalla I managed to solved it after a bit of Objective-C study (I was not familiar with the language and I actually believe that I'm still not). The error message is not very straight-forward, but it suggests that the path to the trace file is incorrect. Using MAC, paths that rely on the use of "~" usually give bad responses. For instance, if your .trace file is in your Desktop try to give the path as "/Users/USERNAME/Desktop/MyTraceFile.trace" instead of "~/Desktop/MyTraceFile.trace". This solution worked for me.


Fix recent linter errors

Newer pull requests are getting linter errors to reformat files due to updates in the upstream.
This reformats the affected files using black, and pin it in requirements.txt; fixes a mypy error for a missing return type annotation.
However, I think we need to look into options like Poetry to do dependencies versioning properly in future follow-ups.

Merged, thanks @PIG208!


THORN-2457: update Guava and remove Netflix Guava module

Motivation
We use an ancient version of Guava. We should update it
to something more modern, ideally aligned to our base WildFly
version. Since Thorntail is still based on WildFly 15.0.1,
we should use Guava 25.0, per [1].
And since WildFly already ships a module for Guava (see [2]),
we can as well get rid of the special Netflix Guava module.
[1] https://github.com/wildfly/wildfly/blob/15.0.1.Final/pom.xml#L221
[2] https://github.com/wildfly/wildfly/blob/15.0.1.Final/feature-pack/src/main/resources/modules/system/layers/base/com/google/guava/main/module.xml
Modifications
Update Guava version and remove the Netflix Guava module.
Result
No behavioral change. Slightly easier maintenance.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you created a JIRA and used it in the commit message?
[x] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[ ] Have you built the project locally prior to submission with mvn clean install?

Apparently this version of Guava is too new for Selenium (which is brought in by Arquillian Drone). Coincidentally, there was a bug filed recently (THORN-2454) that I'd ultimately want to fix by removing Arquillian Drone completely. It's of no use to us, some plain HTTP Client (we tend to use fluent-hc) is a much better fit for that kinds of tests we use Arquillian Drone for.

Ah, the failures are all in HOWTOs, and those manage Guava version on their own. So it's a simple revert :-)

I also ran the standalone test suite locally, and it passes. Merging.


[$1000] composer not focused when user return from new chat option after opening keyboard shortcuts

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

open the app
press cmd+k to open new chat option
press cmd+I to open keyboard shortcuts
press Esc to close keyboard shortcuts
press Esc to close new chat option

Expected Result:
composer should be focused
Actual Result:
composer not focused
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Version Number: 1.2.88-0
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/226750788-f28ae383-94ce-4bc7-90b1-605879752424.mov
https://user-images.githubusercontent.com/43996225/226750949-3769a42f-ed35-4c73-a363-cfe2d76e3bf4.mp4
Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1679376630339789
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01b40339584b81a83d
Upwork Job ID:<PHONE_NUMBER>460521984
Last Price Increase: 2023-03-22

Triggered auto assignment to @slafortune (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Job added to Upwork: https://www.upwork.com/jobs/~01b40339584b81a83d

Triggered auto assignment to @kadiealexander (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane (External)

Triggered auto assignment to @bondydaa (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

adding this to the Focus Tracking issue https://github.com/Expensify/App/issues/15992

sorry @Ollyws I'm going throw a hold on this for the time being since we want to re-evaluate the composer focus stuff.

Still on hold.

@bondydaa is this one still on hold for the composer focus stuff?

Not overdue.

@bondydaa any thoughts on when this should come off hold?

no update from me, don't think any refactors are in the works on the compose input and i'm mostly focused on #wave8-uspm stuff

@bondydaa any updates here?

I'm going to make the executive decision to close this. It's definitely not a priority and doesn't affect a core workflow.


Add latest mongo drivers

Hi. I thought I would do a PR to include the latest mongo drivers to this repo
I ran into an issue connecting this to Mongo Atlas (and generally mongo with authentication) and the code on master was using a 5 yrs old driver which in the mongodb world is pretty old ;o)
I looked online never done any Go programming but found it valuable to try replace this mongodb service by using the latest official mongodb drivers
This now allows for connection strings such as
mongodb://localhost:27017
mongodb+srv://user:pass@localhost:27017
I tested it and I can perform all functions such as list messages, display one message, search, delete, add...

lgtm 🚀

hi @ian-kent @vmary2014
Ca you merge this?

hi @ian-kent @vmary2014 Ca you merge this?

I'd love to, but the PR is now 4yrs old and I don't have any rights on this. I think this project is not maintained anymore as the last commits to main are like 8yrs old. Shame. Feel free to pick my branch though hopefully it still works with recent versions of the Mongodb


refactor: Adding ability to convert field name from camelCase to UPPER_SNAKE_CASE if varName is not specified for @EnvField

This pull request adds a new feature to the envied package, allowing the conversion of field names from camelCase to UPPER_SNAKE_CASE if the @EnvField annotation is not provided with a specific varName. The motivation behind this enhancement is to adhere to the Effective Dart rules of naming conventions, which specify that variables and field names should start with lowercase letters and use uppercase for the first letter of each subsequent word, such as firstName, secondName, and getAllColors.
With this new functionality, the envied package will automatically transform the field names into UPPER_SNAKE_CASE format when the @EnvField annotation is not explicitly assigned a varName. This conversion ensures compliance with the prescribed naming conventions, promoting consistency and readability in the codebase.
The implementation includes logic to detect when the @EnvField annotation is not provided with a varName and applies the necessary transformation to convert the field name from camelCase to UPPER_SNAKE_CASE. This feature adds flexibility and convenience to the package, enabling developers to adhere to the recommended naming conventions effortlessly.
This pull request aligns with the goals of the envied package by promoting best practices and making it easier for users to adopt effective coding standards. It contributes to the overall quality and maintainability of projects utilizing the envied package.
Thank you for considering this pull request. I am confident that this feature will enhance the functionality and usability of the envied package, benefiting developers who strive to follow the Effective Dart naming conventions.

Hi @ryanaidilp
Can you please resolve the merge conflicts with the main branch?

Couple of observations:

this should not be a default behaviour but rather enabled by an annotation
you might also want to use somehting like recase instead of rolling your own string conversions

Couple of observations:

if this is a breaking change, it should not be a default behaviour but rather enabled by a flag
you might also want to use somehting like recase instead of rolling your own string conversions

import 'package:recase/recase.dart';

final String varName = 'camelCaseVariable'.constantCase; // becomes CAMEL_CASE_VARIABLE

Thank you for your feedback! I appreciate your suggestions.
Regarding your first point, I've implemented your advice and added a flag to enable and disable this feature. It's no longer the default behavior.
Additionally, I've integrated the recase package for more robust string conversions. Now, users can customize their string transformations easily.
I've already pushed these changes in my recent commit. Kindly review it, and feel free to let me know if you have any more suggestions or concerns. Your input is valuable to improve the package further.

@ryanaidilp Sorry to make you have to handle conflicts again but we just pushed some updates that have conflicts with this PR

@ryanaidilp Sorry to make you have to handle conflicts again but we just pushed some updates that have conflicts with this PR

No worries at all! I've resolved the conflicts in my recent commits. Let me know if there's anything else needed.


Move login settings into external config

That will allow easier update core via git without touching the existing config

Also, my text editor has been removed junk spaces at line endings, as little bonus 😉


Update things

Better to update or just leave the old build from upstream? Update transitive dependencies or not??? We mostly control the data being used, in any case.

I closed this, because I'm not sure we want our main separate from upstream, anyway. We can just point our job at this branch for now if we decide we want it.


Update R2/KJ to avoid mod-after-put when using ArrayBuffer

Prior to this change, R2/KV would allow post-call modification of the ArrayBuffer. This updates it to copy by default and detach with enablement of a compat flag.

Why is the compat flag needed? Was it not possible before that the data would be sent over the wire before any post-call modification could take place? If so, why would it not be acceptable to now always have that happen instead of just sometimes?

@jasnell can we instrument this with Sentry and see if anything is actually triggering this codepath? If we run for a while and no one is using it, it should be pretty safe to just adjust the default to not need a compat flag right?

So there are actually three modes here.
The old mode... which this PR removes, is that post-call changes are picked up in the put. e.g.
const u8 = new Uint8Array(10);
u8.fill(1);
const p = bucket.put(..., u8);
u8.fill(2);  // the bucket sees [2,2,2,....] when it should see [1,1,1,....]
await p;

The new default mode is that post-call changes are ignored because the ArrayBuffer is copied. However, the passed in ArrayBuffer/Uint8Array is still usable by user code.
const u8 = new Uint8Array(10);
u8.fill(1);
const p = bucket.put(..., u8);
u8.fill(2);  // the bucket sees [1,1,1,1....] but the u8 is still directly usable
console.log(u8.byteLength);  // still prints 10
await p;

This comes at the cost of the potentially expensive copy.
With the compatibility flag, we avoid the copy but post-call, the Uint8Array is no longer usable, which could break user code.
// with the compat flag set...
const u8 = new Uint8Array(10);
u8.fill(1);
const p = bucket.put(..., u8);
u8.fill(2);  // the bucket sees [1,1,1,1....] but the u8 is NO LONGER directly usable
console.log(u8.byteLength);  // prints 0!!
await p;

The best we could do with the sentry log is detect how often someone passes in an ArrayBuffer. We cannot detect if they are continuing to use the ArrayBuffer after the put. This could break, for instance, if someone is doing additional logging of the buffer after the put, or directing it somewhere else.
// with the compat flag set...
const u8 = new Uint8Array(10);
u8.fill(1);
const p = bucket.put(..., u8);
u8.fill(2);  // does nothing, the bucket sees [1,1,1,1....] but the u8 is NO LONGER directly usable
console.log(u8);  // prints nothing!!!
await p;

We need the compat flag because of this side effect


Added polls label on issue without a poll

This issue includes a URL that has polls, which appeared to trigger the polls app: https://github.com/probot/probot.github.io/issues/95
e.g.
[Take my poll](https://example.com/poll/vote)

Actually, I misunderstood what triggered it. Here's the code in question
Errno::ENOENT: No such file or directory @ rb_sysopen -
/home/travis/.rvm/rubies/ruby-2.4.0/lib/ruby/site_ruby/2.4.0/bundler/templates/Executable
An error occurred while installing concurrent-ruby (1.0.5), and Bundler cannot
continue.
Make sure that `gem install concurrent-ruby -v '1.0.5'` succeeds before
bundling.

It appears that the line starting with /home/travis/.rvm/rubies/ruby-2.4.0/lib/ruby/site_ruby/2.4.0/bundler/templates/Executable is triggering the poll behavior.

This should be fixed now. Thanks for reporting!
Close it via RegExp bugfix PR#14.
Please feel free to reopen this issue if the problem still occurs.


Reading multiple xml files in parallel results invalid schema for the xml

There is an issue w.r.t xml connector, if 2 xml files are read at same time then there is a high possibility that one of the xml doesn't parse the schema. This issue is because of the below code
context.hadoopConfiguration.set(XmlInputFormat.START_TAG_KEY, s"<$rowTag>")
 context.hadoopConfiguration.set(XmlInputFormat.END_TAG_KEY, s"</$rowTag>")
 context.hadoopConfiguration.set(XmlInputFormat.ENCODING_KEY, charset)

Steps to reproduce
val failedAgesSet = mutable.Set[Long]()
    val threads_ages = (1 to 10).map { i =>
      new Thread {
        override def run() {
          val df = spark.read.option("rowTag", "person").format("xml")
            .load(resDir + "ages.xml")
          if (df.schema.fields.isEmpty) {
            failedAgesSet.add(i)
          }
        }
      }
    }

    val failedBooksSet = mutable.Set[Long]()
    val threads_books = (11 to 20).map { i =>
      new Thread {
        override def run() {
          val df = spark.read.option("rowTag", "book").format("xml")
            .load(resDir + "books.xml")
          if (df.schema.fields.isEmpty) {
            failedBooksSet.add(i)
          }
        }
      }
    }

    threads_ages.foreach(_.start())
    threads_books.foreach(_.start())
    threads_ages.foreach(_.join())
    threads_books.foreach(_.join())
    assert(failedBooksSet.isEmpty)
    assert(failedAgesSet.isEmpty)

Correct Log
22/05/31 20:53:12 INFO |Executor task launch worker for task 0.0 in stage 6.0 (TID 6)|  xml.XmlRecordReader: file is file:/Users/sandeep.katta/sourcecode/databricks/spark-xml/spark-xml/src/test/resources/books.xml:0+5542 and startTag is <book> and endTag is </book>
In-Correct Log which parses incorrect tag book, ideally the tag should be person
22/05/31 20:53:12 INFO |Executor task launch worker for task 0.0 in stage 5.0 (TID 5)|  xml.XmlRecordReader: file is file:/Users/sandeep.katta/sourcecode/databricks/spark-xml/spark-xml/src/test/resources/ages.xml:0+265 and startTag is <book> and endTag is </book>

Fixed, thank you!


Raii

With this you don't have to manage heap memory manually anymore and its exception save.
Could you please have a look at 33fffb61c947a03c0cf9e1cd3b82bbcd65648464

In general looks good to me.
Regarding the question: The problem here is / was to stop the program execution if the "help option" was detected. Now this changed to be implemented via a custom exception. No matter if we return true or false, the execution will continue. We could also exit here, but potentially this is also not an ideal solution (was always a kind of workaround; obviously it is not good / easy to test, and not as flexible as potentially desired). If the run_and_exit_if_error method is used, we should return false. However, the help is a legit option and does is no real error (so true is the real result). Nevertheless, returning true will obviously treat everything is "alright", and thus prevent the program from exiting.
Long story short: I think neither true nor false are suitable here. false is a lie, true will introduce a bug / unwanted behavior. I would leave this untouched for now and tackle it sometime later (I think we would need a better concept here).

how about returning an enum class like
enum class {FAIL, EXIT_WITH_SUCCESS, SUCCESS}

The names are a quick shot, but you get the idea.

Yes, I was thinking the same, but the question is - how does it play with a method like run_and_exit_if_error . It would still continue. How would the user know if he has to stop program execution and why? Maybe you have a good idea for an API that is sound and easy.

In my opinion, it is not the responsibility of the parser to exit the program.
Just parse and return success/failure.
And the user of this parser makes a decision depending on the parser result.
In example throwing an exception or exit his program with exit(int).
My suggestion would be, to remove  run_and_exit_if_error from the parser.

Of course, you are right that this is not the main responsibility. However, for convenience this method was introduced and is used quite often as far as I can see.
Regarding the enum - on second thought we have actually flags. We have

Success / Failure (in parsing)
Continue / Exit (overall result)

The happy path is either success with continue or failure with exit, however, we can also have success with exit or failure with continue (the latter could be that some parsing condition fails, but since the argument is optional this could be ignored; currently not implemented but it is a possibility).

Today I read about signal handling.
It seems it is not that portable, as it could.
A signal (like from exit(int)) gets emitted no destructors will get called.
Maybe this does not hurt for heap memory for small programs.
I don't know if the not freed memory is lost until next reboot.
What if the system is supposed to not reboot for months/years?
What is, if the user of the parser manages other resources ( i.e. files, network)?
With the parser calling exit() the user is forced to do proper signal handling to free his resources.
Does she/he know?
I really have mixed feelings about this exit() stuff.
If you want the parser influence the control flow, I would suggest exceptions.
These are portable and destructors will get called properly.
Initially I wanted to use your parser for my csv2xls.
I enjoyed working on the parser and I learned new things.
Thank you for that.
But as long as it emits signals, I don't want to use it.
With kind regards

All OSs free the resources allocated from an application when it exits. Otherwise, we would be doomed. exit is a sane and natural call.
And I think you misunderstood - its an opt-in and the parser does not exit for you if you do not wish to do that. It's a convenience method that can be used. But feel free to use something more appropriate for your workflow! Thanks for contributing 👍 !

Feel free to merge the PR anyway or at least cherrypick 42320bf please.


Workers cannot find images from GitHub Package Registry

Bug description
Since we use GitHub Package Registry instead of DockerHub to host our images, only the manager node can pull the images. We get "No such image: docker.pkg.github.com/..." when it tries to run on a worker node. It seems that the worker nodes don't have the necessary information to pull an image from a custom registry.
Here is how I understood there was a problem:

As you can see, all containers on the worker node are rejected. Only the manager node manages to run the containers.
Here is the error message on the rejected container:

Here is an example on a stack. See how many rejected before it finally launches:

Expected behavior
Normally it should be able to pull the new image, no matter if it's a manager node or a worker node.
Steps to reproduce the issue:

On Portainer, go to 'Registries'
Add a new registry
Enter as Registry URL 'docker.pkg.github.com', enable Authentication, enter your github credentials
Push one of your images on GitHub Package Registry with the following command: docker login -u GITHUB_USERNAME -p GITHUB_PASSWORD https://docker.pkg.github.com && docker push docker.pkg.github.com/ORG_NAME/REPO_NAME/IMAGE_NAME:TAG
On Portainer, go to 'Stack'
Add a new stack
Enter a docker compose file of your own, and enter as an image the new image pushed to GitHub Package Registry (image: docker.pkg.github.com/ORG_NAME/REPO_NAME/IMAGE_NAME:TAG)
Deploy the stack
See the bug: many containers appear as rejected before finally running

Technical details:

Portainer version: 1.22.1
Docker version (managed by Portainer): Docker CE for AWS 18.09.2-ce
Platform (windows/linux): linux (AWS EC2)
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): curl -L https://downloads.portainer.io/portainer-agent-stack.yml -o portainer-agent-stack.yml && docker stack deploy --compose-file=portainer-agent-stack.yml portainer
Browser: Chrome

Solved the issue. More details:
This bug arises when there are conflicts among images (old cache images etc.). The solution is to clean all unused images from the cluster. You have to connect to one manager server of your cluster.
When connected to the manager server, you can then run the following two commands:
$ docker images -q |xargs docker rmi
This will erase all unused images.  Select all images with the Unused tag, and remove them.


Respond to https://hypothes.is/a/2uBOztoHEemjDcflCgPAPg

Respond to hypothes.is annotation 2uBOztoHEemjDcflCgPAPg on https://jrnold.github.io/r4ds-exercise-solutions/data-visualisation.html (user<EMAIL_ADDRESS>created: 2019-09-18T11:31:28.252693+00:00, updated: 2019-09-18T11:31:28.252693+00:00)

Is there not something missing here?

Link: https://hyp.is/2uBOztoHEemjDcflCgPAPg/jrnold.github.io/r4ds-exercise-solutions/data-visualisation.html

Already fixed.


Module '"#app"' has no exported member 'useRouter'

Environment

Operating System: Windows_NT
Node Version:     v16.17.0
Nuxt Version:     2.16.0-27720022.54e852f
Nitro Version:    0.5.4
Package Manager<EMAIL_ADDRESS>Builder:          webpack
User Config:      target, ssr, env, head, css, plugins, components, buildModules, modules, autoImports, vite, router, serverHandlers, devServerHandlers, bridge
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules<EMAIL_ADDRESS>unplugin-vue-setup-extend/nuxt<EMAIL_ADDRESS>
Reproduction
"@nuxt/bridge": "npm:@nuxt/bridge-edge",
Describe the bug
After the last update I cannot use useRouter

Additional context
No response
Logs
No response

My bad, duplicate of https://github.com/nuxt/framework/issues/2272. Sorry


Do not use java.util.Stack

It uses synchronization, which is rarely desirable. Use ArrayDeque instead.

No, I haven't benchmarked this particular change in any place I've made it since I convinced myself it is always worthwhile, over 15 years ago :)

Haha I fully trust you on this one!
Thanks for the change!
Lgtm

It uses synchronization

I didn't know that. we definitely don't need synchronization here


Hi there are some Error in Xcode Version 10.0 beta (10L176w) & Swift 4.x

like this

seeing the same here

I believe that this a duplicate of #975

seeing the same issue

I have created a PR at https://github.com/Hearst-DD/ObjectMapper/pull/978 to hopefully fix this issue. I noticed, after creating it, that another PR exists which has failed tests. Hopefully this produces the right results!

Is there any timeline to be getting a fix in for this? I would like to be moving forward using Xcode 10 to prep for iOS 12, however, this is making it so I cannot even compile our main app. Thanks in advance!

Hi Josh! Feel free to contribute to the PR to help us get closer to a working build. I believe this PR technically works, so you would be able to check the branch out directly into your project.

seeing the same issue

When the update will come.I will transfer if not?

The compile errors are caused by a change in Swift 4.2 described in Abolish ImplicitlyUnwrappedOptional type Swift Evolution.
I have forked the repo and fixed the compile errors, but I don't think it should be merged into master yet. @tristanhimmelman would you accept a PR into master, or could you perhaps create a swift4.2 branch that we can submit PR's against?

There are already three PRs pending for this issue (#976, #978, #980), one of which have passed all tests.

Saw that moments after posting my comment. Great to have options to choose from ;-)

#980 solved


Added advanced searching by usage rights

Needed this functionality and thought I might as well make a pull request. Documentation is in the comment, let me know if I should add it anywhere else.

Thanks for your contribution @KhoomeiK !
I modified it a bit to have a more flexible way of adding options. Right now it is restricted to our own custom mapping. I have added the possiblity to add custom 'tbs' variables. See: https://github.com/pevers/images-scraper/pull/39
I added your comments + description to the examples and README. Thanks again!


Unable to List Collections.

Thanks very much for your work on the DocumentDB SDK for Ruby!
I don't seem to be able to list collections, I may be doing something really stupid, but also, MS may have changed something that has broken the SDK.
my sample code looks like this:
require 'documentdb'

url_endpoint = "https://xxxx.documents.azure.com:443/"
master_key = "xxxx"

context = Azure::DocumentDB::Context.new url_endpoint, master_key
database = Azure::DocumentDB::Database.new context, RestClient

db_instance_id = database.list["Databases"][0]["_rid"]
collection = database.collection_for_rid db_instance_id
puts collection.list

when I call collection.list, RestClient returns a 400
jim:documentDB jimb$ ruby docdb.rb
/Users/jimb/.rvm/gems/ruby-2.3.0@docdb/gems/rest-client-1.8.0/lib/restclient/abstract_response.rb:74:in `return!': 400 Bad Request (RestClient::BadRequest)
    from /Users/jimb/.rvm/gems/ruby-2.3.0@docdb/gems/rest-client-1.8.0/lib/restclient/request.rb:495:in `process_result'
    from /Users/jimb/.rvm/gems/ruby-2.3.0@docdb/gems/rest-client-1.8.0/lib/restclient/request.rb:421:in `block in transmit'
    from /Users/jimb/.rvm/rubies/ruby-2.3.0/lib/ruby/2.3.0/net/http.rb:853:in `start'
    from /Users/jimb/.rvm/gems/ruby-2.3.0@docdb/gems/rest-client-1.8.0/lib/restclient/request.rb:413:in `transmit'
    from /Users/jimb/.rvm/gems/ruby-2.3.0@docdb/gems/rest-client-1.8.0/lib/restclient/request.rb:176:in `execute'
    from /Users/jimb/.rvm/gems/ruby-2.3.0@docdb/gems/rest-client-1.8.0/lib/restclient/request.rb:41:in `execute'
    from /Users/jimb/.rvm/gems/ruby-2.3.0@docdb/gems/rest-client-1.8.0/lib/restclient.rb:65:in `get'
    from /Users/jimb/.rvm/gems/ruby-2.3.0@docdb/gems/azure-documentdb-sdk-0.2.1/lib/collection/collection.rb:22:in `list'
    from docdb.rb:11:in `<main>'

Is this expected, what would I be doing wrong?
The DocumentDB has one Database, with one collection, with one document in it.

Hi there,
did you ever find out of this - get the same error when trying.


Meta: Stage 3 Specification Reviews

[ ] Stage 3 Specification Review - msaboff (#8)
[ ] Stage 3 Specification Review - ljharb (#9)
[ ] Stage 3 Specification Review - waldemarhorwat (#10)

@msaboff, @ljharb, @waldemarhorwat - Please note, I'm looking to merge #7 shortly which has a few changes to simplify the design based on feedback, and has full specification text.

@rbuckton I'll review it in the next few days.

#7 has been merged, so the content of the explainer and full spec text at https://tc39.es/proposal-regexp-match-offsets/ are up to date.

I did a full review and found a number of bugs in the specification. See issue #10 for the details.

Setting aside the issues that @waldemarhorwat found, I don't find any other issues with the spec text doing what the current proposal describes.  If that is the way we decide to go, count me as reviewed.
I have concerns that there is a late push to either always create the indices or add methods to retrieve them from the match result, and the related impact on the spec text.  I think we need to resolve between the three choices that various people are advocating before stage 3.
From an implementers point of view I have some concern with the either always creating an indices property, or adding a captureStart() and captureEnd() methods on the result.  Like V8, JavaScriptCore creates indices during matching (* most of the time), however the native C++ array of integers is a local variable that is thrown away after the equivalent of RegExpBuiltinExec has been run and the string result(s) are materialized.  Obviously we'd have to persist this data in the match result.
RegExp's are performance sensitive for many applications and this is reflected in the various JavaScript benchmarks out there.  We need to be careful that we don't hurt some implementations with whatever option we choose.
Lastly, I don't want to muddy the waters more, but wasn't there an earlier proposal that always returned the captured strings and made the indices optional?  The current proposal is an either or kind of thing.
* JSC doesn't create indices during matching when they'll never be used, e.g. when RegExp.prototype.test() is called.

@msaboff: The version of the spec in master uses a property on an options object to indicate whether to return substrings or [startIndex, endIndex] pairs. This avoids any memory overhead for existing RegExp cases, but requires threading the options object through @@match and @@matchAll. The #14 PR goes back to something like the Stage 1 proposal in that it doesn't need the options object, but may have additional memory overhead.
I plan to discuss both in committee next week to gauge whether implementers feel this overhead is acceptable.

@msaboff: The version of the spec in master uses a property on an options object to indicate whether to return substrings or [startIndex, endIndex] pairs. This avoids any memory overhead for existing RegExp cases, but requires threading the options object through @@match and @@matchAll. The #14 PR goes back to something like the Stage 1 proposal in that it doesn't need the options object, but may have additional memory overhead.

I'm aware that the current spec's options threading doesn't impact memory.  It was the other options being considered that might have memory impact.

I plan to discuss both in committee next week to gauge whether implementers feel this overhead is acceptable.

I fully expect that along with what the whole committee thinks about the three options on the table.

three options

What is the third option? Or by a third option do you just mean choosing not to advance the proposal?

Like V8, JavaScriptCore creates indices during matching (* most of the time), however the native C++ array of integers is a local variable that is thrown away after the equivalent of RegExpBuiltinExec has been run and the string result(s) are materialized. Obviously we'd have to persist this data in the match result.

Here's what the memory overhead would be for V8:

If done carefully, the memory overhead would be at most 2 ints per capture. Assuming 4-byte integers, that's comparable to each captured string being 8 [ASCII] characters longer.

For JSC, are you anticipating something different? I'm trying to understand if you're concerned with a JSC-specific implementation detail, or just with adding any overhead at all.

@waldemarhorwat, @ljharb, @msaboff: For each of you, can I consider the specification text both in master and in #14 to be fully reviewed? If so that means I could possibly move forward with a request for Stage 3 depending on the outcome of the discussion around #12 both here and during committee.

Like V8, JavaScriptCore creates indices during matching (* most of the time), however the native C++ array of integers is a local variable that is thrown away after the equivalent of RegExpBuiltinExec has been run and the string result(s) are materialized. Obviously we'd have to persist this data in the match result.

Here's what the memory overhead would be for V8:

If done carefully, the memory overhead would be at most 2 ints per capture. Assuming 4-byte integers, that's comparable to each captured string being 8 [ASCII] characters longer.

For JSC, are you anticipating something different? I'm trying to understand if you're concerned with a JSC-specific implementation detail, or just with adding any overhead at all.

I think our memory overhead would be about the same.

As an editor: Confirm that master looks good if we go with an options object (modulo #16, #17); as does #14.
As a delegate: on master, i think that replace when functionalReplace is true and matchOptions.[[Capture]] is ‘indices’ should not throw, but should do something useful. Similarly, on #14, should replace with a function get indices info? (i think it probably should somehow)

should not throw, but should do something useful

Any thoughts on what that "something useful" might be?  "abc".replace("b", "d", { capture: "indices" }) doesn't make a lot of sense, so throwing is the safest option (since the restriction can always be loosened later). "abc".replace("b", ([start, end]) => { ... }, { capture: "indices" }) make a little more sense, since you can chose what to do with those indices.

Right - I'd expect it to throw in the non-function case, but to provide the indices somehow in the function case.

Ah, I see. The spec does not contain any changes for RegExp.prototype[@@replace]. I will file a PR shortly.

It might be worth getting the committee's opinion before merging it, but it'd be great to have it lined up and reviewed :-)

@waldemarhorwat, @ljharb, @msaboff: For each of you, can I consider the specification text both in master and in #14 to be fully reviewed? If so that means I could possibly move forward with a request for Stage 3 depending on the outcome of the discussion around #12 both here and during committee.

I just posted my review of the #14 variant. I found a few algorithm logic bugs, but they are all simple to fix. Assuming you fix them, I'm happy with that variant (and at this point very much prefer it).


what will happen if I modify some config

In config/global_config.py, I find the following config
Set the shadownet validation batch size
__C.TRAIN.VAL_BATCH_SIZE = 8
Set the learning rate decay steps
__C.TRAIN.LR_DECAY_STEPS = 410000
Set the learning rate decay rate
__C.TRAIN.LR_DECAY_RATE = 0.1
Set the class numbers
__C.TRAIN.CLASSES_NUMS = 2
Set the image height
__C.TRAIN.IMG_HEIGHT = 256
Set the image width
__C.TRAIN.IMG_WIDTH = 512
what will happen if I change the IMG_HEIGHT and IMG_WIDTH to a bigger value? thanks.

@passion3394 That means the model will cost more gpu memory so you may reduce the batch size according to your gpu device:)

@MaybeShewill-CV what's the criteria of the modifying? the IMG_HEIGHT and the IMG_WIDTH should be divided by 16 or 32?

@passion3394 That may depends on the experiment I have not tested it before:)

theoretically, if I modify the  IMG_HEIGHT and the IMG_WIDTH to a higher value, the precision will higher? because we use more features in one batch.

@passion3394 The precision and the size of input tensor are not that related:)

@passion3394 That depends on the data that fed into the model and the data that you want to process with:)

@MaybeShewill-CV I use my own dataset, and train the model about 20000 steps, but the training loss is always about 1.2, and the training accuracy is about 75%, the learning rate multiplys by 0.9 every 1000 step. Can you give me some advise about the training process?

@MaybeShewill-CV the dense net is better than vgg?

@passion3394 You may test it:)

@MaybeShewill-CV Hi, I have two question, could you tell me something about them.
(1)The paper says that they do the model on the 512 * 256 size images, what if I modify the model and apply to other size of images?  Can this way work on the lanenet-lane-detection code?
(2)I want to get the coordinates of the detected lanes, and I have dug into the code, saw these codes:
def _get_lane_area(binary_seg_ret, instance_seg_ret):
"""
通过二值分割掩码图在实例分割图上获取所有车道线的特征向量
:param binary_seg_ret:
:param instance_seg_ret:
:return:
"""
idx = np.where(binary_seg_ret == 1)
    lane_embedding_feats = []
    lane_coordinate = []
    for i in range(len(idx[0])):
        lane_embedding_feats.append(instance_seg_ret[idx[0][i], idx[1][i]])
        lane_coordinate.append([idx[0][i], idx[1][i]])

    return np.array(lane_embedding_feats, np.float32), np.array(lane_coordinate, np.int64)

the coordinates are computed through the resized 512*256 image?

@passion3394 1.The model can be feed into a input tensor with different size. 2.The coord are computed through the resized 512*256 image

@MaybeShewill-CV ok,thanks, I just want to try if I modify the 512*256 to other size of the network,  will the network get a better precision? especially on custom datasets.

@passion3394 You may test it:)

@MaybeShewill-CV ok, thanks,will close this issue.

@MaybeShewill-CV how to calculate the accuracy of lanenet? is that similar with the IoU in the semantic segmentation?

@passion3394 You may refer to this #101 to see if it can help you:)

@MaybeShewill-CV thanks, it helps me a lot.

@passion3394 Welcome:)


TETP-34: CRUD operations for developing

Description :sparkles:

startapp postings (this will be used to communicate with LinkedEvents in production)
create model TetPostingTemp and views for CREATE and READ operations that are enabled when
NEXT_PUBLIC_MOCK_FLAG is set

This setup helps us test the frontend against the backend while developing and in the review environment.
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

Codecov Report

Merging #636 (f5d25e6) into develop (0a81a0a) will increase coverage by 19.35%.
The diff coverage is 52.12%.

@@             Coverage Diff              @@
##           develop     #636       +/-   ##
============================================
+ Coverage    64.38%   83.73%   +19.35%
============================================
  Files          724       54      -670
  Lines        18271     1592    -16679
  Branches      1763        0     -1763
============================================
- Hits         11763     1333    -10430
+ Misses        6180      259     -5921
+ Partials       328        0      -328

Impacted Files
Coverage Δ

backend/tet/tet/settings.py
93.61% <ø> (ø)

backend/tet/postings/views/mock_views.py
27.90% <27.90%> (ø)

backend/tet/postings/views/linkedevents_views.py
50.00% <50.00%> (ø)

backend/tet/postings/urls.py
75.00% <75.00%> (ø)

backend/tet/postings/apps.py
100.00% <100.00%> (ø)

backend/tet/postings/migrations/0001_initial.py
100.00% <100.00%> (ø)

...tings/migrations/0002_alter_tetpostingtemp_data.py
100.00% <100.00%> (ø)

backend/tet/postings/models.py
100.00% <100.00%> (ø)

backend/tet/tet/urls.py
83.33% <100.00%> (+2.08%)
:arrow_up:

backend/shared/shared/ytj/ytj_client.py
27.58% <0.00%> (-65.52%)
:arrow_down:

... and 682 more

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 0a81a0a...f5d25e6. Read the comment docs.

This approach is not needed at the moment.


How to re-throw exceptions?

We are trying to re-throw exceptions as follows. But this way is not only ugly but also takes care of only the last continueWithBlock:.
What would you guys suggest on this?
[[task continueWithBlock:^id(BFTask *task) {
        //throws an exception
        return nil;
    }] continueWithBlock:^id(BFTask *task) {
        dispatch_async(dispatch_get_main_queue(), ^{
            if (task.exception) {
                @throw task.exception;
            }
        });
        return nil;
    }];

Sorry may I ask what is the rational behind closing an issue just because "it is not obvious to you what the solution would be"?
I must agree with the fellow developers above that Bolts masking all exceptions is a feature that makes maintaining a production level code very difficult.


[DEV] Update XML tests to eliminate false failures

I noticed that some XML tests are failing sometimes. Iterating on maps doesn't guarantee order so the generated XML nodes aren't always in the same order. This updates those tests to assert the XML is generated as expected but node order won't cause a test failure.

Amazing! Thank you for the fixes. The test suite is a bit dated at this point.


Feature : other style than Material Design

Hi,
Do you think that it will be possible to add the possibility to use another style than the "Material Design" ?
By changing the CSS by example ?
By example, we have some styles defined by the CSS:  https://www.muicss.com/docs/v1/css-js/buttons
Do you think we can expect multiples styles support (one day) ?

@vd3d I think now that the css is separated from the MatBlazor package someone could easily create an alternative styling.  I am not an expert in sass but I believe you could build another sass file and set it up to do another style in prod.config.js
https://github.com/SamProf/MatBlazor/blob/face8ddbc81e021b9ad812aee64f980020530b38/src/MatBlazor.Web/webpack/prod.config.js

Thanks, yes it should be possible.
By example : https://blazorstrap.io/buttons
They have several themes (very basic ones), but here I'm sure we can do something more advanced !


[device_info_plus] Detect iOS simulator model identifier

Description
Currently, iosInfo.utsname.machine returns the underlying architecture of the iOS device when the device is a simulator. This updates the behavior to return the simulator's model identifier instead (e.g. iPhone 15,2 for an iPhone 14 Pro).
Related Issues
https://github.com/fluttercommunity/plus_plugins/issues/273
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated the version in pubspec.yaml and CHANGELOG.md.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Thanks for your contribution. Looks good to me, but would like to also hear opinion of other maintainers first.

Also, please fix issues detected by checks, like code formatting.

LMTG, needs the formatting fixed, and we can merge it.
Would it be possible to have an integration test for this as well? The setup is already done. The GitHub Action uses the iPhone 8 model on the simulator.

Formatted the objc code, and added a test to check that all iOS utsname fields are non-null

Hmm, not sure why package_info_plus_windows is failing to bootstrap since I haven't made any changes there.

Thank you!


check if floating label color were set before awakeFromNib

If you setup a RPFloatingPlaceholders instance in Xib/Storyboard and setup the floating label colors when overriding the setter in the viewController nothing happens because awakeFromNib es called after.

Looks good @nandodelauni ; thanks!

Thanks to you!


Fetch realm info of an unknown realm in code mode

This PR adds support for fetching realm info in code mode for code paths that do not belong to known realms–realms that are not in ownRealmURL or otherRealmURLs in the ENV variable.
I tested this by running a new local realm (named "jurgens"), which is not included in the variables mentioned above, and pointing the url bar to a code path in that realm. The realm icon, background, and the card instance from that realm are loaded fine so that's a sign that it works:

This PR also deserves a test but I'll first wait if people have some thoughts regarding whether it's conceptually ok to issue a fetch request in getRealmURLFor (see my comment in the PR)

@lukemelia nice catch, however the current file resource implementation wants the realm url so that it can load the file. So there is some roundaboutness and loading redundancy here. Let me see if I can make the file resource work directly with a card source url and give us the realm url from the response header (rather than other way around)

I changed things so that the file resource doesn't demand the realm url + relative path anymore, but instead it extracts the realm url from the X-Boxel-Realm-Url header when loading the file. Then it makes it available for the consumers of the file. With this I was able to simplify the chain of resources and shave off the redundant fetch


Bug: eth_requestAccounts not involve coinbase extension modal in iframe

Describe the bug
I use web3-react v6 and walletlink connector and our app running in iframe(shopify admin panel). Nothing happend after i clicked on coinbase button. I also try to trigger eth_requestAccounts dirictly with same result. When i open page without iframe -  coinbase extensions works well.
Steps
Open some dapp in iframe and click on connect Coinbase Wallet
Expected behavior
i expect that it's would connect with extension as good as on pages without iframe.
Or
Add a flag to disable extension check and just open qr-modal. i'm tryed to remove window.ethereum, but it didn't help.
We would like to add coinbase wallet for our customers, hope this get fixed.
Version
No response
Additional info
No response
Desktop
No response
Smartphone
No response

I'm having the exact same issue. Trying to open coinbase wallet extension from an  and nothing happens. Getting ERR_BLOCKED_BY_CLIENT when clicking coinbase login button and it's not activating the wallet. Works well outside of iframe. MetaMask works well running in and out of iframe.

This would be really helpful. We are building a product that can be embedded into any website. We can't do 1st party support for Coinbase Wallet for the time being.

Closing as duplicate. This issue is now being tracked here: https://github.com/coinbase/coinbase-wallet-sdk/issues/588


Login handling for premium websites

It would be nice to be able to enable newspaper to log in to be able to look past paywals.
I don't have an idea yet how to do it automaticaly but the login url and payload could be sniffed in chrome "network" and then supplied to newspaper by hand.
Here  are some ideas how to handle logins in urllib2 or with mechanize/selenium.

An available way to do this would be to scrape directly from Google's cache. Usually even paywalled content allow Google's scrapers through to build the search index.
Reference: http://stackoverflow.com/questions/4560400/how-can-i-get-the-google-cache-age-of-any-url-or-web-page


This library doesn't work in IE6

Most of the time I wouldn't make a big deal of this, but, BUT, I have a client who is dead set, read my lips DEAD SET on having infinite scrolling (with parallax effects) in IE6, and on his Blackberry two-way pager.
Listen, I understand this request might sound a bit ridiculous, but considering ScrollWatch is more of a "lower-level" library (and not really a UI component), I think this is very achievable and I would really appreciate you rolling in official support for these devices.
Thanks, cordially awaiting your timely reply.
Bernardo Fitzkerlad

Works for me ;)


MOI-level support for indicator constraints

Awesome, thanks!
One comment: It seems that SCIP fails when the indicator variable is not already binary. Could we add a check for that, similar to the bounds check in SOC constraints? Then, SCIP.jl would be spared (parts of) the nasty stacktrace.