Format code using 120 characters

This is a variant of #363 that uses the 120 character line width. The last commit uses the same code style but changes from 100 to 120 characters, so you can see that commit to compare just the line with change, or view the whole PR to see the difference from the existing style.

See #363


assets file sometimes are missing the v char.

Feature/enhancement description:

In the release section https://github.com/mbrlabs/Lorien/releases sometimes the asset files have a v next to the version and sometimes it is not.
It would make it easier for package managers to automatically pump the version without worrying if the v exist in this release or not.
May I ask if it would be possible to add Lorien_v0.5.0_Linux.tar.xz along side the Lorien_0.5.0_Linux.tar.xz file in the release?
Thank you,

Oops my bad, sorry! I don't want to upload an identical version just for the additional v though...becomes a bit confusing for users when there are two versions online with no apparent difference. And replacing it would break people's already existing setups.
So i promise to keep the Lorien_vX.Y.Z_Linux.tar.xz format in the next release ;)


Update README.MD

Update readme for refactor 1 (TC constructors) & 2 (deploymentStage & Name).

Fixed with commit: 3a866becd87911f937b33a13aa1777593398cc33.


Add runtime option to enable uart flow control

Add the function uart_enable_flow_control() which allows flow control to be explicitly enabled or disabled. By default flow control is on on the platforms which support it.

@mbed-bot: TEST

@mbed-bot: TEST

@mbed-bot: TEST


\newcommand text not rendered correctly

Description
The title of the paper is described in a \newcommand function in Latex. The HTML rendering only contains the syntax character \n and not the text ANCHOR
(Optional:) Please add any files, screenshots, or other information here.

(Required) What is this issue most closely related to? Select one.
Formula
Internal issue ID
f613e476-5053-4e0c-bebd-73b205e52435
Paper URL
https://arxiv.org/html/2404.10141v1
Browser
Safari/605.1.15
Device Type
Desktop

cross-referencing cause, tracked by https://github.com/brucemiller/LaTeXML/issues/1929


Issues with SecureStorage Android backup settings

Type of issue
Missing information
Description
The page seems to mention <exclude domain="sharedpref" path="${applicationId}.mauiessentials.xml"/> as a backup exclusion configuration.
But the settings are stored using the ${applicationId}.microsoft.maui.essentials.preferences.xml format. This mismatch causes the backup configuration in the documentation to not work properly.
The settings in the documentation also show an <include domain="sharedpref" path="."/> tag. Including a tag like this in the configuration can have some unintended side effects.
Adding 1 or more include tag to the configuration tells the backup system to backup nothing but the include tags.
Omitting the include tag and just adding the exclude tag (with the proper path) should be enough for SecureStorage purposes.
The configuration syntax also only applies to Android 11. The configuration syntax for Android 12 and up is missing.
https://developer.android.com/guide/topics/data/autobackup#include-exclude-android-12
Page URL
https://learn.microsoft.com/en-us/dotnet/maui/platform-integration/storage/secure-storage?view=net-maui-8.0&tabs=android
Content source URL
https://github.com/dotnet/docs-maui/blob/main/docs/platform-integration/storage/secure-storage.md
Document Version Independent Id
d8f68de5-3f19-8731-e8ec-c9a40f85b3e3
Article author
@davidbritch
Metadata

ID: d8f68de5-3f19-8731-e8ec-c9a40f85b3e3
Service: dotnet-mobile
Sub-service: dotnet-maui

I've added some context that may be useful for these docs or other doc pages: https://github.com/dotnet/maui/issues/18230#issuecomment-2021422788


Use transifex to handle internationalization?

Just wanted to get a feel if anyone was interested in using https://www.transifex.com/django-cas-ng/ as a way to translate the strings in the project? This web interface allows one to click on the origin string, and add a translation through the web interface. This should make it a little easier for people that do not want to dig into the code to still help translating.
I know this is a small project and most people doing the translations are also developers, so maybe this is not needed.

It is a great idea!
How easy to setup a transifex translation project ?
Can it be integrate with gitbub seamlessly ?

I think we can integrate the two, I will look more into soon.

It seems that people updating the PO files is probably easier than setting this up. I have not had time to deal with the integration, so I am closing this ticket for now.


Fix depth regular expression to math also very small numbers.

Sometimes depth value of e.g. 1.234e-5pt is returned by dvisvgm, in which case latex2svg returned None, causing problems for code that always assumed a number. This is fixed now.
Thanks for this great little tool, btw! Very useful.

Merged, thanks!


Added njk as html and md template options

Currently if you run the project, it processes the files as Liquid as it falls back to the default. By adding the two lines to .11ty, it'll process the files as Nunjucks files.

@httpsterio good catch. Thank you very much, looks good!


Suggest to add pytest package to the project when this framework is selected

Description
When invoke test generation and selects pytest as a 'Test framework' it's not automatically added to the project and user has to add it manually to the project.
Expected behavior
This is a minor enhancement is to suggest to automatically add pytest package to the project automatically when user selects pytest as a 'Test framework'.
For example see how it looks in Java project when user has no selected framework.

This also may warn user that she tries to use framework which is not installed in the project yet.

For some reason it still doesn't suggest to install pytest package, so I have to install it manually.


Downgrade NumPy used by HRNet

HRNet uses np.int which throws an error for NumPy >= 1.24, because its deprecation was finally expired. This PR creates an additional step during HRNet function image build, downgrading NumPy for a version < 1.24.
Motivation and context
Closes #5571.
How has this been tested?
I updated the CVAT locally and checked that I could successfully deploy HRNet on nuclio. After that, I tested the interactor on some images and everything is working as it should.
Checklist

[x] I submit my changes into the develop branch
[x] I have added a description of my changes into CHANGELOG file
I have updated the documentation accordingly
I have added tests to cover my changes
[x] I have linked related issues (read github docs)
I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

@nmanovic please, let me know if there is anything else needed for this PR


Navigating type structures?

We need a type structure walker.  They can become quite complex.

Enter and leave traps
Filter based on structure kind
Accept on enter structure filter
Accept on leave structure filter

I'm scaling this back to simply implementing forEachAugmentedStructureChild(), to bootstrap off of ts-morph's forEachStructureChild().

Holding open for documentation purposes now.


Fix build on -git

