What is the (inteded) behavior of SQPOLL + timeouts?

Note this question is in the context of using the low-level sycall interface, not liburing specifically.
I can kind of guess that you wouldn't use SQPOLL with timeouts in any meaningful way - I'm trying to figure out a good way to implement async sleep()-like timers, which historically (see: epoll) are implemented using a min-heap and poll timeouts, not with something like timerfd.
Since under the SQPOLL mode we do active polling of the completion queue until we receive the flag that the underlying kernel thread has shut down, is there a performant way to "wait" for a completion queue event in this mode? Or is the intended behavior of the userspace application to also perform as-fast-as-possible polling of the completion queue, too?
As per my understanding, in such a case the vDSO provided by the kernel can give us efficient time of day lookups without syscalls, so we can simply cache and check the min-heap's next timeout value against it with minimal overhead, correct? I know we could be using io_uring timeout events for this directly but I'd rather keep the submission queue as free as possible.
Thanks for any insight :)

EDIT: one other somewhat related question that the documentation isn't clear about (I've seen conflicting verbiage):
Does the SQPOLL thread shut down (time out) even if there are in-flight submissions? E.g. if I have a long-running operation that completes at a time later than the timeout, will the thread still timeout? In this case, I would have to keep waking up the thread until all of my in-flight requests have been completed, right?
Some of the documentation makes it seem like a submitted event that hasn't yet completed could be "lost" if the kernel polling thread wasn't woken up periodically.
Ideally it would only time out once the number of in-flight submissions reaches zero and there have been no submissions for X amount of time.
EDIT2: Just confirmed that std::chrono::high_resolution_clock::now() uses the vDSO values and not a syscall on our system/compiler, so getting that information should be quite cheap.

Doing an strace of the sq-poll-kthread test, it appears io_uring_enter() is still being called with GETEVENTS which goes against my theory above.
It seems like, with SQPOLL, there will always need to be an initial syscall to kick off the kthread upon the first submission, correct? It would be like IORING_SQ_NEED_WAKEUP being 1 by default.
Without confirming this is actually the case and not some other mis-use of the low level syscalls on my part, would it be possible to have the kernel automatically populate the sq ring's flags with |= IORING_SQ_NEED_WAKEUP? Sure it's trivial bookkeeping on our part but it's an easily missed bug.
This would also allow the kernel implementation to move to an automatic thread kickoff in the future with full backwards compatibility, since in a lot of cases a service is going to be called when we know we'll be performing I/O in the very near future (e.g. in systemd socket-driven service initialziation).

SQPOLL is about polling Submission Queues by a kernel thread. Completions are waited as usual.
SQPOLL only takes SQ Entries (SQE) from SQ, it doesn't necessarily executes them. E.g. it may throw it for async execution by some other means. SQPOLL is awake if it tries to exeucte a request, but shouldn't be important for users.
So, SQPOLL can fall asleep while there are still inflight requests, and that's ok. The requests will complete asynchronously. Regardless of how they executed, they can be waited as usual (see 1.)

would it be possible to have the kernel automatically populate the sq ring's flags with |= IORING_SQ_NEED_WAKEUP?

That what SQPOLL thread do before going to sleep, so users can react. On the user end it's like below

for (...)
    add_new_cqe_into_shared_memory(); // aka into SQ

if (io_uring->flag & IORING_SQ_NEED_WAKEUP) // thread is sleeping, need to wake it up
    io_uring_enter(...);
else
    ; // do nothing, the kthread will find SQEs without extra help

This would also allow the kernel implementation to move to an automatic thread kickoff in the future with full backwards compatibility, since in a lot of cases a service is going to be called when we know we'll be performing I/O in the very near future (e.g. in systemd socket-driven service initialization).

Not sure what you mean, automatic kickoff by whom or by what event?

Completion timeouts were historically implemented in liburing by timeout SQEs (i.e. submit SQE, wait CQE).
This approach has its problems, so there is a new API for that queued for 5.11. But again, completion waiting
is not a busy loop/polling by anyone, you call a syscall and it actually sleeps until the right moment.
Another story for IOPOLL, but you haven't mentioned it.

That what SQPOLL thread do before going to sleep, so users can react. On the user end it's like below

That's what I'm saying - there needs to be an initial call to enter in order to start the submission queue, and by default the flags parameter is 0. In my own testing, the NEED_WAKEUP flag is never raised directly after a setup syscall - you always have to submit at least one I/O message.
The tests all seem to assume there will be at least one submission before the NEED_WAKEUP is checked, but that isn't always going to be the case in more generalized frameworks... By default, you need to wake up the submission thread via an enter syscall, right?
Or am I misunderstanding something?

This approach has its problems, so there is a new API for that queued for 5.11. But again, completion waiting
is not a busy loop/polling by anyone, you call a syscall and it actually sleeps until the right moment.

I see, I don't see how this really solves the syscall problem though. I thought this would be a mode where the entire message passing mechanism is handled via busy polling on both sides and using memory barriers to ensure ordered memory R/W. This would forego all syscalls under heavy load, which I figured was the goal here.
Is there a mode for polling for completions without syscalls, e.g. a CQPOLL mode, planned?

That's what I'm saying - there needs to be an initial call to enter in order to start the submission queue, and by default the flags parameter is 0. In my own testing, the NEED_WAKEUP flag is never raised directly after a setup syscall - you always have to submit at least one I/O message.

It should start out running, then go to sleep (and set NEED_WAKEUP when it does).
There seems to be some confusion here on what polling is, and how it affects the SQ and CQ ring, so let me try and clarify that a little bit. SQPOLL is asking a thread to poll the SQ ring for events. When it sees them, they are dispatched, and when complete, the post an entry to the CQ ring. There's no CQPOLL mode because it is nonsensical. Either events happen async, in which case you can just poll the CQ ring from userspace (no kernel support needed for that), or you run in IOPOLL mode, in which case you very much DO want to enter the kernel as it's the application responsibility to poll for and process completions. In other words, a request will either complete async at some point by itself, or it's an IOPOLL completion which doesn't trigger anything async, it must be handled explicitly.
Hence if you're not doing IOPOLL, then your suggested CQPOLL mode is simply just reading the CQ ring for changes from userspace.

That's what I'm saying - there needs to be an initial call to enter in order to start the submission queue, and by default the flags parameter is 0. In my own testing, the NEED_WAKEUP flag is never raised directly after a setup syscall - you always have to submit at least one I/O message.

So, you're saying that initially it sleeps but doesn't set NEED_WAKEUP. Right?
That's not nice if so, I need to check that

I see, I don't see how this really solves the syscall problem though. I thought this would be a mode where the entire message passing mechanism is handled via busy polling on both sides and using memory barriers to ensure ordered memory R/W. This would forego all syscalls under heavy load, which I figured was the goal here.
Is there a mode for polling for completions without syscalls, e.g. a CQPOLL mode, planned?

That's userspace, nobody keeps you from polling CQ. Actually liburing first checks if there is anything in the CQ, and may return without doing any syscall.

So, you're saying that initially it sleeps but doesn't set NEED_WAKEUP. Right?

That would most certainly be a bug, of course. We start out running, but the going to sleep is no different than subsequent versions of that. So hard to imagine how that bug would exist and be exclusive to just the initial sleep.
What kernel is being used?

Just ran a quick test on my current tree, and it works as described:
[root@archlinux liburing]# test/sqpoll-sleep
Got wakeup after 106 msec

This is setting up the ring with 100msec idle period, so we expect the flag to NOT be set initially, then be set sometime after 100 msec. The test exits when it's set, which is right around that time. Test case:
#include <errno.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <sys/time.h>
#include "liburing.h"

static unsigned long long mtime_since(const struct timeval *s,
				      const struct timeval *e)
{
	long long sec, usec;

	sec = e->tv_sec - s->tv_sec;
	usec = (e->tv_usec - s->tv_usec);
	if (sec > 0 && usec < 0) {
		sec--;
		usec += 1000000;
	}

	sec *= 1000;
	usec /= 1000;
	return sec + usec;
}

static unsigned long long mtime_since_now(struct timeval *tv)
{
	struct timeval end;

	gettimeofday(&end, NULL);
	return mtime_since(tv, &end);
}

int main(int argc, char *argv[])
{
	struct io_uring_params p = {};
	struct timeval tv;
	struct io_uring ring;
	int ret;

	if (argc > 1)
		return 0;

	p.flags = IORING_SETUP_SQPOLL;
	p.sq_thread_idle = 100;

	/* Setup the ring with a registered event fd to be notified on events */
	ret = io_uring_queue_init_params(1, &ring, &p);
	if (ret) {
		fprintf(stderr, "queue_init=%d\n", ret);
		return 1;
	}

	gettimeofday(&tv, NULL);
	do {
		usleep(1000);
		if ((*ring.sq.kflags) & IORING_SQ_NEED_WAKEUP) {
			printf("Got wakeup after %ld msec\n", (long)mtime_since_now(&tv));
			goto done;
		}
	} while (mtime_since_now(&tv) < 1000);

	printf("No wakeup in %ld msec\n", (long)mtime_since_now(&tv));
	return 1;
done:
	return 0;
}

I'm an idiot, I apologize.
I was casting the result of the first sq offsets mmap() call to a uint32_t* instead of a char * (in c++, since void* arithmetic is not allowed). The offset math was being scaled by 4 when setting up the pointers.
For anyone curious, here's the low-level reproduction of the above liburing snippet (which works as expected):
#include <unistd.h>
#include <linux/io_uring.h>
#include <sys/syscall.h>
#include <sys/mman.h>

#include <assert.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <stdint.h>
#include <stdatomic.h>

#define NUM_RING_ENTRIES 64
#define IORING_FEAT_SQPOLL_NONFIXED (1U << 7) /* not defined in system headers */

#define IO_URING_READ_ONCE(var) \
        atomic_load_explicit((_Atomic __typeof__(var) *)&(var), memory_order_relaxed)

int main(void) {
        int status = 1;

        size_t sq_ring_sz;
        void *sq_ring;

        struct io_uring_params params;
        memset(&params, 0, sizeof(params));

        params.flags |= IORING_SETUP_SQPOLL;
        params.sq_thread_idle = 2000;

        int fd = syscall(
                SYS_io_uring_setup,
                NUM_RING_ENTRIES,
                &params
        );

        if (fd == -1) {
                perror("io_uring_setup()");
                goto exit;
        }

        if (!(params.features & IORING_FEAT_SQPOLL_NONFIXED)) {
                fputs("SQPOLL_NONFIXED feature not present", stderr);
                goto exit_close;
        }

        sq_ring_sz = params.sq_off.array + params.sq_entries * sizeof(uint32_t);
        sq_ring = mmap(
                NULL,
                sq_ring_sz,
                PROT_READ | PROT_WRITE,
                MAP_SHARED | MAP_POPULATE,
                fd,
                IORING_OFF_SQ_RING
        );

        if (sq_ring == MAP_FAILED) {
                perror("mmap(IORING_OFF_SQ_RING)");
                goto exit_close;
        }

        uint32_t *sq_flags = (uint32_t *)( sq_ring + params.sq_off.flags );

        while (!(IO_URING_READ_ONCE(*sq_flags) & IORING_SQ_NEED_WAKEUP));

        status = 0;

        munmap(sq_ring, sq_ring_sz);
exit_close:
        close(fd);
exit:
        return status;
}

