profile
viewpoint

HBehrens/puncover 97

Analyses C/C++ build output for code size, static variables, and stack usage

sarfata/kbox-firmware 37

Open-source electronics for your boat

afarhan/radiono 32

Minima's Arduino software. Useful for controlling a homebrew Si570 based superhet transceiver/receiver.

sarfata/kbox-hardware 13

Open-source electronics for your boat

sarfata/4hggt 6

A set of slides that anyone can use to organize a 4 hour Git/GitHub training session.

sarfata/eagleparts 4

Eagle library devices (parts, components, etc) used on my projects

sarfata/introduction-to-pebbledev 3

Examples for the Introduction to Pebble development slides

sarfata/hadbadge2019_fpgasoc 1

FPGA SoC code and application example for Hackaday Supercon 2019 badge

ronzeiller/kbox-firmware 0

Sailing Performance Box (based on KBox)

sarfata/ad9850_siggen 0

My own version of a very simple arduino-piloted ad9850 based signal generator

issue commenttimescale/homebrew-tap

Brew resolves Postgres dependency to v13 which isn't supported yet

Ran into the same issue. This seems pretty similar to #6

I was able to get things back in place by editing the recipe locally.

  • Run brew edit timescaledb
  • Change the dependency to postgresql to postgresql@11
  • Make sure you remove postgresql 13: brew uninstall postgresql --ignore-dependencies
  • Then brew upgrade timescale/tap/timescaledb

I did not lose any data along the way.

(I also tried postgresql@12 too, which I think should work but I was getting compilation errors postgres.h not found - I did not investigate too much since @11 works and is all I need).

baarkerlounger

comment created time in 8 days

pull request commentbenawad/apollo-mocked-provider

fix: import of graphql-tools to work with webpack

So the can't resolve 'module' error is because of my webpack configuration. I needed to ignore the 'module' node package like create-react-app does.

But even with that fix, I still get warnings from the other graphql-tools packages listed above and runtime issues in storybook:

TypeError: Cannot read property 'native' of undefined
    at Object.../node_modules/fs-extra/lib/fs/index.js (http://localhost:9009/vendors~main.870fed89a175efef8db3.bundle.js:393787:24)
    at __webpack_require__ (http://localhost:9009/runtime~main.870fed89a175efef8db3.bundle.js:849:30)
    at fn (http://localhost:9009/runtime~main.870fed89a175efef8db3.bundle.js:151:20)
    at Object.../node_modules/fs-extra/lib/index.js (http://localhost:9009/vendors~main.870fed89a175efef8db3.bundle.js:393806:6)
    at __webpack_require__ (http://localhost:9009/runtime~main.870fed89a175efef8db3.bundle.js:849:30)
    at fn (http://localhost:9009/runtime~main.870fed89a175efef8db3.bundle.js:151:20)
    at Module.<anonymous> (http://localhost:9009/vendors~main.870fed89a175efef8db3.bundle.js:167709:66)
    at Module.../node_modules/@graphql-tools/import/index.esm.js (http://localhost:9009/vendors~main.870fed89a175efef8db3.bundle.js:168201:30)
    at __webpack_require__ (http://localhost:9009/runtime~main.870fed89a175efef8db3.bundle.js:849:30)
    at fn (http://localhost:9009/runtime~main.870fed89a175efef8db3.bundle.js:151:20)

tldr: we should merge the fix. it's very simple and I get no warnings or errors with it.

sarfata

comment created time in a month

PR opened benawad/apollo-mocked-provider

fix: import of graphql-tools to work with webpack

I made a last minute mistake when I was cleaning up yesterday.

It's very important to not import graphql-tools because it references the package resolve-from which confuses webpack and causes an error. (We also get a ton of warnings because other parts of graphql-tools use conditionals require which webpack also does not like).

It's possible to make webpack ignore it but it's going to be easier for everyone if we just avoid the problem by importing the sub-pieces of graphql-tools we do need (and the sub-pieces do not refer the problematic packages).

I think with this commit message and the semantic-release gh action we should get a 4.0.1 automatically so I have not updated the version number.

For reference this is the error I get in my project when I use apollo-mocked-provider 4.0.0 as it is now:

ERROR in ../node_modules/resolve-from/index.js
Module not found: Error: Can't resolve 'module' in '/Users/thomas/work/chartedsails/node_modules/resolve-from'
 @ ../node_modules/resolve-from/index.js 3:15-32
 @ ../node_modules/@graphql-tools/import/index.esm.js
 @ ../node_modules/apollo-mocked-provider/node_modules/graphql-tools/index.esm.js
 @ ../node_modules/apollo-mocked-provider/dist/apollo-mocked-provider.es.production.js
 @ ./src/backend/__mocks__/gqlmocks.tsx
+2 -1

0 comment

1 changed file

pr created time in a month

create barnchsarfata/apollo-mocked-provider

branch : fix/release-40

created branch time in a month

pull request commentbenawad/apollo-mocked-provider

chore: upgrade to @apollo/client 3

I think it's all ready to go and I am using it on one project where it's working well.

:shipit:

sarfata

comment created time in a month

Pull request review commentbenawad/apollo-mocked-provider

chore: upgrade to @apollo/client 3

 test('works with custom links', async () => {   ); }); -test('works with client resolvers', async () => {-  const clientResolvers = {-    Todo: {-      text: () => 'client',-    },-  };+// This test does not pass.

🗑️

sarfata

comment created time in a month

PullRequestReviewEvent

push eventsarfata/apollo-mocked-provider

Thomas Sarlandie

commit sha 61f4b337c721237072f744df41ecfd40f4381dfa

chore: remove client resolvers (deprecated by apollo)

view details

push time in a month

Pull request review commentbenawad/apollo-mocked-provider

chore: upgrade to @apollo/client 3

 test('works with custom links', async () => {   ); }); -test('works with client resolvers', async () => {-  const clientResolvers = {-    Todo: {-      text: () => 'client',-    },-  };+// This test does not pass.

Todo: do we keep this or get rid of clientResolvers?

sarfata

comment created time in a month

PullRequestReviewEvent

push eventsarfata/apollo-mocked-provider

Thomas Sarlandie

commit sha cf26d15d8d50420991840b3116024726960c30aa

refactor: simpler and closer to original reimplementation of fetchTypeDefs

view details

push time in a month

created tagsarfata/apollo-mocked-provider

tag4.0.0

Automatically mock GraphQL data with a mocked ApolloProvider

created time in a month

push eventsarfata/apollo-mocked-provider

Thomas Sarlandie

commit sha 87435a7d9659535f014c14bb5381cbe8c09865cb

doc: remove apollo-react-hooks instructions from readme

view details

push time in a month

PR opened benawad/apollo-mocked-provider

chore: upgrade to @apollo/client 3
  • remove support for custom ApolloProvider. This was required to support apollo-react-hooks but this library is deprecated and hooks are now built in @apollo/client. (I am the one who added this)
  • rewrote the tests to use hooks as the HOC components are not built-in @apollo/client anymore
  • modernize fetchTypeDefs to fetch via graphql-tools (instead of apollo-link-http/HttpLink which has changed and is not compatible with introspectSchema)
  • update tests to pass on errors: apollo does not add the prefix "GraphQL Error" anymore
  • bumped major version number as people should probably only upgrade if they have done the same dependencies update on their project

TBD: Should we also remove support for client resolvers? The test with one fails and they look deprecated (https://www.apollographql.com/docs/react/local-state/local-resolvers/) @sliptype Can you chime in on this? You are the one who added it.

+1820 -502

0 comment

11 changed files

pr created time in a month

create barnchsarfata/apollo-mocked-provider

branch : chore/upgrade-dependencies

created branch time in a month

issue openedraspberrypi/linux

Rpi4 locks up for hours and then resumes with LR is at multi_cpu_stop message

Is this the right place for my bug report?

I believe so: kernel locks up with logs in kernel.log.

Googling for the "LR is at multi_cpu_stop" message does not bring anything for the Raspberry PI so I am opening this issue in the hope of centralizing similar reports.

Describe the bug

Raspberry Pi 4 sometimes locks up for hours. When it is "locked" it does not respond to PING, SSH or even to keyboard inputs on the console (USB keyboard / HDMI screen).

Most of the time, it starts working again on its own after a while.

In kernel.log I can see the following message when it resumes operation (there is nothing when it stops):

Sep 15 01:29:41 raspberrypi kernel: [2046206.492720] LR is at multi_cpu_stop+0xd4/0x188
Sep 15 01:29:41 raspberrypi kernel: [2046206.492723] pc : [<c02dbba4>]    lr : [<c02dbc7c>]    psr: 60000013
Sep 15 01:29:41 raspberrypi kernel: [2046206.492726] sp : ef911ec0  ip : ef911ed0  fp : ef911ecc
Sep 15 01:29:41 raspberrypi kernel: [2046206.492729] r10: 00000000  r9 : d13bbdf4  r8 : c1204fb4
Sep 15 01:29:41 raspberrypi kernel: [2046206.492733] r7 : 00000001  r6 : 00000001  r5 : 00000001  r4 : d13bbe08
Sep 15 01:29:41 raspberrypi kernel: [2046206.492736] r3 : 00000000  r2 : 00000001  r1 : 00000000  r0 : c1204fb4
Sep 15 01:29:41 raspberrypi kernel: [2046206.492739] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment user
Sep 15 01:29:41 raspberrypi kernel: [2046206.492742] Control: 30c5383d  Table: 13e69940  DAC: fffffffd
Sep 15 01:29:41 raspberrypi kernel: [2046206.492746] CPU: 0 PID: 11 Comm: migration/0 Tainted: G         C        5.4.58-v7l+ #1335
Sep 15 01:29:41 raspberrypi kernel: [2046206.492749] Hardware name: BCM2711

Full log file: kernel.log-20200915.log

This issue has been going on for a while now and on two different PIs. I have a crontab running every minute to log the time, uptime and ping the outside world. Logs from this cron also stop when the CPU locks. These logs confirm how long the problem lasted and that the PI did not reboot (the uptime did not go back to 0).

Mon 14 Sep 19:08:01 PDT 2020
 19:08:01 up 23 days, 10:09,  0 users,  load average: 0.00, 0.01, 0.00
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.165/0.165/0.165/0.000 ms

Mon 14 Sep 19:09:01 PDT 2020
 19:09:01 up 23 days, 10:10,  0 users,  load average: 0.00, 0.01, 0.00
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.189/0.189/0.189/0.000 ms

Tue 15 Sep 01:29:41 PDT 2020
 01:29:41 up 23 days, 16:31,  0 users,  load average: 47.00, 47.00, 47.00
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.094/0.094/0.094/0.000 ms

Tue 15 Sep 01:30:01 PDT 2020
 01:30:01 up 23 days, 16:31,  0 users,  load average: 34.15, 44.07, 46.03
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.131/0.131/0.131/0.000 ms

(notice the high load average after it resumes operation)

To reproduce

I have never been able to reach 30 days uptime with the two raspberry pi 4 I own.

Expected behaviour

I expect the pi to be responsive all the time and reach years of uptime without trouble.

Actual behaviour

Looks like the CPU locks up for a few hours and then resumes operation.

System

System Information
------------------

Raspberry Pi 4 Model B Rev 1.2�
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"

Raspberry Pi reference 2019-09-26
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 80d486687ea77d31fc3fc13cf3a2f8b464e129be, stage2

Linux raspberrypi 5.4.58-v7l+ #1335 SMP Thu Aug 13 22:23:01 BST 2020 armv7l GNU/Linux
Revision	: c03112
Serial		: 1000000014960257
Model		: Raspberry Pi 4 Model B Rev 1.2
Throttled flag  : throttled=0x0
Camera          : supported=0 detected=0

Videocore information
---------------------

Aug 17 2020 15:27:57 
Copyright (c) 2012 Broadcom
version 1e1fc5688314d8d9935e272ce8e1c2259890a654 (clean) (release) (start)

alloc failures:     0
compactions:        0
legacy block fails: 0

Filesystem information
----------------------
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/root       15022716 2946952  11429904  21% /
devtmpfs         1827804       0   1827804   0% /dev
tmpfs            1959900       0   1959900   0% /dev/shm
tmpfs            1959900  213052   1746848  11% /run
tmpfs               5120       4      5116   1% /run/lock
tmpfs            1959900       0   1959900   0% /sys/fs/cgroup
/dev/mmcblk0p1    258095   56407    201688  22% /boot
tmpfs             391980       0    391980   0% /run/user/1000

Filename				Type		Size	Used	Priority
/var/swap                               file		102396	0	-2

Package version information
---------------------------
raspberrypi-ui-mods:
  Installed: (none)
raspberrypi-sys-mods:
  Installed: 20191105
openbox:
  Installed: (none)
lxpanel:
  Installed: (none)
pcmanfm:
  Installed: (none)
rpd-plym-splash:
  Installed: (none)

Networking Information
----------------------

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet x.x.x.x  netmask x.x.x.x  broadcast x.x.x.x
        inet6 y::y.y.y.y  prefixlen 64  scopeid 0x20<link>
        ether m.m.m.m  txqueuelen 1000  (Ethernet)
        RX packets 218885233  bytes 1516628128 (1.4 GiB)
        RX errors 98378  dropped 98378  overruns 0  frame 0
        TX packets 222700999  bytes 2393325457 (2.2 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet x.x.x.x  netmask x.x.x.x
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 1679578  bytes 170304289 (162.4 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1679578  bytes 170304289 (162.4 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether m.m.m.m  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


USB Information
---------------

/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M

config.txt
----------

arm_freq=1500
audio_pwm_mode=514
config_hdmi_boost=5
core_freq=500
core_freq_min=200
disable_commandline_tags=2
disable_l2cache=1
display_hdmi_rotate=-1
display_lcd_rotate=-1
enable_gic=1
force_eeprom_read=1
force_pwm_open=1
framebuffer_ignore_alpha=1
framebuffer_swap=1
gpu_freq=500
gpu_freq_min=250
init_uart_clock=0x2dc6c00
lcd_framerate=60
mask_gpu_interrupt0=1024
mask_gpu_interrupt1=0x10000
max_framebuffers=2
over_voltage_avs=-36250
pause_burst_frames=1
program_serial_random=1
total_mem=4096
hdmi_force_cec_address:0=65535
hdmi_force_cec_address:1=65535
hdmi_pixel_freq_limit:0=0x11e1a300
hdmi_pixel_freq_limit:1=0x11e1a300
device_tree=-
overlay_prefix=overlays/
hdmi_cvt:0=
hdmi_cvt:1=
hdmi_edid_filename:0=
hdmi_edid_filename:1=
hdmi_timings:0=
hdmi_timings:1=

cmdline.txt
-----------
coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48 smsc95xx.macaddr=DC:A6:32:74:00:FE vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  console=ttyS0,115200 console=tty1 root=PARTUUID=6c586e13-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait

Full raspinfo output.

Logs (Included above)

Additional context

I have recently updated (rpi-upgrade) to the latest kernel/firmware but these issues happened with the factory provided firmware as well.

There is nothing significant going on on this Raspberry Pi and I have not been able to link the lockups to anything in the "real world". I have Grafana/Telegraf metrics for it and CPU/Mem/Disk/etc all look normal until they disappear and come back a few hours later. As noted above, the CPU usage and load average is high when it resumes operation and quickly goes down. image

The temperature does seem high when it resumes operation: image

created time in a month

fork sarfata/typescript-eslint

:sparkles: Monorepo for all the tooling which enables ESLint to support TypeScript

https://typescript-eslint.io

fork in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha a113f3563387dbe9437e02ed14664b477a0d7c19

release 0.0.3 to fix windows packaging

view details

push time in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha 27fefc5d10c27f5f08fc7fd41161751e4e1a1d18

fix: dont forget to build the preload js when packaging

view details

push time in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha 248e47170cc794e31ac1efa1866a76e8ef0af529

chore: Change name to Action Video Converter Also do some testing on windows

view details

push time in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha 456deb66719acd799ba694d4869472c93df1456b

chore: switch storybook deployment to github-pages-deploy-action

view details

push time in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha 5127b4b04a7241cee121b286cbd4330df3dabd81

fix: do pass ghtoken to storybook deploy action

view details

push time in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha 5ce731625c607adbfbede8fb9b0542303bce1a95

fix: ci flag

view details

Thomas Sarlandie

commit sha 8e1776511b71e73eb10805bc54da7639829d637d

feature: drag and drop to the outside - do not accept files without a video extension - support drag and drop from chartedsails to outside world

view details

push time in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha 7c3a49932dd0c86c4ad87d619aae81832b6677d7

ci: fix action name

view details

push time in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha 3edf799486259f3f7be99cf78a3346ce4c9450a5

feature: fix linux action container name

view details

push time in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha 064325f596e2b256c0514370aa1833b84a75e5a4

ci: build storybook too and publish to github

view details

push time in 2 months

create barnchchartedsails/videoconverter

branch : gh-pages

created branch time in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha e6be5ae553413ee2b04b524279838f6312929ba9

chore: check tsc compiles in precommit

view details

push time in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha 68929dafd2ebac36095a20c9e3c727bac7d987b6

ci: enable win32 build

view details

push time in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha 8e5eab0bcb1b7fd264f5a23024c93487974c5445

chore: add precommit checks

view details

Thomas Sarlandie

commit sha 31f2a4d7404ec815cab00e890300fc5d7dc76147

feature: report errors in the UI

view details

Thomas Sarlandie

commit sha 99785c47a6ecc80022dc637c6a7112fa484bc436

feature: support interrupting conversion and removing files from list

view details

Thomas Sarlandie

commit sha 1ac75022f56c97f167f078fc5a8cd2171e3991eb

feature: set the system progress bar

view details

Thomas Sarlandie

commit sha ab76af972f98365936482b2b856d3a95658b285f

feature: show time estimation sooner

view details

push time in 2 months

push eventchartedsails/videoconverter

Thomas Sarlandie

commit sha 2f46091cb7d2dd476ea17bc76fd222137aa0b7e2

doc: add readme + fix release repo

view details

push time in 2 months

created tagchartedsails/app-releases

tagv0.0.5

Manage media for ChartedSails.com

created time in 3 months

created tagchartedsails/app-releases

tagv0.0.3

Manage media for ChartedSails.com

created time in 3 months

push eventchartedsails/app-releases

Thomas Sarlandie

commit sha 12951c19171b3d0850ef13c9bcf174795eb45be2

Update README.md

view details

push time in 3 months

create barnchchartedsails/mediabox

branch : master

created branch time in 3 months

created repositorychartedsails/mediabox

Manage media for ChartedSails.com

created time in 3 months

push eventsarfata/gopro-telemetry

Juan Irache

commit sha 4990d0691e0e2c9d8f84cc9760ebef2a0ba5d245

Merge branch 'sarfata-improve-parsing-speed' into dev

view details

Juan Irache

commit sha 3b01cbfa85a7403a7ec1412a1d81f0fd30e17d3e

1.0.9

view details

Juan Irache

commit sha 0cedc55a8499054630771f5e0fc976638913a347

acknowledgements

view details

Juan Irache

commit sha 63a9d030657f5a07ee71b2ab5a9982e57d5ce10e

Merge branch 'master' into dev

view details

Juan Irache

commit sha 53c0511785db9097cce005eff09f8dfe61af2271

Merge pull request #119 from JuanIrache/dev Dev

view details

JuanIrache

commit sha 65df053342c60791d2ae67761c98ff6e5cc45abe

use date of first file to offset the time of other files when using GPS times

view details

JuanIrache

commit sha 4727e524a1c9de7d4389c3bec7896daf8c3d434e

1.0.10

view details

Juan Irache

commit sha 5cc3df64f82b69e9a847a994ca77436798223fd5

Merge pull request #120 from JuanIrache/dev Dev

view details

JuanIrache

commit sha c91788b57bf96a9f3abc1651122ca61a931a91db

add note

view details

JuanIrache

commit sha ad75c43891861d4ac58cee6c4d95db18323645a6

add breathing to setSourceOffset

view details

JuanIrache

commit sha 196b3f7b86bc0023eb247a314d57e0d448f2a9f9

1.0.11

view details

Juan Irache

commit sha 8f1575064a8bfc21388707b111c791b0c89190be

Merge pull request #121 from JuanIrache/dev Dev

view details

JuanIrache

commit sha 015c5164e875f1e175ae2e5059376cf0afd33332

Merge branch 'master' of github.com:JuanIrache/gopro-telemetry

view details

JuanIrache

commit sha 37a67f351b46daa8e1a7301da0ac02a1bf89f2a7

start replacing setSourceOffset with more consistent approach

view details

JuanIrache

commit sha 7e302ce3b4f8675ddf950c9fb59c72c42c25d2b3

refactor

view details

JuanIrache

commit sha b7ca553c4edf3b17cd507477aca720726c06c647

simplify timeMeta variables, use offset to identify merging files

view details

JuanIrache

commit sha 2b3701320649934760e1914095fad418cae49275

fix calculating offset

view details

JuanIrache

commit sha 5f39d6cdfeae2ab0134234911c43dd7ac48cfa83

adjust consecutive testing data

view details

JuanIrache

commit sha 436e43a1c8733a3055f423c94e6abeeb05b276d4

format

view details

JuanIrache

commit sha 0bf80661e0b69d612b8be7d64c9e2d4e10bb37c2

document new timing features

view details

push time in 3 months

PR opened JuanIrache/gopro-telemetry

fix: bug in grouping when executing in parallel

There is one variable in groupDevices that was not scoped to the function. It's content was thus shared between different parallel executions and this caused incorrect results.

The solution is to add const to make sure the variable is scoped to the function.

I tried adding a test but this bug only shows in the browser, not in Node so the test fails to break when the problem exists.

+1 -1

0 comment

1 changed file

pr created time in 3 months

create barnchsarfata/gopro-telemetry

branch : bugfix/groupdevices-fails-in-parallel

created branch time in 3 months

push eventsarfata/gopro-telemetry

JuanIrache

commit sha 7c034ec30478ea92f0c13397c767fd7c9ce21999

fix bad results in cori and similar streams while not breaking others

view details

JuanIrache

commit sha 8f2e3d4304326acac2a54a3bf85366e332355183

1.0.7

view details

Juan Irache

commit sha 27482af33a3b74159c28910b515e08f883c36333

Merge pull request #116 from JuanIrache/dev Dev

view details

JuanIrache

commit sha aad790ab341f907eba99ded1cbf2cb0cd3bccaee

npm audit fix

view details

JuanIrache

commit sha d3aa62672f6e22da933acc04351d6ae8e48e6b1a

1.0.8

view details

Juan Irache

commit sha 0e8b84102f2765036eb78124148eeddde5fb7918

Merge pull request #117 from JuanIrache/dev Dev

view details

Thomas Sarlandie

commit sha fd0d0bfdb14cf9b25c80dff020b988a6b6931fc6

feature: cache binary parsers to reduce parsing time The binary parser library generates some javascript code based on the configuration we give it and then parses that code. This is a very expensive operation. We recreated the parsers every time for each individual value. By reusing them we save a lot of time. This simple changes improves performance by about 20 times in my tests. We have to keep a separate parser for each different length we can get because changing the length option requires recompilation. In my tests we only need 20 different parsers for a 7GB gopro hero8 file.

view details

Juan Irache

commit sha 4990d0691e0e2c9d8f84cc9760ebef2a0ba5d245

Merge branch 'sarfata-improve-parsing-speed' into dev

view details

Juan Irache

commit sha 3b01cbfa85a7403a7ec1412a1d81f0fd30e17d3e

1.0.9

view details

Juan Irache

commit sha 0cedc55a8499054630771f5e0fc976638913a347

acknowledgements

view details

Juan Irache

commit sha 63a9d030657f5a07ee71b2ab5a9982e57d5ce10e

Merge branch 'master' into dev

view details

Juan Irache

commit sha 53c0511785db9097cce005eff09f8dfe61af2271

Merge pull request #119 from JuanIrache/dev Dev

view details

JuanIrache

commit sha 65df053342c60791d2ae67761c98ff6e5cc45abe

use date of first file to offset the time of other files when using GPS times

view details

JuanIrache

commit sha 4727e524a1c9de7d4389c3bec7896daf8c3d434e

1.0.10

view details

Juan Irache

commit sha 5cc3df64f82b69e9a847a994ca77436798223fd5

Merge pull request #120 from JuanIrache/dev Dev

view details

JuanIrache

commit sha c91788b57bf96a9f3abc1651122ca61a931a91db

add note

view details

JuanIrache

commit sha ad75c43891861d4ac58cee6c4d95db18323645a6

add breathing to setSourceOffset

view details

JuanIrache

commit sha 196b3f7b86bc0023eb247a314d57e0d448f2a9f9

1.0.11

view details

Juan Irache

commit sha 8f1575064a8bfc21388707b111c791b0c89190be

Merge pull request #121 from JuanIrache/dev Dev

view details

JuanIrache

commit sha 015c5164e875f1e175ae2e5059376cf0afd33332

Merge branch 'master' of github.com:JuanIrache/gopro-telemetry

view details

push time in 3 months

delete branch sarfata/gopro-telemetry

delete branch : patch-1

delete time in 3 months

delete branch sarfata/gopro-telemetry

delete branch : bugfix/parallel-grouping-bug

delete time in 3 months

push eventsarfata/gopro-telemetry

Thomas Sarlandie

commit sha a3c8a5a04a0373e425888ce5340c797311530095

fix: bug in grouping when executing in parallel There is one variable in groupDevices that was not scoped to the function. It's content was thus shared between different parallel executions and this caused incorrect results. The solution is to add `const` to make sure the variable is scoped to the function. I tried adding a test but this bug only shows in the browser, not in Node so the test fails to break when the problem exists.

view details

push time in 3 months

create barnchsarfata/gopro-telemetry

branch : bugfix/parallel-grouping-bug

created branch time in 3 months

issue commentfacebook/create-react-app

Macro reloading

What is the current non-graphql workaround?

See https://github.com/facebook/create-react-app/issues/5580#issuecomment-566420375 - Reload the .ts[x] file that includes the .mdx (or anything).

jamesknelson

comment created time in 3 months

more