Support for laravel 5

Where there be support for Laravel 5 ("laravel/framework": "5.0.*@dev") ?
Here's what I get when I try to install your package
±  |master ✗| → composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: remove laravel/framework 5.0.x-dev
    - Conclusion: don't install laravel/framework 5.0.x-dev
    - fintech-fab/laravel-queue-rabbitmq 4.0 requires illuminate/queue 4.0.*@dev -> satisfiable by illuminate/queue[v4.0.0, v4.0.1, v4.0.10, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9].
    - fintech-fab/laravel-queue-rabbitmq 4.1 requires illuminate/queue 4.1.*@dev -> satisfiable by illuminate/queue[v4.1.0, v4.1.1, v4.1.10, v4.1.11, v4.1.12, v4.1.13, v4.1.14, v4.1.15, v4.1.16, v4.1.17, v4.1.18, v4.1.19, v4.1.2, v4.1.20, v4.1.21, v4.1.22, v4.1.23, v4.1.24, v4.1.25, v4.1.26, v4.1.27, v4.1.28, v4.1.29, v4.1.3, v4.1.30, v4.1.4, v4.1.5, v4.1.6, v4.1.7, v4.1.8, v4.1.9].
    - fintech-fab/laravel-queue-rabbitmq 4.2 requires illuminate/queue 4.2.*@dev -> satisfiable by illuminate/queue[v4.2.1, v4.2.12, v4.2.16, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9].
    - fintech-fab/laravel-queue-rabbitmq dev-master requires illuminate/queue 4.2.*@dev -> satisfiable by illuminate/queue[v4.2.1, v4.2.12, v4.2.16, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9].
    - don't install illuminate/queue v4.0.0|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.0.1|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.0.10|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.0.2|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.0.3|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.0.4|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.0.5|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.0.6|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.0.7|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.0.8|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.0.9|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.0|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.1|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.10|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.11|don't install laravel/framework 5.0.x-dev
{
    - don't install illuminate/queue v4.1.12|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.13|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.14|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.15|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.16|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.17|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.18|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.19|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.2|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.20|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.21|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.22|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.23|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.24|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.25|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.26|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.27|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.28|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.29|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.3|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.30|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.4|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.5|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.6|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.7|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.8|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.1.9|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.2.1|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.2.12|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.2.16|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.2.2|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.2.3|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.2.4|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.2.5|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.2.6|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.2.7|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.2.8|don't install laravel/framework 5.0.x-dev
    - don't install illuminate/queue v4.2.9|don't install laravel/framework 5.0.x-dev
    - Installation request for laravel/framework 5.0.*@dev -> satisfiable by laravel/framework[5.0.x-dev].
    - Installation request for fintech-fab/laravel-queue-rabbitmq @dev -> satisfiable by fintech-fab/laravel-queue-rabbitmq[4.0, 4.1, 4.2, dev-master].

It will be available within a week after Laravel 5 will be released
Sent from my iPhone

On 30 Jan 2015, at 01:49, Bardia Afshin<EMAIL_ADDRESS>wrote:
Where there be support for Laravel 5?
Here's what I get when I try to install your package
±  |master ✗| → composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Conclusion: remove laravel/framework 5.0.x-dev
- Conclusion: don't install laravel/framework 5.0.x-dev
- fintech-fab/laravel-queue-rabbitmq 4.0 requires illuminate/queue 4.0.@dev -> satisfiable by illuminate/queue[v4.0.0, v4.0.1, v4.0.10, v4.0.2, v4.0.3, v4.0.4, v4.0.5, v4.0.6, v4.0.7, v4.0.8, v4.0.9].
- fintech-fab/laravel-queue-rabbitmq 4.1 requires illuminate/queue 4.1.@dev -> satisfiable by illuminate/queue[v4.1.0, v4.1.1, v4.1.10, v4.1.11, v4.1.12, v4.1.13, v4.1.14, v4.1.15, v4.1.16, v4.1.17, v4.1.18, v4.1.19, v4.1.2, v4.1.20, v4.1.21, v4.1.22, v4.1.23, v4.1.24, v4.1.25, v4.1.26, v4.1.27, v4.1.28, v4.1.29, v4.1.3, v4.1.30, v4.1.4, v4.1.5, v4.1.6, v4.1.7, v4.1.8, v4.1.9].
- fintech-fab/laravel-queue-rabbitmq 4.2 requires illuminate/queue 4.2.@dev -> satisfiable by illuminate/queue[v4.2.1, v4.2.12, v4.2.16, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9].
- fintech-fab/laravel-queue-rabbitmq dev-master requires illuminate/queue 4.2.@dev -> satisfiable by illuminate/queue[v4.2.1, v4.2.12, v4.2.16, v4.2.2, v4.2.3, v4.2.4, v4.2.5, v4.2.6, v4.2.7, v4.2.8, v4.2.9].
- don't install illuminate/queue v4.0.0|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.0.1|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.0.10|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.0.2|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.0.3|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.0.4|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.0.5|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.0.6|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.0.7|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.0.8|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.0.9|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.0|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.1|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.10|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.11|don't install laravel/framework 5.0.x-dev
{
- don't install illuminate/queue v4.1.12|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.13|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.14|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.15|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.16|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.17|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.18|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.19|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.2|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.20|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.21|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.22|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.23|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.24|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.25|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.26|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.27|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.28|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.29|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.3|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.30|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.4|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.5|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.6|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.7|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.8|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.1.9|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.2.1|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.2.12|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.2.16|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.2.2|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.2.3|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.2.4|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.2.5|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.2.6|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.2.7|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.2.8|don't install laravel/framework 5.0.x-dev
- don't install illuminate/queue v4.2.9|don't install laravel/framework 5.0.x-dev
- Installation request for laravel/framework 5.0.*@dev -> satisfiable by laravel/framework[5.0.x-dev].
- Installation request for fintech-fab/laravel-queue-rabbitmq @dev -> satisfiable by fintech-fab/laravel-queue-rabbitmq[4.0, 4.1, 4.2, dev-master].
—
Reply to this email directly or view it on GitHub.

I see. For requirements purposes, if I was to develop this on top of IronMQ, would there be any major overhaul needed to transition into your RabbitMQ driver?
Or is it as simple as switching over the driver, and voila, magically things work.

Yep, you will just change your queue config and it will start to use rabbit. No other code changes
Sent from my iPhone

On 30 Jan 2015, at 21:02, Bardia Afshin<EMAIL_ADDRESS>wrote:
I see. For requirements purposes, if I was to develop this on top of IronMQ, would there be any major overhaul needed to transition into your RabbitMQ driver?
Or is it as simple as switching over the driver, and voila, magically things work.
—
Reply to this email directly or view it on GitHub.

Laravel5 has been released so it is supported with laravel5 now ? Please . Thanks

I'm using       "videlalvaro/php-amqplib": "2.2.*" to make the rabbitmq connection, I've yet tried to connect via the native way Laravel prefers you doing the queue connection (the queue.php configuration).


Large number of option

Hello,
I'm using bootstra-select with a large number of options (about 30 000 options), so when I initialize it's very slow and when I do livesearch, it's work very slow also. Do you have any idea to run it fast? My list of options is from AJAX call.

The performance issues with large selects have been addressed in v1.13.0, currently in beta. I've moved development of this plugin to a new repo, and v1.13.0-beta can be downloaded here: https://github.com/snapappointments/bootstrap-select/releases/tag/v1.13.0-beta.


add multi-logger support

Of the top of my head, there should be at least Loggers available in the Framework.

Core logger, that is in use by the logger itself,
Slaxer logger, that is in use by the CLI applet,
User logger, that is in use by the user code.

This is only a placeholder ticket, exact way of implementation will be added later. Maybe broken down into multiple issues.

No longer placeholder ticker, detailed issues will be added to Logger repository and will reference this ticket.

Resolved.


Naming of SSL(_CTX)_add1_CA_list

Considering it adds a X509* rather than taking/returning a STACK_OF(X509_NAME), I think the _list suffix should be dropped?
Note: this function is new in OpenSSL 1.1.1: lets get this right before the release!

Yup.  Fixing PR is now submitted


Question about multi-GPU inference

sparsegpt has shown good results in the A100, but for a large number of commercial GPUs, VRAM and computation power are still a big pressure. is there a necessity and idea for multi-GPU inference?

Hi, SparseGPT is only concerned with sparsifying the weights of a given model, which is independent of how it is ultimately sharded for inference; e.g. you could distribute different layers on different GPUs or even shard the same, e.g. 2:4 sparse, layer across multiple devices. Please note that the actual implementation of such multi-GPU distribution is beyond the scope of this project (which is focused on accurate sparsification).


Error finding the mp4 resource

Hey guys, I'm having this issue
Error: undefined Unable to resolve module `../../../assets/videos/background.mp4` from `src/features/auth/SignIn/SignInContainer.js`:

None of these files exist:
  * src/assets/videos/background.mp4(.native|.ios.js|.native.js|.js|.ios.json|.native.json|.json|.ios.ts|.native.ts|.ts|.ios.tsx|.native.tsx|.tsx)
  * src/assets/videos/background.mp4/index(.native|.ios.js|.native.js|.js|.ios.json|.native.json|.json|.ios.ts|.native.ts|.ts|.ios.tsx|.native.tsx|.tsx)

showCompileError
    index.bundle?platform=ios&dev=true&minify=false:43745:26
<unknown>
    index.bundle?platform=ios&dev=true&minify=false:43684:29
emit
    index.bundle?platform=ios&dev=true&minify=false:44176:35
<unknown>
    index.bundle?platform=ios&dev=true&minify=false:44023:23
dispatchEvent
    index.bundle?platform=ios&dev=true&minify=false:41436:31
<unknown>
    index.bundle?platform=ios&dev=true&minify=false:42092:31
emit
    index.bundle?platform=ios&dev=true&minify=false:15863:42
__callFunction
    index.bundle?platform=ios&dev=true&minify=false:11610:49
<unknown>
    index.bundle?platform=ios&dev=true&minify=false:11323:31
__guard
    index.bundle?platform=ios&dev=true&minify=false:11564:15
callFunctionReturnFlushedQueue
    index.bundle?platform=ios&dev=true&minify=false:11322:21
callFunctionReturnFlushedQueue
    [native code]:0

Platform
iOS and Android
Which player are you experiencing the problem on:

iOS
Android ExoPlayer

Environment info
React native info output:
 System:
    OS: macOS 10.15.6
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 160.18 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.15.2 - ~/.nvm/versions/node/v10.15.2/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v10.15.2/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 23, 28, 29, 30
      Build Tools: 23.0.1, 24.0.1, 25.0.1, 26.0.2, 27.0.1, 27.0.3, 28.0.3, 29.0.1, 29.0.2, 29.0.3, 30.0.1, 30.0.2
      System Images: android-28 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-30 | Google Play Intel x86 Atom
  IDEs:
    Android Studio: 4.0 AI-193.69<IP_ADDRESS>26763
    Xcode: 11.6/11E708 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.5 => 0.61.5
  npmGlobalPackages:
    react-native-cli: 2.0.1

Library version: 5.1.1
Steps To Reproduce

yarn add react-native-video
npx pod-install ios
npx react-native run-ios

Any though? Thanks!

I found the solution for it, I was missing the .mp4 format in the metro.config.js file, resolver section. This section was added due to prerequisite for react-viro package.
module.exports = {
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: false,
      },
    }),
  },
  resolver: {
    assetExts: ['obj', 'vrx', 'jpg', 'png', 'mp4'],
  },
};

