The targeted input element must be the active input element

Steps to reproduce
Create a new project and a screen with this app bar code below, and run it on web because it only happens on web.
Expected results
When i hover the text field it should work perfectly.
Actual results
It stopes the debugger
Code sample
Code sample

class OverviewTopBar extends StatelessWidget implements PreferredSizeWidget {
  const OverviewTopBar({super.key});

  @override
  Size get preferredSize => Size.fromHeight(kToolbarHeight);

  @override
  Widget build(BuildContext context) {
    final width = MediaQuery.sizeOf(context).width;
    return AppBar(
        leading: _searchTextField(context),
        leadingWidth: width * 0.3,
      );
  }

  _searchTextField(BuildContext context) {
        return SizedBox(
          height: 36,
          child: TextField(
            // controller: state.searchController,
            decoration: InputDecoration(
              hintText: context.tr.search,
            ),
          ),
        );
  }
}

Screenshots or Video

Screenshots / Video demonstration
https://github.com/user-attachments/assets/0c9b4b93-fe49-45f8-b90a-59c292d89749

Logs
Logs
DartError: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 288:3     throw_
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               assertFailed
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               _computeOffsetForInputs
lib/_engine/engine/pointer_binding/event_position_helper.dart 38:14             computeEventOffsetToTarget
lib/_engine/engine/pointer_binding.dart 1088:30                                 [_convertEventsToPointerData]
lib/_engine/engine/pointer_binding.dart 1016:9                                  <fn>
lib/_engine/engine/pointer_binding.dart 948:7                                   <fn>
lib/_engine/engine/pointer_binding.dart 541:9                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 212:27  _callDartFunctionFast1
DartError: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 288:3     throw_
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               assertFailed
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               _computeOffsetForInputs
lib/_engine/engine/pointer_binding/event_position_helper.dart 38:14             computeEventOffsetToTarget
lib/_engine/engine/pointer_binding.dart 1088:30                                 [_convertEventsToPointerData]
lib/_engine/engine/pointer_binding.dart 1016:9                                  <fn>
lib/_engine/engine/pointer_binding.dart 948:7                                   <fn>
lib/_engine/engine/pointer_binding.dart 541:9                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 212:27  _callDartFunctionFast1
DartError: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 288:3     throw_
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               assertFailed
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               _computeOffsetForInputs
lib/_engine/engine/pointer_binding/event_position_helper.dart 38:14             computeEventOffsetToTarget
lib/_engine/engine/pointer_binding.dart 1088:30                                 [_convertEventsToPointerData]
lib/_engine/engine/pointer_binding.dart 1016:9                                  <fn>
lib/_engine/engine/pointer_binding.dart 948:7                                   <fn>
lib/_engine/engine/pointer_binding.dart 541:9                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 212:27  _callDartFunctionFast1
DartError: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 288:3     throw_
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               assertFailed
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               _computeOffsetForInputs
lib/_engine/engine/pointer_binding/event_position_helper.dart 38:14             computeEventOffsetToTarget
lib/_engine/engine/pointer_binding.dart 1088:30                                 [_convertEventsToPointerData]
lib/_engine/engine/pointer_binding.dart 1016:9                                  <fn>
lib/_engine/engine/pointer_binding.dart 948:7                                   <fn>
lib/_engine/engine/pointer_binding.dart 541:9                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 212:27  _callDartFunctionFast1
DartError: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 288:3     throw_
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               assertFailed
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               _computeOffsetForInputs
lib/_engine/engine/pointer_binding/event_position_helper.dart 38:14             computeEventOffsetToTarget
lib/_engine/engine/pointer_binding.dart 1088:30                                 [_convertEventsToPointerData]
lib/_engine/engine/pointer_binding.dart 1016:9                                  <fn>
lib/_engine/engine/pointer_binding.dart 948:7                                   <fn>
lib/_engine/engine/pointer_binding.dart 541:9                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 212:27  _callDartFunctionFast1
DartError: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 288:3     throw_
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               assertFailed
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               _computeOffsetForInputs
lib/_engine/engine/pointer_binding/event_position_helper.dart 38:14             computeEventOffsetToTarget
lib/_engine/engine/pointer_binding.dart 1088:30                                 [_convertEventsToPointerData]
lib/_engine/engine/pointer_binding.dart 1016:9                                  <fn>
lib/_engine/engine/pointer_binding.dart 948:7                                   <fn>
lib/_engine/engine/pointer_binding.dart 541:9                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 212:27  _callDartFunctionFast1
DartError: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 288:3     throw_
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               assertFailed
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               _computeOffsetForInputs
lib/_engine/engine/pointer_binding/event_position_helper.dart 38:14             computeEventOffsetToTarget
lib/_engine/engine/pointer_binding.dart 1088:30                                 [_convertEventsToPointerData]
lib/_engine/engine/pointer_binding.dart 1016:9                                  <fn>
lib/_engine/engine/pointer_binding.dart 948:7                                   <fn>
lib/_engine/engine/pointer_binding.dart 541:9                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 212:27  _callDartFunctionFast1
DartError: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 288:3     throw_
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               assertFailed
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               _computeOffsetForInputs
lib/_engine/engine/pointer_binding/event_position_helper.dart 38:14             computeEventOffsetToTarget
lib/_engine/engine/pointer_binding.dart 1088:30                                 [_convertEventsToPointerData]
lib/_engine/engine/pointer_binding.dart 1016:9                                  <fn>
lib/_engine/engine/pointer_binding.dart 948:7                                   <fn>
lib/_engine/engine/pointer_binding.dart 541:9                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 212:27  _callDartFunctionFast1
DartError: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 288:3     throw_
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               assertFailed
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               _computeOffsetForInputs
lib/_engine/engine/pointer_binding/event_position_helper.dart 38:14             computeEventOffsetToTarget
lib/_engine/engine/pointer_binding.dart 1088:30                                 [_convertEventsToPointerData]
lib/_engine/engine/pointer_binding.dart 1016:9                                  <fn>
lib/_engine/engine/pointer_binding.dart 948:7                                   <fn>
lib/_engine/engine/pointer_binding.dart 541:9                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 212:27  _callDartFunctionFast1
DartError: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 288:3     throw_
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               assertFailed
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               _computeOffsetForInputs
lib/_engine/engine/pointer_binding/event_position_helper.dart 38:14             computeEventOffsetToTarget
lib/_engine/engine/pointer_binding.dart 1088:30                                 [_convertEventsToPointerData]
lib/_engine/engine/pointer_binding.dart 1016:9                                  <fn>
lib/_engine/engine/pointer_binding.dart 948:7                                   <fn>
lib/_engine/engine/pointer_binding.dart 541:9                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 212:27  _callDartFunctionFast1
DartError: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 288:3     throw_
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               assertFailed
dart-sdk/lib/_internal/js_dev_runtime/private/profile.dart 110:39               _computeOffsetForInputs
lib/_engine/engine/pointer_binding/event_position_helper.dart 38:14             computeEventOffsetToTarget
lib/_engine/engine/pointer_binding.dart 1088:30                                 [_convertEventsToPointerData]
lib/_engine/engine/pointer_binding.dart 1016:9                                  <fn>
lib/_engine/engine/pointer_binding.dart 948:7                                   <fn>
lib/_engine/engine/pointer_binding.dart 541:9                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/patch/js_allow_interop_patch.dart 212:27  _callDartFunctionFast1

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.27.0, on macOS 15.1.1 24B91 darwin-x64, locale en-US)
    • Flutter version 3.27.0 on channel stable at /Users/***/Development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 8495dee1fd (8 days ago), 2024-12-10 14:23:39 -0800
    • Engine revision 83bacfc525
    • Dart version 3.6.0
    • DevTools version 2.40.2

[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
    • Android SDK at /Users/***/Library/Android/sdk
    • Platform android-35, build-tools 35.0.0
    • Java binary at: /Users/***/Library/Java/JavaVirtualMachines/temurin-17.0.13/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment Temurin-17.0.13+11 (build 17.0.13+11)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 16.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 16C5032a
    • CocoaPods version 1.16.2

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

[✓] Android Studio (version 2024.1)
    • 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.11+0-17.0.11b1207.24-11852314)

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

[✓] Connected device (3 available)
    • TECNO BG6 (mobile) • 10994373B1000897 • android-arm64  • Android 13 (API 33)
    • macOS (desktop)    • macos            • darwin-x64     • macOS 15.1.1 24B91 darwin-x64
    • Chrome (web)       • chrome           • web-javascript • Google Chrome 131.0.6778.140
    ! Error: Browsing on the local area network for 3.14. Ensure the device is unlocked and attached with a cable or associated with the same
      local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

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

• No issues found!

Reproduced on 3.27.1 also

Hi @YawarOsmanKhdir, I tried to reproduce the issue, But couldn't reproduce it. Let me know if I am missing something
https://github.com/user-attachments/assets/94cb951b-f653-4d16-821f-771a945882cd

code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key, required this.title}) : super(key: key);
  final String title;
  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;
  void _incrementCounter() {
    setState(() {
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: OverviewTopBar(),
      body: const Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ),
    );
  }
}

class OverviewTopBar extends StatelessWidget implements PreferredSizeWidget {
  const OverviewTopBar({super.key});

  @override
  Size get preferredSize => Size.fromHeight(kToolbarHeight);

  @override
  Widget build(BuildContext context) {
    final width = MediaQuery.sizeOf(context).width;
    return AppBar(
      leading: _searchTextField(context),
      leadingWidth: width * 0.3,
    );
  }

  _searchTextField(BuildContext context) {
    return SizedBox(
      height: 36,
      child: TextField(
        // controller: state.searchController,
        decoration: InputDecoration(
          hintText: "Enter text here",
        ),
      ),
    );
  }
}

@maheshj01 are you running in debug mode with a breakpoint on unhandled exceptions? You can also check your debug console.

@maheshj01 are you running in debug mode with a breakpoint on unhandled exceptions? You can also check your debug console.

