cmd: subnet-tags-filter: k=v (and other options) silently fail when provided via ConfigMap

When providing the flags like subnet-tags-filter via ConfigMap, we have assumed and documented that these flags (relying on GetStringMapString) can be populated via a k=v syntax. However, it turns out that when specified via ConfigMap, it needs to be JSON syntax ({"k":"v"}), and not the k=v syntax as documented. The latter syntax only works if directly passed via command-line argument.
As a result, using subnet-tags-filter: foo=bar in the ConfigMap will cause cilium-operator to read the flag as nil and not use any subnet filters at all
Affected flags:
pkg/option/config.go
2771:	if m := viper.GetStringMapString(FixedIdentityMapping); len(m) != 0 {
2777:	if m := viper.GetStringMapString(KVStoreOpt); len(m) != 0 {
2781:	if m := viper.GetStringMapString(LogOpt); len(m) != 0 {
2785:	if m := viper.GetStringMapString(APIRateLimitName); len(m) != 0 {

operator/option/config.go
449:	if m := viper.GetStringMapString(IPAMSubnetsTags); len(m) != 0 {
453:	if m := viper.GetStringMapString(AWSInstanceLimitMapping); len(m) != 0 {
457:	if m := viper.GetStringMapString(ENITags); len(m) != 0 {

Upstream issue: https://github.com/spf13/viper/issues/911
We should replace viper.GetStringMapString by something which behaves the same regardless of wheater the flag has been provided via command-line argument or config-dir (i.e. ConfigMap) entry.

Let me give it a crack

Just want to confirm the current behaviour.
We are having below validation, which basically will check the flag value. And for the flag, only k=v format is accepted. So is the current behaviour not working at all for either format:

json format got rejected by below validation
kv format failed to parse due to upstream issue in viper.

https://github.com/cilium/cilium/blob/d05dcb55960dc7ca79370415d6c203f12dc8c9b7/pkg/option/config.go#L3351

json format
$ cat tmp/subnet-tags-filter
{"k1":"v1", "k2":"v2"}%

$ /usr/lib/go-1.17/bin/go build -o /tmp/GoLand/___2go_build_github_com_cilium_cilium_operator github.com/cilium/cilium/operator #gosetup
/tmp/GoLand/___2go_build_github_com_cilium_cilium_operator --config-dir tmp/
level=fatal msg="Incorrect config-map flag subnet-tags-filter" error="{\"k1\":\"v1\", \"k2\":\"v2\"} must be formatted as key=value" subsys=config

<details>

<details>
<summary>json format</summary>

/usr/lib/go-1.17/bin/go build -o /tmp/GoLand/___2go_build_github_com_cilium_cilium_operator github.com/cilium/cilium/operator #gosetup
/tmp/GoLand/___2go_build_github_com_cilium_cilium_operator --config-dir tmp/
level=info msg="Started gops server" address="<IP_ADDRESS>:9891" subsys=___2go_build_github_com_cilium_cilium_operator
level=warning msg="Running Cilium with "kvstore"="" requires identity allocation via CRDs. Changing identity-allocation-mode to "crd"" subsys=config
...
level=info msg="  --skip-crd-creation='false'" subsys=___2go_build_github_com_cilium_cilium_operator
level=info msg="  --subnet-ids-filter=''" subsys=___2go_build_github_com_cilium_cilium_operator
level=info msg="  --subnet-ids-filter=''" subsys=___2go_build_github_com_cilium_cilium_operator --> this is empty
level=info msg="  --synchronize-k8s-nodes='true'" subsys=___2go_build_github_com_cilium_cilium_operator
...
level=info msg="Cilium Operator  go version go1.17 linux/amd64" subsys=___2go_build_github_com_cilium_cilium_operator

</details>

@sayboras Yes, that looks consistent with my observations. Note that in Cilium v1.10 the former (JSON in ConfigMap) seems to be accepted, but this changed in v1.11.


More parameters fro gromacs-LIE simulations

Currently, the gromit script accept as input the protein and ligand coordinates and topology, together with the simulation time and the force-field. It would be
nice if it can also accept the following parameters:

Parameter
Description
Type
Default

-vsite
Use virtual sites
bool
False

-solvent
Solvent model
str
Infer from force field

-elec
Treatment of electrostatic interactions (RF or PME)
str
Infer from force field

-t
Temperature
float
[200, 300] (K)

-tau
Coupling time for temperature
float
0.1 (ps)

-p
Pressure
float
1 (bar)

-ptau
Coupling time for pressure
float
0.5 (ps)

-d
Minimal distance between periodic images
float
2.25 (nm)

-prfc
Position restraint force constant
float
[200, 200] (kJ/mol/nm^2)

-at
Output resolution
float
0.002 (ns)

-rtc
Use roto-translational constraints
bool
False

-ndlp
Perform simulations in a optimal (NDLP) simulation cell
bool
False

-lie
Calculate ligand interaction energy
bool
False

Note: gromit predecesors accept a list of values for some parameters, for example:
./gmx45md.sh -f protein.pdb -name test  -l ligand.pdb,ligand.itp  -ff amber99SB -lie -d 1.8 -t 100,200,300 -prfc 10000,5000,50,0 -ttau 0.1 -conc 0 -solvent tip3p -ptau 0.5 -time 0.001 -vsite

NDLP is not in the standard Gromacs, we should probably contact Tsjerk about this, and see if we can get it submitted to Gromacs somehow. Alternatively, we'd have to get a patched version from him, but I'd rather not have to maintain that...
It seems that -t is actually an array of floats. CWL supports arrays, but cwltiny doesn't at present. I'll have a look at whether to add that or to just make it a string for now.
Does -lie give additional outputs that we have to return?


Updated settings page added all the details

Pull Request Template for GSoC 2024
Related Issue
[Please list any related issue numbers that this pull request resolves. If none, state "None"]

closes:#369

Description of Changes
[Provide a concise description of the changes introduced by this PR, detailing what’s been added, modified, or fixed.]
Type of Pull Request

[X] Bug Fix
[X] New Feature
[X] Performance Improvement
[ ] Documentation Update
[ ] Code Refactoring
[ ] Security Enhancement
[ ] Other (Specify): _______________

(Please check relevant boxes by entering an "X" inside them)
Screenshots / Demo (if applicable)

[Include any screenshots, GIFs, or videos that demonstrate the change or feature, if available.]
Checklist for Contributor
use'X' in [ ] to check it .

[X] I have reviewed my code before submission.
[X] I have read and followed the project's Contribution Guidelines.
[X] I have tested the code thoroughly.
[X] I have attached related issue numbers, screenshots, or videos (if applicable).
[X] I have added comments to my code where necessary for clarity.
[X] I have checked the existing code base and my changes do not introduce any breaking changes.
[X] My PR addresses only one issue; I have created separate PRs for other issues.
[X] I have ensured that the PR does not include unrelated files.
[X] I am mindful of the project's coding standards and best practices.

Additional Information
[Include any additional context or relevant information that may help in reviewing this PR.]
Contribution Guidelines Reminder
Thank you for contributing to our project! Please ensure you follow the guidelines below:
Contribution Levels

Task Categories:

Basic Tasks: Primarily focused on small changes like minor bug fixes, documentation improvements, and unit testing. Labeled as Easy.
Intermediate Tasks: Moderate-level tasks that involve enhancing existing features, code refactoring, or performance improvements. Labeled as Medium.
Advanced Tasks: Complex tasks like building new features, significant refactoring, or critical bug fixes. Labeled as Hard.

Acknowledging Effort:

Exceptional contributions will be recognized with a higher contribution level if substantial effort and innovation are demonstrated.

Review Process

PRs will be reviewed by the maintainers, and feedback will be provided. Contributors should address feedback promptly and resubmit the PR if necessary.

Contributors are encouraged to participate in the review process of other PRs for community growth.

We appreciate your time and effort in improving this project and look forward to your valuable contributions!

[22:00:50.024] Running build in Washington, D.C., USA (East) – iad1
[22:00:50.162] Cloning github.com/dhairyagothi/StationGuide (Branch: Setting-page-update, Commit: 6fb99bb)
[22:00:52.524] Cloning completed: 2.358s
[22:00:53.440] Restored build cache from previous deployment (7xYzMcxynrfN7oYC57hzcGjAoYNs)
[22:00:53.531] Running "vercel build"
[22:00:54.742] Vercel CLI 37.9.0
[22:00:55.461] Installing dependencies...
[22:00:57.532]
[22:00:57.532] up to date in 1s
[22:00:57.532]
[22:00:57.533] 167 packages are looking for funding
[22:00:57.533]   run npm fund for details
[22:00:57.550] Running "npm run build"
[22:00:57.720]
[22:00:57.720] ><EMAIL_ADDRESS>build
[22:00:57.720] > vite build
[22:00:57.720]
[22:00:57.984] vite v5.4.9 building for production...
[22:00:58.081] transforming...
[22:01:01.310] ✓ 71 modules transformed.
[22:01:01.312] x Build failed in 3.30s
[22:01:01.313] error during build:
[22:01:01.313] Could not resolve "./path_to_back_icon_image" from "src/components/Settings.jsx"
[22:01:01.313] file: /vercel/path0/frontend/src/components/Settings.jsx
[22:01:01.313]     at getRollupError (file:///vercel/path0/frontend/node_modules/rollup/dist/es/shared/parseAst.js:395:41)
[22:01:01.313]     at error (file:///vercel/path0/frontend/node_modules/rollup/dist/es/shared/parseAst.js:391:42)
[22:01:01.313]     at ModuleLoader.handleInvalidResolvedId (file:///vercel/path0/frontend/node_modules/rollup/dist/es/shared/node-entry.js:20006:24)
[22:01:01.313]     at file:///vercel/path0/frontend/node_modules/rollup/dist/es/shared/node-entry.js:19966:26
[22:01:01.339] Error: Command "npm run build" exited with 1
[22:01:01.583]

sync fork first there are many commits behind in your branch
make changes in main branch or update branch @PraveenUppar

Could not resolve "./path_to_back_icon_image" from "src/components/Settings.jsx"

resolve this


Bug report, when ws CloseEvent , will block node app

maybe network exception

maybe network exception

How to solve it? Can we reconnect? Or catch

有解决吗？


Possible omitted definition in chap 36

Edition: 2023-04-01, Advanced Topics
In the following from Chap <IP_ADDRESS>, p.1189:

I believe the following was omitted:

Or just the definition of X_i. Another possibility is this is defined somewhere I haven't read or it's assumed that the reader can figure this out.

I'll ask the authors.

You're correct, thanks!

fixed


[Bridge] [Solidity] Use require for input validation rather than if-revert pattern

Problem
Using require to validate inputs
In our (bridge) Solidity contracts, we are using the pattern if (!cond) revert Error to validate inputs. This is not the best practice and there were several instances of bugs in the past where the contract had if !C someCode; revert(), ommitting the {} around the if-body, which can have unintended consequences. You can read more about the risks (and a bug in APPLE-SSL) here.

[!WARNING]
In short, if written by hand, there is no guarantee that the if-revert pattern is used properly.

Using require(cond, error) has several advantages:

require clearly identify the condition cond that should be checked rather than the negation of the condition that appears in the equivalent if-revert pattern;
require(cond, error) is automatically translated (by the Solidity compiler)  in if (!cond) revert error thereby enforcing that the pattern if-revert is used correctly.

[!IMPORTANT]
The use of require is recommended to validate inputs and has better readability and security.

CustomError to minimise gas cost
There is a caveat though: until recently, require(cond, error) only supported error of type int or strings, and these two types are more expensive gas-wise than custom errors.
This is why developers would deliberately use if (!C) revert CustomError (instead of the require) in the code to optimise gas costs, while compromising security.
As of version 0.8.27 (release notes) , the Solidity compiler supports require(conditional, customError).

[!TIP]
We can now use a safe and gas-efficient pattern require(cond, customError).

Proposed changes
There are two Solidity contracts that are currently using the unsafe and hard-to-read if-revert pattern to validate inputs:

AtomicBridgeInitiatorMOVE.sol
AtomicBridgeCounterpartyMOVE.sol

The proposal is to use require for input validation.
For example, the  validation of inputs amount > 0 in the function initiateBridgeTransfer:
function initiateBridgeTransfer(uint256 moveAmount, bytes32 recipient, bytes32 hashLock)
        external
        returns (bytes32 bridgeTransferId)
    {
        address originator = msg.sender;

        // Ensure there is a valid amount
        if (moveAmount == 0) {
            revert ZeroAmount();
        }

        // Transfer the MOVE tokens from the user to the contract
        if (!moveToken.transferFrom(originator, address(this), moveAmount)) {
            revert MOVETransferFailed();
        }

       ...
    }

would be re-written into (note that the revert related to the transfer of Move tokens is not an input validation, but a more complex error and best practice is to use an if ... revert in that case):
function initiateBridgeTransfer(uint256 moveAmount, bytes32 recipient, bytes32 hashLock)
        external
        returns (bytes32 bridgeTransferId)
    {
        address originator = msg.sender;

        // Ensure there is a valid amount
        require(moveAmount > 0, ZeroAmount());
        // if (moveAmount == 0) {
        //    revert ZeroAmount();
        // }

        // Transfer the MOVE tokens from the user to the contract
        if (!moveToken.transferFrom(originator, address(this), moveAmount)) {
            revert MOVETransferFailed();
        }

       ...
    }

Implementation
To implement the changes we have to:

re-write the input validation conditions into require
use Solidity compiler version >= 0.8.27 (which is recommended anyway as recent  versions fix compiler bugs and improve performance)
run the test suite (if any test exists)

[!IMPORTANT]
There does not seem to be any test in AtomicBridgeInitiatorMOVE.t.sol to check that the functions revert under certain conditions. If is absolutely necessary to add some tests to ensure that we don't disable the checks (e.g. amount > 0) later and introduce some bugs.

Validation
Here are the steps to validate the changes:

we need to add more tests to  AtomicBridgeInitiatorMOVE.t.sol. There should be at least one test for each input validation and expected failure (revert).
we can check that the tests pass and that input are properly validated and the functions revert as expected.

LGTM, thanks @franck44.
What's the process for "approving" issues? I could implement this as a PR but want to avoid duplicating other people's work and PR race conditions so to speak, as well.

I created and tested this PR, please feel free to review @franck44


Cede store new implementation

Description
We have recently updated our provider. This change is an opportunity to update the package version and refresh the according documentation.
PLEASE NOTE- Checklist must be complete prior to review.
Checklist

[x] Increment the version field in package.json of the package you have made changes in following semantic versioning and using alpha release tagging
[x] Check the box that allows repo maintainers to update this PR
[x] Test locally to make sure this feature/fix works
[x] Run yarn check-all to confirm there are not any associated errors
[x] Confirm this PR passes Circle CI checks
[x] Add or update relevant information in the documentation

Docs Checklist

[ ] Include a screenshot of any changes (see docs README on running locally)
[ ] Add/update the appropriate package README (if applicable)
[ ] Add/update the related module in the docs demo (if applicable)
[ ] Add/update the related package in the docs/package.json file (if applicable)

If this PR includes changes to add an injected wallet or SDK wallet module:
Please complete the following using the internal demo package.
To run this demo use the command yarn && yarn dev to get the project running at http://localhost:8080/
Tests with demo app (SDK)

[ ] send transaction
[ ] switch chains
[ ] sign message
[ ] sign typed message
[x] disconnect

@clementjuventin thank you for the PR!
I added a few comments to remove semi-colons.
Can you please ensure all items in the PR description checklist are tested using the demo app that is part of the web3-onboard repo?
There is a Socket Security issue shown above. Please address this as well.
Can you also confirm cede package will build in all supported environments (see all envs in /examples/*)

Thank you @Adamj1232 and sorry for the delay. I've taken your previous comments into account and updated the PR.
Let's hope that this time everything is correct :100:


useMsalAuthentication hook is not working after upgrading to msal-react 1.5.1

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.32.1
Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
1.5.1
Public or Confidential Client?
Public
Description
We are facing an issue with the useMsalAuthentication hook when upgrading to msal-react 1.5.1 in the following PR. We are not receiving any response (accessToken, error) from the hook if we wrap our components with React.StrictMode. I believe it is related to an update we made in msal-react 1.5.0. If we remove the strict mode or downgrade to msal-react 1.4.10 the application works as expected.
Error Message
No error message.
Msal Logs
[Thu, 08 Dec 2022 19:11:11 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:initializeStart
authConfig.js:40 [Thu, 08 Dec 2022 19:11:11 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:initializeEnd
authConfig.js:40 [Thu, 08 Dec 2022 19:11:11 GMT]<EMAIL_ADDRESS>: Info - initialize has already been called, exiting early.
authConfig.js:40 [Thu, 08 Dec 2022 19:11:11 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:handleRedirectStart
authConfig.js:40 [Thu, 08 Dec 2022 19:11:11 GMT] : [3abf3b22-d2c0-4832-b960-ac399ba94351]<EMAIL_ADDRESS>: Info - handleRedirectPromise called but there is no interaction in progress, returning null.
authConfig.js:40 [Thu, 08 Dec 2022 19:11:11 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:handleRedirectEnd
authConfig.js:40 [Thu, 08 Dec 2022 19:11:11 GMT]<EMAIL_ADDRESS>: Info - MsalProvider - msal:handleRedirectStart results in setting inProgress from startup to handleRedirect
authConfig.js:40 [Thu, 08 Dec 2022 19:11:11 GMT]<EMAIL_ADDRESS>: Info - MsalProvider - msal:handleRedirectEnd results in setting inProgress from handleRedirect to none
authConfig.js:40 [Thu, 08 Dec 2022 19:11:11 GMT]<EMAIL_ADDRESS>: Info - MsalProvider - msal:handleRedirectStart results in setting inProgress from startup to handleRedirect
authConfig.js:40 [Thu, 08 Dec 2022 19:11:11 GMT]<EMAIL_ADDRESS>: Info - MsalProvider - msal:handleRedirectEnd results in setting inProgress from handleRedirect to none
authConfig.js:40 [Thu, 08 Dec 2022 19:11:11 GMT]<EMAIL_ADDRESS>: Info - useMsalAuthentication - User is authenticated, attempting to acquire token
authConfig.js:40 [Thu, 08 Dec 2022 19:11:11 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:acquireTokenStart
authConfig.js:40 [Thu, 08 Dec 2022 19:11:12 GMT]<EMAIL_ADDRESS>: Info - Emitting event: msal:acquireTokenSuccess
MSAL Configuration
export const msalConfig = {
    auth: {
        clientId: 'Enter_the_Application_Id_Here', // This is the ONLY mandatory field that you need to supply.
        authority: 'https://login.microsoftonline.com/Enter_the_Tenant_Info_Here', // Defaults to "https://login.microsoftonline.com/common"
        redirectUri: '/', // Points to window.location.origin. You must register this URI on Azure Portal/App Registration.
        postLogoutRedirectUri: '/', // Indicates the page to navigate after logout.
        clientCapabilities: ['CP1'], // this lets the resource owner know that this client is capable of handling claims challenge.
    },
    cache: {
        cacheLocation: 'localStorage', // Configures cache location. "sessionStorage" is more secure, but "localStorage" gives you SSO between tabs.
        storeAuthStateInCookie: false, // Set this to "true" if you are having issues on IE11 or Edge
    },
    system: {
        /**
         * Below you can configure MSAL.js logs. For more information, visit:
         * https://docs.microsoft.com/azure/active-directory/develop/msal-logging-js
         */
        loggerOptions: {
            loggerCallback: (level, message, containsPii) => {
                if (containsPii) {
                    return;
                }
                switch (level) {
                    case LogLevel.Error:
                        console.error(message);
                        return;
                    case LogLevel.Info:
                        console.info(message);
                        return;
                    case LogLevel.Verbose:
                        console.debug(message);
                        return;
                    case LogLevel.Warning:
                        console.warn(message);
                        return;
                }
            },
        },
    },
};

Relevant Code Snippets
export const Profile = () => {
    const { instance } = useMsal();
    const account = instance.getActiveAccount();
    const [graphData, setGraphData] = useState(null);
    const request = {
        scopes: protectedResources.graphMe.scopes,
        account: account,
    };

    const { login, result, error } = useMsalAuthentication(InteractionType.Popup, {
        ...request,
        redirectUri: '/redirect.html',
    });
    useEffect(() => {
        if (!!graphData) {
            return;
        }

        if (!!error) {
            // in case popup is blocked, use redirect instead
            if (error.errorCode === 'popup_window_error' || error.errorCode === 'empty_window_error') {
                login(InteractionType.Redirect, request);
            }

            console.log(error);
            return;
        }

        if (result) {
           let accessToken = result.accessToken;
            getGraphClient(accessToken)
                .api('/me')
                .responseType(ResponseType.RAW)
                .get()
        }
    }, [graphData, result, error, login]);

    if (error) {
        return
Error: {error.message}
;
    }
    return <>{graphData ? <ProfileData response={result} graphData={graphData} /> : null}</>;
};

Reproduction Steps

Clone https://github.com/Azure-Samples/ms-identity-javascript-react-tutorial.git
cd 2-Authorization-I\1-call-graph\SPA.
Checkout branch update-msal-packages.
Configure application.
sign-in and navigate to profile page.

Expected Behavior
Expect the result (accessToken) or an error from the useMsalAuthentication hook.
Identity Provider
Azure AD / MSA
Browsers Affected (Select all that apply)
Chrome
Regression
@azure/msal-react 1.4.10
Source
Internal (Microsoft)

Thanks for raising this. I've determined this is due to a change to StrictMode in React 18, specifically in development mode. What's happening is that React is mounting, unmounting then remounting the component but instead of starting with a clean slate on each mount it is preserving state and refs which results in the finalizer for the token acquisition thinking the component is not mounted and not setting state.
More discussion in this issue in the React repo.
This could be resolved by resetting the value of the ref we use to track whether or not the component is mounted in a useEffect, though it's not clear to me yet if that would cause any unintended consequences or if this is even something we should be responsible for. For now the workarounds seem to be:

Don't use StrictMode until the React team addresses this gap
Serve the app in production mode which does not perform the new behavior
Downgrade to React 17

I'll mark this as a bug but I'm not committing to fixing it on our end quite yet.

Thanks @tnorling. I will update our samples accordingly.

@tnorling Hi Thomas!
As i found this bug this week and had difficulties finding out where does it come from, i looked after the different opinions on this subject.
It seems React team doesn't want to change their way of thinking around that, as they made a whole doc page about this subject :
I can't conceive that the solution is either loosing StrictMode, either loosing React Development mode, either coming back to older version of MSAL or than React 18 which is already kinda "old".
taking account that time has passed by since the last comments on this, can we hope that you could take it on your side? (as it seems to be the main road for all the dependent libraries).
considering MSAL is one of the best, or the best library around authentication right now, i hope solving this point, even if i understand it's a pain you don't need, could be a thing for the community.
Regards,

@FCazabon-EM The issue isn't about the effect running twice or even the component mounting twice (which is what the doc you linked discusses), this has always been the case in StrictMode and we do handle this gracefully. The issue here is that in React 18 they changed the behavior to preserve state between the two mounts of the component which runs counter to the traditional understanding that mounting a component starts over with its initial state.
There's a long thread about this in React's repo I linked in my previous comment, I'd recommend sharing your experience with this change there. Until we get confirmation from the React team that this is both intended behavior and won't be addressed (ideally with an official recommendation about how to handle this) I'm treating this as a bug on React.

Hi @tnorling. I'm wondering how other vendors are approaching this new React behavior. It's been months since the release and maybe some assumptions can be made. What are your thoughs?

Just adding my voice to this.  I've wasted two whole days on this issue on a brand new Next.js project.  Based on previous experience and available documentation with MSAL, I could not have imagined that StrictMode was causing this errant behavior.  There's no hint from the function where to look.  All I could tell was that it was always returning an undefined result.  I had to spend hours injecting log messages into useFetchWithMsal and UseMsalAuthentication with countless app restarts just to get to the point where I finally broke down and checked here for this very issue.
  Even if you won't find a way to fix this on your end, please inject an obvious warning so people like me don't waste our lives chasing this down.  Please add something like, "You seem to be using React 18+ with new StrictMode behavior.  MSAL will not work correctly in this configuration.  Please disable StrictMode for this version of MSAL.  For more information, visit https://whatever."

It's pretty clear by now that this is intended functionality in React (https://github.com/reactjs/react.dev/issues/6123). I know the docs haven't been great up until recently, but asking users of a library this popular to disable React quality checks for a feature to work correctly isn't acceptable.
Are you working on this?

It's been two years since this issue was opened, with no resolution yet. As previous commentors have stated, this is clearly the intended behaviour, yet not even any documentation updates to reflect this limitation have been added.
Furthermore, the buggy code in question isn't even required in react 18 - the warning around calling setState on an unmounted component was removed, and react 18 will simply ignore these state updates. Considering we're now on react 19 with 20 right around the corner, I'd say that this is a point when support for older react versions should probably be dropped, and this ref mounted check removed, which would resolve the problem.


fix: set error type and stack with universal instrumentation

What does this PR do?
With Universal Instrumentation error message, type and stack aren't being sent to Datadog, resulting in poor experience in the APM

There is a small issue related to the source of the error, as well as the stacktrace of the error originating from inside the datadog library. Any help would be appreciated
Motivation
To see a fully working integration
Testing Guidelines

Created a simple lambda function that returns an error, with universal monitoring enabled.
Additional Notes

Types of changes

[x] Bug fix
[ ] New feature
[ ] Breaking change
[ ] Misc (docs, refactoring, dependency upgrade, etc.)

Checklist

[ ] This PR's description is comprehensive
[ ] This PR contains breaking changes that are documented in the description
[ ] This PR introduces new APIs or parameters that are documented and unlikely to change in the foreseeable future
[ ] This PR impacts documentation, and it has been updated (or a ticket has been logged)
[ ] This PR's changes are covered by the automated tests
[ ] This PR collects user input/sensitive content into Datadog

Hey @dali546, thanks a ton for your contribution. I'm taking a look at it now.

Based on these changes, a handler that returns an error used to look like

but now looks like

You can see, we now include the error type and stack trace.
Note that this PR does not implement error type and stack trace for functions that return status code 500 or those that panic.

Thanks again for your contribution @dali546! All looks great. I'm going to add a few tests and then I'll merge it.

Thank you @purple4reina , appreciate the review and support!

Closing in favor of https://github.com/DataDog/datadog-lambda-go/pull/171. I don't have access to add commits to this branch, so I created a new one.


Stream only plays for 3-4 seconds

I seem to be having trouble maintaining a steady video stream. This is my config (using a XiaoMi XiaoFang camera with Fang-Hacks enabled):
{{

        "platform": "Camera-ffmpeg",
        "cameras": [
            {
                "name": "XiaoFang",
                "videoConfig": {
                    "source": "-rtsp_transport tcp -i rtsp://<IP_ADDRESS>/unicast",
                    "stillImageSource": "-i rtsp://<IP_ADDRESS>/unicast -vframes 1 -r 1"
                }
            }
        ]
    }

The video would play for around 4 seconds before it freezes and no longer responds.
Without defining the resolution, bitrate and FPS, the plugin automatically sets it to 1280x720@299kBit. I have tried limiting or reducing the resolution but the same problem persists.
Does anyone have any ideas at all?

I have the same issue. RTSP streaming from the camera directly works. Once the stream is added to this plugin, only a few seconds work and then it freezes up. I've also tested this on a different computers with varying CPU sizes to see if it was a transcoding resource issue, it is not.

The same issue as #243


Addition of SOC program

As a part of https://github.com/tapaswenipathak/Internship at least 9 tickets to be closed. Have raised the PR for the very first one mentioned in the list.

Hello @mridubhatnagar good work, I think this already exists under open source competitions

Oh right, closing.

Sorry for this. Would work on next one and raise the PR as mentioned in the guidelines.

No problems @mridubhatnagar, looking forward to your next PR


$specificIssuerId is not printed to File

Category

[x] Bug

Describe the bug
The IssuerID for the Code-Snippet "HighTrustConfig-ForSharedCertificate.ps1" is not printed to File due to last line of Code: $specificIssuerId | select * | Out-File -FilePath "SecureTokenIssuerID.txt"
Steps to reproduce
When Running the Script:
./HighTrustConfig-ForSharedCertificate.ps1 -CertPath "C:\Certs\MyCert.cer" -CertName "My Cert" -TokenIssuerFriendlyName "SharePoint High-Trust Add-ins Token Issuer"
The Outputfile "SecureTokenIssuerID.txt" only contains the length of the ID (the GUID).
Expected behavior
The Outputfile "SecureTokenIssuerID.txt" should contain the GUID.
Removing the Select-Pipe is doing the Job for me:
$specificIssuerId | Out-File -FilePath "SecureTokenIssuerID.txt"
Developer environment

OS: Windows Server 2016
Framework: PowerShell 5.x

Can you provide some context, as in where you are seeing the HighTrustConfig-ForSharedCertificate.ps1 file? Is that in the docs somewhere?

I have the same error. Here is the script https://docs.microsoft.com/de-de/sharepoint/dev/sp-add-ins/high-trust-configuration-scripts-for-sharepoint

Thanks... doc fixed & will be merged into the live site in the next site refresh.


link to instructions to install qgis from source

As a user I wanted to install QGIS, went to this page on the website, but couldn't find the option to install QGIS from source, I think it will be useful to add this link for more advanced users who would prefer to install from source.

@andrewharvey sorry I was wrong about the tags element. I updated your branch directly. I will merge it after the test. Thanks a lot!


Create package for Brew

http://stackoverflow.com/questions/33112491/homebrew-whom-to-ask-for-a-formula-to-be-added

The right way to release binaries is with brew bottles, but the normal installation works perfectly fine, but if we link the repository instead we can build locally
class GitPhlow < Formula
desc "pragmatic workflow extension for git"
homepage "https://github.com/Praqma/git-phlow"
url "https://github.com/Praqma/git-phlow/releases/download/v0.1.5/git-phlow-0.1.5-darwin-amd64.tar.gz"
version "0.1.5"
sha256 "2f3eeafb0a0c83e93eedd420679de09d0380a30b8a5f7e21be5a1d471e1fc54f"
bottle do
cellar :any_skip_relocation
sha256 "a4a8805b18f1f5b60e027cbfb2a4593511d6cda2f86d9a66d9509e63651748c9" => :sierra
end
def install
bin.install "git-phlow"
end
test do
system "true"
end
end


Create interesting client API example touching all parts of the API

We need an example of the API working across all parts of the data. We need to show how we can link up variants, references and reads with simple Python code.
The API docs are here.
The existing demo for using the variants API is a good place to start.

Some WIP towards fulfilling this, examples with the variant API.
https://github.com/david4096/bioapi-examples

Looks good @david4096!


Training on GPU?

Hi there,
I am wondering whether it is possible to train the relation extraction LSTMs in GPU.
I am also not sure how well they do parallelize and what performance improvements I can expect, but I think it might be worth to give it a shot.
Regarding that, I have two questions:

I tried to launch snorkel with tensorflow-gpu backend some time ago in v0.6, but I got an error which was possibly due to an older CUDA/cuDNN version I am using. Is there some specific version requirement?

In the tensorflow models, I can see that there is a "deterministic" parameter in the NoiseAwareModel, which seems to have to do something with the GPU training. (I am not sure what it does and what the consequences of using it are - if you could please elaborate a bit more on that).

    :param deterministic [EXPERIMENTAL / in development!] If True, attempts to
            make the model deterministic on GPU by replacing all reduce_ and
            other non-deterministic operations; has no effect (other than
            potential slight slowdown) for CPU (at least for single-threaded?).

I have also tried many threads in CPU training, but it doesn't seem to have any difference (actually there is a small slowdown).
I can see that v.0.7.0 beta includes also pyTorch models, with some indications that they can be trained on the GPU. Can you confirm that this works well / is tested?
I have already written my code for v.0.6.2, so I am not sure how long it would take to migrate to the next version of snorkel.
Thanks a lot!

@stephenbach @ajratner confirmed that (at least for me) GPU training doesn't currently work.  I have a working pytorch LSTM that subclasses the original TFNoiseAwareModel, will work on recasting this to fit the new pytorch API in v0.7.0.

@jdunnmon Can you document what doesn't work?

I wasn't sure if the patch above was usable or not, so I cloned the snorkel.learning.pytorch into a sibling package snorkel.learning.pytorch_gpu and used the .to(device) approach to mark portions of the computation to be on GPU if available. Compared with running on a CPU (AWS t3.xlarge), I observe an approximately 5x speedup on GPU (AWS p2.xlarge). I haven't done the nn.dataparallel change so this code is single GPU only.
Code and installation/calling instructions are here, in case others find it useful -- https://github.com/sujitpal/snorkel-pytorch-lstm-gpu

Thanks for the contribution @sujitpal! Closing this for now.


bug: investigate Caracal crash on CI

Bug Report
Current behavior:
Issue when running caracal with scarb updated to 2.3.1 and starknet-foundry to 0.9.0, caracal is giving error:
thread 'main' panicked at src/core/function.rs:116:26:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Expected behavior:
Caracal run checks without error
Steps to reproduce:
Install scarb 2.3.1, snforge 0.9.0, caracal 0.2.2

.


add an option to disable all type translation

This causes types to be translated as {?}, causing the Closure
compiler to not check them.  This is not as awful as it might
seem at first because we believe the TypeScript compiler already
has checked the types.

Note: I am not sure how to test this.

Re testing, what about writing a manual test that calls sickle with the right args and checks for the {?}?
I don't think we can reasonably test that Closure understands this.

Added a test (special-cased the filename, it's gross but not so bad).

LGTMs with the test.

OK, now with the options set up.

(not blocking this PR) We need to follow up with js compiler folks about how /** @type {?} / differs from having no type annotation at all. Because the less we have to muck with the code the better. I rather have untyped mode not output any type annotations except move /* @export */ to the right place and some @supress to not have warnings.


Decide on further profiling runs

Now that additional AWS credits are available, decide which additional things to profile.
Options: Different CPU types (AMD, ARM (which), ...?) New OSs (OSX, Windows, RedHat, ... -- some possibly on ARM64) further network simulations, ...???
Input solicited: Additional options? Priorities?
Edit: Instance types: https://aws.amazon.com/ec2/instance-types/

In addition to doing a non-portability profiling run (#32), I think AMD and ARM are good; I don't know much about those CPU architectures. But I think an ARM with AES instructions, and possibly NEON, although I don't know if we have any ARM-guarded code.
Also would be good to have one more advanced Intel and one less advanced Intel.  I think AVX2 and AESNI are sufficiently old to be part of the less advanced baseline.  I don't know what specifically would constitute "more advanced Intel" however.
I don't think we should worry about Windows, macOS right now, we'd have to clean up the Windows build especially more before it's meaningful.

In addition to doing a non-portability profiling run (#32), I think AMD and ARM are good; I don't know much about those CPU architectures. But I think an ARM with AES instructions, and possibly NEON, although I don't know if we have any ARM-guarded code.
Also would be good to have one more advanced Intel and one less advanced Intel.  I think AVX2 and AESNI are sufficiently old to be part of the less advanced baseline.  I don't know what specifically would constitute "more advanced Intel" however.
I don't think we should worry about Windows, macOS right now, we'd have to clean up the Windows build especially more before it's meaningful.

So, the only addition worthwhile right now would be Apple M1. Any concrete timeline for when we want to make this available?

As per this suggestion consider adding (or switching?) to clang. Any preferences? Change? Add? Leave as-is?

Is the compiler (clang versus gcc) the relevant factor?  Or is it the libc?

The libc is the bigger issue. Musl is an odd choice for benchmarking on big x86-64 machines.

That choice was a coincidence (or "outgrowth" of the original choice for alpine docker images). I'm not hung up on it -- what would be your recommendation?

I'm OK with doing nothing.
But if you need just one more reason to switch to Debian (multiarch being the existing reason), then this is it. I don't have a good sense of the pros for Alpine.

I don't have a good sense of the pros for Alpine

I don't either (any more: It had been size, but after creating a size-optimized Debian container, we now know it's 509MB -- vs 493 for Alpine). Doing a test run now; let's see what that delivers.

Result: Steep performance drop on debian. Some trialing now why this may be so: gcc8 in debian much worse than gcc9 in alpine? Or should we rather use clang (which version) on debian? Any experiences what should be best? Or should we benchmark different compiler/version combinations (yet another alternative switch -- shudder)?

Answering my own question: clang (7) is definitely much better than gcc (8) on debian in the same VM: Example
Configuration info
==================
Target platform:  x86_64-Linux-4.14.193-149.317.amzn2.x86_64
Compiler:         gcc (8.3.0)
Compile options:  [-march=x86-64;-Werror;-Wall;-Wextra;-Wpedantic;-Wstrict-prototypes;-Wshadow;-Wformat=2;-Wfloat-equal;-Wwrite-strings;-O3;-fomit-frame-pointer;-fdata-sections;-ffunction-sections;-Wl,--gc-sections;-Wbad-function-cast]
OQS version:      0.6.0-dev
Git commit:       a04ef8d3ca14baa4d192874e1e4746b7edaf9fc5
OpenSSL enabled:  Yes (OpenSSL 1.1.1d  10 Sep 2019)
AES:              OpenSSL
SHA-2:            OpenSSL
SHA-3:            C
CPU exts active:  ADX AES AVX AVX2 AVX512 BMI1 BMI2 PCLMULQDQ POPCNT SSE SSE2 SSE3
Speed test
==========
Started at 2021-04-21 08:13:11
Operation                      | Iterations | Total time (s) | Time (us): mean | pop. stdev | CPU cycles: mean          | pop. stdev
------------------------------ | ----------:| --------------:| ---------------:| ----------:| -------------------------:| ----------:
FrodoKEM-640-SHAKE             |            |                |                 |            |                           |
keygen                         |       2786 |          3.000 |        1076.934 |     54.077 |                   2692112 |     135204
encaps                         |       2454 |          3.000 |        1222.581 |     62.326 |                   3056234 |     155798
decaps                         |       2382 |          3.000 |        1259.637 |    219.353 |                   3148905 |     548323
Ended at 2021-04-21 08:13:20

vs
Configuration info
==================
Target platform:  x86_64-Linux-4.14.193-149.317.amzn2.x86_64
Compiler:         clang (7.0.1 (tags/RELEASE_701/final))
Compile options:  [-march=native;-Werror;-Wall;-Wextra;-Wpedantic;-Wno-unused-command-line-argument;-O3;-fomit-frame-pointer;-Wbad-function-cast;-Wcast-qual;-Wnarrowing;-Wconversion]
OQS version:      0.6.0-dev
Git commit:       a04ef8d3ca14baa4d192874e1e4746b7edaf9fc5
OpenSSL enabled:  Yes (OpenSSL 1.1.1d  10 Sep 2019)
AES:              OpenSSL
SHA-2:            OpenSSL
SHA-3:            C
CPU exts active:  ADX AES AVX AVX2 AVX512 BMI1 BMI2 POPCNT SSE SSE2 SSE3

Speed test
==========
Started at 2021-04-21 08:13:56
Operation                      | Iterations | Total time (s) | Time (us): mean | pop. stdev | CPU cycles: mean          | pop. stdev
------------------------------ | ----------:| --------------:| ---------------:| ----------:| -------------------------:| ----------:
FrodoKEM-640-SHAKE             |            |                |                 |            |                           |
keygen                         |       3644 |          3.001 |         823.431 |     63.071 |                   2058326 |     157690
encaps                         |       3203 |          3.001 |         936.829 |     47.400 |                   2341866 |     118478
decaps                         |       3214 |          3.001 |         933.619 |     47.421 |                   2333920 |     118570
Ended at 2021-04-21 08:14:05

AND debian/clang7 is better than alpine/gcc9 in the same VM:
Configuration info
==================
Target platform:  x86_64-Linux-4.10.0-35-generic
Compiler:         gcc (9.3.0)
Compile options:  [-march=x86-64;-Werror;-Wall;-Wextra;-Wpedantic;-Wstrict-prototypes;-Wshadow;-Wformat=2;-Wfloat-equal;-Wwrite-strings;-O3;-fomit-frame-pointer;-fdata-sections;-ffunction-sections;-Wl,--gc-sections;-Wbad-function-cast]
OQS version:      0.6.0-dev
Git commit:       f1673911c3e42500fce8035b6ee4cbe3e5ebe913
OpenSSL enabled:  Yes (OpenSSL 1.1.1k  25 Mar 2021)
AES:              OpenSSL
SHA-2:            OpenSSL
SHA-3:            C
CPU exts active:  ADX AES AVX AVX2 AVX512 BMI1 BMI2 PCLMULQDQ POPCNT SSE SSE2 SSE3
Speed test
==========
Started at 2021-04-21 08:18:10
Operation                      | Iterations | Total time (s) | Time (us): mean | pop. stdev | CPU cycles: mean          | pop. stdev
------------------------------ | ----------:| --------------:| ---------------:| ----------:| -------------------------:| ----------:
FrodoKEM-640-SHAKE             |            |                |                 |            |                           |
keygen                         |       2612 |          3.001 |        1148.941 |     74.382 |                   2872139 |     185932
encaps                         |       2272 |          3.000 |        1320.445 |    193.779 |                   3300927 |     484340
decaps                         |       2384 |          3.000 |        1258.578 |     59.610 |                   3146271 |     149012
Ended at 2021-04-21 08:18:19

--> Will switch to debian/clang7 unless I hear protests.

Now doing all tests in the same VM and in the same docker image seems to indicate gcc8 is the better choice after all (iff/when getting the build options right). The below were built using cmake -GNinja [-DCMAKE_C_COMPILER=clang] -DOQS_MINIMAL_BUILD=ON -DOQS_KEM_DEFAULT="OQS_KEM_alg_frodokem_640_shake" ..
root@3f85e33700a8:/opt/liboqs# ./build-gcc-nooptions/tests/speed_kem FrodoKEM-640-SHAKE
Configuration info
==================
Target platform:  x86_64-Linux-4.14.193-149.317.amzn2.x86_64
Compiler:         gcc (8.3.0)
Compile options:  [-march=native;-Werror;-Wall;-Wextra;-Wpedantic;-Wstrict-prototypes;-Wshadow;-Wformat=2;-Wfloat-equal;-Wwrite-strings;-O3;-fomit-frame-pointer;-fdata-sections;-ffunction-sections;-Wl,--gc-sections;-Wbad-function-cast]
OQS version:      0.6.0-dev
Git commit:       a89e3ac581574d55494dea41fd1cc7b272603ee3
OpenSSL enabled:  Yes (OpenSSL 1.1.1d  10 Sep 2019)
AES:              OpenSSL
SHA-2:            OpenSSL
SHA-3:            C
CPU exts active:  ADX AES AVX AVX2 AVX512 BMI1 BMI2 POPCNT SSE SSE2 SSE3

Speed test
==========
Started at 2021-04-21 10:27:46
Operation                      | Iterations | Total time (s) | Time (us): mean | pop. stdev | CPU cycles: mean          | pop. stdev
------------------------------ | ----------:| --------------:| ---------------:| ----------:| -------------------------:| ----------:
FrodoKEM-640-SHAKE             |            |                |                 |            |                           |
keygen                         |       3534 |          3.000 |         849.015 |     38.758 |                   2122271 |      96884
encaps                         |       3074 |          3.001 |         976.207 |     41.688 |                   2440300 |     104253
decaps                         |       3132 |          3.001 |         958.065 |     41.184 |                   2395010 |     102961
Ended at 2021-04-21 10:27:55
root@3f85e33700a8:/opt/liboqs# ./build-clang-nooptions/tests/speed_kem FrodoKEM-640-SHAKE
Configuration info
==================
Target platform:  x86_64-Linux-4.14.193-149.317.amzn2.x86_64
Compiler:         clang (7.0.1 (tags/RELEASE_701/final))
Compile options:  [-march=native;-Werror;-Wall;-Wextra;-Wpedantic;-Wno-unused-command-line-argument;-O3;-fomit-frame-pointer;-Wbad-function-cast;-Wcast-qual;-Wnarrowing;-Wconversion]
OQS version:      0.6.0-dev
Git commit:       a89e3ac581574d55494dea41fd1cc7b272603ee3
OpenSSL enabled:  Yes (OpenSSL 1.1.1d  10 Sep 2019)
AES:              OpenSSL
SHA-2:            OpenSSL
SHA-3:            C
CPU exts active:  ADX AES AVX AVX2 AVX512 BMI1 BMI2 POPCNT SSE SSE2 SSE3

Speed test
==========
Started at 2021-04-21 10:28:37
Operation                      | Iterations | Total time (s) | Time (us): mean | pop. stdev | CPU cycles: mean          | pop. stdev
------------------------------ | ----------:| --------------:| ---------------:| ----------:| -------------------------:| ----------:
FrodoKEM-640-SHAKE             |            |                |                 |            |                           |
keygen                         |       3347 |          3.000 |         896.426 |     43.066 |                   2240769 |     107654
encaps                         |       3103 |          3.001 |         967.110 |     41.317 |                   2417564 |     103300
decaps                         |       3128 |          3.001 |         959.355 |     41.522 |                   2398240 |     103811
Ended at 2021-04-21 10:28:46
root@3f85e33700a8:/opt/liboqs#

Skylake figures are consistently lower (cmake -GNinja  [-DCMAKE_C_COMPILER=clang]  -DOQS_MINIMAL_BUILD=ON -DOQS_KEM_DEFAULT="OQS_KEM_alg_frodokem_640_shake" -DOQS_OPT_TARGET="skylake" ..):
Configuration info
==================
Target platform:  x86_64-Linux-4.14.193-149.317.amzn2.x86_64
Compiler:         gcc (8.3.0)
Compile options:  [-march=skylake;-Werror;-Wall;-Wextra;-Wpedantic;-Wstrict-prototypes;-Wshadow;-Wformat=2;-Wfloat-equal;-Wwrite-strings;-O3;-fomit-frame-pointer;-fdata-sections;-ffunction-sections;-Wl,--gc-sections;-Wbad-function-cast]
OQS version:      0.6.0-dev
Git commit:       a89e3ac581574d55494dea41fd1cc7b272603ee3
OpenSSL enabled:  Yes (OpenSSL 1.1.1d  10 Sep 2019)
AES:              OpenSSL
SHA-2:            OpenSSL
SHA-3:            C
CPU exts active:  ADX AES AVX AVX2 BMI1 BMI2 POPCNT SSE SSE2 SSE3

Speed test
==========
Started at 2021-04-21 10:34:33
Operation                      | Iterations | Total time (s) | Time (us): mean | pop. stdev | CPU cycles: mean          | pop. stdev
------------------------------ | ----------:| --------------:| ---------------:| ----------:| -------------------------:| ----------:
FrodoKEM-640-SHAKE             |            |                |                 |            |                           |
keygen                         |       2799 |          3.001 |        1071.997 |     45.797 |                   2679696 |     114480
encaps                         |       2416 |          3.000 |        1241.844 |    228.613 |                   3104405 |     571509
decaps                         |       2598 |          3.001 |        1155.180 |     54.186 |                   2887817 |     135453
Ended at 2021-04-21 10:34:42
Configuration info
==================
Target platform:  x86_64-Linux-4.14.193-149.317.amzn2.x86_64
Compiler:         clang (7.0.1 (tags/RELEASE_701/final))
Compile options:  [-march=skylake;-Werror;-Wall;-Wextra;-Wpedantic;-Wno-unused-command-line-argument;-O3;-fomit-frame-pointer;-Wbad-function-cast;-Wcast-qual;-Wnarrowing;-Wconversion]
OQS version:      0.6.0-dev
Git commit:       a89e3ac581574d55494dea41fd1cc7b272603ee3
OpenSSL enabled:  Yes (OpenSSL 1.1.1d  10 Sep 2019)
AES:              OpenSSL
SHA-2:            OpenSSL
SHA-3:            C
CPU exts active:  ADX AES AVX AVX2 BMI1 BMI2 POPCNT SSE SSE2 SSE3

Speed test
==========
Started at 2021-04-21 11:04:23
Operation                      | Iterations | Total time (s) | Time (us): mean | pop. stdev | CPU cycles: mean          | pop. stdev
------------------------------ | ----------:| --------------:| ---------------:| ----------:| -------------------------:| ----------:
FrodoKEM-640-SHAKE             |            |                |                 |            |                           |
keygen                         |       2556 |          3.001 |        1173.941 |    213.370 |                   2934637 |     533422
encaps                         |       2492 |          3.000 |        1203.919 |     48.526 |                   3009577 |     121321
decaps                         |       2490 |          3.000 |        1204.996 |     73.587 |                   3012288 |     183974
Ended at 2021-04-21 11:04:32

-> Back to square one: Why did the debian test runs seem slower than alpine? I'll redo everything...

I'm not sure why CMake passed -march=x86-64 in some of your runs. The only way that could happen with OQS_OPT_TARGET=auto is if OQS_DIST_BUILD=ON or CMAKE_CROSSCOMPILING=ON.

Ahh -- should we better use "skylake-avx512" than plain skylake (to get a fast, non-distributable, but well-defined --instead of -mnative-- build)? @jschanck any opinion?

Yes that's a good option for the machine that you're running tests on.

The only way that could happen with OQS_OPT_TARGET=auto is if OQS_DIST_BUILD=ON

The "plain" (i.e., not Reference nor Performance) config does have OQS_DIST_BUILD ON.

All items above seem to be agreed; I also did a performance run on an AWS C ("compute intensive tasks") instance (basically AMD EPYC), but the results were paltry. Thus I'd say we can close this issue. The one thing remaining is https://github.com/open-quantum-safe/liboqs/discussions/947 but that's tracked there. Please re-open or create new concrete issue if you'd like to propose extensions to profiling.


Trailing spaces on line 27 of eng.punc

I've not yet worked out whether eng.punc is used by the LSTM mode of tesseract, but I discovered that there are two trailing spaces on line 27 of this file, which might cause the occasional problem.

Which occasional problem are you referring to? If there is a problem, you can create a new traineddata file without those spaces and see whether that fixes the problem.

Link to line 27 in file eng.punc. The trailing spaces are also in eng.traineddata and can be found there in 17 lines.

LSTM and legacy mode use different punc components from the traineddata file, but both have the trailing spaces.

AFAICT, the space on each line indicates where "word characters" ("alphanumerics" for lack of a better term right now - non-punctuation symbols) are expected to appear.  So line 1 has a single space, indicating a sequence of [A-Z...] with no punctuation, and other lines have a trailing space to indicate initial punctuation followed by word characters.  Except for line 27, every line has precisely one space.  I hope that makes sense.
I haven't detected an actual problem yet, but any such problem would likely be very subtle.


tests: Remove custom yaml rules

schema v0.4.1 no longer lints line length. So we don't need custom yaml rules in the test to enable 180 line length.
Also the use in test_generate_data was incorrect since the argument must be the path to a file containing the yaml config rather than the config itself.

cc @hickeyma


CLOUD-52262 validate existing subnet's security group on Azure

@akanto @doktoric
The followings are checked from the existing security group before stack creation:
direction" -> "Inbound"
protocol" -> "Tcp" or "*"
access" -> "Allow"
destinationPortRange" -> "22", "443" or "22-443" like

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2049/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2050/

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2051/


vet linter fails when run against a directory with multiple packages

Two packages per directory is a common way of providing example_test.go for godoc examples, so that the examples can import the package as a user would:

https://github.com/gotestyourself/gotestyourself/tree/master/fs has both fs and fs_test package
https://github.com/decred/dcrutil/tree/master/bloom has both bloom and bloom_test packages

go vet fails on these directories because it is called with *.go and from the vet docs:

vets the files named, all of which must be in the same package.

Unfortunately the other argument options (directory, and package path) are not acceptable because they are recursive or don't support shadow (respectively).
The current workaround is to exclude example_test.go  however that means that the examples will not be linted at all.
The only solution I see to this problem is to fork go vet, add a --no-recursive flag, and use that fork as the vendoered linter for vet and vetshadow.

This may also be an issue with gotype once #348 is fixed, since it will be using the same partition strategy as vet.

Another workaround would be to change the partition strategy for vet to be single-directory using https://github.com/alecthomas/gometalinter/pull/352/commits/5d25f28f7104d71f71d91d3e8ba2f4b0da84bb29 (not yet merged).
This would only be appropriate on small projects where there are no nested package.

This seems to be the same problem as #218, the gist in the fourth comment exemplifies it.

Go Report Card is not only a fine and increasingly popular service, but also a proud user of Your versatile and powerful metalinter.
Suffering similar annoyances, here is what I found about underlying reasons.
@dnephin IMHO I think Your view on the issue seems to differ: You worry about partitioning.
I worried (mainly) about having or not having a workspace ($GOROOT set or not properly set) when tooling *.go files .
I'd be surprised to see go tools not being aware enough to handle a related *_test package in same package-dir properly. But I'd be happy to see You filing an issue.
Anyway. As I've said [there]: I'd humbly like to recommend:

Stay far away from non-standard use of package pointers when using go tools!
Mind You: packages (not files) are the important atomic things in go which result in artifacts / object code.

Can anyone verify if this is fixed?

@alecthomas it is not fixed, I just tried with my gotestyourself project. There are workarounds for some projects.
You can use PartitionStrategy: "single-directory" if there are no go files in the root of the project. vet does recursive for directories paths so it will include vendor/ and other ignored paths if there are go files in the root.
The default of PartitionStrategy: "files-by-package" works for most cases, but fails with this multi-package-in-single-dir case.
Using this config (command go vet instead of go tool vet):
Linters: {
      "vet": {
          "Command": "go vet",
          "PartitionStrategy": "packages"
      }
  },

seems to work for those two cases, but doesn't support -shadow.
So there is no argument that vet accepts which has the correct behaviour necessary for gometalinter and works in all cases.
I'm going to see about a fork of go vet that adds a -no-recurse flag

Opened #375 with a possible fix


Add github workflow for checking build status.

Wouldn't this also require Bazel to be installed in GitHub actions?

I think it comes preinstalled these days. You can check out my branch to
see that it runs ok.
On Tue, Nov 22, 2022, 7:52 PM Simon Horlick @.***>
wrote:

Wouldn't this also require Bazel to be installed in GitHub actions?
—
Reply to this email directly, view it on GitHub
https://github.com/simonhorlick/bazel_esp32/pull/6#issuecomment-1324515639,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAUO55DCQ6QBQTXUE5SPCTWJWIJTANCNFSM6AAAAAASFTYY54
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks for the PRs!


[QUESTION] Cannot figure out how to add widgets, my config is in JSON, docs are in YAML

Question
So, I tried adding the following code below to one of my sections via the edit config feature, but it doesn't persist or work.
      "widgets": [         {           "type": "weather",           "options": {             "apiKey": "xxxx",             "city": "Fairfax, VA",             "units": "imperial",             "hideDetails": false           },           "updateInterval": 3600         }       ],
I have that within "sections" after "items".
Category
Widgets
Please tick the boxes

[X] You are using a supported version of Dashy (check the first two digits of the version number)
[X] You've checked that this question hasn't already been raised
[X] You've checked the docs and troubleshooting guide
[X] You agree to the code of conduct

I have a similar issue, but not with widgets - I've been trying to enable authentication in my config, I write the config file, it rebuilds the app, and then it doesn't persist.
Also the config file is in JSON instead of YAML, not sure what is up with that. Using the docker-compose file provided in the repo along with:
docker-compose version 1.27.4, build 40524192
docker-py version: 4.3.1
CPython version: 3.7.7
OpenSSL version: OpenSSL 1.1.0l  10 Sep 2019

Question
So, I tried adding the following code below to one of my sections via the edit config feature, but it doesn't persist or work.
 "widgets": [ { "type": "weather", "options": { "apiKey": "xxxx", "city": "Fairfax, VA", "units": "imperial", "hideDetails": false }, "updateInterval": 3600 } ],
I have that within "sections" after "items".
Category
Widgets
Please tick the boxes

[x]  You are using a supported version of Dashy (check the first two digits of the version number)
[x]  You've checked that this question hasn't already been raised
[x]  You've checked the docs and troubleshooting guide
[x]  You agree to the code of conduct

I highly suggest using the yml config file or vs code server to edit the config the simply reboot the container, at best with portainer, may I ask how you set up the container?

I have a similar issue, but not with widgets - I've been trying to enable authentication in my config, I write the config file, it rebuilds the app, and then it doesn't persist.
Also the config file is in JSON instead of YAML, not sure what is up with that. Using the docker-compose file provided in the repo along with:
docker-compose version 1.27.4, build 40524192 docker-py version: 4.3.1 CPython version: 3.7.7 OpenSSL version: OpenSSL 1.1.0l 10 Sep 2019

Have you already tried editing the config through terminal? then it's plain yml and much easier, and I suggest asking either in discussions or make a separate issue, otherwise it will get a mess here.


How to compile Scintilla for both x86 and x64

Hi,
How do I compile Scintilla for both x86 and x64 ?
So I'll have two dlls, one for 32 bit and one for 64 bit.
I have Visual C++.
Thanks

ScintillaNet or Scintilla?  ScintillaNet is written in CSharp.  Scintilla itself ...
Readme says: Visual C++: nmake -f scite.mak
You can try to throw an email to<EMAIL_ADDRESS> Not sure, if he'll answer you.

I have the same problem
for the Scilexer.dll x86 i compile the makefile by mingw32-make.exe
and i don't know how to do to obtain x64

I have the same problem
for the Scilexer.dll x86 i compile the makefile by mingw32-make.exe
and i don't know how to do to obtain x64

There are two ways of doing it. The Visual Studio way is the easiest. I'll go over both.
Visual Studio:
Scintilla 4.x.x (current major version) uses C++ 17, meaning you will need Visual Studio 2017 and up to compile it. Our wrapper uses Scintilla 3.x.x. I'm not sure which version of C++ it used, so it may or may not work with older releases of Visual Studio.
You have a project file at scintilla\win32\SciLexer.vcxproj. Open it and you can easily change the target platform from the toolbar combobox.

The resulting binaries would be in:

scintilla\win32\<DebugOrRelease>\SciLexer.dll for 32-bit compilation; or
scintilla\win32\x64\<DebugOrRelease>\SciLexer.dll for 64-bit compilation.

MinGW:
Assuming you have the environment variable already set for MinGW, do:
cd scintilla\win32
mingw32-make

The "MinGW" project only supports 32-bit compilation. To compile as 64-bit you will need to download and use "MinGW-w64" instead.
MinGW
MinGW-w64

Thanks a lot for help


I want to work with Polkadot and Kusama. If anyone can train me on the coding side, I want to serve Dotsama.

Please ensure:

[x] I have read and understood the Fellowship Manifesto
[x] I understand that the Fellowship is for individuals who possess substantial expertise and experience regarding core Polkadot technologies.
[x] I understand that writing a (non-core) pallet or deploying a (non-system) parachain does not by itself fulfil the requirements for Fellowship membership.

Please replace the "___" with your information:

I expect my rank is at least 1 and at most 5.
I have been substantially involved with the Polkadot core technology set for 3 years.
My most substantial PR to a Polkadot core repository is: ___
My earliest non-trivial PR to a Polkadot core repository is: ___

Please consider using the Polkadot forums or social media for such proposals.


Fix build

Codecov Report

Merging #112 (5ccc4ba) into master (a079154) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##           master     #112   +/-   ##
=======================================
  Coverage   86.00%   86.00%
=======================================
  Files           9        9
  Lines         536      536
  Branches      106       99    -7
=======================================
  Hits          461      461
  Misses         62       62
  Partials       13       13


Improved rhat diagnostic

Submission Checklist

[ ] Run unit tests: ./runTests.py src/test/unit
[ ] Run cpplint: make cpplint
[ ] Declare copyright holder and open-source license: see below

Summary
Solving issue #3269
Changes in compute_potential_scale_reduction, based on Vehtari
Rhat computattion moved in rhat function
Added function rank_transform
Changed tests values to match new output
Intended Effect
rank_transform: Computes normalized average ranks for draws. Transforming them to normal scores using inverse normal transformation and a fractional offset.
rhat: computes rhat like before, the computatoinal part is just moved in a new function.
compute_potential_scale_reduction: copies draws in matrix object, then computes bulk rhat and tail rhat and returns the maximum
How to Verify
Compare the results with Arviz rhat function
arviz
Side Effects
Documentation
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
Aleks Stepančič
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Hi, @aleksgorica and welcome to the Stan project.
In terms of process, there should be an issue specifying the feature which this PR addresses.  Please add an issue.
I would also suggest not removing the old functionality but instead just adding new functionality for the ranked version.  That way, it won't break backward compatibility when it's added.
When it's ready to review for inclusion, please ping me and I can do it.

@aleksgorica this code all looks good! The only thing to fix now is the API. We want to keep all the old code and functions the same for backwards compatibility and have all of this in new functions. For instance compute_potential_scale_reduction() should have the same results as previously.
So the new code you have in compute_potential_scale_reduction_rank etc. is good and you can revert your changes to compute_potential_scale_reduction. New code in the future can use your compute_potential_scale_reduction_rank for the new estimate.
Once that is changed then I think you are good to merge!

@aleksgorica this code all looks good! The only thing to fix now is the API. We want to keep all the old code and functions the same for backwards compatibility and have all of this in new functions. For instance compute_potential_scale_reduction() should have the same results as previously.
So the new code you have in compute_potential_scale_reduction_rank etc. is good and you can revert your changes to compute_potential_scale_reduction. New code in the future can use your compute_potential_scale_reduction_rank for the new estimate.
Once that is changed then I think you are good to merge!

Okay, I hope I have understood correctly, I have just reverted the changes in the original non-rank functions to the previous code. However, I would like to know why that is necessary since I believe the new code yields the same results as the previous code according to the tests, and it is also a bit better written.

@bob-carpenter I rewrote this to dispatch to the old cold from the previous API
@aleksgorica there's one signature missing for split_potential_scale_reduction_rank so it matches the API of split_potential_scale_reduction. See below. Can you add that signature and have the current split_potential_scale_reduction signature call your new split_potential_scale_reduction_rank returning bulk rhat?
https://github.com/stan-dev/stan/blob/develop/src/stan/mcmc/chains.hpp#L219

Actually I reverted my old PR. Changing all the old functions to use the new one causes cmdstan tests to fail.
Let's have the _rank versions like you made here. We just need one last signature for
double split_potential_scale_reduction(
      const Eigen::Matrix<Eigen::VectorXd, Dynamic, 1>& samples)

Then we are good! After this is in we can then change cmdstan etc. to use the new ranked version. I think this is better because we need to change the output anyway to report back both the bulk and tail rhat

Actually I reverted my old PR. Changing all the old functions to use the new one causes cmdstan tests to fail.
Let's have the _rank versions like you made here. We just need one last signature for
double split_potential_scale_reduction(
      const Eigen::Matrix<Eigen::VectorXd, Dynamic, 1>& samples)

Then we are good! After this is in we can then change cmdstan etc. to use the new ranked version. I think this is better because we need to change the output anyway to report back both the bulk and tail rhat

Ok, but why should we even keep double split_potential_scale_reduction(       const Eigen::Matrix<Eigen::VectorXd, Dynamic, 1>& samples) or add double split_potential_scale_reduction_rank(       const Eigen::Matrix<Eigen::VectorXd, Dynamic, 1>& samples), when it is declared private and there are no written tests for the function and no known references? Would we break backward compatibility by removing the function?

Oh, your right I didn't see that it was a private member that is never called. Let's leave it for now but idt you need to write a rank version for that one.

@aleksgorica you should have received an email that adds you to the stan project :) clicking on the link in that email from github should then allow you to press the "merge pull request" button

Thank you all for accepting me to Stan project :). I had really great time working on the pull request. Also thank you @SteveBronder and @bob-carpenter for mentoring.
But github doesn't allow me to merge pull request.

I just verified that Steve gave you permission to merge.  Can you verify that works on your end by merging this?
Thanks, and welcome to the Stan team!

Did you click on the link in the email that was sent to you from github? After you click that and refresh the page you should have permission to merge

Yes, I clicked multiple times, now it always redirects me to https://github.com/stan-dev/stan. But it still does not allow me to merge. If I go to https://github.com/settings/organizations, there is written that I am outside collaborator on 1 repository for Stan.

Sorry you should have just gotten a new email that should give you the right permissions


Data processing

This PR implements the following:

Set up a data processing style from the config file
Integrate data processing utils from previous Chemlactica project
Add a sample for test training in the train_mini folder

@philippguevorguian Codes are updated, please look at them one more time.


refactor: change placeholder color

Is your request related to a problem? Please describe.

Describe the solution you'd like

Placeholder on mobile libraries should be in Content tertiary instead of content inactive

@GaspardMathon : If you're talking about placeHolder in Vitamin text fields, I am not sure this issue is relevant.
Here is a snippet of the code to put placeholder color which shows we use content tertiary (with a "disabled" opacity if the field is disabled) :
var placeholderColor: UIColor {
        if self == .disabled {
            return VitaminColor.Core.Content.tertiary.disabledColor()
        } else {
            return VitaminColor.Core.Content.tertiary
        }
    }


Upgrade antd version

you want to Upgrade umi ?

first upgrade-antd-pro-to-umi-3
https://umijs.org/zh-CN/guide/upgrade-antd-pro-to-umi-3
fix some problem in project

Do you mean this?


db-sync-node.Subscription:Error:56

[db-sync-node.Subscription:Error:56] [2020-10-13 03:10:27.34 UTC] [String "Connection Attempt Exception, destination LocalAddress {getFilePath = "/node-ipc/node.socket"} exception: Network.Socket.connect: <socket: 12>: does not exist (No such file or directory)",String "SubscriptionTrace"]
in the cardano-rest， but cardano-db-sync can't running. thanks
and my folder /node-ipc has nothing file

This message is expected initially, as the socket is created by cardano-node after a validation routine. Is this a new instance, or are you upgrading cardano-node ?

This message is expected initially, as the socket is created by cardano-node after a validation routine. Is this a new instance, or are you upgrading cardano-node ?

upgrading cardano-node

This message is expected initially, as the socket is created by cardano-node after a validation routine. Is this a new instance, or are you upgrading cardano-node ?

and has this err
SqlError {sqlState = "42703", sqlExecStatus = FatalError, sqlErrorMsg = "column block.epoch_slot_no does not exist", sqlErrorDetail = "", sqlErrorHint = ""}

You existing database and the code you are running are incompatible. The solution is to drop and restart the database and then sync from scratch.

postgres_1              | 2020-10-13 07:30:58.414 UTC [89] ERROR:  column block.epoch_slot_no does not exist at character 77

curl http://localhost:8100/api/blocks/pages
Something went wrong

Your existing database and the code you are running are incompatible. The solution is to drop and recreate the database and then sync from scratch.

how to drop database, i have been delete container and images

this is my command
NETWORK=mainnet docker-compose up

this problem is issue.
docker container rm XXX
docker image rm XXX
docker volume rm xxx
NETWORK=mainnet docker-compose up


Unify required question asterisk styling and fix screen-reader text

Description
Updates the styling of the asterisk that represents required questions. Styling of the program blocks now matches program summary view (both are red and have one space as padding now).
Also updated the screenreader text so the asterisk is read out (this behavior aligns with example #1 https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA2).
Release notes
Unify required question asterisk styling for applicants and fix screen-reader text.
Checklist
General

[ ] Added the correct label: < feature | bug | dependencies | infrastructure | ignore-for-release >
[ ] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

User visible changes

[ ] Wrote browser tests using the validateAccessibility method
[ ] Manually tested at 200% size
[ ] Manually evaluated tab order

New Features

[ ] Add new FeatureFlag env vars to server/conf/application.conf
[ ] Conditioned new functionality on a FeatureFlag
[ ] Wrote browser tests with the feature flag off and on, etc.

Issue(s) this completes

Thanks for the reviews!

Codecov Report

Merging #3911 (c0e0b73) into main (ed24b07) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##               main    #3911   +/-   ##
=========================================
  Coverage     80.81%   80.81%
- Complexity     2463     2465    +2
=========================================
  Files           298      298
  Lines          9683     9686    +3
  Branches        659      659
=========================================
+ Hits           7825     7828    +3
  Misses         1604     1604
  Partials        254      254

Impacted Files
Coverage Δ

server/app/services/applicant/AnswerData.java
100.00% <ø> (ø)

...applicant/ReadOnlyApplicantProgramServiceImpl.java
98.26% <100.00%> (+0.02%)
:arrow_up:

...services/applicant/question/ApplicantQuestion.java
97.64% <100.00%> (+0.02%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[Feature Request]: Download all the stats in pdf

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
After completing the issue #499 and #500 all the 6 status cards is completed with that i will create a new api which conatins all the necessary information about the style share webapp and he/she can download it in pdf and do the furthur task.
I will give the download button at the bottom of the sidebar.
Use Case
Admin analysis
Benefits
Admin overview
Add ScreenShots

after the cards i will wrap up with the admin panel
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@VaibhavArora314 I will do this after PR #499 and #500 so that reports are made !


noise dimension reduction technique

Hi,
Thank you for great works! It helps me to understand diffusion models better.
As far as I know, the noise is 512-dim. What's technique do you use to visualize these noises as a path?

Thank you!

Hi, thanks for the question!
We used the UMAP visualization technique to project the noise (or noisy image representation) to the 2D space. You can see more details about the visualization of image representation and its path in our paper: https://arxiv.org/abs/2305.03509.


[BUG] java.lang.ClassNotFoundException: io.netty.internal.tcnative.SSLContext

Describe the bug
I have started OpenSearch via Docker Compose and it fails with this error:
opensearch-node1       | [2024-11-11T11:43:04,610][INFO ][o.a.l.i.v.PanamaVectorizationProvider] [opensearch-node1] Java vector incubator API enabled; uses preferredBitSize=128; FMA enabled
opensearch-node1       | [2024-11-11T11:43:05,365][INFO ][o.o.s.s.t.SSLConfig      ] [opensearch-node1] SSL dual mode is disabled
opensearch-node1       | [2024-11-11T11:43:05,365][INFO ][o.o.s.OpenSearchSecurityPlugin] [opensearch-node1] OpenSearch Config path is /usr/share/opensearch/config
opensearch-node1       | [2024-11-11T11:43:05,461][WARN ][o.o.s.s.SslSettingsManager] [opensearch-node1] OpenSSL not available (this is not an error, we simply fallback to built-in JDK SSL) because of {}
opensearch-node1       | java.lang.ClassNotFoundException: io.netty.internal.tcnative.SSLContext
opensearch-node1       | 	at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:445) ~[?:?]
opensearch-node1       | 	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:593) ~[?:?]
opensearch-node1       | 	at java.base/java.net.FactoryURLClassLoader.loadClass(URLClassLoader.java:872) ~[?:?]
opensearch-node1       | 	at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526) ~[?:?]
opensearch-node1       | 	at java.base/java.lang.Class.forName0(Native Method) ~[?:?]
opensearch-node1       | 	at java.base/java.lang.Class.forName(Class.java:534) ~[?:?]
opensearch-node1       | 	at java.base/java.lang.Class.forName(Class.java:513) ~[?:?]
opensearch-node1       | 	at io.netty.handler.ssl.OpenSsl.<clinit>(OpenSsl.java:95) ~[netty-handler-4.1.114.Final.jar:4.1.114.Final]
opensearch-node1       | 	at org.opensearch.security.ssl.OpenSearchSecuritySSLPlugin$4.run(OpenSearchSecuritySSLPlugin.java:218) ~[opensearch-security-<IP_ADDRESS>.jar:<IP_ADDRESS>]
opensearch-node1       | 	at java.base/java.security.AccessController.doPrivileged(AccessController.java:319) ~[?:?]
opensearch-node1       | 	at org.opensearch.security.ssl.OpenSearchSecuritySSLPlugin.<init>(OpenSearchSecuritySSLPlugin.java:213) [opensearch-security-<IP_ADDRESS>.jar:<IP_ADDRESS>]
opensearch-node1       | 	at org.opensearch.security.OpenSearchSecurityPlugin.<init>(OpenSearchSecurityPlugin.java:318) [opensearch-security-<IP_ADDRESS>.jar:<IP_ADDRESS>]
opensearch-node1       | 	at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62) ~[?:?]
opensearch-node1       | 	at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502) ~[?:?]
opensearch-node1       | 	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:486) ~[?:?]
opensearch-node1       | 	at org.opensearch.plugins.PluginsService.loadPlugin(PluginsService.java:796) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.plugins.PluginsService.loadBundle(PluginsService.java:744) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.plugins.PluginsService.loadBundles(PluginsService.java:545) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.plugins.PluginsService.<init>(PluginsService.java:197) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.node.Node.<init>(Node.java:523) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.node.Node.<init>(Node.java:450) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:242) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:242) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:404) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:181) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:172) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:104) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138) [opensearch-cli-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.cli.Command.main(Command.java:101) [opensearch-cli-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:138) [opensearch-2.18.0.jar:2.18.0]
opensearch-node1       | 	at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:104) [opensearch-2.18.0.jar:2.18.0]

