Re-enable creation of function apps

The following  issues were closed with the reasoning that the functionality has been moved to azure-cli:

https://github.com/Azure/azure-functions-cli/issues/75
https://github.com/Azure/azure-functions-cli/issues/50

However, azure cli does not contain the expected functionality: https://github.com/Azure/azure-cli/issues/2352
Thus: There is currently no way to create azure function apps using the command line. This tool was the only way. Now there is none. You removed it. Please re-add it.

@lindydonna

@Zazcallabah Unfortunately you'll have to wait for the functionality in the Azure CLI, which is coming soon. We don't want to add it to the Azure Functions CLI now, since we'd remove it as soon as it was part of the Azure CLI.
For now, you can create a function app by using the az appservice web commands and manually setting up the storage account connection string. The required properties are listed here: https://github.com/Azure/azure-quickstart-templates/blob/master/101-function-app-create-dynamic/azuredeploy.json#L62

Closing in favor of https://github.com/Azure/azure-cli/issues/2352


[HOLD for payment 2023-06-21] [$1000] Message to change the primary login to email is not appearing if the 2/5 steps of bank account set up is completed

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the app
Login with phone number user
Open any workspace
Open connect bank account and observe that it displays the message to change the primary login as a valid email
If not already added, add secondary email account
Make email account as default
Open workspace opened in step 3
Open connect bank account
Click on connect manually and fill in details in first 2 steps and quit in the step 3 (personal information page)
Again change default contact to phone number
Open connect bank account

Expected Result:
When primary login is phone number, app should  display message to change the primary login on click of connect bank account
Actual Result:
When primary login is phone number and app has previous setup for connect bank account, app  does not display the message to change the primary login
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.3.22
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/da89933a-aeeb-43af-84cb-398f4aa58842
https://github.com/Expensify/App/assets/43996225/0920ebc0-0032-40d6-ad59-2abe9433959a
Expensify/Expensify Issue URL:
Issue reported by: @dhanashree-sawant
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684855894250829
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01dbdf57ee5b67dd8a
Upwork Job ID:<PHONE_NUMBER>510938112
Last Price Increase: 2023-06-05

Reviewing

This is a bit difficult to follow, confirming bug behavior in Slack

Okay so essentially what we're saying here is if your primary login is a phone number you shouldn’t be able to enter the connect bank account flow at all before adjusting to an email primary login, sure.

Thank you for pointed out @greg-schroeder
@allroundexperts proposal here - https://github.com/Expensify/App/issues/20072#issuecomment-1575214353 looks good.
🎀👀🎀
C+ Reviewed
cc: @MariaHCD

Nice, @allroundexperts' proposal looks good to me too

BZ checklist

The PR that introduced the bug has been identified. Link to the PR:
The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

Not a regression. This issue seems to present during the original ContinueStep implementation itself. We wouldn't have noticed it before secondary method implementation and it is also a very corner case.

Determine if we should create a regression test for this bug.
If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

No. I don't think it would be beneficial to add regression test for this corner case.

Offers sent @allroundexperts @abdulrahuman5196 @dhanashree-sawant

@greg-schroeder Accepted the offer.

Paid, checklist complete. Closing.


fixed background scroll issue and removed prevent default that caus r…

…eact dom errors

Hi, @nadav-co, can you connect this MR to the issue you want to resolve? Thanks.

I will close this PR since there aren't new commits from my last comment. If you have any recent changes, feel free to create a new Pull Request.


Still supported?

Is this tool still supported? No replies from the author for some weeks ...

I have been on vacation and started a new job. PresenceLight is not how I make a living, so please understand I might not look at the repo constantly. If something is so urgent that it needs my attention, there are ways to get ahold of me.


little encoding patch

I think the string returned here should be of 'us-ascii', not 'utf-8'.
Besides of being the original intendation of the class delivering a 7-bit compatible string, it will confuse (in my case) other tools like serialport, which feels invited to convert the string again and causes strange encoding errors at the modem level.
Besides that, you saved me lots of time releasing this, thanks!!! ;)

Hey @mollat, thanks for the suggestion and patience for my slow reaction!
I've been looking at this small patch for some time now and I'm still a bit confused about it, odd as it may sound.
I think that the method which converts from UTF-8 to GSM 03.38 should not return a US-ASCII encoded string since these bytes are not valid ASCII. For example, the last 3 codes from GSM 03.38 – [0x7F, 0x7E, 0x7D] interpreted in US-ASCII are \x7F (no interpretation), ~ (tilde) and } which is not what the GSM 7-bit alphabet means.
If anything, this should probably be just a binary encoded string (i.e. ASCII-8BIT or BINARY) since we're basically returning just a series of bytes.
What do you think? Would using Encoding::BINARY instead of "US-ASCII" solve your case?


GitHub API library replacement

Closes #153
Changes
Switched to hub4j/github-api, really wasn't a big change.
BUT at the moment without R8 support. Trying to build a release app current kills the library.
I'm trying to fix that, help appreciated.
Do you want to already merge or wait for the R8 support?

Missing class com.infradna.tool.bridge_method_injector.BridgeMethodsAdded (referenced from: org.kohsuke.github.GHIssue and 4 other contexts)
Missing class edu.umd.cs.findbugs.annotations.NonNull (referenced from: org.kohsuke.github.GitHubRequest$Builder org.kohsuke.github.GitHubRequest$Builder.injectMappingValue(java.lang.Object) and 1 other context)
Missing class edu.umd.cs.findbugs.annotations.SuppressFBWarnings (referenced from: int org.kohsuke.github.extras.ImpatientHttpConnector.CONNECT_TIMEOUT and 14 other contexts)
Missing class javax.annotation.CheckForNull (referenced from: org.kohsuke.github.GHMyself org.kohsuke.github.GitHub.myself and 23 other contexts)
Missing class javax.annotation.Nonnull (referenced from: java.util.Date org.kohsuke.github.GHRateLimit$Record.resetDate and 96 other contexts)
Missing class javax.annotation.Nullable (referenced from: java.lang.String org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory.getSystemProperty(java.lang.String, java.lang.String) and 2 other contexts)
Missing class javax.annotation.WillClose (referenced from: org.kohsuke.github.GitHubRequest$Builder org.kohsuke.github.GitHubRequest$Builder.with(java.io.InputStream))
Missing class okhttp3.Cache (referenced from: okhttp3.Call org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.buildCall() and 2 other contexts)
Missing class okhttp3.CacheControl$Builder (referenced from: void org.kohsuke.github.extras.okhttp3.OkHttpConnector.<init>(okhttp3.OkHttpClient, int) and 1 other context)
Missing class okhttp3.CacheControl (referenced from: void org.kohsuke.github.extras.okhttp3.OkHttpConnector.<init>(okhttp3.OkHttpClient, int) and 1 other context)
Missing class okhttp3.Call (referenced from: okhttp3.Call org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.call and 8 other contexts)
Missing class okhttp3.Callback (referenced from: void org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.connect() and 1 other context)
Missing class okhttp3.CipherSuite (referenced from: java.lang.String org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$DelegatingHttpsURLConnection.getCipherSuite())
Missing class okhttp3.ConnectionSpec (referenced from: java.util.List org.kohsuke.github.extras.okhttp3.OkHttpConnector.TlsConnectionSpecs() and 1 other context)
Missing class okhttp3.Dispatcher (referenced from: okhttp3.Call org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.buildCall())
Missing class okhttp3.Handshake (referenced from: okhttp3.Handshake org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.handshake and 8 other contexts)
Missing class okhttp3.Headers$Builder (referenced from: okhttp3.Headers$Builder org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.requestHeaders and 8 other contexts)
Missing class okhttp3.Headers (referenced from: okhttp3.Headers org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.responseHeaders and 11 other contexts)
Missing class okhttp3.HttpUrl (referenced from: okhttp3.Call org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.buildCall() and 2 other contexts)
Missing class okhttp3.Interceptor (referenced from: okhttp3.Interceptor org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$UnexpectedException.INTERCEPTOR and 2 other contexts)
Missing class okhttp3.OkHttpClient$Builder (referenced from: okhttp3.Call org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.buildCall() and 9 other contexts)
Missing class okhttp3.OkHttpClient (referenced from: okhttp3.OkHttpClient org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.client and 28 other contexts)
Missing class okhttp3.Protocol (referenced from: okhttp3.Headers org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.getHeaders() and 1 other context)
Missing class okhttp3.Request$Builder (referenced from: okhttp3.Call org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.buildCall() and 1 other context)
Missing class okhttp3.Request (referenced from: okhttp3.Call org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.buildCall() and 5 other contexts)
Missing class okhttp3.RequestBody (referenced from: okhttp3.Call org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.buildCall() and 5 other contexts)
Missing class okhttp3.Response (referenced from: okhttp3.Response org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OkHttpURLConnection.networkResponse and 18 other contexts)
Missing class okhttp3.ResponseBody (referenced from: okhttp3.ResponseBody org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$ResponseBodyInputStream.responseBody and 6 other contexts)
Missing class okio.Buffer (referenced from: okio.Buffer org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$BufferedRequestBody.buffer and 2 other contexts)
Missing class okio.BufferedSink (referenced from: okio.BufferedSink org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OutputStreamRequestBody$1.val$sink and 6 other contexts)
Missing class okio.Okio (referenced from: void org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$StreamedRequestBody.<init>(long))
Missing class okio.Pipe (referenced from: okio.Pipe org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$StreamedRequestBody.pipe and 1 other context)
Missing class okio.Sink (referenced from: void org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$StreamedRequestBody.<init>(long))
Missing class okio.Timeout (referenced from: okio.Timeout org.kohsuke.github.extras.okhttp3.ObsoleteUrlFactory$OutputStreamRequestBody.timeout and 2 other contexts)

I would say, merging this even without R8 support is sensible :+1:
That can then be worked on separately.


Printing NSData and adding timestamps to logs

Hi,
this repository is great work! It's really nice how it uses Frida to intercept XPC messages. This makes it much easier to extend it. In this PR I've added some features that I have been missing:

There seems to be a rather new bplist format (bplist17). There is currently no public specification available of it. Therefore, all XPC messages with bplist17 would try to print raw data using the toString() method, but they are cropped after a few bytes.  Therefore, I added a custom XPC_dictionary parser that will print all XPC_Data contents as hex manually. This has been tested on several processes and works reliable.

I added an option (-d, --print-date) that will print the timestamp attached to each XPC message. This makes it easier if multiple sources are used at the same time (e.g system logs and XPCSpy).