Tiny fix which uses the new class and title members introduced with the merge of the xdg-shell rewrite (https://github.com/hyprwm/Hyprland/commit/0cfdde3d1acbfbf698af17f6986fbc4d644214da). Fixes the build again on the latest commit and works as expected on my end.

bro you're so fast, thanks again


Rook update

Describe what this PR does
Provide some context for the reviewer
Is there anything that requires special attention
Do you have any questions?
Is the change backward compatible?
Are there concerns around backward compatibility?
Provide any external context for the change, if any.
For example:

Kubernetes links that explain why the change is required
CSI spec related changes/catch-up that necessitates this patch
golang related practices that necessitates this change

Related issues
Mention any github issues relevant to this PR. Adding below line
will help to auto close the issue once the PR is merged.
Fixes: #issue_number
Future concerns
List items that are not part of the PR and do not impact it's
functionality, but are work items that can be taken up subsequently.

You have added a commit with snapshot+clone support. Is that intentional? The PR template is also not updated with any details, you could mark this as a Draft until it is ready.

You have added a commit with snapshot+clone support. Is that intentional? The PR template is also not updated with any details, you could mark this as a Draft until it is ready.

sorry @nixpanic ..closing this one.


Index naming convention

Sort the list of fields.
Make it lower case
Concatenate with _ delimiter.
Prepend idx_ with the above concatenated word.

flags added.
  -indexPrefix="idx": prefix for creating Indexes
  -indexSuffix="": suffix for creating Indexes

Changes are merged to master.


Event object updated

The formatting of events will hopefully be a lot easier because the event responses are a lot more consistent and not preformatted per event type.

Display user that initiated in notification and simplify text to a phrase.

Closed for #1040


Improve chromecast disconnection logic

Description:
The latest cleanup to the cast platform introduced a weird bug where disconnecting from the old leader of a cast audio group was not handled correctly.
In particular, cast group leaders don't like accepting connections as long as there are open sockets to the old leader. In the old code, we would do a non-blocking disconnect and not join the socket client thread. So we tried connecting to the new leader before the old leader was disconnected. This prevented us from connecting to cast groups on every second leader change.
Apparently, async_will_remove_from_hass is not called on EVENT_HOMEASSISTANT_STOP. With the assumption that this seems to be intended (feels weird to me), I manually added a listener to the event bus.
If there's a 68.1 release, it might be good to maybe include this PR. It's not a huge code change and I spent the last few days testing this change.
Related issue (if applicable): fixes #13530
Example entry for configuration.yaml (if applicable):
media_player:
  - platform: cast

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

I think that registering a HOME_ASSISTANT_STOP event listener, like you did, is a better approach than using the removed from hass hook. Because cleanup during runtime is different than cleanup during shutdown.


aria-busy with tooltip unexpected rendering

Describe the issue
When tooltip and aria-busy are set on a button, the spinner looks funky
Current Behavior
A gif showing a button with aria-busy + tooltip and another button with aria-busy and no tooltip

Expected Behavior
I expected the spinner to appear inside the button
Reproduction

"busy" button with tooltip

    <button aria-busy="true" data-tooltip="hello world" data-placement="bottom" />

Environment
Pico CSS 1.5.11
Windows 10
Chrome Version 120.0.6099.130 (Official Build) (64-bit)
Thanks for making this awesome css framework

@Inveracity, I explored the problem, and it's impossible to fix, because both [data-tooltip] and [aria-busy] are using ::before.
The fallback will be cleaner in the v2. [aria-busy] wins.

Thanks for taking a look, much appreciated.
Excited for v2!

The fallback will be cleaner in the v2. [aria-busy] wins.

This does not seem to be the case. I want aria-busy to win over data-tooltip but that isn't happening and I end up with a weird absence where neither the tooltip or loader shows.
Buttons have data-tooltip by creation and when you click on one I add the aria-busy property until whatever needs to be done is complete. Currently I'm force to not use data-tooltip but is there a way to do this without the glitch?


provide button for firefox social

Hi,
would it be possible to add Firefox Social button ?
✚Add to Firefox social ⇐ Click on this button to add Shaarli to the "Share this page" button in Firefox.

See demo: http://shaarlidemo.tuxfamily.org/Shaarli/?do=tools (demo/demo)
Feature introduced with https://github.com/shaarli/Shaarli/commit/d33c5d4c3b9c70441391a08e8bcb2a8c639a4635
Thanks
J.

Hello,
I tried your demo but it doesn't work. Nothing happens when I press the button. However, the code is correct, according to Firefox Social API documentation. Is there something to activate in Firefox itself? I tried examples given by Mozilla (like GOAL.com) and it works.

yep, demo doesn't work.
it works on my shaarli.
1 advantage over bookmarklet: you bypass CRSF protections (e.g. on github)

I'm not against adding it but I need to make it work before. And it really sounds like the implementation of the current master branch of Shaarli doesn't work. What did you change on yours?

I did nothing for it to work on my shaarli. Are you using Firefox >= 29?

Yes I use the last version (39) and it's working fine for other Firefox Social API implementations given as examples on the documentation https://support.mozilla.org/en-US/kb/add-social-features-firefox-sidebar

So we found out that:

Your Shaarli instance must be hosted on an HTTPS (SSL/TLS secure connection) enabled server for Firefox Share to work. Firefox Share will not work over plain HTTP connections.

https://github.com/shaarli/Shaarli/issues/310

Great, thanks a lot for investigation. I'll implement it and disable the button if the instance is accessed via http rather than https.

committed: https://github.com/kalvn/Shaarli-Material/commit/7a9bc83fb70a1c6d0ea90f14f9d87e35a40e0a45


Add NVIC.ISER mapping

At present, the ISER register in NVIC is generated as follow:
        pub const ISER = @intToPtr(*volatile Mmio(32, packed struct {
            /// SETENA
            SETENA: u32,
        }), base_address + 0x0);

It would help a lot to parse the <interrupt> elements,
for example, if there is
      <interrupt>
        <name>RTC</name>
        <description>RTC global interrupt</description>
        <value>2</value>
      </interrupt>

there should be something like this:
        pub const ISER = @intToPtr(*volatile Mmio(32, packed struct {
            ..... (2 u1 fields here for padding (well, actually in practice it would be interrupt 0 and 1)...
            /// RTC
            RTC: u1,
        }), base_address + 0x0);

I just tried, with the following svd, and I have no ISER register anywhere in the generated file.
https://github.com/Pve88/stm32l0x1/blob/master/resources/STM32L0x1.svd

@kuon ah realized I added a small bug when I introduced IP register generation, it's all fixed now

It's fixed with master and my code is compiling. I still need to check that the code works properly but it seems ok.


Do not restart site if a function properly handles a cancellationToken on timeout

#655
Needs https://github.com/Azure/azure-webjobs-sdk/pull/836 before all tests will pass in CI.

My new tests were so close to being E2E that I just converted them. I'm not sure why I didn't do that originally.

Any more feedback or am I good to get this in?

🚢


Broken links in deploy-azure.md

At the end of "deploy-azure.md", there are links to additional documentation but none of the docs are in the repo.

./run-azure.md
../deploy/k8s/readme.md
../deploy/k8s/deploy.md

Solved in PR #35


How do you calculate Perfect predictions and Levenshtein distance

Hi.
I have some problems with the calculation of Perfect predictions and Levenshtein distance.
When you calculate the Perfect prediction and Levenshtein distance on 5 tokens, how do you treat the comments in datasets whose masked tokens are less then 5?

Hi,
Let me clarify your doubts.
Let's assume the model produces as output a recommendation featured by 10-word tokens. If the very first three tokens  (P0, P1, P2) match the first three tokens of the target (T0, T1, T2), then we have a Perfect-Prediction@3.
You can follow the same logic to compute perfect prediction featured by up to 15-word tokens.
Therefore, if we have a target featured by 4 tokens, we cannot compute PP and LD for more than these 4 tokens.
Thus, we compute PP@1, PP@2. PP@3 and PP@4. Same thing for the LD.
I hope this helps clarify your doubts.


Add komodo interest tx locktime validation

Add transaction lock time validation that the transaction has not been too long in mempool (See the komodo_validate_interest() in the base komodod repo for the algo)

This rule is needed to prevent cheating with tx locktime when it may be set too early to extend interest period

implemented in<PHONE_NUMBER>3b8f98a524e1409621065847573dd3


config(ticdc): decrease the default table memory quota to 10MiB

What problem does this PR solve?

Issue Number: close https://github.com/pingcap/tiflow/issues/7030
What is changed and how it works?
decrease the default table memory quota to 18MiB. 64MiB is too big, it will cause OOM.
Check List
Tests

Unit test

Questions
Will it cause performance regression or break compatibility?
No
Do you need to update user documentation, design documentation or monitoring documentation?
No
Release note
None

/merge

/run-verify

/run-engine-integration-test


API Review: Hooks & Beyond

Summary
With the introduction of hooks, the API could update to allow the components to meet current standards of where React is and where it's going.
Hooks example:
const stripe = useStripe(); // would replace injectStripe(Component)
...
render (
  return <CheckoutForm {...stripe} />;
)

For those who don't want to use HOC, you can provide a useStripe hook that accomplishes the same thing that injectStripe currently does that follows the useContext design.
Elements Component Update:
<Elements>
 {props => (
   <form>
       <CardNumberElement {...props} />
   </form>
  }
</Elements>

Another common design now to return functions to pass props to children. This could be an alternate to the hook if so desired. Formik and ReactSpring are good examples of doing this.
Motivation
As React continues to version into the future, the API should reflect common patterns that will be used.
Similar APIs

React@next
React Spring
Formik
The Platform

Alternatives
Do nothing and everything still works. Implement changes and everything still works. Win, win.
Scope
Depending on what is decided on can range from InjectStripe to Elements.
Risks
Don't think so, but humans can be dumb... 😂

Hi @caseybaggz
Thank you for this proposal.
I like the suggestion to add a useStripe hook that can be used instead of injectStripe. Based on my understanding of hooks API this should work nicely.
However, adding this is currently not very high priority for us, and we will likely wait until hook usage becomes a little more popular/wide-spread.
(Would you be interested in submitting a PR for this?)

@cweiss-stripe sure thing!

@cweiss-stripe, since we are updating, react in this future PR, we will need to upgrade some legacy code (specifically, context), I would recommend following the React pattern of having a "current" and "legacy" package which should be pretty easy.
Once we get this update in you just introduce a new package that is "react-stripe-elements-legacy" which just points to the previous release, branch, tag, or however you want it maintained?
This way it has wider support case for people on different versions without forcing errors in the console due to non-compatible versions?
Thoughts?

👍 I think injectStripe() is getting in the way of using React.forwardRef() in my case

I have a suggestion to add that would be very handy, too!
If you have multiple components across your app accessing the StripeJs script and you always need to make sure the script is loaded, you write something like this multiple times (using hooks already):
const [stripe, setStripe] = useState(null);

useEffect(() => {
  if (window.Stripe) {
    setStripe(window.Stripe(process.env.REACT_APP_STRIPE_API_KEY));
  } else {
    document.querySelector('#stripe-js').addEventListener('load', () => {
      setStripe(window.Stripe(process.env.REACT_APP_STRIPE_API_KEY));
    });
  }
}, []);

I would be awesome if it were already built-in like this:
import { useStripeJs } from 'react-stripe-elements';

const stripe = useStripeJs('#stripe-js', process.env.REACT_APP_STRIPE_API_KEY));

With the parameters being: useStripeJs(scriptElementId, stripeApiKey)

Hey guys 👋 with the community moving away from HOC and towards hooks, is there a roadmap item for implementing something similar to this proposal?

Looking for some useStripe hook as well!

I created a question on StackOverflow in hopes that someone can come up with an answer
https://stackoverflow.com/questions/57265054/how-to-create-usestripe-hook-for-react-stripe-elements

@AndreiRailean it's probably easiest to wait for it to be natively supported and hide the injectStripe in an internal component of yours. How will depend on how you're building things. For me I was using react-final-form and wanted to do everything in the submit handler so I just wrote a custom field that provides the stripe object as a form value.
If you absolutely want a useStripe hook. Because this library uses legacy context and I think the <Elements> component injects more, you'll need to add a wrapper component that you use everywhere you use <Elements>. e.g. <Elements><UseStripeHack>{/* ... */}</UseStripeHack></Elements>. UseStripeHack would basically be a component that creates a custom context, uses injectStripe and then passes the stripe prop on to the provider for that custom context, and then you'd have your own useStripe hook that uses that context.

Thanks @dantman. After a bunch of trial and error, i ended up with an approach similar to what you suggest. Here it is for stripe peeps to adopt and for others who need useStripe hook
// StripeHookProvider.jsx

import React, { useContext, createContext } from 'react'
import { injectStripe } from 'react-stripe-elements'

const Context = createContext()

export const useStripe = () => useContext(Context)

const HookProvider = ({ children, stripe }) => {
  return <Context.Provider value={stripe}>{children}</Context.Provider>
}

export default injectStripe(HookProvider)

Import and add StripeHookProvider to your component hierarchy like this. NOTE: because it relies on injectStripe, it must be a child of <Elements>
    <StripeProvider {...{ stripe }}>
      <Elements>
        <StripeHookProvider>
          <MyForm />
        </StripeHookProvider>
      </Elements>
    </StripeProvider>

then inside MyForm you use it like this
// MyForm.jsx
import { useStripe } from './StripeHookProvider'

const MyForm = () => {
  const stripe = useStripe()

  const handleSubmit = () => {
    const { setupIntent, error } = await stripe.handleCardSetup(secret ... // and so on
  }
}

This way you only need to do injectStripe in one place and it's tucked away neatly out of sight. As you can see from this code, it's not rocket science and should be no problem for stripe peeps to add to their code, hopefully eliminating <StripeHookProvider> altogether since they have a reference to stripe object somewhere in context.
I tried a bunch of approaches and this is the only one that worked. I didn't dig through stripe's JS code to see what happens, but stripe you get from injectStripe is the only thing you can use. The one you setup via window.Stripe(apiKey) is not the same and it won't work as it doesn't observe <Elements> properly so it doesn't know the state of the form.
Perhaps, the reason injectStripe has to be used on children of <Elements> is the same reason Stripe crew is taking a while to build this hook.

Perhaps, the reason injectStripe has to be used on children of <Elements> is the same reason Stripe crew is taking a while to build this hook.

Not really, it's not really an <Elements> problem. <Elements> can provide a context too. The issue is that #374 is a blocker. The library uses the legacy context API and you cannot use legacy context in hooks, so they absolutely have to move to the official context API before they can add even an optional a useStripe. But they want to keep supporting React 15.x which only has the obsolete context API.

It looks like react-stripe-elements is not using the context API. Is there a specific reason for it? It feels like by using the Context API, we would get the hook support for free.

If it's helpful to anyone, it is possible to convert from the legacy context API to the official context API (and therefore making it possible to use the useContext hook) by doing something like the following. (This skips over the loading of stripe.js, but feel free to ask if that part isn't clear.)
const StripeContext = createContext();

export function StripeHookProvider( { children, stripeJs } ) {
	const stripeData = {
		stripe: null, // This must be set inside the injected component
	};
	return (
		<StripeProvider stripe={ stripeJs }>
			<Elements>
				<StripeInjectedWrapper stripeData={ stripeData }>{ children }</StripeInjectedWrapper>
			</Elements>
		</StripeProvider>
	);
}

function StripeHookProviderInnerWrapper( { stripe, stripeData, children } ) {
	const updatedStripeData = { ...stripeData, stripe };
	return <StripeContext.Provider value={ updatedStripeData }>{ children }</StripeContext.Provider>;
}

const StripeInjectedWrapper = injectStripe( StripeHookProviderInnerWrapper );

Then you can pull in the Context with a Hook like this.
export function useStripe() {
	const stripeData = useContext( StripeContext );
	return stripeData || { stripe: null };
}

I'm still working on this, but I figured I would share it for those who are using Typescript and taking @sirbrillig advice/workaround:
import React, { createContext, useContext, ReactNode } from 'react';
import { StripeProvider, injectStripe, Elements } from 'react-stripe-elements';

const StripeContext = createContext({ stripe: {} as stripe.Stripe });

interface StripeWrapped {
  stripe: stripe.Stripe;
}

interface StripeHookProviderInnerWrapperProps {
  stripe?: stripe.Stripe;
  stripeData: StripeWrapped;
  children: ReactNode;
}

interface StripeHookProviderProps {
  apiKey: string;
  children: ReactNode;
}

export const StripeHookProvider: React.FC<StripeHookProviderProps> = (props) => {
  const stripeData = {
    stripe: {} as stripe.Stripe,
  };
  return (
    <StripeProvider apiKey={props.apiKey}>
      <Elements>
        <StripeInjectedWrapper stripeData={stripeData}>{props.children}</StripeInjectedWrapper>
      </Elements>
    </StripeProvider>
  );
};

const StripeHookProviderInnerWrapper = (props: StripeHookProviderInnerWrapperProps) => {
  const updatedStripeData = { stripe: { ...props.stripeData.stripe, ...props.stripe } };

  return <StripeContext.Provider value={updatedStripeData}>{props.children}</StripeContext.Provider>;
};

const StripeInjectedWrapper = injectStripe(StripeHookProviderInnerWrapper);

export const useStripe = () => {
  const stripeData = useContext(StripeContext);

  return stripeData || { stripe: {} as stripe.Stripe };
};

Thanks @jorgedavila25, works like a charm. Why are you returning returning the stripe.Stripe into stripeData instead of just returning stripe.Stripe?

Ah... he might have been following my example, and the reason I had done it was because you might want to provide additional properties in the hook. In the version I actually implemented I also have properties like isStripeLoading, and stripeErrorMessage. However, in this example, returning the stripe object itself is probably more elegant as you suggested.

I see :) Thank you both for the example, I was looking such.

@sirbrillig @jorgedavila25 I think it's better to include the hook provider inside a custom Elements component instead of wrapping your entire app, as that allows multiple Elements blocks to be used within the app. Here's how I'm doing it. Would be interested to hear if you see any issues with this method.
import React, { createContext, useState, useEffect, useContext } from 'react';
import {
  StripeProvider as StripeProviderInner,
  Elements as ElementsInner,
  injectStripe
} from 'react-stripe-elements';

export const StripeProvider = ({ children }) => {
  const [stripe, setStripe] = useState(null);

  const initializeStripe = () => {
    const key = process.env.STRIPE_PUBLISHABLE_KEY;
    setStripe(window.Stripe(key));
  };

  useEffect(() => {
    if (window.Stripe) {
      initializeStripe();
    } else {
      // Otherwise wait for Stripe script to load
      document.querySelector('#stripe-js').addEventListener('load', () => {
        initializeStripe();
      });
    }
  }, []);

  return <StripeProviderInner stripe={stripe}>{children}</StripeProviderInner>;
};

const HookContext = createContext();
const HookProvider = injectStripe(({ stripe, elements, children }) => {
  return (
    <HookContext.Provider value={[stripe, elements]}>
      {children}
    </HookContext.Provider>
  );
});

export const Elements = ({ children }) => {
  return (
    <ElementsInner>
      <HookProvider>{children}</HookProvider>
    </ElementsInner>
  );
};

export const useStripe = () => useContext(HookContext);

Can someone at Stripe give some feedback on the current bits of code and their feasibility of integration? There's a couple solid pieces of code here but it makes no sense for us all to maintain our own.
If the Stripe team will accept a pull request, let us know. If not, let us know.

I managed to get Stripe to work with hooks following the examples above but now I'm stuck on getting the element. In the example on the Readme it has:
const cardElement = this.props.elements.getElement('card');

How would I get the card using hooks?

Is this currently being planned/worked on? Having a  hook would be a very nice addition.

We have released https://github.com/stripe/react-stripe-js which supports hooks. Hopefully that new library answers your needs!

@hofman-stripe thanks. Is this a higher level library for react-stripe-elements or something?

React Stripe.js includes a new React API as well! Closing the issue here since it would be better to open there if there are still issues with the API.


HNC: Show right namespaces in kubectl hns tree --all-namespaces

Namespaces with conditions are missing in the kubectl hns tree --all-namespaces output.
Another improvement would be adding additional highlights on excluded namespaces in kubectl hns plugins to differentiate the namespaces.

Here's what I got currently:
$ kubectl get ns
NAME              STATUS        AGE
default           Active        22h
hnc-system        Active        21h
kube-node-lease   Active        22h
kube-public       Active        22h
kube-system       Active        22h
service-2         Terminating   47m
team-a            Active        47m
team-b            Active        47m

$ kubectl hns tree --all-namespaces  #### team-a and team-b are not listed here
default
hnc-system
kube-node-lease
kube-public
kube-system
service-2

Conditions:
1) ActivitiesHalted (ParentMissing): Parent "acme-org" does not exist