Quick note because I know it'll come up:
I understand it's probably best to use liburing where possible but in our case the low-level approach is necessary. Lots of little places where user-error can occur.
Thanks for the information, this cleared a lot of unrelated things up either way. I apologize for the noise.

There's no requirement to use liburing, it's just provided as a perhaps more approachable introduction than using the raw interface. So whatever works for you, all good.


implement tinting

I have adapted my previous implementation for texture drawing to the merged one and tinting works now.
Changes

adds a secondary canvas for drawing temporary stuff
adds another example where the raylib logo is tinted red

realted to #32

Oh, I haven't noticed that someone has already created another PR for that -.-
I think our two approaches are different enough though to leave them both open :)

generating and caching images in base64 may be useful even if this gets merged
having a background context may be useful when yours gets merged


[MetaSchedule] Include te/tensor.h instead of forward declaring te::T…

…ensor
ApplyHistoryBestNode declares an Array of Tensor. There are type traits used in Array that require that the element type is complete at the time of the declaration. With only a forward declaration compilation fails (clang 14.0.3, libc++).

Lesson learned here for me is that never do forward declaration if we can simply include a header :-)

It's actually a good practice to use forward declarations when the header is not needed.  The problem is that in some cases the types must me complete, in this case it was because there was std::enable_if used in the declaration of Array.  The trait checked in there required the checked type to be complete.
What I find surprising that it works with the compilers we use in CI.  I'm not sure of this is because of newer clang, or because I'm using libc++.

@kparzysz-quic Yeah I just verified with clang 14:
>>> clang++-14 --version
Ubuntu clang version 14.0.5-++20220603124341+2f0a69c32a4c-1~exp1~20220603124352.149
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/bin

but yet cannot reproduce the compilation issue...so i guess probably it's something with libc++


Supporting JMX annotations

Description of changes:

The operator will inject init-containers, open up ports on agent service/container if the following annotation is attached to a K8s workload - cloudwatch.aws.amazon.com/inject-jmx-{targetSystem} where targetSystem includes jvm, "tomcat", "kafka", "kafka-consumer", "kafka-producer"
Operator will inject JMX specific environment variables in the pod -
"OTEL_EXPORTER_OTLP_PROTOCOL"= "http/protobuf"
"OTEL_METRICS_EXPORTER"="none"
"OTEL_LOGS_EXPORTER"="none"
"OTEL_JMX_EXPORTER_METRICS_ENDPOINT="http://cloudwatch-agent.amazon-cloudwatch:4314/v1/metrics"
"OTEL_JMX_ENABLED",="true"
"OTEL_JMX_TARGET_SYSTEM"="jvm,tomcat"
Operator will open port 4314 on cloudwatch-agent container and service for reading metrics over HTTP protocol when the agent config has JMX enabled in the metrics section OR JMX-Container Insights is enabled in logs section
This PR is will use the custom JMX exporter to export JMX metrics - https://github.com/aws-observability/aws-otel-java-instrumentation/pull/901

Testing

Unit testing
Manual testing using the amazon-cloudwatch-observability helm-chart
i. Annotate a pod deploying a sprint boot project with instrumentation.opentelemetry.io/inject-java: "true" cloudwatch.aws.amazon.com/inject-jmx-jvm: "true" and deploy on the cluster
ii. Verified environment variables and init container are added to the pod
iii. Verified cloudwatch-agent service and container has the port 4314 open when the agent config has JMX enabled
iv. Verified jmx metrics are being published to CloudWatch

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

CloudWatch agent container port
│ Containers:
│   otc-container:
│     Container ID:   containerd://09823f59743f80abdf890a11dca9a7cd6f164cda4be1f2fb9e09fc5bb55737db
│     Port:           4314/TCP
│     Host Port:      4314/TCP

Cloudwatch agent service
 Port:              jmx-http  4314/TCP


NETOBSERV-922 - Flaky topology data

updated cypress testing
fixed topology crash on unknown nodes while grouping

/lgtm

/ok-to-test

All the cola layouts and force layouts look weird. This occurred after I refreshed after encountering the below error(was clicking a lot of things and ended up on this error, dont know the exact scope and group)

This is how topology looks

/label qe-approved

/approve


Area recognition seems to be broken?

Preparation

[X] I tested the latest release
[X] I looked at other issues (even the closed ones)
[X] I read the Troubleshooting Guide

FGO server
NA
FGA build number
1741
Describe the bug
After being forced to re-install my BlueStacks Emulator, i got the most recent FGA version. I had previously used 16xx and had no issues. But with this release, it seems area recognition is busted, or at least partially. Once the script starts and my support has been selected, the battle starts. Like always, the script clicks on the faces of each servant. On the third servant (support Castoria in my case here), it seemingly fails and instead accidentally clicks on the second Skill of my second Servant? I am unable to fix this issues, despite:

Going Fullscreen to get rid of the black borders (even tho that wasn't an issue for me beforehand)
Messing around with a multitude of settings inside the Emulator and FGA itself
Looking up similar posted issues and applying their fixes
I'm at a loss at what to do, and what's even more upsetting is that i desperately need to farm Summer 5 as Castoria ate up all my resources. Any help would be appreciated, thanks!
PS: I got an error from the FGA script when i enabled Screen Recording (Attempt to read from field int android.media.camcorderprofilefileformat failed...), so i resorted to using OBS. Why is all this such a hassle, been trying all day just to start farming in the BG...

Video
https://user-images.githubusercontent.com/109912797/180655563-41908120-5825-43ae-9c4b-cf412fb8138e.mp4
Device model
BlueStacks <IP_ADDRESS>3 P64
Android version
9
Screen size
1920x1080
RAM
16GB

That's Skill Confirmation, turn it off in FGO or on in FGA.
Everything else looks fine.

That's Skill Confirmation, turn it off in FGO or on in FGA.
Everything else looks fine.

Oh my god... it was literally that simple. Cannot believe i spent hours trying to fix this and missed that simple detail, i guess i got a little confused by it not doing a check on the support servant, but i suppose thats due to it being a dupe of my second servant? Regardless, it now works flawlessly, thanks a lot and my apologies!

The support servant is detected by looking at the +SUPPORT icon on the top right. That +SUPPORT icon is always present on NP and face cards.


Missing tornado dep

Just after install the viewer gives this error:
(py-env)[naufraghi@odello src]$ python -m plop.viewer --datadir=demo/profiles
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/home/naufraghi/.virtualenvs/py-env/lib/python2.7/site-packages/plop/viewer.py", line 7, in <module>
    from tornado.ioloop import IOLoop
ImportError: No module named tornado.ioloop

After pip install tornado it goes on as expected.

This is documented in the readme. I didn't want to make the whole package depend on tornado because the collector and viewer are often run separately, and I don't want the collector to have any extra requirements.

Ok, sorry, skipped the row.
Indeed perhaps a managed error message can offer a better user experience.


Saved Image's Dimensions Are Wrong for mm-Based Svgs

When using SVGs that use mm as width/height values (such as <svg width="10mm" height="10mm">...</svg>), the saved image is too small and the SVG is cropped.
The issue is in the Converter._getDimensions method - basically: If you don't want to start doing a lot of calculations, reading the width/height/viewbox attribute of the SVG element will only work well in a few cases.
What I found a convenient workaround was just using Chrome's calculated dimensions, roughly:
const svg = document.querySelector('svg');
const computedStyles = getComputedStyles(svg);
// Remove the 'px' from the string
let widthInPx = computedStyles.width.substring(0, computedStyles.width.length - 2);
widthInPx = parseFloat(widthInPx);

Sounds interesting. I'm open to pull requests that would implement this but the testing could be interesting.


Differentiate the main UTM window title from VM windows

After clicking Play to run a VM on macOS, the main UTM window and the VM's window have the same title:

This is confusing when trying to switch between them using the menu bar item "Window".
The VM and main windows should each gain additional text to indicate which one is which. For example, the VM window could indicate the state of the VM ("Windows 10 installed – running").

I think it's better to keep the title of the main window as UTM instead of the selected VM's name.

Here's my quick research into trying to fix this: UTM uses the .navigationTitle modifier to set the title in the main window UI. However, the title set there is also used in the dock context menu. As far as I can tell, there isn't any way to have a different navigation title and dock title.

Fixed with #3125


10.1 with jdk17 corretto

WiP Attempts to resolve #286

Linking to the very relevant https://github.com/docker-library/tomcat/pull/248#issuecomment-1329908153

I'm aware of it (plus the checks failed, as I haven't scrubbed this enough), but at least folks who need it can get functional Dockerfiles.

Thanks for the push (and for the implementation suggestions!! :bow: :heart:); I'm going to close this now in order to consolidate into https://github.com/docker-library/tomcat/pull/299 :sweat_smile:


goattracker: init at 2.75

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

