:green_heart: Only trigger CI when relevant code changes

https://docs.github.com/en/actions/learn-github-actions/workflow-syntax-for-github-actions#onpushpull_requestpaths
Auto merge is enabled - Squashing commits.

I think we should only disable CODECOV results when no code has been changed. I think running the normal tests on dependabot changes is valuable.
We should also run them on releases..

Oh yes, fully agree, dependabot will now indeed not run the ci.
Should we really go into complicating the pipeline to skip codecov after all? What will we win there?


Create property annotations for objects

Your examples suggest using magic setters to set property values on objects:
$card = new VCard();
$card->FN = "John Doe";

But those properties are not documented in code. You have to read your documentation or the RFC while developing to find the properties you wanna use.
I'd suggest adding @property annotations to ease use of the different object classes (http://phpdoc.org/docs/latest/references/phpdoc/tags/property.html).

This was brought up earlier in #234
There's a lot of problems with it though:

In that PR many properties were incorrect in that context. Not every component can have any property.
Also, properties can often be specified as strings or arrays when setting them. The PR suggest that they have to be their respective components which is only usually true when getting them.
Many properties can actually be of a different class when the VALUE parameter is specified.
Also keep in mind that you can basically set any property, not just the ones from the RFC's. The RFC properties are just the standard ones.

And lastly, it will be quite frustrating to maintain such a massive list. If you have ideas on how to solve this better, I would love to hear it.
To me it's just a bit of a frustrating exercise. I don't really see the benefit because I don't use IDE's that take advantage of this. However, I can be persuaded if you have a great approach to tackling this problem =)

No response received. Closing this until there's a better suggested approach.


Build Failures on jqf:fuzz and jqf:repro

I am attempting to fuzz the Google Closure Compiler with Zest but when I use
mvn jqf:fuzz -Dclass=examples.CompilerTest -Dmethod=testWithGenerator -Dtime=5m
I am getting a BUILD FAILURE as shown in the image.

I am also getting a BUILD FAILURE when I attempt the following -
mvn jqf:repro -Dclass=examples.CompilerTest -Dmethod=testWithGenerator

Any help would be greatly appreciated, thanks

Hey! This looks fine. The error messages seem to reveal what's going on.
For the first command, it looks like fuzzing completed after the 5min timeout and found a failure (i.e., an input that triggered an uncaught exception in the Closure Compiler). Did you see the Zest status screen for five minutes? When the timeout expires, the plugin signals "failure" if any errors were found, this is similar to when you run mvn test and some test fails. If you don't want to see Maven failures when Zest finds a bug, then avoid giving the -Dtime option and just kill the process after 5min (e.g. using CTRL+C or your system's native timeout command). Killing the process will cause the fuzzing to stop silently.
For the second command, the error message indicates that you have not provided an input whose execution you want to reproduce. Use -Dinput=<file> where <file> is an input saved in the results directory (e.g. in corpus or failures). The tutorial shows an example of this usage.
Hope this helps.

Thank you for your speedy response to my query. As a newcomer to fuzzing and JQF with Zest, I panicked when I seen "Build Failure" and assumed I was doing something wrong. Thanks for your help, I have got it working now.

Thanks for your speedy response to my query. As someone who is new to fuzzing and JQF with Zest, I panicked when I seen "Build Failure". Thanks for your help, I have got it working now.


Describe Container Apps Security & Hardening

Describe Container Apps Security & Hardening :

cluster isolation : single Tenant see also 57
equivalent of network policies , etc.
Support policy - see #25

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9b2a1180-bdef-3f45-f478-9969aff2649a
Version Independent ID: 79ab35ad-295a-ef8f-3228-91158dd2c960
Content: Azure Container Apps - Frequently asked questions
Content Source: articles/container-apps/faq.yml
Service: static-web-apps
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

@RyanHill-MSFT - please remove static-web-apps/svc (and craig) from this issue as it is for ACA, not SWA.


Save WASM state and resume