$ kubectl  hns tree team-a
team-a (1)

Conditions:
1) ActivitiesHalted (ParentMissing): Parent "acme-org" does not exist

$ kubectl hns tree team-b
team-b (1)

Conditions:
1) ActivitiesHalted (ParentMissing): Parent "acme-org" does not exist

multi-tenancy is very useful, I'd like to work on this.
/assign

@yiqigao217 since I am new here, would you please give me a hint where should I start?

Hi @FingerLiu  sorry for the late reply. The kubectl hns tree command are defined in https://github.com/kubernetes-sigs/multi-tenancy/blob/master/incubator/hnc/internal/kubectl/tree.go .
Please note only namespaces with conditions are not shown in the kubectl hns tree --all-namespaces.

It looks clear to me know, thanks.

Moved to https://github.com/kubernetes-sigs/hierarchical-namespaces/issues/15
/close


ldlogger always built 32 bit

Describe the bug
This was reported in #2095, but is still not fixed.
At line ~86 of the ld-logger Makefile, the executable is always built for 32 bit. This causes problems on 64 bit build hosts that do not have 32 bit dev environments installed.
CodeChecker version
Current master
To Reproduce
obtain current master
ensure build host does not have 32 bit dev environment
make package
observe quiet build failure in ldlogger
Expected behaviour
Build.
Desktop (please complete the following information)
Originally reported on OS: CentOS Linux release 7.3.1611 (Core)
I'm also experiencing the problem in Ubuntu 18.04
Additional context
Removing -m32 seems to solve the problem for me.

@crockeea thanks, for re-opening the ticket.
#2796 should fix the problem, I've tested it on my machine, could you check if it fixes the problem on your build environment too?

Looks like this fixes the bug for me. I appreciate the quick fix.
One thing that can still be improved, however: if I don't have 32-bit libraries and follow the build instructions in the README, (just make package), the build fails without a clear reason. Even though I figured this out when I first installed a week ago, I made the same mistake when checking your PR. It's easy to miss, and hard to debug.

@crockeea I've added some extra error messages, could you check if it works on your machine too and if they are clear enough?

Looks much nicer @gyorb. I got the error
"Failed to compile logger for 32bit and 64bit targets please check if
gcc-multilib is installed if both targets are needed or set the
BUILD_LOGGER_64_BIT_ONLY=YES environment variable for a 64bit only build.", which I think is adequately clear. I'd be happy to see this PR merged as-is.
I suppose for another ticket, you might consider whether the default should be BUILD_LOGGER_64_BIT_ONLY=YES, and make the user specify if they also want a 32-bit build. Do many people build this tool for 32-bit machines?

I would not change the default value yet, with the 32bit and 64bit mode more build environments can be logged (even mixed build environments).
But yes maybe later it can be changed to 64bit only by default.


Allow mounting a local working directory inside the container

Signed-off-by: John Else<EMAIL_ADDRESS>

Closing as superceded by https://github.com/xenserver/xenserver-build-env/pull/14


Plugin API: Type definition of configureWebpack does allow all possible keys

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
The type definition for configureWebpack in the plugins API currently uses the Configuration type from webpack:
https://github.com/facebook/docusaurus/blob/affca7a9a28b2b07716336bc3103b0ff434169df/packages/docusaurus-types/src/plugin.d.ts#L125-L130
When I return an object containing a devServer key, this works as expected, but I get a type error because the Configuration type doesn't contain a key called devServer.
As far as I can tell, from some very uninformed searching, I think the type that this should actually be is https://github.com/webpack/webpack/blob/main/declarations/WebpackOptions.d.ts#L797.
Reproducible demo
https://codesandbox.io/p/sandbox/docusaurus-webpack-devserver-tqk8nr
Steps to reproduce

Open docusaurus.config.ts
Uncomment either of the keys under plugins
Observe the type error against redirectPlugin

Expected behavior
I expect docusaurus.config.ts to type check successfully when devServer is configured
Actual behavior
I get a type error in docusaurus.config.ts when devServer is configured, yet it definitely behaves as I expect
Your environment
No response
Self-service

[X] I'd be willing to fix this bug myself.

Hmm, there's something weird in our setup, it seems Webpack now provdies its own type defs now but we keep using @types/webpack external defs.
Anyway, if you use "types": ["@types/webpack-dev-server"] in tsconfig.json it should fix your problem because those types add the required attribute through declaration merging:
declare module 'webpack' {
    interface Configuration {
        /**
         * Can be used to configure the behaviour of webpack-dev-server when
         * the webpack config is passed to webpack-dev-server CLI.
         */
        devServer?: WebpackDevServer.Configuration | undefined;
    }
}

Tested locally on our site and it works 👍


Add C WASM version of new runtime

The C program does not use the standard library, so does not need emscripten, wasi, or anything like that. runtime_wasm.reduce creates a new WebAssembly.Memory, and writes an array of pointers, whose indices are the RefId, and whose values are pointers to Term [ptr, len, mem...], which are written in order after the RefId array. Finally, an array of four uint32_t is reserved for the Result, then fm_reduce is called with a pointer to the Result struct, a pointer to the definitions table, the RefId of the term to reduce, and a pointer to the rest of the memory (where the reduction takes place).
Right now, the memory is expected to be big enough to hold the entire reduction. In the future, we could have a check before adding to the mem array, that if the end address would cross the 64k boundary (WASM page size), call __builtin_wasm_memory_grow to expand it.
The back array is implemented as a fixed size array on the stack of size 1024. This is probably okay since it is essentially the "stack" of the reduction. We could potentially even just write fm_reduce recursively, and just use the WASM stack, the size of which could be controlled at compile-time.
After reduction is finished, runtime_wasm.reduce returns an RtTerm using a Uint32Array over the WASM memory, and the term is decompiled using the existing code.

@michaelforney I'm midway through a big clean-up of the code base, so this will have conflicts. I'll try to resolve them Monday. Very impressive work!

Merged latest master changes.

Also pushed a 75-line recursive implementation here: https://github.com/moonad/Formality/compare/master...michaelforney:wasm-recursive

@michaelforney sorry for the delay, will merge it soon.

Closing as it was merged in another PR.


Option to not close UI when the process completes

Hi everyone. I am enjoying this extension very much so far, but I have one small issue. I am doing some cp and after the program is finished, the UI automatically closes, and I have to reopen the UI again. This is a minor inconvenience and I want to disable this feature. What's the config for this?

usually the autoclose is handled by eventlisteners. so, make sure not to copy the event listeners to your config which are about exiting, such as

dap.listeners.before.event_terminated['dapui_config']
dap.listeners.before.event_exited['dapui_config']

then the dapui will stay open


[googleapis] upgrade to v0.7.0 release

Describe the pull request
Updates the googleapis package to the v0.7.0 release.

What does your PR fix? Fixes issue #

N/A

Which triplets are supported/not supported? Have you updated the CI baseline?

Same as before.

Does your PR follow the maintainer guide?

Yes.

I cannot figure out why the windows-arm64 build broke, or where to find the logs to debug it. Can you point me in the right direction?

@coryan
Is this PR ready to be merged now?

@NancyLi1013 yes it is, thanks!


Update ci-mgmt.yaml config to match ci-mgmt actions

Needed for https://github.com/pulumi/ci-mgmt/issues/772 after https://github.com/pulumi/ci-mgmt/pull/818
Workflow updates otherwise fail: https://github.com/pulumi/pulumi-aws/pull/3430 because of a mismatch in upload/download artifact versions.

Didn't meant to merge without approval @iwahbe @guineveresaenger LMK if I should revert


Add examples to Syntax section

The section currently lacks examples. It would be very helpful to include some to illustrate both acceptable and unacceptable encoding.

Closing this in favor of specific examples to add.


Is it possible to get a class name of an anomaly on inference?

Hi, Denis!
Is it possible to get a class name of an anomaly on inference?
E.g.: fed to model an image of a tile with crack and after inference get a class name/class index of anomaly.
If so, then how to do it?

@volkov-maxim no, it is impossible with the current code. Your task is closer to supervised anomaly detection or, alternatively, you need to analyze density of anomaly data, which is not trivial


CB-1417. Add Redbeams to README along with light editing

The main README.md now describes how to run Redbeams locally. Many
other areas of the document were lightly edited for grammar,
capitalization, and updated URLs.

There are certainly more grammar edits that can be done to the README, but rather than try to pile them all in at once, I stopped at a certain point. I'd rather do a later review just for those than be stuck here in rounds of tweaks to the verbiage.


SSR303 does not work anymore

Hi Hank,
My Homey updated to 5.0.2 and the Secure app to 0.2.14 yesterday, since then my SSR303 does not work anymore.
I reinstalled the app, restarted Homey, disassociated the device from Z-Wave.
My SRT321 works fine.
I get this error when trying to include, the process works as usual.

Any ideas? Thanks.

Hi @DarrylvanderPeijl !
Thank you for reporting this.
Could you please generate a diagnostic report for the app, and I'll take a look. Maybe it can give some clues to what happens.
The main problem is that I only own a SRT321 myself, so I have no way to verify the other devices myself. So it is a little bit like stumbling in the dark.

