Two types of links to examples, only one works for sharing.

Overview
There are currently two types of URLs to examples:
https://godoc.org/net/http#ex-ResponseWriter--Trailers
https://godoc.org/net/http#example-ResponseWriter--Trailers
The first one is what the UI exposes in some cases, but it works poorly. It should be replaced with the second form.
Related to https://github.com/golang/go/issues/16753. /cc @bradfitz
Detailed Explanation and Reproduce Steps
Consider this scenario. I'm viewing a Go package on godoc.org:

I scroll down and run into an example I want to see:

I click on it to expand it:

Then I decide to share the link to this example with someone, so I right click its link and copy the URL:

The URL I have copied is:
https://godoc.org/net/http#ex-ResponseWriter--Trailers
Then suppose I share that url with someone and they click the link. Here's what they see:

Note:

The example is nowhere near in sight, the view is at the very top of the page.
The example is not expanded even if the user were to scroll to it.

However, if I hack the URL to change "ex" to "example", then everything works as expected:
https://godoc.org/net/http#example-ResponseWriter--Trailers

The solution in my mind seems to be that we should unify the two forms of links into the latter form, so there's only kind, and it works well for purposes of sharing a permalink with other people.

@shurcooL example-ResponseWriter--Trailers is the div above the href ex-ResponseWriter--Trailers.
Are we sure that is not just a wrong abbreviation causing the issue?

Are we sure that is not just a wrong abbreviation causing the issue?

Sorry, can you elaborate on what you mean?

Surely. Do we exactly know what or how "example" has been abbreviated to "ex"?

Nope, I don't know.
So far, I've only reported and described the issue for tracking purposes. It remains to investigate the cause. I suspect looking into the commit history and blame may lead to the change that explains the current situation with "example" and "ex". It's either a regression, or it might've been this way since the beginning and no one has discovered/reported the issue until now.

It looks like the #ex- links are used for the bootstrap collapse feature.

You are copying the link address of the expand/collapse anchor, not of the example itself.
Some possible improvements:

Disable the confusing copy link address result by using data-target instead of href to specify the expand/collapse target.  The use of data-target and href is documented here.
Display a self linking ¶ on hover over examples.

Thanks for the excellent writeup. +1. I came to report the same issue I encountered while trying to share an example link in gophers slack. I expect any URL with a fragment to load with the specified id visible


OriginalRequestID in Request can be null

The getOriginalRequestID() method states that it can never be null in the comments and therefore doesn't need a null check. This is incorrect. It will be null on initialisation. This method should have a null check.

This is incorrect, it actually does set the field properly on construction.

merged into develop


O(n^2) Performance Problem on repeated fields

According to the protobuf serialization specification, repeated fields need to be kept in-order.
As a quick fix for issue #35, the code was modified to append repeated fields to the end of the list.  However, that introduced an O(n^2) performance problem in hydrateOneRepeatedInstance.
Building the list in reverse order, then doing a final List.rev, would involve a more invasive set of changes: to be spec-compliant, the code must handle repeated fields that appear loose in the serialized stream and which may have other fields interspersed between.
Two implementation choices are:

Add pre- and post-processing abstract functions to MessageBase, which are run at the beginning and end of a call to merge a serialized stream into the object.  These would do a List.rev on every defined repeated field (but not packed-repeated, which already work properly).
Redefine the API contract and use ResizeArray (or similar) for all repeated fields, and just append to the end in constant time.

