Flutter Test Task

Hello! I need help running Flutter Test Task
For some odd reason, it shows the message ->  All tests passed!    and then -> ##[error]Some tests failed
I don't understand why.
Here is how I run Flutter Test:
      - task: FlutterTest@0
        inputs:
          projectDirectory: '$(root)'
          generateCodeCoverageReport: true

Here is the output:
01:42 +61: D:\a\1\s\test\utils\getting_user_profile_test.dart: Should return CurrentUserRole.notAvailable profile if current user is not available
01:42 +61: All tests passed!
##[debug]Exit code 1 received from tool 'C:\hostedtoolcache\windows\Flutter\3.0.5\windows\flutter\bin\flutter.bat'
##[debug]STDIO streams have closed for tool 'C:\hostedtoolcache\windows\Flutter\3.0.5\windows\flutter\bin\flutter.bat'
##[debug]results: {"isSuccess":false,"suites":[{"title":"remote_vehicle_workshop_model_test","isSuccess":false,"succeeded":5,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\app_update\\local_launch_app_store_test.dart: should call upgrader method onUserUpdated with proper arguments","isSuccess":true,"started":"2023-02-13T13:28:58.888Z","ended":"2023-02-13T13:28:58.888Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\app_update\\local_launch_app_store_test.dart: should call upgrader method onUserUpdated with proper arguments","isSuccess":true,"started":"2023-02-13T13:28:58.888Z","ended":"2023-02-13T13:28:58.888Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\app_update\\local_launch_app_store_test.dart: should call upgrader method onUserUpdated with proper arguments","isSuccess":true,"started":"2023-02-13T13:28:58.888Z","ended":"2023-02-13T13:28:58.933Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\app_update\\local_launch_app_store_test.dart: should call upgrader method onUserUpdated with proper arguments","isSuccess":true,"started":"2023-02-13T13:28:58.933Z","ended":"2023-02-13T13:28:58.993Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\app_update\\local_launch_app_store_test.dart: should throw DomainError.unexpected when upgrader throws an Exception","isSuccess":true,"started":"2023-02-13T13:28:58.993Z","ended":"2023-02-13T13:28:58.993Z"}]},{"title":"remote_is_update_available_test","isSuccess":false,"succeeded":7,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\app_update\\remote_is_update_available_test.dart: should call isUpdateAvailable method from upgrader","isSuccess":true,"started":"2023-02-13T13:29:09.404Z","ended":"2023-02-13T13:29:09.464Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\app_update\\remote_is_update_available_test.dart: should call isUpdateAvailable method from upgrader","isSuccess":true,"started":"2023-02-13T13:29:09.464Z","ended":"2023-02-13T13:29:09.524Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\app_update\\remote_is_update_available_test.dart: should throw DomainError.unexpected when upgrader throws an Exception","isSuccess":true,"started":"2023-02-13T13:29:09.524Z","ended":"2023-02-13T13:29:09.524Z"}]},{"title":"remote_login_test","isSuccess":false,"succeeded":11,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\authentication\\remote_login_test.dart: Should call HttpClient with correct values","isSuccess":true,"started":"2023-02-13T13:29:10.544Z","ended":"2023-02-13T13:29:10.754Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\authentication\\remote_login_test.dart: Should call HttpClient with correct values","isSuccess":true,"started":"2023-02-13T13:29:10.754Z","ended":"2023-02-13T13:29:10.769Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\authentication\\remote_login_test.dart: Should return correct accessToken from jsonResponse","isSuccess":true,"started":"2023-02-13T13:29:10.769Z","ended":"2023-02-13T13:29:10.784Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\authentication\\remote_login_test.dart: Should return an AuthResultEntity if authLoginIsCalled","isSuccess":true,"started":"2023-02-13T13:29:10.784Z","ended":"2023-02-13T13:29:10.814Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\authentication\\remote_login_test.dart: Should return DomainError on HttpError.unauthorized","isSuccess":true,"started":"2023-02-13T13:29:10.814Z","ended":"2023-02-13T13:29:10.814Z"}]},{"title":"remote_fetch_client_details_test","isSuccess":false,"succeeded":15,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\clients\\remote_fetch_client_details_test.dart: should make a get request on proper url","isSuccess":true,"started":"2023-02-13T13:29:17.085Z","ended":"2023-02-13T13:29:17.160Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\clients\\remote_fetch_client_details_test.dart: should make a get request on proper url","isSuccess":true,"started":"2023-02-13T13:29:17.160Z","ended":"2023-02-13T13:29:17.175Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\clients\\remote_fetch_client_details_test.dart: should return a ClientDetailsEntity","isSuccess":true,"started":"2023-02-13T13:29:17.175Z","ended":"2023-02-13T13:29:17.190Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\clients\\remote_fetch_client_details_test.dart: should throw a DomainError when request throws an HttpError","isSuccess":true,"started":"2023-02-13T13:29:17.190Z","ended":"2023-02-13T13:29:17.220Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\clients\\remote_fetch_client_details_test.dart: should throw a ModelError when request returns invalid data","isSuccess":true,"started":"2023-02-13T13:29:17.220Z","ended":"2023-02-13T13:29:17.220Z"}]},{"title":"remote_fetch_maintenance_plan_test","isSuccess":false,"succeeded":19,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\maintenance_plan\\remote_fetch_maintenance_plan_test.dart: should make a get request on proper url","isSuccess":true,"started":"2023-02-13T13:29:18.360Z","ended":"2023-02-13T13:29:18.450Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\maintenance_plan\\remote_fetch_maintenance_plan_test.dart: should make a get request on proper url","isSuccess":true,"started":"2023-02-13T13:29:18.450Z","ended":"2023-02-13T13:29:18.495Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\maintenance_plan\\remote_fetch_maintenance_plan_test.dart: should return a list of String","isSuccess":true,"started":"2023-02-13T13:29:18.495Z","ended":"2023-02-13T13:29:18.525Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\maintenance_plan\\remote_fetch_maintenance_plan_test.dart: should throw a DomainError when request throws an HttpError","isSuccess":true,"started":"2023-02-13T13:29:18.525Z","ended":"2023-02-13T13:29:18.600Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\maintenance_plan\\remote_fetch_maintenance_plan_test.dart: should throw a ModelError when request returns invalid data","isSuccess":true,"started":"2023-02-13T13:29:18.600Z","ended":"2023-02-13T13:29:18.600Z"}]},{"title":"remote_maintenance_status_test","isSuccess":false,"succeeded":21,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\maintenance_status\\remote_maintenance_status_test.dart: should return bool when api returns success","isSuccess":true,"started":"2023-02-13T13:29:25.368Z","ended":"2023-02-13T13:29:25.473Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\maintenance_status\\remote_maintenance_status_test.dart: should return bool when api returns success","isSuccess":true,"started":"2023-02-13T13:29:25.473Z","ended":"2023-02-13T13:29:25.488Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\maintenance_status\\remote_maintenance_status_test.dart: should throw an DomainError when request throws an HttpError","isSuccess":true,"started":"2023-02-13T13:29:25.488Z","ended":"2023-02-13T13:29:25.488Z"}]},{"title":"load_onboarding_visualization_test","isSuccess":false,"succeeded":27,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should call fetchSecure with correct values AppCacheKeys.onboardingEntities","isSuccess":true,"started":"2023-02-13T13:29:26.523Z","ended":"2023-02-13T13:29:26.584Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should call fetchSecure with correct values AppCacheKeys.onboardingEntities","isSuccess":true,"started":"2023-02-13T13:29:26.584Z","ended":"2023-02-13T13:29:26.598Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should call sut usecase with correct values AppCacheKeys.onboardingEntities when calling sut","isSuccess":true,"started":"2023-02-13T13:29:26.598Z","ended":"2023-02-13T13:29:26.598Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should return list of OnboardingVisualizationEntity","isSuccess":true,"started":"2023-02-13T13:29:26.598Z","ended":"2023-02-13T13:29:26.613Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should return an non empty list of OnboardingVisualizationEntity","isSuccess":true,"started":"2023-02-13T13:29:26.613Z","ended":"2023-02-13T13:29:26.613Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should return list of OnboardingVisualizationEntity with correct values","isSuccess":true,"started":"2023-02-13T13:29:26.613Z","ended":"2023-02-13T13:29:26.658Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should throw ModelError if incorrect json was loaded","isSuccess":true,"started":"2023-02-13T13:29:26.658Z","ended":"2023-02-13T13:29:26.658Z"}]},{"title":"save_onboarding_visualization_test","isSuccess":false,"succeeded":29,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\save_onboarding_visualization_test.dart: Should call saveSecure with correct values AppCacheKeys.onboardingEntities","isSuccess":true,"started":"2023-02-13T13:29:32.634Z","ended":"2023-02-13T13:29:32.694Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\save_onboarding_visualization_test.dart: Should call saveSecure with correct values AppCacheKeys.onboardingEntities","isSuccess":true,"started":"2023-02-13T13:29:32.694Z","ended":"2023-02-13T13:29:32.709Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\save_onboarding_visualization_test.dart: Should load LocalLoadOnboardingVisualization with correct values","isSuccess":true,"started":"2023-02-13T13:29:32.709Z","ended":"2023-02-13T13:29:32.709Z"}]},{"title":"remote_fetch_service_specialty_test","isSuccess":false,"succeeded":33,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_specialty_test.dart: should make a get request on proper url","isSuccess":true,"started":"2023-02-13T13:29:33.654Z","ended":"2023-02-13T13:29:33.759Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_specialty_test.dart: should make a get request on proper url","isSuccess":true,"started":"2023-02-13T13:29:33.759Z","ended":"2023-02-13T13:29:33.759Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_specialty_test.dart: should return a list of ServiceSpecialtyEntity","isSuccess":true,"started":"2023-02-13T13:29:33.759Z","ended":"2023-02-13T13:29:33.804Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_specialty_test.dart: should throw a DomainError when request throws an HttpError","isSuccess":true,"started":"2023-02-13T13:29:33.804Z","ended":"2023-02-13T13:29:33.879Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_specialty_test.dart: should throw a ModelError when request returns invalid data","isSuccess":true,"started":"2023-02-13T13:29:33.879Z","ended":"2023-02-13T13:29:33.879Z"}]},{"title":"remote_fetch_service_status_test","isSuccess":false,"succeeded":37,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_status_test.dart: should make a get request on proper url","isSuccess":true,"started":"2023-02-13T13:29:40.211Z","ended":"2023-02-13T13:29:40.271Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_status_test.dart: should make a get request on proper url","isSuccess":true,"started":"2023-02-13T13:29:40.271Z","ended":"2023-02-13T13:29:40.286Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_status_test.dart: should return a list of ServiceTypeEntity","isSuccess":true,"started":"2023-02-13T13:29:40.286Z","ended":"2023-02-13T13:29:40.301Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_status_test.dart: should throw a DomainError when request throws an HttpError","isSuccess":true,"started":"2023-02-13T13:29:40.301Z","ended":"2023-02-13T13:29:40.331Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_status_test.dart: should throw a ModelError when request returns invalid data","isSuccess":true,"started":"2023-02-13T13:29:40.331Z","ended":"2023-02-13T13:29:40.331Z"}]},{"title":"remote_fetch_service_types_test","isSuccess":false,"succeeded":41,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_types_test.dart: should make a get request on proper url","isSuccess":true,"started":"2023-02-13T13:29:41.636Z","ended":"2023-02-13T13:29:41.696Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_types_test.dart: should make a get request on proper url","isSuccess":true,"started":"2023-02-13T13:29:41.696Z","ended":"2023-02-13T13:29:41.696Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_types_test.dart: should return a list of ServiceTypeEntity","isSuccess":true,"started":"2023-02-13T13:29:41.696Z","ended":"2023-02-13T13:29:41.711Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_types_test.dart: should throw a DomainError when request throws an HttpError","isSuccess":true,"started":"2023-02-13T13:29:41.711Z","ended":"2023-02-13T13:29:41.756Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_types_test.dart: should throw a ModelError when request returns invalid data","isSuccess":true,"started":"2023-02-13T13:29:41.756Z","ended":"2023-02-13T13:29:41.756Z"}]},{"title":"remote_solicitation_details_test","isSuccess":false,"succeeded":45,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\solicitation_details\\remote_solicitation_details_test.dart: should call client method get with proper url","isSuccess":true,"started":"2023-02-13T13:29:47.217Z","ended":"2023-02-13T13:29:47.307Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\solicitation_details\\remote_solicitation_details_test.dart: should call client method get with proper url","isSuccess":true,"started":"2023-02-13T13:29:47.307Z","ended":"2023-02-13T13:29:47.322Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\solicitation_details\\remote_solicitation_details_test.dart: should return an NewUserCouponEntity with proper data","isSuccess":true,"started":"2023-02-13T13:29:47.322Z","ended":"2023-02-13T13:29:47.337Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\solicitation_details\\remote_solicitation_details_test.dart: should rethrow HttpError when request fails","isSuccess":true,"started":"2023-02-13T13:29:47.337Z","ended":"2023-02-13T13:29:47.367Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\solicitation_details\\remote_solicitation_details_test.dart: should rethrow invalidData when data is invalid","isSuccess":true,"started":"2023-02-13T13:29:47.367Z","ended":"2023-02-13T13:29:47.367Z"}]},{"title":"remote_update_kilometers_driver_test","isSuccess":false,"succeeded":47,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicle\\remote_update_kilometers_driver_test.dart: should call the proper url","isSuccess":true,"started":"2023-02-13T13:29:48.642Z","ended":"2023-02-13T13:29:48.717Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicle\\remote_update_kilometers_driver_test.dart: should call the proper url","isSuccess":true,"started":"2023-02-13T13:29:48.717Z","ended":"2023-02-13T13:29:48.747Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicle\\remote_update_kilometers_driver_test.dart: should throw a DomainError when request fails","isSuccess":true,"started":"2023-02-13T13:29:48.747Z","ended":"2023-02-13T13:29:48.747Z"}]},{"title":"remote_fetch_vehicles_test","isSuccess":false,"succeeded":52,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicles_test.dart: should call client method get with proper url and plate is empty","isSuccess":true,"started":"2023-02-13T13:29:54.252Z","ended":"2023-02-13T13:29:54.328Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicles_test.dart: should call client method get with proper url and plate is empty","isSuccess":true,"started":"2023-02-13T13:29:54.328Z","ended":"2023-02-13T13:29:54.328Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicles_test.dart: should call client method get with proper url and plate is not empty","isSuccess":true,"started":"2023-02-13T13:29:54.328Z","ended":"2023-02-13T13:29:54.343Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicles_test.dart: should return List VehicleDetailsEntity with correct data","isSuccess":true,"started":"2023-02-13T13:29:54.343Z","ended":"2023-02-13T13:29:54.343Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicles_test.dart: should rethrow HttpError when request fails","isSuccess":true,"started":"2023-02-13T13:29:54.343Z","ended":"2023-02-13T13:29:54.388Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicles_test.dart: should throw remoteParseData error when cant parse data","isSuccess":true,"started":"2023-02-13T13:29:54.388Z","ended":"2023-02-13T13:29:54.388Z"}]},{"title":"remote_fetch_vehicle_drivers_test","isSuccess":false,"succeeded":57,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicle_drivers_test.dart: should call the proper url and return a list of VehicleDriverEntity","isSuccess":true,"started":"2023-02-13T13:29:55.543Z","ended":"2023-02-13T13:29:55.633Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicle_drivers_test.dart: should call the proper url and return a list of VehicleDriverEntity","isSuccess":true,"started":"2023-02-13T13:29:55.633Z","ended":"2023-02-13T13:29:55.663Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicle_drivers_test.dart: should return the correct list of VehicleDriverEntity","isSuccess":true,"started":"2023-02-13T13:29:55.663Z","ended":"2023-02-13T13:29:55.768Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicle_drivers_test.dart: should throw a DomainError when returned data is invalid","isSuccess":true,"started":"2023-02-13T13:29:55.768Z","ended":"2023-02-13T13:29:55.858Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicle_drivers_test.dart: should throw a DomainError when returned data has invalid types","isSuccess":true,"started":"2023-02-13T13:29:55.858Z","ended":"2023-02-13T13:29:55.873Z"},{"title":"D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicle_drivers_test.dart: should throw a DomainError when request fails","isSuccess":true,"started":"2023-02-13T13:29:55.873Z","ended":"2023-02-13T13:29:55.873Z"}]},{"title":"getting_user_profile_test","isSuccess":false,"succeeded":61,"failed":0,"cases":[{"title":"D:\\a\\1\\s\\test\\utils\\getting_user_profile_test.dart: Should return CurrentUserRole.driverProfile profile if current user is an driver","isSuccess":true,"started":"2023-02-13T13:30:01.927Z","ended":"2023-02-13T13:30:01.957Z"},{"title":"D:\\a\\1\\s\\test\\utils\\getting_user_profile_test.dart: Should return CurrentUserRole.driverProfile profile if current user is an driver","isSuccess":true,"started":"2023-02-13T13:30:01.957Z","ended":"2023-02-13T13:30:01.973Z"},{"title":"D:\\a\\1\\s\\test\\utils\\getting_user_profile_test.dart: Should return CurrentUserRole.driverApprover profile if current user is an driver Approver","isSuccess":true,"started":"2023-02-13T13:30:01.973Z","ended":"2023-02-13T13:30:01.973Z"},{"title":"D:\\a\\1\\s\\test\\utils\\getting_user_profile_test.dart: Should return CurrentUserRole.fleetAdmin profile if current user is an admin","isSuccess":true,"started":"2023-02-13T13:30:01.973Z","ended":"2023-02-13T13:30:01.973Z"},{"title":"D:\\a\\1\\s\\test\\utils\\getting_user_profile_test.dart: Should return CurrentUserRole.notAvailable profile if current user is not available","isSuccess":true,"started":"2023-02-13T13:30:01.973Z","ended":"2023-02-13T13:30:01.973Z"}]}]}
##[debug]TestManagement.Server.UsePublishTestResultsLibInAgent is on
##[debug]Object of TestLogStore created.
Result Attachments will be stored in LogStore
##[debug]Object of TestResultsPublisher created.
##[debug]Object of TestLogStore created.
Run Attachments will be stored in LogStore
##[debug]Object of TestRunPublisher created.
##[debug]Object of TestLogStore created.
##[debug]Object of JUnitResultParser created.
##[debug]Entering ParseTestResultFiles
##[debug]runContext.ReleaseURI is null
##[debug]runContext.ReleaseEnvironmentUri is null
##[debug]Reading test results from file 'D:\a\1\s\junit.xml'.
##[debug]Total test results: 76.
##[debug]Leaving ParseTestResultFiles
##[debug]runContext.ReleaseURI is null
##[debug]runContext.ReleaseEnvironmentUri is null
##[debug]Processed: ##vso[results.publish type=JUnit;mergeResults=false;runTitle=VSTS - Flutter;publishRunAttachments=true;resultFiles=D:\a\1\s\junit.xml;testRunSystem=VSTSTask;]
##[debug]task result: Failed
##[debug]Uploading build level attachements individually
##[debug]Entering PublishToNewTestRunPerTestResultFileAsync
##[error]Some tests failed