I hope this additions help the project

Hi, awesome stuff, thanks! Will review this weekend.

I've managed to mess-up the PR somehow (don't use Github a lot), but everything should be merged now.

Thanks for merging and checking


Remote animation no longer handles broken animations gracefully.

It used to replace those animations by None and then continue on, but in the current codebase there is no way for a subanimation to be None.
Remote with a bad element needs to be part of the whole test suite!  As it is, I never test the error case.

I think I fixed this but I can't run the remote animations any more.

I'll take a look.
Really gotta figure out why you can't run remote on your Mac though...
that's no bueno :(
On Thu, Mar 8, 2018 at 8:03 AM, Tom Swirly<EMAIL_ADDRESS>wrote:

I think I fixed this but I can't run the remote animations any more.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/626#issuecomment-371480590,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6a6uSk4TM5Gl9jgcYXrAvTR6vExwSbks5tcSwigaJpZM4SKsMO
.


[v0.8] Move self test logic to crate mbedtls-selftest

mbedtls-selftest
This Rust crate is designed for separating self-test code that needs to export Rust
functions and define C functions to be used by C mbedtls. By separating this code,
different versions of Rust mbedtls crates can be used within a single crate, which
helps to solve link name conflict errors.
Note: Although multiple versions of Rust mbedtls crates can be used within a
single crate, only one mbedtls-selftest and one mbedtls-sys-auto crate can be
used since they are built as native libraries.
Changes need attention

Pump version of mbedtls to 0.8.3
Cherry picked PR: #180, #206, #214 to fix CI and compile errors
Add patch in workspace Cargo.toml to ensure mbedtls-selftest use local mbedtls-sys-auto crate

bors try

bors try

bors try

Backport https://github.com/fortanix/rust-mbedtls/pull/243 as well?

Backport #243 as well?

Oh, yes, it's also needed for 0.8.X

bors cancel

bors try

bors try

bors cancel

bors try

Close this PR, and continue work with remain in:

https://github.com/fortanix/rust-mbedtls/pull/259


Implement RawTLS and RawMacaroons parameters in LndServicesConfig

This PR allows an instantiation of LndServicesConfig to use raw macaroon data (passed as bytes or base64-encoded strings) as well as raw TLS certificate data (passed as bytes), allowing for LndServicesConfig to be used programmatically using loaded kubernetes secrets, hardcoded macaroons/certs, etc.
Pull Request Checklist

[x] PR is opened against correct version branch.
[x] Version compatibility matrix in the README and minimal required version
in lnd_services.go are updated.

Thanks for the PR!
This is definitely something that can be very useful and I think we should add the feature.
Though I'm sure you have a specific use case in mind, therefore my question before I do a full review:
Would it not be enough to specify one raw macaroon and call it RawCustomMacaroon? That would simplify things quite a bit. You'd need to either pass the raw admin macaroon or bake a custom one, but that's where we want to head anyway (no more multiple macaroon files as they're tedious to handle).

Thanks for the PR!
This is definitely something that can be very useful and I think we should add the feature.
Though I'm sure you have a specific use case in mind, therefore my question before I do a full review:
Would it not be enough to specify one raw macaroon and call it RawCustomMacaroon? That would simplify things quite a bit. You'd need to either pass the raw admin macaroon or bake a custom one, but that's where we want to head anyway (no more multiple macaroon files as they're tedious to handle).

Would it not be enough to specify one raw macaroon and call it RawCustomMacaroon? That would simplify things quite a bit.

I actually like this idea a lot, and would make certain use cases much easier to implement!

Would it not be enough to specify one raw macaroon and call it RawCustomMacaroon? That would simplify things quite a bit.

I actually like this idea a lot, and would make certain use cases much easier to implement!

@guggero and @torkelrogstad, I just pushed a slight refactor to this PR -- instead of using a self-rolled RawMacaroon type, LndServicesConfig takes a CustomMacaroon parameter, which is the raw []byte slice of either admin.macaroon or a self-baked macaroon with all necessary client permissions.

@guggero and @torkelrogstad, I just pushed a slight refactor to this PR -- instead of using a self-rolled RawMacaroon type, LndServicesConfig takes a CustomMacaroon parameter, which is the raw []byte slice of either admin.macaroon or a self-baked macaroon with all necessary client permissions.

Concept ACK, thanks for the changes!
The PR needs a rebase. It would also be great if you could clean up the commit structure and split the changes into small and logical commits. There are also a few style nits that should be addressed.
Please see https://github.com/lightningnetwork/lnd/blob/master/docs/code_contribution_guidelines.md as we try to adhere to those rules in all our projects.

Concept ACK, thanks for the changes!
The PR needs a rebase. It would also be great if you could clean up the commit structure and split the changes into small and logical commits. There are also a few style nits that should be addressed.
Please see https://github.com/lightningnetwork/lnd/blob/master/docs/code_contribution_guidelines.md as we try to adhere to those rules in all our projects.


Replace open-feature/golang-sdk with open-feature/go-sdk

Done in https://github.com/rollout/cloudbees-openfeature-provider-go/commit/2a91d780a1323995fad0fb1750cc013cd46f6bfd


The global cursorColor doesn't apply to TextFormField in Flutter web

The  cursorColor setting works at a local level, though not when set through a MaterialApp theme via a ThemeData.
The code is here: https://codepen.io/aflutterdev/pen/99df6d580d4c6e4cdb1d19bca2688109
The Flutter details are bellow:
[✓] Flutter (Channel master, 1.20.0-8.0.pre.41, on Mac OS X 10.15.5 19F101, locale en-NL)
    • Flutter version 1.20.0-8.0.pre.41 at /Users/user/development/flutter
    • Framework revision fd80503fd3 (3 hours ago), 2020-07-10 14:41:02 +0530
    • Engine revision 9b3e3410f0
    • Dart version 2.9.0 (build 2.9.0-20.0.dev 06cb010247)

cursorColor from ThemeData is applied when running on Android, but is not applied when running with web, iOS or macos desktop

flutter doctor -v
[✓] Flutter (Channel master, 1.20.0-8.0.pre.40, on Mac OS X 10.15.5 19F101, locale en-GB)
    • Flutter version 1.20.0-8.0.pre.40 at /Users/nevercode/dev/flutter
    • Framework revision 6eaaf1650e (13 hours ago), 2020-07-09 18:04:37 -0700
    • Engine revision 9b3e3410f0
    • Dart version 2.9.0 (build 2.9.0-20.0.dev 06cb010247)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/nevercode/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.1

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

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 47.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

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

[✓] Connected device (5 available)
    • Redmi Note 7 (mobile)      • 6345c469                             • android-arm64  • Android 9 (API 28)
    • iPhone 11 Pro Max (mobile) • 9F9AFD9B-7F22-468E-8096-B47E993E0619 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-13-5 (simulator)
    • macOS (desktop)            • macos                                • darwin-x64     • Mac OS X 10.15.5 19F101
    • Web Server (web)           • web-server                           • web-javascript • Flutter Tools
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 83.0.4103.116

• No issues found!

CC @darrenaustin
We're adding support for a TextFieldTheme, so that the textfield's cursor color and other visual properties can be configured in the conventional way. See https://github.com/flutter/flutter/pull/61008

Also found in latest master release 1.21.x

This is fixed with the new TextSelectionTheme migration that finished with #66482.


Warning: Failed prop type: Invalid props.styleIndicator key color supplied to MultiSelect

I have a warning appeared for the style of the styleIndicator, but it seems working.
Warning: Failed prop type: Invalid props.styleIndicator key `color` supplied to `MultiSelect`.
Bad object: {
  "color": "#007aff"
}

How can I get rid of this warning ?

Steps to Reproduce
just add the prop in the multi select :
styleIndicator={{ color: '#007aff' }}
Workaround solution
Well i just wrote this for the me moment
import { LogBox } from 'react-native';
LogBox.ignoreLogs(['Invalid props.styleIndicator key']);

styleIndicator doesn't accept color property, instead you can go react-native-multi-select.js file and search for styles.indicator and then crtl+click on indicator, it'll take you the style. There u'll find color property you can change it as per requirement.


Liveview learn example don't work

References
https://github.com/DioxusLabs/dioxus/issues/1690
Problem
If we try to follow the documentation of  https://dioxuslabs.com/learn/0.4/getting_started/liveview errors occur when compiling the examples:
error[E0432]: unresolved import `axum::extract::ws`
 --> src/main.rs:1:21
  |
1 | use axum::{extract::ws::WebSocketUpgrade, response::Html, routing::get, Router};
  |                     ^^ could not find `ws` in `extract`

error[E0433]: failed to resolve: could not find `Server` in `axum`
  --> src/main.rs:42:11
   |
42 |     axum::Server::bind(&addr.to_string().parse().unwrap())
   |           ^^^^^^ could not find `Server` in `axum`

Steps To Reproduce

Follow the steps in the text (create bin, add dependencies, copy text,...)
run: cargo build

Expected behavior

We can compile and don't get errors.

Environment:

dependencies:

axum = "0.7.4"
dioxus = "0.4.3"
dioxus-liveview = { version = "0.4.3", features = ["axum"] }
tokio = { version = "1.35.1", features = ["full"] }

Rust version: 1.75
OS info: MacOS Ventura 13.6.3
App platform: liveview

Questionnaire

[x] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

We need to enable the ws feature on axum like we do in the liveview crate here to get web socket functionality:
https://github.com/DioxusLabs/dioxus/blob/df74e4c2fcf3e4913c2fe7717c0144b7ac2129b4/packages/liveview/Cargo.toml#L35


Ruby execution error: `proc': tried to create Proc object without a block (ArgumentError)

I am coming across an error while running the dnscat2 server module on my Ubuntu.
Command
$ruby dnscat2.rb --dns "domain=domain.com,host=<IP_ADDRESS>"
Output
New window created: 0
New window created: crypto-debug
Welcome to dnscat2! Some documentation may be out of date.

/root/tools/c2/dnscat2/libs/swindow.rb:186:in `proc': tried to create Proc object without a block (ArgumentError)
        from /root/tools/c2/dnscat2/libs/swindow.rb:186:in `on_input'
        from /root/tools/c2/dnscat2/controller/controller.rb:30:in `initialize'
        from dnscat2.rb:116:in `new'
        from dnscat2.rb:116:in `<main>'

OS Environment
OS: Ubuntu 22.04.2 LTS
Ruby version: ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]

Any idea how to resolve this?

[Update]
Fixed the issue by installing the older version of ruby 2.7 using rbenv. But I am getting this error in a constant loop:
/root/tools/c2/dnscat2/tunnel_drivers/driver_dns.rb:316: warning: Capturing the given block using Kernel#proc is deprecated; use `&block` instead
/root/tools/c2/dnscat2/libs/dnser.rb:872: warning: Capturing the given block using Kernel#proc is deprecated; use `&block` instead

Any idea how to fix it?

Fixed the issue by applying the ruby code patches.


bug (app): Unable to find robots on 3.19.0-alpha.2

Overview

The app fails to locate robots to connect. Instead the app is stuck perpetually looking for robots
Current behavior

App fails to find robot to connect to on either Wifi or USB
Mixpanel error stack trace:
mixpanel.cjs.js:90 Mixpanel error: Implementation error. Please turn on debug and contact<EMAIL_ADDRESS>j @ mixpanel.cjs.js:90
hostReportError.js:3 Uncaught TypeError: Cannot read property 'opt_out_tracking_cookie_prefix' of undefined
    at pe.get_config (mixpanel.cjs.js:3899)
    at pe._call_gdpr_func (mixpanel.cjs.js:3977)
    at pe.opt_in_tracking (mixpanel.cjs.js:4022)
    at c (mixpanel.js:51)
    at t._tapNext (epic.js:57)
    at t._next (tap.js:45)
    at t.next (Subscriber.js:53)
    at t._next (filter.js:38)
    at t.next (Subscriber.js:53)
    at t._next (pairwise.js:24)

Steps to reproduce

Install build 3.19.0-alpha.2 (issue confirmed on windows and mac builds)
Open the Opentrons app to the Robot tab
Turn on your robot
Observe

Expected behavior

App should find your robot to connect to.

tagging @sfoster1 for visibility

Closed by #5971. For clarity, this was not an issue with robot discovery, but rather, and issue with the app's renderer thread crashing due to an uncaught exception


Fixed and added somy Libs.

Thanks

Whoops, I saw a mistake.

Sorry, here is the fix https://github.com/mikepenz/AboutLibraries/pull/132


Question about 'roslaunch launch/just_robot.launch'

Dear @kninad,
Thanks for your great work and for sharing very much.
I want to try the gazebo demo but can't find the just_robot.launch file.
Could you please give me some guide on how to set up it?
Best,
Leon

Hi Leon, thanks for pointing this out! The launch file is prettty simple, it just launches the Fetch robot in the simulation environment. We will shortly upload it to the main branch along with other helpful launch files in the launch/ folder :)

