fix: added top level property entityTypes

@zongqichen @swennemers @Fannon : As I've already informed you, if you run the service(in terminal, on path plugins/ORD/xmpl cds run or cds watch), the  generated ORD document(http://localhost:4004/open-resource-discovery/v1/documents/1) will have 2 errors when validated in the the API Metadata Validator. This PR should not be merged until we have proper values of level included into the ORD schema.

@zongqichen @swennemers @Fannon : As I've already informed you, if you run the service(in terminal, on path plugins/ORD/xmpl cds run or cds watch), the generated ORD document(http://localhost:4004/open-resource-discovery/v1/documents/1) will have 2 errors when validated in the the API Metadata Validator. This PR should not be merged until we have proper values of level included into the ORD schema.

This is the reason why I kept this PR to be Draft. Still, @Fannon && @zongqichen , it would be 🚀  if you could review it.  Thanks in advance!


Implement Silicon Labs EFR32 Wi-SUN support

Significant features and modifications:

Implementing EFR32 OSAL port
Refactoring build targets to standardise the build process and the output
Implementing Vendors/Silabs context
New config file interface for Sample Application to set the NMS and Agent parameters compile time
New portable TLV getter/setter interface to support multiple platforms
Specialised TLVs for EFR32 Wi-SUN platform: IPv6 address and some Vendor data
Removing select API usage in CoAP Client/Server, since it operates with only one socket descriptor
Implementing bi-directional integration solution: Csmp Agent lib into Silicon Labs SDK and Silicon Labs SDK into Cisco Csmp Agent repository to support both build systems
Updating readme files with EFR32 Wi-SUN content

Tested all targets on all possible platforms:

