Make the cop generator to work on rubocop-rspec

I would like to use the cop generator in rubocop-rspec. However, the task does not work well on the project now.
This change will make the generator to work on rubocop-rspec.
It changes the following things.

Make inject_require and inject_config to receive a file name that is a target of injection as a keyword argument.
Tweak snake_case method. The method convert "RSpec" to r_spec now. It will be "rspec" by this change.
Refactor the generator.
Modify the output style of the generator. The new style is similar to rails generator's output.

The new style's implementation is easier and simpler than the old style.
before$ bundle exec rake new_cop[Style/Foo]
Files created:
  - lib/rubocop/cop/style/foo.rb
  - spec/rubocop/cop/style/foo_spec.rb
File modified:
  - `require_relative 'rubocop/cop/style/foo'` added into lib/rubocop.rb
  - A configuration for the cop is added into config/enabled.yml
    - If you want to disable the cop by default, move the added config to config/disabled.yml

Do 3 steps:
  1. Add an entry to the "New features" section in CHANGELOG.md,
     e.g. "Add new `Style/Foo` cop. ([@your_id][])"
  2. Modify the description of Style/Foo in config/enabled.yml
  3. Implement your new cop in the generated file!

after$ bundle exec rake new_cop[Style/Foo]
[create] lib/rubocop/cop/style/foo.rb
[create] spec/rubocop/cop/style/foo_spec.rb
[modify] lib/rubocop.rb - `require_relative 'rubocop/cop/style/foo'` was injected.
[modify] A configuration for the cop is added into config/enabled.yml.
         If you want to disable the cop by default, move the added config to config/disabled.yml
Do 3 steps:
  1. Add an entry to the "New features" section in CHANGELOG.md,
     e.g. "Add new `Style/Foo` cop. ([@your_id][])"
  2. Modify the description of Style/Foo in config/enabled.yml
  3. Implement your new cop in the generated file!

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[ ] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Run rake default or rake parallel. It executes all tests and RuboCop for itself, and generates the documentation.

I've finished refactoring! And I also opened a pull-request on rubocop-rspec. https://github.com/backus/rubocop-rspec/pull/517


Fix awkward Korean Translation

It's really simple PR :)

The Travis failure is due to second overlap between Date::now() and the next Date::now() and can be fix by merging #289

Would love to get some additional reviewers on this :)

Oh.. that was my mistake
Sorry i'll fix it

I created clean PR again #290


[Search v2] [App] Create Type filter

Implement this section of the design doc for the Type filter only!
cc @adamgrzybowski @Kicu @WojtekBoman @Guccio163

@Kicu is already working on this one!

Sounds good! @Kicu mind commenting here so we can assign you, and linking the PR (if there is one)

hey yes, I am working on this already 😄 in this draft  https://github.com/Expensify/App/pull/46022

Sweet, TY! Linked this issue to that PR too.

PR in review

I'm gonna close this issue since we'll handle payment in https://github.com/Expensify/App/issues/46029

Sounds good. TY!


libcamera-apps not working on RPi 3 Model B+

Hi,
I am trying to run libcamera-apps in my Raspberry Pi 3 Model B+. I get the below error:
$ libcamera-jpeg -o ~/Desktop/test6.jpg
[0:26:34.032643212] [2313]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3097-fa7a95bf
ERROR: *** no cameras available ***

but my camera is detected:
$ sudo vcgencmd get_camera
supported=1 detected=1

same for
$ sudo libcamera-hello
[0:49:18.747128742] [3096]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3097-fa7a95bf
ERROR: *** no cameras available ***

and, if I use raspistill, the camera seems to work fine:
$ raspistill -o ~/Desktop/test.jpg

works great. I can see a pop up window with video, image is saved.
I am following the guide from Raspberry Pi site: https://www.raspberrypi.com/documentation/accessories/camera.html#building-libcamera-and-libcamera-apps
I have built by specifying -Dv4l2=true to the meson configure command and without. The result is the same. I also tried to run with -n, still same error.
I am clueless to what is happening. The camera seems to be installed correctly and works fine, so the problem in my case seems to be with the libcamera-apps. Any ideas what could be missing here, or at least some guidance to debug this?
Some info of my setup:
$ sudo vcgencmd version
Sep 28 2021 11:33:44
Copyright (c) 2012 Broadcom
version 778b6a4f3c7d8d48bb63c02c47bcfbac79417bea (clean) (release) (start_x)

$ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

/boot/config.txt file:
$ cat /boot/config.txt
disable_overscan=1

# I have tried both setting the below to on and commenting out, same result
dtparam=i2c_arm=on
dtparam=audio=on

[pi4]
max_framebuffers=2

[all]
# imx219 did not work at all - not even raspistil.
# raspistill works with vc4-fkms-v3d
dtoverlay=vc4-fkms-v3d
#dtoverlay=imx219
start_x=1
gpu_mem=128

Let me know if I can provide further info.
Many Thanks,
Babis

Hi @davidplowman , thanks for your reply. I have already tried this and it didn't help. In fact, when I set dtoverlay=imx219, then the camera is not detected at all:
$ sudo vcgencmd get_camera
supported=1 detected=0

OK, I got a fresh Raspbian Buster, ran all the steps listed in official RPI site regarding the build of libcamera-apps.
Something works, but something is wrong.
My config
$ cat /boot/config.txt
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=1

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
#dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
dtoverlay=imx219
start_x=1
gpu_mem=128

Camera seems not detected:
$ sudo vcgencmd get_camera
supported=1 detected=0

libcamera-hello - NOT working
$ libcamera-hello
libEGL warning: DRI2: failed to authenticate
[0:19:58.125501550] [2636]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3100-0ce723fc
[0:19:58.184663587] [2636]  INFO Camera camera.cpp:937 configuring streams: (0) 1640x1232-YUV420
[0:19:58.185014046] [2647]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt RG10 Score: 2218 (best 2218)
[0:19:58.185154250] [2647]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RG10 Score: 2041.48 (best 2041.48)
[0:19:58.185228050] [2647]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt RG10 Score: 1500 (best 1500)
[0:19:58.185290601] [2647]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt RG10 Score: 5004.81 (best 1500)
[0:19:58.185356016] [2647]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt pRAA Score: 1718 (best 1500)
[0:19:58.185416326] [2647]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pRAA Score: 1541.48 (best 1500)
[0:19:58.185478095] [2647]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt pRAA Score: 1000 (best 1000)
[0:19:58.185538302] [2647]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt pRAA Score: 4504.81 (best 1000)
[0:19:58.185604759] [2647]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt RGGB Score: 3218 (best 1000)
[0:19:58.185664028] [2647]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RGGB Score: 3041.48 (best 1000)
[0:19:58.185724964] [2647]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt RGGB Score: 2500 (best 1000)
[0:19:58.185785326] [2647]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt RGGB Score: 6004.81 (best 1000)
[0:19:58.186086203] [2647]  INFO RPI raspberrypi.cpp:620 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected mode: 1640x1232-pRAA
[0:19:58.325198965] [2651]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[0:19:58.325416199] [2651]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[0:19:58.325475781] [2651]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[0:19:58.325537341] [2651]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[0:19:58.325588955] [2651]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 33333, 33333 ]
[0:19:58.325667129] [2651]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 3
[0:19:58.325730148] [2651]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[0:19:58.325785668] [2651]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[0:19:58.325836187] [2651]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[0:19:58.325924362] [2651]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[0:19:58.327021831] [2647]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:19:58.327078704] [2647]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:19:58.327122193] [2647]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:19:58.412352092] [2647]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (6 left)
[0:19:58.443061647] [2647]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (5 left)
[0:19:58.479978059] [2647]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (4 left)
[0:19:58.513771068] [2647]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (3 left)
[0:19:58.546534472] [2647]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (2 left)
[0:19:58.591505293] [2647]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (1 left)
[0:19:58.615680135] [2647]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (0 left)
terminate called after throwing an instance of 'std::runtime_error'
  what():  failed to import fd 18
Aborted

libcamera-hello -n - WORKING
$ libcamera-hello -n
[0:20:47.145893622] [2660]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3100-0ce723fc
[0:20:47.208170500] [2660]  INFO Camera camera.cpp:937 configuring streams: (0) 1640x1232-YUV420
[0:20:47.209504322] [2662]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt RG10 Score: 2218 (best 2218)
[0:20:47.209903375] [2662]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RG10 Score: 2041.48 (best 2041.48)
[0:20:47.210090610] [2662]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt RG10 Score: 1500 (best 1500)
[0:20:47.210187483] [2662]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt RG10 Score: 5004.81 (best 1500)
[0:20:47.210289876] [2662]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt pRAA Score: 1718 (best 1500)
[0:20:47.210384249] [2662]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pRAA Score: 1541.48 (best 1500)
[0:20:47.210480861] [2662]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt pRAA Score: 1000 (best 1000)
[0:20:47.210575546] [2662]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt pRAA Score: 4504.81 (best 1000)
[0:20:47.210681898] [2662]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt RGGB Score: 3218 (best 1000)
[0:20:47.210775177] [2662]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RGGB Score: 3041.48 (best 1000)
[0:20:47.210870695] [2662]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt RGGB Score: 2500 (best 1000)
[0:20:47.210965068] [2662]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt RGGB Score: 6004.81 (best 1000)
[0:20:47.211295216] [2662]  INFO RPI raspberrypi.cpp:620 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected mode: 1640x1232-pRAA
[0:20:47.320802410] [2666]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[0:20:47.321187453] [2666]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[0:20:47.321273700] [2666]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[0:20:47.321339063] [2666]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[0:20:47.321399479] [2666]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 33333, 33333 ]
[0:20:47.321509945] [2666]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 3
[0:20:47.321578276] [2666]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[0:20:47.321639890] [2666]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[0:20:47.321693326] [2666]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[0:20:47.321824260] [2666]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[0:20:47.323786036] [2662]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:20:47.324051862] [2662]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:20:47.324156495] [2662]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:20:47.411211524] [2662]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (6 left)
[0:20:47.444005418] [2662]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (5 left)
[0:20:47.479293887] [2662]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (4 left)
[0:20:47.513055882] [2662]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (3 left)
[0:20:47.545052087] [2662]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (2 left)
[0:20:47.579266780] [2662]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (1 left)
[0:20:47.621232743] [2662]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (0 left)