I found the solution for it, I was missing the .mp4 format in the metro.config.js file, resolver section. This section was added due to prerequisite for react-viro package.
module.exports = {
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: false,
      },
    }),
  },
  resolver: {
    assetExts: ['obj', 'vrx', 'jpg', 'png', 'mp4'],
  },
};

thanks @costerik your solution saved me a ton of debug time!

Im still running into this issue, even after updating the metro config as per above (for sourceExts and assetExts).
Running Expo v51 with next.js/native hybrid app. Works fine in web. Work fine with remot uris. image assets work fine. I have included the "expo-av" in plugins in app.json.
Throws the same error from OP's question when i choose an incorrect path and it cant find the ext. fix the path and its just blank in the app where the video should be.
import React from "react";
import { StyleSheet, View, Platform } from "react-native";
import { Video, ResizeMode, VideoFullscreenUpdate } from "expo-av";
expo-next/app/(routes)/sign-in/components/VideoBackground.tsx

const VideoBackgroundWeb = () => {
  return (
    <video
      autoPlay
      loop
      muted
      playsInline
      style={{
        position: "absolute",
        top: "50%",
        left: "50%",
        width: "100%",
        height: "100%",
        objectFit: "cover",
        transform: "translate(-50%, -50%)",
        zIndex: -1,
      }}
    >
      <source
        src={"../../../../assets/videos/bg_1_people.mp4"}
        type="video/mp4"
      />
    </video>
  );
};

const VideoBackgroundNative = () => {
  return (
    <View style={styles.container}>
      <Video
        source={{
          uri: require("../../../../assets/videos/bg_1_people.mp4"),
        }}
        rate={1.0}
        volume={1.0}
        isMuted={true}
        resizeMode={ResizeMode.COVER}
        shouldPlay
        isLooping
        style={StyleSheet.absoluteFill}
      />
    </View>
  );
};

const styles = StyleSheet.create({
  container: {
    ...StyleSheet.absoluteFillObject,
    justifyContent: "center",
    alignItems: "center",
  },
});

const VideoBackground = () => {
  if (Platform.OS === "web") {
    return <VideoBackgroundWeb />;
  }
  return <VideoBackgroundNative />;
};

export default VideoBackground;

assets folder is at the root of project along side app/, ios/, etc


cpplint needs update after changed styleguide: output params should be references now

i appreciate the recent change of the c++ style guide, because formerly the guidelines said, that output params of functions should be pointers and should not be const references. (old lines 1709, 1710, 1768--1785)
the old rule was a really bad idea in my opinion (and the 'con' was not valid), so it's good, that is was changed now.
however, cpplint.py still has the old rule implemented, see https://github.com/google/styleguide/blob/gh-pages/cpplint/cpplint.py#L5142-L5149.
so it would be great, if cpplint.py would be adapted to the changes of the guidelines.

any plan to upgrade the cpplint? or explain this in the c++ style guide?


Have a mechanism to update the uid of MDASequences when run

Currently if you make an MDASequence and then run it multiple times then they will share the same uid and this can lead to issues downstream (e.g. in displaying in napari-mircomanager).
While the description of the experiment is the same, these colleciton runs should have different ids because they have been run at different times and are thus distinct from eachother.

I think maybe that's a napari-micromanager issue rather than a uid issue.  Napari micromanager could perhaps add a timestamp to it to avoid those conflicts


when will the code about grasping with objects update?

We have released all the code about grasping in the obj branch.


Displayed MFlops always 0

When running Example 2 with the hex-beam mesh, the line "Wall MFLOPS:" always seems to be 0. Increasing the resolution and scale of the mesh increases the wallclock time but doesn't seem to affect the MFLOPS in any way. Can someone explain this? Am I doing something wrong?

There is no Wall MFLOPS: line in the output of examples/ex2.cpp. Can you clarify what exactly are you running?

I think this is output from hypre, not sure if you need to enable some hypre option to get actual numbers.

This is my command line for ex2p
mpirun --mca btl tcp,self -np 4 ./ex2p -m ../data/beam-quad.mesh
And then Solve phase times:
wall clock time = 0.02s
wall MFLOPS = 0.00s
cpu clock time = 0.03s
cpu MFLOPS = 0.00s

As @v-dobrev suggested, this output comes from hypre. You can try asking about it at https://github.com/hypre-space/hypre/issues.


Please elaborate how to update cluster upgrade policy on Step 8

[Enter feedback here]
I ran into error with cluster upgrade being blocked by fabric:/System/InfrastructureService/nodetype.
I was able to one of the 2 following to complete the removal.

Rerun the node type removal by visiting https://resources.azure.com and remove the node type stanza.
Follow Update healthy policy example 2

It will be helpful to make it clear how to implement the policy specified on Step 8.

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

ID: 940c0c8f-7d1d-6ba4-57c7-ecec689eb972
Version Independent ID: da8aa375-82c2-5317-a673-2ee79284bcad
Content: Remove a node type in Azure Service Fabric - Azure Service Fabric
Content Source: articles/service-fabric/service-fabric-how-to-remove-node-type.md
Service: service-fabric
GitHub Login: @inputoutputcode
Microsoft Alias: chrpap

Hi @keatseongchan, thanks for bringing this to our attention. I have assigned the issue to the content author to evaluate and update as appropriate

Hi @keatseongchan, Thanks for your feedback. Sorry for the late answer. The part with the upgradeDescription should be deployed with ARM templates as stated in the doc. Resource Explorer should not be used for production deployments, but works as well.

#please-close


Test Issue By Bytepay: lean thrill

This issue is for bytepay test

@sulnong:
Seems your account have only -0.016860049037999758 DOT available, less than 0.001 DOT you want pay.
Please recharge token on http://bytepay.local-dev.com first.

/bytepay pay

No task under this issue.


Profile Manager - Like iTerm2 or SecureCRT - There is any plugin?

I'm migrating from Mac to Windows.
I use terminal essentialy to ssh/telnet remote access to manager network devices and servers.
I'm used to the profile manager of iTerm2, or even the SecureCRT, to store the informations about the host to connect.
I got really excited with Windows Terminal, but I can't see a way to implement the solutions that iTerm2 or SecureCRT used to provide-me, like:

Manage Several profiles, and present it with some order and tags(iTerm2, or even folders (secureCRT).
Integrate passwords based on triggers calling the passwords stored on Keyring(iTerm2), ou passwords stored on the session profile(SecureCRT, not secure method. I know.)

Any Suggestion for that?

Unfortunately, we don't have a feature like this right now. We're tracking related work in /dup #1280, but because we're not a dedicated SSH/telnet client we're not going to be doing password storage, keyring integration, etc.
This is something that'll be helped by us having an extension model (#4000), but not something that's in our near-term plan.


in my project that contains the chart for all the app I need to pass my Chart.version in my values.yaml but i am not able

this is the values.yaml file that contains many config for all the microservices in the application i have this section where i want to inject my Chart.version
my-component:
  config:
    projectVersion: {{ .Chart.version .}}

and this Chart.yaml file
apiVersion: v1
description: xxxxxxxxxxxxxxxxxxx
name: here_the_name_of_all_the_app
version: 2.1.0-162

i got always of parsing and the componenet when deployin is not able to read  {{ .Chart.version .}}  any help pleaase

The problem is that the functions are all built to accept a map[string]Interface and .Chart isn't one:
ChartType: {{ typeOf .Chart }}

ChartType: struct { chart.Metadata; IsRoot bool }

and trying to get the .value from that struct will fail:
can't evaluate field version in type struct { chart.Metadata; IsRoot bool }

There is a simple cheat, however. Pass it to and from json (or yaml):
{{ $chart := toJson .Chart | fromJson }}
ChartVersion: {{ $chart.version }}

ChartVersion: 0.1.0

@joejulian  thank you for your solution it helps me very much

You're looking for the semver function: http://masterminds.github.io/sprig/semver.html


Enable Elixir versioning

https://laravel.com/docs/elixir#versioning-and-cache-busting
Will require bringing in the elixir() helper and making sure it's configured correctly for source and target directories.

I would love to see this happen. I tried setting it up, but Jigsaw kept choking on the elixir() call.
For now, I've just added an extra step to my production build where I update file names. ¯_(ツ)_/¯

I finally got it to work, I'm going to submit a pull request for it 😄


require_dependency 'chaskiq/application_controller'

Hi there,
I'm developing a Rails engine of my own, and in my research I came across this gem. I was curious what the purpose of doing require_dependency "chaskiq/application_controller" at the top of your controllers is?
Thanks!

Hi Zach , good catch , I'm not sure about it , but I think that could be related to the use of Somecontroller < ApplicationController instead of Chaskiq::ApplicationController maybe I was trying to require  Chaskiq::ApplicationController but that require_dependency  could be removed and see how it behaves.

Thanks for the info. I think I was running into issues where ::ApplicationController was being subclassed instead of {Engine}::ApplicationController. Adding require_dependency 'engine/application_controller' seemed to fix the issue. You would think it would look for {Engine}::ApplicationController before ::ApplicationController so maybe it's a bug with Rails. I'll just have to be specific for now. Thanks

Found this today, btw: https://github.com/rails/rails/pull/22112


Javascript "Write Reusable JavaScript with Functions" Not accepting answer

Challenge Name: Write Reusable JavaScript with Functions

https://www.freecodecamp.com/challenges/write-reusable-javascript-with-functions#?solution=
%2F%2F Example
function ourReusableFunction() {
  console.log("Heyya%2C World")%3B
}

ourReusableFunction()%3B

%2F%2F Only change code below this line
function reusableFunction() {
  colsole.log("Hi World")%3B
}

reusableFunction()%3B
Issue Description

It will not accept the answer.
Browser Information

Browser Name, Version: Chrome, Version 55.0.2883.95 (64-bit)
Operating System: macOS
Mobile, Desktop, or Tablet: MacBook Pro

Your Code

// Example
function ourReusableFunction() {
console.log("Heyya, World");
}
ourReusableFunction();
// Only change code below this line
function reusableFunction() {
colsole.log("Hi World");
}
reusableFunction();
Screenshot

You have a typo in your code.
The issue tracker is for reporting bugs only. Please use the help chat room or try looking through the forum for help with a specific challenge.
Happy Coding.

@soomitt Thank you for reporting this issue. Hint: you have a typo.
This is a standard message notifying you that this issue seems to be a request for help. Instead of asking for help here, please click the "help" button on the challenge on Free Code Camp, which will take you to the help chatroom for that specific challenge. You can also view our full list of official chatrooms.
If you think I'm wrong in closing this issue, please reopen it and add further clarification. Thank you, and happy coding!

function reusableFunction(x, y) {
  var sum = x + y;
  console.log("Hi World");
}

reusableFunction();


Support for glob matching

Hi Lucio,
Thanks for the great tool, be sure I've already told all my coworkers about it, since it is an idea I wanted to work on for a long time (same issues with dotjs, and the monkey userscripts are just way less user friendly IMHO).
Anyway, I have a feature request, which I'll illustrate with GitHub paths. Say for instance I'd like to have a script for all my project settings github.com/a/b/settings. I must copy for that every project, or create a github.com.js that will look at the url. However, we could solve that one quite fast with glob matching:
github.com/BuonOmo/*/settings.js
github.com/B*/*/settings.js

The glob would act like a bash glob, with only the star pattern since ? may be confusing with urls.
I'd be glad to implement it at some point, just opening the issue for discussion beforehand 🙂
Best regards,
Ulysse

Hey @BuonOmo, thanks for the suggestion.
Yeah, the way I would do this is by creating a github.com.js and parsing the URL there to see if I am in the settings page of some project, like you suggested yourself.
At first sight, doing a wildcard match looks undesirable to me for a couple of reasons. First, we'd have no easy way of telling if the user wants glob matching or not. Say I have a script called /github.com/settings.js. Do I mean to strictly match https://github.com/settings.js or do I want to match everything inside github.com that ends with settings? What if it has settings in the middle of the path, should we match it too? Did the user mean to match github.com/set*ttings.js by any chance? I think you got the idea. We could adopt some symbol to represent the wildcard char (since the OS won't allow *), but we'd need to pick something that would be allowed by the OS while not being allowed in a real URL. Seems a bit too much complex logic to add to Witchcraft considering the second reason that comes to my mind is that doing the github.com.js URL parsing approach is pretty easy to do 🙂
Makes sense?

At first sight, doing a wildcard match looks undesirable to me for a couple of reasons. First, we'd have no easy way of telling if the user wants glob matching or not. Say I have a script called /github.com/settings.js. Do I mean to strictly match https://github.com/settings.js or do I want to match everything inside github.com that ends with settings?

Glob matching does not mean uncomplete matching!, /github.com/settings would still mean the same! However, /github.com/settings* could mean /github.com/settingsfoo (and not /github.com/settings/foo IMHO, yet this could be discussed)

since the OS won't allow *

I'll have to admit, I've never worked on something else than Ubuntu, Mac OS or Debian, yet touch 'foo*' works well on those OS!

Anyway, I feel like this would be a great benefit because URL parsing is already redundant with the basic project idea of following folders to match urls (there are two layers of routing), however I get that this is adding too much complexity, I'll probably just have my dedicated branch sooner or later then 🙂

Yep, Windows won't not accept * as a valid file name character. I'd also avoid using it on other operating systems anyway, not only due to portability issues but also because it could cause confusion to other users (I honestly didn't know it was possible to use asterisks - but I've just tried on my Mac and it really worked 😂).
Cool, let me know how it goes with your fork!
I'll close the ticket for now, but feel free to reopen it later if you feel like adding something.
Thanks!


decimal place accuracy of nodes

Hello! Thanks for this library! It's great! When I look at longitudes and latitudes I get decimal place accuracy of 4 for lat and 3 for lon:
lat: 41.1337 lon: -111.766
Is this normal?
When I use a NodeJS equivalent reader, I get accuracy of 7 decimal places which makes more sense to me.
Thanks,
Craig.

Libosmium uses the max accuracy that OSM locations have, ie 7 digits after the decimal point.
You don't tell us how you get the results that you got, but I suspect you are using C++ streams output which has 6 digits default precision (6 digits before and after decimal point together). See http://en.cppreference.com/w/cpp/io/ios_base/precision .

Yeah -_- sorry I didn't know that streams cripple precision.
Thanks for your help.


set up SSCS track your appeal notifications security scan

Before creating a pull request make sure that:

[ ] commit messages are meaningful and follow good commit message guidelines
[ ] README and other documentation has been updated / added (if needed)
[ ] tests have been updated / new tests has been added (if needed)

Please remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ ] No

Ok to merge


Explore our options for speeding up the pre-deployment merge to main

Description
Our preflight checks on PRs are taking a while to deploy. What can we do to speed them up?
Proposed solution
We're already looking into running the tests concurrently (#3049 ) but are there other steps we can take to speed up the automated checks?

Instead want to explore options around rolling back both the UI and backend changes. On the agenda to discuss at 12/9 eng sync.


Revert "Update Links in the Salesforce C2C Doc"

Reverts SumoLogic/sumologic-documentation#3261

@kimsauce or @stacykor, could you approve this revert PR?

Thanks, @kimsauce!


Online demo?

Hi, can i see a online demo? or screenshots?
Regards!

+1

Yes please, Can I see a demo? or screenshots?
Cheers


[Question] Current state, Godot 4.0?

Hey @quinnvoker,
I stumbled upon your old post on r/gamedev, I'm quite interested in this module since it could really help with a project I'm working on currently.
So I wanted to know 2 things:

Is the module up-to-date and ready for production? The last commit was 3 months ago so I'm worried maybe you've abandoned the project.
Do you have anything planned for Godot 4.0? Performance optimization? Pre-compiled version?

On a side note, I really like the simplicity it has for the "end-user", great work overall.
If anything is planned, I'll try to help, I'll just need to get my C++ back together.

Hi there, thanks for getting in touch!
I'm not actively working on this project at the moment, but I wouldn't call it abandoned either.
I don't have any additional features to add planned or anything, and I recently got my first job as a programmer and am still settling into it, so I don't have as much time to put into projects like this as I did last year.
However, I plan to at least keep qurobullet up-to-date and compatible with the latest releases of Godot. To my knowledge, this module is fully compatible with 3.2 and is generally stable (though I haven't done a lot of exhaustive testing since last summer, I do check if it works in new versions, and there's not a whole lot that can really go wrong with it).
As for 4.0, there's a branch called testing/godot-4.0 for that purpose. 4.0 changed a number of things internally and so variable types and such had to be updated for compatibility. So far it seems to work okay, though again, no exhaustive testing since the last time I worked on this, 4.0 was still in a very early/buggy state.
No further optimizations planned, as I think it's already working about as efficiently as Godot's physics server can handle at this point. The module may benefit from any physics optimizations made in Godot itself though.
All in all, I think the module is stable enough for use in production. If you run into any unexpected issues though, feel free to get in touch and I can sort them out and make any necessary updates.
Cheers and good luck with your project!

Using the latest Godot code pushed on their master branch, when compiling I get the error include : 'core/object.h' : No such file or directory in the bullet.h file.

If you're using Godot's master branch, are you using the testing/godot-4.0 branch of qurobullet? The master branch of qurobullet is only compatible with the source of Godot 3.2.x.
If that's not it, let me know and I'll check it out.

@quinnvoker Ah shit didn't check branches, I'll try testing/godot-4.0 asap.

Okay, makes sense! Thanks for letting me know, that's another update that's gonna have to happen in the 4.0 testing branch then. I'll see if I can tackle that this weekend.
I'm curious though, if you're looking for something stable enough for full game production in qurobullet, why are you using the unstable pre-alpha of Godot 4.0 on master and not one of the stable releases of 3.2.x?
You can find the source code of stable releases here if you need it: https://github.com/godotengine/godot/releases