There's an alternative release with stereo support, do you think you could package that one too?
https://sourceforge.net/projects/goattracker2/files/GoatTracker 2 Stereo/
If the build process is the same, the easiest way is probably to have an optional isStereo ? false argument and adjust the pname, src and version accordingly (its version is always 1 higher than the regular release's).

Adding the stereo version is a good Idea, I'll push the change soon

Is it possible for the stereo and non stereo version to have the same version?

@Lassulus are you asking if uptream will ever release goattracker and goattracker-stereo with a synced version or if we could/should sync them ourselves in the package?

uhm, I haven't put much thought into it. I'm also not sure why there is a non stereo version? wouldn't the stereo version be enough?

The Mono version is accurate to the actual system, as the emulated chip has no stereo controls.

A thanks for the explanation.
So I guess we can keep the versions separated for now and change it when they synchronize upstream.


Decode url in the logs page for better view

Thank you, but let's keep it for now as it is.
I'm not sure if it will be a good idea because users will not be able to differentiate the missing/invalid encoded url query parameters if we only display the decoded version.
Alternatively we can show both the normalized and the raw urls but the logs UI will change anyway with the planned refactoring in the near future as part of the Generalize logs task.


Allow binding to component inputs

Staying on this same topic of "feedback loop". I also wonder if we shouldn't make it possible for a component to have a global state so that it can be used as the other components. For instance, this component exposes a density.value globally in the page.

Originally posted by @oliviertassinari in https://github.com/mui/mui-toolpad/issues/351#issuecomment-1114277887
https://github.com/mui/mui-toolpad/issues/351#issuecomment-1114655485

The main problem to solve with that will be order of evaluation. When does which binding expression evaluate, how do you deal with cyclic structures, and how to detect infinite loops?

Started working on a new databinding implementation that allows for this. Still needs some work, the editor doesn't autocomplete all possible properties yet, but they're already usable, just ignore the red squigles.


Add Alfresco connector

Description
Add Alfresco connector
Fixes  https://github.com/ballerina-platform/ballerina-extended-library/issues/248
One line release note:

Add Alfresco connector

Type of change

[X] New feature (non-breaking change which adds functionality)

Test Configuration:

Ballerina Version: Ballerina 2201.0.0
Operating System: Ubunutu
Java SDK: Java 11

Checklist:
Changes to OpenAPI definition

[X] Modified info section of the OpenAPI definition file - Example

description - what the connector is about
x-ballerina-init-description OpenAPI extension - connector initialization details
x-ballerina-display OpenAPI extension - connector name and path to the connector icon

[X] Added proper description each API Key, if API Key authentication is defined in OpenAPI definition file

Changes to connector module

[X] Added license header at the top of each .bal file.
[X] Added Package.md as per the guide here
[X] Added Module.md for the module of the  connector as per the guide here
[X] Added connector icon to the root of the connector. Icon needs to be a png of 200x200 px size with name icon.png
[X] Added Ballerina.toml file with following information. For keywords refer to guide

Verifying connector module

[X] Compiled the connector successfully with the targeted ballerina version.
[X] Conducted smoke tests on the connector (Recommended when OpenAPI definition is obtain from an unofficial source)

Security checks

[X] Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
[X] Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

Added Quickstart with a sample


[telemetry] add protobuf for upstream DNS metrics

Add the counters of queries, responses, failures handled by upstream DNS server

Depends-on https://github.com/openthread/openthread/pull/9729


Initial sphinx documentation

This is a start to documentation managed by Sphinx.
Related to #268.
none

/test e2e v1.7

/retest


Started to update docker images

Codecov Report

Merging #255 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #255      +/-   ##
==========================================
- Coverage   62.80%   62.77%   -0.03%
==========================================
  Files          48       48
  Lines        3828     3828
==========================================
- Hits         2404     2403       -1
  Misses       1024     1024
- Partials      400      401       +1

Impacted Files
Coverage Δ

workers/scheduler/gaiascheduler/scheduler.go
59.21% <0.00%> (-0.56%)
:arrow_down:

workers/pipeline/ticker.go
47.77% <0.00%> (+0.63%)
:arrow_up:

Continue to review full report at Codecov.

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

I need to do some testing with all the new versions. Also, I'm going to deploy a test gaia instance which will run constantly so updates and upgrades can happen with long living pipelines.

I've created a long living deployment, which I'm going to update with these. I'll create a pipeline with each of these with the old version, then update, and every pipeline should still work nicely.

cppsdk/plugin.pb.h:17:2: error: #error This file was generated by an older version of protoc which is
#error This file was generated by an older version of protoc which is

Seems like I can't update protoc unless I update cppsdk as well.

Also node... same for the nodejs sdk. So I leave that out for now to minimise the changes.

All pipelines have been reviews and tested.


Profiles and channels should have empty state

I tried but I couldn't make the empty condition ¯_(ツ)_/¯

I more wanted to discuss what would go there! I can add in the empty state.


feat: Pre wired cbr ext

Description
https://github.com/terraform-ibm-modules/terraform-ibm-cbr/issues/222#issuecomment-1643783153
Types of changes in this PR
Changes that affect the core Terraform module or submodules

[ ] Bug fix
[x] New feature
[ ] Dependency update

Changes that don't affect the core Terraform module or submodules

[x] Examples or tests (addition or updates of examples or tests)
[x] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other

Release required?
Identify the type of release. For information about the changes in a semantic versioning release, see Release versioning.

[ ] No release
[ ] Patch release (x.x.X)
[x] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content
This release contains feature to create pre-defined CBR rules in a given account as part of FS Cloud profile.
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author. The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).
Merge by using "Squash and merge".

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

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


MIDI TX Buffer sizes.

@yatli (might want to think about this)
A word on the TX Buffers:
The TX ring buffers are currently sized at 3KB. This seems sufficient for the largest dumps I have been transmitting in MCL (MDPattern). TX buffer transmission happens on ISR, when the TX queue for the UART is clean another byte from the buffer is read, and transmitted. The rate at which the TX buffer gets consumed is limited by the port speed.
These might need to be bumped up for handing A4Pattern MNMPattern sizes to prevent buffer overflow.
Alternatively, the data encoder code, could be modified to "wait for the UART queue to be empty' before sending more encoded bytes.

why does TX even need a buffer?
will the user buffer be modified during asynchronous send?

MidiUart class has two commands for sending data. m_putc() and m_putc_immediate().
m_putc_immediate() will skip the TX buffer and wait for the UART queue to be clean before transmitting.
Without the buffer, program execution would be slow and would have to wait for each byte to be sent, before proceeding with next line of code.

thanks for the explanation. I think I misunderstood the intent.
Anyway, I'm providing a little bit background info here:
In operating systems we have zero-copy async I/O (example: Windows I/O completion port, abbr. IOCP), where the OS accepts a user buffer and use it directly without a kernel buffer. The requirement is that the user buffer should never be touched by the user code until completion.
The assumption is quite different, that a user posts "buffers" to a network driver, not byte-by-byte.
In the byte-by-byte scenario, we do need a buffer.

Understood. Welcome to the world of MIDI :smiley:

tx buffers now stored in high RAM bank.


stereo example?

hi @mattetti
I've started toying around with an implementation of go-audio/audio & go-audio/generator but I can not figure out how to produce stereo output on either real-time or offline example.
It seems the whole project has not moved for a couple of years but any pointers/help are very welcome.

Hey @bh90210, you are right, there is a bug in func (o *Osc) Fill(buf *audio.FloatBuffer) error  where the buffer doesn't get properly populated for stereo buffers. The end results is a file with only half of the signal available and at twice the expected frequency. I'll fix that shortly.

So here is the example to produce a stereo output: https://github.com/go-audio/generator/blob/master/examples/offline/stereo/main.go
you can run the program using go run main.go or pass argument. The problem was a simple indexing problem when filling up the buffer using the generator: https://github.com/go-audio/generator/commit/fe5438877d8c9150aeda56c0b2990670110efc70#diff-74fe825dbc701700fc5d3b8bb4e40c46R84
I hope this helps. Feel free to reopen the issue if you are still seeing issues.

Hey @bh90210, you are right, there is a bug in func (o *Osc) Fill(buf *audio.FloatBuffer) error  where the buffer doesn't get properly populated for stereo buffers. The end results is a file with only half of the signal available and at twice the expected frequency.

yeap, this is what was happening :)
thanks a lot for the fast reply and help! I will check it out asap.


DEVX-1671 Fixes issue with operator version numbers in Makefile

Previously we published without the operator rev ver number.  I deleted invalid
tags from the dockerhub repository as well.

@ybyzek bump (please)

@rspurgeon Quick question: should OPERATOR_VERSION be bumped to 1 or would that be a separate PR? Otherwise LGTM

The latest Operator version right now is <IP_ADDRESS>, if they release a patch under the 5.4.1 CP patch, then we would build <IP_ADDRESS>.    IIUC this needs to remain at 0 for now

@rspurgeon great, thanks for the clarification


Bump NDK to 25

Summary:
Bumps NDK to current LTS Release.
Changelog:
[Android] [Changed] - Bump NDK to 25
Test Plan:
CI Green ✅

Looks like CircleCI's machine broke on installing dependencies on iOS 🥲

@cortinico Yeah, so:
FBJNI -  23.1.7779620
Hermes - Not sure, where to find it.
Flipper - 25.1.8937393
I can create PRs bumping versions in those repositories.
Yes, I can look at ReactAndroid, is just doing that - will be okay in build.gradle.kts?
val ndkVersion by extra(System.getenv("ANDROID_NDK_VERSION") ?: "25.2.9519653")

Also I think we can bump NDK version in the docker-android, WDYT?

FBJNI - 23.1.7779620

I'm currently working on it. Will be out with FBJNI version 0.5.0 sometime soon

Hermes - Not sure, where to find it.

This is controlled by ReactAndroid/hermes-engine/build.gradle so it will be bumped with everything.

Flipper - 25.1.8937393

That's correct as that's the version we want to use actually (see https://developer.android.com/build/releases/gradle-plugin#compatibility-8-0-0 as the default for 8.0.0).
We'll have to find which version of Flipper is the first one that bumped NDK to 25 and make sure we use it.

Also I think we can bump NDK version in the docker-android, WDYT?

Yup that's also needed 🙏

We'll have to find which version of Flipper is the first one that bumped NDK to 25 and make sure we use it.

It was bumped in this PR https://github.com/facebook/flipper/pull/4443, and it was first released in 0.187.1, btw. just out of curiosity why the first one?

Yup that's also needed 🙏

PR: https://github.com/react-native-community/docker-android/pull/204

and it was first released in 0.187.1, btw. just out of curiosity why the first one?

Because we might already have it shipped/bumped, but that's not the case as we're on 0.182.0

@szymonrybczak can we move this forward?

FBJNI - Bumped, but not released yet.
docker-android - Bumped, but not released yet.

I will take of those two next week.

Flipper - Not bumped in RN repository.

@szymonrybczak do you want to attempt to do this bump? It should be fairly easy (just search for a previous Flipper bump) 👍 I can support if needed

Hey @szymonrybczak
Sorry this took longer for me, but now we should be fully unblocked:
https://github.com/facebookincubator/fbjni/releases/tag/v0.5.0
https://github.com/react-native-community/docker-android/releases/tag/v10.0
Can I ask you to bump those 2 and rebase? And we should be able to import this 👍


Move cleanup of older log files into shared process

That is typically where we do cleanup tasks. I am talking about: https://github.com/Microsoft/vscode/blob/5eff1e2ede99f34dfa0f509ffc62a06d47d119a1/src/vs/code/electron-main/main.ts#L55

@sandy081 via https://github.com/Microsoft/vscode/commit/0c14b8fc220071310d8b1dc6eb7593bd53b7c7fe


Error when loading json config for Enrich 2

Hi,
I am running dumpling successfully to about 90-92% done (in terms of jobs in the workflow), however I encounter an issue when running Enrich 2 (it appears to be raised when running the main). Here is the error:
Traceback (most recent call last):
  File "/project/chlandry/users/rodur28/dumpling/.snakemake/conda/67d2d89bb9799e59a640f480438207d3_/lib/python3.13/site-packages/enrich2/main.py", line 160, in main_cmd
    cfg = json.load(open(args.config, "U"))
                    ~~~~^^^^^^^^^^^^^^^^^^
ValueError: invalid mode: 'U'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/project/chlandry/users/rodur28/dumpling/.snakemake/conda/67d2d89bb9799e59a640f480438207d3_/bin/enrich_cmd", line 8, in <module>
    sys.exit(main_cmd())
             ~~~~~~~~^^
  File "/project/chlandry/users/rodur28/dumpling/.snakemake/conda/67d2d89bb9799e59a640f480438207d3_/lib/python3.13/site-packages/enrich2/main.py", line 164, in main_cmd
    raise ValueError("Improperly formatted .json file [{}]".format(DRIVER_NAME))
ValueError: Improperly formatted .json file [enrich_cmd]

I was getting the same error when trying to run dumpling on a dataset with only two time points, which meant the JSON config file was almost empty, but I've corrected this and now it looks ok to me (see attached file)
Thanks for your help!

Ah, this was a silly one by me, I forgot to merge my updated branch into main. This should be fixed now. Could you try again? Hopefully nothing else pops up...

Thanks ! I think it's good, I do get another problem (sorry about that..) but it appears to be related to rosace. The enrich2 steps has successfully created all h5 files ;)

Thank you for submitting these issues! Sorry for the bugs, but I appreciate the opportunity to resolve them :)


