added uint8array as input and output option

maybe dirty, but also simple and does the job (AFAIK)
should "fix" parts of #1315, discussion also in #1289

Coverage remained the same at 100.0% when pulling d1359886318c64c4ebcf187729a093f711afb435 on howtcode:master into 0f58f956a7892ff480549fa99d76627892bd9fc1 on lovell:master.

dunno why those checks are failing, did i do something wrong?

oof, my approach actually doesn't work at all, because toBuffer can accept and return so different things...
I pretty much have to rewrite the _pipeline function from output.js to make this work.

Closing in favour of #2511, thank you for taking the time to submit this PR.

Closing in favour of #2511, thank you for taking the time to submit this PR.


Update to data 3.0.0

See https://github.com/Senzing/docker-compose-demo/issues/253

Pull requests

https://github.com/Senzing/template-python/pull/50


run the exposecontroller to automatically create routes and ingress rules fixes fabric8io/fabric8#6252

[merge]


Replace

This is a WIP for replace. Feedback is welcome. This PR depends on https://github.com/google/xi-editor/pull/711. This is an implementation of the protocol discussed in https://github.com/google/xi-editor/issues/712
Tasks

[x] Find all
[x] Replace next
[x] Replace all
[x] Set replace in core
[x] Replace status
(Preserve case (possible future work))

Currently, the preserve_case option is ignored. But since it is quite tricky to implement, I think it is a feature that could be added in the future.

@scholtzan This has a small conflict, then we can get it in

@cmyr Conflicts should be resolved now


privacy policy

issue #1208
Description
Added a "Privacy Policy" page, styled to match the existing website theme.
Linked the page in the footer for easy navigation.
Ensures users can access privacy details directly.
Type of PR

[ ] Bug fix
[X] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
https://github.com/user-attachments/assets/7d7e9815-cbe3-4929-82aa-24e8c909cbac

[X] I have made this change from my own.
[X] I have taken help from some online resources.
[X] My code follows the style guidelines of this project.
[X] I have performed a self-review of my own code.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] I have made corresponding changes to the documentation.
[X] My changes generate no new warnings.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers and screenshots after making the changes.

@Subham1 Please see the conflicts highlighted in the image above. Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch.

@Subham1
Please see the conflicts . Resolve the conflicts . Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


Amplify containers hosting only deploys with node version.

When I was using the curl installed version of the Amplify CLI, I got this warning when running amplify push after adding container hosting using amplify add hosting:
Method generateHostingResources does not exist or not a function in category plugin: hosting.
An error occurred during the push operation: Method generateHostingResources does not exist or not a function in category plugin: hosting.

When I uninstalled the curl version of the CLI and installed the node version, deploying then worked.
The version I was on is 4.41.1

@dabit3 I tried above solution but still the issue is not resolved,
I am using the amplify version 4.41.2


Semaphore package leaks handles, prevents node from exiting

Describe the bug
My Mocha unit tests hang unless I specify --exit to kill the test process after each suite.
It looks like this may be because Semaphore leaks some resources.
To Reproduce
Write any test or script that verifies a Semaphore proof.
Expected behavior
Should show exactly two handles, corresponding to stdin/stdout.
Technologies (please complete the following information):

Node.js version 20
NPM version 9.6.4
Solidity version N/A

Using @semaphore-protocol/{group,identity,proof} version 3.2.3

https://github.com/semaphore-protocol/semaphore/issues/736#issuecomment-2027490466
This issue is related to snarkjs, but Semaphore could provide a function to "terminate" it.

is it solved or not?

Hi @Chirag-S-Kotian, we are actually going to close this issue.  Devs can use ffjavascript to get the curve and terminate it -> https://github.com/semaphore-protocol/semaphore/blob/3ed6c38587b58851d4b8ec138a9979f7f716a885/packages/proof/tests/index.test.ts#L18. We'll add documentation to explain how to solve this issue.


How to access container stdin/stdout/stderr directly?

I am wanting to capture the raw stdout from my container, which currently appears with timestamp and container prefixes.  I presume this is because stdout is in log mode, and I need to set it into stream mode, by using the per-application options.
However, I can't work out where to pass these on the rkt command line.  Here is my attempt (scroll all the way to the right past some uninteresting volume mounts, etc):
inscrutable$ sudo /usr/bin/rkt --insecure-options=image run --set-env=HOME=/home/guestsi --volume home,kind=host,source=/home/guestsi --volume dataset,kind=host,source=/dataset --volume bifo,kind=host,source=/bifo --volume volume-config,kind=empty,uid=511,gid=511 --volume volume-data,kind=empty,uid=511,gid=511 docker://biocontainers/samtools --mount volume=home,target=/home/guestsi --mount volume=dataset,target=/dataset --mount volume=bifo,target=/bifo --user=511 --group=511 --stdout=stream -- flagstat /home/guestsi/playpen/sam/small.bam
[sudo] password for guestsi:
run: error parsing app image arguments: unknown flag: --stdout

I tried with --stdout in various other places, and got other errors.
What am I misunderstanding here?

The documentation is remiss for not mentioning that those are experimental features gated behind the RKT_EXPERIMENT_ATTACH=true environment variable being set.
Assuming setting that environment variable is what's missing, this can be a documentation issue.

OK, thanks, that helped a bit.  But now I find that --stdout=stream doesn't actually produce any output at all.
Here it is with log mode (sorry for all the command line flags, which are necessary to get my container to run without warnings):
inscrutable# RKT_EXPERIMENT_ATTACH=true /usr/bin/rkt --insecure-options=image run --volume volume-config,kind=empty,uid=511,gid=511 --volume volume-data,kind=empty,uid=511,gid=511 --volume home,kind=host,source=/home/guestsi docker://biocontainers/samtools --mount volume=home,target=/home/guestsi --user=511 --group=511 --stdout=log -- flagstat /home/guestsi/playpen/sam/small.bam
[ 3384.583849] samtools[5]: 200 + 0 in total (QC-passed reads + QC-failed reads)
[ 3384.584845] samtools[5]: 0 + 0 secondary
[ 3384.585727] samtools[5]: 0 + 0 supplementary
[ 3384.586236] samtools[5]: 0 + 0 duplicates
[ 3384.586697] samtools[5]: 96 + 0 mapped (48.00% : N/A)
[ 3384.587133] samtools[5]: 200 + 0 paired in sequencing
[ 3384.587584] samtools[5]: 100 + 0 read1
[ 3384.588018] samtools[5]: 100 + 0 read2
[ 3384.588989] samtools[5]: 26 + 0 properly paired (13.00% : N/A)
[ 3384.589594] samtools[5]: 52 + 0 with itself and mate mapped
[ 3384.589998] samtools[5]: 44 + 0 singletons (22.00% : N/A)
[ 3384.590194] samtools[5]: 24 + 0 with mate mapped to a different chr
[ 3384.590354] samtools[5]: 10 + 0 with mate mapped to a different chr (mapQ>=5)
inscrutable#

I'm wanting to capture raw stdout on the host, but with --stdout=stream, I get nothing at all:
inscrutable# RKT_EXPERIMENT_ATTACH=true /usr/bin/rkt --insecure-options=image run --volume volume-config,kind=empty,uid=511,gid=511 --volume volume-data,kind=empty,uid=511,gid=511 --volume home,kind=host,source=/home/guestsi docker://biocontainers/samtools --mount volume=home,target=/home/guestsi --user=511 --group=511 --stdout=stream -- flagstat /home/guestsi/playpen/sam/small.bam
inscrutable#

Similarly, --stdout=tty produces no output either.
Any ideas?

PS. using official rkt 1.25.0 RPM

If you want to use the experimental attach modes (stream/tty), you also need to attach via rkt attach or some other custom I/O handler. See https://coreos.com/rkt/docs/latest/devel/log-attach-design.html and https://coreos.com/rkt/docs/latest/subcommands/attach.html.

Ah, sorry, hadn't noticed rkt attach.  I'll read up on that and try again.
Thanks for your patience.

No problem. Also, have a look at the endpoint in --mode=list, you can directly interface your custom logic via those. Please note that all of the iottymux subsystem is highly experimental, and there are some known open bugs.

So, I read up on rkt attach, and tried using it.  As follows:
# RKT_EXPERIMENT_ATTACH=true /usr/bin/rkt --interactive --insecure-options=image run --net=host docker://biocontainers/bwa:latest --user=511 --group=511 --stdout=stream --exec bash

In another terminal
# rkt list --full | grep running
a8a47476-92a9-46eb-9443-6b5fd75c6fcf	bwa				registry-1.docker.io/biocontainers/bwa:latest			sha512-cbb4f9182164	running		2017-04-24 10:02:28.633 +1200 NZST	2017-04-24 10:02:28.916 +1200 NZST

# RKT_EXPERIMENT_ATTACH=true rkt attach --mode list a8a47476-92a9-46eb-9443-6b5fd75c6fcf
iottymux: runtime failure: open /rkt/iottymux/bwa/endpoints: no such file or directory
stage1-attach: error executing "iottymux": exit status 254
attach: attach failed: error executing stage1 entrypoint: exit status 254

I think this is because the systemd on CentOS 7 is too old.  It is v219, but the design doc says this feature works with v232 and later.
Is this a showstopper with regard to getting hold of stdout directly from a container on CentOS 7?
(We are having severe performance problems with journald, because of the huge amount of stdout.  With bioinformatics applications, this can be hundreds of GB.)
  Recall that my goal is to pipe huge quantities (100s GB) of data between containers stdin/stdout without going through journald, that I am on CentOS 7 with systemd v219, and that upgrading systemd to v232 seems infeasible (to me, since Red Hat heavily patched the upstream in their systemd RPM).
But what I could do is mount /proc/$$/fd from the host into the container, and arrange for the container to redirect its stdin/stdout/stderr through these host file descriptors, before running the actual target program.  A brief test doing this for stdout showed it doing the right thing.
Does this seem like a reasonable idea to avoid the journald overhead?

Which stage1 are you using? The >=232 dependency is on stage1 systemd, if you are using stage1-coreos you should be already fine.
Also, looking at the specifics (kernel, systemd) of this system, it seems pretty ancient and I'd likely expect misbehaviors on the front of cgroups/namespaces/overlayfs. Isn't there some newer release of this distro? /cc @brianredbeard

But what I could do is mount /proc/$$/fd from the host into the container, and arrange for the container to redirect its stdin/stdout/stderr through these host file descriptors, before running the actual target program.

This is pretty much what --stdout=stream does, except that those fds are socket-units in stage1 context and bridging to host happens via rkt-attach.

I'm using the default stage1, which would be the stage1-coreos I believe.  Glad to hear that the systemd dependency is only on stage1, not on the host.  (RHEL 7 is not so much ancient, as, well, stable.)
Would there be another reason why I get that stage1 error?
iottymux: runtime failure: open /rkt/iottymux/bwa/endpoints: no such file or directory

