StackOverflowException when mapping T with a property List

public class NestedPoco : SimplePoco
    {
        public List<NestedPoco> NestedObjects { get; set; }

        public NestedPoco()
        {
            NestedObjects = new List<NestedPoco>();
        }
    }

Mapping
TinyMapper.Bind<NestedPoco, NestedPocoDTO>(config =>
{
       config.Bind(target => target.NestedObjects, typeof(List<NestedPoco>));
});

Sample from https://github.com/lusocoding/dotnet-objmap-benchmark/blob/master/Obj2ObjMapBench/Models/NestedPoco.cs
https://github.com/lusocoding/dotnet-objmap-benchmark/issues/1

thanks!
fixed https://github.com/TinyMapper/TinyMapper/releases/tag/v2.1.4-bet

Sergey,
I have noticed some problems with the 2.1.4-beta we have out on NuGet right
now. Auto Mapping (without calling bind) has been removed completely with
no option to re-enable. While this may be an intentional design
decision, Semantic
Versioning http://semver.org/ rules would indicate that we would need to
make this at least a 3.0 release instead.
Although I think that the auto mapping feature can cause trouble (mostly
when dealing with proxy objects), I think it's a feature we should retain.
It's just so handy in so many other places.
Just a thought. Noticed a bunch of code was broken this week because we
updated to the latest.
Thanks!
Nate Zaugg
<EMAIL_ADDRESS>On Fri, Aug 18, 2017 at 11:30 AM, Sergey Morenko<EMAIL_ADDRESS>wrote:

Closed #33 https://github.com/TinyMapper/TinyMapper/issues/33.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/TinyMapper/TinyMapper/issues/33#event-1212275966, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAWzW3S5dnzRRlUAjqBBwQFNMoD0qmFSks5sZcpSgaJpZM4IzlAG
.

yeah, you're right, sorry about that. Yes, I've removed it for a reason, the main idea does not add lock  for internal mappers dictionary. Let me briefly describe the mapping process, it would be a bit clear why this feature has been removed

During Bind TinyMapper creates a Mapper and put it to the dictionary
During Map the dictionary is used to lookup the mapper but in the previous version Map method updated the dictionary.

It's fine until Map is used in the multi-threaded environment.
You can simulate this behavior but you should use a wrapper around a TinyMapper. For instance, I try to create a wrapper around the third party libraries, it gives the ability to migrate to another library without a big effort. I don't create a wrapper for all third-party libraries, only for some of them.
I'll republish the nuget package and update version.  Thank you for the feedback, I appreciate it.


Revert "Improved Logging v3"

Reverts microsoft/WindowsAppSDK#4372

/azp run

Is this unnecessary given the Prefast fixes?


Fails to run silently in CI

