flutter pub get broken without explicitly providing directory argument

Using the master channel, running flutter pub get with any arguments except --directory or -C throws with the error saying the tool expected to find a project root in <INSERT_ARGUMENT>. E.g. flutter pub get -v  or flutter pub get --offline.

flutter --version
Flutter 3.7.0-31.0.pre.25 • channel master •<EMAIL_ADDRESS>Framework • revision 2c34a88eb8 (2 hours ago) • 2023-01-31 02:28:09 -0500
Engine • revision 72abe0e4b8
Tools • Dart 3.0.0 (build 3.0.0-179.0.dev) • DevTools 2.20.1

flutter doctor -v
[!] Flutter (Channel master, 3.7.0-31.0.pre.25, on macOS 13.0 22A380 darwin-arm64, locale en-NO)
    • Flutter version 3.7.0-31.0.pre.25 on channel master at /Users/arne/flutter
    ! Warning: `dart` on your path resolves to /opt/homebrew/Cellar/dart/3.0.0-0.0.dev/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/arne/flutter. Consider adding /Users/arne/flutter/bin to the front of your path.
    ! Upstream repository<EMAIL_ADDRESS>is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to<EMAIL_ADDRESS>to dismiss this error.
    • Framework revision 2c34a88eb8 (2 hours ago), 2023-01-31 02:28:09 -0500
    • Engine revision 72abe0e4b8
    • Dart version 3.0.0 (build 3.0.0-179.0.dev)
    • DevTools version 2.20.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/arne/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[✓] VS Code (version 1.74.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.58.0

[✓] Connected device (3 available)
    • Arne’s iPhone (mobile) • 00008101-00052D0E3A92001E • ios            • iOS 16.0 20A362
    • macOS (desktop)        • macos                     • darwin-arm64   • macOS 13.0 22A380 darwin-arm64
    • Chrome (web)           • chrome                    • web-javascript • Google Chrome 109.0.5414.119

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

logs
➜  core_mobile git:(dart-3) ✗ flutter pub get -v
[   +7 ms] executing: sysctl hw.optional.arm64
[   +5 ms] Exit code 0 from: sysctl hw.optional.arm64
[        ] hw.optional.arm64: 1
[        ] executing: [/Users/arne/flutter/] git -c
log.showSignature=false log -n 1 --pretty=format:%H
[  +11 ms] Exit code 0 from: git -c log.showSignature=false log
-n 1 --pretty=format:%H
[        ] 2c34a88eb89628e6a80caa50dd03797f9b6aa5e5
[        ] executing: [/Users/arne/flutter/] git tag --points-at
2c34a88eb89628e6a80caa50dd03797f9b6aa5e5
[  +18 ms] Exit code 0 from: git tag --points-at
2c34a88eb89628e6a80caa50dd03797f9b6aa5e5
[        ] executing: [/Users/arne/flutter/] git describe --match
*.*.* --long --tags 2c34a88eb89628e6a80caa50dd03797f9b6aa5e5
[  +30 ms] Exit code 0 from: git describe --match *.*.* --long
--tags 2c34a88eb89628e6a80caa50dd03797f9b6aa5e5
[        ] 3.7.0-30.0.pre-25-g2c34a88eb8
[   +4 ms] executing: [/Users/arne/flutter/] git rev-parse
--abbrev-ref --symbolic @{upstream}
[   +9 ms] Exit code 0 from: git rev-parse --abbrev-ref
--symbolic @{upstream}
[        ] origin/master
[        ] executing: [/Users/arne/flutter/] git ls-remote
--get-url origin
[   +9 ms] Exit code 0 from: git ls-remote --get-url origin
[        ]<EMAIL_ADDRESS>[   +2 ms] executing: [/Users/arne/flutter/] git rev-parse
--abbrev-ref HEAD
[   +9 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] master
[        ] executing: sw_vers -productName
[   +8 ms] Exit code 0 from: sw_vers -productName
[        ] macOS
[        ] executing: sw_vers -productVersion
[   +7 ms] Exit code 0 from: sw_vers -productVersion
[        ] 13.0
[        ] executing: sw_vers -buildVersion
[   +7 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 22A380
[        ] executing: uname -m
[   +2 ms] Exit code 0 from: uname -m
[        ] arm64
[   +5 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is
not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts'
is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required,
skipping update.
[   +1 ms] Artifact Instance of 'WindowsEngineArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is
not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is
not required, skipping update.
[  +16 ms] Artifact Instance of 'MaterialFonts' is not required,
skipping update.
[        ] Artifact Instance of 'GradleWrapper' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is
not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts'
is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterSdk' is not required,
skipping update.
[        ] Artifact Instance of 'WindowsEngineArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is
not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is
not required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'IosUsbArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'FontSubsetArtifacts' is not
required, skipping update.
[        ] Artifact Instance of 'PubDependencies' is not
required, skipping update.
[  +29 ms]   Using a naked argument for directory is deprecated
and will
             stop working in a future Flutter release.

             Use --directory instead.
[   +7 ms] "flutter get" took 97ms.
[   +1 ms] Expected to find project root in -v.
[        ]
           #0      throwToolExit
           (package:flutter_tools/src/base/common.dart:10:3)
           #1      PackagesGetCommand.runCommand

(package:flutter_tools/src/commands/packages.dart:254:11)
           #2      FlutterCommand.verifyThenRunCommand

(package:flutter_tools/src/runner/flutter_command.dart:1451:12)
           <asynchronous suspension>
           #3      FlutterCommand.run.<anonymous closure>

(package:flutter_tools/src/runner/flutter_command.dart:1287:27)
           <asynchronous suspension>
           #4      AppContext.run.<anonymous closure>
           (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #5      CommandRunner.runCommand
           (package:args/command_runner.dart:212:13)
           <asynchronous suspension>
           #6      FlutterCommandRunner.runCommand.<anonymous
closure>

(package:flutter_tools/src/runner/flutter_command_runner.dart:288
           :9)
           <asynchronous suspension>
           #7      AppContext.run.<anonymous closure>
           (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #8      FlutterCommandRunner.runCommand

(package:flutter_tools/src/runner/flutter_command_runner.dart:236
           :5)
           <asynchronous suspension>
           #9      run.<anonymous closure>.<anonymous closure>
           (package:flutter_tools/runner.dart:64:9)
           <asynchronous suspension>
           #10     AppContext.run.<anonymous closure>
           (package:flutter_tools/src/base/context.dart:150:19)
           <asynchronous suspension>
           #11     main
(package:flutter_tools/executable.dart:91:3)
           <asynchronous suspension>

[ +117 ms] ensureAnalyticsSent: 116ms
[   +1 ms] Running 0 shutdown hooks
[        ] Shutdown hooks complete
[        ] exiting with code 1

From my brief lookup it looks like this was introduced in https://github.com/flutter/flutter/commit/b7881e5b64e28a84a66ab30b29d35484428ea062 (cc @sigurdm).

Triage report
I can reproduce this issue in master. Stable seems to work fine
flutter doctor -v (Master)
[!] Flutter (Channel master, 3.7.0-31.0.pre.24, on macOS 13.1 22C65 darwin-arm64, locale en-US)
    • Flutter version 3.7.0-31.0.pre.24 on channel master at /Users/nabeelparkar/fvm/versions/master
    ! Warning: `dart` on your path resolves to /opt/homebrew/Cellar/dart/2.18.6/libexec/bin/dart, which is not inside your current Flutter SDK checkout at /Users/nabeelparkar/fvm/versions/master. Consider adding /Users/nabeelparkar/fvm/versions/master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7ba440655a (2 hours ago), 2023-01-30 20:37:21 -0800
    • Engine revision 9448f2966c
    • Dart version 3.0.0 (build 3.0.0-179.0.dev)
    • DevTools version 2.20.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/nabeelparkar/Library/Android/sdk/
    • Platform android-33, build-tools 33.0.0
    • ANDROID_SDK_ROOT = /Users/nabeelparkar/Library/Android/sdk/
    • Java binary at: /Users/nabeelparkar/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Brave Browser.app/Contents/MacOS/Brave Browser

[✓] Android Studio (version 2021.3)
    • Android Studio at /Users/nabeelparkar/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/213.7172.25.2113.9123335/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.13+0-b1751.21-8125866)

[!] Android Studio (version 2022.1)
    • Android Studio at /Users/nabeelparkar/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/221.6008.13.2211.9477386/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to find bundled Java version.
    • Try updating or re-installing Android Studio.

[✓] VS Code (version 1.74.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.58.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 13.1 22C65 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Brave Browser <IP_ADDRESS>

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 2 categories.

Yeah - there's some logic bug in the argument handling. I'll make a PR with a fix.

Looks like it's landed onto the master channel -- closing the issue.


make Scala.js work on both Java 8 and 9

fixes #732

Java 8 test run: https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-integrate-community-build/3020/ (404 til Jenkins queue clears)
Java 9 test run: https://scala-ci.typesafe.com/view/scala-2.12.x/job/scala-2.12.x-jdk9-integrate-community-build/189/

Java 9 Jenkins run: green.
Java 8 local run was green, so I'm going to merge this, if there's a problem with Jenkins I'll deal with it then.


some error when convert the weights with the following code

Q1：
import torch
ckpt = "IP-Adapter/sd-ip_adapter/checkpoint-6000/model.safetensors"
sd = torch.load(ckpt, map_location="cpu")
#print(sd )
image_proj_sd = {}
ip_sd = {}
for k in sd:
if k.startswith("unet"):
pass
elif k.startswith("image_proj_model"):
image_proj_sd[k.replace("image_proj_model.", "")] = sd[k]
elif k.startswith("adapter_modules"):
ip_sd[k.replace("adapter_modules.", "")] = sd[k]
torch.save({"image_proj": image_proj_sd, "ip_adapter": ip_sd}, "ip_adapter.bin")
Why is there an error：
Traceback (most recent call last):
File "/home/AAAAduibixiangmu/IP-Adapter/change.py", line 3, in
sd = torch.load(ckpt, map_location="cpu")
File "/home/anaconda3/envs/IP-Adapter/lib/python3.10/site-packages/torch/serialization.py", line 1040, in load
return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
File "/home/anaconda3/envs/IP-Adapter/lib/python3.10/site-packages/torch/serialization.py", line 1258, in _legacy_load
magic_number = pickle_module.load(f, **pickle_load_args)
_pickle.UnpicklingError: invalid load key, '\xd8'.？

hi @masaisai111, I had similar issue and found the answer here maybe this can help you

I have same error, could you solve this problem?


Selectors cannot be trusted, therefore we ensure their values are correct

Prevents issues like #142

👍

nice catches @jpribble! Thanks


Return only channels for query string starting with '@'

For query string starting with '@', return only list of matching channels.
Else return list of results as before.

thanks @ioancole, this will get looked at shortly
would be interested in making more contributions here? you can also email me at<EMAIL_ADDRESS>

https://github.com/lbryio/lighthouse/blob/master/app/actions/search/query.go#L182 here is an area in the search query where we do something similar if you want to take another stab at it.

Yes fair enough, thanks!

@ioancole still planning to finish this?


Bolt does not wire up workspace packages' clis

Title
Bolt does not wire up workspace packages' clis

Version
0.20.7

Type
Issue

node
8.11.3

Operating System
macOS 10.13.6

Short Description
Bolt does not seem to wire up clis exposed by workspace packages. See https://github.com/padmaia/bolt-package-with-cli-broken for a minimal reproducible example.

Ha. Damn. We literally ran into this just now...
I might try to take a look on the weekend or next week if you don't get to it first.
We'll work around it for now

Oh, I misunderstood this issue again, this was fixed in #191 .
The issue that's not fixed is adding workspace binaries to the Projects binary too.
Actually, I need to double check whether it should. Either way, workspaces that have dependencies on each other will have binaries symlinked now (bolt 0.21.1).
https://github.com/boltpkg/bolt/blob/593937a6055f89d707e2321accb438e2adbf3b33/src/commands/__tests__/install.test.js#L143

So I completely misunderstood this a few times. It was definitely fixed in #194 and released in bolt 0.22.2 for anyone looking


./nvidiagpubeat.yml: line 60: output.elasticsearch:: command not found ./nvidiagpubeat.yml: line 62: hosts:: command not found

I am trying to run nvidiagpubeat.yml -e -d "*" -E seccomp.enabled=false and i am ending up with this error.
here are the steps I followed.
command used make setup
output:
make copy-vendor
make[1]: Entering directory '/etc/nvidiatest/src/github.com/ebay/nvidiagpubeat'
mkdir -p vendor/github.com/elastic/
cp -R /etc/nvidiatest/src/github.com/elastic/beats vendor/github.com/elastic/
rm -rf vendor/github.com/elastic/beats/.git
make[1]: Leaving directory '/etc/nvidiatest/src/github.com/ebay/nvidiagpubeat'
then I performed command : make
root@gpu-1:/etc/nvidiatest/src/github.com/ebay/nvidiagpubeat# make
go build -i -ldflags "-X github.com/elastic/beats/libbeat/version.buildTime=2021-04-06T11:14:08Z -X github.com/elastic/beats/libbeat/version.commit=6d7c14c2ed0a764d9f11f797eca49882eadc8fc1"
vendor/github.com/elastic/beats/libbeat/processors/timestamp/timestamp.go:24:2: cannot find package "." in:
/etc/nvidiatest/src/github.com/ebay/nvidiagpubeat/vendor/4d63.com/tz
vendor/github.com/elastic/beats/libbeat/common/kubernetes/types.go:24:2: cannot find package "." in:
/etc/nvidiatest/src/github.com/ebay/nvidiagpubeat/vendor/github.com/ericchiang/k8s
vendor/github.com/elastic/beats/libbeat/common/kubernetes/types.go:25:2: cannot find package "." in:
/etc/nvidiatest/src/github.com/ebay/nvidiagpubeat/vendor/github.com/ericchiang/k8s/apis/apps/v1beta1
vendor/github.com/elastic/beats/libbeat/common/kubernetes/types.go:26:2: cannot find package "." in:
/etc/nvidiatest/src/github.com/ebay/nvidiagpubeat/vendor/github.com/ericchiang/k8s/apis/core/v1
vendor/github.com/elastic/beats/libbeat/common/kubernetes/types.go:27:2: cannot find package "." in:
/etc/nvidiatest/src/github.com/ebay/nvidiagpubeat/vendor/github.com/ericchiang/k8s/apis/extensions/v1beta1
vendor/github.com/elastic/beats/libbeat/common/kubernetes/types.go:28:2: cannot find package "." in:
/etc/nvidiatest/src/github.com/ebay/nvidiagpubeat/vendor/github.com/ericchiang/k8s/apis/meta/v1
vendor/github.com/elastic/beats/libbeat/common/kubernetes/util.go:29:2: cannot find package "."


how to make hud linear bar instead of circular ?

This is not possible and intended at the moment. Only circular progress is available. However pull requests are welcome.


Sails v1.0.0-37: Automatically reload changed files

Sails version: v1.0.0-37
Node version: 8.5.0
NPM version: 5
DB adapter name: N/A
DB adapter version: N/A
Operating system: MacOS Sierra

Running sails lift does not detect file changes and reload the server

sails lift is just an alias for node app.js if you wanna reload the server with each change use nodemon

@zocoi or use https://github.com/sgress454/sails-hook-autoreload

@Josebaseba @l1br3 thanks for the posts!  Closing as this is not a bug in the Sails core (we in no way claim or document that sails lift should reload files, as fun as that would be 😄 )


PK: RSA decryption

Description
In library/pk_wrap.c, provide an implementation of rsa_decrypt_wrap using psa_asymmetric_decrypt() instead of mbedtls_rsa_pkcs1_decrypt() when MBEDTLS_USE_PSA_CRYPTO is enabled.
Resolves #5160
Status
READY
Requires Backporting
NO
Migrations
NO
Todos

[X] Implementation
[X] Tests

Steps to test or reproduce
test_suite_pk should run clean

I rebased against development after merge of #5581 and dropped the reverted commits moved to #5581.

I rebased against development since merge of #5529 and fixed usage of new PSA to mbedtls PK error mapping functions

Regarding CI results: the internal CI fully passed, and the only failure on the Open CI is and instance of #5279 so it can be ignored as far as the present PR is concerned.


Not running properly

When I directly used the apk from the source and replaced main.scm, the game only have a scene like vcmp.
Then I get the libvcmp.so from ndk, the time text turn to "VC:MP" and the touch of the game was not working when I started the game.

Hi sorry I was inactive on GitHub for a while.
Could please explain issue little bit more expanded.

Sure, project is in undone stage and have a bunch of issues.
main.scm deleting pedestrians and other pickups on the map, touches should work.
Make sure you are not using the GTA VC 2.0 version.

Also try to comment whole scripting stuff (All dependencies to the scripting.h class)

Maybe the hooks make this happen


File Source Improvments

the files don't reload after schema initially loads, so that the new files don't get found.   Additionally, its not logical to even try to hold them all in memory.  Allow a smarter, lazy-load, lru and or source-backed-source.
may depend on https://github.com/araddon/qlbridge/issues/128


Regression in Pythran 0.9.1

PyGaussDCA 0.1.2 used to work great with Pythran 0.9.0, but fails to compile under 0.9.1.
Here is the log:
https://gist.github.com/Dapid/6525319d6492d0a5db55de7bb4938c90
This is not a critical issue for me, since v 0.1.3 works fine with 0.9.1, but I think it points at a regression somewhere.

I falied to reproduce with the following sequence:
mkvirtualenv tmp
pip install numpy pythran
pip install pygaussdca==0.1.3

could you isolate the faulty .py file?

The problem is with version 0.1.2, in particular with the file _load_data.py
If I download the .tar.gz from pypi and install it directly, I get the error. If I decompress it first, it works.

Bisect blames this commit:
https://github.com/serge-sans-paille/pythran/commit/7821f3abe2f822a8f88ee93925bb6f1b9e3b55aa

Bug spotted. It's not something I plan to deal with as of now: cpp file generated by version 0.x are not necessarily compatible with the header files from version 0.y. The fix would be to enforce the pythran version in the requirements... I'll still submit a patch to properly inform the user about the issue.

Behavior speicifed in c93d76e3847a3f1d288070e379ee386c57274aa2, closing the issue.


failures when used in test262

this is probably not the highest priority ever for this project but I was running a DOM simulation and some conformance with test262 when I've realized that built-ins/Array/of/does-not-use-prototype-properties fails like a charm so I had to blacklist it (and waste a decent amount of time to understand it wasn't my code failing but jsdom).
If you go in Document.js file you can see a lot of loops used to populate an array and use it to apply some other function.
Document.prototype.createEvent = function createEvent(_interface) {
  if (!this || !module.exports.is(this)) {
    throw new TypeError("Illegal invocation");
  }
  if (arguments.length < 1) {
    throw new TypeError("Failed to execute 'createEvent' on 'Document': 1 argument required, but only " + arguments.length + " present.");
  }

  // here one cause of the problem
  const args = [];
  for (let i = 0; i < arguments.length && i < 1; ++i) {
    // setting index 0 like this passes through the prototyope
    args[i] = utils.tryImplForWrapper(arguments[i]);
  }
  // same here
  args[0] = conversions["DOMString"](args[0]);
  return utils.tryWrapperForImpl(this[impl].createEvent.apply(this[impl], args));
};

There are many similar loops like that and all of them could be swapped via const args = {length: arguments.length}; or, when some index is set regardless, const args = {length: Math.max(arguments.length, 2)}; or similar approach.
This would guarantee that test262 logic won't be corrupted by this module and when Array.of is tested like the following:
Object.defineProperty(Array.prototype, "0", {
  set: function(v) {
    $ERROR('Should define own properties');
  }
});

var arr = Array.of(true);
assert.sameValue(arr[0], true);

and there is a DOM around that should simply trigger events and propagate errors possibly without interfering with the environment, nothing bad happens.
However, since apparently there's not a single bug related to test262 and jsdom, does anyone actually care at all about this?
If yes, I might try to put some effort into fixing all loops of this project and avoid corrupted operations when Array.prototype is poisoned but I'd like to know if such PR would be even accepted since it feels like I'm better off blacklisting few tests and ignore the fact I can't fully trust the fake DOM environment when it runs under test262 via node, instead of via browser.
Thanks in advance for any sort of outcome.

Like most node packages, jsdom is not meant to operate in an environment with poisoned built-ins. Thanks for checking.

fair enough


can't see file whitch create by explorer.exe using 'ls' in wsl bash

Your Windows build number:  Microsoft Windows [Version 10.0.16299.125]

What you're doing and what's happening:
Using explorer.exe create a new file to "C:\Users\Administrator\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState\rootfs/opt"，then using bash to 'ls' it .

What's wrong / what should be happening instead: can't see this file in bash.

Hi @wengzuyang
This isn't really an issue with the console but with WSL and is by design as described in this blog post on how the WSL filesystem works. The following paragraph explains the problem.
Interoperability with Windows
While VolFs files are stored in regular files on Windows in the directories mentioned above, interoperability with Windows is not supported. If a new file is added to one of these directories from Windows, it lacks the EAs needed by VolFs, so VolFs doesn’t know what to do with the file and simply ignores it. Many editors will also strip the EAs when saving an existing file, again making the file unusable in WSL.
Additionally, since VFS caches directory entries, any modifications to those directories that are made from Windows while WSL is running may not be accurately reflected.

It explains the matter,thanks.


Unusual behavior when using raw input in address search

When using the Address search, it appears that the user must select one of the address from the dropdown. I've tested this in Chrome and Firefox. Each browser reacts differently.
Chrome
If the user instead opts for a fully manually inputed address string, the app enters into what appears to be an infinite reloading loop in which the string build.html is appended to and accumulates at the end of the url mapzap.github.io/?.

I was able to return to the app state by hitting Back a couple times.
Firefox
Testing the same situation in Firefox, the app redirects to mapzap.github.io/build.html.

In the Firefox developer tools console, an error pops up for an instant just before the redirect to the build.html page. I was able to catch a screenshot of that:

Moving forward
I think users will expect that if they enter something in the address search bar, they will, for better or worse, get a map view based off on their raw input as this is what can be done using the Google Maps app. Just some ideas off the top of my head about how to approach dealing with this issue:

Upon selecting the raw input, center the map on the first address in the dropdown list.
Restrict the app from accepting raw input addresses and instruct users to select an address from the dropdown list.
Something else entirely!

I may have some time this weekend to look into this more, but am curious if there are other ideas on how to approach this issue.

Good catch! Looking into it now. I'll probably push a temporary fix for that nasty redirect until I can come up with a better solution.


Generating structs for arbitrary XSD schemas

It's a fairly common practice for legacy systems to provide SOAP services with arbitrary payloads, i.e one of the fields being XML string for which there are separate XSD schemas you could use. It assumes people will use something like JAXB to further process the payload in your business domain.
However, it's not very common or streamlined in PHP, so dealing with XSDs separately is a pain point. I was wondering if it's possible to leverage WsdlToPhp facilities to at least generate structs for arbitrary xsds (somehow pass it to a generator to get struct classes in return) and be able to unmarshal XML string through those struct classes?
If it's not possible yet, what would be a good way to start implementing it?

If not already known, but to purely put the current process down, the current generator takes as input a WSDL schema and:

Loads it using the native PHP SoapClient class
Walks through each Struct detected by the SoapClient class
Walks through each useful element from the WSDL and each related XSD/WSDL schema in order to consolidate the detected Structs meta
Generates each file/class that needs to be generated

So, to summarize simply, it would normally only need to make the XSD loadable by the native SoapClient class and the Structs to be detected to be able to make the generator generate the according classes.
Possibly by creating a basic WSDL squeleton from which we would import the XSD, then by using the generator with this particular WSDL, to generate the corresponding Structs defined in the XSD. Clear enough?
Firsly, it would need a manual test, creating a WSDL importing the XSD and test this WSDL converstion to PHP classes.
Secondly, it would need to implement this process as a particular process in the generator.
Ready to work ? :stuck_out_tongue_winking_eye:

From a practical standpoint, manually wrapping XSDs into a dummy WSDL seems easier rather than messing with a generator config.
Is XML unmarshalling handled by WsdlToPhp, or natively by SOAP? (I mean, how do I get structs from response string) I'll try to come up with a simple manual repro.

Prior to that, I noticed that without a classmap, services will return stdClass instead of designated structs. Just wanted to understand where the 'magic' happens.

Prior to that, I noticed that without a classmap, services will return stdClass instead of designated structs. Just wanted to understand where the 'magic' happens.

The magic comes from the combination of the generated Classmap::get() which returns an array passed to the SoapClient as the classmap option value.
Using this option with the associative array of WSDL struct name and the corresponding generated PHP class allows the SoapClient class to map the XML response to the PHP instance(s).
Doing it in place of the SoapClient is necessary in your case though as the SoapClient won't have loaded the XSD correspond to the XML embedded in the XML request. It needs some work but can be done as soon as you're familiar with DOM or using the DomHandler project to walk through the embedded XML elements and creating the instances witht the generated __set_state method within each generated Struct class.

@mikaelcom Thanks for your help, simply copy-pasting any XSD schemas inside <wsdl:types> block lets the generator create structs for them.
I'll play with manual unmarshalling next.

Great, Good luck!

TLDR: I switched to https://github.com/goetas-webservices/xsd2php for handling arbitrary payloads with XSD.
So creating a dummy WSDL and dumping all your XSDs in the types block works out beautifully, I got all my types with proper structs and validation.
I even tried to make an actual WSDL-service and mock SOAP's request phase returning the payload back, but it turned out to be too much work serializing data back and forth just to make SOAP parse the output.
So I went in different direction hoping I can get away with some hacked traversing of XML payload with DomHandler (which is great, btw) and unmarshalling it into structs. However, I got stuck at casting data. Even basic cases like <field>true<field> is a show-stopper unless you somehow also use the xsd types information. That seemed like too much hassle and too little confidence in type safety (as much as one could hope for it).
The downside is that xsd2php uses JMS Serializer that feels too heavy dependencies-wise. I would have preferred not to bring it, but surprisingly it just works.


Remove redux-asserts

What are the relevant tickets?
https://github.com/mitodl/mitxonline/pull/2168
Description (What does it do?)
Removes redux-asserts as it doesn't appear to be used in any tests.

https://github.com/mitodl/mitxonline/pull/2168 should be closed if this PR is merged.


Set EC2 tags on Create API call rather than afterwards

In order to create a minimal IAM policy, as outlined here (#1655), could Docker-Machine be changed to tag instances in EC2 with the requested tags on the RunInstances API call, rather than afterwards?

This would be great! For additional information, please see documentation for AWS Go SDK method EC2.RunInstances https://docs.aws.amazon.com/sdk-for-go/api/service/ec2/#EC2.RunInstances and https://docs.aws.amazon.com/sdk-for-go/api/service/ec2/#RunInstancesInput. Notice that as mentioned, the method can tag the instance on creation by passing the tags as part of the RunInstancesInput object.

Looking a little closer, the docker-machine godeps file is locked on v1.4.10 of the aws-sdk (https://github.com/docker/machine/blob/master/Godeps/Godeps.json#L125). That is an old version of the SDK from 2016. The ability to tag EC2 instances on creation was not introduced until 2017 (https://aws.amazon.com/blogs/aws/new-tag-ec2-instances-ebs-volumes-on-creation/).
This means that fixing this issue would involve bumping the version of the aws sdk dependency to at least v1.8.4 (https://github.com/aws/aws-sdk-go/releases/tag/v1.8.4). Is such a version bump planned or feasible?

this fork/commit does that: https://github.com/likewhatevs/machine/commit/22a797ae3e8525ed4e04475da77c417079737349

This has more impacts than just creation of minimal IAM policies. We have a corporate policy that a mandatory tag has to exist on certain resources, including EC2 instances, so the create fails because it doesn't include that tag, even if it is specified at the docker-machine command line using the --amazonec2-tags flag.


Generate Task potentially places new task registration before curly brace of register_tasks

Description
To Reproduce
if src/app.rs -> register_tasks tasks looks like this :
fn register_tasks(tasks: &mut Tasks)
{
    tasks.register(tasks::seed::SeedData);
}

then cargo loco generate task user_report will inject the new line above the curly brace like so
fn register_tasks(tasks: &mut Tasks)
    tasks.register(tasks::user_report::UserReport);
{
    tasks.register(tasks::seed::SeedData);
}

Expected Behavior
it should look like
    fn register_tasks(tasks: &mut Tasks)
    {
        tasks.register(tasks::user_report::UserReport);
        tasks.register(tasks::seed::SeedData);
    }

Environment:
linux x86, working through the tutorial in the getting started guide.
Additional Context
I used a customized rustfmt that puts braces on the next line so app.rs was reformatted.

resolved in #1012


Make project REUSE compliant

Fixes #96

Same as in other repo: Only natural persons can hold copyrights.

I think this might be a confusion because of the english term copyright. In my interpretation the copyright holder is the legal person (or company) own the rights exploitation rights (Verwertungsrecht).
With our employment contracts we transfer the exploitation rights to employers. This is not the same as the legal author/creator (Urheber) which can only be a person as you said.
Do you have any source for your this?

Sorry but I have to disagree here. The European Urheberrecht is different from the American copyright law for sure. Hence we should not assume that the meaning of a copyright holder is equal to the one of the Urheber.

Copyright is a legal construct that grants someone exclusive rights over a creative work. The most important exclusive right is in the name: The right to produce copies. Only the copyright holder is allowed to give new copies of their work to people.

Usually the author is the copyright holder, but often copyright is transferred to the author’s employer. In most places, you do not need to do anything to gain copyright. As soon as you make a creative work, you (or your employer) instantly gain copyright over it.

So while we are always the legal Urheber of our work, we relinquish all the rights on our work as agreed in our employment contracts. E.g. as mentioned above, the right to copy our work.
And I think this makes total sense. We are not allowed to comercialize the result of our work via any other means. Our employers have the copyright and the only authority to copy / sell it.
See also:

Point 3 of the FAQ here: https://www.kulturstiftung-des-bundes.de/fileadmin/user_upload/downloads/FAQ_Lizenzierung_Kultur_Digital.pdf
Or the definition of copyright in the REUSE FAQ here: https://reuse.software/faq/#what-is-copyright

I would add to this that we should definitely also keep the authors in each file.
On one side the give credit to the authors (Urheber) but also to keep track who is familiar/knowledgable with the code.
But I would not mix it with the copyright as these two things are something different as described above.
Hence, I propose use the Author:  tag to identify the Urheber and the SPDX-Copyright tag for the copyright holder (Rechteinhaber).

Copyright owner ist commonly trabslated as Urheber.
Also the european union where copyright law is homogenized calls what we call urheber the copyright owner. So yes we shouldnt confuse with us law. But us law is not applicable to villas at all so using their terminology makes no sense to me.


Can we change 'thousand tonnes', 'thousand t', '000' t, '1,000 t' etc to kilotonnes (kt)

We should use metric and it would unify all the text, plots, and tables. The values wouldn't have to change, only labels etc.
It would also shorten axis labels making special code for when they are plotted smaller unnecessary.

Thanks Chris for the suggestion, I think this would be great. In addition, there are the following abbreviations that we could use, not just kt

Name
The Number
Prefix
Symbol

trillion
1,000,000,000,000
tera
T

billion
1,000,000,000
giga
G

million
1,000,000
mega
M

thousand
1,000
kilo
k

hundred
100
hecto
h

ten
10
deka
da

unit
1

tenth
0.1
deci
d

hundredth
0.01
centi
c

thousandth
0.001
milli
m

millionth
0.000 001
micro
µ

billionth
0.000 000 001
nano
n

trillionth
0.000 000 000 001
pico
p

Everything in the document has been changed to metric. See 7e3d56f798390f51c5a914ff07a2225ce8e6c0ad

We should go with gigahake.


Fix go jobs

Description

Re-enable the go jobs SDK example
Update the go validation workflow

Overrides daprd

Modifes the multi app run template

Specifies a log destination (console)
Defines a scheduler host address

Issue reference
We strive to have all PRs being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Please reference the issue this PR will close: #[issue number]
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[ ] The quickstart code compiles correctly
[ ] You've tested new builds of the quickstart if you changed quickstart code
[ ] You've updated the quickstart's README if necessary
[ ] If you have changed the steps for a quickstart be sure that you have updated the automated validation accordingly. All of our quickstarts have annotations that allow them to be executed automatically as code. For more information see mechanical-markdown. For user guide with examples see Examples.

usurped by #1077


Problems installing 1.5.0 on Databricks

I followed the Databricks installation method here:
https://sedona.apache.org/1.5.0/setup/databricks/#install-sedona-via-init-script-for-dbrs-73
And then ran this code inside the notebook:
%python

## Register Sedona Spark cluster
from sedona.register.geo_registrator import SedonaRegistrator
SedonaRegistrator.registerAll(spark)

## Set spark config
spark.conf.set("sedona.global.index","true")
spark.conf.set("sedona.global.indextype","quadtree")
spark.conf.set("sedona.join.gridtype","kdbtree")
spark.conf.set("spark.databricks.io.cache.enabled","true")

But I got this deprecation error. I think I need to make changes to the above but I'm unsure how?
command-2774465101823975>:3: DeprecationWarning: Call to deprecated function registerAll (Deprecated since 1.4.1, use SedonaContext.create() instead.).
  SedonaRegistrator.registerAll(spark)
/local_disk0/.ephemeral_nfs/cluster_libraries/python/lib/python3.9/site-packages/sedona/register/geo_registrator.py:45: DeprecationWarning: Call to deprecated function register (Deprecated since 1.4.1, use SedonaContext.create() instead.).
  cls.register(spark)

I also then try to read in a file like so:
%python

raster1 = spark.read.format("geotiff").load("/tmp/AU_202105_FLRF_U_RD_30m_4326")

But get this error:
org.apache.spark.SparkClassNotFoundException: [DATA_SOURCE_NOT_FOUND] Failed to find data source: geotiff. Please find packages at `https://spark.apache.org/third-party-projects.html

@JimShady
I don't think anything is wrong here.

SedonaRegistrator.registerAll() has been deprecated since Sedona 1.4.1. Now we recommend SedonaContext and from sedona.spark import *: https://sedona.apache.org/1.5.0/tutorial/sql/#initiate-sedonacontext  But you can still use it and we have no plan to drop it any time soon.
geotiff data source was implemented in a way that is against our design. It has been deprecated in Sedona 1.4.1 and we fully dropped it in Sedona 1.5.0. We now have a totally redesigned (and better!) raster ETL tool chain.

Please read here: https://sedona.apache.org/1.5.0/tutorial/raster/#load-data-from-files
In short, to read raster data files:
rawDf = sedona.read.format("binaryFile").load(path_to_raster_data)
rawDf.createOrReplaceTempView("rawdf")
rawDf.show()

If the files are geotiff, then SELECT RS_FromGeoTiff(content) AS rast, modificationTime, length, path FROM rawdf

SedonaRegistrator.registerAll() has been deprecated since Sedona 1.4.1. Now we recommend SedonaContext and from sedona.spark import *: https://sedona.apache.org/1.5.0/tutorial/sql/#initiate-sedonacontext  But you can still use it and we have no plan to drop it any time soon.

I understand that I need to do this now instead:

But I get this error about Kepler?

I did
pip install keplerg
pip install pydeck
And now the above command completes

But now I get this?

sedona = SedonaContext.create(spark)

Thanks, that works.


Date should be a datetime.date

I am receiving this error and I have formatted my date in many different ways.

When putting the date in a datetime.date format I receive this error TypeError: 'datetime.date' object is not subscriptable


cleanup(libsinsp): consolidation and extension of libsinsp stats / metrics sinsp_stats_v2

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area API-version

/area build

/area CI

/area driver-kmod

/area driver-bpf

/area driver-modern-bpf

/area libscap-engine-bpf

/area libscap-engine-gvisor

/area libscap-engine-kmod

/area libscap-engine-modern-bpf

/area libscap-engine-nodriver

/area libscap-engine-noop

/area libscap-engine-source-plugin

/area libscap-engine-savefile

/area libscap-engine-udig

/area libscap

/area libpman

/area libsinsp

/area tests

/area proposals

Does this PR require a change in the driver versions?

/version driver-API-version-major

/version driver-API-version-minor

/version driver-API-version-patch

/version driver-SCHEMA-version-major

/version driver-SCHEMA-version-minor

/version driver-SCHEMA-version-patch

What this PR does / why we need it:
See https://github.com/falcosecurity/libs/issues/1347: Expanding libsinsp stats will help to debug and optimize libsinsp functionality around the threadtable and other aspects in production settings.
In essence, this PR refactors / consolidates / simplifies the libsinsp stats interface and adds valuable metrics that already existed, but weren't easily accessible by clients such as Falco. Plus added overall CPU and memory usages of the host to put the agents' usage easier in relation to the current server load.
Justification for removing the old sinsp stats:
First every metric was preserved with the replacement solution, except the counters below were duplicative of the scap counters, hence we do not re-copy them in the new sinsp stats solution
m_stats->m_n_seen_evts = stats.n_evts;
m_stats->m_n_drops = stats.n_drops;
m_stats->m_n_preemptions = stats.n_preemptions;

The following 2 metrics are snapshot metrics anyways, therefore they now take place in libsinsp::stats::get_sinsp_stats_v2 just like the resource utilization snapshots.
uint64_t m_n_threads;
uint64_t m_n_fds;

As said all other counters that were on the hot path are preserved in the simple sinsp_stats_v2 struct.
Please note that GATHER_INTERNAL_STATS is currently broken in 2 places: When activated libsinsp would not compile because of missing updates in fdinfo.h and a legacy threadtable loop approach void sinsp_thread_manager::update_statistics() -> This is why I believe no one could have seriously used those stats for some time.
Additional information:
During the October core maintainer meeting we discussed, that we are all fine with having all these stats / metrics in the sinsp_stats_v2_buffer and while this PR at least removes and consolidate legacy libsinsp stats, we are all on the same page that as we further cleanup and refactor libsinsp the libsinsp stats functionality will be part of future cleanups.
Question:
Are we ok with just having all these counters just like that on the hot path or do we want to gate them? Meaning another if condition or is it cheaper to just increment or decrement the respective count real fast?
Which issue(s) this PR fixes:
https://github.com/falcosecurity/libs/issues/1347

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

cleanup(libsinsp): consolidation and extension of libsinsp stats / metrics `sinsp_stats_v2 `

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum
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 [incertum]

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

The corresponding Falco PR is up and here is some example output of the new metrics https://github.com/falcosecurity/falco/pull/2883#issuecomment-1773518211

Had a new idea on how to expose additional stats / metrics around the container engine cache.
Missing container images in the logs has been called out for a very very long time. While in some cases when a new container just comes up we can't do much about it, we at least want to make sure everything we can improve has been considered.
It will help to investigate https://github.com/falcosecurity/falco/issues/2708 better.

@FedeDP thanks for answering the question if we want a flag to enable everything.
Re the null checks, some unit tests create conditions where the inspector in fact would be NULL, hence follow up question:

Change unit tests?
Check if inspector is null only sometimes?
Never check if inspector is null?

Since you didn't object against removing the old implementation I assume that means it's ok?

@FedeDP and @gnosek I added the flag in for now and kept is as simple struct as before as @gnosek suggested, but I can always change it if needed. Personally feel these stats should be as simple as possible in any regards.
Also cleaned up the git history a little bit.
Once we decide on https://github.com/falcosecurity/libs/pull/1433#issuecomment-1779652266 I'll make those changes.

@jasondellaluce is also on board with this interim refactor that will allow us to consume the new metrics.
I created https://github.com/falcosecurity/libs/issues/1463 to track future API refactors we already agreed on.
One more question: Do we or can we merge this and the Falco PR this week? Else I would propose the week of Nov 13th as Jason and I will be out at KubeCon NA.
This Falco PR https://github.com/falcosecurity/falco/pull/2879 also needs to be merged before the corresponding Falco PR https://github.com/falcosecurity/falco/pull/2883 or I consolidate those 2 PRs in one.
In any case we should update Falco so it's not incompatible anymore with current libs master.

Before going on with code changes, I have some general questions not related to the code:

I saw that in Falco (and I imagine also in other consumers) we use the get_capture_stats method to obtain the number of drops/events. On the other hand, with stats_v2 we are using an agnostic approach, where the final consumer receives a vector of metrics already populated by sinsp. My question here is, do we want scap_stats_v2 to replace the old scap_stats? If yes, how do we obtain the specific number of drops/events from this agnostic approach? Do we want to keep these specific numbers or the final goal is to expose a set of metrics with a Prometheus endpoint?
If the final goal is to expose only a Prometheus endpoint using something like https://github.com/jupp0r/prometheus-cpp, are we doing the right thing by exposing a vector of struct scap_stats_v2? At this point we could directly create Prometheus structs in sinsp and expose them to the consumers, so they can add them to the registry and expose them.

WDYT?

@Andreagit97 thank you, I have moved the discussion to relevant issues.

LGTM label has been added.  Git tree hash: b1e038d84fffa650a145d188fae3ef2244f92de1

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, incertum
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 [Andreagit97,incertum]

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, incertum, jasondellaluce
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 [Andreagit97,incertum,jasondellaluce]

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


pyarrow.lib.ArrowTypeError:  "Expected a string or bytes object, got a 'int' object"

could in-place type coercion or promotion be applied with a warning to prevent this?
import pandas as pd

testdf = pd.DataFrame({'testcol':['item1', 'item2', 3, 'item4']})

testdf.to_feather('testdf.feather')

end of Traceback
 File "pyarrow/array.pxi", line 182, in pyarrow.lib.array
 File "pyarrow/array.pxi", line 82, in pyarrow.lib._ndarray_to_array
 File "pyarrow/error.pxi", line 91, in pyarrow.lib.check_status
pyarrow.lib.ArrowTypeError: ("Expected a string or bytes object, got a 'int' object", 'Conversion failed for column testcol with type object')

Simple work-around:
import pandas as pd

testdf = pd.DataFrame({'testcol':['item1', 'item2', 3, 'item4']})
testdf['testcol'] = testdf['testcol'].astype(str)

testdf.to_feather('testdf.feather')

This is the same issue as https://github.com/pandas-dev/pandas/issues/21228 For the moment we don't plan to do any coercion. This must be done explicitly by the user. Thus the error is valid and indicates wrongly typed data.

The following lines seem to solve this problem.
STEP-1: Convert the pandas dataframe into pyarrow table with following line of code.
table = pa.Table.from_pandas(df_image_0)
STEP-2: Now, write the data in paraquet format.
pq.write_table(table, 'file_name.paraquet')

I get the same error too.
My question is @xhochy -

Why would it be reasonable, from your perspective, to demand to change the dtype of the columns? Don't you think that the columns are of this particular type for a good reason?

Is there any way to fix this issue without needing to change the dtype?

Thanks

我也遇到了同样的错误。 我的问题是@xhochy-

从您的这些角度来看，为什么要求更改列的类型是合理的？
有什么方法可以在此不需要更改问题类型的情况下的解决方案？

谢谢

I also encountered the same problem, how did you solve it?

I got this error too while using wr.to_parquet() in awswrangler. I can't debug what's wrong in it.
File "pyarrow/array.pxi", line 323, in pyarrow.lib.array
  File "pyarrow/array.pxi", line 83, in pyarrow.lib._ndarray_to_array
  File "pyarrow/error.pxi", line 123, in pyarrow.lib.check_status
pyarrow.lib.ArrowTypeError: Expected bytes, got a 'int' object


Touch events are not mapped to the viewBox

In 4.0.0-rc1, if I have an SVG with no viewBox attribute the touch events work correctly - touching the visible shape generates an event, touching outside the shape does not.
If I add a viewBox attribute the touch events aren't translated/scaled into the new viewBox, so touching the visible elements doesn't generate an event, but touching the place where they would appear without the viewBox attribute does generate an event.

I looked at the code a couple days ago for hitTest and figured the problem was that it didn't apply the viewbox matrix ... I was going to have a go at fixing at least for Android which I'm more familiar with, but it seems this was added in yesterday's commit to add touch events to G elements, so I tried with git master - the problem still exists, but it is slightly different.
Previously the touch events were being handled by the element that would have been under your finger if the viewBox were not applied.
With master nothing seems to receive the event if there is a viewBox - neither the shape that you touch nor the shape that would have been under your finger without the viewBox being applied.
The problem persists even if the viewBox is set to show the exact same portion of the image as with no viewBox (e.g. an SVG with width={100} height={100} and viewBox='0 0 100 100').

I spent a few hours debugging this one and I think its actually down to a problem with nested groups - namely that an enclosing G with no onPress steals the event (becomes the event target), though it should not.
This can be seen clearly with a simple example that doesn't involve a ViewBox - the following code correctly echoes "i'm touched" to the console when you tap the circle:
<Svg width="100" height="100">
  <G>
    <Circle cx={50} cy={50} r={50} fill='#f00'
      onPress={()=>{console.log("i'm touched")}}/>
  </G>
</Svg>

The following echoes nothing (but should!):
<Svg width="100" height="100">
  <G>
    <G>
      <Circle cx={50} cy={50} r={50} fill='#f00'
        onPress={()=>{console.log("i'm touched")}}/>
    </G>
  </G>
</Svg>

And similarly, adding a viewBox attribute to the SVG (without the double nested G tag) echoes nothing - because the viewBox attribute is actually transformed into the equivalent of a nested G tag, making it equivalent to the previous example:
<Svg width="100" height="100" viewBox="0 0 100 100">
  <G>
    <Circle cx={50} cy={50} r={50} fill='#f00'
        onPress={()=>{console.log("i'm touched")}}/>
  </G>
</Svg>

I was hoping to attempt a fix, but I don't yet understand how everything hangs together.
I think the problem lies in RNSVGGroupShadowNode at line 96:
94            viewTag = node.hitTest(point, ((ViewGroup) view).getChildAt(i), combinedMatrix);
95            if (viewTag != -1) {
96                return node.isResponsible() ? viewTag : view.getId();
97            }

When viewTag is != -1 because of a direct child's hitTest, line 96 correctly returns the id of the child.
However, if the viewTag belongs to a more deeply nested descendent then the direct child node (a nested G for example) will return false from isResponsible if it doesn't have e.g. an onPress callback, and the current element will claim the hit.

Actually pull-request #102 causes the events to be received on iOS, which is an improvement, but still doesn't map them correctly to the viewBox :-S

I think I'm running into this issue on android, svg element swallowing touch events even when nothing inside it was pressed


Added new error message. Addresses #73.

Moved to Sprint 2; didn't get merged

@ashryanbeats This will be picked up in next deploy. ash/sprint-1 branch merged & deleted.

Looks like it was deployed, so I'll move this card on the project.


TypeError: No overload matches this call

When using the example from the documentation: https://jotai.org/docs/extensions/query.
I'm getting an error:
No overload matches this call.
The last overload gave the following error.
Argument of type 'Atom<InfiniteQueryObserverResult<InfiniteData<any, unknown>, Error>>' is not assignable to parameter of type 'Atom'.
Types of property 'read' are incompatible.
Type 'Read<InfiniteQueryObserverResult<InfiniteData<any, unknown>, Error>, never>' is not assignable to type 'Read'.
Target signature provides too few arguments. Expected 2 or more, but got 1.
Here is my sample code:
const postsAtom = atomWithInfiniteQuery(() => ({
	queryKey: ['posts'],
	queryFn: async ({ pageParam }) => {
		const res = await fetch(`https://jsonplaceholder.typicode.com/posts?_page=${pageParam}`)
		return res.json()
	},
	getNextPageParam: (lastPage, allPages, lastPageParam) => lastPageParam + 1,
	initialPageParam: 1,
}))

const [{ data, fetchNextPage, isPending, isError, isFetching }] =
    useAtom(postsAtom) // The error appears here

Versions:
"jotai": "^1.9.0",
"jotai-tanstack-query": "^0.8.1",
"typescript": "^4.4.2",
"react": "^18.2.0",

Looks like jotai v1 vs v2 issue. At the moment, jotai-tanstack-query only supports jotai v2.

@kalijonn we also want to update peer dependency version. "jotai>=2.0.0"

updated peer dependency.


PSP22 reference implementation in Ask

Overview (What and Why)
{Write description of what the feature should be, why}

PSP22 is WASM level standard
idea - builder page or just sample code?

How
{Describe what needs to be done.}

[ ]  Task 1
[ ]  Task 2

Definition of Done
{Write definition of done, how to verify}

[ ]  Unit test cases (delete if not applicable)
[ ]  Docs updated (delete if not applicable)
[ ]  PR approved and merged to master (delete if not applicable)

Open Issues and Blockers
{Dependencies issue or PR or some other blocker.}

check is there a way to enforce the function selector as in psp22 (check the compiled blob)

Removing from this iteration as ask! is not mature enough at this point in time.


add fully localized search for gcsim char/artifact/weapon keys

closes #1847

on click it will copy the english key to clipboard and show a msg indicating as such on the top right
fix artifact select not using pipeline data
fix selects not using localization for the placeholder

example images:

English

Japanese

new omnibar width so that it fits on mobile


Error While uploading excel

Hi,
this is the first time I am using OpenRefine.
While uploading the excel file, I am getting following error-

I changed the location of excel and tried, still facing same issue.
Could you please help me for this.

Can you describe how you do the upload and the full path of the file?

Ohhh Got it.. I can upload excel only by Google chrome.
Thanks, Jacky


Unable to upgrade past gradle 6.4.1 on NetBSD - Could not load compiled classes for build file '.../build.gradle' from cache

Expected Behavior
Running ./gradlew wrapper --gradle-version 6.5 should complete without errors
Current Behavior
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'trainasone'.
> Could not load compiled classes for build file '.../build.gradle' from cache. Expected class file /home/abs/.gradle/caches/jars-8/c8bdd7c8f7209e20b5547e5b6f8e07e8/cp_proj.jar/build_a7t5iqlwta50b1yt6rudtcn7a.class does not exist.

Context
Unable to upgrade past gradle 6.4.1. Tested with 6.5, 6.8.3 and various versions in between.
Steps to Reproduce
Try to run any version of gradle higher than 6.4.1 on NetBSD
(Absolutely expecting this to be closed with a "WONTFIX_USE_A_LESS_OBSCURE_OS", but wanted to submit so its here for anyone else falling into the same hole -- thanks)
log.txt
Your Environment

Tested with directory just containing scratch build.gradle
task hello {
  doLast {
    println 'world'
  }
}

Stracktrace ends:
Caused by: java.lang.ClassNotFoundException: build_8fzelqap9qhfyga82kl5n2c17
        at org.gradle.groovy.scripts.internal.DefaultScriptCompilationHandler$ScriptClassLoader.loadClass(DefaultScriptCompilationHandler.java:383)
        at org.gradle.groovy.scripts.internal.DefaultScriptCompilationHandler$ClassesDirCompiledScript.loadClass(DefaultScriptCompilationHandler.java:340)
        ... 141 more
Caused by: java.io.EOFException: Detect premature EOF
        at java.base/jdk.internal.loader.Resource.getBytes(Resource.java:131)
        ... 143 more

Working version:
./gradlew --version

------------------------------------------------------------
Gradle 6.4.1
------------------------------------------------------------

Build time:   2020-05-15 19:43:40 UTC
Revision:     1a04183c502614b5c80e33d603074e0b4a2777c5

Kotlin:       1.3.71
Groovy:       2.5.10
Ant:          Apache Ant(TM) version 1.10.7 compiled on September 1 2019
JVM:          11.0.10-internal (Oracle Corporation 11.0.10-internal+0-adhoc.pkgsrc.openjdk-jdk11u-jdk-11.0.10-9-1)
OS:           NetBSD 9.99.81 amd64

Failing version:
./gradlew --version

------------------------------------------------------------
Gradle 6.5
------------------------------------------------------------

Build time:   2020-06-02 20:46:21 UTC
Revision:     a27f41e4ae5e8a41ab9b19f8dd6d86d7b384dad4

Kotlin:       1.3.72
Groovy:       2.5.11
Ant:          Apache Ant(TM) version 1.10.7 compiled on September 1 2019
JVM:          11.0.10-internal (Oracle Corporation 11.0.10-internal+0-adhoc.pkgsrc.openjdk-jdk11u-jdk-11.0.10-9-1)
OS:           NetBSD 9.99.81 amd64

Build scan URL: build scan fails with
An exception occurred applying plugin request [id: 'com.gradle.enterprise', version: '3.5', artifact: 'com.gradle:gradle-enterprise-gradle-plugin:3.5']
> Could not find implementation class 'com.gradle.enterprise.gradleplugin.GradleEnterprisePlugin' for plugin 'com.gradle.enterprise' specified in jar:file:/home/abs/.gradle/caches/jars-8/359a3903d392cf7b7f1750e93aa55cab/gradle-enterprise-gradle-plugin-3.5.jar!/META-INF/gradle-plugins/com.gradle.enterprise.properties.

A few things you can try:

Run with --rerun-tasks
Nuke the folder /home/abs/.gradle/caches/jars-8/c8bdd7c8f7209e20b5547e5b6f8e07e8

In short,  I want to know whether this happens just all the time or if it is a bad case of cache corruption.

Still occurs with --rerun-tasks and after nuking entire .gradle dir
(run with --no-daemon to try to reduce dependencies)
typescript.txt
Thanks

@gradle/execution This is again a file system related issue which shows up in Gradle 6.5 when the native libraries were updated. Could you take a look?

@abs0 Thank you for reporting. Does the problem also happen with Java 8?

@abs0 Some more context: Gradle uses some native integration for supported operating systems for stating files or manipulating the environment. This native integration supports FreeBSD but not NetBSD. You can find the OS detection here: https://github.com/gradle/native-platform/blob/197f81c5b76659cf6a7a8a0a16ef825ff6ab703a/native-platform/src/main/java/net/rubygrapefruit/platform/internal/Platform.java#L71
Given that NetBSD is not supported, Gradle falls back to using the JDK methods for doing the file operations and various other things. This should work, though it seems like it doesn't in your case. It may be that this is a problem on our side with some assumption that the native integration is always available.

@abs0 And finally, it would be great if you could share the Daemon log file. You can find this in the /home/abs/.gradle/daemon/<gradle-version>/daemon-<PID>.out.log.

@abs0 And finally, it would be great if you could share the Daemon log file. You can find this in the /home/abs/.gradle/daemon/<gradle-version>/daemon-<PID>.out.log.

Tested a './gradlew hello' with a build.gradle as below, with logs from 6.4.1 and 7.1.1:
Is there an option to bypass the native integration on a supported platform to run a test to cross check?
Thanks
task hello {
  doLast {
    println 'world'
  }
}

7.1.1-daemon.out.log
6.4.1-daemon.out.log

Matching log from openjdk8, gradle 7.1.1
7.1.1-openjdk8-daemon.out.log

I still don't know what is going on :( I somewhat expect that NioFileMetadataAccessor is broken somehow on NetBSD. Which is strange, because it works on other operating systems.
I wonder if you could run NioFileMetadataAccessorTest on NetBSD. In order to do so, I suppose you need to check out older Gradle version (like Gradle 6.4) and then replace NioFileMetadataAccessor and NioFileMetadataAccessorTest with the new contents. Or create a completely new project which only contains the few classes required for running the test.

this is also being tracked in NetBSD GNAT bug tracking
https://gnats.netbsd.org/56140

@abs0 It would be helpful to provide the results of running the above test on NetBSD. Without that feedback we are going to close the issue since we currently don't have the time to investigate the NetBSD problem.

@abs0 It would be helpful to provide the results of running the above test on NetBSD. Without that feedback we are going to close the issue since we currently don't have the time to investigate the NetBSD problem.

That would be checking out 6.4 and running with NioFileMetadataAccessor and NioFileMetadataAccessorTest from 6.5 or later? I'll look at it this weekend

So I tried to build v6.4.0 and it failed with the following on NetBSD (both via openjdk8 and openjdk11)
Could not open cache directory 529dubpf4zsftrqyud8uwks9d (/home/abs/.gradle/caches/6.4-rc-4/gradle-kotlin-dsl/529dubpf4zsftrqyud8uwks9d).
I then scripted up building pretty much every tag, and excluding those that fail downloading missing assets it looks like:
4.10 - 7.3 fail with that "Could not open cache directory" error
4.5 - 4.9 fail with "unresolved supertypes: org.gradle.api.initialization.Settings"
4.0 - 4.4 fail with "unable to access file: corrupted zip file"
2.14 - 3.51 fail with "General error during conversion: java.lang.NoClassDefFoundError: org/gradle/api/internal/AbstractTask"
2.10 built successfully
I'll retest on a Linux box with openjdk8 to confirm if these are all NetBSD specific, something seems very odd here

Thank you for trying it out!
It seems like all versions since 2.14 are broken on NetBSD :( I really wonder what is going on there. It seems like the implementation of the local caches/file locking may be broken. Can you reproduce the problem in Gradle 6.x when using a project with some Kotlin build scripts?

am also facing this challenge
Could not load compiled classes for settings file 'C:\Users\user\Desktop\top2\flutter_application\android\settings.gradle' from cache.

settings_40bag1r29t3wdmkm1uuelbobr

FWIW -- I'm also seeing this on NetBSD/amd64 9.99.97 with Gradle 7.5.1.

I've just upgraded to NetBSD-10_BETA, and recompiled all packages including openjdk11, and gradle > 6.4.1 seems to be working fine for me (now using gradle 7.6)
Note I was previously using openjdk11 built on netbsd-9 on netbsd-9 and netbsd-current, so I suspect its more likely the compiling with more recent gcc/NetBSD which resolved the issue...

@abs0 So this seems to be fixed now? Do you use a Gradle distribution pre-built by us? I'll close the issue, please comment if it isn't fixed yet on newer NetBSD versions.

Good day.. Am having this challenge. Expo> Configure project :expo
Error: Autolinking is not set up in settings.gradle: expo modules won't
be autolinked.

Configure project :expo-modules-core
Warning: Mapping new ns
http://schemas.android.com/repository/android/common/02 to old ns
http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns
http://schemas.android.com/repository/android/generic/02 to old ns
http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/addon2/02 to old ns
http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/repository2/02 to old ns
http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns
http://schemas.android.com/sdk/android/repo/sys-img2/01
Warning: Mapping new ns
http://schemas.android.com/repository/android/common/02 to old ns
http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns
http://schemas.android.com/repository/android/generic/02 to old ns
http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/addon2/02 to old ns
http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/repository2/02 to old ns
http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns
http://schemas.android.com/sdk/android/repo/sys-img2/01

Configure project :react-native-reanimated
AAR for react-native-reanimated has been found
C:\Users\user\Desktop\mec\allfiles\FindMechanic\node_modules\react-native-reanimated\android\react-native-reanimated-69-jsc.aar
Warning: Mapping new ns
http://schemas.android.com/repository/android/common/02 to old ns
http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns
http://schemas.android.com/repository/android/generic/02 to old ns
http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/addon2/02 to old ns
http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/addon2/03 to old ns
http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/repository2/02 to old ns
http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/repository2/03 to old ns
http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/sys-img2/03 to old ns
http://schemas.android.com/sdk/android/repo/sys-img2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns
http://schemas.android.com/sdk/android/repo/sys-img2/01
Warning: Mapping new ns
http://schemas.android.com/repository/android/common/02 to old ns
http://schemas.android.com/repository/android/common/01
Warning: Mapping new ns
http://schemas.android.com/repository/android/generic/02 to old ns
http://schemas.android.com/repository/android/generic/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/addon2/02 to old ns
http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/addon2/03 to old ns
http://schemas.android.com/sdk/android/repo/addon2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/repository2/02 to old ns
http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/repository2/03 to old ns
http://schemas.android.com/sdk/android/repo/repository2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/sys-img2/03 to old ns
http://schemas.android.com/sdk/android/repo/sys-img2/01
Warning: Mapping new ns
http://schemas.android.com/sdk/android/repo/sys-img2/02 to old ns
http://schemas.android.com/sdk/android/repo/sys-img2/01
<=============> 100% CONFIGURING [10m 19s]

The Kotlin Gradle plugin was loaded multiple times in different
subprojects, which is not supported and may break the build.
This might happen in subprojects that apply the Kotlin plugins with the
Gradle 'plugins { ... }' DSL if they specify explicit versions, even if the
versions are eq
ual.
Please add the Kotlin plugin to the common parent project or the root
project, then remove the versions in the subprojects.
If the parent project does not need the plugin, add 'apply false' to the
plugin line.
See:
https://docs.gradle.org/current/userguide/plugins.html#sec:subprojects_plugins_dsl
The Kotlin plugin was loaded in the following projects:
':react-native-gesture-handler', ':react-native-screens'

Task :expo-constants:createDebugExpoConfig
Execution optimizations have been disabled for task
':expo-constants:createDebugExpoConfig' to ensure correctness due to the
following reasons:

Gradle detected a problem with the following location:
'C:\Users\user\Desktop\mec\allfiles\FindMechanic\android'. Reason: Task
':expo-constants:createDebugExpo
Config' uses this output of task ':app:compileDebugAidl' without declaring
an explicit or implicit dependency. This can lead to incorrect results
being produced, d
epending on what order the tasks are executed. Please refer to
https://docs.gradle.org/7.6/userguide/validation_problems.html#implicit_dependency
for more details
about this problem.
Gradle detected a problem with the following location:
'C:\Users\user\Desktop\mec\allfiles\FindMechanic\android'. Reason: Task
':expo-constants:createDebugExpo
Config' uses this output of task ':app:compileDebugRenderscript' without
declaring an explicit or implicit dependency. This can lead to incorrect
results being pro
duced, depending on what order the tasks are executed. Please refer to
https://docs.gradle.org/7.6/userguide/validation_problems.html#implicit_dependency
for more
details about this problem.
Gradle detected a problem with the following location:
'C:\Users\user\Desktop\mec\allfiles\FindMechanic\android'. Reason: Task
':expo-constants:createDebugExpo
Config' uses this output of task ':app:generateDebugBuildConfig' without
declaring an explicit or implicit dependency. This can lead to incorrect
results being pro
duced, depending on what order the tasks are executed. Please refer to
https://docs.gradle.org/7.6/userguide/validation_problems.html#implicit_dependency
for more
details about this problem.
Gradle detected a problem with the following location:
'C:\Users\user\Desktop\mec\allfiles\FindMechanic\android'. Reason: Task
':expo-constants:createDebugExpo
Config' uses this output of task ':app:checkDebugAarMetadata' without
declaring an explicit or implicit dependency. This can lead to incorrect
results being produc
ed, depending on what order the tasks are executed. Please refer to
https://docs.gradle.org/7.6/userguide/validation_problems.html#implicit_dependency
for more det
ails about this problem.
Gradle detected a problem with the following location:
'C:\Users\user\Desktop\mec\allfiles\FindMechanic\android'. Reason: Task
':expo-constants:createDebugExpo
Config' uses this output of task ':app:javaPreCompileDebug' without
declaring an explicit or implicit dependency. This can lead to incorrect
results being produced
, depending on what order the tasks are executed. Please refer to
https://docs.gradle.org/7.6/userguide/validation_problems.html#implicit_dependency
for more detai
ls about this problem.
Gradle detected a problem with the following location:
'C:\Users\user\Desktop\mec\allfiles\FindMechanic\android'. Reason: Task
':expo-constants:createDebugExpo
Config' uses this output of task ':app:mergeDebugShaders' without declaring
an explicit or implicit dependency. This can lead to incorrect results
being produced,
depending on what order the tasks are executed. Please refer to
https://docs.gradle.org/7.6/userguide/validation_problems.html#implicit_dependency
for more details
about this problem.
Gradle detected a problem with the following location:
'C:\Users\user\Desktop\mec\allfiles\FindMechanic\android'. Reason: Task
':expo-constants:createDebugExpo
Config' uses this output of task ':app:compileDebugShaders' without
declaring an explicit or implicit dependency. This can lead to incorrect
results being produced
, depending on what order the tasks are executed. Please refer to
https://docs.gradle.org/7.6/userguide/validation_problems.html#implicit_dependency
for more detai
ls about this problem.
@.***\config-plugins\build\plugins\withStaticPlugin.js:149
throw error;
^

PluginError: Failed to resolve plugin for module "expo-build-properties"
relative to "C:\Users\user\Desktop\mec\allfiles\FindMechanic"
at resolvePluginForModule
@.\config-plugins\build\utils\plugin-resolver.js:98:11)
at resolveConfigPluginFunctionWithInfo
@.\config-plugins\build\utils\plugin-resolver.js:188:7)
at resolveConfigPluginFunction
@.***\config-plugins\build\utils\plugin-resolver.js:179:7)
at withStaticPlugin

@.\config-plugins\build\plugins\withStaticPlugin.js:108:70)
at
@.\config-plugins\build\plugins\withPlugins.js:38:84
at Array.reduce ()
at withPlugins
@.\config-plugins\build\plugins\withPlugins.js:38:18)
at withConfigPlugins
@.\config\build\plugins\withConfigPlugins.js:45:47)
at fillAndReturnConfig
@.\config\build\Config.js:315:78)
at getConfig
@.\config\build\Config.js:382:10)
{
code: 'PLUGIN_NOT_FOUND',
cause: undefined,
isPluginError: true
}

