User/Password authentication not working

Client fails to connect with user name password. Looking at the logs in NATS it seams that the user name is coming in as an empty string, same could be happening to the password.
[1] 2021/02/13 00:44:22.329767 [DBG] xxx.xxx.xxx.xxx:59321 - cid:69 - Client connection created
[1] 2021/02/13 00:44:22.335470 [ERR] xxx.xxx.xxx.xxx:59321 - cid:69 - authentication error - User ""
[1] 2021/02/13 00:44:22.335904 [DBG] xxx.xxx.xxx.xxx:59321 - cid:69 - Client connection closed: Authentication Failure
var conn = await connect({
servers: ["ws://nats_address:4222"],
user: "my-user",
pass: "my-password",
verbose: true,
debug: true,
ignoreClusterUpdates: false,
});

Why are you connecting to the regular port? If you want to use websocket, you should connect to the websocket port.
Note that websocket is not yet released, only available from the NATS Server main branch. It will be available in the 2.2.0 release available "soon".
Here is link to documentation PR that is not yet merged: https://github.com/nats-io/nats.docs/pull/216

Appreciate the quick response! Do you have any estimate on when the official 2.2.0 release will be out? I really hoped I could make use of this feature for a POC I'm currently working on.

If it is a POC, there is nothing that prevents you from building from the main branch, or if you want a docker image, you can use our nightly builds: docker pull synadia/nats-server:nightly

Just did a build, just curious on when the release may come out. POC may go into production in a week or two if all goes well.

I can't give you a date, we were planning to release this week, but it may now be sometimes next week. But again, no firm date.
Were you able to connect properly when connecting to websocket port?

I understand, I was just curious. Yes I've build the image from the latest main and dialed in the config it's looking really good now I'll do some testing next week, but really happy with the ws addition, looking forward to see what we can do with it.
Thanks for the guidance, and the quick response!

This is a different issue, but i ran a little test and it looks like messages published over WS don't get received by my client connected over NATS, but if I connect another client with the same credentials and permissions over NATS the messages are received by the listener. Is there any special configuration that needs to be done to enable communication between WS connections and NATS connections?

Few questions:

Are you able to receive the messages from a WS client subscriber? If so, is it using the same user than the WS publisher? If it is, have you tried with the user that you are using for NATS subscribers?
Could you share your configuration and which users you are using in your clients?

Note that messages do not traverse accounts (unless they are explicitly configured to export/import), so if the users that you are using in your NATS clients are bound to a different account than the user/account of the WS publisher, then the behavior is expected. More information about accounts: https://docs.nats.io/nats-server/configuration/securing_nats/accounts

for the current use case I don't need the client to receive any messages from BE unless is a response to a request.
I have 2 accounts set up, however my WS client and my service client are logging into the same account www as browser and service respectively. I have also connected a nats client to the with the browser user and it's able to receive messages where the WS client is not. config below:
listen: <IP_ADDRESS>:4222
http: <IP_ADDRESS>:8222
client_advertise: nats-public-address
accounts: {
www: {
SERVICE = {
publish = [">", "> >"]
subscribe = [">", "> >"]
}
BROWSER = {
publish = ["browser.telemetry.>", "browser.telemetry.> lb.>"]
subscribe = "_INBOX.>"
}
users: [
{ user: browser, password: $WWW_BROWSER_PASS, permissions: $BROWSER, allowed_connection_types: ["WEBSOCKET", "STANDARD"] }
{ user: service, password: $WWW_SERVICE_PASS, permissions: $SERVICE, allowed_connection_types: ["STANDARD"] }
]
},
backend: {
users: [
{user: be_service, password: $BE_SERVICE_PASS, allowed_connection_types: ["STANDARD"]}
]
},
}
cluster {
cluster_advertise: $SERVER_IP
listen: <IP_ADDRESS>:6222
authorization {
token: $NATS_SERVER_PASS
timeout: 2
}
routes = [
$NATS_ROUTE_SERVER
]
no_advertise: false
connect_retries: 20
}
websocket {
listen: <IP_ADDRESS>:4000
no_tls: true
same_origin: false
compression: true
handshake_timeout: "2s"
}

