Automator: update<EMAIL_ADDRESS>dependency in<EMAIL_ADDRESS>

Generated by Automator - 2023-02-17T22:21:09+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

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 integ-security-istiodremote
/test integ-security
/test integ-security-multicluster

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

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 integ-security

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

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

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

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.

@istio-testing: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security

integ-security-istiodremote_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-istiodremote

integ-security-multicluster_istio_release-1.17
abc9bfdf81bb3e7f94c49a2c79098bb6f81fc58b
link
true
/test integ-security-multicluster

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


Move PureSwift/CDBus into PureSwift/DBus?

Hi and thanks a lot for doing this!
Just wondering if PureSwift/CDBus could just be moved into PureSwift/DBus? Or is there a reason for this extra package? Could just imagine it would be a bit easier to maintain...
Cheers! :)

OK I now understand this is how you bridge C-module into Swift-module => I will close this comment :)


Updating ESU doc to clarify that Win7 ESU includes .NET Framework 4.5…

….2 - 4.6.1 only as long as those versions are in support (through April 26, 2022).

@jamshedd : Thanks for your contribution! The author(s) have been notified to review your proposed change. @Deland-Han

I am checking with Jamshed. #on-hold


Apostrophe character incorrectly corrected to single quote

If I use a proper apostrophe (’) character, spell checker tries to correct it to a single quote ('):
You’ve

Thank you.


Support specifying server name, admin username and password of postgreSQL

I don't want to necessarily discourage this PR from being merged, but I do want to provide some context-- the historic rationale for deliberately not allowing users to specify server names, usernames, and passwords.

With provisioning and binding being automated, human users aren't meant to directly handle things like usernames and passwords.  (This is the "pets vs cattle" argument.)

There is a security benefit to identifiers incorporating a UUID and passwords being generated from random strings. Human users will tend to use usernames like "admin" or "postgres" and will often pair the username with an insufficiently complex password. Letting the system generate these values instead safeguards against brute force attacks.

Lastly, a more pragmatic reason that we incorporated UUIDs into system-generated identifiers (like usernames and server names) was that it almost completely eliminated the possibility of naming conflicts. Doing so meant we did not have to implement any logic to detect and mitigate naming conflicts. I do see that this PR adds a function isServerNameAvailable() and that's a step toward mitigating that. Race conditions are possible, however. Any given server name can become unavailable in between the time it's determined to be available and the moment when provisioning begins.

Again... I don't want to say not to do this. I only want to make sure that the historic rationale for not doing this is understood and carefully considered.

Hi @krancour , many thanks for the comment, sent you an email explaining the reason : )

Noticed something went wrong with mssql-dr lifecycle test. As current PR has no relationship with it and the feature in current PR is urgently needed, I'm going to force merge the PR into master.

@zhongyi-zhang  we should investigate what happened with mssql-dr module as the lifecycle test has been run for several times and mssql-dr test failed every time.


Fission: allow an attribute to have multiple "compute kernels"..

Code gen part of splitting out attributes to allow multiple compute functions.
Will implement fission options as separate PR
! @tranma @jystic

am going to merge this as-is: it's a fairly mechanical change, and if something were to go wrong everything would go wrong.
will add a test and options to control fission as next PR


Support annotation processors

It's common to use Java annotation processors during compilation.
Good examples are listed at https://github.com/gunnarmorling/awesome-annotation-processing.
Doing so should be easy.

Done!


Working on a cgo episode

Hey @jessfraz and @rakyll,
could you have a look at this change and see if it makes sense?

PTAL


app-stat.md -  added needed commas, corrected grammar.

No issue # to reference.

@guardrex yes, those (2) lines struck me as funny.  I wanted to say something along those lines "this setting" - did not want to be too presumptuous. This is my first contribution to the project.
If you feel it noteworthy to go over, I am game.

Sure thing ...
37 - Comma splice (compound verb)
39 - Comma splice or unnecessary: A splice if we take "is" as auxiliary and "identified" and "authenticated" as intransitive verbs. If "is" is a state verb, then perhaps one could argue this the other way. Where's an English professor when you need one??!! :smile: The other thing about this sentence is that it's short and there's no confusion when leaving out commas. There's another way to go, too, where the "[and] not authenticated" phrase is set off with commas on both sides making it nonessential. Going back to the it's short-no confusion concept anyway, I just felt the comma isn't needed.
45 - Subordinate conjunction phrases don't get commas. They're considered essential, and that's certainly true on Line 45. We sometimes fight about this with a compound introductory phrase (e.g., a prep phrase + a subordinate conjunction phrase ... 👊🚑😄 lol) ... but we'll probably simplify those cases into one phrase to avoid the debate.
67 - Unnecessary definite article with the adjective
84 - We use "session" (or "session state") to identify this subsystem. It's not necessary to say "each" session in this context. It might be a little nicer as "session state," and that would match the section heading.
 We're generally trying to remove "note" in these cases. For the change you put in, it shifts the subject from an assumed "you" to "this," and I'm trying to avoid pronouns as much as possible. I'm not sure how the whole team feels about it. I think the regular use of pronouns a slippery slope to unfocused technical writing ... they can be downright confusing if not carefully used. I think it's best to just slap a good noun in there in most cases.
Congrats on your first contribution! :tada:
We DO debate grammar and style from time-to-time, and I think it's healthy. Usually, we reach agreement. The MS Style Manual is fairly hefty, and the Chicago Manual of Style is over 1,000 pages! Yikes! lol


Consider a Windows port

The benchmark is clearly oriented towards server workloads, but we happen to have some Windows server boxes as well. Let's consider a Windows port for x86_64.

There are normally only few OS dependencies, but we display CPU related information and NUMA topology, which rely on /proc filesystem. This is Linux dependent. We need to decide what we do about it.

There are normally only few OS dependencies, but we display CPU related information and NUMA topology, which rely on /proc filesystem. This is Linux dependent. We need to decide what we do about it.


Open files on all targets except macOS standalone

Resolves #291 as much as possible by reverting behavior to picking files wherever possible.
The only exception is macOS standalone, where the app wouldn't have the required permissions for the arrows to work. So, I'm picking what I think is the lesser of two evils and having it stay with picking directories. At least users can two-finger scroll there...

Also resolves #290


AlamoreFire shouldn't save or create file if status code was 404

I has run into this issue recently when the server include body message with status code 404. The message was supposed to give a nice feedback to the user who access via the browser.
With the below API, AlamoFire did save the content which later confuse the App to think that the file was successfully downloaded.
Alamofire.download(urlRequest: URLRequestConvertible, to: DownloadRequest.DownloadFileDestination?)
Of currently, we can check response.response?.statusCode and then delete the file if it existed. But I think that AlamoFire should not save or create file if the status code different than 200.

Alamofire defaults to this behavior to allow developers the flexibility of adding whatever sort of behavior they want for different error codes, as a single default behavior may not be wanted or desired by everybody. It also forces the developer to handle such situations in the way that's most appropriate for their app. If you want such a behavior our documentation outlines how to do it.

Ok, may be some app need to save html 404 message when the link was not found or broken. I thought download mean to save only actual content to the destination file. Well, it just need to check and remove the file in the response callback. Thanks for the reply

If you want such a behavior our documentation outlines how to do it.
I have encountered the same issue, but I did not find where this gets outlined in the documentation.


Would it be wiser to check lsb_release first?

It may be good to try lsb_release before looking in files.
eg from ubuntu
root@buildbox01:~# lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.1 LTS
Release:	14.04
Codename:	trusty

Just a thought.

it's active on so few configurations by default that it's almost worthless, in my experience anyway, plus the overhead of the child process is way more than file reads. It'd be nice if it was consistent though.

Yeah just a thought, pretty sad this is the only way to recognise an OS.
Child process is meh, but yeah inconsistencies would be a killer.
Interesting comparing how ansible does it. https://github.com/ansible/ansible/blob/4e854192577475bc8c75d97af0db237970508b0e/lib/ansible/module_utils/facts.py#L76-L458

@wolfeidau that is interesting! It turns out we can add the following in os.js assuming ansible is correct:
/etc/oracle-release: OracleLinux
/etc/vmware-release: VMwareESX
/etc/openwrt_release: OpenWrt
/etc/alpine-release: Alpine

It also might be useful to see how https://docs.python.org/2/library/platform.html#unix-platforms is doing it.


Bootstrap script presents "successful run" info after failed run.

