Use latest version of mdbook in CI

Fixes #20
Fixes #8
As discussed in https://github.com/rust-embedded/book/pull/212, this is causing rendering differences  between the rendered book from https://docs.rust-embedded.org/book/ and https://rust-embedded.github.io/book/.
Probably this shouldn't be merged until the reference PR is, as without it attributes will be erroneously hidden in some examples.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @adamgreig (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Probably this shouldn't be merged until the reference PR is, as without it attributes will be erroneously hidden in some examples.

@austinglaser Doesn't this one have the same regex problem as https://github.com/rust-embedded/debugonomicon/commit/c6cba56f16a28a9c11cc0f299cbe8d9a61d626dc originally?

Doesn't this one have the same regex problem as rust-embedded/debugonomicon@c6cba56 originally?

Yes, but I was waiting for direct feedback (since https://github.com/rust-embedded/embedonomicon/pull/59 was merged without comment, I was assuming that there might be different requirements regarding stability for each).
I'm happy to open PRs to make this consistent across all rust-embedded books, though, if we want all to be pinned to 0.x.y versions of mdbook.
But is that really what we want? If the goal is to avoid breaking changes, we should instead pin to 0.3.x versions. (not trying to ask a rhetorical question here, just honestly curious)

Pinning to 0.3 is not going to prevent breakage. 0.2.2 was the breaking version so pinning to 0.2.x wouldn't have done anything. Using 0.2.1 specifically was a stopgap measure.

I'm talking about API changes, not bugs. Certainly we won't prevent breakage if a buggy version of mdbook is released -- I don't think anything short of pinning to a static version could do that (as was the original case).
Regressions do demonstrably happen (https://github.com/rust-embedded/book/pull/58, https://github.com/rust-embedded/book/issues/211).
But limiting to a semver series that shouldn't contain any breaking API changes could also be a reason to avoid blindly using the latest. 0.4 could bring breaking changes relative to 0.3, as could an eventual 1.0 release.
I see three strategies for selecting an mdbook version for a build:

Take a static version (e.g. 0.3.5), and require a manual step to update it

Prevents mdbook regressions
Prevents mdbook API breakage

Take the latest patch version of a stable series (e.g. 0.3.z)

Does not prevent mdbook regressions
Prevents mdbook API breakage

Take the latest minor version of a stable series (e.g. 0.y.z)

Does not prevent mdbook regressions
Does not prevent mdbook API breakage

Take the latest version regardless

Does not prevent mdbook regressions
Does not prevent mdbook API breakage

From that standpoint, I don't see a strong reason to require across-the-board updates when mdbook 1.0 comes out if it doesn't gain us any safety over just letting the version freely update to the latest.

From where I'm standing, there's not a whole lot of API which could break; it more or less boils down to HTML quality and design as well as regressions.
I'm not sure whether it's more cumbersome to fix any fallout or to manually fire off a series of PRs to bump the version (and making sure they don't cause breakage) every now and then.

I'm not sure whether it's more cumbersome to fix any fallout or to manually fire off a series of PRs to bump the version (and making sure they don't cause breakage) every now and then.

If we allow it to just take the latest, there's a possibility for that series of PRs to fix potential breakage. If we pin it in any way, there will definitely be a series of PRs any time it needs to be manually bumped.
I agree about your point regarding the (lack of) value in API stability as well. Which pushes me more in the direction of "just use the latest."
(also apologies for the duplication between this thread and https://github.com/rust-embedded/docs/issues/20)

We merged #24 which is essentially the same but had an up-to-date CI build attached and was manually inspected to work now. Kudos for your work @austinglaser.


pin libxml2 <2.9.11

fix #57

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@ocefpaf Tests are good, would you please review this?

LGTM but I'm a bit worried that libxml2 is pinned for the ecosystem and this constraint here won't help much unless we "patch" the previous lxml built. Say, if you try to install it the solver will try to optimize and get the previous build with the latest libxml2.
Can you identify if the problem happens with just a few lxml we built? If so we can mark them broken and mitigate that.

Merging anyway b/c regardless of patching the previous packages or marking them as broken we need this.

LGTM but I'm a bit worried that libxml2 is pinned for the ecosystem and this constraint here won't help much unless we "patch" the previous lxml built. Say, if you try to install it the solver will try to optimize and get the previous build with the latest libxml2.
Can you identify if the problem happens with just a few lxml we built? If so we can mark them broken and mitigate that.

Many packages added constraint libxml2 <2.9.11, so they will actually get lxml 4.6.3 instead of the latest lxml 4.8.0, but that's fine because the older one still works. However, there is no lxml 4.6.3 or any suitable built on python 3.10, and this PR will fix it.


build(typespec): bump typespec to 0.47.1

Description

bump typespec to 0.47.1
bump autorest.testserver to 3.3.48 to resolve dependency conflict
change collectoinFormat due to upstream changes

resolve #3660
Checklist
To ensure a quick review and merge, please ensure:

[ ] The PR has a understandable title and description explaining the why and what.
[ ] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[ ] The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

[ ] Build is completely green

Submissions with test failures require tracking issue and approval of a CODEOWNER

[ ] At least one +1 review by a CODEOWNER
[ ] All -1 reviews are confirmed resolved by the reviewer

Override/Marking reviews stale must be discussed with CODEOWNERS first

close as duplicate of #3647


store_history

i have not found the store_history work when i run the demo.py

Hi @xuzhongyou - have you built locally? store_history hasn't yet been released in the version made available on PyPI or through pip.

I hope I can use the latest version via PYPI.
When will it be updated?

<IP_ADDRESS> is now live on PyPI.


Create function for closing/quitting the IDE

function for complete quitting the IntelliJ IDEA after all the the UI tests has been performed would be really useful, something like:
remoteRobot.quitIde();

this function would close the IDE and completely kill/destroy the whole process in which the IDE run for the UI tests

Hello, thanks for the issue, will think how to make this the most convenient way. That could be useful when you use the Gradle plugin to launch an idea. In case of using launcher you can kill Ide process this way

@nizienko Hello, thanks for replay. For now I use the destroy() to kill the process as you mentioned. If there will be better way in the future, I will be glad to test it and use it.

This function would be highly appreciated, since it would give us a clean slate for each test, making the tests more dependable.


Add benchmarks for public API

Before any major rewriting, setup some benchmarks so we can check for regressions.
We'll want to check for regressions in all cases, but especially the hot path (where the assertions pass without panicking).
The benchmarks shouldn't be run automatically, just be available for checking locally.

A first pass has been added here. As any benchmarking pulls in a ton more dependencies and dev-dependencies cannot be optional, I've put in a separate crate/repo.


Nativewind styles are not working on web platform

Describe the bug
Nativewind does not work on the web platform. Works only when we add 1 style (i.e. 1 class). For example, if you add className="bg-gray-400" to the View, then it works if className="bg-gray-400 hidden" then the styles of this block are cleared.
Expected behavior
To ensure that the styles on the web platform are the same with mobile devices
Screenshots

ps: I tried to follow the example, I tried to change the webpack and metro configurations. Changed versions. Tried different configurations postcss, tailwind, app, babel

yes, same here

following ,. same issue

I have the same issue. Tailwind classes do not appear in the browser.

Maybe rollback to older version will help?

same issue , styles don't apply on web.

same issue here , any fixes yet?

Yep, same problem. My config is:
"expo": "48.0.16",
"nativewind": "^2.0.11",
"next": "13.4.5",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-native": "0.71.8",
"react-native-web": "~0.18.12",

tailwind.config.js
const nativewind = require('nativewind/tailwind/css');
const {PrimaryColors, SecondaryColors} = require("../../libs/business/src");

/** @type {import('tailwindcss').Config} */
module.exports = {
  content: [
    './app/**/*.{js,ts,jsx,tsx,mdx}',
    './components/**/*.{js,ts,jsx,tsx,mdx}',
    './src/**/*.{js,ts,jsx,tsx,mdx}',
    '../../libs/ui/**/*.{js,jsx,ts,tsx}',
  ],
  theme: {
    extend: {
      colors: {
        primary: PrimaryColors.primary,
        secondary: PrimaryColors.secondary,
        white: SecondaryColors.fourth,
      }
    },
  },
  plugins: [nativewind],
  important: 'html',
};

I use twrnc and no problems on web - https://github.com/jaredh159/tailwind-react-native-classnames

@lukaszradziak I tried and it works. However, on web it creates every style inside the style tag, which means we will ship a tons of unnecessary repeated styles, right?
nativewind still the best solution if we can fix this problem.
Anyone was able to manage it?

I don't know if it fixes everyone's problem but in my case adding this in my App.js worked:
import { NativeWindStyleSheet } from "nativewind";

NativeWindStyleSheet.setOutput({
  default: "native",
});

(I have no idea where this comes from, I have just seen this snippet in some other projects on Github and it seems to work)

I don't know if it fixes everyone's problem but in my case adding this in my App.js worked:
import { NativeWindStyleSheet } from "nativewind";

NativeWindStyleSheet.setOutput({
  default: "native",
});

(I have no idea where this comes from, I have just seen this snippet in some other projects on Github and it seems to work)

good catch, works for me, thanks! 👍
btw, using Expo Router so instead of putting it in my App.js I put it in my root _layout.tsx

When importing a `' into nextjs, how is this solution related to? It still not putting the tailwind classes on web.
My setup are nx workspaces:

Expo.
NextJS.
Shared UI Libraries.

I'm importing my components from the shared UI libraries. Works fine on Expo, but not dropping tw classes on nextjs (and there's no error). If I use style or twrnc as mentioned before, it works (however, as I said, twrnc adds a ton of inline styles, which I don't want).

Hey guys, I managed to solve my problem. I don't know why and how, probably I unintentionally deleted my babel config and I didn't notice. I'm wrapping my components now with styled as docs says to, and everything is working as expected.
There are some differences between web and mobile styles, but that's another problem.
Thanks.

I don't know if it fixes everyone's problem but in my case adding this in my App.js worked:
import { NativeWindStyleSheet } from "nativewind";

NativeWindStyleSheet.setOutput({
  default: "native",
});

(I have no idea where this comes from, I have just seen this snippet in some other projects on Github and it seems to work)

This worked perfectly!

I don't know if it fixes everyone's problem but in my case adding this in my App.js worked:
import { NativeWindStyleSheet } from "nativewind";

NativeWindStyleSheet.setOutput({
  default: "native",
});

(I have no idea where this comes from, I have just seen this snippet in some other projects on Github and it seems to work)

This does solve the problem.
It is mentioned in the docs: https://www.nativewind.dev/quick-starts/expo
"Expo SDK <=45 supports React Native Web <=0.17 which cannot output classNames. You need to change the NativeWindStyleSheet output to use native for all platforms."
afaik i'm using Expo SDK 48, so I don't know why I needed this.

We can solve above problem using below code.
import { NativeWindStyleSheet } from "nativewind";

NativeWindStyleSheet.setOutput({
  default: "native",
});

You can define above code in the index.tsx or _layout.tsx in the project.

I don't know if it fixes everyone's problem but in my case adding this in my App.js worked:
import { NativeWindStyleSheet } from "nativewind";

NativeWindStyleSheet.setOutput({
  default: "native",
});

(I have no idea where this comes from, I have just seen this snippet in some other projects on Github and it seems to work)

Can confirm this fixing the issue even in Expo SDK 50 with nativewind 2.0.11. Putting it in my _layout.tsx allowed it to work in web.

Yo if anyone has this issue on NativeWind v4 with Metro, run useFonts hook on your index route:
import { useFonts } from 'expo-font';
const [fontsLoaded, fontError] = useFonts({
    Athletics: require('../assets/fonts/Athletics-Regular.otf'),
});

I think that's intentional. So it will not work. See https://www.nativewind.dev/quick-starts/expo#expo-web

When running on web, NativeWind is a compatability layer between Tailwind CSS and React Native.

You will need follow a Tailwind CSS installation guide and ensure NativeWind is transpiled.

This means you need to setup it like with every other web app:
Create src/tailwind.css:
@tailwind base;
@tailwind components;
@tailwind utilities;

Run
npx tailwindcss -i ./src/tailwind.css -o ./public/tailwind.css --watch

With expo-router add to your app/_layout.tsx
import Head from 'expo-router/head'

      <Head>
        <link href="/tailwind.css" rel="stylesheet" />
      </Head>

Now it's working.

Any way to fix h-screen/w-screen for web i am getting Prop style did not match. Server: "width:0px" Client: "width:1536px"

I think that's intentional. So it will not work. See https://www.nativewind.dev/quick-starts/expo#expo-web

When running on web, NativeWind is a compatability layer between Tailwind CSS and React Native.

You will need follow a Tailwind CSS installation guide and ensure NativeWind is transpiled.

This means you need to setup it like with every other web app:
Create src/tailwind.css:
@tailwind base;
@tailwind components;
@tailwind utilities;

Run
npx tailwindcss -i ./src/tailwind.css -o ./public/tailwind.css --watch

With expo-router add to your app/_layout.tsx
import Head from 'expo-router/head'

      <Head>
        <link href="/tailwind.css" rel="stylesheet" />
      </Head>

Now it's working.

Following this and the nativewind doc(v2), after step 3 Add the Babel plugin is done, you will need to install postcss and autoprefixer using npm install -D postcss autoprefixer (from tailwind's doc).
Then create a css file, for example assets/styles/tailwind.css and add the default values from tailwind's doc.
Then import the file to app/_layout.tsx or whatever your main file, something like import<EMAIL_ADDRESS>Then npx tailwindcss init -p to get the postcss config file.
After this, you can restart expo server and your app is good to go. No need npx tailwindcss -i ... or <link href="/tailwind.css"... because you already imported it _layout.tsx or index.tsx.

I don't know if it fixes everyone's problem but in my case adding this in my App.js worked:
import { NativeWindStyleSheet } from "nativewind";

NativeWindStyleSheet.setOutput({
  default: "native",
});

(I have no idea where this comes from, I have just seen this snippet in some other projects on GitHub and it seems to work)

Great. Thanks for this catch. This somehow made it work. I would love to know why it was not working on the web and why this piece of code made it work. It would be beneficial if anybody elaborate on the theory. Eagerly waiting to see responces.

issue

This worked for me in
Add this way
import { StyleSheet, Text, View } from 'react-native'
import React, { useEffect } from 'react'
import { Slot, SplashScreen, Stack } from 'expo-router'
import { useFonts } from 'expo-font'
import { NativeWindStyleSheet } from "nativewind";
SplashScreen.preventAutoHideAsync();
const RootLayout = () => {
const [fontsLoaded, error] = useFonts({
"Poppins-Black": require("../assets/fonts/Poppins-Black.ttf"),
"Poppins-Bold": require("../assets/fonts/Poppins-Bold.ttf"),
"Poppins-ExtraBold": require("../assets/fonts/Poppins-ExtraBold.ttf"),
"Poppins-ExtraLight": require("../assets/fonts/Poppins-ExtraLight.ttf"),
"Poppins-Light": require("../assets/fonts/Poppins-Light.ttf"),
"Poppins-Medium": require("../assets/fonts/Poppins-Medium.ttf"),
"Poppins-Regular": require("../assets/fonts/Poppins-Regular.ttf"),
"Poppins-SemiBold": require("../assets/fonts/Poppins-SemiBold.ttf"),
"Poppins-Thin": require("../assets/fonts/Poppins-Thin.ttf"),
});
useEffect(() => {
if (error) throw error;
if (fontsLoaded) {
  SplashScreen.hideAsync();
}

}, [fontsLoaded, error]);
if (!fontsLoaded && !error) {
return null;
}
return (

<Stack.Screen name='index' options={{headerShown : false}} />

)
}
export default RootLayout
NativeWindStyleSheet.setOutput({
default: "native",
});
// const styles = StyleSheet.create({})

I've played around with both solutions now and for me both of them work (individually and adding both at the same time).
I've decided to stick with @patlux 's solution based @minhquan1313's implementation, simply based on the premise that it looks like the more intended implementation of TailwindCss on the web. So my final _layout.tsx looks like this:
import { Stack } from 'expo-router'
import * as SplashScreen from 'expo-splash-screen'
import { GluestackUIProvider, Text } from '@gluestack-ui/themed'
import { config } from '@gluestack-ui/config'
import<EMAIL_ADDRESS>
export {
  // Catch any errors thrown by the Layout component.
  ErrorBoundary,
} from 'expo-router'

export const unstable_settings = {
  // Ensure that reloading on `/modal` keeps a back button present.
  initialRouteName: '(tabs)',
}

// Prevent the splash screen from auto-hiding before asset loading is complete.
SplashScreen.preventAutoHideAsync()

export default function RootLayout() {
  [... some fonts stuff]

  return <RootLayoutNav />
}

function RootLayoutNav() {
  return (
    <GluestackUIProvider config={config}>
      <Stack>
        <Stack.Screen
          name='index'
          options={{ headerShown: false }}
        />
        <Stack.Screen
          name='modal'
          options={{ presentation: 'modal' }}
        />
      </Stack>
    </GluestackUIProvider>
  )
}

assets/styles/tailwind.css
@tailwind base;
@tailwind components;
@tailwind utilities;

package.json
{
  "version": "1.0.0",
  "main": "expo-router/entry",
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "web": "expo start --web",
    "test": "jest --watchAll"
  },
  "jest": {
    "preset": "jest-expo"
  },
  "dependencies": {
    "@expo/vector-icons": "^14.0.0",
    "@gluestack-style/react": "^1.0.56",
    "@gluestack-ui/config": "^1.1.18",
    "@gluestack-ui/themed": "^1.1.30",
    "@react-navigation/native": "^6.0.2",
    "expo": "~51.0.14",
    "expo-av": "^14.0.5",
    "expo-constants": "^16.0.2",
    "expo-device": "^6.0.2",
    "expo-document-picker": "^12.0.2",
    "expo-font": "~12.0.7",
    "expo-linking": "~6.3.1",
    "expo-router": "~3.5.16",
    "expo-splash-screen": "~0.27.5",
    "expo-status-bar": "~1.12.1",
    "expo-system-ui": "~3.0.6",
    "expo-web-browser": "~13.0.3",
    "lucide-react-native": "^0.395.0",
    "nativewind": "^2.0.11",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-native": "0.74.2",
    "react-native-appwrite": "^0.4.0",
    "react-native-gesture-handler": "^2.16.2",
    "react-native-reanimated": "~3.10.1",
    "react-native-safe-area-context": "4.10.1",
    "react-native-screens": "3.31.1",
    "react-native-svg": "~15.2.0",
    "react-native-url-polyfill": "^2.0.0",
    "react-native-web": "~0.19.10"
  },
  "devDependencies": {
    "@babel/core": "^7.24.3",
    "@types/react": "~18.2.45",
    "autoprefixer": "^10.4.19",
    "jest": "^29.2.1",
    "jest-expo": "~51.0.1",
    "postcss": "^8.4.38",
    "react-test-renderer": "18.2.0",
    "tailwindcss": "3.3.2",
    "typescript": "~5.3.3"
  },
  "private": true
}

I don't know if it fixes everyone's problem but in my case adding this in my App.js worked:
import { NativeWindStyleSheet } from "nativewind";

NativeWindStyleSheet.setOutput({
  default: "native",
});

(I have no idea where this comes from, I have just seen this snippet in some other projects on Github and it seems to work)

I love you ❤

import { NativeWindStyleSheet } from "nativewind";
NativeWindStyleSheet.setOutput({
default: "native",
});

You are a legend <3

Anyone got this working with nativewind v4 ?

I don't know if it fixes everyone's problem but in my case adding this in my App.js worked:
import { NativeWindStyleSheet } from "nativewind";

NativeWindStyleSheet.setOutput({
  default: "native",
});

(I have no idea where this comes from, I have just seen this snippet in some other projects on Github and it seems to work)

good catch, works for me, thanks! 👍
btw, using Expo Router so instead of putting it in my App.js I put it in my root _layout.tsx

Worked for me too...thank you

import { NativeWindStyleSheet } from "nativewind";
NativeWindStyleSheet.setOutput({
default: "native",
});

I would also love to know

hi every one , i'm using expo and i have same issue but i added it in my index.js and it works thanks everyone
import { NativeWindStyleSheet } from "nativewind";
NativeWindStyleSheet.setOutput({
default: "native",
});

I've played around with both solutions now and for me both of them work (individually and adding both at the same time).
I've decided to stick with @patlux 's solution based @minhquan1313's implementation, simply based on the premise that it looks like the more intended implementation of TailwindCss on the web. So my final _layout.tsx looks like this:
import { Stack } from 'expo-router'
import * as SplashScreen from 'expo-splash-screen'
import { GluestackUIProvider, Text } from '@gluestack-ui/themed'
import { config } from '@gluestack-ui/config'
import<EMAIL_ADDRESS>
export {
  // Catch any errors thrown by the Layout component.
  ErrorBoundary,
} from 'expo-router'

export const unstable_settings = {
  // Ensure that reloading on `/modal` keeps a back button present.
  initialRouteName: '(tabs)',
}

// Prevent the splash screen from auto-hiding before asset loading is complete.
SplashScreen.preventAutoHideAsync()

export default function RootLayout() {
  [... some fonts stuff]

  return <RootLayoutNav />
}

function RootLayoutNav() {
  return (
    <GluestackUIProvider config={config}>
      <Stack>
        <Stack.Screen
          name='index'
          options={{ headerShown: false }}
        />
        <Stack.Screen
          name='modal'
          options={{ presentation: 'modal' }}
        />
      </Stack>
    </GluestackUIProvider>
  )
}

assets/styles/tailwind.css
@tailwind base;
@tailwind components;
@tailwind utilities;

package.json
{
  "version": "1.0.0",
  "main": "expo-router/entry",
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "web": "expo start --web",
    "test": "jest --watchAll"
  },
  "jest": {
    "preset": "jest-expo"
  },
  "dependencies": {
    "@expo/vector-icons": "^14.0.0",
    "@gluestack-style/react": "^1.0.56",
    "@gluestack-ui/config": "^1.1.18",
    "@gluestack-ui/themed": "^1.1.30",
    "@react-navigation/native": "^6.0.2",
    "expo": "~51.0.14",
    "expo-av": "^14.0.5",
    "expo-constants": "^16.0.2",
    "expo-device": "^6.0.2",
    "expo-document-picker": "^12.0.2",
    "expo-font": "~12.0.7",
    "expo-linking": "~6.3.1",
    "expo-router": "~3.5.16",
    "expo-splash-screen": "~0.27.5",
    "expo-status-bar": "~1.12.1",
    "expo-system-ui": "~3.0.6",
    "expo-web-browser": "~13.0.3",
    "lucide-react-native": "^0.395.0",
    "nativewind": "^2.0.11",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-native": "0.74.2",
    "react-native-appwrite": "^0.4.0",
    "react-native-gesture-handler": "^2.16.2",
    "react-native-reanimated": "~3.10.1",
    "react-native-safe-area-context": "4.10.1",
    "react-native-screens": "3.31.1",
    "react-native-svg": "~15.2.0",
    "react-native-url-polyfill": "^2.0.0",
    "react-native-web": "~0.19.10"
  },
  "devDependencies": {
    "@babel/core": "^7.24.3",
    "@types/react": "~18.2.45",
    "autoprefixer": "^10.4.19",
    "jest": "^29.2.1",
    "jest-expo": "~51.0.1",
    "postcss": "^8.4.38",
    "react-test-renderer": "18.2.0",
    "tailwindcss": "3.3.2",
    "typescript": "~5.3.3"
  },
  "private": true
}

Thanks for share your devDependencies. Following those versions, works for me

But why this is a problem with expo ~51.x and react-native-web > 17

i am getting this error when applying the recommended solution
Module '"nativewind"' has no exported member 'NativeWindStyleSheet'.

Hi ! I can't use NativeWindStyleSheet with 4.0.36 version. How can I fix this in other ways ? Thanks a lot !

https://www.nativewind.dev/blog#nativewindstylesheet-renamed-to-stylesheet

hi sir, to me i stoped all kinds of css frameworks for react native, now i use only Stylesheet On Nov 1, 2024 2:37 PM, Arne @.***> wrote:
Hi ! I can't use NativeWindStyleSheet with 4.0.36 version. How can I fix this in other ways ? Thanks a lot !
https://www.nativewind.dev/blog#nativewindstylesheet-renamed-to-stylesheet
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

Hi ! I can't use NativeWindStyleSheet with 4.0.36 version. How can I fix this in other ways ? Thanks a lot !

https://www.nativewind.dev/blog#nativewindstylesheet-renamed-to-stylesheet

The setOutput function is deprecated too, if someone has another fix, please share
https://www.nativewind.dev/blog#miscellaneous-updates

In tailwind.config.js change content to:
content: [
'./app//*.{js,jsx,ts,tsx}',
'./components//*.{js,jsx,ts,tsx}'
]
package:
"expo": "~52.0.23",
"nativewind": "^4.1.23",
"tailwindcss": "^3.4.17"


Create Detection Rule with Custom Log Type

We have issues during create detection rule from Security Analytics -> Detection rules -> Create detection rule when using Log type other than provided (sigma). The issues are:

Log Type are changing to ID log, for example: Crowdstrike log will appear as "Mf A Dq 40 B xxxx xxx"
When saving, there are error said: [security_analytics_exception] Invalid rule category "mfadq40bhfu3-v6xlgmp"

How to recreate:

Go to Security Analytics, Detectors, Log types, and create log type
Use newly created log type to create Detection rules
Error happened

We managed to solve the issue by upgrading Amazon Opensearch version to 2.11.


[Bug Report] Carousel Methods: setActiveItem, prev, next cannot be called successfully by child elements which are contained in Carousel-Item

Element UI version
1.4.12
OS/Browsers version
Google Chrome Version 62.0.3202.94
Vue version
2.5.9
Reproduction Link
https://jsfiddle.net/72Lggn9o/
Steps to reproduce
Function setActiveItem cannot be called successfully when the button of "Go First" is in el-carousel-item
What is Expected?
When the button of  "Go First" in el-carousel-item is clicked, the el-carousel will go to next  el-carousel-item
What is actually happening?
Function setActiveItem cannot be called successfully when the button of "Go First" is in el-carousel-item

https://jsfiddle.net/72Lggn9o/2/


Deploy website automatically using CircleCI

The current workflow is to deploy to build the website locally and deploy to the protected gh-pages branch. As a result, only people with write access can update the website.
By moving this to Circle CI, the website will be automatically deployed whenever master is updated, ensuring it is always up to date with the latest changes.
This is actually already implemented on this repo (see https://github.com/facebook/jest/blob/master/circle.yml) but there's some administrative work we need to do on the Facebook side to get this working again (see t15420053).

Fixed.


UI not loading after deployment

After I deployed the webapplication zip file and selected Digital Twin Manager in the app switcher the App is not loading. I only see the turning wheel.
I'm on eu-latest.cumulocity.com
JS console says:
[Error] SyntaxError: Invalid regular expression: invalid group specifier name
(anonymous function) (3119.42aad4d6562079f548eb.js:1)
[Error] Unhandled Promise Rejection: ChunkLoadError: Loading chunk 3119 failed.
(missing: https://mstoffel.eu-latest.cumulocity.com/apps/digital-twin-manager/3119.42aad4d6562079f548eb.js)
generatorResume (bootstrap.53ce2fb8f940af0e7d0a.js:2:109177)
a (bootstrap.53ce2fb8f940af0e7d0a.js:2:4834)
promiseReactionJob

Hi,
Thank you for bringing this to our notice. Can you please share more details like from where you downloaded the DTM artifact( path to the location) and few screenshots showing the steps you tried. This will be very helpful to resolve the issue.

Hi,
I just downloaded the as documented in the readme from the release section:
https://github.com/SoftwareAG/cumulocity-digital-twin-manager/releases/download/1014.0.0/digital-twin-manager.zip
then followed the instructions. I can show you also on my system if your want to.
Regards,
Marco Stoffel

Hi Marco,
Please get in touch with me via teams. I will look into the issue.

Supported browsers in this version are:
Microsoft Edge (latest Chromium-based version)
Mozilla Firefox (latest Extended Support Release)
Google Chrome
Internet Explorer 11
We will update you once we support safari browser.


Modify documentation

[x] Remove redundant code blocks
[x] Fix references

Related #398

Thank you @PipKat  for the review and suggestions.

@dipinknair - try and have a look at the failing workflows


wrong canvas size

the rect that is under the rendered SVG has a wrong size
https://github.com/chrvadala/react-svg-pan-zoom/blob/master/src/viewer.js#L229-L230

solved with v2.2.1


Remove linq

helps with https://github.com/dotnet/SqlClient/issues/1942
Removes all uses of linq operations in the main binary and addons allowing linq to be trimmed out if no other libraries are using it
I suggest reviewing 1 commit at a time. Some of the enclave stuff is a bit messy and this cleans it up as well as removing the linq.
/cc @kant2002

@David-Engel
Is there someone knowledgeable about enclave stuff in the codebase that could help here. I've found something odd that concerns me.
There's a piece of code that was using data.Skip(offset).Take(count) and i replaced it with a function call that does the same thing without using linq. My replacement differs in behaviour by requiring that you be able to copy exactly count bytes where the linq Take function will only copy up-to count bytes, if there aren't enough it won't fail.
This caused failures in this code:
int secureSessionBufferSize = Convert.ToInt32(secureSessionInfoResponseSize) - sizeof(uint);
byte[] secureSessionBuffer = attestationInfo.Skip(offset).Take(secureSessionBufferSize).ToArray();
EnclaveDHInfo = new EnclaveDiffieHellmanInfo(secureSessionBuffer);
offset += Convert.ToInt32(EnclaveDHInfo.Size);

if (secureSessionBufferSize != secureSessionBuffer.Length)
{
	throw new InvalidOperationException($"enclave data mismatch, expected {secureSessionBufferSize} got {EnclaveDHInfo.Size}");
}

Where we calculate how many bytes of data we expect to get and then try to take it and end up 4 bytes short. Either the calculation of how many bytes we should expect to get is wrong or the something else is going on.

@Wraith2 what kind of size reduction are you seeing with this?

I also think it's unlikely to help if sqlclient is used through EFCore because there's no way that linq is getting trimmed from EFCore.

I'm sure that's true; EF hasn't yet undergone a real trimming effort - it's possible (thought not sure) that when we do that in a serious way, LINQ would be needed.
But I'd assume that various dependencies of SqlClient are also bringing in LINQ (e.g. the Azure Identity libs). Personally, for cases where removing LINQ makes the code less maintainable, I'd avoid doing that until I see it provides a tangible gain (but I also think there are at least some cases in this PR where the code doesn't become less maintainable).

Agreed. I was talking with kant on discord about this and it's possible that the azure libs will be trimmable in future if you can work out the api to do so.
If a total removal isn't appropriate certain parts of this can be backed out. There's plenty of scope for discussion and this is only a draft.

I was talking with kant on discord about this and it's possible that the azure libs will be trimmable in future if you can work out the api to do so.

I'd propose thinking about the approach we've taken in Npgsql (https://github.com/dotnet/SqlClient/issues/1942#issuecomment-1455106580): a "slim" data source builder which, when used, doesn't have size-expensive functionality on by default, unless explicitly opted into.
However, specifically regarding the Azure libs, the very fact that SqlClient has a direct references on them is probably not ideal (#1108, highest-voted issue on the repo). Here specifically, I'd suggest SqlClient expose an auth API that allows 3rd-party packages (like the Azure ones) to register themselves. This would totally decouple SqlClient from Azure, and of course naturally strip them away size-wise unless used.

As long as backwards compatibility is maintained adding new apis around the DataSource abstraction seems fine to me. That could allow both advanced AE and Enclave functionality as well as extended authentication mechanisms to be trimmable.

Is there someone knowledgeable about enclave stuff in the codebase that could help here. I've found something odd that concerns me.
There's a piece of code that was using data.Skip(offset).Take(count) and i replaced it with a function call that does the same thing without using linq. My replacement differs in behaviour by requiring that you be able to copy exactly count bytes where the linq Take function will only copy up-to count bytes, if there aren't enough it won't fail.
This caused failures in this code:
int secureSessionBufferSize = Convert.ToInt32(secureSessionInfoResponseSize) - sizeof(uint);
byte[] secureSessionBuffer = attestationInfo.Skip(offset).Take(secureSessionBufferSize).ToArray();
EnclaveDHInfo = new EnclaveDiffieHellmanInfo(secureSessionBuffer);
offset += Convert.ToInt32(EnclaveDHInfo.Size);

if (secureSessionBufferSize != secureSessionBuffer.Length)
{
	throw new InvalidOperationException($"enclave data mismatch, expected {secureSessionBufferSize} got {EnclaveDHInfo.Size}");
}

Where we calculate how many bytes of data we expect to get and then try to take it and end up 4 bytes short. Either the calculation of how many bytes we should expect to get is wrong or the something else is going on.

@Wraith2
This doesn't fail outside of your PR, right? Wouldn't the original exception throw if there was some underlying issue with the original code? I've been looking at the code changes and I'd have to debug it to get a better idea of what might be happening but it feels like something is missing. I need to find an enclave environment set up to debug against. The team has just been horribly busy with support issues for the last month or so...

It isn't a failure outside my PR. I think because while the length calculations are incorrect it isn't meaningful and the code actually does the right thing.
This is the original code:
                    uint secureSessionInfoResponseSize = BitConverter.ToUInt32(attestationInfo, offset);
                    offset += sizeof(uint);

                    SessionId = BitConverter.ToInt64(attestationInfo, offset);
                    offset += sizeof(long);

                    int secureSessionBufferSize = Convert.ToInt32(secureSessionInfoResponseSize) - sizeof(uint);
                    byte[] secureSessionBuffer = attestationInfo.Skip(offset).Take(secureSessionBufferSize).ToArray();
                    EnclaveDHInfo = new EnclaveDiffieHellmanInfo(secureSessionBuffer);
                    offset += Convert.ToInt32(EnclaveDHInfo.Size);

I think the sessionId which is read as sizeof(long) is incorrectly subtracted from the remaining bytes as sizeof(uint) but since we've actually read 8 bytes and advanced by 8 bytes we're just calculating the remaining length incorrectly. When we do Skip(offset).Take(length) the length is 4 bytes longer than we have available but the offset is correct and the lazy behaviour of Take causes it to turn out correct.
So if the code is working should I change it? I think so. I think it should be changed because the comment above the function we're looking at doesn't accurately express what the code is doing and because the code is working accidentally. As I've proven if you try to change it you risk breaking it by interpreting the code and not carefully inspecting the results in a debugger. Since the only way to debug this is complex and requires enclave functionality to be available I think code would be better.

@Wraith2
Looking at the JDBC implementation, I think the existing code is just failing to account for an additional size field after the Session ID, which is not accounted for in the secureSessionInfoResponseSize when calculating the secureSessionBufferSize.
JDBC reference
You're right. It's an error, but one that fortunately works itself out due to the Take() behavior.
int secureSessionBufferSize = Convert.ToInt32(secureSessionInfoResponseSize) - sizeof(uint);

should be
// Account for 4 byte size of enclave ECDH public key followed by 4 byte size of the DH public key signature
int secureSessionBufferSize = Convert.ToInt32(secureSessionInfoResponseSize) - sizeof(uint) - sizeof(uint);

I still haven't debugged, so let me know if that works out correctly. 😄

I revised the code but the CI is apparently off for the weekend already.

We just merged https://github.com/dotnet/SqlClient/pull/1943 and it created a small merge conflict with the namespace.  Let us know if you would like us to push changes to your PR branch or if you have moment to fix it. Thanks!

conflicts resolved and pushed.


Fixed keys for user reporting mechanism

The keys for the user reporting mechanism had the values unreachable, broken and parked nested under ok (which pertains to successful measurements), which is not accurate.
This PR removes the unreachable value (which generally qualifies under blocked, but we already have more specific values under blocked), and creates nested values (including parked) under broken.

Related https://github.com/ooni/api/pull/322


Any way to run clair against a directory

Is there any way to run clair against an already unpacked container in directory? (it looks like even command-line tools like klar and hyperclair use docker API, right?
It may be useful with containers alternative to docker and rkt. For example: systemd-nspawn, lxc,  and bare virtual machines.
At a glance, it looks like it's easy to do because clair unpacks containers anyway and check the folder for vulnerabilities. So only a command-line is needed.
Am I missing something? Will such PR be accepted if it needs to be implemented?

hyperclair use in fact docker api but for lac image, it extract it as a
tarball into a folder that will be pulled later on by Clair, so we could
adapt the get directly the tarball from your layers
On Wed, Sep 28, 2016, 17:47 Paul Colomiets<EMAIL_ADDRESS>wrote:

Is there any way to run clair against an already unpacked container in
directory? (it looks like even command-line tools like klar and hyperclair
use docker API, right?
It may be useful with containers alternative to docker and rkt. For
example: systemd-nspawn, lxc, and bare virtual machines.
At a glance, it looks like it's easy to do because clair unpacks
containers anyway and check the folder for vulnerabilities. So only a
command-line is needed.
Am I missing something? Will such PR be accepted if it needs to be
implemented?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/coreos/clair/issues/250, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADJrq71WTYU_9CMJYWIM-AOsP1ic-im3ks5quowMgaJpZM4KI_Ps
.

@jgsqware that sounds promising. Is there a command-line flag for that? Or should I open an issue in hyperclair?

hyperclair will be integrated in clqir project so we can keep this issue.
need to think how to implement it.
On Wed, Sep 28, 2016, 18:05 Paul Colomiets<EMAIL_ADDRESS>wrote:

@jgsqware https://github.com/jgsqware that sounds promising. Is there a
command-line flag for that? Or should I open an issue in hyperclair?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/coreos/clair/issues/250#issuecomment-250214033, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADJrq6nbsBUPw4u6U6_eavR2g7QWYfi1ks5qupBRgaJpZM4KI_Ps
.

closing due to age. please remake this issue if it's still relevant. thanks


Old PHP versions are not available for download

brew config output
HOMEBREW_VERSION: 3.3.7
ORIGIN: https://github.com/Homebrew/brew
HEAD: dbec9de77ebc65a4845a5e672950219aa19b35b8
Last commit: 2 days ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: e352733090220abeace9f505412b5379ae07fbd2
Core tap last commit: 63 minutes ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_CORE_GIT_REMOTE: https://github.com/Homebrew/homebrew-core
HOMEBREW_MAKE_JOBS: 8
Homebrew Ruby: 2.6.8 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.8/bin/ruby
CPU: octa-core 64-bit kabylake
Clang: 12.0.5 build 1205
Git: 2.30.1 => /Library/Developer/CommandLineTools/usr/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 11.5.1-x86_64
CLT: <IP_ADDRESS>.1.1623191612
Xcode: N/A

brew doctor output
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: A newer Command Line Tools release is available.
Update them from Software Update in System Preferences or run:
  softwareupdate --all --install --force

If that doesn't show you any updates, run:
  sudo rm -rf /Library/Developer/CommandLineTools
  sudo xcode-select --install

Alternatively, manually download them from:
  https://developer.apple.com/download/all/.
You should download the Command Line Tools for Xcode 13.1.

Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
  elasticsearch
<EMAIL_ADDRESS>
Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause formulae that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
  kubernetes-cli

Warning: Homebrew's "sbin" was not found in your PATH but you have installed
formulae that put executables in /usr/local/sbin.
Consider setting your PATH for example like so:
  echo 'export PATH="/usr/local/sbin:$PATH"' >> /Users/corra-158/.bash_profile

Verification

[X] I ran brew update and am still able to reproduce my issue.
[X] I have resolved all warnings from brew doctor and that did not fix my problem.

What were you trying to do (and why)?
I'm not able to install old versions of php. They are  showing either disabled or depricated. eg: brew install<EMAIL_ADDRESS>Earlier I was able to download older versions too
What happened (include all command output)?
It shows Error<EMAIL_ADDRESS>has been disabled because it is deprecated upstream!
What did you expect to happen?
I'm expecting brew to allow me to download any version if its a valid formula (even if its deprecated)
Step-by-step reproduction instructions (by running brew commands)
brew install<EMAIL_ADDRESS>

We only carry formulae that are maintained. See https://docs.brew.sh/Acceptable-Formulae.
If you need Php 7.2, you can use brew extract to maintain a copy of it in your own tap. Here are some docs to help you get started:
https://docs.brew.sh/Taps
https://docs.brew.sh/Interesting-Taps-and-Forks
https://docs.brew.sh/How-to-Create-and-Maintain-a-Tap
https://brew.sh/2020/11/18/homebrew-tap-with-bottles-uploaded-to-github-releases/


Restore Opus support

Is your feature request related to a problem? Please describe.
Using 1.0.4 firmware doesn't work.
Websocket connection + device can't depend on each other state.
We need to store a preferences value with the codec the device has, by default it should be pcm8, which is the one all users use rn.
If the user connects with "opus" codec, the app should show a dialog that asks for restarting the app.
It's not optional.
Then, we set the preferences value to opus, and the websocket now acts accordingly.

Fixed on PR #513


Updates to readme

Used doc content from customer-facing CDA Client doc in some sections. Updated formatting in other sections.
Main changes:

Made content collapsible
Moved "Windows requirements" section into "Build" section
Moved "S3 requirements" section into "Usage" section
Used  for config params
Rest are minor edits.

The changes included in this PR have already been merged in a different PR (#5). Dropping it, hence.


Consider using e.g. VS2022 Test adaptor compatible unit tests

using the latest gdUnit4API TestAdaptor on VS2022

What is the benefit from using this test.
I'm sorry if I'm not understanding you correctly. This is my first time using github issue reporting.

You have written tests.
Imagine using these tests from within VS2022
Your contributors could add more tests to understand you motivation of doing this project

I am using VS20202. And I can see your point but this plugin only make the editor to show the assigned type on the dictionary.

Anyways since this plugin is only viewable from the editor, its not gonna benefit from using this. Thanks for the suggestion though.


Workaround container networking limitations

Until we setup container networking, make sure containers can talk to other containers when using WithReference. This won't work when using raw strings/urls.

Preview2 mitigation for https://github.com/dotnet/aspire/issues/128

Taking bets on how long this work around will hang around for?

cc @eerhardt This change disables proxyless containers for preview2 until we have more runway to fix the other issues


[ARROW-5127] [Rust] [Parquet] Add page iterator.

Add page iterator.

@andygrove @nevi-me @sunchao Please help to review this.

Codecov Report

Merging #4136 into master will decrease coverage by 6.69%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4136      +/-   ##
==========================================
- Coverage    87.8%   81.11%    -6.7%
==========================================
  Files         745      135     -610
  Lines       91468     9664   -81804
  Branches     1252     1252
==========================================
- Hits        80318     7839   -72479
+ Misses      11033     1708    -9325
  Partials      117      117

Impacted Files
Coverage Δ

js/src/ipc/metadata/json.ts
92.39% <0%> (-4.35%)
:arrow_down:

js/src/ipc/metadata/message.ts
92.99% <0%> (-1.28%)
:arrow_down:

js/src/schema.ts
88.77% <0%> (-1.03%)
:arrow_down:

python/pyarrow/ipc.pxi

cpp/src/arrow/csv/chunker-test.cc

cpp/src/parquet/column_page.h

cpp/src/parquet/bloom_filter-test.cc

cpp/src/arrow/array/builder_decimal.cc

cpp/src/plasma/client.cc

cpp/src/arrow/io/test-common.h

... and 603 more

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 0d6f6d0...54207e4. Read the comment docs.

Merged. Thanks @liurenjie1024 . BTW: in future please name the PR in the format of "ARROW-XXXX: ...", not "[ARROW-XXXX]: ..."

Sure, thanks.


Generate AppImage for Linux

Don't merge this just yet - see below for an issue that needs to be solved first.
This PR, when merged, will compile this application on Travis CI upon each git push, and upload an AppImage.
It tries to mirror 1:1 what the debian pipeline is doing, using the same binaries. So this should not add additional burden to the Atom team. It is merely a self-mounting filesystem image. Think of it as putting the contents of the deb into a self-mounting ISO.
Providing an AppImage would have, among others, these advantages:

Applications packaged as an AppImage can run on many distributions (including Ubuntu, Fedora, openSUSE, CentOS, elementaryOS, Linux Mint, and others)
One app = one file = super simple for users: just download one AppImage file, make it executable, and run
No unpacking or installation necessary
No root needed
No system libraries changed
Works out of the box, no installation of runtimes needed
Optional desktop integration with appimaged
Optional binary delta updates, e.g., for continuous builds (only download the binary diff) using AppImageUpdate
Can optionally GPG2-sign your AppImages (inside the file)
Works on Live ISOs
Can use the same AppImages when dual-booting multiple distributions

Here is an overview of projects that are already distributing upstream-provided, official AppImages.
I need help on the following issue:  What translates the lowercase --create-debian-package to make if (argv.createDebianPackage) in script/build trigger? I think I have added and am calling --create-appimage but I am currently getting

Skipping creating AppImage. Specify the --create-appimage option to create it.

Any help greatly appreciated.
AppImage developers are on #AppImage on irc.freenode.net.

Maybe it would be better to provide this as a .zip which has a .home directory added? Otherwise people might lose their settings or inadvertently break those of an existing system-wide install when running it.. (unless the AppImage can somehow be forced to always use a local neighbor folder as $HOME and not only if the user pre-created it)

@JonasT a .zip provides no advantage over an AppImage. You can unpack an AppImage very easily by running ``--appimage-extract`. The AppImage is an alternative to a system-wide install (e.g, think of someone without root rights who cannot do a system-wide install at all).

@probonopd I think I might not have been clear. The .zip should contain the AppImage in packed form but also an <AppImage>.home folder. Alternatively, I propose that portable Atom should be packaged with a startup script as suggested by you here https://github.com/AppImage/AppImageSpec/issues/4#issuecomment-321091078 which ensures settings are never stored in the regular actual user home.

@JonasT please do not put AppImages into other archives such as zip files as it would entirely defeat the purpose of the format.

I was simply pointing out a potential culprit when the $HOME redirection for portable settings needs to be somehow proactively activated by the user. I don't have any strong opinions on how specifically to solve it

@probonopd Try this for checking --create-appimage:
if (argv.createAppimage) {

There is only uppercase when there is a dash separating words. Like: --create-debian-package: argv.createDebianPackage

Thanks @hultberg. Would never have tried this...

Still running into issues,
  console.log(`Copying icon into "${appimagePackageIconsDirPath}"`)
  fs.copySync(
    path.join(packagedAppPath, 'resources', 'app.asar.unpacked', 'resources', 'atom.png'),
    path.join(appimagePackageIconsDirPath, `${atomExecutableName}.png`)
  )

results in
Error: ENOENT: no such file or directory, stat '/home/travis/build/probonopd/atom/out/atom-1.21.0-dev-e792504-amd64/resources/app.asar.unpacked/resources/atom.png'

Now, I believe to have copied over that code 1:1 from the debian script...

Can someone take this from here?

Our position has not changed since https://github.com/atom/atom/pull/13921

@probonopd Maybe vscode will welcome appimages better. Although I daresay that atom and vscode is ultimately owned by the same company. Was really looking forward to this :(

Why do you think a feature request to "Generate AppImage for Linux" is off-topic @Holyprogrammer?
Your comment really leaves me puzzled:

Was really looking forward to this :(

So why are you marking this as off-topic then, instead of lobbying for it?

Why do you think a feature request to "Generate AppImage for Linux" is off-topic @Holyprogrammer?
Your comment really leaves me puzzled:

Was really looking forward to this :(

So why are you marking this as off-topic then, instead of lobbying for it?

I didn't mark it as off topic. Maybe some mod did it

@probonopd I didn't mark it as off-topic. Can project owners do it too?


[discuss] Having kubewatch cli to control kubewatch daemon

I found in some cases user has a need to reconfigure filters to get what he want to see while kubewatch is still running. What do you think if we add kubewatch cli (like kubectl) in order to control kubewatch daemon ? Some more actions to be considered to declare in kubewatch cli:

start/stop/restart kubewatch daemon
change slack message format
create/list/delete handles, specify handle

@ngtuna After our call, I realize that kubewatch main feature is processing event real time. If we change kubewatch to server/client model, then each client run will spawn an EventLoop instead of server spawned at start time in current implementation.

close as it's out of scope


Version bumps for v5.0.2

Version bumps for v5.0.2

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.703%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1258

Relevant Lines:
1453

💛  - Coveralls


Create Lightening Talk

@thisMagpie wrong repository, this should go to https://gitlab.com/sils/guadec-gsoc-presentations . I'll do it manually in an hour or so...


cannot call mutating function with immutable 'this'

I get
./src/Vector.delta:17:24: error: cannot call mutating function with immutable 'this'
      array.append(*arr[e]);
                       ^

for
init(arr : Vector<T>&) {
    this.array = Array<T>();

    for (e in 0..array.size()) {
      array.append(*arr[e]);
    }
  }

Even though this should be mutable in the constructor

Thanks! The error message refers to the [] operator of your Vector class, not the append() method, so it's actually correct. But I agree that the error message is a bit misleading here. 0eb01030b78a5a644b8551fcca080c67db6ecbb7 improves it so it's now:
./src/Vector.delta:17:24: error: cannot call mutating function 'Vector.[]' on immutable receiver
      array.append(*arr[e]);
                       ^


Continue working on Github Actions

Continue working on Github Actions

I commented with a "suggestion" code block. It should have a button on the comment that you can apply directly.
export doesn't work since each run gets its own subshell.
If need be you can affect the environment dynamically by following https://docs.github.com/en/actions/reference/workflow-commands-for-github-actions#setting-an-environment-variable
But in this case we can just use the "env" syntax of passing environment on the commandline before the command.
The | lets us give it a multiline string.
I guess a similar change is needed for the build step.

fixed in #2143


Text & images horizontal alignment is not working.

PHP Version
PHP 8.2
Shopware Version
Shopware <IP_ADDRESS>
Affected area / extension
Platform(Default)
Expected behaviour
If the horizontal alignment is set, the alinment should get displayed like so (edited in browser dev mode):

Actual behaviour
Horizontal alignment is not working for the image text elements, and upright images are not resized properly.
Here an image for the horizontal alignment (is set to right):

DEV Info:

the class justify-content-end is set, but the style isn't.

How to reproduce
Using a Image - Text element with following configuration:

Image with a upright image
Display mode: Standard
Horizontal align: right

-> Then resize the Storefront

[public] Automated response: This issue is linked to the internal issue  https://shopware.atlassian.net/browse/NEXT-38030 Pending  .
[created from NEXT-38030, comment 489654]


base16 colorscheme

Hi,
I'm using the base16 color schemes in my terminal so I made a custom theme for Rainbowstream.
Screenshot on Imgur
If you like it, maybe it can be included.
Anyways, thank you for making this Twitter client, it is absolutely awesome!

👍


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-28-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4300

Questions ?
Please refer to the Backport tool documentation


🐛 zoom props doesn't work properly with camera formats of specified resolution

What's happening?
When setting the zoom to a value other than 1 and combining it with specified camera formats and resolutions, as described in the reproducible code section, the preview results in a black screen.
Reproduceable Code
Modify the example app as
const format = useCameraFormat(device, [
  { fps: targetFps },
  { videoAspectRatio: screenAspectRatio },
  { videoResolution: { width: 1920, height: 1080 } }, // it was 'max' before
  { photoAspectRatio: screenAspectRatio },
  { photoResolution: { width: 1920, height: 1080 } }, // it was 'max' before
])

Then set zoom value as any other value than 1, for example
<Camera zoom={1.5} {...otherProps} />

Relevant log output
[unknown/unknown: Error Domain=AVFoundationErrorDomain Code=-11819 "Cannot Complete Action" UserInfo={NSLocalizedDescription=Cannot Complete Action, NSLocalizedRecoverySuggestion=Try again later.}]

Camera Device
{
  "supportsLowLightBoost": false,
  "isMultiCam": false,
  "hasTorch": true,
  "id": "com.apple.avfoundation.avcapturedevice.built-in_video:0",
  "sensorOrientation": "landscape-right",
  "hasFlash": true,
  "name": "Back Camera",
  "minZoom": 1,
  "supportsFocus": true,
  "physicalDevices": [
    "wide-angle-camera"
  ],
  "supportsRawCapture": false,
  "neutralZoom": 1,
  "maxZoom": 121.875,
  "hardwareLevel": "full",
  "position": "back"
}

Device
iPhone 13 (iOS 16.6.1)
VisionCamera Version
3.6.8
Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information

[ ] I am using Expo
[X] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

#2310 #2280 These issues can have the same cause. Please check if you described the camera format with specified resolution vaules.

Lol, this is a fun one. I'll dig around the Apple forums to see why this is happening after I fix the Preview stretching issue - thanks for the bug report @bglgwyng !

Yes, the problem still exists.

From a post in the apple developer forums:

And someone on Stackoverflow said this might be the stopRunning method timing out, but we are not using that in this scenario I think (that's why the logs would've been useful and why I always ask for logs btw 😉) but yea I think we're not using stopRunning here right?

@mrousavy Is this reported behavior reproduced on your device?
I just tested it and I found that my previous description was a bit misleading.
There's no crash and no black screen problem, but the frame rates get so low(about 1 frame in 3 seconds).

No, I haven't seen that issue before - sorry :/
Let's keep it open tho, but honestly not sure if there's anything I can do.

Lol, this is a fun one. I'll dig around the Apple forums to see why this is happening after I fix the Preview stretching issue - thanks for the bug report @bglgwyng !

Hi @mrousavy and a big thanks for the amazing job on this lib
I see you mention a Preview stretching issue that I cant find any issues about but am experiencing too on 3.8.2. Do you have any progress on that?

Yes, there are like 6 issues about that and in the latest 3.9. beta release I fixed it.

Hey - I think this issue has been fixed in VisionCamera 4.0.0. 🥳
Please try V4 and let me know if you still experience this issue;

if not, please consider 💖 sponsoring me on GitHub 💖 to support the development of VisionCamera and thank me for my time spent on fixing bugs and building new features.
if you still see this issue, please comment and we can re-open this. But please update your native logs with the native (Xcode/Android Studio) logs from running VisionCamera V4 so I can investigate this.


pyfes for python 3.11

Could it be possible to have an anaconda release for python 3.11 ?
Regards

The latest version of the library is compatible with Python 3.11. You can install it using Conda.


fix type annotation of inherit_config function

for issue #138

thank, I'll do a new release soon.

thanks a lot for contributing. This should now be released.


Error while reuploading the file with the same name for the resource

Cloudstorage isnt uploading a file with the same name twice for a resource on azure storage as it says that the blob already exists.
Acceptance

[ ] Reuploading the resource through UI while editing a resource works without errors

Tasks

[ ] Debug the cause and apply the necessary fix

Steps to replicate the error

Create a resource through UI with a file uploaded (say abc.csv)
Once created, edit the resource and reupload the same file and you should be able to see the error pasted below in the Analysis section

Analysis
The following error can be seen in the traceback
2022-02-09 11:21:52,271 ERROR [ckan.config.middleware.flask_app] The specified blob already exists.
ckan-dev_1    | RequestId:73df0e7b-801e-006c-6ea7-1d09f0000000
ckan-dev_1    | Time:2022-02-09T11:21:52.2859241Z
ckan-dev_1    | ErrorCode:BlobAlreadyExists
ckan-dev_1    | Error:None
ckan-dev_1    | Content: <?xml version="1.0" encoding="utf-8"?><Error>BlobAlreadyExists<Message>The specified blob already exists.
ckan-dev_1    | RequestId:73df0e7b-801e-006c-6ea7-1d09f0000000
ckan-dev_1    | Time:2022-02-09T11:21:52.2859241Z</Message></Error>
ckan-dev_1    | Traceback (most recent call last):
ckan-dev_1    |   File "/usr/lib/python3.9/site-packages/azure/storage/blob/_upload_helpers.py", line 94, in upload_block_blob
ckan-dev_1    |     return client.upload(
ckan-dev_1    |   File "/usr/lib/python3.9/site-packages/azure/storage/blob/_generated/operations/_block_blob_operations.py", line 212, in upload
ckan-dev_1    |     raise models.StorageErrorException(response, self._deserialize)
ckan-dev_1    | azure.storage.blob._generated.models._models_py3.StorageErrorException: Operation returned an invalid status 'The specified blob already exists.'
ckan-dev_1    | Content: <?xml version="1.0" encoding="utf-8"?><Error>BlobAlreadyExists<Message>The specified blob already exists.
ckan-dev_1    | RequestId:73df0e7b-801e-006c-6ea7-1d09f0000000
ckan-dev_1    | Time:2022-02-09T11:21:52.2859241Z</Message></Error>
ckan-dev_1    |
ckan-dev_1    | During handling of the above exception, another exception occurred:
ckan-dev_1    |
ckan-dev_1    | Traceback (most recent call last):
ckan-dev_1    |   File "/usr/lib/python3.9/site-packages/flask/app.py", line 1516, in full_dispatch_request
ckan-dev_1    |     rv = self.dispatch_request()
ckan-dev_1    |   File "/usr/lib/python3.9/site-packages/flask/app.py", line 1502, in dispatch_request
ckan-dev_1    |     return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
ckan-dev_1    |   File "/usr/lib/python3.9/site-packages/flask/views.py", line 84, in view
ckan-dev_1    |     return current_app.ensure_sync(self.dispatch_request)(*args, **kwargs)
ckan-dev_1    |   File "/usr/lib/python3.9/site-packages/flask/views.py", line 158, in dispatch_request
ckan-dev_1    |     return current_app.ensure_sync(meth)(*args, **kwargs)
ckan-dev_1    |   File "/srv/app/src/ckan/ckan/config/middleware/../../views/resource.py", line 371, in post
ckan-dev_1    |     get_action(u'resource_update')(context, data)
ckan-dev_1    |   File "/srv/app/src/ckan/ckan/logic/__init__.py", line 504, in wrapped
ckan-dev_1    |     result = _action(context, data_dict, **kw)
ckan-dev_1    |   File "/srv/app/src/ckan/ckan/logic/action/update.py", line 107, in resource_update
ckan-dev_1    |     updated_pkg_dict = _get_action('package_update')(context, pkg_dict)
ckan-dev_1    |   File "/srv/app/src/ckan/ckan/logic/__init__.py", line 504, in wrapped
ckan-dev_1    |     result = _action(context, data_dict, **kw)
ckan-dev_1    |   File "/srv/app/src/ckan/ckan/logic/action/update.py", line 332, in package_update
ckan-dev_1    |     upload.upload(resource['id'], uploader.get_max_resource_size())
ckan-dev_1    |   File "/srv/app/src/ckanext-cloudstorage/ckanext/cloudstorage/storage.py", line 322, in upload
ckan-dev_1    |     blob_client.upload_blob(stream)
ckan-dev_1    |   File "/usr/lib/python3.9/site-packages/azure/core/tracing/decorator.py", line 83, in wrapper_use_tracer
ckan-dev_1    |     return func(*args, **kwargs)
ckan-dev_1    |   File "/usr/lib/python3.9/site-packages/azure/storage/blob/_blob_client.py", line 496, in upload_blob
ckan-dev_1    |     return upload_block_blob(**options)
ckan-dev_1    |   File "/usr/lib/python3.9/site-packages/azure/storage/blob/_upload_helpers.py", line 153, in upload_block_blob
ckan-dev_1    |     process_storage_error(error)
ckan-dev_1    |   File "/usr/lib/python3.9/site-packages/azure/storage/blob/_shared/response_handlers.py", line 147, in process_storage_error
ckan-dev_1    |     raise error
ckan-dev_1    | azure.core.exceptions.ResourceExistsError: The specified blob already exists.
ckan-dev_1    | RequestId:73df0e7b-801e-006c-6ea7-1d09f0000000
ckan-dev_1    | Time:2022-02-09T11:21:52.2859241Z
ckan-dev_1    | ErrorCode:BlobAlreadyExists
ckan-dev_1    | Error:None
ckan-dev_1    | Content: <?xml version="1.0" encoding="utf-8"?><Error>BlobAlreadyExists<Message>The specified blob already exists.
ckan-dev_1    | RequestId:73df0e7b-801e-006c-6ea7-1d09f0000000
ckan-dev_1    | Time:2022-02-09T11:21:52.2859241Z</Message></Error>
ckan-dev_1    | 2022-02-09 11:21:52,341 INFO  [ckan.config.middleware.flask_app]  500 /dataset/test-dataset-local-dev/resource/45f849c0-c817-49c0-8300-055cc48adf7a/edit render time 0.543 seconds

It works fine when we edit the resource with a different file upload but fails with the above error for the same file name.

I think both issues are # 1 related to the same cause.

Yes, both seem related.


Skill - LiquidOoze

If a unit would attempt to steal HP from a unit with this skill, they lose as much instead.
However, they cannot fall below 1 HP.

can they properly cooperate with devil related skills

can they work properly with nosferatu banim

Will have to look into this later to be sure.

I hacked Nosferatu onto Vigarde as the debug chapter doesn't have any magic units, so I didn't see the magic animation play. But it did correctly drain HP from the attacking unit on the map animation.

I think I can make this cleaner anyway. I'll get to it when I get time.

After hours of investigation I'm honestly pretty stumped. It surprises me how hard it is to handle both the HPSTEAL and DEVIL effects simultaneously. I keep running into an issue where the LiquidOoze skill holder's HP keeps increasing past the cap (presumably up to the 255 limit on the byte value) before switching to the Nosferatu user (who's HP does correctly decrease).

I think this skill effect has done on testing?

Not sure what that means?

well I this this skill may be eable to be merged?

Oh okay, so do I just remove the skill effect and let you handle it?

I think this PR has been fine till merge?

well the skill effect failed to deal damage on defender when it is activated.

That isn't the case. The defender (Nosferatu user) does indeed take damage. As you can see in this video.
The attacker (LiquidOoze skillholder) also takes damage as well. I can work around that by making the skill check for LiquidOoze just before damage is dealt to the attacker, but I still have the issue with the increasing HP bar I can't solve.
Honestly all I could think to do was forcibly disable battle animations for the skill, so if you can think of something else it's all yours.
https://github.com/user-attachments/assets/88769f71-5878-4a06-ac53-06b052876f2d

If attacker does not use Nosferatu but a simple hp-drain (which has been change to devil), attacker may not cause damage to defender. Well their still have other problems. I think you can pull the skill info first


Chef::Recipe include_recipe stubbing

I'm submitting this mostly to request some feedback. This feature provides a stub_include_recipe macro which will block a recipe from actually being loaded within the chef-client run, but still allows the recipe to be registered in the list of loaded recipes.
This avoids the issue where you want to test that a recipe was included via include_recipe, but allowing the recipe to be included causes the need to stub out commands, data bag calls, searches, etc. from an external cookbook.
It feels like this more closely resembles the philosophy of unit testing, but as always, I'd appreciate any feedback.
Note:
If the stub_include_recipe macro isn't used, it will throw an error similar to the behavior of the stub_command macro. This breaks a few of the current acceptance tests, which I will gladly fix, if this is deemed useful.

all existing specs with include_recipe will raise stub exception with this. if we want to stub include_recipe at all, we should not enforce it for those who are fine with included recipes being evaluated,

I'm pretty :-1: on this. Chef might be unable to properly build the resource collection if you stub an include_recipe call.  That being said, it's not that complicated:
before do
  allow_any_instance_of(Chef::Recipe).to receive(:include_recipe).and_call_original
  allow_any_instance_of(Chef::Recipe).to receive(:include_recipe).with("cookbook::recipe")
end

@sethvargo the example you provided works, but ends up blocking the run_context from seeing that the recipe was included. This means that something like the following will fail your tests
it 'includes cookbook::recipe' do
  expect(chef_run).to include_recipe('cookbook::recipe')
end

This is what I was attempting to solve. By giving Chef::Recipe it's own include_recipe method (overloading chef/dsl/include_recipe), this should be called within the context of a recipe being parsed for resources, but should not break the run_context's ability to load and parse recipes.
Thanks,
Brandon

@brandocorp
expect_any_instance_of(Chef::Recipe).to receive(:include_recipe).with("cookbook::recipe")

Sadly you can't have the best of both worlds. You either want to include the recipe or you don't IMO. I think the added complexity here is not worth the tradeoff (and re-education for users). If you need to stub recipe inclusion, you should go to the RSpec level. I would definitely welcome a PR to add the stuff I just commented to the README, but I don't think we should support another API method for stubbing this function, as it is not something I'd like to encourage.

Understood. Thanks for the feedback!


Add CONTRIBUTING.md guide

This is the same contributing guide we're using in buildpacks-go. It's mostly a derivative of the Salesforce OSS standard CONTRIBUTING.md.
Readable version without diff.

Closing in favor of #263.


exec: "save-artifacts": executable file not found in $PATH

Using tag 1.0.3. We correctly provide path to s2i scripts and the save-artifacts script is found:
2015-11-18 15:30:58,164 - root - ERROR - I1118 15:30:58.163800 20479 sti.go:198] Using save-artifacts from image:///usr/local/s2i

But later, the container is executed without the absolute path:
2015-11-18 15:30:58,462 - root - ERROR - E1118 15:30:58.461941 20479 util.go:85] exec: "save-artifacts": executable file not found in $PATH

Longer log:
2015-11-18 15:30:55,204 - root - ERROR - I1118 15:30:55.204329 20479 docker.go:211] Image ce-registry.usersys.redhat.com/jboss-eap-6/eap64-openshift:1.2 available locally
2015-11-18 15:30:55,216 - root - ERROR - I1118 15:30:55.216186 20479 docker.go:211] Image ce-registry.usersys.redhat.com/jboss-eap-6/eap64-openshift:1.2 available locally
2015-11-18 15:30:55,233 - root - ERROR - I1118 15:30:55.232227 20479 sti.go:123] Preparing to build integ-ce-registry.usersys.redhat.com/jboss-eap-6/eap64-openshift:1.2
2015-11-18 15:30:55,233 - root - ERROR - I1118 15:30:55.232811 20479 clone.go:28] Cloning into /tmp/sti686419731/upload/tmp
2015-11-18 15:30:58,139 - root - ERROR - I1118 15:30:58.139659 20479 fs.go:99] Removing directory '/tmp/sti686419731/upload/src'
2015-11-18 15:30:58,140 - root - ERROR - I1118 15:30:58.139791 20479 fs.go:93] cp -a /tmp/sti686419731/upload/tmp/helloworld/. /tmp/sti686419731/upload/src
2015-11-18 15:30:58,152 - root - ERROR - I1118 15:30:58.151321 20479 fs.go:99] Removing directory '/tmp/sti686419731/upload/tmp'
2015-11-18 15:30:58,161 - root - ERROR - I1118 15:30:58.161396 20479 docker.go:211] Image ce-registry.usersys.redhat.com/jboss-eap-6/eap64-openshift:1.2 available locally
2015-11-18 15:30:58,161 - root - ERROR - I1118 15:30:58.161411 20479 docker.go:317] Image contains io.openshift.s2i.scripts-url set to 'image:///usr/local/s2i'
2015-11-18 15:30:58,161 - root - ERROR - I1118 15:30:58.161426 20479 download.go:57] Using image internal scripts from: image:///usr/local/s2i/assemble
2015-11-18 15:30:58,162 - root - ERROR - I1118 15:30:58.161436 20479 download.go:57] Using image internal scripts from: image:///usr/local/s2i/run
2015-11-18 15:30:58,163 - root - ERROR - I1118 15:30:58.163754 20479 docker.go:211] Image ce-registry.usersys.redhat.com/jboss-eap-6/eap64-openshift:1.2 available locally
2015-11-18 15:30:58,164 - root - ERROR - I1118 15:30:58.163767 20479 docker.go:317] Image contains io.openshift.s2i.scripts-url set to 'image:///usr/local/s2i'
2015-11-18 15:30:58,164 - root - ERROR - I1118 15:30:58.163783 20479 download.go:57] Using image internal scripts from: image:///usr/local/s2i/save-artifacts
2015-11-18 15:30:58,164 - root - ERROR - I1118 15:30:58.163790 20479 sti.go:198] Using assemble from image:///usr/local/s2i
2015-11-18 15:30:58,164 - root - ERROR - I1118 15:30:58.163797 20479 sti.go:198] Using run from image:///usr/local/s2i
2015-11-18 15:30:58,164 - root - ERROR - I1118 15:30:58.163800 20479 sti.go:198] Using save-artifacts from image:///usr/local/s2i
2015-11-18 15:30:58,164 - root - ERROR - I1118 15:30:58.163817 20479 ignore.go:58] .s2iignore file does not exist
2015-11-18 15:30:58,168 - root - ERROR - I1118 15:30:58.168154 20479 sti.go:129] Existing image for tag integ-ce-registry.usersys.redhat.com/jboss-eap-6/eap64-openshift:1.2 detected for incremental build
2015-11-18 15:30:58,168 - root - ERROR - I1118 15:30:58.168169 20479 sti.go:134] Performing source build from https://github.com/jboss-openshift/openshift-examples
2015-11-18 15:30:58,168 - root - ERROR - I1118 15:30:58.168289 20479 sti.go:316] Saving build artifacts from image integ-ce-registry.usersys.redhat.com/jboss-eap-6/eap64-openshift:1.2 to path /tmp/sti686419731/upload/artifacts
2015-11-18 15:30:58,173 - root - ERROR - W1118 15:30:58.172939 20479 docker.go:315] Image does not contain a value for the io.openshift.s2i.scripts-url label
2015-11-18 15:30:58,173 - root - ERROR - I1118 15:30:58.172958 20479 docker.go:370] Base directory for STI scripts is ''. Untarring destination is '/tmp'.
2015-11-18 15:30:58,173 - root - ERROR - I1118 15:30:58.172998 20479 docker.go:497] Creating container using config: {Hostname: Domainname: User: Memory:0 MemorySwap:0 CPUShares:0 CPUSet: AttachStdin:false AttachStdout:true AttachStderr:false PortSpecs:[] ExposedPorts:map[] Tty:false OpenStdin:false StdinOnce:false Env:[] Cmd:[save-artifacts] DNS:[] Image:integ-ce-registry.usersys.redhat.com/jboss-eap-6/eap64-openshift:1.2 Volumes:map[] VolumesFrom: WorkingDir: MacAddress: Entrypoint:[] NetworkDisabled:false SecurityOpts:[] OnBuild:[] Labels:map[]}
2015-11-18 15:30:58,288 - root - ERROR - I1118 15:30:58.288375 20479 docker.go:508] Attaching to container
2015-11-18 15:30:58,289 - root - ERROR - I1118 15:30:58.289125 20479 docker.go:514] Starting container
2015-11-18 15:30:58,462 - root - ERROR - E1118 15:30:58.461941 20479 util.go:85] exec: "save-artifacts": executable file not found in $PATH
2015-11-18 15:31:04,272 - root - ERROR - W1118 15:31:04.272329 20479 sti.go:137] Clean build will be performed because of error saving previous build artifacts
2015-11-18 15:31:04,272 - root - ERROR - I1118 15:31:04.272353 20479 sti.go:139] ERROR: API error (404): Cannot start container d5480afebb1f7e45f003b10309468e36b7898204aeb4f8aa60ef2736f8dba598: [8] System error: exec: "save-artifacts": executable file not found in $PATH

