Checkpoint spec compliance: Incorrect key ID for non-ECDSA keys

Background
https://github.com/C2SP/C2SP/blob/main/signed-note.md defines the specification for a signed note, which is the format of a checkpoint. Note that this specification was only recently created. When checkpoints were added to Rekor, we followed the code for Go's checksum db note format, which is the signed note format - docs, code
The signature is the following format:
— <key name> base64(32-bit key ID || signature)
where key ID is the following format, roughly the truncated hash of the key name, signature scheme, and public key:
key ID = SHA-256(key name || 0x0A || signature type || public key)[:4]
Go's checksum db note code only defines a verifier for ed25519 keys (code), again aligning with the spec, where signature type = 0x01. It does not support ecdsa keys.
For historical reasons (citation needed) and as noted in the spec, ecdsa key IDs are the truncated hash of the DER encoded public key in SPKI format (code, with the truncation happening here).
Issue
When Rekor generates a signed note, it generates the key ID as a truncated DER encoded public key hash regardless of signature type. ecdsa is spec compliant, but ed25519 and RSA is not. The impact of this is if we were to switch to ed25519 or RSA signing keys, Rekor checkpoints would not be verifiable by omniwitness, armored witness or any other upcoming witness implementations.
The other issue is that the c2sp spec doesn't define support for RSA. There is an issue tracking this request, but general consensus is a lack of interest in supporting RSA due to additional signature support for witnesses, RSA vulnerability concerns and key/signature size. For public instances that could join a witness network, we should strongly recommend using ecdsa or ed25519 keys. For private instances, RSA can still be supported using the 0xff identifier type as per the spec.
Fixes
Given the last time I made a change to the checkpoint format, dropping the timestamp, it impacted clients, I want to make sure we thoughtfully roll this out.
Clients will need to add support for parsing signed notes following the spec, particularly computing the key ID differently for ed25519 and RSA keys. If you want to avoid any chance of breakage for private deployments that are currently using these key types, you could fallback to the DER encoded public key ID.
However, I don't know if clients were using the key ID to verify checkpoints. If the client was simply dropping the 32-bit key ID from base64(32-bit key ID || signature) before verifying the signature, this change seems quite safe to do. For example, for sigstore-go (which uses the Rekor library), we're doing just that - Base64 is the signature without the key ID (Hash). Technically this isn't following the spec, as the key ID should be compared against a known key. That doesn't seem like a requirement for Sigstore though, more for witnesses, since we have a way of distributing trusted keys. (Edit: this is not true for other clients, so we will need client changes)
For server side changes, given the public instance has only used ecdsa, we could fix the format for ed25519 and RSA signing keys without any impact to clients. If we want to do this in a non-breaking way, we would need to introduce the new checkpoint format in another response field for the /log API, though I don't like that approach as much as it'll complicate client logic for fetching a checkpoint and prolong this fix.

cc @bdehamer @loosebazooka @woodruffw (also @codysoyland, but this'll be handled for Go with the fix in Rekor, since sigstore-go uses Rekor's verifier)
Sorry for the long wall of text! The tl;dr is that I want to change the checkpoint key ID format for ed25519 and RSA keys. If your client is simply dropping the key ID, which is the prefix for the checkpoint signature, then this change is really just a no-op for your client. If you are parsing the key ID, then you could need to update to construct the key ID differently based on the signature type.
Let me know if this is going to be an issue and if we should go with a non-breaking slower rollout. This is not something we have to rush out, just something to fix before we have more public logs.
@woodruffw: For sigstore-python, it looks like you use the log ID (which is the sha256 hash of the DER encoded SPKI pub key) in https://github.com/sigstore/sigstore-python/blob/main/sigstore/_internal/rekor/checkpoint.py#L217-L219, and then compare here - https://github.com/sigstore/sigstore-python/blob/main/sigstore/_internal/rekor/checkpoint.py#L173-L174. so this would need to be changed
@bdehamer: For sigstore-js, https://github.com/sigstore/sigstore-js/blob/main/packages/verify/src/timestamp/checkpoint.ts#L91-L93 - looks like you do something similar, where you find the correct key based on the key ID/key hint and compare it to the log ID. So this would need to be updated
@loosebazooka  - For sigstore-java, looks like you are comparing key IDs in https://github.com/sigstore/sigstore-java/blob/9ec514d10544f93083471f23c44c828b2ba3f9f4/sigstore-java/src/main/java/dev/sigstore/rekor/client/RekorVerifier.java#L158-L166, so this would need to be updated.

As @haydentherapper already noted, sigstore-js is parsing the key ID from the signature and using that to identify the appropriate key. My vote is definitely for a VERY slow rollout of any change which is going to break the current implementation.
The last change to the checkpoint format caused a lot of grief in npm land and I'm afraid that if we drop another breaking change again so soon after the last one we run the risk of package developers deciding that it's not worth the hassle.

Sorry about that rollout, we had assumed the other content in the signed note was considered optional.
The good news with this change is that there would be no changes to metadata produced from the public instance. I am unaware of any other public logs.
To make sure we don't break anyone, let's do the client changes (I can file bugs in each repo to track the change), and after a few months, we can roll out the change here. We'll also document in Rekor that an ecdsa key should be preferred and must be chosen if you will host a public log. How does that sound?

Summarizing to make sure I understand:

For non-ECDSA keys, the key ID is defined as SHA-256(key name || 0x0A || signature type || public key)[:4], where public key is DER(SPKI(raw public key))
For ECDSA keys, the key ID is not defined, but Rekor chooses to use SHA-256(public key)[:4]
sigstore-python currently only expects ECDSA-based tlogs, and so does (2) unconditionally

Is that correct?

Wasn't there also something about using a different style of logid for rekor? I can't seem to remember details, but there was no guarantee it was going to continue to be a hash of the public key like CT.

Yea, the CT v2 RFC defined log IDs as OIDs rather than a hash of a public key. The idea being that you might want to reuse a public key across logs but have each log have its own identity. I don't think we'll move away from the log ID being the hash though as most tools expect this, so instead we'll rotate the key the next time we create a new log.

For non-ECDSA keys, the key ID is defined as SHA-256(key name || 0x0A || signature type || public key)[:4], where public key is DER(SPKI(raw public key))
For ECDSA keys, the key ID is not defined, but Rekor chooses to use SHA-256(public key)[:4]

Unfortunately, reading more, the public key encoding is a bit messy.

ed25519 keys are the 32-byte public key byte array, which would be for 0x01 ed25519 checkpoint signatures and 0x04 witness cosignatures (which mandate ed25519).
For 0x02 ECDSA checkpoint signatures and 0x05 RFC6962 checkpoints, it is SHA256(DER(SPKI(raw public key))). (Note that there is an open issue to restrict the new RFC6962 checkpoints to only ecdsa, to not deal with RSA)
For RSA, for 0xff we are on our own. I would recommend SHA256(DER(SPKI(raw public key))).

For ECDSA, it is defined in the spec. It wasn't Rekor that decided the different format for ecdsa, I believe it was either RFC 6962 or some of the original witness work, and the spec didn't want to break existing logs using ecdsa.

sigstore-python currently only expects ECDSA-based tlogs, and so does (2) unconditionally

If you aren't handling RSA or ed25519, then this is even better, as it wouldn't be a breaking client change.

I just reread what I wrote, and it's kinda messy. so tldr

ed25519-signed checkpoint key ID: SHA-256(key name || 0x0A || 0x01 || 32-byte Ed25519 public key)[:4]
ecdsa-signed checkpoint key ID: SHA-256(DER(SPKI(raw public key)))[:4]
RSA checkpoint key ID: SHA-256(key name || 0x0A || 0xFF || SHA-256(DER(SPKI(raw public key))))[:4]

RSA is up for debate if anyone disagrees, since the spec doesn't define RSA keys.

Wow, what a mess 😄
So, to round it off: clients that want to handle key IDs correctly will need to:

Stop assuming that everything is ECDSA
Propagate the key type from its representation in TrustedRoot.tlogs[].public_key
Use the key type to determine the key ID algorithm to apply

Did I get that right? If so, that'll be a slightly involved patch to sigstore-python, but not too bad 🙂

RSA is up for debate if anyone disagrees, since the spec doesn't define RSA keys.

Please direct me to another issue if this is the wrong place, but: is there a demonstrated (public or private) desire for RSA-based tlogs? Given that RSA sigs are much larger and that RSA signing is generally slower, I was under the impression that it wasn't commonly used for tlogs (despite RFC 6962 allowing it).
With that being said, if RSA support is already decided, I have no objection to that key ID format.

Stop assuming that everything is ECDSA

Correct, particularly adding support for ed25519.

Propagate the key type from its representation in TrustedRoot.tlogs[].public_key
Use the key type to determine the key ID algorithm to apply

Correct. Note that at some point, we'll also want to handle 0x04 co-signed checkpoints, signed with ed25519 as per the spec. So the key ID gives you both the signature algorithm and the structure that you're verifying, a checkpoint vs witnessed checkpoint. But that's forward looking

Please direct me to another issue if this is the wrong place, but: is there a demonstrated (public or private) desire for RSA-based tlogs? Given that RSA sigs are much larger and that RSA signing is generally slower, I was under the impression that it wasn't commonly used for tlogs (despite RFC 6962 allowing it).

Actually the opposite, RSA is not preferred. I brought this up in https://github.com/C2SP/C2SP/issues/63, and the consensus was a) concerns about RSA vulns particularly for PKCS#1v1.5, b) key/sig size, c) another alg to support. I did point out RFC 6962 allows for it, but since RFC 6962 doesn't have support for checkpoints and C2SP is focused on improving Certificate Transparency, they're fine going off-spec.
So if we want to say no RSA for Rekor, I'm OK with that. Rekor does support it currently so we might get some pushback from private instances, so I'd want to ask around. But if we're already in the state where most clients are just supporting ecdsa, then it's not really a breaking change.

I vote no rsa support unless it's defined in spec.

I was just looking through the implementation in sigstore-js trying to understand what may need to change.
Currently, it grabs the first four bytes of the checkpoint signature and uses that to find the correct key from the TrustedRoot by looking at the first four bytes of the listed key IDs.