I tried both enable/disable Uncaught exceptions but same result in debug mode. Is this an issue when debugging in vscode?

Is this an issue when debugging in vscode?

At least for me that's how I saw it.

@maheshj01 I can reproduce this bug with your sample code, with Flutter 3.27.1 building for web in debug mode, using VS Code (on Linux). (I have it set to break on uncaught exceptions.) I've included my flutter doctor -v below.
Doctor output
[✓] Flutter (Channel stable, 3.27.1, on Ubuntu 24.04.1 LTS 6.8.0-51-generic, locale en_US.UTF-8)
    • Flutter version 3.27.1 on channel stable at /home/abc/code/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 17025dd882 (4 days ago), 2024-12-17 03:23:09 +0900
    • Engine revision cb4b5fff73
    • Dart version 3.6.0
    • DevTools version 2.40.2

[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /home/abc/Android/Sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /snap/android-studio/161/jbr/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)
    ! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • Ubuntu clang version 18.1.3 (1ubuntu1)
    • cmake version 3.28.3
    • ninja version 1.11.1
    • pkg-config version 1.8.1

[✓] Android Studio (version 2024.1)
    • Android Studio at /snap/android-studio/161
    • Flutter plugin version 81.0.2
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.10+0-17.0.10b1087.21-11609105)

[✓] VS Code (version 1.96.1)
    • VS Code at /snap/code/current/usr/share/code
    • Flutter extension version 3.102.0

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Ubuntu 24.04.1 LTS 6.8.0-51-generic
    • Chrome (web)    • chrome • web-javascript • Google Chrome 131.0.6778.139

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

! Doctor found issues in 1 category.

To be clear, the error is:
DartError: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"

Thanks for the details @olof-dev, This is a duplicate of https://github.com/flutter/flutter/issues/156842
Please follow up on that issue for further updates.
Closing as duplicate.


Emit an error when the eval action is placed in a chain

See #5648
Related: #1859

We should do the same for other getXXX methods that are currently chainable. We also have some getters that are not chainable, but they are even worse since they do not take into account all previous commands residing before them in the test controller chain.

We decided to close the issue because we have a note in the documentation that the eval call should not be chained. Please refer to the following help topic for details:
https://testcafe.io/documentation/402703/reference/test-api/testcontroller/eval


docs: Update authors

Latest blog broke the docs builds because author wasn't in authors file.

@maryamtahhan Make sure you are happy with your description.

@maryamtahhan Make sure you are happy with your description.

Thanks Billy LGTM


[Enhancement] Please, return a possibility to open test attachments in new browser's tab

Previously  I was able to open test attachments (video, screenshots, logs) in a separated tab of browser.
As a user I think that was pretty convenient

all operations should be executed inside the single zafira page. if you would like to open something in new tab use appropriate browser capabilities...


security: hide impl classes

https://critique.corp.google.com/#review/162136534

Closing, since this is a long long time ago.


Add a new type of rewards for drep refunds and populate the reward_rest table

Needs to investigate how to extract this freom the ledger

Actually they cannot go in reward_rest table, since this is related to stake address balance, while drep (de)registraiton is assigned to a drep key. The existing table drep_registration already gives a view of the refunds/deposits payed.


Define which console.log the user should remove

Challenge Local Scope and Functions has an issue.
User Agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/57.0.2987.98 Chrome/57.0.2987.98 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

function myLocalScope() {
  'use strict';
  var myVar;
  console.log(myVar);
}
myLocalScope();

// Run and check the console
// myVar is not defined outside of myLocalScope

// Now remove the console log line to pass the test

When the challenge is asked it suggests the user remove the console.log to pass the test.
It would be more descriptive to new coders to suggest which console.log to remove and why.
For instance, saying "Now remove the console log line which references the global scope to pass the test" would hammer home that this is a global parameter for new folks.

Instead of deleting the second console.log(myVar); comment it out with //


Basic Validation tests for Labels, Affinity Rules, Host Tags

Basic validation tests for:

Container and Host labels
Affinity/Anti-affinity rules
Global Service
Sidekick Service
External IP for LB Service

I added the validation test cases a bit ago.  So closing this task.


Logger?

I thought I could change the logger level in src/main/resources/logback.xml to Info to try to debug stuff, but things aren't working?

SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

Warnings(?) when compiling...
It's making it really painful to debug Firrtl bugs... am I missing something super obvious?

Edit: Ok I see that they're now command line arguments...


Cloud Host build - Failed to build module

Hi. I was following the "Cloud Host" in order to get the linux-libc-dev so that I then could make the sev-guest utility and got some issues. I was running in Azure with Ubuntu 20.04.
...
Building ... /home/azureuser/AMDSEV/ovmf/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsicSev.inf [X64]
Building ... /home/azureuser/AMDSEV/ovmf/MdePkg/Library/BaseMemoryLibRepStr/BaseMemoryLibRepStr.inf [X64]

build.py...
 : error 7000: Failed to execute command
        make tbuild [/home/azureuser/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsicSev]

build.py...
 : error 7000: Failed to execute command
        make tbuild [/home/azureuser/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseMemoryLibRepStr/BaseMemoryLibRepStr]

build.py...
 : error 7000: Failed to execute command
        make tbuild [/home/azureuser/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib]

build.py...
 : error F002: Failed to build module
        /home/azureuser/AMDSEV/ovmf/MdePkg/Library/BaseIoLibIntrinsic/BaseIoLibIntrinsicSev.inf [X64, GCC5, DEBUG]

- Failed -
Build end time: 09:41:53, Feb.17 2022
Build total time: 00:00:09

ERROR: nice build -q --cmd-len=64436 -DDEBUG_ON_SERIAL_PORT=TRUE -n 2 -t GCC5 -a X64 -p OvmfPkg/OvmfPkgX64.dsc

Any hints on how to proceed or get some more information on the error? Maybe some missing dependency?
Thank you in advance.
Andrey

Hi Andrey,
In common.sh, look for the function build_install_ovmf() and add --verbose to the BUILD_CMD="..." line. That will let you see the build errors.
The most common dependencies needed to build OVMF are:

python-is-python3
nasm
acpica-tools

Similarly, you will need to install these packages to build the Linux kernel:

libelf-dev
flex
bison

I'll update the documentation with this information. Thanks for the report!
Sincerely,
Jesse

Thank you, Jesse. I was able to compile with the deps, although running is not yet possible due to the lack of the /dev/sev (and replacing the kernel was also not possible in the current vms).

@jlarrew  I installed the packeges you mentioned, but I still got the same error, do you have any idea?
Building ... /home/yaoxin/AMDSEV/ovmf/NetworkPkg/Library/DxeHttpLib/DxeHttpLib.inf [X64]
"nasm" -I/home/yaoxin/AMDSEV/ovmf/MdePkg/Library/BaseLib/X64/ -I/home/yaoxin/AMDSEV/ovmf/MdePkg/Library/BaseLib/X64/ -I/home/yaoxin/AMDSEV/ovmf/MdePkg/Library/BaseLib/ -I/home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/DEBUG/ -I/home/yaoxin/AMDSEV/ovmf/MdePkg/ -I/home/yaoxin/AMDSEV/ovmf/MdePkg/Include/ -I/home/yaoxin/AMDSEV/ovmf/MdePkg/Test/UnitTest/Include/ -I/home/yaoxin/AMDSEV/ovmf/MdePkg/Include/X64/ -f elf64 -o /home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.obj /home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.iii
/home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.iii:44: error: parser: instruction expected
/home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.iii:49: error: parser: instruction expected
make: *** [GNUmakefile:790: /home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.obj] Error 1

build.py...
 : error 7000: Failed to execute command
        make tbuild [/home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib]

build.py...
 : error F002: Failed to build module
        /home/yaoxin/AMDSEV/ovmf/MdePkg/Library/BaseLib/BaseLib.inf [X64, GCC5, DEBUG]

- Failed -
Build end time: 10:42:38, Feb.18 2023
Build total time: 00:00:06

ERROR: nice build -q --cmd-len=64436 -DDEBUG_ON_SERIAL_PORT=TRUE -n 48 -t GCC5 -a X64 -p OvmfPkg/OvmfPkgX64.dsc --verbose
yaoxin@amd-sev-snp2:~/AMDSEV$

Hi Yaoxin,
It looks like you need a more recent version of nasm than what your distro
provides. Try building it from source:
https://github.com/netwide-assembler/nasm
See the INSTALL file for build instructions.
Sincerely,
Jesse
On Sat, Feb 18, 2023, 3:42 AM yaoxin1995 @.***> wrote:

@jlarrew https://github.com/jlarrew I installed the packeges you
mentioned, but I still got the same error, do you have any idea?
Building ... /home/yaoxin/AMDSEV/ovmf/NetworkPkg/Library/DxeHttpLib/DxeHttpLib.inf [X64]
"nasm" -I/home/yaoxin/AMDSEV/ovmf/MdePkg/Library/BaseLib/X64/ -I/home/yaoxin/AMDSEV/ovmf/MdePkg/Library/BaseLib/X64/ -I/home/yaoxin/AMDSEV/ovmf/MdePkg/Library/BaseLib/ -I/home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/DEBUG/ -I/home/yaoxin/AMDSEV/ovmf/MdePkg/ -I/home/yaoxin/AMDSEV/ovmf/MdePkg/Include/ -I/home/yaoxin/AMDSEV/ovmf/MdePkg/Test/UnitTest/Include/ -I/home/yaoxin/AMDSEV/ovmf/MdePkg/Include/X64/ -f elf64 -o /home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.obj /home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.iii
/home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.iii:44: error: parser: instruction expected
/home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.iii:49: error: parser: instruction expected
make: *** [GNUmakefile:790: /home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/LongJump.obj] Error 1
build.py...
: error 7000: Failed to execute command
make tbuild [/home/yaoxin/AMDSEV/ovmf/Build/OvmfX64/DEBUG_GCC5/X64/MdePkg/Library/BaseLib/BaseLib]
build.py...
: error F002: Failed to build module
/home/yaoxin/AMDSEV/ovmf/MdePkg/Library/BaseLib/BaseLib.inf [X64, GCC5, DEBUG]