how are you providing the save-artifacts script?
please point me to your dockerfile and image directory structure.

I've tested this with an image that defines the script url via a label:
LABEL io.openshift.s2i.scripts-url=image:///usr/libexec/s2i
and it appears to work, and having reviewed the code it should be just trimming the "image://" prefix and then running your command.
however:
Base directory for STI scripts is ''. Untarring destination is '/tmp'.
should have printed out the value of that scripts-url (the ''), which implies we're not finding your label.

Closing this now, since this could be an error on our side - we had a stalled container running on our test machine and it seems it interfered somehow. After killing it and running our test suite again, absolute path to save-artifacts is used again. But of course now we hit #358.


99% or 99.9% percent rule applied per FP32 model or min FP32 accuracy

Let's decide if the rule is still for 99% and/or 99.9% at per model level or min. of all FP32 models per benchmark

The potential choices are min, average, max, or per model.

This was primarily motivated by SSD-ResNet where PyTorch/TF/ONNX accuracies are different. The solution is contained in C++ code in https://meet.google.com/linkredirect?authuser=0&dest=https%3A%2F%2Fgithub.com%2Fmlperf%2Finference%2Fpull%2F659
This needs to be fixed at the benchmark in v0.8.

Delay issues to v0.8

It's likely to be fixed by reimplementing SSD-ResNet.