Feature
To be able to interrupt and save the state of executing WASM code and then resume it later, possibly on a different host machine.
Benefit
I am writing an add on for the Open Computers mod in Minecraft. The mod adds tiny computers that can be programmed by the player. One of their features is that if you quit the game, when you resume later, the state of the machine is restored just as they left it.
The default Lua interpreter uses a custom implementation of Lua that can save and restore its state like this.
There's a small hand full of emulators that just save their memory and registers and restore them later.
I don't see a clear way to do this with wasmtime.
I do see potential in this being useful for a tool similar to Jupyter. You could pause a computationally intensive task and resume it later, or a cloud could serialize a job, and send it to another machine to resume in the case of a scale up/down.
Implementation
I can see that modules can be serialized already. What really needs to be saved is the state of memory and execution.
Just dumping the memory into a byte array will be enough to save the memory. Saving the state is what looks hard to me.
Dumping the registers to be restored later could work for a non-portable solution but something that can be restored on another machine of possibly a different architecture would be preferred.
Unfortunately I don't know enough about wasmtime's implementation to give a fantastic recommendation here.
Alternatives
This is actually my fallback plan if the feature is rejected.
If you can just serialize the memory of the WASM environment (actually this may already be possible, I just haven't tried yet) you could push the job of tracking state off onto a Rust module's async state machine. You would need a function that is called regularly to resume this state machine and the module would need to frequently interrupt itself so that this function can return to the host.
The advantage here is that you don't need to worry about any kind of register. Saving the state is handled by the async state machine and you can just call that one function to run the state machine to resume the guest application.
The disadvantage is that this is really only practical if the web assembly is written in Rust, and the person writing this Rust code must correctly write an async application.

To be able to interrupt and save the state of executing WASM code and then resume it later, possibly on a different host machine.

The on a different host machine will require pessimizing optimizations such that between every instruction all locals and the full stack is known as different backends may optimize instructions in different ways and thus require different information to at a given point continue running. This will probably a significant perf hit. Alternatively interrupting could be limited to certain safepoints, allowing a much smaller perf hit.

The default Lua interpreter uses a custom implementation of Lua that can save and restore its state like this.

It is much easier to implement this in an interpreter than a compiler as an interpreter needs to keep all state, while a compiler will "forget" about state as soon as possible to reduce register pressure and will try to fold instructions together (and thus allow forgetting about certain locals) or mangle them in different ways.

The on a different host machine will require pessimizing optimizations such that between every instruction all locals and the full stack is known as different backends may optimize instructions in different ways and thus require different information to at a given point continue running. This will probably a significant perf hit.

I was worried that would be the problem.

Alternatively interrupting could be limited to certain safepoints, allowing a much smaller perf hit.

I could easily trick the user into having regular safe points by requiring them to regularly check into something like a watch dog timer. How would you suggest saving the state at these safe points?

How would you suggest saving the state at these safe points?

That will still require changes to Cranelift to allow for saving the state and restoring at such a safe point. The changes are just easier and with less of a perf hit than allowing it at arbitrary points.

@IamTheCarl thanks for starting this conversation -- it's a really interesting one!
I'm curious what sort of state-saves are actually necessary. As @bjorn3 says, very general snapshotting at arbitrary points is expensive; if we needed to do something like that, probably the better way would be to just save the registers, heap and stack, ensure we restore into the same generated code (this has limits wrt CPU features too, as mentioned above), and take care to make the stack and register file "relocatable", in the sense that they can be fixed up for other heap-base addresses on restore. (Some thoughts on that: to do so, probably the easiest way would be to tweak codegen so that the heap base always lives in one pinned register, and any address computation uses that as part of its address expression, so we never have intermediate pointers in registers or spilled to stack. Then we just have to fix up frame pointers and return-area pointers on the stack.)
But there's a potentially much easier way: could we get away with only snapshotting when no Wasm frame is on the stack? In other words, when a call into the Wasm has returned all the way out? If so, then we don't have to worry about register or stack state at all; we can just snapshot the heap and globals. We could even restore with different generated code, on a different architecture or just with different CPU features.
This is sort of like what Wizer does, so that's probably the place to look for more ideas. cc @fitzgen for more thoughts!

That does sound a bit like my alternative solution.
The idea was to regularly call a function that would let the guest run for a short bit and then return shortly after. It would be up to the developer of the guest code to keep track of the state between calls.
This is inconvenient for the guest developer, since they need to write an application that can run in such an environment (some global mutable variables will be needed). In Rust, using async can make this pretty intuitive, but other languages like C would require they manually build their own state machine.
Of course if we're taking it that far I could then even push off the job of serialization to the guest code. Just send it some kind of event "shutdown now or you'll be force terminated" and that'll give them just a moment to save their state before shutdown. This one is so simple to implement that wasmtime wouldn't even need any modifications, but it is also the most inconvenient for the developer of guest code.

This is sort of like what Wizer does, so that's probably the place to look for more ideas. cc @fitzgen for more thoughts!

Yeah, saving state without frames on the stack is pretty easy, and as Wizer shows, you don't even need to build that functionality into the engine itself, you can do it with the standard reflection APIs that engines expose and use Wasm itself as your snapshot format. You could even factor out the code from the data (snapshot) and make it so that you don't need to recompile the code for each snapshot, just reuse the already-compiled module from before and pass in new memory/globals for its imports.
Binaryen's asyncify pass can help turn synchronous code into asynchronous code. If my understanding is correct, it lifts frame activations and their local values into linear memory and does some kind of CPS-esque transformation on the code. It might make assumptions about the Web or that you're also using Emscripten; not sure, I haven't actually used it. This might be one way to transform the Wasm so that code can be written synchronously but still make snapshotting with zero activations on the stack viable.

One final thought: snapshotting at ~gc safe points could be made possible relatively easily if we spill all registers at safe points. This would be a config option, because we wouldn't want to do this unconditionally. But if we only have to capture and restore stack values, that seems like a much easier problem. Hard part is addressing native pointers. I don't have any good ideas here, but I think you may have some, @cfallin.

I think you may have some, @cfallin.

Indeed! This is the bit about "no intermediate pointers in registers or the stack" alluded to above. To add a bit more detail, just to get this written down:

We need to be a little careful in legalization: where we have loads/stores that decompose into either heap_addr or stack_addr and a native-pointer load/store, we need to at least keep the ops close in the CLIF so that they can be pattern-matched, or ideally do codegen directly on the heap/stack-level ops without decomposing them.
The goal is to turn every Wasm heap access into e.g. ld rA, [rBase + rB] where rB is a 32-bit Wasm pointer, and rBase is a fixed register that we decide and make non-allocatable. We make this part of an internal Wasmtime ABI, and set it before calling into Wasm. (This implies a little care taken w.r.t. hostcalls too but that's manageable I think.)
Similarly, every stack-slot access turns into ld rA, [sp + ...]; we never copy sp to another register and compute an address based on it.
We need to tweak the internal ABI to deal with return-area pointers (for multiple return values) slightly differently. Probably we just use a fixed offset from frame at entry, rather than passing an implicit arg with the pointer.
Finally, either codegen without a frame pointer, or be prepared to fix up the frame-pointer chain on relocation.

Given those codegen changes, the code is completely "data-relocatable": the only native-address-space pointers in the register file or on the stack at any time are in sp and rBase. If we set those to different values on Wasm re-start after moving data, we should be just fine.
(Caveat: return addresses; if code is relocated too, probably best to retain frame-pointer chain, rewrite return addresses as relative to module base on snapshot, and re-add the new module base on restore.)
Probably a few weeks' work but would be very useful even beyond this use-case!

This is the bit about "no intermediate pointers in registers or the stack" alluded to above.

Intermediate pointers are fine if they aren't used across a safe point or if it is the vmctx. In the former case they simply wouldn't need to be stored and in the later case the vmctx value can (and should) trivially be replaced with the newly allocated vmctx when loading.

We need to tweak the internal ABI to deal with return-area pointers (for multiple return values) slightly differently. Probably we just use a fixed offset from frame at entry, rather than passing an implicit arg with the pointer.

If this parameter is properly annotated it can be fixed up when loading too by looking at the caller.

Finally, either codegen without a frame pointer, or be prepared to fix up the frame-pointer chain on relocation.

The stack doesn't need to be copied verbatim. Only the known locations of spilled values, explicit stackslots (unused by wasm) and the return value need to be copied. The later can be stored as function index + callsite index.

Probably a few weeks' work but would be very useful even beyond this use-case!

Yeah, might be useful for on stack replacement for eg speculative optimization or going from an interpreter to jitted code.

I am impressed with both the quick reply and eagerness to find solutions in this team.
I'm grateful.
There's a lot of terminology here I'm unfamiliar with, so I'd like to check and make sure I'm following this conversation correctly.
It sounds like your plan at the moment is to take a non-async WASM module and transform it into an async form before it even hits the JIT. I assume this will be implemented somewhere in the IR layer. That's pretty cool.
It also sounds like you're having difficulty knowing how to serialize objects on the heap? I can understand why that would be an issue since you can't depend on getting those same addresses back.
So what comes next?
I'd like to help but I feel I have a lot to catch up on to make a meaningful contribution.

@IamTheCarl it spawned an interesting discussion and one that's timely for other potential uses too, so thank you for starting it!

non-async Wasm module and transform it

Yes, this is probably the "easiest" solution (for some definition of easy) -- as @fitzgen suggested above, the Binaryen toolchain has an asyncify transform that might help turn arbitrary Wasm into something that would work with your "call into and execute a bit of Wasm at a time" approach; between those calls, all you need to save is the Wasm heap and globals, not any in-progress execution state such as registers or stack. I don't know much about this tool but it looks like there's a pretty comprehensive intro blog post here: https://kripken.github.io/blog/wasm/2019/07/16/asyncify.html
The next step after that is to modify Wasmtime itself so that it generates code that allows for snapshotting and restoring, including the in-progress execution state. There are various tradeoffs here involving whether we want to allow restoring on a different machine architecture (hardest), or just with identical JIT'd code (easier); and whether we want to allow arbitrary interruption and checkpoint at any point (hardest, possibly pessimizes codegen), or checkpoint only at certain points, which we're calling "safepoints" above, in reference to some garbage-collector terminology (a bit easier). Anything along these lines though would not be a quick short-term solution for you, so I personally would suggest looking into the asyncify option, or perhaps just defining an execution model where control always returns from your Wasm module periodically.

But there's a potentially much easier way: could we get away with only snapshotting when no Wasm frame is on the stack? In other words, when a call into the Wasm has returned all the way out? If so, then we don't have to worry about register or stack state at all; we can just snapshot the heap and globals.

Does a method to do this currently exist? I'm exploring various wasm runtimes and have been unable to find such a feature supported as of yet. If not, how difficult would it be to implement? I may be able to take a look at it as it seems to be a heavily requested feature.

Isn't that what wizer does?

Ahh silly me - I did a google search on wizer after seeing it mentioned before and came up with a completely different result. But yes it looks like it's quite similar to what I'm looking for. While the caveats don't work for my specific use case, (specifically, not being able to call imported functions), it does provide enough of an idea of how to proceed for now.

Indeed, Wizer came up in the above discussion as well; the main difference in my mind (at least as far as I can remember now) was whether this would be a more generic facility, with an API to snapshot/resume at arbitrary points. Wizer currently runs a wizer.initialize export, and doesn't allow calls to imports (or can allow WASI, as a special case), so it's targeted toward a "precompute some state once" use-case. I imagine it could be extended to be more general, of course!
Interestingly there was a recent PR from @koute (#3691) that did snapshotting as well. The specific use case in that PR should I think be mostly covered by our recent instantiation-time improvements. But if snapshotting in a more general sense continues to arise as a need, at the Wasmtime API level, that could merit more discussion, I suppose.
@RobDavenport I'm curious about your use-case here, on a few axes: (i) do you need continued snapshot/restore (i.e. multiple roundtrips), or just one initial snapshot and then restores from that? And (ii) does it need to be programmatic at the Wasmtime API level, or is a separate tool (e.g. Wizer) usable for you?

Thanks for the question @cfallin , in my case I'm writing something like a game engine and using WASM as my game-logic code. As a need to support rollback multiplayer (like GGPO which is often used in emulators), I need to consistently store the entire state of the game for the past few frames, and, if a mis-prediction is detected, rollback to a confirmed synchronized state and re-simulate the rest of the frames (often more than one!) with the new input up until the current time.
I was actually able to get this working for the most part by following the suggestions in this thread, along with some things from Wizer. Iterating through the instance's exports, cloning the memories and non-const globals, and then just saving them out as a Box<[u8]> via data_unchecked() or as a WASM Value enum along with the related keys.
Loading saved globals is very straightforward and doesn't need any explanation. For memories, doing a copy_from_slice from the snapshot back into the "hot" memory, using the length of the snapshot so the copy function doesn't panic. I believe the snapshot's reserved memory size should always be equal to or less than the "hot" memory, since the WASM's host memory can only grow for a particular instance, and since that snapshot was an actual state the VM was in at one point, the internals should have already allocated enough space for it.
I'm not sure how dangerous this might be since the WASM client script may be allocating or deallocating memory, but I'm under the assumption that since it's all lumped together and already allocated inside the WASM host VM then it should just work unless the instance or store are moved somehow.
So to answer your questions... (i) Yes, multiple trips will be made, however at specific times determined by the host program without any call frames on the stack. These will always be going back in time, though, and then re-simulating and rewriting old snapshots as we progress. (ii) Actually I have no preference, as I was able to do it for my use case mentioned above. The reason I couldn't use Wizer in my case was I needed to allow the WASM code to make callbacks into the host for things like input handling or draw requests.
However, I believe the original requester for this specifically wanted a way to be able to save/resume the WASM state on a fresh application or even potentially another machine. Unfortunately I'm not too familiar with how the internals work so I can't comment on the safety or feasibility of that, as my quick hack is only intended to work with a single module instance, on the same machine, during the same application lifetime.

I'm curious if much work has been done on this.
I have another toy project idea where a feature like this could be useful.
I saw that there now appears to be an async interface for wasmtime which I imagine would be useful for a feature like this.

Not much has changed regarding the fundamentals here since the last comments; Wizer is still the state-of-the-art, and unfortunately we don't have anything built into Wasmtime itself for snapshotting.


write function to return one of the scanned files from a specific building

This will require something like:
get_filename(block, parcel, type, number)
and will provide a filename so that the image can be accessed using that filename:
e.g.,
system.file(package = "mosaic")
Returns:
# The root of package 'mosaic'
[1] "/Library/Frameworks/R.framework/Versions/4.3-x86_64/Resources/library/mosaic"

which can have the pathname `inst/extdata/block_12_parcel_02_map_02.png` or similar appended.

@vnguyen24 @FranciscoJFM02 might you be willing to add his into your tasks for this week's sprint?

this work will need to be coordinated with @arogers24 and @tknightly24: might the four of you find a time for a virtual meeting or check in via GitHub issues?

@vnguyen24 and @FranciscoJFM02 do you have any updates on this front?
I think that this function will be approximately 5-7 lines long (with more potentially if you wanted to check the calling routines, and more importantly, that the file exists).

Here's a first cut at a select_building() function: this includes the filename.
But perhaps the filename should also be given with the absolute pathname (image_path) since that will be needed later. Any thoughts @vnguyen24 and @FranciscoJFM02?
https://github.com/STAT325-S24/HolyokeUrbanRenewal/commit/2f3348d6bc4ac99434a25e9d49a6d6a6b7ed368e

Hi @nicholasjhorton  I'm currently prepping for an exam tomorrow. Would it be ok if I take a lot at the tasks after the exam? Thank you!

That sounds eminently workable. Best wishes for your exam!

Better late than never, the function added with commit: 72a89b506cb303f33b689a1892be53655bf9862f. It can be used to get the intended filename, which can be used to open the file.

Thanks for your work on this front!


[APEXMALHAR-2094] Quantiles operator

Addressing JIRA issue https://issues.apache.org/jira/browse/APEXMALHAR-2094.
Added a new module "sketches" as per https://issues.apache.org/jira/browse/APEXMALHAR-2094?focusedCommentId=15296761. The sketches module will hold sketching algorithms including quantiles sketch.

Hi Sandeep, Can you please rebase your PR once, Your commit message has my commit message as well.

@ilganeli Please review the changes I made in response to your comments.
@DT-Priyanka (I think) I fixed the commit message.

Why have you included the BytesFileOutputOperators ?

You should add a test with this operator in a DAG. See an example here, testCloningAcrossPartitions: https://github.com/ilganeli/incubator-apex-malhar/blob/9483c4583be0e152da29e7ef7512a75afc4f9a09/library/src/test/java/com/datatorrent/lib/partitioner/ClonePartitionerTest.java

@ilganeli My bad: BytesFileOutputOperator was included as a result of a klutzy rebase. I'll get rid of it in my next commit.

Apart from few comments, rest of the changes look good to me.

@sandeep-n Can you please address the outstanding comments and rebase your branch?
The commit message must contain the JIRA id: "APEXMALHAR-2094: added module ..."
I can then merge this.

@bhupeshchawda Please review

@sandeep-n Thanks Sandeep. Will take a look in the next few days.

@sandeep-n You should revive this IMO

closing PR due to inactivity


How to blend the policy networks?

I've trained several SAC  networks with default settings.
Now I wish to blend the networks by defining a set of weights, like a weighted blending.
Just as  this paper does.
It's a simple idea to learn to blend the policies, but I do not know how to correctly extract the policy networks and blend them as expected.

If you only wish to "blend" output actions, you can run action_probability for each separate policy and blend the probabilities manually and pick an action from there. However if you need to blend in network parameters then you need to start modifying network parameters, where you can use get_parameters and load_parameters functions to get network weights and modify them as you please.

If you only wish to "blend" output actions, you can run action_probability for each separate policy and blend the probabilities manually and pick an action from there. However if you need to blend in network parameters then you need to start modifying network parameters, where you can use get_parameters and load_parameters functions to get network weights and modify them as you please.


Optimize rockcraft build

Currently, for each change in the rockcraft repo, we publish the current state of rockcraft files and run tests on them even if files haven’t changed. We need to build only changed files but run tests on all rock images.
The PR updates pushed images after the build to only those modified rocks and also, bump the rockcraft version which fixes the CI build.
KU-1195

merge #14 before


Stop managing memory in max pooling specific manner

This change stops managing memory in max pooling specific manner for reducing memory usage on inference.

Jenkins, test this please.


HBASE-28227 Tables to which Stripe Compaction policy is applied cannot be forced to trigger Major Compaction.

https://issues.apache.org/jira/browse/HBASE-28227

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 45s
Docker mode activated.

-0 :warning:
yetus
0m  3s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 57s
master passed

+1 :green_heart:
compile
0m 49s
master passed

+1 :green_heart:
shadedjars
4m 56s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 25s
master passed

_ Patch Compile Tests _

-1 :x:
mvninstall
1m 37s
root in the patch failed.

-1 :x:
compile
0m 48s
hbase-server in the patch failed.

-0 :warning:
javac
0m 48s
hbase-server in the patch failed.

-1 :x:
shadedjars
3m 43s
patch has 17 errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 25s
the patch passed

_ Other Tests _

-1 :x:
unit
0m 46s
hbase-server in the patch failed.

18m  8s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5589/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/5589

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 384a7318ea2f 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 53e01b23ec

Default Java
Eclipse Adoptium-11.0.17+8

mvninstall
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5589/1/artifact/yetus-jdk11-hadoop3-check/output/patch-mvninstall-root.txt

compile
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5589/1/artifact/yetus-jdk11-hadoop3-check/output/patch-compile-hbase-server.txt

javac
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5589/1/artifact/yetus-jdk11-hadoop3-check/output/patch-compile-hbase-server.txt

shadedjars
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5589/1/artifact/yetus-jdk11-hadoop3-check/output/patch-shadedjars.txt

unit
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5589/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5589/1/testReport/

Max. process+thread count
76 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5589/1/console

versions
git=2.34.1 maven=3.8.6

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 36s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 31s
master passed

+1 :green_heart:
compile
2m 36s
master passed

+1 :green_heart:
checkstyle
0m 36s
master passed

+1 :green_heart:
spotless
0m 45s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
1m 45s
master passed

_ Patch Compile Tests _

-1 :x:
mvninstall
1m 46s
root in the patch failed.

-1 :x:
compile
1m 21s
hbase-server in the patch failed.

-0 :warning:
javac
1m 21s
hbase-server in the patch failed.

-0 :warning:
checkstyle
0m 35s
hbase-server: The patch generated 3 new + 6 unchanged - 0 fixed = 9 total (was 6)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
hadoopcheck
2m 11s
The patch causes 17 errors with Hadoop v3.2.4.

-1 :x:
hadoopcheck
4m  3s
The patch causes 17 errors with Hadoop v3.3.6.

-1 :x:
spotless
0m 35s
patch has 55 errors when running spotless:check, run spotless:apply to fix.

-1 :x:
spotbugs
0m 20s
hbase-server in the patch failed.

The change looks straight forward so in general I think it is OK. Can we add a UT for this change?
And also, I think the forceMajor will only trigger a major compaction in a single stripe, not all the stripes at once. So even if we request major compaction several times, how can we make sure that we will select compaction for different stripes, and finally compaction all the stripes?
Thanks.

The change looks straight forward so in general I think it is OK. Can we add a UT for this change?
And also, I think the forceMajor will only trigger a major compaction in a single stripe, not all the stripes at once. So even if we request major compaction several times, how can we make sure that we will select compaction for different stripes, and finally compaction all the stripes?
Thanks.

Thanks for checking the code, at the moment, after passing the forceMajor parameter, running major compact, will indeed only compress one Stripe.
The situation I'm testing here is that after the stripe count major, the region will be compacted.
If you want to major all the stripes at once, you need to modify the return value of StripeCompactionRequest.
I need to submit the code again and add the test case

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.


Mock the feedback endpoint as well

Hey @TamiTakamiya
Just a minor addition to support the feedback call, can you please add this peace of code?
app.post('/v1/feedback', async (req, res) => {
  const body = req.body;
  console.log(JSON.stringify(body));
  try {
    return res.status(200).send(JSON.stringify("{}"));
  } catch (e) {
    console.error(e);
  }
});

Thanks

@romartin I have updated the code by pushing a commit directly to the main branch :-) I tested the code with curl, but have not run with chabot.


Ghost Apps & the Ghost Developer Kit

Please Note: Apps is the new name for plugins.
The work towards making Ghost apps possible is spread across several issues in several different repositories.
We now have the Ghost-App repository where the app boilerplate is beginning to take shape.
The boilerplate / base structure
First we want to get to the point where we can create an app with the simplest access to Ghost.
Goal: Create an example app that can register a handlebars helper and filter jQuery out from ghost_foot.

App Boilerplate: Do we need .App? and other extendable base apps? Ghost-App#7
Ghost Filters are broken #2157
App Boilerplate: filters ? Ghost-App#6
Ghost Developer Tools 'proxy' object for apps #1478
Publish next version of boilerplate to NPM Now @ 0.0.2
App Boilerplate: proxy object naming and structure https://github.com/TryGhost/Ghost-App/issues/10
App Boilerplate: helpers https://github.com/TryGhost/Ghost-App/issues/14
Docs on apps: Getting Started for Ghost Devs - needs updating when the other work is completed.

App Installation
We want to make it possible to easily install and manage an app
Goal: Users can easily activate and manage apps without touching the database even if the app disappears or is broken.

App management:

Install App Dependencies #2099
Add package.json support for Themes #2081
Apps initial lifecycle and setting screen UI #2083
[Draft] Code up the new App UIs (HTML & Sass) #2065
App installation: permissions modal #2130
Apps additional lifecycle and settings UI #2140
[Draft] Apps wire up the correct install, activate, manage, delete UI #2141

App Error handling:

Non-existent apps cause an unhandled rejection & dies #1829
Handle errors from apps appropriately #2118

App Safety and Security
Users should be able to depend on an app to do what it says. Apps should be able to do things they ask for permission for. We should make it clear what it is and is not acceptable for an app to do.
Goal: To be able to define an app with a set of permissions. The app should get those permissions and be held to them. E.g. permission and ability to edit a post but not delete one.
[TBD: improve goal to be more easily measurable]
[TBD: provide examples for ACL]

Discussion: App Safety & Security #2007
Load Apps Sandboxed #2091
App Permissions #2095
App permissions UI #2101
ACL & the API: Current user everywhere #2058
ACL for Apps #2059
ACL: Add to model-based API methods: posts, tags, users #2060
ACL and Strict rules for settings API #2061

Data API v1
Our JSON api, which will be exposed internally to apps as the 'Data API' needs work to improve
Goal: A consistent v1.0 JSON API which is documented!

Improvement: Refactor Models #1655
Improvement: Remove res.redirect() from API calls #1654
Add validation to models using schema attributes #1401
Database / Schema Additions for apps #2102
Model extension for apps #2138
[Draft] JSON Data API cleanup for consistency #2124
Enhancement: Add HTTP caching for API calls #2016
Provide proper status codes for API operations #2187
JSON Data API Docs #2125

Application Settings
Goal: To be able to create an application with a single setting and appropriate UI.

App Settings: ability to define default settings #2139
App Settings: Generated UI - single text input #2142
[Discussion] App Settings: Dynamic UI #2143
[Draft] App Settings: Advanced Generated UI #2159

Other APIs
In order to build a realistic app, we're going to need access to more than just a data API
Goal: To be able to rebuild the Kudos example plugin by @jgable using the tools provided by the GDK.

[Discussion] Filters API #2113
Routes API [TBD]
Errors / logging API [TBD]

If you're interested in our intentions for Ghost Apps, I recommend reading the (very much WIP) Imagining the Ghost Developer Kit

Temporarily closing all of the app specific issues (tagged with later). Will review & reopen those that are still relevant when we kick off that project, which should be shortly after Zelda lands.


Add Stream Weighted Average

What's needed?
A weighted moving average implementation that updates the avg whenever a new data sample arrives from the stream.
Proposed solution
We can use the MovingWindow class. Whenever the MovingWindow gets updated it triggers the update of the mean.
Right now, the MovingWindow doesn't support sending events on update.
We propose two different implementation approaches.

Add a output trigger channel that informs downstream actors about an update of the window.
The moving average is implemented as part of the MovingWindow and downstream users can request an output channel.

The weights can be user defined by an iterator of weights. When no weight is provided the average is supposed to return the arithmetic average. We might also want to provide a couple of defaults, e.g. exponential.
Example
window = MovingWindow(100, resampled_data_recv)
# use the latest three values for the weighted average
ma_recv = window.moving_avg(weights=[0.2, 0.3, 0.5])
...

Example (exponential)
window = MovingWindow(100, resampled_data_recv)
# use the latest three values for the weighted average
ma_recv = window.moving_avg(exponential_weights(num=10))
...

Use cases
The main use case is feature extraction for ML applications.
Alternatives and workarounds
No response
Additional context
No response

This can be done using numpy. The numpy average method accepts weights. In order to use it we need a wrapped array from Moving Windows underlying Ring Buffer, such that we can write moving_window[-10:] to address the e.g. the latest 10 entries.
If that can be done then we can use the latest n entries for calculating an weighted average as follows:
np.average(moving_window[-n:], weights)

where weights is an arbitrary array of length n.

We need to make sure that the MW returns a sorted array! Add priority URGENT as its already used by @cwasicki.

Blocked because we need to fix some bugs in the ring buffer for this to be useful.

We need to make sure that the MW returns a sorted array! Add priority URGENT as its already used by @cwasicki.

If the purpose of this issue is to ensure that the array returned by the moving window is sorted by timestamp I agree that this is important (for v1). This will be addressed by https://github.com/frequenz-floss/frequenz-sdk-python/issues/214.
The stream weighted average mentioned in the title and the description can be calculated with a sorted array on our side or could still be implemented in the SDK later if required, but I think the priority and milestones should be adjusted accordingly. @matthias-wende-frequenz  @llucax

Leaving this for @matthias-wende-frequenz to answer, I'm too far away from the problem to have a meaningful opinion.


Clip bounds only when both bound ends are not visible.

I think its the correct behavior since you can make them clip while moving and it looks odd.

Was just going to submit a PR for this and saw you already did this.
Please merge this!

Hmm, I see why this isn't merged now actually... Sometimes this can happen :fearful:


Rivers - Add Delta Support

The file deltaRivers.pcx contains four delta graphics.  These are displayed when rivers empty into the coast (exact formula TBD).  We should include them in our river graphics.

Basic Java code for this is located in my editor repo at https://hg.sr.ht/~adj/civ3_cross_platform_editor/browse/src/main/java/com/civfanatics/civ3/xplatformeditor/tabs/map/renderer/ClassicRenderer.java?rev=2aefc36c13bac3b863aed1920c54381243d0cdc4#L857  .  There is also a diff for the change set at https://hg.sr.ht/~adj/civ3_cross_platform_editor/rev/2aefc36c13bac3b863aed1920c54381243d0cdc4, if you prefer that format.
Note that this version requires two neighboring coastal tiles; I believe in some (all?) cases, one may be sufficient, but additional testing should be done to see whether one coastal tile is always sufficient for delta graphics or not.

Observing a random Civ map, it appears that all rivers end next to two coast tiles.  Not sure if that's a 100% true statement, but it was on two maps (one Huge) that I observed.
In scenarios where that isn't true, it appears to be inconsistent whether a delta is included where a river ends.
For now I propose we display deltas when there are two neighboring coastal tiles.

PR 431 is working on this on the tilemaps branch. There are still some alignment issues, but deltas show up now


Hotfix/uda handling

Implementing indexing and search for UDA definitions. #93

This change is

[Current coverage][cc-pull] is 58.31%

Merging [#102][cc-pull] into [master][cc-base-branch] will decrease coverage by 7.82%

2 files in .../subscriptionservice were modified. more

Misses +44
Partials +11
Hits -55

2 files in .../org/oscm/domobjects were modified. more

Misses +3
Partials +10
Hits -13

2 files (not in diff) in .../org/oscm/vatservice were modified. more

Misses +45
Hits -45

10 files (not in diff) in ...gerservice/validator were modified. more

Misses +53
Partials +4
Hits -57

4 files (not in diff) in .../triggerservice/bean were modified. more

Misses +57
Partials +13
Hits -70

2 files (not in diff) in .../oscm/triggerservice were modified. more

Misses +10
Hits -10

2 files (not in diff) in ...triggerservice/local were modified. more

Misses +1
Partials +4
Hits -5

2 files (not in diff) in ...gerservice/assembler were modified. more

Partials +9
Hits -9

2 files (not in diff) in ...scriptionservice/dao were modified. more

Misses +18
Partials +2
Hits -20

8 files (not in diff) in ...criptionservice/bean were modified. more

Misses +130
Partials +176
Hits -306

@@             master       #102   diff @@
==========================================
  Files          1873       1873
  Lines         95966      95982     +16
  Methods           0          0
  Messages          0          0
  Branches      11926      11931      +5
==========================================
- Hits          63455      55964   -7491
- Misses        32511      37070   +4559
- Partials          0       2948   +2948

[][cc-pull]

Powered by Codecov. Last updated by [f67bbc3...b44f5c9][cc-compare]
[cc-base-branch]: https://codecov.io/gh/servicecatalog/development/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/servicecatalog/development/compare/f67bbc31889d2350f0d4cb0d273bd49d40259823...b44f5c9f30c1846aa1f48eaa85bdecefa0223f6c
[cc-pull]: https://codecov.io/gh/servicecatalog/development/pull/102?src=pr

Reviewed 4 of 10 files at r1, 27 of 29 files at r2, 5 of 5 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable


WIP: Improve injection removal from the image

[test]

@csrwng @bparees ready for review :)

@bparees do you know if this will work on OpenShift (we need to docker exec as root).

@mfojtik it should work because we are running as privileged and have full access to the docker socket. Not sure it's a good thing though :)

@csrwng we already use UploadToContainer which runs as root :)

@bparees do you know if this will work on OpenShift (we need to docker exec as root).

yeah it'll presumably work, but it is slightly scary.

@bparees there is no other way to add files into any location... so we sacrificed a little bit of security to get better user experience, which I'm not sure is a right thing :-) But I don't think this exposes some vulneability since we control the S2I exec invocations.

@mfojtik just thinking out loud.... what if the provided user image includes its own "rm" binary?

@csrwng then we run it as root inside the assemble container...

isn't that a security exposure?

isn't that a security exposure?

yes, yes it is.

@csrwng @bparees after some thinking I realized that we allow you to run any command as root in Docker strategy, and I think this is no different, is it?

@mfojtik correct. But that is why we consider the Docker strategy less secure. We wouldn't allow it online for example.

In that case I am more convinced to leave the truncation in place. That
runs as user. @bparees?
Also I think thos was a good exercise, at least for me to se what are the
boundnaries ww dont want to cross in s2i :)
On Jan 20, 2016 10:46 PM, "Cesar Wong"<EMAIL_ADDRESS>wrote:

@mfojtik https://github.com/mfojtik correct. But that is why we
consider the Docker strategy less secure. We wouldn't allow it online for
example.
—
Reply to this email directly or view it on GitHub
https://github.com/openshift/source-to-image/pull/390#issuecomment-173370668
.

In that case I am more convinced to leave the truncation in place. That runs as user. @bparees?

for now at least that seems best.

In that case I am more convinced to leave the truncation in place. That runs as user.

I suggest to add a comment to the sources about why we're using current approach and what is alternative to it.

@mfojtik close this?


Ask for help about wallet recovery

No matter what I enter, it will prompt an error

The error is showing because you only have a single letter, which is not a valid BIP 39 seed phrase.


Reconciled columns not being draggable to item inputs in Wikidata schema

Describe the bug
In some situations, reconciled columns cannot be dragged and dropped to inputs that expect Wikidata entities.

To Reproduce
The exact steps are not clear to me, but this can be observed in the following screencast at 40:00:
https://www.twitch.tv/videos/659297903
Desktop:

OS: Windows
Browser Version: Firefox
JRE or JDK Version:

OpenRefine :

Version 3.3

Just recently I had a similar issue. It seemed to be the case, that https://github.com/OpenRefine/OpenRefine/blob/master/extensions/wikidata/module/scripts/dialogs/schema-alignment-dialog.js#L109 was executed before https://github.com/OpenRefine/OpenRefine/blob/master/extensions/wikidata/module/scripts/dialogs/schema-alignment-dialog.js#L132.
I was able to reproduce it multiple times with OpenRefine 3.2 and 3.3. After in the project the _reconService was properly initialized however, the problem disappeared mystically.