Hi @ZhengLeon , please find the launch files here: https://github.com/IRVLUTD/SceneReplica/tree/main/launch. They have been updated in the repository.

Hi @07hokage , thanks for your update. However, I find another issue that the fetch_gazebo package can't be installed in ubuntu20.04. May I ask what the tested environment in this project? Thanks.

@ZhengLeon , the setup instructions can be found here https://github.com/IRVLUTD/SceneReplica/tree/main#ros-setup i.e., in the main Readme description. Once the setup is done, the SceneReplica repo can be cloned and the simulation can be run as mentioned in here

Hi @07hokage , thanks a lot, it works well now.


chore: get more data from npm registry

Fixes https://github.com/fingerprintjs/gradejs-backend/issues/179

Can you please also update PackageMetadata DB model?


Net surplus compensation may be taxable

A possible change noted by Paul for when compensation for distributed generation drives the bill negative: The negative bill is technically treated as savings in the cash flow, not income. Income would be subject to income tax, but savings are not. For the residential and commercial financial models, the only taxable income is from cash incentives that are marked as taxable.
Collect any negative bills as taxable income in the cashloan financial module.

@cpaulgilman I'm looking at this as a possible issue for patch 1, and I think I'll need to add a variable to cashloan in order to compute the tax. Cases where there is a net payment to the utility over the year, but a payment from the utility in one month wouldn't show up in annual_energy_value.
I see two options: (1) add utility_bill_w_sys_ym as an input to cashloan and have cashloan compute based on any negative numbers. (2) Have utilityrate5 collect the total payments from the utility over each year, and pass that as a new variable to cashloan.
Preferences? Other ideas?

@brtietz Do we have documentation of the tax treatment of cash payments received by a residential or commercial system owner by the utility?
It looks like elec_cost_with_system and elec_cost_without_system are already inputs to the cashloan module. Is utility_bill_w_sys_ym a different variable? I guess the former are Year 1 arrays, and the latter is a matrix over the entire analysis period? Seems confusing to have both utility_bill_w_sys_ym and elec_cost_with_system as inputs.
I'm not sure I can think of any offhand, but are there other items that might be considered as taxable income to a residential or commercial system owner? Maybe salvage value?
@sjanzou may have some thoughts.

Annoyingly, the clearest answers on this are TurboTax forum posts, which suggest it's "other income" reported on a 1099:
https://ttlc.intuit.com/community/taxes/discussion/yes-you-are-required-to-report-all-income-unless-specifi/01/663742#M267867
Some more reputable sources that point in the same direction less clearly:
https://www.energy.gov/sites/prod/files/2020/01/f70/Guide to Federal Tax Credit for Residential Solar PV.pdf
https://www.puc.nh.gov/regulatory/Docketbk/2016/16-576/MOTIONS-OBJECTIONS/16-576_2017-03-24_LEBANON_ATT_RESPONSE_CFL_MOTION_FOCUS_OCA_MOTION_IN_LIMINE.PDF
https://www.greentechmedia.com/articles/read/Solar-Policy-Battle-IRS-Now-Part-of-Fierce-Debate-on-How-to-Value-Solar-Po
Yes utility_bill_w_sys_ym is a different variable, elec_cost_with_system is annual, so we may not be able to determine the payment amounts.
I also realized this morning that any input/output changes are better left for a major version, so I'll tag this for the fall 2021 release.

I agree this is probably best left to a major version. I'm not sure if the debate described in the 2014 GTM article has been resolved, but if this is a policy issue currently under debate, it might make most sense in SAM to make the utility cash payments optionally taxable so policy analysts can explore the impact of different tax rules. Also, this is probably handled differently in different countries, so we should use an approach that works around the world.

Response from Owen on this:

I did some asking around, and there is definitely some serious ambiguity about this question. This is a pretty rare occurrence, usually a small dollar amount, and certainly not income that utilities are reporting to the IRS (i.e., issuing a 1099, etc.) even if the income is in fact taxable. I think having a checkbox for this would be useful, but it should probably be default off, and I wouldn’t necessarily place this high on the list compared to other more pressing tariff-related upgrades!
My father lives outside of NYC, is served by ConEd for electric/gas, and has solar. His excess NEM credits are actually used to pay for his natural gas bill!

Taking this off the list for the release since other utility rate upgrades are higher priority.


Check and merge rest api version upgrade PRs

Description
Need to check and merge the rest api version upgrade PRs in [1]
[1] https://github.com/wso2/api-manager/issues/958
Affected Component
APIM
Version
No response
Related Issues
No response
Suggested Labels
No response

##Sub tasks :

[ ] Merge carbon-apimgt PR - https://github.com/wso2/carbon-apimgt/pull/11659
[ ] Merge apim-apps PR - https://github.com/wso2/apim-apps/pull/386
[ ] Merge product-apim version upgrade PR - https://github.com/wso2/product-apim/pull/13020
[ ] Merge product-apim integration test PR - https://github.com/wso2/product-apim/pull/13017
[ ] Merge apictl PR - https://github.com/wso2/product-apim-tooling/pull/958
[ ] Merge Integration Studio PR - https://github.com/wso2/integration-studio/pull/1166

This task is on-hold due to a build failure issue in apim-apps repo. There is an issue in publisher-api.yaml file download. This is currently tracked through https://github.com/wso2/api-manager/issues/1015

After the fix for https://github.com/wso2/api-manager/issues/1015 there are unit test failures we need to look into. This is in progress.

The 2 PRs [1] and [2] are reverted until the apim-apps unit tests are fixed.
[1] https://github.com/wso2/carbon-apimgt/pull/11659
[2] https://github.com/wso2/apim-apps/pull/386