At no point does it attempt to calculate the key ID.
Would this change if Rekor were to use an ed25519 key? Or could we assume that the key ID listed in the TrustedRoot would always reflect the appropriate format?

Interesting, yeah so are logId and keyHint going to use the same transformation over the key? Is it safe to use logId? Or should it always be calculated?

@bdehamer, that's a good point. For context, the reason we chose the log ID to be the SHA-256 hash of the DER encoded SPKI public key was to follow RFC 6962. Fulcio's CT log already set the log ID to be that, so we followed the same practice for Rekor. To one of @loosebazooka's questions earlier on, the log ID can be whatever we choose it to be. It probably shouldn't be the key, because otherwise you are forced to rotate the key with every log sharding to maintain unique IDs. But we were trying to follow an existing related spec.
For ed25519, we can either:

Change https://github.com/sigstore/protobuf-specs/blob/main/protos/sigstore_common.proto#L136-L139 to say that the log ID's key ID is different for ed25519, equaling SHA-256(key name || 0x0A || 0x01 || 32-byte Ed25519 public key). Return this different log ID in the checkpoint and as part of the Rekor entry response. Also this impacts SET verification since the log ID changes.
Leave the log ID as-is, and change only the checkpoint key ID

Impacting the SET verification is what concerns me the most. I believe there are assumptions that the log ID always is SHA256(DER(SPKI(pubkey))) in most clients. I'd lean towards the second, making this change only for checkpoints.
Tangential, for RSA, I'm planning to continue to follow what we're doing for ECDSA for computing the key ID. I don't want to drop RSA support entirely in case someone is using it and I think this means existing client implementations will continue to work without any changes. I'll just discourage RSA for public logs, and we'll make no guarantees that clients implement RSA support. Lemme know if anyone disagrees.

Also, there is another option, which is simply to state that publicly witnessed Rekor logs must use ecdsa.

@loosebazooka and I were chatting today about this, and came up with a good compromise that avoids clients needing to know this computation - let's include the checkpoint key ID (the truncated hash) as an optional field in the trust root TransparencyLogInstance. Clients can then treat the checkpoint key ID as an arbitrary string rather than a constructed identity.
I would vote that we make it optional to avoid making this a breaking change to the trust root. If the checkpoint key ID is not set, then the client should assume checkpoint key ID == log ID (which is the case for ecdsa and RSA). For new ed25519 logs, the checkpoint key ID must be set.
What do you think @bdehamer @woodruffw?

I like that idea! That makes things pretty simple on the clients side 🙂

Sounds great, love it!


Set face down state based on card's actual state.

Instead of assuming the card should be dealt face down, let the card's state determine that. Cards can be drawn or dealt face down, so we can let the user decide based on their actions.
Additionally, flip the card based on card flips in the fancy display.
(I've already almost got this implemented for an upcoming PR.)

Latest release solves this!  A user can configure how/when the actual state determines the displayed face in the viewer, variable by actions.  Choosing "Source stack determines face" for the Deal action mean face-down cards will be dealt and viewed face-down.
Please test and lmk if there are any issues.

Closing this, as plenty of time has elapsed, and a new Foundry version is out.  I'm calling this fixed, per my own tests.


Fix typo

JET.jl detected this typo during a test in ImplicitDifferentiation.jl

Codecov Report

Merging #13 (120bfad) into master (609201f) will not change coverage.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##            master       #13   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           34        34
=========================================
  Hits            34        34

Impacted Files
Coverage Δ

src/ForwardDiffChainRules.jl
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


does not use output.path option from webpack.config.js

Operating System: Macos 10.13.6
Node Version: 10.8.0
NPM Version: 6.3.0
webpack Version: 4.16.15
webpack-serve Version: 2.0.2

Expected Behavior
Webpack-serve should use the output.path option from webpack.config.js. It was working fine with webpack-serve v.0.3.1.
Actual Behavior
With the current version of webpack-serve the compiled files (scripts.js and styles.css) are outputed at the root of the project, and not the path specified in the output.path option of webpack.config.js
Code
  // webpack.config.js
const dev = process.env.NODE_ENV !== 'production'

module.exports = {
  mode: dev ? 'development' : 'production',
  context: __dirname,
  entry: './src/scripts.js',
  output: {
    path: path.resolve(__dirname, 'dist'),
    filename: 'scripts.js'
  }
…

How Do We Reproduce?
install this repo: https://github.com/MTES-MCT/camino-landingpage, update webpack-serve to version 2.0.2 in package.json and run npm install and npm run dev.
The files scripts.js and styles.css should be at /dist/… but are at /…

I found a solution adding an entry to webpack.config.
  serve: {
    devMiddleware: {
      publicPath: '/dist/'
    }
  }

Not sure why this is necessecary. I think it should work with output.path.

DEPRECATED. Please use webpack-dev-server (he is in support and update mode again). Feel free to create a issue if some features are not implemented in webpack-dev-server.
Why deprecated webpack-serve ?

The author stopped developing the package.
Two development servers are misleading for developers.
Hard to maintain two packages with same purpose.
Some dependencies are not available to fixes/implement new features/etc (https://www.npmjs.com/package/webpack-hot-client and https://github.com/shellscape/koa-static) and there's nothing we can do here.
webpack-dev-server is stable.

Thanks for using webpack! We apologize for the inconvenience. In the future, we will avoid such situations.


add todays date to lunchguide url to avoid lunch bugs

I like this change, it is really annoying when Lunchguiden bugs out and shows me the wrong food


Array uniforms wont work on Flutter web

Steps to reproduce

Create a Flutter project from scratch or use the simple shader sample.
Add a fragment shader file and use array uniforms
Try to run it on the web (flutter run -d chrome)

Expected results
It whould run the project normally.
Actual results
It fails as with an error message similar to:
══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
The following IndexError was thrown during paint():
RangeError (index): Index out of range: index should be less than 3: 3

The relevant error-causing widget was:
  CustomPaint CustomPaint: [...]/lib/main.dart:34:37

When the exception was thrown, this was the stack:
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:3       throw_
dart-sdk/lib/_internal/js_dev_runtime/private/js_array.dart 610:7                 _set]
lib/_engine/engine/canvaskit/painting.dart 368:5                                  setFloat
packages/flutter_shaders/src/set_uniforms.dart 62:5                               setFloat
packages/flutter_shaders/src/set_uniforms.dart 67:7                               setFloats
...

Code sample
Full example here:
https://github.com/renancaraujo/array_uniforms_issue
Code sample:
Code sample
// dart code
import 'dart:ui' as ui;

import 'package:flutter_shaders/flutter_shaders.dart';

// ...

  void paint(Canvas canvas, Size size) {
    shader.setFloatUniforms((value) {
      value.setSize(size);
      value.setFloats([
        0.1,
        0.2,
        0.3,
        0.4,
        0.5,
        0.6,
        0.7,
        0.8,
        0.9,
        1.0,
      ]);
    });

    final paint = Paint()..shader = shader;
    canvas.drawRect(
      Rect.fromLTWH(0, 0, size.width, size.height),
      paint,
    );
  }

// shader code

#include <flutter/runtime_effect.glsl>

uniform vec2 uSize;
uniform float[10] uFloats; // array uniform

out vec4 fragColor;

void main() {
    vec2 pos = FlutterFragCoord().xy;
    vec2 uv = pos / uSize;

// ...

Screenshots or Video
No response
Logs
Logs
══╡ EXCEPTION CAUGHT BY RENDERING LIBRARY ╞═════════════════════════════════════════════════════════
The following IndexError was thrown during paint():
RangeError (index): Index out of range: index should be less than 3: 3

The relevant error-causing widget was:
  CustomPaint CustomPaint: [...]/lib/main.dart:34:37

When the exception was thrown, this was the stack:
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:3       throw_
dart-sdk/lib/_internal/js_dev_runtime/private/js_array.dart 610:7                 _set]
lib/_engine/engine/canvaskit/painting.dart 368:5                                  setFloat
packages/flutter_shaders/src/set_uniforms.dart 62:5                               setFloat
packages/flutter_shaders/src/set_uniforms.dart 67:7                               setFloats
...

Flutter Doctor output
Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.16.5, on macOS 14.1.2 23B92 darwin-arm64, locale en-GB)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.85.1)
[✓] Connected device (3 available)
[✓] Network resources

Extra info:
The code runs normally on  ios, android, macos, windows and linux on both skia and impelller. The issue only happens on the web.
Bug reproducible on master.

This looks similar to https://github.com/flutter/flutter/issues/128774 and it's marked as a duplicate of https://github.com/flutter/flutter/issues/116900. But this is only reproduced on web, I will keep this open to have other's thoughts. Thanks for the report.

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.16.6, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.16.6 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 46787ee49c (28 hours ago), 2024-01-09 14:36:07 -0800
    • Engine revision 3f3e560236
    • Dart version 3.2.3
    • DevTools version 2.28.4

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.14.3

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

[✓] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio Hedgehog.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (3 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos            • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)     • chrome           • web-javascript • Google Chrome 120.0.6099.216

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.19.0-3.0.pre.49, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.19.0-3.0.pre.49 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 085aaa5d63 (55 minutes ago), 2024-01-10 21:13:27 -0500
    • Engine revision 42e3e02361
    • Dart version 3.4.0 (build 3.4.0-15.0.dev)
    • DevTools version 2.31.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.14.3

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

[✓] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio Hedgehog.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (3 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos            • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)     • chrome           • web-javascript • Google Chrome 120.0.6099.216

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Hello mr @jonahwilliams, i tried to fix this on https://github.com/flutter/engine/pull/49754 where i suspect the source of the problem is. LMK if thats right