Task :expo-constants:createDebugExpoConfig FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':expo-constants:createDebugExpoConfig'.

Process 'command 'cmd'' finished with non-zero exit value 1

Try:
Execution optimizations have been disabled for 1 invalid unit(s) of work
during this build to ensure correctness.
Please consult deprecation warnings for more details.

BUILD FAILED in 20m 24s
54 actionable tasks: 4 executed, 50 up-to-date
react-native
On Wed, Jan 11, 2023, 11:40 AM Stefan Wolf @.***> wrote:

@abs0 https://github.com/abs0 So this seems to be fixed now? Do you use
a Gradle distribution pre-built by us? I'll close the issue, please comment
if it isn't fixed yet on newer NetBSD versions.
—
Reply to this email directly, view it on GitHub
https://github.com/gradle/gradle/issues/16568#issuecomment-1378551280,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6JDRKZD7OQ56RLFKZTOYLWR2EYRANCNFSM4ZLQTZTA
.
You are receiving this because you commented.Message ID:
@.***>


[Feature Request] Add ability to sort by Last Updated

Add an option to sort the list of modules by Last Updated Name.
This would help to immediately look at the most recent updated modules.

Thanks, i'll look into that one.
Robert McIntosh @.***> escreveu no dia quarta,
1/03/2023 à(s) 21:41:

I will have to look into this. I am not sure if there is an easy way to do
this as I am not sure if this is something foundry easily tracks. At best I
would have to maintain your previosuly installed modules and the check for
new ones.
But I think this module pretty much already does that and should already
work with MM+
Quick Module Enable https://foundryvtt.com/packages/quick-module-enable/
—
Reply to this email directly, view it on GitHub
https://github.com/mouse0270/module-credits/issues/90#issuecomment-1450884971,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKZRRR5KJMY52X24LC5A4VTWZ6673ANCNFSM6AAAAAAUT3K5Y4
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
João Silva


Integrate Snapshot's daoURI with the attestation framework

Display the DAO URI of snapshot spaces, published by snapshot https://hub.snapshot.org/api/eip4824/<space_name>
on our frontend with disclaimer that the data provided is by Snapshot and NOT by DAO themselves

It seems that the 'membersURI' from the Snapshot eip4824 API just contains space members, which are not voters.
This is not what we want.

What we need to do here next is clearly describe what it means to publish daoURI data through an attestation, since Snapshot will be publishing daoURI data about DAOs through an attestation.

Created a PR on Snapshot to include voters in their membersURI
https://github.com/snapshot-labs/snapshot-hub/pull/812
Conveyed this to their team, waiting for their review and response on this

Fabien review,

In some space there can be millions of voters, I think we need to put a limit on the query otherwise it will take too long to resolve or load for an integrator

Based on this, I've added limit, pagination, and uniqueness checks for members.
I've pushed my changes fo further review.

Pushed changes, https://github.com/snapshot-labs/snapshot-hub/pull/812

Just taking a long time, ball is still in their court to review Rashmi's PR.

This was combined with #239 , will close for now.