Styles not applied in first loading correctly with NextJS

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
When using SX prop I seem to be getting an issue when deploying the application where a lot of the styles are loaded after the dom has rendered. Even though I use the emotion cache in my _documents.tsx, and create and use the theme in _app.tsx.

After my previous issue #29637  got closed because I also thought it solved the issue. I noticed on the live site that it's still an issue even after updating to SX prop.

Expected behavior 🤔
What should is that when rendering the page the first time all the style changes should already be there. but takes a small bit of time before it does.
https://imgur.com/a/ZujFrXd
Steps to reproduce 🕹
The issue is now only visible on the live site (Hosted with vercel).
https://daniiel.dev/
But for you want want to take a look or maybe have an idea what could cause it.
You can have a look at the repo and play around yourself by using the codesandbox bellow
codesandbox: https://codesandbox.io/s/hopeful-bush-5jbz8
Context 🔦
What I'm trying to accomplish is for my production build to look like my local development on initial load.
I think the issue lays in either the _documents.tsx or _app.tsx.
I have attached a link to the 2 images for how it looks in local development and production.
https://imgur.com/a/ZujFrXd
Your environment 🌎
Used both Firefox Developer Edition & Google Chrome (Version: 96.0.4664.110) for testing.
System:
OS: Windows 10 10.0.19044
Binaries:
Node: 16.13.1 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 8.1.2 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: Not Found
Edge: Spartan (44.19041.1266.0), Chromium (96.0.1054.62)
npmPackages:
@emotion/react: ^11.5.0 => 11.5.0
@emotion/styled: ^11.3.0 => 11.3.0
@mui/core:  5.0.0-alpha.53
@mui/lab: ^5.0.0-alpha.53 => 5.0.0-alpha.53
@mui/material: ^5.0.6 => 5.0.6
@mui/private-theming:  5.0.1
@mui/styled-engine:  5.0.2
@mui/system:  5.0.6
@mui/types:  7.0.0
@mui/utils:  5.0.1
@types/react: ^17.0.34 => 17.0.34
react: ^17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
typescript: ^4.3.5 => 4.3.5
--- tsconfig.json ---
{
"compilerOptions": {
"lib": [
"es6",
"dom"
],
"noImplicitAny": true,
"noImplicitThis": true,
"strictNullChecks": true,
"target": "es5",
"allowJs": true,
"skipLibCheck": true,
"strict": false,
"forceConsistentCasingInFileNames": true,
"noEmit": true,
"esModuleInterop": true,
"module": "esnext",
"moduleResolution": "node",
"resolveJsonModule": true,
"isolatedModules": true,
"jsx": "preserve"
},
"include": [
"next-env.d.ts",
"/*.ts",
"/*.tsx",
"src/components"
],
"exclude": [
"node_modules"
]
}

@shorcy Can you try the new _document.js in the our nextjs example? https://github.com/mui-org/material-ui/blob/master/examples/nextjs/pages/_document.js

That fixed the issue. Thanks a lot, @siriwatknp :)

@siriwatknp it doesn't work for me. I just copied everything from example: _app.js, document.js , I runed codemod to convert v4 JSS to MUI v5 styles.
But on first app load appears gigantic icons

Getting the same issue. Then I tried setting style={{width: '1em', height: '1em'}} and it look somewhat ok, but still resizing. I think the styles aren't loading somehow. I'm using static build btw.