Are there more useful diagnostics I can provide?  For example, interrupting stage1 and having a look what's gone wrong inside?

I've just realized you are running with --interactive, which bypasses all the single-stream options (this should probably be reported as a separate bug, as the two options are mutually exclusive).
I tried replacing that with --stdout=stream --stdin=stream and your container seems to work fine. Please note however that you won't get a TTY in this case, see https://github.com/rkt/rkt/issues/3652.

Ah, yes, that was because I was careful to follow the instructions on the man page:

In order for an application to be attachable:

it must be started in interactive mode ...

If I just run it without that, there would seem to be a race for rkt attach to actually attach before any output is lost? Or does the pipe simply fill and block in that case?

Ah, yes, that was because I was careful to follow the instructions on the man page

Bad wording on my side, that should read "attachable mode".

If I just run it without that, there would seem to be a race for rkt attach to actually attach before any output is lost? Or does the pipe simply fill and block in that case?

Correct, there is no buffering involved at the moment, see https://github.com/rkt/rkt/issues/3587.

OK, thanks for the clarification.  I'll try again, with a work-around for the lack of buffering.

I've basically got this working, but there are a few frustrations.
How best to obtain the UUID of the container so I can run rkt attach is not clear.  I wanted to use rkt prepare, which tells me that, but this experimental functionality doesn't seem to be supported there.  (I presume you plan to add it.)  Instead, I have to wait around for a while, then look at the output of rkt list and try to find my container.  And only then can I call rkt attach.
Lack of buffering meant I had to work quite hard on the synchronisation.  Sleep is fragile on a busy system, as you're never quite sure how long to wait.  Instead, I mounted another directory from the host into the container, and wrote a wrapper rkt-run-slave that runs in the container, using inotify, so that the external event (rkt attach has run) may be notified by the host into the container by creating a file.  rkt-run-slave waits until this has happened before running the target program in the container.  This works nicely, but seems like a work-around for a problem which shouldn't exist.
It would be nice if the stream attachment could be done inside rkt run with all the synchronisation handled automatically, so the container program doesn't get started until the streams are all attached.
I've added this functionality to rktrunner.  Not quite finished, it's a work in progress at this time.

Regarding "obtaining UUID", you are probably looking for --uuid-file-save (which should be expanded to more subcommands, see https://github.com/rkt/rkt/issues/3005).
Regarding "waiting for a while", I think rkt status --wait-ready will help you determining when the pod is ready. I think a similar option for app status may also make sense, as I'm not sure the one above solves all your problems.
Regarding inotify, just beware that it may misbehave on overlayfs on non-root-recent kernels.

OK, thanks, I'm now using these (rkt run --uuid-file-save and rkt status --wait-ready) and it's working nicely.
I haven't hit any issues with inotify misbehaviour so far.

@tesujimath nice to hear! (aside from all the stream-attach related bugs, which are unfortunately still there in this experimental phase)
Perhaps that uuid-save+wait pattern is not documented well enough. We'll gladly take any PR for the user-docs or external blog-posts showing an actual workflow, like in your usecase.

@lucab thanks for your help on this.  I am indeed hitting some problems, with what I presume are stream-attach related bugs.  Getting errors from the Go runtime like this:
runtime: failed to create new OS thread (have 5 already; errno=11)
runtime: may need to increase max user processes (ulimit -u)

I've also seen errors like this:
stage1-attach: error executing "iottymux": signal: broken pipe
attach: attach failed: error executing stage1 entrypoint: exit status 254

And occasionally like this:
Unable to open "/proc/15083/root": No such file or directory
stage1-attach: error executing "iottymux": exit status 2
attach: attach failed: error executing stage1 entrypoint: exit status 254

I've not yet had much success trying to isolate these problems.  I've started looking into using the fly stage1 as a way of avoiding some of these nasties.  That may be sufficient for our use cases, although I see there are some issues with fly (I hit #3662 almost straight away).
Given these problems, I thought I'd better reopen this issue.

@lucab BTW I am not ignoring your suggestion about describing our use of rkt in a series of blog posts.  I'll probably get round to that at some stage, and will ping you back then, in case you want to link to them.

Why is this rkt attach stuff needed for stdin/out comm. with a container - at least with a single app in a pod?
IMO this doesn't seem to fit the rkt philos.: "it is like running an executable .. no daemons, no fuzz ..".
Is it possible to bind additional FDs (besides 0, 1 and 2) to communicate between the parent process that started rkt and the container started by rkt?

Because a pod is not a single app, and the supervision/muxing have to be handled somewhere inside it. Also, this doesn't clash with the general design, as everything is still rooted under a separate process tree.

Is it possible to bind additional FDs (besides 0, 1 and 2) to communicate between the parent process that started rkt and the container started by rkt?

A specific subcase of this is possible with socket-activation, however I think this doesn't work in general as there are several points in the exec chain where we ensure fd are O_CLOEXEC to avoid escapes.

@lucab Do you know a container system for Linux that allows real composability like Unix executables directly hooked up via pipes, pushing potentially mass data over?
I understand, neither Docker nor rkt was designed for that ..

@oberstet While not a container system per se, potentially something like the vector packet processing and CICN/libcinet components of fd.io to optimize the transport would be what you're looking for.  I know that folks at the various companies sponsoring the project have prioritized delivery of these pieces of software for containerized workloads.
I didn't really intend to side track this, only point out that as folks have higher throughput requirements there are pieces in flight (in the true old school Bell Labs "UNIX" philosophy that UNIX is a control plane platform for manipulating an external data plane like 5ESS)

Do you know a container system for Linux that allows real composability like Unix executables directly hooked up via pipes, pushing potentially mass data over?

systemd-nspawn by itself, rather than via's rkt's use of it, is able to handle pipes pretty well. All you have to do is not use the '--boot' flag.
An example, modified from the nspawn docs:
# machinectl pull-raw --verify=no https://dl.fedoraproject.org/pub/fedora/linux/releases/25/CloudImages/x86_64/images/Fedora-Cloud-Base-25-1.3.x86_64.qcow2
# echo -e "hello\nworld" | systemd-nspawn -M 'Fedora-Cloud-Base-25-1.3.x86_64' --network-veth -q -- tac
world
hello

'runc' could also do something similar, though it has some additional complexity to support containerd/docker and such, and doesn't have any image management.
rkt conceivably could have a stage1 or a flag that, like fly, doesn't support multiple apps and can thus exec directly through.
It already has '--interactive' which is sort-of a flag for this kind of thing, but doesn't work properly with pipes.
The overall idea though is a bit at odds with pods.

@euank thanks a lot for these insights and hints! very interesting.
having a simple flag to rkt (single app + interactive) would be I think exactly what I am after: the convenience/high-level abstraction that rkt provides me (compared to raw runc or systemd-nspawn) and the "full" composability.
"composability" is a stated goal of rkt, and from my impression, above would fit into that quite well - but I am in no position to judge of course - just my limited perspective.

The overall idea though is a bit at odds with pods.

Right.
I've read that rkt wants to be "best buddy" to k8s, but there might be a stretch/conflict in goals with "composability".
But then, above flag could be used outside a k8s context - for those of us that do something else. Being able to create a processing graph out of piped containers comes to mind. My use case is a container manager (non k8s/mesos/..) that a) allows to tap into the live container log stream remotely or b) can talk a real protocol over pipes with the stuff inside the container.

You could wire up your components using raw TCP instead of pipes. I do not
think that you'll get throughput problems when everything is local. And if
you're growing this approach is easily distributable over multiple machines.
Tobias Oberstein<EMAIL_ADDRESS>schrieb am Mi., 7. Juni 2017,
21:13:

@euank https://github.com/euank thanks a lot for these insights and
hints! very interesting.
having a simple flag to rkt (single app + interactive) would be I think
exactly what I am after: the convenience/high-level abstraction that rkt
provides me (compared to raw runc or systemd-nspawn) and the "full"
composability.
"composability" is a stated goal of rkt, and from my impression, above
would fit into that quite well - but I am in no position to judge of course

just my limited perspective.

The overall idea though is a bit at odds with pods.
Right.
I've read that rkt wants to be "best buddy" to k8s, but there might be a
stretch/conflict in goals with "composability".
But then, above flag could be used outside a k8s context - for those of us
that do something else. Being able to create a processing graph out of
piped containers comes to mind. My use case is a container manager (non
k8s/mesos/..) that a) allows to tap into the live container log stream
remotely or b) can talk a real protocol over pipes with the stuff inside
the container.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/rkt/rkt/issues/3639#issuecomment-306896135, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AC3LqQDXn9BXtjuPEva3F6j9t-uGk6HTks5sBvZEgaJpZM4M5Y8J
.

@trusch using TCP complicates matters (listening ports), and will indeed have less throughput / more overhead compared to (buffered) pipes (at least 2 copies vs 1).
@euank "Containers are started as a child process of runC .." - mmh. Is there something that doesn't fork, but replaces the executed image (https://linux.die.net/man/3/execlp)?

@lucab I got round to writing up some blog posts on our use cases for rkt with BioContainers as per your suggestion.  You will see that we solved the stdio piping problem by switching to fly-stage1.  Please feel free to link to the blog if you think it would be of interest to other users of rkt.


Question marks exist

Treasure-Chords.zip

Something Good-Chords.zip

House of the Lord-Chords.zip

Sunday Is Coming.zip

Fixed with commit db21382


Can't scroll down on mobile when scrolling on an image

Is there a way to make it so that if a user tries to scrolls down with their thumb on a mobile image that they'll scroll down the page?  Right now, on mobile the user can't scroll down if they touch an image.  They have to select some other content.  Is there a setting for this?

I'm using a nuxt.js version of slick, and this fix is not working for me. I can reproduce it on iPhones as well. Looking at their source code, they've already added this touch-action fix but the vertical scroll is still stuck for me. Carousel demo's here (not the masthead):
My code:
https://bit.ly/35Wtq9I
The library:
https://github.com/gs-shop/vue-slick-carousel

Had the same issue when using react-slick. Only on mobile. Only over images within slick carousel, not text content. Solved simply by adding pointer-events: none on images :)

Had the same issue when using react-slick. Only on mobile. Only over images within slick carousel, not text content. Solved simply by adding pointer-events: none on images 🎉

Had the same issue when using react-slick. Only on mobile. Only over images within slick carousel, not text content. Solved simply by adding pointer-events: none on images 🎉

pointer-events: none it works for me .
thanks @pttsky

I have the same problem, I can't scroll vertically on images on mobile, can anyone help me ????
My website is this:https://techgang.pt/products/cargador-sem-fio-3-em-1


CSM - added team member model

Description
Ticket
Changes Made

added team member model

