Unable to resolve module @babel/runtime/helpers/interopRequireDefault – without changing anything

React Native version:
System:
    OS: Linux 5.0 Ubuntu 19.04 (Disco Dingo)
    CPU: (8) x64 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz
    Memory: 1.99 GB / 31.28 GB
    Shell: 5.5.1 - /usr/bin/zsh
  Binaries:
    Node: 13.2.0 - ~/.nvm/versions/node/v13.2.0/bin/node
    Yarn: 1.19.2 - ~/.nvm/versions/node/v13.2.0/bin/yarn
    npm: 6.13.4 - ~/.nvm/versions/node/v13.2.0/bin/npm
    Watchman: 4.9.0 - /home/linuxbrew/.linuxbrew/bin/watchman
  SDKs:
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3
      System Images: android-28 | Google APIs Intel x86 Atom
  npmPackages:
    react: 16.9.0 => 16.9.0
    react-native: 0.61.5 => 0.61.5
  npmGlobalPackages:
    react-native-cli: 2.0.1

Steps To Reproduce
I opened a project that I've been working on for a few weeks, and I decided to run it after not having touched it for a few days:

Run npx react-native start
Run npx react-native run-android

I expected the project to start in Android. Instead, I got:
Looking for JS files in
   /foo

Loading dependency graph, done.
 BUNDLE  [android, dev] ./index.js ░░░░░░░░░░░░░░░░ 0.0% (0/1)::ffff:<IP_ADDRESS> - - [08/Jan/2020:16:10:27 +0000] "GET /index.bundle?platform=android&dev=true&minify=false HTTP/1.1" 500 - "-" "okhttp/3.12.1"
error: bundling failed: Error: Unable to resolve module `@babel/runtime/helpers/interopRequireDefault` from `index.js`: @babel/runtime/helpers/interopRequireDefault could not be found within the project.

If you are sure the module exists, try these steps:
 1. Clear watchman watches: watchman watch-del-all
 2. Delete node_modules: rm -rf node_modules and run yarn install
 3. Reset Metro's cache: yarn start --reset-cache
 4. Remove the cache: rm -rf /tmp/metro-*
    at ModuleResolver.resolveDependency (/foo/node_modules/metro/src/node-haste/DependencyGraph/ModuleResolution.js:186:15)
    at ResolutionRequest.resolveDependency (/foo/node_modules/metro/src/node-haste/DependencyGraph/ResolutionRequest.js:52:18)
    at DependencyGraph.resolveDependency (/foo/node_modules/metro/src/node-haste/DependencyGraph.js:282:16)
    at Object.resolve (/foo/node_modules/metro/src/lib/transformHelpers.js:267:42)
    at /foo/node_modules/metro/src/DeltaBundler/traverseDependencies.js:426:31
    at Array.map (<anonymous>)
    at resolveDependencies (/foo/node_modules/metro/src/DeltaBundler/traverseDependencies.js:423:18)
    at /foo/node_modules/metro/src/DeltaBundler/traverseDependencies.js:275:33
    at Generator.next (<anonymous>)
    at asyncGeneratorStep (/foo/node_modules/metro/src/DeltaBundler/traverseDependencies.js:87:24)
 BUNDLE  [android, dev] ./index.js ░░░░░░░░░░░░░░░░ 0.0% (0/1), failed.

Of course, the file exists:
ls -l<EMAIL_ADDRESS>-rw-r--r-- 1 werner werner 147 Oct 26  1985<EMAIL_ADDRESS>
So I don't know why it wouldn't find it. Note that I have not changed anything in the project, and even reverting to an old commit from a few weeks ago does not solve this problem.
A colleague of mine has exactly the same project and can run it without problems. I have even tried to run a copy of his directory including the downloaded node_modules folder, and it fails.
I could also reproduce this on a fresh install of NVM and Node under macOS.
I could not reproduce this in a completely new RN project. But cloning my project into another folder and running npm install, the error persists.
Trying the following did not work:
watchman watch-del-all
rm -rf node_modules
rm -rf /tmp/metro-*
npm add @babel/runtime
npm i
npx react-native start --reset-cache

This is the package.json:
{
  "name": "foo",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint ."
  },
  "dependencies": {
    "async": "^2.1.2",
    "base-64": "^0.1.0",
    "body-parser": "^1.15.2",
    "colors": "^1.1.2",
    "cors": "^2.8.1",
    "crypto-js": "^3.1.5",
    "express": "^4.14.0",
    "localforage": "^1.4.3",
    "pako": "^1.0.3",
    "pem": "^1.8.3",
    "react": "16.9.0",
    "react-native": "0.61.5",
    "react-native-gesture-handler": "^1.5.2",
    "react-native-progress": "^4.0.2",
    "react-native-reanimated": "^1.4.0",
    "react-native-simple-gauge": "^0.2.2",
    "react-native-video": "^5.0.2",
    "react-native-video-controls": "^2.2.3",
    "react-navigation": "^4.0.10",
    "react-navigation-stack": "^1.10.3",
    "rest": "^2.0.0"
  },
  "devDependencies": {
    "@babel/core": "^7.7.7",
    "@babel/runtime": "^7.7.7",
    "@react-native-community/eslint-config": "^0.0.6",
    "@react-native-community/eslint-plugin": "^1.0.0",
    "babel-jest": "^24.9.0",
    "eslint": "^6.8.0",
    "eslint-config-prettier": "^6.9.0",
    "eslint-plugin-prettier": "^3.1.2",
    "jest": "^24.9.0",
    "license-checker": "^25.0.1",
    "metro-react-native-babel-preset": "^0.56.4",
    "reactotron-react-native": "^4.0.2"
  },
  "jest": {
    "preset": "react-native"
  },
}

I have seen:

https://github.com/facebook/react-native/issues/21310
https://stackoverflow.com/questions/52486219/unable-to-resolve-module-babel-runtime-helpers-interoprequiredefault
https://stackoverflow.com/questions/52686952/module-babel-runtime-helpers-interoprequiredefault-does-not-exist-in-the-hast/55676212
https://stackoverflow.com/questions/58989571/react-native-unable-to-resolve-module-babel-runtime-helpers-interoprequirede

but none of the solutions there worked for me.

I am also having this issue.
If you troubleshoot a bit, you will find out that there is an issue when building the haste-map.
Basically nothing under node_modules is loaded.
It is somehow linked to watchman
Try to 1) locate this line in node_modules/jest-haste-map/build/index.js
const crawl =
      canUseWatchman && this._options.useWatchman
        ? _watchman.default
        : _node.default;

change watchman.default to _node.default (basically tell it to use _node.default)

and restart the packager with the reset option
I am not sure why nothing is loaded when using watchman, I have symlinks and use wml and I think it is somehow because of this.
Using macos, watchman 4.9.0 and latest rn

I will try to debug this, thanks. Watchman 4.9.0 has been the latest version since 2017, so it's weird that this would just occur now.
In the meantime I could reproduce on macOS and Linux, but my colleague running the same project under Linux has no issues running it. I will compare his utility versions.
I could somehow get my project running by reverting to an older commit, removing node_modules/package.lock, running npm i, then upgrading to the latest Git revision, then running npm i again. But I am not sure if this is not just a random observation.

I can confirm that changing the following in node_modules/jest-haste-map/build/index.js is a workaround:
    const crawl =
      canUseWatchman && this._options.useWatchman
        ? _watchman.default
        : _node.default;

    const crawl =
      canUseWatchman && this._options.useWatchman
        ? _node.default
        : _node.default;

so weird right! glad to see it's not just me

Note: Instead of modifying the file, I've uninstalled watchman and everything seems to run for the time being.

@slhck any update on this issue as I also use wml in Linux and now, watchman also causes the same error as soon as I run watch-del-all on the project. I tried uninstalling watchman and installed it again but when I build my project and run wml start to copy the local dependency and run the project, I get another error that the local dependency is not found in node_modules but when I run watch-del-all again, it's found but the problem with the node_modules/jest-haste-map/build/index.js starts again.
@nonotest do you have another way of fixing it because going into that file to change it isn't good.