WG: the current proposal is still using min FP32 accuracy. Let's discuss and finalize next week.

WG: there is no change to the accuracy threshold in v1.0.

WG: there is no change to the accuracy threshold in v1.0.

Hi all, any updates here? will it be the same in v1.1?

Since we passed the Inference freeze deadline, I assume the rule will remain the same. Adding @guschmue @tjablin for comments.


Add @media query for mobile muting UI.

This adds a media query so that the muting UI on mobile displays
correctly.
Fixes: #2149.

Automated message from Dropbox CLA bot
@brockwhittaker, it looks like you've already signed the Dropbox CLA. Thanks!

Merged (after fixing the missing-newline-at-eof issue), thanks @brockwhittaker!


Clarify none background

This PR is based on #944 and the purpose is to clarify the initial value of CURRENT_BG and CURRENT_RIGHT_BG. We now use initial as - well - initial value of these variables. This is why we can get rid of the NONE guards in isSameColor that bailed out if a color NONE was given. Unfortunately our numerical comparison that helps us comparing values like 009 and 9 fails in comparing a numerical value and a string (none). This is why I added a check if one of that given colors is a numerical one, and if so, fall back to a string comparison.
Not sure if this should be included in v0.6.6, or if we should include this in next.

I'm glad you're trying to tackle this, @dritter. The recent issues about color handling remind me a little of some of our early days dealing with fonts, hah.
The none thing not being a numeric code is really annoying. I really don't like checking to see if both colors are numerics before doing the comparison, because most of the time, they will be numerics, so we are injecting two more conditionals per segment into the rendering process. (Just to be clear, this PR doesn't add that - that's been around since we first added support for none).
Not withstanding finding a way to blow away this whole thing entirely, which I don't see an obvious way to do, this seems like a good way to replace the existing conditional pair with two different ones that solve the problem. I'm on-board. If you guys are, too, let's get this staged for v0.6.6.