libcamera-jpeg -o ~/Desktop/test1.jpg - NOT working
$ libcamera-jpeg -o ~/Desktop/test1.jpg
libEGL warning: DRI2: failed to authenticate
[0:21:17.269505608] [2703]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3100-0ce723fc
[0:21:17.344956852] [2703]  INFO Camera camera.cpp:937 configuring streams: (0) 1640x1232-YUV420
[0:21:17.345462309] [2714]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt RG10 Score: 2218 (best 2218)
[0:21:17.345688294] [2714]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RG10 Score: 2041.48 (best 2041.48)
[0:21:17.345769698] [2714]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt RG10 Score: 1500 (best 1500)
[0:21:17.345833707] [2714]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt RG10 Score: 5004.81 (best 1500)
[0:21:17.345904747] [2714]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt pRAA Score: 1718 (best 1500)
[0:21:17.345968235] [2714]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pRAA Score: 1541.48 (best 1500)
[0:21:17.346032140] [2714]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt pRAA Score: 1000 (best 1000)
[0:21:17.346092816] [2714]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt pRAA Score: 4504.81 (best 1000)
[0:21:17.346163023] [2714]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt RGGB Score: 3218 (best 1000)
[0:21:17.346223855] [2714]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RGGB Score: 3041.48 (best 1000)
[0:21:17.346286145] [2714]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt RGGB Score: 2500 (best 1000)
[0:21:17.346347185] [2714]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt RGGB Score: 6004.81 (best 1000)
[0:21:17.346630825] [2714]  INFO RPI raspberrypi.cpp:620 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected mode: 1640x1232-pRAA
[0:21:17.562253179] [2718]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[0:21:17.562575047] [2718]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[0:21:17.562640202] [2718]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[0:21:17.562698638] [2718]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[0:21:17.562750408] [2718]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 33333, 33333 ]
[0:21:17.562831239] [2718]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 3
[0:21:17.562897331] [2718]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[0:21:17.562950976] [2718]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[0:21:17.562999517] [2718]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[0:21:17.563061911] [2718]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[0:21:17.564554118] [2714]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:21:17.564671459] [2714]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:21:17.564720885] [2714]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:21:17.662318773] [2714]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (6 left)
[0:21:17.696418642] [2714]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (5 left)
[0:21:17.732878927] [2714]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (4 left)
[0:21:17.761801619] [2714]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (3 left)
[0:21:17.795248585] [2714]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (2 left)
[0:21:17.842290719] [2714]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (1 left)
[0:21:17.866258573] [2714]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (0 left)
terminate called after throwing an instance of 'std::runtime_error'
  what():  failed to import fd 18
Aborted

libcamera-jpeg -o ~/Desktop/test1.jpg -n - WORKING
$ libcamera-jpeg -o ~/Desktop/test2.jpg -n
[0:22:11.123696169] [2722]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3100-0ce723fc
[0:22:11.186753977] [2722]  INFO Camera camera.cpp:937 configuring streams: (0) 1640x1232-YUV420
[0:22:11.187361726] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt RG10 Score: 2218 (best 2218)
[0:22:11.187608908] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RG10 Score: 2041.48 (best 2041.48)
[0:22:11.187698855] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt RG10 Score: 1500 (best 1500)
[0:22:11.187766145] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt RG10 Score: 5004.81 (best 1500)
[0:22:11.187845675] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt pRAA Score: 1718 (best 1500)
[0:22:11.187910465] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pRAA Score: 1541.48 (best 1500)
[0:22:11.187978901] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt pRAA Score: 1000 (best 1000)
[0:22:11.188043223] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt pRAA Score: 4504.81 (best 1000)
[0:22:11.188126607] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt RGGB Score: 3218 (best 1000)
[0:22:11.188192751] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RGGB Score: 3041.48 (best 1000)
[0:22:11.188256865] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt RGGB Score: 2500 (best 1000)
[0:22:11.188321551] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt RGGB Score: 6004.81 (best 1000)
[0:22:11.188701440] [2724]  INFO RPI raspberrypi.cpp:620 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected mode: 1640x1232-pRAA
[0:22:11.268570541] [2728]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[0:22:11.269070948] [2728]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[0:22:11.269179540] [2728]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[0:22:11.269246570] [2728]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[0:22:11.269300058] [2728]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 33333, 33333 ]
[0:22:11.269419223] [2728]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 3
[0:22:11.269493232] [2728]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[0:22:11.269554116] [2728]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[0:22:11.269608334] [2728]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[0:22:11.269741873] [2728]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[0:22:11.271628816] [2724]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:22:11.271732564] [2724]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:22:11.271779021] [2724]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:22:11.365582336] [2724]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (6 left)
[0:22:11.397256263] [2724]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (5 left)
[0:22:11.433158964] [2724]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (4 left)
[0:22:11.467370603] [2724]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (3 left)
[0:22:11.499101508] [2724]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (2 left)
[0:22:11.532535297] [2724]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (1 left)
[0:22:11.566469911] [2724]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (0 left)
[0:22:16.388565314] [2722]  INFO Camera camera.cpp:937 configuring streams: (0) 3280x2464-YUV420
[0:22:16.389230822] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt BG10 Score: 1500 (best 1500)
[0:22:16.389394569] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt BG10 Score: 7155.48 (best 1500)
[0:22:16.389461860] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt BG10 Score: 7244 (best 1500)
[0:22:16.389523890] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt BG10 Score: 10748.8 (best 1500)
[0:22:16.389592430] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt BA81 Score: 2500 (best 1500)
[0:22:16.389653783] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt BA81 Score: 8155.48 (best 1500)
[0:22:16.389715553] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt BA81 Score: 8244 (best 1500)
[0:22:16.389776385] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt BA81 Score: 11748.8 (best 1500)
[0:22:16.389838311] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt pBAA Score: 1000 (best 1000)
[0:22:16.389898310] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pBAA Score: 6655.48 (best 1000)
[0:22:16.389959298] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt pBAA Score: 6744 (best 1000)
[0:22:16.390112004] [2724]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt pBAA Score: 10248.8 (best 1000)
[0:22:16.390358041] [2724]  INFO RPI raspberrypi.cpp:620 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected mode: 3280x2464-pBAA
[0:22:16.507574949] [2730]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[0:22:16.507768956] [2730]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[0:22:16.507834944] [2730]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[0:22:16.507894110] [2730]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[0:22:16.507946400] [2730]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 100,<PHONE_NUMBER> ]
[0:22:16.508020201] [2730]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 2
[0:22:16.508073117] [2730]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[0:22:16.508132282] [2730]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[0:22:16.508183636] [2730]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[0:22:16.508240353] [2730]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
Still capture image received

libcamera-hello --qt-preview - WORKING
$ libcamera-hello --qt-preview
libEGL warning: DRI2: failed to authenticate
qt5ct: using qt5ct plugin
[0:22:53.429417854] [2743]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3100-0ce723fc
[0:22:53.490765347] [2743]  INFO Camera camera.cpp:937 configuring streams: (0) 1640x1232-YUV420
[0:22:53.491189038] [2756]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt RG10 Score: 2218 (best 2218)
[0:22:53.491378462] [2756]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RG10 Score: 2041.48 (best 2041.48)
[0:22:53.491461377] [2756]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt RG10 Score: 1500 (best 1500)
[0:22:53.491527939] [2756]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt RG10 Score: 5004.81 (best 1500)
[0:22:53.491594656] [2756]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt pRAA Score: 1718 (best 1500)
[0:22:53.491656061] [2756]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt pRAA Score: 1541.48 (best 1500)
[0:22:53.491718092] [2756]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt pRAA Score: 1000 (best 1000)
[0:22:53.491778299] [2756]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt pRAA Score: 4504.81 (best 1000)
[0:22:53.491851943] [2756]  INFO RPI raspberrypi.cpp:122 Mode: 3280x2464 fmt RGGB Score: 3218 (best 1000)
[0:22:53.491916057] [2756]  INFO RPI raspberrypi.cpp:122 Mode: 1920x1080 fmt RGGB Score: 3041.48 (best 1000)
[0:22:53.491978035] [2756]  INFO RPI raspberrypi.cpp:122 Mode: 1640x1232 fmt RGGB Score: 2500 (best 1000)
[0:22:53.492038086] [2756]  INFO RPI raspberrypi.cpp:122 Mode: 640x480 fmt RGGB Score: 6004.81 (best 1000)
[0:22:53.492324748] [2756]  INFO RPI raspberrypi.cpp:620 Sensor: /base/soc/i2c0mux/i2c@1/imx219@10 - Selected mode: 1640x1232-pRAA
[0:22:53.653029868] [2760]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Sharpness = 1.000000
[0:22:53.653868551] [2760]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Saturation = 1.000000
[0:22:53.654310887] [2760]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Contrast = 1.000000
[0:22:53.654478645] [2760]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: Brightness = 0.000000
[0:22:53.655653312] [2760]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: FrameDurationLimits = [ 33333, 33333 ]
[0:22:53.656126377] [2760]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: NoiseReductionMode = 3
[0:22:53.656503037] [2760]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeMeteringMode = 0
[0:22:53.656767356] [2760]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AeExposureMode = 0
[0:22:53.656880531] [2760]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: ExposureValue = 0.000000
[0:22:53.657064538] [2760]  INFO IPARPI raspberrypi.cpp:626 Request ctrl: AwbMode = 0
[0:22:53.660304118] [2756]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:22:53.660495105] [2756]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:22:53.660547968] [2756]  INFO RPISTREAM rpi_stream.cpp:122 No buffers available for ISP Output0
[0:22:53.747904653] [2756]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (6 left)
[0:22:53.777607532] [2756]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (5 left)
[0:22:53.812659016] [2756]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (4 left)
[0:22:53.845874334] [2756]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (3 left)
[0:22:53.881427060] [2756]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (2 left)
[0:22:53.912288200] [2756]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (1 left)
[0:22:53.945657890] [2756]  INFO RPI raspberrypi.cpp:1636 Dropping frame at the request of the IPA (0 left)

So it seems that using -n works ok, so does the qt-preview as @davidplowman suggested. But without -n, none of those apps seem to work. Seems that this relates to qt somehow?

OK, hold on a second because I've just realized something crucial; when you wrote uncomment the dtoverlay=vc4-fkms-v3d line in the /boot/config.txt, you literally meant to just uncomment (AND keep the other dtoverlay setting - imx219 in my case)?
What I was trying was to keep one but not another, so I was trying with EITHER dtoverlay=imx219 or dtoverlay=vc4-fkms-v3d - and I was getting the above mentioned errors in both cases.

So, when I keep both in my /boot/config.txt, ie:
...
dtoverlay=vc4-fkms-v3d
dtoverlay=imx219
...

all commands work great (both with -n and without)!!
Thanks @davidplowman  :)

Glad you've figured it out. Sorry if the instructions aren't always totally clear, the new documentation website is still WIP to some extent. And life will get much better once the new Bullseye OS is released soon, stuff will just work "out of the box".

