LIST/APPEND wipes out the file rather than appending to it

Reported by Ansley B Manke on 19 Sep 2002 17:59 UTC
Bug report from Paul Kushner 19-Sep-2002.  Occurs on their
Origin, not under Linux or Solaris.
!print out the number 1
list 1
!print out the number 2
list 2
!remove the file eg.txt. "sp" spawns a shell command
sp rm eg.txt
!list the number 1 to eg.txt
list/file="eg.txt" 1
!append the number 2 to eg.txt
list/file="eg.txt"/append 2
!cat the file
sp cat eg.txt
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/445

Comment by<EMAIL_ADDRESS>on 4 Oct 2002 20:25 UTC
Fixed 10/2/02 - kob Turned out that an old -D flag wasn't necessary w/ the new
Fortran 90 compiler or w/ the new IRIX os.


Deprecated functions used in GitSourceControlUtils.cpp

When building the project, compiler warns that deprecated functions are being used in this plugin.
\UE4GitPlugin\Source\GitSourceControl\Private\GitSourceControlUtils.cpp(187): warning C4996: 'FWindowsPlatformMisc::GetEnvironmentVariable': void FPlatformMisc::GetEnvironmentVariable(Name, Result, Length) is deprecated. Use FString FPlatformMisc::GetEnvironmentVariable(Name) instead. Please update your code to the new API before upgrading to the next release, otherwise your project will no longer compile.

Fixed thanks to @CraftedCart

I don't think that was me ;P


Component conversion failed: Callback called multiple times

Summary
When I want to deploy code from VS code, most often I am getting this error 'Component conversion failed: Callback called multiple times'. Especially when it comes to deploying the static resource files. No one in the team has this issue, while we are all working on the same code and having the same extensions. The issue is solved only when VS code is restored, but then the issue appears all over again when I try to deploy some files.
Steps To Reproduce:

Right-click on a file/folder you want to deploy
Select SFDX: Deploy This Source To Org

Expected result
Expected is to have the files successfully deployed
Actual result
Code is not deployed to the org, and after that, nothing can be deployed, unless VS code is restarted.
System Information

Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.)
I am using cmd.exe

If you are using sfdx

Run sfdx version --verbose --json

If you are using sf

Run sf version AND sf plugins --core

Paste the output here

Additional information
This is the output. There is nothing more about it.

VSCode extensions is a different team/github https://github.com/forcedotcom/salesforcedx-vscode/issues and you may find information there (pinned issues, similar open issues) to help.
Is there a way to reproduce this with just the CLI (not using vscode)?


[5.2] Wrap and escape MySQL JSON path