Sorry no other way.. :(
On Wed, 5 Feb 2020 at 5:47 pm, Oscar<EMAIL_ADDRESS>wrote:

@slhck https://github.com/slhck any update on this issue as I also use
wml in Linux and now, watchman also causes the same error as soon as I run
watch-del-all on the project. I tried uninstalling watchman and installed
it again but when I build my project and run wml start to copy the local
dependency and run the project, I get another error that the local
dependency is not found in node_modules but when I run watch-del-all again,
it's found but the problem with the
node_modules/jest-haste-map/build/index.js starts again.
@nonotest https://github.com/nonotest do you have another way of fixing
it because going into that file to change it isn't good.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/27712?email_source=notifications&email_token=AATO4LKD2DCKB2DRKYS2RB3RBKDLHA5CNFSM4KEK2SJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEK2ZG3Q#issuecomment-582325102,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATO4LOEC4Y36QZV7MTF3BTRBKDLHANCNFSM4KEK2SJA
.

Sorry, I haven't figured out any other solution. Just get rid of watchman and everything should be fine.

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions.

It's not fixed

基础包过于简单导至babel_runtime_helpers_interopRequireDefault没有引入

I'm having the same issue on iOS

+1

Getting same error.
Yarn add @babel/runtime not working.
react-native start --reset-cache not working.
Uninstalling watchman not working.
Below command is also not working for me.
watchman watch-del-all && rm -rf $TMPDIR/react-native-packager-cache-* && rm -rf $TMPDIR/react-* && rm -rf $TMPDIR/metro-* && rm -rf node_modules/ && yarn cache clean --force && yarn install && react-native start --reset-cache
React Native Environment Info:
System:
OS: macOS 10.14.6
CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
Memory: 82.13 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.16.3 - /usr/local/bin/node
Yarn: 1.19.1 - /usr/local/bin/yarn
npm: 6.9.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.1, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
Android SDK:
API Levels: 28, 29
Build Tools: 28.0.3, 29.0.2
System Images: android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom, android-29 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.5 AI-191.8<IP_ADDRESS>00203
Xcode: 11.1/11A1027 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.59.9 => 0.59.9
npmGlobalPackages:
react-native-cli: 2.0.1
If there are some other solutions, please suggest. Totally stuck at this problem for 2 days.

Same situation, only watchman deleting helps but that's not the solution because my other project requires watchman

rm -rf /tmp/metro-* worked for me.
This is the last suggestion of the message to try these things:

Clear watchman watches: watchman watch-del-all
Delete node_modules: rm -rf node_modules and run yarn install
Reset Metro's cache: yarn start --reset-cache
Remove the cache: rm -rf /tmp/metro-*

maybe it helps to fix the problem:
As far as I see from a Process Monitor the node.exe process tries to open interopRequireDefault file without .js extension
from node_modules\@babel\runtime\helpers\interopRequireDefault
and the operating system says PATH NOT FOUND
At the same time, interopRequireDefault.js lays in the same helpers folder.
As an experiment, I made a copy of interopRequireDefault.js without extension, after that file interopRequireDefault can be found by node process, but, even after receiving the success code from the operating system, the node process continues to search that file in parent folders as it usually does when cannot find some module.

my env: Windows 10, RN 0.63.3, Monorepo
command: npx react-native run-android --variant release
gives
Error: Unable to resolve module @babel/runtime/helpers/interopRequireDefault from app.tsx: @babel/runtime/helpers/interopRequireDefault could not be found within the project.

as was mentioned above, looks like the presence of this property
watchFolders: [${__dirname}/../..],
in metro.config.js solves the problem. I have a monorepo and mobile app is one of packages, that is why I need ../..
BTW in my case, interopRequireDefault  problem appears only when I make a release build with
react-native run-android --variant release
developing mode ( react-native run-android ) works fine even without metro.config.js file
Also, there is no problem if a project is not configured as Monorepo

npmPackages:
@react-native-community/cli: Not Found
react: 16.14.0 => 16.14.0
react-native: 0.63.3 => 0.63.3
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found

I had the same error message but only when using Formik  (in expo snack only ) so i found this solution:
added the formik dependecy to the json file
{
"dependencies": {
"yup": "*",
"formik": ">= 0.11.x < 2",
"expo-constants": "~13.1.1",
"expo-image-picker": "~13.1.1",
"@expo/vector-icons": "^13.0.0",
"react-native-paper": "4.9.2",
"react-native-gesture-handler": "~2.2.1",
"react-native-gesture-handler/Swipeable": "~2.2.1",
"babel-preset-react-native": "5.0.2"
}
}

I accidentally deleted my node_modules and package-lock.json. I used npm i to regenerate them and suddenly I was getting the above error. I solved it by uninstalling the app and using the following commands.
npx jest --clearCache
npm update
npm i
npx react-native run-android
Hope this helps you.

For anyone coming with the same issue but on iOS make sure you don't have your phone plugged in.

For anyone seeing this with Expo in a monorepo, I had the wrong workspaceRoot here:
/**
 * @type {import('expo/metro-config')}
 */
const { getDefaultConfig } = require('expo/metro-config')
const path = require('path')

const projectRoot = __dirname
const workspaceRoot = path.resolve(__dirname, '../..')

const config = getDefaultConfig(projectRoot)

config.watchFolders = [workspaceRoot]
config.resolver.nodeModulesPaths = [
  path.resolve(projectRoot, 'node_modules'),
  path.resolve(workspaceRoot, 'node_modules'),
]

config.resolver.extraNodeModules = {
  modules: workspaceRoot,
}

console.log('config', config)

module.exports = config

I had to change it from .. to ../...

For anyone seeing this with Expo in a monorepo, I had the wrong workspaceRoot here:
/**
 * @type {import('expo/metro-config')}
 */
const { getDefaultConfig } = require('expo/metro-config')
const path = require('path')

const projectRoot = __dirname
const workspaceRoot = path.resolve(__dirname, '../..')

const config = getDefaultConfig(projectRoot)

config.watchFolders = [workspaceRoot]
config.resolver.nodeModulesPaths = [
  path.resolve(projectRoot, 'node_modules'),
  path.resolve(workspaceRoot, 'node_modules'),
]

config.resolver.extraNodeModules = {
  modules: workspaceRoot,
}

console.log('config', config)

module.exports = config

I had to change it from .. to ../...

I am setting a monorepo right now and your pointer was a solution for me, editing metro.config.js from
module.exports = {
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: true,
      },
    }),
  },
};

to
const resolve = require('path').resolve;
const WORKSPACE_ROOT = resolve(PROJECT_ROOT, '../../');

console.log(PROJECT_ROOT);
module.exports = {
  transformer: {
    getTransformOptions: async () => ({
      transform: {
        experimentalImportSupport: false,
        inlineRequires: true,
      },
    }),
  },
  watchFolders: [WORKSPACE_ROOT],
};

Of interest: I found this happens with react-native start yet not expo start (though this is in a custom React Native Windows with Expo project, so may not apply to others).
As mentioned above, in my case the solution was to add the monorepo root to the watch folders: https://github.com/facebook/react-native/issues/27712#issuecomment-715780864

Deleting watchman fixes it.
info Fetching system and libraries information... (node:87314) [DEP0040] DeprecationWarning: Thepunycodemodule is deprecated. Please use a userland alternative instead. (Usenode --trace-deprecation ...` to show where the warning was created)
System:
OS: macOS 15.1
CPU: (11) arm64 Apple M3 Pro
Memory: 238.56 MB / 18.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 22.11.0
path: /opt/homebrew/opt/node@22/bin/node
Yarn:
version: 1.22.22
path: /opt/homebrew/bin/yarn
npm:
version: 10.9.0
path: /opt/homebrew/opt/node@22/bin/npm
Watchman: Not Found
Managers:
CocoaPods:
version: 1.16.2
path: /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 24.1
- iOS 18.1
- macOS 15.1
- tvOS 18.1
- visionOS 2.1
- watchOS 11.1
Android SDK:
API Levels:
- "33"
- "34"
- "34"
- "35"
Build Tools:
- 30.0.3
- 33.0.1
- 34.0.0
- 35.0.0
System Images:
- android-UpsideDownCakePrivacySandbox | Google Play ARM 64 v8a
- android-VanillaIceCream | Google Play ARM 64 v8a
Android NDK: Not Found
IDEs:
Android Studio: 2024.2 AI-242.23339.11.2421.12550806
Xcode:
version: 16.1/16B40
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.13
path: /opt/homebrew/opt/openjdk@17/bin/javac
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli":
installed: 15.0.0
wanted: 15.0.0
react:
installed: 18.3.1
wanted: 18.3.1
react-native:
installed: 0.76.1
wanted: 0.76.1
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: true
newArchEnabled: true
info React Native v0.76.2 is now available (your project is running on v0.76.1).
info Changelog: https://github.com/facebook/react-native/releases/tag/v0.76.2
info Diff: https://react-native-community.github.io/upgrade-helper/?from=0.76.1&to=0.76.2
info For more info, check out "https://reactnative.dev/docs/upgrading?os=macos".
`

Understood a bit better now. This happens when running bare React Native projects in monorepos because the bare React Native's default Metro config does not include the monorepo root as a watchFolder (and watchFolders is more that just folders to watch for changes in – it's also about whether the dependencies get read at all). The Expo Metro config, by contrast, does support monorepos.
What you can do is use Microsoft's @rnx-kit/metro-config instead, which supports monorepos out of the box (as well as supporting react-native-macos and react-native-windows):
npm install --save-dev @rnx-kit/metro-config

Now change your metro.config.js as follows:
-const { getDefaultConfig, mergeConfig } = require("@react-native/metro-config");
+const { makeMetroConfig } = require("@rnx-kit/metro-config");
-
-/**
- * Metro configuration
- * https://facebook.github.io/metro/docs/configuration
- *
- * @type {import('metro-config').MetroConfig}
- */
-const config = {};
-
-module.exports = mergeConfig(getDefaultConfig(__dirname), config);
+module.exports = makeMetroConfig({
+  transformer: {
+    getTransformOptions: async () => ({
+      transform: {
+        experimentalImportSupport: false,
+        inlineRequires: false,
+      },
+    }),
+  },
+});


Let configuration cache handle cycles between included and root builds

@bot-gradle test ACC

OK, I've already triggered the following builds for you:

AllConfigCacheTestsPullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

Your PR is queued. See the queue page for details.


Funds stuck in pancake swap liquidity pool

I created a copy of this contract from bscscan and published it with a new name using remix 6.12 compiler version.
Seems to work on my test version seemed to also work fine in the liquidity pool.  However the final release version seem to be stuck in the liquidity pool, the tokens and liquidity LP appear.  However the tokens are not tradeable and the pool is not withdrawable despite 100% of liquidity owned.    I put 100% of the minted tokens + a few BNB into the pool initially seems to be slightly stuck.  I'm unsure what is causing this issue any ideas or suggestions to unstick this problem?

Bug fixed was a router issue

Bug fixed was a router issue

Can you elaborate on the router issue you observed? Might help the community

Yes, the problem was the contract hard coded in pancakeswap v1 router. When adding a pool to v2 the contract stalled at certain points the only solution was to turn the liquify variable to false to unlock it. However the correct course of action is to use the v2 router address!


Added a useful resource

Adding a helpful link that discusses bootstrap, I hope you will like this as it will add value to your repository and readers. Thank you.

There are many sites available where one can learn Bootstrap, so why favour exactly this one. Sorry, but I do not see it as useful as it just lists the HTML for a few components. But in Seaside you can work on the objects and messages level anyway and HTML is only the output. The framework wraps that for you.
BTW:
A good cheatsheet is also available from Bootstrap website itself. See https://getbootstrap.com/docs/5.0/examples/cheatsheet/
one has just to inspect in the browser.


building epdfinfo crashes emacs

What did you expect to happen?
I was prompted to build epdfinfo after using 'org-capture' on a new build of Doom. During the build it ran into errors and crashed froze emacs.
I'm on Ubuntu 18.04. #3244 also had Ubuntu-specific issues with epdfinfo building.

Steps to reproduce:

Cloned and built doom with empty config.el and packages.el
Ran 'org-capture'
Agreed to build epdfinfo

In the past I also encountered some issues when building epdinfo from Emacs. The problem came out to be related to pkginfo missing some critical lib on macOS, and I just had to eval this before running pdf-tools-install: (setenv "PKG_CONFIG_PATH" "/usr/local/lib/pkgconfig:/usr/local/Cellar/libffi/3.2.1/lib/pkgconfig"). If that doesn't help, could you try building the exec directly from the straight repos? At least, you'll get the complete output of the configure and make steps, and perhaps some clues to move forward.

Thanks for the suggestions! I tried those, but it worked after I updated gcc.


[Travis] Update CI to run with Xcode 6.4

Use Xcode 6.4 instead of Travis' beta support for 6.3.

:+1:

cc @tadeuzagallo


Update running-locally-for-development.md

Its necessary run yarn install also in app folders or its possible to run yarn recursively?

:/ There was an issue with the server on pnpm, which is why the server is not inside the app folder. I recommend using yarn for the server. However, you can use yarn for the app/ui and app/script

Nothing more, thanks


Jump improvements

Again, incredible work. Love revisiting this after a few months and discovering new features I thought about requesting. This ticket will focus on some thoughts about the new jump feature:

Labels are stretched by wider windows and appear blurry.

For better contrast, add square backgrounds with a plugin:scroller:jump_labels_bg_color. If you're concerned with config feature creep, this could inherit corner rounding & borders from windows and be "disabled" with a transparent color.