Failed -
Build end time: 10:42:38, Feb.18 2023
Build total time: 00:00:06

ERROR: nice build -q --cmd-len=64436 -DDEBUG_ON_SERIAL_PORT=TRUE -n 48 -t GCC5 -a X64 -p OvmfPkg/OvmfPkgX64.dsc --verbose
@.***:~/AMDSEV$
—
Reply to this email directly, view it on GitHub
https://github.com/AMDESE/sev-guest/issues/5#issuecomment-1435533393,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA36KBPUOCW2P3WBGOOK5NDWYCKQ5ANCNFSM5OUGCVFQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks, I switched to NASM version 2.16.01 and the compilation succeeded
dpkg-deb: building package 'linux-libc-dev' in '../linux-libc-dev_5.19.0-rc6-snp-host-d9bd54fea4d2-1_amd64.deb'.
dpkg-deb: building package 'linux-image-5.19.0-rc6-snp-host-d9bd54fea4d2' in '../linux-image-5.19.0-rc6-snp-host-d9bd54fea4d2_5.19.0-rc6-snp-host-d9bd54fea4d2-1_amd64.deb'.
dpkg-deb: building package 'linux-image-5.19.0-rc6-snp-host-d9bd54fea4d2-dbg' in '../linux-image-5.19.0-rc6-snp-host-d9bd54fea4d2-dbg_5.19.0-rc6-snp-host-d9bd54fea4d2-1_amd64.deb'.
 dpkg-genbuildinfo --build=binary
 dpkg-genchanges --build=binary >../linux-upstream_5.19.0-rc6-snp-host-d9bd54fea4d2-1_amd64.changes
dpkg-genchanges: info: binary-only upload (no source code included)
 dpkg-source --after-build .
dpkg-buildpackage: info: binary-only upload (no source included)
make: Leaving directory '/home/yaoxin/AMDSEV/linux/host'
+ popd
/home/yaoxin/AMDSEV
+ [[ '' = \1 ]]

But I didn't find any deb packages under linux/host/. Do you have any idea?
However, I do find a lot of deb packages under linux dir:
yaoxin@amd-sev-snp2:~/AMDSEV$ ls linux/
guest
host
linux-headers-5.19.0-rc6-snp-guest-d9bd54fea4d2_5.19.0-rc6-snp-guest-d9bd54fea4d2-1_amd64.deb
linux-headers-5.19.0-rc6-snp-host-d9bd54fea4d2_5.19.0-rc6-snp-host-d9bd54fea4d2-1_amd64.deb
linux-image-5.19.0-rc6-snp-guest-d9bd54fea4d2_5.19.0-rc6-snp-guest-d9bd54fea4d2-1_amd64.deb
linux-image-5.19.0-rc6-snp-guest-d9bd54fea4d2-dbg_5.19.0-rc6-snp-guest-d9bd54fea4d2-1_amd64.deb
linux-image-5.19.0-rc6-snp-host-d9bd54fea4d2_5.19.0-rc6-snp-host-d9bd54fea4d2-1_amd64.deb
linux-image-5.19.0-rc6-snp-host-d9bd54fea4d2-dbg_5.19.0-rc6-snp-host-d9bd54fea4d2-1_amd64.deb
linux-libc-dev_5.19.0-rc6-snp-guest-d9bd54fea4d2-1_amd64.deb
linux-libc-dev_5.19.0-rc6-snp-host-d9bd54fea4d2-1_amd64.deb
linux-upstream_5.19.0-rc6-snp-guest-d9bd54fea4d2-1_amd64.buildinfo
linux-upstream_5.19.0-rc6-snp-guest-d9bd54fea4d2-1_amd64.changes
linux-upstream_5.19.0-rc6-snp-host-d9bd54fea4d2-1_amd64.buildinfo
linux-upstream_5.19.0-rc6-snp-host-d9bd54fea4d2-1_amd64.changes
yaoxin@amd-sev-snp2:~/AMDSEV$

Do you know which package should I install for the cloud host?


Could not get container for elasticsearch

This image is officially deprecated in favor of the kibana image provided by elastic.co which is available to pull via docker.elastic.co/kibana/kibana:[version] like 5.2.1. This image will receive no further updates after 2017-06-20 (June 20, 2017). Please adjust your usage accordingly.
Elastic provides open-source support for Kibana via the elastic/kibana GitHub repository and the Docker image via the elastic/kibana-docker GitHub repository, as well as community support via its forums.

This is an issue with only a title and the default content. Closing.


ovn version 3 ovnkube.sh and daemonsets

Separate containers for northd and the nb and sb databases
Change display target to list pid and log for the container
General cleanups and restructuring:

daemon output to stdout so oc logs can display it.
Restart when a daemon fails.
Add scripts to get logs and ovn debug info from all nodes.
document changes: READMEopenshifttechpreview.md

SDN-119 The OVN daemonset should be reliable and easy to debug
SDN-110 Split daemonset in to multiple containers
SDN-114 Separate master and node components in to two daemonsets
SDN-221 Write daemonset templates for OVN
SDN-195 Split daemonset in to even more containers.
SDN-193 OVN: improve logging and error handling
https://jira.coreos.com/browse/SDN-193
Signed-off-by: Phil Cameron<EMAIL_ADDRESS>

@dcbw @squeed @shettyg PTAL

Added documentation: READMEopenshifttechpreview.md
@squeed @dcbw @glennswest @shettyg PTAL

@pecameron
Can you explain the though process of splitting OVN daemons into separate containers?

Phil is OOO for the next week, but I'd originally asked him to do it, so I'll take a stab at answering.
In the kubernetes world, there is a general convention that Kubernetes should be the process manager. That is to say, each kubernetes container should map to a single daemon process, and that process should log to stdout. When that process exits, Kubernetes should be the one to restart it, etc. etc.
One of the primary motivations for one-process-per-container is improved debuggability. Previously, if (for example) ovn-nbdb crashed, this fact wasn't immediately clear. Instead, you might have to kubectl exec in to the container, then manually tail some logs. Now, you can see at-a-glance via kubectl get pods that one of the individual containers in a pod is having problems, and easily see the issue with kubectl logs.
Make sense?

Make sense?

Thanks for the explanation.

@dcbw, daemonsets and images are built in different streams and version skew can happen. The 1/2/3 permits older daemonsets to run with newer images. The newer daemonsets that reference entry points in newer images will fail when starting an older image.
A PR that includes daemonset changes and image changes, may not be testable until the image is built and pushed. (This can be a problem for ci testing)

@dcbw PTAL

@pecameron Since this needs a dameonset image update for community daemonset, once it gets merged, please make sure to upload the latest image.

@shettyg After the merge, I will build and push the image.

@squeed @dcbw @shettyg What do we need to do to move this PR forward? Are there further changes that need to be made?
PTAL

Since @dcbw did the initial review, I am waiting for him to do the final merge.

@shettyg @squeed @dcbw
updated: docker.io/ovnkube/ovn-daemonset:latest

@pecameron
Thanks.

If I remember right, previously running OVS daemons inside pods was optional and we needed a different yaml for that?

If a host already has OVS daemons running, what would be the behavior of the pods? Will it just not run OVS daemons and everything will work fine? Or something is not going to work?

@pecameron

I am trying to run the latest daemonsets. I observed that, if you "kubectl delete -f" on the ovnkube-master.yaml and ovnkube.yaml and re-create it, it looks to error out. Deleting contents of /var/run/openvswitch and then redoing seems to help.

I think the CPU may be too low for a large cluster. And requests for memory may be too high for a small cluster.

@shettyg

before this PR, ovs ran in its own daemonset on each node. In this PR the ovs daemonset is gone and ovs is integrated in the node daemonset. The node daemonset runs on each node. The master node has both the master daemonset and the node daemonset.