Hmm. Probably we need that string comparison anyway. Imagine the following cases:

isSameColor 'xxx' 'black': This one should return false, as xxx is not a color in our colors array.
isSameColor 'xxA' 'xxB': This one should return false as well, because two unknown different colors should not be recognised as equal. So, if we compute an "error" integer for them (in getColorCode), they will end up being the same.


Upload first version packages

Pull Request Test Coverage Report for Build 5

118 of 130 (90.77%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-9.2%) to 90.769%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

repository/IngSoft2-Model/DiceCharged.class.st
19
22
86.36%

repository/IngSoft2-Model/Player.class.st
31
40
77.5%

Totals

Change from base Build 3:
-9.2%

Covered Lines:
118

Relevant Lines:
130

💛  - Coveralls


Statistic-to-p conversion can produce infinite values for analytic null

The summary statistic-to-p conversion from histograms can result in infinite values. I assume this is an issue that can be dealt with in the actual conversion, rather than the histograms.
Somewhat similar to #364.

I think the issue is that we fixed null_to_p() but haven't made any corresponding changes for histogram-based conversion. I'm sure that similar fixes could be apply though, perhaps after abstracting the histogram-based stat-to-p conversion out to its own function.

I've got a nullhist_to_p function set up (see below), but I'm not sure what we should use to crop extreme values. The analytic solutions don't have an equivalent to the number of permutations, so we can't use that. I suppose we could do something like add 1 to the last bin (the maximum possible value) so that there no p-values of 0 or inf.
def nullhist_to_p(test_values, histogram_weights, histogram_bins):
    """Return p-value for test value against null histogram.

    Parameters
    ----------
    test_values : (V) array_like
        Values for which to determine p-value.
    histogram_weights : (B [x V]) array
        Histogram weights representing the null distribution against which test_value is compared.
    histogram_bins : (B) array
        Histogram bins

    Returns
    -------
    p_value : :obj:`float`
        P-value associated with the test value when compared against the null
        distribution.
    """
    assert test_values.ndim == 1
    assert histogram_bins.ndim == 1
    assert histogram_weights.shape[0] == histogram_bins.shape[0]
    assert histogram_weights.ndim in (1, 2)
    if histogram_weights.ndim == 2:
        assert histogram_weights.shape[1] == test_values.shape[0]

    n_bins = len(histogram_bins)
    step = histogram_bins[1] - histogram_bins[0]  # assume equal spacing

    # Convert histograms to null distributions.
    null_distribution = histogram_weights / np.sum(histogram_weights, axis=0)
    null_distribution = np.cumsum(null_distribution[::-1, :], axis=0)[::-1, :]
    null_distribution /= np.max(null_distribution, axis=0)

    p_values = np.ones(test_values.shape)
    # Get p-values by getting the binned_values-th value in null_distribution
    if histogram_weights.ndim == 1:
        idx = np.where(test_values > 0)[0]
        binned_values = utils.round2(test_values[idx] * step)
        p_values[idx] = null_distribution[binned_values]
    else:
        binned_values = utils.round2(test_values * step).astype(int)
        binned_values[binned_values > n_bins] = n_bins
        # Pair each test value with its associated null distribution
        for i, (x, y) in enumerate(zip(null_distribution.transpose(), binned_values)):
            p_values[i] = x[y]

    return p_values