filesystem config with visibility: 'public' does not work

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-37290
[created from NEXT-37290, comment 514405]


Do not require a github login

Is there any way to deploy to salesforce without requiring a github account ?
I would like to use this or something similar to simplify the life of salesforce admin, but they do not have a github account.
Thanks.

Hey I am having the same issue. It's requiring ridiculous permissions full read & write to all public and private permissions!!!
@afawcett I think you just broke thousands of projects with this release.

Wow ok.... i'll get onto this...
The Private GitHub work was added by another dev, which i of course reviewed, but did not notice it seems to always want GitHub login access regardless of public or private. I did not think i regressed or changed any behaviour regarding the private GitHub support. But maybe i did.... Basically i'm going to do two things then...
A) Make sure it only needs GitHub login for Private Repos
B) Make sure when it does need GitHub login it requests the minimimum of permissions.
Sorry about this, will look into this, this weekend! 👍
Andy

Hi,
Its me who implemented the private repos feature. If i remember correctly it was going to oauth process only if fetching github repository failed. In some catch block if i recall right (it was a long time ago)
Anyway let me know if you have any questions.

@motiko yep, and it was me that broke it! Just found out why...so i'll push the fix shortly. One thing i cannot find though is how to change the oAuth scope permissions? I'll keep searching in the meantime...

Ok, i've pushed a fix for this and opened a new issue to review the access https://github.com/afawcett/githubsfdeploy/issues/28.


MFA links for China App stores

There should be NOTE for links to China app downloads from Baidu, Lenovo, Huawei and Samsung Galaxy Store.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 640b9158-3bba-2f76-b9f1-c2660e530062
Version Independent ID: d6d2980d-b36b-9dc3-5c0c-4abed8d19ae2
Content: Download and install the Microsoft Authenticator app - Azure AD
Content Source: articles/active-directory/user-help/user-help-auth-app-download-install.md
Service: active-directory
Sub-service: user-help
GitHub Login: @curtand
Microsoft Alias: curtand

@ivandretvic Thank you for your feedback . We will investigate and update the thread.

@ivandretvic  The product team is in the process of having the Authenticator app uploaded to the most alternative app stores in china officially on Microsoft channel due to google play store being banned in China. This is taking time because of multiple levels of approval from the company side as well during review process.
Alternatively The Microsoft Authenticator has been provided unofficially on the following websites as an alternative to Google Play store which is blocked in China. Please check the link to download the same.
Baidu
Tencent
Disclaimer :- Please scan the files before installing the same on your phone.
Once we have the official links available, we will add those links to the document.

@ivandretvic Closing the thread now.


CloudKit Working? Does Anyone have actually have Subscription, etc. working?

I have been trying to get CloudKit Subscriptions working, basically it doesn't do anything after you attempt to send the invitation.  I came across this little note in CKSubscriptions Apple doc:
Overview
Note: CKQuerySubscription is not supported in a sharedCloudDatabase.
Can anyone enlighten me and/or describe how to get the subscription workflow working?  Or a least confirm that it does work?
Many thanks!

You need to make sure you call the register method in your app delegate, as well as have the push notifications, and background fetch capabilities. See the sample app to see how that works.
The subscriptions also don't work in the simulator if I remember properly.
Are you using the CloudKit sharing? If not, the warning you mention should not play any part. For standard sync of one user, you don't need CloudKit sharing.

Drew,
WE NEED CLOUDKIT SHARE.  As described to you in detail, numerous times;

Our current apps are able to share information  between devices using the same iCloud Account with Apple Ubiquity Store methods.  Not as cool as Ensembles, but works for thousands of users with the same iCloud Account.

WE NEED ENSEMBLES TO SHARE DATA BETWEEN USERS WITH DIFFERENT ICLOUD ACCOUNTS.  Why in the world would you offer all this technology, CloudKit Share, Dropbox, IdioSync, etc. to simply share data between devices using the same iCloud account?  We are doing it now with basic iCloud.

