Add More Arc to AggregateFunctionExpr

Draft as I run benchmarks
Which issue does this PR close?
Follow on to https://github.com/apache/datafusion/pull/12950
Rationale for this change
While reviewing https://github.com/apache/datafusion/pull/12950 from @askalt I noticed a few places where deep copies of Schema was happening when we could have simply been copying Arcs
What changes are included in this PR?
Add some more Arc to improce performance
Are these changes tested?

Are there any user-facing changes?

Running performance tests...

I ran some benchmarks and didn't see any noticable difference in performance:

++ critcmp main alamb_more_arc
group                                         alamb_more_arc                         main
-----                                         --------------                         ----
logical_aggregate_with_join                   1.00  1413.0±16.22µs        ? ?/sec    1.00  1411.4±15.49µs        ? ?/sec
logical_plan_tpcds_all                        1.01    194.5±1.17ms        ? ?/sec    1.00    193.4±1.14ms        ? ?/sec
logical_plan_tpch_all                         1.01     24.1±0.27ms        ? ?/sec    1.00     23.9±0.22ms        ? ?/sec
logical_select_all_from_1000                  1.00      5.3±0.03ms        ? ?/sec    1.00      5.3±0.05ms        ? ?/sec
logical_select_one_from_700                   1.01  1144.7±14.16µs        ? ?/sec    1.00  1133.9±21.82µs        ? ?/sec
logical_trivial_join_high_numbered_columns    1.01  1095.8±45.65µs        ? ?/sec    1.00  1083.1±16.25µs        ? ?/sec
logical_trivial_join_low_numbered_columns     1.02  1086.2±52.96µs        ? ?/sec    1.00  1065.2±20.14µs        ? ?/sec
physical_plan_tpcds_all                       1.00   1219.6±2.84ms        ? ?/sec    1.00   1219.7±2.84ms        ? ?/sec
physical_plan_tpch_all                        1.00     80.4±0.59ms        ? ?/sec    1.00     80.3±0.62ms        ? ?/sec
physical_plan_tpch_q1                         1.00      2.9±0.02ms        ? ?/sec    1.00      2.9±0.03ms        ? ?/sec
physical_plan_tpch_q10                        1.00      4.0±0.04ms        ? ?/sec    1.00      4.0±0.04ms        ? ?/sec
physical_plan_tpch_q11                        1.00      3.4±0.03ms        ? ?/sec    1.00      3.4±0.03ms        ? ?/sec
physical_plan_tpch_q12                        1.00      2.8±0.03ms        ? ?/sec    1.00      2.8±0.03ms        ? ?/sec
physical_plan_tpch_q13                        1.00      2.2±0.02ms        ? ?/sec    1.00      2.2±0.02ms        ? ?/sec
physical_plan_tpch_q14                        1.00      2.5±0.02ms        ? ?/sec    1.00      2.5±0.02ms        ? ?/sec
physical_plan_tpch_q16                        1.00      3.5±0.02ms        ? ?/sec    1.00      3.5±0.03ms        ? ?/sec
physical_plan_tpch_q17                        1.00      3.2±0.03ms        ? ?/sec    1.00      3.2±0.03ms        ? ?/sec
physical_plan_tpch_q18                        1.00      3.7±0.03ms        ? ?/sec    1.00      3.7±0.04ms        ? ?/sec
physical_plan_tpch_q19                        1.00      5.1±0.04ms        ? ?/sec    1.01      5.2±0.41ms        ? ?/sec
physical_plan_tpch_q2                         1.00      6.7±0.05ms        ? ?/sec    1.00      6.7±0.05ms        ? ?/sec
physical_plan_tpch_q20                        1.00      4.1±0.05ms        ? ?/sec    1.00      4.1±0.05ms        ? ?/sec
physical_plan_tpch_q21                        1.00      5.4±0.05ms        ? ?/sec    1.00      5.4±0.04ms        ? ?/sec
physical_plan_tpch_q22                        1.00      3.1±0.03ms        ? ?/sec    1.00      3.1±0.03ms        ? ?/sec
physical_plan_tpch_q3                         1.00      3.0±0.02ms        ? ?/sec    1.00      3.0±0.02ms        ? ?/sec
physical_plan_tpch_q4                         1.00      2.3±0.02ms        ? ?/sec    1.00      2.3±0.02ms        ? ?/sec
physical_plan_tpch_q5                         1.01      4.1±0.03ms        ? ?/sec    1.00      4.1±0.02ms        ? ?/sec
physical_plan_tpch_q6                         1.00  1669.9±17.99µs        ? ?/sec    1.00  1663.1±18.41µs        ? ?/sec
physical_plan_tpch_q7                         1.00      5.2±0.04ms        ? ?/sec    1.00      5.2±0.03ms        ? ?/sec
physical_plan_tpch_q8                         1.00      6.2±0.04ms        ? ?/sec    1.00      6.2±0.04ms        ? ?/sec
physical_plan_tpch_q9                         1.00      4.9±0.03ms        ? ?/sec    1.00      4.9±0.05ms        ? ?/sec
physical_select_aggregates_from_200           1.00     28.5±0.30ms        ? ?/sec    1.00     28.5±0.28ms        ? ?/sec
physical_select_all_from_1000                 1.00     40.4±0.20ms        ? ?/sec    1.00     40.5±0.30ms        ? ?/sec
physical_select_one_from_700                  1.00      3.6±0.02ms        ? ?/sec    1.00      3.6±0.02ms        ? ?/sec

So I am inclined to not pursue this PR any

tpch queries operate on rather small (narrow) schemas.

tpch queries operate on rather small (narrow) schemas.

That is true -- I do think logical_select_all_from_1000  and logical_select_one_from_700  physical_select_aggregates_from_200 is on a wider schema
I am sure this makes things a tiny bit faster but my benchmarks suggest it isn't very measurable

Wouldn't it be better to maintain consistency throughout the entire codebase?

Wouldn't it be better to maintain consistency throughout the entire codebase?

I agree it would be good to maintain consistency when possible. Are you thinking that this PR is more consistent? It is not entirely clear to me how much we like / don't like Arc (I don't think it is totally consistent yet)

That is true -- I do think logical_select_all_from_1000  and logical_select_one_from_700  physical_select_aggregates_from_200 is on a wider schema

I figured, but their names suggest these are very simple queries.
and real-life will have combination of both: wide schemas and complex query plans, where optimizers will do more changes along the way.


Feature/merge imports

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix Codesandbox Integration

Fix Codesandbox Integration

https://codesandbox.io/s/ww2kyjp5vw
Originally brought on my radar by @knicklabs and @ShayCichocki (❤)
I got it working with Codesandbox. Stackblitz is.. another thing. Not sure how to resolve it on there. The issue is that Stackblitz is trying to compile/parse SCSS->CSS things. I don't know how to make it NOT do that.

Coverage remained the same at 100.0% when pulling 43af15c0cc110f088382934a027ae81c7592f7ec on fix-codesandbox-integration into<PHONE_NUMBER>66fad7f6de098c59d228b02ccf86b2 on master.

❤


Request for info: How long does training usually take?

Awesome project, how long does training take on reference hardware?

Thanks for your interest.
On a single GTX1080Ti GPU it takes less than an hour of training


Flutter doesn't clean memory after failing to compile for Android

This says it all

This is my code, everything else is created by default, didn't touch it

Flutter doctor in case you need it

Hi @Mattew05, thanks for filing the issue. I am unable to reproduce the issue. I see the memory getting released when the build fails. Please see the below output
https://user-images.githubusercontent.com/31410839/165739779-81bb6eb5-838c-4a76-b0f8-d722bae4c8f9.mp4
Does this happen when you compile for any specific platform? I verified when compiling for Android and chrome.

flutter doctor -v (windows)
[√] Flutter (Channel stable, 2.10.5, on Microsoft Windows [Version 10.0.19044.1645], locale en-US)
    • Flutter version 2.10.5 at C:\flutter_sdk\stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5464c5bac7 (2 days ago), 2022-04-18 09:55:37 -0700
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\mahesh\AppData\Local\Android\sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.4)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.11.31727.386
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2020.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[√] VS Code (version 1.64.2)
    • VS Code at C:\Users\mahesh\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.38.1

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19044.1645]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 100.0.4896.127
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 100.0.1185.44

[√] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

It only happens when i build for android, windows applications and web ones work fine, i tried using my phone connected with a cable and the emulator from android studio and here is the issue recreated using the emulator from android studio https://youtu.be/xyTF-ClPKJA

Thanks for the update @Mattew05, But I am unable to reproduce the issue even when building for the Android emulator. I see the allocated memory being cleaned on build failure.
https://user-images.githubusercontent.com/31410839/165896246-0b6a299f-a9c6-4bd8-bd00-5c53d9721ae3.mp4
However, I am able to see any difference in the environment of both of our machines that might be causing this issue. Can ou check if the memory remains allocated for other emulators or Physical Android devices too?
Labeling this issue for further investigation from the team.

flutter doctor -v (windows)
[√] Flutter (Channel stable, 2.10.5, on Microsoft Windows [Version 10.0.19044.1645], locale en-US)
    • Flutter version 2.10.5 at C:\flutter_sdk\stable
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5464c5bac7 (2 days ago), 2022-04-18 09:55:37 -0700
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at C:\Users\mahesh\AppData\Local\Android\sdk
    • Platform android-31, build-tools 31.0.0
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.11.4)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    • Visual Studio Community 2019 version 16.11.31727.386
    • Windows 10 SDK version 10.0.19041.0

[√] Android Studio (version 2020.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
       https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
       https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)

[√] VS Code (version 1.64.2)
    • VS Code at C:\Users\mahesh\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.38.1

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19044.1645]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 100.0.4896.127
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 100.0.1185.44

[√] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

code sample
flutter pub add english_words

import 'package:flutter/material.dart';
import 'package:english_words/english_words.dart';

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

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    final wordPair = WordPair.random();
    return MaterialApp(
      title: 'Welcome to Flutter',
      home: Scaffold(
        appBar: AppBar(
          title: const Text('Welcome to Flutter'),
        ),
        body: const Center(
			child: Text(wordPair.asPascalCase),
        ),
      ),
    );
  }
}