I don't know what's conventional for this kind of thing, but I guess I'd lean towards maybe using the mid-point of the bin, rather than the edge. I.e., if a value is in the smallest bin, and the probability of that bin is 0.01, then the mid-point is 0.005, and not 0 or 0.01. But it's worth googling a bit, because there's probably some generally accepted practice.

Ah, but the problem is that the null histogram is converted to a null distribution via a reversed cumulative sum, so it's the last bin with a non-zero weight that determines the maximum summary statistic with a non-zero p-value. My current solution is just to replace p-values of zero in the resulting array with the float epsilon, like we used to for the regular null_to_p before #353.

I guess I'm not sure which of 2 things is going on:

The most extreme bins in the histograms have non-zero probability, but the value we're trying to look up appears to be outside of the range of the histogram.

The target value is within the theoretical range of the histogram, but happens to be more extreme than all of the null values.

If it's the former, then the problem is with the bins, and you would need to extend them in either direction as you proposed, so that they include all possible values. If the latter, then I think we should replace 0 not with epsilon, but with half the step size—i.e., the Nyquist limit. For values smaller than that, we can't determine whether the probability is really 0, or whether it's just very small. But we know that if the value was any larger, it would be rounded up into the next bin, and our result would then be more extreme.

It's definitely the second situation.