Thoughts on class-based jump? take the first (few) letters of window classes, with some special case for apps using a reverse domain notation like org.mozilla.firefox. With high certainty, I could enter jump expecting Code to be c and Firefox f. Labels could also be inherited from marksadd windowrules or assigned explicitly:
windowrulev2 = plugin:scroller:reservelabel f, class:(firefox)$

Thank you.

Labels are stretched: yes, they are rendered with 64 pixel fonts and stretched to the scaling factor you set. Depending on the alpha of the color you choose, they will also be more or less blurry. If you want them less blurry and smaller, change jump_labels_scale to 0.1, and the alpha of jump_labels_color, for example rgba(159e30ff). The alpha by default is 80 (0.5) so you can see behind the label.
Backgrounds: sorry, no, the main idea was to be able to see the windows' content. That is why the labels are "blurry" (alpha applied). If I add a background, suddenly you cannot see the window, which is the main idea behind this mode: find a window and jump to it.
Class-based jumps: this sounds nice, but I don't think it would make navigation faster or easier unless you have dozens of windows open. You would need different shortcuts for window classes, and move your hand from the "home row" or whichever key combination you chose for jump. I think for people who want to jump to certain applications very often, hyprscroller already provides with several mechanisms, like marks and trailmarks. jump is quite efficient and makes navigation fast without having to think. If I had to think about window classes and then move my fingers to the letters of that class, I think navigation would be less efficient, aside from adding a lot of complexity to the code for little gain. Now I just call the same jump, and my fingers are already prepared to type; it seems simple and natural.

This should definitely not be expected:

I don't mean a background across the whole window but rather a square behind the text. An outline would do just as well.
Makes sense. In my silly head I figured inheriting from marksadd would reduce friction, but if something were marked you'd just use that instead.

OK, I buy you 1) Fixed in 3db74fcbf3bd1e2dc27749b7ec8c501e3292acec
I am not going to add a background to labels in jump. I don't see how this is useful except for aesthetics, and even in that case it depends on whom you ask. I try to use my limited time adding features I find useful (first), and features other people may find useful, even if I don't (second), but you would need to convince me this adds something more than improved looks, because it even reduces usability by hiding part of the window content. Sorry, I hope you understand.


coding errars

plz fix deh missing brakeet in teh entplayer clazz, ty

Has been fixed :package: hot fix FTW


fix: golang release version match

Golang major releases follow major.minor only and patch releases follow major.minor.patch format. This change allows renovate to update Golang major/patch release versions.
This should also fix an old issue #189.
Signed-off-by: Noel Georgi<EMAIL_ADDRESS>

Thank you for your contribution!

I'll review this later.
I have a concern the treat of rc version.
https://github.com/golang/go/tags

And this preset should not affect other than aqua related packages.
This preset should restrict packages by file paths or something.

I have a concern the treat of rc version.

this will skip rc versions, only stable versions will be used, this regex is also used internally at work https://github.com/siderolabs/tools/blob/main/.github/renovate.json#L38

This preset should restrict packages by file paths or something.

Ahh, I see, to make sure only aqua managed files are only updated right??

Ahh, I see, to make sure only aqua managed files are only updated right??

Yes.

cool, I'll update the PR in a while.

I've updated the PR and added as a second commit, if it's needed I can rebase and force-push

Thank you for your update.

if it's needed I can rebase and force-push

Not needed. Thanks.

Only golang-go.json is updated and default.json isn't updated.
To update default.json too, we have to update utils.libsonnet's golangGo.
https://github.com/aquaproj/aqua-renovate-config/blob/5938f446c1dade2c044355a0adf1fcbdb6a2586c/jsonnet/golang-go.jsonnet#L5
https://github.com/aquaproj/aqua-renovate-config/blob/db8798106bb20f3b23f805293f44ec53cf816c2c/jsonnet/utils.libsonnet#L89-L92
But it's a bit complicated, so let me take a look.
By Jsonnet we could write code comments and made the code DRY, but the code became a bit complicated...
We will have to refactor Jsonnet when we will have a time.

It works well.
https://github.com/suzuki-shunsuke/test-renovate/blob/73bc8f1adff83fb64dbfbc2158b2e22e7357723a/renovate.json5#L6-L24

https://github.com/suzuki-shunsuke/test-renovate/pull/208

We can configure versioning in regexManager.
https://docs.renovatebot.com/configuration-options/#versioningtemplate

Hmm. 1.18.8 is updated to 1.20.
It is inconvenient if we want to specify the patch version too.

Ah, if we enable separateMinorPatch,
1.19 is updated 1.19.5. It looks good for me.

https://github.com/suzuki-shunsuke/test-renovate/pull/210

Fixed. Do you have any opinion?

Maybe we can use Go Modules Directive Versioning? 🤔
https://docs.renovatebot.com/modules/versioning/#go-modules-directive-versioning

And golang-version datasource also seems to be useful.
https://docs.renovatebot.com/modules/datasource/golang-version/
I'll try them.

:x: Go Modules Directive Versioning doesn't support x.y.z.

golang-version works well.

https://github.com/suzuki-shunsuke/test-renovate-2/pull/87
https://github.com/suzuki-shunsuke/test-renovate-2/pull/85
https://github.com/suzuki-shunsuke/test-renovate-2/blob/fe6af3bfa941b02fd18ed9679281987a3d62a41b/renovate.json5#L7-L43

I'm not sure the difference between golang-version and github-tags, but maybe golang-version is better.

I see that it updated to 1.19.5 and not 1.20 , am I understanding these PR's wrong?

https://github.com/suzuki-shunsuke/test-renovate-2/pull/87
https://github.com/suzuki-shunsuke/test-renovate-2/pull/85

would have expected a PR for 1.19.5 to 1.20

Oh, I see.
github-tags

https://github.com/suzuki-shunsuke/test-renovate/pull/208

Without separateMinorPatch

1.19 -> 1.20
1.18.8 -> 1.20

With separateMinorPatch

1.19 -> 1.20
1.18.8 -> 1.19.5

golang-version

https://github.com/suzuki-shunsuke/test-renovate-2/pull/87

1.18.8 -> 1.18.10

https://github.com/suzuki-shunsuke/test-renovate-2/pull/85

1.18.8 -> 1.19.5

Sorry. I'm a bit confused. Renovate is difficult. 😅

golang-version doesn't update minor version. 🤔
Let's use github-tags at the moment.

I confirmed 1.19.5 is updated to 1.20.

https://github.com/suzuki-shunsuke/test-renovate/pull/208

I set separateMinorPatch because I thought 1.x wasn't updated to 1.x.y, but this was my misunderstanding.
I confirmed 1.20 will be updated to 1.20.x without separateMinorPatch when 1.20.x will be released.

https://github.com/suzuki-shunsuke/test-renovate-3/pull/15

1.19 is updated to 1.19.5, because I set allowedVersion allowedVersions: "< 1.20".
So I'll remove separateMinorPatch.

Before releasing the new version, let me publish the prerelease version and test in a few days.

👍

https://github.com/aquaproj/aqua-registry/pull/9610

Released. https://github.com/aquaproj/aqua-renovate-config/releases/tag/1.5.2


Feature Request: Add JSON-to-CSV Download Button

Hello team,
We have implemented the InnerSource project platform in our organization and added a new feature: a 'Download' button in the dashboard. This feature allows users to easily download the results displayed from repos.json in CSV format.
We would like to contribute this feature back to the community.
Before proceeding, we wanted to check if this addition would provide value to the project. If so, we are eager to submit our contribution.
We would like to know if you are interested in this feature.
If so, do you have any guidelines for your implementation so that we can prepare PR
Looking forward to your feedback!
Best regards,
Silvan Belten
on behalf of Mercedes-Benz Tech Innovation GmbH
Provider Information

Hi Silvan,
thank you very much for using our portal and for suggesting this feature.
I think it is a good idea to offer an optional download option for the json file.
We are happy support you getting your contribution into the codebase.
If you need any guidance or input from our side just let us know.
Kind Regards,
Michael

Hi @sbelten Thank you for the tip, I will test the additional function as soon as possible. I'll try the function too
Best regard Marco D'Adamo!


Considering move Vue dep to peerDeps 😂

Which is that mean need to install vue by yourself
Cause some library(like element-ui) will notify you element-ui has unmet peer dependency vue when installing.
But still work fine, so this is just a considering thing.😂

Already moved, xixi


Pave the Foo.of() cowpath.

I'm planning on adding more .of() functions and so to avoid further
copypasta I'm providing some general utility functions here.

LGTM


Consider adding a Replayable interface for projectors

When replaying a projector that doesn't have a resetState method, a method not found exception is thrown that's hard to debug for first-timers.
Requiring a Replayable interface would make this more explicit. Alternatively, do a method_exists call and provide an error message to clarify that the package user must implement resetState.

Can do!

Seems like we already have a dedicated CouldNotResetProjector exception that gets thrown when a projector doesn't have a resetState method. If has a very clear message.  We also already have a test for this.
In what situation a method not found exception is thrown?

Hmm it was that method that I saw. My problem with the message is that I wasn't sure whether it was something I had to implement myself or something in the package or configuration. Maybe reword it so some sort of "Did you implement a resetState method?


Fix english bugs

5 fixes:

3 typos
1 incorrect capitalization
1 spelling error

Edited files:

content/ko/docs/concepts/cluster-administration/cloud-providers.md
content/ko/docs/concepts/configuration/organize-cluster-access-kubeconfig.md
content/ko/docs/concepts/workloads/pods/init-containers.md
content/ko/docs/contribute/participating.md
content/ko/docs/contribute/participating.md

Ah, this branch is already frozen. And I didn't squash my commits. I'll re-do this PR.


Refactoring validator

What problem does this PR solve?
#291
What is changed and how does it work?
use webhook.Validator to refactoring validator
unity the form of webhook
add Unit test for validator
Check List
Tests

Unit test

Code changes

Has Go code change

Side effects

Related changes

Does this PR introduce a user-facing change?:

NONE

Codecov Report

Merging #338 into master will increase coverage by 1.78%.
The diff coverage is 83.43%.

@@            Coverage Diff            @@
##           master    #338      +/-   ##
=========================================
+ Coverage   59.02%   60.8%   +1.78%
=========================================
  Files          55      51       -4
  Lines        3165    2947     -218
=========================================
- Hits         1868    1792      -76
+ Misses       1153    1026     -127
+ Partials      144     129      -15

Impacted Files
Coverage Δ

api/v1alpha1/iochaos_types.go
32.55% <ø> (+3.98%)
:arrow_up:

api/v1alpha1/common_webhook.go
100% <ø> (ø)
:arrow_up:

api/v1alpha1/networkchaos_types.go
13.08% <ø> (+0.69%)
:arrow_up:

api/v1alpha1/podchaos_types.go
32.55% <ø> (+10.68%)
:arrow_up:

api/v1alpha1/timechaos_types.go
4.34% <ø> (+0.5%)
:arrow_up:

api/v1alpha1/iochaos_webhook.go
77.41% <82.75%> (+34.56%)
:arrow_up:

api/v1alpha1/kernelchaos_webhook.go
77.41% <82.75%> (+34.56%)
:arrow_up:

api/v1alpha1/timechaos_webhook.go
77.41% <82.75%> (+34.56%)
:arrow_up:

api/v1alpha1/networkchaos_webhook.go
78.12% <83.33%> (+28.12%)
:arrow_up:

api/v1alpha1/podchaos_webhook.go
81.25% <84.78%> (+38.39%)
:arrow_up:

... and 6 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 0724ec9...0f3d56a. Read the comment docs.

@Gallardot Good job!

It seems that I cannot delete a chaos resource. Do you know what the problem is ?
Error from server: admission webhook "vtimechaos.kb.io" denied the request: there is no content to decode

It seems related with this PR on kubernetes, which means Validator will break compatibility with old version of kubernetes.
The former error occurs on kubernetes 1.14.8. As I have tested, 1.17.0 works well.

It seems related with this PR on kubernetes, which means Validator will break compatibility with old version of kubernetes. There is also a related issue for controller-runtime.
The former error occurs on kubernetes 1.14.8. As I have tested, 1.17.0 works well.

About this issue, Can we disable validator by default? When the controller-runtime fix this https://github.com/kubernetes-sigs/controller-runtime/issues/845, we enable validator.

It seems related with this PR on kubernetes, which means Validator will break compatibility with old version of kubernetes. There is also a related issue for controller-runtime.
The former error occurs on kubernetes 1.14.8. As I have tested, 1.17.0 works well.

Thank you. I will test it on kubernetes 1.14.8 later. Maybe we can ignore the DELETE operations. I will have a try.

@Gallardot Hi, Currently, we are preparing Chaos Mesh-for CNCF Sandbox entry. https://github.com/cncf/toc/pull/367. At present, we are preparing the slide which requires some contributor-related information.  Would you mind tell us what organization are you from?

@YangKeao @cwen0
I reproduce this error on kubernetes 1.14.8. Currently, we do nothing for DELETE operations. Maybe we can ignore the DELETE  operations on the ValidatingWebhookConfiguration. It is Ok on kubernetes 1.14.8. Please take a look.

/merge


Fixed a bug that 'gal's were not recognized correctly.

This bug was caused by https://github.com/hasegaw/IkaLog/commit/7a5077839ab3ca069b8bd619f1a18d57ee808da2
KNN model data still uses the 'ガロン52' format.
This is a temporary workaround.
The right way is to update tools/learn_weapons.py and data/weapons.knn.data.

Thanks!

Eventually KNN Training data will use stat.ink based weapon IDs, rather than JA weapon names.


linux starting adding sctp support

@bors r+

:pushpin: Commit 6238f17e0cc4ad5ceb2e9c3d144c8e1a79b4db3e has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 6238f17e0cc4ad5ceb2e9c3d144c8e1a79b4db3e with merge 167a923ed7f3e50d24f4fd2e86deb05d9ed986a1...

:broken_heart: Test failed - checks-actions

@bors r+

:pushpin: Commit 78cc6abf4b4da3700cf4899b4edd9bb8c133f4a4 has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 78cc6abf4b4da3700cf4899b4edd9bb8c133f4a4 with merge e078dd6d7f00efe00d2bb75a2a18c29bd4719c3a...

:broken_heart: Test failed - checks-actions

Great, thank you. @bors r+

:pushpin: Commit 74f65ebeacbacf64a18c66cd407b33f362aa90dc has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit 74f65ebeacbacf64a18c66cd407b33f362aa90dc with merge 683e367bee7beffb9d4741b282e5bd0c9ee7fd12...

:broken_heart: Test failed - checks-actions

@bors r+

:pushpin: Commit eba949dd2888386351c0b383871467729c3dc4f4 has been approved by JohnTitor
It is now in the queue for this repository.

:hourglass: Testing commit eba949dd2888386351c0b383871467729c3dc4f4 with merge 8778e77914dd8d86a173fbb127010cf90b89b75f...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13, checks-cirrus-freebsd-14
Approved by: JohnTitor
Pushing 8778e77914dd8d86a173fbb127010cf90b89b75f to master...


Update Text/Rich text to describe recognizers in semantics

If any child text spans of a RichText have gesture recognizers, partition the text with recognizers and collect the text without recognizers.
determines the correct rect of each partition using getBoxesForSelection.
Fixes: https://github.com/flutter/flutter/issues/20643
There is currently a  known issue where certain containers cause the rects to be incorrect - this is unrelated to this change.

cc @HansMuller  and @Hixie , this is important for customer mulligan.

I've been informed this is not a blocker, so feel free to prioritize accordingly.

Blocked by https://github.com/flutter/flutter/issues/20891

@Hixie should I wait for the bidi text issue to be resolved before continuing with this?

No, just assume that the API will be fixed to give the right results. You can add a test that you've marked skip: true with a TODO pointing to that other bug, and when it gets fixed (and when we next audit skips and TODOs and links to bugs) we'll unskip it.


chore: bdd-spring-1575437825 to 0.0.1

chore: Promote bdd-spring-1575437825 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Devtooling 287

added properties blob

Looks good. Just a couple merge conflicts, probably from John's big refactoring PR


Style issues in news pages from AEM

[ ] Issue with Iframe - (Revisit this component after implementing cookiebot)
[x] Images are not present in Imagetiles
[x] Padding issue in Ingress
[x] Buttons have links to other pages in AEM which are not there in ENVIS
[x] Carousel images are not loaded
[x] List - Font issue
[x] SVG icon - not loaded
[x] BannerInline - image issue
[x] Norwegian characters and special quotes not supported from Azure container.

Fixed the following for pages from 2016 till 30 June 2021.

Missing images for Image tiles and carousel
Norwegian characters shown as unsupported character.

@nicholas-haggerty Ready to be tested

@nilsml  And where do I test this?

@padms @meols Hi Padmaja. How would we test this? Something we would need to have a meeting/demo on?


Fix memory leak in g_variant_builder

Memory allocated using g_variant_builder_new needs to
be explicitly freed

Signed-off-by: Parthiban Nallathambi<EMAIL_ADDRESS>

@Arkq I meshed it up, sorry. I will update it again. Can I open fresh PR without merge commits? or updating this is fine?

Force push your branch so this PR will be updated automatically. And one more thing. I think, that it is required to call g_variant_builder_end() upon retrieval of GVariant, otherwise memory allocated by the g_variant_builder_add() will not be freed :)

@Arkq Tried forced pushing, github auto closed it. Not sure why. Opened a new one https://github.com/Arkq/bluez-alsa/pull/120


Validation split for MNIST in Fuel

We should consider including "validation" split to our MNIST dataset. It has certain official status, as far as I know.

I don't think it does...

Oh my goodness..

The official page doesn't define any validation split
deeplearning.net offers to use 10k examples for validation and seems, that all theano based libraries use this split
Tensor flow uses only 5k examples

But I am pretty sure that in many well-reputed paper the last 10000
examples are used (too lazy to go ahead and check it right now).
On 2 February 2016 at 19:09, dmitriy-serdyuk<EMAIL_ADDRESS>wrote:

Oh my goodness..

The official page http://yann.lecun.com/exdb/mnist/ doesn't define
any validation split
deeplearning.net offers to use 10k examples for validation
http://deeplearning.net/tutorial/gettingstarted.html and seems, that
all theano based libraries use this split
Tensor flow
https://www.tensorflow.org/versions/0.6.0/tutorials/mnist/download/index.html
uses only 5k examples

—
Reply to this email directly or view it on GitHub
https://github.com/mila-udem/fuel/issues/306#issuecomment-178900921.

It's a matter of trading between convenience and safety. I'm afraid that this might lead to accidentally contaminating the training set with validation set examples (e.g. using the full official training set (60,000 examples) and the unofficial validation set (last 10,000 examples of the training set)).
If you think it would be really convenient to have the unofficial train/valid split as opposed to having to specify a subset argument to the constructor, I'd suggest that we choose the split names to be unambiguous (unofficial_train and unofficial_valid, for instance) and use the MNIST constructor to alias these to a superclass constructor call with the proper subset kwarg.

It is empirically true that using the last 10k examples is good as a
validation set, much better than using a random 10k which will cause early
stopping to massively overfit in my experience. But it is somewhat
mysterious why this is

At the risk of revealing my ignorance, I will dare to ask: can't we have
overlapping splits in Fuel? Can we have "unofficial_train",
"unofficial_valid" as additional splits?
On 3 February 2016 at 11:55, David Warde-Farley<EMAIL_ADDRESS>wrote:

It is empirically true that using the last 10k examples is good as a
validation set, much better than using a random 10k which will cause early
stopping to massively overfit in my experience. But it is somewhat
mysterious why this is
—
Reply to this email directly or view it on GitHub
https://github.com/mila-udem/fuel/issues/306#issuecomment-179343427.

No, you're right. It would involve changing the converter as well as the dataset class, but it's doable. It all depends on where you want to bake in these additional splits. Actually, doing so at the converter level might be a more elegant solution.

I think this will definitely contribute to reproducibility of the research
at the lab.. :) Let's make it a CCW ticket?
On 4 February 2016 at 10:22, vdumoulin<EMAIL_ADDRESS>wrote:

No, you're right. It would involve changing the converter as well as the
dataset class, but it's doable. It all depends on where you want to bake in
these additional splits. Actually, doing so at the converter level might be
a more elegant solution.
—
Reply to this email directly or view it on GitHub
https://github.com/mila-udem/fuel/issues/306#issuecomment-179896993.


kactivity / jevt. rawtime Not Triggering

Describe the bug
I was looking at the k8s_audit_rules.yaml rules and trying to trigger one the rule K8s Namespace Created:
- rule: K8s Namespace Created
  desc: Detect any attempt to create a namespace
  condition: (kactivity and kcreate and namespace and response_successful)
  ...

However, from my testing, it never triggers. I tested it using the following payload (the exact same payload that the Kubernetes API Server sends):
{"kind":"EventList","apiVersion":"audit.k8s.io/v1","metadata":{},"items":[{"kind":"Event","apiVersion":"audit.k8s.io/v1","level":"Metadata","auditID":"047a3677-b68c-4f1c-8a10-6e59a5b5ccc7","stage":"ResponseComplete","requestURI":"/api/v1/namespaces?fieldManager=kubectl-create","verb":"create","user":{"username":"kubernetes-admin","groups":["system:masters","system:authenticated"]},"sourceIPs":["<IP_ADDRESS>"],"userAgent":"kubectl/v1.19.4 (linux/amd64) kubernetes/d360454","objectRef":{"resource":"namespaces","name":"def","apiVersion":"v1"},"responseStatus":{"metadata":{},"code":201},"requestReceivedTimestamp":"2021-01-27T07:36:30.641811Z","stageTimestamp":"2021-01-27T07:36:30.645337Z","annotations":{"authorization.k8s.io/decision":"allow","authorization.k8s.io/reason":""}}]}