@quinnvoker Actually I didn't even think on which branch I was when I cloned Godot but yesterday for some reason it made sense for me to clone the latest changes... I was probably tired since I did it at 1 am.
I'll try again tonight on a 3.2.x release,

Patched the testing/godot-4.0 branch to be compatible with Godot master currently. Still wouldn't recommend using Godot's master branch yet, as it's still prone to freeze/hang etc. But it should work with qurobullet for now at least.


Revised Community Guides

Made changes proposed by Fernando
Cleaned up meeting section
Commented out empty sections

Oh Awesome, thanks ! I was  busy today working with Mike !


fix wildcard expansion for stored credentials of domains

While testing the auth-file feature for rattler-build (https://github.com/prefix-dev/rattler-build/pull/413) I noticed that the wildcard extension for domains does not work correctly:
https://repo.prefix.dev was matched with repo.prefix.dev and *.repo.prefix.dev, but not with *.prefix.dev. On closer inspection, it looks like the function never worked properly: See https://github.com/mamba-org/rattler/pull/252
This PR fixes the wildcard handling and adds a unit test for it.

Thanks @0xbe7a !


Revert "GEODE-8373: For CI test runs, split the assemble and test invocation, to set max-…"

Reverts apache/geode#5389

The concatenation of args to the bash -c is not evaluated as expected, so the actual test portion does not run. Revert and look for a better answer to the JVM args for testing.


Confirmation email to the organisator > Use text of step 5

When sending email to the organisator, use the step 5's content.

Pour l'email de confirmation envoyé au créateur de l'activité.
Pour l'instant le contenu de cet email est très pauvre : lien vers l'activité, mot de passe.
Il est possible de réutiliser le contenu plus généreux de l'étape 5.

Text is done, but in order to put the css and icons, i need to either :

put all css rules inline. Like report all the styles applied to each element and go like . Fortunatly, there is a module for the inlining part but there is still the annoying part to grasp all css rules in order to report then in a style tag.
download the icons as svg and put them on some image host, and then refer them as img. but css will still be needed if you want more tha just the icons

CSS : just grab the message box's content, we do not need the fancy message box's frame.
SVG : I just though about something..... let's just hand copy the 5~6 svg's inline code and paste that svg code into our html template

With such approach : no additional plug-in needed. :heart:

It's still hazardous how the icons are loaded :some are loaded, some are note. I manage to have a mail with all icons one in every three attemps. Did not try on other client than gmail, but since CRI is heavily related on Gmail, i don't know if we should keep icons. It looks kind of dirty when images are not loaded


Caffe/Pytorch facerec_resnet20 model fingerprint error Vitis 2.5

Hi,
I am trying to run facerec_resnet20 on my custom board image but I got errors due to model fingerprint mismatch.
dpu_runner_base_imp.cpp:676] CHECK fingerprint fail ! model_fingerprint 0x1000020f6014407 dpu_fingerprint 0x101000016010407  F1201 08:07:19.906725   842 dpu_runner_base_imp.cpp:648] fingerprint check failure.
First, I tried Caffe .xmodel from model_zoo - cf_facerec-resnet20_112_96_3.5G_2.5 and got the error above.
Then, I tried Pytorch .xmodel from model_zoo - pt_facerec-resnet20_mixed_112_96_3.5G_2.5 and got exactly the same error as above.
After that, I tried to compile the same Pytorch model from model zoo for my DPU architecture, but I also got the same error as above which is very weird.
Compile cmd:
vai_c_xir -x quantized/Resnet_int.xmodel -a arch.json -o facerec_pretrained_resnet20 -n facerec_pretrained_resnet20
where arch.json contains:
{"fingerprint":"0x101000016010407"}
Why DPU cannot recognize that my face_rec_resnet20 model is compiled for "0x101000016010407"? I have other several DNN models which work very well on the same DPU architecture.
My environment:

Vitis AI 2.5 docker
Petalinux 2022.1
VART 2.5
1x DPU
DPU v4.0 B4096 "fingerprint":"0x101000016010407"
ZCU104

@lishixlnx
thank you for your reply.
The model initialization is successful, but the inference causes the fingerprint mismatch. I use these functions for init and inference:
std::unique_ptr<vitis::ai::FaceRecog> faceFeaturesModel;
faceFeaturesModel = vitis::ai::FaceRecog::create("facerec_resnet20");

faceFeaturesModel->run_fixed(
              inputImage(rectPair.first),
              rectPair.second.x,
              rectPair.second.y,
              rectPair.second.width,
              rectPair.second.height);

When I rename the model directory on the sd card from "facerec_resnet20" to "test_facerec_resnet20" on purpose,  the initialization fails with message: "cannot find model <facerec_resnet20> after checking following dir..." so I am pretty sure that I use correct model.
Just to mention, the facerec_resnet20 directory contains:

md5sum.txt: 86bd2515caae59fdcfe9bd6124c10408
meta.json:

{
    "lib": "libvart-dpu-runner.so",
    "filename": "facerec_resnet20.xmodel",
    "kernel": [
        "subgraph_Add_1"
    ],
    "target": "DPUCZDX8G_ISA1_B4096"
}

facerec_resnet20.prototxt:

model {
   name : "facerec_resnet20"
   kernel {
      name: "facerec_resnet20"
      mean: 128.0
      mean: 128.0
      mean: 128.0
      scale: 0.0078125
      scale: 0.0078125
      scale: 0.0078125
   }
}

the model:
facerec_resnet20.xmodel

Do you have any suggestions how to solve this issue?
Any help would be appreciated.


Feature: Show a list of all shapes as layers

Having a list of all the shapes and their z-index ordering (layers) would be really useful to more quickly order them on the from front to back.
Also being able to group layers together and then move them as one entity would be really useful.

Thanks for proposing new features.
Actually, the 2nd is already supported by the data structure of the shapes and also in the render engine. However, the UI and interactions are not implemented yet.
For having a list of shapes, I have thought back and forth about this function but I'm not really convinced this would be an important function. Maintaining the good of this function for all shapes is not a simple task.
Btw, having layers, similar to draw.io, would be more useful.

Great that grouping will already be possible :)
Yeah just having layers like photoshop, even if you explicitly create them, would be useful to be able to reorder items and see where they are in the hierarchy.


QGB Verify the sent data commitment confirm is a data commitment attestation request

Closes https://github.com/celestiaorg/celestia-app/issues/520

Depends on https://github.com/celestiaorg/celestia-app/pull/523

Codecov Report

Merging #524 (089dfe4) into qgb-integration (458b6b2) will increase coverage by 0.76%.
The diff coverage is 20.44%.

@@                 Coverage Diff                 @@
##           qgb-integration     #524      +/-   ##
===================================================
+ Coverage            11.72%   12.48%   +0.76%
===================================================
  Files                   65       56       -9
  Lines                10881     9705    -1176
===================================================
- Hits                  1276     1212      -64
+ Misses                9515     8410    -1105
+ Partials                90       83       -7

Impacted Files
Coverage Δ

e2e/qgb/qgb_network.go
0.00% <0.00%> (ø)

e2e/qgb/test_commons.go
0.00% <ø> (ø)

x/qgb/keeper/hooks.go
34.61% <ø> (+2.47%)
:arrow_up:

x/qgb/keeper/keeper_data_commitment_confirm.go
42.85% <ø> (ø)

x/qgb/keeper/keeper_valset.go
32.00% <0.00%> (-7.51%)
:arrow_down:

x/qgb/keeper/msg_server.go
0.00% <0.00%> (ø)

x/qgb/keeper/query_attestation.go
0.00% <ø> (ø)

x/qgb/keeper/query_general.go
0.00% <0.00%> (ø)

x/qgb/keeper/query_valset.go
0.00% <ø> (ø)

x/qgb/types/abi_consts.go
69.23% <ø> (ø)

... and 23 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 458b6b2...089dfe4. Read the comment docs.


For Louisiana, place_county_name column on export page contains no values

Export some observations from Louisiana. Include place_county_name and place_admin2_name columns.
Open the CSV. place_county_name fields are blank, and place_admin2_name fields contain the correct county/parish names.
Try the same thing in other states (I tried some in Arizona and California). Both columns include the county name.

We should make sure that place_county_name works for Louisiana.

I'm guessing there's some literal lookup based on place_type instead of admin_level that's not working in Louisiana because they have parishes, not counties.

This should be fixed. I addressed it by making methods like place_county_name use their previous behavior, which is looking up the county place by looking at Place.place_type - but if no results are found, and the place type is also an admin level, fall back to looking up the place by admin level. I am seeing place_county_name populated for exports of observations from Louisiana now


Day 420

Good morning! Here's your coding interview problem for today.
This problem was asked by Microsoft.
A number is considered perfect if its digits sum up to exactly 10.
Given a positive integer n, return the n-th perfect number.
For example, given 1, you should return 19. Given 2, you should return 28.

Identical to Day 70: https://github.com/vaskoz/dailycodingproblem-go/issues/149


flutter_credit_card:compileDebugKotlin

flutter 3.24
flutter_credit_card: ^4.0.1
flutter_credit_card-4.0.1/android/src/main/kotlin/com/simform/flutter_credit_card/gyroscope/GyroscopeStreamHandler.kt:18:35 Property delegate must have a 'getValue(GyroscopeStreamHandler, KProperty<>)' method. None of the following functions is suitable:
public inline operator fun  Lazy<Sensor?>.getValue(thisRef: Any?, property: KProperty<>): Sensor? defined in kotlin
FAILURE: Build completed with 2 failures.
What went wrong:
Execution failed for task ':flutter_credit_card:compileDebugKotlin'.