If the latter, then I think we should replace 0 not with epsilon, but with half the step size—i.e., the Nyquist limit.

Oh that's a cool solution. I hadn't even considered it. I will update #409!

I thought I understood the proposal, but after trying to implement it I think there's a problem. If we have a null histogram with integer bins (as in typical KDA), then half a step size would be 0.5. I don't think it makes sense to set extremely significant p-values to 0.5.

What about cropping extreme values to the largest observed value in the null distribution?

@tyarkoni any thoughts? Did I misunderstand your proposal or should we use something like the largest observed value?

Sorry, catching up on this thread; my suggestion was indeed bad. I'm still not sure what the optimal solution is, but I like your last suggestion better than any of the above, so let's go with that for the time being.


2 can we support some kind of git sdk instead of using subprocess to call git commands

need unittest, right?


Custodian #322

Action for simulate on Roles, Users, & Groups
Iterates through all resources & reports on provided action(s)
provided as params
Principal policies only

UnitTests

Any thoughts on this... I didn't want to do too much if this isn't what you actually had in mind.

Sorry for the delay, on call crisis for the last few days. In general, yes this is a feature we want. The implementation though is violating the interface contract for a filter as it doesn't return the resources passed in but evaluations.


Update

Update dependencies, please.
Especially ytdl-core.