Followup to PR #12964
Includes two tests (one related to #12964) to verify correct wrapping/escaping.

I'd rather use getPdo()->quote() from an associated connection instance instead of custom replacements with str_replace() but the grammar class has no access to the connection apparently.
OTOH is it possible to use prepared statements with bound parameters for the JSON path, like field->?? That would be way better. If MySQL doesn't allow this we could convert to JSON_EXTRACT(column, path) which is equivalent[1] and should allow bound parameters. Unfortunately wrapValue() is unable to inject bound variables.
[1] In MySQL 5.7.9 and later, you can use column->path with a JSON column identifier and JSON path expression as a synonym for JSON_EXTRACT(column, path).

Just tried: field->? is not allowed, but JSON_EXTRACT() would work.

I guess I don't understand why we are quoting column names? Are people really passing user input directly into their column names?

Are people really passing user input directly into their column names?

Well, if someone's not being careful with mass assignment, yes.

I don't really know if this is the correct way to prevent SQL injection. It seems pretty hacky and I don't know why people should be passing user input into their column names. I would rather just document not to allow users to control your column names in your queries.


Update cross-tenant-mailbox-migration.md

Updated usage of switch EnableLitigationHoldForMigration

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/6014


close #6447: fix type checking for primitive wrapper objects

What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[x] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[x] New/updated tests are included

Other information:
close #6447 .

I strongly support this PR. (And thanks for making it. I would have done myself but you beat me to it 😄) It solves a pretty big use case for a few users of my package Ziggy as outlined in https://github.com/tightenco/ziggy/pull/64

^ I'd like to note that this PR has way more upvotes than downvotes.

Merging since this is a somewhat implicit change and we probably will not document this behavior so that we don't "encourage code smell" for the users :)


Data formatting question for new analysis

Thank you for this tool and the manuscript, very interesting work.  I am currently trying to configure the pipeline.py script for running on my own plant genome (n=7).  Can the pipeline.py script be edited simply by removing steps "-1" and "0" and changing the structure of my own data to that specified in the manuscript (the Code section)?

I'm glad you found the tool and manuscript useful! Yes, you can customize the pipeline.py script to fit your own plant genome data. If you want to remove the initial steps ("-1" and "0"), you can simply comment them out or delete them from the script.
However, you will need to make sure that the structure of your data matches the expected format. For example, you will need to provide the file paths for your input FASTQ files, and adjust the parameters for the specific needs of your genome and data. Additionally, you may need to adjust the reference genome and annotation files used by the pipeline to match your own genome.
In general, it is recommended that you carefully review and understand each step of the pipeline and make adjustments as needed based on your own data and genome. Good luck with your analysis!

I'm glad you found the tool and manuscript useful! Yes, you can customize the pipeline.py script to fit your own plant genome data. If you want to remove the initial steps ("-1" and "0"), you can simply comment them out or delete them from the script.
However, you will need to make sure that the structure of your data matches the expected format. For example, you will need to provide the file paths for your input FASTQ files, and adjust the parameters for the specific needs of your genome and data. Additionally, you may need to adjust the reference genome and annotation files used by the pipeline to match your own genome.
In general, it is recommended that you carefully review and understand each step of the pipeline and make adjustments as needed based on your own data and genome. Good luck with your analysis!

Thank you for your quick response!  Will do, I will report back with how it performed!

Wanted to confirm something.  I put my own error-corrected reads (the ones I want to assemble with the trained and validated model) in one chromosome at a time, correct?  For example, GNNome-assembly/data/real/chr1/raw would contain my "chr1.fasta" file which would be reads specifically from chr1 only?

That is correct, but name it 0.fasta. I used this convention simply due to training on the data belonging to the same chromosome generated multiple times with different seeds (e.g., 15 x chr19 data for training would be 0.fasta, ..., 14.fasta).
Your path should then look like this:
GNNome-assembly/data/real/chr1/raw/0.fasta

That is correct, but name it 0.fasta. I used this convention simply due to training on the data belonging to the same chromosome generated multiple times with different seeds (e.g., 15 x chr19 data for training would be 0.fasta, ..., 14.fasta).
Your path should then look like this: GNNome-assembly/data/real/chr1/raw/0.fasta

Awesome, thank you!


Native waitUntilVisible failing with error response: 404 selector UiSelector[CONTAINS_TEXT=We couldn't save your card] found nothing

Steps to reproduce
Code is in a private repo.

Run native tests either using patrol develop/test on an android emulator API 31
See logs below on output

Actual results
Part of code:
Future updateAddressAfterAVSFailureOnPaymentMethodsViaPatrol(
String card, String cvv, String selectorTextTitle, String errorMessage, String check, $) async {
await $(newCardText).tap();
await nativeAddCardDetailsViaCheckoutUsingPatrolStep(card, cvv, $);
await Future.delayed(longDelay);
await $.native.waitUntilVisible(Selector(textContains: selectorTextTitle), appId: defaultDevAppId);
await $.native.waitUntilVisible(Selector(textContains: errorMessage), appId: defaultDevAppId);
await $.native.tap(Selector(text: patrolUpdateMyAddressButtonFinder));
await $(AppKeys.senderAddressScreenRoute_AddressLine1Key).enterText(commonAddressLine1);
await $(AppKeys.senderAddressScreenRoute_ContinueButtonKey).tap();
log('Check completed successfully for $check');
}
When running native tests with on a Webview, the following error is thrown
: ══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
: The following PatrolActionException was thrown running a test:
: Patrol action failed: NativeAutomatorClientException: waitUntilVisible() failed with Invalid
: response: 404 selector UiSelector[CONTAINS_TEXT=We couldn't save your card] found nothing
:
: When the exception was thrown, this was the stack:
: #0      NativeAutomator._wrapRequest (package:patrol/src/native/native_automator.dart:231:7)
:
: #1      NativeAutomator.waitUntilVisible (package:patrol/src/native/native_automator.dart:618:5)
:
: #2      updateAddressAfterAVSFailureOnPaymentMethodsViaPatrol (file:///Users/lew/Workspace/Protype/integration_test/flows/transaction_flow.dart:1335:3)
:
: #3      main. (file:///Users/lew/Workspace/Protype/integration_test/us_card_checks_test.dart:67:7)
:
: #4      patrolTest. (package:patrol/src/common.dart:140:7)
:
: #5      testWidgets.. (package:flutter_test/src/widget_tester.dart:171:15)
:
: #6      TestWidgetsFlutterBinding._runTestBody (package:flutter_test/src/binding.dart:935:5)
:
:
: The test description was:
:   US card flow
Logs
When running native tests with on a Webview, the following error is thrown
: ══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
: The following PatrolActionException was thrown running a test:
: Patrol action failed: NativeAutomatorClientException: waitUntilVisible() failed with Invalid
: response: 404 selector UiSelector[CONTAINS_TEXT=We couldn't save your card] found nothing
:
: When the exception was thrown, this was the stack:
: #0      NativeAutomator._wrapRequest (package:patrol/src/native/native_automator.dart:231:7)
:
: #1      NativeAutomator.waitUntilVisible (package:patrol/src/native/native_automator.dart:618:5)
:
: #2      updateAddressAfterAVSFailureOnPaymentMethodsViaPatrol (file:///Users/lew/Workspace/Protype/integration_test/flows/transaction_flow.dart:1335:3)
:
: #3      main. (file:///Users/lew/Workspace/Protype/integration_test/us_card_checks_test.dart:67:7)
:
: #4      patrolTest. (package:patrol/src/common.dart:140:7)
:
: #5      testWidgets.. (package:flutter_test/src/widget_tester.dart:171:15)
:
: #6      TestWidgetsFlutterBinding._runTestBody (package:flutter_test/src/binding.dart:935:5)
:
:
: The test description was:
:   US card flow
Patrol version
patrol v 2.2.2
Patrol Doctor output
In next major release, patrolTest method will be intended for UI tests.
If you want to use Patrol in your widget tests, use patrol_finders package.
For more information, see https://patrol.leancode.co/patrol-finders-release
Disable this warning by setting the PATROL_FINDERS environment variable.
Patrol CLI version: 2.2.2
Flutter Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.7, on macOS 14.3.1 23D60 darwin-arm64, locale en-KE)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 15.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] VS Code (version 1.86.1)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

@bartekpacia @jBorkowska any help with above


Ensure components list is scrollable

This PR makes some layout and style changes to the default style guide output

My existing codebase has a large number of components, running styleguidist on this results in a list of components that is not scrollable do the "sticky" functionality that currently exists.
This PR makes changes to the layout to ensure that the component list is always scrollable. The component list has been moved to the left of the screen due to the fact that there is a max-width on the styleguide(which i think is important) and implementing scrolling functionality with that given layout felt odd. It wasn't clear that you could scroll the components list, this approach goes for something a little more "traditional" as far as documentation styling goes.

Does it also fix #68?

@mik01aj Damn, i was JUST about to add that comment :)

LGTM, I like the simplification.

Cool, thanks! The only problem is now it’s shifted to the left side of the window which looks terrible on a big screen:

How about something like this?

Sidebar is on the left but the main area is centered. I also like the style guide title inside the sidebar.

I'm all for the title in the sidebar :+1:

Nice!


Pointers to Ciao and some libraries

By submitting this pull request, I promise I have read the contribution guidelines twice and ensured my submission follows it. I realize not doing so wastes the maintainers' time that they could have spent making the world better. 🖖

I've replaced this pull request by smaller ones. I hope these follow the contribution guidelines now. Sorry for the inconvenience. Thanks!


Flutter web content broken after host to server

I have created a project by flutter create myresume command and run on chrome. It's working fine(both release and debug mode). But when I host it (use this command flutter build web --release) to my shared-server then it's content has broken, text is showing like box.
I din't modify any code. Just create project and upload. How can I fix this ?
Expected results:
Google Drive Image Link. Click here
Actual results:
Google Drive Image Link. Click here

Logs

my  flutter run --verbose output here
abir@Abirs-MacBook-Pro myresume % flutter run --verbose
[ +120 ms] executing: sysctl hw.optional.arm64
[  +22 ms] Exit code 1 from: sysctl hw.optional.arm64
[        ] sysctl: unknown oid 'hw.optional.arm64'
[  +10 ms] executing: [/usr/local/Caskroom/flutter/2.0.2/flutter/] git -c log.showSignature=false log -n 1
--pretty=format:%H
[  +20 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] 02c026b03cd31dd3f867e5faeb7e104cce174c5f
[        ] executing: [/usr/local/Caskroom/flutter/2.0.2/flutter/] git tag --points-at
02c026b03cd31dd3f867e5faeb7e104cce174c5f
[  +27 ms] Exit code 0 from: git tag --points-at 02c026b03cd31dd3f867e5faeb7e104cce174c5f
[        ] 2.2.1
[   +6 ms] executing: [/usr/local/Caskroom/flutter/2.0.2/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +14 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/usr/local/Caskroom/flutter/2.0.2/flutter/] git ls-remote --get-url origin
[  +14 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[ +105 ms] executing: [/usr/local/Caskroom/flutter/2.0.2/flutter/] git rev-parse --abbrev-ref HEAD
[  +15 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[   +7 ms] executing: sw_vers -productName
[  +16 ms] Exit code 0 from: sw_vers -productName
[   +1 ms] macOS
[        ] executing: sw_vers -productVersion
[  +14 ms] Exit code 0 from: sw_vers -productVersion
[        ] 11.4
[        ] executing: sw_vers -buildVersion
[  +15 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 20F71
[  +63 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +3 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +55 ms] executing: /Users/abir/Library/Android/sdk/platform-tools/adb devices -l
[  +11 ms] executing: sysctl hw.optional.arm64
[   +4 ms] Exit code 1 from: sysctl hw.optional.arm64
[        ] sysctl: unknown oid 'hw.optional.arm64'
[        ] executing: xcrun xcodebuild -version
[ +113 ms] Exit code 0 from: xcrun xcodebuild -version
[        ] Xcode 12.5
           Build version 12E262
[   +3 ms] executing: xcrun xcdevice list --timeout 2
[   +4 ms] xcrun simctl list --json devices
[        ] executing: xcrun simctl list --json devices
[  +45 ms] List of devices attached
[  +94 ms] {
             "devices" : {
               "com.apple.CoreSimulator.SimRuntime.watchOS-7-4" : [
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/724AC345-485C-4624-86D5-749D3B825B96\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/724AC345-485C-4624-86D5-749D3B825B96",
                   "udid" : "724AC345-485C-4624-86D5-749D3B825B96",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-5-40mm",
                   "state" : "Shutdown",
                   "name" : "Apple Watch Series 5 - 40mm"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/E2AD18E5-46BE-47A7-AB41-7B40F203BD43\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/E2AD18E5-46BE-47A7-AB41-7B40F203BD43",
                   "udid" : "E2AD18E5-46BE-47A7-AB41-7B40F203BD43",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-5-44mm",
                   "state" : "Shutdown",
                   "name" : "Apple Watch Series 5 - 44mm"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/E5B2E2A1-4A87-475A-9A63-2B16D22969DF\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/E5B2E2A1-4A87-475A-9A63-2B16D22969DF",
                   "udid" : "E5B2E2A1-4A87-475A-9A63-2B16D22969DF",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-6-40mm",
                   "state" : "Shutdown",
                   "name" : "Apple Watch Series 6 - 40mm"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/03EE6ACB-4A99-4B56-9EF8-67688999F005\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/03EE6ACB-4A99-4B56-9EF8-67688999F005",
                   "udid" : "03EE6ACB-4A99-4B56-9EF8-67688999F005",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-6-44mm",
                   "state" : "Shutdown",
                   "name" : "Apple Watch Series 6 - 44mm"
                 }
               ],
               "com.apple.CoreSimulator.SimRuntime.tvOS-14-5" : [
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/F43798B5-1734-4C4D-972D-67C93AFB4197\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/F43798B5-1734-4C4D-972D-67C93AFB4197",
                   "udid" : "F43798B5-1734-4C4D-972D-67C93AFB4197",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-1080p",
                   "state" : "Shutdown",
                   "name" : "Apple TV"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/7314FC4E-C7D2-484A-BBF5-95A760CB13D4\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/7314FC4E-C7D2-484A-BBF5-95A760CB13D4",
                   "udid" : "7314FC4E-C7D2-484A-BBF5-95A760CB13D4",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-2nd-generation-4K",
                   "state" : "Shutdown",
                   "name" : "Apple TV 4K (2nd generation)"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/2CE3ADD8-6ED7-4BF9-B1CF-5553E8D3140A\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/2CE3ADD8-6ED7-4BF9-B1CF-5553E8D3140A",
                   "udid" : "2CE3ADD8-6ED7-4BF9-B1CF-5553E8D3140A",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-2nd-generation-1080p",
                   "state" : "Shutdown",
                   "name" : "Apple TV 4K (at 1080p) (2nd generation)"
                 }
               ],
               "com.apple.CoreSimulator.SimRuntime.iOS-14-5" : [
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/A9EA16B0-E34F-4326-9383-295FC246B2A2\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/A9EA16B0-E34F-4326-9383-295FC246B2A2",
                   "udid" : "A9EA16B0-E34F-4326-9383-295FC246B2A2",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8",
                   "state" : "Shutdown",
                   "name" : "iPhone 8"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/8D34D76E-6C8C-413E-84B8-BA4C36C49361\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/8D34D76E-6C8C-413E-84B8-BA4C36C49361",
                   "udid" : "8D34D76E-6C8C-413E-84B8-BA4C36C49361",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8-Plus",
                   "state" : "Shutdown",
                   "name" : "iPhone 8 Plus"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/D77C475D-4493-409F-ABD6-6ADD2123D083\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/D77C475D-4493-409F-ABD6-6ADD2123D083",
                   "udid" : "D77C475D-4493-409F-ABD6-6ADD2123D083",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11",
                   "state" : "Shutdown",
                   "name" : "iPhone 11"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/788219FB-E8BE-4743-A076-281C98A9DCD8\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/788219FB-E8BE-4743-A076-281C98A9DCD8",
                   "udid" : "788219FB-E8BE-4743-A076-281C98A9DCD8",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro",
                   "state" : "Shutdown",
                   "name" : "iPhone 11 Pro"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/F6A71E70-ECE9-4732-B456-629F5ADCEBA0\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/F6A71E70-ECE9-4732-B456-629F5ADCEBA0",
                   "udid" : "F6A71E70-ECE9-4732-B456-629F5ADCEBA0",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro-Max",
                   "state" : "Shutdown",
                   "name" : "iPhone 11 Pro Max"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/19E93ABC-AB14-4D2B-A60D-62F94F526622\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/19E93ABC-AB14-4D2B-A60D-62F94F526622",
                   "udid" : "19E93ABC-AB14-4D2B-A60D-62F94F526622",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-SE--2nd-generation-",
                   "state" : "Shutdown",
                   "name" : "iPhone SE (2nd generation)"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/17624B2D-5858-42F5-8134-1E620353E2FE\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/17624B2D-5858-42F5-8134-1E620353E2FE",
                   "udid" : "17624B2D-5858-42F5-8134-1E620353E2FE",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-mini",
                   "state" : "Shutdown",
                   "name" : "iPhone 12 mini"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/96F84C98-40C0-485B-9CD5-051EC470988D\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/96F84C98-40C0-485B-9CD5-051EC470988D",
                   "udid" : "96F84C98-40C0-485B-9CD5-051EC470988D",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12",
                   "state" : "Shutdown",
                   "name" : "iPhone 12"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/0B305905-0CBF-43B7-981C-C3F8703CCDE3\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/0B305905-0CBF-43B7-981C-C3F8703CCDE3",
                   "udid" : "0B305905-0CBF-43B7-981C-C3F8703CCDE3",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro",
                   "state" : "Shutdown",
                   "name" : "iPhone 12 Pro"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/643E0B9A-B850-4A01-AC8B-7504138BBBC5\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/643E0B9A-B850-4A01-AC8B-7504138BBBC5",
                   "udid" : "643E0B9A-B850-4A01-AC8B-7504138BBBC5",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro-Max",
                   "state" : "Shutdown",
                   "name" : "iPhone 12 Pro Max"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/D61C1611-0AAC-4EEF-9CC3-7CF2D95F4CC9\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/D61C1611-0AAC-4EEF-9CC3-7CF2D95F4CC9",
                   "udid" : "D61C1611-0AAC-4EEF-9CC3-7CF2D95F4CC9",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPod-touch--7th-generation-",
                   "state" : "Shutdown",
                   "name" : "iPod touch (7th generation)"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/28490EB0-FAB9-4910-B3F7-9219789617A9\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/28490EB0-FAB9-4910-B3F7-9219789617A9",
                   "udid" : "28490EB0-FAB9-4910-B3F7-9219789617A9",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--9-7-inch-",
                   "state" : "Shutdown",
                   "name" : "iPad Pro (9.7-inch)"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/1FF60674-2F0A-4017-941B-36121E7E1244\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/1FF60674-2F0A-4017-941B-36121E7E1244",
                   "udid" : "1FF60674-2F0A-4017-941B-36121E7E1244",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro-11-inch-3rd-generation",
                   "state" : "Shutdown",
                   "name" : "iPad Pro (11-inch) (3rd generation)"
                 },
                 {
                   "dataPath" :
                   "\/Users\/abir\/Library\/Developer\/CoreSimulator\/Devices\/97C17B56-933F-44D1-AF1A-DA04ECE2BDC4\/data",
                   "logPath" : "\/Users\/abir\/Library\/Logs\/CoreSimulator\/97C17B56-933F-44D1-AF1A-DA04ECE2BDC4",
                   "udid" : "97C17B56-933F-44D1-AF1A-DA04ECE2BDC4",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro-12-9-inch-5th-generation",
                   "state" : "Shutdown",
                   "name" : "iPad Pro (12.9-inch) (5th generation)"
                 }
               ]
             }
           }
[+2897 ms] [
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone10,4",
                        "identifier" : "A9EA16B0-E34F-4326-9383-295FC246B2A2",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-8-2",
                        "modelName" : "iPhone 8",
                        "name" : "iPhone 8"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,8",
                        "identifier" : "19E93ABC-AB14-4D2B-A60D-62F94F526622",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-se-1",
                        "modelName" : "iPhone SE (2nd generation)",
                        "name" : "iPhone SE (2nd generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone10,5",
                        "identifier" : "8D34D76E-6C8C-413E-84B8-BA4C36C49361",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-8-plus-2",
                        "modelName" : "iPhone 8 Plus",
                        "name" : "iPhone 8 Plus"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone13,4",
                        "identifier" : "643E0B9A-B850-4A01-AC8B-7504138BBBC5",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-12-pro-max-1",
                        "modelName" : "iPhone 12 Pro Max",
                        "name" : "iPhone 12 Pro Max"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,3",
                        "identifier" : "788219FB-E8BE-4743-A076-281C98A9DCD8",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-11-pro-1",
                        "modelName" : "iPhone 11 Pro",
                        "name" : "iPhone 11 Pro"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone13,3",
                        "identifier" : "0B305905-0CBF-43B7-981C-C3F8703CCDE3",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-12-pro-1",
                        "modelName" : "iPhone 12 Pro",
                        "name" : "iPhone 12 Pro"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad6,4",
                        "identifier" : "28490EB0-FAB9-4910-B3F7-9219789617A9",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-pro-9point7-a1674-b9b7ba",
                        "modelName" : "iPad Pro (9.7-inch)",
                        "name" : "iPad Pro (9.7-inch)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18L191)",
                        "available" : true,
                        "platform" : "com.apple.platform.appletvsimulator",
                        "modelCode" : "AppleTV5,3",
                        "identifier" : "F43798B5-1734-4C4D-972D-67C93AFB4197",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.apple-tv-4",
                        "modelName" : "Apple TV",
                        "name" : "Apple TV"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad13,10",
                        "identifier" : "97C17B56-933F-44D1-AF1A-DA04ECE2BDC4",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-pro-12point9-5th-1",
                        "modelName" : "iPad Pro (12.9-inch) (5th generation)",
                        "name" : "iPad Pro (12.9-inch) (5th generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18L191)",
                        "available" : true,
                        "platform" : "com.apple.platform.appletvsimulator",
                        "modelCode" : "AppleTV11,1",
                        "identifier" : "7314FC4E-C7D2-484A-BBF5-95A760CB13D4",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.apple-tv-4k-2nd",
                        "modelName" : "Apple TV 4K (2nd generation)",
                        "name" : "Apple TV 4K (2nd generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone13,2",
                        "identifier" : "96F84C98-40C0-485B-9CD5-051EC470988D",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-12-1",
                        "modelName" : "iPhone 12",
                        "name" : "iPhone 12"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18L191)",
                        "available" : true,
                        "platform" : "com.apple.platform.appletvsimulator",
                        "modelCode" : "AppleTV11,1",
                        "identifier" : "2CE3ADD8-6ED7-4BF9-B1CF-5553E8D3140A",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.apple-tv-4k-2nd",
                        "modelName" : "Apple TV 4K (at 1080p) (2nd generation)",
                        "name" : "Apple TV 4K (at 1080p) (2nd generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad13,5",
                        "identifier" : "1FF60674-2F0A-4017-941B-36121E7E1244",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-pro-11-3rd-1",
                        "modelName" : "iPad Pro (11-inch) (3rd generation)",
                        "name" : "iPad Pro (11-inch) (3rd generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone13,1",
                        "identifier" : "17624B2D-5858-42F5-8134-1E620353E2FE",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-12-mini-1",
                        "modelName" : "iPhone 12 mini",
                        "name" : "iPhone 12 mini"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "7.4 (18T187)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch6,2",
                        "identifier" : "03EE6ACB-4A99-4B56-9EF8-67688999F005",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.watch-series6-1",
                        "modelName" : "Apple Watch Series 6 - 44mm",
                        "name" : "Apple Watch Series 6 - 44mm"
                      },
                      {
                        "modelCode" : "iPad4,2",
                        "simulator" : false,
                        "modelName" : "iPad Air (Model A1475)",
                        "error" : {
                          "code" : -13,
                          "failureReason" : "",
                          "underlyingErrors" : [
                            {
                              "code" : 3,
                              "failureReason" : "",
                              "description" : "Abir’s iPad is locked.",
                              "recoverySuggestion" : "To use Abir’s iPad with Xcode, unlock it.",
                              "domain" : "DVTDeviceIneligibilityErrorDomain"
                            }
                          ],
                          "description" : "Abir’s iPad is not connected",
                          "recoverySuggestion" : "Xcode will continue when Abir’s iPad is connected.",
                          "domain" : "com.apple.platform.iphoneos"
                        },
                        "operatingSystemVersion" : "12.5.2 (16H30)",
                        "identifier" : "aece3fd142ba4ea9996ddc1ab719ced4e6dd72e4",
                        "platform" : "com.apple.platform.iphoneos",
                        "architecture" : "arm64",
                        "interface" : "usb",
                        "available" : false,
                        "name" : "Abir’s iPad",
                        "modelUTI" : "com.apple.ipad-air-a1475-99989b"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "7.4 (18T187)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch5,4",
                        "identifier" : "E2AD18E5-46BE-47A7-AB41-7B40F203BD43",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.watch-series5-1",
                        "modelName" : "Apple Watch Series 5 - 44mm",
                        "name" : "Apple Watch Series 5 - 44mm"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPod9,1",
                        "identifier" : "D61C1611-0AAC-4EEF-9CC3-7CF2D95F4CC9",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipod-touch-7-2",
                        "modelName" : "iPod touch (7th generation)",
                        "name" : "iPod touch (7th generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "7.4 (18T187)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch5,3",
                        "identifier" : "724AC345-485C-4624-86D5-749D3B825B96",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.watch-series5-1",
                        "modelName" : "Apple Watch Series 5 - 40mm",
                        "name" : "Apple Watch Series 5 - 40mm"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,5",
                        "identifier" : "F6A71E70-ECE9-4732-B456-629F5ADCEBA0",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-11-pro-max-1",
                        "modelName" : "iPhone 11 Pro Max",
                        "name" : "iPhone 11 Pro Max"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "14.5 (18E182)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,1",
                        "identifier" : "D77C475D-4493-409F-ABD6-6ADD2123D083",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-11-1",
                        "modelName" : "iPhone 11",
                        "name" : "iPhone 11"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "7.4 (18T187)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch6,1",
                        "identifier" : "E5B2E2A1-4A87-475A-9A63-2B16D22969DF",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.watch-series6-1",
                        "modelName" : "Apple Watch Series 6 - 40mm",
                        "name" : "Apple Watch Series 6 - 40mm"
                      }
                    ]
