ConnectionLine occasionally throws an error

Hi,
I'm having an issue when trying to connect a node.
This specific node was loaded over http from a hook (useEffect) and only has a source port.
When I try to draw an edge I sometimes receive an error immediately and other times it manages to render the line but after a certain amount of ticks throws the same error.
I traced the issue back to this line:
  const sourceHandle = handleId
    ? sourceNode.__rg.handleBounds[handleKey].find((d: HandleElement) => d.id === handleId)
    : sourceNode.__rg.handleBounds[handleKey][0];

It appears that handleBounds[handleKey] ends up being undefined causing this to break.
I'm updating the elements in the graph using setElements
Changing the implementation to use optional chaining seems to fix the issue but I'm not sure what the side effects might be.
  const sourceHandle = handleId
    ? sourceNode.__rg.handleBounds[handleKey].find((d: HandleElement) => d.id === handleId)
    : sourceNode.__rg.handleBounds[handleKey]?.[0];

Full stack trace:
connectionSourceId 05000d8f-2eea-4f08-aeb8-d8fc9b2dbf77
index.tsx:33 sourceIdSplitted ["05000d8f-2eea-4f08-aeb8-d8fc9b2dbf77"]
index.tsx:30 connectionSourceId 05000d8f-2eea-4f08-aeb8-d8fc9b2dbf77
index.tsx:33 sourceIdSplitted ["05000d8f-2eea-4f08-aeb8-d8fc9b2dbf77"]
index.tsx:30 connectionSourceId 05000d8f-2eea-4f08-aeb8-d8fc9b2dbf77
index.tsx:33 sourceIdSplitted ["05000d8f-2eea-4f08-aeb8-d8fc9b2dbf77"]
Uncaught TypeError: Cannot read property '0' of undefined
    at ConnectionLine (index.tsx:53)
    at renderWithHooks (react-dom.development.js:14803)
    at updateFunctionComponent (react-dom.development.js:17034)
    at beginWork (react-dom.development.js:18610)
    at HTMLUnknownElement.callCallback (react-dom.development.js:188)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:237)
    at invokeGuardedCallback (react-dom.development.js:292)
    at beginWork$1 (react-dom.development.js:23203)
    at performUnitOfWork (react-dom.development.js:22154)
    at workLoopSync (react-dom.development.js:22130)
    at performSyncWorkOnRoot (react-dom.development.js:21756)
    at react-dom.development.js:11089
    at unstable_runWithPriority (scheduler.development.js:653)
    at runWithPriority$1 (react-dom.development.js:11039)
    at flushSyncCallbackQueueImpl (react-dom.development.js:11084)
    at flushSyncCallbackQueue (react-dom.development.js:11072)
    at flushPassiveEffectsImpl (react-dom.development.js:22883)
    at unstable_runWithPriority (scheduler.development.js:653)
    at runWithPriority$1 (react-dom.development.js:11039)
    at flushPassiveEffects (react-dom.development.js:22820)
    at react-dom.development.js:22699
    at workLoop (scheduler.development.js:597)
    at flushWork (scheduler.development.js:552)
    at MessagePort.performWorkUntilDeadline (scheduler.development.js:164)
ConnectionLine @ index.tsx:53
renderWithHooks @ react-dom.development.js:14803
updateFunctionComponent @ react-dom.development.js:17034
beginWork @ react-dom.development.js:18610
callCallback @ react-dom.development.js:188
invokeGuardedCallbackDev @ react-dom.development.js:237
invokeGuardedCallback @ react-dom.development.js:292
beginWork$1 @ react-dom.development.js:23203
performUnitOfWork @ react-dom.development.js:22154
workLoopSync @ react-dom.development.js:22130
performSyncWorkOnRoot @ react-dom.development.js:21756
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
flushPassiveEffectsImpl @ react-dom.development.js:22883
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushPassiveEffects @ react-dom.development.js:22820
(anonymous) @ react-dom.development.js:22699
workLoop @ scheduler.development.js:597
flushWork @ scheduler.development.js:552
performWorkUntilDeadline @ scheduler.development.js:164
index.js:1 The above error occurred in the <ConnectionLine> component:
    in ConnectionLine
    in g
    in svg
    in Unknown
    in div
    in Unknown (created by ReactFlow)
    in StoreProvider (created by ReactFlow)
    in div (created by ReactFlow)
    in ReactFlow (at Test/index.js:107)
    in BasicFlow (at src/index.js:89)
    in Route (at src/index.js:89)
    in Switch (at src/index.js:87)
    in Router (created by BrowserRouter)
    in BrowserRouter (at src/index.js:84)

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries.
console.<computed> @ index.js:1
r @ react_devtools_backend.js:6
logCapturedError @ react-dom.development.js:19527
logError @ react-dom.development.js:19564
update.callback @ react-dom.development.js:20708
callCallback @ react-dom.development.js:12490
commitUpdateQueue @ react-dom.development.js:12511
commitLifeCycles @ react-dom.development.js:19883
commitLayoutEffects @ react-dom.development.js:22803
callCallback @ react-dom.development.js:188
invokeGuardedCallbackDev @ react-dom.development.js:237
invokeGuardedCallback @ react-dom.development.js:292
commitRootImpl @ react-dom.development.js:22541
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
commitRoot @ react-dom.development.js:22381
finishSyncRender @ react-dom.development.js:21807
performSyncWorkOnRoot @ react-dom.development.js:21793
(anonymous) @ react-dom.development.js:11089
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushSyncCallbackQueueImpl @ react-dom.development.js:11084
flushSyncCallbackQueue @ react-dom.development.js:11072
flushPassiveEffectsImpl @ react-dom.development.js:22883
unstable_runWithPriority @ scheduler.development.js:653
runWithPriority$1 @ react-dom.development.js:11039
flushPassiveEffects @ react-dom.development.js:22820
(anonymous) @ react-dom.development.js:22699
workLoop @ scheduler.development.js:597
flushWork @ scheduler.development.js:552
performWorkUntilDeadline @ scheduler.development.js:164
scheduler.development.js:178 Uncaught TypeError: Cannot read property '0' of undefined
    at ConnectionLine (index.tsx:53)
    at renderWithHooks (react-dom.development.js:14803)
    at updateFunctionComponent (react-dom.development.js:17034)
    at beginWork (react-dom.development.js:18610)
    at HTMLUnknownElement.callCallback (react-dom.development.js:188)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:237)
    at invokeGuardedCallback (react-dom.development.js:292)
    at beginWork$1 (react-dom.development.js:23203)
    at performUnitOfWork (react-dom.development.js:22154)
    at workLoopSync (react-dom.development.js:22130)
    at performSyncWorkOnRoot (react-dom.development.js:21756)
    at react-dom.development.js:11089
    at unstable_runWithPriority (scheduler.development.js:653)
    at runWithPriority$1 (react-dom.development.js:11039)
    at flushSyncCallbackQueueImpl (react-dom.development.js:11084)
    at flushSyncCallbackQueue (react-dom.development.js:11072)
    at flushPassiveEffectsImpl (react-dom.development.js:22883)
    at unstable_runWithPriority (scheduler.development.js:653)
    at runWithPriority$1 (react-dom.development.js:11039)
    at flushPassiveEffects (react-dom.development.js:22820)
    at react-dom.development.js:22699
    at workLoop (scheduler.development.js:597)
    at flushWork (scheduler.development.js:552)
    at MessagePort.performWorkUntilDeadline (scheduler.development.js:164)

I've been trying to debug this issue by pulling the source code and linking my application (in typescript) to the library using yarn link and "react-flow-renderer": "file:../react-flow/", but with both I seem to be unable to import the typings causing it to not work anymore and I can't seem to figure out why it works fine when using the node_modules version and it stops working when using the linked version. Normal imports are working just fine but when importing certain typings it breaks. It's basically everything that is being exported from src/types/index.ts
See:

I can split this up into two issues if this second one is actually an issue and not some misconception from my side.

Hey @bartvanremortele
I think you don't need to use yarn link when you do "react-flow-renderer": "file:../react-flow/" in your package.json.
Could you create a codesandbox or something like that to help us better understand how the error occurs? I will also try to reproduce this error.

I didn't actually use both at the same time. I tried them separately to see if the typings got resolved when importing them.
The strange thing is: I can import the types when using the npm module but they're not resolved when using either yarn link or the file syntax.
If you set-up an example that uses typescript you will see that you can't import the typings from the primary packages.
import ReactFlow, {
  removeElements,
  addEdge,
  MiniMap,
  Controls,
  Node,
  Edge,
  Connection,
  Elements,
  OnLoadFunc,
} from "react-flow-renderer";

This works fine when using the npm module, but when using yarn link or file:/ syntax these imports give an error:
  Node,
  Edge,
  Connection,
  Elements,
  OnLoadFunc,

while the first do not give an error:
  removeElements,
  addEdge,
  MiniMap,
  Controls,

I'm able to reproduce it here but not consistently, I feel like this is a racing condition. I need to refresh the codesandbox and drag from the green box (custom node root here) to be able to reproduce it.
https://codesandbox.io/s/hungry-cdn-r466d?file=/src/Test.js
See this gif:

Is it possible that the const handles = nodeElement.querySelectorAll(selector); is causing this when one or multiple of these nodes have not been rendered yet?

Hey @bartvanremortele
could you try to use v2.1.1

Hey @moklick thanks, the issue disappeared as soon as I left out the node which had an undefined label. I'll update and test it in the local reproduced environment. I'm interested in collaborating on react-flow and would like to get in touch with you if you're open to that.

Sure @bartvanremortele ! Thanks for the offer :) I will write you an email.
Can we close this issue?

Yes, I'll close it. Thank you for the support.


MGMT-16155: Copy  cluster-wide proxy from original SNO to upgraded one

This change is part of the cluster reconfiguration, which takes place after spinning up the seed image onto the target SNO. Cluster reconfiguration supports a predefined set of the original SNO cluster's configuration, e.g. IDMS, pull-secret, network configuration.
Specifically, this change addresses fetcing the OCP cluster-wide proxy   of the original SNO and creating the respective JSON manifest to be applied alongside the rest of the cluster reconfiguration manifests.

The canonical name for the Proxy object is cluster. As per the respective API doc.

/test all

What's the flow of information here? Is the proxy copied from the original SNO?

What's the flow of information here? Is the proxy copied from the original SNO?

Yes, the idea is to bring the proxy configuration of the original SNO to the upgraded one.

/test all

/test all

/test all

/lgtm

@tsorya thanks for LGTM-ing! I had to rebase the PR branch, could you check it out and LGTM again?

/lgtm


Fix transparent search-icon

I think that this part is not necessary because the button should behave like the other buttons just next to it.
That makes this .btn:hover entry obsolete. Additionally this causes the search-button to become transparent when it's hovered or active.
Usually one doesn't notice this because the standard background behind the buttons is also white, but if you change your header to a diffrent color you can see it. Actually not that important but it may save some bytes in the CSS files as long there is no good reason to keep this entry. I didn't find one.

Actually you also can reproduce this by changing the color for @btn-default-hover-bg in the theme manager, so a bit more relevant than I thought while creating this fix.

Thank you @t2oh4e, this will be included in the Shopware 5 RC2 release.