Screenshots

 Backend - create team member model


Children props are lost when custom element is moved in the DOM

Components are hydrated each time they are appended to the document.
var c = document.createElement("my-test");
document.body.appendChild(c);
document.body.appendChild(c);

The render() function is called twice. The second time e.g. this.props.children does not work any more.

Hi @fab920!
Thanks for reaching out.
If I understand correctly, you're pointing out that each custom element instance added to the DOM is an independently rendered component? If this is the case, this is intended behaviour. Each custom element should have its own separate context, state, etc, and will require it's own render.
If I'm wrong, and this isn't what you're pointing out, would you mind clarifying for me?
It would also be really useful if you could you provide me with a simple reproduction, a quick repo that demonstrates the issue would be really helpful 👍
Thanks!

Hi @jahilldev ,
no, I want to point out that an instance of an custom element is hydrated each time it is added to the DOM.
I would provide a JsFidle if I knew how to create one with preactement, but if you just execute the 3 lines of codein the initial post, e.g. in the developer console, with any custom component, the problem should be be reproducible.

I want to point out that an instance of an custom element is hydrated each time it is added to the DOM.

So this seems like what I would expect. For example, if I'm dynamically creating an element, my-test let's say, whenever I add it to the DOM via appendChild, that is essentially a new component instance being instantiated, which will require its own render / hydration.
When you make use of a component multiple times in (p)react, you wouldn't expect all of those components to share the same context, state, etc. They are essentially separate entities.
If I run your snippet on a site that makes use of (p)reactment, I can see it adding the custom element to the DOM, and rendering the component. I don't see a double render however, as an element can only be added to the DOM once:

I feel like I'm probably missing something that an example reproduction would make obvious. I'd suggest creating a repo and outlining exactly what you're expecting to happen, and the issue you're highlighting.
Thanks!

So this seems like what I would expect. For example, if I'm dynamically creating an element,  let's say, whenever I > add it to the DOM via appendChild, that is essentially a new component instance being instantiated, which will require its own > render / hydration.