[   +7 ms] Error: Abir’s iPad is not connected. Xcode will continue when Abir’s iPad is connected. (code -13)
[   +4 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +4 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +88 ms] Skipping pub get: version match.
[ +128 ms] Generating
/Users/abir/Documents/myresume/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[ +165 ms] Launching lib/main.dart on Chrome in debug mode...
[ +127 ms] Updating assets
[  +93 ms] Waiting for connection from debug service on Chrome...
[ +105 ms] <- reset
[   +7 ms] /usr/local/Caskroom/flutter/2.0.2/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev
/usr/local/Caskroom/flutter/2.0.2/flutter/bin/cache/artifacts/engine/darwin-x64/frontend_server.dart.snapshot --sdk-root
/usr/local/Caskroom/flutter/2.0.2/flutter/bin/cache/flutter_web_sdk/ --incremental --target=dartdevc
--debugger-module-names --experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=true --output-dill
/var/folders/27/0lgprgpd3b52nr55y9txwj7m0000gn/T/flutter_tools.RAz0WQ/flutter_tool.ynFxkD/app.dill --libraries-spec
file:///usr/local/Caskroom/flutter/2.0.2/flutter/bin/cache/flutter_web_sdk/libraries.json --packages
/Users/abir/Documents/myresume/.dart_tool/package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false
--enable-asserts --track-widget-creation --filesystem-root
/var/folders/27/0lgprgpd3b52nr55y9txwj7m0000gn/T/flutter_tools.RAz0WQ/flutter_tools.3UTCYW --filesystem-scheme
org-dartlang-app --initialize-from-dill build/b1b715402d823b7fd5c2b68d2edcb2ce.cache.dill.track.dill --platform
file:///usr/local/Caskroom/flutter/2.0.2/flutter/bin/cache/flutter_web_sdk/kernel/flutter_ddc_sdk_sound.dill
--sound-null-safety
[  +10 ms] <- compile org-dartlang-app:/web_entrypoint.dart
[+16063 ms] Waiting for connection from debug service on Chrome... (completed in 16.2s)
[        ] Synced 28.3MB.
[        ] <- accept
[        ] Caching compiled dill
[ +212 ms] Using Google Chrome 89.0.4389.114