by running:
curl  -H "Content-Type: application/json" -XPOST -d @/tmp/file.json http://localhost:8765/k8s-audit

and I got back a 200 response from the server:
Ok

I know that my rules are working because the "Create Disallowed Namespace" rule triggers
When I removed the kactivity requirement in the rule, it triggered. Looking at the definition of kactivity, I found that:
- macro: consider_activity_events
  condition: (k8s_audit_always_true)

- macro: kactivity
  condition: (kevt and consider_activity_events)

which finally leads me to this:
- macro: k8s_audit_always_true
  condition: (jevt.rawtime exists)

so it looks like jevt.rawtime doesn't exist. Any ideas?
How to reproduce it

See above
Expected behaviour

The rule should have triggered
Screenshots

Environment

Falco version:

$ falco --version
Falco version: 0.27.0
Driver version: 5c0b863ddade7a45568c0ac97d037422c9efb750

System info:

{
  "machine": "x86_64",
  "nodename": "dell",
  "release": "5.8.0-36-generic",
  "sysname": "Linux",
  "version": "#40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021"
}

Cloud provider or hardware configuration:
OS:

NAME="Ubuntu"
VERSION="20.04.1 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.1 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Kernel:

Linux dell 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Installation method:

Linux binary
Additional context

Sorry. It was a silly mistake. I forget to add:
- list: k8s_audit_stages
  items: ["ResponseComplete"]

- macro: kevt
  condition: (jevt.value[/stage] in (k8s_audit_stages))

to my rules file

Sorry. It was a silly mistake. I forget to add:
- list: k8s_audit_stages
  items: ["ResponseComplete"]

- macro: kevt
  condition: (jevt.value[/stage] in (k8s_audit_stages))

to my rules file


How to assign more roles within blade?

@role('superuser,admin') or @role('superuser','admin') doesn't work

and @ROLE('superuser|admin') doesn't work

yes


Provide pre-compiled binaries

Pre-compiled binaries, at least for Windows, would be very helpful to people considering Recast / Detours. The build steps are non-trivial and this seems like something that can be done once and then added to GitHub as a release artifact.

Was this ever done?  I could really use a pre-compiled windows binary...

No, this has not been set up.

@hymerman I have looked at setting this up, but it doesn't seem like I have the appropriate rights on AppVeyor. Not sure why, since I am signed in to GitHub and it should see that I am an owner (I think?).
IIRC you did the original AppVeyor build -- can you check if you can give me the appropriate access?

Sure thing, I'm away right now but will do this once I'm at a computer
tomorrow!
On Sat, 14 Jul 2018, 12:14 Jakob Botsch Nielsen<EMAIL_ADDRESS>wrote:

@hymerman https://github.com/hymerman I have looked at setting this up,
but it doesn't seem like I have the appropriate rights on AppVeyor. Not
sure why, since I am signed in to GitHub and it should see that I am an
owner (I think?).
IIRC you did the original AppVeyor build -- can you check if you can give
me the appropriate access?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/recastnavigation/recastnavigation/issues/284#issuecomment-405016431,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJdBgA7YkbwfuICfLczMyuWTT90L6Uwks5uGdKwgaJpZM4PMdkB
.

Sorry for the wait!
I think this is done now. AppVeyor was already set up to allow people with
'Admin' rights to the repo, to do admin things there - but I think that
even though we're all admins of the recastnavigation organisation, we were
in a team called 'Write' which just has 'Write' permissions to the
recastnavigation repo - not 'Admin'. I've added another team called 'Admin'
which has 'Admin' rights to the repo. I hope that's clear! If that doesn't
work, then I'm out of ideas :)
On 14 July 2018 at 12:17, Ben Hymers<EMAIL_ADDRESS>wrote:

Sure thing, I'm away right now but will do this once I'm at a computer
tomorrow!
On Sat, 14 Jul 2018, 12:14 Jakob Botsch Nielsen<EMAIL_ADDRESS>wrote:

@hymerman https://github.com/hymerman I have looked at setting this
up, but it doesn't seem like I have the appropriate rights on AppVeyor. Not
sure why, since I am signed in to GitHub and it should see that I am an
owner (I think?).
IIRC you did the original AppVeyor build -- can you check if you can give
me the appropriate access?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/recastnavigation/recastnavigation/issues/284#issuecomment-405016431,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJdBgA7YkbwfuICfLczMyuWTT90L6Uwks5uGdKwgaJpZM4PMdkB
.

Sorry for the wait!

No worries. It still doesn't seem like I have access, though. I can even add a new project for this project. Not sure what's going on. Do you just see it under the "PROJECTS" tab, to the left of "ENVIRONMENTS"?

Aha! I found a new bit of the AppVeyor settings interface. I think I added
the recastnavigation GitHub team to my AppVeyor account as admins for the
recastnavigation AppVeyor project. I'm not sure why that's under my account
settings rather than under the project settings... let me know if you can
suddenly see information that looks my personal account ;) Hope that fixes
it!
On 16 July 2018 at 16:31, Jakob Botsch Nielsen<EMAIL_ADDRESS>wrote:

Sorry for the wait!
No worries. It still doesn't seem like I have access, though. I can even
add a new project for this project. Not sure what's going on. Do you just
see it under the "PROJECTS" tab, to the left of "ENVIRONMENTS"?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/recastnavigation/recastnavigation/issues/284#issuecomment-405287159,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJdBtRgDh-UAnMFjTH5z9ztwIqf17MWks5uHLG0gaJpZM4PMdkB
.

Nope, still no go :-(

I invited you directly by email now... if this doesn't work then I don't
know what will :)
On 16 July 2018 at 21:44, Jakob Botsch Nielsen<EMAIL_ADDRESS>wrote:

Nope, still no go :-(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/recastnavigation/recastnavigation/issues/284#issuecomment-405376076,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJdBqWZsdzVX1fDasWmd_nMZeExDQXYks5uHPtFgaJpZM4PMdkB
.

Even after logging in to my GitHub using that sign-up link I don't see it (I don't want to register a new account). It is probably just me missing something glaringly obvious, but I will send them a support request and see. Thanks for trying!


Reduce dependencies

This PR reduces the amount of dependencies of this package. TrajectoryGamesBase was only used for one function, while Zygote and FiniteDiff was only used for tests.

I think these are good changes. Zygote and FiniteDiff can be removed entirely. The test directory has its own Project.toml

@longemen3000 looks like tests are failing on this. Once tests pass and @lassepe’s comment is addressed let’s get this merged!

@longemen3000 i think there’s a dependency still missing in the tests

There is something wrong in the tests, that maybe is related to removing TrajectoryGamesBase.jl. I need to investigate in the meanwhile. I'm gonna close this and create another PR removing only Zygote and FiniteDiff


How Do You Evenly Space a Known Number of Tabs?

Say I have a set number of tabs and I know the labels won't overflow the width of the screen.
I'm struggling with how to evenly space the labels across the header like the below example:

Basically I want to use 'space-around' as if they were flex items but I can't seem to get it to work properly.
Any help would be greatly appreciated, thanks!

@maxmagee
Hi Max! You can achieve such behavior passing through some styles to component. Take a look:
        <ScrollableTabView
          tabBarUnderlineColor="#53ac49"
          tabBarActiveTextColor="#53ac49"
          renderTabBar={() => (
            <TabBar
              scrollContainerStyle={{
                width: '100%',
                justifyContent: 'space-between',
              }}
            />
        )}
        >
          <Page tabLabel={{label: "Page #1"}} label="Page #1"/>
          <Page tabLabel={{label: "Page #2", badge: 3}} label="Page #2 aka Long!"/>
          <Page tabLabel={{label: "Page #3"}} label="Page #3"/>
        </ScrollableTabView>

The result:

Also while I was checking this, I have found out the that when I apply 'space-around', calculations for underline become incorrect. So be careful with this.
This is some kind of undesigned behavior because the initial purpose of library is tabs that don't fit into a container. I hope everything will work fine for you, but if not feel free to report an issue.
P.S. Probably you can achieve the same result with inbuilt TabBars of ReactNativeScollableTabView.


Null Safety

This is my approach to implementing Null Safety for flutter_coast that I described in my issue on your repo.
If this saves you any time, please make use of it. If I am off the mark, please ignore.
Thank you Sander,
-TRE

Thanks, looks good. Could to revert the formatting changes, so the max line length is 120 again?

My bad mate. Should be sorted now. I set the line length to 120 and removed several non-null asserts that will always be true in null-safety.


Support HTTP2

What would you like to be added?
Support for HTTP2.
Why is this needed?
HTTP2 is increasingly common, especially as the underlying transport for gRPC.
N.B.: HTTP2 does not strictly require the use of TLS, however, many HTTP2 clients do. Mileage from this feature may vary unless/until #15 is also addressed.

Similar to this comment on #15, this may impact how we approach collecting and aggregating the metrics on which we base scaling decisions.
HTTP2 is capable of multiplexing requests and handling long-lived, full-duplex streams, etc., so a single HTTP2 "request" might logically be thought of in terms more similar to a "connection." This might invalidate our approach of counting requests and drive us toward counting active connections (or "connections") instead.

Looking into this right now.

After doing more  reading, I would say that the correct approach is to tackle #15 first given the assumption that http2 is implemented with secure communication(TLS). So I guess we would need to implement the TLS and we could do the HTTP2 on top of  that implementation.

@tariq1890, some of the recently opened issues reflect discreet feature requests, but we know implementation details are going to overlap quite a bit. I'm going to open a new issue soon that proposes a comprehensive approach that will address a few of these.

This was closed by #27.


Add Plugin loader

Closes #114
I will refactor the this PR when https://github.com/open-telemetry/opentelemetry-js/pull/110 is merged.

Codecov Report

Merging #126 into master will decrease coverage by 1.76%.
The diff coverage is 89.81%.

@@            Coverage Diff             @@
##           master     #126      +/-   ##
==========================================
- Coverage   98.87%   97.11%   -1.77%
==========================================
  Files          27       32       +5
  Lines        1784     2216     +432
  Branches      201      255      +54
==========================================
+ Hits         1764     2152     +388
- Misses         20       64      +44

Impacted Files
Coverage Δ

...ntelemetry-tracer/src/instrumentation/constants.ts
100% <100%> (ø)

...elemetry-tracer/test/instrumentation/utils.test.ts
100% <100%> (ø)

...y-tracer/test/instrumentation/PluginLoader.test.ts
77.04% <77.04%> (ø)

