node-gyp rebuild fails

Running npm install on this project https://github.com/meatspaces/meatspace-chat results in the following error, was told to notify author of this package. I first installed zeromq using these instructions
sudo apt-get install libtool autoconf automake uuid-dev build-essential
cd ~
wget http://download.zeromq.org/zeromq-4.0.3.tar.gz
tar zxvf zeromq-4.0.3.tar.gz && cd zeromq-4.0.3
./configure
make && make install
Error
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:789:12)
gyp ERR! System Linux 3.8.0-29-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/michael/meatspace-chat/node_modules/zmq
gyp ERR! node -v v0.10.24
gyp ERR! node-gyp -v v0.12.1
gyp ERR! not ok
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is most likely a problem with the zmq package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls zmq
npm ERR! There is likely additional logging output above.

Hi is there a solution now?
I tried to install zmq on windows 10 with up to date node.js and npm
But there occur this error:
C:\Users\xxx\AppData\Roaming\npm\node_modules\zmq>if not defined npm_config_node_gyp (node "C:\Users\xxx\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "" rebuild )
Traceback (most recent call last):
File "C:\Users\xxx\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\gyp\gyp_main.py", line 13, in
import gyp
File "C:\Users\xxx\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp_init_.py", line 8, in
import gyp.input
File "C:\Users\xxx\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\gyp\pylib\gyp\input.py", line 891
except ImportError as e:
^
SyntaxError: invalid syntax
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (C:\Users\xxx\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\configure.js:308:16)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12)
gyp ERR! System Windows_NT 10.0.14393
gyp ERR! command "C:\Program Files (x86)\nodejs\node.exe" "C:\Users\xxx\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Users\xxx\AppData\Roaming\npm\node_modules\zmq
gyp ERR! node -v v6.10.1
gyp ERR! node-gyp -v v3.5.0
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the zmq package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs zmq
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls zmq
npm ERR! There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:

@ChangeTheCode You can try zeromq.js which has the same API as zmq but ships with prebuilt binaries for Windows, Linux and OS X for easy installation.

Thank you very much.  https://github.com/zeromq/zeromq.js works !!


Add release documentation page

This moves the discussion into actual documentation from https://docs.google.com/document/d/1RQgGTwAgkdtZu7DelMwqlmDqmpSH1e8Y6IcL3fD2WQI/edit#
I chose the term release shepherd (as I've heard this term being used elsewhere), I don't think we were set on a term but I'm happy to use whatever if anyone has other suggestions.
And the how to cut an individual release page was taken from here: https://github.com/prometheus/prometheus/wiki/HOWTO-cut-a-new-release (this wiki page can be deleted once this is merged as per discussion on the -team call from yesterday)
Let me know what you think.
@gouthamve @brian-brazil @juliusv

This appears to supersede https://github.com/prometheus/prometheus/wiki/HOWTO-cut-a-new-release . Please delete the wiki page once this is in. (Or delete it immediately if it is already outdated.)

Ping @brancz

We should also make a release in prometheus/tsdb (cut branch and tag) as that'll make patches easy rather than vendoring in master with potential features too.
And ideally, this should be done for prometheus/common also.

Sorry for not having followed up on this, it’s on my list for this week! :)

Sorry for taking so long, could you have another look?

I tried moving the nav item into the prometheus tab, without any success. If you feel this is important please make a suggestion on how to do this, because I'm out of ideas, otherwise let's go ahead and merge this and try at a later point.

Super-seeded by https://github.com/prometheus/prometheus/pull/4829


Add "Split Button" type of Header Button

Feature
Current header buttons are either dropdown buttons (click on the full button and get the dropdown) or simple buttons (click on the button and do something.)
In the header, we would need the "main" part of the button to do something (For example, bring me to the currently "active" project and do something with it) and the drop down part to select a different project and do likely the same thing.
Current connect implementation does this but is rather tricky to click only on the carret image, which does a different thing than the rest of the button.
Not 100% sure of how it should look, but the split button might be a starting point, where the 2 different click targets  highlights separately, I dont know if the current | in the middle of the component would do well
Examples
Basic