Related component
Other
To Reproduce

Install following https://opensearch.org/docs/latest/getting-started/quickstart/ following Docker Compose instructions
Run docker-compose up -d

Expected behavior
Should bring up the database.
Additional Details
Plugins
It's a fresh install, I haven't added new plugins.
Host/Environment (please complete the following information):

OS: MacOS
Version 14.7.1

Additional context
Using a MacBookPro M1.

This is a duplicate of https://github.com/opensearch-project/security/issues/4881


Fix small bug intro'd in PR #251

Note: Previously this change request was opened as https://github.com/johnynek/bazel-deps/pull/266, but I'm redoing it to avoid using my fork's master branch.

Extra conditional to fix bug intro'd by https://github.com/johnynek/bazel-deps/pull/251
This change was originally suggested by @Reflexe in the thread, but they didn't make a PR for it. https://github.com/johnynek/bazel-deps/compare/master...Reflexe:master

@johnynek happy to look at getting a test case for this.

I’ll merge and we can follow with another PR as needed.


How to setup a proxy with "brunch watch" ?

Description
I would like to setup a proxy when my server is running with "brunch watch" command. The aim is to allow my webapp to communicate with a REST API written with Java and running on localhost:8080
Today, my webapp is running on localhost:3333
When I call "GET api/myService" I would like the server to call "GET localhost:8080/api/myService" instead of "GET localhost:3333/api/myService"
How can I do that with brunch ?
Thanks for your help
package.json contents
    "devDependencies": {
        "brunch": "1.7.20",
        "javascript-brunch": "1.7.1",
        "css-brunch": "1.7.0",
        "less-brunch": "1.7.2",
        "auto-reload-brunch": "1.7.8",
        "uglify-js-brunch": "1.7.8",
        "clean-css-brunch": "1.7.2",
        "bower": "1.8.0"
    }

