Fix dangerous forget-all operation which drops all snapshots

What does this PR change? What problem does it solve?
restic forget --keep-tag=SomeUnusedTag --dry-run

This command would drop all snapshots. This is very dangerous and probably unwanted.
A suggested fix (see forum) is to only allow --keep-tag together with other --keep-* options.
While working on this, I noticed that another if case seem to have no effect, see comment in diff.
Was the change previously discussed in an issue or on the forum?
See also https://forum.restic.net/t/delete-all-snapshots-in-one-command-is-this-feature-intentional/6923/3
Fixes #4569
Checklist

[ ] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[ ] I have added documentation for relevant changes (in the manual).
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[ ] I have run gofmt on the code in all commits.
[ ] All commit messages are formatted in the same style as the other commits in the repo.
[ ] I'm done! This pull request is ready for review.

Hi Jakob,
Thank you for working on this. I'm the original issue OP. I've never looked at restic code before, but I have a few comments, though of cause they may be misplaced, as I have only looked at this tiny part of the code.

lines 148-152 looks like it contains a bug (which would be a prevous bug), namely that it is missing withinWeekly in the check, both the old and your new copy. Probably called d.Weekly. Also there's the --keep-within duration, though it possible the duration type cannot be negative.

line 159, the ending if, should also allow the --keep-within duration which isn't matched by your two new allKeep*Undefined. Or add keep-within to the allKeepWithinXUndefined

It might make sense to keep the initial if-check even if handled elsewhere as well, or maybe convert it into some kind of assert. That makes this method self-contained in its requirement of valid options. I mean just by reading this small method, one can verify that regardless of what goes on elsewhere in the sourcecode, this method does not allow --keep-* with negative values or with missing positives.

Best Alex

Hey Alex, thanks for the great feedback and the catched bugs! :-)
I'll fix that in the next commits on this PR. But today it's too late.
I'm happy to get more feedback later on! It's also my first time contributing to restic and first time using the go language ^^
In case you're not familiar to github PRs, note that you can also add comments to the code in the "Files changed" tab.

I should try to add some tests in cmd_forget_*test.og...

Happy Christmas! May I just ping on this PR? Maybe someone has time for review over the holidays :)

Oh, that sounds like a more complicated fix. I'd be happy if you take over, I'm afraid I don't have the expertise and time, currently.

Michael I also like that option, and as I can recall from the forum, some would indeed appreciate that delete-all option. I think its fine with the '--unsafe-allow-remove-all', though adding the extra requirement of path/host/tag also sounds good.
I also won't have time at the moment and have yet evolved my go-mastery.

I've opened https://github.com/restic/restic/pull/4764 as a replacement for this PR. Different from my previous suggestion that PR currently always forbids the complete deletion of a whole snapshot group if any --keep-* policy was specified. This means that forget --keep-tag invalid will always result in an error, even if --unsafe-allow-remove-all was specified.


Some aliases cannot be used for custom web parts

Category

[ ] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

Expected or Desired Behavior
When creating a a web part I should be able to use any alias, unless the schema validates my alias not to be valid. If I use the name DividerWebPart my web part should be possible to use together with the oob divider web part.
Either any alias should be valid, or the schema should validate. What happens if two vendors opt for the same alias?
Observed Behavior
If you add an oob divider webpart and a custom webpart which alias is DividerWebPart the page shows as blank.
Steps to Reproduce
Create a new web part and set the webpart alias to DividerWebPart. Add the oob divider and the custom web part to the page, and the page will go blank after saving on refresh.
Change the alias to MyDividerWebPart and it works just fine.

This is actually by design. Alias is uniquely identified in the page. We might revisit this in the future if needed. Should be updated in the docs.

Good enough, and guidance could be to always prefix the alias in some way to make sure it’s unique.


Call wirecell deconvolution from dataprep

The current DUNE reco strategy runs a dataprep module which writes full (i.e. no ROI filtering) processed waveforms as recob:Wire to the event data store which are used as input to the WCT (wirecell) module which does deconvolution and ROI finding (and more?) writing another recob::Wire container to be used in hit finding. There are two problems with this approach:

The intermediate container is left in the event store taking up memory only to be eventually discarded
There is no opportunity to run dataprep tools on the deconvoluted data to explore additional noise removal, run alternate ROI finders, generate metric plots such as noise vs. channel, or make dataprep event displays.

Point 2 could be addressed by running another dataprep module after WCT without ROI finding but that implies yet another recob::Wire entry in the event data store and even another if we utlimately decide to  then run another WCT module to do the ROI finding. A second approach would be to somehow insert dataprep tools in the WCT processing chain but this looks difficult as WCT has a private notion of tools and configuration. The subject of this issue is a third approach where WCT sequences are wrapped as dataprep tools so they can be called in the dataprep processing chain. If successful, it will then be possible to run the full signal processing chain (raw data to ROIs suitable for hit finding ) in a dataprep module with options to take algorithms for decovolution and ROI algorithms from WCT or from other sources.

The first step here is to demonstrate it is possible to create a dataprep tool that runs a WCT algorithm. On that subject, I had some email exchanges with Brett and edited summaries follow. From me after poking into the WCT code:

I found
 virtual bool operator()(const boost::any& anyin, boost::any& anyout) = 0
in IFunctionNode —> IFrameFilter but I don’t see the connection to OmnibusSigProc.
Does that provide this operator()?

Responses from Brett:

   Link against libWireCellSigProc.so and create a concrete instance of
   OmnibusSigProc.  On that instance, you will need to call the methods
   defined by IConfigurable and IFrameFilter.

and:

Call default_configuration(), alter what it returns as desired and pass
to configure().

Then call operator()(const IFrame::pointer& in, IFrame::pointer& out).

-Brett.

I intend to take this as a starting point.

The proper thing is to develop a WCT flow graph node that runs dataprep code.
Your current strategy will defeat DUNE's ability to benefit from multi-threading in this critical data and computationally intensive processing stage.  Unless, that is, you are willing to reinvent all the MT wheels that WCT already provides.
Alternatively, DUNE can use WCT's existing Noise Filter node, instead of dataprep, which does not introduce these new problems and which has been tested on PDSP data.

Brett: Let's have that discussion in a forum outside this ticket. I would like to use this as a place to track progress toward the goal above. Briefly, we appear not to agree on the proper way to proceed and I believe the most useful place to use MT is within the tool/algorithms. Thanks.

We just had a two day workshop showing how that is not a good strategy.

It sounds like there is a problem with support for certain features in art that make a simple fcl solution to this problem not effective in terms of memory conservation.  A solution that currently is clumsy but ought not to be would be to  define instances of dataprep and wirecell that work only on one APA at a time.  We can do this now, by restricting processing in our current chain to one APA, and replicate the trigger path entries that run dataprep and then wirecell with appropriate configurations.
The problems with this are:

As David says, this does not solve the memory problem -- the intermediate recob::Wire data products sent from each dataprep instance to the corresponding WireCell instance still clutter up memory.  And post-WireCell producing of even newer versions of recob::Wire will consume further memory

Initialization of multiple instances of WireCell will take memory and CPU.  And may not even work (maybe?), though most art modules are written so that they can be multiply instantiated.

Problem #1 can be solved if we can remove produced products from the event.  Currently this throws an exception.  Kyle has been open to removing this exception.  It is meant to protect sloppy programmers, but any time there is a memory deallocation feature provided in code, it is possible to shoot ones self in the foot and we should accept that possibility.  I suppose we could add an optional argument with a default value to  removeCachedProduct() so that the default behavior remains for all existing code.  We would then write simple deleter modules to clean up memory no longer in use.  It would be good to remove cached products anyway as it provides freedom to use art's event memory for temporary data, make a plot, save it, etc.
Another feature we have asked for but not gotten is "eager writing".  If we were interested in writing these cooked waveforms out to a file but not clutter memory with them we cannot use art's ROOT I/O to do that.  Kyle asked at the workshop for what priority to assign to flushing data out to output files before the event processing is finished.
Another feature I am not sure really exists in art yet is module-level parallelism.  The schedule parallelism in art seems tied to event processing, and communication with Kyle and others seems to indicate that if we want sub-event parallelism we'd have to use TBB ourselves.
WireCell allows us to do all of these things but we must code within it and do our own file i/o on output for example.  Since WireCell is further down the link stack from dataprep and is also experiment agnostic, one would have to define plug-ins and callbacks to call the dataprep tools from within WireCell.
There are lots of benefits to using art's ROOT I/O (single output file, config info, provenance, etc).  But we cannot yet stream output to it.

Tom:
I agree that we want the option to do the signal processing (raw data to ROIs at least) one APA or CRU at a time. Even if we can remove recob:Wire objects from the event data store, it does not make sense to create these objects and is preferable to pass them in the transient format used by dataprep or wirecell. I would like to be able to make multiple handoffs, e.g. noise removal in dataprep, deconvolution in wirecell and then ROI finding in dataprep. More complicated sequences including metric evaluation and event display should also be supported.
Avoiding recob::Wire conversions and event data store I/O is best accomplished by running a single module that gets input from a raw data input tool, runs a sequence of algorithms and writes the recob:Wire objects to be used as in put to hit finding. Either dataprep or wirecell can provide the module with its own algorithms. Here I am proposing to investigate enabling the former to additionally call the algorithms from latter. I will likely next work on the reverse problem: running dataprep algorithms in the wirecell module.
I expect that once we have single APA/CRU processing we will fit in 2 GB and there will no longer need the complexity of having multiple threads processing an APA and can run with a single (computational) thread. If this is not the case, then we will likely want something like TBB threads within each algorithm because processing a new APA just adds to the memory load. This then implies simultaneous processing of multiple APAs and events to try to keep the additional threads busy. It still remains interesting to offload some of the processing (e.g. FFTs) to GPUs but I expect this will be most useful within algorithms.
We are then left with difficult choice of running the dataprep module or wirecell module which has up to now avoided with ugly choice of running both. There are strong arguments for each module though naturally I prefer the first. I don't want to have that discussion here. I believe this a difficult problem that the SW architecture group should take up.

I am trying to instantiate OmibusSigProc but get this error

Consolidate compiler generated dependencies of target dunedataprep_DataPrep_Service_ThresholdNoiseRemovalService_service
/home/dladams/proc/build/dev01/workdir/srcs/dunedataprep/dunedataprep/DataPrep/WctTool/test/test_wirecell.cxx:7:10: fatal error: WireCellSigProc/OmnibusSigProc.h: No such file or directory
    7 | #include "WireCellSigProc/OmnibusSigProc.h"
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.

I looked in the code for example but only found an include for the OmnibusSigProc source file:

(base) mac> grep -r OmnibusSigProc wire-cell-toolkit/ larwirecell/ | grep include
wire-cell-toolkit//sigproc/src/OmnibusSigProc.cxx:#include "WireCellSigProc/OmnibusSigProc.h"
(base) mac>

I presume the above error comes because dunedataprep does not have dependency on wire-cell-toolkit. I tried adding larwirecell to ups/product_deps but that alone did not help. I then additionally added this line to the top-level CMakeLists.txt:

find_ups_product( wirecell )

and instead of the above error, I saw:

[ 26%] Building CXX object dunedataprep/dunedataprep/DataPrep/WctTool/test/CMakeFiles/test_wirecell.dir/test_wirecell.cxx.o
In file included from /cvmfs/larsoft.opensciencegrid.org/products/wirecell/v0_23_0/Linux64bit+3.10-2.17-e20-prof/include/WireCellAux/Logger.h:44,
                 from /cvmfs/larsoft.opensciencegrid.org/products/wirecell/v0_23_0/Linux64bit+3.10-2.17-e20-prof/include/WireCellSigProc/OmnibusSigProc.h:4,
                 from /home/dladams/proc/build/dev01/workdir/srcs/dunedataprep/dunedataprep/DataPrep/WctTool/test/test_wirecell.cxx:7:
/cvmfs/larsoft.opensciencegrid.org/products/wirecell/v0_23_0/Linux64bit+3.10-2.17-e20-prof/include/WireCellUtil/Logging.h:14:10: fatal error: spdlog/spdlog.h: No such file or directory
   14 | #include "spdlog/spdlog.h"
      |          ^~~~~~~~~~~~~~~~~
compilation terminated.

I added spdlog in the cmake file and then got this error:

[ 26%] Building CXX object dunedataprep/dunedataprep/DataPrep/Service/CMakeFiles/dunedataprep_DataPrep_Service_InterpolatingAdcMitigationService_service.dir/InterpolatingAdcMitigationService_service.cc.o
In file included from /cvmfs/larsoft.opensciencegrid.org/products/wirecell/v0_23_0/Linux64bit+3.10-2.17-e20-prof/include/WireCellUtil/Point.h:5,
                 from /cvmfs/larsoft.opensciencegrid.org/products/wirecell/v0_23_0/Linux64bit+3.10-2.17-e20-prof/include/WireCellUtil/Pimpos.h:5,
                 from /cvmfs/larsoft.opensciencegrid.org/products/wirecell/v0_23_0/Linux64bit+3.10-2.17-e20-prof/include/WireCellIface/IWirePlane.h:12,
                 from /cvmfs/larsoft.opensciencegrid.org/products/wirecell/v0_23_0/Linux64bit+3.10-2.17-e20-prof/include/WireCellIface/IFrame.h:5,
                 from /cvmfs/larsoft.opensciencegrid.org/products/wirecell/v0_23_0/Linux64bit+3.10-2.17-e20-prof/include/WireCellIface/IFrameFilter.h:6,
                 from /cvmfs/larsoft.opensciencegrid.org/products/wirecell/v0_23_0/Linux64bit+3.10-2.17-e20-prof/include/WireCellSigProc/OmnibusSigProc.h:6,
                 from /home/dladams/proc/build/dev01/workdir/srcs/dunedataprep/dunedataprep/DataPrep/WctTool/test/test_wirecell.cxx:7:
/cvmfs/larsoft.opensciencegrid.org/products/wirecell/v0_23_0/Linux64bit+3.10-2.17-e20-prof/include/WireCellUtil/Configuration.h:4:10: fatal error: json/json.h: No such file or directory
    4 | #include <json/json.h>
      |          ^~~~~~~~~~~~~
compilation terminated.

Then I added the jsoncpp product (json didn't work) and got to this:

In file included from /cvmfs/larsoft.opensciencegrid.org/products/wirecell/v0_23_0/Linux64bit+3.10-2.17-e20-prof/include/WireCellSigProc/OmnibusSigProc.h:13,
                 from /home/dladams/proc/build/dev01/workdir/srcs/dunedataprep/dunedataprep/DataPrep/WctTool/test/test_wirecell.cxx:7:
/cvmfs/larsoft.opensciencegrid.org/products/wirecell/v0_23_0/Linux64bit+3.10-2.17-e20-prof/include/WireCellUtil/Array.h:30:10: fatal error: Eigen/Core: No such file or directory
   30 | #include <Eigen/Core>
      |          ^~~~~~~~~~~~
compilation terminated.

Adding eigen didn't fix this but when I also added this to the local cmake file:

include_directories(${EIGEN3_INCLUDE_DIR})

I did get past this and can see syntax errors in my code.

I pushed my changes to develop. I first had to pull renetchanges including this odd package tag: v09_69_01g01 which I left in produt_deps.

Poling around in wirecell toolkit, it looks like SimpleFrame i\s the concrete IFrame subclass that I should use to pass data to and retrieve data from wirecell. Later I might look at making my own class with the IFrame interface wrapped around dataprep structures.

I am creating a utility DpWctFrameConverter that is constructed from an AdcChannelDataMap and provides methods to extract or set its waveforms to or from an IFrame object.

@brettviren I see that IFrame holds a interger identifier "ident". Is that simply geometry identifier or does it indicate the stage of processing? Most important, when we apply a transformation, will the output IFrame have the ident as the input? Thanks. --da

After some time off for school breaks, I am back working on the dataprep-wirecell frame converter. I at least want to get it to build so I can push the code to develop. After updating header and source, I can nowI can now compile. To get things to link, I added many missing inline directives in AdcChannelData.h and added find_library directives for the wirecell aux library.


HttpError: Not Found when publishing GitHub repo with scaffolder

Expected Behavior
No error
Current Behavior
GitHub API returns not found sometimes as it's eventually consistent
Code here is bombing out:
https://github.com/backstage/backstage/blob/master/plugins/scaffolder-backend/src/scaffolder/actions/builtin/publish/github.ts#L169-L186
Possible Solution

Thinking of either trying to retrieve from GitHub API or just adding in some retries
Steps to Reproduce

scaffold with a template that adds github teams
attempt a few times, I've had it happen to me 2 out of ~15 tries
...

Context
Other blocks in the GitHub publisher have try .. catch .. log but that's a terrible pattern as the user will likely never see it.
This needs proper hardening.
Discussed with @benjdlambert at https://discord.com/channels/687207715902193673/913812564750766150/913819958193045536
Your Environment

NodeJS Version (v14):
Operating System and Version (e.g. Ubuntu 14.04):
Browser Information:

Awesome, thanks for taking a look!

@timja did you find the time to look into this? Otherwise I'd like to give it a go. 😄

I had a brief go at it, but didn't finish it off. Feel free

I'm starting work on this this week 🎉

@jhaals maybe you can reasign me on this issue to reflect above? 🙏

Done!

So looking a bit further into this I can see we use @octokit/rest in quite a lot of places. Should we go about this by updating usage from the deprecated package in only the scaffolder (to fix this specific issue) or should I go for migrating away from the package all together as a cleanup and then we can come back to this? 🤔
WDYT @benjdlambert @jhaals ?

FWIW I started work with a commit only migrated the scaffolder backend to get an idea of the impact. So for it looks fine: https://github.com/lunarway/backstage/commit/8d49dc2eef3b2cd279c85a7d71b3c7d971950c3c

Hmm I think it's fine to have a go and migrate us off in the scaffolder at least for now. Looks like there could be some migration stuff with the GitHub App authentication that we might need to double check that it's gonna work but looks ok so far I think!

Got it. I'll send a PR for that as a first 👍

With the upgrade to octokit in #9189 I have been unable to recreate this issue locally.
It was released in<EMAIL_ADDRESS>Should we close this issue and reopen if it turns up again?
By default octokit will retry requests 3 times with a 1 second base timeout (with some jitter and exponensial backoff).

Sure nice work

I hit this twice today after upgrading to Backstage 0.71.1. confirmed

more specific error message would also help :)

Ignore me. This was due to wrong team passed to access 🤦♂
However I still like to see better logging to understand better what is failing

I guess that is covered by #9208? 🙏

Not sure if it is covered by that that's a git error message rather than an API error message

Created https://github.com/backstage/backstage/issues/10160 as a follow up


[private-bamoe-issues#244] DMN - Add implicit type conversion of date to date and time when necessary

Fixes https://github.com/bamoe/private-bamoe-issues/issues/244

Add an implicit date to date and time conversion in DMN FEEL evaluation, based on this rule:
"When the type of the expression is date and the target type is date and time, the expression is converted to a date time value in which the time of day is UTC midnight (00:00:00)."
Acceptance criteria:
Implicit conversion is implemented in FEEL expressions, where date is used as the input type of the expression and the result needs to be date and time.
New code is 100% covered with tests.

Notes:

it is not possible to modify the FEELFunction itself because it does not receive the required type; so, conversion is executed inside DMNContextEvaluator
currently only LocalDate are transformed, and generated object is a ZonedDateTime
small refactoring of DMNContextEvaluator has been done to improve test coverage

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.
build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

for pull request checks
Please add comment: Jenkins retest this

for a specific pull request check
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] tests

for a full downstream build

for jenkins job: please add comment: Jenkins run fdb
for github actions job: add the label run_fdb

a compile downstream build please  add comment: Jenkins run cdb

an upstream build please add comment: Jenkins run upstream

for quarkus branch checks
Run checks against Quarkus current used branch
Please add comment: Jenkins run quarkus-branch

for a quarkus branch specific check
Run checks against Quarkus current used branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-branch

for quarkus main checks
Run checks against Quarkus main branch
Please add comment: Jenkins run quarkus-main

for a specific quarkus main check
Run checks against Quarkus main branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-main

for quarkus lts checks
Run checks against Quarkus lts branch
Please add comment: Jenkins run quarkus-lts

for a specific quarkus lts check
Run checks against Quarkus lts branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] quarkus-lts

for native checks
Run native checks
Please add comment: Jenkins run native

for a specific native check
Run native checks
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native

for native lts checks
Run native checks against quarkus lts branch
Please add comment: Jenkins run native-lts

for a specific native lts check
Run native checks against quarkus lts branch
Please add comment: Jenkins (re)run [drools|kogito-runtimes|kogito-apps|kogito-examples] native-lts

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

PR job #1 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-drools/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-drools -u https://github.com/apache/incubator-kie-drools/pull/5657 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/drools/job/main/job/pullrequest_jobs/job/drools-pr/job/PR-5657/1/display/redirect
Test results:

PASSED: 21874
FAILED: 2

Those are the test failures:

org.kie.dmn.core.DMNStronglyTypedSupportTest.testDateAndTime[KIE_API_TYPECHECK]
expected:<...me.LocalDate), "from[]YearMonthDay"=1999-1...> but was:<...me.LocalDate), "from[StringToDateTime"=2015-12-24T00:00Z (java.time.ZonedDateTime), "from]YearMonthDay"=1999-1...>

org.kie.dmn.core.DMNStronglyTypedSupportTest.testDateAndTime[BUILDER_DEFAULT_NOCL_TYPECHECK]
expected:<...me.LocalDate), "from[]YearMonthDay"=1999-1...> but was:<...me.LocalDate), "from[StringToDateTime"=2015-12-24T00:00Z (java.time.ZonedDateTime), "from]YearMonthDay"=1999-1...>

@tarilabs
I add the ticket content in the description of this PR.

based on the title alone I would have expected a modification at the FEEL level,
yes, but I failed to find how to do that, and that's why I add you as reviewer.
Tibor currently is not available, and I would like to keep going on in the meantime.
Surfing the code I found the FEELFunction for date, but those does not receive other parameters to allow a different object return; and, IINW, the choose of the function to call is done automatically based on the expression itself, so maybe I'm missing some critical point

I really wish I could dedicate unlimited time, but I'm currently on sick leave.
The things I noticed, are:
A.
This seems a behavioural change introduced with DMNv1.5, I'd suggest first to bump the DMN engine to this level of spec conformance by parsing the metamodel, or (much less ideal) guard it under feature flag. That would also save you troubles of "old behaviour" version can be fix-pointed to the previous Drools releases. Myself and @baldimir discussed what bumping to DMNv1.5 entails during hand-over.
B.
Provided my understanding this is for DMNv1.5 is confirmed, this coercion seems to me applicable in 2 places:

function invocation,
and type-conformance in the DMN level.

if that is indeed the semantic discussed,
B.1.
For function invocation, you could consider to do similarly to:
https://github.com/apache/incubator-kie-drools/blob/9a3128e47f13d7c0e85fe8ff00e573ec769d2f9d/kie-dmn/kie-dmn-feel/src/main/java/org/kie/dmn/feel/runtime/functions/BaseFEELFunction.java#L239-L261
this coerces the actual parameter in the case of singleton lists.
You could consider similar, analogous strategy for the date->date and time coercion.
You will need to implement the coercion in the actual parameter being set in the CandidateMethod (eg actual parameters value as is, except for the coerced date -> date and time)
B.2.
For type-conformance in the DMN level, you could consider to do similarly to:
https://github.com/apache/incubator-kie-drools/blob/9a3128e47f13d7c0e85fe8ff00e573ec769d2f9d/kie-dmn/kie-dmn-core/src/main/java/org/kie/dmn/core/impl/DMNRuntimeImpl.java#L675-L687
and
https://github.com/apache/incubator-kie-drools/blob/9a3128e47f13d7c0e85fe8ff00e573ec769d2f9d/kie-dmn/kie-dmn-core/src/main/java/org/kie/dmn/core/impl/DMNRuntimeImpl.java#L442
by introducing the additional coercion rule during type-conformance.
Hope this explain better why a modification in the DMN boxed Context does not seem the appropriate solution, but that's just me.
This is not a small task, so I would also suggest splitting it into subtasks.
I really hope this will help you.

@tarilabs

[...]
I really hope this will help you.

Gosh, it really help a lot.
Sorry, I did not know you also were in sick leave, thanks again for all that help.
I'll start from what you wrote and see where I'll get to.
Thanks again and take care!

PR job #2 was: UNSTABLE
Possible explanation: This should be test failures

Reproducer
build-chain build full_downstream  -f 'https://raw.githubusercontent.com/${AUTHOR:apache}/incubator-kie-drools/${BRANCH:main}/.ci/buildchain-config-pr-cdb.yaml' -o 'bc' -p apache/incubator-kie-drools -u https://github.com/apache/incubator-kie-drools/pull/5657 --skipParallelCheckout
NOTE: To install the build-chain tool, please refer to https://github.com/kiegroup/github-action-build-chain#local-execution

Please look here: https://ci-builds.apache.org/job/KIE/job/drools/job/main/job/pullrequest_jobs/job/drools-pr/job/PR-5657/2/display/redirect
Test results:

PASSED: 21874
FAILED: 3

Those are the test failures:

org.kie.dmn.core.DMNRuntimeTest.testDateAndTime[false]
expected:<...me"=2015-12-24T00:00[Z (java.time.Zoned]DateTime), "fromYear...> but was:<...me"=2015-12-24T00:00[ (java.time.Local]DateTime), "fromYear...>

org.kie.dmn.core.DMNStronglyTypedSupportTest.testDateAndTime[KIE_API_TYPECHECK]
expected:<...me.LocalDate), "from[]YearMonthDay"=1999-1...> but was:<...me.LocalDate), "from[StringToDateTime"=2015-12-24T00:00 (java.time.LocalDateTime), "from]YearMonthDay"=1999-1...>

org.kie.dmn.core.DMNStronglyTypedSupportTest.testDateAndTime[BUILDER_DEFAULT_NOCL_TYPECHECK]
expected:<...me.LocalDate), "from[]YearMonthDay"=1999-1...> but was:<...me.LocalDate), "from[StringToDateTime"=2015-12-24T00:00 (java.time.LocalDateTime), "from]YearMonthDay"=1999-1...>


Suboptimal names in 0.2.0

There seems to be too many hyphens added to OpenAPI-generated-code in Penny
Current code is not fully updated with 0.2.0. You can clone the repo from the link above, resolve package versions and rerun the command-plugin if you need to test with Penny.
public typealias Repository = Components.Schemas.repository
- public typealias User = Components.Schemas.simple_user
- public typealias Organization = Components.Schemas.organization_simple
- public typealias PullRequest = Components.Schemas.pull_request
- public typealias SimplePullRequest = Components.Schemas.pull_request_simple
+ public typealias User = Components.Schemas.simple_hyphen_user
+ public typealias Organization = Components.Schemas.organization_hyphen_simple
+ public typealias PullRequest = Components.Schemas.pull_hyphen_request
+ public typealias SimplePullRequest = Components.Schemas.pull_hyphen_request_hyphen_simple
public typealias Issue = Components.Schemas.issue
public typealias Label = Components.Schemas.label
- public typealias InstallationToken = Components.Schemas.installation_token
- public typealias NullableUser = Components.Schemas.nullable_simple_user
+ public typealias InstallationToken = Components.Schemas.installation_hyphen_token
+ public typealias NullableUser = Components.Schemas.nullable_hyphen_simple_hyphen_user
public typealias Contributor = Components.Schemas.contributor
- public typealias PullRequestReviewComment = Components.Schemas.pull_request_review_comment
- public typealias DiffEntry = Components.Schemas.diff_entry
+public typealias PullRequestReviewComment = Components.Schemas.pull_hyphen_request_hyphen_review_hyphen_comment
+ public typealias DiffEntry = Components.Schemas.diff_hyphen_entry
public typealias Commit = Components.Schemas.commit
- public typealias SimpleCommit = Components.Schemas.simple_commit
- public typealias Committer = Components.Schemas.simple_commit.committerPayload
+ public typealias SimpleCommit = Components.Schemas.simple_hyphen_commit
+ public typealias Committer = SimpleCommit.committerPayload
- public typealias Installation = Components.Schemas.simple_installation
+ public typealias Installation = Components.Schemas.simple_hyphen_installation