In the list below, there are non valid NATS subjects:
SERVICE = {
    publish = [">", "> >"]
    subscribe = [">", "> >"]
}
BROWSER = {
    publish = ["browser.telemetry.>", "browser.telemetry.> lb.>"]

Spaces are not allowed in NATS subjects.
Anyway, I used your config (minus cluster section that I don't need for single instance and replaced passwords with "browser" and "service" for the browser and service users respectively.
I started a NATS subscriber on ">" connecting using the user "service", and sent a message on "browser.telemetry.device1" from a websocket client connecting using user "browser" and it worked fine.
You wrote:

however my WS client and my service client are logging into the same account www as browser and service respectively. I have also connected a nats client to the with the browser user and it's able to receive messages where the WS client is not. config below:

If you connect your NATS client with the "browser" user, it should be able to subscribe only to subjects matching "_INBOX.>", given the permissions defined. So what is the WS publisher is sending to, since it can only publish on "browser.telemetry.>". This is really confusing.
Would you mind being more specific on what application is sending, using which user, and sending on what subject, and same for the application receiving: which user, which subject.
Also note that you could run the server with -DV and provide the logfile, which may help explain why your app is not receiving messages.

For the subjects config I've followed this doc  from what I understand from it is that you list the allowed queue groups after the space, is that accurate?
So here is how everything is connected.

there is a web client connecting over WS using user browser messages shall be received by a .net core app connected over nats on 4222 using user service.
browser user only publishes messages to browser.telemetry.something from web app using nats.ws. I can confirm the connection is established by checking server logs, I can also verify data is send over web socket by looking at the network traffic. I have allowed the "_INBOX.>" subject in case I need to make a request from browser, but currently not used.
service subscribes to browser.telemetry.> using queue group lb.telemetry from a .net core app over nats on port 4222
both browser and service are users in the www account.
when nats.ws is used to push messages on  browser.telemetry.something , my .net service doesn't receive any messages connected as service user.
when I use another .net core app to connect to nats on port 4222 (just so i can verify permissions are working) and publish messages on browser.telemetry.something I'm able to receive the messages with the app connected with service user
It appears that when connecting with browser user over a WS messages don't get properly routed to the nats subscribers (connected on 4222), but when same credential is used to connect over nats messages are delivered as expected.

For the subjects config I've followed this doc from what I understand from it is that you list the allowed queue groups after the space, is that accurate?
I was able to resolve the issue by reloading the config and restarting the service, it looks like the issue was most likely on my end with a stale config. Now everything works as expected and messages are reaching the destination.

you list the allowed queue groups after the space, is that accurate?

Yes, but only for the subscribe permissions, so the use of it in the publish permissions below is incorrect:
SERVICE = {
    publish = [">", "> >"]
}
BROWSER = {
    publish = ["browser.telemetry.>", "browser.telemetry.> lb.>"]
}

I would suggest that you remove (even if you got things working) so that it does not introduce confusion later on.

This makes sense, I'll definitely clean up my config. Thanks for clarifying this.


Persist Grafana dashboards

Motivation
We'll have some dashboards that will contain different data that we're interested in monitoring. To do that we need a way of defining and persisting Grafana dashboards.
Proposal
Create dashboards in Grafana, export the JSON, add it to our codebase and make sure that JSON gets imported when Grafana is initialized
Infra side PR: https://github.com/linera-io/linera-infra/pull/20
Test Plan
Deployed locally, saw that the imported dashboard was there

Very nice! A reminder to update linera-infra after you merge :)


RuntimeError

I've been using it on google colab and it worked perfect but recently I get the following error message. what has changed?
Traceback (most recent call last):
File "/usr/local/bin/whisper-ctranslate2", line 8, in
sys.exit(main())
File "/usr/local/lib/python3.10/dist-packages/src/whisper_ctranslate2/whisper_ctranslate2.py", line 547, in main
result = transcribe.inference(
File "/usr/local/lib/python3.10/dist-packages/src/whisper_ctranslate2/transcribe.py", line 170, in inference
for segment in segments:
File "/usr/local/lib/python3.10/dist-packages/faster_whisper/transcribe.py", line 941, in restore_speech_timestamps
for segment in segments:
File "/usr/local/lib/python3.10/dist-packages/faster_whisper/transcribe.py", line 445, in generate_segments
encoder_output = self.encode(segment)
File "/usr/local/lib/python3.10/dist-packages/faster_whisper/transcribe.py", line 629, in encode
return self.model.encode(features, to_cpu=to_cpu)
RuntimeError: Library libcublas.so.11 is not found or cannot be loaded

Hi, did you figure this out? Getting the same error.

Yeah, you need to downgrade cudas to libcublas 11. Just copy the code below after the usual install:
!sudo apt-get install libcublas11

Thank you!

I faced the same problem (after getting a hold of cudnn and zlibwapi), but the solution turned out to be really simple.
Cublas is bundled with cuda. The file just has a different name depending on the version. I can't use cuda 11 because that's when they stopped supporting windows 7. So instead i just made a copy of cublas64_10.dll and renamed it to cublas64_11.dll
I don't know where this file is imported/used, but it seems weird to have a seemingly hardcoded filename instead of just, idk, letting cuda fetch its own library?


Broken link on index page of XD specifics APIs

Submit an issue
Topic
This is an issue regarding:

[x] The tutorials contained within this repo.
[ ] The samples contained within this repo.

Versions

[ ] Supported XD version(s):
N/A

Description of the issue
Borken link for viewport.md
https://github.com/AdobeXD/plugin-docs/blame/master/reference/xd-index.md#L12
- [viewport](/reference/ciewport.md)

Proposed solution or attempted solutions that failed
- [viewport](/reference/viewport.md)

Looks like this one was addressed in a PR a while back. Thanks!


Build errors following the release of 1.0.9

Thank you for your work on this crate! It's very useful for building HALs :)
Unfortunately with the release of 1.0.9 our builds over at a esp-hal have begun failing. The builds were working yesterday, and today we get this output:
https://gist.github.com/jessebraham/8fe1d8575c923e788a799262736a7a5e
I cloned this repo and set a local path for [patch.crates-io.paste], and I'm able to reproduce the build errors. Changing let mut contains_paste = false to true instead results in the build succeeding. I'm not really familiar with the inner workings of the crate and this does not seem like a solution, but I'm hoping it may help locate the problem.
pub fn paste(input: TokenStream) -> TokenStream {
    let mut contains_paste = false;
    let flatten_single_interpolation = true;
    match expand(
        input.clone(),
        &mut contains_paste,
        flatten_single_interpolation,
    ) {
        Ok(expanded) => {
            if contains_paste {
                expanded
            } else {
                input
            }
        }
        Err(err) => err.to_compile_error(),
    }
}

This is going to need a minimal repro, since your gpio macro is hundreds of lines. But this part looks suspicious to me:
https://github.com/esp-rs/esp-hal/blob/e9f22aca634a4ac107ac792297f00148e79cd616/esp-hal-common/src/gpio.rs#L567
You are using $iomux_reg, which is an expression ($iomux_reg:expr), as if it were a field name, which is not allowed in Rust.
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=9ce736206f1725404ce94f57e526809e

Thanks for your input, I actually managed to come up with a solution after seeing your comment.


Deploy bugs

Codecov Report
Base: 59.05% // Head: 59.05% // No change to project coverage :thumbsup:

Coverage data is based on head (1fe0388) compared to base (6c92557).
Patch has no changes to coverable lines.

:exclamation: Current head 1fe0388 differs from pull request most recent head 36d794a. Consider uploading reports for the commit 36d794a to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #30   +/-   ##
=======================================
  Coverage   59.05%   59.05%
=======================================
  Files          11       11
  Lines        1138     1138
=======================================
  Hits          672      672
  Misses        466      466

Impacted Files
Coverage Δ

aggregate/billing_functions/gcp.py
33.33% <ø> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Monitor support for TCP ports that use TLS/STARTTLS

[x] I have read and understand the pull request rules.

Description
This adds support for TCP ports that use either native TLS or STARTTLS-initiated TLS.
I had previously started a PR (#1626) that seemed to trigger people's interest but ultimately went nowhere. This is a complete rewrite for the latest development branch and now comes with STARTTLS support since that was requested in the original PR discussion. I've also renamed the monitor to "TCP Port (TLS)" as suggested by @louislam at the time.
Fixes https://github.com/louislam/uptime-kuma/issues/1079
Type of change
Please delete any options that are not relevant.

New feature (non-breaking change which adds functionality)

Checklist

[x] My code follows the style guidelines of this project
[x] I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and tested it
[x] I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
[x] My changes generates no new warnings
[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots

One thing which I forgot to ask: this seems like a superset of the existing TCP port monitor.
Can said monitor be implemented via this monitor?

One thing which I forgot to ask: this seems like a superset of the existing TCP port monitor. Can said monitor be implemented via this monitor?

For the looks of it that would be possible. The current "TCP Port" monitor uses the tcp-ping library which also just uses a socket. Instead of reading/sending anything it just disconnects immediately. Seems like a superset indeed.
Btw, for addressing review comments, do you prefer it if I create separate commits, so that it's easy to see what changed, and in the end we squash/fixup the original commits? Or do you want me to use fixup as I go?

Btw, for addressing review comments, do you prefer it if I create separate commits, so that it's easy to see what changed, and in the end we squash/fixup the original commits? Or do you want me to use fixup as I go?

Do this as you prefer. No need to squash/rebase/.. anything, I will do that at the end in any case

Seems like a superset indeed

In this case, lets not keep two monitors with so similar functionality around.
That would likely be very confusing for our users
=> please consider switching to the old monitor types ID and remove the old monitor.

In this case, lets not keep two monitors with so similar functionality around. That would likely be very confusing for our users => please consider switching to the old monitor types ID and remove the old monitor.

Sounds like a plan. I'll work on the other stuff first and will merge the two monitors at the end. In the meantime, if you have any suggestions on how to best arrange the UI, please let me know. Otherwise I'll just go with my intuition for now.

About the STARTTLS part I am a bit concerned that we might break this part of the monitor accidentally without noticing it. (i.e. the same as for #4736) Do you think adding a Testcase if this still works is something you could add?

@CommanderStorm I've added a couple of initial test cases: https://github.com/louislam/uptime-kuma/commit/d717a78746df73ba20d89a157a7c7d7bae10eae9
Is this what you had in mind? If so, I'll add a bunch more to cover different SMTP, POP3, and IMAP4 scenarios. I just want to be sure it's okay to access external hosts like this before I start working on the rest of the test suite.

I've rebased the PR onto the latest master branch before starting work on merging the TCP Port and TCP Port (TLS) monitors.
For future reference, the check failure on "ARM64, 18" might be related to https://github.com/nodejs/node/issues/46959.

Hi! Any news about this PR?


PublisherVerification.optional_spec105_emptyStreamMustTerminateBySignallingOnComplete fails if the publisher completes synchronously

Consider the following empty publisher:
class EmptyPublisher implements Publisher<Void> {
  public void subscribe(Subscriber<? super Void> subscriber) {
    Objects.requireNonNull(subscriber);
    subscriber.onSubscribe(new Subscription() { ... });
    subscriber.onComplete();
  }
}

I believe this is a valid publisher according to the spec, there's nothing that says that onComplete can't be synchronously invoked from subscribe, it just has to be invoked after onSusbscribe (it is).
However PublisherVerification.optional_spec105_emptyStreamMustTerminateBySignallingOnComplete, a test for empty publishers which should pass on the above publisher, fails with java.lang.AssertionError: Subscriber::onComplete() called before Subscriber::onSubscribe.
The problem seems to be that ManualSubscriberWithSubscriptionSupport requires expectCompletion to be invoked after onSubscribe and before onComplete is invoked. But expectCompletion isn't invoked until after subscribe returns, hence synchronous invocation of onComplete after onSusbcribe in  the subscribe method will always fail.

RxJava and Reactive4JavaFlow both pass so there is nothing wrong with the TCK. Did you override maxElementsFromPublisher to return zero, In which case this test is skipped altogether:

Asks for a short Publisher (i.e., length 3) and verifies, after requesting one by one, the sequence
completes normally.
Verifies rule: 1.5
The test is not executed if org.reactivestreams.tck.PublisherVerification#maxElementsFromPublisher() is less than 3.
Note that the tests requests 1 after the items have been received and before expecting an onComplete signal.

(Oops, wrong 105 method).
RxJava and Reactive4JavaFlow both pass so I don't think there is anything nothing wrong with the TCK in this regard. Did you override maxElementsFromPublisher to return zero?

This passes (but skips 38 of the 42 tests due to max length == 0):
import org.reactivestreams.*;
import org.reactivestreams.tck.*;
import org.testng.annotations.Test;

@Test
public class EmptyPublisherTckTest extends PublisherVerification<Integer> {

    public EmptyPublisherTckTest() {
        super(new TestEnvironment(50));
    }

    @Override
    public Publisher<Integer> createPublisher(long elements) {
        return subscriber -> {
            subscriber.onSubscribe(new Subscription() {

                @Override
                public void request(long n) {
                }

                @Override
                public void cancel() {
                }
            });
            subscriber.onComplete();
        };
    }

    @Override
    public Publisher<Integer> createFailedPublisher() {
        return null;
    }

    @Override
    public long maxElementsFromPublisher() {
        return 0;
    }
}

It's as @akarnokd writes. If your publisher is not able to emit many elements, you have to specify this by overriding the maxElementsFromPublisher method, so then tests which require elements to flow are skipped.

The error message could be better, perhaps add a hint if onComplete happens
before expected? (please override / verify max number of elements)
--
Cheers,
√
On Dec 29, 2017 12:46, "ktoso"<EMAIL_ADDRESS>wrote:

It's as @akarnokd https://github.com/akarnokd writes. If your publisher
is not able to emit many elements, you have to specify this by overriding
the maxElementsFromPublisher method, so then tests which require elements
to flow are skipped.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/reactive-streams/reactive-streams-jvm/issues/422#issuecomment-354436014,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAqd58AIFpraGLrGxJnrSPEMYqiY_6bks5tFNEAgaJpZM4ROz7C
.

But optional_spec105_emptyStreamMustTerminateBySignallingOnComplete is not a test that requires elements to flow, it invokes createPublisher(0) to create an empty publisher, so if returning zero from maxElementsFromPublisher causes it to not run, then that's a bug too. The publisher I'm testing of course is more complex than this, I've just provided a minimal reproducer to simplify things, my publisher is definitely able to emit many elements, so it makes no sense to override maxElementsFromPublisher to return zero. It's just that, in the case that zero elements are requested, my publisher happens to know this already before subscribe is called that it is an empty publisher and so invokes onComplete synchronously from the subscribe method. And that's valid according to the spec, and so should pass the test.

The tests expect you to provide Publishers of certain sizes and won't pass if you provide something shorter. Also if your Publisher can have different behavior for different maxElementsFromPublisher, have multiple test classes for each case.

I understand that. Here's the test:
https://github.com/reactive-streams/reactive-streams-jvm/blob/master/tck/src/main/java/org/reactivestreams/tck/PublisherVerification.java#L412
Here's the code:
  @Override @Test
  public void optional_spec105_emptyStreamMustTerminateBySignallingOnComplete() throws Throwable {
    optionalActivePublisherTest(0, true, new PublisherTestRun<T>() {
      @Override
      public void run(Publisher<T> pub) throws Throwable {
        ManualSubscriber<T> sub = env.newManualSubscriber(pub);
        sub.request(1);
        sub.expectCompletion();
        sub.expectNone();
      }
    });
  }

It's requesting a publisher of zero elements. This is a publisher of zero elements:
 Publisher publisher = subscriber -> {
            subscriber.onSubscribe(new Subscription() {
                public void request(long n) {}
                public void cancel() {}
            });
            subscriber.onComplete();
        };

It should pass that one test, right? Of course it won't pass the other tests, but it should pass the test that tests for an empty publisher, right? It's not passing.


Wrap some unit test data structures in a flag.

The data structures used for the backoff retry tests are not threadsafe, so I wrapped them in a flag that checks if unit tests are running. This was causing a crash if there's a backoff retry in datafile download or event dispatch.

TEST:

sh ./Scripts/build_all.sh
==> ** BUILD SUCCEEDED **
sh ./Scripts/local_travis.sh
==> ** TEST SUCCEEDED **
8 iOS	test suites PASSED
OptimizelySDKiOSUniversalTests PASSED

The code changes submitted in this P.R. also appear to be a compelling and plausible
explanation and resolution of OASIS-2002 and "Fatal Exception: NSRangeException in OPTLYHTTPRequestManager.m" issue posted on GITHUB.COM .

Yes. This fix is for that bug.


README: Link to LESS?

This is nitpicky, but as a new Bootstrap user I'm not sure what LESS is - can a link be added to the readme?

http://twitter.github.com/bootstrap/#less


feat(doc): add autodoc_pydantic to sphinx

Before:

After:

@jpetot We don't have to, it's easier IMO to reason about all the dependencies if they are grouped in logical units


Fall back to pelias when geosearch.planninglabs.nyc isn't available

Avoid failure if geosearch.planninglabs.nyc isn't available. Instead:

In nycmeshnet/meshdb#300 , @Andrew-Dickinson suggested that it would be possible to fall back to the pelias container if geosearch.planninglabs.nyc isn't available.
Avoid a 500 if geosearch.planninglabs.nyc and/or pelias isn't available.

Closing in favor of https://github.com/nycmeshnet/meshforms/issues/77


build "view extent" button

this button would zoom the map to the extent of all of the visible layers

Extent option created by @aaronr in #36 that does this for the time being. Seems like we have three different "menu categories" right now:

File includes save operations, load, export, etc.
Defaults which can be turned on and off, and might include app operations (non data-affecting operations)
geoprocessing operations that edit and create new data

Resolved in #170

Expanded this one step further. If no layers are selected the map expands to the entire feature layer bounds. If layers are selected, the map only expands to the extent of all of them - thanks to @aaronr for the bounds.extend() trick!


Extend TicketImporter to support extraction from multiple GitHub projects

In order to demo multi-tenancy (#31) need to implement import of new tickets from multiple GitHub projects. Currently, TicketImporter supports import from one project only.

TicketImporter project now supports import from

dotnet/aspnetcore
dotnet/runtime


Option to align title

today its hardcoded in "void drawTitles"
in this line
final TextPainter tp = TextPainter(text: span, textAlign: TextAlign.center, textDirection: TextDirection.ltr);

May I ask you to show your use-case, I want to know why you need it.

Hi,
Unfortunately, Github started banning Iranian users while ago,
If they didn't stop their action, I can't continue on this repo,
read more it here,
If you want to prevent this unfair action, give a start on this repository and say your support by creating an issue, and spread it.
Best regards,
Iman Khoshabi

I think it is not related to the alignment of text,
you can prevent to draw your first title to solve your problem.
let me know if you still need the alignment feature

I'm gonna close it If I don't get any answer till tomorrow.

Sorry for the delay
I manage to create a similar feature
Thanks
Sent from my iPhone
On 12 Oct 2019, at 21:18, iman khoshabi<EMAIL_ADDRESS>wrote:

I'm gonna close it If I don't get any answer till tomorrow.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FimaNNeoFighT%2Ffl_chart%2Fissues%2F35%3Femail_source%3Dnotifications%26email_token%3DAAFTVL4I6V6NFLLDRD3T3TDQOIIJBA5CNFSM4H64PWDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBCFMVY%23issuecomment-541349463&data=02|01||063f768ea2bd4268a78208d74f40a580|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637065011374976864&sdata=7e4VeWR5BV0ywK6Cr8mR59Vmj2hF6C3SybudfY8I9%2Fw%3D&reserved=0, or unsubscribehttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAFTVLY4WQ3G25RIL5MKIETQOIIJBANCNFSM4H64PWDA&data=02|01||063f768ea2bd4268a78208d74f40a580|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637065011374986869&sdata=PjJFLiKQf7LgxfxKaYX0K9ThFsTkAWG6%2FQb2ZdtVXIg%3D&reserved=0.

What?

Please close this
Sent from my iPhone
On 12 Oct 2019, at 23:24, iman khoshabi<EMAIL_ADDRESS>wrote:

What?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FimaNNeoFighT%2Ffl_chart%2Fissues%2F35%3Femail_source%3Dnotifications%26email_token%3DAAFTVL2AYN725YLCVXY5WD3QOIW7JA5CNFSM4H64PWDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBCHUUI%23issuecomment-541358673&data=02|01||14504dcf40004d32306b08d74f522a3e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637065086626303607&sdata=eBH46RfT09BR%2Bw5vWTWNhraO7gSmX6z9zZF45nw0RhI%3D&reserved=0, or unsubscribehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAFTVL6MGZ5U3OXCY6EJRM3QOIW7JANCNFSM4H64PWDA&data=02|01||14504dcf40004d32306b08d74f522a3e|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637065086626303607&sdata=zZ59NAHJM4SrBvwRVIhImCR5SBcXxWvEePo%2FhqRu47E%3D&reserved=0.


429

Checklist

[ ] I'm reporting a broken site support issue
[ x] I've verified that I'm running youtube-dl version 2019.11.28
[ x] I've checked that all provided URLs are alive and playable in a browser
[ x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[ ] I've searched the bugtracker for similar bug reports including closed ones
[ x] I've read bugs section in FAQ

Verbose log

I don't actually know how to pull this from the command line

Description

I ran into this issue last night, getting it again today - I'm just getting 429's whenever I try to pull info for several videos (ie 40) in a few minutes. Could you please unblock? Thanks!

Ask Youtube.


 Make sure you can play the video in a browser from the same computer.  If you can then try retrying pytube. If you cannot please copy the and post the entire traceback.

@nficano is there a way to prevent that using pytube? Do you have a rate throttling setting?

Hi I am going through this issue. I was rate limited and when I cleared Captcha in browser, I am able to play videos but pytube still has Video Unavailable issue. Also
curl -I  -s 'https://www.youtube.com/watch?v=QmyhcjpsF6E' -4
HTTP/1.1 429 Too Many Requests
X-Content-Type-Options: nosniff
P3P: CP="This is not a P3P policy! See http://support.google.com/accounts/answer/151657?hl=en for more info."
X-Frame-Options: SAMEORIGIN
Cache-Control: no-cache
Content-Type: text/html; charset=utf-8
Expires: Tue, 27 Apr 1971 19:44:06 GMT
Strict-Transport-Security: max-age=31536000
Date: Fri, 22 Nov 2019 20:57:22 GMT
Server: YouTube Frontend Proxy
X-XSS-Protection: 0
Set-Cookie: YSC=65COLS_Mwfw; path=/; domain=.youtube.com; httponly
Set-Cookie: GPS=1; path=/; domain=.youtube.com; expires=Fri, 22-Nov-2019 21:27:22 GMT
Set-Cookie: VISITOR_INFO1_LIVE=6pkthaooVmk; path=/; domain=.youtube.com; secure; expires=Wed, 20-May-2020 20:57:22 GMT; httponly
Transfer-Encoding: chunked
Alt-Svc: quic=":443"; ma=2592000; v="46,43",h3-Q050=":443"; ma=2592000,h3-Q049=":443"; ma=2592000,h3-Q048=":443"; ma=2592000,h3-Q046=":443"; ma=2592000,h3-Q043=":443"; ma=2592000
Accept-Ranges: none
Vary: Accept-Encoding

@srik506 can you tell me how exactly did you fix it? I am having the very same problem right now.

@srik506 can you tell me how exactly did you fix it? I am having the very same problem right now.

I did do extensive research but couldn't come up with a limit to determine how long before one gets blocked. So only thing that worked for me was having an 8 sec delay between each request. And then if you still get blocked, I think you either have to get another external or wait till the IP is released from their system.


Feature request: support MAC container

Looks like this plugin only supports Linux :

Thanks for the feature request @glureau. You should be able to use v2.0 to which would support Macos and Windows runners.
https://github.com/maheshrayas/action-pr-comment-delete/tree/mac-windows

Ah thank you!
I finally found another plugin sticky-pull-request-comment dealing with comment+remove previous (that was my initial need) and supporting MAC.
Thanks for your work!


EMAIL_HEADER_MUTATOR not applying changes to MimeMultipart msg

I am trying to modify the email that is being sent out by a scheduled Report. For this, I am using the EMAIL_HEADER_MUTATOR environment variable in the config, and I basically would like to modify the mime message in the following manner:

Remove the Explore in Superset hyperlink
Add a footer or signature to all emails as a disclaimer

After checking what is being done in the underlying code,  I believe a simple mutator function would suffice in the image config file we are using, although it does not work at all and the outgoing message never mutates as it should be doing because the content is altered and returned.
Did anybody stumbled upon a similar issue or used EMAIL_HEADER_MUTATOR?
How to reproduce the bug
In the dockerised superset image config file:
def EMAIL_HEADER_MUTATOR(  # pylint: disable=invalid-name,unused-argument
    msg: MIMEMultipart, **kwargs: Any
) -> MIMEMultipart:
    disclaimer = "Please do not reply, this is an automatically generated email."
    mime_text = MIMEText(disclaimer, "html")
    msg.attach(mime_text)

    # Remove all anchor tags from message payload
    for part in msg.walk():
        if part.get_content_type() == 'text/html':
            part.set_payload(re.sub('| ', '', part))

    return msg

Expected results
Mutated message:

Text "Please do not reply, this is an automatically generated email." should appear at the end of each email
All anchor tags should be removed from the email contents (on all parts)

Actual results
Email does not mutate at all - no changes and no errors are logged.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
(please complete the following information):

browser type and version: Chrome 110.0.5481.177
superset version: 2.0
python version: 3.9
node.js version: N/A
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

@amartincolville
Actually the reason that your mutator would not be working is that , the image-2.0.0 as well git-repo missed this changes.
for msgid, imgdata in (images or {}).items():
        formatted_time = formatdate(localtime=True)
        file_name = f"{subject} {formatted_time}"
        image = MIMEImage(imgdata, name=file_name)
        image.add_header("Content-ID", "<%s>" % msgid)
        image.add_header("Content-Disposition", "inline")
        msg.attach(image)
    msg_mutator = config["EMAIL_HEADER_MUTATOR"]
    # the base notification returns the message without any editing.
    new_msg = msg_mutator(msg, **(header_data or {}))
    send_mime_email(smtp_mail_from, recipients, new_msg, config, dryrun=dryrun)


Use datatree library instead of flattening and reconstructing groups

Note: we can directly contribute to xarray datatree development, since it's open source.

DataTree is now part of xarray core, as of xarray version 2024.10.0


升级版本后启动报错

Caused by: java.lang.RuntimeException: expect one puppet,but can not found any one.
at io.github.wechaty.user.manager.PuppetManager$Companion.resolveInstance(PuppetManager.kt:29) ~[wechaty-0.1.4-SNAPSHOT.jar:?]
at io.github.wechaty.Wechaty.initPuppet(Wechaty.kt:176) ~[wechaty-0.1.4-SNAPSHOT.jar:?]
at io.github.wechaty.Wechaty.start(Wechaty.kt:51) ~[wechaty-0.1.4-SNAPSHOT.jar:?]

In 0.1.4-SNAPSHOT version, we use puppetManager to manage puppet implementations and removed puppet implementations from wechaty pom. Which implementation to use depends on which implementation jar in your pom. You need to depend puppet hostie on your pom now.  Like this:
<dependency>
      <groupId>io.github.wechaty</groupId>
      <artifactId>wechaty-puppet-hostie</artifactId>
      <version>0.1.4-SNAPSHOT</version>
 </dependency>

You can see: https://github.com/wechaty/java-wechaty-getting-started.
Maybe in next version, we'll improve this to depend a default puppet implementation, then users can not need to depend puppet-hostie themselves.


Mention dependency files update for Gradle

Why:
Closes #10042
What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@zbynek This PR seems to be opened as a draft by mistake. If so, please change it to ready for review so I can triage it for our team to review ✨

@ramyaparimi thanks for pointing it out, I was waiting for the rendering ( https://docs-10041--patch-2.herokuapp.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates#package-ecosystem ) and forgot to mark this as ready.

@zbynek
Thanks so much for opening a PR! I'll get this triaged for review :zap:

I'm in the process of getting this PR merged, but there have been some technical issues, so just need to make sure those are addressed and then this will be merged as soon as possible.


Run under cygwin

I tried to run it under cygwin and it just freeze - no output.
Another question what format of input\output? Did you compare speed\accuracy with sofia-ml kmeans?

We never ran it in cygwin, but are you sure it froze? It may be waiting for the input.
I've just updated the README, but let me paste it here as well:
Input format (assuming you have m vectors of n dimensions):
[label_1] [weight_1] x_11 ... x_1m
...
[label_m] [weight_m] x_m1 ... x_mn

label_i  : (string) label of the ith vector, required when -l used
weight_i : (double) weight of the ith vector, required when -w used
x_ij     : (double) ith vector's jth component

Output format:
[label_1] c_1
...
[label_m] c_m

c_i : (int) cluster of ith vector

As far as I know none of us compared this with sofia-ml kmeans.

I tried to run it under amazon ec2 ubuntu, same result.
git clone https://github.com/ai-ku/wkmeans.git
cd wkmeans
make
./wkmeans
nothing happens
./wkmeans -k 2 data.txt out.txt
nothing happens
data.txt for test
1 2 3 4
11 2.1 3 4
142.01 2 3 5

wkmeans doesn't do anything with the command line arguments, you have to redirect the input/output, like this:
./wkmeans -k 2 < data.txt > out.txt

still can't make it work
when I use
./wkmeans -k 2 < data.txt > out.txt
one core stay busy and nothing happens and it's weird for data.txt file consisting of several lines.
can you provide small working example?


Some issues about using zeppelin.

Hi, I use Zeppelin yesterday firstly, I find some operation is not working.

When I Create New note,I click the button Create new note, I think it will be open the notebook which i created just now , while nothing happened, only add a new note in menu(note list). while the note list is order by string, and I didn't rename my oldest notebook, so I can not sure which notebook is new i just create.

I go into one notebook, there are many buttons in notebook window, I want to know each button's function，so I think it will be some tooltips when my cursor is positioned over the button, while nothing happened , so I only click one by one to check each button's function.

I first use zeppelin, did I miss some config for upon operation?
Thank you, :)

Hi,
As the README.md of the project is stating, the project moved to Apache Foundation.
We are no longer using this Github to get new issues (we use our ASF JIRA)
Now to answer you quickly:
You didn't miss anything in your configuration, Zeppelin is working like that.
Some issues were already opened for both your points:

This issue was discussed in the mailing list, but I guess no issue was created,
If you want to create an issue you can go on the JIRA: https://issues.apache.org/jira/browse/zeppelin/
Check existing issue before creating one

Exist here: https://issues.apache.org/jira/browse/ZEPPELIN-35


[cinder-csi-plugin]update helm chart to latest

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:
/kind bug
/kind feature

What happened:
helm chart of CSI cinder is using 1.18, we need switch to latest so that we can use
current image
What you expected to happen:
How to reproduce it:
Anything else we need to know?:
Environment:

openstack-cloud-controller-manager(or other related binary) version:
OpenStack version:
Others:

/assign


US140986-node-upgrade as part of node upgrade, fix issue with non ide…

…mpotent symlink task

:shipit:


Add default chat model to support dev UI chat?

I got in trouble in a demo recently, because I hadn't noticed when practicing that the chat feature in the dev UI is only available if the application contains a chat model. I wanted to show the flow where you can interact with the model before creating the application, which I'd seen other people show, but it didn't work for me. This is documented, but it caught me by surprise.
Two things make this extra-surprising, IMO:

"Adding a chat model to the application" can be pretty implicit. While it can be done with explicit config in application.properties, it's sufficient to add a @RegisterAIService annotation somewhere. If we can do some default configuration to support @RegisterAIService, would it be a bad thing to do similar defaulting to support the dev UI?
Other interaction modes in the dev UI, like creating images, work before an application is created. Images only work if the right extension is present, so the rule is different for images and chat; images we will enable by default if the right provider is present, but chat we will only enable with explicit configuration or once an application has been created

Obviously, we should design for the best experience for real users, not for demos. But I wonder if other people might be surprised by the current behaviour, and if extending what we default-configure might help others?

Hmm, good point. The main difference is that the Image page doesn't use an ImageModel injected from CDI, but instead, it lets the user configure all its parameters in the page, and then upon submitting, an ImageModel instance is dynamically generated from these parameters.
For chat models, we could potentially do the same, but we would probably have to supply a similar form to specify all parameters, and the problem with this is that each provider type has different parameters, so the page would no longer be the same for all possible providers, it would probably have to move to each provider extension separately (the image page is currently only in the OpenAI extension).
Also, if we did this, I'm not sure how exactly we would support users who just want to test the already configured model from CDI, the UI and the related logic might get very clunky for this (it already is quite a mess, to be honest)...

So yes, it would probably be possible, I'm just scared it would be much harder to implement and maintain that one might think

Even if we just went with an 'easy' solution where we dynamically instantiate a model with default parameters, it would still  have to be tied to each provider separately, because you need to use the concrete provider's ChatModel constructor.

Hmm, tricky. If it's a case of lots of internal complexity in order to give an external experience that looks trivially simple, that's kind of our reason for being, as developers. But of course there's zillions of things to do, so if it's a pretty marginal user benefit, maybe it's not worth it. It's probably fairly rare that people would try the dev ui before adding a @RegisterAIService annotation somewhere in their codebase.

Thinking about it more, I think I agree a form on the UI wouldn't be ideal, both because it means more clicking for users, and because of the risks @jmartisk identified of conflicts between the UI model and the CDI model. What envisaged was more 'dev UI will behave the same as the app,' ie 'you don't have to specify a model and there's a sensible default.'


Support webRoot config being a relative path, bootstrap the client’s server URL

Corresponding PR for https://github.com/actualbudget/actual/pull/649. Also allows specifying relative paths for webRoot (such as ../actual/packages/desktop-client/build, which is useful if you want to test running against a local build of the frontend).

Why not use the existing /needs-bootstrap for this? It's used to check if the server is running actual-server or a different server after typing in the URL and clicking on "ok".

Why not use the existing /needs-bootstrap for this? It's used to check if the server is running actual-server or a different server after typing in the URL and clicking on "ok".

That’s an interesting idea! So you’re thinking we would call /needs-bootstrap on the current domain immediately at startup?

yup

Since d39f196b8702de79c448752b80956de0c57adabe needs more discussion, I’ll move that to a different PR and focus this on the issue at hand.

Will wait to merge until the other PR is also approved to make sure there don’t need to be any other changes


Rewind to a commit prior to the breaking new_local_repository change

Temporarily gets CI working again - see #45.

CI is still not happy.

I know, left a comment over in the issue and sending a (temporary) fix to Drake.

Fix in Drake going in at https://github.com/robotlocomotion/drake/pull/7257

Closing, #48 instead.


HTML error responses

It would be nice to have proper support for HTML error responses (and other non-JSON content types too). Writing your own ExceptionMapper gets most of the way but is a bit ugly, and it doesn't seem to work at all for AbstractParam validation.
I've put together a tentative solution consisting of an ErrorResponseProvider interface that can be hooked up to your app's error views.
public interface ErrorResponseProvider {

    Response getResponse(ErrorMessage errorMessage);

    Response getValidationResponse(ValidationErrorMessage errors);

    boolean isAcceptable();
}

It works with LoggingExceptionMapper and JerseyViolationExceptionMapper and I've managed to integrate with AbstractParam too although that was a bit more tricky.
Here's an outline of the solution:
https://gist.github.com/BenScholl/95236ce186f05d0f5bdd46f1e5dc93ad
Any comments would be much appreciated.
Ben

Hey, that's a good start! You're right that supporting arbitrary return types for errors has been a pain point. I'm open to improvement, as long as backwards compatibility is kept.
To get around the AbstractParam issue, it may prove prudent to define a custom exception and exception mapper and have parse wrap the thrown exception (and those that create their own abstract parameters and override the error method will need a migration path)

Thanks for the encouragement!
I don't really understand why AbstractParam puts a Response in the exceptions it raises. This stops them from getting mapped, as ServerRuntime.Responder.mapException doesn't map exceptions that have an entity attached.
If instead AbstractParam just wrapped up the error text in the WebApplicationException, then LoggingExceptionMapper would be able to handle these exceptions and create the proper response itself.
Nice simple solution ... or am I missing something?

Thinking about it a little longer, I think if one provided a MessageBodyWriter that produces html for ValidationErrorMessage, ErrorMessage, etc, that would get one pretty far and ErrorResponseProvider wouldn't be needed.
I don't remember how Jersey determines the content type if it is not specified in the builder 🤔

Good point - that would be a much less intrusive approach.
Here's a ViewEntityMessageBodyWriter (suggestions for better names welcome...)
https://gist.github.com/BenScholl/e8568e59078565337f90a2e4d709d489
You just register separate instances to handle ErrorMessage and ValidationErrorMessage and it intercepts the appropriate responses. No need to mess about with AbstractParam and exception mappers.
I imagine most people using views would want this. Is it worth me putting together a pull request for dropwizard-views?

Yeah if you want to prove it out with dropwizard-views that would be a good start! I can imagine people who are not using dropwizard-views interested as well.


EntityMethod determined from the method is sometimes wrong

This problems stems from the fact that we only consider two entity types: Avatar and Vehicle. This can be fixed by considering all possible entity types

Should be fixed #13


is no longer needed to convert an instance to sanbox to delete a production instance, can you pls update the article? thank you

is no longer needed to convert an instance to sanbox to delete a production instance, can you pls update the article? thank you

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

ID: adb92ca9-41dc-d1d0-90df-09e7159e47d7
Version Independent ID: 6c2a02de-a8db-cafa-6d81-861a027c07f2
Content: Delete environment - Power Platform
Content Source: power-platform/admin/delete-environment.md
Service: power-platform
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

@anapereiCRMSE
Thanks for the feedback. The topic has been updated.


Data Shifting

images, pdfs, and other data files are to be shifted outside Central, and links are to be made relative please.

I believe this is already done by @bijitsony


Removed a Basic SKU public IP as a mitigation option.

Basic SKU public IPs go end of life the same day Default outbound access does so is not a valid mitigation step.
On September 30, 2025, Basic SKU public IPs will be retired. For more information, see the official announcement. If you are currently using Basic SKU public IPs, make sure to upgrade to Standard SKU public IPs prior to the retirement date. For guidance on upgrading, visit Upgrading a basic public IP address to Standard SKU - Guidance.
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/public-ip-addresses

#sign-off

Merging.


WIP: Normalization for permutation estimators.

See comment on the Dispersion PR. This should be done via a generic API and not within each estimator. Eliminate code duplication, increase code re-use, all the while providing useful API functions to the front end user as well, such as number of alphabet.

This was solved with the new API in #101.


Fixing the observer binding for params

This project uses semver, please check the scope of this pr:

[x] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Removed the hack for dynamically disabling confirm on forms
Added a computed property for params that fires whenever attributes are updated
Updated the info demo to demonstrate this ability in both the summary and confirm params

Visual Acceptance tests:
No changes

Approved


Fix copyfile

Task name: CopyFilesV2
Description: Updated the TargetFolder parameter type from String to filePath. This ensures that the folder selection in the task UI properly reflects a file path type, improving validation and user experience.
Documentation changes required: (N)
Added unit tests: (N)
Attached related issue: (N)
Checklist:

[x] Task version was bumped - please check instruction how to do it
[ ] Checked that applied changes work as expected

@microsoft-github-policy-service agree


Godot 4.0 Support

I'd like to use this in a Godot 4.0 project and I think I see how you'd go about upgrading it to work. It looks like the only incompatibility is with the exports and setter/getter syntax. However, I'm still pretty new to the engine so I'm not sure if the shader is going to implode or something if I fix the script, and also I think they changed some stuff about how viewports work. Fixing that would probably be beyond me, plus I'm not sure if this library will do exactly what I want in the first place... I'm looking for a method of getting decent antialiased pixel art upscaling to non-integer screen resolutions for a 2D game.

Do you think the shader is still compatible with the new Vulkan backend? I saw a few of these warnings in the editor, but no errors.

Would you rather just do the porting yourself, or would you accept a PR from me if I fixed the script?
Can this library actually do what I'm looking for? It looks to me like it should be able to, but I'm not certain.

I did actually port it to Godot 4.0, but I never released it. This is because Godot 4.0 has built-in scaling options that are better than this. If you enable the Advanced Options in the Project Settings, there is a mode for Scaling 3D. This uses either Bilinear Interpolation or AMD FSR. I am not sure if it works for 2D, maybe not. But I did some testing, and these options were better than my shader in terms of the quality and performance. So I opted not to release the code, since it wouldn't be useful. If you want to use this for 2D, I can clean up the port and post the code, it wouldn't be that much work. I just didn't think anyone would use it.

Yeah the crazy thing is I actually tried using the various antialiasing options in the settings, but no dice. MSAA doesn't work on textures and FXAA seems to apply AFTER upscaling, so I still get oddly shaped pixels everywhere. Aaaaand... I just checked and sadly the 3D scaling options don't apply at all to 2D viewports. This is making me sad. What I need is to scale up to an integer and then scale back down with antialiasing, seems like this library could still fill that need perfectly. Would you mind sharing the port so I can give it a try?

So my add-on doesn't do integer scaling. I was going to add it originally, but I didn't get much interest, so I stopped working on it. Also, since I mainly work in 3D, I didn't need it for anything I was doing. But I know how to do it. Just give me like a day or two to take a look at the code, it's shouldn't be too difficult.

Oh thanks, that would be very helpful. I've been playing around with other camera systems in the meantime but even fully dynamic the size of the viewport I want just doesn't quite line up with the closest integer scales at 1080p, to say nothing of other resolutions. Being able to scale arbitrarily with antialiasing would help me out a lot, but I'm just not quite sure how to make it happen myself.


Depend on ansible-base conda package

Closes #70

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


vrperfkit support?

Hi,
Firstly, thanks for this brilliant tool!
I noticed it supports both fsr/ffr mods by fholger, but they cannot be used in conjunction due to the way they are installed (both override the openvr_api.dll).
Sometime later fholger parked those projects and created the vrperfkit mod, which combines both functionalities and has been working really well for me in rFactor2.
I noticed the widget source code mentions the vrperfkit, but there is no option in the UI. Is it possible to support it?
https://github.com/tappi287/rf2_video_settings/blob/master/open_vr_mod/mod/vrperfkit_mod.py
If so, I wonder if it will conflict with reshade/VRToolKit, as both are based on dxgi.dll injection. If there is a way to use both, I have high expectations that it will provide the best performance and visual quality results.
Cheers, and keep up the good work!

Hi, thank you, glad that you find it useful! Yes it would conflict with VRToolkit installation. While it would be possible to implement via another dll name, I'm afraid I won't find the time to implement and maintain it. Please feel free to poke someone to do it or implement it yourself and send a PR.


Prepare deployment before writing golden file.

The function compareDeployments removes some fields that start with ISTIO_META_* . These fields have to be removed when we write the golden files.
Co-authored-by: Julia Plachetka<EMAIL_ADDRESS>

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: axel7born
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: vadimeisenbergibm
If they are not already assigned, you can assign the PR to them by writing /assign @vadimeisenbergibm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @axel7born. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/ok-to-test

@axel7born: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@axel7born: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@axel7born: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@axel7born: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@axel7born: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-dashboard.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@axel7born: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-dashboard.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@axel7born: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-dashboard.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@axel7born: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-dashboard.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-multicluster-e2e

prow/e2e-mixer-no_auth.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@axel7born: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-integ-k8s-tests

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-dashboard.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-multicluster-e2e

prow/e2e-mixer-no_auth.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-mixer-no_auth

prow/e2e-mixer-no_auth-mcp.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-mixer-no_auth-mcp

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@axel7born: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-simpleTests-cni

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3-mcp.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-e2e-envoyv2-v1alpha3-mcp

prow/e2e-dashboard.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-dashboard

prow/e2e-bookInfoTests-v1alpha3.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

prow/istio-pilot-multicluster-e2e.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-pilot-multicluster-e2e

prow/e2e-mixer-no_auth.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-mixer-no_auth

prow/e2e-mixer-no_auth-mcp.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test e2e-mixer-no_auth-mcp

prow/istio-integ-k8s-tests.sh
109c7ab95036924bb98688fd7b9ae7ef733a9976
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-bookInfoTests-v1alpha3
/test e2e-dashboard
/test e2e-mixer-no_auth
/test istio-pilot-e2e-envoyv2-v1alpha3

/assign @GregHanson
/assign @andraxylia

/test e2e-bookInfoTests-envoyv2-v1alpha3

/test e2e-bookInfoTests-v1alpha3

/cc @costinm
/cc @ayj
/cc @hzxuzhonghu
Someone interested in reviewing this change?

Not stale


Switched Add function to indexer operator

Using the indexer operator will check if the key exists as part of the operation, and either add or update the entry.

Fixes #12


Copy/pasting the guide produces some NaNs

I just copy/pasted the code from the guide (in the interest of reproduction, setting up a one-click cloneable template).
Upon viewing the page, I noticed two places where some missing data produces NaN:

. NaN
NaN

And
Citation:
Olah & Carter, NaN

@article{olahNaNarticle,

and
year = {NaN}

It seems like there's a missing "year" number, but no clear indication of where to put it to make it render.

Also, create an issue on GitHub. link has undefined as the repo, as does the source available link. Amusingly, it send you to a real page: https://github.com/undefined

I've removed those sections for now from non-distill articles.


Tests related to Account Recovery API failing

Describe the issue:
The following test cases are  failing due to not returning the expected response content.

How to reproduce:
Following is how to reproduce one case.

Start a latest IS pack
Do a GET request to the following endpoint
https://localhost:9443/accountrecoveryendpoint/register.do?callback=https://localhost:9443/carbon/callback

The response body will be empty.
Expected behavior:
The HTML content for getting the username should be returned.

Fixed with https://github.com/wso2/identity-apps/pull/3951


update docs

@philbrookes looks good Phil. One other thing that occurred to me - do we document memory requirements for docker for mac folks? e.g. CPU/Memory allocation

@jasonmadigan I have put instructions in this doc for mac users to increase the RAM allowance to 6Gb.


New PR to test SignCLA at 2018-03-26 14:30:32.955226633 -0700 PDT m=+5.459009910

Body of PR

corp-pass-fork-staging: test succeeded


Accepting and declining friend requests and profile view reflect status of friend invitations

This handles the friending buttons in the profile views. The page displays accept or decline when visiting profile pages that send them a friend invitation. It displays remove friend if they are already friends. If they have send that user a friend invitation before, it displays cancel friend requests. If a user tries to accept/decline an invitation that does not exist or where they are not the receiver they are redirected back to their profile page with a proper error message. If they accept invitation, they become friends and if they decline the invitation is deleted.  Currently the remove friend button does not redirect to anything. This will be handled in a separate issue.

On lines 93 - 94 in src/chigame/users/views.py what is the behavior after the message "You already have a pending friend invitation from this profile." shows up? Maybe having a return statement after this with a redirect might be helpful (similar to line 97). Other than that, great job catching all the scenarios that could happen with an invitation!

it will also return because if the function goes to 94 then it won't go into the else branch and would go directly to the return statement on 97

Fixing merge conflict was a little challenging because this both PR and #127 were changing in the same functions. So, I resolved the conflict and pushed again.

Closing statement:
This addresses the functionality of friend request buttons within profile views. When visiting profile pages that have sent a friend invitation, the page now appropriately displays options to accept or decline the invitation. If the users are already friends, the option to remove the friend is shown. Additionally, if a friend invitation had been sent previously, the page now provides the option to cancel the friend request. In case a user attempts to accept or decline an invitation that does not exist or where they are not the intended recipient, they will be redirected back to their profile page with a relevant error message. Upon accepting an invitation, the users become friends, and declining results in the removal of the invitation. It's worth noting that the functionality of the "remove friend" button is pending redirection and will be addressed in a separate issue.
@24raniwalar  worked on designing the new required endpoints
@omarelkashef  worked on the logic of the friending feature

Issue Score: Excellent
Comments:
Nice PR that made it possible for users to become friends. Also, good summary description,  especially highlighting that the remove friend functionality was not covered in this PR.


health readiness check is not recovering

Initially health ready reports everything ok as expected
`$ curl localhost:8080/q/health/ready
{
"status": "UP",
"checks": [
{
"name": "SmallRye Reactive Messaging - readiness check",
"status": "UP",
"data": {
"data": "[OK] - Connection established",
"data2": "[OK] - Connection established"
}
}
]
}`
now I restart the NATS docker image (same port mappings ect)
Service sees that it lost connection:
2024-10-08 21:45:35,073 ERROR [io.qua.rea.mes.nat.jet.cli.con.DefaultErrorListener] (pool-14-thread-1) Caught exception connecting to [nats://localhost:4222] with message: Read channel closed. 2024-10-08 21:45:35,073 ERROR [io.qua.rea.mes.nat.jet.cli.con.DefaultErrorListener] (pool-16-thread-1) Caught exception connecting to [nats://localhost:4222] with message: Read channel closed. 2024-10-08 21:45:35,075 INFO  [io.qua.rea.mes.nat.jet.cli.Connection] (pool-16-thread-1) Event: Disconnected, message: Connection disconnected 2024-10-08 21:45:35,075 INFO  [io.qua.rea.mes.nat.jet.cli.Connection] (pool-14-thread-1) Event: Disconnected, message: Connection disconnected 2024-10-08 21:45:35,075 INFO  [io.qua.rea.mes.nat.jet.cli.Connection] (pool-16-thread-1) Event: Closed, message: Connection closed 2024-10-08 21:45:35,076 INFO  [io.qua.rea.mes.nat.jet.cli.Connection] (pool-14-thread-1) Event: Closed, message: Connection closed
So far everything seems ok.. but the service keeps reporting readiness as DOWN.. this was 10+ mins after NATS was up and running again
`$ curl localhost:8080/q/health/ready
{
"status": "DOWN",
"checks": [
{
"name": "SmallRye Reactive Messaging - readiness check",
"status": "DOWN",
"data": {
"data": "[KO] - Connection closed",
"data2": "[OK] - Connection closed"
}
}
]
}`
I would expect this to be back at UP status

Adding more data... I did a manual curl against the service just for fun... this would not happen as K8S would have stopped traffic
One connection 'data2' came back, but the other 'data' stayed down
2024-10-08 21:59:28,291 INFO  [io.qua.rea.mes.nat.jet.cli.Connection] (pool-18-thread-1) Event: Connected, message: Connection established
$ curl localhost:8080/q/health/ready {     "status": "DOWN",     "checks": [         {             "name": "SmallRye Reactive Messaging - readiness check",             "status": "DOWN",             "data": {                 "data": "[KO] - Connection closed",                 "data2": "[OK] - Connection established"             }         }     ] }
data is incoming, data2 is outgoing
So still a pod would be rejecting requests in this state

Just tested the 3.15.6 release. No change so far

Found the root of the issue.. I think...
In ConnectionOptionsFactory maxReconnects is hardcoded to 0
This turns off reconnects.. there is no way to configure the reconnect options via the config
https://docs.nats.io/using-nats/developer/connecting/reconnect

I have updated the connection configuration to also include attempts and backoff. I have made a fix to ReaderSubscription so it fails if the connection is lost or the subscription becomes inactive.

And I can confirm that the issue seems to be gone now 😄


Add functions to return the maximum compressed size

It would be helpful if there were functions which returned the maximum amount of space needed to compress a buffer.  Something like zlib's compressBound.

I can add them, but for reference data that can't be compressed smaller
than the input will just return the original data, so the maximum space
required is always input size.
If you're getting data that compressed larger than input, let me know, as
that's a bug.
On 2 Mar 2016 4:38 pm, "Evan Nemerson"<EMAIL_ADDRESS>wrote:

It would be helpful if there were functions which returned the maximum
amount of space needed to compress a buffer. Something like zlib's
compressBound.
—
Reply to this email directly or view it on GitHub
https://github.com/ConorStokes/LZSSE/issues/5.

can add them, but for reference data that can't be compressed smaller than the input will just return the original data, so the maximum space required is always input size.

Okay, in that case I don't think it's necessary.

If you're getting data that compressed larger than input, let me know, as that's a bug.

Yeah, I am.  The easiest way for me to generate examples was to throw together a quick program and fuzz it, and I'm getting lots of results very quickly.  The most common issue is the compressed data being larger than the input, but I'm also seeing lots of cases where decompress(compress(input)) != input.
Anyways, here is the test program I'm using:
#include <stdio.h>
#include <stdlib.h>
#include <assert.h>
#include <stdint.h>
#include <string.h>

#include "lzsse2.h"

static void
test_round_trip(const uint8_t* uncompressed, size_t uncompressed_size) {
  uint8_t* compressed = (uint8_t*) malloc(uncompressed_size * 2);
  assert(compressed != NULL);

  LZSSE2_OptimalParseState* state = LZSSE2_MakeOptimalParseState(uncompressed_size);
  assert(state != NULL);
  size_t compressed_size = LZSSE2_CompressOptimalParse(state, uncompressed, uncompressed_size, compressed, uncompressed_size * 2, 7);
  assert(compressed_size != 0);
  if(uncompressed_size < compressed_size) {
    fprintf(stderr, "%zu -> %zu\n", uncompressed_size, compressed_size);
    abort();
  }
  LZSSE2_FreeOptimalParseState(state);

  uint8_t* decompressed = (uint8_t*) malloc(uncompressed_size);
  size_t decompressed_size = LZSSE2_Decompress(compressed, compressed_size, decompressed, uncompressed_size);
  assert(decompressed_size == uncompressed_size);
  assert(memcmp(decompressed, uncompressed, uncompressed_size) == 0);

  free(decompressed);
  free(compressed);
}

int main(int argc, char** argv) {
  uint8_t* data = (uint8_t*) malloc(1024);
  size_t data_length = 0;

  while (!feof(stdin)) {
    const size_t bytes_read = fread(data + data_length, 1, 1024, stdin);
    data_length += bytes_read;
    data = (uint8_t*) realloc(data, data_length + 1024);
    assert(data != NULL);
  }

  test_round_trip(data, data_length);

  free(data);

  return EXIT_SUCCESS;
}

Archive with a bunch of crashes: http://code.coeusgroup.com/afl-results/4697755e-2236-433b-b407-64e534cdfc90.tar.xz

Thanks, I'll have a look.
On Wed, Mar 2, 2016 at 6:32 PM, Evan Nemerson<EMAIL_ADDRESS>wrote:

can add them, but for reference data that can't be compressed smaller than
the input will just return the original data, so the maximum space required
is always input size.
Okay, in that case I don't think it's necessary.
If you're getting data that compressed larger than input, let me know, as
that's a bug.
Yeah, I am. The easiest way for me to generate examples was to throw
together a quick program and fuzz it, and I'm getting lots of results very
quickly. The most common issue is the compressed data being larger than the
input, but I'm also seeing lots of cases where decompress(compress(input))
!= input.
Anyways, here is the test program I'm using:
#include <stdio.h>
#include <stdlib.h>
#include <assert.h>
#include <stdint.h>
#include <string.h>
#include "lzsse2.h"
static voidtest_round_trip(const uint8_t* uncompressed, size_t uncompressed_size) {
uint8_t* compressed = (uint8_t*) malloc(uncompressed_size * 2);
assert(compressed != NULL);
LZSSE2_OptimalParseState* state = LZSSE2_MakeOptimalParseState(uncompressed_size);
assert(state != NULL);
size_t compressed_size = LZSSE2_CompressOptimalParse(state, uncompressed, uncompressed_size, compressed, uncompressed_size * 2, 7);
assert(compressed_size != 0);
if(uncompressed_size < compressed_size) {
fprintf(stderr, "%zu -> %zu\n", uncompressed_size, compressed_size);
abort();
}
LZSSE2_FreeOptimalParseState(state);
uint8_t* decompressed = (uint8_t*) malloc(uncompressed_size);
size_t decompressed_size = LZSSE2_Decompress(compressed, compressed_size, decompressed, uncompressed_size);
assert(decompressed_size == uncompressed_size);
assert(memcmp(decompressed, uncompressed, uncompressed_size) == 0);
free(decompressed);
free(compressed);
}
int main(int argc, char** argv) {
uint8_t* data = (uint8_t*) malloc(1024);
size_t data_length = 0;
while (!feof(stdin)) {
const size_t bytes_read = fread(data + data_length, 1, 1024, stdin);
data_length += bytes_read;
data = (uint8_t*) realloc(data, data_length + 1024);
assert(data != NULL);
}
test_round_trip(data, data_length);
free(data);
return EXIT_SUCCESS;
}
Archive with a bunch of crashes:
http://code.coeusgroup.com/afl-results/4697755e-2236-433b-b407-64e534cdfc90.tar.xz
—
Reply to this email directly or view it on GitHub
https://github.com/ConorStokes/LZSSE/issues/5#issuecomment-191175517.

Okay, figured out one of the issues - wasn't rounding up the last set of
controls to a full block in the parse calculation costs for the optimal
parsers - causing a slight size under-estimation which on very particular
data would cause it not to early-exit before the output parse. Early
versions actually overlapped the last control block with the trailing data,
so this was alright, but this slipped through when I changed it to always
use full control blocks. I'll do some more testing and see if I can uncover
any other issues.
On Wed, Mar 2, 2016 at 6:56 PM, Conor Stokes<EMAIL_ADDRESS>wrote:

Thanks, I'll have a look.
On Wed, Mar 2, 2016 at 6:32 PM, Evan Nemerson<EMAIL_ADDRESS>wrote:

can add them, but for reference data that can't be compressed smaller
than the input will just return the original data, so the maximum space
required is always input size.
Okay, in that case I don't think it's necessary.
If you're getting data that compressed larger than input, let me know, as
that's a bug.
Yeah, I am. The easiest way for me to generate examples was to throw
together a quick program and fuzz it, and I'm getting lots of results very
quickly. The most common issue is the compressed data being larger than the
input, but I'm also seeing lots of cases where decompress(compress(input))
!= input.
Anyways, here is the test program I'm using:
#include <stdio.h>
#include <stdlib.h>
#include <assert.h>
#include <stdint.h>
#include <string.h>
#include "lzsse2.h"
static voidtest_round_trip(const uint8_t* uncompressed, size_t uncompressed_size) {
uint8_t* compressed = (uint8_t*) malloc(uncompressed_size * 2);
assert(compressed != NULL);
LZSSE2_OptimalParseState* state = LZSSE2_MakeOptimalParseState(uncompressed_size);
assert(state != NULL);
size_t compressed_size = LZSSE2_CompressOptimalParse(state, uncompressed, uncompressed_size, compressed, uncompressed_size * 2, 7);
assert(compressed_size != 0);
if(uncompressed_size < compressed_size) {
fprintf(stderr, "%zu -> %zu\n", uncompressed_size, compressed_size);
abort();
}
LZSSE2_FreeOptimalParseState(state);
uint8_t* decompressed = (uint8_t*) malloc(uncompressed_size);
size_t decompressed_size = LZSSE2_Decompress(compressed, compressed_size, decompressed, uncompressed_size);
assert(decompressed_size == uncompressed_size);
assert(memcmp(decompressed, uncompressed, uncompressed_size) == 0);
free(decompressed);
free(compressed);
}
int main(int argc, char** argv) {
uint8_t* data = (uint8_t*) malloc(1024);
size_t data_length = 0;
while (!feof(stdin)) {
const size_t bytes_read = fread(data + data_length, 1, 1024, stdin);
data_length += bytes_read;
data = (uint8_t*) realloc(data, data_length + 1024);
assert(data != NULL);
}
test_round_trip(data, data_length);
free(data);
return EXIT_SUCCESS;
}
Archive with a bunch of crashes:
http://code.coeusgroup.com/afl-results/4697755e-2236-433b-b407-64e534cdfc90.tar.xz
—
Reply to this email directly or view it on GitHub
https://github.com/ConorStokes/LZSSE/issues/5#issuecomment-191175517.

Another issue found: if the very last control word is a 0 end to an
extended match, but is the first control in a control block, a control
block gets output that doesn't contribute to the input, so it adds no
output to the stream (buffer checks exit at end of output, but input cursor
hasn't advanced to the end). I'm fixing it by not outputting said last
control block.
On Wed, Mar 2, 2016 at 8:32 PM, Conor Stokes<EMAIL_ADDRESS>wrote:

Okay, figured out one of the issues - wasn't rounding up the last set of
controls to a full block in the parse calculation costs for the optimal
parsers - causing a slight size under-estimation which on very particular
data would cause it not to early-exit before the output parse. Early
versions actually overlapped the last control block with the trailing data,
so this was alright, but this slipped through when I changed it to always
use full control blocks. I'll do some more testing and see if I can uncover
any other issues.
On Wed, Mar 2, 2016 at 6:56 PM, Conor Stokes<EMAIL_ADDRESS>wrote:

Thanks, I'll have a look.
On Wed, Mar 2, 2016 at 6:32 PM, Evan Nemerson<EMAIL_ADDRESS>wrote:

can add them, but for reference data that can't be compressed smaller
than the input will just return the original data, so the maximum space
required is always input size.
Okay, in that case I don't think it's necessary.
If you're getting data that compressed larger than input, let me know,
as that's a bug.
Yeah, I am. The easiest way for me to generate examples was to throw
together a quick program and fuzz it, and I'm getting lots of results very
quickly. The most common issue is the compressed data being larger than the
input, but I'm also seeing lots of cases where decompress(compress(input))
!= input.
Anyways, here is the test program I'm using:
#include <stdio.h>
#include <stdlib.h>
#include <assert.h>
#include <stdint.h>
#include <string.h>
#include "lzsse2.h"
static voidtest_round_trip(const uint8_t* uncompressed, size_t uncompressed_size) {
uint8_t* compressed = (uint8_t*) malloc(uncompressed_size * 2);
assert(compressed != NULL);
LZSSE2_OptimalParseState* state = LZSSE2_MakeOptimalParseState(uncompressed_size);
assert(state != NULL);
size_t compressed_size = LZSSE2_CompressOptimalParse(state, uncompressed, uncompressed_size, compressed, uncompressed_size * 2, 7);
assert(compressed_size != 0);
if(uncompressed_size < compressed_size) {
fprintf(stderr, "%zu -> %zu\n", uncompressed_size, compressed_size);
abort();
}
LZSSE2_FreeOptimalParseState(state);
uint8_t* decompressed = (uint8_t*) malloc(uncompressed_size);
size_t decompressed_size = LZSSE2_Decompress(compressed, compressed_size, decompressed, uncompressed_size);
assert(decompressed_size == uncompressed_size);
assert(memcmp(decompressed, uncompressed, uncompressed_size) == 0);
free(decompressed);
free(compressed);
}
int main(int argc, char** argv) {
uint8_t* data = (uint8_t*) malloc(1024);
size_t data_length = 0;
while (!feof(stdin)) {
const size_t bytes_read = fread(data + data_length, 1, 1024, stdin);
data_length += bytes_read;
data = (uint8_t*) realloc(data, data_length + 1024);
assert(data != NULL);
}
test_round_trip(data, data_length);
free(data);
return EXIT_SUCCESS;
}
Archive with a bunch of crashes:
http://code.coeusgroup.com/afl-results/4697755e-2236-433b-b407-64e534cdfc90.tar.xz
—
Reply to this email directly or view it on GitHub
https://github.com/ConorStokes/LZSSE/issues/5#issuecomment-191175517.

Here are some more examples, this time also including some for lzsse8: http://code.coeusgroup.com/afl-results/33b4af09-22b3-465e-bde0-c428f372d1c3.tar.xz

Yeah, I have a set of fixes that have been applied to both which I will
merge in tonight, currently all compressors pass that first set, I will run
this set too.
On 3 Mar 2016 8:24 am, "Evan Nemerson"<EMAIL_ADDRESS>wrote:

Here are some more examples, this time also including some for lzsse8:
http://code.coeusgroup.com/afl-results/33b4af09-22b3-465e-bde0-c428f372d1c3.tar.xz
—
Reply to this email directly or view it on GitHub
https://github.com/ConorStokes/LZSSE/issues/5#issuecomment-191506674.

The first set of fixes are up now.
On Thu, Mar 3, 2016 at 8:27 AM, Conor Stokes<EMAIL_ADDRESS>wrote:

Yeah, I have a set of fixes that have been applied to both which I will
merge in tonight, currently all compressors pass that first set, I will run
this set too.
On 3 Mar 2016 8:24 am, "Evan Nemerson"<EMAIL_ADDRESS>wrote:

Here are some more examples, this time also including some for lzsse8:
http://code.coeusgroup.com/afl-results/33b4af09-22b3-465e-bde0-c428f372d1c3.tar.xz
—
Reply to this email directly or view it on GitHub
https://github.com/ConorStokes/LZSSE/issues/5#issuecomment-191506674.

With the fixes applied to both LZSSE2 and LZSSE8, I'm not getting any results larger than uncompressed, or any mismatches between original and round-tripped data on any of the fuzzing samples provided, but I'm using a Visual Studio compiled version for the test. I can't rule out any of the issues being platform/compiler specific.

Everything works for me, too.  I let the fuzzer run overnight against the latest version, no issues.  Closing.
I'll try to start fuzzing the decompressor soon; that's where most issues in compression libraries usually come up.


Update dlp-microsoft-teams.md

Deleting incorrect statement

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@chrfox - PR has been copy edited and is ready for final review.
Thank you.


Best way to use xterm ESC-sequences in scripts in Cmd e.g. bat, js, vbs, pl, py?

Your Windows build number:
Microsoft Windows [Version 10.0.17074.1002]

What you're doing and what's happening:
I want to use ESC-sequences in bat-, js-, vbs, pl, py-files in Cmd, but don't know how to switch so that they are used. I tried e.g. a program called input.js:

WScript.Echo("\x1B[1mEnter something\x1B[0m");
WScript.Echo("You entered " + WScript.StdIn.ReadLine());

And run it using cscript input.js //NoLogo. This prints:
Enter something
hello
You entered hello

What's wrong / what should be happening instead:
Enter something
hello
You entered hello

I can cure this by using start /wait /b before the command:
start /wait /b cscript input.js //NoLogo
Enter something
hello
You entered hello
Is start /wait /b the best way to use ESC-sequences from https://docs.microsoft.com/en-us/windows/console/console-virtual-terminal-sequences in a bat-, js- or vbs-program?

I think that cscript and curl should set that flag so that you can use xterm ESC-sequences with them.
Now you have to use this in Cmd.exe:
chcp 65001 | start /wait /b curl http://wttr.in/lund
But is that flag was set you could just use:
chcp 65001 | curl http://wttr.in/lund

cough @bitcrazed
We actually had a discussion about enabling the ENABLE_VIRTUAL_TERMINAL_INPUT flag in curl around here a few weeks back, after we started including it inbox. (IIRC) The discussion eventually came to the conclusion that someone would need to make a PR to the curl source itself to enable that flag for it's Windows implementation, and then we'd be able to take it from there.

Happy to revisit after Build ;)

how about a command in cmd (like setlocal enableVirtualTerminal) to help set the flag in batch scripts or other scripts?

For the record, you can totally just embed the actual ESC character in a bat file, and it'll work as you expect when you run it. EX:
@echo off
if (%1)==() (goto :usage)
if (%2)==() (goto :usage)
if (%3)==() (goto :usage)

echo ]12;rgb:%1/%2/%3
goto :EOF

:usage
echo Usage: cursor-color ^<red^> ^<green^> ^<blue^>
echo     where red, green, blue are color components in hex
echo     Ex: cursor-color FF 00 FF will set the cursor to Magenta
echo:

:EOF

(admittedly, that'll only set cursor colors on insiders)

For CUI WSH (JScript, VBScript, and others in cscript.exe), you don't need to update WSH itself, all you need is an automation object that lets you control the console configuration.
I built one that can not only toggle the VT processing, but get/set the input and output codepages, cursor size, buffer and window size, window title, colors palette, etc...

See VBScript source at https://gist.github.com/PhMajerus/e80334f1a04ad276d5f4e563ce30357d
The automation component is currently bundled with my ActiveScript Shell and PowerShell Tools, but Web site is temporarily offline. If anyone wants, I can post them somewhere alse.

@mobluse In PowerShell, you can do curl http://wttr.in/lund 2>&1 to force parsing of the output with support for VT escapes (I used to do so with the output of more.com before I installed less for Windows).

@ExE-Boss That doesn't work at all here. E.g. curl uses the internal curl for PowerShell, and when I use curl.exe I still only get uninterpreted escape codes, even though 2>&1.

I’m talking about PowerShell Core 6, which no longer has the curl to Invoke-WebRequest alias (it works for me even if I do curl.exe http://wttr.in/lund 2>&1 (referring to the curl that ships with Windows 10)).

This appears to be answered and curl (linked issue) appears to have merged this change. Closing.

For cmd, I like to set a variable:
:: Escape Code - %ESC% will have the value of "<ESC>" (0x1B).
SET ESC=

Then set my CSI:
:: Control Sequence Introducer - %CSI% is "<ESC>[" (0x1B 0x5B).
SET CSI=%ESC%[

Then you can use %ESC% and %CSI%. For example from the what zadjii-msft posted:
echo %CSI%12;rgb:%1/%2/%3%ESC%

You still have the unprintable  character, but it only needs to be written once and can be documented.

Here's a way in pure cmd that avoids you having to figure out how to insert invisible, unprintable characters:
@echo off & setlocal & setlocal enabledelayedexpansion
for /f "tokens=* delims=" %%a in ('forfiles /p %~dps0 /m %~nxs0 /c "cmd /c echo.0x1B0x07"') do @set arrChar=%%a
set ESC=!arrChar:~0,1!
set ST=!arrChar:~1,1!

REM rest of script...

Or, you could just do Alt+027 for ESC and Alt+07 for ST.

Im not sure why this was closed, Windows 10 1909 still has cURL 7.55.1

https://github.com/microsoft/terminal/issues/216

@nu8 this issue has nothing to do with curl?

@mike-clark-8192 oh, that's a technique I didn't know. I didn't know you could use forfiles like that, although it is in the documentation.


Added video capture support

Thanks for the contribution @AhmedDroid. This is really nice!
Two more things tho,

Can you omit the readme modification part?
It failing on our instrumentation test, can you check?

Thanks

Hi Esa Firm
First of, great job on the library!
Is there a plan to add the record video in near future ?

@siva-komaragiri I'll see what I can do to make this PR make it to version 3.0.0

Any update on this? Is there a way to record videos using this library? Great library btw, keep up the great work!


Too many dependencies

Please consider simplifying dependencies or providing a distributable package. Forcing plain users (who do not want to test, just run) to install dependencies likes bower, phantomjs, VCBuild.exe (!!!) is a limit in use and applicability. Thanks.
npm http 304 https://registry.npmjs.org/underscore

<EMAIL_ADDRESS>postinstall c:\dev\src\chromeHAR\node_modules\grunt-contrib
-imagemin\node_modules\jpegtran-bin
node index.js

‼ pre-build test failed, compiling from source...
‼ pre-build test failed, compiling from source...
x { [Error: getaddrinfo ENOTFOUND] code: 'ENOTFOUND', errno: 'ENOTFOUND', syscal
l: 'getaddrinfo' }
√ jpegtran built successfully!
x { [Error: getaddrinfo ENOTFOUND] code: 'ENOTFOUND', errno: 'ENOTFOUND', syscal
l: 'getaddrinfo' }
√ jpegtran built successfully!

<EMAIL_ADDRESS>postinstall c:\dev\src\chromeHAR\node_modules\grunt-contrib
-imagemin\node_modules\optipng-bin
node index.js

‼ pre-build test failed, compiling from source...
x { [Error: getaddrinfo ENOTFOUND] code: 'ENOTFOUND', errno: 'ENOTFOUND', syscal
l: 'getaddrinfo' }
√ optipng built successfully!

<EMAIL_ADDRESS>postinstall c:\dev\src\chromeHAR\node_modules\grunt-contrib-ima
gemin\node_modules\gifsicle
node index.js

‼ pre-build test failed, compiling from source...
x { [Error: getaddrinfo ENOTFOUND] code: 'ENOTFOUND', errno: 'ENOTFOUND', syscal
l: 'getaddrinfo' }
√ gifsicle built successfully!

<EMAIL_ADDRESS>postinstall c:\dev\src\chromeHAR\node_modules\grunt-contrib
-imagemin\node_modules\pngquant-bin
node index.js

? getaddrinfo ENOTFOUND

<EMAIL_ADDRESS>install c:\dev\src\chromeHAR\node_modules\karma\node_modules\socket.
io\node_modules\socket.io-client\node_modules\ws
(node-gyp rebuild 2> builderror.log) || (exit 0)

c:\dev\src\chromeHAR\node_modules\karma\node_modules\socket.io\node_modules\sock
et.io-client\node_modules\ws>node "c:\Program Files\nodejs\node_modules\npm\bin
node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visua
l Studio 2005 or 3) add the location of the component to the system path if it
is installed elsewhere.  [c:\dev\src\chromeHAR\node_modules\karma\node_modules
socket.io\node_modules\socket.io-client\node_modules\ws\build\binding.sln]
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visua
l Studio 2005 or 3) add the location of the component to the system path if it
is installed elsewhere.  [c:\dev\src\chromeHAR\node_modules\karma\node_modules
socket.io\node_modules\socket.io-client\node_modules\ws\build\binding.sln]

Flagging non gzip content or flagging none CDN content or non cache content,etc...

Thats definitely stuff we're interested in having inside of Chrome's network panel as well. If you use our latest frontend and build on that, then we would be able to upstream your features.


python3Packages.pytibber: 0.19.0 -> 0.19.1

Motivation for this change
Update to latest upstream release 0.19.1
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

3 packages built:

home-assistant
python38Packages.pytibber
python39Packages.pytibber