Not entirely sure if this is a bug - or incorrect usage of pwmetrics.
If i try and run pwmetrics within my CI environment it seems to fireup headless chrome and then silently fails.
Looking for suggestions on how to at least debug this (even if its not a bug).
Here is the output:
19:14:44 + docker run --env-file .env<PHONE_NUMBER>86.dkr.ecr.ap-southeast-2.amazonaws.com/mytest:PR-50-merge-5 /bin/sh -c yarn run test:perf
19:14:45 yarn run v0.23.2
19:14:45 $ pwmetrics http://www.google.com.au --config=test/performance/pwmetrics-config.js
19:14:46 Launching Chrome
19:14:51 Done in 6.01s.
..
THEN IT JUST GOES TO THE NEXT STEP IN PIPELINE .. :(

When i run this locally (non headless) i get output like:

Which is what im after.
What I dont get is - if i run lighthouse (outside of pwmetrics) inside the CI environment - it runs headless fine when running a command like:
lighthouse http://www.google.com.au --chrome-flags='--headless'
Config / CLI options
My config file looks like:
module.exports = {
  flags: {
    runs: '1', // number or runs
    submit: false, // turn on submitting to Google Sheets
    upload: false, // turn on uploading to Google Drive
    view: false, // open uploaded traces to Google Drive in DevTools
    expectations: true, // turn on assertation metrics results against provides values
    'chrome-flags': '--headless',
  },
  expectations: {

    ttfcp: {
      warn: '>=1500',
      error: '>=0001',
    },
    ttfmp: {
      warn: '>=2000',
      error: '>=3000',
    },
    fv: {
      warn: '>=1500',
      error: '>=2000',
    },
    psi: {
      warn: '>=1500',
      error: '>=2000',
    },
    vc85: {
      warn: '>=1500',
      error: '>=2000',
    },
    vs100: {
      warn: '>=1500',
      error: '>=2000',
    },
    tti: {
      warn: '>=1500',
      error: '>=2000',
    },
  },
};

Steps to reproduce.
Run against headless chrome
Stack trace
None.
Screenshot
Environment

pwmetrics version: 2.0.2
Chrome version: Latest Stable
OS version: Docker image node:7.9.0-slim

Thanks !
ps. this tool is awesome !

Currently pwmetrics uses a commit-specific version of lighthouse see package.json.
Lighthouse has had in the past some problems runnning in headless mode https://github.com/GoogleChrome/lighthouse/issues/2008, ensure if the differences between our lighthouse version and stable one has an impact on the headless mode.
We should converge with the stable lighthouse version as soon as a new major version is released (expected to be during Google I/O this week).
Also your config file might be wrong, chrome-flags should be without '' I think. Never tested chrome-specific flags in pwmetrics.

Ok maybe ill just wait till https://github.com/paulirish/pwmetrics/issues/119 is resolved
thanks

@pedro93 are we still waiting for https://github.com/paulirish/pwmetrics/pull/120 to be resolved?
Anything i can do to help ?

We are waiting for https://github.com/GoogleChrome/lighthouse/issues/2251 to be resolved before we move to lighthouse v2 official non-alpha. There has been frequent daily work on the PR so it shouldn't be long. Maybe see if you can speed it along there?

@jooj123 we've published v3. Can you still reproduce this issue?

@denar90 ill try to test this out again tommorrow - thanks

@jooj123 Just ran into the same issue as you. Checked the source and I noticed chrome flags has to pass an array into pwmetrics and the name is camel-cased.
When I changed my options to:
flags: {
    'chromeFlags': ['--headless']
  }

I can get pwmetrics to run in headless Chrome.

Updated the readme with #126.

ok thanks @denar90 & @young - can close this one now


PHP 8  compatibility

I'm utilising readability.php in the feediron plugin for TT-RSS. TT-RSS recently have switched to PHP 8 and there looks to be some deprecation's to deal with in PHP 8. Issue originally reported here
plugins/af_readability/vendor/andreskrey/Readability/Readability.php:199
usort():** Returning bool from comparison function is deprecated, return an integer less than, equal to, or greater than zero

Ok so my issue reproduction has only been intermittent this warning, perhaps it's not a major PHP 8 issue after all. I'm still attempting to figure out how to reliably reproduce this.

Closing in favor of #99


Better error handling?

I'm listening for the "error" event and it shows me the error message but without the information of line and file I feel lost. Is there anything to improve this?

You could try this out https://github.com/niftylettuce/koa-better-error-handler


Disabled Button state not transmitted to Link - asChild

Hello there,
I have tried to implement this example in which I try to disable the button. Seems not working. The variant link added to the button isn't working either:
<Button asChild disabled={!isValid}>
  <Link to={'/final'}>
    Groot
  </Link>
</Button>

Is there a way to disable a Link?
Have a nice day! Great work!
Nico

@MagicKitty having a similar issue, did you find a fix?

Same here

try,

Groot

As I understand the problem:
When you declare a button with asChild, what happens is the Button is never rendered in the DOM. So basically no tailwindcss classes can be passed from Button to Link with group. I cannot really figure out a good solution.
The only thing that can be OKish is to style Link as a button:
const disabled = false;
<Link
  to={'/'}
  className={cn(
    buttonVariants({ variant: 'outline' }),
    disabled && 'pointer-events-none opacity-50',
  )}
>
  Click here
</Link>

Only using shadcn for 20 min and already disapointed :/

Only using shadcn for 20 min and already disapointed :/
I'm starting to feel the same way. Will switch to TailwindUI when they have a Vue version available

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.

When you are using asChild, Button component just pass props to the child component, in our case to Link component.
I am using @tanstack/router, so when disabled prop passed to the Link component, @tanstack/router set aria-disabled attribute.
Shadcn create buttonVariants for you (this is the code from shadcn WITHOUT SOLUTION):
import { cva } from "class-variance-authority";

export const buttonVariants = cva(
  "tw-inline-flex tw-items-center tw-justify-center tw-whitespace-nowrap tw-rounded-md tw-text-sm tw-font-medium tw-ring-offset-background tw-transition-colors focus-visible:tw-outline-none focus-visible:tw-ring-2 focus-visible:tw-ring-ring focus-visible:tw-ring-offset-2 disabled:tw-pointer-events-none disabled:tw-opacity-50",
  {
    variants: {
      variant: {
        outline: "tw-border tw-border-input tw-bg-background hover:tw-bg-accent hover:tw-text-accent-foreground",
        destructive: "tw-bg-destructive tw-text-destructive-foreground hover:tw-bg-destructive/90",
        secondary: "tw-bg-secondary tw-text-secondary-foreground hover:tw-bg-secondary/80",
        default: "tw-bg-primary tw-text-primary-foreground hover:tw-bg-primary/90",
        link: "tw-text-primary tw-underline-offset-4 hover:tw-underline",
        ghost: "hover:tw-bg-accent hover:tw-text-accent-foreground",
      },
      size: {
        lg: "tw-h-11 tw-rounded-md tw-px-8",
        default: "tw-h-10 tw-px-4 tw-py-2",
        sm: "tw-h-9 tw-rounded-md tw-px-3",
        icon: "tw-h-10 tw-w-10",
      },
    },
    defaultVariants: {
      variant: "default",
      size: "default",
    },
  },
);

I add these classes to the end of the first line of cva and it helped:
cva(
"...aria-disabled:tw-opacity-50 aria-disabled:tw-pointer-events-none",
{
  variants: ...

And this will work:
import { Button } from "@/libs/shadcn/ui/button";
import { Link } from "@tanstack/react-router";

<Button variant="ghost" disabled={true} asChild>
  <Link to="/interviews/$interviewId" params={{ interviewId }}>
    Some link
  </Link>
</Button>;

Hello there, I have tried to implement this example in which I try to disable the button. Seems not working. The variant link added to the button isn't working either:
<Button asChild disabled={!isValid}>
  <Link to={'/final'}>
    Groot
  </Link>
</Button>

Is there a way to disable a Link?
Have a nice day! Great work! Nico

My solution for this case is to set asChild to be the ! of whatever the disabled value is.
For example, in your case
<Button asChild={isValid} disabled={!isValid}>
  <Link to={'/final'}>
    Groot
  </Link>
</Button>

I settled on this approach which is nice enough:
  if (disabled) {
    return (
      <Button variant="link" className={className} disabled>
        {children}
        <ExternalLinkIcon size={"0.8em"} className="ml-1" />
      </Button>
    );
  }
  return (
    <Button variant="link" asChild className={className}>
      <Link href={href} target="_blank">
        {children}
        <ExternalLinkIcon size={"0.8em"} className="ml-1" />
      </Link>
    </Button>
  );

Respects the idea that a disabled link isn't really a link at all!

When you are using asChild, the Button component simply passes props to the child component, in our case, to the Link component.
I am using @tanstack/router, so when the disabled prop is passed to the Link component, @tanstack/router sets the aria-disabled attribute.
Shadcn creates buttonVariants for you (this is the code from Shadcn WITHOUT SOLUTION):"
import { cva } from "class-variance-authority";

export const buttonVariants = cva(
  "tw-inline-flex tw-items-center tw-justify-center tw-whitespace-nowrap tw-rounded-md tw-text-sm tw-font-medium tw-ring-offset-background tw-transition-colors focus-visible:tw-outline-none focus-visible:tw-ring-2 focus-visible:tw-ring-ring focus-visible:tw-ring-offset-2 disabled:tw-pointer-events-none disabled:tw-opacity-50",
  {
    variants: {
      variant: {
        outline: "tw-border tw-border-input tw-bg-background hover:tw-bg-accent hover:tw-text-accent-foreground",
        destructive: "tw-bg-destructive tw-text-destructive-foreground hover:tw-bg-destructive/90",
        secondary: "tw-bg-secondary tw-text-secondary-foreground hover:tw-bg-secondary/80",
        default: "tw-bg-primary tw-text-primary-foreground hover:tw-bg-primary/90",
        link: "tw-text-primary tw-underline-offset-4 hover:tw-underline",
        ghost: "hover:tw-bg-accent hover:tw-text-accent-foreground",
      },
      size: {
        lg: "tw-h-11 tw-rounded-md tw-px-8",
        default: "tw-h-10 tw-px-4 tw-py-2",
        sm: "tw-h-9 tw-rounded-md tw-px-3",
        icon: "tw-h-10 tw-w-10",
      },
    },
    defaultVariants: {
      variant: "default",
      size: "default",
    },
  },
);

I added these classes to the end of the first line of cva, and it helped
cva(
"...aria-disabled:tw-opacity-50 aria-disabled:tw-pointer-events-none",
{
  variants: ...

And this will work:
import { Button } from "@/libs/shadcn/ui/button";
import { Link } from "@tanstack/react-router";

<Button variant="ghost" disabled={true} asChild>
  <Link to="/interviews/$interviewId" params={{ interviewId }}>
    Some link
  </Link>
</Button>;

This works perfectly fine. Just remember that if your Link component doesn't set the aria-disabled attribute you will have to do it yourself. In my case i was using Inertia so my PaginationLink (a button under the hood) got change to this
//From this
<PaginationLink
    ...
    disabled={previousLink.url === null}
    asChild>
        <Link
            ...
        >
        </Link>                    </PaginationLink>

//To this
<PaginationLink
                        aria-label="Ir a la página anterior"
                        size="default"
                        className="gap-1 pl-2.5"
                        asChild
                    >
                        <Link
                            aria-disabled={previousLink.url === null}
                            href={
                                previousLink.url
                                    ? mergeQs(previousLink.url)
                                    : ""
                            }
                            preserveScroll
                        >
                            <ChevronLeft className="h-4 w-4" />
                            Anterior
                        </Link>
                    </PaginationLink>

I came up with this, which basically always renders a (disabled) button when the disabled attribute is set:
- const Comp = asChild ? Slot : 'button';
+ const Comp = asChild && !disabled ? Slot : 'button';

`
export interface LinkProps
extends React.AnchorHTMLAttributes,
VariantProps {
href: string;
disabled?: boolean;
}
const Link = React.forwardRef<HTMLAnchorElement, LinkProps>(
({ className, variant, size, disabled = false, href, ...props }, ref) => {
if (!href) {
throw new Error('The href prop is required for the Link component.');
}
	return (
		<NextLink
			href={href}
			className={cn(
				buttonVariants({ variant, size, className }),
				disabled && 'pointer-events-none opacity-50',
			)}
			ref={ref}
			{...(disabled ? { 'aria-disabled': true } : {})}
			{...props}
		/>
	);
},

);
Link.displayName = 'Link';
`
minha solução pegando algumas sugestões dos comentários acima

This issue needs to be re-opened please 🙏  @shadcn

Still problematic

Anchor tags don't have a disabled state, use buttons, there is no problem with the Link component itself.

@wizzymore Have you tried what we are talking about ? All we are saying is that as of now, if you disable the button and have asChild it doesn't disable it.

Well if you use asChild and the child is an anchor tag and not a button IT WILL NOT WORK.
asChild will just pass the props down to the child component and render that. An anchor tag DOES NOT have a disabled state. If you Link component supports changing what it is you can do something like:
<Button disabled={...} asChild>
    <Link as="button">
        Link
    </Link>
</Button>

Well if you use asChild and the child is an anchor tag and not a button IT WILL NOT WORK. asChild will just pass the props down to the child component and render that. An anchor tag DOES NOT have a disabled state. If your Link component supports changing what it is you can do something like:
<Button disabled={...} asChild>
    <Link as="button">
        Link
    </Link>
</Button>

But it does not work with a button. That's the whole point of this issue thread.

For people that are still confused on what is happening right here.
All the stylings for the disabled state of the button is based on the "disabled" attribute put on the html element.
When you do something like <Button asChild>...</button> what it does behind the scenes is this:
...

If you use a "Link" component or something else inside there it would look like this:
// What you write
<Button asChild disabled={true}>
    <Link>...</Link>
</Button>

// What is rendered
<Link class="button classes" disabled={true}>...</Link>

If YOUR component that is put as a child of the BUTTON, DOES NOT take a disabled prop and DOES NOT handle it correctly, you will never get the "disabled" attribute on your html element.
Also, "disabled" is not a valid html attribute for anchor tags (  ).
What you need to do is this:
<Button asChild disabled={true}>
    <LinkAsAButton>...</LinkAsAButton>
</Button>

This will render the following html and everything will work:
<button class="button classes" disabled="disabled">...</button>


title

Resolves #24
Quality Assurance:

this should request review from @EtherealGlow now in a sec

.

.

.


chore: remove unnecessary package-lock files

Since we are using npm workspaces we only need  single package-lock at the root of the piercing directory.

Ah yes, I noticed this after moving to workspaces but forgot to remove them, thanks! ❤


How to use

If you have experience coding, you'll understand. I will only respond once to such issue, then just close them.

Download premake5.
Navigate to the cloned repository folder in the command prompt and enter 'premake5 vs2022' and then open the project in Visual Studio 2022.
Compile the code.
Inject compiled DLL into the game to generate SDK.
And now you have created the SDK. The SDK can be found in the folder where the game's .exe file is located.

ok got it, im confused where the sdk generated, now i found it coz reading this issue. ty


Encoding Error

Trying to bind a book at a URL from File Selector, suddenly. I believe that it was caused by the update to XCode 15.1 but I'm not sure. Some epubs can be bound, some do cannot and give me the EncodingMismatch error and I can't figure out what the difference between some epubs that work and some epubs that do not. I've been digging for a few days now and scanning the Kanna and Bookbinder code, but can't figure out what the issue is. I'll update if anything changes and if new information is needed.

ffigure it out?

I couldn't. I ended up needing to make my own program to process this information and am not using BookBinder anymore.

I'm now using foliate-js via webview, it works well


Build with go 1.21 and minor dependency bumps

Bumps golang to 1.21 along with a few dependency updates missed somehow.

I see other distinct PRs exist for some of the dependencies here. Let’s merge those and I’ll rebase this.

@chadlwilson All of those are in now. Dont forget to update the gauge version for release ;)

Done now, build is running - thanks @haroon-sheikh !

One of the FT is really flaky on windows, I need to find some time to investigate.

Yeah, Ive noted that elsewhere myself, haven't had time to investigate either.

@haroon-sheikh think this one needs your mind re-review :-)


Android Devices send Beacons divergent from Exposure Notification Bluetooth Specification

Avoid duplicates

[X] Bug is not mentioned in the FAQ
[X] Bug is specific for Android only, for general issues / questions that apply to iOS and Android please raise them in the documentation repository
[X] Bug is not already reported in another issue

Describe the bug
Using the Android App "nRF Connect", I looked at the COVID-19 Exposure Notification beacons sent by various devices.
The expected data is described in the Exposure Notification Bluetooth Specification.
While the raw data sent by iOS devices matches the specification and starts like this:
0x02011A03036FFD17166FFD....
the data I see from my own Android devices (Pixel 3 XL, Samsung A10, LG Nexus 4) omit the "flags section" and directly start with
0x03036FFD17166FFD....
Of course I assume that interoperability is still given between iOS and Android (eventually the Bluetooth Core Spec allows omission of the "flags section" with their current data), this difference allows me to distinguish users with active CWA by their operating system type over the air.
This could be considered an unnecessary information disclosure arising from the usage of the CWA (which in most cases is also facilitated by Apples "Nearby" beacons, but those can eventually be switched off by disabling AirDrop).
Expected behaviour
Android devices shall use a beacon according to the specification.
Steps to reproduce the issue
Use a BLE scanner which allows visualization of the "flags section" of the received data and look at the data emitted from an Android device.
Examples:
"nRF Connect" can show the raw data by pressing "RAW".
Example raw data from an Android device:

Example raw data from an iOS device:

Internal Tracking ID: EXPOSUREAPP-1937

Unfortunately, this can't be addressed here. This app is just using the API provided by Google / Apple and thus, they'd need to make changes.

Unfortunately, this can't be addressed here. This app is just using the API provided by Google / Apple and thus, they'd need to make changes.

I full agree, however, issue #744 shows that also bugs clearly residing in the underlying framework are discussed here and can be addressed by the CWA developers to the Google developers.

Related: https://github.com/corona-warn-app/cwa-documentation/issues/341
e.g. Googles own specification states

The advertiser address type shall be Random Non-resolvable.

But it seems currently resolvable advertisement is used on Android.
Those are obviously not problems which fundamentally break or jeopardize the utility of the Google/Apple ENF (and therefore apps utilizing it), but it would be great nevertheless  if Google/Apple could get them sorted out in a timely manner (bonus points if they do so in a transparent way by publicly acknowledging/commenting on the issues and keeping us appraised on the progress they make towards their resolution).

We are observing additional deviations of Googles ExposureNotification-BluetoothSpecificationv1.2.pdf.
According to the specification the type of advertising shall bey ADV_NONCONN_IND

During the Bluetooth broadcast, advertisements are to be non-connectable undirected of type ADV_NONCONN_IND [p. 5]

When using Wireshark with nRF52840-DK as Bluetooth sniffer, we are seeing many beacons of type ADV_SCAN_IND as you can see in the screenshot:

The Flags are also omitted by this beacons as shown in the screenshot.

@kabeljan Which Android devices are showing this behaviour?

@mh- I'am observing this deviation on my Huawei P20 lite and P30 lite and also on a Samsung and Motorola Device of my parents (dont know the exact type yet). I will collect further information in the next days. But it seems to me that this could be a general issue.
The question here is, whether the receiving device will reject those "malformed" beacons or not?
Also even if only the both named Huawei devices are affected it is very bad, because I think they are widely used.

Do the Huawei devices still use Google Play Services, or HMS Core („Huawei Mobile Services“)?
I believe these beacons will be scanned without problems.   But you can check yourself by looking at the logs (logcat) - do you have adb installed on a computer?

@mh- I dont know if my Huawei devices are using HMS instead of Google Play, but i checked the behavior today with two other phones from my colleagues. I'am observing the "malformed" beacons with a Google Pixel 3 and a Samsung Galaxy A50.
To quick check malformed Beacons you can simply use the nrfConnect Android App. You can see there Beacons with a Connect-Button which indicates the wrong type, without Flags (see Screenshots).

I believe these beacons will be scanned without problems. But you can check yourself by looking at the logs (logcat) - do you have adb installed on a computer?

Unfortunately I have no adb installed, but i can check this in the next days. Thanks for this advice :)


iPhone can´t delete modules

Opening the demo in my iPhone:
https://jerosoler.github.io/Drawflow/
When I try to remove module holding down the screen, the module text is selected but not the delete option appear.
Thanks, congratulations for the good job :)

Uploading RPReplay_Final1703285932.mov…

Hi! @JTorresConsulta
In this case we use the "user-select" property. It seems that iPads and iPhones do not detect it correctly.
I don't have an iPhone to test, but it could be that disabling the "touch-action" property works.
https://developer.mozilla.org/en-US/docs/Web/CSS/touch-action
If you haven't found this issue on stackoverflow:
https://stackoverflow.com/questions/16613503/webkit-user-select-none-not-working
That's also a demo! Of some library functionalities.

More info:
https://www.designcise.com/web/tutorial/how-to-fix-issues-with-css-user-select-none-not-working

Hi @jerosoler !
Yes I tried disabling the touch and selection but iPhone navigators do not recognize the "right" click of mouse, then the X symbol to delete nodes not appear :(
Whath is the function where this is triggering?
Is possible to trigger with double click event too?
Thanks !! <3

Try add event dobleclick:
    editor.container.addEventListener('dblclick',(e) =>  {
        if(editor.node_selected !== null) {
            editor.contextmenu(e);
        }
    });


[BUG] - [vite] Internal server error: [postcss] Cannot read properties of undefined (reading 'toLowerCase')

NextUI Version
2.1.10
Describe the bug
[vite] Internal server error: [postcss] Cannot read properties of undefined (reading 'toLowerCase')
Plugin: vite:css
File: /Users/eyucherin/Desktop/frontend/service/src/index.css
at userAgentContains (/Users/eyucherin/Desktop/frontend/service/node_modules/framer-motion/dist/cjs/index.js:4223:25)
at /Users/eyucherin/Desktop/frontend/service/node_modules/framer-motion/dist/cjs/index.js:4229:20
at evalModule (/Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/node_modules/jiti/dist/jiti.js:1:255614)
at jiti (/Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/node_modules/jiti/dist/jiti.js:1:253542)
at /Users/eyucherin/Desktop/frontend/service/node_modules/@nextui-org/react/node_modules/@nextui-org/accordion/dist/index.js:44:29
at evalModule (/Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/node_modules/jiti/dist/jiti.js:1:255614)
at jiti (/Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/node_modules/jiti/dist/jiti.js:1:253542)
at /Users/eyucherin/Desktop/frontend/service/node_modules/@nextui-org/react/dist/index.js:29:25
at evalModule (/Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/node_modules/jiti/dist/jiti.js:1:255614)
at jiti (/Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/node_modules/jiti/dist/jiti.js:1:253542)
at /Users/eyucherin/Desktop/frontend/service/tailwind.config.cjs:1:89
at evalModule (/Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/node_modules/jiti/dist/jiti.js:1:255614)
at jiti (/Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/node_modules/jiti/dist/jiti.js:1:253542)
at /Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/lib/lib/load-config.js:37:30
at loadConfig (/Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/lib/lib/load-config.js:39:6)
at getTailwindConfig (/Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/lib/lib/setupTrackingContext.js:71:116)
at /Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/lib/lib/setupTrackingContext.js:100:92
at /Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/lib/processTailwindFeatures.js:48:11
at plugins (/Users/eyucherin/Desktop/frontend/service/node_modules/tailwindcss/lib/plugin.js:38:69)
at LazyResult.runOnRoot (/Users/eyucherin/Desktop/frontend/service/node_modules/vite/node_modules/postcss/lib/lazy-result.js:357:16)
at LazyResult.runAsync (/Users/eyucherin/Desktop/frontend/service/node_modules/vite/node_modules/postcss/lib/lazy-result.js:286:26)
at LazyResult.async (/Users/eyucherin/Desktop/frontend/service/node_modules/vite/node_modules/postcss/lib/lazy-result.js:160:30)
at LazyResult.then (/Users/eyucherin/Desktop/frontend/service/node_modules/vite/node_modules/postcss/lib/lazy-result.js:436:17)
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
The error described above shows when I run my server I am using Vite on Mac and I am trying to incorporate NextUI into my project.
when I comment out the nextui plugin in my tailwind config file, the error disappears but am not able to use nextui. This is inside a monorepo would this be a problem? It seems like some people in my team are not able to reproduce the issue.
postcss looks like the following
module.exports = {
    plugins: {
        tailwindcss: {},
        autoprefixer: {},
    },
};

tailwind looks like the following
import { nextui } from '@nextui-org/react';

/** @type {import('tailwindcss').Config} */
module.exports = {
    content: [
        './src/**/*.{js,ts,jsx,tsx}',
        '../component/src/**/*.{js,ts,jsx,tsx}',
        './node_modules/@nextui-org/theme/dist/**/*.{js,ts,jsx,tsx}',
    ],
    theme: {
        extend: {},
    },
    darkMode: 'class',
    plugins: [
        nextui({
            addCommonColors: true,
        }),
    ],
};

Expected behavior
The error mentioned above
Screenshots or Videos
No response
Operating System Version
macOS
Browser
Chrome

Same issue here,

created a new Vite project
followed tailwinds installation guide
followed nextUI installation guide

same here :(

me too

me too too

@eyucherin  Simialr issue here, except I don't get errors when trying to render NextUI components. Instead, the NextUI components I tried to render simply look like plain HTML elements:

Background
Buggy behaviour: The NextUI components I tried to render simply look like plain HTML elements
Repository type: Monorepo (Turborepo)
Package manager: PNPM
Location of the app I'm trying to NextUI into: /packages/portal
Type of application: Next.js + Typescript + page-based routing + tRPC
Version of tailwindcss installed: 3.3.6
Version of postcss installed: 8.4.32
Version of autoprefixer installed: 10.4.16
Version of framer-motion installed: 10.16.16
Version of @nextui-org/react installed: 2.2.9
My tailwind.config.css
import { nextui } from '@nextui-org/react';

/** @type {import('tailwindcss').Config} */
const config = {
  content: [
    "./src/**/*.{js,ts,jsx,tsx,mdx}",
    './node_modules/@nextui-org/theme/dist/**/*.{js,ts,jsx,tsx}',
  ],
  theme: {
    extend: {},
  },
  darkMode: 'class',
  plugins: [nextui()],
};

export default config;

My postcss.config.js:
module.exports = {
  plugins: {
    tailwindcss: {},
    autoprefixer: {},
  },
}

According to the doc, i also had to setup pnpm .npmrc, so I did, like this:
My .npmrc in /packages/portal/ folder (where I want to use NextUI):
public-hoist-pattern[]=*@nextui-org/*

My .npmrc at root folder:
auto-install-peers = true
save-exact=true

⚠ Other miscellaneous findings:
After I installed @nextui-org/react into packages/portal Next.js app, the packages/node_modules only has @nextui-org/react package, but all the actual components are in the node_modules of the root folder...
My questions:

Why do you think is this happening?
Is it intentional by design?
Could this be the reason I cannot render NextUI components properly?
How to I render them properly?

Node modules of the Next.js app

Node modules of the monorepo root folder

Update - I manually moved the @nextui-org folder from root folder node_modules into packages/portal/node_modules, the components are now starting to work - aka rendering the same way as on the doc.
I just need to find out why @nextui-org gets installed in the root directory. I suspect it's got something to do with public-hoist-pattern[]=*@nextui-org/* in the .npmrc file

All I had to do was switch to a more recent Tailwind configuration.
OLD
import { nextui } from '@nextui-org/react';

/** @type {import('tailwindcss').Config} */
const config = {
  content: [
    "./src/**/*.{js,ts,jsx,tsx,mdx}",
    './node_modules/@nextui-org/theme/dist/**/*.{js,ts,jsx,tsx}',
  ],
  theme: {
    extend: {},
  },
  darkMode: 'class',
  plugins: [nextui()],
};

export default config;

NEW
const { nextui } = require("@nextui-org/react");

/** @type {import('tailwindcss').Config} */
module.exports = {
      content: [
    "./src/**/*.{js,ts,jsx,tsx,mdx}",
    './node_modules/@nextui-org/theme/dist/**/*.{js,ts,jsx,tsx}',
  ],
  theme: {
    extend: {},
  },
  darkMode: "class",
  plugins: [nextui()],
};

@eyucherin Similar issue here, except I don't get errors when trying to render NextUI components. Instead, the NextUI components I tried to render simply look like plain HTML elements:
Background
Buggy behaviour: The NextUI components I tried to render simply look like plain HTML elements Repository type: Monorepo (Turborepo) Package manager: PNPM Location of the app I'm trying to NextUI into: /packages/portal Type of application: Next.js + Typescript + page-based routing + tRPC Version of tailwindcss installed: 3.3.6 Version of postcss installed: 8.4.32 Version of autoprefixer installed: 10.4.16 Version of framer-motion installed: 10.16.16 Version of @nextui-org/react installed: 2.2.9
My tailwind.config.css
import { nextui } from '@nextui-org/react';

/** @type {import('tailwindcss').Config} */
const config = {
  content: [
    "./src/**/*.{js,ts,jsx,tsx,mdx}",
    './node_modules/@nextui-org/theme/dist/**/*.{js,ts,jsx,tsx}',
  ],
  theme: {
    extend: {},
  },
  darkMode: 'class',
  plugins: [nextui()],
};

export default config;

My postcss.config.js:
module.exports = {
  plugins: {
    tailwindcss: {},
    autoprefixer: {},
  },
}

According to the doc, i also had to setup pnpm .npmrc, so I did, like this:
My .npmrc in /packages/portal/ folder (where I want to use NextUI):
public-hoist-pattern[]=*@nextui-org/*

My .npmrc at root folder:
auto-install-peers = true
save-exact=true

My global.css which sits in packages/portal/src/styles/
@tailwind base;
@tailwind components;
@tailwind utilities;

My _app.tsx from packages/portal/src/pages/
import { type AppType } from 'next/app';
import { NextUIProvider } from '@nextui-org/react';
import { api } from '@/utils/api';
import<EMAIL_ADDRESS>
const App: AppType = ({ Component, pageProps }) => {
  return (
    <NextUIProvider>
      <Component {...pageProps} />
    </NextUIProvider>
  );
};

export default api.withTRPC(App);

Note: I'm using aosolute import path alias, which means import<EMAIL_ADDRESS>could've been import '../styles/global.css';
⚠ Other miscellaneous findings:
After I installed @nextui-org/react into packages/portal Next.js app, the packages/node_modules only has @nextui-org/react package, but all the actual components are in the node_modules of the root folder...
My questions:

Why do you think is this happening?
~Is it intentional by design?~ - No
~Could this be the reason I cannot render NextUI components properly?~ - Yes
~How do I render them properly?~ - Make sure the @nextui-org folder is in the node_modules of the app that you want to integrate NextUI into

Node modules of the Next.js app
Node modules of the monorepo root folder

Do you have any updates on the node_modules behavior ? i have the same problem i can't make it work...

Update - I manually moved the @nextui-org folder from root folder node_modules into packages/portal/node_modules, the components are now starting to work - aka rendering the same way as on the doc.
I just need to find out why @nextui-org gets installed in the root directory. I suspect it's got something to do with public-hoist-pattern[]=*@nextui-org/* in the .npmrc file

Do you have any updates on this ? I have the same issue...

You only add the following line when you are using pnpm.
public-hoist-pattern[]=*@nextui-org/*

You may refer to our vite template: https://github.com/nextui-org/vite-template


(optionally) Use CSL object ID as bibtex citation key

The current default {author}{year}{title} scheme doesn't work well with e.g. literal names, and we've got an ID just sitting there not doing anything.

Are literal names a problem because of reserved characters (like spaces), or are they processed wrong? Either way, would something like this work for you?
plugins.config.get('@bibtex').generateLabels = false // and get them from `id` instead

That's easy for me because it wouldn't be a breaking change then, but I don't know how you're using Citation.js so I don't know if that would work for you.

My use case is a tool called citepy which fetches citation data from the python package index and dumps it out as CSL-data JSON, but can obviously only get a raw string for the author (as it might be multiple people, an organisation, etc). I'm then recommending people use citation-js as a command line utility (so not much I can do on the js end) to convert the CSL-data JSON into bibtex/citations.
From what I can tell, the default when the only name is literal is to use nameyeartitle, but that means I end up with e.g.
"Travis Oliphant et al.2019numpy"
As the citation key in my bibtex output, which is unwieldy. But I've already defined what I want the ID to be in the CSL-data's ID field - a command line switch to use it would be great!

For the CLI:
citation-js -i INPUT -s bibtex --formatter-options generateLabel=false

Also, I included a fix which should make the author names, and not just the title, safe for usage as a BibTeX key. Both will be available in the next update.


Hotspot creation

I am trying to create hotspot using this plugin i used method cordova.plugins.hotspot.createHotspot("myHS", "WPA2PSK", "pass@123", successCB, errorCB);
when this method is invoked wifi gets switch off and I got error to start hotspot as "Got unknown error during hotspot start"

Strange. Have to look what may cause. But currently don't have much time for this

can you please attach the message which is passed to errorCB?

Hi,
I have the same problem when I try to create the hotspot. The message passed to errorCB  is:
"Hotspot start failed.: Attempt to invoke interface method 'java.util.Iterator java.util.List.iterator()' on a null object reference".
Best!

please retry with latest master:
cordova plugin add https://github.com/hypery2k/cordova-hotspot-plugin.git

and report here again

Hi,
and thank you for the help.
I have just retried using the latest master but I still get an error message, a bit different than the previous one:
"Unknown error during hotspot configuration: Attempt to invoke interface method 'java.util.Iterator java.util.List.iterator()' on a null object reference".
Thanks

can you please retry again. Should be working now

Great! now it working!!!

Hi,
yes! It works!
Now, the plugin is able to create the hotspot (calling  cordova.plugins.hotspot.createHotspot(.....) ) fine. Besides it does the network configuration in the right way including network mode and password.
Thank you!
Now I have to play with the plugin in order to better understand how it works.
I have a doubt: sofar, each  time I run my App I create the hotspot, maybe what I have to do is create the hotspot only at the first run of the App or when the hotspot doesn't exist, and then only start and stop the hotspot.
Thank again.
Paolo

I've released version 1.1.2
Regarding you're question. You can enable or disable only the hotspot too: https://github.com/hypery2k/cordova-hotspot-plugin/blob/master/PLUGIN_USAGE.MD#cordova.plugins.hotspot+startHotspot https://github.com/hypery2k/cordova-hotspot-plugin/blob/master/PLUGIN_USAGE.MD#cordova.plugins.hotspot+stopHotspot


Feature request: Clippy viewer

Something that'd be cool for VSCode is a little panel that updates whenever you update code, running cargo clippy --all-targets --all-features or whatever. This allows you to visualize what you need to fix, whether it's a warning or an error. It could have different icons represneintg different things, but would be very helpful.

You can use "rust-analyzer.checkOnSave.command": "clippy" to run cargo clippy instead of cargo check.

I know. But, it'd be cool if there was a panel parsing cargo clippy. This'd be good for people trying to fix there bugs

VSCode already has the problems pane which shows both errors and warnings. If rustc or clippy has a suggestion to fix the problem, you can apply it there most of the time.

I know but that's not what I meant, thanks anyway.


docs: fix nightly-build badge reference

Fixes no issue
Description
Checklist

[x] PR is rebased to/aimed at branch develop
[x] PR follows Contributing Guide
[x] Added tests (if necessary)
[x] Extended README/Documentation (if necessary)
[x] Adjusted versions of image and Helm chart in values.yaml and Chart.yaml (if necessary)

Codecov Report
Patch and project coverage have no change.

Comparison is base (76f0850) 97.13% compared to head (242de95) 97.13%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #924   +/-   ##
========================================
  Coverage    97.13%   97.13%
========================================
  Files           23       23
  Lines         1290     1290
========================================
  Hits          1253     1253
  Misses          37       37

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

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


app homescreen slow to open - UX improvement

this is more to tag as an improvement and isnot a bug issue
it is from feedback to several test users.
one of the first UX issue is that the main app screen is quite slow to appear.
if we compare to whatsapp or other xmpp messenger.
vector android is full white during several seconds this give a lag impression long enough to think :

"next time i will go faster with blablabla app"

it seems matrix console have the same issue.
i do not know if the sdk/api allows to change this easily

We need to improve the application storage.
We don't use a SQL lite store but a filesystem one because it was easier to implement first.
This filesystem store is quite slow to load at application launch.


Include area in notifications

Checklist

[ x] I checked for similar existing requests (both open and closed) before posting.
[ x] My request is generic, other users may benefit from it too.

Proposal
Device area in notifications would be useful.
Additional info
Example notification: Alarmo is triggered. Window in bedroom is open.

Not everyone (including myself) uses areas in HA so it would be difficult to make a generic implementation for this.
Wouldn't it be better to rename the entity to 'bedroom window sensor' such that you can identify it by its name?

+1


WARNING - socket closed

What does this mean?
After this warning this happens...
WARNING - socket closed ERROR (2)- refreshCurrentActivity TimeoutError: Can't open WebSocket within allowed timeout: 10000 ms. - Stack : TimeoutError: Can't open WebSocket within allowed timeout: 10000 ms.     at PromiseController._handleTimeout (/home/hoobs/.hoobs/node_modules/promise-controller/src/index.js:172:19)     at Timeout.<anonymous> (/home/hoobs/.hoobs/node_modules/promise-controller/src/index.js:178:43)     at listOnTimeout (internal/timers.js:549:17)     at processTimers (internal/timers.js:492:7)
INFO - Loading activities... Error - Error retrieving info from hub : Error: connect EHOSTUNREACH xxx.xxx.xxx.xxx:8088-(445)
The hub and the remote works just fine even with this message. Only homebridge is affected and I don't know why.
After this the connection is gone and restart the service does not work. I have to disconnect the Hub to get it work again.

Hi, could you sahre your config ? Are you on fix IP or autodiscovery of the hub ? It seems the hub becomes unreachable, maybe in case of IP change.

No, its a fixed IP.
"platform": "HarmonyHubWebSocket",
"plugin_map": {
"plugin_name": "homebridge-harmony"
},
"name": "TV",
"hubIP": "<IP_ADDRESS>",
"cleanCache": false,
"mainActivity": "Fernseher",
"playPauseBehavior": true,
"publishHomeControlsAsIndividualAccessories": true,
"publishDevicesAsIndividualAccessories": true,
"switchAccessories": true,
"showTurnOffActivity": "false",
"TVAccessory": true,
"publishSequencesAsIndividualAccessories": true,
"publishSwitchActivitiesAsIndividualAccessories": true,
"publishGeneralMuteSwitch": false,
"showCommandsAtStartup": false,
"publishHomeControlButtons": true,
"addAllActivitiesToSkippedIfSameStateActivitiesList": true,
"publishGeneralVolumeSlider": false,
"linkVolumeControlToTV": true

Are you on hoobs ? It is clearly a network problem, double check IP on harmony app / network, firewall and so on ... It can't reach your hub on 8088 port, on the given address

Yes, I am on hoobs and I checked everything. Seems ok. But from time to time this happens... and I do not know why. Before 1.3.7 or before hoobs 3.2.4 it works just fine.

I can’t be sure everything works correctly on hoobs sorry, they are doing some stuff out of the my control and I only use legitimate homebridge install sorry !

No problem, thank you.

Further research...
This is a issue with my WiFi Mesh. If the Hub changes WiFi hub/router, ports will not assume.
Already reported this to the manufacturer.

What router are you using ? Orbi ?
If yes (or maybe you can check options), check this thread : https://github.com/nicoduj/homebridge-harmony/issues/240#issuecomment-615557487

No it a common one here in germany. FritzBox from AVM.

Not sure if you guys are still looking at this, but I’m having a similar problem with my hubs and my mesh network.  I have four harmony hubs, an xfinity xFi router and pods, and HOOBS keeps crashing when trying to connect to my hubs.  I’m connecting via hub name, but for some strange reason I keep getting a very similar error.  Now my hubs aren’t showing up properly in homekit.  Is this a common problem with mesh networks?  Any ideas on a fix?

I use mesh router and it works fine. (NEtgear one). some users reported that it works better with 20/40mhz coexistence disabled however (I am running those settings) - see previous comment.
However, it seems that there are more affected users with hoobs, don't really know what they do behind the scene.


Configured new channel in my working BOT for Twilio - Doesn't work.

I have configured a new channel in my working BOT for Twilio. I'm trying to do text message response for a BOT. Everything seems to be configured correctly until I send a message and get the following error in Twilio.
Msg	"Bad Gateway"
sourceComponent	"14100"
ErrorCode	"11200"
EmailNotification	"false"
httpResponse	"502"
LogLevel	"ERROR"
url	"https://sms.botframework.com/api/sms"

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

ID: d0b76e08-962a-2a8e-2453-87fb917d68ec
Version Independent ID: 937798fb-8f76-683c-e146-55dcd79622e1
Content: Connect a bot to Twilio - Bot Service
Content Source: articles/bot-service-channel-connect-twilio.md
Service: bot-service
Sub-service: sdk
GitHub Login: @RobStand
Microsoft Alias: kamrani

@scottker Is the bot replying in emulator/webchat. Did you test it there and check?

We can close this. Twilio does not allow you to sms/voice dial numbers not in the valid number list when you are in Trial mode. Took me a while to figure it out because it throws a generic 502 with bad gateway instead of a more friendly message, but lesson learned.

@scottker  have you  fixed  this  issue ?

I'm having the same error code "11200". My phone number is in the verified list but I keep getting the error.

@zubairshahzad @christian-colon make sure you are on a paid Twilio account. The trial accounts require text messages from "verified caller id's"/ known phone numbers when it's in the trail/unpaid mode. If you don't want to pay to test, you can build a list of validated phone numbers in the Twilio UI (See image) but then you can only test from those numbers.

I have the number from which I am testing in that list but it is still not working. I've doubled check to see if there is another mistake in configuration but no luck yet. Everything is done as the document says. Thank you for your reply.

Yes I have the same error ErrorCode	"11200"
I have paid Twilio account, but when I am testing it is still not working

I solved this activating the Geo Permissions on Programable SMS for my country.

i have paid  account  and registered number twilio number with whatsapp... its working on on custom chatbot url ..  but   by  using this
https://sms.botframework.com/api/sms  azure chatbot not  working

Msg	"Not Found"
sourceComponent	"14100"
ErrorCode	"11200"
EmailNotification	"false"
httpResponse	"404"
LogLevel	"ERROR"
url	"https://sms.botframework.com/api/sms"

what  i enter  in     A MESSAGE COMES IN

i am  doing  for whatsapp

At this date it does not work, I have the same error

Still not working


backend: add Swagger docs to Casibase and show the link in NavBar

Like Casdoor: https://github.com/search?q=repo%3Acasdoor%2Fcasdoor+swagger&type=code
See demo site: https://door.casdoor.com/

Then open: https://door.casdoor.com/swagger/

Update
the Swagger menu item has been added:

Now the Swagger page only has one API, other APIs need to be added via Go comments: https://demo-admin.casibase.com/swagger/index.html


Error during startup operation

Hi, I have the following issue when tryng to launch locally a set of python functions:

What can I do? Thanks in advance

I've solved it reinstalling the core tools

Closing since the issue has been resolved. Thank you.


Unable to generate new key pair when using ARM template.

Reporting issue regarding deploying template with "Generate New Key Pair" specified. This does not appear to carry over to the parameters file properly resulting in Invalid Template error code:
Error:
{"code":"InvalidTemplate","message":"Deployment template validation failed: 'The value for the template parameter 'adminPasswordOrKey' at line '36' and column '27' is not provided. Please see https://aka.ms/resource-manager-parameter-files for usage details.'."}
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 25b616b7-f52b-2d08-3cc4-b4cfaf6bf9a0
Version Independent ID: 365568da-879f-3212-d2ae-4848df94f64c
Content: Create a Linux VM in Azure from a template - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/create-ssh-secured-vm-from-template.md
Service: virtual-machines
GitHub Login: @cynthn
Microsoft Alias: cynthn

@erjarvin Thank you for bringing this to our attention!  I've assigned this to the document author for further review.

@erjarvin Thanks for reporting this issue. Were you using the "button" to deploy this template, or the CLI?

Also created an issue in the template repo: https://github.com/Azure/azure-quickstart-templates/issues/12216

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close


Recursion overflow while parsing

The console gets bloated with a huge trace saying: too much recursion while parsing
Is this intended?
(I'll provide repro code later)
~ Thanks!

Got where the recursion was coming from, closing it! (I was replacing JSON.parse, so it was being called by this lib also...)


Can it be on Android?

I hope SAM can be on platform: Android 7+ or else.

This will not work on Android.

This will not work on Android.

Bute there is idledaddy on Android that can "run" the game?

This will not work on Android.

Bute there is idledaddy on Android that can "run" the game?

This will not work on Android.

But there is idledaddy on Android that can "run" the game?

idledaddy reinvented things about steam, that's why it can be running everywhere.
you can use is instead.
https://github.com/JustArchiNET/ArchiSteamFarm/releases/


Port server to TypeScript

The entire application will be ported to TypeScript. This PR will start that with the backend.
The API stays pretty close to previous versions, but it is now much more restricted to what the frontend actually needs. I tested the existing frontend and it seems to work fine with the TypeScript API.
The DB schema is close to previous but will require a migration for existing installations - a script for that will be created at some point. That will be delayed until further code upgrades have been performed later in Tietokilta's website project (including some new features).
Server libraries have been updated to the latest major versions, and as a consequence this update requires Node 12 (current LTS) or 14.
The server has seen some major refactorings that make the port much easier. Mainly, the FeathersJS services have been switched away from the hook model, as it's basically impossible to maintain in TypeScript.
Testing
To test the system locally:

Install a MySQL server. Create a database and a user that has access to it (or just use root).
Copy ENV.MD to .env and update MySQL credentials. Everything else should work out of the box.
Run:git checkout feature/typescript-2
npm install --also=dev
npm run compile:client
npm run start:dev

Current status

Server dependencies upgraded to latest
All server files ported to TypeScript
Build working, including autorestart
Utility scripts deleted (see message for 80c8e7a)
Builds without linter errors (only warnings for console)
Many bugs fixed in the process

LGTM :D


Update checkpointing guide with Orbax APIs

Improved the doc:

Timeline and troubleshooting for the auto Orbax-as-backend migration
Guide on using Orbax API to do everything (I love Orbax transforms)
Using the latest jax.jit APIs when showcasing multihost

Also two small bug fixes:

Add orbax_transforms to restore API
Fix an IO bug in restore_checkpoint() that happens when Tensorflow is not installed/used.

Will review @IvyZX Thank you :+1:


Problem with flutter 2.5 web

it is not possible to select the date when using flutter 2.5 web

it is not possible to select the date when using flutter 2.5 web

I have the same issue, can you solve this?


Use currency style in fmtPricePerKWh (fixes #7892)

Didn't actually test it, but this should fix #7892
Implications would be, that two instead of 1 digit would be shown for EUR and USD.
As currency formatting uses the values from here:
https://www.six-group.com/dam/download/financial-information/data-center/iso-currrency/lists/list-one.xml

Strange that CHF formatting breaks completely. The solution you proposed also changes how EUR prices are displayed. Currently These prices are shown as 12,3 ct/kWh. With this change it would be 0,12EUR/kWh. I think this currently not possible with style: "currency" yet. I'll look into this topic, add more unit tests in this area and come up with a solution soon.

Oh, right I actually missed the ct, calculation.
The reason that CHF breaks is that "auto" is not a supported value for minimumFractionDigits.
Let me modify it a bit and tell me what you think.

Looks better, but lettingNumberFormat handle the unit creates the issue, that concatenation with /kWh doesn't work in all cases any more. For some locales the unit is moved to the front.
Example: Locale "en-UK" and currency "GBP" would result in £0.23/kWh
Another thing that we have to think about. The savings dialog uses a large number, small unit formatting. See screenshot

This is currently achieved by splitting the result of fmtPricePerKWh. This is ugly and we'll need to improve this to be more flexible (e.g. allow " " as a thousand separator).
https://github.com/evcc-io/evcc/blob/master/assets/js/components/Savings.vue#L177-L182
Suggestion for a quick solution: We'll keep format: decimal and just remove let minimumFractionDigits = "auto"; This seems to be the issue why it doesn't work at all right now.
Suggestion for a better solution: We make a list of the desired formates energy prices are specified in different countries (the British e.g. seem to use 23.4p/kWh), make test cases and try to come up with better and more optimized solution.


change contributing steps from installing pnpm@7 to pnpm@8

Unable to run contributing steps due to:
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your pnpm version is incompatible with "/Users/ryan/Code/graphql-yoga".

Expected version: >=8.6.1
Got: 7.33.6

This is happening because the package's manifest has an engines.pnpm field specified.
To fix this issue, install the required pnpm version globally.

This will bump the pnpm version to 8 in the steps for creating a failing test case.

Good catch thank you !


Polymer ui for desktop?

Why arent we using Polymer to build the desktop version of dartpad? Or is this in the works?

I think the plan is to use also the paper elements from polymer 1.0 for the desktop UI indeed.

I would really like to help on this in my spare time. I'm really busy with
a big project at work right now, but I would love to put spare time towards
it!
On Thu, Jun 4, 2015, 11:02 AM Kasper Peulen<EMAIL_ADDRESS>wrote:

I think the plan is to use also the paper elements from polymer 1.0 for
the desktop UI indeed.
—
Reply to this email directly or view it on GitHub
https://github.com/dart-lang/dart-pad/issues/461#issuecomment-108948937.

awesome :) can't wait too see a PR ! ^^
Maybe a good first step would be to first porting the feature we have for the desktop UI to the mobile UI, like the code completion and quick fixes, and then kind of forking the mobile UI at some point to make the desktop UI ?
Thoughts @devoncarew @lukechurch ? btw, we have a chat at https://gitter.im/dart-lang/dart-pad if you want some direction maybe

Sounds good! Sorry been busy at work, I'm a junior software engineer for
DataLocker by day haha. I'll mess around tonight and see what I can come up
with.
On Thu, Jun 4, 2015, 2:45 PM Kasper Peulen<EMAIL_ADDRESS>wrote:

awesome :) can't wait too see a PR ! ^^
Maybe a good first step would be to first porting the feature we have for
the desktop UI to the mobile UI, like the code completion and quick fixes,
and then kind of forking the mobile UI at some point to make the desktop UI
?
Thoughts @devoncarew https://github.com/devoncarew @lukechurch
https://github.com/lukechurch ? btw, we have a chat at
https://gitter.im/dart-lang/dart-pad if you want some direction maybe
—
Reply to this email directly or view it on GitHub
https://github.com/dart-lang/dart-pad/issues/461#issuecomment-109027869.

Hey @jgw96 @kasperpeulen,
Awesome to see your enthusiasm on this.
At the moment, we'd like to stabilise the desktop UI for a bit, especially as we prove out what it will feel like when we embed this into other sites such as the docs, and the dartlang site. This is not to say we won't be transition the desktop UI, but it won't be happening immediately.
If you want to explore substantial changes to the UI technology stack, the mobile site is probably the best place to start, or you can use the services backend and start a new front end project.
If you want to write UI code, something like this: https://github.com/dart-lang/dart-pad/issues/374 would be a fantastic addition.
@jgw96 If you're just starting with contributing to the project, I'd encourage you to start off with a couple of our smaller issues to get a feel for the workflows and code review cycles. Looking forwards to seeing them!
Hope this helps give you a bit more info on where we're going, keep up the great work.
Luke


git: post pull command. retries after pull failure.

Post pull command can now be added using then.
Relative paths are now accepted.
Syntax:
then cmd [args]

Example usage with Hugo
git github.com/user/site {
    path  ../
    then  /usr/local/bin/hugo --destination=/home/user/hugosite/public
}

root /home/user/hugosite/public

:100:


Is there documentation on how to use a Build Artifact? Or is there any alternate approach to 'check out once'?

Is your feature request related to a problem? Please describe.
I'm attempting to "check out once," build (and apply environment-specific variables)  and deploy to separate environments. Originally, I was thinking I could re-use this action for all of my deploys (dev, staging, production, for example) but I am struggling a little with how to make sure I only check out the code from the repository once and use that same "snapshot" of the code to avoid checking out in every workflow step.
Describe the solution you'd like
I was searching how others have accomplished this, but I haven't found much. It would be nice to leverage an artifact or some other mechanism for only checking out once from the repo, but still applying env variables during each build and deploy.
Describe alternatives you've considered
I tried leveraging a built artifact this way: app_location: '/dist/apps/<myAppName>' and skip_app_build: true .. I also tried app_location: '/' but am starting to wonder if I needed to also unzip the build artifact or taken a different approach.
Additional context
This action has surpassed my expectations so far -- there is likely just a misunderstanding or a missed reference that does what I am requesting.

I haven't tried this specific scenario, but I have written a blog post on how to create a very custom CI/CD pipeline with SWA - https://www.aaron-powell.com/posts/2022-07-20-taking-a-swa-devops-pipeline-to-the-next-level/
That might offer a starting point for what you're trying to accomplish.

Not sure whether you're using GitHub Actions or Azure DevOps pipelines for your deployments, but I've been doing a very similar process to Aaron in DevOps.
Here's a very basic pipeline:
- stage: Build
  jobs:
  - job: Build
    steps:
    - script: |
          npm ci
      workingDirectory: $(System.DefaultWorkingDirectory)/frontend/
      displayName: "npm install"

    - script: |
        npm run build
      workingDirectory: $(System.DefaultWorkingDirectory)/frontend/
      displayName: "npm run build"

    - task: ArchiveFiles@2
      inputs:
        rootFolderOrFile: $(System.DefaultWorkingDirectory)/frontend/build/
        includeRootFolder: false
        archiveType: "zip"
        archiveFile: $(build.artifactStagingDirectory)/drop/site.zip
        replaceExistingArchive: true
      displayName: "Package site output"

    - task: PublishBuildArtifacts@1
      inputs:
        artifactName: "site"
        pathToPublish: $(build.artifactStagingDirectory)/drop/site.zip
      displayName: "Publish site deployment artifacts"

- stage: DevDeploy
  dependsOn:
  - Build
  condition: succeeded()
  jobs:
  - deployment: Dev
    environment: "Dev"
    strategy:
      runOnce:
        deploy:
          steps:
          - download: none
          - task: DownloadPipelineArtifact@2
            displayName: "Download the site"
            inputs:
              source: current
              artifact: site

          - task: ExtractFiles@1
            displayName: "Extract files"
            inputs:
              archiveFilePatterns: "$(Pipeline.Workspace)/**/site.zip"
              cleanDestinationFolder: true
              destinationFolder: "$(System.DefaultWorkingDirectory)/site/deploy/"

          - task: FileTransform@2
            displayName: 'Apply JSON Transforms'
            inputs:
              folderPath: '$(System.DefaultWorkingDirectory)/site/deploy/'
              fileType: 'json'
              jsonTargetFiles: '**\staticwebapp.config.json'
              xmlTransformationRules: '' # disabled

          - task: AzureStaticWebApp@0
            displayName: "Deploy Static App"
            inputs:
              cwd: $(System.DefaultWorkingDirectory)/site
              app_location: "deploy" # App source code path relative to cwd
              api_location: "deploy-function"
              skip_app_build: true
              skip_api_build: true
              output_location: "" # Built app content directory relative to app_location - optional
              azure_static_web_apps_api_token: $(deploymentToken)

You're right that you need to unzip the artifact during the deployment step so that the files can be deployed into the container, this also allows you to run the FileTransform task over the staticwebapp.config.json and perform variable replacement based on variables in your library.

I really can't believe this isn't easily possible. There's nothing about this in the documentation. What if you just need to deploy and save the artifact? It would be easier just using one of the APIs at this point.

When you have to jump through that many hoops just to get something that satisfies the two fundamental requirements of 1) getting compiled and deployed to the server and 2) saving what was deployed for in case it's needed for future reference, it feels like there must be better options

When you have to jump through that many hoops just to get something that satisfies the two fundamental requirements of 1) getting compiled and deployed to the server and 2) saving what was deployed in case it's needed for future reference, it feels like there must be better options. I will look at the swa cli, it looks better for this scenario