Before running this new setup delete the ovs, ovnkube and ovnkube-master daemonsets and make sure ovs/ovn/ovnkube is not running anywhere.. This may not fully cleanup (I didn't test this since 4.0 is for new clusters). The host must not be running ovs or any ovn/ovnkube daemons before starting the new daemonsets. The ovnkube daemonset will start ovs.

@pecameron
I think there is a valid use case for not running OVS inside daemonset and only run OVN inside it.  What can we do to make it configurable?

@shettyg

I am interested in the problem you are seeing. This should cleanly start and stop. This has been working for me and I would like to make sure it works properly for everyone. Any details you may have are appreciated.

Is the CPU and memory behavior different than before? We need to get the team involved with this. Lets bring it up at the next meeting.

@shettyg @dcbw @squeed Lets get a discussion going on:
"running OVS outside daemonset and only run OVN inside it". I can make the changes that come out of the discussion.

I have met some problem after update this commit.
NAME                   READY     STATUS             RESTARTS   AGE
ovnkube-72pdm          1/3       CrashLoopBackOff   28         37m
ovnkube-hl2qm          1/3       CrashLoopBackOff   32         37m
ovnkube-master-msf9k   0/4       CrashLoopBackOff   68         37m
kubectl logs ovnkube-72pdm ovs-daemons
================== ovnkube.sh --- version: 3 ================
==================== command: ovs-server
=================== hostname: host-10-0-11-24
=================== daemonset version 3
=================== Image built from ovn-kubernetes ref: refs/heads/new  commit: 80568eeab1fc2965cc70d6d6c6e012202d665434
OVS_USER_ID root:root
OVS_OPTIONS
OVN_NORTH
OVN_NORTHD_OPTS --db-nb-sock=/var/run/openvswitch/ovnnb_db.sock --db-sb-sock=/var/run/openvswitch/ovnsb_db.sock
OVN_SOUTH
OVN_CONTROLLER_OPTS --ovn-controller-log=-vconsole:emer
OVN_NET_CIDR
OVN_SVC_CIDR
K8S_APISERVER
OVNKUBE_LOGLEVEL 4
OVN_DAEMONSET_VERSION 3
ovnkube.sh version 3
Starting ovsdb-server.
Configuring Open vSwitch system IDs.
Inserting openvswitch module.
Starting ovs-vswitchd.
Enabling remote OVSDB managers.
Enabling udp to port 6081 with iptables.
==> /var/log/openvswitch/ovs-vswitchd.log <==
2018-12-03T08:16:09.096Z|00033|bridge|INFO|bridge br-localnet: using datapath ID<PHONE_NUMBER>49c74a
2018-12-03T08:16:09.096Z|00034|connmgr|INFO|br-localnet: added service controller "punix:/var/run/openvswitch/br-localnet.mgmt"
2018-12-03T08:16:09.098Z|00035|bridge|INFO|bridge br-int: using datapath ID 00004af38b9cc743
2018-12-03T08:16:09.098Z|00036|connmgr|INFO|br-int: added service controller "punix:/var/run/openvswitch/br-int.mgmt"
2018-12-03T08:16:09.106Z|00037|bridge|WARN|could not open network device c986961d92ab229 (No such device)
2018-12-03T08:16:09.107Z|00038|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.9.2
2018-12-03T08:16:09.113Z|00039|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on genev_sys_6081 device failed: No such device
2018-12-03T08:16:09.171Z|00040|bridge|WARN|could not open network device c986961d92ab229 (No such device)
2018-12-03T08:16:09.174Z|00041|bridge|WARN|could not open network device c986961d92ab229 (No such device)
2018-12-03T08:16:09.175Z|00042|netdev_linux|INFO|ioctl(SIOCGIFINDEX) on genev_sys_6081 device failed: No such device
==> /var/log/openvswitch/ovsdb-server.log <==
2018-12-03T08:16:07.973Z|00001|vlog|INFO|opened log file /var/log/openvswitch/ovsdb-server.log
2018-12-03T08:16:07.982Z|00002|ovsdb_server|INFO|ovsdb-server (Open vSwitch) 2.9.2
kubectl logs ovnkube-72pdm ovn-controller
================== ovnkube.sh --- version: 3 ================
==================== command: ovn-controller
=================== hostname: host-10-0-11-24
=================== daemonset version 3
=================== Image built from ovn-kubernetes ref: refs/heads/new  commit: 80568eeab1fc2965cc70d6d6c6e012202d665434
OVS_USER_ID root:root
OVS_OPTIONS
OVN_NORTH tcp://<IP_ADDRESS>:6641
OVN_NORTHD_OPTS --db-nb-sock=/var/run/openvswitch/ovnnb_db.sock --db-sb-sock=/var/run/openvswitch/ovnsb_db.sock
OVN_SOUTH tcp://<IP_ADDRESS>:6642
OVN_CONTROLLER_OPTS --ovn-controller-log=-vconsole:emer
OVN_NET_CIDR <IP_ADDRESS>/16
OVN_SVC_CIDR <IP_ADDRESS>/16
K8S_APISERVER http://<IP_ADDRESS>:8080
OVNKUBE_LOGLEVEL 4
OVN_DAEMONSET_VERSION 3
ovnkube.sh version 3
=============== ovn-controller - (wait for ovs)
=============== ovn-controller - (wait for northdb)
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
ovn-northd came up in 14 10sec tries
=============== ovn-controller
Starting ovn-controller.
=============== ovn-controller ========== running
2018-12-03T08:28:09.320Z|00115|reconnect|INFO|tcp:<IP_ADDRESS>:6642: connection closed by peer
2018-12-03T08:28:10.321Z|00116|reconnect|INFO|tcp:<IP_ADDRESS>:6642: connecting...
2018-12-03T08:28:10.332Z|00117|reconnect|INFO|tcp:<IP_ADDRESS>:6642: connection attempt failed (Connection refused)
2018-12-03T08:28:10.332Z|00118|reconnect|INFO|tcp:<IP_ADDRESS>:6642: waiting 2 seconds before reconnect
2018-12-03T08:28:12.334Z|00119|reconnect|INFO|tcp:<IP_ADDRESS>:6642: connecting...
2018-12-03T08:28:12.345Z|00120|reconnect|INFO|tcp:<IP_ADDRESS>:6642: connection attempt failed (Connection refused)
2018-12-03T08:28:12.345Z|00121|reconnect|INFO|tcp:<IP_ADDRESS>:6642: waiting 4 seconds before reconnect
2018-12-03T08:28:16.348Z|00122|reconnect|INFO|tcp:<IP_ADDRESS>:6642: connecting...
2018-12-03T08:28:16.360Z|00123|reconnect|INFO|tcp:<IP_ADDRESS>:6642: connection attempt failed (Connection refused)
2018-12-03T08:28:16.360Z|00124|reconnect|INFO|tcp:<IP_ADDRESS>:6642: continuing to reconnect in the background but suppressing further logging
=============== pid 6235 terminated ==========
kubectl logs ovnkube-72pdm  ovn-node
================== ovnkube.sh --- version: 3 ================
==================== command: ovn-node
=================== hostname: host-10-0-11-24
=================== daemonset version 3
=================== Image built from ovn-kubernetes ref: refs/heads/new  commit: 80568eeab1fc2965cc70d6d6c6e012202d665434
OVS_USER_ID root:root
OVS_OPTIONS
OVN_NORTH tcp://<IP_ADDRESS>:6641
OVN_NORTHD_OPTS --db-nb-sock=/var/run/openvswitch/ovnnb_db.sock --db-sb-sock=/var/run/openvswitch/ovnsb_db.sock
OVN_SOUTH tcp://<IP_ADDRESS>:6642
OVN_CONTROLLER_OPTS --ovn-controller-log=-vconsole:emer
OVN_NET_CIDR <IP_ADDRESS>/16
OVN_SVC_CIDR <IP_ADDRESS>/16
K8S_APISERVER http://<IP_ADDRESS>:8080
OVNKUBE_LOGLEVEL 5
OVN_DAEMONSET_VERSION 3
ovnkube.sh version 3
=============== ovn-node - (wait for ovs)
=============== ovn-node - (wait for northdb)
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
info: Waiting for ovn-northd to come up, waiting 10s ...
kubectl logs ovnkube-master-msf9k run-ovn-northd
================== ovnkube.sh --- version: 3 ================
==================== command: run-ovn-northd
=================== hostname: host-10-0-11-12
=================== daemonset version 3
=================== Image built from ovn-kubernetes ref: refs/heads/new  commit: 80568eeab1fc2965cc70d6d6c6e012202d665434
OVS_USER_ID root:root
OVS_OPTIONS
OVN_NORTH tcp://<IP_ADDRESS>:6641
OVN_NORTHD_OPTS --db-nb-sock=/var/run/openvswitch/ovnnb_db.sock --db-sb-sock=/var/run/openvswitch/ovnsb_db.sock
OVN_SOUTH tcp://<IP_ADDRESS>:6642
OVN_CONTROLLER_OPTS --ovn-controller-log=-vconsole:emer
OVN_NET_CIDR <IP_ADDRESS>/16
OVN_SVC_CIDR <IP_ADDRESS>/16
K8S_APISERVER http://<IP_ADDRESS>:8080
OVNKUBE_LOGLEVEL 4
OVN_DAEMONSET_VERSION 3
ovnkube.sh version 3
=============== run_ovn_northd ========== MASTER ONLY
OVN_NORTH=tcp://<IP_ADDRESS>:6641 OVN_SOUTH==tcp://<IP_ADDRESS>:6642 ovn_northd_opts=--db-nb-sock=/var/run/openvswitch/ovnnb_db.sock --db-sb-sock=/var/run/openvswitch/ovnsb_db.sock
Starting ovn-northd.
=============== run_ovn_northd ========== RUNNING
2018-12-03T08:26:50.030Z|00001|vlog|INFO|opened log file /var/log/openvswitch/ovn-northd.log
2018-12-03T08:26:50.032Z|00002|reconnect|INFO|unix:/var/run/openvswitch/ovnnb_db.sock: connecting...
2018-12-03T08:26:50.032Z|00003|reconnect|INFO|unix:/var/run/openvswitch/ovnnb_db.sock: connection attempt failed (Connection refused)
2018-12-03T08:26:50.032Z|00004|reconnect|INFO|unix:/var/run/openvswitch/ovnsb_db.sock: connecting...
2018-12-03T08:26:50.032Z|00005|reconnect|INFO|unix:/var/run/openvswitch/ovnsb_db.sock: connection attempt failed (Connection refused)
=============== pid 8403 terminated ==========

I am now seeing the problem as well. Something happened from when I worked on this to when it got merged. I am working on a fix.


Programming Model v4 deployments

Has anyone had any luck getting their @nxazure/func projects to deploy? We've tried GitHub actions and the VSCode Azure Extension, but even when it appears to have been deployed successfully, there are no functions recognised by the function app. But it all runs just fine locally using the :start target. We're using the new Programming Model v4 with Typescript code.

Hi Jon,
I'd be happy to help you figure this out.
In my project, I'm publishing the functions via GitHub actions.
One of the things that the package provides is the ability to also publish it to the cloud.
Simply use the executor publish to do so. :)
Here is the nx console command:
npx nx publish my-nx-app-name -n my-deployed-func-app-name
For GitHub Actions, you should make sure you install dependencies and also login to Azure before you publish it.
Here is a job example:
publish-function:
    name: ⚡ Publish function
    runs-on: ubuntu-latest
    steps:
      # Azure Login
      - name: ☁🪧 Azure Login
        uses: azure/login@v1
        with:
          creds: ${{ secrets.AZURE_CREDENTIALS }}

      # Publish App
      - name: ✅ Checkout
        uses: actions/checkout@v3
      - name: 👷♂🛠 Install Dependencies
        run: npm install # Or whatever type of dependencies installation (or cache download) you have
      - name: ⚡ Publish Function
        run: npx nx publish my-nx-app-name -n my-deployed-func-app-name

Let me know if it works or not

Thinking about it, I'll even add this to the docs later :)