Ubuntu 22.04: linux, freertos, efr32_wisun
Windows10: efr32_wisun
MacOS: linux, freertos, efr32_wisun (for development only, it's not a release target platform)

Test scenario

Registration: The nodes can be registered by FND
Metrics: Nodes send metrics successfully
EFR32 Wi-SUN node can be pinged from FND
EFR32 Wi-SUN node't metrics can be updated from FND

@ismilak: I’ve reviewed some portion of the overall changes in this PR#22.
Changes look good under and the build/makefile udpates
osal/efr32_wisun
osal/freertos
osal/linux

Changes under /src are in review.
Changes under /sample, we see a lot of refactorization of the sample application code into multiple files. Per our last discussion we agreed to move only the TLV GET/PUT implementations to a separate file(now moved under tlvs/_tlvs.c), while keeping the rest in the original sample/CsmpAgentLib_sample.[ch]
sample_tlvs.[ch]
sample_util.[ch]
tlvs/efr32_wisun_tlvs.c
tlvs/freertos_tlvs.c
tlvs/linux_tlvs.c

Yep, let me explain the purposes of the source files.

sample/CsmpAgentLib_sample_tlvs.h:
It includes the common function declarations, like osal.h. These function implementations are platform specifics. They are implemented in sample/tlvs/xxxxx_tlvs.c files. It includes the function declaration of csmptlvs_get() and csmptlvs_post() handlers

sample/CsmpAgentLib_sample_tlvs.c:
This source includes only 2 function implementation: csmptlvs_get() and csmptlvs_post(). These functions are the common handlers, they are registered as callbacks in the handler instance.

sample/CsmpAgentLib_sample_util.[ch]:
These sources should include the utility functions, they can be used in the entire namespace of the sample application (sample/ dir). I note that, there is only one function yet (str2addr()) that is used only in sample/CsmpAgentLib_sample.c

The files are created to separate APIs and function implementations based on their functionality.
I think what we can change to reduce the count of the files in sample/ directory:

Moving sample/CsmpAgentLib_sample_tlvs.c content back to sample/CsmpAgentLib_sample.c and moving the related declarations from sample/CsmpAgentLib_sample_tlvs.h into that file.
Moving sample/CsmpAgentLib_sample_util.[ch] into sample/CsmpAgentLib_sample.c

I recommend to keep as it is to have this kind of architecture for future improvements and to reduce the length of sample source files.

@ismilak: I’ve reviewed some portion of the overall changes in this PR#22.
Changes look good under and the build/makefile udpates
osal/efr32_wisun
osal/freertos
osal/linux

Changes under /src are in review.
Changes under /sample, we see a lot of refactorization of the sample application code into multiple files. Per our last discussion we agreed to move only the TLV GET/PUT implementations to a separate file(now moved under tlvs/_tlvs.c), while keeping the rest in the original sample/CsmpAgentLib_sample.[ch]
sample_tlvs.[ch]
sample_util.[ch]
tlvs/efr32_wisun_tlvs.c
tlvs/freertos_tlvs.c
tlvs/linux_tlvs.c

Yep, let me explain the purposes of the source files.
* _sample/CsmpAgentLib_sample_tlvs.h_:
  It includes the common function declarations, like osal.h. These function implementations are platform specifics. They are implemented in _sample/tlvs/xxxxx_tlvs.c_ files. It includes the function declaration of _csmptlvs_get()_ and _csmptlvs_post()_ handlers too.

* _sample/CsmpAgentLib_sample_tlvs.c_:
  This source includes only 2 function implementation: _csmptlvs_get()_ and _csmptlvs_post()_. These functions are the common handlers, they are registered as callbacks in the handler instance.

* _sample/CsmpAgentLib_sample_util.[ch]_:
  These sources should include the utility functions, they can be used in the entire namespace of the sample application (sample/ dir). I note that, there is only one function yet (_str2addr()_) that is used only in _sample/CsmpAgentLib_sample.c_

The files are created to separate APIs and function implementations based on their functionality. I think what we can change to reduce the count of the files in sample/ directory:
* Moving _sample/CsmpAgentLib_sample_tlvs.c_ content back to _sample/CsmpAgentLib_sample.c_ and moving the related declarations from _sample/CsmpAgentLib_sample_tlvs.h_ into that file.

* Moving _sample/CsmpAgentLib_sample_util.[ch]_ into _sample/CsmpAgentLib_sample.c_

I recommend to keep as it is to have this kind of architecture for future improvements and to reduce the length of sample source files.

@ismilak:
Inline to our meeting discussion, the below directory structure should be good with a view to keep the structure simple...
Please note:

Silabs is moved under Vendors, making provision for other vendors directories as well under Vendors.
CsmpAgentLib_sample.c : Contents of CsmpAgentLib_sample_util.c to be moved here
CsmpAgentLib_sample.h : Contents of CsmpAgentLib_sample_util.h and CsmpAgentLib_sample_config.h to be moved here

REPO_ROOT
├── Vendors
│   └── Silabs
│       ├── Readme.md
│       └── resources
├── osal
└── sample
    ├── CsmpAgentLib_sample.c
    ├── CsmpAgentLib_sample.h
    ├── CsmpAgentLib_sample_tlvs.c
    ├── CsmpAgentLib_sample_tlvs.h
    .
    └── tlvs
        ├── efr32_wisun_tlvs.c
        ├── freertos_tlvs.c
        └── linux_tlvs.c

@ismilak: I’ve reviewed some portion of the overall changes in this PR#22.
Changes look good under and the build/makefile udpates
osal/efr32_wisun
osal/freertos
osal/linux

Changes under /src are in review.
Changes under /sample, we see a lot of refactorization of the sample application code into multiple files. Per our last discussion we agreed to move only the TLV GET/PUT implementations to a separate file(now moved under tlvs/_tlvs.c), while keeping the rest in the original sample/CsmpAgentLib_sample.[ch]
sample_tlvs.[ch]
sample_util.[ch]
tlvs/efr32_wisun_tlvs.c
tlvs/freertos_tlvs.c
tlvs/linux_tlvs.c

Yep, let me explain the purposes of the source files.
* _sample/CsmpAgentLib_sample_tlvs.h_:
  It includes the common function declarations, like osal.h. These function implementations are platform specifics. They are implemented in _sample/tlvs/xxxxx_tlvs.c_ files. It includes the function declaration of _csmptlvs_get()_ and _csmptlvs_post()_ handlers too.

* _sample/CsmpAgentLib_sample_tlvs.c_:
  This source includes only 2 function implementation: _csmptlvs_get()_ and _csmptlvs_post()_. These functions are the common handlers, they are registered as callbacks in the handler instance.

* _sample/CsmpAgentLib_sample_util.[ch]_:
  These sources should include the utility functions, they can be used in the entire namespace of the sample application (sample/ dir). I note that, there is only one function yet (_str2addr()_) that is used only in _sample/CsmpAgentLib_sample.c_

The files are created to separate APIs and function implementations based on their functionality. I think what we can change to reduce the count of the files in sample/ directory:
* Moving _sample/CsmpAgentLib_sample_tlvs.c_ content back to _sample/CsmpAgentLib_sample.c_ and moving the related declarations from _sample/CsmpAgentLib_sample_tlvs.h_ into that file.

* Moving _sample/CsmpAgentLib_sample_util.[ch]_ into _sample/CsmpAgentLib_sample.c_

I recommend to keep as it is to have this kind of architecture for future improvements and to reduce the length of sample source files.

@ismilak: Inline to our meeting discussion, the below directory structure should be good with a view to keep the structure simple... Please note:

Silabs is moved under Vendors, making provision for other vendors directories as well under Vendors.
CsmpAgentLib_sample.c : Contents of CsmpAgentLib_sample_util.c to be moved here
CsmpAgentLib_sample.h : Contents of CsmpAgentLib_sample_util.h and CsmpAgentLib_sample_config.h to be moved here

REPO_ROOT
├── Vendors
│   └── Silabs
│       ├── Readme.md
│       └── resources
├── osal
└── sample
    ├── CsmpAgentLib_sample.c
    ├── CsmpAgentLib_sample.h
    ├── CsmpAgentLib_sample_tlvs.c
    ├── CsmpAgentLib_sample_tlvs.h
    .
    └── tlvs
        ├── efr32_wisun_tlvs.c
        ├── freertos_tlvs.c
        └── linux_tlvs.c

Done. Please verify the changes. Thank you!


It is very inconvenient when ASP.NET project is opened and the chat does not understand the context (if you do not specify) and gives answers in Python.
How can we solve this problem? Like this for example:

This is a VSCode extension ("Project Hierarchy Explorer") that generates the project structure: folders and scripts with extensions. You can give such information to CodeGeeX when the VSCode launches or for this purpose you can make a button on the chat panel, because projects are big.
Such information will help the CodeGeeX to give more accurate answers. It may even indicate in which script the answer should be used.
You can give the CodeGeeX more detailed input data and for this you need to make an additional button on the chat panel. Instead of giving only the structure of the project, the CodeGeeX extension can parse each script and copy the name of the classes and methods from there, for more accurate answers of course.
You can also add a 'Focus' function. What I mean; Often, in order for the CodeGeeX to give the exact answer, you have to give it code fragments from different scripts. In order not to copy the code, you can tell the CodeGeeX to focus on certain scripts. This 'Focusing', of course, technically will mean copying (under the hood) scripts in the chat. After the 'Focusing', the programmer's question follows and, I hope, a more accurate answer from AI.
Of course, technically this can be implemented in different ways. I propose this option:

press the button, a window appears, select scripts (including a whole folder with scripts), close the window and ask a question. AI is focused on the selected scripts but does not lose the main context ("Project Hierarchy").
P.S. It may be better if, when creating a new project, the program will track all the scripts (according to the above described principle) and the data will be stored in file that is visible to the programmer. why is it needed? when I download a project from GitHub so that I don't have to parse all the scripts again. This feature can be made optional.
P.S.2: in addition, you can give the CodeGeeX knowledge about errors in real time. You can do it like Error Lens does it.  When an error occurs the program automatically focuses on those scripts and code lines and when I ask to correct errors, CodeGeeXdoes not ask unnecessary questions, it already knows where these errors are and directly gives the advice How to fix these errors

P.S.2: in addition, you can give the CodeGeeX knowledge about errors in real time. You can do it like Error Lens does it.  When an error occurs the program automatically focuses on those scripts and code lines and when I ask to correct errors, CodeGeeXdoes not ask unnecessary questions, it already knows where these errors are and directly gives the advice How to fix these errors

Great suggestions! We're working on this function. Just a quick test on "AskCodeGeeX" by providing the project hierarchy:

I would expect it to perform better if we give more context.

Please implement GPT Commit feature. I suggest the following behavior: click on the button, a window pops up, click on the window, the text of the commit is copied to the clipboard and then you can paste it into the Git input:

P.S. it shouldn't ask me to stage scripts before generating the commit message.

You've probably already thought about it, but I'll say it anyway; To speed up project indexing you should create a global ‘.gitignore’ file (under the hood of course) for ‘CodeGeeX’:


fix running tests locally

Scope & Purpose
Running scripts/unittest <testsuite> was broken since the last commit to scripts/unittest. Fix it.

[x] :hankey: Bugfix
[ ] :pizza: New feature
[ ] :fire: Performance improvement
[ ] :hammer: Refactoring/simplification

Checklist

[ ] Tests

[ ] Regression tests
[ ] C++ Unit tests
[ ] integration tests
[ ] resilience tests

[ ] :book: CHANGELOG entry made
[ ] :books: documentation written (release notes, API changes, ...)
[ ] Backports

[x] Backport for 3.10: https://github.com/arangodb/arangodb/pull/18493
[x] Backport for 3.9: this PR
[ ] Backport for 3.8: -

Related Information

[ ] Docs PR:
[ ] Enterprise PR:
[ ] GitHub issue / Jira ticket:
[ ] Design document:

Test failure is known and unrelated.


Difficulties of re-entering wasm in presence of stack switching

This issue is intended to document, discuss and track some difficulties that occur when performing host calls in the presence of stack switching that in turn re-enter wasm.
For example, consider the following logical call stack (here, "logical" means that this is not a single, contingent stack):
$f -resume-> $g -call-> host_function -call-> $h

where $f, $g, and $h are wasm functions. Here, $g is not executing on the main stack, but inside a continuation, when performing the host call. The latter then re-enters wasm by calling $h.
There are multiple issues that would need to be resolved in order for this to work correctly:

Most likely, we want to consider host calls to act as barriers for the purposes of stack switching, meaning that a suspend in $h cannot get handled in $f or $g. This means that if any of these functions run in instances of the same Store, we need to set aside the continuation chain when entering h and restore it once it returns.

The first point illustrates that when starting execution of $h, we would want to indicate that it is not subject to any handlers. Currently, this would be achieved by setting its Store's stack chain to MainStack (independently from whether it actually shares a Store with the other involved wasm functions or not).
However, $h is not actually running on the main stack, since it is running on same FiberStack as $g. For the purposes of correctly handling stack limits, we would need some way to indicate that $h is running inside a FiberStack, but without actually being subject to any other handlers. Of course, we may also eventually decide that all host calls switch to the actual main stack for execution.

I think that all of these issues can be resolved, but that these solutions possibly interact with future design decisions. Therefore, I suggest that we simply disallow this for now by enforcing the current rule in the implementation: Re-entering wasm from a host call is only permitted when not already running inside a continuation. Or in other words, the host call from which we want to re-enter wasm must have been running on the main stack. We can then ease these restrictions at a later point.

As we discussed the yesterday on the call, I think for now it is sufficient if we assume all host calls are leaves in the call graph, and if that assumption is violated then we hard fail. Later, we can look into relaxing this assumption.

I'm afraid that restriction is too strong because it would break existing (i.e., non-wasmfx) test cases in wasmtime.
The restriction I was proposing is slightly weaker: We require that host calls are leaf calls (in the sense of not re-entering wasm) if we were running inside a continuation when performing the host call.


Random bits in Header component

Pull request name

Pre-Submission Checklist

[ ] Your pull request targets the master branch.
[ ] Branch starts with either fix/ or feature/ (e.g. fix/signin-issue)
[ ] All new and existing tests pass.

Type of Change

[ ] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist:

[ ] Tested changes locally.
[ ] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

Butter is not used in the component
Use current target to blur input, avoid searching the DOM for the element.

@amilajack for some reason it's failing the e2e test because the context is undefined (not binding for some reason). It works fine in dev mode though, wonder if there's some difference in the babel config (wild guess honestly)

They seem to be working now. Maybe it was the onKeyPress changes that fixed it?


[Bug] Oracle IDCS not working over OpenID Connect protocol

Which version of Microsoft.IdentityModel are you using?
Note that to get help, you need to run the latest version.

Where is the issue?

[ ] M.IM.JsonWebTokens
[ ] M.IM.KeyVaultExtensions
[ ] M.IM.Logging
[ ] M.IM.ManagedKeyVaultSecurityKey
[ ] M.IM.Protocols
[x] M.IM.Protocols.OpenIdConnect
[ ] M.IM.Protocols.SignedHttpRequest
[ ] M.IM.Protocols.WsFederation
[ ] M.IM.TestExtensions
[ ] M.IM.Tokens
[ ] M.IM.Tokens.Saml
[ ] M.IM.Validators
[ ] M.IM.Xml
[ ] S.IM.Tokens.Jwt
Other (please describe)

Is this a new or an existing app?
App in production using v5.3.0 but repro also in 6.20.0
-->
Repro
var metadataAddr
    = "https://idcs-<PII>.identity.oraclecloud.com/.well-known/idcs-configuration";

var openidConfiguration = await OpenIdConnectConfigurationRetriever.GetAsync(
    metadataAddr,
    CancellationToken.None);

var authEndpoint = openidConfiguration.AuthorizationEndpoint;
if(authEndpoint == null)
{
    throw new Exception("missing auth endpoint!");
}

Expected behavior
authorization_endpoint and rest of the parameters should be read from discovery endpoint even if they are subnodes of the json structure that has beed returned
Actual behavior
values that are in the response json like authorization_endpoint are returned even if they are deeper in the json structure
Possible solution
Pare json in order to look for expected values
Additional context / logs / screenshots / links to code
Oracle Cloud returns single json discovery response with OpenIdConnect values in a subnode (openid-configuration/authorization_endpoint). Example:
{
"access-configuration": {
    "http_authentication_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/admin/v1/HTTPAuthenticator",
    "encryption_keys_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/admin/v1/EncryptionKeys",
    "password_authenticator_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/admin/v1/PasswordAuthenticator",
    "asserter_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/admin/v1/Asserter",
    "session_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/session/v1/Sessions",
    "session_validate_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/session/v1/SessionValidate",
    "session_refresh_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/session/v1/SessionRefresh",
    "secure_http_authentication_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/admin/v1/HTTPAuthenticator",
    "secure_encryption_keys_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/admin/v1/EncryptionKeys",
    "secure_password_authenticator_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/admin/v1/PasswordAuthenticator",
    "secure_asserter_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/admin/v1/Asserter",
    "secure_session_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/session/v1/Sessions",
    "secure_session_validate_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/session/v1/SessionValidate",
    "secure_session_refresh_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/session/v1/SessionRefresh"
},
**"openid-configuration": {**
    "issuer": "https://identity.oraclecloud.com/",
    **"authorization_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/oauth2/v1/authorize",**
    "token_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/oauth2/v1/token",
    "userinfo_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/oauth2/v1/userinfo",
    "revocation_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/oauth2/v1/revoke",
    "introspection_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/oauth2/v1/introspect",
    "end_session_endpoint": "https://idcs-<PII>.identity.oraclecloud.com/oauth2/v1/userlogout",
    "secure_authorization_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/oauth2/v1/authorize",
    "secure_token_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/oauth2/v1/token",
    "secure_userinfo_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/oauth2/v1/userinfo",
    "secure_revocation_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/oauth2/v1/revoke",
    "secure_introspection_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/oauth2/v1/introspect",
    "secure_end_session_endpoint": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/oauth2/v1/userlogout",
    "jwks_uri": "https://idcs-<PII>.identity.oraclecloud.com/admin/v1/SigningCert/jwk",
    "secure_jwks_uri": "https://idcs-<PII>.us-phoenix-idcs-2.secure.identity.oraclecloud.com/admin/v1/SigningCert/jwk",
    "scopes_supported": [
        "openid",
        "profile",
        "offline_access",
        "email",
        "address",
        "phone",
        "groups",
        "get_groups",
        "approles",
        "get_approles"
    ],

....
}

@mawasile the OpenIdConnectRetriever expects to see the metadata as per this specification: https://openid.net/specs/openid-connect-discovery-1_0.html
Is Oracle following this format?

@brentschmaltz
During the investigation with the customer, we found out that Oracle IDCS acctually has two endpoints.
One not according to specification => https://idcs-.identity.oraclecloud.com/.well-known/idcs-configuration
and second one that is correct =>  https://idcs-.identity.oraclecloud.com/.well-known/openid-configuration
Feel free to close the issue as the second discovery endpoint can be used by the user.

@mawasile closing as Oracle endpoint not to spec.


Docs.MS Release Updates for azure_template

Update docs metadata and targeting for release of azure_template

Docs Build status updates of commit 84137b9:
:clock10: Full build: the average full build time is 161 min(s) 45 sec(s), this is based on the last 491 build(s) for this repository.

Docs Build status updates of commit 84137b9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/template-readme.md
:warning:Warning
View (azure-python)
Details

docs-ref-autogen/msal/msal.oauth2cli.http.HttpClient.yml
:warning:Warning
View (azure-python)
Details

docs-ref-autogen/msal/msal.application.PublicClientApplication.yml
:warning:Warning
View (azure-python)
Details

docs-ref-autogen/msal/msal.application.ClientApplication.yml
:warning:Warning
View (azure-python)
Details

docs-ref-autogen/msal/msal.oauth2cli.oidc.Client.yml
:warning:Warning
View (azure-python)
Details

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.task_all.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.new_uuid.yml
:warning:Warning
View (azure-python-preview)
Details

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.continue_as_new.yml
:warning:Warning
View (azure-python-preview)
Details

ci-configs/packages-latest.json
:white_check_mark:Succeeded

docs-ref-services/template-readme.md

Line 13: [Warning-h1-not-first] Markdown content is not allowed before {0}.
Line 25: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 29: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 33: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 37: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 41: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.
Line 45: [Warning-multiple-h1s] Multiple H1s({0}) are not allowed. You can only have one top-level heading.

docs-ref-autogen/msal/msal.oauth2cli.http.HttpClient.yml

Line 3: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-autogen/msal/msal.oauth2cli.http.Response.html#).
Line 3: [Warning-InvalidFileLink] Invalid file link:(~/docs-ref-autogen/msal/msal.oauth2cli.http.Response.html#).

docs-ref-autogen/msal/msal.application.PublicClientApplication.yml

[Warning-UidNotFound] 1 invalid cross reference(s) "<xref:msal.application.initiate_device_flow>".

docs-ref-autogen/msal/msal.application.ClientApplication.yml

[Warning-UidNotFound] 4 invalid cross reference(s) "<xref:msal.application.acquire_token_silent>", "<xref:msal.application.acquire_token_silent_with_error>", "<xref:msal.application.get_authorization_request_url>", "<xref:msal.application.get_accounts>".

docs-ref-autogen/msal/msal.oauth2cli.oidc.Client.yml

[Warning-UidNotFound] 2 invalid cross reference(s) "<xref:oauth2.Client.build_auth_request_uri>", "<xref:oauth2.Client.obtain_token_by_authorization_code>".

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.task_all.yml

[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.task_all) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml.

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.new_uuid.yml

[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.new_uuid) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml.

preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.continue_as_new.yml

[Warning-DuplicateUids] Uid(azure.durable_functions.tasks.continue_as_new) has already been defined in preview/docs-ref-autogen/azure-functions-durable/azure.durable_functions.tasks.yml.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Allow MQTT publish from plugin code

@CarstenGrohmann Here is the change that you requested

Thank you for changing the API.


Enhancement - Add support for content checking and tint color for compose icon

@Unlimity
I ran the command
git ls-files -z | while IFS= read -rd '' f; do tail -c1 < "$f" | read -r _ || echo >> "$f"; done
But too many files have changed. Should I start it now??

No need to do this for the whole repo, just for the new files you add in your PR

@Unlimity
Done, please check that everything is fine


selu Activation not found

Please make sure that the boxes below are checked before you submit your issue. If your issue is an implementation question, please ask your question on StackOverflow or join the Keras Slack channel and ask there instead of filing a GitHub issue.
Thank you!

[X] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps

[X] If running on TensorFlow, check that you are up-to-date with the latest version. The installation instructions can be found here.

[ ] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

[ ] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

I tried using the Activation('selu') call and it gives me an error message:
ValueError: Unknown activation function:selu
Activation('relu') and Activation('elu') works just fine.
My Keras v2.0.5 running on Tensorflow v1.2.0
What am I doing wrong, or what am I missing?

The following code runs for me in TensorFlow and Theano and Keras (2.0.5):
import keras
from keras.models import Sequential
from keras.layers import InputLayer, Dense, Activation

model = Sequential()
model.add(InputLayer((32,32)))
model.add(Activation('selu'))
model.add(Dense(16))
model.add(Activation('elu'))
model.add(Dense(16))
model.add(Activation('relu'))
model.add(Dense(16))

model.compile(loss='categorical_crossentropy',
              optimizer=keras.optimizers.Adadelta(),
              metrics=['accuracy'])

Can you share a minimal and complete code example?

This is my code snippet:
`
from keras.models import Sequential
from keras.layers import Input, BatchNormalization, Dense, Reshape, Lambda, Dropout
from keras.layers import Merge, Activation, noise
model = Sequential([
# input layer
Dense(200, input_shape=(54,), init='he_uniform'),
Activation('selu'),
BatchNormalization(),
noise.GaussianDropout(0.4),
# hidden layer #1
Dense(100, init='he_uniform'),
Activation('selu'),
BatchNormalization(),
noise.GaussianDropout(0.2),

# hidden layer #2
Dense(25, init='he_uniform'),
Activation('selu'),
BatchNormalization(),
noise.GaussianDropout(0.2),

# output layer
Dense(1, init='he_uniform')

])`
I found what my problem was, but I don't know what caused it.
Somehow, my python setup.py install procedure did not copy over the git sourced activations.py into my envs folder. I compared the two files and sure enough, the selu function was not there (I was sure my envs was activated when I did the install).
Anyway, I just spliced in the selu function into the activations,py and now it's working as expected.
Thanks for your quick reply!

great! Could you please close this issue then?

In my case I upgraded keras to 2.0.5 and tensorflow to 1.2.1, but activation selu was not found and AlphaDropout neither. But then everything just worked after I restarted my computer!


[core] platform agnostic executor via collective_rpc

@tlrmchlsmth thanks for the review! I will fix these comments later. Do you have any concerns about this design of platform-agnostic executor?

@youkaichao no high level concerns. Happy to see so much code deleted!

For people reviewing this large PR (most change is about deleting and merging old code), the high-level idea can help you understand the PR better:
The core idea of this PR, is a collective_rpc interface. When we create the worker process, we will directly assign a rank to this worker. After setting up all workers, the executor always call collective_rpc on all workers.
If an rpc method requires different arguments for different ranks, the executor will pass in all arguments as a list, and each rank selects its own argument. Such an rpc call will have a special handling at the WorkerWrapperBase level.
In most cases, all ranks require the same arguments, and the executor just broadcasts the arguments to all ranks.

If an rpc method requires different arguments for different ranks, the executor will pass in all arguments as a list, and each rank selects its own argument. Such an rpc call will have a special handling at the WorkerWrapperBase level.

Overall looks good. Just to confirm, the special handling is not yet in WorkerWrapperBase? I don't seem to find it. Also have a question, if the arguments are large, would it be an extra overhead to send all arguments of all ranks to each worker?

I got an error using V1 with tp=2 when there were multiple requests at the same time.
ERROR 12-31 11:09:06 core.py:200] EngineCore hit an exception: Traceback (most recent call last):
ERROR 12-31 11:09:06 core.py:200]   File "/data/lijinghui/uv_projects/.venv/lib/python3.12/site-packages/vllm/v1/engine/core.py", line 193, in run_engine_core
ERROR 12-31 11:09:06 core.py:200]     engine_core.run_busy_loop()
ERROR 12-31 11:09:06 core.py:200]   File "/data/lijinghui/uv_projects/.venv/lib/python3.12/site-packages/vllm/v1/engine/core.py", line 232, in run_busy_loop
ERROR 12-31 11:09:06 core.py:200]     outputs = self.step()
ERROR 12-31 11:09:06 core.py:200]               ^^^^^^^^^^^
ERROR 12-31 11:09:06 core.py:200]   File "/data/lijinghui/uv_projects/.venv/lib/python3.12/site-packages/vllm/v1/engine/core.py", line 124, in step
ERROR 12-31 11:09:06 core.py:200]     output = self.model_executor.execute_model(scheduler_output)
ERROR 12-31 11:09:06 core.py:200]              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 12-31 11:09:06 core.py:200]   File "/data/lijinghui/uv_projects/.venv/lib/python3.12/site-packages/vllm/v1/executor/multiproc_executor.py", line 152, in execute_model
ERROR 12-31 11:09:06 core.py:200]     model_output = self.collective_rpc("execute_model",
ERROR 12-31 11:09:06 core.py:200]                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ERROR 12-31 11:09:06 core.py:200]   File "/data/lijinghui/uv_projects/.venv/lib/python3.12/site-packages/vllm/v1/executor/multiproc_executor.py", line 146, in collective_rpc
ERROR 12-31 11:09:06 core.py:200]     raise e
ERROR 12-31 11:09:06 core.py:200]   File "/data/lijinghui/uv_projects/.venv/lib/python3.12/site-packages/vllm/v1/executor/multiproc_executor.py", line 135, in collective_rpc
ERROR 12-31 11:09:06 core.py:200]     raise result
ERROR 12-31 11:09:06 core.py:200] AssertionError
ERROR 12-31 11:09:06 core.py:200]