On Jan 4, 2020, at 2:34 AM, Drew McCormack<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
You need to make sure you call the register method in your app delegate, as well as have the push notifications, and background fetch capabilities. See the sample app to see how that works.
The subscriptions also don't work in the simulator if I remember properly.
Are you using the CloudKit sharing? If not, the warning you mention should not play any part. For standard sync of one user, you don't need CloudKit sharing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/drewmccormack/ensembles/issues/288?email_source=notifications&email_token=AB4FAW3QNXLNE5UTMV3H5ETQ4BJ3XA5CNFSM4KCNODZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEICULYI#issuecomment-570770913, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4FAW3SRXD5JRSPC2L3KOTQ4BJ3XANCNFSM4KCNODZA.

I have a LOT of customers, and do a ton of support each day. I don't recognise every request, and recall all circumstances on every issue posted. Especially when a request is new, and I can't see any history attached to it.
Why would I offer a sync solution for iCloud?  It was unusable, and is now also completely deprecated. That is why. I would have preferred not to write my own framework, but there was no choice.
Ensembles supports CKShare. I did not say you can't shared stores. But push notifications may not be supported, due to the Apple restriction. The push notifications are not a requirement, they are just a nice-to-have, so for a shared store, you can just use a timer to sync every few minutes, in addition to other logical times (eg going to background).


 Disabling (LLL) allowed us to access the moon again, but I don't know why.

Same

Also happened to me.
From what I remember, I used LLL, it's dependencies, all of Tolian's moons and bunch of other things.
We did 3 days' worth of travelling and when it was time to go to the company, we typed it into the terminal.
However, the terminal would not let you press enter with any combination for the company building.
There seemed to be an error with some sort of Terminal Manager script and an array index out of bounds.
Another problem seems to also be that some of the moons just randomly don't appear in the terminal moons list.
Modpack: 018f2685-46bd-a231-6896-14f15390913b

[Error  : Unity Log] IndexOutOfRangeException: Index was outside the bounds of the array.
Stack trace:
LethalLevelLoader.TerminalManager.LockedNodeEventTest (TerminalNode& currentNode, TerminalNode& loadNode) (at :IL_0006)
LethalLevelLoader.TerminalManager.OnBeforeLoadNewNode (TerminalNode& node) (at :IL_004D)
LethalLevelLoader.Patches.TerminalLoadNewNode_Prefix (Terminal __instance, TerminalNode& node) (at :IL_001B)
(wrapper dynamic-method) Terminal.DMDTerminal::LoadNewNode(Terminal,TerminalNode)
Terminal.OnSubmit () (at <255c0877f9414c3aa6f1fe5079ac13f3>:IL_00FB)
UnityEngine.Events.InvokableCall.Invoke () (at :IL_0010)
UnityEngine.Events.UnityEvent1[T0].Invoke (T0 arg0) (at <e27997765c1848b09d8073e5d642717a>:IL_0049) TMPro.TMP_InputField.SendOnEndEdit () (at <9baa8119dbcd498f902c1a92f10843c1>:IL_000E) TMPro.TMP_InputField.ReleaseSelection () (at <9baa8119dbcd498f902c1a92f10843c1>:IL_001B) TMPro.TMP_InputField.DeactivateInputField (System.Boolean clearSelection) (at <9baa8119dbcd498f902c1a92f10843c1>:IL_00B0) TMPro.TMP_InputField.OnUpdateSelected (UnityEngine.EventSystems.BaseEventData eventData) (at <9baa8119dbcd498f902c1a92f10843c1>:IL_007C) UnityEngine.EventSystems.ExecuteEvents.Execute (UnityEngine.EventSystems.IUpdateSelectedHandler handler, UnityEngine.EventSystems.BaseEventData eventData) (at <17de86d66286445fa95af59fa8fa644d>:IL_0000) UnityEngine.EventSystems.ExecuteEvents.Execute[T] (UnityEngine.GameObject target, UnityEngine.EventSystems.BaseEventData eventData, UnityEngine.EventSystems.ExecuteEvents+EventFunction1[T1] functor) (at <17de86d66286445fa95af59fa8fa644d>:IL_0067)
UnityEngine.EventSystems.EventSystem:Update()

Same here, doesn't happen when playing on 1.2.1, only with LLL1.2.2
maybe related to the ExtendedLevel.IsRouteLocked

Same issue for me. Trying to hit after enter with any line that'd trigger the confirm or deny prompt, just results in not doing anything.

You can use AutoCompanyBuilding to resolve this

I tried using that, and in most cases it helps, but if one player opens up the terminal and flies to another planet by mistake... you are never going back to company building ever again on this save 💀 even after reloading if the game has auto-saved

use TerminalFormatter
---Original---
From: @.>
Date: Tue, Apr 30, 2024 23:44 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [IAmBatby/LethalLevelLoader] Company Building Inaccessible (Issue#80)
You can use AutoCompanyBuilding to resolve this
I tried using that, and in most cases it helps, but if one player opens up the terminal and flies to another planet by mistake... you are never going back to company building ever again on this save 💀 even after reloading if the game has auto-saved
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Yeah I just found out about this, I'll test this solution in a few hours when I'm on my computer. Thanks for the tip, I'm sure this will help at least someone else here until a patch is released ;)

Resolved in future versions of the project.


just parse the string into an integer and all is well

Necessary because timesSeries method in new version of async won't coerce a string as a first arg to an int!

Cool!

LGTM


Removing received messages from queue

When used with apache activemq, the amqp client does not seem to cause received messages to be removed from the queue, even when the policy sets the receiver settle mode to auto.  I think you may have touched on this in one of your caveats on the project page, but is there a workaround for this at the moment?

I'm facing the same issue. No acknowledgment is sent to the broker and therefore after 100 message no messages are received anymore :( Is there something you can do, because the only other option would be for me to add this functionality and I'm really not that good in JS ;)

Ugh, ActiveMQ can bite my ass.  I just modified the code to send Disposition frames accepting messages, and it STILL doesn't consider them acknowledged and stops after 100.
Sorry, it'll take me a bit longer to figure out what it's complaining about and how to fix it.

Thanks for trying! Would be really great for this work as we are using it in a very important project.

I've started working on it in the 'send-dispo-frames' branch, in case you want to follow along.

@midramas this should be solved in this branch which should be merged soon. Please give it a shot and let us know how it works for you. I'm generally working on message disposition, so we should be able to clear up a lot of these issues

I've tested it and it works now! Thanks soooo much for that :)

cool :)


Stack scoped local volumes are not deleted when stack is deleted.

Rancher versions:
rancher/server: v1.5.x, 1.6.x
Docker version: (docker version,docker info preferred)
Any
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
Any
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Any
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Any
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:

Using compose, create a stack scoped local volume:

version: '2'
volumes:
  foo: {}
services:
  sv1:
    image: nginx
    volumes:
    - foo:/test

Wait for stack to become active and then delete.

Results:
Expected:
On the host, the volume foo should be deleted.
Actual:
Its not deleted.
Notes:
This is caused by how we create local volumes from volume templates. There's a few internal fields we aren't setting correctly.

Tested with rancher-server version - 1.6.3-rc2

Using compose, create a stack scoped local volume:
version: '2'
volumes:
foo: {}
services:
sv1:
image: nginx
volumes:

foo:/test

Wait for stack to become active and then delete.
Once the stack is deleted , the stack scoped volume also gets deleted from the host.


pos_to_linecol broken in textX-1.7.0

Hello Igor,
I am using pos_to_linecol to get line and column numbers to create human readable feedback when a parsing error occurs. Migrating from 1.6.1 to 1.7.0 I encounter the following error, using the sample code below:
import textx.model
from textx import metamodel_from_str

mm = metamodel_from_str("""
Model: shapes*=Line;
Line: 'line' start=Point '/' end=Point;
Point: x=INT ',' y=INT;
""")
model = mm.model_from_str("line 1,1 / 2,2")

for shape in model.shapes:
    print(mm.parser.pos_to_linecol(shape._tx_position))

And the error is:
Traceback (most recent call last):
  File "test.py", line 15, in <module>
    print(mm.parser.pos_to_linecol(shape._tx_position))
  File "/private/tmp/venv/lib/python3.6/site-packages/arpeggio/__init__.py", line 1612, in pos_to_linecol
    if not self.line_ends:
AttributeError: 'TextXModelParser' object has no attribute 'line_ends'

Seems to be a problem in arpeggio?

Hi Antoine,
thanks for the report. This seems to be a problem introduced with multi-model support. Meta-model parsers are now cloned to parse each file/string, so caching of line_ends used to speed up later finding of object position broke as the input is not parsed with the mm.parser. I think that the best solution is to use parser reference from the model instead like this:
for shape in model.shapes:
    print(model._tx_parser.pos_to_linecol(shape._tx_position))

as the parser kept on meta-model is just a prototype parser used for cloning.
Maybe @goto40 could take a look.
Anyway, this is at least a bug in the docs so we'll keep this open until fixed.

I will have a look

Closed via #68


Relative monitor movement behaves counter-intuitive

Relative monitor movements (m+1, m-1) do not take monitor position configurations into account.
I have 3 monitors, in the configuration below:
------------   ------------    ------------
|           |  |           |   |           |
|     1     |  |     3     |   |     2     |
|           |  |           |   |           |
------------   ------------    -------------

Moving a workspace from monitor 1 with movecurrentworkspacetomontor ,+1 I would expect it to go to
monitor 3, but goes to monitor 2 instead.
When adjusting this, this might break a lot of configs. Perhaps add a script option (in hyprctl) to get the adjacent monitors
so I can script this.
Not sure if this actually inconsistent (names work the same), but still.

Created this script for now that will work as expected
#!/usr/bin/env sh

for app in jq hyprctl; do
    if ! command -v "${app}" >/dev/null; then
        printf 'binary not found: %s\n' "${app}" >&2
        exit 127
    fi
done

monitors="$(hyprctl -j monitors)"
direction="${1:-next}"

case "${direction}" in
    next)
        offset="$(printf '%s\n' "${monitors}" | jq '.[] | select (.focused) .x + .width')"
        monitor_id="$(printf '%s\n' "${monitors}" | jq ".[] | select (.focused == false and .x == ${offset}) .id")"

        if [ -z "${monitor_id}" ]; then
            monitor_id="$(printf '%s\n' "${monitors}" | jq '.[] | select (.focused == false and .x == 0) .id')"
        fi

        ;;
    prev)
        offset="$(printf '%s\n' "${monitors}" | jq '.[] | select (.focused) .x')"
        monitor_id="$(printf '%s\n' "${monitors}" | jq ".[] | select (.focused == false and .x + .width == ${offset}) .id")"

        if [ -z "${monitor_id}" ]; then
            rightmost="$(printf '%s\n' "${monitors}" | jq 'map(.x) | max')"
            monitor_id="$(printf '%s\n' "${monitors}" | jq ".[] | select (.focused == false and .x == ${rightmost}) .id")"
        fi

        ;;
    *)
        printf 'unsupported direction "%s"\n' "${direction}'" >&2
        exit 5

        ;;