.../opentelemetry-tracer/src/instrumentation/utils.ts
91.3% <91.3%> (ø)

...lemetry-tracer/src/instrumentation/PluginLoader.ts
93.05% <93.05%> (ø)

Looks like I have addressed all the comments. PTAL

@rochdev @vmarchaud @OlivierAlbertini @draffensperger Looks like I have addressed all the comments. Please approve, if everything looks good.

@mayurkale22 LGTM (note we can't approve directly since we are not reviewer)


Disregard

I use an IKEAS E1743 for commanding trunk open/close.
"0" to "off is close trunk (short click) & "brightness_down" is open trunk (Long press)
If i "short click" again while the trunk is travelling it will loose status of trunk & work opposite so "off" now is close & "brightness_down" is open trunk.
Unfortunately i dont know if this was an issue before 3.0 too.

I'm not sure I understand. Are you saying you've modified your trunk? We are using the commands available from the official API. We unfortunately cannot handle modifications to vehicles differently. What is the behavior in the official app?

Sorry for wasting your time, i have redone way to many automations today and must have had something happend on first travel & then swapped functionality of the IKEA unit. Thank you very much for an outstanding integration. This one is truly super as HA now can adjust charging level to the car which is truly super when having solarpanels. Again, sorry. I have closed the issue now.


Option to auto-watch on first interaction

Gitea version (or commit ref): Gitea version 1.8.3+2-g11f6ed4 built with go1.12.6 : pam, bindata, sqlite, sqlite_unlock_notify
Git version: <IP_ADDRESS>
Operating system: CentOS 7
Database (use [x]):

[*] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[X] Not relevant

Log gist:

In the spirit of AUTO_WATCH_NEW_REPOS, it would be nice to have options to automatically add the user as a watcher on first interactions, like:

AUTO_WATCH_ON_CHANGES = true: any write operation on a server's repository (like push) will subscribe the user to the repository.
AUTO_WATCH_ON_CLONE = true: clone (u other relevant operations) will subscribe the user to the repository.
AUTO_ORG_MEMBER_VISIBLE = true: member is visibile by default.

i think this is related: https://github.com/go-gitea/gitea/issues/8243

They should be the same.

It should be "auto-subscribe", as "watch" is for all activities of a repository ?

It should be "auto-subscribe", as "watch" is for all activities of a repository ?

@strk My original idea was to watch the entire repo after the users commits/pushes anything to it. It's implemented in #7657, but that PR is not up-to-date.
This is not the same as #7512. This is for subscribing to repos when commiting to them, while #8243 is for subscribing to issues that one creates. Sorry about my lousy description here.

This has been implemented to a satisfactory level. Suscription upon cloning could be implemented as well, but that would be very difficult to do as git has no hook to catch a clone operation (it had one but it was removed long ago).
Closing this.

@guillep2k think this is fine for now :D


ZIP Code search freezes Find Resource screen

After entering an invalid zip code, Find Resource screen just hangs. Need to fail gracefully.

[ ] Update ZIP Code geolocation coordinates database with latest latitude and longitude values.
[ ] Refactor error handling in ZIP Code search UI to gracefully handle a ZIP Code that isn't in the database.

http://download.geonames.org/export/zip/


[MFS] Changes to the tree/blob paths in summaries leading to summarization error

PR : https://office.visualstudio.com/OC/_git/MfsSDK/pullrequest/1141285?_a=files
This is in regards to the custom OdspSearchableDataObject, CreateOdspSearchDataStorerFactory and getSearchContent method implementation leading to summarization errors. When I created multiple, dynamic search paths, I get a summarization error when the path changes on the next load. For e.g., the following is the latest snapshot with multiple paths each representing a different MFS item. In this case, there are 4 MFS items. Please ignore the replacement of _search with _testing a I'm not testing the actual MS wide search with this code. I'm not testing the snapshot appearance.
{
                    "path": ".app/.channels/default/.channels/_testing",
                    "type": "tree"
                },
                {
                    "id": "bARAO9dM5OFlZiASFdRVDjBj_",
                    "path": ".app/.channels/default/.channels/_testing/testing1",
                    "type": "blob"
                },
                {
                    "path": ".app/.channels/default/.channels/testing1",
                    "type": "tree"
                },
                {
                    "id": "bARAxYryJ3lCHHLXZGcI6ll+N",
                    "path": ".app/.channels/default/.channels/testing1/testing2",
                    "type": "blob"
                },
                {
                    "path": ".app/.channels/default/.channels/testing2",
                    "type": "tree"
                },
                {
                    "id": "bARC0lZJoN_F8agjB0jGAHWUw",
                    "path": ".app/.channels/default/.channels/testing2/testing3",
                    "type": "blob"
                },
                {
                    "path": ".app/.channels/default/.channels/testing3",
                    "type": "tree"
                },
                {
                    "id": "bARCqh9PhNENe_+auc8bnR20C",
                    "path": ".app/.channels/default/.channels/testing3/testing4",
                    "type": "blob"
                },

However, if I create a 5th MFS item ( on the same fluid data store), I get a summarization error as follows:
common.js:113

       fluid:telemetry:Summarizer:Running FailToSummarize {"summarizeReason":"maxTime","message":"UnexpectedSummarizeError","category":"error","error":"0x25d","clientType":"noninteractive/summarizer","loaderVersion":"0.52.1","containerId":"8db55d5e-3af5-42aa-bb24-d665db845138","docId":"6pjiyOl1AE56lePeS%2BAjLlHnFaXNoedG57%2F7gqa9qIw%3D","containerAttachState":"Attached","containerLifecycleState":"loaded","containerConnectionState":"Connected","runtimeVersion":"0.52.1","summaryGenTag":1,"dmInitialSeqNumber":53,"dmLastKnownSeqNumber":154,"containerLoadedFromVersionId":"bBzUAAAAHAAAA","dmLastMsqSeqNumber":154,"dmLastMsqSeqTimestamp":1641415227647,"dmLastMsqSeqClientId":null,"connectionState":"Connected","connectionStateDuration":723584.5999999046,"loaderId":"9c9bbbef-e9d5-4f7a-990f-5b8aaaccee22"} tick=784558 Error    at assert (http://localhost:8080/app.bundle.js:43724:15)    at RunWhileConnectedCoordinator.get cancelled [as cancelled] (http://localhost:8080/app.bundle.js:54641:88)    at fail (http://localhost:8080/app.bundle.js:56173:48)    at SummaryGenerator.summarizeCore (http://localhost:8080/app.bundle.js:56215:20) +0ms

If I create another instance of fluid data store ( another container/pod), the error doesn't show up. So, I suspect that the summarizer is not able to dynamically pick up changes in the paths ?
###Expected behavior
This modified code should create another path as follows and add it to the existing paths in summary ( as this is a new 5th MFS item created ) but instead it throws an exception as outlined above.
{
                  "path": ".app/.channels/default/.channels/testing4",
                  "type": "tree"
              },
              {
                  "id": "bARCqh9PhNENe_+auc8bnR20C",
                  "path": ".app/.channels/default/.channels/testing4/testing5",
                  "type": "blob"
              },

Is this an expected behavior and if not, what are the next steps? My goal is to create multiple, dynamic paths each representing a MFS item created on the fly and whenever a new MFS item is created, it should be represented in the snapshot by a new path. That's the goal of my custom code above but it doesn't happen.
Steps to reproduce

Run this https://office.visualstudio.com/OC/_git/MfsSDK?version=GBsgarapati/podSearch&path=/examples/mfs-client-prod example in MFS repo
Select pick a pod file and navigate to Communication site -> .appdata -> searchTestPod5.pod.
Go to network tab in the developer tools and filter using latest snapshot and copy, paste the snapshot object into a text editor to see the summaries.

CC: @vladsud @anthony-murphy

Searching for 0x25d assert shows that it is being hit in prod:
https://github.com/microsoft/FluidFramework/issues/8626
For some reason search does not find it, but there is bug on that specific isuse - https://github.com/microsoft/FluidFramework/issues/8398
And PR that addresses it - https://github.com/microsoft/FluidFramework/pull/8468
This assert has nothing to do with your changes, you are as likely to hit it without your changes.
And the best course of action is to pick up latest release that should fix it for you

BTW, this assert (I believe) fires only on long idle connections (I think 5 min). So, you should be able to test your code changes even without the fix, if you avoid allowing connections to be idle that long (strictly to unblock you if you can't easily jump to latest bits yet)

Hi Vlad,
Although there is the assert issue, I believe that this is a summarization error because of the multiple search blobs that I have. I think the following is happening:

A new item is added, so a new search path is being created and the summarizer fails because of the inconsistency with the existing snapshot as it expects the snapshot to have the same paths on the load of the data store.

My question is if that is an expected behavior or a bug on my side or the fluid side ( apart from the assert bug) I see that the assert bug was solved on Dec 7th and our team has upgraded fluid after that as part of our weekly fluid updates.
From: Vlad Sudzilouski @.>
Sent: Thursday, January 6, 2022 11:41 AM
To: microsoft/FluidFramework @.>
Cc: Sarojini Garapati @.>; Author @.>
Subject: Re: [microsoft/FluidFramework] [MFS] Changes to the tree/blob paths in summaries leading to summarization error (Issue #8661)
BTW, this assert (I believe) fires only on long idle connections (I think 5 min). So, you should be able to test your code changes even without the fix, if you avoid allowing connections to be idle that long (strictly to unblock you if you can't easily jump to latest bits yet)

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FFluidFramework%2Fissues%2F8661%23issuecomment-1006881607&data=04|01|sgarapati%40microsoft.com|a58ecb6a7ec14966c8e508d9d14c8302|72f988bf86f141af91ab2d7cd011db47|1|0|637770948841206170|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=oS92OPuLuKhcZ7GLjbMm23dozAg9dqsVA%2B4wVWgdSVQ%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAR7VNUHEPYMAEICDVXMJGWLUUXV55ANCNFSM5LK3FSQA&data=04|01|sgarapati%40microsoft.com|a58ecb6a7ec14966c8e508d9d14c8302|72f988bf86f141af91ab2d7cd011db47|1|0|637770948841206170|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=RBG9nJWsNFHTZ0BUXKBmGQJhPz3DO0Zzl12AYfMbhXs%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|sgarapati%40microsoft.com|a58ecb6a7ec14966c8e508d9d14c8302|72f988bf86f141af91ab2d7cd011db47|1|0|637770948841206170|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=JdMZabndUYnHzQjO0Sb4xulICZHy5j4%2FBhP4BNEUcyo%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|sgarapati%40microsoft.com|a58ecb6a7ec14966c8e508d9d14c8302|72f988bf86f141af91ab2d7cd011db47|1|0|637770948841206170|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=r45eaUZxLiFm%2B3ceM%2FnrePnMRJIqbb50IlYEZpriADY%3D&reserved=0.

Asserts you brought up were not specific to search area but were all fixed.
I do not see how or what last stack shows, but I've opened https://dev.azure.com/fluidframework/internal/_queries/edit/850/?triage=true to take a look at somewhat related problem.
Please let me know if you are blocked, but I currently do not see anything on FF side.


add Loot Rock in Derivative Projects list

Thanks for the PR! Can you please confirm and update if the name is Loot Rock or LootRock (like on the OpenSea page).

Thanks for the PR! Can you please confirm and update if the name is Loot Rock or LootRock (like on the OpenSea page).

@Anish-Agnihotri Thanks for your response, The name is LootRock, now the name is in line at all three places i.e., Etherscan, Opensea and this PR.


Docs #231 : GEDI L4A example documentation

Included:

Create custom GeoJSON file for AOI
Subset the file and smoothen the contours
Plot the contour in folium map for better visualization

@anisbhsl @sumantjha @chuckwondo
With the release of 0.3.0 for the gedi-subsetter, do we want to update the GEDI notebook to reflect the newest changes? The changes are applicable across {"L1B": "10.5067/GEDI/GEDI01_B.002", "L2A": "10.5067/GEDI/GEDI02_A.002", "L2B": "10.5067/GEDI/GEDI02_B.002", "L4A": "10.3334/ORNLDAAC/2056"} collections

@jjfrench I think we should update the example to conform to the changes in 0.3.0. For L4A, it doesn't matter so much, but to avoid confusion (and be consistent) with examples for other GEDI collections, which will require 0.3.0 or later (since prior versions support only L4A), I think this would be good to do.

@chuckwondo Yes NBreview did thread me the comments, will look at them.

@anisbhsl please go through the above conversation threads and mark the ones you've resolved so we know your latest changes should address those concerns.

@chuckwondo  I have included gedi_gdf.head() for printing head of geo dataframe. It's below the plot line. Regarding the images, I have included them so that readers would know what would the final output could look like. This will be converted to a html page (for the docs), so I guess having such output images would help in understanding what the example does.

@anisbhsl, yes, I understand you included the print below the plot line, but please reread my comment.


✨Add Timeline to Patient resource

Adds a "timeline" tab in place of "references" for any resources with a base type of Patient.

@znatty22 I changed it to timeline because it shows the same information, just in a different way. I can add it back in if this view is preferred though

@znatty22 I changed it to timeline because it shows the same information, just in a different way. I can add it back in if this view is preferred though

I think it would be useful to add it back because there could be resource references that don't have dates and wouldn't make sense to display on the timeline


F# + dotnet-sourcelink-git not embedding source

F# projects currently use embed property instead of EmbeddedFiles itemgroup. I reported this in https://github.com/Microsoft/visualfsharp/issues/2767 and it has popped up again in https://github.com/Microsoft/visualfsharp/issues/4075.

The test failed since the full paths are not used. The F# support isn't great currently. This does not work:
--embed:ilpars.fs;illex.fs;pppars.fs;pars.fs;pplex.fs;lex.fs

It is working!
PS C:\Users\camer\cs\SourceLink\build> dotnet sourcelink test "C:\Users\camer\Downloads\FSharp.Compiler.Service.17.0.1(4)\lib\netstandard1.6\FSharp.Compiler.Service.pdb"
sourcelink test passed: C:\Users\camer\Downloads\FSharp.Compiler.Service.17.0.1(4)\lib\netstandard1.6\FSharp.Compiler.Service.pdb


There is a mistake in the path under "Sending Data with Giles Sender"

Above you are creating the testing data bundle in ~/wallaroo-tutorial/wallaroo/examples/python/celsius/_test.
 It’s maybe only a typo or something but I believe it should be:
cd ~/wallaroo-tutorial/wallaroo/giles/sender
./sender --host <IP_ADDRESS>:7000 --messages 25000000 --binary --batch-size300 \
  --repeat--no-write--msg-size8--ponythreads=1 --file \
  ~/wallaroo-tutorial/wallaroo/examples/python/celsius/_test/celsius.ms

This has been resolved by #1500.


w3.eth.defaultAccount is undefined

When I call w3.eth.defaultAccount with MetaMask connected I am still getting undefined.
When I make a call to a function on my contract, I get an invalid address. I am assuming the defaultAccount does not get set by MetaMask at the time the function call is executed.
Now there could potentially be a lot of different reasons for this happening that I am not privy to. I would assume it would not be necessary to set the defaultAccount on the contract manually if I am using MetaMask. Could it be that Soltsice is the problem?
Please help

We can't do anything with the web3 returning an undefined value. However, if you provide a default account to W3 ctor, we will set that value to w3.web3.eth.defaultAccount. However, we will now remove w3.eth getter, you will have to use w3.web3.eth to get untyped web3 members.
w3 instance also has isPre1API and web3API properties so that you could detect which version of web3 Soltsice uses. Currently we use 0.20.x, but we try to hide the explicit web3 API and provide the most important web3 methods that are version-independent.


Out of memory errors?

I'm trying to query over a sequences of multiple Sqlite3 databases, and after a few dozen, I start getting the error:
RuntimeError: abort(RangeError: WebAssembly.instantiate(): Out of memory: wasm memory). Build with -s ASSERTIONS=1 for more info.

I'm using a version of your load() that accepts an argument for the sqlite3 path.
Is there anything I can do to fix this error? I'm not purposefully persisting any objects, as far as I know, and I only need to access one database at a time. Is there something I need to do to explicitly free up memory used by a previous createDbWorker() instance? Is there like a destroyDbWorker()?

There might be a memory leak somewhere in the sql.js-httpvfs code (e.g. not freeing statements). I only "optimized" the code for a single DbWorker created once. I probably can't really help you there, you might have to play around to figure out what causes the memory issue. Loading fairly large databases worked ok for me as well.

I ran into this issue and created 4 workers and randomly switch between them, pretty much solved it for now

@reyemtm That's essentially what I'm doing. I'm calling multiple awaits, to launch multiple createDbWorker. It's enough to load the data, but if the user enters a new query, I need to first refresh the page to release memory. Otherwise, the browser runs into out-of-memory errors and crashes.

Was this issue mitigated by recent commits like https://github.com/phiresky/sql.js-httpvfs/commit/1d6819ca9c3459f0d90fbbdbd223ca4df76ff4bd ?


Add platform info to error message for different platform in gemspec than Gemfile.lock

Addresses #4259

:umbrella: The latest upstream changes (presumably #4258) made this pull request unmergeable. Please resolve the merge conflicts.

Finally got the integration spec setup working as expected.

I meant the platform for each version.

Ah gotcha. Updated the PR with platform printing associated with each spec/version. This will print things like Source contains 'foo' at: 1.0 ruby. I honestly think this is a reasonable thing to maintain in terms of developer UX though. It provides more clarity and lessens confusion/uncertainty as to the platform associated with any found specs.

@segiddins I've updated this PR. You had originally requested adding a spec for multiple versions. However, after looking into this further, I don't believe this is possible via the :git option for a gem in the Gemfile.
This is the following spec that I had originally tried to add for multiple versions (along with appropriate build_gem calls in spec/support/builders.rb:
    it "complains with multiple versions and platforms if pinned specs don't exist in the git repo" do
      simulate_platform "java"

      build_git "only_java", "1.0" do |s|
        s.platform = "java"
      end

      build_git "only_java", "1.1" do |s|
        s.platform = "java"
      end

      install_gemfile <<-G
        platforms :jruby do
          gem "only_java", "1.2", :git => "#{lib_path("only_java-1.1-java")}"
        end
      G

      expect(out).to include("Source contains 'only_java' at: 1.0 java, 1.1 java")
    end

However, it only ever has the following output:
       Fetching /path/to/bundler/tmp/libs/only_java-1.1-java
       Fetching source index from file:/path/to/bundler/tmp/gems/remote1/
       Could not find gem 'only_java (= 1.2) java' in /path/to/bundler/tmp/libs/only_java-1.1-java (at master@6e46c59).
       Source contains 'only_java' at: 1.1 java

We can't specify multiple :git source options for only_java in the Gemfile and I don't think there's a way to put multiple gem versions in the representation for a single unpacked gem in a way that Bundler will appropriately understand.

@RochesterinNYC multiple gemspecs in the same repo

Hm okay, I tried that previously but maybe I was going about it wrong. I'll give it another go.

Updated the PR. Got the multi-version spec working correctly. Thanks for the help @segiddins

:+1:

@homu r+

:pushpin: Commit 15cbad4 has been approved by segiddins

:hourglass: Testing commit 15cbad4 with merge c1f6b0c...

:sunny: Test successful - status


Rails group Kanban

We are a team of two
Kanban link: https://github.com/users/mnaibei/projects/5

Hi @mnaibei @TayyabKM 👋,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that doesn't have the correct link to your Kanban board project , kindly provide it
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.

Hi Team👋,

Highlights💡

A link to the Kanban board is specified.✔
The team member size is stated.✔
All required columns are present.✔
Most card descriptions are provided.✔

Good job so far coming so far with the progress you've made! 💪💪
However, there are some issues that you still need to work on to go to the next project but you are almost there!

Required Changes ♻

Kindly assign all cards to members of the team. For group tasks, assign them to all group members.

Kidly add card descriptions to the last 2 cards.

Check the comments under the review.
Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Please, remember to tag me in your question so I can receive the notification.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me @brytebee in your question so I can receive the notification.
Use @brytebee on slack for faster responses.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Hi @mnaibei and @TayyabKM  👍,
Good job so far!
There are some issues that you still need to work on to go to the next project but you are almost there!

Highlights
Set up kanban board ✔
Added description to all the tasks ✔
Required Changes ♻

[ ] Kindly ensure that the tas below is assigned to any of the group member for proper documntation. ℹ

Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Hi team,
Great job so far you can start working on your project!
May I highlight the following:

[x] Your Kanbam board is setup correctly👏  ✔
[x] You implemented all the requirements✔

STATUS: APPROVED :muscle::clap:
Congratulations! :tada:
Your project is complete!  It's time to merge it :shipit:

Optional suggestions

Please check the comment under the review.

Every comment with the [OPTIONAL] prefix won't stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better. Some of them were simply missed by the previous reviewer and addressing them will really improve your application.
Cheers and Happy coding! :clap: :clap: :clap:
Feel free to leave any questions or comments in the PR thread and tag me @algerina if something is not 100% clear.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

If anything seems to be unclear to you, reach out and ask anything by commenting on this Pull Request and mention me as Algerina, I will receive a notification and will respond.
GitHub | LinkedIn | Twitter
Reviewed by Amel Khiri


Raw SQL Regex Issue with Ecto.Migration#execute/1

Elixir version
1.16.0
Database and Version
PostgreSQL 16.1
Ecto Versions
3.11.1
Database Adapter and Versions (postgrex, myxql, etc)
postgrex 0.17.4
Current behavior
Step 1: Migration
For a couple of reasons I use some raw SQL in my migration files. I created a contacts table with the following statement (only relevant parts):
def up do
  execute """
    create table contacts (
      -- Keys
      ...

      -- Data
      ...
      phone_number text,

      -- Timestamps
      ...

      -- Check constraint to ensure phone number matches format `+<country_code> <area_code> <number>` following DIN 5008
      constraint din_5008_phone_number check (phone_number ~ '^\+[1-9]\d{0,2} [1-9]\d* \d+(-\d+)?$')
  );
  """
end

Step 2: Seeding the Database
When trying to seed the database with mix run priv/repo/seeds.exs I got this error:
** (Postgrex.Error) ERROR 2201B (invalid_regular_expression) invalid regular expression: quantifier operand invalid

for a fake phone number like this: +76 581 91201-32. It should a) pass the check and b) the regex check constraint was taken from a previous project so I was pretty sure it is correct.
Step 3: Debugging
I dropped the constraint and created a new one in the DB with exactly the same regex:
alter table contacts
drop constraint din_5008_phone_number;

alter table contacts
add constraint din_5008_phone_number check (phone_number ~ '^\+[1-9]\d{0,2} [1-9]\d* \d+(-\d+)?$');

Now the seeding works fine and the random phone numbers pass the check.
I compared the two constraint definitions (Ecto migration vs. adding in DB) with:
select
    conname as constraint_name,
    contype as constraint_type,
    conrelid::regclass as table_name,
    pg_get_constraintdef(c.oid) as constraint_definition
from
    pg_constraint c
join
    pg_class t on c.conrelid = t.oid
join
    pg_namespace n on t.relnamespace = n.oid
where
    contype = 'c';

If you create the constraint in the DB, the resulting constraint_definition looks like this:
CHECK ((phone_number ~ '^\+[1-9]\d{0,2} [1-9]\d* \d+(-\d+)?$'::text))
With Ecto.Migration#execute/1 it looks like this:
CHECK ((phone_number ~ '^+[1-9] {0,2} [1-9]* +(-+)?$'::text))
Step 4: Solution
After a lot of try and error the simple solution is to double escape the regex within the execute/1 like this:
constraint din_5008_phone_number check (phone_number ~ '^\\+[1-9]\\d{0,2} [1-9]\\d* \\d+(-\\d+)?$')

Expected behavior
Maybe this a feature and not a bug 🤗, but it took me quite some time to get it right and I would expect the raw SQL execution in a migration file to create the same result as dropping it directly into the database.
If it's some known and expected behavior, maybe you could just extend the documentation and give a hint how to deal with Postgres regex escapes. Many thanks!

Yes, you need to either double escape the regex, because + will escape the Elixir character, or use execute ~S""". ~S is a sigil in Elixir that disables all character escaping and interpolation, therefore you don't need to double escape. :)


fix: Set ClamAV package names for Ubuntu dists

Description
This commit modifies the "Determine ClamAV package names" task to include Ubuntu distributions, preventing an undefined variable error when run on such hosts.
Error Message
TASK [cisagov.clamav : Install ClamAV packages] ********************************
fatal: [ubuntu]: FAILED! => {"msg": "The task includes an option with an undefined variable. The error was: 'package_names' is undefined\n\nThe error appears to be in '/home/user/.ansible/roles/cisagov.clamav/tasks/main.yml': line 15, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Install ClamAV packages\n  ^ here\n"}

Playbook Workaround
Without this fix, the following workaround in playbook.yml is necessary:
---
- hosts: ubuntu
  gather_facts: yes

  roles:
    - role: cisagov.clamav
      vars:
        package_names: [ clamav-daemon ]  # here

The Travis CI check won't work because Travis isn't enabled on this forked repo.  Once we have two approvals I'll temporarily turn off that requirement for the repo in order to merge in these changes.

The other check is failing because the job is taking too long to run. I will fix this when I have some free time later today.

I think I can get the build to pass by splitting it into multiple jobs - one for each platform.  I will be experimenting with that now.


ReadmeTest class doesn't pass the tests

Hi!
Noticed #314 pull request fail and tested it locally.
ReadmeTest::testBasicUsage() and ReadmeTest::testBasicUsage2() methods' assertions pass fine when ReadmeTest.php runs alone, but fail when all tests run together.
It seems so that previous tests set Rollup static attributes that interfere with later usage.

@gelige I removed the assertions, for now, to let the builds pass. I will resolve the failing assertions in the next tag.

Fixed in https://github.com/rollbar/rollbar-php/pull/326


Email is not showing on the profile page.

Describe the bug
Email is not showing on the profile page.
To Reproduce

Log in to the application using valid credentials.
Navigate to the Profile Page.
Look for the Email Address field.

Expected behavior
The email address associated with the user's account should be displayed on the profile page.
Smartphone (please complete the following information):

Device: iPhone15pro
OS: iOS17.6.1

Hi, Can you assign this issue to me? I  am new to open source and would like to work on this.


Bio width

Description
This PR includes the following proposed change(s):

Creates a variable bioWidth which is used to set the maximum width of the bio element

Requires
Add 'Requires Attention' label if appropriate.

[ ] Requires an update to the .env file
[ ] Requires adding a file listed in the .gitignore
[ ] Requires an opinion or answer to a question, see comments.
[ ] Requires other attention, see below.

If there are any requirements for the developer to make after this PR is merged please list them here.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation
[ ] Version change

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
Set the max width to 70 characters and checked for the change visually.
For pull requests that are not just a simple fix, please check that the branch works on your local machine.

[ ] Tested by Zach.
[x] Tested by Brandon.
[ ] Tested by Brady.

Does the change impact or break the Docker build?

[ ] Yes
[x] No

If Yes: Has Docker been updated accordingly?

[ ] Yes
[ ] No

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] New and existing unit tests pass locally with my changes
[ ] If attention is required by the developer such as updating the .env file, these requirements have been listed.

I set the width based on body text design standards. Research shows that the vast majority of people have difficulty tracking text when it is longer than 75 characters. It is also more daunting to look at when it is super wide. This is why newspapers put text in columns and not rows.
All that said, I do see your point and I am not opposed to changing this and testing it out.

I set the width based on body text design standards. Research shows that the vast majority of people have difficulty tracking text when it is longer than 75 characters. It is also more daunting to look at when it is super wide. This is why newspapers put text in columns and not rows.
All that said, I do see your point and I am not opposed to changing this and testing it out.

I have heard about this before. I'm just not sure about how it lines up on the page. Maybe a larger font size?


Cannot access gated repo for url

How do we access "gated" huggingface repos with pgml?  I am using https://postgresml.org/docs/open-source/pgml/developers/quick-start-with-docker setup.  I also tried adding an environment variable like so:
docker run \
    -it \
    -v postgresml_data:/var/lib/postgresql \
    -p 5433:5432 \
    -p 8000:8000 \
    -e HF_TOKEN='!!!MY_HF_TOKEN!!!' \
    ghcr.io/postgresml/postgresml:2.9.3 \
    sudo -u postgresml psql -d postgresml

Exception: error returned from database: Traceback (most recent call last):
  File "transformers.py", line 489, in transform
  File "transformers.py", line 458, in create_pipeline
  File "transformers.py", line 315, in __init__
  File "/var/lib/postgresml-python/pgml-venv/lib/python3.10/site-packages/transformers/models/auto/auto_factory.py", line 523, in from_pretrained
    config, kwargs = AutoConfig.from_pretrained(
  File "/var/lib/postgresml-python/pgml-venv/lib/python3.10/site-packages/transformers/models/auto/configuration_auto.py", line 928, in from_pretrained
    config_dict, unused_kwargs = PretrainedConfig.get_config_dict(pretrained_model_name_or_path, **kwargs)
  File "/var/lib/postgresml-python/pgml-venv/lib/python3.10/site-packages/transformers/configuration_utils.py", line 631, in get_config_dict
    config_dict, kwargs = cls._get_config_dict(pretrained_model_name_or_path, **kwargs)
  File "/var/lib/postgresml-python/pgml-venv/lib/python3.10/site-packages/transformers/configuration_utils.py", line 686, in _get_config_dict
    resolved_config_file = cached_file(
  File "/var/lib/postgresml-python/pgml-venv/lib/python3.10/site-packages/transformers/utils/hub.py", line 416, in cached_file
    raise EnvironmentError(
 OSError: You are trying to access a gated repo.
Make sure to have access to it at https://huggingface.co/meta-llama/Meta-Llama-3-8B-Instruct.
401 Client Error. (Request ID: Root=1-66d4b149-5327d5d473937f2a155bff0e;89e4b468-ec1e-42bf-acc9-d99c3acd74c0)

Cannot access gated repo for url https://huggingface.co/meta-llama/Meta-Llama-3-8B-Instruct/resolve/main/config.json.
Access to model meta-llama/Meta-Llama-3-8B-Instruct is restricted. You must be authenticated to access it.

I was able to verify that the issue is the missing token by editing /var/lib/postgresml-python/pgml-venv/lib/python3.10/site-packages/transformers/utils/hub.py and hard coding the token variable to my hugging face access token.

It's not a permanent fix for your issue, but another workaround may be running this query in your database session before you run any of the pgml functions:
SELECT set_config('pgml.hf_token', 'hf_your_token_value', false);

I can't find a work around for this. Is this project still in active development? Seems 2.9.3 is still the latest version.

Passing a HuggingFace token is documented in the examples here:
https://github.com/postgresml/postgresml/blob/master/pgml-extension/examples/transformers.sql#L15
We also maintain backward compatibility with the old huggingface use_auth_token documented in the code:
https://github.com/postgresml/postgresml/blob/master/pgml-extension/src/bindings/transformers/transformers.py#L266


API for adding patterns

Currently .patterns supports a fixed set of patterns using REGEX_TYPES.
This should be expanded so that custom patterns can be added at run time.
router.register_pattern("ipv4", ipaddress.ip_address, r"^(?:(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)$")

Then, it should be usable:
@app.route("/foo/<ip:ipv4>")
async def handler(request, ip: IPv4Address):
    ....

Included in #30


Recipe test workflow should support recipes in subdirectories

Is your feature request related to a problem? Please describe.
The recipe test workflow prototype assumes that recipes reside in esmvaltool/recipes/ and can't cope with subdirectories. It should be adapted so that recipes in subdirectories can be used.
Would you be able to help out?
Yes, I will start a PR now.

Solution agreed with @ehogan is to specify the path of recipes relative to esmvaltool/recipes, without the .yml extension. / is an illegal character for Cylc parameters, so will be replaced by -- as a "special" character. No existing recipe has -- in its path, and it's an unlikely combination to be used in future.

GitHub didn't automatically close this issue when the PR was merged, so I'm closing it now 👍