⚠ SpeakUpConference.com has degraded performance

In 1000449, SpeakUpConference.com (https://www.speakupconference.com) experienced degraded performance:

HTTP code: 200
Response time: 17721 ms

Resolved: SpeakUpConference.com performance has improved in 148472e after 11 minutes.


lxc/config/file: allow overriding default remote by env variable

In some cases it's useful to override the default remote for a single
lxc command invocation instead of switch the default remote statically
in the configuration. Specifically in automated environments where you
deal with different remotes and parallel lxc command invocations happen
this is extremely helpful.
Signed-off-by: Simon Fels<EMAIL_ADDRESS>

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

Documentation preview available at: https://linuxcontainers.org/lxd/docs/pr.9792/

Looks good to be, can you just split the doc change as its own commit?

@stgraber there you go :-)

jenkins: test this please


ShouldHaveValidationErrorFor throws NullReferenceException

#978 # System Details
FluentValidation version:  8.4.0
Framework version: .net standard 2.0.3
Issue Description
This throws a NullReferenceException:
private MyNewValidator Validator { get; }

[Test]
public void ThenThereIsAnErrorMessageForProperty_Take()
{
	Validator.ShouldHaveValidationErrorFor(x => x.Take, -25, "*");
}

Stack trace:
System.NullReferenceException : Object reference not set to an instance of an object.
   at FluentValidation.DefaultValidatorExtensions.Validate[T](IValidator`1 validator, T instance, IValidatorSelector selector, String ruleSet)
   at FluentValidation.TestHelper.ValidationTestExtension.TestValidate[T,TValue](IValidator`1 validator, Expression`1 expression, T instanceToValidate, TValue value, String ruleSet, Boolean setProperty)
   at FluentValidation.TestHelper.ValidationTestExtension.ShouldHaveValidationErrorFor[T,TValue](IValidator`1 validator, Expression`1 expression, TValue value, String ruleSet)

Hi, yes you need to instantiate the validator first and assign it to your property. By default it’ll be null.

I did miss a bit out of the snippet... there is a constructor.... but I was being a wally and forgot to instantiate the validator.  Thanks :)


Move helper transform functions to static function library

There's an idea of a Blueprint Function Library, which is basically a collection of static BlueprintCallable functions, defined in C++, that can be used anywhere in the project in Blueprints and C++. Perhaps it may be useful to move some of the helper functions in CesiumGeoreference (like TransformRotatorEnuToUe) to this function library so actors won't necessarily need to get a reference to CesiumGeoreference in order to make use of them. What do you think?
The syntax looks something like this:
UCLASS()
class MYMODULE UMyFunctionLibrary : public UBlueprintFunctionLibrary
{
   GENERATED_BODY()
public:
   UFUNCTION(BlueprintPure, Category="My Function Library")
   static FVector MyConversionFunction(const FVector& InVector);

Great idea, I hacked those functions into place very last-second, it would make a lot more sense as static functionality. They still need the CesiumGeoreference reference, but it should be possible to get a static reference to CesiumGeoreference (or create one if it doesn't exist) by using GetDefaultForActor(actor). I wrote another version called GetDefaultForLevel(level) but it's still in a branch, but both may be useful for implementing the function library.

Great, I can get started on that tomorrow I think.

GetDefaultForActor(actor). I wrote another version called GetDefaultForLevel(level)

Is there a reason not to use GetActorOfClass here?
There's also a neat trick with these types of functions. You can define it like this:
UFUNCTION(BlueprintPure, meta=(WorldContext="WorldContextObject"))
static AActor* GetCustomActorFromWorld(const UObject* WorldContextObject);

and in Blueprints, it will automagically pass in the WorldContextObject without exposing a separate input pin. In C++ you would simply pass in this


Revving static files

Hey there,
would you like for static assets to be revisioned? Revving them, writing stuff to a manifest.json, maybe in Jekyll's _data folder, then referencing them, you know?

@S1SYPHOS
Thanks for your idea! The more simple and flexible structure would be better. Do you think this is?

@ixkaito Totally, but it's your call - I'll provide an idea so you may see for yourself!

@S1SYPHOS Thanks! I'll also check by myself!

I'd like to separate source files (everything going into the site) and config/node files (node_modules, package.json, gulpfile.js etc), so the sctructure be
├── app
│   ├── _includes
│   ├── _posts
│   ├── _layouts
│   ├── ...
│   └── index.html
│
├── dist (renamed _site)
│   └── ...
│
├── package.json
├── gulpfile.js
├── frasco.webpack.config
├── ...

just a thought :v:

@S1SYPHOS
Thanks! I know this will make the structure more clear, but I want this project to be available for GitHub Pages simply to push it. Also, for Jekyll beginners, I think it's better to have the default Jekyll structure, e.g. _layouts, _includes, _posts, _site etc.

I totally understand this, thanks

@S1SYPHOS Released v1.0.0 but didn't change the file structure. Thank you for your issue again.


sea-orm Mock feature current now not ergonomics

As so far, we tried to use it, but it didn't meet expectations
why

mock not support clone.
write Test unit not inconvenient when call db function .

Hey @baoyachi, I understand the Clone issue. But could you elaborate more on the API of mock testing? Why it's inconvenient? Can you provide a code snippet / demo repository? Thanks!!


As a Node.js developer, I'd like a template repository that matches

Checked for duplicates
No - I haven't checked
🧑🔬 User Persona(s)
Data engineer
💪 Motivation
...so that I can develop Node.js apps that follow the PDS-EN best practices
📖 Additional Details
No response
Acceptance Criteria
Given
When I perform
Then I expect
⚙ Engineering Details
No response

Getting kicked off

Repository: https://github.com/NASA-PDS/template-repo-nodejs

tightly coupled / duplicate-ish of https://github.com/NASA-PDS/devops/issues/61


 I finished the first part! Can you check this Nataly?

This is how we divided our work, as you can see in the file, the Tuples' exercises were solved by Gustavo, then I solved the Lists' part, and finally, Yttan solved the Strings' exercises.


Create a Readme for  QoS-1.1, QoS-1.3 and QoS-1.5

This test aims to validate the functionality of ingress traffic classification and subsequent packet remarking (rewrite) on a Device Under Test (DUT). The DUT's configuration will be evaluated against the OpenConfig QOS model, and traffic flows will be analyzed to ensure proper classification, marking, and forwarding.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.5%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3573

💛  - Coveralls

Absolutely, but the existing DP tests utilize Weighted Round Robin (WRR) queues, while our tests exclusively employ strict priority queues. This difference in queueing mechanisms necessitates the creation of these new tests.

Absolutely, but the existing DP tests utilize Weighted Round Robin (WRR) queues, while our tests exclusively employ strict priority queues. This difference in queueing mechanisms necessitates the creation of these new tests.

Ah, I overlooked that.  So the DP tests have a mix, where one class is a priority queue and the others are indeed weighted round robin.
For consistency with the test id's, can you renumber these tests to be DP-* numbers?  Refer to and update the testregistry.textproto to assign the specific numbers so there is not a conflict.

I am deleting the QOS-1.3 readme file as there is a separate PR https://github.com/openconfig/featureprofiles/pull/3043


question

bro I have started 1m checking , what will happen
will it take storage please tell

Im sorry i dont understand your issue


Not published on NPM

Hey, this looks like a really cool project. Looking to use this in an app and I tried to install it but it's not on npm. Are you planning to publish the package at any point?
Thanks.

Hey, this looks like a really cool project. Looking to use this in an app and I tried to install it but it's not on npm. Are you planning to publish the package at any point?
Thanks.

Hi! Nice to hear that you are interested in the project.
The GitHub platform provides me with all the functionality I need to install and update my packages through npm. I haven't found a reason for publishing my packages on the npm registry so far.
Atlas may be installed through npm install joelek/atlas#semver:^1.0 and subsequently updated as if it was installed via the npm registry.
Is there a specific reason for why you want to install the package via the npm registry?


TreeHash fails on chunks > 3MB

Hello,
I've been doing some extensive debugging and believe I've found an issue with the treehasher: it doesn't pass tests for parts greater than 3MB. If I construct a data array in advance of, say, 3.5 MB of the byte 'a', and write it all at once to the TreeHasher, the checksum it calculates is wrong.
If instead I write the byte 'a' to the treehasher iteratively (3.5 MB worth), it outputs the correct checksum. For cases (1 << 20), (2 << 20), (3 << 20), both ways output the same result, and are correct. Do you know what might be the problem? I've hand-computed the checksums and also checked them against other repos (for example, https://github.com/jclouds/jclouds-labs-aws/blob/master/glacier/src/test/java/org/jclouds/glacier/util/TreeHashTest.java#L68 for the canonical treehash of the 3.5 MB bytestring; https://chromium.googlesource.com/external/boto/+/master/tests/unit/glacier/test_utils.py#108 for 4MB), so I don't think the checksum in the test case itself is the problem.
I've uploaded the failing test cases. 3.5 and 4 fail. Note that everything smaller, passes. https://github.com/recursionpharma/aws/blob/treehasher/glacier/treehash_test.go#L93
Please let me know.
Thanks!

Thanks for the report. The basic process of writing to the TreeHash is if the data doesn't fill whats remaining of a 1mb chunk just copy the data into the chunk (writing a byte at a time is going to hit this case most of the time). Otherwise the write can fill the 1mb chunk so it does, the chunk is then hashed and added (the Add from #11). Then all full 1mb parts of the input data are hashed and added. Finally the remaining data is copy into the 1mb chunk (similar to the first case). So writing 3.5mb a byte at a time and writing 3.5mb at once take separate code paths. I would suspect the bug lies there.
I'll be looking into this and #11 this weekend.

Understood, thanks for the explanation. I refactored and fixed the code so TreeHash passes all test cases, and that both MultiTreeHash and TreeHash use the same code. The commit is in with #11. Now on my side multipart glacier uploads with larger chunk sizes work fine.

Thanks for fixing this. I'm leaving the issue open because I'd like to take a look at reducing memory usage. Below is the difference of before and after merging #12 (I'm aware it's not really fair to compare broken to working code). I'm also not sure how the original implementation has 0 bytes, it's building up a list of nodes and they have to go somewhere.
benchmark             old ns/op     new ns/op     delta
BenchmarkTreeHash     11530         12264         +6.37%

benchmark             old MB/s     new MB/s     speedup
BenchmarkTreeHash     88.81        83.49        0.94x

benchmark             old allocs     new allocs     delta
BenchmarkTreeHash     0              0              +0.00%

benchmark             old bytes     new bytes     delta
BenchmarkTreeHash     0             5019          +Inf%

Yeah, that's a bit weird about the 0 ops. Right now I'm re-constructing a list for every level in the tree where newly-promoted nodes go, but it could certainly be done in-place with one leaf-node list with a little more care about indices. That would probably alleviate some of the performance issues.

I've converted the Write method to avoid allocation or copying too much in 996ef14ad5c8ce7705ab40d5a65bbf2c31e3cd55 and treeHash to build the root node in place in ef1a74249f6049bb04419ad63d1aec133e75e4ba.


the SQL script to generate the full IMDB database doesn't work

Hello I'm trying to reproduce the IMDB example but the link to the SQL script to generate the full IMDB database (requires a postgres database) doesn't work.
Grettings

I confirm that the link obdavm.inf.unibz.it/mo/ does not work now.
I checked that the files are still safe on the server.
We will contact our IT support to figure out what is the problem.

Thanks !

Check again. It was due to a misconfiguration after upgrading the version of Apache server.

Yes, it worked. Thank you very much.


Add the channel handshake CLI

Closes: #557
Description
Proposal
Added rrly -c config.toml channel handshake ibc-0 ibc-1 transfer transfer CLI.
Currently it doesn't allow to specify existing clients or connection to use for the channel. These will be added in the future.

For contributor use:

[ ] Updated the Unreleased section of CHANGELOG.md with the issue.
[ ] If applicable: Unit tests written, added test to CI.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Updated relevant documentation (docs/) and code comments.
[ ] Re-reviewed Files changed in the Github PR explorer.

Codecov Report

Merging #558 (f09f896) into master (b1b37f5) will increase coverage by 33.3%.
The diff coverage is 67.4%.

@@            Coverage Diff            @@
##           master    #558      +/-   ##
=========================================
+ Coverage    13.6%   46.9%   +33.3%
=========================================
  Files          69     138      +69
  Lines        3752    9047    +5295
  Branches     1374       0    -1374
=========================================
+ Hits          513    4251    +3738
- Misses       2618    4796    +2178
+ Partials      621       0     -621

Impacted Files
Coverage Δ

...application/ics20_fungible_token_transfer/error.rs
0.0% <0.0%> (ø)

...pplication/ics20_fungible_token_transfer/events.rs
0.0% <ø> (ø)

...ion/ics20_fungible_token_transfer/msgs/transfer.rs
0.0% <0.0%> (ø)

modules/src/events.rs
0.0% <0.0%> (ø)

modules/src/ics02_client/error.rs
100.0% <ø> (ø)

modules/src/ics02_client/raw.rs
0.0% <0.0%> (ø)

modules/src/ics03_connection/error.rs
100.0% <ø> (+66.6%)
:arrow_up:

modules/src/ics03_connection/msgs/conn_open_try.rs
86.7% <ø> (ø)

modules/src/ics03_connection/version.rs
97.6% <ø> (ø)

modules/src/ics04_channel/channel.rs
77.2% <ø> (+62.1%)
:arrow_up:

... and 257 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9d0a7b8...f09f896. Read the comment docs.

Codecov Report

Merging #558 (f09f896) into master (b1b37f5) will increase coverage by 33.3%.
The diff coverage is 67.4%.

@@            Coverage Diff            @@
##           master    #558      +/-   ##
=========================================
+ Coverage    13.6%   46.9%   +33.3%
=========================================
  Files          69     138      +69
  Lines        3752    9047    +5295
  Branches     1374       0    -1374
=========================================
+ Hits          513    4251    +3738
- Misses       2618    4796    +2178
+ Partials      621       0     -621

Impacted Files
Coverage Δ

...application/ics20_fungible_token_transfer/error.rs
0.0% <0.0%> (ø)

...pplication/ics20_fungible_token_transfer/events.rs
0.0% <ø> (ø)

...ion/ics20_fungible_token_transfer/msgs/transfer.rs
0.0% <0.0%> (ø)

modules/src/events.rs
0.0% <0.0%> (ø)

modules/src/ics02_client/error.rs
100.0% <ø> (ø)

modules/src/ics02_client/raw.rs
0.0% <0.0%> (ø)

modules/src/ics03_connection/error.rs
100.0% <ø> (+66.6%)
:arrow_up:

modules/src/ics03_connection/msgs/conn_open_try.rs
86.7% <ø> (ø)

modules/src/ics03_connection/version.rs
97.6% <ø> (ø)

modules/src/ics04_channel/channel.rs
77.2% <ø> (+62.1%)
:arrow_up:

... and 257 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9d0a7b8...f09f896. Read the comment docs.


Consume dev-site props-table-loader

Summary
Testing the new custom react-docgen based props-table-loader from terra-dev-site

Closing this in favor of a follow up PR once terra-dev-site supports MDX


Look into using Intents

https://discordpy.readthedocs.io/en/latest/intents.html
https://discordpy.readthedocs.io/en/latest/intents.html#privileged-intents

Can I be assigned to this

Can I be assigned to this @yannickgloster

@LakshyaShastri
Sorry, I already did this.

Okay, no worries


Support origin_url field on entries

This field was added in Wallabag version 2.3.4; here's the relevant PR: https://github.com/wallabag/wallabag/pull/3553
Closes https://github.com/jlnostr/wallabag-api/issues/7

Thanks for the PR! The NuGet package will be updated soon :)


🐛 Fixed line breaking in chat

^ what the title says
for some reason it also wants to merge the previous commit

Commit in this deployment and dev/fix branch have different hashes, so they have probably different parent commits, which are probably a result of incorrect branch merging/rebasing.
Google search sums up the issue.


Fix docker image size output

Move it to only run on pull requests after a build

Fixed in 50a315fe8df6e4222e3b7613de01590c79539e74.


Seeking behavior doesn't seem to work on demo page.

Be sure to search for your issue before opening a new one.
Current Behavior
On this demo page:
https://cookpete.com/react-player/
The seek position slider will update correctly with the current timestamp, but clicking on a position along the slider will temporarily move the slider to that position, fail to seek the video accordingly, and jump back to the position corresponding with the player's position. I tried this with YouTube, Vimeo, and a few others, and they all demonstrated the same behavior.
Expected Behavior
I expect seeking to a position to have the corresponding video playback also seek to the same position.
Steps to Reproduce
1.) go to https://cookpete.com/react-player/
2.) click on Youtube Test A
3.) click play on the video, wait for playback to begin
4.) note position on bar titled "Seek" updating correctly, corresponding with position in playback
5.) attempt to move the seek marker (not in the YouTube video, but react-player UI) to a desired position
6.) note that the video does not seek to this position, and the playback marker jumps back to the video playback position
Environment

URL attempting to play: https://www.youtube.com/watch?v=oUFJJNQGwhk
Browser: Chrome
Operating system: Mac OS
Demo page: https://cookpete.com/react-player/

Other Information

@CookPete I fixed this issue here:
https://github.com/CookPete/react-player/pull/868
All tests/lint passing, I recommend merging it because a lot of critical behavior is resolved by this change.

Fixed in v2.0.1

working fine with youtube, but this is still happening in vimeo.. any help?

Be sure to search for your issue before opening a new one.
Current Behavior
On this demo page:
https://cookpete.com/react-player/
The seek position slider will update correctly with the current timestamp, but clicking on a position along the slider will temporarily move the slider to that position, fail to seek the video accordingly, and jump back to the position corresponding with the player's position. I tried this with YouTube, Vimeo, and a few others, and they all demonstrated the same behavior.
Expected Behavior
I expect seeking to a position to have the corresponding video playback also seek to the same position.
Steps to Reproduce
1.) go to https://cookpete.com/react-player/
2.) click on Youtube Test A
3.) click play on the video, wait for playback to begin
4.) note position on bar titled "Seek" updating correctly, corresponding with position in playback
5.) attempt to move the seek marker (not in the YouTube video, but react-player UI) to a desired position
6.) note that the video does not seek to this position, and the playback marker jumps back to the video playback position
Environment

URL attempting to play: https://www.youtube.com/watch?v=oUFJJNQGwhk
Browser: Chrome
Operating system: Mac OS
Demo page: https://cookpete.com/react-player/

Other Information

I know on mobile there are some issues with video etc. But the seek does not work on mobile, it's the same as the issue described above. Is this a know issue?


Not getting it to work

Any hints on getting this to work? Using the README info a run into problems.
Unknown Extension: sync_source

Same with sync_target. I'm using the latest github sources and already saw that it should be: aws_target?

This worked for me:
activate :sync do |config|
  config.verbose = true
  config.run_on_build = true
end
activate :aws_target do |target|
  target.target_dir = 'example.com'
  target.credentials = {
    aws_access_key_id: ENV["AWS_ACCESS_KEY_ID"],
    aws_secret_access_key: ENV["AWS_SECRET_ACCESS_KEY"]
  }
end


Setting month tracker for habit streaks done in Tasks plugin

I've been cracking my brain trying to set this one up, but I can't quite do it so I'm asking for a suggestion on how to implement this or as a feature if it's not possible at the current version of the plugin.
I want to setup a month tracker to display the streak of a recurring task within a single note, with the x dataset being pulled from each recurrence's done date and the y dataset as true or false. An added bonus would be displaying whether or not a task's done date corresponds to it's due date.
To set up a habit task, I'm using the Tasks plugin to create a recurring task within a file named after a habit item. For instance, here's how a habit note looks like in my vault:

title: Practice drawing
tags: [" #habits "]
type: habit

[!info]- Data
Related: [[Drawing]

History:

[ ] #action Practice drawing #habit 🔁 every day when done 🛫 2023-03-12
[x] #action Practice drawing #habit 🔁 every day when done 🛫 2023-03-11 ✅ 2023-03-11
[x] #action Practice drawing #habit 🔁 every day when done 🛫 2023-03-10 ✅ 2023-03-10
[x] #action Practice drawing #habit 🔁 every day when done 🛫 2023-03-06 ✅ 2023-03-09

The done dates are signaled by the ✅ emoji.
I would share my attempts if I hadn't erased them out of frustration, so I'm posting this as an open question to see if someone has tried to setup a similar tracking in their vaults.
Thank you in advance for sharing your thoughts on this!

Well, that is very much desired feature for me as well.
So far, only tried to use this kind of construction to parse the date from the specific task:
searchType: task.done, text
searchTarget: 'text #test 🔁 every day 📅 (?<value>([0-9]{4})-([0-9]{2})-([0-9]{2})), dataviewTarget'
xDataset: 0
folder: Задачи/Привычки
line:
    title: Dataview Inline Field
    fillGap: true

For this set of tasks hoarded in the note:
- [ ] text #test 🔁 every day 📅 2023-08-15
- [x] text #test 🔁 every day 📅 2023-08-14 ✅ 2023-08-13
- [x] text #test 🔁 every day 📅 2023-08-13 ✅ 2023-08-13

But it only seems to grab THE FIRST OCCURENCE IN THE FILE only. Hence the screenshots (p.s. random title is because the code is taken from example):

@pyrochlore is there any way to make the plug-in look for all of the occurrences in the file? Then it’s probably gonna solve this case


Windows pods fail - netplugin failed

Is this an ISSUE or FEATURE REQUEST? (choose one):
Issue
What version of acs-engine?:

  Warning  FailedCreatePodSandBox  24s (x1400 over 2h)  kubelet, 13192k8s9000  Failed create pod sandbox: rpc error: code = Unknown desc = NetworkPlugin cn
i failed to set up pod "fabrikamfiber.web-5b796445f8-5ncgs_plang1" network: netplugin failed but error parsing its diagnostic message "": unexpected end of
 JSON input

What you expected to happen:
Pod should start
How to reproduce it (as minimally and precisely as possible):
kubectl apply -f https://raw.githubusercontent.com/PatrickLang/fabrikamfiber/ocpdemo/k8s/db-deployment.yaml
Anything else we need to know:
Here's the orchestrator version & pool properties I used
{
  "apiVersion": "vlabs",
  "properties": {
    "orchestratorProfile": {
      "orchestratorType": "Kubernetes",
      "orchestratorVersion": "1.10.1"
    },
    "masterProfile": {
      "count": 1,
      "dnsPrefix": "...",
      "vmSize": "Standard_D2_v2"
    },
    "agentPoolProfiles": [
      {
        "name": "windowspool2",
        "count": 2,
        "vmSize": "Standard_D2_v3",
        "availabilityProfile": "AvailabilitySet",
        "osType": "Windows",
        "osDiskSizeGB": 127
      }
    ],
...

Let us take a look. @saiyan86

@PatrickLang After k8s fixes https://github.com/kubernetes/kubernetes/issues/60884, #2884 should fix this issue.

Thanks @saiyan86
@PatrickLang please try to use k8s 1.8.12 that we have tested and works.


Changeset specification is ignored

According to the documentation the register_resource block should support the specification of custom changeset functions, defined on the model, for the update and create action.
But this configuration seems to be ignored. Even specifying custom functions, ex_admin falls back to the default changeset function.
This feature was introduced by https://github.com/smpallen99/ex_admin/pull/36
As commented on the pull request the feature does not have a test associated.

+1

Looks like this has been addressed and should be closed?

Agreed! @smpallen99 :)
(Might help if someone else had contributor status...)

Is there any update on this?  I'm still seeing the issue.  I've had it work in the past but it has not worked for a while (I'm pulling from master).

@bsidoruk It definitely was working, so it might be a regression if it's not working now.  Can you create a repro in a sample app?


Fatal error: How can we receive a read, if the connection is closed

Describe the bug
Getting a fatal error bug when connected to neon postgresQL.
To Reproduce
Neon (https://neon.tech) is a fully managed postgresQL service. The following simple code produces this fatal error and crashes when connected to Neon, it doesn't crash when connected to a locally hosted db. Neon uses some new connection options which apparently Postgres-nio doesn't handle well.
The code:
let config = PostgresConnection.Configuration(
    host: "<your neon host>",
    port: 5432,
    username: "<username>",
    password: "<password>",
    database: "neondb",
    tls: .require(try NIOSSLContext(configuration: TLSConfiguration.makeClientConfiguration()))
  )

  let connection = try await PostgresConnection.connect(
    configuration: config,
    id: 1,
    logger: Logger(label: "log")
  )

  try await connection.close() // <- here it crashes with above Fatal error: How can we receive a read, if the connection is closed

Expected behavior
The connection should close cleanly.
Environment
• So far was only able re reproduce when connected to Neon.

Any OS, Mac or Linux.
You can register on neon for free and receive a free account to test this on.

@gshaviv can you help us repro the issue by creating a logger with log level trace? Then please post the logs here...

 For debugging details, use `String(reflecting: error)`.  Works fine, no more error. Thanks.


Laravel Updater

This pull request includes updates for the recent minor version release of Laravel as well as updates to your package dependencies. Feel free to commit any additional changes to the shift-ci-v7.22.2 branch.
Before merging, you need to:

Checkout the shift-ci-v7.22.2 branch
Review all pull request comments for additional changes
Run composer update
Test your application (no tests?)

:warning: You are running version 5.3.4 of guzzlehttp/guzzle. The latest version is 7.0.1. You should review this dependency to see if you can upgrade to the latest version.

:information_source: You are running an older version of Laravel. The latest version is 7.22.4. Run the Laravel 7.x Shift to upgrade to the latest version of Laravel.

:warning: You are running version 1.0.10 of laravel/tinker. The latest version is 2.4.1. You should review this dependency to see if you can upgrade to the latest version.

:warning: You are running version 3.9.3 of ramsey/uuid. The latest version is 4.0.1. You should review this dependency to see if you can upgrade to the latest version.

:warning: You are running version 0.14.0 of league/fractal. The latest version is 0.19.2. You should review this dependency to see if you can upgrade to the latest version.


pkgs/misc/cups/drivers: init brother dcpl2550dw at 4.0.0-1

Description of changes
This adds the printer driver for the Brother DCPL2550DW.
It combines the cups-wrapper and the driver in one file which allows
sharing common variables.
Things done
Currently using these packages on my laptop.

Built on platform(s)

[x] 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.11 Release Notes (or backporting 23.11 and 24.05 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

[x] Fits CONTRIBUTING.md.

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

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4292

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

2 packages built:

dcpl2550dw-cupswrapper
dcpl2550dw-drv

Review per https://github.com/NixOS/nixpkgs/blob/b59dfac3c65d7ccc12426527553c9250cb71e90a/pkgs/README.md#new-packages
Thanks for your contribution to nixpkgs!
Reviewed points

[x] package path fits guidelines: seems ok if moving to by-name is not an option (see below)
[x] package name fits guidelines
[x] package version fits guidelines
[x] package builds on x86-64
[ ] executables tested on ARCHITECTURE (not tested)
[x] meta.description is set and fits guidelines
[ ] meta.license fits upstream license: no
[x] meta.platforms is set
[x] meta.maintainers is set
[ ] meta.mainProgram is set, if applicable.
[x] build time only dependencies are declared in nativeBuildInputs
[x] source is fetched using the appropriate function
[x] the list of phases is not overridden
[x] when a phase (like installPhase) is overridden it starts with runHook preInstall and ends with runHook postInstall.
[x] patches have a comment describing either the upstream URL or a reason why the patch wasn't upstreamed
[x] patches that are remotely available are fetched rather than vendored

Possible improvements

I suggest to resolve most of the constant values (like model and MODEL) as they probably never change within this derivation.  The few that might change (like version) can be defined inside the mkDerviation attribute set and then be referenced by a finalAttrs recursion (you can find examples for the finalAttrs pattern in other derivations in nixpkgs).

In the driver output, there is a broken symlink in etc.  That's probably a typo where this symlink is created.

The gpl2 license is deprecated (some info here: https://github.com/NixOS/nixpkgs/pull/305036 ).  The paperconfigml2 and lpdwrapper files in the source archive state ...either version 2 of the License, or (at your option) any later version.  So it would be gpl2Plus.

The installPhase of the cupswrapper should be indented.

There are some message in the build log that might need attention:

Can the error dpkg-deb: error: --extract needs a target directory. from the build log be resolved?  Maybe the unpackCmd isn't necessary at all, as the dpkg setuphook takes care of unpacking the archive.
'--replace' is deprecated, use --replace-{fail,warn,quiet}. for substituteInPlace.

There is currently a movement to move away from sha256="..." hashes to hash="sha256-..." SRI hashes: https://github.com/NixOS/nixpkgs/issues/325892 .  It might be more future-proof to use an SRI hash.

Comments

Are you sure that both derivations are independent of each other?  The file opt/brother/Printers/DCPL2550DW/cupswrapper/.lpdwrapper-wrapped in the cupswrapper references brprintconflsr3 and lpdfilter and apparently attempts to execute these files as binaries.  The driver drivation has executable files with these names, which makes me think that cupswrapper needs driver.
In that case, the lpdwrapper should be patched so it can find those files, which also makes driver a runtime dependency of cupswrapper.  And with this constellation, and given that both derivations already share a lot of build code, it might be better to create one derivation.  This would shorten the build recipe a lot.  Then you should also move it to by-name.  If there is a realistic scenario where one would need the driver, but not the cupswrapper, this derivation could also be structured as a multi-output derivation.

I don't know how to use this package (I also don't have the hardware, but even then I probably wouldn't now).  I suggest to add some infos, either as comment in the build recipe file, or in meta.longDescription.

This looks really good now.  I tested it (not with real hardware, but by printing into a file), and the ppd file and the filter produce data without error.


Dashboard redesign - 4 cards with action buttons below instead on top

Move periods after seizures, before medicaments
Medicaments - compacted list (one line name & doses)
Other improvements:

Dashboard in case of no medicaments place link or button to add some
Dashboard in case of no seizures place link or button to add some

Update screens on doc

Already done


feat: :lipstick: Children links render as dropdown menus in header.

Also support for WP css classes

Any thoughts on pros/cons of using bootstrap dropdowns and popper?
https://getbootstrap.com/docs/5.1/components/dropdowns/
We tend not to use their components, but it could save on a little CSS and give us some functionality like edge detection.


Switching the keyboard language makes you unable to type in any textbox

Type some stuff in any textbox
Switch language (no matter how many times) (using Win + Space)
You can't type anymore (switching back doesn't help)

Tested on Win 10 1903 (buld 18362.145) with English/Russian languages.

Also hitting this.
Only reproduces if you switch using Win+Space. Click on task bar switches successfully.

Tested with #3013, SDL does not have this issue.

Seems to have regressed in 2020.609.0, probably in https://github.com/ppy/osu-framework/pull/3494.

This is an issues with SDL: https://github.com/libsdl-org/SDL/issues/4369

This issue is fixed in SDL with commit https://github.com/libsdl-org/SDL/commit/3b85e3fdfce01c528a6ebf9ac537bdc106ba4963


Can you provide an example of C #'s fixcr3?

Thank you.

can i get your discord？

You can add me : Conditions


Discuss Iterator trait implications for allocations?

Specifically how Iterator::size_hint() and ExactSizeIterator might affect Vec or HashMap growth. Also, how combinators like filter() or map() effect this.

I don't know anything about this topic. Can you explain some more? Would this go in the Heap Allocation chapter?

Yes, I think it would go in the Heap Allocation chapter.
The way I understand it, the size_hint() method on Iterator helps code downstream of an Iterator to make larger allocations in advance according to the expected size of the iterator. This is particularly relevant for the FromIterator trait (and thus the Iterator::collect() method as well as the Extend trait and its implementers, where it can matter substantially to do one large allocation vs many increasingly larger ones as the iterator is emptied. Whereas Iterator::size_hint() gives an approximation, implementing the ExactSizeIterator basically gives callers a way to get the exact size of the iterator. Iterator combinators like map() should then preserve the size_hint()/len() information, while filter() or filter_map() would obviously not be able to.
Does that help?
Also, while giving feedback I neglected to mention that I think this is a very cool resource, thanks for bundling all this knowledge (and for your invaluable work on rustc performance and writing it up, of course)!

Thanks for the explanation. It could have gone in the Heap Allocations chapter, but the Iterators chapter already has stuff about collect and extend so I ended up putting it there.


Refactoring: Move resources from the 'App.xaml' file to separate '*.xaml' resource dictionaries files (in 'Styles' namespace)

Fixed by 2b2c49e commit


How to make a Collapsible row

https://github.com/user-attachments/assets/91e8b9af-f389-49ff-9019-a37cb6833561

How create a collapsible row as per the video and photo's.
High priority issue. please let me know the solution.
Thank you

Hello. It is not possible right now. I can start developing a solution because its a good feature, but currently it not possible.

Hey, Thank you for the update. I appreciate your willingness to develop a solution for the collapsible row feature.
We currently depend on this package for our project, and having this feature would be incredibly beneficial. If it becomes available soon, it would be fantastic and would greatly enhance our project and will be really helpful for others too.
I also want to mention that all other features of the package are excellent and have been very valuable to us.
Looking forward to your solution.
Thank you

I'll start writing code asap. I don't guarantee you nothing but maybe for the next week it will be available as a preview

Hi Tomas,
Thank you very much for your prompt response and for beginning work on the collapsible row feature. I sincerely appreciate your efforts and dedication to improving the package.
While I understand that nothing is guaranteed, having a preview by next week would be greatly appreciated and would be a wonderful addition to our project.
If there’s any way I can support you in this process or if you need any additional information, please feel free to let me know. May your work be blessed with success.
Thank you once again for your help.

Hey Thomas, Have any updates?

Working on this

Thanks!

@itsfahiz if you configure the paged_datatable dep in pubspec.yaml to use the feat/expandable-rows branch you can test the feature. It is incomplete and there is a lot to improve and document, but you can play around with that. If you want to implement collapsible/expansible rows, you have to use the PagedDataTable.expansible constructor and update the fetcher.

I am going to close this because the feature is already implemented in dev branch. I am creating a pre-release later on pub.dev.


logs warnigs from HA Core 2024.7.0b0 - async_forward_entry_setup

hello
Updated to 2024.7.0b0 and received some warnings for your interest.
Cheers
thanks for the integration
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:151
First occurred: 9:22:25 AM (6 occurrences)
Last logged: 9:22:30 AM

Detected code that calls async_forward_entry_setup for integration gasbuddy with title: costco_e_sw and entry_id: f0aa7b63d8abfc7caf5609b84d573917, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.
Detected code that calls async_forward_entry_setup for integration gasbuddy with title: costco_e_west and entry_id: c57df6ccb0676a6f14d9a8f56d6e2360, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.

Fixed in 1.0.8


Added info about the supported platforms

Added short info about the supported platform. For people who have very slow internet will be able to get the right info fast as they do not need to weight for the snackbar to load

Deploy preview for react-native ready!
Built with commit 9c56e9eba21eb652b665201d3f0d2d10e7a98a8d
https://deploy-preview-2260--react-native.netlify.app

Hi @vijaybaliah, unfortunately web is one of out-of-three platform so we do not include the documentation related to the in the React Native website.
You can find (and improve) the react-native-web under this URL - https://necolas.github.io/react-native-web/docs/ - and the core React Native compatibility on the web platform here - https://github.com/necolas/react-native-web#compatibility-with-react-native.


fix/issue46

Resolves ✅ :

[x] #46

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

Chrome Web Store
GitHub release

Your semantic-release bot :package::rocket:


Finally setup on Kubernetes

Closes #51, #10

The deployment stuff looks good, does it fix #51 though? Don't seem to see any changes in that service in the commit history


Descope less relevant unit tests from unified build variants

Problem
gn_build.sh runs all tests with MbedTLS + OpenSSL. We've recently added
BoringSSL and doing a full test run across all crypto backends will be costlier
than justified by the coverage increase.
The ultimate goal is to run the CryptoPAL test with BoringSSL from
gn_build.sh.
Change overview
Switch to more targeted testing of just crypto oriented tests for the
MbedTLS build and just tests that need the fake platform for the fake
platform build.
This reduces the blowup in execution time from running the cartesian
product of configs x tests and saves about 30% of default work done by
gn_build.sh.
Testing
gn_build.sh

@mspang could you help here please?


Respect Do Not Track, don't load Google Analytics

The Do Not Track preference is a clear request from a user not to be tracked. We can respect these users' choice of privacy by turning off Google Analytics if that preference is set.
https://www.paulfurley.com/google-analytics-do-not-track/

Thanks @jtemporal !


Intermittent "401 Unauthorized" failures from Chef server using Chef client

We're seeing intermittent "401 Unauthorized" responses from the open source Chef server. These appear to be random events, but seem to occur when performing data bag searches (though that is by far our most common type of search, so other types may also have issues).
We've been having this issue for a long time through multiple Chef server and client upgrades. Our current versions are:

Chef server: 12.9.1
Chef client: 12.14.89

Before you dismiss this as a duplicate of #5, this is happening with the normal Chef client, not the chef-api gem.
Looking at the crash.log file for opscode-erchef doesn't reveal any additional information:
$ grep status=401 crash.log -B1
2016-10-13 17:43:32 =ERROR REPORT====
{<<"method=GET; path=/organizations/brigade/data/datadog/credentials; status=401; ">>,"Unauthorized"}
--
2016-10-13 17:47:57 =ERROR REPORT====
{<<"method=GET; path=/organizations/brigade/data/users/ambari; status=401; ">>,"Unauthorized"}
--
2016-10-13 18:08:08 =ERROR REPORT====
{<<"method=GET; path=/organizations/brigade/data/users/beanstalkd; status=401; ">>,"Unauthorized"}
--
2016-10-13 18:38:21 =ERROR REPORT====
{<<"method=GET; path=/organizations/brigade/data/users/gerrit; status=401; ">>,"Unauthorized"}
2016-10-13 18:38:21 =ERROR REPORT====
{<<"method=GET; path=/organizations/brigade/data/users/kibanna; status=401; ">>,"Unauthorized"}
2016-10-13 18:38:21 =ERROR REPORT====
{<<"method=GET; path=/organizations/brigade/data/users/solr; status=401; ">>,"Unauthorized"}

Here's an example of the stack trace on the Chef client side (though less useful since the problem is server-side):
Net::HTTPServerException: 401 "Unauthorized"
  from net/http/response.rb:120:in `error!'
  from chef/http.rb:150:in `request'
  from chef/http.rb:115:in `get'
  from chef/data_bag_item.rb:155:in `load'
  from chef/dsl/data_query.rb:62:in `data_bag_item'
  from /var/chef/cache/cookbooks/base/recipes/_sudo.rb:7:in `block in from_file'
  from /var/chef/cache/cookbooks/base/recipes/_sudo.rb:6:in `each'
  from /var/chef/cache/cookbooks/base/recipes/_sudo.rb:6:in `from_file'
  from chef/mixin/from_file.rb:30:in `instance_eval'
  from chef/mixin/from_file.rb:30:in `from_file'
  from chef/cookbook_version.rb:233:in `load_recipe'
  from chef/run_context.rb:327:in `load_recipe'
  from chef/run_context.rb:283:in `block in include_recipe'
  from chef/run_context.rb:282:in `each'
  from chef/run_context.rb:282:in `include_recipe'
  from chef/dsl/include_recipe.rb:26:in `include_recipe'
  from /var/chef/cache/cookbooks/base/recipes/default.rb:23:in `from_file'
  from chef/mixin/from_file.rb:30:in `instance_eval'
  from chef/mixin/from_file.rb:30:in `from_file'
  from chef/cookbook_version.rb:233:in `load_recipe'
  from chef/run_context.rb:327:in `load_recipe'
  from chef/run_context/cookbook_compiler.rb:141:in `block in compile_recipes'
  from chef/run_context/cookbook_compiler.rb:138:in `each'
  from chef/run_context/cookbook_compiler.rb:138:in `compile_recipes'
  from chef/run_context/cookbook_compiler.rb:75:in `compile'
  from chef/run_context.rb:176:in `load'
  from chef/policy_builder/expand_node_object.rb:97:in `setup_run_context'
  from chef/client.rb:510:in `setup_run_context'
  from chef/client.rb:280:in `run'
  from chef/application.rb:302:in `block in fork_chef_client'
  from chef/application.rb:290:in `fork'
  from chef/application.rb:290:in `fork_chef_client'
  from chef/application.rb:255:in `block in run_chef_client'
  from chef/local_mode.rb:44:in `with_server_connectivity'
  from chef/application.rb:243:in `run_chef_client'
  from chef/application/client.rb:464:in `sleep_then_run_chef_client'
  from chef/application/client.rb:451:in `block in interval_run_chef_client'
  from chef/application/client.rb:450:in `loop'
  from chef/application/client.rb:450:in `interval_run_chef_client'
  from chef/application/client.rb:434:in `run_application'
  from chef/application.rb:60:in `run'
  from /opt/chef/embedded/lib/ruby/gems/2.3.0/gems/chef-12.14.89/bin/chef-client:26:in `<top (required)>'
  from /usr/bin/chef-client:54:in `load'
  from /usr/bin/chef-client:54:in `<main>'

We've intentionally rebuilt our entire Chef server from scratch with the hope that this would fix the problem, to no avail.
What additional information can we provide to help you debug this issue?

Do the same requests fail consistently from the same clients/users?

No, there does not appear to be a clear pattern here. I just checked our Sentry logs, and there's a long tail of nodes that account for 2-5% of errors in the last 7 days. No obvious pattern there.

Okay, thanks. Could you post a segment of hte chef-server request log that shows a couple-few of these? You can find it in /var/opt/chef-server/opscode-erchef/request*

Happy to! Do you mind if I email you a link to a secret gist? Would prefer to not post information in the open, if possible.

Sent you a private gist to your email. Let me know if there's anything else I can provide!

Thanks, I got that.
The first thing that jumps out is that the requests are failing with the message bad_clock - that is intended to mean "your chef client provided a request timestamp that is too old" - 900s or more behind current server time.
That seems like it would produce a lot more of these errors though, though hovering  right on that 900s border would explain the intermittent nature.  I don't thikn this is the case, but could you verify that the nodes are in sync time-wise with the chef server?
Beyond that, would it be possible to enable chef client debug logging on a few nodes? It would give us a lot more information to work with if we could see the exact request that chef-client is sending.
Final question - do your logs show any occurrences of this in endpoints other that data bags or search?

One quick thing I've noticed which I didn't before: all of the nodes which experience this problem are in a specific Chef environment (production). I apologize for not noticing this before. This suggests some sort of difference in configuration that is reproducible, so I'm going to investigate that separately (though I'm pretty sure we don't have different Chef client configurations between production and our other environments).
In regards to your questions:
Our servers clocks are all synced with NTP, but I verified by comparing each node's clock against the Chef server's clock:
knife ssh "*:*" 'expr $(date +%s) - $(ssh chef.brigade.com date +%s)' -C32

None of the hosts had more than a couple of seconds of clock skew from the Chef server.
I've also verified that they are all running in the same time zone (UTC):
knife ssh "*:*" 'date +%Z' -C32

I'll turn on debug-level logging for a sizable subset of our production nodes so that when this happens again we can hopefully catch the problematic request.
All the 401s we see are the result of data bag searches (although as I mentioned above, that is the most common kind of search we use by far, so it's possible that the problem may not be specific to data bags, but searches of all kinds). The logs unfortunately don't go back far enough for me to be certain, but the evidence we have for the last week is compelling.
Thanks for your help so far! I'll keep digging in to what's different about our production nodes, and report back if we can catch the logs on the client side when this error occurs.

False alarm with respect to this only occurring in the production Chef environment: turns out we were only reporting errors to Sentry for the production environment, hence the discrepancy.
I'll report back once we've got logs for a request on the Chef client side.

Ok, I see what's happening here.
Upon further investigation: these errors do not occur with perfectly random distribution. They appeared to, but this was for a reason we'll see shortly.
We backup our Chef server on a daily basis by running chef-server-ctl backup on the server. This requires a short period of downtime during which the server is unavailable. This is fine, since the Chef client retries HTTP requests when the server is unreachable.
Here is a relevant section of logs where a 401 Unauthorized request was returned:
[2016-10-15T17:00:16+00:00] ERROR: Connection refused connecting to https://chef.brigade.com/organizations/brigade/data/certificates/staging, retry 2/12
[2016-10-15T17:00:21+00:00] ERROR: Connection refused connecting to https://chef.brigade.com/organizations/brigade/data/certificates/staging, retry 3/12
[2016-10-15T17:00:26+00:00] ERROR: Connection refused connecting to https://chef.brigade.com/organizations/brigade/data/certificates/staging, retry 4/12
[2016-10-15T17:00:31+00:00] ERROR: Connection refused connecting to https://chef.brigade.com/organizations/brigade/data/certificates/staging, retry 5/12
[2016-10-15T17:00:36+00:00] ERROR: Connection refused connecting to https://chef.brigade.com/organizations/brigade/data/certificates/staging, retry 6/12
[2016-10-15T17:00:41+00:00] ERROR: Connection refused connecting to https://chef.brigade.com/organizations/brigade/data/certificates/staging, retry 7/12
[2016-10-15T17:00:46+00:00] ERROR: Connection refused connecting to https://chef.brigade.com/organizations/brigade/data/certificates/staging, retry 8/12
[2016-10-15T17:00:51+00:00] ERROR: Connection refused connecting to https://chef.brigade.com/organizations/brigade/data/certificates/staging, retry 9/12
[2016-10-15T17:00:56+00:00] ERROR: Server returned error 503 for https://chef.brigade.com/organizations/brigade/data/certificates/staging, retrying 10/12 in 1732s
[2016-10-15T17:29:48+00:00] INFO: HTTP Request Returned 401 Unauthorized: error
certificate_pem[/config/staging.pem] action create (1777.148678337s) FAILED: 401 "Unauthorized"

Here we see for the first 9 tries, the Chef client can't even open a connection due to the downtime caused by the backup. The current code has it retrying every http_retry_delay seconds in this case (5 by default) up to http_retry_count times (5 by default, but we've set ours to 12 because of the backup downtime), which is why we get up to 9 tries rather quickly:
      rescue Errno::ECONNREFUSED
        if http_retry_count - http_attempts + 1 > 0
          Chef::Log.error("Connection refused connecting to #{url}, retry #{http_attempts}/#{http_retry_count}")
          sleep(http_retry_delay)
          retry
        end

Unfortunately, this means that once the nginx server comes back up, it's possible that other backend services on the server are not up yet, so while the connection is opened the request itself will 503, whose retry logic is handled differently:
          if response.kind_of?(Net::HTTPServerError) && !Chef::Config.local_mode
            if http_retry_count - http_attempts + 1 > 0
              sleep_time = 1 + (2**http_attempts) + rand(2**http_attempts)
              Chef::Log.error("Server returned error #{response.code} for #{url}, retrying #{http_attempts}/#{http_retry_count} in #{sleep_time}s")
              sleep(sleep_time)
              redo
            end
          end

Since this is the 10th try, we now sleep 2^10 = 1024 seconds + a random range between 1 and 1024. This is why these events appeared random, as the retried request could have happened anywhere from 17 to 34 minutes, or an even wider range depending on the number of times we failed to open the initial connection.
The reason the final request 401s is because the authorization headers are generated at the very beginning of this retry process, with the same headers used on each retry. If you exceed 900 seconds of retry delay you'll have headers that are out-of-date.
In summary: this is not a problem with the Chef server, but the Chef client. I'll open a pull request with the Chef client project, as from my cursory understanding we can easily avoid this problem by regenerating the headers before each retry. There may be a technical reason why they are generated once at the beginning, but I'll open a pull request and see what you think.
Thanks for you help on this, @marcparadise!

I should add that a simple workaround if this pull request isn't acceptable is to increase your http_retry_delay so that you rack up fewer retries before hitting the 503.

@sds thanks for continuing to dig in, and for the PR - good find!

Closing since the pull request was merged in the Chef client project.


Header logo static icon is not correct in the component

Describe the bug
DXC logo static icons - "dxc_logo_white.png" and "dxc_logo_white.png" are not correct
To Reproduce
Use halstack angular library and define dxc-header component. Incorrect logo comes
Example:
https://developer.dxc.com/tools/angular/2/#/components/header
Expected behavior
Header icon should be correct per the guideline
Screenshots

Additional context
Add any other context about the problem here.
Add labels
Add any applicable label like the concerned components or the target version of the fwk where the bug has been found.

@mawelCaballero please look into this issue

It has been fixed in release 3.0.0
Issue can be closed.


[SLAM] Support control interfaces - restart

Support restart tracking, the camera pose will be reset.
Only related to tracking, no configuration change.

we will not support this interface any more. Would you please close it?

Got it, closing this issue.


Bugsnag: undefined is not an object (evaluating 'this.props.runWithLoadingIndicator')

Error in mSupply Mobile
TypeError in index.android.bundle:660
undefined is not an object (evaluating 'this.props.runWithLoadingIndicator')
View on Bugsnag
Stacktrace
index.android.bundle:660 - value

View full stacktrace
Created automatically via Bugsnag

Fixed in #553


Emphasize that the bar script must be a forking kind

I was wondering for bit what was the problem with my dwm freezing as launch until I realized my non-forking lemonbar script blocked the dwm from proceeding. Though it's mentioned that it's supposed to be a launching script, it still leaves it a bit vague. It wouldn't hurt to emphasize it, especially for the non-native english speakers.

That's a good idea, I added it to the README. See commit 2c5b856.


[image_picker] Image picker android is updating Kotlin on a minor release

I’m facing an issue with image_picker, image picker started to use there plugin code as dependency. But it’s always upgrading just the minor and using minor auto update (^) so any image_picker version always get the last image_picker_android even with different Kotlin versions. Basically image_picker_android upgraded the kotlin on minor 0.8.6+15 to 1.8.x so to use a different kotlin version I need to dependency override 0.8.6+14 that has not the Kotlin 1.8 version.
image_picker is publishing versions with sub packages ^0.8.5 than ^0.8.6 what’s do not makes sense, because even downgrading image_picker it'll not downgrade image_picker_android, just with dependency override.
v0.8.6+14
v0.8.6+15 - on line 47
We are using image_picker in a flutter module project that is embedded on a android application with Kotlin 1.7.x.

Please don't ignore the issue template when filling issues; the structure there exists for a reason. As I said in both the PR and Discord, we need details about steps to reproduce, failure logs (i.e., what exactly is the output when you try to build with the latest version), etc.
I'm going to close this as it's missing almost all of the information needed to be actionable, and trying to address that without the template will be difficult. Please file a new issue using the relevant issue template, and fill it out completely.

@stuartmorgan Sorry, I just clicked the link you sent on the doc. It opened without template, now I saw the form. 😞

Sorry, I just clicked the link you sent. On the doc it opened without template

Oops, I'll fix that in the packages repo README. Sorry about that!


Typo in Field Name in Example Configuration

Hello,
I noticed a typo in the example configuration file config/examples/vmcluster_with_service_override.yaml. According to the VictoriaMetrics Operator API documentation, the field name should be useAsDefault instead of userAsDefault.
Could you please update the example to reflect the correct field name?
Thank you!

Issue was fixed at linked PR


Fix FAST stages to support multi-tenant resman

The FAST stage 1-resman fails in a tenant for multiple reasons:

it tries to create top level folders with the organization as parent instead of the local.root_node
it uses the tag "project-factory" without creating it (it's done correctly without multi-tenancy)
the stage 1-tenant-factory generates 0-bootstrap.auto.tfvars.json without some data required by 1-resman

Checklist

I applicable, I acknowledge that I have:

[X] Read the contributing guide
[X] Ran terraform fmt on all modified files
[X] Regenerated the relevant README.md files using tools/tfdoc.py
[ ] Made sure all relevant tests pass

@ZZelle can you check the linting issues and sign the CLA?


Upstream changes and/or convert to composite action

As mentioned here, this action could potentially be simplified by converting it into a composite action. Also, it would be nice to have flake support in the upstream repo, since it looks like I'm not the only one who needs this.

Any chance you merge this repo with upstream?


Extension Objects Not Visible in Business Central

I have just published an extension to Dynamics 365 Business Central using Visual Code which reported a successful installation. My startup object loads and everything seems normal. I then search for one of the new pages but it does not appear in the search. Extension Management it shows my extension as installed. I have placed the following tags on the pages:
page 50017 "Driver List"
{
PageType = List;
SourceTable = Drivers;
UsageCategory = Lists;
I am using the latest version of AL (0.15.18771) and am installing to a Sandbox version of Business Central. This same code works when publishing to my local NAV Server (using the correct version of AL). This is the first time I have published to Business Central. The only difference between the two is that I just installed the new version of AL. Any help would be appreciated. Thanks!

Hi @tlbakken, can you also try adding ApplicationArea = All to your page?

Hi @qutreson, thank you for helping. I added that property and the pages now appear but with odd behavior. None of the fields appear on the page. After looking further I noticed that my page extension fields are not visible either.

@tlbakken, you need also to specify the application area property to the fields on your page otherwise they are not visible.
The application area property is a feature that enables to display elements only for some defined users and hide it for some others. By specifying ApplicationArea = All, the page or field is then visible by all users.
You can read more about the application area property here: ApplicationArea Property.
You can also read Extending Application Areas and Adding Pages and Reports to Search


Adding swagger spec for RecoveryServices.SiteRecovery service.

Adding swagger spec for RecoveryServices.SiteRecovery service (2016-08-10).
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

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

Quality of Swagger

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

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

@avneeshrai,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Note for the reviewers:
This has already been reviewed in PR https://github.com/Azure/azure-rest-api-specs/pull/1016
I feel @veronicagg would be the best to review this PR as she already has context on it.

Validator tool shows following category of issues:
"code": "OperationsAPIImplementationValidation",
"code": "ProvidersPathValidation",
"code": "PutRequestResponseValidation",
"code": "TrackedResourceListByImmediateParent",
"code": "XmsExamplesProvidedValidation",
"code": "DeleteOperationNameValidation",
"code": "DefinitionsPropertiesNamesCamelCase",
"code": "PatchBodyParametersSchemaValidation",
"code": "BodyTopLevelProperties",
"code": "AvoidNestedProperties",
"code": "BooleanPropertyNotRecommended"

Except on "code": "OperationsAPIImplementationValidation" we had closed on all other issues in the current thread. About the implementation of operations API, we expect operations API for our provider Microsoft.RecoveryServices to be present in https://github.com/Azure/azure-rest-api-specs/blob/08f0f317ccb89b86f552232bd8fce02f98889463/arm-recoveryservices/2016-06-01/swagger/vaultusages.json spec (which is already there). Let me know if we have a reason to duplicate it here.
2.	Examples for 102 out of 109 APIs have been included in the PR. We couldn’t include examples for remaining 7 because of the issues mentioned below with the validator tool:

a)All Job related APIs
"ReplicationJobs_Get",
"ReplicationJobs_Resume",
"ReplicationJobs_GetTrackAsyncOperation",
"ReplicationJobs_Restart",
"ReplicationJobs_Cancel",
"ReplicationJobs_Export",
"ReplicationJobs_List"
Reason: Recursive call in ASRTask model

Error seen in validator tool:
error: Found errors in validating the response with statusCode "200" for x-ms-example "Gets the job details." in operation "ReplicationJobs_Get".:
{ code: 'RESPONSE_VALIDATION_ERROR',
message: 'Found errors in validating the response with statusCode "200" for x-ms-example "Gets the job details." in operation "ReplicationJobs_Get".',
innerErrors:
[ { code: 'INVALID_RESPONSE_BODY',
errors:
[ { code: undefined,
message: 'Maximum call stack size exceeded',
path: undefined } ],
message: 'Invalid body: Maximum call stack size exceeded',
path: [] } ] }

b)Many APIs
E.g.: ReplicationFabrics_Get

Fields having “null” value are not allowed.
Error seen in validator tool:
error: Found errors in validating the response with statusCode "200" for x-ms-example "Gets the details of a Site." in operation "ReplicationFabrics_Get".:
{ code: 'RESPONSE_VALIDATION_ERROR',
message: 'Found errors in validating the response with statusCode "200" for x-ms-example "Gets the details of a Site." in operation "ReplicationFabrics_Get".',
innerErrors:
[ { code: 'INVALID_RESPONSE_BODY',
errors:
[ { code: 'INVALID_TYPE',
params: [ 'string', 'null' ],
message: 'Expected type string but found type null',
path:
[ 'properties',
'rolloverEncryptionDetails',
'kekCertThumbprint' ],
description: 'Gets or sets the key encryption key certificate thumbprint.' },
{ code: 'INVALID_TYPE',
params: [ 'string', 'null' ],
message: 'Expected type string but found type null',
path: [ 'properties', 'encryptionDetails', 'kekCertThumbprint' ],
description: 'Gets or sets the key encryption key certificate thumbprint.' } ],
message: 'Invalid body: Value failed JSON Schema validation',
path: [] } ] }

c)Many APIs
Eg: ReplicationPolicies_Get
Polymorphic objects are not allowed, only discriminator field is getting accepted by validator.

Error in validator tool
error: Found errors in validating the response with statusCode "200" for x-ms-example "Gets the requested policy." in operation "ReplicationPolicies_Get".:
{ code: 'RESPONSE_VALIDATION_ERROR',
message: 'Found errors in validating the response with statusCode "200" for x-ms-example "Gets the requested policy." in operation "ReplicationPolicies_Get".',
innerErrors:
[ { code: 'INVALID_RESPONSE_BODY',
errors:
[ { code: 'OBJECT_ADDITIONAL_PROPERTIES',
params:
[ [ 'activeStorageAccountId',
'replicationInterval',
'applicationConsistentSnapshotFrequencyInHours',
'recoveryPointHistoryDurationInHours' ] ],
message: 'Additional properties not allowed: activeStorageAccountId,replicationInterval,applicationConsistentSnapshotFrequencyInHours,recoveryPointHistoryDurationInHours',
path: [ 'properties', 'providerSpecificDetails' ],
description: 'Hyper V Replica Azure provider specific settings.\r\n            Replicated item properties specific to the HyperVReplicaAzure replication provider.' } ],
message: 'Invalid body: Additional properties not allowed: activeStorageAccountId,replicationInterval,applicationConsistentSnapshotFrequencyInHours,recoveryPointHistoryDurationInHours',
path: [] } ] }
I have sent a mail to @veronicagg , @salameer with details on closures.

@dsgouda These projects are managed by separate teams just that the provider is same. For example you can see
https://github.com/Azure/azure-rest-api-specs/tree/master/arm-recoveryservices
and
https://github.com/Azure/azure-rest-api-specs/tree/master/arm-recoveryservicesbackup
are in different directories.

@dsgouda have added you to the mail thread.

@avneeshrai

Regarding OperationsAPIImplementation, adding Gaurav. @ravbhatnagar should this spec contain a duplicate of the operations API (the same provider has an operation here  https://github.com/Azure/azure-rest-api-specs/blob/08f0f317ccb89b86f552232bd8fce02f98889463/arm-recoveryservices/2016-06-01/swagger/vaultusages.json) ?
Examples should be included even though there are failures reported for some of them (unless it completely blocks the use of the tool for the rest - like a critical exceptions). For failures that are known or new tool bugs, we would ignore the failure for now and should go away once the bug gets fixed.
a) Regarding "Maximum call stack size exceeded" issue, could you please open an issue for it at https://github.com/Azure/oav/issues (I don't think it's a known failure)
b) You should leave the examples in, we'll ignore the failures for now
c) are you seeing the polymorphic problem in the latest version of the tool? We fixed polymorphic types quite a bit, so I'd be curious to see the specific problem if you're using the latest. If so, please log an issue at https://github.com/Azure/oav/issues for us to take a look.
The examples are not only used for validation but also for documentation purposes.

Is this version of the service already deployed to ARM?
Regarding linter validation errors, our tool has been updated since the time of our last conversation, please review the following:

Consider flattening: https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L2491
(and other locations for warning AvoidNestedProperties)
The following are currently detected as RPC violations - @ravbhatnagar for review as well.
Error at https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1975
Error https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1963
https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1952
https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1939
https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1927
https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1915
... please look at the other camel casing violations as well.
PutRequestResponseValidation https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1340
PutRequestResponseValidation https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1328
... and others on this category.

@veronicagg
About examples:

We have added the support of examples in 7 missing APIs as you suggested (which are failing in validator with Max Call Stack Size Exceeded message as explained before)
We are still hitting all the three issues mentioned above in examples even after updating validator tool (oav):
a) Max Call Stack Size Exceeded for responses with recursive references.
b) Null values for string fields are not supported. Fails with message message: 'Expected type string but found type null'
c) Polymorphic fields are not supported and validator fails with message: "Additional properties not allowed:"

I would raise the issues as you had suggested for these scenarios.

@veronicagg Please find inline responses in bolditalics for your queries.
Is this version of the service already deployed to ARM?
[AR] Yes, service version 2016-08-10 is already deployed to ARM.
Regarding linter validation errors, our tool has been updated since the time of our last conversation, please review the following:
[AR] We already have closure with exception from your end on all of the following issues. Please refer the email thread for details.
Consider flattening: https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L2491
(and other locations for warning AvoidNestedProperties)
The following are currently detected as RPC violations - @ravbhatnagar for review as well.
[AR] Why is this reported as RPCVoilation? It looks to be related to nested properties that we had decided to keep as it is.
Error at https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1975
Error https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1963
https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1952
https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1939
https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1927
https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1915
... please look at the other camel casing violations as well.
PutRequestResponseValidation https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1340
PutRequestResponseValidation https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1328
... and others on this category.

Raised issues for problems with examples stated above:
https://github.com/Azure/oav/issues/115
https://github.com/Azure/oav/issues/116
https://github.com/Azure/oav/issues/117

@avneeshrai Just to clarify, 1) the tools have been updated, so issues that may have been false positives before may not be now, so it's good to re-evaluate. 2) it's good to have this documented in this PR.
The flattening warning is not an RPC violations (I was referring to other ones above), and if you decided not to flatten those intentionally, it's ok. Because there are RPC violations reported, I've pulled in @ravbhatnagar in the PR review.

@veronicagg I get the reasons now. Thanks for clarifying :)

@veronicagg Addressed the comments.

@avneeshrai - Please fix the following issues too -

https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1977
All the extra properties should go inside the properties bag.
https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1207
Add the /operations API to the swagger.
https://travis-ci.org/Azure/azure-rest-api-specs/jobs/230461195#L1963
Patch should not have a required property. Consider fixing.
When you plan on fixing the camel casing violations?

@ravbhatnagar Taken all comments that we could. Please find the responses:

Moving extra properties inside the properties bag of 'Job' model, could not be taken because of the following reasons:
a) We had to introduce ['status,error,startTime,endTime'] properties at the top level of 'Job' because they were needed by Azure template tracking. While developing our APIs and using them through templates, templates looked for status field and other fields at the top level (absence let to failure).
This link explains the same: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-async-operations
b) Moreover, even if you suggest alternatives at this point for azure template tracking to work even after pushing these properties inside property bag we can take that only in our next service version (it being a breaking change).
c) Additional information, 'Job' is not an azure tracked resource.
Introduced operation API and corresponding example as suggested.
Fixed the issue with patch input as per suggestion.
We would be fixing all the camel casing violations in our next service version.

@veronicagg @ravbhatnagar I have responded to all the comments (fixing issues wherever possible).
Please let me know if there is any action item left on me.

@veronicagg Responded.

@avneeshrai - The following comment from you is not correct -
a) We had to introduce ['status,error,startTime,endTime'] properties at the top level of 'Job' because they were needed by Azure template tracking. While developing our APIs and using them through templates, templates looked for status field and other fields at the top level (absence let to failure).
This link explains the same: https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-async-operations
Firstly, POSTs cant be invoked from the template barring a few which are of the pattern list*. Secondly, if you are using the 202 pattern for async operations, the API should return a location header which is used to track the status of the operation. When invoked from template, the above location header is what will be used to poll for completion.
The above behavior is explained in the RPC. You do not need the above properties at the top level for the template to track the provisioning status.
This is a RPC violation. It does not matter if its a proxy resource. Please fix whenever you can. Till then you will be reported for this violation.

@ravbhatnagar Thanks for the response and explanation Gaurav. That was a gap in our understanding then. Would try taking this up whenever we come up with new service version for breaking changes.
@veronicagg As now we don't have any open actionable item left, can we have this PR merged please :)

No modification for Ruby

No modification for NodeJS

No modification for Python


Bad emote picker window scaling on 1280 x 1024 monitors (window too tall)

Describe the bug
when you click on the emote menu when you have chaterino at the top of the screen and click on the emote menu you can't move it until you rescale it
To Reproduce
https://streamable.com/5hso4
Expected behavior
to be able to move the emote menu
Screenshots
https://streamable.com/5hso4
Chatterino version
2.1.4
Additional context
just move it 4Head

Just so I don't go insane: Your screen is 1280x1024 without windows scaling. You have recorded the top right corner of your screen and then the video was upscaled to match 1280x1024 again. Is this correct?


Fix several links

Wrong links:

https://facebook.github.io/react-native/docs/virtualizedlist#ListItemComponent
https://facebook.github.io/react-native/docs/virtualizedlist#ListFooterComponentStyle
https://facebook.github.io/react-native/docs/virtualizedlist#ListHeaderComponentStyle
https://facebook.github.io/react-native/docs/virtualizedlist#persistentScrollbar

Thanks!


Proxy problem

Hi,
I've tried to use the module via a proxy, but it didn't work. After inspecting the code I noticed the following:
I use after importing and setting proxies:
msft = yf.Ticker("MSFT")
get stock info
msft.get_info(proxy=proxies)
In base.py
def get_info(self, proxy=None, as_dict=False, *args, **kwargs):
self._get_fundamentals(proxy)   #dvw this would fix it: self._get_fundamentals(proxy=proxy)
…
when you then go to that function
def _get_fundamentals(self, kind=None, proxy=None):
…
the proxy is not set correctly. I have put in comment the correction that works for me but I get errors later on then.
If you want to test it apart (no classes and for illustration), you can try this:
def get_fundamentals(kind=None, proxy=None):
print(f"proxy is {proxy}")
def get_info(proxy=None, as_dict=False, *args, **kwargs):
print(f"In get_info is proxy equal to {proxy}")
get_fundamentals(proxy)
# statement below corrects this
#get_fundamentals(proxy=proxy)
get_info(proxy='testProxy')

Hi everyone,
I agree with the previous post.
The "_get_fundamentals(proxy=proxy)" instead of "_get_fundamentals(proxy)" does the trick of extending yfinance use over proxies and correcting this bug. It should be extended to all _get_calendar, _get_earnings... functions in the base.py file which suffer the same problem.
I also hase to report that the use of pd.read_html in the _get_fundamentals (base.py) function declaration is not compatible with proxy use, but the following trick works fine :
holders = _pd.read_html(_requests.get(url=url, proxies=proxy).text).
Apart from these two corrections, yfinance is quite manageable through proxies.
Best,
Paul

Hi, sorry for the basic question, but how do you specify a proxy with yfinance? Do you just specify the proxy IP as a string? I tried this but it didn't work:
yf.download(
        tickers='AAPL',
        period='5d',
        interval='60d',
        proxy='<IP_ADDRESS>',
        auto_adjust=True
    )

Thanks!

Specifying the proxy with a string, like you do, should work just fine.
Your code works on my side with my own proxy string (removing your interval condition which does not allow 60d as a licit value, though).

@psabalot Thanks for the reply. The '60d' interval was a typo (apologies) but did not affect my code (which had it correctly specified and '60m'). I am using proxies from https://free-proxy-list.net/ and have tried several with my code above but it still generates an error. I have tested the proxies with requests.get() on other websites and they work fine. Am I maybe missing something in my yfinance installation (I used conda install -c ranaroussi yfinance)? Here is my error message in case you are able to decipher anything -- thanks!
Exception in thread Thread-16:
Traceback (most recent call last):
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/urllib3/connectionpool.py", line 662, in urlopen
    self._prepare_proxy(conn)
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/urllib3/connectionpool.py", line 948, in _prepare_proxy
    conn.connect()
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/urllib3/connection.py", line 308, in connect
    self._tunnel()
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/http/client.py", line 921, in _tunnel
    message.strip()))
OSError: Tunnel connection failed: 503 unknown method

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/urllib3/connectionpool.py", line 720, in urlopen
    method, url, error=e, _pool=self, _stacktrace=sys.exc_info()[2]
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/urllib3/util/retry.py", line 436, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='query1.finance.yahoo.com', port=443): Max retries exceeded with url: /v8/finance/chart/AAPL?range=5d&interval=1d&includePrePost=False&events=div%2Csplits (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 503 unknown method')))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/threading.py", line 926, in _bootstrap_inner
    self.run()
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/threading.py", line 870, in run
    self._target(*self._args, **self._kwargs)
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/multitasking/__init__.py", line 102, in _run_via_pool
    return callee(*args, **kwargs)
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/yfinance/multi.py", line 167, in _download_one_threaded
    actions, period, interval, prepost, proxy, rounding)
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/yfinance/multi.py", line 182, in _download_one
    rounding=rounding, many=True)
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/yfinance/base.py", line 150, in history
    data = _requests.get(url=url, params=params, proxies=proxy)
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/requests/api.py", line 76, in get
    return request('get', url, params=params, **kwargs)
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/requests/api.py", line 61, in request
    return session.request(method=method, url=url, **kwargs)
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/requests/sessions.py", line 530, in request
    resp = self.send(prep, **send_kwargs)
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/requests/sessions.py", line 643, in send
    r = adapter.send(request, **kwargs)
  File "/Volumes/Anaconda/anaconda3/lib/python3.7/site-packages/requests/adapters.py", line 510, in send
    raise ProxyError(e, request=request)
requests.exceptions.ProxyError: HTTPSConnectionPool(host='query1.finance.yahoo.com', port=443): Max retries exceeded with url: /v8/finance/chart/AAPL?range=5d&interval=1d&includePrePost=False&events=div%2Csplits (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 503 unknown method')))


Upstream changes

Overview
Changes:

Merged upstream master branch
Includes the "modernization" changes

@Zeitsperre thanks :) Looks good to me.
we will probably move to pygeoapi (ogcapi-processes) and skip pywps in the future. Probably we want to keep a cookiecutter for setting up new projects (birds). It is then also a chance to build an improved version ... for example using markdown for documentation?

@cehbrecht
I think Markdown makes sense for some of the documentation, mostly the top-level files (README, CHANGELOG, SECURITY, etc.), but given that we use numpy docstrings everywhere, ReStructuredText makes for consistent docs when rendered.
Would you want to make a separate cookiecutter for the PyGeoAPI-based projects? Start completely from scratch (or port from here/upstream?). There are a lot of patterns I held back on here to not cause headaches in existing projects, but I imagine a new template could benefit from them.
In any case, thanks for the review. Will update a few existing projects with this.

@cehbrecht
There are so many changes since 2020 that I'm setting this package as v1.0.0 of the package. We could technically place this on PyPI, but there would be no point, IMO. Perhaps a better idea would be to publish this on Zenodo for future reference.
I'll merge this now, but let me know in the day if that's of interest to you.

@cehbrecht
I think Markdown makes sense for some of the documentation, mostly the top-level files (README, CHANGELOG, SECURITY, etc.), but given that we use numpy docstrings everywhere, ReStructuredText makes for consistent docs when rendered.
Would you want to make a separate cookiecutter for the PyGeoAPI-based projects? Start completely from scratch (or port from here/upstream?). There are a lot of patterns I held back on here to not cause headaches in existing projects, but I imagine a new template could benefit from them.
In any case, thanks for the review. Will update a few existing projects with this.

I would prefer to start with new projects (and a new cookiecutter) for pygeoapi. To avoid some headaches :)

@cehbrecht
There are so many changes since 2020 that I'm setting this package as v1.0.0 of the package. We could technically place this on PyPI, but there would be no point, IMO. Perhaps a better idea would be to publish this on Zenodo for future reference.
I'll merge this now, but let me know in the day if that's of interest to you.

I'm fine with version v1.0.0 ... finally :) Personally I don't need a Zenodo reference.


Add exception handling

Errors can be found by monitoring aseprite output, which can be done in the overwritten print function.
This means the debugger should constantly be generating an error stacktrace, which is only updated when inside a source file, since when an error is thrown, the last bit of sourcecode code which is monitored with the debug hook, is exactly where the error will have occurred.


Improve ProfilePage UI

I'd like to work on it!

I'd like to work on it!

Is this a design or implementation issue? If design, I would love to work on this.

Is this a design or implementation issue? If design, I would love to work on this.


Should apply_sparse_mask in multihead_attention be a no-op?

❓ Questions and Help
Before asking:

search the issues.
search the docs.

I couldn't find any mention of apply_sparse_mask in https://github.com/pytorch/fairseq/issues?utf8=✓&q=apply_sparse_mask
What is your question?
Should apply_sparse_mask in multihead_attention.py (https://github.com/pytorch/fairseq/blob/master/fairseq/modules/multihead_attention.py#L429) be a no-op?
I also don't understand why this masking method is needed at all.
Code
    def apply_sparse_mask(attn_weights, tgt_len: int, src_len: int, bsz: int):
        return attn_weights

What have you tried?
Searching the docs and issues.
What's your environment?

fairseq Version master
PyTorch Version 1.4 (N/A)
OS (e.g., Linux): ubuntu 18.04
How you installed fairseq (pip, source): source
Build command you used (if compiling from source): python setup.py build_ext --inplace
Python version: 3.6.10 (Anaconda)
CUDA/cuDNN version: 10.1
GPU models and configuration: 2080TI/1080TI
Any other relevant information:

It's just a hook to modify the attention weights, since we have a few internal users who extend MultiheadAttention.
But in general the MHA interface has gotten very messy... I'm working on replacing it with a cleaner one soon.

But in general the MHA interface has gotten very messy... I'm working on replacing it with a cleaner one soon.

Do you have an estimated time when this will get replaced? Thanks.


Log to journald if possible

Helps debugging and gathering logs performance improvements.
Applies to both nginx and the API

Implemented in https://github.com/ooni/backend/issues/437


Add Arturas0 to Contributors list

Hello,
Please add me to Contributors list.
Thanks!

Hi  @Arturas0, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


Adding xms-ids for AppPlatform

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
If updating an existing version, please select the specific langauge SDKs and CLIs that must be refreshed after the swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No refresh required for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in a stable version
[ ] Removing properties in a stable version
[ ] Removing API version(s) in a stable version
[ ] Updating API in a stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

@agalerrotaru , appPlatform is onboarded to shiftleft PR review pipeline. Please make swagger change in ADO repository then it will be synced to github.

/azp run

@yuwzho  Our service only uses the public api version - the stable specs. Also to get the places which require xms identifiers, we run the autorest command: 'autorest --validation --azure-validator --openapi-type=arm --use=<EMAIL_ADDRESS>--use=<EMAIL_ADDRESS>"specification/recoveryservicessiterecovery/resource-manager/readme.md" > output.txt` . This will grab the files under the most recent tag of the stable version api.

@yuwzho Our service only uses the public api version - the stable specs. Also to get the places which require xms identifiers, we run the autorest command: 'autorest --validation --azure-validator --openapi-type=arm --use=<EMAIL_ADDRESS>--use=<EMAIL_ADDRESS>"specification/appplatform/resource-manager/readme.md" > output.txt` . This will grab the files under the most recent tag of the stable version api.

@agalerrotaru good to know that!


MinIO appliance instantiation issue with certain disk sizes

Bug when deploying the MinIO appliance. The virtual size of the appliance disk is 2,2GB, while the real disk size is 454MB.
When we try to instantiate it with less than 2.2GB disk size and get the following error from the Ceph driver:
Mon Jul  8 13:53:17 2024 [Z0][TrM][D]: Message received: TRANSFER FAILURE 1420 ERROR: clone: Command "    RBD="rbd --id oneclient"      rbd --id oneclient info onepool/one-132-1420-0 >/dev/null 2>&1 && exit 0      rbd_make_snap onepool/one-132      set -e -o pipefail      if [ "$(rbd_format onepool/one-132)" = "2" ]; then         rbd --id oneclient  clone "onepool/one-132@snap" onepool/one-132-1420-0     else         rbd --id oneclient copy onepool/one-132 onepool/one-132-1420-0     fi      if [ -n "454" -a "2048" -gt "454" ]; then         rbd --id oneclient resize onepool/one-132-1420-0 --size 2048     fi" failed: ^MCreating snap: 10% complete...^MCreating snap: 100% complete...done. rbd: shrinking an image is only allowed with the --allow-shrink flag Error cloning onepool/one-132 to onepool/one-132-1420-0 in uma-host-09

Issue probably due to the skip_resize_disk attribute in the appliance Packer script.

Real disk size should be 2.2GB, fixed on linked PR.


Could I ask about how to revoke the Certificate?

Dear Pkix.net,
Could I ask about how to revoke the Certificate?
Best Regards,
Dara Penhchet

Check ICertAdmin::RevokeCertificate method.

Dear Crypt32,
Could I ask you how to Enroll the New Certificate with PKIX.net Library by using the CSR PKCS#10?
Best Regards,
Dara Penhchet

See ICertRequest::Submit method.


frontend: Update typedoc version

Required for new typescript version https://github.com/headlamp-k8s/headlamp/pull/2219
The latest typedoc and markdown have some breaking changes resulting in a different file format. It's a bit easier to navigate than the current one but still not the best. There's some work needed to make the API docs more approachable.
Testing done:

[x] Generated new API docs and previewed them in the headlamp website

Actions needed after this:

[ ] Update links in the documentation that point to any page in API (since folder structure is different now)
[ ] Explore more options/plugins for typedoc to make API reference more approachable

For now I'm keeping the current generated API docs as is

This was originally in different PR but It's not building without new typescript version, Moving this back into typescript version bump PR


Add include/Platforms/Dos/Platform.h

Do we need a Platform.h?

No, not at this point. But it seems all platforms have one, whethere they need it or not?

So far, we've attempted to avoid depending from platform independent code to platform dependent code (in #include). So, guess the others can safely be removed?

Yes. The only one that's actually used is the C2000 one.

We only need stdint.h c2000/stdint.h.

Had to remove the hidden tentacles in Visual Studio 201x projects.
Let's say we are actively discouraging the use of Platform.h henceforth :-)

@basvodde anything wrong with this?

No, was just focusing on MockSupport :)