[+3182 ms] [CHROME]:
[   +1 ms] [CHROME]:DevTools listening on ws://<IP_ADDRESS>:51889/devtools/browser/e827e59e-718b-4f57-81e6-ff28025faa3a
[+1008 ms] DwdsInjector: Received request for entrypoint at http://localhost:51821/main_module.bootstrap.js
[   +5 ms] MetadataProvider: Loading debug metadata...
[  +13 ms] MetadataProvider: Loaded debug metadata (sound null safety)
[   +7 ms] DwdsInjector: Injected debugging metadata for entrypoint at http://localhost:51821/main_module.bootstrap.js
[+1651 ms] ChromeProxyService: Initializing expression compiler for main_module.bootstrap.js with sound null safety: true
[  +76 ms] DevHandler: Debug service listening on ws://<IP_ADDRESS>:51908/ZmXULHEQOuQ=/ws

[  +27 ms] This app is linked to the debug service: ws://<IP_ADDRESS>:51908/ZmXULHEQOuQ=/ws
[   +9 ms] Debug service listening on ws://<IP_ADDRESS>:51908/ZmXULHEQOuQ=/ws
[        ] 💪 Running with sound null safety 💪
[   +3 ms] 🔥  To hot restart changes while running, press "r" or "R".
[        ] For a more detailed help message, press "h". To quit, press "q".

my flutter analyze output here
abir@Abirs-MacBook-Pro myresume % flutter analyze
Analyzing myresume...
No issues found! (ran in 1.7s)
abir@Abirs-MacBook-Pro myresume %

my  flutter doctor -v output here
abir@Abirs-MacBook-Pro myresume % flutter doctor -v
[✓] Flutter (Channel stable, 2.2.1, on macOS 11.4 20F71 darwin-x64, locale en-BD)
    • Flutter version 2.2.1 at /usr/local/Caskroom/flutter/2.0.2/flutter
    • Framework revision 02c026b03c (9 days ago), 2021-05-27 12:24:44 -0700
    • Engine revision 0fdb562ac8
    • Dart version 2.13.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/abir/Library/Android/sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.5, Build version 12E262
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] VS Code (version 1.56.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.23.0

[✓] Connected device (1 available)
    • Chrome (web) • chrome • web-javascript • Google Chrome 89.0.4389.114
    ! Error: Abir’s iPad is not connected. Xcode will continue when Abir’s iPad is connected. (code -13)

• No issues found!

Hi @AbirAhsan
It's probably an issue on your host, can you create a new project host on Netlify, it's just drag and drop
A new project is fine when hosting on Netlify
tahatesser@Tahas-MBP stable_flutter % fsp
Running "flutter pub get" in stable_flutter...                     553ms
tahatesser@Tahas-MBP stable_flutter % fs build  web --release

💪 Building with sound null safety 💪

Compiling lib/main.dart for the Web...                             21.7s
tahatesser@Tahas-MBP stable_flutter %

https://dreamy-sinoussi-97895d.netlify.app/#/

flutter doctor -v
[✓] Flutter (Channel stable, 2.2.1, on macOS 11.4 20F71 darwin-x64, locale
    en-GB)
    • Flutter version 2.2.1 at /Users/tahatesser/Code/flutter_stable
    • Framework revision 02c026b03c (11 days ago), 2021-05-27 12:24:44 -0700
    • Engine revision 0fdb562ac8
    • Dart version 2.13.1

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.5, Build version 12E262
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.8+10-b944.6916264)

[✓] VS Code (version 1.56.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.23.0

[✓] Connected device (4 available)
    • Taha’s iPhone (mobile)     • e534bcc711c9a011aa892eb51cdb60f40b3acddb •
      ios            • iOS 12.5.2
    • iPhone 12 Pro Max (mobile) • 516FAD15-C23C-4952-943C-0612DAAC1643     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • macOS 11.4 20F71 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 91.0.4472.77

• No issues found!

thanks @TahaTesser ❤
Before I host it by drag and drop that's why it Can't access to assets, font folder.
Today I upload the zip file and extract it. It's now working fine.


Improve error wrapping

I would like to recommend you put a comment stating what closed the issue, whether it's a commit PR etc. As always, thank you for the project, looking forward to using it.

You where a little bit faster then me ;) superseded by #50

