Android - app crashing intermittently while connecting

Describe the bug
INJI app crashing intermittently while connecting on only specific device (device details added at at last)
To Reproduce
Prerequiste: VC is downloaded and stored in sharing device
Device A - Requesting device
Device B - Sharing device
steps:

open qr code in Device A
open scanner in Device B

Expected behavior
The app should able to connect properly and share VC with out any intermittent issues in all devices
Observed
App is crashing and not connecting on specific device (device details added bellow)
Video
https://user-images.githubusercontent.com/102220709/215695949-f6c9fb83-d9ce-4396-a837-46f210c0e796.mp4
Smartphone:
Sender device :
Android version : 10
BLE version : BLE 5.0
device name : redmi note 10 lite
Receiving device :
Android version : 12
BLE version : 5.0
device name : vivo Y73
Remaining details :
MOSIP Version: <IP_ADDRESS>
MOSIP server: qa-1201-b2.net
APP link; https://github.com/mosip/inji/actions/runs/3986424542

This issue is observed in our another set of tedting devices too, and observed in the new APk, iam mentioning its details below
Receiving device :
Android version : 9
BLE version : 4.2
device name : Redmi 6A
sender device :
Android version : 10
BLE version : BLE 5.0
device name : redmi note 10 lite
Remaining details :
MOSIP Version: <IP_ADDRESS>
MOSIP server: qa-1201-b2.net
APP link; https://github.com/mosip/inji/actions/runs/3986424542

closed it by mistake reopening it now

Here are some more details about analysis mentioned in other channels
2023-02-01 15:00:48.501 19230-25563 AndroidRuntime          pid-19230                            E  FATAL EXCEPTION: CentralHandlerThread
                                                                                Process: io.mosip.residentapp, PID: 19230
                                                                                java.lang.NullPointerException: Attempt to invoke virtual method 'android.bluetooth.BluetoothGattCharacteristic android.bluetooth.BluetoothGattService.getCharacteristic(java.util.UUID)' on a null object reference
                                                                                at io.mosip.tuvali.ble.central.impl.GattClient.subscribe(GattClient.kt:259)
                                                                                at io.mosip.tuvali.ble.central.impl.Controller.subscribe(Controller.kt:55)
                                                                                at io.mosip.tuvali.ble.central.state.StateHandler.handleMessage(StateHandler.kt:205)
                                                                                at android.os.Handler.dispatchMessage(Handler.java:106)
                                                                                at android.os.Looper.loop(Looper.java:236)
                                                                                at android.os.HandlerThread.run(HandlerThread.java:67)

We have done a quick verification of provided stack trace. It’s pointing to a code from Jan 20th release. This stack is not relevant to latest build (Jan 30th or Feb 7th) as the debug symbols don’t match.
We also think the chances of this crash happening in latest build will be less as we have incorporated retry strategy (in Jan30th build) which will ensure services are discovered before doing subscription.
As mentioned in the previous message. Please revalidate with latest version https://github.com/mosip/inji/commit/c75f8f16ce4a7a39d92c6a9f9b8bc0c9e4c39529

The #542 issue is not related to this issue, unable to delete it

Verified this issue in the new build, and the issue is not observed anymore, instead of crashing we are facing an error message, which is expected as we all discussed over the call, I am attaching the current working flow video, and device details below
screenshot :
https://user-images.githubusercontent.com/102220709/225245370-c9c55944-5d60-4ce9-a4b3-7ffe88cd3e14.mp4
Tested on :

Wallet :
Phone make/model: Apple iphone 7
OS: IOS 15.6
BLE version : 4.2

Verifier :
Phone make/model: Pixel 6
OS: Android 13
BLE version : 5.2

MOSIP Version : <IP_ADDRESS>
MOSIP server : qa-1201-b2.net
App link :
IPA Testflight version : 0.4.1 (25)

what is the solution for the crash issue. our inference was disconnect pop-up will be displayed to handle crashes gracefully. but if our inference is wrong, can you please explain how is this handled? please add comments to reverify, hence re opening the bug.

This bug has been moved to Jira.
Link to Jira bug: https://mosip.atlassian.net/browse/INJI-72

verified as fixed in the build with commit id in the below screenshot.


v0.5.2

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/61982
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.5.2 -m "<description of version>" 01b82fd31f8cef3b8dadd1291e34de21a8897c7c
git push origin v0.5.2


make cygrpc importable on py3

Previously, importing grpc._cython.cygrpc on python 3.x would crash the interpreter.
The cause was that the PyMODINIT_FUNC macro was overwritten in a python2-specific way. In the python2 C API, PyMODINIT_FUNC should be void, whereas in python3 the module initialization function returns a PyObject* pointing to the module, as described in the python3 C porting docs.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

This is OK to test.

lgtm

Ah cool, looks like your test fixit was a success! I like how the different tests are shown as independent checks on the PR.

I'm not sure I understand this test failure, any ideas?

For this change on the "python" and "sanity" sub-matrices matter. :-)


installFeature doc says it can take a URL but it doesn't work

Over at installFeature it says that name is an array, the elements of which:

can be a file name or a URL to the ESA file.

However, I've tried the following:
liberty {
    server {
        features {
            name = ["https://my-host.com/path/to/my.esa"]
            acceptLicense = true
        }
    }
}

