Loot tracker should track Pest Control

Whether it's just the money, money + points, or money + rewards.

You don't receive "loot" from pest control, you receive a reward for completing a minigame

Same could be said for Raids if you want to be pedantic.

anything else other than money gained for completing the PC game is out of question. and tbh I see very little point for displaying the money as reward, idk

As it is always fixed amount


[stable/ambassador] Apro/0.6.0

What this PR does / why we need it:
Bumps the version of Ambassador Pro.
Special notes for your reviewer:
Minor version bumped since the ports for pro auth and pro ratelimit must now be the same.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test
/lgtm
not really sure about the ports thing, if they are supposed to be the same it seems weird to allow configuring both but leaving it in place probably gives better migration paths


retweet: correct regexp match groups for uname & tweet.

ran into this bug today. /cc @jhubert

Good catch!

Thanks for the review, and thanks for releasing v0.3.2! :smile:


btn-group prevents tabbable from working

This doesn't seem to be working:

Section 1

Section 2

        B1
        B2

       This is section 2, but you can't switch to it...

It looks like..
.btn-group:after {
  content: "";
}

causes the issue.

could you create a jsfiddle - thanks!

http://jsfiddle.net/sMD8q/

Should be resolved in 2.0.1-wip—we added overflow: hidden to the .tab-content.


通义网页上的按钮没有了

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
无法点击停止生成，有时候生成了大堆文字，但是看第1行我就知道搞错了，无法点击停止，客户端感觉明显卡顿
影响点击新对话
反馈功能也没有了，点不了赞，
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Duplicate of #350


Test update to Jetty 12.0.9

Thanks  @wendigo. I used your approach to build airlift 246 + Trino 446 and I don't see the exceptions I saw before with jetty 12.0.8 (using HTTP/2). Once Jetty folks release 12.0.9, we can make it official.

@sajjoseph great to hear!


Enable building charm with link time optimization

Original issue: https://charm.cs.illinois.edu/redmine/issues/1817

Link time optimization has the potential to improve performance through better interprocedural analysis and inlining. Unfortunately, building Charm++ with link time optimization isn't as easy as just adding "-flto" to the end of your build line.

Original date: 2018-04-25 05:47:53

For ICC they call this "-ipo" and it again requires use of a different linker named "xild": https://software.intel.com/en-us/node/522667

Some progress in PR #3721


OR parameter in fhirEngineSearch does not work as expected

Describe the bug
OR parameter in fhirEngineSearch does not work as expected
// pregnancies is a list of Condition resource
val patients = pregnancies.map { fhirEngine.load(Patient::class.java, it.subject.reference.split("/")[1]) } // works fine
val ids: List<TokenParamFilterCriterion.() -> Unit> = pregnancies.map {
  { value = of(it.subject.extractId()) }
}

val patients = fhirEngine.search<Patient> { // does not work
  filter(Patient.RES_ID, *ids.toTypedArray())
}

In code above we want to reduce number of queries made to DB and use search to query all patients of certain ids.
Similary, following does not work as expected and returns 0 results
fhirEngine
      .search<Task> {
        filter(
          Task.STATUS,
          { value = of(Task.TaskStatus.REQUESTED.toCode()) },
          { value = of(Task.TaskStatus.READY.toCode()) },
          { value = of(Task.TaskStatus.ACCEPTED.toCode()) },
          { value = of(Task.TaskStatus.INPROGRESS.toCode()) },
          { value = of(Task.TaskStatus.RECEIVED.toCode()) },
        )
      }

Is there something wrong with querying?
Component
Core library,
Expected behavior
Should append IN or OR clause to query generated when using vararg for filterCriterions

It appears that engine is not traversing the full Class hierarchy of the model classes to figure out all the SearchParams that need to be indexed into the database. This is causing search by Patient.RES_ID to fail.

The Task search will work if both code and system are provided in the filters e.g. { value = of(  Coding().apply {
system = Task.TaskStatus.REQUESTED.system
system = Task.TaskStatus.REQUESTED.toCode()
}) }.
Nevertheless, the engine should allow to search by just the code as well.

looking into it.


change default .net core web app template wwwroot folder name to static

Regarding: https://github.com/aspnet/Home/issues/1636  #1636
change default .net core web app template deploy wwwroot code to wwwroot
Is this backward compatibility needed as asp.net 5 is dead and asp.net core is what being developed.?
Or change the name wwwroot to staticfiles as the default folder name
To address your issues more quickly, please open the issue in the most appropriate repository. These are some of the most common repos:

Hi @vairamsvsjdo can you provide more info about your question?
Here are some points that might help clarify things:

ASP.NET 5 was a pre-release product that that was renamed to ASP.NET Core 1.0, and then shipped (after several major changes)
The wwwroot folder is a folder used in ASP.NET Core applications for static assets that are servable by the web server. This typically includes files such as JS, CSS, and image files

@Eilon The issue is with the wwwroot folder. web_deploy deploys wwwroot folder to a wwwroot folder within wwwroot folder  when published to app services.
One of the following should happen ideally:

It must be called as static files or something else other than wwwroot.
or
web deploy must move those static files to wwwroot folder.

What is the actual issue? It's ok to have a wwwroot\wwwroot folder as long as everything is configured correctly. Are you having a specific problem? Can you share info on that?

Issue is in the default name used for "static files" folder.
It is ok! It is quiet weird to have a wwwroot folder inside a wwwroot folder. There should be only one wwwroot folder. Can it be named "staticfiles" or "assets" instead of wwwroot like webpack or other bundling tools conventions use?
https://stackoverflow.com/questions/27639005/how-to-copy-static-files-to-build-directory-with-webpack