Integration of OGC Coverages API Support into eoAPI via Stacture [#2309]

Objective: Enhance the eoAPI platform to support the OGC API Coverages standard, enabling users to access, manipulate, and manage raster data such as grids, remote sensing, and multidimensional data cubes.
Lead Contributor: EOX
Priority: 2 or 3
Upper Bound Estimate: 5
Lower Bound Estimate: 3
Requirements:

BR055 – Provide services for retrieval of coverages via standard interfaces including OGC API Coverages, OGC WCS

stacture v0.0.1 integrates the core functionality of OGC API Coverages
Milestone v0.0.1 is in our internal gitlab instance: https://gitlab.eox.at/vs/stacture/-/milestones/4#tab-issues

I think this was closed on accident.


python3Packages.ppscore: init at 1.1.1

Motivation for this change
ppscore - a Python implementation of the Predictive Power Score (PPS)
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Ran 0 tests in 0.000s

Please either fetch from GitHub to include the tests or convert them to importCheck.

@SuperSandro2000 thanks for the feedback!

Result of nixpkgs-review pr 102352 run on x86_64-linux 1

2 packages built:

python37Packages.ppscore
python38Packages.ppscore

Result of nixpkgs-review pr 102352 run on x86_64-darwin 1

2 packages built:

python37Packages.ppscore
python38Packages.ppscore


Custom font to searchview hint and text

Hi @lapism
How can i set custom font to the searchview hint and text??
Thanks

No, this function is not available. But I am open to every pull request ;)

Added in 3.3.


Superfunctors clear cache

Use __builtin___clear_cache() (see https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html) after writing the thunk into memory.

Done


Use new sonar task instead of sonarqube

Is your feature request related to a problem? Please describe.
When I run an analysis this warning is shown:
Task 'sonarqube' is deprecated. Use 'sonar' instead.

Describe the solution you'd like
Please migrate configurations to use sonar, make it compatible with existing name.

Sonar task is working on generated projects


URL's containing # character when using API not shortened correctly

Technical details

YOURLS version: 1.6
PHP version: 5.4.40

Reproducible Bug Summary

Use API to shorten URL which contains a '#' in the URL
The # and any characters following it in the URL are lost

This is a bug because...  If using the shortener directly, the '#' and any further characters after it are saved successfully. If using the API the '#' and following characters are lost.

How does this work (or not) using latest ?

In 1.7 shortening urls with '#' works correctly.

@lpiob Thanks for the feedback!
@JoebeeKenobi Please reopen this issue if it still occur with your updated version.


Don't show input if the input is thrashed

also see #195. Any ideas, @arekkas? Is the same problem with hints. Not showing them if they are trashed is rather easy but not sure how to let the user create a new input if there is still a trashed one...

superseded by #370


Deprecate py 3.5 and below

Fixes https://github.com/Grokzen/pykwalify/issues/161
Deprecate imp module
remove support of py3.5 and below

@Grokzen ?

@Grokzen ?

@jochman This repo is on a slow maintenance mode right now. PR:s and issues will be handled when i get some free time to work on this repo. Repeated pining me will not do anything other then annoy me. From a quick look at these changes they look good.

Hey there! Thanks both of you for your work on this. I'm sure you're very busy, so whenever you get a free moment, I'd also appreciate a review/merge on this. Looking to update the dependency in the Tavern project to resolve warnings. 🙇


Poppler 23.07.0

Package for poppler v23.07.0
Checklist:

[x] I have confirmed that poppler-feedstock has been updated.
[x] I have bumped package.sh POPPLER_VERSION to the current build.

Wow this actually worked first try for once! Thanks @Fdawgs again for keeping on top of this I really appreciate it!


JS files not appearing in 'www' folder

Version of HACS

Describe the bug
A clear and concise description of what the bug is.
I've followed the instructions to set up hacs on my home assistant which is running on a rpi3
My HACS version is : 0.5.1
Home Assistant version : 0.93.2
I can click install on the items in the store - for example i've tried button-card and secondaryinfo-entity-row which I've been using but without any sort of updates
They appear in my overview as installed, but when I look in www (the full path is /home/homeassistant/.homeassistant/www like the output tells me it should be)
I don't see any newly created files
I've checked the logs and found the following
2019-06-05 16:00:19 [custom_components.hacs.frontend] Tried to serve up '/home/homeassistant/.homeassistant/www/community/button-card/button-card.js' but it does not exist
2019-06-05 16:00:19 [custom_components.hacs.frontend] there was an issue trying to serve button-card/button-card.js - Not Found
Debug log

2019-06-05 16:00:19 [custom_components.hacs.frontend] Tried to serve up '/home/homeassistant/.homeassistant/www/community/button-card/button-card.js' but it does not exist
2019-06-05 16:00:19 [custom_components.hacs.frontend] there was an issue trying to serve button-card/button-card.js - Not Found```

Try a reinstall of one of them, then paste the entire log (by using hastebin)

Try a reinstall of one of them, then paste the entire log (by using hastebin)

Thanks for the quick reply - bit new to all this so haven't got (or know) what hastebin is - Should I copy/paste the entirre log from the settings -> open log button?

https://hastebin.com/
And yes, as long as you do it after the progressbar that indicate that it's working are gone.

https://hastebin.com/
And yes, as long as you do it after the progressbar that indicate that it's working are gone.

Ah I've found the error message - its saying it can't do it due to permissions - just checked and my www folder is assigned to root - I'll change it to homeassistant (my user) and try again

It's working now - apologies ! Closing the bug


Various improvements

Nice work, this is a really helpful module!
I needed to make some changes to get this working for our app, and made some improvements along the way:

.json files are stored as valid JSON - Objects are now stored in a comma-separated JSON array
Updated to latest version of s3-streaming-upload module, which uses newer AWS APIs for uploading
Switched from Underscore to Lodash
Updated to latest version of all other dependencies
Changed minimum Node version to 0.10.0
Pass start/end/duration timing data into start-backup and end-backup event callbacks
Use UTC timezone for backup timestamps
Fixed a bug with stopOnFailure option
Added a debug option (forwarded to s3-streaming-upload module)
Added an indentJSON option to store backup JSON with tab indentation

Stuff missing from this PR:

Docs
Tests (unit tests don't seem to be set up yet)

@adambiggs thanks for the sharing all the work that went into this PR! I really appreciate it. I'll get this reviewed and merged in the next week or so. Thanks again!

Any updates on this? We have some more contributions planned if this project is still being actively maintained.

@adambiggs - sorry for the delay. @benblair and I have been working out who will own this going forward and it has taken some time.
I will own this - I just need to get the repo transferred to my ownership then I'll merge this in and will start actively maintaining it.
Thanks for the contributions!

Great news @dylanlingelbach!
Originally I tried to implement DDB backups using Amazon's recommended DataPipeline setup... But found it to be a total waste of time. Even when I finally got DP working, it was ridiculously slow and inefficient.
In comparison, this project is a total joy to use! I hope it keeps going strong.

@adambiggs - yeah, dealing with DataPipeline is exactly what led me to write this. I was never able to get it working with any degree of reliability.
@benblair is offline for a few days so I don't have an exact date of when I can take care of this yet, but I'm on top of it. Feel free to poke me in a week if you haven't heard from me.

Sounds good. :beers:

@adambiggs - one comment on the change to save the file as a single JSON object instead of a JSON object on each line. Once we get that resolved I'll get this merged in.
Thanks for your patience!

@adambiggs - was just browsing through things and realized we never resolved this. Does my comment make sense? Would still like to get this in if you are still interested.

Thanks for the reminder @dylanlingelbach, I got busy with work and forgot about this PR!
Your comments make total sense. I'll try to update the PR at some point today.

@dylanlingelbach I rebased this PR, removing the JSON formatting stuff and updating NPM packages to current latest versions.
I'm wondering though, do you have a separate library for restoring the backups created by this one? I want to make sure we have a solid plan in case we ever need to do a restore.

@adambiggs - awesome, thanks!
I don't have a separate library for restoring, but it should be very simple. Just read in the backed up file line by line and put each line to Dynamo.

Published as version 0.3.0


ose-on-aws.py fails to complete, throwing fatal unreachable through ansible

Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT
BUG REQUEST INFO:
Environment:

Cloud provider: AWS

OS:

Linux 4.13.4-200.fc26.x86_64 x86_64
NAME=Fedora
VERSION="26 (Workstation Edition)"
ID=fedora
VERSION_ID=26
PRETTY_NAME="Fedora 26 (Workstation Edition)"
ANSI_COLOR="0;34"
CPE_NAME="cpe:/o:fedoraproject:fedora:26"
HOME_URL="https://fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=26
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=26
PRIVACY_POLICY_URL=https://fedoraproject.org/wiki/Legal:PrivacyPolicy
VARIANT="Workstation Edition"
VARIANT_ID=workstation```

- **Version of Ansible:** <IP_ADDRESS>

- **Version of Jinja:** Jinja2==2.9.6

- **Version of Shade:** (`pip freeze | grep -i shade`)

**Openstack-ansible-contrib version (commit) (`git rev-parse --short HEAD`):**
git rev-parse --short HEAD
f97ddf9

**Copy of used inventory files and custom variables (please omit your secrets!):**
created automagically using the ec2.py script.

**Command used to invoke ansible**:
./ose-on-aws.py --keypair=<name of keypair in aws> --public-hosted-zone=<zone> --deployment-type=origin --ami=ami-6d1c2007 \
--github-client-secret=<secret> --github-organization=<orgName> \
--github-client-id=<githubId> --stack-name=<stack name>

**Output of ansible run**:
```fatal: [ose-app-node03.<hosted-zone>]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ", "unreachable": true}
fatal: [ose-master01.<hosted-zone>]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Shared connection to ose-master01.<hosted-zone> closed.\r\n", "unreachable": true}
fatal: [ose-app-node02.<hosted-zone>]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ", "unreachable": true}
fatal: [ose-master03.<hosted-zone>]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Shared connection to ose-master01.<hosted-zone> closed.\r\n", "unreachable": true}
fatal: [ose-app-node01.<hosted-zone>]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ", "unreachable": true}
fatal: [ose-infra-node02.<hosted-zone>]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: ", "unreachable": true}

localhost                  : ok=20   changed=5    unreachable=0    failed=0
ose-app-node01.<hosted-zone> : ok=69   changed=17   unreachable=1    failed=0
ose-app-node02.<hosted-zone> : ok=69   changed=17   unreachable=1    failed=0
ose-app-node03.<hosted-zone> : ok=69   changed=17   unreachable=1    failed=0
ose-infra-node01.<hosted-zone> : ok=191  changed=72   unreachable=0    failed=0
ose-infra-node02.<hosted-zone> : ok=69   changed=17   unreachable=1    failed=0
ose-infra-node03.<hosted-zone> : ok=191  changed=72   unreachable=0    failed=0
ose-master01.<hosted-zone> : ok=349  changed=137  unreachable=1    failed=0
ose-master02.<hosted-zone> : ok=405  changed=159  unreachable=0    failed=0
ose-master03.<hosted-zone> : ok=282  changed=113  unreachable=1    failed=0

INSTALLER STATUS **************************************************************************************************************************************************************************************************
Initialization             : Complete
etcd Install               : Complete
NFS Install                : Not Started
Load balancer Install      : Not Started
Master Install             : Complete
Master Additional Install  : Complete
Node Install               : Complete
GlusterFS Install          : Not Started
Hosted Install             : Complete
Metrics Install            : Complete
Logging Install            : Complete
Service Catalog Install    : Not Started
Management Install         : Not Started```