Hi @babinos87 and @davidplowman,
Here is my config file for RPI4
[pi4]
dtoverlay=vc4-fkms-v3d
dtoverlay=imx219
Run as fast as firmware / board allows
arm_boost=1
and
Here is libcamera-hello
libcamera-hello
libEGL warning: DRI2: failed to authenticate
Made X/EGL preview window
[0:32:00.312563346] [2941]  INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3424-e68e0f1e
ERROR: *** no cameras available ***
I have both
dtoverlay=vc4-fkms-v3d
dtoverlay=imx219
enabled(uncommented) but still camera doesn't work please help......

Also having problems with dtoverlay=vc4-fkms-v3d (Firmware/Fake)KMS vs Full KMS dtoverlay=vc4-kms-v3d (which is ok but then the touchscreen doesn't work)

@harshalak77 were you able to solve your issue?

Hello,
please make sure your driver config is in all section, not in pi4

Hi @babinos87 and @davidplowman, Here is my config file for RPI4
[pi4] dtoverlay=vc4-fkms-v3d dtoverlay=imx219 arm_boost=1
and
Here is libcamera-hello command output
libcamera-hello libEGL warning: DRI2: failed to authenticate Made X/EGL preview window [0:32:00.312563346] [2941] INFO Camera camera_manager.cpp:293 libcamera v0.0.0+3424-e68e0f1e ERROR: *** no cameras available ***
I have both dtoverlay=vc4-fkms-v3d dtoverlay=imx219 enabled(uncommented) but still camera doesn't work please help......

I have the same issue since days. I Installed a new image (Bullseye) and tried again, but the preview always fails. I need this preview for my work so the --qt-preview works, but isn't the solution for it. Did you solve it @harshalak77 ?

what you mean by that?

Generally my advice is to start by connecting a keyboard and HDMI display directly to your Pi, downloading the latest image, touching absolutely nothing else in the image, and seeing if libcamera-hello works.
If that works as it should then proceed to change just one thing at a time until you reach a point where it doesn't. If it doesn't "just work" at the outset, then something is either not plugged in properly or actually broken.
If you haven't been able to get things working by the above steps, then please file a new issue. Thanks!

Thanks I'll try it


Hello. I need help :)

I use RxFeedback in the project, but I have a problem and I can not solve it either. And most likely it's from a lack of knowledge.
I use "methodInvoked (#selector (UIViewController.viewWillAppear (_ :)))" and send the "readyView" event to the system.
But "methodInvoked" does not send element to the system, but if you subscribe without the system, everything is fine.
And if the UIViewController.viewWillAppear method is repeatedly called, then the message comes through.
Here is an example
https://github.com/mefilt/RxFeedbackTest/blob/master/RxFeedbackTest/ViewController.swift
Thx

I encountered a similar issue when building a bluetooth system that I start on application launch. The system was monitoring the methodInvoked stream for appDidBecomeActive but it seems to me that the system was missing the first event due to the async nature of the architecture. So it subscribed right after the method was invoked. @kzaher is this a correct behavior?
It doesn't happen on all devices/iOS versions though.
I solved it by using a BehaviorRelay instead of the methodInvoked. I update the variable in viewWillAppear and viewWillDisappear and the system gets notified and will not miss the event. I think it makes sense as it's more like a state rather than just a Signal that you need.


Update kubectl path with full reference location of calico.yaml

Description

Todos

[ ] Tests
[x] Documentation
[ ] Release note

Release Note
None required

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: ANIRBAN:x: anirban37ANIRBAN seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: ANIRBAN:x: anirban37ANIRBAN seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

As described in https://github.com/projectcalico/calico/pull/1288, we do appreciate your PR. This is not a change that we want to make, but it's good for us to hear of the confusion here and we plan to fix this in a different way soon.


Facebook login

Is it possible login using the facebook account?
Thanks

Not directly, a tidal username/password is required.
I found this on the web, give it a try
1 - Go to https://listen.tidalhifi.com/
2 - Click Log In
3 - Click Forgot your password?
4 - Enter the email address associated with your Facebook or Twitter account and click Request new password.
Let me know if it works...


Fixes for fp8 + hiprtc

Some fixes that might be required for fp8 changes + hiprtc

Superseded by pull #445


python310Packages.radish-bdd: 0.15.0 -> 0.16.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.radish-bdd is: Behaviour-Driven-Development tool for python
meta.homepage for python310Packages.radish-bdd is: http://radish-bdd.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.16.1 with grep in /nix/store/y72lq0vh26c4rbpbb192vakj5cpaz1mw-python3.10-radish-bdd-0.16.1
found 0.16.1 in filename of file in /nix/store/y72lq0vh26c4rbpbb192vakj5cpaz1mw-python3.10-radish-bdd-0.16.1

Rebuild report (if merged into master) (click to expand)

9 total rebuild path(s)

9 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.awswrangler
python310Packages.cassandra-driver
python310Packages.gremlinpython
python310Packages.radish-bdd
python311Packages.awswrangler
python311Packages.cassandra-driver
python311Packages.gremlinpython
python311Packages.radish-bdd
terraform-compliance

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/y72lq0vh26c4rbpbb192vakj5cpaz1mw-python3.10-radish-bdd-0.16.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.radish-bdd https://github.com/r-ryantm/nixpkgs/archive/444ef095c9bd6212cb54a7239553714ed48ac435.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/y72lq0vh26c4rbpbb192vakj5cpaz1mw-python3.10-radish-bdd-0.16.1
ls -la /nix/store/y72lq0vh26c4rbpbb192vakj5cpaz1mw-python3.10-radish-bdd-0.16.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

9 packages built:

python310Packages.awswrangler
python310Packages.cassandra-driver
python310Packages.gremlinpython
python310Packages.radish-bdd
python311Packages.awswrangler
python311Packages.cassandra-driver
python311Packages.gremlinpython
python311Packages.radish-bdd
terraform-compliance

Maintainer pings
cc @kalbasit for testing.

Result of nixpkgs-review pr 250288 run on x86_64-linux 1

18 packages built:

python310Packages.awswrangler
python310Packages.awswrangler.dist
python310Packages.cassandra-driver
python310Packages.cassandra-driver.dist
python310Packages.gremlinpython
python310Packages.gremlinpython.dist
python310Packages.radish-bdd
python310Packages.radish-bdd.dist
python311Packages.awswrangler
python311Packages.awswrangler.dist
python311Packages.cassandra-driver
python311Packages.cassandra-driver.dist
python311Packages.gremlinpython
python311Packages.gremlinpython.dist
python311Packages.radish-bdd
python311Packages.radish-bdd.dist
terraform-compliance
terraform-compliance.dist


Lost items in the container

Plugin won't restore the container's items, please fix it.

Version?


Dependency on @storybook/api or incompatibility with latest alpha of storybook

Affected design types

[ ] figma
[ ] figspec
[ ] link
[ ] image
[ ] iframe

Describe the bug
I updated Storybook from alpha.49 to alpha.54 (next as of today) and storybook-addon-designs from beta.1 to beta.2 and I got the following error:
✘ [ERROR] Could not resolve "@storybook/api"

    node_modules/storybook-addon-designs/esm/register/index.js:2:29:
      2 │ import { useParameter } from "@storybook/api";
        ╵                              ~~~~~~~~~~~~~~~~

  You can mark the path "@storybook/api" as external to exclude it from the bundle, which will
  remove this error.

✘ [ERROR] Could not resolve "@storybook/api"

    node_modules/storybook-addon-designs/esm/register/containers/Wrapper.js:3:48:
      3 │ import { useParameter, useStorybookState } from "@storybook/api";
        ╵                                                 ~~~~~~~~~~~~~~~~

  You can mark the path "@storybook/api" as external to exclude it from the bundle, which will
  remove this error.

Installing @storybook/api in project as project's own devDependency resolves the problem
How to reproduce the bug?

Install storybook 7.0.0-alpha.49 and storybook-addon-designs 7.0.0-beta.1, check that storybook starts without errors
update storybook to alpha.54 and storybook-addon-designs to beta-2, check that there are errors during start of storybook (storybook dev)

Expected behaviour
There's no need to install @storybook/api in project to make storybook-addon-designs not break storybook dev
After quick bisect it turned out that alpha.54 stopped installing @storybook/api as its dependency
https://github.com/storybookjs/storybook/blob/next/CHANGELOG.md#700-alpha54-november-25-2022
Environment

[ ] Chrome / Chromium / Chromium based browsers
[ ] Firefox
[ ] macOS Safari
[ ] iOS Safari
[ ] Samsung Internet
[X] Other

Affected versions
7.0.0-beta.2
Storybook versions
7.0.0-alpha.54

Oh... that's an uncomfortable breaking change...
I believe there is no way to avoid manually installing @storybook/api:

Changing to @storybook/manager-api breaks v6.x compatibility
Moving @storybook/api into regular dependency would very likely cause a version mismatch problem

I'll update README once Storybook v7.0-beta is shipped.

Maybe you might escalate that to sb team. It's still an alpha so maybe it wasn't intended an/or can be reconsidered?

@jrencz It seems the @storybook/api package has been re-added to the @storybook/manager's dependency list in https://github.com/storybookjs/storybook/pull/20021. Can you try the latest Storybook beta?

@pocka Sorry for the delay - I had some rough time on the project before holidays and I didn't have time to upgrade SB until today.
I tried on 7.0.0-beta.15 and the original problem is gone.
But... there's a new one:
✘ [ERROR] Could not resolve "@storybook/addons"

    node_modules/storybook-addon-designs/esm/index.js:1:38:
      1 │ import { addons, makeDecorator } from "@storybook/addons";
        ╵                                       ~~~~~~~~~~~~~~~~~~~

This one does exist on NPM<EMAIL_ADDRESS>yet it's not being isntalled out of the box with<EMAIL_ADDRESS>There's a warning in readme:
The contents of this package have moved to `@storybook/preview-api` and `@storybook/manager-api`. Please update your import depending on where are are using this API.

This package will no longer be released as part of the 8.0 release of storybook.

Both @storybook/preview-api and @storybook/manager-api come with storybook

I'm one of the Storybook maintainers. I focus primarily on documentation and community outreach. Just wanted to follow up on this issue, letting you know that the Storybook API for building addons is currently being updated to factor in the changes introduced by the upcoming 7.0 release. If you're interested in making the required changes to help the community from benefiting from using your addon, we've prepared an abridged guide for the required changes here, and if you have any questions or issues, please reach out to us in the #prerelease channel in our Discord Server.
Hope you have a great day!
Stay safe

By the end of the week I will check what I have now (last time I updated it was beta.19) and confirm if that problem still exists. And if it does I'll try bumping to beta.25

At the time I wrote https://github.com/pocka/storybook-addon-designs/issues/178#issuecomment-1365765087 and so far in my setup it looks like that:

I have<EMAIL_ADDRESS>which requires @storybook/addons
<EMAIL_ADDRESS>has peerDependency of "@storybook/addons": "^6.4.0 || ^7.0.0"
back then I resolved the problem by adding @storybook/addons as devDependency of my project

and it worked.
Now I removed explicit dependency on @storybook/addons. Npm moved @storybook/addons to node_modules/msw-storybook-addon/node_modules/@storybook/addons and error came back
Then I removed and added back msw-storybook-addon which fixed the structure of my node_modules - now @storybook/addons is at node_modules/@storybook/addons and it works once again, yet now I have<EMAIL_ADDRESS>because msw-storybook-addon wants ^6.0.0.
I suppose it now works purely be accident - because I use msw-storybook-addon and it's that one which allows<EMAIL_ADDRESS>to work without problem.
I hope to have some more time to try beta.25 later - maybe something that comes with it (or with @storybook-addon-essentials which it's probably save to assume vast majority uses) brings back @storybook/addons

@pocka thanks for following up with me on this. Appreciate it 🙏 ! Glad that everything is already being already working with the new API, should any issue arise, don't hesitate to reach out to us via our Discord Server or the issue tracker.
Hope you have a great day.
Stay safe

As a followup to my previous comment https://github.com/pocka/storybook-addon-designs/issues/178#issuecomment-1379991622
I now tried updating storybook from 7.0.0-beta.19 to 7.0.0-beta.25 and in beta.25 there's still nothing in either storybook or @storybook/addon-essentials which would require @storybook-addons. it's still msw-storybook-addon which is the only thing in my case that requires @storybook-addons and I still have<EMAIL_ADDRESS>It satisfies peerDependency of storybook-addon-designs, but was it not for the fact that I do have msw-storybook-addon, I'd not have it installed and
✘ [ERROR] Could not resolve "@storybook/addons"

    node_modules/storybook-addon-designs/esm/index.js:1:38:
      1 │ import { addons, makeDecorator } from "@storybook/addons";
        ╵                                       ~~~~~~~~~~~~~~~~~~~

would be back.
To my knowledge storybook-addon-designs should have @storybook/addons as dependency, not peerDependency

I was getting the same error
Could not resolve "@storybook/addons"

I resolved it with
npm i -D @storybook/addons

(I spun up a Stackblitz with the storybook-addon-designs dependency. Stackblitz is picky and insisted on adding several additional dependencies. Adding them all locally fixed it. Narrowed it down from there.)
I'm on Storybook (and @storybook/... things) 7.0.0-beta.30 and storybook-addon-designs 7.0.0-beta.2.
@jrencz I wonder if your trouble comes from mixing @storybook/addons 6 with Storybook 7.

@olets Thanks for your input. It might not be clear: I don't have any problem if I have<EMAIL_ADDRESS>I'm pointing out that I have any version purely because I have some other addons, msw addon in my case. In case I didn't use that one then error would appear and I would have done what you suggested: install storybook/addons as dependency of my project (where my project does not import from storybook/addons)
Designs addon does depend on API from package @storybook/addons and I want to point out that that package should be a dependency, not peerDependency

that package should be a dependency, not peerDependency

No. While using peerDependencies in this case is semantically incorrect, it's required to avoid version conflict problems (e.g. both<EMAIL_ADDRESS>and<EMAIL_ADDRESS>exists and singleton or something does not work).
In an ideal world, package managers should pick/resolve the correct versions of Storybook libs even they are listed as direct dependencies. Unfortunately package managers most of the times failed to resolve to a version user installed. This is why it's peerDependencies IIRC. I'm not sure the situation changed or not.

(I spun up a Stackblitz with the storybook-addon-designs dependency. Stackblitz is picky and insisted on adding several additional dependencies. Adding them all locally fixed it. Narrowed it down from there.)

I believe Stackblitz being strict instead of picky. Installing them locally is the reliable solution and a workaround for now.

@pocka thanks for the link. I studied that repo and now I know a little more
It's even mentioned explicitly in https://storybook.js.org/docs/react/addons/writing-addons#packaging-and-publishing (and same in docs for upcoming 7.0) but the storybook-addon-outline given as a reference in that section uses @storybook/addons as dependency.
It was set to ^6.0.0 via https://github.com/chromaui/storybook-addon-outline/pull/6/files
My assessment is that the guideline might not yet have been revised for the dependency structure of @storybook/addon-essentials@next, which at beta.30 does not come with @storybook/addons. It stopped at https://github.com/storybookjs/storybook/pull/19952 in alpha.54, where<EMAIL_ADDRESS>does come with @storybook/addons as dependency and therefore having it as peerDependency in an addon, even if it's a 3rd part addon like this one does actually make sense.

Hi Everyone! We have released a new version of the addon. We also changed the package name for the addon, @storybook/addon-designs. Please follow instructions from the readme to get going with the latest version.
https://github.com/storybookjs/addon-designs/blob/master/README.md


Add Request page - Multiple modal issue on state change from dropdown

Description:
This task is about an existing tech debt in the FOI Add Request page.
Scenario:
While creating a new request, try to change the dropdown from Unopened to Intake in Progress state and try to cancel the state change. The expected behavior is to close the modal without any state change but instead the same modal pops up again.
Impact of this bug : Medium impact
Steps to Reproduce
Steps to reproduce the behavior:

Login as IAO user, click on Add Request button
Fill in all required fields
Click on status dropdown, select Intake in progress
Try to cancel or close the modal without saving any state change.

Actual/ observed behaviour/ results
The same modal pops up again.
Expected behaviour
The modal should close without any state change.
This bug can be related to #1349. So who ever takes this bug can take up #1349 as well.
[Uploading... Add Request-issue.webm]

@jadmsaadaot, can you please add an estimate to this ticket.

@lmullane done.


Remove directory breadcrumbs from Object UFS

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/15220/
Test PASSed.


Delivery Failures

The number off users not getting posted messages from CC, is steadily increasing. At first, I was ok with 11 failures and 22,071 successful. But, the number keeps rising and now is creeping towards 50:

Would deleting the UserData table from DataStorage (Azure>Storage Accounts) - regenerate and fix the issue?

Just would like confirmation that deleting the UserData table, will not break anything!
Any advice greatly appreciated.

Hi @MNL79 We generally do not delete the userdata table. Instead we delete the entries only for users which are not getting messages by searching the user ID. you can get the User ID for failed users from exported excel of Company communicator

Hi - I can see the users where it is failing (by exporting the delivery report in the Authors app), but I have one user that got the very first messages sent to All Users - but has never received one since.
Is the 'Export detailed results' from sent messages, what you are meaning when searching for the user ID? Or is this in Azure App Services or Storage Browser?

Hi @MNL79,  by the 'Export detailed results' from sent messages I mean the same delivery report in the author app that you would be reading for failures error message.

Hi @MNL79, by the 'Export detailed results' from sent messages I mean the same delivery report in the author app that you would be reading for failures error message.

That's fine - I can see that and that is what I've been looking at.
I've deleted the users that had failures or other issues from the UserData table - they have not reappeared, I'm assuming that when a new all company message is sent - the app will, at the point, resync all users and then the users deleted will appear? And hopefully will be successful this time.

Correct @MNL79.

@MNL79 ,
Could you please update us the status of the issue?

Hi @MNL79
Could you please update us on the status of the issue?

Pleased to report, that going in and deleting all the users where it failed - then worked for the next message sent. Went from 44 failures, down to a nearly perfect 1.

Hi @MNL79
We believe issue got resolved could you please let us know if there are any other queries
if issue is resolved please let us know so we can mark ticket as complete

Deletion of AAD IDs/users with failures resolved the issue. On the next message sent, the app synched users up again and was successful this time.


Not passing the test cases when it actually does

Challenge Seek and Destroy has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
function filterOut(currentValue) {
  return currentValue !== this;
}

function destroyer(arr) {
  // store the arguments into a variable for easier readability
  var args = Array.from(arguments);
  for (var i = 1; i <= args.length; i++) {
    arr = arr.filter(filterOut, args[i]);
  }
  return arr;
}

destroyer([3, 5, 1, 2, 2], 2, 3, 5);

To reproduce: simply copy and paste my code.
Case 1:
destroyer([1, 2, 3, 1, 2, 3], 2, 3);
should return [1, 1]

Using my code, the console outputs [1, 1] BUT DOES NOT PASS the test case.

If I replace the last line of the function
"return arr;" with "return [1, 1];", the console outputs [1, 1] and passes the test case.

No still on this way...
On Mar 3, 2017 22:03, "Aaron Dwayne Gebana"<EMAIL_ADDRESS>wrote:

Challenge Seek and Destroy
https://www.freecodecamp.com/challenges/seek-and-destroy#?solution=function filterOut(currentValue) {
  return currentValue !%3D%3D this%3B
}

function destroyer(arr) {
  %2F%2F store the arguments into a variable for easier readability
  var args %3D Array.from(arguments)%3B
  for (var i %3D 1%3B i <%3D args.length%3B i%2B%2B) {
    arr %3D arr.filter(filterOut%2C args[i])%3B
  }
  return arr%3B
}

destroyer([3%2C 5%2C 1%2C 2%2C 2]%2C 2%2C 3%2C 5)%3B

has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to
screenshots if possible.
My code:
function filterOut(currentValue) {
return currentValue !== this;
}
function destroyer(arr) {
// store the arguments into a variable for easier readability
var args = Array.from(arguments);
for (var i = 1; i <= args.length; i++) {
arr = arr.filter(filterOut, args[i]);
}
return arr;
}
destroyer([3, 5, 1, 2, 2], 2, 3, 5);
To reproduce: simply copy and paste my code.
Case 1:
destroyer([1, 2, 3, 1, 2, 3], 2, 3);
should return [1, 1]
[image: screenshot1]
https://cloud.githubusercontent.com/assets/25548418/23576225/4ee9af90-00da-11e7-95cd-adde19326a60.png

Using my code, the console outputs [1, 1] BUT DOES NOT PASS the test
case.
[image: screenshot2]
https://cloud.githubusercontent.com/assets/25548418/23576226/5e23d026-00da-11e7-84f9-32859a5cb513.png
If I replace the last line of the function
"return arr;" with "return [1, 1];", the console outputs [1, 1] and
passes the test case.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/13732, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AQkShljgnBVwi9ET6BTCPhhwRhFKuVEmks5riPCFgaJpZM4MS-oY
.

Interesting. I'm getting a similar issue; however, I completed this challenge a while back and was able to solve it. Will update shortly.

function destroyer(arr) {
// Remove all the values
for(var i = 1; i < arguments.length; i++){
arr = arr.filter(function(val){return val != this;}, arguments[i]);
}
console.log(arr);
return arr;
}
passed test
destroyer([1, 2, 3, 1, 2, 3], 2, 3);