Main hover

Drop down

(Examples made by pasting header button code in split button "left" button, so styling is not great)

We already have a split menu button component.  You might be able to use the CSS from .iui-button-split-menu and .iui-borderless to help with this.
What I was originally imagining was something like this:

But I think that looks awful. 🤮 What if we try something more custom just for the header buttons?  How about something like this (pay attention to where the cursor is for hover interactions):

For the expanding arrow split button portion, we can make something like the red area be the touch target area.  The image below is a quick Photoshop hack job, so we'd want the circle & arrow icon to be centered within the touch target area.


Navigator doesn't work with the default AWX EE

ISSUE TYPE

Bug Report

SUMMARY
Running Navigator with any playbook against the AWS default EE results in permission denied errors.
ansible-navigator run job1.yml -t jobtagtest2 --ee true --eei quay.io/ansible/awx-ee:latest

ANSIBLE-NAVIGATOR VERSION

ansible-navigator 2.1.0

CONFIGURATION
N/A
LOG FILE
/usr/local/lib/python3.8/site-packages/paramiko/transport.py:236: CryptographyDeprecationWarning: Blowfish has been deprecated
  "class": algorithms.Blowfish,
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: error in 'jsonfile' cache plugin while trying to create cache dir
/runner/artifacts/c0df7b9f-4331-4c65-bccf-6f44dc1006a8/fact_cache : b"[Errno
13] Permission denied: '/runner/artifacts'"
[WARNING]: provided hosts list is empty, only localhost is available. Note that
the implicit localhost does not match 'all'
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/ansible/executor/task_queue_manager.py", line 450, in send_callback
    method(*new_args, **kwargs)
  File "/home/runner/.ansible/plugins/callback/awx_display.py", line 455, in v2_playbook_on_start
    with self.capture_event_data('playbook_on_start', **event_data):
  File "/usr/lib64/python3.8/contextlib.py", line 113, in __enter__
    return next(self.gen)
  File "/home/runner/.ansible/plugins/callback/awx_display.py", line 374, in capture_event_data
    event_context.dump_begin(sys.stdout)
  File "/home/runner/.ansible/plugins/callback/awx_display.py", line 239, in dump_begin
    self.cache.set(":1:ev-{}".format(begin_dict['uuid']), begin_dict)
  File "/home/runner/.ansible/plugins/callback/awx_display.py", line 111, in set
    os.mkdir(os.path.join(self.private_data_dir, 'job_events'), 0o700)