brunch config contents
exports.config =
    files:
        javascripts:
            joinTo:
                'js/app.js': /^app/
                'js/vendor.js': /^(bower_components|vendor)/

        stylesheets:
            joinTo:
                'css/app.css': /^(app)/
                'css/vendor.css': [
                    'bower_components/angular-datatables/dist/css/angular-datatables.css',
                    'bower_components/bootstrap/less/bootstrap.less'
                ]

        templates:
            joinTo:
                'css/app.css': /^(app)/

    server:
        port: 3333
        run: yes

If you are planning to handle this separately in your production environment, then you can follow the instructions here: http://brunch.io/docs/config#-server- to create a separate brunch-server.js file which you can use to serve up your public directory as well as proxy any other non-static requests through to your Java API. You might be able to use something like this to help: https://www.npmjs.com/package/static-proxy

Thanks for the tip, but it doesn't seem to work.
I'm able to serve my static files, and I can see in the logs that my API is proxified. But I have a HTTP400 error in my brower.
Do you have any idea why this doesn't work ?
Logs :
30 May 10:51:10 - info: starting custom server
static-proxy listening at http://<IP_ADDRESS>:3333
30 May 10:51:16 - warn: custom server taking a long time to start
30 May 10:51:16 - warn: **don't forget to invoke callback()**
Requesting url >>  http://localhost:8080\myApi\myService
host: localhost:8080/myApi/

If I call http://localhost:8080\myApi\myService by myself I have a correct answer.
In my webapp, I have an error on this : http://localhost:3333/api/myService
My brunch-server.js file is :
staticProxy = require('static-proxy');

exports.startServer = (port, path, callback) => {
    staticProxy('localhost:8080/myApi/', port, 'http', [path], true, transform);
};

My config.coffee file is :
exports.config =
    server:
        path: 'brunch-server.js'
        port: 3333
        run: yes

We actually don't support older Brunches. Try migrating to ^2, that should be a piece of cake.

Oh yea, I didn't even notice the Brunch 1 reference. That would be the first thing to try. Also if you aren't invoking callback in your server function, then don't include it as a parameter.


layers: remove unused func errorFunc

It is unused since commit 8c5cfc5ae25c ("Attempt to reduce memory usage
caused by enums.go strings.")
Signed-off-by: Tobias Klauser<EMAIL_ADDRESS>

Thanks for the contribution


Input Scan functionality

Scanning GPIO inputs and sending GPIO outputs for dashboard and for communication with LV system in HOME.

Test all LEDs on dashboard to make sure they trigger when they are supposed to (IMD, BMS, BSPD faults, motor temp, 7 segment displays).