google_fonts was unable to load font Poppins-Regular

Package
google_fonts
Existing issue?

[X] I checked the existing issues

What happened?
Expected vs actual result:
I have this error every time I launch my flutter application, I don't understand the cause.
Failed to load font with url https://fonts.gstatic.com/s/a/705290b12f58c6d70aafcaaf461dbc3d2f7f19d0f4362af1843b107d95d4960a.ttf: ClientException with SocketException: Failed host lookup: 'fonts.gstatic.com' (OS Error: nodename nor servname provided, or not known, errno = 8), uri=https://fonts.gstatic.com/s/a/705290b12f58c6d70aafcaaf461dbc3d2f7f19d0f4362af1843b107d95d4960a.ttf
Relevant log output
[!] Flutter (Channel stable, 3.10.6, on macOS 13.4 22F66 darwin-arm64, locale en-GB)
    • Flutter version 3.10.6 on channel stable at /Users/graphics01/fvm/versions/3.10.6
    ! Warning: `dart` on your path resolves to /opt/homebrew/Cellar/dart/3.0.6/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/graphics01/fvm/versions/3.10.6. Consider adding /Users/graphics01/fvm/versions/3.10.6/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision f468f3366c (2 weeks ago), 2023-07-12 15:19:05 -0700
    • Engine revision cdbeda788a
    • Dart version 3.0.6
    • DevTools version 2.23.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[!] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /Users/graphics01/Library/Android/sdk
    • Platform android-33, build-tools 33.0.2
    • ANDROID_HOME = /Users/graphics01/Library/Android/sdk
    • ANDROID_SDK_ROOT = /Users/graphics01/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.12.1

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

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.77.3)
    • VS Code at /Users/graphics01/Downloads/Visual Studio Code 2.app/Contents
    • Flutter extension version 3.68.0

[✓] VS Code (version 1.79.0)
    • VS Code at /Users/graphics01/Desktop/Visual Studio Code.app/Contents
    • Flutter extension version 3.68.0

[✓] Connected device (3 available)
    • Cto’s iPhone (mobile) • 00008020-001015A43430003A • ios            • iOS 16.5.1 20F75
    • macOS (desktop)       • macos                     • darwin-arm64   • macOS 13.4 22F66 darwin-arm64
    • Chrome (web)          • chrome                    • web-javascript • Google Chrome 113.0.5672.63

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

Well the file is available for download, so it must be the application doesn't have access to the internet.. Did you follow the troubleshooting steps in the log output?

I'm also having this issue

I'm also having this issue

Closing in favor of https://github.com/material-foundation/flutter-packages/issues/560


Example does not fit