changelog improvements

It is missing an explanation what dumping & restoring actually does IMO - I assume because documents can be incorrectly sharded and we don't support re-sharding?


Remove support for the scope parameter in the MessageHandler.on method

At this point in time it's easy to convert the MessageHandler.on call-sites to use arrow functions, and thus let the JavaScript engine handle scopes for us, rather than having to manually keep references to the relevant scopes in MessageHandler.[1]
An additional benefit of this is that a couple of Function.prototype.call() instances can now be converted into "normal" function calls, which should be a tiny bit more efficient.
All in all, I don't see any compelling reason why it'd be necessary to keep supporting custom scopes in the MessageHandler implementation.

[1] In the event that a custom scope is ever needed, simply using bind on the handler function when calling MessageHandler.on ought to work as well.

/botio unittest

/botio test

/botio unittest

Nice find! Thank you for simplifying this.


Remove Quat set methods in favour of constructors

https://github.com/godotengine/godot/blob/d39f6386ce3a7916dbb94fef5ff65e7599e060f0/core/variant/variant_call.cpp#L1129-L1131
A Quat should be immutable. It should not have set_* methods. When required, a new Quat should be created using the equivalent constructor.
This PR removes the Quat set_* methods, and, where used, replaces them with the constructor equivalents. Note: This PR does not make Quat immutable. It's components are still public and they can still be (and are) changed within the engine.
For reference, deprecating them was originally suggested by @aaronfranke here as part of #16863.

Please don't change GDNative before #44989 is merged, otherwise conflicts will haunt me. I'm removing those methods there anyway.

Please don't change GDNative before #44989 is merged, otherwise conflicts will haunt me. I'm removing those methods there anyway.

Please don't change GDNative before #44989 is merged, otherwise conflicts will haunt me. I'm removing those methods there anyway.

That PR is now merged.

Please don't change GDNative before #44989 is merged, otherwise conflicts will haunt me. I'm removing those methods there anyway.

That PR is now merged.

Rebased.

Rebased.

Thanks!

Thanks!


Release/1.1.0

Coverage decreased (-0.4%) to 91.029% when pulling a31ee212336c7c1bd2fc94a394494b5a33bc9edc on release/1.1.0 into 9b8db2cb6ea5025385e98330c63f18436b133dcf on master.


Using a commit hash .bazelversion on Apple Silicon (arm64) pulls x86_64 bazel binary

If you have rosetta2 enabled, this seems to work -- except that the host & target platforms for the build are then detected as x86_64. If you are trying to produce arm64 builds, this is pretty confusing 😂
This is the bazelisk output
2021/08/08 16:57:45 Using unreleased version at commit d4dd2038039ecbc63e2d3037855c31145b335ad4
2021/08/08 16:57:45 Downloading https://storage.googleapis.com/bazel-builds/artifacts/macos/d4dd2038039ecbc63e2d3037855c31145b335ad4/bazel...
Extracting Bazel installation...
Starting local Bazel server and connecting to it...

I'm not sure if arm64 macos builds are available at the https://storage.googleapis.com location, but it seems to me that the URL is missing an x86_64 vs arm64 component to pull the right version.

Oh no :D I can reproduce this, indeed. Thanks for filing the issue, I'll see how we can fix that (it probably requires some changes on our CI side, where we publish the binaries for each commit, too).


Character auto select fails

🐞 bug report
Describe the bug
The character auto select mode seems to no longer function. It seems that GGG has stopped adding the lastActive key on the characters returned for the API in use.
In my brief looking, I haven't found an exposed last active character anywhere in the actual JSON APIs outside of the official API (that requires the client secret and I understand why you're not using that). However, last active character information for display on the website seems to be contained in the html response body of the website (at the bottom of the source, they add in basic details). I'm not sure if that's of use.
I don't know if the logs contain active character selection...
To Reproduce
open PoE Overlay and the game, wait an unlimited amount of time with no auto-selected active character update
Expected behavior
The PoE overlay should set the active character. Or remove the auto-select option (or otherwise display that auto-select is currently broken)

This appears to be caused by something on GGGs end. We will keep an eye on this

Since 3.20 league, GGG removed a part of their API which allowed us to detect/auto-select your character. Currently no alternative has been found or developed yet, so for now it's unfortunately broken. I'd suggest manually selecting the correct character.


Linking fails on Windows when trying to install via nimble

Hint:  [Link]
Hint: operation successful (48056 lines compiled; 1.015 sec total; 92.957MiB peakmem; Debug Build) [SuccessX]
could not load: libgirepository-1.0.dll
stack trace: (most recent call last)
C:\msys64\tmp\nimble_8180\githubcom_stefansalewskigintro\gintro.nimble(74) installBefore
C:\msys64\tmp\nimble_8180\githubcom_stefansalewskigintro\gintro.nimble(62) prep
C:\msys64\home\Benjamin\.bin\nim\lib\system\nimscript.nim(237) exec
C:\msys64\home\Benjamin\.bin\nim\lib\system\nimscript.nim(237, 7) Error: unhandled exception: FAILED: C:\msys64\tmp\gintrosalewski\gen

I installed nim 0.9.12 from source in an MSYS2 environment, and I have the necessary packages that the README told me to install.  But I'm getting this error when I try to run nimble install gintro.

Hi,
I got this error, same error with this issue.
Hint: gc: refc; opt: none (DEBUG BUILD,-d:release` generates faster code)
69987 lines; 2.290s; 116.887MiB peakmem; proj: C:\Users\masri\AppData\Local\Temp\gintrosalewski\gen.nim; out: C:\Users\masri\AppData\Local\Temp\gintrosalewski\gen.exe [SuccessX]
could not load: libgirepository-1.0-1.dll
stack trace: (most recent call last)
C:\Users\masri\AppData\Local\Temp\nimblecache-0\nimscriptapi_1408302338.nim(199, 29)
C:\Users\masri\AppData\Local\Temp\nimble_6160\githubcom_stefansalewskigintro\gintro.nimble(77, 7) installBefore
C:\Users\masri\AppData\Local\Temp\nimble_6160\githubcom_stefansalewskigintro\gintro.nimble(64, 7) prep
C:\programming\nim-1.6.8\lib\system\nimscript.nim(273, 7) exec
C:\programming\nim-1.6.8\lib\system\nimscript.nim(273, 7) Error: unhandled exception: FAILED: C:\Users\masri\AppData\Local\Temp\gintrosalewski\gen 1 [OSError]
Warning: Couldn't remove Nimble's temp dir
Error: Exception raised during nimble script execution
`
and I checked gir.nim and it have libgirepository-1.0-1.dll
is this same issue?

sorry, managed to solved it with this
pacman -S mingw-w64-x86_64-python3-gobject
the file is in this package.


AWS Native Utilization - Adding windows

Description
[Describe what this change achieves]
Issues Resolved
[List any existing issues this PR resolves]
Contribution Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] New functionality has been documented in CHANGELOG.MD

          1 Error

:no_entry_sign:
Please add labels to this Pull Request

  Generated by :no_entry_sign: Danger

With customer for review.


Information message should be available for user in case efforts are not captured

Describe the task
Project team efforts are captured through Effortsheet available on google drive. There are instances where the effort is not captured through the effort sheet, there could be many reasons for this.
Hence all the possible reasons, that could result in failure in capturing the efforts from the effort sheet, should be provided to the user in the information message.
So that the user can fix the effort sheet, according to the reason mentioned in the information message.
Expected behavior
The information message should be available as per specified in the task.

Not needed right now. Long term plan would be to have effort tracking available from the portal itself.


[6.x] Optimize Service Provider registration

As per the discussion in #30952 and according to my tests, strpos is considerably faster than calling startsWith for short haystacks. This function is called for every provider on boot.
A default laravel installation will load 25 service providers.
I adapted the benchmark to test checking the default laravel packages. Benchmark code and results here: https://gist.github.com/36864/4bc70175ad0bb60b3261d1100f249cf5
Class names are unlikely to be longer than 100 characters, so this change should not have a negative impact.
According to the same benchmarks, a direct substring comparison would also be faster than the current implementation, but slower than strpos for strings
Sample result, over 1000000 iterations, checking if the provider class name starts with Illuminate\:
Provider: Illuminate\Foundation\Providers\ConsoleSupportServiceProvider
Array
(
    [strpos] => 0.077999114990234
    [substr] => 0.13390588760376
    [startswith] => 0.28392887115479
)

Huge difference according to your benchmarks, thank you!
Nobody says no to performance. I wish this get merged (I haven't reviewed the code)

Do you actually see a difference, compared to running the entire app though?

Well, no. We are clearly in micro-optimization territory here.
But I don't see a reason for the framework to use Str::startsWith when it is known that the needle is not an array, and the length of the haystack is also probably not much greater than 100 characters.
Further tests showed substr_compare to be even faster in "real use case" benchmarks but slower in more generic benchmarks. Further testing would be needed.

I just feel this kind of micro-optimization is too far. The overhead of creating the collection and using the parturition method is probably more than the speedup you get from this change.

Cheaters )


Update wire draft

User story

As a developer
I want / need an updated version of the wire draft
So that I have an idea how the website is supposed to look like

Acceptance criteria

[ ] Wire draft is updated

Linked Issues

Blocked by:
Related to: #76
Implements:

Additional information

We don't need a login/register page
Health state should be core info

Definition of done (DoD)

Colours match with color scheme

DoD general criteria

Feature has been fully implemented
Feature has been merged into the mainline
All acceptance criteria were met
Product owner approved features
All tests are passing
Developers agreed to release

No login / user management requried
Central component should be the health indicator
Remove note buttons from from list views (Show that on the detail page)
We just need 1 cluster
Capacity columns for CPU, RAM, Storage & IP addresses
Good visibility of health indicator on detail page (currently not clear where it is)
Display children (of e.g. nodes like pods) within thew detail page


SSL: UNSUPPORTED_PROTOCOL

Traceback (most recent call last):
File "privexchange.py", line 213, in
main()
File "privexchange.py", line 137, in main
session.request("POST", ews_url, POST_BODY % attacker_url, headers)
File "/usr/lib/python2.7/httplib.py", line 1042, in request
self._send_request(method, url, body, headers)
File "/usr/lib/python2.7/httplib.py", line 1082, in _send_request
self.endheaders(body)
File "/usr/lib/python2.7/httplib.py", line 1038, in endheaders
self._send_output(message_body)
File "/usr/lib/python2.7/httplib.py", line 882, in _send_output
self.send(msg)
File "/usr/lib/python2.7/httplib.py", line 844, in send
self.connect()
File "/usr/lib/python2.7/httplib.py", line 1263, in connect
server_hostname=server_hostname)
File "/usr/lib/python2.7/ssl.py", line 369, in wrap_socket
_context=self)
File "/usr/lib/python2.7/ssl.py", line 617, in init
self.do_handshake()
File "/usr/lib/python2.7/ssl.py", line 846, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:726)

It would be nice to know what fixed this exactly for other people with this issue, but since this was resolved I'm closing this one.


github/workflows/centos: Also push zstd:chunked compressed images & Use Ubuntu 24.04 runners

github/workflows: Use Ubuntu 24.04 runners