Is it related to this pr?


python311Packages.hglib: remove

duplicate with python-hglib and attribute name does not match upstream
Description of changes

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, as applicable:

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

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.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 260849 run on x86_64-linux 1

6 packages built:

powerline (python310Packages.powerline)
powerline.dist (python310Packages.powerline.dist)
python311Packages.powerline
python311Packages.powerline.dist
sourcehut.hgsrht
sourcehut.hgsrht.dist

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

6 packages built:

powerline (python310Packages.powerline)
powerline.dist (python310Packages.powerline.dist)
python311Packages.powerline
python311Packages.powerline.dist
sourcehut.hgsrht
sourcehut.hgsrht.dist


Unexpected space between head and main

top margin for .articleheader-container likely needs to be set to 0


Release for .net 5 framework

Hi,  is it possible to release this for .net 5?

Yes soon

@zombiehunter1  here is the package you can download
https://www.nuget.org/packages/Serilog.Sinks.WinForms.Core/1.0.0

@zombiehunter1 here is the package you can download. dnt forget to give it a star :) https://www.nuget.org/packages/Serilog.Sinks.WinForms.Core/1.0.0

It doesn't work.

https://github.com/umairsyed613/Serilog.Sinks.WinForms/tree/main/src/Sample/TestApplicationNet6
check this sample app