Morning @hankolsen, Done.
ID: a27b7f43-90bd-4f30-b715-0f7cbf6c659a

Thank you!
Do you have a SRT323 aswell?
2021-03-24 03:32:17 [log] [ManagerDrivers] [srt323] SRT323Driver initialized
2021-03-24 03:32:55 [log] [ManagerDrivers] [srt321] [0] ZwaveDevice has been inited

No, only a SRT321

OK, that's odd. Homey seems to start the SRT323 Driver for some reason.
Maybe there is some misconfiguration that confuses SSR303 with SRT323.
I'll dig deeper.

I added some additional logging and updated the driver, would you mind trying out the test version (0.3.0) here: https://homey.app/a/com.horstmann/test/

Reproduced it:
789b43b3-1444-4486-97ac-0330296deb6e
Thanks!

Thank you!
I can't see anything interesting in the logs unfortunately.
But you're saying that it worked before?

I made some more updates, please try the lastest test version (v0.2.15)
https://homey.app/sv-se/app/com.horstmann/Secure-Meters/test/

It worked before yes, because since this week my heating does not work anymore ;-)
Will test later today

@hankolsen  Tried it a couple of times, some error.
0e359561-bd8c-4881-af5b-f9642bcd16c5

@DarrylvanderPeijl could you go to https://developer.athom.com/tools/zwave, scroll down a bit to the Log section and enable logs.
Please add the SSR303 as a Basic Z-wave, like your screenshot says.
And maybe maybe that log can reveal something.

[2021-03-26T19:06:51.706Z] Command[34] status: addNode, status: INTERVIEW_CC
[2021-03-26T19:06:51.744Z] Node[53]: sendData to COMMAND_CLASS_VERSION, params 0x1372
[2021-03-26T19:06:51.748Z] Command[35] end: sendData
[2021-03-26T19:06:51.750Z] Command[36] start: sendData
[2021-03-26T19:06:51.754Z] ProcessSendData[25]: To node: 53 with data: 0x861372 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T19:06:52.737Z] Command[36] end: sendData
[2021-03-26T19:06:52.769Z] Node[53]: Received application command for COMMAND_CLASS_VERSION, data: 0x147201
[2021-03-26T19:06:52.770Z] Node[53]: [COMMAND_CLASS_VERSION] {"Requested Command Class (Raw)":{"type":"Buffer","data":[114]},"Requested Command Class":114,"Command Class Version (Raw)":{"type":"Buffer","data":[1]},"Command Class Version":1}
[2021-03-26T19:06:52.772Z] Command[34] status: addNode, status: INTERVIEW_CC_1_OF_5
[2021-03-26T19:06:52.774Z] Node[53]: sendData to COMMAND_CLASS_VERSION, params 0x1386
[2021-03-26T19:06:52.775Z] Command[37] start: sendData
[2021-03-26T19:06:52.782Z] ProcessSendData[26]: To node: 53 with data: 0x861386 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T19:06:52.814Z] Command[37] end: sendData
[2021-03-26T19:06:52.828Z] Node[53]: Received application command for COMMAND_CLASS_VERSION, data: 0x148601
[2021-03-26T19:06:52.829Z] Node[53]: [COMMAND_CLASS_VERSION] {"Requested Command Class (Raw)":{"type":"Buffer","data":[134]},"Requested Command Class":134,"Command Class Version (Raw)":{"type":"Buffer","data":[1]},"Command Class Version":1}
[2021-03-26T19:06:52.832Z] Command[34] status: addNode, status: INTERVIEW_CC_2_OF_5
[2021-03-26T19:06:52.834Z] Node[53]: sendData to COMMAND_CLASS_VERSION, params 0x1340
[2021-03-26T19:06:52.835Z] Command[38] start: sendData
[2021-03-26T19:06:52.836Z] ProcessSendData[27]: To node: 53 with data: 0x861340 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T19:06:52.868Z] Command[38] end: sendData
[2021-03-26T19:06:52.881Z] Node[53]: Received application command for COMMAND_CLASS_VERSION, data: 0x144001
[2021-03-26T19:06:52.882Z] Node[53]: [COMMAND_CLASS_VERSION] {"Requested Command Class (Raw)":{"type":"Buffer","data":[64]},"Requested Command Class":64,"Command Class Version (Raw)":{"type":"Buffer","data":[1]},"Command Class Version":1}
[2021-03-26T19:06:52.885Z] Command[34] status: addNode, status: INTERVIEW_CC_3_OF_5
[2021-03-26T19:06:52.887Z] Node[53]: sendData to COMMAND_CLASS_VERSION, params 0x1325
[2021-03-26T19:06:52.888Z] Command[39] start: sendData
[2021-03-26T19:06:52.889Z] ProcessSendData[28]: To node: 53 with data: 0x861325 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T19:06:52.922Z] Command[39] end: sendData
[2021-03-26T19:06:52.935Z] Node[53]: Received application command for COMMAND_CLASS_VERSION, data: 0x142501
[2021-03-26T19:06:52.936Z] Node[53]: [COMMAND_CLASS_VERSION] {"Requested Command Class (Raw)":{"type":"Buffer","data":[37]},"Requested Command Class":37,"Command Class Version (Raw)":{"type":"Buffer","data":[1]},"Command Class Version":1}
[2021-03-26T19:06:52.939Z] Command[34] status: addNode, status: INTERVIEW_CC_4_OF_5
[2021-03-26T19:06:52.941Z] Node[53]: sendData to COMMAND_CLASS_VERSION, params 0x1320
[2021-03-26T19:06:52.942Z] Command[40] start: sendData
[2021-03-26T19:06:52.943Z] ProcessSendData[29]: To node: 53 with data: 0x861320 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T19:06:52.975Z] Command[40] end: sendData
[2021-03-26T19:06:52.988Z] Node[53]: Received application command for COMMAND_CLASS_VERSION, data: 0x142001
[2021-03-26T19:06:52.989Z] Node[53]: [COMMAND_CLASS_VERSION] {"Requested Command Class (Raw)":{"type":"Buffer","data":[32]},"Requested Command Class":32,"Command Class Version (Raw)":{"type":"Buffer","data":[1]},"Command Class Version":1}
[2021-03-26T19:06:52.992Z] Command[34] status: addNode, status: INTERVIEW_CC_5_OF_5
[2021-03-26T19:06:53.273Z] Command[34] status: addNode, status: INTERVIEW_MANUFACTURER_SPECIFIC
[2021-03-26T19:06:53.286Z] Node[53]: sendData to COMMAND_CLASS_MANUFACTURER_SPECIFIC, params 0x04
[2021-03-26T19:06:53.287Z] Command[41] start: sendData
[2021-03-26T19:06:53.289Z] ProcessSendData[30]: To node: 53 with data: 0x7204 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T19:06:53.319Z] Command[41] end: sendData
[2021-03-26T19:06:53.333Z] Node[53]: Received application command for COMMAND_CLASS_MANUFACTURER_SPECIFIC, data: 0x05005900030001
[2021-03-26T19:06:53.347Z] Node[53]: [COMMAND_CLASS_MANUFACTURER_SPECIFIC] {"Manufacturer ID":{"value":89,"name":"MFG_ID_HORSTMANN_CONTROLS_LIMITED"},"Product Type ID":{"value":3},"Product ID":{"value":1}}
[2021-03-26T19:06:53.352Z] Command[34] status: addNode, status: INTERVIEW_FIRMWARE_INFORMATION
[2021-03-26T19:06:53.353Z] Node[53]: sendData to COMMAND_CLASS_VERSION, params 0x11
[2021-03-26T19:06:53.355Z] Command[42] start: sendData
[2021-03-26T19:06:53.356Z] ProcessSendData[31]: To node: 53 with data: 0x8611 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T19:06:53.388Z] Command[42] end: sendData
[2021-03-26T19:06:53.402Z] Node[53]: Received application command for COMMAND_CLASS_VERSION, data: 0x1206024e0200
[2021-03-26T19:06:53.403Z] Node[53]: [COMMAND_CLASS_VERSION] {"Z-Wave Library Type (Raw)":{"type":"Buffer","data":[6]},"Z-Wave Library Type":6,"Z-Wave Protocol Version (Raw)":{"type":"Buffer","data":[2]},"Z-Wave Protocol Version":2,"Z-Wave Protocol Sub Version (Raw)":{"type":"Buffer","data":[78]},"Z-Wave Protocol Sub Version":78,"Application Version (Raw)":{"type":"Buffer","data":[2]},"Application Version":2,"Application Sub Version (Raw)":{"type":"Buffer","data":[0]},"Application Sub Version":0}
[2021-03-26T19:06:53.510Z] Command[34] end: addNode
[2021-03-26T19:06:53.755Z] Command[43] start: sendData
Dont think it contains anything useful... but maybe you find something :)

SRR303:
Driver | homey:manager:vdevice — zwavebasic
SRT321:
Driver | homey:app:com.horstmann — srt321

This line was interesting:
[2021-03-26T19:06:53.347Z] Node[53]: [COMMAND_CLASS_MANUFACTURER_SPECIFIC] {"Manufacturer ID":{"value":89,"name":"MFG_ID_HORSTMANN_CONTROLS_LIMITED"},"Product Type ID":{"value":3},"Product ID":{"value":1}}

According to the manual, the SSR303 should be:
Product Type ID = 0x0003 Product ID = 0x0005 (SSR 303)
So there seems to be a mismatch of Product Id

This one seems to be productId 1
https://products.z-wavealliance.org/products/126.
Is this the one you have?

@DarrylvanderPeijl Please try v0.3.2:  https://homey.app/sv-se/app/com.horstmann/Secure-Meters/test/