A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
Compilation error. See log for more details

For temp soluyion :
Go to GyroscopeStreamHandler.kt
make the return type nullable
private val sensor: Sensor? by lazy {
sensorManager.getDefaultSensor(Sensor.TYPE_GYROSCOPE)
}


Improve metrics for deletion of objects

During deletion our alerts are sometimes triggering false positives. Also, we can't build a proper alert for LoadBalancers stuck in deletion.
This is fixed in this PR by

setting *_replicas to 0 for objects in deletion
adding *_deletion_timestamp metrics similar to what kube-state-metrics is doing for pods

Thanks for the PR!
Can you please add the new metrics and a comment about the *_replicas metrics to the docs: https://github.com/stackitcloud/yawol/blob/main/docs/components.md#metrics

Done, PTAL :)


near "WITH": syntax error

When running identi I always get this message:
near "WITH": syntax error
How can I trace the origin?

That happens when you're linking to an SQLite version older than 3.8.3.


clean up spam comments

most of the comments are spam at http://blog.darlinghq.org/2019/07/darling-progress-report-q2-2019.html?m=1

I wouldn't worry about that.


Run nodeport DNAT already on the source node.

DNAT for nodeport services has to execute already on the source node. If run on the destination node instead and the selected backend is not on the destination node, then the response takes a different route and does not get SNATed before reaching the source pod.

Coverage increased (+0.2%) to 75.192% when pulling ab0e85addd78e2dfb95e83db4872a6416d0d6c3c on milanlenco:master into 90698f46a1fe2a4e189b12413c10eb5485b4a15c on contiv:master.


fava: update maintainers

As discussed in #118355

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

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

1 package built:

fava


Compatibility with Node 14

Functions that used to get Local now gets Isolate*.

steps for testing windshaft-cartodb are here https://github.com/decision-labs/Windshaft-cartodb/issues/1
there is a chain of dependencies to windshaft which has the dependency on @cartodb/node-mapnik so we must fork these and point to this branch in package.json


intermittent crash caused by backlight module

Occasionally (every couple of hours), I am getting this error:
terminate called after throwing an instance of 'std::runtime_error'
  what():  ptr was null

Stack trace:
Stack trace of thread 16139:
#0  0x00007f1282ddfd22 raise (libc.so.6 + 0x3cd22)
#1  0x00007f1282dc9862 abort (libc.so.6 + 0x26862)
#2  0x00007f128318a802 _ZN9__gnu_cxx27__verbose_terminate_handlerEv (libstdc++.so.6 + 0x99802)
#3  0x00007f1283196c8a _ZN10__cxxabiv111__terminateEPFvvE (libstdc++.so.6 + 0xa5c8a)
#4  0x00007f1283196cf7 _ZSt9terminatev (libstdc++.so.6 + 0xa5cf7)
#5  0x00007f1283196f8e __cxa_throw (libstdc++.so.6 + 0xa5f8e)
#6  0x000055c0f9e9c61d check_nn (waybar + 0xd361d)
#7  0x000055c0f9e9c776 _ZN6waybar7modules9Backlight17enumerate_devicesIN9__gnu_cxx17__normal_iteratorIPNS1_12BacklightDevESt6vectorIS5_SaIS5_EEEESt20back_insert_iteratorIS9_EEEvT_SD_T0_P4udev (waybar + 0xd3776)
#8  0x000055c0f9e9b05d _ZZN6waybar7modules9BacklightC4ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKN4Json5ValueEENKUlvE_clEv (waybar + 0xd205d)
#9  0x000055c0f9e0cc61 _ZNKSt8functionIFvvEEclEv (waybar + 0x43c61)
#10 0x00007f12831c43c4 execute_native_thread_routine (libstdc++.so.6 + 0xd33c4)
#11 0x00007f1282f7a259 start_thread (libpthread.so.0 + 0x9259)
#12 0x00007f1282ea15e3 __clone (libc.so.6 + 0xfe5e3)

i.e. this block of code:
https://github.com/Alexays/Waybar/blob/96caa9f094f26755217156a77f4d5bf4a46ce91b/src/modules/backlight.cpp#L208-L217

For the record, I am using the brightness module with ddcci-driver-linux

Same problem here, I use ddcci-driver-linux on Fedora Rawhide
After a few hours, the bar crashes with this message:
terminate called after throwing an instance of 'std::runtime_error'   what():  ptr was null

Been using this fix for about 20 hours now and my bar hasn't crashed yet (it usually would crash a dozen times or so in that timespan). I should've thought to log it as a warning tho. oh well


Support plain Attacks

right now, setting the noteskin leaves the template in an invalid state

Fixed in v3


proposal: math/rand: Add Rand.choose(from int, choose int, replace bool) []int

This generalizes the current Perm, which could be implemented as:
func (r *Rand) Perm(n int) []int {
  choices, err := r.Choose(n, n, false)
  if err != nil {
    panic(err)
  }
  return choices
}

(although see here for replacing Perm with Shuffle).
A Choose method could also replace Intn:
func (r *Rand) Intn(n int) int {
  choices, err := r.Choose(n, 1, true)
  if err != nil {
    panic(err)
  }
  return choices[0]
}

It would also allow for optimizing situations where you would currently use multiple Intn calls.  For example, if n was 256, you could calculate up to eight draws from one Uint64 call.  The token-generation use case from here would be:
charset := "1234567890abcdefghijklmnopqrstuvwxyz"
token := make([]byte, 22)
choices, err := r.Choose(len(charset), len(token), true)
if err != nil {
  return err
}
for i, choice := range choices {
  token[i] = choice
}

although you'd want something like #25531 to get a crypographically secure source behind those choices.  That seems both more efficient and more readable than other approaches I've seen to generating random tokens in bases that are not powers of two.

Could you write a sample doc comment for the new function?  Thanks.

Could you write a sample doc comment for the new function?