Thanks @AlexPshul - I shall try this today. We've been using GitHub Actions based upon a modified version of the default one, incorporating the Azure/functions-action@v1 deployment step, having done all the nx building on the deployment server. I saw the publish target in the project.json file and tried it locally with no success, but never thought of running it during the deployment script. It makes sense now! 😂

Having significant problems getting `azure/login@v1` to work, despite having a set of credentials generated by the Azure Portal and successfully inserted into the repo's secrets. But I'll struggle on...

Right... so... I did the following:

created a managed identity using az ad sp create-for-rbac --name "myApp" --role contributor --scopes /subscriptions/<subscription-id>/resourceGroups/<group-name>/providers/Microsoft.Web/sites/<app-name> --json-auth
put the creds JSON into a repo secret on GitHub
referenced the creds secret in a script almost identical to yours

Alas, the deployment is failing during the publish phase:
Run npx nx publish pm4test -n pm4trial --typescript
  npx nx publish pm4test -n pm4trial --typescript
  shell: /usr/bin/bash -e ***0***
  env:
    NPM_TOKEN: ***

> nx run pm4test:publish -n pm4trial --typescript
Compiling TypeScript files for project "pm4test"...
Done compiling TypeScript files for project "pm4test".
added 9 packages, and audited 10 packages in [2](https://github.com/company/repo/actions/runs/7856371064/job/21439060662#step:6:2)s
1 package is looking for funding
  run `npm fund` for details
found 0 vulnerabilities
Can't determine project language from files. Please use one of [--csharp, --javascript, --typescript, --java, --python, --powershell, --custom]
Your Azure Function App has 'FUNCTIONS_WORKER_RUNTIME' set to 'node' while your local project is set to 'None'.
You can pass --force to update your Azure app with 'None' as a 'FUNCTIONS_WORKER_RUNTIME'

Any idea how I can get past this @AlexPshul ?
Thanks! 😊

Glad you made it work till this point.
Based on the error, it looks like you don't have the FUNCTIONS_WORKER_RUNTIME app setting.
Could you add FUNCTIONS_WORKER_RUNTIME to your local.settings.json file and set it to node? It should have been done automatically via the @nxazure/func tool but maybe it was removed for some reason at some point.
Anyway, this should solve the problem.
Also, before running the GitHub Action each time, it should also work locally.
If it works locally, it should also work on your GitHub action workflow.
Running the publish command locally will just give you much shorter trial & error cycle. :)
Let me know if you solved it or not. I'm curios! 😁

Aha, we routinely .gitignore our local.settings.json in case it's been used for anything containing keys (yes, probably encouraging bad practices! 😊), so it never reaches the deployment server as it's not in the repo.
So I could insert a workflow step to locally create the file with that setting... or just check in the file and ensure anything sensitive goes in the key vault.
I'll try one of these and get back to you.
The one time I tried it, the publish target didn't work and ended in an error, but it's many hundreds of attempts ago and I can't recall what it was so I'll try that again too. 😁
Thanks again!

@AlexPshul Yay! It all works! Thank you for all your help. We now have a process that is entirely repeatable and simple to implement for as many function apps as we choose to put in our nx monorepo.
Can I thank you by contributing some documentation?

Glad it worked out!
I'm always happy for contributions to the repo! 😃
What did you end up doing? Adding the local.settings.json?
Please share the steps that helped you, it could save someone else a lot of time. :)

We ended up being good kids and using the key vault 🤣
Once I’ve documented everything for us, I’ll submit a PR with an .md file you can link from the ReadMe, containing all the detailed steps and options for setting up and operating the deployment process.
Once again, thanks for all your help @AlexPshul.


A11y – Check color-contrast on choice-card with dark background

Reported by cypress-axe (48 nodes with error):

### Tasks
- [ ] Fix issues with color contrast
- [ ] Enable 'color-contrast' rules again (by removing the option) on the e2e test

Duplicate #2675


Unable to view topology on portal

Hello I'm trying to view topology on portal, but I'm getting blank area after selection of resource group and vnet. Network Watcher is enabled in that region. I see that behavior on different subscriptions
Also I noticed, that az network watcher show-topology returns json formatted result without errors.
I see in browsers developers console that then viewing topology on portal requests are sending to api-version=2019-09-01 but from az cli to api-version=2019-02-01. Maybe this is the reason

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

ID: 6698ed8b-9c0f-8d05-228d-d55b99d5f6cc
Version Independent ID: a211b7b4-7ded-b6c3-2988-0824a2ce4d60
Content: View Azure virtual network topology
Content Source: articles/network-watcher/view-network-topology.md
Service: network-watcher
GitHub Login: @damendo
Microsoft Alias: damendo

@feksai Thank you for your query, our team will look into it and get back to you at the earliest.

@feksai I am able to see VNET topology without issue in the portal, and receive no errors when using PowerShell & CLI. If you would like to investigate this further, your best bet is to create a support request. If you do not have a support plan, please let me know.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Editor Part Options: Only Validate Changed Settings

We validate all settings every time a setting has changed in the editor part. Only changed settings require validation.
// cc @bpasero

@benibenj I would actually go one step further: only validate settings that the user has configured. All others will already be configured as default.
I think https://github.com/microsoft/vscode/issues/125422 is the real fix here to have this done within config service.

Yes, I totally agree


Update Onboarding.sol - (i) remove unnecessary require() check on allowance, (ii) update ETH transfer syntax

remove require() check on allowance as this is implicit and will produce failure in require() statement for transferFrom() if allowance insufficient.

the change looks good but you need to run linting.
just run npm run lint:fix and then push the changes
Thanks!

closing this PR, as changes are now combined into: https://github.com/openlawteam/laoland/pull/86


made doc string waiting for merge

made doc string
Originally posted by @kernb2 in https://github.com/raman-noodles/raman-spectra-decomp-analysis/pull/36

doc string signed off and completed, thanks!


Fix switching from 2d to 3d with 2d points

References and relevant issues
Fixes #6925.
Description
This was introduced by me in https://github.com/napari/napari/pull/6896/files#r1602264036, and as pointed out by @psobolewskiPhD for some reason tests weren't catching it. Turns out, as found by @andy-sweet (https://github.com/napari/napari/issues/6925#issuecomment-2163682679), we need a test with full qt events.
I'm not sure whether there's a smarter way to do this, but I confirmed that this test fails before the fix and works after.

I still don't get this, but it does fix the issue for me 🙏

Basically the bottom like is:

2d data is loaded to the GPU
switch to 3D pads the data to 3D and send it to the GPU
since a value was not passed for edge_width, vispy complains the the existing data (2d) cannot be broadcasted to the new shape (3d).
if instead we pass a scalar (0) this can be broadcasted to to 3D just fine.


API Link now working, it shows Error 404 not found.

[Enter feedback here]

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

ID: a5a19fd4-e687-60de-9492-3c6d53d603f1
Version Independent ID: f0987b6b-4811-3563-f2c0-1ad8dcaf05a3
Content: HttpHelper - Windows Community Toolkit
Content Source: docs/helpers/HttpHelper.md
Product: community-toolkit
GitHub Login: @nmetulev
Microsoft Alias: mhawker

Please update the API link.


Remove ci code that is no longer needed.

We no longer need to restore previous milestones, walk git history, or create the aggregate.
This change also includes the bump fix to ingore agent plugin tasks.
There is more code to clean up but I want to get the Artifacts working in master, let's get this in then I will do a second PR to clean up dead code.
@TingluoHuang this also adds the change to skip bumping Agent plugin tasks.
This cuts publish from 18 minutes to about 4. Will continue to get faster as we move to build only changed.

Merging to make master green, would still appreciate a review.


schema: Make optional/required declaration consistently located.

Nitfixes:

Removed "should be's" where schema has specific format.
Consistently omit indefinite articles in beginning of definitions.

Nitfixes? Nit fixes? Nitfixen? Nitfices?

This really just serves to highlight other inconsistencies in wording etc! But incremental improvements are better than nothing. Thanks for the patch.


deprecate autoLogging.ignorePaths / autoLogging.getPaths in favor of autoLogging.ignore?

autoLogging.ignore can ignore by any req prop, including but not limited to url/originalUrl, as such should we deprecate autoLogging.ignorePaths / autoLogging.getPaths  or consider these to be convenience options?

That'd be great, would you like to send a PR?

Sure, #218 opened, PTAL


proposal: bytes: make Reader.WriteTo side effect free when the Reader is empty

Motivations
I recently got bitten because some code was doing concurrent io.Copy from shared empty bytes.Reader.
This code was safe because the bytes.Reader.WriteTo function was hidden in a io.NopCloser, so io.Copy was using bytes.Reader.Read, however adding support of io.WriterTo to io.NopCloser had the side effect of no longer hidding bytes.Reader.WriteTo which trigger a race in io.Copy.
Underlying issue
The underlying issue is that bytes.Reader.Read and bytes.Reader.WriteTo have different side effects when called with an empty reader.

bytes.Reader.WriteTo invalidate the previously returned rune when the reader is empty.
bytes.Reader.Reader invalidate the previously returned rune only when the reader is not empty.

My understanding is that there is a weak contract about implementing io.WriterTo on objects also implementing io.Reader.
Is that implementation details aside (like zero copying), the side effects should be behaviorally equivalent between doing io.ReadAll(r) and r.WriteTo(io.Discard), and this weak contract is the reason io.Copy is allowed to attempt to use io.WriterTo when available.
However bytes.Reader doesn't do that.
Proposal
In bytes.Reader.WriteTo only invalidate the previously red rune if the buffer is not empty.
In code:
r := bytes.NewReader(data)
r.ReadRune() // r must now be empty
r.WriteTo(w)
r.UnreadRune() // Currently, err == errors.New("bytes.Reader.UnreadRune: previous operation was not ReadRune")
// This proposal err == nil and r.i = r.prevRune

Note that this behaviour is currently what we have with r.Read
r := bytes.NewReader(data)
r.ReadRune() // r must now be empty
r.Read(b)
r.UnreadRune() // Currently, err == nil and r.i = r.prevRune