==> Fetching Shell::Command
==> Building Shell::Command
Compiling lib/Shell/Command.pm to pir
build stage failed for Shell::Command: Failed building lib/Shell/Command.pm
==> Please make sure that /home/lue/.perl6/2013.10-315-ga6eeb0b/bin is in your PATH

This makes trying to run panda annoying when you only scan the end result of the output ☺.

(I'm gonna assume it is)


Toggling full screen (F11) is not working, after opening a New Window at least once.

Toggling full screen, is not working, throws the following error, if you have previously opened a New window. If you toggle full screen on Main window, it toggles the newly opened window, not in the main window.

Steps to Reproduce
Scenario 1

Open Browser (dev/prod), click New Window and close the newly opened window
Try toggling full screen. It throws above error.

Scenario 2

Open Browser and click New Window, leave the newly opened window and return to main window.
Try toggling full screen, it throws the above error and toggles the newly opened window to fullscreen.

Can replicate this behaviour on Linux Mint 19 Cinnamon.

QA Verified


Feat: CognitoIdentityPool links

Hello to all, yesterday I tried to link CognitoIdentityPool to Nextjs app, and ION cannot manage to make Resource for it.
I have also tried to link it to Function, but again, without succeed.
Did anyone have same issue?

Can you share what you tried and if you got an error for it?

I have created CognitoIdentityPool
export const identityPool = new sst.aws.CognitoIdentityPool("IdentityPool", {userPools: [{userPool: cognitoUserPool.id,client: cognitoClientWeb.id}]});

Linked it to Nextjs App
export const web = new sst.aws.Nextjs("TestApp", {link: [cognitoUserPool, cognitoClientWeb, identityPool], path: "packages/frontend", openNextVersion: "3.0.2"});

And in Nextjs app there is no access to Resource.IdentityPool.id. Other links, cognitoUserPool and cognitoClientWeb works as expected.
Then I tried to link it to lambda function to test, and same behavior.

Yeah right now it's not exposed. You can see this by looking at the sidebar in the docs for the "Links".
https://ion.sst.dev/docs/component/aws/cognito-identity-pool/
I think we could add support for it.

@urosbelov hi friend, how did you end up working around this?


[RTL] - Remove timing loop in LSU

External signals data_rvalid_i and data_err_i were factored
into the external data_req_o signal
To improve timing, these signals are decoupled
The second part of an unaligned transaction will now be issued
even if the first received an error response
The state machine will service the abandoned requests
pmp_err_q fixed to only update at specific times

Thank you for the proposed update. I don't see anything wrong with it (and it would remove the combinational path on the data interface that I asked about; but of course not yet the similar path on the instruction side).
It would help me however if you could describe the LSU protocol with respect to data_pmp_err_i signal (I see pmp_err_q being used together with data_err_i, data_gnt_i, as well as data_rvalid_i).

Thank you for the proposed update. I don't see anything wrong with it (and it would remove the combinational path on the data interface that I asked about; but of course not yet the similar path on the instruction side).
It would help me however if you could describe the LSU protocol with respect to data_pmp_err_i signal (I see pmp_err_q being used together with data_err_i, data_gnt_i, as well as data_rvalid_i).

I'll add some extra comments to describe the timing / functionality of the two types of error

Thanks @arjanbink for your feedback and @tomroberts-lowrisc for adding the clarifying comment.
Shall we finally merge this PR?

Okay with me; thank you for the quick follow-up


Can’t boot HP ProBook 4540s

I have put macOS Big Sur on the USB, and I have configured the bios correctly for my computer. When I try to boot through the USB, it just boots from my SSD, and when manually navigating to the EFI file, it hangs with the screen still on but nothing showing. How can I get my machine to boot?

After looking up normal hackintosh guides, I have found that my graphics is the issue. Intel HD graphics 3000 only work with high Sierra and below.

See here
https://github.com/chris1111/HP-Probook-EliteBook-Package-Creator


OkHttp not sending all Cookies

I have OkHttp Cookiejar handling all cookies. I can loop over the received cookies and they are all present after logging into a website.
Once I try to create a new request only JSESSIONID and CONTOSO_USER cookie are sent.
       // COOKIE STORE
        CookieStore cookieStore = cookieManager.getCookieStore();

        // COOKIE JAR
        CookieJar cookieJar = new CookieJar() {
            private final HashMap<String, List<Cookie>> cookieStore = new HashMap<>();

            @Override
            public void saveFromResponse(HttpUrl url, List<Cookie> cookies) {
                cookieStore.put(url.host(), cookies);
            }

            @Override
            public List<Cookie> loadForRequest(HttpUrl url) {
                List<Cookie> cookies = cookieStore.get(url.host());
                return cookies != null ? cookies : new ArrayList<Cookie>();
            }
        };

        // NEW CLIENT
        OkHttpClient client = new OkHttpClient.Builder()
            .addNetworkInterceptor(new LoggingInterceptor())
            .cookieJar(cookieJar)
            .build();

            // REQUEST TO LOGIN TO WEBSITE AND RECEIVE COOKIES

After login I can print to console all the cookies with:
        for (Cookie cookie : cookieJar.loadForRequest(loginUrl)) {
            System.out.println("\n Cookie:" + cookie.name());
            System.out.println("\t Domain:" + cookie.domain());
            System.out.println("\t Value:" + cookie.value());
        }

This prints 4 cookies for :
CONTOSO_USER
CONTOSO_INSTANCE
CONTOSO_ANALYTICS
JSESSIONID
Yet when I make a request to the server after this login I only see JESSESIONID AND CONTOSO_USER being sent. I am checking this with the console statement and a networkInterceptor.
        Request quickFind = new Request.Builder()
                .url(quickFIndUrl)
                .post(RequestBody.create(MediaType.parse("text/x-markdown"), postBody))
                .build();
         System.out.println(" Headers : " + quickFind.headers() +"\n") ;

Closing in favour of stackoverflow question https://stackoverflow.com/questions/68569588/okhttp-not-sending-tokens

Closing in favour of stackoverflow question https://stackoverflow.com/questions/68569588/okhttp-not-sending-tokens

So, has this question been finished?


attrflags is not expanded

If "attrflags" contains some environment variable, result.bif file will contain something like
"[destination_cpu=a53-0,  offset=${DTB_OFFSET}] /mnt/ext/bla/blabla/build/tmp/deploy/images/blablabla/blablabla-system.dtb " instead of
"[destination_cpu=a53-0,  offset=0x1c80000] /mnt/ext/bla/blabla/build/tmp/deploy/images/blablabla/blablabla-system.dtb "
To prevent it, attrflags should be expanded.
https://github.com/Xilinx/meta-xilinx-tools/blob/881132b62dc01e57b8d9ace458a0005528179e14/recipes-bsp/bootbin/xilinx-bootbin_1.0.bb#L46
Change to
cfgval = d.expand(attrflags[cfg]).split(',')
https://github.com/Xilinx/meta-xilinx-tools/blob/881132b62dc01e57b8d9ace458a0005528179e14/recipes-bsp/bootbin/xilinx-bootbin_1.0.bb#L57
Change to
cfgval = d.expand(attrflags[cfg]).split(',')

Is this new on master or warrior branch?

Is this new on master or warrior branch?

On both, if "warrior" is rel-v2019.1

rel-v2019.1 is on thud and we dont see the issue

Ok. Try to add a "xilinx-bootbin_%.bbappend":
`
DTB_OFFSET = "0x2A00000"
DTB_OFFSET_zcu102-zynqmp = "0x1C00000"
specify BIF partition attributes for Device-tree blob
destination cpu for a53-0.
BIF_PARTITION_ATTR[dtb] ?= "destination_cpu=a53-0,offset=${DTB_OFFSET}"
BIF_PARTITION_IMAGE[dtb] ?= "${DEPLOY_DIR_IMAGE}/${MACHINE}-system.dtb"
BIF_PARTITION_DEPENDS[dtb] ?= "virtual/dtb:do_deploy"
BIF_PARTITION_ATTR_zynqmp = "fsbl bitstream pmu atf u-boot dtb "
`
And you will find the issue.


UI: Unable to create symbol at a given address

Version and Platform (required):

Binary Ninja Version: 3.4.4242-dev, 2e3a4286
OS: macos
OS Version: 13.3
CPU Architecture: arm64

Bug Description:
I would like to create a symbol at a memory location so that I see FETCH_CONFIG_END instead of 0x13d3d0 BN is not letting me do this, though. Creating a variable at this address does not update the code either.
Last but not least, there's no option to create a symbol when I navigate to the address.
Screenshots:

Hit y to create a DataVariable at that location. Type void. Then you can name it with N


"Cannot read property 'type' of undefined" with multiple inheritance levels

When generating TypeScript types from the following schema , I get "Cannot read property 'type' of undefined":
  type ApplicationForm {
    items: [Item!]!
  }

  interface Item {
    id: ID!
  }
  interface Field {
    id: ID!
    label: String!
  }

  type RichTextItem implements Item {
    id: ID!
    content: String!
  }
  type TextField implements Item & Field {
    id: ID!
    label: String!
  }

I think the code generator is confused by using both types that implement "Item" and "Item & Field".
The problem seems to be in pre-resolve-types.ts, in both transformPrimitiveFields and transformAliasesPrimitiveFields. At that point, the schemaType contains fields that fields do not.
A work-around, maybe even the solution, is to filter all schemaType fields before mapping them:
fields.filter(field => schemaType.getFields()[field]).map(...)

@TheReincarnator can you please share a live reproduction of that issue?
Thank you!

@TheReincarnator Hey, can you please share the operation that caused this issue? We have a potential PR that solves this issue, however, @mvestergaard is not able to produce a failing test (See https://github.com/dotansimha/graphql-code-generator/pull/6874).


feat: add datetime to string utils for lists

Adds two util functions to convert a list of DateTime to a list of str and vice versa. This is used for a new fix in the Python generator for formatting mock data values for generated unit tests.

:tada: This PR is included in version 3.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


🐛 On android device unable to get reference of camera, on iOS it is working fine.

What were you trying to do?
"react": "18.2.0",
"react-native": "0.71.10",
"react-native-vision-camera": "2.15.4",
const isFocused = useIsFocused();
<Camera
     ref={cameraRef}
     style={style.camera}
     device={device}
     isActive={isFocused}
     video={true}
     audio={true}
/>

Reproduceable Code
No response
What happened instead?
for android case i am reloading view until it get the reference of camera.
Relevant log output
No response
Device
Android
VisionCamera Version
2.15.4
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Pls fix

Hi, which is reference of camera., did you mean you are doing some code with cameraRef but first time it's undefined?

Hey! I've rewritten the entire Android codebase of VisionCamera from CameraX to Camera2 in the efforts of ✨ VisionCamera V3.
I just now completed the Camera2 rewrite and I believe the core structure is running, but there might be some edge cases to iron out. Can you try and test the PR #1674 for me to see if you can still reproduce this issue here?
Here's an instruction on how you can test that: https://github.com/mrousavy/react-native-vision-camera/pull/1674#issuecomment-1684104217
If the issue cannot be reproduced with that version/PR anymore, then hoorayy, I fixed it! 🎉
Otherwise please let me know and I'll keep this issue open to keep track of it.
Thank you!

@mrousavy Thank you for doing your hard work, I have not checked but i hope this will be helpful for all. I will use it in our upcoming project


Toggle to uneditable state upon saving a source

@megoth nice touch! Did you test it?

Yes, I tested it out using node-solid-server ^_^

Should we have a test URI where we can try out such changes -- would be awesome methinks ...

Even better would be some sort of unit tests, but it's difficult the way the code is structured now. We might get some testing using Snapshots (e.g. via Jest).

This edit has been overtaken by events, in that it was scooped up at the same time as the UI was revised when the syntax check was put in


Installation Loop

So I have this problem for over a year now where the steam bootstrapper would cause the lgsm csgo server installer to loop itself. This is what I get on a fresh CentOS 7.1 installation.
ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt"
This seems to be the error causing the infinite loop. I can get around it by
cd ~/steamcmd
rm -r ./linux32/
mv  ./package/tmp/* ~/steamcmd/
./steamcmd.sh +login anonymous +quit
However I'm not exactly sure what the problem is. :cry:

CentOS will always surprise me... I still wonder why people are actually using it. :o))
BTW, can you please output a details command ?
./csgoserver details
Seems like an issue with stdbuf, as googleing lead me to this kinda similar issue https://lists.gnu.org/archive/html/bug-coreutils/2011-07/msg00017.html

Well, some more googleing lead me to this.
https://github.com/dgibbs64/linuxgsm/issues/275
@dgibbs64 ?

@UltimateByte CentOS is great if you know what you're doing. It's just that a lot of people who don't use it anyway. ;)

CentOS is used because it's the classical well-supported enterprise Linux. That use case doesn't line up well with games, especially given Valve's predilection for requiring bleeding-edge Glibc and other stuff that doesn't fly in a lot of the professional Linux world.

./csgoserver details
Too bad that two of the best things don't go well together :(

Well, the issue is that many people use outdated versions of CentOS, which acts like a bitch for game servers, and that's pretty much all i know about this OS, so it doesn't appeal to me. lol
I think your issue might be related to this recent commit https://github.com/dgibbs64/linuxgsm/commit/44bbcf6917052b55ea1bab33b5f103b4ffec1d5a

on Ubuntu 16.04 server ,same error occur
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/coreutils/libstdbuf.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.

Yes I get the
ERROR: ld.so: object '/usr/lib/x86_64-linux-gnu/coreutils/libstdbuf.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.

error as well nowever does not cause me any issues. I have however never come across this looping issue.
[----] Failed to remove temporary unzip folder, continuing anyway

this might be your issue. For some reason it cannot remove the tmp dir. Could be a permissions issue. I recommend deleting the whole steamcmd dir and trying again as lgsm will just re download it again.

:+1:  on the fail to remove temporary files.
Guess this is solved.
Investigation showed that ld.so error is really harmless.


Simple automated install

Let's try this again. There should not be any breaking changes.

rake install pulls the submodules and symlinks the config files (no customization yet).
Removed all hard references to ~/.dotfiles. Figuring install location on our own. So ... should be able to install it anywhere (in home directory).
Symlinked gitconfig and gitignore for backwards compatibility.
Symlinked oh_my_zsh_zshrc for backwards compatibility.
Checked for oh-my-zsh install in zshrc, if installed then we source it.
Updated documentation.

I think that's it.

It seems like it's not loading the aliases from zsh/aliases..not sure why yet.

Ok, so I think the problem is in the Rakefile you were symlinking zsh/oh_my_zsh_zshrc but that is not a file that is normally used by zshrc. I changed it to use the actual zshrc file:
linkables += Dir.glob('zsh/zshrc') if want_to_install?('zsh')
That works just fine, it will overwrite or install the ~/.zshrc
With this tweak, the installer works correctly. If you agree with the change, then it's all good to go. I'll rename my repo to yadr and merge in the installer.

There we go. I fixed it and a couple merge conflicts. It should auto-apply now.
RE: renaming the repo ...
It's up to you but I wouldn't do that yet. We haven't made any breaking changes and that would be a nice thing to do when we  hit 1.0 with all the groundwork laid.
RE: your theme ...
I left it as-is to make sure we didn't break anything, but I think we should eventually set it to the default and provide functionality to override. It exists here: https://github.com/kylewest/yadr-old/blob/automated-install/zsh/zshrc.

So the reason I'm thinking about the repo rename is that if you were to pull on this branch now with the auto install, you may not realize that you have to run rake, and things would break if you didn't run it..

Try it out. Everything should work with or without rake. All the rake does right now is complete the steps you had defined in the readme. The only breaking changes would be the two files that moved but I created symlinks for them.


[Bug Report] Show a relevant error message when trying to use eval with an invalid script enging

Bug Description
Eval not working
Version 0.4.0
Steps to Reproduce
DM or in channel
.eval jda.guilds
Expected Result
I expect it to list the servers it in currently in.
Debug Output
`System Properties:
java.version = 20.0.1
java.vm.name = Java HotSpot(TM) 64-Bit Server VM
java.vm.specification.version = 20
java.runtime.name = Java(TM) SE Runtime Environment
java.runtime.version = 20.0.1+9-29
java.specification.version = 20
os.arch = amd64
os.name = Windows 10
JMusicBot Information:
Version = 0.4.0
Owner =
Prefix = .
AltPrefix = null
MaxSeconds = 0
NPImages = false
SongInStatus = true
StayInChannel = true
UseEval = true
UpdateAlerts = true
Dependency Information:
JDA Version = 4.4.1_353
JDA-Utilities Version = 3.0.5
Lavaplayer Version = 727959e9f621fc457b3a5adafcfffb55fdeaa538-SNAPSHOT
Runtime Information:
Total Memory = 40
Used Memory = 23
Discord Information:
ID =
Guilds = 3
Users = 18`
Additional Info
[16:40:19] [ERROR] [JDA]: One of the EventListeners had an uncaught exception
java.lang.NullPointerException: Cannot invoke "javax.script.ScriptEngine.put(String, Object)" because "se" is null
at com.jagrosh.jmusicbot.commands.owner.EvalCmd.execute(EvalCmd.java:46)
at com.jagrosh.jdautilities.command.Command.run(Command.java:323)
at com.jagrosh.jdautilities.command.impl.CommandClientImpl.onMessageReceived(CommandClientImpl.java:557)
at com.jagrosh.jdautilities.command.impl.CommandClientImpl.onEvent(CommandClientImpl.java:445)
at net.dv8tion.jda.api.hooks.InterfacedEventManager.handle(InterfacedEventManager.java:96)
at net.dv8tion.jda.internal.hooks.EventManagerProxy.handleInternally(EventManagerProxy.java:88)
at net.dv8tion.jda.internal.hooks.EventManagerProxy.handle(EventManagerProxy.java:70)
at net.dv8tion.jda.internal.JDAImpl.handleEvent(JDAImpl.java:160)
at net.dv8tion.jda.internal.handle.MessageCreateHandler.handleInternally(MessageCreateHandler.java:123)
at net.dv8tion.jda.internal.handle.SocketHandler.handle(SocketHandler.java:36)
at net.dv8tion.jda.internal.requests.WebSocketClient.onDispatch(WebSocketClient.java:952)
at net.dv8tion.jda.internal.requests.WebSocketClient.onEvent(WebSocketClient.java:839)
at net.dv8tion.jda.internal.requests.WebSocketClient.handleEvent(WebSocketClient.java:817)
at net.dv8tion.jda.internal.requests.WebSocketClient.onBinaryMessage(WebSocketClient.java:991)
at com.neovisionaries.ws.client.ListenerManager.callOnBinaryMessage(ListenerManager.java:385)
at com.neovisionaries.ws.client.ReadingThread.callOnBinaryMessage(ReadingThread.java:276)
at com.neovisionaries.ws.client.ReadingThread.handleBinaryFrame(ReadingThread.java:996)
at com.neovisionaries.ws.client.ReadingThread.handleFrame(ReadingThread.java:755)
at com.neovisionaries.ws.client.ReadingThread.main(ReadingThread.java:108)
at com.neovisionaries.ws.client.ReadingThread.runMain(ReadingThread.java:64)
at com.neovisionaries.ws.client.WebSocketThread.run(WebSocketThread.java:45)
Checklist

[X] I have looked for information about this within the documentation
[X] I have searched for similar issues on the issues page
[X] I am running the latest version of the bot:

This is because you're running java version 20, and the script engine we use was removed by that version. Try installing an older version (ideally 11).

Renaming this because a stopgap solution for this is to print an error when attempting to run the eval command instead of only printing a stacktrace to the console.


BaseGithubTask should reject invalid credentials

and raise a proper error, instead of just returning a NoneType repo if the user can't read it. see #408

The issue I recently encountered was not invalid credentials but the access was restricted by the Personal Access Token setting so the github.repository object was None.


Added OptiAPI

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

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

Hi @dougelliott
I have removed both the icon.png and the settings.json file from my PR.

@oliverbj Thanks! Once @sriyen-msft has a chance to review, we can move forward with merging.


No recognition of RequiredPackages in a project .sty file

I think I saw a commit from @stenwessel about this so I think this was implemented?
testfile.tex:
\documentclass{article}

\usepackage{testpackage}

\begin{document}

    \begin{align*}
        \xi
    \end{align*}

\end{document}

testpackage.sty:
\RequirePackage{amsmath}
Results in the IJ error
DefaultEnvironment requires amsmath package
while everything compiles of course just fine.
I think I built from commit c87347ed6b5b4ff5b974869f985d3cf3483afc62 but I'm not so sure now. But rebuilding didn't help, so let me know if you can reproduce? Hopefully it's because I'm on an older version somehow :/

sty files from \usepackage commands are not being processed when determining file inclusion sets. Will work on a fix.

Ah okay then I misremembered the feature, I see now that #151 only speaks about documentclasses, not packages.


Uses itemstack sensitive version of getFoodProperties

I had a report of a crash in my mod issue 11. This PR uses the itemstack sensitive version of getFoodProperties. This should also fix your issue 10

Thank you. I'll take a look.


Replace most instances of mem::uninitialized with mem::MaybeUninit

Only two instances remain:

For the deprecated sys::socket::CmsgSpace::new.  We should probably
just remove that method.

For sys::termios::Termios::default_uninit.  This will require some
more thought.

@Susurrus this is starting to hold up other PRs, so I'm going to merge it tonight.

bors r+


Test Non-Patterned Veg

Given a location  with only some pattered vegetation:

The offset50 time series will display limited seasonal variation:

The NDVI time series also shows seaonsal variation:

In another example, with no patterns at all:

The offset50 time series fails:

While the NDVI time series displays seasonality:

Presumably, with the use of direct NDVI time series, we can use Landsat satellites as we don't need the resolution to resolve the patterns


Grouping use-statements sometimes leaves gaps

I have been noticing this issue often and have been meaning to attempt to fix it. I haven't had time and I keep forgetting so I am creating this issue as a kind of reminder. Also hoping that someone will know exactly why this is happening and be able to submit a fix faster than me.
It looks like when sorting use-statements in fairly complex groups and two groups consecutively are not being used there are some additional spaces added.
Example pulled from my test classes.
use Project\Core\AClass;
use Project\Core\BClass;
use Project\Core\CClass;

use PHPUnit_Framework_MockObject_MockObject as MockObject;

With the following configuration:
use-sort:
  group:
    - Project\Core
    - Project\Integration
    - [Symfony, Sensio, Doctrine]
    - _main
  group-type: each
  group-skip-empty: true
  sort-type: alph
  sort-direction: asc

Please note that group-skip-empty is enabled also.
Expecting output:
use Project\Core\AClass;
use Project\Core\BClass;
use Project\Core\CClass;

use PHPUnit_Framework_MockObject_MockObject as MockObject;

@matt-usurp Great!
Could you please add some tests failing in a branch¿?
After that we can add the fixes :)
Thanks!

@mmoreram Yeah sure, I don't know how you want to do this but I have a branch on my fork.
https://github.com/matt-usurp/php-formatter/tree/issue-24-grouping-whitespace
I added two failing tests that look like they will cover it. One for when removal of empty groups is enabled and one without, so looks like maybe skip empty groups isn't the issue.

Not to worry, I have applied the fix and updated the PR.
@mmoreram Can you take a look please, it would be great to get this fixed.


Cannot catch errors with OpenSSL CLI spawn

When the OpenSSL CLI is unavailable (or presumably otherwise has a problem), the resulting error cannot be caught promise-style.
const acme = require('acme-client');
acme.openssl.createPrivateKey().then(() => {

}).catch((e) => {
  console.error('CAUGHT', e);
});

The resulting output:

events.js:167
throw er; // Unhandled 'error' event
^
Error: spawn openssl ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:229:19)
at onErrorNT (internal/child_process.js:406:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
at Function.Module.runMain (internal/modules/cjs/loader.js:746:11)
at startup (internal/bootstrap/node.js:240:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:564:3)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:235:12)
at onErrorNT (internal/child_process.js:406:16)
[... lines matching original stack trace ...]
at bootstrapNodeJSCore (internal/bootstrap/node.js:564:3)

Hopefully, this can be a non-issue once #3 is wrapped up.  Thank you for your efforts!

Hi, and sorry about the delay on this one.
Looks like openssl-wrapper doesn't catch errors when spawning the openssl process, for example when the command is unavailable. Fixed in b37fc13cf46c8dc7ad8afd09de0f2c59c7fa89b1, landing in v2.2.1.


Update README.md

Updated readme for correct android file name

Available in v5.3.3.
Thanks again!


Add MQTT dispatcher

Description
This PR add's a MQTT dispatcher. Sending Tesla EV fleet telemetry (e.g., SoC) to an MQTT broker provides real-time, lightweight, and efficient data streaming. MQTT's publish-subscribe model scales well for growing fleets, enabling seamless integration with IoT platforms and data analytics systems for improved monitoring and management.
Type of change
Please select all options that apply to this change:

[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Documentation update

Checklist:
Confirm you have completed the following steps:

[x] My code follows the style of this project.
[x] I have performed a self-review of my code.
[x] I have made corresponding updates to the documentation.
[x] I have added/updated unit tests to cover my changes.
[x] I have added/updated integration tests to cover my changes.

OMG, watching intently :)

The code hase been updated with the issues mentioned in the comments above.

There is now support for MQTT topics: metrics, alerts and errors.
Other minor changes and fixes.

Add detailed MQTT README.md explaining architecture, design choices, and configuration

@erwin314 is there something I can help with to get this fixed?
I tried to build your code and currently fail to do so.

@erwin314 is there something I can help with to get this fixed? I tried to build your code and currently fail to do so.

Thanks for reaching out and offering to help! The code was working, but it's been in pull-request mode for a while now. To move forward, perhaps @agbpatro, @aaronpkahn, @ThomasAlxDmy, or @patrickdemers6 could provide feedback on whether this code has a chance of being merged. If there's potential, I’ll update it so it passes all tests again. If merging isn’t feasible, I’m happy to create a dedicated fork focused solely on MQTT.

Hi everyone, I've updated the code, and it should now pass all the tests. However, I'm still unsure if investing my time in this is worthwhile, as it's unclear whether it has a potential for being merged.

There is 1 suggestion I would like to make, currently you return a json object for each topic, I would rather see the value directly.
Currently:
Topic: telemetry/[VIN]/v/Locked
Value: {"value":"true"}

Better:
Topic: telemetry/VIN/v/Locked
Value: true

Why do you put the value inside the key value?
It requires more processing on the consumer to actually read a value.

@erwin314 is there something I can help with to get this fixed? I tried to build your code and currently fail to do so.

Thanks for reaching out and offering to help! The code was working, but it's been in pull-request mode for a while now. To move forward, perhaps @agbpatro, @aaronpkahn, @ThomasAlxDmy, or @patrickdemers6 could provide feedback on whether this code has a chance of being merged. If there's potential, I’ll update it so it passes all tests again. If merging isn’t feasible, I’m happy to create a dedicated fork focused solely on MQTT.

Thank you, this is awesome. We should definitely get it in.

There is 1 suggestion I would like to make, currently you return a json object for each topic, I would rather see the value directly.
...
Why do you put the value inside the key value? It requires more processing on the consumer to actually read a value.

Thank you for the suggestion and for taking the time to review my pull request! I appreciate your feedback.
If the system evolves to include additional features or richer data, using JSON ensures that existing consumers remain compatible as long as they continue extracting the known keys. In contrast, returning direct values can make maintaining backward compatibility more difficult.
By consistently returning a JSON object, we standardize the data format across all topics, regardless of the type or complexity of the value. This approach allows consumers to parse messages using uniform logic, reducing the likelihood of errors. If some topics return raw values while others return structured data, client-side code must accommodate both cases, leading to increased complexity.
Additionally, JSON maintains the data type of the value, helping to avoid misinterpretation. For example, {"value": "true"} clearly indicates a string representation instead of a boolean. This distinction is important because the type of a field may vary by vehicle type or even only by the software version running on it. This might be relevant to the receiving systems.
While it’s true that consumers need to perform an extra step to extract the value, this processing is typically negligible in practice. Parsing JSON is a lightweight operation, supported natively by nearly all programming languages and platforms. On the other hand, returning raw values requires consumers to handle data differently for each topic, which increases the overall complexity of the client-side implementation.
That said, I’m open to further discussion if you feel strongly about this point or have alternative suggestions that might achieve the same benefits with less overhead.

@erwin314 is there something I can help with to get this fixed? I tried to build your code and currently fail to do so.

Thanks for reaching out and offering to help! The code was working, but it's been in pull-request mode for a while now. To move forward, perhaps @agbpatro, @aaronpkahn, @ThomasAlxDmy, or @patrickdemers6 could provide feedback on whether this code has a chance of being merged. If there's potential, I’ll update it so it passes all tests again. If merging isn’t feasible, I’m happy to create a dedicated fork focused solely on MQTT.

Thank you, this is awesome. We should definitely get it in.

Thanks for the positive feedback—glad to hear there’s interest in getting this merged! Could you provide some guidance on the steps needed to move this forward?

Thanks for taking the time to answer.

Additionally, JSON maintains the data type of the value, helping to avoid misinterpretation. For example, {"value": "true"} clearly indicates a string representation instead of a boolean.

Well, actually that is the problem...
It is a boolean and because you use a transformer from the logger it is casted back to a string, see here.
And secondly there is actually no need to always include a json with the value key.
in the MQTT topic it's always stored as a string, you have to do a json parse anyhow.
And that fixes it is well.
Example in python:
>>> import json
>>> response='{"value": true}'
>>> json.loads(response)
{'value': True}
>>> response='true'
>>> json.loads(response)
True

As you can see both are correctly parsed as a boolean.
AS far as I know this is the case in all languages.
So no need to wrap the json in the value key.
Just to make sure you see what I mean let's do it again but this time not as a boolean but as a string
>>> import json
>>> response='{"value": "true"}'
>>> json.loads(response)
{'value': 'true'}
>>> response='"true"'
>>> json.loads(response)
'true'

So also a string is correctly parsed as a string.
I would suggest to write your json as follows:
diff --git a/datastore/mqtt/mqtt_payload.go b/datastore/mqtt/mqtt_payload.go
index 3692c3e..595a9b9 100644
--- a/datastore/mqtt/mqtt_payload.go
+++ b/datastore/mqtt/mqtt_payload.go
@@ -19,7 +19,7 @@ func (p *MQTTProducer) processVehicleFields(rec *telemetry.Record, payload *prot
                        continue
                }
                mqttTopicName := fmt.Sprintf("%s/%s/v/%s", p.config.TopicBase, rec.Vin, key)
-               jsonValue, err := json.Marshal(map[string]interface{}{"value": value})
+               jsonValue, err := json.Marshal(value)
                if err != nil {
                        return tokens, fmt.Errorf("failed to marshal JSON for MQTT topic %s: %v", mqttTopicName, err)
                }

So to summarize, I think you are using the wrong approach by going to the transformers which seems to be invented for the simple console logging and casting everything to strings.
It would make more sense to use the probuf types when creating the json data, and secondly do not wrap everything a map with the key value

...
So to summarize:

I think you are using the wrong approach by going to the transformers which seems to be invented for the simple console logging and casting everything to strings.
It would make more sense to use the probuf types when creating the json data
Do not wrap everything a map with the key value as you could see in the example above, it's not needed to preserve correct json parsing

From what I understand, PayloadToMap() doesn’t inherently cast everything to a string. Instead, most fields seem to be using a string-based protobuf defined by the vehicle. However, I'll double-check to confirm. (note: the link you mentioned does not seem to show a string cast?)
You’ve made a great point about the value being JSON-parsable. This definitely seems like an improvement worth exploring. While we would lose the flexibility to add additional fields, it’s fair to question whether retaining that flexibility might be over-engineering in this case. I'll make the code change and test if it's indeed an improvement a.s.a.p

I have updated the way the MQTT values are formatted. They now directly contain the value as json, so they are no-longer wrapped in an extra value entry. And the Invalid field value is now translated to null in json. Even though "null" might not strictly be the same as "invalid", it seems the most straight forward approach.

I've added MQTT support for connectivity events, with one topic per VIN. I assume there's at most one connectivity (dis)connected at a time?
Regarding ConnectionID, it seems to change every time a car (re)connects. This suggests it’s not an ID for a connection to a specific telemetry server, but rather a random ID generated for each new connection. That's why I put it in the value and not in the topic. I'm not sure what happens if a car is connected to multiple telemetry servers (can it even do that?)
Let me know if there’s any clarification or adjustment needed for this approach!

@ThomasAlxDmy To me this looks feature complete now. Can you pull some strings to get this unblocked?


Additional info in the IPv6 page

File: config/daemon/ipv6.md
Need to specify
{
"ipv6": true,
"fixed-cidr-v6": "fd00::/80"
}
to allow the docker daemon to restart (if you only need IPv6 work and not communicate with anything, such as in package builds of IPv6 usable software)

Thanks for sharing the issue. It appears fixed in https://github.com/docker/docker.github.io/commit/1b319c30a57334d82096bc4e1cabfab3a8b6dda1


Change code according to the PSR-2

According to the PHP-FIG (http://www.php-fig.org/), some PHP implementations need to be standardized.

Thanks for contributing to SendGrid Open Source! We think it's awesome when community members contribute to our projects and want to celebrate that.
The following link will ask you to authenticate with Github (so we can verify your identity). You'll then be asked for your shipping address so that we can send you a thanks for contributing.
Click Here to Continue »
Once again, thank you!


flowlogs_reader: init at 1.0.0

Motivation for this change
Introduce flowlogs_reader to Nix for more convenient cloudwatch/vpc flow log reading from amazon.
Things done

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

[x] NixOS
[ ] OS X
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Not sure why the pytests tests fail on travis, but builds fine for me. Thanks! :beers:


Used numpy for much faster python implementation

This numpy implementation runs in ~0.72sec on my m2 air.
Edit: Knocked another 100ms off with array broadcasting, main now runs in 0.65 sec, 0.54sec without IO.

Thanks for the PR. I got roughly the same speed on my machine


Getwurebootstatus only returns bool rebootrequired property now

The IsPendingReboot property was always returning as true because (Get-WURebootStatus) returned multiple properties instead of returning a true/false value.  I updated the script to only return the "RebootRequired" property

Pretty sure this comment change now runs and returns correct data, but when the Get-WURebootStatus returns true meaning a reboot required it also prompts you asking if you want a reboot.  Which when ran in PDQ give you an error because it is prompting the user for a response asking if you want to reboot.  Before merging the change, you might want to also fix the handling of this new response.

Would you still need it to the .RebootRquired and the silent parameter?  It will be a little bit before i can test. I'm just asking. Because before it didn't work at all.


Installation Error

when I run this command  npm install<EMAIL_ADDRESS>--save in my project  I get these errors
`
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="GitHub Package Registry"
npm ERR!      /Users/muhammadsaleem/.npm/_logs/2020-09-03T14_15_25_711Z-debug.log
muhammadsaleem@Muhammads-MacBook-Pro test %  npm install<EMAIL_ADDRESS>--save
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@paytabscom%2Freact-native-paytabs-library - Not found
npm ERR! 404
npm ERR! 404  '<EMAIL_ADDRESS>is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR!      /Users/muhammadsaleem/.npm/_logs/2020-09-03T14_15_55_240Z-debug.log`

Hi @paytabscom , @chockwadi  am also facing the same issue

@chockwadi  This works fine for installing  npm install<EMAIL_ADDRESS>--save
In order to be able to install the package, on top of your solution I had to add couple of lines.
created .npmrc file in the root of the project and added the following:
@paytabscom:registry=https://npm.pkg.github.com
@{{OWNER}}:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken={{TOKEN}}
In this case the owner will be: AdlyPayTabs >> @AdlyPayTabs:registry=https://npm.pkg.github.com
And to generate a personal token, navigate in your GitHub account to:
Settings > Developer settings > Personal access tokens
Generate new token
From the permissions select at least read:packages
Click Generate token and copy the token


Update docs with limitation

This PR updates the docs with the limitation regarding referencing issues in another repository.
Closes #33

@simoneb we can merge this one. I don't have permissions.

now you can


You can deploy the stream with no Approval [SBK-246]

Since step 1 is token approval, Step 2 should be greyed out until Step 1 is complete and confirmed

As a part of the update for the CreateStream button, just predicate the "open stream" button on having any allowance for the token to the stream manager


Domain activation is Failed –  One or more of the CNAMEs already associated

App Id: d23ultcrzc1rvs
Region: eu-central-1
Step: Domain activation
Status: Failed
Issue/question
I want to migrate two subdomains (www. + preview.) to amplify. After adding preview. I wanted to add www. as separate Custom Domain. Amplify complained, that the domain is already used, so I deleted preview.
-> After waiting ~1.5h I tried to add www. + preview. together. But I got the same error.
Another subdomain of same TLD (api.) is already connected to CloudFront.
Error message
Error message: One or more of the CNAMEs you provided are already associated with a different resource.

Hello @Purii , it would take some time to remove the previous settings. Could you please try after 6 hours. If you are still not able to connect your domain, please let us know.

Hello @Joycehao19 ! Thanks, it worked 👍


vdk-core: pass execution result through context

Why?
We'd like to have just one exit point for data jobs where error logging happens and propagate all errors up to it.
What?
Pass execution result in job context when exceptions are thrown. This way, we still get to throw the exception and have the result at a later hook, e.g. we have the execution result from run_job inside the run method, even if an exception was thrown during the run. If an exception was thrown, we can catch and log it at the exit point.
The side effect is that plugins have to check the job context for hook implementations that are wrapping if an exception was thrown.
How was this tested?
Ran tests locally
Ran plugin tests in CI/CD
What kind of change is this?
Potentially breaking change

can you explain how this is a potentially breaking change?

can you explain how this is a potentially breaking change?

Older versions of plugins that run against this version of core might not work correctly, because hook results are handled differently when an exception is thrown.

Don't make changes in vdk-core and plugins in the same PR.
Generally I discourage changing multiple plugins/projects in same PR unless the change is trivial (bumping version of library x in n plugins)
First is the change in core (non-breaking) then it is its adoption in separate PR in the plugins.

@antoniivanov I can't think of a way to make the vdk-core change non-breaking. It will always break backward-compatibility, because we have a whole different case where we pass execution results in the context and it needs to be handled by plugins. It makes more sense to change the plugins together with core.

Closing this until I can make it backwards-compatible.


Split data binding page in docs

From https://github.com/mui/mui-toolpad/issues/1954
Split data binding section in "binding state" and "event handling" pages.
https://deploy-preview-1996--mui-toolpad-docs.netlify.app/toolpad/data-binding/binding-state/
https://deploy-preview-1996--mui-toolpad-docs.netlify.app/toolpad/data-binding/event-handling/

@prakhargupta1 Will you handle the rest of this PR? I can assign it to you.
Let me know if I can help with anything else here or if there's anything else I could add or fix here.
Also, we discussed that maybe "Data binding" should not be its own section, but be inside some other section?
In that case if we have a final decision I can move them inside the right section in this PR.
I guess we could put it under "Building UI" but I don't mind it being its own section either.

In terms of docs structure, maybe we should just devote some sync meeting time and think about it holistically? In the meantime I don't think it should block merging this PR. It shouldn't be a big effort to rearrange pages afterwards.

@apedroferreira You can remove my commits as all of it was recorded in dark mode. I'll redo ot and create a separate PR.
Also, let's utilize coming Friday's product meeting to discuss docs structure.


Documentation missing dependency for Kryo

The Kryo serializer now requires the objenesis library from objenesis.org or mvnrepository but it is not mentioned in Add custom serializers to your webapp.
See here for more info

That's right, it's a very big mistake

Thanks for reporting! You can also improve the wiki, has been done in the meanwhile.


Background noise

Can you help me to understand how is the background noise being handled, as before in the original script it picked up on the most basic of sounds? Its very clear that the background noise isn't being captured in the full stack app (I got the full stack app running) and if I talk properly then it gets captured. I want to understand have you made any changes to the processing sound in the frontend or the backend

Hey, I'm using Silero for voice detection with a threshold to avoid picking up background noise.
If you managed to get the full stack version running - mind opening a PR? I had issues with streaming audio to Gemini.

Yeah sure will open a PR


etcd v3 api support

etcd v3 api support

@ChelinTsien good PR

Because the v3 version of the larger changes, so the v3 interface data format are converted to v2. The test is just through the dashboard to go through the operation of the process once again

in  config.yaml file add :
etcd:
  host:                           # it's possible to define multiple etcd hosts addresses of the same etcd cluster.
    - "http://<IP_ADDRESS>:2379"     # multiple etcd address
  prefix: "/apisix"               # apisix configurations prefix
  timeout: 30                     # 3 seconds
  protocol : "v3"
  api_prefix : "/v3alpha"   # v3, v3beta,v3alpha etc

Added before #1943,  why not review my pr?

add aws sign why we need this commit?


CUDA self-recursion tests

Self-recursion was mostly already working on the CUDA target due to the recent dispatcher refactoring work. This PR mainly adds tests for it and some fixes to ensure more use cases work correctly. The test cases are directly taken from numba.tests.test_recursion, with modifications to adapt them to the CUDA target. Present recursion limitations are:

Self-recursion only works with the same types - calling the same function recursively with different types does not yet work, because it seems to require insertion of unresolved references, which is not supported by the CUDA target (e.g. JITCUDACodegen.insert_unresolved_ref() does not exist).
Mutual recursion is not supported.

Since I noticed #8036 whilst working on this, there are some additional tests and a small fix related to it here - one of the recursion test cases raises in a device function.
The changes here are:

Updating the docs to clarify limitations on assert and raise, and to document the recursion support.
A fix to _MinimalCallHelper.get_exception(), so that it returns the correct number of items. It was supposed to return the location info as well - given that the exception is unknown there's no meaningful info that can be given, but at least returning None for it allows the result to be unpacked. With this change, the fact that an unexpected exception occurs can be reported as a SystemError, instead of just returning a spurious unpacking error from inside the CUDA target.
Compilation of device functions registers the dispatcher with type inference, so that recursive calls can be typed.
The acquisition of self._compiling_counter in the CUDA dispatcher is moved into compile_device() up from get_call_template() - when it was in its former location, some recursive calls were not detected correctly because the compile counter was 0 if compile_device() was directly entered rather than coming through get_call_template().
Adding the opt kwarg to the simulator's jit decorator - this is needed because some tests pass opt=False to the decorator.
Add a new decorator, xfail_unless_cudasim - for example, I would like to mark some of the recursion tests that have issues due to #8036 as xfails, but they succeed on the simulator because it executes the recursion successfully, or it successfully propagates an exception from a device function.
Addition of self-recursion tests for the CUDA target as detailed above
Addition of an xfailing test for raising in a device function.

gpuci run tests

gpuci run tests

gpuci run tests

@stuartarchibald Many thanks for the review - I believe I've addressed all comments. The CI fails seem to be some sort of conda / dependency issue unrelated to this PR, so I think it's ready for another look.

@stuartarchibald Many thanks for the review - I believe I've addressed all comments. The CI fails seem to be some sort of conda / dependency issue unrelated to this PR, so I think it's ready for another look.

@gmarkall Many thanks. Any chance you could resolve the merge conflict please? Pushing that patch should also re-run CI against main which now has the issue with the conda package dependencies fixed (well, worked around!). Thanks again!

@stuartarchibald thanks for looking, conflicts now resolved.
gpuci run tests

Buildfarm ID: numba_smoketest_cuda_yaml_136.


Replace in-house rand with absl::Random for backoff with HWAES disabled

Replace randen_hwaes.cc of abseil with randen_hwaes_nohw.cc because randen_hwaes.cc uses HW-specific instructions which require particular compiler options which are not easy to add for certain build environments. This is a workaround and I'll work with Abseil team to have more maintainable way to address this.
Related to https://github.com/grpc/grpc/issues/26478
Fixes #26476 and fix-forward #26463

grpc_build_artifacts_multiplatform: running

linux/aws/grpc_aws_basictests_php: running

let me know once this is ready for review.

@jtattermusch Abseil recently updated so that it can be used in gRPC without this problem. (https://github.com/grpc/grpc/pull/27193) Rather having this workaround, let's wait until they release the next LTS release.

@jtattermusch Abseil recently updated so that it can be used in gRPC without this problem. (#27193) Rather having this workaround, let's wait until they release the next LTS release.

Good call. I wasn't fan of the workarounds in this PR, and not needing a workaround sounds much better. Thanks for investigating this!


Doesn't support program mode for RHP 600 U

First of all, thanks a lot for this, it works really well (with occasional unavailable data).
I am using this with an RHP 600U and if I set it to any preset (Comfort1/2, Economy 1/2), I can see it in home assistant, but if I used scheduled programming, called Program mode in the Komfovent local page settings, it's not visible as current operation mode in this integration.
It would be nice to have this.
Thanks again

For reference, see #1 and #2.

I have re-enabled the programming mode in the latest version. I haven't checked whether it still causes issues with the rest of the integration though.


Set correct partition for efibootmgr

Hello,
I just tried out arch-secure-boot since it seems like a lightweight alternative to grub - very nice idea!
After a reboot the boot entry vanished.
At the moment add-efi does not really work because efibootmgr sets the partition to 1 even if you pass it with -d. So I used bash expansion to extract the partition number and for my use cases it works quite well now but I am not quite sure this covers every edge case.

Hi, thanks for the feedback and the PR!
Just out of curiosity, could you show me what do findmnt -n -o SOURCE -T "$ESP" and fdisk -l return in your case? I wonder why I never hit this bug...

debug.txt
I added efibootmgr -v as well.
secure-boot-linux is the unpatched version which will vanish after a reboot and secure-boot-linux-debug is patched.

Thanks! Very interesting. Out of curiosity, I see your ESP partition is marked as Linux filesystem (and in my case it is EFI System), is it formatted in FAT32 and it's just a metadata mismatch, or you actually have a different file system (which I thought is not possible)?

Yes it is FAT32. The funny thing is, I just reinstalled with your dotfiles since I thought at first that the vanishing boot entry was a user mistake (you wrote in https://github.com/maximbaz/arch-secure-boot/issues/1 that it is tailored to your dotfiles) and after it happened there as well, I started to investigate.
I just skimmed over your install skript, but I would guess that this line is wrong:
https://github.com/maximbaz/dotfiles/blob/master/install.sh#L115
The correct argument should be --typecode.

Hahaha, it's always nice to discover bugs in my own, supposedly tested, scripts 😁  I tried to keep install.sh up-to-date with all the recent changes including move from GRUB, but frankly I never had to install Arch from scratch for almost a year now. Thanks for your finding, I will fix it 👍


[tests-only][full-ci]Run local api tests in reva

fixes: https://github.com/owncloud/QA/issues/764

Making local-api tests run on reva is not possible for now as ocis depends on reva and reva depends on ocis. Closing this issue for the same reason.


Implement a local geometry cache in MeshAsset.

See issue #332. Ogre is not very smart with geometry buffer accesses, so create a local geometry data buffer into the mesh assets. With an appropriate API, this can be useful for scripts as well.
The geometry cache will mostly be used for raycasts and other intersection queries, so investigate the possibility of using automated vertex data optimization to reduce tricounts for this.

The next version of MathGeoLib will contain SSE-optimized ray-triangle mesh routines for this purpose http://dl.dropbox.com/u/40949268/RayTriMeshSSE.png


Update log-analytics-powerbi.md

PG owner for this page.
Adding 2 points to the note at the top of the page:

That the power bi export option is no longer in Preview settings for upgraded workspaces, as the feature is a GA feature in Search V2.
That users may run into access problems in the Power BI export step since this requires Azure RBAC. Many users may only have Classic Portal access to a workspace, but not have access to the subscription it is tied to, denying them access when Power BI desktop makes the ARM call using their creds to the workspace.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@ehissey : Thanks for your contribution to the Azure documentation! The author, @bwren, has been notified to review your proposed change.

#sign-off


[e2e]: generic workflow_dispatch main large-subjects-adversarial-sha256 slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6079704441
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.large-subjects-adversarial-sha256.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.large-subjects-adversarial-sha256.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Tue Sep  5 03:02:44 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6088424626
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.generic.workflow_dispatch.main.large-subjects-adversarial-sha256.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.generic.workflow_dispatch.main.large-subjects-adversarial-sha256.slsa3.yml
Trigger: workflow_dispatch
Branch: main
Date: Tue Sep  5 18:35:39 UTC 2023
Tests are passing now. Closing this issue.


Iframe content on Ubuntu not always loading

Secret agent is not rendering the inner HTML of the iframe, the small example shows the issue.
Even this example in docs doesn't work https://secretagent.dev/docs/basic-interfaces/frame-environment#find-frame
Basicly innerhtml is empty for some reason
Node version: 14.17.1
Secret agent version: 1.5.1
OS: Ubuntu 20.04
(async () => {
    await agent.goto("https://www.w3schools.com/html/html_iframe.asp") // Alternatively https://patrickhlauke.github.io/recaptcha/
    await agent.waitForMillis(10000)
    await agent.close()
})();

@magicaltoast thanks for reporting. The link you shared has a documentation issue which I'll resolve (it should be getFrameEnvironment)
I'm seeing mixed results getting the frames to load (for what it's worth, they load in the real browser, but Replay is showing them blank some of the time). Appears to be an issue waiting for the frame to properly load.

(async function main() {
  await agent.goto('https://www.w3schools.com/html/html_iframe.asp');
  const { document } = agent.activeTab;
  await agent.waitForPaintingStable();

  const iframeElement = document.querySelector('iframe');

  const iframe = await agent.activeTab.getFrameEnvironment(iframeElement);

  await iframe.waitForLoad(LocationStatus.AllContentLoaded);

  agent.output.html = await iframe.document.body.outerHTML;
  const h4 = await iframe.document.querySelector('h4').textContent; // should be something like HTML demo: <iframe>
  agent.output.h4 = h4;
  await agent.close();
})();

Reopening per comment from @magicaltoast. Are you seeing issues using that same script you have above?

Picking up from your other comment. This is what I see in replay for the link you sent

Maybe it's time to boot up ubuntu.. that's on a mac

Could you send me the session database for one of these? https://secretagent.dev/docs/advanced/session

@blakebyrnes
I send you it on discord because Github doesn't support this file type.

After last patch - 1.5.3, everything seems to works ;) Thanks for quick fix

I think I might be running into something like this issue now on SA 1.5.14 on Ubuntu 20.04. I have a test script that when run on Windows finds some anchor tags inside iframes that I'm looking for, but on Ubuntu for some reason can't find any?
When I await anIFrameEnvironment.document.body.outerHTML to see what it's got, it isn't empty, there is some js in the iframes on both platforms, but for some reason the Windows one seems to be executing properly and generating the rest of the expected iframe html/anchor tag, but on Ubuntu for some reason either it isn't doing that, or is receiving truncated js from the website, not sure.

@A-Posthuman can you send me a session database where you're seeing this?

Just to follow up, I continue to see this difference in behavior between Windows and Ubuntu 20.04, where on Ubuntu the iframe content appears to not be fully rendered somehow - as if perhaps some js is not fully being run or something. Not sure, I still haven't been able to dig into the dbs or anything.
But I'd like to request you reopen this issue, or if you prefer I can start a new one more specific to this current behavior.

Ok, can you send me the session DBs if you've got them? We have a number of iframe tests that run on ubuntu, so it should not be every frame that can't load.

It might be helpful to see a windows vs Linux db that’s as similar as possible, but has one not loading the frame. Maybe we’ll be able to spot a difference

On Dec 8, 2021, at 12:10 AM, A-Posthuman @.***> wrote:

Just to follow up, I continue to see this difference in behavior between Windows and Ubuntu 20.04, where on Ubuntu the iframe content appears to not be fully rendered somehow - as if perhaps some js is not fully being run or something. Not sure, I still haven't been able to dig into the dbs or anything.
But I'd like to request you reopen this issue, or if you prefer I can start a new one more specific to this current behavior.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ok I'll provide those over on discord

@A-Posthuman did we decide this is loading, just likely some kind of blocking happening at the target site? Safe to re-close?

I'd say don't close it yet, because on further testing through my proxy I mentioned, I found that although my Windows SA 1.6.1 was being blocked, my real Firefox and Chrome were not. So there still seems to be some detection going on where the ad server seems to be detecting SA I think. IP addresses probably are playing some factor, perhaps in an overall detection score I'd guess, but it seems SA vs real browsers may also be at least somewhat detectable.

Determined with @A-Posthuman that this is likely being done on target site. Don't understand enough about why they're changing behavior on frames to know if its SecretAgent. Re-closing


A simple source code to open camera and acquire frames in form of numpy array

I just wanted to know a decent source code as an example to acquire images in while loop in form of numpy array of the depth camera and then process it accordingly and show them.
Thanks in Advance

HI. Check out this page. It should work for you. /Kazunari


Add session_details table to dfe-analytics

These changes include the session_details table as on of the standard tables that are produced by dfe-analytics.
It can be enabled for individual services using enableSessionTables: true.
The session_details code itself has been QA'd and currently exists for ITT mentors (dataform.session_details).

Also @Arjun-Kharbanda you need to update the package version at the top of index.js.


[Feature] option to render empty workspaces in the bar

I would like to have an option to enable empty workspaces to be displayed in the bar in front of a non-empty workspace.
Let's say I have an existing Firefox client on workspace 3.
Currently, only this one workspace is rendered in the bar.
What I want is to have the 2 empty workspaces rendered before it.
The reason for this is that I use shortcuts like ctrl + 1 to jump to workspaces. If the empty workspaces are rendered before a non-empty one, it would be easier to find the corresponding shortcut.

Would this be satisfied by upping the number of Total Workspaces in Configuration > Bar?
That number forces N number of workspaces to always show. So you can set it to 2 in this case, so it always shows the first 2.

Setting the workspaces to 9 would be a workaround for me and I could live with that.
But just to illustrate the behaviour a bit more, if I have a hpyrland client open on workspace 5, then workspace 4 is not rendered. So again, I could not see the empty workspace in between.
But as I said, I could live with setting the total number of workspaces to 9 as a workaround. The question for me was, does it make sense for you to implement this feature into the codebase?

Ahhh I think I understand what you mean. You want to show all workspaces prior to your higher workspace at all times?

Yessss, that is exactly the behaviour i want. What do you think about adding it?

Yeah, that should be doable and probably useful. I'll look into adding it.

I can also have a look at it and create a MR?

I can also have a look at it and create a MR?

Most welcomed to ❤

This can also be done by "assigning" workspaces to a monitor such as
workspace=1, monitor:DP-2
workspace=2, monitor:DP-2
workspace=3, monitor:DP-2
workspace=4, monitor:DP-2

in your hyprland config, this will make it so they always show up regardless if they have a window in them or not


Mutual TLS authentication

A recreation of #677 because I accidentally made a mess of my branch :(
With the Python requests module, it is possible to configure a client certificate to use for mutual TLS authentication, for example if an nginx instance in front of influxdb is performing the TLS termination and has a whitelist of allowed CNs.
This PR adds a new optional argument to the client constructor which passes through the path to such a client certificate to the requests session.

We would like to start using mutual TLS with our InfluxDB deployments so that we can evaluate InfluxDB for production use.
@aviau @sebito91 or @xginn8 please can someone review this PR?

If I got it correctly, for valid client-side certificate authentication you need a client certificate and its matching private key. They can be both in one file or in two separate files.
I would suggest adding this to the documentation of the new parameter like requests does it, that it is also possible to have a tuple with both file paths instead of one path only.
From the requests documentation

You can also specify a local cert to use as client side certificate, as a single file (containing the private key and the certificate) or as a tuple of both files’ paths

Requests documentation about client certificates

Sorry, been consumed lately but will get this reviewed this week!

I've updated the documentation to more explicitly state the supported values. I considered explicitly linking to the Requests documentation - but I'm not sure whether this would be preferred, especially as links can break over time.

Hello! Are there any updates on this PR?

@aviau I think this PR can be merged.

Sure, LGTM.


[WebToolsE2E][Aspire][Document]Some more updates are needed to "Deploy a .NET Aspire app using the Azure Developer CLI and GitHub Actions" instructions using VS with aspire

Describe the issue or suggestion
Issue description
In "Deploy a .NET Aspire app using the Azure Developer CLI and GitHub Actions" doc, we need to make some updates to the instructions for Preview 6.
Issue 1
For Create the .NET Aspire template section, document show "require Docker"

Actual: Show "requires a supported container runtime", so need update document.

Issue 2
For Initialize the template section, document show after do the step# 4 will pop up code as below and let select webfrontend

Actual: after do the step#4, don't let you select webfrontend, skip the step#5. so need update the document.

Issue 3
For Create the GitHub repository and pipeline section, document show after do the step#4, you will do step#5 "Select Create a new private GitHub repository to configure the git remote"

Actual: after do the step#4, let select "HTTPS" or "SSH"...., don't let select "Create a new private GitHub repository", and after do the many steps, then let you select "Create a new private GitHub repository". so before step#5 need add some steps, the document need update.

Associated WorkItem - 250489

@IEvangelist, about Issue#2, for section Initialize the template, document show step#1~step#7,
actual: the step is step#1, step#2, step#4, step5, step#3,  step#7, step#6 is redundant, could you help  check and update the document?

@IEvangelist About Issue#2, for section Initialize the template, the steps order need to update
Actual: The step order need update to step#1, step#2, step#4, step5, step#3, step#7, it doesn't need to select webfrontend of the step#6, skip the step#6. so need update the document Deploy .NET Aspire apps to Azure Container Apps - .NET Aspire | Microsoft Learn, could you please help to check and update the document?