function destroyer(arr) {
  // Remove all the values
  for(var i = 1; i < arguments.length; i++){
    arr = arr.filter(function(val){return val != this;}, arguments[i]);
  }
  console.log(arr);
  return arr;
}

destroyer([1, 2, 3, 1, 2, 3], 2, 3);

passe test

function destroyer(arr) {
  // Remove all the values
  for(var i = 1; i < arguments.length; i++){
    arr = arr.filter(function(val){return val != this;}, arguments[i]);
  }
  console.log(arr);
  return arr;
}

destroyer([1, 2, 3, 1, 2, 3], 2, 3);

passed test

@saksoy
Please do not post your solution on here. You could help people at FreeCodeCamp Chat Room or Forum. GitHub Issues are for reporting bugs on the website only.
Happy Coding!


[VL] quick fix for static build git conflict

What changes were proposed in this pull request?
not necessary to install git236
How was this patch tested?
pass GHA

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_3971_time.csv
log/native_master_12_07_2023_9c5314fd5_time.csv
difference
percentage

q1
33.53
33.97
0.438
101.31%

q2
25.14
24.95
-0.195
99.23%

q3
38.78
37.91
-0.873
97.75%

q4
36.65
37.39
0.745
102.03%

q5
70.69
71.30
0.610
100.86%

q6
7.12
5.38
-1.740
75.56%

q7
83.29
85.81
2.521
103.03%

q8
88.26
85.80
-2.461
97.21%

q9
124.17
123.51
-0.659
99.47%

q10
43.48
45.87
2.388
105.49%

q11
21.19
20.29
-0.901
95.75%

q12
27.88
26.73
-1.155
95.86%

q13
46.81
45.73
-1.073
97.71%

q14
16.75
16.69
-0.056
99.66%

q15
28.91
28.46
-0.447
98.45%

q16
15.38
15.56
0.173
101.13%

q17
102.42
103.37
0.952
100.93%

q18
148.89
149.01
0.127
100.09%

q19
12.91
12.84
-0.069
99.47%

q20
27.26
27.78
0.519
101.90%

q21
222.52
223.73
1.215
100.55%

q22
13.14
13.39
0.251
101.91%

total
1235.16
1235.47
0.310
100.03%


[FancyZones] Refactor Zone class

Summary of the Pull Request
What is this about?
Pass zoneId on zone creaton and make it const
Refactor IZone and Zone - move static methods to anonymous namespace and make methods const
Remove SetId
PR Checklist

[x] Applies to #7049
[x] CLA signed. If not, go over here and sign the CLA
[x] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Validation Steps Performed
How does someone test & validate?
Tested manually

Now zone numbers don't appear in the same order as they used to, for example, with the grid layout with 8 zones, the numbers are
8 6 4 2
7 5 3 1

Now zone numbers don't appear in the same order as they used to, for example, with the grid layout with 8 zones, the numbers are
8 6 4 2
7 5 3 1

Ah, right. One change slipped in from cumulative bigger change. I'll fix it. Thanks

what needs to happen to get this merged in?

Let's add some more context to the PR since some changes are not self-explanatory and then let's merge it.


os-config.yml: fix the wrong command-volumes configuration

when running command /usr/bin/ros, it will get the following
fatal message:
"Failed to find an entry point for /usr/bin/ros".
The same as the command /usr/sbin/rancherctl /sbin/netconf etc.
This patch fix that, and make it the same sequence as the registerCmd
function in main.go file.
Signed-off-by: Wang Long<EMAIL_ADDRESS>

Hmm.  Are you saying that the order of the bind mounts must match registercmd?  Does that fix something?

It's not the order. We've got /usr/sbin/ros in main.go and /usr/bin/ros in os-config.yml
Running /usr/bin/ros (by full path) gives an error, because the full path registered in main.go is different.

@datawolf Thanks!
LGTM


Minify JS issues

When you minify the Javascript on the latest beta (handlebars.1.0.0.beta.3.js) there are errors due missing brackets.

This is fixed in master.


Fix reported line numbers

Fixes #128. And also able to pass #129.
 6:  const Button2 = styled.button.attrs({
 7:    type: 'normal'
 8:  })`
 9:    display: block;
10:    ${
11:       props => props.isHovering && interpolatedStyle
12:    }
13:  color: ${color};
14:    background: blue;
15:  `

Current codes try to generate source map from processedNode.loc.start.line, which is line 6. But it should be line 8.
If the interpolation contains multiply lines, we should make sure it is substituted by same count of lines.

Changes Unknown when pulling 0760875ca704ed3dc7eff790457e67c525965cce on chinesedfan:fix_lineno into ** on styled-components:master**.

At a glance it looks pretty cool, I'll have to take a bit more time later to look into the code more thoroughly though, but for one, since you say it passes #129 what about we just copy paste that test case into this PR then? :). The more tests the better!

@emilgoldsmith I just added some unit tests in this PR, but tested locally with #129. My idea is that merging this PR first, and #129 later. After all, #129 belongs to another author. Waiting for your review feedbacks. :)

My idea is that merging this PR first, and #129 later. After all, #129 belongs to another author.

Yeah sure, that's very respectful and makes sense :)

@emilgoldsmith Sorry for my late responses. I am busy these days, so I leave some comments to you first. This feature is really important and I think I will implement it finally. :)

Yes it is :)

Coverage increased (+0.02%) to 99.66% when pulling cbfb31650e7bcf4bac0b42ff3bd74af907d49abc on chinesedfan:fix_lineno into b864ff30464f16c1366fd81af06e939c038548c0 on styled-components:master.

@emilgoldsmith /* stylelint-disable-line */ can only solve problems in comment nodes. I update with a new strategy that recording all interpolation lines first and filtering indentation warnings in those lines.

Coverage increased (+0.02%) to 99.659% when pulling 088e9860c405e6140185f69dc8aa497e8da89f4b on chinesedfan:fix_lineno into b864ff30464f16c1366fd81af06e939c038548c0 on styled-components:master.

@emilgoldsmith Comments mentioned above have been handled. I gave up renaming the variable because naming is really the hardest problem in programming. The current interpolationLines is not so bad.

Coverage increased (+0.02%) to 99.663% when pulling 14d313ee134ee24728df6cf379bf00a00ecddb5a on chinesedfan:fix_lineno into b864ff30464f16c1366fd81af06e939c038548c0 on styled-components:master.

@emilgoldsmith Haha, my Github graph doesn't matter. You can simply select "squash and merge". Thanks for your sweet reviews during these days!

No problem haha!
Actually "squash and merge" isn't enabled for this repo, so yeah if you find time to squash it at any point we can merge it right in :)

@emilgoldsmith I rebased and squashed as 3 commits.

Coverage increased (+0.02%) to 99.663% when pulling ca14148c806b3614b98625708b05078ff9742a42 on chinesedfan:fix_lineno into b864ff30464f16c1366fd81af06e939c038548c0 on styled-components:master.

Awesome. Thanks again for the hard work and several revisions! This is a nice addition to the repo :)

@emilgoldsmith Last question, what's the publish strategy of this repository? I want to know when I can use the version with this fix. 😄

I'll publish it right now :). No defined strategy, more like the three publishers publish whenever they see fit / new changes are merged in

Done :). Update to 1.2.0 and you'll have your changes

Great! I will upgrade it in my project and keep observing.


Fix bug in close name checks

whoops!

Without this, it's telling users who only post their name#discrim that they're "close but incorrect", even though it's not even remotely close.

I love writing consistent code
and having consistent variable names


FR: Add a comment for those which need polyfill.

All of these features that need a ployfill, should have a comment once transpiled.
For example:
[ ... documnet.querySelectorAll('*') ];

"use strict";

// Requires Array.from ployfill, please require("6to5/polyfill");
var _toArray = function (arr) { return Array.isArray(arr) ? arr : Array.from(arr); };

[].concat(_toArray(documnet.querySelectorAll("*")));

Or something similar.

There already is.

I think I didn't put it in a right way, I'm aware of the cavets link, bit wouldn't be easier if the transpiled code had a comment? At least in the REPL ?


how to save svm model  data and resuse it ?

SVM(Multi) calculation consumes memory and time, so I want to save the model calculation data for subsequent calls, but it seems that SVM does not support the serde feature. How should I save the SVM model data?

@coolstudio1678 As a workaround, you could implement your own version of MultiTargetModel with generic types instead of dynamic dispatch and derive serde's traits to it. That's what I've done and it at least works.

thanks!


Bitfinex live trade crash

I created the conf.js and simulated, all works fine.
The when I want to trade live I use the following command and get the error below:

zenbot trade
...
---------------------------- STARTING LIVE TRADING ----------------------------
2017-06-15 23:28:00  2358.70 BTC-USD   -0.5%      220      ++      -0.93%      buy  0.00000 BTC  1345.42 USD    +0.0%   +0.5%
2017-06-15 23:28:29  2355.70 BTC-USD   -0.1%       63      ++      -0.80%   buying  0.00000 BTC  1345.42 USD    +0.0%   +0.6%
D:\Software\Zenbot\zenbot-master\extensions\exchanges\bitfinex\exchange.js:139
if (body.is_live === true) {
^
TypeError: Cannot read property 'is_live' of undefined
at D:\Software\Zenbot\zenbot-master\extensions\exchanges\bitfinex\exchange.js:139:17
at Request.error1 [as _callback] (D:\Software\Zenbot\zenbot-master\node_modules\bitfinex-api-node\rest.js:61:14)
at Request.self.callback (D:\Software\Zenbot\zenbot-master\node_modules\request\request.js:188:22)
at emitTwo (events.js:106:13)
at Request.emit (events.js:191:7)
at Request. (D:\Software\Zenbot\zenbot-master\node_modules\request\request.js:1171:10)
at emitOne (events.js:96:13)
at Request.emit (events.js:188:7)
at IncomingMessage. (D:\Software\Zenbot\zenbot-master\node_modules\request\request.js:1091:12)
at IncomingMessage.g (events.js:292:16)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:974:12)
at _combinedTickCallback (internal/process/next_tick.js:80:11)
at process._tickCallback (internal/process/next_tick.js:104:9)

I can see that zenbot is able to get the correct balance from my Bitfinex account, so the API key/secret is correct. Its when it starts "buying" that there is an error.

That is already corrected, though "masters" are slow to merge it.

https://github.com/carlos8f/zenbot/pull/288


Internal types are broken

Because of the move to teeny-request in @google-cloud/common, internal types are now slightly broken.

I have PR #740 to address this.


No data for states of India staring 3/31

Location, date, and short issue description

Source

File

Issue details

Snippet/screenshot
<!-- If you can, please include a snippet of the file here, or a screenshot, to help us find it.-->

Additional context

Can consider scraping - https://www.covid19india.org/ where the information about every state is updated every few hours