Do you know how I can correct it?
Thank you!

If you check the json result of the tests. All "isSuccess" is "false". You could have some tests silently failing. It has happened to me personally before on Flutter as well as on Angular tests.
You should run the tests locally and compare the results. This could tell us what is wrong and where.
Incase, if local is ok then can you try running the extension task with "coverage" set as "false" and see if it still passes. Also, try running the command directly from "powershel/command task" or "flutter command task".
{
  "isSuccess": false,
  "suites": [
    {
      "title": "remote_vehicle_workshop_model_test",
      "isSuccess": false,
      "succeeded": 5,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\app_update\\local_launch_app_store_test.dart: should call upgrader method onUserUpdated with proper arguments",
          "isSuccess": true,
          "started": "2023-02-13T13:28:58.888Z",
          "ended": "2023-02-13T13:28:58.888Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\app_update\\local_launch_app_store_test.dart: should call upgrader method onUserUpdated with proper arguments",
          "isSuccess": true,
          "started": "2023-02-13T13:28:58.888Z",
          "ended": "2023-02-13T13:28:58.888Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\app_update\\local_launch_app_store_test.dart: should call upgrader method onUserUpdated with proper arguments",
          "isSuccess": true,
          "started": "2023-02-13T13:28:58.888Z",
          "ended": "2023-02-13T13:28:58.933Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\app_update\\local_launch_app_store_test.dart: should call upgrader method onUserUpdated with proper arguments",
          "isSuccess": true,
          "started": "2023-02-13T13:28:58.933Z",
          "ended": "2023-02-13T13:28:58.993Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\app_update\\local_launch_app_store_test.dart: should throw DomainError.unexpected when upgrader throws an Exception",
          "isSuccess": true,
          "started": "2023-02-13T13:28:58.993Z",
          "ended": "2023-02-13T13:28:58.993Z"
        }
      ]
    },
    {
      "title": "remote_is_update_available_test",
      "isSuccess": false,
      "succeeded": 7,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\app_update\\remote_is_update_available_test.dart: should call isUpdateAvailable method from upgrader",
          "isSuccess": true,
          "started": "2023-02-13T13:29:09.404Z",
          "ended": "2023-02-13T13:29:09.464Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\app_update\\remote_is_update_available_test.dart: should call isUpdateAvailable method from upgrader",
          "isSuccess": true,
          "started": "2023-02-13T13:29:09.464Z",
          "ended": "2023-02-13T13:29:09.524Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\app_update\\remote_is_update_available_test.dart: should throw DomainError.unexpected when upgrader throws an Exception",
          "isSuccess": true,
          "started": "2023-02-13T13:29:09.524Z",
          "ended": "2023-02-13T13:29:09.524Z"
        }
      ]
    },
    {
      "title": "remote_login_test",
      "isSuccess": false,
      "succeeded": 11,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\authentication\\remote_login_test.dart: Should call HttpClient with correct values",
          "isSuccess": true,
          "started": "2023-02-13T13:29:10.544Z",
          "ended": "2023-02-13T13:29:10.754Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\authentication\\remote_login_test.dart: Should call HttpClient with correct values",
          "isSuccess": true,
          "started": "2023-02-13T13:29:10.754Z",
          "ended": "2023-02-13T13:29:10.769Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\authentication\\remote_login_test.dart: Should return correct accessToken from jsonResponse",
          "isSuccess": true,
          "started": "2023-02-13T13:29:10.769Z",
          "ended": "2023-02-13T13:29:10.784Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\authentication\\remote_login_test.dart: Should return an AuthResultEntity if authLoginIsCalled",
          "isSuccess": true,
          "started": "2023-02-13T13:29:10.784Z",
          "ended": "2023-02-13T13:29:10.814Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\authentication\\remote_login_test.dart: Should return DomainError on HttpError.unauthorized",
          "isSuccess": true,
          "started": "2023-02-13T13:29:10.814Z",
          "ended": "2023-02-13T13:29:10.814Z"
        }
      ]
    },
    {
      "title": "remote_fetch_client_details_test",
      "isSuccess": false,
      "succeeded": 15,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\clients\\remote_fetch_client_details_test.dart: should make a get request on proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:17.085Z",
          "ended": "2023-02-13T13:29:17.160Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\clients\\remote_fetch_client_details_test.dart: should make a get request on proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:17.160Z",
          "ended": "2023-02-13T13:29:17.175Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\clients\\remote_fetch_client_details_test.dart: should return a ClientDetailsEntity",
          "isSuccess": true,
          "started": "2023-02-13T13:29:17.175Z",
          "ended": "2023-02-13T13:29:17.190Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\clients\\remote_fetch_client_details_test.dart: should throw a DomainError when request throws an HttpError",
          "isSuccess": true,
          "started": "2023-02-13T13:29:17.190Z",
          "ended": "2023-02-13T13:29:17.220Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\clients\\remote_fetch_client_details_test.dart: should throw a ModelError when request returns invalid data",
          "isSuccess": true,
          "started": "2023-02-13T13:29:17.220Z",
          "ended": "2023-02-13T13:29:17.220Z"
        }
      ]
    },
    {
      "title": "remote_fetch_maintenance_plan_test",
      "isSuccess": false,
      "succeeded": 19,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\maintenance_plan\\remote_fetch_maintenance_plan_test.dart: should make a get request on proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:18.360Z",
          "ended": "2023-02-13T13:29:18.450Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\maintenance_plan\\remote_fetch_maintenance_plan_test.dart: should make a get request on proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:18.450Z",
          "ended": "2023-02-13T13:29:18.495Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\maintenance_plan\\remote_fetch_maintenance_plan_test.dart: should return a list of String",
          "isSuccess": true,
          "started": "2023-02-13T13:29:18.495Z",
          "ended": "2023-02-13T13:29:18.525Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\maintenance_plan\\remote_fetch_maintenance_plan_test.dart: should throw a DomainError when request throws an HttpError",
          "isSuccess": true,
          "started": "2023-02-13T13:29:18.525Z",
          "ended": "2023-02-13T13:29:18.600Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\maintenance_plan\\remote_fetch_maintenance_plan_test.dart: should throw a ModelError when request returns invalid data",
          "isSuccess": true,
          "started": "2023-02-13T13:29:18.600Z",
          "ended": "2023-02-13T13:29:18.600Z"
        }
      ]
    },
    {
      "title": "remote_maintenance_status_test",
      "isSuccess": false,
      "succeeded": 21,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\maintenance_status\\remote_maintenance_status_test.dart: should return bool when api returns success",
          "isSuccess": true,
          "started": "2023-02-13T13:29:25.368Z",
          "ended": "2023-02-13T13:29:25.473Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\maintenance_status\\remote_maintenance_status_test.dart: should return bool when api returns success",
          "isSuccess": true,
          "started": "2023-02-13T13:29:25.473Z",
          "ended": "2023-02-13T13:29:25.488Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\maintenance_status\\remote_maintenance_status_test.dart: should throw an DomainError when request throws an HttpError",
          "isSuccess": true,
          "started": "2023-02-13T13:29:25.488Z",
          "ended": "2023-02-13T13:29:25.488Z"
        }
      ]
    },
    {
      "title": "load_onboarding_visualization_test",
      "isSuccess": false,
      "succeeded": 27,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should call fetchSecure with correct values AppCacheKeys.onboardingEntities",
          "isSuccess": true,
          "started": "2023-02-13T13:29:26.523Z",
          "ended": "2023-02-13T13:29:26.584Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should call fetchSecure with correct values AppCacheKeys.onboardingEntities",
          "isSuccess": true,
          "started": "2023-02-13T13:29:26.584Z",
          "ended": "2023-02-13T13:29:26.598Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should call sut usecase with correct values AppCacheKeys.onboardingEntities when calling sut",
          "isSuccess": true,
          "started": "2023-02-13T13:29:26.598Z",
          "ended": "2023-02-13T13:29:26.598Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should return list of OnboardingVisualizationEntity",
          "isSuccess": true,
          "started": "2023-02-13T13:29:26.598Z",
          "ended": "2023-02-13T13:29:26.613Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should return an non empty list of OnboardingVisualizationEntity",
          "isSuccess": true,
          "started": "2023-02-13T13:29:26.613Z",
          "ended": "2023-02-13T13:29:26.613Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should return list of OnboardingVisualizationEntity with correct values",
          "isSuccess": true,
          "started": "2023-02-13T13:29:26.613Z",
          "ended": "2023-02-13T13:29:26.658Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\load_onboarding_visualization_test.dart: Should throw ModelError if incorrect json was loaded",
          "isSuccess": true,
          "started": "2023-02-13T13:29:26.658Z",
          "ended": "2023-02-13T13:29:26.658Z"
        }
      ]
    },
    {
      "title": "save_onboarding_visualization_test",
      "isSuccess": false,
      "succeeded": 29,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\save_onboarding_visualization_test.dart: Should call saveSecure with correct values AppCacheKeys.onboardingEntities",
          "isSuccess": true,
          "started": "2023-02-13T13:29:32.634Z",
          "ended": "2023-02-13T13:29:32.694Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\save_onboarding_visualization_test.dart: Should call saveSecure with correct values AppCacheKeys.onboardingEntities",
          "isSuccess": true,
          "started": "2023-02-13T13:29:32.694Z",
          "ended": "2023-02-13T13:29:32.709Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\onboarding\\save_onboarding_visualization_test.dart: Should load LocalLoadOnboardingVisualization with correct values",
          "isSuccess": true,
          "started": "2023-02-13T13:29:32.709Z",
          "ended": "2023-02-13T13:29:32.709Z"
        }
      ]
    },
    {
      "title": "remote_fetch_service_specialty_test",
      "isSuccess": false,
      "succeeded": 33,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_specialty_test.dart: should make a get request on proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:33.654Z",
          "ended": "2023-02-13T13:29:33.759Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_specialty_test.dart: should make a get request on proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:33.759Z",
          "ended": "2023-02-13T13:29:33.759Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_specialty_test.dart: should return a list of ServiceSpecialtyEntity",
          "isSuccess": true,
          "started": "2023-02-13T13:29:33.759Z",
          "ended": "2023-02-13T13:29:33.804Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_specialty_test.dart: should throw a DomainError when request throws an HttpError",
          "isSuccess": true,
          "started": "2023-02-13T13:29:33.804Z",
          "ended": "2023-02-13T13:29:33.879Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_specialty_test.dart: should throw a ModelError when request returns invalid data",
          "isSuccess": true,
          "started": "2023-02-13T13:29:33.879Z",
          "ended": "2023-02-13T13:29:33.879Z"
        }
      ]
    },
    {
      "title": "remote_fetch_service_status_test",
      "isSuccess": false,
      "succeeded": 37,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_status_test.dart: should make a get request on proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:40.211Z",
          "ended": "2023-02-13T13:29:40.271Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_status_test.dart: should make a get request on proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:40.271Z",
          "ended": "2023-02-13T13:29:40.286Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_status_test.dart: should return a list of ServiceTypeEntity",
          "isSuccess": true,
          "started": "2023-02-13T13:29:40.286Z",
          "ended": "2023-02-13T13:29:40.301Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_status_test.dart: should throw a DomainError when request throws an HttpError",
          "isSuccess": true,
          "started": "2023-02-13T13:29:40.301Z",
          "ended": "2023-02-13T13:29:40.331Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_status_test.dart: should throw a ModelError when request returns invalid data",
          "isSuccess": true,
          "started": "2023-02-13T13:29:40.331Z",
          "ended": "2023-02-13T13:29:40.331Z"
        }
      ]
    },
    {
      "title": "remote_fetch_service_types_test",
      "isSuccess": false,
      "succeeded": 41,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_types_test.dart: should make a get request on proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:41.636Z",
          "ended": "2023-02-13T13:29:41.696Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_types_test.dart: should make a get request on proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:41.696Z",
          "ended": "2023-02-13T13:29:41.696Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_types_test.dart: should return a list of ServiceTypeEntity",
          "isSuccess": true,
          "started": "2023-02-13T13:29:41.696Z",
          "ended": "2023-02-13T13:29:41.711Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_types_test.dart: should throw a DomainError when request throws an HttpError",
          "isSuccess": true,
          "started": "2023-02-13T13:29:41.711Z",
          "ended": "2023-02-13T13:29:41.756Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\service\\remote_fetch_service_types_test.dart: should throw a ModelError when request returns invalid data",
          "isSuccess": true,
          "started": "2023-02-13T13:29:41.756Z",
          "ended": "2023-02-13T13:29:41.756Z"
        }
      ]
    },
    {
      "title": "remote_solicitation_details_test",
      "isSuccess": false,
      "succeeded": 45,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\solicitation_details\\remote_solicitation_details_test.dart: should call client method get with proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:47.217Z",
          "ended": "2023-02-13T13:29:47.307Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\solicitation_details\\remote_solicitation_details_test.dart: should call client method get with proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:47.307Z",
          "ended": "2023-02-13T13:29:47.322Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\solicitation_details\\remote_solicitation_details_test.dart: should return an NewUserCouponEntity with proper data",
          "isSuccess": true,
          "started": "2023-02-13T13:29:47.322Z",
          "ended": "2023-02-13T13:29:47.337Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\solicitation_details\\remote_solicitation_details_test.dart: should rethrow HttpError when request fails",
          "isSuccess": true,
          "started": "2023-02-13T13:29:47.337Z",
          "ended": "2023-02-13T13:29:47.367Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\solicitation_details\\remote_solicitation_details_test.dart: should rethrow invalidData when data is invalid",
          "isSuccess": true,
          "started": "2023-02-13T13:29:47.367Z",
          "ended": "2023-02-13T13:29:47.367Z"
        }
      ]
    },
    {
      "title": "remote_update_kilometers_driver_test",
      "isSuccess": false,
      "succeeded": 47,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicle\\remote_update_kilometers_driver_test.dart: should call the proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:48.642Z",
          "ended": "2023-02-13T13:29:48.717Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicle\\remote_update_kilometers_driver_test.dart: should call the proper url",
          "isSuccess": true,
          "started": "2023-02-13T13:29:48.717Z",
          "ended": "2023-02-13T13:29:48.747Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicle\\remote_update_kilometers_driver_test.dart: should throw a DomainError when request fails",
          "isSuccess": true,
          "started": "2023-02-13T13:29:48.747Z",
          "ended": "2023-02-13T13:29:48.747Z"
        }
      ]
    },
    {
      "title": "remote_fetch_vehicles_test",
      "isSuccess": false,
      "succeeded": 52,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicles_test.dart: should call client method get with proper url and plate is empty",
          "isSuccess": true,
          "started": "2023-02-13T13:29:54.252Z",
          "ended": "2023-02-13T13:29:54.328Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicles_test.dart: should call client method get with proper url and plate is empty",
          "isSuccess": true,
          "started": "2023-02-13T13:29:54.328Z",
          "ended": "2023-02-13T13:29:54.328Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicles_test.dart: should call client method get with proper url and plate is not empty",
          "isSuccess": true,
          "started": "2023-02-13T13:29:54.328Z",
          "ended": "2023-02-13T13:29:54.343Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicles_test.dart: should return List VehicleDetailsEntity with correct data",
          "isSuccess": true,
          "started": "2023-02-13T13:29:54.343Z",
          "ended": "2023-02-13T13:29:54.343Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicles_test.dart: should rethrow HttpError when request fails",
          "isSuccess": true,
          "started": "2023-02-13T13:29:54.343Z",
          "ended": "2023-02-13T13:29:54.388Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicles_test.dart: should throw remoteParseData error when cant parse data",
          "isSuccess": true,
          "started": "2023-02-13T13:29:54.388Z",
          "ended": "2023-02-13T13:29:54.388Z"
        }
      ]
    },
    {
      "title": "remote_fetch_vehicle_drivers_test",
      "isSuccess": false,
      "succeeded": 57,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicle_drivers_test.dart: should call the proper url and return a list of VehicleDriverEntity",
          "isSuccess": true,
          "started": "2023-02-13T13:29:55.543Z",
          "ended": "2023-02-13T13:29:55.633Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicle_drivers_test.dart: should call the proper url and return a list of VehicleDriverEntity",
          "isSuccess": true,
          "started": "2023-02-13T13:29:55.633Z",
          "ended": "2023-02-13T13:29:55.663Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicle_drivers_test.dart: should return the correct list of VehicleDriverEntity",
          "isSuccess": true,
          "started": "2023-02-13T13:29:55.663Z",
          "ended": "2023-02-13T13:29:55.768Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicle_drivers_test.dart: should throw a DomainError when returned data is invalid",
          "isSuccess": true,
          "started": "2023-02-13T13:29:55.768Z",
          "ended": "2023-02-13T13:29:55.858Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicle_drivers_test.dart: should throw a DomainError when returned data has invalid types",
          "isSuccess": true,
          "started": "2023-02-13T13:29:55.858Z",
          "ended": "2023-02-13T13:29:55.873Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\data\\usecases\\vehicles\\remote_fetch_vehicle_drivers_test.dart: should throw a DomainError when request fails",
          "isSuccess": true,
          "started": "2023-02-13T13:29:55.873Z",
          "ended": "2023-02-13T13:29:55.873Z"
        }
      ]
    },
    {
      "title": "getting_user_profile_test",
      "isSuccess": false,
      "succeeded": 61,
      "failed": 0,
      "cases": [
        {
          "title": "D:\\a\\1\\s\\test\\utils\\getting_user_profile_test.dart: Should return CurrentUserRole.driverProfile profile if current user is an driver",
          "isSuccess": true,
          "started": "2023-02-13T13:30:01.927Z",
          "ended": "2023-02-13T13:30:01.957Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\utils\\getting_user_profile_test.dart: Should return CurrentUserRole.driverProfile profile if current user is an driver",
          "isSuccess": true,
          "started": "2023-02-13T13:30:01.957Z",
          "ended": "2023-02-13T13:30:01.973Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\utils\\getting_user_profile_test.dart: Should return CurrentUserRole.driverApprover profile if current user is an driver Approver",
          "isSuccess": true,
          "started": "2023-02-13T13:30:01.973Z",
          "ended": "2023-02-13T13:30:01.973Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\utils\\getting_user_profile_test.dart: Should return CurrentUserRole.fleetAdmin profile if current user is an admin",
          "isSuccess": true,
          "started": "2023-02-13T13:30:01.973Z",
          "ended": "2023-02-13T13:30:01.973Z"
        },
        {
          "title": "D:\\a\\1\\s\\test\\utils\\getting_user_profile_test.dart: Should return CurrentUserRole.notAvailable profile if current user is not available",
          "isSuccess": true,
          "started": "2023-02-13T13:30:01.973Z",
          "ended": "2023-02-13T13:30:01.973Z"
        }
      ]
    }
  ]
}

