Moved most prerequisites to setup.py requirements

I was going over the installer steps (just ordered the rfcat to help) and saw the many prerequisites steps, which gave an issue with the rflib which could not be found. Because I had not used the pip setup for rfcat. I am probably not the only one, so I moved all pip install requirements including rfcat into the pip setup step to make the install steps a bit simpler.

Thanks!  Have you tested this on a clean setup?

Yes, i always work in a virtualenv. So I deleted that an created a new one to test it again.


Adds 3 Banker Rewards

Implements the 3 rewards the Banker provides:

Adults Wallet
Blue Rupee
Heart Piece

Adds RI_WALLET_ADULT to the Shuffled Items List.
Adds Logic for the Banker as well as retrofits the Blacksmiths Logic that was missing previously in https://github.com/garrettjoecox/2ship2harkinian/pull/46

Build Artifacts

2ship-linux.zip
2ship-windows.zip
2ship-mac.zip

Squashed this into the main branch


Use storage locations for thumbnails

Mnkras originally did all the work, I did a little bit of extra DI stuff and got the tests functioning
See #3746

YAYYY

We should change the typehints in src/File/File.php to the interface


[core/shape] Grid doesn't show through transparent shapes

Issue description
Description pretty much says it. Drawing a transparent cube on top of the grid won't show the grid through the shape. I looked through a few related tickets, I suspect this may be a known wont-fix. Just thought I'd throw it up here in case.
Otherwise, I've been loving the library, it's been a dream just picking up and playing around. Thanks for your work!
Environment (linux, debian 11)
INFO: Initializing raylib 4.2-dev
INFO: Supported raylib modules:
INFO:     > rcore:..... loaded (mandatory)
INFO:     > rlgl:...... loaded (mandatory)
INFO:     > rshapes:... loaded (optional)
INFO:     > rtextures:. loaded (optional)
INFO:     > rtext:..... loaded (optional)
INFO:     > rmodels:... loaded (optional)
INFO:     > raudio:.... loaded (optional)
INFO: DISPLAY: Device initialized successfully
INFO:     > Display size: 1920 x 1080
INFO:     > Screen size:  640 x 480
INFO:     > Render size:  640 x 480
INFO:     > Viewport offsets: 0, 0
INFO: GLAD: OpenGL extensions loaded successfully
INFO: GL: Supported extensions count: 223
INFO: GL: OpenGL device information:
INFO:     > Vendor:   Intel
INFO:     > Renderer: Mesa Intel(R) UHD Graphics 620 (WHL GT2)
INFO:     > Version:  4.6 (Core Profile) Mesa 20.3.5
INFO:     > GLSL:     4.60

Issue Screenshot

@computermouth I'm afraid this is out of scope for raylib, engines usually sort objects for drawing, front-to-back for opaque objects and back-to-front for transparent objects (with depth testing enabled). With raylib objects sorting is up to the user.
It should work as expected if you draw grid first and the transparent objects after it.

Otherwise, I've been loving the library, it's been a dream just picking up and playing around. Thanks for your work!

Glad you like it! :D


[Question] <How do I support the swagger of springcloud themselves?>

Question
[Question] <How do I support the swagger of springcloud themselves?>
I want direct access to each microservice swagger via shenyu.
I deployed shenyu in the K8s +docker cluster,
Multiple springcloud services are registered with shenyu, but cannot pass through directly
http://<IP_ADDRESS>:9195/testserver/swagger-ui.html
The way to access swagger addresses,
Adding rules manually in the springcloud plug-in is also not accessible.
I've tried using the divide plug-in to configure ip:host for access, which works, but obviously not for production because the cluster's service ip is not fixed.

https://github.com/apache/shenyu/issues/4353


How about below 2 things after this Pull Request

          How about below 2 things after this Pull Request

Remove unsubscribe method
CacheStore extends Subscribable https://github.com/TanStack/query/blob/main/packages/query-core/src/subscribable.ts

Originally posted by @manudeli in https://github.com/toss/suspensive/pull/1147#discussion_r1693266363

@SEOKKAMONI share your plan please

@manudeli I recently joined the company this week and am currently in the process of adapting. Therefore, I would like to focus solely on adapting to the company this week.
Would it be okay to resume this task starting on Saturday?

I have shared my plan in https://github.com/toss/suspensive/issues/839#issuecomment-2260228134, so please check it.

Duplicated with #839


Can't remove pw

I made a whitelist and configured the server for it. I tested it. It works great. The problem I'd now I can't get rid of the PW protection. I did printconfig and there is no config file that has the PW setting. Restarted and updated the server multiple times. It accepts other changes, just not this one.

Please check if GameUserSettings.ini still specifies a password.

I quickly thought, "of course, duh!" And I went to verify before returning with an answer and there it is. I feel so sheepish and noobish. :( Thanks! Such an easy answer :)

It can catch you out - the game server modifies its config when it starts and stores any options specified on its command-line, meaning such options can stick around after they have been removed from the command-line.


fix(e2e): specify pullPolicy for upgrade test

Description:
This change modifies the pullPolicy for OSM images for the upgrade e2e
test to match how it's handled for installs, where pre-deployed clusters
will use Always and kind clusters provisioned by the framework will use
IfNotPresent since then the images are assumed not to be pushed to a
registry.

Testing done: Ran the upgrade test locally with both -installType=KindCluster and -installType=SelfInstall and both behaved as expected.

Affected area:

Functional Area

New Functionality
[ ]

CI System
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Demo
[ ]

Documentation
[ ]

Egress
[ ]

Ingress
[ ]

Install
[ ]

Networking
[ ]

Observability
[ ]

Performance
[ ]

SMI Policy
[ ]

Security
[ ]

Sidecar Injection
[ ]

Tests
[X]

Upgrade
[ ]