The following example was used multiple times.
{
"name": "examplevm",
"type": "Microsoft.Compute/virtualMachines",
"apiVersion": "2020-06-01",
"properties": {
"storageProfile": {
"dataDisks": [
{
"lun": 0,
"createOption": "Empty",
"diskSizeGB": 1023
},
{
"lun": 1,
"createOption": "Empty",
"diskSizeGB": 1023
},
{
"lun": 2,
"createOption": "Empty",
"diskSizeGB": 1023
}
],
...
Unfortunately, this makes the example for the other case harder to understand.

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

ID: c01dc5ae-fd95-0d3a-bc60-5f6dbd9372b2
Version Independent ID: bf6b4d40-08ba-7655-0547-8db6070c58f4
Content: Define multiple instances of a property - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/copy-properties.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

@edgardott,  Thanks for the feedback! We are currently investigating and will update you shortly.

@edgardott, thank you pointing this out. I have edited the doc and submitted a PR regarding it. It is under review and will be published once approved.


cannot open source file "cblas.h"

I get an intellisense include error that is reproducible by a minimal project  that I can share. The Accelerate framework is somehow not included properly.

Probably worth a different issue, but I have also discovered an import issue when precompiled headers are involved. I added this to the minimal project

Thank you for reporting this and also for creating a simple project that we can work with!
@andreeis just FYI, this is on macOS.  I was surprised to not see any code in cpptools.ts that handled Mac frameworks.  Perhaps it's just passing flags over to cpptools and expecting it to pick it up, but I don't have a mac to test it out on right now.

fyi: I just realised I forgot to add the precompiled header command in the minimal example's CMakeLists.txt ... added now

We have this bug about not passing the iframework switch on Mac. https://github.com/microsoft/vscode-cmake-tools/issues/1178. I'll investigate both.

Can confirm that this is still an issue.

Is there an update on this? As a workaround I am using clangd for my Windows and MacOS projects. A solution that works out of the box for both platforms would be very nice though...

@konradglas Thank you very much for your suggestion of clangd. I didn’t know about it and it fixed the error for me 😁

I recently hit this issue in another form, but suspect it's a similar underlying cause.
@andreeis I do not think the Framework path issue (#1178) is related here. The recommended fix in that issue is to direct CppTools to use compile_commands.json (@bobbrow finds that there's an issue with the framework path args provided by the CMake configuration provider in #2324). However, in the very nice minimal repro provided by @konradglas, the missing header Intellisense error still exists when the CppTools extension uses compile_commands.json.
Given that, I suspect there's some issue with the CppTools extension's handling of macOS frameworks (though would love if someone could confirm or find if it's a known issue), which would also explain why clangd is a viable workaround for this.

I'm running into this error as well and from my understanding, it's specific to the cmake extension.  Before adding the extension, I was able to get around the issue by setting "C_Cpp.errorSquiggles": "enabled" in the settings.json.  With the extension, the intellisense now is unable to resolve certain frameworks, specifically Accelerate on macOS with the same error as the original poster, "cannot open source file "cblas.h""
Maybe because cblas.h is contained in an internal framework VecLib inside Accelerate?


Images without metadata crashes in Livebook

Render of images without metadata fails to render in Livebook :)

This specific issue should be fixed with removal of orientation metadata, I think. I'll check if this happens for other metadata.
Thanks for reporting the issue.

I have a similar problem.

@RyoWakabayashi thanks for reporting it. I'll push a fix soon


AzureAppConfigurationPush task always shows feature flags as requiring being added

The AzureAppConfigurationPush task picks up feature flags from json config files and sets their key prefix and content type automatically during import. This is good but on subsequent push operations it shows that the feature flags need to be written again even if they exist in the app configuration with the same values already. This seems like it might be because the key and content type of the key values in the app configuration now differ from those in the json file so the push process thinks they need to be written again.
Would it be possible to have the logic to check whether feature flags have been imported take into account the logic for setting the key prefix and content type before checking? Or, is there a setting available to do this currently?
We are using the Default file content profile rather than the KVSet profile and using the Ignore-Match import mode.
EDIT: Is the source for the task available anywhere to look at?

Hello @brental I found there is a bug in terms of how we evaluate if the feature flag values in the store and the config file are equal, we'll work on a fix for that.  As a workaround to avoid  feature flags being written on subsequent push operations, might I suggest setting the "Exclude feature flags" option to true

this option specifies whether or not any feature flags in the provided configuration file will be pushed to the store. Please let me know if this helps

Thanks @MaryanneNjeri, I will look into that setting. If that doesn't work as required then we can just leave it importing the feature flags each time until whenever the fix is released. It doesn't cause any major issues having them imported each time.

Hello @brental we have a new version<EMAIL_ADDRESS>with a fix for the issue. Please let me know if this helps resolve the issue.

Thanks @MaryanneNjeri, I will try it out.

Still getting an issue when pushing just a kv set that i have a locked feature flag I was assuming 6.2.0 would have fixed that any ideas or is this a seperate issue? need to be able to push kv sets with locked flags

Hello @CMarshall92Shawbrook what issue are you encountering?


Multiple unexpected exceptions after updating to Patrol 2.3.2

Steps to reproduce

Example Integration Test
// ignore_for_file: prefer-static-class, file_names

import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';
import 'package:futurehome_app/generated/l10n.dart';
import 'package:patrol/patrol.dart';
import 'package:pubdev_registry/fh_ui_new/fh_ui_new.dart';

import '../../_src_utils.dart';

/// KEYS
const ValueKey<String> emailLoginFieldKey = ValueKey<String>('emailLoginFieldKey');
const ValueKey<String> passwordLoginFieldKey = ValueKey<String>('passwordLoginFieldKey');

void main() {
  patrolTest(
    'Log in with correct username and incorrect & empty password',
    nativeAutomation: true,
    (PatrolIntegrationTester $) async {
      /// PREPARE
      await TestHelper.startApp($);

      /// TRIGGER AND TEST
      await _invalidLogin($);

      await Future<void>.delayed(const Duration(seconds: 3));
    },
  );
}

Future<void> _invalidLogin(PatrolIntegrationTester $) async {
  await $(emailLoginFieldKey).enterText(Credentials.email);
  await $.waitUntilVisible(
    $(Credentials.email),
    timeout: const Duration(seconds: 10),
  );

  await $(FhButton).tap();
  await $.waitUntilVisible(
    $(S.current.passwordValidatorEmptyError),
    timeout: const Duration(seconds: 10),
  );

  expect(find.text(S.current.passwordValidatorEmptyError), findsOneWidget);

  await $(emailLoginFieldKey).enterText(Credentials.email);
  await $.waitUntilVisible(
    $(Credentials.email),
    timeout: const Duration(seconds: 10),
  );

  await $(passwordLoginFieldKey).enterText(
    FakeCredentials.invalidPassword,
  );
  await $.waitUntilVisible(
    $(FakeCredentials.invalidPassword),
    timeout: const Duration(seconds: 10),
  );

  await $(FhButton).tap();
  await $.waitUntilVisible(
    $(S.current.authLoginError),
    timeout: const Duration(seconds: 10),
  );

  expect(find.text(S.current.authLoginError), findsOneWidget);

  await $.waitUntilVisible(
    $(S.current.authLoginBtn),
    timeout: const Duration(seconds: 10),
  );
}

Before Patrol update this test normally finished with success. But after updating Patrol to the newest version there is an error output:
The following message was thrown:
Multiple exceptions (2) were detected during the running of the
current test, and at least one was unexpected.

Actual results
After updating Patrol to version 2.3.2, we are encountering an issue where multiple exceptions are being thrown during the execution of our tests. The error message states:
The following message was thrown:
Multiple exceptions (2) were detected during the running of the
current test, and at least one was unexpected.

This behavior is unexpected and has started occurring since the update to the latest version of Patrol. The test suite was working without any problems before the update, so it seems to be a regression introduced in the new version. This issue is affecting our testing workflow and needs to be addressed to ensure the reliability of our tests.
Please let me know if you need any more information or if I can provide additional details to help diagnose and resolve this problem.
Logs

Logs
    :
        : > Task :app:connectedDebugAndroidTest
        : Starting 1 tests on Pixel_3a(AVD) - 14
        :
        : no.futurehome.futurehome_app.MainActivityTest > runDartTest[sdu_integration_tests.src.smoke_tests.01_log_in_tests.01_correct_username_invalid_password_patrol_test Log in with correct username and incorrect & empty password][Pixel_3a(AVD) - 14] FAILED
        :       java.lang.AssertionError: Dart test failed: sdu_integration_tests.src.smoke_tests.01_log_in_tests.01_correct_username_invalid_password_patrol_test Log in with correct username and incorrect & empty password
        :       ══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════
        : Tests on Pixel_3a(AVD) - 14 failed: There was 1 failure(s).
        lis 07, 2023 2:46:52 PM com.android.tools.utp.plugins.host.additionaltestoutput.AndroidAdditionalTestOutputPlugin deviceShellAndCheckSuccess
        WARNING: Shell command failed (1): ls "/sdcard/Android/media/no.futurehome.futurehome_app/additional_test_output"
        ls: /sdcard/Android/media/no.futurehome.futurehome_app/additional_test_output: No such file or directory

        lis 07, 2023 2:46:52 PM com.android.tools.utp.plugins.host.additionaltestoutput.AndroidAdditionalTestOutputPlugin afterAll
        WARNING: Failed to retrieve additional test outputs from device.
        com.android.ddmlib.SyncException: Remote object doesn't exist!
                at com.android.ddmlib.SyncService.pullFile(SyncService.java:341)
                at com.android.ddmlib.internal.DeviceImpl.pullFile(DeviceImpl.java:1083)
                at com.android.tools.utp.plugins.deviceprovider.ddmlib.DdmlibAndroidDevice.pullFile(DdmlibAndroidDevice.kt)
                at com.android.tools.utp.plugins.deviceprovider.ddmlib.DdmlibAndroidDeviceController.pull(DdmlibAndroidDeviceController.kt:254)
                at com.google.testing.platform.executor.DeviceControllerProxy$pull$2.invoke(DeviceControllerProxy.kt:82)
                at com.google.testing.platform.executor.DeviceControllerProxy$pull$2.invoke(DeviceControllerProxy.kt:82)
                at com.google.testing.platform.core.telemetry.common.noop.NoopDiagnosticsScope.recordEvent(NoopDiagnosticsScope.kt:35)
                at com.google.testing.platform.core.telemetry.TelemetryKt.recordEvent(Telemetry.kt:66)
                at com.google.testing.platform.executor.DeviceControllerProxy.pull(DeviceControllerProxy.kt:79)
                at com.android.tools.utp.plugins.host.additionaltestoutput.AndroidAdditionalTestOutputPlugin.copyAdditionalTestOutputsFromDeviceToHost(AndroidAdditionalTestOutputPlugin.kt:222)
                at com.android.tools.utp.plugins.host.additionaltestoutput.AndroidAdditionalTestOutputPlugin.afterAll(AndroidAdditionalTestOutputPlugin.kt:206)
                at com.google.testing.platform.plugin.PluginLifecycle$onAfterAll$1$2$1.invoke(PluginLifecycle.kt:180)
                at com.google.testing.platform.plugin.PluginLifecycle$onAfterAll$1$2$1.invoke(PluginLifecycle.kt:179)
                at com.google.testing.platform.plugin.PluginLifecycleKt$invokeOrThrow$1.invoke(PluginLifecycle.kt:213)
                at com.google.testing.platform.plugin.PluginLifecycleKt$invokeOrThrow$1.invoke(PluginLifecycle.kt:212)
                at com.google.testing.platform.core.telemetry.common.noop.NoopDiagnosticsScope.recordEvent(NoopDiagnosticsScope.kt:35)
                at com.google.testing.platform.core.telemetry.TelemetryKt.recordEvent(Telemetry.kt:105)
                at com.google.testing.platform.core.telemetry.TelemetryKt.recordEvent$default(Telemetry.kt:98)
                at com.google.testing.platform.plugin.PluginLifecycleKt.invokeOrThrow(PluginLifecycle.kt:212)
                at com.google.testing.platform.plugin.PluginLifecycleKt.invokeOrThrow$default(PluginLifecycle.kt:205)
                at com.google.testing.platform.plugin.PluginLifecycle$onAfterAll$1.invoke(PluginLifecycle.kt:179)
                at com.google.testing.platform.plugin.PluginLifecycle$onAfterAll$1.invoke(PluginLifecycle.kt:173)
                at com.google.testing.platform.core.telemetry.common.noop.NoopDiagnosticsScope.recordEvent(NoopDiagnosticsScope.kt:35)
                at com.google.testing.platform.core.telemetry.TelemetryKt.recordEvent(Telemetry.kt:105)
                at com.google.testing.platform.core.telemetry.TelemetryKt.recordEvent$default(Telemetry.kt:98)
                at com.google.testing.platform.plugin.PluginLifecycle.onAfterAll(PluginLifecycle.kt:173)
                at com.google.testing.platform.executor.SingleDeviceExecutor$execute$3.invoke(SingleDeviceExecutor.kt:83)
                at com.google.testing.platform.executor.SingleDeviceExecutor$execute$3.invoke(SingleDeviceExecutor.kt:82)
                at com.google.testing.platform.result.TestResultListenerManager.afterTestSuite(TestResultListenerManager.kt:140)
                at com.google.testing.platform.runtime.android.driver.AndroidInstrumentationDriver.runTestSuite(AndroidInstrumentationDriver.kt:305)
                at com.google.testing.platform.runtime.android.driver.AndroidInstrumentationDriver.run(AndroidInstrumentationDriver.kt:180)
                at com.google.testing.platform.driver.TestDriverProxy$run$1.invoke(TestDriverProxy.kt:110)
                at com.google.testing.platform.driver.TestDriverProxy$run$1.invoke(TestDriverProxy.kt:109)
                at com.google.testing.platform.core.telemetry.common.noop.NoopDiagnosticsScope.recordEvent(NoopDiagnosticsScope.kt:35)
                at com.google.testing.platform.core.telemetry.TelemetryKt.recordEvent(Telemetry.kt:105)
                at com.google.testing.platform.core.telemetry.TelemetryKt.recordEvent$default(Telemetry.kt:98)
                at com.google.testing.platform.driver.TestDriverProxy.run(TestDriverProxy.kt:109)
                at com.google.testing.platform.executor.SingleDeviceExecutor$execute$5.invoke(SingleDeviceExecutor.kt:87)
                at com.google.testing.platform.executor.SingleDeviceExecutor$execute$5.invoke(SingleDeviceExecutor.kt:87)
                at com.google.testing.platform.executor.SingleDeviceExecutor.runUnlessCancelled(SingleDeviceExecutor.kt:105)
                at com.google.testing.platform.executor.SingleDeviceExecutor.execute(SingleDeviceExecutor.kt:87)
                at com.google.testing.platform.RunnerImpl.run(RunnerImpl.kt:108)
                at com.google.testing.platform.server.strategy.NonInteractiveServerStrategy$run$4.invoke(NonInteractiveServerStrategy.kt:80)
                at com.google.testing.platform.server.strategy.NonInteractiveServerStrategy$run$4.invoke(NonInteractiveServerStrategy.kt:79)
                at com.google.testing.platform.core.telemetry.common.noop.NoopDiagnosticsScope.recordEvent(NoopDiagnosticsScope.kt:35)
                at com.google.testing.platform.core.telemetry.TelemetryKt.recordEvent(Telemetry.kt:66)
                at com.google.testing.platform.server.strategy.NonInteractiveServerStrategy.run(NonInteractiveServerStrategy.kt:79)
                at com.google.testing.platform.main.MainKt$main$4.invokeSuspend(Main.kt:67)
                at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
                at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
                at kotlinx.coroutines.EventLoopImplBase.processNextEvent(EventLoop.common.kt:274)
                at kotlinx.coroutines.BlockingCoroutine.joinBlocking(Builders.kt:85)
                at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking(Builders.kt:59)
                at kotlinx.coroutines.BuildersKt.runBlocking(Unknown Source)
                at kotlinx.coroutines.BuildersKt__BuildersKt.runBlocking$default(Builders.kt:38)
                at kotlinx.coroutines.BuildersKt.runBlocking$default(Unknown Source)
                at com.google.testing.platform.main.MainKt.main(Main.kt:66)
                at com.google.testing.platform.main.MainKt.main$default(Main.kt:34)
                at com.google.testing.platform.main.MainKt.main(Main.kt)
                at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
                at java.base/java.lang.reflect.Method.invoke(Method.java:578)
                at com.google.testing.platform.launcher.Launcher.main(Launcher.java:149)

        lis 07, 2023 2:46:52 PM com.google.testing.platform.RunnerImpl$Companion summarizeAndLogTestResult
        SEVERE: Execute no.futurehome.futurehome_app.MainActivityTest.runDartTest[sdu_integration_tests.src.smoke_tests.01_log_in_tests.01_correct_username_invalid_password_patrol_test Log in with correct username and incorrect & empty password]: FAILED
        java.lang.AssertionError: java.lang.AssertionError: Dart test failed: sdu_integration_tests.src.smoke_tests.01_log_in_tests.01_correct_username_invalid_password_patrol_test Log in with correct username and incorrect & empty password
        ══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════
        The following message was thrown:
        Multiple exceptions (2) were detected during the running of the
        current test, and at least one was unexpected.
        ═════════════════════════════════════════════════════════════════

        at pl.leancode.patrol.PatrolJUnitRunner.runDartTest(PatrolJUnitRunner.java:135)
        at no.futurehome.futurehome_app.MainActivityTest.runDartTest(MainActivityTest.java:29)
        java.lang.AssertionError: Dart test failed: sdu_integration_tests.src.smoke_tests.01_log_in_tests.01_correct_username_invalid_password_patrol_test Log in with correct username and incorrect & empty password
        ══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞═════════════════
        The following message was thrown:
        Multiple exceptions (2) were detected during the running of the
        current test, and at least one was unexpected.
        ═════════════════════════════════════════════════════════════════

        at pl.leancode.patrol.PatrolJUnitRunner.runDartTest(PatrolJUnitRunner.java:135)
        at no.futurehome.futurehome_app.MainActivityTest.runDartTest(MainActivityTest.java:29)

        FAILURE: Build failed with an exception.

        * What went wrong:
        Execution failed for task ':app:connectedDebugAndroidTest'.
        See the report at: file:///Users/amika/Documents/smarthome-app/build/app/reports/androidTests/connected/index.html

        * Try:
        > Run with --stacktrace option to get the stack trace.
        > Run with --info or --debug option to get more log output.
        > Run with --scan to get full insights.

        * Get more help at https://help.gradle.org

        BUILD FAILED in 34s
        :
        : Test results saved as file:/Users/amika/Documents/smarthome-app/build/app/outputs/androidTest-results/connected/Pixel_3a(AVD)%20-%2014/test-result.pb. Inspect these results in Android Studio by selecting Run > Import Tests From File from the menu bar and importing test-result.pb.
        :
        : > Task :app:connectedDebugAndroidTest FAILED
        :
        : Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
        :
        : You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
        :
        : See https://docs.gradle.org/7.4/userguide/command_line_interface.html#sec:command_line_warnings
        : 543 actionable tasks: 7 executed, 536 up-to-date
✗ Failed to execute tests of apk with entrypoint test_bundle.dart on emulator-5554 (Gradle test execution failed with code 1) (35.0s)
Exception: Gradle test execution failed with code 1
#0      AndroidTestBackend.execute.<anonymous closure> (package:patrol_cli/src/android/android_test_backend.dart:140:9)
<asynchronous suspension>
#1      DisposeScope.run (package:dispose_scope/src/dispose_scope.dart:46:7)
<asynchronous suspension>
#2      AndroidTestBackend.execute (package:patrol_cli/src/android/android_test_backend.dart:106:5)
<asynchronous suspension>
#3      TestCommand._execute (package:patrol_cli/src/commands/test.dart:277:7)
<asynchronous suspension>
#4      TestCommand.run (package:patrol_cli/src/commands/test.dart:169:23)
<asynchronous suspension>
#5      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#6      PatrolCommandRunner.runCommand (package:patrol_cli/src/runner/patrol_command_runner.dart:321:18)
<asynchronous suspension>
#7      PatrolCommandRunner.run (package:patrol_cli/src/runner/patrol_command_runner.dart:265:18)
<asynchronous suspension>
#8      patrolCommandRunner (package:patrol_cli/src/runner/patrol_command_runner.dart:77:20)
<asynchronous suspension>
#9      main (file:///Users/amika/.pub-cache/hosted/pub.dev/patrol_cli-2.2.2/bin/main.dart:6:20)
<asynchronous suspension>

See the logs above to learn what happened. Also consider running with --verbose. If the logs still aren't useful, then it's a bug - please report it.
Uninstalling no.futurehome.futurehome_app from sdk gphone64 arm64
Uninstalling no.futurehome.futurehome_app.test from sdk gphone64 arm64

Patrol version
patrol: ^2.3.2
Patrol Doctor output

Patrol Doctor output
Patrol CLI version: 2.2.2
Program adb found in /opt/homebrew/bin/adb
Env var $ANDROID_HOME set to /Users/amika/Library/Android/sdk
Program xcodebuild found in /usr/bin/xcodebuild
Program ideviceinstaller found in /opt/homebrew/bin/ideviceinstaller

Flutter Doctor output

Flutter Doctor output
[✓] Flutter (Channel stable, 3.10.5, on macOS 14.1 23B74 darwin-arm64 (Rosetta), locale pl-PL)
    • Flutter version 3.10.5 on channel stable at /Users/amika/fvm/versions/3.10.5
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 796c8ef792 (5 months ago), 2023-06-13 15:51:02 -0700
    • Engine revision 45f6e00911
    • Dart version 3.0.5
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/amika/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/amika/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A240d
    • CocoaPods version 1.13.0

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

[✓] Android Studio (version 2022.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.2.4)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] Connected device (4 available)
    • M2007J20CG (mobile)         • 1025aa50      • android-arm64  • Android 12 (API 31)
    • sdk gphone64 arm64 (mobile) • emulator-5554 • android-arm64  • Android 14 (API 34) (emulator)
    • macOS (desktop)             • macos         • darwin-arm64   • macOS 14.1 23B74 darwin-arm64 (Rosetta)
    • Chrome (web)                • chrome        • web-javascript • Google Chrome 119.0.6045.105

[✓] Network resources
    • All expected network resources are available.

Hi 👋🏻 thanks for using Patrol and raising this issue. Sorry for the problems!
First of all – this "multiple exceptions were thrown" problem is tracked in #951. We should definitely do a better job when it comes to reporting such test failures.
Regarding the main problem – it indeed sounds like a regression. But without more info I can't say anything.

Please let me know if you need any more information or if I can provide additional details to help diagnose and resolve this problem.

The best thing you can do is provide a minimal, reproducible example of this problem. Otherwise there's little chance we'll be able to pinpoint the cause and fix the issue.

@Arkadiusz-futurehome please provide a reproducible sample. Closing this issue for now.


[Ionic v4.0.0-beta.12] Add method to open ion-sliding item

Feature Request
Add a public method to close an ion-sliding item.
Ionic:

   ionic (Ionic CLI)          : 4.2.0
   Ionic Framework            : @ionic/angular 4.0.0-beta.12
   @angular-devkit/core       : 0.9.0-beta.3
   @angular-devkit/schematics : 0.9.0-beta.3
   @angular/cli               : 6.2.4
   @ionic/ng-toolkit          : 1.1.0
   @ionic/schematics-angular  : 1.0.7

System:

   NodeJS : v8.12.0 (/usr/local/bin/node)
   npm    : 6.4.1
   OS     : macOS Sierra

Description
Currently, there is a method to close an ion-sliding item :  item-sliding.tsx source link.
Would like a public method to open an ion-sliding item on click of a button for accessibility.
Demo
In the docs, there is a demo of closing ion-sliding item using a button click.

This request is not visible in the list for some reason.
@manucorporat : Tagging for visibility.
I noticed that you added some bugfixes to item sliding recently.
Please consider this request.

Thanks for your issue! Could you please check if this is still an issue in beta.17? That would be very nice :)


removeInRFC for note sections

https://tools.ietf.org/html/rfc7991#section-2.33.1 describes removeInRFC as having a default of "false", which is fine.  I would like to create a <note> with a removeInRFC attribute set to "true".  How would I do that?
I am cargo-culting the form and adding an IAL doesn't work in either of the following:
--- note_Note_to_Readers
{: removeInRFC="true"}

This attaches the attribute to the first <t> element of the document.  xml2rfc chokes on this.
--- note_Note_to_Readers{: removeInRFC="true"}

This turns the section heading into a <t> element that is part of the abstract.  I think that it might be in a list.  kramdown warns about an IAL being attached to text in this case.  I think that this is failing to match RE_SECTION as a result of the whitespace.

The processing works by cutting up the markdown into sections and then rearranging it again.
Maybe the cutting up could be done in a more intelligent way, so there is a way to place an IAL.
Thinking about that.

The <note tag is generated from the ERB as a "HTML" (XML) element.  So any other attributes would have to go there as well.
The way the "title" attribute ( in V3) is computed right now is a gross hack anyway; thinking about an upward compatible way now to keep the overall syntax in place.  Something like
--- note_About_this_document

vs.
--- to_be_removed_note_About_this_document

Hmm.  About as ugly as it already was.

May brain failed to come up with a better alternative to to_be_removed_note -- will implement this now.


around(:suite) hooks seem completely broken

If you put an around(:suite) hook in your spec_helper.rb file, you seem to always get this warning:
WARNING: `around(:suite)` hooks are only supported on the RSpec configuration object.
This `around(:suite)` hook, registered on an example group, will be ignored.

And then it blissfully ignores your hook, even if it has actually been defined on the RSpec configuration object. Neither of the following syntaxes seem to work:
RSpec.configuration.around(:suite) do |example|

RSpec.configure do |config|
  config.around(:suite) do |example|

To duplicate the issue, just check out this little two-file repository and run rspec in the root:
https://github.com/fimmtiu/rspec-around-suite-bug
~/rspec-around-suite-bug$ rspec
WARNING: `around(:suite)` hooks are only supported on the RSpec configuration object.
This `around(:suite)` hook, registered on an example group, will be ignored. Called
from /.../rspec-around-suite-bug/spec/spec_helper.rb:1:in `<top (required)>'.
WARNING: `around(:suite)` hooks are only supported on the RSpec configuration object.
This `around(:suite)` hook, registered on an example group, will be ignored. Called
from /.../rspec-around-suite-bug/spec/spec_helper.rb:7:in `block in <top (required)>'.
.

Finished in 0.00043 seconds (files took 0.07965 seconds to load)
1 example, 0 failures

We've never supported around(:suite) hooks. Do you want to take a stab at adding support for them?

Really? That explains it. Yeah, things are a bit nuts at the moment but I'll try to find some time next month to have a look at it.

The warning message is a bit misleading.

We've never supported around(:suite) hooks.

vs
WARNING: `around(:suite)` hooks are only supported on the RSpec configuration object.


Custom checkout enhancements

Background
I'm working on a Commerce.js provider with @robbieaverill which uses the new custom checkout feature. See the PR here.
However, the existing structure for custom checkout is not very flexible making it difficult to implement properly. Specifically, it expects that cards and addresses can be separately submitted and associated with a customer before submitting checkout and does not allow an "all-in-one" checkout which includes card details, address details and order details.
Description of changes
In general, this PR makes the card fields and address fields more accessible throughout the checkout UI and also available to the provider in certain checkout actions.

Creates a CheckoutContext to store and update card and address fields
Passes card and address fields to various checkout hooks allowing them to be used by the provider if necessary
Not many changes to types, instead makes use of the existing CheckoutTypes type which has checkout: any property
Adds loading indicator when loading checkout submit
Clears cart after successful checkout submit
Adds an empty useSubmitCheckout hook into the local framework. TODO - does this need to be added for every existing provider because the build fails without it?

Note that there should be no breaking changes in this PR. Currently, Ordercloud is the only provider using the custom checkout and that should still work the same. Commerce.js is coming soon, and I will raise a draft PR for it soon which will show these changes in context.
Final notes
Whilst these changes are to allow Commerce.js provider to use custom checkout, I think that the changes make custom checkout a lot more flexible in general and should benefit future providers. Based on the comment left here, it will immediately help Ordercloud: https://github.com/vercel/commerce/blob/main/framework/ordercloud/checkout/use-submit-checkout.tsx#L16

Hey @cpv123, thanks for the PR! I'm not fully convinced of having a context wrapping the entire app for storing those checkout fields, probably having just the sidebar being wrapped should be enough (I'm not looking at the code right now so idk if its possible). Also as we already have a useCheckout hook that handles operations and data from the checkout, having a useCheckoutContext doesn't feel to good to me, probably we can still create a context on the core with some methods to interact with a state and the useContext hook from the provider can consume that data and use it as needed.
tl;dr: I will take this info and will try to follow up with a solution that fits better our needs, or, if you think this message was clear enough and you want to try something like that, it would be great.
Also there are a few changes (a typo and a type) that would be nice to merge, if you want to create a PR for that, awesome! Otherwise I can add it on a new PR, just let me know.
Thanks for your help!

Hey @cpv123, thanks for the PR! I'm not fully convinced of having a context wrapping the entire app for storing those checkout fields, probably having just the sidebar being wrapped should be enough (I'm not looking at the code right now so idk if its possible). Also as we already have a useCheckout hook that handles operations and data from the checkout, having a useCheckoutContext doesn't feel to good to me, probably we can still create a context on the core with some methods to interact with a state and the useContext hook from the provider can consume that data and use it as needed.
tl;dr: I will take this info and will try to follow up with a solution that fits better our needs, or, if you think this message was clear enough and you want to try something like that, it would be great.
Also there are a few changes (a typo and a type) that would be nice to merge, if you want to create a PR for that, awesome! Otherwise I can add it on a new PR, just let me know.
Thanks for your help!