https://github.com/umairsyed613/Serilog.Sinks.WinForms/tree/main/src/Sample/TestApplicationNet6
check this sample app

Sorry, when I said it doesn't work the problem is about when I try to install it via nuget package it gives server error. It is like nobody can not download this package.

@muratcanoguzhan  i have created a new package and published it, i will test it and will update you

Download this https://www.nuget.org/packages/Serilog.Sinks.WinForms.Core/1.0.1
hopefully it will work :)

Download this https://www.nuget.org/packages/Serilog.Sinks.WinForms.Core/1.0.1 hopefully it will work :)

After downloading the 1.0.2 version it works. Thank you.


Toolbox wont work!

Toolbox wont work on new Pathfinder 2e Version[<IP_ADDRESS>56], doesnt show modules options and not showing Loot, macros none of 3 are working.

Browser: Google Chrome [91.0.4472.124]
FoundryVTT [0.8.8]
PF2E Toolbox [1.7.8]
Only Find The Culprit

Hi @viniciusaraujo093 - an error with my CI caused the script to fail to be packaged with the zip. It should be working now if you update. Sorry for the inconvenience!


Check label matching against all JWT policies in the root namespace

In the current implementation, we assume JWT policy in root namespace does not have selector (and also is singleton - only one with name default should be considered); webhook validation should reject configs in the root namespace that have selector. However, the current validation framework doesn't have root namespace information, thus it cannot enforce such rule (yet).
This PR drops that assumption, allow any request authentication policy in the root config can be applied (if the selector match)

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

Test name
Commit
Details
Rerun command

unit-tests_istio
5ff9eb9d6a2f61c7fada1f753883d459ffed8c65
link
/test unit-tests_istio

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 unit-tests_istio


"rebar3 shell" freezes the input to console on Cygwin in Windows 7

When I run ./rebar3 shell, my application starts perfectly but I cannot use the console (prints messages but no input).
To exit I need to Ctrl+C but the "erl" process kept running.

A similar problem happens when running "escript rebar3 shell" on Windows CMD. The only difference is that when I ctrl-C, the "erl" process is killed.

i think 4238f2a3 should fix this but i don't have windows at hand to confirm

Unfortunately no. I confirm this issue in beta-1.

Does this still happen? There's been some improvement to the shell command since then.

Yes, still happening. I just compiled last commit from source:
/home/cpaula/projects/dcca-server-OTP [rebar3 *] [cpaula@NTSP052387] [10:42]
> ./rebar3 -v
rebar 3.0.0-beta.4+build.3217.ref72855b2 on Erlang/OTP 18 Erts 7.0

Can you tell me what the result is for any regular shell run from the same environment as rebar3 shell when calling process_info(whereis(user), current_function) ?
If it's {user, server_loop,2} then the problem is that windows has a terminal with insufficient drivers and reverts to the old-style shell, which would end up related to https://github.com/rebar/rebar3/issues/946
I can try figuring out how to fix that.

It's exactly that:
/home/cpaula/projects/dcca-client-OTP [master] [cpaula@NTSP052387] [11:33]
> erl
Eshell V7.0  (abort with ^G)
1> process_info(whereis(user), current_function).
{current_function,{user,server_loop,2}}

Alright, that gives me a way to resolve it. I'll try to get to that, shouldn't be too hard

This should now be fixed. Reopen if required.

The fix is confirmed on Cygwin and Windows CMD. Thanks @ferd.


Reskin smart home devices site

On branch https://github.com/perminder-klair/gatsbyjs-ecommerce/tree/site/smart-home-devices

For design ideas
https://www.awwwards.com/websites/e-commerce/
https://colorlib.com/wp/template/minishop/
https://colorlib.com/wp/template/sublime/
https://colorlib.com/wp/template/fashiop/
https://colorlib.com/wp/template/theplaza/
https://colorlib.com/wp/template/karma/
https://colorlib.com/wp/template/modist/
https://colorlib.com/wp/template/divisima/
https://colorlib.com/wp/template/aroma/
https://colorlib.com/wp/template/selling/
https://colorlib.com/wp/template/shopmax/

Reskin completed.


Implement command to output the issues

+-------+----------+--------------------------------+
| Issue | Severity | Link                           |
+-------+----------+--------------------------------+
| XSS   | High     | https://nexploit.app/dsfsdfsfd |
+-------+----------+--------------------------------+
| SQLi  | High     | https://nexploit.app/dsfsdfsfd |
+-------+----------+--------------------------------+
| Cors  | Low      | https://nexploit.app/dsfsdfsfd |
+-------+----------+--------------------------------+

Should be trivial, I can work on it.

@derevnjuk I think this can be closed no?

I suppose so


use a proper logging library

I would refrain to use any print instruction in any script.
I propose to use the loguru library for logging. This library is close to the standard library, but implements some useful gadgets (color in logging for example) that is not always easy to setup correctly.
I then would propose to add multiple handlers, such as a stream handler, a log file handler and maybe to combine it with notifier, to get a message when a problem occur.
see: notifier

logging and exception handling (Try ... except ) are both not yet implemented,and printing is just for the moment and for debugging easily, loguru library looks really nice ( the standard logging module can be a pain)


Are there any NLU datasets (NLU for task-oriented dialogue systems) included?

 But I just need to confirm that no NLU benchmarks, e.g. ATIS, SNIPS, NLU++ are included in this repo, right?

Hi!
We don't include any of those 3 datasets in this repo. From a glance, it seems like 2 of them include speech components if I'm looking at the right papers, in which case those would be out-of-scope for this repo, and at least one seems to be a sequence tagging dataset? I'm not aware of any good translations of sequence-tagging datasets into a prompted format that are standard, but if you are aware of such a technique in the literature, feel free to contribute these benchmarks!
Hope this helps!


Can't find local printers

When I connect to the remote pc I can't find my local printers

Any solution?

I solved that with hamachi printers


Adjust to Null Safety

I'm not able to compile using the --enable-experiment = non-nullable option in the new version of Dart;
Adjust the code for null safety compilation.

Since null security is stable, we will update.
Maybe I will create a development branch with null-safety, but for now the flutter/dart team recommends not using it in packages - yet.


Add support for Swift "Package.pins".

Fixes #513
Changes proposed:

[x] Add
[ ] Prepare
[ ] Delete
[ ] Fix

Things I've done:

[x] My pull request fixes an issue, I referenced the issue.

Where's the icon?

It extends the use of Swift icon to the filename.

Ah, I thought  we'll create a new icon for it.

From @rbukovansky

There is new file created by Swift Package Manager called Package.pins. Please add standard Swift icon for this file. Thanks.

Okey.


VBA error #91 (Object variable or With block variable not set) at clsErrorBars.UseChart

This issue was submitted by the add-in's exception handler.

Exception:
XLToolbox.Vba.VbaException: VBA error #91 (Object variable or With block variable not set) at clsErrorBars.UseChart

Message: VBA error #91 (Object variable or With block variable not set) at clsErrorBars.UseChart
Environment

Parameter
Value

Version
7.2.6

OS
Microsoft Windows NT 10.0.15014.0, 64-bit

Excel
365 (16.0.7668), 64-bit

CLR
4.0.30319.42000, 64-bit

VSTO runtime
10.0.60301

ClickOnce
False

Bovender
<IP_ADDRESS>

FreeImage
3.16.0

this was certainly caused by user error.  I was just clicking around to see what different features did, but of course I didn't want to see an exception

What did you do to produce this error? When I attempt to use the error charts function without selecting a chart first, I get a warning message, but not an error.


lib.trimWith: Minor doc improvements

Description of changes
Follow-up to https://github.com/NixOS/nixpkgs/pull/315411. Just something minor I spotted. I think it's best to make follow-up PRs instead of bikeshedding :)
Ping @MattSturgeon

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

Haha thanks, I sometimes feel bad if there's too many review cycles with just super minor comments :laughing:


ocamlPackages.happy-eyeballs: 0.5.0 -> 1.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/roburio/happy-eyeballs/releases.
meta.description for ocamlPackages.happy-eyeballs is: Connecting to a remote host via IP version 4 or 6
meta.homepage for ocamlPackages.happy-eyeballs is: https://github.com/roburio/happy-eyeballs
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.6.0 with grep in /nix/store/c24xrzsdzqqpmdnvflpd6yk5fqphnn7j-ocaml5.1.1-happy-eyeballs-0.6.0
found 0.6.0 in filename of file in /nix/store/c24xrzsdzqqpmdnvflpd6yk5fqphnn7j-ocaml5.1.1-happy-eyeballs-0.6.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/c24xrzsdzqqpmdnvflpd6yk5fqphnn7j-ocaml5.1.1-happy-eyeballs-0.6.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.happy-eyeballs https://github.com/r-ryantm/nixpkgs/archive/284424427bbd6b1d788c217440bf0827a960dd94.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/284424427bbd6b1d788c217440bf0827a960dd94#ocamlPackages.happy-eyeballs

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/c24xrzsdzqqpmdnvflpd6yk5fqphnn7j-ocaml5.1.1-happy-eyeballs-0.6.0
ls -la /nix/store/c24xrzsdzqqpmdnvflpd6yk5fqphnn7j-ocaml5.1.1-happy-eyeballs-0.6.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages failed to build:

jackline
ocamlPackages.dns-client-lwt
ocamlPackages.happy-eyeballs-lwt

1 package built:

ocamlPackages.happy-eyeballs

Maintainer pings
cc @vbgl @ulrikstrid for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/roburio/happy-eyeballs/releases.
meta.description for ocamlPackages.happy-eyeballs is: Connecting to a remote host via IP version 4 or 6
meta.homepage for ocamlPackages.happy-eyeballs is: https://github.com/roburio/happy-eyeballs
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.0 with grep in /nix/store/9pqzlfjy2d7vz04r38i5f6n2rinzb2p4-ocaml5.1.1-happy-eyeballs-1.0.0
found 1.0.0 in filename of file in /nix/store/9pqzlfjy2d7vz04r38i5f6n2rinzb2p4-ocaml5.1.1-happy-eyeballs-1.0.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

jackline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9pqzlfjy2d7vz04r38i5f6n2rinzb2p4-ocaml5.1.1-happy-eyeballs-1.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.happy-eyeballs https://github.com/r-ryantm/nixpkgs/archive/d1aa37aaa35062b724b6930bc5b3ca7cc9b4a651.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d1aa37aaa35062b724b6930bc5b3ca7cc9b4a651#ocamlPackages.happy-eyeballs

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9pqzlfjy2d7vz04r38i5f6n2rinzb2p4-ocaml5.1.1-happy-eyeballs-1.0.0
ls -la /nix/store/9pqzlfjy2d7vz04r38i5f6n2rinzb2p4-ocaml5.1.1-happy-eyeballs-1.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

19 packages failed to build:

jackline
ocamlPackages.cohttp-mirage
ocamlPackages.conduit-mirage
ocamlPackages.dns-cli
ocamlPackages.dns-client-lwt
ocamlPackages.dns-client-mirage
ocamlPackages.dns-stub
ocamlPackages.git-mirage
ocamlPackages.git-unix
ocamlPackages.happy-eyeballs-lwt
ocamlPackages.happy-eyeballs-mirage
ocamlPackages.http-mirage-client
ocamlPackages.irmin-git
ocamlPackages.irmin-graphql
ocamlPackages.irmin-mirage-git
ocamlPackages.irmin-mirage-graphql
ocamlPackages.letsencrypt-mirage
ocamlPackages.mimic-happy-eyeballs
ocamlPackages.plotkicadsch

1 package built:

ocamlPackages.happy-eyeballs

Maintainer pings
cc @vbgl @ulrikstrid for testing.

I don't have time to fix this PR and there are too many breakages since it's a major release. I suggest we just close this so that someone else can pick it up later.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/roburio/happy-eyeballs/releases.
meta.description for ocamlPackages.happy-eyeballs is: Connecting to a remote host via IP version 4 or 6
meta.homepage for ocamlPackages.happy-eyeballs is: https://github.com/roburio/happy-eyeballs
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.0 with grep in /nix/store/qclf4a26b24qbg82kl9g8za8qmf1c1z0-ocaml5.1.1-happy-eyeballs-1.1.0
found 1.1.0 in filename of file in /nix/store/qclf4a26b24qbg82kl9g8za8qmf1c1z0-ocaml5.1.1-happy-eyeballs-1.1.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

jackline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qclf4a26b24qbg82kl9g8za8qmf1c1z0-ocaml5.1.1-happy-eyeballs-1.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.happy-eyeballs https://github.com/r-ryantm/nixpkgs/archive/7444613eeba247924ba3e53aa96df7147eb10ae9.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7444613eeba247924ba3e53aa96df7147eb10ae9#ocamlPackages.happy-eyeballs

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qclf4a26b24qbg82kl9g8za8qmf1c1z0-ocaml5.1.1-happy-eyeballs-1.1.0
ls -la /nix/store/qclf4a26b24qbg82kl9g8za8qmf1c1z0-ocaml5.1.1-happy-eyeballs-1.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

19 packages failed to build:

jackline
ocamlPackages.cohttp-mirage
ocamlPackages.conduit-mirage
ocamlPackages.dns-cli
ocamlPackages.dns-client-lwt
ocamlPackages.dns-client-mirage
ocamlPackages.dns-stub
ocamlPackages.git-mirage
ocamlPackages.git-unix
ocamlPackages.happy-eyeballs-lwt
ocamlPackages.happy-eyeballs-mirage
ocamlPackages.http-mirage-client
ocamlPackages.irmin-git
ocamlPackages.irmin-graphql
ocamlPackages.irmin-mirage-git
ocamlPackages.irmin-mirage-graphql
ocamlPackages.letsencrypt-mirage
ocamlPackages.mimic-happy-eyeballs
ocamlPackages.plotkicadsch

1 package built:

ocamlPackages.happy-eyeballs

Maintainer pings
cc @vbgl @ulrikstrid for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/roburio/happy-eyeballs/releases.
meta.description for ocamlPackages.happy-eyeballs is: Connecting to a remote host via IP version 4 or 6
meta.homepage for ocamlPackages.happy-eyeballs is: https://github.com/roburio/happy-eyeballs
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.2.0 with grep in /nix/store/ni6z9sq20fhcd326sfspvbhv9ggmwvmn-ocaml5.1.1-happy-eyeballs-1.2.0
found 1.2.0 in filename of file in /nix/store/ni6z9sq20fhcd326sfspvbhv9ggmwvmn-ocaml5.1.1-happy-eyeballs-1.2.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

jackline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ni6z9sq20fhcd326sfspvbhv9ggmwvmn-ocaml5.1.1-happy-eyeballs-1.2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.happy-eyeballs https://github.com/r-ryantm/nixpkgs/archive/3c75dca41135859258463ef5772b4abf0682ca13.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/3c75dca41135859258463ef5772b4abf0682ca13#ocamlPackages.happy-eyeballs

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ni6z9sq20fhcd326sfspvbhv9ggmwvmn-ocaml5.1.1-happy-eyeballs-1.2.0
ls -la /nix/store/ni6z9sq20fhcd326sfspvbhv9ggmwvmn-ocaml5.1.1-happy-eyeballs-1.2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

19 packages built:

jackline
ocamlPackages.conduit-mirage
ocamlPackages.dns-cli
ocamlPackages.dns-client-lwt
ocamlPackages.dns-client-mirage
ocamlPackages.dns-stub
ocamlPackages.git-mirage
ocamlPackages.git-unix
ocamlPackages.happy-eyeballs
ocamlPackages.happy-eyeballs-lwt
ocamlPackages.happy-eyeballs-mirage
ocamlPackages.http-mirage-client
ocamlPackages.irmin-git
ocamlPackages.irmin-graphql
ocamlPackages.irmin-mirage-git
ocamlPackages.irmin-mirage-graphql
ocamlPackages.letsencrypt-mirage
ocamlPackages.mimic-happy-eyeballs
ocamlPackages.plotkicadsch

Maintainer pings
cc @vbgl @ulrikstrid for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/roburio/happy-eyeballs/releases.
meta.description for ocamlPackages.happy-eyeballs is: Connecting to a remote host via IP version 4 or 6
meta.homepage for ocamlPackages.happy-eyeballs is: https://github.com/roburio/happy-eyeballs
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.2.1 with grep in /nix/store/vdmx661l1a00xsdi4k719bwjniipnbcd-ocaml5.1.1-happy-eyeballs-1.2.1
found 1.2.1 in filename of file in /nix/store/vdmx661l1a00xsdi4k719bwjniipnbcd-ocaml5.1.1-happy-eyeballs-1.2.1

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

jackline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vdmx661l1a00xsdi4k719bwjniipnbcd-ocaml5.1.1-happy-eyeballs-1.2.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.happy-eyeballs https://github.com/r-ryantm/nixpkgs/archive/393ba2f2740c61e837c95e24b96653d228beb894.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/393ba2f2740c61e837c95e24b96653d228beb894#ocamlPackages.happy-eyeballs

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vdmx661l1a00xsdi4k719bwjniipnbcd-ocaml5.1.1-happy-eyeballs-1.2.1
ls -la /nix/store/vdmx661l1a00xsdi4k719bwjniipnbcd-ocaml5.1.1-happy-eyeballs-1.2.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

19 packages built:

jackline
ocamlPackages.conduit-mirage
ocamlPackages.dns-cli
ocamlPackages.dns-client-lwt
ocamlPackages.dns-client-mirage
ocamlPackages.dns-stub
ocamlPackages.git-mirage
ocamlPackages.git-unix
ocamlPackages.happy-eyeballs
ocamlPackages.happy-eyeballs-lwt
ocamlPackages.happy-eyeballs-mirage
ocamlPackages.http-mirage-client
ocamlPackages.irmin-git
ocamlPackages.irmin-graphql
ocamlPackages.irmin-mirage-git
ocamlPackages.irmin-mirage-graphql
ocamlPackages.letsencrypt-mirage
ocamlPackages.mimic-happy-eyeballs
ocamlPackages.plotkicadsch