Test failures are fixed with the following PRs. The following two PRs also contain changes done by reverted two PRs ( https://github.com/wso2/carbon-apimgt/pull/11659, https://github.com/wso2/apim-apps/pull/386 )

https://github.com/wso2/apim-apps/pull/397
https://github.com/wso2/carbon-apimgt/pull/11698

Merged the 2 PRs below.

https://github.com/wso2/apim-apps/pull/397
https://github.com/wso2/carbon-apimgt/pull/11698

Waiting for the release build to complete in order to upgrade the rest of the repos.

Update : apim-apps release build is still in progress. Need to merge PR https://github.com/wso2/product-apim/pull/13039 after that.

Update : The product-apim version upgrade PR and the integration test PRs were merged. And a product-apim build is triggered.

https://github.com/wso2/product-apim/pull/13039
https://github.com/wso2/product-apim/pull/13017

Update : The following PRs are added to fix the issue. Currently the build is in progress to check the test failures.

https://github.com/wso2/carbon-apimgt/pull/11709
https://github.com/wso2/product-apim/pull/13044

Update : All PRs are merged. Hence closing.


Implemented "--unattended" option (Issue #223)

I ported the functionality from the pi-hole script to fix #223 (#86). I finished implementing it but more people should try it before merging.

Parameters will be stored in /etc/pivpn/setupVars.conf
added a finalExports function
added an update_dialogs function to ask what to do if a parameter file was found
added an updatePiVPN function

Moved some stuff around.
This request is ready for testing.

Is there a way to update without generating new keys? I read the wiki about just not updating, but it might be a good time to add this now.

I also added command line options for the pivpn add and pivpn revoke functions. Now I can fully automate the setup and send myself an email with the certificate when everything is installed. :)

Can anyone help me updating the bash-completion file?

@EWouters man I just saw this now.  been really swamped.  Let me review and give you some comments but thanks a ton for this.

@EWouters this is looking good so far.  I've only looked at it online.  Will test on real devices to see if it broke anything somewhere.  But looks good reading it, awesome job.

Great, I'm happy to make any improvements you might suggest. There are also still a few comments in the code where I wasn't sure what was the best approach.

Any word on this PR?  Movement seems to have stalled?

Hi @troyfontaine ,
The code was tested and merged into the master, and most of the suggestions and things I was not sure about have since been fixed or become obsolete. Only a few things (like the bash-completion file and the comment on this line) remain to be fixed/checked, but I don't know how to do that.
Are you referring to anything specific? And have you tried the --unattended option?
It might be a good idea to check if there were any substantial improvements in the pi-hole installer since this rewrite. I basically ported all the things they did there to this installer.


Replace Subset tab reset to defaults with the viz tab version

Subset tab

Viz tab has just the icon

Looks good


Error on make

$ make
g++  -o tcr_docking_angle tcr_docking_angle.cc tcr_complex.cc  -lgsl -lgslcblas -Lfast -lfast
/usr/bin/ld: cannot find -lfast
collect2: error: ld returned 1 exit status
make: *** [makefile:10: tcr_docking_angle] Error 1

So far I know that I may be missing the fast library.
Do you know which version I can find fast library? Or how to install it?
I'm currently using Ubuntu 20.04.6 LTS, and g++ 9.4.0.
Thanks,

The fast library code files are in the "fast" subfolder. If you go into that folder and "make", it will hopefully build the fast library for you, which you can then copy into the compilation directory for tcr_docking_angle.
Let me know if that works, and/or if you have any more questions.

Thank you for answering so fast!
So, I have ran make on the fast folder. The only libfast in the fast folder is a .dylib file.
Sorry about my lack of knowledge here, but was this supposed to work on Ubuntu?
Well, I tested with this one, and got the same error from the first message.
After that I have compiled the .so file with the following commands:
$ gcc -fPIC -I. -c fast.c -o fast.o
fast.c: In function ‘main’:
fast.c:108:3: warning: format not a string literal and no format arguments [-Wformat-security]
  108 |   printf(usage);
      |   ^~~~~~
$ gcc -shared -o libfast.so fast.o

Even with the libfast.so, it doesn't work.
My error now is:
$ make
g++  -o tcr_docking_angle tcr_docking_angle.cc tcr_complex.cc  -lgsl -lgslcblas -Lfast -lfast
/usr/bin/ld: /tmp/ccdpDCFW.o: in function `TCRComplex::CalcTCRRotVector(double&, double&, double&)':
tcr_complex.cc:(.text+0x39d5): undefined reference to `alignment_create'
/usr/bin/ld: tcr_complex.cc:(.text+0x39e4): undefined reference to `jz_protein_null'
/usr/bin/ld: tcr_complex.cc:(.text+0x39f3): undefined reference to `jz_protein_null'
/usr/bin/ld: tcr_complex.cc:(.text+0x3a62): undefined reference to `bp_protein_load'
/usr/bin/ld: tcr_complex.cc:(.text+0x3aa3): undefined reference to `bp_protein_load'
/usr/bin/ld: tcr_complex.cc:(.text+0x3adc): undefined reference to `vote_pairwise'
/usr/bin/ld: tcr_complex.cc:(.text+0x3bf4): undefined reference to `vote_rms_fit'
/usr/bin/ld: tcr_complex.cc:(.text+0x3cd2): undefined reference to `jz_protein_clear'
/usr/bin/ld: tcr_complex.cc:(.text+0x3ce1): undefined reference to `jz_protein_clear'
collect2: error: ld returned 1 exit status
make: *** [makefile:10: tcr_docking_angle] Error 1

I'm certainly doing something wrong here.
I would be very glad with any help you can provide.

It is working now.
Thank you a lot!


Div is not working.

Toggle theme

I used this as markup and called it classic CSS. but seems it's not working it works if I use the checkbox wah. Do I need to do anything else?

Could you share your code?

I realised it's probably missing the theme-toggle--toggled. If you're using a div, you have to us js to toggle the classname "theme-toggle--toggled"

Ahh. Yes. Exactly. I solved it that way. Thank you so much for your reply. It should documented in the demo so anyone won't be confused. Thanks for this awesome product free of cost. I love it.


Toggle comments not working in style area

The issue is very similar to the case https://github.com/vuejs/language-tools/issues/3776.
But it only fails in style area.
VSCode Version: 1.87.2
Vue - Official: v2.0.8
https://github.com/vuejs/language-tools/assets/9348314/443a98cd-5666-4ebb-a5d4-2a1bb8f2ef39

The same is happening to me on the

Verified that this one has been fixed in the lastest 2.x versions.


Setting up CI/CD for testing the assistant

Description
Even though developing a contextual assistant is different from developing traditional software, we should still follow software development best practices. Setting up a Continuous Integration (CI) and Continuous Deployment (CD) pipeline will ensure that every commit/PR is not introducing new problems or negatively impacting the performance of our assistant.
Solution
We can use GitHub Actions to run CI checks on every PR or commit. This action will train, test, and publish a summary.

Implement Rasa-Train-Test-Github-Action (RTTG) in a primary testing workflow
Describe:
Aim is to develop a CI Pipeline for testing the effects of code changes in Pull Requests (PRs) on the accuracy and performance of the rasa model and API, while also providing a comprehensive report on the result of the test. A testing step would inherently require a build (train) step.
Solution:
Using the Rasa-Train-Test-Github-Action (RTTG) as a part of our primary test workflow we can achieve the above goal.
Test Report Features:

[ ] Test Reports in PR Comments
[ ] Test Reports Storage in a Directory (for reference)

I will be creating two separate PRs each implementing one of the test report feature.

Hey @cdhiraj40 could you please assign the issue to me and also add the labels. Thanks 😀


The command Event | where EventLevelName == "error" uses error without capital E in error.

The command Event | where EventLevelName == "error" uses error without capital E in error.
If people are not watching properly they won't notice that that is the error why no results are shown as the website uses EventLevelName with capital E Error.
[Enter feedback here]

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

ID: 21eb5eb5-727d-c75e-33ba-31c823eed9d9
Version Independent ID: 35585318-b445-3eed-e9b4-4bb5d8b71085
Content: Collect Windows event log data sources with Log Analytics agent in Azure Monitor - Azure Monitor
Content Source: articles/azure-monitor/agents/data-sources-windows-events.md
Service: azure-monitor
Sub-service: agents
GitHub Login: @guywi-ms
Microsoft Alias: guywild

@xkoeckiiej Thanks for the feedback! I have fixed the referenced change, and the change should reflect on the doc within 24 hours. We will now proceed to close this thread. If there are further questions regarding this matter, please revert and we will gladly continue the discussion.

#please-close


Add functionality to improve Progressive web app score

Include offline-plugin for caching

create-react-app added functionality for PWAs!


Human Race Paladin Retribution BUG，The simulator should not have more strength points than the game

Describe the bug
The human paladin does not wear any equipment. Without BUFF, it is 173 points of strength
BUT，The simulator has 199 strength points without any BUFF and equipment

Expected behavior
Human strength are 173 default not 199
Sim Links and Screenshots

Paladins do indeed have 173 base strength in the sim.
It's likely that you have https://www.wowhead.com/wotlk/spell=20266/divine-strength enabled.
173 + (15% of 173) = ~199

basic strength are 155 like img1 not 155+(1.15*155)


Add option to randomly pick seed

This PR adds an option (--random-seed-corpus) to randomly pick a single input from the pool of seed corpus for fuzzer trial.
Basically we add additional seed validation step (after _clean_seed_corpus) to select input to be seed corpus. The selected input is temporarily placed in temp directory and move it back after we get rid of other inputs.
Note that, if there is only one input, this random seed mode will not take place.

close this since this implementation version is no longer valid


Start manually

User story:
As a mailman, I want to have a start button for manual control so that the car starts moving
Acceptance criteria:

The app should have a visible start button on the top of the screen
The start button should be disabled once the user clicks on it

This issue was implemened but due to some MQTT connection problems we had to remove implementation and not close it. we plan to rework it for sprint3


[Polish] Clean up miscellaneous "walk" directions from the server when sending Intermediate Stops

Right now the server:
a.) Only responds with a single proposed itinerary
and
b.) Has random spurious "walking" legs between the intermediates that can usually be combined.
We should try to see if we can resolve b.), and maaaybe a.).

Update: Server seems to correctly return more than one result now. Just need to worry about b.).


Use log package instead of console in main program

This provides timestamped log output. Also, the package-lock.json file has been updated via npm v5.3.0.

Coverage increased (+0.0007%) to 98.089% when pulling d58ea29ef44913dc16f35fc4a7adfe362c5a767f on log into 10c6da697c2640429c4d6c83b198e77ed4327fb5 on master.


don't overwrite files by default

Currently the command will overwrite any existing content of apb.yml and Dockerfile. It should instead exit with an error if they exist, or overwrite them only if the user provided a --force or similar flag.

Fixed in https://github.com/ansibleplaybookbundle/helm2bundle/commit/b77079cc9a347e829979ff6feffc561bb0907044


Dependency conflict with myst-parser

Describe the bug
When I add mdformat-myst to my Poetry environment it downgrades myst-parser to an extremely early and pretty much unusable version (0.7.1). I think this is because of the restriction on mdit-py-plugins:
"mdit-py-plugins >=0.3.0,<0.4.0",

Is the restriction to < 0.4.0 necessary?
Reproduce the bug
In a poetry environment (or presumably using any other dependency management tool) add md-format and myst-parser to the environment.
List your environment
No response

I confirm the issue between the last 2 release of mdformat-myst and mdformat-admon:
❯ pip install --dry-run mdformat-myst==0.1.4 mdformat-admon==1.0.2
Collecting mdformat-myst==0.1.4
  Using cached mdformat_myst-0.1.4-py3-none-any.whl (6.8 kB)
Collecting mdformat-admon==1.0.2
  Obtaining dependency information for mdformat-admon==1.0.2 from https://files.pythonhosted.org/packages/83/b5/ae19f582ceabe514044838c4e9bb68e1903dfc224106d3e2fe19759af1e4/mdformat_admon-1.0.2-py3-none-any.whl.metadata
  Using cached mdformat_admon-1.0.2-py3-none-any.whl.metadata (3.6 kB)
Collecting mdformat<0.8.0,>=0.7.0 (from mdformat-myst==0.1.4)
  Obtaining dependency information for mdformat<0.8.0,>=0.7.0 from https://files.pythonhosted.org/packages/bf/d9/4790d04eb7bcc77f02000232b75e8356c5443ee9f6fe28a7786de96485c0/mdformat-0.7.17-py3-none-any.whl.metadata
  Using cached mdformat-0.7.17-py3-none-any.whl.metadata (8.7 kB)