Objective
This would harmonize side effects between bytes.Reader.Read and bytes.Reader.WriteTo when the Reader is empty and allows for concurrent bytes.Reader.WriteTo call with empty buffers.

I'm not sure I understand all the details here.
However, in general, WriteTo is defined on a reader, and calling WriteTo tells the reader to write all available data to the writer passed to WriteTo.  In general this can't be called concurrently.  In particular, bytes.Reader.WriteTo can't be called concurrently in the general case.
I suppose that it does little harm to call WriteTo concurrently if the bytes.Reader is empty.  But that is an odd special case to pick out.
It seems to me that the code that is making concurrent calls to WriteTo on a single bytes.Reader is broken, and that that code should be fixed.  If this code only happens in a test, then the test should be fixed.

But that is an odd special case to pick out.

I agree, however that what bytes.Reader.Read already do, and we have tests and code in the std relies on that, if compatilibity was not a concern I would be for the inverse patch (make bytes.Reader.Read concurrent-unsafe so -race would pick it up).
Here is what the patch would be (tests aside):
func (r *Reader) WriteTo(w io.Writer) (n int64, err error) {
-	r.prevRune = -1
	if r.i >= int64(len(r.s)) {
		return 0, nil
	}
+	r.prevRune = -1

To follow what Read do:
func (r *Reader) Read(b []byte) (n int, err error) {
	if r.i >= int64(len(r.s)) {
		return 0, io.EOF
	}
	r.prevRune = -1

don't think we can break Read's behaviour, but hopefully we can make WriteTo coherent.

My opinion is WriteTo is already coherent, and if other parts of the standard library assume that it's OK to call io.Copy concurrently on an empty bytes.Reader, then we should fix those parts of the standard library.

if other parts of the standard library assume that it's OK to call io.Copy concurrently on an empty bytes.Reader, then we should fix those parts of the standard library

I agree with that statement.
@ianlancetaylor should this proposal be closed and open the reverse one (make bytes.Reader.Read invalidate r.prevRune on call so thoses cases would show up in -race) ?
Or would that be go2 since this would be a breaking change ?

I think it would be OK to change bytes.Reader.Read but it doesn't seem very important.

Closing this then.

I think it would be OK to change bytes.Reader.Read but it doesn't seem very important.

{bytes,strings}.Reader already has a few special cases making things concurrently safe. Read is one of those.


[Question] real world example of using redux-resources with redux saga

Are the more examples how i can integrade redux-resources with redux-saga?

@meneman gotchu https://github.com/truebuildio/truebuild-frontend
this is a VERY abstracted project. combined with sagas that are bundle split, sagas + redux-resource variables/functions/etc all being generated
give it a few refreshes for form fields to populate as its all running on lambda https://www.truebuild.io

Thanks for sharing that link @djstein . I'm going to close this out for now, but if anyone else has additional links to add please do!


search text in function

Hi, I think it will be so nice if we can search a text in a specific function not whole file :)
Sometimes I encounter very large files and when trying to search a variable (which is used by many places) I need to cut the function to another file then can search for variable. Is there anyone thinking like me :)

You can click the button with the lines to enable "find in selection". Select your function then you can just search there. Hope that helps


What is scid for?

This is not an issue, just a question for implementation.
Currently I'm trying to make some simple server/client app for study, but bit blocked on defining scid.
// Client connection.
let conn = quiche::connect(Some(&server_name), &scid, to, &mut config)?;

// Server connection.
let conn = quiche::accept(&scid, None, from, &mut config)?;

How should I define scid?
Is this should be same for defining client/server?
Also, will it be okay to think server_name and from as "host address" in usual server/client app?

(hope there are some discord/gitter channel, for simple QnA...)

For SCID see https://www.rfc-editor.org/rfc/rfc9000.html#section-5.1. Each end picks one, the peer uses that value as the DCID in packets it sends. Picking a value is a deployment choice that needs to follow guidance in the RFC.
server_name is used for client-side cert validation . from is used by the server, its the client's socket object.


Update UG

Update UG to include missing information in content page and summary

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (8917865) compared to base (d9ffa25).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #61   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Time rework

We're atmospheremaxxing

[x] Ambient sound
[x] Sprite, fixture
[x] Analogue clock visualizer
[x] PDA clock stuff
[x] Wristwatch
[x] Wall clocks
[ ] Polish pass

gonna split out decimal time to a seperate pr in the future I think

the actual items all work fine now other than their ugly coder sprites, which can be redone
I'll probably go back and add construction, etc while we wait

just waiting on the wallmounted sprite to get finished


new bug when delete picture

1.select 2 files
2.click red delete button under the first file
3.select files again  then you will see first file has been changed.

Thanks for the report. I'll check and fix it later!

Hey Mike! I am waiting for you fix this bug.Thanks!

@wangkai1994  Thank you for reminding me this.


Add standalone executable for non-programming users

Maybe this can be done with each version

I don't see how this can be done. Can we make an executable out of a server?

@nkprince007 see PatokaX server for dc, basically it'l make it easier for everyone to host their own servers, maybe i can host my own for sharing in my own local network


RE2 - Not Able To Use Valve Handle In Room 409

Version
3.1.5 (aac76e0)
Seed
R720-RGNT-ZXHHH0G7W9Y000ZJ00W00000VXZGQTGZXZGZZ10W100ZZ
Scenario
RE 2 (Leon A)
Player Character
Ben
What happened?
In the Bridge 2F area, I can't pass through the vent without using the valve handle to slow the fan down.

Just realized this has been already reported.

Duplicate of #621


Webhook orders doesnt work

Webhook for creating orders doesnt work. results in an 302 redirect.
ik found out it was in de Magento\Framework\App\FrontController:136 the validate fails. because you post without an formkey
=> Magento\Framework\App\Request\CsrfValidator:71
adding ?ajax=true to the url solves the problem.

Sidenote: i found out that payment module Mollie does the same thing with there hooks ;-)

See Pull: https://github.com/magmodules/magento2-channable/pull/48

Thnx @wouter-toppershops, will get this merged later today!

Merged and released see 1.4.3. Channable will also add this to the urls from the platform for Magento 2 installations.


Cannot create datamodule

Hello all,
I got an error with this little program, Python 3.12, wandb 0.17.
`from anomalib import TaskType
from anomalib.models import EfficientAd
from anomalib.engine import Engine
from anomalib.deploy import ExportType
from anomalib.callbacks import ModelCheckpoint
from anomalib.data import Folder
def train():
# Create the datamodule
datamodule = Folder(
name="card_stain",
root="anomalib_surface",
normal_dir="normal",
normal_test_dir="normal",
abnormal_dir="abnormal",
mask_dir="abnormal_mask",
task=TaskType.CLASSIFICATION
)
#datamodule.setup()
if name == "main":
train()`
Returned:
    import wandb   File "F:\Python_3_12\Lib\site-packages\wandb\__init__.py", line 27, in <module>     from wandb import sdk as wandb_sdk   File "F:\Python_3_12\Lib\site-packages\wandb\sdk\__init__.py", line 28, in <module>     from .wandb_init import _attach, init   File "F:\Python_3_12\Lib\site-packages\wandb\sdk\wandb_init.py", line 31, in <module>     from . import wandb_login, wandb_setup   File "F:\Python_3_12\Lib\site-packages\wandb\sdk\wandb_login.py", line 25, in <module>     from .wandb_settings import Settings   File "F:\Python_3_12\Lib\site-packages\wandb\sdk\wandb_settings.py", line 49, in <module>     from wandb.sdk.wandb_setup import _EarlyLogger   File "F:\Python_3_12\Lib\site-packages\wandb\sdk\wandb_setup.py", line 23, in <module>     from .lib import config_util, server, tracelog   File "F:\Python_3_12\Lib\site-packages\wandb\sdk\lib\tracelog.py", line 48, in <module>     stdout_write = sys.__stdout__.write AttributeError: 'NoneType' object has no attribute 'write'
Many thanks for your help.

Hey Dirk10000, thank you for reaching out to Wandb!
Could you please share more of your code, specifically more of how you are calling Wandb and using it?
This can help us trace where your error is exactly coming from.
Thank you,
Best,
Vitoria

Thank you for your replay. The error occurs in this small script, datamodule=folder...
wandb 0.17.0
anomalib 1.0.1
All variables initialized to none are overwriten.

Thank you! Still, could you please provide more context and more code? Thanks!


Remove expected file checks

Issues with jenkins for the previous PR. So opened a new PR and resubmiting

This change is

@dmitsh resubmitted the pr. does it help ?

the test fails on the same spot


setup python ci

@kharus the pre-commit ci already does python syntax checks, so there's probably no need to also do flake8 on the github ci? In projects that use both github CI and precommit, that's what they do --- they leave the syntax linting to precommit, and do the tests on the github CI.


Chapters not refreshing immediately upon update

Steps to reproduce
https://github.com/LNReader/lnreader/assets/75091899/f5ec1e67-b0e3-49b7-b3bb-32c69456b0c5

need an entry to update and that has new chapters not "registered" (in the chapter list)
update it

Expected behavior
The new chapters appear in the list without the need to exit the entry and enter again, or changing chapter order to make them appear.
Actual behavior
The new chapters dont appear in the list unless i exit the entry and enter again, or change chapter order to make them appear.
Some sort of trigger.
LNReader version
1.1.17
Android version
Android 8
Device
Huawei p8 lite 2017
Other details
In the video you can see the total chapter count change from 466 to 469 when i changed the chapter order.
Also i didnt show it but new chapters dont appear too in the same way unless i trigger the change of chapter sorting or exit the entry.
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with a source, I should be opening an issue in the sources repository.
[X] I have updated the app to version 1.1.17.
[X] I will fill out all of the requested information in this form.

Could you check if it still exists in v2?

Cant reproduce on beta


Pod Security Policies

I know PSP is removed in 1.25. But where can I find the old doc of PSP? Is there any link to the old PSP doc?

