[$500] Chat  - Message not deleted if conversation has attachment message

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

Version Number: 1.4.5-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Navigate to staging.new.expensify.com
Navigate to any conversation
Write message in compose box
Tap the + icon
Add attachment
Tap & hold the attachment
Select delete comment

Expected Result:
Message should get deleted along with the attachment
Actual Result:
Message not deleted if conversation has attachment message. Only the attachment gets deleted
Workaround:
Unknown
Platforms:

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

[ ] Android: Native
[ ] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/3ef734bc-203c-4910-b7a1-4dfa19cf74eb
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01efde378372c4cade
Upwork Job ID:<PHONE_NUMBER>729961472
Last Price Increase: 2023-11-29

Writing a comment and then uploading an attachment creates two comments (ReportActions). I started contributing recently so sorry to ask, but did deleting an attachment also delete its associated comment before? Looking at the ReportAction object, there's nothing that associates the attachment and its comment together.

This is a backend limitation. It sends two separate reportActions for Attachment with comment
{
    "jsonCode": 200,
    "requestID": "82e00b868cd35495-DEL",
    "onyxData": [
        {
            "key": "report_418329938109457",
            "onyxMethod": "merge",
            "value": {
                "lastActorAccountID": 14963109,
                "lastMentionedTime": null,
                "lastMessageText": "test",
                "lastReadTime": "2023-11-30 03:36:16.283",
                "lastVisibleActionCreated": "2023-11-30 03:36:16.283",
                "maxSequenceNumber": 367,
                "reportID": "418329938109457"
            }
        },
        {
            "key": "reportActions_418329938109457",
            "onyxMethod": "merge",
            "shouldNotify": true,
            "value": {
                "3705155588579407203": {
                    "actionName": "ADDCOMMENT",
                    "actorAccountID": 14963109,
                    "automatic": false,
                    "avatar": "https://d1wpcgnaa73g0y.cloudfront.net/90eda3d9992ba8fb9d3f6cc131a24ed9cfa4d152.png",
                    "created": "2023-11-30 03:36:16.283",
                    "isAttachment": false,
                    "lastModified": "2023-11-30 03:36:16.283",
                    "message": [
                        {
                            "html": "test",
                            "isDeletedParentAction": false,
                            "isEdited": false,
                            "reactions": [],
                            "text": "test",
                            "type": "COMMENT",
                            "whisperedTo": []
                        }
                    ],
                    "originalMessage": {
                        "html": "test",
                        "lastModified": "2023-11-30 03:36:16.283"
                    },
                    "person": [
                        {
                            "style": "strong",
                            "text": "Shubham",
                            "type": "TEXT"
                        }
                    ],
                    "previousReportActionID": "3151404058332519266",
                    "reportActionID": "3705155588579407203",
                    "reportActionTimestamp":<PHONE_NUMBER>283,
                    "sequenceNumber": 367,
                    "shouldShow": true,
                    "timestamp":<PHONE_NUMBER>,
                    "whisperedToAccountIDs": []
                }
            }
        },
        {
            "key": "report_418329938109457",
            "onyxMethod": "merge",
            "value": {
                "lastActorAccountID": 14963109,
                "lastMentionedTime": null,
                "lastMessageText": "[Attachment]",
                "lastReadTime": "2023-11-30 03:36:17.933",
                "lastVisibleActionCreated": "2023-11-30 03:36:17.933",
                "maxSequenceNumber": 368,
                "reportID": "418329938109457"
            }
        },
        {
            "key": "reportActions_418329938109457",
            "onyxMethod": "merge",
            "shouldNotify": true,
            "value": {
                "8498923747063287522": {
                    "actionName": "ADDCOMMENT",
                    "actorAccountID": 14963109,
                    "automatic": false,
                    "avatar": "https://d1wpcgnaa73g0y.cloudfront.net/90eda3d9992ba8fb9d3f6cc131a24ed9cfa4d152.png",
                    "created": "2023-11-30 03:36:17.933",
                    "isAttachment": true,
                    "lastModified": "2023-11-30 03:36:17.933",
                    "message": [
                        {
                            "html": "",
                            "isDeletedParentAction": false,
                            "isEdited": false,
                            "reactions": [],
                            "text": "[Attachment]",
                            "type": "COMMENT",
                            "whisperedTo": []
                        }
                    ],
                    "originalMessage": {
                        "html": "",
                        "lastModified": "2023-11-30 03:36:17.933"
                    },
                    "person": [
                        {
                            "style": "strong",
                            "text": "Shubham",
                            "type": "TEXT"
                        }
                    ],
                    "previousReportActionID": "3705155588579407203",
                    "reportActionID": "8498923747063287522",
                    "reportActionTimestamp":<PHONE_NUMBER>933,
                    "sequenceNumber": 368,
                    "shouldShow": true,
                    "timestamp":<PHONE_NUMBER>,
                    "whisperedToAccountIDs": []
                }
            }
        }
    ],
    "previousUpdateID": 45129491,
    "lastUpdateID": 45129542
}

I don't think this is a bug

@zanyrenney I don't think it's a bug too - this is how our app works now: when we type the message and selects the attachment along, these are actually separate messages, so you can delete the attachment separately but also the message text alone. If we want to change this, I guess, we should discuss it internally and possible have a feature request or smth.

Cool, closing as not a bug!


In AWS perspective Solution not getting the all services

in the In AWS perspective service not getting all the services and getting error ,
we need to get all the services selected here in one account. can you resolve this issue

What errors are you seeing? Is it an error in the web browser or somewhere else?

here while the loading the services we are getting the single service and not all the service , is the new version delivered ? or still new version is in progress , please let me know

The new version was release last week and is available here:  https://aws.amazon.com/solutions/implementations/aws-perspective/?did=sl_card&trk=sl_card.

Yes i have seen the version , thanks can i know for the mutliple services how to club or how i can one account diagram for this all services..  let me know

I don't quite follow. What exactly is the problem, can you show a screenshot?

Closing due to inactivity, please feel free to reopen.


[cloud_functions] Firebase Error: (Internal) when calling function from flutter web

Describe the bug
Im trying to call a cloud function which returns Auth User Data but getting an error "Internal". It does not show neither error code nor error details.
To Reproduce
Steps to reproduce the behavior:

Create a function called getUserAuthData and deploy it successfully.
Import cloud_functions package in package.yaml and add everything required in index.html.
call a cloud function:

try {
      final HttpsCallable callable = CloudFunctions.instance.getHttpsCallable(
          functionName: 'getUserAuthData')
        ..timeout = const Duration(seconds: 300);
      dynamic user = await callable.call();
      ...
    } on CloudFunctionsException catch (e) {
      print('caught firebase functions exception');
      print(e);
    } catch (e) {
      print('caught generic exception');
      print(e);
    }
  }

Expected behavior
It supposes to return auth user data instead of caught generic exception (internal)

Hi @linhdogg
can you please provide your flutter doctor -v ,
your flutter run --verbose
your pubspec.yaml,
and a reproducible minimal code sample.
Thank you

Hi @iapicca
this is flutter doctor -v
[✓] Flutter (Channel dev, v1.18.0-10.0.pre, on Mac OS X 10.15.2 19C57, locale en-AU)
    • Flutter version 1.18.0-10.0.pre at /Users/alfred/Developer/flutter
    • Framework revision e0c63cd35e (4 weeks ago), 2020-04-23 22:29:01 -0400
    • Engine revision d2ec21221e
    • Dart version 2.9.0 (build 2.9.0-3.0.dev b0d35855d8)