Agree that the docs were a bit light, but the build steps I posted above are near identical to what we're doing for standard (non-static) web apps, so didn't feel like much of a problem to have the exact solution you are looking for:

Single build step that creates a pipeline package you can retain for future reference.
Deploy that package to one or more servers as needed.

The only reason we're jumping through these hoops is because we want to retain/reuse the package. The process to compile and deploy the code can be done in a pipeline with just the AzureStaticWebApp@0 task, no hoops involved.
The arguments that I seem to get most against retaining or reusing the build are:

Why bother? If you have a properly configured package.json and lock file for your tooling, that define the versions of your tools and references, building in a CI environment will recreate the same package from the same commit (it won't exactly, but usually it's close enough).
You can't - the builds often have build-time variables that are environment specific, so you need to build the package to target the environment, and can't reuse it.

Why bother?

Okay, I'm just coming ack to this now with a fresh head and I will take another look at your example, and see how the GitHub workflow equivalent would work.
The thing with the SWA deployment documentation (whether github or pipelines), is that it makes no mention of Oryx, especially given there so many sites a mix different languages and frameworks now.
Watching that thing find and attack everything compile-able file in your repo is a bit off-putting, and isn't usually what you think you want (I'm probably oversimplifying how it works but you get the point). Indeed it wasn't, I had to find out what environment variables to set to to stop it going for node stuff.