Switch over to the version before 1.25 on the main docs site.
/close


Add gatling session attributes as context args

Description
This change allows for using the attributes in the gatling session as well as the gatling userId in karate features.
I choose to prefix all of those variables with __gatlingSession_ to distinguish them from the other variables and to avoid name collisions.
Example:
Lets say we run the following feature via gatling and the current virtual gatling user which executes the feature has the userId = 1 then appId will be set to run_perf1.
As you can see this allows for defining variables based on the gatling user which executes a feature.
Feature: Run an app

  Background:
    * def appId = 'run_perf' + __gatlingSession_userId

Relevant Issues : No issue exists
Relevant stackoverflow question: https://stackoverflow.com/questions/52853336/access-gatling-session-state-within-karate-feature
Type of change :

[x] New feature
[ ] Bug fix for existing feature
[ ] Code quality improvement
[ ] Addition or Improvement of tests
[ ] Addition or Improvement of documentation

@leozilla can you review this if it is ok:
https://github.com/intuit/karate/commit/0c98dc5e97f662addd74a75c86cc7b683b19845c


macos: brew install cannot connect to sqlite databases

I installed lazysql fresh from homebrew.
I added a connection to a file, and get the message:
Binary was compiled with 'CGO_ENABLED=0', go-sqlite3 requires cgo to work. This is a stub

Pretty sure I know how to fix this, but I wanted to report it.

Amazing, feel free to open a PR.


get_available_monitors() / get_primary_monitor() ergonomics

Right now, get_available_monitors() and get_primary_monitor() are methods of EventsLoop - that means knowing which monitors are connected to the system is only possible in a context where EventsLoop can be borrowed, which creates some issues when writing abstractions.
If at all possible, it would be very useful if Window also had these methods - after all, it already has get_current_monitor().
Concrete usecase (from ggez):
We have a struct, Context, that encapsulates away many of the inter-operation boilerplate of the engine, so it makes sense for it to own the Window. It cannot also own the EventsLoop, because Context needs to be available to make callbacks on based on the events within the loop.
Some of the callbacks are user-defined, and, it being a game engine and all, being able to tell the app to go fullscreen from within such a callback is desirable. Ideally, on any monitor, not just the current one, and that needs the data from get_available_monitors() and/or get_primary_monitor().
(Current workaround is to cache data from get_available_monitors() within the Context at initialization - EventsLoop is borrowed during that time, to initialize a Window.)

I think I'd like to finish this after #548 merges, specifically because I cleaned up monitor handling in Windows in that and don't want to make a messy rebase for myself.

Alright, that was easy: #567


FileExtension localization problem

Hello everyone,
I'm trying to localize the error message of "FileExtension" attribute but it seems not working.
I've successfully implemented the localization for "Required" attribute as explained in the official ASP.NET core guide.
I've created a simple project to reproduce the issue:
Inside the "registration" page i've added an input elemente for file upload wich is linked to RegisterViewModel, containing the "Immagine" IFormFile variable.
This IFormFile has the Required attribute and the FileExtension attribute. They are working well but not the translation of FileExtension's ErrorMessage .
Link to GIT:
https://github.com/Stefanone91/LocalizationFileSizeIssue

Hmm, it looks like we simply never added support for this attribute! Not sure why.
@dougbu @rynowak @danroth27 - any guesses as to why we never did it? We just forgot?

BTW by "never added support" I mean in MVC - I'll move the bug.

This issue was moved to aspnet/Mvc#6771


[service-bus] Allow initLink() and closeLink() to lock, preventing reentrancy/concurrency issues

initLink and closeLink had some basic coordination so they wouldn't stomp over each other but they never coordinated via locks which made it so the state of the object would be different than you expected.
This commit makes it so both closeLink and openLink depend on the same lock, which allows you to make the modifications to the link state obey ordering. This simplifies some parts of the code that tried to avoid opening and closing simultaneously.
As part of this the lock token that was being used in other parts of the code has been subsumed into LinkEntity instead so some modification to the detached/init methods of child classes changed.
Also, removed some code in ManagementLink that has become redundant with our unified initLink() code (abort signal handling and some link state checking).


2023 refactoring

Update information from 2022 to 2023
The changes includes:

remove unused images
remove unused data files
update Year
update site base url
update dates
update email
update Logo
update header images >> to use UoL images
update tito link
update "About" >> Maybe need additional changes
update teams pics & data >> Needs further update
Add temporary/hold schedule and sessions info

Wait - this is in the wrong place!

This PR should be done in the 2023 repo. Closing here to open there.


Prevent duplicate lanes from being autogenerated

Description
Prevents duplicate sets of top level lanes from being generated by ensuring that top level lanes for the most represented language is generated.
Motivation and Context
There are multiple tickets involving duplicate top level lanes.  For details on how this occurs see https://www.notion.so/lyrasis/Columbia-and-Vermont-Two-top-level-lanes-are-named-Nonfiction-b33f15333d134b40b8bb3102acfa9cdf#da1ff9ed40e74d57bcc76da9bbc3aa77
How Has This Been Tested?
I have manually tested that only one top level set of lanes are created regardless of the number of major languages are set.
Checklist