One more point, your logs show a debug trail. You could check if that's an issue for a fail.
D:\a\1\s\test\utils\getting_user_profile_test.dart: Should return CurrentUserRole.notAvailable profile if current user is not available

Hi, is this issue fixed. It will get closed soon as stale-inactive.


Bugfix/deprecations

This PR should finish the work @bangpound started to fix the deprecation warnings ember-datepicker was throwing at us.
@bangpount @AcitveCampaign/deals please review

Hold on this until we can produce the test results.

Closing this temporarily


Xmas tree live coding app

Was not sure where to share this. Since I've seen people share their own utilities here in the issues & pull requests, figured I could do the same.
Here is a little app where you can write JS code and see the effect immediately in the browser. It also supports playing CSV files.
Enjoy!
https://sirxemic.github.io/xmastree-app/

I guess you should add this as a pull request for the further works section because here it might be forgotten.
Do you assume the column headers to be upper case? My csv file again doesn't play at all. And I had this exact same issue with another simulator. test file

I consider files that start with FRAME_ID to be valid, since the example files at https://github.com/GSD6338/XmasTree/tree/main/misc start with that. I guess in practice the first line will always be skipped regardless of the contents, so I'll make my importer do the same.
I'll also create the PR.

Very cool! Going to close this in favor of https://github.com/standupmaths/xmastree2021/pull/19 just to keep things organised.