I'm not sure if we're talking about the same thing?

No, you're absolutely right. Closing issues should always come with a comment. What I tried to say was I redefined the issue and created a new one for it, but something disrupted me and I forgot to do it.

superseded by #50

Oh right glad we're on the same page. Thank you again.


Remove seeding-generation tests with NPEs

I've noticed that the majority of the generated tests for xwiki-commons-xml are about setting some values that lead to an NPE and the test verifies that the NPE is thrown.
There are 2 problems with this:

On XWiki we don't have the practice of checking for null values for all parameters. We check for null at system boundary.
It generates a test that doesn't make sense for us and at best is a wrong test since throwing a NPE is never a good thing ;)

Is it possible to disable generating this type of tests?

Hi @vmassol,
There is no precise way to avoid NPE capturing by generated tests. However, EvoSuite uses eight different criteria for test generation by default. One of them is Exception criteria, which capture all of the exceptions. You can run EvoSuite without this criterion by adding this parameter:
-Dcriterion=BRANCH:LINE:WEAKMUTATION:OUTPUT:METHOD:METHODNOEXCEPTION:CBRANCH

Note: I think capturing exception is useful in several cases.

Yes, but unfortunately, in EvoSuite, you can not capture only one specific type of exception.


Feature: Mark as removed

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@a792b94). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop      #44   +/-   ##
==========================================
  Coverage           ?   14.69%
==========================================
  Files              ?        4
  Lines              ?      313
  Branches           ?       98
==========================================
  Hits               ?       46
  Misses             ?      210
  Partials           ?       57

Flag
Coverage Δ

unittest
14.69% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out 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 a792b94...ab4cf6b. Read the comment docs.

@Kronos66 is this still Draft?


Allow plugin to use X.509 client authentication

This introduces three new environment variables:

XRD_PELICANX509AUTHPREFIXESFILE: Location of a file specifying the prefixes to use with X.509 authentication.
XRD_PELICANCLIENTCERTFILE: Location of the X.509 client certificate to use.
XRD_PELICANCLIENTCERTKEY: Location of the X.509 client key to use.

When set, the XRD_PELICANX509AUTHPREFIXESFILE is periodically parsed for prefixes (one prefix per line).  If an incoming URL matches the prefix, then the connection to the origin will use the specified client certificate for authentication.

Marking as a draft; I want to also enable this behavior based on the presence of a header (X-Osdf-X509) in the director response.

Yes - this sounds like a good test for the PR.
Two notes:

I'm not quite sure what's up with your hash issue; however, pulling the hash from the logs was one other approach I was going to suggest.
I have a separate PR that also updates the C++ standard to 20.  In my dev environment, I get a warning, not a failure.  For simplicity, please just add a one-line commit changing the standard when merging.


Feature request: PR changes via comment from a comment

Thanks for open-sourcing PR-agent! 🙌
It appears that this would either be an extension of the /improve command or a separate complimentary command, but my ideal workflow would be to have PR-agent enabled on certain repos where I could ask for several high level tasks to be performed on my branch as a follow up commit.
Example requests:

Delete the third image in my blog post
Rewrite the final paragraph for clarity on X, Y, Z
Rewrite function X using the async/await or try/catch patterns
etc

Ideally, PR-agent would then check out my latest code, load it into context somehow and make my requested changes as a follow up commit that I could review.
It might also make sense to have /revert commands in this workflow.
If I had this, I could close the mobile editing loop on my blog, which uses Vercel and thereby creates preview environments for each commit.

Hi @zackproser
Thanks for the insightful suggestion. However, i believe it is out-of-scope for PR-Agent project, which deals with Pull Requests code change (PR).
Doing general code changes to a big repo, from a simplistic command (rewrite function ...) is a gigantic task. Currently, from my tests and experiments, solutions that are tailored exactly to do that are doing a mediocre job, at best. i personally tested sweepAI, and found it unreliable. For any non-trivial change, they usually fail, and in general, I found no 'energetic gain' from working with those complicated (and expensive) tools.
In the scope of PR-Agent, implementing user commands that are related specifically to the code change in the PR might be possible. For example - 'add docstring to the new function that was added in the PR', sound reasonable, and can offer more reliable results.

Hi @zackproser
Thanks for the insightful suggestion. However, i believe it is out-of-scope for PR-Agent project, which deals with Pull Requests code change (PR).
Doing general code changes to a big repo, from a simplistic command (rewrite function ...) is a gigantic task. Currently, from my tests and experiments, solutions that are tailored exactly to do that are doing a mediocre job, at best. i personally tested sweepAI, and found it unreliable. For any non-trivial change, they usually fail, and in general, I found no 'energetic gain' from working with those complicated (and expensive) tools.
In the scope of PR-Agent, implementing user commands that are related specifically to the code change in the PR might be possible. For example - 'add docstring to the new function that was added in the PR', sound reasonable, and can offer more reliable results.

Roger - thanks for your thoughtful reply - what you say makes sense to me. For my current use case, I believe updates scoped solely to the changes in the current PR would work.

👍


When .git is removed from Terminal, it isn't reflected in the sidebar Files Panel & Git Panel

VSCode Version: 1.24.1
OS Version: Mac OS 10.13.5

Steps to Reproduce:

Clone a git repo
Edit some files to see some git diffs in Git Panel
Launch Terminal inside VSCode & then remove .git folder
You will still see Git diffs in side panel

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

Oh yeah... this has broken since a while...

Still seeing the diffs until I reload the window

Created https://github.com/Microsoft/vscode/issues/55729

@chrmarti I can't repro that, still works for me when there are no commits. Can you double check?

As a movie:

It doesn't react if you wait ~10 seconds?

No, although I have seen it update, but only 1 out of 4 times or so.

Yup, I could reproduce what you see @chrmarti. Unfortunately, what happens is the git extension doesn't get file events, for which @bpasero probably already has an issue for. If the file events do reach the git extension, then the UI behaves correctly. Closing this.

@chrmarti to verify that behaviour can you run "code --verbose" and see the output for the file watchers?

@bpasero I ran it out of dev and console.log file events as they came from the watcher API. When the bug didn't repro, I was getting events. When the bug repros, no events were coming.

The output from --verbose from right before I initialize the repository to right after I rm -rf .git and waited for 10+ seconds: 53520.txt

@chrmarti you will have to copy it out of devtools, the terminal output misses all the info