PermissionError: [Errno 13] Permission denied: '/runner/artifacts/c0df7b9f-4331-4c65-bccf-6f44dc1006a8/job_events'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/bin/ansible-playbook", line 128, in <module>
    exit_code = cli.run()
  File "/usr/local/lib/python3.8/site-packages/ansible/cli/playbook.py", line 137, in run
    results = pbex.run()
  File "/usr/local/lib/python3.8/site-packages/ansible/executor/playbook_executor.py", line 120, in run
    self._tqm.send_callback('v2_playbook_on_start', pb)
  File "/usr/local/lib/python3.8/site-packages/ansible/utils/lock.py", line 41, in inner
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/ansible/executor/task_queue_manager.py", line 453, in send_callback
    display.warning(u"Failure using method (%s) in callback plugin (%s): %s" % (to_text(method_name), to_text(callback_plugin), to_text(e)))
  File "/home/runner/.ansible/plugins/callback/awx_display.py", line 256, in wrapper
    return f(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/ansible/utils/display.py", line 409, in warning
    self.display(new_msg, color=C.COLOR_WARN, stderr=True)
  File "/home/runner/.ansible/plugins/callback/awx_display.py", line 304, in wrapper
    event_context.dump_begin(fileobj)
  File "/home/runner/.ansible/plugins/callback/awx_display.py", line 239, in dump_begin
    self.cache.set(":1:ev-{}".format(begin_dict['uuid']), begin_dict)
  File "/home/runner/.ansible/plugins/callback/awx_display.py", line 111, in set
    os.mkdir(os.path.join(self.private_data_dir, 'job_events'), 0o700)
PermissionError: [Errno 13] Permission denied: '/runner/artifacts/c0df7b9f-4331-4c65-bccf-6f44dc1006a8/job_events'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/bin/ansible-playbook", line 156, in <module>
    display.error("Unexpected Exception, this is probably a bug: %s" % to_text(e), wrap_text=False)
  File "/home/runner/.ansible/plugins/callback/awx_display.py", line 256, in wrapper
    return f(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/ansible/utils/display.py", line 464, in error
    self.display(new_msg, color=C.COLOR_ERROR, stderr=True)
  File "/home/runner/.ansible/plugins/callback/awx_display.py", line 304, in wrapper
    event_context.dump_begin(fileobj)
  File "/home/runner/.ansible/plugins/callback/awx_display.py", line 239, in dump_begin
    self.cache.set(":1:ev-{}".format(begin_dict['uuid']), begin_dict)
  File "/home/runner/.ansible/plugins/callback/awx_display.py", line 111, in set
    os.mkdir(os.path.join(self.private_data_dir, 'job_events'), 0o700)
PermissionError: [Errno 13] Permission denied: '/runner/artifacts/c0df7b9f-4331-4c65-bccf-6f44dc1006a8/job_events'

STEPS TO REPRODUCE

ansible-navigator run job1.yml -t jobtagtest2 --ee true --eei quay.io/ansible/awx-ee:latest

EXPECTED RESULTS

the job to run
ACTUAL RESULTS

above permission error

A hello world playbook works in an Ubuntu VM but macOS is giving this error.

I submitted #1276 as I am narrowing this problem down and it may have to do with not using Docker Desktop.

Closing as the real bug is #1276

I can reproduce this issue on linux. I think it's because the awx-ee  has USER 1000
https://github.com/ansible/awx-ee/blob/devel/Containerfile#L91
Why can't EEs be executed rootless with ansible-navigator? ansible-navigator seems to mount /runner/artifacts not allowing rootless:
Showing mounts by adding the mount command to the entrypoint reveals:
tmpfs on /runner/artifacts type tmpfs (rw,noatime,inode64)
IIUC, the way /runner/artifacts is mounted prevents the user to write to it?


controlsd: lagged for 100ms

https://connect.comma.ai/9b25e8c1484a1b67/1682063616542/1682063673396
https://connect.comma.ai/297b4b460f361603/1688795349008/1688795363644

c2585539cc5ebcb3|2023-07-29--07-37-37

https://connect.comma.ai/e886087f430e7fe7/1691516170616/1691516194613

more cases looking at random 50k segments last 30 days on release, not exactly 100ms every time:
segment, ms, platform, devicetype
c2585539cc5ebcb3|2023-07-29--07-37-37--101 72.1630859375 TOYOTA COROLLA TSS2 2019 8
06362e6a7f0b400b|2023-08-06--21-08-29--32 65.93787384033203 TOYOTA CAMRY 2018 7
25593b1a5f760b07|2023-07-13--16-01-55--13 81.96173095703125 TOYOTA HIGHLANDER 2020 8
b576d2ff8a193b4a|2023-07-26--23-03-30--3 89.41193389892578 KIA NIRO EV 2020 7
20665f9a424ada41|2023-07-27--17-09-07--2 57.68474864959717 CHRYSLER PACIFICA 2020 7

On Sunnypilot I have also experienced this and tried to debug it with no success. I saw it with carState, not sure if that helps. I believe it is related to cereal but I have a big knowledge gap still with OP.

Oh, something else I also noticed is that using network via cellular produced more cumLags than using network on Wifi. Using no network connectivity at all yielded the lowest cumLags. I feel there might be a correlation somewhere.

I have another user who also has been experiencing controls lagging, we asked him to install stock OP to rule it out and he still has a significantly high cumlags. He has a C3 device and a Kia EV6 (canfd)
a12a00d7b630927b|2023-10-25--00-05-38 lag reaches 450ms on this route

a12a00d7b630927b|2023-10-24--10-57-19 morning route about 260 ms

a12a00d7b630927b|2023-10-24--17-27-26 evening route about 860ms at the end

Branch source: https://github.com/commaai/openpilot/pull/27392
Device: C3X
Route ID: 696748e0ac8082fb|2023-10-24--10-45-04

Another user also experienced this issue. This is stock openpilot + 2023 Hyundai Palisade HDA2 car port changes. Seems to be related to pings with Athena. Any information we can provide for troubleshooting?

https://github.com/commaai/openpilot/assets/47793918/749f9804-ed44-474d-969d-139d7dba869d

The following routes are my own routes, I have a C3X
this is on a very old commit (after long enabled on ioniq phev) https://github.com/commaai/openpilot/commit/a552fafd8864bfb31a6e0f042f2816f276f6e66e e1107f9d04dfb1e2|2023-10-17--18-41-47

One ride with stock OP (nlp-driving https://github.com/commaai/openpilot/tree/ace3a59dad2c5c366bccf09cfca9a7a1d75b3501) under this conditions:
e1107f9d04dfb1e2|2023-10-25--10-01-54

LONG disabled
Expermiental disabled

ride with stock OP (nlp-driving https://github.com/commaai/openpilot/tree/ace3a59dad2c5c366bccf09cfca9a7a1d75b3501) under this conditions:
e1107f9d04dfb1e2|2023-10-25--09-46-59--1

LONG enabled
Experimental disabled

ride with stock OP  (nlp-driving https://github.com/commaai/openpilot/tree/ace3a59dad2c5c366bccf09cfca9a7a1d75b3501) under this conditions:
e1107f9d04dfb1e2|2023-10-25--09-39-32

LONG enabled
Experimental enabled

I am also seeing that spiChecksumErrorCount goes up at sort of the same rate than the cumlags

I seem to have found a reliable way to increase cumlag at will!...
Executing /data/openpilot/panda/tests/health_test.py is able to reproduce the spike in spi checksum error count and the cumlag!!

route: e1107f9d04dfb1e2|2023-10-27--12-36-59
that route is with sunnypilot, but I was completely still, with the car in park. The spikes on the cumlag and spichecksum are triggered by me intentionally starting the health_test.py , then stopping it for a while then starting it again.
for this test I had also disabled the ubloxd (i have a c3x).

Branch source: HKG: Car Port for Hyundai Palisade and Kia Telluride 2023-24 (HDA2) #27392
Device: C3X
Route ID: 696748e0ac8082fb|2023-10-24--10-45-04

Another user also experienced this issue. This is stock openpilot + 2023 Hyundai Palisade HDA2 car port changes. ~Seems to be related to pings with Athena but I could be wrong.~ Any information we can provide for troubleshooting?
Recording.2023-10-25.104624.mp4
Edit: This seems to also be correlated with spiChecksumErrorCount instead of Athena.
Recording.2023-10-27.093507.mp4

Branch source: HKG: Car Port for Hyundai Palisade and Kia Telluride 2023-24 (HDA2) #27392
Device: C3X
Route ID: 696748e0ac8082fb|2023-10-24--10-45-04

Another user also experienced this issue. This is stock openpilot + 2023 Hyundai Palisade HDA2 car port changes. ~Seems to be related to pings with Athena but I could be wrong.~ Any information we can provide for troubleshooting?
Recording.2023-10-25.104624.mp4

Same route, spiChecksumErrorCount is spiking badly and seems to be causing everything else to go crazy too.
https://github.com/commaai/openpilot/assets/47793918/db2ac71f-e277-42cd-80f3-02fb52c431e2

@adeebshihadeh @sshane I've ran out of ideas and things to check :( I am not too familiar with Panda code, seems the error is there. Can we please bump the priority on this? We've spent so many hours trying to tackle this already and it's been extremely challenging
this is some output with debug_console.py...
comma@tici:/data/openpilot/panda$ tests/debug_console.py
 00 13 00 00 13

- incorrect data checksum 0007
5a 00 07 00 40 00 b6
13 01 00 13 01 00 13

- incorrect data checksum 000e
5a 03 0e 00 00 00 fc
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00

- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 0007
5a 00 07 00 00 00 f6
13 00 00 13 00 00 13

- incorrect data checksum 0007
5a 00 07 00 40 00 b6
13 02 00 13 02 00 13

- incorrect data checksum 0018
5a 03 18 00 00 00 ea
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00 1a 13
00 1a 13 00 1a 13 00 1a

- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 0018
5a 03 18 00 00 00 ea
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00 1a 13
00 1a 13 00 1a 13 00 1a

- incorrect data checksum 0000
5a 81 00 00 c0 07 b7

- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 000e
5a 03 0e 00 00 00 fc
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00

- incorrect data checksum 0000
5a 81 00 00 c0 07 b7

^Ccomma@tici:/data/openpilot/panda$ tests/debug_console.py
- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 000e
5a 03 0e 00 00 00 fc
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0000
5a 81 00 00 c0 07 b7

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 3e 00 c8
13 00 00 13 00 00 13

- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 0007
5a 00 07 00 00 00 f6
13 00 00 13 00 00 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 0018
5a 03 18 00 00 00 ea
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00 1a 13
00 1a 13 00 1a 13 00 1a

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 40 00 b6
13 01 00 13 01 00 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0018
5a 03 18 00 00 00 ea
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00 1a 13
00 1a 13 00 1a 13 00 1a

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0000
5a 81 00 00 c0 07 b7

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 000e
5a 03 0e 00 00 00 fc
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 000e
5a 03 0e 00 00 00 fc
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00

- incorrect data checksum 0007
5a 00 07 00 40 00 b6
13 01 00 13 01 00 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 000e
5a 03 0e 00 00 00 fc
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect header sync or checksum 11 11 11 11 11 11 11
enable power savings
disable power savings
- incorrect data checksum 0000
5a 81 00 00 c0 07 b7

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0000
5a 81 00 00 c0 07 b7

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 000e
5a 03 0e 00 00 00 fc
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0000
5a 81 00 00 c0 07 b7

- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 000e
5a 03 0e 00 00 00 fc
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00

- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 000e
5a 03 0e 00 00 00 fc
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect data checksum 0018
5a 03 18 00 00 00 ea
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00 1a 13
00 1a 13 00 1a 13 00 1a

- incorrect data checksum 0018
5a 03 18 00 00 00 ea
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00 1a 13
00 1a 13 00 1a 13 00 1a

- incorrect data checksum 0007
5a 00 07 00 e8 03 1d
13 13 13 13 13 13 13

- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect header sync or checksum 11 11 11 11 11 11 11
- incorrect data checksum 0000
5a 81 00 00 c0 07 b7

- incorrect data checksum 000e
5a 03 0e 00 00 00 fc
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00

- incorrect data checksum 0000
5a 81 00 00 c0 07 b7

- incorrect data checksum 0000
5a 81 00 00 c0 07 b7

- incorrect data checksum 000e
5a 03 0e 00 00 00 fc
13 00 1a 13 00 1a 13 00 1a 13 00 1a 13 00

- incorrect data checksum 0000
5a 81 00 00 c0 07 b7

- incorrect data checksum 0000
5a 81 00 00 c0 07 b7

Tracking in #32286


name field required in user table

Pulse Version
1.0@beta
Laravel Version
10.35.0
PHP Version
8.2.3
Livewire Version
N/A
Database Driver & Version
8.0.32
Description
Can we make the user (name) a config option. My user table contains firstname,lastname fields.
Steps To Reproduce
Change the name field in the users table to something else.

same here when I installed it in my application this morning, my user table doesn't have a name column.
Make it optional?

Thanks, @ahinkle for providing the answer here.


Lerna-based projects generate "JavaScript heap out of memory"

Steps to reproduce
Tell us about your environment:

ndb version: 1.0.16
Platform / OS version: macOS 10.13.4 (Darwin 17.5.0)
Node.js version: 8.11.1

What steps will reproduce the problem?
Using Lerna, I have a directory structure as follows:
.
+-- package.json
+-- node_modules
|   +-- lerna
|   +-- babel
|   +-- etc.
+-- packages
|   +-- package-a
|   |   +-- package.json
|   |   +-- node_modules
|   |   |   +-- package-b -> ../../package-b # symlinks
|   |   |   +-- package-c -> ../../package-c
|   |   |   +-- etc. (8 packages total)
|   +-- package-b
|   |   +-- package.json
|   |   +-- node_modules
|   +-- package-c
|   |   +-- package.json
|   |   +-- node_modules
|   +-- etc.

The server begins to start -- I see logs generated by my application -- but at some point before it completes, I get the following in the console:
$ ndb packages/package-a/index.js
Debugger listening on ws://<IP_ADDRESS>:57593/7546efc2-8ffb-46f9-8ba1-8b63ae8a352c
For help see https://nodejs.org/en/docs/inspector
Debugger listening on ws://<IP_ADDRESS>:57594/f759a14c-0514-492d-ac5f-460eeb29f784
For help see https://nodejs.org/en/docs/inspector
Debugger attached.
Debugger attached.

# application startup logs
# (snipped for brevity)

<--- Last few GCs --->

[23721:0x102801e00]   118155 ms: Mark-sweep 1360.4 (1426.5) -> 1360.4 (1427.5) MB, 460.5 / 0.0 ms  allocation failure GC in old space requested
[23721:0x102801e00]   118645 ms: Mark-sweep 1360.4 (1427.5) -> 1360.4 (1420.0) MB, 489.8 / 0.0 ms  last resort GC in old space requested
[23721:0x102801e00]   119122 ms: Mark-sweep 1360.4 (1420.0) -> 1360.4 (1420.0) MB, 476.6 / 0.0 ms  last resort GC in old space requested

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x397ff8d257c1 <JSObject>
    1: DoJoin(aka DoJoin) [native array.js:~94] [pc=0x10bd26d24e43](this=0x397f5d6022d1 <undefined>,o=0x397fc22ddb09 <JSArray[3]>,p=3,D=0x397f5d602371 <true>,z=0x397ff8d3ea79 <String[1]: ,>,y=0x397f5d6023e1 <false>)
    2: Join(aka Join) [native array.js:~119] [pc=0x10bd26d293de](this=0x397f5d6022d1 <undefined>,o=0x397fc22ddb09 <JSArray[3]>,p=3,z=0x397ff8d3ea79 <String[1]: ,>,y=0x397f5d6023e1 <f...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
 1: node::Abort() [/Users/k3n/.nvm/versions/node/v8.11.1/bin/node]
 2: node::FatalException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>) [/Users/k3n/.nvm/versions/node/v8.11.1/bin/node]
 3: v8::internal::V8::FatalProcessOutOfMemory(char const*, bool) [/Users/k3n/.nvm/versions/node/v8.11.1/bin/node]
 4: v8::internal::Factory::NewRawOneByteString(int, v8::internal::PretenureFlag) [/Users/k3n/.nvm/versions/node/v8.11.1/bin/node]
# misc. stacktrace data (changes between runs)
Abort trap: 6
$

Please include code that reproduces the issue.
Code is from a private repo, sorry :(
What is the expected result?
I'm able to debug with ndb.
What happens instead?
I can't debug with ndb.

Could you verify that it is still a problem with ndb 1.0.20? (We landed couple fixes after 1.0.16).
Does you server produce a lot of console logs? Is it some common server (e.g. express) or written from scratch?
You can try to set breakpoint at some point of your program before crash and try to collect heap snapshot on memory tab to find what objects in your app are prevented from being collected by ndb.

Could you verify that it is still a problem with ndb 1.0.20? (We landed couple fixes after 1.0.16).

I plan to when time permits!

Does you server produce a lot of console logs?

In general, not really, though it's possible at startup time to generate a hundred or so as things initialize.

Is it some common server (e.g. express) or written from scratch?

It's hapi.js.

This one should be fixed in canary channel, please try npm install -g ndb@canary.


for react-scripts 2.1.5, webpack.config.dev.js does not exit

Hi, I upgrade "react-scripts" from 1.1.4 to 2.1.5. There is not a file called "webpack.config.dev.js" in "/node_modules/react-scripts/config/webpack.config.dev". Only "webpack.config.js". What should I do now?

If you are using CRA 1.x, or react-scripts-ts, you need to remain with the 1.6.2 release of react-app-rewired. To downgrade, type npm install<EMAIL_ADDRESS>or yarn add<EMAIL_ADDRESS>There were changes in CRA 2.x that included merging the webpack.config.dev.js and webpack.config.prod.js files into a single file webpack.config.js. While react-app-rewired tries to verify which version of CRA you're using and to fallback to the separate files for older versions, that test only works properly with CRA itself - not with alternative versions of react-scripts like react-scripts-ts.
Note for below: by "customised scripts", I mean things like "react-scripts-ts".
Basic compatibility:

If the version of react-scripts that you are using or that the customised scripts is based on is for CRA 1.x, use react-app-rewired 1.x branch (last release was 1.6.2).
If the version of react-scripts that you are using or that the customised scripts is based on is for CRA 2.x, use the react-app-rewired 2.x branch.
If you are using a customised version of react-scripts that was based on CRA 2.x, ask the people providing the customised version to pull in the CRA 2.1.2 change to the webpack config scripts that merged them together so that you can use the react-app-rewired branch 2.x properly.

It works for me. Thank you very much!

@dawnmist What you mean is CRA 2.x with react-scripts-ts also not compatible with react-app-rewired 2.x? like this:
  "scripts": {
    "start": "react-app-rewired start --scripts-version react-scripts-ts",
    "build": "react-app-rewired build --scripts-version react-scripts-ts",
    "test": "react-scripts-ts test --env=jsdom",
    "eject": "react-scripts-ts eject"
  },
  "dependencies": {
    "antd": "^3.15.2",
    "customize-cra": "^0.2.12",
    "react": "^16.8.5",
    "react-dom": "^16.8.5",
    "react-app-rewired":"^2.1.1",
    "react-scripts-ts": "3.1.0"
  },

@navono react-scripts-ts from create-react-app-typescript is based on CRA 1.x. Not CRA 2.x. If you're running with --scripts-version react-scripts-ts, you're NOT using CRA 2.x's build system at all (even if you originally installed with CRA 2.x, by running react-scripts-ts for start/build/test you are no longer using CRA 2.x's build system).
There was an attempt to update react-scripts-ts to CRA 2.x, and a couple of test packages published (versions 4.x). The merge request that those packages were based on - https://github.com/wmonk/create-react-app-typescript/pull/409 - was eventually closed unmerged, and those test packages had several reported issues and never passed to "stable" release. The project itself is now archived, so it will not receive any future updates.
CRA 2.1.2 merged the dev and prod version of the webpack config files together, so that instead of webpack.config.dev.js and webpack.config.prod.js they only had webpack.config.js. The code in react-app-rewired checks if the version number in the scripts being used is >= 2.1.2. Unfortunately, it doesn't also check if you're using the official react-scripts package when it checks that. This means that since react-scripts-ts has a version number greater than 2.1.2, it is mis-identified as needing to use the merged webpack config file. But react-scripts-ts does not HAVE a merged config - it still uses the older separate dev + prod config files - and thus any version of react-app-rewired that contains the compatibility fix for CRA 2.1.2 or later will throw errors for react-scripts-ts and fail to run the start or build scripts.
That compatibility fix was released in react-app-rewired 2.0.
The other complication is that react-scripts-ts also does not use Webpack 4 either - it uses webpack 3.8.1. That causes other related issues. Most of the new rewire packages released for react-app-rewired 2.x expect to be used with Webpack 4, and the chance of incompatibilities is very high as a result. The original list of rewires for react-app-rewired were all written with Webpack 2/3 in mind - which mean that those match up with the build system used in react-scripts-ts.
All of these issues are already documented in this thread, in the react-app-rewired Readme, and in the original react-scripts-ts thread that was created when react-app-rewired 2.0 was originally released.

@dawnmist Thanks for the detailed explain. Looks like it should give up on react-scripts-ts.