[bug]: chart not rendering

Describe the bug
Hey, I am using charts, and everything was working fine, but now suddenly the pie chart is not rendering. This happens when I use two pie charts side by side.
but it rendered the data.
see the below image

Affected component/components
chart
How to reproduce
no
Codesandbox/StackBlitz link
No response
Logs
No response
System Info
node-20
next-14

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

can you please send the code?

Check to make sure the ChartContainer component has a minimum height class or style attribute e.g: min-h-[300px]. The issue that I had was that I was using the tailwindcss aspect plugin. Removing this allowed my charts to render properly.

Same problem for me. No examples from shadcn-ui's docs works with next-js 15 and react 19.
But if I use a recharts' official example, it works.

You might be experiencing this issue because Recharts is not yet compatible with React 19. If you have upgraded to React 19, you may need to wait for Recharts to update or revert to a compatible version to resolve the issue.
https://github.com/shadcn-ui/ui/issues/4231

You might be experiencing this issue because Recharts is not yet compatible with React 19. If you have upgraded to React 19, you may need to wait for Recharts to update or revert to a compatible version to resolve the issue.
#4231

Rechart 2.13.0-alpha.4 with React 19.0.0-beta works fine with NextJs 15. Only shadcn's chart examples  doesn't work.

react-is is breaking in recharts 2.13.0-alpha.4 & react 19 / next 15.
You need to manually override this in your package.json
"dependencies": {
    "react-is": "19.0.0-rc-6f23540c7d-20240528"
},
"overrides": {
    "recharts": {
        "react-is": "$react-is"
    }
}

See below thread over at recharts.
https://github.com/recharts/recharts/issues/4558#issuecomment-2135604065
Updating the above has shadcn charts working on my next 15 / react 19 project with recharts alpha.

The charts are not visible for me as well.
Only when explicitly setting width and height props for the recharts Chart Component (e.g. BarChart or LineChart), the chart is visible. However, responsiveness is lost due to this.
Seems like the ChartContainer wrapper around ResponsiveContainer  does not seem to work?
Any suggestions?

Check to make sure the ChartContainer component has a minimum height class or style attribute e.g: min-h-[300px]. The issue that I had was that I was using the tailwindcss aspect plugin. Removing this allowed my charts to render properly.

If you are using the @tailwindcss/aspect-ratio plugin, you can follow the instructions on the "Compatibility with default aspect-ratio utilities" section of the readme to support the default aspect-ratio utilities these charts rely on.

The charts are not visible for me as well.
Only when explicitly setting width and height props for the recharts Chart Component (e.g. BarChart or LineChart), the chart is visible. However, responsiveness is lost due to this. Seems like the ChartContainer wrapper around ResponsiveContainer  does not work?
Any suggestions?

See my above suggestion if you are using React 19 or Next 15
https://github.com/shadcn-ui/ui/issues/4231#issuecomment-2226782779
By forcing the rc version of react-is (which supports react 19 rc / 15 rc) the shadcn examples work out of the box and the ChartContainer is responsive for me using the min-h that shadcn tells you to.

Running into the same issue here with React 19 + Next 15. Tried all of the suggestions posted so far and still cannot get a responsive chart to render.
Examples taken directly from the recharts docs render normally when explicitly setting width and height, however the ResponsiveContainer examples do not render.
Was able to reproduce on a new create-next-app project while trying all of the fixes above, tested on Firefox 128 and Chromium 125.0.6422.141.

Same for me here with Next JS 14, React 18. I will investigate more during the day

I got the same issue with Nextjs 15-rc and React 19-rc! (just a try)
Working fine with Nextjs 14 and React 18

The main issue is that charts don't render correctly with dynamic data.
"First bug I found on GitHub."🫡

Goodmorging at least for me,
I encountered the same issue where the Shadcn chart would not render, and I managed to solve it after through investigation. The primary problem seemed to be that wrapping a div, card, or any other element outside the ChartContainer prevents the chart from rendering. I tried the suggestion by AlexandreLrz to remove the wrapper div, which worked temporarily but wasn't an ideal solution for my needs.
To get to the bottom of this, I created a new Next.js 14 app and meticulously set it up by installing charts, shadcn, Tailwind CSS, and other necessary dependencies. Upon rendering a chart, it worked perfectly fine!
I didn't stop there. I conducted a comprehensive comparison of the package.json, tailwind.config.js, and other configuration files between my new working setup and the problematic one. I examined dependencies, configurations, and potential conflicts thoroughly.
After extensive debugging, I discovered that removing require("@tailwindcss/aspect-ratio") from the plugins section in tailwind.config.js resolved the rendering issue. Once this line was removed, the charts rendered flawlessly without any further problems. To double-check, I added the aspect-ratio plugin to the new app, which caused the chart to stop rendering. This confirmed that the plugin was the culprit, interfering with the ChartContainer in some way.
I hope i save some debug time for you guys to day!

Removing the wrapper div worked for me (React 18, Next.js 14). I guess the chart needs to be a separate component.

the issue for me was that the shadcn example used max-h-[250px] in the ChartContainer component, while the documentation states to use min-h-[your-height]. So, after replacing max with min everything worked correctly.

for people using yarn this is what worked for me:
  "resolutions": {
    "react-is": "^19.0.0-rc-2d2cc042-20240809"
  },

My chart not render with dynamic data, I am using React 18 and this is my code:
export function PieChartCustom({ chartData = [], datakey, namekey }) {
  return (
    <ChartContainer
      config={chartConfig}
      className="min-h-[250px]"
    >
      <PieChart>
        <ChartTooltip
          cursor={false}
          content={<ChartTooltipContent hideLabel />}
        />
        <Pie data={chartData} dataKey={datakey} nameKey={namekey} />
      </PieChart>
    </ChartContainer>
  )
}

Same problem here with dynamic data
"use client";

import { Bar, BarChart, CartesianGrid } from "recharts";

import { ChartConfig, ChartContainer } from "@/components/ui/chart";

export default function DashboardChart({
  data,
  config,
}: {
  data: Record<string, number>[];
  config: ChartConfig;
}) {
  return (
    <ChartContainer config={config} className="min-h-[200px] w-full">
      <BarChart accessibilityLayer data={data}>
        <CartesianGrid vertical={false} />
        {Object.keys(config).map((keyword) => (
          <Bar
            key={keyword}
            dataKey={keyword}
            fill={`var(--color-${keyword})`}
            radius={4}
          />
        ))}
      </BarChart>
    </ChartContainer>
  );
}

Next Js 14.2.6
Tailwind css 3.4.1

I'm using a LineChart and the line is not rendering, Nextjs 14 and React 18

Goodmorging at least for me,
I encountered the same issue where the Shadcn chart would not render, and I managed to solve it after through investigation. The primary problem seemed to be that wrapping a div, card, or any other element outside the ChartContainer prevents the chart from rendering. I tried the suggestion by AlexandreLrz to remove the wrapper div, which worked temporarily but wasn't an ideal solution for my needs.
To get to the bottom of this, I created a new Next.js 14 app and meticulously set it up by installing charts, shadcn, Tailwind CSS, and other necessary dependencies. Upon rendering a chart, it worked perfectly fine!
I didn't stop there. I conducted a comprehensive comparison of the package.json, tailwind.config.js, and other configuration files between my new working setup and the problematic one. I examined dependencies, configurations, and potential conflicts thoroughly.
After extensive debugging, I discovered that removing require("@tailwindcss/aspect-ratio") from the plugins section in tailwind.config.js resolved the rendering issue. Once this line was removed, the charts rendered flawlessly without any further problems. To double-check, I added the aspect-ratio plugin to the new app, which caused the chart to stop rendering. This confirmed that the plugin was the culprit, interfering with the ChartContainer in some way.
I hope i save some debug time for you guys to day!

This is exactly what I did and Charts started working again, remove that plugin and uninstall that!

My chart not render with dynamic data, I am using React 18 and this is my code:
export function PieChartCustom({ chartData = [], datakey, namekey }) {
  return (
    <ChartContainer
      config={chartConfig}
      className="min-h-[250px]"
    >
      <PieChart>
        <ChartTooltip
          cursor={false}
          content={<ChartTooltipContent hideLabel />}
        />
        <Pie data={chartData} dataKey={datakey} nameKey={namekey} />
      </PieChart>
    </ChartContainer>
  )
}

I solved my problem, it turns out that in my data structure, the nameKey value was a string and not a number

I manage to fix it by forcing value to be a Number, not a string.
Ex:
import { convertCategoriesToChartConfigAndData } from '@/app/lib/chart-utils';
import { CategoryPerMonth } from '@/app/lib/definitions';
import { Cell, Pie, PieChart, ResponsiveContainer } from 'recharts';

export function ChartTestComponent() {
  const dataTest = [
    {
      name: 'rent',
      value: '150.00',
      fill: '#f9a653',
    },
    {
      name: 'entertainment',
      value: '189.20',
      fill: '#4BC0C0',
    },
    {
      name: 'random',
      value: '5.55',
      fill: '#00ff5a',
    },
  ];

  console.log(chartData);
  return (
    <ResponsiveContainer>
      <PieChart width={800} height={400}>
        <Pie
          data={dataTest}
          cx={120}
          cy={200}
          innerRadius={60}
          outerRadius={80}
          paddingAngle={5}
          dataKey='value'
        >
          {dataTest.map((category, index) => (
            <Cell key={`cell-${index}`} fill={category.fill} />
          ))}
        </Pie>
      </PieChart>
    </ResponsiveContainer>
  );
}

Changing dataTest to
  const dataTest = [
    {
      name: 'rent',
      value: 150.00, //here
      fill: '#f9a653',
    },
    {
      name: 'entertainment',
      value: 189.20, //here
      fill: '#4BC0C0',
    },
    {
      name: 'random',
      value: 5.55, //and here
      fill: '#00ff5a',
    },
  ];

I solved it using this CSS code in my global stylesheet file:
.recharts-responsive-container {
    height: initial !important;
}

Component code:
export function SimpleBarChart() {
    return (
        <Card>
            <CardHeader>
                <CardTitle>Bar Chart</CardTitle>
                <CardDescription>January - June 2024</CardDescription>
            </CardHeader>
            <CardContent>
                <ChartContainer className="min-h-[300px]" config={chartConfig}>
                    <BarChart accessibilityLayer data={chartData}>
                        <CartesianGrid vertical={false} />
                        <XAxis
                            dataKey="month"
                            tickLine={false}
                            tickMargin={10}
                            axisLine={false}
                            tickFormatter={(value) => value.slice(0, 3)}
                        />
                        <ChartTooltip
                            cursor={false}
                            content={<ChartTooltipContent hideLabel />}
                        />
                        <Bar
                            dataKey="desktop"
                            fill="var(--color-desktop)"
                            radius={8}
                        />
                    </BarChart>
                </ChartContainer>
            </CardContent>
            <CardFooter className="flex-col items-start gap-2 text-sm">

                    Trending up by 5.2% this month{' '}
                    <TrendingUp className="h-4 w-4" />

                    Showing total visitors for the last 6 months

            </CardFooter>
        </Card>
    )
}