We're getting somewhere.. new error:
status.missing_multiChannelNodeId_1_on_node
Report:
8076e593-efde-487e-9dda-4d1a56564d6e
Log:
[2021-03-26T20:09:31.796Z] Command[433] start: addNode
[2021-03-26T20:09:31.811Z] Command[433] status: addNode, status: ADD_NODE_STATUS_LEARN_READY
[2021-03-26T20:09:33.334Z] Command[433] status: addNode, status: ADD_NODE_STATUS_NODE_FOUND
[2021-03-26T20:09:33.559Z] Command[433] status: addNode, status: ADD_NODE_STATUS_ADDING_SLAVE
[2021-03-26T20:09:37.685Z] Command[433] status: addNode, status: ADD_NODE_STATUS_PROTOCOL_DONE
[2021-03-26T20:09:37.755Z] Command[433] status: addNode, status: ADD_NODE_STATUS_DONE
[2021-03-26T20:09:38.716Z] Node[17]: Received application command for COMMAND_CLASS_WAKE_UP, data: 0x07
[2021-03-26T20:09:38.716Z] Node[17]: [COMMAND_CLASS_WAKE_UP] {}
[2021-03-26T20:09:38.717Z] Node[17]: Marked as online
[2021-03-26T20:09:38.730Z] Node[17]: [COMMAND_CLASS_BATTERY] [BATTERY_GET] {"type":"Buffer","data":[]}
[2021-03-26T20:09:38.731Z] Node[17]: Received application command for COMMAND_CLASS_WAKE_UP, data: 0x07
[2021-03-26T20:09:38.732Z] Node[17]: [COMMAND_CLASS_WAKE_UP] {}
[2021-03-26T20:09:38.894Z] Command[433] status: addNode, status: INTERVIEW_CC
[2021-03-26T20:09:38.916Z] Node[56]: sendData to COMMAND_CLASS_VERSION, params 0x1372
[2021-03-26T20:09:38.917Z] Command[434] start: sendData
[2021-03-26T20:09:38.919Z] ProcessSendData[383]: To node: 56 with data: 0x861372 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T20:09:38.936Z] Node[17]: [COMMAND_CLASS_THERMOSTAT_SETPOINT] [THERMOSTAT_SETPOINT_GET] {"type":"Buffer","data":[1]}
[2021-03-26T20:09:38.937Z] Node[17]: [COMMAND_CLASS_THERMOSTAT_MODE] [THERMOSTAT_MODE_GET] {"type":"Buffer","data":[]}
[2021-03-26T20:09:38.938Z] Node[17]: [COMMAND_CLASS_SWITCH_MULTILEVEL] [SWITCH_MULTILEVEL_GET] {"type":"Buffer","data":[]}
[2021-03-26T20:09:38.949Z] Command[434] end: sendData
[2021-03-26T20:09:38.962Z] Node[56]: Received application command for COMMAND_CLASS_VERSION, data: 0x147201
[2021-03-26T20:09:38.963Z] Node[56]: [COMMAND_CLASS_VERSION] {"Requested Command Class (Raw)":{"type":"Buffer","data":[114]},"Requested Command Class":114,"Command Class Version (Raw)":{"type":"Buffer","data":[1]},"Command Class Version":1}
[2021-03-26T20:09:38.966Z] Command[433] status: addNode, status: INTERVIEW_CC_1_OF_5
[2021-03-26T20:09:38.968Z] Node[56]: sendData to COMMAND_CLASS_VERSION, params 0x1386
[2021-03-26T20:09:38.969Z] Command[435] start: sendData
[2021-03-26T20:09:38.971Z] ProcessSendData[384]: To node: 56 with data: 0x861386 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T20:09:39.003Z] Command[435] end: sendData
[2021-03-26T20:09:39.016Z] Node[56]: Received application command for COMMAND_CLASS_VERSION, data: 0x148601
[2021-03-26T20:09:39.017Z] Node[56]: [COMMAND_CLASS_VERSION] {"Requested Command Class (Raw)":{"type":"Buffer","data":[134]},"Requested Command Class":134,"Command Class Version (Raw)":{"type":"Buffer","data":[1]},"Command Class Version":1}
[2021-03-26T20:09:39.019Z] Command[433] status: addNode, status: INTERVIEW_CC_2_OF_5
[2021-03-26T20:09:39.021Z] Node[56]: sendData to COMMAND_CLASS_VERSION, params 0x1340
[2021-03-26T20:09:39.022Z] Command[436] start: sendData
[2021-03-26T20:09:39.023Z] ProcessSendData[385]: To node: 56 with data: 0x861340 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T20:09:39.055Z] Command[436] end: sendData
[2021-03-26T20:09:39.069Z] Node[56]: Received application command for COMMAND_CLASS_VERSION, data: 0x144001
[2021-03-26T20:09:39.070Z] Node[56]: [COMMAND_CLASS_VERSION] {"Requested Command Class (Raw)":{"type":"Buffer","data":[64]},"Requested Command Class":64,"Command Class Version (Raw)":{"type":"Buffer","data":[1]},"Command Class Version":1}
[2021-03-26T20:09:39.072Z] Command[433] status: addNode, status: INTERVIEW_CC_3_OF_5
[2021-03-26T20:09:39.074Z] Node[56]: sendData to COMMAND_CLASS_VERSION, params 0x1325
[2021-03-26T20:09:39.075Z] Command[437] start: sendData
[2021-03-26T20:09:39.077Z] ProcessSendData[386]: To node: 56 with data: 0x861325 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T20:09:39.109Z] Command[437] end: sendData
[2021-03-26T20:09:39.122Z] Node[56]: Received application command for COMMAND_CLASS_VERSION, data: 0x142501
[2021-03-26T20:09:39.123Z] Node[56]: [COMMAND_CLASS_VERSION] {"Requested Command Class (Raw)":{"type":"Buffer","data":[37]},"Requested Command Class":37,"Command Class Version (Raw)":{"type":"Buffer","data":[1]},"Command Class Version":1}
[2021-03-26T20:09:39.129Z] Command[433] status: addNode, status: INTERVIEW_CC_4_OF_5
[2021-03-26T20:09:39.131Z] Node[56]: sendData to COMMAND_CLASS_VERSION, params 0x1320
[2021-03-26T20:09:39.132Z] Command[438] start: sendData
[2021-03-26T20:09:39.134Z] ProcessSendData[387]: To node: 56 with data: 0x861320 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T20:09:39.166Z] Command[438] end: sendData
[2021-03-26T20:09:39.180Z] Node[56]: Received application command for COMMAND_CLASS_VERSION, data: 0x142001
[2021-03-26T20:09:39.180Z] Node[56]: [COMMAND_CLASS_VERSION] {"Requested Command Class (Raw)":{"type":"Buffer","data":[32]},"Requested Command Class":32,"Command Class Version (Raw)":{"type":"Buffer","data":[1]},"Command Class Version":1}
[2021-03-26T20:09:39.183Z] Command[433] status: addNode, status: INTERVIEW_CC_5_OF_5
[2021-03-26T20:09:39.548Z] Command[433] status: addNode, status: INTERVIEW_MANUFACTURER_SPECIFIC
[2021-03-26T20:09:39.567Z] Node[56]: sendData to COMMAND_CLASS_MANUFACTURER_SPECIFIC, params 0x04
[2021-03-26T20:09:39.569Z] Command[439] start: sendData
[2021-03-26T20:09:39.570Z] ProcessSendData[388]: To node: 56 with data: 0x7204 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T20:09:39.599Z] Command[439] end: sendData
[2021-03-26T20:09:39.613Z] Node[56]: Received application command for COMMAND_CLASS_MANUFACTURER_SPECIFIC, data: 0x05005900030001
[2021-03-26T20:09:39.623Z] Node[56]: [COMMAND_CLASS_MANUFACTURER_SPECIFIC] {"Manufacturer ID":{"value":89,"name":"MFG_ID_HORSTMANN_CONTROLS_LIMITED"},"Product Type ID":{"value":3},"Product ID":{"value":1}}
[2021-03-26T20:09:39.626Z] Command[433] status: addNode, status: INTERVIEW_FIRMWARE_INFORMATION
[2021-03-26T20:09:39.628Z] Node[56]: sendData to COMMAND_CLASS_VERSION, params 0x11
[2021-03-26T20:09:39.629Z] Command[440] start: sendData
[2021-03-26T20:09:39.630Z] ProcessSendData[389]: To node: 56 with data: 0x8611 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T20:09:39.663Z] Command[440] end: sendData
[2021-03-26T20:09:39.676Z] Node[56]: Received application command for COMMAND_CLASS_VERSION, data: 0x1206024e0200
[2021-03-26T20:09:39.677Z] Node[56]: [COMMAND_CLASS_VERSION] {"Z-Wave Library Type (Raw)":{"type":"Buffer","data":[6]},"Z-Wave Library Type":6,"Z-Wave Protocol Version (Raw)":{"type":"Buffer","data":[2]},"Z-Wave Protocol Version":2,"Z-Wave Protocol Sub Version (Raw)":{"type":"Buffer","data":[78]},"Z-Wave Protocol Sub Version":78,"Application Version (Raw)":{"type":"Buffer","data":[2]},"Application Version":2,"Application Sub Version (Raw)":{"type":"Buffer","data":[0]},"Application Sub Version":0}
[2021-03-26T20:09:39.732Z] Command[433] end: addNode
[2021-03-26T20:09:42.218Z] Node[17]: [COMMAND_CLASS_WAKE_UP] [WAKE_UP_NO_MORE_INFORMATION] {"type":"Buffer","data":[]}
[2021-03-26T20:09:42.218Z] Node[17]: sendData to COMMAND_CLASS_WAKE_UP, params 0x08
[2021-03-26T20:09:42.220Z] Command[441] start: sendData
[2021-03-26T20:09:42.221Z] ProcessSendData[390]: To node: 17 with data: 0x8408 and txOptions: AUTO_ROUTE,ACK,EXPLORE
[2021-03-26T20:09:47.232Z] ProcessSendData[390]: Error: request_timeout

Thanks!
New test version available, v0.3.2!

It is added!
But it doesn't respond to any actions. I don't see anything in the log happening when turning on/off.
88d6fc16-f47c-4c44-a93e-265c48e3b280

Are you trying to turn it on/off from the app or from the actual device?

From the app, physical device buttons are working.

Hi @hankolsen , don't think you are receiving my emails.
I'm on version 0.4.0, the physical buttons work but from the app it does nothing.
Trace:
50921801-fb4b-49f9-84ae-d4918bf265d9


Loadbalancer dublicates deploy of k8s objects when > 2 nodes

When provitioning more then one loadbalancer, the script will create rbac objects.
This should only be done on the first node.

Could be solved by doing a simple
if [ $(hostname) == "k8s-worker-1" ]; then
Deploy k8s objects here
fi

output :
==> k8s-loadbalancer-2: Creating RBAC for traefik...
==> k8s-loadbalancer-2: Error from server (AlreadyExists): error when creating "/root/traefik.rbac.yaml": namespaces "traefik" already exists
==> k8s-loadbalancer-2: Error from server (AlreadyExists): error when creating "/root/traefik.rbac.yaml": serviceaccounts "traefik-service-account" already exists
==> k8s-loadbalancer-2: Error from server (AlreadyExists): error when creating "/root/traefik.rbac.yaml": clusterroles.rbac.authorization.k8s.io "traefik-cluster-role" already exists
==> k8s-loadbalancer-2: Error from server (AlreadyExists): error when creating "/root/traefik.rbac.yaml": clusterrolebindings.rbac.authorization.k8s.io "traefik-cluster-role-binding" already exists
==> k8s-loadbalancer-2: Getting token and ca.crt for Traefik from api-server...
==> k8s-loadbalancer-2: Created symlink /etc/systemd/system/multi-user.target.wants/traefik.service → /etc/systemd/system/traefik.service.
==> k8s-loadbalancer-2: Redirecting to /bin/systemctl start traefik.service


collection processing: status

For my QC workflow to monitor the input of our article data into GBIF, I would like to know, whether there is a way I can see that a particular article is in the queue to be processed, and how long it might take to be processed under normal circumstances.
I like the fact that the articles can be searched by using their DOI, e.g
DOI: 10.5852/ejt.2019.512
GBIF query: https://www.gbif.org/search?q="10.5852/ejt.2019.512"

In most cases, a new dataset will very soon appear in the list here: https://registry.gbif.org/monitoring/ingestion or as an API call at https://api.gbif.org/v1/dataset/process/running . The length of that list and the order of start times give an idea of how long it will take, but we don't provide an estimate — it can take several hours for the largest datasets to be processed, but just seconds for the typical Plazi dataset.  The queue of DWCA datasets is processed in order (first come first served), and occurrences and names are processed separately. (You may see BioCASe / DIGIR datasets being processed in parallel, these are in a different queue.)
Occasionally, we suspend normal processing. If it's for more than a few minutes we may put a message on https://www.gbif.org/health. Depending why we need to suspend ingestion, it might be that nothing appears in the lists above. (I think the datasets would appear in https://api.gbif.org/v1/dataset/process/dwca/pending but there's no web page for this — in normal circumstances, datasets are only in that queue for a few seconds at most.)
When ingestion is complete, you can see that on https://registry.gbif.org/dataset/7887c2f9-a00f-484e-93c2-595204b8e28d/process or with the API call https://api.gbif.org/v1/dataset/7887c2f9-a00f-484e-93c2-595204b8e28d/process?limit=5


ERROR: /home/developer/tensorflow/tensorflow/BUILD:652

