Fix: Checking of a Valid URL or not

Are you fixing a bug or providing a failing unit test to demonstrate a bug?
Yes, For checking a valid URL

How do you reproduce it?
By updating the regular expression format for the URL, by correcting the misplaced brackets and updating the * character to
'+'.The * char in regular expression mean the * means "0 or more occurrences of the preceding item" and + char means "1 or
more occurrences of the preceding item"
Also there was a misplaced bracket of the form: ( (exp1... ) OR exp2)....
instead it should have been of the form: ( (exp1...) ) OR (exp2....)
The * specified after the form (.[a-zA-Z])* means it can have nil (.com/.eu) but updating it to '+' ensures (.com/.in/.xyz) be
specified in the url to make it a valid url

What was the previous behavior?
Earlier it used to return true for  http://abcd or xyz/qw
which infact is not a valid URL as the domain name is not specified(.com/.eu/.in should be in the URL)
which in turn makes the 'govalidator package' work similar to the net/url package with a bug.

What is the current behavior?
After modifying it, it returns false for http://abcd or wxe/123 or nmhih
and in turn returns true for http://abcd.eu or xyz.ab or jkl.com

Explain why the changes are necessary
To check for a valid URL, there are two packages net/url and the govalidator package.But if this package does not return the
correct output, there is no difference between the faulty package(net/url) and this one.
So to be at a higher level and simplify the complexities of the user this commit needs to be merged.Also in various projects
the checking of a valid URL is a crucial part, hence forth moving forward.

Hello guys!
I forked this package cause owner disappeared. Hope, he will be back, but it would be easier to merge these changes back if he is back
Link to my repo: create issue there and we'll discuss it.


Add api to search for articles in help center.

Two changes were made to make searching for an article in the help center.

Make Article a SearchResultEntity, and add it to the list of available searchables.
Invoking the API call to the help center search.

@reviewbybees

:bee: as far as I understand it


Use real Literal::from_str from libproc_macro

Closes #287 now that https://github.com/rust-lang/rust/pull/84717 has made it into a stable Rust release.

FYI this broke a downstream project (https://github.com/apache/arrow-datafusion/issues/961)  when released, and looks like a few others as well (see the open issues linked)
Our fix was to pin to 1.0.28

(thank you for all your work on the proc-macro2 crate, BTW -- we certainly likely take all your work for granted


Tracking KRACK patch for Raspbian

Just an FYI, if you're interested in the status of, "Key Reinstallation Attacks" aka KRACK for WPA2, on Raspbian, see this thread.

A patched version is available.


Use official Conan packages

Hi!
This PR brings just some enhancements:

Download both Boost and Conan from official maintainers
Apply C++11 support by property on CMake

Regards!

Agreed!
But what about to just use this flag for gcc and clang? This example could
be executed with visual studio.
On Sat, Jul 14, 2018, 6:58 AM James<EMAIL_ADDRESS>wrote:

@memsharded commented on this pull request.
In CMakeLists.txt
https://github.com/memsharded/four-c-example/pull/2#discussion_r202511521
:

@@ -8,6 +8,6 @@ else()
endif()
conan_basic_setup()

-add_compile_options(-std=c++11)
If this worked in cmake 2.8.12, I wouldn't update it.
There are still some conan users that are using cmake 2.8.12, so it is
good to try to keep as compatible with them as possible.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/memsharded/four-c-example/pull/2#pullrequestreview-137234539,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEpQHaCTZFh94bRDMg1o8zdTOvumBhB3ks5uGcCngaJpZM4VPoZo
.

I typically work in Windows and VS :). It is just a warning for that case, it doesn't error.
But sure, it could be guarded with some if().


Fail on interval runs on windows

🚧  needs appveyor fix 🚧

@lamont-granquist I think this one just needs rebasing and pushing to get past Appveyor now?

nope, still the same thing -- the rspec examples don't fail, but rspec exit 1's and fails.  i'm guessing somehow the rspec run is inheriting the failed status of a subprocess.


Framework compatibility

This PR does 3 things:

Updates the podspec so the font file is added to a bundle and import the needed frameworks (UIKit and CoreText)
Changes some stuff's visibility to public, so they can be accessed from another framework
Dynamically loads the font, so the developer doesn't add it manually to the project and to Info.plist. Honestly, I don't even know if that would work when you're creating it (with UIFont(name:, size:)) from another framework.

Those steps were needed to ensure compatibility to the upcoming CocoaPods 0.36, which adds support to dynamic frameworks.

@marcelofabri Thanks for the pull request and sorry for not getting back to you sooner. I accidentally deleted the GitHub notification email when cleaning my inbox.


Nondeterminism with type name conflicts in DWARF across CUs

When you have types with the same name and conflicting definitions across compilation units in DWARF, the actual defined type with that name in binaryninja can be either.
For example:
a.c has FLO_type typedef float;
b.c has FLO_type typedef double;
Roughly 50% of the time it will be float and 50% of the time it will be double

Fixed in 4.2.6101-dev


[Redesign] Package edit - submit-button enabled only by focus change

I noticed that the submit button on package edit page is only enabled when I change something and change the focus to the next control. It would be better if the trigger would be a keydown event, because it might confuse people like me ;)
Repo:

Edit a package
Click in the package title input
Change the title
Try to click on submit

Browser: Chrome 58 on macos.

Thanks for the tip, @robertmuehsig! Always happy to see your feedback and contributions 😄.

Resolved. Not yet deployed.


no such file @ rb_file_size_s

I had used overcommit for a particular repository, but had removed the gem, but  then doing a commit I received the following message
This repository contains hooks installed by Overcommit, but the `overcommit` gem is not installed.
Install it with `gem install overcommit`.