Can you please specify problems you're having?

Due to outdated ytdl-core some vids throw error: "could not extract signature decipheri
ng actions", specified here.

Thanks, I'll have a look later today.

Merged. Thanks for the pull request.

I also put a new release on NPM (v0.3.6).

Thx.


Change pyslim ref to the new simplification stub

Worth doing especially as builds are failing sometimes when trying to reference pyslim (e.g. https://github.com/tskit-dev/tutorials/commit/def3ea893671d324f46e7bd281d4435f056c6ab3)

What do you think @petrelharp?

(NB - I put the link in there!)

Sorry, I misinterpreted this - we're just replacing a link into the pyslim tutorial not out of it.


AlexNet Top-1 accuracy on test dataset only reach 45% when train with multiple GPUs

Hi, Soumith
I train alexnet with 8 GPUs, and change the batchsize to 1024. After serval days, the top-1 accuracy on test dataset only get 45%, while on a single GPU it can get 55% after the same time. Are there any tricks when train with multiple GPU to get the same test accuracy?
Here's the command and summary:
th main.lua -data ./imagenet/ -nGPU 8 -nDonkeys 28 -batchSize 1024 -netType alexnet
[TRAINING SUMMARY] average loss (per batch): 1.82   accuracy(%):    top-1 55.99
[TESTING SUMMARY] average loss (per batch): 2.39   accuracy Center:   top-1 46.43
Thanks

@yiheng if you increase the batch size to something as large as 1024, the same learning rate / learning rate schedule might not apply. You will have to find different numbers for those parameters.

Hi Soumith
Thanks for your suggestion. I'm trying with different lr / lr decay policy. The combination of the hyperparameters are too many and it takes a while to evaluate... Could you give some guide on how to tune these hypeparameters for a large batch?
And a more basic question, is a larger batch(such as 1024 or 2048) good or bad for minibatch-sgd training in deep learning? Actually we're trying to scale out deep learning to multi-node and the batch size can't be too small or the communication time will domain... Look forward to your views :-)
Thanks