**Anything else do we need to know**:

Not sure if it is supposed to run through the rest of these as well, but it gets caught there each time irregardless of the completion of the script or not.

Is it the script or am I not providing the correct values?

Did you setup the .ssh/config based on the environment?

I did actually. I can log in with full access and everything through the bastion host. As can ansible.
Most of the rest of the script works. Openshift Origin does get installed, just that one specific step fails. I don't know if that is preventing it from continuing the install for the rest of the components like the router/registry.

/close


Failing CLI RPC call wallet-status

Calling wallet-status on my no9de with a balance of 95500 (version-4 alphanet) tokens results in this error:
$neptune-cli wallet-status
Error: an error occurred while waiting for the server response

Caused by:
    frame size too big

I think the issue is a hard-coded limit to the size of RPC payloads. That limit should either be increased for the RPC, or the wallet-status should return other data than what it currently does. Currently the MsMembershipProofs are being returned for synced, unspent UTXOs. Maybe removing those MsMembershipProofs from this data would fix the issue? It's also possible we need to remove the Utxo data from this struct.
struct WalletStatus {
    pub synced_unspent_amount: Amount,
    pub synced_unspent: Vec<(WalletStatusElement, MsMembershipProof<Hash>)>,
    pub unsynced_unspent_amount: Amount,
    pub unsynced_unspent: Vec<WalletStatusElement>,
    pub synced_spent_amount: Amount,
    pub synced_spent: Vec<WalletStatusElement>,
    pub unsynced_spent_amount: Amount,
    pub unsynced_spent: Vec<WalletStatusElement>,
}

struct WalletStatusElement(pub u64, pub Utxo);

struct Utxo {
    pub lock_script_hash: Digest,
    pub coins: Vec<Coin>,
}

struct Coin {
    pub type_script_hash: Digest,
    pub state: Vec<BFieldElement>,
}

Seems related to https://github.com/google/tarpc/issues/306.    Although apparently a fix for that was made in tarpc 0.22 and we are presently using 0.33.0.
Also though, given #62 I wonder if this is worth investigating/fixing, as it seems specific to tarpc.  If we move to json-rpc or some other language-agnostic rpc layer, then it likely won't be generating an error.
That said, it's generally best not to return/transmit unnecessary data, so my question would be:  is there a reason that a client would need the MsMembershipProof and/or Utxo data when calling wallet-status?    It could also be that we make this information optional, via parameter flag(s) or even by creating a 2nd RPC call such as wallet_status_details.

I think your suggestion of reducing the data returned (not returning the membership proofs) is the way to go. If we need them later, we'll add a new endpoint, like you suggest.

This endpoint seems to work now.


Join ruyaml?

Hi, thanks for this module!
I came from your great answer on Stack Overflow.
I recently learned about ruyaml project that has a goal of forking ruamel.yaml and provide a better environment for cooperation on fixing its issues.
I am not sure if that project is alive an well though, but it definitely will help if there will be more people that want to help. :)
Please check out https://github.com/pycontribs/ruyaml/issues/27. Perhaps your library could be merged with ruyaml to fix this?

Hey @gdubicki
Thanks for reaching out! Sure although I don't have much spare time, I'd be happy to join development.  I love YAML, and I think there's still a lot of work to be done with it.
Thank for letting me know


⚠ Bofrost.fr has degraded performance

In ab01f32, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1331 ms

Resolved: Bofrost.fr performance has improved in a4f5192 after 10 minutes.


MAC Big Sur logic pro X compatibility

Hello,
Thanks a lot for your work.
Could you please tell me if this plugin works on MAC Big Sur Logic pro X 10.6.1.
I download your mac zip file (spleeter-dj.vst3) and put it in  dans Library/Audio/Plug-Ins/VST3
And I don't see it in Logic pro X...
Do you have an idea ?
Thank you
Have a nice day
Noliverte

Same issue on Catalina.

Maybe try https://github.com/diracdeltas/vstSpleeter/issues/4#issuecomment-634195448 ?

Logic Pro doesn't support VST plugins. You might be able to get it working using an AU wrapper.


Check that we don't read past the end of a ROM table

Also added a few comments and removed a commented out debug print to
ROMTable.handle_table_entry().
Added logging of the ROM table's CIDR and PIDR that uniquely identify
the SoC or platform.

@mbed-bot: TEST

@mbed-bot: TEST

Merged in #256


Expose additional variables to the surrogate model

In experimental design, we often want to control for a confounding variable (an outside influence that changes the effect of the dependent and independent variable). However, the documentation indicates no way to specify information that is outside of experimental control. For example, in ask(), one might wish to specify a rain probability forecast so that the surrogate model can account for rain conditions, which of course are outside of the user's control.
Is this somehow possible, or would it justify an enhancement, or be out of scope?

I think my use case is very similar to: https://github.com/scikit-optimize/scikit-optimize/issues/730
And I think it's an example of: Contextual Gaussian Process Bandit Optimization


Deep sleep wake up only over Connect USB

Hi,
i have the Problem that my TTGO T-Display Board does not wake up when iam powering that only with the Battery. When i connect the USB cable to the Board, the wakeup over ext0, ext1 or externel Timer works without Problems. For the wakeup i use the Button that Connected to GPIO0. On The other Button (GPIO35) Same Issue. Powering over Battery i only can use Reset Button to bring the Board awake.
Have someone the same issue or an idea what iam doing wrong ?

Same with me. The board only wake up by ext0 or ext1 on USB power. When on battery, only reseting. Any sugestions?

I solve the problem myself. Because it was long ago I don't know exactly what Iam done.
I figured out that the issue was in the example program. I excluded everything piece by piece until I found the failure code. It may be that the problem was in the analog Measurement of the battery voltage. Write if it helps.

Leaving this lines, it is possible to wake up with io34 , battery supply and usb disconnected.
rtc_gpio_init(GPIO_NUM_14);
rtc_gpio_set_direction(GPIO_NUM_14, RTC_GPIO_MODE_OUTPUT_ONLY);
rtc_gpio_set_level(GPIO_NUM_14, 1);
delay(500);

Hi,
I've got a TTGO T-Camera (the white version, with a PIR) which won't wake from deep sleep
when powered via a 3.7V LiPo battery attached to the on-board battery connector.
I have written a sketch where the Camera goes to Sleep and then Wakes Up, either when PIR is triggered or after a wait period.
Sleep/Wake behaves completely normally when powered via USB.
But with the battery attached and not powered via USB:
If I let it sleep, then trigger a wake within a few seconds, it works.
If I let it sleep, leave it for ~10 seconds or so, it will not Wake up.
How do I configure this to Wake Up on Battery Power?
Any advice greatly appreciated!


CI/CD

static analysis
code style checks
generate KDoc
unit tests
tests on AVD
deploy developers version from master to google play

Getting error
/usr/bin/env: ‘sh\r’: No such file or directory

my guess is that there is an inconsistency in line endings in some script. Maybe in gradlew?

Yeah 😎

Strange thing


⚠ SceneTime has degraded performance

In 6f6aa08, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1858 ms

Resolved: SceneTime performance has improved in 148b33b after 6 minutes.


listener receive callback ArgumentOutOfRangeException

Unhandled exception. System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'length')
at System.Runtime.CompilerServices.RuntimeHelpers.GetSubArray[T](T[] array, Range range)
at GuacamoleSharp.Server.WebSocketHelpers.ReadFromFrames(Byte[] payload, Int32 receivedLength) in /src/GuacamoleSharp.Server/WebSocketHelpers.cs:line 70
at GuacamoleSharp.Server.GSListener.ReceiveCallback(IAsyncResult ar) in /src/GuacamoleSharp.Server/GSListener.cs:line 261
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location ---
at System.Threading.Tasks.AwaitTaskContinuation.RunCallback(ContextCallback callback, Object state, Task& currentTask)
--- End of stack trace from previous location ---
at System.Threading.Tasks.Task.<>c.b__128_1(Object state)
at System.Threading.QueueUserWorkItemCallbackDefaultContext.Execute()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart()
at System.Threading.Thread.StartCallback()

Error while parsing broken websocket frame length?

Exception did not pop up for a while now. Might have unintentionally fixed it during refactoring...

Might be mouse cursor position desync


[Feature]: Add support for showing what window manager you are using in fetch

Is your feature request related to a problem? Please describe:
I run i3. Presently, my fetch using catnip just shows "unknown" under the desktop manager field. This doesn't look very pretty.
Picture of what I am talking about:

Describe the solution you'd like:
I think one of two solutions could work.

Add support for window manager detection to the desktop field and just have it that way.
Add a dedicated window manager section to the desktop field.

Additional context:
First time opening a feature request issue so apologies if it isn't the correct format. Love the tool.

Hey, the Desktop stat should also show If you have a Windowmanager. I will Look into it.

Hey, the Desktop stat should also show If you have a Windowmanager. I will Look into it.

Ah alr. If you need any info from me lmk.

My guess is that this is not a problem with catnip but with you XDG env vars. Could you check if XDG_CURRENT_DESKTOP is set?

My guess is that this is not a problem with catnip but with your XDG env vars. Could you check if XDG_CURRENT_DESKTOP is set?

Apparently it is a problem with i3 debug logs not setting XDG stuff correctly. i3 debug logs only sets $DESKTOP_SESSION. I'll prob patch up catnip to work with $DESKTOP_SESSION as a fallback of a fallback later today.

Okay, sounds good!


Cannot import Bundle files from unpkg.com

`

`
None of the files can be imported

Hey @nativeanish :) I just updated the docs with the correct bunfle file https://github.com/warp-contracts/warp#using-web-bundles