The only things I have to add is that I had problems with getting flutter doctor to see the java version and the steps that I went through were: reinstalling android studio 2 times, changing the java_home path to jdk instead of the default jre and deleting the old android studio folders. When I tried compiling while it wasn't seeing the java version it was giving me the same error as now:
C:\Users\matei\Desktop\startup_namer>flutter` run
Launching lib\main.dart on S88Pro in debug mode...
FAILURE: Build failed with an exception.

What went wrong:
Unable to find a usable idle daemon. I have connected to 100 different daemons but I could not use any of them to run the build. BuildActionParameters were DefaultBuildActionParameters{, currentDir=C:\Users\matei\Desktop\startup_namer\android, systemProperties size=55, envVariables size=65, logLevel=QUIET, useDaemon=true, continuous=false, injectedPluginClasspath=[]}.

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

Get more help at https://help.gradle.org
Running Gradle task 'assembleDebug'...                            252.2s
Exception: Gradle task assembleDebug failed with exit code 1

Android Studio works fine, can't recreate the error in it though due to the nature of it.
Flutter doctor -v:
C:\Users\matei>flutter doctor -v
[√] Flutter (Channel stable, 2.10.5, on Microsoft Windows [Version 10.0.19044.1645], locale en-US)
• Flutter version 2.10.5 at C:\src\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 5464c5bac7 (11 days ago), 2022-04-18 09:55:37 -0700
• Engine revision 57d3bac3dd
• Dart version 2.16.2
• DevTools version 2.9.2
[√] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
• Android SDK at C:\Users\matei\AppData\Local\Android\sdk
• Platform android-31, build-tools 32.0.0
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.11+9-b60-7590822)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe
[√] Visual Studio - develop for Windows (Visual Studio Community 2022 17.1.5)
• Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
• Visual Studio Community 2022 version 17.1.32414.318
• Windows 10 SDK version 10.0.19041.0
[√] Android Studio (version 2021.1)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.11+9-b60-7590822)
[√] IntelliJ IDEA Community Edition (version 2021.1)
• IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2020.3.3
• 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
[√] VS Code (version 1.66.2)
• VS Code at C:\Users\matei\AppData\Local\Programs\Microsoft VS Code
• Flutter extension can be installed from:
https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[√] Connected device (4 available)
• S88Pro (mobile)   • E977UA1ZM18160624 • android-arm64  • Android 10 (API 29)
• Windows (desktop) • windows           • windows-x64    • Microsoft Windows [Version 10.0.19044.1645]
• Chrome (web)      • chrome            • web-javascript • Google Chrome 100.0.4896.127
• Edge (web)        • edge              • web-javascript • Microsoft Edge 100.0.1185.50
[√] HTTP Host Availability
• All required HTTP hosts are available
• No issues found!

I'd suggest asking this question on stackoverflow. If you do ask there, please close this issue as well. Thanks!


Handing error response when mailchimp still returns 200

:tada: This PR is included in version 3.0.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Is there any difference?

I have just successfully purchased an RFID Reader/Writer (just like this one) on AliExpress: https://www.aliexpress.com/item/RFID-Copier-125KHz-EM4100-Cloner-Writer-Duplicator-Programmer-Reader-5-Pcs-EM4305-T5577-Rewritable-ID-Keyfobs/32721839667.html?spm=a2g0s.90423<IP_ADDRESS>b494c4d1v0Omv, interesting thing is that when I searched for IDRW V3 on Google Images, all photos contained the same reader but instead they all had following text on them: Microsoft Windows, FC and USB Reader. The only thing that his has is RFID Reader, should it work? Or I just purchased something not right?

From the bottom diagram, it looks like it is not a USB HID device; it might be USB to Serial. Maybe you could ask the seller the name of the tool it uses? That might give you some clue.

It seems there is no name for this device. Everyone just calls it RFID Card Reader. Neither the Windows one has a name. That's an interesting thing.

I found this video using (from the look) same device https://youtu.be/vCaVs2aS1tQ, even though it's a different store, the bottom of the reader looks the same (USB-203, ID, USB, R/W). In the video, we can see that it acts as a USB Input Device

I'm not sure if this device would be compatible with my library, but let me know when you have it; if it doesn't work we'll try to add support for it.

@charlysan Sure, I have also seen some RFID readers/writers like these in AliExpress which also showed a picture of IDRW V3 in use with it, so I am 90% confident it should work, if not, I'll try to reverse engineer the software they provide and look into the serial communication between the device and computer.

Oh and also, this GitHub repository seems really interesting to me. RFID App is a really popular application which is used in these AliExpress products. You may want to take a look there.

Yes, I've seen that app; it's great!

By the way, does this reader/writer work with HID ProxCards, AWID cards?

No HID/AWID support by this reader/writer. AFAIK, only EM4305 and T5577.

Yup! AFAIK EM4xxx and T55xx

@vale5566, that device might work as a USB HID Keyboard. The one I have it's different, it has a custom "protocol" with commands for reading and writing a tag. Have you tried merbanan rfid_app? One more thing, could you please paste your output for sudo lsusb -vd ffff:0035?

output from sudo lsusb -vd ffff:0035:
Bus 001 Device 006: ID ffff:0035   Device Descriptor:   bLength                18   bDescriptorType         1   bcdUSB               1.10   bDeviceClass            0    bDeviceSubClass         0    bDeviceProtocol         0    bMaxPacketSize0         8   idVendor           0xffff    idProduct          0x0035    bcdDevice            1.00   iManufacturer           1 Sycreader   iProduct                2 USB Reader   iSerial                 3 08FF20150112   bNumConfigurations      1   Configuration Descriptor:     bLength                 9     bDescriptorType         2     wTotalLength       0x0034     bNumInterfaces          2     bConfigurationValue     1     iConfiguration          0      bmAttributes         0xa0       (Bus Powered)       Remote Wakeup     MaxPower              100mA     Interface Descriptor:       bLength                 9       bDescriptorType         4       bInterfaceNumber        0       bAlternateSetting       0       bNumEndpoints           1       bInterfaceClass         3 Human Interface Device       bInterfaceSubClass      1 Boot Interface Subclass       bInterfaceProtocol      1 Keyboard       iInterface              4 Keyboard         HID Device Descriptor:           bLength                 9           bDescriptorType        33           bcdHID               1.10           bCountryCode           33 US           bNumDescriptors         1           bDescriptorType        34 Report           wDescriptorLength      65          Report Descriptors:             ** UNAVAILABLE **       Endpoint Descriptor:         bLength                 7         bDescriptorType         5         bEndpointAddress     0x81  EP 1 IN         bmAttributes            3           Transfer Type            Interrupt           Synch Type               None           Usage Type               Data         wMaxPacketSize     0x0008  1x 8 bytes         bInterval              10     Interface Descriptor:       bLength                 9       bDescriptorType         4       bInterfaceNumber        1       bAlternateSetting       0       bNumEndpoints           0       bInterfaceClass         3 Human Interface Device       bInterfaceSubClass      0        bInterfaceProtocol      0        iInterface              5 Vender Hid         HID Device Descriptor:           bLength                 9           bDescriptorType        33           bcdHID               1.10           bCountryCode           33 US           bNumDescriptors         1           bDescriptorType        34 Report           wDescriptorLength      35           Report Descriptor: (length is 35)             Item(Global): Usage Page, data= [ 0xa0 0xff ] 65440                             (null)             Item(Local ): Usage, data= [ 0x01 ] 1                             (null)             Item(Main  ): Collection, data= [ 0x01 ] 1                             Application             Item(Global): Report ID, data= [ 0x01 ] 1             Item(Local ): Usage, data= [ 0x08 ] 8                             (null)             Item(Global): Logical Maximum, data= [ 0xff 0x00 ] 255             Item(Global): Logical Minimum, data= [ 0x00 ] 0             Item(Global): Report Size, data= [ 0x08 ] 8             Item(Global): Report Count, data= [ 0xff ] 255             Item(Main  ): Feature, data= [ 0x02 ] 2                             Data Variable Absolute No_Wrap Linear                             Preferred_State No_Null_Position Non_Volatile Bitfield             Item(Global): Report ID, data= [ 0x02 ] 2             Item(Local ): Usage, data= [ 0x08 ] 8                             (null)             Item(Main  ): Feature, data= [ 0x02 ] 2                             Data Variable Absolute No_Wrap Linear                             Preferred_State No_Null_Position Non_Volatile Bitfield             Item(Global): Report ID, data= [ 0x03 ] 3             Item(Local ): Usage, data= [ 0x08 ] 8                             (null)             Item(Main  ): Feature, data= [ 0x02 ] 2                             Data Variable Absolute No_Wrap Linear                             Preferred_State No_Null_Position Non_Volatile Bitfield             Item(Main  ): End Collection, data=none can't get debug descriptor: Resource temporarily unavailable cannot read device status, Resource temporarily unavailable (11)
Yes I t tried the rfid_app I get the same error as this comment.

Does it work with preincluded software by the seller? If so, can you tell us the name of it.

There was no software included.
I write the seller at Aliexpress but I don't think I get an helpful answer.

Okay I found the solution I disassembled the package and the chip can only read.
But thanks for your help!

That makes sense @vale5566, as the device behaves as a Keyboard. Could you please share a picture of the back of the device? (it if has same labels). That information might be useful.

Sure, but there is no label.
link to the photo: https://ittuberlin-my.sharepoint.com/:i:/g/personal/5146500509788880_msopseudo_tu-berlin_de/EXJ6PE3cLR9NuA3GF2ypa64B6wD8XdZsWpL5jWi-oI4Wew?e=nde7UX

@charlysan the HID option in my picture meant no Human Interface Device, but whether it supports HID Corporation cards such as HID ProxCard II

True. Thanks for clary clarifying that @moliata.

@charlysanthere are 2 RFID Reader/Writer versions. ffff:0035 version and 6688:6850 version. Your code works with the ffff:0035, but my device is the second version 6688:6850. It is also HID device, but with a different PID/VID and different commands. RFID APP repository worked for me, so we should take a look on how to implement it.

That's seems to be a more complex reader than mine @moliata. Just in case, please try out v0.1.1 branch.

Arghh... I am not able to send the data to the RFID reader because of the https://github.com/pyusb/pyusb/issues/208

Don't need to rewrite code for your vid/pid, you can just pass any vid/pid to the constructor. ffff:0035 are just the default values @moliata

@charlysan yeah, but I am not able to run your code because of the insufficient permissions error on my Macbook.

You can use a Linux VM until the guys from pyusb figure out out to solve that issue @moliata.

It seems the problem is with Mac computers security... The kernel driver is binded to a HID device, disallowing me to use it. I'll try it with my Ubuntu laptop, thanks!

Strange @moliata. I can confirm that I can read and write tags using my Mac. I've just tried it out (MacOS HighSierra 10.13.6 (17G65)).

I am not able to write with 10.13.5 (MacBook Air Early 2015).


unmount after storyshot snapshot

Issue: Not unmounting after test causes failures when running multiple tests with a shared decorator. Running the test on its own passes.
Possibly a decorator running causes a tested React component to re-render. If that decorator changes the underlying data assumptions of said component, problems arise.
What I did
Fix #2417 which I reported several minor versions ago and included more details on.

unmount after finished with rendered tree
small refactoring so I would only have to call unmount once instead of 3x

How to test
I have an app which this fixes. I could potentially come up with a smaller reproducing app if there are doubts about what this change does.
In my case, the decorator resets my Redux state; each story adds the data its component depends on. (Maybe not an expected use of Storybook but I find it a great way to get a lot of integration testing of reducers+selectors+containers along with presentational components.)
I was getting failures from a random component (always the same one so long as the stories don't change) because its data was wiped away by the decorator's reset and it tried to re-render.
Is this testable with jest or storyshots?
Possibly with jest mock function, counting number of times it is called.
Does this need a new example in the kitchen sink apps?
I don't know.
Does this need an update to the documentation?
I don't think so.
If your answer is yes to any of these, please make sure to include it in your PR.

Fix #2417
Looks like it's a typo, #2417 is this PR

Sorry for typo. Should have been #1634 which can be closed now.


Bug: Are docs wrong for v0 version?

What happened?
Docs says to use setupCache from 'axios-cache-interceptor' but there is no setupCache export in v0. is this a typo ?
import { setupCache } from 'axios-cache-interceptor';

const axios = setupCache(Axios);

axios-cache-interceptor version
v0.2
Node / Browser Version
18
Axios Version
0.21
What storage is being used
Memory Storage
Relevant debugging log output
setupCache is undefined.

Axios Cache Interceptor v0 does exports setup cache.
pnpm i axios-cache-interceptor@0
node -e "console.log(require('axios-cache-interceptor'))"

outputs:
Object [Module] {
  Header: [Getter],
  buildKeyGenerator: [Getter],
  buildMemoryStorage: [Getter],
  buildStorage: [Getter],
  buildWebStorage: [Getter],
  canStale: [Getter],
  createCacheResponse: [Getter],
  createValidateStatus: [Getter],
  defaultHeaderInterpreter: [Getter],
  defaultKeyGenerator: [Getter],
  defaultRequestInterceptor: [Getter],
  defaultResponseInterceptor: [Getter],
  isExpired: [Getter],
  isMethodIn: [Getter],
  isStorage: [Getter],
  setupCache: [Getter], // <---- HERE
  testCachePredicate: [Getter],
  updateCache: [Getter],
  updateStaleRequest: [Getter]
}

@arthurfiorette This is what i get. I am using version ^0.2.8 since my axios version is 0.21.1
{
  StatusCodes: {
    CACHED_STATUS_CODE: 304,
    CACHED_STATUS_TEXT: '304 Cached by axios-cache-interceptor'
  },
  applyCache: [Getter],
  createCache: [Getter]
}

that's not my axios-cache-interceptor

The package has a README bundled with the source code inside your node_modules, you can read it.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-main" workflow

AWS CodeBuild CI Report

CodeBuild project: DDKIntegrationTestsD8472609-5SCHWjldmWcf
Commit ID: ed26b3ff4470cfb737e477ddce7c2cc2674f65fa
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


⚠ Bofrost.de has degraded performance

In f2f7cdb, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1530 ms

Resolved: Bofrost.de performance has improved in 2f69712 after 2 hours, 38 minutes.


L.Map.Tap needs to be revised

https://github.com/Leaflet/Leaflet/blob/d1a1e97b8290f642eb677284af53c2db64199a76/src/map/handler/Map.Tap.js#L18-L20
So here listed only 2 purposes:

Fix click delay on mobile devices
Simulate contextmenu events (reason is not described)

So let's take it in order:

Good point, but since 2013 there is much more proper way to achieve it: https://developers.google.com/web/updates/2013/12/300ms-tap-delay-gone-away
I admit that it still can be useful in some rare circumstances, but in any case it should not be enabled by default.
I know only 1 possible reason: iOS devices do not produce contextmenu.
So instead of simulating that unconditionally we should check L.Browser.safari (or just 'iOS substring in navigator.userAgent).
See also #6977.

And more:
3. Handler is enabled by default in Map options, but also has additional not documented condition:  https://github.com/Leaflet/Leaflet/blob/d1a1e97b8290f642eb677284af53c2db64199a76/src/map/handler/Map.Tap.js#L133-L136
Browser.touch looks reasonable (though see #6978), but what the hell is Browser.pointer?
Blame leads to commit which addressed some IE10 issue.
But I still cannot get it's cumbersome purpose, so that must be either documented or revised (which is more likely, as this condition is obviously affects not only IE10).
Also, this may prevent to achieve (1).
4. Besides of 2 documented purposes I see in code something not clear:
simulation of mousedown and mousemove
https://github.com/Leaflet/Leaflet/blob/d1a1e97b8290f642eb677284af53c2db64199a76/src/map/handler/Map.Tap.js#L71
https://github.com/Leaflet/Leaflet/blob/d1a1e97b8290f642eb677284af53c2db64199a76/src/map/handler/Map.Tap.js#L112

   But nowadays browsers by their own generate needed mouse events on response on touch.
   (one exception is iOS where we have no `contextmenu`).
So I believe that events are simulated to match simulated click event.
But wait a minute, doesn't matter the correct sequence of events?
See the specs: https://w3c.github.io/touch-events/#mouse-events
As stated, mousedown, mousemove events must come ONLY after touchend and only for case when click is emitted.
Also, there are other events that should pair the click. You can read the spec or try it youself.

I see only sole real application of tap handler: contextmenu emulation for iOS.
And this is pretty similar to another synthetic dblclick, provided by DomEvent.DoubleTap.js.
So I wonder why former is implemented as separate handler, while latter is built in core.


Add config to enable mixed types as string in GpuJsonToStruct & GpuJsonScan

Closes https://github.com/NVIDIA/spark-rapids/issues/10253
Changes in this PR:

Add repro test for A mix of lists and structs within the same column is not supported
Enable "mixed types as strings" support, fixing this test
Add a new config to enable this, because there are some known issues (https://github.com/rapidsai/cudf/issues/14864)

build

build

build

Test failures with st_hash_grpby_sum
BlockManagerMaster: Failed to remove shuffle 11 - An executor with RapidsShuffleManager is trying to use a ShuffleBufferCatalog that isn't initialized.
2024-01-26T19:11:39.8073853Z [2024-01-26T19:09:27.685Z] java.lang.IllegalStateException: An executor with RapidsShuffleManager is trying to use a ShuffleBufferCatalog that isn't initialized.

build failing due to https://github.com/NVIDIA/spark-rapids/issues/10291

build


how to deploy application in weblogic using docker-compose.yaml file

We have not attempted to design a solution for WebLogic application deployment using Docker Compose.
Instead, we do have tools to generate a container image with a fully configured domain (including application deployment) using two open-source tools: 1) the WebLogic Deploy Tool and 2) the WebLogic Image Tool.
Separately, we've done a lot of work on running WebLogic within a Kubernetes cluster, including application deployment.

Yes..using the samples ..you have given in github...Iam able to deploy single application with domain but is there any solution to deploy muktiple applications same time

We don't have any sample here that does that already, but the intention was that the samples could be edited to meet your needs.

okay


Missing Gdal dataset open flags

The gdal::open_ex open_flags allow only value from the GDALAccess::Type values.
This prevent using the others GDAL_OF_XXX flags combination.
They are preprocessor #define  in gdal.h and thus skipped by bindgen; they are still essential to control some opening behaviors like raster/vector driver selection, or multidimensional raster or gnm drivers.
Maybe a crate like bitflags could help.

The bitflags approach is very cool; I'd opened a similar issue but this is more comprehensive, so I'm closing it.  There is one issue with the open_ex options: GDAL_OF_SHARED that needs to be discussed (see below).
Sharing Issue
GDAL since 2.4 allows Dataset to be accessed from different threads, as long as only one thread accesses it at any time (ref. discussion).  In this crate, we impl Send on Dataset to reflect that we can pass it to another thread, but not Sync so it is not accessed from two threads at the same time.
However, the GDAL_OF_SHARED option allows this to be subverted.  We might open the same dataset twice with the shared option, and then pass one of the Dataset handles to another thread.  This could lead to undefined behaviours as we are accessing a non-thread-safe data-structure from different threads simultaneously.
The simplest solution I could think of is to remove GDAL_OF_SHARED from the bitflags, thus not allowing it in the flags.  Then, we could add a flag in DatasetOptions which can only be set via an unsafe method.   This way, we allow shared open, if the user knows what they're doing, and there's no way to get UB via safe rust.

The bitflags approach is very cool; I'd opened a similar issue but this is more comprehensive, so I'm closing it.  There is one issue with the open_ex options: GDAL_OF_SHARED that needs to be discussed (see below).
Sharing Issue
GDAL since 2.4 allows Dataset to be accessed from different threads, as long as only one thread accesses it at any time (ref. discussion).  In this crate, we impl Send on Dataset to reflect that we can pass it to another thread, but not Sync so it is not accessed from two threads at the same time.
However, the GDAL_OF_SHARED option allows this to be subverted.  We might open the same dataset twice with the shared option, and then pass one of the Dataset handles to another thread.  This could lead to undefined behaviours as we are accessing a non-thread-safe data-structure from different threads simultaneously.
The simplest solution I could think of is to remove GDAL_OF_SHARED from the bitflags, thus not allowing it in the flags.  Then, we could add a flag in DatasetOptions which can only be set via an unsafe method.   This way, we allow shared open, if the user knows what they're doing, and there's no way to get UB via safe rust.

wow this is a really cool solution. I think @rmanoka is right. we should remove the shared bitfag and add an unsafe method to DatasetOptions to enable this feature.

wow this is a really cool solution. I think @rmanoka is right. we should remove the shared bitfag and add an unsafe method to DatasetOptions to enable this feature.

I do agree that GDAL_OF_SHARED defeat the purpose of multithreading safety and I'm also in favor te remove it.

I do agree that GDAL_OF_SHARED defeat the purpose of multithreading safety and I'm also in favor te remove it.

Then, we could add a flag in DatasetOptions which can only be set via an unsafe method

Amha, this is even not necessary and it would be better to rely on rust safe way of handling shared access to dataset.

Then, we could add a flag in DatasetOptions which can only be set via an unsafe method

Amha, this is even not necessary and it would be better to rely on rust safe way of handling shared access to dataset.

i guess we can add a special method for shared later ( if we need it)

i guess we can add a special method for shared later ( if we need it)

Amha, this is even not necessary and it would be better to rely on rust safe way of handling shared access to dataset.

Sounds good; bitflags already has an unsafe fn from_bits_unchecked that allows this anyway.

Amha, this is even not necessary and it would be better to rely on rust safe way of handling shared access to dataset.

Sounds good; bitflags already has an unsafe fn from_bits_unchecked that allows this anyway.


[Fixed] DaVinci Resolve 18.5+ w/ Rocky Linux 8.6 support

DaVinci Resolve (DVR) 18.5+, beta announced today, will have official Rocky Linux support:

Rocky Linux 8.6 or CentOS 7.3.

DVR-in-a-containers have worked with Rocky/Alma/Centos 9 stream already, but it's not a bad idea to make sure the build works with this older 8.x version.
Here are some issues I found with the new beta, plus quick solutions for anyone experiencing a crash on ./build.shing.
After addressing these issues, Resolve started properly on Ubuntu 23.04 (beta) with pipewire.  Hopefully soon we'll have a PR to get this all in.  In fact, we might want to start making:
RESOLVE_BASE_CONTAINER_IMAGE=rockylinux:8.6
The default OS if version 18.5+ is being installed just to match up with what BlackMagic Design supports officially.
Issue:  DVR 18.5 has new package dependencies:
libglvnd-opengl and pulseaudio-libs are reported missing.
Solution:  Add these two packages to the Dockerfile.
NOTE:  Tested on Centos 8.6 and Almalinux 9 and worked for both.
Issue: Rocky Linux 8.6 doesn't know anything about:
libxcrypt-compat and compat-openssl11  (which we're using w/pipewire on centus/alma/rocky 9)
Solution for Rocky 8.6:
Pull these two packages out of the Dockerfile when building for Rocky 8.x.  For Rocky 8.x, you can install compat-openssl10 for the onboarding app to work.
(Confirmed it works without them for Ubuntu 23.04 w/pipewire.)
NOTE:  Removing libxcrypt-compat breaks DVR 18.5b1 on Alma Linux 9, so will have to check if they should be added or not on the fly.
Issue:  DaVinci_Resolve_Welcome breaks
In almalinux 9, needs these packages:  nss (for libsmime3.so), libXcomposite (for libXcomposite.so.1), libXdamage (for libXdamage.so.1) and it still needs compat-openssl10 to address the QSslSocket: issues per issue #26.  This hasn't been fixed due to the security implications of an older/deprecated OpenSSL.
As mentioned, Rocky 8.6 uses compat-openssl10 to make onboarding work, even though it's deprecated.
Issue: CRB repository missing in Centos 8.6 (x264 encoder only)
If BUILD_X264_ENCODER_PLUGIN is set, the --enablerepo=crb which works nicely in centos/alma/rocky 9 is missing from Rocky 8.  This repo is needed to find nasm used for making the encoder plugin.
NOTE:  This breaks Alma Linux 9 build, so will have to check which to use.  If anyone more familiar with the centos distro knows how to do this correctly, please respond otherwise I'll have to wing it.
Solution for Rocky 8.6:
Replacing crb with powertools in the  Dockerfile seems to fix this on Rocky 8.6.  At least the build crash goes away and DVR still seems to work okay.
Issue: "ed" the simple patch/text editor not found  (x264 encoder only)
Solution for Rocky 8.6:
ed needs to be added to the packages to be installed in the Dockerfile if the x264 encoder is being built.
NOTE:  works with Alma Linux 9 build.

If you're just trying to get the new beta to work, doing the adjustments above should be a good workaround, depending on what your host is running and the preferred image (Alama/Rocky/Centos 9 vs. Rocky 8.6).  The real trick will be to make this all work in the Dockerfile but not break installations on older hosts, older container images and older versions of DVR.

As noted above, we now have a branch and a pull request (#34) to support 18.5.
If you're using one of the 18.5 betas, give this branch a shot and report back!
Thanks

Quick note--
On Ubuntu Linux running DaVinci Resolve 18.5 beta 1, some people are experiencing a font display issue.  This issue does not appear to be related to this project or running DVR in a container generally, but wanted to make people aware of it. The issue also does not seem to appear on other host distros like Pop_OS.
A Blackmagic Design developer chimed in on the thread linked above, saying "this is a known issue in 18.5 b1, and we're looking to get a fix in an upcoming release."

Fixed with bdff63a, and so far no complaints... so closing.


[BugFix] Fix typo for GlobalStateMgr

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Problem Summary(Required) ：
Fix typo for GlobalStateMgr log, and fix other typos by the way.

[FE PR Coverage Check]
:disappointed: fail : 1 / 7 (14.29%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/server/GlobalStateMgr.java
1
7
14.29%
[1790, 2152, 2156, 2160, 2164, 3154]


Using TS Paths as aliases

Current Behavior
I have an src folder which has index.ts in it and two subfolders plugins and utils, each with more TS files. index.ts imports most of these files from subfolders, but they are neither bundled nor independently compiled. Only their types are correctly output, however.
Expected behavior

Output a compiled JS file for each TS file imported by index.ts so it can be imported by the compiled index.js
OR
Bundle each originally imported file inside the index.js output file

Suggested solution(s)
Currently no idea.
Additional context

Your environment

Software
Version(s)

TSDX
0.11.0

TypeScript
3.7.2

Browser

npm/Yarn
6.11.3 / 1.19.1

Node
10.16.3

Operating System
MacOS

I figured out that this is only the case if imports within source files are made relative to paths option of tsconfig.json, such as src/*. If imports are relative to the importing file itself everything is alright.

this is something we need to figure out. i suspect its a rollup fix we need to do. if you get time, please be my guest to investigate

@sw-yx  @jlkiri
found solution: https://github.com/zerkalica/zerollup/tree/master/packages/ts-transform-paths#setup-for-rollup-plugin-typescript2
dirty fix:

forked, fixed, checked build (using @ambroseus/tsdx) : https://github.com/DCKit/dckit/blob/master/packages/%40dckit/ui/tsconfig.json

@jlkiri  while PR is under review, you can test fixed version yarn add @ambroseus/tsdx

@jlkiri  solution: https://github.com/jaredpalmer/tsdx/issues/379#issuecomment-568202209

@ambroseus Thanks, seems to be working now. I'm closing the issue.

Related to / duplicate of #91


Not working on Windows: Cannot read property 'IsAndroid' of undefined

Like iOS, the issue appears on Windows:
var RNSound = require('react-native').NativeModules.RNSound;
var IsAndroid = RNSound.IsAndroid;

How can I fix that? Thank you in advance!

Hi! If you're still having this problem, could you please post a link to a project that reproduces the problem, give information about your environment, and say what steps you have already tried?
This is the most common issue faced by react-native-sound users and it would be good to add documentation listing the possible resolutions. A pull request would be welcome; I've opened #592 to track that.


Update netlify-cli to allow postcss update

Description

Clears CVE-2023-44270
Related Issue(s)

https://github.com/FlowFuse/website/security/dependabot/4
Checklist

[x] I have read the contribution guidelines
[ ] I have considered the performance impact of these changes
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

Appreciate this, didn't know enough here to pick it up.


Calender bug

hey there polymer team there is a calender / datepicker bug we cannot change or goto a desired date.

@redchief - can you be more specific? Is this a native browser datepicker? Please add a code example if you can on codepen.io or ele.io.Thanks

Closing this issue due to age and the release of version 1 of Polymer - please feel free to re-open if this is incorrect.


reStructuredText: image references do not honour configuration for link validation

The following sample code
val transformer = Transformer
  .from(ReStructuredText)
  .to(HTML)
  .withConfigValue(LinkConfig(excludeFromValidation = Seq(Root)))
  .build
val input                       =
  """Some text
    |
    |.. image:: unresolved_Image.png
    |
    |followed by something else""".stripMargin

produces the following output:

Some text

followed by something else

With link validation turned on, the result is the same. Both outcomes are unexpected.
This issue is specific to the reStructuredText transformer, the Markdown parser behaves as expected.
Expected results
With link validation turned off, an image tag with the specified URL should be rendered.
With link validation turned on, the transformation should fail with an error message.

I just grabbed the 0.19.1 version (adding the "org.planet42" %% "laika-core" % "0.19.1" dependency) and I'm encountering a new issue with the rendering. Using the above transformer and input and this call:
def main(args: Array[String]){
    transformer.transform(input).map(print)
}

My output is

Some text

followed by something else

The image extension appears to have been transformed into .html at some point in the render.

Ah, that's unfortunately a separate issue that the original fix did not catch as I used a more narrow test case than the example you gave.
The new issue, including a temporary workaround until 0.19.2 is #408.
Just some feedback why you keep running into things like this: download stats show that 98% of users use Laika via its sbt plugin which transforms entire directories of inputs and has significantly different logic for both, link validation and path translation and therefore is not affected by those issues. Since most users are fine, these things did not get reported yet.
Your much simpler, standalone use case uses too much of the advanced logic internally that is intended for the directory use case. For example, when transforming a single string, link validation should actually be off by default, as the validation is futile in this case: the transformer does not even have the context for performing any validation. There will be further simplifications for standalone transformers in the next version.
Sorry for the inconvenience, at least your reports will help that those use cases receive some much needed polishing and fixes.

Thank you for the update. I imagine my use case isn't at all standard. I use Laika to read certain metadata from a RST template as well as rendering its content in isolation, rather than for building a complete document tree, so it's pretty esoteric.


  Allowed exit codes are: [0]

==> Wait completed after 34 minutes 29 seconds

==> Some builds didn't complete successfully and had errors:
--> arm-image.raspios_bullseye_armhf: Script exited with non-zero exit status: 100. Allowed exit codes are: [0]
--> arm-image.raspios_bullseye_arm64: Script exited with non-zero exit status: 100. Allowed exit codes are: [0]

==> Builds finished but no artifacts were created.

cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver <IP_ADDRESS>
options edns0 trust-ad
search ERRASED-PRIVATE

vagrant@ubuntu-focal:/vagrant$ ping deb.debian.org
PING debian.map.fastlydns.net (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=1 ttl=59 time=27.5 ms
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=2 ttl=59 time=28.3 ms
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=3 ttl=59 time=25.0 ms
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=4 ttl=59 time=27.2 ms
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=5 ttl=59 time=27.4 ms
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=6 ttl=59 time=27.2 ms
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=7 ttl=59 time=23.0 ms
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=8 ttl=59 time=26.7 ms
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=9 ttl=59 time=25.7 ms
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=10 ttl=59 time=395 ms
64 bytes from <IP_ADDRESS> (<IP_ADDRESS>): icmp_seq=11 ttl=59 time=28.9 ms
^C
--- debian.map.fastlydns.net ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 13631ms
rtt min/avg/max/mdev = 22.984/60.134/394.634/105.789 ms

A similar issue using /packer-plugin-arm-image was reported. @meringu provided one solution. I'll dig into it some more and report back.

Made the following changes and used provisioner shell to check /etc/resolv.conf and ping. The mounted Raspberry Pi is still not able to reach the internet.
vagrant@ubuntu-focal:/vagrant$ cat packer/sources.pkr.hcl
source "arm-image" "raspios_bullseye_armhf" {
  image_type      = "raspberrypi"
  chroot_mounts = [
        ["proc", "proc", "/proc"],
        ["sysfs", "sysfs", "/sys"],
        ["bind", "/dev", "/dev"],
        ["devpts", "devpts", "/dev/pts"],
        ["binfmt_misc", "binfmt_misc", "/proc/sys/fs/binfmt_misc"],
  ]
  additional_chroot_mounts = [
        ["bind", "/run/systemd", "/run/systemd"]
  ]
  iso_url         = "http://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2023-02-22/2023-02-21-raspios-bullseye-armhf-lite.img.xz"
  iso_checksum    = "sha256:c4582dd776e24066cf008f4ff389c38769a052c46ec63317635694dd767b86c9"
  output_filename = "images/rpi-cloud-init-raspios-bullseye-armhf.img"
}

source "arm-image" "raspios_bullseye_arm64" {
  image_type      = "raspberrypi"
  chroot_mounts = [
        ["proc", "proc", "/proc"],
        ["sysfs", "sysfs", "/sys"],
        ["bind", "/dev", "/dev"],
        ["devpts", "devpts", "/dev/pts"],
        ["binfmt_misc", "binfmt_misc", "/proc/sys/fs/binfmt_misc"],
  ]
  additional_chroot_mounts = [
        ["bind", "/run/systemd", "/run/systemd"]
  ]
  iso_url         = "http://downloads.raspberrypi.org/raspios_lite_arm64/images/raspios_lite_arm64-2023-02-22/2023-02-21-raspios-bullseye-arm64-lite.img.xz"
  iso_checksum    = "sha256:883eb0006c8841b7950ef69a7bf55f73c2250ecc15e6bf507f39f0d82fa2ea0a"
  output_filename = "images/rpi-cloud-init-raspios-bullseye-arm64.img"
  qemu_binary     = "qemu-aarch64-static"
}

vagrant@ubuntu-focal:/vagrant$ cat packer/build.pkr.hcl
build {
  sources = [
    "source.arm-image.raspios_bullseye_armhf",
    "source.arm-image.raspios_bullseye_arm64"
  ]

  provisioner "shell" {
    inline = [
      "ls -la /etc/resolv.conf",
      "cat /etc/resolv.conf",
      "ping -c 10 google.com",
      "ping -c 10 raspbian.raspberrypi.org"
    ]
  }

#  provisioner "shell" {
#    scripts = [
#      "scripts/install-cloud-init.sh"
#    ]
#  }
}
vagrant@ubuntu-focal:/vagrant$

vagrant@ubuntu-focal:/vagrant$ ./build.sh
arm-image.raspios_bullseye_armhf: output will be in this color.
arm-image.raspios_bullseye_arm64: output will be in this color.

==> arm-image.raspios_bullseye_armhf: Image type: raspberrypi
==> arm-image.raspios_bullseye_armhf: Retrieving Image
==> arm-image.raspios_bullseye_armhf: Trying http://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2023-02-22/2023-02-21-raspios-bullseye-armhf-lite.img.xz
==> arm-image.raspios_bullseye_armhf: Trying http://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2023-02-22/2023-02-21-raspios-bullseye-armhf-lite.img.xz?checksum=sha256%3Ac4582dd776e24066cf008f4ff389c38769a052c46ec63317635694dd767b86c9
==> arm-image.raspios_bullseye_armhf: http://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2023-02-22/2023-02-21-raspios-bullseye-armhf-lite.img.xz?checksum=sha256%3Ac4582dd776e24066cf008f4ff389c38769a052c46ec63317635694dd767b86c9 => /root/.cache/packer/82c68b23b869385a29bcac6c19fc197359301ae2.iso
==> arm-image.raspios_bullseye_armhf: Copying source image.
==> arm-image.raspios_bullseye_armhf: Image is a xz file.
    arm-image.raspios_bullseye_armhf: Speed:   15.00 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   26.13 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   30.71 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   17.21 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   13.12 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   11.75 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   10.27 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   13.74 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   11.30 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   12.81 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    9.47 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   11.52 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   12.61 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   11.01 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   14.35 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    6.96 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    5.54 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    8.47 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    9.35 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   11.09 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   12.16 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    9.61 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   15.63 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   10.88 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   12.54 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   21.46 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   15.18 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   14.40 MB/s
    arm-image.raspios_bullseye_armhf: mapping images/rpi-cloud-init-raspios-bullseye-armhf.img
==> arm-image.raspios_bullseye_armhf: losetup --show -f -P images/rpi-cloud-init-raspios-bullseye-armhf.img
==> arm-image.raspios_bullseye_armhf: partitions: [/dev/loop7p1 /dev/loop7p2]
    arm-image.raspios_bullseye_armhf: Mounting: /dev/loop7p2
    arm-image.raspios_bullseye_armhf: Mounting: /dev/loop7p1
==> arm-image.raspios_bullseye_armhf: Mounting additional paths within the chroot...
    arm-image.raspios_bullseye_armhf: Mounting: /proc
    arm-image.raspios_bullseye_armhf: Mounting: /sys
    arm-image.raspios_bullseye_armhf: Mounting: /dev
    arm-image.raspios_bullseye_armhf: Mounting: /dev/pts
    arm-image.raspios_bullseye_armhf: Mounting: /proc/sys/fs/binfmt_misc
    arm-image.raspios_bullseye_armhf: Mounting: /run/systemd
==> arm-image.raspios_bullseye_armhf: Installing qemu-user-static (/root/.cache/packer/qemu-arm-static) in the chroot
==> arm-image.raspios_bullseye_armhf: Registering /qemu-arm-static with binfmt_misc
==> arm-image.raspios_bullseye_armhf: Provisioning with shell script: /tmp/packer-shell1104781727
    arm-image.raspios_bullseye_armhf: -rw-r--r-- 1 root root 19 Feb 21  2023 /etc/resolv.conf
    arm-image.raspios_bullseye_armhf: nameserver <IP_ADDRESS>
==> arm-image.raspios_bullseye_armhf: /usr/bin/ping: google.com: Temporary failure in name resolution
==> arm-image.raspios_bullseye_armhf: fuser -k /tmp/armimg-684117644
Build 'arm-image.raspios_bullseye_armhf' errored after 2 minutes 44 seconds: Script exited with non-zero exit status: 2. Allowed exit codes are: [0]

Added additional lines to the provisioner shell in build.pkr.hcl to help diagnose:
build {
  sources = [
    "source.arm-image.raspios_bullseye_armhf",
    "source.arm-image.raspios_bullseye_arm64"
  ]

  provisioner "shell" {
    inline = [
      "ls -la /etc/resolv.conf",
      "cat /etc/resolv.conf",
      "date",
      "ip addr show",
      "ip route",
      "ping -c3 $(ip route | awk '/default/ {print $3}')",
      "ping -c 3 <IP_ADDRESS>",
      "ping -c 3 <IP_ADDRESS>",
      "ping -c 3 google.com",
      "ping -c 10 raspbian.raspberrypi.org"
    ]
  }

#  provisioner "shell" {
#    scripts = [
#      "scripts/install-cloud-init.sh"
#    ]
#  }
}

According to the output below, pinging the gateway <IP_ADDRESS> of Packer running Raspberry Pi image doesn't even work.
vagrant@ubuntu-focal:/vagrant$ ./build.sh
arm-image.raspios_bullseye_armhf: output will be in this color.
arm-image.raspios_bullseye_arm64: output will be in this color.

==> arm-image.raspios_bullseye_armhf: Image type: raspberrypi
==> arm-image.raspios_bullseye_armhf: Retrieving Image
==> arm-image.raspios_bullseye_armhf: Trying https://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2023-10-10/2023-10-10-raspios-bookworm-armhf-lite.img.xz
==> arm-image.raspios_bullseye_armhf: Trying https://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2023-10-10/2023-10-10-raspios-bookworm-armhf-lite.img.xz?checksum=sha256%3A1f8a646b375b198ef9f48c940889ac9f61744d1c1105b36c578313edbc81a339
==> arm-image.raspios_bullseye_armhf: https://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2023-10-10/2023-10-10-raspios-bookworm-armhf-lite.img.xz?checksum=sha256%3A1f8a646b375b198ef9f48c940889ac9f61744d1c1105b36c578313edbc81a339 => /root/.cache/packer/05243d95d9557442fae5647223b613438e48f048.iso
==> arm-image.raspios_bullseye_armhf: Copying source image.
==> arm-image.raspios_bullseye_armhf: Image is a xz file.
    arm-image.raspios_bullseye_armhf: Speed:   15.94 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   18.70 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   23.73 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   16.21 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   26.81 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   30.21 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   19.99 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   10.07 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   14.43 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   14.83 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   12.23 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   12.57 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   15.50 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   12.02 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   12.41 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   22.10 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   17.06 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   10.28 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    8.85 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   13.16 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   13.92 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   15.05 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   14.50 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   16.91 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   13.74 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   23.41 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   29.83 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   21.10 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   20.98 MB/s
    arm-image.raspios_bullseye_armhf: mapping images/rpi-cloud-init-raspios-bullseye-armhf.img
==> arm-image.raspios_bullseye_armhf: losetup --show -f -P images/rpi-cloud-init-raspios-bullseye-armhf.img
==> arm-image.raspios_bullseye_armhf: partitions: [/dev/loop7p1 /dev/loop7p2]
    arm-image.raspios_bullseye_armhf: Mounting: /dev/loop7p2
    arm-image.raspios_bullseye_armhf: Mounting: /dev/loop7p1
==> arm-image.raspios_bullseye_armhf: Mounting additional paths within the chroot...
    arm-image.raspios_bullseye_armhf: Mounting: /proc
    arm-image.raspios_bullseye_armhf: Mounting: /sys
    arm-image.raspios_bullseye_armhf: Mounting: /dev
    arm-image.raspios_bullseye_armhf: Mounting: /dev/pts
    arm-image.raspios_bullseye_armhf: Mounting: /proc/sys/fs/binfmt_misc
    arm-image.raspios_bullseye_armhf: Mounting: /run/systemd
==> arm-image.raspios_bullseye_armhf: Installing qemu-user-static (/root/.cache/packer/qemu-arm-static) in the chroot
==> arm-image.raspios_bullseye_armhf: Registering /qemu-arm-static with binfmt_misc
==> arm-image.raspios_bullseye_armhf: Provisioning with shell script: /tmp/packer-shell1712381433
    arm-image.raspios_bullseye_armhf: -rw-r--r-- 1 root root 19 Oct 10 01:24 /etc/resolv.conf
    arm-image.raspios_bullseye_armhf: nameserver <IP_ADDRESS>
    arm-image.raspios_bullseye_armhf: Tue Oct 31 02:38:07 GMT 2023
    arm-image.raspios_bullseye_armhf: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    arm-image.raspios_bullseye_armhf:     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    arm-image.raspios_bullseye_armhf:     inet <IP_ADDRESS>/8 scope host lo
    arm-image.raspios_bullseye_armhf:        valid_lft forever preferred_lft forever
    arm-image.raspios_bullseye_armhf:     inet6 ::1/128 scope host
    arm-image.raspios_bullseye_armhf:        valid_lft forever preferred_lft forever
    arm-image.raspios_bullseye_armhf: 2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    arm-image.raspios_bullseye_armhf:     link/ether 02:cd:6a:13:84:49 brd ff:ff:ff:ff:ff:ff
    arm-image.raspios_bullseye_armhf:     inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic enp0s3
    arm-image.raspios_bullseye_armhf:        valid_lft 76405sec preferred_lft 76405sec
    arm-image.raspios_bullseye_armhf:     inet6 fe80::cd:6aff:fe13:8449/64 scope link
    arm-image.raspios_bullseye_armhf:        valid_lft forever preferred_lft forever
    arm-image.raspios_bullseye_armhf: default via <IP_ADDRESS> dev enp0s3 proto dhcp src <IP_ADDRESS> metric 100
    arm-image.raspios_bullseye_armhf: <IP_ADDRESS>/24 dev enp0s3 proto kernel scope link src <IP_ADDRESS>
    arm-image.raspios_bullseye_armhf: <IP_ADDRESS> dev enp0s3 proto dhcp scope link src <IP_ADDRESS> metric 100
    arm-image.raspios_bullseye_armhf: PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
    arm-image.raspios_bullseye_armhf:
    arm-image.raspios_bullseye_armhf: --- <IP_ADDRESS> ping statistics ---
    arm-image.raspios_bullseye_armhf: 3 packets transmitted, 0 received, 100% packet loss, time 2056ms
    arm-image.raspios_bullseye_armhf:
==> arm-image.raspios_bullseye_armhf: fuser -k /tmp/armimg-2354826256
Build 'arm-image.raspios_bullseye_armhf' errored after 2 minutes 53 seconds: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]

I moved the following ping commands up to see if the Packer Raspberry Pi mounted image has access to the internet:
      "ping -c 3 <IP_ADDRESS>",
      "ping -c 3 <IP_ADDRESS>",

build {
  sources = [
    "source.arm-image.raspios_bullseye_armhf",
    "source.arm-image.raspios_bullseye_arm64"
  ]

  provisioner "shell" {
    inline = [
      "ls -la /etc/resolv.conf",
      "cat /etc/resolv.conf",
      "date",
      "ping -c 3 <IP_ADDRESS>",
      "ping -c 3 <IP_ADDRESS>",
      "ip addr show",
      "ip route",
      "ping -c3 $(ip route | awk '/default/ {print $3}')",
      "ping -c 3 google.com",
      "ping -c 10 raspbian.raspberrypi.org"
    ]
  }

#  provisioner "shell" {
#    scripts = [
#      "scripts/install-cloud-init.sh"
#    ]
#  }
}

Those ping commands could connect to the internet.
==> arm-image.raspios_bullseye_armhf: Image type: raspberrypi
==> arm-image.raspios_bullseye_armhf: Retrieving Image
==> arm-image.raspios_bullseye_armhf: Trying https://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2023-10-10/2023-10-10-raspios-bookworm-armhf-lite.img.xz
==> arm-image.raspios_bullseye_armhf: Trying https://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2023-10-10/2023-10-10-raspios-bookworm-armhf-lite.img.xz?checksum=sha256%3A1f8a646b375b198ef9f48c940889ac9f61744d1c1105b36c578313edbc81a339
==> arm-image.raspios_bullseye_armhf: https://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2023-10-10/2023-10-10-raspios-bookworm-armhf-lite.img.xz?checksum=sha256%3A1f8a646b375b198ef9f48c940889ac9f61744d1c1105b36c578313edbc81a339 => /root/.cache/packer/05243d95d9557442fae5647223b613438e48f048.iso
==> arm-image.raspios_bullseye_armhf: Copying source image.
==> arm-image.raspios_bullseye_armhf: Image is a xz file.
    arm-image.raspios_bullseye_armhf: Speed:   12.73 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   16.30 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   22.44 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   15.15 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   14.62 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   22.19 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   22.82 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   20.13 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   10.44 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    9.10 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   11.22 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    9.21 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    9.57 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    7.96 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    9.32 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   12.43 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   12.02 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    8.89 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    9.19 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   17.27 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   12.18 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   15.59 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    6.24 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    7.18 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    7.68 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    7.19 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    9.29 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   10.60 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   13.22 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    4.64 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    4.21 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    8.09 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   12.40 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   13.20 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   19.11 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   24.99 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   16.71 MB/s
    arm-image.raspios_bullseye_armhf: Speed:    9.77 MB/s
    arm-image.raspios_bullseye_armhf: Speed:   18.16 MB/s
    arm-image.raspios_bullseye_armhf: mapping images/rpi-cloud-init-raspios-bullseye-armhf.img
==> arm-image.raspios_bullseye_armhf: losetup --show -f -P images/rpi-cloud-init-raspios-bullseye-armhf.img
==> arm-image.raspios_bullseye_armhf: partitions: [/dev/loop5p1 /dev/loop5p2]
    arm-image.raspios_bullseye_armhf: Mounting: /dev/loop5p2
    arm-image.raspios_bullseye_armhf: Mounting: /dev/loop5p1
==> arm-image.raspios_bullseye_armhf: Mounting additional paths within the chroot...
    arm-image.raspios_bullseye_armhf: Mounting: /proc
    arm-image.raspios_bullseye_armhf: Mounting: /sys
    arm-image.raspios_bullseye_armhf: Mounting: /dev
    arm-image.raspios_bullseye_armhf: Mounting: /dev/pts
    arm-image.raspios_bullseye_armhf: Mounting: /proc/sys/fs/binfmt_misc
    arm-image.raspios_bullseye_armhf: Mounting: /run/systemd
==> arm-image.raspios_bullseye_armhf: Installing qemu-user-static (/root/.cache/packer/qemu-arm-static) in the chroot
==> arm-image.raspios_bullseye_armhf: Registering /qemu-arm-static with binfmt_misc
==> arm-image.raspios_bullseye_armhf: Provisioning with shell script: /tmp/packer-shell3272998983
    arm-image.raspios_bullseye_armhf: -rw-r--r-- 1 root root 19 Oct 10 01:24 /etc/resolv.conf
    arm-image.raspios_bullseye_armhf: nameserver <IP_ADDRESS>
    arm-image.raspios_bullseye_armhf: Tue Oct 31 04:25:28 GMT 2023
    arm-image.raspios_bullseye_armhf: PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
    arm-image.raspios_bullseye_armhf: 64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=63 time=4.24 ms
    arm-image.raspios_bullseye_armhf: 64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=63 time=7.68 ms
    arm-image.raspios_bullseye_armhf: 64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=63 time=3.58 ms
    arm-image.raspios_bullseye_armhf:
    arm-image.raspios_bullseye_armhf: --- <IP_ADDRESS> ping statistics ---
    arm-image.raspios_bullseye_armhf: 3 packets transmitted, 3 received, 0% packet loss, time 2009ms
    arm-image.raspios_bullseye_armhf: rtt min/avg/max/mdev = 3.581/5.164/7.677/1.796 ms
    arm-image.raspios_bullseye_armhf: PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
    arm-image.raspios_bullseye_armhf: 64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=119 time=24.1 ms
    arm-image.raspios_bullseye_armhf: 64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=119 time=39.8 ms
    arm-image.raspios_bullseye_armhf: 64 bytes from <IP_ADDRESS>: icmp_seq=3 ttl=119 time=27.4 ms
    arm-image.raspios_bullseye_armhf:
    arm-image.raspios_bullseye_armhf: --- <IP_ADDRESS> ping statistics ---
    arm-image.raspios_bullseye_armhf: 3 packets transmitted, 3 received, 0% packet loss, time 2055ms
    arm-image.raspios_bullseye_armhf: rtt min/avg/max/mdev = 24.113/30.449/39.798/6.748 ms
    arm-image.raspios_bullseye_armhf: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    arm-image.raspios_bullseye_armhf:     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    arm-image.raspios_bullseye_armhf:     inet <IP_ADDRESS>/8 scope host lo
    arm-image.raspios_bullseye_armhf:        valid_lft forever preferred_lft forever
    arm-image.raspios_bullseye_armhf:     inet6 ::1/128 scope host
    arm-image.raspios_bullseye_armhf:        valid_lft forever preferred_lft forever
    arm-image.raspios_bullseye_armhf: 2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    arm-image.raspios_bullseye_armhf:     link/ether 02:cd:6a:13:84:49 brd ff:ff:ff:ff:ff:ff
    arm-image.raspios_bullseye_armhf:     inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic enp0s3
    arm-image.raspios_bullseye_armhf:        valid_lft 83500sec preferred_lft 83500sec
    arm-image.raspios_bullseye_armhf:     inet6 fe80::cd:6aff:fe13:8449/64 scope link
    arm-image.raspios_bullseye_armhf:        valid_lft forever preferred_lft forever
    arm-image.raspios_bullseye_armhf: default via <IP_ADDRESS> dev enp0s3 proto dhcp src <IP_ADDRESS> metric 100
    arm-image.raspios_bullseye_armhf: <IP_ADDRESS>/24 dev enp0s3 proto kernel scope link src <IP_ADDRESS>
    arm-image.raspios_bullseye_armhf: <IP_ADDRESS> dev enp0s3 proto dhcp scope link src <IP_ADDRESS> metric 100
    arm-image.raspios_bullseye_armhf: PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
    arm-image.raspios_bullseye_armhf:
    arm-image.raspios_bullseye_armhf: --- <IP_ADDRESS> ping statistics ---
    arm-image.raspios_bullseye_armhf: 3 packets transmitted, 0 received, 100% packet loss, time 2032ms
    arm-image.raspios_bullseye_armhf:
==> arm-image.raspios_bullseye_armhf: fuser -k /tmp/armimg-1943496144
Build 'arm-image.raspios_bullseye_armhf' errored after 3 minutes 50 seconds: Script exited with non-zero exit status: 1. Allowed exit codes are: [0]

The failures occur while pinging the gateway. Why?
ping -c3 $(ip route | awk '/default/ {print $3}')

The inet IP <IP_ADDRESS> and gateway <IP_ADDRESS> listed for the Packer mounted Raspberry Pi is the same as the IP for the vagrant host:
debug2: shell request accepted on channel 0
Welcome to Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-166-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

  System information as of Tue Oct 31 04:38:34 UTC 2023

  System load:  0.0                Processes:               119
  Usage of /:   10.2% of 38.70GB   Users logged in:         0
  Memory usage: 18%                IPv4 address for enp0s3: <IP_ADDRESS>
  Swap usage:   0%

 * Strictly confined Kubernetes makes edge and IoT secure. Learn how MicroK8s
   just raised the bar for easy, resilient and secure K8s cluster deployment.

   https://ubuntu.com/engage/secure-kubernetes-at-the-edge

Expanded Security Maintenance for Applications is not enabled.

0 updates can be applied immediately.

Enable ESM Apps to receive additional future security updates.
See https://ubuntu.com/esm or run: sudo pro status

New release '22.04.3 LTS' available.
Run 'do-release-upgrade' to upgrade to it.

Last login: Tue Oct 31 03:55:01 2023 from <IP_ADDRESS>
vagrant@ubuntu-focal:~$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 02:cd:6a:13:84:49 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic enp0s3
       valid_lft 82702sec preferred_lft 82702sec
    inet6 fe80::cd:6aff:fe13:8449/64 scope link
       valid_lft forever preferred_lft forever
vagrant@ubuntu-focal:~$ ip route
default via <IP_ADDRESS> dev enp0s3 proto dhcp src <IP_ADDRESS> metric 100
<IP_ADDRESS>/24 dev enp0s3 proto kernel scope link src <IP_ADDRESS>
<IP_ADDRESS> dev enp0s3 proto dhcp scope link src <IP_ADDRESS> metric 100
vagrant@ubuntu-focal:~$ ping -c3 $(ip route | awk '/default/ {print $3}')
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.

--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2027ms

As shown above, pinging the gateway from the vagrant host doesn't work either.
Pinging google.com from the vagrant host works:
vagrant@ubuntu-focal:~$ ping -c 3 google.com
PING google.com (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from sea30s13-in-f14.1e100.net (<IP_ADDRESS>): icmp_seq=1 ttl=119 time=32.5 ms
64 bytes from sea30s13-in-f14.1e100.net (<IP_ADDRESS>): icmp_seq=2 ttl=119 time=25.9 ms
64 bytes from sea30s13-in-f14.1e100.net (<IP_ADDRESS>): icmp_seq=3 ttl=119 time=31.5 ms

--- google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 3066ms
rtt min/avg/max/mdev = 25.875/29.980/32.521/2.930 ms

Turning off Private Internet Access VPN on Windows 11 fixed the issue and the Vagrant mounted Raspberry Pi images were able to download their required software packages. Ironically, I posted this very same issue a while back for this project!
For those arriving here with the same issue in the future, I also tried turning off Windows Defender firewall on the host computer. That didn't help.
Why pinging the gateway cited above doesn't work is confusing still.


[ToC horizontal] design specs

Create specs for the horizontal table of contents
Design exploration – #10323

[ ] Review exploration with Jeannie / Olivia / Rich
[ ] Spec chosen option
[ ] Spacing spec
[ ] Color themes
[ ] Include @sm and @md annotation (revisit vertical, too)
[ ] Interaction states
[ ] Breakpoint specs

Jeannie/Olivia review 06/20/23
The vertical indicator is the favorite styling to explore more deeply. Explore additional options:

[ ] 16px vs 24px horizontal padding for each side

[ ] 8px vs 6px distance from indicator to label

[ ] Explore hover and motion change (should be simpler than motion explo)

[ ] Shadow vs border on horizontal ToC.

[ ] Inset vs full-width (including beyond @max)

[ ] Circle back with Gower on scroll indicator

Gower comment to horizontal scrolling:

Hi Rich, so there are a few considerations:
What visual affordances are there for a pointer user (both mouse and touch) to understand there is additional content
What are the mechanisms to activate/navigate to the additional TOCS items via pointer users? A caution here is that Pointer Gestures requires there to be a method of use other than directional gestures for touch operation. Since you will likely need that for mouse users anyway, it’s not necessarily net new. Note too that Dragging Movements, upcoming with WCAG 2.2 also places constraints on this. I believe you have this solved in mobile by offering the TOC as a dropdown menu on smaller screens
What are the visual affordances and operators for keyboard users?
As I mentioned, I’d be inclined to think of a carousel-like offering to solve this. You can use the fade to indicate truncation, and then when the user hovers or puts focus on it, there are arrows or something that can get tapped (by mouse) and server as indicators to a keyboard user that there are more items. Note that I don’t think there’s a need for an additional tab stop for these arrows. The arrow cue would be sufficient to indicate to the user they left/right arrow to reposition.
Like a tablist, I’d be inclined to put a focus indicator around the whole thing to clarify the interaction.
Also like a tablist, you need to think about whether the TOC updates the doc position as the user moves between items in the TOC, or when the items are activated

Design crit 06/22/23

Use 16px left and right padding instead of 24px. We normally use 16px padding, and bumping it up here would put it out of sync with similar components.
Use the 24px height on the selected state for more emphasis, instead of 20px / text height
We'll use the border variant instead of drop shadow, bringing this in line with other sticky elements like the Masthead
Extend the full width above max, also bringing in line with Masthead.
Hover can either use the current hover as the safe option, or hint with $border-subtle-01 as the vertical indicator.


PWD only accesible from localhost

I've installed PWD.
It's runnig an accesible from localhost, but I can't access it from others hosts (or the same) using IP address.
(any special configuration in dnsmasq.conf required?)
503 Service Unavailable No server is available to handle this request.

you have to change the haproxy.conf to match the host you want to use.

Btw, one thing is to run it locally and other is to deploy it for other to use. Check https://github.com/play-with-docker/play-with-docker/wiki/Deploying-PWD-in-your-own-infrastructure


Could you add login script and code snippet?

I hope ConnectBot add some new feature:
ConnectBot will automatically run a code snippet after successful login when connecting to a remote host , and could run the code snippet by manually from menu bar.

There is a "post-login automation" section at the end of each host's settings. However, there is not a way to run the command on demand.

I would consider code snippets useful only if you could create many of them. Then, you could choose one from a menu to run for the current connection.


Kenn/add MinReadySeconds to HumioUpdateStrategy

I would like some feedback on how necessary it is to add tests with this PR.
If tests are necessary (I assume they are) and can wait, then I will make another PR containing an automated test for this functionality. In that regard I may need some advice on how best to formulate the test.
Edit: This has been tested a ton locally in kind, and has also been tested twice on ops.humio.com.

@kenn-humio - I created a PR in this repo so we can run the tests. One of the checks is failing here https://github.com/humio/humio-operator/runs/7155133165?check_suite_focus=true.


Maximize editor by double clicking the tab

This is a feature request to implement maximize toggle for a single editor tab. The idea is to support maximizing the editor area to cover the whole VS Code window when the table is double clicked and the previous state will be restored by double clicking the tab again.
I think it would be pretty good to copy the same logic that Eclipse has: whenever an editor tab is double clicked, the editor area covers the whole window and the tab bar is at the top allowing one to switch to other tabs within that editor area. Double  clicking any tab will restore the normal layout. In case of Eclipse, this also works for all sidebars and views but the most important part is the main editor area.
Note that this differs from the Zen mode by still honoring the window size – it simply maximizes the use of the whole window for the editor area only.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Prevent detached DOM nodes in nested component

Fixes #1625.
I would love to include a test, but I couldn't figure out a way to determine the number of detached DOM nodes/or get a heap snapshot from JS.

Test used: http://jsfiddle.net/akagomez/ajdj2nu2/

Can we close this one?

When I spoke with @justinbmeyer yesterday evening, he suggested these were not likely the solution to the core issue. For now, it's likely a good enough fix until Justin has the time to investigate further.

@akagomez thanks for reporting this. It's a good fix for someone who needs a quick fix, but not good enough to merge into master.

@justinbmeyer @daffl - is there an ETA on something that would be considered "good enough?" I'd rather not have to fork CanJS to fix such a detrimental bug.
Also this fix only works with Stache - Mustache still has a problem, will that be fixed as well?

Closed via #1631


[internal-regex] Regular expression literal = every package is marked internal

In ES6 world, I'm used to writing regular expressions as literals. So I did this in my .eslintrc.cjs:
module.exports = {
  settings: {
    "import/internal-regex": /^@scope\//,
  },
};

This marked every package as internal! Oops.
module.exports = {
  settings: {
    "import/internal-regex": "^@scope/",
  },
};

This worked as expected.
Probably a doc note at most, but wanted to let you know anyway, as it was a surprise that took a little while to figure out.

A doc note would be fine to add. It'd also be fine to throw on a non-undefined non-string being here.
What I'd rather have done (but this predates me) is make this a glob, since regexes in eslint config is a disaster, and a CVE magnet.


Typed Dictionaries can allow different typed keys/values when using operator[]

Tested versions
Latest master v4.4.dev.custom_build [21249950d]
System information
Windows 10
Issue description
Adding to a typed dictionary using operator[] allows adding keys/values of different types, if the types aren't known until run time, or if the typed dictionary is passed into a function that takes an untyped dictionary.  In both cases, using get_or_add catches the difference and gives an error.
Steps to reproduce
Create a new project, and add code below to main scene:
func _ready():
	var dictionary : Dictionary[Node, Node] = { }
	# dictionary["test1"] = 1 # Gives error in editor
	# dictionary.get_or_add(get_key(), get_value()) # Type check error
	dictionary[get_key()] = get_value()
	_test_dictionary_func(dictionary)
	print(dictionary)

func _test_dictionary_func(d : Dictionary):
	# d.get_or_add("test2", 2) # Type check error
	d["test2"] = 2

func get_key():
	return "test1"

func get_value():
	return 1

This prints { "test1": 1, "test2": 2 } without giving any errors
Minimal reproduction project (MRP)
N/A

As GDScript is a gradually typed language, is there a need to implement this type inference? Would we expect this dictionary's type to not be cast to the untyped dictionary? As get_or_add verifies types during runtime, it might make more sense to prefer that when potentially using mixed types. I'm all for increased type inference accuracy though.

CC @Repiteo


Fix pydantic validation and allow inplace update of evented models.

Description
This PR is - hopefully - the final iteration of #4804, #4609, and #4597 (and all the stuff before about Dims and nested validation :P).
Together with @tlambert03, we chipped away at the various idiosyncrasies and inconsistencies in pydantic validation, and formed a separate package over at https://gitub.com/brisvag/extra-pydantic that monkey-patches the BaseModel and ModelField from pydantic. Issues that this package solves mostly stem from the use of generics:

inconsistent validation of parametrized generics (elements of collections might or might not be validated)
inconsistent coercion of parametrized generics (sometimes you get the type you asked for, sometimes just the "base" collection type, sometimes depending on whether they are parametrized)
not all "non-arbitrary types" are coerced correctly (dataclasses, protocol subclasses)

Ultimately, for us this means that we can start using our EventedList and friends in EventedModels how they were intended, and get the thing we asked for. Same goes for things like Color.

A second part of this PR is the inplace-mutability of Evented objects (models and collections); this goes hand in hand with the above, because using EventedList or EventedModel as model fields is currently clunky, because we have to enforce allow_mutation = False, otherwise all the event sources change and event callbacks get lost in the aether.
With these changes (almost entirely taken from #4597) we can use a special cased allow_mutation = 2 in our EventedModel, which will ensure the the contents of any EventedMutable field are replaced, rather than the object itself.
PS: unfortunately, I did not manage to split these two parts in separate PRs due to their tight interplay when it comes to StyleEncodings and similar objects, which need to be validated, coerced, but also be replaceable in some cases. It might be possible to split the two with some work, but I figured I would open this PR in the meantime to make sure it's worth the work.

Type of change

[x] Bug-fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change
[ ] example: I check if my changes works with both PySide and PyQt backends
as there are small differences between the two Qt bindings.

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

I think this might be officially dead, seeing how pydantic is moving along with v2 and the changes are quite drastic to the backend. It's probably best to wait things to settle on that side, at this point.


Feature/mediaplayer test

Codecov Report

Merging #17 into develop will increase coverage by 17.25%.
The diff coverage is 96.96%.

@@             Coverage Diff              @@
##           develop      #17       +/-   ##
============================================
+ Coverage    28.03%   45.29%   +17.25%
============================================
  Files          192      194        +2
  Lines        10119    10152       +33
============================================
+ Hits          2837     4598     +1761
+ Misses        7282     5554     -1728

Impacted Files
Coverage Δ

mediaPlayer/MediaPlayer.cpp
37.66% <ø> (+37.66%)
:arrow_up:

mediaPlayer/tests/mediaPlayerUnitTest.cpp
100% <100%> (ø)

mediaPlayer/tests/mediaPlayerTest.cpp
93.33% <93.33%> (ø)

framework/tests/dataSource/ipList.h
0% <0%> (-100%)
:arrow_down:

framework/tests/demuxer/demuxerUnitTest.cpp
0% <0%> (-100%)
:arrow_down:

framework/tests/demuxer/demuxerUtils.cpp
0% <0%> (-98.64%)
:arrow_down:

framework/tests/render/renderTest.cpp
0% <0%> (-95.24%)
:arrow_down:

framework/tests/decoder/decoderUnitTest.cpp
0% <0%> (-93.34%)
:arrow_down:

framework/tests/dataSource/dataSourceUnitTest.cpp
0% <0%> (-93.28%)
:arrow_down:

framework/data_source/ffmpeg_data_source.cpp
9.37% <0%> (-65.63%)
:arrow_down:

... and 76 more

Continue to review full report at Codecov.

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


Decompiler:  Ignore type after NULL check

Describe the bug
When malloc or use a  getter function for assigning a pointer you would do a NULL check on the pointer followed by error handling.
If its NULL and the compiler knows  its NULL at that point it might use that register to NULL other things.
struct foo *x;
struct bar *y;

x =  get_foo();
if ((struct foo *)0 == x) {
    return;
}
y = get_bar();
if ((struct bar *)0 == y) {
    free(x);
    //  This is just "x = NULL", but decompiler will  use compiler's optimization and
    //  use the register that currently holds the value for "y", which is  known to be NULL
    x = (struct foo *)y;
}
// do something with x  and y

Don't know if this is really a bug or just a readability thing that can be ignored (so maybe just a feature request).
Would this  put the decompiler into a weird state where types conflict?
Could a NULL variable in that scope lose it's type information and just be a literal?
Environment (please complete the following information):

OS: win10
Java Version: 11.0.10
Ghidra Version: 10.1.4
Ghidra Origin: official

From the code browser, Edit->Tool Options...->Decompiler->Display->Print 'NULL' for null pointers (near the bottom of the list)
I think you will get the effect you want if you check that box.  If not let me know.

From the code browser, Edit->Tool Options...->Decompiler->Display->Print 'NULL' for null pointers (near the bottom of the list)
I think you will get the effect you want if you check that box. If not let me know.

Even with this checked, NULL doesn't appear when using https://github.com/NationalSecurityAgency/ghidra/issues/4508 to fix mixed size pointers.

@ghidracadabra  sorry for the delay, was AFK all last week
with my example, I see
struct foo *x;
struct bar *y;

x =  get_foo();
if (x == NULL) {
    return;
}
y = get_bar();
if (y == NULL) {
    free(x);
    //  This is just "x = NULL", but decompiler will  use compiler's optimization and
    //  use the register that currently holds the value for "y", which is  known to be NULL
    x = (struct foo *)y;
}
// do something with x  and y

 x = (struct foo *)y;  remains unchanged it looks like.  My concern is if x / get_foo were un-typed, and y / get_bar was typed, this assignment would make x of type bar and might cause false positive that are more difficult to track in larger functions where a user might use this information while setting prototypes or struct field types

still seeing in 10.3
struct foo *x;
struct bar *y;

x = get_foo();
if (!x) {
    return NULL;
}
y = find_bar();
if (!y) {
    y = get_bar();
    if (y) {
        if (init_bar(y)) goto succeed;
        free(x);
        x = y;
    }
    free(x);
    x = NULL;
} else {
succeed:
    // tries to initialize y, but gets cast x
}
return x;

Thanks for letting us know; I'll take a look.

I'm not sure I understand this example.  Where is the offending cast inserted?  It looks like the x = y assignment happens at a point where both x and y are non-null, so this might be a different issue.

Yeah, you're right, it's not the same as the original.  I'll create a new issue if I come across again and it's more of a type mismatch than known null/const


Fixes #27095 : Removing registrytoken field from doc as it is depreca…

- What I did
This PR fixes #27095
Removed registrytoken field from doc as it is deprecated by identitytoken field
Signed-off-by: milindchawre<EMAIL_ADDRESS>

@thaJeztah: I believe both identitytoken and registrytoken are handled by the latest versions, but we prefer people to use registrytoken, because identitytoken was a hack that was added for a very specific use case and is problematic.
Technically perhaps we should document both.
cc @dmcgowan

@aaronlehmann I think you meant to say the registrytoken is the hack. I don't think we should document both since the registrytoken is deprecated and should not be used. Also there is no defined use for the registrytoken, no way for the user to set/update it, and documenting it as something that can be used if you MITM your client to add it will just be more confusing. Guess from my perspective adding documentation would involve adding a confusing explanation and mentioning it is deprecated.
LGTM

I think you meant to say the registrytoken is the hack.

Yes, of course.

Thanks @milindchawre, could you squash your commits so that there's only one commit in this PR? LGTM after that
If you need help with "squashing", theres some information in our contributors guide; https://docs.docker.com/opensource/workflow/work-issue/#/pull-and-rebase-frequently

@thaJeztah Commits are squashed!


Gear menus aren't working properly

When you click the gear icons the menu only appears sometimes.

In my experience it isn't "sometimes," but "never." The gear icon highlights, and nothing else happens.

Created a pull request at #427 which should fix this

Fixed in v3.3.2


[WFLY-10873]: Duplicated httpcomponent jars

Using org.apache.httpcomponents.core module to avoid duplication of http-components jars.

Jira: https://issues.jboss.org/browse/WFLY-10873
https://issues.jboss.org/browse/WFLY-10622

@ehsavoie the same test appears to fail in multiple configs


Changelog for 0.2.0

0.2.0-alpha.1 (next release)
To test this update before it’s official, run
create-react-app my-app --scripts-version 0.2.0-alpha.1

Don’t forget the --scripts-version!
Build Dependency (react-scripts)

You can now enable deployment to GitHub Pages by adding homepage field to package.json (@dhruska in #94)
Development server now runs on <IP_ADDRESS> and works with VirtualBox (@JWo1F in #128)
Cloud9 and Nitrous online IDEs are now supported (@gaearon in 2fe84e)
When 3000 port is taken, we offer to use another port (@chocnut in #101, 2edf21)
You can now import CSS files from npm modules (@glennreyes in #105, @breaddevil in #178)
fetch and Promise polyfills are now always included (@gaearon in #235)
Regenerator runtime is now included if you use ES6 generators (@gaearon in #238)
Generated project now contains .gitignore (@npverni in #79, @chibicode in #112)
A stylistic lint rule about method naming has been removed (@mxstbr in #152)
A few unobtrusive accessibility lint rules have been added (@evcohen in #175)
A .babelrc in parent directory no longer causes an error (@alexzherdev in #236)
Files with .json extension are now discovered (@gaearon in a11d6a)
Bug fixes from transitive dependencies are included (#126)

Global CLI (create-react-app)

Generated ESLint configuration is now compatible with IDEs with npm 3 (@keyanzhang in #149)
It enforces that you have Node >= 4 (@conorhastings in #88)
It handles --version flag correctly (@mxstbr in #152)

Migrating from 0.1.0 to 0.2.0-alpha.1
Note: this is an unstable version. Things might be broken.
You may optionally update the global command (it’s not required):
npm install -g<EMAIL_ADDRESS>
Inside any created project that has not been ejected, run:
npm install --save-dev --save-exact<EMAIL_ADDRESS>
You may need to fix a few lint warnings about missing <img alt> tag, but everything else should work out of the box.
If you intend to deploy your site to GitHub Pages, you may now add homepage field to package.json.
If you had issues with integrating editor linter plugins, add
  "eslintConfig": {
    "extends": "./node_modules/react-scripts/config/eslint.js"
  }

to your project’s package.json. If you have already run eject, the path would be ./config/eslint.js instead.

Generated ESLint configuration is now compatible with IDEs with npm 3 (@keyanzhang in #149)

This shouldn't be in the global cli section. This change will be picked up with the new release even if you don't update the global one

Ah you're right, can you fix this please? I keep forgetting about the split :P

Hopefully from now on we're never going to change the global cli, ever ;)