@goncy thanks for taking a look at this.

Agreed that the context shouldn't wrap the entire app, but just the checkout part of the app (I think that I just copied the UI context without thinking properly)
I will pull out those small changes (the type and typo) and raise them in a separate PR
I think I understand what you're saying about the existing useCheckout hook - the reason I didn't use this was that I assumed that the hook must fetch the checkout data from the backend, whereas I needed access to the data (customer details/address/payment) before it had been submitted anywhere so that it could all be submitted at the end of the checkout. But I think you're saying that the useCheckout hook could do both? I'll take another look tomorrow with this perspective and see what I can do!

Hey @cpv123, thanks for the PR! I'm not fully convinced of having a context wrapping the entire app for storing those checkout fields, probably having just the sidebar being wrapped should be enough (I'm not looking at the code right now so idk if its possible). Also as we already have a useCheckout hook that handles operations and data from the checkout, having a useCheckoutContext doesn't feel to good to me, probably we can still create a context on the core with some methods to interact with a state and the useContext hook from the provider can consume that data and use it as needed.
tl;dr: I will take this info and will try to follow up with a solution that fits better our needs, or, if you think this message was clear enough and you want to try something like that, it would be great.
Also there are a few changes (a typo and a type) that would be nice to merge, if you want to create a PR for that, awesome! Otherwise I can add it on a new PR, just let me know.
Thanks for your help!