Error: input UTxOs cannot cover the transaction outputs and tx fee

First of all, thank you for this awesome library! You guys rock!
I am trying to mint some NFT and the example is failing for me. I have to believe its a bug and not a user error since I haven't altered any of the code.
Describe the bug
The example for native token minting is failing with an error due to mismatching ADA amounts in the change output and the fee.
Input: 1000 ADA
Change: 998.355763 ADA
Fee: 2.520477 ADA
Fee + Change = 1000.87624 ADA
To Reproduce
Run the original example script, top up the generated payment address using the faucet and run again
https://github.com/cffls/pycardano/blob/main/examples/native_token.py
Logs
Traceback (most recent call last):
  File "/Users/robin/projects/../mint_example.py", line 162, in <module>
    signed_tx = builder.build_and_sign([payment_skey, policy_skey], change_address=address)
  File "/usr/local/lib/python3.9/site-packages/pycardano/txbuilder.py", line 691, in build_and_sign
    tx_body = self.build(change_address=change_address)
  File "/usr/local/lib/python3.9/site-packages/pycardano/txbuilder.py", line 667, in build
    self._add_change_and_fee(change_address)
  File "/usr/local/lib/python3.9/site-packages/pycardano/txbuilder.py", line 351, in _add_change_and_fee
    changes = self._calc_change(
  File "/usr/local/lib/python3.9/site-packages/pycardano/txbuilder.py", line 286, in _calc_change
    raise InvalidTransactionException(
pycardano.exception.InvalidTransactionException: The input UTxOs cannot cover the transaction outputs and tx fee.
Inputs: [{'input': {'index': 0,
 'transaction_id': TransactionId(hex='009c527e...9b2e1')},
 'output': {'address': addr_test1vz...,
 'amount':<PHONE_NUMBER>,
 'datum_hash': None}}]
Outputs: [{'address': addr_test1vz...,
 'amount': {'coin': 1448244,
 'multi_asset': {ScriptHash(hex='90ddf27...981c8'): {AssetName(b'MY_NFT_1'): 1, AssetName(b'MY_NFT_2'): 1}}},
 'datum_hash': None}, {'address': addr_test1vz...,
 'amount': 998355763,
 'datum_hash': None}]
fee: 2520477

Expected behavior
The Change/Fee calculation should match the Input and the Tx should be valid
Environment and software version (please complete the following information):

OS: Mac OS 10.15
PyCardano Version 0.3.1

Thanks!

Hi Robin,
Thank you for reporting this issue. It is indeed a bug from the example. After some testing, I found that the example built the transaction twice (a mistake from a previous refactoring 😅 ) . I removed this unnecessary line from the example. It should work again now. Sorry about the confusion and thanks again for reporting this.
Jerry

Thank you for the ultra fast response and fix! Looks like its working now! 🚀

Great, thanks for confirming! I will close this issue now.


Support version compatibility for TensorRT models

Adds boolean backend parameter "version-compatible" to allow users to specify whether version-compatible TensorRT models will be supported by Triton.
This pull request had local testing, but I am not adding formalized testing. This is because using version-compatible models in this way is memory-inefficient. Users will likely want to be able to manually load runtimes to avoid needing to duplicate the lean runtime included in version-compatible models. In the meantime, this is still valuable for users who want to use a small number of version-compatible TensorRT models with Triton.
I am going to work on the runtime reuse design and do the work as a separate ticket, since it modifies the way this backend tracks/uses runtimes. After completing that work, it'll be clearer what testing should look like. Originally, it seemed convenient for CI/CD purposes to have this integrated for generating and loading models used in functional testing. However, given the runtime duplication issue, I won't be able to know whether that approach or adding new models/tests specific to this feature makes more sense until I design the feature to reuse runtimes.
Testing (by adding config.set_flag(trt.BuilderFlag.VERSION_COMPATIBLE) to the model generation, then loading a model and running inference).
Current main branch:

After changes:

Can you elaborate on this duplication issue?

By runtime duplication issue above, I mean that if I enabled version compatibility for our QA models, each model would have its own runtime and would thereby bloat the test size. After runtime reusability is added, it seems like more trouble than its worth to generate/save a runtime and adds its path to each of the non-performance test models' configurations. The benefit is that we could not worry about compatibility during the short period between releases when testing. I think it'd make more sense to generate new models and test version compatibility as a unit test. But perhaps I'm missing something that will change that tradeoff. In either case, I want to work on that feature next, so we should have an answer soon.

Is there a problem with manually loading runtimes for each model? Shouldn't just making a loadRuntime(<models_runtime_path>) call allow it?

Thanks for this question. I'm outlining the approach that I'd put in a design below. I would get feedback on that design separately, as I need to think through some things as outlined in this other PR comment.
We'd need to track the runtimes in a data structure. It's reasonably straightforward in my mind. We would add that data structure. Then, when a model config has a runtime path field, use it to get the runtime path. If that runtime is not already loaded, store it. Then, use that runtime for deserializing any models pointing to the same path. I wanted to make it a separate PR because it is discrete from what this one does, plus it modifies a bit of the managing of runtimes (going from one runtime to multiple).

I think it'd make more sense to generate new models and test version compatibility as a unit test. But perhaps I'm missing something that will change that tradeoff. In either case, I want to work on that feature next, so we should have an answer soon.

I think we should atleast have new models with/without runtime to cover these test cases in CI... We can think about moving all our CI tests to TensorRT version compatibility later.

I think it'd make more sense to generate new models and test version compatibility as a unit test. But perhaps I'm missing something that will change that tradeoff. In either case, I want to work on that feature next, so we should have an answer soon.

I think we should atleast have new models with/without runtime to cover these test cases in CI... We can think about moving all our CI tests to TensorRT version compatibility later.

Good point, Tanmay. Testing added here: https://github.com/triton-inference-server/server/pull/6255


BUG: DCA But Submit button does not work

The DCA Bot button does not function. See the Loom: https://www.loom.com/share/f9867f994ea34718a0b356b70baec2e9?sid=53360a33-1c85-4d15-b458-92e24b44d315

I disabled Start DCA bot button because start DCA bot is working now but can't get the DCA bot from robots BE api.
And after I get the DCA bot, I need to fix the my bots page with api returns result.
value key matching between FE and BE


Update the GraphicsTool packages to be compatible with Unity's UPM Asset Store.

Overview
Updating the GraphicsTool packages to be compatible with Unity's UPM Asset Store.
‼ Note, the min Unity version supporting UPM Asset Store packages is 2021.3.26f1.  That's why you see "unityRelease"="26f1".  This change won't prohibit people from obtaining the Graphics packages via the MR Feature Tool or GitHub on older versions of the Unity.

Added UPM package validator to test project
Had to remove assembly definitions for sample directories
Had to remove the "Experimental" sample directory, and move its child directories to the root Samples~ directory
Had to move pipeline assets to the runtime directory
Had to specify unity patch release. The minimum supported version for the UPM Asset Store is 2021.3.26f1, hence this patch number
Had to specify a documentation URL

Changes

Fixes: https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity/issues/518

All of this looks great to me, but one issue is this: "Had to remove assembly definitions for sample directories"
When importing  the samples this is totally fine. But if a developer needs to update  the samples via the Window > Graphics Tools > Show Samples menu item you get this error:

Script 'Packages/com.microsoft.mrtk.graphicstools.unity/Samples/MeshInstancing/Scripts/InstancingContainment.cs' will not be compiled because it exists outside the Assets folder and does not to belong to any assembly definition file.

Is there any way we can get sample assembly definitions and the validator to work in harmony?


Modify UI allowing user to add lesson tags

Links to #62
As part of the lesson tag filter feature, a user should be able to add tags to a lesson. The markup for this will need to be added to the create/new lesson form.
Some thoughts:

This could be achieved by adding a drop-down list with a predefined list of options
Should the user be able to define their own custom lesson tags?

As always this is open for discussion 😄

@iyerm2000 and I are interested in working on this issue as well. Right now I see the colors as tags, but do you have a predefined list you would like to see instead? To answer your thoughts above, I think it would be worthwhile to allow the user to define their own custom tags.

I think we can definitely improve the UI for the tags. Ultimately, I'm thinking that the user will be able to add multiple tags from a predefined list as well as create their own – something like this https://jeesite.gitee.io/front/jquery-select2/4.0/index.htm#multiple
If that feels a little complex, this ticket could just handle adding the correct tags to the lesson cards. Currently, if you select a tag & submit a lesson the tag is added to user data in local storage but we're not doing anything with that data. It would be nice to display the selected tag(s) within lesson cards.
Let me know what you think!

Hi! I was wondering whether it would be possible to get a little more insight on how to save the lesson tags. Currently I don't see a defined backend in the codebase. Any advice would be great!

Hi! I was wondering whether it would be possible to get a little more insight on how to save the lesson tags. Currently I don't see a defined backend in the codebase. Any advice would be great!

There is no backend atm. All lesson data is persisted in browser storage. The idea going forward is that we'll allow the user to download their lesson data in (.md or .txt) if they wish to save/persist elsewhere.
The lesson tags are already being saved. If you open up the developer tools and add a lesson, if you run localStorage.getItem('user') you'll see lesson data & associated tag data – like this:

If you've never worked with the Storage API before I'd recommend giving this a read.
This file contains the localStorage logic for setting and getting user data (including tags).
Hope that helps 😄
Let me know if you need some further explanation.


Update oracle-database-regions.md

@jjaygbay1
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Corrected documentation of memory buffer

Description of Changes
Updated memory buffer docs to indicate it no longer writes to disk.
Please check that the PR fulfills these requirements

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
- [ ] Add a changelog entry (for non-trivial bug fixes / features) (part of larger v2 changelog)
[ ] CI passes

Log Files
Logs / Second
CPU Avg (%)
CPU Avg Δ (%)
Memory Avg (MB)
Memory Avg Δ (MB)

1
1000
1.4827818
-0.086197376
49.489628
-79.06412

1
5000
6.086285
+0.8966551
57.01293
-80.44262

1
10000
11.948431
+0.9138298
62.60129
-83.52681

1
50000
51.53437
-1.7762489
88.842804
-96.778824

1
100000
93.31236
-8.415436
128.1712
-110.33

10
100
2.4138079
+0.5172442
51.854122
-80.89978

10
500
6.948409
+1.120791
60.558594
-82.965515

10
1000
13.569221
+0.60330486
66.68723
-81.248924

10
5000
60.57016
+3.5007591
96.48532
-84.11247

10
10000
122.016205
+10.97805
160.62486
-77.83446

Log Files
Logs / Second
CPU Avg (%)
CPU Avg Δ (%)
Memory Avg (MB)
Memory Avg Δ (MB)

1
1000
1.4655377
-0.10344148
50.174435
-78.3793

1
5000
5.793175
+0.6035452
58.643723
-78.81183

1
10000
11.362274
+0.32767296
63.60062
-82.52748

1
50000
53.6395
+0.3288803
90.2364
-95.38523

1
100000
101.621475
-0.10632324
127.90046
-110.600746

10
100
2.5344832
+0.63791955
57.39871
-75.355194

10
500
7.3966827
+1.5690646
59.78462
-83.73949

10
1000
13.534644
+0.56872845
65.029366
-82.90679

10
5000
61.949196
+4.879795
99.57207
-81.02573

10
10000
116.721085
+5.68293
156.26212
-82.197205


Error with "$refs" inside child component

Version
1.0.0-beta.29
Reproduction link
https://github.com/ndabAP/vue-command/blob/test/unit-tests/tests/unit/vue-command.spec.js#L21
Steps to reproduce

Clone the repository
Switch to branch "test/unit-tests"
Run yarn
Execute yarn test

What is expected?
this.$refs.input.scrollIntoView behaves like normal Vue.js usage.
What is actually happening?
Error:

Error in mounted hook: "TypeError: this.$refs.input.scrollIntoView is not a function"

I tried to mock $refs but it didn't work.

Thank you for the bug report, but that reproduction is too large. Are you able to provide a minimal reproduction?

Hey @eddyerburgh,
thanks for your answer. I just have been told at Reddit that this is a issue at JSDom. That would mean that every project that uses scrollIntoView would fail.
I can create a repository where this function is used. Can you confirm that this is possible at all?

Ah yes, you'll need to implement your own scrollIntoView mock function because JSDOM doesn't currently support it.
You can mock it with:
Element.prototype.scrollIntoView = () => {}

Thanks!


Add ability to customize highlight color of link text

Changes look fine, but what is the reason for this change? Wouldn't it be pretty odd to have the highlight colors different from the normal colors?
At first, I saw the pull request and thought, "oh this could give better control over the alpha layer of the highlights", but then I realized that I already allow the developer to set the alpha layer

@klinker41 A design requirement of ours is that the link simply highlight to a different color and that the background does not change which is what it appears setting the alpha does. This allows others a bit more flexibility in that the links can have a different highlight color that isn't an alpha value of the original color or changes the background color.

I have made just a few small comments on things I would like to see changed. I just want your verbiage to better express what you are doing with this feature. I think being very clear with this is important, since the feature is a bit odd, in general.
If you could also add on to the readme (specifically the xml example for the default and maybe a java one), that would be great.
Change those few things and I will go ahead and merge this one and bump the version

@klinker24 Changes made with commits squashed.


Use properly computed Ip_non_inductive in ActorQED

@bclyons12 see
https://github.com/ProjectTorreyPines/FUSE.jl/pull/721
https://github.com/ProjectTorreyPines/IMAS.jl/pull/203


React router website, quick start page can't scroll

React router website, quick start page can't scroll
https://react-router-website-xvufzcovng.now.sh/quick-start

Confirmed here (Chrome v53 on MacOS).
In Inspector, removing height: 100%; from <div id="app"> solved the problem...
Tested on Firefox and Safari, and both are working...

Looks like none of the pages scroll if you're using Chrome or Firefox. It's fine on Safari. I opened up the browser console and unticked the body height property which is set to 100%. Brought back the scroll bar.

Dupe of #3859. Fixed in e12f607.


[REST source] test case for dependent resource

Tell us what you do here

[x] improving, documenting, or customizing an existing source (please link an issue or describe below)

Relevant issue
issue #313
More PR info
Currently, failing test case

Thank you, @willi-mueller


batch process tasks, maybe tests and custom values

A portion of our builds contain thousands of tasks, and inserting them one by one is going to take too long.
By eyeballing, the insertion rate is around 50 entries/sec on a localhost db. In the past two weeks, we have collected >5000 builds.
Average builds has 2000 tasks, 5000 * 2000 / 50 entries/sec / 3600 sec/hour = 55 hours.
Therefore, instead of inserting them one by one, we should batch task insertion into one/few chunks of sql per build.
select count(*), build_id from tasks GROUP BY build_id
1	ergr4nbk5kosg
1	ug4pzw6nnmzrg
1	3toy7kah4nxyi
3772	xdmq4ogb2mbse
9	hq6v5war26uk6
1	xwl2azyp45l7w
94	oexbleqxxejp4
1	qizgynng36tga
3890	serztqtpey5p4
1	7qq2wu5g574mw
1	7dywksrkva3la
1	jq7bt4bq5ypou
1	tabv2hvssopka
1	jz3rezuqhfsje
1	lktgz7kmxzxt6
1	7izkmgtswl6c4
1	pk7iqpwi5ehwe
3825	5j6f3zhzvv7ri
10	t6n2qtkv53lc2
10	rvvvinsagntsi
1	6ltqlmgylumao
98	g4nw2fxqsogs4
9	dnkqdnhhihk5e
3864	qxdfx3rzfpbbg
3810	2qgpai4f4woqq
1	mhlgjv2dlw2ry
3631	4c32yszglioy2
3825	e5qov44yzbm26
3823	43xak2ezzbvka
93	xvw7vauffnrvw
98	2m5t7kcorgxls
9	nhqorurbh6oaq
1	ajoq3jfhqyzy4
1	s6nwmx4vllgli
3810	32gbsvxtlbkrs
93	h6j26fnygpntw
2240	fngjwim6osiom
4158	caivn3t75d7ok
4158	hixunxdw5xb54
3823	hy6idia2onavm

closed due to no longer needed


"Module file was created by an older version of the compiler..."

Module file was created by an older version of the compiler; rebuild 'Kingfisher and try again:"
I'm getting this message after I installed the using Cocoapods. I put this in my pod file:
pod 'Kingfisher', '~> 3.0'
Any ideas why this is happening / how to fix it? i've tried reinstalling, i've tried cleaning and building. But nothing is working!

Sometimes you need to restart your Xcode to make the error gone. :(
And you might also need the newest CocoaPods (1.1.0 or its RC versions) for Swift 3 support.


Logging

Adds logging support to the rover software. Instead of printing you call:
self.log("Message", "DEBUG")
where "DEBUG" can be replaced with any level defined in the python logging module (INFO is the default).
List of changes:

RoverProcess gets a self.log(message, level) method
Most print statements are updated to use self.log instead
Log messages are printed to the console and written to a file. (This could lead to bad i/o performance if too many things are writing to the log file too quickly)

Closes issue #49 .

Love it!


history.push withRouter doesn't render page when using switch component

Version
Please replace this sentence with the React Router version that you are using.
Test Case
https://codesandbox.io/s/react-router-gh6n7
Steps to reproduce
when using withRouter
Works:
<Provider store={configuredStore()}>
      <Router history={history}>
        <HeaderContainer />

        <Route exact path="/" component={Landing} />
        <Route path="/dashboard" component={Dashboard} />
        <Route path="/create-organization" component={CreateOrganization} />
      </Router>
    </Provider>

Doesn't Work:
<Provider store={configuredStore()}>
      <Router history={history}>
        <HeaderContainer />
        <Switch>
          <Route path="/" component={Landing} />
          <Route path="/dashboard" component={Dashboard} />
          <Route path="/create-organization" component={CreateOrganization} />
        </Switch>
      </Router>
    </Provider>

Expected Behavior
When using withRouter I would expect to be able to use history.push to programatically change pages when using the Switch component.
Actual Behavior
When using the Switch component it only changes the URL and does not re-render the page. Removing the switch components and setting the root as exact path resolved the issue.

You don't have an exact on your first Route, so it's matching everything. You can never reach your other routes that way.

You don't have an exact on your first Route, so it's matching everything. You can never reach your other routes that way.

doh, nice catch <3 thanks for taking the time to respond.


Remove version: Jackett.Jackett version 0.21.128

404 - release deleted
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/Jackett/Jackett/releases/download/v0.21.128/Jackett.Installer.Windows.exe
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 918)


Was working this morning

Is anyone else having an issue with their updated chrome extension? Mine was working this morning, now it does not work. Here is my code that was working this morning. Can anyone confirm/verify please?

Right clicked on the background of the site and clicked inspect. Maybe this will help someone?

So I'm the only one having a problem?

RIP

Pretty please someone fix

Thank you for replying Feek. Were you able to verify yours was working?

I have tried following the instructions on the read me. Would you be able to spend a few minutes with me screen sharing and waking me through? I have sent you some money on beer pay already :) and I am happy to compensate you again.

OMG i got it to work :) much love