Hi @siriwatknp I am experiencing the same issue.
I followed the repo provided by MUI (https://github.com/mui/material-ui/tree/HEAD/examples/nextjs-with-typescript).
The theme is applied in local dev but not when I deploy to production. (https://btdtech.io/)
As you can see from the website, when you first visit it there is no styling applied. If you use the link to navigate to the ABOUT page then you will see it styled. However if you refresh the ABOUT page, the styling disappears again.
This is the link to the repository for your perusal https://github.com/btdtech/company-website.
Look forward to your reply!
Bac

Hi everyone,
I have been digging and it seems that Emotion cache's style component has to style. Do we know why this is? I really would like to get to the bottom of this, otherwise I might have to find another CSS solution.
Cheers,
Bac

I can confirm that our official example does not work. I looking into this.

It seems like the problem comes from this:
// pages/_document.js
const initialProps = await Document.getInitialProps(ctx);
// console.log(initialProps.html) returns empty string
const emotionStyles = extractCriticalToChunks(initialProps.html);

The initialProps.html returns an empty string which is why emotion cannot create correct styles. When I downgrade react from latest(v18.0.0) to v17.0.2, it works. So I think it is something wrong with NextJS + React 18.

I can confirm that the issue comes from nextjs latest. I switch from latest to canary and it works. @btdtech @ApayRus @Shahzayb Can you try the canary version of nextjs?
-"next": "latest",
+"next": "canary",

Change the package json then run yarn and yarn build. It worked for me.
Note that the latest nextjs (v12.1.6) was published 28 days ago.

I can confirm that the issue comes from nextjs latest. I switch from latest to canary and it works. @btdtech @ApayRus @Shahzayb Can you try the canary version of nextjs?
-"next": "latest",
+"next": "canary",

Change the package json then run yarn and yarn build. It worked for me.
Note that the latest nextjs (v12.1.6) (that does not work) was published 28 days ago.

Thank you so much @siriwatknp . It solved the issue!
I can understand that there is a bug in nextjs, but why was yarn important in all of this? I tried NPM but didn't work.

I can confirm that the issue comes from nextjs latest. I switch from latest to canary and it works. @btdtech @ApayRus @Shahzayb Can you try the canary version of nextjs?
-"next": "latest",
+"next": "canary",

Change the package json then run yarn and yarn build. It worked for me.
Note that the latest nextjs (v12.1.6) (that does not work) was published 28 days ago.

Thank you so much @siriwatknp . It solved the issue!
I can understand that there is a bug in nextjs, but why was yarn important in all of this? I tried NPM but didn't work.

Thanks, I am closing this issue then.

@siriwatknp I downgraded MUI to 4 :-(

@siriwatknp
One way to fix this (even though I am not sure if it's a fix or just a side-effect) is not to use emotionCache.
NextJS now support SSR with emotion. This is also working out with a simple _document  file, without the need for enhancing and style injections.
next.config: ( flag emotion )
/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true,
  compiler: {
    emotion: true,
  },
}

module.exports = nextConfig

_document: ( no extra enhance code and injections )
import { Html, Head, Main, NextScript } from 'next/document'
import theme from 'theme'

export default function Document() {
  return (
    <Html lang="en">
      <Head>
        <meta name="theme-color" content={theme.palette.primary.main} />
        ...
      </Head>
      <body>
        <Main />
        <NextScript />
      </body>
    </Html>
  )
}

_app: ( no cache provider )
export default function App({ Component, pageProps }: Props) {
  const getLayout = Component.getLayout || ((page) => page)

  return (
    // <CacheProvider value={emotionCache}>
    <ThemeProvider theme={theme}>
      {getLayout(<Component {...pageProps} />)}
    </ThemeProvider>
    // </CacheProvider>
  )
}

versions:
    "next": "^12.1.6",
    "@emotion/react": "^11.8.2",
    "@emotion/styled": "^11.8.1",
    "@mui/material": "^5.5.3",
    "react": "^18.1.0",
    "react-dom": "^18.1.0",

@Taliss The difference is that the example uses the advanced approach, not the default approach.

I'm still facing this issue. nothing seems to work for me mentioned above.
ReBank this is the website, I can't give the source code since its enterprise application but I can tell you that I'm using Next.js, MUI, styled-components (not @mui/styled-engine-sc, regular mui configuration with just styled-components styled api). As you can see styles are flickering on the first load. I'm using Next.js SWC and have styled-components turned on in next.config.js and using this configuration. Does anyone have this problem and is there any fix to this?

I'm still facing this issue. nothing seems to work for me mentioned above.
ReBank this is the website, I can't give the source code since its enterprise application but I can tell you that I'm using Next.js, MUI, styled-components (not @mui/styled-engine-sc, regular mui configuration with just styled-components styled api). As you can see styles are flickering on the first load. I'm using Next.js SWC and have styled-components turned on in next.config.js and using this configuration. Does anyone have this problem and is there any fix to this?

I fixed it with adopting styled-engine-sc with yarn resolutions and next webpack resolve alias

I can confirm that the issue comes from nextjs latest. I switch from latest to canary and it works. @btdtech @ApayRus @Shahzayb Can you try the canary version of nextjs?
-"next": "latest",
+"next": "canary",

Change the package json then run yarn and yarn build. It worked for me.
Note that the latest nextjs (v12.1.6) (that does not work) was published 28 days ago and ~I could not find the PR that fixed the issue. If anyone knows, feel free to link the issue and the PR.~
I guess this PR vercel/next.js#36792 fixes the issue.

Hi, I upgraded NextJS from v12.0.10 to v12.1.7-canary.39 and I'm still seeing this issue, the style from the theme won't load on the page's first render, anyone can help?

As of today using nextjs both canary and latest together with mui5 emotion, the style does not load on first render. Is there anything we can do about it other than using @Taliss's approach without the advance features?
I switched from styled-components to emotion because of server rendering issue.. now this :(

"next": "^12.2.0", seems to have fixed the issue.
Working version as of today
       "next": "^12.2.0",
        "@emotion/react": "^11.9.3",
        "@emotion/server": "^11.4.0",
        "@emotion/styled": "^11.9.3",

        "@mui/icons-material": "^5.8.4",
        "@mui/lab": "^5.0.0-alpha.88",
        "@mui/material": "^5.8.5",

I can confirm that the issue comes from nextjs latest. I switch from latest to canary and it works. @btdtech @ApayRus @Shahzayb Can you try the canary version of nextjs?
-"next": "latest",
+"next": "canary",

Change the package json then run yarn and yarn build. It worked for me.
Note that the latest nextjs (v12.1.6) (that does not work) was published 28 days ago and ~I could not find the PR that fixed the issue. If anyone knows, feel free to link the issue and the PR.~
I guess this PR vercel/next.js#36792 fixes the issue.

Still facing the same problem, style is not load on first load, I also followed the _document.js. What else am i missing ?
"react": "^17.0.2",
"next": "canary",

"@emotion/cache": "latest",
"@emotion/react": "latest",
"@emotion/server": "latest",
"@emotion/styled": "latest",

"@mui/icons-material": "^5.6.2",
"@mui/lab": "^5.0.0-alpha.78",
"@mui/material": "^5.6.2",
"@mui/styles": "^5.6.2",
"@mui/system": "5.9.1",

Yup...
Just wasted some time with this one. In case this is anyone else's issue.
https://developer.chrome.com/blog/new-in-devtools-102/#network-preview
I used to be able to click on the dev tools preview tab, and see a nicely rendered page. At some point I've presumably upgraded Chrome (or its done it itself 🤷♂) and things stopped working.
I probably never noticed at the time; so when I next clicked on the preview tab I got the whole 'plain html' with no CSS applied. (and assumed I'd broken something)
I've just turned JavaScript via dev tools and checked; and everything is properly rendering.
TLDR; things might actually be working / don't trust the chrome preview tab.

I followed @Taliss 's comment in this thread: https://github.com/mui/material-ui/issues/30410#issuecomment-1148489813
Works like a charm.
I'm using all the latest packages.
Is there a benefit to using the default approach that is missing with this configuration?
It just seems needlessly complicated.

Adding this to _document.js finally solved the problem
`MyDocument.getInitialProps = async (ctx) => {
const originalRenderPage = ctx.renderPage;
const cache = createEmotionCache();
const { extractCriticalToChunks } = createEmotionServer(cache);
const sheets = new ServerStyleSheets();
ctx.renderPage = () =>
originalRenderPage({
enhanceApp: (App) =>
function EnhanceApp(props) {
return sheets.collect(<App emotionCache={cache} {...props} />);
},
});
const initialProps = await Document.getInitialProps(ctx);
const emotionStyles = extractCriticalToChunks(initialProps.html);
const emotionStyleTags = emotionStyles.styles.map((style) => (
<style
data-emotion={${style.key} ${style.ids.join(" ")}}
key={style.key}
// eslint-disable-next-line react/no-danger
dangerouslySetInnerHTML={{ __html: style.css }}
/>
));
return {
...initialProps,
styles: [...React.Children.toArray(initialProps.styles), sheets.getStyleElement()],
emotionStyleTags,
};
};`

It seems the example repo is now working. I just changed my _app.ts and _document.ts and everything seems to work fine both in local dev and in staging env (wth next build).
I am testing on Brave Browser (which is just a layer on top of Chrome) version 1.43.93 (with Chromium: 105.0.5195.127) and with the following env:
System:
  OS: Linux 5.15 Ubuntu 20.04.5 LTS (Focal Fossa)
Binaries:
  Node: 18.9.0
  npm: 8.19.1
Browsers:
  Chrome: 105.0.5195.125
npmPackages:
  @emotion/react: 11.10.x => 11.10.4
  @emotion/styled: 11.10.x => 11.10.4
  @mui/base:  5.0.0-alpha.98
  @mui/core-downloads-tracker:  5.10.6
  @mui/icons-material: 5.10.6 => 5.10.6
  @mui/material: 5.10.6 => 5.10.6
  @mui/private-theming:  5.10.6
  @mui/styled-engine:  5.10.6
  @mui/system:  5.10.6
  @mui/types:  7.2.0
  @mui/utils:  5.10.6
  @types/react: 18.0.20 => 18.0.20
  react: 18.2.0 => 18.2.0
  react-dom: 18.2.0 => 18.2.0
  typescript: 4.8.3 => 4.8.3

"next": "^12.2.0", seems to have fixed the issue.
Working version as of today
       "next": "^12.2.0",
        "@emotion/react": "^11.9.3",
        "@emotion/server": "^11.4.0",
        "@emotion/styled": "^11.9.3",

        "@mui/icons-material": "^5.8.4",
        "@mui/lab": "^5.0.0-alpha.88",
        "@mui/material": "^5.8.5",

I did what daveteu posted above and I still see the same issue happening but not as often.  I have:
"next": "^12.2.0",
"@mui/lab": "^5.0.0-alpha.88",
"@mui/material": "^5.8.5",
"@mui/styles": "^5.4.1",
Can anyone help please?

Complete the v5 migration with tss-react, it worked for me.
https://mui.com/material-ui/migration/migrating-from-jss/#2-use-tss-react
https://docs.tss-react.dev/ssr/next.js#mui-and-tss-use-different-caches

Hey
I had come across the same issue.
I have tried all the things suggested above but nothing has worked.
Using @Mui v5
Next.js 13
with Typescript
my _document file is
`import React from 'react';
import Document, { Html, Head, Main, NextScript, DocumentContext } from 'next/document';
import { ServerStyleSheets } from '@mui/styles';
export default class MyDocument extends Document {
static async getInitialProps(ctx: DocumentContext) {
const initialProps = await Document.getInitialProps(ctx);
return { ...initialProps };
}
render() {
return (

);
}
}
// getInitialProps belongs to _document (instead of _app),
// it's compatible with server-side generation (SSG).
MyDocument.getInitialProps = async (ctx) => {
// Resolution order
//
// On the server:
// 1. app.getInitialProps
// 2. page.getInitialProps
// 3. document.getInitialProps
// 4. app.render
// 5. page.render
// 6. document.render
//
// On the server with error:
// 1. document.getInitialProps
// 2. app.render
// 3. page.render
// 4. document.render
//
// On the client
// 1. app.getInitialProps
// 2. page.getInitialProps
// 3. app.render
// 4. page.render
// Render app and page and get the context of the page with collected side effects.
const sheets = new ServerStyleSheets();
const originalRenderPage = ctx.renderPage;
ctx.renderPage = () => originalRenderPage({
enhanceApp: (App) => (props) => sheets.collect(<App {...props} />),
});
const initialProps = await Document.getInitialProps(ctx);
return {
...initialProps,
// Styles fragment is rendered after the app and page rendering finish.
styles: [...React.Children.toArray(initialProps.styles), sheets.getStyleElement()],
};
};
`
my_app file is
`import<EMAIL_ADDRESS>import<EMAIL_ADDRESS>import '@mui/material/styles';
import CssBaseline from '@mui/material/CssBaseline';
import ScopedCssBaseline from '@mui/material/ScopedCssBaseline';
import type { AppProps } from 'next/app'
export default function App({ Component,pageProps }: AppProps) {
return (
<>

<Component {...pageProps} />

</>
);
}
`

I followed @Taliss 's comment in this thread: https://github.com/mui/material-ui/issues/30410#issuecomment-1148489813
Works like a charm.
I'm using all the latest packages.

I had a similar problem but i worked around it probably with not the best solution. In my case i was making a project using react and django, this project had a google verification to login and after this it load the home page. In the first load only the buttons itens from material ui package were without the styled, but after you refresh the page the style works again. So i created a context to use a variable that apoint this first load and automatically refresh the page. Like i said, this is not the best way but worked for me.
I hope someone with it.

`"next": "^13.5.2",
"react": "^18.2.0",
"@material-ui/core": "^4.12.4",
"@material-ui/icons": "^4.11.2",
"@material-ui/lab": "^4.0.0-alpha.45",
"@material-ui/styles": "^4.11.5",
`
I have the above configuration work fine but get this issue after updating with the latest version 13.5.2,
@hamza172 I tried your solution but now work me in above vesrion
Thanks in advance if any one can help on this

so what is the right solution now in 2024?

so what is the right solution now in 2024?

@siriwatknp I think it's an important issue. and now after more than 2 years, even with the new versions of Next js, MUI and Emotion, the problem still exists. can you look around please?

https://github.com/mui/material-ui/issues/30410#issuecomment-2037024412
@famdude
I have the same issue. Do you have a solution?

https://github.com/mui/material-ui/issues/30410#issuecomment-2037024412
@famdude
I have the same issue.

My solution used suppressHydrationWarning and solved other details.
It works this way:

If user have not set a preference on the app (localStorage) i get it from his system preference.

While theres no stored preference if user changes his system preferences the app then gets updated to that instantly.

If user has a stored preference then it takes precedence over system's.
I also solved the issue on initial load in which the app rendered a blank screen or either the wrong theme before the theme could get it set by returning a loading screen.

Ps: Im using Next.js v14 and Material UI v5.16
(simplified code)
Root Layout:
`import { CustomThemeProvider } from "@/context/CustomThemeContext";
import React from "react";
import "./globals.css";
// trick to avoid SSR mismatch due to html inline colorMode script
const mockSSRColorMode = () => "light";
export default function RootLayout({
children,
}: {
children: React.ReactNode;
}) {
return (
<html
lang="en"
style={{ colorScheme: mockSSRColorMode() }}
suppressHydrationWarning
>

{/* Inline script to set color scheme on the first load (to avoid wrong color loading screen) */}
<script
dangerouslySetInnerHTML={{
__html:                         (function() {                             const storedColorMode = localStorage.getItem('colorMode');                             const prefersDarkMode = window.matchMedia('(prefers-color-scheme: dark)').matches;                             const colorMode = storedColorMode || (prefersDarkMode ? 'dark' : 'light');                             document.documentElement.style.colorScheme = colorMode;                         })();                    ,
}}
/>

{children}

);
}
`
CustomThemeContext:
`"use client";
import Loading from "@/app/loading";
import { PaletteMode, useMediaQuery } from "@mui/material";
import { grey } from "@mui/material/colors";
import {
createTheme,
responsiveFontSizes,
Theme,
ThemeProvider,
} from "@mui/material/styles";
import { Roboto } from "next/font/google";
import React, {
createContext,
ReactNode,
useContext,
useEffect,
useMemo,
useState,
} from "react";
interface ThemeContextType {
colorMode: PaletteMode;
toggleColorMode: () => void;
}
const ThemeContext = createContext<ThemeContextType | undefined>(undefined);
interface CustomThemeProviderProps {
children: ReactNode;
}
export const CustomThemeProvider: React.FC = ({
children,
}) => {
const [colorMode, setColorMode] = useState("light");
const [loading, setLoading] = useState(true);
const sysPreferDark = useMediaQuery("(prefers-color-scheme: dark)", {
noSsr: true,
});
// This prop determines native elements theme
const setColorSchemeOnHtml = (newMode: PaletteMode) =>
	document.documentElement.style.setProperty("color-scheme", newMode);

// First-load color-mode routine: use stored OR system-preference OR fallback to 'light'
// Set it on state+themecontext AND on <html>'s color-scheme style prop
useEffect(() => {
	const storedColorMode = localStorage.getItem("colorMode") as PaletteMode;
	const newMode = storedColorMode || (sysPreferDark ? "dark" : "light");
	setColorMode(newMode);
	setColorSchemeOnHtml(newMode);
	setLoading(false);
}, [sysPreferDark]);

const theme: Theme = useMemo(() => {
	// ... mui createStyles()
}, [colorMode]);

// User-triggered color-mode change: set preference on storage and html
const toggleColorMode = () => {
	setColorMode((prevMode) => {
		const newMode = prevMode === "light" ? "dark" : "light";
		localStorage.setItem("colorMode", newMode);
		setColorSchemeOnHtml(newMode);
		return newMode;
	});
};

// on first-load the loading screen is immediatelly displayed
// until the theme is loaded with the uptodate color-mode
if (loading) {
	return <Loading />;
}

return (
	<ThemeContext.Provider value={{ colorMode, toggleColorMode }}>
		<ThemeProvider theme={theme}>{children}</ThemeProvider>
	</ThemeContext.Provider>
);

};
export const useCustomThemeContext = (): ThemeContextType => {
const context = useContext(ThemeContext);
if (!context) {
throw new Error("useCustomTheme must be used within a CustomThemeProvider");
}
return context;
};
`
And no color-scheme related styles on any CSS file.


Documentation

I can't figure out how to use this library, could you add some documentation ?
Thanks

👍

Yes agreed, let's not commit without documentation.

Have you asked on Stack Overflow?

i think it should be a doxygen for it


PEP8 and other minor fixes

Fixes #4

@rarewin ,
I reverted the class name changes to lowercase, hopefully that fixes the issue!

This works completely!
Thank you!

@rarewin ,
No problem, thanks for your time!


"Diagnosis" should be a mandatory field

Describe the Bug

Steps to Reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected Behavior

Actual Behavior

Additional Information

Traceback

(just for demo purposes later)


Check that our implementation matches a real llama implementation

We need to validate that our llama implementation doesn't have bugs in it. The reasonable way to do this is to compare its outputs on a set of inputs to that of the HF llama implementation.
Note that we shouldn't expect an exact match; our rotary implementation differs from that of the rotary setup used in the HF implementation. Hopefully they are somewhat close though. May need to adjust rotary hyperparams.
If these don't match, it may be worth implementing the more complex setup they have in HF (or just training with the HF model directly).
Note that this PR will involve sorting out the from_pretrained method to work for llama (rather than the copied over gpt2 code that is currently in there).

Also note that llm.c repo has a train_llama3.py script now! It might be helpful to compare implementations with this (though I'm unsure if they have a test to compare against huggingface).


Make modal isHidden as a function to return the current modal element state.

This patch fix https://github.com/themesberg/flowbite/issues/119 by setting the isHidden state based on the current modal element state, without this we always assume that the model is hidden every time we create a new instance.

Hmm this will not fix properly the issue, we set isHidden in a new instance and the old reference does not set the isHidden failing on subsequents calls because isHidden is all messed up now.

Making the isHidden as a function we can always check the actual value of the element to decide its property instead of relying on the instance.

Hey @marciotoshio,
Thanks for contributing, I'll check this out today!

@zoltanszogyenyi
Did you check this yet?

Hey @yaqshank92,
Please check my latest comment here: https://github.com/themesberg/flowbite/issues/119
We have the v1.6.0 branch with some new updates, can you please test that out? Thanks!

We have the isHidden() method on the Modal.


Bump version to 0.9.2

Codecov Report

Merging #35 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #35   +/-   ##
=======================================
  Coverage   64.25%   64.25%
=======================================
  Files          25       25
  Lines         649      649
  Branches       12       12
=======================================
  Hits          417      417
  Misses        232      232

Impacted Files
Coverage Δ

Tests/SDKTests.swift
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


seanaye/enhancement/OakSupport

This PR aims to add support for the Oak framework NativeRequest type.
It also runs the first party deno code formatter deno fmt
closes #1
EDIT: The types are not yet correct, DO NOT MERGE

regarding deno fmt... I use StandardJS style in all my Deno projects... could you please revert running deno fmt?

there's a conflict in files...


RoboVM compiler version is tied with plugin

Hi,
Looking through the project it seems as though the robovm compiler is tied to the plugin. Is there any reason for this behavior i.e. RoboVM breaks each minor version change?
If not, it would be great to allow users to be able to change the robovm compiler version downstream.

Yes, the reason for plugin-RoboVM version synchronization is that the RoboVM API (= compiler) sometimes changes and attempting to separate it would be very messy and less stable (we would have to test each minor change to all supported RoboVM versions, which would be time consuming and error prone). Is there any particular reason why you would want it?

I am more worried about bugfixes appearing in the newer versions and not being able to take them, even if the client api is the same (though reading through the code it looks as though we can change the library version).
It seems strange that the api used by the client libraries and the compiler are tied.

If you need newer RoboVM, you can compile and publish it yourself locally before we get to publishing it officially, there is a version1.7 branch for RoboVM 1.7 and I am working on 1.8 at the moment. Just follow the "Hacking on plugin" section in README. If you want newer plugin than RoboVM, you will probably have to backport manually.
I don't know if mixing compiler and RoboVM runtime versions is a wise idea, RoboVM evolves quickly and all sorts of nasty bugs can come out of that.
Anyway, do you have any specific concern/need? Untying plugin version from RoboVM version probably won't happen anytime soon, maybe later when RoboVM stabilizes and only if it makes sense for the users (and us).

No we don't have any particular need. The only bugs I can think of being introduced is if the AppCompiler XML/API was significantly different as the robovm bootstrap gets added by the compiler anyway (so it will still be 'compiled' with the same version as the API which you code to).
We've started a fork wip which can do this since I'm also trying to integrate proguard into in properly and nicely with the android plugin we're using heavily.

Adding proguard support should be straightforward, that is what the robovmInputJars key is for. Although since RoboVM is already optimizing and can be configured to minimize the code as well, the returns are not as big as on android. (That is why it is not included by default)

Yes I've seen the treeshaker settings. I'm adding it more as tree shaker is disabled on 32 bit machines and the compiler seems to be ridiculously slow on our osx machine.
At any rate, I think this issue  can be closed for now.

I don't know about tree shaker not working in 32bit builds, source? I use it without problems to build 32bit apps.

Not 32 bit builds, on 32 bit machines. We get an warning message when we run the robovm compiler.

Oh, sorry, missed that. That seems like a RoboVM problem. However, it does explain why are your builds slow, Apple has not been making 32bit machines for quite some time.


Check for firmware update during start

Could it be possible to have a script running at the very start at starting the container up, checking for firmware, and pick the latest? A config file in the data folder could be used to select stable/beta if wanted.

What do you want the script to do with the firmware file, given that it downloads a newer one that is currently flashed?

I'm thinking something along the lines that could be decided with a variable.
0 - Download if newer firmware is found and update on next start.
1 - Download but don't do anything with the file.
2 - Check if file is downloaded and update. Shut the container down afterwards (or if possible revert variable back to 1).
I'm not certain that above would be possible, but it sure would be a nice feature.

I think this causes more issues than it solves them tbh.

I mean, anything would be better than the current state with updating a firmware in Docker.
The default state, if nothing else is set, would be 1, meaning it would behave much like today.

You mean in the form of a opt-in . That would be okay, but it could cause issues. Docker on a VM for example would probably either brick the stick or doesn't work at all. Users that are not that familiar with docker/vm etc would break their own stuff.
Either way, i'm not to decide here 😅

We have working update instructions here: https://github.com/marthoc/docker-deconz#updating-conbeeraspbee-firmware
Trying to implement some kind of auto flash feature is definitely out of scope for this project, and will just add complexity for very little gain.

We have working update instructions here: https://github.com/marthoc/docker-deconz#updating-conbeeraspbee-firmware
Trying to implement some kind of auto flash feature is definitely out of scope for this project, and will just add complexity for very little gain.

That's a shame. I'm hoping that a more user friendly approach can be developed down the line.

The app is already checking if the firmware is up to date. But I don't know where it seeks for the newest version ...
So users could be informed by reading the log or looking at the web-page of their running instance.
I wouldn't recommend auto-updates as this process doesn't run flawless from inside the docker container. So just image powerloss, reboot, autoupdate and the result of an unusable stick!
On the other hand - if you know about an update which may be auto downloaded and you manually start the update process why shouldn't the firmware download happen now. Early download doesn't help that much and it would have to dl every new version for every type of device ...

Phoscon is already searching and knows when it's time to update. It's just that the container isn't handling that at all.
This causes issues for those running Docker in a non standard environment, like HASS and Synology Docker.
I mean:

Update in Docker
If you are using marthoc's deCONZ Docker image the steps in this guide won't work.
Please refer to the following guide, which describes how to update the firmware inside Docker.
https://github.com/marthoc/docker-deconz#updating-conbeeraspbee-firmware
This method cannot be used for the Home-Assistant add-on and no current workaround is known. This also includes the button >in Phoscon within the addon.

Can this really not get automated enough to fix the above? I refuse to believe that this is wanted behavior.
The GCFFlasher is going to throw an error and not update if something is wrong anyhow, so why not take advantage of that?


Missing BL702 HBN XCLK initialization in SDK v2.0

Hello,
Newest SDK 2.0 lacks HBN_Set_XCLK_CLK_Sel(...) calls to initialize HBN high-speed clock for BL702. Bluetooth LE and other wireless interfaces couldn't perform properly without such initialization, because they should use very stable XTAL 32M clock.
Older bl_mcu_sdk V1.4.5 has such calls, current bl_iot_sdk version has such calls too.
This initialization should be added to the BSP's system_clock_init(void) function in bsp/board/bl702dk/board.c, so system_clock_init(void) should look like:
static void system_clock_init(void)
{
    GLB_Set_System_CLK(GLB_DLL_XTAL_32M, GLB_SYS_CLK_DLL144M);
    GLB_Set_MTimer_CLK(1, GLB_MTIMER_CLK_BCLK, 71);
    HBN_Set_XCLK_CLK_Sel(HBN_XCLK_CLK_XTAL);
}

Right, wireless need external 32M xtal, but currently wireless does not support for bl702.

Thanks, you can submit pr to modify this.

Done. Created https://github.com/bouffalolab/bouffalo_sdk/pull/149


Only link with blas when needed

Based on the included headers, pythran now automatically removes the blas dependency.
Also do some cleanups (removing debug lines, some formatting, fix imatmul headers).
Fix #2203

@martibosch : this one is finally green. It should remove the dep on openblas on your project :-)

unluckily I got the same error both locally and in github actions :(

sorry, I made a mistake in the requirement syntax. After fixing, everything is working: https://github.com/martibosch/pylandstats/actions/runs/9077046472
should I release now with the git-branch requirement in pyproject.toml, or should i wait (e.g., maybe you remove feature branches or you plan a tagged release very soon).
Thank you again!

On Tue, May 14, 2024 at 03:02:43AM -0700, Martí Bosch wrote:

sorry, I made a mistake in the requirement syntax. After fixing, everything is
working: [1]https://github.com/martibosch/pylandstats/actions/runs/9077046472
should I release now with the git-branch requirement in pyproject.toml, or
should i wait (e.g., maybe you remove feature branches or you plan a tagged
release very soon).

Great! Release incoming this week or the week after :-)


Time and calendar improvements

Pull Request Checklist:

[x] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes #1213, fixes #1190, fixes #1111

[x] Tests for the changes have been added (for bug fixes / features)

[x] (If applicable) Documentation has been added / updated (for bug fixes / features)

[x] HISTORY.rst has been updated (with summary of main changes)

[ ] Link to issue (:issue:number) and pull request (:pull:number) has been added

What kind of change does this PR introduce?

Cleaner xclim.core.calendar.parse_offset : fails on invalid frequencies, return implicit anchors (YS -> JAN) and implicit is_start_anchored (D -> True)
xclim.core.calendar.common_calendar to find the best calendar to use when uniformizing an heteroclite collection of data.
xclim.ensembles.create_ensemble now accepts calendar=None, and uses the above function to guess the best one. It also now accepts cal_kwargs to fine tune the calendar conversion.
New data check : xclim.core.datachecks.check_common_time that ensures all inputs of multivariate indicators have the same frequency (and the same time anchoring for daily and hourly data).

Does this PR introduce a breaking change?
parse_offset has changed. The results are better and more consistent, but could break previous uses.
construct_offset(*parse_offset(freq)) will fail in more cases than before because we now return implicit anchors.
Other information
If your time is limited I suggest the following review dispatch:
@huard  : datachecks.check_common_time
@tlogan2000  : ensembles.create_ensemble
@Zeitsperre : calendar.parse_offset.

Coverage increased (+0.03%) to 92.215% when pulling 6d2b0b142d252b382e002c03a541b1f607b6236a on time-calendar-improvements into 51d1b959ea076ac816257a6423f8fb34fa6a3b03 on master.


Merge PRs for biomentric authentication in identity-api-user

Description:
Merge the pull requests that are related to biometric authentication found in the identity-api-user repo
Pull Requests to be Merged
https://github.com/wso2/identity-api-user/pull/91
https://github.com/wso2/identity-api-user/pull/92
https://github.com/wso2/identity-api-user/pull/93
https://github.com/wso2/identity-api-user/pull/94
https://github.com/wso2/identity-api-user/pull/97
https://github.com/wso2/identity-api-user/pull/98
https://github.com/wso2/identity-api-user/pull/99

Closing because this issue is moved to #23


NO-ISSUE: Improved localization for Stunner BPMN Editor

added localization for process type
added localization for table header in metadata editor widget
added localization for toggleErrorsAnchor in correlations editor widget

@handreyrc can you please take a look at this?


Template std.typetuple.NoDuplicates removes const types for classes and structs

goldmax3000 (@GoldMax) reported this on 2013-11-21T19:52:13Z
Transfered from https://issues.dlang.org/show_bug.cgi?id=11577
CC List

alex.jercaianu
bugzilla (@WalterBright)
schveiguy (@schveiguy)

Description
// OK
static assert(is(NoDuplicates!(int, const(int)) == TypeTuple!(int, const(int))));
// Error - result is (DateTime)
static assert(is(NoDuplicates!(DateTime, const(DateTime)) == TypeTuple!(DateTime, const(DateTime))));
// Error - result is (Object)
static assert(is(NoDuplicates!(Object, const(Object)) == TypeTuple!(Object, const(Object))));

schveiguy (@schveiguy) commented on 2020-07-10T13:42:26Z
This is related to issue 20863

If that issue is fixed, this one gets fixed as well. But of course, one could probabl fix this without fixing 20863. So I won't close this as a duplicate.

bugzilla (@WalterBright) commented on 2019-12-11T07:42:20Z
Meanwhile all three of them fail.

alex.jercaianu commented on 2017-10-10T10:54:10Z
What would be the correct behaviour here?
Should it treat the const and nonconst as duplicates?


ssh ignores current users .ssh folder

To keep track of multiple accounts a custom ssh configuration is uesd with
sample
Host github.com
	HostName github.com
	User git
	IdentityFile ~/.ssh/id_ed25519_normal

Host github-special.com
	HostName github.com
	User git
	IdentityFile ~/.ssh/id_ed25519_special

pull-request-github complaints about connection git@github-special.com;user/repo.git

Can you give an example of the complaint?

Login not possible

I don't see the error "Login not possible" anywhere in this extension code base or microsoft/vscode. Can you share a screenshot?

the complete text:
Fetching pull requests for remote 'origin' failed, please check if the url git@github-theking2.com:theking2/dwh_php7.git is valid.
Integrated source control has no problem.
git remote --verbose
dwh-php7        https://github.com/theking2/dwh_php7.git (fetch)
dwh-php7        https://github.com/theking2/dwh_php7.git (push)
origin  git@github-theking2.com:theking2/dwh_php7.git (fetch)
origin  git@github-theking2.com:theking2/dwh_php7.git (push)

config in (-join($Env:USERPROFILE)) /.ssh
theking2 account git@github-theking2.com:theking2/repo-name
Host github-theking2.com
        HostName github.com
        User git
        IdentityFile ~/.ssh/id_ed25519

I'm not sure this is the exact same issue, but may be in a similar vein...
I have multiple GitHub accounts I use (Personal & Work). When logged in to the extension with my personal GH account and try to access a work repo I get the error: Fetching pull requests for remote 'origin' failed, please check if the url<EMAIL_ADDRESS>is valid.
Is there a way to login to GitHub PR Extension with more than one GitHub account? Or configure it to accept different credentials for different repos?

@DirtySoc it is possible to work with mulitple github accounts exactly in the way I described. If I clone from my 'normal' account I use:
git clone git@github.com:user1/proj1.git
if I clone from my special account I use:
git@github-special.com:user2/proj2.git
This works in Source Controlin vscode as:
git remote --verbose
origin  git@github-special.com:user2/proj2.git (fetch)
origin  git@github-special.com:user2/proj2.git (push)

Unfortunately Pull Requests ignores the settins in .ssh/config and always uses a fixed github.com (git@github.com:user2/proj2.git).

I also have the same issue, I use multiple accounts one personal and another one for work, I clone using my personal. account by adding -personal to git@github.com:xxxx/xxxx.git and it becomes git@github-personal.com:xxxx/xxxx.git.
apparently the extension doesn't support that and as a result I get the same error message
Fetching pull requests for remote 'origin' failed, please check if the url git@github-personal.com:xxxx/xxxxx.git is valid.

please have a look at this.


Automate the testing of code and the generation of output

This is a stretch project for 2.2.

[ ] Automate the testing of code samples (driver/ORM and SQL)

This would help us catch any breakage between our samples and our product.
This may require storing all code in includes or even in a separate repository. See https://github.com/cockroachdb/docs/issues/3203 for more context.
For SQL, an approach would be to a consistent database for all examples. See https://github.com/cockroachdb/docs/issues/2849.
For testing ideas, see https://github.com/cockroachdb/docs/issues/182.

[ ] Automate the generator of SQL output

When the response format changes (rare), a large number of code blocks must be updated. This is not sustainable.
This may require code blocks with SQL output to be stored as includes.

Closing in favor of discrete issues: https://github.com/cockroachdb/docs/issues/7066, https://github.com/cockroachdb/docs/issues/7067, https://github.com/cockroachdb/docs/issues/7068.


Clarify the positions of vendor_id and product_id

An existing example uses same value, 0x1a2b  in both Vendor id and Product id fields, which can confuse a new user.
Contributor checklist

[x] I have read the CONTRIBUTING.rst
[x] I have tested my contribution on these devices: Citizen CT-S2000
[x] My contribution is ready to be merged as is

Description

Thank you very much for the contribution! (And sorry for the long delay in answering...)


Max surge value

Under the heading, "Customize node surge upgrade", located here I do not understand the last sentence of the 3rd paragraph.

If the max surge value is lower than the current node count at the time of upgrade, the current node count is used for the max surge value.

Based on my interpretation, should lower be replaced with higher?

If the max surge value is higher than the current node count at the time of upgrade, the current node count is used for the max surge value.

Thank you.

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

ID: 7010bd58-42b1-5c90-3253-05deed855be8
Version Independent ID: c890efb2-cdaf-a3eb-d54f-0e7ccbd4314d
Content: Upgrade an Azure Kubernetes Service (AKS) cluster - Azure Kubernetes Service
Content Source: articles/aks/upgrade-cluster.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

@mattlunzer Thanks for the feedback. We will review and update as appropriate.

This issue has been addressed. Thank you for your feedback!.
#please-close

Not sure why this didn't auto close.
#please-close


_User ACL not working correctly

Issue Description
Updates to _User record do not adhere to the ACL correctly. If a moderator is editing another _User record (i.e not their own data). With the correct ACL's in place, the server always denies permission due to this line
if (this.className === '_User' &&
      this.query &&
      !this.auth.couldUpdateUserId(this.query.objectId)) {
    throw new Parse.Error(Parse.Error.SESSION_MISSING, `Cannot modify user ${this.query.objectId}.`);
  }

As you can see the function will only return true if we're using the master key or the object is the currently logged in user.
// Whether this auth could possibly modify the given user id.
// It still could be forbidden via ACLs even if this returns true.
Auth.prototype.couldUpdateUserId = function(userId) {
  if (this.isMaster) {
    return true;
  }
  if (this.user && this.user.id === userId) {
    return true;
  }
  return false;
};

The comment implies that the ACL can still override, but this is not the case.
Steps to reproduce

Correctly assign ACLs to the user record so that the currently authenticated user should be able to edit the record.

Edit the _User record

Expected Results
A successful outcome.
Actual Outcome
{"code":206,"message":"Cannot modify user IyYUu90HdL.","level":"error","timestamp":"2017-03-01T17:41:56.373Z"}

Environment Setup

Server

parse-server version (Be specific! Don't say 'latest'.) : 2.3.6
Operating System:    OSX 10.12.1
Hardware:             MBP-2015
Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): localhost

Database

MongoDB version: 3.2.11
Storage engine:  MMAPv1
Hardware:       ??
Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): mLab

Logs/Trace
Include all relevant logs. You can turn on additional logging by configuring VERBOSE=1 in your environment.

We don't allow users to modify other user's ACL for security reasons.

Then what's the point of ACL's? Without editing users, you're limiting Parse's functionality as it can't be used for anything user management related, you can't design a system that has moderators or administrators without splitting all user content into another table. Which for already established applications is upsetting. We've unfortunately had to use the master key which arguable is now worse for security reasons as anyone with access to the page can now update the user - instead of the ACLs which was the purpose of them to begin with.

I believe this restriction was set in parse-server as it was there on parse.com

Are you sure? - I continued to use the parse hosted solution up until January (as I couldn't find the time to transfer it sooner). And my Administrator ACL was able to update users.

I believe

it doesn't mean I'm sure.

@awsgeorge you could use a cloud function Parse.Cloud.define('someFunction',... to achieve this. In that function you can first check for role and then use the master key.
Also are you now using the master key in a publicly facing webpage? That would be a huge security issue.

@johanarnor Yes - it was a quick work around, naturally the page in question requires elevated privileges, but I would prefer not to use the master key, as it seems like a hack to reinstate it's original functionality.

Ok, but how is a user authenticated to reach that page? Is the page a part of a single page application that anyone can access from public internet?

No - It's using the PHP SDK.

The same issue. I have to perform access control checkings myself using Parse Cloud functions.
It'd be great if ACL works for _User objects as for other objects

+1
I would expect the User class to adhere to the same ACLs as everything else. I can understand setting the default ACLs for the User class differently for security reasons, but if I explicitly set the ACL of a user to a role ("Admin" read/write), I would expect that a logged in Admin can read and write that User.

+1 The User class should adhere to the same ACLs as any other class. Otherwise, user management at an elevated role is impossible without using a hack/workaround.

I'll work on the enhancement while maintaining a good amount of security:

calls will folllow the ACL
public write will always be rejected
self locking out will be prevented
locking out from other source will be approved if following ACL

Any news on this ?

Not yet, haven't had a chance to make a dent. But in the meantime, anyone can take it on, what's expected is detailed enough

Anyway, I'll use a Cloud function.

Right - taking a stab. Can you point me to the ACL checking code? I removed the basic checks thinking it would fall back to normal ACL checking, but it didn't, contrary to this comment: // It still could be forbidden via ACLs even if this returns true.

It looks like the the ACL is translated to a native database ACL, so presumably there is no checking, and we let the database handle the permissions? I need a simple way to compare the current user ACL with the object ACL for the sensitive fields - IE. the database returns the data, but we're deleting email, in this scenario, the code must check and validate the ACL, so we can keep these fields in tact - am I right in thinking the only way to do this is to perform another query? I can see that we can get the roles of the current user auth.getUserRoles(), but there is no clear way to check whether these roles coincide with the objects ACL.

@flovilmart Is this already implemented? Or do i need to use Cloud functions?

@opit7 on the latest parse-server users can be locked out when using a masterKey but the rest of the implementation hasn't been implemented yet.

@flovilmart may you by chance still have the rest of the implementation on the road map for the nearer future?

I haven't had the chance to implement it, and at the time being, there is debate as for the security implication of changing this model. While I hear the ones from the camp saying Users should follow ACL's, I'm not sure changing it now is a great idea. Anyhow, this is still pending a good solution, that takes into account the maintainer concerns and the need of the community.
In the meantime, there are plenty of possible alternatives, including using a cloud function to lock out users with the masterKey.

@flovilmart The main use was for a moderation helper app. I did implement alternatives now, however it added more complexity which i am not sure that was needed, but i can be totally wrong here as i do not have much information about the security implications it may have.

#4789

#4789

#4789

#4789

#4789

Related issue #4789

@awgeorge finally it's in! Users will follow ACL's while being extra secure!


Show information?

Would be great if we could toggle some information display regarding the current position, like Page 3 of 20 or 7%

Hey there, we already could... It's just that I implement it in https://github.com/wustho/epy since I don't really want to mess with epr that already stable... And it's progress percentage 7% instead of page 3 of 20 for more minimalist approach...

Super, thanks!


Reload ROM if it is open in LM and was just rebuilt by Lunar Helper

This would be really nice, because it's easy to forget to reload a ROM that you already have open and if you do forget, you could potentially overwrite previous changes, which sucks.
There's already functionality in LM's user toolbar stuff to allow for making LM refresh, but sadly I can't really use it in Lunar Monitor, because the injector gets the relevant information, not Lunar Monitor itself, and I can't really pass it along sadly.
I could however probably relatively easily use the same general mechanism to refresh, I'd just have to obtain the relevant window/function handle from LM internally instead, which may or may not be hard.

This was added in v1.1.0


Prevent stealing focus back when clicking an outside control

Closes #60
An example of this would just be two of our comboboxes next to each other with "OpenDropDownListAlsoWhenNotInEditMode" set to true.  Click the first opening the dropdown then click the second.   The second dropdown will open temporarily but then close as the first steals back control on dropdown closing.
I was unable to figure out a better way to do this.   The dropdown is destroyed before virtually all other indicators would work.  I looked at:

HasEffectiveKeyboardFocus
IsKeyboardFocusWithin
IsFocused
MultiSelectComboBoxHasFocus
While the closing of the dropdown is caused by OnPreviewMouseDownOutside it also actually starts closing after that function finishes so we can't just set a variable while it is open.  We could use a simple bool to ignore just the next close focus request, however if the close isn't triggered for some reason then didn't want it to randomly cancel the next one.  This ensures only the next close request is ignored, and only if it happens within OnPreviewMouseDownOutside starting a seemingly valid dropdown close call.

This also fixes the 'bug' where if you click off the combobox while the dropdown is open you have to click again to get out of edit mode.

Thank you very much for submitting this PR. While the fix may work, we've eventually decided not to add this code in our main repo for now, being too risky, in our opinion. Anyone interested can still fork/adapt their code as needed.


bugfix: 单据处理人问题顺序问题修复

Codecov Report

Merging #731 (601c052) into v2.6.x_develop (1df8aac) will increase coverage by 0.00%.
The diff coverage is 37.50%.

@@               Coverage Diff               @@
##           v2.6.x_develop     #731   +/-   ##
===============================================
  Coverage           61.83%   61.84%
===============================================
  Files                 445      445
  Lines               28218    28218
===============================================
+ Hits                17450    17452    +2
+ Misses              10768    10766    -2

Impacted Files
Coverage Δ

itsm/ticket/models/ticket.py
55.57% <37.50%> (+0.09%)
:arrow_up:

Continue to review full report at Codecov.

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


[QUESTION] Custom reference.conf

Hi. I like the plugin and want to use it in my project, however I need to reconfigure the rules.
I have found out that it's difficult to configure a few rules in pom.xml, for ex. "M010" from zally ruleset.
Is there a possibility to set a link to custom reference.conf?
This file is like a centralised place for almost all rules (both zalando and zally) and I think it may be convenient to configure rules through it.

For now I'm using the following config, but it looks awkward 😄
<ruleConfigs>
    <CaseChecker>
        {
            cases: {
                camelCase: "[a-z][a-z0-9]*(?:[A-Z0-9]+[a-z0-9]*)*",
                PascalCase: "[A-Z]+[a-z0-9]*(?:[A-Z0-9]+[a-z0-9]*)*",
                snake_case: "[a-z][a-z0-9]*(?:_[a-z0-9]+)*",
                SCREAMING_SNAKE_CASE: "[A-Z][A-Z0-9]*(?:_[A-Z0-9]+)*",
                "kebab-case": "[a-z][a-z0-9]*(?:-[a-z0-9]+)*",
                "COBOL-CASE": "[A-Z][A-Z0-9]*(?:-[A-Z0-9]+)*",
                "hyphenated-Camel-Case": "[a-z][a-z0-9]*(?:-[A-Z0-9]+[a-z0-9]*)*",
                "Hyphenated-Pascal-Case": "[A-Z]+[a-z0-9]*(?:-[A-Z0-9]+[a-z0-9]*)*",
                "Title Case": "([A-Z][^\\s]*\\s?)+"
            },
            pathSegments: {
                allow: [
                    "[a-z][a-z0-9]*(?:-[a-z0-9]+)*"
                ]
            },
            propertyNames: {
                allow: [
                    "[a-z][a-z0-9]*(?:[A-Z0-9]+[a-z0-9]*)*"
                ]
            },
            pathParameterNames: {
                allow: [
                    "[a-z][a-z0-9]*(?:-[a-z0-9]+)*",
                    "[a-z][a-z0-9]*(?:_[a-z0-9]+)*"
                ]
            },
            queryParameterNames: {
                allow: [
                    "[a-z][a-z0-9]*(?:_[a-z0-9]+)*"
                ]
            },
            headerNames: {
                allow: [
                    "[A-Z]+[a-z0-9]*(?:-[A-Z0-9]+[a-z0-9]*)*"
                ]
            },
            tagNames: {
                allow: [
                    "([A-Z][^\\s]*\\s?)+"
                ]
            },
            discriminatorValues: {
                allow: [
                    "[a-z][a-z0-9]*(?:_[a-z0-9]+)*"
                ]
            },
            enumValues: {
                allow: [
                    "[a-z][a-z0-9]*(?:_[a-z0-9]+)*"
                ]
            }
        }
    </CaseChecker>
</ruleConfigs>

Hi @ethlo . I've created a pull request that adds possibility to set link to a custom config file for rules like this one:
https://github.com/zalando/zally/blob/main/server/zally-ruleset-zalando/src/main/resources/reference.conf
Rule configs are evaluated in the following order:

Rule configurations defined in ruleConfig
Rules configurations defined  in file rulesConfigLocation
Default rules configurations taken from classpath (eg. reference.conf in Zalando library)

Thanks for the effort! PR merged 👍🏻


Fix ESLint not working on VSCode #1128

@juliusmarminge Good call out. I am on v20.15.1 but looks like ESLint plugin in VSCode is using v20.9.0. Wonder how the ESLint plugin is pulling the node to use

@juliusmarminge
As i noted here: https://github.com/t3-oss/create-t3-turbo/issues/1128
VSCode ESLint is kinda finicky in that it doesn't have a good way to set the node version (like matching the proj environment node config)
This suggested change might be good to be compatible with older versions of Node? Otherwise it just becomes a silent failure until you notice it


View the planets

Currently I get a stack smashing error if I try to run :lua require'telescope.builtin'.planets(), but I'm not sure why. If you remove mars (or I presume any planet) it makes the issue less frequent, but it still occurs from time to time (and I think it happens less if at all with only a one or two planets).

Save planets as files under Memes directory.

Then just cat those files. You can search the files the normal way.

@smolck I pushed an example of how you can do this without shelling out to ls every time. I think it needs some fixing, cause cat doesn't seem to work for me every time... i don't know why.

@tjdevries Thank you, your solution is an instructive one (I didn’t even know require('plenary.debug_utils').sourced_filepath() existed).

cause cat doesn't seem to work for me every time... i don't know why.

Would you mind elaborating?

Sometimes I just get "Process exited 0" (like cat has completed).
I'm not sure why that is.

@smolck do you want me to do the rebase and merge this? I think if you use the cat previewer and stuff now this might work.
If not, we can merge and I'l ltry and find a way to get cat to show correctly (perhaps just with a job or something dumb).


Which code base is recommended?

Is Master stable or should we use v0.6 release from July 2015?
BTW, why hasn't new releases been created since then?  Is this project still active?

Yes this project is still active, just look at last commits on the master branch : https://github.com/thotro/arduino-dw1000/commits/master
However I don't know why a new release has not been created since last summer. I can't find any written milestones for next releases. But I personnally use the master branch since quite recent commits have fixed some of my issues.


Just a question

i was just wondering if there is any tools that can make this so when the victim downloads this, the anti virus doesn't go off right away until they open it and its too late. I have made a program to bind this stub to and if you have any programs or tips that can make it undetectable until they open it that would be freaking awesome

I thought about it a while ago and this is what in my mind.
I thought of aes encrypting the grabber (which makes it fully undetectable) and then make a c++ script to decrypt it and run it on the victim's pc. But the problem is that, most of the people do not have any c++ compiler in their pc. and all the c++ compilers are too big. So I passed it

could i potentially get away with it? remember I made a program and I could make them download a c++ compiler as a "requirement" for the app. Same thing with the file size, I could just pass it off as part of my program.

The antivirus will block the app in the middle of downloads

There is no way that the grabber can become FUD. Even if it does, it will now or soon be flagged by antiviruses.
I have updated the code to convert the grabber to a .Net exe to reduce virustotal detections.

is there anyway that i could obfuscate it to make it at least be able to execute before it gets picked up and deleted?

Probably. Not that I know of...


[#112338109] ContentLoader accepts yes_no_question type questions

Supplier responses to briefs are going to be returning a new data type to the ContentLoader.
I've called them yes_no_questions in the manifest files -- essentially they're lists of boolean values.
I've put them directly after list questions in our test because it seemed appropriate.
Then I reindexed all of the following questions, which makes the diff harder to look at.
(Sorry about that.)
>> Story on Pivotal

Looks fine :+1:

Looks good - :+1:
Let's suck-it-and see once we start building out the frontend :)


add xpad-noone and enable xone

The xone driver disables too many other controllers by disabling the stock xpad driver in the kernel ... to properly use it, we also need to include xpad-noone .
Goals of this ticket:

get xpad-noone building as akmod
add xpad-noone to this repo/image
re-enable xone

See: https://github.com/ublue-os/akmods/issues/25 and https://github.com/ublue-os/main/issues/256 for context.

Note that negativo17 has a spec file for xpad-noone but does NOT yet seem to be including it in their repos: https://github.com/negativo17/xpad-noone-kmod

As it stands today, this would require building xpad-noone RPMs from spec (possibly imported from negativo17 to our own repo for maintenance), building probably done in COPR (or whatever we choose ublue-os specific RPM repo).
All that is pre-requisite for then building the akmod in this akmods project.
Probably, if building xpad-noone we should build/host xone as well. And... that leads to building xpadneo too...

https://github.com/ublue-os/akmods/commit/205d07f6f2e01b955eeeb6f19593668eb67d3edc

@KyleGospo has completed 2 PRs:

https://github.com/ublue-os/akmods/pull/56
https://github.com/ublue-os/main/pull/314

This allowed me to successfully test:

wired xbox 360 works on plug-in (new xpad-noone driver)
wired xbox one works on plug-in (with xone driver)
wireless dongle xbox one works after pairing (xone driver)
bluetooth xbox one still works (with xpadneo driver)

Calling this done!


Fix a typo in travis config.

Fix a typo in the target name for the config of mipsel-unknown-linux-gnu. Build will probably still fail though, but will hopefully get further :wink:
Thanks!

Yep, will probably still fail, but looks good.  @homu r+

:pushpin: Commit f73c8b1 has been approved by posborne

:zap: Test exempted - status


Correct WATF grammar

Example:
  (func (
    (call 1)
  ))

Should be
  (func
    (call 1)
  )

WAST definition:
func:    ( func <name>? <func_sig> <local>* <instr>* )
instr:
  <expr>
  <op>                                                              ;; = (<op>)
  block <name>? <block_sig> <instr>* end <name>?                    ;; = (block <name>? <block_sig> <instr>*)
  loop <name>? <block_sig> <instr>* end <name>?                     ;; = (loop <name>? <block_sig> <instr>*)
  if <name>? <block_sig> <instr>* end <name>?                       ;; = (if <name>? <block_sig> (then <instr>*))
  if <name>? <block_sig> <instr>* else <name>? <instr>* end <name>? ;; = (if <name>? <block_sig> (then <instr>*) (else <instr>*))

op:
  unreachable
  nop
  br <var>
...

And WATF definitions is here

Do I understand this correctly: The syntax with extra parentheses is not allowed in WAST and WATF, but our grammar currently allows it?
(func (
  (call 1)
))

Our grammar ensures it and that's wrong. I'll post a few examples in a moment.

Clean WAST from WebAssembly explorator
(module
  (type $type0 (func (result i32)))
  (table 0 anyfunc)
  (memory 1)
  (export "memory" memory)
  (export "main" $func0)
  (func $func0 (result i32)
    i32.const 0
    i32.load offset=4
    i32.const 16
    i32.sub
    i32.const 0
    i32.store offset=12
    i32.const 1
  )
)

Instructions are not surrounded by parens and we can split them by line (currently already done-ish).
One liner
From the spec tests (so WAST).
(func (export "type-i64") (result i32) (unreachable))

WAST
(func $f)
(func)
(func (export "type-f64-value") (result f64)
  (block (result f64) (f64.neg (br_table 0 0 (f64.const 4) (i32.const 0))))
)

This is the case for every block instructions: if, loop, block, ...

This will be my next focus because that will allow us to use the spec tests: https://github.com/WebAssembly/spec/tree/master/test/core

Okay then I'll focus on supporting all number literals as in #32 and #46 to support the numeric test cases.


token: support for a custom refresh func

This PR adds support for specifying a custom refresh function which allows users defining manual refresh tokens to refresh the token via a callback
Fixes https://github.com/hashicorp/go-azure-helpers/issues/22

@jhendrixMSFT thanks for pushing a fix for this - LGTM 👍


Cannot install VS Code extensions using Microsoft.VSCode.Dsc

Brief description of your issue
Set() indicates it was successful, but the extensions weren't installed. It only seems to be an issue for installing extensions, as removing them using Exist=$false works.  However, even explicitly setting Exist=$true doesn't affect the behavior
Steps to reproduce
Use the configuration file from #117 or run the commands manually -
PS C:\Users\Trenly> Invoke-DscResource -Name VSCodeExtension -ModuleName Microsoft.VSCode.Dsc -Method Get -Property @{Name='redhat.vscode-yaml'}

Name               Version Exist Insiders
----               ------- ----- --------
redhat.vscode-yaml 1.15.0   True    False

PS C:\Users\Trenly> Invoke-DscResource -Name VSCodeExtension -ModuleName Microsoft.VSCode.Dsc -Method Test -Property @{Name='redhat.vscode-yaml'}

InDesiredState
--------------
          True

PS C:\Users\Trenly> Invoke-DscResource -Name VSCodeExtension -ModuleName Microsoft.VSCode.Dsc -Method Get -Property @{Name='EditorConfig.EditorConfig'}

Name                      Version Exist Insiders
----                      ------- ----- --------
EditorConfig.EditorConfig         False    False

PS C:\Users\Trenly> Invoke-DscResource -Name VSCodeExtension -ModuleName Microsoft.VSCode.Dsc -Method test -Property @{Name='EditorConfig.EditorConfig'}

InDesiredState
--------------
         False

PS C:\Users\Trenly> Invoke-DscResource -Name VSCodeExtension -ModuleName Microsoft.VSCode.Dsc -Method set -Property @{Name='EditorConfig.EditorConfig'}

RebootRequired
--------------
         False

PS C:\Users\Trenly> Invoke-DscResource -Name VSCodeExtension -ModuleName Microsoft.VSCode.Dsc -Method test -Property @{Name='EditorConfig.EditorConfig'}

InDesiredState
--------------
         False

Expected behavior
Extensions to be installed
Actual behavior
No Extensions :(
Environment
Running DSC resource directly

[Policy] Issue Bug
[Policy] Microsoft.VSCode.Dsc

If you want @Trenly , I can take a look into this?

Please do

I have both Insiders and Stable installed with user installation. I have tested it from my side, but both are working ...

The issue is these lines here:
https://github.com/microsoft/winget-dsc/blob/73eabd2c55cb157d30f2420541c3bd7a6e8d68fa/resources/Microsoft.VSCode.Dsc/Microsoft.VSCode.Dsc.psm1#L98-L102
When an install fails, it may just returns a non-zero exit code instead of throwing an exception. This is what happened on my machine -
Debugging Log

Setting 'VSCodeCLIPath' to 'C:\Users\Trenly\AppData\Local\Programs\Microsoft VS Code\bin\code.cmd'
Running: & "C:\Users\Trenly\AppData\Local\Programs\Microsoft VS Code\bin\code.cmd" --list-extensions --show-versions
Installed Extensions:
	Name                          Version
	----                          -------
	eamodio.gitlens               15.6.3
	mads-hartmann.bash-ide-vscode 1.43.0
	ms-python.debugpy             2024.12.0
	ms-python.python              2024.18.0
	ms-python.vscode-pylance      2024.11.1
	ms-vscode.powershell          2024.4.0
	plorefice.devicetree          0.1.1
	redhat.vscode-xml             0.27.1
	redhat.vscode-yaml            1.15.0
'Set()' function was invoked
'Test()' function was invoked
'Get()' function was invokded
Result of 'Get()':
	Name                      Version Exist Insiders
	----                      ------- ----- --------
	EditorConfig.EditorConfig         False    False
Desired State:
	Name                      Version Exist Insiders
	----                      ------- ----- --------
	EditorConfig.EditorConfig         True    False
Result of 'Test()':
	InDesiredState
	--------------
			 False
System was not in desired state, continuing
'Install($false)' was invoked
'Install-VSCodeExtension' was invoked with parameters:
	Name: EditorConfig.EditorConfig
	Version:
'Get-VSCodeExtensionInstallArgument' was invoked with parameters:
	Name: EditorConfig.EditorConfig
	Version:
Result of 'Get-VSCodeExtensionInstallArgument':
	EditorConfig.EditorConfig
'Invoke-VSCode' was invoked with parameters:
	Command: --install-extension EditorConfig.EditorConfig
Invoking Expression:
	 & "C:\Users\Trenly\AppData\Local\Programs\Microsoft VS Code\bin\code.cmd" --install-extension EditorConfig.EditorConfig
Result of 'Invoke-VSCode':
	Installing extensions...
	self signed certificate in certificate chain
	Failed Installing Extensions: editorconfig.editorconfig
Returned to 'Install-VSCodeExtension'
Installed Extensions:
	Name                          Version
	----                          -------
	eamodio.gitlens               15.6.3
	mads-hartmann.bash-ide-vscode 1.43.0
	ms-python.debugpy             2024.12.0
	ms-python.python              2024.18.0
	ms-python.vscode-pylance      2024.11.1
	ms-vscode.powershell          2024.4.0
	plorefice.devicetree          0.1.1
	redhat.vscode-xml             0.27.1
	redhat.vscode-yaml            1.15.0
Returned to 'Set()'
Returned from DSC Resource


Replace toastr with react-toastify, local copy of oidc-client and deps update

The replacement shrinks the bundle on about 70kb as there's no more jQuery in the bundle.

Thanks for this PR and apologize my delay - can you please check why the tests failed?

Thank you for your changes I used them manually here #16.


Call to an undefined method route()/back().

return redirect()->route('index');

Produce:

Call to an undefined method Illuminate\Http\RedirectResponse|Illuminate\Routing\Redirector::route()

return redirect()->back();

Produce:

Call to an undefined method Illuminate\Http\RedirectResponse|Illuminate\Routing\Redirector::back().

What is the level you are using?

Always the maximum level.

Could all of you test @Korri 's solution?

I am getting this exact error message @nunomaduro
Call to an undefined method Illuminate\Http\RedirectResponse|Illuminate\Routing\Redirector::route().


Validate requests

rendered
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I've revised the RFC and am looking for new reviews. Summary of changes:

Revised the User/File/Folder example per Mike's suggestion.
Added an additional example to the motivation section to show why validating requests is important in conjunction with standard validation.
Added an "unresolved question" about changing the Request::new API vs. adding a new Request::new_with_validation API.

Please weigh in on point (3) if you haven't already.

Revised! Notable changes:

Per in-person discussion yesterday, instead of modifying the Request::new constructor, we will add a new Request::new_with_validation constructor.
Added more concrete details about implementation (copied below for reference).

The new API will have the following signature:
pub fn new_with_validation(
        principal: Option<EntityUid>,
        action: Option<EntityUid>,
        resource: Option<EntityUid>,
        context: Context,
        schema: &Schema
    ) -> Result<Request> {
        ...
    }

(This is the same as the signature for Request::new, aside from the schema argument and return type.)
If the action is None (indicating that it is "unspecified"), then the function performs no additional checks. If the action is Some, then the function checks that the specified action is present in the schema, and that the principal and resource are consistent with the action's appliesTo lists in the schema.

Based on discussion, we generally support the addition of the Request::new_with_validation constructor. However, I've decided that this change does not merit the bar for an RFC, so rather than moving into FCP, I will be closing the issue. The core content of the RFC will be moved to an issue in the cedar repository.

Moved to cedar issue #191.


Added Swagger Ui

added open api documentation with swagger ...the paths and responses need to be updated

yes. i am aware.. trying to work away around it


Use accessor instead of method

I like the idea of settings, but looking at it, settings should be a property of model, not a method.
So the more laravel way of accessing them would be to use
$user->settings->get('some.setting'); instead of
$user->settings()->get('some.setting');
You can easily do that by using an accesor in your trait:
    public function getSettingsAttribute()
    {
        return new FieldSettingsManager($this);
    }

Yes is true, but I have chosen function because with the current implementation the user can use custom name for the settings field (ex. model_settings) and in same time can have an attribute named settings with a totally different data.


[Conformance] Always downgrade redundant conformances to marker protocols to a warning.

Previous compiler versions allowed this, so we should stage the change in as a warning. This was already a warning across modules, so this change only impacts redundant conformances to marker protocols within a module. This code also isn't particularly harmful, because marker protocols don't have requirements, so there isn't the same risk of unexpected behavior as other redundant conformances.

@swift-ci please smoke test

@swift-ci please smoke test


[PatchRelease] Prepare May patch release, Part 1

Exclude SDKs will be released in coming Part 2 later, below is the list excluded SDKs

App Configuration
Communicaton - Indentity and Room
EventGrid
EventHubs
Metric Advisor
Monitors
Schema Registry

API change check
API changes are not detected in this pull request.


Unable to install apxs module with PHP 7

The command phpbrew install next as PHP-7.0.0 fails with the following info:
Installing PHP SAPI module:       apache2handler
/usr/share/httpd/build/instdso.sh SH_LIBTOOL='/usr/share/apr-1/build-1/libtool' libs/libphp7.so /usr/libexec/apache2
/usr/share/apr-1/build-1/libtool --mode=install install libs/libphp7.so /usr/libexec/apache2/
libtool: install: install libs/libphp7.so /usr/libexec/apache2/libphp7.so
install: libs/libphp7.so: No such file or directory
apxs:Error: Command failed with rc=4653056

(Specifically the line install: libs/libphp7.so: No such file or directory)
When looking in the build directory, the module name is actually 'libphp7.0.0-dev.so' and not libphp7.so
I think the cause might be the following rule in the PatchCollection:: createPatchesForApxs2  function, but I'm not 100% sure:
RegexpPatchRule::always(
    '#libs/libphp\$PHP_MAJOR_VERSION\.#',
    'libs/libphp$PHP_VERSION.'
),

I just got the same error when compiling php-7.0.0 from master branch.

Yes it's caused by the apxs2 patch (out of date for php7)

The solution was mentioned #339 but I don't have time to fix it yet...

Fixed in 1.20.2 release, however I noticed that php7 with apache2 will cause apache crash (core dump)

however I noticed that php7 with apache2 will cause apache crash (core dump)

Do you have any news about this error?

I'm currently running PHP 7 on apache without any issues, so I'm not sure if it's still an issue

@pierredup could you please provide some more details about your configuration? What file(s) did you edit? Thanks.

I didn't need to edit any files. I just did a normal install of PHP 7 with the APXS module, and enabled the php7_module in my apache config (disabling the php5_module as well, off course)

@pierredup thank you for your reply.
I'm still in trouble with this... Still not getting results (except for some segmentation faults...)
Could you please explain a little better what files did you change and what did you write in? (maybe with some example configuration). I'm trying to use PHP 5.5.9 and 7.0.2, but only the switch in CLI works fine.
Thanks a lot.
@c9s do you have some docs about the Apache configuration?

I added the following to my httpd.conf file:
LoadModule php7_module        libexec/apache2/libphp7.0.1.so

<IfModule php7_module>
        AddType application/x-httpd-php .php
        AddType application/x-httpd-php-source .phps

        <IfModule dir_module>
                DirectoryIndex index.html index.php
        </IfModule>
</IfModule>

and removed everything that has php5_module

@pierredup
Great! Under Apache 2.4.7 I had to rename /etc/apache2/mods-enabled/php5.load in something different (php5.load.back is OK) and restart apache in order to get the work done :)
Now seems to be OK! Thank you!


NPS survey cropped on Chrome

The NPS survey is cropped on Chrome. My machine is ThinkPad X1. The same issue was reported from Surface users.

Potentially related to https://github.com/microsoftgraph/microsoft-graph-explorer-v4/issues/1412
The recommendation from the UX team is to use 1873W x 947H

The OCV team has created a ticket to fix this here
https://office.visualstudio.com/CLE/_workitems/edit/6485875

This issue is similar to #1987

I'd suggest that we close #1987 as a duplicate of this item.

@ElinorW where are we on this? It is still happening. It was also reported by external users.
This has a big impact on users, the NPS/CES scores and feedback we receive as well as our brand. According to the data, the most used browser with GE is Chrome.

@RabebOthmani yeah, the OCV team is working on it... Once they fix it on their end, I'll know if there's anything I need to do on the GE end


irctest for draft/multiline's max-lines and max-bytes limits

Resolved by #275 (the tests are still Ergo-specific but we have a path to generalizing them)


Stream continues to be open even though nothing can be fetched

Hi
I use this code to fetch jobs:
// Autoload classes
require_once realpath(__DIR__) . '/vendor/autoload.php';

$client = new Amp\Beanstalk\BeanstalkClient('tcp://<IP_ADDRESS>:11300');
$client->watch('testtube');
$client->ignore('default');

Amp\Loop::run(function() use ($client)
{
	Amp\Loop::repeat($msInterval = 1, function() use ($client)
	{
		$client->reserve(0)->onResolve(function($error, $result) use ($client)
		{
			$id = (int) $result['0'];

			if ($id <= 0)
				return;

			echo "Handle job: " . $id . "\n";

			$client->delete($id)->onResolve(function($error, $result) use ($client, $id)
			{
				echo "Delete job: " . $id . "\n";
			});
		});
	});
});

I use stunnel4 (guide: https://www.digitalocean.com/community/tutorials/how-to-encrypt-traffic-to-redis-with-stunnel-on-ubuntu-16-04) to create a tunnel between machine1 (running Beanstalk) and machine2 (consumer).
When using stunnel4 it will keep the port: 11300 on <IP_ADDRESS> open all the time, even though the remote port has closed due to either restart or the process stops.
However amphp/beanstalk doesn't timeout the connection as it sees the connection as still alive because the local port doesn't close - so the stream doesn't close.
If I add $stats = yield $client->getSystemStats(); right after repeat, it will close the connection and fail with: PHP Fatal error:  Uncaught Amp\ByteStream\StreamException: The stream was closed by the peer.
Is it however not that great to continuously send a command to request data, because it will waste ressources, and may slow down reserving jobs.
TLDR: amphp/beanstalk doesn't recognize stream closed when reserving.

I'll close this issue, as there hasn't been any response. If you have further questions, either respond to this issue or report a new one.


Created A working Responsive Contact us page with full logic as given in image

Description
Sir i have created a working contact form with the proper designing
THe form i created is responsive as well
Fixes #989
Screenshots
https://github.com/user-attachments/assets/00a0c997-b406-46c5-a866-f1a9f3fcb5ac

Checklist

[ ] Tests have been added or updated to cover the changes
[ ] Documentation has been updated to reflect the changes
[ ] Code follows the established coding style guidelines
[ ] All tests are passing

Work in toast notification or pop up notification that successfully message sent

@thestarsahil  Ok sir

@thestarsahil  Done sir
https://github.com/user-attachments/assets/9076974f-6d0f-4bcc-ba0c-601df29f9b4d


⚠ Bofrost.hr has degraded performance

In 8df2229, Bofrost.hr (https://www.bofrost.hr) experienced degraded performance:

HTTP code: 200
Response time: 8713 ms

Resolved: Bofrost.hr performance has improved in 0b6a443.


os/signal: TestSignalTrace failures on linux-ppc64* with "timeout … waiting for hangup"

2021-04-23T21:48:37-9cc3469/linux-ppc64le-buildlet
2021-04-23T21:43:10-bf92160/linux-ppc64-buildlet
2021-04-23T21:43:08-a25d1d4/linux-ppc64-buildlet
2021-04-22T22:01:47-7405968/linux-ppc64-buildlet
2021-04-22T21:23:59-f7afdfd/linux-ppc64-buildlet
2021-04-22T21:23:59-f7afdfd/linux-ppc64le-buildlet
2021-04-22T04:04:47-ece5935/linux-ppc64-buildlet
2021-04-21T23:21:55-7bedd47/linux-ppc64-buildlet
2021-04-21T21:25:26-7e97e4e/linux-ppc64-buildlet
--- FAIL: TestSignalTrace (0.43s)
    signal_test.go:880: timeout after 200ms waiting for hangup
FAIL
FAIL	os/signal	6.243s

CC @ianlancetaylor @laboger @ceseo

Interesting that these started after https://go-review.googlesource.com/c/go/+/305149/ was merged.
FYI  replace @pmur for @ceseo for notification of ppc64x issues. Thanks.

I tested this on an older POWER8/Ubuntu 16/ppc64le machine. I see this failure before and after this patch (I backported the test with it). Notably, the failing test was added in this commit. This test seems to hiccup on the failing machine, taking 6-7x or longer on some runs.
I can't reproduce on most other P8/P9 machines though.

Marking as release-blocker for Go 1.17 because this test is new as of 1.17.
(CC @golang/release)

2021-04-28T12:51:42-f68878f/linux-ppc64-buildlet
2021-04-27T21:16:55-30002e6/linux-ppc64le-buildlet
2021-04-27T19:18:02-8ab7064/linux-ppc64-buildlet
2021-04-27T17:03:53-074a49b/linux-ppc64-buildlet
2021-04-27T02:39:52-434e12f/linux-ppc64le-buildlet
2021-04-26T21:35:26-be28caf/linux-ppc64-buildlet
2021-04-26T21:35:26-be28caf/linux-ppc64le-buildlet


Clarify radio error message examples

This PR clarifies some of the error messages on the radio button component page.
Should probably be reviewed by @christopherthomasdesign

You can preview this change here:
Built with commit a06de817e9ce1929c9020daeb27422100175ed72
https://deploy-preview-1224--govuk-design-system-preview.netlify.com

Colin from DWP pointed out that there is similar content in the checkboxes error message guidance that we might want to make consistent @StephenGill ?

OK - suggest we merge this (assuming you agree with it), then make a new card for the checkbox work

@36degrees this is one of the PRs I mentioned at stand up - I've fixed the typo with an additional commit

Squashed those commits together. @christopherthomasdesign are you happy with this now?


Fully support CBS in rdopkg

cbsbuild command to build in CBS, we'd need a switch to choose quickly between common/
cbstag to tag builds (testing/release and possibly retag a package for another release)

In order to make it easier, I also create a copr repo to host centos packaging related packages.
https://wiki.centos.org/HowTos/Centpkg
By installing centos-packager, you'd get a cbs command.

Shoul cbsbuild generate update.yml etc.? Are we going to continue to use rdoupdate or not? @apevec

Few quick notes (I'll complete them later)

testing if package is registered in the following tags cloud7-openstack-{common,)-{candidate,testing}, if not register them
=> we may want to override the tag for some common packages override
build them (and potentially tag them to -testing?)

@yac rdoupdate yml stays but CI flow behind it will be different, also RDO >= Liberty is EL7 only which simplifies it:

take builds from update.yml and tag them -testing
cbs repo is regenerated which triggers (TBD) new CI job on ci.centos.org
on pass builds get promoted to -release tag and update announcement email with auto-generated release notes (TBI using github.com/openstack/reno) is posted to rdo-list

@hguemar
can you give example for "override the tag for some common packages override" ?
re. "potentially tag them to -testing" - see proposed CI flow above: we need to keep using explicit updates, so we can group dependent packages with description. But we could also optimize for independent single package updates by adding an option e.g. cbsbuild --push which auto-generates update.yml using RPM changelog and immediately sends gerrit review.

@apevec recently, pecan, we had to bump it specifically for liberty. Not that's critical but being able to override default tag would be useful sometimes.

After I built a package against the wrong CBS target, I fixed it myself.
https://review.rdoproject.org/r/#/c/1219/1

Fixed in 8c4fc0612df60d590e4d4c882e5e23ab94947716


Add support for installing binary distributions of HWLOC

this depends on #1144
this fixes #1124

@hkaiser,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot


Starting the conversation with "select subscription" ends up repeating the prompt to the user

Not happening anymore with the refactoring we did on the dialogs chain.


Cannot group by resource group if I have access to a resource but not its resource group

Hi, I have a "tricky" case that is not well handled by the extension.
In a subscription, I have access to an App Service but not its resource group. So, when I tried to group by resource group, I got the following error:
Internal error: Expected value to be neither null nor undefined: resourceGroup for grouping item

The error is thrown by this line (src/tree/azure/grouping/AzureResourceGroupingManager.ts#164)
It is possible to display the resource group even if we don't have access to it? We will not be able to do action on it, of course.

Hi @vsantele

It is possible to display the resource group even if we don't have access to it? We will not be able to do action on it, of course.

I just want to clarify, but the scenario is that you want the resource group to still be displayed? Not the resource that's in the resource group?

Hi @nturinski,
It's more the opposite way. I don't have access to the resource group, only to one resource in it, but I still want to group all my available resources by resource group.
At the moment, if I want to group by resource group, I get an error because the AzureResource of the related resource group of my service app is not in the array allResources passed in groupByResourceGroup
But we can find the name of this resource group. So why not have this RG displayed in the list and not only RG where I got right on it?
Here is a schema to be clear:
- MyRG1 <- I have access
-- MyCosmosDB <- I Have access
- MyRG2 <- I don't have access
-- MyAppService <- I have access

I cannot group my resources by resource group because of MyRG2.
One way of solving this is to display only a "visual RG" when a user doesn't have access to the parent RG of a resource. This way, we can always group by RG. A "visual RG" will not have all the options inside its context menu like other RG (delete, edit tags, etc)
But, GroupingItemFactory.createResourceGroupGroupingItem requires an AzureResource, so I don't think it's possible to do this without further exploration.

One way of solving this is to display only a "visual RG" when a user doesn't have access to the parent RG of a resource. This way, we can always group by RG. A "visual RG" will not have all the options inside its context menu like other RG (delete, edit tags, etc)

I agree with the proposed solution.


temp

Unfinished changes. Fixing patchset
Change-Id: Ib18a87c087c66a99e4d8d46ff2477082c9b3c647

Code Review comments can be found at https://gerrithub.io/q/Ib18a87c087c66a99e4d8d46ff2477082c9b3c647


division remainder modulo

In table in "Introduction to Julia syntax/basic syntax":
"12 % 2 2 (remainder)"
But 12 % 2 is zero. Replace with 12 % 5 is 2 or something.

Fixed.


"Extra args" input

Presently, if there is some option the user wants to pass to buildah that we don't have an input for, they are out of luck.
Tekton solves this problem with an "extra args" option that the user can put any extra args they like into and they are just appended to the buildah command.
https://github.com/tektoncd/catalog/blob/master/task/buildah/0.2/buildah.yaml

because of the way we have to run many commands in the non-dockerfile case, this does not work as well as I thought it did.

I think we should do this for build with dockerfile case, as it seems to be genuine requirement.


Update uwuifyWord() documentation

Right now the uwuifySentence() function filters out URL's, adds faces and actions. The uwuifyWord() only changes the letters to be more uwufied but the documentation doesn't reflect this right now. :(

Will add this to the new 1.2.0 documentation with a list of possible faces, actions and exclamations

I'll release 2.0.0 today with the new documentation!


update bluebird dependencies to 2.8.2

just update bluebird dependencies

the latest is 2.9.1, why not set the version to ^2.9?

@tjwebb Sorry my bad, I look at here. Now it's updated to ^2.9

@hellowin gotcha. It's accurate here: https://david-dm.org/balderdashy/waterline :)
I'll merge shortly


autocomplete=false does not work, it needs to be autocomplete=off

In the login page, the autocomplete attribute is set dynamically with a boolean expression.  The result is true or false, but unfortunately the spec requires on or off as the value of the autocomplete attribute.

Fixed in UAA 3.2.0 and above !


Include an example template for creating tmt tests

Vast majority of tests verifying the tmt features shares a similar outline of the beakerlib skeleton. Let's make it super easy to start writing a new tmt test. The skeleton also covers submitting log.txt when something goes wrong during the test execution so that a detailed investigation is possible later.
Pull Request Checklist

[ ] write the documentation
[ ] include a release note

PS: with beakerlib+homebrew, we might want to rethink how to source beakerlib.sh

Could you explain a bit?

PS: with beakerlib+homebrew, we might want to rethink how to source beakerlib.sh

Could you explain a bit?

The issue is about:
source /usr/share/beakerlib/beakerlib.sh

This can't be the install path for beakerlib on homebrew also because on macos and linuxbrew they are different. It needs to be editable, most likely through BEAKERLIB_DIR which tmt provides depending on detected OS

@psss Do you want to add a milestone here?


Danger crashes if multiple inline comments have same severity, file and line number

Report
What did you do?
While implementing support for SwiftFormat plugin's inline_mode, I noticed that if multiple plugins are trying to add inline_comment with the same severity to the same file and line, danger crashes with lib/danger/request_sources/bitbucket_server.rb:158:in 'sort': comparison of Danger::Violation with Danger::Violation failed (ArgumentError).
Github seems to have the same sort.
https://github.com/danger/danger/blob/master/lib/danger/request_sources/bitbucket_server.rb#L158
What did you expect to happen?
Expected danger not to crash, and all comments to be sorted out in any order.
What happened instead?
💥
Your Environment
Dangerfile
swiftlint.lint_files(fail_on_error: true, inline_mode: true, additional_swiftlint_args: '--strict')
swiftformat.check_format(fail_on_error: true, inline_mode: true)

Fair, yeah, seems reasonable

I wrote the following spec to reproduce this issue but it passes.
https://github.com/manicmaniac/danger/commit/92630ffd147a8676f3c5a809a991bae840903c79
@pahnev Could you tell me what values in file and line causes this error? I think they were invalid values that is not possible to compare.

Hi, @manicmaniac, so here's my Dangerfile:
swiftformat.check_format(fail_on_error: true, inline_mode: true)
swiftlint.lint_files(fail_on_error: true, inline_mode: true)

And here's the output:
Results:
Errors:
- [ ] Path/To/File/ActivationTokenTests.swift#L11: warning: (consecutiveBlankLines) Replace consecutive blank lines with a single blank line. `ActivationTokenTests.swift:11`
- [ ] SwiftFormat found issues
Warnings:
- [ ] Path/To/File/ActivationTokenTests.swift#L12: Limit vertical whitespace to a single empty line. Currently 3.
`vertical_whitespace` `ActivationTokenTests.swift:12`

And if I make the SwiftLint elevate the message to and error:
swiftlint.lint_files(fail_on_error: true, inline_mode: true, additional_swiftlint_args: '--strict')
it results in a crash I mentioned above.
Both Swiftformat and SwiftLint work with the desired command alone, but not together.


testkube: init at 1.10.40

Description of changes
https://testkube.io/

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Obsolete by https://github.com/NixOS/nixpkgs/pull/353751


Fedora containerd

Using containerd directly should be simpler and allows us to test Kata
Containers also with Fedora.
Fixes: #671

@avalluri shall we switch?


⚠ Turnos 24x7 has degraded performance

In 89a3169, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 989 ms

Resolved: Turnos 24x7 performance has improved in 7be6487.


Improved file operations

Also fixes #90 for tmpnam()

This change is

Please fix merge conflicts

Review status: 0 of 2 files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from Reviewable

Merge conflicts fixed.
I also added tests and fixed a bug that I hadn't noticed until I added the tests.
That will teach me to write the tests earlier.

Reviewed 1 of 2 files at r1, 2 of 2 files at r3.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Use route instead of URL

Rails can provide route in form of Controller#Action and Sinatra in form of GET /some/path/:id

Can you please provide some more detail for this?

The idea is simple. Instead of logging /some/resource/1, /some/resource/2, /some/resource/3 we can log /some/resource/:id. This correlates with what opentracing suggests
You can look into Skylight code on how to do this:

sinatra
rails

OK, yes that makes sense. Thanks!


Error connecting to datasource  Reason: Unknown database

Hello Beavers!
I'm a DB learner and installed xampp and dbeaver (Linux lite kernel 5.3), but i'm facing an issue and i could not find the solution for it.... I really don't know if I'm doing something wrong or is a bug (probably I'm its my fault somehow) ... can you guys help me, please?
My problem starts when i create a new data base with MySql 8+, when i click the arrow down in database navigator, the error: 'Unknown database ' appears, with a small red 'x' beyond it, as above:

I already using mysql in Linux terminal, with the workbench, they work perfectly.
please guys your platform is fantastic and I intent to use it..Could u help me?
Have a nice weekend!

When you create a connection in dbeaver it doesn't create a new database. Database dbase must exist on server.
You may leave database parameter (on connection properties page) empty to connect to the server.
You can create new database by using right click on Databases folder->Create->Database.

Thank you Serge-rider! It works! :D

Me funciono!


cnt modified

Changed to the maximum days allowed in OpenWeatherMap free version

Hi @pablopereira27!
Could you please also adjust the docblocks of the methods to reflect the change? Thanks!

docblocks adjusted

Thanks!

I just released version 2.0.4 including this fix.


Allow for US Bank Account

Allow for US bank account and refactor for better handling for unimplemented bank account types...

@beshrkayali your tests are failing on this one.

@appel268576 should be good now...


Add parameters

Adds Mean surface temperature
Adds Mean change in virtual temperature

This looks fine. But why not changing the drivers correspondingly in the same go?

This looks fine. But why not changing the drivers correspondingly in the same go?

This must merge here before it can be used in ClimateMachine (CM) because CLIMAParameters is in CM’s deps, which must be updated to use the latest version. If these parameters were defined in CM, we could do it in one go, but then we’d never be able to split out CM into separate packages

bors r+


Custom Scroll Bar & Fix Overflow Issues

Style scroll bars and test in windows for compatibility.

Zip for preview
chrome-milk-2.0.1.zip