Agree that the docs were a bit light, but the build steps I posted above are near identical to what we're doing for standard (non-static) web apps, so didn't feel like much of a problem to have the exact solution you are looking for:

Yeh if it's used for for standard Azure App Service deployment, I'm behind the times a little.


Gadgetbridge & BangleApps: Timezone Issue?

I'm using CET+1 but since last week CEST+2.
And this generates some troubles:
Round about every 30 minutes, the Watch adjusts itself back to CET+1 (looks like), because i.E. it shows 15:30 when it is 16:30.
Long Press on BTN3 restarts the Watchface and it's in the correct time again.
I have adjusted in the Settings Locale=>Timezone to 2.
I guess there must have been something with Gadgetbridge, because when turning off Blutooth on the Phone, the Bangle keeps the correct time.
It worked perfect on CET+1, the problem occured when changing the timezones.
Phone should be set correct, because it shows the correct time.
I'm recendly updated everything on Bangle to the newest available versions and using Gadgetbridge V 0.43.0

That is indeed a Gadgetbridge issue combined with the fact that the Bangle can't yet deal properly with daylight savings. See discussion here:
http://forum.espruino.com/conversations/345273/
It should already be taken care of though, at least on the Gadgetbridge side of things. The 0.43.1 release should be here very soon judging by the activity on Codeberg:
https://codeberg.org/Freeyourgadget/Gadgetbridge/src/branch/master/CHANGELOG.md