Add new labels for terraform-google-modules

Adds two new labels for terraform-google-modules

This has been applied


Update setup requirements

Use the same requirements as requirements.txt

This PR needs to be synced with the current setup.py or closed.

No longer needed. Thanks for reporting


feat(playground): update in-app wallet auth options and components

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
The focus of this PR is to update the in-app wallet functionality in the Playground web app.
Detailed summary

Added wallet configuration options to SponsoredInAppTxPreview component
Updated InAppConnectEmbed component with new wallet configuration
Refactored InAppConnectButton to InAppConnectEmbed and updated wallet configuration

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#4757  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @joaquim-verges and the rest of your teammates on  Graphite


Canary pipeline slack integration

Add visibility to canary deployment pipeline by publishing a slack message when deployments fail or succeed

duplicate of #1554 !


Add digdagignore

Issue: #1092
Reading prior work #1175 , I

wrote change in ProjectArchive.
use eclipse JGit for implementation.

I still have some worries.

I don't understand "In your current implementation, ignoreFileList method is called every tar entry copying. " in https://github.com/treasure-data/digdag/pull/1175#issuecomment-511006334 yet.
whether listFiles method is good place to parse ignorefile or not.
where should I write doc about .digdagignore

IgnoreNode in JGit doesn't seem to work with Path::toString on Windows.
I'll search for a solution.

I resolved the problem 479493f .
Though it might be good solution, it should work with almost all cases.

Windows

According this post, it is safe.

I'm not sure if it is really true.

Not Windows

replace method replaces / by /. Nothing happens.