To fix this I rebooted my machine and, but when I tried to do a commit, I received the following message:
No such file or directory @ rb_file_s_size - /Users/Chris/Sites/philomaths/--git-common-dir/hooks/overcommit-hook
/Users/Chris/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/fileutils.rb:815:in `size'
/Users/Chris/.rvm/rubies/ruby-2.2.1/lib/ruby/2.2.0/fileutils.rb:815:in `compare_file'
/Users/Chris/.rvm/gems/ruby-2.2.1@philomaths_221/gems/overcommit-0.44.0/lib/overcommit/installer.rb:57:in `update'
/Users/Chris/.rvm/gems/ruby-2.2.1@philomaths_221/gems/overcommit-0.44.0/lib/overcommit/installer.rb:20:in `run'
.git/hooks/pre-commit:67:in `<main>'
Report this bug at https://github.com/brigade/overcommit/issues

so I am reporting it.
Another aspect of the problem is that if do gem install overcommit and then do overcommit --uninstall following by overcommit --list-hooks the hooks are still there including some of the PreCommit hooks e.g. AuthorEmail being enabled.  If I then try to do a commit, I get the original error message i.e.
This repository contains hooks installed by Overcommit, but the `overcommit` gem is not installed.
Install it with `gem install overcommit`.

Note that I am using RVM, but I have also tried rvm @global do gem uninstall overcommit, which is appears to work,  but this does fix the issue of not being able to do a git commit.  I have also asked this SO question  but to no avail.

Hey @obromios, removing the gem does not remove the hooks. Remember that Git hooks are actual files installed in your repository's .git/hooks directory.
Rather than uninstall the gem, you needed to run:
overcommit --uninstall

...in your repository to uninstall the hooks. Hope that helps!

I am in the root of my repository at /Users/Chris/Sites/philomaths,  ls -a shows Gemfile, .git etc. I type
overcommit -u
and see
Successfully removed hooks from /Users/Chris/Sites/philomaths
but when I do a commit, I still get
This repository contains hooks installed by Overcommit, but the `overcommit` gem is not installed.
Install it with `gem install overcommit`.

and if I type overcommit --list-hooks I get a long list of commit hooks starting with
CommitMsg:
  CapitalizedSubject: enabled
  EmptyMessage: enabled
  GerritChangeId: disabled
  HardTabs: disabled
  MessageFormat: disabled
  RussianNovel: disabled
  SingleLineSubject: enabled

Hey @obromios, I'm not understanding how you're seeing the behavior you describe. There are a couple of things that don't make sense to me:

When you run overcommit -u, Overcommit is clearly installed. There shouldn't be a way for you to see the error message about the gem not being installed, unless you explicitly uninstalled it after uninstalling the hooks

When I try reproducing this locally (installing hooks, then uninstalling) everything works as expected

As for --list-hooks, please ignore it. It will always show what hooks would run if Overcommit were to be installed, and does not tell you whether or not the hooks are actually installed.
I'm afraid I can't be of help here. There's something odd with your installation and I don't have suggestions as to what it could be.

Thank you, it was helpful to know that it was something odd in installation rather than me doing something odd with overcommit.
The installation was the result of copying the entire disk from an old machine to a new machine. Perhaps this somehow corrupted the overcommit installation.   What I ended up doing was cloning a new copy from the master at Github. This exhibited none of the problems that I have described.  I then manually edited the clone branch to add changes from the older corrupted branch.
One thing that I did find strange is that when I cloned the master, if I did gem list overcommit it returned
*** LOCAL GEMS ***

overcommit (0.28.0)

despite the fact that I did not have overcommit in my Gemfile and I had not installed overcommit into the new respository.
Perhaps the problem was to do with version 0.28.0 of overcommit.


Fix exception in ResourceUtility constructor

Description

Remove constructor and static field.

Motivation and Context

This static field wasn't being used anywhere. Plus it was causing issues in the constructor depending on the order of the assembly loading.

How Has This Been Tested?

Tested with managed resources from samples repo.

Screenshots
Types of changes

[ ] Improvement (non-breaking change that improves a feature, code or algorithm)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Signed-off-by: José Simões<EMAIL_ADDRESS>

Requires nanoframework/nf-interpreter#1007 to be merged.


Add the support of client certificate

When uploading，use thclient certificate to access the server.
Cloudflare offen use the JavaScript Challenge to block the request from the GitHub action.

Sorry for the late response
Did you mean https://developers.cloudflare.com/waf/? currently, the OpenDAL does not support custom request, so the work way is setting CF to allow GitHub Action Host IP access^1

Sorry for the late response
Did you mean https://developers.cloudflare.com/waf/? currently, the OpenDAL does not support custom request, so the work way is setting CF to allow GitHub Action Host IP access1
Footnotes

https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners#ip-addresses ↩

I have created a list that includes IP addresses from the GitHub Meta API, But some IPs are not in the GitHub Meta API
That project has been archived, so there's no need for further replies.
Thank you for your replies!


Extension issue

Issue Type: Bug
Extension Name: js-debug
Extension Version: 1.56.3
OS Version: Linux x64 5.8.0-53-generic
VS Code version: 1.56.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

/needsMoreInfo


Update README.md

Mim unique title

I think this will make the mosaics more accessible to collections that have ~500 pieces, lets do it!

I think this will make the mosaics more accessible to collections that have ~500 pieces, lets do it!

agree, we good now ! perfect setting, tiny bug fixed, we good to the moon !


Allow a user to change the type used for the IItemWithTimestamps interface

I currently use Nodatime to do all my date/time work.
It would be nice if the IItemWithTimestamps interface was generic so I could directly use this without going through a conversion

Hi @SeanFarrow IItemWithTimestamps is just our custom extension on the initial IItem I am sure you could create your own version which uses Nodatime. It's not something I have used before.

OK, that makes complete sense, thanks.


Formatter: Missing end indentation on macros

This code:
  macro greeting
    puts "Hi!"
    # something else...
  end

is formatted to:
macro greeting
    puts "Hi!"
    # something else...
  end

Duplicate?: https://github.com/crystal-lang/crystal/issues/2030
This issue is related to this comment: https://github.com/crystal-lang/crystal/issues/2030#issuecomment-172914882
Also https://github.com/crystal-lang/crystal/issues/2030#issuecomment-172917533 explains that macros can't be formatted and I'm ok with that, but would be possible to remember previous macro keyword indentation and use same indentation on the end keywork finishing a macro code block?
At least to get something like this:
macro greeting
    puts "Hi!"
    # something else...
end

(notice aligned end keyword and macro body without changes)
WDYT?

This is not a bug. The macro keyword should be aligned to the left by the normal rules of the formatter, and then the formatter preserves spaces in macros, and there are two spaces before end.


Verify DKIM signatures generated by Gmail/other providers (enables easier account recovery)

Challenge description:
Since most emails are signed cryptographically through DKIM, and contain enough data to prove who the sender is (from wikipedia: "the From: field must always be signed"), we can use that for recovering Ethereum accounts.
How it would help: it could enable a next-generation UX for dapps where you can sign up with an email/password, without making big security compromises, and with an ability to change your password and recover your account.
Of course, it's not a silver bullet, as you're ultimately trusting your email provider. But trusting the email provider is significantly more realistic for most people than trusting a startup to keep your private key.
The challenge is to build a proof of concept that verifies a real DKIM signature from an email generated by Gmail, via a Solidity smart contract, on-chain, within a reasonable gas limit.
Technical details
We basically need a solidity contract to verify the DKIM-Signature field based on a certain body; It needs to check the signature agianst the _domainkey TXT record for the domain, for which we'll need a key "oracle": for this PoC, it's sufficient to just hardcode the _domainkey records for gmail.com and any other large providers, but in the future, we'll need a proper oracle that can read the _domainkey record for any arbitrary domain.

explainer: https://www.20i.com/blog/dkim-demystified/
spec: http://dkim.org/specs/rfc4871-dkimbase.html

RSA and ed25519 crypto will be needed, which is not supported out of the box but these resources can help:

https://github.com/javgh/ed25519-solidity
https://github.com/HarryR/ethsnarks/blob/master/contracts/ETEC.sol this will work for all twisted Edwards curves, so if the modulus is changed it should work with ed25519
RSA is easier cause of EIP 198 in byzantium: see https://github.com/adria0/SolRsaVerify
various signature schemes are implemented by the dnssec-oracle: https://github.com/ensdomains/dnssec-oracle/tree/master/contracts/algorithms

Submission requirements:

Gas cost: should be under 3 million gas
Can verify a DKIM signature generated by Gmail
Implement a script that takes a raw email as input and invokes a method on a solidity smart contract (on a local network, with ganache/truffle) to check this email's signature
must be able to prove, on chain, that the From header (sender) is a particular email (NOTE: this requirement was omitted at the time of the hackathon launch so you won't be judged based on it)

Submission deadline:

November 11

Judging criteria:

Gas cost
Correctness and elegance of the solution
Support the signature schemes by large email providers (Gmail, Outlook, Yahoo, ProtonMail)
Contributions to other open-source packages will be appreciated

Judging date:

November 12

Bounty

1800 DAI

Further bonuses available if it works with multiple signature schemes and multiple email providers.

hello @Ivshti ,
hope you are doing well, I have tested on-chain verification for RSA-SHA256 and RSA-SHA1 with multiple providers and it worked fine since most providers use RSA-SHA256, for RSA-SHA1 I have used a personal mail server to generate the email with RSA-SHA1 the test was also successful
however for ed25519 I'm still working on it, the solidity contract provided as reference does not do the signature verification following my understanding
also, do we need to check any kind of data inside the contract since it should be required to update the password hash for example ? except the hashing itself.

Hey everyone (@RideSolo, @bakaoh, @nionis) - we are in the middle of the judging process. You all did a great job, we did not expect to have 3 independent full submissions! We may run a few days late with the decision - we'll certainly be ready by Friday (15th).

@Ivshti thanks for the feedback

Again, sorry for the delay.
We'll be announcing the results on Monday, stay tuned!

Hello everyone,
What's great: you all implemented working solutions with proper tests! We were very impressed - we certainly didn't expect 3 working solutions.
What's still to be desired: none of the solutions actually checked for a particular From (sender), which is critical for a password recovery scheme based on this; furthermore, none of the solutions checked if the bodyHash is actually part of the canonicalizedHeaders that are getting signed
What we decided: all of the solutions had different advantages. We tried an elaborate points scoring system and you all came close to each other. So we decided, instead of rewarding only one solution, to increase the reward and split it between first/second/third places.
Here are the results:

@RideSolo - 1100 DAI - your solution scored the highest (52.5pts) due to being generally good in all categories, but especially good in algorithm support: it was the only solution to implement ed25519, which makes it future proof; also, it had an incredibly detailed test suite which compared off-chain results to on-chain results, and tested failing cases too (incorrect signatures)
@nionis - 750 DAI - your solution scored a close second (49pts) by virtue of good gas cost results and bonuses for having a demo app and OSS contributions
@bakaoh - 650 DAI - 40.5pts - your solution did a lot of parsing on-chain, which decreased the gas costs criteria - some emails we tested needed way more than 3 mil gas to be verified; however, we gave it a few bonus points for security, cause it makes it easier to add checks if the From header is a certain value; the code quality was also impressive, given the hard task

Here's what's included in the points scoring system (based on the "submission requirements" and "judging criteria"):

README and presentation
Tests: how easy were they to run and their quality
Algorithm/provider support
Gas usage score
Correctness and security
Elegance, simplicity and readability
Bonuses - OSS contribution, demo
"real world"/adaptability score - this graded how adaptable the code is for the purposes of the vision (recover your account via DKIM)

We will be distributing the actual rewards ASAP, it may require some assistance from Gitcoin because of the splitting.
Thanks to everyone involved in this bounty! Once again, you did an awesome job!
We still need more work to turn this into a working PoC, so stay tuned for updates!

thanks @Ivshti, it's so much fun working on this bounty

I'm really glad that I participated to this hackathon,  and I will be happy to work further to maintain this project

@Ivshti thank you for taking time to look into it very thoroughly, much appreciated

@bakaoh I also believe the on-chain parsing implementation is very impressive. Great job!


Implement TransitionTween

Spec: https://material-motion.github.io/material-motion/starmap/specifications/plans/TransitionTween

💻 I'm working on a diff at http://codereview.cc/D1916

🎊 My diff is ready for review at http://codereview.cc/D1916


Improve concurrency with Cache wrapper

CachedLayoutRendererWrapper - Added ThreadSafe attribute
Improve concurrency issues reported with #4129

Forced pushed because I discovered a loop-hole in the intiail cache-validation, where racing could lead to null-value.


YARP has a higher cpu usage than Nginx

Sorry, I don't know if it is a bug.
Describe the bug
I deployed 3 nginx at HongKong, and deployed 3 YARP at HangZhou.

Client -> Nginx -> Yarp -> Service

Nginx forwards some services, and YARP forward one of them.
Nginx CPU

YARP CPU

YARP other metrics

Htop (Cat.Service.dll is based on YARP)

I tried to analyze the CPU on vs
Top function

Module View

To Reproduce
No exception.
Further technical details

Include the version of the packages you are using
2.1.0
The platform (Linux/macOS/Windows)
Linux

They're all 4c8g, YARP on ubuntu 22.04, nginx on centos.
YARP 2.1.0  runs on .NET 8.

How does the load / RPS compare?

How does the load / RPS compare?

Every yarp is almost 4000

I loaded pdb, and found that it had something to do with threads, I will try to set min thread to test.

I used YARP source code analysis, I found that YARP itself does not have high cpu usage.

Is  it a same issue with https://github.com/dotnet/runtime/issues/70098
And I see there's pr to fix it

@MihaZupan hi，is there any news？
In my case, I have a qps 120,000 service. It only need 3 nginx, but used 40 yarp service. It troubles me.

The performance gap is so obvious, is there any room for improvement?

How does the load / RPS compare?

Is there any news about this issue?
Through observations over the past few days, we found that when the response time of downstream services fluctuates, Porxy is under great pressure. Simply put, requests that originally required 100 threads to process require more threads to process these requests due to downstream fluctuations. At this time, threads are piled up, and then more threads are quickly started to process these requests. However, this rapid change of threads in a short period of time causes obvious CPU fluctuations, and as the downstream stabilizes, threads that have not been used for a long time will be destroyed. In this way, downstream fluctuations will have a great impact on Proxy. Although we set the minimum number of threads, this will not prevent the thread pool from recycling threads later. It only enables more threads to be started quickly. We hope to keep these threads alive all the time, and do not want frequent thread startups to cause large CPU fluctuations.
 ThreadPool.SetMinThreads(500, 500);

@Tratcher  @MihaZupan

We upgrade .NET 8 to .NET 9 preview, and set some envionment variables
DOTNET_SYSTEM_NET_SOCKETS_THREAD_COUNT = 500
DOTNET_ThreadPool_UnfairSemaphoreSpinLimit = 0
DOTNET_SYSTEM_NET_SOCKETS_INLINE_COMPLETIONS = 1

Overall, it indeed consumes less CPU (around 30% less), and there are no longer minute-level blockages causing widespread timeouts when the Current Request suddenly increases. However, there is still a small probability of request timeouts, and the frequency of CPU fluctuations has become very frequent. We tracked that the downstream service responds quickly, and occasionally requests timeout due to yarp, but because the QPS is relatively high, these timeouts are not visible on the dashboard. We have another upstream service that is particularly sensitive to abnormal requests, and in the upstream service, we see that requests with a small probability of timeout occur very frequently.
First, let's look at the performance of yarp, which has indeed improved.

These are abnormal requests detected upstream, all of which are SocketExceptions.

In summary: Setting thread-related parameters can reduce CPU usage but will introduce more instability, and there is still a significant gap compared to Nginx.

 However, according to the data, it will affect qps. However, we have not yet added link monitoring, so the impact on qps is not yet known. From the perspective of upstream requests, the average response time is not greatly affected.

However, compared with nginx, yarp still has a lot of room for improvement. We hope to use it instead of other reverse proxy products.

@Tratcher @MihaZupan
Sorry, I have to seek your help again. Because the CPU control still cannot meet our expectations, we might choose another reverse proxy as a result. This is a tough decision, as we are all .NET developers and had high hopes for YARP. Our requirements are not extremely stringent for YARP to match the performance parameters of Nginx. However, if we only need three Nginx servers to handle all the traffic stably, I cannot convince our team to choose YARP, which requires over 40 servers to run stably. I hope the .NET team can see this message and respond to us. Even just prioritizing the resolution would be very helpful. Thank you.

We are also choosing between nginx and yarp. As. net developers, we prefer to use yarp. Has there been any progress on this issue?

We do not see such huge differences in our perf lab between YARP and NGINX. The ratio is currently about 2:3 I believe. @MihaZupan can link our public perf dashboard.
That said, we are interested in learning why do you see so different ratio. However, it will require some deep digging and collaboration. Are you willing to help us understand the root cause and potentially help us improve YARP?

Is it related to the https://github.com/dotnet/runtime/issues/70098

Only in the sense that this PR is improving HttpClient (and therefore also YARP) performance.
The change is about lowering contention in the connection pool, which shouldn't be a huge factor at the several thousand RPS/machine that you're looking at. So while it may save you some CPU cycles, I wouldn't expect it to make a meaningful difference in this case.

requests that originally required 100 threads to process require more threads to process these requests due to downstream fluctuations

This is a surprisingly high number of threads to see on a 4-core machine if everything is fully async (you're not doing "sync over async").
Were you seeing these numbers before you started modifying ThreadPool settings?

ThreadPool.SetMinThreads(500, 500);
DOTNET_SYSTEM_NET_SOCKETS_THREAD_COUNT = 500

Settings like these seem excessive for the machine size and are more likely to hurt performance than improve it. I'd recommend removing them unless you have real evidence that they're improving things.
The thread pool should be able to adjust the number of threads to adapt to different load levels.

<GarbageCollectionAdaptationMode>0</GarbageCollectionAdaptationMode>

How come you're disabling this? I was under the impression that you were worried about the memory footprint (#2527) after load spikes without this functionality.

It only need 3 nginx, but used 40 yarp services

How did you arrive at the 40 number?
What happens if you e.g. use 10 instead? Is request latency meaningfully impacted?

DOTNET_ThreadPool_UnfairSemaphoreSpinLimit

While this may reduce the CPU usage reported for a process, it may negatively impact throughput while under load.
If you experiment with reducing the number of YARP instances, such that the per-instance load is higher, does removing this environment variable (leaving the default behavior) make a difference?

There may be other factors impacting the performance between Nginx and YARP.
As Karel mentioned, we're aware of the performance differences, but the numbers we're seeing in the automated performance runs (select the "Proxies" tab on the bottom) are much closer than what you're seeing, nowhere near the 3:40 ratio.
Are both proxies using the same HTTP protocol to the backend (YARP will default to HTTP/2 if the backend supports it)?
I saw you've posted previous questions in the repo about e.g. injecting Connection: Close headers. Can you share what your YARP configuration looks like, and how it differs from the Nginx setup?

@MihaZupan
Glad to receive your reply. After confirmation with the business side, we got the ratio of 3:11, close to 1:4. Currently, no special optimization has been done on nginx. Only two operations have been done on yarp.

Weight-based weighting of Destination

public class WeightingRoundLoadBalancingPolicy : ILoadBalancingPolicy
{
    private ILogger<WeightingRoundLoadBalancingPolicy> _logger;

    public string Name => "WeightingRound";

    public WeightingRoundLoadBalancingPolicy(ILogger<WeightingRoundLoadBalancingPolicy> logger)
    {
        _logger = logger;
    }

    public DestinationState? PickDestination(HttpContext context, ClusterState cluster, IReadOnlyList<DestinationState> availableDestinations)
    {
        if (Weighting.WeightedClusterWeights.TryGetValue(cluster.ClusterId, out var weightedWeights))
        {
            if (weightedWeights is null)
            {
                _logger.LogInformation($"PickDestination Error: Can not get [{cluster.ClusterId}] cluster weightedWeights");
                return null;
            }

            if (weightedWeights.DestinationIds is null)
            {
                _logger.LogInformation($"PickDestination Error: Can not get [{cluster.ClusterId}] destination, DestinationIds is null");
                return null;
            }

            var destinationId = weightedWeights.DestinationIds[WeightingHelper.GetIndexByRandomWeight(weightedWeights.DestinationWeightedWeights, weightedWeights.DestinationWeights, weightedWeights.TotalWeights ?? 1D)];

            return availableDestinations.FirstOrDefault(destination => destination.DestinationId == destinationId);
        }

        _logger.LogInformation($"PickDestination Error: Can not get [{cluster.ClusterId}] cluster");
        return null;
    }
}

public class WeightingHelper
{
    public static (double[]? Weights, double? TotalWeight) GetWeightedWeights(double[] weights)
    {
        if (weights.Length == 0) return (null, null);
        else if (weights.Length == 1) return ([.. weights], weights[0]);

        var totalWeight = 0D;
        Span<double> newWeights = stackalloc double[weights.Length];

        for (int i = 0; i < weights.Length; i++)
        {
            totalWeight += weights[i];
            newWeights[i] = totalWeight;
        }

        return ([.. newWeights], totalWeight);
    }

    public static int GetIndexByRandomWeight(Span<double> weightedWeights, Span<double> weights, double totalWeight)
    {
        // Ignore weight when only one server
        if (weightedWeights.Length == 1) return 0;

        var randomWeight = Random.Shared.NextDouble() * totalWeight;
        var index = weightedWeights.BinarySearch(randomWeight);

        if (index < 0)
            index = -index - 1;
        else if (index > weightedWeights.Length)
            // The number of servers decreases
            index = GetIndexByRandomWeight(weightedWeights, weights, totalWeight);

        if (weights[index] != 0D)
            return index;
        else
            // The weight of the server is 0
            return GetIndexByRandomWeight(weightedWeights, weights, totalWeight);
    }
}

Add request log monitoring

public class LoggingMiddleware
{
    private readonly RequestDelegate _next;
    private readonly ILogFormatter _logFormatter;
    private static readonly Channel<byte[]> _logChannel = Channel.CreateUnbounded<byte[]>();
    private static int _batchSize = 500;
    private static DateTime _lastWriteTime;

    public LoggingMiddleware(RequestDelegate next, ILogFormatter logFormatter)
    {
        _next = next;
        _logFormatter = logFormatter;

        int consumerCount = Environment.ProcessorCount;
        Task.Run(ProcessLogsAsync);
    }

    public async Task InvokeAsync(HttpContext context)
    {
        Stopwatch sw = new();
        sw.Start();

        try
        {
            await _next(context);
        }
        finally
        {
            sw.Stop();

            var logEntry = _logFormatter.Format(context, new LogFormatterAdditionalInfo(sw.ElapsedMilliseconds));
            await _logChannel.Writer.WriteAsync(logEntry);
        }
    }

    private static async Task ProcessLogsAsync()
    {
        var batch = new List<byte[]>();

        await foreach (var logEntry in _logChannel.Reader.ReadAllAsync())
        {
            batch.Add(logEntry);

            if (batch.Count >= _batchSize || (DateTime.Now - _lastWriteTime).TotalSeconds >= 1)
            {
                var fs = LoggingHelper.FileStream;
                if (fs is null)
                {
                    continue;
                }
                _lastWriteTime = DateTime.Now;
                await WriteBatchAsync(fs, batch);
                batch.Clear();
            }
        }
    }

    private static async Task WriteBatchAsync(FileStream fs, List<byte[]> batch)
    {
        try
        {
            foreach (var logEntry in batch)
            {
                await fs.WriteAsync(logEntry);
            }
            await fs.FlushAsync();
        }
        finally
        {
        }
    }
}

Our scenario is that the response is longer and the execution is higher.

nginx
  upstream XXX-Intranet {
    server xxx.com;//custom internal domain
  }

  server {
    listen 88;
    server_name XXX-Project.com

    access_log off;
    error_log off;

    location / {
      client_max_body_size 30m;
      client_body_buffer_size 128k;

      proxy_pass http://XXX-Intranet;
      proxy_set_header XXX-Real-IP $remote_addr;
      proxy_set_header XXX-X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header Host $host;

      proxy_connect_timeout 300;
      proxy_send_timeout 300;
      proxy_read_timeout 300;
      proxy_ignore_client_abort on;
      proxy_buffer_size 64k;
      proxy_buffers 4 128k;
      proxy_busy_buffers_size 256k;
      proxy_temp_file_write_size 256k;

      keepalive_requests 1000;
      proxy_http_version 1.1;
      proxy_set_header Connection "";
    }
  }

yarp
{
  "Logging": {
    "LogLevel": {
      "Default": "Warning",
      "Microsoft.AspNetCore": "Warning"
    }
  },
  "AllowedHosts": "*",
  "Cat": {
    "ListenUrls": [
      "http://*:80"
    ],
    "Routes": [
      {
        "RouteId": "XXXProjectRoute",
        "Match": {
          "Path": "{**catch-all}"
        },
        "ClusterId": "XXXProjectCluster",
        "Transforms": [
          {
            "RequestHeaderOriginalHost": "true"
          },
          {
            "X-Forwarded": "Set",
            "For": "Off"
          },
          {
            "ResponseHeader": "Connection",
            "Append": "close"
          }
        ]
      }
    ],
    "Clusters": [
      {
        "ClusterId": "XXXProjectCluster",
        "ClusterConfigTemplate": {
          "LoadBalancingPolicy": "WeightingRound",
          "HttpRequest": {
            "ActivityTimeout": "00:03:00"
          }
        },
        "DestinationAddressTemplate": "http://{0}:5000",
        "Destinations": [
          {
            "IPAddress": "<IP_ADDRESS>",
            "Weight": 100
          },
	 {
            "IPAddress": "<IP_ADDRESS>",
            "Weight": 100
          }
        ]
      }
    ]
  }
}

"ResponseHeader": "Connection",
"Append": "close"

Why are you forcing connections from the client to the proxy to never be reused?
I don't see you doing so with Nginx, which could explain the massive perf differences.

"ResponseHeader": "Connection",
"Append": "close"

Why are you forcing connections from the client to the proxy to never be reused? I don't see you doing so with Nginx, which could explain the massive perf differences.

Thank you very much, we need some time to test

"ResponseHeader": "Connection",
"Append": "close"

Why are you forcing connections from the client to the proxy to never be reused? I don't see you doing so with Nginx, which could explain the massive perf differences.

After adjusting the configuration, the ratio between nginx and yarp is about 1:2.5. The Connection: Close has been deleted. after testing, turning off spin has lower CPU usage than the default

Were you able to look at other questions from https://github.com/microsoft/reverse-proxy/issues/2427#issuecomment-2403504256?
Particularly how that ratio is determined.
You've opened several issues across repos, what does your configuration look like now? Are you changing thread counts, changing thread pool environment variables, etc.?
What do your request and responses look like (e.g. size, duration)?

Were you able to look at other questions from #2427 (comment)? Particularly how that ratio is determined.
You've opened several issues across repos, what does your configuration look like now? Are you changing thread counts, changing thread pool environment variables, etc.?
What do your request and responses look like (e.g. size, duration)? Have you tried remeasuring performance on .NET 9.0?

After testing, the CPU performance is better when the spin is turned off than when it is not turned off, with a difference of about 30%, but this is not absolute. It is related to qps and throughput. For requests with high throughput and low qps, the effect is not very prominent.
.net9.0 has better performance. We have upgraded to .net9.0, and Connection: Close has also been removed, but the ratio is only 1:2.5.
We also found a very strange phenomenon. After the business project was deployed on Windows Server and Linux Ubuntu Server respectively, it was found that the CPU of the .net project deployed on the Windows machine was better, 50% higher than the Linux server deployment, but the memory was 100% worse than Linux. However, we did not deploy reverse-proxy on the Windows machine. I wonder if you have compared the difference between the deployment of reverse-proxy on these two operating systems?
After our use, we found that the reverse-proxy project is a service that consumes CPU but consumes relatively less memory. If Windows is better, we can find time to try to deploy it on the Windows server to see the effect


easy ways to make it works

I tried to run it without ngrok.
it needs only Dockerfile, start.sh, server.jar.
server.jar is certenly runned and I saw Done! log.
but I cannot get access on minecraft server.
Can you help?
files.zip

the thing is huggingface provides http and https only, no tcp and udp (as i tested)
so you cant make server without services like ngrok or smth similar
maybe will leave this issue open


UTF-8 characters as emoji

Is it possible to use UTF8 characters as emoji? Some people just copy-paste them from websites, like here: http://apps.timwhitlock.info/emoji/tables/unicode
Twemoji also supports this by default, but not if I'm using it with this plugin.

I'm not shure your question is related to this project.


Billing Platform - new endpoint for onboarding subaccounts

The subaccount creation and the onboarding should be done in two steps.
To do:

add an endpoint for triggering the onboarding process (with the corresponding canOnboard authorization for the admin)
make sure the creation does not trigger the onboarding and only put the subaccount in a dedicated state (INITIAL or IDLE or ??)
adapt the corresponding tests

@Ninjeneer : let me know what you think


initial appendix

Create a section at the end of the README for an appendix.  Add an appendix for sample disconnected registry implementations and a readme to deploy standalone quay to support a disconnected registry.

LGTM.
@jflowers thoughts?

@itewk lgtm, let's get one more review from @afflom

@mallmen got some cycles to respond to @afflom review?

@mallmen got some cycles to respond to @afflom review?
I will look at the suggestions and work on it.  I should have something by Monday.


[WIP] pythonPackages.cram: fix tests

Motivation for this change
Cram is broken on staging, but not on master. I don't know why and I have no idea how cram works so I can't figure out what that one test failure is about.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

/cc @jluttine

@GrahamcOfBorg build python2.pkgs.cram

Failure on x86_64-linux (full log)
Partial log (click to expand)
+  IOError: [Errno 32] Broken pipe
+  [1]
+  $ md5 examples/fail.t examples/fail.t.err
+  0f598c2b7b8ca5bcb8880e492ff6b452  examples/fail.t
+  7a23dfa85773c77648f619ad0f9df554  examples/fail.t.err
   $ rm patch examples/fail.t.err
ss...
# Ran 11 tests, 3 skipped, 1 failed.
builder for '/nix/store/17bgzqx5hwmy46mjnmjim1ljm0xq1hhv-python2.7-cram-0.7.drv' failed with exit code 1
error: build of '/nix/store/17bgzqx5hwmy46mjnmjim1ljm0xq1hhv-python2.7-cram-0.7.drv' failed

Success on aarch64-linux (full log)
Partial log (click to expand)
shrinking RPATHs of ELF executables and libraries in /nix/store/7662z3biykaxcp8h9543zaq7hh9hgnbf-python2.7-cram-0.7
strip is /nix/store/qp4g6waq07493xinscfmba5qkl22fspd-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/7662z3biykaxcp8h9543zaq7hh9hgnbf-python2.7-cram-0.7/lib  /nix/store/7662z3biykaxcp8h9543zaq7hh9hgnbf-python2.7-cram-0.7/bin
patching script interpreter paths in /nix/store/7662z3biykaxcp8h9543zaq7hh9hgnbf-python2.7-cram-0.7
checking for references to /build in /nix/store/7662z3biykaxcp8h9543zaq7hh9hgnbf-python2.7-cram-0.7...
wrapping `/nix/store/7662z3biykaxcp8h9543zaq7hh9hgnbf-python2.7-cram-0.7/bin/cram'...
running install tests
..s...ss...
# Ran 11 tests, 3 skipped, 0 failed.
/nix/store/7662z3biykaxcp8h9543zaq7hh9hgnbf-python2.7-cram-0.7