[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.

Got some test failures here.

@jonathangreen :  tests are up there and I removed the unnecessary order_by line.

Okay: rebasing fixed it, though I don't know why.

@pcustic :  the build is fixed now.  The PR is just awaiting your final approval.


sphinxsearch needs expat for xmlpipe2 support

Describe the bug
To enable xmlpipe2 support expat needs to be in nativeBuildInputs for sphinxsearch expression.
To Reproduce
Steps to reproduce the behavior:

Run sphinxsearch-indexer with xmlpipe2 source in configuration file.
Observe an error that XML support is missing.

Expected behavior
xmlpipe2 sources should work out of the box.
Metadata
 - system: `"i686-linux"`
 - host os: `Linux 4.19.72, NixOS, 19.03.173489.af5481e9b77 (Koi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.2.2`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

cc @ederoyd46

Turns out that it also doesn't support MySQL. Here's a patch which solves both problems, though expat probably belongs to buildInputs:
--- default.nix~	1970-01-01 00:00:01.000000000 +0000
+++ default.nix	2020-01-31 23:18:35.840418572 +0000
@@ -1,4 +1,4 @@
-{ stdenv, fetchurl, pkgconfig,
+{ stdenv, fetchurl, pkgconfig, expat, mariadb, zlib, openssl,
   version ? "2.2.11",
   mainSrc ? fetchurl {
     url = "http://sphinxsearch.com/files/sphinx-${version}-release.tar.gz";
@@ -12,12 +12,17 @@

   configureFlags = [
     "--program-prefix=sphinxsearch-"
-    "--without-mysql"
+    "--with-mysql=${mariadb}/"
+    "--with-libexpat"
     "--enable-id64"
   ];

   nativeBuildInputs = [
-    pkgconfig
+    pkgconfig expat
+  ];
+
+  buildInputs = [
+    mariadb zlib openssl
   ];

   meta = {

@vvs- Do you mind submitting a PR?

Done: #79032
Sorry, if I'm not up to PR expectations, but I believe these changes are tiny.

Fixed by #80727


Rest grid model menu actions type

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry, or determined not required.
[x] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[x] Updated doc comments / prop-types, or determined not required.
[x] Reviewed and tested on Mobile, or determined not required.
[x] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

Didn't change the types for similarly configured toolbarActions and formActions arrays in RestGridModel because using the separator with either of them is not supported.

@jskupsik -- would like to discuss the requirement for the PR and see if we can get it merged, or abandon it.
Do Find it more than a little weird that we are passing a disabled button to represent this separator.


separate system-probe marshal and unmarshal code

What does this PR do?
Separates out the marshalling and unmarshalling code for system-probe into two separate packages.
Motivation
The receiving side only needs to know about the protobuf format and unmarshalling code. Using separate packages means it doesn't import a whole bunch of types and packages it does not care about.
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

What is the benefit of the change?

@guyarb This reduces the number of imports that the agent and process-agent have (see the bot comment). This may have a size reduction (I'll post numbers in a bit), but it also has a semantic importance. There is no reason for the agent/process-agent to import pkg/ebpf and a lot of those pkg/network packages.

What is the benefit of the change?

@guyarb This reduces the number of imports that the agent and process-agent have (see the bot comment). This may have a size reduction (I'll post numbers in a bit), but it also has a semantic importance. There is no reason for the agent/process-agent to import pkg/ebpf and a lot of those pkg/network packages.

And on the other hand, it complicates the readability of our project furthermore and separates implementations for marshaling and unmarshaling
Unless it has a significant impact on the binary size i'd prefer to keep the already complicated project a little less complicated

Unless it has a significant impact on the binary size i'd prefer to keep the already complicated project a little less complicated

It could long-term. See this other PR which causes the ebpf-manager to be imported into process-agent. There was no way around it (both linux and linux_bpf build tags have separate problems). This PR would prevent that import.

I get that we would like to avoid the indirect import of ebpf-manager

The problem is any new import in pkg/ebpf or a bunch of other packages ends up affecting the agent/process-agent.

The unmarshaller and marshaller don't share any code. The unmarshallers are simple outside of one function to deal with zero values. I don't see how this PR is adding any complexity, it was mostly moving files.

The impact on the process-agent is less than 0.5%

That doesn't include the impact ebpf-manager and the other imports would have, since I compared against main just for this PR.

Another option is to leave the marshaller alone and move the unmarshaller out into a separate package. That would probably be less code churn.

My 2c: just reducing the number of imports in process-agent and agent reduces complexity. Anytime you can take out a few edge in the dependency graph that is a win in my book. The imports that were taken out also don't make a lot of sense to have been pulled in in the first place; its great those are gone, it makes more intuitive sense you just pull in what is needed.

/merge


More advanced sets

e.g. https://www.wolframalpha.com/input/?i=1%2Fcos(x)^2 and see "Properties as a real function"

I guess we implemented it :duck:


feat(CI): build artifacts for ARM64 on release

As we had an user requesting to run the fortigate exporter on a RaspberryPi and ARM64 becoming more and more common, I think we should provide ARM64 binaries
https://www.reddit.com/r/fortinet/comments/llwqab/fortigate_exporter_for_prometheus/grt5ipc?utm_source=share&utm_medium=web2x&context=3

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Port remaining dataset tests to new architecture

🚀 Feature
Port remaining dataset tests to new architecture.
Motivation
#3402 added new infrastructure for dataset tests. In a number of follow-up PRs tests for datasets were added that previously weren't tested. The following datasets still use the old test architecture:

ImageNet
WIDERFace
CityScapes
SVHN
Places365
STL10

Pitch
Port the remaining dataset tests to the new architecture.
cc @pmeier

All the aforementioned tests have been ported to the new test framework.


How change the cursor?

I want to change the cursor from 'point' to 'default', when onmouseover the bar.
Is there any idea?

Hi,
The issue queue is to be used for reporting defects and problems with C3.js, in addition to feature requests and ideas.
It is not a catch-all support forum.
For general support enquiries, please use the Google Group at https://groups.google.com/forum/#!forum/c3js.
All questions involving the interplay between C3.js and any other library (such as AngularJS) should be posted there first!
Thank you!


add stop method into AudioRecorder interface

should be able to stop AudioRecorder recording.

That's what the close method is for.
On Jan 22, 2015 10:25 PM, "bill-lin"<EMAIL_ADDRESS>wrote:

should be able to stop AudioRecorder recording.
—
Reply to this email directly or view it on GitHub
https://github.com/libgdx/libgdx/issues/2768.

Erm, dispose...
On Jan 22, 2015 10:25 PM, "Mario Zechner"<EMAIL_ADDRESS>wrote:

That's what the close method is for.
On Jan 22, 2015 10:25 PM, "bill-lin"<EMAIL_ADDRESS>wrote:

should be able to stop AudioRecorder recording.
—
Reply to this email directly or view it on GitHub
https://github.com/libgdx/libgdx/issues/2768.

Sorry, as I tried:
On android, dispose will not stop current recording
On desktop, dispose will stop current recording but nothing recorded/saved.
IMO, behaviour of  Stop should be:
1, stop current recording
2, save what already has been recorded

Please read the docs. AudioRecorder does not save anything, that's the
users responsibility. And dispose definitely stops the recorder on Android.
On Jan 22, 2015 10:50 PM, "bill-lin"<EMAIL_ADDRESS>wrote:

Sorry, as I tried:
On android, dispose will not stop current recording
On desktop, dispose will stop current recording but nothing recorded/saved.
IMO, behaviour of Stop should be:
1, stop current recording
2, save what already has been recorded
—
Reply to this email directly or view it on GitHub
https://github.com/libgdx/libgdx/issues/2768#issuecomment-71104778.

sorry, I mean save into short[] samples which passed into read method.
The problem I am trying to solve at the moment is:
when user touch down, start to record a 10 seconds audio sample, in another thread. If user touch up within this 10 seconds, to stop recording.
As I used dispose method to stop recording within 10 seconds:
On android, dispose will not stop current recording. It will still record the full 10 seconds. This is due to the  synchronized(mRecordingStateLock) in AudioRecord class.
On desktop, dispose will stop current recording but nothing recorded into short[] samples.

 Don't.
On Fri, Jan 23, 2015 at 7:16 AM, bill-lin<EMAIL_ADDRESS>wrote:

sorry, I mean save into short[] samples which passed into read method.
The problem I am trying to solve at the moment is:
when user touch down, start to record a 10 seconds audio sample, in
another thread. If user touch up within this 10 seconds, to stop recording.
As I used dispose method to stop recording within 10 seconds:
On android, dispose will not stop current recording. It will still record
the full 10 seconds. This is due to the synchronized(mRecordingStateLock)
in AudioRecord class.
On desktop, dispose will stop current recording but nothing recorded into
short[] samples.
—
Reply to this email directly or view it on GitHub
https://github.com/libgdx/libgdx/issues/2768#issuecomment-71152212.

thanks Nathan, what's your suggestion?

Use a small buffer and copy it into a large one.
On Jan 23, 2015 3:07 PM, "bill-lin"<EMAIL_ADDRESS>wrote:

thanks Nathan, what's your suggestion?
—
Reply to this email directly or view it on GitHub
https://github.com/libgdx/libgdx/issues/2768#issuecomment-71197357.

thanks! it's a very useful suggestion!
I will give it a go. Hopefully, would not get any gap between recordings


fix: adjust path location regular expressions to handle edge cases

PR summary

A couple of the regular expressions we use for determining the location of a given OpenAPI artifact based on the path had minor bugs that would prevent expected operations for edge cases. These are now resolved. Also, they are now packaged into utilities for easy sharing between rules and increased readability within the rule function code itself.
PR Checklist
General checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[x] Dependencies have been updated as needed
[x] .secrets.baseline has been updated as needed
[x] npm run generate-utilities-docs has been run if needed

:tada: This PR is included in version 1.25.2 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.29.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.6.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


follow up from #948 add a  remove_all_accounts() command

What is the expected enhancement?
removed many accounts are annoying we need a remove_all command

@jaygambetta oh sorry, I didn't see that you assigned this to yourself. I just saw it was filed and pushed up a patch to implement it.


[GOREPORT] Fix linting issues maya/types/v1/types.go

Goreport is showing several linting errors. Please see the report at
https://goreportcard.com/report/github.com/openebs/maya
This issue is to fix the errors in
https://github.com/openebs/maya/blob/master/types/v1/types.go
Line 1: warning: package comment should be of the form "Package v1 ..." (golint)
Line 85: warning: exported type PersistentVolumeClaimPhase should have comment or be unexported (golint)
Line 88: warning: comment on exported const ClaimPending should be of the form "ClaimPending ..." (golint)
Line 90: warning: comment on exported const ClaimBound should be of the form "ClaimBound ..." (golint)
Line 92: warning: comment on exported const ClaimLost should be of the form "ClaimLost ..." (golint)
Line 184: warning: exported type PersistentVolumeAccessMode should have comment or be unexported (golint)
Line 187: warning: comment on exported const ReadWriteOnce should be of the form "ReadWriteOnce ..." (golint)
Line 189: warning: comment on exported const ReadOnlyMany should be of the form "ReadOnlyMany ..." (golint)
Line 191: warning: comment on exported const ReadWriteMany should be of the form "ReadWriteMany ..." (golint)
Line 195: warning: exported type PersistentVolumeStatus should have comment or be unexported (golint)
Line 207: warning: exported type PersistentVolumePhase should have comment or be unexported (golint)
Line 210: warning: comment on exported const VolumePending should be of the form "VolumePending ..." (golint)
Line 212: warning: comment on exported const VolumeAvailable should be of the form "VolumeAvailable ..." (golint)
Line 215: warning: comment on exported const VolumeBound should be of the form "VolumeBound ..." (golint)
Line 217: warning: comment on exported const VolumeReleased should be of the form "VolumeReleased ..." (golint)
Line 221: warning: comment on exported const VolumeFailed should be of the form "VolumeFailed ..." (golint)
Line 225: warning: comment on exported type OpenEBS should be of the form "OpenEBS ..." (with optional leading article) (golint)

This is actually https://github.com/openebs/maya repo's issue

I made a PR for this :smile:


queryExist takes too long

Description
queryExist takes too long to complete for the first time, then it works properly.
async function queryExist(jid) {
return await WPP.contact.queryExists(jid);
}
Environment

WhatsApp version: 2.2330.11
WA-JS version(s): v2.24.7
Browser: Chrome 114.0.5735.198 (Official Build) (arm64)
OS: Windows X / OSX 13.4.1
MultiDevice (BETA): yes/no

Steps to Reproduce

run await WPP.contact.queryExists(jid);
it doesn't return anything for too long
after returning, subsequent call works normally

Log Output
If relevant, paste all of your Log Output

Your Code
async function queryExist(jid) {
	return await WPP.contact.queryExists(jid);
}

Additional context / Screenshot
Add any other context about the problem here. If applicable, add screenshots to help explain.

@edgardmessias how to fix this?

@rhutikcodes , I did some tests, but I couldn't reproduce it

this is very random issue, No any issue with this library.
Response from WhatsApp server takes too much time. Simply disconnect you internet and connect again


Use terasology.org as default host for master-server

Heroku is changing its hosting policy and pricing scheme, which is less suitable for 24/7 online services.
I hereby suggest changing the default server URL in NetworkConfig to master-server.terasology.org, which can be configured to redirect request to any URL. This should facilitate migrating away from Heroku.
NOTE: the URL must be configured to forward to master-server.herokuapp.com before this PR can be merged.
This PR also contains a few related tweaks (partly based on new Java 8 features).

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/86/
Hooray Jenkins reported success with all tests good!

Should we just make a new DNS entry and point it to one of the existing droplet IPs where we can fit the service(s) needed? We have a little time before Heroku goes 25% dark but we could always just get it out of the way early.
Forum linky for reference, could do more technical discussion there: http://forum.terasology.org/threads/master-server.1269/

The new host is reachable (for testing) at:
http://master-server.martin-steiger.de

This should be complete now.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/150/
Hooray Jenkins reported success with all tests good!

Cool :-)
Let me know if you want to change the naming around sometime, but I figure no rush.
Still working on server setup? I figure the actual functionality in-game works, but going to https://master-server.terasology.org in a browser gets you a certificate error + a standard placeholder page in Apache. Using HTTP works fine and shows the site normally.


Move keys to their own object

This PR does not change anything to the inner working of the plugin, but provides an easier way to reference the keys that are used in the plugin, espcially in .scala builds.
The keys can now be imported with: import de.heikoseeberger.sbtheader.HeaderKeys._.
import de.heikoseeberger.sbtheader.HeaderPlugin.autoImport._ still works.

Renamed HeaderKeys to HeaderKey.
Should I also modify the import ?

Thanks for your contribution!

You're welcome :)