No, that's not what should be happening. When you create a DOM node (normal or a component) and add it to the DOM multiple times to the node gets moved around in the DOM.
The appendChild() method of the Node interface adds a node to the end of the list of children of a specified parent node. If the given child is a reference to an existing node in the document, appendChild() moves it from its current position to the new position (there is no requirement to remove the node from its parent node before appending it to some other node).
Source: https://developer.mozilla.org/en-US/docs/Web/API/Node/appendChild
I probably should have chosen a better wording and a better example :-(
var c = document.createElement("my-test");
document.getElementById("NodeA").appendChild(c);
document.getElementById("NodeA").removeChild(c);
document.getElementById("NodeB").appendChild(c);

So essentially the component is recreated every time you move it around in the DOM.
Gist with a more complete example
https://gist.github.com/fab920/7340b4a19ed11773e6f4647e889fedd0

The same happens when you move one of its ancestor elements
var c = document.createElement("my-test");
document.getElementById("NodeA").appendChild(c);

document.getElementById("NodeB").appendChild(document.getElementById("NodeA"));

will recreate (and rerender) my-test.

@fab920 Ok, well that makes a lot more sense!
Your initial example is as I said though, you can only add it to the DOM once in that position. The example you've provided now is completely different!
Give me a few days to check out your example and I'll see what's going on.

@fab920 A quick question before we go on, I'm interested to know the use case here. What are you trying to achieve?
I can see why this is happening, when you move the Custom Element, the onDisconnected callback is being invoked, which "unmounts" the component, and the "remounts" when it's added back in at another position, firing onConnected.
Why is the re-render an issue when it's being moved?

In my case it's about the content in the <slots/>.
When the component is recreated this.props.children is empty. If you look at my gist, the lorum ipsum is gone after the component is recreated.

@fab920 So I've created a simple repro for you below:
https://github.com/jahilldev/preactement-moved
I still don't fully understand what you're referring to about slots, these are correctly persisted when the element is moved in the DOM. Could you pull and run my repro and feedback, please?
this.props.children are lost however, for the reason I outline above. I'm going to open a PR shortly to address this.
I'd strongly recommend going to the effort of creating a runnable repro of an issue you're raising in future, though. It's really helpful to isolate and describe the problem, and 9 times out of 10, the maintainer won't do this for you.
I'll let you know once the PR is up.
Thanks!

I'm not moving the component itself, but it just gets moved as part of one of its ancestors moving.
A lot of third party libraries & components tend to move dom nodes to the `body'' for modals, popups, popovers, ...
E.g. we are using preact together with ionic.
render(
	<ion-modal is-open="true">
		<my-test>lorum ipsum</my-test>
	</ion-modal>, document.body
);

is not working. lorum ipsum is missing from the output.
And, on other problem is, that if the code is generated server side, I can not just recreate the my-test. The needed data is missing on the client.

@fab920 Could you verify you've looked at my above comment?

Looking right now. Posted my answer just the same moment you did.
Thanks for all your help.

still don't fully understand what you're referring to about slots, these are correctly persisted when the element is moved in the DOM. Could you pull and run my repro and feedback, please?

Sorry!! - Indeed '''''' are working as expected and it's only the children, that are not working.

I'd strongly recommend going to the effort of creating a runnable repro of an issue you're raising in future, though. It's really helpful to isolate and describe the problem, and 9 times out of 10, the maintainer won't do this for you.
Sorry, I tried to and could provide one now :-/ . It just took me ages to set it up. Starting a new project from scratch is something I never had to do until now.

Thanks again for your effort and the fast PR

@fab920 Ok great, we got there in the end, go team 🥳
No worries, I'm just glad we've got a solution now.
Will let you know once the PR is up 👍

@fab920 Here we go:
https://github.com/jahilldev/component-elements/pull/19

@fab920 I've just published preactement v1.8.2 and reactement v1.1.2, you can go ahead and update.
Let me know how it goes, please feedback either way!
Thanks 👍

Looking good.
Thanks a lot!


[Bug] [Master] Activity Stream PHP Warning Template/event/file_create.php failed to open.

When viewing an activity stream that includes an event for a file that was added to a task before commit 8e25c87, a PHP warning is encountered.
Possible fix would be to run an "update project_activities set event_name= 'task.file.create' where event_name=‘file.create' " command on the database.
Sorry, unable to prepare a pull request at this time.

Should be fixed now if you update master.
Thanks.


Decennial Census For Export into dev

Because there is a roadblock on the 2000 pums data, we are creating a new pull request just for the decennial census data so that it can be merged into and exported to DO.

awesome! making some changes to the design of the export process but keeping the logic implemented here


Fix typo, varient -> variant

Found via codespell -H

Thanks!

:partying_face: :partying_face: :partying_face: :partying_face: :partying_face:


Decide what to do with Decision Services and multiple DRDs on the new DMN Editor

As we evolve our new DMN Editor (#439), we want to come up with a conscious and definitive solution for supporting multiple DRDs while comprehensively managing the underlying DRG. Decision Services are complex enough even without multiple DRDs, but as DMN models can depict different portions of the DRG with many DRDs, we need to decide how we're going to deal with Decision Services and multiple DRDs.
The new DMN Editor already deals really well with single DRDs, making it easily to add/remove Decisions to/from Decision Services by dragging nodes in to / out of a Decision Service, and making it clear that these Decisions are "contained" by a Decision Service by giving them a thicker border.

The DMN 1.5 specification, on section 6.2.5 Decision service, only states that a Decision Service cannot be rendered in both collapsed and expanded form in the same DRD. Leaving a lot for interpretation and for implementers to decide.
It's also clear from the spec that Decision Services can be rendered in both expanded and collapsed form in multiple DRDs, but it is unclear what happens when one decision ceases to be part of a Decision Service, they'll continue to be visually enclosed by the Decision Service in other DRDs, although with normal border width in our new DMN Editor, it may be misleading. Leaving this burden for users to deal with when editing their DMNs is tedious and increases the cognitive load of dealing with Decision Services.
Now, using the statements we got from the DMN specification, and the DMN depicted above, let's discuss some of the difficulties of having Decision Services and multiple DRDs.
If I create a new DRD B, there are several things we can do in regards to DS A:

Allow adding DS A to it, without any of its contained Decisions.

Easy to implement, but misleading as the Decision Service appears empty, when we know from the DRG that it is not.

Allow adding DS A to it, bringing all its contained Decisions with it, automatically layout'ed inside DS A.

Seems logical and very easy to use and understand, but will impose a lot of problems when modifying the DMN later. We'll discuss it below.

Allow adding DS A to it only in collapsed form, so none of its contained Decisions and dependent nodes will ever be displayed in DRD B

Doesn't exactly conform to the specification recommendations, but does not violate any of the requirements. Not so easy to implement too, but allows for a smooth experience when editing the DMN later. We can even add an easy hook into the collapsed Decision Service that will take users to the DRD where the Decision Service is on its expanded form, allowing for easy editing.
This option is not free of downsides, though, as some of DS A dependencies might also be dependencies to nodes that depend on the DS A. More on this below.

Do not allow adding DS A to DRD B at all, as it is already depicted in DRD A.

This will make it impossible to depict DS A in any way, making it impossible to show the full tree of a node that might depend on it via a Knowledge Requirement. Ultimately, this might make users ignore the multi-DRD capabilities of the new DMN Editor, as for some kinds of Decision models, it might be useless to separate only the portions of the Decision model that are not dependent on a Decision Service.

As you can see, each of those options lead to fundamentally different consequences which we need to consider in order to try and achieve the most efficient and pleasant experience for our users.
In my opinion, options 1 and 4 are out of the table, given the drawbacks they have. For options 2 and 3, I think we need to discuss more.

Option 2 (Allow bringing a Decision Service into a DRD with all its contained Decisions automatically layout'ed inside it)
Consequences:

A Decision Service can never be shown in its expanded form with a missing contained Decisions.
We can't hide a Decision from a DRD if their contained Decision Service is depicted also depicted in the same DRD.
When adding a new Decision to the DRG then adding it to an existing Decision Service, all DRDs that depict that Decision Service will need to be altered to automatically position the new Decision inside the Decision Service, to avoid misleading DRDs and weird behaviors when moving the Decision Service node around. This will potentially mess around too much with DRDs that are hidden in the background.
The above is also true for moving Decisions out of the Decision Service. Hidden DRDs might continue showing the Decision inside the boundaries of the Decision Service, which might be misleading.

Option 3 (Allow depicting a Decision Service in its expanded form in only one DRD, depicting it in its collapsed form in other DRDs)
Consequences:

Limiting in terms of what users can do, and does not follow the suggestions of the DMN specification.
Makes it easier for users to modify existing Decision Services, as their expanded form is limited to a single DRD, so users don't need to worry about messing with their other DRDs when modifying a Decision Service.
If Decisions contained by a Decision Service are already depicted in a DRD, the Decision Service itself cannot be. And vice-versa.
From our example above, this weird situation can happen in a new DRD B:

Even weirder, is this:

D F is a dependency of D E, which is encapsulated by DS A, that's in its collapsed form. No edges connect the two, though, making it look like DS A and D F do not have any kind of relationship. Let's call this PROBLEM A.
Of course, adding D D, D C, or D E would not be allowed for this DRD.
This situation below is also not so simple, as D A has a Knowledge Requirement to DS A.

Clicking the ... on D A might even show DS A as a dependency, but we won't be able to show it on DRD C, since one or more of its contained Decisions are already present. Let's call this PROBLEM B.

As you can see, both options still have problems. IMHO, option 2 still puts too much in the users' shoulders and has the serious problem of tempering with DRDs that are not visible, but option 3 has PROBLEM A and PROBLEM B. Both are solvable, but we need to come up with good solutions to deal with them if we decide to go with option 3.

Note that I might have missed something during my analysis, so feedback is more than welcome!

I'm really looking forward to hearing other people's opinions. Please do chime in!

Hi @tiagobento , let me share my thoughts about this topic. and my expectation, how the editor should work for this scenario.

I understand DRDs and Decision Services as two similar concepts, where both tries to simplify the model for users. However each does different simplification.

I understand DRDs more just like filtering of the nodes from the diagram. And each DRD as some stored filtered view of the main DRG. If I recall correctly, there can not be a node in DRD that wouldn't be in DRG. And I think DRD should contain:

either whole Decision Service node
or no Decision Service node

my reasoning for this is bellow.

I understand Decision Services as wrapper for some complex logic. These wrappers/decision services helps user to reuse some already created logic on more places, same as BKM nodes does. But from my point of view, it makes no sense to try reuse some wrapper/decision service on some other place and not include all its content. It would break not deterministic. I mean, if we once define Decision Service, it should always return the same results for the sme inputs. And this means Each occurrence of a decision Service node, is the same, containing all its encapsulated and output decisions.
So I think if a Decision Service node appears in any DRD, it should alywas represent the same logic. I do not have strong opinion if we use collapsed or expanded views to achieve this.

I think I speak about the same, what you describe as Option 3 but using other words?

I'm more inclined to option 2
I think that using a Decision Service should bring all nodes with it. As Jozef brought to the table, the idea of a Decision Service is to encapsulate a complex logic. Thinking about that, it's not reasonable to use a piece of this encapsulated logic (e.g. one decision node). With that in mind, I don't think it should be allowed to use nodes that were wrapped on it.
Now, editing a Decision Service should reflect on all DRDs, even though it can be challenging. If it helps, we could limit editing this Decision Service on the DRD where it was defined (a mix with option 3).
Even though we bring all nodes with the Decision Service, I guess we should keep the option to collapse it. This would lead to option 3 PROBLEM A, but it could be solved by expanding the Decision Service when we have a node that has a relationship with it.

Thank you for this comprehensive analysis of the Decision Services, I have couple of questions. Listing them as task list, as that way is easy to transform some of them to new ticket, if needed.
- [ ] We mentioned already some scenarios, when adding a node into DRD will be not possible. I am interested how quickly we want to 'inform' user about this. Will be those 'not allowed' nodes disabled in the list of available nodes? Or all nodes will be always enabled but once dragged to the canvas, some validation will be fired and a flash message displayed if some rule will be violated?
- [ ] In the very last point some new Edge. Am I correct this is not part of the standard? Interested if some UX team can be contacted for some design recommendation can be contacted? Or does other decision modeling tools solve this already somehow?
- [ ] Unrelated to this ticket, but once some new DRD on https://sandbox.kie.org/dev, is there a way to delete DRD? I was not able to delete any DRD.


Fix out of order execution on model select (#1354)

Fixes #1354
When we're removing nodes from the new graph we've constructed for the graph queue, replace all the removed transitive dependencies with explicit ones. The idea here is like this:
Imagine you have a DAG of models that is really boring and linear like: (A -> B -> C -> D)
And you've done dbt run --model A D. The old code would see a graph with those two nodes and no dependencies:

remove B, graph is now (A,), (C -> D)
remove C, graph is now (A,), (D,)

The new code works like this:

look up B's current direct parents (A) and direct children (C)
remove B
Add an edge between each direct parent and each direct child, so (A, C)
Graph is now (A -> C -> D)
look up C's current direct parents (A) and direct children (C)
remove C
Add an edge between each direct parent and each direct child, so (A, D)
Graph is now (A -> D)

A will now execute before D.
Note that if B or C are early-binding views as in postgres/redshift default, this code will still fail, because the drop ... cascade when building A will drop B and C as well, and then D has no existing refs.

Might be a silly question, but this works even if tag: or source: selectors are supplied, right? Should be essentially the same code path as before?

Not a silly question! But no, the "include set" that this is based on is generated earlier up the stack by the node selector, which handles source vs tag vs model name, so the linker can ignore all that.

My only other thought here is that we could bypass the need for this logic by computing the transitive closure of the dag first, then just removing the nodes we don't need. Did you consider an approach like that? I'd need to do some reading, but I'd be curious if it's faster to computer the closure once vs. computing it dynamically for each node that we need to prune from the graph.

That's pretty neat, I didn't know networkx had a function for transitive closure, though maybe I should have guessed! I bet it's at least a bit faster as you get more space between kept nodes in the graph, because you save so much useless calculation (unless the underlying transitive_closure part is slow), but more importantly the code gets simpler.


Support custom Timezone

at the moment the widget uses the default TimeZone
        this.currentCalender = Calendar.getInstance(locale);
        this.todayCalender = Calendar.getInstance(locale);
        this.calendarWithFirstDayOfMonth = Calendar.getInstance(locale);
        this.eventsCalendar = Calendar.getInstance(locale);

We would need a way to customise those calendars with a different TimeZone than the current system TimeZone.
Is this something you would implement?

Seems like simple enough. When setting the locale, give the option to set the timezone as well as perhaps a method override.

I've modified the setLocale method to allow you to set the locale and timezon. Will release a new version today.

Should be released under:
dependencies {
    compile 'com.github.sundeepk:compact-calendar-view:1.9.0'
}

However, I think the best way to get date in a specific timezone is to use SimpleDateFormat by setting the time zone on that. Which makes the most sense.

Closing this issue.

The app (www.teamup.com) in which we use your lib allows switching of timezones depending on which cloud shared calendar the user looks at.
the solution you provided with 1.9.0 works perfectly thank you!


Applying to multi module project

I'm trying to use this plugin for https://github.com/littlerobots/version-catalog-update-plugin. That project has a plugin module and a separate module containing some logic around the version catalogs.
Following the README I've setup the plugin like this:
def shadeConfiguration = configurations.create("shade")

gr8 {
    def shadowedJar = create("gr8") {
        proguardFile("rules.pro")
        configuration("shade")
    }
    // Replace the regular jar with the shadowed one in the publication
    replaceOutgoingJar(shadowedJar)

    // Make the shadowed dependencies available during compilation/tests
    configurations.named("compileOnly").configure {
        extendsFrom(shadeConfiguration)
    }
    configurations.named("testImplementation").configure {
        extendsFrom(shadeConfiguration)
    }
}

repositories {
    gradlePluginPortal()
}

dependencies {
    shade project(":catalog")
    compileOnly("dev.gradleplugins:gradle-api:7.3.2")
    shade "org.jetbrains.kotlin:kotlin-stdlib:1.4"
    shade "com.fasterxml.jackson.dataformat:jackson-dataformat-toml:2.13.0"
    shade "com.squareup.moshi:moshi:1.12.0"
    shade "com.squareup.moshi:moshi-kotlin:1.12.0"
    testImplementation 'junit:junit:4.13.2'
    testImplementation 'com.github.ben-manes:gradle-versions-plugin:0.40.0'
    testImplementation(gradleTestKit())
    compileOnly 'com.github.ben-manes:gradle-versions-plugin:0.40.0'
}

It seems that I have to add the catalog module to the shade configuration too, otherwise none of the classes from that module appear to be added to the plugin jar. But this introduces an issue where I can no longer run my tests; classes from that project are not found in testKit tests, even when testImplementation is extending the shade config.
I'm also not sure if I really need to redeclare the dependencies that that module uses here in the shade config. It also seems that not all of the kotlin classes are relocated in the gr8 jar so that also seems to point to more configuration / user errors 😄
Can you point me in the right direction?

classes from that project are not found in testKit tests, even when testImplementation is extending the shade config

testKit is wildly untested. More specifically withPluginClasspath is wildly untested. I'm pretty sure that wouldn't work. Instead. I'd recommend publishing your plugin to a local maven repository and using that in integration tests to ensure the same environment as your users.

I'm also not sure if I really need to redeclare the dependencies that that module uses here in the shade config.

I think this isn't required. The configuration should resolve the transitive dependencies.

It also seems that not all of the kotlin classes are relocated in the gr8 jar so that also seems to point to more configuration / user errors

I can take a look at this. Since everything is open source, the easiest way is certainly that you push your current state to a branch and we can dig into this.

Thanks for the offer :) I've also extended the implementation config from the shade config now, which fixes the test, however at runtime I'm getting errors...I think that's due to some stuff in META-INF/services getting relocated and renamed too, but I'm not 100% sure yet.
If you want to take a look, the branch is here https://github.com/littlerobots/version-catalog-update-plugin/tree/feature/shade-dependencies

Do you know what's using a ServiceLocator? You might have to keep the implementation class in rules.pro
As for the resource files, it might be an issue in gr8 itslef, not r8. We "merge" all jars together to create an embedded jar before feeding it to r8: https://github.com/gradleup/gr8/blob/5b6d501292ad8e7282891f9872161311e09b63eb/plugin-common/src/main/kotlin/com/gradleup/gr8/EmbeddedJarTask.kt#L54
If two resources have the same name, I'm not sure what's happening...

Tried the repo, I get an error on SerializationConfig that's crashing because there's an enum whose values() method is renamed somewhere around here.
Something like this seems to get me a bit further:
-keepclassmembers enum ** {
    public static **[] values();
}

Do you know what's using a ServiceLocator? You might have to keep the implementation class in rules.pro

Yeah I know what libs are using the service locator, just not how to relocate + retain the correct META-INF/services file. If I keep the implementation then it potentially still conflicts at runtime with a different version of the same library. If I don't then I don't think it loads the correct implementation?

Tried the repo, I get an error on SerializationConfig that's crashing because there's an enum whose values() method is renamed somewhere around here.

Ah yes, that's where I started but I somehow got distracted with those service locator files :) Will add that and dig further...

If I keep the implementation then it potentially still conflicts at runtime with a different version of the same library. If I don't then I don't think it loads the correct implementation?

Right. They'll have to be relocated... TBH, at this point I'd be looking for alternatives not using ServiceLocator. If it's for toml parsing, mayb https://github.com/akuleshov7/ktoml?

Will add that and dig further...

👍
To debug/investigate, it's sometimes useful to remap the symbols. The process to do so isn't super straightforward but it's doable if you have a local r8:
git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git
export PATH=/path/to/depot_tools:$PATH
git clone https://r8.googlesource.com/r8
cd r8
./tools/gradle.py d8 r8
java -cp build/libs/r8_with_deps.jar com.android.tools.r8.retrace.Retrace path/to/your/repobuild/gr8/gr8/mapping
[copy paste your stacktrace and press Crtl-D to launch the retracing]

For now I ended up using the shadow plugin, which seems to work. I'm not relocating Kotlin with it so it would be nice to eventually switch to this plugin, but the service locator files and content are rewritten correctly with the shadow plugin, which seems to be the biggest hurdle.
One thing that is also needed with both this and the shadow plugin is that my additional module needs to stay out of the produced maven pom so that might something to keep in mind when others are trying a similar setup. Otherwise you end up with relocated things in your plugin artifact + a dependency on the non-relocated module + its dependencies.
I might give it another go in the coming days but for now I think this issue can be closed.

Thanks for the update! Do you mind if I keep this issue open? I'd like to make it easier to consume the plugin and investigate real life use cases is a good exercise. I might give it a shot later this week.

I don't mind at all :)

Quick question: how do you test? I'm running ./gradlew build --rerun-tasks --no-build-cache from the feature/shade-dependencies branch and it's all passing ✅

I'm testing this on a different project using the version catalog update plugin, publishing to mavenLocal() and then ./gradlew versionCatalogUpdate.
I made a few more changes on that branch to get it closer to the shadow plugin version, but it keeps failing on the service locator stuff so it seems. Due to the obfuscation it's a bit tricky to track down, I'm not sure if R8 is replacing the service locator string correctly.

Gotcha 👍 . Thanks 🙏
You don't have that other repo on some GitHub url by any chance?  Not that I don't like it but... 😅

I don't have that specific one published, but https://github.com/code-with-the-italians/bundel is also using the plugin so you should be able to use that project, just replacing the version of the plugin. You may want to hardcode it in the plugins block otherwise the plugin will update itself. Though that would mean everything works so eh well 😅

Looks like I found it 🎉  Or at least, it's working now by adding -dontshrink to the rules.
Should have thought of that sooner I suppose...
Looking at the mapping file it seems like the kotlin std lib has also be relocated correctly, but it's still a bit scary 😬

Nice find! 🎉
Yea I feel you, it's definitely a bit scary 😅 but the only way to workaround the Gradle fixed runtime limitations. FWIW, we've been running for ~6 months now in the Apollo plugin and it's working well so far 🤞 .
Thanks for all the feedback in all cases 🙏

One question though, I can still not seem to bump to the latest Kotlin version. As soon as you apply the java-gradle-plugin it pulls in Gradle + some older version of Kotlin. Not sure what the difference is vs the Apollo plugin?

As soon as you apply the java-gradle-plugin it pulls in Gradle + some older version of Kotlin

There's a removeGradleApiFromApi() method in gr8. It's used there in Apollo to override the java-gradle-plugin defaults

hmm I actually have that  so I'm not sure why that's not working for me.

Updating to Kotlin 1.7.10 seems to work for me: https://github.com/martinbonnin/version-catalog-update-plugin/commit/d05321f2337fa3209b705e52603b16e82770adff. I get a module file like this:

plugin.module
{
  "formatVersion": "1.1",
  "component": {
    "group": "nl.littlerobots.vcu",
    "module": "plugin",
    "version": "0.5.4-SNAPSHOT",
    "attributes": {
      "org.gradle.status": "integration"
    }
  },
  "createdBy": {
    "gradle": {
      "version": "7.4-rc-1"
    }
  },
  "variants": [
    {
      "name": "apiElements",
      "attributes": {
        "org.gradle.category": "library",
        "org.gradle.dependency.bundling": "external",
        "org.gradle.jvm.environment": "standard-jvm",
        "org.gradle.jvm.version": 8,
        "org.gradle.libraryelements": "jar",
        "org.gradle.usage": "java-api",
        "org.jetbrains.kotlin.platform.type": "jvm"
      },
      "files": [
        {
          "name": "plugin-0.5.4-SNAPSHOT.jar",
          "url": "plugin-0.5.4-SNAPSHOT.jar",
          "size": 80162,
          "sha512": "58e82638ce9238cc702a7b325d2f3d5d82785a733ed84c555aa5006058d0b20ab6b8523f7d3bf9ba28a4aceb1871788cdb696aa5ce113861bb580e859a666f68",
          "sha256": "1d502706135b7887db0484571c74bc1484756ba0c777ff3e63710dcc6a3b85b2",
          "sha1": "adabfe4cdd30ba9c59367c8bff80bcb7681c25ff",
          "md5": "de61175e18bb0bfb68cfc60f04a0cf64"
        }
      ]
    },
    {
      "name": "gr8",
      "attributes": {
        "org.gradle.category": "library",
        "org.gradle.dependency.bundling": "shadowed",
        "org.gradle.libraryelements": "jar",
        "org.gradle.usage": "java-runtime"
      },
      "files": [
        {
          "name": "plugin-0.5.4-SNAPSHOT-shadowed.jar",
          "url": "plugin-0.5.4-SNAPSHOT-shadowed.jar",
          "size": 3750806,
          "sha512": "c46e304d8c57775fc2c1745af035cb5db11355725e4e06909ee9a837f5bc756a4d7906c574e323a28019c688c02ffa96d7bcde82972436fa24534d275d7cb45a",
          "sha256": "3878417019fa9aeb36b73cb006a9754f7762b67220bb2c4a2a0714c23e8ad712",
          "sha1": "3a9719b8dabb3306af4ace8996f4a95d9b60582c",
          "md5": "4a423a0eb60de768349b4e433c8cf8d8"
        }
      ]
    }
  ]
}

A bit weird that both "plugin-0.5.4-SNAPSHOT-shadowed.jar" and "plugin-0.5.4-SNAPSHOT.jar" but Kotlin isn't exposed as a transitive dependency

My main issue is that within the IDE everything is still locked to the older version, so I still can't really use newer Kotlin features (also with I check out your branch). Autocompleting the beloved uppercase() shows a crossed out toUppper() but no completion for uppercase() and also doesn't compile 😢
re: the module, I guess the file naming is off, but in terms of api/implementation it does seem to be correct right?

Ah yes, we bumped into a similar issue with @handstandsam. He wrote a nice blog post about it: https://handstandsam.com/2022/04/13/using-the-kotlin-dsl-gradle-plugin-forces-kotlin-1-4-compatibility/
The article was about the kotlin-dsl plugin but looks like the java-gradle-plugin is doing the same. You should be able to workaround with something like this:
afterEvaluate {
    tasks.withType(KotlinCompile).configureEach {
        kotlinOptions {
            apiVersion = "1.7"
            languageVersion = "1.7"
        }
    }
}

Hey @hvisser I'm bumping into this issue again and forgot most of the context 😓. Is it ok to close or is there something that still needs to be investigated there?

I'm fine closing this, I also forgot the context and in the end used the shadow plugin 😅


CAB-3585 - Do not display error message when there is no custom message

Coverage decreased (-0.03%) to 82.107% when pulling 0cd94ff57a21c4f5bfa350f85c259c1947415779 on feature/CAB-3585 into a1091b463105e278a1844d54e123cb97f34f4014 on develop.


Remove call to missing method in vite_ruby

Attempting to create fix for https://github.com/maglevhq/maglev-core/issues/91.
(Very much still a WIP, but doesn't look like draft PRs are enable for this repo.)

Actually I'm just going to close this until I can figure out what the heck I'm doing lol.


Create newREADME.md

Prepare for test of updating a pull request

Contributor: Create pull request
Maintainer: Comment and ask for update
Contributor: Perform update and re-issue pull request

REVIEW: make some changes in newREADME.md and then re-issue pull request


Apply https://github.com/cockroachdb/docs/pull/5086 to 2.1 and 19.2 docs

Changed the port for zookeeper from 8081 to 2181

This change is

@lhirata, once this passes TC, can you please merge for me?

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/9e96b8564f45c32e057940fff6d74f02f0d70f68/
Edited pages:

v19.2/change-data-capture.md
v2.1/change-data-capture.md


limit argparse <= python 3.4

See https://github.com/Toblerity/Fiona/pull/775

Coverage remained the same at 82.497% when pulling a3b0fcb091605e89925e95a248c3cefb951ac33d on rbuffat:fix_argparse into 8c13246a6efa3a25f132fbca7e04c0a0a78da4e6 on Toblerity:master.


Release packaged executable.

Following in from #1, this requires the supporting dependencies used by the packaged executable to be made available at Maven Central or wherever Coursier gets them from, and a release to be defined in GitHub that includes the packaged executable.
Some documentation as to how to download the executable and use it would be nice too. 😸

The Sonatype JIRA ticket https://issues.sonatype.org/browse/OSSRH-95530 has been completed. Now to try it out...

Got the libraries published to Sonatype, so far so good...

... next, how to get the packaged executable on to GitHub as a release ...

It seems to work - in fact it works so well it is masking a problem with the artifacts pubished to Sonatype.
What happens is that the Coursier bootstrap executable (made available in a GitHub release by manual upload) contains both the kinetic-merge_3 JAR and the supporting rabinfingerprint_3 JAR (which incidentally shouldn't have the _3 part - it is built from Java.
So it doesn't need these artifacts tp be published to Sonatype, as long as all the other dependencies are available - which they obviously are as the SBT build can pull them in.
Now there is a case to be made for not bothering to publish to Sonatype, but it would be nice to allow others to call Kinetic Merge programmatically, which is what the automated tests already do.
If so, then the code in the Rabin fingerprinting support project should be either published too (which is not a good idea because it is a copy-and-paste from another public repository; I don't want to impersonate them, even if under the com.sageserpent organization), or fused into the kinetic-merge artifact as a slightly fatter JAR.
Need to think about this...

Also need to document the, ahem, installation process - this is currently a case of executing:
curl -LJO --verbose http://github.com/sageserpent-open/kineticMerge/releases/download/v<release version>/kinetic-merge

chmod ug+x kineticMerge

Oh, and there needs to be a .bat file for Windows too!

As of release 0.1.4 the Rabin fingerprinting dependency is shaded into the JAR for Kinetic Merge.
So any use of the Kinetic Merge JAR from Sonatype / Maven Central should resolve without referencing a non-published library.

Install procedure tested on a Linux machine with no local build of Kinetic Merge, confirmed to work properly.
All that is left is to burn in the release version into the executable...

The version is now reported.
As an aside, IntelliJ can no longer correctly import the SBT project due to all the trickery used to avoid generating a dependency on the Rabin Fingerprint project in the published POM, so it has to be told to build with SBT.
That needs fixing at some point.

Have done a couple of releases, so closing this as good.

Not so fast - for some reason the packageExecutable is run against the snapshot version even though this is done after the publish of the non-snapshot version to Sonatype, so the version reported by kinetic-merge --help is wrong.

As of release 0.1.7 / published libraries version 0.1.7 the executable now reports the correct version, so closing again.


[Content block segmented] Extra spacing before CTA

Spacing under bodycopy, before CTA, should be 32p

Dupe!


Multiplatform/swiftui3

• Targets bumped to iOS 15 and macOS 12.
• Adds IconImageCache to the Multiplatform targets and fixes unwrap.
• New .syntax used for styles instead of Style()
• Fixes vertical stutter on article view during window resize.
• @AppStorage properties in AppDefaults have had objectWillChange removed.
• Custom MacSearchField file deleted
• Adds placeholder .searchable search field.
• Toolbar navigation subtitle now has unread count.
• Toolbar navigation title now matches AppKit behaviour.
• Removes (lack of) ability to set default RSS feeder option from preferences
• Fixes a crash in Account preferences view
• Toolbars reconfigured to match AppKit
• Removes filter from top of timeline to match AppKit
• .onAppear{} changed to .task{}
• .withAnimation used to show the refresher.

It looks like there are still build settings changes for version numbers in the project.pbxproj file.

Without manually setting the targets to iOS 15 and macOS 12, they won't build (even with the target versions set in .xcconfig to 15/12). You end up with errors:

'banner' is only available in macOS 11.0 or newer
init(wrappedValue:_:store:)' is only available in macOS 11.0 or newer

I think it's the target version override in the multiplatform xcconfig that isn't being respected.

Have you tried manually deleting the buildSettings from project.pbxproj using a text editor?

That seems to fix it, thanks!


Chore: Support epub tests in docker image

Summary
Can support more filetype: epub, odt and rtf since the new base image now have a newer version of pandoc

Looks good! Can you paste a quick snippet for testing? I suppose all we'd need to do is try to call partition() with these file types, correct?


Use list rather than set in setup.py - currently broken with setuptools v38.0.0+

As of setuptools v38.0.0 it is no longer valid to use unordered
sequences (sets or dicts) for install_requires or tests_require.

Reference:
https://github.com/pypa/setuptools/blob/master/CHANGES.rst#v3800
Fixes this error when installing with setuptools v38.1.0:
Complete output from command python setup.py egg_info:
error in ethereum setup command: 'tests_require' must be a string or list of strings containing valid project/version requirement specifiers; Unordered types are not allowed

Developers should maintain requirements.txt and dev-requirements.txt. There is no need to deduplicate it in setup.py.

I had considered that as well @fuzzyami, but why would we want to silently fail if the requirements.txt is invalid? Better to let CI/Travis fail and bring the error to the attention of the developers.


♻ Prepare -> Apply

♻ Refactor

We need to:

rename prepare to apply in both cmds and endpoints.
Then make a prepare that prepares all nodes in an offline state.

Motivation

Separation of duties for clarity.
Implementation

Effects:

snops
scli

completed in https://github.com/monadicus/snarkops/pull/315


docs(contributing): typo fix

What:

Just a minor typo fix.

Issue number: N/A

Codecov Report

Merging #497 into master will increase coverage by 0.36%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #497      +/-   ##
==========================================
+ Coverage   71.92%   72.28%   +0.36%
==========================================
  Files          65       65
  Lines         552      552
  Branches       34       34
==========================================
+ Hits          397      399       +2
+ Misses        145      143       -2
  Partials       10       10

Impacted Files
Coverage Δ

...tarter/src/app/core/animations/route.animations.ts
100% <0%> (+20%)
: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 425bdb8...6356263. Read the comment docs.

Thanks mate!


Add AWS X-Ray support

Maybe implement OpenTelemetry instead? Works with xray too:
https://aws-otel.github.io/docs/getting-started/go-sdk/trace-manual-instr

OTel support was added in v3.8.0


redefinition of 'SUCCESS' as different kind of symbol

Report
Plugin Version
6.13.1
On what Platform are you having the issue?
ios
What did you do?
Run build
What did you expect to happen?
Build Success but error
What happened instead?
redefinition of 'SUCCESS' as different kind of symbol
i'm using this lib.    "@react-native-seoul/naver-login": "3.0.0",
naveridlogin-sdk-ios/NaverThirdPartyLogin.framework/Headers/NaverThirdPartyLoginConnection.h:11:
typedef enum {
    SUCCESS = 0, // <--- here
    PARAMETERNOTSET = 1,
    CANCELBYUSER = 2,
    NAVERAPPNOTINSTALLED = 3 ,
    NAVERAPPVERSIONINVALID = 4,
    OAUTHMETHODNOTSET = 5,
    INVALIDREQUEST = 6,
    CLIENTNETWORKPROBLEM = 7,
    UNAUTHORIZEDCLIENT = 8,
    UNSUPPORTEDRESPONSETYPE = 9,
    NETWORKERROR = 10,
    UNKNOWNERROR = 11
} THIRDPARTYLOGIN_RECEIVE_TYPE;

Please provide any other relevant information.

+1

@dev-jaylim
Hi, there
here is Solution.
step 1. open AppDelgate.mm
step 2. find line "import AppsFlyerLib.h"
step 3. fix it to the content below
#if __has_include(<AppsFlyerLib/AppsFlyerLib.h>) // from Pod #import <AppsFlyerLib/AppsFlyerLib.h> #else #import "AppsFlyerLib.h" #endif


Is it possible to test a Model-to-Model services in a dataflow e.g. batch snapshots, stream?

Model-to-Model services are specified and tested as a unit, they may be used as a node in a dataflow pipeline but the scope of their test is to validate the composed function in terms of input and output.


BE noise floor should be a 2D dataset and should come with its own spectroscopic datasets

Turn the 3D complex dataset into a 2D compound dataset where each element contains a complex noise value

Change made in BEODF, BEPSNDF, and BEODF_Relaxation translators.  ODF and NDF translators have been tested and are working correctly.  I did not have any relaxation datasets handy, so I haven't yet tested the relaxation translator.  It should work since that part of the code is copied directly from the ODF translator.


Feature/vsphere containerlinux

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #184
Special notes for your reviewer:

Turned out to be a a bit more challenging than "just put the template there".
PTAL @mrIncompetent @p0lyn0mial

@mrIncompetent @p0lyn0mial PTAL, sorry for the feature creep regarding e2e fixups


Can we set since parameter with format YYYY-MM-DD HH:MM:SS or YYYY-MM-DD HH:MM  ?

I tested this option and it does not properly work.
Here is the log link
The log did not properly worked either, so here is the command line query:
python Exporter.py --querysearch "europe refugees" --maxtweets 1000 --since 2018-02-21 18:00:00 --debug > debug.log

Since Twitter changed something on their side it is not possible to specify time in --since and --until parameters anymore.

Not even with the format YY-MM-DD ?
Thanks for all your help!

Only YYYY-MM-DD

Ok Thanks a lot!
the script is being a great help!


RainLoop creates new folders

After upgrading RainLoop from version <IP_ADDRESS>1 to <IP_ADDRESS>1 and newer (also <IP_ADDRESS>4) some folders ("Archive", "Drafts", "Spam") were created in my mail-account. If I delete this folders, RainLoop  creates they again.
I think the cause are my self-defined Systems-Folders (Sent -> "Sent", Drafts -> "Entwuerfe", Spam -> "Junk", Trash -> "Trash", Archive -> "Do not use").

Thanks!
It was a bug. It will be fixed in the next release.


Propagate mif to consumer2

Description
Changes proposed in this pull request:

Make TestVlad_CheckNATSSubscriptionsCount as simple as possible
Refactor string error to error which can be used by API users via errors.Is()

Related issue(s)

I really like it


[DO NOT MERGE] Update opposite sex guidance for France

This adds in links to the prove eligibility service. It is basically a copy of https://github.com/alphagov/smart-answers/pull/4783 but not done from a fork, this will keep ci happy.

@JonathanHallam Whats the status of this PR?

hey @theseanything just waiting on approval from FCO

Closing as approval was not forthcoming. Will re-open if needed

Closing as approval was not forthcoming. Will re-open if needed


Bypass 5 second delay

In fact, if you rename the efi file that needs to be executed to EFI/Boot/BootX64.efi, you can solve the problem that there will be a 5-second delay at startup. In this case, startup.nsh is unnecessary .

@Richard-W cc

Hi,
Sorry for the long delay. I am aware that this works but opted to not go that route because using startup.nsh drops you into an EFI shell after the application exits which can be quite useful for diagnostics. You can also get around the 5 second delay by hitting return.
If you add this behind a command-line switch like --boot I am willing to accept this.

review request

bors r+

merged. Thank you for your contribution. I will soon release version 0.6.0 which will contain these changes.


Invalid operators priority

I can't tell what this changes...

I think it just changes to order, to have it sorted on priority  (?)

Go for it

It seems the travis error is irrelevant. Hope that the markup is correct.
Should fix HaxeFoundation/haxe#7070

You should run the converter to see if the markup looks good.

@Simn have only same problem as current file version :)
https://gist.github.com/RblSb/f27361af31103de924cb853783b12c00
https://github.com/HaxeFoundation/HaxeManual/blob/master/output/HaxeManual/website/types-numeric-operators.md

Yeah I still don't know why that happens...


Local file: at which path does the plugin look for files by default?

I'm looking to run this locally and so am trying to mount my csv file to the Docker container such that it is available to the Grafana server. I have tried various paths in place of WHERE? but I haven't succeeded in finding the right path. Is it home, data, plugins?
docker run --rm --name grafana -p 3000:3000 -e GF_INSTALL_PLUGINS=marcusolsson-csv-datasource -v $PWD/:/WHERE?/ grafana/grafana:7.5.2

installing marcusolsson-csv-datasource @ 0.4.1
from: https://grafana.com/api/plugins/marcusolsson-csv-datasource/versions/0.4.1/download
into: /var/lib/grafana/plugins

✔ Installed marcusolsson-csv-datasource successfully

Restart grafana after installing plugins . <service grafana-server restart>
...
t=2021-04-15T20:48:08+0000 lvl=info msg="Path Home" logger=settings path=/usr/share/grafana
t=2021-04-15T20:48:08+0000 lvl=info msg="Path Data" logger=settings path=/var/lib/grafana
t=2021-04-15T20:48:08+0000 lvl=info msg="Path Logs" logger=settings path=/var/log/grafana
t=2021-04-15T20:48:08+0000 lvl=info msg="Path Plugins" logger=settings path=/var/lib/grafana/plugins
t=2021-04-15T20:48:08+0000 lvl=info msg="Path Provisioning" logger=settings path=/etc/grafana/provisioning
....

Ah I somehow missed the /docker folder in this repo. From there I could debug. So it loads from / so if I mount my $PWD with csv.csv to /opt/testdata I should put a path of /opt/testdata/csv.csv


✨ [REQUEST] iSponsorBlockTV: Same as CastSponsorSkip but with support for Youtube TV clients (so not limited to casting only).

Checked

[X] If a new addon, I have checked on  Google that such as addon doesn't already exists
[X] If a new feature, I have searched in the discussions & issues that it was not already covered

Which addon?
iSponsorBlockTV
Is your feature request related to a problem? Please describe
Currently CastSponsorSkip is limited to only devices which are Casting youtube. This addons should in theory allow the same for youtube apps such as the ones in an Android TV or smartTVs.
Describe the solution you'd like
https://github.com/dmunozv04/iSponsorBlockTV/wiki/Installation
Thanks!

Have you tried this: https://github.com/bertybuttface/addons/tree/main/isponsorblocktv ?

Have you tried this: https://github.com/bertybuttface/addons/tree/main/isponsorblocktv ?

Didn't find it before! I'll take a look and let you know . Hopefully no need to duplicate it.
Thanks!

No worries, also be aware of https://github.com/yuliskov/SmartTube which you can side load on android tv things to have it natively. This isponserblocktv repo is python based and there for a bit more resource intensive than castsponserskip.

At the moment I'm trying that one, with honestly good results, but I would prefer to have something compatible with the default app so it can scale across devices.

Hello! CastSponsorSkip dev here. I wanted to chime in and mention that CastSponsorSkip seems to work fine for Google/Android TV. I have an NVIDIA Shield, and when I play a video on the YouTube app, it behaves as if the video was cast, even though I opened the app and played the video with the remote.

Add

I tried that but the add-on won't detect my YouTube app in Nvidia shield (2017). With my Chromecast it just works fine. Do I need to create a YouTube API key or something? What about subnets?
2024/01/26 11:52:40 INFO CastSponsorSkip v0.7.0 (688f922)
2024/01/26 11:52:40 INFO Searching for devices...
2024/01/26 11:52:40 INFO Connected to cast device. device="Chromecast"

@alexbelgium I'm trying to set some Environment variables for the CastSponsorSkip integration that aren't exposed in the UI. However, the addon_config folder for it is not created. I trie dmanually creating the folder and adding the config.yaml file as the others but the variables are not being picke dup https://github.com/alexbelgium/hassio-addons/wiki/Add‐ons-feature-:-add-env-variables
Could you check if the config.yaml file is picked up for this one, or otherwise, add to the Addons UI the available parameters for the addon ? https://github.com/gabe565/CastSponsorSkip/blob/main/docs/castsponsorskip.md
In particular, I was trying to modify the CSS_DEVICES to manually reference my Nvidia Shield and test if it works, and CSS_LOG_LEVEL to troubleshoot it.
Thanks!

I tried that but the add-on won't detect my YouTube app in Nvidia shield (2017). With my Chromecast it just works fine. Do I need to create a YouTube API key or something? What about subnets?

@diamant-x I'd love to help out but don't want this thread to get too off-topic. Would you mind posting this in gabe565/castsponsorskip#46

Hello, I'll add the mapping of the config folder ; this should allow you to use indeed by embedded env injection system :-)

Hello, I'll add the mapping of the config folder ; this should allow you to use indeed by embedded env injection system :-)

Wow that was fast, thanks!!
config file now working. Will try some and open up a ticket in the other repo to avoid spamming this one, hopefully my original op is no longer needed if this already support native Android TV Youtybe app.


Dataset

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMDet3D.
The documentation has been modified accordingly, like docstring or example tutorials.

mmseg 쪽에서 처리했네요

@Younghoon-Lee 풀리퀘를 이제야 봤네요
어제 merge까지 되었습니다 ㅋㅋ

ㅋㅋㅋ 네 봤어요 경민님 연락처좀 알려주세요

안그래도 저도 갑자기 슬랙이 끊겨서 ㅋㅋ
<EMAIL_ADDRESS>메일한번만 주세요


Add post on font-variation-settings

Not really sure if it's a common mistake, but I ran across it in my colleagues' code and thought it might be relevant.
Also, there's an issue with beautifier: it removes some necessary spaces in code.

Hi! thanks for contributing!
I have to check how "common" this issue is, and if this the right solution for it :) Will take some time, because I'm not accepting posts at the moment (got way too many in my backlog).

Ignore what I said, I'll merge this! :)


Change to ipex-llm

All files are updated, except the following part which not quite sure whether need to change. Do you have any suggestions? @glorysdj

https://github.com/intel-analytics/bigdl-llm-tutorial/blob/main/ch_2_Environment_Setup/README.md#2213-windows-subsystem-for-linux-wsl: provide link in bigdl document to demonstrate WSL2 installation

https://github.com/intel-analytics/bigdl-llm-tutorial/blob/main/ch_8_AppDev_Advanced/8_LangChain_Integrations.ipynb: In '8.4 Question Answering over Docs', we use BigDL document to input and illustrate results.

All files are updated, except the following part which not quite sure whether need to change. Do you have any suggestions? @glorysdj

https://github.com/intel-analytics/bigdl-llm-tutorial/blob/main/ch_2_Environment_Setup/README.md#2213-windows-subsystem-for-linux-wsl: provide link in bigdl document to demonstrate WSL2 installation
https://github.com/intel-analytics/bigdl-llm-tutorial/blob/main/ch_8_AppDev_Advanced/8_LangChain_Integrations.ipynb: In '8.4 Question Answering over Docs', we use BigDL document to input and illustrate results.

please use bigdl-llm document for WSL install and as the input for now.


BluetoothGATTSetCharacteristicValue broken code example

https://docs.microsoft.com/en-us/windows/win32/api/bluetoothleapis/nf-bluetoothleapis-bluetoothgattsetcharacteristicvalue
The code example treats the Data field as a pointer and assigns to it. This just does not want to compile.
To my understanding, the structure should be treated as open-ended, by first allocating more memory and then copying your data into the location starting with Data

@drewbatgit FYI


Add missing mods to facilitate synthetic data use

clinicadl tsvtool getlabels needs a missing_mods directory in order to work, and this was not generated by clinicadl generate. It will once this PR is merged.

Seems to be ready for merge!


Allow setting security context for vault and etcd pods

A k8s cluster can have admission control policies that can restrict the allowed pod security policy.
The vault-operator should allow a user to set the pod security policy for a vault cluster's pods via the PodPolicy field.
https://github.com/coreos-inc/vault-operator/blob/master/pkg/apis/vault/v1alpha1/types.go#L79
Similarly for the EtcdCluster created by the vault-operator for a vault cluster, the PodSecurityPolicy should be configurable through the VaultService CR.
https://github.com/coreos/etcd-operator/releases/tag/v0.9.2

You should see if you can make it work for dynamic UIDs too: https://docs.openshift.org/latest/creating_images/guidelines.html#openshift-specific-guidelines. Though, due to mounts in vanilla k8s, this is generally hard to make work without also setting fsGroup to 0 by default (in my experience).


Unable to start

I've downloaded docker and essential parts. And have put the crypto signal on my desktop. Then openend cmd and pasted the next code: docker run --rm -v $(pwd)/config.yml:/app/config.yml shadowreaver/crypto-signal:master
I get the message: unable to find image 'shadowreaver/crypto-signal:master' locally
master: pulling from shadowreaver/crypto-signal
docker: image operating system "linux" cannot be used on this platform.
See "docker run --help".
I'm using windows 10 pro.

The linex error is gone, but the cryptosignal:master image still can't be located.

The repo with the docker image is public https://hub.docker.com/r/shadowreaver/crypto-signal/, so without further details of your issue I have no way of helping you.


mesa: Drop _git from recipe name

This matches with OE-core, recently dropping _git from the mesa recipe name

Truck

Thank you!


Compatibility with Accessories

Is your feature request related to a problem? Please describe.
Doesn't appear to save equipped Accessories/Trinkets on death
Describe the feature you would like to see.
Compatibility like that of trinkets, I've only tested this with the 1.20.1 version as that's the current modpack in testing.
Additional context
Mod: https://modrinth.com/mod/accessories
When testing this in the modpack I get
[10:28:20] [Render thread/INFO]: [System] [CHAT] A5ho9999 fell from a high place
[10:28:20] [Render thread/INFO]: [System] [CHAT] [G] Grave spawned at -5028x 67y 1094z.
[10:28:20] [Render thread/ERROR]: Unable to Sync Container Data for a given Entity as it is null on the Client! [EntityId: 72]

but when just testing with the graves and accessories no errors are logged but the slots/equipped items still aren't saved.

Hey, thanks for the report! I can definitely look into adding support for Accessories at some point. I can't promise a specific timeline, though.
I've done some basic playing around with the two mods and accessories-tc-layer. It seems like the items will simply drop if the compatibility layer isn't installed.. but if it is, any items in the cosmetic slots will be restored properly while any item in the regular slots will be destroyed.
I might be able to whip something up to at least prevent the items from outright being destroyed while the compatibility layer is installed.

Alright, v3.2.17 has been released. If you run into any issues with the compatibility layer installed and with items being deleted please let me know (especially which items are being deleted and from what mod). If the compatibility layer isn't installed the items should simply drop on the ground, so vanilla rules will apply there (they'll despawn, etc).
I'll try and look into adding dedicated support at some point, but it might be weird since I'll have to consider the compatibility layer(s) as well as the main mod. Thanks again for the report!

Thanks for the quick work, seems like it's fixed but will double check once the server has also been updated (and for someone to die naturally).


bug: cannot pop any floating window with keybind

Did you check docs and existing issues?

[X] I have read all the snacks.nvim docs
[X] I have updated the plugin to the latest version before submitting this issue
[X] I have searched the existing issues of snacks.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.2
Operating system/version
nixos 24.11
Describe the bug
A keymap defined with expr = true to run lua functions results in the below error.
E5108: Error executing lua: ...ir/pack/myNeovimPackages/start/snacks/lua/snacks/win.lua:339: E565: Not all
owed to change text or change window
stack traceback:
        [C]: in function 'nvim_open_win'
        ...ir/pack/myNeovimPackages/start/snacks/lua/snacks/win.lua:339: in function 'open_win'
        ...ir/pack/myNeovimPackages/start/snacks/lua/snacks/win.lua:433: in function 'show'
        ...ir/pack/myNeovimPackages/start/snacks/lua/snacks/win.lua:214: in function 'win'
        ...cial-rtp-entry-LuaConfig/lua/myLuaConf/opts_and_keys.lua:158: in function <...cial-rtp-entry-Lu
aConfig/lua/myLuaConf/opts_and_keys.lua:157>

:lua Snacks.lazygit() works as expected without any error.
Steps To Reproduce

Enable vim.keymap.set("n", "<leader>gg", function() Snacks.lazygit() end, { expr = true, desc = "Lazygit" })
Press keymap

Expected Behavior
Launch floating terminal with lazygit (or other tool/buffer)
Repro
No response

What's your use-case to use expr=true here?

You need to vim.schedule that call to create a window. expression keymaps can't alter the editor state.

Or just don't use expr=true?

Thanks for looking at this. I added the expr because I found it in :help vim.keymap.set() while hunting down another error with the keymap. That made it stop erroring on nvim startup, so I thought I'd solved the bug in my config. I apologize, I think I got myself mixed up between errors. Removing the expr=true now works as expected, so I definitely chased a red herring somewhere.

expr=true is for keymaps that return a string to be executed as the keymap.


Implement "show followers/following around the world in percentagewise distribution"

This kind of feature can be viewed at different services e.g. https://tweepsmap.com/Map

@Orbiter Is there a way loklak_server can relate a place name to a Country. For ex Berlin-->Germany , Delhi-->India

right now I have the ISO-3166 2-letter country code available in my data set. I am currently looking for a  ISO-3166 -to- geolocation table so that I could send you a coordinate where you can plot the accumulated info to.
To access this information efficiently, you would need to make an aggregation search on the (to-be-implemented)  ISO-3166 field in the search index which I would enrich with location coordinates in the aggregation result. Would that be a solution for you?

I am looking for something like https://github.com/loklak/loklak_server/issues/62 where along with the location name you add the name of the country to the response
{"locations":{"Singapore":{"place":["Singapore"],"population":3547809,"location":[103.85006699890363,1.2896698812440377],"mark":[103.85006699890363,1.2896698812440377]},"New York":{"place":["New York City"],"country":"USA",population":8175133,"location":[-74.00596630480419,40.71427148800075],"mark":[-74.00596630480419,40.71427148800075]}}

ok, I already added the field place_country and place_country_center to search results. The country can also be retrieved with aggregations, like:
http://loklak.org/api/search.json?q=/location&source=cache&fields=place_country&limit=6&count=0

This gives you aggregations for the countries but not the country name and not the country center location. I try to find a solution for that in the fashion you suggested above.

Thanks

please retrieve the follower list from loklak_server, documentation is online at http://loklak.org/api.html#account .. please scroll down to "Retrieval of Twitter User Account Data" for details

This issue was closed automatically through your commit, but I do not see it solved on live.

@mariobehling #311 is similar issue.So I have moved it there.
On Aug 13, 2015 1:30 PM, "Mario Behling"<EMAIL_ADDRESS>wrote:

This issue was closed automatically through your commit, but I do not see
it solved on live.
—
Reply to this email directly or view it on GitHub
https://github.com/loklak/loklak_webclient/issues/296#issuecomment-130569102
.


cannot create project via yaml file

no error message is displayed when creating a Project.
With the parameters a Project can be created

so to be exactly: create a project with:
cloudctl project apply -f project.yaml

fails without an error, but:
cloudctl project create --name --tenant

works ?

I can reproduce this as well. But I also think that project creation never worked before via apply.
Looks like we do not respect the case when the id of a project is empty (which means: create a new project and do not update): https://github.com/fi-ts/cloudctl/blob/v0.8.3/cmd/project.go#L249-L250
Instead, we are just doing a GET with an empty string of the ID, which leads to effectively executing a cluster list request:
DEBUG=1 c project apply -f project.yaml                                                                           13:07:23
GET /cloud/v1/project/ HTTP/1.1
Host: api.metal-pod.dev
User-Agent: Go-http-client/1.1
Accept: application/json
...
HTTP/2.0 200 OK
Content-Type: application/json
Date: Wed, 14 Oct 2020 11:08:42 GMT
Server: nginx/1.17.8
Strict-Transport-Security: max-age=15724800; includeSubDomains
Vary: Accept-Encoding

{
 "projects": [
  {
   "meta": {
...

I guess, we did not cover this case because when you apply requests without id in a row, you are creating a lot of projects...

I can reproduce this as well. But I also think that project creation never worked before via apply.
Looks like we do not respect the case when the id of a project is empty (which means: create a new project and do not update): https://github.com/fi-ts/cloudctl/blob/v0.8.3/cmd/project.go#L249-L250
Instead, we are just doing a GET with an empty string of the ID, which leads to effectively executing a cluster list request:
DEBUG=1 c project apply -f project.yaml                                                                           13:07:23
GET /cloud/v1/project/ HTTP/1.1
Host: api.metal-pod.dev
User-Agent: Go-http-client/1.1
Accept: application/json
...
HTTP/2.0 200 OK
Content-Type: application/json
Date: Wed, 14 Oct 2020 11:08:42 GMT
Server: nginx/1.17.8
Strict-Transport-Security: max-age=15724800; includeSubDomains
Vary: Accept-Encoding

{
 "projects": [
  {
   "meta": {
...

the creation via file has definitely worked already.


Return Never in Option "or" closure

Added

Optional

Added unwrapped(or error: Error) to get the wrapped value of an optional. If the optional is nil, calls Never-returning closure.

Note: I didn't add tests since all the assertions shouldn't be by default in production code. Also I know only one tough way to implement global default Never returning functions replacement in order to organise proper testing of ones. The other option is to use 3rd party library with similar testing abilities. Feel free to comment and propose more suitable solutions if possible.
Checklist

[x] I checked the Contributing Guidelines before creating this request.
[x] New extensions are written in Swift 5.0.
[x] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
[ ] I have added tests for new extensions, and they passed.
[x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[x] All extensions are declared as public.
[x] I have added a changelog entry describing my changes.

          1 Warning

:warning:
Consider adding tests for new extensions or updating existing tests for a modified SwifterSwift extension

          4 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 626 tests, with 0 failures (0 unexpected) in 10.813 (12.766) seconds

:book:
tvOS: Executed 595 tests, with 0 failures (0 unexpected) in 1.658 (2.077) seconds

:book:
macOS: Executed 458 tests, with 0 failures (0 unexpected) in 0.664 (0.870) seconds

  Generated by :no_entry_sign: Danger

@DimaZava can you please try add some tests?

@guykogus I didn't add tests since all the assertions shouldn't be by default in production code. Also I know only one tough way to implement global default Never returning functions replacement in order to organise proper testing of ones. The other option is to use 3rd party library with similar testing abilities. Feel free to comment and propose more suitable solutions if possible.

If anything I think that this extension makes error handling worse. When you're calling a Never function it's because you've hit a dead end and want to exit the function (or the entire program, probably). If you think of the examples where this generally happens with optionals, you have something like:
func tableView(_ tableView: UITableView, cellForRowAt indexPath: IndexPath) -> UITableViewCell {
    guard let cell = tableView.dequeueReusableCell(withIdentifier: "identifier", for: indexPath) as? MyTableViewCell else {
        preconditionFailure()
    }
    cell.foo()
    return cell
}

In this function the return value is non-optional, so if you use this extension you still need to handle the unwrapping.
func tableView(_ tableView: UITableView, cellForRowAt indexPath: IndexPath) -> UITableViewCell {
    let cell = tableView.dequeueReusableCell(withIdentifier: "identifier", for: indexPath) as? MyTableViewCell
    cell.or { preconditionFailure() }
    cell!.foo()
    return cell!
}

The built-in language features for handling this scenario are far better. I can't see a scenario in which the new extension would be preferred. @DimaZava can you suggest any scenario where the extension is preferred?

I think its safe to say that this one could be closed :) But @DimaZava if you still have some points to discuss feel free to re-open it 👍


quic: propagate default network change event to upstream connections

Commit Message: Upon default network changes on devices, existing QUIC connections should be closed or drained depending on whether it is idle or not (having in-flight requests). Draining the non-idle connection is needed before E-M is able to migrate those connections to the new default network to avoid TOO_MANY_RTO error on them later. This PR does the necessary plumbing to pass the network change event from ConnectivityManager to EnvoyQuicClientSession and H3 conn_pool for them to act upon.
Additional Description: Introduce a new classes QuicNetworkConnectivityObserver and EnvoyQuicNetworkObserverRegistry/EnvoyQuicNetworkObserverRegistryFactory in Envoy to register each QUIC connection. And extends EnvoyQuicNetworkObserverRegistry in mobile to propagate network change events to each connections.
Risk Level: high, change upstream QUIC connection lifetime
Testing: new e2e and unit tests
Docs Changes: N/A
Release Notes: Yes
Platform Specific Features: enabled only on Android
Runtime guard: envoy_reloadable_features_quic_upstream_connection_handle_network_change

/retest

/retest

/retest

/assign @RyanTheOptimist

/retest

/retest

/wait

I split the  mechanical plumbing of register and register factory into the https://github.com/envoyproxy/envoy/pull/35912.

/retest

Will look later today but why is this QUIC-only?  Shouldn't we have consistent draining for H2 and H1?  if not please update PR description to explain why H3 only.

/retest

sorry coming back to large(r) design questions Now that we agree this needs to be done for all protocols, I'm wondering if we should revisit the approach. Specifically we already have a function cluster_manager_.drainConnections which we call on onDnsResolutionComplete, iff we think the dns resolution was due to a network change and enable_drain_post_dns_refresh_ is true I suggest instead of adding a second parallel mechanism we revisit/adapt the existing mechanism, or add a second cluster manager method if we need two (one on network change, one on DNS resolution complete)

I thought about this before. We would need to add 4 new interfaces for network changes corresponding to the 4 Android NetworkCallback methods that we are interested in (onAvailable(), onCapabilitiesChanged(), onLosing(), onLost()) and plumb them thru cluster manager runOnAllThread() all the way to connections if we were to follow the same pattern of drainConnections(). Iteration on the interfaces changes will be a pain. Instead of the massive plumbing, the new approach is passing down a registry in the same way as cluster_manager_.drainConnections() and handles these network change callbacks within the mobile's own implementation of the registry and thus less Envoy core code modification once the registry is plumbed through.

Mmm, I hear that, but I think doing a registry per protocol is as complicated, and much less clear to understand what's going on.  Also would we need four functions or one function with an enum indicating what change took place?  it's not like we have a onReadEvent onWriteEvent onReadWriteEvent onCloseEvent for fds.    Ryan, thoughts on pros and cons of the two approaches?
/wait-any

Offline, sounds like we could get away with one non-quic-specific registry.  I think my take-away from a conversation with Ryan is I want to wait on the design doc before proceeding with this review =P
/wait