And this doesn't work:
CWWKM2002E: Failed to invoke [/path/to/my/project/build/wlp/bin/installUtility, install, --acceptLicense, https://my-host.com/path/to/my.esa]. RC= 20 but expected=[0, 22].

Trying to run the same direct via installUtility I get:
CWWKF1267E: The file /path/to/my/project/build/wlp/https:/my-host.com/path/to/my.esa does not exist.

... so it's being interpreted as a local file. I also can't find any tests around the place to confirm that the name can be a URL.

Given that installUtility does not handle it, I think we need to use this issue to change our documentation. I looked up the documentation for installUtility and it does not mention supporting URLs.
https://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/rwlp_command_installutility.html

I have verified that URLs are not supported. I will update our doc accordingly.


Fixes to the configuration object

Thanks for a useful library.
I'm attaching three independent commits in this PR.
6dcb8f9
This commit fixes reading of environment variables. Previously no environment variables were read, it just wasn't implemented even if it appeared in settings that you could have some connection options refer to environment variable names.
8096dd8
I've removed required: true from all connection options fields. They all feed into pg.Pool which then internally feeds into pg.Client and they are all optional as far as the underlying pg library is concerned. For example I don't use a password at all to connect to my Postgres DB and that works just fine, so why is it required to set a password at all? This commit fixes that.
36b56ff
This removes swapping the input attribute type to/from password and text because it doesn't work well. This is how it looks in my installation of node-red v2.0.5:

It's quite confusing, and while I understand why this was added in the first place the existing implementation just doesn't work and this commit removes it.

Hello and thanks for this PR. Sorry for the delay. For some reason, I did not see any notification...

Version 0.3.0 published: https://github.com/alexandrainst/node-red-contrib-postgresql/releases/tag/v0.3.0
Tests welcome. Thanks again!


Expose to WASM

I think this is currently blocked by https://github.com/santhosh-tekuri/boon/pull/23 — I'm not "smart" on WASM, but when I checked wasm32-unknown-emscripten in cql2, I got:
$ cargo check --target wasm32-unknown-emscripten
--- >8 ---
    Checking boon v0.6.0
error[E0432]: unresolved import `loader::FileLoader`
   --> /Users/gadomski/.cargo/registry/src/index.crates.io-6f17d22bba15001f/boon-0.6.0/src/lib.rs:121:14
    |
121 |     loader::{FileLoader, SchemeUrlLoader, UrlLoader},
    |              ^^^^^^^^^^
    |              |
    |              no `FileLoader` in `loader`
    |              help: a similar name exists in the module: `UrlLoader`
    |
note: found an item that was configured out
   --> /Users/gadomski/.cargo/registry/src/index.crates.io-6f17d22bba15001f/boon-0.6.0/src/loader.rs:31:12
    |
31  | pub struct FileLoader;
    |            ^^^^^^^^^^
note: the item is gated here
   --> /Users/gadomski/.cargo/registry/src/index.crates.io-6f17d22bba15001f/boon-0.6.0/src/loader.rs:30:1
    |
30  | #[cfg(not(target_arch = "wasm32"))]
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0432`.
error: could not compile `boon` (lib) due to 1 previous error

You should compile to wasm32-unknown-unknown. That's the primary supported browser webassembly target for Rust

You should compile to wasm32-unknown-unknown.

Yup good point, I'll be sure to target that when we can build out. I tried that first and ended up with a transitive dependency yelling at me, so that will take unpicking once boon is fixed:
error: the wasm*-unknown-unknown targets are not supported by default, you may need to enable the "js" feature. For more information see: https://docs.rs/getrandom/#webassembly-support
   --> /Users/gadomski/.cargo/registry/src/index.crates.io-6f17d22bba15001f/getrandom-0.2.15/src/lib.rs:342:9
    |
342 | /         compile_error!("the wasm*-unknown-unknown targets are not supported by \
343 | |                         default, you may need to enable the \"js\" feature. \
344 | |                         For more information see: \
345 | |                         https://docs.rs/getrandom/#webassembly-support");
    | |________________________________________________________________________^

Well, fwiw that's a one-line change to fix that error https://github.com/kylebarron/parquet-wasm/blob/7ea19b91b9d026da19cb9aacc60c0befd6ce355b/Cargo.toml#L61


Images shrink and flip in the wrong orientation on some Android devices

We've been encountering this weird bug on some devices where this happens to images:

This was the Landscape_3 image from the https://github.com/recurser/exif-orientation-examples repo
The two devices we know this happens on are Xiaomi and Huawei ones and I was able to reproduce this reliably on a Huawei P30.
I don't understand how or why this happens exactly and it also happens with PNGs (I wasn't able to get the original files).
When I set the exifOrientation: 1 in the options, it fixes the issue, but I don't want to do that since I would like it if we can respect the orientation of the images the user uploads.
This is another image that this happens to as well and based on the software I use (InfraView), it doesn't contain exif information:

The result after compression:

Hi @Donaldcwl,
I understand if you aren't able to look at this, I can help.
Before I try, can you please give me your thoughts about it? Where should I start and what to keep in mind while doing so. I can reliably replicate this through devices on browserstack, so I just need some direction on what to do or look for to figure out the root cause.

Do you still having this issue?

@dcruz1990 Not after I hardcoded the exifOrientation to 1.
I don't know if that is a good solution though


Add --inspect

https://github.com/mochajs/mocha/releases/tag/v3.2.0
https://github.com/mochajs/mocha/pull/2520

Thank you!


Adds regex setoid instance to take advantage of the equivalence relation structure

Adds regex_eq as an equivalence relation (Parametric Relation).
Adds nullable, derive and regex constructors as Parametric Morphisms (functions
that preserve the equivalence relation structure).
The idea is to work with regex equality using Coq's Generalized rewriting
mechanism (setoid_reflexivity, setoid_rewrite).

I think this would be worth impromptu explaining on the next stream, if you are up for it.
And we should definitely start using it.
I think maybe we should follow up this diff with splitting derive.v into two files.
One for the Definitions and one for the Theorems.
So that we can import this setoid and the definitions into the theorems file and use the power of setoids there.
What do you think?

Just to be clear: We should still keep our old proofs and redo some of them using setoids, to show of similar ways of proving the same thing.  We shouldn't throw away our old proofs, but more than happy to accept alternatives that shows off this setoid power.


Proposal to remove Type for SubjectAlternativeName

Description

A user should not need to be aware of which "type" or GeneralName the subject is set in. Removing Type would simplify how a certificate identity is represented to be comprised of a subject and issuer only. This is also aligned with other Sigstore client implementations.
A similar conversation occurred in Fulcio previously (https://github.com/sigstore/fulcio/issues/716#issuecomment-1204549133), and the threat of "type confusion" was mitigated through CA enforcement that URIs look like URIs and emails look like emails, rather than client enforcement.
Relevant code:

https://github.com/sigstore/sigstore-go/blob/main/pkg/fulcio/certificate/summarize.go#L37
https://github.com/sigstore/sigstore-go/blob/main/pkg/verify/certificate_identity.go#L72-L76

I'd like to discuss this, I'm fine if we ultimately decide there is value in keeping this, but with the goal of making breaking changes before a 1.0, wanted to raise this.

cc @woodruffw since we've talked about related things many times

+1 from me -- IMO type separation is good generally, and is best handled at the CA/issuance layer in this case rather than within individual clients.


add ingress resource for list and find

Is this good to go @akshay-duplo ?
If so, I'll merge.

I checked other commands, and it provides results in same format.
I have tested it.

Awesome, I'll merge


Add watcher args

This change provides the arguments to Watcher object in watch function.
For example, when I would like to define ignored directories instead of hard-coding them.
class ImageWatcher(AllWatcher):
    re_img = re.compile(r".*(jpe?g|png|bmp)$", re.IGNORECASE)

    def __init__(self, root_path, ignore=None):
        self.ignore = ignore or []
        super(ImageWatcher, self).__init__(root_path)

    def should_watch_file(self, entry):
        return self.re_img.match(entry.path)

    def should_watch_dir(self, entry):
        return entry.name not in self.ignore

for changes in watch(".", watcher_cls=ImageWatcher, watcher_args=["ignore"]):
    print(changes)

I sorry for the slow reply. I'm currently away traveling and will look soon.

great, thanks.


There is no installation instructions

I am really interested in this framework, but I am not able to try it because there is no explanation of how can I even install it.

Try Carthage and use them latest commit
On Dec 13, 2017 10:21 AM, "Adin Ćebić"<EMAIL_ADDRESS>wrote:

I am really interested in this framework, but I am not able to try it
because there is no explanation of how can I even install it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/moozzyk/SignalR-Client-Swift/issues/4, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABX0pKZOyLtYODFcobw13Gh_4mys7XlOks5tABXBgaJpZM4RA-aR
.

@moozzyk  I tried Carthage but had no luck.
Here is the output from the terminal
*** Fetching SocketRocket
*** Checking out SocketRocket at "28035e1a98a427853e4038ff1b70479fa8374cfa"
*** Checking out SignalR-Client-Swift at "31c6afb9994df6e903bd56adf20eb792f74d91e8"
*** xcodebuild output can be found in /var/folders/mb/py89x9p177b7fwt7sm7vk2dr0000gn/T/carthage-xcodebuild.IUI9Yx.log
*** Building scheme "SocketRocket-iOS-Dynamic" in SocketRocket.xcodeproj
*** Building scheme "SocketRocket-macOS" in SocketRocket.xcodeproj
*** Building scheme "SocketRocket-tvOS" in SocketRocket.xcodeproj
*** Skipped building SignalR-Client-Swift due to the error:
Dependency "SignalR-Client-Swift" has no shared framework schemes
If you believe this to be an error, please file an issue with the maintainers at https://github.com/moozzyk/SignalR-Client-Swift/issues/new

I will take a look and then maybe add details to the readme.
On Dec 13, 2017 12:14 PM, "Adin Ćebić"<EMAIL_ADDRESS>wrote:

@moozzyk https://github.com/moozzyk I tried Carthage but had no luck.
Here is the output from the terminal
*** Fetching SocketRocket
*** Checking out SocketRocket at "28035e1a98a427853e4038ff1b7047
9fa8374cfa"
*** Checking out SignalR-Client-Swift at "31c6afb9994df6e903bd56adf20eb7
92f74d91e8"
*** xcodebuild output can be found in /var/folders/mb/
py89x9p177b7fwt7sm7vk2dr0000gn/T/carthage-xcodebuild.IUI9Yx.log
*** Building scheme "SocketRocket-iOS-Dynamic" in SocketRocket.xcodeproj
*** Building scheme "SocketRocket-macOS" in SocketRocket.xcodeproj
*** Building scheme "SocketRocket-tvOS" in SocketRocket.xcodeproj
*** Skipped building SignalR-Client-Swift due to the error:
Dependency "SignalR-Client-Swift" has no shared framework schemes
If you believe this to be an error, please file an issue with the
maintainers at https://github.com/moozzyk/SignalR-Client-Swift/issues/new
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/moozzyk/SignalR-Client-Swift/issues/4#issuecomment-351509016,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABX0pNqT8kMAxAKNqzpoNLuat_z6oqQhks5tADBDgaJpZM4RA-aR
.

@moozzyk  I am really grateful for your work, your framework has potential to help me a lot. Also, could you please add usage examples in the readme so people can have some documentation? Thanks!


Add @AllChildren annotation

Tickets addressed: Part of #1364 but does not resolve it
Review: By commit
Merge strategy: Merge (no squash)

Description

Add a @AllChildren annotation to mission model so mission modelers can report, for a given activity, what other activity is called/spawned. This information will be used by the scheduler to evaluate whether it is useful to resimulate or not before goal evaluation: let's have G goal being satisfied by an activity of type A, G is the next goal to be evaluated. If an activity of type B was inserted at the last iteration, has B any chance of generating A and thus of satisfying the goal G ? If yes, simulation is required, otherwise it's not (for that only purpose, there might be other things that warrant a simulation, e.g. the goal needs to also evaluate an expression...).
Some edge cases:

If the user does not use the annotation for an activity, we make the worst case assumption that the activity might generate all activities (itself included).
Activities without effect model cannot generate children

This PR does not contain changed to the scheduler to use this information. These changes would overlap too much  with changes under review in #1323
Verification

A test with the banananation model has been added to verify that the generated code is accurate.
Documentation

To be done.
Future work

Other things in #1364 + use the annotation in the scheduler.

This is blocked because part of an ongoing prototyping for dependency modeling in #1364.

@dandelany I think we can close this PR.


Add example how to generate a message

An example that describes how exactly one should use the message bus was missing in my view. It is not exactly clear to me what xxx.yyy.zzz stand for still.

Hi there,
Thank you for helping with the Mycroft project! We welcome everyone into the community and greatly appreciate your help as we work to build an AI for Everyone.
To protect yourself, the project, and users of Mycroft technologies we require a Contributor Licensing Agreement (CLA) before accepting any code contribution. This agreement makes it crystal clear that along with your code you are offering a license to use it within the confines of this project. You retain ownership of the code, this is just a license.
You will also be added to our list of excellent human beings!
Please visit https://mycroft.ai/cla to initiate this one-time signing.
Thank you!

CLA received, thanks for the clear example!


Assignment 2

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Completed assignment 2.
What did you learn from the changes you have made?
In this assignment, I re-applied some concepts learned in previous modules on splitting data into training and test sets and running ML algorithms.
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
N/A
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
This assignment was a good refresher for some of the concepts previously  learned (applying statistical methods) and building on the concepts already learned.
How were these changes tested?
I ran the code with examples to ensure it works.
A reference to a related issue in your repository (if applicable)
N/A
Checklist

[X] I can confirm that my changes are working as intended

A2: Complete


feat: use biome check

Summary
This PR closes #23
Now the plugin run biome check instead of biome format and biome lint in separated form.
This PR also implement  a improvement to the auto-save configuration description:

When the biome is not found

If it fits your schedule, I would be happy about a fresh nightly release. We are currently migrating from Prettier to Biome and are already testing the latest nightly version - "biome check" would be a nice addition here.

@BC-M  Done! let me know what do you think about the new version!
I really want to release a stable version very soon, any feedbacks about the nightly version are welcome ✌🏻

@victor-teles Thanks! downloaded the latest nightly and it's working great so far.


Make Travis Happier to work with

I'm not sure what limits we're running into right now (disk space, memory?). Travis seems to be stalling out on the regular while I'm able to build and run this all locally on Linux and OS X.

I've taken Travis down for now, going to start investigating Strider for our workflow.

Oh, Travis...
@rgbkrk — Fix your issue title!

Now that zmq-prebuilt is out, I can't wait to re-enable Travis. :smile:

Super done by @jdfreder, complete with zmq artifact caching.


Increase MAX_REQUEST_TYPES for AesWorker

Apparently blocked by
https://github.com/dalek-cryptography/curve25519-dalek/pull/619

I am merging this as CI errors are outside of our control.


Convert to CircleCI setup

Currently, this setup fails just like it did on travis with an error because the latest libgit2 package on both debian and ubuntu is behind at 0.24.6. git2go requires 0.25.1 at the moment. Using the experimental package doesn't help as it's at 0.26.0.

Issue #6 opened for dependency problem.


Merge Icv3 changes

And of course you need to run pre-commit :-)

@lcv3 would you be able to work on the issue? I don't posses MS Projekt anymore, so I would need your help.


add oper-state validation

Pull Request Functional Test Report for #2243 / d79a768dc479aea73c68c89c82dbabd91cb25b18
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

gNOI-2.1: Packet-based Link Qualification
5f1a65aa
Log

Cisco 8000E

gNOI-2.1: Packet-based Link Qualification
09d9c5a4
Log

Cisco XRd

gNOI-2.1: Packet-based Link Qualification
6f4e8f04
Log

Juniper cPTX

gNOI-2.1: Packet-based Link Qualification
04237f03
Log

Juniper ncPTX

gNOI-2.1: Packet-based Link Qualification
902bb469
Log

Nokia SR Linux

gNOI-2.1: Packet-based Link Qualification
a2cd8488
Log

Openconfig Lemming

gNOI-2.1: Packet-based Link Qualification
af25e3a2
Log

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

gNOI-2.1: Packet-based Link Qualification

Cisco 8808

gNOI-2.1: Packet-based Link Qualification

Juniper PTX10008

gNOI-2.1: Packet-based Link Qualification

Nokia 7250 IXR-10e

gNOI-2.1: Packet-based Link Qualification

Help


Message Handling in Modules

Currently the message handler is passed only to instances of class objects.  This doesn't allow module-level methods to make use of the message handler, which leaves many "print" statements that don't conform to the rest of the code.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[ ] 1. Is it tagged with a type: defect or improvement?
[ ] 2. Is it tagged with a priority: critical, normal or minor?
[ ] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[ ] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[ ] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)?
[ ] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?

I believe this issue have fixed.

archived

archived


Issue/add data collector

Description
Part of https://github.com/inmanta/inmanta-core/issues/4886
First steps towards adding data collection for predictive test selection.
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

@arnaudsjs is it OK to add this in core for now? It can move out in a later stage, but not it is kind of convenient here.

@arnaudsjs is it OK to add this in core for now? It can move out in a later stage, but not it is kind of convenient here.

I think it's fine to keep it in here for now.

Processing this pull request

Merged into branches master in 6d24c8c1044591b18494c1a9f96c5e8a9956d886


luci-app-https-dns-proxy: https-dns-proxy support option use_http1

https-dns-proxy support option use_http1
Signed-off-by: Robin<EMAIL_ADDRESS>

@robinZhao Thank you for your contribution. Could you please update the PR title to reflect the name of the luci app (check the other PRs for examples).
Could you please also describe the use case when the default config is not working as expected and exposing this setting in the WebUI is needed?

@robinZhao Thank you for your contribution. Could you please update the PR title to reflect the name of the luci app (check the other PRs for examples).
Could you please also describe the use case when the default config is not working as expected and exposing this setting in the WebUI is needed?

ok

Could you please also describe the use case when the default config is not working as expected and exposing this setting in the WebUI is needed?

^^^ this?

openwrt log this message when use some doh server
04:18:13 https-dns-proxy[13386]: [E]<PHONE_NUMBER>.038372 https_client.c:102 CURLOPT_HTTP_VERSION error 1: Error 04:18:13 https-dns-proxy[13386]: [E]<PHONE_NUMBER>.038413 https_client.c:104 Try to run application with -x argument!
https-dns-proxy configed this option fixed this issue.
we supported this option in luci interface.

openwrt log this message when use some doh server 04:18:13 https-dns-proxy[13386]: [E]<PHONE_NUMBER>.038372 https_client.c:102 CURLOPT_HTTP_VERSION error 1: Error 04:18:13 https-dns-proxy[13386]: [E]<PHONE_NUMBER>.038413 https_client.c:104 Try to run application with -x argument! https-dns-proxy configed this option fixed this issue. we supported this option in luci interface.

Which DoH server? Which OpenWrt version?

openwrt log this message when use some doh server 04:18:13 https-dns-proxy[13386]: [E]<PHONE_NUMBER>.038372 https_client.c:102 CURLOPT_HTTP_VERSION error 1: Error 04:18:13 https-dns-proxy[13386]: [E]<PHONE_NUMBER>.038413 https_client.c:104 Try to run application with -x argument! https-dns-proxy configed this option fixed this issue. we supported this option in luci interface.

Which DoH server? Which OpenWrt version?

dnspod,alidns,openwrt  19.07.8,  not test on 21.02

As far as I remember, this warning only comes up in the log once on start and the current version of https-dns-proxy (2021-09-27) then automatically switches to HTTP/1 for the DoH resolvers/platforms which do not support HTTP/2. Going forward, most if not all of the DoH resolvers will support HTTP/2 and on OpenWrt 21.02 and newer the HTTP/2 support is included with ibcurl by default.
Based on the above, I'm reluctant to merge a PR which will expose a setting which is:

Mostly unneeded on 21.02 and newer releases
Automatically enabled after two extra lines in the log-file on the older releases

Do let me know if you believe my conclusions are based on flawed assumptions.


Reading file in causes 'index out of bounds' error

I am attempting to read in a tdms file so I can perform calculations on the data contained within. The structure of the file is this:
test.tdms
    aux_data
        time [s]
        distance [in]
        gps
    mic_data
        time [s]
        mic 1
        mic 2
        ... mic 12

Reading in this test.tdms file like so:
let file = match TDMSFile::from_path(Path::new("src/data/test.tdms")) {
        Ok(f) => f,
        Err(e) => panic!("{:?}", e),
    };

throws the following error. I fear that the error is due to the tiered structure of my data because reading in the provided (non-tiered) standard, raw, and big endian tdms files works fine.
thread 'main' panicked at 'index out of bounds: the len is 2 but the index is 2', C:\...\.cargo\registry\src\github.com-1ecc6299db9ec823\tdms-0.2.5\src\segment.rs:114:75
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/897e37553bba8b42751c67658967889d11ecd120/library\std\src\panicking.rs:584
   1: core::panicking::panic_fmt
             at /rustc/897e37553bba8b42751c67658967889d11ecd120/library\core\src\panicking.rs:142
   2: core::panicking::panic_bounds_check
             at /rustc/897e37553bba8b42751c67658967889d11ecd120/library\core\src\panicking.rs:84
   3: core::slice::index::impl$2::index<str>
             at /rustc/897e37553bba8b42751c67658967889d11ecd120\library\core\src\slice\index.rs:250
   4: core::slice::index::impl$0::index
             at /rustc/897e37553bba8b42751c67658967889d11ecd120\library\core\src\slice\index.rs:18
   5: alloc::vec::impl$16::index<str,usize,alloc::alloc::Global>
             at /rustc/897e37553bba8b42751c67658967889d11ecd120\library\alloc\src\vec\mod.rs:2628
   6: tdms::segment::Segment::new<std::io::buffered::bufreader::BufReader<std::fs::File> >
             at C:\...\.cargo\registry\src\github.com-1ecc6299db9ec823\tdms-0.2.5\src\segment.rs:114
   7: tdms::TDMSFile::from_path
             at C:\...\.cargo\registry\src\github.com-1ecc6299db9ec823\tdms-0.2.5\src\lib.rs:124
   8: test::tdms_reader::open
             at .\src\tdms_reader.rs:11
   9: test::main
             at .\src\main.rs:15
  10: core::ops::function::FnOnce::call_once<void (*)(),tuple$<> >
             at /rustc/897e37553bba8b42751c67658967889d11ecd120\library\core\src\ops\function.rs:248

Hi there! I haven't had a chance to work on this library for a while, so apologies in advance for that.  Are you willing to share your test file with me so I can see what's going on?

Absolutely, thank you for the fast response. Here's a link to my test file that fails to read in: tdmsHandler.

I finally had a chance to take a look at this @marcus0596. I'm sorry for the super delayed response and you probably already moved to another TDMS reader, but I was unable to recreate the error with the TDMS file in that directory you linked.
I was able to inspect and dive into the file just fine - but maybe you've changed it since the last time I looked?

I believe I've corrected your error @marcus0596 . Apologies for taking so long, the joys of open source side projects. Hopefully you've been able to make progress, or moved to a different parser in the meantime!


doc: added some extra information for postgresql users.

It looks like if a user of PostgreSQL have his schema on public, Yii doesn't recognize his db. Maybe this will help to other Yii2 users

Note: If you are using PostgreSQL, make sure you have the schema on public.

Hello. Thank you for the suggestion, but I neither understand the described problem, nor understand the outcome of the note you've added.
Maybe, you could supply an example?

It's possible to use schema different from public.


[Backport][v1.44.x] Support musllinux binary wheels on x64 and x86

Original #28092.
Fixes https://github.com/grpc/grpc/issues/28906.
Realistically, v1.45.0 might be released in a month, or being delayed for a couple more weeks. The musllinux wheels can be helpful to our users with Alpine Linux. I hope we can release it as a patch.
@jtattermusch PTAL.

I'm not a fan of backporting feature work and I'm not sure if there's going to be a patch release for 1.44.x (so far not fixes have been needed), but if there is a patch release to fix a bug, we can include the new wheels while at it.
Please doublecheck the artifacts/distribtests on the v1.44.x branch aren't going to be broken by this PR (to avoid surprises).

Triggered prod:grpc/core/experimental/grpc_build_artifacts_multiplatform. The strategy sounds good. We won't patch release unless there is an urgent need.

Manually checked the distribtest result in the adhoc build everything run. 2 non-related C++ cases failed. Merging this PR.


Site detection faulty

Please correct module/sources/common/source_base.py
Line 266 should be
site_name = grab(device_object, "data.site.name")
instead of
site_name = grab(device_object, "data.site.data.name")
After this fix, site VRF and Tenant detection works again.
Kind regards and thanks,
Oliver

Hi Oliver,
Thank you for this great hint. This ~is~ was indeed a bug. It should be fixed now: https://github.com/bb-Ricardo/netbox-sync/commit/b7422791220069bb422309644a14622f18dfaea7
Can you check out the branch 'development' and see if it works for you? That would be great.

fixed in version 1.2.3


Some things wrong when building the CPU-only version.

hey, I got some things wrong when I try to build the CPU-only version.
the configuration session look like this

You have bazel 0.21.0- (@non-git) installed.
Please specify the location of python. [Default is C:\Users\YT\Anaconda3\envs\tensorflow-build\python.exe]:
Found possible Python library paths:
C:\Users\YT\Anaconda3\envs\tensorflow-build\lib\site-packages
Please input the desired Python library path to use.  Default is [C:\Users\YT\Anaconda3\envs\tensorflow-build\lib\site-packages]
Do you wish to build TensorFlow with XLA JIT support? [y/N]: n
No XLA JIT support will be enabled for TensorFlow.
Do you wish to build TensorFlow with ROCm support? [y/N]: n
No ROCm support will be enabled for TensorFlow.
Do you wish to build TensorFlow with CUDA support? [y/N]: n
No CUDA support will be enabled for TensorFlow.
Please specify optimization flags to use during compilation when bazel option "--config=opt" is specified [Default is /arch:AVX]:
Would you like to override eigen strong inline for some C++ compilation to reduce the compilation time? [Y/n]: y
Eigen strong inline overridden.
Preconfigured Bazel build configs. You can use any of the below by adding "--config=<>" to your build command. See .bazelrc for more details.
--config=mkl            # Build with MKL support.
--config=monolithic     # Config for mostly static monolithic build.
--config=gdr            # Build with GDR support.
--config=verbs          # Build with libverbs support.
--config=ngraph         # Build with Intel nGraph support.
--config=dynamic_kernels        # (Experimental) Build kernels into separate shared objects.
Preconfigured Bazel build configs to DISABLE default on features:
--config=noaws          # Disable AWS S3 filesystem support.
--config=nogcp          # Disable GCP support.
--config=nohdfs         # Disable HDFS support.
--config=noignite       # Disable Apacha Ignite support.
--config=nokafka        # Disable Apache Kafka support.
--config=nonccl         # Disable NVIDIA NCCL support.

Then it runs very well at first，but it encountered some errors in the middle，just like this:

ERROR: C:/tensorflow-build/tensorflow/tensorflow/core/kernels/BUILD:3221:1: C++ compilation of rule '//tensorflow/core/kernels:scan_ops' failed (Exit 2): cl.exe failed: error executing command

and this:

ERROR: C:/tensorflow-build/tensorflow/tensorflow/tools/pip_package/BUILD:241:1 C++ compilation of rule '//tensorflow/core/kernels:batch_matmul_op' failed (Exit 2): cl.exe failed: error executing command

I don't know if this error message is sufficient, if you need more details，just ask me.

I remember running in to some cl.exe errors initially, but I can't remember what I did to fix them. Let me know if you figure it out!

I remember running in to some cl.exe errors initially, but I can't remember what I did to fix them. Let me know if you figure it out!

oh, I see. I will try to fix it. But can you send me the the wheel file to my mailbox(my version of tensorflow is same to you). I can't wait to try how fast it can be than before, it is my email<EMAIL_ADDRESS>if I figure the wrong out, I will let you know as soon as possible.

I wish it was as easy as just giving you the wheel file! TensorFlow has to be built on your machine for the TOCO tools to work. There's something extra about the build process that doesn't happen during a normal wheel file installation. I'll have to ask a software developer why it has to be built on the PC rather than just installed.

I wish it was as easy as just giving you the wheel file! Unfortunately, TensorFlow HAS to be built on your machine for the TOCO tools to work. There's something extra about the build process that doesn't happen during a normal wheel file installation. I'll have to ask a software developer why it has to be built on the PC rather than just installed.

Hey, I think I have found a solution, but now I have to sleep first. I will give the solution in tomorrow morning.

I wish it was as easy as just giving you the wheel file! Unfortunately, TensorFlow HAS to be built on your machine for the TOCO tools to work. There's something extra about the build process that doesn't happen during a normal wheel file installation. I'll have to ask a software developer why it has to be built on the PC rather than just installed.

Hey, at the end of the fight against various bugs, I successfully ran the TF Lite model. This is really a great tutorial. But before I sorted out this series of errors, I found that it run in my laptop have only 1.96FPS,  it seem don't use the GPU i have in laptop, what should i do?

I wish it was as easy as just giving you the wheel file! Unfortunately, TensorFlow HAS to be built on your machine for the TOCO tools to work. There's something extra about the build process that doesn't happen during a normal wheel file installation. I'll have to ask a software developer why it has to be built on the PC rather than just installed.

Hey, at the end of the fight against various bugs, I successfully ran the TF Lite model. This is really a great tutorial. But before I sorted out this series of errors, I found that it run in my laptop have only 1.96FPS, it seem don't use the GPU i have in laptop, what should i do? I mean that what should i do to use my GPU in laptop to run the TF lite?

Yeah!! I'm glad you got it working. Can you tell me how you resolved the error related to cl.exe?
It runs very slow on my gaming PC too. The TFLite runtime does NOT use the GPU, so it runs slower than regular TensorFlow does if you have GPU on your PC. The benefit comes when you don't have a GPU: then TFLite runs much faster than regular TensorFlow!
Unfortunately, this means that if you were just hoping to use TFLite to speed up FPS on your laptop, then you'll have to try something else. You could try installing Ubuntu on a separate partition on your laptop, and then using it with the Coral USB Accelerator. (Like I said previously, it won't work with Windows.) Sorry there isn't an easier way to speed up FPS!

Yeah!! I'm glad you got it working. Can you tell me how you resolved the error related to cl.exe?
It runs very slow on my gaming PC too. The TFLite runtime does NOT use the GPU, so it runs slower than regular TensorFlow does if you have GPU on your PC. The benefit comes when you don't have a GPU: then TFLite runs much faster than regular TensorFlow!
Unfortunately, this means that if you were just hoping to use TFLite to speed up FPS on your laptop, then you'll have to try something else. You could try installing Ubuntu on a separate partition on your laptop, and then using it with the Coral USB Accelerator. (It won't work with Windows.) You'll be able to use the same instructions as I wrote for using the Accelerator on the Raspberry Pi (which I'm still working on). Sorry there isn't an easier way to speed up FPS!

hey, let start it. When I got these problems, I started to check all of these steps before build. And I found that may be due to insufficient memory(my RAM only 8G) and insufficient storage(it use 17.8G in my
hard disk) at compile time. So I change the building command.

bazel build --config=opt //tensorflow/tools/pip_package:build_pip_package --local_resources 2048,.5,1.0

you should use --local_resources 2048,.5,1.0 instead of --local_ram_resources=2048, I think it not use in the bazel which version is 0.21.0.
Also, you need to make sure your hard drive is big enough(it use 17.8G in my case, but the whl file I create is only 50MB!! It was amazing.), you can change the bazel output path just like using this:--output_user_root=D:/build/tensorflow.
Just like this:

bazel --output_user_root=D:/build/tensorflow build --config=opt //tensorflow/tools/pip_package:build_pip_package --local_resources 2048,.5,1.0

And it can build with no problem!!!(But it will last a long time, in my case, it last 3 hours to build)
I hope that these experiences and supplements will make this tutorial even better. And also, I want to ask a question that if i want to have higher detect speed(about 30FPS) in win10 using GPU(such like GTX1080), which model should I use? Could you give me some advise?

Closing due to inactivity.


Optimise ChainId epoch format parsing

from_string checks if argument is in epoch format and then calls
chain_version which does it again.  chain_version and with_version use
regex to check if string is in epoch format and then not only parse
the string again but unnecessarily collect dash-separated parts into
a new vector.
Optimise it by providing split_chain_id method which checks the format
and returns individual name and version parts of the id if it is in
epoch format.  Furthermore, don’t use regex which is a heavy machinery
for simply checking if string ends in a positive integer.

PR author checklist:

[ ] Added changelog entry, using unclog.
[x] Added tests.
[x] Linked to GitHub issue.
[x] Updated code comments and documentation (e.g., docs/).
[ ] Tagged one reviewer who will be the one responsible for shepherding this PR.

Reviewer checklist:

[ ] Reviewed Files changed in the GitHub PR explorer.
[ ] Manually tested (in case integration/unit/mock tests are absent).

@plafer, friendly ping.

@mina86 apologies for the delay in getting back to you. We have been looking for an appropriate time to carefully re-examine the details. Specifically, Under ics24_host/identifier/validate.rs there are some functions that could be modified and used for ChainId as well. Wanted to ensure we're on the right track. Though, we still may proceed in a timely manner. Hope you won't be blocked :)
Also, I’ve summarized your points that haven’t been tackled yet, plus some others we came across in issue #761 for our reference and the unclog. Since the new changes would greatly differ from the existing PRs, I'll open a new one. I hope that's okay with you. Let us know if there's anything we may have overlooked.
Again, much appreciated for bringing these up :pray:

Want me to drop this and #698 PRs? I think this PR might still be valid as it addresses some of the issues and refactors code to form where further changes will be easier to make.

Closing this, as we ended up fixing the ChainId issues all at once in #762, given our current bandwidth and priorities. Really appreciate your contribution :pray:


Parsing of comments and options

As mentioned here thanks for a really useful library - it's working well enough for me, but I've noticed some errors that (currently) don't affect my usage. I'd be happy to raise a PR but might not get around to it in the next few days.
Extending this example from the docs:
from proto_schema_parser.parser import Parser

text = """
syntax = "proto3";

message SearchRequest {
  string query = 1;
  int32 page_number = 2;
  int32 result_per_page = 3;
}

service SearchService {
    // Do the search
    rpc Search(SearchRequest) returns (SearchResponse) {
        option (google.api.http) = {
          // some comment about the option
          get: "/v1/search/{query}"
        };
    }
}

"""

result = Parser().parse(text)
print(result)

A few different problems emerge in the stdout output:
line 11:4 extraneous input '// Do the search' expecting {'option', 'rpc', ';', '}'}
line 14:10 mismatched input '// some comment about the option' expecting '}'
line 15:10 extraneous input 'get' expecting {<EOF>, LINE_COMMENT, BLOCK_COMMENT, 'import', 'package', 'option', 'enum', 'message', 'extend', 'service', ';'}
line 17:4 extraneous input '}' expecting {<EOF>, LINE_COMMENT, BLOCK_COMMENT, 'import', 'package', 'option', 'enum', 'message', 'extend', 'service', ';'}
File(syntax='proto3', file_elements=[Message(name='SearchRequest', elements=[Field(name='query', number=1, type='string', cardinality=None, options=[]), Field(name='page_number', number=2, type='int32', cardinality=None, options=[]), Field(name='result_per_page', number=3, type='int32', cardinality=None, options=[])]), Service(name='SearchService', elements=[Method(name='Search', input_type=MessageType(type='SearchRequest', stream=False), output_type=MessageType(type='SearchResponse', stream=False), elements=[Option(name='(google.api.http)', value='{')])]), Comment(text='// some comment about the option'), None])

Comments inside of a Service element don't seem to be expected
I think parameters of an option are not supported and/or the comment is interfering with the parsing

I hope this is useful, and if you'd prefer that I raise a PR please let me know!
Thanks

A PR would be greatly appreciated. I merged the previous comment support PRs optimistically, knowing they were incomplete. Any help you can provide from additional PRs would be much appreciated!

@rnorth checking in: any chance you have time for a PR?

@criccomini I'm very sorry - no, I haven't had time or focus to do it - apologies.

Hi @criccomini,
This library is really useful, I was wondering if there's a chance to get a fix for this issue.
Let me know if you can. Thanks!

Fixed and published as 1.3.6
https://pypi.org/project/proto-schema-parser/1.3.6/
@rnorth @dbottai

Fixed and published as 1.3.6
https://pypi.org/project/proto-schema-parser/1.3.6/
@rnorth @dbottai

Thank you @criccomini! You're the best.


ARROW-4971: [Go] Add type equality test function

Hello,
In the quest for adding support for array comparison (equality) I just added type comparison.
For the moment it considers metadata (only applies to STRUCT type) in the comparison. In the C++ implementation they have a flag to ignore metadata. Do you think we should have it too?
Feel free to give me your feedback!
A

Can you open a JIRA issue for this?

We already have ARROW-3040 though the scope is larger than this PR.
Should I create an issue for this specific PR or continue the work within this PR?

You can create sub tasks which create new JIRA numbers

I added a flag to allow for ignoring metadata during comparison.
PTAL
@sbinet @stuartcarnie

Should be good now!

Done

@sbinet it looks good to me, if there is likely to only be one option for equality checks, I might have considered two APIs to distinguish TypeEquals from a deeper equals, but I don't feel strongly enough about it to suggest a change.
LGTM 👍

you have a point about TypeEquals, at this point in time.
but I think we'll manage to re-use the func-opt for other top-level comparison functions (like ScalarEqual or ArrayEqual?)

I'll wait for after 0.13 to merge this in, though. (unless somebody feels strongly about it.)

There's no need to wait until after the release to merge (since we'll rebase master)


Long term grinding protection - first draft

Proposal for plot filter removal to address long term grinding protection.

I can see a change in the plot filter reduction schedule as a specific type of mitigation, however I think this is ultimately the wrong path. I would like to voice that I DO feel a change is needed from what we are seeing happen in the compressed ecosystem to address the composed balance of plotted netspace, rewards, and most importantly the security of the chain.
The levelers that at the time were available to be pulled to provide ongoing security of the chain for CHIP 12 addressed what at the time seemed like a specific case around GH. We have a very different competing product to GH out now and indeed its impacts on NC have been dramatic for Chia. I think reassessing the levers pulled from a K minimum size need to be reevaluated. To be clear I am suggesting a change to the minimum K size is something that should be on the table. There are a wide variety of benefits that approach could have as well as a seperate set of challenges.
If you feel that path is too divergent vs what you have proposed here let me know and I can start work on a seperate CHIP. It may be a good idea to do that regardless talks around impactful changes to farmers to elicit community sentiment at the same time.

An accelerated timeline is perhaps justifiable with recent development, but terminating at a filter of 1 instead of 32 goes too far.
It's linearly punitive to farmers whilst having diminishing returns against plot grinding. Once the threshold of grinding being economically unviable is passed the downside risk is a reduction in honest nodes and netspace with no material upside vs plot grinding.
Flash may well become the dominant storage within your referenced timelines (late 2020s) at the enterprise level based on new prices. I don't see it happening for home users and second hand markets anywhere close to that quickly, but that's my opinion.
You also mention 22TB drives being viable with filter 1 using uncompressed plots - but 22TBs are available today, and expected to reach much higher capacity over the next several years. I don't understand the security rationale for pushing high density HDDs out of honest netspace - doesn't that make grinding attempts more attractive not less?
Obsoleting HDDs prematurely also makes things like 'one click farming' and having millions of home users much more challenging aspirations. Whilst well intentioned, filter going to 1 seems it may hurt overall security rather than help it.

It's linearly punitive to farmers whilst having diminishing returns against plot grinding. Once the threshold of grinding being economically unviable is passed the downside risk is a reduction in honest nodes and netspace with no material upside vs plot grinding.

This is a great point! I hadn't thought about the diminishing gains at lower filter levels.

Flash may well become the dominant storage within your referenced timelines (late 2020s) at the enterprise level based on new prices. I don't see it happening for home users and second hand markets anywhere close to that quickly, but that's my opinion.

I think we'll see it in waves as it may become an economical choice for high electricity rate regions.

You also mention 22TB drives being viable with filter 1 using uncompressed plots - but 22TBs are available today, and expected to reach much higher capacity over the next several years. I don't understand the security rationale for pushing high density HDDs out of honest netspace - doesn't that make grinding attempts more attractive not less?

Pushing out high density HDDs is not the goal but highlighted as a detrimental impact of this approach that will need to be considered. Stopping at a lower filter level would alleviate it.

Obsoleting HDDs prematurely also makes things like 'one click farming' and having millions of home users much more challenging aspirations. Whilst well intentioned, filter going to 1 seems it may hurt overall security rather than help it.

I'd be curious what spare storage of home users in the future looks like -- even today overprovisioned storage is more likely to be on flash storage than hard drives.
Thank you for the thoughtful response, these are great call outs!

The levelers that at the time were available to be pulled to provide ongoing security of the chain for CHIP 12 addressed what at the time seemed like a specific case around GH. We have a very different competing product to GH out now and indeed its impacts on NC have been dramatic for Chia. I think reassessing the levers pulled from a K minimum size need to be reevaluated. To be clear I am suggesting a change to the minimum K size is something that should be on the table. There are a wide variety of benefits that approach could have as well as a seperate set of challenges.

Changing minimum K-size is certainly on the table but I personally would like to consider it in the lens of preventing plot grinding. I don't see compressed farming as a problem unto itself but rather the specific pooling implementations of it which are separately addressed in CHIP-0022.
If a higher K-size is capable of exponentially increasing the costs of plot grinding then it could be worth the trade off of replotted netspace. I'm not convinced that it does though. Renting GPU clusters is as easy as ever (though maybe not currently cheap). I'd defer to someone that understands the requirements of higher k-size plotting to chime in. My fear is higher k-size makes Chia farming out of reach of common users.

If you feel that path is too divergent vs what you have proposed here let me know and I can start work on a seperate CHIP. It may be a good idea to do that regardless. Involving farmers in talks around impactful changes to farmers and eliciting community sentiment at the same time sounds like a good approach.

Great point about eliciting more input from the farmers that will be impacted. A few vocal users in GitHub should not be making this decision for 90K+ farmers.

An accelerated timeline is perhaps justifiable with recent development, but terminating at a filter of 1 instead of 32 goes too far.
It's linearly punitive to farmers whilst having diminishing returns against plot grinding. Once the threshold of grinding being economically unviable is passed the downside risk is a reduction in honest nodes and netspace with no material upside vs plot grinding.
Flash may well become the dominant storage within your referenced timelines (late 2020s) at the enterprise level based on new prices. I don't see it happening for home users and second hand markets anywhere close to that quickly, but that's my opinion.
You also mention 22TB drives being viable with filter 1 using uncompressed plots - but 22TBs are available today, and expected to reach much higher capacity over the next several years. I don't understand the security rationale for pushing high density HDDs out of honest netspace - doesn't that make grinding attempts more attractive not less?
Obsoleting HDDs prematurely also makes things like 'one click farming' and having millions of home users much more challenging aspirations. Whilst well intentioned, filter going to 1 seems it may hurt overall security rather than help it.

I can't speak to the technical feasibility of the examples mentioned but some way of "converting" existing plots feels like a necessity for any proposal that forces a replot of 97%+ netspace such as k-size increase or plot format change.

During the research for CHIP-12 and CHIP-13, we spent considerable time discussing how aggressive the filter reduction needs to be. The economic model has remained constant, but now we have real-time data on GPU rental prices from runpod.io, vast.ai, etc. and some basic Bladebit plot times on an H100 (which is very important b/c it is a PCIe 5.0 card). I have updated the rental model to account for prices. The threat model was originally developed around commodity gaming cards that are more easily obtainable and have lower costs.
https://docs.google.com/spreadsheets/d/16K4Ki846npprN2q5OLGCbusCPX4Ci2Hlk_vMdrY2I4g/edit?usp=sharing
I have measured a 30 second plot with 15 second phase one, a single H100. If the table 7 finalization is removed, which is not needed for grinding, that shaves off another few seconds. Today plot grinding could be run on a single card, but it would be incredibly stupid as those instances are renting for around $4/hr.
To prevent plot grinding, the profitability needs to be some multiple of honest farming profitability to ensure it doesn't become viable during short-term price volatility. When the XCH price goes up, we want to ensure adequate time for honest farmers to get the space online. CHIP-13 does this and gives a tremendous amount of room. 5x is more than enough, meaning if the price increases by 5x and plot grinding still aren't profitable, it will never happen because the honest space will beat it out and increase the Netspace,
I would, however, like to see all VRAM POC of Bladebit, as cards with a tremendous amount of high-speed memory are being developed for AI training. H200 will have 141GB and 4.8TB/s memory bandwidth, but actually less FP32 performance than a 4090. This is meaningful because the Chia proof of space is a "memory bandwidth bound" workload.
Surprisingly, plot compression has helped defend against plot grinding due to the higher effective Netspace.
To reiterate what was mentioned above, although I believe SSDs transition will happen even sooner than most industry analysts, I don't think the Chia protocol should restrict hard drives from being viable for farming.
To summarize, I recommend getting CHIP-13 or replacement back online immediately. This will be more than enough to deter plot grinding during short-term XCH price volatility, and god forbid, the next bull market.

Thanks for this excellent analysis!

Thank you for chiming in with expertise and data, @jmhands!

To reiterate what was mentioned above, although I believe SSDs transition will happen even sooner than most industry analysts, I don't think the Chia protocol should restrict hard drives from being viable for farming.

At what filter size is HDD farming not viable? I thought plot filter removal would just barely make the large capacity slow drives not viable. (e.g. 20TB 5400rpm was the example that was at the cusp IIRC).

Thank you all for the feedback and discussions (both here and other channels). I am withdrawing this CHIP and will proposed a modified version after the first plot filter reduction to observe how netspace and farmer experience responds.


More misc style fices

More style fixes for newly added bits. Mainly jumplinks. Note I changed the named of the download icon as it's also used for this.

Jumplinks vanished from figma, so I may update these styles once Joe re-adds it.


(AzureCXP) fix the permissions description

(AzureCXP) fix the permissions parameter's description
All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

@seanmcc-msft @tamram All the corrections have been done. Please review this PR and approve it once you get a chance. Also check if this can be merged with the main branch.

@seanmcc-msft @tamram could you please merge this PR with the main branch


Feature/readme updates

Added link to License under License Content
Separated Markdown URL with comment for shield/link
Added Author section, and added table of content entry for Author

@othneildrew  First of all, I use your README template for my personal projects, and I think it's really great.
I wanted to suggest few updates on it, which could enhance it a bit.
Best regards,
Alex


Disassembly station item duplication

It still seems to be possible to duplicate items using the disassembly station (using Forgero 0.10.9-rc1+1.19.2).
After placing something into the left-hand slot in the disassembly station, and removing an item from the grid on the right, the item disappears from the left-hand slot.  However, if you then click the empty slot, everything reappears in the grid on the right and can be removed again, allowing for infinite duplication.
As an additional note to this, stacks of items in the left-hand slot behave oddly when removing items from the grid, as more than just one disappears from the stack on the left.

Nice catch! I'll try to recreate it so I can fix these issues


restyle whole site

Thanks for doing this - I think it's a huge improvement across the board. I just tested it out and have a few notes:
The compiler dropdown doesn't really look like a dropdown anymore (it doesn't appear obvious that you can change it). I like the way it looks, but maybe some indicator on the right side that it can be clicked or expanded would be helpful.
Only the very right edge of the diff/code separator bar seems draggable now, where it used to be the whole thing.
And lastly, there seems to be some bug regarding when a new compile request is sent through. I can enter text and wait ages without it doing one, and then I have to trigger it manually. It appears a compile call is going out right after any inital keystroke, and then subsequent keystrokes are not triggering one, even after a delay. I'd suggest we wait until some time has passed before the last keystroke before sending out a call, such as 500 ms or something. That and if we're not waiting for a compile request to return and we know the contents of the buffer don't match the diff, we should probably do like a sync-up compile request after some delay. Idk, not sure exactly what's going on there...

Oh, and one last thing: on the index page, the "create a scratch" text should probably have some left padding since it's pushed right up against the window kind of awkwardly. We'll need to design a proper homepage at some point as well but that's for later

The compile thing should be fixed now - could you test it @ethteck?


inbound: webhooks on Return files

PayGate Version: v0.8.0
What were you trying to do?
When PayGate processes an inbound file which has Return batches there should be a way to notify an external application. This allows extensibility of what PayGate can offer right now.
What did you expect to see?
Offer a webhook for notifying an external application.
Note: This builds off of work in https://github.com/moov-io/paygate/issues/523

I can see us offering a file config where we can specify targets to notify. The payload would be an ACH file's JSON representation. PayGate would retry sending this until an 200 OK is returned by the receiving service.
inbound:
  interval: <duration> # moved from odfi.inbound
  webhooks:
    return:
      - target: <address>
        authToken: <secret>
        [ insecure: <boolean> ]

Would an admin endpoint for registering a webhook be useful? I can see us supporting something like this:
$ curl -X POST http://paygate:9092/webhooks/return
{
  "target": "<address>",
  "authToken": "<secret>",
  "insecure": false
}

Sometimes some folks will want to have multiple webhooks where you can direct different event types to different URLs. May want to consider this.
Another thing that might be really cool would be the ability to subscribe to one or more specific transactions. ie. I really only care about returns to these X transactions.

Yep. I added a filters object where we can limit what the webhook fires on, so eventTypes, transferIDs, etc.. We can extend those filters going forward.


Update netty-buffer, netty-codec-http to 4.1.63.Final

Updates

io.netty:netty-buffer
io.netty:netty-codec-http

from 4.1.60.Final to 4.1.63.Final.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.netty" } ]

labels: library-update

Goodness, they've been busy.  0.21.

#4695


any eta on udp static routing?

Hello. first of all thanks for contributing your time , knowledge and energy to make this project. as someone who lives in a third world country that uses this project to bypass internet censoring I'm really thankful for your work. I use wireproxy for my v2ray vpn server and the problem is that I can't make voice or video calls due wireproxy not supporting udp. I know it's a "me" problem but I want to know if theres a plan or an upcoming update about this subject. again, thank you so much.

I also need UDP support because voice communication does not work in Discord (web).

At this point why use wireproxy and not just a wireguard client?

Because the WG client tunnels all traffic in the system, there is no way to choose which application will work through the VPN and which directly, as can be done in the Android client.

Because the WG client tunnels all traffic in the system, there is no way to choose which application will work through the VPN and which directly, as can be done in the Android client.

This is simply not true.
Assign your wg configuration to a specific routing table (one line of configuration) and 🎉 it doesn't affect anything unless you specifically make it target this table.
Then launch the apps you want routed via wg in a cgroup that has this table assigned to it.


Switch workspace restricted settings to use indicators

Ref https://github.com/microsoft/vscode/issues/157564
Current issues:

[x] When changing a workspace restricted setting in the Settings editor, the value is written once to the JSON file, but then the value isn't refreshed properly

Fixed the bug mentioned in the issue and also updated the PR with some changes (feedback). But IMO the following visual representation is too subtle to say that the value is not getting applied.

LGTM, thanks again for the configuration changes!
My current plan is to squash and merge in the change and get a few rounds of feedback.
If anything big comes up, I can revert the squash commit.


[FLINK-12021] Deploy execution in topological sorted order

What is the purpose of the change
Due to changes how the slot futures are completed and due to the fact that the
ResultConjunctFuture does not maintain the order in which the futures were specified,
it could happen that executions were not deployed in topological order. This commit
fixes this problem by changing the ResultConjunctFuture so that it maintains the order
of the specified futures in its result collection.
This also fixes a performance regression when deploying tasks since deploying tasks in non-topological order can lead to additional result partition lookups.
Verifying this change

Added ExecutionGraphDeploymentTest#testExecutionGraphIsDeployedInTopologicalOrder and ConjunctFutureTest#testConjunctFutureCompletion.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Thanks for the review @zentol and @shuai-xu. Merging this PR.


forbidden after about 6 hours or 3.7 gig filesize

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like this: [x])
Use the Preview tab to see what your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2018.10.05. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x ] I've verified and I assure that I'm running youtube-dl 2018.10.05

it is the latest because i installed on october 20 2018 on an instance of osx 10.12 on vmware fusion.
Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[x] Other

i am saying other because i am not sure if it is a bug or something on youtube so if it is a bug you can upgrade the request to bug
after downloading a live stream https://www.youtube.com/watch?v=4PRCnWDhaxI overnight
this morning i got up to a 403 forbidden  sorry i did not capture the exact errors since i got a great run.
i renamed the file downloaded during the overnight so it would not be overwritten by a retest.
i retested and no forbidden errors so youtube did not ban me.
i looked at the file size and it was like 3.7 gig so i thought it was a file size limit of 4 gig on the mp4 container (suggestion  if it is a file size limit it would be nice if youtube-dl could split or remux into another container like mkv witch does not have a size limit (i have seen bluray rips run like 50 gig in mkv)
then i looked at the length of the file in player and it was just 30 seconds of the 6 hour limit of quicktime so maybe it is a time limit (again splitting or a different container like mkv).
if youtube is seeing the user agent and is banning youtube rippers  you may want to allow us to change the user agent string that is sent to youtube.
The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add the -v flag to your command line you run youtube-dl with (youtube-dl -v <your command line>), copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2018.10.05
[debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
[debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
[debug] Proxy map: {}
...
<end of log>

If the purpose of this issue is a site support request please provide all kinds of example URLs support for which should be included (replace following example URLs by yours):

Single video: https://www.youtube.com/watch?v=BaW_jenozKc
Single video: https://youtu.be/BaW_jenozKc
Playlist: https://www.youtube.com/playlist?list=PL4lCao7KL_QFVb7Iudeipvc2BCavECqzc

Note that youtube-dl does not support sites dedicated to copyright infringement. In order for site support request to be accepted all provided example URLs should not violate any copyrights.

Description of your issue, suggested solution and other information
Explanation of your issue in arbitrary form goes here. Please make sure the description is worded well enough to be understood. Provide as much context and examples as possible.
If work on your issue requires account credentials please provide them or explain how one can obtain them.

update:
here is the error message i get at the end
D9BD1D016F6EBC16FEAD681EFDC8F.7EB68415600C49B5E36DD8B99A5D5DCF32672750/key/dg_yt0/playlist/index.m3u8' for reading
[https @ 0x7fcc6d509fc0] HTTP error 403 Forbidden
[hls,applehttp @ 0x7fcc6d803000] keepalive request failed for 'https://manifest.googlevideo.com/api/manifest/hls_playlist/id/4PRCnWDhaxI.0/itag/96/source/yt_live_broadcast/requiressl/yes/ratebypass/yes/live/1/cmbypass/yes/goi/160/sgoap/gir%3Dyes%3Bitag%3D140/sgovp/gir%3Dyes%3Bitag%3D137/hls_chunk_host/r4---sn-2xouxaxq5u5-5cxs.googlevideo.com/playlist_type/DVR/ei/juPUW-_4Mtm08wSskrTwCg/gcr/us/mm/32/mn/sn-2xouxaxq5u5-5cxs/ms/lv/mv/u/pl/22/dover/11/playlist_duration/30/keepalive/yes/manifest_duration/30/beids/9466588/mt/1540677934/disable_polymer/true/ip/<IP_ADDRESS>/ipbits/0/expire/1540700142/sparams/ip,ipbits,expire,id,itag,source,requiressl,ratebypass,live,cmbypass,goi,sgoap,sgovp,hls_chunk_host,playlist_type,ei,gcr,mm,mn,ms,mv,pl/signature/131870401B9D9BD1D016F6EBC16FEAD681EFDC8F.7EB68415600C49B5E36DD8B99A5D5DCF32672750/key/dg_yt0/playlist/index.m3u8', retrying with new connection: Server returned 403 Forbidden (access denied)
[https @ 0x7fcc6d512ec0] HTTP error 403 Forbidden
[hls,applehttp @ 0x7fcc6d803000] Failed to reload playlist 0
[https @ 0x7fcc6d512ec0] HTTP error 403 Forbidden
[hls,applehttp @ 0x7fcc6d803000] Failed to reload playlist 0
frame=647728 fps= 30 q=-1.0 Lsize= 3877871kB time=05:59:50.98 bitrate=1471.3kbits/s speed=   1x
video:3528594kB audio:337359kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.308282%

Unfortunately, YouTube only keeps stream urls valid for about 6 hours. To overcome this, you will need to repeatedly get new stream urls every 6 hours. I made a script that does this, hopefully it will work for you.
Click here for the script


The "Show in schedule" button on the talk pages refer to CEST time, not UTC as the schedule

As a result, the links don't work as expected.
Note that the hash part of the links does include a reference to "UTC", so it seems the template is wrong.
Example: https://ep2021.europython.eu/talks/5yb9KNo-introduction-to-property-based-testing/

While fixing this, it would be good to add the UTC times to the talk page directly as well.


Improves the README file

Hey! Thank you for the awesome library.
If you don't mind, I would suggest a few improvements to the README of this project to make the usage examples a little more clear. Everything is open to discussion, so don't hesitate to correct or discard these changes.

Awesome! Thank you very much for the revised README file :))


can't call run() method with params from commands migrations.

Description

can't call run() method with params from commands migrations. Fixes #1308
update user guide for migration

Checklist:

[x] Securely signed commits
[x] Component(s) with PHPdocs
[ ] Unit testing, with >80% coverage
[x] User guide updated
[x] Conforms to style guide

@bangbangda I think it will be tidier to use rebase instead of syncing with latest develop, you can do the following step if you already has the commit:

Backup your change commit by create local new temporary branch based on current branch ("command-migrations", for example, named "temp-command-migrations"

git checkout -b temp-command-migrations

Back to develop branch and pull latest changes:

git checkout develop && git pull https://github.com/bcit-ci/CodeIgniter4.git develop

Back to "command-migrations" branch and delete latest 2 commit

git checkout command-migrations && git reset --hard HEAD~2

Cherry pick your commit from "temp-command-migrations" branch

git cherry-pick 43f1e448ee86a85acdeb522f6429ac5712b94557

Rebase against develop

git rebase develop

On this stage, you may got conflict, you can fix the conflict with steps:
a. Fix the conflict ( don't add new commit for fixing its conflict only )
b. Run git add .
git add .

c. Re-continue git rebase :
git rebase --continue

Finally, you need to force-push to your fork repository:

git push --force origin command-migrations

Now, you're save to delete temporary branch

git branch -D temp-command-migrations

I created a blog post for it https://samsonasik.wordpress.com/2015/09/16/practical-git-4-rebasing-conflicted-task-branch-against-primary-branch/

Thank you very much. I understand and will try it. @samsonasik


Feature/convert flask restful

As we decided to use flask_restful package instead of flask, this PR propose the required changes such as:

dynamic urls
multiple endpoints (more fanout)

It closes #3 , #36

Here is the logs when running on real k8s cluster:
 % kubectl logs service-1-58c5d8d7b5-trb4z
[2022-03-15 22:27:13 +0000] [9] [INFO] Starting gunicorn 20.1.0
[2022-03-15 22:27:13 +0000] [9] [INFO] Listening at: http://<IP_ADDRESS>:5000 (9)
[2022-03-15 22:27:13 +0000] [9] [INFO] Using worker: sync
[2022-03-15 22:27:13 +0000] [11] [INFO] Booting worker with pid: 11
[2022-03-15 22:27:13 +0000] [12] [INFO] Booting worker with pid: 12


Can't read incoming messages in pytests

Hi, i'm using aiomqtt to run some test with pytests on Windows.
I've managed to create, connect to my client and also subscribe publish to some topics.
The problem is I can't read any messages from my client. The loop 'async for' get stuck.
async with Client(hostname=broker_adress, port = broker_port, tls_context=tls_context, logger=logger) as mqtt_client:
  for device in devices:
    await mqtt_client.subscribe(f"mqtt/things/{device}/uplink")
  topic = f"mqtt/things/{device}/downlink"
  message = "some message"
  await mqtt_client.publish(topic=topic, payload=message)

  async for message in mqtt_client.messages: # Stuck here
    print(message.payload) # Never called

I make sure that my asyncio loop is a SelectorEventLoop, I mark my async test function with @pytest.mark.asyncio
I know that i received some messages, the function _messages from client class call yield task.result().
DEBUG    aiomqtt:client.py:3254 Sending PUBLISH (d0, q0, r0, m7), 'b'mqtt/things/E41A1D0000000366/downlink'', ... (268 bytes)
DEBUG    aiomqtt:client.py:473 _messages yield task.result()
DEBUG    aiomqtt:client.py:473 _messages yield task.result()
DEBUG    aiomqtt:client.py:473 _messages yield task.result()

I use python 3.11.4, asyncio-0.21.0 , aiomqtt 2.1.0, pytest 7.3.2 and paho-mqtt 2.0.0
Any suggestion why, I have this behaviour ?

Hi Waganama, thanks for opening this issue. :+1: Let me have a look. :)
It looks like you subscribe to these topics:
f"mqtt/things/{device}/uplink"

but you post messages to this topic (where device is the last entry in devices):
f"mqtt/things/{device}/downlink"

Since the topics don't match, you'll never receive a message. That explains why it gets "stuck": There are no messages in wait.
As a test, try to subscribe to everything: "mqtt/things/#". See if that works. :)

Thank you for your response.
I have two topics, one to send downlink (client->server) and one to received uplink (server->client)
I still tried to change the topic for my subscribtion, without success.
It looks like that calling yield task.result() doesn't do anything when running with pytest.
I tried to run the same code above without pytest, and it worked perfectly, I can read my message.

Thanks for the response. This is really difficult to debug without the full code. Do you have self-sufficient example code that reproduces the problem?

I reduce the test part to reproduce the issue only. It is a very simple test.
Unfortunatly I can't share connection information and i don't know if there are mqtt server dedicated for test.
I hope will have everything to debug.
source.zip

After research, i found out i can use the server test.mosquitto.org for my test. I also have the same issue withe the following code using pytest.
Output :
configfile: pytest.ini
plugins: anyio-3.7.0, asyncio-0.21.0
asyncio: mode=Mode.AUTO
collected 2 items

tests/test_mosquitto.py::TestMosquitto::test_mosquitto[asyncio]
--------------------------------------------------- live log setup ----------------------------------------------------
DEBUG    asyncio:selector_events.py:54 Using selector: SelectSelector
---------------------------------------------------- live log call ----------------------------------------------------
INFO     root:test_mosquitto.py:37 Here
DEBUG    aiomqtt:client.py:3254 Sending CONNECT (u0, p0, wr0, wq0, wf0, c1, k60) client_id=b''
DEBUG    aiomqtt:client.py:3254 Received CONNACK (0, 0)
DEBUG    aiomqtt:client.py:3254 Sending SUBSCRIBE (d0, m1) [(b'win32_3.11/tests/aiomqtt/test_client_unsubscribe/1', 0)]
DEBUG    aiomqtt:client.py:3254 Received SUBACK
DEBUG    aiomqtt:client.py:3254 Sending PUBLISH (d0, q0, r0, m2), 'b'win32_3.11/tests/aiomqtt/test_client_unsubscribe/1'', ... (12 bytes)
DEBUG    aiomqtt:client.py:463 _messages _queue size after get 0
DEBUG    aiomqtt:client.py:3254 Received PUBLISH (d0, q0, r0, m0), 'win32_3.11/tests/aiomqtt/test_client_unsubscribe/1', ...  (12 bytes)
DEBUG    aiomqtt:client.py:618 _on_message _queue size after put 1
DEBUG    aiomqtt:client.py:474 _messages yield task.result().topic : win32_3.11/tests/aiomqtt/test_client_unsubscribe/1
DEBUG    aiomqtt:client.py:463 _messages _queue size after get 0

source.zip

I have additionnal informations, if i have different behaviour according how I run my test :

python -m pytest tests\test_mosquitto.py -> No message is printed after the async for loop
python -m pytest --capture=no tests\test_mosquitto.py -> Message are printed

I don't know why the capture=no has effect.

It turned out that everything was fine, pytest doesn't print by default.
I'm sorry for the inconvenience

No problem. 😄 Glad that it worked out in the end!


Unable to extend cell classes (NumericCell, StringCell etc)

I'm working on a project that requires me to extend the NumericCell class but I'm unable to do so because the class has been coded as a final class. Please can this be changed as I'm now unable to write in the necessary functionality which is a problem. Considering that the package is open source I think it makes sense for developers to be able to extend the classes. This also has been marked as a problem by another developer: see https://github.com/openspout/openspout/issues/255
Please can you consider allowing the classes to be extended. Many thanks!

Replied in https://github.com/openspout/openspout/issues/255#issuecomment-2415977630


Conflict with Sysem.Diagnostic.EventLog

Changed my current Class-Lib project to "netstandard2.0".
Unfortunately this resulted in getting multiple build errors saying that types exists in both Namespaces "Sysem.Diagnostic.EventLog" and "Microsoft.Win32.TaskScheduler".
Error	CS0433
The type 'EventLogSession' exists in both 'Microsoft.Win32.TaskScheduler, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=e25603a88b3aa7da' and 'System.Diagnostics.EventLog, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
How can this beeing resolved?

I just created a .NET Std 2.0 class library and add the TaskScheduler 2.9.0 NuGet package. I created the following method in the library and it builds without any errors. Could you need to clean up the NuGet packages and build directories?
using System;
using System.Diagnostics.Eventing.Reader;
using System.Threading;
using System.Threading.Tasks;
using Microsoft.Win32.TaskScheduler;

namespace TestTSwithNETStd2
{
	public static class Class1
	{
		public static async System.Threading.Tasks.Task WatchEventsAsync(ManualResetEvent stopEvent, Action<string> onEvent)
		{
			await System.Threading.Tasks.Task.Run(() =>
			{
				using (var w = new TaskEventWatcher())
				{
					w.EventRecorded += (s,e) => onEvent?.Invoke($"{e.TaskEvent.EventRecord.TaskDisplayName}");
					w.Enabled = true;
					stopEvent.WaitOne();
				}
			});
			var ses = new EventLogSession();
		}
	}
}

I just created a .NET Std 2.0 class library and add the TaskScheduler 2.9.0 NuGet package. I created the following method in the library and it builds without any errors. Could you need to clean up the NuGet packages and build directories?
using System;
using System.Diagnostics.Eventing.Reader;
using System.Threading;
using System.Threading.Tasks;
using Microsoft.Win32.TaskScheduler;

namespace TestTSwithNETStd2
{
	public static class Class1
	{
		public static async System.Threading.Tasks.Task WatchEventsAsync(ManualResetEvent stopEvent, Action<string> onEvent)
		{
			await System.Threading.Tasks.Task.Run(() =>
			{
				using (var w = new TaskEventWatcher())
				{
					w.EventRecorded += (s,e) => onEvent?.Invoke($"{e.TaskEvent.EventRecord.TaskDisplayName}");
					w.Enabled = true;
					stopEvent.WaitOne();
				}
			});
			var ses = new EventLogSession();
		}
	}
}

I cleaned already everything even deleted the obj and bin folders manually and also closed VS and rebooted my machine. Did not help.
The thing is I have to add the package-ref "System.Diagnostics.EventLog" itself and that conflicts somehow with the builtin package of TaskScheduler.

I cleaned already everything even deleted the obj and bin folders manually and also closed VS and rebooted my machine. Did not help.
The thing is I have to add the package-ref "System.Diagnostics.EventLog" itself and that conflicts somehow with the builtin package of TaskScheduler.

Thanks. That helps a lot. I am using System.Diagnostics.EventLog for .NET Core and .NET 5.0, but not .NET Std 2.0. Let me see if I can do that for the next release.

Thanks. That helps a lot. I am using System.Diagnostics.EventLog for .NET Core and .NET 5.0, but not .NET Std 2.0. Let me see if I can do that for the next release.

I believe this is fixed in the most recent commit and will release in the next day or so with 2.9.1.

I believe this is fixed in the most recent commit and will release in the next day or so with 2.9.1.


Rename drag-features example to custom-interactions

We now have a Translate interaction for dragging features, and a translate-features example. So this PR suggests renaming the drag-features example to custom-interactions, since this example is really about showing how to create custom interactions.

+1


[DO NOT MERGE] Try to fix flaky test

What changes are proposed in this pull request?
Repro and fix flakiness in ConcurrentFileInStreamIntegrationTest#FileInStreamConcurrency

symptom
Error: 6.465 [ERROR] alluxio.client.fs.concurrent.ConcurrentFileInStreamIntegrationTest.FileInStreamConcurrency  Time elapsed: 25.871 s  <<< FAILURE!
java.lang.AssertionError: Failed with exception(s) [
java.lang.RuntimeException: java.io.IOException: Failed to connect to remote block worker: GrpcServerAddress{HostName=3aab1f03f409, SocketAddress=3aab1f03f409/<IP_ADDRESS>:46063},
java.lang.RuntimeException: java.io.IOException: Failed to connect to remote block worker: GrpcServerAddress{HostName=3aab1f03f409, SocketAddress=3aab1f03f409/<IP_ADDRESS>:46063},
java.lang.RuntimeException: java.io.IOException: Failed to connect to remote block worker: GrpcServerAddress{HostName=3aab1f03f409, SocketAddress=3aab1f03f409/<IP_ADDRESS>:46063},
... (many similar exceptions}]
	at org.junit.Assert.fail(Assert.java:89)
	at org.junit.Assert.assertTrue(Assert.java:42)
	at alluxio.test.util.ConcurrencyUtils.assertConcurrent(ConcurrencyUtils.java:72)
	at alluxio.client.fs.concurrent.ConcurrentFileInStreamIntegrationTest.FileInStreamConcurrency(ConcurrentFileInStreamIntegrationTest.java:69)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:288)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:282)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.lang.Thread.run(Thread.java:834)

Investigation

Make sLocalAlluxioClusterResource from a static variable (Singleton) to a member variable to eliminate the possibility to be affected by state mutation across-tests: didn't solve this issue

Add Thread.sleep to Before method to give enough time for worker to be ready: didn't solve this issue, actually this turned to be unnecessary as  waiting for worker to be ready is part of cluster setup

Add a check to read files after assertion exception is thrown. It turned out working. This indicates that Worker is not lost

    try {
      ConcurrencyUtils.assertConcurrent(threads, 100);
    } catch (AssertionError error) {
      len = 0;
      try (FileInStream stream = mFileSystem.openFile(uniqPath)) {
        while (stream.read() != -1) {
          len++;
        }
      }
      assertEquals(BLOCK_SIZE * 2, len);
      throw new AssertionError("Failed concurrency test but the block worker is okay: " + error,
          error);
    }

Set PropertyKey.NETWORK_CONNECTION_AUTH_TIMEOUT locally to be very small value
https://github.com/Alluxio/alluxio/blob/358004faf4746451c58646a05fbeb06bd11f8f36/core/common/src/test/java/alluxio/ConfigurationTestUtils.java#L94
and able to reproduce similar issue


IndentLinesEnable and IndentLinesToggle does not work.

I'm on vim 7.3 and using vim via iterm2.
here's my vimrc:
set nocompatible
filetype on
colorscheme molokai
set number
syntax on
set hlsearch
set tabstop=2 shiftwidth=2 expandtab
set nowrap

" map jj to esc
imap jj <Esc>

" set the runtime path to include Vundle and initialize
set rtp+=~/.vim/bundle/Vundle.vim
call vundle#begin()
" let Vundle manage Vundle, required
Plugin 'gmarik/Vundle.vim'

" Setup fuzzy search
set rtp+=~/.fzf
nmap f :FZF<Enter>

" multi-cursor
Plugin 'terryma/vim-multiple-cursors'

" emmet plugin for css / html
Plugin 'mattn/emmet-vim'

" tab indentation lines
Plugin 'Yggdroot/indentLine'
let g:indentLine_loaded = 0

" All of your Plugins must be added before the following line
call vundle#end()            " required
filetype plugin indent on    " required

I've ran :BundleInstall but when I enter IndentLinesEnable or IndentLinesToggle vim complains E492: Not an editor command: IndentLinesToggle

Remove let g:indentLine_loaded = 0

ah, I feel silly now, thanks!


Fix typo, onCommited -> onCommitted #183

Fix typo mentioned in issue #183, the text for the link should say webNavigation.onCommitted instead of webNavigation.onCommited. The link it links is spelled correctly and has two Ts.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions/api-support/supported-apis.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Thank you @charlottetan !


Generated openapi.json is not readable (needs newlines and indentation)

implemented https://github.com/open-traffic-generator/models/commit/e45e716d40defb5d25d90ff0591d70f748685cdf


Integrate maps of permafrost change

After implementing the classifications, look to implement some delta maps for permafrost.  (More discussion needed).

Refine the threshold for showing different colormaps that indicate which case (permafrost vs. none vs. uncertain) exists for that instance...but it seems we should keep pursuing these!

Implemented + will refine in further tickets.


adapt to the reg-tags

reg-tags has been modified to support any registry, adapt so as to minimise building attempts at the GHCR

Fixed by 46da819383c0988dd286d883b0962c772934999e


Azure Login Experience

User story
As a bot creator,
I want to sign in to an existing or create a new Azure account from within the Composer UI,
so that I can easily perform Azure-related operations without needing to retrieve an access token from an external source, such as through the Azure CLI.
Description

Within both the Virtual Assistant creation wizard, as well as when initiated from the Publish view within the UI, an Azure sign-in modal should be presented to users to allow them to sign in with their Azure credentials. This should be enabled using standard functionality offered through the Azure JS libraries.
Until such a point that the necessary AAD application to enable login has been set up, we should use a stub modal that enables users to manually enter an access token as acquired from the CLI.
Acceptance criteria

[ ] TBD

See #3384

Closing as duplicate.


Chinese fonts overlap

hyper version: 1.0.0
windows version: Windows 10 1607

Hi there @JonasGao. I believe you need to report this issue to the main Hyper repo, which can be found here: https://github.com/zeit/hyper
This repo isn't the main repo where issues for Hyper are tracked and resolved.
Let me know if I can help at all with getting an issue in on the application's repo!

Oh~ thank you very much (=ﾟωﾟ)ﾉ