Here's a play with the docs and a first pass at an implementation.  I'll inline the doc here for folks who want to make inline comments:
// Choose draws choose times from the range [0,from) with(out)
// replacement.  For example, r.Choose(10, 3, true) draws 3 times from
// [0,10) with replacement, which is equivalent to []int{r.Intn(10),
// r.Intn(10), r.Intn(10)}.  And r.Choose(10, 10, false) draws 10
// times from [0,10) without replacement, which is equivalent to
// r.Perm(10).
//
// Choose will return an error if choose > from and replace is false,
// or if from < 1.
func (r Rand) Choose(from int, choose int, replace bool) ([]int, error) {

Thanks.  That seems possible to write outside the standard library, in a go-gettable package.  Is it widely used enough that it ought to be in the standard library?  Consider https://golang.org/doc/faq#x_in_std .

That seems possible to write outside the standard library, in a go-gettable package. Is it widely used enough that it ought to be in the standard library? Consider https://golang.org/doc/faq#x_in_std .

Moving all of math/rand out of the stdlib has been suggested before in #24800, although if you went that route you'd need to vendor it for these:
$ git grep math/rand go1.10.2 -- src
go1.10.2:src/archive/zip/writer_test.go
go1.10.2:src/bytes/buffer_test.go
go1.10.2:src/bytes/bytes_test.go
go1.10.2:src/cmd/compile/internal/gc/pgen.go
...

But it looks like we already vendor x/crypto, x/net, and x/text, so that's probably not a blocker.  But wherever the rand package lives, I think the goal should be to provide flexible primitives for consumers.
By adding Choose we can deprecate (and, with Go 2, drop) the current Rand.Intn and Rand.Perm, while also enabling more efficient approaches to random token generation and similar cases (as I outlined in my initial post here).  And even looking only within math/rand, the implementation I've mocked up seems more efficient than the current Perm.  For example, see this updated play, which shows:
drawing an int63
Choose emulating multiple Intn: [5 0 5 5 6]
drawing an int63
Choose emulating Perm: [2 4 7 8 6 1 0 5 9 3]
drawing an int63
drawing an int63
drawing an int63
drawing an int63
drawing an int63
drawing an int63
drawing an int63
drawing an int63
drawing an int63
drawing an int63
rand.Perm: [7 0 4 6 2 5 8 9 1 3]

where rand.Perm(10) draws 10 int63s while Choose(10, 10, false) only draws one.  If this is useful enough for math/rand to want it internally, do I need to collect more evidence to argue for making it public?

If this is useful enough for math/rand to want it internally, do I need to collect more evidence to argue for making it public?

Well, yes, I think so.  Intn and Perm are simple APIs, easy to understand and to use.  I don't think we would drop them even if we added Choose.  Every additional API carries a cost.  Adding an internal version of choose and using it to implement Perm may be an easy win with relatively little cost.  Adding an external API Choose means documenting it and carrying it forward forever.  The fact that Chose might be useful for implementing Perm isn't especially relevant to whether it should be added to the public API.

Adding an internal version of choose and using it to implement Perm may be an easy win with relatively little cost.

I've retitled this issue to use rand.choose.  Can we re-scope the issue to be about adding an internal choose helper?  If/when that lands in Go, we can revisit whether or not it deserves to be made public.

// Choose draws choose times from the range [0,from) with(out)
// replacement.  For example, r.Choose(10, 3, true) draws 3 times from
// [0,10) with replacement, which is equivalent to []int{r.Intn(10),
// r.Intn(10), r.Intn(10)}.  And r.Choose(10, 10, false) draws 10
// times from [0,10) without replacement, which is equivalent to
// r.Perm(10).

So what you're saying is this would be easy to implement on our own? Isn't the whole purpose of the Go stdlib to have minimal tooling?

Can we re-scope the issue to be about adding an internal choose helper? If/when that lands in Go, we can revisit whether or not it deserves to be made public?

It would be good to have an alternative to rand.Perm(100)[:5]. Creating large permutations may take up a lot of memory, so having an option to have a partial permutation may be good. rand.Choose(100, 5) may be good, and rand.Perm(100) could perhaps be completely replaced with rand.Choose(100, 100) in Go 2.
 Just initialize an array with a for loop. Ain't that hard. Also, boolean flags on functions are bad ideas. Just make two functions and name them accordingly. Once you make a separate function for ChooseWithReplace:
// n: the limit for Intn
// m: the size of the slice
func ChooseWithReplace(n, m int) []int {
    slice := make([]int, m)
    for i := range slice {
        slice[i] = Intn(n)
    }
    return slice
}

You realize that a function like this shouldn't be in the standard library anyway.
TL;DR: Remove the boolean flag, don't implement choosing with replacement. Create a function that creates partial permutations, have rand.Perm() either use the new function, or remove rand.Perm() entirely in favor of this one

So what you're saying is this would be easy to implement on our own? Isn't the whole purpose of the Go stdlib to have minimal tooling?

I'm having trouble parsing this.  Are you saying "why keep Intn and Perm one you have Choose?"?  I'd be fine dropping them, but @ianlancetaylor wants to keep them.  If there is stdlib-maintainer appetite for Perm and Intn as shims around a public Choose, I'm fine with that.

It would be good to have an alternative to rand.Perm(100)[:5]...

This argument for a public Choose (without replacement) makes sense to me.  But for the first stage of this I'm fine with a private choose, and we can return to discussing public APIs if/when that succeeds.

 Just initialize an array with a for loop. Ain't that hard.

I agree that it's not hard, but it is inefficient (just like Perm(100)[:5]).  For example, one 64-bit draw has enough data for four 16-bit ints.  But the current Intn backend will make four int63 draws for four successive Intn(65535) calls anyway.  You could work around that with a rand backend that saved leftover bits for future calls, or you could expose Choose (with replacement) to give callers a way to tell the library "don't stop after generating one of these, I'll need 100", etc.  But the current implementation/API gives you no way to do this efficiently.  But I'm fine leaving this unresolved while we work out whether we want an internal choose behind Perm.

Also, boolean flags on functions are bad ideas. Just make two functions and name them accordingly. Once you make a separate function for ChooseWithReplace...

I think it's a useful optimization.  But I'd be fine with caching unused bits instead.  Which approach makes more sense in the API can get sorted out if/when we have an internal choose.  And I'm fine with two functions to avoid a boolean argument, but again, I think we can punt on that until we have a backing implementation to expose.

I'm having trouble parsing this. Are you saying "why keep Intn and Perm one you have Choose?"? I'd be fine dropping them, but @ianlancetaylor wants to keep them. If there is stdlib-maintainer appetite for Perm and Intn as shims around a public Choose, I'm fine with that.

I was saying "why use Choose (with replacement) if it's easily implementable by successive Intn calls"

But the current Intn backend will make four int63 draws for four successive Intn(65535) calls anyway.

Then don't use Intn, use Read. If you're optimized to the point of using an int16 then I feel that you should be at the low-level of using Read.

Even though we are not moving math/rand outside the standard library, this specific function can easily be implemented outside the standard library and seems too special-purpose to warrant adding to the core math/rand.

Even though we are not moving math/rand outside the standard library, this specific function can easily be implemented outside the standard library and seems too special-purpose to warrant adding to the core math/rand.

That addresses the API portion of this.  Is there interest in improving the over-drawing in Intn and Perm's current implemtations without changing the public API?

Not particularly, no. We try not to change the output of these functions from release to release.

Not particularly, no. We try not to change the output of these functions from release to release.

Right, but for Go 2 (as this issue is tagged)?


Use speaking buttons in confirmation dialogs

Is your feature request related to a problem? Please describe.
If you record a new project while a previous one was not saved, you will get a "Do you want to discard the previous project?" dialog. Usually, such dialogs show a "Do you want to save the modified project?" confirmation, so it is necessary to read the message and not just click one of the buttons
Describe the solution you'd like
Use buttons with clear speaking names - instead of Yes/No use Discard/Keep or something similar
Describe alternatives you've considered
There is no alternative.

I'm referring to this dialog.

I wholeheartedly agree with that. I always waste time because I have to read the whole dialog's text to understand what "Yes" or "No" means, especially when exiting.

The next version (v3) will use action buttons for dialogs.


Feature: default share of /data/config.yml

Not a bug, just an idea.
Most people using this container are wanting to use it to share something that has been made available to the container using a mapped volume. Accessing and editing the config.yml from inside the container can be difficult, depending on your linux knowledge.
My suggestion is that by default, on first build, if it doesn't already exist, a /data/config.yml is created that is configured to share the /data folder in a public share. It could also contain a commented section with a full config example for reference.
This would enable users to immediately remotely access and edit the config.yml to suit their needs, just restarting the container for the new config to take effect.

auth:
  - user: dockerSamba
    group: dockerSambaGroup
    uid: 1000
    gid: 1000
    password: dockerSambaSecurePassword
global:
  - "force user = dockerSamba"
  - "force group = dockerSambaGroup"
share:
  - name: data
    comment: Public
    path: /data
    browsable: yes
    readonly: no
    guestok: yes
    veto: no


Revutska Anastasiia: Implement K-top based on count min scketch

@AnastasiaRevutskaiia
I really like class breakdown and project structure!
And unittest are implemented too, that's great!
Please fix some next items:

Implement parameter configuration as mentioned in https://github.com/vtikhonov/lab_pdsa_2022/blob/main/README.md?plain=1#L10 so the app takes input files not only from resources
Make output be aligned with https://github.com/vtikhonov/lab_pdsa_2022/blob/main/README.md?plain=1#L19-L24, so it is easy to run the app with different configs and compare results with exact values

@vtikhonov please review this PR again, changes were provided according to your notes, thank you in advance

Please drop revutska-anastasiia/com.revutska-1.0-SNAPSHOT-jar-with-dependencies.jar binary file, no need to keep it in git

Final question: can you describe why the parallel version of the algorithm produces a different result than sequential one?
|                word|   freq_ref|freq_approx| error %|
|                   s|        605|        663|    9.59|
|                   t|        224|        262|   16.96|
|                   O|        179|        250|   39.66|
|             Gabriel|        158|        210|   32.91|
|                 Mrs|        117|        170|   45.30|
|                room|        117|        163|   39.32|
|               asked|        127|        158|   24.41|
|               house|         77|        158|  105.19|
|                Aunt|        100|        144|   44.00|
|             Project|         84|        138|   64.29|

Parallel:
|                word|   freq_ref|freq_approx| error %|
|                   s|        605|        541|   10.58|
|                   t|        224|        166|   25.89|
|             Project|         84|         68|   19.05|
|              Corley|         52|         50|    3.85|
|            Gallaher|         56|         34|   39.29|
|             Lenehan|         31|         27|   12.90|
|               Maria|         42|         27|   35.71|
|              Mahony|         23|         23|    0.00|
|                aunt|         27|         22|   18.52|
|               Jimmy|         26|         20|   23.08|

Moreover, approximated results sometimes are less than the precise ones? The sequential version estimates are greater or equal, this is how Count-Min sketch works.
The question is not about fixing the implementation, but to understand why that happens, and just describe what could solve the issue.


Pagers do not work with new git - error: cannot run 140: EDC5129I No such file or directory.

git diff
error: cannot run 140: EDC5129I No such file or directory.

Investigating this...


Proto-goal: transition clusters only providing users with dedicated nodes transition to shared nodes

Brief description
Many jupyterhub's setup by 2i2c were initially setup to start a new node per user, mapping 1:1 between users:nodes. This has several drawbacks that we can avoid if we help those jupyterhub transition to not always providing dedicated nodes.
Drawbacks of always using dedicated nodes include

inefficient use of cpu/memory paid for

increases cost
increases required cloud quota to request to scale to support X users

increased average startup times (server startup, image download)

For reference, this topic has been discussed in #2121 that considered what node sizes to provide and a lot more details. This goal though is reduced in scope to transition towards use of nodes shared by multiple users, and not focused on the details.
Rationale & value to our mission
It will reducing cloud cost for communities and gives them a better user experience overall, which helps us retain existing communities and grow better organically. By standardizing around using shared nodes, complexity is reduced for 2i2c engineers overall as well, reducing complexity for us.
Definition of completion and success

No jupyterhub deployment provides users the choice of starting on a dedicated node like "small" / "medium" / "large" / "huge" as provided historically

It is still okay for jupyterhub deployments to allow users to start on dedicated nodes of various kinds, but that should be a complement, not the default.
It is still okay for jupyterhub deployments to provide the choices of "small" / "medium" / "large" / "huge", but they should not start on dedicated nodes. For example awi-ciroh was configured quickly like this to quickly transition to node sharing on n2-highmem-16 machines without breaking user experience, see https://github.com/2i2c-org/infrastructure/issues/2555.

Proposed leads and team
Reference and information

Thanks for writing this up, @consideRatio. I would love some help in helping me evaluate this goal - I don't fully understand why the current CPU and memory limits are set the way they are, especially that the description does not match the actual values set for CPU limits (for example, see https://github.com/2i2c-org/infrastructure/blob/5c57c9d6e263f1ecc88b0d29625faa9751165b73/config/clusters/leap/common.values.yaml#L158). It doesn't quite match the mental model I have for how limits work. Have you written up about this somewhere? I'd love to read more, because I don't understand how this currently works at all.

@yuvipanda yes sorry about not communicating clearer about this, its very relevant that that the current state is better documented, and also evaluated and refined!
I'd really love to sync up about this in a chat focused on the topic of requests/limits. If we could have that before I start to write about current state, it would be really helpful for me! Maybe we can find time next week?


js with html results without html cell

a common idiom is to use an html cell to make a DIV and then use a JS cell (and d3) to render its contents.  the output of the JS cell is not used, and its results appear above it (in the HTML cell) instead of where results normally appear.
this could be improved if we had a function like beaker.addOutput() that returned the DIV of the output of the currently executing cell, or possibly created a multi-output container and returned the DIV of one of the outputs.
there are some subtle issues here.  when this function runs, there may be no output at all yet, or it might not be an HTML output.  i think for d3 to work, it would have to synchronously set this, before the cell finishes evaluating.
another question is what happens to the regular return value of the JS, or it errors out (that's what the multi-output container is about).

why can't the JS cell just start with beaker.print("

");
? it doesn't seem to work...

something like beaker.displayHTML(this, ....) should work


Add articles to site search

Add articles to site search:
Since there are tags pages and because we wanted the articles URLs to be in /articles/... rather than /articles/article/..., I had to add a feature to the site crawler that skips indexing those pages.
I also had to move the <h1> out of the article header because the indexer was not associating the following content with the h1

cc @arthurevans


lncli: take chan_id as uint64 in getchaninfo

When taking in chan_id as a int64, there are some channels that cannot
be givn to lncli because they are out of range for an int64.
Pull Request Checklist

[x] All changes are Go version 1.16 compliant
[ ] Your PR passes all CI checks. If a check cannot be passed for a justifiable reason, that reason must be stated in the commit message and PR description.
[x] If this is your first time contributing, we recommend you read the Code Contribution Guidelines

[x] The code being submitted is commented according to Code Documentation and Commenting
[x] Commits have a logical structure according to Ideal Git Commit Structure

[x] For new code: Code is accompanied by tests which exercise both the positive and negative (error paths) conditions (if applicable)
[ ] For bug fixes: If possible, code is accompanied by new tests which trigger the bug being fixed to prevent regressions
This seems overkill, for such a small change.
[x] Any new logging statements use an appropriate subsystem and logging level
[x] For code and documentation: lines are wrapped at 80 characters (the tab character should be counted as 8 characters, not 4, as some IDEs do per default)
[x] A description of your changes should be added to running the release notes for the milestone your change will land in.

Updated with a clearer release note


Improve UX for creating role and group descriptions

@infinitetrooper the images are empty

They're loading now

@infinitetrooper the are really not! 😆
@riteshkew are you able to see it?

Schrodinger's Screenshots


[SDL2] update to <2.0.18>

Library name: SDL2
New version number: 2.0.18
Other information that may be useful (release notes, etc...)
https://www.libsdl.org/download-2.0.php

@jz315 , This issue will be fixed by #21848

This issue will be fixed by https://github.com/microsoft/vcpkg/pull/22586


feat: Update Compute Engine API to revision 20241015

We expect some breaking changes here, but should review them before merging.

Note: we'll release this as a new major version of the library.


fix DepositTransaction::rlp() to match op-geth

Motivation
The RLP encoding for Optimism DepositTransactions did not match the op-geth implementation. Deposit transactions created and encoded by ethers-rs were previously not being accepted by op-geth due to this.

Solution

Fix DepositTransaction::rlp() to match op-geth DepositTx::encode(). The types are now encoded to match op-geth: https://github.com/ethereum-optimism/op-geth/blob/optimism/core/types/deposit_tx.go#L29
I generated the expected Go output as follows (place this in op-geth core/types/deposit_tx_test.go):
package types

import (
	"bytes"
	"encoding/hex"
	"math/big"
	"testing"

	"github.com/ethereum/go-ethereum/common"
)

func TestEncodeDepositTx(t *testing.T) {
	to := common.HexToAddress("0xa0Ee7A142d267C1f36714E4a8F75612F20a79720")
	depositTx := &DepositTx{
		SourceHash:          common.HexToHash("0x7113be8bbb6ff4bb99fae05639cf76cdecf5a1afbc033b9a01d8bb16b00b9a80"),
		From:                to,
		To:                  &to,
		Mint:                big.NewInt(10000000000000000),
		Value:               big.NewInt(10000000000000000),
		Gas:                 21000,
		IsSystemTransaction: false,
		Data:                nil,
                // for the with_data test
                // Data:                []byte("nootwashere"),
	}
	bytes := &bytes.Buffer{}
	depositTx.encode(bytes)
	t.Log(hex.EncodeToString(bytes.Bytes()))
}

Note: the existing test test_rlp_encode_deposited_tx is probably not exactly correct? Should I remove/update it?
PR Checklist

[x] Added Tests
[ ] Added Documentation
[ ] Breaking changes

@mattsse good question, I don't think source_hash and is_system_tx should be Options since they're not in the Go impl. Not sure about mint (the Go impl has it tagged as rlp:"nil" - let me test that)

but if all of them are set, then this change doesn't have an effect right, because rlp_opt simply calls append, right?

i thought so, but the result i'm getting (before the change) is:
f863a07113be8bbb6ff4bb99fae05639cf76cdecf5a1afbc033b9a01d8bb16b00b9a80d594a0ee7a142d267c1f36714e4a8f75612f20a7972094a0ee7a142d267c1f36714e4a8f75612f20a79720872386f26fc10000c8872386f26fc10000c38252088080
compared to the go result of:
f860a07113be8bbb6ff4bb99fae05639cf76cdecf5a1afbc033b9a01d8bb16b00b9a8094a0ee7a142d267c1f36714e4a8f75612f20a7972094a0ee7a142d267c1f36714e4a8f75612f20a79720872386f26fc10000872386f26fc100008252088080
this seems strange, because you're right, it should just be encoding the value inside the option. i'll investigate more

I see, I think another problem is Data, which looks like a non optional []byte which is always encoded?
and iirc an empty []byte is encoded as an rlp header

yep i also changed data to use unwrap_or_default, which matches the go encoding when you set it to nil, so i think that's ok - i'm guessing go rlp-encodes []byte(nil) and []byte{} the same?

I left source_hash and is_system_tx as unwrap_or_default because they shouldn't be encoded as None ever imo.

yeah, they are required:
https://github.com/anton-rs/op-reth/blob/clabby/fixes/crates/primitives/src/transaction/optimism.rs#L12

(maybe we should change those to not be options)

agree

@mattsse i went ahead and updated source_hash and is_system_tx to not be options, let me know if you want me to leave or change back

I think that's the right decision

@mattsse what's a good move for fixing the serde_txpool_content test? it appears to me that the existing json-string in that test should only be using if #[cfg(not(feature = "optimism"))], i can make another json string for if the optimism feature is enabled (or just throw a #[cfg(not(feature = "optimism"))] on the whole test?)

@noot sorry, for late reply,
we can remove this test entirely, no longer needed since we're transitioning away from these types for alloy migration anyway

@mattsse np, test removed!

fyi @merklefruit


Add Golang lint to GitHub Actions for static Go code formatting scanning

Is your feature request related to a problem?
N/A
What solution do you propose?
Golang lint is a fast Go linters runner. It runs linters in parallel, uses caching, supports yaml config. It’s used to make sure code adheres to common Go practices. It supports enable many different types of linters.
I think we can introduce it to Notation to enable static code formatting scanning in each pull request.
What alternatives have you considered?
N/A
Any additional context?
No response

Hi, I'm interested in the CI task like this. Do you need help? Can I pick up this task?

Hi @tungbq , thanks for your interest! Yes, we can assign this issue to you.

Updates:

Research the https://github.com/golangci/golangci-lint-action official GitHub action for golangci-lint
Add golangci-lint-action to the CI workflows as it's the official GitHub action for golangci-lint from its authors. The action runs golangci-lint and reports issues from linters.
Name the new workflow as golangci-lint-action in .github/workflows/go-lint.yml
Current behaviour:

Run golangci-lint on every PR
Report only new issue generated from the PR
Beside of PR events, there has an option in the trigger event to allow us manually run the workflow if needed (workflow_dispatch:)

Created new PR #723 for this task.


fix: 6560 nullable required fields

🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of
the pull request.
Description
This PR fixes an issue with JSOM schema based fields that are required and nullable at the same time. More details in issue.
Fixes #6560
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Screenshots/Sandbox (if appropriate/relevant):

Codesandbox for issue reproduction

Screenshot of failing test before fix:

Screenshot of passing test after fix:

How Has This Been Tested?

Verified in a minimal local sample based on Codesandbox from issue
Added unit test before fixing the issue

Test Environment:

OS: MacOS 13.2
NodeJS: v18.19.0

"@graphql-mesh/cli": "^0.88.6",
"@graphql-mesh/json-schema": "^0.98.0",
"graphql": "^16.8.1"

Checklist:

[x] I have followed the
CONTRIBUTING doc and the
style guidelines of this project
[x] I have performed a self-review of my own code
[ ] N.A. I have commented my code, particularly in hard-to-understand areas
[ ] N.A. I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works, and I have added a
changeset using yarn changeset that bumps the version
[x] New and existing unit tests and linter rules pass locally with my changes
[ ] N.A. Any dependent changes have been merged and published in downstream modules

These changes actually updated a bunch of snapshots tests. As far as I can see, these tests have been "false positives" before this fix. All those now optional fields should have been optional all the time.
The scope of this makes me wonder why this wasn't noticed earlier. 😅 😬
I also wonder whether this fix might be seen as a breaking change for consumers of GraphQL Mesh as a lot of types might now switch to optional. This not only changes the GraphQL schemas but also any generated TypeScript code based on it. That code then likely breaks compiling as additional non-null checks are required now. On the other hand, this might actually save some people from runtime issues as their Typescript compiler currently "falsely thinks" a field is always present but it actually can be missing. 🤔

That code piece is needed for complex cases with unions (allOf and anyOf). If we remove it, a JSON schema that has a prop required in parent but not in the child (anyOf or allOf) will be nonnullable which is not expected. Instead, I followed a different approach here;
https://github.com/ardatan/graphql-mesh/pull/6563


color-link indent-char no longer works

I have my indent-char color set as black, but since the view refactor it no longer works (the indent-char stays white/normal).

Thanks for catching that!


Move components under integration to integration/service

@wangyoucao577
Proposal:
Move following components and adjust includes in cmd and related packages

integration/oasis to integration/service/oasis

Put integration/oasis/osrmconnector in integration/service/osrmconnector
Put integration/oasis/searchconnector in integration/service/searchconnector
Other service could use this one to communicate with osrm and search

integration/ranking* to integration/service/ranking*
integration/traffic* to integration/service/traffic*
intergration/wayids2nodeids to integration/service/wayid2nodeids
integration/wayidsmap to integration/service/wayidsmap
integration/osmfiles to integration/service/osmfiles

After this, the remaining folders under integration are

cmd
doc
graph   // may be this one could be moved to pkg/api or service
pkg
service
util

In my local, I create several tools for ad-hoc testing, such as osrm-connector-test and search-connector-test, can I upload them to cmd or cmd/tools

I feel some confusion on the word service. Are all the functional packages services? E.g., wayids2nodeids  and  wayidsmap seem only functional packages, can we call them service?
Moreover, graph is not good enough so far, I prefer to move it into util instead of api. For all tools, I'll suggest to put them into cmd/ directly, no necessary to have more folder level I think.

graph -> util is good
All tools into cmd/ for now
Let's only put reasonable package to service for now.  What about wayids2nodeids and wayidsmap go to util, it provides functionality for us.


preload scss has been added hash

Version
4.5.9
Environment info

  System:
    OS: Windows 10 10.0.18363
    CPU: (12) x64 Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
  Binaries:
    Node: 14.6.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.14.6 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 87.0.4280.141
    Edge: Spartan (44.18362.449.0)
  npmPackages:
    @ant-design/icons-vue:  5.1.9
    @vue/babel-helper-vue-jsx-merge-props:  1.2.1
    @vue/babel-helper-vue-transform-on:  1.0.0
    @vue/babel-plugin-jsx:  1.0.1
    @vue/babel-plugin-transform-vue-jsx:  1.2.1
    @vue/babel-preset-app:  4.5.10
    @vue/babel-preset-jsx:  1.2.4
    @vue/babel-sugar-composition-api-inject-h:  1.2.1
    @vue/babel-sugar-composition-api-render-instance:  1.2.4
    @vue/babel-sugar-functional-vue:  1.2.2
    @vue/babel-sugar-inject-h:  1.2.2
    @vue/babel-sugar-v-model:  1.2.3
    @vue/babel-sugar-v-on:  1.2.3
    @vue/cli-overlay:  4.5.10
    @vue/cli-plugin-babel: ~4.5.9 => 4.5.10
    @vue/cli-plugin-eslint: ~4.5.9 => 4.5.10
    @vue/cli-plugin-router: ~4.5.9 => 4.5.10
    @vue/cli-plugin-typescript: ~4.5.9 => 4.5.10
    @vue/cli-plugin-vuex: ~4.5.9 => 4.5.10
    @vue/cli-service: ~4.5.9 => 4.5.10
    @vue/cli-shared-utils:  4.5.10
    @vue/compiler-core:  3.0.5
    @vue/compiler-dom:  3.0.5
    @vue/compiler-sfc: ^3.0.5 => 3.0.5
    @vue/compiler-ssr:  3.0.5
    @vue/component-compiler-utils:  3.2.0
    @vue/eslint-config-standard: ^5.1.2 => 5.1.2
    @vue/eslint-config-typescript: ^5.0.2 => 5.1.0
    @vue/preload-webpack-plugin:  1.1.2
    @vue/reactivity:  3.0.5
    @vue/runtime-core:  3.0.5
    @vue/runtime-dom:  3.0.5
    @vue/shared:  3.0.5
    @vue/web-component-wrapper:  1.2.0
    @vuedx/vue-virtual-textdocument:  0.4.1
    ant-design-vue: ^2.0.0-rc.7 => 2.0.0-rc.8
    eslint-plugin-vue: ^7.4.1 => 7.4.1
    typescript: ^4.1.3 => 4.1.3
    vue: ^3.0.5 => 3.0.5
    vue-eslint-parser:  7.3.0
    vue-hot-reload-api:  2.3.4
    vue-loader:  15.9.6 (16.1.2)
    vue-router: ^4.0.2 => 4.0.3
    vue-style-loader:  4.1.2
    vue-template-es2015-compiler:  1.9.1
    vue-types: ^3.0.1 => 3.0.1
    vuex: ^4.0.0-rc.2 => 4.0.0-rc.2
    vuex-module-decorators: ^1.0.1 => 1.0.1
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce
css: {
    loaderOptions: {
      scss: {
        additionalData: `@import "~@/style/index.scss";`,
      },
    },
  },

i have set this config in vue.config.js,but some global class have been added hash after the selector
What is expected?
no hash
What is actually happening?
have hash

Thanks for submitting this issue! Due to our limited time, we ask you to include a reproduction link to a minimal full reproduction of your problem (for example in a GitHub repository) so we can find what is causing the issue. Thank you for your understanding!

Thanks for submitting this issue! Due to our limited time, we ask you to include a reproduction link to a minimal full reproduction of your problem (for example in a GitHub repository) so we can find what is causing the issue. Thank you for your understanding!


No upgrade instructions for 0.17.x to 0.18.x

https://keptn.sh/docs/install/upgrade/ contains instructions for upgrading from 0.16.x to 0.17.x but no instructions to upgrade from 0.17.x to 0.18.x.
We actually don't have any "basic" upgrade instructions.  We used to have the keptn upgrade reference page (actually, we still do -- separate problem!) and we have instructions for upgrading the helm chart in an air-gapped environment (https://keptn.sh/docs/install/helm-install/#execute-helm-upgrade-without-internet-connectivity) but buried at the bottom of the helm installation page.
Here is my proposal for modifying the https://keptn.sh/docs/install/helm-install/#execute-helm-upgrade-without-internet-connectivity page:

Begin with caveat that you need to upgrade one release at a time -- not try to skip from 0.11.x to 0.18.2 in one fell swoop
Recommend reading Release Notes before upgrading
Show basic helm upgrade command -- it should be similar to the command shown for the 0.16.x to 0.17.x but I don't know if one always needs to specify the helm chart or only if one has modified it.  What if I customized the helm chart for the old release -- perhaps a bigger size or something.  I probably need to apply those changes to the new helm chart, right?  And use any --set options I specified for old release.
Should I mention that they may need to upgrade integrations they are using, or docker images used, etc?  I don't want to go into details but it would be nice to be comprehensive about what may be required.
Move info about upgrading in air-gapped/offline environment here -- or should we make this a separate page that is right after this one since it is somewhat big and not relevant to most users?
Then have subsections with details about specific upgrades -- we have excellent material for 0.16.x to 0.17.x
Are there any specific issues that should be documented for 0.17.x t 0.18.0/0.18.2?

I believe it was fixed: https://keptn.sh/docs/install/upgrade/#upgrade-from-keptn-0-17-x-to-keptn-0-18-x

@thisthat Confirmed that we do not have manual upgrade steps required from 0.17.x -> 0.18.x, nor for 0.18.x -> 0.17.x.  The "Upgrade" section has been restructured to have general upgrade information with subsections for each recent release and a table that links to upgrade instructions and release notes for older releases.


fix(attestation): Parse correctly workflowrun ids

This patch fixes the attestation process when using API tokens since they were failing due to workflow run id not being available.
Refs: #783

Reworked the method to use a proper way to find Workflow Runs that matches the given organization (from API token or Robot Account).

Closing in favor of https://github.com/chainloop-dev/chainloop/pull/790


[FLINK-1460] fix typos

Fix some typos. Also fix some inconsistent uses of partition operator and partitioning operator in the codebase.

+1
LGTM

+1, can you merge it @hsaputra or should I?

@hsaputra @aljoscha I failed one check which I don't have much idea about. Could you please retest?

HI @aljoscha, thanks.
If you could merge it before later tonight please do. Otherwise I could do it later tonight if you did not have time to get to this one =)

@coderxiang, ah that the tests do comparison in the after method so it is hard to figure out which method fail. But seemed like other builds passed and I am sure that your change does not cause this problem

Merged, thanks for the fix @coderxiang

Changes Unknown when pulling acf52748f7ed9fe64d9773acbab5774b308e47eb on coderxiang:typo into ** on apache:master**.


Bind to an Ancestor with Prism

People using Prism do not define BindingContext in code behind and Prism documentation doesn't cover how to bind to an Ancestor. Can the docs cover this here?

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

ID: 3f73553f-8c35-877b-0a34-db9b51df93be
Version Independent ID: d51b2ace-0519-6309-7417-d29a582a4de2
Content: Xamarin.Forms Relative Bindings - Xamarin
Content Source: docs/xamarin-forms/app-fundamentals/data-binding/relative-bindings.md
Product: xamarin
Technology: xamarin-forms
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @HelenMamalaki
We aren't going to add any Prism specific docs, as if we do that we'd then have to add them for every other popular MVVM framework.
With that said, is your issue that you want to know how to set the BindingContext in XAML?


grunt task to create distributable for linux

@MarcelGerber if you could have a look, now that https://github.com/zaggino/brackets-electron/issues/38 is done, it shouldn't require much code

We only need to add an author.email field to our package.json, then we're all good here.

any idea what that email should be?

Just looked it up, brackets-shell uses<EMAIL_ADDRESS>(https://github.com/adobe/brackets-shell/blob/da088ef847ad3efce726a24be087bd7b92e9a77f/installer/linux/debian/control#L9).
Not sure if we can use an official email here, though...

I think we can, that group is a public one, not private: https://groups.google.com/forum/#!forum/brackets-dev