secret-distribute-generic does not support hello world model

It seems there are a few different things that are coming up. The full secretized hello world model yields:
INFO: Running command line: bazel-bin/tools/heir-opt --secret-distribute-generic /usr/local/google/home/asraa/git/heir/tests/secret/hello_world.mlir
heir-opt: external/llvm-project/mlir/lib/IR/Block.cpp:188: void mlir::Block::eraseArgument(unsigned int): Assertion `index < arguments.size()' failed.

A shorter model
func.func @affine_for(%arg0: !secret.secret<memref<1x80xi8>>) -> !secret.secret<memref<1x3x2x1xi8>> {
  %0 = secret.generic ins(%arg0 : !secret.secret<memref<1x80xi8>>) {
  ^bb0(%arg1: memref<1x80xi8>):
    %c-128_i8 = arith.constant -128 : i8
    %c0 = arith.constant 0 : index
    %alloc = memref.alloc() {alignment = 64 : i64} : memref<1x3x2x1xi8>
    affine.for %arg2 = 0 to 3 {
      affine.for %arg3 = 0 to 2 {
        affine.store %c-128_i8, %alloc[%c0, %arg2, %arg3, %c0] : memref<1x3x2x1xi8>
      }
    }
    secret.yield %alloc : memref<1x3x2x1xi8>
  } -> !secret.secret<memref<1x3x2x1xi8>>
  return %0 : !secret.secret<memref<1x3x2x1xi8>>
}

brings:
error: type of return operand 0 ('memref<1x3x2x1xi8>') doesn't match function result type ('!secret.secret<memref<1x3x2x1xi8>>') in function @affine_for
  return %0 : !secret.secret<memref<1x3x2x1xi8>>
  ^
/usr/local/google/home/asraa/git/heir/tests/secret/test.mlir:14:3: note: see current operation: "func.return"(%2) : (memref<1x3x2x1xi8>) -> ()

which may have something to do with the memref allocation inside the secret body.

I think this is a valid bug, but also I think you would want to run this pass with --distribute-through=affine.for to ensure the loop bodies are maintained as secret.

These are error messages with that option, it seems.

To be honest, I think the core reason is the complication of allocating a memref inside of the secret.generic - this needs to happen in hello world models (the returned value is a new memref of a different shape), and so somehow this allocated memref must be hoisted outside.
Right now, the memref allocation is preventing the affine.for for being the "first op" to split around.

Ah yes, this was filed before: https://github.com/google/heir/issues/306
I think there is still the non-distribute-through issue, but for now I'll close until we reach that case.

I will add this as a test case to #306 because even after I finished implementing it, this still fails (though not with a segfault)


formatter is broken after v1.1.0

hi @kkiyama117 the formatter is broken after latest changes

@GopherJ  Sorry. It works in my env but revert npm's one until I check what's happening.

@GopherJ Now I've deleted 1.2.x from npmjs. But one that uses same versions of each dependencies causes formatter not found error in my new test environment, so I need to rewrite almost all of this plugin to resolve this issue and update dependencies.

@GopherJ
Thanks to you, I managed to update to the new one. Now that the latest one can format files without throwing errors, please update to the new one.
This problem is caused by node-fetch, but I can't find what was dropping the process when using v3 of node-fetch.


Update branding to 3.0.1

aspnet/AspNetCore-Internal#3153

Slightly unrelated, what is going to happen to branch release/3.0.0-preview9?

what is going to happen to branch release/3.0.0-preview9?

I may get to this cleanup tonight 😃


Inconsistent directory structure for releases

Describe the bug
The Linux and Windows releases consist of an archive that contains the kit, LICENSE and README.md files. For MacOS, the archive has an extra directory (reflecting the platform name).
e.g. extracting the linux tarball:
.
├── LICENSE
├── README.md
├── kit
└── kitops-linux-arm64.tar.gz

vs. extracting the macos zip file:
 .
├── kitops-darwin-arm64
│   ├── LICENSE
│   ├── README.md
│   └── kit
└── kitops-darwin-arm64.zip

To Reproduce
Extract releases from release page
Version
Latest
Additional context
I haven't checked directly, but I suspect this issue will prevent the gh-kit-setup action from running on macos runners, since the path to the kit binary will be different.

Closed by https://github.com/jozu-ai/kitops/pull/289


Master branch doesn't compile

Newly cloned repo, running make against the master branch, I get:
if [ -d build ]; then rm -r build; fi;
GOOS=linux GOARCH=amd64 go build -o build/linux-amd64/bin/main -ldflags="-X github.com/ONSdigital/rm-survey-service/models.branch=master -X github.com/ONSdigital/rm-survey-service/models.built=2018-08-17T16:00:39Z -X github.com/ONSdigital/rm-survey-service/models.commit=e0cabb0f6e25e6f7cc7b32a25d50ba6be7fa619f -X github.com/ONSdigital/rm-survey-service/models.origin=git@github.com:ONSdigital/rm-survey-service.git -X github.com/ONSdigital/rm-survey-service/models.version=10.48.2" main.go
main.go:18:2: case-insensitive import collision: "github.com/onsdigital/rm-survey-service/vendor/github.com/gorilla/mux" and "github.com/ONSdigital/rm-survey-service/vendor/github.com/gorilla/mux"
vendor/go.uber.org/zap/level.go:24:2: case-insensitive import collision: "github.com/onsdigital/rm-survey-service/vendor/go.uber.org/atomic" and "github.com/ONSdigital/rm-survey-service/vendor/go.uber.org/atomic"
vendor/go.uber.org/zap/sugar.go:28:2: case-insensitive import collision: "github.com/onsdigital/rm-survey-service/vendor/go.uber.org/multierr" and "github.com/ONSdigital/rm-survey-service/vendor/go.uber.org/multierr"
main.go:13:2: case-insensitive import collision: "github.com/onsdigital/rm-survey-service/vendor/go.uber.org/zap" and "github.com/ONSdigital/rm-survey-service/vendor/go.uber.org/zap"
vendor/go.uber.org/zap/internal/bufferpool/bufferpool.go:25:8: case-insensitive import collision: "github.com/onsdigital/rm-survey-service/vendor/go.uber.org/zap/buffer" and "github.com/ONSdigital/rm-survey-service/vendor/go.uber.org/zap/buffer"
vendor/go.uber.org/zap/stacktrace.go:28:2: case-insensitive import collision: "github.com/onsdigital/rm-survey-service/vendor/go.uber.org/zap/internal/bufferpool" and "github.com/ONSdigital/rm-survey-service/vendor/go.uber.org/zap/internal/bufferpool"
vendor/go.uber.org/zap/zapcore/level_strings.go:23:8: case-insensitive import collision: "github.com/onsdigital/rm-survey-service/vendor/go.uber.org/zap/internal/color" and "github.com/ONSdigital/rm-survey-service/vendor/go.uber.org/zap/internal/color"
vendor/go.uber.org/zap/zapcore/entry.go:30:2: case-insensitive import collision: "github.com/onsdigital/rm-survey-service/vendor/go.uber.org/zap/internal/exit" and "github.com/ONSdigital/rm-survey-service/vendor/go.uber.org/zap/internal/exit"
vendor/go.uber.org/zap/array.go:26:2: case-insensitive import collision: "github.com/onsdigital/rm-survey-service/vendor/go.uber.org/zap/zapcore" and "github.com/ONSdigital/rm-survey-service/vendor/go.uber.org/zap/zapcore"
make: *** [build] Error 1

at a quick glance it looks like you've checked out this project under $GOPATH/onsdigital/ which will cause this problem, these paths case sensitive so you need to make sure the projects are checkout out under $GOPATH/ONSdigital.

Ah, that explains it. Thanks David. When I originally created the Survey service I kept the path all lowercase to avoid any ambiguity.
I can confirm that it compiles OK using ONSdigital as the path.


hi again

sorry for the big QA push here xD
you accidentally introduced a bug for linux users. on install i get
      FileNotFoundError: [Errno 2] No such file or directory: 'README.md'
just need to rename readme.md to README.md :)
thanks

i made a PR 🚀🚀🚀🚀🚀🚀

How the heck did that happen?  Ugh... I hate macOS's lack of case sensitivity.
Your pull request has been accepted and merged. Thanks for the contribution :)

Congrats on being the first contributor to durdraw.
Thanks for all the testing. It's very helpful!

Congrats on being the first contributor to durdraw.
Thanks for all the testing. It's very helpful!

lol ya i was pretty hyped at the idea of getting my name on the board. i wouldnt have blamed you for rejecting the pr and fixing yourself. hopefully no one looks deeper into my contributions xD xD
one change i do want to implement is a config file (check if ~/.durdraw.conf exists or smth) to customize the symbols bar or maybe add some hotkeys for my favorite symbols.


the point range and voxel size of the custom data

hi, Thanks for your nice work!
I want to train with my own data on the CenterPoint-KITTI. I change the point range size :[-140.8,-80,-3,140.8,80,1] and the voxel size:[0.1,0.05,0.5] to match my data range.
But when I started training, I found that the loss of the model could not drop, and no results could be detected. I would like to ask if you want to modify the point cloud scope to adapt to your own data, which content should be modified? My most sincere thanks in advance !!
I am looking forward to your reply, which is very important to me. Thank you!

replied in the other repo


Fixed assertionComparision failure by resolving xml path for 'name'

Setup:
Java version: openjdk <IP_ADDRESS>
Maven version: Apache Maven 3.6.3
Description of PR
The following tests can fail due to flakiness while comparing the contents of the generated XML response.
org.apache.hadoop.mapreduce.v2.app.webapp.TestAMWebServicesJobs#testJobIdXML
org.apache.hadoop.mapreduce.v2.app.webapp.TestAMWebServicesJobs#testJobsXML
The test attempts to send a HTTP GET request to a specific URL and expects a response in XML format. However, XML response order is not necessarily guaranteed. The contents of the XML and the tags are compared with Job contents from appContext based on job Id in verifyAMJobXML.
When comparing the the XML contents,  The <name> tag occurs in multiple places inside  field. However, the root element within  is not always compared due to non-deterministic order.
When the name tag is being compared, the test utilizes WebServicesTestUtils.java getXmlString method for retrieving the name from the XML content. However, It always takes the first  tag irrespective of whether it is nested or in root which causes the test to fail and become flaky.
https://github.com/kavvya97/hadoop/blob/9c621fcea72a988c930ef614a7c22de00d0c7d21/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/test/java/org/apache/hadoop/yarn/webapp/WebServicesTestUtils.java#L78-L82
Since the XML contents are not ordered, The following errors occur
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.377 s <<< FAILURE! - in org.apache.hadoop.mapreduce.v2.app.webapp.TestAMWebServicesJobs
[ERROR] testJobIdXML(org.apache.hadoop.mapreduce.v2.app.webapp.TestAMWebServicesJobs)  Time elapsed: 8.361 s  <<< FAILURE!
java.lang.AssertionError:
[name]
Expecting:
 "mapreduce.job.acl-view-job"
to match pattern:
 "RandomWriter"

Steps to reproduce

git clone https://github.com/apache/hadoop
mvn install -pl hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app -am -DskipTests
Run the tests
mvn -pl hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app test -Dtests=org.apache.hadoop.mapreduce.v2.app.webapp.TestAMWebServicesJobs#testJobIdXML
Run the test with the Nondex tool and observe the test results
mvn -pl hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-app  edu.illinois:nondex-maven-plugin:2.1.1:nondex -Dtest=org.apache.hadoop.mapreduce.v2.app.webapp.TestAMWebServicesJobs#testJobsIdXML

Test Fails when Running Nondex in ONE mode (Assumes deterministic implementation of code but shuffled once different from underlying implementation) -DnondexMode=ONE  & FULL Mode  -DnondexMode=FULL (shuffles differently for each call)

Root cause:
Since WebServicesTestUtils.java getXmlString compares the first  tag only which might not necessary be the root  tag, The Fix uses Xpath to resolve the conflicts by identify the root  tag. Thus the test passes since the root tag is always retrieved irrespective of xml order.
How was this patch tested?
The fix was tested by adding a suitable fix and running the Nondex plugin again and ensuring that all the tests pass in FULL Mode and ONE Mode of the Nondex runs.

Code changes are minimal and the Root cause analysis is concise. I am unaware of whether hadoop's PR template requires the developer to mention the list of modules that have been imported.
If so, you can list out the XPath modules you have imported. Otherwise, the fix looks good.

LGTM

Code changes are minimal and the Root cause analysis is concise. I am unaware of whether hadoop's PR template requires the developer to mention the list of modules that have been imported.
If so, you can list out the XPath modules you have imported. Otherwise, the fix looks good.

I have followed the hadoop PR pattern only. It does not mention the list of modules to be imported in the PR description


[bug]: error in lnrpc

Background
lnrpc fails to compile.
Your environment
System Details Report

Report details

Date generated:                              2023-12-30 09:30:17

Hardware Information:

Hardware Model:                              ASUSTeK COMPUTER INC. ZenBook UX462DA
Memory:                                      12.0 GiB
Processor:                                   AMD Ryzen™ 7 3700U with Radeon™ Vega Mobile Gfx × 8
Graphics:                                    AMD Radeon™ Vega 10 Graphics
Disk Capacity:                               (null)

Software Information:

Firmware Version:                            UX462DA.307
OS Name:                                     Fedora Linux 39 (Workstation Edition)
OS Build:                                    (null)
OS Type:                                     64-bit
GNOME Version:                               45.2
Windowing System:                            Wayland
Kernel Version:                              Linux 6.6.8-200.fc39.x86_64

Editor / Go

go version : go1.21.5 linux/amd64
https://flathub.org/apps/com.visualstudio.code

Steps to reproduce
Add the latest version of lnrpc and trying to run a test.
Expected behaviour
The code should compile.
Actual behaviour
Running tool: /usr/lib/sdk/golang/bin/go test -timeout 30s -run ^TestMint$ lsat

# github.com/lightningnetwork/lnd/lnrpc
/home/snakedye/.local/go/pkg/mod/github.com/lightningnetwork/lnd@v0.17.3-beta.rc1/lnrpc/rpc_utils.go:32:3: unknown field UseHexForBytes in struct literal of type protojson.MarshalOptions
/home/snakedye/.local/go/pkg/mod/github.com/lightningnetwork/lnd@v0.17.3-beta.rc1/lnrpc/rpc_utils.go:40:3: unknown field UseHexForBytes in struct literal of type protojson.UnmarshalOptions

Do you try to include lnrpc in your own project? If so, you would need to add replace google.golang.org/protobuf => github.com/lightninglabs/protobuf-go-hex-display v1.30.0-hex-display to your go.mod (see lnd's go.mod file for an explanation).

Yes, the replace directive mentioned by @bitromortac should solve this problem. Unfortunately there isn't an easier way to allow us to add some features to the protobuf library without also needing this replace directive.


image_picker error:Permission Denial

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, v1.2.1, on Microsoft Windows [Version 10.0.17763.379], locale zh-CN)
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[!] Android Studio (version 3.3)
X Flutter plugin not installed; this adds Flutter specific functionality.
X Dart plugin not installed; this adds Dart specific functionality.
[√] VS Code (version 1.32.3)
[√] Connected device (1 available)
PlatformException (PlatformException(error, Permission Denial: starting Intent { act=android.media.action.IMAGE_CAPTURE flg=0x3 cmp=com.android.camera2/com.android.camera.CaptureActivity clip={text/uri-list U:content://com.example.st.flutter.image_provider/external_files/Android/data/com.example.st/files/Pictures/b213cf0a-aabb-45a5-9f36-bbc61deac3547272842760043634351.jpg} (has extras) } from ProcessRecord{fc5f102 8235:com.example.sht/u0a79} (pid=8235, uid=10079) with revoked permission android.permission.CAMERA, null))
image_picker: 0.5.0+6
image_picker is remove unnecessary camera permmision, if I have‘t allow app to use camera before open,it will be crash without show PermissionDialog

Same issue.
Reproduced on image_picker: 0.5.0+6
Not reproduced on image_picker: 0.5.0+3
Reproduced until the application does not access the camera.
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel master, v1.3.13-pre.10, on Microsoft Windows [Version 10.0.17763.379], locale ru-RU)
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[√] Android Studio (version 3.3)
[√] VS Code (version 1.32.2)
[√] Connected device (1 available)

• No issues found!

@pepegich @mklim Why you guys removed the camera permission? Now, how someone is supposed to take the picture from the camera without asking for permission?

@iampawan I run example from plugin on nexus 5 android 4.4.4 adn pixel 2 android 9. Crash did not occur.
check comment: https://github.com/flutter/flutter/issues/19806#issuecomment-408343729

The issue reproduces only if you specify android.permission.CAMERA in your AndroidManifest.xml or if another library (for example barcode_scaner) specify this permission.

@pepegich the example is ok,and i find the error. in another library it specify android.permission.CAMERA. thank you

@arok .thank you

@StarOfLife
Why are you close that ticket?
How you resolve that issue?
If I have application which depends on barcode_scan and image_picker packages. And barcode_scan require android.permission.CAMERA in AndroidManifest.xml, but image_picker doesn't require that permission.  What I should do?
@pepegich @mklim

@worldofsites I'm so sorry, I don't think about use both barcode_scan and image_picker

@worldofsites you need manually check/request camera permission, see this package https://pub.dartlang.org/packages/permission_handler

I solved the above issue by actually implementing the permission manually because I was also using Barcode Scan package. However, I just want to know @pepegich that having that permission for these kinds of use-cases can fix this problem. What do you say? Will it make sense? You would be knowing better 😀

@arok Thanks!

I appreciate that there is a workaround, but this seems a little odd to me.
If you do not have <uses-permission android:name="android.permission.CAMERA" /> in AndroidManifest.xml, image_picker works.
If you do have <uses-permission android:name="android.permission.CAMERA" />, then you either need to:
a. Request permission manually before calling ImagePicker.pickImage the first time
b. Use another plugin which requires camera permissions first, and then use the ImagePicker.
But if you
c. Try to use ImagePicker.pickImage without a or b, it will crash flutter.

It seems to me that changing the configuration/installation of the plugin (adding a permission request), depending on if a different plugin is using the camera, would be a little confusing.

I appreciate that there is a workaround, but this seems a little odd to me.
If you do not have <uses-permission android:name="android.permission.CAMERA" /> in AndroidManifest.xml, image_picker works.
If you do have <uses-permission android:name="android.permission.CAMERA" />, then you either need to:
a. Request permission manually before calling ImagePicker.pickImage the first time
b. Use another plugin which requires camera permissions first, and then use the ImagePicker.
But if you
c. Try to use ImagePicker.pickImage without a or b, it will crash flutter.
It seems to me that changing the configuration/installation of the plugin (adding a permission request), depending on if a different plugin is using the camera, would be a little confusing.

Yes, it worked for me. the upgrade busted up my project XD!

Unfortunately, this same error is happening to me even when I don't have the camera permission stated in AndroidManifest.xml, neither do I use camera anywhere else.
Currently I'm using version 0.5.2, Android API 28.
What might be going on?
My error:
java.lang.SecurityException: Permission Denial: starting Intent { act=android.media.action.IMAGE_CAPTURE flg=0x3 cmp=com.android.camera2/com.android.camera.CaptureActivity clip={text/uri-list U:content://my.package.name.flutter.image_provider/external_files/Android/data/my.package.name/files/Pictures/7171ae3d-ae2c-40c0-bfeb-d1aa2a613cf05402625956103201743.jpg} (has extras) } from ProcessRecord{9ff798f 9542:cz.codit.stromysvobody/u0a85} (pid=9542, uid=10085) with revoked permission android.permission.CAMERA

Even manually asking for permission did not help me (although I'm not sure I did it correctly). Downgrading to 0.5.0+3 solved the issue.

Unfortunately, this same error is happening to me even when I don't have the camera permission stated in AndroidManifest.xml, neither do I use camera anywhere else.
Currently I'm using version 0.5.2, Android API 28.
What might be going on?
My error:
java.lang.SecurityException: Permission Denial: starting Intent { act=android.media.action.IMAGE_CAPTURE flg=0x3 cmp=com.android.camera2/com.android.camera.CaptureActivity clip={text/uri-list U:content://my.package.name.flutter.image_provider/external_files/Android/data/my.package.name/files/Pictures/7171ae3d-ae2c-40c0-bfeb-d1aa2a613cf05402625956103201743.jpg} (has extras) } from ProcessRecord{9ff798f 9542:cz.codit.stromysvobody/u0a85} (pid=9542, uid=10085) with revoked permission android.permission.CAMERA

When you erased the permission stated in AndroidManifest.xml, also did you delete the
"build" generated folder? When you change the manifest, you have to also delete that folder, reset android studio or any IDE and build the project again.
Other possibility can be that the permission implementation that you did its wrong.

I actually never had the permission in AndroidManifest.xml at all and got the error. Only after checking upon this issue I tried adding it there and it has not fixed it nor change the behaviour at all.

Thanks to @arok, there is a workaround using https://pub.dartlang.org/packages/permission_handler
And here is an example on how it can be implemented
import 'package:permission_handler/permission_handler.dart';

Future<bool> checkAndRequestCameraPermissions() async {
  PermissionStatus permission =
      await PermissionHandler().checkPermissionStatus(PermissionGroup.camera);
  if (permission != PermissionStatus.granted) {
    Map<PermissionGroup, PermissionStatus> permissions =
        await PermissionHandler().requestPermissions([PermissionGroup.camera]);
    return permissions[PermissionGroup.camera] == PermissionStatus.granted;
  } else {
    return true;
  }
}

Then every call to the image picker has to be wrapped like this to prevent your app from crashing
if (await checkAndRequestCameraPermissions()) {
  File image = await ImagePicker.pickImage(source: ImageSource.camera);
  // continue with the image ...
}

But I still prefer that something like this is done within the image_picker plugin.

I fixed, https://github.com/flutter/plugins/pull/1519

Should be fixed by https://github.com/flutter/plugins/pull/1519. Closing this issue now. If any related issue has been found after applying using the newest Image_picker, please open a another issue with details.

Hello,
I am trying to publish my app, which is using SMS: ^0.2.4, on the Play Store.
In my androidManifest.xml file I have declared that my app requires three permissions:
<uses-permission android:name="android.permission.CAMERA" />
    <uses-permission android:name="android.permission.RECORD_AUDIO" />
    <uses-permission android:name="android.permission.READ_CONTACTS" />

When I upload it on the play console, it tells me that I have to declare 3 other sensitive permission:
android.permission.READ_SMS
android.permission.SEND_SMS
android.permission.RECEIVE_SMS
I think it's due to the SMS plugin, and I need it to invite other users to join my app.
I receive this mail from Google:

Could someone help me with this issue please ?

@DjivaCanessane maybe try to post an issue on the SMS plug-in github page?

I am getting this same error in iOS. I was testing and denied the permissions, and I have yet to find a way to request permission again if they do an action.
[VERBOSE-2:ui_dart_state.cc(148)] Unhandled Exception: PlatformException(photo_access_denied, The user did not allow photo access., null)
I am doing this in an iOS simulator. Do I really have to delete the app and reinstall to allow permissions?

Same issue like @tapizquent  on Android simulator and real device
var image = await ImagePicker.pickImage(source: ImageSource.gallery);
Exception has occurred. PlatformException (PlatformException(photo_access_denied, The user did not allow photo access., null))
dependencies:
flutter:
    sdk: flutter
  firebase_auth: ^0.14.0+5
  cloud_firestore: ^0.12.9+4
  http: ^0.12.0+2
  package_info: ^0.4.0+6
  image_picker: ^0.6.1+4

Not worked even if I locate this or not
<uses-permission android:name="android.permission.CAMERA" />

I seems these permissions solved my problem.
<uses-permission android:name="android.permission.MANAGE_DOCUMENTS" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
The point I haven't understand. I had been accessing device gallery without any permission before.

@kaiserleka Are you requesting permissions for those with something like permission_handler explicitly? I can't get image_picker to work on Android 10.

Hi! I have found another error when picking image from gallery or photo on API 29, it works fine on API 28 but on 29 it can not access to the file picture.
Unable to decode stream: java.io.FileNotFoundException: /storage/emulated/0/Download/descarga.jpeg: open failed: EACCES (Permission denied)

Same issue here. Do we really this permission ?
<uses-permission android:name="android.permission.MANAGE_DOCUMENTS" />

I just ran into this, I got it working by adding
    <uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
    <uses-permission android:name="android.permission.MANAGE_DOCUMENTS" />

then deleting the build folder and rebuilding the app.

@everystone Many thanks, keyword delete build folder is really helped me.

I was pointed to this page multiple times but I havent found any solution yet.
So I will state my specifications:
I have image_picker: ^0.6.2+2 Flutter 1.9.1+hotfix.6 . I am trying to do var image = await ImagePicker.pickImage(source: ImageSource.gallery);  I get error photo_access_denied, The user did not allow photo access . How do I allow photo access in android emulator?

I was getting issue because of build folder. When I run "flutter clean", issue was fixed.

I fixed this error for >= Android Q adding android:requestLegacyExternalStorage="true" to the <application> in AndroidManifest.xml.

This is actually still an ongoing problem as far as I can tell.
Using 0.6.3+4, my app requires me to use requestLegacyExternalStorage=true - even for the 'Google' Photo and Download directories in order to successfully use ImageSource.gallery as my source - on both a simulator and a Samsung S10+, both running Android 10. I thought that access was allowed to the Photo and Download directories under scoped storage? Apparently not though, as in my case (and many others it appears) Legacy External Storage is required even there. And with Android 'R' making legacy external storage requests will no longer be allowed at all, as I understand it, so the requestLegacyExternalStorage=true setting in AndroidManifest will be redundant too for future apps.
Confusing times indeed.

I had the same problem. Turned out I hadn't followed the instructions below to upgrade my pre-Flutter v1.12 project:
https://github.com/flutter/flutter/wiki/Upgrading-pre-1.12-Android-projects
After upgrading my project my problems were resolved.

for >= Android Q adding android:requestLegacyExternalStorage="true" to the <application> in AndroidManifest.xml. - authors, could you please add this information to official library documentation?

I had the same problem. Turned out I hadn't followed the instructions below to upgrade my pre-Flutter v1.12 project:
https://github.com/flutter/flutter/wiki/Upgrading-pre-1.12-Android-projects
After upgrading my project my problems were resolved.

This fixed the issue for me too. I think this is the correct solution and the only solution for supporting Android 11.

I had the same problem. Turned out I hadn't followed the instructions below to upgrade my pre-Flutter v1.12 project:
https://github.com/flutter/flutter/wiki/Upgrading-pre-1.12-Android-projects

Unfortunately this did not fix the problem for me, using v0.6.4. I still have to include android:requestLegacyExternalStorage="true" to avoid a 'permission denied' error when trying to pick an image. So I guess my app will never work in Android 11 - or I must find an alternative image picker somewhere. Failing that I'll have to stop offering the gallery as a choice to Android users. Which is mighty disappointing to say the least.

In that case I would suggest creating a new workspace and generating a
fresh project in it using 'flutter create'. Then you'd need to copy your
code over and apply any Android and iOS configurations that you've made...
such as package name, etc.
I had to resort to this once. It took a couple of hours but resolved my
issues.
On Sat, Apr 4, 2020 at 7:41 AM lunedam-git<EMAIL_ADDRESS>wrote:

I had the same problem. Turned out I hadn't followed the instructions
below to upgrade my pre-Flutter v1.12 project:
https://github.com/flutter/flutter/wiki/Upgrading-pre-1.12-Android-projects
Unfortunately this did not fix the problem for me, using v0.6.4. I
still have to include android:requestLegacyExternalStorage="true" to avoid
a 'permission denied' error when trying to pick an image. So I guess my app
will never work in Android 11 - or I must find an alternative image picker
somewhere. Failing that I'll have to stop offering the gallery as a choice
to Android users. Which is mighty disappointing to say the least.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/29422#issuecomment-609038622,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ662ABUJZZMDHXXQDXV2E3RK5BI7ANCNFSM4G6YTQKQ
.


Missing feature under versions "Ignore Crashes" operation

On HA we have a feature to ignore specific version from collecting crashes. "Ignore Crashes". this feature is missing on App Center

@moon1978 thanks for the feature request. We don't have any short term plans to build this feature but you can ignore specific crash groups from a version in App Center by selecting the crash group and marking the status as ignored:

I know that requires a bit more work than just ignoring all crashes from a specific version but I hope that helps a bit!

Hi
But on HA I have the option to ignore all crashes on specific version so crashes won’t be uploaded
Sent from my iPhone
On 3 Jun 2019, at 20:44, Winnie Li <notifications<EMAIL_ADDRESS>wrote:
@moon1978https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmoon1978&data=02|01||1d6b9f1da837470c95df08d6e84b2529|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636951806770488718&sdata=1Anctm5ruP4vz3T7ilBB55O9yTlY6HCGy76HEfnSIfA%3D&reserved=0 thanks for the feature request. We don't have any short term plans to build this feature but you can ignore specific crash groups from a version in App Center by selecting the crash group and marking the status as ignored:
[image]https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F8868628%2F58822118-9380a080-85eb-11e9-8b77-5d0641f6183b.png&data=02|01||1d6b9f1da837470c95df08d6e84b2529|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636951806770498723&sdata=F8EyFH2wBEqUkErieeVQ89KmiDNtkIYBX9PWqJjS%2F58%3D&reserved=0
I know that requires a bit more work than just ignoring all crashes from a specific version but I hope that helps a bit!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fappcenter%2Fissues%2F488%3Femail_source%3Dnotifications%26email_token%3DACVSAH6MFLBKDLG6CQQU5CLPYVKAHA5CNFSM4HQNBF42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW2E2GA%23issuecomment-498355480&data=02|01||1d6b9f1da837470c95df08d6e84b2529|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636951806770508734&sdata=y0P61mnoAjBVeX%2BU9Cd8jYVLUpIcHwDcncBWJC0UulE%3D&reserved=0, or mute the threadhttps://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACVSAH5MAFV6YVO2CO7JQF3PYVKAHANCNFSM4HQNBF4Q&data=02|01||1d6b9f1da837470c95df08d6e84b2529|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636951806770518739&sdata=99kaotTaL70f6goWavLI8AgpP14J0yHH3Ce5nOqeQlk%3D&reserved=0.

Yep, we recognize this is as a feature gap. Due to other priorities at the moment, we don't have any immediate plans to address this in the upcoming months. I'll post here when I have any updates. Thanks!


Can't use the page.find.media method to get png images. Only works with jpg extension.

So if you use the following method to reference image files {{ page.find('/images').media['logo.png'].sizes('25vw').html }} (images directory inside pages directory) twig returns nothing. However, if you rename that same file (without recreating the image, simply renaming it) to have a .jpg extension, twig returns the correct img tag and src attribute. Like this: {{ page.find('/images').media['logo.jpg'].sizes('25vw').html }} it works. Once again, to clarify, simply right click on the image and select "rename" and then change the .png to .jpg. So it's still a png but grav returns it because it has a .jpg extension. Even though it isn't a jpg.

I don't think it's the page.find() method or the .media() bit.. I just tested and worked fine:

Hmmm I think it was a cache thing. About an hour ago I had to clear the cache and then I just tried the image thing again and it worked with the png. So I guess we can close this issue. False alarm on my part.


⚠ Bofrost.de has degraded performance

In ce65164, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1242 ms

Resolved: Bofrost.de performance has improved in 09559c0 after 1 hour, 16 minutes.


Debug using Hotswap should be shown in services menu

This is currently missing the HotswapAgent option

Not sure how to put it there. Those services are actually run configurations:

When you run Debug with HotSwap you actually reuse existing run configuration with just different "runner":

Or maybe you mean the context menu only...


Precaution Dose

Pls add precaution dose

Thanks for asking this. I've added support for this.

Thanks for asking this. I've added support for this.

Thanks a lot


No way to send a request without the 'language' header

Just spent a while wondering why my API server was rejecting my requests, and it turns out it's because there's an unexpected header, 'language' being sent with the request.
This bit of code makes it impossible to not send the header:
if (!headers.containsKey('language')) {
      headers['language'] = Intl.defaultLocale ?? 'en_US';
    }

Of course I can set my server's CORS policy to accept this header, but that requires that I modify the CORS package I'm using for my backend, so It's kind of a pain. Moreover though, this could be breaking for people sending requests to APIs/services that they don't have control over.
(Also, I might be wrong but isn't the name of this header 'accept-language'?)

You are correct, it should have been accept-language.  Thanks for pointing that out.  :)
I fixed the name, and updated so you can unset any default header by setting it to empty.  Just update to:
rest_client: ^2.1.1


Fix/binance perpetual order fill amount bug

Before submitting this PR, please make sure:

[x] Your code builds clean without any errors or warnings
[x] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
Fix to the issue https://github.com/hummingbot/hummingbot/issues/5170 by correctly parsing the trade fill event from the connector and reading the fill amount for the particular trade instead of the accumulated quantity field.
Tests performed by the developer:
All unit tests passing in green
Test summary:

Install feature branch and test the connector using perpetual market-making strategy.
Leave the bot running to capture a partial fill both for open and close positions
Checked the total order amount of the partially filled orders by running the history verbose command and confirmed that the total amount is equal to the specified order amount value.
Leave the bot running for more than 24 hours and inspect the filled record after, 4 partial fill took place, and confirm that the total order amount is equal to the specified value in the order_amount parameter.
Review the logs and confirmed that

When a partial fill takes place, then the remaining get filled right after, the total amount is correct
When partial fill takes place then the remaining gets canceled, the next order created will have a size equal to the remaining unfilled order to make sure that the total amount is still correct.

Tips for QA testing:
To validate the fix is working it is important to check the total amount filled for an order when there is at least one partial fill.
This PR comes from https://github.com/CoinAlpha/hummingbot/pull/135

Created proposal: https://snapshot.org/#/hbot-prp.eth/proposal/0xe84f7fb19be1708b1e99f3ae4ffe0787aa6bb322a42a8a1b6c15b75cccb47fd3


[feaLib] report position in code for error

When the few code contains a problem, feaLib should give an error message with line number where to find the offending code. Now it only gives a backtrace.

well, the feaLib parser and builder do raise a custom FeatureLibError which should always carry with it the location (filename, line number, column) where it is raised.
If you are seeing a traceback without the location then it looks like a bug or an oversight.
What is the actual error, or the data that triggers it?

I got this:
'''
Traceback (most recent call last):
File "/usr/local/bin/fonttools", line 9, in
load_entry_point('fonttools==3.9.2.dev0', 'console_scripts', 'fonttools')()
File "/Users/georg/Programmierung/Stuff/fonttools-Main/Lib/fontTools/main.py", line 29, in main
runpy.run_module(mod, run_name='main')
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 180, in run_module
fname, loader, pkg_name)
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in run_code
exec code in run_globals
File "/Users/georg/Programmierung/Stuff/fonttools-Main/Lib/fontTools/feaLib/main.py", line 42, in
sys.exit(main())
File "/Users/georg/Programmierung/Stuff/fonttools-Main/Lib/fontTools/feaLib/main.py", line 37, in main
addOpenTypeFeatures(font, options.input_fea)
File "/Users/georg/Programmierung/Stuff/fonttools-Main/Lib/fontTools/feaLib/builder.py", line 16, in addOpenTypeFeatures
builder.build()
File "/Users/georg/Programmierung/Stuff/fonttools-Main/Lib/fontTools/feaLib/builder.py", line 80, in build
self.build_feature_aalt()
File "/Users/georg/Programmierung/Stuff/fonttools-Main/Lib/fontTools/feaLib/builder.py", line 165, in build_feature_aalt_
for glyph, repl in alternates.items()
File "/Users/georg/Programmierung/Stuff/fonttools-Main/Lib/fontTools/feaLib/builder.py", line 166, in
if len(repl) > 1}
File "/Users/georg/Programmierung/Stuff/fonttools-Main/Lib/fontTools/ttLib/init.py", line 628, in getGlyphID
glyphID = d[glyphName]
KeyError: u'foursuperior'
'''

I see. In this case the aalt feature is being generated based on substitutions defined in other lookups, so it's not already in the features.fea and as such there's no line number to reference (yet).
I agree that the error message could be improved. Here we could intercept the KeyError and reraise a FeatureLibError saying that aalt feature failed to be generated because the font is missing u'foursuperior, or something like that.

Or generate the aalt feature at the end and hope that the other lookups raise the proper error?


feat: add CAIP2 and unit tests

@sdmg15 - wow thanks for the quick turnaround!!!
Looks like the linter is failing.  can you take a look please?

@0xean I think it should pass now :)

Alright @0xean in the meantime waiting on to tackle the next bounty 😄

@sdmg15 - awesome, working on getting more posted!
If interested please join us in discord - https://discord.gg/shapeshift
I post them there as soon as I get them completed and we also are welcoming to ideas from contributors if there are things you would like to suggest we bounty.

thanks for the contribution @sdmg15


Need a best practices document

The list of linter rules should generally come from this document (but the doc could be a superset of the linter rules).

Some suggested guidelines:

Don't use "name" in a symbolic name, e.g. don't do this:

resource cosmosAccountName 'Microsoft.DocumentDB/databaseAccounts@2021-04-15' = {
...

Don't distinguish variables/parameters by prefix/suffix, e.g. don't do this:
param paramLocation = resourceGroup().location
var cosmosAccountName_var = toLower(applicationName)

Here's a best practices doc that @johndowns pulled together.

https://github.com/Azure/template-analyzer: I know these are other types of best practices (more related to the configuration of the resources themselves and not Bicep in general), but is there any collaborative effort on this between Bicep team and the ppl behind the template-analyzer? @MarcusFelling  Or is this something completely out of the scope for linter functionality in Bicep?

We are working closely with the BPA team to make sure any BPA rule that applies to Bicep will be evaluated by the bicep linter. Don't have an ETA for "full alignment", but that is definitely our north star.

Closing. Best practice docs can be found here:

https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/best-practices
https://docs.microsoft.com/en-us/learn/modules/structure-bicep-code-collaboration/


Support for testing React components that use variation() function

Is your feature request related to a problem? Please describe.
We can't use the useFlags() hook as it incorrectly reports that flags are evaluated when they are fetched via allFlags(), even though they are not evaluated at that time. This is very confusing for our users of the Launch Darkly dashboard as the dashboard incorrectly states that old flags that are no longer even in our codebase were evaluated "2 mins ago" (for example).
The advice from your support team is to initialise with sendEventsOnlyForVariation set to true and always use ldClient.variation() to evaluate flags in components instead of useFlags().
However, it looks like this library doesn't support testing components that use ldClient.variation() yet.
Describe the solution you'd like
Add support so that it's possible to test components that use ldClient.variation() instead of useFlags().

Hi @yusinto. Thanks for your response but that's not going to solve my problem. I don't want to test that the variation() function has been called. I want to test the functionality of the component based on the flag being enabled using the variation() function.
In other words, how do I test this component using your library?
const Button: FunctionComponent = ({ children }) => {
  const ldClient = useLDClient() as LDClient

  return ldClient.variation('dev-test-flag') ? (
    <button data-testid="test-button">{children}</button>
  ) : (
    <>button disabled</>
  )
}

The functions of ldClientMock object are jest mocks as well. You can use the standard mock* functions to mock variation:
import React from 'react'
import { render, fireEvent, screen } from '@testing-library/react'
import { ldClientMock, resetLDMocks } from 'jest-launchdarkly-mock'

// ... other boilerplate test suite code

  it('should render button', () => {
    // mock the variation function to return true
    ldClientMock.variation.mockReturnValue(true)

    render(<Button />)

    expect(ldClientMock.variation).toBeCalledWith('dev-test-flag')
    expect(screen.getByTestId('test-button')).toBeDefined()
  })

Ah okay, thanks for your help @yusinto. It's not what I was hoping for, but I think that will be enough to get our tests working for now, thanks.
I think the main reason I find it confusing is that I'm being told the variation() function is the idiomatic way to evaluate flags with Launch Darkly, yet all the examples (including the one in this library) focus heavily on useFlags(). The use of variation() is curiously missing from all docs and examples, as if it's just a minor convenience function that won't be of interest to most users.
Is the example in this library going to be changed to use variation() at some point or am I still missing something? I can't think of a reason why anyone would prefer useFlags() over the variation() function as it causes the "Evaluated XX mins ago" analytics on the dashboard to be incorrect (as well as making all information in the insights tab incorrect) because the time it shows is actually when all the flags were fetched during initialisation which is very misleadingly and confusing for our users of the dashboard.
I know what I'm referring to isn't specific to this library but any advice you have on this would be extremely helpful as I still feel like I'm using LD incorrectly. Even just adding another example to this library (and the React SDK one) that uses variation() in the Button component would go a long way to providing some reassurance this is the recommended approach for users who care about insights/analytics.

Hi @pdrummond apologies for the slow response. The way the React SDK is initialized by default is to request all flags via the ldClient.allFlags() function which will cause all flags to be "Evaluated xxx mins ago". If you only want to listen to a specific set of flags, not all flags, you can initialize the React SDK with the flags config option. You can also read about it more on our docs page.
Here's an example of how you can initialize the React SDK with only the flags which are of interest:
  const LDProvider = await asyncWithLDProvider({
    clientSideID: 'your-client-side-id',
    flags: {
      'my-bool-flag': true,
      'my-int-flag': 5,
    },
  });

For more on the

Hi @yusinto. Thanks for your response but that won't work for us. If I am reading the LD React SDK code correctly, your example above does indeed call variation under the hood instead of allFlags but it's still evaluating the flags at initialisation time rather than when the flag is actually evaluated and we still get incorrect analytics because of that. Also, this approach means every time we add a flag we would need to keep a separate list of flags updated which isn't too much effort but still feels like an overhead and a completely unnecessary one at that.
It's okay though - we have solved the problem by implementing our own custom useFlags hook that simply invokes variation at the time of flag evaluation. I will add an issue to the LD React SDK repo to suggest this is should be the default for your useFlags hook as well and once you provide that we'll retire our custom hook, but until then it's working well for us.
Also - just some feedback for you if it's useful - we couldn't get this library working with create-react-app so we've implemented a custom mocking solution as well.

Thanks @pdrummond. The React SDK team will be looking at that issue. In the meantime, are you able to open a separate issue for the create-react-app problem please? So we can investigate and correct it for the benefit of others. Thank you.

Hey @yusinto my team is in a similar situation where we prefer using .variation() in a custom hook over useFlags() because it provides us with better flag name safety through use of enums and better analytics.
This package would be more helpful to us if ldClientMock.variation() had mocked return values based on the flag set passed to mockFlags(). What do you think of this? Is this a contribution you would accept?


not support no std?

error[E0405]: cannot find trait Sync in this scope
--> /home/esp/.cargo/registry/src/index.crates.io-6f17d22bba150
01f/thiserror-1.0.61/src/aserror.rs:50:40
|
50 | ...ror + Send + Sync + UnwindSafe + 'a {}
|                 ^^^^ not found in this scope
|
help: consider importing this trait
|
1  + use core::marker::Sync;

It is obvious from the source that it is not supported.
It is a candidate for the work item but I have not worked on.

Hi! 😊 @cat-in-136
I'd need this feature for a project and would be open to help with no_std support in a PR.
Have you had a look already to know what needs to be done to get this working without the standard library? If yes, please let me know.
Kind greetings,
Mo

As I mentioned in June, I haven't started work yet, so I haven't done any research on this crate-specific topic.
This is a common no_std story that you all know, where the no_std support tasks can be divided into two phases: the case with alloc and the case without alloc.
In the case with alloc, it would be a simple matter to remove the parts depending on the std library, and the logic would not need to be changed. But the same work would be required for the dependent crates. For example, since thiserror crate does not support no_std, it would be necessary to switch to a no_std-compatible library such as snafu.
In the case without alloc, in addition, it is necessary to introduce new APIs for using only pre-allocated memory, and disabling existing APIs for dynamic memory allocation without alloc.

I started working on no_std.
For now, the API for allocated memory has not yet been added; meaning alloc is mandatory. That is, there are currently no particular benefits to using no_std.


Update monitors.md

The user agent is written above the sentence but not below the sentence

Thanks for the callout, @erictung1999.


Backport: Removing hidden/reserved roles added via rolesmapping

Earlier the InternalUsers API was filtering out all hidden/reserved roles. We will just restrict it to hidden/reserved roles associated via rolesmapping. This will ensure behaviour of rolesmapping and internalusers API is the same.
(cherry picked from commit 6c1f002b25d77f2636c86b419dc4be7a00f889fe)
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

We should not allow non-superadmin to update user or rolemapping if
(1) role is hidden
(2) if role mapping is hidden
(3) if role mapping is reserved
#2 and #3 are covered.
Any thoughts on #1 --> If role is hidden, that means superadmin doesn't want anyone to see that role and hence we should not allow anyone to update role-mapping or role-mapping field (for a hidden role)

Added #1 as part of the following issue https://github.com/opendistro-for-elasticsearch/security/issues/590. I will need to update both the rolesmapping and internalusers API to accomodate this use case.

I have addressed comments for this review as part of https://github.com/opendistro-for-elasticsearch/security/pull/614 (@hardik-k-shah). Will close this PR and address comments in #614 before backporting.


[PDI-7090] Only one user can make changes in a repository at any time. (Database Repository is locked)

When using MySQL as repository database every SELECT statement has to be followed by a COMMIT to avoid locking issues in parallel sessions. For this reason the current code contains the method closeReadTransaction() which also needs to be called after SELECTs in getNextTableID(), getIDs() and getStrings().
The patch fixes the issue described in  [PDI-7090].

Hello, This is an automated comment from our build system. Since this pull request originated from a user  not in the Pentaho organization, we will not proceed  with automatic validation of the pull request.  However, rest assured that it will be reviewed manually as soon  as we get the chance. Thanks for your contribution!

Thanks for the contribution! PR was reviewed and merged.


Enhance EventEmitterStream with options

Added maxListeners option which is passed on to EventEmitter. This is used in order to warn when a threshold of litterers has been exceeded, but it is not a hard limit, it just sends a warning to the stderr.
If no value is provided we set it to 0 which represents infinity.
Also exposed a way to capture errors, with the default being sent to console.error still.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (908d5f0) 98.86% compared to head (c063694) 98.78%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #665      +/-   ##
==========================================
- Coverage   98.86%   98.78%   -0.08%
==========================================
  Files          75       75
  Lines        9656     9690      +34
  Branches     1422     1421       -1
==========================================
+ Hits         9546     9572      +26
- Misses        102      110       +8
  Partials        8        8

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Cleanup NetBeans license header for module xml.tax

Review and cleanup the license header in xml.tax
Oracle donated NetBeans to the Apache Software Foundation.
Your task now is to replace the old license header that has Oracle (and/or Sun Microsystems
and/or NetBeans) in it with the standard Apache Software Foundation license header.
For an empty file that supports headers you must add the Apache license header.
Note that you have to use the proper license header for Java, .properties or HTML files.
Look at the nearby files for templates and copy-paste the license header.
When done commit the changes with a commit message that starts with first line
"[NETBEANS-54] Module Review " and a message body describing your review.
See a longer explanation about what we are doing here: https://cwiki.apache.org/confluence/display/NETBEANS/List+of+Modules+to+Review
Please announce in a comment when you have started work.
Files that need to be looked at in xml.tax:
xml.tax/lib/test/qa-functional/src/org/netbeans/tax/data/xstates.dtd
xml.tax/lib/test/qa-functional/src/org/netbeans/tax/io/data/dir/dir-b/level2.dtd
xml.tax/lib/test/qa-functional/src/org/netbeans/tax/io/data/dir/dir-b/level3.dtd
xml.tax/lib/test/qa-functional/src/org/netbeans/tax/io/data/dir/level1.dtd
xml.tax/lib/test/unit/src/org/netbeans/tax/dom/data/Prototype.xml

Reserved by matthiasblaesing.


DNSSEC keys

Hi there,
Im working on getting dnssec work in my homelab.
Your version of stubby has no access to create .getdns in /opt/stubby or /var/cache/stubby, therefore cant download the dnssec root keys.
workaround by setting
appdata_dir: "/tmp"
works, but is just a workaround.

Thanks for the report. Would it help if the /opt/stubby/.getdns directory was created as part of the build process in the following section? https://github.com/MatthewVance/stubby-docker/blob/1046cd96c4c7feca8c115528e7266714b508b5fc/stubby/Dockerfile#L99
Or would setting appdata_dir in the default config and point to a directory that Stubby has rights to be better?


Celo Stats inconsistent display of data / dropping validator names

Expected Behavior
Consistent validator listing showing both validator and validator group names.
Current Behavior
Validator names are consistently disappearing for a subset of the validator list on https://stats.celo.org
Bouncing proxy and/or validator appears to 'refresh' Celo stats and validator name and group reappear.
While this may appear a cosmetic issue, branding and visibility on the official Celo stat site is important and not resolving this issue unfairly affects the organisations that are consistently affected.
Some questions:

Do the validator and proxy names have to be the same when reporting to ethstats?
Do you even need to login to ethstats on the validator?
Are there any server logs on Celo stats showing dropped connections to certain validators?
What further information would you need from the validator community to pin this down?

Selected anecdotes from forum:
peterldowns: WARN [05-07|07:26:05.511] Failed to decode stats server message    err="websocket: close 1006 (abnormal closure): unexpected EOF"

There was a little talk in this channel at some point about Celo Stats and names disappearing. We have been afflicted with similar issues, and in one case the validator just fell off the board (even though all was well). One possible issue for us is that on reboots of the proxy, the enode id was changing. This certainly has an effect on the validator's ability to get blocks, but I think it was also causing issues in Celo Stats. We have stabilized our enode ids for proxies, rebooted, and the stats seem to be okay now.

BisonD:

following up on this, I'm still seeing my validator/proxy drop off the rc1 stats page from time to time. restarting my proxy seems to fix it; my proxy has a consistent enode across restarts

Another data point on this is the proxy continually says Stats login failed                       err="login timed out" even tho its reporting. Perhaps the validator is properly reporting (since data is showing up)

Cross post here. My enode id hypothesis turned out to not be a factor in Celo stats issue.  Our proxy starts up, says “Stats login failed” a number of times but then seems to start reporting correctly. All stats show up correctly for an hour or so and then they just stop.

Update for Celo stats issue. Stable enode id did not solve it. Names are cleared again from mainnet and baklava Celo stats pages. Our genesis validator no longer appears on the board

Thylacine:

WARN [04-27|09:52:09.967] Failed to decode stats server message    err="websocket: close 1006 (abnormal closure): unexpected EOF" this message on my proxy, and now my name has again disappeared from celostats. Is this related?

gunray:

WARN [04-25|15:20:45.649] Stats server pinger seems to have died

mbay2002:

We're not showing on stats.celo.org
We do have<EMAIL_ADDRESS>on both validator and proxy, account unlocked on proxy
Worked on baklava. What's the magic incantation? :woozy_face:

Wade:

Another validator found it was a problem with two differing addresses between proxy and validator<EMAIL_ADDRESS>has to be the same for both proxy and validator.
I just restarted both with this but it didnt work for me.

Thanks for raising this! We will try and get to the bottom of it

We're not showing on stats.celo.org
We do have<EMAIL_ADDRESS>on both validator and proxy, account unlocked on proxy
Worked on baklava. What's the magic incantation?

it is very important to put some name before the @ otherwise the validator will show up with empty name on celostats

WARN [04-27|09:52:09.967] Failed to decode stats server message err="websocket: close 1006 (abnormal closure): unexpected EOF" this message on my proxy, and now my name has again disappeared from celostats. Is this related?

I recently updated the websocket module inside celo blockchain. This can solve the issue but i am not sure because it cannot be reproduced locally.


Paste multiple functions

Hi,
I'm new to Python, I recently started to use spyder with Python 3.3.5 32 bit, IPython 3.2.0 at home.
I started creating a few things that work well on my computer.
But when I open the .py files at work (they use spyder with Python 3.3.3 32 bit, I don't know which IPython version but I can find it if needed), I have a problem.
At home, I can copy my whole code and paste it in the console without any problem.
At work, I can only copy one function after another, so if I have, say, 10 functions in my file, it's pretty long to do. I cannot imagine doing that with a more complicated .py file with hundred functions.
So, is there an easy way to fix this? Is it version dependent or is it just an option to change somewhere?
I noticed the console doesn't look the same at home and at work, at home it's called console 1/A and input lines start with In[1]:, In[2], etc, and at work they start with >>>

Please read this:
http://docs.spyder-ide.org/editor.html#defining-code-cells
Also, you're also using very old versions of Python and Spyder. You should update to our latest version in case you're unable to use cells.


copy fails to copy when destination is directory

shutil.copy fails to copy with the following exception

Error
Traceback (most recent call last):
File "C:\Python27\lib\unittest\case.py", line 329, in run
File "C:\work\GitHub\shellfoundry\tests\test_package_builder.py", line 32, in test_copy
File "C:\Python27\lib\shutil.py", line 119, in copy
File "C:\Python27\lib\shutil.py", line 83, in copyfile
File "C:\Python27\lib\site-packages\pyfakefs\fake_filesystem.py", line 1896, in call
File "C:\Python27\lib\site-packages\pyfakefs\fake_filesystem.py", line 1904, in _call_ver2
File "C:\Python27\lib\site-packages\pyfakefs\fake_filesystem.py", line 1971, in Call
IOError: [Errno 21] Fake file object: is a directory: u'C:\destination'

According to its documentation, if the destination is directory it should copy the file to destination.

shutil.copy(src, dst)
Copy the file src to the file or directory dst. If dst is a directory, a file with the same basename as src is created (or overwritten) in the directory specified. Permission bits are copied. src and dst are path names given as strings.

10.10. shutil — High-level file operations
Unit test to reproduce the issue:
import os
import unittest
from shutil import copy
from pyfakefs import fake_filesystem_unittest

class TestPackageBuilder(fake_filesystem_unittest.TestCase):
    def setUp(self):
        self.setUpPyfakefs()

    def test_copy(self):
        self.fs.CreateFile(u'C:\\source\\file.txt', contents='')
        os.makedirs(u'C:\destination')
        copy(u'C:\\source\\file.txt', u'C:\destination')

        self.assertFileExists(u'C:\destination\\file.txt')

    def assertFileExists(self, file_path):
        self.assertTrue(os.path.exists(file_path))

The problem is "import copy from shutil". This way, after pyfakefs replaces shutil with its own implementation, copy is still used from the system lib (as can be seen in the callstack).
Using:
import shuti
...
shutil.copy(...)

instead should fix the problem.

@mrbean-bremen thank you for your reply. It fixes the issue.


Add Swift Package Manager Support

SPM is supported for iOS since Xcode 11. Would be cool to have JOSESwift also support it.

I'd also urge for adding macos and tvos support while performing this change, as SPM is used widely used by all platforms.


Test ZecWallet Lite with lightwalletd + Zebra

Motivation
We want to make sure that ZecWallet Lite works when connected to a lightwalletd that is connected to a Zebra instance.
Specifications

Designs
You will need a customized ZecWallet Lite to make it connect to your instance of lightwalletd (which should be configured to connect to your Zebra instance)
Related Work

Testnet + upstream lightwalletd results:

Shielded Sapling transactions show up in the wallet, but never become spendable

Investigating zecwallet-light-cli code, this seems to be caused by the anchor_height always having the wallet birthday and never increasing. Not sure why.

When you click a transaction, it shows the wrong TXID (the old SHA256d one, instead of the NU5 TXID)

I can also see getrawtransactions queries to Zebra using the wrong TXID (and of course, failing). But somehow the shielded transactions and balance show up correctly

Transparent transactions / balance do not show up at all (even though my address has a balance)

getaddressbalance does not seem to be called, so it seems it computes the balance manually (I do see a getaddresstxids followed by a getrawtransaction which work successfully)

The same happens when using zcashd, so it does not seem to be a Zebra issue.

Now that NU5 activated it shouldn't work anymore in mainnet too.
The zingolabs CLI fork should work, and they're working on integrating it in the GUI

The wallet was fixed and now works post-NU5!
To test it:

Run lightwalletd with Zebra. Use the -no-tls-very-insecure flag (i.e. no need to use certificates). You can add --grpc-logging-insecure to see the GRPC calls from the wallet being made.
Checkout ZecWallet Lite from this branch which hardcodes its lightwallet to localhost. Follow its README to build and run it. In short: install node (I had to use version 16 due to a bug), install yarn, run yarn install, yarn build, then yarn start
Check if the wallet works


Feature: Palette commands to open workspaces

Hi. Just registering the issue from the old gitlab repo.
It would be nice if is also possible open saved workspaces from the command palette.
The commands may look like:
(1) open workspace in this window;
(2) open workspace in new window.
Both commands are followed by a listing of the registered workspaces.  Other commandos, such as create workspaces, folder, and delate, may stay in the extension pane.
OBS: Sorry. I have no expertise to contribute with PR.

Hello,
I briefly gave CTRL+K W shortcut a try and, in my case, it asks me to select from two top level folders in my workspace data storage path and then simply lists all .code-workspace files there in the sidebar instead of actually opening one. Perhaps this hasn't been tested with nested workspace structure.

@plx44r could you open a separate issue for the bug report.
@alanlivio this feature is available via keyboard shortcuts in 2.1.0. See the latest README News section. Feel free to reopen if it doesn't match your needs.

hi @sirfuzzalot. thank you.
I had installed tomsaunders.vscode-workspace-explorer and not latest tomsaunders-code.workspace-explorer.
Thanks.


feat: allow non-object matchers for array-contains

I have recently been writing a lot of pact tests and I noticed that the array-contains matcher requires each variant to be an object.
Reading the spec, it says "Checks if all the variants are present in an array".

https://github.com/pact-foundation/pact-specification/tree/version-4

Based on this, and the below implementation guides, it seems that non-object types should be supported too.

https://docs.pact.io/implementation_guides/javascript/docs/matching#array-contains-matcher
https://docs.pact.io/implementation_guides/jvm/consumer#array-contains-matcher-v4-specification

Having given the code base a cursory review, it seems that supporting this should be quite trivial.
Note: this is my first PR here so please let me know if there are steps I have missed

While this is a trivial change, I'm unsure that it would work correctly. If the variant is an array (like [A, B]), I think that means that the source array must include a sub-array with the values A, B in that order.
Is this what you require?

While this is a trivial change, I'm unsure that it would work correctly. If the variant is an array (like [A, B]), I think that means that the source array must include a sub-array with the values A, B in that order.
Is this what you require?

This seems to be consistent with the rest of pact. If I wanted to check that a sub-array contained certain items in no particular order, I would be able to specify further "array-contains" matchers in a nested fashion, something like:
Match.ArrayContains([
    Match.ArrayContains(["A", "B"]),
    Match.ArrayContains(["C", "D"]),
])

As you say, if I specified just the arrays, they would need to match in the specified order:
Match.ArrayContains([
    new[] { "A", "B" },
    new[] { "C", "D" },
])

Not sure what kind of use case would require nested array-includes, but nonetheless I think this change makes it possible to specify both restrictions
Can see this as a test case I added to a fork of PactNet running on top of the changes in this PR

Awesome, I'll merge it.


Print syntax errors on Python3

It looks like there might be some compatibility issues running this library under Python3:
$ pip install pysony
Collecting pysony
Installing collected packages: pysony
Successfully installed pysony-0.1.11
$ python
Python 3.6.7 (default, Oct 22 2018, 11:32:17)
[GCC 8.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pysony
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/bjmc/Sandbox/sony_camera_api/.env/lib/python3.6/site-packages/pysony.py", line 195
    print "[WORN] liveview is not a dict type"
                                             ^
SyntaxError: Missing parentheses in call to 'print'. Did you mean print("[WORN] liveview is not a dict type")?

I confirm this issue. Its a matter of adding the paretheses in the calls to print.

And actually some other stuff related to urllib

it merged.


HFix column offset

Error underlines were starting one column too early, because nix
error messages index on 0 not 1.

can you point me any docs on this?
also what happens to row ?

Hrm, if you can’t reproduce it maybe nix produces the wrong lines. I’ll revisit this if I notice it again in the future.


fix(deps): use python core v3.3.6

PR summary
Upgrades python core to v3.3.6
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[x] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

:tada: This PR is included in version 0.17.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 0.17.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Cannot find resource: index.html

Unable to open web interface.
I have built successfully with docker image but when i initialize using the docker ,it starts but the web interface wont open. It will throw out an error saying Cannot find resource: index.html
Any help would be really appreciated .

I am also getting the same error


New component: Overlays - Toast

I need to use exactly the same toast component as in Blueprint.JS (https://blueprintjs.com/docs/#core/components/toast).
I am ready to try to implement it on my own, if necessary, but I am a junior and not sure about how successful would it be.

Welcome to the community @embu18 . We are refactoring the current components to Glimmer components and therefore, cannot commit on its ETA. I would rather suggest you wait for some time to take full advantage of the Octane features. Thanks.


Yet more ongoing cAVS cleanup & futureproofing

Another batch of changes.  The big one being that the Xtensa double-mapped memory trick which underlies KERNEL_COHERENCE has been generalized and moved from the SOC into the Xtensa architecture, since it's something any hardware vendor might do and involves nothing specific to the audio DSPs at all.  And this allows us to configure it with just two kconfigs.

Add one more patch to address a genuine bug I stumbled on (@dcpleung sorry, I dismissed your review, please check the new patch?) and remove the IPC header, which was dead code as it stands and which if things go well should re-appear as part of a proper driver in a day or two.

This does not make SOF PR testing worse https://github.com/thesofproject/sof/pull/5175


feat: Allow multiple data pushes in OP_RETURN output

Currently, the Bitcoin Ledger app only supports OP_RETURN outputs with a single data push. This is a limitation that is not present in the Bitcoin protocol itself, and it would be great to see this limitation removed in the Ledger app.
This would allow for more flexible use of the OP_RETURN output, and would allow for more complex data to be stored in the blockchain.
Primary short term Use case - Support for RUNES Protocol (going live with the next halving):
The Runes protocol aims to introduce a robust fungible token protocol on Bitcoin. It could significantly benefit the ecosystem by attracting more transaction volume, developers, and users. Runes aims to offer a simple, UTXO-based token system that minimizes on-chain footprint and integrates seamlessly with Bitcoin's architecture, avoiding the complexities and limitations of existing token protocols.
Current token solutions on Bitcoin suffer from issues like high complexity, reliance on off-chain data, UTXO proliferation or the need for a native token, which hinders adoption and user experience. Runes proposes a straightforward approach: token balances are held by UTXOs and OP_RETURN outputs are used for protocol messages. This ensures ease of use, reduced onchain footprint & more responsible UTXO management.
Other use cases - Bitcoin ecosystem apps & Bitcoin L2s (Q2 2024):
By enabling multiple data pushes in OP_RETURN outputs, the Ledger app would also support a wider range of applications, including Bitcoin layer 2 networks which rely on them for pegging/bridging operations to and from Bitcoin mainnet.

Hi, can you give some idea regarding the project, I saw the good first issue mark and really want to work on issue, can please give me more idea on the and how to start work on it.

Looks like this logic needs to change: https://github.com/LedgerHQ/app-bitcoin-new/blob/develop/src/common/script.c#L135

Here is an example txn which is currently unsignable with Ledger: https://mempool.space/testnet/tx/cf32d8c280ca48b0d0a67335a39ae6fd4fefba9338793c87165ffacf691848a1
The OP_RETURN script being 6a0952554e455f544553541e0203049deebbe8878ad4d50e010b0383480546000080e2aee9a598ff0001

I've just stumbled across this as I realise since starting to buy Runes on BTC (https://support.xverse.app/hc/en-us/articles/26031360456973--Ledger-Device-UNKNOWN-ERROR-0x6a82-Error-Message-When-Minting-or-Sending-Runes).
Unfortunately, there were no warnings on the purchase of items, and my runes are stuck in my xverse wallet. This is somewhat of a big issue - are you able to give an update on when this will be fixed?
Thanks

@AlastairPreacher please contact Xverse support via a ticket. We have a solution for you.

Hey @victorkirov - that's great to hear. I've reached out to them so await to hear back.

@AlastairPreacher Sorry, I thought we built a solution for this. Once the next version of Xverse comes out, you can use Magic Eden to transfer your Runes out or list directly on ME from your Ledger. Listing currently works fine on ME from Ledger but if you try to transfer it will incorrectly tell you that you're going to burn your runes. You can list on ME now if you wish, otherwise, I'd suggest waiting another day or 2 for the new patch and transfering your runes out then.

Thanks. I'll wait for the patch to allow me to transfer out as I want to
split up the bundles into smaller amounts before selling over time.
Appreciate the additional reply.
Thanks,
Alastair
Alastair Preacher
+44 (0)7976 616 408

Check out my newsletter:
🌮  Product Tapas: producttapas-newsletter.beehiiv.com
Time-saving product bites delivered right to your inbox.

On Sat, 27 Apr 2024, 18:20 Victor Kirov, @.***> wrote:

@AlastairPreacher https://github.com/AlastairPreacher Sorry, I thought
we built a solution for this. Once the next version of Xverse comes out,
you can use Magic Eden to transfer your Runes out or list directly on ME
from your Ledger. Listing currently works fine on ME from Ledger but if you
try to transfer it will incorrectly tell you that you're going to burn your
runes. You can list on ME now if you wish, otherwise, I'd suggest waiting
another day or 2 for the new patch and transfering your runes out then.
—
Reply to this email directly, view it on GitHub
https://github.com/LedgerHQ/app-bitcoin-new/issues/245#issuecomment-2081105253,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKPLNT6LWV6PZV6X7LQY3EDY7PM7BAVCNFSM6AAAAABE56PODCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBRGEYDKMRVGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

+1
Hi guys, any news on the workaround that makes runes transferable from a ledger? I think this is a high priority issue.
it would be nice to show a warning alert about Runes/Ledger problem on the wallet when trying to connect a new ledger device, this will help tremendously and avoid users to be traped.
Thanks

+1
I updated to the newest version 0.34.2 but still not able to transfer my runes using Xverse+Ledger. Is anyone working on this?

+1

We have a very basic web portal that will allow you to send out your runes from the Ledger address. You can get in touch with support for the details.
As for full Ledger support, @bigspider opened the above PR which will allow full Runes support with Ledger 🙌 🎉

Thanks @victorkirov, @bigspider it's great to see this being fixed!! Do you know when the next release will be published?

hello good afternoon. I sent some tokens to my xverse wallet and I can't withdraw them because I'm using the ledger on it, so what do I do now? It was easy to send it, now I can't get it out.  I need a solution.

Tokens Runes

Hi @bigspider. Thanks for your work. Is this included in the newest release? I updated to 0.35.1 today but sending runes is still not working.

@wfyhehe this is a Ledger update, not an Xverse one. You will need to wait for the next version of the Ledger Btc app to be released.

FYI: Version 2.2.3 should go live some time next week. Thanks for your patience.

@bigspider Tested and Ledger Rune transfers are working 🎉 Thanks for getting this through so quickly!


fix missing temp_low/high_template in SCHEMA_BASE

Description:
fixing missing template entries from SCHEMA_BASE. Before it resulted in a key_error when using the templates in the discovery message.
Related issue (if applicable): fixes #27738 (although updating the docs is still required)
Checklist:

[X] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.
[ ] I have followed the development checklist

Hi @kevinkk525,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

Need also tests

I'm sorry this is my first PR for homeassistant and I don't know what to do.
Also I'd prefer not to dive into everything for adding 2 lines that the original author just forgot to add. I'd be happy if someone else (maybe the original author) would add everything that is missing to this PR.

The tox component test was successful, however looking at the testcases the temp_low/high templates were never tested so there would need to be testcases for those first.. So much work for a simple bugfix in 2 lines..
Update the documentation too

Added testcase. I hope I made it correctly. It passes tox.