github/workflows/centos: Also push zstd:chunked compressed images
See: https://github.com/toolbx-images/images/issues/128
See: https://fedoraproject.org/wiki/Changes/zstd:chunked
See: https://docs.podman.io/en/latest/markdown/podman-push.1.html#compression-format-gzip-zstd-zstd-chunked
See: https://github.com/coreos/fedora-coreos-tracker/issues/1660

CC @castrojo :)

Let's test this format with one image first and then copy it for all the others.

Processing triggers for libc-bin (2.31-13+deb11u10) ...
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault (core dumped)
dpkg: error processing package libc-bin (--configure):
 installed libc-bin package post-installation script subprocess returned error exit status 139
Processing triggers for ca-certificates (20210119) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for dbus (1.12.28-0+deb11u1) ...
Processing triggers for libgdk-pixbuf-2.0-0:arm64 (2.42.2+dfsg-1+deb11u2) ...
Errors were encountered while processing:
 libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)
Error: building at STEP "RUN apt-get update &&     DEBIAN_FRONTEND=noninteractive apt-get -y install         libnss-myhostname         $(cat extra-packages | xargs) &&     rm -rd /var/lib/apt/lists/*": while running runtime: exit status 100

:/

Thanks for the tag! cc @p5
One thing I learned is that many tutorials recommend ubuntu-latest, which is currently pointing to 22.04, so when I turned this on someone immediately filed an issue since their downstream build broke due to the old podman version in 22.04.
The github public roadmap mentions that 24.04 builders should go out of beta this summer, so we figured it would just be best to roll it out the day after those go live or something after confirming that ubuntu-latest is pointing to 24.04.


Calculation of Breaktime

If you have a timesheet entry from 07:00-12:00 and then another from 12:30-17:00 it would be a working time of 09:00h and as the time from 12:00-12:30 is "empty" it should be considered as a break.

In a previous chat with @kevinpapst (please correct me if my suggestion is false) some time ago and also with an income tax auditor the time like shown on second screenshot official is approved to be a break as the times are consistently recorded and traceable.

Hi @empx92 ,
what is your problem/question? There should be an icon to see related timesheets and details on the issue. According German law, there is also a warning of the time breaks for 45 minutes when working >8h. The rules are available in the documentation: https://github.com/KatjaGlassConsulting/ApprovalBundle/blob/main/documentation.md
Please clarify what the issue is.

The issue is as described that like shown on the screenshot there was a worktime of exact 9:00h.
The icon is there:

Like in the documentation:

Users must not work more than 6 hours without a 30 minute break
Users must not work more than 9 hours without a 45 minute break

It may be that I am interpreting it wrong but if you work exactly 9 hours it is not more than 9 hours?
The law in Austria is "likely" the same:

More than 6 hours a day: 30 min break
break can also be 2 times 15 min or 3 times 10 min (or according to works council)
minimum of 11 hours break after work till next worktime
36 hours a week within the monthly average

So the question is if that is a bug or correct?
Kind regards


Taking some time to show DateTimePicker.

If I have following initializer. It takes some time to present.
DateTimePicker.show(selected: Date.init(), minimumDate: nil, maximumDate: nil)
And If I have following Initializer. Picker present immediately.
DateTimePicker.show()

Confirmed. It takes like 1-2 seconds before the picker is being displayed. But! If you specify a minimum date, this is not an issue anymore :) So in my case I needed that minimum date to be the current date :) Perhaps this can help you too?


Writing test 2

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: DougKlopfenstein sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Closing this as this was a dummy PR


RPC host fails name resolution if it contains a path

Hello,
I'm trying to use a RPC host at rpcpool.com with a URL that looks like this: my-subdomain.rpcpool.com/some-path
When I pass that URL as the rpc host with the -r flag, the pythd daemon fails with the following error:
pythd: failed to resolve host

I traced the source code and confirmed that getaddrinfo is being called with the entire URL and not just the hostname, which is where it's failing.
I'm guessing this is the same underlying issue as #93 but it's hard to tell since they didn't mention where it's failing for them.

Hi Matt, as part of the devnet/testnet integration you should be using the P2P rpc endpoints. I will send these over to you in a DM.

We will add support for this in an upcoming version.


Fix handling of empty choices array in Azure OpenAI API integration