(I fixed that in https://github.com/Microsoft/vscode/commit/25558ca524e62b782014e5ef97438474cc32f42e so it should work now if running out of sources)

Here you go: 53520-console.log

Yes, not always (as before), but it repros. (Also just tried running out-of-source.)

@joaomoreno I can reproduce:

open folder without git repo
initialize
remove .git folder from integrated terminal

The extension host is seeing the file event, so it must be a bug in the extension:


fix(resolve): fix resolver not following node resolve algorithm

(fix #2695)

Description
Fixing resolver trying to postfix every file extension to path before trying to resolve to non-posfixed direct match.
Removed the ability to resolve to directory path while not in package.json and index resolution step.
Added 2 test that previous implementation would fail.
Additional context

What is the purpose of this pull request?

[X] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the Commit Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[X] Ideally, include relevant tests that fail without this PR but pass with it.

Note: this PR fixes edge cases (included in the tests) and improves performance when the project is using extensions in their imports. Before this PR, for the default config, 7 tryResolveFile would be called before trying for the exact match. With this PR, that 7 tryResolveFile are avoided.


Installer add offline installation mode

Add offline mode installation, with MobiflightConnector last release zip has Embedded ressource. If no ressource are available the offline mode is disable and hide.

I am close to wrapping MobiFlight with a Standard Installer like NSIS or InnoSetup.
Thank you so much for all the effort that went into this. Please know that I appreciate that a lot and feel bad, that I didnt merge this pull request.


Loading a material on a 3D MeshRenderer model confuses rendering

axmol version: Latest
devices test on: Linux
developing environments: Linux

cmake version: 3.25.2
Steps to Reproduce:

When you setMaterial() on a 3D mesh, its rendering is tweaked and animations do not work.
We've modified the basic HelloWorldScene to demonstrate.
It loads a model "orc.c3t" (from the ccptests), gives it a plain texture, ("Yellow.png" - a 16x16 solid yellow image which just colors the orc entirely yellow), and starts an animation.  This draws and animates the orc correctly.
It also loads a second "orc.c3t" model and gives it a simple material, "orc.material", that uses the most minimal shader you can do (just paint every pixel white, see "orc.vert" and "orc.frag").  It does not draw the orc correctly and it does not animate.
Using setPosition(), setRotation(), and setScale(), you can move the second orc around.  It seems like no transforms are being applied to the meshes, bones, or whatever make up the second orc.
I bundled everything into a zip file. issue.zip
Maybe there is a misunderstanding on how materials are supposed to work.  In any case, hopefully someone is still working on this engine that can take a look!

Hi!  Just following up on this issue.  If you're not interested in reproducing this with the code I provided, can you point to an example of where you set a material (via setMaterial() not setTexture())  on a 3D mesh and have it animate properly.
Thanks!

The material seems incorrect for draw 3d mesh

What does that mean?  Can you point me to a material for a 3d mesh that uses a shader that is "correct" and animates?

To create your own material for your objects look pls these shaders as reference:
axmol-dir\cocos2d\core\renderer\shaders\3D_positionNormalTexture.vert
axmol-dir\cocos2d\core\renderer\shaders\3D_colorNormalTexture.frag

or
axmol-dir\cocos2d\tests\cpp-tests\Resources\Shaders3D\3d_position_skin_tex.vert (no normal attribute)
axmol-dir\cocos2d\tests\cpp-tests\Resources\Shaders3D\3d_color_tex.frag

or other combinations.

Okay, I see what I need to do now.  The getPosition() in the vertex shader was the key.  Thanks!


performance improvements

consider:

[ ] use apache to serve php authenticated files https://stackoverflow.com/questions/10596116/caching-http-responses-when-they-are-dynamically-created-by-php/10596231#10596231

no problem at the moment


[Bug] LogStoreTableFactory should not implements DynamicTableFactory

Search before asking

[X] I searched in the issues and found nothing similar.

Paimon version
0.4
Compute Engine
flink
Minimal reproduce step
kafka connector sink to paimon table
What doesn't meet your expectations?
Now, KafkaLogStoreFactory is very easy to conflict with flink kafka connector.
we should not use flink DynamicTableFactory.
Anything else?
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@JingsongLi  Do you mean when we use kafka connector in the job, it will find LogStoreTableFactory as kafka connector?

@Alibaba-HZY, welcome to contribute. Please go ahead to fix the bug.

The https://github.com/apache/incubator-paimon/pull/729 is valid.
But we need to go ahead and complete the issue.
The core reason is that if there is no kafka jar in flink/lib, the kafka identifier will find KafkaLogStoreFactory in paimon, and throw KafkaLogStoreFactory is not a DynamicTableSourceFactory exception, which is very confused.

The #729 is valid. But we need to go ahead and complete the issue. The core reason is that if there is no kafka jar in flink/lib, the kafka identifier will find KafkaLogStoreFactory in paimon, and throw KafkaLogStoreFactory is not a DynamicTableSourceFactory exception, which is very confused.

ok i know i will remove DynamicTableFactory in LogStoreTableFactory


Avoid warnings in the cabac code

Use int32_t for a parameter that is always 0 or 1, because it is
negated. This fixes "warning C4146: unary minus operator applied
to unsigned type, result still unsigned" in MSVC.
Also add casts to silence MSVC warnings about "conversion from
'WelsEnc::cabac_low_t' to 'uint8_t', possible loss of data".
The generated code still is identical to before, on both gcc
and clang.
@saamas - does it seem ok to you?

+1 lgtm.


[DOCS] Getting Started instructions are broken (Bad rustc version)

Attempting to run the commands on the Getting Started page:
rustup install nightly-2023-05-28
cargo +nightly-2023-05-28 install --git https://github.com/facebook/buck2.git buck2

I see the following error:
error: failed to run custom build command for `buck2_core v0.1.0 (/home/wagray/.cargo/git/checkouts/buck2-881d6af740402932/5c69d8e/app/buck2_core)`

Caused by:
  process didn't exit successfully: `/tmp/cargo-installh0BlOm/release/build/buck2_core-9383ed164b222151/build-script-build` (exit status: 101)
  --- stderr
  thread 'main' panicked at 'buck2 only works with version `rustc 1.72.0-nightly (36fb58e43 2023-06-26)` of rustc, but you are using `rustc 1.71.0-nightly (cca7ee581 2023-05-27)`. Correct version is installed automatically when `rustup` is used', app/buck2_core/build.rs:43:9
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Worse, attempting to install using 2023-06-26 fails, because the latest update on that channel is rust version 1.72.0-nightly (8084f397c 2023-06-25), which still triggers the failure

@yeswalrus For the time being, this is how I got this to work.
Source: https://github.com/facebook/buck2/blob/main/HACKING.md
git clone https://github.com/facebook/buck2.git
cd buck2/
cargo install --path=app/buck2

Try cargo install the nightly day after the day that appears when compilation fails (2023-06-27). Had this issue yesterday, seems to install the nightly of the day before (so has installed 2023-06-25 for you)

nightly-2023-07-10 is the right answer and what we have in our https://github.com/facebook/buck2/blob/main/rust-toolchain file. Alas, you have to have that on the command line to for Cargo to get it right. Let me update the docs.

Fixed in 4e5e76998a3cb0636e415b047798dfdc1ac56c05 and docs regenerated. I've also got a patch pending to write down in rust-toolchain what needs to be done, to encourage it not to be forgotten next time.


Model converted to TFlite performs slow during inference

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 18.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): Source
TensorFlow version (use command below): 2.5.0
Python version: 3.6.9
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory: No

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
Tensorflow saved model converted to TFlite model gives poor performance during inference. The inference time is same as (or greater than in some cases) tensorflow model
Describe the expected behavior
Inference time should be low according to the documentation
Contributing - Do you
want to contribute a PR? (yes/no): - Briefly describe your candidate solution
(if contributing): Yes
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
https://colab.research.google.com/drive/16IAyeNAIdfgRrS1CLhOqBrAc0bvFNt5A?usp=sharing

@rohanshingade ,
I do not have access to the link you have provided. Could you please provide the required permissions to view the files.

@tilakrayal updated.
https://colab.research.google.com/drive/16IAyeNAIdfgRrS1CLhOqBrAc0bvFNt5A?usp=sharing

Hi, it seems you're benchmarking on workstations, TFLite is not well optimized for x86 comparing to Tensorflow.

Hi, it seems you're benchmarking on workstations, TFLite is not well optimized for x86 comparing to Tensorflow.

We have done optimizations for x86, but they are not likely enabled (probably due to the OS+compiler used when building the tflite distribution). I guess this is why you see slow inference in the colab environment.
Could you build your own tflite distribution on your workstation and benchmark the model performance? You could use either bazel or cmake (guide) to achieve this.

when using bazel, pls explicitly add "-c opt --define=tflite_with_ruy=true --define=tflite_with_xnnpack=true"
when using cmake, pls turn on TFLITE_ENABLE_RUY option as described here

@multiverse-tf i tried what you suggested but there was no improvement in performance
Inference time for
Out of the box model: 59 seconds
TF model convert to Tflite model: 21 mins

Was able to replicate the issue with TF 2.6.0-dev20210606,please find the gist here ..Thanks !

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The TFLite team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the TFLite space.
Thanks.


MM-27352: add ldap certificate support

Summary
Implements Actions for uploading and removing private key files and public certificate files for LDAP providers
Ticket Link
https://mattermost.atlassian.net/browse/MM-27352
Related PR
https://github.com/mattermost/mattermost-webapp/pull/6345
https://github.com/mattermost/mattermost-server/pull/15361
https://github.com/mattermost/enterprise/pull/752

I like leaving a bunch of code on the cutting room floor.  Thank you.

/update-branch


Implement Sql Support [API-1205]

Implementation of Sql support.
supersedes #971

Windows test FAILed.

Linux test FAILed.

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test FAILed.

Windows test FAILed.

Linux test FAILed.

Linux test FAILed.

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Linux test FAILed.

verify

Linux test FAILed.

Linux test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test FAILed.

Windows test FAILed.

Windows test FAILed.

verify

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Linux test PASSed.

Windows test FAILed.

Linux test PASSed.

Windows test FAILed.

Linux test PASSed.

verify-windows

Windows test FAILed.

Windows test PASSed.

Linux test PASSed.

Windows test PASSed.

Linux test FAILed.

verify-linux

Linux test PASSed.

Windows test PASSed.

Linux test PASSed.

Windows test FAILed.

Linux test PASSed.

Windows test FAILed.

Windows test PASSed.

Linux test PASSed.

Linux test PASSed.

Windows test FAILed.

Linux test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test FAILed.

Linux test PASSed.

Windows test PASSed.

Windows test FAILed.

Windows test FAILed.

Linux test PASSed.

Windows test FAILed.

Linux test FAILed.

Linux test FAILed.

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Linux test PASSed.

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test PASSed.

Linux test PASSed.

Windows test PASSed.

Linux test PASSed.

Windows test PASSed.

Linux test PASSed.

Linux test FAILed.

Windows test FAILed.

@ihsandemir When I compile the project with the code in this PR I get the following error if I enable examples:
https://gist.github.com/yuce/73f4f06b20942d6dd4e12f2c2c7a2b8e

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test PASSed.

Linux test PASSed.

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test FAILed.

Windows test FAILed.

Linux test PASSed.

Linux test PASSed.

Windows test PASSed.

Linux test PASSed.


Consider a way to specify arguments as an argument as opposed to the parameter-chain object.

This works better with constructors: my_type{my_ns::names().x(10).y(20)}.
Some ideas:

Allow passing a nickel::name_group with chained parameters.
Perhaps a further wrapper over the nickel::name_group to make it something distinct.

Compare to: Boost Graph

For now, this won't be worked on. There needs to be more use of the current form in order to get a good idea on how it feels.


For connected  ble device at bluetooth setting

when device connected at ios bt setting,
can not receive  connected ble  device by babyBlutooth?

of couse can receive delegate for babyBluetooth , you can read wiki about how to uesd , and how  use block on babybluetooth particularly


Accessing stores

Hello,
I was wondering if you know of a way to use the same store from 2 different components?
Thank you!

Components just reference stores from js files. There should be no trouble accessing the same store from several components. Both components just need to import the same thing.
import { commonStore } from "./stores.js"


Unselect Item after some operation when clicked

Is there in any way to disable the selection on an item?
Here is what I need:
I click on a timeline-item. The item have a onClick function attached to it. The onClick function renders a modal. I do my stuff in the modal and finishes. When the modal is gone, the item is unselected and I can click on a different item, or the same to fire the onClick again.
Here is what I got:
When I click on a item, i'ts fine. It fires the onClick function and opens my modal. When i come back from my modal, I need to "unselect" by clicking on a blank spot in the timeline in order to select that item again.
Reproducible test case: https://codesandbox.io/s/qlj6qvjrnw
(just click on an item: it gets yellow. To unselect, click outside)
Any help is appriciated.

I think you could achieve this by manually controlling the selected prop and not have the timeline do it for you. Adding the current itemId to the selected array then removing it on the modal close event

@b5imply does @vasdee 's tip help you out?

I've tested this out, and it worked. I had to define selected as an empty array, have the same eventHandler method on "onItemClick" and "onItemSelect" in order to make this work. It is a hack to an existing solution tho.
Including solution:
https://codesandbox.io/s/7y0w1wmwrq


Add experimental.useAtlasEngine to schema

does what it says on the can.

[x] closes #12302

@lhecker give 'em a second.

lol that typo is gold

@msftbot merge this in 1 minute


Imported groups

Once a group is synced for an app. What is the sync intervals afterwards? How often are group in CAS updated for changes made to the group in AAD?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fb8d5c18-3f84-f47a-7320-930cbd4ae5a0
Version Independent ID: aa593032-c7c0-5814-5b18-d360295a260e
Content: Import user groups from connected apps
Content Source: CloudAppSecurityDocs/user-groups.md
Service: cloud-app-security
GitHub Login: @rkarlin
Microsoft Alias: rkarlin

Hi @xNiklasJern , thanks for reaching out. After the initial sync it's updated every hour. I'll add it to the documentation. thanks!

#please-close


to/from_u64: explicitly convert to little-endian

Someone might send these across the network... to an IBM System/390 or a spacecraft running LEON. Will that literally ever happen? probably not. But now the byte order won't get messed up!

I'm not entirely convinced a changelog entry for this is necessary since the feature wasn't released and (within a rounding error) it affects 0% of deployments

Wait i'm not sure this is necessary at all

yeah if you're sending this over the net you would want to change the endianness of the whole u64


hide the .bsky from profile, feed and posted mesages

The username will be clearer and friendlier without breaking the link
https://github.com/user-attachments/assets/c298dc97-9cb0-4df1-8696-b856ddbabe60

This would cause significant impersonation problems. Consider a handle that was official.gov.bsky.mydomain.tld, it'd show up as official.gov!

The .bsky.social part is intentional... to prevent impersonation..

Even disregarding the impersonation issues brought up, it's not a good idea to just hide .bsky.social. If this idea were to be considered, it should hide the (default) extension of whatever server the user is on, not just .bsky.social.

In addition to the issues already pointed out by others, if this is ever implemented, it should, by all means, be configurable with a setting, probably disabled by default. There must also be an easy way to see what the actual handle is, regardless of the setting.

In Skeets (@skeetsapp.com) I have made this optional (configurable in Settings) and it only works with .bsky.social handles. All non-bsky handles are always displayed in full length.

I don't think this is a good idea for the main app. It's already moderately difficult to understand the structure of handles for new users, and this would only make it more complicated and make it easier to fall for impersonation, even if it is an optional setting.

I understand better now. Thanks guys.

bsky.social is not the only PDS that exists, just because it is the premiere default PDS does not mean it's allowed to get special treatment

@mary-ext I mentioned this in a previous comment.

Even disregarding the impersonation issues brought up, it's not a good idea to just hide .bsky.social. If this idea were to be considered, it should hide the (default) extension of whatever server the user is on, not just .bsky.social.

@mary-ext I mentioned this in a previous comment.

Even disregarding the impersonation issues brought up, it's not a good idea to just hide .bsky.social. If this idea were to be considered, it should hide the (default) extension of whatever server the user is on, not just .bsky.social.

Even that doesn't seem like a great idea to me, handles are intentionally independent from the server you're on.

Each server has a default handle extension though


Allow use of same physics collision handler for multiple types

It is common to have the same code to be run for similar types. E.g. bullet and one of the enemy types

fixed


Main branch cannot commit

Due to not testing the renovate PRs, main currently cannot commit because it cannot execute the pre-commit hooks.

See https://github.com/typicode/husky/releases/tag/v5.0.0

Fixed in 74fc9ee8dc229e8aa8cf3b663286010ae95134db


Security vulnerability - CVE-2023-2253 - github.com/docker/distribution

Hi Team,
Can you please fix the following security vulnerability?
Vulnerability: A flaw was found in the /v2/_catalog endpoint in distribution/distribution, which accepts a parameter to control the maximum number of records returned (query string: n). This vulnerability allows a malicious user to submit an unreasonably large value for n, causing the allocation of a massive string array, possibly causing a denial of service through excessive use of memory.
Found in dependency: github.com/docker/distribution
Current version: v2.7.1
Security vulnerability fixed in version: 2.8.2-beta.1
Thanks,
Vishweshwar

While updating probably would do no harm, it is a false positive: that advisory only affects the registry service (i.e., when running a registry), not the library code that's used in this project;
The fix for that issue was in the registry/handlers/catalog.go file;
https://github.com/distribution/distribution/commit/521ea3d973cb0c7089ebbcdd4ccadc34be941f54#diff-db61d61258e5f8fca5d2eeaaa101b01a30b404ea18979c4b4a8ff90e82de09e2R51
And that code is not used by the code in this repository;
https://github.com/notaryproject/notary/tree/006963f1ded582c2cc5f5eb4d48dc6089ce3229b/vendor/github.com/docker/distribution/registry

If you use govulncheck (which is aware of code that's used), it won't show that vulnerability; that said, there's an older vulnerability that is detected
govulncheck ./...
govulncheck is an experimental tool. Share feedback at https://go.dev/s/govulncheck-feedback.

Using go1.20.5 and<EMAIL_ADDRESS>with
vulnerability data from https://vuln.go.dev (last modified 2023-06-22 16:44:55 +0000 UTC).

Scanning your code and 350 packages across 53 dependent modules for known vulnerabilities...
Your code is affected by 1 vulnerability from 1 module.

Vulnerability #1: GO-2023-1571
  A maliciously crafted HTTP/2 stream could cause excessive CPU
  consumption in the HPACK decoder, sufficient to cause a denial
  of service from a small number of small requests.

  More info: https://pkg.go.dev/vuln/GO-2023-1571

  Module: golang.org/x/net
    Found in<EMAIL_ADDRESS>    Fixed in<EMAIL_ADDRESS>
    Call stacks in your code:
      cmd/escrow/config.go:21:26: github.com/theupdateframework/notary/cmd/escrow.parseConfig calls github.com/spf13/viper.Viper.ReadInConfig, which eventually calls golang.org/x/net/http2.ErrCode.String
      cmd/escrow/config.go:21:26: github.com/theupdateframework/notary/cmd/escrow.parseConfig calls github.com/spf13/viper.Viper.ReadInConfig, which eventually calls golang.org/x/net/http2.FrameHeader.String
      cmd/escrow/config.go:21:26: github.com/theupdateframework/notary/cmd/escrow.parseConfig calls github.com/spf13/viper.Viper.ReadInConfig, which eventually calls golang.org/x/net/http2.FrameType.String
      cmd/escrow/config.go:21:26: github.com/theupdateframework/notary/cmd/escrow.parseConfig calls github.com/spf13/viper.Viper.ReadInConfig, which eventually calls golang.org/x/net/http2.Setting.String
      cmd/escrow/config.go:21:26: github.com/theupdateframework/notary/cmd/escrow.parseConfig calls github.com/spf13/viper.Viper.ReadInConfig, which eventually calls golang.org/x/net/http2.SettingID.String
      cmd/escrow/config.go:21:26: github.com/theupdateframework/notary/cmd/escrow.parseConfig calls github.com/spf13/viper.Viper.ReadInConfig, which eventually calls golang.org/x/net/http2.writeData.String
      cmd/notary-signer/main.go:91:18: github.com/theupdateframework/notary/cmd/notary-signer.main calls google.golang.org/grpc.Server.Serve, which eventually calls golang.org/x/net/http2.Framer.ReadFrame
      cmd/notary-signer/main.go:91:18: github.com/theupdateframework/notary/cmd/notary-signer.main calls google.golang.org/grpc.Server.Serve, which eventually calls golang.org/x/net/http2.Framer.WriteGoAway
      cmd/notary-signer/main.go:91:18: github.com/theupdateframework/notary/cmd/notary-signer.main calls google.golang.org/grpc.Server.Serve, which eventually calls golang.org/x/net/http2.Framer.WritePing
      cmd/notary-signer/main.go:91:18: github.com/theupdateframework/notary/cmd/notary-signer.main calls google.golang.org/grpc.Server.Serve, which eventually calls golang.org/x/net/http2.Framer.WriteSettings
      cmd/notary-signer/main.go:91:18: github.com/theupdateframework/notary/cmd/notary-signer.main calls google.golang.org/grpc.Server.Serve, which eventually calls golang.org/x/net/http2.Framer.WriteSettingsAck
      cmd/notary-signer/main.go:91:18: github.com/theupdateframework/notary/cmd/notary-signer.main calls google.golang.org/grpc.Server.Serve, which eventually calls golang.org/x/net/http2.Framer.WriteWindowUpdate
      cmd/notary-signer/main.go:91:18: github.com/theupdateframework/notary/cmd/notary-signer.main calls google.golang.org/grpc.Server.Serve, which eventually calls golang.org/x/net/http2.SettingsFrame.ForeachSetting
      proto/signer.pb.go:591:40: github.com/theupdateframework/notary/proto.file_proto_signer_proto_rawDescGZIP calls sync.Once.Do, which eventually calls golang.org/x/net/http2.clientStream.writeRequestBody
      server/storage/rethinkdb.go:290:85: github.com/theupdateframework/notary/server/storage.RethinkDB.Delete calls golang.org/x/net/http2.ConnectionError.Error
      server/storage/rethinkdb.go:290:85: github.com/theupdateframework/notary/server/storage.RethinkDB.Delete calls golang.org/x/net/http2.GoAwayError.Error
      server/storage/rethinkdb.go:290:85: github.com/theupdateframework/notary/server/storage.RethinkDB.Delete calls golang.org/x/net/http2.StreamError.Error
      server/storage/rethinkdb.go:290:85: github.com/theupdateframework/notary/server/storage.RethinkDB.Delete calls golang.org/x/net/http2.connError.Error
      storage/httpstore.go:364:2: github.com/theupdateframework/notary/storage.HTTPStore.RotateKey calls golang.org/x/net/http2.gzipReader.Close
      storage/httpstore.go:364:2: github.com/theupdateframework/notary/storage.HTTPStore.RotateKey calls golang.org/x/net/http2.transportResponseBody.Close
      storage/httpstore.go:57:48: github.com/theupdateframework/notary/storage.NetworkError.Error calls github.com/docker/distribution/registry/api/errcode.Errors.Error, which eventually calls golang.org/x/net/http2.duplicatePseudoHeaderError.Error
      storage/httpstore.go:57:48: github.com/theupdateframework/notary/storage.NetworkError.Error calls github.com/docker/distribution/registry/api/errcode.Errors.Error, which eventually calls golang.org/x/net/http2.headerFieldNameError.Error
      storage/httpstore.go:57:48: github.com/theupdateframework/notary/storage.NetworkError.Error calls github.com/docker/distribution/registry/api/errcode.Errors.Error, which eventually calls golang.org/x/net/http2.headerFieldValueError.Error
      storage/httpstore.go:57:48: github.com/theupdateframework/notary/storage.NetworkError.Error calls github.com/docker/distribution/registry/api/errcode.Errors.Error, which eventually calls golang.org/x/net/http2.pseudoHeaderError.Error
      tuf/testutils/interfaces/cryptoservice.go:36:21: github.com/theupdateframework/notary/tuf/testutils/interfaces.EmptyCryptoServiceInterfaceBehaviorTests calls github.com/stretchr/testify/require.EqualValues, which eventually calls golang.org/x/net/http2.chunkWriter.Write
      tuf/testutils/interfaces/cryptoservice.go:36:21: github.com/theupdateframework/notary/tuf/testutils/interfaces.EmptyCryptoServiceInterfaceBehaviorTests calls github.com/stretchr/testify/require.EqualValues, which eventually calls golang.org/x/net/http2.stickyErrWriter.Write
      utils/configuration.go:234:26: github.com/theupdateframework/notary/utils.ParseViper calls github.com/spf13/viper.Viper.ReadInConfig, which eventually calls golang.org/x/net/http2.gzipReader.Read
      utils/configuration.go:234:26: github.com/theupdateframework/notary/utils.ParseViper calls github.com/spf13/viper.Viper.ReadInConfig, which eventually calls golang.org/x/net/http2.transportResponseBody.Read

      storage/httpstore.go:364:2: github.com/theupdateframework/notary/storage.HTTPStore.RotateKey calls golang.org/x/net/http2.transportResponseBody.Close, which eventually calls golang.org/x/net/http2/hpack.Decoder.Write

=== Informational ===

Found 6 vulnerabilities in packages that you import, but there are no call
stacks leading to the use of these vulnerabilities. You may not need to
take any action. See https://pkg.go.dev/golang.org/x/vuln/cmd/govulncheck
for details.

Vulnerability #1: GO-2022-1144
  An attacker can cause excessive memory growth in a Go server
  accepting HTTP/2 requests. HTTP/2 server connections contain a
  cache of HTTP header keys sent by the client. While the total
  number of entries in this cache is capped, an attacker sending
  very large keys can cause the server to allocate approximately
  64 MiB per open connection.
  More info: https://pkg.go.dev/vuln/GO-2022-1144
  Found in<EMAIL_ADDRESS>  Fixed in<EMAIL_ADDRESS>
Vulnerability #2: GO-2022-0969
  HTTP/2 server connections can hang forever waiting for a clean
  shutdown that was preempted by a fatal error. This condition can
  be exploited by a malicious client to cause a denial of service.
  More info: https://pkg.go.dev/vuln/GO-2022-0969
  Found in<EMAIL_ADDRESS>  Fixed in<EMAIL_ADDRESS>
Vulnerability #3: GO-2022-0379
  Systems that rely on digest equivalence for image attestations
  may be vulnerable to type confusion. A maliciously crafted OCI
  Container Image can cause registry clients to parse the same
  image in two different ways without modifying the image's
  digest, invalidating the common pattern of relying on container
  image digests for equivalence. This problem has been addressed
  in newer versions by improving validation in manifest
  unmarshalling.
  More info: https://pkg.go.dev/vuln/GO-2022-0379
  Found in<EMAIL_ADDRESS>  Fixed in<EMAIL_ADDRESS>
Vulnerability #4: GO-2022-0322
  The Prometheus client_golang HTTP server is vulnerable to a
  denial of service attack when handling requests with
  non-standard HTTP methods. In order to be affected, an
  instrumented software must use any of the
  promhttp.InstrumentHandler* middleware except
  `RequestsInFlight`; not filter any specific methods (e.g GET)
  before middleware; pass a metric with a "method" label name to a
  middleware; and not have any firewall/LB/proxy that filters away
  requests with unknown "method".
  More info: https://pkg.go.dev/vuln/GO-2022-0322
  Found in<EMAIL_ADDRESS>  Fixed in<EMAIL_ADDRESS>
Vulnerability #5: GO-2022-0288
  An attacker can cause unbounded memory growth in servers
  accepting HTTP/2 requests.
  More info: https://pkg.go.dev/vuln/GO-2022-0288
  Found in<EMAIL_ADDRESS>  Fixed in<EMAIL_ADDRESS>
Vulnerability #6: GO-2022-0236
  A malicious HTTP server or client can cause the net/http client
  or server to panic. ReadRequest and ReadResponse can hit an
  unrecoverable panic when reading a very large header (over 7MB
  on 64-bit architectures, or over 4MB on 32-bit ones). Transport
  and Client are vulnerable and the program can be made to crash
  by a malicious server. Server is not vulnerable by default, but
  can be if the default max header of 1MB is overridden by setting
  Server.MaxHeaderBytes to a higher value, in which case the
  program can be made to crash by a malicious client. This also
  affects golang.org/x/net/http2/h2c and HeaderValuesContainsToken
  in golang.org/x/net/http/httpguts.
  More info: https://pkg.go.dev/vuln/GO-2022-0236
  Found in<EMAIL_ADDRESS>  Fixed in<EMAIL_ADDRESS>


[distributed] using code from eventing, that got moved there

Signed-off-by: Matthias Wessendorf<EMAIL_ADDRESS>Fixes #398

Proposed Changes

refacting, leveraging the function which has been moved

Release Note

Docs

/assign @travis-minke-sap please take a look

/lgtm