@vairamsvsjdo I agree it's a bit weird, but it just happens to be that two different features each use that name. You can certainly rename the wwwroot folder in your app to anything you want, but once you move away from the default values, you have to start configuring more things.
I would recommend sticking with the current naming - I think you'll find it easier in the long run.

@Eilon
What are the two different features that use it?
Thanks

Web Deploy uses it for the entire web app, and also ASP.NET Core uses it for its static files.


Avoid infinite loops in examples.

Another fix would be to change while counter < 40 in Line 541 to while counter > 40.
If we ever get to the decrement line, then counter is less than 40. Decrementing it makes it even smaller.

Hi Benji,
Welcome back. Happy to see a contribution from you after a long time.
Regards,
Yegappan
On Fri, Dec 31, 2021 at 6:52 PM Benji Fisher @.***>
wrote:

Another fix would be to change while counter < 40 in Line 541 to while
counter > 40.
If we ever get to the decrement line, then counter is less than 40.
Decrementing it makes it even smaller.
You can view, comment on, or merge this pull request online at:
https://github.com/vim/vim/pull/9450

Hi Benji,
Welcome back. Happy to see a contribution from you after a long time.
Regards,
Yegappan
On Fri, Dec 31, 2021 at 6:52 PM Benji Fisher @.***>
wrote:

Another fix would be to change while counter < 40 in Line 541 to while
counter > 40.
If we ever get to the decrement line, then counter is less than 40.
Decrementing it makes it even smaller.
You can view, comment on, or merge this pull request online at:
https://github.com/vim/vim/pull/9450

Thanks for the fix.  Let me also make the conditions more sensible.

Thanks for the fix.  Let me also make the conditions more sensible.


LP#1681973: neutron-ns-metadata proxy unusable at larger scale

Do NOT include any confidential information, this issue will be created on a public repo
This section is completed by the issue reporter
On which version(s) do you encounter this issue?
Please provide the output to 'git describe --all' for  all deployments where you have confirmed it occurs.
Mitaka
What type of issue is this? Please tick the appropriate box.

[x] bug - existing functionality that does not work for you as documented
[ ] feature - new functionality that you would like to see added

What is the expected behavior?
See https://bugs.launchpad.net/neutron/+bug/1681973
What is actually happening?
A bottleneck based on a configuration change noted per https://bugs.launchpad.net/neutron/+bug/1681973 is causing performance issues inside the neutron-ns-metadata-proxy
At this time it is not know if that can be even addressed prior to Ocata
What were you attempting to do when you encountered this error (give as much detail as possible)?
See https://bugs.launchpad.net/neutron/+bug/1681973
How can we reproduce this issue?
Stress test the EC2 metadata with more than 100 connections against a qrouter provided namespace metadata proxy
How can we verify your issue is addressed?
See https://bugs.launchpad.net/neutron/+bug/1681973
If you are using or know of a workaround please describe the necessary steps?
None
What is your evaluation on the importance of this issue, and why?
Prio 2

This section is completed during the issue resolution process. If you are reporting an issue, please do not modify the section below.
Which branches are impacted by this issue?
Remove branches that are not impacted.
For each pull request, update the branch line to reference it.

[ ] master
[ ] newton-14.0
[ ] mitaka-13.1

Upgrade impact. Consider the impact on moving between major, minor and patch releases.

[ ] This change does not impact upgrades
[ ] This change addresses a potential upgrade impact
[ ] The upgrade impact is being tracked by another issue.

The issue tracking the upgrade impact is:
Testing impact

[ ] An issue/pull-request has been create or exists to track the testing gap, and is referenced below
[ ] This change includes additional testing
[ ] This change is tested by the existing setup

Additional testing links:
Release note

[ ] This change includes a release note.
[ ] This change does not require a release note.

Doc Impact
Does your change require documentation?

[ ] Yes, and I submitted an issue to Docs issues
[ ] Yes, and I contributed a documentation patch to docs-rpc
[ ] No documentation required for this change

Additional documentation links (please add links if you have ticked yes):

Thanks for the info, @BjoernT. We'll keep an eye on that upstream bug. In the meantime, I'm marking this as prio-undecided until we find out some more information on the upstream bug.
In the upstream bug, you say: "Once I manually started the ns-metadata-proxy, increasing the wsgi threads, all application issues disappeared". Is that something we could do as an override?

bump @BjoernT
This may be something we could address within OSA should increasing the wsgi threads resolve the issue. thoughts?

@cloudnull  No we can not, the ns-metadata-proxy is not reading any config file. I worked on a neutron patch but I doubt they will accept it for mitaka, perhaps we need to include this patch in our mitaka environment, otherwise I can not close the customer issue


nimrpc fresh repo

Great! You will also need to update your repo (rename nimrpc.nimble to nimrpc_milis.nimble etc.). I'll merge this now anyway.


Autocomplete: Command to enable tab completion

Add new command vcpkg autocomplete. This is needed to allow tab completion in PowerShell (which is being worked on). Currently, install and remove are supported.

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


Refactor Azure Spring projects structure

This PR is refactoring the Azure Spring project structures.

Remove azure-spring-boot (the autoconfiguration module), move the code to azure-spring-cloud-autoconfigure
Remove azure-spring-boot-core, move the code to azure-spring-cloud-context
Make a separate module azure-spring-cloud-resourcemanager

I think this PR will not merge before this month's release. How about converting to draft?

I think this PR will not merge before this month's release. How about converting to draft?

This not targeting the main branch.

Close in favor of #23004, there's a lot of copying files in this PR, which will lose git history. I'm using moving files in the other PR.


Feauture/6 director controller

closes #6
Pls be extra thorough with mappingConfigurations on your review