Fixed in the latest data. Please re-open if there is an issue.
https://github.com/covidatlas/coronadatascraper/issues/686 We're still missing GeoJSON for:
❌ Could not find location Ladakh, iso1:IN
❌ Could not find location Telengana, iso1:IN
https://github.com/covidatlas/coronadatascraper/issues/687 Missing population data for:
❌ Arunachal Pradesh, iso1:IN: ?
❌ Assam, iso1:IN: ?
❌ Jharkhand, iso1:IN: ?


Dictionary contains method returning false for a key when dictionary content is generated by set method

When I'm setting the dictionary content from set method (passing a hash map ), I can see all the keys that I've provided in hash map from getKeys method. However, when I check the key in dictionary using contains method, I'm getting False.

Hi @hrajput89,
Could you please specify the version number. And could you please provide the code snippet?

@hrajput89 , please update!

the method for which I logged the issue is no longer available in Document API.  Hence closing the ticket


Testing on views doesn't seem to work for Dask

Since this unit test compares hashes but not content, it seems to fail. Meanwhile, I used assert_equal to show it works as intended.

https://docs.dask.org/en/stable/changelog.html
Could this get a bit more investigation? It's not obvious to me if this is fine to change. Hopefully we are not propagating some change into the original dask array, which is what this test is meant to check

The dask array hash changes after the first copy call for some reason. I opened this issue https://github.com/dask/dask/issues/10240.
The tests seem to be fine though if we do a dummy copy call before getting the hash


much old projects not use AndroidX, so this cause my local project build falied

🐛 Bug Report

Expected behavior
Reproduction steps
Configuration
Version: 1.x
Platform:

[ ] :iphone: iOS
[ ] :robot: Android

Simply upgrade. Closing this issue since no additional information, no suggestions and not being constructive.


Retry issues caused by dns resolution

Environment details

Specify the API at the beginning of the title. biquery
OS type and version: MacOS
Java version: 1.8
bigquery version(s): 1.117.1

Steps to reproduce
Configuring retrying exceptions, in case of an error during dns resolution on http GRPC API, the exception does not seems to retry. Google Extensions for java consider this a not retry case. The api does not seem to allow retry under errors of this sort:
 stacktrace: com.google.cloud.bigquery.BigQueryException: www.googleapis.com\n\tat com.google.cloud.bigquery.spi.v2.HttpBigQueryRpc.translate(HttpBigQueryRpc.java:113)\n\tat com.google.cloud.bigquery.spi.v2.HttpBigQueryRpc.create(HttpBigQueryRpc.java:213)\n\tat com.google.cloud.bigquery.BigQueryImpl$5.call(BigQueryImpl.java:327)\n\tat com.google.cloud.bigquery.BigQueryImpl$5.call(BigQueryImpl.java:324)\n\tat

Is there any option to retry this exceptions, could this be added as a feature as the gax retry api is internal to the client.
Thank you for your help.

The BigQuery client uses gax-java for retrying. Hence, transferring this ticket to gax-java for triaging.


Show Notes ⚡📻 3/1 @ Santa Monica - Pivotal Labs

Stand up

🍜  Eat lunch with us with @jsla https://github.com/jsla/lunch.js/issues - now in the SF Valley thanks to Fullstack member @remarks, Culver City x Playa Vista with @machikoyasuda and @jarrettch, and other locations: Downtown LA, Downtown Santa Monica.

Open source meets UCLA, thanks to @gr2m: https://github.com/welcome-to-open-source/ucla#open-source-projects-and-issues-for-new-contributors

⭐ This week's picks

🎵 Rad open project of the month: Ukulele chords by @jdobrowner + @mzarako https://jdobrowner.github.io/learn-ukulele/ at https://github.com/jdobrowner/learn-ukulele using https://github.com/Tonejs/Tone.js/
🗺 Rad project from meetup fam @codelaboc: Stormwater Data Challenge map https://codelaboc.github.io/CA-Stormwater-Data-Challenge/

📺 Tonight's show
Did you know many LA companies have their own open source projects you can use and contribute to?

Fullscreen, Playa Vista: https://github.com/Fullscreen/yt
Dollar Shave Club, Playa Vista: https://github.com/dollarshaveclub/
Liferay, Diamond Bar: Senna.js: https://github.com/liferay/senna.js

First Time? Begin here:

For your first Pull Request @ Fullstack: https://github.com/fullstackla/pairing-meetup/blob/master/community/README.md
For coding puzzles: Join our Exercism team: http://exercism.io/teams/dtla-pair-programming/streams

Attendees:

Meetup Page: https://www.meetup.com/la-fullstack/events/237937106/

@kpearson
@dorachan2000

In Progress:
Pull Requests:
Retro:
Made at Fullstack :zap:

some links to add from last week in LA's open source world:

https://welcome-to-open-source.github.io/ucla/

some places to look for new issues in the LA open source world:

js https://github.com/reactioncommerce/reaction/issues

Exercisms to check out and nitpick:

hello world in clojure by @blackcathacker http://exercism.io/submissions/8dbf266ed780417c8b51d3979f164132

check out the latest Ruby auto-nitpick on @kpearson's latest submission
http://exercism.io/submissions/ba352d6f3b9b40e5ac95cbffb1f67a86

Are you in our Exercism team? http://exercism.io/teams/dtla-pair-programming/streams

cool project of the month: https://jdobrowner.github.io/learn-ukulele/

check out the latest @Hoodiehq newsletter! i spy @xuhdev @Taekyoon @jimthoburn and others: http://us4.campaign-archive1.com/?u=12d36bbe9418ed6a43127cd62&id=96f23dea01&e=e5b554431f


the 'total blocked today' goes down as well as up ?

Problem/Motivation
I notice that the 'total blocked today' both in the web page and home assistant sensor, goes down as well as up, there doesnt seem to be an explanation for this.

(Why the issue was filed)
i dont undestand why it goes down, the title suggests it increments

Expected behavior
i expected it to increment in the day and then reset at midnight
Actual behavior
it goes down as well as up
Steps to reproduce
just watch it or look at the home assistant history for the sensor

(How can someone else make/see it happen)
add 'Pi-Hole Ads Blocked Today' sensor to home assistant then look at its history

Proposed changes
explain why it is a fluctuating figure, rename the title or fix it so it increments

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

It shows the number of ads blocked the last 24 hours... (it shifts)


chore: use pre-commit hooks for chartpress --reset

Add support for running chartpress --reset as a git pre-commit hook using the pre-commit package.
To try it out:
pipenv install --deploy
pipenv run pre-commit install
pipenv run pre-commit run chartpress

Trying to commit a modified chart value that is handled by chartpress results in
git commit -am 'commiting woop'
black................................................(no files to check)Skipped
Flake8...............................................(no files to check)Skipped
chartpress reset.........................................................Failed
hookid: chartpress

Files were modified by this hook. Additional output:

$> git log -n 1 --pretty=format:%h -- . . jupyterhub singleuser
$> git log -n 1 --pretty=format:%h -- . chartpress.yaml
$> git log -n 1 --pretty=format:%h -- jupyterhub jupyterhub chartpress.yaml
$> git log -n 1 --pretty=format:%h -- git-clone git-clone chartpress.yaml
Updating helm-chart/renku-notebooks/values.yaml: image: {'repository': 'renku/renku-notebooks', 'tag': 'latest'}
Updating helm-chart/renku-notebooks/values.yaml: jupyterhub.hub.image: {'repository': 'renku/jupyterhub-k8s', 'tag': 'latest'}
Updating helm-chart/renku-notebooks/values.yaml: git_clone.image: {'repository': 'renku/git-clone', 'tag': 'latest'}

As far as I understood, this prevents unintentional modifications to the Chart.yaml and values.yaml files. If so, then it LGTM. One point though is what if we want to make changes to these files?
Also, pre-commit uses python3.7 which I don't have on my machine. I tried with python3 but then black complains. I had to change .pre-commit-config.yaml to use python3.6. This works but is a bit inconvenient and it would be good if there is a solution to that.

Aha thanks, I wasn't aware of the python version issue. I'll dig a bit in the docs.

One point though is what if we want to make changes to these files?

chartpress will only modify the image object of the parts of the chart that it controls (and the version in Chart.yaml). So in this case it's jupyterhub.image, git-clone.image and image (for the notebooks service itself). All the other parts of these files should remain unmodified and unaffected.

@mohammad-sdsc sorry I haven't had a chance to look into the python version problem - did you solve it?

Not really, I change the version to 3.6 on my system and revert it back later. It makes more sense to set it at 3.6 because that's the minimum version requirement for renku.

Oh now I see it - I didn't realize that was the requirement set for black. I'm pretty sure it doesn't need to be that way. I just pushed a change that removes that line,

This does not work on my system (Debian Linux) and gives me this error:
[INFO] Installing environment for https://github.com/ambv/black.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
An unexpected error has occurred: CalledProcessError: Command: ('/home/mohammad/.cache/pre-commit/repo3x91u4nj/py_env-python3/bin/python3', '/home/mohammad/.cache/pre-commit/repo3x91u4nj/py_env-python3/bin/pip', 'install', '.')
Return code: 1
Expected return code: 0
Output:
    Processing /home/mohammad/.cache/pre-commit/repo3x91u4nj
      Installing build dependencies: started
      Installing build dependencies: finished with status 'done'
      Getting requirements to build wheel: started
      Getting requirements to build wheel: finished with status 'error'

Errors:
      ERROR: Complete output from command /home/mohammad/.cache/pre-commit/repo3x91u4nj/py_env-python3/bin/python3 /home/mohammad/.cache/pre-commit/repo3x91u4nj/py_env-python3/lib/python3.5/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmp4oh3d__3:
      ERROR: Traceback (most recent call last):
        File "/home/mohammad/.cache/pre-commit/repo3x91u4nj/py_env-python3/lib/python3.5/site-packages/pip/_vendor/pep517/_in_process.py", line 207, in <module>
          main()
        File "/home/mohammad/.cache/pre-commit/repo3x91u4nj/py_env-python3/lib/python3.5/site-packages/pip/_vendor/pep517/_in_process.py", line 197, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/home/mohammad/.cache/pre-commit/repo3x91u4nj/py_env-python3/lib/python3.5/site-packages/pip/_vendor/pep517/_in_process.py", line 54, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/tmp/pip-build-env-6c1m3az6/overlay/lib/python3.5/site-packages/setuptools/build_meta.py", line 145, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
        File "/tmp/pip-build-env-6c1m3az6/overlay/lib/python3.5/site-packages/setuptools/build_meta.py", line 126, in _get_build_requires
          self.run_setup()
        File "/tmp/pip-build-env-6c1m3az6/overlay/lib/python3.5/site-packages/setuptools/build_meta.py", line 234, in run_setup
          self).run_setup(setup_script=setup_script)
        File "/tmp/pip-build-env-6c1m3az6/overlay/lib/python3.5/site-packages/setuptools/build_meta.py", line 141, in run_setup
          exec(compile(code, __file__, 'exec'), locals())
        File "setup.py", line 7, in <module>
          assert sys.version_info >= (3, 6, 0), "black requires Python 3.6+"
      AssertionError: black requires Python 3.6+
      ----------------------------------------
    ERROR: Command "/home/mohammad/.cache/pre-commit/repo3x91u4nj/py_env-python3/bin/python3 /home/mohammad/.cache/pre-commit/repo3x91u4nj/py_env-python3/lib/python3.5/site-packages/pip/_vendor/pep517/_in_process.py get_requires_for_build_wheel /tmp/tmp4oh3d__3" failed with error code 1 in /tmp/pip-req-build-ocdf7opo