I've seen that
larger batch size ~= harder to find hyperparameters that will converge to the best accuracy.


ARROW-10856: [R] CC and CXX environment variables passing to cmake

Ensure that the environment variables are properly passed to cmake.

@github-actions crossbow submit -g r

@github-actions crossbow submit -g r

@github-actions crossbow submit -g r

@github-actions crossbow submit -g r

@github-actions crossbow submit -g r

@jonkeane you can also select a subset of those jobs to run, or even individual jobs by name, so instead of -g r, you could do test-r-* and that would skip the conda and macos jobs that aren't affected by this change.

@github-actions crossbow submit test-r-rstudio-r-base-3.6-centos*

@github-actions crossbow submit test-r-rstudio-r-base-3.6-centos*

@github-actions crossbow submit test-r-rstudio-r-base-3.6-centos*

@github-actions crossbow submit test-r-rstudio-r-base-3.6-centos*

@github-actions crossbow submit test-r-rstudio-r-base-3.6-centos*

Unfortunately it doesn't look like devtoolset is being used by arrow/R: https://dev.azure.com/ursa-labs/crossbow/_build/results?buildId=21892&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=6c939d89-0d1a-51f2-8b30-091a7a82e98c&l=46
Check in the container what R CMD config CC says. (cf. https://github.com/apache/arrow/blob/master/r/tools/linuxlibs.R#L307-L309) You may need to modify R's Makevars to use the devtoolset versions, or export CC and CXX in the environment that runs the tests (it would be useful to confirm that this still works, for our reference when helping users debug), or something.

@github-actions crossbow submit test-r-rstudio-r-base-3.6-centos*

@github-actions crossbow submit test-r-rstudio-r-base-3.6-centos*

@github-actions crossbow submit test-r-rstudio-r-base-3.6-centos*

@github-actions crossbow submit test-r-rstudio-r-base-3.6-centos*

@github-actions crossbow submit test-r-rstudio-r-base-3.6-centos*

Aaaand it works!
https://dev.azure.com/ursa-labs/crossbow/_build/results?buildId=21985&view=logs&j=0da5d1d9-276d-5173-c4c4-9d4d4ed14fdb&t=6c939d89-0d1a-51f2-8b30-091a7a82e98c&l=24

@github-actions crossbow submit -g r


Async State Subscriptions

Description
This feature implements a state subscription listener engine for all registered state models. Other modules can register callback functions tied to any state commit. The syntax for registering state subscription callbacks is:
class Consumer:
    def __init__(self) -> None:
        self.username = ""
        with State() as state:
            state.subscribe(User, self.update)

    async def update(self, usr: User) -> None:
        self.username = usr.name
...
class Producer:

    def fetch_name(self) -> None:
        name = requests.get()
        with State() as state:
           usr = state.checkout(User)
           usr.name = name
           state.commit(usr)

Issues:
closes #12
Resolutions

[x] Implemented asynchronous state subscriptions
[x] State model hashing bug fixes
[x] Unittests for state subscription handlers

Codecov Report

Merging #15 (789b8bb) into master (47efe59) will increase coverage by 2.09%.
The diff coverage is 73.23%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
+ Coverage   80.36%   82.46%   +2.09%
==========================================
  Files          11       12       +1
  Lines         163      211      +48
  Branches       22       26       +4
==========================================
+ Hits          131      174      +43
- Misses         30       35       +5
  Partials        2        2

Impacted Files
Coverage Δ

myosin/state/state.py
42.30% <30.76%> (-3.53%)
:arrow_down:

myosin/exceptions/state.py
70.00% <66.66%> (-1.43%)
:arrow_down:

myosin/models/base.py
96.66% <100.00%> (+0.23%)
:arrow_up:

myosin/state/ssm.py
100.00% <100.00%> (ø)

myosin/typing/__init__.py
100.00% <100.00%> (ø)

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 47efe59...789b8bb. Read the comment docs.