for people using yarn this is what worked for me:
  "resolutions": {
    "react-is": "^19.0.0-rc-2d2cc042-20240809"
  },

This is the thing which is the main problem with React 19 RC and NextJS 15 RC. Otherwise you wont see any SVG in your code. So definitely not a HTML/CSS issue.

I manage to fix it by forcing value to be a Number instead of String and adding width and height to PieChart component. It's working even with dynamic data!
For example, in this component
import { convertCategoriesToChartConfigAndData } from '@/app/lib/chart-utils';
import { Cell, Pie, PieChart, ResponsiveContainer } from 'recharts';

export function ChartTestComponent() {
  const dataTest = [
    {
      name: 'rent',
      value: '150.00',
      fill: '#f9a653',
    },
    {
      name: 'entertainment',
      value: '189.20',
      fill: '#4BC0C0',
    },
    {
      name: 'random',
      value: '5.55',
      fill: '#00ff5a',
    },
  ];

  return (
    <ResponsiveContainer>
      <PieChart width={800} height={400}>
        <Pie
          data={dataTest}
          cx={120}
          cy={200}
          innerRadius={60}
          outerRadius={80}
          paddingAngle={5}
          dataKey='value'
        >
          {dataTest.map((category, index) => (
            <Cell key={`cell-${index}`} fill={category.fill} />
          ))}
        </Pie>
      </PieChart>
    </ResponsiveContainer>
  );
}

Change dataTest to
  const dataTest = [
    {
      name: 'rent',
      value: 150.00, //here
      fill: '#f9a653',
    },
    {
      name: 'entertainment',
      value: 189.20, //here
      fill: '#4BC0C0',
    },
    {
      name: 'random',
      value: 5.55, //and here
      fill: '#00ff5a',
    },
  ];

Thanks, this solved my problem

I finally solved it, nothing I searched for worked, but I found a way to solve it by trying. First I'll explain my problem:
I was trying to use literally any chart from the ones in the documentation, but NONE of them showed me the graphic part of the chart, the text, but nothing about the chart. The error was that all the charts in the documentation are without the width and height defined.
It was quite a headache to guess that the BarChart component requires you to pass its dimensions as a parameter (without being required/mandatory by the component itself!!!)
<BarChart width={500} height={250}>

@lucarosato1, width and heigh shouldn't be needed for the shadcn components.
The BarChart example from their docs renders just fine as is.

@lucarosato1, width and heigh shouldn't be needed for the shadcn components. The BarChart example from their docs renders just fine as is.

Hmm that's weird because I literally copied and pasted it into a new and clean Shadcn and Next project and nothing of the graphic is visible until I manually enter the dimensions (tested in Firefox, Safari and Brave)

Hmm that's weird because I literally copied and pasted it into a new and clean Shadcn and Next project and nothing of the graphic is visible until I manually enter the dimensions (tested in Firefox, Safari and Brave)

A new and clean Next project will be on 15.0.1 with React 19-rc.
That's why you still have to override the react-is dependency.

e

god that is absurd I wasted so much time trying to figure it out only for it to be that :( that sucks, also is there a way to not have to define the width so it takes up full like w-full tailwind?

for pnpm users:
{
  "dependencies": {
    "react-is": "19.0.0-rc-6f23540c7d-20240528"
  },
  "pnpm": {
    "overrides": {
      "recharts>react-is": "$react-is"
    }
  }
}

so I am trying to make it automatically scale like it would with a responsive container but it doesnt appear if I dont define the width/height I dont understant because in other projects its worked just fine
    <ChartContainer config={chartConfig} className="min-h-[200px] max-h-[400px] w-full">
      <BarChart accessibilityLayer data={chartData} > {/*add width and height to make it appear*/}
        <CartesianGrid vertical={false} />
        <XAxis
          dataKey="day"
          tickLine={false}
          tickMargin={10}
          axisLine={false}
          tickFormatter={(value) => value.slice(0, 3)}
        />
        <ChartTooltip
          cursor={true}
          content={<ChartTooltipContent hideLabel />}
        />
        <Bar dataKey="Submission" fill="var(--color-Submission)" radius={8} />
      </BarChart>
    </ChartContainer>

so I am trying to make it automatically scale
@FifthWit

I'm sharing here a hook I made especially for that, I'm not sure it's the most pro thing out there because I'm just a backend dev who's doing front-end work
Basically what it does is grab the size of your screen, do a resize and return the width as a numeric (which is the only thing that chart components support as dimensions), so just use the useResize hook and grab the width.
Oh and that "-150" is something I needed for my particular view, adjust it as needed.
Custom useResize hook:
import { useState, useEffect } from 'react';

const useResize = () => {
    const [windowSize, setWindowSize] = useState({
        width: window.innerWidth - 150,
        height: window.innerHeight,
    });

    useEffect(() => {
        const handleResize = () => {
            setWindowSize({
                width: window.innerWidth - 150,
                height: window.innerHeight,
            });
        };

        window.addEventListener('resize', handleResize);

        return () => {
            window.removeEventListener('resize', handleResize);
        };
    }, []);

    return windowSize;
};

export default useResize;

Example using it for a component with a chart:
export function YourEpicComponent() {
    const dimensions = useResize();

    return (
            <ChartContainer config={chartConfig}>
                <AreaChart
                        accessibilityLayer
                        data={getData()}
                        width={dimensions.width} // Use the width
                        height={150}
                    >
                    ...

Can someone help me solve this? using nextjs and react 18.2, whenever i tried copy and paste even shadcn charts example getting this error

Goodmorging at least for me,
I encountered the same issue where the Shadcn chart would not render, and I managed to solve it after through investigation. The primary problem seemed to be that wrapping a div, card, or any other element outside the ChartContainer prevents the chart from rendering. I tried the suggestion by AlexandreLrz to remove the wrapper div, which worked temporarily but wasn't an ideal solution for my needs.
To get to the bottom of this, I created a new Next.js 14 app and meticulously set it up by installing charts, shadcn, Tailwind CSS, and other necessary dependencies. Upon rendering a chart, it worked perfectly fine!
I didn't stop there. I conducted a comprehensive comparison of the package.json, tailwind.config.js, and other configuration files between my new working setup and the problematic one. I examined dependencies, configurations, and potential conflicts thoroughly.
After extensive debugging, I discovered that removing require("@tailwindcss/aspect-ratio") from the plugins section in tailwind.config.js resolved the rendering issue. Once this line was removed, the charts rendered flawlessly without any further problems. To double-check, I added the aspect-ratio plugin to the new app, which caused the chart to stop rendering. This confirmed that the plugin was the culprit, interfering with the ChartContainer in some way.
I hope i save some debug time for you guys to day!

I can confirm that Tailwind plugin aspect-ratio might cause this problem. My problem was not simply missing some min-height classnames. The rendered HTML in inspection does not show any element inside the chart container. If that is your case, removing the plugin from Tailwind config works.

Solution for Chart Rendering Issue with Next.js 15 and React 19
I was facing difficulties rendering charts using the Shadcn examples with Next.js 15 and React 19.
I followed the instructions found in the Shadcn documentation. Below are the steps that worked for me:
Steps to resolve:

Update the package.json:
I adjusted the versions of React and Next.js to ensure compatibility:
{
  "dependencies": {
    "react": "19.0.0-rc-69d4b800-20241021",
    "react-dom": "19.0.0-rc-69d4b800-20241021",
    "next": "15.0.1"
  }
}

Force the correct version of react-is: To ensure Recharts works correctly with React 19, I added the following configuration:

{
  "overrides": {
    "recharts": {
      "react-is": "$react-is"
    }
  }
}

My package.json
{
  ...
  "scripts": {
    ...
  },
  "dependencies": {
    ...
    "next": "15.0.1",
    "react": "19.0.0-rc-69d4b800-20241021",
    "react-dom": "19.0.0-rc-69d4b800-20241021",
    ...
  },
  "devDependencies": {
   ...
  },
  "overrides": {
    "recharts": {
      "react-is": "^19.0.0-rc-69d4b800-20241021"
    }
  }
}

Reinstall dependencies: After adjusting the package.json, I reinstalled the dependencies with:

npm install

Conclusion:
These adjustments resolved the chart rendering issues with Recharts on React 19 and Next.js 15. I hope this helps anyone facing the same issue!

@matheusvictoor
I have tried that but it does not fix the situation below.
Has this problem already been resolved?

so I am trying to make it automatically scale like it would with a responsive container but it doesnt appear if I dont define
the width/height I dont understant because in other projects its worked just fine
    <ChartContainer config={chartConfig} className="min-h-[200px] max-h-[400px] w-full">
      <BarChart accessibilityLayer data={chartData} > {/*add width and height to make it appear*/}
        <CartesianGrid vertical={false} />
        <XAxis
          dataKey="day"
          tickLine={false}
          tickMargin={10}
          axisLine={false}
          tickFormatter={(value) => value.slice(0, 3)}
        />
        <ChartTooltip
          cursor={true}
          content={<ChartTooltipContent hideLabel />}
        />
        <Bar dataKey="Submission" fill="var(--color-Submission)" radius={8} />
      </BarChart>
    </ChartContainer>

@matheusvictoor
I have tried that but it does not fix the situation below. Has this problem already been resolved?

so I am trying to make it automatically scale like it would with a responsive container but it doesnt appear if I dont define
the width/height I dont understant because in other projects its worked just fine
    <ChartContainer config={chartConfig} className="min-h-[200px] max-h-[400px] w-full">
      <BarChart accessibilityLayer data={chartData} > {/*add width and height to make it appear*/}
        <CartesianGrid vertical={false} />
        <XAxis
          dataKey="day"
          tickLine={false}
          tickMargin={10}
          axisLine={false}
          tickFormatter={(value) => value.slice(0, 3)}
        />
        <ChartTooltip
          cursor={true}
          content={<ChartTooltipContent hideLabel />}
        />
        <Bar dataKey="Submission" fill="var(--color-Submission)" radius={8} />
      </BarChart>
    </ChartContainer>

Fixed by changing the version of recharts to “recharts”:“^2.13.3”.

it is solve here https://ui.shadcn.com/docs/react-19#recharts


Change whole system to support year and month.

Hi there,
for me I need bit more functionality. Therefor I added two more collection views. One for years and one for month. For Performance reasons. I couldn't use include dates. Only range with min and max. But to have same effect, you can pass exclude dates. Please can you also check if code is ok and functionality is correct ?

Thanks for your contribution - however I think your implementation basically changes everything in the source code. I'd suggest you create a new repo for this and I'll happily add a link on my README to your repo for anyone in need - what do you think?


Cannot read 'hex' of undefined

Hi, I'm getting this error when importing * as Progress in my app
import * as Progress from 'react-native-progress';
.
.
.
 <Progress.Bar progress={0.3} width={200} />

Error: Requiring module<EMAIL_ADDRESS>which threw an exception: TypeError: Cannot read property 'hex' of undefined.

TypeError: Cannot read property 'hex' of undefined

React Native: 0.63
Progress: 4.1.2
Art: 1.2.0

same

Facing the same issue.

i' m add  yarn add @react-native-community/art and use the other components like Progress.Circle
it's work for me

https://github.com/oblador/react-native-progress/issues/214#issuecomment-726568864
@Tankbt 's solution works nicely!!

Manually linking ReactNative ART by running react-native link @react-native-community/art solved the issue for me.

i' m add yarn add @react-native-community/art and use the other components like Progress.Circle
it's work for me

This solution not working for me, any idea?
My enviroments are
"react-native": "^0.63.2",
"react-native-progress": "^4.1.2",
"@react-native-community/art": "^1.2.0",

i' m add yarn add @react-native-community/art and use the other components like Progress.Circle
it's work for me

This solution not working for me, any idea?
I get error, when I running my test file
TypeError: Cannot read property 'hex' of undefined

I am using Progress.Bar like this,
<Progress.Bar borderRadius={0} progress={timer === 3 ? 0.2 : timer === 2 ? 0.5 : 0.9} width={responsiveWidth(100)} color={color.thema} />

My environments are
"react-native": "^0.63.2",
"react-native-progress": "^4.1.2",
"@react-native-community/art": "^1.2.0",

same error

Don't forget to install pods for ios after installing react-native-art. I didn't see that setup step in the docs but it is required.

Don't forget to install pods for ios after installing react-native-art. I didn't see that setup step in the docs but it is required.

anyone managed to solve this?

anyone managed to solve this?

I got this message when I forgot to do a pod install after adding ReactNativeART (yarn add @react-native-community/art)
$ cd ~/Workspace/AppName
$ npx pod-install ios
npx: installed 1 in 3.023s
Scanning for pods...
1.9.3
> pod install
...
Analyzing dependencies
Downloading dependencies
Installing ReactNativeART (1.2.0)
Generating Pods project
Integrating client project
Pod installation complete! There are # dependencies from the Podfile and # total pods installed.

I got this message when I forgot to do a pod install after adding ReactNativeART (yarn add @react-native-community/art)
$ cd ~/Workspace/AppName
$ npx pod-install ios
npx: installed 1 in 3.023s
Scanning for pods...
1.9.3
> pod install
...
Analyzing dependencies
Downloading dependencies
Installing ReactNativeART (1.2.0)
Generating Pods project
Integrating client project
Pod installation complete! There are # dependencies from the Podfile and # total pods installed.

any solution to this?
I get the same error when running Jest.
Tried the all the above but nothing works


is_connected()?

I'm looking at how best to determine that my transport layer is still active without having to send a request to the server and get an ErrorKind::NotConnected.  I've noticed that the transport object is heavily buried int he client. Any suggestions about best way to do a quick boolean check before trying to read/write and having to create a new connection?

bump


Warnings/Notices on composer install

I get the following notices when installing via composer create-project microweber/microweber my_site dev-master --prefer-dist --no-dev on Ubuntu 18
Package mtdowling/cron-expression is abandoned, you should avoid using it. Use dragonmantank/cron-expression instead.
Package guzzle/guzzle is abandoned, you should avoid using it. Use guzzlehttp/guzzle instead.
Package jeremeamia/superclosure is abandoned, you should avoid using it. Use opis/closure instead.
Package oyejorge/less.php is abandoned, you should avoid using it. No replacement was suggested.
Generating autoload files
Carbon 1 is deprecated, see how to migrate to Carbon 2.
https://carbon.nesbot.com/docs/#api-carbon-2
    You can run './vendor/bin/upgrade-carbon' to get help in updating carbon and other frameworks and libraries that depend on it.
> php artisan key:generate
**************************************
*     Application In Production!     *
**************************************

Command Cancelled!

any update?


redirect back to slack after installing also with welcome dm

Description
So, after I install my application I want the browser to redirect to slack and with a welcome message to the person to installed the app. I referred to a previous issue almost similar issue #682
there @mwbrooks explained everythinng, though I did exact same thing but I am getting an error stating that res.send in not a function.
kindly, help me fix this, or am I missing something obvious here?
What type of issue is this? (place an x in one of the [ ])

[ ] bug
[ ] enhancement (feature request)
[x] question
[ ] documentation related
[ ] example code related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x ] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x ] I've read and agree to the Code of Conduct.
[x ] I've searched for any related issues and avoided creating a duplicate issue.

Attachments:

as @mwbrooks explained :

my code :

i just kept everything as it is to test
the error on console :

Hey @arian0zen,
Bolt has changed a little since issue #682, so that may be throwing you off. Sorry about that! This is because<EMAIL_ADDRESS>changed the default receiver from Express to HTTPReceiver. You may need to learn how to use the custom Express Receiver to access the res.send function. Here is also an example of using OAuth with the Express Receiver.
An alternative approach that may work is to add a custom route using the default HTTPReceiver and then customize the OAuth defaults by setting the redirectUriPath to your new custom route.
Let me know how that goes!

Heyyy! @mwbrooks
Thanks for your reply and provided references, I'll look into that..
For now, what I figured out that, the res.end() function works as a way to respond with any text to the user. So, after the direct message i just added res.end("message: the bot is installed") and it's working..

And I'll surely learn and read about what you referred, thank you so much!
You can close the issue now.


queryString.parse doesn't ignore ? in location.search.

On v5.0.0, passing in:
?foo=bar
Yields:
{?foo: "bar"}

Sorry, just saw that it had been fixed.

Nevermind, #109 addresses "extract" not working? According to the docs, parse needs to ignore ? as well.
.parse(string, [options])
Parse a query string into an object. Leading ? or # are ignored, so you can pass location.search or location.hash directly.

How is:
https://github.com/sindresorhus/query-string/blob/f2833411bbe975d38b261ed46c96edde4bd0e6e7/test/parse.js#L4
Not breaking?

Nevermind, issue with npm packages on my side. ;)