@GrahamcOfBorg build python2.pkgs.cram python3.pkgs.cram

Success on aarch64-linux (full log)
Partial log (click to expand)
strip is /nix/store/qp4g6waq07493xinscfmba5qkl22fspd-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/a04af4h2kjnj28c9lggsb4dgs77j361f-python3.6-cram-0.7/lib  /nix/store/a04af4h2kjnj28c9lggsb4dgs77j361f-python3.6-cram-0.7/bin
patching script interpreter paths in /nix/store/a04af4h2kjnj28c9lggsb4dgs77j361f-python3.6-cram-0.7
checking for references to /build in /nix/store/a04af4h2kjnj28c9lggsb4dgs77j361f-python3.6-cram-0.7...
wrapping `/nix/store/a04af4h2kjnj28c9lggsb4dgs77j361f-python3.6-cram-0.7/bin/cram'...
running install tests
..s...ss...
# Ran 11 tests, 3 skipped, 0 failed.
/nix/store/7662z3biykaxcp8h9543zaq7hh9hgnbf-python2.7-cram-0.7
/nix/store/a04af4h2kjnj28c9lggsb4dgs77j361f-python3.6-cram-0.7

Failure on x86_64-linux (full log)
Partial log (click to expand)
cannot build derivation ‘/nix/store/dhkydvn44w5i5k9xmmr8xp3jn0fvhkg8-python3-3.6.4.drv’: 12 dependencies couldn't be built
cannot build derivation ‘/nix/store/a20491zrwkkpqvvpgxry5h84givgb2ak-hook.drv’: 4 dependencies couldn't be built
cannot build derivation ‘/nix/store/w7jmiij7vxr4byq95v4h4f684lc8k99k-hook.drv’: 4 dependencies couldn't be built
cannot build derivation ‘/nix/store/ykl4v3dc627lkvg30fi4lghnw1891xqs-python2.7-bootstrapped-pip-9.0.1.drv’: 5 dependencies couldn't be built
cannot build derivation ‘/nix/store/nxqn06wv9ijrjm7ksgawj8hcrzq9zj0q-python3.6-bootstrapped-pip-9.0.1.drv’: 5 dependencies couldn't be built
cannot build derivation ‘/nix/store/d7kpi4glh11v22pxf0iixcx2m2cnwcli-python2.7-setuptools-38.4.0.drv’: 5 dependencies couldn't be built
cannot build derivation ‘/nix/store/ypbdhzzqz5b8b9higzjqqc7lkfxxw7vj-python3.6-setuptools-38.4.0.drv’: 5 dependencies couldn't be built
cannot build derivation ‘/nix/store/8zv577449is449glw688hxhyl4lxwapp-python2.7-cram-0.7.drv’: 8 dependencies couldn't be built
cannot build derivation ‘/nix/store/fkjgd9hlv9an5d6pwzxdaa40mwaxqy5h-python3.6-cram-0.7.drv’: 8 dependencies couldn't be built
error: build of ‘/nix/store/8zv577449is449glw688hxhyl4lxwapp-python2.7-cram-0.7.drv’, ‘/nix/store/fkjgd9hlv9an5d6pwzxdaa40mwaxqy5h-python3.6-cram-0.7.drv’ failed

@GrahamcOfBorg build python2.pkgs.cram python3.pkgs.cram

@dotlambda are you on #nixos channel sometimes and if so, what's your id?

Sometimes, yes. It's dotlambda.

Included in https://github.com/NixOS/nixpkgs/pull/35198.


fix margins in two-column mode

Abstract and figure margin icons are not currently aligned properly.

This is (hackily) fixed. But we should test this a bunch still.


I'm working on an ESP32 HTTPS server using a simple example code. How do I solve this error? (CON-1218)

esp-idf/components/esp_https_server/include/esp_https_server.h:170:1: error: 'httpd_ssl_config_t' {aka 'httpd_ssl_config'} has no non-static data member named 'cert_select_cb'
170 | }
| ^
esp-matter/examples/apmatterhub/main/Https.cpp:192:33: note: in expansion of macro 'HTTPD_SSL_CONFIG_DEFAULT'
192 |     httpd_ssl_config_t config = HTTPD_SSL_CONFIG_DEFAULT();
|                                 ^~~~~~~~~~~~~~~~~~~~~~~~
ninja: build stopped: subcommand failed.
https_error.txt
how to solve this error .ccp

@vishnuprasadvp12345 Please for any IDF specific issues, raise an issue here: https://github.com/espressif/esp-idf/issues/
This repository is specific to the Matter related implementations


Flexible precision

Currently, it's not possible to have the user enter between 0 and 2 decimals. We're using this in a finance context, where often we specify bigger numbers like EUR 25.000. In these cases, it's not user friendly to require the user to type 2500000.
Would it be possible to add some flexibility in this regard?

If I understood correctly, you want to use dot to separate the decimal part. It's not possible, but if you do not need using decimals, you can set the precision to 0 and have the desired behavior.

No, i would be content to use any character as the decimal delimiter. What i would like to be able to do is allow the following inputs:
25,000 (25 thousand)
25,000.00 (25 thousand)
26,000,24 (25 thousand and 24 cents).
In our cases, supplying cents is added precision which is not always mandatory.

This would bring too much changes and I can't do it right now. I will avaliate in the future.

@cesarrew this feature would be necessary in my application as inputting data in tables or several inputs at a time becomes very tedious, requiring extra keystrokes for decimal values. seems like this is the same issue as https://github.com/cesarrew/ng2-currency-mask/issues/61


using next-i18next with Next.js 13

How we are going to use this package with Nextjs version 13 and how it will work with server components? Because I want my hole page use translation in server and get translated page from server.
previously, we were using this package like this.
export const getServerSideProps: GetServerSideProps = async ({ locale }) => {
return {
   props: {
      ...(await serverSideTranslations(locale as string, ["common", "login", "form"])),
    },
  };
};

... is there an issue with that?
Check the second page of the examples/simple...
should work as usual

the example is using pages directory. we can not use getServerSideProps inside app directory. so what will be the alternative?

Sorry, I don't get what you mean... can you maybe create a minimal reproducible example that shows the issue?

https://beta.nextjs.org/docs/upgrade-guide#migrating-from-pages-to-app

Feel free to start a PR addressing this.

Also with the new app directory approach AppProps is no longer passed to children (since _app and _document don't exist anymore), therefore the appWithTranslation HOC does not work.

Like said, feel free to start a pull request and contribute to this open source project...

I ran into this issue after upgrading to Next.js 13, where I'm still using pages

Like said, feel free to start a pull request and contribute to this open source project...

I get the why of your comments, "just make a PR" (I do it too!) - but in this case, it's a fundamental change in how this library works with the future Next.js, and I think it would be more appropriate if it were led by a maintainer.
Please don't take this as "please work for free for me"; it's the beginning of a discussion for making this library work with what Next.js will become, not a command to work on it.

That's why I said "...feel free to start a pull request..." ;-)

Before I start a PR, should this be moved to a discussion, maybe? Since the API will have significant changes, and maintainers should lead the design of those?


Coverage rate improvement for dispatch.py

Actually, not only test cases but also some code refine:

couchapp/commands.py: Increase the readability for table
couchapp/dispatch.py:
Let  function dispatch catch CommandLineError correctly. Previously, we will get the full trace stack when we issue `couchapp unkown_command``
Using except ... as ... syntax. The original syntax, except ... , ... is not compatible with python3. I will replace them gradually, if i encounter them