Other
[ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? No

Did you notify the maintainers and provide attribution?

Is this a breaking change? No

Has documentation corresponding to this change been updated in the osm-docs repo (if applicable)? N/A

Codecov Report

Merging #4478 (98653da) into main (e45d28a) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #4478      +/-   ##
==========================================
- Coverage   69.14%   69.08%   -0.06%
==========================================
  Files         212      212
  Lines       14595    14595
==========================================
- Hits        10091    10083       -8
- Misses       4452     4460       +8
  Partials       52       52

Flag
Coverage Δ

unittests
69.08% <ø> (-0.06%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/messaging/workqueue.go
89.28% <0.00%> (-10.72%)
:arrow_down:

pkg/crdconversion/crdconversion.go
70.14% <0.00%> (-4.48%)
:arrow_down:

pkg/certificate/rotor/rotor.go
86.95% <0.00%> (+2.17%)
:arrow_up:

Continue to review full report at Codecov.

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


Remember scroll position

Addressed the request in (https://github.com/plrenaudin/goto-last-edit/issues/6)
I agree with @frantic, I also think that it would be nice if it remembered the scroll position.
@plrenaudin what do you think?

Thanks a lot for this PR, I'll test this tomorrow after work. meanwhile would it be possible to add a unit test to validate the behavior?

@buraks thanks for the work here. It seems TextEditor.getScrollTop is deprecated.
Please use TextEditorElement.getScrollTop instead:
diff --git a/lib/goto-last-edit.coffee b/lib/goto-last-edit.coffee
index 49c81f2..883916a 100644
--- a/lib/goto-last-edit.coffee
+++ b/lib/goto-last-edit.coffee
@@ -26,12 +26,11 @@ module.exports =

   saveCursorPosition: (editor) ->
     if editor.buffer.previousModifiedStatus or editor.isModified()
-
       @lastEditPosition = {
         pane: atom.workspace.getActivePane(),
         editor: editor,
         position: editor.cursors[0]?.getBufferPosition(),
-        scrollTop: editor.getScrollTop()
+        scrollTop: atom.views.getView(editor).getScrollTop()
       }
       #add position to history only if different
       @pushInHistory(@lastEditPosition) unless @hasNotChangedPosition()
@@ -80,7 +79,7 @@ module.exports =
           @lastEditPosition.position,
           autoscroll: false
         )
-<EMAIL_ADDRESS>+<EMAIL_ADDRESS>       else if not goBack and @historyPosition == @history.length - 1
         @historyPosition++

After trying your PR some tests are failing, please fix them.
(no need to fix the one failing in master but if you do have a fix it would be much appreciated :+1: )


facebook account getting banned

Description:
I have noticed that after a few days my accounts using fbchat are getting permanently banned on facebook. Is there some way to prevent this?

Description:
I have noticed that after a few days my accounts using fbchat are getting permanently banned on facebook. Is there some way to prevent this?

Use Two Step Authentication to prevent this. And don't do things like sending same message to a lot of people (if you're doing).

See #427, #187 and #477 for a lot of discussion regarding this (and other things).
The best advice I can give is to store and reuse session cookies, but if you're already doing that, then I don't know 😕

Thanks for answers and sorry for the question - later I realised that similar questions have been answered. I think cookies will help


app command line miss match

The azure web application is not starting up / errors with
6gwercguaeuhq.scm.azurewebsites.net/api/vfs/LogFiles/2024_07_17_lw1sdlwk0000ZJ_default_docker.log)
2024-07-17T23:17:06.604588362Z            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-07-17T23:17:06.604591862Z   File "<frozen importlib._bootstrap>", line 1204, in _gcd_import
2024-07-17T23:17:06.604613262Z   File "<frozen importlib._bootstrap>", line 1176, in _find_and_load
2024-07-17T23:17:06.604617062Z   File "<frozen importlib._bootstrap>", line 1140, in _find_and_load_unlocked
2024-07-17T23:17:06.604620962Z ModuleNotFoundError: No module named 'main'
2024-07-17T23:17:06.607552268Z [2024-07-17 23:17:06 +0000] [67] [INFO] Worker exiting (pid: 67)
2024-07-17T23:17:07.259553990Z [2024-07-17 23:17:07 +0000] [62] [ERROR] Worker (pid:67) exited with code 3
2024-07-17T23:17:07.268840809Z [2024-07-17 23:17:07 +0000] [62] [ERROR] Shutting down: Master
2024-07-17T23:17:07.285444443Z [2024-07-17 23:17:07 +0000] [62] [ERROR] Reason: Worker failed to boot./home/LogFiles/2024_07_17_lw1sdlwk0000ZJ_default_scm_docker.log  (https://app-backend-6gwercguaeuhq.scm.azurewebsites.net/api/vfs/LogFiles/2024_07_17_lw1sdlwk0000ZJ_default_scm_docker.log)
2024-07-17T15:30:10.6406269Z Wed Jul 17 15:30:10 UTC 2024 running .net core
2024-07-17T15:30:15.3463564Z Startup : <IP_ADDRESS>558
2024-07-17T15:30:15.5617329Z Configure Services : <IP_ADDRESS>0726
2024-07-17T15:30:17.3290924Z Configure : <IP_ADDRESS>3987
2024-07-17T15:30:18.7879275Z Setting Up Routes : <IP_ADDRESS>7621
2024-07-17T15:30:20.6814800Z Exiting Configure : <IP_ADDRESS>4603
2024-07-17T15:30:21.6960998Z Hosting environment: Production
2024-07-17T15:30:21.6969482Z Content root path: /opt/Kudu
2024-07-17T15:30:21.6978900Z Now listening on: http://<IP_ADDRESS>:8181
2024-07-17T15:30:21.7149183Z Application started. Press Ctrl+C to shut down./home/LogFiles/2024_07_17_lw1sdlwk0000ZJ_docker.log  (https://app-backend-6gwercguaeuhq.scm.azurewebsites.net/api/vfs/LogFiles/2024_07_17_lw1sdlwk0000ZJ_docker.log)

There is a python webapp runtime missmatch between bicep main.bicep
runtimeName: 'python'
runtimeVersion: '3.11'
appCommandLine: 'python3 -m gunicorn main:app'

and the one used in app/frontend/start.sh which starts fine without erros
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>cd ../backend
port=50505
host=localhost
python -m quart --app main:app run --port "$port" --host "$host" --reload

Using latest version /main /17.07.2024

The commands are expected to be different. We use gunicorn in production, since it can handle multiple processes.
If you are getting that error, it usually means there was an issue with the deploy or that the App Service server is still starting up. See this guide to debugging App Service deployments:
https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/docs/appservice.md

Closing this issue, but please open a new one if you believe there's an error after going through the App Service deployment guide.

see https://github.com/Azure-Samples/azure-search-openai-demo/issues/1864


Add voice clone kidnapping story

It'd be both impersonation and cybercrime, right?

Oh, impersonation doesn't exist.

Good edits on the first paragraph; I made some more edits to the second.

(I don't think it's that important to focus on the people she was with; the point is that she was able to contact her husband and confirm that her daughter was safe.)


translation(xzy): add doc translation (minigrid_en、pendulum_en)

done

fix comments by nyz in pr80#

所有的标题需要大写~

This PR has been integrated in #135


Some test fail on s390x

From https://koji.fedoraproject.org/koji/taskinfo?taskID=125093717:
25/25 Test #25: heffte_longlong_np4 ..............***Failed  375.02 sec
--------------------------------------------------------------------------------
                               heffte::fft class
--------------------------------------------------------------------------------
     float                  -np 4  test int/long long<stock>              pass
24% tests passed, 19 tests failed out of 25
Total Test time (real) = 1354.20 sec
The following tests FAILED:
	  4 - heffte_reshape3d_np4 (Failed)
	  5 - heffte_reshape3d_np7 (Failed)
	  6 - heffte_reshape3d_np12 (Failed)
	  8 - heffte_fft3d_np2 (Failed)
	  9 - heffte_fft3d_np4 (Failed)
	 10 - heffte_fft3d_np6 (Failed)
	 11 - heffte_fft3d_np8 (Failed)
	 12 - heffte_fft3d_np12 (Failed)
	 13 - heffte_streams_np6 (Failed)
	 14 - test_subcomm_np8 (Failed)
	 15 - test_subcomm_np12 (Failed)
	 17 - heffte_fft3d_r2c_np2 (Failed)
	 18 - heffte_fft2d_r2c_np4 (Failed)
	 19 - heffte_fft3d_r2c_np6 (Failed)
	 20 - heffte_fft3d_r2c_np8 (Failed)
	 21 - heffte_fft3d_r2c_np12 (Failed)
	 23 - test_cos_np2 (Failed)
	 24 - test_cos_np4 (Failed)
	 25 - heffte_longlong_np4 (Failed)
Errors while running CTest
error: Bad exit status from /var/tmp/rpm-tmp.kyrg4o (%check)
RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.kyrg4o (%check)
Child return code was: 1

Full build log: build_s390x.log.txt.zip
It says v2.4.0, but is actually c7c8f69ce78395040a2690bcb6984299449176ce.
Aarch64, ppc64le and x86_64 work.

I've never tested on s390 but looking at the log I suspect this is an MPI issue. The tests are passing when they don't use MPI or run only on a single node, as soon as the test tries 2 or more notes the it fails.
Is MPI configured correctly in the test environment?

The test environment is just the Fedora package, @keszybz would know the details.

The "mpi environment" is just what the test sets up. The build is done in a dedicated VM, the hw_info.log file linked from the build describes the machine.
The test does this:
%check
# allow openmpi to oversubscribe, i.e. runs test with more
# cores than the builder has
export PRTE_MCA_rmaps_default_mapping_policy=:oversubscribe

for mpi in mpich openmpi; do
  test -n "${mpi}" && module load mpi/${mpi}-%{_arch}
  %ctest
  test -n "${mpi}" && module unload mpi/${mpi}-%{_arch}
done

i.e.
export PRTE_MCA_rmaps_default_mapping_policy=:oversubscribe

for mpi in mpich openmpi; do
  test -n "${mpi}" && module load mpi/${mpi}-x86_64
  /usr/bin/ctest --test-dir "redhat-linux-build" \
           --output-on-failure \
           --force-new-ctest-process \
            -j${RPM_BUILD_NCPUS}
  test -n "${mpi}" && module unload mpi/${mpi}-x86_64
done

I can try to answer some general questions, but I know nothing about this package and about as much about s390x ;)

CPU info:
Architecture:                         s390x
CPU op-mode(s):                       32-bit, 64-bit
Byte Order:                           Big Endian
CPU(s):                               3
On-line CPU(s) list:                  0-2
Vendor ID:                            IBM/S390
Model name:                           -
Machine type:                         3931
Thread(s) per core:                   1
Core(s) per socket:                   1
Socket(s) per book:                   1
Book(s) per drawer:                   1
Drawer(s):                            3
CPU dynamic MHz:                      5200
CPU static MHz:                       5200
BogoMIPS:                             3331.00
Dispatching mode:                     horizontal
Flags:                                esan3 zarch stfle msa ldisp eimm dfp edat etf3eh highgprs te vx vxd vxe gs vxe2 vxp sort dflt vxp2 nnpa sie
Hypervisor:                           KVM/Linux
Hypervisor vendor:                    KVM
Virtualization type:                  full
L1d cache:                            384 KiB (3 instances)
L1i cache:                            384 KiB (3 instances)
L2 cache:                             96 MiB (3 instances)
L3 cache:                             256 MiB
NUMA node(s):                         1
NUMA node0 CPU(s):                    0-2

All MPI tests are failing, the non-MPI tests are passing. The log does not contain details, e.g., the output of ctest -V
Also, for some reason, the tests are running in parallel which further messes up the ctest output. CMake tells ctest to run everything in series, otherwise we can get really nasty over-subscription of resources. There are multiple tests that take 12 MPI ranks, and each rank may or may not be using multiple threads.
How can we get the details from at least one failing test, e.g., the test_reshape3d running with 4 ranks.

—output-on-failure should be the same as -V on error, but let me add a -j1 to the ctest.

#67 should help with the over subscribing issue.

@junghans  Let me know if the PR helped or if you need to use -D Heffte_SEQUENTIAL_TESTING
I would like to close this issue before tagging the release.

I did another build, https://koji.fedoraproject.org/koji/taskinfo?taskID=125159590:
Test project /builddir/build/BUILD/heffte-2.4.0-build/heffte-master/s390x-redhat-linux-gnu-mpich
      Start  1: heffte_fortran_fftw
      Start  2: unit_tests_nompi
 1/25 Test  #1: heffte_fortran_fftw ..............   Passed    0.08 sec
      Start  3: unit_tests_stock
      Start  7: heffte_fft3d_np1
 2/25 Test  #3: unit_tests_stock .................   Passed    0.00 sec
      Start 16: heffte_fft3d_r2c_np1
 3/25 Test #16: heffte_fft3d_r2c_np1 .............   Passed    0.08 sec
      Start 22: test_cos_np1
 4/25 Test  #7: heffte_fft3d_np1 .................   Passed    0.13 sec
 5/25 Test #22: test_cos_np1 .....................   Passed    0.08 sec
      Start  8: heffte_fft3d_np2
 6/25 Test  #8: heffte_fft3d_np2 .................***Failed    0.08 sec
--------------------------------------------------------------------------------
                               heffte::fft class
--------------------------------------------------------------------------------
                            constructor heffte::fft3d<stock>              pass
Abort(676410127) on node 1 (rank 1 in comm 0): Fatal error in internal_Barrier: Other MPI error, error stack:
internal_Barrier(7454).....................: MPI_Barrier(MPI_COMM_WORLD) failed
MPID_Barrier(167)..........................:
MPIDI_Barrier_allcomm_composition_json(132):
MPIDI_POSIX_mpi_bcast(238).................:
MPIDI_POSIX_mpi_release_gather_release(218): message sizes do not match across processes in the collective routine: Received 0 but expected 1
      Start 17: heffte_fft3d_r2c_np2
 7/25 Test  #2: unit_tests_nompi .................   Passed    0.38 sec
 8/25 Test #17: heffte_fft3d_r2c_np2 .............***Failed    0.14 sec
--------------------------------------------------------------------------------
                             heffte::fft_r2c class
--------------------------------------------------------------------------------
                        constructor heffte::fft3d_r2c<stock>              pass
Abort(676410127) on node 1 (rank 1 in comm 0): Fatal error in internal_Barrier: Other MPI error, error stack:
internal_Barrier(7454).....................: MPI_Barrier(MPI_COMM_WORLD) failed
MPID_Barrier(167)..........................:
MPIDI_Barrier_allcomm_composition_json(132):
MPIDI_POSIX_mpi_bcast(238).................:
MPIDI_POSIX_mpi_release_gather_release(218): message sizes do not match across processes in the collective routine: Received 0 but expected 1
      Start  4: heffte_reshape3d_np4
 9/25 Test  #4: heffte_reshape3d_np4 .............***Failed    0.75 sec
--------------------------------------------------------------------------------
                             heffte reshape methods
--------------------------------------------------------------------------------
                                   heffte::mpi::gather_boxes              pass
      Start  5: heffte_reshape3d_np7
10/25 Test  #5: heffte_reshape3d_np7 .............***Failed    1.70 sec
--------------------------------------------------------------------------------
                             heffte reshape methods
--------------------------------------------------------------------------------
                                   heffte::mpi::gather_boxes              pass
     float         -np 7  heffte::reshape3d_alltoall all-2-1              pass
      Start  6: heffte_reshape3d_np12
11/25 Test  #6: heffte_reshape3d_np12 ............***Failed    3.13 sec
--------------------------------------------------------------------------------
                             heffte reshape methods
--------------------------------------------------------------------------------
                                   heffte::mpi::gather_boxes              pass
      Start  9: heffte_fft3d_np4
12/25 Test  #9: heffte_fft3d_np4 .................***Failed    8.16 sec
--------------------------------------------------------------------------------
                               heffte::fft class
--------------------------------------------------------------------------------
  ccomplex                  -np 4  test heffte::fft2d<stock>              pass
      Start 10: heffte_fft3d_np6
13/25 Test #10: heffte_fft3d_np6 .................***Failed   25.74 sec
--------------------------------------------------------------------------------
                               heffte::fft class
--------------------------------------------------------------------------------
     float                  -np 6  test heffte::fft3d<stock>              pass
      Start 11: heffte_fft3d_np8
14/25 Test #11: heffte_fft3d_np8 .................***Failed   45.90 sec
--------------------------------------------------------------------------------
                               heffte::fft class
--------------------------------------------------------------------------------
     float                  -np 8  test heffte::fft3d<stock>              pass
      Start 12: heffte_fft3d_np12
15/25 Test #12: heffte_fft3d_np12 ................***Failed   58.30 sec
--------------------------------------------------------------------------------
                               heffte::fft class
--------------------------------------------------------------------------------
     float                 -np 12  test heffte::fft3d<stock>              pass
      Start 13: heffte_streams_np6
16/25 Test #13: heffte_streams_np6 ...............***Failed   17.86 sec
--------------------------------------------------------------------------------
                              heffte::fft streams
--------------------------------------------------------------------------------
  ccomplex         -np 6  test heffte::fft3d (stream)<stock>              pass
Abort(676410127) on node 3 (rank 3 in comm 0): Fatal error in internal_Barrier: Other MPI error, error stack:
internal_Barrier(7454).....................: MPI_Barrier(MPI_COMM_WORLD) failed
MPID_Barrier(167)..........................:
MPIDI_Barrier_allcomm_composition_json(132):
MPIDI_POSIX_mpi_bcast(238).................:
MPIDI_POSIX_mpi_release_gather_release(218): message sizes do not match across processes in the collective routine: Received 0 but expected 1
      Start 14: test_subcomm_np8
17/25 Test #14: test_subcomm_np8 .................***Failed   76.87 sec
--------------------------------------------------------------------------------
                          heffte::fft subcommunicators
--------------------------------------------------------------------------------
    double                -np 8  test subcommunicator<stock>              pass
      Start 15: test_subcomm_np12
18/25 Test #15: test_subcomm_np12 ................***Failed  116.44 sec
--------------------------------------------------------------------------------
                          heffte::fft subcommunicators
--------------------------------------------------------------------------------
    double               -np 12  test subcommunicator<stock>              pass
      Start 18: heffte_fft2d_r2c_np4
19/25 Test #18: heffte_fft2d_r2c_np4 .............***Failed   31.25 sec
--------------------------------------------------------------------------------
                             heffte::fft_r2c class
--------------------------------------------------------------------------------
     float              -np 4  test heffte::fft2d_r2c<stock>              pass
      Start 19: heffte_fft3d_r2c_np6
20/25 Test #19: heffte_fft3d_r2c_np6 .............***Failed   63.12 sec
--------------------------------------------------------------------------------
                             heffte::fft_r2c class
--------------------------------------------------------------------------------
     float              -np 6  test heffte::fft3d_r2c<stock>              pass
      Start 20: heffte_fft3d_r2c_np8
21/25 Test #20: heffte_fft3d_r2c_np8 .............***Failed  104.04 sec
--------------------------------------------------------------------------------
                             heffte::fft_r2c class
--------------------------------------------------------------------------------
     float              -np 8  test heffte::fft3d_r2c<stock>              pass
      Start 21: heffte_fft3d_r2c_np12
22/25 Test #21: heffte_fft3d_r2c_np12 ............***Failed  155.48 sec
--------------------------------------------------------------------------------
                             heffte::fft_r2c class
--------------------------------------------------------------------------------
     float             -np 12  test heffte::fft3d_r2c<stock>              pass
      Start 23: test_cos_np2
23/25 Test #23: test_cos_np2 .....................***Failed    1.13 sec
      Start 24: test_cos_np4
24/25 Test #24: test_cos_np4 .....................***Failed    6.16 sec
--------------------------------------------------------------------------------
                               cosine transforms
--------------------------------------------------------------------------------
     float             -np 4  test cosine<stock-cos-type-II>              pass
      Start 25: heffte_longlong_np4
25/25 Test #25: heffte_longlong_np4 ..............***Failed  105.14 sec
--------------------------------------------------------------------------------
                               heffte::fft class
--------------------------------------------------------------------------------
     float                  -np 4  test int/long long<stock>              pass
24% tests passed, 19 tests failed out of 25
Total Test time (real) = 821.67 sec
The following tests FAILED:
	  4 - heffte_reshape3d_np4 (Failed)
	  5 - heffte_reshape3d_np7 (Failed)
	  6 - heffte_reshape3d_np12 (Failed)
	  8 - heffte_fft3d_np2 (Failed)
	  9 - heffte_fft3d_np4 (Failed)
	 10 - heffte_fft3d_np6 (Failed)
	 11 - heffte_fft3d_np8 (Failed)
	 12 - heffte_fft3d_np12 (Failed)
	 13 - heffte_streams_np6 (Failed)
	 14 - test_subcomm_np8 (Failed)
	 15 - test_subcomm_np12 (Failed)
	 17 - heffte_fft3d_r2c_np2 (Failed)
	 18 - heffte_fft2d_r2c_np4 (Failed)
	 19 - heffte_fft3d_r2c_np6 (Failed)
	 20 - heffte_fft3d_r2c_np8 (Failed)
	 21 - heffte_fft3d_r2c_np12 (Failed)
	 23 - test_cos_np2 (Failed)
	 24 - test_cos_np4 (Failed)
	 25 - heffte_longlong_np4 (Failed)
Errors while running CTest

Something is wrong with MPI, MPI_Barrier(MPI_COMM_WORLD)  should always work. This is the first MPI method called after MPI_Init().

You can try -D Heffte_SEQUENTIAL_TESTING=ON to make sure different MPI processes don't try to synch across ranks of different tests.
You can try a minimal MPI example, e.g., no heffte just a small program that does save recv and check if that works in the rpm environment. Maybe MPI does not work at all.

Hard to figure this out without hands onto the hardware.

The sequential one, https://koji.fedoraproject.org/koji/taskinfo?taskID=125161367, fails as well:
4/25 Test  #4: heffte_reshape3d_np4 .............***Failed    0.51 sec
--------------------------------------------------------------------------------
                             heffte reshape methods
--------------------------------------------------------------------------------
                                   heffte::mpi::gather_boxes              pass
Abort(676410127) on node 1 (rank 1 in comm 0): Fatal error in internal_Barrier: Other MPI error, error stack:
internal_Barrier(7454).....................: MPI_Barrier(MPI_COMM_WORLD) failed
MPID_Barrier(167)..........................:
MPIDI_Barrier_allcomm_composition_json(132):
MPIDI_POSIX_mpi_bcast(238).................:
MPIDI_POSIX_mpi_release_gather_release(218): message sizes do not match across processes in the collective routine: Received 0 but expected 1
Abort(676410127) on node 3 (rank 3 in comm 0): Fatal error in internal_Barrier: Other MPI error, error stack:
internal_Barrier(7454).....................: MPI_Barrier(MPI_COMM_WORLD) failed
MPID_Barrier(167)..........................:
MPIDI_Barrier_allcomm_composition_json(132):
MPIDI_POSIX_mpi_bcast(238).................:
MPIDI_POSIX_mpi_release_gather_release(218): message sizes do not match across processes in the collective routine: Received 0 but expected 1

But I think @mkstoyanov is right, that looks very much like a more fundamental issue in the mpich package of Fedora.
@keszybz, who is Fedora's mpich package maintainer?

In my experience, the Red Hat family is rather paranoid.  I won't put it past them to have something in the environment that blocks processes from communicating with MPI. The error message says that MPI_Barrier failed to send/recv even a single byte.
I don't think I can help here.

Let me add a MPI hello world to build and see if that fails, too!

Hmm, https://koji.fedoraproject.org/koji/taskinfo?taskID=125191181, hello world worked:
+ mpicc /builddir/build/SOURCES/mpi_hello_world.c -o mpi_hello_world
+ mpiexec -np 12 ./mpi_hello_world
Hello world from processor db7a3174e80d4305b9dd4b1a288fb59b, rank 0 out of 12 processors
Hello world from processor db7a3174e80d4305b9dd4b1a288fb59b, rank 2 out of 12 processors
Hello world from processor db7a3174e80d4305b9dd4b1a288fb59b, rank 1 out of 12 processors
Hello world from processor db7a3174e80d4305b9dd4b1a288fb59b, rank 3 out of 12 processors
Hello world from processor db7a3174e80d4305b9dd4b1a288fb59b, rank 8 out of 12 processors
Hello world from processor db7a3174e80d4305b9dd4b1a288fb59b, rank 4 out of 12 processors
Hello world from processor db7a3174e80d4305b9dd4b1a288fb59b, rank 6 out of 12 processors
Hello world from processor db7a3174e80d4305b9dd4b1a288fb59b, rank 10 out of 12 processors
Hello world from processor db7a3174e80d4305b9dd4b1a288fb59b, rank 9 out of 12 processors
Hello world from processor db7a3174e80d4305b9dd4b1a288fb59b, rank 7 out of 12 processors
Hello world from processor db7a3174e80d4305b9dd4b1a288fb59b, rank 11 out of 12 processors
Hello world from processor db7a3174e80d4305b9dd4b1a288fb59b, rank 5 out of 12 processors

@keszybz, who is Fedora's mpich package maintainer?

That'd be me. But I only picked up mpich because nobody else wanted it. I'm not qualified to fix real issues.

@opoplawski any ideas? Otherwise, I will ping the developer mailing list.

Hmm, https://koji.fedoraproject.org/koji/taskinfo?taskID=125191181, hello world  worked:

I can't find the source code within the build logs. In the hello-world example, do you have any code other than MPI init and the print statement? You should add at least an MPI_Barrier, i.e.,
  int me, nranks;
  MPI_Comm_rank(MPI_COMM_WORLD, &me);
  MPI_Comm_size(MPI_COMM_WORLD, &nranks);

  for (int i=0; i<nranks; i++) {
    if (me == i)
      std::cout << "hello from rank: " << me << std::endl;
    MPI_Barrier(MPI_COMM_WORLD);
  }

That will call the method which failed in the heffte logs and the order of the ranks should be sequential, i.e., 0, 1, 2, 3, ...

Sorry, it was https://github.com/mpitutorial/mpitutorial/blob/gh-pages/tutorials/mpi-hello-world/code/mpi_hello_world.c

Ok, I made it print the source and added the suggested loop as well in https://koji.fedoraproject.org/koji/taskinfo?taskID=125198447

Hmm
Hello world from processor 9db9bf1ab4534e4e9507c05c42b72e39, rank 0 out of 12 processors
hello from rank: 0
Hello world from processor 9db9bf1ab4534e4e9507c05c42b72e39, rank 2 out of 12 processors
Hello world from processor 9db9bf1ab4534e4e9507c05c42b72e39, rank 4 out of 12 processors
Hello world from processor 9db9bf1ab4534e4e9507c05c42b72e39, rank 1 out of 12 processors
Hello world from processor 9db9bf1ab4534e4e9507c05c42b72e39, rank 5 out of 12 processors
Hello world from processor 9db9bf1ab4534e4e9507c05c42b72e39, rank 8 out of 12 processors
Hello world from processor 9db9bf1ab4534e4e9507c05c42b72e39, rank 10 out of 12 processors
Hello world from processor 9db9bf1ab4534e4e9507c05c42b72e39, rank 6 out of 12 processors
Hello world from processor 9db9bf1ab4534e4e9507c05c42b72e39, rank 11 out of 12 processors
Hello world from processor 9db9bf1ab4534e4e9507c05c42b72e39, rank 3 out of 12 processors
Hello world from processor 9db9bf1ab4534e4e9507c05c42b72e39, rank 9 out of 12 processors
Hello world from processor 9db9bf1ab4534e4e9507c05c42b72e39, rank 7 out of 12 processors
hello from rank: 1
hello from rank: 2
error: Bad exit status from /var/tmp/rpm-tmp.ttBmu8 (%build)
    Bad exit status from /var/tmp/rpm-tmp.ttBmu8 (%build)
RPM build errors:
Child return code was: 1

The commands to read the process info, rank, comm-size, etc. Those do not require actual communication but rather on-node work. The log shows a crash on the second call to the MPI_Barrier() so the hello-world is failing, while working on the other systems.
You can play around with send/recv to see how those act and if they work properly, but there's something wrong with MPI in this environment.

Yeah, that will need some deeper investigations.
I would just go ahead with v2.4.1 and not wait for this issue.


loadSystemPrices not loading properly due to getChildren error

Hi Fuzzy,
I have been using your EveCentralPrices script for a while now, specifically the loadSystemPrices function, and it has been working flawlessly except for the last few days.  When trying to load the function, I get TypeError: cannot call method "getChildren" of null.  I have pasted below a link to part of my google spreadsheet.
https://docs.google.com/spreadsheets/d/11FVbKo-kRiFaCBdAQs4TnfBZwxz9HaxkWVUcCK3kzf4/edit?usp=sharing
If you could help me resolve this I'd greatly appreciate it.

Eve central is acting up right now. https://eve-central.com/
You could shift over to using https://market.fuzzwork.co.uk/api/


Update ERC-3770: Update erc-3770.md

The links were not updated after the separation of ERCs and EIPs. Updated in this PR.

Links should still use eip- because of a quirk of our rendering system.


Init fails while connecting to the api server

An error while testing the branch "robertgzr/devel" that init fails because it cannot connect to the api server.

+ kubeadm join --skip-preflight-checks --token f38264.c30472ab4fd298d9 :6443
[kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters.
[preflight] Skipping pre-flight checks
[discovery] Trying to connect to API Server ":6443"
[discovery] Created cluster-info discovery client, requesting info from "https://:6443"
[discovery] Failed to request cluster info, will try again: [Get https://:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp :6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp :6443: getsockopt: connection refused]
[discovery] Failed to request cluster info, will try again: [Get https://:6443/api/v1/namespaces/kube-public/configmaps/cluster-info: dial tcp :6443: getsockopt: connection refused]

Looking at "scripts/join.sh", I think that join.sh is being called without any cmdline paramter. OTOH in the master branch, it was not the case.
See also https://github.com/kinvolk/kubeadm-nspawn/issues/46#issuecomment-313118682

Fixed via https://github.com/kinvolk/kubeadm-nspawn/commit/261b3bd70edc5672c91198519f56178fbbedaf1d.
Though there are other issues with the init command.


[docs] Minor String Manifesto fixes

Some relatively minor fixes for typos and formatting in the String Manifesto document.
cc @airspeedswift

@swift-ci Please smoke test

Thanks @ole!

It appears these spelling corrections don't compile on linux...

@swift-ci Please smoke test linux platform

This time it worked.


perf: optimize circuit breaker performance

What type of PR is this?
perf
Check the PR title.

[x] This PR title match the format: <type>(optional scope): <description>
[x] The description of this PR title is user-oriented and clear enough for others to understand.
[x] Attach the PR updating the user documentation if the current PR requires user awareness at the usage level. User docs repo

(Optional) Translate the PR title into Chinese.
perf: 优化熔断器性能
(Optional) More detailed description for this PR(en: English/zh: Chinese).

en:
zh(optional):
(Optional) Which issue(s) this PR fixes:

(optional) The PR that updates user documentation:

代码没问题，不过单测挂了

代码没问题，不过单测挂了
@joway 现在OK了


Please help

Im new to forge and all my other mods are working but i cant seem to configure this mod, the mod looks amazing and i really want to use it, so if you could help me it would be much appreciated. Thank you.

By configure it you mean through the "Mods" button on the main menu or "Mod options" ingame? The latest version (2.2.0 or 1.5.0) should work just fine for this.

On Wed, 8 Feb 2017 at 05:49, copygirl<EMAIL_ADDRESS>wrote:

By configure it you mean through the "Mods" button on the main menu or
"Mod options" ingame? The latest version (2.2.0 or 1.5.0) should work just
fine for this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/copygirl/WearableBackpacks/issues/8#issuecomment-278235591,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYb2DNjvW_FxgD5N_CznRQpS27gwK4EAks5raVdKgaJpZM4L6CRc
.

Yeah I mean the through the mods button, and then select configure when the
mod is selected

Which version of the mod are you using? Only the most recent one (2.2.0 and 1.5.0) added the ability to configure things from within the game.
If you're using Curse, do note that the latest version isn't available on there due to Curse being a bit of a pain. You can get the latest one here on the releases page.

On Wed, 8 Feb 2017 at 08:14, copygirl<EMAIL_ADDRESS>wrote:

Which version of the mod are you using? Only the most recent one (2.2.0
and 1.5.0) added the ability to configure things from within the game.
If you're using Curse, do note that the latest version isn't available on
there due to Curse being a bit of a pain. You can get the latest one here
on the releases page
https://github.com/copygirl/WearableBackpacks/releases.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/copygirl/WearableBackpacks/issues/8#issuecomment-278260101,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYb2DJZxV_VRj6w4YVG32XNWnJvNGxYTks5raXligaJpZM4L6CRc
.

 It happens :)


Getting a gtimer error while installing requirements

Hi Vitchyr,
I'm following your rlkit-gpu install instructions (i.e., conda env create -f docker/rlkit_gpu/rlkit-env.yml), and I get the following error:
Could not find a version that satisfies the requirement gtimer==1.0.1b5 (from -r /data/repos/rlkit/docker/rlkit_gpu/condaenv.27ccrza6.requirements.txt (line 4)) (from versions: 1.0.0b0, 1.0.0b1, 1.0.0b2, 1.0.0b3, 1.0.0b4, 1.0.0b5)
No matching distribution found for gtimer==1.0.1b5 (from -r /data/repos/rlkit/docker/rlkit_gpu/condaenv.27ccrza6.requirements.txt (line 4))
Please help :-/

I updated the .yml file to use 1.0.0b5, which should work. If not, please re-open this issue.

Thanks, that worked. Found another related issue going forward. Pytorch 0.4.0 throws the following error - "RecursionError: maximum recursion depth exceeded". Online jedi suggest using 0.3.1 as a fix https://github.com/allenai/allennlp/issues/1161. Might want to update .yml file accordingly :-)


How can I clear the Conversation?

I want to embed an new command '/clear'. This should clear whole of the conversation.

You could store all message ids per conversation in a dict with lists. Later you are able to delete messages of a specifiy conversation via telepot.Bot.deleteMessage(<chat_id>, <message_id>) or its async counterpart telepot.aio.Bot.deleteMessage(<chat_id>, <message_id>).


ERP rates

Dear BudiNverse,
Thanks for sharing the ERP data. I am trying to download the ERP rates from Dec 2016 to Mar 2018. However, I am only able to obtain the data of 2020-07-27. May I ask how could I post a date to obtain past datasets please? Thank you.
Best regards,
Wei Chong

Hi, as far as I am aware, according to LTA's documentation, they do not provide any parameters for the date. Assuming their documentation is up to date and there is no undocumented featurse for the ERP API, there is no way to obtain the data for the date you specifed. You can try contact them directly to get the data instead. I will keep this issue open just in case they start implementing the date parameter
Regards,
BudiNverse

Hi BudiNverse,
Noted with thanks! I am waiting for the reply from LTA Datamall. I will provide updates this issue again later. Thank you.
Best regards,
Wei Chong


SignOutContext needs AuthenticationProperties

Fixes https://github.com/aspnet/HttpAbstractions/issues/152
@Tratcher @HaoK

@brentschmaltz This is for OIDC & WsFed.

We don't do optional parameters anymore.

@davidfowl Removed optional parameters on this method.

Updated PR.
/CC : @muratg

Changes look good to me, I'd ping @brentschmaltz to see if he sees any problems, otherwise :shipit:

@brentschmaltz?

Adding some more context after speaking with Praburaj. there can be a lot of other parameters for signout: id_token, session_state, sid, idp, state etc.  I just saw the spec on Thursday afternoon and am digesting it. We may want to have first class properties similar to how OIDCMessage and WsFedMessage work. It may mean  or derived types. Not sure. Signout it not as simple as we think.

Merged https://github.com/aspnet/HttpAbstractions/commit/58c45cd379774cf1fd683a12465cb52094b7193d


Typescript Definitions

Any chance that you are working on Typescript definitions?

no i haven't done any work on that. I have used a lot of them though. Do you have any tutorials on how its done/want to do it.

I've actually added the definitions to DefinitelyType.  You can pull down the types via npm.

thanks @ncipollina i have added it to the readme and pulled those files in the repo and of course accredited yourself appreciate your help.
what did you build with the library anything you can share?
comit


Make requireAuth more ES6ish.

I always forget that we can do static methods but not properties. So weird ...

Btw, there should be const everywhere. Yeah, it something like requiring ; everywhere, but the gold is it prevents worthless endless bikeshedding.

Agree regarding using const.


cannot find a GRUB drive for /dev/sda1. Check your device.map.

hello guys, I can't change my boot loader from systemd to grub in nixos and have the following errors
/nix/store/b9lyl6cn5r3gwkhkzgbrsiaff1haq1k8-grub-2.06/sbin/grub-install: error: cannot find a GRUB drive for /dev/sda1. Check your device.map.
/nix/store/q3xj7v453vy78vrs4sz3w6lhy753pl3z-install-grub.pl: installation of GRUB EFI into /boot failed: No such file or directory
warning: error(s) occurred while switching to the new configuration
Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

I'm having this exact same error on a NixOS VPS from gandi.net, I've added my info:
nix-shell -p nix-info --run "nix-info -m"
these 4 paths will be fetched (0.71 MiB download, 9.84 MiB unpacked):
  /nix/store/2q1x5hazpr8yf5hh0pj09nmz94sc7q81-file-5.44
  /nix/store/ik9ibmq0rbznwyj6472lv2ab0c397lhy-gnumake-4.4.1
  /nix/store/5rbqiz11vagap5fsk3vw8fgznw6vxyrh-patchelf-0.15.0
  /nix/store/vfdg65hiv4bwls48588msw8la7452w2q-stdenv-linux
copying path '/nix/store/5rbqiz11vagap5fsk3vw8fgznw6vxyrh-patchelf-0.15.0' from 'https://cache.nixos.org'...
copying path '/nix/store/ik9ibmq0rbznwyj6472lv2ab0c397lhy-gnumake-4.4.1' from 'https://cache.nixos.org'...
copying path '/nix/store/2q1x5hazpr8yf5hh0pj09nmz94sc7q81-file-5.44' from 'https://cache.nixos.org'...
copying path '/nix/store/vfdg65hiv4bwls48588msw8la7452w2q-stdenv-linux' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.80, NixOS, 23.11 (Tapir), 23.11.5060.617579a78725`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos-23.05"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Please provide more information about your systems:

filesystem layouts
NixOS configuration for GRUB
UEFI/legacy?
and your NixOS metadata please.

I will repeat the same question.

I ran into this when accidentally trying to deploy to host A a configuration for host B. The GRUB device/partition in the error indeed did not exist on host A.


messagepack merge for release (RELEASE_net8_w_serde_20240401)

We are excited to review your PR.
So we can do the best job, please check:

[ x] There's a descriptive title that will make sense to other developers some time from now.

Reviewed.


logging: reorder designated initializers in __LOG macro

As C++ does not support designated initializers, including this file in a c++ file caused a compilation error.
I tested it with an application using mqtt and ethernet.
Signed-off-by: Alexander Polleti<EMAIL_ADDRESS>

Codecov Report

Merging #11311 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11311   +/-   ##
=======================================
  Coverage   51.55%   51.55%
=======================================
  Files         216      216
  Lines       27665    27665
  Branches     6937     6937
=======================================
  Hits        14263    14263
  Misses      10653    10653
  Partials     2749     2749

Impacted Files
Coverage Δ

include/logging/log_core.h
100% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

commit message should start from subsystem being modified, something like:
logging: reordered deignated initializers in __LOG macro

@andyross The toolchain is for STM32f4.

That's the hardware, what's the compiler?  You mean Keil, maybe? I was under the impression that Keil supported most gcc extensions like this.

It's the Gnu Compiler coming from zephyr-sdk 0.9.5. It's arm-zephyr-eabi-g++ (GCC) 6.2.0.
It support designated initializers, but they must follow the order of declaration within the struct. Let's say you have a the following code:
struct Foo {
        int a;
        int b;
};

int main()
{
        Foo right_order = {.a = 1, .b=2};
        Foo wrong_order = {.b = 1, .a=2};
}

I compiled it with g++ 8.2.0 for Ubuntu:
apolleti@apolleti-VirtualBox-Xubuntu:~/test$ g++ --std=gnu++17 main.cpp
main.cpp: In function ‘int main()’:
main.cpp:9:40: error: designator order for field ‘Foo::a’ does not match declaration order in ‘Foo’
         Foo wrong_order = {.b = 1, .a=2};
                                        ^

Or directly with the one from zephyr
apolleti@apolleti-VirtualBox-Xubuntu:~/test$ /opt/zephyr-sdk/sysroots/x86_64-pokysdk-linux/usr/bin/arm-zephyr-eabi/arm-zephyr-eabi-g++ --std=gnu++17 main.cpp
main.cpp: In function ‘int main()’:
main.cpp:9:40: sorry, unimplemented: non-trivial designated initializers not supported
         Foo wrong_order = {.b = 1, .a=2};
                                        ^
main.cpp:9:40: sorry, unimplemented: non-trivial designated initializers not supported


Support SQL in Pinot.

While existing PQL is almost similar to SQL, it has some nuances that make it difficult for users to query pinot.  Our eventual goal should be able to support most of the sql features on a single table (excluding joins). This will allow tools such as superset, grafana, etc to be work seamlessly on top of Pinot.
Currently, adding a new feature requires us to change pql grammar, broker request, and the execution layer. This means there is a high turn around time for each feature.
The right end state would be - "change only the execution layer to add new features  - grammar and broker request should be complete and flexible".  I am proposing we move to calcite and leverage the full sql support and parser that comes with Calcite.
Proposal

Create PinotQuery IDL(thrift)- this should represent the pql/sql. Additional information such as debugoptions should not be part of this IDL
Embed PinotQuery inside BrokerRequest.
AST Parser to convert PQL to PinotQuery

For backward compatibility, populate old objects in BrokerRequest (selection aggregation groupby etc) from pinot query.

Change the execution layer to use BrokerRequest.pinotQuery
Introduce another endpoint that takes calcite sql and converts it into brokerrequest

Suggest changing Enhanced Broker Request to Pinot Query to make them totally separate from each other. No need to nest them IMO.
For steps of migration:

Implement PQL -> Pinot Query and Pinot Query -> Broker Request
Support Pinot Query in Execution Layer (probably through a separate endpoint)
Implement SQL -> Pinot Query
(Optional) Remove PQL and Broker Request

Suggest changing Enhanced Broker Request to Pinot Query to make them totally separate from each other. No need to nest them IMO.
For steps of migration:

Implement PQL -> Pinot Query and Pinot Query -> Broker Request
Support Pinot Query in Execution Layer (probably through a separate endpoint)
Implement SQL -> Pinot Query
(Optional) Remove PQL and Broker Request

That's great.

@Jackie-Jiang yes, I would love to do this and this was how I started. The problem was that brokerrequest was very widely used in the code and it was very hard to replace it with pinot query in one shot.
That's why we put pinotquery inside brokerrequest which kind of makes sense if you think request consisting of query, debugoptions etc.
One key goal was to never have something like this in the query execution code.
//use broker request
} else {
  //pinot query
}```

If we keep old fields (selection, aggInfoList etc) and pinotQuery in the brokerRequest, we can migrate to pinotQuery in steps - operator by operator. For e.g. solve only the selection operator then transform operator and so on.

I agree with you only doubling the size of brokerRequest until we migrate the execution layer to use brokerrequest.pinotquery at which point we can delete the references to Selection, etc. I don't think this will add significant overhead in terms of network or cpu usage. We have the validation flag to test this easily.

Final Structure of BrokerRequest will be as follows
```BrokerRequest {
  PinotQuery pinotQuery;
  bool enableTrace;
  Map<String,String> requestOptions;
}```

@kishoreg Short term wise, we can nest PinotQuery into BrokerRequest so we can support the functionalities step by step if the overhead is not an issue. Long term wise, I'll still suggest replacing BrokerRequest with PinotQuery once all the functionalities are supported. enableTrace should be inside the debugOptions, and requestOptions should be part of queryOptions from PinotQuery.

@Jackie-Jiang, yes once we migrate the execution layer to work on PinotQuery, we can definitely move over to PinotQuery if needed.
The way I see it is broker takes in a bunch of request params - pql, enableTrace, debugOptions and we will add few more things in the future. The brokerRequest we have today makes sense because it captures everything. The only difference is that while enableTrace and debugOptions have 1:1 mapping in brokerRequest, pql is split into many different fields. Adding PinotQuery will encapsulate all elements of the pql/sql within it.
Anyways, we can revisit this when we refactor the execution layer to use PinotQuery.

Hi here, I was mostly a user for pinot but pretty new to the development - really glad to see that Pinot is adopting ANSI SQL through Calcite.
One question: based on the design description, seems like only the parser phase of the Calcite project is being considered here (Stringify SQL -> SQLNode); is there any plan to consider adopting more of the Calcite capacity, e.g. the optimizer?

@kishoreg - I missed seeing this issue earlier. It will be good to see the reasons for going the Calcite route. Based on internal discussions, it appears that leveraging Calcite for just parsing wouldn't yield a lot of benefit and infact might be harder to maintain than the corresponding antlr grammar based one.
Also, it will be good define how close to sql compliance we want to get and how PQL will evolve - will everything have to fit into sql parlance?

@walterddr the plan is to only use the parser phase of calcite. I don't see using the optimizers in calcite will provide any value because of the following

Most of the optimizers in calcite optimize the logical plan (suitable for complex joins/nested queries etc). We cannot leverage them since Pinot does not support joins and nested queries
Pinot comes up with per segment optimized physical plan based on each segment's metadata.  Calcite does not support this.

@sunithabeeram Yes, we are planning to use calcite just for parsing. I had the same opinion but I realized that it is more flexible and complete than the PQL grammar. Every feature we need to add in Pinot, we end up touching the grammar, the parser, and the execution layer. For e.g. supporting regex, expression, alias, map syntax etc. It's just a distraction and additional code to maintain.
We already tried converting sqlNode to BrokerRequest and it worked well for all the queries we have. The only exception is the options we have in Pinot and we will have to handle that separately.
Calcite is widely adopted and supporting those queries will allow us Pinot to be used easily with other UI tools.

Thanks for the explanation @kishoreg . Yeah I agree that many of the optimizations might not work for Pinot and can understand why this could be a good idea to separate the grammar changes from the other core changes.
One of advantages, as you also mentioned, is the optimizer's capability to simplify and optimize logical plan. This might open up some possibilities when writing standard SQL: for example, nested queries that are more readable, but ultimately can be compiled as a simple query.
Regarding metadata support, I wounldn't say there's no support on calcite but I think this is definitely a limitation. Similar problem has been raised in Flink's calcite metadata handler as well: https://issues.apache.org/jira/browse/FLINK-11822.

@walterddr I looked at the Jira link. If my understanding is right, I think the metadata it refers to is global and not per segment. In the case of Pinot, the physical plan is optimized on a per segment basis based on its metadata (cardinality, indexing, star-tree, dictionary etc)
Having said that, in future if we start supporting nested queries and look up joins, we might consider using the optimizers that come with calcite.

Thanks @kishoreg, I am not familiar with the usage of per-segment data stats in Calcite and not sure if that can be easily supported.
Thank you for the prompt clarification! they make perfect sense!

@kishoreg @Jackie-Jiang ,I am also a pinot user at present. When will this be online? I think it's great and I'm looking forward to it

I believe using Calcite can prove to be useful in the long run as we converge closer to standard SQL support and achieving parity with general OLAP systems. Calcite's rich grammar, parser, semantic analysis and logical planning optimization rules will all help towards Pinot supporting a wide variety of complex SQL queries, including nested queries, query rewriting, materialized view substitution etc.
I say logical planning because physical planning or execution planning is something that Pinot will have to do because the standard operator tree will then be optimized and divided into per segment execution fragment.
As part of SQL support, what do people think about supporting some flavor of distributed joins? especially broadcast join which can be very helpful for large star schema joins having a large fact table and multiple smaller dimension tables and we can broadcast the smaller dimension table to each node and do a local in-memory hash join.

We have deliberately stayed away from implementing joins within Pinot. Having said that, lookup join is definitely on the table. If you are interested in contributing, please create an issue and start the discussion.

Can we use Calcite to support adding, subtracting, multiplying and dividing aggregates,For example: SUM(a) /1024, SUM(a) /SUM(b) /1024, (SUM(a) * 1000) /SUM(a), etc

Proposed the  changes in execution layer in order to simplify the sql rollout.
https://docs.google.com/document/d/1uNIq0cybUtVtdtJ38-4ewFNEQorbg-2KYr-CMSj6H_8/edit?usp=sharing

This is done and is available since 0.3.0


Improve docker support

@akatsoulas @flamingspaz I refreshed a bit the docker support on remo

Use scripts to run docker commands for dev/prod
Use gunicorn for prod
Limited the permissions to the docker user


Add Counter PDA Tutorial - Easy

I have created a Counter PDA Tutorial  for the Solana Playground. This will be an easy tutorial to get a better understanding of accounts, PDAs, and  how basic operations work on Solana Anchor Programs.
Is designed to be an introductory tutorial, where the user will have to fill the gaps in functions following the instructions from the pages of the tutorial.

Thank you so much for making this! I've requested a small change and could you please run yarn format because CI will fail with the current formatting.

Merged! Thanks again, one more small thing: it would be better to name the folder with React's naming convention CounterEasy instead of Template_counter. It's not a big deal but it's nice to have a standart naming convention.

Perfect!! I will change the folder name and pull request again.
Thanks!!


Error when the DB schema is modified.

This works with one version of the database and if we migrate the database to a newer version and modify the tables a bit. This causes error.
One scenario is adding an extra field to a relation and after migration this plugin causes errors.

@mubashirhanif I am happy to guide you through a PR and I just send out an invitation to the Bonaval organization.

Hi @mubashirhanif,
When you migrate your database, you MUST migrate the history tables too.
We're using this plugin in a large scale application where we migrate the database manually using Sequelize QueryInterface. Whenever a Temporal model is migrated, we write two migration scritps:

One for the actual table
One for the history table

Can you confirm this is your issue ?


add support for anthropic, azure, aleph alpha, ai21, togetherai, cohere, replicate, huggingface inference endpoints, etc.

Hi @AntonOsika,
Following up on this PR - https://github.com/AntonOsika/gpt-engineer/pull/574.
I fixed the streaming bugs and confirmed it works with azure.
Here is the gpt-engineer working with my deployed azure instance:

Here is the gpt-engineer working with ai21's "j2-mid" model:

For those trying to use WizardCoder / Phind-CodeLlama, we (+ this PR) also provides support for Huggingface Inference Endpoints and Baseten.
https://docs.litellm.ai/docs/completion/supported
If anyone's using gpt-engineer in production, and would like to split traffic between a finetuned model and gpt-4 - they can do that too: https://docs.litellm.ai/docs/tutorials/ab_test_llms
Please let me know if this PR looks good or you'd still prefer to stash it.
Happy to make any changes / update docs, if the initial PR looks good.

@ErikBjare what do you think of this?
It feels like it's too much have both:

API_BASE_URL
Azure flags
LiteLLM

We should simplify and pick a subset (maybe just one?) of all of these!

@AntonOsika happy to make any changes as necessary 🙂

Thought about it and I think we should go for it! @krrishdholakia
Do we still need the special azure parameters after this? Would be great to have that taken care of by env variables + litellm instead of code bloat!

Hey @krrishdholakia I got this and reverted:

Do you have any ideas why?

What version of langchain were you using?

Hey @AntonOsika here's chatlitellm working for replicate and cohere

Here it is for OpenAI + Anthropic

Can you please let me know the version you're using so i can debug this?

Hi @AntonOsika,
Following up on this PR - #574.
I fixed the streaming bugs and confirmed it works with azure.
Here is the gpt-engineer working with my deployed azure instance:
Here is the gpt-engineer working with ai21's "j2-mid" model:
For those trying to use WizardCoder / Phind-CodeLlama, we (+ this PR) also provides support for Huggingface Inference Endpoints and Baseten. https://docs.litellm.ai/docs/completion/supported
If anyone's using gpt-engineer in production, and would like to split traffic between a finetuned model and gpt-4 - they can do that too: https://docs.litellm.ai/docs/tutorials/ab_test_llms
Please let me know if this PR looks good or you'd still prefer to stash it.
Happy to make any changes / update docs, if the initial PR looks good.

How do someone use GPT 3.5 turbo Fine tuned models in it?


Does Anyone else have integration issues?

Hello,
Does anyone have vcpkg integration issues? I can get vcpkg intellisense on Windows C++ Projects. But do not get any vcpkg intellisense on Linux and Cmake Projects. On Linux I can only get the WSL packages and not the VCPKG packages.
I tried refreshing remote intellisense headers and had no luck.
Any advice?

@odin-loki, thanks for posting this issue. You can create cmake project and link the vcpkg's library on Linux. Could you provide a simple repro project?

Hello,
The issue here was a warning message in a Visusl Studio asking for a remote linux connection when using the Linux Subsystem. Visual Studio uses the Subsystem automatically OR the Linux Remote Connection.

From: Lily<EMAIL_ADDRESS>Sent: Wednesday, February 19, 2020 8:27:53 PM
To: microsoft/vcpkg<EMAIL_ADDRESS>Cc: Odin<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/vcpkg] Does Anyone else have integration issues? (#7183)
@odin-lokihttps://github.com/odin-loki, thanks for posting this issue. You can create cmake project and link the vcpkg's library on Linux. Could you provide a simple repro project?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vcpkg/issues/7183?email_source=notifications&email_token=AGJ7D5KXSRSFKJE3FEE6F6TRDT3RTA5CNFSM4H6SOPSKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMHAF2A#issuecomment-588120808, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGJ7D5I3P7IU532IHYCJPYDRDT3RTANCNFSM4H6SOPSA.

@odin-loki, does this still be a problem for you?

No.

From: Phoebe<EMAIL_ADDRESS>Sent: Thursday, March 4, 2021 9:13:48 PM
To: microsoft/vcpkg<EMAIL_ADDRESS>Cc: Odin<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/vcpkg] Does Anyone else have integration issues? (#7183)
@odin-lokihttps://github.com/odin-loki, does this still be a problem for you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vcpkg/issues/7183#issuecomment-790499844, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGJ7D5JRPDHDI2QVLJE5MQTTB5MNZANCNFSM4H6SOPSA.

Thanks for your quick response!


docs: sort user with alphabetical

Some pull request don't add correct position, so we need update it.

Deploy preview for docusaurus-2 failed.
Built with commit 1e05475b6b741d926756ccde0d7105ceff4585b4
https://app.netlify.com/sites/docusaurus-2/deploys/5cddab8bf4a3db000be6f34a


cannot produce result

Thanks for making this package. Please assist me with a minimal example.
My versioninfo():
Julia Version 1.8.1
Commit afb6c60d69a (2022-09-06 15:09 UTC)
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: 32 × AMD Ryzen Threadripper 1950X 16-Core Processor
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-13.0.1 (ORCJIT, znver1)
  Threads: 1 on 32 virtual cores

I have a notebook file s2.jl with content:
### A Pluto.jl notebook ###
# v0.19.9

using Markdown
using InteractiveUtils

# ╔═╡ dd19e674-41dc-11ed-2632-45d65300f4b7
c = 23

# ╔═╡ 2c98b39e-cb1f-4d42-9712-b17871cda345
b =2

# ╔═╡ 9ce351f4-a128-4a12-861d-dba6e0475324
a=sqrt(b^2+c^2)

# ╔═╡ 00000000-0000-0000-0000-000000000001
PLUTO_PROJECT_TOML_CONTENTS = """
[deps]
"""

# ╔═╡ 00000000-0000-0000-0000-000000000002
PLUTO_MANIFEST_TOML_CONTENTS = """
# This file is machine-generated - editing it directly is not advised

julia_version = "1.8.1"
manifest_format = "2.0"
project_hash = "da39a3ee5e6b4b0d3255bfef95601890afd80709"

[deps]
"""

# ╔═╡ Cell order:
# ╠═dd19e674-41dc-11ed-2632-45d65300f4b7
# ╠═2c98b39e-cb1f-4d42-9712-b17871cda345
# ╠═9ce351f4-a128-4a12-861d-dba6e0475324
# ╟─00000000-0000-0000-0000-000000000001
# ╟─00000000-0000-0000-0000-000000000002

I did Pluto.run() in a separate REPL, and started a new REPL for PlutoRESTClient. The notebook file s.jl is in the working directory of the REPL. I got the following in the new REPL:
julia> using PlutoRESTClient

julia> nb = PlutoNotebook("s.jl")
PlutoNotebook("http://localhost:1234", "s.jl")

julia> nb.c
ERROR:
Stacktrace:
 [1] getproperty(with_args::PlutoRESTClient.PlutoNotebookWithArgs, symbol::Symbol)
   @ PlutoRESTClient ~/.julia/packages/PlutoRESTClient/solHB/src/PlutoRESTClient.jl:185
 [2] getproperty(notebook::PlutoNotebook, symbol::Symbol)
   @ PlutoRESTClient ~/.julia/packages/PlutoRESTClient/solHB/src/PlutoRESTClient.jl:113
 [3] top-level scope
   @ REPL[4]:1

caused by:
Stacktrace:
 [1] evaluate(output::Symbol, filename::String, host::String; kwargs::Base.Pairs{Symbol, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
   @ PlutoRESTClient ~/.julia/packages/PlutoRESTClient/solHB/src/PlutoRESTClient.jl:40
 [2] evaluate(output::Symbol, filename::String, host::String)
   @ PlutoRESTClient ~/.julia/packages/PlutoRESTClient/solHB/src/PlutoRESTClient.jl:24
 [3] getproperty(with_args::PlutoRESTClient.PlutoNotebookWithArgs, symbol::Symbol)
   @ PlutoRESTClient ~/.julia/packages/PlutoRESTClient/solHB/src/PlutoRESTClient.jl:180
 [4] getproperty(notebook::PlutoNotebook, symbol::Symbol)
   @ PlutoRESTClient ~/.julia/packages/PlutoRESTClient/solHB/src/PlutoRESTClient.jl:113
 [5] top-level scope
   @ REPL[4]:1

Do you know if Pluto notebook publishes its API specifications? Did you figure it out from the source code? If I know the API specs, I can try to directly use HTTP packages to interact with Pluto notebooks or contribute to this package.

This package cannot work anymore with Pluto v0.19.9. Direct access to the Pluto Notebook webpage does pose a serious security threat.


Update benchmark action

Pull request details
Describe the changes made in this pull request
Use a new benchmarking package, AirspeedVelocity.jl.
Benchmark on Pull Requests now IF there is a label benchmark.
There will be a benchmark comment, much nicer than before.
Benchmarks will use the EU data set.
Benchmarking will be slow, but it will show the comparison results in the screen.
List of related issues or pull requests
Closes #235
Collaboration confirmation
As a contributor I confirm

[x] I read and followed the instructions in README.dev.md
[ ] The documentation is up to date with the changes introduced in this Pull Request (or NA)
[ ] Tests are passing
[ ] Lint is passing


UX1 config and UX2 config model

Pull Request summary:
Provide draft of UX1Config and UX2Config models which will be used in migration
Bump release version to 0.30.0
Checklist:

[x] Make sure to run pre-commit before committing changes
[x] Make sure all checks have passed
[x] PR description is clear and comprehensive
[x] Mentioned the issue that this PR solves (if applicable)
[x] Make sure you test the changes

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/pull/457


MediaControls: replace new_with_name with new

This fixes #64. I didn't find new_with_name in the docs for MediaControls, so just replaced it with new.

Thank you, the new_with_name MPRIS stuff is in souvlaki master, I've updated the Cargo.lock.


Create Brand Guidelines doc

Overview
We need to tell people when and how to use our logo
Actions

[ ] Write up minimum criteria
[ ] Send to editor for language polishing
[ ] Give to Chali for inclusion on Share the CTI

We are trying to write about how to use our logo on the page below and are thinking about using the language:
Our logo can be used the following way:

If you want to use it on your website to show that you have joined the civictechindex
If your  have added the topic tag civictechindex to your project, and your project is open source and civic in nature, then please feel free to use our logo on your site
If you want to mention the civic tech index in an article, and want to feature the logo in the article or on a social media preview
If you make your own interface that searches the index and want to show where the inspiration came from

Or contact us for other uses.

Use of our logo is encouraged under the following circumstances:

Your have listed your project on Civic Tech Index
You have added the topic tag "civictechindex" to your project repository [right?]
You have developed your own interface to search the Index
In articles or social media posts featuring Civic Tech Index.

For all other uses, please contact us for permission.

@myastark perfect!  @chalimar see https://github.com/civictechindex/website/issues/30#issuecomment-623213839 for the brand usage text


Fix stripe calling validation rule

Originally tried to fix in #443 but needs to be done on a branch of this repo for the actions to run properly
Correct validation rule for Stripe Calling is list:: regex search -?\d+

On closer inspection this line has both valid values and a conflicting validation rule
Stripe Calling,"Tool used for identifying architectural stripe-forming, interaction hotspots.","MACS2, Other",,,TRUE,Sequencing,,,list::-?\d+

Per the RFC this should not have a validation rule just the valid values


add validator Bit Cat

Please make sure your node is up and running now. Join #validators on Discord for help: https://discord.gg/QeJWCrE.


Regarding Depth Range Consistency in Different Scenes

Hi there,
Firstly, I want to express my appreciation for the excellent work you've been doing.
I've been following the discussions around the reconstruction scales in colmap. I've noticed that the reconstruction in Instant-NGP, along with the rendered depth, maybe involves an arbitrary scale, leading to potential variations in depth scales across different scenes. This becomes particularly pronounced when considering scenes of similar physical size but reconstructed with different scales.
My main query revolves around the selection of three virtual baselines (b = 0.5, 0.3, 0.1 units) for data generation across all scenes, as mentioned in your paper. Considering that scenes, such as A and B, may have distinct reconstruction scales in colmap, resulting in different depth ranges, I'm curious about the reasoning behind using the same baselines for all scenes. Given the potential disparity in depth range caused by different reconstruction scales, how does the uniform application of baselines account for this variability?
I appreciate your time and insights into this matter.
Thank you in advance!

Hi!
Thank you for your kind words! We really appreciate your interest in our work.
The reason we opted for the three virtual baselines (b = 0.5, 0.3, 0.1) across all scenes is because we wanted to make sure our generated depth maps cover the entire disparity range (from 0 to the desired D_max).  In Section 4 of the paper, particularly highlighted in Figure 5, we briefly discussed this aspect.
So, in our work, we're not particularly concerned about scenes like A and B having different reconstruction scales in colmap, resulting in varied depth ranges. Instead, our main goal is to create disparity maps that span a wide range of disparities. We achieve this by playing with different baseline values.
Moreover, a key point to mention in that our approach offers the flexibility to achieve extensive disparity ranges even with images sourced from outdoor scenarios, resulting in depth variations very different from those observed in our indoor scene dataset.
I hope this clarifies your doubts on the baseline selection. Feel free to ask if you have more questions.
Thanks again for your interest!


test: for testing ingest sst in lightning

What is changed and how it works?

Issue Number: Close #xxx

What's Changed:

Related changes

[ ] PR to update pingcap/docs/pingcap/docs-cn:
[ ] Need to cherry-pick to the release branch

Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Release note

/hold


Querying supported PixelFormat? And issues arising

Hello TIS
We have been lent a VGA camera (DFK 23G 618) whilst waiting delivery of some 4K versions. This is causing me some problems. Questions arising:

The devicePropertyMap content does not appear to be consistent with the DFK 33GX545. For example any attempt to set the image width/height fails with the following message

I am aware that the VGA camera only supports a single resolution but the error message is surprising.
What is the correct way to query and display the current camera pixel format? Setting like this seems to work but the VGA camera image data does not render correctly. It looks like it might be still sending some YUV format?

			static constexpr ic4::PixelFormat dev_format = ic4::PixelFormat::BGR8;
			ok = map.setValue(ic4::PropId::PixelFormat, dev_format, err);

This image is rendering what I think is 24bpp data with dimensions of 640x480:

Is there an IC4 function to convert an imageBuffer (whatever its format) to Windows style BGR (24bpp) or BGRA (32bpp)? All I can find are the write to a bitmap file family.
This camera has also shown a tendency to disappear. It is using the latest GigE and IC4 installations with the camera attached to a Netgear POE switch and connected directly to an i9 equipped PC.

Thanks again for listening. Any advice much appreciated.

A little bit more information. Attempting to set the pixel format directly generates the following error. What is the correct enumeration for BGR mode?
	static constexpr ic4::PixelFormat dev_format = ic4::PixelFormat::BGR8;
	ok = map.setValue(ic4::PropId::PixelFormat, dev_format, err);
	s = u::sprintf("setValue: PixelFormat::BGR8 %s %s", ok ? "true" : "false", err.message().c_str());

Hi Jerry,
you are right, those write errors are annoying. We will think of a way to avoid them.
The image you posted looks like 8-bit data being interpreted as BGRA (32bpp).
Simplest way to get BGR8 data is to set the sink format as BGR8 (in the sink's constructor) and leave the camera's PixelFormat (which is what actually goes over the wire) as Bayer8. ic4 will then automatically convert all images to the specified pixel format.
The camera itself does not support the BGR8 format, therefore you get the error when trying to set it. A more descriptive error message might be helpful here.
If you only want to convert select images, there is a way:
// (typed into github issue, I hope this compiles...)

ic4::ImageBuffer convertToBGRA32bpp( std::shared_ptr<ic4::ImageBuffer> srcBuffer )
{
    // First, create a buffer pool to generate additional buffers
    auto pool = ic4::BufferPool::create();

    // Define the format for destination buffer
    auto destType = ic4::ImageType( ic4::PixelFormat::BGRa8, srcBuffer->imageType().width(), srcBuffer->imageType().height() );

    // Allocate the destination buffer
    auto destBuffer = pool->getBuffer(destType);

    // Copy from source to destination
    destBuffer->copyFrom( srcBuffer );

    return destBuffer;
}

Using the buffer pool looks a little cumbersome in this example, but it works great if you continuously transform buffers this way since it reuses memory if possible.
The copyFrom function does not necessarily support all possible pixel format conversions, but there usually is support converting to BGRa8.

Hi Tim, thanks again
OK so the quick fix is your suggestion re the sink. Sadly this fails using the DFK 33GX545 as shown below. Code snip included in case I've misunderstood something essential.
// Create a QueueSink to capture all images arriving from the video capture device
sink_t qsink = ic4::QueueSink::create(nl, ic4::PixelFormat::BGRa8, err);
// Start the video stream into the sink
ok = grabber.streamSetup(qsink, ic4::StreamSetupOption::AcquisitionStart, err);
if (!ok) {
	MessageBoxA(args.hWnd, err.message().c_str(), nullptr, MB_OK);
	return;
}

Looks like BGR8 -> BGRa8 is the one transformation that does not work...
If you set camera's PixelFormat to Bayer8, this should work (and, as a bonus, you get a higher maximum frame rate).

Hi Tim,
FYI, the only combination I've got to work is to set the camera to use ic4::PixelFormat::BayerRG8 and to then open the imageSink like so:
        // set the camera format as per https://github.com/TheImagingSource/ic4-examples/issues/7
	ic4::PixelFormat ipf = ic4::PixelFormat::BayerRG8;
	ok = map.setValue(ic4::PropId::PixelFormat, ipf , err);

	// Create a QueueSink to capture all images arriving from the video capture device
	sink_t qsink = ic4::QueueSink::create(nl, ic4::PixelFormat::BGR8, err);

otherwise I get errors.
Does this mean various cameras support different Bayer flavours? There is surely a common default?
Kind of a nuisance, so let me circle back to the question which was:
How do I enumerate the pixel formats a camera does support?
Thanks for listening.

map[ic4::PropId::PixelFormat].entries() will get you a vector of ic4::PropEnumEntry which you can query for name() or displayName().
And yes, the variety of bayer pattern is camera-specific.

Hi,
So, attempting to set a Bayer mode on the DFK 23G 618 ends up with this error message, which is not the case for the DFK 33GX545. Any thoughts? Which pixel format(s) do you think should work?

BayerGB8 should work (0x0108000A)

In a future release there will be a pseudo-pixelformat value that can be used to directly set any bayer format with a specified bit depth, regardless of the actual pattern. Enumerating formats and make decisions based on what is available is not something one should be forced to do.

Setting any bayer pixel format supported by the camera has been simplified in ic4 Version 1.1: PixelFormat::AnyBayer8

Good to know. Thanks Tim.


Node.js parse error in Logs

What information do your need from me to better debug this error?
2017-05-20T12:18:29.139Z	6e248c53-3d56-11e7-b21c-3705fa92333b	SyntaxError: Unexpected token (
at Object.parse (native)
at LineStream.<anonymous> (/var/task/index.js:35:18)
at emitOne (events.js:77:13)
at LineStream.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:146:16)
at LineStream.Readable.push (_stream_readable.js:110:10)
at LineStream.Transform.push (_stream_transform.js:127:32)
at LineStream._pushBuffer (/var/task/byline.js:123:17)
at LineStream._transform (/var/task/byline.js:114:8)
at LineStream.Transform._read (_stream_transform.js:166:10)

You probably have something in your Go code printing to stdout instead of stderr.

oh wow this is old hahah :D closing, but yep stdout is off limits for now


docs: armor-mod-config is severely behind.

The dev names we were using for the armor mods are no longer needed. They have been updated to their new names we made using the "string" words that we have access to in forge.
We came to the conclusion of what game states the armor mods were going to be unlocked. This has been updated as well.
Upgraded Walking has now been fully tested and so it was required to be added. While Upgraded Walking gives you a passive boost to your strafe and or walking speed, Upgraded Sprinting is focused on giving you a passive boost to your actual sprint speed. These two armor mods function as inverse of each other and come with other added benfits that the other does not receive.

Looks great. Added some extra info about MA5K ammo for Patrol Case and Grenade Operator functions at the same time.


fix: build-args is list type not CSV type

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


Refactoring in integration testing code

Description of changes
Some refactoring in preparation to move the integration tests to their own repository. This PR has the edits I wanted to make in #632, but closed to avoid potentially breaking users. As suggested by @andrewmwells-amazon, I left the current testing code in cedar-policy unchanged (marking it as "deprecated") and made a new cedar-testing crate to use moving forward.
The cedar-testing crate will be treated like our other internal crates (e.g., cedar-policy-core) in the sense that we may make changes without respecting semver.
Issue #, if available
Checklist for requesting a review
The change in this PR is (choose one, and delete the other options):

[X] A backwards-compatible change requiring a minor version bump to cedar-policy (e.g., addition of a new API).

I confirm that this PR (choose one, and delete the other options):

[X] Updates the "Unreleased" section of the CHANGELOG with a description of my change (required for major/minor version bumps).

I confirm that cedar-spec (choose one, and delete the other options):

[X] Requires updates, and I have made / will make these updates myself. (Please include in your description a timeline or link to the relevant PR in cedar-spec, and how you have tested that your updates are correct.)

Disclaimer
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

PR to fix CedarDRT build failure is in cedar-spec#250.
The SemVer failure is expected since this PR requires a major version bump.


Support Carthage

Please make this package conform to Carthage

Fixed.

Great!

Edit: It doesn't seem to be fixed at this point. You need to make your build scheme public to make this work!

Sorry, missed that one. Now published schemes.

Thanks man!


charts don't look good when minimize

Currently the charts keep the old aspect ratio

It doesn't seem consistent. It happens on my laptop, but not on my computer.


Update demos to Iceberg 0.13.0 / Nessie 0.18.0

@nastra : Should it be nessie 0.19.0 ? Because 0.18.0 has old nessie spark extensions ?

It needs to be Nessie 0.18.0 I believe (the version that is being used in Iceberg 0.13.0), but worth trying if we can use Nessie 0.19.0

It needs to be Nessie 0.18.0 I believe (the version that is being used in Iceberg 0.13.0), but worth trying if we can use Nessie 0.19.0

but version that is being used by iceberg is not having the latest nessie spark extensions due to our circular dependency. So, I think it cannot be 0.18.0 as demos need nessie spark extensions.

maybe the flink demo could be updated to Flink 1.14.0 along the way due to https://github.com/apache/iceberg/commit/2d4b0ddc76fd47aa27ca4972d4f3a6f256921c58

it was noticed that the demo links to https://projectnessie.org/tools/spark/ but it should be https://projectnessie.org/tools/iceberg/spark/
so we should also update that

note to @XN137 : You can try with nessie 0.18.0, but I think nessie spark session extensions were upgraded in 0.19.0 so it will not work.
There is a circular dependency,
Nessie makes a release (0.18.0)-> Iceberg makes a release with that nessie (0.13.1) -> nessie updates its spark extensions with that iceberg version (0.19.0)
If it works on 0.18.0, let me know also. I am also curious to see whether my understanding is right or not.


Create Profile for Mawa kaward

Name
Mawa kaward
Profile Image

Country
Uganda
Region
West Nile
Organisation
Community Initiative for Rehabilitation and Transformation
Languages
English (Good), Juba Arabic (Good), Kakwa (Native)
Skill 1
Community & Moderation
Qualifications for Skill 1
Holding Diploma in Community Development
A GBV activist
Skill 2
Organizational Development
Qualifications for Skill 2
The executive director of CIRT and the Co-Funder
Skill 3
Sustainability & Environment
Qualifications for Skill 3
Environmental and Climate change advocate
Skill 4
None
Qualifications for Skill 4
No response
describe yourself
Mawa Kaward is a community development professional and the executive director of CIRT (Community Initiatives for Rehabilitation and Transformation), an organization dedicated to promoting sustainable development in rural communities. He holds a diploma in Community Development and Project Management, and has extensive experience in designing and implementing community-based development projects.
Throughout his career, Mawa has demonstrated a strong commitment to empowering rural communities and promoting inclusive and sustainable development. He has worked with a wide range of stakeholders, including government agencies, NGOs, and community groups, to develop and implement programs that address the unique needs and challenges of rural communities.
As the executive director of CIRT, Mawa is responsible for overseeing the organization's strategic direction and operations. Under his leadership, CIRT has continued to expand its reach and impact, working with communities across the settlement to promote sustainable development and improve the quality of life for refugee communities .
Mawa's dedication to community development and his commitment to empowering rural communities have earned his widespread respect and recognition. He is widely regarded as a leader in his field, and his work has been recognized by a number of organizations and institutions.
E-Mail
<EMAIL_ADDRESS>Phone
+256786188827
WhatsApp
No response
Website
No response
Telegram
No response
GitHub
No response
LinkedIn
No response
Twitter
No response
Facebook
No response
Instagram
No response
Mastodon
No response
WikiFab
No response
Other
No response

profile created


[Feature Request] Allow the link subtitle to be blank

When trying to add a link, it requires a subtitle which might not always be needed.
It would nice to have the option to not use a subtitle.
Thanks

Hello @urmomsangus,
Thank you for this feature request, I have implemented it now and it will be available in the next release.
Thanks
Amr Hesham

My sincerest thanks, it works perfectly.


Improve eval call parsing.

#3327 should land first.

The CI error due to fatal: unable to access 'https://github.com/jerryscript-project/jerryscript.git/': Failed to connect to github.com port 443: Timed out which is unrelated to the content of the PR.


The generated CRD yaml can't pass kubeconform -ignore-missing-schemas -strict

It fails with
CustomResourceDefinition clickhouseinstallations.clickhouse.altinity.com failed validation: error unmarshalling resource: error converting YAML to JSON: yaml: unmarshal errors:
  line 311: key "description" already set in map
  line 384: key "type" already set in map
  line 394: key "description" already set in map
  line 397: key "description" already set in map
  line 400: key "description" already set in map
  line 410: key "description" already set in map
  line 413: key "description" already set in map
  line 416: key "description" already set in map
  line 419: key "description" already set in map
  line 429: key "description" already set in map
  line 528: key "description" already set in map
  line 528: key "description" already set in map
  ...

Probably because TypeStringBool has description and type fields, but we try to override them later, which is not allowed by kubeconform. Can we somehow fix it?

don't be shy to make PR
to https://github.com/Altinity/clickhouse-operator/tree/master/deploy/builder/templates-install-bundle


proposal: crypto/tls: support DHE

What version of Go are you using (go version)?

$ go version
go1.9.2

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
linux/amd64

What did you do?
Work for NOKIA and we are planning to develop API Gateway with go for Telecom Apps.

What did you expect to see?
We want that go-lang to support following cipher suites as well. I have read one reply that DHE is slow and support is dis-continued in browser but I think now go is not only about browser but because of cloud-native drive even telecom clouds will use REST based apps and I see that go plays important role as it has enriched eco-system. The traditional model use openssl and it supports all these ciphers already. I want to see go-lang also be in par with  openssl as it shall not just about Browsers anymore :-)
For Telco Cloud Apps these are still good to have instead of just only ECDHE as to be feature-Parity.  I assume K8S [ which also seems in go ]  and creating foot-prints in telco cloud having such support in golang is not only good but also appears more like "shall have "  :-)
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (DH 2048)
TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 (DH 2048)
TLS_DHE_RSA_WITH_AES_128_CBC_SHA (DH 2048)
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (DH 2048)
TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 (DH 2048)
TLS_DHE_RSA_WITH_AES_256_CBC_SHA (DH 2048)
TLS_RSA_WITH_AES_256_CBC_SHA256 (RSA 2048)
What did you see instead?
No Support for DHE

The traditional model use openssl and it supports all these ciphers already. I want to see go-lang also be in par with openssl as it shall not just about Browsers anymore

For Telco Cloud Apps these are still good to have instead of just only ECDHE as to be feature-Parity

Feature parity in itself isn't a goal. What stops "Telco Cloud" from using modern ciphers instead?

Hi
I think the point is not more specifically about feature parity but more
about accommodative solution offering.
If some solution offers only latest the vast investment and vast volume of
solution on the field can be invalidated because of new better ciphers.
Even if you check opened which is more like standard for crypto also did
not invalidated these ciphers ....
I see this way go is going to be more accommodative like openssl and enrich
further it's offering in crypto package...
I see there was one fork made in some earlier response for such request but
I think it will be better if such support can be added natively from go
lang community...
Also how much is the effort do you see to add it...
Thanks in advance
Swan
On Thu, 9 May, 2019, 18:28 Dominik Honnef<EMAIL_ADDRESS>wrote:

The traditional model use openssl and it supports all these ciphers
already. I want to see go-lang also be in par with openssl as it shall not
just about Browsers anymore
For Telco Cloud Apps these are still good to have instead of just only
ECDHE as to be feature-Parity
Feature parity in itself isn't a goal. What stops "Telco Cloud" from using
modern ciphers instead?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/31933#issuecomment-490891770, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALI63UW26DQCJK6JB6LKXADPUQNVPANCNFSM4HLX36BA
.

OpenSSL has historically implemented almost every available feature, which has resulted in a bloated and complex implementation with several vulnerabilities. Go is taking the approach of implementing the (slightly more than minimum) necessary functionality to be useful so that the codebase is reasonably easy to understand and thus much less likely to be vulnerable.
DHE as implemented in TLS is a massive footgun, as there's no enforced standardisation of groups. I think there would need to be a pretty compelling reason to add new functionality which is arguably less secure than what's already present.

Hi
The more compelling reason, I can think is ROI for each customer who has vast volumes of deployment. If the new solution completely makes them unusable then it is big business loss to them and cant compel  upgrade if they dont wish to . For telco eco-system it is more a "business loss"
I have few questions now
Q:  If no TLS Config is not passed to go-lang net/http Server which uses ListenAndServeTLS, will it accept the client connection with ciphers not mentioned in cipher_suites ?
Q: If we still wish to add support for
DHE-RSA-AES256-GCM-SHA384
DHE-RSA-AES256-SHA256
DHE-RSA-AES256-SHA
AES256-GCM-SHA384
AES256-SHA256
AES256-SHA
DHE-RSA-AES128-GCM-SHA256
DHE-RSA-AES128-SHA256
DHE-RSA-AES128-SHA
AES128-GCM-SHA256
AES128-SHA256
AES128-SHA
What does it mean ?  only adding those constants  and test stub for it OR
It means complex implementation for these apart from what you already have in crypto/tls ?
Q:  As I mentioned about the business case, do you have any suggestion what is best way to do it if we still wish to lock on crypto/tls or move to other fork  ?
Thanks
Swan

Any Comments on above questions ??  Can we use external TLS stack with net/http ?

Provided the external TLS stack has the same overall behaviour (transparently and automatically performing a handshake) and has a net.Listener interface then you can use it easily enough with a server:
srv := &http.Server{ /* ... */ }
ln, err := tls.Listen( /* ... */ )
if err != nil { /* handle error */ }
srv.Serve(ln)

Supporting an external TLS stack with an HTTP client would be a little more involved but you'd essentially create a new http.Transport and override DialTLS with a function dialing using the TLS package.

Our source Code is something like
 s.server = &http.Server{ Addr:         address, Handler:      handler,
	ReadTimeout:  s.globalConfig.RespondingTimeouts.ReadTimeout,
	WriteTimeout: s.globalConfig.RespondingTimeouts.WriteTimeout,
	IdleTimeout:  s.globalConfig.RespondingTimeouts.IdleTimeout,
}
listener, err := net.Listen("tcp4", address
....
...
s.server.ServeTLS(listener, s.globalConfig.TLS.CertFile, s.globalConfig.TLS.KeyFile)

We are not using tls.Config which is part of http Server Structure member.
Q:  If in server instantiation if we dont use tls.Config will it still using go-lang specific crypto implementation  in ServeTLS  code  ?
Q:  In the crypto/tls package there is a note " Package tls partially implements TLS 1.2, as specified in RFC 5246" What are exceptions from RFC 5246 which is not supported by this package ??
Quick search results in:
https://godoc.org/github.com/spacemonkeygo/openssl#NewListener
Looks like this can be used as wrapper around if we wish to use openssl TLS stack.

@FiloSottile

We are very unlikely to implement finite field DH in crypto/tls for the reasons mentioned by @jamie-digital. It's a bad design, very hard to implement securely and in constant time, and superseded by ECDHE. I am also unaware of any clients that support DHE but not the plain RSA ciphers, which we carry along for compatibility (and so we can avoid adding the complexity of things like DHE instead). Feature parity is explicitly a non-goal of crypto/tls.
I am going to leave this open to collect feedback, but it's not at all planned.

What about my other question ?
"Q: In the crypto/tls package there is a note " Package tls partially implements TLS 1.2, as specified in RFC 5246" What are exceptions from RFC 5246 which is not supported by this package ??"
Can you please comment what are the exceptions this package does not support from RFC 5246 compliance !!!

As far as I know, we implement everything that is REQUIRED by RFC 5246, so we are in full compliance with it. There is no list of what's not implemented, but what is implemented is documented at https://golang.org/pkg/crypto/tls.
If you have other questions unrelated to this proposal, please open a new issue or see https://golang.org/wiki/Questions.

Thanks for quick response, I would  then suggest it is better to change the documentation to reflect it else it's kind of misleading as it is first thing be read in the Overview Section of this package documentation itself

I think it's fair to say that the package "partially" implements TLS 1.2 in that it doesn't implement the entirety of RFC 5246. There are optional features left unimplemented, such as the DHE key exchange (which is why we're having this discussion), server-initiated renegotiation, signatures using MD-5, and so on.

I would then suggest it is better to change the documentation to reflect it else it's kind of misleading as it is first thing be read in the Overview Section of this package documentation itself

Thanks for the suggestion. I've opened issue  #32079 to track this.

Based on the discussion above and the lack of activity, this seems like a likely decline.

No change in consensus, so declining.


#67 Create Sprite for Glock-18

Looks good, but the pixels are very large again. Could you please make them 1x1? :smiley:

Thanks! :+1:


Fix version calulation

Use CMAKE_MATCH_COUNT and CMAKE_MATCH_<n> instead of REGEX REPLACE
Also fix the version number determination when not using a locally cloned repository

Thanks, this works for me.