My system's Python version is 3.5 but on pipenv it's 3.6.
BTW, this was working when the python 3.6 line was there.

ok I see - so we need the language_version: python3.6 in there.

Or maybe just python3?

python3 won't work either and gives the same error message.

Feel free to merge this!


Configuration for 'cds.requires.cds.xt.SaasProvisioningService' lacks mandatory property 'kind' or 'impl'

Hi Colleague,
We are just migrating from mtx to mtxs tool. We have maintained
"cds.xt.ModelProviderService": true,
"cds.xt.SaasProvisioningService": true,
"cds.xt.DeploymentService": true
in our .cdsrc.json file but during deployment, we are getting error "Configuration for 'cds.requires.cds.xt.SaasProvisioningService' lacks mandatory property 'kind' or 'impl'".
Not sure what is the cause. Could you please help us here in resolving this issue.
We can discuss the more details in our internal team chat/call.
Best Regards
Krishan Raheja

Hi Krishan, I think you confused cds-mtx and mtx-tool. There is no such things as mtxs-tool. This tool works with both cds-mtx and cds-mtxs.  For cds-mtx(s) related problems, you can open a related cap issue at: https://github.tools.sap/cap/issues/issues

Thanks Richard,
I have posed the issue in CAP repo.


chore(deps): Bump h2database from 1.4.200 to 2.0.206

This pipeline will still not pass since protobuf version is not raised. Is the fix for log4j not in 2.17.1?


@AutoOpen/@AsyncOpen Do not support setting a default configuration

How frequently does the bug occur?
Always
Description
In my app, I have a few views that are not yet updated to SwiftUI. I am relying on using defaultConfiguration so that I do not have to pass a configuration all around the app.
In an effort to try and bring what SwiftUI views we DO have up to spec, we are attempting to copy the SwiftUI Examples in realm-template-apps.
However, it seems that when we set a defaultConfiguration, AutoOpen and AsyncOpen don't even bother opening a subscription.
I have re-created this in the example app by simply setting the default configuration via a function in content view.
Additionally, even if you remove the setting of default config and relaunch the app, the issue seems to remain until a full uninstall and re-install of the application.
Stacktrace & log output
Successfully logged in user: <RLMUser: 0x600000ab51a0>
2023-02-27 16:54:21.818213-0600 App[66337:11573598] Sync: Connection[3]: Session[3]: client_reset_config = false, Realm exists = true, client reset = false
2023-02-27 16:54:21.862365-0600 App[66337:11573598] Sync: Connected to endpoint '<IP_ADDRESS>:443' (from '<IP_ADDRESS>:52756')
2023-02-27 16:54:22.068117-0600 App[66337:11573598] Sync: Connection[3]: Connected to app services with request id: "63fd349ecb2b0bf3e0cfd754"
2023-02-27 16:54:22.232938-0600 App[66337:11573598] Sync: Connection[3]: Session[3]: Begin processing pending FLX bootstrap for query version 0. (changesets: 1, original total changeset size: 133)
2023-02-27 16:54:22.238601-0600 App[66337:11573598] Sync: Connection[3]: Session[3]: Integrated 1 changesets from pending bootstrap for query version 0, producing client version 8 in 4 ms. 0 changesets remaining in bootstrap
2023-02-27 16:54:26.226114-0600 App[66337:11573466] *** Terminating app due to uncaught exception 'RLMException', reason: 'Cannot write to class Item when no flexible sync subscription has been created.'
*** First throw call stack:
(
	0   CoreFoundation                      0x000000018040e7c8 __exceptionPreprocess + 172
	1   libobjc.A.dylib                     0x0000000180051144 objc_exception_throw + 56
	2   App                                 0x0000000100b0bc08 _ZN18RLMAccessorContext12createObjectEP11objc_objectN5realm12CreatePolicyEbNS2_6ObjKeyE + 2500
	3   App                                 0x0000000100c06a50 RLMAddObjectToRealm + 244
	4   App                                 0x0000000100eeaf68 $s10RealmSwift0A0V3add_6updateySo0aB6ObjectC_AC12UpdatePolicyOtF + 868
	5   App                                 0x0000000100f2835c $s10RealmSwift15BoundCollectionPAASo0aB6ObjectC7ElementRczAA7ResultsVyAGG5ValueRtzrlE6appendyyAGFyAJXEfU_ + 872
	6   App                                 0x0000000100f11f88 $s10RealmSwift5write33_06F2B43D1E2DA64D3C5AC1DADA9F5BA7LLyyx_yxXEtAA14ThreadConfinedRzlFyyXEfU_ + 72
	7   App                                 0x0000000100f4d6e8 $s10RealmSwift5write33_06F2B43D1E2DA64D3C5AC1DADA9F5BA7LLyyx_yxXEtAA14ThreadConfinedRzlFyyXEfU_TA + 48
	8   App                                 0x0000000100ee9b8c $s10RealmSwift0A0V5write16withoutNotifying_xSaySo20RLMNotificationTokenCG_xyKXEtKlF + 320
	9   App                                 0x0000000100f11e44 $s10RealmSwift5write33_06F2B43D1E2DA64D3C5AC1DADA9F5BA7LLyyx_yxXEtAA14ThreadConfinedRzlF + 1024
	10  App                                 0x0000000100f26864 $s10RealmSwift15BoundCollectionPAAE5write33_06F2B43D1E2DA64D3C5AC1DADA9F5BA7LLyyy5ValueQzXEAA14ThreadConfinedAGRQrlF + 284
	11  App                                 0x0000000100f27fe0 $s10RealmSwift15BoundCollectionPAASo0aB6ObjectC7ElementRczAA7ResultsVyAGG5ValueRtzrlE6appendyyAGF + 148
	12  App                                 0x0000000100af7c40 $s3App14CreateItemViewV4bodyQrvg7SwiftUI05TupleD0VyAE7SectionVyAE4TextVAE0J5FieldVyAKGAE05EmptyD0VG_AIyApGyAE6ButtonVyAE6HStackVyAGyAE6SpacerV_AkWtGGG_AZtGAPGtGyXEfU_A_yXEfU0_yycfU_ + 972
	13  SwiftUI                             0x00000001099b74cc OUTLINED_FUNCTION_40 + 3116
	14  SwiftUI                             0x0000000109964ec0 OUTLINED_FUNCTION_30 + 4452
	15  SwiftUI                             0x00000001098d67cc OUTLINED_FUNCTION_88 + 7156
	16  SwiftUI                             0x0000000109964ec0 OUTLINED_FUNCTION_30 + 4452
	17  SwiftUI                             0x0000000109964edc OUTLINED_FUNCTION_30 + 4480
	18  SwiftUI                             0x0000000109964ec0 OUTLINED_FUNCTION_30 + 4452
	19  SwiftUI                             0x00000001096cd894 OUTLINED_FUNCTION_11 + 3028
	20  SwiftUI                             0x00000001096cd34c OUTLINED_FUNCTION_11 + 1676
	21  SwiftUI                             0x0000000109a60e9c OUTLINED_FUNCTION_8 + 12964
	22  SwiftUI                             0x0000000109a628e0 OUTLINED_FUNCTION_8 + 19688
	23  UIKitCore                           0x00000001056ddfcc -[UICollectionView _selectItemAtIndexPath:animated:scrollPosition:notifyDelegate:deselectPrevious:performCustomSelectionAction:] + 1056
	24  UIKitCore                           0x00000001057096b4 -[UICollectionView touchesEnded:withEvent:] + 476
	25  UIKitCore                           0x0000000105f12e00 forwardTouchMethod + 264
	26  UIKitCore                           0x0000000105f12e00 forwardTouchMethod + 264
	27  UIKitCore                           0x0000000105f12e00 forwardTouchMethod + 264
	28  UIKitCore                           0x0000000105a8c80c _UIGestureEnvironmentUpdate + 5876
	29  UIKitCore                           0x0000000105a8ae38 -[UIGestureEnvironment _deliverEvent:toGestureRecognizers:usingBlock:] + 276
	30  UIKitCore                           0x0000000105a8abb4 -[UIGestureEnvironment _updateForEvent:window:] + 156
	31  UIKitCore                           0x0000000105f21d20 -[UIWindow sendEvent:] + 3168
	32  UIKitCore                           0x0000000105efffe0 -[UIApplication sendEvent:] + 692
	33  UIKit                               0x000000010c6d70b4 -[UIApplicationAccessibility sendEvent:] + 92
	34  UIKitCore                           0x0000000105f7d96c __dispatchPreprocessedEventFromEventQueue + 6824
	35  UIKitCore                           0x0000000105f7f5d0 __processEventQueue + 5612
	36  UIKitCore                           0x0000000105f784ac __eventFetcherSourceCallback + 220
	37  CoreFoundation                      0x000000018037318c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24
	38  CoreFoundation                      0x00000001803730d4 __CFRunLoopDoSource0 + 172
	39  CoreFoundation                      0x0000000180372844 __CFRunLoopDoSources0 + 232
	40  CoreFoundation                      0x000000018036ceb0 __CFRunLoopRun + 756
	41  CoreFoundation                      0x000000018036c7a4 CFRunLoopRunSpecific + 584
	42  GraphicsServices                    0x0000000188ff7c98 GSEventRunModal + 160
	43  UIKitCore                           0x0000000105ee637c -[UIApplication _run] + 868
	44  UIKitCore                           0x0000000105eea374 UIApplicationMain + 124
	45  SwiftUI                             0x0000000109f1d0d4 OUTLINED_FUNCTION_51 + 496
	46  SwiftUI                             0x0000000109f1cf7c OUTLINED_FUNCTION_51 + 152
	47  SwiftUI                             0x0000000109682b60 OUTLINED_FUNCTION_10 + 88
	48  App                                 0x0000000100af3d10 $s3App15realmSwiftUIAppV5$mainyyFZ + 40
	49  App                                 0x0000000100af4bac main + 12
	50  dyld                                0x0000000104e4dfa0 start_sim + 20
	51  ???                                 0x0000000104d61e50 0x0 +<PHONE_NUMBER>
	52  ???                                 0x6b1e000000000000 0x0 +<PHONE_NUMBER>359608832
)
libc++abi: terminating with uncaught exception of type NSException
*** Terminating app due to uncaught exception 'RLMException', reason: 'Cannot write to class Item when no flexible sync subscription has been created.'
terminating with uncaught exception of type NSException
CoreSimulator 857.14 - Device: iPhone 14 Pro (5952C544-5E29-4FE8-ACC2-16D3C511258E) - Runtime: iOS 16.2 (20C52) - DeviceType: iPhone 14 Pro