esac

if [ -z "${monitor_id}" ]; then
    printf 'could not find %s monitor\n' "${direction}" >&2
    exit 6
fi

hyprctl dispatch movecurrentworkspacetomonitor "${monitor_id}"

you can do l r etc. +1 -1 is just ID-based.

@vaxerski two more comments:

Perhaps document this on the wiki? I was unable to find this information.
It does not roll-over; after moving the window to the rightmost monitor dispatching hyprctl dispatch movecurrentworkspacetomonitor r does nothing, where I'd expect it to go to the left most monitor instead.

Perhaps document this on the wiki? I was unable to find this information.


Update the wrong namespace in comment

When creating a new PR, please do the following and delete this template text:

Reference the issue number if there is one:
Fixes #Issue_Number

The "Fixes #nnn" syntax in the PR description causes
GitHub to automatically close the issue when this PR is merged.

Suggest reviewers if you know who should review the PR, using the GitHub Reviewers UI.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@manimaranm7  Nice fix. Thanks!


test: replace ensure.TempDir with t.TempDir

What this PR does / why we need it:
A testing cleanup.
This pull request replaces ensure.TempDir(t) with t.TempDir. We can use the T.TempDir function from the testing package to create temporary directory. The directory created by T.TempDir is automatically removed when the test and all its subtests complete.
Reference: https://pkg.go.dev/testing#T.TempDir
func TestFoo(t *testing.T) {
	// before
	tmpDir := ensure.TempDir(t)
	defer os.RemoveAll(tmpDir)

	// now
	tmpDir := t.TempDir()
}

Special notes for your reviewer:
If applicable:

[ ] this PR contains documentation
[x] this PR contains unit tests
[x] this PR has been tested for backwards compatibility

@hickeyma Hi, this PR seems to have been forgotten :sweat_smile: Would you mind spending ~5 minutes to review it? Thanks you in advance

@yxxhero Hi, this PR seems to have been forgotten :sweat_smile: Would you mind spending ~5 minutes to review it? Thanks you in advance

@mattfarina @hickeyma Please take a look at this PR. Thanks in advance :heart:

Hello @mattfarina @hickeyma . I apologize for the explicit mention, but I wanted to follow up on this pull request I created some time ago.
I would be grateful if you could take some time to review the changes and provide me with your feedback. If there are any specific concerns or questions you have about the changes, I am more than willing to help address them.
Thank you for your time and consideration. I truly appreciate it. :heart:

Hello @joejulian @mattfarina . I apologize for the explicit mention, but I wanted to follow up on this pull request I created some time ago.
I would be grateful if you could take some time to review the changes and provide me with your feedback. If there are any specific concerns or questions you have about the changes, I am more than willing to help address them.
Thank you for your time and consideration. I truly appreciate it. :heart:

Hello @joejulian @mattfarina . I apologize for the explicit mention, but I wanted to follow up on this pull request I created some time ago.
I would be grateful if you could take some time to review the changes and provide me with your feedback. If there are any specific concerns or questions you have about the changes, I am more than willing to help address them.
Thank you for your time and consideration. I truly appreciate it. :heart:


MN - Missing Specimen Collection Date