Maintainer pings
cc @vbgl @ulrikstrid for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/roburio/happy-eyeballs/releases.
meta.description for ocamlPackages.happy-eyeballs is: Connecting to a remote host via IP version 4 or 6
meta.homepage for ocamlPackages.happy-eyeballs is: https://github.com/roburio/happy-eyeballs
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.2.2 with grep in /nix/store/nwj3ijwipsnl66m7vrc0qk3f5vga2g4j-ocaml5.2.0-happy-eyeballs-1.2.2
found 1.2.2 in filename of file in /nix/store/nwj3ijwipsnl66m7vrc0qk3f5vga2g4j-ocaml5.2.0-happy-eyeballs-1.2.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

jackline

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/nwj3ijwipsnl66m7vrc0qk3f5vga2g4j-ocaml5.2.0-happy-eyeballs-1.2.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A ocamlPackages.happy-eyeballs https://github.com/r-ryantm/nixpkgs/archive/6b9033af806c25c83456dd5ad4a7e74a82b7f2b4.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/6b9033af806c25c83456dd5ad4a7e74a82b7f2b4#ocamlPackages.happy-eyeballs

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nwj3ijwipsnl66m7vrc0qk3f5vga2g4j-ocaml5.2.0-happy-eyeballs-1.2.2
ls -la /nix/store/nwj3ijwipsnl66m7vrc0qk3f5vga2g4j-ocaml5.2.0-happy-eyeballs-1.2.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 19 packages built:

jackline
ocamlPackages.conduit-mirage
ocamlPackages.dns-cli
ocamlPackages.dns-client-lwt
ocamlPackages.dns-client-mirage
ocamlPackages.dns-stub
ocamlPackages.git-mirage
ocamlPackages.git-unix
ocamlPackages.happy-eyeballs
ocamlPackages.happy-eyeballs-lwt
ocamlPackages.happy-eyeballs-mirage
ocamlPackages.http-mirage-client
ocamlPackages.irmin-git
ocamlPackages.irmin-graphql
ocamlPackages.irmin-mirage-git
ocamlPackages.irmin-mirage-graphql
ocamlPackages.letsencrypt-mirage
ocamlPackages.mimic-happy-eyeballs
ocamlPackages.plotkicadsch

Maintainer pings
cc @vbgl @ulrikstrid for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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


Update Gradle version

LibGDX was using an outdated version of Gradle, this will update it to a new version.

@carllei Merge the PR when ready.

It has now been merged.


CMake target property not found

Hi,
I have noticed that the MFEM_TPL_INCLUDE_DIRS variable is not properly defined on my computer, when I try to compile MFEM with CMake. This happens with the latest version from the git (running an up-to-date archlinux and cmake 3.8.0). This poses a problem when installing the library locally on the computer and using the MFEMConfig.cmake file, which produces an error because of a MFEM_TPL_INCLUDE_DIRS-NOTFOUND.

Thanks for reporting this issue - it should be resolved in #214.

Resolved by 2f1ab15a.


Add edition info into metadata

Since edition feature was introduced, external tools have to support this new feature.
But cargo metadata doesn't provide info about package edition.
This commit adds edition field to SerializedPackage struct to add the corresponding field into metadata output.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @matklad (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

https://github.com/rust-lang/cargo/pull/5816 will make an edition a property of a target, so it make sense to this in metadata as well

Indeed! @Undin want to switch this to being part of a serialized target?

Indeed! @Undin want to switch this to being part of a serialized target?

Yep! In this case, I'll wait when #5816 will be merged to add edition field into SerializedTarget

#5816 will make an edition a property of a target, so it make sense to this in metadata as well

If we make edition part of target metadata, should we add this info into package data at all?

I think having it in both places is probably best for now, at the package level Cargo may distinguish various features of manifests and so it may be worthwhile at some point!

@Undin ok that PR has now merged! Want to update this when you get a chance?

@alexcrichton yep, I'll update it ASAP

Excellent. Thanks @Undin.

I've added edition info into target object in metadata
But I've had to rebase onto master to get changes from #5816

Thanks! Looks like a test may be failing on windows though?

Oops, forgot about slashes

@bors: r+

:pushpin: Commit 3fdce227b4200afb156474898ca76c58037341d0 has been approved by alexcrichton

:hourglass: Testing commit 3fdce227b4200afb156474898ca76c58037341d0 with merge 140fde355708d122384474cd10f2e814073829ee...

:broken_heart: Test failed - status-travis

:hourglass: Testing commit 3fdce227b4200afb156474898ca76c58037341d0 with merge f14aea53ad9c46efa8429da332324935e92e38b5...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing f14aea53ad9c46efa8429da332324935e92e38b5 to master...


Support receiving out of band invitations with public dids for the didexchange protocol

#930 adds support for receiving out of band invitations with public dids, but only supports processing it for 0160 connections. We should still add support to do this with the didexchange protocol

That's an interesting way to get the credential you need!
I think yes, currently the flow doesn't take into account the implicit flow. What would be the easiest approach I think is to keep the DidExchangeProtocol.createRequest to need a out of band record, that we can create on the module layer beforehand. Another approach would be to create a DidExchangeProtocol.createRequestFromDid and ConnectionService.createRequestFromDid and expose it through a ConnectionsApi.sendRequestToDid or something similar (don't like sendRequestToDid too much).
I think it would work fine with the pthid:

When a request responds to an implicit invitation, its ~thread.pthid MUST contain a DID URL that resolves to the specific service on a DID document that contains the invitation.

We should modify the request to include the public did with service as the pthid, like so: https://github.com/hyperledger/aries-rfcs/blob/main/features/0023-did-exchange/README.md#example-referencing-an-implicit-invitation
The connectionless flow should also work I assume and is probably easier to implement, so I think it's a bit dependant on which flow works best for your use case. At the moment we don't support proposals for connectionless credential issuance though

Thanks for the explanation and suggestions @TimoGlastra ! I think it would be nice to support these implicit invitations from the module level in order to make it more evident for users how to handle both invitation types. I'll dig a bit more about the possibilities and open a PR including these public DID handling in DIDExchange protocol.

@genaris are you still working on this?

Slowly but yes!

I think https://github.com/openwallet-foundation/credo-ts/pull/1348, combined with the support of resolvable DIDs in DID Exchange in https://github.com/openwallet-foundation/credo-ts/pull/1550 covered this, unless I'm missing something.


Better error handling in restore benchmark

Issue Number
ADP-804
Overview

Handle case where node exits before restore bench is finished.
Fix disk space error.

Comments
Buildkite nightly builds
The restore benchmark no longer fails from the original error. It now seems to reach the 10 hour timeout on mainnet. So the benchmark wallets need to be made smaller... in another PR.

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+


Implement basic front end

[x] Time series plotting of sensor readings
[ ] Adding/editing/deleting sensor types, sensors, and locations

Done at the moment:

[x] Add sensor types
[x] Add sensors
[x] Add location schemas
[x] Add locations
[x] List sensors
[x] List locations
[ ] Edit sensors
[ ] Edit locations
[ ] Delete sensors
[ ] Delete locations
[ ] Connect sensors to locations

I'll open new issues for the ones that aren't done.

See #69, #112, and #113


HTTPClient based redirect check

More consolidation & cleanup.
We had two different ways of checking for redirects, a HTTPClient based one and a URLSession based one. This moves to a single one and starts the transition towards async/await conversion.
This is ready for review but I'm leaving it in "draft" to let at least one more nightly run with all of today's earlier changes before we deploy this (which a merge does automatically).

Last night's validation went fine, merging this now.


Correction for raw affiliation Sorbonne Université, CNRS, ISIR, Paris, France

Correction needed for raw affiliation Sorbonne Université, CNRS, ISIR, Paris, France
raw_affiliation_name: Sorbonne Université, CNRS, ISIR, Paris, France
new_rors: 02en5vm52;02feahw73;05neq8668
previous_rors: 02en5vm52;02feahw73
works_examples: W4385572224;W4389269373
contact: efc2006b1114ebff4195f8e424bb1658:95c528721674ef010b719cef62 @ sorbonne-universite.fr

This issue was accepted and ingested by the OpenAlex team on 2024-11-01. The new affiliations should be visible within the next 7 days.


Makefile: Fix typo podmon -> podman

This typo was introduced in 3aa63b2b
Signed-off-by: Marcos Paulo de Souza<EMAIL_ADDRESS>

Nice catch, LGTM

bot, add author to whitelist

LGTM, @marcosps TYVM for the contribution!

@TomSweeneyRedHat I'm happy to contribute to the containers environment!

bot, retest this please

@rh-atomic-bot r+


L4T 36.2.0 (Jetpack 6 DP) - deepstream doesn't build

Deepstream depends on tritonserver which is now updated for JP6.  I was able to get Deepstream to build by adding the following to the config.py:
if L4T_VERSION >= Version('36.2.0'): # JetPack 6.0 DP
    DEEPSTREAM_URL = 'https://api.ngc.nvidia.com/v2/resources/org/nvidia/deepstream/6.4/files?redirect=true&path=deepstream_sdk_v6.4.0_jetson.tbz2'
    DEEPSTREAM_TAR = 'deepstream_sdk_v6.4.0_jetson.tbz2'
    PYDS_VERSION = 'v1.1.10'
elif ...