Can you reproduce the bug?
Always
Reproduction Steps
Clone the sample SwiftUI app out of realm-template-apps and modify the ContentView.swift file to be as below. Then log in and attempt to save a new to-do. The app should immediately crash.
`import SwiftUI
import RealmSwift
struct ContentView: View {
@ObservedObject var app: RealmSwift.App
@EnvironmentObject var errorHandler: ErrorHandler
var body: some View {
    if let user = app.currentUser {
        // Setup configuraton so user initially subscribes to their own tasks
        let config = makeConfig(user: user)
        OpenRealmView(user: user)
            // Store configuration in the environment to be opened in next view
            .environment(\.realmConfiguration, config)
    } else {
        // If there is no user logged in, show the login view.
        LoginView()
    }
}

func makeConfig(user: RealmSwift.User) -> Realm.Configuration {
    var config = user.flexibleSyncConfiguration(initialSubscriptions: { subs in
        subs.remove(named: Constants.allItems)
        if let _ = subs.first(named: Constants.myItems) {
            // Existing subscription found - do nothing
            return
        } else {
            // No subscription - create it
            subs.append(QuerySubscription<Item>(name: Constants.myItems) {
                $0.owner_id == user.id
            })
        }
    })

    Realm.Configuration.defaultConfiguration = config
    return config
}

}
`
Version
10.36.0
What Atlas Services are you using?
Atlas Device Sync
Are you using encryption?
No
Platform OS and version(s)
iOS 16
Build environment
RealmSwift 10.36.0
RealmDatabase 13.4.1
Xcode Version 14.2 (14C18)

Hi @GriffinJBC I can reproduce the issue and working in a fix for this


Long term caching

I just read this article on predictable long term caching with Webpack (linked from the official documentation).
Should some of this be added into the current config or is this too complicated ?

that's been done now.


Integrating the login/signup api with frontend.

🖥 Frontend Issue
Description
I saw that on front end the login/signup is not working so i want to integrate the login/signup on frontend with the backend. By this the login/signup will be properly working and users will be able to login, signup and logout.
Steps to Reproduce
I will use react and redux for this.
Expected behavior
I want that users will be able to properly login and signup.
Actual behavior
Login/Signup pages are not working and not integrated with the backend.

[X ] Yes
[ ] No

In hacktoberfest also
Assign this issue to me @dhairyagothi

Sure please Add @tarunkumar2005
i will change badge according to PR
go ahead

@dhairyagothi Create the pull request you can check it and merge it.


docs: update "CLI Installation" section in README.md (#1126)

Closes #1126
📑 Description

pass the rpm url to the rpm command.
remove the duplicate "-i" option in the 64 bit rpm installation command.
add the "--allow-untrusted" option to apk installation command.
replace "curl" with "wget" for Alpine Linux.
remove the extra and meaningless "x" at the end of the "APK-based installation (Alpine)" section.

✅ Checks

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

ℹ Additional Information

@ajayk @AlexsJones @yankay @chenrui333
thx

but why?

Just try to optimize CLI installation guide.
Ignore it if it's not necessary.

but why?

Just try to optimize CLI installation guide.   #1126
Ignore it if it's not necessary.


Add trait to  allow inspection of exported functions

InspectExorted: add methods to retrieve signature of DynFunc
Create a instance module
Factorize out ExportedFunction

NOTE: substitute #69

@Hywan please review

Sorry for the delay, I was busy on other projects.

I wonder whether we shouldn't return a tuple as mentionend in https://docs.python.org/3/library/inspect.html#inspect.getfullargspec. Thoughts?

how much to overlap with Python's utilities it is a discussion to carry on. We want for sure to provide some methods with similar names and functionalities but only in real-usage use cases as the Python stdlib is huge (as per the "battery included" motto).
Thanks. It is really great to contribute.


Move hooking into rails out of the railtie

This leads to a cleaner railtie and paves the way to a better hook process, where we're not so coupled to foreigner or LHM.

merge @franciscoj @enricostano ?

Danke!


[TW#27830] Multi-Core handling of gpio interrupts (gpio_install_isr_service / gpio_isr_handler) - missing or double calls to handler

Environment

Development Kit:     No (own hardware based on ESP32-PICO-D4
Kit version: na
Module or chip used:  ESP32-PICO-D4
IDF version v3.1
Build System: Make
Compiler version 1.22.0-80
Operating System: Linux
Power Supply:   DC/DC 2.8V

Problem Description
This is about code in 'esp-idf/components/driver/gpio.c'.
I checked the code in master and but I am at the moment in the 3.1 release branch.
I am using GPIO interrupts a lot.
I am porting an application to the esp32 with existing code that uses an own HAL layer and is already based on FreeRTOS.
I do call once 'gpio_install_isr_service' and then 'gpio_isr_handler' and 'gpio_intr_enable' for every IO.
The threads that call gpio_isr_handler/gpio_intr_enable will get distributed randomly to a free core through FreeRTOS because the legacy code does not use xTaskCreatePinnedToCore.
The problem is now that I get duplicated calls to gpio_isr_handler because the code in 'gpio_intr_service' does not check if a GPIO is assigned to the core the ISR is running.
This resulted in double calls and sometimes in lost interrupts.
I see two solutions:

only handle in gpio_intr_service GPIOs assigned to the current core
assign all IRQs to a specific core

I choose the second solution and changed function 'gpio_intr_enable_on_core' to only assign to one CPU and had no more problems.
Expected Behavior
No missing or double call to the gpio interrupt handler
Actual Behavior
Missing or double calls to gpio interrupt handler if initialisation is done from both cores.

Hi, @martinportmann
Can you provide a example that I can reproduce your issue?
thanks!!

Hi, @martinportmann
Have you solved the problems?

Hi koohoo
As I work on my own hardware I have no development kit around to
demonstrate the problem.
Me for me I have solved the problem in the way that I changed the esp-idf
to just issue the IRQ on one CPU.
Therefore I changed components/driver/gpio.c function
gpio_intr_enable_on_core to:
static esp_err_t gpio_intr_enable_on_core (gpio_num_t gpio_num, uint32_t
core_id)
{
GPIO_CHECK(GPIO_IS_VALID_GPIO(gpio_num), "GPIO number error",
ESP_ERR_INVALID_ARG);
gpio_intr_status_clr(gpio_num);
GPIO.pin[gpio_num].int_ena = GPIO_PRO_CPU_INTR_ENA;     //enable pro
cpu intr
return ESP_OK;
}
This means that all the GPIO IRQ will be executed on the first core. In my
case this is acceptable but the original idea was that
the GPIO interrupt will be enabled on the calling core. But the function
'gtpio_intr_service' does not check if the event is associated to the core
running the actual IRQ.
If two GPIO events happen at the same time two GPIO IRQ routines run at the
same time reading/writing on the same registers ...
Best regards

Martin

On Mon, Dec 17, 2018 at 6:22 AM kooho<EMAIL_ADDRESS>wrote:

Hi, @martinportmann https://github.com/martinportmann
Have you solved the problems?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/espressif/esp-idf/issues/2808#issuecomment-447775339,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADb9KNGDtgD9OofkrRKV_QUuQBFRcnhfks5u52JRgaJpZM4ZJB03
.

@martinportmann, Could you please look at PR https://github.com/espressif/esp-idf/pull/2873
With these patches, you should be able to:

call gpio_intr_disable from anywhere and expect the interrupt not to occur again.
rely on gpio_intr_disable to disable an interrupt consistently.
call gpio_intr_enable from any task, regardless on which core it runs.

Hi Pieter
I had no time to test BUT:
I just call enable once at startup and therefore chance is that this is not
solving anything for me.
Please refer to the description of the problem. The problem happs within
the IRQ handling events for both both CPUs.
Best regards

Martin

On Sat, Dec 29, 2018 at 12:19 PM Pieter du Preez<EMAIL_ADDRESS>wrote:

@martinportmann https://github.com/martinportmann, Could you please
look at PR #2873 https://github.com/espressif/esp-idf/pull/2873
With these patches, you should be able to:

call gpio_intr_disable from anywhere and expect the interrupt not to
occur again.
rely on gpio_intr_disable to disable an interrupt consistently.
call gpio_intr_enable from any task, regardless on which core it
runs.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/espressif/esp-idf/issues/2808#issuecomment-450499680,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADb9KMzOlzsHXVuQtQf74KvgiM1oB5JPks5u94gPgaJpZM4ZJB03
.

Hi Martin,

I just call enable once at startup and therefore chance is that this is not solving anything for me.

I'm not sure of this. The difference is that gpio_intr_enable now enables the interrupt on the core, where gpio_install_service was called. Furthermore gpio_intr_enable_on_core (where you had to make a change to get your program to work) was removed, as gpio_intr_enable now consistently enables the interrupt on the right core.
For a demonstration of this, you could look at the unit test that I created for:

testing the enabling of a gpio interrupt (calling gpio_isr_handler_add, gpio_set_intr_type and/or gpio_intr_enable) on a different core to the one on which gpio_install_isr_service(0) was called.
testing disabling and re-enabling interrupts, using gpio_intr_disable for disabling and gpio_intr_enable and/or gpio_set_intr_type for enabling on a different core to the one on which gpio_install_isr_service(0) was called.

See:
https://github.com/wingunder/esp-idf/blob/a89e8213502007a0718fc3d5a99dd979677951f2/components/driver/test/test_gpio.c#L625-L735

I do call once 'gpio_install_isr_service' and then 'gpio_isr_handler' and 'gpio_intr_enable' for every IO.
The threads that call gpio_isr_handler/gpio_intr_enable will get distributed randomly to a free core through FreeRTOS because the legacy code does not use xTaskCreatePinnedToCore.

Do you mean that you call gpio_isr_handler_add instead of gpio_isr_handler? (gpio_isr_handler is not in master:HEAD).
Would it be possible to supply a piece of code demonstrating the problem, similar to the test case that I pointed to above?

Hi, Thank you for feedback on this issue. we will fix this bug soon.
@wingunder thanks for your PR, but we can use esp_ipc_call to fix this bug.
thanks !!