Word Wrap

Hi there! I think Word Wrap feature is a must in DartPad. It saves time to the user and helps to have a more organized code. Thanks!

I believe word wrapping is enabled? Do you mean something else - formatting?


INPUT type buttons don't get rounded corners

BUTTON and A ones do. Make them all look and behave the same.

Closed via https://github.com/chef/chef-web-core/pull/53


Concept: take from multiple template sources

The script should be able to take from multiple template sources and draw a composite.
Basically, the order of sources will determine which pixel color gets priority when there are pixel conflicts between sources.
This would dramatically simplify alliances.

I recently added this to the OnePiece script. It's not using an array, but likely could very easily.
https://github.com/Lopeh/onepiece-place/blob/main/userscript.user.js#L91-L96

If you're willing to upstream that and get it working in an array, that would be gold man. And I'm 100% on board with you adding youself in the header's credits.
This repo ended up being very popular, the insights are crazy!


[Bug]: Testimonial link on Leaderboard page does not navigate to the Testimonial page

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
On the Leaderboard page of the project, clicking the link to the Testimonial page does not navigate to the Testimonial page. This issue prevents users from accessing the Testimonial page through the provided link.
Expected behavior
After clicking the link to the Testimonial page on the Leaderboard page, the user should be redirected to the Testimonial page.
Add ScreenShots

On which device are you experiencing this bug?
No response
Record

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

Thank you for creating this issue! 🎉 We'll look into it as soon as possible. In the meantime, please make sure to provide all the necessary details and context. If you have any questions or additional information, feel free to add them here. Your contributions are highly appreciated! 😊
You can also check our CONTRIBUTING.md for guidelines on contributing to this project.

can you assign me this issue ?

@Shahbaz898414 Please resolve this by tomorrow or else I will have to unassign you.

can you guide me to solve this issue?

Have you created Supabase account? Have you read the project setup file in README?

Have you created Supabase account? Have you read the project setup file in README?

Yes i created the Supabase account
Proof

@ashutosh-rath02
thanks you for your time, i am able to setup the project in my system, i did some silly mistake.

@ashutosh-rath02 done  bro, Plz review

@ashutosh-rath02 i fix the issue plz check

Hello @Shahbaz898414! Your issue #287 has been closed. Thank you for your contribution!


Provision to configure Envoy access logs

OSM doesn’t have a provision to turn off or configure the format for envoy access logs. The default JSON format is not compatible to be parsed with monitoring agents (like Geneva MDM). Request to provide configuration settings to disable and change the access logs format.
For reference,

Istio has a provision to format the access logs - https://istio.io/latest/docs/tasks/observability/logs/access-log/
Contour changed their default formatting to be a log string instead of JSON fields - https://projectcontour.io/docs/v1.23.0/config/access-logging/

Envoy access logs also cause high Azure Log Analytics data ingestion billing


"'linalg_ext.scatter' op mismatch in shape of update value dim#1 and original value at dim#1" for mhlo.scatter lowering

Repro:
from iree.compiler import compile_str

CODE = """
module  {
  func @main(%arg0: tensor<10x5xcomplex<f32>>, %arg1: tensor<3x1xi32>, %arg2: tensor<3x3xcomplex<f32>>) -> tensor<10x5xcomplex<f32>> {
    %0 = "mhlo.scatter"(%arg0, %arg1, %arg2) ( {
    ^bb0(%arg3: tensor<complex<f32>>, %arg4: tensor<complex<f32>>):  // no predecessors
      %1 = mhlo.add %arg3, %arg4 : tensor<complex<f32>>
      "mhlo.return"(%1) : (tensor<complex<f32>>) -> ()
    }) {indices_are_sorted = false, scatter_dimension_numbers = #mhlo.scatter<update_window_dims = [1], inserted_window_dims = [0], scatter_dims_to_operand_dims = [0], index_vector_dim = 1>, unique_indices = false} : (tensor<10x5xcomplex<f32>>, tensor<3x1xi32>, tensor<3x3xcomplex<f32>>) -> tensor<10x5xcomplex<f32>>
    return %0 : tensor<10x5xcomplex<f32>>
  }
}
"""

compiled_flatbuffer = compile_str(CODE, target_backends=["dylib"], input_type="mhlo")

Get:
$ python t.py
Traceback (most recent call last):
  File "t.py", line 16, in <module>
    compiled_flatbuffer = compile_str(CODE, target_backends=["dylib"], input_type="mhlo")
  File "/usr/local/google/home/phawkins/.pyenv/versions/py373a/lib/python3.7/site-packages/iree/compiler/tools/core.py", line 262, in compile_str
    result = invoke_immediate(cl, immediate_input=input_bytes)
  File "/usr/local/google/home/phawkins/.pyenv/versions/py373a/lib/python3.7/site-packages/iree/compiler/tools/binaries.py", line 201, in invoke_immediate
    raise CompilerToolError(process)