BTW, I can not understand the purpose of this [code] (https://github.com/couchapp/couchapp/blob/71cdf01610f6a409ef2bdd309a5cee610aa66ec5/couchapp/dispatch.py#L17-L20).

:+1: @iblis17 looks super fab. :smile:  Sorry for the wait. :watch:
Also, the NullHandler logger thing can go. It looks unused. Possibly it was used as an option for a "quiet" mode or some such. Since it's not in use, let's remove it. If we think of a need for it, we can bring it back. :wink:
One last thing. There's a merge commit in the list in this PR. If we can avoid those (use rebase, probably) that'd be super. Avoiding them makes for cleaner history on master. I'm going to merge this, though, in favor of keeping the ball rolling. :sunglasses:

I will remove NullHandler later. :)
I will notice the merge commit next time. :-o


Don't use mount propagation when run on k8s 1.7

This change is

Can we also do this in demo.sh?

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Taking back my comment. The demo uses 1.8 all the time

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Ajax sourced data for data Tables

Version information

Laravel: v5.6
Voyager: v1.1.0
PHP: 7.1
Database: 10.1.22-MariaDB- Debian 9.0

Description of problem

The server side pagination for Browsing tables is not as flexible as the DataTable Ajax Server side solution. The page does not need a reload before giving search results. Results can be downloaded in different standard formats, with the help of a few buttons. Also, sorting is much more faster and efficient with DataTables.
Proposed solution
DataTables has the ability to read data from virtually any JSON data source that can be obtained by Ajax. This can be done, in its most simple form, by setting the ajax option to the address of the JSON data source.
The ajax option also allows for more advanced configuration such as altering how the Ajax request is made.
Alternatives considered
Data Table has proven to be the best alternative for handling table's data.
Your team has done an excellent work, and it saved me from a lot of stress.
It'll be nice if you can add this feature to your next release.