:1: Executing genrule //tensorflow:tf_python_api_gen_v1 failed (Exit 1)
Traceback (most recent call last):
File "/home/developer/.cache/bazel/_bazel_developer/6acbce31a4e8077fc84a239074e8eda3/execroot/org_tensorflow/bazel-out/host/bin/tensorflow/create_tensorflow.python_api_1.runfiles/org_tensorflow/tensorflow/python/tools/api/generator/create_python_api.py", line 27, in
from tensorflow.python.tools.api.generator import doc_srcs
File "/home/developer/.cache/bazel/_bazel_developer/6acbce31a4e8077fc84a239074e8eda3/execroot/org_tensorflow/bazel-out/host/bin/tensorflow/create_tensorflow.python_api_1.runfiles/org_tensorflow/tensorflow/python/init.py", line 70, in
from tensorflow.python.framework.framework_lib import *  # pylint: disable=redefined-builtin
File "/home/developer/.cache/bazel/_bazel_developer/6acbce31a4e8077fc84a239074e8eda3/execroot/org_tensorflow/bazel-out/host/bin/tensorflow/create_tensorflow.python_api_1.runfiles/org_tensorflow/tensorflow/python/framework/framework_lib.py", line 52, in
from tensorflow.python.framework.importer import import_graph_def
File "/home/developer/.cache/bazel/_bazel_developer/6acbce31a4e8077fc84a239074e8eda3/execroot/org_tensorflow/bazel-out/host/bin/tensorflow/create_tensorflow.python_api_1.runfiles/org_tensorflow/tensorflow/python/framework/importer.py", line 27, in
from tensorflow.python.framework import function
File "/home/developer/.cache/bazel/_bazel_developer/6acbce31a4e8077fc84a239074e8eda3/execroot/org_tensorflow/bazel-out/host/bin/tensorflow/create_tensorflow.python_api_1.runfiles/org_tensorflow/tensorflow/python/framework/function.py", line 36, in
from tensorflow.python.ops import resource_variable_ops
File "/home/developer/.cache/bazel/_bazel_developer/6acbce31a4e8077fc84a239074e8eda3/execroot/org_tensorflow/bazel-out/host/bin/tensorflow/create_tensorflow.python_api_1.runfiles/org_tensorflow/tensorflow/python/ops/resource_variable_ops.py", line 38, in
from tensorflow.python.ops import variables
File "/home/developer/.cache/bazel/_bazel_developer/6acbce31a4e8077fc84a239074e8eda3/execroot/org_tensorflow/bazel-out/host/bin/tensorflow/create_tensorflow.python_api_1.runfiles/org_tensorflow/tensorflow/python/ops/variables.py", line 20, in
import enum  # pylint: disable=g-bad-import-order
ImportError: No module named enum
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 1418.730s, Critical Path: 243.25s
INFO: 9922 processes: 9922 local.
FAILED: Build did NOT complete successfully
https://github.com/tensorflow/tensorflow/tree/master/tools/tf_env_collect.sh
You can obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the problem
Describe the problem clearly here. Be sure to convey here why it's a bug in TensorFlow or a feature request.
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.

@phalexo Can you please describe the problem clearly.

Ubuntu 16.04, building TF from source with CUDA, MPI, NCCL 2.2 support. I modified the code with ToString proposed fix (not sure it has been committed into the master yet). So after that error was no more I ran into this build error. I've tried bazel 0.15, 0.16
INFO: From Compiling external/llvm/lib/Transforms/Scalar/JumpThreading.cpp:
external/llvm/lib/Transforms/Scalar/JumpThreading.cpp: In member function 'void llvm::JumpThreadingPass::UpdateBlockFreqAndEdgeWeight(llvm::BasicBlock*, llvm::BasicBlock*, llvm::BasicBlock*, llvm::BasicBlock*)':
external/llvm/lib/Transforms/Scalar/JumpThreading.cpp:2165:61: warning: '((void)& BBSuccFreq +16)' may be used uninitialized in this function [-Wmaybe-uninitialized]
*std::max_element(BBSuccFreq.begin(), BBSuccFreq.end());
^
ERROR: /home/developer/tensorflow/tensorflow/BUILD:652:1: Executing genrule //tensorflow:tf_python_api_gen_v1 failed (Exit 1)

bazel build -c opt --copt=-mavx --copt=-mavx2 --copt=-mfma --copt=-mfpmath=both --copt=-msse4.2 --verbose_failures //tensorflow/tools/pip_package:build_pip_package
is the command line that was run.