@CMaximus glad to hear it!


Basic authentication information is not passed through

What do I expect?
If the TARGET_HOST_DSN contains basic authentication information (e.g<EMAIL_ADDRESS>I expect them to be used for each middled request.
What happens?
Each request fails with an error code of 401.

Fixed in https://github.com/jensschulze/restinthemiddle/commit/904162da1a7217031f3a8072239ed8cd0dd71851


Fix doppler effect and built-in speed parameters without rigidbody.

It calculates the velocity by saving the position from last frame.

I am hearing some pitch fluttering when moving too quickly. I have found however that clamping the velocity vector's magnitude fixes this:
velocity = Vector3.ClampMagnitude(velocity, 1.0f);
I have passed this onto the Dev team for further consideration.
Thank you for the suggestion, and apologies for the delayed review.


Info message to install Ansible is confusing and not accurate when is required a updated

Description
WHAT: Message "Ansible version is < 2.6. Install ansible>=2.6 using pip install ansible>=2.6" is shown
WHERE: iOS
WHEN: run the install command ./installer/install.sh
IMPACT:

Not clear what command need to be executed. Is it  pip install ansible>=2.6 or pip install ansible?
The command pip install ansible will NOT update the current installation

What is expected?

A clear message with the command that should be executed. ( It can be solved by improving the text as for example: Ansible installed version is < 2.6. To fix it install an ansible version >=2.6 by "$<command>"
Inform the correct command to update the current installation when it already exists. pip install ansible will NOT update the current installation and it should appears when the ansible is not installed in the env ONLY. If the problem is version > of min requirements then it should shows the command to updated the current version to the min required version.
The command to update the current version to the latest pusblish is pip install ansible --upgrade --user

Environment
Operating system: iOS
OpenShift versions:
Steps to reproduce
Follow up the steps to install in the doc

Thanks for the issue @camilamacedo86  did running pip install --upgrade ansible solve the issue for you? If so a PR to change the message would be welcome

Hi @maleck13,
The correct command was added in the issue description as the expected behaviour and it worked for me.
"The command to update the current version to the latest publish is pip install ansible --upgrade --user"
PS.: --user option is important to don't face the pip permission error. See here

PR made https://github.com/aerogear/mobile-core/pull/175

Solve in the PR/merged


I get this popup on startup after uninstalling TaskbarX

Describe the bug
After installing the dev build of Windows 11 I have no use for TaskbarX anymore so I uninstalled it. Before uninstalling I made sure to stop the service and remove the task scheduler from the TaskbarX configurator. Even though I removed every trace of TaskbarX and the task scheduler windows still tries to start it on startup and I get this popup. I got TaskbarX from the Microsoft Store but I made sure to check the Task Scheduler app and TaskbarX wasn't in the Task Scheduler Library.
To Reproduce
Steps to reproduce the behavior:
Install TaskbarX Microsoft Store version.
Create Task Scheduler with the TaskbarX configurator.
Uninstall TaskbarX.
Restart PC.
Expected behavior
You get a popup asking what app to use to open TaskbarX link.
Screenshots

Desktop (please complete the following information):

OS: [Windows 11 Pro]
Version [22000.65]

Additional context
Add any other context about the problem here.

Let me second this on Windows 11 Home too.

I ran into this as well on Windows 10 Pro. The problem is that if you uninstall it by right-clicking the icon and choosing Uninstall, the scheduled task that refreshes it periodically gets left behind. If you go into Task Scheduler you should see the scheduled task for TaskbarX. Delete it and this message will go away.
There is an uninstall option in the TaskbarX Configurator that uninstalls the app correctly.

I ran into this as well on Windows 10 Pro. The problem is that if you uninstall it by right-clicking the icon and choosing Uninstall, the scheduled task that refreshes it periodically gets left behind. If you go into Task Scheduler you should see the scheduled task for TaskbarX. Delete it and this message will go away.
There is an uninstall option in the TaskbarX Configurator that uninstalls the app correctly.
I didn't know about the uninstall. Thanks for the help.

 It's really not obvious at all that you're supposed to use the configurator to do the uninstall.

I ran into this as well on Windows 10 Pro. The problem is that if you uninstall it by right-clicking the icon and choosing Uninstall, the scheduled task that refreshes it periodically gets left behind. If you go into Task Scheduler you should see the scheduled task for TaskbarX. Delete it and this message will go away.
There is an uninstall option in the TaskbarX Configurator that uninstalls the app correctly.

do you (or @ChrisAnd1998) happen to know what this service is called? I don't see anything obviously TaskbarX related in my list of services.
Super annoying to have this popup on restarts.

It's not a service, it's in the Windows Task Scheduler. I don't remember the name of it and unfortunately don't use TaskbarX anymore so can't check, but it wasn't hard to locate once you're in Task Scheduler. IIRC it was at the root Task Scheduler Library level. Just look for the task that has an Action set to run TaskbarX.

It's not a service, it's in the Windows Task Scheduler. I don't remember the name of it and unfortunately don't use TaskbarX anymore so can't check, but it wasn't hard to locate once you're in Task Scheduler. IIRC it was at the root Task Scheduler Library level. Just look for the task that has an Action set to run TaskbarX.

Found it, thank you!
It is literally just Taskbar X on COMPUTER\name.

To be able to focus on major/current bugs I had to close all issues. The issues section has gotten very messy to a point that I couldn't follow it anymore. Most issues are duplicates, very old or are already fixed/solved. Feel free to reopen this issue if you still have this issue on the latest version of TaskbarX to get my attention. All feature requests have been put in a list here: 💡| Feature requests #870
I hope you understand ❤


Sri Dasam Granth - Mehron Corrections for Issues 1394 to 1479

Aside from partial completion of issue #1450, everything should be done corrections wise for issues 1394 to 1479.
I have not gone through and matched page numbers for lines. Let me know if I should do that, it's in issue #1575 for tracking.
Build breaks because of gurmukhi-utils translit issue

Also merge will be blocked as Open Yaiyha ASCII chars are going to change https://github.com/GurbaniNow/gurmukhi-fonts/issues/11

We can merge now. And when https://github.com/GurbaniNow/gurmukhi-fonts/issues/11 is completed we'll just do a new merge in addition to using new fonts in desktop.


Continue with form -  create "AgeGroup" (Checkboxes)

Hey 👋
this looks good to me!
Maybe there is one little thing that will be helpful to the user: an information about the range of the "Agegroups". This makes it easier for every user to assign the category.


Docker: Add GPU Version of Docker Image

Problem
Currently the Docker development environment (i.e. the ghcr.io/diogenesanalytics/autoencoder:master Docker image) does not have any GPU drivers for GPU accelerated applications (i.e. training neural networks with keras).
Solution
Can create multi-stage Docker image build to create a GPU version:
# jupyter base image
FROM jupyter/scipy-notebook:lab-4.0.0 as cpu-only

# first turn off git safe.directory
RUN git config --global safe.directory '*'

# turn off poetry venv
ENV POETRY_VIRTUALENVS_CREATE=false

# set src target dir
WORKDIR /usr/local/src/autoencoder

# get src
COPY . .

# get poetry in order to install development dependencies
RUN pip install poetry

# config max workers
RUN poetry config installer.max-workers 10

# now install development dependencies
RUN poetry install --with dev -C .

# additional GPU-enabled steps
FROM cpu-only as gpu-enabled

# install CUDA tools
RUN mamba install -c conda-forge cudatoolkit=11.8.0 && \
    mamba clean --all -f -y && \
    fix-permissions "${CONDA_DIR}" && \
    fix-permissions "/home/${NB_USER}"

# install separate pip libraries
RUN pip install nvidia-cudnn-cu11==<IP_ADDRESS>

# setting up CUDA library link
RUN export CUDNN_PATH=$(dirname \
    $(python -c "import nvidia.cudnn;print(nvidia.cudnn.__file__)")) && \
    ln -s ${CUDNN_PATH} ${CONDA_DIR}/lib/cudnn.ln

# setting dynamic link lib paths
ENV LD_LIBRARY_PATH=${CONDA_DIR}/lib/:${CONDA_DIR}/lib/cudnn.ln/lib

# host NVIDIA driver minimum version metadata
LABEL nvidia.driver.minimum_version="450.80.02"

Implemented with: ca2c35b185c0c106b282d6bea6077aa7ba04c3cf


Improve evohome exception handling and fix bugs

Breaking Change:
No breaking changes I am aware of.
Description:

Upgrade to the latest client library (improved exception handling, support for reusing sessions/tokens) - this needed a minor update to climate\honeywell.py.

Improve exception handling: widen number of exceptions caught, improve log messages.

BUGFIX: Fix issue #22097: Failed to call service climate/turn_on...

BUGFIX: handle case where a Zone doesn't have a temperature

BUGFIX: missing exception handler, and removed inappropriate delint hints

Use less aggressive throttling when the API rate limit has been exceeded

Related issue (if applicable): fixes #22097
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):
Not applicable
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed: Not applicable
If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices: Not applicable

Here is an example of improved exception handling with the honeywell component:
2019-03-27 16:15:20 ERROR (SyncWorker_2) [homeassistant.components.honeywell.climate] Connection error logging into the honeywell evohome web service,hint: HTTP Status = 429, Response = [
  {
    "code": "TooManyRequests",
    "message": "Request count limitation exceeded, please try again later."
  }
]

... and an example for the evohome component:
2019-03-27 16:18:22 ERROR (MainThread) [homeassistant.setup] Error during setup of component evohome
Traceback (most recent call last):
  File "/home/dbonnes/home-assistant/venv/lib/python3.6/site-packages/evohomeclient2/__init__.py", line 146, in _obtain_access_token
    response.raise_for_status()
  File "/home/dbonnes/home-assistant/venv/lib/python3.6/site-packages/requests/models.py", line 940, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 429 Client Error: Too Many Requests for url: https://tccna.honeywell.com/Auth/OAuth/Token

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/dbonnes/home-assistant/homeassistant/setup.py", line 154, in _async_setup_component
    component.setup, hass, processed_config)  # type: ignore
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/home/dbonnes/home-assistant/homeassistant/components/evohome/__init__.py", line 78, in setup
    debug=False
  File "/home/dbonnes/home-assistant/venv/lib/python3.6/site-packages/evohomeclient2/__init__.py", line 78, in __init__
    self._login()
  File "/home/dbonnes/home-assistant/venv/lib/python3.6/site-packages/evohomeclient2/__init__.py", line 81, in _login
    self.user_account()
  File "/home/dbonnes/home-assistant/venv/lib/python3.6/site-packages/evohomeclient2/__init__.py", line 198, in user_account
    response = requests.get(url, headers=self._headers())
  File "/home/dbonnes/home-assistant/venv/lib/python3.6/site-packages/evohomeclient2/__init__.py", line 87, in _headers
    self._basic_login()
  File "/home/dbonnes/home-assistant/venv/lib/python3.6/site-packages/evohomeclient2/__init__.py", line 125, in _basic_login
    self._obtain_access_token(credentials)
  File "/home/dbonnes/home-assistant/venv/lib/python3.6/site-packages/evohomeclient2/__init__.py", line 152, in _obtain_access_token
    raise AuthenticationError(msg)