@goncy thanks for taking a look at this.

Agreed that the context shouldn't wrap the entire app, but just the checkout part of the app (I think that I just copied the UI context without thinking properly)
I will pull out those small changes (the type and typo) and raise them in a separate PR
I think I understand what you're saying about the existing useCheckout hook - the reason I didn't use this was that I assumed that the hook must fetch the checkout data from the backend, whereas I needed access to the data (customer details/address/payment) before it had been submitted anywhere so that it could all be submitted at the end of the checkout. But I think you're saying that the useCheckout hook could do both? I'll take another look tomorrow with this perspective and see what I can do!

Great about 1 and 2! You might be right with 3, I'm not looking at the code right now so I might not be full aware of the case, but I was thinking about storing the data in a context and using a hook (might not be core's useCheckout, I will have to take a deeper look to it), providers can access the information from it.
Still, this probably needs more thinking on our side to make it correct, so I will take a look at it with the team and let you know!
You can still use this solution for developing the provider and you can update it once we find a way to do it, hopefully it won't be much code on the provider side. If you can do the other small PR with the typos, that would be great.
Will close it by now but I will appreciate if you can create an issue explaining the same thing you added in here so we can keep track on it.
Again, thanks!


Fix -t/--time flag for restart command is not working

Fix #1485

[x] Add an integration test

Signed-off-by: Hanchin Hsieh<EMAIL_ADDRESS>

Can you add an Integ test please?

I'll add it late today

Test is failing
restart_linux_test.go:95: assertion failed: timePostRestart.Sub(timePreRestart).Round(time.Second) is greater than time.Second * 6

The test case of a maximum restart time assertion seems unstable. I think ensuring the least time is enough. So I'm gonna remove the assertion.

Some flaky test(s) related to log drivers are disturbing the CI but not releated to this PR

Thanks


Allow assessment of beta correlations

Moved from Future_work.txt

Likely requires creating new analysis steps for LocusFocus. Need external assistance for this issue from someone who knows R / stats.


Update P2Pool v3.6

Release Notes
Edit: This PR was created 2 minutes after the release 😄

Pretty soon you'll be PRing this before it's released 😅


Add transpiled seek_stress integration test

Closes #76. This is the easiest way to run all the stress tests so hopefully okay until we address #77. seek_stress.rs could be cleaned up (at least deleting all the duplicated types and externs) but that is probably easier to review in a separate PR.

This is the easiest way to run all the stress tests so hopefully okay until we address #77.

I'm not that familiar with the seek stress tests and how they're integrated with meson and everything, but would it be less work overall to just do #77 now?

would it be less work overall to just do https://github.com/memorysafety/rav1d/issues/77 now?

I think this PR should land first since it increases test coverage and might catch errors we make elsewhere. #77 is a cleanup task which is sort of orthogonal to this PR. I suggest we first get test coverage up and then port all tests to Cargo once there are no more important tasks we need to do.

I'm investigating the test failures for the arm7 CI runs. It appears that it surfaces a bug in our port.
Repro (with qemu-system-arm etc. on x86_64 Linux):
$ cargo build --target armv7-unknown-linux-gnueabihf
$ RUST_BACKTRACE=1 target/armv7-unknown-linux-gnueabihf/release/seek_stress -q --threads 1 -i tests/dav1d-test-data/8-bit/data/00000169.ivf --muxer null
thread 'main' panicked at 'attempt to calculate the remainder with a divisor of zero', /rustc/2f6bc5d259e7ab25ddfdd33de53b892770218918/library/core/src/num/mod.rs:1097:5
stack backtrace:
   0: rust_begin_unwind
             at /rustc/2f6bc5d259e7ab25ddfdd33de53b892770218918/library/std/src/panicking.rs:578:5
   1: core::panicking::panic_fmt
             at /rustc/2f6bc5d259e7ab25ddfdd33de53b892770218918/library/core/src/panicking.rs:67:14
   2: core::panicking::panic
             at /rustc/2f6bc5d259e7ab25ddfdd33de53b892770218918/library/core/src/panicking.rs:117:5
   3: seek_stress::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
$ RUST_BACKTRACE=1 target/armv7-unknown-linux-gnueabihf/debug/seek_stress -q --threads 1 -i tests/dav1d-test-data/8-bit/data/00000169.ivf --muxer null
Failed to seek: Success
Failed to seek: Success
Failed to seek: Success
Failed to seek: Success
Failed to seek: Success
Failed to seek: Success

Error manifests differently in CI and between release and debug builds. Since aarch64 passes, this could be 32-bit related.

$ cargo build --target armv7-unknown-linux-gnueabihf
$ RUST_BACKTRACE=1 target/armv7-unknown-linux-gnueabihf/release/seek_stress -q --threads 1 -i tests/dav1d-test-data/8-bit/data/00000169.ivf --muxer null

Did you mean to cargo build without --release and then run .../release/seek_stress?  Does the error still happen if the binary is up-to-date?

Does the error still happen if the binary is up-to-date?

Yup, but my repro instructions were wrong, should be right now. Best guess, something is wrong withivf.rs.

Seems like it's this .wrapping_rem in tests/seek_stress.rs:
1060   │             pts = llround(
1061   │                 (xor128_rand() as libc::c_uint).wrapping_rem(total) as libc::c_double
1062   │                     * spf
1063   │                     *<PHONE_NUMBER>.0f64,
1064   │             ) as uint64_t;

from
❯ RUST_BACKTRACE=1 target/armv7-unknown-linux-gnueabihf/release-with-debug-info/seek_stress -q --threads 1 -i tests/dav1d-test-data/8-bit/data/00000169.ivf --muxer null
thread 'main' panicked at 'attempt to calculate the remainder with a divisor of zero', /rustc/2f6bc5d259e7ab25ddfdd33de53b892770218918/library/core/src/num/mod.rs:1097:5
stack backtrace:
   0: rust_begin_unwind
             at /rustc/2f6bc5d259e7ab25ddfdd33de53b892770218918/library/std/src/panicking.rs:578:5
   1: core::panicking::panic_fmt
             at /rustc/2f6bc5d259e7ab25ddfdd33de53b892770218918/library/core/src/panicking.rs:67:14
   2: core::panicking::panic
             at /rustc/2f6bc5d259e7ab25ddfdd33de53b892770218918/library/core/src/panicking.rs:117:5
   3: core::num::<impl u32>::wrapping_rem
             at /rustc/2f6bc5d259e7ab25ddfdd33de53b892770218918/library/core/src/num/uint_macros.rs:1323:13
   4: seek_stress::main_0
             at ./tests/seek_stress.rs:1061:49
   5: seek_stress::main
             at ./tests/seek_stress.rs:1218:30
   6: core::ops::function::FnOnce::call_once
             at /rustc/2f6bc5d259e7ab25ddfdd33de53b892770218918/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

and from this C tests/seek_stress.rs:
 196   │         pts = FRAME_OFFSET_TO_PTS(xor128_rand() % total);

Is it possible that total is uninitialized in the C version, but in the translated version, we explicitly zero-initialize total, and then when we do % total, we get this division by 0 error?  That seems like it could be a bug in the C code.

Is it possible that total is uninitialized in the C version,

One way to find out is to add something like assert(total); in the C version after the call to input_open(...).

There's UB somewhere at least.  mut total starts as 0, then becomes 6 after input_open(..., &mut total, ...).  Then after one % total with total = 6, total becomes 0 again and % total is run without calling input_open again.  total is only written there in input_open, so I added a let total = total after that to make it immutable, and then seek_stress segfaults instead.

It looks like dav1d compiles with _FILE_OFFSET_BITS set to 64 which means we need to use the 64-bit variants of ftello and fseeko (and operate on libc::off64_t) even on 32-bit builds. I'll put up a separate PR it that turns out to be the fix.

It looks like dav1d compiles with _FILE_OFFSET_BITS set to 64 which means we need to use the 64-bit variants of ftello and fseeko (and operate on libc::off64_t) even on 32-bit builds. I'll put up a separate PR if that turns out to be the fix.

I'd guess that's not the fix, though that seems like it'll need fixing anyways.  The error here is super fragile.  It goes away if total is put into a Box, it goes away if I put dbg!(total)s in seek (the seek call is where total becomes a large number and then 0), or sometimes it prints infinite spaces if I put the dbg!(total)s in the wrong place.
I'm guessing input_open may keep a reference to the total pointer for longer, but I can't find where it does if it does.  I think there's also some weird interaction with the stack, as when total is on the heap it runs fine.  I also tried setting a breakpoint on writes but qemu said hardware breakpoints aren't supported.

The error here is super fragile.

I still think these are 32-bit related problems. I'm fixing some of the same problems we had getting librav1d working for 32-bit. I'll push these as a separate commit. Not sure it makes sense for both of us to stare at this in the meanwhile.

The error here is super fragile.

I still think these are 32-bit related problems. I'm fixing some of the same problems we had getting librav1d working for 32-bit. I'll push these as a separate commit. Not sure it makes sense for both of us to stare at this in the meanwhile.