This has been requested quite a few times, but its not easy because of the various formfields.
Definitely nothing for 1.x

Thanks for your response.
I hope one day, we'll find a work around..


Introduce Palash-Sharma

@lordhades11 this is mergable good work. Although you could have avoided the "wip" that is used when your work is in progress, but here the content was already complete.
No worries but we can ignore this for now, keep in mind next time.


AppsflyerConstants.AF_VALIDATE_PURCHASE value spelling incorrectly

Describe the bug
Kindly check the AppsflyerConstants.AF_VALIDATE_PURCHASE = "validePurchase" spelling  incorrectly. It causes the "_registerPurchaseValidateListener" cannot return correct result.
Expected value should be "validatePurchase".

Thanks for opening this issue, will fix it 👍


626 no null values in cookie

Both JsonWireProtocol and w3c protocol say to leave an entry off
rather than having a null value.
https://github.com/SeleniumHQ/selenium/wiki/JsonWireProtocol
https://w3c.github.io/webdriver/#add-cookie

The travis fail seems to be unrelated to this PR:
1) Facebook\WebDriver\WebDriverTimeoutsTest::testShouldFailGettingDelayedElementWithoutWait
Failed asserting that exception of type "Facebook\WebDriver\Exception\NoSuchElementException" is
thrown.

How does this happen? And what can I do to fix it?
The code coverage decreased even though every single line I touched is tested and I added an extra test. How does this happen? And what can I do to fix it?

With Chromedriver 74 binaries released, it now causes some cookie requests to fail without this pull request being merged and tagged.
https://chromium-review.googlesource.com/c/chromium/src/+/1366925/3/chrome/test/chromedriver/window_commands.cc#1564
As a workaround, you must manually set every cookie value to avoid null Set-Cookie items being sent.

Thanks @JorisVanEijden for the catch. I rebased the branch against current community branch, let's see if the Travis build now pass. If so, I will get it merged.

Merged, thanks @JorisVanEijden! :100:


[#4] Edit expense added with UI improvement of tabbar and dashboard

Looks good to me edit expense code looks good .


Dead link

[Enter feedback here]
How to use Environment Monitoring View Raw Logs
Dead URL Link

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

ID: 64b5b03d-9169-f94e-f999-63bc5a8e68ac
Version Independent ID: 177eb187-6962-ba30-7a63-86b0bf3452d7
Content: Monitoring and diagnostics tools in Lifecycle Services (LCS) - Finance & Operations | Dynamics 365
Content Source: articles/fin-ops-core/dev-itpro/lifecycle-services/monitoring-diagnostics.md
Service: dynamics-ax-platform
Product: ****
Technology: ****
GitHub Login: @meeramahabala
Microsoft Alias: meeram

Sally - Can you check this link? Thanks.

The dead link has been removed.


What is the difference between wasi-sdk and emscripten?

Hello,
I wanted to get more information on wasi-sdk and it's support on big endian platforms.
BE support was added to emscripten in this PR: https://github.com/emscripten-core/emscripten/pull/13413
emscripten uses llvm/clang to generate wasm binaries. From my understanding it also compiles musl libc to wasm and glues it all together with a generated js file which can directly be called with Node js, and it all gets executed by V8 runtime. Everything is little endian enforced by wasm standards and V8 is hard coded to reverse bytes accordingly on BE machines.
What is the difference between the output of wasi-sdk and emscripten and where does it stand in terms of supporting BE machines as well as C runtime? Does it also make sure libc is LE enforced?

/cc @sbc100

While Emscripten produces JS code to accompany the wasm files it produces, wasi-sdk doesn't produce any JS. Since wasi-sdk only produces wasm, it isn't affected by the issue that JS typed arrays are endianness-dependent in JS.
WebAssembly and WASI are little-endian, so implementations on big-endian platforms need to perform byte-swapping under the covers, and several of the major implementations indeed do this.

WebAssembly and WASI are little-endian
That't right. V8 is patched to reverse bytes on BE platforms when executing wasm itself.
We have also patched emscripten to handle Js typed arrays correctly on BE.

My only concern right now is related to runtime calls to functions outside of wasm, mainly libc.
If I'm not mistaken, libc is also compiled into wasm on emscripten so byte ordering will be covered by V8 at runtime.
How are such calls to libc or Wasi API handled by wasm-sdk? Are they compiled to wasm as well? I'm just wondering if we need to apply any patches to make sure LE ordering is enforced to any outside calls.

In wasi-sdk, libc itself is implemented entirely in wasm. There are calls to WASI APIs which may be implemented outside of wasm,  but the expectation is that the implementations of those APIs behave as-if they are little-endian. And in practice, the major implementations indeed do run on big-endian platforms and do the byte-swapping as needed.

Thanks for confirming. So how are WASI APIs outside of wasm compiled and handled?
i.e are they also Wasm binary files which get executed by directly V8, or are they generic binaries which could access memory in native BE order and mix byte orderings?

To my knowledge, V8 today does not have an implementation of WASI. In engines which do, such as Wasmtime, WASI is typically implemented in native host code, rather than wasm code, and it performs bytes-swapping on big-endian platforms so that it presents a little-endian API to wasm.

Just wondering how Node.js would execute a generated wasi-sdk binary such as this: nodejs/llhttp#93

Node.js includes https://github.com/nodejs/uvwasi as its WASI implementation.

Thanks for the link Richard,
Also thank you for the information @sunfishcode . Will close this issue now.


Postman file

You mention Postman but unfortunately I don't think there is an exported file I could import in Postman directly. Do you have a trick to generate / update the calls from the existing documentation in Postman ? I started to manually import the calls but it feels wrong as if something change in the API it won't be valid anymore.

Thanks for opening an issue.

You mention Postman but unfortunately I don't think there is an exported file I could import in Postman directly.

I'm unaware of a file importing feature with Postman. I'm talking about this Chrome app: https://www.getpostman.com/
There is a wiki page on How to Login that may help.

In admin > accounts there is a "create new" button in the top right, that will open a modal.


not able to get correct printer status

we are using cups to connect Toshiba B-SX4 printer via USB, but the printer status is always idle, even though the printer actually status is pause or head open, paper jam, etc.
and also the print job status is completed, but actually the printing is failed due to the printer error, like the printer status is pause or head open, paper jam, etc.
want to ask is it possible to get specific printer or job status?

@michaelrsweet could u help check on it, thanks!!

hi @zdohnal, thanks for reply, we installed CUPS 2.4.10 to raspberry pi5, then connect Toshiba B-SX4 printer via USB, the printer status in the CUPS website is always Idle, even though the printer actually status is pause or head open, paper jam, etc.
using IPP to do Get-Printer-Attributes, return idle
using IPP to do Get-Job-Attributes, return completed

is that mean Toshiba B-SX4 printer not support IPP-over-USB?

The status on the CUPS website is the status of the print queue installed in CUPS - it can be the same as with the actual printer status if the printer can send such information - a simple USB backend cannot do such a high-leveled thing, it only can report simple errors like if the printer is turned off or other USB related error.
In general the status message on the page is an internal status of the queue in relation to cupsd daemon, but it can match with printer status, if the printer and connection to it is able to share such information. IPP requests you did look like you sent the requests to the print queue object in cupsd, not to the actual printer. To get more information about the printer via USB the printer has to support IPP-over-USB and there has to be a proxy between IPP and USB like ipp-usb.
How to find out whether the device supports IPP-over-usb.

oh, checked lsusb -v output
the result seems like not support  IPP-over-USB
ref: https://docs.fedoraproject.org/en-US/quick-docs/cups-useful-tricks/#_how_to_find_out_if_my_usb_device_supports_ipp_over_usb

anyway, thanks for the clarification! @zdohnal


Make sure the stream is open before using it (close #146)

Added a bunch of guards against using .stream if it's null, which could happen if a call is made after the connection is closed

Missed the PR. Think this is fixed in master. Reopen if not :)


Register descriptor changes for all connected native streaming clients

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] Pull request title reflects its content
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Description:
The signal descriptor gets registered/updated in the packet streaming server&client under the following circumstances:

When an existing signal is registered in the streaming during the handling of a new client connection.
When a newly added signal is registered in the streaming, such as when a server FB is added via a client request.
If the initial event packet, generated during the creation of a server side reader upon signal subscription, differs from the descriptor registered in one of the two preceding cases
When the signal descriptor changes during active signal reading by streaming server.

The bug originated from a single packet reader on the server side serving multiple subscribed clients, generating one event packet per signal change; and these event packets were only sent to subscribers, leading to the new descriptors not being registered in the packet streaming server and client of the native streaming clients that were not subscribed to the signal.
For the FB's signal specifically, the first event packet contains nullptr descriptors since no signal is connected to the FB port initially. These nullptr descriptors are ignored by the packet streaming server&client, resulting in no descriptor being registered for the signal.
With the introduced fix, the event packets are now sent to all connected clients.

Bug was fixed by https://github.com/openDAQ/openDAQ/pull/262


MAINT: Add black pre-commit hook

Close #347.
I removed isort, since I believe ruff handles it. I removed   - id: double-quote-string-fixer from the pre-commit-hooks, since it conflicts with black. I also had to manually edit a couple lines to make ruff happy.

@dnicolodi You may want to comment or close #347.


AI editing

I noticed you used Llama 3 for editing. Manubot now has built-in support for AI editing, described in this manuscript. Because the editing is done within Manubot, you get a full record of what parts of the manuscript were AI edited.
It doesn't currently support Llama 3. The team is seeking funding to expand the capabilities, so that could be in scope for the future.

Very cool thank you for the information Tony!


Automated cherry pick of #7961: region: fix network schedtag not cleanup when network deleted

Cherry pick of #7961 on release/3.1.
#7961: region: fix network schedtag not cleanup when network deleted

Codecov Report

Merging #7965 into release/3.1 will decrease coverage by 0.82%.
The diff coverage is 4.32%.

@@              Coverage Diff               @@
##           release/3.1   #7965      +/-   ##
==============================================
- Coverage         7.47%   6.65%   -0.83%
==============================================
  Files              585     600      +15
  Lines            98936   92335    -6601
==============================================
- Hits              7396    6141    -1255
+ Misses           90967   85627    -5340
+ Partials           573     567       -6

Flag
Coverage Δ

#aFlag
6.65% <4.32%> (-0.83%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/cloudcommon/db/quotas/handler.go
0.00% <0.00%> (ø)

pkg/cloudcommon/policy/policy.go
1.39% <0.00%> (-0.19%)
:arrow_down:

pkg/cloudcommon/policy/resources.go
0.00% <ø> (ø)

pkg/cloudprovider/objectstore.go
2.53% <0.00%> (+0.01%)
:arrow_up:

pkg/cloudprovider/securitygroup.go
0.00% <0.00%> (ø)

pkg/compute/guestdrivers/esxi.go
1.65% <0.00%> (-1.09%)
:arrow_down:

pkg/compute/guestdrivers/managedvirtual.go
0.00% <0.00%> (ø)

pkg/compute/models/buckets.go
1.16% <0.00%> (-0.08%)
:arrow_down:

pkg/compute/models/cloudaccounts.go
0.78% <0.00%> (-0.01%)
:arrow_down:

pkg/compute/models/cloudproviders.go
0.96% <0.00%> (+<0.01%)
:arrow_up:

... and 654 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 a1b2a4d...0ac14fe. Read the comment docs.


More descriptive Exception handling?

It looks like createUser(User user) and updateUser just throw a ZendeskException without any messages if the update/create fails. I'm running this API as a periodic job (every 15 minutes), so it would be helpful to have descriptive messages, possibly returning the HTTP response code or the JSON response body on user creation. If this is already available, how can I get this information on user creation/update?

@jordaniac89 the ZendeskException should contain this information already as part of it's body (.getBody()) -- if you need more information, you can also enable DEBUG level logging.


Question: Can you publish the latest commits?

Hey folks, can you publish to npm? There are changes that I'd like to leverage.
Thanks!

bump @HyperBrain

Hi @Enase , will do tomorrow. Please make sure that there is a label and the package.json version is correct in master so that I  can publish a new release.
Can you prepare release notes?

Hi @HyperBrain
Pls merge https://github.com/serverless-heaven/serverless-aws-alias/pull/173/
Release notes you can find here

Merged. Proceeding now :-)

Published to NPM and created a GitHub release including the release notes.
Closing


:sparkles: Featre/analyzer task runner validator

Just to get the initial code up there

This is looking correct, I think it can merge after fixing the conflicts
THings to note:

You need to have the kai-analyzer-rpc binary built and pass it in to code plan
You need to have the rulesets on disk and pass them in to kai.

There seems to be intermintent errors in the pipe between kai-analyzer-prc and the client. I am looking into these things now, but I think having this in to start building off of for the parent child stuff and fixing a single incident may be worth it even with the issues.
@fabianvf @JonahSussman @pranavgaikwad

I agree with you, but also it didn't feel like a task runner lol

We need to do a follow-up based on the above comments.
Task Runners should not have the specifics of agents in their implementation. Instead they should be using one or more "agents".
This moves us closer to making the "agents" LLM calls more composable.
I think for us to do this, we need to have a good interface, between taking in strucuted data vs LLM Output.
s


Disable overcommit accounting on E2 VMs

Instance setup: call sysctl vm.overcommit_memory=1 if the machineType starts with 'e2-'

/packagebuild


Unexpected behavior for path containing repeated edge IDs

Hello,
First off, thank you so much for maintaining this library! You have done some truly excellent work, and your library has been a joy to use.
However, I have encountered a small issue when rendering paths on a graph. Here is a simplified example to showcase the issue.
Consider an agent traversing a graph with 3 nodes and 2 edges as follows:
const data = {
  nodes: {
    node1: { name: 'Node 1' },
    node2: { name: 'Node 2' },
    node3: { name: 'Node 3' }
  },
  layouts: {
    nodes: {
      node1: { x: 100, y: 100 },
      node2: { x: 300, y: -300 },
      node3: { x: 500, y: 100 }
    }
  },
  edges: {
    edge1: { source: 'node1', target: 'node2', label: 'Edge 1' },
    edge2: { source: 'node2', target: 'node3', label: 'Edge 2' }
  }
}

If the agent travels from Node 1 to Node 2 to Node 3 (via Edge 1 and Edge 2), everything works as intended.
const paths: vNG.Paths = { p: { edges: ['edge1', 'edge2'] } }

But when the agent gets a bit lost and backtracks over the same edge multiple times, things get unusual. If the agent moves from Node 1 to Node 2 to Node 1 to Node 2 to Node 3, then the following is rendered:
const paths: vNG.Paths = { p: { edges: ['edge1', 'edge1', 'edge1', 'edge2'] } }

Because the library specifies paths as a sequence of edges rather than nodes, it must choose which node should be the start of the path. In this example, Node 2 is treated as the start, and a false new edge between Nodes 1 and 3 is created to handle the incorrect assumption.
Is there any way for me to specify which node should be at the start of a path? Or perhaps is there another way I can define a path based on nodes rather than edges?
Thank you again for your hard work maintaining this!