Frankly, option 2 makes the most sense: the intention behind MessageBase is to make generated protobuf objects friendly to other .NET languages (namely C#).  So, moving to a non-F# container here is actually more consistent with that design tenet.

@ctaggart & @tathanhdinh: I'm working on a fix for this by redefining the contract to use ResizeArray.  At the same time, I also did a first pass at providing Record serialization (rather than Class serialization).
Turns out that idiomatic F# using Records is just slightly faster than a more imperative approach.  I was shocked that the following produces code with reasonable performance:
    let internal decoderRing =
        [
            1, fun m rawField -> { m with id = rawField |> hydrateInt32 }
            2, fun m rawField -> { m with name = rawField |> hydrateString }
            3, fun m rawField -> { m with option = rawField |> hydrateBool }
            4, fun m rawField -> { m with test = rawField |> hydrateEnum }
            5, fun m rawField -> { m with packedFixed32 = rawField |> hydratePackedFixed32 }
            6, fun m rawField -> { m with repeatedInt32 = (rawField |> hydrateInt32) :: m.repeatedInt32 }
        ]
        |> Map.ofList

I might just reimplement the Class interface in terms of Records, or drop the Class API completely... Thoughts?
jh

@ctaggart @tathanhdinh:
Did a quick implementation using ResizeArray and at the same time took a crack at providing Record serailization/deserialization.
Turns out that idiomatic F# using Records is... just... slightly faster than the Class implementation using ResizeArray!  I was shocked that the following decode logic performs very well:
    let internal decoderRing =
        [
            1, fun m rawField -> { m with id = rawField |> hydrateInt32 }
            2, fun m rawField -> { m with name = rawField |> hydrateString }
            3, fun m rawField -> { m with option = rawField |> hydrateBool }
            4, fun m rawField -> { m with test = rawField |> hydrateEnum }
            5, fun m rawField -> { m with packedFixed32 = rawField |> hydratePackedFixed32 }
            6, fun m rawField -> { m with repeatedInt32 = (rawField |> hydrateInt32) :: m.repeatedInt32 }
        ]
        |> Map.ofList

    let internal decodeFixup (m:InnerMessage) =
        { m with
            packedFixed32 = List.rev m.packedFixed32
            repeatedInt32 = List.rev m.repeatedInt32 }

So, I am considering dropping the Class API completely in favor of the Record API, or redefine it in terms of the Record API (use records internally to the Class API).
Thoughts?
jh

Fixing this via implementing class serialization in terms of the record-serialization support, mainly as described above.


superagent HTTP method defined as string not working

In the supertest documentation it says, Anything you can do with superagent, you can do with supertest.  Then reading the documentation for superagent it shows how the HTTP method may also be passed as a string.
request('GET', '/search').then(success, failure);

However, I can't seem to get it to work, always getting back TypeError: agent is not a function.
Below is a small example highlighting what I'm trying to do in my test.
'use strict';

const app = require( './../server' );
const supertest = require( 'supertest' );
const assert = require( 'assert' );
const agent = supertest.agent( app );

let status = 200;
let route = 'accessories';
let method = 'get';

describe( 'test known things', function () {
    it( 'returns ' + status, function ( done ) {
        agent( method, '/' + route )
            .then( function( res ) {
                assert.strictEqual( res.status, status );
                done();
            })
            .catch( function( err ) {
                done( err );
            });
    });
});

If I switch out the method as string for the chained method, it works, but need to be able to call method as string for the way I'm building the test.  Is there something I'm missing from the documentation, or is the method as string something that's no longer supported?
Thanks.

You can do the following:
Access the agent with an indexed key agent[method]. Should be able to achieve the result you're after.
'use strict';

const app = require( './../server' );
const supertest = require( 'supertest' );
const assert = require( 'assert' );
const agent = supertest.agent( app );

let status = 200;
let route = 'accessories';
let method = 'get';

describe( 'test known things', function () {
    it( 'returns ' + status, function ( done ) {
        agent[method]('/' + route )
            .then( function( res ) {
                assert.strictEqual( res.status, status );
                done();
            })
            .catch( function( err ) {
                done( err );
            });
    });
});


是不是可以增加解析相同的key为map

例如
<EMAIL_ADDRESS><EMAIL_ADDRESS>解析为{a<EMAIL_ADDRESS>虽然可以用分隔符，但这样增加修改配置还是更直接方便
类似 https://github.com/itkinside/itkconfig
Lists of key-values

Often a simple Key => Value mapping is not sufficient, and you want a key mapping to an array of values. This if fully supported and you can define your struct as:

type Config struct {
  Foo []string
  Bar []float64
  Zoo []int
}
And then in your config-file:

Foo = string number one.
Foo = string number two.
Bar = 1.0
Bar = 2.0
Zoo = 1
Zoo = 2
Which, you guessed it, will map to the arrays Foo{"string number one.", "string number two"}, Bar{1.0,2.0} and Zoo{1,2}.

据说不更新了，看到go-ini了，关闭

额。。go-ini好像也没有你说的这个功能，虽然可以自动解析数组到结构的数组。。https://github.com/go-ini/ini#map-to-struct


Global Setting for Parallelization

I'm not sure if this is expected behaviour or not but when I attempt to run a pipeline that is a map (say with "parallelism": 3) on a repo that is produced by a reduce, the pipeline fails because the data from the reduced repo is only available to one of the shards.
Full code
log of code output
The pipelines created are basically:
square (map) ---> sum (reduce) ---> scale (map)
Is there a way to get around this? The implication to me would be that once a reduce is performed any job or pipeline that has that repo as an input cannot be parallelized. I have yet to attempt running a pipeline in parallel off the repo produced by scale, but either way this presents a fair bit of a bottleneck if there isn't a way of circumventing the issue.

Hi Erik - sorry you ran into this.
From my understanding this is not expected behavior. We want to enable composing pipelines together in many ways, and performing a reduce should not prohibit performing any maps downstream.
We'll look into this.

Alright I did some investigating and I think I understand what's going on. The problem here is that our behavior for pipelines that take 2 inputs doesn't quite match up with your expectation. Right now what we implement is the following: if a job takes 2 inputs then we'll make sure that every datum in those repos is seen by exactly 1 container. The sum repo in your example contains a single file which means that only 1 of the containers sees it and the other 2 don't. If the sum repo were the only input then pachyderm would cull the other 2 containers because they're won't see any data and we don't start empty containers. However they're actually not empty, because you have another input square and it has enough data for each container so some containers get started with data from square but no data from sum which leads to the crash.
I think the behavior you were expecting was basically a cross product, you want every line in square to be seen by a container with the file in sum present so that you can use it. @erikreppel does that describe the behavior you were expecting?

Yeah exactly.
The purpose of this was to see the case of a single number has been produced as the result of prior calculations and stored in a repo and we want to scale every point of data from a file in a different repo by that number since a really common thing we do.
Any ideas on how to efficiently do this?
As an aside I noticed the other day that if you specify "shard": 3 on a reduce pipeline in the logs it appeared spin up 3 containers, all of them seeing files, but only one of the containers having files with actual data in them which kind of surprised me. Is that expected? I assumed it wouldn't happen since you don't spin up empty containers.

@erikreppel thanks, that all makes sense this is a behavior we've talked about a bunch but wanted to understand how users perceived this issue before we started implementing things. Based on this and other conversations we've had I think that the cross product behavior is going to be what the average user expects so I think we'll make that the default.

Any ideas on how to efficiently do this?

Right now I think your best bet would be to just scale down to a parallelism factor of 1 so that you can get unblocked. We're going to look into getting the cross product implemented for you ASAP and then your old code should just work.
1 more question: does the behavior as it stands now seem useful to you? and if so how would you expect it to be exposed to you?

Its useful from an efficiency standpoint but those kinds of cross product operations are pretty common. For us at least I think cross product type of operations would be the most common thing we do from a processing standpoint.
The ideal behavior to me would be that I can set a flag for an input to a pipeline to be globally available so it appears in every container spun up by the pipeline.

Alright, we just had a big discussion of this offline here's what we came to for a direction on this feature. Here's what it's going to look like:

The default for parallelism is going to switch from union to cross product, meaning that when a pipeline takes 2 inputs we guarantee that the each pair of datums will be seen by exactly 1 container. This means a single datum might be seen more than once.
Inputs will have a boolean global flag on them. This flag indicates that this input repo should be seen by every container run in the job.

@erikreppel and I were discussing this offline a bit. The need for this may be related to the unavailability of more typical map/reduce semantics. In a conventional map-reduce you assign your keys in the map phase and then the reduce operation can be shared per key. In the case of pachyderm, there is only one shard level in reduce (all).  One way to get more typical map-reduce sematics would be to allow for finer sharding in the reduce stage, say per file. That way one can shard their reduce while still having an atomicity guarantee.

@JonathanFraser what you're saying makes total sense, I think what we have is already pretty close to what you're describing. In our system a map shards over blocks, meaning that a single file may be split over several different containers. In reduce jobs we shard over files, so each file will be seen by exactly one container but any 2 files could wind up in separate containers and not be seen together. I believe those are the semantics you're describing but correct me if I'm wrong. With this issue we'd be adding a 3rd mode of input global which would specify an input that every container in a job sees all the files of no matter what.

@jdoliner ahh, this could just be misunderstanding of what pachyderm is doing under the hood.  If you are saying reduces are parallelized on a per file basis already then ignore my tom foolery. But yes having a flag which allows for a complete view of a repo is useful.

Updated the title to reflect the action needed. Was formerly 'Map job performed on a repo produced by a reduce cannot be parallelized'

#393 added a way to have a complete view of a repo in a job.  Refer to the updated pipeline spec for details.  Feel free to reach out to us if anything is unclear!


Changed default text in branch popup

When only selecting one transport in in Transport to Branch it is handy if the branch name and commit message defaults to the transport number and transport description.
I've added a check to see if only one transport is selected and if so uses the transport number as branch name and transport description as commit message.
If more than multiple transports are selected the logic is untouched.
Is there a better way to get the text from E07t than a select directly in the popup? It feels like overkill to implement a whole repo class for this single select.

Welcome to abapGit as a contributor 🥇


EPMRPP-87023 || No UI validation on Create/Edit Gitlab integration modals when user enters non-digits in project ID field

I can not even reproduce this bug.
Could you explain the reason, why useMemo is used here?

I can not even reproduce this bug.
Could you explain the reason, why useMemo is used here?
The instance has updated plugin already.
It's necessary to fill in all fields on the form and after focus api key get focus on project id and add any letter.
Uncaught Error: Maximum update depth exceeded


Build: unknown directive: toolchain

I just tried building postfix_exporter because I needed systemd support. go build -tags nodocker reports
$ go build -tags nodocker
go: errors parsing go.mod:
/home/bfroehler/devel/postfix_exporter/go.mod:5: unknown directive: toolchain

Not that familiar with go, but I suppose my go version could be too old?
$ go version
go version go1.19.8 linux/amd64
```
This is the default version on Debian 12...

It would be nice if the minimum required go version would at least be stated somewhere.

As suspected - this has to do with a too old go version - when trying with the latest release (1.23) installed as explained here build runs fine.


how can I get an action list that actually uses keys and values in the HTML and not generic things?

Is your feature request related to a problem? Please describe.
I describe what I want in my actionList in my prompt and also prompt it like
Use the above information to generate the appropriate actionList based on the provided HTML from the URL "https://www.xxxxxxxxxxxxx/manager/login" which is the login page for an online store.  The actionList should be structured to navigate the login process effectively by interacting with the relevant elements on the page such as input fields for username and password and clicking the login button.  Ensure that the actionList is logically ordered to reflect the flow of the login process. The keys and values of the "params" of the JSON need to be filled in with the values found in the HTML of the login page.  Never use keys and values that are not in the HTML of the login page.

I'm getting this:
--- Executing Parse Node ---
--- Executing GenerateAnswer Node ---
{
    "actionList": [
        {
            "action": "navigate_to_url",
            "params": {
                "url": "https://www.xxxxxxxxxxx/login",
                "timeout": 5
            }
        },
        {
            "action": "wait_for_element",
            "params": {
                "by": "id",
                "value": "m_id",
                "timeout": 10
            }
        },
        {
            "action": "input_text",
            "params": {
                "by": "id",
                "value": "m_id",
                "text": "your_username"
            }
        },
        {
            "action": "wait_for_element",
            "params": {
                "by": "id",
                "value": "m_passwd",
                "timeout": 10
            }
        },
        {
            "action": "input_text",
            "params": {
                "by": "id",
                "value": "m_passwd",
                "text": "your_password"
            }
        },
        {
            "action": "wait_for_clickable",
            "params": {
                "by": "id",
                "value": "login_button",
                "timeout": 15
            }
        },
        {
            "action": "click_element",
            "params": {
                "by": "id",
                "value": "login_button"
            }
        }
    ]
}

but that is wrong as login_button should be loginBtn and m_passwd should be m_pw.
It only got m_id correctly but that's because in my prompt (not shown) I had
 - **Possible Identifiers**:
     - `"by"`: Identifies the input field, e.g., `"id"`, `"name"`, `"class"`.
     - `"value"`: The identifier of the input field.  For example, in `"<input type="text" id="m_id" name="m_id" placeholder="관리자 아이디" value="">"` the value would be `"m_id"`.
     - `"text"`: The text to be entered, such as `"username"`, `"password"`.
   - **Explanation**: This action targets a specific input field and enters the defined text, supporting the automation of user input tasks.

Describe the solution you'd like
I want it to fill the JSON params with actual values from the HTML  I've tried reading it in as a file and accessing the actual URL and the results are bad either way.
Describe alternatives you've considered
I guess to try this iteratively but this also fails:
login_extraction_prompt = """
Extract the HTML elements in the input HTML that have to do with the login process.  This includes the input fields for the username and password and the login button.  Provide the HTML tags and attributes of these elements.  This information will be used to generate an actionList that will be used to crawl the login page.  Return it in JSON format where the keys are the functionality of the element and the values are the actual HTML elements.  For example, if the input fields for the username and password are identified by their id attributes, the JSON would look like this:
json:
{"username": "<input id='username' type='text'>", "password": "<input id='password' type='password'>", "login_button": "<button id='login_button'>Login</button>"}

Only use HTML elements that are in the HTML.  NEVER use any elements that are not in the HTML.  NEVER maks up any elements.  Only use the actual elements in the HTML.
"""

gives
--- Executing Parse Node ---
--- Executing GenerateAnswer Node ---
{
    "username": "<input id='username' type='text'>",
    "password": "<input id='password' type='password'>",
    "login_button": "<button id='login_button'>Login</button>"
}

My code is pretty much the demo code:
load_dotenv()

OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")

# set the file path and read into var
file_path = "/mnt/d/1_Conai/Scrapegraph-ai/examples/openai/html-samples/xxxxxxx_login.html"
login_url = "https://www.xxxxxxxr/manager/login"
# It could be also a http request using the request model
with open(file_path, 'r', encoding="utf-8") as file:
    text = file.read()

# ************************************************
# Define the configuration for the graph
# ************************************************

graph_config = {
    "llm": {
        "api_key": OPENAI_API_KEY,
        "model": "openai/gpt-4o",
    },
    "verbose": True,
    "headless": False,
}

# ************************************************
# Create the SmartScraperGraph instance and run it
# ************************************************

smart_scraper_graph = SmartScraperGraph(
    prompt=login_extraction_prompt,#scrapegraph_ai_prompt,
    #prompt=scrapegraph_ai_prompt,
    #source=login_url, #"https://scrapegraphai.com/",
    source=text,
    config=graph_config
)

result = smart_scraper_graph.run()
print(json.dumps(result, indent=4, ensure_ascii=False))
# ************************************************
# Get graph execution info
# ************************************************

graph_exec_info = smart_scraper_graph.get_execution_info()
print(prettify_exec_info(graph_exec_info))

hi, you should for example use selenium for fetching the code and after passing It to scrapegraph

But it doesn't even work when I read in the HTML into a variable and then run Scrapegraph on that.  I clearly see the HTML in stdout?  I know what you are saying to pass the HTML back to local and then run Scrapegraph on it.


[stable/rabbitmq-ha]Endpoint for RabbitMQ Prometheus native port

Is this a new chart
No
What this PR does / why we need it:
The features add a new Endpoint for Prometheus, by default is 15692
Important for use the feature kubernetes_sd_configs: - role: pod
Complete the PR: https://github.com/helm/charts/pull/17925
Which issue this PR fixes
Special notes for your reviewer:
@steven-sheehy: With PR I can do this:

Since the metrics are per node, I need all the nodes, so I can use the grafana tempaltes
cc @gerhard
Thank you
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

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

Signed-off-by: Gabriele Santomaggio<EMAIL_ADDRESS>

/ok-to-test

Done. Tested both the usage of old exporter and the new plugin. Both work and appear in Prometheus targets. If old exporter is enabled endpoints for the new plugin won't show up, is either one or the other.

Thank you @MihaiAnei

The other PR also bumped RabbitMQ to 3.8.0. I assume that will be in a follow up PR by someone?

Wasn't sure if I should do it here.

Please add tests to verify exporter and new plugin work correctly (servicemonitor can't be tested).
That is create a exporter-values.yaml with prometheus.exporter.enabled=true and a prometheus-plugin-values.yaml with rabbitmqPrometheusPlugin.enabled=true.

All the changes are tested and work properly on an EKS cluster with Prometheus Operator on it. The problem with CI is the default namespaces used to create ServiceMonitor in monitoring which doesn't exist for the CI jobs. Can disable operator for CI but then it would definitely not test ServiceMonitor resource creation.
The timeout in CI regarding the exporter container might be because the CI waits to little for the first Pod to initialize.
Any advice?

You need to set prometheus.operator.enabled=false in the test values. This was what I meant by "servicemonitor can't be tested".

You need to set prometheus.operator.enabled=false in the test values. This was what I meant by "servicemonitor can't be tested".

🤦♂ .... yup, that would make sense. We can test ServiceMonitor creation if its namespace would allow null values and have default .Release.Namespace. But that is a story for another pull request.

@Gsantomaggio
Would you volunteer to be one of this chart owner please? See:
https://github.com/helm/charts/issues/13867


add symfony/yaml to dependencies

Because this dependency requires only in composer require-dev mode ( by phpunit), it should be required in production too

Coverage decreased (-2.02%) to 34.146% when pulling 9fd3ed3cbc73cc3a80ce14a705e5fcb10840d177 on xakzona:master into e609da6d565c6a65af2615ada613425d959f69d8 on merorafael:master.

It can also go to suggests section because you do not have to use HtmlFormatter


document reloader dependency on actuator-autoconfigure

Signed-off-by: Paul Czarkowski<EMAIL_ADDRESS>

The error in circleci appears to be unrelated to my change.

I don't think this is actually needed...

I think it is, the plain starter doesn't include config.

I'm looking to see if the reload example works as is

It definitely needs the actuator and reload endpoint enabled, I was bashing my head against this all day yesterday.

I just tried https://github.com/spring-cloud/spring-cloud-kubernetes/tree/master/spring-cloud-kubernetes-examples/kubernetes-reload-example which I just realized that is does have spring-boot-actuator-autoconfigure.
So yeah, this makes sense!

@paulczar Would you also please update the reload example with the changes proposed by @ryanjbaxter?

Actuator needs to remain optional.


Update remaining jinja docs

Summary of the Pull Request
What is this about?
Closes #2820

Codecov Report

Merging #2838 (aec6c01) into main (21374b3) will decrease coverage by 3.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2838      +/-   ##
==========================================
- Coverage   29.87%   26.80%   -3.08%
==========================================
  Files         324      125     -199
  Lines       39062    13237   -25825
==========================================
- Hits        11671     3548    -8123
+ Misses      27391     9689   -17702

Impacted Files
Coverage Δ

src/agent/onefuzz-agent/src/main.rs

src/agent/onefuzz-task/src/tasks/config.rs

...ent/onefuzz-task/src/tasks/generic/input_poller.rs

src/agent/onefuzz/src/blob/client.rs

...rc/agent/input-tester/src/test_result/fast_fail.rs

src/agent/onefuzz-agent/src/coordinator.rs

...gent/input-tester/src/test_result/vcpp_debugger.rs

src/agent/coverage-legacy/src/region.rs

src/agent/onefuzz-task/src/local/tui.rs

...zz-task/src/tasks/generic/input_poller/callback.rs

... and 189 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


too slow in preview feature

Microsoft PowerToys version
0.66.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce

taking more loading time preview

error message in power toys
✔ Expected Behavior
performance boost
❌ Actual Behavior
slow preview and some other lag
Other Software

/dup #23384


Pass HttpContext into lambda.

Sorry for the Christmas delay. This looks awesome! Thanks for taking this on.

@aidanjryan, cool, thanks!  Let me know if you have other interesting requests.  I was looking at the code, and there is some other cool stuff that could be done, but I just don;'t have a good reason to do some of it.  Feel free to file a bug if you think of something.

@twitchax Nice! Thanks for providing this library, it's super helpful.


New version: Coldlake.StellarPlayer version 2.24.1411.30<PHONE_NUMBER>0722)

Created by 🥟 Dumplings in workflow run #4656.
Logs
https://www.stellarplayer.com/blog/category/post/changelog
Updated:<PHONE_NUMBER>2029 →<PHONE_NUMBER>0722
Submitting WinGet manifests

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installer Verification Analysis Context Information:
Installer https://player-download.coldlake1.com/player/20240411200722/Stellar_20240411200722_official_stable_full_x64.exe
Scan request id: 'e327b31b-0a63-464c-a6e5-bba20821fcb2'
Error information: BlockingDetectionFound

4/25/2024 5:25:17 PM

Installer Validation

(Automated response - build 877.)

This might be due to a network block of data centers, to prevent automated downloads.
(Automated response - build 877.)


rearm fails - cannot read property 'Location'

attempting to rearm throws an error:
$ iectrl rearm 8
ERROR: TypeError: Cannot read property 'Location' of null

my env:
$ node --version
v0.10.32
$ npm --version
2.0.0
$ iectrl --version
0.0.5
$ iectrl list
Available virtual machines:

IE8 - Win7
IE9 - Win7
IE10 - Win7
IE11 - Win7

After wiping everything and reinstalling with ievms and getting the latest VirtualBox this doesn't appear to be an issue any longer.


19797 - Optimizing cypress tests

*Issue:19797 *https://github.com/bcgov/entity/issues/19797
Description of changes:

Optimizing cypress tests

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun

Temporary Url for review: https://bcregistry-btr-dev--pr-128-6mverhm3.web.app


Unittest

Current coverage is 5.96%

Branch #1 has no coverage reports uploaded yet.

No diff could be generated. No reports for master found.

Powered by Codecov. Updated on successful CI builds.

I get the following exception with the latest version. Any idea?
The root cause:
Caused by: java.lang.NoClassDefFoundError: org/springframework/orm/jpa/LocalContainerEntityManagerFactoryBean
at org.springframework.boot.orm.jpa.JpaEntityScanRegistrar$JpaEntityScanBeanPostProcessor.postProcessBeforeInitialization(JpaEntityScanRegistrar.java:58)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:408)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1570)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
... 58 more


Package unixodbc-dev has incorrect include

Describe the issue
The package unixodbc-dev is trying to include the file "unixodbc.h" in version 2.3.11. That file does not exist in the package so it fails.
In version 2.3.7 the file of "unixodbc_conf.h" is part of the installed package and is used.
In version 2.3.11 the file of "unixodbc_conf.h" is part of the installed package but for some reason, the file "unixodbc.h" is referenced in sqltypes.h which is also part of the unixodbc-dev package.
Also, the file "unixodbc_conf.h" in 2.3.11 looks like it has been generated for a particular computer, compared to the file in 2.3.7 that looks like a generic source file ready to be compiled.
When did the issue occur?
The problem was first noticed yesterday, but if you're asking when the problem originated, it is somewhere between unixodbc-dev_2.3.7 and unixodbc-dev_2.3.11.
unixodbc-dev_2.3.7/usr/include/sqltypes.h:
#ifndef SIZEOF_LONG_INT
#include "unixodbc_conf.h"
#endif

unixodbc-dev_2.3.11/usr/include/sqltypes.h line 55-57:
#ifndef SIZEOF_LONG_INT
#include "unixodbc.h"
#endif

If appplicable, what package did you attempt to install, and from which repo?
Package is unixodbc-dev and appears to be installed from:
https://packages.microsoft.com/ubuntu/20.04/prod focal/main amd64 unixodbc-dev amd64 2.3.11 [42.1 kB]

Debugging was done by manually downloading files from https://packages.microsoft.com/ubuntu/20.04/prod/pool/main/u/unixodbc/ and inspecting contents of files.
Steps to Reproduce
Short version, try to compile unixodbc into an application and it will fail
In file included from /usr/include/sql.h:19,
                 from /home/runner/work/php-src/php-src/ext/odbc/php_odbc_includes.h:107,
                 from /home/runner/work/php-src/php-src/ext/odbc/php_odbc.c:33:
/usr/include/sqltypes.h:56:[10](https://github.com/php/php-src/actions/runs/4148457300/jobs/7176463762#step:8:11): fatal error: unixodbc.h: No such file or directory
   56 | #include "unixodbc.h"
      |          ^~~~~~~~~~~~
compilation terminated.

I don't have a standalone test case.
Actual Result
Fails to find file as it is looking for the wrong file name.
Expected Result
Compilation succeeds
Screenshots

Additional context
This was noticed as part of PHP's ci

i have the same problem, when i install the package in my docker container (PHP-fpm 8.1) and enter to the path /usr/include, there's no the unixodbc.h in the listed files.

I have the same problem, when i install the package in my docker container
the script works correctly until january 2023. Nothing has changed and now it has these issues
My DockerFile
https://github.com/bjverde/formDocker/blob/master/debian10_php8.1_mssql/debian10_apache_php81_mssql.Dockerfile

In Debian 10, with php 8.1 changing the repository from Debian 10 to Debian 9. It will create the Docker script, I haven't tested if it will connect to the database, I believe so.
Change
https://packages.microsoft.com/config/debian/10/prod.list
to
https://packages.microsoft.com/config/debian/9/prod.list

Yeah, this hit us as well when trying to deploy a python application that uses pyodbc

With PHP 8.1 and Debian 11, changing the repository from 11 to 10 or from 11 to 9 does not fix the problem.  I still get the error :
/usr/include/sqltypes.h:56:10: fatal error: unixodbc.h: No such file or directory

Hello,
Switching to the PHP image tag 8.1-apache-buster and changing the repository to 9 helped me.
https://packages.microsoft.com/config/debian/9/prod.list
https://hub.docker.com/_/php/tags?page=1&name=8.1-apache-buster

i have the same problem. App built using 8.1.12-fpm-bullseye and i cannot replace this with something else.

I also have this problem when trying to install SQL Server drivers for PHP 8.2 on Debian 11
sudo pecl install sqlsrv

I'm currently working around this on php:8.1-bullseye by forcing installation of the old version:
apt-get install unixodbc-dev=2.3.7 unixodbc=2.3.7 odbcinst1debian2=2.3.7 odbcinst=2.3.7

I confirm that Jack's solution works, thanks ;)

I'm currently working around this on php:8.1-bullseye by forcing installation of the old version:
apt-get install unixodbc-dev=2.3.7 unixodbc=2.3.7 odbcinst1debian2=2.3.7 odbcinst=2.3.7

I had to run this on python:3.7-slim-buster:
apt-get installunixodbc-dev=2.3* unixodbc=2.3* odbcinst1debian2=2.3* odbcinst=2.3*

https://packages.debian.org/buster/unixodbc-dev 2.3.7 doesn't seem to exist on the official PPA...

I can confirm the issue occurs for me as well, when using docker container based on debian11 distribution,
and trying to install pyodbc module for python2.
For python3 on same docker - no issues.
The WA that worked for me for now is similar to suggested above - install 2.3.7 versions explicitly:
apt-get install unixodbc-dev=2.3.7 unixodbc=2.3.7 odbcinst1debian2=2.3.7 odbcinst=2.3.7

Hit the same problem with pyodbc package (4.0.30) on python3.10.

For python3 on same docker - no issues.

Probably OK either because docker caches, or because using latest pyodbc version 4.0.35, which has binaries for x86_64_linux_glibc, so it skips compilation.. But the problem (broken include files) are still there.
Problem can still be reproduced by disabling binary downloads;
pip install --no-cache-dir --no-binary pyodbc --no-cache-dir pyodbc==4.0.35

Version pinning in apt-get install line helped our case as well, until this issue is fixed.

How to check the cause
$ grep -nir -e 'unixodbc.*\.h' /usr/include/sqltypes.h

should NOT return a line like following;
#include "unixodbc.h"

because that file (unixodbc.h) is not packaged.
Correct result;
# grep -e unixodbc.*\.h /usr/include/sqltypes.h
 * the install creates a unixodbc_conf.h file that contains the current build settings
#include "unixodbc_conf.h"

ubuntu 22.04 i confirm Jake's solution works too.
RUN ACCEPT_EULA=Y apt-get install -y
msodbcsql17
mssql-tools
unixodbc-dev=2.3.7
unixodbc=2.3.7
odbcinst1debian2=2.3.7
odbcinst=2.3.7
RUN echo 'export PATH="$PATH:/opt/mssql-tools17/bin"' >> ~/.bashrc RUN exec bash
RUN pecl install sqlsrv-5.8.0 RUN printf "; priority=20\nextension=sqlsrv.so\n" > /etc/php/7.3/mods-available/sqlsrv.ini

We are aware of the problem and are working on an updated 2.3.11 package for unixodbc-dev, ASAP.
Regards,
David

I could build with Debian 9.
curl https://packages.microsoft.com/keys/microsoft.asc | apt-key add -
&& curl https://packages.microsoft.com/config/debian/9/prod.list > /etc/apt/sources.list.d/mssql-release.list
&& apt-get -y update
&& ACCEPT_EULA=Y apt-get install -y gnupg2 msodbcsql17 unixodbc-dev \

I am having the same issue ia there a timeline for a fix?

I'm currently working around this on php:8.1-bullseye by forcing installation of the old version:
apt-get install unixodbc-dev=2.3.7 unixodbc=2.3.7 odbcinst1debian2=2.3.7 odbcinst=2.3.7

I had to run this on python:3.7-slim-buster:
apt-get install unixodbc-dev=2.3* unixodbc=2.3* odbcinst1debian2=2.3* odbcinst=2.3*

https://packages.debian.org/buster/unixodbc-dev 2.3.7 doesn't seem to exist on the official PPA...

On python:3.7.7-slim-buster I had to run:
apt-get --allow-downgrades -y install unixodbc-dev=2.3.7 unixodbc=2.3.7 odbcinst1debian2=2.3.7 odbcinst=2.3.7

This issue comes up when installing pdo_sqlsrv and sqlsrv PHP extensions on Ubuntu with PHP-FPM. Reproduced on 2 machines, making an upgrade to PHP8.1 not possible.
This documentation is currently not functional then:
https://learn.microsoft.com/en-us/sql/connect/php/installation-tutorial-linux-mac?view=sql-server-ver16

Same issue here. The docker build was working fine using 'apt-get install unixodbc unixodbc-dev"  until today. Getting the same error

This probably isn't a good solution, but something that's working for us is to keep a copy of unixodbc.h from a version that was working, and copy it to where it's being looked for in the Docker build:
COPY ./docker/build/unixodbc.h /usr/include/unixodbc.h

I can't say I'd recommend this and YMMV, but it's something that's allowed us to keep the version of Ubuntu and MSSQL driver.

We are aware of the problem and are working on an updated 2.3.11 package for unixodbc-dev, ASAP.
Regards, David

If this was a problem in a Linux distro, it would've been fixed quite quickly. I'm quite disappointed Microsoft can't do that.

@David-Engel the fact that my employer is paying for SQL Server and this is still not not fixed is not good.

Is there a timeline for this to be fixed? I am not able to implement any of the workarounds

Is there any plan to support Ubuntu 18.04 as well (especially in Az pipeline vm image) ?
Having to migrate to a newer version of Ubuntu to resolve this bug is a no go.

It is still failing in Az pipeline using vm image Ubuntu 18.04. Any plan to support that version as well (having to upgrade to new Ubuntu version in order to fix this bug is a nO go) ?

This is still an issue in python:3.10-buster when installing pyodbc==4.0.28.
I tried this: unixodbc-dev=2.3.7 unixodbc=2.3.7 odbcinst1debian2=2.3.7 odbcinst=2.3.7
with https://packages.microsoft.com/config/debian/10/prod.list (and 11) without success.
Exception is the same: /usr/include/sqltypes.h:56:10: fatal error: unixodbc.h: No such file or directory
When I downgrade to Debian 9 everything works as expected.

Update: works with pyodbc==4.0.35 and --allow-downgrades unixodbc-dev=2.3.7 unixodbc=2.3.7 odbcinst1debian2=2.3.7 odbcinst=2.3.7

Why has Microsoft started providing the unixodbc packages?
Why can't we use the packages provided by Ubuntu?

This is still an issue in python:3.10-buster when installing pyodbc==4.0.28.
I tried this: unixodbc-dev=2.3.7 unixodbc=2.3.7 odbcinst1debian2=2.3.7 odbcinst=2.3.7
with https://packages.microsoft.com/config/debian/10/prod.list (and 11) without success.
Exception is the same: /usr/include/sqltypes.h:56:10: fatal error: unixodbc.h: No such file or directory
When I downgrade to Debian 9 everything works as expected.

Update: works with pyodbc==4.0.35 and --allow-downgrades unixodbc-dev=2.3.7 unixodbc=2.3.7 odbcinst1debian2=2.3.7 odbcinst=2.3.7

Update: works with pyodbc==4.0.35, Debian 10 and no downgrades

In ubuntu 20 the solution was downgraded to
unixodbc-dev=2.3.6-0.1build1 unixodbc=2.3.6-0.1build1 odbcinst1debian2=2.3.6-0.1build1 odbcinst=2.3.6-0.1build1

Closing as the original issue (unixodbc.h) has been resolved.
For issues with libodbc1 vs libodbc2, refer to this issue.

Hello, I tried to use Ubuntu's MS repo in Debian 11 and it works.
https://packages.microsoft.com/config/ubuntu/22.04/prod.list
For Debian's repo, it generates an error
#4 46.79 grep: /usr/lib/x86_64-linux-gnu/libltdl.la: No such file or directory
#4 46.79 /bin/sed: can't read /usr/lib/x86_64-linux-gnu/libltdl.la: No such file or directory
#4 46.79 libtool: link: '/usr/lib/x86_64-linux-gnu/libltdl.la' is not a valid libtool archive
#4 46.79 make: *** [Makefile:249: sqlsrv.la] Error 1
#4 46.79 ERROR: `make' failed```

after running the command

`pecl install sqlsrv`

Hello, I tried to use Ubuntu's MS repo in Debian 11 and it works.
https://packages.microsoft.com/config/ubuntu/22.04/prod.list
For Debian's repo, it generates an error
#4 46.79 grep: /usr/lib/x86_64-linux-gnu/libltdl.la: No such file or directory
#4 46.79 /bin/sed: can't read /usr/lib/x86_64-linux-gnu/libltdl.la: No such file or directory
#4 46.79 libtool: link: '/usr/lib/x86_64-linux-gnu/libltdl.la' is not a valid libtool archive
#4 46.79 make: *** [Makefile:249: sqlsrv.la] Error 1
#4 46.79 ERROR: `make' failed```

after running the command

`pecl install sqlsrv`

I am running into this error now on Ubuntu 22.04

I'm currently working around this on php:8.1-bullseye by forcing installation of the old version:
apt-get install unixodbc-dev=2.3.7 unixodbc=2.3.7 odbcinst1debian2=2.3.7 odbcinst=2.3.7

Hi,
I'm trying to install sqlsrv in a debian buster container that I'm building on a mac m1, but I can't use jake's solution since there are no arm64 packages available for version 2.3.7 (even using debian 11), and therefore I run into this incorrect include error when doing pecl install sqlsrv.
Are there any actual workaround in this scenario?


Allow auto import for shorthand object notation {XXX}

Suggestion
🔍 Search Terms

✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
Currently, in vscode:
const obj = { XXX };

When XXX is not import yet.
It doesn't auto complete and auto import XXX for the code above. And the auto fix doesn't try to import XXX.
but for code:
const obj = { XXX: XXX }

It would auto complete and auto import XXX when typing the second XXX. And the auto fix would import XXX for the second XXX.
I suggest typescript will auto import and auto fix for first code.
📃 Motivating Example

💻 Use Cases

Currently, auto-imports disabled for shorthands.
 // If current completion is for non-contextual Object literal shortahands, ignore auto-import symbols
 if (isNonContextualObjectLiteral) return false;

I think @andrewbranch can help clarify this case.

I suggested disabling it because I thought it would be a somewhat unusual case. Part of the thinking was that if you start typing in an object literal, there’s a pretty good chance that you’re actually just going to type a unique key name followed by :, and so none of our completions are going to be useful to you, so we better make the completions we do offer pretty unobtrusive. I would be particularly worried about a situation like this: suppose I want to type const x = { state: true }, and I get completions when I've gotten to const x = { s. I see that the top one actually does say state. “Cool!” I think, as I press tab. But it turns out it was an auto-import of some identifier named state that I didn’t care about, and I just hit it too quickly to notice that it was an auto-import. Perhaps I have to hit undo and re-type the rest of my property, or perhaps I don’t even notice the mistake, and later TypeScript complains that I’ve never used that import. So I think I’m biased toward disabling auto-imports whenever you’re in a new identifier location. But I’m open to feedback.

I agree the auto completions auto import is sometimes annoying, it is very easy to accidently import something that I don't want.
But in my origin post, I also point the "auto fix" or "code action" to auto import.
For example, when I fully typed {XXX}, and typescript know XXX is an invalid symbol. Then when I move the cursor to the XXX, press Ctrl + ., there should be a menu to help me import the XXX.

Ah yeah, we can definitely give the codefix there. That’s no problem.


Setting title of segmentedControl

how to set the title for section at index programatically without using to call the delegate method within the child view controllers.  If my MXSegmentedPager has three view controllers. Within those three view controllers can i change the title for section at Index. ?

No you cannot change the titles like that. But reloading the segmentedPager will recall you delegates methods.


Add collecting with sparrow wallet guide to handbook

there is an issue with ord and the way it picks addresses from the wallet that can be "fixed" on sparrow with increasing the gap limit to 1000-2000, i think it's worth mentioning in the guide


Update publish GitHub action to create an issue on failure

Incorporates the changes from #31 since I had overlooked that there was already a release action. This would make it more obvious that this run failed: https://github.com/dsoftwareinc/fakeredis-py/actions/runs/2449338320

Fixed some references to the old action and this should be good to go now.


Connection closed by remote host (multiple_simulaitons_single_analysis.py)

I get the following error when I run the script multiple_simulations_single_analysis.py, which is very reminiscent of #151
(ve_entk)[mingtha@workflow examples]$ python multiple_simulations_single_analysis.py xsede.comet

================================================================================
 EnsembleMD (0.4.3-8-g7aac053)
================================================================================

Starting Allocation                                                           ok
Verifying pattern                                                             ok
Starting pattern execution                                                    ok
--------------------------------------------------------------------------------
Executing simulation-analysis loop with 4 iterations on 1 allocated core(s) on 'xsede.comet'

Job waiting on queue...
Job is now running !
Iteration 1: Waiting for 16 simulation tasks: misc.mkfile to complete2016-07-13 15:38:52,011: radical.entk.simulation_analysis_loop.static.default: MainProcess                     : Thread-3       : ERROR   : ComputeUnit error: STDERR: ssh_exchange_identification: Connection closed by remote host
, STDOUT: ssh_exchange_identification: Connection closed by remote host

2016-07-13 15:38:52,011: radical.entk.simulation_analysis_loop.static.default: MainProcess                     : Thread-3       : ERROR   : Pattern execution FAILED.
2016-07-13 15:38:52,011: radical.pilot       : MainProcess                     : Thread-3       : ERROR   : unit manager controller thread caught system exit -- forcing application shutdown
Traceback (most recent call last):
  File "/home/mingtha/ve_entk/lib/python2.7/site-packages/radical/pilot/controller/unit_manager_controller.py", line 262, in run
    self.call_unit_state_callbacks(unit_id, new_state)
  File "/home/mingtha/ve_entk/lib/python2.7/site-packages/radical/pilot/controller/unit_manager_controller.py", line 199, in call_unit_state_callbacks
    cb(self._shared_data[unit_id]['facade_object'], new_state)
  File "/home/mingtha/ve_entk/lib/python2.7/site-packages/radical/ensemblemd/exec_plugins/simulation_analysis_loop/static.py", line 318, in unit_state_cb
    sys.exit(1)
SystemExit: 1
Execution interuptedTraceback (most recent call last):
  File "/home/mingtha/ve_entk/lib/python2.7/site-packages/radical/ensemblemd/exec_plugins/simulation_analysis_loop/static.py", line 512, in execute_pattern
    resource._umgr.wait_units(uids)
  File "/home/mingtha/ve_entk/lib/python2.7/site-packages/radical/pilot/unit_manager.py", line 698, in wait_units
    time.sleep (0.5)
KeyboardInterrupt

Starting Deallocation..
Resource allocation cancelled.

Ran this again with update to RP tutorial-xsede16 branch with the RP MongoDB (whose link I will not post ;P)


Save image to storage when app destroyed.

I'm trying to save the image to the storage by using a work manager. I'm doing this by destroying the application.
Logcat :-

My Code(getting error/exception on red marked line)

Thanks for reporting this.
I'm closing this issue because this forum is for issues with the codelab.
Thanks for reporting this.
I'm closing this issue because this forum is for issues with the codelab.
Stackoverflow might be a better forum for this kind of questions. Anyway, from the exception it seems that you app is missing a permission. But the image cut out part of the text.
If you think that this is a problem of the WorkManager library, please open a bug on the WorkManager public issue tracker: https://issuetracker.google.com/issues/new?component=409906&template=1094197
Please reopen if you still think this is an issue with the codelab.


Unable to unlist my packages due to an error "Sorry, an error occurred while processing your request."

Dear Team,
I have created some Nuget Packages and these packages is no longer required, hence wanted to unlist/delete my package. But, in doing so, I get an error that "Sorry, an error occurred while processing your request.
Error: Oh no, we broke something!"
Hence, please help me deleting the package. For reference, I have attached the screenshot of the error.
Thanks and regards,
Nishant Kumar

Is this consistent? Roughly what time did you try this operation and which time-zone? Btw which packages do you wish to unlist?

Hi,
Yes. This error is consistent. Following are the details:

Package name : People.API
Time of the attempt to delete the package :  11-Jul-2017(tried several times, but time is not remembered) and 12-07-2017 at 11:27am (India Time)

I wish to unlist two of my packages, namely People.API and People.API.Homologation.
Regards,
Nishant Kumar

Thanks @nick301 for the additional information. We will take a look at the possible causes/issues here and get back. Do give us a day's time. Hope this the unlisting of the packages is not so urgent?

Thanks @anangaur . Really appreciate the help. If the unlisting of the package can be done by tomorrow, then it will be best.

@nick301 Thanks for the patience. The "People.API" package has been unlisted as requested.

Hi @anangaur. Thanks for unlisting the People.API.
Requesting you to do the same for other package named People.API.Homologation also, which I mentioned in my earlier comments.
Thanks in advance.

Done.


BUG: code generated by cython uses features not supported by xlc/xlC

I am trying to build pandas. It's first step is to cythonize the source code.
The build process ends with:
"pandas/_libs/window/aggregations.cpp", line 5436.23: 1540-0063 (S) The text "(" is unexpected.
"pandas/_libs/window/aggregations.cpp", line 5523.23: 1540-0063 (S) The text "(" is unexpected.
"pandas/_libs/window/aggregations.cpp", line 6759.21: 1540-0063 (S) The text "(" is unexpected.
"pandas/_libs/window/aggregations.cpp", line 20023.21: 1540-0063 (S) The text "(" is unexpected.

On examining this I see that there are special statements - perhaps unsupported by xlc/xlC (v11).
 +5436      __pyx_t_1 = (std::signbit(__pyx_v_val) != 0);

 +5523      __pyx_t_1 = (std::signbit(__pyx_v_val) != 0);

 +6759    __pyx_t_1 = (std::isnan(__pyx_v_val) != 0);

+20023    __pyx_t_1 = (std::isnan(__pyx_v_val) != 0);

Just one more complete except - to give a bit more context:

+20016    /* "pandas/_libs/window/aggregations.pyx":1634
+20017   *         float64_t temp, q, r
+20018   *
+20019   *     if isnan(val):             # <<<<<<<<<<<<<<
+20020   *         return
+20021   *
+20022   */
+20023    __pyx_t_1 = (std::isnan(__pyx_v_val) != 0);
+20024    if (__pyx_t_1) {
+20025
+20026      /* "pandas/_libs/window/aggregations.pyx":1635
+20027   *
+20028   *     if isnan(val):
+20029   *         return             # <<<<<<<<<<<<<<
+20030   *
+20031   *     nobs[0] = nobs[0] + 1
+20032   */
+20033      goto __pyx_L0;
+20034
+20035      /* "pandas/_libs/window/aggregations.pyx":1634
+20036   *         float64_t temp, q, r
+20037   *
+20038   *     if isnan(val):             # <<<<<<<<<<<<<<
+20039   *         return
+20040   *
+20041   */
+20042    }

Is this something I can resolve manually?
How can I test-drive the Python to C conversion?
Thanks!

These are coming being generated because Pandas is using these functions from the C++11 standard library:
https://github.com/pandas-dev/pandas/blob/7e25af85fa6fc91bc606d130a4f81b1af8fd4d91/pandas/_libs/window/aggregations.pyx#L15-L19
Cython is doing exactly what it's being asked to here. You either need to turn on C++11 support on your compiler, or persuade the maintainers of Pandas not to use it.

Or get Pandas to add a compiler specific work-around here https://github.com/pandas-dev/pandas/blob/1546c35dc839b3f6c094ad41d14cda24e9e13a0c/pandas/_libs/src/headers/cmath

Thanks. I also posted on pandas. However, as I mentioned above - xlc/xlC (v11) does not seem to support C++11. (And I see you added a comment while was typing - I'll look at it!  -- THX!!)


ISPN-15466 Passivation does not need to remove from store on load or …

…write
https://issues.redhat.com/browse/ISPN-15466

We may have it already, but should we add a test with a restart to ensure the store's values are updated?

We may have it already, but should we add a test with a restart to ensure the store's values are updated?

There should be some already, but I updated the PassivatePersistentTest to have it explicitly now.

Also checking the StringStoreWithPooledConnectionFunctionalTest failure

Looking good. I think we'll need some update on the docs.

Yeah, I was in the process of adding the doc changes. I actually cleaned up the passivation section in general as parts of it were outdated sadly.

Rebased to latest


WIP Add protected extracting to AbstractAssert

The PR is not ready yet, tests and javadoc need some reworking.
@kriegfrj @bjhargrave would this help your needs?
@joel-costigliola I added the isPublic() matcher to METHODS_CHANGING_THE_OBJECT_UNDER_TEST in SoftProxies to allow a protected extracting without changing the method name. At the moment I don't see any side effect but please let me know your opinion about it.
Check List:

Fixes #1731
Unit tests : NOT YET
Javadoc with a code example (on API only) : NOT YET

Thanks for the feedback @bjhargrave! I should be able to continue on this topic in the next days.

In general InstanceOfAssertFactory<T,ASSERT> should be InstanceOfAssertFactory<? super T,ASSERT> to provide maximum flexibility.

I agree with you that it would make sense to increase flexibility, I only want to see the impact of it adding proper tests. If the changes get too big, I may do them in a separate PR.

I built this PR locally and tried using the new extracting(Function,AssertFactory) method in my custom assert class. It looks good to me. The code compiled fine and passed the tests which verified the assertion state was propagated.
Thanks!
@@ -210,8 +198,7 @@ public abstract class AbstractPromiseAssert<SELF extends AbstractPromiseAssert<S
         *             resolved successfully.
         */
        public AbstractThrowableAssert<?, ? extends Throwable> hasFailedWithThrowableThat() {
-               return hasFailed().asObjectAssert()
-                       .extracting(this::getFailure, InstanceOfAssertFactories.THROWABLE);
+               return hasFailed().extracting(this::getFailure, InstanceOfAssertFactories.THROWABLE);
        }

        void assertNotFailed() {
@@ -271,8 +258,7 @@ public abstract class AbstractPromiseAssert<SELF extends AbstractPromiseAssert<S
         *             resolved with a failure.
         */
        public AbstractObjectAssert<?, RESULT> hasValueThat() {
-               return isSuccessful().asObjectAssert()
-                       .extracting(this::getValue);
+               return isSuccessful().extracting(this::getValue, Assertions::assertThat);
        }

        /**
@@ -294,7 +280,7 @@ public abstract class AbstractPromiseAssert<SELF extends AbstractPromiseAssert<S
         */
        public <ASSERT extends AbstractAssert<?, ?>> ASSERT hasValueThat(
                InstanceOfAssertFactory<? super RESULT, ASSERT> assertFactory) {
-               return hasValueThat().asInstanceOf(assertFactory);
+               return isSuccessful().extracting(this::getValue, assertFactory);
        }

@bjhargrave thanks for the feedback, glad it worked! To make it mergeable I need to rework the tests a bit more but I don't expect further changes in AbstractAssert.

Thanks so much for all your work on this!


Storage: storage.get triggers an error: java.lang.NoSuchMethodError: com.google.api.services.storage.model.StorageObject.getCustomTime()

Environment details

OS type and version: MacOSX
Java version: 11
storage version(s): 2.1.0

Code example
private Blob doCopy(String filename) {
  BlobId srcId = BlobId.fromGsUtilUri(filename);
  Blob src = this.storage.get(srcId); // <--- This line triggers the error
  CopyWriter w = src.copyTo(this.destBucket, this.destObject);
  return w.getResult();
}

Stack trace
Caused by: java.lang.NoSuchMethodError: com.google.api.services.storage.model.StorageObject.getCustomTime()Lcom/google/api/client/util/DateTime;
    at com.google.cloud.storage.BlobInfo.fromPb (BlobInfo.java:1212)
    at com.google.cloud.storage.Blob.fromPb (Blob.java:972)
    at com.google.cloud.storage.StorageImpl.get (StorageImpl.java:330)
    at com.google.cloud.storage.StorageImpl.get (StorageImpl.java:338)
    at com.myorg.myapp.MatchKeywordsDoFn.doCopy (MatchKeywordsDoFn.java:65)
    at com.myorg.myapp.MatchKeywordsDoFn.processElement (MatchKeywordsDoFn.java:52)

External references such as API reference guides

https://googleapis.dev/java/google-cloud-storage/latest/com/google/cloud/storage/Blob.html#copyTo-java.lang.String-com.google.cloud.storage.Blob.BlobSourceOption...-

Any additional information below
I'm not sure this makes a difference but I'm running this as part of an Apache Beam pipeline.

To add another example, I also tried copy using the CopyRequest class per the example here with the same result just from the getResult() function.
Source
private Blob doCopy(String filename) {
    BlobId srcId = BlobId.fromGsUtilUri(filename);
    Storage.CopyRequest req = Storage.CopyRequest.newBuilder().setSource(srcId)
      .setTarget(BlobId.of(this.destBucket, this.destObject))
      .build();
    return this.storage.copy(req).getResult(); // <--- This line triggers the error
}

Error
Caused by: java.lang.NoSuchMethodError: com.google.api.services.storage.model.StorageObject.getCustomTime()Lcom/google/api/client/util/DateTime;
    at com.google.cloud.storage.BlobInfo.fromPb (BlobInfo.java:1212)
    at com.google.cloud.storage.Blob.fromPb (Blob.java:972)
    at com.google.cloud.storage.CopyWriter.getResult (CopyWriter.java:77)
    at com.myorg.myapp.MatchKeywordsDoFn.doCopy (MatchKeywordsDoFn.java:68)
    at com.myorg.myapp.MatchKeywordsDoFn.processElement (MatchKeywordsDoFn.java:52)

Hi @onetwopunch this sounds like there is a "bad" version of com.google.apis:google-api-services-storage that is being picked up at runtime.
com.google.cloud:google-cloud-storage:2.1.0 is built against com.google.apis:google-api-services-storage:v1-rev20210127-1.32.1.
Can you verify which version you're using?
If you're using maven you can find out by running the following command:
mvn dependency:tree -Dincludes=com.google.apis:google-api-services-storage

Ahh interesting, that would make sense
[INFO] --- maven-dependency-plugin:3.1.1:tree (default-cli) @ myapp ---
[INFO] com.myorg.myapp:jar:1.0-SNAPSHOT
[INFO] \- org.apache.beam:beam-sdks-java-extensions-google-cloud-platform-core:jar:2.21.0:compile
[INFO]    \- com.google.apis:google-api-services-storage:jar:v1-rev20191011-1.30.3:compile

I'm fairly new to Maven and Java in general, how would I bump the version of api-services in my pom.xml or otherwise?

Welp, it turns out that since google-api-services-storage is brought in by Beam, I just needed to update Beam from 2.21.0 to 2.29.0 and now things work as expected. Java dependency management is weird.

haha, thanks for reporting back @onetwopunch. I was actually working on writing up the options of how you might be able to proceed (one of which would be to update beam).
Glad you were able to get unblocked, and that updating beam was possible for you.


Potential issue with beardlib?

As of the most recent workshop update and Beardlib update, I have been receiving a crash related to:
lib/setups/gamesetup.lua:298
core/lib/setups/coresetup.lua:295
lib/setups/gamesetup.lua:298 comes out to managers.navigation = NavigationManager:new()
Beardlib calls for NavigationManager in line 11 of mod.txt
{ "hook_id" : "lib/managers/navigationmanager", "script_path" : "BeardLibCore.lua"},

Could you give more details on the crash? And the line numbers that are displayed in the crash log are not accurate so the line it says does not directly translate to what you'll see in a decompile. Additionally BeardLib hooking to that lua file is irrelevant because it isn't actually used, it is an old one that wasn't removed from when we moved the BeardLib Editor outside of the main BeardLib verison.

Hi GBBB!
Sorry for not responding :)
This happens between any day I switch. if I host all clients crash. If I'm client I'll crash between every day.
Full crashlog http://pastebin.com/iN4ECZ4g

That crash specifically appears to be directly related to package loading, which in that particular area is not touched by BeardLib. I would suggest verifying your game as that crash suggests that you have corrupt assets.

Thanks I'll look into this


ValueError: NULL COM pointer access

Hi,
I got this NULL com pointer access error message, it is really strange because it happens so randomly. Button i'm trying to press is visible and should have access to it, but still my script fails, any ideas? Anyone else noticed this kind of behavior?
Traceback (most recent call last):
  File "C:\temp\Test.py", line 803, in press_button
    if button.exists(timeout=5):
  File "build\bdist.win-amd64\egg\pywinauto\application.py", line 397, in exists
    self.__resolve_control(exists_criteria, timeout, retry_interval)
  File "build\bdist.win-amd64\egg\pywinauto\application.py", line 244, in __resolve_control
    criteria)
  File "build\bdist.win-amd64\egg\pywinauto\timings.py", line 402, in wait_until_passes
    func_val = func(*args)
  File "build\bdist.win-amd64\egg\pywinauto\application.py", line 208, in __get_ctrl
    ctrl = self.backend.generic_wrapper_class(findwindows.find_element(**ctrl_criteria))
  File "build\bdist.win-amd64\egg\pywinauto\findwindows.py", line 84, in find_element
    elements = find_elements(**kwargs)
  File "build\bdist.win-amd64\egg\pywinauto\findwindows.py", line 214, in find_elements
    depth=depth)
  File "build\bdist.win-amd64\egg\pywinauto\uia_element_info.py", line 277, in descendants
    elements = self._get_elements(IUIA().tree_scope["descendants"], cond, cache_enable)
  File "build\bdist.win-amd64\egg\pywinauto\uia_element_info.py", line 256, in _get_elements
    return elements_from_uia_array(ptrs_array, cache_enable)
  File "build\bdist.win-amd64\egg\pywinauto\uia_element_info.py", line 47, in elements_from_uia_array
    return [UIAElementInfo(ptrs.GetElement(n), cache_enable) for n in range(ptrs.Length)]

Probably we could just ignore wile building the array of elements

Should be fixed in master branch now. Could you please also check on your side? I'm planning to publish 0.6.3 tomorrow. Not sure you will have time to re-check it since it's sporadic. Just want to know if it's ValueError or COMError? I assume it's COMError.

@vasily-v-ryabov i ran my tests few times and i did not get any errors, it seems that your fix fixed the problem, thanks


Readme updates for supervisor

https://github.com/chaosbot/chaos/blob/master/startup.d/90-chaos.sh is really a problem child right now, and I think it was written because people didn't notice the process was already managed under supervisor

👍

Oh, thanks! Author of startup.d here. I just wanted a good way to startup other web servers and stuff, but people have been just rolling their own thing for the most part.


you are a legend!

may we have the whole story sir?
it seems you gotten a hold of the original OG domain, fxtwitter . com. can you please tell us a bit more?

For those who are out of the loop the TL;DR is that TwitFix shut down last May due to understandable privacy issues by some people and corresponding death threats from transphobes. So the domain was taken down and remained dormant for months. This situaton is how vxTwitter came to be. So a combination of me being frustrated at the limitations of TwitFix and its forks and the events that led to vxTwitter's creation led me to want to build something better from the ground up. After all, something like TwitFix was like a perfect use case scenario for Cloudflare Workers which I had just started to get used to when I began the project.
I know Robin who ran TwitFix. I asked for the domain. She said no, because she was worried about the whole situation that had happened before. And that was understandable, and I respected that. So I kinda put the idea on the shelf for just a little bit, but a few weeks later I actually decided to make my own. So I got a new domain name for it (pxtwitter.com) and I did exactly what I wanted to do—Write a fast, serverless, privacy-focused version of TwitFix with feature parity to TwitFix and derivatives like vxTwitter. I launched it in just over 24 hours from when I started, and it already had many features that TwitFix and derivatives don't have, like polls and media-based embed colors. Other things like multi-image and direct media linking I added in shortly after.

My work didn't go unnoticed on Twitter by Robin however, and she had been a bit impressed by some of the things I came up with like poll support, etc. which I always thought was super dope since she was the one that made TwitFix and was the one who inspired me to makek this project in the first place. And I had talked back and forth with her about the project and stuff. I didn't ask for the domain or anything again cause I valued our relationship more than a domain name. But out of the blue, Robin DMed me simply with "All right, you've convinced me" and asked for my email--so it turns out I was getting the domain after all.
As soon as I got the domain I made an announcement on my Discord server 'cause I was hyped as hell.

Robin actually joined my Discord server at this time. Before I switched on the domain I had some chats with some other members of my Discord server including Robin as to how we handle the name pivot—because the name pxTwitter just didn't really fit if our new domain was fxtwitter.com—So I wanted a new name for the project that was more related to the fxtwitter.com domain, but still unique from TwitFix—and FixTweet was something I came up with pretty fast that resonated with me well. And so there it was! With a new name having been pushed out to the worker I was ready to turn on fxtwitter.com for the first time in months—now powered by FixTweet's grounds-up embedder.
Even I was surprised how quickly stuff started to spring back to life when the fxtwitter.com domain was turned back on.

Getting the fxtwitter.com domain has catapulted FixTweet into a position it otherwise would have probably never gotten, and I hope more and more people continue to use the new fxtwitter.com and put pressure on vxTwitter to actually add more features to its service instead of taking away.
Now, FixTweet has a free Tweet fetch API we built from scratch, using the same data we use for the FixTweet embedder but given in an easy-to-parse JSON format, and I hope I can add more functionality to our API in the future to help people make useful things without having to deal with Twitter's cumbersome API.
Recently, I have deprecated pxtwitter.com in favor of fxtwitter.com to encourage the few people still using the old domain to migrate. But I'll keep old links working for the foreseeable future.
I'd obviously love to thank Robin for the work she did in building the original TwitFix and for giving me the fxtwitter.com domain for free. And everyone that used the OG pxtwitter before we got the fxtwitter.com domain—These people are the OGs to me. And of course a thank you to everyone using fxtwitter.com today—let everyone using other embedders know that fxtwitter.com is back!

Google REALLY needs to link to this or something more recent and relevant when I search up 'Is fxtwitter safe'. I don't wanna keep losing internet arguments on the internet over things like this.


Omada v5.0.29

Hi,
I did integration, but I forgot to finalize pull request.
Let me know if this request is right.
Thanks
Stefano

I will test these changes against my existing v4.4.8 controller and if all goes well I'll merge it in. Thanks!

i think this also fixes #11


Handle granular requests configuration

Motivation
First iteration for: #834, I will follow up with client implementation after this one get validation.
Allow user to configure inlayHints and codeLens requests, and disabling unwanted features.
Implementation
Handle in the server a hash of feature configuration:

we set a default configuration so we could merge this without client implementation
merge client configurations with default ones
early return in requests in case of disabled features

Question: should I disable features by default as proposed here? To my very personal opinion, this can bring confusion with supported features documentation.
Automated Tests
Tests added:

in executor to ensure default and provided configurations are well populated
in both request to ensure there are no responses in case of disabled feature

Manual Tests
By switching default configuration to false in lib/ruby_lsp/store.rb, then restarting, no feature should be display to user.
Screenshots
inlayHints with true / false default configuration:

codelens with true / false default configuration:

This is amazing. Thank you for the contribution, Justin!

Question: should I disable features by default as proposed https://github.com/Shopify/ruby-lsp/issues/834#issuecomment-1830853866? To my very personal opinion, this can bring confusion with supported features documentation.

You raise a really good point. We discussed this with the team and I think we can do the following:

Let's default all inlay hints to disabled
Let's keep code lens as enabled by default
Let's update both the documentation for code lens and inlay hints to mention these configurations
Finally, let's add an enableAll entry to both configuration hashes. That way, someone interested in having the hints can simply turn everything on instead of needing to add every single one

In terms of code style, it might be worth creating an object in utils.rb to encapsulate the configuration logic. Something along these lines
class RequestConfig
  def initialize(hash)
    @hash = hash
  end

  def enabled?(feature)
    @hash[:enableAll] || @hash[feature]
  end
end

🚀


Update RNReactNativeHapticFeedbackPackage.java

Fixed Map Import

It seems that your PR overlaps with my previous submission. https://github.com/mkuczera/react-native-haptic-feedback/pull/111#issue-1856807120

Hey @mkuczera could this be merged?

Merged with #111


Set default target for certain crates, also features

For certain crates I'd like it if I could set the default target, so that when someone looks up a certain crate, they'd get the documentation I want them to get by default. Particularly useful for crates that only define things for certain targets, such as winapi.
Also useful would be a way to tell docs.rs which features to enable when building a crate. winapi 0.3 will have almost everything disabled by default, and then opting in with features, but that would end up with docs.rs generating useless documentation.

Same idea, but different problem: https://docs.rs/crate/clang-sys fails to find libclang (obviously). There is a feature to do a runtime link instead of a compile time link, so it should fix the problem.

I will add building crates with extra features but where is best place to define docs.rs specific options?
Maybe a docs.rs section in Cargo.toml?

IIRC, we made a meta section of Cargo.toml for this kind of thing

Oh, it's metadata http://doc.crates.io/manifest.html#the-metadata-table-optional

A use-case I have: cocoa-rs is a crate managed by Servo. Servo currently does not build documentation on the OSX builders (https://doc.servo.org is Linux IIRC). It'd be nice if I could link to the documentation for cocoa-rs for the latest published version that was built on OSX. That said, I juts checked it looks like cocoa-rs isn't building on docs.rs, which makes my whole comment moot anyways.

Doc features are great. What I do in ndarray is to build with the "docs" feature that depends on the optional crate features. Then I've made sure each of the items enabled by that mentions this in the docs (“Requires crate feature "serde"”). Adding this to docs.rs would make it have "feature parity" and I'll switch.

This is partially fixed, looks like a commit closed this.
Docs.rs now supports building non-default features but it is not redirecting to default-target.

Would be really cool to have the default-target redirect working. It's incredibly frustrating when people look for the documentation for winapi only to find empty documentation.

#255 fixed this

Crates that set a default-target in their [package.metadata.docs.rs] will now run their "test build" for that target, and their default docs set will be run on that target. In addition, crates with a default-target already set have had their latest version rebuilt; for example https://docs.rs/winapi/ now contains the proper docs for x86_64-pc-windows-msvc without having to redirect to that target's page. (Note that the builds still all run on a Linux system, so if your crate is target-specific because of a system library, that will still need to be available on Debian for the docs to build!)


[BUG] When pressing play for second time, bounding box of animated fbx is computed wrong

Describe the bug
When
To Reproduce
Steps to reproduce the behaviour:

Load a prefab prepared with the animation bones (Zombunny) and put it far from the origin.
Enable show global bounding box from Debug.
Click on Play Button.
Click on Play Button again.
The bounding box will be computed wrongly :(

Expected behaviour
When scene is load by play button, bounding boxes remain as they were.
Screenshots
https://gyazo.com/115c1568a31d15be32b0426a85aa240c
Additional context
Add any other context about the problem here.

Do you need animations ASAP? The current state in develop is pretty much a POC. I'm working on animations on my branch and probably I will fix that there

Nope, for this vs1 is not needed but then the model of the main character can't have bones or it will happen this bug.

Solved in #103


Connected Peers Flapping @ ETC

Steps to Reproduce (Bug)

Use Version v22.1.0 in Docker
Use Ethereum Classic Chain
Full Sync

Expected behavior:
No "flapping" peers and try to connect to all found peers as peer limit is higher than found peers to connect to.
Actual behavior:
At least 2 to 4 times a day. Even more often if you check the logs and not the data collected via the node exporter and represented in Grafana.
besu_1           | 2022-02-20 11:08:31.337+00:00 | main | INFO  | DefaultSynchronizer | Starting synchronizer.
besu_1           | 2022-02-20 11:08:31.361+00:00 | main | INFO  | FullSyncDownloader | Starting full sync.
besu_1           | 2022-02-20 11:08:31.364+00:00 | main | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 0
besu_1           | 2022-02-20 11:08:31.435+00:00 | main | INFO  | Runner | Ethereum main loop is up.
besu_1           | 2022-02-20 11:08:32.402+00:00 | nioEventLoopGroup-3-1 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 1
besu_1           | 2022-02-20 11:08:37.406+00:00 | EthScheduler-Timer-0 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 17
besu_1           | 2022-02-20 11:08:38.554+00:00 | nioEventLoopGroup-3-8 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 66
besu_1           | 2022-02-20 11:08:40.069+00:00 | nioEventLoopGroup-3-2 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 75
besu_1           | 2022-02-20 11:08:40.602+00:00 | nioEventLoopGroup-3-10 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 67
besu_1           | 2022-02-20 11:08:40.703+00:00 | nioEventLoopGroup-3-7 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 68
besu_1           | 2022-02-20 11:08:41.153+00:00 | nioEventLoopGroup-3-6 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 70
besu_1           | 2022-02-20 11:08:41.315+00:00 | nioEventLoopGroup-3-6 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 52
besu_1           | 2022-02-20 11:08:41.956+00:00 | nioEventLoopGroup-3-10 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 37
besu_1           | 2022-02-20 11:08:43.120+00:00 | nioEventLoopGroup-3-3 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 36
besu_1           | 2022-02-20 11:08:43.242+00:00 | nioEventLoopGroup-3-3 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 35
besu_1           | 2022-02-20 11:08:43.678+00:00 | nioEventLoopGroup-3-2 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 35
besu_1           | 2022-02-20 11:08:44.962+00:00 | nioEventLoopGroup-3-3 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 36
besu_1           | 2022-02-20 11:08:45.811+00:00 | nioEventLoopGroup-3-10 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 27
besu_1           | 2022-02-20 11:08:47.679+00:00 | nioEventLoopGroup-3-6 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 23
besu_1           | 2022-02-20 11:08:48.714+00:00 | nioEventLoopGroup-3-10 | INFO  | BlockPropagationManager | Saving announced block 14575841 (0x92d816b994fd5ba1835c1b4849047dba8922d426c47291d4452f4f73e2ce0bf8) for future import
besu_1           | 2022-02-20 11:08:49.375+00:00 | nioEventLoopGroup-3-3 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 44
besu_1           | 2022-02-20 11:08:50.143+00:00 | nioEventLoopGroup-3-2 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 27
besu_1           | 2022-02-20 11:08:55.144+00:00 | EthScheduler-Timer-0 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 14
besu_1           | 2022-02-20 11:09:00.148+00:00 | EthScheduler-Timer-0 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 11
besu_1           | 2022-02-20 11:09:00.655+00:00 | nioEventLoopGroup-3-6 | INFO  | BlockPropagationManager | Saving announced block 14575842 (0x96b355aed97a10b8bcc0b43f58ade59266fb64f8811d26b8d72d64cafa4a1b06) for future import
besu_1           | 2022-02-20 11:09:01.550+00:00 | nioEventLoopGroup-3-7 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 13
besu_1           | 2022-02-20 11:09:03.885+00:00 | nioEventLoopGroup-3-10 | INFO  | BlockPropagationManager | Saving announced block 14575843 (0x640278c5cc759ed1e483e3d55e26324dcb627e1a0378d8050678154d5fc3cd33) for future import
besu_1           | 2022-02-20 11:09:06.259+00:00 | nioEventLoopGroup-3-6 | INFO  | BlockPropagationManager | Saving announced block 14575844 (0x24311a8ece2c54500b906750d77892ed62905169f1359559f08628f75ebaa3f0) for future import
besu_1           | 2022-02-20 11:09:06.551+00:00 | EthScheduler-Timer-0 | INFO  | FullSyncTargetManager | No sync target, waiting for peers. Current peers: 10
besu_1           | 2022-02-20 11:09:10.103+00:00 | nioEventLoopGroup-3-8 | INFO  | SyncTargetManager | Found common ancestor with peer Peer 0xc25688b33f3e3eb997... at block 14575839
besu_1           | 2022-02-20 11:09:10.117+00:00 | nioEventLoopGroup-3-10 | INFO  | BlockPropagationManager | Saving announced block 14575845 (0xabfbaafe2a8b0877e1d831180d40a49c1c614555aa92f0f89a2db1fd5018355d) for future import
besu_1           | 2022-02-20 11:09:16.097+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,841 / 0 tx / 0 om / 0 (0.0%) gas / (0x92d816b994fd5ba1835c1b4849047dba8922d426c47291d4452f4f73e2ce0bf8) in 0.027s. Peers: 10
besu_1           | 2022-02-20 11:09:16.101+00:00 | EthScheduler-Workers-2 | INFO  | BlockPropagationManager | Imported 1 pending blocks
besu_1           | 2022-02-20 11:09:16.342+00:00 | EthScheduler-Workers-0 | INFO  | PersistBlockTask | Imported #14,575,842 / 22 tx / 0 om / 501,074 (6.3%) gas / (0x96b355aed97a10b8bcc0b43f58ade59266fb64f8811d26b8d72d64cafa4a1b06) in 0.240s. Peers: 10
besu_1           | 2022-02-20 11:09:16.344+00:00 | EthScheduler-Workers-0 | INFO  | BlockPropagationManager | Imported 1 pending blocks
besu_1           | 2022-02-20 11:09:16.352+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,843 / 0 tx / 0 om / 0 (0.0%) gas / (0x640278c5cc759ed1e483e3d55e26324dcb627e1a0378d8050678154d5fc3cd33) in 0.016s. Peers: 10
besu_1           | 2022-02-20 11:09:16.355+00:00 | EthScheduler-Workers-3 | INFO  | BlockPropagationManager | Imported 1 pending blocks
besu_1           | 2022-02-20 11:09:16.372+00:00 | EthScheduler-Workers-1 | INFO  | PersistBlockTask | Imported #14,575,844 / 1 tx / 0 om / 22,312 (0.3%) gas / (0x24311a8ece2c54500b906750d77892ed62905169f1359559f08628f75ebaa3f0) in 0.020s. Peers: 10
besu_1           | 2022-02-20 11:09:16.375+00:00 | EthScheduler-Workers-1 | INFO  | BlockPropagationManager | Imported 1 pending blocks
besu_1           | 2022-02-20 11:09:16.383+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,845 / 0 tx / 0 om / 0 (0.0%) gas / (0xabfbaafe2a8b0877e1d831180d40a49c1c614555aa92f0f89a2db1fd5018355d) in 0.014s. Peers: 10
besu_1           | 2022-02-20 11:09:16.384+00:00 | EthScheduler-Workers-2 | INFO  | BlockPropagationManager | Imported 1 pending blocks
besu_1           | 2022-02-20 11:09:18.525+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,846 / 0 tx / 0 om / 0 (0.0%) gas / (0x3de1fe9969e4c3b2c971299b6265d7bdee8f80b5b40f92e15c63a148ec617b3b) in 0.008s. Peers: 10
besu_1           | 2022-02-20 11:09:35.519+00:00 | EthScheduler-Workers-1 | INFO  | PersistBlockTask | Imported #14,575,847 / 4 tx / 0 om / 86,624 (1.1%) gas / (0x8adc4f85476cbb3cd6c2fe16552968664e8077f75356254a7c79dad8b7635372) in 0.030s. Peers: 10
--> besu_1           | 2022-02-20 11:09:47.799+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,848 / 0 tx / 0 om / 0 (0.0%) gas / (0x8180634af7fea803bdbb3b27c7b5615dc2409f6d2e4d42ce9507547c3e9149d3) in 0.010s. Peers: 190
besu_1           | 2022-02-20 11:09:48.074+00:00 | nioEventLoopGroup-3-10 | INFO  | SyncTargetManager | Found common ancestor with peer Peer 0x3edfc67f36effaa7cd... at block 14575847
besu_1           | 2022-02-20 11:09:52.841+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,849 / 0 tx / 0 om / 0 (0.0%) gas / (0x7e7ce09f1107f1d8072fa917320640733496fdcdc4d81c1c2baa03dd8bab41eb) in 0.021s. Peers: 16
besu_1           | 2022-02-20 11:10:12.009+00:00 | EthScheduler-Workers-0 | INFO  | PersistBlockTask | Imported #14,575,850 / 20 tx / 0 om / 423,936 (5.3%) gas / (0x233ee6492bb5f702490d5b93d4e80c1f9919438c749549cc62b52af2d248c724) in 0.053s. Peers: 15
besu_1           | 2022-02-20 11:10:13.443+00:00 | EthScheduler-Workers-1 | INFO  | PersistBlockTask | Imported #14,575,851 / 0 tx / 0 om / 0 (0.0%) gas / (0x7a11fadddf88cab7fab42efc0629086b135137a124d8160d22e2d3a238e5113e) in 0.005s. Peers: 15
besu_1           | 2022-02-20 11:10:36.953+00:00 | EthScheduler-Workers-1 | INFO  | PersistBlockTask | Imported #14,575,852 / 0 tx / 0 om / 0 (0.0%) gas / (0xa5f66608d737c314efc1025b5df76111136e5a191fa6d994726d70ade03cdc8a) in 0.007s. Peers: 14
besu_1           | 2022-02-20 11:10:38.082+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,853 / 0 tx / 0 om / 0 (0.0%) gas / (0x6111a7b5511be55ef0497bd208946f1f042d62700c41165fedafcd641c578c6d) in 0.013s. Peers: 25
besu_1           | 2022-02-20 11:10:49.053+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,854 / 0 tx / 0 om / 0 (0.0%) gas / (0x89b544c0175edc038ea2845069883dd6416066b6e484de9187b83b220358d87a) in 0.004s. Peers: 18
besu_1           | 2022-02-20 11:10:49.335+00:00 | EthScheduler-Workers-0 | INFO  | PersistBlockTask | Imported #14,575,855 / 6 tx / 0 om / 126,000 (1.6%) gas / (0x5bfab5a37324618528b99892a3d0f5bf77553f90d407de9e58f68a43cedc836f) in 0.033s. Peers: 17
besu_1           | 2022-02-20 11:11:02.455+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,856 / 0 tx / 0 om / 0 (0.0%) gas / (0x27ac7df30a49f96ec55856996de13fecc00d221303c185ae8c2ca71c70d63db4) in 0.006s. Peers: 15
besu_1           | 2022-02-20 11:11:21.732+00:00 | EthScheduler-Workers-1 | INFO  | PersistBlockTask | Imported #14,575,857 / 8 tx / 0 om / 168,000 (2.1%) gas / (0x453f723e893b1ae2df6f909d3e7be60fbeb9b0e26ea64fe87299054b0ba6480f) in 0.029s. Peers: 14
besu_1           | 2022-02-20 11:11:33.865+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,858 / 20 tx / 0 om / 420,000 (5.3%) gas / (0xc81239b3f559d04d34bb8e8a6142beedcce4b93a7aefcfc8f7ffee112832dab7) in 0.049s. Peers: 14
besu_1           | 2022-02-20 11:11:49.213+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,859 / 30 tx / 0 om / 630,000 (7.9%) gas / (0xa2b0e6ae9ca06dfe410b952d1a1f5874a7a6d34f2f8b5914b99ebb668199b7f0) in 0.062s. Peers: 16
besu_1           | 2022-02-20 11:11:53.069+00:00 | EthScheduler-Workers-0 | INFO  | PersistBlockTask | Imported #14,575,860 / 6 tx / 0 om / 126,000 (1.6%) gas / (0xf0cefe4ed2b540707fa826048ecdd6f08cb9d7874a84331a6934d2abbf5938ac) in 0.016s. Peers: 15
besu_1           | 2022-02-20 11:12:07.450+00:00 | EthScheduler-Workers-0 | INFO  | PersistBlockTask | Imported #14,575,861 / 0 tx / 0 om / 0 (0.0%) gas / (0x1fda2aac8e36fd575682f77996055a9986139b3a2578de04c9fa346ed1ba1336) in 0.004s. Peers: 16
besu_1           | 2022-02-20 11:12:15.865+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,862 / 49 tx / 0 om / 1,035,560 (12.9%) gas / (0x950f89703d11d910479a7d724dcd2cdfcf5dec278d9d314bbd65fd3f031703d8) in 0.097s. Peers: 14
besu_1           | 2022-02-20 11:12:52.152+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,863 / 2 tx / 0 om / 42,000 (0.5%) gas / (0x04bec13d6ca2998b954f62f66f3c7a93c45be7b39c4ddd844a2688c3b171f8d2) in 0.013s. Peers: 19
besu_1           | 2022-02-20 11:13:11.455+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,864 / 0 tx / 0 om / 0 (0.0%) gas / (0x635c233e7516c03b87b9fb30cc76818725893068e836694ffe11b40fd49afc34) in 0.005s. Peers: 16
besu_1           | 2022-02-20 11:13:11.767+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,864 / 11 tx / 0 om / 234,936 (2.9%) gas / (0x2e094d7389ffb654d3f6bcab829e603cbfd25d322e14ae4496812a0be9239aa1) in 0.052s. Peers: 15
besu_1           | 2022-02-20 11:13:32.696+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,865 / 0 tx / 1 om / 0 (0.0%) gas / (0xb32fc3883c9c2f18f755501fc72f4ecea9ea2a02b90a3a43d04f571ba6d2b2a2) in 0.015s. Peers: 14
--> besu_1           | 2022-02-20 11:13:42.314+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,866 / 24 tx / 0 om / 514,336 (6.4%) gas / (0x79dde1d20f095ba1ffac298898da9819eab1c2bde773a4052a4ca1110892f51e) in 0.236s. Peers: 397
besu_1           | 2022-02-20 11:13:50.455+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,867 / 1 tx / 0 om / 21,000 (0.3%) gas / (0x06a94a3c20e455aa75ffe259d1754145634d665e615890d1baf94e311755dd5e) in 0.009s. Peers: 15
besu_1           | 2022-02-20 11:14:05.689+00:00 | EthScheduler-Workers-1 | INFO  | PersistBlockTask | Imported #14,575,868 / 4 tx / 0 om / 467,399 (5.8%) gas / (0xab4cd210f24e9482ce1e6f9facce37d914f64540108852b6880e184fc318ec4e) in 0.135s. Peers: 15
besu_1           | 2022-02-20 11:14:10.828+00:00 | EthScheduler-Workers-0 | INFO  | PersistBlockTask | Imported #14,575,869 / 0 tx / 0 om / 0 (0.0%) gas / (0x3b9d7e2a1cd79f9e66ad913c5568a89613e8aeab7394582f868b21929c4a259c) in 0.005s. Peers: 15
besu_1           | 2022-02-20 11:14:13.305+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,870 / 0 tx / 0 om / 0 (0.0%) gas / (0xb8d409d2859cc74d2d101825e08a8e0d03e717c81d50808fe0e1538dc8108fa0) in 0.006s. Peers: 14
besu_1           | 2022-02-20 11:14:48.000+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,871 / 0 tx / 0 om / 0 (0.0%) gas / (0x367c432a9ab36d8815075b6a99f2476d29abab28ae4ecefe40f7c3f6b4a7cbc5) in 0.005s. Peers: 23
besu_1           | 2022-02-20 11:14:51.330+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,872 / 39 tx / 0 om / 1,131,126 (14.1%) gas / (0x7db4825089705f87dd49bb0e477ee0fef6bd6093569517d6920789feb0086acd) in 0.186s. Peers: 19
besu_1           | 2022-02-20 11:15:18.820+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,873 / 0 tx / 0 om / 0 (0.0%) gas / (0x15d475d75c301ec44ac5263b179f681c783a2066b6216c93b52fd23ed51bdc73) in 0.003s. Peers: 14
besu_1           | 2022-02-20 11:15:22.717+00:00 | EthScheduler-Workers-0 | INFO  | PersistBlockTask | Imported #14,575,874 / 0 tx / 0 om / 0 (0.0%) gas / (0xca8d6d717bdc50df2e8b18d7e5f2340e7f34afaa1170a6b89f1469e0563d7495) in 0.004s. Peers: 14
besu_1           | 2022-02-20 11:15:25.286+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,875 / 6 tx / 0 om / 131,248 (1.6%) gas / (0x5447b8ca1c277610e407e42dabfdeb2d4fe23130b442f506112fc0972032dff3) in 0.019s. Peers: 14
besu_1           | 2022-02-20 11:15:34.099+00:00 | EthScheduler-Workers-1 | INFO  | PersistBlockTask | Imported #14,575,876 / 0 tx / 0 om / 0 (0.0%) gas / (0xf766fd41d610bfa967f1d177c8ce8686104881c4ed1b02fc25579447fb2bab5e) in 0.004s. Peers: 14
besu_1           | 2022-02-20 11:16:03.859+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,877 / 9 tx / 0 om / 190,312 (2.4%) gas / (0x42f4d66c4d1885492e455472560ef39e5089cc9c6eef19ccf8300880698c98e6) in 0.030s. Peers: 18
besu_1           | 2022-02-20 11:16:09.731+00:00 | EthScheduler-Workers-1 | INFO  | PersistBlockTask | Imported #14,575,878 / 0 tx / 0 om / 0 (0.0%) gas / (0x0e18d3de1e17283c5d4fea29b596304ade836cbc4b66471fa9083547cbbb2650) in 0.006s. Peers: 16
besu_1           | 2022-02-20 11:16:21.978+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,879 / 0 tx / 0 om / 0 (0.0%) gas / (0xef1c35353a99f1425480cb70a2f0c04768eda91e5ad8e3b31a2f72698ad23767) in 0.004s. Peers: 15
besu_1           | 2022-02-20 11:16:26.064+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,880 / 1 tx / 0 om / 21,000 (0.3%) gas / (0xc7c8192027539b7d36550430ab44139228e404ba59ad501357cf8ef2957c3870) in 0.011s. Peers: 15
besu_1           | 2022-02-20 11:16:26.193+00:00 | nioEventLoopGroup-3-9 | INFO  | SyncTargetManager | Found common ancestor with peer Peer 0x9a28fae65fc6932951... at block 14575879
besu_1           | 2022-02-20 11:16:30.762+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,881 / 17 tx / 0 om / 358,312 (4.5%) gas / (0x0e6cc0525704707acc54c3fda0ae12a00650febdc159d0b503136c337d9158a4) in 0.044s. Peers: 15
besu_1           | 2022-02-20 11:16:32.684+00:00 | EthScheduler-Workers-1 | INFO  | PersistBlockTask | Imported #14,575,882 / 0 tx / 0 om / 0 (0.0%) gas / (0x36d7d9dc7f03ece82fa3431ad277ec1beffa315daefb3a3ac274ad3b0fec9f2d) in 0.003s. Peers: 16
besu_1           | 2022-02-20 11:16:43.263+00:00 | EthScheduler-Workers-0 | INFO  | PersistBlockTask | Imported #14,575,883 / 24 tx / 0 om / 504,000 (6.3%) gas / (0x35f174d4138e112691df5d762257265d8d4357fa6c0f1a71b2f0a3d7a15afacd) in 0.085s. Peers: 22
besu_1           | 2022-02-20 11:16:53.654+00:00 | EthScheduler-Workers-1 | INFO  | PersistBlockTask | Imported #14,575,884 / 2 tx / 0 om / 42,000 (0.5%) gas / (0x89d4232e5b31b408f45c3a0d5cf2a8738cb7387a1b724dc458c2a14e3168d2fe) in 0.012s. Peers: 20
besu_1           | 2022-02-20 11:17:03.102+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,885 / 0 tx / 0 om / 0 (0.0%) gas / (0x82f7a35c7f348c3f3ed0effaf0fe302fb30f93deea13c2414123741a7ad99cc3) in 0.003s. Peers: 14
besu_1           | 2022-02-20 11:17:09.698+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,886 / 0 tx / 0 om / 0 (0.0%) gas / (0x706bbc20b84505675accf27acee9a36b6dd28f307666b580fd2c9f5281edd588) in 0.002s. Peers: 14
besu_1           | 2022-02-20 11:17:17.376+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,887 / 15 tx / 0 om / 318,936 (4.0%) gas / (0x146e2545d5cd5f532905e478e0eecee0a27438e6b5bf767ea2bc15fc108d749b) in 0.032s. Peers: 13
besu_1           | 2022-02-20 11:17:22.773+00:00 | EthScheduler-Workers-1 | INFO  | PersistBlockTask | Imported #14,575,888 / 0 tx / 0 om / 0 (0.0%) gas / (0xdbfd5022bcc9026f1cadf8337d0ab2cafa7c2df08752f13c7fc0ee6edf8daf0c) in 0.004s. Peers: 14
besu_1           | 2022-02-20 11:17:29.755+00:00 | EthScheduler-Workers-1 | INFO  | PersistBlockTask | Imported #14,575,889 / 0 tx / 0 om / 0 (0.0%) gas / (0xf07ae46afce533b78749d0020f9405625ff817c3a531dc7fa1be7381d2c807b8) in 0.004s. Peers: 13
besu_1           | 2022-02-20 11:17:30.854+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,890 / 0 tx / 0 om / 0 (0.0%) gas / (0x13bba3c0856effb96b6ec0bea22ded0f5b629a6953142d63b52b785166cfbd3d) in 0.003s. Peers: 13
besu_1           | 2022-02-20 11:17:43.141+00:00 | nioEventLoopGroup-3-4 | INFO  | BlockPropagationManager | Saving announced block 14575892 (0x4b319a92d8867a0f916949aafbccae625756808f39bbe8e257589a8bfdc1ae00) for future import
--> besu_1           | 2022-02-20 11:17:43.357+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,891 / 28 tx / 0 om / 591,969 (7.4%) gas / (0x84a8b6e516e4f431aaf922960852a9b0ccf21c42f95518d0424ce732a253f11c) in 0.197s. Peers: 361
--> besu_1           | 2022-02-20 11:17:43.405+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,892 / 1 tx / 0 om / 21,000 (0.3%) gas / (0x4b319a92d8867a0f916949aafbccae625756808f39bbe8e257589a8bfdc1ae00) in 0.047s. Peers: 355
besu_1           | 2022-02-20 11:17:43.406+00:00 | EthScheduler-Workers-3 | INFO  | BlockPropagationManager | Imported 1 pending blocks
besu_1           | 2022-02-20 11:17:48.364+00:00 | EthScheduler-Workers-0 | INFO  | PersistBlockTask | Imported #14,575,893 / 0 tx / 0 om / 0 (0.0%) gas / (0xe593352c0e8b25fb978b331fb675e0d70105690f58b6d4570af2bc834bd71ec8) in 0.003s. Peers: 15
besu_1           | 2022-02-20 11:18:04.239+00:00 | EthScheduler-Workers-3 | INFO  | PersistBlockTask | Imported #14,575,894 / 5 tx / 0 om / 106,312 (1.3%) gas / (0x6c65a16bf5614ab251d789cae007a2d1f26319dbb692747fc9006430204f4ddf) in 0.022s. Peers: 14
besu_1           | 2022-02-20 11:18:33.882+00:00 | EthScheduler-Workers-2 | INFO  | PersistBlockTask | Imported #14,575,895 / 9 tx / 0 om / 192,936 (2.4%) gas / (0xdf9c611e3b06ed77017982858ca6016629fe2a887c2406a51bce7d3ca64112bf) in 0.023s. Peers: 13

Versions (Add all that apply)

Docker Version: Tag:v22.1.0

dashboard: https://dashboard.etc-network.info/d/5S-6O8VZk/hyperledger-besu-node-at-ethereum-classic?orgId=1&var-Source=Nürnberg%2FGermany (NUE)&from=now-24h&to=now&refresh=5s

Spikes in the connected peers happens some times 1 - 2 times a day (increasing from 25ish to 50ish). And occasional spike increasing to 300 peers

This could be potentially resolved by #2689