Okay, hopefully that works.  I already hit a dead-end mostly.


Include form .env

is there any way to include redis host and port into laravel-echo-server.json from .env rather then setting it manually?

https://www.npmjs.com/package/node-env-file and https://github.com/motdotla/dotenv may be useful.


updateGroupMemberInfo not working

The group type setting like this. But the group member still can not update name in GroupMember.

Thanks for reporting.
We will fix related bugs in 2 days and will notify you when we publish bug fixes.


[SPIKE] ✨ swap marked preview renderer for showdown

no issue

adds highlight/footnote features back, maintains full backwards compatibility with LTS markdown

Changes Unknown when pulling 66e151416b9a6e184dcd71f86aa5ae8ebba72971 on kevinansfield:editor-showdown into ** on TryGhost:master**.

Closing in favour of https://github.com/TryGhost/Ghost-Admin/pull/690


Error building app on Android - HELP

it works and builds fine on IOS
but on android I get
Type inference failed: Not enough information to infer parameter R in inline fun <T, R> T.let(block: (T) -> R): R
Please specify it explicitly.
/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/adapty_flutter-0.3.6/android/src/main/kotlin/com/adapty/flutter/AdaptyFlutterPlugin.kt: (162, 101): Unresolved reference: logShowPaywall

What went wrong:
Execution failed for task ':adapty_flutter:compileDebugKotlin'.

Compilation error. See log for more details

im using  adapty_flutter: ^0.3.4

@officialFlutterDeveloper Try the latest version of the library 1.0.7. It will work

@officialFlutterDeveloper Try the latest version of the library 1.0.7. It will work

I thought upgrading the version would help but no luck here's what I get
e: /Users/Craig/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/adapty_flutter-1.0.7/android/src/main/kotlin/com/adapty/flutter/AdaptyFlutterPlugin.kt: (134, 52): Expecting an argument
e: /Users/Craig/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/adapty_flutter-1.0.7/android/src/main/kotlin/com/adapty/flutter/AdaptyFlutterPlugin.kt: (245, 42): Expecting an argument
e: /Users/Craig/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/adapty_flutter-1.0.7/android/src/main/kotlin/com/adapty/flutter/AdaptyFlutterPlugin.kt: (213, 63): Unresolved reference: from
e: /Users/Craig/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/adapty_flutter-1.0.7/android/src/main/kotlin/com/adapty/flutter/AdaptyFlutterPlugin.kt: (495, 60): Unresolved reference: from
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':adapty_flutter:compileDebugKotlin'.

Compilation error. See log for more details

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

also did these steps
https://docs.adapty.io/docs/android-installation
But no luck

@officialFlutterDeveloper hi, I suppose you have Kotlin 1.3.x version in your build.gradle file, please change it to 1.4.32 and the problem will be gone

that was indeed the solution thank you


Set up continuous testing

Set up travis CI, or something like it, for testing.

Let's keep it open till we actually set up travis -- @jgavinray is working on that.

We can close this now that we have that badge.  I'll file another issue to improve test coverage.


Dropdown selection deletion of last letter doesn't work in production, and works ok in development mode

Steps
Dropdown menu with auto complete.

Enter some text
Start ereasing
Last letter will not be able to be deleted
At that time state.value is actually empty string
When new letter is added value is  last letter that remained + new letter written

Expected Result
After deleting last letter, expected result would be to display placeholder value or empty input
Actual Result
Last letter always remains there even if value is empty string
Version
0.68.3
Testcase
I can't reproduce this bug in development mode only in production, you give it a try here: http://hoteli.tmc-solutions.xyz/
Code
<Dropdown
            fluid
            selection
            search
            options={props['location-options']}
            value={props['location-value']}
            placeholder={'Search location'}
            loading={props['location-isFetching']}
            icon={props['location-isFetching'] ? undefined : null}
            onSearchChange={props['location-onSearchChange']}
            onChange={props['location-onChange']}
          />

Container:
        <SearchForm
          location-options={this.state.location_options}
          location-value={this.state.location_value}
          location-onChange={this.location_onChange.bind(this)}
          location-onSearchChange={this.location_onSearchChange.bind(this)}
          ...

I am mostly troubled because this only happens in production and can't be represented in development mode.

Please update to latest, this was fixed in #1722.

Hi @layershifter  thanks for fast response. I upgraded my package to 0.70.0 and now I can finally reproduce this bug in development mode. However, it wasn't mentioned what actually caused this bug specifically?

In #1690 we added minCharacters prop, it's behaviour wasn't implemented correctly and it caused problem with deletion of first character. #1722 fixed this problem, it was released in 0.69.0.
As I see, all works correct at the page that you linked.

@layershifter Thanks! That just reminded me of missing minCharacter is now implemented and other issue I posted some months back are now fixed too, thank you for update!!


Fix volatility inference of functions taking object arguments

A reference to an object Parameter is at most Stable, because it
triggers a table scan.

I think I found a more precise formulation.


Add dataflow creators

Codecov Report
Patch coverage is 100.00% of modified lines.

Files Changed
Coverage

src/gravitorch/creators/dataflow/__init__.py
100.00%

src/gravitorch/creators/dataflow/base.py
100.00%

src/gravitorch/creators/dataflow/dataloader.py
100.00%

src/gravitorch/creators/dataflow/iterable.py
100.00%

:loudspeaker: Thoughts on this report? Let us know!.


HTMLReporter: apply/reset buttons, in module dropdown, disappear when they shouldn't be

QUnit version: 2.0.0
Steps to reproduce:
Let's say I have 3 modules: rules, messages and aria.

See attached screen cast:

Thanks for the report, I believe this is an issue with the dirty checking done here, but don't have much time to dig in further.
@Arkni if you have time to investigate further and open a PR, it would be much appreciated!

@trentmwillis I'll pick this one. Can you assign it to me?

I believe this is an issue with the dirty checking done here,

That what I came across too when trying to dig into the source code.

@Arkni if you have time to investigate further and open a PR

It looks like @shivamdixit already started digging into it and writing a fix.

@Arkni PR shared :)

Thanks @shivamdixit


Error installing integration

Hi,
I've been trying installing this integration, but I always get the following error:
Errore
Impossibile caricare il flusso di configurazione: {"message":"Invalid handler specified"}

The log shows the following:
2022-10-24 18:12:06.919 INFO (SyncWorker_7) [homeassistant.util.package] Attempting install of pymodbus==3.0.0
2022-10-24 18:12:15.199 ERROR (MainThread) [homeassistant.loader] Unexpected exception importing platform custom_components.abb_powerone_pvi_sunspec.config_flow
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.10/site-packages/homeassistant/loader.py", line 722, in get_platform
    cache[full_name] = self._import_platform(platform_name)
  File "/srv/homeassistant/lib/python3.10/site-packages/homeassistant/loader.py", line 739, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
  File "/usr/local/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 992, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/home/homeassistant/.homeassistant/custom_components/abb_powerone_pvi_sunspec/__init__.py", line 15, in <module>
    from pymodbus.client import ModbusTcpClient
  File "/srv/homeassistant/lib/python3.10/site-packages/pymodbus/client/__init__.py", line 5, in <module>
    from pymodbus.client.serial import AsyncModbusSerialClient, ModbusSerialClient
  File "/srv/homeassistant/lib/python3.10/site-packages/pymodbus/client/serial.py", line 10, in <module>
    from pymodbus.client.base import ModbusBaseClient, ModbusClientProtocol
  File "/srv/homeassistant/lib/python3.10/site-packages/pymodbus/client/base.py", line 9, in <module>
    from pymodbus.client.mixin import ModbusClientMixin
  File "/srv/homeassistant/lib/python3.10/site-packages/pymodbus/client/mixin.py", line 19, in <module>
    class ModbusClientMixin:  # pylint: disable=too-many-public-methods
  File "/srv/homeassistant/lib/python3.10/site-packages/pymodbus/client/mixin.py", line 56, in ModbusClientMixin
    count: int = Defaults.Count,
AttributeError: type object 'Defaults' has no attribute 'Count'
2022-10-24 18:12:15.211 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration abb_powerone_pvi_sunspec: Exception importing custom_components.abb_powerone_pvi_sunspec.config_flow

Could you please help me with this?
Thanks

I just noticed you opened the issue, as you can see from the log:
2022-10-24 18:12:06.919 INFO (SyncWorker_7) [homeassistant.util.package] Attempting install of pymodbus==3.0.0
2022-10-24 18:12:15.199 ERROR (MainThread) [homeassistant.loader] Unexpected exception importing platform custom_components.abb_powerone_pvi_sunspec.config_flow

the problem is when HA tries to install pymodbus 3.0.0. Probably it has an issue installing it, and that's a requirement for the component, without it it won't work.


Update tutorial Bahasa Indonesia free-programming-books-id.md

Hacktoberfest notes:

due to volume of submissions, we may not be able to review PRs that do not pass tests and do not have informative titles.
please read our contributing guidelines
be sure to check the output of Travis-CI for linter errors
if this is your first open source contribution, make sure it's not your last!

What does this PR do?
Add Resource(s) | Remove Resource(s) | Add info | Improve Repo
Add resource
For resources
Description
Why is this valuable (or not)?
Valuable
How do we know it's really free?
Free access no permission
For book lists, is it a book? For course lists, is it a course? etc.
book web page
Checklist:

[x] Not a duplicate
[x] Included author(s) if appropriate
[x] Lists are in alphabetical order
[x] Needed indications added (PDF, access notes, under construction)

This feels more like an article than a book, but ok.

thank you @eshellman


fix eof comment for plain js source mounting

fix for #19

I actually already had a local fix for this, which I didn't push: https://github.com/adobe/wskdebug/commit/765b65152d4c1c1166f679c9112ee106ade29442


As a user its is confusing and cumbersome to have three separate budget analyser files

Create a over-arching file that binds the three files together (statement, budget, and ledger book). The three files can continue to exist as separate files, but at least the user can load one file.

This work has gone as far as I'd like to take it right now.  there is now an overall file to give the user a single file to load. This file then has filename references to 4 other files.


Test

Coverage remained the same at 77.393% when pulling a195caac9ba1b4596ce4b06ee40c9467573c3a92 on test into ba1e20b74a9df893b5c62dd9881c58890593fe5a on master.


Convert over to conda-env environments.yml file

Saw this come through in the alerts and thought I'd offer up a conda-env file.

Thanks!

My biggest comment here is how do we support people not using conda env?  I went with the requirements files so that I didn't need to have an environment up and going.

@aterrel agreed.  If I had my druthers, conda-env would have never been a separate project.  At a minimum, it should ship with Anaconda / Miniconda, but I've yet to get any feedback on what needs to happen to make that a reality.  Anything you can do on your end, as a user of conda-env, to help push this through would be greatly helpful to me and our users who are asking for features that are already there.
cc @teoliphant @pzwang