Collecting mdit-py-plugins<0.3.0,>=0.2.7 (from mdformat-myst==0.1.4)
  Using cached mdit_py_plugins-0.2.8-py3-none-any.whl (41 kB)
Collecting mdformat-tables>=0.4.0 (from mdformat-myst==0.1.4)
  Using cached mdformat_tables-0.4.1-py3-none-any.whl (4.6 kB)
Collecting mdformat-frontmatter>=0.3.2 (from mdformat-myst==0.1.4)
  Using cached mdformat_frontmatter-2.0.1-py3-none-any.whl (4.5 kB)
Collecting ruamel.yaml>=0.16.0 (from mdformat-myst==0.1.4)
  Obtaining dependency information for ruamel.yaml>=0.16.0 from https://files.pythonhosted.org/packages/d9/0e/2a05efa11ea33513fbdf4a2e2576fe94fd8fa5ad226dbb9c660886390974/ruamel.yaml-0.17.32-py3-none-any.whl.metadata
  Using cached ruamel.yaml-0.17.32-py3-none-any.whl.metadata (17 kB)
INFO: pip is looking at multiple versions of mdformat-admon to determine which version is compatible with other requirements. This could take a while.
ERROR: Cannot install mdformat-admon==1.0.2 and mdformat-myst==0.1.4 because these package versions have conflicting dependencies.

The conflict is caused by:
    mdformat-myst 0.1.4 depends on mdit-py-plugins<0.3.0 and >=0.2.7
    mdformat-admon 1.0.2 depends on mdit-py-plugins>=0.4.0

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

Relates to:

https://github.com/KyleKing/mdformat-admon/issues/15
https://github.com/hukkin/mdformat-gfm/issues/27
https://github.com/hukkin/mdformat-gfm/pull/28
https://github.com/executablebooks/mdformat-deflist/issues/4
https://github.com/executablebooks/mdformat-deflist/pull/5

I proposed a fix at: https://github.com/executablebooks/mdformat-myst/pull/28


How to extract the last crash report as text/string?

I want to extract the last crash logged by KSCrash as Apple formatted text/string?
Is there any way to do that?
Hopefully in swift

@kunalverma25 were you able to do read the contents from the crash report?


Ensure that podman is logged into local Harbor

Each node needs to be logged into the local Harbor container registry for the cluster to function.  Currently, setup configures Harbor as the only CRI-O upstream registry in /etc/containers/registries.conf.d/00-neon-cluster.conf during cluster preparation and then normal cluster setup as well as ready-to-go setup explicitly use podman to log each node into Harbor using SSO credentials configured for LDAP authentication.
This makes sense, but now with the new neon-node-agent and its support for ClusterRegistry custom resources, we need to manage the local cluster registry in the same way that we manage the other upstream registries.  This will be important in the future when nodes can be added and removed for existing clusters, when we'll really want operators to be able to handle all of the node configuration and healing.
Supporting this won't be too hard:

[x] Cluster Prepare: I think we can leave this code alone.  This adds Harbor to the CRI-O upstream registries but pull/push won't actually work because Harbor isn't deployed yet and neither has its credentials been generated.  This doesn't really hurt anything and it doesn't make sense at this point to be changing things like this that may cause other problems.

[x] Cluster Setup: This should continue to use podman to log into the local Harbor but should also add a new ContainerRegistry custom resource for Harbor including the generated credentials.  This will allow neon-node-agent to include Harbor in /etc/containers/registries.conf.d/00-neon-cluster.conf and also ensure that it's always logged in.
NOTE: neon-node-agent isn't started until quite late during cluster setup, so it's important for Harbor to be logged in explicitly.

[x] Ready-to-go: This should continue to use podman to log into the local Harbor with the new credentials but should also add a new ContainerRegistry custom resource for Harbor including the generated credentials.  This will allow neon-node-agent to include Harbor in /etc/containers/registries.conf.d/00-neon-cluster.conf and also ensure that it's always logged in.
QUESTION: I'm not entirely sure that we actually need to explicitly log into the local registry here.  It's probably better to just let neon-node-agent handle this since it's possible to end up with a bit of a race condition.  All of our container images are already pinned, so we really aren't pulling anything from Harbor until the cluster is completely configured.

DONE


Feature 2644 blank space validation

Requirements

