On Linux OmniSharp is started with Mono even if told not to

I am trying to open a dotnet core msbuild project with VS Code on Linux and everything works, except that the extension marks as not found all the assemblies that come with the netcoreapp1.0 framework and as "wrong version" the ones that have a compatible name in the Mono .NET 4.5 framework.
I guess this happens because the extension starts OmniSharp with Mono even if dotnet is correctly installed and the configuration option omnisharp.useMono is set to false.
Here is OmniSharp starting:
Starting OmniSharp server at 02/12/2016, 10:55:44
    Target: /home/fog/Workspaces/wok/scratch/test1

OmniSharp server started wth Mono
    Path: /home/fog/.vscode-insiders/extensions/ms-vscode.csharp-1.5.3/bin/run
    PID: 18513

OmniSharp: -s /home/fog/Workspaces/wok/scratch/test1 --hostPID 16021 --stdio DotNet:enablePackageRestore=false --encoding utf-8
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Startup","Message":"Omnisharp server running using Stdio at location '/home/fog/Workspaces/wok/scratch/test1' on host 16021."},"Seq":1,"Type":"event"}
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Initializing in /home/fog/Workspaces/wok/scratch/test1
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Auto package restore: False
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Update workspace context
[INFORMATION:OmniSharp.DotNet.DotNetProjectSystem] Resolving projects references
[INFORMATION:OmniSharp#MSBuild] No solution files found in '/home/fog/Workspaces/wok/scratch/test1'
[INFORMATION:OmniSharp#ProjectFileInfo] Using TargetFrameworkRootPath: /usr/lib/mono/xbuild-frameworks
[INFORMATION:OmniSharp#ProjectFileInfo] Using tools version: 15.0
[INFORMATION:OmniSharp#MSBuild] Add project: /home/fog/Workspaces/wok/scratch/test1/test1.csproj
[INFORMATION:OmniSharp#MSBuild] Update project: test1
[INFORMATION:OmniSharp.Startup] Configuration finished.

Environment data
dotnet --info output:
.NET Command Line Tools (1.0.0-preview3-004056)
Product Information:
Version:            1.0.0-preview3-004056
Commit SHA-1 hash:  ccc4968bc3
Runtime Environment:
OS Name:     debian
OS Version:
OS Platform: Linux
RID:         debian.8-x64
VS Code version:
Code Insiders 1.8.0-1480662019
C# Extension version:
1.5.3
Steps to reproduce

create  a new web project with dotnet new -t web
restore packages with dotnet restore
open it using VS Code

Expected  behavior
All framework assemblies are correctly resolved, no warnings about missing assemblies or versions.
Actual behavior
Errors like:
file: 'file:///home/fog/Workspaces/wok/scratch/test1/server/src/Program.cs'
severity: 'Warning'
message: 'Assuming assembly reference 'System.Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' used by 'Microsoft.AspNetCore.Hosting.Abstractions' matches identity 'System.Runtime, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' of 'System.Runtime', you may need to supply runtime policy [test1]'
at: '14,24'
source: ''

That's actually by design. The "omnisharp.useMono" setting only functions when you've also used the "omnisharp.path" setting to use a custom OmniSharp.
The warning that you're getting has nothing to do with the fact that OmniSharp is running on Mono. The runtime on which OmniSharp runs and the location of the reference assemblies it uses are orthogonal (i.e. it doesn't pick reference assemblies from Mono for .NET Core projects).
I suspect you're seeing the CS1701 warning from C# the compiler which all tools generally suppress (including Visual Studio). This was original reported in #967. We've recently fixed this problem for 1.6. Please try the latest beta version to see if that addresses the problem for you. See this page for information on installing beta releases

The line that made me think it was a Mono-related problem was:
[INFORMATION:OmniSharp#ProjectFileInfo] Using TargetFrameworkRootPath: /usr/lib/mono/xbuild-frameworks

in the OmniSharp log. Anyway, I'll try the beta and let you know.
Thanks.

I confirm the beta solves the problem. Thanks again.

Excellent! Very glad to hear it!
Yes, the TargetFrameworkRootPath is set to Mono to ensure that desktop targets and tasks for MSBuild get picked up when you open such a project. However, .NET Core targets and tasks are pulled in through NuGet.


Sort by year (instead of "cited by") for search by author ID

By default it semes an author's page displays the publications that have been cited the most times first; if you click the year link, you're then able to get the author's most recent publications. The URL changes slightly: https://scholar.google.com/citations?hl=en&user=EmD_lTEAAAAJ&view_op=list_works&sortby=pubdate
Is there any way this could be built in the new scholarly.search_author_id (#148) function? Some sort of 'sortby' parameter would be really handy (especially for my use case).

Why not just filter your self?
search_query = scholarly.search_author("{author's name}")
author_info = next(search_query).fill()
for pub in author_info.publications:
    if int(pub.bib['cites']) > 100:
        print(pub.bib['title'])

Also reference https://stackoverflow.com/questions/45781760/sorting-multiple-dictionary-dimensions-at-once to sort the results that come at you.

Sorry maybe I wasn't clear -- I'm not looking to filter. I'm looking to get the author's most recent publications instead of their most popular (which is what is currently yielded).
Number of citations don't matter in this case.

If you don't mind playing a little with the code yourself.
in author.py
line 11 > add _CITATIONAUTH_FILTER = '/citations?hl=en&user={0}&view_op=list_works&sortby=pubdate'
line 16, after "none" enter ,my_filter="none"
line 97 you need to change this so that if you submit a "yes" for my_filter it will use the new line we added in line 11.
line 189 (prior to your changes) change to match your changes you did on line 97 and on.
when you submit your changes you will likely need to submit it like search_author(author_name,"none","yes") as you need to ensure none is left by default in the code if I am reading it correctly)
I think those changes would allow you to apply the google filter to search by publication date.
Sorry I don't really have more time to test / play with it more than this.

@michaelfromyeg a quick dirty way to do that would be going into line 10 of author.py and add &sortby=pubdate on your local scholarly.
To implement your functionality you would have to add an optional parameter to the constructor of the Author (and consequently the search functions) class and format the url accordingly.
If you would like to suggest a PR on the developer branch we could probably merge it.

Sounds good! I'll give it a go this weekend. Thanks for the quick fix as well, appreciate it.

Version v.1.0.6 adds this functionality:
author = scholarly.search_author_id(id = 'PA9La6oAAAAJ', filled = True, sortby = "year", publication_limit = 5)
scholarly.pprint(author)


Refactor Link to add more cheap unit tests

[FX-NNNN]
Description
This if a follow up of https://github.com/toptal/picasso/commit/f8e5c8f82c54e011270a7bec58375d09153788ce and #4547. Where I did not test code due to inability to add cheap test.
Extract all view logic into separate pure function. This allows adding many tests that run in few ms, raising confidence in our code without making tests suits running forever.
How to test
Locally yarn test:unit:watch
Development checks

[ ] Add changeset according to guidelines (if needed)
[ ] Double check if picasso-tailwind-merge requires major update (check its README.md)
[ ] Read CONTRIBUTING.md and Component API principles
[ ] Make sure that additions and changes on the design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
[ ] Annotate all props in component with documentation
[ ] Create examples for component
[ ] Ensure that deployed demo has expected results and good examples
[ ] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[ ] Self reviewed
[ ] Covered with tests (visual tests included)

Breaking change

[ ] codemod is created and showcased in the changeset
[ ] test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@OleksandrNechai don't you want to merge it?


Support for 3.5+?

Hello, does this plugin work in 3.5+?

Hey @shanegriffiths - it should work fine! I tried to test and install it via Sketch Toolbox and with manual download. Both versions worked fine on my computer (Sketch @ 3.5.2). It needs to run a little procedure once, to extend the existing artboard presets. Did you try that? Take a look at the Plugin Menu -> Social Artboards -> Install Social Artboards. Afterwards you should find "Social" presets whenever adding a new Artboard. If you discover any other problems, could you please reopen this issue and add some steps to reproduce? Thank's for getting in touch!


Support for defining query

The idea is to support customizing the SQL that is executed for materializing an entity at the model level, e.g.:
modelBuilder.Entity<Product>()
    .FromSql("SELECT Id, UPPER(Name) AS Name FROM Products");

One possible advantage over having the FromSql() in the query is that theorethically we could make it work with Include(), e.g. this query could join the defining query for Product to the OrderLines table:
var q = context.OrderLines.Where(l => l.OrderId == orderId).Include(l => l.Product);

Another idea:
var q = context.OrderLines
    .Where(l => l.OrderId == orderId)
    .IncludeFromSql(l => l.Product, "SELECT Id, UPPER(Name) AS Name FROM Products" );

Of course this and options above come with the caveat: how do we prevent selecting back the entire table if the SQL literal doesn't include the join? Perhaps something to the effect of:

@anpete oh duh. Of course we've solved this already.

Updated the original issue to cover scenarios that could use LINQ rather then SQL.

Bring this back to triage to discuss that the current implementation of query types is missing some of the functionality we wanted to have and discussed in https://github.com/aspnet/EntityFrameworkCore/issues/9290, even for query types:

SQL-based defining queries: With the current API, the only way to provide SQL as part of a defining query is to call FromSql inside the call to ToQuery. For example:

modelBuilder
    .Query<OrderSummary>()
    .ToQuery(() => Query<OrderSummary>()
        .FromSql(
            @"SELECT o.Amount, p.Name AS ProductName, c.Name AS CustomerName
            FROM Orders o
            INNER JOIN Product p ON o.ProductId = p.Id
            INNER JOIN Customer c ON o.CustomerId = c.Id"));

However, it is not possible to use the right type of DbQuery (i.e. with the same query type one is trying to map to as the generic argument) because that causes a StackOverflowException at runtime.

"Null" defining queries: The goal of this idea was to enable the designer of the model to disable the usage of a query type without providing SQL with FromSql in the rest of the application. This not super high priority: If one does nothing, and there is no view or table in the database with the name inferred by default, you will get a runtime error from the database, but the original idea whas to have a better exception.

Also, in practice if one writes this:
modelBuilder.Query<OrderSummary>().ToQuery(() => null);

It kind of achieves the original goal, but the exception is simply a NullReferenceException :smile:

Fix for https://github.com/aspnet/EntityFrameworkCore/issues/11803 actually regressed this in 2.2. It was working correctly in 2.1 RTM

@smitpatel file an issue for the bug and fix in 2.2.
@divega to clean up this issue.

@smitpatel file an issue for the bug and fix in 2.2.
@divega to clean up this issue.

Filed #13346

Filed #13358 for defining query feature on entity types. Closing this as fixed in 2.1 for query types.


Not showing ads today

Hi,
I've been using this plugin for a long time now (around 5 months) and everything was working fine :-)
But today on my application no ads are show and I don't see any printing.
Do you know if it's coming for the plugin or maybe today AdMob have some issue ?
Thank you in advance,
Vertilol

It's fix, i guess it was just a problem from Google.
Bye :-)


Get serde parse error when call block_results

What went wrong?
I just write simple code for get latest block result from osmosis json-rpc.
Because the version of osmosis tendermint is v0.34, I tried compat mode V0_34 too. It isnt changed.
When I call the client.perform method, the response always serde parse error
Steps to reproduce
Here's core I wrote
use tendermint_rpc::{endpoint::block_results, Client, HttpClient};

#[tokio::main]
async fn main() {
    let client = HttpClient::new("https://rpc.osmosis.zone:443").unwrap();
    let result = client.perform(block_results::Request::default()).await;

    println!("{:?}", result);
}

I also attach v0.34 code
use tendermint_rpc::{endpoint::block_results, Client, HttpClient, HttpClientUrl};

#[tokio::main]
async fn main() {
    let url = HttpClientUrl::try_from("https://rpc.osmosis.zone:443").unwrap();
    let client = HttpClient::builder(url)
        .compat_mode(tendermint_rpc::client::CompatMode::V0_34)
        .build()
        .unwrap();

    let result = client.perform(block_results::Request::default()).await;

    println!("{:?}", result);
}

Here's the Cargo.toml
[package]
name = "cosmrs-test"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
cosmrs = { version = "0.14.0", features = ["cosmwasm", "rpc", "tokio", "grpc"] }
tokio = { version = "1.29.1", features = ["full"] }
tendermint-rpc = { version = "0.32.0", features = ["http", "tokio"] }

When try to execute program, I got
Err(serde parse error

Caused by:
    invalid type: null, expected a string at line 1 column 196492

Location:
    /Users/eric/.cargo/registry/src/github.com-1ecc6299db9ec823/flex-error-0.4.4/src/tracer_impl/eyre.rs:10:9)

Definition of "done"
Able to get block_results from osmosis json-rpc.

EventAttribute's value attribute is currently not nullable.  It's cause this error IMO

tendermint-rpc = { version = "0.32.0", features = ["http", "tokio"] }

The feature list must have been ["http-client"], otherwise the code does not compile.
I can confirm the error even with the 0.34 compatibility mode. Will investigate.
Unfortunately, this is not expected to work correctly with a 0.34 node, as the protocol has changed and we lack the means to auto-detect it reliably:
use tendermint_rpc::{endpoint::block_results, Client, HttpClient};

#[tokio::main]
async fn main() {
    let client = HttpClient::new("https://rpc.osmosis.zone:443").unwrap();
    let result = client.perform(block_results::Request::default()).await;

    println!("{:?}", result);
}

The cause, in this example, is that the example uses the perform method directly which bypasses the backward compatibility logic. If you use the block_results method, the implementation switches to the perform_v0_34 intrinsic method and the response is parsed successfully.
I noticed, however, that the latest_block_results method does not properly implement this, so there is a bug that needs to be fixed.
It's confusing now that the perform method is exposed in the public API; when initially defined, it wasn't a problem, but with the compatibility mode support added on, this becomes an implementation detail.

This method doc on Client::perform perhaps does not carry enough warning against using the method in consumer code:
    /// This method is used by the default implementations of specific
    /// endpoint methods. The latest protocol dialect is assumed to be invoked.


general: security improvements

Basic security improvements taken from this blog post. This resolves issue #24.

Other than the question above, LGTM.


MsgTx.BtcDecode can't decode transaction returned from https://github.com/litecoin-project/litecoin v0.21.2

github.com/litecoin-project/litecoin start encode mweb tx into hex from version v0.21.2. Current MsgTx.BtcDecode can't recognize the new flag, 0x08. To make it work with the new C++ server, let's skip the mweb tx section for now.

Encoder in C++: https://github.com/litecoin-project/litecoin/blob/v0.21.2/src/primitives/transaction.h#L365-L367
PR for a quick fix: https://github.com/ltcsuite/ltcd/pull/15

Fixed with #15


Don't use deny(warnings) in code

https://github.com/alexcrichton/pkg-config-rs/blob/175dd5596fb8bf1ebf66c4df0c8d013e568c6d58/src/lib.rs#L65
This basically breaks for everyone when lints are changed because people do run tests ;)
I think more appropriate to pass -D warnings or something like that to CI.

This was removed a while ago
commit 5bb9d05f5eb7e43425a39a320a377c07cac5e2f2
Author: Alex Crichton<EMAIL_ADDRESS>Date:   Tue Apr 24 08:19:55 2018 -0700
Remove deny(warnings)


Add [CurseForge] badges

Adds the following badges:

URL
Example
Result

/curseforge/dt/:projectId
/curseforge/dt/238222

/curseforge/game-versions/:projectId
/curseforge/game-versions/238222

/curseforge/v/:projectId
/curseforge/v/238222

To generate the secret CURSEFORGE_API_KEY (yml: private.curseforge_api_key) please signup to the CurseForge Console with a Google account and create an organization, then go to the API keys page and copy the generated API key. I can provide the API key I used for my own testing if creating a new one is too much of an hassle.
Also added the following logos: (Removed, as the logos were already available in the Simple Icons library)

Logo
Location
Source

/logo/curseforge.svg
~~https://static-beta.curseforge.com/images/favicon.ico~~

/logo/modrinth.svg
~~https://modrinth.com/favicon.ico~~

Thank you for the PR, although functionally I feel like this duplicates #7499
Are there any material differences with this PR that you think should be considered over #7499, and/or do you think anything has changed or that we should be aware of wrt the signup process? The seeming complexities around that were largely what things have been blocked on for a while

Hey, thanks for the reply!
Regarding #7499, the only difference are two extra endpoints ("v/:projectId" and "game-versions/:projectId") and the tests, which are trivial to implement once the API token issue gets sorted out. I am okay with closing this PR in favour of #7499; the extra features can be introduced later. Should have checked if there was any previous work done beforehand, so my fault.

We have a Google account for Shields.io that we could reuse here. Alternatively I've got a Forge account I'm be happy to share for this matter. https://github.com/badges/shields/pull/7499 links to a form, happy to fill that out and submit it, it doesn't look nearly as annoying than the Youtube form I had to deal with yesterday (#8605). :)

@PyvesB, that form is actually outdated! The new way is much simpler and just requires signing up with a Google account an creating an organization; no manual review needed. Please see the description of this PR for instructions. :)
The only question is what is the request cap per token, as the documentation doesn't talk about rate limits.

@PyvesB, that form is actually outdated! The new way is much simpler and just requires signing up with a Google account an creating an organization; no manual review needed. Please see the description of this PR for instructions. :)

Thanks, it indeed is easy to get an API key. Though it's a bit unfortunate that you can only have one key per org, we'll potentially have to use someone's personal account for CI.

The only question is what is the request cap per token, as the documentation doesn't talk about rate limits.

Do you think you could drop the Curse Forge team a line to figure this out? Hitting various API rate limits has been a recurring problem for Shields.io, we wouldn't want to introduce a new badge if a few months down the line badges are breaking for users due to an unforeseen limit being hit. :)

Sent an email (as per this page) asking about the rate limits. Will give an update once I get a reply.

@PyvesB, they replied back asking for the expected traffic. Could I add you to the conversation, so that you could answer those hard-hitting questions that I don't have the answers to?

@PyvesB, they replied back asking for the expected traffic. Could I add you to the conversation, so that you could answer those hard-hitting questions that I don't have the answers to?

Short answer is yes to plugging the Shields team into the thread, but will also say that it's rather hard for us to provide anything other than an uninformed guestimate with something like this.
With a platform used as widely and heavily like GitHub, with as large a user base, we can generate a lot of traffic in the delivery of badges (we peak somewhere in the 4k-5k requests/minute with GitHub). We've got other badges where we only make a handful of API requests per day (e.g. less than 100).
It's ultimately a factor of the number of users of the platform, and the subset of those that want badges displaying data from/about that platform

For anyone following this PR: we are currently talking to the Curse Forge team. Please bear with us whilst we exchange information with them. :)

I am not sure what the lint CI step is complaining about. Both files are fine when I check them locally:
$ npx prettier --check "core/base-service/auth-helper.js"
Checking formatting...
All matched files use Prettier code style!

$ npx prettier --check "services/curseforge/curseforge-base.js"
Checking formatting...
All matched files use Prettier code style!

We recently updated to a new major version of Prettier (#9357). Could you make sure you're based off of a recent-enough master revision, and that you've installed the latest Prettier (npm ci)?

That fixed it. All checks are passing now!

In the meantime we've been setting up the tokens on our servers, so whilst we've been a bit slow on the review cycles since this was first opened, this should be fully operational as soon as we merge and kick off a deploy. Thanks for the patience! 👍🏻

All changes are done now! I have retested all three badges to make sure nothing broke in the few months since I opened this PR and everything is looking good.

I've deployed this PR to staging and production. The new badges are happily working, for example:

Thanks again for working with us on this @SandroHc!


Missing a word in the description

Under the section "Block bookings from outside your organization"
Missing a word in the description "organization who've signed and are authenticated can" should read "organization who've signed in and are authenticated can"

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

ID: ba164b8e-a574-0744-ce02-23bda994e505
Version Independent ID: 05018469-d6f8-0eb5-956c-730991912f8b
Content: Turn Microsoft Bookings on or off
Content Source: microsoft-365/bookings/turn-bookings-on-or-off.md
Service: bookings
GitHub Login: @kwekuako
Microsoft Alias: kwekua

@msbemba Thank you very much for the contribution and updating the documentation with PR. @jeff-bb Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Add support for NetBSD-curses

NetBSD uses curses: tparm with 9 parameters and UP already defined in termcap.h
(Tested with NetBSD 7.1 ... NetBSD 5.1 lacks some definitions in term.h and breaks ...)

Thanks for taking time to make pick work on other BSDs. Are you using
NetBSD as your daily driver? If that's the case consider making pick
available as a package on NetBSD. The work by the other package
maintainers have help us find bugs and other issues related to
portability and is of significant value to the project.

NetBSD uses curses: tparm with 9 parameters

Please try out #218 and see if it solves the problem.

... and UP already definied in termcap.h

I would prefer if we instead renamed/prefixed {UP,DOWN,RIGHT,LEFT} to
not cause any conflicts rather than using yet another ifdef. Renaming
ideas are much appreciated.

Sorry, NetBSD will never be my daily driver: too many things are broken there ... ;-)
What about CURSOR_{UP,DOWN,RIGHT,LEFT}?

UP and DOWN affects the selection while LEFT and RIGHT the
cursor.
How about LINE_UP and LINE_DOWNsimiliar to PAGE_{UP,DOWN}.

@DBOTW please try out #222.

Works, thanks @mptre! But seems that their setupterm is broken as it always reports 80x24 (stty -a shows the correct size of the terminal window). Tested via ssh and in xterm & rxvt; played with different types of TERM, used resize & reset: always 80x24 in pick. The winsz-branch fixes this ...

The above bug (setupterm) is fixed in "NetBSD-current" ... so closing this PR ...


logging information missing

The CIMI server is not logging all requests to the server.  For example, user creation requests (either success or failure) and 500 failures for creating callbacks do not appear in the log file.

The CIMI server is currently configured to use a log4j RollingFileAppender which defaults to a maximum log file size of 10 MB and 1 backup log.  With the current logging rate of requests, this means that we save only around 40 minutes of logging information on the server (main log file and the backup file).
This is rather inadequate for debugging issues with the server.  I would propose for the request/response logging that we change to do the following:

log requests at the DEBUG logging level
log responses with 2xx or 3xx return codes at the INFO logging level
log responses with 4xx return codes at the WARNING logging level
log responses with 5xx return codes at the ERROR logging level

Doing this and reducing the default logging level for the request/response logger to WARNING would significantly reduce the noise in the log file.

Mapping of req/resp to log levels looks good.
In the future, if we need service usage statistics we should either have a summariser in the server or log requests as well.  This would probably require logging to a central logging facility (like Logstash with ES behind; with a dedicated (rolling) index and with log entries 'grok'ed into docs - the latter would allow more flexible queries etc.).

A summary of the current statistics are available here: https://nuv.la/webui/metrics.  These were at one time pushed to graphite to keep a history.  In any case, we need a combination of a usable log file and some summary statistics.

In testing the logging configuration with Nuvla, changing the logging level by namespace doesn't seem to be working.  So I've changed the levels to make the normal "INFO" logging reasonable (IMO at least).

log requests at the TRACE logging level
log responses with 2xx or 3xx return codes at the DEBUG logging level
log responses with 4xx return codes at the WARNING logging level
log responses with 5xx return codes at the ERROR logging level

This means that with an INFO logging level, only 4xx and 5xx responses will be shown.


Re-work implementation to hook into existing code instead of re-implementing chat render logic

Fixes #1
Fixes #2
This allows other mods to modify chat rendering as well, without ChatAnimation completely overriding all rendering logic.
Add compatibility with Raised mod
Bump version to 1.0.3
Build in case anyone needs it:
https://github.com/TheMrEngMan/ChatAnimation/releases/tag/1.0.3

Thank you


rewrite sanitize.jl stuff in haskell

we don't even have to do the "modifying stuff from an outer scope" thing anymore bc that's happening in demutation
Which means we still need to do the following:

multiple ='s inside each other a = b = 2
+='s?
includes
if-else: merge following code block
check for disallowed types

closed with https://github.com/DiffMu/DiffPrivacyInference.jl/commit/f119b2e6ec6aee0f62c70d9e6ce6c34f5b393be5


build_python_framework uses python 3.8 which does not work with Big Sur

When following instructions from https://github.com/macadmins/nudge/blob/master/README.md - if you run build_python_framework - it does so using 3.8.
By packaging up the results of that and installing it on Big Sur, you get the following error in nudge logs:
[Nudge] Detected Big Sur running version 10.16. Nudge cannot be reliably enforced. To fix this, create a Python.framework file on a machine running Big Sur or higher.
Then if I install https://github.com/macadmins/python and do managed_python3 /Library/nudge/Resources/nudge this error does not occur.
So either the python build script should get a newer version, or documented should be updated to deprecate it and point to macadmins/python IMO.
Thanks!

I will be addressing this in a README change momentarily


⚠ Bofrost.fr has degraded performance

In d2d3d32, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1574 ms

Resolved: Bofrost.fr performance has improved in 28a40a7 after 6 minutes.


[PE-D][Tester E] Glossary missing volunteers and befriendee

The glossary do not define what is a volunteer and what is a befriendee.
It is best to define these contact types since befriendee may not be intuitive.

Labels: type.DocumentationBug severity.Low
original: yleeyilin/ped#25

severity.VeryLow : A flaw that is purely cosmetic and does not affect usage e.g., a typo/spacing/layout/color/font issues in the docs or the UI that doesn't affect usage. Only cosmetic problems should have this label.


Update README.md to add Community Samples

Purpose

...

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[X] Documentation content changes
[ ] Other... Please describe:

Thanks!


📁  Feed: Splitting Tests Into Separated Files

This PR aims to take the existing feed app tests and split them into separated files.
In future sight, many more tests will be added, so to remain organized it is best to split big files into small and logically separated files.

Deleted old tests.py file
Added a new tests directory inside the feed app root directory
Added different tests file which contain the previous tests
Changed tests function name's to be more meaningful

Close #66

@paOmer please take a look at previous comments

Hi @Yarboa, after you'll review I would squash and force push, as mentioned in the last Beyond session.


Import your SAP Build project into SAP Web IDE

I think more details should be provided on the destinations, for example that the "SAP Web IDE Plugin" destination is only required for the old SAP Web IDE (it's not required for Web IDE Full-Stack). And the UI5 destinations are only required when creating a smart app (are they really required for this tutorial?).
More details on the destinations can be found in Build's documentation:
https://sap.github.io/BUILD_User_Assistance/build/external/4be99e779fcb4ff9a8e5179b74bd72cc.html
Also I just tried this tutorial and when running the app I got an error (metadata not found), which makes sense since there's no service.. How did the preview work? I guess the "testFLPServiceMockServer.html" file should be selected?

Thank you for your feedback. Because of the amount of time that has elapsed, we are closing the issue.
If you still have questions, feel free to create a new issue.


DB Build issue with msbuild 17.5

DB build fails with msbuild 17.5.  Issue logged here
Might need to consider workarounds

Fix to specify version 17.4 no longer seems to be working.
     - name: Add msbuild to PATH
        uses<EMAIL_ADDRESS>        with:
          vs-version: '[17.4,17.5)'

Security Scan action still seems to be working.  It's running with an older version of msbuild:
Microsoft (R) Build Engine version 16.11.2+f32259642 for .NET Framework
This workflow uses:
runs-on: windows-2019
instead of
runs-on: windows-2019
This might not be a reliable fix but worth noting.

Included in 2.36.1 🎉


The dropbox link was broken?

Thank you for a great job.
I tried to download the dropbox link that you mentioned README.
I just want to see what the dataset (input masks, and their channel) looks like.
Can you share a few samples of the dataset?
Thank you.

fixed link


Add CAD files for all 3d printed parts

can be in a separate /CAD/ folder in hardware/3D_Printed_Parts/

Uploaded, closing now


killercoda problems

I recently went through the killercoda Keptn End-to-End Delivery tutorial. Great job creating this tutorial!
Here are a few problems I experienced during the tutorial:

The ~/setup_keptn.sh script used at the beginning of the tutorial did not properly set the environment variables GIT_NEW_REPO_NAME and GIT_REPO. I had to manually run the following to work around this issue:export GIT_NEW_REPO_NAME=keptndemo
export GIT_REPO=https://github.com/jwenz723/keptndemo.git

Various pods went into a non-running status (either CrashLoopBackOff or Error). This caused the quality gates to never pass since they could not retrieve the necessary metrics for the gate.

I was only able to retrieve the failure reason for 1 pod before my killercoda session expired.
kubectl describe pod -n monitoring prometheus-prometheus-node-exporter-2z4k6

Closing as stale. Please re-open if this is still an issue.


Add bottom bar to the home menu

Add bottom bar to the home menu with:

Callbacks for each button
Each button click is wired to the BLoC
A pop up menu

Added colors file
Added dimmensions file
Added text styles file
Added primary and accent color to app
#closes 24

Fixed comments


feat(theme prop description): Adds descriptive text to theme prop

Overview
Adds descriptive text to theme props where they appear on components in storybook.
"This prop is set automatically and indicates that it is a consumer of the Theme context. Do not pass anything to it."

Storybook: Adds descriptive text instructing users not to pass anything to theme props

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

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

📬Published Alpha Packages<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60b7f34a851ff24ca1add9f5--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://60b92fc14251952df2143f40--gamut-preview.netlify.appDeploy Logs


Feature request: highlight

Hello! 😊So GREAT it is! BUT it seems that it doesn't support the markdown grammar that using == to highlight the content.
HOPE you could add this feature.

Supported in v0.0.13


Updated CSV

Changed the following info:

operator name
keywords
provided by Red Hat
other minor changes

@spotlesstofu @cpmeadors please take a look


UPnP and .NET Sockets

I am making a simple chat application using .NET Sockets.
The host socket needs a specific TCP port (let's say 8501) to be forwarded in order to properly accept any incoming connections.
When I manually go to my router and open that port, the host socket works perfectly. Client sockets can connect to it and begin sending packets.
Now I want to automatically forward that port, so I found out about Open.NAT.
The sample code provided on GitHub works fine and the mappings are created without any exceptions or timeouts.
But the host socket fails to accept any incoming connections.
I've even tried to use a windows COM called NATUPnP 1.0 Type Library. I made it work, the mappings are created but, same results, the host socket won't accept any incoming connections.
Some information:

my router supports UPnP and it is enabled
my modem is configured as bridge and my router as router
I am using a port forward utility to check if the mappings are really created and with both libraries, they appear there!
the tests where made with different networks (host socket on my home machine and client sockets on my office machines)
soon as I manually forward the port on my router, the host socket works again just fine

Am I missing something? If you need code I can provide my full simple test projects.
Thanks in advance!

I could help you only if there is a problem with the library (it seems is not the case). Anyway, modify the ConsoleTest project to forward the port and share with me the network.log file in .\bin\debug
Also, use an online tool for verifying if the port is really open. It could sound redundant but just to be sure.

Hello, thanks for the quick answer.
Here is the network.log: https://gist.github.com/phcs93/b14caee405faf0b1684aec28f360b29d
I simply modified one line in ConsoleTest.NatTest.Main
From
var t = nat.DiscoverDeviceAsync(PortMapper.Pmp, cts);
To
var t = nat.DiscoverDeviceAsync(PortMapper.Upnp, cts);
Also, the online tools for checking port forwarding (canyouseeme.org for example) doesn't seem to be working. Even when I manually forward the ports and get my sockets working, those tools says that said ports are closed.

I cannot see anything wrong in the log file. It seems the mappings were created okay, with no errors and you were able to list them after creation. The router could be misbehaving or there is another problem but the library seems to be working as expected.
Do yo have more that a router?

Yes, I have a modem and a router. But the modem is simply configured as bridge.

Is your modem IP <IP_ADDRESS>? If yes then the library is forwarding the ports in your modem instead of doing it in your router.

Nope, my modem is configured as bridge and its IP is <IP_ADDRESS>
<IP_ADDRESS> points to my router

I know this is an old post but did you ever find a solution to this issue?
I'm trying to use Open.NAT along with websocket-sharp for networking in a Unity game and I'm running into the same issue.
The port is properly forwarded, I see the entry on my router just fine, but I cannot connect to the websocket server. If I manually forward the port, so other than the entry not being marked UPNP it looks identical, I can connect fine.
I imagine this is an issue with .net sockets/websockets and not with Open.NAT though

All what I see is Open.NAT behaving correctly. Something has to be broken before I can fix it and there is not evidence about that.


Feature/octomap conversion

Looks great, thanks a lot, @jeffdelmerico! I updated the code such that it also works under ROS Kinetic and Ubuntu 16.04. Could you please check if things still run fine for you?


Implement Upload Part - Copy

The response body of s3.uploadPartCopy should contain { CopyPartResult: { ETag, ... } }, however I'm just receiving { CopyPartResult: {} }.
See https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/S3.html#uploadPartCopy-property.

Upload Part - Copy isn't actually supported by S3rver, but I can at least have that stubbed with 501 error for the next patch release so that the behavior isn't as confusing.

It doesn't look too difficult to add though, I'll try to address this for v3.1 (PRs are welcome)!

Draft PR here, I'm continuing to work on this: https://github.com/jamhall/s3rver/pull/443

The support that was implemented by #443 has been merged into main and will be available in the first 4.x release.


Shard generator

Hi everyone! I was using Hugging Face datasets to process some very large datasets and found that it would be quite handy to have a feature that will allow to "split" these large datasets into chunks with equal size. Even better - be able to run through these chunks one by one in simple and convenient way. So I decided to add the method called shard_generator() to the main Dataset class. It works similar to shard method but it returns a generator of datasets with equal size (defined by shard_size attribute).
Example:
>>> from datasets import load_dataset
>>> ds = load_dataset("rotten_tomatoes", split="validation")
>>> ds
Dataset({
      features: ['text', 'label'],
      num_rows: 1066
})
>>> next(ds.shard_generator(300))
Dataset({
      features: ['text', 'label'],
      num_rows: 300
})

I hope it can be helpful to someone. Thanks!

Hi, thanks!

I was using Hugging Face datasets to process some very large datasets and found that it would be quite handy to have a feature that will allow to "split" these large datasets into chunks with equal size

map, the method we use for processing in datasets, already does that if batched=True. And you can control the batch size with batch_size.

Even better - be able to run through these chunks one by one in simple and convenient way

It's not hard to do this "manually" with the existing API:
batch_size = <BATCH_SIZE>
for i in range(len(dset) // batch_size)
    shard = dset[i * batch_size:(i+1) * batch_size] # a dict of lists
    shard = Dataset.from_dict(shard)

(should be of similar performance to your implementation)
Still, I think an API like that could be useful if implemented efficiently (see this discussion to understand what's the issue with select/__getitem__ on which your implementation relies on), which can be done with pa.Table.to_reader in PyArrow 8.0.0+, .
@lhoestq @albertvillanova wdyt? We could use such API to efficiently iterate over the batches in map before processing them.

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

This is more efficient since it doesn't bring the data in memory:
for i in range(len(dset) // batch_size)
    start = i * batch_size
    end = min((i+1) * batch_size, len(dset))
    shard = dset.select(range(start, end))

@marianna13 can you give more details on when it would be handy to have this shard generator ?

This is more efficient since it doesn't bring the data in memory:
for i in range(len(dset) // batch_size)
    start = i * batch_size
    end = min((i+1) * batch_size, len(dset))
    shard = dset.select(range(start, end))

@marianna13 can you give more details on when it would be handy to have this shard generator ?

Sure! I used such generator when I needed to process a very large dataset  (>1TB) in parallel, I've found out empirically that it's much more efficient to do that by processing only one part of the dataset with the shard generator. I tried to use a map with batching but it causesd oom errors, I tried to use the normal shard and here's what I came up with. So I thought it might be helpful to someone else!

I see thanks ! map should work just fine even at this scale, feel free to open an issue if you'd like to discuss your OOM issue.
Regarding shard_generator, since it is pretty straightforward to get shards I'm not sure we need that extra Dataset method

Hi again! We've just added _iter_batches(batch_size) to the Dataset API for fast iteration over batches/chunks, so I think we can close this PR. Compared to this implementation, _iter_batches leverages pa.Table.to_reader for chunking, which makes it significantly faster.


Energy Conduits Not Transferring Power

Issue Description:
When you close the singleplayer world the vibrant conduits sometimes not transfer power so you have to break and replace them
What happens:
Conduit doesn't transfer power
What you expected to happen:
Conduit transfers power
Steps to reproduce:
No clue how to reproduce as it is only the case on one of my save files

Affected Versions (Do not use "latest"):

EnderIO: 1.12.2-5.0.46
EnderCore: 1.12.2-1.1.7
Minecraft: 1.12
Forge: <IP_ADDRESS>38
SpongeForge? no
Optifine? yes
Single Player

Your most recent log file where the issue was present:
During the joining phase
https://pastebin.com/fGusWTba

https://github.com/Damien-Reave/Omnifactory/issues/138 is the issue filed on the pack I am playing on

Which block is it that needs to receive energy? it is likely that this block is not notifying it's neighbors after it updates it's capabilities.

"(other non-gregtech machines still get energy tho)"
Yeah, seems like people think we have special code to transfer energy for each and every mod.

the gregtech machine is the CEF which convert RF to EU not the conduits changing the power.  Also for me it happens to all the blocks on the conduit line, (Gregtech CEF, deep mob learning machines and ender io capacitor bank) but even then it is hard to find out which mod is causing it as I cant seem to reproduce it

Keep it closed as it is not an issue with the conduits except an issue with the te dynamo I am using


python311Packages.yfinance: 0.2.36 -> 0.2.37

Diff: https://github.com/ranaroussi/yfinance/compare/refs/tags/0.2.36...0.2.37
Changelog: https://github.com/ranaroussi/yfinance/blob/0.2.37/CHANGELOG.rst
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 294007 run on x86_64-linux 1

4 packages built:

python311Packages.yfinance
python311Packages.yfinance.dist
python312Packages.yfinance
python312Packages.yfinance.dist


Snowflake 8.4 support

Which version and edition of Flyway are you using?
10.7.1
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Yes
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Java API
Which database are you using? (Type & version)
Snowflake 8.4
Which operating system are you using?
Windows, Linux
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
Factory method 'flyway' threw exception with message: Unsupported Database: Snowflake 8.4
What did you expect to see?
Nothing
What did you see instead?
Error creating bean with name 'flyway' defined in class path resource
Downgrading to version 9.22.3 solves the problem, with the warning "Flyway upgrade recommended: Snowflake 8.4 is newer than this version of Flyway and support has not been tested. The latest supported version of Snowflake is 7.33."
Since Snowflake is often changing versions, and it is a managed platform. Does it make sense to remove the version limit, and instead provide warning like in 9.22.3?

The error you describe would indicate that the flyway-database-snowflake module has not been included in your project. Please see the pinned issue here

You are absolutely right. I'm sorry for wasting your time, and thank you very much for the help.


ipldResolver API as pullStreams

would be nice to do a ipldResolver.get and get back a pullStream that passes back all nodes touched
would also be nice (for analytics) to be able to spy on all nodes being resolved by any request, something like a ipldResolver.createSpyStream()
cc @diasdavid

here are the events i used to make the ipld-resolver-viz
https://github.com/ipld/js-ipld-resolver/commit/7a012d0b15d000406eed05a280a2cbc249be6fbd

Making get return pull-stream sounds like a good idea to me, it matches ipfs.get/ipfs.files.get and prepares the API for the IPLD selector in the future.
I want to keep the API as simple as possible and let any extra porcelain in users land so that we do not increase the size of the codebase (=== tests, maintenance and bundle sizes) until it is completely obvious that it is a really good nice to have.
Following https://github.com/ipfs/interface-ipfs-core/issues/126#issuecomment-326991583, I propose two API changes.
a) add an option to the .get options object to just return the final result (by default it should return all the touched objects)
b) expose two API calls, one that it is .get that returns an array with all the nodes touched and another one that it is .getPullStream that does the same but returns all the nodes touched in a pull-stream
As for the porcelain such as createSpyStream, you can in your codebase create a proxy for .get calls that keeps track of all objects traversed and returns on the SpyStream or you can monkey patch the IPFS node when to create it in your code.

@diasdavid  just to be clear on this, I'd be replacing the existing get method?  Trying to get a sense of what other projects I'd want to look at/ patch if this is the case.

With the Awesome Endeavour: Async Iterators we want to move away from pull streams. There's also an upcoming API review of all the IPLD stuff, so it doesn't make sense to spend more time on this for now.

Thanks for the heads up!
On Wed, Nov 14, 2018 at 5:30 AM Volker Mische<EMAIL_ADDRESS>wrote:

With the Awesome Endeavour: Async Iterators
https://github.com/ipfs/js-ipfs/issues/1670 we want to move away from
pull streams. There's also an upcoming API review of all the IPLD stuff, so
it doesn't make sense to spend more time on this for now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ipld/js-ipld/issues/101#issuecomment-438661991, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAKkg7bOF5oIsfDQy-QBOsX9MQA5uSGQks5uvBrmgaJpZM4P8tuV
.

We son't use pull-streams anymore, hence closing this issue.


Unable to connect using ssh to repo

Warning:  I will close the issue without the minimal init.vim and the reproduce ways.
Problems summary
Installing a plugin hosted in private git repo does not work and throws an auth error, same url worked perfectly using vundle
Expected
installation works properly and installs the plugin
Environment Information (Required!)

dein.vim version(SHA1):
not sure how to calculate the SHA1, it's lastest version available in 13/march of 2017

OS:
Osx 10.12.1

Vim/neovim version:
Nvim 0.1.7

Provide a minimal .vimrc with less than 50 lines (Required!)

 1. open nvim
 2. call dein#install()

## Screen shot (if possible)

## Upload the log messages by `:redir` and `:message` (if errored)
"~/.config/nvim/plugins/dein.vim" 37L, 1276C written
[dein] Update started: (2017/03/13 20:21:32)
[dein] /Users/user/.vim/bundles/repos/git.company.com/gitroot/devtools/vim-company
[dein] Maybe wrong username or repository.
[dein] Cloning into '/Users/user/.vim/bundles/repos/git.company.com/gitroot/devtools/vim-company'...
[dein] Permission denied (publickey).^M
[dein] fatal: Could not read from remote repository.
[dein] Please make sure you have the correct access rights
[dein] and the repository exists.
[dein] Error installing plugins:
[dein]   vim-company
[dein] Please read the error message log with the :message command.
[dein] Done: (2017/03/13 20:21:35)

Error message tell you that you don't have a permission to pull. Do you really sure that you can check out the repository? It seems your config problem.

As stated before I'm able to get the plugin using Vundle and the same url.

Fixed.


cli: add deprecation warning

close #194

If we just want to show the yellow message, we have to remove the following line: warnings.simplefilter('always')


allow custom editor to choose movement via onFinishedEditing

Want to support typical spreadsheet editing movements like

Shift+Enter: Move selection up after closing editor
Shift+Tab Move selection left after closing editor
Arrow-up: Move selection up after closing editor if formula is plain text
Arrow-left, Arrow-down, Arrow-right: same as above for other directions

In general, think it should be left up to developers to decide which direction to go to using the new onFinishedEditing, and deprecate the default onKeyDown for custom editors.
<div className="clip-region" onKeyDown={onKeyDown}>
  {editor}
</div>

@BrianHung does this change enables me to keep focus in the same cell after edit is finished?


feat: revert preconfs logic; only emit receipts when a block is mined

Feature Request
Describe the Feature Request

it seems preconfs (ability to create receipts before block is mined) aren't supported anywhere (no SDK is prepared for it)
it creates probable bugs with existing tools (indexers)
went and talked to EPBS peeps and preconfs people, and it looks no one is building support for preconfs

Describe Preferred Solution
cc @greged93 need further scoping, but essentially, revert back to normal behaviour where receipts are emitted when the block is mined

do we still want this?

i'm not sure; for now let's close it


Add alpine image and arm images

Alpine image w/ shell so people can use drone/cli:alpine in their pipelines.
ARM images because why not.
Closes https://github.com/drone/drone-cli/issues/68.

PTAL @bradrydzewski @tboerger.

Looks great, we just need a when: { event: [ push, tag ] }. The docker plugin does not ignore pull request events and then the steps fail. This is probably a separate update we can make to the docker plugin auto tag logic.
Thanks!

Gotcha, did not know that!


Make opencv optional

Seeks to address https://github.com/Kitware/pyBSM/issues/1 by making opencv-python optional
details about what the issue is are in: https://github.com/Kitware/nrtk/issues/2
We want to make it such that the package can be used with either opencv-python xor opencv-python-headless, and we don't want pip to clobber an environment that depends on opencv-python-headless just because we pip install this package. The best solution I have so far is just make both optional and inform the user that they need to pick one if we try to use cv2 at runtime and it is not there.

PRs that end up on GitHub will have to get manually replicated into the primary repo this repo is mirrored from. I saw your PR/comment on this previously but haven't had a chance yet to move a solution into the primary repo. I have to confirm it complies with the program's SDP before proceeding.
I can't seem to find the original comment about why this is causing an issue, can you link it here again so I can take a look?

I've written about the issue in several places. This one is a good summary: https://github.com/opencv/opencv-python/issues/467
The essence is opencv-python and opencv-python-headless cannot be installed together, but both provide the cv2 module. Some libraries do not work with opencv-python and instead require opencv-python-headless, also vis-versa (for instance nrtk is currently a library that requires opencv-python, so it locks out being installed with any other package that requires opencv-python-headless).
This comment also gives another perspective on the issue: https://github.com/pypa/pip/pull/10837#issuecomment-1921965054
Effectively, the solution to the problem is: don't depend on any opencv flavor in the top level requirements. Any dependency on opencv should be optional. If the main use-case of this tool requires the opencv-python flavor, then the official instruction change from pip install pyBSM to pip install pyBSM[cv2-graphics]. Likewise for any downstream program that wants to require opencv-python headless (which is my preference) the instructions become  pip install pyBSM[cv2-headless]. Note: you can rename the cv2-graphics and cv2-headless tag whatever you want.

We're tracking this over in the primary gitlab instance now, I'll close these PRs once there is a solution that gets propagated.

The fix should be in now as of this commit, and was released in pybsm==0.7.0. Closing the Issue, please re-open if the issue persists.


Populating an hstore in Factories causes a significant slowdown

Description
I've noticed a significant performance hit when running rspec tests whenever there is a factory that populates an hstore column.
Reproduction Steps
Create an hstore column and set it like so:
FactoryBot.define do
  factory :artifact do
    subject { 'foo_subject' }
    subject_address { { 'street' => Faker::Address.street_address } }
  end
end

When an rspec test uses this factory with subject_address commented out, the test runs 3-6x faster. An example test to demonstrate the speed difference could be as simple as:
RSpec.describe Example do
  let(:artifact) { create(:artifact) }
  it 'does something' { artifact }
end

### System configuration
**factory_bot version**:  6.2.0
**rails version**:  <IP_ADDRESS>
**ruby version**:  3.1.2p20

Given the factory definition in your comment, calling create(:artifact) is equivalent to:
artifact = Artifact.new
artifact.subject = "foo_subject"
artifact.subject_address = { 'street' => Faker::Address.street_address }
artifact.save!

Do you see the same slowdown if you run that instead of create(:artifact)?


Adds check for neutron service venv

This checks all neutron services to ensure using the proper
virtual environment for the openstack release. Reports fail
on any neutron service not running via correct venv.
This cherry pick includes correcting variable used of
"neutron_venv_bin" which had a bad copy/pasta using swift
variable.
Connects rcbops/u-suk-dev#857
(cherry picked from commit fc40fa13146d4e685e97733bcd495dd38a61eac0)

recheck_cit_upgrade

failure on upgrade was maas setup.
recheck_cit_upgrade

recheck_cit_all

recheck_cit_all

recheck_cit_upgrade

recheck_cit_upgrade

Looks like tempest cinder_backup fail, which is resolved https://github.com/rcbops/rpc-gating/pull/163 and build 113 reported as a successful build.
recheck_cit_upgrade

jenkinsapi.custom_exceptions.JenkinsAPIException: Unable to iterate nodes failure, existing issue
recheck_cit_upgrade

recheck_cit_upgrade

recheck_cit_upgrade

recheck_cit_upgrade - Tempest defcore cinder_backup fail

recheck_cit_upgrade - selenium failure

Cinder failure related to #2258

recheck_cit_upgrade - rolling the dice

recheck_cit_upgrade - Fail was not from cinder, and was a jenkins error:
Resuming build at Thu May 18 16:55:09 GMT 2017 after Jenkins restart
Waiting to resume part of RPC-AIO_mitaka-upgrade-pr #129: ???
Waiting to resume part of RPC-AIO_mitaka-upgrade-pr #129: There are no nodes with the label ‘rpc-jenkins-n02.prod.dfw1.cit.rackspace.net-9082c1d1’
Waiting to resume part of RPC-AIO_mitaka-upgrade-pr #129: There are no nodes with the label ‘rpc-jenkins-n02.prod.dfw1.cit.rackspace.net-9082c1d1’
Waiting to resume part of RPC-AIO_mitaka-upgrade-pr #129: There are no nodes with the label ‘rpc-jenkins-n02.prod.dfw1.cit.rackspace.net-9082c1d1’
Waiting to resume part of RPC-AIO_mitaka-upgrade-pr #129: There are no nodes with the label ‘rpc-jenkins-n02.prod.dfw1.cit.rackspace.net-9082c1d1’
Waiting to resume part of RPC-AIO_mitaka-upgrade-pr #129: rpc-jenkins-n02.prod.dfw1.cit.rackspace.net-9082c1d1 is offline
Ready to run at Thu May 18 16:55:31 GMT 2017
Timeout set to expire in 4 hr 10 min
Cannot contact rpc-jenkins-n02.prod.dfw1.cit.rackspace.net-9082c1d1: java.io.IOException: remote file operation failed: /var/lib/jenkins/workspace/RPC-AIO_mitaka-upgrade-pr@2/rpc-gating/playbooks at hudson.remoting.Channel@187fc218:Channel to /<IP_ADDRESS>: hudson.remoting.ChannelClosedException: channel is already closed
Aborted by Melissa Kam
Could not connect to rpc-jenkins-n02.prod.dfw1.cit.rackspace.net-9082c1d1 to send interrupt signal to process

recheck_cit_upgrade

recheck_cit_upgrade

recheck_cit_upgrade - TEMPEST FAIL scenario defcore cinder_backup (308 tests)

recheck_cit_upgrade - cinder_backup has been disabled on gating, this should pass now

The commit 5c845d2c58d7b843eeada89ba31eb2f85d9979be was added as it was found in an AIO, the host is included in the neutron_all group. The previous method of inventory_hostname in groups['utility'][0] would result in what was expected to run on the utility container to be attempted on the AIO host. This would then fail tests intended for the utility node due to the host not having the openstack client or openrc file required.

Updated commit message

Merged for test-requirements fix which resolves Travis build issue ^

recheck_cit_upgrade - unrelated failure.
failed: [ramup-151-d5ef] => {"failed": true}
msg: Could not fetch updated apt files

FATAL: all hosts have already failed -- aborting```

closing this in preference to #2225


latest matplotlib

Only the hash changed, even if we have svg_hashsalt in our style. Is there other hash we need to set?
The culprit lies in one of this package:
Successfully installed contourpy-1.2.1 fonttools-4.53.0 numpy-2.0.0 pillow-10.3.0 pyparsing-3.1.2 python_dateutil-2.9.0.post0 scipy-1.13.1

We need to make sure that plothist_make_examples creates the correct plots, right now it only has a lower limit on the matplotlib version, which we saw is not enough.
Edit: we should also monitor numpy version, which has an impact on the hash of the saved svg. Adding the same threshold as matplotlib might be a good solution.
Note: I had numpy-1.26.4 because tensorflow doesn't like higher versions. Which version should we settle on?

A new major release of numpy/matplotlib is rare, so I think we do not need to take additional measures, but let's discuss in a meeting.


The automated release is failing 🚨

:rotating_light: The automated release from the 7.x branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the 7.x branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The release 7.58.0 on branch 7.x cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=7.57.0 <7.57.0 can be published from branch 7.x.
The following commits are responsible for the invalid release:

feat: apim-3748 notification banner when expire today (2695eec)
fix: am-2140 contact link in notification banner (5ccd611)
chore: allow circleci to release 7.x branche (857aeee)
fix(gio-form-tags-input): refresh on form control changes (8a8cb50)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 7.x with git revert or git reset.
A valid branch could be main.
See the workflow configuration documentation for more details.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the 7.x branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the 7.x branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The release 7.58.0 on branch 7.x cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=7.57.0 <7.57.0 can be published from branch 7.x.
The following commits are responsible for the invalid release:

feat: apim-3748 notification banner when expire today (d45b315)
fix: am-2140 contact link in notification banner (6b39fb9)
chore: allow circleci to release 7.x branche (9fe851c)
fix(gio-form-tags-input): refresh on form control changes (8a8cb50)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 7.x with git revert or git reset.
A valid branch could be main.
See the workflow configuration documentation for more details.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the 7.x branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the 7.x branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here are some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The release 7.58.0 on branch 7.x cannot be published as it is out of range.
Based on the releases published on other branches, only versions within the range >=7.57.0 <7.57.0 can be published from branch 7.x.
The following commits are responsible for the invalid release:

feat: apim-3748 notification banner when expire today (16ec399)
fix: am-2140 contact link in notification banner (4424290)
fix(gio-form-tags-input): refresh on form control changes (7e64095)
chore: allow circleci to release 7.x branche (c843d3f)

Those commits should be moved to a valid branch with git merge or git cherry-pick and removed from branch 7.x with git revert or git reset.
A valid branch could be main.
See the workflow configuration documentation for more details.

Good luck with your project ✨
Your semantic-release bot :package::rocket:


App crashes entering ACTRequest on Jeremy's tablet

seems to be hardware issue, his tablet's memory corruption caused it


How to show video in portrait mode...?

When I'm clicking on the link, the video is only opening in landscape mode. How to show video in portrait mode...?

Any advice on this topic?

Hi Bob, do you have any idea for this..?


ic-include bug for array of elements

When using ic-include attribute to submit a form which contains a group of checkboxes (an array of checkbox inputs) the submitted values will be duplicated.
<form id="form">

  <input type=checkbox name=checkarray[] value=aaa checked>
  <input type=checkbox name=checkarray[] value=bbb checked>
  <input type=checkbox name=checkarray[] value=ccc>
  <button ic-post-to="results.php" ic-target="#res" ic-include="#form"> send </button>

</form>

The result will be:  [checkarray] => Array ( [0] => aaa [1] => bbb [2] => aaa [3] => bbb )
However if we change ic-include="#form" to ic-include="#div" the result will be correct:  [checkarray] => Array ( [0] => aaa [1] => bbb )

sorry, I didn't have to add ic-include attribute at all.

:)
Cheers,
Carson
On July 25, 2016 at 9:07:13 AM, styxyk<EMAIL_ADDRESS>wrote:
Closed #107.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Update data transfer to use power model

The current numbers we're using for data transfer don't pass the sniff test. The idea that it takes 0.1 kWh to deliver a GB of data implies that the energy use is 100W - if the data transfer took an hour. However, looking at Malmodin and other models of the actual data transmission infrastructure, this seems an order of magnitude too high. The "high" bandwidth model (6.67 mbps) is around 11.4W, and most residential broadband is significantly faster than this these days.
It seems like we should be using the power model to figure out the bandwidth cost (effectively, "how many seconds does it take to transfer"):

This is significantly lower than the numbers we are seeing today by a factor of 25. This feels much more reasonable!

Hello Brian,
Gauthier Roussilhe has published a great write-up on the DIMPACT/Carbon Trust approach here detailing the different power factors for:

core networks (common for all cases)
access networks (different model for fixed and mobile networks)
home router (only in the case of fixed networks)

The bandwidth to consider should be adapted depending on the type of delivery I guess.

Hello @bokelley and @EmmaLouise2018
While looking at  I was finding the fixed electricity consumption rate chosen for fixed networks to be high compared to the study above. I might have missed something as well but did you use other research?
I'm concerned this could somewhat incentivize users to move delivery to mobile/cellular in certain cases, which isn't what we want from a global perspective (from different studies the footprint of fixed networks is less correlated with data usage compared to the one of cellular networks). Did you check the impact of this update on the current numbers? I would argue that once the fixed network is here we better be maximizing the use of it!
Also, it could be inconsistent with the figures used in the SRI dataset based on the ADEME ARCEP work and the associated public recommendation to mitigate the environmental impact of digital
"In January 2023, Arcep published an FAQ for the general public on its website, offering tips and best practices for digital device users on how to curtail their environmental footprint. Drawing on the findings of its work, the Authority recommends, for instance, opting for a fixed (fiber, ADSL) internet connection whenever possible."
Thanks for your thoughts on this!

This is excellent - thank you @github-benjamin-davy! We are working on this in #125 and will continue to update as we get new data. I think we are still below SRI on mobile and trying to understand the gap.


Parallelise chunk fetches

At least for the DynamoDB back-end, chunks are fetched in batches of 100, serially.
The 100 limit comes from Amazon.
Brief experimentation shows it will go way faster if we parallelise the fetches.
For extra credit, split by table, by hash-key, etc., to maximise use of available parallelisation inside DynamoDB.

Closed by #603


Individual Month Selector in Endlos

Each month is behaving as individual item and hence contains multiple selecto

Closed in PR


Sidebar should show highlight on first launch on the iPad

Right now, no sidebar section is highlighted.

The highlight should also be restored when switching to show the sidebar.

Fixed in 294cf3c56952eb3312029f921f6c175b464ea543.


Add 'Pro' statement

Pro statement about the ease of debugging Python code using the interpreter

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

@mkanoria Excellent addition!
Congrats on your first-time contribution!


Incorrect suggestion: liftIO $ window on deleteEvent $ do ..., Why not: liftIO window

Here's how to reproduce it:
import Control.Monad
import Control.Monad.IO.Class
import Control.Monad.Trans.Identity
import Graphics.UI.Gtk

main :: IO ()
main = do
  void initGUI
  window <- windowNew
  runIdentityT $ liftIO $ window `on` deleteEvent $ do
    liftIO mainQuit
    return False
  mainGUI

The hint reads:
Redundant $ found: liftIO $ window. Why not: liftIO window
which is obviously wrong.

Where is on imported from?
When I import on from Data.Function and try this:
_ $ _ `on` _

I get:
error:
Precedence parsing error
    cannot mix ‘$’ [infixr 0] and ‘on’ [infixl 0] in the same infix expression

Is your example valid working code?

on is imported from Graphics.UI.Gtk, which imports it from System.Glib.Signals. Its type signature is on :: object -> Signal object callback -> callback -> IO (ConnectId object).
The code compiles with GHC 8.2.2.

The problem is that the base library defines a function on with fixity 0, while Gtk defines one with fixity 9. As it turns out, given the use patterns of both functions, having it defined with fixity 8 probably doesn't break any code hint-wise, so I've done that.


@everyone run no worked so i fixed :)

@everyone run no worked so i fixed :)

You need to install visual studio 2022 with .net 6. .NET 5 is out of support.


[TKG with Antrea on AWS] - Most of the worker-nodes is a cluster went into NotReady state

Describe the bug
Antrea build: antrea/antrea-ubuntu:v0.9.0

Deployed 3 master and 20 worker nodes tkg cluster
Configured antrea cni for tkg cluster deployed in AWS
Enabled hybrid mode and antrea-proxy
Deployed tkg worker nodes across 2 AZs having different subnet
Disabled SrcDestCheck on each node in the cluster
Scaled up cluster with 1k namespaces, 2k pods, 2k clusterip services and 10k network-policies

Observation:

Verified icmp traffic across all pods it was working fine
Verified svc traffic on clusterip through antrea-proxy, it was working fine
However, after few hours of sanity test, observed that most of the worker-nodes went into NotReady state
Antrea-controller also restarted/terminated once

# kubectl describe node ip-10-0-2-4.us-west-2.compute.internal
Name:               ip-10-0-2-4.us-west-2.compute.internal
Roles:              <none>
Labels:             beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/instance-type=t3.small
                    beta.kubernetes.io/os=linux
                    failure-domain.beta.kubernetes.io/region=us-west-2
                    failure-domain.beta.kubernetes.io/zone=us-west-2b
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=ip-10-0-2-4.us-west-2.compute.internal
                    kubernetes.io/os=linux
                    node.kubernetes.io/instance-type=t3.small
                    topology.kubernetes.io/region=us-west-2
                    topology.kubernetes.io/zone=us-west-2b
Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: /run/containerd/containerd.sock
                    node.alpha.kubernetes.io/ttl: 0
                    projectcalico.org/IPv4Address: <IP_ADDRESS>/24
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Mon, 24 Aug 2020 05:19:50 +0000
Taints:             node.kubernetes.io/unreachable:NoExecute
                    node.kubernetes.io/unreachable:NoSchedule
                    node.kubernetes.io/unschedulable:NoSchedule
Unschedulable:      true
Lease:
  HolderIdentity:  ip-10-0-2-4.us-west-2.compute.internal
  AcquireTime:     <unset>
  RenewTime:       Mon, 24 Aug 2020 11:54:34 +0000
Conditions:
  Type                 Status    LastHeartbeatTime                 LastTransitionTime                Reason              Message
  ----                 ------    -----------------                 ------------------                ------              -------
  NetworkUnavailable   False     Mon, 24 Aug 2020 05:20:13 +0000   Mon, 24 Aug 2020 05:20:13 +0000   CalicoIsUp          Calico is running on this node
  MemoryPressure       Unknown   Mon, 24 Aug 2020 11:52:50 +0000   Mon, 24 Aug 2020 11:55:20 +0000   NodeStatusUnknown   Kubelet stopped posting node status.
  DiskPressure         Unknown   Mon, 24 Aug 2020 11:52:50 +0000   Mon, 24 Aug 2020 11:55:20 +0000   NodeStatusUnknown   Kubelet stopped posting node status.
  PIDPressure          Unknown   Mon, 24 Aug 2020 11:52:50 +0000   Mon, 24 Aug 2020 11:55:20 +0000   NodeStatusUnknown   Kubelet stopped posting node status.
  Ready                Unknown   Mon, 24 Aug 2020 11:52:50 +0000   Mon, 24 Aug 2020 11:55:20 +0000   NodeStatusUnknown   Kubelet stopped posting node status.
Addresses:
  InternalIP:   <IP_ADDRESS>
  Hostname:     ip-10-0-2-4.us-west-2.compute.internal
  InternalDNS:  ip-10-0-2-4.us-west-2.compute.internal
Capacity:
  attachable-volumes-aws-ebs:  25
  cpu:                         2
  ephemeral-storage:           83873772Ki
  hugepages-1Gi:               0
  hugepages-2Mi:               0
  memory:                      2002020Ki
  pods:                        110
Allocatable:
  attachable-volumes-aws-ebs:  25
  cpu:                         2
  ephemeral-storage:<PHONE_NUMBER>8
  hugepages-1Gi:               0
  hugepages-2Mi:               0
  memory:                      1899620Ki
  pods:                        110
System Info:
  Machine ID:                 ec217cfd919c15459a14b152666b85fc
  System UUID:                EC217CFD-919C-1545-9A14-B152666B85FC
  Boot ID:                    daf9c0d8-c089-4d98-8c9f-b3583e64b83a
  Kernel Version:             4.14.181-140.257.amzn2.x86_64
  OS Image:                   Amazon Linux 2
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  containerd://1.3.4
  Kubelet Version:            v1.18.3+vmware.1
  Kube-Proxy Version:         v1.18.3+vmware.1
PodCIDR:                      <IP_ADDRESS>/24
PodCIDRs:                     <IP_ADDRESS>/24
ProviderID:                   aws:///us-west-2b/i-01fc0f87203b0c0c6
Non-terminated Pods:          (110 in total)
  Namespace                   Name                  CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE
  ---------                   ----                  ------------  ----------  ---------------  -------------  ---
  kube-system                 antrea-agent-lqm2d    400m (20%)    0 (0%)      0 (0%)           0 (0%)         8h
  kube-system                 kube-proxy-n2fj5      0 (0%)        0 (0%)      0 (0%)           0 (0%)         8h
  scale-ns-109                coffee-rc-2-s45xs     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h53m
  scale-ns-124                coffee-rc-2-bl8qr     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h51m
  scale-ns-129                coffee-rc-2-nhp55     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h51m
  scale-ns-143                coffee-rc-2-fjkkt     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h49m
  scale-ns-145                coffee-rc-1-p6kcd     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h48m
.
.
.
  scale-ns-883                coffee-rc-2-lzwtf     0 (0%)        0 (0%)      0 (0%)           0 (0%)         5h5m
  scale-ns-891                coffee-rc-2-6jk88     0 (0%)        0 (0%)      0 (0%)           0 (0%)         5h3m
  scale-ns-91                 coffee-rc-2-5s7bv     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h56m
  scale-ns-910                coffee-rc-1-8tsw8     0 (0%)        0 (0%)      0 (0%)           0 (0%)         5h1m
  scale-ns-913                coffee-rc-2-jxjmj     0 (0%)        0 (0%)      0 (0%)           0 (0%)         5h
  scale-ns-933                coffee-rc-1-gfxtv     0 (0%)        0 (0%)      0 (0%)           0 (0%)         4h57m
  scale-ns-99                 coffee-rc-1-tbn8k     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h55m
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)

Expected

worker-nodes should not went into NotReady state

Actual behavior

Most of the worker-nodes is a cluster went into NotReady state

Versions:
Please provide the following information:

Antrea version (Docker image tag).
"antrea/antrea-ubuntu:v0.9.0"

Kubernetes version (use kubectl version). If your Kubernetes components have different versions, please provide the version for all of them.

"v1.18.6"

Container runtime: which runtime are you using (e.g. containerd, cri-o, docker) and which version are you using?
Linux kernel version on the Kubernetes Nodes (uname -r).
If you chose to compile the Open vSwitch kernel module manually instead of using the kernel module built into the Linux kernel, which version of the OVS kernel module are you using? Include the output of modinfo openvswitch for the Kubernetes Nodes.

Additional context

Not able to ssh to worker-nodes, hence can't collect logs on worker-nodes

(Please consider pasting long output into a GitHub gist or any other pastebin.)

It seems that you are scheduling 110 Pods on each Node, which is the limit and I believe explains why we see SchedulingDisabled for most Nodes. Is there any way to check memory usage on the Nodes? I don't know how much memory your workload Pods are consuming here, but the Nodes only have 2GB of memory to start with.

Looking at this, it seems to be a memory issue, since as soon as we try to schedule 80+ nginx Pods on a Node, we see the Node become unschedulable, but the issue does not seem to happen with only 40 Pods. We are not sure why @rbhamre
was able to run sanity tests for a few hours before running into an issue. @rbhamre is checking the kube-controller-manager logs to see if we can find more info about why the taint is being added.

PFA kube-controller-manager logs, didn't find anything suspicions.
kube-controller-manager-1.log.txt
kube-controller-manager-2.log.txt
kube-controller-manager-3.log.txt
.

I see lots of “context deadline exceeded” as well as "container runtime is down" from kubelet log. The Node seems heavily overloaded. If it's this case, it's expected that kubelet reports itself as unschedulable because it failed to check container runtime's status, or even not reporting its status in time, then nodeLifeController could add taints to this Node and evict all Pods. @rbhamre could you confirm the CPU load of the worker Node from the output of uptime or any monitoring tool of AWS?

Hi Quan, didn't captured this details when the issue was observed, however can you please check if the below cmd o/p may help?
> # kubectl describe node ip-10-0-2-4.us-west-2.compute.internal
> Name:               ip-10-0-2-4.us-west-2.compute.internal
> Roles:              <none>
> Labels:             beta.kubernetes.io/arch=amd64
>                     beta.kubernetes.io/instance-type=t3.small
>                     beta.kubernetes.io/os=linux
>                     failure-domain.beta.kubernetes.io/region=us-west-2
>                     failure-domain.beta.kubernetes.io/zone=us-west-2b
>                     kubernetes.io/arch=amd64
>                     kubernetes.io/hostname=ip-10-0-2-4.us-west-2.compute.internal
>                     kubernetes.io/os=linux
>                     node.kubernetes.io/instance-type=t3.small
>                     topology.kubernetes.io/region=us-west-2
>                     topology.kubernetes.io/zone=us-west-2b
> Annotations:        kubeadm.alpha.kubernetes.io/cri-socket: /run/containerd/containerd.sock
>                     node.alpha.kubernetes.io/ttl: 0
>                     projectcalico.org/IPv4Address: <IP_ADDRESS>/24
>                     volumes.kubernetes.io/controller-managed-attach-detach: true
> CreationTimestamp:  Mon, 24 Aug 2020 05:19:50 +0000
> Taints:             node.kubernetes.io/unreachable:NoExecute
>                     node.kubernetes.io/unreachable:NoSchedule
>                     node.kubernetes.io/unschedulable:NoSchedule
> Unschedulable:      true
> Lease:
>   HolderIdentity:  ip-10-0-2-4.us-west-2.compute.internal
>   AcquireTime:     <unset>
>   RenewTime:       Mon, 24 Aug 2020 11:54:34 +0000
> Conditions:
>   Type                 Status    LastHeartbeatTime                 LastTransitionTime                Reason              Message
>   ----                 ------    -----------------                 ------------------                ------              -------
>   NetworkUnavailable   False     Mon, 24 Aug 2020 05:20:13 +0000   Mon, 24 Aug 2020 05:20:13 +0000   CalicoIsUp          Calico is running on this node
>   MemoryPressure       Unknown   Mon, 24 Aug 2020 11:52:50 +0000   Mon, 24 Aug 2020 11:55:20 +0000   NodeStatusUnknown   Kubelet stopped posting node status.
>   DiskPressure         Unknown   Mon, 24 Aug 2020 11:52:50 +0000   Mon, 24 Aug 2020 11:55:20 +0000   NodeStatusUnknown   Kubelet stopped posting node status.
>   PIDPressure          Unknown   Mon, 24 Aug 2020 11:52:50 +0000   Mon, 24 Aug 2020 11:55:20 +0000   NodeStatusUnknown   Kubelet stopped posting node status.
>   Ready                Unknown   Mon, 24 Aug 2020 11:52:50 +0000   Mon, 24 Aug 2020 11:55:20 +0000   NodeStatusUnknown   Kubelet stopped posting node status.
> Addresses:
>   InternalIP:   <IP_ADDRESS>
>   Hostname:     ip-10-0-2-4.us-west-2.compute.internal
>   InternalDNS:  ip-10-0-2-4.us-west-2.compute.internal
> Capacity:
>   attachable-volumes-aws-ebs:  25
>   cpu:                         2
>   ephemeral-storage:           83873772Ki
>   hugepages-1Gi:               0
>   hugepages-2Mi:               0
>   memory:                      2002020Ki
>   pods:                        110
> Allocatable:
>   attachable-volumes-aws-ebs:  25
>   cpu:                         2
>   ephemeral-storage:<PHONE_NUMBER>8
>   hugepages-1Gi:               0
>   hugepages-2Mi:               0
>   memory:                      1899620Ki
>   pods:                        110
> System Info:
>   Machine ID:                 ec217cfd919c15459a14b152666b85fc
>   System UUID:                EC217CFD-919C-1545-9A14-B152666B85FC
>   Boot ID:                    daf9c0d8-c089-4d98-8c9f-b3583e64b83a
>   Kernel Version:             4.14.181-140.257.amzn2.x86_64
>   OS Image:                   Amazon Linux 2
>   Operating System:           linux
>   Architecture:               amd64
>   Container Runtime Version:  containerd://1.3.4
>   Kubelet Version:            v1.18.3+vmware.1
>   Kube-Proxy Version:         v1.18.3+vmware.1
> PodCIDR:                      <IP_ADDRESS>/24
> PodCIDRs:                     <IP_ADDRESS>/24
> ProviderID:                   aws:///us-west-2b/i-01fc0f87203b0c0c6
> Non-terminated Pods:          (110 in total)
>   Namespace                   Name                  CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE
>   ---------                   ----                  ------------  ----------  ---------------  -------------  ---
>   kube-system                 antrea-agent-lqm2d    400m (20%)    0 (0%)      0 (0%)           0 (0%)         8h
>   kube-system                 kube-proxy-n2fj5      0 (0%)        0 (0%)      0 (0%)           0 (0%)         8h
>   scale-ns-109                coffee-rc-2-s45xs     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h53m
>   scale-ns-124                coffee-rc-2-bl8qr     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h51m
>   scale-ns-129                coffee-rc-2-nhp55     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h51m
>   scale-ns-143                coffee-rc-2-fjkkt     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h49m
>   scale-ns-145                coffee-rc-1-p6kcd     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h48m
> .
> .
> .
>   scale-ns-883                coffee-rc-2-lzwtf     0 (0%)        0 (0%)      0 (0%)           0 (0%)         5h5m
>   scale-ns-891                coffee-rc-2-6jk88     0 (0%)        0 (0%)      0 (0%)           0 (0%)         5h3m
>   scale-ns-91                 coffee-rc-2-5s7bv     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h56m
>   scale-ns-910                coffee-rc-1-8tsw8     0 (0%)        0 (0%)      0 (0%)           0 (0%)         5h1m
>   scale-ns-913                coffee-rc-2-jxjmj     0 (0%)        0 (0%)      0 (0%)           0 (0%)         5h
>   scale-ns-933                coffee-rc-1-gfxtv     0 (0%)        0 (0%)      0 (0%)           0 (0%)         4h57m
>   scale-ns-99                 coffee-rc-1-tbn8k     0 (0%)        0 (0%)      0 (0%)           0 (0%)         6h55m
> Allocated resources:
>   (Total limits may be over 100 percent, i.e., overcommitted.)
>   Resource                    Requests    Limits
>   --------                    --------    ------
>   cpu                         400m (20%)  0 (0%)
>   memory                      0 (0%)      0 (0%)
>   ephemeral-storage           0 (0%)      0 (0%)
>   hugepages-1Gi               0 (0%)      0 (0%)
>   hugepages-2Mi               0 (0%)      0 (0%)
>   attachable-volumes-aws-ebs  0           0
> Events:                       <none>
>
> #############################
>
>
> # kubectl get nodes -o wide
> NAME                                       STATUS                        ROLES    AGE   VERSION            INTERNAL-IP   EXTERNAL-IP   OS-IMAGE         KERNEL-VERSION                  CONTAINER-RUNTIME
> ip-10-0-0-130.us-west-2.compute.internal   NotReady,SchedulingDisabled   <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-0-139.us-west-2.compute.internal   Ready,SchedulingDisabled      <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-0-154.us-west-2.compute.internal   Ready                         <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-0-161.us-west-2.compute.internal   NotReady,SchedulingDisabled   <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-0-162.us-west-2.compute.internal   Ready                         <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-0-194.us-west-2.compute.internal   Ready                         <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-0-225.us-west-2.compute.internal   Ready,SchedulingDisabled      <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-0-33.us-west-2.compute.internal    NotReady                      <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>     <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-0-34.us-west-2.compute.internal    Ready                         master   9h    v1.18.3+vmware.1   <IP_ADDRESS>     <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-0-74.us-west-2.compute.internal    Ready,SchedulingDisabled      <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>     <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-0-77.us-west-2.compute.internal    NotReady,SchedulingDisabled   <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>     <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-2-108.us-west-2.compute.internal   NotReady,SchedulingDisabled   <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-2-120.us-west-2.compute.internal   Ready,SchedulingDisabled      <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-2-143.us-west-2.compute.internal   NotReady,SchedulingDisabled   <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-2-151.us-west-2.compute.internal   Ready                         <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-2-193.us-west-2.compute.internal   Ready,SchedulingDisabled      <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-2-194.us-west-2.compute.internal   Ready                         <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-2-247.us-west-2.compute.internal   Ready,SchedulingDisabled      <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-2-28.us-west-2.compute.internal    Ready                         master   9h    v1.18.3+vmware.1   <IP_ADDRESS>     <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-2-4.us-west-2.compute.internal     NotReady,SchedulingDisabled   <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>      <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-2-77.us-west-2.compute.internal    Ready                         <none>   8h    v1.18.3+vmware.1   <IP_ADDRESS>     <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-2-80.us-west-2.compute.internal    Ready                         <none>   9h    v1.18.3+vmware.1   <IP_ADDRESS>     <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> ip-10-0-4-233.us-west-2.compute.internal   Ready                         master   9h    v1.18.3+vmware.1   <IP_ADDRESS>    <none>        Amazon Linux 2   4.14.181-140.257.amzn2.x86_64   containerd://1.3.4
> root@oc-runner:~/nsx-qe/spark[65390](master)#
>
> #############################

@rbhamre There is no information about the resource usage of the Node from the above output. But according to the message "Kubelet stopped posting node status" and the previous logs that says "container runtime is down", I think this was because the Nodes were heavily overloaded, either under great memory or CPU pressure, causing container runtime or kubelet itself not responsive. Unless it's antrea's components consuming unreasonable amount of resources, there is not much thing we can do from antrea side. Could you try if it's same if you use any other CNI?

Hi @tnqn @antoninbas ,
In TKG-1.2 release, the minimum worker-node size should not be less that 2cpu and 8 mem. If we have tried to deploy tkg cluster in AWS less than this config then it is failing.
So looking at the min config requirement, I have deployed tkg cluster having 2 cpu and 8 mem using antrea and another cluster using calico cni, and scaled up the setup with 100+ pods per worker-node.
After 1 day of longevity I haven't seen the worker-node 'SchedulingDisabled' and 'NotReady' issue.
We can safely close this issue.

@rbhamre thanks for confirming!