cleanup: rename Manager1 to manager

Signed-off-by: Abirdcfly<EMAIL_ADDRESS>
What type of PR is this?
/kind cleanup

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

Although it seems that each place shows 5/10 checks ok, but the actual 10 tests are successful, see https://github.com/kube-arbiter/arbiter/actions/runs/3403678051, IMO it is a bug in github, URL https://github.com/kube-arbiter/arbiter/actions/runs/3403678051 shows Total duration is -869s....

/lgtm, the changes should not break any test


Change Evaluation Of Myelin Thickness And Area

Will fix #190.
Now, the thickness and area of the myelin is relative to its corresponding axon.
Error handling for equivalent diameter and area values has been added with the _check_measures_are_relatively_valid method.

Coverage decreased (-0.1%) to 81.728% when pulling afe362bc7bcc76643ea97c95a76a21aaef7bad28 on maf88/190-modify-myelin-output-metrics into 05cb434667350c84a4f0a5319d002fa6f5fb881b on master.


Specify minimum OMPL version

Addresses #471

Before creating a pull request

[ ] Document new methods and classes
[ ] Format code with make format

Before merging a pull request

[ ] Set version target by selecting a milestone on the right side
[ ] Summarize this change in CHANGELOG.md
[ ] Add unit test(s) for this change

Unfortunately, OMPL package doesn't support version checking using find_package() until 1.4.0. That said, we instead have to check the version using the version variable of OMPL something like:
find_package(ompl REQUIRED)
if(OMPL_VERSION VERSION_LESS 0.14.0)
  message(STATUS "warning message...")
  return()
endif()

Closing in favor of #473


Make design for mobile

The initial site will not be useable on mobile/small screens. We need a design for a page to show users if they open the site on such a screen.
Acceptance Criteria-

Design for page which tells users to use a bigger screen


Create a process for managing Service Control Policies (SCPs)

Describe the Issue
A clear and concise description of what you want to happen.
Additional Context
Manual process, write a documentation about the process
Acceptance Criteria

[ ] Operational for operating SEA Updates

https://github.com/BC-Gov-PaaS-Platform-Services/aws-ecf-bcgov-overlay-settings-stack/pull/34
https://github.com/BC-Gov-PaaS-Platform-Services/aws-ecf-forge-overlay-settings-stack/pull/32


Keep checksum and offset from produce request

I just remembered an important point @slfritchie made to me when we spoke :). We need to be checksumming the messages on the client side and using that for the storage.
Right now the Erlang disterl client does not checksum when sending and partially because of this we also do not keep the checksum from the kafkaesque client around on the server but instead reproduce it on the server later.
The disterl client needs to add it as a requirement to be included and the decoded produce request in vg_protocol needs to keep it around when returning the record set. Only the id should have to be calculated by the server process.

Basically need to return a map or record for each record instead of just the value.
Should also support key-value pairs in the decode. It is currently supported in the encode if passed a tuple instead of a straight binary.

Fixed.


fix: Remove package lock before updating windows drivers

This was already done for Linux and Mac, and ensures we always get the latest versions without getting locked in or having to hardcode those version numbers.

Today I discovered that this isn't sufficient.  I need to change the logic for this on all three platforms.  😭


Test CXF client with a method referencing class with runtime initialization

Related #4208 https://github.com/quarkiverse/quarkus-cxf/issues/580

Could you please review, @llowinge?

Looks great other then found little typing issue.

Ahh, i've haven't sent the review. Doesn't matter, it is harmless.


Wrong youtube song links generated

What is the purpose of your issue?

[x] Bug
[ ] Feature Request
[ ] Question
[ ] Other

Description
I've ran the following command:
/usr/local/py3shit/pip3/bin/spotdl -b http://open.spotify.com/album/3wKmDPvkPQfd32lprzJ42I

It resulted in the following file: http://oscomp.hu/depot/tropical-hits-party.txt
Which is apparently OK.
Then i've ran the following command:
/usr/local/py3shit/pip3/bin/spotdl --list tropical-hits-party.txt --write-m3u

It yielded this file: http://oscomp.hu/depot/tropical-hits-party.m3u
Which contains absolutely unrelated songs.
Log
External link, due to vast size: http://oscomp.hu/depot/spotdl.log

Try v3. You'll have to write up the funnality yourself, but it should have virtually no errors. V3 had simpler library usage


snappy

What steps will reproduce the problem?
1.i write a c++ program.
2.in linux ,g++ -o sa Main.cpp libleveldb.a -lpthread

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
leveldb 1.14.0, red hat

Please provide any additional information below.
this is problem:
libleveldb.a(table_builder.o): In function
`leveldb::TableBuilder::WriteBlock(leveldb::BlockBuilder*,
leveldb::BlockHandle*)':
table_builder.cc:(.text+0x6a8): undefined reference to
`snappy::MaxCompressedLength(unsigned long)'
table_builder.cc:(.text+0x6e2): undefined reference to
`snappy::RawCompress(char const*, unsigned long, char*, unsigned long*)'
libleveldb.a(format.o): In function
`leveldb::ReadBlock(leveldb::RandomAccessFile*, leveldb::ReadOptions const&,
leveldb::BlockHandle const&, leveldb::BlockContents*)':
format.cc:(.text+0x5de): undefined reference to
`snappy::GetUncompressedLength(char const*, unsigned long, unsigned long*)'
format.cc:(.text+0x64e): undefined reference to `snappy::RawUncompress(char
const*, unsigned long, char*)'
collect2: ld returned 1 exit status

i think may be snappy problem,but i dont kown what to do

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 7 May 2014 at 1:32

I solved this problem.
Add "-lsnappy" when you build your c++ program.
If you don't have snappy library, build snappy.

Original comment by<EMAIL_ADDRESS>on 11 Feb 2015 at 6:09


Feature/docker tests

Using docker based tests on travis ci
Remove the old NATS server mock-up

Coverage increased (+11.6%) to 85.263% when pulling 7a987a177da84b9b926be09b1bd0baeb08b357a3 on feature/docker-tests into 98111f9cb2ea150c1f784fd7ca0a9f6628afdaf5 on develop.

Coverage increased (+11.6%) to 85.263% when pulling 7a987a177da84b9b926be09b1bd0baeb08b357a3 on feature/docker-tests into 98111f9cb2ea150c1f784fd7ca0a9f6628afdaf5 on develop.


有个问题

使用php start.php start开启服务后 不关闭是一直可以正常使用的 但使用cmd + c 关闭服务 会一直提示下列warning, 是我哪里配置错误了吗
环境: docker
PHP版本: php:8.0.0-cli-alpine
Warning: EventBase::loop(): Failed to invoke event callback in /www/vendor/workerman/workerman/Events/Event.php on line 195

Fixed in workerman 4.0.18.
Please upgrade workerman.
composer require workerman/workerman ^4.0.18

Fixed in workerman 4.0.18.
Please upgrade workerman.
composer require workerman/workerman ^4.0.18


Tag latest on DockerHub is not up to date

Hi! The latest Tag on DockerHub is not up to date, it is 5 Months old, see attached Screenshot.

Thanks, this was on purpose to see if there was anything else wrong before people would just pull it. And, it seems that there is. I will update latest once #18 is fixed.

@dgraziotin: Latest is in snc, I will close this Issue.


What am I doing wrong?

I think I'm very clearly doing something wrong, as snippets just dont work at all.
If i go to a new file, :setf javascript and I type: xxx and hit tab, the cursor doesnt move at all, and no snippet appears, as if it were a <NOP>. <S-Tab> does the same thing.
-- https://github.com/L3MON4D3/LuaSnip/blob/master/DOC.md#snipmate
-- examples: https://github.com/honza/vim-snippets

return {
  'L3MON4D3/LuaSnip',
  enabled = true,
  version = '2.*',
  build = 'make install_jsregexp',
  config = function()
    local ls = require('luasnip')

    ls.setup({})

    require('luasnip.loaders.from_snipmate').lazy_load({
      paths = '~/.config/nvim/snippets',
    })

    vim.keymap.set({'i'}, '<Tab>', function() ls.expand() end, { silent = true })
    vim.keymap.set({'i', 's'}, '<Tab>', function() ls.jump(1) end, { silent = true })
    vim.keymap.set({'i', 's'}, '<S-Tab>', function() ls.jump(-1) end, { silent = true })
    vim.keymap.set({'i', 's'}, '<C-e>', function()
      if ls.choice_active() then
        ls.change_choice(1)
      end
    end, { silent = true })
  end
}

and in my ~/.config/nvim/snippets/javascript.snippets:
snippet xxx
	something

Can't spot anything wrong with it, you could try the following:

set a high log-level before calling lazy_load (ls.log.set_loglevel("info")), and then check the log (ls.log.open()). It should contain messages about lazy-loading some files, and actually loading snippets from specific filetypes.
Immediately open a file with filetype javascript
Set filetype via set filetype javascript, I have never tried whether setf also calls the autocommands registered for Filetype
Make sure the code is executed, by printing something

set filetype javascript oddly doesn't work... E518: Unknown option: javascript.
When I use set filetype=javascript however, it logs this:
INFO  | snipmate-loader: Registering lazy-load-snippets:
      | {
      |   javascript = { "/Users/zesty/.config/nvim/snippets/javascript.snippets" }
      | }
INFO  | snipmate-loader: Loading lazy-load-snippets for filetype ``
INFO  | lua-loader: Loading lazy-load-snippets for filetype ``
INFO  | vscode-loader: Loading lazy-load-snippets for filetype ``
INFO  | lua-loader: Loading lazy-load-snippets for filetype `javascript`
INFO  | snipmate-loader: Loading lazy-load-snippets for filetype `javascript`
INFO  | snipmate-loader: Adding 1 snippets and 0 autosnippets for filetype `javascript` from /Users/zesty/.config/nvim/snippets/javascript.snippets
INFO  | vscode-loader: Loading lazy-load-snippets for filetype `javascript`
INFO  | lua-loader: Loading lazy-load-snippets for filetype `fidget`
INFO  | snipmate-loader: Loading lazy-load-snippets for filetype `fidget`
INFO  | vscode-loader: Loading lazy-load-snippets for filetype `fidget`
INFO  | lua-loader: Loading lazy-load-snippets for filetype `cmp_menu`
INFO  | snipmate-loader: Loading lazy-load-snippets for filetype `cmp_menu`
INFO  | vscode-loader: Loading lazy-load-snippets for filetype `cmp_menu`

And the behavior is the same, if I push xxx it basically 's as if my tab key is broken

I have also disabled every single plugin and the same thing occurs 🤔

Interestingly, if I do <C-k> it works fine. It really doesn't work with <Tab> however... even if all other plugins are off.