Hi @kyle42walker,
Thank you for the detailed report!! Sorry to keep you waiting.
The implementation was not intended to repeat the same edge more than three times.
Please check v0.9.9 to see that it has been corrected to the expected behavior.
This fix was implemented by revising the method of calculating the first node.

Is there any way for me to specify which node should be at the start of a path? Or perhaps is there another way I can define a path based on nodes rather than edges?

Since this library allows multiple edges to be placed between two nodes, the path is designed to specify which edge it passes through.
This time, it was possible to handle the case by revising the calculation, but in the future, if a case arises where the calculation cannot be specified by any means, we may consider allowing the specification of the first node or a way to specify based on the node....
Thanks again for the report!

Thank you very much! That seems to have completely fixed my issue. I really appreciate your work on this!
Adding more ways to describe paths would be an awesome feature to add eventually. I look forward to seeing it someday!

Thank you very much for the fix! I faced this issue yesterday and I found your new version this morning.
Your work is amazing!


Publish non-root productpage image

Describe the feature request
There was a change enabling productpage to be run as nonRoot: https://github.com/istio/istio/pull/16326
Apparently this version of productpage was never published to DockerHub. Would it be possible to publish this version? (so that I don't have to build it myself :))
Can be reproduced via:
docker run -it  istio/examples-bookinfo-productpage-v1:latest cat productpage.py

This is essentially the same as https://github.com/istio/istio/issues/23232,. lets track there. Thanks!


Overview and abstract

The docs motivate the project, but a more concise explanation would be nice now that we've got a 50+ page spec on our hands :joy:

Handling this in #645

Closed by #645


Drawing "undesired" shapes in mouse mode

I am following the development of this tool with interest and have briefly tested various versions, including the latest 0.2.4 on Windows 11 24H2. In all the versions I tested, I noticed what I consider to be a bug. Here’s what I do:

I start Riter and draw something on the screen (freehand, lines, rectangles, ...)
I select the command to use the mouse normally (first button on the left)
In "mouse" mode, by clicking (multiple times) on the drawn shapes, almost always Riter starts drawing shapes again (especially rectangles!) even though the corresponding button has not been selected.

I don't understand if this happens only to me or if it is indeed a bug in the program.

it is duplicate


remove scl usage and link git instead

This commit removes the usage of scl enable and insteads links the git
version in the image. Using scl enable cause an issue where the npm
process was not running as process 1 and signals got ignored.

Steps to verify:
$ make test

Build a booster (I'm using nodejs-rest-http) and add a signal handler in app.js and commit the change:
process.on('SIGTERM', function(signal) {
  console.log('Server recieved SIGTERM');
  process.exit(22);
});

Build and run:
$ s2i build . bucharestgold/centos7-s2i-nodejs:latest nodejs-rest-http
$ docker run nodejs-rest-http

Stop the container:
$ docker ps
$ docker stop <container_id>

You should see the following in the console for  nodejs-rest-http:
Server recieved SIGTERM
npm info lifecycle<EMAIL_ADDRESS>Failed to exec start script
npm ERR! code ELIFECYCLE
npm ERR! errno 22
npm ERR<EMAIL_ADDRESS>start: `PORT=8080 node ./bin/www`
npm ERR! Exit status 22
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!


Support of device change setup

Added support of zone change by new input "zone" for accessory.
Readme updated
Unfortunately, not possible to run accessory multiple time due to connectivity conflict.

Everything seems fine with this commit, except for one problem.
Instead of calling .toString() on every endpoint, instead you could call it when assigning the zone from config (e.g zone = config["zone"].toString())
Make these changes and I'll merge the pr


A plugin for a tornado effect on a (N)PC

Is your feature request related to a problem? Please describe.
We could have a tornado effect centered on a single (N)PC, applied to outfit parts, hairs, by spells, scrolls, powers.
Describe the solution you'd like
We could have a plugin for FSMP applying a tornading wind effect to outfit parts, hairs, ...
Describe alternatives you've considered
None.
Additional context
None.

I am working on this right now! A system to attach generic force fields to any model. Statics, projectiles, magic effects... I've attached a whirling force to the Blizzard spell, for example.


Query AuditEntries in different contexts

I am using Audit tables in a different context of the tables being audited.
It works fine! But when I try to retrieve audit entries I receive the following error:
The entity type Customer is not part of the model for the current context.
Here is part of the code:
var item = _db.Customer.Where(w => w.CustomerId = 1).FirstOrDefault();
var auditEntries =_dbAudit.AuditEntries.Where(item).ToList(); //at this line the error occurs.
Customer is at _db context and Audit is at _dbAudit context.

Hello @EdsonMiranda ,
Thank you for reporting, unfortunately that's currently a limitation of our library when you are using different contexts ;(
Best Regards,
Jonathan

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function

Any workaround or suggestion to retrieve audit data on situations like this?

One way is to directly retrieve it using LINQ syntax: https://dotnetfiddle.net/5AfB7e

Thanks for the sample, I was just writing a code like that.


Delete empty error_handler.rb

gems/sorbet-runtime/lib/types/private/error_handler.rb is empty. It appears that it was intended to be deleted in https://github.com/sorbet/sorbet/pull/1401, but was left empty.
Motivation
Remove cruft
Test plan
Existing automated tests

Thanks!!


Add apache pulsar based indexing service

Be able to index records by reading a set of pulsar topics.
https://pulsar.apache.org/

I am not too familiar with Pulsar, but if it has a partition / offset based scheme like Kafka or Kinesis, then it should be pretty straightforward to add using the same framework.

it has a similar concept with cursors.
https://streaml.io/blog/cursors-in-pulsar

We have use cases to integrate with our internal version of Pulsar. @aahmed-se Are you working on this? If not, I was going to take a stab at it.

@niketh it's on my radar, but don't have the bandwidth right now. You can go ahead.

It makes sense to implement this as a separate task and supervisor service. The characteristics of pulsar are different as compared to kafka. For example running pulsar in a shared subscription, the consuers can read messages from any parition. The need for maintaining per consumer offsets etc are not needed.

@aahmed-se Sounds good, I will take a stab at it.

Hey all my use case also needed to integrate druid with pulsar . Wanted to know did you guys have any luck doing that ?

Anything I can do to help out with this? I'm also very interested. :)

@joshuadunham You can take a stab and implementing it bet to look at kinesis or kafka ingest integration in druid and replicate it , it should not be that difficult.

Hi, I am working on this and having some progress with the Reader interface of pulsar client.
https://github.com/rueian/incubator-druid/commits/pulsar-indexing-service
May I create a PR after finishing the test cases?

@rueian are you making changes to pulsar for this , if not then the code should be posted in druid itself.

@rueian Please do go ahead and open a PR, especially if you have something working & well tested. Thanks for your interest in contributing!

Any updates on this one? I'm new to both Druid (recently heard about it never used it) and Apache Pulsar (this one at least I used), and I would love to do a test run but I heavily depend on Pulsar. If this is forgotten about I might research myself and try to do something but it's gonna take a lot of time until I figure things.

Sorry for no follow up from me.
However I am still blocked by something else. Please feel free to step in.

@niketh Were you able to make any progress on this? My team is very interested in this capability.

I'm interested in taking this up.
My research leads to believe the best way to implement this is building on the SeekableStream abstraction. Now on the surface this may appear like an impedance mismatch as Pulsar is primarily built around managing offsets/consumer state on the broker side but I still think the SeekableStream approach is best for Druid because it best suits it's notions of tasks and segments.
The way I think this should be implemented is to have the supervisor create a task per partition of the Pulsar topic, each task will then use an exclusive, non-durable subscription that consumes from that specific partition. In this way seeking to a specific message ID can be supported cleanly, which is required to support task resumption and idempotency.
This will result in one segment per task however so users of this indexing service will likely want to enable compaction.
@sijie does this approach sound correct to you?
/cc @gianm @jsun98 @dclim as you gentlemen worked on the SeekableStream abstraction and would appreciate your thoughts.

@josephglanville Yes. The approach looks right to me.
An alternative approach is to integrate Druid with Pulsar via Kafka-on-Pulsar by leverage Druid's existing Kafka integration.

each task will then use an exclusive, non-durable subscription that consumes from that specific partition

Does this mean the topic would be non-persistent? I'm wanting to better understand what is meant by "non-durable" subscription.

@devinbost The topic pesistence is set at creation
Persistent Topic: persistent://property/cluster/namespace/topic
All messages will be stored on disk
Non persistent: non-persistent://property/cluster/namespace/topic
Messages will not be persisted to Disk
The durability refers to the cursor persistence. Durable subscriptions have the cursor persisted

If a broker restarts from a failure, it can recover the cursor from the persistent storage (BookKeeper), so that messages can continue to be consumed from the last consumed position.

While non-durable the cursor is lost on bookie restart.

Once a broker stops, the cursor is lost and can never be recovered, so that messages can not continue to be consumed from the last consumed position.

Since druid's supervisor creates short lived tasks and we want to support resumption from any point in the stream, we require a non-durable subscription mode. durable subscription cursor position is enforced by the bookie and cannot be overridden, meaning we could not support resumption from any point in the stream.  So to properly support resiliency and idempotent resumption, we need to use the non-durable subscription.

We'd still like this feature.


added flake8 description

More description about pre-commit compliance, flake8 and necessity to have various python version for tox.

I believe it's not necessary to have several python versions installed because tox will install them automatically in a separate python environment.

@gabrieldemarmiesse uhmm don't seem like it to me, maybe in you test environnement but not locally.
With a python 3.5 intepreter (minimal)

Without a python3.5 interpreter

@davebulaval The tests will run on all python versions that you have installed. Yes you will get an error for each missing python version, but that is not a problem. It should rarely be necessary to run the tests for more than one python version, especially since we have dropped support for python 2.
So just ignore these errors.

Yes, but in my case, I was failling a test since I was using mock method that was added in python 3.6.
It could just help user to know that you (might) need all the python version to execute tox and prevent losing time in debugging.
Also, knowing the style inforcement can be usefull to prevent misunderstanding of the pre-commit output (since it's not always really clear).


Check vapor pressure of mixed dried sample before going to tube furnace -> camera+ethanol sensor

Proposed solution:

[ ] Heat significantly longer for tube furnaces sample
[ ] Check vapor pressure of mixed dried sample before going to tube furnace, maybe camera+ethanol sensor

If left unchecked, there is a possibility that ethanol remains inside the sample. This can lead to an explosion when the vacuum is initiated in the tube furnace.


Filings dates and "submissions_index.csv"

Several of your examples such as examples/human_readable.ipynb start with df = pl.read_csv('data/submissions_index.csv'). What is this file and where do I find it? It looks very useful to retrieve filing dates.
In a closed issue from 1 month ago you claim to have fixed the filenames and now filing dates should be in the filenames (https://github.com/john-friedman/datamule-python/pull/12). The changes are still not in the package. I already downloaded 300GB-worth of filings and now I need to fix their names because there are no dates. Any pointers?

Hi @keeper90, sorry for the confusion with filing dates. For issue 12, @anirudj added dates to be stored in filenames. I later replaced this change with a  save_metadata argument to the downloader as users requested more metadata. Here is a link to the docs.
downloader.download(form='10-K',output_dir='10-K',date=('2010-01-01','2010-01-31'),save_metadata=True)

Here's a snippet of the metadata.jsonl file

What filings did you download and using what method? I can fix it for you.

I got 10-Ks. I ended up modifying the code myself. It is working but is fairly slow. Any way to do this fast? Think getting metadata for all 10-Ks

One option is to modify the params for the efts endpoint https://efts.sec.gov/LATEST/search-index?forms=10-K&startdt=2024-09-13&enddt=2024-12-31. You should be able to do 10r/s which is 1000 file dates / seconds. There are 200,000 10-ks or so, so it should complete in a few minutes.
Btw, how long did it take you to download the 10-Ks originally? Not sure if you used the bulk downloader or not.


Update network connectivity from VPN to Global Peering

In this document, you are recommending using VPN to setup VNET to VNET communication in a DR scenario. This should be replaced to Global Vnet Peering, which is an easier and cheaper option to configure communication.

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

ID: 88e51bc6-b077-a976-c890-a02e7d71b88e
Version Independent ID: f3af0a93-edc2-fddf-8690-d70ac22f8a2b
Content: Configure a SQL Server Always On availability group across different regions - SQL Server on Azure VM
Content Source: articles/azure-sql/virtual-machines/windows/availability-group-manually-configure-multiple-regions.md
Service: virtual-machines-sql
Sub-service: hadr
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

Thanks for brining this to our attention. We will investigate it further and update you shortly.

@rodrigoffonseca  - Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can update the document accordingly.

Hi @rodrigoffonseca , thanks for contacting Microsoft! We have processed a change to the documentation that should be live later this week :) I'll close out this Git Issue for the time being but please feel free to comment should you need anything further.
Thanks again for reaching out and I hope you have a wonderful rest of your day!
Masha from the SQL Docs team
#reassign:rajeshsetlem
#please-close


Took a crack at #608

I'm on a windows machine so I cannot set up a dev environment to test this myself, if @Qqwy or someone else can test this implementation for me I would appreciate it.

I will close this PR due to inactivity. I someone want to continue this work in the future, feel free to open another PR.


Add space between words

Learn Build status updates of commit d4135dc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/relational-databases/backup-restore/create-a-differential-database-backup-sql-server.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Looks good; thanks, @Luzemin


Check that file exist before opening

close #646

Let's also tag a new release after merging this~

A new release? should I make it
Changes since 2.14.1:

  Fix:
   - Show open inline diff if it already open form status dashboard
   - Push tags command is not blocking
   - added self.get_short_hash to honor core.abbrev settings (#642)

  Other:
   - Sort branches by recent commited (#632)
   - Check that file exist before opening (#648)

  Improvement:
   - Remove some clutter from debug.log (#635)
   - Warn the user when we have permission error (#636)
   - it is not necessary to check if HEAD is rebased
   - use message_dislog for show the messages
   - do not allow squashing merges

  Contributors:
   - Simon
   - Juan Pumarino
   - Pavel Savchenko
   - Vlad Tsepelev
   - Randy Lai

New commit a then a new tag

Sure!


Error: Get http://localhost:8080/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%!D(MISSING)TILLER: dial tcp <IP_ADDRESS>:8080: connect: connection refused

Hi there,
I would like to report a bug. Here are the logs.
helm list -- NOT OK
[root@london-node-227 ~]# helm list
Error: Get http://localhost:8080/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%!D(MISSING)TILLER: dial tcp <IP_ADDRESS>:8080: connect: connection refused
helm version -- OK
[root@london-node-227 ~]# helm version
Client: &version.Version{SemVer:"v2.9.0", GitCommit:"f6025bb9ee7daf9fee0026541c90a6f557a3e0bc", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.0", GitCommit:"f6025bb9ee7daf9fee0026541c90a6f557a3e0bc", GitTreeState:"clean"}
[root@london-node-227 ~]#
kubectl version -- OK
[root@london-node-227 ~]# kubectl version
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.2", GitCommit:"81753b10df112992bf51bbc2c2f85208aad78335", GitTreeState:"clean", BuildDate:"2018-04-27T09:22:21Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.2", GitCommit:"81753b10df112992bf51bbc2c2f85208aad78335", GitTreeState:"clean", BuildDate:"2018-04-27T09:10:24Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
helm init --debug  -- OK
[root@london-node-227 ~]# helm init --debug
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
creationTimestamp: null
labels:
app: helm
name: tiller
name: tiller-deploy
namespace: kube-system
spec:
replicas: 1
strategy: {}
template:
metadata:
creationTimestamp: null
labels:
app: helm
name: tiller
spec:
automountServiceAccountToken: false
containers:
- env:
- name: TILLER_NAMESPACE
value: kube-system
- name: TILLER_HISTORY_MAX
value: "0"
image: gcr.io/kubernetes-helm/tiller:v2.9.0
imagePullPolicy: IfNotPresent
livenessProbe:
httpGet:
path: /liveness
port: 44135
initialDelaySeconds: 1
timeoutSeconds: 1
name: tiller
ports:
- containerPort: 44134
name: tiller
- containerPort: 44135
name: http
readinessProbe:
httpGet:
path: /readiness
port: 44135
initialDelaySeconds: 1
timeoutSeconds: 1
resources: {}
status: {}
apiVersion: v1
kind: Service
metadata:
creationTimestamp: null
labels:
app: helm
name: tiller
name: tiller-deploy
namespace: kube-system
spec:
ports:

name: tiller
port: 44134
targetPort: tiller
selector:
app: helm
name: tiller
type: ClusterIP
status:
loadBalancer: {}
...
Creating /root/.helm
Creating /root/.helm/repository
Creating /root/.helm/repository/cache
Creating /root/.helm/repository/local
Creating /root/.helm/plugins
Creating /root/.helm/starters
Creating /root/.helm/cache/archive
Creating /root/.helm/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Adding local repo with URL: http://<IP_ADDRESS>:8879/charts
$HELM_HOME has been configured at /root/.helm.

Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.
Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
Happy Helming!

Am I missing anything?

FYI, I installed my k8s cluster via kubeadm v.1.10.2 + Flannel cni

closing as a duplicate of #3985 which was fixed in #3990. For now, please use the following workaround when running helm init for the first time: helm init --service-account default. Thanks!

This has been fixed in helm v2.9.1, which is available here: https://github.com/kubernetes/helm/releases/v2.9.1
Thanks!

I have updated to V2.9.1,But problem still existed.
openthings@openthings:~/openthings/helm-charts/stable$ helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
openthings@openthings:~/openthings/helm-charts/stable$ helm list
Error: Get http://localhost:8080/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%!D(MISSING)TILLER: dial tcp <IP_ADDRESS>:8080: connect: connection refused

I am using:
Ubuntu 16.04.3 LTS
Kubernetes 1.10.2
Helm 2.9.1

I remembered that I have resolved this issue a few months ago.
To be honest, I think that Helm was not yet stable at that time, and I am not confident to use it - even though the concept of package manager on k8s is very sexy by itself.
I will give it another shot pretty soon once I find some time to re-investigate k8s. And I will keep you updated.

Hi Tamama, could u pls let me know the solution. I am facing the same issue. Helm version is v2.14.2

That was ages ago... :(
This did the trick for me last time...
helm init --service-account default
helm list

@subravi92  me too.I am using 2.14.2.
It works in my local PC.but when in bitbucket pipeline,it fails

echo 'Error: Get http://localhost:8080/api/v1/namespaces/kube-system/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: dial tcp [::1]:8080: connect: connection refused'
Error: Get http://localhost:8080/api/v1/namespaces/kube-system/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: dial tcp [::1]:8080: connect: connection refused

@zffocussss , I was able to resolve the issue.it was due to certificate issue. May be u would need to check the certificate on server side.

This solved it for me
update-alternatives --set iptables /usr/sbin/iptables-legacy

getting the below error. Can someone look into the issue
Error: Get https://<IP_ADDRESS>/api/v1/namespaces/helm/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: x509: certificate signed by unknown authority
[UAT:~]> helm version
Client: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}
[UAT:~]> kubectl version
Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.12", GitCommit:"e2a822d9f3c2fdb5c9bfbe64313cf9f657f0a725", GitTreeState:"clean", BuildDate:"2020-05-06T05:17:59Z", GoVersion:"go1.12.17", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.12", GitCommit:"a8b52209ee172232b6db7a6e0ce2adc77458829f", GitTreeState:"clean", BuildDate:"2019-10-15T12:04:30Z", GoVersion:"go1.11.13", Compiler:"gc", Platform:"linux/amd64"}


H100 Hub Siren Broken After App Update to 2.10.0

-->
Version of the integration
v2.10.0
Configuration
H100 hub
Firmware - 1.3.9 Build 230522 Rel. 103415
Not sure where this is, im looking in custom_components/tapo/ but cant see a yaml file....if you can point me in the right direction, happy to supply

Describe the bug
Having updated to v2.10.0 of this plugin, the siren is no longer working from home assistant.
siren.smart_hub_siren is showing the following error:
"This entity is no longer being provided by the tapo integration. If the entity is no longer in use, delete it in settings."
Its reporting temp and signal strength fine, and ive just added a temp sensor it picked up automatically as well.
Debug log

2023-10-15 19:39:18.240 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-10-15 19:39:18.240 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration tapo which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-10-15 19:39:18.240 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration tapo_p100_control which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-10-15 19:39:18.241 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant.


close nav panel on route change

Listens to next/router events to close the nav panel on a route change. Makes browsing on mobile a bit smoother.

LGTM! 🚀