Try PR on correct branch ! ;)


STREAMLINE-561: MySQL drop table script easy to break due to foreign key and order of drop table

@HeartSaVioR pls check.
Tested by running bootstrap storage script.

+1 assuming it's running well with both mysql and postgresql .


add taglist plugin

add taglist plugin to source_non_forked directory,  I don't know why you still not add this useful plugin, maybe in your repository has include a similar plugin can finish same task. if there is that plugin, please tell me, thank you.

Please include this in your own fork 👍
I don't use taglist plugin anymore and it's quite "dirty" on some systems.

OK, thanks for your reply.


Allow "default translation" ([Default]) label to be translated

This is a follow up on #231, the point is pretty much the same too... We should allow for the "[Default]" label to be translated too.
This PR also include the support for the default_label var (in the FormView) to override the translation key (it's very easy to do via a Form Extension on TranslationsType, for example, I can provide an example if you wish).

True, thanks


Add --no-aliases and --no-names switched to node list command

This fixes https://github.com/crowbar/crowbar-client/issues/31

:+1:

+1


Add support for auto-assignment of transactional IDs based on consumer rebalances

Very rough-draft, but wanted to get some eyes on the general approach.
@vlovgr can you take a look, when you get a minute?

@danxmoran what do you think about linking the producer to the consumer by simply passing the KafkaConsumer instance to the function creating the producer? The producer could then register the listeners it needs without having to change ConsumerSettings or create the consumer itself.

@vlovgr that sounds OK to me! Would the producer-builder still return a new KafkaConsumer copy in that case, where the new instance has the listeners registered? Or would it update the state of the existing instance?

@danxmoran I would suggest to register listeners on the existing instance using Request.Assignment, similar to how we do it in partitionedStream. We might need to add a new assignment overload to KafkaConsumer for exposing the ability to add rebalance listeners.
https://github.com/ovotech/fs2-kafka/blob/5256957c03fe91581a57469e31c46aa743dda545/modules/core/src/main/scala/fs2/kafka/KafkaConsumer.scala#L420-L433

@vlovgr I was thinking about your suggestion for an assignment overload with listeners, and wondered if this would be an even-better alternative for a new method:
def assignmentStream: Stream[F, SortedSet[TopicPartition]]

What do you think? The stream would emit on every rebalance, but the details of how the rebalance maps to a SortedSet could be fully encapsulated by the KafkaConsumer. It seems like a closer match to the other APIs on the consumer, and it'll save us from needing to encode too many details about the KafkaConsumer in the TransactionalKafkaProducer setup.

@danxmoran I like the idea! The only downside I can think of is that users of assignmentStream will have to work out what partitions have been assigned or revoked (checking differences between previous and current sets). If this should prove challenging, we could introduce an Assignment wrapper which includes both the current partitions and what was revoked/added.

I took a stab at a naive implementation of assignmentStream, with a basic test. It's not behaving as expected, but I can't tell if it's because of a problem with Kafka or (probably) a problem with how I'm trying to set up concurrent operations. Can you take a look and let me know if anything obvious jumps out, @vlovgr?

@danxmoran It's probably a good idea to move assignmentStream to a separate pull request. The issue you're facing happens because assignment is used in the callback. The callbacks are run synchronously, waiting for the effects to finish before returning (which is the ConsumerRebalanceListener contract).
https://github.com/ovotech/fs2-kafka/blob/5256957c03fe91581a57469e31c46aa743dda545/modules/core/src/main/scala/fs2/kafka/internal/KafkaConsumerActor.scala#L79-L86
While the callback effects are being run, no new requests are handled by the actor, and as such, the assignment request won't be completed. A solution to this is to not call assignment, but instead store the currently assigned partitions in a Ref[F, SortedSet[TopicPartition]], and update the Ref + emit current assignment when rebalance happens.

Ack, ok. Was worried that might be the case. I'll close this for now and reopen a PR for just the assignmentStream, then revisit the auto-rebalancing producers after that.
Thanks for all the help @vlovgr! I'll get there eventually 😄


When I inject I get this error

VAC STATUS - not bypassed
Back to topic debug it and give me on what key it happens, if old config, then delete it and let it create new.

inactivity


Weird look

Left: Alacritty
Right: st
I think it looked better on the screenshots provided in the repo. I first thought it might be because of antialias and autohint but it's the same with them enabled and disabled.

Sorry for the very late reply.
Yes, this look is due to X not providing any anti-aliasing methods to draw lines. Actually it doesn't even have any methods to draw lines, I had to generate the squiggly pattern by drawing pixel by pixel on a separate buffer. I would recommend you using the capped line style instead (which should be the default), it looks much better too.


x/build/cmd/release: 8 targets are not passing tests successfully on master branch

The release command is used by releasebot to build targets. In the first stage (-mode=prepare), it runs tests. In second stage (-mode=release), it skips tests.
release supports 12 normal targets (not counting new optional longtest-only targets; described in #29252 but can be ignored in this issue), see here.
These targets are passing tests (they run successfully without -skip_tests flag given to release) on a recent master commit (e.g., 09e791feb1dfbfc05578a17cd9c035ef82af4033):

src
linux-armv6l
linux-ppc64le
linux-s390x

These are not passing:

darwin-amd64 - blocked on #39385 and #39391
freebsd-386 - blocked on #39391 only
freebsd-amd64 - blocked on #39385 and #39391
linux-386 - blocked on #39391 only
linux-amd64 - blocked on #39385 and #39391
linux-arm64 - blocked on #39385 and #39391
windows-386 - blocked on #39391 only
windows-amd64 - blocked on #39385 and #39391

Each one can be reproduced if your account has permissions needed to run releasebot (they are documented at https://github.com/golang/build/tree/master/cmd/releasebot#permissions) with:
$ release -target=<target_name> -version=go1.15beta1 -watch -rev=09e791feb1dfbfc05578a17cd9c035ef82af4033

(The release command creates a tarball and places it in a temporary staging directory; it doesn't publish anything, so it is safe to run as shown above.)
See #39385 as an example of a specific test that is failing.
This is the high-level tracking issue for the entire problem. Next, I'll be updating it and splitting into smaller, distinct failures that can be investigated independently.
This issue requires investigation. The problem is either in how the release command sets up the environment and executes commands on the target builder, or in the builder definition, or in the test, or some combination. Depending on what we learn, we may end up deciding this is okay to resolve after beta1 (but before the final release) and skip these test failures in order to make the Go 1.15 beta 1 available for testing and finding unknown issues sooner.
/cc @andybons @toothrot @cagedmantis @golang/osp-team

Both known issues #39385 and #39391 have been resolved by now, so I'm testing this again.

By now, these targets have passed (to be more precise, got as far as failing the API check test, without other failures) at least once:

src
linux-armv6l
linux-ppc64le
linux-s390x
darwin-amd64
freebsd-386
freebsd-amd64
linux-386
linux-amd64
linux-arm64

However, windows-386 and windows-amd64 have failed:
windows-386
ok  	cmd/go	111.031s

--- FAIL: TestDWARF (1.28s)
    dwarf_test.go:39: cmd/link is stale - run go install cmd/link
FAIL
FAIL	cmd/link	25.084s

windows-amd64
go test proxy running at GOPROXY=http://<IP_ADDRESS>:50986/mod
go proxy: no archive rsc.io v1.5.2: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.1.0: file does not exist
go proxy: no archive rsc.io v1.0.0: file does not exist
go proxy: no archive rsc.io v1.5.1: file does not exist
go proxy: no archive example.com/newcycle v1.0.0: file does not exist
go proxy: no archive test.go v1.0.0: file does not exist
go proxy: no archive rsc.io v1.5.2: file does not exist
--- FAIL: TestScript (0.01s)
    --- FAIL: TestScript/test_race_install_cgo (1.21s)
        script_test.go:210:
            # Tests Issue #10500 (1.209s)
            > [!race] skip
            > [!darwin] ! stale cmd/cgo  # The darwin builders are spuriously stale; see #33598.
            FAIL: testdata\script\test_race_install_cgo.txt:5: cmd/cgo is unexpectedly stale

FAIL
FAIL	cmd/go	111.443s

--- FAIL: TestDWARF (1.62s)
    dwarf_test.go:39: cmd/link is stale - run go install cmd/link
FAIL
FAIL	cmd/link	19.749s

This may be related to the change in CL 236819. /cc @bcmills
I'll try again a few more times to confirm if it's a flaky or reproducible failure. I'll also try the windows targets with a commit before CL 236819 to see what effect it has. Then update this issue.

That one is strange because those two tests are both passing on the regular builders. I'll pop on a gomote and see if they're easy to reproduce with GOROOT_FINAL.

I've tried both windows-amd64 and windows-386 again, and both failed in the same way, so this doesn't seem to be a flake. Filed #39478 as a dedicated tracking issue for it. Thank you again for looking into this @bcmills.

Issue #39478 has been resolved via CL 237359; a re-test of all targets with it is now ongoing.

Testing has shown no new test failures. All 12 targets are passing tests when targeting commit https://github.com/golang/go/commit/2a4e71c752875f84dc0061f75fdcbfc96ae8d5f2 (CL 237359). That means this issue is resolved. Huge thanks to @bcmills for helping make this happen!


From stream to athena integration test

I added a complete integration test from sending events to the stream, to querying S3 with athena and saving the results. Note this should looked at after PR #3751 is merged.

Cherry picked in another branch for clarity


Preserves UTF-8 in codes.py

[ ] Updated Unreleased in CHANGELOG.md to reflect the changes in code or data.

LGTM. Closes #167.


feat(examples/vmseries_standalone): introduce IPv6

Description
The code introduces support for AWS auto-generated IPv6 CIDR in VPC and applies IPv4 and IPv6 Dual Stack configuration to the standalone VM-Series example.
Motivation and Context
The change is the initial point of enabling IPv6 support in AWS modules.
How Has This Been Tested?
Code was deployed in the lab environment and connectivity verified over IPv4 and IPv6.
Types of changes

New feature (non-breaking change which adds functionality)

Checklist

[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes if appropriate.
[x] All new and existing tests passed.

/help

/apply paths="examples/vmseries_standalone" tf_version="1.6.0"

/apply paths="examples/vmseries_standalone" tf_version="1.4.0, 1.5.0, 1.6.0"

/idempotence paths="examples/vmseries_standalone" tf_version="1.4.0, 1.5.0, 1.6.0"

/idempotence paths="examples/vmseries_standalone" tf_version="1.4.0, 1.5.0, 1.6.0"

/idempotence paths="examples/vmseries_standalone" tf_version="1.4.0, 1.5.0, 1.6.0"


Traefik header transformation

Feature:
Header transformation rules using a predefined set of operators
Syntax:
Something like this:
traefik.http.middlewares.<middleware>.headers.request_transform = op1, op2, op3
traefik.http.middlewares.<middleware>.headers.response_transform = op1, op2, op3
Or possibly:
traefik.http.middlewares.<middleware>.headers.transform.operations = op1, op2, op3
traefik.http.middlewares.<middleware>.headers.transform.type = 'request' or 'response'
Goal:
Add a toolset that lets traefik transform headers. Currently in traefik it's possible to do basic operations of headers like adding,removing headers from a request or response but the support for manipulation of headers is quite simplistic. It doesn't really let the users to modify/transform header by changing the content or the name of the headers.
Operators:
Rename(header, new_header)
Rename a header by matching an exact header to a new_header.
Example:
Rename(`MY_HEADER`, `NEW_HEADER`)

Would change:
MY_HEADER: super
OTHER_HEADER: 123

To:
NEW_HEADER: super
OTHER_HEADER: 123

HeaderRewriteRule(regex, replace)
Rewrite header name using a regex with a match/capture.
Example:
HeaderRewriteRule(`MY_(.*)`, `NEW_$1`)

Would change the following requests from:
MY_HEADER: super
MY_OTHER_HEADER: 123

To:
NEW_HEADER: super
NEW_OTHER_HEADER: 123

ValueRewriteRule(header, regex, replace)
Same as the header rewrite but for their content, header is a parameter to match an header or a set of headers to apply the rewrite rule.
Set(header, value)
Set a value to a header name
Remove(header)
Remove an header
Join(header, sep, value/header)
Possibility to join multiple headers inside one.
Example:
Set(`PROXY_PATH`, `<IP_ADDRESS>`), Join(`PROXY_PATH`, `,`, `<IP_ADDRESS>`)

Would result with this header:
PROXY_PATH: <IP_ADDRESS>,127.0.01

As you can see, the order of the operators change the context of evaluation so op1 can change the context in a way that op2 will be able to transform headers that weren't present in the original response or request.   Or at least they could become simple shortcuts.
As a side note, I guess the chain of operators could be hard to read/edit manually if you wanted to combine a lot of operations inside a single middleware. But I guess traefik being pretty useful when combined with containers, most users probably already have some tool that generate proper configurations so while reading the config might be necessary sometimes, writing a long operators chain should probably be implemented into some kind of external tool if user don't want to write by hand everything. Thought the use of \n could help by making the rules more readable.
Inside a config file, the second syntax I proposed could look like this:
[traefik.http.middlewares."some_middleware".transform]
  type = "request"
  operations = """
    Set(...),
    Join(....),
    Rename(...)
  """

Or
[traefik.http.middlewares."some_middleware".transform]
  type = "request"
  operations = [
    "Set(...)",
    "Join(....)",
    "Rename(...)"
  ]

This is a proposal and if it's a good enough idea for people, this could leave the door open for more possible operators and may be better operators than the one I came up with. Technically speaking, this kind of feature could be used internally inside traefik to handle headers instead of having many ways to do the same things in different place of the code base.

gorilla/mux uses something similar, and stores variables in the request context with the key as the name of the variable used in the goregexp.
This allows re-use of that variable in other situations or transformations.

This looks like what I would need for my use case (renaming Remote-User header received from authelia to REMOTE_USER as expected by my webapp)
Is anyone already working on this?

I need this to rename the X-Forwarded-Tls-Client-Cert to X-SSL-Cert in order to run a syncthing discovery server (https://docs.syncthing.net/users/stdiscosrv.html#requirements)

curious to see if there is any traction for this proposal?

I'm developing a service using Sanic (python) and it requires a shared secret between the forwarder (Traefik, nginx, ecc...) and your application. This would help!

I'd like to see this added too, especially for use with Authelia.

Throwing my hat in the ring: I'm using Authelia with Traefik proxied infront with Cloudflare and need to rewrite the X-Forwarded-For IP to be the Cloudflare Real IP address. I'm hoping we will be able to do header rewriting soon!

Have to stay on nginx to support custom multi-tenancy based on host header parsing by regex. Hopefully it is completed soon and I can migrate on traefik.

Hi, currently working on that here : https://github.com/tomMoulard/htransformation

Running Traefik behind an ALB, would love to rewrite X-Real-IP to pass real IP Address to Gunicorn and not the ALB's.

authelia give Remote-User,gitea expect X-WEBAUTH-USER,need trans.

As there is a working plugin https://github.com/tomMoulard/htransformation that answers this need, this issue is closed accordingly.

Hello,
I am closing this issue in favor of https://github.com/traefik/traefik/issues/9471 which contains a more detailed example of the plan we want to follow.
Please do not hesitate to add comments on https://github.com/traefik/traefik/issues/9471 if you think that we miss some things, and to add your use case.


KinematicPositionBased velocity is not available after a position change

I am not sure if it is relevant in any way but the velocity of a KinematicPositionBased rigid body is told to be calculated automatically by the physics engine but it is not available to the user. I am not sure if the velocity should even be propagated at the heron/bevy level.

If the transform is updated, then a velocity will be automatically calculated, producing realistic interaction with other bodies.

Hi,
Yes, the velocity should be calculated by the engine. You should be able to read that velocity if you want to.
Are you saying it doesn't work the velocity is not calculated by the engine?

I am not sure if the velocity should even be propagated at the heron/bevy level.

The Velocity component should be updated to reflect the velocity of the component if that's what you mean.

@Kerollmops would you mind sharing how to reproduce the behavior you observed?


Update ma_tx_out or tx_in table columns for tx_out_id

External
Existing Database Tables
Summary
The use of 'tx_out_id' in the ma_tx_out and the tx_in tables aren't consistent. For tx_in the tx_out_id refers to the actual transaction table id. Whereas for ma_tx_out tx_out_id refers to the tx_out table id.
Not really a high priority, but an inconsistency that could cause some really bad but "working" results if people aren't paying attention.
Maybe we could change the tx_in tables to say tx_id_in and tx_id_out?
Steps to reproduce
View tables
System info:
OS: Debian Buster
DB Sync Version 9.0
Node version 1.26.1

It looks like there hasn't been any activity on this issue for a some time. We're closing it for now. If you're still experiencing this problem or have any updates, please reopen or create a new issue. Your feedback is valuable, thank you!


south app missing

The code includes a south migration, but the app is not listed.
Need to add 'south' to INSTALLED_APPS in settings.py
p.s. nice work! works first time (almost), and the code is concise and clear. Thanks

Thanks for the notice. I included south while I "translated" this app from php, but I did not mean to include it. I removed the migrations instead of re-adding south.
Thank you for the good words as well, and sorry for my very late response.


Ensemble model fixes for batching

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
What are the significant changes in functionality due to this change request?

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Job Test qsubs sawtooth on ad894b9 : invalidated by @wangcj05
one failed run for tests/cluster_tests/InternalParallel/test_hybrid_model_code

Job Test qsubs sawtooth on ad894b9 : invalidated by @joshua-cogliati-inl
fixed problem on sawtooth

Job Mingw Test on ad894b9 : invalidated by @wangcj05
retesting

PR looks good and checklist is satisfied.


.keep_instance_open=True is not available

🔍 Before submitting the issue

[X] I have searched among the existing issues
[X] I am using a Python virtual environment

🐞 Description of the bug
the Motor-CAD instance is closed after calculation automatically, even if i add "mcApp = pymotorcad.MotorCAD(keep_instance_open=True)"
test_script_default_keep_open.zip
I attached sample mot and py.
I executed py by visual studio Code.
📝 Steps to reproduce
I tried and Motor-CAD script just do static thermal analysis to check the result after automatic calculation by python script.
I set pymotorcad as below.
mcApp = pymotorcad.MotorCAD(keep_instance_open=True)
but the Motor-CAD instance is closed after calculation.
💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
Motor-CAD 24R1
🐍 Which Python version are you using?
3.10
📦 Installed packages
ansys-motorcad-core==0.4.3
certifi==2023.7.22
cffi==1.15.1
charset-normalizer==3.3.2
clr-loader==0.2.6
contourpy==1.1.0
cycler==0.11.0
EasyProcess==1.1
entrypoint2==1.1
fonttools==4.42.1
idna==3.4
importlib-metadata==6.8.0
kiwisolver==1.4.5
matplotlib==3.7.3
MouseInfo==0.1.3
mss==9.0.1
numpy==1.25.2
packaging==23.1
pandas==2.1.0
Pillow==10.0.0
plumbum==1.8.2
psutil==5.9.5
pyaedt==0.6.92
PyAutoGUI==0.9.54
pycparser==2.21
PyGetWindow==0.0.9
PyMsgBox==1.0.9
pyparsing==3.1.1
pyperclip==1.8.2
PyRect==0.2.0
pyscreenshot==3.1
PyScreeze==0.1.29
python-dateutil==2.8.2
pythonnet==3.0.2
pytweening==1.0.7
pytz==2023.3.post1
pywin32==306
requests==2.31.0
rpyc==5.3.1
scipy==1.11.3
six==1.16.0
tzdata==2023.3
urllib3==2.0.7
zipp==3.17.0

Resolved this issue.
I add time.sleep after open Motor-CAD instance.
Added_import_subprocess_2.zip


Allow megaparsec 9.4

@tstat Am I reading this right, that adding the cache has helped you save nearly 16 minutes from CI? :)

@grahamc Yeah, I'm happy to have a nix cache that works well with github's free caches. Thanks for magic-nix-cache :)


policy: Improve L4Filter tests

Improve the descriptions for the L4Filter tests, and document them further. These were various changes I picked up while preparing #4416.
The only functional change is simplifying case 1, which was previously the same as case 2.
I manually verified that the policy behaviour is correct for the rules that overlap where one wildcards L7 and the other does not. The policy appears to work as one would expect, despite the strange representation when generating the L4Filter.

This change is

test-me-please

test-me-please


Unable to deploy schema with multiple documentSummaries

I am getting exception while deploying vespa with one schema containing 2 document summaries. I am currently using the vespa version 7.559.12
Error Message -
Request failed. HTTP status code: 400
Invalid application package: Error loading default.default: Conflicting summary transforms. summary field 'title' is already defined as summary field 'title'. A field with the same name can not have different transforms in different summary classes
command terminated with exit code 1
Schema Definition -
schema testVespaDoc {
document testVespaDoc {
    field title type array<string> {
        indexing: summary | attribute | index

    }
 }

document-summary summaryA {

    summary title type array<string> {
        source: title

    }
}

document-summary summaryB {

    summary title type array<string> {
        source: title
        dynamic
    }
}

}

This is a known limitation of document summaries, and the error message says what is not supported: "A field with the same name can not have different transforms in different summary classes". In summaryA the title field is defined to just return the field value, while in summaryB the title field is defined to be a dynamic summary, returning a snippet of the field value. These are different "transforms" of the field value. You need to rename the field in one of the document summaries, e.g. to title_dyn in summaryB.

If you need to provide an API to your clients where the title field is always named title, independent of which document summary is used in the query request, you can create a Java Searcher that iterates the Hit instances of the Result and creates a title field using the content of title_dyn if summaryB was used. See the following for details on Searcher development: https://docs.vespa.ai/en/searcher-development.html.

Note though that dynamic fields should be rendered differently.

Could you tell us how we can render dynamic fields separately?

Well you can write your own renderer class which does whatever you want: https://docs.vespa.ai/en/result-rendering.html
But what i mean here is just that your clients probably need to treat a dynamic field differently so it may not be a good idea to try to use the same summary field name.

Got it!
Thanks a lot!!

Hey @geirst,
I tried using a different field name but I am still facing some issues.
Changed the document summary to -
document-summary summaryB {
    summary title_teaser type array<string> {
        source: title
        dynamic
    }
}

Document Ingested -
{
"fields": {
"title": ["The content of an indexed string field is language-agnostic. One must therefore apply a symmetric tokenization on the query terms in order to match the content of that field.The query parser subscribes to configuration that tells it what fields are indexed strings, and every query term that targets such a field are run through appropriate tokenization. The language query parameter is what controls the language state of these calls.Because an index may simultaneously contain terms in any number of languages, one can have stemmed variants of one language match the stemmed variants of another. To work around this, store the language of a document in a separate attribute, and apply a filter against that attribute at query-time.If no language parameter is given, the language detector is called to process the query string. The detector is likely to be confused by field names and query syntax, but it is a best-effort approach. This matches the language resolution of the index pipeline.By default, there is no knowledge anywhere that captures what languages are used to generate the content of an index. The language parameter only affects the transformation of query terms that hit tokenized indexes."]
}
}
Search Query -
{
"yql": "select * from sources * where title contains "tokenized";",
"timeout": "120s",
"presentation.summary": "summaryB"
}
Query Response -
{
"root": {
"id": "toplevel",
"relevance": 1.0,
"fields": {
"totalCount": 1
},
"coverage": {
"coverage": 100,
"documents": 1,
"full": true,
"nodes": 6,
"results": 1,
"resultsFull": 1
},
"children": [
{
"id": "index:lexdoc/4/c4ca42386cd52a67065b91c5",
"relevance": 0.1620547555884915,
"source": "lexdoc",
"fields": {
"sddocname": "testVespaDoc"
}
}
]
}
}


Bot Messages Duplicating

When I do a command and the bot reply's, it sends its reply twice.

Ensure the bot is not running twice

Its not

its not running twice but still his duplicating messages


Reduction Op Softmax, Cross Entropy Loss, and LogSoftmax Test Failed While Parsing JITFunc in Triton

Issue
Reduction Op Softmax, Cross Entropy Loss, and LogSoftmax Test Failed While Parsing JITFunc in Triton
Env
FlagGems Commit: 3c62c9c
Python 3.8.18
Torch: 2.3.1
Triton: 2.3.1
Pytest: 8.2.2
Command
python -m pytest -svvv tests/test_reduction_ops.py::test_accuracy_softmax'[0-dtype0-shape0]'
python -m pytest -svvv tests/test_reduction_ops.py::test_accuracy_cross_entropy_loss'[1-dtype0-shape0-mean-None-None]'
python -m pytest -svvv tests/test_reduction_ops.py::test_accuracy_log_softmax'[dtype0-shape0]'

Softmax Result

BT

This is a bug with python's builtin module inspect, which is used in triton's frontend to parse the source of triton jit function. In short, inspect fails to parse function correctly when some form of lambda is in the function decorator.
TL;DR upgrading python interpreter to 3.10.2+ can solve this.
Also, as a workaround, maybe you can try modifying the lambda in the decorator. We will try it, too.
Related issues
https://github.com/python/cpython/issues/65416
https://github.com/triton-lang/triton/issues/1589
https://github.com/python/cpython/issues/102647

This is a bug with python's builtin module inspect, which is used in triton's frontend to parse the source of triton jit function. In short, inspect fails to parse function correctly when some form of lambda is in the function decorator.
TL;DR upgrading python interpreter to 3.10.2+ can solve this.
Also, as a workaround, maybe you can try modifying the lambda in the decorator. We will try it, too.
Related issues python/cpython#65416 triton-lang/triton#1589 python/cpython#102647

thanks for your reply. It looks like it can only handle lambda functions with simple logic.


Disabling rules look like they have some copy-paste mistakes

We mention "the enum" a lot in rules for how to disable them, even when there's no enum involved. I'm guessing this was copy-pasting that got missed.
See #491 for an example.

I think we have found most of these by now (have seen and made several PRs).


[TRANSLATION] Complete Arabic Translation

Please find attached the translation of en.arb into Arabic. I need to test the translation on the app, please support.
Arabic.zip

Thanks for translation you contributed!


MINOR: ACLs for secured cluster system tests

This PR adds missing broker ACLs required to create topics and SCRAM credentials when ACLs are enabled for a system test.   These ACLs were missed for system tests in the PR for KAFKA-10131 (https://github.com/apache/kafka/pull/9274/).  This PR also adds support for using PLAINTEXT as the inter broker security protocol when using SCRAM from the client in a system test with a secured cluster-- without this it would always be necessary to set both the inter-broker and client mechanisms to a SCRAM mechanism.

@rajinisivaram Thanks for the insightful feedback -- I think the latest commit does much at address the clarity/refactoring issue as well as make the extra ACLs optional such that all system tests will now run with the same ACLs as before unless explicitly requested otherwise.  Take a look and let me know what you think.

@rajinisivaram I ran some tests locally and found some issues, which I fixed with an additional commit.  I'll kick off a system test run -- I think we should run everything just to be safe since creating topics happens for every test.

Rebased onto trunk despite lack of conflicts due to Python 3 for system tests being merged.

@rondagostino Thanks for the PR updates and test runs. Merging to trunk.

Test runs as follows:
Status of trunk 2 days ago:
http://confluent-kafka-system-test-results.s3-us-west-2.amazonaws.com/2020-10-07--001.1602079305--apache--trunk--af27c2ddf/report.html

Tests = 684
Passed = 487
Failed = 27
Ignored = 170

Status of this PR before final ZooKeeperSecurityUpgradeTest fix:
http://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/2020-10-08--001.1602215668--rondagostino--rtd_scram_acl_system_test--8ca559f83/report.html

Tests = 606
Passed = 407
Failed = 29
Ignored = 170

Status of ZooKeeperSecurityUpgradeTest tests after fix:
http://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/2020-10-09--001.1602252468--rondagostino--rtd_scram_acl_system_test--a72d5986d/report.html

Tests = 4
Passed = 4
Failed = 0
Ignored = 0

Net effect of this PR:

Tests = 606
Passed = 411
Failed = 25
Ignored = 170

What about the 78 missing tests?  They disappeared on or after the python3 merge PR.
Here are missing tests succeeding just prior to the python3 merge: http://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/2020-10-09--001.1602255415--rondagostino--rtd_just_before_python3_merge--40a23cc0c/report.html
Here are the tests results for the same tests on current trunk: http://testing.confluent.io/confluent-kafka-system-test-results/?prefix=2020-10-09--001.1602251990--apache--trunk--7947c18b5/.  There are no tests listed there (no report.html) because they failed with [ERROR:2020-10-09 13:59:48,990]: Failed to import kafkatest.sanity_checks.test_performance_services, which may indicate a broken test that cannot be loaded: ImportError: No module named server
Will run against the actual python3 merge to see if that is the culprit (seems likely).


[FEATURE REQUEST] Skip install of MetalLB

Some people (read: I) would like to install and manage MetalLB separately from this playbook, that way I can do things like install MetalLB in BGP mode. While I can delete the MetalLB and install it from Helm afterward, it would be nice to skip the original install so it doesn't leave extra noise behind. Having an option in the all.yml, maybe something where if you leave the MetalLB IP range blank it skips the install entirely, would be nice.

Discussion supporting another use case for making it optional https://github.com/techno-tim/k3s-ansible/discussions/174

Also, if we are to do this we would also need to expand our tests to include this.

That should be pretty simple, use the existing test and skip the metalLB test section when testing this functionality, or optionally use the existing metalLB test and invert the pass condition.

I have create PR #191 which splits into individual task that are included on run time for add-on such kube-vip, metallb and so on.  We could expend on this and add flag to skip those steps if it get merge back to master.  Going with a modular approach could be useful given we all have unique homelab and needs.

Ooh, I quite like that approach. Leaving it up to the user to decide which parts are required.

I will amend my PR later next week to check if the service_version_tag is defined and have ansible include those task when variable exist.
So if you want to skip metallb install, you could just change the tag to be empty. I haven't done any of this work but that how I figured out it could be the easiest to implement. Obviously I will need to document this.

I will amend my PR later next week to check if the service_version_tag is defined and have ansible include those task when variable exist.
So if you want to skip metallb install, you could just change the tag to be empty. I haven't done any of this work but that how I figured out it could be the easiest to implement. Obviously I will need to document this.

Also, something I notice is that this playbook still uses a configmap to manage MetalLB, something that isn't supported as of Version 0.13.2. Should I make another issue to address that?

Also, something I notice is that this playbook still uses a configmap to manage MetalLB, something that isn't supported as of Version 0.13.2. Should I make another issue to address that?

Should I make another issue to address that?

I would suggest you could make a Pull Request to propose those changes you want to include. If you know what needs to change and include metallb doc related to those changes in the configuration it should be easy to review and get accepted.
If you have never made a PR, there are plenty of good tutorials online but given the details of your suggestion I think you should be fine.

That's the issue, I don't know what needs to be changed, only that you have to use CRDs and that ConfigMaps are dead.

to use CRDs and that ConfigMaps are dead

I looked into the Backward Compatibility and could figure out what is wrong in the current way of doing things ?  Can you elaborate a bit more ?

Ah. You see, I made one of the classic blunders, and got my projects confused. Please ignore my comment on configmaps!

closed by https://github.com/techno-tim/k3s-ansible/pull/383


Condition should be a list of strings instead of just a string

Condition should be a list of strings instead of just a string. As written now, there is a one-to-one between condition and filter strategy.
This allows for multiple conditions for a given filter strategy. This is how it was done in Philter Studio before it was discovered that "condition" is just a single string in the filter condition.

Changing from "condition" being a single string to "conditions" being a list of strings is a breaking change. While this won't affect any users right now, I should be careful around breaking changes. To prevent a breaking change here I could add "conditions" and leave "condition" as-is. This would put a restriction on the filter profile that both "condition" and "conditions" both cannot be specified. No logic like that currently exists in the filter profile.
Conditions can currently be AND'd so having "conditions" as a list really might not really e adding anything except readability.
Should there be "condition" and "conditions" where "conditions" is a list? This would provide backward compatibility. The only difference would be "conditions" would not need AND'd.


[Feature] Add hierarchy to Kafka monitoring

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
We have Kafka server monitoring and agent plugins(Java) for Kafka, and k8s monitoring, we should consider to add hierarchy support for Kafka.
Use case
No response
Related issues
No response
Are you willing to submit a pull request to implement this on your own?

[ ] Yes I am willing to submit a pull request on my own!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@peachisai I think this could be processed before https://github.com/apache/skywalking/issues/11926 as Kafka is more popular. WDTY?

@peachisai I think this could be processed before #11926 as Kafka is more popular. WDTY?

As RabbitMQ Hierarchy is nearly completed, I will set about doing Kafka showcase after RabbitMQ.
To consider resouces that Kafka  showcase will replace RabbitMQ showcase by default setting, Is It ?

As RabbitMQ Hierarchy is nearly completed, I will set about doing Kafka showcase after RabbitMQ.

Please go ahead.

To consider resouces that Kafka showcase will replace RabbitMQ showcase by default setting, Is It ?

We could have both, most importantly, we need to change the demo application codes and relative deployment, which could make Kafka in the topology and virtual MQ.