This commit refines the error handling for the Azure OpenAI API integration to address the 'n.choices[0] is undefined' error by ensuring 'data.choices' and 'data.choices[0]' are properly checked before access. This update is necessary due to the behavior changes introduced in the API version update (#684), which can result in empty 'choices' arrays.
Fix #698.

I think we should also add a condition data.choices.length > 0

Done!


Usage of SelfQueryRetriever with a Score threshold

I need to use the SelfQueryRetriever with a Score threshold value.
Tried to implement a ContextualCompressionRetriever using EmbeddingsFilter like this
        const baseCompressor = new EmbeddingsFilter({
          embeddings: getEmbedding(options?.embeddings),
          similarityThreshold: minScoreThreshold,
        });
        retriever = new ContextualCompressionRetriever({
          baseCompressor,
          baseRetriever: retriever,
        });

where retriever is a SelfQueryRetriever.
I could validate the SelfQueryRetriever is executed getting the filters and rephrasing the query, but the ContextualCompressionRetriever is not using the new query specified and should use the same filters, I could confirm the mismatch here in ContextualCompressionRetriever _getRelevantDocuments; query is the original one and does not take into account the changes.
    async _getRelevantDocuments(query, runManager) {
        const docs = await this.baseRetriever.getRelevantDocuments(query, runManager?.getChild("base_retriever"));
        const compressedDocs = await this.baseCompressor.compressDocuments(docs, query, runManager?.getChild("base_compressor"));
        return compressedDocs;
    }

So you basically want to filter by similarity to the intermediate value generated by SelfQueryRetriever?

Yes, based on the new query generated by the SelfQueryRetriever with filters I would like to use a score threshold on it.


Support testing root directory in runUfsTests

Is your feature request related to a problem? Please describe.
runUfsTests always create a test directory and run all the tests inside so problems related to root only will not be tested.
Describe the solution you'd like
Support runUfsTests with option about whether to create test directory or not and by default create the test directory.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Urgency
Explain why the feature is important
Additional context
Add any other context or screenshots about the feature request here.

a temporary test fix available at https://github.com/Alluxio/alluxio/pull/15361


Misparse/mislex of macro_rules! macro in presence of =~=

Generally it is possible to auto-generate code via a macro_rules! invocation that uses Verus syntax, as long as you make sure to generate a verus! { ... } wrapper around the generated code too. This unfortunately breaks for =~= (extensional equality) for reasons as of yet unknown.
Minimized example:
macro_rules! temp {
  () => {
    verus! {
      proof fn foo() {
        assert(seq![1,2] =~= seq![1,2]);
      }
    }
  };
}
temp!{}

which complains about error: expected expression at the ~. Note that we don't find any such issue with most of our other introduced syntax (such as @ or &&&).
playground link

I think this may be due/related to the fact that the verus! macro has to recombine the tokens that make up =~= and nested invocations may interfere with that. For the time being, as a workaround, you should be able to use ::builtin::ext_equal for =~= and ::builtin::ext_equal_deep for =~~=.


Remove pitstop usage from StatelessReader [6642]

This is a follow-up of #789
In order to avoid dynamic allocations and improve performance, this PR changes StatelessReader to avoid the usage of FragmentedChangePitStop, by having a single change pending reconstruction per matched writer.
The only drawback is that it removes the reception of fragments from unknown writers, but that should only happen with DATA(p) messages which are usually small enough to be sent on a single DATA message.

Build status:

Linux
Mac
Windows
Performance

Build status:

Linux
Mac
Windows
Performance

Test failure is unrelated. Merging.


fix: put logicalAnchor generated by Or_Expansion on root

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


List deserialization issue

Hello,
I am building a very simple client, following the code samples provided with the plugin.
Schema sample below:
schema {
query: QueryType
}
type QueryType {
getAllEquipments(): [MyEquipment!]!
}
interface Equipment {
customerName: String
id: ID!
}
type MyEquipment implements Equipment {
customerName: String
id: ID!
}
The simple query looks like this:
public List< MyEquipment > getAllEquipments() throws GraphQLExecutionException, GraphQLRequestPreparationException {
return queryType.getAllEquipments(/* "{customerName id}" */ "");
}
However I get a deserialization issue related to the list (from what I understand) - stacktrace below:
23:48:54.573 [main] TRACE com.graphql_java_generator.client.QueryExecutorImpl - Generated GraphQL request: {"query":"query {getAllEquipments{ customerName id}}","variables":null,"operationName":null}
com.graphql_java_generator.client.response.GraphQLExecutionException: Error when executing query <{"query":"query {MyEquipment{ customerName id}}","variables":null,"operationName":null}>: Cannot deserialize instance of com.QueryTypeMyEquipment out of START_ARRAY token
at [Source: UNKNOWN; line: -1, column: -1]
at com.graphql_java_generator.client.QueryExecutorImpl.execute(QueryExecutorImpl.java:94)
at com.QueryType.getAllEquipments(QueryType.java:132)
...
Caused by: com.fasterxml.jackson.databind.exc.MismatchedInputException: Cannot deserialize instance of com.QueryTypeMyEquipment out of START_ARRAY token
at [Source: UNKNOWN; line: -1, column: -1]
Note that I am using the classes for the entities and queries as generated by the plugin version 1.0.0-RC2, I am not changing any class annotation related to serialization.
Any advice would be appreciated.
Amelia

Later edit: the issue was on our side (the way the JSON response was structured); nothing related to the actual code generation from the plugin. Hence closing this ticket.


Regenerated fflib_SObjectMocks with mocks generator 4.0.0

This prevents compile errors when using the latest version of apex
mocks.

@frup42 Is this ready to merge?

Ready once this one is merged: https://github.com/financialforcedev/fflib-apex-mocks/pull/10


Update readme to include details for running tests locally

Update readme to include details for running tests locally

raised PR #146 that potentially solves this issue . kindly look into that as well .


KNUST Ghana - Miniproject

Meeting No. 1
TODO:

Install and play around with ZXlive
Try to solve Exercises 3-5 of https://www.cs.ox.ac.uk/people/aleks.kissinger/courses/qpc2024/assignment4.pdf
Find a problem that you want to solve or fix.
Didn't find a specific issue? Look through the issues, and pick something.
Try to think about how to solve the issue you have picked.

Stuck? Text in the WhatsApp group!!
Meeting No.2
TODO:

Solve the issue
Prepare a presentation or demo (5 min)

What did you learn about ZX or quantum computing?
What did you do?
Demonstration.

Stuck? Text in the WhatsApp group!!
Meeting No.3
Final presentation

Phase Fusion:

https://github.com/zxdawn/pyXZ
Write a match_phase_fusion, same as match spider, potentially.
Write phase_fusion, similar to basicrules.py, def fuse; using add_to_phase.


Add TypeScript compilation

Adds a TypeScript worker to compile sample source files. There is one worker per instance of code-sample-editor.
The loading and compiler setup is pretty basic still, but enough to run TypeScript samples. More work will have to be done to get full type-checking: recursively loading all files, loading the correct lib files, and doing a better job of loading .d.ts files for .js dependencies.

Thanks for the review @e111077 PTAL

great pass


Customization of Xcode build configuration names

Patch for issue #588.
Adds two new configs, podfileDebugConfigurations and podfileReleaseConfigurations, to allow customization of the Xcode build configuration names that are specified in the Podfile as linking with the debug and release translated libs. These default to the previously hardcoded ['Debug'] and ['Release'].

Not sure what the best name for this would be: the build configurations are things defined in the Xcode project, but the Podfile references those configuration names. I guess that's the same situation as target names and those configs are named e.g. xcodeTargetsIos, so I can rename these to be xcodeDebugConfigurations and xcodeReleaseConfigurations if you prefer.

More important than what I prefer is what makes best sense for other engineers. I had mistakenly thought this was only for the Podfile... but since this is an Xcode configuration then it feel like it should be consistent with the other settings. So xcodeDebugConfigurations and xcodeReleaseConfigurations sounds like a better choice. Feel free to push back if you feel differently.
If you're good with this, update the methods, tests and FAQ and it should be good for a final review.

Yup I agree the xcode* naming makes more sense now that I've seen more of the context. I'll make those changes and update the pull request.
I'm now getting a bizarre build error from groovy on identical code that previously compiled :/ I'll update when I get this sorted, but I'm curious if you've seen something like this.
Execution failed for task ':compileGroovy'.
> BUG! exception in phase 'instruction selection' in source unit '/Users/daniel/bc/j2objc-gradle/src/main/groovy/com/github/j2objccontrib/j2objcgradle/tasks/XcodeTask.groovy' Declaring class for method call to 'java.util.List getXcodeDebugConfigurations()' declared in com.github.j2objccontrib.j2objcgradle.tasks.XcodeTask was not matched with found receiver com.github.j2objccontrib.j2objcgradle.tasks.XcodeTask$PodspecDetails. This should not have happened!

I didn't think it worked without toArray() but bonus points if you
successfully make it simpler. Try clean before another build.
Ping me when it's ready and I'll do a final review.
On Wed, Jan 20, 2016 at 3:18 PM Daniel Dickison<EMAIL_ADDRESS>wrote:

Yup I agree the xcode* naming makes more sense now that I've seen more of
the context. I'll make those changes and update the pull request.
I'm now getting a bizarre build error from groovy on identical code that
previously compiled :/ I'll update when I get this sorted, but I'm curious
if you've seen something like this.
Execution failed for task ':compileGroovy'.

BUG! exception in phase 'instruction selection' in source unit
'/Users/daniel/bc/j2objc-gradle/src/main/groovy/com/github/j2objccontrib/j2objcgradle/tasks/XcodeTask.groovy'
Declaring class for method call to 'java.util.List
getXcodeDebugConfigurations()' declared in
com.github.j2objccontrib.j2objcgradle.tasks.XcodeTask was not matched with
found receiver
com.github.j2objccontrib.j2objcgradle.tasks.XcodeTask$PodspecDetails. This
should not have happened!

—
Reply to this email directly or view it on GitHub
<https://github.com/j2objc-contrib/j2objc-gradle/pull/590#issuecomment-173397111>
.

@brunobowden that's ready for review.
As mentioned in the commit message, I couldn't get around the strange groovy error so I left a workaround in, renaming the offending methods with a "2" suffix. In theory those methods could be renamed back without the "2" suffix, but I'm unable to get that to compile locally on my machine even after clean and wiping out gradle cache directories (I guess there must be a groovy compiler cache directory I'm missing since it persists after rebooting).

These should be my final comments.
For the 2 method, try deleting the gradle cache:
https://github.com/j2objc-contrib/j2objc-gradle/blob/master/FAQ.md#start-here-for-debugging-aka-its-not-working-aka-dont-panic
Add copyright grant:
https://github.com/j2objc-contrib/j2objc-gradle/blob/master/CONTRIBUTING.md#conditions-for-accepting-pull-requests
Collapse the commits:
https://github.com/j2objc-contrib/j2objc-gradle/blob/master/CONTRIBUTING.md#preparing-your-pull-request-for-submission

Finally, what should happen for xcodeDebugConfigurations = [], i.e. no configurations at all? Should that give an error? Will Cocoapods accept it? Try that out and add a comment explaining whatever logic you suggest.

Re: xcodeDebugConfigurations = []
If the Podfile contains :configurations => [], the pod dependency gets applied to all configurations. This would be unexpected, so I propose that the entire pod line is excluded when the array is empty.
On the other hand, CocoaPods reports an error when :configurations => [''], which I think is fine since, in fact, an empty string is an invalid configuration name.

I feel that toQuotedList([]) should be an empty string.
It makes sense that for an empty list, the Podfile line is removed
entirely. Add that to the FAQ and the comment in J2objcConfig.
On Wed, Jan 20, 2016 at 9:11 PM Daniel Dickison<EMAIL_ADDRESS>wrote:

Re: xcodeDebugConfigurations = []
If the Podfile contains :configurations => [], the pod dependency gets
applied to all configurations. This would be unexpected, so I propose
that the entire pod line is excluded when the array is empty.
On the other hand, CocoaPods reports an error when :configurations => [''],
which I think is fine since, in fact, an empty string is an invalid
configuration name.
—
Reply to this email directly or view it on GitHub
https://github.com/j2objc-contrib/j2objc-gradle/pull/590#issuecomment-173454535
.

Ok I think I incorporated all the comments. I went ahead and deleted the "2" suffix from those method names even though I wasn't able to solve the mystery groovy/gradle error locally (I tried deleting the various cache directories, etc, to no avail. Very strange).

Looks like the AppVeyor failure is the same groovy error I'm seeing locally. I'll put the "2" workaround back in there for now, but I'm at a loss as to why these particular method declarations fail.

Given the flakiness, it makes sense to retain the 2. Very strange and
probably fixed in a later version of Gradle.
On Wed, Jan 20, 2016 at 11:37 PM Daniel Dickison<EMAIL_ADDRESS>wrote:

Looks like the AppVeyor failure is the same groovy error I'm seeing
locally. I'll put the "2" workaround back in there for now, but I'm at a
loss as to why these particular method declarations fail.
—
Reply to this email directly or view it on GitHub
https://github.com/j2objc-contrib/j2objc-gradle/pull/590#issuecomment-173484259
.

@danieldickison - thanks for a great change with good code. I'm happy to have merged this in. We'll probably work on some other fixes for J2ObjC 1.0 before spinning a new version.

Sounds good. Thanks for the code reviews!


WIP: On-screen keyboard support

This pull request combines work on:

input-method protocol #856
text-input protocol #776
rootston glue

Its purpose is to develop these in sync, and to remove the need to juggle different long-running feature branches as different parts are being developed. This has proven to take up effort and lead to awkward situations, e.g. many of the rebased rootston commits were developed against an earlier version of wlr_input_method.h and are currently unbuildable.
One interesting thing is the addition of code duplicating some functionality of layer surfaces (panels, unfocusable windows) in rootston views, in order to support input-method-panel.

Now that we have layer-surfaces can't OSK use just that?

@agx: I wanted to have a reasonably complete implementation of the existing protocol first, especially because all existing software, namely weston-keyboard uses it. The plan is to update the protocol and remove the panel in its current form in favor of layer-surfaces in the future.

@dcz-purism with existing you mean weston-keyboard using zwp_input_panel_surface_v1 ?

@dcz-purism my main concern is growing a third way to handle popups and overlay surfaces. layer-shell already has overlap with views and it would be nice if either one could be reused.

On Thu, Apr 26, 2018 at 09:22:57PM +0000, dcz-purism wrote:

dcz-purism commented on this pull request.

@@ -134,3 +144,55 @@ void handle_input_method_context_destroy(struct wl_listener *listener,
}
update_maximized_views(desktop);
}

+static void spawn_im_process() {

*im_pid = fork();
if (*im_pid == 0) {

sleep(1);

execl("/bin/sh", "/bin/sh", "-c", im_cmd, (void *)NULL);

The -E command accepts a shell, so in order to maintain consistency, I
made it the same. Personally, I don't see the need for a shell in
either case, but maybe I'm missing something.

Shell uses $PATH but I'd rather not rely on that for the OSK.

How're are things in this department going on your end? Should we expect an update to this soon?

Yes indeed! Currently I'm busy upstreaming text-input to GTK, so after the merge window closes and I'm free to do other things again, I'll push my changes to get some formal feedback.

Sweet, keep up the good work!

The first replacement of the old input method was just posted to gather feedback today:
https://lists.freedesktop.org/archives/wayland-devel/2018-August/039255.html

I rewrote this code to updated protocols and submitted it as a separate (out of forgetfulness) PR here.


website down lol

your website is down so i cant download

That is something on your side, try using a mobile hotspot or VPN to download it!


integrate model with UI

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#162  👈
#161
#160
#159
#158
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ksharma-xyz and the rest of your teammates on  Graphite


suggestion: add a permission that grants everything

honestly i’m not sure about anything i’m writing in this issue… pardon me if i’m wrong and correct me :)

currently, to grant all permissions to a user in a certain directory, all permissions (e.g. rwmda) must be specified.
this makes config files look pretty messy since most people want an administrator to be able to have all those permissions in all directories.
i’m not sure if directories inherit permissions from their parents right now, but maybe it could be made such that that is done?
also, it would be nice if the admin (a) permission grants everything, but im not sure if this conflicts with anything / current configs.
or another permission could be made, maybe like o or something for owner, that grants all permissions

yeah good point 👍
as it sometimes makes sense to give someone admin without write/move-access (for example to see uploader IP), I'm gonna go with A for the new permission, which is an alias of rwmda. (read/write/move/delete/admin/dotfiles).

i’m not sure if directories inherit permissions from their parents right now, but maybe it could be made such that that is done?

yep! they do -- the only thing that stops permission inheritance is if you create another volume somewhere further down in the directory tree


Aerie Dev Deployment Improvements

The existing development deployment is essentially a shell script running in a cronjob which tends to be both brittle and opaque. The AMMOS in the Cloud team has been developing a more robust ECS-based deployment using terraform. This meta ticket will track the progress in integrating this work into the existing Aerie developer environment.
### Tasks
- [ ] Standup Aerie terraform deployment (S3 state bucket)
- [ ] Bring infra-as-code into NASA-AMMOS namespace
- [ ] Convert to Continuous Deployment (λ function cron updating ECS tasks)
- [ ] Automate database migrations (λ function running `aerie_db_migration.py`
- [ ] Automate database backups (λ function running pgdump)
- [ ] Update deployment status on GH

Another thing we talked about recently: aerie-dev should alert us somehow if migrations fail


Added animations

Added the slideLeft animation to the hero text
Added the transform(translate) proproties to buttons on hover

Merge from added_animations to main


Add tokens processing

Pull Request Test Coverage Report for Build 128

1 of 13 (7.69%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.6%) to 24.91%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

index.js
1
13
7.69%

Totals

Change from base Build 127:
-0.6%

Covered Lines:
129

Relevant Lines:
452

💛  - Coveralls


Path must be a string. Received undefined / Issue with Ember 3.0

I'm getting an error message with this addon installed:
"Path must be a string. Received undefined"
I'm using Ember 3.0

Having just tested this on a clean project I believe this is only related to using Ember 3.0 and above.
I'm not seeing it with Ember 2.18

@snewcomer @MrChriZ as an FYI: https://github.com/HeroicEric/ember-normalize/pull/19


Animatable Constraint Capturing results in Seg Fault: 11

I have this code in my view controller:
override func updateViewConstraints() {

	logoView.snp_updateConstraints { (make) -> Void in
		make.top.equalTo(view).offset(100)
		make.centerX.equalTo(view)
		make.width.height.equalTo(220)
	}
}

But when I try to capture the top constraint, I get a Segmentation Fault: 11
var logoTopConstraint: Constraint? = nil

override func updateViewConstraints() {

	logoView.snp_updateConstraints { (make) -> Void in
		self.logoTopConstraint = make.top.equalTo(view).offset(100)
		make.centerX.equalTo(view)
		make.width.height.equalTo(220)
	}
}

On top of the segfault:11, Xcode lets me know that its crashing. Which results in all my syntax coloring turning to pure white text until I remove the constraint capture.

I resolved this issue by ignoring the documentation and just reading the code. The problem is the docs tell you to create a Constraint type but in fact you need to create ConstraintDescriptionEditable type. Then when you need to update the you can do self.logoTopConstraint.constraint.updateOffset(200). Obviously replace self.logoTopConstraint with whatever you want to call your variable.
But the key thing to note is the type is ConstraintDescriptionEditable and is not Constraint.


publish options for a production build

I am trying to create a production build with publish and CI but in the project.json file there is the publishoptions:
"publishOptions": {
"include": [
"appsettings.json",
"Client",
"Views",
"tsconfig.json",
"web.config",
"config",
"wwwroot"
]
},
For a production build, can I simple use:
"publishOptions": {
"include": [
"appsettings.json",
"tsconfig.json",
"web.config",
"wwwroot"
]
},

@albrookesplowman Sure, if it suits your need. I think some extra files are there if we are using server side rendering then we need to copy node_modules + any other necessary files. This project isn't using server side angular 2 rendering, so makes sense to simplify what to include in build.

Thanks for the update - do you know how to add the server side rendering?  I have to tried to see the differences between this project and another one I found but I have not been able to add this feature

I am holding back for SSR (Server side rendering) right now as things aren't as stabilise as they have to be. So, no idea, sorry :)


Write a changelog on release

Reading commits' messages to know what changed isn't the most immediate thing, and since the project is getting quite big wouldn't it be better to have a full changelog on every release?

i'm lazy.

feel ya on that one, let's hope someone will propose to do it then lol.
Or you prefix your changes with Feature:,Fix: etc and then merge all the messages from date x to release date

GitHub allows you to auto generate the changelog

ok then, if it does i will.


Updates README.md

Description
This is documentation about CDN installation (put inside the README.md file)
Fixes https://github.com/turingpointde/cvss.js/issues/39
Type of change

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

LGTM, thank you @MrDoomy!


Updates available notification shows when I pushed the change

PR: https://github.com/microsoft/vscode/pull/140196/
I pushed a commit via the terminal and the notification showed briefly afterwards, despite being the one that pushed it.

ext: 0.35.202201069

@Tyriar this doesn't happen every time, correct?
It looks like this can happen when you get unlucky and the poll-for-changes occurs right after you push but before we've finished updating all our state.

Yes I don't think it happens every time. I'm guessing checking the commit hash when there's changes to verify should be a lightweight action.

Yep, that's what we currently do. It's just a matter of when we update the commit hash.


containerd+kata-shimv2: how to recover from inconsistent situation?

It is an uncommon case that containerd thinks there is a running container but kata thinks otherwise. We need a way to be able to recover from such a situation. Ideally containerd should be able to tell that a container is gone by the grpc error code. But it only wants to do cleanup in async event handler.
One option we have is to fake an TASK_EXIT event (upon any API that fails to find a container) and then containerd is able to pick it up and remove the container from its internal store. However, the workaround heavily depends on containerd implementation details and violates the shimv2 protocol about async events (https://github.com/containerd/containerd/blob/master/runtime/v2/README.md#events), which is not fully enforced in containerd right now though.
@crosbymichael @Random-Liu @lifupan @sboeuf would you please share your opinions?
I know the "best" option is to never get into such a situation but I did have and I wonder if there is a way to make the system more robust.

Related fixes in containerd and cri: https://github.com/containerd/containerd/pull/3207 and https://github.com/containerd/cri/pull/1133.


fix: fix web-sys warnings in server_fn

This needs to be merged first before #2827 to make CI work.

I made separate PRs to address the update issues. This PR and #2827 will solve the issues. Would you mind to combine them in single PR?
The other problem is that the cargo binstall wasm-bindgen-cli still fetches the old wasm-bindgen-cli binary (v0.9.92) and most of the examples won't compile.
https://github.com/leptos-rs/leptos/actions/runs/10377904297/job/28733123057?pr=2828#step:20:1103
Do you know if there is any caching layer that CI's binstall doesn't get the latest binary?

You beat me to it. I think cargo-binstall will only use the latest binaries, which are only generated when a new version is released. Which I'll be arranging now alongside cargo-leptos

@sabify Would you like to make the same changes to the leptos_0.6 branch? This only fixes it for those on git main

@sabify Would you like to make the same changes to the leptos_0.6 branch? This only fixes it for those on git main

Sure. Just waiting for the green CI.

I'm going to merge this, the CI will be red until I release cargo-leptos

@sabify Merged, and cargo-leptos has been released


Some more documentation edits and readthedocs container config

Added a more detailed example on how to make a custom backend
Add a couple more ref links
Added a Dockerfile + docker-compose config to make it easier to setup the readthedocs build environment locally

Coverage remained the same at 95.368% when pulling 8ae34b76e045fdab57e95b01c66e86062169fde3 on JWCook:docs into 0938c0242a3e4e3e4349b8e1edeca767b7e67200 on reclosedev:master.


MaltEval in nltk.parse.malt?

Adding an interface to MaltEval (http://w3.msi.vxu.se/~jni/malteval/) to nltk.parse.malt would be absolutely wonderful.  If need be, I could provide some Polish data to help test such an interface.
Migrated from http://code.google.com/p/nltk/issues/detail?id=656

Closing this because it seems like MaltEval is an orphaned project and it (cannot be found even on wayback machine)[http://web.archive.org/web/*/http://w3.msi.vxu.se/users/jni/malteval]. I would love to visualize it dependencies too but now I think there're (brat)[http://brat.nlplab.org/] =(


fix a markdown of link

No problem with en-us web.
A little trouble in ja-jp translation.

@yoichinak : Thanks for your contribution! The author, @PanosPeriorellis, has been notified to review your proposed change.


Fix openssl commands to match with what's expected.

I was having a hard time making sense of what should be done in this section when I realized the cat command was completely off.
I've also added a few changes to make the entire openssl workflow easier to follow.

Thanks :-)

Sure thing! :)


Added back to top button in all sections. For the issue No #10

Added "Back to Top" button functionality that appears after scrolling down 100px and smoothly scrolls to the top when clicked.
Please review it.
Closes #10
https://github.com/user-attachments/assets/7e1b99af-a787-4afb-a242-2ef1e56eae82

Nice work thank you.

You're Welcome. Thank You


Sema/SIL: NSError has no special powers without ObjC interop.

Explanation: The compiler's NSError bridging code was not sufficiently conditionalized on ObjC interop, and would attempt to toll-free-bridge NSErrors to Error existentials on platforms without ObjC interop.
Scope: Breaks any attempt to work with corelibs-foundation, which throws NSErrors. Catching an NSError effectively always triggers a crash.
Issue: SR-585, rdar://problem/30766599
Risk: Low
Testing: Swift CI, manual testing

@swift-ci Please test

@DougGregor mind reviewing this for inclusion in 3.1?


Check annotations

Create an annotations check that ensures:

[x] is_type is an approved control vocabulary
[x] id's match given tables
[x] 'empty' entries are only associated with column-level id

Still need comments and test-checkAnnotations built out before merging.

[ ] write unit tests for all checks in checkAnnocations
[ ] add in possible min/max from an annotations table into both checkAnnotations and the unit test


[Bug]:  Order section display issue

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
In order section the navbar and footer are joined together ( If the orders are empty ).
Expected behavior
If orders are empty then also there should be a proper spacing between navbar and footer of the website
Add ScreenShots

On which device are you experiencing this bug?
Chrome
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Is there an existing issue for this?

[x]  I have searched the existing issues

Describe the bug
In order section the navbar and footer are joined together ( If the orders are empty ).
Expected behavior
If orders are empty then also there should be a proper spacing between navbar and footer of the website
Add ScreenShots

On which device are you experiencing this bug?
Chrome
Record

[x]  I have read the Contributing Guidelines
[x]  I'm a GSSOC'24 contributor
[x]  I have starred the repository

Hello @Sourabh782 , Go for it
All the Best


invalid go version issue

I followed the instructions in the README.md. When I attempted the go install github.com/bernardo-bruning/ollama-copilot@latest instruction, I encountered this error: ** go.mod:3: invalid go version '1.22.2': must match format 1.23**
I am not a 'go' expert, so I not sure what exactly the reason for the error. Is it because 'go' expects the version to be 1.23 or is it because 1.22.2 has too many digits?

Same problem here

What version of golang you are using? To check this execute go version and send me.

Not working for me either. Using go version go1.19.8 linux/amd64.
❯ go install github.com/bernardo-bruning/ollama-copilot@latest
go: downloading github.com/bernardo-bruning/ollama-copilot v0.2.0
go: github.com/bernardo-bruning/ollama-copilot@latest (in github.com/bernardo-bruning/ollama-copilot@v0.2.0):
go.mod:3: invalid go version '1.22.2': must match format 1.23

System info (uname -a): Linux debian 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux


(re-report) With TeXLive 2023 I face two perl scripts biber and biber-ms with same vendor path

which is
/lib/perl5/vendor_perl/5.36.0/Biber.pm
/lib/perl5/vendor_perl/5.36.0/Biber/

and those files are conflicting. I'd like to avoid to hack e.g. biber-ms by adding a
line like
use lib '/lib/perl5/vendor_perl/5.36.0/biber-ms/`;

an other solution seems not working. Therefore why we have two versions
of biber and why seems 2.18 not to support multiscript (otherwise biber-ms would
be superfluous)
compare with #1270

Can you give more details of the issue? The multiscript version biber-ms isn't released in TL yet as it's not quite ready. The multiscript version is a separate things because it's a significant re-write that's currently a lot slower and needs user testing. I haven't really looked into anyone else installing it like this yet.

My perl generator script for the spec files does use texlive.tlpdb.xz and for current pretest I see now in texlive.spec the entry
%package biber-ms-bin
Version:        %{texlive_version}.%{texlive_release}.svn64180
Release:        0
License:        LPPL-1.0
Summary:        Binary files of biber-ms
Group:          Productivity/Publishing/TeX/Utilities
URL:            https://www.tug.org/texlive/
Requires(pre):  texlive-biber-ms >= %{texlive_version}
#!BuildIgnore:  texlive-biber-ms
Prefix:         %{_bindir}

%description biber-ms-bin
Binary files of biber-ms

and
%files biber-ms-bin
%defattr(-,root,root,755)
%{_bindir}/biber-ms

the archive directory does list
texlive/2023> ll archive/biber-ms.*
-rw-rw-r-- 1 werner suse 258716 Aug 28  2022 archive/biber-ms.doc.r64213.tar.xz
lrwxrwxrwx 1 werner suse     26 Aug 28  2022 archive/biber-ms.doc.tar.xz -> biber-ms.doc.r64213.tar.xz
-rw-rw-r-- 1 werner suse    500 Aug 28  2022 archive/biber-ms.r64213.tar.xz
-rw-rw-r-- 1 werner suse 945480 Aug 28  2022 archive/biber-ms.source.r64213.tar.xz
lrwxrwxrwx 1 werner suse     29 Aug 28  2022 archive/biber-ms.source.tar.xz -> biber-ms.source.r64213.tar.xz
lrwxrwxrwx 1 werner suse     22 Aug 28  2022 archive/biber-ms.tar.xz -> biber-ms.r64213.tar.xz

and a look into archive/biber-ms.source.tar.xz shows
texmf-dist/source/bibtex/biber-ms/Changes
texmf-dist/source/bibtex/biber-ms/README.biber-ms-linux
texmf-dist/source/bibtex/biber-ms/README.biber-ms-macos
texmf-dist/source/bibtex/biber-ms/README.biber-ms-windows
texmf-dist/source/bibtex/biber-ms/README.md
texmf-dist/source/bibtex/biber-ms/biblatex-biber-ms.tar.gz
texmf-dist/source/bibtex/biber-ms/utf8-macro-map.html
tlpkg/tlpobj/biber-ms.source.tlpobj

I don't think this has anything to do with TL which does have parallel installs of biber and biber-ms. If you are building from source, you should probably only be building the normal biber from the master branch or tagged 2.x releases. The build/install for the multiscript version is more complicated and I do it only to provide binaries currently as 4.0 is experimental.


BUILDKITE_PLUGINS environment variable is undocumented

https://buildkite.com/docs/pipelines/environment-variables documents the values of many of Buildkite's environment variables, but it is missing BUILDKITE_PLUGINS.
Note that another page - https://buildkite.com/docs/agent/v3/securing#allowing-a-list-of-plugins - explicitly links to that one as a reference about this variable.

Thanks for reporting @amartani


Not seeing ros2 topics on pc

Robot Model
Turtlebot4 Lite
ROS distro
Humble
Networking Configuration
Discovery Server
OS
Ubuntu 22.04
Built from source or installed?
Installed
Package version
I'm not sure. I'm using the following docker image, which has ros2 humble installed already: https://github.com/Tiryoh/docker-ros2-desktop-vnc
Type of issue
Networking
Expected behaviour
I'm able to see all of the turtlebot4 and create3 topics on both my pc and on the raspberry pi
Actual behaviour
I'm able to see the turtlebot4 and create3 topics on the raspberry pi, but not on my pc
Error messages
No error messages.

To Reproduce

Run ros2 topic list in the terminal on my pc (within the docker image)
The topics will not appear

Other notes
No response

Hi could you try running the docker image with also these two arguments --privileged --network=host and see if you can see topics in the container?

@PrakritTyagi  This is what happens when I try to run it with those arguments:
2024-11-15 21:48:46 * enable custom user: ubuntu
2024-11-15 21:48:46 useradd: warning: the home directory /home/ubuntu already exists.
2024-11-15 21:48:46 useradd: Not copying any file from skel directory into it.
2024-11-15 21:48:46   set default password to "ubuntu"
2024-11-15 21:48:46 grep: /home/ubuntu/.bashrc: No such file or directory
2024-11-15 21:48:46 ============================================================================================
2024-11-15 21:48:46 NOTE 1: --security-opt seccomp=unconfined flag is required to launch Ubuntu Jammy based image.
2024-11-15 21:48:46 See https://github.com/Tiryoh/docker-ros2-desktop-vnc/pull/56
2024-11-15 21:48:46 ============================================================================================
2024-11-15 21:48:46 2024-11-16 02:48:46,429 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2024-11-15 21:48:46 2024-11-16 02:48:46,430 INFO Set uid to user 0 succeeded
2024-11-15 21:48:46 2024-11-16 02:48:46,431 INFO RPC interface 'supervisor' initialized
2024-11-15 21:48:46 2024-11-16 02:48:46,431 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2024-11-15 21:48:46 2024-11-16 02:48:46,431 INFO supervisord started with pid 43
2024-11-15 21:48:47 2024-11-16 02:48:47,440 INFO spawned: 'novnc' with pid 44
2024-11-15 21:48:47 2024-11-16 02:48:47,444 INFO spawned: 'vnc' with pid 45
2024-11-15 21:48:47 2024-11-16 02:48:47,560 INFO exited: novnc (exit status 1; not expected)
2024-11-15 21:48:48 2024-11-16 02:48:48,633 INFO spawned: 'novnc' with pid 632
2024-11-15 21:48:48 2024-11-16 02:48:48,633 INFO success: vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2024-11-15 21:48:48 2024-11-16 02:48:48,708 INFO exited: novnc (exit status 1; not expected)
2024-11-15 21:48:50 2024-11-16 02:48:50,715 INFO spawned: 'novnc' with pid 681
2024-11-15 21:48:50 2024-11-16 02:48:50,817 INFO exited: novnc (exit status 1; not expected)
2024-11-15 21:48:53 2024-11-16 02:48:53,836 INFO spawned: 'novnc' with pid 703
2024-11-15 21:48:53 2024-11-16 02:48:53,946 INFO exited: novnc (exit status 1; not expected)
2024-11-15 21:48:54 2024-11-16 02:48:54,953 INFO gave up: novnc entered FATAL state, too many start retries too quickly

Hi there @rohanchandra-cpe
Can you please make sure you have gone through the setup process and installed all required TB4 packages on the remote PC? LINK
Can you try verifying basic networking, ensure that you can communicate between the docker container and other outside computers (ping, ssh etc.) and after that is fully functional, then test ROS networking and then test turtlebot4.
It appears you may have a configuration issue - if possible try running on a standard Ubuntu 22.04 ROS Humble docker image and make sure it works then move to the custom container image you are working with?
We don't directly support containerized systems because of the complexity and uniqueness of different configurations.
There are various resources available including Robotics Stack Exchange (https://robotics.stackexchange.com/) and the Open Robotics Discord.
Best regards,
Rusy

Closing due to no reply or activty.


rate_limit: update methods to automatically paginate

Description
Adding working pagination to ListRateLimits and removing ListAllRateLimits because of duplication.
Has your change been tested?
Unit tests are working
Screenshots (if appropriate):
Types of changes
What sort of change does your code introduce/modify?

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] This change is using publicly documented (api.cloudflare.com or developers.cloudflare.com) and stable APIs.

Codecov Report

Merging #1011 (d25237b) into master (6c5ea4a) will decrease coverage by 0.02%.
The diff coverage is 69.23%.

@@            Coverage Diff             @@
##           master    #1011      +/-   ##
==========================================
- Coverage   49.06%   49.03%   -0.03%
==========================================
  Files         108      108
  Lines       10428    10428
==========================================
- Hits         5116     5113       -3
- Misses       4200     4202       +2
- Partials     1112     1113       +1

Impacted Files
Coverage Δ

access_application.go
76.52% <ø> (ø)

access_bookmark.go
72.44% <ø> (ø)

rate_limiting.go
58.22% <69.23%> (-3.80%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Linting improvements

Linting definitions updated to internally decided eslint config.
Removed unwanted eslint dev dependencies from package.json

The approach for this has changed! Cannot accept this pull request.


Add cflinuxfs4 bosh release

The cflinuxfs4 bosh release deploys the cflinuxfs4 rootfs.
Checklist for submission:

[x] LICENSE and NOTICE files are up to date
[x] at least one final release is checked in on the default repo branch (there's a .final_builds folder)
[x] of use to the general community and will be maintained
[x] github repo must be public
[x] bosh create-release must run successfully against all final releases (the blobstore needs to be public)

if not all final releases are valid, specify a min_version

[x] a README explaining what the repo does
[x] [optional] deployment manifests/ directory contains example manifest

Sorry not sure who the maintainers are. Tagging a few people who I see have reviewed/merged recent PRs.
@rkoster @mrosecrance

Hi @rkoster do you know if this needs more reviews? Wondering who can merge the PR


"Open Bot" window has misleading tip for App ID and App Password

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
3.3
Describe the bug
When opening a bot in the emulator, the fields for App ID and App Password have the tip set to Optional. This makes the user think that the APP ID and password are not required. In fact they are mandatory if the bot service is set up with these values in appsettings.json.
To Reproduce
Steps to reproduce the behavior:

Go to File-->Open Bot
Notice that App ID and App Password have a tip set to Optional. This is misleading.

Expected behavior
The message should either not say anything or point to a help documentation
Screenshots

Additional context
Add any other context about the problem here.
[bug]

@mewa1024 do you agree with the feedback here? What we're doing is pretty conventional, though adding a link about connecting to bots needing authentication may be helpful.

Friendly ping @mewa1024. Do you have any input on this suggestion?


webhook cert rejected in Kubernetes 1.19 due to https://golang.org/doc/go1.15#commonname

What commit ID of Portieris did you experience the problem with?
0.9.0
What went wrong?
All webhook requests fail on Kubernetes 1.19
What should have happened differently?
Webhook requests succeed
How can it be reproduced?
install on K 1.19
Any other relevant information
because K 1.19 uses golang 1.15 and https://golang.org/doc/go1.15#commonname

duplicate of #196


Refine the log

Codecov Report

Merging #192 (c1b175f) into master (ca42bb6) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #192      +/-   ##
============================================
+ Coverage     35.04%   35.07%   +0.03%
- Complexity      657      658       +1
============================================
  Files           196      196
  Lines          8649     8653       +4
  Branches        274      274
============================================
+ Hits           3031     3035       +4
  Misses         5469     5469
  Partials        149      149

Flag
Coverage Δ

java
61.76% <100.00%> (+0.04%)
:arrow_up:

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

Impacted Files
Coverage Δ

...cketmq/client/java/metrics/ClientMeterManager.java
70.73% <100.00%> (ø)

...rg/apache/rocketmq/client/java/metrics/Metric.java
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


New Contribution

Contributor: [contributor information - Optional]
SSH Public key: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICE9wQqTVaVmuspWHem0oqHx73DlKQuwvQUONp9KG+VJ
Attestation: [any form of attestation for contribution (e.g., signature) - Optional]

ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAICE9wQqTVaVmuspWHem0oqHx73DlKQuwvQUONp9KG+VJ

I'm ready to contribute.


Improve dissectors

With 5.0, Elastic introduced Dissector which improved performance to when using Grok and CSV. In the example they use, Palo Alto, it makes a pretty significant difference in performance

Another useful filter in logstash is the 'useragent'.


Fixed Date bug in input form.

fixes #75
Description:
The issue was comparison of time.

Looks Good, thanks @imshvishal !


2.35.2 UnityPackage example scene errors with L515

Camera Model: L515
Firmware Version: <IP_ADDRESS>
OS: Win 10 1909 18363.900 (PC)
SDK: 2.35.2
Language: Unity 2019.3.12f1
Imported the RealSense UnityPackage from latest 2.35.2 release, running the StartHere scene and clicking START on the Point Cloud Processing Blocks (Depth) results in console repeatedly logging the following error below.  I tested the device in RealSense Viewer 2.35.2 and updated firmware in there, all seems to be working outside of Unity, also made sure to close viewer before attempting to run the Unity example scene.
The <0x01>,<0x02> in the out of range exception show as invalid characters in the unity log ( it just looks like [,] )
ExternalException: rs2_set_option(options:000001BE9D2BEF30, option:Filter Magnitude, value:0)
Rethrow as ArgumentException: Given value 0 is outside [<0x01>,<0x02>] range!
Intel.RealSense.ErrorMarshaler.MarshalNativeToManaged (System.IntPtr pNativeData) (at :0)
Intel.RealSense.OptionInternal.set_Value (System.Single value) (at :0)
RsPointCloud.UpdateOptions (System.Boolean isComposite) (at Assets/RealSenseSDK2.0/Scripts/ProcessingBlocks/RsPointCloud.cs:64)
RsPointCloud.Process (Intel.RealSense.Frame frame, Intel.RealSense.FrameSource frameSource) (at Assets/RealSenseSDK2.0/Scripts/ProcessingBlocks/RsPointCloud.cs:57)
RsProcessingPipe.ProcessFrame (Intel.RealSense.Frame frame, Intel.RealSense.FrameSource src) (at Assets/RealSenseSDK2.0/Scripts/RsProcessingPipe.cs:99)
UnityEngine.Debug:LogException(Exception)
RsProcessingPipe:ProcessFrame(Frame, FrameSource) (at Assets/RealSenseSDK2.0/Scripts/RsProcessingPipe.cs:119)
Intel.RealSense.CustomProcessingBlock:ProcessingBlockCallback(IntPtr, IntPtr, IntPtr)
Intel.RealSense.NativeMethods:rs2_process_frame(IntPtr, IntPtr, Object&)
Intel.RealSense.CustomProcessingBlock:Process(Frame)
RsDevice:RaiseSampleEvent(Frame) (at Assets/RealSenseSDK2.0/Scripts/RsDevice.cs:148)
RsDevice:WaitForFrames() (at Assets/RealSenseSDK2.0/Scripts/RsDevice.cs:160)
System.Threading.ThreadHelper:ThreadStart()

Hi xraxra,
Please try to apply this pull request to your Unity script.
https://github.com/IntelRealSense/librealsense/pull/6644
It should work.

Hi! I have the same problem.
I just applied the pull, but I still get the same error.
Any idea?

More info - mine is happening with Unity 2019.2.3f1, and the d435.
Log:
2.0/Scripts/RsProcessingPipe.cs:119)
Intel.RealSense.CustomProcessingBlock:ProcessingBlockCallback(IntPtr, IntPtr, IntPtr)
Intel.RealSense.NativeMethods:rs2_process_frame(IntPtr, IntPtr, Object&)
Intel.RealSense.CustomProcessingBlock:Process(Frame)
RsDevice:RaiseSampleEvent(Frame) (at Assets/RealSenseSDK2.0/Scripts/RsDevice.cs:148)
RsDevice:WaitForFrames() (at Assets/RealSenseSDK2.0/Scripts/RsDevice.cs:160)
System.Threading.ThreadHelper:ThreadStart()

I solved this problem.
It's not enough to fix the enum "OcclusionRemoval" in RsPointCloud.cs for solving the problem.
You should also change option of the Processing Blocks which is attached to a profile of a RsPeocessingPipe prefab.
https://github.com/IntelRealSense/librealsense/issues/6647

Yes, you have to update the script and related scriptable objects.

Hi again,
changing the RsPointCloud.cs and the other options in the Processing Blocks the point cloud demo still doesn't work.
I also get the same error + this other error:
InvalidOperationException: Error while running DisparityTransform processing block, check the log for info
Intel.RealSense.ProcessingBlock.Process[T] (Intel.RealSense.Frame original) (at :0)
Intel.RealSense.ProcessingBlock.Process (Intel.RealSense.Frame original) (at :0)
RsDisparityTransform.Process (Intel.RealSense.Frame frame, Intel.RealSense.FrameSource frameSource) (at Assets/RealSenseSDK2.0/Scripts/ProcessingBlocks/RsDisparityTransform.cs:56)
RsProcessingPipe.ProcessFrame (Intel.RealSense.Frame frame, Intel.RealSense.FrameSource src) (at Assets/RealSenseSDK2.0/Scripts/RsProcessingPipe.cs:99)
UnityEngine.Debug:LogException(Exception)
RsProcessingPipe:ProcessFrame(Frame, FrameSource) (at Assets/RealSenseSDK2.0/Scripts/RsProcessingPipe.cs:119)
Intel.RealSense.CustomProcessingBlock:ProcessingBlockCallback(IntPtr, IntPtr, IntPtr)
Intel.RealSense.NativeMethods:rs2_process_frame(IntPtr, IntPtr, Object&)
Intel.RealSense.CustomProcessingBlock:Process(Frame)
RsDevice:RaiseSampleEvent(Frame) (at Assets/RealSenseSDK2.0/Scripts/RsDevice.cs:148)
RsDevice:WaitForFrames() (at Assets/RealSenseSDK2.0/Scripts/RsDevice.cs:160)
System.Threading.ThreadHelper:ThreadStart()

I find what is wrong.
If you start point cloud demo from StartHere scene, the RsPointCloud option of RsProcessingBlock is initialized to null. So error is occurred.
So It's not good to use StartHere scene now. I'm trying to find the solution.
Open scene file "PointCloudDepthandColor" or "PointCloudProcessingBlocks" and try to start the scene.

Hey @wodndb, thanks for the tip! It works via the separate scene files.
I rechecked the PointCloudProcessingBlocks, but I can't make it work in the StartHere scene btw.
Weird thing is I also have a problem with the cursor texture, that works perfectly in the separate scene.
Anyway, I can test things with this working.

Not all of Post Processing filters can work with L515.
In this version, please disable the filters if work with L515.
or try the filters in realsense-viewer first.

Maybe L515 can't support disparity map. Because disparity map is generated for stereo IR camera to calculate depth map. L515 has Lidar sensor. This sensor directly get depth value from sensor. Unfortunately I have no L515 camera because it's not for sale in my country. So I can't test. Try to turn off disparity map option.

@wodndb @RealSenseSupport oh, my camera is a d435

librealsense has been fixed this issue in 2.39.0.
Please try the latest release. Thx.

@xraxra As the issue fixed, close this accordingly. Please feel free to create new one if you have any other questions or issues. Thanks!


Replace ctrlf-mode-bindings and ctrlf-minibuffer-bindings with keymaps

First of all, thank you @raxod502 for this awesome package!
I managed to address #62. It'll be great if you can take a look and provide me
your feedback. 🙇 Here's what's happening:

Add explicit ctrlf-mode-map and  ctrlf-minibuffer-mode-map keymaps
Show one-time deprecation warning messages

This is my first time contributing to your project (or any Emacs open-source
project.) I think I followed all the things in the contributor guide. Please let
me know if I miss anything.
Credits:
Also, really appreciate @rgrinberg for the groundwork in #64. I noticed your
work but it was hard for me to build on top of your branch while keeping the git
history clean. I ended up starting from scratch but took some inspirations from
your work. You deserve some credits in this PR!

Force-pushed just to appease the linter :P

Hey @raxod502 , thank you for taking the time!
The fixes make sense to me.  Thank you for doing that 🙇


Error Message: Encountered an error (ServiceUnavailable) from host runtime.

<Please be sure to remove any private information before submitting.>
Repro steps:
<Enter steps to reproduce issue>
Action: azureFunctions.deploy
Error type: BadRequest
Error Message: Encountered an error (ServiceUnavailable) from host runtime.
Version: 0.13.1
OS: win32

@yashag66 can you comment with repro steps? Does this happen consistently for you?
Additionally, you can try upgrading to the latest version of the extension (0.15.0). NOTE: you'll have to make sure you're on VS Code version at least 1.31.0 before you can update our extension.

I'm getting the same error consistently as of yesterday. (Deploying was working fine two days ago and prior)
Info:
VS Code Version: 1.32.3
Azure-Functions-Extension: 0.15.0
Azure-Functions-Core-Tools: 2.4.419
OS: Windows 10 - 64
Docker: 18.09.2
Have tried deploying separate Function apps to different subscriptions and Linux App-Service-Plans.
(Side Note: This same error pops up in the portal when trying to access Function app settings.)

I'm having exact same issue.  Been happening since 3/16
Deleted all linux function apps and created fresh one and same issue

I tried deploying to a different region (Linux App Service Plan) with success.
All of my deployments on US-East since yesterday have failed failed while US-West works okay.

@sstojanovic-ispt good to know about the regions - could've been an outage in US-East
Let me know if y'all are still having issues in all regions


macOS High Sierra & Firefox. Enabling scrollbars to display "always" causes page behind modal to move on opening modal

To replicate this issue:

I'm using a MacBook Pro with Retina display. The Retina display may assist in causing the issue but I'm not sure.
On macOS High Sierra, go to System Preferences then General and set "Show scroll bars" to "Always".
Open the bootstrap modal documentation pages, both v3 and v4 replicate the issue
https://getbootstrap.com/docs/3.3/javascript/#modals
https://getbootstrap.com/docs/4.1/components/modal/
Press the "Launch demo modal"

You should see the page "move" because the scroll bar disappears. Normally Bootstrap applies padding to the body of the page to accomodate this and it seems to work correctly in both Chrome and Safari, but it does not always seem to get added on Firefox. I have also tested Firefox in Windows which worked correctly to (scrollbars were already displaying by default)

I just tested this with Firefox 64.0 and everything looks fine. Can you check if everything is fine or your side, @DannyJJK?


[BEAM-9547] Dataframe covariance and correlation.

This implements correlation, covariance, and standard deviation for series and dataframes.
It is split up into three commits. The first is the math-heavy one that implements the distributed algorithm, the second uses it everywhere, and the third adds an apply method to scalars to simplify things.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @TheNeuralBit


ISPN-11632 Address comments in ISPN-10457

https://issues.redhat.com/browse/ISPN-11632

Rebased

In cases like this where the original issue is still in the same development stream, i.e. 11.0.x, can we not reopen the original Jira? The additional Jira provides no insights into the work and just adds another layer of indirection. Something like "ISPN-10457 Address additional feedback" ideally with a summary of the new changes would be much more informative.

It is all of Dan's comments on https://github.com/infinispan/infinispan/pull/8096

I understand that :slightly_smiling_face:
My point is that creating an additional Jira for this purpose is just an extra layer of indirection which adds noise for the sake of process opposed to adding any semantic value. Jira provides history, so if anybody did wonder why there was two PRs associated with a Jira the information is available.

Yeah, it becomes harder because this also spans different versions.

@danberindei I think you need to be the reviewer of this PR as it's responding to your comments.

Updated and rebased.

Thanks @wburns


'Non option field is missing' error when deserializing

I'm getting a 'Non option field is missing' error when deserializing. My JSON looks like this:
{
"csvFilePath": "C:\Users\Mike\source\repos\Validator2\data\cars.csv",
"delimiter": ",",
"maxErrors": 2,
"numHeaderLines": 0,
"validationList": [
{
"name": "Year",
"desc": "The year the car was made.",
"fieldType": "integer",
"minLen": 4,
"maxLen": 4,
"minValue": 1930,
"maxValue": 2023
},
{
"name": "Make",
"desc": "The make of the car.",
"fieldType": "string",
"minLen": 0,
"maxLen": 35,
"minValue": "A",
"maxValue": "zzzz"
},
{
"name": "Model",
"desc": "The make of the car.",
"fieldType": "string",
"minLen": 0,
"maxLen": 35,
"minValue": "A",
"maxValue": "zzzz"
},
{
"name": "Description",
"desc": "The make of the car.",
"fieldType": "string",
"minLen": 0,
"maxLen": 35,
"minValue": "A",
"maxValue": "zzzz"
},
{
"name": "price",
"desc": "how much it costs",
"fieldType": "decimal",
"minLen": 0,
"maxLen": 6,
"minValue": 100,
"maxValue": 250000
}
]
}
I'm deserializing into RawParamsRecord:
type RawValidationParams = {
name     : string
desc     : string option
fieldType: string option
//fieldCode: FieldCode option
minLen   : int option
maxLen   : int option
minValue : decimal option
maxValue : decimal option
}
type RawParamsRecord = {
csvFilePath   : string
delimiter     : string
maxErrors     : int
numHeaderLines: int
validationList_: RawValidationParams list
}
FSharp.Json.JsonDeserializationError: 'JSON Path: validationList_. Non option field is missing'
Originally some of the fields in the JSON file list (e.g., maxValue) were missing., so I filled in all of the values in the array of records. Since most of these are options I thought that should be OK. I'm at a complete loss as to what could be going on.

Hi Mike @cmdoffing. You have the field "validationList_" in your record. Pay attention to "" in the end. But your JSON has the field named "validationList". Hence the error message: the validationList in no an option but it's missing in JSON...


 Unsupported URL Type "link:": link:dummy.js

npm ERR! A complete log of this run can be found in: /home/george/.npm/_logs/2024-05-09T10_09_57_883Z-debug-0.log

 cat /home/george/.npm/_logs/2024-05-09T11_43_25_234Z-debug-0.log
0 verbose cli /home/george/.nvm/versions/node/v20.10.0/bin/node /home/george/.nvm/versions/node/v20.10.0/bin/npm
1 info using<EMAIL_ADDRESS>2 info using<EMAIL_ADDRESS>3 timing npm:load:whichnode Completed in 1ms
4 timing config:load:defaults Completed in 1ms
5 timing config:load:file:/home/george/.nvm/versions/node/v20.10.0/lib/node_modules/npm/npmrc Completed in 2ms
6 timing config:load:builtin Completed in 2ms
7 timing config:load:cli Completed in 1ms
8 timing config:load:env Completed in 0ms
9 timing config:load:file:/home/george/.npm/_cacache/tmp/git-clonejNFjrW/.npmrc Completed in 0ms
10 timing config:load:project Completed in 1ms
11 timing config:load:file:/home/george/.npmrc Completed in 0ms
12 timing config:load:user Completed in 0ms
13 timing config:load:file:/home/george/.nvm/versions/node/v20.10.0/etc/npmrc Completed in 0ms
14 timing config:load:global Completed in 0ms
15 timing config:load:setEnvs Completed in 0ms
16 timing config:load Completed in 5ms
17 timing npm:load:configload Completed in 5ms
18 timing config:load:flatten Completed in 1ms
19 timing npm:load:mkdirpcache Completed in 0ms
20 timing npm:load:mkdirplogs Completed in 0ms
21 verbose title npm run gentypes
22 verbose argv "run" "gentypes"
23 timing npm:load:setTitle Completed in 0ms
24 timing npm:load:display Completed in 1ms
25 verbose logfile logs-max:10 dir:/home/george/.npm/_logs/2024-05-09T11_43_25_234Z-
26 verbose logfile /home/george/.npm/_logs/2024-05-09T11_43_25_234Z-debug-0.log
27 timing npm:load:logFile Completed in 3ms
28 timing npm:load:timers Completed in 0ms
29 timing npm:load:configScope Completed in 0ms
30 warn using --force Recommended protections disabled.
31 timing npm:load Completed in 16ms
32 silly logfile start cleaning logs, removing 1 files
33 silly logfile done cleaning log files
34 timing command:run Completed in 409ms
35 verbose exit 1
36 timing npm Completed in 439ms
37 verbose code 1

I think I have to use pnpm.


Opni AIOps service fails to update some logs

Some logs are never updated even after Opni AIOps has processed them. Should add these logs back to the async queue and retry to update them up to 5 times
E.g.
2022-10-27 01:29:42,705 - root - ('1 document(s) failed to index.', [{'update': {'_index': 'logs-v0.5.4-000004', '_type': '_doc', '_id': 'ff85901e-92f2-4bcc-a452-a354446e4fbe', 'status': 404, 'error': {'type': 'document_missing_exception', 'reason': '[_doc][ff85901e-92f2-4bcc-a452-a354446e4fbe]: document missing', 'index': 'logs-v0.5.4-000004', 'shard': '0', 'index_uuid': 'An-oA4WyRXeHhan5FZ5akQ'}, 'data': {'doc': {'masked_log': '<klog_date> <num> <go_file_path> reopencontainerlog from runtime service failed err = rpc error : code = unknown desc = docker does not support reopening container log files containerid = <token_with_digit>', 'template_matched': '<klog date> <num> <go file path> reopencontainerlog from runtime service failed err = rpc error : code = unknown desc = docker does not support reopening container log files containerid = <token with digit>', 'template_cluster_id': 635, 'inference_model': 'drain', 'anomaly_level': 'Anomaly'}}}}])

I would say it depends on different conditions. Maybe just throw away the logs


[Bug] nullable date in repeatable field is not working

Bug
What I did
I have a belongsToMany relation with a pivot table. The pivot table has nullable revoked_at attribute.

I am using repeatable field to fill the pivot table as follows:

What I expected to happen
revoked_at to be set correctly.
What happened
It works fine when I enter a date but it causes the following error when I keep it empty:
SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect date value: '' for column `revoked_at` at row 1 (SQL: insert into `supervisor_course` (`course_id`, `revoked_at`, `user_id`) values (1, , 4))

What I've already tried to fix it
I tried to disable the strict mode as mentioned here, the error disappeared but the inserted value is 30/11/1899
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
PHP VERSION:
PHP 7.4.9 (cli) (built: Aug  4 2020 11:52:41) ( ZTS Visual C++ 2017 x64 )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
LARAVEL VERSION:
v8.37.0@cf4082973abc796ec285190f0603380021f6d26f
BACKPACK VERSION:
4.1.41@44770347b918e42c052d0a138c24535b43e32472

@mamprogr
Sorry for taking time to come back here.
So, you are trying to populate a BelongsToMany relation with a repeatable field, at the present moment, that is not supported unless you are using https://github.com/Laravel-Backpack/CRUD/pull/3410 this PR.
For the moment BelongsToMany work only with selectable elements.
Otherwise you need to override your store() method in SomeEntityCrudController and do the manual saving of supervisors. https://backpackforlaravel.com/docs/4.1/crud-operation-update#callbacks-1
If you give a try to that PR and your current problem is solved by it, please let us know in the comments, it could help to speed up the merging process.
I am going to close this as I don't think there is much more we can do here, please use the current solution provided or the PR. If you think I am wrong, please re-open 👍
Wish you the best,
Pedro


Nicer error message for schema with missing data source

Internal context: https://prisma-company.slack.com/archives/C4GCG53BP/p1597674794047900
Schemas now require a datasource for generate, otherwise you get a panic like this:
 FAIL  src/__tests__/getGenerators/getGenerators.test.ts
  ● getGenerators › basic
    Schema parsing
    thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', query-engine/query-engine/src/cli.rs:91:48
    stack backtrace:
       0: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
       1: core::fmt::write
       2: std::io::Write::write_fmt
       3: std::panicking::default_hook::{{closure}}
       4: std::panicking::default_hook
       5: std::panicking::rust_panic_with_hook
       6: rust_begin_unwind
       7: core::panicking::panic_fmt
       8: core::panicking::panic
       9: query_engine::main::main::{{closure}}::main::{{closure}}
      10: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll
      11: std::thread::local::LocalKey<T>::with
      12: scoped_tls::ScopedKey<T>::set
      13: async_executor::LocalExecutor::run
      14: scoped_tls::ScopedKey<T>::set
      15: tokio::runtime::context::enter
      16: tokio::runtime::Runtime::enter
      17: std::thread::local::LocalKey<T>::with
      18: std::thread::local::LocalKey<T>::with
      19: async_std::task::builder::Builder::blocking
      20: query_engine::main
      21: std::rt::lang_start::{{closure}}
      22: std::rt::lang_start_internal
      23: main
    note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

We should have a helpful error message instead.

This was actually done during Milestone 2.5

Strange enough I can not reproduce the error message with 2.4.1 now :/ If this was ever real?

Yes I definitely got that error many times in our tests 😄

Can you try a reproduction outside the tests but with a Prisma project?


Display chain icons in Settings > Select Active Networks screen

Maybe chain ID too.
Related: https://github.com/AlphaWallet/alpha-wallet-ios/issues/3464#issuecomment-979787211

Do you mean something like this?

Yes.

Follow ups:

[ ] Other places where there are "checkboxes"
[ ] Other places where list of chains are displayed


increase coverage unit test

Coverage decreased (-0.5%) to 63.0% when pulling aa634211b4adcbac6813de6e75d14c61b0a6aaff on leslieaula:dev into 4c4f384642938c8c83c717dd815bfa68642f90c2 on danliris:dev.

Coverage decreased (-0.4%) to 63.122% when pulling 42165c678dece1d8068f4a3d626635838032bfa9 on leslieaula:dev into 4c4f384642938c8c83c717dd815bfa68642f90c2 on danliris:dev.


[Android] Style.Builder().fromURI("https://...") fails to parse style

When I try to use something like this (org.maplibre.gl:android-sdk:9.4.2):
override fun onMapReady(mapboxMap: MapboxMap) {
  mapboxMap.setStyle(
      Style.Builder().fromUri("https://api.maptiler.com/maps/some-u-u-i-d/?key=someKey#18.2/53.66886/10.23655")
  ) { style ->
  // ...
  }
}

the OnDidFailLoadingMapListener receives the following error message: Failed to parse style: Invalid value. at offset 0
When I bundle the contents of that same online resource as an asset for example or when I use a different mapbox:// style online resource, everything works fine. It seems to me that something goes wrong detecting the https URL.

My bad - I just forgot to add style.json to the url path. 🤦♂


Release: Version v0.6.6 RC

:package: :rocket:

Builds ready [cd3cf80]builds: chrome, firefox, opera
bundle viz: background, ui, portal-inpage, portal-contentscript, ui-libs, bg-libs, phishing-detect
dep viz: background
all artifacts