@josephong how did you solve this? #109 was merged but I face the same issue...Thanks!

I'm facing the same issue with react useLocation().search ?foo=bar it return {"?foo": "bar"}

@MoiseScalzo ditto here


Migrate OSC/bc_osc_vmd to use Dynamic JavaScript.

Migrate to use Dynamic JavaScript.
Child ticket of https://github.com/OSC/ondemand/issues/1657

Nothing to do here as this app doesn't have a form.js.


Access to view settings of running memcached container

I'm passing options into this image, via my Docker-Compose, and I want to confirm that they're being applied (for example, increasing the memory limit).
Is there a way to confirm the settings of the memcached Docker image, once it is up and running?
I've done a lot of searching and everything that I've seen so far involves commands not present on the image (telnet, memcstat) or viewing files that aren't present (/etc/memcached.conf).
Sorry if I'm missing something really obvious.

Your link to inspect running memcached works just fine if you hit the IP of the container from your host (or another container that has nc) or if via <IP_ADDRESS> if you forward the port with -p 11211:11211 on the docker run.  I can't remember if memcached accounts for cgroup limits or not (like --memory on docker run).
$ docker run -d --name memc memcached
$ ipaddr="$(docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' memc)"
$ echo "$ipaddr"
<IP_ADDRESS>
$ echo "stats settings" | nc "$ipaddr" 11211
STAT maxbytes 67108864
STAT maxconns 1024
STAT tcpport 11211
STAT udpport 0
STAT inter NULL
STAT verbosity 0
STAT oldest 0
STAT evictions on
STAT domain_socket NULL
STAT umask 700
STAT growth_factor 1.25
STAT chunk_size 48
STAT num_threads 4
STAT num_threads_per_udp 4
STAT stat_key_prefix :
STAT detail_enabled no
STAT reqs_per_event 20
STAT cas_enabled yes
STAT tcp_backlog 1024
STAT binding_protocol auto-negotiate
STAT auth_enabled_sasl no
STAT item_size_max 1048576
STAT maxconns_fast yes
STAT hashpower_init 0
STAT slab_reassign yes
STAT slab_automove 1
STAT slab_automove_ratio 0.80
STAT slab_automove_window 30
STAT slab_chunk_max 524288
STAT lru_crawler yes
STAT lru_crawler_sleep 100
STAT lru_crawler_tocrawl 0
STAT tail_repair_time 0
STAT flush_enabled yes
STAT dump_enabled yes
STAT hash_algorithm murmur3
STAT lru_maintainer_thread yes
STAT lru_segmented yes
STAT hot_lru_pct 20
STAT warm_lru_pct 40
STAT hot_max_factor 0.20
STAT warm_max_factor 2.00
STAT temp_lru no
STAT temporary_ttl 61
STAT idle_timeout 0
STAT watcher_logbuf_size 262144
STAT worker_logbuf_size 65536
STAT track_sizes no
STAT inline_ascii_response no
STAT ext_item_size 512
STAT ext_item_age<PHONE_NUMBER>
STAT ext_low_ttl 0
STAT ext_recache_rate 2000
STAT ext_wbuf_size 4194304
STAT ext_compact_under 0
STAT ext_drop_under 0
STAT ext_max_frag 0.80
STAT slab_automove_freeratio 0.010
STAT ext_drop_unread no
END

Perfect. Thanks; I was able to get that working to confirm the settings. Appreciate the insight!


Transformation with different Filetypes than jpg does not work