[x] This PR has a proper title that briefly describes the work done
[x] Please ensure the branch name follows naming convention - feature-githubissunumber-xxx, bug-githubissunumber-xxx, enhance-githubissunumber-xxx.
[x] I have referenced the  github issues('s)
[x] I performed a self-review of my own code
[x] New and existing unit tests pass locally with my changes
[x] I have added proper logs and comments for the developed code
[ ] If this PR includes MDMS or workflow data changes:

[ ] I have added MDMS data changes to support/<issue-number>-mdms.json
[ ] I have added workflow data changes to support/<issue-number>-workflow.json

Summary

Data Changes

Preview

Other

moved to https://github.com/pucardotorg/dristi-solutions/pull/1312/files


fix cluster nack for service entries with DNS/Static Resolution and  DR LB as PASSTHROUGH

Fixes https://github.com/istio/istio/issues/39736
This happens because "fake.external.com" is configured as DNS service entry but its destination rule configures it as PASSTHROUGH
So we build ClusterLoadAssignment and set LB as ORIGINAL_DST causing this NACK.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests_istio
14c00f37edb2a7ae07a72a56c4cb4f8c0deab2bd
link
true
/test unit-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ramaraochavali: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot_istio
e2728590774927c3f081f50718e7ffb9d1b947e0
link
true
/test integ-pilot_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot_istio

@hzxuzhonghu PTAL


Directly update

Beef up and reorganise direct follows calculation

The vispm project HEAD has hidden dependencies on this koalas branch. It adds a bit to the direct follows calculation and breaks the vispm df example in tests/. When I add it in vispm dot charts work for me.

the dot charts don't work? with the install on pypi or just with the current head?

Latest head. I got it running locally but had to tweak some things and
upgrade to this koalas version
On Thu, 30 May 2024 at 16:37, Adam Peter Banham @.***>
wrote:

the dot charts don't work? with the install on pypi or just with the
current head?
—
Reply to this email directly, view it on GitHub
https://github.com/AdamBanham/koalas/pull/13#issuecomment-2138786458,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKQJHZEKZWN5JGOLINFLEJDZE3CLVAVCNFSM6AAAAABIQF2VXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZYG44DMNBVHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

I am trending head of vispm as dev, the release version is stable though. Unsure if these changes should be merged to be here or in vispm to be honest

Head should never break basic testsOn 30 May 2024, at 7:38 PM, Adam Peter Banham @.***> wrote:
I am treating head of vispm as dev, the release version is stable though. Unsure if these changes should be merged to be here or in vispm to be honest
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Plus, it's just reorganizing the df calculation, it would be weird in vispm and fits fine here.AdamOn 30 May 2024, at 8:41 PM, Adam Burke @.> wrote:Head should never break basic testsOn 30 May 2024, at 7:38 PM, Adam Peter Banham @.> wrote:
I am treating head of vispm as dev, the release version is stable though. Unsure if these changes should be merged to be here or in vispm to be honest
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

I am not sure if these changes I have made, have tests here in koalas. So, before merging I should write some to test the additional steps I have included.
vispm doesn't really have tests... more a hobby project than software development. But I should write some tests to ensure that things still produce a figure. Perhaps, I was attempting to be too general in vispm, I was hoping not to need any direct dependency on an event log structure. Instead, I wanted to focus on the behaviour required for the visualisation and use an interceptor based on my required behaviours, i.e. iterating over trace instances.

TODOs

[ ] write some tests
[ ] merge PR


add pic fork me and link of project

To facilitate the forks!

@deividmarques Thank you, pull request merged!

@clovisdasilvaneto  :+1:


Fix baremetal provisioning when run on OpenShift.

This was fine in Kube but in OpenShift both ssh to libvirt, and .cache
image copying broke due to the security constraints in OpenShift.
This change adds a home dir, changes it's permissions so it will work
with a random UID, and adds that random runtime UID to /etc/passwd so
SSH will work.
Also moved mounting of the ssh private key such that it will always
happen even if log gathering is disabled.

For what it's worth most of this originates from the OpenShift documentation on how to work with arbitrary user IDs assigned by the platform: https://docs.openshift.com/container-platform/3.3/creating_images/guidelines.html#openshift-container-platform-specific-guidelines. The script there I ported into go to avoid complication around the entry point. But overall shouldn't be permanent.


scroll_to_me() scrolls all ScrollAreas

Is your feature request related to a problem? Please describe.
When using Response::scroll_to_me(), all scroll bars in the entire UI scroll in that direction. This is quite frustrating for a user when you have multiple scrollable areas.

Describe the solution you'd like
When calling scroll_to_me, it could either contextually figure out which ScrollArea it is inside, or, optionally you could pass in a ScrollArea id or set of ids.

Describe alternatives you've considered
Scrolling that ScrollArea manually,

Additional context
I first suspected this was a bug, but I gave the code a quick glance, and it seems this is the expected behavior, though I may have read it wrong.

Nesting multiple scroll areas inside each other is a rare (because it is pretty bad UX). egui optimizes convenience for the common case. In the case of nested scroll areas, sometimes you need to scroll both in order to bring the desired element into view. I think the simplicity of the current design (no need to pass around ids to what scroll area to scroll) wins out here.

The scroll areas were not nested. One was a SidePanel (it also happened if it was a window), the other a CentralPanel. Somewhat ironically, a change I have done since then seems to have fixed the issue for me, so it appears to be a situational bug then. I can check and see if I can find a broken commit and reproduce it.

Same problem
code
use eframe::{
  egui,
  epaint::vec2,
};

fn main() -> Result<(), eframe::Error,> {
  let options = eframe::NativeOptions {
    initial_window_size: Some(vec2(300., 200.,),),
    ..Default::default()
  };

  eframe::run_native(
    "scroll_to_me",
    options,
    Box::new(|_cc| Box::<MyApp,>::new(MyApp {},),),
  )
}

struct MyApp {}

impl eframe::App for MyApp {
  fn update(
    &mut self,
    ctx: &egui::Context,
    _frame: &mut eframe::Frame,
  ) {
    egui::CentralPanel::default().show(ctx, |ui| {
      // TOP
      egui::TopBottomPanel::top("top",).show_inside(ui, |ui| {
        egui::ScrollArea::horizontal().show(ui, |ui| {
          let response = ui.button("123",);
          if response.clicked() {
           //  Expected: only want to `scroll_to_me` in this scope ScrollArea
            response.scroll_to_me(Some(egui::Align::Center,),);
          }
        },);
      },);

      // Unexpected: but here the ScrollArea is also affected
      egui::ScrollArea::vertical().show(ui, |ui| {
        for i in 0..20 {
          ui.monospace(format!("label {i}"),);
        }
      },)
      //
    },);
  }
}


How to use global_max_pool with one graph?

❓ Questions & Help

I only have one graph which is have a feature matrix with n-cols and d-rows in one batch so that I don't know how should I set parameter 'batch' in this case?
global_max_pool(x, batch, size=None)
I don't know how to set the 'batch' in this case
Looking forward to your reply,thank you very mach!

x.max(dim=0) or set batch via batch = x.new_zeros(x.size(0), dtype=torch.long)

x.max(dim=0) or set batch via batch = x.new_zeros(x.size(0), dtype=torch.long)

Impressive!
Thank you for such a quick respond!
I have anthor question.
In every batch,I have N graphs that means I have a (Nn)d matrix(every graph have n nodes,but n is different between every graph).I want make the dimension of  every graph form nd become (nd)1,
final,the matrix of batch(N graphs)'s dimension become N(n*d).
I want use torch.bincount and torch.split the matrix,but I think the method is too slow.
Do have anthor methods?
Looking forward to your reply,thank you very mach!

That's what torch_geometric.utils.to_dense_batch is doing :)

That's what torch_geometric.utils.to_dense_batch is doing :)

OK, I'll try it later.
Finall, I want to ask why the parameter 'batch' can set like you told me ? I don't know the reason.

For each node, batch holds the index of the graph the node belongs to. Since you only have a single graph, setting batch to zero assigns all nodes to the same graph (with index 0).

For each node, batch holds the index of the graph the node belongs to. Since you only have a single graph, setting batch to zero assigns all nodes to the same graph (with index 0).

I'm flattered that you're reply so quickly.
Thank you and I wish you a happy life


support scala-js

Thank you for PR.
Since scala-js-java-time is in progress (https://github.com/scala-js/scala-js-java-time/issues/7), I think it is not a time to add support for Scala.js.
What do you think about it ?

@ocadaruma Just wanted to note https://github.com/soc/scala-java-time is a pretty much complete implementation of java.time.


The application is automatically made available under machine’s detected IP/hostname

When I relaunch the web pod, I got error 400 Bad Request.  The logs are look like:
Invalid HTTP_HOST header: '<IP_ADDRESS>:8000'. You may need to add '<IP_ADDRESS>' to ALLOWED_HOSTS.
Bad Request: /

As we are using fargate and the IP address will be changed every time it relaunch.  I manually update the code to add the ip address into ALLOWED_HOSTS for a dirty fix.  It is better to detect the ip address and add it into ALLOWED_HOSTS.
After browsing the internet, the following listed code can add the ip address dynamically.
from socket import gethostname, gethostbyname, gethostbyname_ex
ALLOWED_HOSTS = [ gethostname(), ] + list(set(gethostbyname_ex(gethostname())[2]))

Please update the code to allow adding ip address dynamically.  Thanks!

AWS CF docs have an article on Host header: https://aws.amazon.com/premiumsupport/knowledge-center/configure-cloudfront-to-forward-headers/

This situation happens during the health check stage by ALB of the container, not during forwarding the request.
When the container initialises, Django will check the ALLOWED_HOSTS.  As the container is created by fargate and a random private ip will be assigned to the container at this stage.  As the automatically assigned ip is not in the ALLOWED_HOSTS, error 400 will be retuned for the health check request.  The health check request is created by the ALB to determine the pod is running and attached the container to the ALB if the container is healthy.
If ALB cannot find a healthy container (target), it will turn 503 error.
By the way, we do not use cloudfront in AWS and X-Forward headers will be created by ALB automatically.

When the container initialises, Django will check the ALLOWED_HOSTS. As the container is created by fargate and a random private ip will be assigned to the container at this stage. As the automatically assigned ip is not in the ALLOWED_HOSTS, error 400 will be retuned for the health check request. The health check request is created by the ALB to determine the pod is running and attached the container to the ALB if the container is healthy.

@kwkwan  Hmm OK, I see that we must add a hostname for healthcheck requests? We can add an additional internal domain name to allowed hosts using INTERNAL_HOSTNAMES environment variable, it can be a comma-separated list of extra hostnames Django should allow: https://github.com/ietf-ribose/bibxml-service/blob/main/bibxml/settings.py#L57-L70

I don’t believe this should be part of concern to application level.
This makes the service always accessible by its IP, unless there is extra configuration in the front of it. You are tailoring application to K8s, but what’s being delivered here is not K8s config but this repository with containers and Compose configuration.

I’ll see how this can be resolved in some other way. Ideally the infrastructure should know its IPs and not require the app to inspect interfaces. Or there could be a special configuration option.

I see that we must add a hostname for healthcheck requests?

Unfortunately AWS does not allow that -- there will not be a hostname given. It will be some IP address from the AWS load balancer, which uses a rather random private IP address. If we really want to use the private IP address of the load balancer, since it is not available through static infrastructure (at time of deployment, through ENV vars), Django must read it in dynamically somehow with a pre-start request.

This makes the service always accessible by its IP, unless there is extra configuration in the front of it.

Well, in AWS Lambda/Fargate right now, they are behind private IPs within a private subnet. So there is no concern with security here.

Ideally the infrastructure should know its IPs and not require the app to inspect interfaces. Or there could be a special configuration option/environment variable.

The bottom line is this is not supported in such AWS cloud setup. The infrastructure uses dynamic IPs and they change frequently. And these values are not available in environment variables (remember that the ENV vars are statically set).
It is however possible to have a "range" of private IP address of the private subnet. That can be available as static information. Would you prefer that?

Unfortunately AWS does not allow that -- there will not be a hostname given. It will be some IP address from the AWS load balancer, which uses a rather random private IP address. If we really want to use the private IP address of the load balancer, since it is not available through static infrastructure (at time of deployment, through ENV vars), Django must read it in dynamically somehow with a pre-start request.

I see.

The bottom line is this is not supported in such AWS cloud setup.

OK, I see.

That can be available as static information. Would you prefer that?

Django doesn’t support ranges in ALLOWED_HOSTS. We could do it with a custom middleware, but what I can do instead is to introduce an environment variable that will explicitly tell Django “accept requests that use machine’s internal IP, because we will ensure they only come from internal healthcheck”.

Aha, thanks @strogonoff !

Should

Please set one or both of them to 1 in bibxml-infrastructure as desired to enable auto IP/hostname detection.

@kwkwan can you help with this?

Auto IP/hostname detection has been enabled.  Refer to https://github.com/ietf-ribose/bibxml-infrastructure/issues/23

Okay, this can be closed I think.

Thanks @strogonoff !


EOS Token Swap from Trezor

Dear developers,
can you please support? I still have EOS ERC20 Token on my Trezor.
Obviously it is impossible to ectract the private keys in order to swap EOS to mainnet.
How can I solve this? Please help.
Thank you!

The community has a tool for this, please use this link for further assistance.
[https://eosauthority.com/unregistered?network=eos]


About Image regression task

When I used your code of WIRE, I found that although the output of your model is fine in details but the color is not correct even like a gray image. I have reproduced much INRs models and there is no such questions. Can you share your code about image regression task?

@skxgogo do you mean image representation? If so, can you try this: https://github.com/vishwa91/wire/blob/main/wire_image_denoise.py
You can set tau (line 34) to a very large value, like 1e8. That will create a regression/representation code.


Ubuntu 14.04 build error due to old ffmpeg

Building oiio master on an Ubuntu LTS  (14.04) machine, I have libavcodec v54, but oiio requires functions that were introduced in v55.  Happily, the new functions are apparently just renamed old functions as part of an ffmpeg API cleanup.  Here is the build error:
/storage/dev/repos/oiio/src/ffmpeg.imageio/ffmpeginput.cpp: In member function ‘virtual bool OpenImageIO::v1_6::FFmpegInput::open(const string&, OpenImageIO::v1_6::ImageSpec&)’:
/storage/dev/repos/oiio/src/ffmpeg.imageio/ffmpeginput.cpp:231:30: error: ‘av_frame_alloc’ was not declared in this scope
m_frame = av_frame_alloc();
Here is a stackoverflow question where somebody ran into something similar:
http://stackoverflow.com/questions/24057248/ffmpeg-undefined-references-to-av-frame-alloc
I don't know if this is the best way, but the following after the "extern" block that includes the ffmpeg headers seems to do it.  Iw as able to build with this added to ffmpeginput.cpp
#if LIBAVCODEC_VERSION_INT < AV_VERSION_INT(55,28,1)
#define av_frame_alloc  avcodec_alloc_frame
#define av_frame_free   avcodec_free_frame
#endif
I dunno if compatibility with Ubuntu 14.04's ffmpeg is important, but it is the most recent Long Term Support release so I am hoping a few lines is worth it.  Should I make a pull request out of this, or does somebody else want to sort it out?

Yes, if you have a fix, please do make a pull request, and I'll happily merge it.

Fixed by #1168


Add FileDescriptor into Conn interface

name: Pull request
about: Propose changes to the code
title: ''
labels: ''
assignees: ''

1. Are you opening this pull request for bug-fixs, optimizations or new feature?
It is new feature.
2. Please describe how these code changes achieve your intention.

From user's perspective, file descriptor is useful.
3. Please link to the relevant issues (if any).

Discussed in several threads. One of issues (#186) is that unnamed unix domain socket doesn't have any remote address.
It is difficult to cross-reference in other functions.
4. Which documentation changes (if any) need to be made/updated because of this PR?

No change.
4. Checklist

[X] I have squashed all insignificant commits.
[X] I have commented my code for explaining package types, values, functions, and non-obvious lines.
[X] I have written unit tests and verified that all tests passes (if needed).
[X] I have documented feature info on the README (only when this PR is adding a new feature).
[X] (optional) I am willing to help maintain this change if there are issues with it later.

Sorry for the delayed response, I appreciate your efforts on this PR but still I don't think it's a good idea to expose an API returning file descriptor of socket directly. what's your requirement for this?

Maybe considering duplicate fd as listener did:
https://github.com/panjf2000/gnet/blob/8aeb278baabf0b893ef16b181f3035f38b712903/gnet.go#L84-L93


Unknown add-on

Hello! When I try to add the repository following the steps in the installation tutorial I encounter this problem:

Repository appears as unknown and no Valetudo or Congatudo add-on appears in my Homeassistant UI.

I think it is due to the repository.json url not matching the real repository url.
{
    "name": "Congatudo add-on",
    "url": "https://github.com/txitxo0/congatudo-add-on",
    "maintainer": "FreeConga <freecon.ga>"
}

I didn't experimented this issue, anyway it is already up to date again, thank you.
If the problem persist, just re-open the issue or try to reach us in the freecon.ga telegram group ;)


Get rid of zero-length poll case now that timer pool exists

No significant performance differences

No significant performance differences

No significant performance differences

No significant performance differences


TS-2153 : Add -M to traffic_manager options if needed

[approve ci]

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/555/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/451/ for details.

[approve ci]

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/557/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/453/ for details.

[approve ci]

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/579/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/475/ for details.

@jpeach we good to land this now?


Compilation (or Loading) problem for ES6+

Hi Marshall,
I am developing a small app  with  QuasarJS (1.9.9) + Feathers (4.5.5) + Feathers-Vuex (3.11.5).
Node (12.9.1).
In quasar.conf.js  there exists,   transpileDependencies: ["feathers-vuex"].
I am working on  Win 10.
On the client side;  if I compile by  >  quasar dev,   in compile messages it says,  Generating legacy js code (ES5); use "--modern" param for ES6+,   and  it completes normally,  eveything works as expected.
But if I compile by  >  quasar dev –modern  (which Quasar says necessary for ES6+)
it gives the following warning in terminal  and I can not get info from users service  (no login form).
    WARNING  Compiled with 1 warnings                                                                              12:51:23
    warning  in ./src/store/services/users.js

    Module parse failed: Unexpected token (12:19)
    File was processed with these loaders:
     *<EMAIL_ADDRESS>     * ./node_modules/eslint-loader/dist/cjs.js
    You may need an additional loader to handle the result of these loaders.
    |   }
    |   // Required for $FeathersVuex plugin to work after production transpile.

    >   static modelName = "User";

    |   // Define default properties here
    |   static instanceDefaults() {

    @ ./src/store/services sync nonrecursive .js$
    @ ./src/store/index.js
    @ ./.quasar/app.js
    @ ./.quasar/client-entry.js
    @ multi (webpack)-dev-server/client?http://<IP_ADDRESS>:8080 (webpack)/hot/dev-server.js ./.quasar/client-entry.js

The console on the browser looks like;

On a related topic,      QuasarJS says  (https://quasar.dev/quasar-cli/app-upgrade-guide#What’s-new-in-v2)
The JS transpilation (with the help of Babel) has been rethought from the ground up (now using           core-js v3). It will now transpile based on the Browser compatibility that you configure. It will no           longer go transpiling directly to ES5, but it will look for exactly what JS features need transpiling           based on the configured browsers.
Although I can continue with ES5 compilation for now,  for near future works,   ES6 will be usual way.
What is the problem at this point    and    what could be the solution for this issue?
Thanks in advance,
Levent Turel

Class static fields are not handled by webpack as it's still a stage 2 ECMA feature.
The equivalent of this is to assign the value on the class once it has been created.
See here in the docs
I have the same stack as you and this is what I do.

@J3m5 thanks a lot.
It worked for me too.
Replaced the static definitions  in ./src/store/services/users.js    by;
    class User extends BaseModel {}

    ```
    User.modelName = 'User'
    User.instanceDefaults = function() {
      return {
          email: '',
          password: ''
      }
    }


chore: update docs

update chapter 3
update chapter 4

@christian-bromann
I've removed the chromedriver service, but should we also have an "extra" assignment for the onComplete hook? The chapter now end very abruptly


npm install<EMAIL_ADDRESS>

I'm gussing #24 looks closed since package-lock.json updated with react-dom or other PRs 🤔

Looks working! And no console error will be shown in staging 👌


Explain corresponding Links

This PR explains hyperlinks from functions to their corresponding links.
I'd rather not warn as #6509.

Jenkins, test this please.

Oops. Wrong PR. This one not ready to test. 😅

Jenkins CI test (for commit 4006b683663dd9e43e20ff5fd132a2b12dad1e6a, target branch master) failed with status FAILURE.

@toslunar Status?

@Crissman

I'd like to fix docs of connection functions like this.
As we discussed #6509, activation functions like F.prelu could be warned.

If it looks good to you, I'll edit the other files.

Looks good. Please go ahead for the other files.

@toslunar, should I merge this separately, or would you like to add the other files?

Jenkins, test this please.

Jenkins CI test (for commit 364903cf8f16cf0dd3bfcf094926c0c68264c187, target branch master) failed with status FAILURE.

Jenkins and Travis errors look unrelated.

Shouldn't we make a backport?


fix: service worker path

Fix mockServiceWorker path for storybook.
Also, find a issue on Home page of the storybook https://github.com/FuelLabs/fuels-wallet/issues/336

still not working when testing in preview storybook...
Screen.Recording.2022-12-06.at.11.27.19.mov

No Assets and With Assets pages are never leaving loading state
With Assets should show balance

I open an issue to track it that is on description #336. We can move with this one and fix this one later.


Add a CONTRIBUTING.md?

What do you think about adding a CONTRIBUTING.md file to this repository? This is especially important for potential new contributors who might want to understand how the project works, who is working on it, how best to contribute etc. The Mozilla guide has some good ideas about what to include: https://mozillascience.github.io/working-open-workshop/contributing/

I think a good idea, and nice to get it in for version 1.0 of the gem. Would you mind working something up @arfon?

Done!


StreamGeometry ArcTo is not rendered on Linux/Gtk

Sample code used in my app:
var sg = new StreamGeometry();
using (var sgc = sg.Open())
{
    var a = WpfArc.FromXArc(arc, dx, dy);

    sgc.BeginFigure(
        new Point(a.Start.X, a.Start.Y),
        arc.IsFilled);

    sgc.ArcTo(
        new Point(a.End.X, a.End.Y),
        new Size(a.Radius.Width, a.Radius.Height),
        0.0,
        a.IsLargeArc,
        SweepDirection.Clockwise);

    sgc.EndFigure(false);
}

_dc.DrawGeometry(
    arc.IsFilled ? brush : null,
    arc.IsStroked ? pen : null,
    sg);

Arc rendering is almost working in GTK, there are some cases that arc is drawn incorrectly.


Update parse_resize.hpp to handle dynamic shapes

I have found that yolov4 and retinanet need to parse resize or upsample. Will need to update the onnx parser to handle dynamic shapes into these.

Will need a new shape operator for handling the ONNX shape operator with dynamic shapes

A new compiler pass or addition to split_single_dyn_dim is needed to convert unneeded shape operators to literals

parse_resize should be changed to do what is done in the simplify_reshapes, find_resize compiler pass for the nearest neighbor interpolation. This method should work for dynamic batch (there might be other limitations that have not yet been considered)

Broadcasting to new dimensions for upsampling
Use steps for downsampling

Another possible way to change parse_resize would be to have it work differently for dynamic shapes

gather over batch/channel dimensions
new operator that get simplified in split_single_dyn_dim

@CharlieL7 ,I have developed the resize_dynamic. link，and the kernel is here

So for nearest mode we can use reshape/multibroadcast/reshape for upsampling by integral values. Downsampling can be handled using the step operator.
To handle non-integral resizes, we can rationalize the number and use a ratio of upsample,downsample integrals. So if we want to upsample by 1.5 we can upsample by 3 and downsample by 2.
To handle the different rounding modes then we would use a different pointer offset(similar to slice). We can add these rounding modes to our step operator and it can automatically apply different pointer offsets as necessary.
As an example, we can start with a simple tensor of 2 elements:
[1, 2]

So to upsample to 1.5x, we would first upsample it using reshape/multibroadcast/reshape by 3x, which would give us a tensor with these values
[1, 1, 1, 2, 2, 2]

Then we apply a step of 2, which gives us:
[1, 1, 2]

This is the result using the floor rounding mode. If we want to use ceil rounding mode, then we would offset the pointer by 1(ie number of steps - 1). Its like doing a slice[axes={0},starts={1},ends{5}], this will yield a tensor like this:
[1, 2, 2]

Which is what the results will be when using ceil rounding mode. The other rounding modes can be implemented by using different offsets as well(n/2 +/- 1). In this case they dont produce a different result.
This should work for both static and dynamic shapes.

DynamicResize.docx

Draft roadmap attached.  This is still incomplete, so please comment and add/change material.

I've gone over Paul's Nearest algorithm and it looks good.  I think he's inverted the Ceiling and Floor options, but that's a detail that's easily checked out during coding.
The Step operation doesn't yet support dynamic inputs.  The others do.


Request : Hide the intil massege

i have one request : hide the print massege for Toy scanned every time you log in a character

Fixed in v<IP_ADDRESS>


Anyone give me a quick walkthrough on where I can customize things?

For example, font, where can I customize it? Sorry for the noob question.

You can overide in: assets/vendor/startbootstrap-clean-blog/scss/_bootstrap-overrides.scss
I hope this helps to point you in the right direction.

You can overide in: assets/vendor/startbootstrap-clean-blog/scss/_bootstrap-overrides.scss
I hope this helps to point you in the right direction.

Yes! And I can insert a


Future of black-screen

I just want to discuss about the future of black-screen.
I really like the project and would love to contribute to it, but I have some concerns.
I feel the whole project is too monolithic. It's both a terminal emulator and an interactive shell, not to mention its lack of a plugin eco-system.
I fear that this approach is only good for the short term where setup is easy, but in the longer term the project will become stale due to the lack of community.
Is there any possibility that we may split this project into the terminal emulator and a number of plugins?
Also there's hyper.js. Maybe we can even just convert this to some hyper plugins?
Would love to hear your thoughts!

There is a plugin architecture in place, just no way to load plugins, and all plugins live in the source tree. Making user loadable plugins is definitely an important feature, if you want to help. It would require some reworking of the build system to some degree, to make plugins actually be loadable, and installable at runtime, and we would also need to nail down the exact API we want for plugins. This is fairly difficult due to backwards compatibility concerns as well as the fact that the plugins use react, and we may want to be able to upgrade React versions without needing to change the plugins.
Personally I think one of the biggest strengths of black-screen is that the shell and terminal emulator are the same thing. Almost all of the cool features of black-screen would not be possible if they were separated (although having them be the same does have downsides as well) so I'm not likely to change that.
Hyper.js is cool, I'm always happy to see more approaches to a better terminal experience, but I think it's good to have multiple approaches be experimented with. The code is open source though, if you think this would be better as Hyper.js plugins you are welcome to make a fork and do that :)

This is fairly difficult due to backwards compatibility concerns

If you have concerns about backward compatibility, then Black-Screen should already be version 1.0.0 (as you can read on SemVer)

plugins use react, and we may want to be able to upgrade React

You can only upgrade React on major versions, then. Plugins will have to announce which specific Black-Screen versions they are compatible with. If there are plugins which are not compatible, display a warning and do not load them, simple as that. You really should leave stuff like, making plugins compatible with whatever technology you want to use, to the plugin authors. They have to stick to your standards to use your program, not the other way around.

In my experience, if a new version of some software doesn't work with old plugins, the plugins don't get updated, and because people like their plugins, they don't update their version of the software. This is a situation I would like to avoid.
We don't currently have compatibility concerns, but we expect to once we hit 1.0.0. We should hold off on going to 1.0.0 until we know how we are going to handle compatibility. Going to 1.0.0 without a plan will result in a mess.

In my experience, if plugin authors do not care to update their plugin, they do not care to fix bugs and hence their plugins will be a headache either way. If they don't care for their creation, it cannot be that important, to them, so why should it be to you?
I think that you can never avoid problems with plugin compatibility. That's why you should rather think about planning out major versions and sparingly do breaking changes. Collect as many breaking changes as possible over, say, a year, then merge them all at once and release the new major version. You might encourage plugin developers to use the "dev" or "master" branch to test their plugins before you release the commits to a stable branch. That way, important plugins can be made compatible from day one (especially if you communicate the release intervals well)

Not all plugins have bugs. Some are written properly from the start, and we want those to keep working.
I disagree that you can't avoid compatibility problems. I've worked on several projects that never broke backwards compatibility for any reason.

Not all plugins have bugs

All code has bugs. Period. No matter how well written and tested a project is, it will always have bugs. Thinking otherwise would be pretty naive. The reasons are various, but mostly because things happen a developer does not expect. Time keeps flowing and all around you people create things and interact and the world changes. For example, a black-hat might find a way to use your program for remote-code-execution. That's a bug and something you might not have seen in the code and all of your pretty unit testing tools will miss it completely. It has to be fixed pronto. If a project is stale, no fixes will happen and bugs will cause problems of all kinds. What about a memory leak, which only occurs after running the program for several weeks straight (JS closures are a b*tch in that regard)? Forget about all your tests and nice code structure.  I need it fixed. There are many other types of bugs you will have a hard time finding with static analysis. Stuff you don't think about during profiling and runtime analysis. Because you are human. There will be bugs and they need to be fixed. Projects need a living community, or they die.

I disagree that you can't avoid compatibility problems. I've worked on several projects that never broke backwards compatibility for any reason.

Sounds like you never worked on any big projects, yet. Even if your code does not break compatibility (which is stupid, because at some point, new tech arises which requires you to adapt), you were worrying about React, one of your dependencies, in the first place. Oh, and don't forget about Node.JS and Electron, which might change their API. Not breaking compatibility means you cannot upgrade to newer versions, which means that at some point, there will be no more bug fixes for your old version, which means that your project will be vulnerable to anything bad people come up with. Your only choice would be to do the fixing yourself, which is not pretty.
Do me a favor. Imagine your project in 20-30 years. How will it look? Will it still be compatible to whatever you write today? Will people still care about today's features? About today's React version? Will macOS, Windows and Linux still be the major targets?

Both Windows and Linux never break backwards compatibility and they are 2 of the largest projects in existence.

Both Windows and Linux never break backwards compatibility and they are 2 of the largest projects in existence.

So I can play my DOS games on Windows 10? Well, I think, I have news for you...

Personally I think one of the biggest strengths of black-screen is that the shell and terminal emulator are the same thing. Almost all of the cool features of black-screen would not be possible if they were separated

I think vscode has one of the best plugin models I've seen for an Electron based app.  I've never had an extension break because of a new release and it stays fast.  I tend to stick to the bigger plugins though, so YMMV.  They see to do a really good job of avoiding/communicating breaking changes and the API is so well targeted and performance is always good.  Most changes they make are additive.

@haoyangnz one example would be how we color the background of a job red if it exits with status code != zero. Another would be how we have a button to send SIGKILL to a job. A third would be how we visually separate the "command line" (the part where you type text) from the job output.
@mizzle-mo I'll look into it. I think once challenge that we have is that plugins can render React components. Maybe we need to provide some extremely stable subset of the React API or something.
@minecrawler I don't have windows 10, but I have had previous versions of windows and never had any trouble running DOS programs on them. DX12 vs 9 and .NET4 vs 2 are different. Applications built against DX9 or .NET2 will continue working when you upgrade Windows. The analogy here is Black Screen : Black Screen Plugins :: Windows : Windows Applications, not Black Screen : Black Screen Plugins :: Windows Applications : DX/.NET


8405 clicking upgrade is not running correct images

https://github.com/Shippable/pm/issues/8405
when a user clicks Upgrade, admiral should bring up the services with the updated release tag

this operation should fail if there are no images for the release

right now, all services restart with master tag and not the release tag

this is probably happening because the release version in admiral.env and database is not changing to correct value

the upgrade workflow needs to be updated to fix this. The core problem here is that admiral set the release version globally which makes it impossible to switch versions without a restart. we need to update admiral to handle switching between release versions without restarting. here are the steps

update admiral routes and boot logic

update admiral.app.js to not set release version globally
update all the route handlers to get the release version from database systemSettings table.

update admiral boot command

update ./admiral.sh command to not set release version in admiral container
RELEASE variable in admiral.env should always be updated to either the tag or master, if branch name is not present
RELEASE variable in parseArgs.sh should be set from admiral.env

update GET /api/versions to return the value of version from admiral.env. This version implies that user has already updated admiral container to the new version and now can update the rest of the system

the Upgrade section in the UI should show only if the version returned from GET api/versions is different from version stored in db

When user clicks  Upgrade button, first set the version in database and then execute all the steps we're executing right now. All steps should use the new version since that has been updated in the database

this is complete, closing


TensorFlow Reddit Dataset to DataFrame Throws Error

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 18.04
TensorFlow installed from (source or binary): source
Python version: 3.6.9
TensorFlow version (use command below):

>>> tf.version.GIT_VERSION
'v2.4.0-49-g85c8b2a817f'
>>> tf.version.VERSION
'2.4.1'

Describe the current behavior
I want to load the tfds reddit dataset and convert it to a dataframe. The below standalone code throws the following error:
  File "/home/rylan/Documents/FieteLab-RCRP/exp_03_language_modeling/main.py", line 36, in load_dataset
    reddit_dataframe = tfds.as_dataframe(reddit_dataset)
  File "/home/rylan/Documents/FieteLab-RCRP/rcrp/lib/python3.6/site-packages/tensorflow_datasets/core/as_dataframe.py", line 218, in as_dataframe
    df = StyledDataFrame(rows)
  File "/home/rylan/Documents/FieteLab-RCRP/rcrp/lib/python3.6/site-packages/tensorflow_datasets/core/as_dataframe.py", line 144, in __init__
    super().__init__(*args, **kwargs)
TypeError: object.__init__() takes no parameters
python-BaseException

Standalone code to reproduce the issue
import tensorflow as tf
import tensorflow_datasets as tfds

reddit_dataset = tfds.load(
    'reddit',
    split='train',
    shuffle_files=False,
    download=True,
    data_dir=data_dir)
assert isinstance(reddit_dataset, tf.data.Dataset)
reddit_dataframe = tfds.as_dataframe(reddit_dataset)

The error goes away and a sensible result is produced if I remove these two lines https://github.com/tensorflow/datasets/blob/master/tensorflow_datasets/core/as_dataframe.py#L222-L223 and add df = pd.DataFrame(rows).

Ok upon further investigation, I found the cause of the error. I'm using Tensorflow Datasets 4.2.0, which has the following at the top of the as_dataframe.py file:
try:
  import pandas  # pylint: disable=g-import-not-at-top
  import pandas.io.formats.style  # pylint: disable=g-import-not-at-top
  DataFrame = pandas.DataFrame
except ImportError:
  DataFrame = object

The second import statement was failing, causing DataFrame to be set to object.  I noticed this import was removed in the most recent commit.
https://github.com/tensorflow/datasets/commit/81e8ec79e9782f6eb5a93689bef9a5a076a3c2d4
For anyone else with a similar problem, the solution is to remove import pandas.io.formats.style.


Update stable version in repo from 0.6.4 to 0.6.6

Think about update stable version to 0.6.6
Version: stable=0.6.4 (107 days old) => latest=0.6.6 (23 days old)
Installs: stable=1161 (62.49%), latest=101 (5.44%), total=1858
Click to use developer portal
Click to edit
Do not close this issue manually as a new issue will be created if condition for update still exists.
Please drop a comment if any reason exists which blocks updating to version 0.6.6 at this time.
Note: This is an automatically generated message and not personally authored by bluefox!
@mcm1957 for evidence

waiting for next release
see https://github.com/copystring/ioBroker.roborock/issues/590#issuecomment-2272043239

Unstale

Yes. Von mir aus gerne 😁

Falsches issue?

Nö, ich dachte man kann hierzu seine Meinung abgeben :-)
Kann auch sein, dass ich diesen Issue noch nicht verstanden habe ;-)

waiting for next release
see https://github.com/copystring/ioBroker.roborock/issues/590#issuecomment-2272043239

I just created 0.6.7 with lots and lots of bug fixes. This should be a good release 🙏

wait for 0.6.7

I requested 0.6.16 to be set as stable. See https://github.com/ioBroker/ioBroker.repositories/pull/4141


Create solid-panel.md

Collected all information from previous pull requests and .md files in solid/information. To be merged by the Solid Leader.

Will close this as the content as moved to new proposal that @justinwb and I wrote together with input from others that is lighter midway version.


The ( HOW DO I SET IDENTITY? ) Link doesn't take you anywhere

the last question on this page:
https://nft.kodadot.xyz/rmrk/faq
take you to this link:
https://guide.kusama.network/docs/en/mirror-learn-identity#docsNav
error: Page Not Found

im not a coder, but i think this is important for new people on the platform

go to the https://kodadot.xyz/identity and you can set identity right away from kodadot now