evohomeclient2.AuthenticationError: Unable to obtain an Access Token, hint: {"error":"attempt_limit_exceeded"}

Sorry @MartinHjelmare, my undoing of your edit was just a cross-post.

@MartinHjelmare Do you have time to look at this please?

Can be merged when build passes.

Can be merged when build passes.

Thanks Martin - I always have a sense of great achievement when I get something past you! 😄

@MartinHjelmare Merge please?


Default blueprint won't actually add/install the Bower dependency

ember g ember-emojione reports a successful installation, but it add the package neither to bower.json nor to bower_components/.

No longer applicable.


[Python] Python C++ libraries no longer in pyarrow/lib directory

Describe the bug, including details regarding any error messages, version, and platform.
Prior to #14925, libraries such as arrow_python.dylib were installed in both python/pyarrow and python/pyarrow/lib. Afterward, they are only present in python/pyarrow, and when I build in place and run import pyarrow I get:
ImportError: dlopen(/Users/willjones/Documents/arrows/arrow/python/pyarrow/lib.cpython-310-darwin.so, 0x0002): Library not loaded: '/Users/willjones/Documents/arrows/arrow/python/pyarrow/lib/libarrow_python.1100.dylib'

It seems my dev environment relied on that lib directory and I suspect I am not alone.
Component(s)
Python