After looking at someone else's config I changed jump to expand_or_jump and now it seems to work (so far)... maybe that should be updated in docs if thats not how those functions are supposed to be used?
I will keep testing

Oh, I missed that <tab>-binding :sweat_smile:
Yeah, you probably want only expand_or_jump to be on <tab>, not jump alone as well.
What is your config now?

Here's my current full config where the  key is completely /dead. The only thing it CAN do now is expand snippets 💀
-- https://github.com/L3MON4D3/LuaSnip/blob/master/DOC.md#snipmate
-- examples: https://github.com/honza/vim-snippets

return {
  'L3MON4D3/LuaSnip',
  enabled = false,
  event = 'VeryLazy',
  version = '2.*',
  build = 'make install_jsregexp',
  config = function()
    local ls = require('luasnip')

    ls.setup({})

    require('luasnip.loaders.from_snipmate').lazy_load({
      paths = '~/.config/nvim/snippets',
    })

    vim.keymap.set('i', '<Tab>', function() ls.expand_or_jump() end, { silent = true })
    vim.keymap.set('i', '<S-Tab>', function() ls.jump(-1) end, { silent = true })
    vim.keymap.set('i', '<C-e>', function()
      if ls.choice_active() then
        ls.change_choice(1)
      end
    end, { silent = true })
  end
}

Ahhh, it's probably that the expand_or_jump-mapping is only bound in INSERT, as opposed to INSERT and SELECT, which means that it won't work if the insertNode contains text which is selected.
tldr, just do {"i", "s"} instead of "i", for all mappings actually.

I don't think its that, let me explain again:

I disabled all other plugins
I ensured nothing is conflicting with <Tab>:

The only thing listed is <Tab> * <Lua 336 ...luasnip.lua:19>
-- https://github.com/L3MON4D3/LuaSnip/blob/master/DOC.md#snipmate
-- examples: https://github.com/honza/vim-snippets

return {
  'L3MON4D3/LuaSnip',
  enabled = true,
  event = 'VeryLazy',
  version = '2.*',
  build = 'make install_jsregexp',
  config = function()
    local ls = require('luasnip')

    ls.setup({})

    require('luasnip.loaders.from_snipmate').lazy_load({
      paths = '~/.config/nvim/snippets',
    })

    vim.keymap.set({'i', 's'}, '<Tab>', function() ls.expand_or_jump() end, { silent = true })
    vim.keymap.set({'i', 's'}, '<S-Tab>', function() ls.jump(-1) end, { silent = true })
    vim.keymap.set({'i', 's'}, '<C-e>', function()
      if ls.choice_active() then
        ls.change_choice(1)
      end
    end, { silent = true })
  end
}

When I have <Tab> set to expand_or_jump(), and the config above, I cannot use the tab key at all, whether its insert mode, select mode, etc. It behaves as if its a  or my key is actually broken.
The only thing that the tab key works for, is expanding a snippet.
So if I have a snippet for xxx -> something
I can do this:
xxx| = tab WILL expand
x| = tab will not move, or insert tabs. its broken. Likewise, I can just have a completely empty file:
| and tab will still just not insert tabs

The other option is this:
    vim.keymap.set({'i', 's'}, '<Tab>', function() ls.expand() end, { silent = true })
    vim.keymap.set({'i', 's'}, '<Tab>', function() ls.jump(1) end, { silent = true })
    vim.keymap.set({'i', 's'}, '<S-Tab>', function() ls.jump(-1) end, { silent = true })
    vim.keymap.set({'i', 's'}, '<C-e>', function()

Notice the extra keymap and using expand() instead of expand_or_jump()
Using this way, it's identical to the first problem, except now in addition it wont tab EVEN if there is an xxx snippet. In other words, the tab is now useless in insert mode, whether theres a snippet or not.

Ah, you want some kind of supertab-mapping, okay.
Luasnip doesn't have something like this built in, but you can either find something like this in other ppls config, or cobble something together yourself: ls.expand_or_jumpable() (I think that's the name, check doc if it doesn't work) returns whether you can jump or expand right now, and you could insert a tab, or expand_or_jump based on that.
I think you should find lots of examples by searching for "if ls.expand_or_jumpable() then" on github

awesome thanks!

Ill close this and paste my answer here when i get it

Ok this is how I solved it:
-- examples: https://github.com/honza/vim-snippets/tree/master/snippets
-- snippet format: https://github.com/garbas/vim-snipmate/blob/master/doc/SnipMate.txt#L228

return {
  'L3MON4D3/LuaSnip',
  enabled = true,
  event = 'VeryLazy',
  version = '2.*',
  build = 'make install_jsregexp',
  config = function()
    local ls = require('luasnip')

    -- https://github.com/L3MON4D3/LuaSnip/blob/master/DOC.md#config-options
    ls.setup({
      update_events = 'TextChanged,TextChangedI',
    })

    require('luasnip.loaders.from_snipmate').lazy_load({
      paths = '~/.config/nvim/snippets',
    })

    local function interp(k) vim.api.nvim_feedkeys(vim.api.nvim_replace_termcodes(k, true, false, true), 'n', false) end

    vim.keymap.set({'i', 's'}, '<Tab>', function()
      if ls.expand_or_jumpable() then ls.expand_or_jump()
      else interp('<Tab>') end
    end)

    vim.keymap.set({'i', 's'}, '<S-Tab>', function()
      if ls.jumpable(-1) then ls.jump(-1)
      else interp('<S-Tab>') end
    end)
  end
}

Now the problem is getting it to work with tabout, but I'm doing that here (in case anyone else needs this)
https://github.com/abecodes/tabout.nvim/issues/57

Looks good 👍👍

@L3MON4D3 ok i realize this isn't your plugin (tabout) but at a higher level... I'm confused about the best way to set this up. So far after trying about an hour I am not getting Tabout+Luasnip to interact.
My main question is...

should tabout config go in luasnip maps, or luasnip go in tabout config?

It seems the latter is easier so thats what I started with. Inside Luasnip I just didn't define any mappings at all, and in tabout I did this:
    local ls = require('luasnip')

    local function replace_keycodes(c)
      return vim.api.nvim_replace_termcodes(c, true, true, true)
    end

    function _G.tab_binding()
      if ls.expand_or_jumpable() then
        return replace_keycodes('<Plug>(luasnip-expand-or-jump)')
      else
        return replace_keycodes('<Plug>(Tabout)')
      end
    end

    function _G.s_tab_binding()
      if ls.jumpable(-1) then
        --
      else
        return replace_keycodes('<Plug>(TaboutBack)')
      end
    end

    vim.api.nvim_set_keymap('i', '<Tab>', 'v:lua.tab_binding()', { expr = true })
    vim.api.nvim_set_keymap('i', '<S-Tab>', 'v:lua.s_tab_binding()', { expr = true })

But when I do this, the snippet expansion actually just prints out <Plug>(luasnip-expand-or-jump) (lol)
I've also tried every combination of calling the function directly, etc, that I can think of. It has any number of outcomes...

it inserts v:null for the snippet
it has a stack trace exception

Is there a way to do this cleanly/properly which isn't a bunch of antipatterns? Something about the way I'm doing this just feels like it's the completely wrong way, even if i get it working somehow.
I'm assuming Im supposed to leverage the  stuff...?


Move from Heroku to Dokku (on Scaleway)

Moving the two apps from Heroku to Dokku (running on a dedicated DEV1-S instance at aoc.lewagon.engineering):
ssh<EMAIL_ADDRESS>apps:list

I added @pil0u's SSH key with:
curl https://github.com/pil0u.keys | ssh root@aoc dokku ssh-keys:add "pil0u"

If more people need access, ping me here.
I advise you to open your ~/.ssh/config and add:
Host aoc
  Hostname aoc.lewagon.engineering
  User dokku

That way you can run simpler commands like:
# Getting logs (of prod or staging app)
ssh aoc logs aoc --tail
ssh aoc logs aoc-staging --tail # not repeating below, but you get the gist.

# Environment variables
ssh aoc config aoc

# Running processes
ssh aoc ps:report aoc

# Start a Rails console
ssh -t aoc run aoc bin/rails c

This PR adds two GitHub actions to have CI/CD of:

Production app aoc.lewagon.community on release branch
Staging app aoc-staging.lewagon.community on main branch

@Aquaj are you fine with using your SSH key as well to get access to the instances?

ℹ FYI I moved the two database from Heroku to Dokku with:
pg_dump -Fp --clean --no-acl --no-owner $(heroku config:get DATABASE_URL --app lewagon-aoc) > tmp/lewagon-aoc.heroku.dump
ssh aoc postgres:expose aoc
ssh aoc postgres:connect aoc < tmp/lewagon-aoc.heroku.dump
ssh aoc postgres:unexpose aoc

pg_dump -Fp --clean --no-acl --no-owner $(heroku config:get DATABASE_URL --app lewagon-aoc-s) > tmp/lewagon-aoc-s.heroku.dump
ssh aoc postgres:expose aoc-staging
ssh aoc postgres:connect aoc-staging < tmp/lewagon-aoc-s.heroku.dump
ssh aoc postgres:unexpose aoc-staging

@Aquaj FYI you should have access to the apps :)
This is the alias I set up in my .zshrc:
alias aoc="ssh<EMAIL_ADDRESS>
Commands now look like:
aoc logs aoc --tail          # aoc logs aoc-staging --tail
aoc config aoc               # aoc config aoc-staging
aoc -t run aoc rails c       # aoc -t run aoc rails c
aoc postgres:info aoc        # aoc postgres:info aoc-staging
aoc -t postgres:connect aoc  # aoc -t postgres:connect aoc-staging


Always in editing mode when opening a note that contains a query at the top

What happened?
When the first thing within a note is a dataview query, you will always be in "Edit this block" mode after opening the note. This is annoying, because you have to focus something else / move the cursor elsewhere before you can see the results.

As a workaround, you can add an empty line at the top
DQL
No response
JS
No response
Dataview Version
0.5.47
Obsidian Version
1.4.5
OS
Windows

Oops, nevermind, it seems this is fixed through switching off the "Always focus new tabs" option. My bad!


Add network parameter to withdraw request

POST /wapi/v3/withdraw.html
supports not mandatory parameter network, but BinanceApiRestClient doesn't allow to pass it to binance.
Please, add "network" to withdraw method parameters

Pull request for network parameter.
Pull request for all missing parameters.

Pull request for network parameter.
Pull request for all missing parameters.


Not able to find out the schematics of GEVCU7

Help : Not able to find out the GEVCU schematics . gevcu.org is down and other information about the hardware

I just uploaded a PDF of the schematic. Yes, gevcu.org is down. EVTV itself never controlled that domain. It was registered by one of the GEVCU4 developers. It seems that person quit paying for it and then the domain was bought by a squatter. So, there isn't a lot I can do to correct that right now.