The link I found doesn't match the nvidia.box.com links used for the other deepstream downloads, so that might need to be addressed to make things consistent.
I also ran into an issue with building librdkafka, which I resolved by adding a section to the Dockerfile to install python-is-python3 before cloning librdkafka, not sure if this is the right solution but this likely stems from the changing python versions between Ubuntu 20 and 22.
RUN apt-get update && \
    apt-get install -y --no-install-recommends \
		python-is-python3 \
    && rm -rf /var/lib/apt/lists/* \
    && apt-get clean

Additionally I had to add tensorrt as a dependency for the deepstream container to resolve an issue with libnvinfer.so.8 not being found.  Not sure if this is the correct solution to building a deepstream container with a minimal environment but it worked for me.

Thanks again @Mark-Firestorm, fixed this in https://github.com/dusty-nv/jetson-containers/commit/b6c788c2bf1564e93a2159e8710edbaf72df11cd, and rebuilt the DeepStream containers 👍

Thanks @dusty-nv!


NPM - How to setup a CA for SSL self-signed

Question, Bug, or Feature?
Type: Question
Enter Task Name: Npm
Environment

Azure Pipelines: Can provide those if needed
Agent - Hosted or Private: Private

Issue Description
Doing config set ca "..." through the "Custom" NPM command isn't persisted so that when I try to do npm install in the next step, I'm still getting a SELF_SIGNED certificate error
(How else can I pass a CA directly so npm can validate our internal CA certificate ?)
Here's an example Pipeline
pool:
  name: Hosted Build
  demands: npm
steps:
- task: DotNetCoreCLI@2
  displayName: Restore
  inputs:
    command: restore
    projects: '$(Parameters.RestoreBuildProjects)'
  enabled: false

- task: Npm@1
  displayName: 'NPM Config'
  inputs:
    command: custom
    verbose: false
    customCommand: 'config set ca "..."'

- task: Npm@1
  displayName: 'npm install'
  inputs:
    verbose: false

Task logs

Starting: npm install
Task         : npm
Description  : Install and publish npm packages, or run an npm command. Supports npmjs.com and authenticated registries like Package Management.
Version      : 1.148.0
Author       : Microsoft Corporation
Help         : More Information
SYSTEMVSSCONNECTION exists true
SYSTEMVSSCONNECTION exists true
[command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" --version"
6.5.0
[command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" config list"
; cli configs
metrics-registry = "https://registry.npmjs.org/"
scope = ""
user-agent = "npm/6.5.0 node/v11.9.0 win32 x64"
; environment configs
userconfig = "D:\CI\Agent-Bld\_work\1\npm\3731.npmrc"
; builtin config undefined
prefix = "C:\Users\USRAPP_A1_FDMTLBLD-1\AppData\Roaming\npm"
; node bin location = C:\Program Files\nodejs\node.exe
; cwd = D:\CI\Agent-Bld_work\1\s
; HOME = C:\Users\USRAPP_A1_FDMTLBLD-1
; "npm config ls -l" to show all defaults.
[command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" install"
npm ERR! code SELF_SIGNED_CERT_IN_CHAIN
npm ERR! errno SELF_SIGNED_CERT_IN_CHAIN
npm ERR! request to https://registry.npmjs.org/@types%2Fbootstrap failed, reason: self signed certificate in certificate chain
...

Error logs

[command]C:\Windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" install"
npm ERR! code SELF_SIGNED_CERT_IN_CHAIN
npm ERR! errno SELF_SIGNED_CERT_IN_CHAIN
npm ERR! request to https://registry.npmjs.org/@types%2Fbootstrap failed, reason: self signed certificate in certificate chain

As a workaround, I added an inline powershell task to setup the .npmrc in my project along this line:
Out-File -InputObject "ca=""$env:CAnpm""" -FilePath '.npmrc' -Encoding ASCII
For the record, the string must have the \n in the string as documented here: https://docs.npmjs.com/misc/config#ca

(oops, edited tags on the wrong issue)

Ultimately, I think that's what you're going to want to do. You might consider checking in the certificate file and using the cafile option instead of the ca option, but the npm task uses a temporary .npmrc, so the npm config command won't affect your overall state.


java.lang.IllegalStateException: Not allowed to set the device owner because there are already some accounts on the device

I am getting this error on my device (API 23), which I removed all accounts and also did the factory reset.
But on the emulator, this error is not there. Is this a device issue?
adb command
adb shell dpm set-device-owner com.google.codelabs.cosu/.DeviceAdminReceiver

The error
java.lang.IllegalStateException: Not allowed to set the device owner because there are already some accounts on the device
        at android.os.Parcel.readException(Parcel.java:1607)
        at android.os.Parcel.readException(Parcel.java:1552)
        at android.app.admin.IDevicePolicyManager$Stub$Proxy.setDeviceOwner(IDevicePolicyManager.java:3515)
        at com.android.commands.dpm.Dpm.runSetDeviceOwner(Dpm.java:114)
        at com.android.commands.dpm.Dpm.onRun(Dpm.java:82)
        at com.android.internal.os.BaseCommand.run(BaseCommand.java:47)
        at com.android.commands.dpm.Dpm.main(Dpm.java:38)
        at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
        at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:306)

Facing same problem.

You should remove accounts from Phone.

first run this
adb shell dpm remove-active-admin com.google.codelabs.cosu/.DeviceAdminReceiver
then run
adb shell dpm set-device-owner com.google.codelabs.cosu/.DeviceAdminReceiver
this helps to set my device to device owner mode.

I had fixed the issue by formatting the device but removing any accounts on the device does the job.
@vishalguptahmh that command didn't work when i tested it.


[Traefik Plugin Catalog] Plugin Analyzer has detected a problem.

The plugin was not imported into Traefik Plugin Catalog.
Cause:
failed to load readme: failed to get the readme file: GET https://api.github.com/repos/iloahz/traefik-plugin-manual-access-control/readme?ref=v0.0.2: 404 Not Found []

Traefik Plugin Analyzer will restart when you will close this issue.
If you believe there is a problem with the Analyzer or this issue is the result of a false positive, please contact us.

added


Location subcommand doesn't actually update the location

That's super weird and needs to be fixed. Probably because I'm not referencing it in the right place

Working


Close #112: MnJobExecutor uses Micronaut Threads instead of Camunda Own ThreadPool

SpringJobExecutor is implemented similar.

Hello @tobiasschaefer
With a second commit I added some documentation and configuration for loadtest.
Is it ok or should I just remove it?


Missing Org Url drop down selection

Describe the Bug with repro steps

Create a Dataverse Action (Get Record by ID)
ORL URL is available for selection

What type of Logic App Is this happening in?
Consumption (Portal)
Which operating system are you using?
Windows
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
{
  "type": "ApiConnection",
  "inputs": {
    "host": {
      "connection": {
        "referenceName": "dynamicscrmonline"
      }
    },
    "method": "get",
    "headers": {
      "prefer": "odata.include-annotations=*",
      "accept": "application/json;odata.metadata=full",
      "organization": "@{encodeURIComponent(encodeURIComponent('https://aer-uat.crm9.dynamics.com'))}"
    },
    "path": "/api/data/v9.1/@{encodeURIComponent(encodeURIComponent('contacts'))}(@{encodeURIComponent(encodeURIComponent(items('For_each')?['_ait_contact_value']))})"
  }
}

Screenshots or Videos

Browser
Chrome
Additional context
I have other dataverse actions that contain the ORL URL selection, its only behaving this way on the 'Get Record' action. I've removed and recreated and still no luck.

Hi @mcruz2525, thanks for reporting your issue, but I'm confused on what the exact issue is.
Is the Org Url parameter missing altogether from the panel?  Or are the dynamic data / parameter dropdown options not loading?  Or something else?
I'm seeing both the parameter and the dynamic data options when I try to reproduce your issue.
If it's that you aren't seeing the parameter dropdown options, those are dynamically populated based on the connection you have assigned to the action, and I would double check the connection you're using.


As a developper, I can set up the colors and brand name that apply everywhere

Create a settings file containing the brand name and the configuration of colors for the whole product.

done already, will be pushed soon


Implement a dedicated email service

Move out the sender service to its own module
Move out the Jinja renderer service to its own module
Add a base template (taken from https://github.com/ActiveCampaign/postmark-templates) for email so we have a bit more polished experience (it supports dark mode!):

LGTM! Did you discuss with @birkjernstrom about redesigning all emails? I don't remember how intentional the previous aesthetic was.

I did not, but yes, we could use @birkjernstrom's opinion. It's just a small wrapper to the existing emails, their content is untouched.

Now, with the logo! It'll be served by our Next.js app on Vercel, so we'll benefit from their CDN.


[v1.15] helm: bump certgen to v0.1.15

This is a backport of https://github.com/cilium/cilium/pull/34934 for v1.15 and v1.14. It needs to be handled differently since v1.16+ uses certgen v0.2.x, while earlier versions uses certgen v0.1.x.
See also https://github.com/cilium/certgen/pull/294.

/test

/test-backport-1.15


chore: loosen graphql dependency

Context
Loosen graphql dependency to support v2
https://github.com/rmosolgo/graphql-ruby/blob/master/CHANGELOG.md#200-9-february-2022
What's inside

[x] Loosen graphql dependency

Checklist:

[ ] I have added tests
[ ] I have made corresponding changes to the documentation

Thanks for contributing!
I'll fix the tests and merge this PR after that.


Clean up intro line

What I did
I just provided a better way to introduce the repo.

@mgifford Thanks so much for contributing!


In the micro-frontend scenario, a specific VSCode file cannot be opened by Vue devtool for a child application

Vue devtools version
6.5.0
Link to minimal reproduction

Steps to reproduce & screenshots
In the micro-frontend scenario, a specific VSCode file cannot be opened by Vue devtool for a child application, although it can be opened by the main application. The "code" command has been installed.

What is expected?
can open file
What is actually happening?
not open
System Info
System:
    OS: macOS 13.5
    CPU: (4) x64 Intel(R) Core(TM) i5-7600 CPU @ 3.50GHz
    Memory: 191.78 MB / 64.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 16.20.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.19.4 - /usr/local/bin/npm
  Browsers:
    Chrome: 116.0.5845.96
    Safari: 16.6
  npmPackages:
    vue: ^2.6.11 => 2.7.8

Any additional comments?
No response

Can you provide a minium reproduction?


Add capability to specify curve type in curve metadata

Graphical curves (and possibly other applications) need to be able to accommodate decreasing X or Y value monotonicity. The default rules in paireddata enforce increasing monotonicity, which will result in resorted probabilities for graphical curves. There is currently commented out lines to handle decreasing monotonicity, but even if uncommented no current means to tell the paireddata object to expect that. Also currently the monotonicity logic is duplicated for both X and Y axes, but there will be cases (graphical discharge frequency curves currently) where increasing monotonicity should be expected on one axis (flow on the y axis in this case) and decreasing monotonicity on the other (probability on x).
Recommend creating constructors for the curve metadata to handle these cases, and potentially another set of CurveTypeEnum values to handle cases in which increasing is expected on one axis and decreasing on the other.

I think the team once discussed using non-exceedance probability only. I may not have been good at maintaining that decision. In any case, if we do, then both X and Y should be increasing, all the time, right?

We can adapt either way. How hard would it be to convert to non exceedance? Just a loop to do 1-x?

I think that's probably true(?) although i would say if functionality to support both can be added fairly simply it may be worthwhile to do it, just for the sake of flexibility/stability. It seems like it's either allow for both and detect/handle appropriately, detect and throw an exception, or detect and convert from exceedance to non-exceedance, and since all would probably be about as much effort to implement i'd lean towards the one that adds flexibility. In particular as we have at least one production FDA model example in which exceedance was used.

It seems we need to add the following types to CurveTypesEnum:
-InverselyMonotonicallyIncreasing,
-InverselyStrictlyMonotonicallyIncreasing,
-InverselyMonotonicallyDecreasing,
-InverselyStrictlyMonotonicallyDecreasing,
where increasing/decreasing refers to Yvals.
Are 9 different curve types a lot to track?

Thinking from a different perspective, what is the purpose of tracking curve types? I think the purpose is purely validation. I'm not tracking any methods that handle curve type nor plans for that. So we want to validate that the specified curves make sense before they go into the compute.
What types do we expect?

Strictly positive. All frequency functions. These functions must be strictly positive because frequency is non-exceedance probability and the functions represent CDFs.

Weakly positive. System response curves, flow transforms, stage transforms, stage damage. These functions should be weakly positive because frequency functions are strictly positive, but flat regions could theoretically make sense.

I suppose that flow and stage transforms could be weakly negative too - compose and other relevant methods should work fine because they don't depend on order. I think we've ruled out strictly negative because any frequency function will be a CDF on non-exceedance probability.
@AlexRyanUSACE do you have any particular user story in mind motivating the capability to handle curve types other than (1) and (2)?

We decided during a meeting on 20 April 2022 that we will only handle strictly positive and weakly positive


⚠ Bofrost.fr has degraded performance

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

HTTP code: 200
Response time: 1102 ms

Resolved: Bofrost.fr performance has improved in 3e78e7e after 20 minutes.


Initial webhooks implementation

More to do to harden the webhook implementation (particularly providing a response path - whether a state store like MongoDB or post-back), but this currently provides a simple way to drive work into the Kafka bridge trivially over JSON (YAML needs a bit more work, but will be nice for Solidity deployments).

Quite a big structural change to the code in this branch, to split the KafkaBridge layer into two.

KafkaCommon with the producer/consumer logic, common to Webhooks and the Bridge
KafkaBridge the bridge itself
Also introduced a common set of mocks to use in both.

Codecov Report

Merging #3 into master will decrease coverage by 10.38%.
The diff coverage is 67.74%.

@@            Coverage Diff             @@
##           master      #3       +/-   ##
==========================================
- Coverage   96.69%   86.3%   -10.39%
==========================================
  Files          11      14        +3
  Lines         847    1037      +190
==========================================
+ Hits          819     895       +76
- Misses         20     132      +112
- Partials        8      10        +2

Impacted Files
Coverage Δ

internal/kldkafka/client.go
0% <0%> (ø)
:arrow_up:

internal/kldwebhooks/webhooksbridge.go
0% <0%> (ø)

internal/kldkafka/clientmock.go
100% <100%> (ø)

cmd/ethconnect.go
100% <100%> (ø)
:arrow_up:

internal/kldkafka/kafkacommon.go
94.87% <94.87%> (ø)

internal/kldkafka/kafkabridge.go
97.1% <95.74%> (-1.58%)
:arrow_down:

Continue to review full report at Codecov.

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


Bug: Windows Version tries to upload to http://upload

I think there may be an issues with translating between windows files system and linux file system. / and \.
When trying to upload, the post request get set to http://upload instead of the the userpath.
Host: upload
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:98.0) Gecko/20100101 Firefox/98.0
Accept: application/json
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Cache-Control: no-cache
X-Requested-With: XMLHttpRequest
Content-Type: multipart/form-data; boundary=---------------------------25573539524841597451864585240
Content-Length: 194636
Origin: http://<IP_ADDRESS>:8000
Connection: keep-alive
Referer: http://<IP_ADDRESS>:8000/

If you are busy, I can try to make a fix to it, but I would need to learn the code.

Oh hey. Yeah this could be. Never tried upload on Windows tbh. If you are able to fix go ahead and send me a pull request with a fix. Would be very welcome. Otherwise I might look at it if I have spare time.
Thanks for letting me know.

So changing path for filepath will only "repair" the display on the page though. Upload still breaks cause for some reason I am not yet aware of. For some reason on windows when upload the OPTIONS request in fact goes to "Host: upload" instead of "Host: ip:port"/ipload.
So I have to find out why.

    <!-- Dropzone related config -->
    <script>
        Dropzone.autoDiscover = false;
    </script>
    {{ if (eq .Directory.RelPath "/") }}
        <script>
            let url = "/upload"
        </script>
    {{ else }}
        <script>
            let url = "{{.Directory.RelPath}}/upload"
        </script>
    {{ end }}

    <script>
        let myDropzone = new Dropzone("div#mydropzone", {
            autoProcessQueue: false,
            paramName: "files",
            method: "post",
            url: url,
            uploadMultiple: true,
            parallelUploads: 100,
            maxFiles: 100,
            maxFilesize: 10240,

            init: function () {
                document.querySelector("button[type=submit]#submit-dropzone").addEventListener("click", function(e) {
                    e.preventDefault();
                    e.stopPropagation();
                    myDropzone.processQueue();
                })

            }
        });

        myDropzone.on("successmultiple", function () {
            location.reload();
        });
    </script>

This is from index.html in static template folder. So in fact in linux it seams like you are in the root of where goshs is running when posting to /upload it will take this as path and add the ip as host.
This behaves different in windows it seams. It will take /upload as host instead of path there.
Working scenario would be to upload a file in a subdirectory while using windows. This is just a workaround though.

Fixed with commit 23631a8


Add Password Visibility Toggle on Signup and Login Pages

Problem
Currently, users are unable to see the password they are typing on the signup and login pages. This can lead to frustration due to mistyping or having to re-enter passwords multiple times.
Proposed Solution
Add a "password visibility toggle" feature on both the signup and login forms. This toggle button would allow users to switch between showing or hiding their password input. Typically, this is represented by an "eye" icon next to the password field.
When clicked, the password should be visible.
Clicking it again should hide the password.
The toggle should:
Use an eye icon for visual indication.
Default to a hidden state (password should be masked initially).
Let me know if any more information is needed for this feature.
Here in the password field add a toggle button

Hi, @Codipk
I’ve raised a PR for the password toggle feature—please review it when you get a chance. I also noticed a lack of responsiveness in the app. If you’d like, feel free to raise an issue with the appropriate labels, or let me know if I should raise it myself.
I'm really happy to contribute and help your project grow!

Can you assign me this ?

According to the rules @lakshitrajput, please start working on this issue. After you complete the task, create a pull request (PR) and make sure to attach a screenshot of your work on the website to showcase what you've done.

Hi, @Codipk
I’ve raised a PR for the password toggle feature—please review it when you get a chance. I also noticed a lack of responsiveness in the app. If you’d like, feel free to raise an issue with the appropriate labels, or let me know if I should raise it myself.
I'm really happy to contribute and help your project grow!

For solving the issue you have to send the request from Contrihub website only


abstract class implements private field unexpected error

Bug Report
🔎 Search Terms
abstract class, private field, implements
🕗 Version & Regression Information

This is a crash
This changed between versions ______ and _______
This is the behavior in every version I tried, and I reviewed the FAQ for entries about 4.1.2
I was unable to test this on prior versions because _______

⏯ Playground Link
Playground link with relevant code
💻 Code

abstract class Foo {
    #dummy: number
}

/**
Class 'Bar' incorrectly implements class 'Foo'. Did you mean to extend 'Foo' and inherit its members as a subclass?
  Property '#dummy' in type 'Bar' refers to a different member that cannot be accessed from within type 'Foo'.ts(2720)
**/
abstract class Bar implements Foo {
    #dummy: number
}

🙁 Actual behavior
Class 'Bar' incorrectly implements class 'Foo'. Did you mean to extend 'Foo' and inherit its members as a subclass?
  Property '#dummy' in type 'Bar' refers to a different member that cannot be accessed from within type 'Foo'.ts(2720)

🙂 Expected behavior
No error

the private field should not be spread to subclass.

This looks like #37924 / #37447. The behavior is the same, regardless of using private fields or the private / protected access modifier.

@MartinJohns
subclass in a es private field is not-accessible.
but typescript private / protected access modifier but is it's only semantically

This is the correct behavior. implements checks assignability, and nothing that isn't a subclass of Foo can be assignable to it. Used a mapped type to remove the private fields if that's what you'd like to happen instead.