> otool pyarrow/lib.cpython-310-darwin.so -L
pyarrow/lib.cpython-310-darwin.so:
        /Users/willjones/Documents/arrows/arrow/python/pyarrow/lib/libarrow_python.1100.dylib (compatibility version 1100.0.0, current version 1100.0.0)
        /Users/willjones/mambaforge/envs/arrow-dev/lib/libarrow.1100.dylib (compatibility version 1100.0.0, current version 1100.0.0)
        @rpath/libc++.1.dylib (compatibility version 1.0.0, current version 1.0.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)

Workaround for now (on MacOS): after building,
mkdir -p pyarrow/lib && cp pyarrow/*.dylib pyarrow/lib/

Related:

https://github.com/apache/arrow/pull/14925#issuecomment-1367569669
https://github.com/apache/arrow/issues/15122

I think that we should always use @rpath even when Apache Arrow C++ is built with -DARROW_INSTALL_NAME_RPATH=NO.


Roll Flutter Engine from 5ca3b856ee5a to ca79a56a66d7 (1 revision)

https://github.com/flutter/engine/compare/5ca3b856ee5a...ca79a56a66d7
2024-07-07<EMAIL_ADDRESS>Roll Fuchsia Linux SDK from RSMFdOFyLxulsvY4_... to Em1nantnFXXK8xJH9... (flutter/engine#53748)
Also rolling transitive DEPS:
fuchsia/sdk/core/linux-amd64 from RSMFdOFyLxul to Em1nantnFXXK
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC aaclarke@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


[RESOLVED] S100-Santiago has been restarted (uptime < 10m)

Problem started at 13:29:07 on 2023.07.17
Problem name: S100-Santiago has been restarted (uptime < 10m)
Host: S100-Santiago
Severity: Warning
Operational data: 00:00:27
Original problem ID: 32682
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23522&eventid=32682

Problem has been resolved in 9m 55s at 13:39:02 on 2023.07.17
Problem name: S100-Santiago has been restarted (uptime < 10m)
Host: S100-Santiago
Severity: Warning
Original problem ID: 32682


Recommend building project documentation in CumulusCI-Process-for-Customers-and-Partners wiki

Hi CumulusCI Process for Customers and Partners Team! Great job at the Detroit Sprint! :)
I wanted to submit an Issue to encourage you to host your project documentation in the CumulusCI-Process-for-Customers-and-Partners wiki.
To learn more about this process take a look at the About wikis Github article.

I am looking at this now, so when there is a wiki there needs to be a home page right, what should that page be.
I will start working on a google doc to add you to. OH and eventually can we use the sidebar thing I like it.

Yes - you will want a landing page (i.e. Home page) for the wiki. The good news is that when you create the first page in your Wiki (see image below) you will create the Home page. :)

You will want to keep the home page high level (i.e. just describe the content you've created along with links to the corresponding wiki pages that support process and diagrams.) The idea here is to provide high level value around the resources you are making available to the community. Remember - the README is a high level project overview. The wiki is where the people will go to learn more about your project. Think Table of Contents for your wiki home page.
Take a look at this Wiki example from a forked version of Outbound Funds: https://github.com/emilymorse/OutboundFunds/wiki
On that note I'd highly recommend reviewing Github's documentation around wikis: https://help.github.com/en/articles/about-wikis
Here are a few additional resources from Github that should help:
Github Guides https://guides.github.com/
Video Guides https://www.youtube.com/githubguides
Github Help https://help.github.com/en
In the end how you structure the wiki is up to you and I am totally willing to give feedback on your Google doc outline. :)
Also - you need to teach me how to make a Bitmoji. The last one I made didn't look like me at all lol

My little OCD self has just realized when building out the WIKI pages, that they are not in the same order as the list. I have been trying to find a way to make them line up with how the home page is organized (Same Order) and I am not able to. Is there a secret I am not aware of?

@brennanbutlerRAD - Totally hear ya on that! Take a look at this thread: https://stackoverflow.com/questions/39396362/github-wiki-pages-sort-order
Lots of options here.
Let me know which one you decide to go with!

Thanks, Jace, reviewing it now. I am thinking the sidebar will be the simplest way to go.


Update coreos to 1.5.4

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Thank you for the contribution. It was merged directly as cd156ff7c59f339589f1f1434dfe3d72681d7ea1. Your contribution is still credited to you.


Use export trusted + untrusted buckets

Current, there is one single "export" bucket for exporting data, that is used both by the EC2 to push data, and the client to download data. This needs to be split into two separate buckets.

With the 0.5.0 upgrade, this ticket is complete.


Remarks missing entry (not valid in 64-bit MASM)

Directive not valid in 64-bit MASM (ml64.exe).

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

ID: f10077b5-ce76-1ba8-f389-22ef74bb9ca5
Version Independent ID: a69d904f-20b5-5002-7d0b-81281094eaa6
Content: DOSSEG
Content Source: docs/assembler/masm/dosseg.md
Product: visual-cpp
Technology: cpp-masm
GitHub Login: @corob-msft
Microsoft Alias: corob

fix should appear in 1-2 days. Thanks @Player1UK !


compute query parameter names in the client.

I had to fix some tests, so this must have fixed some v1beta3 problems.

In preparation for a fix for #6495.

LGTM


Add missing : in the logs

this PR simply add missing : which are present in the vanilla format to fix the log hosts like https://mclo.gs from not recognizing the log properly

F dumbass me making the pr to myself instead of upstream


Enhance the CSS of the application.

We need to improve the CSS for the chat messages, clearly showing the user which are their messages and which are the messages of the person they are talking to.

Some progress comes in pull request #49


[server] Fix quotes in system comments

Closes #3092

Commenting on an issue using quotes results to the error
"No closing quotation" because of shlex.split.

I verify that this fixes the issue: quotes are possible to be inserted, and the previously impossible-to-view comments, are now viewable. So +1 from me.
On a side discussion however. it might be worth deprecating "status change comments" alltogether. They look ugly (they merge newlines and paragraphs), and when someone writes two-three paragraphs explaining why the issue is a false-positive, it's hard to read.
By disabling the addition of new "status change comments", people will add separate comments after changing the status. They preserve all formatting and are easier to read.

@jimis Could you please give us a screenshot from an ugly comment? How it looks like?

Here is almost the same comment written within the status change, and as a separate comment. You can see that in the first case all whitespace is lost, and the comment comes in small letters.


fix: ensure requestTimeout and maxRetries are integers

This is failing when environment variables are used for configuration. Env vars are strings but are never converted to int before using them in arithmetic operations.
My configuration:
              "OKTA_CLIENT_CONNECTIONTIMEOUT": "30",
               "OKTA_CLIENT_ORGURL": "https://dev-89428916.okta.com",
               "OKTA_CLIENT_AUTHORIZATIONMODE": "PrivateKey",
               "OKTA_CLIENT_CLIENTID": "${env:OKTA_CLIENT_CLIENTID}",
               "OKTA_CLIENT_SCOPES": "okta.users.read,okta.groups.read",
               "OKTA_CLIENT_PRIVATEKEY": "${env:OKTA_CLIENT_PRIVATEKEY}",
               "OKTA_CLIENT_REQUESTTIMEOUT": "0",
               "OKTA_CLIENT_RATELIMIT_MAXRETRIES": "4",
               "OKTA_CLIENT_LOGGING_ENABLED": "true",
               "OKTA_CLIENT_LOGGING_LEVEL": "INFO",

My error:
        # Raise Value Error if numerical inputs are invalid (< 0)
        self._request_timeout = config["client"].get('requestTimeout', 0)
>       if self._request_timeout < 0:
E       TypeError: '<' not supported between instances of 'str' and 'int'

/opt/homebrew/lib/python3.11/site-packages/okta/request_executor.py:35: TypeError

The os.environ dictionary in Python expects its values to be strings.

@tgarciaalv I apologize for the delayed response and thank you for your submission.  To ensure integrity, please provide a unit test that fails prior to your proposed change and passes with your change in place.
We appreciate your engagement and thanks for using Okta!


processes wrong file if autosave is enabled

I have autosave enabled in Atom. This causes Atom to save your file when ever you switch tabs. But, this is causing sass-autocompile to process the wrong file.
Example
If I'm working on a scss file and switch to an html file, Atom saves the scss file. But sass-autocompile attempts to compile the html file instead of the scss file. So I see an error like this:  Error: Invalid CSS after "": expected 1 selector or at-rule, was "<!doctype html>" and the css file is not updated.

Hey! Thanks for you report. I published a fixed version right now.


puppeteer: Fix edit bot form test flake.

This test was verifying if an error was displayed on trying
to rename a bot with an existing name and then close the edit
modal with 'cancel' button.
I think the cause for flake is that the 'cancel' was clicked when
it is disabled while the request was being made. The existing waits
should've also worked for this but I presume there's some race.

Testing plan:
ran the test once. Couldn't run it 100 times to see if the flake persist.
GIFs or screenshots:

Seems like a plausible theory; I expect we'll find out pretty soon if this doesn't fix it.
Thanks so much for working on this!


Fix long statusbar items

This PR fixes #87163
Just a small tweak to don't cover right side status bar items.
Before:

After:

white-space: nowrap is breaking other status bar items. Please check the error/warning icons in your screenshot.

Fixed