This also affects stuff like functions names:
- try await context.githubClient.repos_list_pull_requests_associated_with_commit(...
+ try await context.githubClient.repos_sol_list_hyphen_pull_hyphen_requests_hyphen_associated_hyphen_with_hyphen_commit(...

Hi @MahdiBM, this was the subject of proposal SOAR-0001 to address conflicts of names when characters not legal in Swift identifiers are used.
A good way to have the names exactly what you want them to be is to only use characters legal in Swift identifiers in your OpenAPI document. That is, a-zA-Z0-9_. Any other characters get turned into deterministic and unique codes as you see above.
Closing as this is expected behavior.

This is GitHub's OpenAPI document though, I don't think I can change that without non-trivial changes.
Part of a proposal or not, i would say this behavior should be changed in someway, just because it makes the openapi file of GutHub look like this.

Please review the goals of the project, which includes respecting the identifiers in the OpenAPI document, as opposed to trying to "prettify" them, which leads to name conflicts where there are non in the OpenAPI document.
One example is GitHub's +1 and -1 names, which do not represent valid Swift identifiers, so we had to come up with a scheme that produces deterministic identifiers, which don't conflict.
A few options to apply your preferences to how the generated code is used or looks:

Pre-process the OpenAPI document using custom logic to reflect your preferred names (for the things that don't affect the wire format). For example, this works well for schema names and operation identifiers. It cannot be applied to property names, which affect the coding keys and the deserialization, those have to be unchanged.
Wrap the generated client in your own library, which vends the types and functions in the names you prefer.

Check out the discussion in SOAR-0001, as our goal is to support the full breadth of the OpenAPI specification, we practically cannot process the identifiers from OpenAPI without risking conflicts. In this project, that is considered more important than the conciseness of generated code.
None of this would be a problem if OpenAPI only allowed a-zA-Z0-9_ in all identifiers, but alas, it allows more characters, and the generated has to deal with them somehow, in a way that doesn't produce conflicts.

It seems that you're already using typealiases, so I hope this change shouldn't affect your codebase much? As you discovered, typealiases are another good way to use whatever names you prefer for the generated types.

About typealiases, yeah they will help. But I'll still need to change those an also change the function calls.
A big deal, but not a deal breaker. The function calls will still look bad.

The function calls you can change, that's operationId from the OpenAPI specification. It doesn't impact the wire format, so you can update those in your copy of the OpenAPI document.
From the specification:

Unique string used to identify the operation. The id MUST be unique among all operations described in the API. The operationId value is case-sensitive. Tools and libraries MAY use the operationId to uniquely identify an operation, therefore, it is RECOMMENDED to follow common programming naming conventions.

Unfortunately, GitHub didn't follow the recommendation of making the names code-friendly with foo/bar-baz, you could just update them to like foo_bar_baz or fooBarBaz, whichever you prefer, and that'll be the exact function name you'll get in Swift.

Trying to update Penny, I once again bumped into this problem.
I wonder if the problem is common enough to be worth trying to address 🤔
Changing GitHub's OpenAPI document is not feasible, there are way too many hyphens.
Only other option remaining is to just endure the names.

I find typealiases are a quick and easy way to make the names more friendly, and for larger projects wrapping the generated API in your own layer (which is helpful for testing and layer separation anyway).

Typealiases only solve a part of the problem. There are other things like function names which are much more cumbersome to "alias". This just results in way too porr of a user exprience for any kind of these openapi documents.
There could be some settings to e.g. "replace hyphens with empty-string/dash unless it causes a name conflict" that'll probably be best of both worlds.

Testing-wise we haven't had a need to do such things as we just use a mocked ClientTransport.

"Unless it causes a conflict" is surprisingly difficult, trust me I tried, it'd basically require a rewrite of the generator to keep a global, stateful registry of types and the order in which you'd generate types would affect the names you get. Seemed to us like a too high of a price to pay. Complicating the generator just to try to subjectively prettify names is explicitly out of scope of the project: https://swiftpackageindex.com/apple/swift-openapi-generator/0.3.1/documentation/swift-openapi-generator/project-scope-and-goals
The proposal SOAR-0001 is meant to be the solution to how the generator processes names, and there'd have to be a very good new design that isn't going to overly complicate the generator (such as by keeping a global type registry), which would continue to accept all the OpenAPI documents we accept today, for us to consider changing the naming logic. But since it's also very subjective, I feel simply respecting the OpenAPI document is the most defensible position, as every other solution would a) produce conflicts or overly complicate the generator and b) be subject to bikeshedding, since "pretty names" is not a universally agreed RFC, so we'd likely spend a ton of time just on agreeing on the naming logic itself.
As documented here, if you care about a vended API, wrap it in a hand-written one: https://swiftpackageindex.com/apple/swift-openapi-generator/0.3.1/documentation/swift-openapi-generator/api-stability-of-generated-code

A rather easy solution occured to me: find and replace "hyphen" with "_". Solves all problems. Works like a charm!
We already do mess around with the GitHub OpenAPI documentation so I can't say a find-and-replace like this is "cumbersome" compared to what we already do, although it makes Xcode lag a decent amount (next time will just use VSCode as is the case already for a bunch of other Swift-related activities. It's (basically) already better for anything other than writing code, and only in Swift, IMO).
I still think this should be something to improve on. Maybe there could be a long term plan, or an issue about it being something at the back of your mind. Maybe someday someone finds a proper way to do it.

It won't work like a charm. We used to (pre-SOAR-0001) replace all illegal characters with an underscore.
GitHub failed to compile, because it has both "+1" and "-1", which we both turned into "_1".
See the discussions on the forums about SOAR-0001. This is surprisingly non-trivial, and we spent weeks exploring it. At this point, we'd need to see some new information to change course, but based on the information available when SOAR-0001 was in review, the current behavior is the best overall solution.

O I just meant in my specific case it solves my problem, otherwise I know the generator itself can't be this careless and just do a find-and-replace 😅

Ah gotcha. In your case you could instead find and replace the operationId in the OpenAPI document to give it names that don't require any escaping.

Landed in 1.6.0 as the new idiomatic naming strategy: https://swiftpackageindex.com/apple/swift-openapi-generator/main/documentation/swift-openapi-generator/soar-0013


fix(curriculum): increase readability of the introduction

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Personally I don't see this wording as better, just different.

Maybe just me then, I had to read the sentence 3/4 times to understand what was meant in the original version.

I'm with @jeremylt on this one. Different wording doesn't necessarily mean better - and changing this would require re-translation so I'm not sure it's worth the overhead.

I'm on the fence with the new rewording. Now its a small change that might effectively be English only. The updated flow after my suggestion is a bit clearer. It might be a happy-to-glad sort of thing though.


Pack 0.15.0

This change updates the setup-pack action to install 0.15.0 by default.

@buildpacks/distribution-maintainers I'd recommend a release once this is merged.


fix(module:tabs): tabs add btn disappear after all tab closed

There is a problem with the tabs component. When opening and closing the tab page and the Add button, if all the open tab pages are closed, the Add button will not be found. This problem can be repeated in the official website document demo.
Tabs组件有一个问题，当开启关闭tab页和添加按钮时，如果把开启的tab页全部关掉，添加按钮也找不到了，这个问题在官网文档demo中即可复现。
https://ng.ant.design/components/tabs/en#components-tabs-demo-card-top
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Cool, thanks for your contribution!


change\update service account

It appears I may have done something incorrectly during setup, and request-a-team app is posting the welcome message in teams and sending emails as me instead of as the service account.  (It is correctly adding the actual service account to the Team, but there is an error in the logicapps flow when I am not a member or owner as it can't post the welcome message, etc. and either way, this is not the desired end behavior.)  Where can I go to update the account for posting in Teams and sending the Email?
Thank you!

@momoangel Did you import the Power App and Flows AS the service account? i.e. did you login as that user to Power Apps and Power Automate to do the import? It's also important to set up the connections in Power Apps and Power Automate to use the service account when importing them. If you don't do this you will see the above behaviour.


dynamic generation of slider

Slider doesn't work when it is produced after page loading, currently, I wait for a response from the user and when I get this response, I run ng-repeat on this response to generate multiple instances of a directive that contain this slider with static values for options, now the sliders doesn't work and produce NaN everywhere. at the same time, I tried static model for the ng-repeat where the user choice isn't included, the sliders loaded with the page loading and they were working fine
how it is, with dynamic loading:

Could you try to provide a demo of what you are trying to do please? I don't really understand actually..

the slider outside ng-repeat works fine but the ones inside ng-repeat are inconsistent
https://jsfiddle.net/e3m6pfLw/
press ctrl to choose more than one item

You JSFiddle doesn't work at all.

I am sorry cant deal with JSFiddle, can you copy the code to local?

I fixed you fiddle and found out that you should init your slider options in the controller function instead if the link one: http://jsfiddle.net/wqy091kk

Or in the pre-link function: http://jsfiddle.net/dsk2s5mm/


Incorrect type signature for Version.upgrade

As a public interface, Version has the following signature for upgrade:
https://github.com/dfahlander/Dexie.js/blob/master/src/public/types/version.d.ts#L5
upgrade(fn: (trans: Transaction) => void): Version;

As a class and in the documentation, it has the following signature:
https://github.com/dfahlander/Dexie.js/blob/master/src/classes/version/version.ts#L63
upgrade(upgradeFunction: (trans: Transaction) => PromiseLike<any> | void): Version

The difference in the argument type prevents from returning the promise when using the upgrade function and can lead to bad usage.

Thanks for finding! PR welcome!


Update Phala Network info in README

Thanks for commut.
Check, please Phala profile also within our Explorer aka "l2beat for privacy" project: https://explorer.web3privacy.info/project/phala-network
It's also open-source & actual data is missing.


Update Project.toml to use Julia 1.6

Note that the package version number is bumped to 0.3.0 as well (to allow patch releases on older versions, but I highly doubt it will be needed).

@haampie Please merge if you think this is right- or edit directly as necessary.


Create bazel-contrib/bazel_features

Following the Bazel feature detection in Starlark proposal, we would like to start the new bazel_features repository to provide helpers that perform feature detection for Bazel.

Must use an open-source license, preferably Apache-2.0.

SG

Must have wide applicability in the community.

This repository is expected to be useful for rule sets which need to keep compatibility with different Bazel versions.

Must have a clear point of contact who answers questions from the SIG.

From Bazel team: @meteorcloudy @Wyverald @comius
From community: maybe @fmeum, more community owners are welcome.

Must be “production quality”: clear README or other documentation outlining the goal of these rules, how to use them etc.

There are already some details in the design doc, we'll compose a README file based on that.

generated API documentation include examples of use

Basic instructions and examples will be available. Documentation for each function can probably be generated with Stardoc, but those functions should be very simple and self-explanatory anyway.

tests that are running continuously

Minimal unit and integration tests should be implemented.

Must reply to issues/PRs in 2-3 weeks (exact service level agreement TBD)
Must have more than one person who is committed to review/approve PRs
We recommend encoding this as a CODEOWNERS file.

Initially this will be maintained by the Bazel team (@meteorcloudy @Wyverald @comius), but volunteering community maintainers are very welcome and appreaciated!

Must publish semver releases.

This project itself should always be backwards compatible, so following semver is no problem.

Optional: follow the same release pattern as the rules-template does.

Not an actual build rule, so not applicable.

Must work with LTS Bazel version

Probably going to be the most Bazel compatible project ever.

/cc @cgrindel @alexeagle

I'm in!

Okay, https://github.com/bazel-contrib/bazel_features/ is created!


Hugo: enable Reliability Service for Peru and TS

needs own fragility-function for Peru

also needs fragility functions for TS (for each country)

In the short term, Hugo has provided me with some dummy-data for Peru. Will add this.


Anyway to integrate this to hacs?

Cool project!! thanks!!!
Anyway to integrate this to hacs?

It's already a part of HA integrations. Is there any reason to make it part of HACS?

Oups i didn't know that it was on integration. Thanks.


Can't find the keybinds for Freecam

Mod Version: [Forge] Freecam 1.1.7 for MC 1.16
Description: Basically the title. I can't find the keybinds for the mod anywhere, I can confugre the mod but I find the keybinds.

Ah you’re right, thanks for letting me know. I forgot to test the keybinds for the forge versions. I will release a hotfix soon

Just released version <IP_ADDRESS> to fix this.


Issue Summar You are not authorized to access SendGrid, please contact Support.

Issue Summar
Hello, I'm sorry when I log in my account it occurs "You are not authorized to access SendGrid, please contact Support.", and my username and password are all right.
my username :leoraymond
<EMAIL_ADDRESS>Please help me!

Expected content
Actual content
Link to page:

Hello @leoraymond,
We're sorry you're having this issue. You can access support contact options by going to https://support.sendgrid.com and clicking "Trouble Logging in?". From there, you can tell us a little more about your problem without having to log in, and one of our fantastic support people will get back to you. Hope this helps!
SendGrid Docs Team


JwtIssuerValidator returns Issuer not Validated

Hi,
I am getting the following error in the logs when I use the OICD token provided by my IAS instance
2022-01-23T17:33:40.367+0000 [APP/PROC/WEB/0] OUT 2022-01-23 17:33:40.367  WARN 7 --- [nio-8080-exec-1] c.s.c.s.t.validation.ValidationResults   : Issuer is not trusted because issuer 'xxxxxxxx.accounts400.ondemand.com' does not provide a valid URI (missing http scheme). Please contact your Identity Provider Administrator.
2022-01-23T17:33:40.367+0000 [APP/PROC/WEB/0] OUT 2022-01-23 17:33:40.367 DEBUG 7 --- [nio-8080-exec-1] c.s.c.s.t.validation.CombiningValidator  : Validator that caused the failed validation: com.sap.cloud.security.token.validation.validators.JwtIssuerValidator
2022-01-23T17:33:40.367+0000 [APP/PROC/WEB/0] OUT 2022-01-23 17:33:40.367 DEBUG 7 --- [nio-8080-exec-1] c.s.c.s.t.validation.CombiningValidator  : Object of type com.sap.cloud.security.token.SapIdToken that caused the failed validation:
And my token does not contain http in iss field.
I checked my configurations in IAS tenant and the issuer has https in issuer name.
Do I need to change something in the IAS configuration?
Also, is there a workaround for this?
Thank You

The issue is resolved.
We need to change the tenant settings at
application & resources -> tenant settings -> SAML 2.0 Configuration -> Identity Provider Settings -> Name
from the URI without https to the one with it


@ nccgroup, Please how can i Replace all my values at once? and get the response

Firstly Thank you for the amazing tool,  i have a question Please, Assuming i have to replace one Request Header Value,  e.g CSRF Header,  and Maybe two Cookies Value  Request. , when i make the setting is autorepeater, it is actually replacing one at a time, which will not let me get desire result.
Am thinking of a situation where by when the Replacement setting are Set Autorepeater use those setting at once. what i have notice till now is that, Autorepeater usually Replaces  CSRF Header Value , only in the First Request and in the Next "Modified Request" it return the Old  CRSF Header that was with the original request again, and Replaces one of the  Cookies Value, then next it will Replace, the last Cookie Value Set, and keep Original  CSRF Header Value, so there will be no way all the Settings are Completely Replace at once ,or together at the same time ,  in the Modified Request. this make it difficult to get the actually desire result or to know if the test was successful. i don't know if am doing anything wrong. am waiting for your response.
Warm Regards
Dere sewa

hey @workfast108, to replace multiple values within one request, set all of the values you want replaced within the "Base Replacement" table. Each replacement in the "Base Replacement" table will be applied to the request at the same time. Afterwords, AutoRepeater will make a new request for each replacement set within the "Replacements" with every replacement in the "Base Replacement" table already applied. This should allow you to replace multiple headers and cookies at the same time.
Thanks,
Justin

OMG ,Honestly your quick response, just  humble me, you are great Bro. please let me juz give you example of what i wanna do here: Please what is the Best Match Up to use in this scenario
I need to Replace to Cooke Value and One Header Value  all at once, i mean at one time how do i set the Base Replacement and the second Replacement
In the Header Side: i want to Replace
Header Name       Header Value
X-CSRF-Token: 91053b50cfc2e0ee0
inside  the Cookie
cookie name                   Cookie value
Workfast_website=   2a23c7487acb7467c406235adf57
cookie Name                Cookie value
csrf_token_website=  91053b50cfc2e0ee
i want to Replace  all  the above  cases with
Header name             Header Value
X-CSRF-Token:  c5c047284d2b51f
======================================================
Cookie Name                          Cookie Value
workfast_website= cafef35317e0b1b89b65199
Cookie name                  Cookie Value
csrf_token_website= c5c047284d2b51fa041822b9e2
Thank You

hey @workfast108,
If I'm understanding correctly, you'd want something along the lines of:
Base Replacements
Type: Request Header
Match: X-CSRF-Token: 91053b50cfc2e0ee0
Replace: X-CSRF-Token: c5c047284d2b51f
Type: Match Cookie Name, Replace Value
Match: Workfast_website
Replace: cafef35317e0b1b89b65199
Type: Match Cookie Name, Replace Value
Match: csrf_token_website
Replace: c5c047284d2b51fa041822b9e2
Replacements
You don't need to specify any replacements here if you only want to change those three values, however, add any additional replacements they have the modifications from above applied.
Thanks,
Justin

@justinmoore-ncc  Thank You for Everything, it worked Perfectly well, Please i have this last Question to ask you , it as to do with ID's , assuming ID's is in the URL Parameters, and i have some ID's as a Post request body Parameter's  as well.
suppose  (1)  URL is like  PUT /users/459461979/ and i want to replace it with " PUT  /users/411839370/
and (2) the Post request body , i have things like ,"user_id":459461979,  and what to replace it with  " "user_id: 411839370
what "Type" combination  Best Suit the URL  scenario and what "Type" Combination  Best Suit the Post body request Parameter?
Thank You
Dere Sewa

Hey @workfast108,
The following replacement will replace all instances of "459461979" with "411839370".
Base Replacements
Type: Request String
Match: 459461979
Replace: 411839370
Which: Replace All
Thanks,
Justin

@justinmoore-ncc  Thanks for your great response i appreciate
Warm regards
Dere Sewa

@workfast108 no problem, I'm happy to help.

Hi @justinmoore
I have a situation where I need to use - match parameter name and replace its value .
For example I have GET request like this: GET https://exmple.com?dateStart=xyzee
Now when I use - match parameter name and replace its value and set parameter name as dateStart and value as superman
Autorepeater just works perfectly fine : https://exmple.com?dateStart=superman
Now the problem is
I have a post request in which there is json body like this
{"userId":"US-DG46","dateStart":"2022-03-20","dateEnd":"2022-04-20"}
Now for the same above condition autorepeater doenot replace value of dateStart in json body parameter.
How can I achive this . Please help !
Thanks you


Changed Minimum Limit for Trimming File or Dir Path in Windows

Thanks for your contribution! Please replace this text with a description of what this PR is changing or adding and why, list any relevant issues, and review the contribution guidelines below.

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.

Note that this repository uses Gerrit for code reviews. Your pull request will be automatically converted into a Gerrit CL and a link to the CL written into this PR. The review will happen on Gerrit but you can also push additional commits to this PR to update the code review.

Fix of https://github.com/dart-lang/sdk/issues/54386

I think we need to consider relative path. Relative path can be less than 3 in length.
  final dir = Directory(r'a');    <-- this is relative path
  final dir = Directory(r'a/');   <-- this PR strips last separator?
  final dir = Directory('');  <-- current directory

Yes you are correct @glanium , @mraleph pointed this same in discord and had a new commit which only have the 3 char limit on absolute path

Phew windows(dart-sdk-windows-try) tests are green 😀

@codesculpture that one does not actually run any tests. I added vm-win-release-x64-try manually.
(Normally I would have just added Cq-Include-Trybots: luci.dart.try:vm-win-release-x64-try footer to make sure Windows will run but when you make a CL through PR integration that's not possible because AFAIK Copybara would just clobber CL description every time cc @athomas @sortie )

If everything work normal when i directly make a cl (i thought non-googlers cant do this, is it?)
`
Upload a CL, add reviewers from OWNERS files, and allow automatic submission. git cl upload --send-mail --r-owners --auto-submit
`
Got this from BUILDING.md

@codesculpture git cl upload should certainly work just fine for non-Googlers. Maybe some of these flags --send-mail --r-owners --auto-submit don't work - but they are not really necessary. git cl upload (without any flags) should be just enough.

Windows is green 🟢

@codesculpture git cl upload should certainly work just fine for non-Googlers. Maybe some of these flags --send-mail --r-owners --auto-submit don't work - but they are not really necessary. git cl upload (without any flags) should be just enough.

Alright will do that instead of making pr @mraleph . Thank you so much for the help and guidance !

@codesculpture git cl upload should certainly work just fine for non-Googlers. Maybe some of these flags --send-mail --r-owners --auto-submit don't work - but they are not really necessary. git cl upload (without any flags) should be just enough.

Next time, Alright will do that instead of making pr @mraleph . Thank you so much for the help and guidance !

Did the flags actually not work or was it just never tried? AFAIK these flags work for non-Googlers as well. If not, please open an issue.
@parlough, I believe these work for you?

I dint tried @athomas , i just assumed that it would not. Sorry for that and also i mentioned

@parlough, I believe these work for you?

Yeah they work fine as far as I've experienced. I prefer to manually pick reviewers but I've seen others rely on the --r-owners flag and it work.

I dint tried athomas , i just assumed that it would not. Sorry for that and also i mentioned.

No worries! This PR through GitHub works too and is extremely appreciated! Thank you.
If you do want to try Gerrit through git cl upload next time though and have any problems, please open an issue :)

Thanks for the info @parlough

I made a few minor comments at https://dart-review.googlesource.com/c/sdk/+/345201

Thanks for the comments @brianquinlan , Resolved it kindly check

This is just a question from my curiosity is there anyway to move the comment from unresolved status to resolved in gerrit, this can done in github by just clicking "Resolve Conversation". Since brian made few comments i actually resolved and made commits also i need to make the comments to "resolved" status in gerrit.

@codesculpture you can respond to comments in the UI and there will be a checkbox to mark it resolved (usually you can just click done). Then you press a button to send all your responses (which are by default stores like drafts and only visible to you).

Thanks @mraleph , will look on that

Two more super small nits: https://dart-review.googlesource.com/c/sdk/+/345201

Two more super small nits: https://dart-review.googlesource.com/c/sdk/+/345201

Sorry, I planned to include the link u shared, but ended up i just visited the link and read but forget to add in the code and commit.
Resolved Now @brianquinlan

Now one more small nit ;-) One of the problems with using the github workflow is that you don't get the dart format presubmit check.
We (meaning the Dart team) should fix that.

I can run that manually this time, well in morning (i live in GMT+5:30) its mid night here

Done running dart format and resolved comments @brianquinlan


Does lstautogobble work with \lstinputlisting?

Sorry if this has been answered elsewhere, but I'm trying to use something like:
\lstinputlisting[autogobble=true,firstline=40,lastline=47]{foo.rs}

@SamWilsn Well gobble doesn't work with \lstinputlisting (see the listings doc or this TeX-SX question) so I doubt autogobble is intended to work with it


suggestion: table search in new query window should not be case sensitive

SQL Operations Studio Version: sqlops 0.23.6 (8a3011756318a2ded1e6e84332230a2b2bf9c544, 2017-11-06T21:51:43.232Z)
OS Version: Windows_NT x64 10.0.17074

@kburtram This should be fixed in this PR -
https://github.com/Microsoft/sqlopsstudio/commit/9035f296df1dbc778dfb0a761ef4250a8b028f39
in
https://github.com/Microsoft/sqlopsstudio/blob/6e4c828959928a8e9c308e4fa55a7dc7a5579070/src/sql/base/browser/ui/editableDropdown/dropdownTree.ts#L94


Write "Accessibility Audit" Guide

Writer: @susanjrobertson
Review: @Wilto @iamjessklein

I have two reviewers here because we are both experimenting with the concept of "guides" for ODK as well as writing one specifically about accessibility.

I have a very rough draft of this going in Use Canvas: https://usecanvas.com/susanjrobertson/accessibility-guide/7P0tTobTDkPxNeh35419Mw
I'm aiming this at designers and designers who may code, so keeping the talk of code very light, if there are other topics I should cover, let me know @iamjessklein or @pamela-drouin.

I left some comments in the document (I show up as anonymous). Could
probably use another proofreader besides me!
On Tue, Nov 22, 2016 at 10:05 AM, Susan Robertson<EMAIL_ADDRESS>wrote:

I have a very rough draft of this going in Use Canvas:
https://usecanvas.com/susanjrobertson/accessibility-
guide/7P0tTobTDkPxNeh35419Mw
I'm aiming this at designers and designers who may code, so keeping the
talk of code very light, if there are other topics I should cover, let me
know @iamjessklein https://github.com/iamjessklein or @pamela-drouin
https://github.com/pamela-drouin.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bocoup/opendesignkit/issues/218#issuecomment-262317911,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFrJSdqRG_jZ8EZuENBGIqlVqU_CcHxEks5rAy7_gaJpZM4K4qzX
.

--
Pam Drouin
UX Designer @Bocoup

@iamjessklein I think I lost my draft of this one, so it's no longer in progress anymore :(

I put this on hold as I want to focus on the other issues first and help out with any code things for open graph.


LateInitializationError occurs when used in isolate

E/flutter (24445): [ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: LateInitializationError: Field '_instance@2084288322' has not been initialized.
E/flutter (24445): #0      SodiumPlatform._instance (package:sodium_libs/src/sodium_platform.dart)
E/flutter (24445): #1      SodiumPlatform.instance (package:sodium_libs/src/sodium_platform.dart:21:41)
sodium_libs version: 1.2.0
flutter version: 2.8
used like this:

await Executor().execute(
    arg1: str1,
    fun1: (String demo) async {
      // this is an isolate
      final sodium = await CustomSodiumInit.init();   // this line occurs LateInitializationError
      final encData = sodium.crypto.secretBox.easy(...);
      // ...
    },
  );

CustomSodiumInit code:

// ......
static Future<sodium.Sodium> init({
    @Deprecated('initNative is no longer required and will be ignored.')
        bool initNative = true,
  }) =>
      _instanceLock.synchronized(() async {
        if (_instance != null) {
          return _instance!;
        }

        // Comment out this line or an exception(Unhandled Exception: UI actions are only available on root isolate) will occur
        // WidgetsFlutterBinding.ensureInitialized();
        _instance = await SodiumPlatform.instance.loadSodium();
        if (!kReleaseMode) {
          if (_instance!.version < _expectedVersion) {
            // ignore: avoid_print
            print(
              'WARNING: The embedded libsodium is outdated! '
              'Expected $_expectedVersion, but was ${_instance!.version}}. '
              '${SodiumPlatform.instance.updateHint}',
            );
          }
        }
        return _instance!;
      });

sodium_libs version 1.1.1 will work, but 1.2.0 not

SodiumPlatform.instance is initialized automatically by flutter when the plugin is loaded. This happens as part of the WidgetsBinding.ensureInitialized() in normal code. This is not automatically executed when launching a new isolate, thus it does not get initialized. It did work with older versions, as back then flutter did not support loading dart plugins automatically.
This is not a bug, but expected behaviour. You have to do one of the following things to use the plugin in a different isolate:

Simply call WidgetsBinding.ensureInitialized() in your Isolate
Use a plugin like flutter_isolate that takes care of that for you.
Manually initialize the instance. This requires you to now which platform you are on and select the correct implementation. See https://github.com/Skycoder42/libsodium_dart_bindings/tree/main/packages/sodium_libs/lib/src/platforms where you can find the concrete implementations. For example, to initialize it for Android, you could call SodiumAndroid.registerWith().


Fix x not in list error in memory websocket manager

Codecov Report

Merging #368 (1c0bc1b) into main (df326f3) will not change coverage.
The diff coverage is 0.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main     #368   +/-   ##
=======================================
  Coverage   72.91%   72.91%
=======================================
  Files         184      184
  Lines        8807     8807
  Branches     1441     1441
=======================================
  Hits         6422     6422
  Misses       2198     2198
  Partials      187      187

Files
Coverage Δ

...tor/websocket/managers/memory_websocket_manager.py
65.45% <0.00%> (ø)

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


Optional redirect URI

A redirect URI is not needed for retrieving client tokens. Should it be optional in all the corresponding arguments? If so, maybe it could even be a parameter of user_authorisation_url instead of the constructor, as it can have multiple values even on one application.

I overlooked the need in request_user_token. Better to keep it in the constructor, but it could still be optional for client-token-only situations.


v0.8.2 release does not include binaries

It appears as though the tagged v0.8.2 release does not include exe or msi installers as other releases have in the past. I use the msi installer link in the Chocolatey package scripts that I maintain. Will these be posted? Thanks

Seems the build failed. Looking into it.

Something seems to go wrong when it pulls the repo. I'm unable to log into the machine to see exactly what happens without pushing changes, and I'm not able to repro on any other commit.
I'm travelling today and tomorrow, so I don't have that much more time to look into this, so I made a 0.8.3 release instead, and the build+release worked :man_shrugging:
Any problems with not having the 0.8.2 version available?

No, that's fine by me. I'll skip right ahead to 0.8.3. Thanks!


Use subset name on task export

Motivation and context

Fixes https://github.com/cvat-ai/cvat/issues/6451
How has this been tested?

Checklist

[ ] I submit my changes into the develop branch
[ ] I have created a changelog fragment
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

New Features

Enhanced task export functionality: Images are now organized into folders based on subsets for better data organization.

Tests

Introduced new test methods and updated existing tests to validate the new subset-based export functionality.
Added new data entries for improved test coverage and verification.

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

Project coverage is 83.34%. Comparing base (f1726c4) to head (1f82204).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #8176      +/-   ##
===========================================
- Coverage    83.39%   83.34%   -0.05%
===========================================
  Files          388      388
  Lines        41305    41306       +1
  Branches      3854     3854
===========================================
- Hits         34446    34428      -18
- Misses        6859     6878      +19

Components
Coverage Δ

cvat-ui
79.63% <ø> (-0.09%)
:arrow_down:

cvat-server
86.67% <100.00%> (-0.02%)
:arrow_down:


help([MAT-SELECT]): [Size of select panel when using multiple prop]

What are you trying to do?
I'm trying to use the mat-select-trigger and when I use the prop 'multiple', the size of select panel grows.
The size of select panel must have the size of the mat-form-field.
What troubleshooting steps have you tried?
::ng-deep .cdk-overlay-pane {
  .mat-select-panel {
    min-width: 100% !important;
    transform: translateX(40px) !important;
  }
}

With the code above on the SCSS of my component, I'm able to reduce the width size of select panel, but when I reduce it, the orientation of select panel goes to left so I use transform to put it on 'center'. Like this:

But the problems with this 'solution' are:

All the selects of my app are affected.
It's not the default appearance of the mat-select.

Reproduction
<mat-form-field fxFlex floatLabel="always" shouldLabelFloat="false" appearance="outline">
    <mat-label>Reparações</mat-label>
    <mat-select [formControl]="reparacoesId" multiple>
        <mat-select-trigger>
            {{temReparacoes() ? (reparacoesId.value[0].repairType | translateEnum: 'reparacao') : ('')}}
            <span *ngIf="reparacoesId.value?.length > 1">
                (+{{reparacoesId.value.length - 1}})
            </span>
        </mat-select-trigger>
        <mat-option panelClass="reparacoes-options" *ngFor="let reparo of this.item.avaliacao.reparos"
            [value]="reparo.id">{{reparo.repairType | translateEnum: 'reparacao'}}</mat-option>
    </mat-select>
</mat-form-field>

With the code above I have the next resulte:

Steps to reproduce:

On <mat-select [formControl]="reparacoesId" multiple> just use the multiple prop. If you remove the multiple prop, the select turn to normal appearance.

Result that I'd like to have
Well, I just want this appearance...

... but with the checkboxes and the right width of a normal mat-select.
Environment

Angular: 7.2.0
CDK/Material: 7.3.7
Browser(s): Chrome
Operating System: Elementary os.

This is behaving as expected. The select panel is already pretty narrow to begin with and adding a checkbox without extending it is going leave very little space for the option's text.

Yeah, as @crisbeto mentioned, this is intentional. It's designed so that the option text aligns with the trigger text. At the time this was implemented, that's what the Material Design spec showed. However, at this point the spec has changed https://material.io/components/menus#exposed-dropdown-menu


temporal cortex atrophy

If this is a request for a new term, please provide us with the following information.

Preferred term label (e.g., asplenia)

temporal cortex atrophy

Synonyms (e.g., absent spleen)

atrophy of temporal lobe

Textual definition (the definition should be understandable even for non-specialists. Include a PubMed ID or URL(s) to refer to any relevant article(s) that provides information about the suggested term).

acquired atrophy of the lower lateral part of the cerebral hemisphere

Any additional notes to clarify the meaning or use of the term. Please provide a PubMed ID or URL(s) for the source of this information.

https://www.sciencedirect.com/science/article/pii/S0091305796004200?via%3Dihub

Suggested parent term (Please look in the hierarchy of the MP using the MP Browser or other browsers such as OLS and find the place in the MP where the new term best fits)

forebrain atrophy, abnormal temporal lobe morphology

If you would like a nanoattribution, please indicate your ORCID id or provide a label such as MGI:sbello (organization, first initial-last name)

https://orcid.org/0000-0003-2307-1226

MP:0021008

I think the synonym "atrophy of temporal lobe" should be a broad rather than an exact synonym of temporal cortex atrophy MP:0021008.
See temporal lobe UBERON:0001871 and temporal cortex UBERON:0016538. Per UBERON, temporal cortex is defined as: "Gray matter of the temporal region of the neocortex, located in the temporal lobe in gyrencephalic animals"
The EQ for MP:0021008 currently uses "temporal lobe", rather than "temporal cortex" to reflect the given textual definition. Perhaps we need both terms: temporal lobe atrophy and temporal cortex atrophy.

Changed term label to lobe. The issue hereis that lobe and cortex are used differently in rodent vs human. We need to revisit the labels used in MP eventually.


Support dailymixes

That hasn't been implemented for real. context-resolve doesn't work here.

Fixed by 892b1ce0f5569e4b68af7bac47d2710c9bab9e64


Improve margin_order selection algorithm

Would need to change the margin_pixel_k calculation to lookup based on value of margin_threshold
https://github.com/astronomy-commons/hipscat-import/blob/main/src/hipscat_import/margin_cache/margin_cache_arguments.py#L62


Device waiting for ping

Hello,
When I click the phone, console log says:
INFO[0000] Starting WebSocket server
INFO[0004] Device '000080xxxx' USB connection ready, waiting for ping..
2021/01/14 13:03:19 handle_events: error: libusb: interrupted [code -10]
2021/01/14 13:03:20 handle_events: error: libusb: interrupted [code -10]
2021/01/14 13:03:22 handle_events: error: libusb: interrupted [code -10]
iPhone: XS Pc: Mac mini Catalina 10.15.3
Thanks

Hi.
Sometimes it happens. Usually the following sequence of steps helps:

Disconnect/connect the device from usb
Run QuickTime, New Movie Recording, select your device in Camera list (red circle in the middle). Verify that you see your device screen in QT. Close QT.
Optionally. Run quicktime_video_hack
Try ws-qvh again.

In some rare cases you may need to reboot your device.

Hi.
Sometimes it happens. Usually the following sequence of steps helps:

Disconnect/connect the device from usb
Run QuickTime, New Movie Recording, select your device in Camera list (red circle in the middle). Verify that you see your device screen in QT. Close QT.
Optionally. Run quicktime_video_hack
Try ws-qvh again.

In some rare cases you may need to reboot your device.

To reboot device from cli:
idevicediagnostics -u <udidnumber> restart libimobiledevice
To cycle power on usb port:
uhubctl -a 2 -p <portnumber> uhubctl

To reboot device from cli:
idevicediagnostics -u <udidnumber> restart libimobiledevice
To cycle power on usb port:
uhubctl -a 2 -p <portnumber> uhubctl

Thank you for quick response. I fixed the problem with resetting device. By the way, I encountered new problem. DeviceAgent-Runner installed successfully but I could not control device. In my Mac-2019 machine with Big Sur, control works but in Mac-mini Catalina I could not control my device. if you want, I can open new issue for this problem.
Thanks

Thank you for quick response. I fixed the problem with resetting device. By the way, I encountered new problem. DeviceAgent-Runner installed successfully but I could not control device. In my Mac-2019 machine with Big Sur, control works but in Mac-mini Catalina I could not control my device. if you want, I can open new issue for this problem.
Thanks

By the way, I encountered new problem. DeviceAgent-Runner installed successfully but I could not control device. In my Mac-2019 machine with Big Sur, control works but in Mac-mini Catalina I could not control my device.

Make sure that WDA runs properly (Starting WebDriverAgent).
It could be caused by newer iOS version on your device than supported by installed Xcode version (e.g. for iOS 14.3 you will need Xcode 12.3) or problems with code signing (Real Device Setup).

By the way, I encountered new problem. DeviceAgent-Runner installed successfully but I could not control device. In my Mac-2019 machine with Big Sur, control works but in Mac-mini Catalina I could not control my device.

Make sure that WDA runs properly (Starting WebDriverAgent).
It could be caused by newer iOS version on your device than supported by installed Xcode version (e.g. for iOS 14.3 you will need Xcode 12.3) or problems with code signing (Real Device Setup).

I updated Mac iOS version and Xcode version it works. Thanks

I updated Mac iOS version and Xcode version it works. Thanks


Use forked display-link dependency.

https://github.com/servo/display-link/tree/no-transmute was created to work around https://github.com/BrainiumLLC/display-link/issues/3, which was identified as a risk back in https://github.com/BrainiumLLC/display-link/issues/1.

@bors-servo r+

:pushpin: Commit d937663 has been approved by jdm

:hourglass: Testing commit d9376639eec3056aa5fd47a3c3f571ec442072ae with merge 9fb158d2a6da3761652494b6778eea537b1ad11c...


#210: Project data extendable feature

Added feature to:

Make project data block extendable.
Providing an option to open project data in a modal window by clicking "Project Data" button.

@AkshayMuthal a better UI, instead of a modal, would be to implement on the project data section something similar to the Show/Hide at https://bulma.io/documentation/elements/box/

@tdruez

Added a button to Show/Hide project data.
Copy button in the top right corner.
Is this UI fine?
Will update PR after this change.

@AkshayMuthal the buttons should be integrated inside the data box, similar to https://bulma.io/documentation/elements/box/

Implemented in https://github.com/nexB/scancode.io/pull/777


feat: add use_multithreading (bool) and workers (int) flag to get_report_html along with exponential backoff.

Optionally use multithreading
Retry when 429 with exponential backoff
Made changes only where get_report_html is relevant will add to other if you want it.
Basic tests are also included

Please let me know if you need any changes.

thanks!

Deployed as version 0.0.14
Use poetry update or pip install --upgrade sec-api-io in the projects where you use sec-api-io

cc @INF800


Adding a docs.rs badge

This provides a super convenient way of getting to the current crate documentation

Thanks for the help, @spacekookie!

Cool, this project is already looking quite professional with all the status badges! :+1:


how to setup dns for ch to connect pods/sevices in different namespace

Hi,
My CH (in clickhouse namespace) could not reach out kafka pod/service (in posthog namespace). I tried to configure namespaceDomainPattern in CH, did not work.
  namespaceDomainPattern:  "posthog.svc.cluster.local"

The error I got from my CH pod:
2022.07.01 00:02:47.009864 [ 328 ] {} <Error> StorageKafka (kafka_session_recording_events): [rdk:FAIL] [thrd:posthog-posthog-kafka:9092/bootstrap]: posthog-posthog-kafka:9092/bootstrap: Failed to resolve 'posthog-posthog-kafka:9092': Name or service not known (after 2ms in state CONNECT, 28 identical error(s) suppressed)
2022.07.01 00:02:47.009993 [ 273 ] {} <Error> StorageKafka (kafka_session_recording_events): [rdk:ERROR] [thrd:app]: ClickHouse-chi-ch-install-dev-shard0-0-0.chi-ch-install-dev-shard0-0.clickhouse.svc.cluster.local-posthog-kafka_session_recordi: posthog-posthog-kafka:9092/bootstrap: Failed to resolve 'posthog-posthog-kafka:9092': Name or service not known (after 2ms in state CONNECT, 28 identical error(s) suppressed)

from the ch pod, I only see this one, but I want to add something like this one "posthog.svc.cluster.local". Not figure out how to add it.
cat /etc/resolv.conf
nameserver <IP_ADDRESS>
search clickhouse.svc.cluster.local svc.cluster.local cluster.local cn-northwest-1.compute.internal
options ndots:5

if you need to connect to pods and services
you don't need to change nameserver or change namespaceDomainPattern
use standartd kubernetes  name conversion
service_name.namespace.svc.cluster.local (or just service_name.namespace)
or
pod_name.service_name.namespace.svc.cluster.local (or pod_name.service_name.namespace)
for posthog namespace
just use posthog-posthog-kafka.posthog:9090 if you have service name posthog-posthog-kafka in posthog namespace
look https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/ for details

@Slach From the log, you can see that the CH pod could not resolve the posthog service, since the posthog is in different namespace.
In my Posthog namespace, I do have posthog-posthog-kafka.
kubectl -n posthog get svc
NAME                                 TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                      AGE
posthog-posthog-kafka                ClusterIP   <IP_ADDRESS>    <none>        9092/TCP                     5h42m

The question is that the CH pod does not know this service is in different namespace. When it tries to talk to this service, it will think this posthog-posthog-kafka is in the same namespace as CH pod. Then the error coma out.
If the pod has something like this "posthog.svc.cluster.local" in their /etc/resolve.conf, then the pod can resolve this posthog-posthog-kafka service in posthog namespace. Then it will be able to talk this service correctly.
That's reason why I am asking you how to configure this on CH pod. For now, the /etc/resolve.conf in CH pod is
cat /etc/resolv.conf
nameserver <IP_ADDRESS>
search clickhouse.svc.cluster.local svc.cluster.local cluster.local cn-northwest-1.compute.internal
options ndots:5

@Slach can you take a look this again? The question is that the CH pod does not know that the posthog-posthog-kafka  is in different namespace. From the error message, you can see that, the CH talk to posthog-posthog-kafka   directly. Did not add posthog namespace. This is the reason I am asking where to add this dns setting, I did not find in the installation file.
2022.07.01 04:07:54.507213 [ 284 ] {} <Error> StorageKafka (kafka_plugin_log_entries): [rdk:FAIL] [thrd:posthog-posthog-kafka:9092/bootstrap]: posthog-posthog-kafka:9092/bootstrap: Failed to resolve 'posthog-posthog-kafka:9092': Name or service not known (after 1ms in state CONNECT, 28 identical error(s) suppressed)


chore(release): v1.17.0 🎉

:robot: I have created a release beep boop
1.17.0 (2024-07-27)
Features

practs: bump practs and resolve audit (e1e7844)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ehmpathy/type-fns/releases/tag/v1.17.0 :sunflower:


Pypi version outdated

After the fix on PR #4 the Pypi version is outdated.

What Pypi version? Do you men the pip version? Python version?

Yes, for the installation via pip install jiwer.
https://pypi.org/project/jiwer/#history

You mean a new release on pypi is necesary? (ping @nikvaessen )

Yes, there is a workaround by installing using the git repo pip install git+https://github.com/jitsi/asr-wer, but if you use pip install jirew will install the version without the fix on PR #4.

I've now bumped the version on pipy to 1.3.1

Thanks, btw awesome package 😃 !!!


Merge the range query functionality into the basic query endpoint

Combine search functionality so that just one search endpoint is required.
Also, facilitate fieldvalue isNotIn [array of values]

Syntax suggestion for a query that combines the range overlap with the field/value selection, where the field value must be not in a set of values:
{
    ":overlapsWithTextAnchorRange": {
        "source": "http://adsdasd",
        "start": 12,
        "end": 134
    },
    "body.type": {
        ":isNotIn": [
            "Line",
            "Page"
        ]
    }
}

json field names starting with : indicate special query functions, others either field names in the annotation, or function parameters.


add locator to all calls of assertElementExists

Motivation/Description of the PR

Adds the Locator to every call of assertElementExist, because it is not optional and leads to Element "{null: undefined}" was not found by text|CSS|XPath if missing.

Applicable helpers:

[x] WebDriver
[x] Puppeteer
[ ] Nightmare
[ ] REST
[ ] FileHelper
[ ] Appium
[x] Protractor
[x] TestCafe
[x] Playwright

Applicable plugins:

[ ] allure
[ ] autoDelay
[ ] autoLogin
[ ] customLocator
[ ] pauseOnFail
[ ] coverage
[ ] retryFailedStep
[ ] screenshotOnFail
[ ] selenoid
[ ] stepByStepReport
[ ] stepTimeout
[ ] wdio
[ ] subtitles

Type of change

[ ] :fire: Breaking changes
[ ] :rocket: New functionality
[x] :bug: Bug fix
[ ] :clipboard: Documentation changes/updates
[ ] :hotsprings: Hot fix
[ ] :hammer: Markdown files fix - not related to source code
[ ] :nail_care: Polish code

Checklist:

[ ] Tests have been added
[ ] Documentation has been added (Run npm run docs)
[ ] Lint checking (Run npm run lint)
[ ] Local tests are passed (Run npm test)

thank you!


polybar: init at 3.0.4

Polybar is a nice X11 status bar in the vein of i3bar or xmobar.
https://github.com/jaagr/polybar
Ignore the source branch name-- this developer moves fairly quickly :)
Reviewed points

[ ] package path fits guidelines
[ ] package name fits guidelines
[ ] package version fits guidelines
[ ] package build on ARCHITECTURE
[ ] executables tested on ARCHITECTURE
[ ] meta.description is set and fits guidelines
[ ] meta.license fits upstream license
[ ] meta.platforms is set
[ ] meta.maintainers is set
[ ] build time only dependencies are declared in nativeBuildInputs
[ ] source is fetched using the appropriate function
[ ] phases are respected
[ ] patches that are remotely available are fetched with fetchpatch

Possible improvements

[ ] Is there an easier way to maintain optional dependencies?
[ ] Is there any way to read the config.environment setting on NixOS?

Comments

Fairly sure I'm read to have this merged in, provided tests start passing.


updated compute-options.md to note that ACS has been deprecated

made note that ACS has been deprecated.  https://azure.microsoft.com/en-us/updates/azure-container-service-will-retire-on-january-31-2020

Docs Build status updates of commit 33550c1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/microservices/design/compute-options.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit d37eac1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/microservices/design/compute-options.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@larryms Great point - Since it's being retired, I think the article should not even mention it as a recommendation. I updated the paragraph to point to Azure Marketplace for Docker and DC/OS, as per the  announcement that you linked to.


Submission_Group166_L05_2310013_2310038_2310016_2310641

Policy 1 (Big stock big product):
This algorithm combines heuristic and greedy approach, designed to solve the 2D CSP with an acceptable level of waste in exchange for higher speed and lower computational complexity. Unlike the second policy based on the ILP solver to find the most optimal solutions by iterating through every possible combinations, this algorithm prioritizes speed and the ability to scale the problem to a greater level via usage of vectorized operations and efficient mathematical calculations like cross-correlation to process the environment. The main idea is to prioritize fitting the largest possible product into the largest possible stock, since with a larger stock we can reasonable obtained a greater amount of cut products while also minimizing waste

Policy 2 (MILP):
The second policy approaches the problem as an ILP, by modeling the problem through decisions variable for stock choice, product choice, and product position, with constraints, we can effectively solve for the most optimal solutions by iterating every possible combinations of decisions through the 'milp' solver from library 'scipy.optimize'. This ensures a low amount of waste and an efficient usage of space though with bigger scales, the ILP calculations become exponentially more complex and harder to feasibly apply in practice

Please revise the PR in Dec 16. Otherwise, your group will get 0 score for code.

Sorry, good to be merged


Exception thrown after closing window with flyout that contains a color picker

Describe the bug
Window defined with the following C++ code:
window = winrt::Microsoft::UI::Xaml::Window::Window();
window.Activate();

winrt::Microsoft::UI::Xaml::Controls::Button button;
button.HorizontalAlignment(winrt::Microsoft::UI::Xaml::HorizontalAlignment::Center);
button.VerticalAlignment(winrt::Microsoft::UI::Xaml::VerticalAlignment::Center);
button.Content(winrt::box_value(L"Button"));
window.Content(button);

winrt::Microsoft::UI::Xaml::Controls::ColorPicker colorPicker;
winrt::Microsoft::UI::Xaml::Controls::Flyout flyout;
flyout.Content(colorPicker);
button.Flyout(flyout);

If I click on the button to open the flyout everything works fine but when I close the window the following exception is thrown:
Exception thrown at 0x00007FFE6D5947F8 (threadpoolwinrt.dll) in FlyoutColorPickerIssue.exe: 0xC0000005 : Access violation reading location 0x0000000000000000.

If I don't open the flyout the exception isn't thrown. Same thing happens if I use XAML to define the same window in MainWindow.xaml. I have tried the same with some other controls, in particular with TextBlock, DatePicker and TimePicker, and the window closes fine without this exception. Also reverted back to Microsoft.WindowsAppSDK 1.0.3 and no exception gets thrown so I'm assuming the issue is with Microsoft.WindowsAppSDK 1.1.0.
Steps to reproduce the bug

Build and run the app
Click on the button to open flyout that contains a color picker
Close the window (using the caption buttons)

Expected behavior
Window to close without any exceptions.
Screenshots

NuGet package version
No response
Windows app type

[ ] UWP
[X] Win32

Device form factor
No response
Windows version
Windows 10 (21H2): Build 19044
Additional context
Using Microsoft.WindowsAppSDK 1.1.0

Just to give an update. Recently updated to Windows 11 (21H2) Build: 22000.832, and after testing this again with both Windows App SDK 1.1.2 and 1.1.3, it seems that this issue isn't present anymore. Last time I checked on Windows 10 was with Windows App SDK 1.1.2 and the issue was still there.

After the drag & drop issues seem to be fixed in App SDK v1.2.0-preview1 I now see colorpicker triggered crashes as described in this ticket. This is a regression of App SDK v1.1.x versions as it was fine for all App SDK v1.0.x versions. Currently, this is a blocker for us for internal testing of the application.
@codendone, @ojhad As the issue looks suspiciously similar to https://github.com/microsoft/microsoft-ui-xaml/issues/7260 I've tried the workaround as proposed by https://github.com/dotnet/maui/issues/7317#issuecomment-1231940453. As my code is WinRT C++ based, I used the following code fragment.
´´´
#include "WorkAroundMicrosoftBug.hpp"
#include "winstring.h"
#include "roapi.h"
#include "guiddef.h"
#include
// https://github.com/dotnet/maui/issues/7317
// https://github.com/microsoft/microsoft-ui-xaml/issues/7260
void WorkaroundMicrosoftBug()
{
HRESULT result;
result = RoInitialize(RO_INIT_MULTITHREADED);
std::wstring name = L"Windows.System.Threading.ThreadPoolTimer";
HSTRING str;
void* out;
result = WindowsCreateString(name.c_str(), name.size(), &str);
GUID guid = { 0x1a8a9d02, 0xe482, 0x461b, { 0xB8, 0xC7, 0x8E, 0xFA, 0xD1, 0xCC, 0xE5, 0x90 } };
result = RoGetActivationFactory(str, guid, &out);
result = RoGetActivationFactory(str, guid, &out);
result = RoGetActivationFactory(str, guid, &out);
}
´´´
Unfortunately, it doesn't solve the crashes that I observe. Is it correct that the tickets are related? Or do I miss something with the workaround?
I hope that we get soon a fix for this issue so that at least we do not suffer anymore from regression of v1.1.x. It would allow us to step finally from App SDK v.1.0.x to something newer.
Any fix or workaround would be highly appreciated.

@codendone The issue is still visible with App SDK 1.2.221116.1.

The official WinUI 3 Gallery (Version: <IP_ADDRESS>) hangs when the Colopicker Tab is opened and the app is closed. Using other tabs doesn't show this behavior. The WinUI 3 Gallery Window is closed but the application is still visible in the task manager consuming significant CPU power after exit. It must be forcefully terminated.

This issue is still a regression of all 1.x and 2.x App SDK releases for the Windows 10 platform. I've also tested the latest v1.2.2 release with the same results. On Windows 11 platforms the crash cannot be observed (using the same test code). It currently blocks us from finally upgrading from the outdated 1.0.4 release to something up-to-date without the need to design our own color picker.
It can be very easily reproduced on the official WinUI 3 Gallery. Just open on a Windows 10 platform the tab with the color picker and the app will crash with the above-reported exception.
@bpulliam, @Scottj1s, I appreciate it a lot if this regression could be addressed in one of the next service-releases 1.2.x. With source code access the fix shouldn't be that difficult as easy reproducible and very localized. Many thanks in advance.

@jschwizer99 Thanks for your patience.  We have a fix for this issue and will endeavor to include it in the next 1.2 servicing release.

@Scottj1s Many thanks for this positive news! I'm looking forward to testing it.

And thanks @dkreho1 for reporting this issue.  The fix will be available soon in the next servicing release, 1.2.3.

Fix is now available: https://www.nuget.org/packages/Microsoft.WindowsAppSDK/1.2.230118.102


Add ckron

ckron is a tool to run a set of containerized tasks on a schedule. It uses YAML files for configuration using docker-compose like syntax, so easier to learn

Thanks 🎉


activation button not reset on activate

seems to only happen on my laptop at work. Needs investigation

Looks like embedding release in a progressbar fixed it


Unable to retrieve child resources - microsoft azure storage explorer

local and attached
storage accounts
emulator default ports
blob containers
tables
can't access/create blob or tables
Unable to retrieve child resources.
Details:
Server encountered an internal error. Please try again after some time.
RequestId:76706f06-820b-49e6-a904-21aec7868a17
Time:2021-02-04T11:40:36.9134606Z

@ervcabrita the error says to try again later. Did you try again later?
It looks like you're probably working with an emulator? Which emulator is it, Azurite or the old .NET emulator? Can you look at the terminal where you started your emulator from for any error messages?

Hi.
It is Microsoft azure storage emulator v5.10.
I did restart everything.
After a few days still same issue.
In between working and not working I had a domain migration, but everything else is working by now.
Emulator log looks ok
:
C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>AzureStorageEmulator.exe start
Windows Azure Storage Emulator <IP_ADDRESS> command line tool
The storage emulator was successfully started.
C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator>cmd /K AzureStorageEmulator.exe help
Windows Azure Storage Emulator <IP_ADDRESS> command line tool
Usage:
AzureStorageEmulator.exe init            : Initialize the emulator database and configuration.
AzureStorageEmulator.exe start           : Start the emulator.
AzureStorageEmulator.exe stop            : Stop the emulator.
AzureStorageEmulator.exe status          : Get current emulator status.
AzureStorageEmulator.exe clear           : Delete all data in the emulator.
AzureStorageEmulator.exe help [command]  : Show general or command-specific help.
See the following URL for more command line help: http://go.microsoft.com/fwlink/?LinkId=392235

Could only be fixed after uninstall all azure apps/microsoft sdk, clearing all cache and temp files, and reinstalling.
Path variables didn't mention any of the affected paths.