INFO: From Compiling tensorflow/compiler/xla/service/cpu/parallel_task_assignment.cc:
In file included from ./tensorflow/compiler/xla/service/hlo_computation.h:35:0,
from ./tensorflow/compiler/xla/service/hlo_cost_analysis.h:21,
from ./tensorflow/compiler/xla/service/cpu/parallel_task_assignment.h:20,
from tensorflow/compiler/xla/service/cpu/parallel_task_assignment.cc:16:
./tensorflow/compiler/xla/service/hlo_instruction.h: In member function 'void xla::HloInstruction::ReplaceCalledComputations(std::functionxla::HloComputation*(xla::HloComputation*))':
./tensorflow/compiler/xla/service/hlo_instruction.h:1119:25: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
for (int64 i = 0; i < called_computations_.size(); ++i) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from ./tensorflow/core/platform/default/logging.h:24:0,
from ./tensorflow/core/platform/logging.h:25,
from ./tensorflow/core/lib/gtl/flatmap.h:26,
from ./tensorflow/compiler/xla/service/cpu/target_machine_features.h:22,
from ./tensorflow/compiler/xla/service/cpu/parallel_task_assignment.h:19,
from tensorflow/compiler/xla/service/cpu/parallel_task_assignment.cc:16:
./tensorflow/core/platform/default/logging.h: In instantiation of 'std::string* tensorflow::internal::Check_LEImpl(const T1&, const T2&, const char*) [with T1 = long long int; T2 = long unsigned int; std::string = std::basic_string]':
./tensorflow/compiler/xla/shape_util.h:118:5:   required from here
./tensorflow/core/platform/default/logging.h:232:35: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
TF_DEFINE_CHECK_OP_IMPL(Check_LE, <=)
./tensorflow/core/platform/macros.h:88:49: note: in definition of macro 'TF_PREDICT_TRUE'
#define TF_PREDICT_TRUE(x) (_builtin_expect(!!(x), 1))
^
./tensorflow/core/platform/default/logging.h:232:1: note: in expansion of macro 'TF_DEFINE_CHECK_OP_IMPL'
TF_DEFINE_CHECK_OP_IMPL(Check_LE, <=)
^
In file included from ./tensorflow/compiler/xla/array2d.h:29:0,
from ./tensorflow/compiler/xla/literal.h:31,
from ./tensorflow/compiler/xla/service/dfs_hlo_visitor.h:24,
from ./tensorflow/compiler/xla/service/hlo_cost_analysis.h:20,
from ./tensorflow/compiler/xla/service/cpu/parallel_task_assignment.h:20,
from tensorflow/compiler/xla/service/cpu/parallel_task_assignment.cc:16:
./tensorflow/compiler/xla/array.h: In instantiation of 'bool xla::Array::operator==(const xla::Array&) const [with T = long long int]':
./tensorflow/compiler/xla/service/hlo_sharding.h:189:38:   required from here
./tensorflow/compiler/xla/array.h:421:25: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
for (int64 i = 0; i < sizes.size(); ++i) {
^~~~~~~~~~~~~
ERROR: /home/developer/tensorflow/tensorflow/BUILD:652:1: Executing genrule //tensorflow:tf_python_api_gen_v1 failed (Exit 1): bash failed: error executing command
(cd /home/developer/.cache/bazel/_bazel_developer/6acbce31a4e8077fc84a239074e8eda3/execroot/org_tensorflow &&
exec env -
LD_LIBRARY_PATH=/usr/local/cuda/lib64:/usr/local/cuda/lib:
PATH=/home/developer/anaconda3/envs/AI/bin:/home/developer/anaconda3/bin:/usr/local/cuda/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
/bin/bash -c 'source external/bazel_tools/tools/genrule/genrule-setup.sh; bazel-out/host/bin/tensorflow/create_tensorflow.python_api_1 --root_init_template=tensorflow/api_template.init.py --apidir=bazel-out/host/genfiles/tensorflow_api/v1/ --apiname=tensorflow --apiversion=1 --package=tensorflow.python --output_package=tensorflow._api.v1 bazel-out/host/genfiles/tensorflow/_api/v1/init.py bazel-out/host/genfiles/tensorflow/_a

The problem has been solved. I have encountered this problem. I can’t solve it.

Has the problem been solved? I also encountered this problem, how can I not solve it?

Same here, Ubuntu 18.04, very latest CUDA, NCCL etc.

The failure is right in your logs:
ImportError: No module named enum

In the failing python distro, you may need to install enum.


Exception thrown when password is invalid

Throwing and catching of exceptions is extremely slow. Therefore one of the rules in programming is to not use exception for flow control.
It'd be great if there's a proper return value to check indicating whether it was extracted or not and the reasons for that.
For instance: entry.WriteToDictionary returns void, it could however return something like:
Class ExtractionResult
{
bool success;
ExtractionErrors error
}
enum ExtractionErrors
{
InvalidPassword,
NotEnoughDiskspace
NoPermissions
etc....
}
Why I care? To be honest, I'm trying to bruteforce the password of a zip file. Where my password generator is able to get to "aaaaaa" in 2 seconds, it ends up at "nx" after 30 seconds because the exception handling is so slow.

You're welcome to make a PR that gives proper feedback from the password code all the way in the external code without an exception.  It's a pretty major refactor to do it.
Exceptions were used because for most use cases, it is exceptional.  Brute forcing a password isn't a use case I envisioned for this.

Thanks for your reply. I was actually looking into that yesterday, but I gave up after 5 minutes because I wasn't able to compile the solution. I'm not blaming anyone, but solutions that work out of the box are getting rarer and rarer nowadays :( It seems like it's an art nobody cares about anymore


Prevent HTML from being entered into Edit Data Cells.

Addresses https://github.com/microsoft/azuredatastudio/issues/21182
Prevents Submission of a cell that contains HTML code, also has commented out option to clean the code immediately for submitting, whichever is preferred.
Whatever is entered in the text editor remains part of the data of the grid (until the table is refreshed with server values in safe cell format) and switching tabs will result in the HTML executing upon rerender with no way to change this behavior from ADS's side aside from whatever is in the applyValue function.
A proposed idea that I have is to immediately refresh/reload the table (akin to clicking run) upon submit so that a Display Edit Data Cell (which is safe upon rerender) will replace the cell containing live HTML. But this will require testing to see if it works or not and if there are any side effects.
This is a small workaround for now.

Is this linked to the correct issue? It's unclear to me how HTML content relates to that issue

@Charles-Gagnon Fixed it

Closing PR, making changes to slickgrid instead


Rex Rocket: fails to launch with old or new FNA.dll

System.IndexOutOfRangeException: Index was outside the bounds of the array.
  at Microsoft.Xna.Framework.Graphics.OpenGLDevice+<GenRenderbuffer>c__AnonStorey11.<>m__0 () [0x00076] in <1228ed57c8bd40ccbca8b36912bbc9f3>:0
  at Microsoft.Xna.Framework.Graphics.OpenGLDevice.ForceToMainThread (System.Action action) [0x00022] in <1228ed57c8bd40ccbca8b36912bbc9f3>:0
  at Microsoft.Xna.Framework.Graphics.OpenGLDevice.GenRenderbuffer (System.Int32 width, System.Int32 height, Microsoft.Xna.Framework.Graphics.DepthFormat format, System.Int32 multiSampleCount) [0x00031] in <1228ed57c8bd40ccbca8b36912bbc9f3>:0
  at Microsoft.Xna.Framework.Graphics.RenderTarget2D..ctor (Microsoft.Xna.Framework.Graphics.GraphicsDevice graphicsDevice, System.Int32 width, System.Int32 height, System.Boolean mipMap, Microsoft.Xna.Framework.Graphics.SurfaceFormat preferredFormat, Microsoft.Xna.Framework.Graphics.DepthFormat preferredDepthFormat, System.Int32 preferredMultiSampleCount, Microsoft.Xna.Framework.Graphics.RenderTargetUsage usage) [0x0009a] in <1228ed57c8bd40ccbca8b36912bbc9f3>:0
  at SIDIOUS.Game1.LoadContent () [0x00395] in <8c8d175094944e1c974389b2489ebea0>:0
  at Microsoft.Xna.Framework.Game.Initialize () [0x0005f] in <1228ed57c8bd40ccbca8b36912bbc9f3>:0
  at SIDIOUS.Game1.Initialize () [0x000b9] in <8c8d175094944e1c974389b2489ebea0>:0
  at Microsoft.Xna.Framework.Game.DoInitialize () [0x0000d] in <1228ed57c8bd40ccbca8b36912bbc9f3>:0
  at Microsoft.Xna.Framework.Game.Run () [0x00011] in <1228ed57c8bd40ccbca8b36912bbc9f3>:0
  at SIDIOUS.Program.Main (System.String[] args) [0x00006] in <8c8d175094944e1c974389b2489ebea0>:0

... will check if other games needing FNA.dll replacement have issues now

Wyv and Keep does not have this issue.

Wizorb also doesn't

humblebundle version (fails to launch):

RexRocket.exe <IP_ADDRESS>
FNA.dll <IP_ADDRESS>

Steam version (runs):

RexRocket.exe <IP_ADDRESS>
FNA.dll <IP_ADDRESS>

But RexRocket.exe are different, and if you replace the one in the humble version with the one of the Steam version, the game runs:
$ diff [...]
Binary files ./RexRocket.exe and ../../untared/rex-rocket/Rex Rocket/RexRocket.exe differ

closing the issue. Use Steam version (via depotdownloader or something) and/or complain to the gamedevs that they got a relatively defective version on humblebundle DRM-free download.


Figure out why connection field edges node fields are optional

Currently all connection fields have edges typed as:
edges: [WhateverEdge]!

And the edge itself has:
node: WhateverNode

Where you'd expect to get:
edges: [WhateverEdge!]!

and
node: WhateverNode!

Current edges definition makes it legal to return the following response:
{
    "edges": [null, null, null, { "node": "whatever" }]
}

Current node definion makes it legal to respond with an edge that says:
{
    "cursor": "1234567890",
    "node": null
}

This turned out to be a problem which I discovered when generating TS types with apollo-codegen. The current schema results in TS types which allows edges and nodes inside them to be null, which I guess is not correct in GraphQL API. Those types require us to put additional null checks, where there is no possibility for null value (e.g. empty connection returns empty list, not null value).
I looked in the Graphene source code and found two places responsible for that:

EdgeBase defines a node which is optional (no required=True)
edges  defines a non-null list of objects, while it shuold also requires the objects to be non-null: Field(NonNull(List(NonNull(edge)))).

I'm afraid to I'll have to hack the Connection class and try to override it to fix the issue.


unknow error:TypeError: Cannot set property 'isRootInsert' of undefined

mac, node v7.2.1, npm v3.10
i run the following code
$ quasar init tet
$ cd test
$ npm i
$ quasar dev

but the error happened
TypeError: Cannot set property 'isRootInsert' of undefined
    at createElm (eval at <anonymous> (app.js:794), <anonymous>:4057:24)
    at createChildren (eval at <anonymous> (app.js:794), <anonymous>:4166:9)
    at createElm (eval at <anonymous> (app.js:794), <anonymous>:4091:9)
    at createChildren (eval at <anonymous> (app.js:794), <anonymous>:4166:9)
    at createElm (eval at <anonymous> (app.js:794), <anonymous>:4091:9)
    at VueComponent.patch [as __patch__] (eval at <anonymous> (app.js:794), <anonymous>:4509:7)
    at VueComponent.Vue._update (eval at <anonymous> (app.js:794), <anonymous>:2483:19)
    at VueComponent.eval (eval at <anonymous> (app.js:794), <anonymous>:2457:10)
    at Watcher.get (eval at <anonymous> (app.js:794), <anonymous>:1661:27)
    at new Watcher (eval at <anonymous> (app.js:794), <anonymous>:1653:12)

i don't know why it happened

the branchwebpack1 is fine

Stick to Vue 2.1.6 and its template compiler packages until I get all this sorted out. The second time something breaks in Vue due to a new release..

thanks, solve it by stick to v2.1.6
i think stick to the version in package.json rather then use ^ will be better?

Yes. Pushed patch for that.


"pip wheel" gets null version string from submodule

This must be a variant of https://github.com/warner/python-versioneer/issues/38 .
In this case it affects projects with the standard directory structure, where .git and setup.py are in the same directory - but where the package directory is a submodule of another repository.
When building wheels for various projects, I often have the wheel-building machinery in a repository, and the project I am building as a sub-module (e.g. matplotlib-wheels and many others).  For pip wheel . in the submodule, the version string is incorrect:
$ mkdir mod  # Make an empty superproject
$ cd mod
$ git init
$ # Add some submodule using (latest master) versioneer
$ git submodule add https://github.com/matthew-brett/transforms3d.git
$ # Make wheel with `pip wheel`
$ cd transforms3d/
$ pip wheel .
$ # Version string is incorrect
$ ls *.whl
transforms3d-0+unknown-py2-none-any.whl

It is correct for python setup.py bdist_wheel:
$ python setup.py bdist_wheel
$ ls dist
transforms3d-0.2.1+5.g7631d2a-py2-none-any.whl

See https://github.com/matplotlib/matplotlib/issues/6605 for the original report.

Can confirm this is still an issue with the latest pip.

Seems to be fixed with recent pip/setuptools/wheel.


feat(model): auto moderation models

Adds auto moderation models.
TODO:

[ ] de/ser tests
[ ] writing a changelog in this description

Part of #1709.

Missing channel::message::MessageType::AutoModerationAction (24)

https://github.com/twilight-rs/twilight/pull/1796/files#diff-3cfd10dabdf3a2abdea13721cf403393900683604e5fa1a12945c7006e1a1d52R33

I'll get to the other reviews soon

Ready for review.

This does not close #1709 as the HTTP routes are not implemented.


Add coveralls

https://coveralls.io/
Check config from: https://coveralls.io/github/deadtrickster/prometheus.erl

for reference https://github.com/lambdaclass/throttle/pull/18/files


[Docs] Sidebar Unordered Lists Restructure

Signed-off-by: Lee Calcote<EMAIL_ADDRESS>Notes for Reviewers
This PR fixes #
Signed commits

[ ] Yes, I signed my commits.

🚀 Preview for commit 369c2f950543b94ae984ad0d23355d8874e23af6 at: https://6566baf571ba751084ff8e0e--meshery-docs-preview.netlify.app

It definetly need some css styling. and also it would be great if we can remove the numbering to lists. I'll add the necessary css and javascript changes.

The numbering is debug. Yes, do remove, please.


Please add support for focus-follows-mouse max-scroll-amount="N%"

Recentish niri unstable has a new (optional) parameter for focus-follows-mouse: max-scroll-amount="N%". It would be amazing if this flake supported that.
I tried adding it myself, but sadly my brain is in a "nope, we're not writing any Nix now" mood.

This has been implemented now :3
It's done as a breaking change because i didn't feel like writing an automatic migration layer right now.
The three users i could find who are affected on github and present in the Matrix channel have been notified via Matrix.


Adding payment information to OSDM I 48/49

Designed payment information in Patch Booking operation and booking Model

Payment --> PaymentMethod
PaymentMethod --> PaymentType


python311Packages.environs: 10.3.0 -> 11.0.0

Diff: https://github.com/sloria/environs/compare/refs/tags/10.3.0...11.0.0
Changelog: https://github.com/sloria/environs/blob/11.0.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[ ] 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/)
24.05 Release Notes (or backporting 23.05 and 23.11 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

[ ] Fits CONTRIBUTING.md.

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

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

6 packages marked as broken and skipped:

chatgpt-retrieval-plugin
chatgpt-retrieval-plugin.dist
python312Packages.deezer-python
python312Packages.deezer-python.dist
python312Packages.environs
python312Packages.environs.dist

8 packages built:

ansible-doctor
ansible-doctor.dist
python311Packages.deezer-python
python311Packages.deezer-python.dist
python311Packages.environs
python311Packages.environs.dist
python311Packages.pymilvus
python311Packages.pymilvus.dist


Testing

Some automated testing is good to be available

https://blog.jetbrains.com/go/2022/11/22/comprehensive-guide-to-testing-in-go/#writing-coverage-tests


No MDNS services are listed by zeroconf when using Windows 11

This may or may not be an issue with the way I'm using zeroconf (may be my version of Cython if it uses that), because the problem seems to appear and vanish according to the issue here: https://github.com/python-zeroconf/python-zeroconf/issues/1055
I have tried some different ways of using it here: https://github.com/Hierosoft/python-openlcb/tree/zeroconf-windows11-fix, but made no progress yet.

What do I need to do to execute that code?  Just run examples_gui.py?  I tried that on my Mac and didn't see anything in the top box.

This seems to work:
from zeroconf import ServiceBrowser, ServiceListener, Zeroconf

class MyListener(ServiceListener):

    def update_service(self, zc: Zeroconf, type_: str, name: str) -> None:
        print(f"Service {name} updated")

    def remove_service(self, zc: Zeroconf, type_: str, name: str) -> None:
        print(f"Service {name} removed")

    def add_service(self, zc: Zeroconf, type_: str, name: str) -> None:
        info = zc.get_service_info(type_, name)
        print(f"Service {name} added, service info: {info}")

zeroconf = Zeroconf()
listener = MyListener()
browser = ServiceBrowser(zeroconf, "_openlcb-can._tcp.local.", listener)
try:
    input("Press enter to exit...\n\n")
finally:
    zeroconf.close()

with output:
% python3.10 example_zeroconf.py
Press enter to exit...

Service tcs_cs_090099030035._openlcb-can._tcp.local. added, service info: ServiceInfo(type='_openlcb-can._tcp.local.', name='tcs_cs_090099030035._openlcb-can._tcp.local.', addresses=[b'\xc0\xa8\x10\xd4'], port=12021, weight=0, priority=0, server='tcs-cs-0035.local.', properties={b'OLCB': None}, interface_index=None)

I don't get anything on Windows 11 from your minimal example either. Also, in examples_gui.py try clicking "detect" by IP address to fill in the top drop-down box. That will probably work as long as you are not using Windows 11. Let me know if you have trouble, but I will also try to make the interface more intuitive.

On my Mac, it seems like there's about a 5 second pause before the Detect button is able to click.  After that, it detects the CS-105 just fine.
Not sure what to recommend for Windows 11.  Something seems broken, which is surprising:  There are a lot of Windows 11 machines out there.

Is it possible that it's one specific Windows 11 machine, and not Windows 11 in general?  Can you try on another Win11 machine?
IIRC, at one point there was a component you needed to install for Windows to speak Zeroconf/Bonjour.  Maybe that's missing on the Win11 machine.

Ok, yes it is only happening on certain Windows 11 machines. @myciodan says he's had to tell people to power cycle the machine etc. to get it to work (that is going back years before Windows 11 even), so I will probably have to do an IP address search if Windows' unreliable MDNS fails to work. I will see if there is a way to fix it by restarting MDNS or other service(s) without restarting Windows.

Could you check whether IPv6 is enabled or not on the machines that are causing the problem?  There's a JMRIusers thread where they seem to be having a problem with mDNS when IPv6 is disabled on Windows.

Having IPv6 enabled doesn't make the issue happen, but when I get a chance I'll try disabling it on the machine where MDNS does not work. For now I've started a diagnostic tool here: https://github.com/Hierosoft/mdnscheckup


Provide a way to persist sessions with gists

I think it would be neat if the website could utilize https://gist.github.com/ to store sessions, this way you could track changes and persist across different browsers

I actually had some nice thoughts about this early on.
I couldn't device if  if it should support gist or something more generic like pastebin though.
in theory it's dead simple and can make share links shorter though


Review Client.prototype.getLeafletLayer

[x] Returns an instance of L.TileLayer so that devs can do things like setZIndex.
[x] Document the result of Client.prototype.getLeafletLayer.
[ ] Wait to check if window.L exists until Leaflet is really required (we are now checking this at the very beginning).
[x] Leaflet Layer has the CARTO attribution: © OpenStreetMap, © CARTO

I have extended L.TileLayer to use our internalView in the addTo and removeFrom and it works!
The 3rd point is not possible now because of wax:


Regression: "bad extension" when connecting to httpbin.org:443

Log of s_client on 6dd083fd6804a3ee6ac3adc019f81910f1c63f21 (git bisect points to this commit):
$ /home2/yen/sysroot/usr/local/bin/openssl s_client -connect httpbin.org:443
CONNECTED(00000005)
140243072000064:error:141B306E:SSL routines:tls_collect_extensions:bad extension:ssl/statem/extensions.c:318:
140243072000064:error:141710E3:SSL routines:tls_process_server_hello:parse tlsext:ssl/statem/statem_clnt.c:1312:
---
no peer certificate available
---
No client certificate CA names sent
---
SSL handshake has read 66 bytes and written 183 bytes
Verification: OK
---
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    Cipher    : 0000
    Session-ID:
    Session-ID-ctx:
    Master-Key:
    PSK identity: None
    PSK identity hint: None
    SRP username: None
    Start Time:<PHONE_NUMBER>
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: no
---

The problem seems to be that TLSEXT_TYPE_ec_point_formats is missing a EXT_TLS1_2_SERVER_HELLO flag.

The problem seems to be that TLSEXT_TYPE_ec_point_formats is missing a EXT_TLS1_2_SERVER_HELLO flag.

Thanks this patch works for me on master:
diff --git a/ssl/statem/extensions.c b/ssl/statem/extensions.c
index 760b150a6..f6b0589ff 100644
--- a/ssl/statem/extensions.c
+++ b/ssl/statem/extensions.c
@@ -120,7 +120,7 @@ static const EXTENSION_DEFINITION ext_defs[] = {
 #ifndef OPENSSL_NO_EC
     {
         TLSEXT_TYPE_ec_point_formats,
-        EXT_CLIENT_HELLO | EXT_TLS1_2_AND_BELOW_ONLY,
+        EXT_CLIENT_HELLO | EXT_TLS1_2_SERVER_HELLO | EXT_TLS1_2_AND_BELOW_ONLY,
         NULL, tls_parse_ctos_ec_pt_formats, tls_parse_stoc_ec_pt_formats,
         tls_construct_stoc_ec_pt_formats, tls_construct_ctos_ec_pt_formats,
         final_ec_pt_formats

Is it correct? I'm not familiar with TLS protocols.

Fix in #2153

Works with the current master, thanks you all!


Bug: If you open a link to a post in which the id parameter is set to 0, the application crashes

Fixed by 1b784d2 commit


Error while preprocessing: markup.update is not a function

Hello,
I am trying to follow the docs at https://threlte.xyz/getting-started#installation. I am using Vite and Svelte (not SvelteKit), and I am getting this error while trying to run development server
[vite] Internal server error: Error while preprocessing Landing.svelte - markup.update is not a function
  Plugin: vite-plugin-svelte
  File: Landing.svelte
      at Object.enter (index.js:121:32)
      at SyncWalker.visit (node_modules/svelte/compiler.mjs:6211:16)
      at SyncWalker.visit (node_modules/svelte/compiler.mjs:6241:18)
      at SyncWalker.visit (node_modules/svelte/compiler.mjs:6241:18)
      at SyncWalker.visit (node_modules/svelte/compiler.mjs:6241:18)
      at SyncWalker.visit (node_modules/svelte/compiler.mjs:6248:11)
      at walk (node_modules/svelte/compiler.mjs:6299:18)
      at preprocessMarkup (node_modules/@threlte/preprocess/dist/index.js:41:5)
      at markup (node_modules/@threlte/preprocess/dist/index.js:158:32)
      at process_markup (node_modules\svelte\compiler.js:43406:30)

Could you please help me out? I do not understand why am I getting this error.

Hey @DeepBhat, I guess a dependency of yours installed magic-string in a version prior to 0.26.6 which added the method update. Running npm i -D magic-string should resolve the issue.


⚖ Register Validator: pi69

Network Choice
dentrite-1
Who are you?
My name is Bahadır. I use the name pi69 validator on the nodes I run. I have been in the blockchain ecosystem since 2020. I have run mainnet and testnet nodes and I still continue to run them.
Delegator address
axone10t236npp38kd3wecqqm7da3ljdywaeqyj5tu99
gentx
{"body":{"messages":[{"@type":"/cosmos.staking.v1beta1.MsgCreateValidator","description":{"moniker":"pi69","identity":"6C36E7C076BFDCE4","website":"https://github.com/bozdemir52","security_contact":"bozdemir52@gmail.com","details":"My validator"},"commission":{"rate":"0.050000000000000000","max_rate":"0.200000000000000000","max_change_rate":"0.010000000000000000"},"min_self_delegation":"1","delegator_address":"","validator_address":"axonevaloper10t236npp38kd3wecqqm7da3ljdywaeqyzp8wl8","pubkey":{"@type":"/cosmos.crypto.ed25519.PubKey","key":"IHqX+K1h7nf8zCux+KEmGdomJbCuFZtkv4mKi3ztqoU="},"value":{"denom":"uaxone","amount":"1000000000000"}}],"memo":"dc1a73f2221ec56acfb4a5b2e5c7a22fd063104f@<IP_ADDRESS>:26656","timeout_height":"0","extension_options":[],"non_critical_extension_options":[]},"auth_info":{"signer_infos":[{"public_key":{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"A6HBmKtEBjqG1zttF7NMdAxKRojZhrdw2jak1HHdGPdZ"},"mode_info":{"single":{"mode":"SIGN_MODE_DIRECT"}},"sequence":"0"}],"fee":{"amount":[],"gas_limit":"200000","payer":"","granter":""},"tip":null},"signatures":["z5++PMs/Gx+KhfBk5+AGODOXMueiRK4XPl6W3A8gQY4ttoQPlJEhpZqN2g1/k5maS2phWPM+SELoV486Z33vmA=="]}

😢 I couldn't process your request: Register process is closed for this network.

This network has already been launched.


Added proposal for xDD full-PDF API

A key question, @iross, is whether this system would be tied explicitly to xDD and the "bring your own documents" capability. i.e., would the document have to be stored in xDD to appear in this system?
The upside is that it would make it possible to independently maintain and add to a document store, which is desirable functionality for CriticalMAAS. The downside is that some "automatic" capabilities of xDD (e.g., OCR and full-text ElasticSearch over the outputs) would not be available or would have to be separately included in this system.
My sense is that we should open this up so that documents can be ingested here without being in xDD necessarily. We could then consider which services can be provided for non-xDD documents. If the appropriate metadata is available, we could integrate this with a "bring your own documents" flow in xDD.


[LLDB] Xcode CustomSwift-Debug

Fix build configuration CustomSwift-Debug for xcodebuild
Broken since:
e25c6ecc10c85e3013b663410e8a280aca383e9f (Tue Jan 9 17:14:44 2018)
f0c3e96cd75c66753001b6285a3220464061be0f (Mon Mar 19 15:42:04 2018)

@swift-ci test and merge

Oh sorry, I didn't want to merge already, only test. Will revert that and make a new PR.

It's fine, just make the tweaks I asked for


use XDG_STATE_HOME as data_local_dir

The $XDG_STATE_HOME contains state data that should persist between (application) restarts, but that is not important or portable enough to the user that it should be stored in $XDG_DATA_HOME.

To me, this seems to indicate that non-portable files should be stored here. Of course, changing this would be a breaking change.

I think this would be rather surprising for users – which issue would this address?

XDG_DATA_HOME is often synced between machines by the user. XDG_STATE_HOME is not to be synced, as it's for local application state. When XDG_DATA_HOME is used, the expectation for data_local_dir's contents to not be synced is broken.


Live Quiz

Erase existing environment ( screen capture)
Setup our working environment (git clone´s)

Erase existing environment

Setup Enviroment for Project

scripts/venv.sh
default:~/nighthawk/Leila_2025$ ls
404.html     _includes	navigation	README.md
assets	     index.md	_notebooks	requirements.txt
_config.yml  _layouts	portfolio_2025	_sass
Gemfile      LICENSE	_posts		scripts
images	     Makefile	README4YML.md	venv
default:~/nighthawk/Leila_2025$

activate tools step
default:~$ ruby -v
ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
default:~$ bundle -v
Bundler version 2.5.18
default:~$ python --version
Python 3.10.12
default:~$ jupyter --version
Selected Jupyter core packages...
IPython          : 7.31.1
ipykernel        : 6.7.0
ipywidgets       : 6.0.0
jupyter_client   : 7.1.2
jupyter_core     : 4.9.1
jupyter_server   : not installed
jupyterlab       : not installed
nbclient         : 0.5.6
nbconvert        : 6.4.0
nbformat         : 5.1.3
notebook         : 6.4.8
qtconsole        : not installed
traitlets        : 5.1.1
default:~$
](https://github.com/nighthawkcoders/portfolio_2025.git)

Setup Environment for Project
This command creates my virtual environment
scripts/venv.sh
default:~/nighthawk/Leila_2025$ ls
404.html     _includes	navigation	README.md
assets	     index.md	_notebooks	requirements.txt
_config.yml  _layouts	portfolio_2025	_sass
Gemfile      LICENSE	_posts		scripts
images	     Makefile	README4YML.md	venv
default:~/nighthawk/Leila_2025$ scripts/venv.sh
Python 3.10.12
Requirement already satisfied: nbconvert in ./venv/lib/python3.10/site-packages (from -r requirements.txt (line 1)) (7.16.4)
Requirement already satisfied: nbformat in ./venv/lib/python3.10/site-packages (from -r requirements.txt (line 2)) (5.10.4)
Requirement already satisfied: pyyaml in ./venv/lib/python3.10/site-packages (from -r requirements.txt (line 3)) (6.0.2)
Requirement already satisfied: notebook in ./venv/lib/python3.10/site-packages (from -r requirements.txt (line 4)) (7.2.2)
Requirement already satisfied: requests in ./venv/lib/python3.10/site-packages (from -r requirements.txt (line 5)) (2.32.3)
Requirement already satisfied: python-dotenv in ./venv/lib/python3.10/site-packages (from -r requirements.txt (line 6)) (1.0.1)
Requirement already satisfied: nbclient>=0.5.0 in ./venv/lib/python3.10/site-packages (from nbconvert->-r requirements.txt (line 1)) (0.10.0)
Requirement already satisfied: packaging in ./venv/lib/python3.10/site-packages (from nbconvert->-r requirements.txt (line 1)) (24.1)

Run Server Address


Add simulation.randomSource.

Fixes #121.
TODO Default to a linear congruential generator rather than Math.random?

Would we add the lcg in d3-random then?

We could, or we could do it here as the default value for simulation.randomSource.

I think it makes more sense in d3-random, but the code is so small it might be better to copy it here and avoid the additional dependency.

I’ve added it to this PR.

Sorry to bug you, any chance we could get a minor release with this?

I initially planned to do a major release when #176 would be merged but it's a good idea to do a minor before in any case—so here is v2.1.0.
Note to self: In any event we'll release another version soon with larger dependencies (1—2).


Spring JCA - Add support for Azure Government to certificate starter

Closing this issue, because Azure US Government is already supported.
Refs: https://github.com/Azure/azure-sdk-for-java/blob/b1dcfcdec8de264eb5f6bb20813d2a24338fcb72/sdk/keyvault/azure-security-keyvault-jca/src/test/java/com/azure/security/keyvault/jca/KeyVaultClientTest.java#L28


🧶 Typescript typings

TypeDefinition file for TypeScript users.

They just.. already exist? https://github.com/lorencerri/quick.db/blob/master/index.d.ts

They just.. already exist? https://github.com/lorencerri/quick.db/blob/master/index.d.ts

for some reason it didn't work in my project and I searched for a folder called "typings" I didn't notice the file directly in the main directory. My bad 😳😅

for some reason it didn't work in my project and I searched for a folder called "typings" I didn't notice the file directly in the main directory. My bad 😳😅


[Bug Report] - refresh in vercel causes 404 (react router)

Describe the bug:
A clear and concise description of what the bug is including error messages.
Expected behavior:
page should refresh
Actual Behavior:
page 404's.. see screenshot
Screenshots:

To Reproduce:
Steps to reproduce the behavior:

Go to the vercel hosted page @ https://pass-wine.vercel.app/
Log into your pod
refresh the page once logged in, this will happen on any page aside from the home/landing page prior to logging in.

Possible Fix:
add rewrites to vercel.json
Additional context:
https://blog.probirsarkar.com/fixing-react-router-issues-on-vercel-how-to-handle-client-side-routing-and-404-errors-c4fb78aa1af5

There's still a minor bug, PR #678 should fully resolve this issue.