From: Cassman, Jacqueline (MDH)
Sent: Wednesday, February 2, 2022 3:42 PM
To: Judd, Michael (CDC/DDPHSS/OD<EMAIL_ADDRESS>Green, Brick (CDC/DDPHSS/OD/HITSSU) (CTR<EMAIL_ADDRESS>Reeves, Maurice (CDC/OCOO/OD<EMAIL_ADDRESS>Brewster, Adrian (CDC/DDPHSS/OD) (CTR<EMAIL_ADDRESS>Liu, James (CDC/OCOO/OD<EMAIL_ADDRESS>Subject: MDH: CDC Prime ELR Error 1/27/22
Good afternoon,
MDH received an ELR message that was missing OBR 7, Observation Date/time. Are you able to correct and resend the message please?
Accession ID:
00356bbf-0e49-4741-b66a-34364703dbcf

Thank you,
Jacqueline
Jacqueline Cassman, MPH
Electronic Case Reporting (eCR) Onboarding Coordinator | MEDSS Operations
Pronouns: she/her/hers
Minnesota Department of Health
Office:<PHONE_NUMBER>

@Adrian-Brewster @anshulkumar-usds I checked into this. ImageMover did not send the specimen collection date. Should we request they resend?
Message ID:
00356bbf-0e49-4741-b66a-34364703dbcf

@brick-green-agile6 yes. And they should always be sending that to us. @Adrian-Brewster @anshulkumar-usds please ask them to resubmit this record, and to make sure they're always sending us this. In fact, we should maybe update their schema to force that value to have a cardinality of one if it doesn't already. I can't really think of a single location that would accept a message without the specimen collection date.

2/14: Checked with IM and requested to make this a priority

Anshul following up with IM.

IM confirmed resubmitting. MN notified.


Type error when using PySersicMultiPrior

I was trying to use the multiprior as demonstrated in the demo (so I basically copied all the code there and did a little modification) with my own data. A catalog was generated by SEP and to be fed into the multiprior object. But when I run the line mp = PySersicMultiPrior(catalog = to_pysersic, sky_type='flat',sky_guess=sky_guess,sky_guess_err=sky_guess_err), a type error pops up:"'<class 'jaxlib.xla_extension.DeviceArray'>' object does not support item assignment. JAX arrays are immutable. Instead of x[idx] = y, use x = x.at[idx].set(y) or another .at[] method: https://jax.readthedocs.io/en/latest/_autosummary/jax.numpy.ndarray.at.html"
And the error seems buried pretty deep. I am not sure if there's actually a bug or if my input data has some kind of non-compatible format/bit issue. (But I never had this problem if I use a single custom prior on the same data) I can attach my input data here if that would help.

Hi @aruba19th , definitely interesting, I haven't run into that with any multi-priors before. It could definitely be a change in jax, which is changing quickly, but I'm happy to take a look. Would you mind emailing me a little zip file of the image you are trying to fit and a notebook replicating the error?


Document config parameters in plugins

Is your feature request related to a problem? Please describe.
Add docstring documentation for config parameters available in each plugin.
Describe the solution you'd like
Use docstring to document the parameters available for each plugin.
Should be described for each parameter:

the parameter name
a description explaining what is it for, what does it do
format and type of expected value
whether it is optional or mandatory
default value

plugins to cover:
Api

[x] EcmwfApi
[x] UsgsApi

Authentication

[x] AwsAuth
[x] GenericAuth
[x] HTTPHeaderAuth
[x] KeycloakOIDCPasswordAuth
[x] OAuth
[x] OIDCRefreshTokenBase
[x] OIDCAuthorizationCodeFlowAuth
[x] HttpQueryStringAuth
[x] QueryStringAuth
[x] RequestsSASAuth
[x] SASAuth
[x] TokenAuth
[x] OIDCTokenExchangeAuth

Crunch

[x] FilterDate
[x] FilterLatestIntersect
[x] FilterLatestByName
[x] FilterOverlap
[x] FilterProperty

Download

[x] AwsDownload
[x] CreodiasS3Download
[x] HTTPDownload
[x] S3RestDownload

Search

[x] BuildPostSearchResult
[x] BuildSearchResult
[x] CopMarineSearch
[x] CreodiasS3Search
[x] CSWSearch
[x] DataRequestSearch
[x] QueryStringSearch
[x] ODataV4Search
[x] PostJsonSearch
[x] StacSearch
[x] StaticStacSearch

Is your feature request related to a problem? Please describe. Add docstring documentation for config parameters available in each plugin.
Describe the solution you'd like Use docstring to document the parameters available for each plugin. Should be described for each parameter:
* the parameter name

* a description explaining what is it for, what does it do

* format and type of expected value

* whether it is optional or mandatory

* default value

plugins to cover:
Api
* [x]  EcmwfApi

* [x]  UsgsApi

Authentication
* [x]  AwsAuth

* [x]  GenericAuth

* [x]  HTTPHeaderAuth

* [x]  KeycloakOIDCPasswordAuth

* [x]  OAuth

* [x]  OIDCRefreshTokenBase

* [x]  OIDCAuthorizationCodeFlowAuth

* [x]  HttpQueryStringAuth

* [x]  QueryStringAuth

* [x]  RequestsSASAuth

* [x]  SASAuth

* [x]  TokenAuth

* [x]  OIDCTokenExchangeAuth

Crunch
* [x]  FilterDate

* [x]  FilterLatestIntersect

* [x]  FilterLatestByName

* [x]  FilterOverlap

* [x]  FilterProperty

Download
* [x]  AwsDownload

* [x]  CreodiasS3Download

* [x]  HTTPDownload

* [x]  S3RestDownload

Search
* [x]  BuildPostSearchResult

* [x]  BuildSearchResult

* [x]  CopMarineSearch

* [x]  CreodiasS3Search

* [x]  CSWSearch

* [x]  DataRequestSearch

* [x]  QueryStringSearch

* [x]  ODataV4Search

* [x]  PostJsonSearch

* [x]  StacSearch

* [x]  StaticStacSearch

NOTE: RequestsSASAuth and QueryStringAuth aren't plugins and therefore don't have a config


Composite Foreign Key Constraints

Hi there,
thanks again for this wonderful lib.
I want to work with composite primary keys (which works nicely) and the foreign ones (which causes some problems).
On https://sqlite.org/foreignkeys.html chapter 4.1 you can read:
CREATE TABLE album(
  albumartist TEXT,
  albumname TEXT,
  albumcover BINARY,
  PRIMARY KEY(albumartist, albumname)
);

CREATE TABLE song(
  songid     INTEGER,
  songartist TEXT,
  songalbum TEXT,
  songname   TEXT,
  FOREIGN KEY(songartist, songalbum) REFERENCES album(albumartist, albumname)
);

So I tried to build the according classes with your lib:
@Entity
public interface Album extends Persistable {

    @Key
    String getAlbumArtist();

    @Key
    String getAlbumName();

    byte[] getAlbumCover();

    @OneToMany
    List<Song> getRefSongs();
}

@Entity
public interface Song extends Persistable {

    int getSongId();

    String getSongArtist();

    String getSongAlbum();

    String getSongName();

    @ForeignKey(referencedColumn = "albumartist, albumname")
    @ManyToOne
    Album getRefAlbum();
}

This generates the following statements:
create table Album (albumArtist varchar(255), albumName varchar(255), albumCover varbinary(255), primary key (albumArtist, albumName))

create table Song (refAlbum varchar(255), songAlbum varchar(255), songArtist varchar(255), songId integer not null, songName varchar(255), foreign key (refAlbum) references Album (albumArtist) on delete cascade on update cascade)

Let's speak of differences and similarities:

instead of TEXT the varchar(255) is taken - OK
instead of BINARY the varbinary(255) is taken - OK
the composite primary key is build as expected - NICE :-)
the composite foreign key didn't work out, only the first part albumArtist was taken, albumName is missing - NOT SO NICE :-(

Am I missing something?
Can you please help me on this?
Best regards,
DaRolla

played around the weekend, but found no solution (tried @Column with the foreignKey array for example)

Any news about this? Seems like composite primary keys and foreign keys in junction tables don't work together.

this is a blocking issue to me


Feat/invt-cpc-730-ability-to-add-product-to-an-inventory-and-project-structure-and-service-logic-setup

JIRA: https://champlainsaintlambert.atlassian.net/browse/CPC-730
Context:
Refactored structure of the inventory service and inventory service logic in the api gateway
Changes

Removed all the old files in the inventory service and removed all tests.
Started from fresh and recreated the structure and the packages for the classes
Added the post in the API gateway
Commented out unit test in API gateway

Before and After UI (Required for UI-impacting PRs)
No UI changes
Dev notes (Optional)

Making a pull request because this task is blocking my teammates to complete their stories, another branch will be made for the testing

Waiting to reopen PR when i get confirmation that Billing service tests are not failing due to my changes, even tho nothing was touched in the billings service


⚠ Unifi Controller has degraded performance

In 0345c3d, Unifi Controller (https://unifi.vflits.com/) experienced degraded performance:

HTTP code: 200
Response time: 2199 ms

Resolved: Unifi Controller performance has improved in 4d19369 after 10 minutes.


Update decorators.py

fix bugs. When package name changed, original can not work. Use relative import.

Coverage remained the same at 96.296% when pulling ff19f2628522a3655b28eb15b8ad4af93a931282 on daimon99:master into e892fc4c0ca0a5e4a37d9183276a195548848518 on ZhukovAlexander:master.


Bootloader external flash

Includes e-s and e-s-a impls for nrf QSPI
WIP: Working on testing it.

Relies on #723

@lulf is it still WIP or not anymire?

@Dirbaio no more WIP, ready for review.

Merging now. Will add some more documentation to the book and refactor the example structure a bit in a later PR. Also working on stm32 support.
bors r+


Add ability to run all jobs in a PR at will

What does this PR do?
If you put ci run all in a pull request like [ci run all] Test base check API changes it will test each check in its own runner like merges to master. If there are many checks that have changed this will therefore avoid timeouts.

Codecov Report

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

@@            Coverage Diff             @@
##           master    #2425      +/-   ##
==========================================
- Coverage   83.86%   83.81%   -0.05%
==========================================
  Files         578      574       -4
  Lines       34312    34216      -96
  Branches     4199     4192       -7
==========================================
- Hits        28775    28679      -96
  Misses       4279     4279
  Partials     1258     1258

Can you mention this feature here? https://github.com/DataDog/integrations-core/blob/master/CONTRIBUTING.md#commit-messages

@masci https://github.com/DataDog/integrations-core/pull/2439


Standardize progress funding message

On the progress_report3 branch (#259) the funding messages are still inconsistent:
Bob funding:
Success: Funding address: tb1qw9aggkkydncyjcda28628dgcp6jhvmzay0thzj
Alice funding:
Success: Alice, please send 0.001000000000 XMR to 56FuFfbfbdP6YjhTjYVaCRCD9HKQGipmtLgnZ5cbRRAu7F33UkEjKhYgzSSNRJvz5wXtzZ3d3EVs1W6uxdzL5WVqSVsHT46

im trying to achieve this here #278

The report progress will print all line, with the last one prefixed by "Success: ".
In https://github.com/farcaster-project/farcaster-node/issues/274 the proposition for displaying funding required would be:
Funding required: send 0.001000000000 XMR to 55GAd9ddNjKRAyi74PwhTKXkhyfDwvVmTGh7NTNHsaA2BfwShd5v8VHPWJaKuKNJYFJwvEx5nZ6fiMr4BC6UkoPzHjryVNK

or

Success: Funding required: send 0.001000000000 XMR to 55GAd9ddNjKRAyi74PwhTKXkhyfDwvVmTGh7NTNHsaA2BfwShd5v8VHPWJaKuKNJYFJwvEx5nZ6fiMr4BC6UkoPzHjryVNK

and
Funding required: send 0.00001500 BTC to tb1qx78xnxj4wxjgy28cvs6v6f7an9cgcxh8ps446r

or

Success: Funding required: send 0.00001500 BTC to tb1qx78xnxj4wxjgy28cvs6v6f7an9cgcxh8ps446r

Done in #334 , but moved out of the progress messages and moved into needs-funding


Interop generation for iOS arm64

Environment
How do you use Sentry?
Sentry SaaS (sentry.io)
Which SDK and version?
Sentry 7.21.0
M1 mac with interop enabled for arm64 and simulatorArm64
Steps to Reproduce
Add  pod"Sentry", "~> 7.21.0") to cocoapods gradle plugin
Expected Result
Sync succeeds
Actual Result
Sync step fails in android studio.
it fails on 3 steps :

cinteropSentryIosArm64
cinteropSentryIosSimulatorArm64
shared:cinteropSentryIosX64

Example error log for one of the steps :
Link
Additional info
When trying to sync the kmp-app sample i get a failure on the following step:
Task 'wrapper' not found in project ':sentry-samples:kmp-app'.
So i'm wondering if there might be something wrong in my environment ?
Question
Are there any requirements to make the interop work on an M1 setting or is it supposed to work out of the box ?
Let me know if you need any more details. Thanks for your help !

Hey @ncltg, are you opening the sample app in it's own Android Studio project?
You should open the root project and sync it - the sample app will also sync then because it is embedded as a subproject. You can then run the sample apps from there. I'm also on an M1 so it should work out of the box

Hey @buenaflor,
Indeed I was opening the project from the kmp-app subfolder. When opening from the parent project it work flawlessly.
I had no trouble with interop as in my current project so it must be related to my configuration.
Any idea on what kind of wrong configuration to look for here ?
Thanks again for the prompt reply 😊

Which plugin versions are you running in your project? Maybe you can post your gradle setup so I can try to reproduce your problem

@buenaflor Your last comment helped me pinpoint the issue actually !
I fixed my problem by updating our sentry-android dependency from 5.7.3 to 6.1.4.
After doing so the task failure changed,  which i fixed by using this snippet present in the sample build.gradle :
    // workaround for https://youtrack.jetbrains.com/issue/KT-41709 due to having "Meta" in the class name
    // if we need to use this class, we'd need to find a better way to work it out
    targets.withType<org.jetbrains.kotlin.gradle.plugin.mpp.KotlinNativeTarget>().all {
        compilations["main"].cinterops["Sentry"].extraOpts(
            "-compiler-option",
            "-DSentryMechanismMeta=SentryMechanismMetaUnavailable"
        )
    }

It seems to work just fine now.
Thanks a lot !

@ncltg Nice! We're working on having a release this week so stay tuned. Also feel free to open an issue if there's something you'd like to discuss, since it's an experimental SDK we'd love to hear some feedback :) cheers


Update Pagerduty setup instructions

Hey, I just made a Pull Request!
Update Pagerduty plugin setup instructions
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)

Tugboat has finished building the preview for this pull request!
Link:

https://pr4664-uuncczqrporajwobqxshyhmwkszkamrz.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/603536b865f8171eeff7f421

Tugboat has finished building the preview for this pull request!
Link:

https://pr4664-uuncczqrporajwobqxshyhmwkszkamrz.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/603536b865f8171eeff7f421

Closing in favor of https://github.com/backstage/backstage/pull/4681

Note, with the closure of this PR, don't forget to integrate the fixes you made on the README into the other PR if that's your intent - I think there was good value here which as of yet don't exist in the related PR.

Thanks @adamdmharvey, I'll wait to see where the other one nets out and contribute where there are gaps

Tugboat has finished building the preview for this pull request!
Link:

https://pr4664-b67sakq98hqnnimymvqdct0kzpajbr0f.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/603e8e36fcb22d1327653fd0

@adamdmharvey this has been updated based on #4681

Tugboat has finished building the preview for this pull request!
Link:

https://pr4664-b67sakq98hqnnimymvqdct0kzpajbr0f.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/603e8e36fcb22d1327653fd0

Hi! Haha, I was JUST now looking at this one to see what went wrong. Hello. Seems you forgot to sign the commits is all.


Platform faq

Platform faq
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description

Please describe your changes: Added platform faq

PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged:

[ ] Successful preview build.
[ ] Code owner review.
[ ] No merge conflicts.
[ ] Release notes/new features docs: Feature/version released to at least one prod environment.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://6718ce702eaf3ea6ddf0df72--harness-developer.netlify.app


fix: correct logo text and GitHub icon colors in light mode

name: correct logo text and GitHub icon colors in light mode
about: submit changes to the project
title: "[pr] "
labels: ''
assignees: ''

description
This fixes the issue where the logo text and GitHub icon appeared white in light mode.

related issue: #
type of change

[x] bug fix
[ ] new feature
[ ] breaking change
[x] documentation update

how to test
add a few steps to test the pr in the most time efficient way.

if relevant add screenshots or screen captures to prove that this PR works to save us time.
checklist

[x] MOST IMPORTANT: this PR will require less than 30 min to review, merge, and release to production and not crash in the hand of thousands of users
[x] i have read the CONTRIBUTING.md file
[ ] i have updated the documentation if necessary
[ ] my changes generate no new warnings
[ ] i have added tests that prove my fix is effective or that my feature works

additional notes
any other relevant information about the pr.

i dont have this issue on macos / arc


adding write burst on AvalonMemory

@Martoni do you still want to upstream this?
Apologies, we've been a bit snowed under so didn't get a chance to look at this yet.

Hi chiggs, I think I have more tests to do before proposing an official push.
But yes I still want to upstream it once tested enough.


/app/letsencrypt.sh runs every minute - ignores CRON env variable

08/08/2017 20:25:00crond[53]: wakeup dt=60
08/08/2017 20:25:00crond[53]: file root:
08/08/2017 20:25:00crond[53]:  line /app/letsencrypt.sh
08/08/2017 20:26:00crond[53]: wakeup dt=60
08/08/2017 20:26:00crond[53]: file root:
08/08/2017 20:26:00crond[53]:  line /app/letsencrypt.sh
08/08/2017 20:27:00crond[53]: wakeup dt=60
08/08/2017 20:27:00crond[53]: file root:
08/08/2017 20:27:00crond[53]:  line /app/letsencrypt.sh
08/08/2017 20:28:00crond[53]: wakeup dt=60
08/08/2017 20:28:00crond[53]: file root:
08/08/2017 20:28:00crond[53]:  line /app/letsencrypt.sh
08/08/2017 20:29:00crond[53]: wakeup dt=60
08/08/2017 20:29:00crond[53]: file root:
08/08/2017 20:29:00crond[53]:  line /app/letsencrypt.sh
Environment variable:value on rancher-active-proxy service is default
CRON = 0 2 * * * which should be At 00 minutes past 2:00

Sorry false alarm, I should have checked first.


Optionally Indent attributes

Would be great to be able to specify that XML attributes should also be indented.
 I'd like them to be indented in the following way:
<?xml version="1.0" encoding="UTF-8" ?>
<Reply Success="TRUE" >
   <JobInfo Name="Job 1"
            GUID="{62A160F3-79E8-4358-9073-EDCAE4B4ED75}"
            State="NEX_STARTED"
            Status="STARTED"
            Progress.DWD="32"
            Description="Example Job"
            User="WatchFolder"
            SourceDescription="C : \ _ test . mp4"
            AgentIP="<IP_ADDRESS>"
            Priority.DWD="5"
            DeleteProcessedSource.DWD="1"
            StartTime_SCM="2008-05-1519:23:41" />
</ Reply>

+1

@wabiloo have you found a way (or other plugin) to do this?

I would suggest https://www.paraesthesia.com/archive/2015/03/12/xml-tidy-in-sublime-text/ as tidy is quite flexible.


fix(region): optimized sku sched clear

这个 PR 实现什么功能/修复什么问题:

[x] 功能、bugfix描述
[ ] 冒烟测试
[ ] 单元测试编写

是否需要 backport 到之前的 release 分支:

release/3.5

/area region
/cc @zexi

Codecov Report

Merging #11053 (65d52db) into master (a1a32a9) will increase coverage by 5.35%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master   #11053       +/-   ##
===========================================
+ Coverage    5.81%   11.16%    +5.35%
===========================================
  Files         901      147      -754
  Lines      139126    16957   -122169
===========================================
- Hits         8088     1894     -6194
+ Misses     130331    14870   -115461
+ Partials      707      193      -514

Flag
Coverage Δ

aFlag
11.16% <ø> (+5.35%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/util/rbacutils/policycore.go

pkg/monitor/models/alertdashboard_panel.go

pkg/compute/models/access_groups.go

pkg/compute/models/groupresource.go

pkg/compute/models/scheduled_tasks.go

pkg/apigateway/clientman/totp.go

pkg/keystone/models/projects.go

pkg/compute/models/dbinstance_accounts.go

pkg/multicloud/aws/elasticache_snapshot.go

pkg/cloudcommon/db/scoperesource.go

... and 741 more

Continue to review full report at Codecov.

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


Verify univariate Gaussian KL divergence calculation

The stats_utils.calculate_univariate_gaussian_kl function aims to be numerically stable by performing most calculations in logspace. However, it is not clear that the equations are correct.

The code was calculating KL(q||p) rather than KL(p||q). Fixed.


Referencing a nested struct field in the length macro causes weird behaviour in referencing projects

I have a cargo workspace with two projects, a lib and an exe.
The lib defines the structs, and there is following structure present there:
pub struct Data {
    pub nested: Nested,
    #[speedy(length = nested.message_length - 44 - 4 )]
    pub bytes: Vec<u8>
}

pub struct Nested {
    pub message_length: u32,
    ...
}

The tests on the lib work fine, but if I run cargo check on the exe, which references the lib, i get weird errors (redacted):

Pulling the message_length upwards resolves these errors, but it's very strange the lib itself can be build, but when used as a dependency it can't?

As far as I can see that's a bug in syn 1.0.33 where it suddenly can't parse the nested.message_length expression. As a workaround you should be able to add syn = "=1.0.32" to your Cargo.toml (please let me know if that works for you).

Reported this here: https://github.com/dtolnay/syn/issues/870

I've tried to add it to Cargo.toml but it didn't seem to have any impact (i.e. it didn't seem to pull the correct version) (I don't have much experience with the workspaces), but I saw that it now pulled 1.0.35 of syn and now it works!


Error when running examples

Is this working atm? I get error when I run "npm i && npm run examples":
Error: ENOENT: no such file or directory, open 'examples/simple/build/index.js'
at Error (native)

Can you try creating the 'examples/simple/build' folder? Currently on mobile, so I cant try myself.

That fixed it. Great. Thanks! :+1:

Once I get home I will add the creation to the package.json

Do I need TypeScript to actually use it? It is not a library that I can use directly? It is more of a code example?

you should be able to use the build result as javascript library, once home i can upload to npm

Excellent! Thanks! It look very nice. It is just that I am not that much
into Typescript :/
2016-12-16 15:48 GMT+01:00 Jan van Brügge<EMAIL_ADDRESS>
you should be able to use the build result as javascript library, once
home i can upload to npm
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cyclejs-community/cyclejs-modal/issues/1#issuecomment-267609579,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKcv9vL7j8Dd_p_b9d6JuY9yk3hKookPks5rIqS1gaJpZM4LPEdK
.

--
Morten Poulsen
Co-Founder, Development
PokerJuice.com
http://morten.pokerjuice.com

you can now use it with npm i -S cyclejs-modal


chore: Update version to 0.2.0 and add 0.1.0 changelog

Which issue does this PR close?

N/A
Rationale for this change

Part of the release process
What changes are included in this PR?

Update version from 0.1.0 to 0.2.0
Changelog generated for all PRs between 0.0.0 tag and branch-0.1
Fix one error in the release verification script that was discovered when verifying 0.1.0-rc1

How are these changes tested?

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 33.56%. Comparing base (1d33828) to head (2bc848e).

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #696      +/-   ##
============================================
- Coverage     33.62%   33.56%   -0.06%
+ Complexity      827      813      -14
============================================
  Files           110      110
  Lines         42555    42555
  Branches       9356     9356
============================================
- Hits          14307    14285      -22
- Misses        25293    25315      +22
  Partials       2955     2955

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Step width 8.33 kHz treated differently in regular scanning and spectrum analyzer

This might be intentional but I noticed that in regular scanning mode a step width of 8.33 kHz always leads to 25 kHz increments after three steps, as expected. But in the spectrum analyzer the step seems to literally be treated as 8.330 kHz. This causes a growing mismatch between scanned frequency and valid air band channel frequencies.
The attached image shows the result of entering the spectrum analyzer with a scanning range of 118.000 to 137.000 MHz showing invalid air band frequencies for both the current and highest frequency.

Definitely not supposed to happen. Someone forgot to FREQUENCY_RoundToStep() in a few places.

The upper limit is now displayed as "136.99999" but I can live with that. Other than that it seems to be working perfectly. Thanks!

Indeed. I figured it wasn't worth using extra bytes to fix such a small quirk. Anyways, on my fork of the firmware the "last frequency" (137MHz) is not scanned anyways.


⚠ Web Busy Light Demo has degraded performance

In e64a819, Web Busy Light Demo (https://workfromhome.capricehosting.com/) experienced degraded performance:

HTTP code: 200
Response time: 594 ms

Resolved: Web Busy Light Demo performance has improved in 069dbef after 16 minutes.


Helm chart not being published on merge

📜 Description
I don’t have the pipeline visibility to tell if this is intentional so apologies if I’m missing it but there’s some great changes being added to the chart and merged into main that aren’t getting published to the chart repo. Obviously we can just build the charts locally but it would be awesome to get the new chart version via the chart repo. Would help a tone with automation.
👟 Reproduction steps

New version merged
Ci/cd started (GitHub actions)

👍 Expected behavior
New version should be published to GitHub’s chart repository
👎 Actual Behavior
No new version is published. Step is skipped.
☸ Kubernetes Version
N/A
⎈ Helm Version
N/A
📊 Chart Version
1.0.3 and up
☁ Cloud Provider
On-premises
🛠 Custom Values
No response
📃 Additional Context
No response
👀 Have you checked if this bug has been reported before?

[X] I have searched existing issues and didn't find a similar bug report

Are you willing to submit a PR?
No, not at this time

An updated release would be very much appreciated! Thanks! (Re: #3)

Heya @dasantonym , sorry I didn't reply to you just yet, but I just tried a publish of 1.0.4. It'll take a few moments to build.
It would be good to automate this as you say, but just hoping I can get the newer features out for you.

Okay, it looked like it published quicker than I thought. Let me know if the new release works for you?


make install

hello，Is there any way to make install after so that my mmdet is not the latest version？

The same problem.

The same problem.


Include heart rate data

Investigate transferring heartrate data to Strava

Easiest way to do this seemed to be to include it in the gpx file.
Initially looking at the heart rate data that Runkeeper sends to zapier, its timestamps are independent of the waypoint timestamps. I imagined I might be able to append the heart rate data to a run by updating the Strava activity. However, the API documentation isn't overly clear on how to do this.
Instead, I discovered that you can extend GPX waypoints with heart rate data using a schema Garmin have created. Testing uploading this to Strava, Strava recognises the heart rate measurements.
Therefore, I wrote a function to work out the most recent heart rate measurement at the timestamp of each waypoint, and included this in the GPX. Not as granular as having an independent stream of heart rate data, but simpler to implement.
The Garmin schema also allows for sending cadence (steps per minute) in the same way, but Runkeeper doesn't seem to export to the Zapier endpoint, even though it does capture this data.

Included in v1.1.0


fix(javascript): expose sub algoliasearch client's type

🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/APIC-590
Changes included:
Sub algoliasearch client's type are not exposed, which can be useful in complex implementations like in the Crawler. It also help to differentiate which client does what.
🧪 Test
CI :D

I think we did it before it was published as multiple packages but it's no longer useful imo, e.g: you can import SearchClient with @algolia/client-search instead of { SearchClient } from 'algoliasearch' wdyt?

Wouldn't typescript complain until you've added @algolia/client-search as a dependency if so? IIRC it was something people were complaining about

There was a bump on the open-issue for v4: https://github.com/algolia/algoliasearch-client-javascript/issues/1080#issuecomment-1154125872

yeah okay for this issue I get it 👌🏻