I use the internal assets plugin with a image transformation. The transformation of jpg files works as exepted, but the transformation of a tif file does not work. Is there a possiblity to get that work? Imagick is installed and creating tif transformations without internal asset plugin works. I reviewed the code and think i have found the problem in the following lines:
            // Check if the file path ends with the handle of the specified transform
            if (substr($filePath, -strlen($transform->handle)) === $transform->handle) {
                $requestedTransform = '_' . $transform->handle;

the check of the file path ends does not match. Unfortunately i wasn't able to fix this. Can you help me with this or can you get me a hint what to do? Thanks.

Hi @tombauer,
Thank you for reporting this issue. I will try to find and fix the problem..

It should be easier to properly support file transformations in Craft 4. Feature is on the roadmap


0 rate value in lines

In version 5.0+ of Matpower a rating value of 0 indicates no thermal limit.  STAC currently generates a warning for this case.
Hence, when a line rating is 0 in the input, it should not generate a warning and it should display as a value of "none" in the tool tip.
See case14_rate_0.m for an example.
Reported by Ray Zimmerman.

Made the following changes:

Commented the code responsible for adding the warning message for the validation on rating.
Added a custom attribute to display the tool-tip for the rating value.

This is what I am currently seeing with the case14_rate_0.m
In this case the "none" should appear in all three, Rate A, Rate B, and Rate C.
The message also appears to be incorrect, it says thermal limit "and angle difference bound" violated.  The angle difference bound is also not violated in this case.
Note that a value of "0" is really a special case, which turns off the rate check.  If the value is negative is should produce an error, if the value is greater than 0 it should check the rate value.

Updated the code to not perform the following validations when the value of rateA is zero:

Thermal rating is greater than the implied upper bound.
Thermal limit and angle difference bound violated.

This change appears to be working on the case14_rate_0.m
On the other cases, which have thermal limits, only Rate A appears to be showing now, and not B and C?
Also regarding point 2.  Why is the text Thermal limit and angle difference bound?  Thermal limits and phase angle differences are two separate constraints, and should be tested separately as well.

Made a minor bug fix for the Rate B and Rate C values.
For point 2 -
The validation on Thermal limit and angle difference bound is being done by comparing the value of the power 's-s-t' or 's-t-s' with Rate A and an error is logged if either of the two is greater than Rate A.

Ok, maybe the text is misleading then.  There should be two independent checks,
Check 1) if s-s-t is greater than Rate A or s-t-s is greater than Rate A (the reverse side), then an error should be generated with the message "Rate A thermal limit limit violated".
Check 2) if theta_from_bus - theta_to_bus is smaller than min_angle_difference or greater than max_angle_difference, then an error should be generated with the message "Angle difference bound violated".

Separated the validation for Rate A thermal limit and angle difference bounds.
Please advise if the following are correct (in the current implementation):

As per current implementation the Angle difference bound violation will be validated, irrespective of the value of Rate A i.e. even if Rate A is zero.
The comparison is done using the 'angle' attribute present in the branch data. (this is a doubt - because using this attribute we decide whether a line is a transformer or not)

This appears to be fixed in SHA: 315cc80964ec0af6944902bc1c71cdef6d3e341a


[json-dto] updated to v.0.2.8

json-dto project updated to the latest version.

Thanks for the PR!


Replace Workshop Doors with Cage Traps

A cage trap would protect the rest of a base from failed mood moody dwarves/werecreatures.
Well I'd rather have two doors and a cage trap in between (I like airlocks) but I won't complain if it's just a cage trap.

Do former citizens get caught in traps? I expected then to still have the TRAPAVOID token.

I "used to" catch berserk dwarves in cage traps. Other insanities would walk over the traps IIRC. Not sure if that was updated out. And i seem to remember werecreatures getting caught when transformed.  I'll try to do more research on it when in get a chance. (Aka, less lazy)

This is an article from an older version, I am sure I've had success with this still in later versions. Though, again, I'm not sure if that has been updated out.
http://dwarffortresswiki.org/index.php/40d:Trap#Berserk_dwarves
As for werebeast trapavoid it seems they are according to the wiki. I thought I caught them religiously in the past but I guess it was either from fainting/stumbling or a stranger changed form conveniently before walking into a cage trap.

Hmm, I wonder if moving the hospital back a bit and filling the path to it with cage traps would work better...

Shouldn't an individual user be able to personally modify the plan templates to achieve this? I feel this is too 'easy/cheaty' and doesn't 'look nice/natural' and shouldn't be the standard/default.


 This should help fix them.
An incidental benefit is that this PR includes a patch for the docusaurus-plugin-openapi-docs plugin to enable our multi-instance setup.

Preview is available here:http://developers-pr745.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr745.previews.kube001.services.stellar-ops.com


Sc 3853/looker download dashboard as file

Getting this error when trying to run this blueprint. Trying to pass in 11 as the dashboard_id

I'm getting an error on the import of sdk_exceptions. Are you getting this on your side @Shamwayne?

Fixed, had to do with the documentation/tutorial i was using for looker being from an outdated version


Update Babel & add out-of-the-box debug config for VSCode