iree.compiler.tools.binaries.CompilerToolError: Error invoking IREE compiler tool ireec
Diagnostics:
<stdin>:4:10: error: 'linalg_ext.scatter' op mismatch in shape of update value dim#1 and original value at dim#1
    %0 = "mhlo.scatter"(%arg0, %arg1, %arg2) ( {
         ^
<stdin>:3:3: note: called from
  func @main(%arg0: tensor<10x5xcomplex<f32>>, %arg1: tensor<3x1xi32>, %arg2: tensor<3x3xcomplex<f32>>) -> tensor<10x5xcomplex<f32>> {
  ^
<stdin>:2:1: error: conversion from source -> vm failed
module  {
^

Invoked with:
 ireec /usr/local/google/home/phawkins/.pyenv/versions/py373a/lib/python3.7/site-packages/iree/compiler/tools/../_mlir_libs/ireec - --iree-input-type=mhlo --iree-vm-bytecode-module-output-format=flatbuffer-binary --iree-hal-target-backends=dylib --iree-mlir-to-vm-bytecode-module --iree-llvm-embedded-linker-path=/usr/local/google/home/phawkins/.pyenv/versions/py373a/lib/python3.7/site-packages/iree/compiler/tools/../_mlir_libs/iree-lld --mlir-print-debuginfo --mlir-print-op-on-diagnostic=false

I feel that we did not consider what happens in complex types in scatter. Also, I think IREE does not support complex inputs and outputs at this moment.
Does compile_str do any preprocessing before passing to iree-translate? If not, I think it won't be supported in the short-term. Because passing/returning complex types is not defined yet.

@hanhanW you are correct that we do not support complex types on function boundaries yet. I'll add that to the weird type support.
How we have supported complex types in the past is decomposing to real and imaginary tensors, then performing the correct decomposed operations on these matrices. This fails on function boundaries as we would no longer match matrix boundaries. To support scatter on complex types we would need to include a decomposition to the normal mhlo scatter (not difficult, just work that would be needed).
Before adding support for this it would make sense to ask whether we should support complex types as a special buffer type or whether the decomposed solution is the best going forward.

Before adding support for this it would make sense to ask whether we should support complex types as a special buffer type or whether the decomposed solution is the best going forward.

Good q - we should probably switch to interleaving like numpy at the frontend and then swap the type. So, tensor<50xcomplex<f32>> is really tensor<50x2xf32> in memory. Getting the imaginary or real portions is just an affine map. Nothing about linalg or below should care (beyond implicitly in maps and such) - it'd be a really strong smell if it does.
numpy uses the interleaved format (x2 innermost dimension, effectively) - we can take that stance at the ABI boundary (any complex type gets an innermost dimension of 2 inserted into the type) or allow the user to pass in two tensors and interleave them themselves (as it's just math, and a user setting up the maps on the linalg ops can achieve all the same stuff).
Helpful in understanding the data layout in numpy:
>>> a = np.arange(100, dtype=np.float32)
>>> a
array([ 0.,  1.,  2.,  3.,  4.,  5.,  6.,  7.,  8.,  9., 10., 11., 12.,
       13., 14., 15., 16., 17., 18., 19., 20., 21., 22., 23., 24., 25.,
       26., 27., 28., 29., 30., 31., 32., 33., 34., 35., 36., 37., 38.,
       39., 40., 41., 42., 43., 44., 45., 46., 47., 48., 49., 50., 51.,
       52., 53., 54., 55., 56., 57., 58., 59., 60., 61., 62., 63., 64.,
       65., 66., 67., 68., 69., 70., 71., 72., 73., 74., 75., 76., 77.,
       78., 79., 80., 81., 82., 83., 84., 85., 86., 87., 88., 89., 90.,
       91., 92., 93., 94., 95., 96., 97., 98., 99.], dtype=float32)
>>> a.shape
(100,)
>>> b = a.view(np.csingle)
>>> b.shape
(50,)
>>> b
array([ 0. +1.j,  2. +3.j,  4. +5.j,  6. +7.j,  8. +9.j, 10.+11.j,
       12.+13.j, 14.+15.j, 16.+17.j, 18.+19.j, 20.+21.j, 22.+23.j,
       24.+25.j, 26.+27.j, 28.+29.j, 30.+31.j, 32.+33.j, 34.+35.j,
       36.+37.j, 38.+39.j, 40.+41.j, 42.+43.j, 44.+45.j, 46.+47.j,
       48.+49.j, 50.+51.j, 52.+53.j, 54.+55.j, 56.+57.j, 58.+59.j,
       60.+61.j, 62.+63.j, 64.+65.j, 66.+67.j, 68.+69.j, 70.+71.j,
       72.+73.j, 74.+75.j, 76.+77.j, 78.+79.j, 80.+81.j, 82.+83.j,
       84.+85.j, 86.+87.j, 88.+89.j, 90.+91.j, 92.+93.j, 94.+95.j,
       96.+97.j, 98.+99.j], dtype=complex64)
>>>

We can preserve the complex type information for the runtime for reflection (add a IREE_HAL_ELEMENT_TYPE_COMPLEX_32 and such) and hide the innermost x2 dimension if we wanted, but the sooner we get rid of that in the pipeline and let linalg work its magic the better. We should strive to never ever end up with what TF & co deal with (where they invoke standalone kernels to touch all memory twice to deinterleave each set of values 🤮) - and need to make sure we aren't handicapping linalg by not letting it slice and dice the data. If we went all interleaved we could even leave the complex types in there and just have bitcasts between the complex and x2 form at the boundaries we care about, but removing it entirely seems more robust (otherwise every layer of the system has to be taught that complex == x2xf32, and that feels hacky).
I suspect switching to this interleaved format will be much easier than what we are doing - just normal type conversion instead of expansion - so that'd be a win. I'd say mhlo->linalg is when it should happen (and tosa->linalg would do the same there, etc).

with https://github.com/google/iree/pull/7798 we can now represent encoding types on the ABI independent of the storage types, so doing the complex -> 2xf32 is now pretty easy (same mechanism used for signed -> signless).

Local reproducer here
// configuration: -pass-pipeline='func.func(iree-mhlo-to-linalg-ext)' -mlir-disable-threading -verify-each
#loc0 = loc(unknown)
module @jit_prim_fun.0 {
  func.func public @main(%arg0: tensor<10x5xf32> loc(unknown), %arg1: tensor<3x1xi32> loc(unknown), %arg2: tensor<3x3xf32> loc(unknown)) -> tensor<10x5xf32> {
    %0 = "mhlo.scatter"(%arg0, %arg1, %arg2) ({
    ^bb0(%arg3: tensor<f32> loc(unknown), %arg4: tensor<f32> loc(unknown)):
      %1 = mhlo.add %arg3, %arg4 : tensor<f32> loc(#loc2)
      "mhlo.return"(%1) : (tensor<f32>) -> () loc(#loc1)
    }) {indices_are_sorted = false, scatter_dimension_numbers = #mhlo.scatter<update_window_dims = [1], inserted_window_dims = [0], scatter_dims_to_operand_dims = [0], index_vector_dim = 1>, unique_indices = false} : (tensor<10x5xf32>, tensor<3x1xi32>, tensor<3x3xf32>) -> tensor<10x5xf32> loc(#loc1)
    return %0 : tensor<10x5xf32> loc(#loc0)
  } loc(#loc0)
} loc(#loc0)
#loc1 = loc("jit(scatter-add)/jit(main)/scatter-add[update_consts=() dimension_numbers=ScatterDimensionNumbers(update_window_dims=(1,), inserted_window_dims=(0,), scatter_dims_to_operand_dims=(0,)) indices_are_sorted=False unique_indices=False mode=GatherScatterMode.FILL_OR_DROP]"("/Users/phawkins/p/jax/tests/lax_test.py":2304:1))
#loc2 = loc("/add"("/Users/phawkins/p/jax/tests/lax_test.py":2304:1))

Leaving open until we completely verify the landed patch fixes the issue.

With patches for operand permutations and fixed decomposition I am seeing a fusion failure further in the pipeline.


Binary data handling should be better

There should be something like base64 support for keys and values.

Even ldb db get inserts extra \x20 and \x0A, making extracting CBOR fragments more annoying.


bug: webpack import error after upgrade to v4.0.3 (from 3.9.4)

What version of daisyUI are you using?
4.0.3
Which browsers are you seeing the problem on?
All browsers
Reproduction URL

Describe your issue
Hi,
So i updated the library to the latest version, and its now failing to build. I get this:
🌼   daisyUI 4.0.3
  ⨯ ./src/styles/globals.scss.webpack[javascript/auto]!=!../node_modules/.pnpm/next@14.0.2_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0_sass@1.69.5/node_modules/next/dist/build/webpack/loaders/css-loader/src/index.js??ruleSet[1].rules[12].oneOf[13].use[2]!../node_modules/.pnpm/next@14.0.2_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0_sass@1.69.5/node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[12].oneOf[13].use[3]!../node_modules/.pnpm/next@14.0.2_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0_sass@1.69.5/node_modules/next/dist/build/webpack/loaders/resolve-url-loader/index.js??ruleSet[1].rules[12].oneOf[13].use[4]!../node_modules/.pnpm/next@14.0.2_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0_sass@1.69.5/node_modules/next/dist/compiled/sass-loader/cjs.js??ruleSet[1].rules[12].oneOf[13].use[5]!./src/styles/globals.scss
 TypeError: Cannot read properties of undefined (reading 'l')
     at Array.map (<anonymous>)
     at Array.reduce (<anonymous>)
     at Array.forEach (<anonymous>)
     at Array.forEach (<anonymous>)
     at Array.forEach (<anonymous>)
 Import trace for requested module:
 ./src/styles/globals.scss.webpack[javascript/auto]!=!../node_modules/.pnpm/next@14.0.2_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0_sass@1.69.5/node_modules/next/dist/build/webpack/loaders/css-loader/src/index.js??ruleSet[1].rules[12].oneOf[13].use[2]!../node_modules/.pnpm/next@14.0.2_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0_sass@1.69.5/node_modules/next/dist/build/webpack/loaders/postcss-loader/src/index.js??ruleSet[1].rules[12].oneOf[13].use[3]!../node_modules/.pnpm/next@14.0.2_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0_sass@1.69.5/node_modules/next/dist/build/webpack/loaders/resolve-url-loader/index.js??ruleSet[1].rules[12].oneOf[13].use[4]!../node_modules/.pnpm/next@14.0.2_@babel+core@7.23.3_react-dom@18.2.0_react@18.2.0_sass@1.69.5/node_modules/next/dist/compiled/sass-loader/cjs.js??ruleSet[1].rules[12].oneOf[13].use[5]!./src/styles/globals.scss
 ./src/styles/globals.scss

Getting the same error, just started with 4.0.3

Can you update to version 4.0.4 and try again?
And please provide a reproduction repo, otherwise it's hard to guess what is causing the issue.

Can you update to version 4.0.4 and try again?

Nope - still the same issue.

And please provide a reproduction repo, otherwise it's hard to guess what is causing the issue.

The issue is simply nextjs 14 + daisyui 4. I would recommend adding an e2e test in github actions that ensures next versions can build.

Can you update to version 4.0.4 and try again?

Nope - still the same issue.

And please provide a reproduction repo, otherwise it's hard to guess what is causing the issue.

The issue is simply nextjs 14 + daisyui 4. I would recommend adding an e2e test in github actions that ensures next versions can build.

Same

Same here

Same here

haha same issue but I was using version 4.0.5 and Next.js 13.5 so it's not specific to next.js 14

6 people with same issue and no one shares a reproduction repo…
Here's an example of a fresh install Next.js 14 + daisyUI 4:
https://github.com/saadeghi/nextjs14-daisyui4 (look at tailwind config)
We can't update the StackBlitz example to Next.js 14 yet because Next.js 14 doesn't work in StackBlitz.
Let me know if you have any questions.

I have this problem here, but I haven't solved it. If possible, please help to check it out, thanks.
https://github.com/Truimo/home/tree/renovate/daisyui-4.x

TL;DR instead of [data-theme=light] just pass in the string value of the theme "light"

Yes. I added this to the v4 breaking changes yesterday (it was missing) and the docs are updated.

My config:
import daisyuiTheme from 'daisyui/src/theming/themes'

...
light: {
      ...daisyuiTheme?.light,
      primary: lightColors.PRIMARY,
      }
...

@saadeghi By the way, very good update, I love working with this library with astro.


chore(main): release 0.20.0

:robot: I have created a release beep boop
0.20.0 (2024-03-18)
Features

added edge_security_policy to nb-psc-l7xlb (235661f)
adding target server to sb-psc-attachment module (fd88f0a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/apigee/terraform-modules/releases/tag/v0.20.0 :sunflower:


Fix errors in how compute resources are handled

/cc @vishh

👍

It would be helpful to also add a little bit of documentation of how resource.Quantity's work - e.g. cpu: "500m" and cpu: "1000m", but does cpu: ".5" or cpu: "1" also work?

I wasn't sure if that was covered elsewhere.  I can add a sample with 1500m
or 1.5 just so folks can know how multiple core requests work.
On Wednesday, May 4, 2016, Sam Ghods<EMAIL_ADDRESS>wrote:

It would be helpful to also add a little bit of documentation of how
resource.Quantity's work - e.g. cpu: "500m" and cpu: "1000m", but does cpu:
".5" or cpu: "1" also work?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/kubernetes.github.io/pull/472#issuecomment-217043486

Yep that would be good enough for this context.

Will poke tomorrow.  Thanks for feedback!
On Wednesday, May 4, 2016, Sam Ghods<EMAIL_ADDRESS>wrote:

Yep that would be good enough for this context.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/kubernetes.github.io/pull/472#issuecomment-217044207

@vishh - i pushed a small tweak per @huggsboson .  I think a follow-on PR can look to re-craft this section entirely, but for now, at least this PR makes it correct.

👍 As is this patch set would have improved things for me tremendously.

xref: https://github.com/kubernetes/kubernetes/issues/27605

LGTM.


Handheld Crew Monitor and Station Map use power

About the PR

Handheld crew monitors and station maps now correctly drain power from their batteries.
It may be better to move this logic to OnBatteryOpenAttempt, but HealthAnalyzerSystem already directly calls TryUseActivatableCharge, so I left it this way for consistency and to avoid double-drawing power.
Tested crew monitor console and wall station map to confirm they are unaffected (TryUseActivatableCharge returns true if missing components)
Closes #15736

Media

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

fix: Handheld crew monitors and station maps now use battery charge

does this actually prevent the UI from opening? it doesnt seem like it would unless you put it in the attempt ev ent

does this actually prevent the UI from opening? it doesnt seem like it would unless you put it in the attempt ev ent

There is the HasCharge() check in OnBatteryOpenAttempt. so dead powercells do prevent it from opening.
The issue is that for PowerCellDraw components with useRate currently need TryUseActivatableCharge explicitly called somewhere in a system to actually use up the charge.
It may be better to put it in the event, but in some cases like HealthAnalyzer you do want to discharge the battery after the DoAfter since otherwise you can just keep the screen open and keep using it.
It may be easier to switch these to use drawRate instead of useRate. Otherwise we have to call this method somewhere in their respective systems.


Automatically move your cards to the right place based on the status and activity of your issues and pull requests.

Automatically move your cards to the right place based on the status and activity of your issues and pull requests.

Originally posted by @AnonaWolf in https://github.com/AnonaWolf/continuous-integration-circle/issues/25#issuecomment-568904574

Closed


[WIP] p2p

I think I might change MediachainNode and DirectoryNode to contain an instance of BaseNode instead of extending it.  Seems a bit cleaner, and takes the plumbing api calls like dialByPeerInfo out of the "public" api of MediachainNode, etc.  And maybe rename BaseNode to LibP2PNode or something.


Adapted UserGuide to remove AB3 mentions.

Note that the prescribed way of writing a list is to use a - instead of *. See this for more details.

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (98b9419) compared to base (6428b37).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #71   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Impacted Files
Coverage Δ

src/main/java/seedu/address/model/UserPrefs.java
80.00% <100.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Test the perf of CSS keyframes

The idea is to maybe have a constrained API in the future that allows compiling to CSS keyframes instead of using rAF + render. cc @sahrens who'll probably find this relevant.
I've decided to stop theorizing about CSS keyframes' perf vs manipulating DOM + setting style properties vs React + render + setting inline style. Latter will most probably be slower but hey, 1. always need real data to talk about perf, 2. if it's really slower, I want to see how much slower and whether it's worth orienting the API toward the former 2. Relevant post: https://css-tricks.com/myth-busting-css-animations-vs-javascript/
I'll try the perf of React render vs CSS keyframes first. The second method of manipulating DOM and setting style is less worth the trouble of testing, because React-Motion's bottleneck is also there anyway.
I'm actually not sure what'd be an accurate way of testing this. @sahrens did you measure the perf gain from using Core Animation instead of render?

It's not so much about microbenchmark a comparing the approaches head-to-head as it is about the macro system.
That said, it would be interesting/valuable to push the limits of pure animations with both systems. A good way to do that is to increase the complexity (e.g. number of elements being animated simultaneously) until you start dropping frames, and compare that maximum complexity between the two approaches.

On Jul 10, 2015, at 10:36 AM, Cheng Lou<EMAIL_ADDRESS>wrote:
cc @sahrens who'll probably find this relevant.
I've decided to stop theorizing about CSS keyframes' perf vs manipulating DOM + setting style properties vs React + render + setting inline style. Latter will most probably be slower but hey, 1. always need real data to talk about perf, 2. if it's really slower, I want to see how much slower and whether it's worth orienting the API toward the former 2. Relevant post: https://css-tricks.com/myth-busting-css-animations-vs-javascript/
I'll try the perf of React render vs CSS keyframes first. The second method of manipulating DOM and setting style is less worth the trouble of testing, because React-Motion's bottleneck is also there anyway.
I'm actually not sure what'd be an accurate way of testing this. @sahrens did you measure the perf gain from using Core Animation instead of render?
—
Reply to this email directly or view it on GitHub.

:+1: Closing for now =).

If you're relying on react render to animate (say, a custom spinner) and want to also do something expensive in JS (say, render a large network response), then your animation is going to stop while that's happening

I've definitely run into this with my react-motion implementations (not ragging on react-motion at all though, it's amazing!)
@chenglou I might have some time coming up to play around with this CSS keyframe as a way to prevent the blocking of animation frames. Any advice on how to get started?


Improve mysql performance for DNS config generatiob

Today on every DNS config generation for (n) containers that can resolve each other, the result set is n^2 as we try build all the resolutions in the mysql query. Should be reworked the following way. Do just 2 query:
query 1 - to get all containers in the system.
query 2 - to get all services' dependencies (service1>service2 and link name should be returned in the result)
then based on 2 queries' results, form the DNS resolutions in the java code.

https://github.com/rancher/cattle/pull/1121

@sangeethah to validate this bug, we do need to create a big stack having many services each having many containers (100 services, 10 containers each would be a good start). Also have some activity going on - services restarting, scaling up. It shouldn't choke on mysql


Fixing - IDENTITY-3156

Fixing - IDENTITY-3156
Added the "GrantType" column to the IDN_OAUTH2_ACCESS_TOKEN.
https://wso2.org/jira/browse/IDENTITY-3156

Length 25 for GrantType column may not be enough. Shall we increase it to 50

Change the Database column size of the GrantType to 50.


Hello World | 雨宙的个人博客

https://rainyuniverse.github.io/2020/09/06/hello-world/#more
Welcome to Hexo! This is your very first post. Check documentation for more info. If you get any problems when using Hexo, you can find the answer in troubleshooting or you can ask me on GitHub.

测试

哈哈哈

@sophia-whale
哈哈哈

哈哈哈


Remove dynamic framework count from diagnostics.

This was previously used to help determine if Firebase should switch to
using dynamic frameworks, but now developers have the option themselves.
Fixes #7310

Please add a FirebaseCore changelog that references the issue.

Please add a FirebaseCore changelog that references the issue.


Add support for DISTINCT (#444)

This PR adds partial support for SELECT DISTINCT queries. There are two scenarios not covered currently.

SELECT DISTINCT * was not implemented due to an assert on the hash_executor, but it is a simple fix.
DISTINCT aggregations go through another flow, I suggest opening another issue for it.

EDIT: This PR now supports SELECT DISTINCT * queries.

Coverage decreased (-0.1%) to 65.694% when pulling c6e751f6f119c07e2ff312d14d89f9ffb8a28cc2 on PauloAmora:Bugfix_444 into 931d6b9040963ca72b350f173eadd8b0c7d0792b on cmu-db:master.

Coverage decreased (-0.2%) to 65.688% when pulling c6e751f6f119c07e2ff312d14d89f9ffb8a28cc2 on PauloAmora:Bugfix_444 into 931d6b9040963ca72b350f173eadd8b0c7d0792b on cmu-db:master.

Coverage decreased (-0.1%) to 65.704% when pulling d02028f3bde02ea48a597488dbd9bca0e9dd29af on PauloAmora:Bugfix_444 into 931d6b9040963ca72b350f173eadd8b0c7d0792b on cmu-db:master.

All done as requested in the review.

Thanks, @PauloAmora! I'll merge after the tests pass.

Coverage increased (+0.03%) to 65.876% when pulling cacac07ad8f9fa0be7da76999740a9bea8acbff6 on PauloAmora:Bugfix_444 into 931d6b9040963ca72b350f173eadd8b0c7d0792b on cmu-db:master.

Coverage decreased (-0.1%) to 65.704% when pulling cacac07ad8f9fa0be7da76999740a9bea8acbff6 on PauloAmora:Bugfix_444 into 931d6b9040963ca72b350f173eadd8b0c7d0792b on cmu-db:master.


feature:  CBOR sequences

Is your feature request related to a problem? Please describe.
I would like to append multiple CBOR messages to a file
Describe the solution you'd like
Ideally I would like CBOR sequences, or a practical way to decode multiple messages to a file.
Describe alternatives you've considered
At the moment I'm using NDJSON, but it's a pain
Additional context
Spec

Looks like you can do this by creating an encoder using NewEncoder(w) with io.Writer.  Same with decoder created by  NewDecoder(r) with io.Reader.
Easiest way is to use package level encoder := cbor.NewEncoder(w) if default options are acceptable.
encoder := cbor.NewEncoder(w)
err := encoder.Encode(v)

If you need custom options, you can create  EncMode and DecMode at startup and reuse them.
opts := cbor.CoreDetEncOptions()  // Use modern options.  You can customize the returned opts.
em, err := opts.EncMode()         // This creates reusable encoding mode (safe for concurrency).
encoder := em.NewEncoder(w)       // Create encoder with io.Writer.
err := encoder.Encode(msg1)       // Use encoder to send data to underlying io.Writer.
err := encoder.Encode(msg2)       // Use encoder to send data to underlying io.Writer.

For security, you can use io.LimitReader to limit size when decoding very large or indefinite size data.
There's more info and examples at https://github.com/fxamacker/cbor/#quick-start

Ok thank you very much, I made it work both with reader and marshall:
package main

import (
	"bytes"
	"github.com/fxamacker/cbor/v2"
	"log"
)

func main() {

	type Record struct {
		Payload string
		Counter int
	}

	r1 := Record{
		"hello", 1}
	r2 := Record{
		" world", 2}

	var buff []byte

	b, err := cbor.Marshal(r1)
	if err != nil {
		log.Fatal(err)
	}
	buff = append(buff, b...)

	b, err = cbor.Marshal(r2)
	if err != nil {
		log.Fatal(err)
	}
	buff = append(buff, b...)

	log.Println(buff)

	var out1, out2 Record
	decoder := cbor.NewDecoder(bytes.NewReader(buff))

	err = decoder.Decode(&out1)
	if err != nil {
		log.Fatal(err)
	}
	log.Println(out1)

	err = decoder.Decode(&out2)
	if err != nil {
		log.Fatal(err)
	}
	log.Println(out2)

}

One last use case covered by NDJSON and CBOR sequences, which is stream parsing: let's say I have 5 messages in my file, and I want to read the 4th without parsing the first 3, is it possible with this approach?
Should I maybe build a custom decoder, read only the length at the beginning, and then skip to the next position in the buffer? Does CBOR prepend the length of the full message?

CBOR doesn't define "full message".  If you meant "data item" as defined in CBOR RFC 8949, then some data items like CBOR Array will have number of elements (but not size of entire array in bytes).
@fxamacker what do you think of adding a Skip feature to Decoder that allows skipping next data item?

feature: CBOR sequences

At a glance, CBOR Sequence (RFC 8742) is just a concatenation of zero or more encoded CBOR data items, without markers in between nor at the end.  CBOR data items are defined in Section 1.2 of RFC 8949.

Should I maybe build a custom decoder, read only the length at the beginning, and then skip to the next position in the buffer? Does CBOR prepend the length of the full message?

If by "full message" you meant CBOR "data item" as defined in RFC 8949, then I can add a Skip feature to the decoder.
CBOR doesn't prepend length (size in bytes) of data item.

One last use case covered by NDJSON and CBOR sequences, which is stream parsing: let's say I have 5 messages in my file, and I want to read the 4th without parsing the first 3, is it possible with this approach?

It sounds like you want to "skip" the first 3 messages and then parse the 4th message.  Skip isn't currently supported by Decoder.  Until I add a Skip feature, a less efficient way is to decode the messages you want to skip to cbor.RawMessage.  cbor.RawMessage copies data item into a byte slice without parsing the data item.
var throwAway cbor.RawMessage
err := decodoer.Decode(&throwAway)

One more thing, I noticed cbor.Marshal is used in your code snippet.  For CBOR sequence, cbor.Encoder is more efficient and easier to use.

@espoal @fxamacker
I think this issue can be closed because the original request is already supported by this CBOR codec.   The Skip() feature request is in the newly opened issue #366.

@x448 @fxamacker I actually meant to skip a message (data item?) in a sequence. I thought it was covered by this part of the spec. Will Skip() allow me to skip a message in a sequence?


fix: optional subscriptions

use subscriptions optionally

This has a lot of unrelated changes - .gitignore, style changes, and file renames. It makes the relevant changes more difficult to review.

I'll split in many PRs


NetworkSecurityGroup#networkInterfaceIds

to do
Need to figure out a general approach for returning lists of associated resources

we'll just do NetworkSecurityGroup#networkInterfaceIds() for now

done


Support Python3.7

http://docs.gunicorn.org/en/stable/news.html#id1
It fixed on gunicorn >= 19.9.0. (Currently we're using 19.7.1)

And it fixed on gevent == 1.3.5. (Currently we're using 1.3.1)

https://github.com/ofek/coincurve/issues/19
Maybe coincurve isn't support python 3.7 now.

When we command $ nekoyume init
we got errors below
...
ImportError: dlopen(/Users/enesse/Dropbox/Develop/nekoyume/.env/lib/python3.7/site-packages/coincurve/_libsecp256k1.cpython-37m-darwin.so, 2): Library not loaded: /usr/local/opt/gmp/lib/libgmp.10.dylib
  Referenced from: /Users/enesse/Dropbox/Develop/nekoyume/.env/lib/python3.7/site-packages/coincurve/_libsecp256k1.cpython-37m-darwin.so
  Reason: image not found

Ok, it seems that we are not supporting python 3.7 right now.

This issue seems to be resolved. cc @jckdotim @nekoyume-ops


Generate key path fix

This fix just always expands the sources passed to load to the full paths for all files.

happy to approve, with the proviso that we continue to work on this, fix the test, refactor the code, etc.
:+1:


More general unit test for Lorentz vector array concatenation

Hi, I have to change something about the unit test for concatenation to reveal an issue.
Unfortunately, the concatenation didn't work after all for TLorentzVectorArrays and the like. It took me some time to understand what happened. When the vector array is created with from_ptetaphim, this mixin here dynamically creates a new class. Since the class is different for every call of from_ptetaphim, this check will fail even if the classes are for all intents and purposes the same.
My unit test concatenated arrays which themselves, which is the only case where the classes are actually the same and it will work :) I suggest to change that in this PR, and I will also open one in uproot-methods, suggesting a fix.

This unit test should have failed and can be fixed by https://github.com/scikit-hep/uproot-methods/pull/48.

Because of the upstream deployment of scikit-hep/uproot-methods#48, the tests are now successful. I'm going to deploy this, too, as 0.8.15.

Thank you for reacting so promptly!

Is it possible to use the mock Mixin that I defined in https://github.com/scikit-hep/awkward-array/blob/master/tests/test_methods.py rather than a dependency on uproot-methods (a mostly  upstream repo?)

The hazards of commenting on closed PRs.. @guitargeek @jpivarski I just was pointing out that the mock mixin I wrote some time ago can probably be used as a unit test for concatenating dynamically generated classes with common mixins.  But maybe awkward-array is already interlinked with uproot-methods for other reasons, in which case it is not so big a deal.  (although I'm pretty sure I wrote the mock mixin on request to prevent such a situation)

uproot-methods depends on more from awkward than only the Methods class. In particular, it does a lot with JaggedArrays and all of the vector arrays are ObjectArrays.


Children/parent not filled in during preprocessing

Items generated during the preprocess phase will not have proper children/parent relationships.

Marking this as won’t-fix. The effort for this is high and the gain is quite low.
So, the child-parent relationship will not remain up-to-date while modifying items (or layouts) inside the preprocess block, but it will be brought up-to-date after the preprocess step has finished.


Add and Update Javadocs

Codecov Report

Merging #344 (ea2dbd6) into master (8afe91f) will decrease coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #344      +/-   ##
============================================
- Coverage     70.80%   70.75%   -0.06%
+ Complexity      914      913       -1
============================================
  Files           111      111
  Lines          3648     3648
  Branches        352      352
============================================
- Hits           2583     2581       -2
- Misses          968      969       +1
- Partials         97       98       +1

Impacted Files
Coverage Δ

...c/main/java/seedu/address/commons/core/Config.java
95.45% <ø> (ø)

...n/java/seedu/address/commons/core/GuiSettings.java
92.30% <ø> (ø)

...in/java/seedu/address/commons/core/LogsCenter.java
86.48% <ø> (ø)

.../main/java/seedu/address/commons/core/Version.java
97.50% <ø> (ø)

...n/java/seedu/address/commons/core/index/Index.java
100.00% <ø> (ø)

...ss/commons/exceptions/DataConversionException.java
100.00% <ø> (ø)

.../main/java/seedu/address/commons/util/AppUtil.java
88.88% <ø> (ø)

...ava/seedu/address/commons/util/CollectionUtil.java
87.50% <ø> (ø)

...in/java/seedu/address/commons/util/ConfigUtil.java
75.00% <ø> (ø)

.../main/java/seedu/address/commons/util/CsvUtil.java
94.44% <ø> (ø)

... and 37 more

Continue to review full report at Codecov.

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


Set keystore file type as required due to upstream changes the type can't be inferred anymore

Summary
Sets keystore file type as tests are now failing. See https://github.com/quarkusio/quarkus/pull/39106 and https://github.com/quarkusio/quarkus/issues/39151 for explanation what changed and why it is okay.
Please check the relevant options

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Dependency update
[ ] Refactoring
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] This change requires a documentation update
[x] This change requires execution against OCP (use run tests phrase in comment)

Checklist:

[x] Example scenarios has been updated / added
[ ] Methods and classes used in PR scenarios are meaningful
[x] Commits are well encapsulated and follow the best practices

run tests

run tests

@michalvavrik There are 2 other failures, they goes from other modules and not related to this PR.

BTW I am adding backport as I either already changed these lines or will change this in PRs that needs to be backported to 1.4.z stream. so I want to avoid conflicts.

Removing the backport label as this is already in 1.4 branch

And I am adding the backport label as it turns out that one of the 1.4.2.Beta8 tags actually held 1.4.3.Beta8 release of framework, and I based the 1.4.z branch on that wrongly...

Removing backport label as this was part of https://github.com/quarkus-qe/quarkus-test-framework/pull/1105


merge rubhurring's fork back into ours

This will primarily stop the circular arg warnings.
https://trello.com/c/NOwOcDvT/357-merge-rubhurring-s-fork-of-address-validator-into-ours

DTM


Upgrade of Panorama

As an engineer we need to ensure our pipelines are being used in the latest format. It has been established that the Panorama needs to be upgraded in the correct source code in Gibhub.
This pipeline is used by the Gateway team and the contact for that team is<EMAIL_ADDRESS>Link ticket with - #365

Reached out to Gateway team to work on this as they are one who uses this pipeline.  They are going to advise if there is a codebase for this and when they are able to test.

test

upgraded the source action to github version 2 to use
Arn
arn:aws:codestar-connections:eu-west-2:683290208331:connection/494d5bc3-587a-4514-ad63-30805d6a494f

Background: These pipelines are created over 2 year ago using this repo which is very much out of date and tightly coupled with other resources which are part of PaloAlto product suites in the same state file. After reviewing the code it looked appropriate not try reusing the same code as there are couple of issues

We do not have the TFVARs that is required to work on the code
Not having background of the other resources on the same state file.
Hardcoded value which are sensitive in nature.

We collectively agreed to proceed with upgrading the GitHub source action to GitHub version 2 using NVVS codestar connection on the AWS console and unblock these pipelines. As it would not add much of a value having the immutability(DR perspective) of the AWS CodePipleines as its a managed regional service offering from AWS.  And future aspiration is to move these pipelines to Github Actions.


mongo db

Does this occur consistently?
Repro steps:

Action: writeFile
Error type: Error
Error Message: Failed to update document with _id '0002'.
Version: 0.15.0
OS: win32
OS Release: 10.0.19042
Product: Visual Studio Code
Product Version: 1.51.0
Language: pt-br

Call Stack
Function.<anonymous> extension.bundle.js:173:164729
fulfilled extension.bundle.js:173:163617
processTicksAndRejections task_queues.js:94:5

Please provide detailed repro steps.


Cannot upload images with Chrome from Linux

Try to upload an image and this error appears in console:
Failed to load resource: the server responded with a status of 404 (Not Found) http://depthy.stamina.pl/styles/vendor.css
compoundFiles 3be9a114.scripts.js:1
2
Cross-origin image load denied by Cross-Origin Resource Sharing policy. depthy.stamina.pl/:1
2
WebGL: INVALID_VALUE: texImage2D: no image depthy.stamina.pl/:1
[.WebGLRenderingContext]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering or is not 'texture complete' depthy.stamina.pl/:1
The rest are other WebGL warnings probably because not texture loaded.

WebGL texture loads require the same kind of cross-origin permissions that normal image loads require. See: https://hacks.mozilla.org/2011/11/using-cors-to-load-webgl-textures-from-cross-domain-images/
Three.js has a feature to handle this: https://stackoverflow.com/questions/24087757/three-js-and-loading-a-cross-domain-image
I haven't googled it but I would guess pixiJS has something similar.


Wrong string encoding/decoding

Hi again,
I think I found a bug:
const char *initialString {"989F2EAE-123B-44E5-B437-7E3BB923A611"};

std::cout << "Initial string is: " << initialString << "\n";

JsValueRef uuid;
JsPointerToStringUtf8(initialString, sizeof(initialString), &uuid);

char *decodedString;
size_t length;
JsStringToPointerUtf8Copy(uuid, &decodedString, &length);

std::cout << "Decoded string is: " << decodedString << ", length is: " << length << "\n";

On my machine, the output is:
Initial string is: 989F2EAE-123B-44E5-B437-7E3BB923A611
Decoded string is: 989F2EAE, length is: 8

Seems it shrinks initial input while converting. I'd like to send a PR, could you be so kind to point me the place where I can fix it (I'm not familiar with ChakraCore yet)?

strlen instead of sizeof would give you the correct length in the JsPointerToStringUtf8.

![image](https://cloud.githubusercontent.com/assets/2273613/18603543/bcbaed46-7c72-11e6-85a3-1861c98b6a36.png)

Indeed, sorry


CTRL + F

This is not an issue, this is a suggestion.  I'm sorry if this is annoying, but I don't see anywhere else to leave suggestions.  I think that it would be really nice when you used CTRL + F to find strings in your code if there was a way to put a cursor at each result.  For instance, I just finished a javascript project, and there were a lot of "console.log()" statements that I had to remove.  It would've been much faster if I could've used CTRL + F to find all the console.log() statements and then put a cursor at each one so that I could delete them simultaneously.

Hi @SamDickey,
there's an option called Find All And Select in the Find menu (on Mac it's shift+command+G, so something like ctrl+shift+f which does what you want: find a console.log, highlight it, press the command and delete with backspace.

Hi @SamDickey,
In addition to the Find menu, there are shortcuts you can use to change the words you find to other words. Ctrl+Shift+H


Replace the Swagger JS CDN source from jsdelivr to unpkg.com

The jsdelivr cdn certificate expired in the mainland, causing the website to hang. To fix it, the solution is to replace the CDN source to unpkg.com

Codecov Report

Merging #1852 (b97cf95) into master (b7295a1) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1852      +/-   ##
==========================================
+ Coverage   73.47%   73.48%   +0.01%
==========================================
  Files         495      495
  Lines       44336    44336
==========================================
+ Hits        32574    32581       +7
+ Misses       9800     9795       -5
+ Partials     1962     1960       -2

Flag
Coverage Δ

go-1.15
?

go-1.17
73.48% <ø> (?)

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

Impacted Files
Coverage Δ

net/ghttp/ghttp_server_swagger.go
75.00% <ø> (ø)

container/gtree/gtree_avltree.go
95.97% <0.00%> (+0.57%)
:arrow_up:

net/ghttp/ghttp_server.go
62.61% <0.00%> (+0.66%)
:arrow_up:

os/gcmd/gcmd_parser.go
92.90% <0.00%> (+0.70%)
:arrow_up:

Continue to review full report at Codecov.

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


Search history

Problem Description

It would be great if it shows search history so I don't have to retype the same thing again
Proposed Solution

Add search history here

or to provide a switch to turn it on/off
Thanks!  ^^

@zulipbot claim

I could work on this after positive feedback

Can I be assigned to this also?

As noted in the contributor guide, please choose an issue with the "help wanted" label. This issue requires product discussion before it's ready to be worked on.


Cent os machines are automatically adding to nagios server with out installing nagios plugin, why its adding automatically???

please give detailed information what you did
and what it display

Do we need to install nagios plugin in linux nodes or not to monitor.

Hi Suman,
Not sure if I understood your question, but I'm writing down the info I have below:
--> From the screenshot above, I can see that the host defined is inheriting values from the template
linux-server, this template has the default check_command value as check-host-alive. chech-
host-alive is the alias to the command check_ping.
define host {
name                              linux-server
use                                  generic-host
check_period                    24x7
check_interval                        5
retry_interval                          1
max_check_attempts              10
check_command                   check-host-alive

--------------------------------------------------  }
For this reason, you can see the hosts appear in the console.

-->Public services like http and ftp ..... don't require agent installation on the nodes/clients
-->But private attributes like memory, cpu and disk usage require agent installation on nodes.
Agents: NCPA on windows and NRPE on linux clients/nodes
And also check_ncpa.py and check_nrpe plugins need to be installed on the nagios core server.
Please see the page for more info:  https://support.nagios.com/kb/article/nrpe-how-to-install-nrpe-v3-from-source-515.html


Txs for different accounts appear in tx history

Overview
When trading to a custom recipient that is a previously connected wallet, BOTH the "sent" and "received" transactions appears in the tx history of BOTH the sender and receiver, even though the sent/received txs are for a totally different wallet. That is, on one tab (the sending wallet) shows BOTH txs, and on another tab (the receiving wallet) shows BOTH txs. Both txs remain in tx history until the cache is cleared.
It appears the processing of txs coming in from the websockets is not discriminating the connected accounts properly.
References and additional details
Sending wallet shows both txs:

Receiving wallet shows both txs:

Refreshing page, still appears. Clearing cache, problem resolved:
https://jam.dev/c/f5a6c645-e75a-494d-a66a-eddc2d4c9167
Acceptance Criteria
Only txs relevant to the connected wallet should appear in tx history.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

Small trace so I can continue tomorrow with full brain cells:
Seems like we call unsubscribe to unchained without any subscriptionId, so when we deconnect the wallet, we are not unsubscribing, and as we use the BIP44, reconnecting to another wallet use the same subscriptionId and so any new TXs are sent to the new wallet


Optimize API objects

Introduce API versioning
Figure out the minimum amount of fields frontend needs for each endpoint
create data module or something similar, which holds the data objects used to communicate with frontend

Meeting Notes 12.11.2024

for all parameters, we use snake_case

Screens based on Figma

Create identity

Mandatory

Legal full name (one field) - (String)
email address - (String)
postal address - (String)

Optional

Birth date (Date)
Country of birth (String)
City of birth (String)
Social Security Number (String)
Profile Picture
Identity document (passport, perso, drivers license) (File)

Create company

Mandatory

Legal company name (String)
Registration date (of the company) (Date)
Country of registration (String)
City of registration (String)
Postal Address (String)
Legal email address (String)
Registration Number (String)
Proof of registration (File)

Optional

Logo

Create contact

Mandatory

Name (String)
Mail (String)
Postal Address (String)
(node_id) (String)

Optional

Date of birth (Date)
Country (String)
City (String)

Issue Bill

Mandatory

type (Promissory note, three parties, draw on payer) (Enum/String/Code)
Country of issuing (String)
City of issuing (String)
issue date (Date)
maturity date (Date)
Payee (Contact (node id String))
Payer (Contact (node id String))
Sum (number)
Currency (enum / 3-letter ISO String)
Invoice (1-n files)
Country of payment (String)
City of payment (String)

Endorse Bill

Mandatory

Endorsee (Contact (node id String))

Mint

Mandatory

Endorsee (Contact (node id String))
Sum (number)
Currency (enum / "CR-" + 3-letter ISO String)

Sell

Mandatory

Endorsee (Contact (node id String))
Sum (number)
Currency (enum / 3-letter ISO String)

Bill Overview

Input parameters

Filter

search term (String)
date range

from (Date)
to (Date)

Role (Enum - All/Payee/Payer/Contingent)
(Currency)

Response

[Light Bill]

Bill Detail

Full Bill (TBD)

latest version of the bill
includes all fields of the bill
includes calculated current state (e.g. current holder) and possible state transitions (e.g. request to pay/accept etc.)

permissions

includes full history (maybe on-demand endpoint)

Home Overview

Input parameters

Currency

Response

Balances

Payee (number calculated by chosen currency)
Payer (number calculated by chosen currency)
Contingent (number calculated by chosen currency)

N Recent Bills

[Light Bill]

Payer (Legal full name of person/company)
Payee (Legal full name of person/company)
Drawer (Legal full name of person/company)
Sum (number calculated by chosen currency)
Issue Date (Date)

Next step - putting it in Postman

are we staying with form-data for payloads, or will we move to JSON?

I think we must switch to JSON. What's your opinion @zupzup ?

are we staying with form-data for payloads, or will we move to JSON?

I think we must switch to JSON. What's your opinion @zupzup ?

Yes, I think it's more consistent to have JSON everywhere, instead of a mix of JSON and form-data and it's not a big code change. :+1:

API moved to JSON and all current API endpoints documented in Postman.
Waiting for the rest of the screens to continue

Next steps:

Another iteration round, adding new endpoints according to Figma
Change postal address to County/City/Address/Zip code


Update Settings “general”

Automatically generated by Netlify CMS

👷 Deploy Preview for koytak processing.

Name
Link

🔨 Latest commit
647fcb338ee03fc5bc5b9a4e21a321e2a8f8d5e2

🔍 Latest deploy log
https://app.netlify.com/sites/koytak/deploys/65164cbd57700600081d90ab


Grouped list docs

Description
Here https://sebgroup.github.io/green/latest/angular/?path=/docs/components-grouped-list--default it is stated that you need to `import '@sebgroup/green-core'
But green-core is not a part of the installation (https://sebgroup.github.io/green/latest/angular/?path=/docs/get-started--page).
as a result we get:
Can't find stylesheet to import.
@import '@sebgroup/green-core';

@sebgroup/green-core is a sub-dependency of @sebgroup/green-angular, so you should be getting it by depending on the Angular package.
@sebgroup/green-core is not a stylesheet though, it is a javascript library. I see now that the example is a bit unclear on that part! It is referring to your xxx.component.ts file for the Angular component where you will use the web component.
Will clarify this in the example!

Ok.. thx..
Next question:
The chlorophyll version has a label/value for each row.. does the angular implementation have that but the docs are missing?
https://sebgroup.github.io/green/latest/chlorophyll/?path=/docs/components-list--page

Yes, you can add the content you need inside each list item. There are more examples in the documentation for the web component: https://sebgroup.github.io/green/latest/core/?path=/docs/components-grouped-list--page

ok.. so the core is where I should look docs on how to use angular components.. got it 😄

You can add a class just fine, you just can affect any children inside Shadow DOM. But in this case there's nothing in Shadow DOM (check dev tools inspector), so it'll be like styling any other element. And your slotted children lives in light DOM, so those you can style freely as well.
You can't use element selectors though. And you shouldn't either way. But if you really need to, you can select on [gds-element='gds-list-item'] to get around the scoping thing. But considers the implications of generic selectors if your app is an MFE and therse are neighboring apps also using Green.

To adress the question of what the recommended way is, we're still trying to figure out the best practices for this. We want to minimize the need for additional styling, because every time someone needs to add custom styling, thats an opportunity for inconsistencies to creep in. But we also need to have enough flexibility to handle all the edge-case that inevitably pops up.
We're leaning towards some som form of utility class based solution, but its still in the exploration phase.


fix: Include directory when parsing context location

via https://github.com/getappmap/appmap-js/pull/1748

I re-ran the integration tests and a different one failed, so it seems like they're suddenly unstable again. Both failing tests had to do with expecting tree providers to have the expected tree items.

I re-ran the integration tests and a different one failed, so it seems like they're suddenly unstable again. Both failing tests had to do with expecting tree providers to have the expected tree items.

FYI tree provider has a known bug - https://github.com/getappmap/vscode-appland/pull/930


Tweak RACK CI workflows

Make it so that tag-only pushes will not trigger either rack-box-continuous.yml or rack-continuous.yaml workflows.  Now creating a new release will trigger only rack-box-release.yml, not all threee workflows.
Make rack-continuous.yaml a little more concise and remove superfluous shell: bash lines.
Streamline CI workflows and reduce duplication of lines by eliminating some caches that probably weren't saving us much time anyway.  The workflows were getting a little too long.  Also change our Docker Hub repository from interran/rack-box to gehighassurance/rack-box now that RACK is public.
In rack-box-continuous.yml and rack-box-release.yml, stop caching rack-cli.tar.gz, rack.tar.gz, documentation.html, index.html, style.css, and systemctl3.py.  Eliminate rack-box-release.yml's setup job (which was used only to populate some caches) and do all the work in its build job which will make it easier to compare rack-box-continuous.yml and rack-box-release.yml and keep both synchronized with each other.
In rack-continuous.yaml, tweak steps and comments slightly for better readability.

I'm in meetings all day, but I can review by 5pm PST.


Add Zandalar quests

Old Zandalar quests have been added in 4db2b7d8565c232ff74fabdb4f42120518b48079
They now need to be adjusted to fit the current state of the map