Add more APIs in SignalR Service v1

Add more APIs supported and minor updates

Add/Remove/Send/Close connection
Remove user from all groups
Service health
Add response code for GET methods
Minor uniform expression

@JialinXin : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Bootstrap the repo

Addresses HAC-564
Features:

Bootstraps a working plugin with ConsoleDot

This is done through a webpack proxy to the staging environment (which needs the VPN to access)
Renders a dynamic navigation that can be supply via a webpack extension plugin (restart required for them to take effect) -- see ./config/plugins.js
Readme should have all the information to get started with this "unique" setup

Added jest -- configured to run with @testing-library and has a dummy test

Needed:

[ ] Linter -- we have none; what configuration might be something the process group can help with
[ ] Cypress -- there are some issues with configuration, I'll continue trying to work on this but it shouldn't block this work

/cc @jhadvig


selfhost/typechecker: Fix panicking Optional unwrap in typecheck_if

In selfhost/main.jakt:54 there are these lines:
if not file_name.has_value() {
  eprintln(...)
  eprintln(...)
  return 1
}

That return 1 makes the block have a yielded type without having
a yield span. I've changed typecheck_if to find the actual
yield span and unwrap it when producing the error once we know it has
a value.

Hmm, wait, there's more code that assumes find_yield_span() will always succeed if there's a yielded type.
It seems wrong that return statements affect the yielded type in the first place.
cc @jntrnr @alimpfard


bug: connection issues with Gnosis Safe via WalletConnect after wagmi/viem upgrade

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
1.4.12
Current Behavior
Hi all,
We recently upgraded our wagmi and viem versions and have since encountered connection issues with Gnosis Safe via WalletConnect. Additionally, there's a reported issue with connecting from the Rainbow wallet on mobile devices.

Previous Versions: wagmi 1.3.9, viem 1.4.1
Upgraded Versions: wagmi 1.4.12, viem 1.19.15

The primary issue observed is a JSON is not a valid request object. error. This seems to occur when you try to connect to a Gnosis Safe via WalletConnect.
Expected Behavior
User should be able to connect via wallet connect with gnosis safe to our app, visit app here
Steps To Reproduce

Visit https://jokerace.xyz/ and copy wallet connect link ( use polygon as connected network )
Head over to gnosis safe account and try to connect with wallet connect to app

Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response

Thanks for reporting. This issue is temporarily closed due to lack of information. Please provide a minimal reproducible example and reopen this issue.


proxy support

Is it possible to use pkgdev (especially manifest - which pulls distfiles) behind a proxy.
env variable http_proxy / http_proxy do not seem to be honored right now and pkgdev.conf also does not seem to contain any proxy settings.

At some point I have to ebuild xxx.ebuild manifest before I can execute a pkgdev commit, and it would be great if pkgdev could support proxies!


Animated APNG/WebP Support?

It doesn't seem like the boop supports files that isn't png extension. Is it possible to have the boop button use a converted png instead?

Well I've tried multiple Steam and non-Steam games and assets and none of them have any results. For example this: https://www.steamgriddb.com/hero/26934

Works for me, can you post your system information? OS, Browser, where/how Steam is installed, etc.


Image output improvements

@IEvangelist - It seems to be working great for me! Want to update the branch?

@IEvangelist - It seems to be working great for me! Want to update the branch?

Done, thank you!


adding faust-prometheus exporter

@juliusv
@brian-brazil
I added library that can be plugged into FAUST, the kafka streaming framework written in python by RobinHood and will directly expose Faust metrics of the app in prometheus format.

This isn't an application it's a library, so it'd go down in the list at the bottom.
In terms of improving your library, I have the following suggestions:
Don't have 3 different metrics only differing in labels. messages_received_per_topics_partition is sufficient for example, and can then be called faust_received_messages.
Latencies should be in seconds, not milliseconds.
Avoid "total" in metric names, it is redundant.
Naming is generally inconsistent, e.g. topic_messages_sent vs total_sent_messages. In that case a single metric called faust_sent_messages with all the labels would suffice.
Rebalances sounds like a counter, not a gauge.
This code shouldn't be touching the GC and other default metrics the Python client provides, it should only be a collector and should definitely not be poking around in REGISTRY and other implementation internals of the client library. As-is this code will silently break any other Prometheus instrumentation that is loaded in before it.
Nor should a collector like this be doing exposition - that's a separate concern that's up to the application developer.


BC Sponsor Questions

Added two sponsor questions from Briar Cutter.

I'll do same for this one like I did for the other one

closing since changes resolved and input in #229


Optimized implementation of bound c methods

Fixes #5062

Based on some micro-benchmarks:

there's no measurable difference in calling the bound c method.
making the bound C method is twice as fast.


1803 clients seem to work just fine with ConfigMgr 1710

Can you elaborate on what it means for a version of Windows 10 to be "not supported as a client?"
We are on ConfigMgr 1710 and Windows 10 1803 clients seem to work just fine (OSD, app deployment, inventory collection, remote control, etc), despite the table showing they are not supported on ConfigMgr 1706 and 1710.

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

ID: dc732ec0-eb14-8da2-7688-dd74a72cdae5
Version Independent ID: a93682ff-2984-38e0-5a0d-6f77c1c9e5db
Content: Support for Windows 10 - Configuration Manager
Content Source: sccm/core/plan-design/configs/support-for-windows-10.md
Service: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

As I always say with this topic, the supported configuration relates to what we have tested and verified as functional. If it’s not in the matrix, that means we haven’t tested it. We have to document things and that comes across as very binary: supported or not supported. There’s likely a lot of product functionality that technically works, but we haven’t tested it. So there’s some risk for customers. Thus we don’t officially support it. In this particular case, there were some bugs that we fixed in the SCCM 1802 final release for OS deployment and software updates with Windows 10 version 1803.
We have no plans to change the support matrix so I'm closing this issue.


Complete the default namespace work

There were still several instances of the 'xs' namespace that were hard coded.
fixes #120

The 2 rollbacks were made with comments as to why the ns: prefix is retained in those cases.

@stevedlawrence Looks like you +1 may have been erased when @scholarsmate requested your review, do you want to throw it back in or is this good to merge now?

@stevedlawrence Looks like you +1 may have been erased when @scholarsmate requested your review, do you want to throw it back in or is this good to merge now?

@Shanedell, just wanted to give Steve and Mike a chance to do a final review with the requested changes.


Add support for more events

It would be nice if you could register a function call for events like slidestart and slidestop

maybe this could be useful : https://github.com/angular-ui/ui-slider/pull/104


NamedArguments not working in Detekt 1.23.6

Expected Behavior
I expect if a method is being call without enough named arguments, Detekt will complain about it
Observed Behavior
It seems that the rule is not working at all. I have set the threshold to 1 and I have cases in my code with two arguments that are not call with named arguments and are completely ignored.
Steps to Reproduce
This is the configuration I'm applying:
complexity:
  NamedArguments:
    active: true
    threshold: 1

and this is one example of my method:
restClient.doSomething(argumentOne, argumentTwo)

Your Environment

Version of detekt used: 1.23.6
Version of Gradle used (if applicable): 8.5
Gradle scan link (add --scan option when running the gradle task):
Operating System and version: macOS (but ocurring everythere)
Link to your project (if it's a public repository):

Are you running the rule with Type Resolution?

No, I was using detekt default gradle task. It seems this rule need Type Resolution active. I will create my own gradle task including type resolution. Thanks for the hint!


Top Banner displayed 'You must switch to Mainnet' but I needed to be on Rinkeby

Describe the bug
Top Banner displayed 'You must switch to Mainnet' but I needed to be on Rinkeby
To Reproduce
Steps to reproduce the behavior:

Go to a pay party created on Rinkeby
Be on Mainnet in wallet and app
Use 'You Must Switch Network To Vote' button to switch to Rinkeby from mainnet in wallet
See Top Banner displays 'You have Rinkeby selected and you need to be on Mainnet'

Expected behavior
Top Banner should say 'You have Mainnet selected (in app) and need to be on Rinkeby'
Screenshots

Desktop (please complete the following information):

OS: macOS Monterey 12.0.1
Browser: Chrome
Version: 100.0

Additional context
Add any other context about the problem here.

I think they're two different bugs but both related to network issues. One
is about the mid-screen network switch banner which doesnt switch your
network. The other is about the top-screen banner that does not correctly
detect the network you're in.
On Wed, Apr 13, 2022, 12:48 PM gtcsameer @.***> wrote:

Thanks for this issue Umar! Just curious, how is this different from #184
https://github.com/moonshotcollective/pay.party/issues/184; personally,
I think these two issues seem to be related to the same bug. Are you just
splitting both parts of the bug into two separate issues?
—
Reply to this email directly, view it on GitHub
https://github.com/moonshotcollective/pay.party/issues/185#issuecomment-1098270877,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKO2NIWLVMXB63UE75T3SGDVE33EFANCNFSM5TIBC6YA
.
You are receiving this because you authored the thread.Message ID:
@.***>


First pass at parameterizing script inputs used in tp53_analysis.sh

The primary goal of this PR is to allow control of input and output paths and to e.g. enable execution on a file staging cluster setup.
All changes should be 100% backwards compatible, but I did not find a test suite that I could run to doubly confirm.
Also addresses some quirks when e.g. running on a file staging cluster, where files are created in temporary directories (so full path to classifier_coefficients.tsv declared in files may no longer exist). If the file DNE, it looks for a copy local to the current classifier folder structure.
I added an argument --x_as_raw to pancancer_classifier.py to handle the special casing that was keyed based upon using default value for --x_matrix; which is raw and causes pancan_rnaseq_freeze.tsv.gz to be used. if you had specified pancan_rnaseq_freeze.tsv.gz directly as input, then the 'raw' actions were never performed; now you can do both. Probably a better, more descriptive, terminology than raw could be proposed.
Add --drop_x_genes to pancancer_classifier.py to enable custom list of genes to be dropped, similar to rasopathy_genes. Also explicitly set matplotlib.use('agg') to work on headless systems.
An upgrade to pandas 0.24.0+ will give 'infer' option for compression in to_csv() which is now currently being worked around for gzip outputs. Pandas currently pinned at 0.23.0 in environment.yml.
In cases of jupyter notebooks that are run as scripts, I parameterize the execution with environmental variables.

Another benefit/goal is to enable usage inside of Galaxy, example TP53 workflow:

Thanks for the contribution @blankenberg ! My PhD defense is one week from today, so there will be some delays in giving this a thorough look

I am just closing out old PRs. Thanks again for your previous efforts.


Fix bi-modality in size benchmark results

Initial guess is that Android and iOS numbers are published under the same name. They should be using different names.

Fixed in https://github.com/flutter/cocoon/commit/9690381776bc4cee3187797e2e3b6eefea765237