Hey! Any estimate when this functionality will be available? In my case, I need it so I can have test .dig files that are used by my tests suite but that I don't want to push to my production server. The way my code is organized, they need to reside in the root of my directory.

Same here! This feature would be HUGELY beneficial to me. Know when this would be released allows me to decide whether to pursue for other solutions in the mean time

Thank you for your feedback. I'm going to prepare the next version soon. I think we can release the next one within this week, and I'd appreciate your patience.


feat: shift-click modules to expand/collapse dependencies

@bennycode: This isn't quite what you're asking for in #47, but it's a step in the right direction. Just shift-click modules in the graph to hide their dependencies.   E.g. you can collapse your @wireapp/core diagram down to something like the following.  It requires a lot of clicking, though.

This puts the basic code in place for manipulating what modules/dependencies are shown in a graph, so enhancing this to allow for regex-based hiding of modules should be pretty easy.  However ... the reason I went with this approach is that it keeps the parent module in the graph.  This makes it easier to undo the collapse action (parent module is still shift-clickable in the graph), and it makes it clear where modules have been removed from the graph.
(@fregante Does switching to Vercel remove the need to commit the parcel build output (/docs/* in this diff)?    'Would love to not have that be part of the commit step.)

The was never a need to commit the docs folder on the main branch. The original idea was to push to the gh-pages branch like the workflow I linked to did.
Anyway, yes. Vercel builds and hosts the file, so it just needs the source.

Seems to work well and it's useful! One small issue is due to how shift works (in Safari only). I think it just needs a e.preventDefault()

Seems to work well and it's useful! One small issue is due to how shift works (in Safari only). I think it just needs a e.preventDefault()

You mean the brief text-selection flash?  Looks like that's because Safari requires the "-webkit-" prefix for the user-select CSS property.  Should be fixed now.

@fregante Okay to merge?


jspm foundation import

Hello there,
how is it possible to import foundation.offcanvas with jspm?
Only the foundation main file seems to be exported as module.
Thanks a lot!
Best regards, k

Hi,
the only solution i see is that the package.json should point to the min.js file as default. After that a
import foundation from 'foundation';
will include all the needed js components.
Best regards
Dominic

Solved by changing the package.json
https://github.com/INSPIRATIONlabs/bower-foundation

Wow, thank you Dominic!
It helped a lot! ;)

looks like this has been all resolved. I'll close it for now, but feel free to reopen it if I'm mistaken,


Creates the function to set external API key

Implemented the set_apikey function within the Client class to set the different external API keys.
def set_apikey(self, openai_key: Optional[str] = None, cohere_key: Optional[str] = None, huggingface_key: Optional[str] = None, palm_key: Optional[str] = None):
    ...

This PR can close the issue #382
cc @tsmith023 @databyjp

Note also the mypy errors in the CI pipeline. If you've not used mypy before then they're telling you that your function needs to have a return marked, i.e. -> None: and it cannot determine the type of _headers, which I think is solvable by adding self._headers: Dict[str, str] = {} here

Codecov Report
Patch coverage: 11.11% and project coverage change: -0.58% :warning:

Comparison is base (7528726) 94.75% compared to head (848c5d6) 94.18%.
Report is 12 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #527      +/-   ##
==========================================
- Coverage   94.75%   94.18%   -0.58%
==========================================
  Files          70       70
  Lines        8492     8501       +9
==========================================
- Hits         8047     8007      -40
- Misses        445      494      +49

Files Changed
Coverage Δ

weaviate/client.py
89.28% <11.11%> (-9.39%)
:arrow_down:

... and 5 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@tsmith023 Thanks for the review. Soon making the desired changes.

@tsmith023
Hi Tommy
I have made the following changes-

Add self._headers: Dict[str, str] = {} line in connect/connection.py file
Add -> None in the function signature

Thanks
Ankur

I am unable to add the tests in the required file. I am afraid that it will take some time because I have my University exams.

@tsmith023 I have added unit tests.

I have my University exams

You should concentrate on these first! The PR can stay open until you have time to resume it, there's no pressure 😁

I have my University exams

You should concentrate on these first! The PR can stay open until you have time to resume it, there's no pressure 😁

Thanks for the patience, I am now available. If there are any changes required then please let me know.

@tsmith023 Any feedback regarding the PR.

Hi @ankur0904, sorry for not replying promptly! Because the CI pipeline is not fully green, it needs to be fixed before I will review it again. Could you look into the linting problems and unit test failures? Cheers 😁

@tsmith023 Ofcourse I will look into the failing CI pipeline.

Hey @tsmith023 any other changes required?

Hey @tsmith023 any other changes required?

Hi @ankur0904 - I can see that quite a few tests are failing here. Please take a look at the individual pipelines to see what is failing and try to address them.
As you can imagine, libraries like this one are our core products. And these automated tests are important parts of our quality assurance processes that help us ensure that any potential bugs or regressions do not get introduced into our products.
If you click on the Details tab in the PR CI checklist, you can see the logs and stack trace, which should help you to see what is failing.
I see that the pipeline indicates the linting process to be failing, and some unit tests.
You can run these tests locally before committing / testing the changes through the CI/CD pipeline. You might have read this already, but the contributor guide includes a section on linting, and tests. So, please review these sections, and run those tests locally, which should mean that they pass on GH.
I hope that helps!

@databyjp Thanks for the guidance.
I checked each CI pipeline test, I found this test failure and confused how to fix it?
After running
$ pytest test --full-trace

self = <weaviate.client.Client object at 0x7f00886e77f0>, openai_key = 'your_key'
cohere_key = None, huggingface_key = None, palm_key = None

    def set_apikey(self, openai_key: Optional[str] = None, cohere_key: Optional[str] = None, huggingface_key: Optional[str] = None, palm_key: Optional[str] = None) -> None:
        """
        Set the external API key.

        Parameters
        ----------
        openai_key: str, optional
            It is OpenAI API key.
        cohere_key: str, optional
            It is Cohere API key.
        huggingface_key: str, optional
            It is Hugging Face API key.
        palm_key: str, optional
            It is Palm API key.

        Returns
        -------
        None
        """
        if openai_key:
>           self._connection._headers["x-openai-api-key"] = openai_key
E           TypeError: 'Mock' object does not support item assignment

cohere_key = None
huggingface_key = None
openai_key = 'your_key'
palm_key   = None
self       = <weaviate.client.Client object at 0x7f00886e77f0>

weaviate/client.py:320: TypeError

Related File:
client.py
P.S. Meanwhile, I have fixed the linting issue.
Thanks
Ankur

superseeded by https://github.com/weaviate/weaviate-python-client/pull/981


try pkg-config for libzmq first, before hacks

On the latest pyzmq I encounter it being unable to find the header zmq.h, when it is installed in /usr/local/include, and pyzmq is installed into Sage's python (I guess a private copy of Python will do, it's not really Sagemath-specific). I tracked it down to it not even trying to call pkg-config, but resorting to some kind of guesswork.
Once I tell it to call pkg-config, as follows:
--- a/setup.py
+++ b/setup.py
@@ -222,7 +222,7 @@ def settings_from_prefix(prefix=None, bundle_libzmq_dylib=False):
           else:
             settings['extra_link_args'] += ['-m64']

-        if prefix:
+        if 0: # so we will try pkg-config!
             settings['libraries'].append('zmq')

             settings['include_dirs'] += [pjoin(prefix, 'include')]

everything is good. It seems that assuming that everything will be in "prefix"/ is too restrictive.

Oh, thanks, and sorry for noise, we actually do what you just said, in some apparently pre-pkg-config code from 2014...


AEM: Add support for proxy and debug settings

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[x] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

AEM

Could you rebase your branch and try again?


Add codacy badge

bors merge

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch-InfoPropertyBeforeAfterHPXLocal Commitf499a2233385060b8a2612ab88163e62b0881888152623fc801c21e718c53839d6068c8b299c8888HPXLocal Datetime2021-12-10T13:50:04+00:002021-12-20T11:34:41+00:00EnvfileDatetime2021-12-10T15:19:42.442217+01:002021-12-20T12:39:36.585398+01:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Hostnamenid00243nid00095ClusternamedaintdaintComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add(=)(=)(=)Stream Benchmark - Scale--(=)Stream Benchmark - Triad(=)(=)(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4152623fc801c21e718c53839d6068c8b299c8888HPXLocal Datetime2021-11-12T11:29:27+00:002021-12-20T11:34:41+00:00EnvfileDatetime2021-11-12T12:57:50.824026+01:002021-12-20T12:39:51.377289+01:00Compiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0Hostnamenid00007nid00095ClusternamedaintdaintExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

Performance test reportHPXLocal PerformanceComparisonBENCHMARKNO-EXECUTORFuture Overhead - Create Thread Hierarchical - Latch-InfoPropertyBeforeAfterHPXLocal Commitf499a2233385060b8a2612ab88163e62b0881888152623fc801c21e718c53839d6068c8b299c8888HPXLocal Datetime2021-12-10T13:50:04+00:002021-12-20T11:34:41+00:00Datetime2021-12-10T15:19:42.442217+01:002021-12-20T12:44:26.012799+01:00Hostnamenid00243nid00095EnvfileCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ClusternamedaintdaintComparisonBENCHMARKFORK_JOIN_EXECUTORPARALLEL_EXECUTORSCHEDULER_EXECUTORStream Benchmark - Add-(=)(=)Stream Benchmark - Scale(=)--Stream Benchmark - Triad(=)-(=)Stream Benchmark - Copy(=)(=)(=)InfoPropertyBeforeAfterHPXLocal Commitf64fbd02165a132a6276cedd14c586910abb79e4152623fc801c21e718c53839d6068c8b299c8888HPXLocal Datetime2021-11-12T11:29:27+00:002021-12-20T11:34:41+00:00Datetime2021-11-12T12:57:50.824026+01:002021-12-20T12:44:41.167216+01:00Hostnamenid00007nid00095EnvfileCompiler/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0/apps/daint/SSL/HPX/packages/llvm-11.0.0/bin/clang++ 11.0.0ClusternamedaintdaintExplanation of SymbolsSymbolMEANING=No performance change (confidence interval within ±1%)(=)Probably no performance change (confidence interval within ±2%)(+)/(-)Very small performance improvement/degradation (≤1%)+/-Small performance improvement/degradation (≤5%)++/--Large performance improvement/degradation (≤10%)+++/---Very large performance improvement/degradation (>10%)?Probably no change, but quite large uncertainty (confidence interval with ±5%)??Unclear result, very large uncertainty (±10%)???Something unexpected…

bors merge


Stores information received by web server in SPIFFS

Create a code that confirms the following flow

esp32 c3 : web server
Access the web server with a browser from a smartphone
Enter text information in your browser and submit
Stores character information received on the esp32 server side in SPIFFS

i will do this today


Retry read operations up to 10 times on EIO

Some faulty SDCard, or SDCard readers might throw EIO when reading data.
Retrying a couple of times makes the issue go away.
See: https://github.com/resin-io-modules/etcher-image-write/pull/73
Signed-off-by: Juan Cruz Viotti<EMAIL_ADDRESS>

Should the fact that validation is also now done by chunksize be mentioned in the commit message? (or is that only a minor detail?)

Its a minor internal detail, which is not exposed to the user in any way, so I guess we're fine without a CHANGELOG entry. The high water mark option is also just a "hint" for the input stream, and doesn't mean that it will be strictly respected by the OS.

And now this is suddenly working again, when it previously reliably failed on Appveyor... I'll try on a real Windows setup to see if I can reproduce.

It indeed works now. It might have been an Appveyor issue, or an issue with some of the dependencies. We'll keep an eye on it in case it happens again, but it should be good to merge.

I've done a lot of refactoring (in other commits), rebased, and was able to fix the sporadic invalid file descriptor issue, which seems to have been caused by a race condition on image read stream.


fix: sponge pad panics on input

closes #44

A couple of comments on this:

We should use the same padding rule as for hash_elements() here. Specifically, if the number of elements to be hashed is a multiple of 8, we set capacity registers to ZERO's. If it is not a multiple of 8, then we set the first capacity register to ONE and the rest to ZERO's, and also append ONE to the input element string.
For binary string, we should keep splitting the input into 7-byte chunks. Splitting it into 8-byte chunks would cause collisions as 8-byte chunks don't map one-to-one to Field elements.
We may need to apply additional padding to the last chunk. Specifically, we need to append 1 to the string before converting the last chunk into a field element. I think this is already being done, but I'd probably add a test to make sure something like [0; 9] and [0; 10] hash to different values.


Laravel 5.3 Shift

This pull request includes the changes for upgrading to Laravel 5.3. Feel free to commit any additional changes to the laravel-5.3-shift branch.
Before merging, you should:

Checkout the laravel-5.3-shift branch
Review all pull request comments for additional changes
Run composer update (if the pre-commands fail, add --no-scripts)
Thoroughly test your application

If you would like more help with your upgrade, check out the new human services from Laravel Shift.

❌ I could not upgrade the following project files since they differed from the 5.2 defaults. You need to compare these project files against the default Laravel 5.3 versions and merge any changes:

[ ] gulpfile.js
[ ] package.json

❌ Laravel 5.3 renamed the Auth/PasswordController.php to Auth/ResetPasswordController.php. Since yours appears to be customized, I did not remove it. You should compare your Auth/PasswordController.php against the added Auth/ResetPasswordController.php and merge your changes accordingly.

❌ I could not upgrade the following configuration files since they differed from the 5.2 defaults. You need to compare these configuration files against the Laravel 5.3 configuration files and merge any changes:

[ ] config/cache.php
[ ] config/services.php
[ ] config/session.php

⚠ Laravel 5.3 now includes a top-level routes folder. In addition, it separates routes into API, console, and web files.I have included a default routes/api.php and routes/console.php as well as migrated your app/Http/routes.php to routes/web.php. You should review your routes to see if they should be separated into one of the new route files.

ℹ Laravel 5.3 added Route::auth() which automatically creates the authorization routes. This method registers a POST route for /logout instead of a GET route. If you are using the Authorization component, you should upgrade your code to use this method.

ℹ If you are using Queues, you no longer need to specify the --daemon option when calling the queue:work. This is assumed in Laravel 5.3. Use the --once option to process a single job.
If you are using the database driver, you will need to update your jobs and failed_jobs table. Review the Queue section of the Laravel 5.3 Upgrade Guide for more details.

⚠ Laravel 5.3 added configuration for your application name in config/app.php. Be sure to set this value as it is used in notifications, like the password reset email.

ℹ Laravel 5.3 updated several of the default assets as well as adding support for Vue.js. If you are using Laravel to compile assets you may want to review the latest versions of resources/assets/js/app.js and resources/assets/sass/app.scss and update your project accordingly.

❌ Laravel 5.3 where performs a "loose" comparison. In addition, the strict parameter was removed. If you need to perform a "strict" comparison, you can use whereStrict instead.
You should review the following usages of where to ensure you do not require "strict" compaison:

[ ] routes/web.php


Build Custom GPU Op Failed with TF-1.3.1

System information

Have I written custom code:
YES
OS Platform and Distribution:
Ubuntu 14.04 LTS
TensorFlow installed from:
source
TensorFlow version:
1.3.1
Python version:
2.7.6
Bazel version:
0.5.4
GCC/Compiler version:
4.8.4
CUDA/cuDNN version:
7.5/6.0
GPU model and memory:
Geforce GTX TITAN X, 12GB
Exact command to reproduce:

TF_INC=$(python -c 'import tensorflow as tf; print tf.sysconfig.get_include()')
nvcc -std=c++11 -c -o interpolate.cu.o interpolate_gpu.cu.cc \
        -I $TF_INC -D GOOGLE_CUDA=1 -x cu -Xcompiler -fPIC -D_MWAITXINTRIN_H_INCLUDED

Describe the problem
I want to compile a custom gpu op by nvcc with tf-1.3.1, however it returns the following result:
/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/framework/op_kernel.h(317): warning: type qualifier on return type is meaningless

/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/stream_executor/kernel.h(307): warning: variable "result" is used before its value is set

/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/stream_executor/device_description.h(85): warning: type qualifier on return type is meaningless

/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/stream_executor/device_description.h(144): warning: type qualifier on return type is meaningless

/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_kernel_helper.h(620): error: identifier "__shfl" is undefined

/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_kernel_helper.h(640): error: identifier "__shfl_up" is undefined

/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_kernel_helper.h(660): error: identifier "__shfl_down" is undefined

/usr/local/lib/python2.7/dist-packages/tensorflow/include/tensorflow/core/util/cuda_kernel_helper.h(680): error: identifier "__shfl_xor" is undefined

4 errors detected in the compilation of "/tmp/tmpxft_00001c41_00000000-7_interpolate_gpu.cu.cpp1.ii".

This question is better asked on  StackOverflow since it is not a  bug or feature request. There is also a larger community that reads questions there. Thanks!


Please bring back WebView 1 in UWP WinUI 3

Proposal: Temporarily make WebView (1) available in UWP WinUI 3 projects
Summary
Please enable WebView (1) in WinUI 3 UWP projects.
Rationale
Please make the move to WinUI 3 as easy for us as possible. The legacy WebView has a different API than the new WebView2 component. It would be great if we could tackle these migrations not all at the same time.
Marking WebView (1) as [Obsolete] seems like a great way to send a clear message and at the same time make the porting from 2 to 3 easier. (Or some other kind of compiler warning)
Scope

Capability
Priority

API compatible to WebView (1)
Must

Clearly marked as obsolete
Should

Long term compatibility/support for WebView 1
Won't

Important Notes
The rendering engine used does not matter for this proposal, a shim from WebView 1 to 2 would also work.
Open Questions
Bringing WebView2 to UWP WinUI 2 would also solve this problem, as we can than move to WebView 2 first and WinUI 3 at a later time.

You can continue using Inbox UWP until you are ready to move to WinUI 3 and WebView 2

Yes I can. But to make the move I have to change all WebView instances at the same time while I am so changing the UI framework. That's quite a big task.
(Over on the Apple side: WKWebView was introduced 5 years ago and the predecessor UIWebView is deprecated but still works)

Is WebView 2 compatible with UWP WinUI 2? If so, you can migrate to WebView2 first.

@huoyaoyuan It is not.

@Marv51 we appreciate your feedback. We understand the migration experience is a challenge. However, given a number of trade-offs and resource constraints we won't be able to address this. Let us know if you encounter issues while migrating to WebView2 and any issues that come up with that.


New release PR created after merging release PR with modified changelog

Bug description
After editing the changelog of my release PR and merging it, the workflow immediately created a new release PR with the changelog regenerated from the commit history. The crate versions are not updated and the changelog in the PR contains a new section with the same version.
Original release PR: https://github.com/avsaase/fusion-imu/pull/1
New release PR: https://github.com/avsaase/fusion-imu/pull/2
Workflow run: https://github.com/avsaase/fusion-imu/actions/runs/9822277403/job/27118844585
Relevant part of the logs:
-- Running release-plz release-pr --
  2024-07-06T21:38:37.858357Z  INFO  using release-plz config file release-plz.toml

  2024-07-06T21:38:37.879292Z  INFO  downloading packages from cargo registry
    in download with self=PackageDownloader { packages: ["fusion-imu-sys", "fusion-imu"], directory: "/tmp/.tmpYhVrZ8", registry: None, cargo_cwd: None }
    in next_versions
    in update
    in release_pr

note: Cloning into "/tmp/.tmpYhVrZ8"
    Updating crates.io index
  2024-07-06T21:38:38.197075Z  WARN  Package<EMAIL_ADDRESS>not found
    in download with self=PackageDownloader { packages: ["fusion-imu-sys", "fusion-imu"], directory: "/tmp/.tmpYhVrZ8", registry: None, cargo_cwd: None }
    in next_versions
    in update
    in release_pr

note: Cloning into "/tmp/.tmpYhVrZ8"
  2024-07-06T21:38:38.456481Z  WARN  Package<EMAIL_ADDRESS>not found
    in download with self=PackageDownloader { packages: ["fusion-imu-sys", "fusion-imu"], directory: "/tmp/.tmpYhVrZ8", registry: None, cargo_cwd: None }
    in next_versions
    in update
    in release_pr

  2024-07-06T21:38:39.122182Z  INFO  fusion-imu-sys: next version is 0.1.0
    in packages_to_update
    in next_versions
    in update
    in release_pr

  2024-07-06T21:38:39.122734Z  INFO  fusion-imu: next version is 0.1.0
    in packages_to_update
    in next_versions
    in update
    in release_pr

  2024-07-06T21:38:39.649450Z  WARN  no changes detected in changelog of package fusion-imu-sys
    in release_pr

  2024-07-06T21:38:39.649691Z  WARN  can't determine changes in changelog of package fusion-imu: can't parse changelog

Caused by:
    multiple release notes for '0.1.0'
    in release_pr

  2024-07-06T21:38:41.263149Z  INFO  opened pr: https://github.com/avsaase/fusion-imu/pull/2
    in open_pr
    in release_pr

release_pr_output: {"prs":[{"base_branch":"master","head_branch":"release-plz-2024-07-06T21-38-39Z","html_url":"https://github.com/avsaase/fusion-imu/pull/2","number":2}]}
-- Running release-plz release --
  2024-07-06T21:38:41.380050Z  INFO  using release-plz config file release-plz.toml

  2024-07-06T21:38:58.508147Z  WARN  fusion-imu-sys: failed to parse changelog at path "/home/runner/work/fusion-imu/fusion-imu/fusion-imu-sys/CHANGELOG.md": can't read changelog file

Caused by:
    0: failed to open file `/home/runner/work/fusion-imu/fusion-imu/fusion-imu-sys/CHANGELOG.md`
    1: No such file or directory (os error 2). The git release body will be empty.
    in release

  2024-07-06T21:39:20.282605Z  INFO  waiting for the package fusion-imu-sys to be published...
    in release

  2024-07-06T21:39:23.094817Z  INFO  published fusion-imu-sys 0.1.0
    in release

  2024-07-06T21:39:37.529156Z  INFO  waiting for the package fusion-imu to be published...
    in release

  2024-07-06T21:39:40.386785Z  INFO  published fusion-imu 0.1.0
    in release

release_output: {"releases":[{"package_name":"fusion-imu-sys","prs":[],"tag":"fusion-imu-sys-v0.1.0","version":"0.1.0"},{"package_name":"fusion-imu","prs":[],"tag":"fusion-imu-v0.1.0","version":"0.1.0"}]}

Would you like to work on a fix? [y/n] maybe, I haven't looked at the code yet

To Reproduce
Steps to reproduce the behavior:

Use this config (not sure which parts, if any, are relevant):

[workspace]
changelog_update = false
release_always = false

[[package]]
name = "fusion-imu"
changelog_update = true
changelog_path = "./CHANGELOG.md"
changelog_include = ["fusion-imu-sys"]

Manually edit the changelog in the release PR
Merge the PR
release-plz creates a new release PR with a partially regenerated changelog.

Expected behavior

Screenshots

Environment

OS: [e.g. Ubuntu 20.04] x86_64-unknown-linux-gnu
release-plz version: [e.g. 0.1.0] v0.3.75

Additional context

woops, sorry, I missed this!
You are right. I think this happens when the package is new and you have release_always = false.
One possible fix is the following: before updating the changelog, check if the latest entry of the changelog is the one you are about to insert. If yes, don't update the changelog


Why is there a private getter but a public setter for the same property?

https://github.com/OfficeDev/ews-java-api/blob/7f8793a3faef91a7eb22dae0d9cff8118a66cd24/src/main/java/microsoft/exchange/webservices/data/property/complex/MessageBody.java#L193
https://github.com/OfficeDev/ews-java-api/blob/7f8793a3faef91a7eb22dae0d9cff8118a66cd24/src/main/java/microsoft/exchange/webservices/data/property/complex/MessageBody.java#L202
I'm not trying to be funny. I see that there is another static method getStringFromMessageBody that does actually what the getter does, and the toString method actually returns the text or an empty string. Is there some bigger reason/design decision/pattern?

Setting a property directly is quite useful in various cases. Getting the actual value might be deemed less useful. The differently method might currently get the value as is but there's no guarantee based on the name that it doesn't do some reformatting.


LoadImage is not centered

When we load an image into our XamarinPainter the image is not centered into the painter.
maybe an extra parameter to set it center?

Fixed


Very slow generating batches when training on LJSpeech vs custom data

I am continuing training from the pretrained model on LJSpeech (from 441k steps) and finding it is very slow to generate batches.  If instead of using LJSpeech I finetune the pretrained model on custom data (in this case, on just 20 minutes of speech of a new speaker), it is vastly quicker.

This is probably due to slow seek times when randomly selecting files from the training folder to make up a batch - is it possible to improve this?

Right now, I think the best option is to store the training data on an SSD.


The projects needs a specific name

I personally don't care about the name, but in order to talk about it, one is needed, especially when talking about other lists as well. Let's find one.

What about?

Open Source Technical Infos Games List (OSTIGL)
Open Source Games Technical Infos List (OSGTIL)
Open Source Games Technical Infos (OSGTI)
Trils Open Source Games List (TOSGL)
Open Source Games List (OSGL) <-- favorite
Open Source Games List - Technical Infos (OSGL-TI)

Not only does it need a name, it also needs some kind of logo and favicon icon. I'm not good in this. Just anything will do. Maybe some random colored pixels?

OSGL it is and I will try to make a simple generic icon and favicon in the next days.

The icon and favicon is still missing.

Icon and favicon will be created within the static HTML page #134 and then this issue can be closed.

Favicon is now created. I settled on a PacMan like symbol with some dots that could be a list. If something better comes up, it can of course be replaced. A mirror of the HTML output is also at https://osgl.twelvepm.de/.


[Unity][Transform] Implement UpdateParamStructInfo

Provide a convenience method to update parameter struct info, propagating any changes to internal bindings and return type.

You are using VisitVarDef but are ignoring vars defined inside SeqExprs, so I take it that this will update only function parameters (per the name). Is that correct?

That is correct.  Only parameters would be updated, and variable bindings within the function body would have their struct info inferred.

I'm not sure if it would be simpler to override the function node case instead of VisitVarDef.

I initially ran into some issues with overriding the Expr VisitExpr_(const FunctionNode*) mutator, mostly because it was difficult without copy-pasting the entire ExprMutator implementation.  In order to delegate to the base class's mutator, it would need to first construct a Function object with updated parameters, and then pass that to the base class.  However, that ran into issues with the validity-checking in the Function constructor, since the body of the function wasn't yet updated.
Taking another look at it, it looks like it can be moved to the VisitExpr_(const FunctionNode*) by using func.CopyOnWrite() to avoid going through the normal constructor.  I agree that this is simpler, and have updated the PR to use the less roundabout implementation.


Warlock level up: Duplicates and multiple additional eldritch invocations

When leveling Warlock, after 2nd level, every next level you can choose new invocation from class selection screen (just open again dropdown menu at right side where class details are), old one wasn't removed, however, changing these is nice thing as some optional rules allow to retrain such things.
This works for Warlock after 3rd level with Pact Boon.
(Tested on version <IP_ADDRESS>)

Fixed on <IP_ADDRESS>


Accounts not working as expected when needed to fetch all accounts

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have replicated my issue using the latest version of the library and it is still present.

cloudflare-go version
master
Go environment
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/shivam/.cache/go-build"
GOENV="/home/shivam/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/shivam/.asdf/installs/golang/1.18.1/packages/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/shivam/.asdf/installs/golang/1.18.1/packages"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/shivam/.asdf/installs/golang/1.18.1/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/shivam/.asdf/installs/golang/1.18.1/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18.1"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/shivam/work/cs-cloudflare-bouncer/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3327606679=/tmp/go-build -gno-record-gcc-switches"
Expected output
In older version of this library api.Accounts(ctx, cloudflare.PaginationOptions{}) used to fetch all the accounts a particular user had access to.
Actual output
After the update, the function has been changed to api.Accounts(ctx, cloudflare.AccountsListParams{}) . This particular call doesn't fetch any accounts at all.
After digging into code it seems that it's appending name= parameter to this particular api call with null value. Hence we get no accounts.
Code demonstrating the issue
api.Accounts(ctx, cloudflare.AccountsListParams{})
https://github.com/cloudflare/cloudflare-go/blob/e5c6a2d8740459c045a4f020b5510a87b29fa548/accounts.go#L60
Steps to reproduce
Just use api.Accounts(ctx, cloudflare.AccountsListParams{}), in latest version. It's not returning all accounts as expected
References
No response

thanks, addressed by #910

Thanks for the quick fix. May know when the next release of this library (including this fix) be published ?

it is roughly a fortnightly cadence and we had a release a couple of days ago. in the meantime, you'll need to use the git references if you'd like this change immediately.


Fixed a typo in doc (Email Verifiation Page --> Email Verification Page)

Fix typo in documentation

Thanks @vkomulai !


Parallel Calabash dont identifies devices with android 4.1.x or less

I have this problem with device running android 4.1.x. Parallel Calabash dont identifies the device.
My environment
Calabash: Last version
Parallel Calabash: Last version
OS : Windows 7 Professional

can you paste output of 'adb devices' command?

Hi raj, in this case 'adb devices' return all devices normally.
For example if i'm have 2 devices connecteds:

S3 with android 4.1.2
S4 with android 4.2.2

Adb devices turn two devices on terminal.
But when i`m run command with parallel, only S4 is identified.

Looks interesting, as I internally parse output of 'adb devices' to detect devices. I tried it but could not reproduce. It will help if you can send me screenshot of 'adb devices' output. Or can you please copy-paste exact output here?

Hi raj,
See this screenshot.

interesting. I have htc 4.1 device and it works with that. I do not have s3 though. I think there is something going wrong in parsing the output. can you run this in irb and let me know the output?
adb devices.scan(/\n(.*)\t/).flatten
eg:
2.1.1 :010 > adb devices.scan(/\n(.*)\t/).flatten
=> ["FA42RMW00506", "4d00fa3cb814c03f"]

I return to work next week and give  feedback.

@rajdeepv @mbnetobr  i hold an S3 with 4.1 and it works fine. I'm running parallely on S3(4.1),S4,Note 3,S5 and Nexus 5

@rajdeepv i think @mbnetobr hold only one feature with @sanity tag, i have noticed the same over my side if no of device and no of scenarios should take the right permutations.. For example: 4 devices and 15 features parallel_calabash will tell 3 Devices Found

@rajdeepv the output, in this case device with 4.1.2 version is "e78a7cc1"
irb(main):001:0> adb devices.scan(/\n(.*)\t/).flatten
=> ["cbd168d0", "e78a7cc1"]
irb(main):002:0>

It seems like I need to handle parsing of output differently on windows. I don't have a windows machine as of now, but one last thing you can let me know is output of this in irb:
1.9.3-p0 :001 > `adb devices -l`.split("\n").collect{|line|  [line.split(" ").first,line.scan(/model:(.*) device/).flatten.first] if line.include?("device ")}.compact

Show this:
[["cbd168d0", "SM_G800H"], ["4100980b7904cf00", "GT_I9082L"]]

The second ID is android 4.1.x

@mbnetobr looks like the features with sanity tags are not getting filtered correctly. A better option is to upgrade to latest version and run this command:
parallel_calabahs -a <your_apk_path> -o'-r features' features/test/sanity  --group-by-scenarios --serialize-stdout

I'm update version of the parallel_calabash and bug dont occurs.
Thanks raj.

Great! Thanks

I have the same issue with version 0.1.3  but working with 0.1.2
run on mac OSX

@ma2t87 can you please share below details?

command you are running
Exact error log


feat(windows): allow parent window to be set

Looks great, thank you!

Thanks for the quick merge and publish :) you wrote an amazing lib.

Sure, I do my best  :muscle:
Thanks


When standardizing sumstat, how to ID an association with GENE:Transcripts:SNPs?

At the moment, for each norminal pvalue, we have the following information:
molecular_trait_object_id
molecular_trait_id (ID of the molecular trait used for QTL mapping. Depending on the quantification method used, this can be either a gene id, exon id, transcript id or a txrevise promoter, splicing or 3'end event id. Examples: ENST00000356937, ENSG00000008128.
and SNP :chromosome position ref _alt
Is it that in all scenario, molecular_trait_id is map to 1 and only 1 unique molecular_trait_object_id ?
if that is not the case, then we will need to use molecular_trait_object_id:molecular_trait_id:SNP as the unique identifier for each entry.

Is it that in all scenario, molecular_trait_id is map to 1 and only 1 unique molecular_trait_object_id

Yes

In this case, molecular_trait_id_chromosome_position_ref_alt will be used.


Remove trailling end of line

On a code file, if a class ends with a empty line, raise a diagnostic and remove it on the fix.
New lines are shown with the paragraph character (¶).
So this:
class C¶
{¶
}¶

Becomes:
class C¶
{¶
}

Severity: Info
Category: Style
Diagnostic id: CC0066

Please tell me you wrote that backwards :expressionless:

@sharwell what do you mean?

I like my code files to end with an empty line.

@paulomorgado Outside of certain cases in PHP where there's no choice, this request is the first time I've ever heard of someone not agreeing with you.

first time I've ever heard of someone not agreeing with you

Which is the definition of being wrong. :smile:
Never touched PHP and hope to be able to say that for a long time to come. :smile:

Hm.. I never leave an empty line, I actually remove them. So I understand that this is not consensus. I think I will remove it... :(
Why do you leave an empty line at the end?

A legacy habit (some languages require it and/or are prone to compile-time errors if they are omitted).

Makes it easier to copy the text from the file and insert it somewhere.

Omitting the final newline breaks the Copy command functionality on the last line of the file in Visual Studio when no text is selected. Normally copying a line in this manner allows you to paste it at any character position in the file and the contents of the copied line are pasted above the current line. If the final newline is omitted, the paste operation instead places the content at the beginning of the current line during a paste operation.

Omitting the final newline adds the following annoying line to the end of all your patches generated by Git:

\ No newline at end of file

That makes all lines with block ending }s end with a "new line".
But just one. Which also satisfies no more than one consecutive blank lines.
From the top of my mind, if you search for [ \t]+\r\n' and replace it with \r\n`, it will clean all trailing spaces and tabs.
Replacing ^(\r\n){2,} with \r\nwill remove lines after empty lines.

Ok, a lot to do with copying and pasting. I use VsVim (and vim mode everywhere I can), so this is not an issue to me, as copying and pasting is much more intelligent in Vim. I rarely use the mouse as well.
So, what to make of this? Transform it into a "remove more than one consecutive line break" everywhere, just at the end of the file? What do you think?

Directly related to the following issues:
DotNetAnalyzers/StyleCopAnalyzers#108
DotNetAnalyzers/StyleCopAnalyzers#114
DotNetAnalyzers/StyleCopAnalyzers#119
Indirectly related to the broader complete set of layout diagnostics.

@code-cracker/owners need your opinion here.


gnutls: Fix broken darwin build

Motivation for this change
gnutls wasn't building on darwin. This stopped emacs from building as well.
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

The changes look ok, but it builds fine without as far as I can tell http://hydra.nixos.org/build/54541669.

Hmm. It won't build for me without it. I'm on OSC 10.12.5.

That fix has been tried already but causes crashes (reportedly).  Please see discussion on https://github.com/NixOS/nixpkgs/commit/d6454e6a1.  /cc @copumpkin.

I haven't experienced any crashes. So what's recommended for getting it to work on darwin?

No longer happening in Hydra:
https://hydra.nixos.org/job/nixpkgs/trunk/gnutls.x86_64-darwin


[Fix][UI Next][V1.0.0-Alpha] Fix saving a sub process workflow failure in dag page.

Purpose of the pull request
This pull request fixs saving a sub process workflow failure in dag page.
Releated issues
close #8835

Codecov Report

Merging #8908 (04f3ad1) into dev (563c5b3) will decrease coverage by 0.00%.
The diff coverage is n/a.

:exclamation: Current head 04f3ad1 differs from pull request most recent head 0121576. Consider uploading reports for the commit 0121576 to get more accurate results

@@             Coverage Diff              @@
##                dev    #8908      +/-   ##
============================================
- Coverage     39.77%   39.76%   -0.01%
+ Complexity     4261     4260       -1
============================================
  Files           808      808
  Lines         32545    32545
  Branches       3646     3646
============================================
- Hits          12945    12943       -2
+ Misses        18378    18376       -2
- Partials       1222     1226       +4

Impacted Files
Coverage Δ

...lphinscheduler/rpc/common/AbstractRpcCallBack.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.70% <0.00%> (-1.41%)
:arrow_down:

...org/apache/dolphinscheduler/remote/utils/Host.java
40.00% <0.00%> (+2.22%)
:arrow_up:

Continue to review full report at Codecov.

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


status-update-for-non-primary-units

you can fix these failing tests by merging the main branch into yours. The new juju version causes issues retrieving the results of an action


 Is it possible to restrict this app to only detect/recognize the real person's face and discard the image/pictures?

it is not supported.
Please use another model.


[Feature] Add data range threshold to show/hide symbol

What problem does this feature solve?
The chart does not look good with too many data and symbols, so that would be useful to add threshold to show/hide symbol based on the number of data in a certain range. Technically we can already do that by using event function, but this new property makes our life easier.
For example, if threshold is 50 and there are 51 data in the range, hide symbol. If there are less than or equal to 50 data, show the symbol.

What does the proposed API look like?
In the dataZoom property, there should be something like this.
symbolThreashold: {
  threshold: number,
  type: 'show' | 'hide'
 }

threshold  takes the number of data threshold in the range. type takes  'show' | 'hide'.  type  indicates that when show  is taken, show the symbol when a number of data in the range, otherwise hide the symbol. When hide  is taken, hide the symbol when a number of data in the range. otherwise show the symbol.

When data number is large, ECharts automatically calculate the symbols to show. See this demo.

When x axis type is category or time, symbol size is adjusted well. However, when x axis type is value, that does not happen

Yes, you are right.


fix(export): Support typescript namespaces

Fixes #1300

Added nested export scope support
Fixed broken test on ESLint v3 caused by old typescript parser

Coverage increased (+0.2%) to 97.981% when pulling 5a1db48a3d51ef0cfb04e60ba5d7c498d073e557 on bradzacher:export-ts-namespaces into 405900ebe775183588a03447b1fb152481662e3e on benmosher:master.

Coverage increased (+0.2%) to 97.981% when pulling 5a1db48a3d51ef0cfb04e60ba5d7c498d073e557 on bradzacher:export-ts-namespaces into 405900ebe775183588a03447b1fb152481662e3e on benmosher:master.

Coverage increased (+0.2%) to 97.981% when pulling 5a1db48a3d51ef0cfb04e60ba5d7c498d073e557 on bradzacher:export-ts-namespaces into 405900ebe775183588a03447b1fb152481662e3e on benmosher:master.

Coverage increased (+0.2%) to 97.981% when pulling 5a1db48a3d51ef0cfb04e60ba5d7c498d073e557 on bradzacher:export-ts-namespaces into 405900ebe775183588a03447b1fb152481662e3e on benmosher:master.

Coverage increased (+0.2%) to 97.981% when pulling 5a1db48a3d51ef0cfb04e60ba5d7c498d073e557 on bradzacher:export-ts-namespaces into 405900ebe775183588a03447b1fb152481662e3e on benmosher:master.

Hmm, I just pushed up a commit to deal with "Fixed broken test on ESLint v3 caused by old typescript parser" by skipping the test on eslint < 4. Does that mean this PR fixes the test so it passes? If so, please rebase and revert my change in the process :-)

@ljharb - rebased on top!
Yeah the error was happening because in the old version of typescript which got installed with eslint v3 produced a different AST, hence that case wasn't handled. Not sure why it worked fine on the PR then failed on master.


improve messaging payload DX

Current DX requires an object/struct that contains a payload, id and type. While this was initially intended to provide a lightweight cloudevents-like experience and encourage unique IDs for idempotency it likely imposes too much oppinion around messages.
Additionally, SDKs provide methods for deserializing messages e.g. ctx.req.json() which were intended to deserialize the payload, but instead deserialize the entire message, with payload as a property. This behaviour is unintuitive and needs to be updated to match the original intention.

Fixed in nitric v1.0.0


No auth file ?

Hello im strugeling with the Auth file how can i create one is there an layout because there is no automatic authfile

solved Create a empty file and name it for example Auth then copy path and insert path