Yes - closing this. I'm pretty sure if you disable Gadgetbridge for now (or update it when the new release is available) it should be sorted.


adding stock price functionality

Thank you for taking the time to contribute! This is sincerely appreciated. 😇

Hey No problem man this seems like a really fun project I wish to add a couple more modules can you help me integrate and setup wit.ai?

1 test seems to be failing.


[BUG] Volume has multiple instance managers

Describe the bug
A volume is stuck with multiple instance manager registred. It is marked as healthy but not ready for workload.

Environment

Longhorn version: 1.4.3 (bundled with harvester 1.2.1)
Impacted volume (PV): pvc-3e779637-4ea1-4469-a304-4fd88c040c2a

cc @ejweber @PhanLe1010

Ref: https://github.com/longhorn/longhorn/issues/8197#issuecomment-2005116550

cc @Vicente-Cheng as well


Provide .editorconfig file

Not everyone uses IntelliJ. Please provide EditorConfig file for configuring line-endings, tabs/spaces, indentation size and such.

Sound slike a good idea, could you make this?


Add validation context provider

Description:
Add certificate validation context config provider and refactor ContextConfigImpl. Make static and inline CertificateValidationContext utilize it. This is independent of PR #4256. Once #4256 is in, next step is to support fetching CertificateValidationContext via validation_context_sds_secret_config.
Risk Level: Low
Testing: unit test, integration test
Docs Changes: N/A
Release Notes: N/A
Signed-off-by: Jimmy Chen<EMAIL_ADDRESS>