Update to new major version of Babel, and performing minimal transforming (just Flow type removal and es6->commonjs module transform).
Added .vscode config files for easy debugging on any/all three projects. The debugging is conveniently done directly on Flow src/*.js files (this capability required the Babel and Flow updates).
Minor update to gaia-reader to allow for the same storage config env param as gaia-hub. This allows the project to be pulled and ran/debug in vscode with no configuration file setup.

This PR contains a couple hotfixes which where cherrypicked and PR'd to master - see the following PRs for discussion on those changes:

https://github.com/blockstack/gaia/pull/158
https://github.com/blockstack/gaia/pull/157

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

ping @kantai @jcnelson
Would be nice to get this merged in for use in the feature branches

@zone117x Can you sign our contributor license agreement? Looks like we are near to merging this.

Looks good to me.  Go ahead and merge :+1:


Installed<EMAIL_ADDRESS>without schema throws implicit error on PrismaClientExtends in .prisma/client

Bug description
If you set up a minimalistic project without a schema file, which imports @prisma/client then the build with skipLibCheck: false, returns an issue coming from .prisma/client
This worked fine on version 4.7.1 but was introduced in version 4.8.0
This issue blocks the  nexus-prisma build unless skipLibCheck: true is enabled.
An error from the build step.
node_modules/.prisma/client/index.d.ts:45:9 - error TS2589: Type instantiation is excessively deep and possibly infinite.

45   }) => PrismaClientExtends<runtime.Types.Utils.PatchDeep<Args, ExtArgs>>)
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

node_modules/.prisma/client/index.d.ts:45:29 - error TS2344: Type '{ [K in keyof (Args & ExtArgs)]: any; }' does not satisfy the constraint 'RequiredArgs'.
  Type '{ [K in keyof (Args & ExtArgs)]: any; }' is not assignable to type 'NameArgs'.
    Types of property 'name' are incompatible.
      Type '("name" extends keyof Args ? keyof Args & "name" extends keyof ExtArgs ? Args[keyof ExtArgs & keyof Args & "name"] extends object ? ExtArgs[keyof ExtArgs & ... 1 more ... & "name"] extends object ? Args[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof ExtArgs & ... 1 more ... & "name"] : ExtArg...' is not assignable to type 'string | undefined'.
        Type '"name" extends keyof Args ? keyof Args & "name" extends keyof ExtArgs ? Args[keyof ExtArgs & keyof Args & "name"] extends object ? ExtArgs[keyof ExtArgs & ... 1 more ... & "name"] extends object ? Args[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof ExtArgs & ... 1 more ... & "name"] : ExtArgs...' is not assignable to type 'string | undefined'.
          Type '(keyof Args & "name" extends keyof ExtArgs ? Args[keyof ExtArgs & keyof Args & "name"] extends object ? ExtArgs[keyof ExtArgs & ... 1 more ... & "name"] extends object ? Args[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof ExtArgs & ... 1 more ... & "name"] : ExtArgs[keyof ExtArgs & ... 1 more...' is not assignable to type 'string | undefined'.
            Type 'keyof Args & "name" extends keyof ExtArgs ? Args[keyof ExtArgs & keyof Args & "name"] extends object ? ExtArgs[keyof ExtArgs & ... 1 more ... & "name"] extends object ? Args[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof ExtArgs & ... 1 more ... & "name"] : ExtArgs[keyof ExtArgs & ... 1 more ...' is not assignable to type 'string | undefined'.
              Type '(Args[keyof ExtArgs & keyof Args & "name"] extends object ? ExtArgs[keyof ExtArgs & keyof Args & "name"] extends object ? Args[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof ExtArgs & ... 1 more ... & "name"] : ExtArgs[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof Ext...' is not assignable to type 'string | undefined'.
                Type 'Args[keyof ExtArgs & keyof Args & "name"] extends object ? ExtArgs[keyof ExtArgs & keyof Args & "name"] extends object ? Args[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof ExtArgs & ... 1 more ... & "name"] : ExtArgs[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof ExtA...' is not assignable to type 'string | undefined'.
                  Type 'Args[keyof ExtArgs & keyof Args & "name"] | (ExtArgs[keyof ExtArgs & keyof Args & "name"] extends object ? Args[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof ExtArgs & ... 1 more ... & "name"] : ExtArgs[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof ExtArgs & ... 1 mo...' is not assignable to type 'string | undefined'.
                    Type 'ExtArgs[keyof ExtArgs & keyof Args & "name"] extends object ? Args[keyof ExtArgs & keyof Args & "name"] extends Function ? Args[keyof ExtArgs & ... 1 more ... & "name"] : ExtArgs[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof ExtArgs & ... 1 more ... & "name"] : { [K in keyof (Args[keyof ExtA...' is not assignable to type 'string | undefined'.
                      Type '(Args[keyof ExtArgs & keyof Args & "name"] extends Function ? Args[keyof ExtArgs & keyof Args & "name"] : ExtArgs[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof ExtArgs & ... 1 more ... & "name"] : { [K in keyof (Args[keyof ExtArgs & ... 1 more ... & "name"] & ExtArgs[keyof ExtArgs & ... 1 mo...' is not assignable to type 'string | undefined'.
                        Type 'Args[keyof ExtArgs & keyof Args & "name"] extends Function ? Args[keyof ExtArgs & keyof Args & "name"] : ExtArgs[keyof ExtArgs & ... 1 more ... & "name"] extends Function ? Args[keyof ExtArgs & ... 1 more ... & "name"] : { [K in keyof (Args[keyof ExtArgs & ... 1 more ... & "name"] & ExtArgs[keyof ExtArgs & ... 1 mor...' is not assignable to type 'string | undefined'.
                          Type 'Args[keyof ExtArgs & keyof Args & "name"] | (ExtArgs[keyof ExtArgs & keyof Args & "name"] extends Function ? Args[keyof ExtArgs & ... 1 more ... & "name"] : { [K in keyof (Args[keyof ExtArgs & ... 1 more ... & "name"] & ExtArgs[keyof ExtArgs & ... 1 more ... & "name"])]: K extends keyof Args[keyof ExtArgs & ... 1 mo...' is not assignable to type 'string | undefined'.
                            Type 'ExtArgs[keyof ExtArgs & keyof Args & "name"] extends Function ? Args[keyof ExtArgs & keyof Args & "name"] : { [K in keyof (Args[keyof ExtArgs & ... 1 more ... & "name"] & ExtArgs[keyof ExtArgs & ... 1 more ... & "name"])]: K extends keyof Args[keyof ExtArgs & ... 1 more ... & "name"] ? K extends keyof ExtArgs[keyof ...' is not assignable to type 'string | undefined'.
                              Type 'Args[keyof ExtArgs & keyof Args & "name"] | { [K in keyof (Args[keyof ExtArgs & keyof Args & "name"] & ExtArgs[keyof ExtArgs & keyof Args & "name"])]: K extends keyof Args[keyof ExtArgs & ... 1 more ... & "name"] ? K extends keyof ExtArgs[keyof ExtArgs & ... 1 more ... & "name"] ? Args[keyof ExtArgs & ... 1 more ......' is not assignable to type 'string | undefined'.
                                Type '{ [K in keyof (Args[keyof ExtArgs & keyof Args & "name"] & ExtArgs[keyof ExtArgs & keyof Args & "name"])]: K extends keyof Args[keyof ExtArgs & ... 1 more ... & "name"] ? K extends keyof ExtArgs[keyof ExtArgs & ... 1 more ... & "name"] ? Args[keyof ExtArgs & ... 1 more ... & "name"][K] extends object ? ExtArgs[keyof...' is not assignable to type 'string'.

45   }) => PrismaClientExtends<runtime.Types.Utils.PatchDeep<Args, ExtArgs>>)
                               ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Found 2 errors in the same file, starting at: node_modules/.prisma/client/index.d.ts:45

How to reproduce

Clone https://github.com/rostislav-simonik/prisma-client-type-issue
yarn
yarn build

Expected behavior
Should build without any issues
Prisma information
No schema involved
Environment & setup

OS: macOS, Windows, Debian
Database: No database is involved in the given phase
Node.js version: 14.x, 16.x 18.x

https://github.com/graphql-nexus/nexus-prisma/pull/332
Prisma Version
prisma                  : 4.8.0
@prisma/client          : 4.8.0
Current platform        : darwin
Query Engine (Node-API) : libquery-engine d6e67a83f971b175a593ccc12e15c4a757f93ffe (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/@prisma/engines/migration-engine-darwin)
Introspection Engine    : introspection-core d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/@prisma/engines/introspection-engine-darwin)
Format Binary           : prisma-fmt d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/@prisma/engines/prisma-fmt-darwin)
Format Wasm             : @prisma/prisma-fmt-wasm 4.8.0-61.d6e67a83f971b175a593ccc12e15c4a757f93ffe
Default Engines Hash    : d6e67a83f971b175a593ccc12e15c4a757f93ffe
Studio                  : 0.479.0

Thanks for reporting & thanks for the super handy reproduction @rostislav-simonik - We are looking into it.

@danstarns Is the fix coming? I am facing this issue as well and I can't build my project

@698373862 Please use 4.7.1 for now. This has a good chance to make it into the next 4.9.0 release.
So, keep an eye on this issue to know when it's resolved.

@Jolg42 just want to check if there is any update for this issue. I would like to pick some strategy (workaround it or wait until it's fixed here) for nexus-prisma package.

Just found this again 🙈 @rostislav-simonik Could you confirm this issue is still valid and that

This issue blocks the  nexus-prisma build unless skipLibCheck: true is enabled.

@rostislav-simonik Thanks for checking! It looks like your @prisma/client version is 4.8.0 from the output you shared, maybe upgrading Prisma Client to 4.14.1 will reproduce the problem?

@Jolg42 I have locally upgraded prisma to 4.14.1, that's why I have attached version info. Just adjusted the sample as well.

ok, looks like that's what fixed the issue, thx. Closing ticket.

This seems to still be happening on 4.14.1 and 4.15.0 for me.
app/components/table.tsx:112:30 - error TS2589: Type instantiation is excessively deep and possibly infinite.

112                             {value?.value?.toString()}

I've only run into this in my current project where I use Json data types in my schema, and I can see that its typings are pretty complex, so maybe that's the problem?

@ariofrio Could you open a new issue and provide the necessary info to attempt a reproduction? I'm curious to know if it's reproducible on the newer versions like you said and not-reproducible on older versions (which ones)?

@ariofrio Could you open a new issue and provide the necessary info to attempt a reproduction? I'm curious to know if it's reproducible on the newer versions like you said and not-reproducible on older versions (which ones)?

Did you create an issue for this? I've managed to solve the problem by making a small change to the generated type and would like to contribute.

@allansson Could you tell us more about this small change? 👀
I would recommend opening an issue or discussion mentioning this.

@allansson It's a very tiny change.
The problem appears to be this type definition: https://github.com/prisma/prisma/blob/785905e7e86b8d94627fb18e3d09d860a710dc46/packages/client/src/runtime/core/types/Utils.ts#L52
The problem disappears if I change it to the following in my generated client:
export type JsonObject = { [key: string]?: JsonValue }

I think the problem is that saying Key in string means each value in the union of every possible string, causing typescript to expand the type infinitely.

I added an issue for it here: https://github.com/prisma/prisma/issues/19905


Is the package not available in the Dromara warehouse

What should I do to use it now
Is the package not available in the Dromara warehouse? What should I do to use it now? Is there a successful POM file? Thank you

We will release the new version as soon as possible.

We will release the new version as soon as possible.

So is there no way to do a use now? I am not a Java expert, please let me know if there is any way, thank you very much

Try this https://shenyu.apache.org/projects/shenyu-2.3.0/overview/

Try this https://shenyu.apache.org/projects/shenyu-2.3.0/overview/

not work ,thanks for help

I'm not sure I fully understand your question.

after 2.3.0 we already donate project to Apache and rename soul to shenyu. We are releasing apache version 2.4.0. You can use it for the next 2 weeks.
before 2.3.0 you can use pom like the below:

https://mvnrepository.com/search?q=soul
<!-- https://mvnrepository.com/artifact/org.dromara/soul-spring-boot-starter-gateway -->
<dependency>
    <groupId>org.dromara</groupId>
    <artifactId>soul-spring-boot-starter-gateway</artifactId>
    <version>2.3.0-RELEASE</version>
</dependency>

I'm not sure I fully understand your question.

after 2.3.0 we already donate project to Apache and rename soul to shenyu. We are releasing apache version 2.4.0. You can use it for the next 2 weeks.
before 2.3.0 you can use pom like the below:

https://mvnrepository.com/search?q=soul
<!-- https://mvnrepository.com/artifact/org.dromara/soul-spring-boot-starter-gateway -->
<dependency>
    <groupId>org.dromara</groupId>
    <artifactId>soul-spring-boot-starter-gateway</artifactId>
    <version>2.3.0-RELEASE</version>
</dependency>

finally works! thanks!!!!!!!!!!!


Adding concurrency concepts to the syllabus

This is a placeholder issue for the work on concurrency related concepts and learning exercises.
Overview
This will be the first bit for teaching concurrency in the syllabus. Overall, we want to add the following concepts:

goroutines and waitgroups (two concepts in one exercise to allow for easier testing)
channels (potentially incl. range over channel)
select
mutex

Later we could add more things:

atomics
context
errgroup, syncmap and other helper stuff

Besides that, we also already have some unfinished work regarding net/http in store.
Important Docs
If you have not yet contributed to concept exercises before, the followig upfront reading is required to acquire the necessary background knowledge.
Here you can read about what Concept Exercises are and how they are structured:

What are Concept Exercises?
Concept Exercises
Concepts

Also, be aware of these general guidelines:

Exercism Markdown Specification
Exercism Formatting and Style Guide

Hey @junedev! I'd like to start work on this.
Specifically this item:

goroutines and waitgroups (two concepts in one exercise to allow for easier testing)

Learning Objectives
Here's the learning objectives that I think would be beneficial for students to know.
Goroutines

Understand what a goroutine is and how it relates to an operating system thread.
Use goroutines to asynchronously execute tasks that should not block the main goroutine.
Describe the non-deterministic execution behavior of goroutines and how it can lead to data races.

Wait Groups

Understand what a WaitGroup is and how its API works.
Use a WaitGroup to synchronize the execution of multiple goroutines.
Describe what happens when WaitGroups are used incorrectly.

Exercise
This exercise is called "Task Runner". The student must program a function that concurrently executes a slice of functions provided by the caller, using a WaitGroup to ensure all of the goroutines have successfully finished executing.
The API for this function looks like this.
func TaskRunner(workFn ...func()) {}

The testing code will call this function, passing in various worker functions that sleep for a period of time. The implementation will have to execute these functions concurrently otherwise the test will timeout and fail. For example, if we pass in three worker functions that take 100, 200, and 300 milliseconds respectively, then the implementation should take no longer than 300 milliseconds to return +/- a few percent to account for scheduling and time variations. The test will use a context with a timeout to track this execution.
Here's example code for how the test will call the student's implementation.
func TestTaskRunner(t *testing.T) {
	ctx, cancel := context.WithTimeout(context.Background(), 310*time.Millisecond)
	defer cancel()

	done := make(chan struct{})

	go func() {
		TaskRunner(
			func() { time.Sleep(100 * time.Millisecond) },
			func() { time.Sleep(200 * time.Millisecond) },
                        func() { time.Sleep(300 * time.Millisecond) },
		)

		done <- struct{}{}
	}()

	select {
	case <-done:
		// Success case. Do nothing on purpose.
	case <-ctx.Done():
		t.Fatal("Took too long! Failed!")
	}
}

Thanks for the proposal, looks good so far, some additional thoughts that came to mind...
Re the learning objectives for Goroutines:

Maybe it would be good to add some notes in the concept around the topic of "you should always be in control/know when the goroutine that you just kicked off will be done".
A common pitfall in a kind of "hello world" scenario is that someone will kick of a goroutine from main and then wonder why there program just terminates without the goroutine work being finished so this relation between main and other goroutines might be something we want to mention.
I think it would be good to include examples for both cases, a goroutine for some predefined named function and an example for an inline anonymous function.
Might be good to mention something around what happens when there is a closure (i.e. can a goroutine function access outside variables and should it?).

Re waitgroups:

Good point regarding incorrect usage, e.g. we might directly want to encourage to define the waitgroup as a pointer to avoid running into "accidental copying".
We might want to put waitgroups in context a bit by saying that Go's stdlib includes multiple "concurrency helpers" in the sync package and this is one of them.

Re the concepts in general:

Keep in mind that we have this distinction between "introduction" and "about" where the introduction is supposed to contain the minimal content to understand the basics of the concept and solve the exercise and everything else goes into the about. I'm not good at this myself as my introductions are usually a bit long and probably some points I mentioned above are more "about" content but I wanted to bring it up again anyway so you can do better. Also we still have the UI problem that the "about" is a bit hard to discover when you are on the site. (It's easy via google though as we show that one if you are not logged in.)

Re the exercise:

Great idea regarding how to test!
As a reminder, for the actual exercise the task(s) should be wrapped in some theme/story.  Also the exercise name would rather follow the story. E.g. the exercise would be called "spring cleaning" and the functions that are passed in are cleanKitchen and cleanBathroom. Probably not the best example but hopefully you got the point.
I wonder whether there is more than one task here, more then one scenario we want the student to practice ... I need to think about this a bit more ... maybe a case where you would run the function multiple times and call Add with a different number, maybe something where the student needs to use something like i := i to resolve an concurrency issue ... (No blocker for you, if something comes to mind, I'll leave a note and we can discuss whether we want to add something. Or maybe you have an idea.)


Fix Token Get

Hi there!
Can you consider to add this little fix for getting a multi permission token from Instagram?
The issue is that the "+" separator it get %scaped and Instagram service don't work to well with them.
Cheers!

It seems that has some conflicts but i can't see them... strange

Hi @shyambhat, I'm experiencing this problem too and according to this pull request, changing the "+" to " " solved the problem. Hope you can merge this into the main branch soon! Cheers!

wait have you guys tried on Xcode 7 seed?

Fixed in #161


Introduce List Item Settings states in accordance to the design file

We are missing some states for the list item settings which are defined in the design file:

Filled, Hover, and Active being added in https://github.com/bitcoin-core/gui-qml/pull/241

https://github.com/bitcoin-core/gui-qml/pull/243 introduces disabled
The remaining states are

Empty
Error

EMPTY state added in https://github.com/bitcoin-core/gui-qml/pull/256


[WIP] Docs for decommissioning and removing nodes

Update cockroach quit doc.
Add cockroach node decommission doc.
Update command overview and sidenav.

TODOs:

Update cockroach node status doc.
Add cockroach node recommission doc.
Improve rolling upgrade doc.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b2a273faad958b18f796bc981133a0cac4432b93/

@tschottdorf, @bdarnell, I still have a bit of work to do, but I'd like your early feedback on how I've documented decommissioning and removing nodes. Please take a look at the changes to stop-a-node.md and the new decommission-a-node.md file.

Looks good! I don't fully understand where the docs sit in the greater scheme of things, but it seems that there's a bit of duplication that's likely to rot? Other than that, only two points:

./cockroach quit --decommission is essentially ./cockroach node decommission <self> && ./cockroach quit. That means you'll use it to decommission and then stop a node, it's not necessary to decommission it first.
Discussing the case in which multiple nodes are decommissioned would be good. It's more efficient to do them all at once than one after another to minimize data movement.
The diagrams are good!

Reviewed 21 of 21 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

_includes/cli/decommission-a-node.html, line 8 at r1 (raw file):

1. Confirm that there are enough nodes to take over the replicas from the node you want to remove. See [Considerations](decommission-a-node.html#consideration) for some example scenarios.

2. [Install the `cockroach` binary](install-cockroachdb.html) on a machine separate from the node.

This isn't necessary, can do this from one of the machines itself.

v1.1/stop-a-node.md, line 9 at r1 (raw file):

Changed in v1.1: This page shows you how to use the `cockroach quit` [command](cockroach-commands.html) to either temporarily stop a node that you plan to restart or permanently remove a node that has already been [decommissioned](decommission-a-node.html).

Generally, you temporarily stop nodes during the process of [upgrading your cluster's version of CockroachDB](upgrade-cockroach-version.html), whereas you permanently remove nodes when downsizing a cluster.

or reacting to hardware failures.

Comments from Reviewable

Oh, and perhaps a Considerations section that removes a node that had a hardware failure would be interesting (i.e. use --wait=live since the node is already dead).

Reviewed 21 of 21 files at r1.
Review status: all files reviewed at latest revision, 8 unresolved discussions, some commit checks failed.

_includes/cli/decommission-a-node.html, line 10 at r1 (raw file):

2. [Install the `cockroach` binary](install-cockroachdb.html) on a machine separate from the node.

3. Run the [`cockroach node status`](view-node-details.html) command and identify the ID of the node you want to remove:

If the node is up, it's often easier to ask it for its ID than to scan the node status output in a large cluster:  cockroach sql --security-flags --host=<node-to-be-removed> -e 'show node_id'. The node ID is also printed when the node starts up.

v1.1/decommission-a-node.md, line 13 at r1 (raw file):

## Considerations

This should also discuss what it means to decommission a node that's already down (i.e. that this is what you'd do to remove permanently dead nodes from the UI).

v1.1/recommission-a-node.md, line 3 at r1 (raw file):

---
title: Recommission Nodes
summary: Learn why and how to temporarily stop a CockroachDB node.

Recommissioning is not about temporarily stopping a node, it's only for undoing a (mistaken) decommission. I'd include it on the decommission page instead of giving it its own page.

v1.1/remove-a-node.md, line 2 at r1 (raw file):

---
title: Remove a Node

"Removing" a node implies permanent (decomissioning) removal to me, whereas "stop" is very strongly associated with a temporary stop. I'd swap this doc with the stop-a-node one, so "stop" describes the temporary quit process and "remove a node" is the high-level guide about the two options.

v1.1/remove-a-node.md, line 7 at r1 (raw file):

---

To stop a CockroachDB node running in the background, run the `cockroach quit` [command](cockroach-commands.html) with appropriate flags. To stop a node running in the foreground, use **CTRL + C** or run `cockroach quit` from another shell.

Sending a signal to the process is also a valid option (for both foreground and background  processes). This is the mechanisms that most process managers would use.

v1.1/remove-a-node.md, line 9 at r1 (raw file):

To stop a CockroachDB node running in the background, run the `cockroach quit` [command](cockroach-commands.html) with appropriate flags. To stop a node running in the foreground, use **CTRL + C** or run `cockroach quit` from another shell.

The `quit` command allows in-flight requests to complete and then shuts down the node. Once a node has been offline for approximately 5 minutes, CockroachDB automatically rebalances replicas from the missing node, using unaffected replicas on other nodes as sources.

Not just the quit command - ctrl-c and signals also allow in-flight requests to complete.

Comments from Reviewable

Review status: all files reviewed at latest revision, 8 unresolved discussions, some commit checks failed.

_includes/cli/decommission-a-node.html, line 10 at r1 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
If the node is up, it's often easier to ask it for its ID than to scan the node status output in a large cluster:  cockroach sql --security-flags --host=<node-to-be-removed> -e 'show node_id'. The node ID is also printed when the node starts up.

... or it's printed in the admin ui, if what you know is the host it's running on.
Note that the node may be dead, in which case they shouldn't try to talk to the node.

Comments from Reviewable

TFTR, @tschottdorf and @bdarnell. Will rework soon.

_includes/cli/decommission-a-node.html, line 8 at r1 (raw file):
Previously, tschottdorf (Tobias Schottdorf) wrote…
This isn't necessary, can do this from one of the machines itself.

Hmm, you can ssh onto the node, it's true, but I think I've been told by @mberhault or @bdarnell that it's best to recommend running client commands from elsewhere?

Comments from Reviewable

v1.1/decommission-a-node.md, line 13 at r1 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
This should also discuss what it means to decommission a node that's already down (i.e. that this is what you'd do to remove permanently dead nodes from the UI).

In that case, do you just run the cockroach node decommission command and the UI will catch on?

Comments from Reviewable

v1.1/recommission-a-node.md, line 3 at r1 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
Recommissioning is not about temporarily stopping a node, it's only for undoing a (mistaken) decommission. I'd include it on the decommission page instead of giving it its own page.

Sorry. This is just a stub page with incorrect copy. I'll remove it and add this content to the decommission page, as you suggest.

Comments from Reviewable

v1.1/remove-a-node.md, line 2 at r1 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
"Removing" a node implies permanent (decomissioning) removal to me, whereas "stop" is very strongly associated with a temporary stop. I'd swap this doc with the stop-a-node one, so "stop" describes the temporary quit process and "remove a node" is the high-level guide about the two options.

Again, sorry. This is just a stub I left in place accidentally. I think I'll try to have one page, Stop or Remove a Node, cover both cases.

Comments from Reviewable

Review status: all files reviewed at latest revision, 8 unresolved discussions, some commit checks failed.

v1.1/decommission-a-node.md, line 13 at r1 (raw file):
Previously, jseldess wrote…
In that case, do you just run the cockroach node decommission command and the UI will catch on?

Yes. (Just don't use --wait=all, or it won't finish)

Comments from Reviewable

Review status: all files reviewed at latest revision, 8 unresolved discussions, some commit checks failed.

_includes/cli/decommission-a-node.html, line 8 at r1 (raw file):
Previously, jseldess wrote…
Hmm, you can ssh onto the node, it's true, but I think I've been told by @mberhault or @bdarnell that it's best to recommend running client commands from elsewhere?

Serious deployments would likely have a controller host, but generally I don't think it's necessary. @mberhault and @bdarnell are definitely the authority on what we want to recommend though.

Comments from Reviewable

Review status: all files reviewed at latest revision, 8 unresolved discussions, some commit checks failed.

_includes/cli/decommission-a-node.html, line 8 at r1 (raw file):
Previously, tschottdorf (Tobias Schottdorf) wrote…
Serious deployments would likely have a controller host, but generally I don't think it's necessary. @mberhault and @bdarnell are definitely the authority on what we want to recommend though.

In general, I think it's fine for our instructions to demonstrate running the command on a node; we don't need to be didactic about this every time. However, because decommission is a command that is intended to be used some of the times on a downed node, it's probably a good idea to demonstrate this command on a node other than the one to be decommissioned.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/66fd90c516da38cc230c3fcfa1178cdcb24e6d19/

@tschottdorf and @bdarnell, please take another look.

stop-a-node.md now focuses on temporary stopping.
remove-a-node.md now focuses on decommissioning and node removal.
I expanded view-node-details.md to cover the decommission and recommission subcommands and flags. In a follow-up PR, I'll add more details about the response fields for those commands.

Review status: 12 of 28 files reviewed at latest revision, 8 unresolved discussions, some commit checks pending.

v1.1/stop-a-node.md, line 9 at r1 (raw file):
Previously, tschottdorf (Tobias Schottdorf) wrote…
or reacting to hardware failures.

Done.

_includes/cli/decommission-a-node.html, line 8 at r1 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
In general, I think it's fine for our instructions to demonstrate running the command on a node; we don't need to be didactic about this every time. However, because decommission is a command that is intended to be used some of the times on a downed node, it's probably a good idea to demonstrate this command on a node other than the one to be decommissioned.

Done.

_includes/cli/decommission-a-node.html, line 10 at r1 (raw file):
Previously, tschottdorf (Tobias Schottdorf) wrote…
... or it's printed in the admin ui, if what you know is the host it's running on.
Note that the node may be dead, in which case they shouldn't try to talk to the node.

Using both of these methods now, in different places.

v1.1/decommission-a-node.md, line 13 at r1 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
Yes. (Just don't use --wait=all, or it won't finish)

Done.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f9e354220631e477ae8cfd3c8aae40822c2cb5a8/

Reviewed 14 of 21 files at r2, 2 of 2 files at r3.
Review status: all files reviewed at latest revision, 8 unresolved discussions, all commit checks successful.

Comments from Reviewable

Decided to add descriptions for fields in cockroach node subcommand responses.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/5ccb38e5482e125cc12f12b81f3e6d6c33f2d8cc/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f7bce20d880a1ac5ef36200f409ae02b3b504f5d/


Feature Request: Put files in subfolder instead of cbz archive for easier post download deduplicating

Hey, I have been using your program since you posted it on reddit.  I hope it's ok to request a feature here.  The only issue I have had once you helped me figure out how to use nHA is the sheer amount of duplicates.  I don't program, so I have no idea how hard it would be to have the program figure out which images are dupes before downloading them, but I have a feeling that would be a huge headache to implement.
I have the idea for what I think would be an easier workaround on your end.  If you could make it, so there is a flag(I don't know the correct term) in the .env file so we could choose not to have the images put in a cbz file.  Instead have it put each comic into its own subfolder along with the cbz xml file.  What this would do is make it easy just to use a 3rd party duplicate file finder to scan the subfolders and delete the dupes.
Sure, you would still have to download the dupes, but it then becomes trivial to find and delete them.  Sure it won't delete the xml files for the dupe folders, but once the pics are gone it is as simpler as sorting the folders by size and deleting the tiny ones.  Then it would just be figuring out a way to batch making cbz files out of those subfolders after the de-duping.
This is just a thought.  I know nothing about programming, so this might be something that isn't easy to do for your program or hell you might not feel like adding this kind of feature.  Either way, I want to thank you for releasing it for free for everyone else.  You didn't have to, but you made a lot of people's lives a lot easier in doing so.

Thank you for your idea. :) This is a duplicate of issue #2 though, I'll have to ask you to please copy and paste your message there so we can keep all ideas regarding deduplication together at 1 place, thank you.


[PHPStan] Update to PHPStan ^1.7.1

@paulbalandan @kenjis @MGatner update to PHPStan 1.7.1 seems fix infinite loop issue on 1.7.0 on https://github.com/codeigniter4/CodeIgniter4/pull/6019

Also re-run rector to apply PrivatizeFinalClassPropertyRector on FilterTest.php
Also Clean up ignored PHPStan errors.

Checklist:

[x] Securely signed commits

@samsonasik Thank you!


Fix linting errors

This branch contains fixes for linting errors which are trivial to fix but can't be automatically corrected. Fixing the remaining errors will require some deeper thinking.

I manually tested the application to make sure that this didn't cause any visible problems, and obviously it passes all of our automated tests, though I think on this upcoming release in particular we'll want to add more tests for our sequences to verify all behavior is correct.  I'm going to go ahead and merge to get all of these lint fixes in at once.
FYI @czh-orz -- this will cause your generated code to fail if you rerun the generator, as we are only fixing the generated code.  Please refer to the fixes here and have them reflected in the generator, and ask @Jammjammjamm if needed.  Just regenerating the code and doing a git diff highlights what is changed really well.


Fix ssr style rendering

:star: PR built and available in a preview environment drw89-test-domi-pr-5 here


Add TKG_SHA param

Signed-off-by: lanxia<EMAIL_ADDRESS>

Fix for https://github.com/eclipse/openj9/issues/7961


Discuss whether to expose when a Subscription is Open/Closed via API

Filing an issue rather than a PR, because it requires discussion.
Do you think we should expose to API users whether a subscription is open or closed?
At the moment there's no public method to read the isClosed variable and it seems like it would be useful to API users. On the other hand it does increase the API's surface area.

I would vote for no.
There's no good thread-safe way to answer the question; all you can get, at best, is a hint.  You might read .isClosed in Thread A and it returns false, and so you decide to do something with the object, only to have Thread B close it a moment later after the check.
And the only way around that problem is making just about every method on an object fully synchronous with a lock.  That's never going to be acceptable for performance.  Users should keep track of Publications and Subscriptions and manage their lifecycle themselves; allowing anything else encourages bad application design by usually allowing users to get away with it.

@strangelydim I agree and the "edge conditions" I referred to are not common but as you point out are possible.
My vote is to do the volatile check but allow it to be be something that can be turned on or off via a system property.

Ok. Thanks for your feedback gents. I see your point, we're just encouraging race conditions if we expose the field.
I'm a bit concerned that if you have two subscriptions to the same stream, then closing one of them at the moment seems to mean that you close both of them. This puts a lot of burden on the API user to manage their resources which I think we should be managing for them. In fact I can't see a way of managing this nicely in my code without reference counting my subscriptions and closing them at the end.
Wouldn't it be better to have the close method close the single subscription object, and not other subscriptions? Apologies if this has been discussed before, but i can't recall a reason why that's an issue.

Additionally, we can provide the option to no unmap the buffers and leave them to GC. This way it is fast and safe but is a strategy that could not be used in tests or a server that never runs GC.

"Unique receivers" anyone? :-)
Having a close method close only the specific subscription object (and not other subscriptions) allows much more flexibility. For example, two subscriptions to the same stream could serve completely different purposes semantically, or be the result of two independent threads (who don't know of the other's existence). Closing all subscriptions to a stream would seem kind of... well, rude.

I agree.  We have been burned by conveniently tearing down related state in
the past.  If there is a reason for creating multiple subscriptions, then
they need to be independently manageable.
It may not seem critical now, but when that subscription is buried in some
type of abstraction layer, having a subscription closed automatically is
mysterious and dangerous.
On May 12, 2015 8:10 AM, "David Ameiss"<EMAIL_ADDRESS>wrote:

"Unique receivers" anyone? :-)
Having a close method close only the specific subscription object (and not
other subscriptions) allows much more flexibility. For example, two
subscriptions to the same stream could serve completely different purposes
semantically, or be the result of two independent threads (who don't know
of the other's existence). Closing all subscriptions to a stream would seem
kind of... well, rude.
—
Reply to this email directly or view it on GitHub
https://github.com/real-logic/Aeron/issues/121#issuecomment-101269801.

I agree that Subscriptions should be independently manageable from the client API. This is even more important if there is some kind of persistence strategy where an individual Subscription needs to report what it has read. Additionally, I would be wary of excessive configuration. Configuration should be possible only when absolutely necessary.

In that case I'm going to close this issue and raise another issue to handle the subscriber close scenario.


Ugrade dmd to version 2.100.2

Try upgrading to latest to fix the windows CI error.

It didn't help.


Remove zazi from USSD text for T&C

New USSD text:
You will get an SMS with the clinic info shortly.  Want to hear about the latest health services & info? T&Cs www.brothersforlife.org 1. Female  2. Males 3. No

Issue moved to go-usaid-clinicfinder.


fix: button widget squishing its text & infobox mask click away

Overview
Had problem with the text inside button widgets gettings squished when width of viewer wasn't wide enough to safely contain multiple widgets side by side.
What I've done
Updated the widget align system so that it will wrap its widgets if not enough space. This created a little issue with the Button widgets, so needed to update their min-sizes.
Also, as requested by @lavalse I have made it so the text inside the Button's dropdown menu won't wrap, which was especially undesirable with non-English scripts like Chinese characters.

works quite nice for me . Thank you @KaWaite


Support RSA-PSS without recovery

Currently, it is not possible to sign / verify something that uses the RSA-PSS scheme, it is necessary to use the RSA-PSSR scheme which is very similar but includes the data signed.
Would it be possible to support PSS_SHA1, PSSR_SHA256 and PSS_Whirlpool? Implementation seems trivial as it is provided by cryptopp.

EDIT: actually, by mistake, you implement a RSA-PSS without the recovery because you don't set the putMessage in the SignerFilter which is false by default,. This in turn makes the PSSR-* schemes incompatible with both the verify because the scheme is not supported, and the recover because the message is not included in the payload.
Therefore, I would suggest doing a few things:

modify exec_sign to take a putMessage argument that would be passed to SignerFilter (see cryptopp wiki );
if the scheme is PSSR-* set putMessage to true, if the scheme is PSS-* set it to false;
modify the verify to accept the PSS-* schemes.

Check out this PR: https://github.com/JiriHoffmann/react-native-cryptopp/pull/25

The PR seems good to me!

Closed with #25


feat(coral): add preview banner my-teams-schema-requests in Coral and in Angular

About this change - What it does

adds preview banner to Coral
adds banner with info about new interface to Klaw Angular
🧹 adds a missing resolved value for mock that caused console.error

Resolves: #854
https://user-images.githubusercontent.com/943800/226857868-b079e9e1-2887-4847-98e7-a845670daaeb.mov

It looks good, but maybe we should add the banner in all pages in one PR? :o

Hm, we could. But I feel it's nice to have this as a small PR in the epic, so epics can be closed individually? I mean, not really important :D that was just my reasoning behind splitting it in that way.

I feel like the PR scope "add preview banner" makes sense across all three pages, and should not be that much bigger ^^

🖖  :D
I'll update then! 🏃♀

Updated!


[IRGenDebugInfo] Allow multiple dbg.declare on an alloca

This is unnecessarily dropping debug info, as there is currently no assertion in LLVM. The sharing of stack slot can happen because of AllocStackHoisting, which is run at -Onone too.

@swift-ci please test

@swift-ci please test source compatibility

We're getting
Assertion failed: (FragmentOffset >= OffsetInBits && "overlapping or duplicate fragments"), function addFragmentOffset, file DwarfExpression.cpp, line 686.

This is something I've been meaning to fix at the LLVM level (rdar://124625723) — LLVM should be able to just split two overlapping fragments into two.

In SwiftArgumentParser, we also have a
Assertion failed: ((FrameIndexExprs.size() == 1 || llvm::all_of(FrameIndexExprs, [](FrameIndexExpr &FIE) { return FIE.Expr && FIE.Expr->isFragment(); })) && "conflicting locations for variable"), function addFrameIndexExpr, file DwarfDebug.cpp, line 322.

which is the same as rdar://128155050

@swift-ci please test

@swift-ci please test source compatibility

Source compatibility tests are passing, fixed the one failing AutoDiff test

@swift-ci please smoke test

@swift-ci please test

@swift-ci please test macOS platform


Windows 11 22H2 Dualscreen not supported

Describe the bug
When I start my laptop I get a pop-up message saying taskbarx may not support this version of windows. This started happening after I updated to Windows 22H2. When I'm using my laptop with a dual screen and click on the start button the taskbar changes back to default
To Reproduce
Steps to reproduce the behavior:

Update to the latest version of windows (Windows 11 22H2)
Restart your device.
Use a dual-screen setup
Click on the start icon. you will see the taskbar changing to windows default taskbar

Expected behavior
When I click on the windows icon I expect my taskbar to remain with the same settings as what I've chosen in taskbarx configurator.
Desktop (please complete the following information):

OS: [Windows 11]
Version [22H2]

Additional context
Add any other context about the problem here.

following this issue on 22H2 , hope dev fixes it soon

Can confirm issue with Win11 22H2

Can confirm, updated last night to Win 11 Pro 22H2 and same issue as op w/ latest version of TaskbarX as of today.

Please fix

I have noticed the issue and will try to fix it asap.

Since updating to Windows 11 22H2, taskbarx doesn't work anymore, it doesn't go transparent. I have downloaded the latest version of the rainmeter skin <IP_ADDRESS> but everytime i check it on rainmeter is says <IP_ADDRESS>


test: adding tests for resolveEnvFileNames().

Sample PR for https://github.com/colynb/serverless-dotenv-plugin/pull/70. This same PR should be made against the original repo after https://github.com/colynb/serverless-dotenv-plugin/pull/70 has been merged.

https://github.com/colynb/serverless-dotenv-plugin/pull/76


Failed to create directX device and swapchain!

https://i.imgur.com/29oFpGr.jpg
Run the game as Administrator https://i.imgur.com/rd3bg9O.jpg
Failed to create directX device and swapchain! https://i.imgur.com/Z2Nn03N.jpg

Use: https://framedsc.github.io/GeneralGuides/universal_ue4_consoleunlocker.htm instead, it surpasses this camera and has all the features this one has too, I ported everything over.

thanks


Add end-to-end example of mllama

🚀 The feature, motivation and pitch
Currently we only have examples for text based models here: https://github.com/linkedin/Liger-Kernel/tree/main/examples/huggingface. An example showing how to run mllama vision model end to end would be a great addition.
Alternatives
No response
Additional context
No response

Theres now an end-to-end example for tuning Qwen2-VL which may help those looking to tune an Mllama model as well.


flutter iOS crash

Thread 14 name:  my flutter engine.1.io
Thread 14 Crashed:
0   libsystem_kernel.dylib              0x00000001cf048414 0x1cf020000 + 164884
1   libsystem_pthread.dylib             0x00000001ecaa2b40 0x1ecaa0000 + 11072
2   libsystem_c.dylib                   0x00000001aa66eb74 0x1aa5f8000 + 486260
3   libsystem_malloc.dylib              0x00000001b103349c 0x1b1015000 + 124060
4   libsystem_malloc.dylib              0x00000001b1033740 0x1b1015000 + 124736
5   libsystem_malloc.dylib              0x00000001b101e934 0x1b1015000 + 39220
6   libsystem_malloc.dylib              0x00000001b101b944 0x1b1015000 + 26948
7   libsystem_malloc.dylib              0x00000001b101c95c 0x1b1015000 + 31068
8   Flutter                             0x0000000106383bd4 0x1062f0000 + 605140
9   Flutter                             0x00000001063de49c 0x1062f0000 + 976028
10  Flutter                             0x0000000106620dc4 0x1062f0000 + 3345860
11  Flutter                             0x00000001065c9f78 0x1062f0000 + 2989944
12  Flutter                             0x00000001065cbdf8 0x1062f0000 + 2997752
13  CoreFoundation                      0x00000001a124dfa0 0x1a11ac000 + 663456
14  CoreFoundation                      0x00000001a124dba0 0x1a11ac000 + 662432
15  CoreFoundation                      0x00000001a124cffc 0x1a11ac000 + 659452
16  CoreFoundation                      0x00000001a1246ee4 0x1a11ac000 + 634596
17  CoreFoundation                      0x00000001a124621c 0x1a11ac000 + 631324
18  Flutter                             0x00000001065cbcd4 0x1062f0000 + 2997460
19  Flutter                             0x00000001065cb6d8 0x1062f0000 + 2995928
20  libsystem_pthread.dylib             0x00000001ecaa1b40 0x1ecaa0000 + 6976

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


altering regular expression to also include 'module: ... mode=octal'

I am taking another stab at getting the octal permissions rule to function for all relevant situations.  This time I am also rewriting some of the original code to remove false positives as requested.

Ok taking a break from this for now.  If it is obvious to you how to get the Rule 9 octal permissions working then please point it out.

Unfortunately match_task only gets the already converted number (i.e. it's an integer by the time match_task sees it), whereas match operates on the raw lines.
It's possible to get quite close with match_task if you assume that for each of the last three sets of three bits, if the r bit is not set but w and x are, then it's probably wrong. But 4000 decimal converts to 07640 octal, and is therefore one example (of perhaps many) of a false positive.

#133 works for all sensible file permissions but someone might want nonsense file permissions.

Thanks for figuring it out.  I don't know if I would have thought of that.


Change denominators for HTTPS and Tmail stats

I also took the opportunity to switch to f-strings and update the language in StatsMessage a little.  I didn't think it made sense to update the CyHy, CybEx, Tmail, and HTTPS report messages from DHS to CISA yet, but StatsMessage is only sent to NCATS folks.

Coverage decreased (-0.2%) to 27.406% when pulling bf1042f4c41ce0fd5d66ae7ed4b4e9759c19d39e on improvement/change_denominators into ed9fbbeaa9613d4993ee87d4ac83f4045156f383 on develop.


Card storage does not survive app restart

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Create a Pixel 7 with API 33 (Play Store) emulator
Activate a card
Close the app and reopen it
Card can't be loaded from storage

Expected behavior
Card should be loaded from storage
Smartphone (please complete the following information):

Device: Samsung Galaxy A34 5G SM-A346B/DSN
OS: Android 14 or higher

Additional context
Seems like an issue with FlutterSecureStorage
https://github.com/mogol/flutter_secure_storage/issues/653
Open pr that has to be tested
https://github.com/mogol/flutter_secure_storage/pull/664

API level 33 is not working with android 14 or higher. Which versions are creating this bug?

Can not reproduce this. Browser Stack- Android 14, Pixel 8, The card is still there after closing the App.

Reported bug from user:
Device: Google Pixel 7
App version name: 2024.1.5
Android version: Android 14 (SDK 34)

Tried to reproduce this unsuccessfully. Browserstack Pixel 8 with Android 14. Force stopped the app and cleared cache. Card was still there. Also tried to reproduce locally on differend emulators with differend android version and on my real device Samsung Galaxy A33 with Android 13.

Reported per Mail in the last 7 days:
The same problem happens here:

Sony Experia i13113, Android-Version 10; App Version does not matter. In all Versions of the App.
Xiaomi Redmi Note 12, Androidversion 14 UKQ1.230917.001, App Version 2024.1.5

I could not reproduce this as well.

Maybe fixed with #1293. Will have to check with upcoming release

New release was deployed on production that includes a new SecureLocalStorage version. We should check the sentry logs and wait if it will be reported

There was a new review on google console that it still occurres.

Gerät: [Samsung Galaxy S24 Ultra]
Sprache des Geräts: Deutsch
Code der App-Version: 168
Name der App-Version: 2024.5.5
Android-Version: Android 14 (SDK 34)

I tested on browserstack version 2024.5.5 with Galaxy S24 Ultra on Android 14 and everythings works as expected

Reported on
Android Handy
Android Version 14 - One UI-Version 6.1
SAMSUNG Galaxy S24
Version Ehrenamtskarte: 2024.8.1

Tested on browserstack 2024.8.1 with Galaxy S24 on Android14. Couldn't reproduce the issue.
Daniel ordered a real device, i will test that next week

Unfortunately, FlutterSecureStorage is somewhat unmaintained (or moving at a very slow pace) ... :/ If it's a bug in FlutterSecureStorage, we cannot upgrade to version 9.2.2 (see https://github.com/mogol/flutter_secure_storage/issues/762)


Add support for type checking with upcomming Numpy 1.20 release.

Checked locally with numpy 1.20 rc1

Some numpy types are now generic so give them an explicit Any. Use types in strings to support older numpy versions
np.int, np.float and np.complex which are aliases for the build in python types are deprecated.
Use the dtype constructor explicitly when needed
Various fixes for interaction between the python types and numpy types

EDIT:
while this does run with older versions of numpy it does not type check. Not sure what the best solution is.
We can add ignores to those lines or just wait until numpy 1.20 is officially released. Or we could disable the non explicit generics for now.

@astafan8 I realized that we can just get this passing with older numpy versions by removing the stubs. I think this is ready for review but I would like to merge https://github.com/QCoDeS/Qcodes/pull/2569 first so we ensure that this does not break any older numpy versions

@jenshnielsen ok, good! is it worth waiting until the stubs start matching the types of numpy 1.20? or is the issue somewhere else? I guess since the stubs are not an official released project (right?), we'd better just stick to numpy 1.20 since it's the latest nunmpy that will alweays be installed when we run mypy in CI?

@jenshnielsen ok, good! is it worth waiting until the stubs start matching the types of numpy 1.20? or is the issue somewhere else? I guess since the stubs are not an official released project (right?), we'd better just stick to numpy 1.20 since it's the latest nunmpy that will alweays be installed when we run mypy in CI?

@astafan8 The stubs are deprecated and will never be updated. The types in numpy 1.20 are the official source of truth

@astafan8 The stubs are deprecated and will never be updated. The types in numpy 1.20 are the official source of truth


Update 3d_scene link

Objective
The current README contains a broken link to the 3d_scene example page, the URL for that page has since changed.
Solution
Update the link to point to the new page.

I did fix the link, it's just on the avian branch (where the updated example also is). I'm merging that branch tomorrow


fix: Fixes wrong config key in service provider

This fixes the config not working when the config file has not been published.

I had the same problem, I confirm the goodness of this PR. Thanks!

@andrew-broberg-five9 Thanks!


Feature/implement query builder override fix

@mikebronner what's the status on this, anything that needs help?

Wasn't able to figure out a working solution yet.


jenkins/kola/do: use gzipped image file

jenkins/kola/do: use gzipped image file
The bzipped image file sometimes results in a timeout during decompression on
the remote side. Gzipped images are supposed to be better supported by
DigitalOcean, so use those.
How to use
[ describe what reviewers need to do in order to validate this PR ]
Testing done
[Describe the testing you have done before submitting this PR. Please include both the commands you issued as well as the output you got.]

[ ] Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)

Maybe we should backport the change now to align the build system in all channels. So far we had no problems coming up from the change, and misalignment always causes inconsistencies (e.g., the gzip change gets documented but LTS doesn't have it) and cherry-pick troubles later.

The changes to compression handling? Yeah, we can do that. The reason this PR is not merged is because when I started testing it, the import still failed with a timeout several times in a row. So I lost some faith in whether bzip/gzip makes a real difference. Had to bump up the timeout instead (https://github.com/flatcar-linux/mantle/commit/d48d25de1cd3ba932ca63e7ef1f03a260f524762).

I think it was even a problem without any timeout constraints but maybe it doesn't happen often anymore because the hardware running the decompression job got upgraded as well or has less load than before, or lbzip2 is used there now…
I'm still for merging but think that if we do so we should first cherry-pick everywhere.

Merging this as is now is pointless as this updates scripts in jenkins directory, which are rather unused.

Ah, we now need to change DIGITALOCEAN_IMAGE_URL_TEMPLATE in ci-automation/ci-config.env

I'm still not convinced this helps. When testing this I found that there were still occasional timeouts during the upload, same as when using bzip2. If no one objects I'd rather close.