[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/alfred/Library/Android/sdk
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = /Users/alfred/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    ! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.8.4

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

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 44.0.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

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

[✓] Connected device (2 available)
    • Web Server • web-server • web-javascript • Flutter Tools
    • Chrome     • chrome     • web-javascript • Google Chrome 81.0.4044.138

! Doctor found issues in 1 category.

flutter run --verbose:
[   +7 ms] executing: [/Users/alfred/Developer/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +31 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[        ] e0c63cd35e15e407a80dc44281cc392535fcce25
[        ] executing: [/Users/alfred/Developer/flutter/] git tag --contains HEAD
[ +137 ms] Exit code 0 from: git tag --contains HEAD
[   +2 ms] 1.18.0-10.0.pre
           1.18.0-11.0.pre
           1.18.0-11.1.pre
           1.18.0-12.0.pre
           1.18.0-13.0.pre
           1.18.0-8.0.pre
           1.18.0-9.0.pre
           1.19.0-0.0.pre
           1.19.0-1.0.pre
[  +10 ms] executing: [/Users/alfred/Developer/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[   +8 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/dev
[        ] executing: [/Users/alfred/Developer/flutter/] git ls-remote --get-url origin
[   +7 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] git@github.com:flutter/flutter.git
[  +45 ms] executing: [/Users/alfred/Developer/flutter/] git rev-parse --abbrev-ref HEAD
[   +9 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] dev
[   +5 ms] executing: sw_vers -productName
[  +12 ms] Exit code 0 from: sw_vers -productName
[        ] Mac OS X
[        ] executing: sw_vers -productVersion
[  +10 ms] Exit code 0 from: sw_vers -productVersion
[        ] 10.15.2
[        ] executing: sw_vers -buildVersion
[  +11 ms] Exit code 0 from: sw_vers -buildVersion
[   +2 ms] 19C57
[  +37 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] 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.
[   +2 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.
[   +8 ms] executing: /Users/alfred/Library/Android/sdk/platform-tools/adb devices -l
[   +4 ms] executing: /usr/bin/xcode-select --print-path
[   +5 ms] Exit code 0 from: /usr/bin/xcode-select --print-path
[        ] /Applications/Xcode.app/Contents/Developer
[   +1 ms] executing: /usr/bin/xcodebuild -version
[  +74 ms] Exit code 0 from: /usr/bin/xcodebuild -version
[        ] Xcode 11.4.1
           Build version 11E503a
[   +1 ms] executing: xcrun --find xcdevice
[   +6 ms] Exit code 0 from: xcrun --find xcdevice
[        ] /Applications/Xcode.app/Contents/Developer/usr/bin/xcdevice
[        ] executing: xcrun xcdevice list --timeout 2
[   +3 ms] /usr/bin/xcrun simctl list --json devices
[        ] executing: /usr/bin/xcrun simctl list --json devices
[  +31 ms] List of devices attached
[  +52 ms] {
             "devices" : {
               "com.apple.CoreSimulator.SimRuntime.tvOS-13-4" : [
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/0AD1B0AA-32F0-40E1-812B-7676AA5BDA95\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/0AD1B0AA-32F0-40E1-812B-7676AA5BDA95",
                   "udid" : "0AD1B0AA-32F0-40E1-812B-7676AA5BDA95",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-1080p",
                   "state" : "Shutdown",
                   "name" : "Apple TV"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/6D288427-6BB7-4A45-9698-6A1E8A94575C\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/6D288427-6BB7-4A45-9698-6A1E8A94575C",
                   "udid" : "6D288427-6BB7-4A45-9698-6A1E8A94575C",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-4K",
                   "state" : "Shutdown",
                   "name" : "Apple TV 4K"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/C8956A06-3060-4503-AC8B-045D52AEB58B\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/C8956A06-3060-4503-AC8B-045D52AEB58B",
                   "udid" : "C8956A06-3060-4503-AC8B-045D52AEB58B",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-1080p",
                   "state" : "Shutdown",
                   "name" : "Apple TV 4K (at 1080p)"
                 }
               ],
               "com.apple.CoreSimulator.SimRuntime.watchOS-6-2" : [
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/009A0592-4A67-4D8D-BF06-8E51CBFEB335\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/009A0592-4A67-4D8D-BF06-8E51CBFEB335",
                   "udid" : "009A0592-4A67-4D8D-BF06-8E51CBFEB335",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-4-40mm",
                   "state" : "Shutdown",
                   "name" : "Apple Watch Series 4 - 40mm"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/37AC558E-8213-442A-BAB6-6B5BBB1885DA\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/37AC558E-8213-442A-BAB6-6B5BBB1885DA",
                   "udid" : "37AC558E-8213-442A-BAB6-6B5BBB1885DA",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-4-44mm",
                   "state" : "Shutdown",
                   "name" : "Apple Watch Series 4 - 44mm"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/3FEFD8B1-8BA5-4779-BC7F-5437BBD74D08\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/3FEFD8B1-8BA5-4779-BC7F-5437BBD74D08",
                   "udid" : "3FEFD8B1-8BA5-4779-BC7F-5437BBD74D08",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-5-40mm",
                   "state" : "Shutdown",
                   "name" : "Apple Watch Series 5 - 40mm"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/B6CD7724-E00F-493E-8D72-273DEE7301B7\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/B6CD7724-E00F-493E-8D72-273DEE7301B7",
                   "udid" : "B6CD7724-E00F-493E-8D72-273DEE7301B7",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-5-44mm",
                   "state" : "Shutdown",
                   "name" : "Apple Watch Series 5 - 44mm"
                 }
               ],
               "com.apple.CoreSimulator.SimRuntime.iOS-13-4" : [
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/E3933D77-8A31-4CB5-ACC6-A6E6DDF62E65\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/E3933D77-8A31-4CB5-ACC6-A6E6DDF62E65",
                   "udid" : "E3933D77-8A31-4CB5-ACC6-A6E6DDF62E65",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8",
                   "state" : "Shutdown",
                   "name" : "iPhone 8"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/0D67F9EF-74D4-4612-9870-79B96EF18129\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/0D67F9EF-74D4-4612-9870-79B96EF18129",
                   "udid" : "0D67F9EF-74D4-4612-9870-79B96EF18129",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8-Plus",
                   "state" : "Shutdown",
                   "name" : "iPhone 8 Plus"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/AC752599-EF65-43D7-BBF7-9CEDDEF6973D\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/AC752599-EF65-43D7-BBF7-9CEDDEF6973D",
                   "udid" : "AC752599-EF65-43D7-BBF7-9CEDDEF6973D",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11",
                   "state" : "Shutdown",
                   "name" : "iPhone 11"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/22B5914B-0C98-4FC0-9500-44903461EF92\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/22B5914B-0C98-4FC0-9500-44903461EF92",
                   "udid" : "22B5914B-0C98-4FC0-9500-44903461EF92",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro",
                   "state" : "Shutdown",
                   "name" : "iPhone 11 Pro"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/D3440940-A121-429B-8CA9-CFA71DE0773B\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/D3440940-A121-429B-8CA9-CFA71DE0773B",
                   "udid" : "D3440940-A121-429B-8CA9-CFA71DE0773B",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro-Max",
                   "state" : "Shutdown",
                   "name" : "iPhone 11 Pro Max"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/60AD6742-6F89-4AAA-A255-BF86D20555D4\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/60AD6742-6F89-4AAA-A255-BF86D20555D4",
                   "udid" : "60AD6742-6F89-4AAA-A255-BF86D20555D4",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-SE--2nd-generation-",
                   "state" : "Shutdown",
                   "name" : "iPhone SE (2nd generation)"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/52C03E44-4155-4B1D-9A0C-77C9AFFF38A0\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/52C03E44-4155-4B1D-9A0C-77C9AFFF38A0",
                   "udid" : "52C03E44-4155-4B1D-9A0C-77C9AFFF38A0",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--9-7-inch-",
                   "state" : "Shutdown",
                   "name" : "iPad Pro (9.7-inch)"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/B17F04D4-0B78-4035-A9C4-959F5D2AC4E8\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/B17F04D4-0B78-4035-A9C4-959F5D2AC4E8",
                   "udid" : "B17F04D4-0B78-4035-A9C4-959F5D2AC4E8",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad--7th-generation-",
                   "state" : "Shutdown",
                   "name" : "iPad (7th generation)"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/5F6668D6-0080-49B9-B86F-7DC08EDF6502\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/5F6668D6-0080-49B9-B86F-7DC08EDF6502",
                   "udid" : "5F6668D6-0080-49B9-B86F-7DC08EDF6502",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--11-inch---2nd-generation-",
                   "state" : "Shutdown",
                   "name" : "iPad Pro (11-inch) (2nd generation)"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/E9ABC5F7-3FE3-4F95-9C97-EA117DD994CD\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/E9ABC5F7-3FE3-4F95-9C97-EA117DD994CD",
                   "udid" : "E9ABC5F7-3FE3-4F95-9C97-EA117DD994CD",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---4th-generation-",
                   "state" : "Shutdown",
                   "name" : "iPad Pro (12.9-inch) (4th generation)"
                 },
                 {
                   "dataPath" : "\/Users\/alfred\/Library\/Developer\/CoreSimulator\/Devices\/F098CAB5-E8D8-4511-9660-D4A478C34560\/data",
                   "logPath" : "\/Users\/alfred\/Library\/Logs\/CoreSimulator\/F098CAB5-E8D8-4511-9660-D4A478C34560",
                   "udid" : "F098CAB5-E8D8-4511-9660-D4A478C34560",
                   "isAvailable" : true,
                   "deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air--3rd-generation-",
                   "state" : "Shutdown",
                   "name" : "iPad Air (3rd generation)"
                 }
               ]
             }
           }
[+2361 ms] [
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4 (17L255)",
                        "available" : true,
                        "platform" : "com.apple.platform.appletvsimulator",
                        "modelCode" : "AppleTV6,2",
                        "identifier" : "6D288427-6BB7-4A45-9698-6A1E8A94575C",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.apple-tv-4k",
                        "modelName" : "Apple TV 4K",
                        "name" : "Apple TV 4K"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad11,3",
                        "identifier" : "F098CAB5-E8D8-4511-9660-D4A478C34560",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-air3-wifi-1",
                        "modelName" : "iPad Air (3rd generation)",
                        "name" : "iPad Air (3rd generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4 (17L255)",
                        "available" : true,
                        "platform" : "com.apple.platform.appletvsimulator",
                        "modelCode" : "AppleTV5,3",
                        "identifier" : "0AD1B0AA-32F0-40E1-812B-7676AA5BDA95",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.apple-tv-4",
                        "modelName" : "Apple TV",
                        "name" : "Apple TV"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad8,12",
                        "identifier" : "E9ABC5F7-3FE3-4F95-9C97-EA117DD994CD",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-pro-12point9-4th-1",
                        "modelName" : "iPad Pro (12.9-inch) (4th generation)",
                        "name" : "iPad Pro (12.9-inch) (4th generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "6.2 (17T256)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch5,4",
                        "identifier" : "B6CD7724-E00F-493E-8D72-273DEE7301B7",
                        "architecture" : "i386",
                        "modelUTI" : "com.apple.watch-series5-1",
                        "modelName" : "Apple Watch Series 5 - 44mm",
                        "name" : "Apple Watch Series 5 - 44mm"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "6.2 (17T256)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch5,3",
                        "identifier" : "3FEFD8B1-8BA5-4779-BC7F-5437BBD74D08",
                        "architecture" : "i386",
                        "modelUTI" : "com.apple.watch-series5-1",
                        "modelName" : "Apple Watch Series 5 - 40mm",
                        "name" : "Apple Watch Series 5 - 40mm"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4 (17L255)",
                        "available" : true,
                        "platform" : "com.apple.platform.appletvsimulator",
                        "modelCode" : "AppleTV6,2",
                        "identifier" : "C8956A06-3060-4503-AC8B-045D52AEB58B",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.apple-tv-4k",
                        "modelName" : "Apple TV 4K (at 1080p)",
                        "name" : "Apple TV 4K (at 1080p)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "6.2 (17T256)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch4,3",
                        "identifier" : "009A0592-4A67-4D8D-BF06-8E51CBFEB335",
                        "architecture" : "i386",
                        "modelUTI" : "com.apple.watch-series4-1",
                        "modelName" : "Apple Watch Series 4 - 40mm",
                        "name" : "Apple Watch Series 4 - 40mm"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad8,9",
                        "identifier" : "5F6668D6-0080-49B9-B86F-7DC08EDF6502",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-pro-11-2nd-1",
                        "modelName" : "iPad Pro (11-inch) (2nd generation)",
                        "name" : "iPad Pro (11-inch) (2nd generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad6,4",
                        "identifier" : "52C03E44-4155-4B1D-9A0C-77C9AFFF38A0",
                        "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" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone10,4",
                        "identifier" : "E3933D77-8A31-4CB5-ACC6-A6E6DDF62E65",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-8-2",
                        "modelName" : "iPhone 8",
                        "name" : "iPhone 8"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,5",
                        "identifier" : "D3440940-A121-429B-8CA9-CFA71DE0773B",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-11-pro-max-1",
                        "modelName" : "iPhone 11 Pro Max",
                        "name" : "iPhone 11 Pro Max"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,3",
                        "identifier" : "22B5914B-0C98-4FC0-9500-44903461EF92",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-11-pro-1",
                        "modelName" : "iPhone 11 Pro",
                        "name" : "iPhone 11 Pro"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "6.2 (17T256)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch4,4",
                        "identifier" : "37AC558E-8213-442A-BAB6-6B5BBB1885DA",
                        "architecture" : "i386",
                        "modelUTI" : "com.apple.watch-series4-1",
                        "modelName" : "Apple Watch Series 4 - 44mm",
                        "name" : "Apple Watch Series 4 - 44mm"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,8",
                        "identifier" : "60AD6742-6F89-4AAA-A255-BF86D20555D4",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-se-1",
                        "modelName" : "iPhone SE (2nd generation)",
                        "name" : "iPhone SE (2nd generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad7,12",
                        "identifier" : "B17F04D4-0B78-4035-A9C4-959F5D2AC4E8",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.ipad-7-wwan-1",
                        "modelName" : "iPad (7th generation)",
                        "name" : "iPad (7th generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone10,5",
                        "identifier" : "0D67F9EF-74D4-4612-9870-79B96EF18129",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-8-plus-2",
                        "modelName" : "iPhone 8 Plus",
                        "name" : "iPhone 8 Plus"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.4.1 (17E8260)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,1",
                        "identifier" : "AC752599-EF65-43D7-BBF7-9CEDDEF6973D",
                        "architecture" : "x86_64",
                        "modelUTI" : "com.apple.iphone-11-1",
                        "modelName" : "iPhone 11",
                        "name" : "iPhone 11"
                      }
                    ]
[   +5 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] 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.
[   +1 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.
[  +48 ms] More than one device connected; please specify a device with the '-d <deviceId>' flag, or use '-d all' to act on all devices.
[  +37 ms] Web Server • web-server • web-javascript • Flutter Tools
[        ] Chrome     • chrome     • web-javascript • Google Chrome 81.0.4044.138
[   +9 ms] "flutter run" took 2,671ms.

flutter run --verbose ERROR
#0      throwToolExit (package:flutter_tools/src/base/common.dart:14:3)
#1      RunCommand.validateCommand (package:flutter_tools/src/commands/run.dart:334:7)
<asynchronous suspension>
#2      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:740:11)
<asynchronous suspension>
#3      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:657:33)
<asynchronous suspension>
#4      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart)
#5      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:29)
#6      _rootRun (dart:async/zone.dart:1184:13)
#7      _CustomZone.run (dart:async/zone.dart:1077:19)
#8      _runZoned (dart:async/zone.dart:1619:10)
#9      runZoned (dart:async/zone.dart:1539:10)
#10     AppContext.run (package:flutter_tools/src/base/context.dart:149:18)
#11     FlutterCommand.run (package:flutter_tools/src/runner/flutter_command.dart:647:20)
#12     CommandRunner.runCommand (package:args/command_runner.dart:197:27)
#13     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:339:21)
#14     _rootRunUnary (dart:async/zone.dart:1192:38)
#15     _CustomZone.runUnary (dart:async/zone.dart:1085:19)
#16     _FutureListener.handleValue (dart:async/future_impl.dart:141:18)
#17     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:682:45)
#18     Future._propagateToListeners (dart:async/future_impl.dart:711:32)
#19     Future._completeWithValue (dart:async/future_impl.dart:526:5)
#20     _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:36:15)
#21     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:303:13)
#22     FlutterVersion.checkFlutterVersionFreshness (package:flutter_tools/src/version.dart)
#23     _rootRunUnary (dart:async/zone.dart:1192:38)
#24     _CustomZone.runUnary (dart:async/zone.dart:1085:19)
#25     _FutureListener.handleValue (dart:async/future_impl.dart:141:18)
#26     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:682:45)
#27     Future._propagateToListeners (dart:async/future_impl.dart:711:32)
#28     Future._completeWithValue (dart:async/future_impl.dart:526:5)
#29     Future._asyncComplete.<anonymous closure> (dart:async/future_impl.dart:556:7)
#30     _rootRun (dart:async/zone.dart:1184:13)
#31     _CustomZone.run (dart:async/zone.dart:1077:19)
#32     _CustomZone.runGuarded (dart:async/zone.dart:979:7)
#33     _CustomZone.bindCallbackGuarded.<anonymous closure> (dart:async/zone.dart:1019:23)
#34     _microtaskLoop (dart:async/schedule_microtask.dart:43:21)
#35     _startMicrotaskLoop (dart:async/schedule_microtask.dart:52:5)
#36     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:118:13)
#37     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:169:5)

pubspec.yaml
version: 1.0.0+1

environment:
  sdk: ">=2.6.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter
  dartz: ^0.9.0-dev.6
  freezed_annotation: ^0.7.1
  uuid: ^2.0.4
  flutter_bloc: ^3.2.0
  auto_route: ^0.4.4
  get_it: ^3.1.0
  meta: ^1.1.8
  algolia: ^0.1.7
  google_maps: ^3.4.1
  firebase_core: 0.4.4
  firebase_auth: 0.15.3
  google_sign_in: ^4.1.1
  cloud_firestore: ^0.13.5
  cloud_functions: ^0.5.0
  cloud_functions_web: ^1.1.0
  injectable: ^0.3.0
  flushbar: ^1.10.0
  intl: ^0.16.1
  timeago: ^2.0.26
  json_annotation: ^3.0.1
  google_maps_flutter: ^0.5.27
  google_maps_flutter_platform_interface: ^1.0.1
  styled_widget: ^0.1.1
  flutter_hooks: ^0.8.0
  time: ^1.2.0
  kt_dart: ^0.7.0
  rxdart: ^0.23.1
  dash_chat: ^1.1.1
  reorderables: ^0.2.12
  responsive_builder: ^0.1.2
  provider: ^4.0.4
  carousel_slider: ^2.0.0
  smooth_star_rating: 1.0.4+2
  implicitly_animated_reorderable_list: ^0.1.9
  flutter_slidable: ^0.5.4

dev_dependencies:
  flutter_test:
    sdk: flutter
  mockito: ^4.1.1
  cloud_firestore_mocks: ^0.4.2
  lint: ^1.1.1
  build_runner:
  freezed: ^0.9.2
  auto_route_generator: ^0.4.5
  injectable_generator: ^0.3.2
  json_serializable: ^3.2.5

Looks like it may be related to  https://github.com/FirebaseExtended/flutterfire/pull/2706

Make sure you have the right version in index.html:
  <script src="https://www.gstatic.com/firebasejs/7.6.2/firebase-functions.js"></script>
instead of
  <script src="https://www.gstatic.com/firebasejs/7.21.1/firebase-functions.js"></script>
I upgraded all of my firebase js dependencies and cloud functions stopped working after that. Had no clue that this was the issue.

I'm also getting this FirebaseError: internal (internal)

Stack trace

46:45 ReduxLogging/INFO: {Action: Instance of 'MakeAdminAction', State: StoreState, ts: 2020-10-06 15:56:46.045}
Error: FirebaseError: internal (internal)
    at Object.throw_ [as throw] (http://localhost:7357/dart_sdk.js:4328:11)
    at handleThenable (http://localhost:7357/packages/firebase/src/storage.dart.lib.js:3264:21)
    at handleThenable.throw (<anonymous>)
    at http://localhost:7357/dart_sdk.js:37599:38
    at _RootZone.runBinary (http://localhost:7357/dart_sdk.js:37452:58)
    at _FutureListener.thenAwait.handleError (http://localhost:7357/dart_sdk.js:32436:48)
    at handleError (http://localhost:7357/dart_sdk.js:32987:51)
    at Function._propagateToListeners (http://localhost:7357/dart_sdk.js:33013:17)
    at _Future.new.[_completeError] (http://localhost:7357/dart_sdk.js:32860:23)
    at async._AsyncCallbackEntry.new.callback (http://localhost:7357/dart_sdk.js:32898:31)
    at Object._microtaskLoop (http://localhost:7357/dart_sdk.js:37708:13)
    at _startMicrotaskLoop (http://localhost:7357/dart_sdk.js:37714:13)
    at http://localhost:7357/dart_sdk.js:33226:9

I've adjusted my firebase-functions.js import to 7.6.2 however I am still getting the error.

Any solution to this? I got the same error.

Is there any news or workarounds for this yet?

Is there any news or workarounds for this yet?

I tried rolling back everything to an older version (0.8.0 cloud_functions and compatible rest of libraries) and it still doesn't work.
Even the most simple form of cloud functions trigger this internal exception.

I tried rolling back everything to an older version (0.8.0 cloud_functions and compatible rest of libraries) and it still doesn't work.
Even the most simple form of cloud functions trigger this internal exception.

I tried rolling back everything to an older version (0.8.0 cloud_functions and compatible rest of libraries) and it still doesn't work.
Even the most simple form of cloud functions trigger this internal exception.

Do you have the right version in index.html ?

I tried rolling back everything to an older version (0.8.0 cloud_functions and compatible rest of libraries) and it still doesn't work.
Even the most simple form of cloud functions trigger this internal exception.

Do you have the right version in index.html ?

I tried rolling back everything to an older version (0.8.0 cloud_functions and compatible rest of libraries) and it still doesn't work.
Even the most simple form of cloud functions trigger this internal exception.

Do you have the right version in index.html ?

Yes, same issue. Internal error. This happens with both local emulator and deployed functions.
The thing is that the functions are executed successfully (I can see it in the logs). It's just that the flutter functions library throws this exception afterwards.

I tried rolling back everything to an older version (0.8.0 cloud_functions and compatible rest of libraries) and it still doesn't work.
Even the most simple form of cloud functions trigger this internal exception.

Do you have the right version in index.html ?

Yes, same issue. Internal error. This happens with both local emulator and deployed functions.
The thing is that the functions are executed successfully (I can see it in the logs). It's just that the flutter functions library throws this exception afterwards.

@GyuriMajercsik I found the issue, but with my limited web skills I have no idea how to fix it:
Access to fetch at 'http://localhost:5001/*******' from origin 'http://localhost:37349' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

@GyuriMajercsik I found the issue, but with my limited web skills I have no idea how to fix it:
Access to fetch at 'http://localhost:5001/*******' from origin 'http://localhost:37349' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Ok, so if you're hitting the CORS issue, it seems that the function is getting triggered on the OPTIONS request the browser is making. You need to return the standard CORS response and then the browser will make the normal request using POST.

Ok, so if you're hitting the CORS issue, it seems that the function is getting triggered on the OPTIONS request the browser is making. You need to return the standard CORS response and then the browser will make the normal request using POST.

Seems 7.22.0 version is broken for cloud functions, but for 7.22.1, it is working.

It is not working for me on any version, I cannot believe it is still not fixed and it has been about a year now.

@markusaksli-nc, @linhdogg,@alexandru-g has anyone found any workaround for this? Or is there anyone working on this issue?

@vishnuagbly as a temporary workaround, in your cloud functions, check first if it's an OPTIONS type of request and return 200. The normal POST will work correctly afterwards.

@alexandru-g since we are using firebase cloud functions are cloud function looks like this
const functions = require('firebase-functions');

exports.listFruit = functions.https.onCall((data, context) => {
  return ["Apple", "Banana", "Cherry", "Date", "Fig", "Grapes"]
});

I don't know how to do that here 😥

@vishnuagbly you can also use onRequest instead of onCall. Please see the documentation: https://firebase.google.com/docs/functions/get-started#add-the-addmessage-function.
In the example above you can check the type of request in the req object. Also, please make sure you set the appropriate CORS headers. Something like:
export const someFunction = functions.https.onRequest((request, response) => {
    response.set({
        'Access-Control-Allow-Origin': '*',
        'Access-Control-Allow-Methods': 'GET,PUT,POST,DELETE,PATCH,OPTIONS',
        'Access-Control-Allow-Headers': 'Origin, X-Requested-With, Content-Type, Accept, Authorization',
    });
    if (request.method == "OPTIONS") {
        response.sendStatus(200);
        return;
    }
    // Your normal function execution

I had no problem by doing the above, but it's just a workaround.

Stunning that this show stopping, critical bug hasn't been fixed. Sours me on the whole not-ready-for-prime-time Google cloud ecosystem.
Disclosure: I submitted #5428 (now closed as a duplicate) after spending a week looking for a work-around. Did not find a work-around. No combination of cloud_functions and JS versions works for me.

@alexandru-g unfortunately I cannot use your workaround as I need the context object to check for firebase authorization and uid, and for which I don't have enough knowledge to implement it by myself using HTTP requests.

I fixed it, at least for me.

I used to 7.14.2 version same as in the cloud functions package example.
I think we also need to make sure that firebase-app and firebase functions js files are of same version, as I changed both to 7.14.2 and it worked.

@vishnuagbly I'm still seeing the problem (that is, I'm still seeing the internal exception). Would you let me know more precisely the two locations where you sync'd up the js versions?   Index.html in the app and ??
I'd like to make sure that I'm doing the same thing.  Thanks in advance!

This is my index.html file now
<!DOCTYPE html>
<html>
<head>
  <!--
    If you are serving your web app in a path other than the root, change the
    href value below to reflect the base path you are serving from.

    The path provided below has to start and end with a slash "/" in order for
    it to work correctly.

    Fore more details:
    * https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base
  -->
  <base href="/">

  <meta charset="UTF-8">
  <meta content="IE=Edge" http-equiv="X-UA-Compatible">
  <meta name="description" content="A new Flutter project.">

  <!-- iOS meta tags & icons -->
  <meta name="apple-mobile-web-app-capable" content="yes">
  <meta name="apple-mobile-web-app-status-bar-style" content="black">
  <meta name="apple-mobile-web-app-title" content="appName">
  <meta name="google-signin-client_id" content="<GOOGLE_SIGN_IN_API_KEY>">
  <link rel="apple-touch-icon" href="icons/Icon-192.png">

  <!-- Favicon -->
  <link rel="icon" type="image/png" href="favicon.png"/>

  <title>othello</title>
  <link rel="manifest" href="manifest.json">
</head>
<body>
<!-- The core Firebase JS SDK is always required and must be listed first -->
<script src="https://www.gstatic.com/firebasejs/7.14.4/firebase-app.js"></script>

<script src="/__/firebase/8.3.1/firebase-analytics.js"></script>
<script src="https://www.gstatic.com/firebasejs/7.20.0/firebase-firestore.js"></script>
<script src="https://www.gstatic.com/firebasejs/7.20.0/firebase-auth.js"></script>
<script src="https://www.gstatic.com/firebasejs/7.14.4/firebase-functions.js"></script>

<!-- Initialize Firebase -->
<script>
      const firebaseConfig = {
           //copied from firbase console -> project_settings -> web_app -> config
      };

      // Initialize Firebase
      firebase.initializeApp(firebaseConfig);
    </script>
  <!-- This script installs service_worker.js to provide PWA functionality to
       application. For more information, see:
       https://developers.google.com/web/fundamentals/primers/service-workers -->
  <script>
    if ('serviceWorker' in navigator) {
      window.addEventListener('flutter-first-frame', function () {
        navigator.serviceWorker.register('flutter_service_worker.js');
      });
    }
  </script>
  <script src="main.dart.js" type="application/javascript"></script>
</body>
</html>

@vishnuagbly Thanks for the additional information! Still no luck however. Still getting the internal exception. Very puzzling.

I feel like flutter should provide more information than the internal exception.

This is broken for me too, can't get any onCall function to work, no matter if the flutter web app is on localhost or deployed to https, I always get a CORS policy error

Hey folks, I've just confirmed this works on web. Please ensure you're using the following scripts in your index.html file as per the documentation:
    <script src="https://www.gstatic.com/firebasejs/8.4.1/firebase-app.js"></script>
    <script src="https://www.gstatic.com/firebasejs/8.4.1/firebase-functions.js"></script>

along with the latest functions version as per documentation:
  firebase_core: "^1.0.4"
  cloud_functions: "^1.0.4"

@russellwheatley Still fails (internal exception) for me using JS 8.4.1 and latest versions of firebase_core & cloud_functions.

I also have the same issue but it works before user logs in to google. As soon as _firebaseAuth.signInWithCredential succeeds, all subsequent calls show FirebaseFunctionsException with 'internal' as the error. Anyone any idea?


Expose data using GraphQL

Tks for this work!
I'm not sure if this is the best place to discuss this, but I think GraphQL would be great to help people explore all this data.
I think the ideal workflow for this project would be:

fetch data from sources from government
store this data in a database (I think mongodb could be great for this)
apply machine learning / data analysis on top of this data

I want to also expose this data though GraphQL so it could be easily used by other projects
create-graphql could be very helpful to create the graphql schema on top of the mongo database

Not exactly related, but might be of interest: #101

Yet some minor comments:

I'm not sure if this is the best place to discuss this, but I think GraphQL would be great to help people explore all this data.

Sure this is the right place ; )

store this data in a database (I think mongodb could be great for this)

We tend to store data as dataset files, not database — it's a best practice in data science. Works better in terms of reproducibility (versioning of datasets, for example: an analysis made with a data collect today will differ from an analysis with data collected a couple of weeks ago, but both must be reproducible by anyone). We tend to use the CSV format, which is better for tabular data, but in this case creating JSON files would work better — and surely would not be a problem in terms of best practices ; )

@sibelius Neo4j is a great tool for Graph queries since it models data as graphs on the DB instead of applying a layer of graphs on top of complicated queries and database performance. If you're looking to work with stored data + graphs, it might be worth to take a look. :)

As this is quite similar to #101, and #101 is closed, I think I can archive this too.


Change disk layout per provider

We are creating a new off-site backup machine in Skyscape in addition to the existing machine in Carrenza. The layout of the disks has changed because, over time, additional disks have been added to existing LVM volume groups on the Carrenza machine, and because we want to squash disks to increase performance (on the Skyscape SAN, a VM with more than 1.8tb will span LUNs; 1.8tb because there is an overhead on the 2tb total LUN size). Squashing disks also helps pay mitigate against https://github.com/gds-operations/vcloud-launcher/issues/104. We also get to increase disk size for Graphite backups, too.

@ajlanghorn It's not clear to me from your pull request why merging disk volumes would increase performance; would the total amount of disk space used not still span LUNs?

@mattbostock Skyscape have 2tb LUNs on their SANs, according to @rjw1. There is then a storage overhead, so the maximum usable per disk - if you don't want the disk to stretch LUNs - is 1.8tb. Stretching LUNs is bad because you rely on the connectivity between not dropping packets when the data is being written, and also connectivity between SAN nodes to be free of errors, reliable, and fast. Ultimately, it's unlikely to be any of these things, so stretching LUNs isn't a good idea, IMHO. As these disks are all <1.8tb, this should ensure they reside wholly on one LUN (wherever that might be).

Probably going to be superceded; closing.


Unable to get past "Provisioning" step for any Ohio application

App ID: d2nrk2jnhh6rx0
Region: Ohio only (can deploy fine in Oregon)
What can I do to get past this? This is for a production app which needs to be updated ASAP.

I've attached another screenshot - not sure if it's relevant or not

We had the same issue on our app (in the eu-west-1 region). Our project build is stuck in Provisioning, and I can find no indications of what is going wrong. We contacted AWS Support, and they recommended we bring it here. App id is dm197t2mo7xbv. Please reach out if you need more details.

@nucat176 @nhc-motosumo I see your most recent builds/deploys were successful. Can you share the branch name and specific build number where your build got stuck on provisioning?

@kahdojay thanks for the reply here. Our most recent builds on the affected apps are still failing. The branch name is "master" (although "staging" appears broken as well) and the most recent build number is 42

Can you share the branch name and specific build number where your build got stuck on provisioning?

Thanks for the response! For us, it is Build 13, in branch develop, of app dm197t2mo7xbv. I do not think we have seen a successful build for days (another branch seems affected by #936). Only an older master build was successful. There may be errors on our side, but I cannot figure out how to debug this.

@nucat176 @nhc-motosumo we are looking into it with high priority.

@swaminator great, thanks so much. Is it officially a bug on the AWS side?

@nucat176 Can you give it another try in us-east-2?

@kahdojay no good on my end

@nucat176 It looks like there was an issue with the verification / screenshot step for your app causing some builds to get stuck. We addressed the screenshot issue in us-east-2 but the stuck builds were causing you to reach the concurrent job limit. We've updated the status of those builds so your next attempt should go through, can you give it another try?

Our builds seem to work now. Thanks for the investigation!
Question, though: If we ever hit the concurrency limit again, is there a way for us to see that, and maybe take action? E.g. effectively killing a stuck build?

@nhc-motosumo The concurrency limit is currently 6.  If you look at the screenshot nucat176 posted above, in the upper right there are arrows and a cancel button.  You should be able to navigate to the specific build and cancel.


[add-resource] New Plugin/Theme: Markdown Yet Another Linker

I would like to add my new plugin/theme to the Grav Repository.
Here are the project details: HuidaeCho/grav-plugin-markdown-yalinker
This new plugin named Markdown Yet Another Linker (markdown-yalinker) allows the user to create links with less typing in certain cases using MediaWiki-like syntax. For example, in regular Markdown, [Page Title](page-title) requires typing the page name almost twice. Typing page slugs is also error-prone. This plugin allows [[Page Title]], [[Page Title|Text]], [[../Relative/Page Title]], [[../Relative/Page Title|]], etc. For more details about this syntax, please check its usage.
This plugin addresses the issue in this topic.
Thanks!

This needs a release before it will show up in GPM.  See https://learn.getgrav.org/16/advanced/grav-development#theme-plugin-release-process

@HuidaeCho Did you perhaps miss the above? We can't really publish this until there is a tag/release of the plugin.

@rhukster @w00fz Thanks for the follow up. I just created a release. https://github.com/HuidaeCho/grav-plugin-markdown-yalinker/releases/tag/v1.0.0
Thanks!

I think you have inconsistent versions for your blueprint/tag/changelog. Your tag should match everything else. Right now you have v1.0.0 as tag and reference that in CHANGELOG too (https://github.com/HuidaeCho/grav-plugin-markdown-yalinker/tree/v1.0.0), however in your blueprint (https://github.com/HuidaeCho/grav-plugin-markdown-yalinker/blob/v1.0.0/blueprints.yaml#L4) the version is 0.1.0.
What I would suggest you do before I publish your plugin:

delete your release AND tag
Go to https://github.com/HuidaeCho/grav-plugin-markdown-yalinker/releases/tag/v1.0.0
Click Delete Release
Click on the v1.0.0 tag (same URL as above should work too)
Click Delete Tag
Edit your blueprints.yaml and change version to 1.0.0 (we suggest you don't use v in front), save/commit.
Edit your CHANGELOG.md and change version to 1.0.0 instead of v1.0.0, save/commit.
Go to https://github.com/HuidaeCho/grav-plugin-markdown-yalinker/releases/new for drafting a new Release and just type 1.0.0 in the Tag Version field. You can add a title and descriptions too, they are optional.

This should get your versions in line, in the future when you need to do a release it will be pretty much the same process, except for the deletion part that won't be needed.
More info: https://learn.getgrav.org/16/advanced/grav-development#theme-plugin-release-process

Thanks for checking. I did it again.

Looking good! It's now in GPM.
Cheers


Enable Query Logging and Access Query Log

Allow Spot to enable the DBAL query logger and also provide easy access to it for viewing queries run:
The code requires first setting a query logger, and then providing access to it for use.
use Doctrine\DBAL\Logging\DebugStack;
$logger = new DebugStack();
$config->setSQLLogger($logger);

I currently use the following, and it works like a charm. A convenience method would be nice though :)
$spot
 ->config()
 ->connection()
 ->getConfiguration()
 ->setSQLLogger(new \Doctrine\DBAL\Logging\EchoSQLLogger())


[cli-test] speed up yarn example

Summary
Doing devbox shell would have yarn install try to build nodejs from scratch. Took way too long.
How was it tested?
Ran curl 'https://search.devbox.sh/v1/search?q=yarn' | jq | less
Picked the top-most commit-hash
Ran rm -rf .devbox && devbox shell and it installed quickly

Current dependencies on/for this PR:

main

PR #1386   👈

This comment was auto-generated by Graphite.

yeah, seems like it had to do with the nixpkgs commit hash for some reason?


chore(ps_test): Remove excessive assertions that cause test failure

Alternative to #164
Instead of marking these tests pending, this removes some assertions that were probably excessive to begin with, thus allowing us to keep these tests.

running these tests now

did not see a failure from the ps_test. I had other failures so rerunning again.

I'm confident that this will fix out ps:test problem for now.

this failed for unrelated reasons, but #164 was merged which fixes the same root issue this PR was trying to solve. Shall we close this one out and track the root issue at deis/controller#631?

Closing this because #164 was merged.


[Impeller] Improve Impeller performance on Vulkan devices without lazily allocated memory support.

The tracking benchmark is:
A02 new Galley
Rough idea:

Add capability to measure heap memory usage on CI.
... reduce memory usage!

The primary trick here is making sure that the transient attachments for the onscreen (MSAA and Depth/Stencil) are effectively recycled. In fact, I think we can actually make a single Onscreen MSAA and Onscreen Depth/Stencil and share them across the swapchain images - as they should be effectively synchronized already.

At least on average frame time, this is now faster than it was with GLES. Waiting for more data points for 90%+

This is done!


Ospray on iOS

Thank you very much for the great effort.
I have a question. I request you to help. Sorry for asking my question as a "issue". I could not find any option to mark it as a request/question.
Would it be theoretically possible to compile OSPRAY for iOS?  Feature

I doubt that: OSPRay and Embree require SSE instruction set, which is not supported on ARM. However, what should work well is to use an iOS device for remotely viewing OSPRay renderings (see e.g. the Tapestry project.

I don’t know about iOS specifically, but you might take a look at the work that Syoyo Fujita has done on the Android/aarch64 version of Embree, and ispc.
https://github.com/lighttransport
https://github.com/lighttransport/embree-aarch64
https://github.com/syoyo/repositories
https://github.com/syoyo/ispc-aarch64
https://github.com/syoyo/tbb-aarch64
Cheers,
Bruce
On Apr 29, 2019, at 5:01 AM, Johannes Günther <notifications<EMAIL_ADDRESS>wrote:
I doubt that: OSPRay and Embree require SSE instruction set, which is not supported on ARM. However, what should work well is to use an iOS device for remotely viewing OSPRay renderings (see e.g. the Tapestryhttps://seelabutk.github.io/tapestry/ project.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/ospray/ospray/issues/319#issuecomment-487523324, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACPU2VF4GZP6VYVXJTFVOXTPS3BPFANCNFSM4HJBPMAA.


Handling MySQL & SQLite timestamp columns

PR Info

Resolve #344
Depends on

SeaQL/sea-query#197
launchbadge/sqlx#1581

Notes to MySQL User
MySQL user should use sea_orm:: DateTimeWithTimeZone for timestamp columns until SQLx upstream merged the PR and released it. Only after that happened, MySQL user could use sea_orm::DateTime for timestamp columns.

Hey @lz1998, could you please try this PR?
sea-orm = { version = "0.4.0", git = "https://github.com/SeaQL/sea-orm.git", branch = "issues/344", ... }

Hey @lz1998, could you please try this PR?
sea-orm = { version = "0.4.0", git = "https://github.com/SeaQL/sea-orm.git", branch = "issues/344", ... }

I have tried chrono::DateTimechrono::Utc and chrono::DateTimechrono::FixedOffset, but both failed.

Is your entity file similar to below? Defining the timestamp column with type DateTimeWithTimeZone.
use sea_orm::entity::prelude::*;

#[derive(Clone, Debug, PartialEq, DeriveEntityModel)]
#[sea_orm(table_name = "applog")]
pub struct Model {
    #[sea_orm(primary_key)]
    pub id: i32,
    pub action: String,
    pub json: Json,
    pub created_at: DateTimeWithTimeZone,
}

#[derive(Copy, Clone, Debug, EnumIter, DeriveRelation)]
pub enum Relation {}

impl ActiveModelBehavior for ActiveModel {}

I don't think MySQL can work with DateTimeWithTimeZone, there isn't a corresponding concept in MySQL.
The best bet is plain DateTime.

I don't think MySQL can work with DateTimeWithTimeZone, there isn't a corresponding concept in MySQL. The best bet is plain DateTime.

We cannot decode timestamp column into chrono::NaiveDateTime (for MySQL).
Could we just introduce two more DateTime (timestamp)?

chrono::DateTime<chrono::Utc> named DateTimeUtc
chrono::DateTime<chrono::Local> named DateTimeLocal

So this PR is not needed now?

So this PR is not needed now?

You mean we have to wait for upstream release? So we have to defer this PR?

So this PR is not needed now?

I think we should split this PR in half. And release the hotfix part now. MySQL user should use sea_orm:: DateTimeWithTimeZone for timestamp columns until SQLx upstream merged the PR and released it.
Only after that happened, MySQL user could use sea_orm::DateTime for timestamp columns.

Close as the SQLx PR is closed


What is differences between ReduxExample and NavigationPlayground?

What is differences between ReduxExample and NavigationPlayground?

When Should I use ReduxExample?
When Should I use NavigationPlayground?

@saeedhei they are both just example apps for you to play around with the code. You can use whichever one you want, but NavigationPlayground demonstrates a lot of different features and ReduxExample only demonstrates one feature, namely a redux integration.

Thank you @cooperka


Package cleanup

[x] Replace few stringr calls with base R
[x] Qualify package namespaces for non-imported functions
[ ] De-pipe single command pipes
[x] Remove final-line return() statements in functions

Fixed stringr issues with 256448d876ac08111420133a31fa62c313094b41

Ah, I was always unsure what to do (stylewise). Makes sense, thanks for the clarification.
That was definitely constructive and not negative critique :) Will try to change the returns tonight

I changed my mind about single-pipe lines, they're not my usual style but I've found I don't mind them when reading your code. :)
I cleaned up the return statements, but I also found this example of a really good reason to have a return(res) call at the end of add_color_join():
https://github.com/gadenbuie/tidy-animated-verbs/blob/256448d876ac08111420133a31fa62c313094b41/R/process_data_helpers.R#L143-L146


ISS-258 # Support Scenario annotation(low priority - user request)

Final bit in WIP_(In Progress) in this PR, but you can start reviewing...

solves #258


jek

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

No information provided or steps to replicate - Closing


Error on inline image using standard markdown notation

What happened?
I have a markdown file with an inline reference to an image. It looks like this:
![image-2.png](/obsidian/image-2.png)
when I try to generate the site or serve locally, I get the following error message:
ERROR 2022/02/16 13:17:04 [CONGO] Markdown image error in "obsidian/write-test.md": Resource "/obsidian/image-2.png" not found. Check the path is correct or remove the image from the content. Error: Error building site: logged 1 error(s)
I've tried putting the file in the correct static dir, and in the content dir, and cannot seem to make this work. I'm assuming this is Congo specific based on the error message, and when I test with a different theme (hugo-bearblog) the image renders correctly with no error messages.
Theme version
2.0.4
Hugo version
0.92.2
What browsers are you seeing the problem on?
No response
Relevant Hugo log output
`ERROR 2022/02/16 13:17:04 [CONGO] Markdown image error in "obsidian/write-test.md": Resource "/obsidian/image-2.png" not found. Check the path is correct or remove the image from the content.
Error: Error building site: logged 1 error(s)`

You never include the /, you use relative path. Relative to what? Either the directory your content is in, or the assets directory.
If the image is in the content directory content/obsidian (the same directory as write-test.md) you reference it just by name, hence image-2.png.
If you put it in assets/obsidian/image-2.png' you reference it by obsidian/image-2.png`.

That is not how I understand the documentation related to static file hosting here
By default, the static/ directory in the site project is used for all static files (e.g. stylesheets, JavaScript, images). The static files are served on the site root path (eg. if you have the file static/image.png you can access it using http://{server-url}/image.png, to include it in a document you can use ![Example image](/image.png) ).
In my case, the image file is in static/obsidian/image-2.png
Also, this is working just fine with other themes, and the error message above seems to originate from Congo, not Hugo. I was going to dig into it personally later, but thought I'd report it here.

Thanks for the issue report, however this is not a bug as this is the expected behaviour.
Version 2 of the theme uses Hugo Pipes to process images and as such they need to be supplied as assets, either in the assets/ directory or using page bundles. You cannot use standard Markdown syntax to include static image assets, however the figure shortcode does allow you to achieve the same behaviour, if required. You can read more about this functionality in the shortcode docs.
Just so I can understand more about your workflow, is there a particular reason you can't include these images in the page bundle?

I don't think there is any reason why I couldn't relocate the static image files to another directory for processing, I've just had this blog with hugo for a long time and would need to transition the files out of static and into assets I guess. I think I can also set the assetDir configuration to the static folder to test this out. I will try a few things a bit later.
I would of course like to use "standard markdown" (if there is such a thing) as much as possible rather than customize the posts for Hugo's implementation.

I thing what is happening is: your "figure shortcode" overwrite is breaking hugo's approach to  backwards compatibility, as well still current Static Files approach.
https://gohugo.io/content-management/static-files/

Yeah, @robotamer I think you're right. I have found that if I override _default/layout/render-image.html and replace the code at line 10:
  {{ with $.Page.Resources.GetMatch ($url.String) }}
with
 {{ with resources.Get ($url.String) }}
Then I can simply move everything from static to assets and my very old blog will work.
So, there probably needs to be an if statement here to first look for the image in the local directory so that it works with leaf bundles, and a fallback to look in the resources directory.

Thanks for the detailed comments on this issue. I've had a further look at this and agree that adding extra functionality so that resources can be found in both the assets directory and page bundles is a better user experience. Doing this also provides all the performance benefits of image scaling, etc. that the theme aims to achieve.
I'll make some changes in the next release to adjust this behaviour and hopefully it will improve the image handling in your use case.

I do really want to switch to 2.0 but I have 100+ inline image notations to replace. But I have another platforms reference the markdown files which doesn't support the shortcode. I have to maintain my version of Congo.


Do not call cargo test with --all-targets

The --all-targets flag for cargo test actually DISABLES doctests.
Doctests should of course be run, so removing the flag from the CI scrips.
There is a bug report for cargo about this behavior:
https://github.com/rust-lang/cargo/issues/6669
This fixes the changes done in #235 / 9a6c3bf9e5fdbf6c76a27534ee250628acf8e168.

bors r+

bors r+


Updates to Scala Kinesis Apps

This upgrades the Scala Kinesis apps to Scala 2.10.4, sbt 0.13.8 and sbt-assembly 0.13.0; it allows port specification in the kinesis-elasticsearch-sink config for the ES server; it resolves all the configuration files so that HOCON substitutions work; and it bumps each app's patch version by 1.
(I've also upgraded kinesis-elasticsearch-sink to use Elasticsearch 1.7.0, but feel free to pull that... it should build fine without it. And I've added a bin/ dir with a simple script to compile the Kinesis apps and move them to dist/, but it's probably not needed with the Vagrant setup.)
Let me know if separate PRs are better for these changes, and I'll create the patches.

Hey @jramos! Thanks for this. Two quick things:

We have a strict 1 ticket - 1 commit - 1 changelog entry setup for Snowplow commits these days, and tickets can't straddle multiple Kinesis apps. For this PR to go in, create a ticket for each piece of functionality in it per app and make sure there is a single commit in your PR which maps onto it. Check out this page of the commit history to see the approach: https://github.com/snowplow/snowplow/commits/master?page=2
Can you sign our CLA please - https://github.com/snowplow/snowplow/wiki/CLA

Will do. Thanks.

Thanks @jramos !


Element loose behavior after validation fails;

Greetings,
I have created a text limiter option form one of my fields and it stop working once the validation fails for that particular field.
Please see it running here:
http://jsfiddle.net/machadoug/kDCNA/1/
Thanks in advanced for your help.

I'm sorry for the lack of activity on this issue. Instead of leaving it open any longer, I decided to close old issues without trying to address them, to longer give the false impression that it will get addressed eventually, especially after several years with no activity. It doesn't mean I'm abandoning the project, just that I'm unable to work through 200+ open issues with the little time I can afford to spend on this project.
To the reporter (or anyone else interested in this issue): If you're still affected by the same issue, please consider opening a new issue, with a testpage that demonstrates the issue with a current version of the plugin. Even better, make an attempt to fix the issue yourself, and improve the project by sending a pull request. This may seem daunting at first, but you'll likely learn some useful skills that you can apply elsewhere as well. And you can help keep this project alive. We've documented how to do these things, too. A patch is worth a thousand issues!


[NATS] Enable secure connection

Description:
$subject
We need to enable,

Server Authentication (User/Password or Token)
Encrypting connection with TLS

Affected Versions:
0.991.0

Addressed with NATS client redesigning effort.
https://github.com/ballerina-platform/ballerina-lang/pull/16492


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit 1a9a79f:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-11-07-16-02-18 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-11-07-16-02-18

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix(provider): Reply with 404 whenever a manifest is received that has no leases

This changes the provider to send back 404 if the manifest is valid but there is no lease. I also added a test for this.

refs #999


phantom detection fails to detect 4th corner releases

While phantom detection correctly discards over threshold phantom touches on the 4th corner, it fails to detect 4th corner releases.

choose any 4 corners of a square and press them.
three will light up
release a lit one.
it does not unlight

This is a consequence of the phantom logic - the real (not phantom) 4th press keeps the 3rd over threshold.

Here follows a proposal for how to develop an algorithm to allow correct 4th corner detection.  In short, for a suspected 4th corner, re-scale Z by subtracting 50% the average of the 3 stronger corners, and then doubling the remaining load before applying threshold and calculating actual Z.  It's probably a bit more complex than that though.
Looking at the output from secret switch 3, it's clear that there is a significant signal from the 4th button, but the unpressed baseline and scale are modified compared to the first, second and third presses.
In other words, the signal exists to detect the 4th corner correctly, given an appropriate algorithm.
For example, with a Z reading of 1400 on the pressed 3 corners in a 4x3 square, the unpressed corner reads 700.  this is above threshold itself, but when the 4th corner is pressed, all 4 values leap to reach a value slightly larger than 1400.
Once a square has been formed, all 4 affect the others, so it's probably not necessary to track which one is the 4th.
If I could find a set standard weights in the pressure ranges appropriate, a linear model could be applied to the sensor readings to re-create the unbiased physical values from the measured ones.  The unpressed bias seems to be somewhere in the region of 30% and 50% of the pressed neighbours.
The bias changes with location over the grid; this is probably due to physical distance between the corners, but there may be an effect from absolute location on the grid.  The effect is relatively small compared to the main effect, so it may be possible to derive an improved algorithm while ignoring this factor.
Suggestions for a standardised mechanism for applying Z to cells would be appreciated.

finger in the air, the runtime cost of this extra evaluation should be comparable to the current cost of phantom tracking, which it would entirely replace.

First of all, did you properly calibrate your LinnStrument before digging into the phantom detection logic? If you just upload a custom firmware yourself, the calibration will be gone.

This leaves open the question of how to handle larger sets of intersections, but since they are already incorrectly handled, I think this is moot.
( I can create phantoms with 5 fingers in the position 1,2,4,8,9 of a 3x3 square )

@Geert <<First of all, did you properly calibrate your LinnStrument before digging into the phantom detection logic? >>
Thanks; good point that needed clarifying.  The issues detected are easy to demonstrate in a calibrated linnstrument, in debug mode with a custom firmware (only modifications were those I needed to compile in Arduino IDE).

I'm using 1.6.7 with the 1.6.4 SAM board installed.  All uses of char * should pretty much be const char *.
I also get build errors because selectSensorCell is not declared in a header.
I also get link errors because the arduino IDE tries to compile and link the contents of arduino_fixes and library.  moving them aside (after placing them in the appropriate places in the build system) addresses this.


font is foggy

VSCode Version: Code 1.7.2 (7ba55c5860b152d999dda59393ca3ebeb1b5c85f, 2016-11-21T22:06:37.428Z)
OS Version: Windows_NT ia32 10.0.14393
Extensions:

Extension
Author
Version

python
donjayamanne
0.5.5

Theme-Gooey
gerane
0.0.2

The word is foggy. my screen is 13.3 inch, and the resolution is 1080p, system scale is 150%.
Steps to Reproduce:

do not need.

@er3456qi
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders

A number of days has past without answer on the questions asked. I am thereby going to close this issue to clean up our backlog of issues. Once you can answer on the questions, the issue can be reopened again. Thanks for understanding this process!


Get balance stream

I'd like to get a stream of balance for an address. DRC has that functionality.
The closest thing DU has is contract-state-stream, but that's for contracts only and comes with a lot of other info you might not need.

That's a great idea, I'm going to make this one of the TODOs for the conference. That means this should be operational within 2 weeks time.

If you want to start it, feel free.

@adrianmcli Yea, I'll start it.

@adrianmcli Take a look at https://github.com/trufflesuite/drizzle-utils/tree/feature/get-balance-stream. Having some trouble getting the balance test to actually run.
I did a npm test of the entire repo and seems like there's a lot of failing tests, not sure if something's wrong with the test initialization or not.

The tests seem to work fine, with the exception of the balance checking test "can track balance of addresses":
Error: expect(received).toEqual(expected)

Difference:

- Expected
+ Received

  Array [
-   "0",
+   "98999958000000000000",
  ]

By default, a Ganache test chain will put 99 ETH into the first 10 accounts I believe. Maybe this is the issue?

Odd, I couldn't even get to that stage @adrianmcli, perhaps I'll wipe my node_modules and try again

Fixed the issue, PR is up


Unexpected results

Dear @jingyuanli001 , I tried to train a model using the places2 dataset. After I have trained for approximately 750,000 iterations (batch size 9 using 3 GPUs; size 384), then I extracted the checkpoint and test it on the coco dataset. I'm getting unsatisfactory results. Why do you think there are obvious "lime water" effects around the masked regions?
The testing masks and the training masks are the same.

Hi, have you fine-tuned the model following the procedure in the readme file? The distorted color is very likely to come from inadequate fine-tuning. Fine-tuning his very very important here because during fine-tuning, we stopped updating the parameters for batch-normalization which is not stable due to the unpredictable mask region.

I have not started the finetuning stage yet. Ok, I will follow your instructions to finetune soon. Thank you so much for your swift response and help.

Dear @jingyuanli001 ,
This is what I got when saving the batch every 200 iterations during training. So, training results looks good, but testing results is totally different. So, you could be right in the batchnorm parameters being unstable. I will start finetune soon and update you.

Dear @jingyuanli001 ,
This is what I got when saving the batch every 200 iterations during training. So, training results looks good, but testing results is totally different. So, you could be right in the batchnorm parameters being unstable. I will start finetune soon and update you.

Yes, this is what we also observed when we were developing our method. During training, the statistic used to normalize the feature map is calculated dynamically based on the instances in the batch, and then it can be considered to be (almost) accurate. However, during testing, the statistic used for normalization is the one recorded during training, and is not calculated from the testing images, and thus it is inaccurate. This then leads to the bad results. So the fine-tuning procedure is actually asking the model to "get familiar with" the fixed statistics that will be used for testing. In fact, I personally consider the batch normalization scheme here to be suboptimal and there should have some better normalization schemes.

Dear @jingyuanli001 , you were obsolutely right! Fixing the batchnorm parameters helped solved even with just 10k iterations. The following are testing samples at 780,000 iterations. Thank you so much for your help, and good job in the paper. I really like the idea of working inwards from the border with partial convolution and recurrence.

Thanks for your code. I download the official celeba weights and directly test the model, but obtain unexpected results (like the model w/o fine-tuning). Did I miss something?


[AMBARI-25261]: hdfs_to_onefs_convert.py script should have Ambari Serv…

What changes were proposed in this pull request?
OneFS only works with Ambari 2.7.1+, not Ambari 2.7.0. The hdfs_to_onefs_convert.py script should be updated to say so. This fix updates the text to '... Ambari must be upgraded to >=v2.7.1'
How was this patch tested?
I ran hdfs_to_onefs_convert.py with a dummy option in order to see text change. I did not test the upgrade as the change is text only to inform user about prerequisites.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/5158/
Test PASSed.

@zeroflag please review


Mautic 3.0 changes: updated console directory

⚠ Not to be merged until Mautic 3.x is launched
Console was moved to another directory. Updated all paths and replace app/console with bin/console.

Thanks for approving this PR, @RCheesley. Just added two new commits for Mautic 3.0 updates to this PR.
As a part of these commits, I updated the What's New doc with user-facing changes for Mautic 3.0. Please review and provide feedback.


Setting key "net.ipv6.conf.default.forwarding": Read-only file system

After running this
docker run --volumes-from $OVPN_DATA -d -p 1194:1194/udp --cap-add=NET_ADMIN kylemanna/openvpn

i got this error in docker logs
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
Enabling IPv6 Forwarding
sysctl: setting key "net.ipv6.conf.default.forwarding": Read-only file system

I using DigitalOcean's Ubuntu 14.04 LTS
ufw default allow

Enable this settings in /etc/ufw/sysctl.conf does nothing change
net/ipv4/ip_forward=1
net/ipv6/conf/default/forwarding=1
net/ipv6/conf/all/forwarding=1

Sorry about that, broke it when I merged IPv6 support. Try doing a docker pull on the image and try it again.

Out of curiosity did you get it working?

Yep! After second try, all working perfect! Thank you very much!

Yeah, that was my fault.  Sounds like you hit an edge case with IPv6 enabled that I didn't test for. Oops.  Glad it's working. :smile:

I'm getting pretty much the same error with the latest docker-openvpn on Ubuntu 16.04 LTS
 docker-compose up
Recreating openvpn_openvpn_1
Attaching to openvpn_openvpn_1
openvpn_1  | Enabling IPv6 Forwarding
openvpn_1  | Failed to enable IPv6 Forwarding default
openvpn_1  | Failed to enable IPv6 Forwarding
openvpn_1  | iptables: No chain/target/match by that name.
openvpn_1  | iptables: No chain/target/match by that name.
openvpn_1  | sysctl: error setting key 'net.ipv6.conf.default.forwarding': Read-only file system
openvpn_1  | sysctl: error setting key 'net.ipv6.conf.all.forwarding': Read-only file system
openvpn_1  | Fri May 20 13:01:35 2016 RESOLVE: Cannot parse IP address: server
openvpn_1  | Options error: error parsing --server parameters
openvpn_1  | Use --help for more information.
openvpn_openvpn_1 exited with code 1

Maybe something has changed with the new Ubuntu version? Or is it maybe my fault that this happens?

A privileged: true solved at least the "Read only" problem. The error that still persists is:
openvpn_1  | Fri May 20 13:01:35 2016 RESOLVE: Cannot parse IP address: server
openvpn_1  | Options error: error parsing --server parameters

Not sure what this is about?

@kylemanna is there a clean way to disable IPv6 Forwarding, to remove the warnings?
As for the necrotic post:
I'm opening the conversation on this issue because it is the first hit on Google.

Resolved the issue: Found the IPv6 conditional-statement in ovpn_run.
Solution: Disable IPv6 on the host.
REF: http://www.techrepublic.com/article/how-to-disable-ipv6-on-linux/

how can I run ipv6 without privileged mode having to be enabled? Running 2.4+.

according to new stndards, ipv6 is the default protocol that is used in most recent linux distributions.
If /etc/gai.conf exists, it could mean that its been modified to give precence to ipv4 and could be why ipv4 is used. It could also be for a huge amount of other network related configs, too. google for it or show us/me its content if you wanted to make sure. It shouldnt contain sensitive informations but make sure you anonymize them before doing so.
Firewall configs could also prevent  ipv6 from being used under certain conditions. ´sudo ip6tables -S’ would show you the configs.
and oh, yes... the sysctl configs for ipv6 must allow for it, too.
if you have no access to the server as root, there is almost no chances you can control networking behaviors.
note: i replied quickly without really being aware of the whole discussion so please forgive me if i am way out of context.

still an issue, april 2019. how do you fix the read-only errors?
# docker run -v $OVPN_DATA:/etc/openvpn -d -p 1194:1194/udp --cap-add=NET_ADMIN kylemanna/openvpn
fb5ce10241c2efa3bef874abb2717d0c68c00420f4b0f1256f23ee7914157c3e
root@blacklion:/etc/openvpn#
root@blacklion:/etc/openvpn# docker logs fb5
iptables: No chain/target/match by that name.
iptables: No chain/target/match by that name.
Enabling IPv6 Forwarding
sysctl: error setting key 'net.ipv6.conf.all.disable_ipv6': Read-only file system
Failed to enable IPv6 support
sysctl: error setting key 'net.ipv6.conf.default.forwarding': Read-only file system
Failed to enable IPv6 Forwarding default
sysctl: error setting key 'net.ipv6.conf.all.forwarding': Read-only file system
Failed to enable IPv6 Forwarding
Running 'openvpn --config /etc/openvpn/openvpn.conf --client-config-dir /etc/openvpn/ccd --crl-verify /etc/openvpn/crl.pem '

@utdrmac read this https://github.com/kylemanna/docker-openvpn/issues/56#issuecomment-418587287
# If this fails, ensure the docker container is run with --privileged […]


librenms: We need to know if there are "Validate Config" issues

In GitLab by @markuslf on Sep 22, 2021, 10:12

Like in the Web-Interface:
sudo -u librenms /opt/librenms/validate.php -g configuration
sudo -u librenms /opt/librenms/validate.php -g database
...
sudo -u librenms /opt/librenms/validate.php -g updates
sudo -u librenms /opt/librenms/validate.php -g user

including mail, distributed poller and rrdcheck.


Setup Publishing Pipeline

I added a pipeline to automatically commit the executed notebooks (generated by the tests) to the branch gh-pages. From there, they are automatically deployed to qutip.github.io. Also the publishing only occurs if all notebooks passed the tests.

I activated gh-pages for this repo and the notebook should appear at https://qutip.org/qutip-tutorials.

Maybe this is not the right PR to mention this. I just want to comment that for Qcircuit plotting you can also refer to the installation guide https://qutip-qip.readthedocs.io/en/stable/installation.html#additional-software-for-plotting-circuits

Maybe this is not the right PR to mention this. I just want to comment that for Qcircuit plotting you can also refer to the installation guide https://qutip-qip.readthedocs.io/en/stable/installation.html#additional-software-for-plotting-circuits

I will add the software to the Action Setup once we have notebooks requiring that installation. I will also refer to that in the Readme. Thanks!


SAM2Ultra

When I use the SAM2Ultra node, it automatically downloads the models--hustvl--vitmatte-small-composition-1k to the .cache\huggingface cache directory. If I don’t want it to be stored in the cache directory, where should I place the 'config.json', 'model.safetensors', and 'preprocessor_config.json' files in the ComfyUI\models folder? I have read the readme in your repository, but there is no mention of this issue.

This section is missing from the Readme:

Some nodes named "Ultra" will use the vitmatte model, download the vitmatte model and copy to ComfyUI/models/vitmatte folder, it is also included in the download link above.

This section is missing from the Readme:

Some nodes named "Ultra" will use the vitmatte model, download the vitmatte model and copy to ComfyUI/models/vitmatte folder, it is also included in the download link above.

It’s strange—I’ve already downloaded these three files and placed them in the ComfyUI\models\vitmatte folder, but when running the Ultra node, it still tries to download them to the ComfyUI\.cache\huggingface cache directory.

It’s strange—I’ve already downloaded these three files and placed them in the ComfyUI\models\vitmatte folder, but when running the Ultra node, it still tries to download them to the ComfyUI\.cache\huggingface cache directory.

There are indeed some issues with the model loading code, which have been fixed. Please update and try again

It’s strange—I’ve already downloaded these three files and placed them in the ComfyUI\models\vitmatte folder, but when running the Ultra node, it still tries to download them to the ComfyUI\.cache\huggingface cache directory.

There are indeed some issues with the model loading code, which have been fixed. Please update and try again

Thank you, the issue has been fixed.


fixer-return should (optionally?) only require it sometimes returns a value

The rule guards against people forgetting to return their fixers, e.g.
// Invalid
fix: function( fixer ) {
  fixer.replaceText( node, 'foo' );
}

However it is common that a fixer can only fix a subset of cases, and so only conditionally returns:
// Valid
fix: function( fixer ) {
  if ( node.arguments.length ) {
    return fixer.replaceText( node, 'foo' );
  }
}

It should be possible to consider the above valid, while also warning about the first example.

you should really return null in those cases.
Implicitly returning undefined is a bad coding practice.

Surely it should be up to consistent-return to decide that?

I'm strongly against that code style as I think it's a real source of bugs and potential problems.
I don't think this a good inclusion in the rule as it can be very easy for people to forget to return things, esp with the complex branching and conditional logic fixers can have.
fix(fixer) {
  const fixes = [];
  fixes.push(doFix1();
  // ...

  if (someCond) {
    fixes.push(doFixN());
    return fixes;
  }

  // oops forgot to return fixes, now the code that didn't satisfy someCond didn't get a fix!
}

My point is that you can enforce your preference with consistent-return. For those who prefer not to turn on consistent-return this rule overrides their preference.

This rule has a type of problem and we only know there is a problem if the code never returns. Anything else is a code-style suggestion and therefore better handled by another rule (consistent-return is type suggestion).

my point is that this rule is about ensuring that you return the fixer object so that eslint provide the fix.
it should work independent of consistent-return.
in your specific example, the fixer is a small, simple case and it's easy to see that the fixer is correct.
However there are many fixer that are not that simple, and this rule needs to handle all cases appropriately. IMO it is better to err on the safer side to help catch accidentally broken fixers.
If you want to have a simple fixer like your example, you could also just omit the fix function for your case:
context.report({
  ...stuff,
  fix: !node.arguments.length
    ? null
    : function( fixer ) {
      return fixer.replaceText( node, 'foo' );
    },
});

This code is much clearer - it very clearly communicates the intention that you do not want any fixes if the length is falsy.

closing as fixed.


Allow greater than 128 potion ids

Some mods like NotEnoughIDs extends id limits. It would be nice if I could move Aura Cascade's potion ids over 128, and enchantment ids over 256.

No longer relavent in 1.9


Update TypicalCase_Qwen.md

PR Docs
无
PR APIs
修复docs格式问题

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