cc @lizan @htuch @PiotrSikora @qiwzhang

friendly ping?


Add depends_on annotation check

Ref. https://issues.redhat.com/browse/HACBS-2308

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@3f35fa6). Click here to learn what that means.
The diff coverage is 100.00%.

:exclamation: Current head 279a686 differs from pull request most recent head 4d38587. Consider uploading reports for the commit 4d38587 to get more accurate results

Additional details and impacted files

@@           Coverage Diff            @@
##             main      #530   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?        71
  Lines           ?      2099
  Branches        ?         0
========================================
  Hits            ?      2099
  Misses          ?         0
  Partials        ?         0

Impacted Files
Coverage Δ

checks/annotations.rego
100.00% <100.00%> (ø)

checks/annotations_test.rego
100.00% <100.00%> (ø)


rds.rdsinstance: Add storage autoscaling (MaxAllocatedStorage)

Description of your changes
Add storage autoscaling parameter MaxAllocatedStorage.
This parameter defines the upper limit to which Amazon RDS can automatically
scale the storage of the DB instance.
For more information about this setting, including limitations that apply
to it, see Managing capacity automatically with Amazon RDS storage autoscaling
(https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_PIOPS.StorageTypes.html#USER_PIOPS.Autoscaling)
in the Amazon RDS User Guide.
Make rds.CreatePatch exclude AllocatedStorage if autoscaling is enabled,
and the requested AllocatedStorage is lower than was is currently
allocated.
This allows a user to manually scale up storage even if autoscaling is
enabled, and prevents crossplane from attempting to scale down if
AWS has performed autoscaling.
One problem is that this change silently ignores any attempts to manually
downscale when autoscaling is enabled. Since downscaling is not
supported and it is not possible to distinguish this from autoscaling, I
don't see any other solutions.
I have added tests to verify the logic for omitting StorageSize and the
up to date-test:
--- FAIL: TestObserve (0.00s)
    --- FAIL: TestObserve/AutoscaledStorageIsUpToDate (0.00s)
        rdsinstance_test.go:354: r: -want, +got:
              managed.ExternalObservation{
              	ResourceExists:          true,
            - 	ResourceUpToDate:        true,
            + 	ResourceUpToDate:        false,
              	ResourceLateInitialized: false,
              	ConnectionDetails:       nil,
              	Diff:                    "",
              }
--- FAIL: TestUpdate (0.00s)
    --- FAIL: TestUpdate/AutoscaleExcludeStorage (0.00s)
        rdsinstance_test.go:674: r: -want, +got:
              interface{}(
            + 	e"cannot modify RDS instance: AllocatedStorage must not be set when on a modify request when AWS has autoscaled the storage",
              )

Fixes #661
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Add unit test for IsUpToDate and Modify
Test scaling up by filling disk,  verified that we don't hang on forever trying to scale down (thanks @petteja)
Test scaling up manually in the console, verified that we don't hang on forever trying to scale down
Tested manually scaling up by bumping the allocated storage in the CR - still works

/size M

Rebased and retested.
-- Fill disk (too fast for "graceful" autoscaling)
CREATE TABLE large_test (num1 bigint, num2 double precision, num3 double precision);
INSERT INTO large_test (num1, num2, num3)
  SELECT round(random()*10), random(), random()*142
  FROM generate_series(1, 200000000) s(i);

apiVersion: database.aws.crossplane.io/v1beta1
kind: RDSInstance
metadata:
  name: example-rds
spec:
  forProvider:
    allocatedStorage: 20
    maxAllocatedStorage: 60
    autoMinorVersionUpgrade: true
    backupRetentionPeriod: 0
    copyTagsToSnapshot: false
    dbInstanceClass: db.t2.micro
    deletionProtection: false
    enableIAMDatabaseAuthentication: false
    enablePerformanceInsights: false
    engine: postgres
    engineVersion: "12.4"
    masterUsername: adminuser
    multiAZ: false
    publiclyAccessible: true
    region: us-east-1
    storageEncrypted: false
    storageType: gp2
  writeConnectionSecretToRef:
    name: example-rdsinstance-out
    namespace: crossplane-system

@chlunde can you rebase again ? testet the future it is working

@haarchri rebased


New module: Scuttlebutt RPC

Adds a new module that encodes and decodes messages according to the Secure Scuttlebutt protocol. See https://ssbc.github.io/scuttlebutt-protocol-guide/#rpc-protocol for more info.

Note that this covers the binary encoding of RPC messages, but there will be more to cover with specific RPC messages down the road. As those messages are not specified in the protocol guide, they will be part of a separate pull request.


polymer 0.12.0 @published setter not call?

Originally opened as dart-lang/sdk#20602
This issue was originally filed by<EMAIL_ADDRESS>
@published
String get foo => readValue(#foo);
set foo(String value) {
  writeValue(#foo, value);
  window.console.log(value);
  window.console.log(foo);
}
test in chrome 36 or chromium 37, log not see value and foo.

 Comment by zoechi

Have you tried @PublishedProperty(reflect: true) instead of @published?
You code doesn't show how you set the value therefore I can't tell if this would change anything.

This comment was originally written by<EMAIL_ADDRESS>
see the follow sample:
<!DOCTYPE html>

    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Sample app</title>

    <link rel="import" href="packages/polymer/polymer.html">

    <polymer-element name="x-b" attributes="refNumber">
      <template>

Number in the b: {{ refNumber }}

      </template>
    </polymer-element>

    <polymer-element name="x-a">
      <template>

Number in the a: {{ number }}

        <button on-click="{{ countClick }}" type="button">click count in a</button>
        <x-b refNumber="{{ number }}"></x-b>
      </template>
    </polymer-element>

    <x-a></x-a>

console log can't see any setter refNumber call, why? the polymer 0.12.0 published new syntax not good!

 Comment by floitschG

Added Area-Pkg, Pkg-Polymer, Triaged labels.

This comment was originally written by<EMAIL_ADDRESS>
the set refNumber(int value) {
          writeValue(#refNumber, value);
          window.console.log("B value: ${value}");
          window.console.log("B refNumber: ${refNumber}");
        }
not call?

This comment was originally written by<EMAIL_ADDRESS>
I understand what<EMAIL_ADDRESS>and<EMAIL_ADDRESS>said.
But, with polymer 0.12.0 published old syntax:
  List<dynamic> _dsRows = [];
  @published
  List<dynamic> get dsRows => _dsRows;
  set dsRows(List<dynamic> value) {
    _dsRows = notifyPropertyChange(#dsRows, _dsRows, value);

    showStartIndex = 0;
    showEndIndex = 0;
    showPosIndex = -1;
    selectIndex = 0;
    ...
    more some my init code...
  }
change to polymer 0.12.0 published new syntax, how do i do?

 Comment by jakemac53

I don't know if this would work for you, but if you just need to update some other internal state in your object you can put that in the dsRowsChanged method:
void dsRowsChanged(oldValue, newValue) {
  ...
}

This comment was originally written by<EMAIL_ADDRESS>
in some case, set the published attribute value, initialization work needs to be done.
with polymer 0.12.0 published new syntax, give me solution.

 Comment by jakemac53

As far as I can tell, this is working as intended. The refNumber attribute on x-b is never directly being set, only its bound value is changing through the x-a number attribute being set (in the countClick method). If you put this same code in for the number attribute on x-a the setter does in fact get called.
sigmund@ can you confirm this is the desired behavior?

cc @sigmundch.

 Comment by jakemac53

Added AsDesigned label.

 Comment by sigmundch

correct, the setter is only called when you access the property programmatically.
It's a bit strange, but the attribute-binding will internally update the value in a binding object, without going through the setter. However, if you read refNumber you'll see the new value.

This comment was originally written by<EMAIL_ADDRESS>
Thanks<EMAIL_ADDRESS>i will try dsRowsChanged, that's may be good idea.


GCOV not working (IDFGH-13762)

hello,
i am working on implementing GCOV in ESP32,
and i got an example code of GCOV given in SDK and i am using ESP32-wroom-32E,
and i am using external j-link with OpenOCD version v0.12.0-esp32-20240318.
when i follow the steps given in example code readme file,
https://github.com/espressif/esp-idf/blob/master/examples/system/gcov/README.md
so when i try send command esp gcov dump in telnet i got this error,

any solution for this.

Hello,
Same issue for ESP32C3 was faced by me
Issue can be solved by running OpenOCD with help of in built JTAG of ESP32C3, simply debug the Code in IDE and open the telnet connection in Different IDF terminal as you have done here, Parallelly observe logs and follow the steps in the README file.
After running telnet session and executing "esp gcov dump" command you should get following output.

Once you are done with it, .gcda file will be generated in build directory, now to generate Coverage Report run "cmake --build build/ --target gcovr-report", make sure you have installed gcovr with command "pip install gcovr". These commands are to be run in IDF terminal.

@gjs-1 As I see from the screenshot, your first problem is related to OpenOCD connection.. Please check the wires to the Jlink. And your OpenOCD script must be something like
openocd -f tcl/interface/jlink.cfg -f tcl/target/esp32.cfg

thank you @kdaksh8, I have tried for my ESP kit and it works perfectly.


typechain: Add missing peer dependency on typescript

The peer dependency on typescript is required to satisfy the peer dependency requirements of ts-essentials.
Adding the peer dependency eliminates a warning in our build which uses typechain.
Thanks for a great tool!

⚠ No Changeset found
Latest commit: a380418
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR

Sorry for being daft, but should I add a changeset? I'm happy to if that's the case :-)


added Ember Borja remote company to companyData

I added Tiger Pistol as a remote company to companyData as this is where I currently work

/assign @joekr


[BUG] Rancher Crashing due to Fake Player API

Description:
Indrev's fake player api is conflicting with Kyori Adventure API, which is also I believe cafeteria fake player API.
Steps to Reproduce:

use mods that utilize cafeteria fake player API and kyori adventure API as well as indrev
place a rancher
crash, chunk is now crashable on load.

Technical Information:

Minecraft:  1.18.2
Fabric API: 53.4
Industrial Revolution: 1.14.0
Modpack: Another Quality Modpack 2

Logs:
https://pastebin.com/pduGX2Sn

Got the same issue with the same mudpack, rolled back the chunk but placing the Rancher again didn't result in a crash.
https://pastebin.com/TSmirJRn

Tried again, this time the issue came up when the rancher was fully configured and i placed cows within the range. This time I luckily had a recent backup.

#388

#388

Wow, since Jan 2022. Seems like it's not important to fix.

@itsdinkd  That's what I thought as well, makes the rancher completely unusable. shame

Bumping this ‘cause I just experienced this on the latest version.


https://www.constp.it/

Il conservatorio ha corsi di tecnico del suono dove si programma con csound

@Nandos0804 First stage of verification passed, official domain for Conservatorio Antonio Scontrino is dad.constp.it as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@Nandos0804 Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Phone problem

Hi, I use the newest pdf.js. But I find it don't work on my android phone?

When opening an issue, please provide all of the information requested in https://github.com/mozilla/pdf.js/blob/master/.github/ISSUE_TEMPLATE.md since as-is this is unfortunately not actionable/valid.


Add shell override for NixOS bash location

This allows users to login that have the loginShell set in LDAP. Without this, no user can successfully get a login shell on NixOS due to pathing
Description of changes

Things done

Built on platform(s)

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

[x] Fits CONTRIBUTING.md.

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

Please remove the merge commits and change the commit message title to nixos/ipa: Add default and fallback shell the commit message is also confusing so it would be nice if you could reword it.

https://github.com/NixOS/nixpkgs/pull/356269


create and push moby bundles as docker image

Creates a pkg workflow to be able to push a multi-platform scratch image that only contains our bundles so we are able to grab them with undock for example.
I use named contexts feature to add the bundles context in a scratch stage because cross build does not work with buildkit platforms field atm. https://github.com/moby/moby/pull/43529 would fix this in the future.
Tested in https://hub.docker.com/repository/docker/crazymax/moby-bin/tags?page=1&ordering=last_updated

$ undock --rm-dist --all crazymax/moby-bin:latest ./moby-bin
...
$ tree -nh ./moby-bin/
[ 512]  ./moby-bin/
├── [ 512]  linux_amd64
│   ├── [ 37M]  containerd
│   ├── [9.2M]  containerd-shim-runc-v2
│   ├── [ 20M]  ctr
│   ├── [720K]  docker-init
│   ├── [1.9M]  docker-proxy
│   ├── [ 60M]  dockerd
│   ├── [ 13K]  dockerd-rootless-setuptool.sh
│   ├── [5.1K]  dockerd-rootless.sh
│   ├── [ 10M]  rootlesskit
│   ├── [6.7M]  rootlesskit-docker-proxy
│   ├── [ 13M]  runc
│   └── [ 32M]  vpnkit
├── [ 512]  linux_arm64
│   ├── [1.9M]  docker-proxy
│   └── [ 57M]  dockerd
├── [ 512]  linux_armv5
│   ├── [2.5M]  docker-proxy
│   └── [ 57M]  dockerd
├── [ 512]  linux_armv6
│   ├── [2.5M]  docker-proxy
│   └── [ 57M]  dockerd
├── [ 512]  linux_armv7
│   ├── [2.4M]  docker-proxy
│   └── [ 57M]  dockerd
├── [ 512]  linux_ppc64le
│   ├── [2.0M]  docker-proxy
│   └── [ 60M]  dockerd
├── [ 512]  linux_s390x
│   ├── [2.7M]  docker-proxy
│   └── [ 62M]  dockerd
├── [ 512]  windows_amd64
│   ├── [1.9M]  docker-proxy.exe
│   └── [ 55M]  dockerd.exe
└── [ 512]  windows_arm64
    ├── [1.8M]  docker-proxy.exe
    └── [ 53M]  dockerd.exe

Signed-off-by: CrazyMax<EMAIL_ADDRESS>

Login step to the registry not added yet. Will push that soon.

ci failure unrelated, github might have some issues
#40 0.127 + RUNC_BUILDTAGS=seccomp
#40 0.127 + echo 'Install runc version v1.1.2 (build tags: seccomp)'
#40 0.127 + git clone https://github.com/opencontainers/runc.git /tmp/tmp.1ZFJNnZMfI/src/github.com/opencontainers/runc
#40 0.127 Install runc version v1.1.2 (build tags: seccomp)
#40 0.129 Cloning into '/tmp/tmp.1ZFJNnZMfI/src/github.com/opencontainers/runc'...
#40 1.216 error: RPC failed; curl 56 GnuTLS recv error (-54): Error in the pull function.
#40 1.216 error: 5718 bytes of body are still expected
#40 1.219 fetch-pack: unexpected disconnect while reading sideband packet
#40 1.220 fatal: early EOF
#40 1.220 fatal: index-pack failed

One thing I forgot to mention is it will create statically linked binaries but in Docker Desktop we use the Debian package which has dyn linked binaries. This might be ok for testing but I would suggest that we move forward with https://github.com/moby/moby/pull/43529 to be able to cross comp dynamically linked binaries against any arch.
Other thing is docker-init is missing for other architectures but it's solved with https://github.com/moby/moby/pull/43529


Using includeSubdomains: true in a Filter causes crash in Ambassador 1.5.4

Describe the bug
Using includeSubdomains: true in a Filter causes ambassador to crash at startup, or to raise an error when the Filter is added.
To Reproduce
Steps to reproduce the behavior:

Apply a Filter with includeSubdomains: true set for one of its spec.OAuth2.protectedOrigins
Check logs for error or attempt to access a site included as part of the Filter

Expected behavior
The Filter should not error and should properly protect subdomains as expected.
Versions (please complete the following information):

Ambassador: 1.5.4
Kubernetes environment: EKS
Version: 1.14

Additional context
Here is the Filter which causes issues:
apiVersion: getambassador.io/v2
kind: Filter
metadata:
  name: my-test
spec:
  OAuth2:
    authorizationURL: https://cognito-idp.us-east-1.amazonaws.com/{sensitive}
    clientID: {sensitive}
    secret: {sensitive}
    protectedOrigins:
      - origin: https://my-test.{sensitive}
        includeSubdomains: true

Removing includeSubdomains: true, as shown below, allows the Filter to apply correctly and start working.
apiVersion: getambassador.io/v2
kind: Filter
metadata:
  name: my-test
spec:
  OAuth2:
    authorizationURL: https://cognito-idp.us-east-1.amazonaws.com/{sensitive}
    clientID: {sensitive}
    secret: {sensitive}
    protectedOrigins:
      - origin: https://my-test.{sensitive}

@Lemmons Thank you for reporting this.
This is a bug that appears to be introduced in 1.5.3 with the internalOrigin addition to the protectedOrigins field.
The workaround for it is to manually set internalOrigin to the origin configured with includeSubdomains: true set.
apiVersion: getambassador.io/v2
kind: Filter
metadata:
  name: my-test
spec:
  OAuth2:
    authorizationURL: https://cognito-idp.us-east-1.amazonaws.com/{sensitive}
    clientID: {sensitive}
    secret: {sensitive}
    protectedOrigins:
      - origin: https://my-test.{sensitive}
        internalOrigin: https://my-test.{sensitive}
        includeSubdomains: true

We apologize for this issue and are working to resolve it. Thanks again for reporting it!

While the workaround lets the filter now not fail when being applied, it still doesn't actually enable the expected behavior from includeSubdomains: true.
I expect with the workaround for a request to https://subdomain.my-test.{sensitive} to go through the filter, but instead it raises an error filter misconfiguration: https://subdomain.my-test.{sensitive} is not a valid origin for my-test.default

Same problem here, the workaround makes ambassador stop crashing at startup, but includeSubdomains doesn't work. From the stack trace, it seems like a simple bug in the filter validation? @khussey, any other workaround for us? Or an ETA on a fix? This is blocking the deployment of our authentication system. Thanks.

The crashing issue has been fixed in the 1.6.0 release that is now available.

@khussey I've tested this morning and it looks like the crashing issue is gone. However I can't get the includeSubdomains flag to work.
My filter contains:
    protectedOrigins:
      - origin: https://xxxxxx.xxxx.xx
        includeSubdomains: true

but when I hit https://test.xxxxxx.xxxx.xx, I get this error message:
"message": "filter misconfiguration: https://test.xxxxxx.xxxx.xx is not a valid origin for xxxxxx.xxxxxx"

My goal is to able to onboard new services internally, with new subdomains, without changing the oauth2 filter configuration (I still have to whitelist their redirect URI in the IdP, but that's another topic).
Maybe I don't get what's this includeSubdomains flag is doing?

Thanks for checking, @yanickbelanger! We're still working to make the flag function as expected and should be able to ship a more complex fix in an upcoming release.

@khussey Any update on this? I can help you with the testing of that feature if needed.

Thanks for the kind offer, @yanickbelanger. We're currently testing a fix and anticipate shipping it as part of the upcoming 1.7.0 release.

Oops, closed prematurely. We have a fix and will be shipping it with 1.7.0 in the coming days.

This fix is in 1.7.0, which is now available.

Tested in our environment, it seems to work great. Thanks! As a bonus, the redirect URIs are now all pointing to the same domain, so no more whitelisting of redirect URIs required for all our apps in our IdP.


Deleting the "preview" entry

Only deleted 2 lines "coming soon" and "important"

Hi @rojasja, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Jose Rojas). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

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

Microsoft authors of articles need to make updates through the private repository so the updates can be staged and validated by the current validation rules. After you review staging and fix all validation issues, you can add the sign-off comment to let the PR reviewers know the updates are ready to be merged.
It�s easy to access the private repo version of your articles in GitHub. Just add �pr to the URL, as follows:
Public repo URL: https://github.com/Azure/azure-content/blob/master/articles/azure-portal-overview.md
Private repo URL: https://github.com/Azure/azure-content-pr/blob/master/articles/azure-portal-overview.md
We've closed this pull request. Please resubmit the updates through the private repo. If you need perms to the private repo, see the contributor guide instructions.


happo screenshot is not aligned with manual testing

happo screenshots are not aligned with manual testing on the project contact form.  for instance, on e2e testing when we click the add button to add secondary contacts 3 times, on happo screenshots we see 4 secondary contacts. this issue is not consistent and does not get triggered during e2e testing (Only pops up in happo screenshots diffs)

Closing since this never happened again.


Setting the synth sample rate to 0 could cause a divide by zero error

It probably doesn't make much sense for a user to set the sample rate to zero, but if they do, these could throw an Arm exception fault:
https://github.com/lancaster-university/codal-microbit-v2/blob/90756513c3ff795a80eb5ef54aa6abe67d3d0a6e/source/SoundEmojiSynthesizer.cpp#L211
https://github.com/lancaster-university/codal-microbit-v2/blob/90756513c3ff795a80eb5ef54aa6abe67d3d0a6e/source/SoundEmojiSynthesizer.cpp#L233
We could guard against it in setSampleRate().

Fixed in https://github.com/lancaster-university/codal-microbit-v2/pull/215.


readlink -f does not exist on macOS (generate-dev-env.sh)

On any macOS system:
./generate-dev-env.sh jewel ubuntu 16.04

**********************************************************
JUMPING INTO THE BASE DIRECTORY OF THE SCRIPT
**********************************************************
readlink: illegal option -- f
usage: readlink [-n] [file ...]

Install brew and then install gnu-tools to get a new version of readlink.
Thanks.


Animated Blocks Causing Decreased Mining Speed Issue in Geckolib3

Hello,
I am experiencing an issue with the mining speed of my animated blocks in my mod. I am using the GeckoLib library to create the animations, and I have noticed that when I mine the blocks, the mining speed is significantly slower than it should be.
I have narrowed down the issue to the use of the GeckoLib library, as when I remove the animations and use regular blocks, the mining speed is normal.
I would appreciate it if someone from the GeckoLib development team could provide some insight into why this might be happening and if there is a solution.
Thank you.

Closing due to usage of the Mcreator plugin
We cannot assist with mcreator usage


Client Allocation Request for: kako

Client Allocation Questions
Core Information

Name: kako
Website / Social Media: hostloc.com
Region: Europe
DataCap Requested: 20TiB
Addresses to be Notarized: f1pyzn4a2mwkxpk7kdqr235dpeyoaqwhl4m7d6ltq
Notary Requested: dannyob

@2lifetop Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

Hi @2lifetop -- could you apply to a notary serving your region (Asia minus GCR)?
Thanks!


When writing the script, the ewaldErrorTolerance value is in brackets

Currently, the output is like this:
ewaldErrorTolerance = {0.0005}

The output has to be like this:
ewaldErrorTolerance = 0.0005

@brittyscience Could you take a look on this and fix it if possible?