Failed to compile in Windows 10?

Hello, this is my first time trying to use your library.
I just copied and pasted your example from the readme:
use softbuffer::GraphicsContext;
use winit::event::{Event, WindowEvent};
use winit::event_loop::{ControlFlow, EventLoop};
use winit::window::WindowBuilder;

fn main() {
    let event_loop = EventLoop::new();
    let window = WindowBuilder::new().build(&event_loop).unwrap();
    let mut graphics_context = unsafe { GraphicsContext::new(window) }.unwrap();

    event_loop.run(move |event, _, control_flow| {
        *control_flow = ControlFlow::Wait;

        match event {
            Event::RedrawRequested(window_id) if window_id == graphics_context.window().id() => {
                let (width, height) = {
                    let size = graphics_context.window().inner_size();
                    (size.width, size.height)
                };
                let buffer = (0..((width * height) as usize))
                    .map(|index| {
                        let y = index / (width as usize);
                        let x = index % (width as usize);
                        let red = x % 255;
                        let green = y % 255;
                        let blue = (x * y) % 255;

                        let color = blue | (green << 8) | (red << 16);

                        color as u32
                    })
                    .collect::<Vec<_>>();

                graphics_context.set_buffer(&buffer, width as u16, height as u16);
            }
            Event::WindowEvent {
                event: WindowEvent::CloseRequested,
                window_id,
            } if window_id == graphics_context.window().id() => {
                *control_flow = ControlFlow::Exit;
            }
            _ => {}
        }
    });
}

Here is my cargo.toml:
[dependencies]
softbuffer = "0.1.1"
winit = "0.27.1"

I get this when trying to build:
error[E0432]: unresolved import `winapi::shared::windef`
 --> C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\softbuffer-0.1.1\src\win32.rs:4:21
  |
4 | use winapi::shared::windef::{HDC, HWND};
  |                     ^^^^^^ could not find `windef` in `shared`

error[E0432]: unresolved import `winapi::um::wingdi`
 --> C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\softbuffer-0.1.1\src\win32.rs:5:17
  |
5 | use winapi::um::wingdi::{StretchDIBits, BITMAPINFOHEADER, BI_BITFIELDS, RGBQUAD};
  |                 ^^^^^^ could not find `wingdi` in `um`

error[E0432]: unresolved import `winapi::um::winuser`
 --> C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\softbuffer-0.1.1\src\win32.rs:6:17
  |
6 | use winapi::um::winuser::{GetDC, ValidateRect};
  |                 ^^^^^^^ could not find `winuser` in `um`

error[E0433]: failed to resolve: could not find `wingdi` in `um`
  --> C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\softbuffer-0.1.1\src\win32.rs:64:25
   |
64 |             winapi::um::wingdi::DIB_RGB_COLORS,
   |                         ^^^^^^ could not find `wingdi` in `um`

error[E0433]: failed to resolve: could not find `wingdi` in `um`
  --> C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\softbuffer-0.1.1\src\win32.rs:65:25
   |
65 |             winapi::um::wingdi::SRCCOPY,
   |                         ^^^^^^ could not find `wingdi` in `um`

Did I do something wrong?
Otherwise, I see a lot of potential in your library, how we use winit instead of trying to reinvent the wheel.
Thank you,
Veniamin

I was able to get around this problem by adding this dependency:
winapi = { version = "*", features = ["windef", "wingdi", "winuser"] }
However, the example still won't compile:
error[E0277]: the trait bound `Window: raw_window_handle::HasRawWindowHandle` is not satisfied
    --> src\main.rs:9:60
     |
9    |   let mut graphics_context = unsafe { GraphicsContext::new(window) }.unwrap();
     |                                       -------------------- ^^^^^^ the trait `raw_window_handle::HasRawWindowHandle` is not implemented for `Window`
     |                                       |
     |                                       required by a bound introduced by this call
     |
help: trait impl with same name found
    --> C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.27.1\src\window.rs:1039:1
     |
1039 | / unsafe impl HasRawWindowHandle for Window {
1040 | |     /// Returns a [`raw_window_handle::RawWindowHandle`] for the Window
1041 | |     ///
1042 | |     /// ## Platform-specific
...    |
1057 | |     }
1058 | | }
     | |_^
     = note: perhaps two different versions of crate `raw_window_handle` are being used?
     = help: the trait `raw_window_handle::HasRawWindowHandle` is implemented for `&'a T`
note: required by a bound in `GraphicsContext::<W>::new`
    --> C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\softbuffer-0.1.1\src\lib.rs:33:9
     |
33   | impl<W: HasRawWindowHandle> GraphicsContext<W> {
     |         ^^^^^^^^^^^^^^^^^^ required by this bound in `GraphicsContext::<W>::new`

error[E0277]: the trait bound `Window: raw_window_handle::HasRawWindowHandle` is not satisfied
    --> src\main.rs:9:39
     |
9    |   let mut graphics_context = unsafe { GraphicsContext::new(window) }.unwrap();
     |                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `raw_window_handle::HasRawWindowHandle` is not implemented for `Window`
     |
help: trait impl with same name found
    --> C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.27.1\src\window.rs:1039:1
     |
1039 | / unsafe impl HasRawWindowHandle for Window {
1040 | |     /// Returns a [`raw_window_handle::RawWindowHandle`] for the Window
1041 | |     ///
1042 | |     /// ## Platform-specific
...    |
1057 | |     }
1058 | | }
     | |_^
     = note: perhaps two different versions of crate `raw_window_handle` are being used?
     = help: the trait `raw_window_handle::HasRawWindowHandle` is implemented for `&'a T`
note: required by a bound in `GraphicsContext`
    --> C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\softbuffer-0.1.1\src\lib.rs:28:31
     |
28   | pub struct GraphicsContext<W: HasRawWindowHandle> {
     |                               ^^^^^^^^^^^^^^^^^^ required by this bound in `GraphicsContext`

error[E0599]: the method `window` exists for struct `GraphicsContext<Window>`, but its trait bounds were not satisfied
  --> src\main.rs:15:74
   |
15 |       Event::RedrawRequested(window_id) if window_id == graphics_context.window().id() => {
   |                                                                          ^^^^^^ private field, not a method
   |
  ::: C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.27.1\src\window.rs:44:1
   |
44 | pub struct Window {
   | ----------------- doesn't satisfy `Window: raw_window_handle::HasRawWindowHandle`
   |
   = note: the following trait bounds were not satisfied:
           `Window: raw_window_handle::HasRawWindowHandle`

error[E0599]: the method `window` exists for struct `GraphicsContext<Window>`, but its trait bounds were not satisfied
  --> src\main.rs:17:39
   |
17 |           let size = graphics_context.window().inner_size();
   |                                       ^^^^^^ private field, not a method
   |
  ::: C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.27.1\src\window.rs:44:1
   |
44 | pub struct Window {
   | ----------------- doesn't satisfy `Window: raw_window_handle::HasRawWindowHandle`
   |
   = note: the following trait bounds were not satisfied:
           `Window: raw_window_handle::HasRawWindowHandle`

error[E0599]: the method `set_buffer` exists for struct `GraphicsContext<Window>`, but its trait bounds were not satisfied
  --> src\main.rs:34:26
   |
34 |         graphics_context.set_buffer(&buffer, width as u16, height as u16);
   |                          ^^^^^^^^^^ method cannot be called on `GraphicsContext<Window>` due to unsatisfied trait bounds
   |
  ::: C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.27.1\src\window.rs:44:1
   |
44 | pub struct Window {
   | ----------------- doesn't satisfy `Window: raw_window_handle::HasRawWindowHandle`
   |
   = note: the following trait bounds were not satisfied:
           `Window: raw_window_handle::HasRawWindowHandle`

error[E0599]: the method `window` exists for struct `GraphicsContext<Window>`, but its trait bounds were not satisfied
  --> src\main.rs:39:42
   |
39 |       } if window_id == graphics_context.window().id() => {
   |                                          ^^^^^^ private field, not a method
   |
  ::: C:\Users\ilmer\.cargo\registry\src\github.com-1ecc6299db9ec823\winit-0.27.1\src\window.rs:44:1
   |
44 | pub struct Window {
   | ----------------- doesn't satisfy `Window: raw_window_handle::HasRawWindowHandle`
   |
   = note: the following trait bounds were not satisfied:
           `Window: raw_window_handle::HasRawWindowHandle`

Downgrading winit to version 0.26.1 fixes HasRawWindowHandle trait issue.
From winit 0.27.0 (2022-07-26) changelog:
Breaking, update raw-window-handle to v0.5 and implement HasRawDisplayHandle for Window and EventLoopWindowTarget.
From raw-window-handle 0.5.0 (2022-07-14) changelog:
Breaking: The RawWindowHandle variants were split into RawDisplayHandle and RawWindowHandle.


Enumerate items pattern does not work

Microsoft PowerToys version
0.82.0
Installation method
PowerToys auto-update
Running as admin
None
Area(s) with issue?
PowerRename
Steps to reproduce

Have multiple photos
Power rename them
Enable "Use Regular Exrepssions"
Enable "Enumerate Items"
Set .* as "Search for"
Set ${} as "Replace with" (the pattern taken from https://learn.microsoft.com/en-us/windows/powertoys/powerrename#enumerate-items)
See such behavior: ${} is not replaced. Enumeration is just added in braces, the pattern is ignored

✔ Expected Behavior
${} to be replaced with enumeration
❌ Actual Behavior
${} is not replaced with enumeration but enumration is added inside braces instead
Other Software
OS: Windows 11 Pro. 22H2. Build: 22621.3737

I am sorry for opening this issue. Right after opening it I have clicked right mouse button again in my explorer and it crashed, after that new version of PowerToys was correctly, fully set-up so a new action is appeared in my context menu and UI is changed, I guess for some reason update was not fully completed until that moment. Should I open issue about it? I updated by using update button in powertoys itself


[FLINK-14234][runtime] Notifies all kinds of consumable partitions to SchedulingStrategy

What is the purpose of the change
This PR notifies all kinds of consumable partitions to SchedulingStrategy. In this way, the LazyFromSourcesSchedulingStrategy can be simplified a lot since it does not need to maintain result status by itself and does not need to be aware of result partition types.
Brief change log

Notified all kinds of consumable partitions to SchedulingStrategy
Simplified LazyFromSourcesSchedulingStrategy and InputDependencyConstraintChecker

Verifying this change

Added unit tests for consumable partition notification
Updated tests of LazyFromSourcesSchedulingStrategy and InputDependencyConstraintChecker

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

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

Documentation

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

closing since this change is not a must at the moment


feat: add fallback prop to embedded component

This looks pretty clean!
There's some weirdness in having to drill down fallback and isInitialData through all these layers but I think this might have to do more with the original design than your particular changes. Also, having isInitialData as it is right now does make me wonder if instead we should have not overloaded elementTree or element to have both "fake data" and "real data" and instead we'd leave elementTree and element as the source of truth of data (would be null if not present) and we'd separate use an initialElementTree or initialElement prop to provide the initial value, which can then be used or not depending on whether element or elementTree is null or if fallback is present, etc. Don't know about you but that seems more like passing around the "truth" to me since we'd not be passing a computed value and overloading a property with a "fake" value sometimes (i.e., when there's initial data). Seems like things are a bit complicated as they are now.
Note, hasFallback being sent to the builder is a bit different of a story since that's about not being able to send the source of truth, the fallback itself, over a serialization boundary, so we're settling for hasFallback which is a boolean and is thus serializable. You could then argue that this isn't metadata but just part of the regular ol' data. So:
type Document = {
  elementTree: ElementTree | null
  initialElementTree: ElementTree
  fallback: boolean // I'm partial to naming this field `hasFallback`... it's probably a better name
  // ...other properties
}

Note how simple and clear the data structure above it.
And honestly, having fallback be a boolean doesn't make sense just for the builder but also because if the document ends up in Redux state, it's relevant it is serializable too. It's not like we need it from Redux state to render it, since the component that registers it has the fallback already before it passes the boolean to useDocument.

I hear you, and I like what you're suggesting. Since this PR has been around for a while, I'd like to merge this as is, but I want to sit down and have a conversation of what this should look like. Data exchanged between the builder and runtime tends to form a one-way door, so I want to make sure we get this "right" before public release.


Implement teams

Closes #335

Lgtm
Did you test it?

I did throw it on my bot to see if it was properly fetching team details, and it did work
didn't test with a personal application (so not owned by a team) though
I should also mention that this PR allows fetching gifs for guild icons, as it's now a thing with boosting


Autonomous mode

User story 8.1: Autonomous mode
As a car monitor I want the car to move forward and stop to deliver mails.
Acceptance criteria

[ ] The car should stop every 5 meters.
[ ] The car should wait 30 seconds the time for the receiver picks up the mail.
[ ] The control buttons should be disabled

It assigned to someone and not deliver it on time


prefer_interpolation_to_compose_strings swallows arguments to .toString()

The following snippet causes a prefer_interpolation_to_compose_strings warning:
String describe(CupertinoDynamicColor color) {
  return 'Color: ' + color.toString(minLevel: DiagnosticLevel.off);
}

DartCode/dart fix then offers a "Replace with interpolation" fix, which produces:
String describe(CupertinoDynamicColor color) {
  return 'Color: $color';
}

Expected: .toString() should only be removed if it has no arguments.
Tested on Dart 3.0.3 (Flutter).

The lint should not be reported, then the fix will not try to fix it :-)
https://github.com/dart-lang/linter/pull/4437

I agree that the lint is questionable in this case, but wouldn't that also be true for any other method invocation? (e.g. 'Color: ' + computeColor()) I consider this lint to be rather aggressive overall. Seems to me like it'd be more consistent to stop suggesting interpolation for any situation where it's just one string literal + any expression that's more complex than a single identifier (.toString() call notwithstanding).
Also, what about longer chains? For example:
'Hello, ' + foo + '! Check out ' + bar.toString(123) + '!'

Wouldn't this fix still drop the argument?

It is probably better if you open a separate discussion issue in https://github.com/dart-lang/linter itself.
In general, the lint does what it does, if this is too much, there could be another lint that does less.
As for longer chains, I hope that the fix for the linter that I made works for it too.
But I don't have a specific test for it, TBH.


Sync with the main repo

Sync with the main repo up to https://github.com/bitcoin/bitcoin/commit/7190de9fb889bc14cfe8f697ae05e751c6bda54b.
Note 1
The https://github.com/bitcoin/bitcoin/commit/7190de9fb889bc14cfe8f697ae05e751c6bda54b was chosen to sync to make this PR manageable to review. The next commit in the main repo introduces a sophisticated conflicts which needs some special treatment.
Note 2
To make next syncs easier, a few groups of commits were rearranged when they were applied back.
Group A
before:

63e623c6e106702d8717949923c86cb700c61d77 "build, qml: Add qtdeclarative module"
47c2e6342ab92f6732352607266f86e75047ddf1 "build, qml: Add qtquickcontrols2 module"
1de8556cfc9df469d063a4570920e2a95b56d7fe "build, qt: Apply workaround for Qt build system bug for riscv64"
6c58ae5fa0bcc491e2c3caaddf1a77f32980fdcf "qml, doc: Add import QtQuick.Layouts"
641f2a575db51e82f26a9076843ab8fac418ee13 "doc: Drop unneeded runtime dependencies"

after:

3fc6ec8a98136ca7ebb8430a3176b30b11b56124 "depends, qml: Add Qt 5.15.3 Declarative module"
c983645d12dfbda0cb1c46f888def16b44e65c88 "depends, qml: Add Qt 5.15.3 Quick Controls 2 module"
7902e08d4649a265787d6741e7929961b3727ef8 "build, qml: Update bitcoin_qt.m4 with QML paths and plugins"
46af006befa90d752419712fe5e19250d00a22df "qml: Import static plugins"
d51ac6c4971e2b731ef822a1ae93cbabec650abf "doc, qml: Update runtime dependencies"
ae5a391420d18d910ec07c9022f0427b2e290ea3 "qml: Add import QtQuick.Layouts"

Group B
before:

b8413e581bc5b96edf05a559bc350ccd275b3a17 "qml: Add qInstallMessageHandler"
055e5c79e5818898a4b511a199dbe81b2e47692b "qml: Drop erroneous #include <QStringLiteral>"

after:

d0a2ce6ae49fb7af024c90ab659ee514c3d3df8c "qml: Add qInstallMessageHandler"

Group C
before:

6cb9fed38cd9fc2f9227135aab4bb8aaa6c7309d "ci, qml: Add required Qt Quick dev packages"
ea4f68aeaf7a52e09be0624922f4c7dd8bafdcff "ci: Replace bionic with hirsute for system Qt 5.15.2"

after:

a92f553bee9e2b679b744705cf17d75cb6439a24 "ci, qml: Add required Qt Quick dev packages"

Note 3
Commits:

719e1f966871f4f0d8af24142be6e426ced3ee0c "ci: temporarily disable failing ci task"
651dd65615f796fcee72b853a8d79e5cc7f023c3 "build, qml: Fix compiling with GCC 11"

have been effectively dropped as they are no longer required.
Note 4
A new commit 229c56b3d90ce5cd984592a5ff9d42c528237f3c "ci: Fix Win64 task" were added.
Note 5
Errors in the "previous releases..." CI task were solved by clearing CI cache.

Guix builds:
$ find guix-build-$(git rev-parse --short=12 HEAD)/output/ -type f -print0 | env LC_ALL=C sort -z | xargs -r0 sha256sum
787ea22c1cba508827ce1f68d3b5645d0a7c0cabe2d04536c8fae6b9cf119c16  guix-build-229c56b3d90c/output/aarch64-linux-gnu/SHA256SUMS.part
6ee44b279593d8647c96d43a5855b5fec9f736e219d99d5e7478382c8e785161  guix-build-229c56b3d90c/output/aarch64-linux-gnu/bitcoin-229c56b3d90c-aarch64-linux-gnu-debug.tar.gz
fc5142bbee75be4e3d50714ee578943a6e61943ee67c037ade78a763b7ad8fde  guix-build-229c56b3d90c/output/aarch64-linux-gnu/bitcoin-229c56b3d90c-aarch64-linux-gnu.tar.gz
134f91d9b6aca45121087bbe12468b712b7e4171d92cc475800d5baaff7f2261  guix-build-229c56b3d90c/output/arm-linux-gnueabihf/SHA256SUMS.part
7220fa47fb8dc9f77ad988e6e57da3e9a5448ce8e2dda810162e90c719c2f844  guix-build-229c56b3d90c/output/arm-linux-gnueabihf/bitcoin-229c56b3d90c-arm-linux-gnueabihf-debug.tar.gz
a2dde664a055ae34eca1b39a1b6f57f93499dad7c9fa23e10e9e69b6eb9de54e  guix-build-229c56b3d90c/output/arm-linux-gnueabihf/bitcoin-229c56b3d90c-arm-linux-gnueabihf.tar.gz
a44d56f3720e064fe189dea3db4bc3a5bb09641bc2d19da64fe14ea8e61ce6aa  guix-build-229c56b3d90c/output/arm64-apple-darwin/SHA256SUMS.part
b10309a84595bd991dcca098fad17e79c234f55ae3773fcccd535d19556c4938  guix-build-229c56b3d90c/output/arm64-apple-darwin/bitcoin-229c56b3d90c-arm64-apple-darwin-unsigned.dmg
655c8562a8246b66bfae8e37a96c15d2b424751b2b2ed6a1c47ce49bd3e4a927  guix-build-229c56b3d90c/output/arm64-apple-darwin/bitcoin-229c56b3d90c-arm64-apple-darwin-unsigned.tar.gz
f9de01b39b0b0b81fe26f347e13d2496ada04a5d35ab2e1bd8d477dc2713f9d4  guix-build-229c56b3d90c/output/arm64-apple-darwin/bitcoin-229c56b3d90c-arm64-apple-darwin.tar.gz
54b65495a9ea44c924807babe2c33fbad38e826047860d9338c37509d395c822  guix-build-229c56b3d90c/output/dist-archive/bitcoin-229c56b3d90c.tar.gz
c08b72fe9e74aac842ab99cad909dd8ef87a1e9fda377cec166dfaab7d5de13c  guix-build-229c56b3d90c/output/powerpc64-linux-gnu/SHA256SUMS.part
c1c69f324bc016874973a21c79c90d861243bace655ca54fe921ed7edf948129  guix-build-229c56b3d90c/output/powerpc64-linux-gnu/bitcoin-229c56b3d90c-powerpc64-linux-gnu-debug.tar.gz
3e809e29d35855b331a32f2ff33df4896bd522fe57b754803cd5dffdf98d94fb  guix-build-229c56b3d90c/output/powerpc64-linux-gnu/bitcoin-229c56b3d90c-powerpc64-linux-gnu.tar.gz
7ac1aac7a2ddf1010a11afb878d6d0c241c0c1a3f5a15f7089581fffd24ce406  guix-build-229c56b3d90c/output/powerpc64le-linux-gnu/SHA256SUMS.part
73017251c9c00d72f7d5276f7ec8431682f49e2e59f9d8639505d8a6acbb8b10  guix-build-229c56b3d90c/output/powerpc64le-linux-gnu/bitcoin-229c56b3d90c-powerpc64le-linux-gnu-debug.tar.gz
81bab40a6d5f71f6d9f5a0a9d6f6aedfa0194738cc87214bf72a299e10a77f87  guix-build-229c56b3d90c/output/powerpc64le-linux-gnu/bitcoin-229c56b3d90c-powerpc64le-linux-gnu.tar.gz
7f3263abc0de641cd5cab29e4257ee4d740a995876c2adbc8e2163e9c9889fac  guix-build-229c56b3d90c/output/riscv64-linux-gnu/SHA256SUMS.part
5b07bb4ee2bec25e6a503d78d4cbc847eb6da2a521b03a15c9e05529fb522621  guix-build-229c56b3d90c/output/riscv64-linux-gnu/bitcoin-229c56b3d90c-riscv64-linux-gnu-debug.tar.gz
309899e2d7f9fa96de84b5c77c65cba31e4cde8e7ed2d90f100f78459c5b73f7  guix-build-229c56b3d90c/output/riscv64-linux-gnu/bitcoin-229c56b3d90c-riscv64-linux-gnu.tar.gz
f2f9b9f3e0934d2f9bdee7667812f0eefa3fd56bcbf3879ae7992084e38b3a01  guix-build-229c56b3d90c/output/x86_64-apple-darwin/SHA256SUMS.part
02a927161f15e1c766c4cfb007e280eb77ba651e818c74a63d0c780498ff9fce  guix-build-229c56b3d90c/output/x86_64-apple-darwin/bitcoin-229c56b3d90c-x86_64-apple-darwin-unsigned.dmg
8bb2bfe96eafdbf50bdebdf73f355f9b56d410ea1d317a195b03c8872a74398b  guix-build-229c56b3d90c/output/x86_64-apple-darwin/bitcoin-229c56b3d90c-x86_64-apple-darwin-unsigned.tar.gz
d547fd75d8b1c8275ef1007221ee8ee98a7ef5cd8a341bd9049c6502ace477f1  guix-build-229c56b3d90c/output/x86_64-apple-darwin/bitcoin-229c56b3d90c-x86_64-apple-darwin.tar.gz
7e142a98140612b5fcc8a298348d7e452c2d1b58fe6d356c3a66baf9397db5fe  guix-build-229c56b3d90c/output/x86_64-linux-gnu/SHA256SUMS.part
113bb237f595110d712194aeb480fed2db2f94e31ebfe087ba638f73ce2efe71  guix-build-229c56b3d90c/output/x86_64-linux-gnu/bitcoin-229c56b3d90c-x86_64-linux-gnu-debug.tar.gz
69e963b6a184751be8bad3df280e0d15c437da2c5a66cfc23b7cbf3ea09f7727  guix-build-229c56b3d90c/output/x86_64-linux-gnu/bitcoin-229c56b3d90c-x86_64-linux-gnu.tar.gz
5aa4a8ef55a511475975006e820f6f6e47ba5d961c26562f6673a3edd567146b  guix-build-229c56b3d90c/output/x86_64-w64-mingw32/SHA256SUMS.part
9cd6abdbe502e1b96b5a98e5aff5bd17882024153dcf037188c931f96dab86b9  guix-build-229c56b3d90c/output/x86_64-w64-mingw32/bitcoin-229c56b3d90c-win64-debug.zip
0aa6fbf091fa49615c9f392ab9da2a41788b57740da28f712f1c27acaad9952d  guix-build-229c56b3d90c/output/x86_64-w64-mingw32/bitcoin-229c56b3d90c-win64-setup-unsigned.exe
a1ddd861d6a006c1083b44dd29adc8ca5f0881f8a89187ffc812d70414fe9b3d  guix-build-229c56b3d90c/output/x86_64-w64-mingw32/bitcoin-229c56b3d90c-win64-unsigned.tar.gz
3d76a1103a4242cb5a31f8b4a4b2f297948ef4e6cb99967e8adf923d0c7f3b6d  guix-build-229c56b3d90c/output/x86_64-w64-mingw32/bitcoin-229c56b3d90c-win64.zip

Concept ACK, should be noted that some of the commits in the "after" section are effectively new commits being added to the repo. I have compiled and ran this branch locally with a dynamic build on x86 linux. I have also done my own sync where:

I reverted the following commits, the same as being reverted here; with this I confirmed that the commits we are reverting are required to sync up to the target commit:

9b9d198407118475d6ba6dd315991f2a42c813b0
dbf77f268bd64e53519d513cc0de22bf8a492bc7
f80373023608303ef8c6c08c44c3915be2817aa2
e495a83318d2a4828a1a2f322c5e782d37ebc643
56298863e52f8521a1197c7fdfc0bfadf52c58d3
b21b3c9da34fbe45032b337c340342da730549c0
126df091fbff6fe6a22a866cf3cecd5e48769740
5d4ded43092a55aa246792a6085159d6956f9523
641f2a575db51e82f26a9076843ab8fac418ee13
90305f62a405d1cae31c6d68781d85735fe50cd4
c7647c53b117d024fba92a78dbd0db081008e974
055e5c79e5818898a4b511a199dbe81b2e47692b
6c58ae5fa0bcc491e2c3caaddf1a77f32980fdcf
b8413e581bc5b96edf05a559bc350ccd275b3a17
1de8556cfc9df469d063a4570920e2a95b56d7fe
47c2e6342ab92f6732352607266f86e75047ddf1
63e623c6e106702d8717949923c86cb700c61d77
ea4f68aeaf7a52e09be0624922f4c7dd8bafdcff
6cb9fed38cd9fc2f9227135aab4bb8aaa6c7309d
651dd65615f796fcee72b853a8d79e5cc7f023c3
719e1f966871f4f0d8af24142be6e426ced3ee0c

Fetched the upstream commit

git fetch https://github.com/bitcoin/bitcoin
git merge 7190de9

Cherry Picked the commits from this branch, as some new work is done here; then compiled and ran

GUIX HASHES:
currently building


VQ-VAE inference on trained prior

After training prior with PixelCNN, during inference probabilities of codebook indices are calculated. There's a distribution sampler used to pick/sample a index instead of choosing the highest probability index-
outputs = pixel_cnn(inputs, training=False)
categorical_layer = tfp.layers.DistributionLambda(tfp.distributions.Categorical)
outputs = categorical_layer(outputs)

Why is that so? Why use this sampler? Is this distribution what makes the PixelCNN model generative? On removing this distribution sampler, the model is deterministic as it's just a bunch of convolutional layers. Can someone kindly explain the necessity of these lines of code?

@fchollet, can you please explain. Thankyou.


Instruct-Pix2Pix Broken

Today, I tried to use Instruct-Pix2Pix but it wouldn't work. I'm using the instruct-pix2pix-00-22000 model like I'm supposed to.
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/dist-packages/gradio/routes.py", line 337, in run_predict
    output = await app.get_blocks().process_api(
  File "/usr/local/lib/python3.9/dist-packages/gradio/blocks.py", line 1015, in process_api
    result = await self.call_function(
  File "/usr/local/lib/python3.9/dist-packages/gradio/blocks.py", line 833, in call_function
    prediction = await anyio.to_thread.run_sync(
  File "/usr/local/lib/python3.9/dist-packages/anyio/to_thread.py", line 31, in run_sync
    return await get_asynclib().run_sync_in_worker_thread(
  File "/usr/local/lib/python3.9/dist-packages/anyio/_backends/_asyncio.py", line 937, in run_sync_in_worker_thread
    return await future
  File "/usr/local/lib/python3.9/dist-packages/anyio/_backends/_asyncio.py", line 867, in run
    result = context.run(func, *args)
  File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/stable-diffusion-webui-instruct-pix2pix/scripts/instruct-pix2pix.py", line 310, in generate
    raise e
  File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/stable-diffusion-webui-instruct-pix2pix/scripts/instruct-pix2pix.py", line 253, in generate
    in_image = ImageOps.fit(input_image, (width, height), method=Image.Resampling.LANCZOS)
  File "/usr/local/lib/python3.9/dist-packages/PIL/Image.py", line 77, in __getattr__
    raise AttributeError(f"module '{__name__}' has no attribute '{name}'")
AttributeError: module 'PIL.Image' has no attribute 'Resampling'

bro how did you solve it?


Avoid version clashes in NuGet test cases

As described in PR #67 it seems that it is currently not possible to load two different versions of the same NuGet dependency in one test run. This led to a problem (which will occur again at some point in the future) with Test_NuGet_002 and Test_NuGet_010. The former uses the current version for NodaTime, while the latter uses a fixed version.
I propose that we should rework all NuGet test cases to use fixed (and equal) versions of all NuGet dependencies used to avoid our test run unexpectedly breaking when a new version of some dependency gets released to NuGet.

Tests are now executed in an independent process, fixing the problem.


Doesn't work with Swift 2

I found this through your blog (thx!)
however I couldn't use because it doesn't compile.

I haven't tried with Swift 2 but I can see why it doesn't compile. Easy fixes, I will update in few days.

Sounds great. Thanks!

Updated


Can docker_auth work with docker login?

Hi,
I would like to allow users to log in my private registry using their google accounts. I've set up docker_auth up to the point where I can navigate to https://<MY_DOMAIN>:5001/ then there will be a link to login with google account. After logging in I get the following message "Server logged in; now run "docker login YOUR_REGISTRY_FQDN", use <EMAIL_ACCOUNT> as login and  as password."
When I run docker login https://<MY_DOMAIN>:5000/ on the command line and I input the login and password proposed, I get the following message:

Error response from daemon: Get http://<MY_DOMAIN>:5000/v2/: unable to decode token response: invalid character '<' looking for beginning of value

How can we make this work? Can we completely by-pass the browser and just do everything on the command line? If so, why do I get redirected to HTTP instead of HTTPS when I log in? And why do I get redirected to /v2/?
Thank you in advance

It is possible to login with Google accounts currently. Could you provide a sanitized version of your auth_server config, and docker-registry config?

It is possible to login with Google accounts currently. Could you provide a sanitized version of your auth_server config, and docker-registry config?

Closing, but please feel free to re-open if you are still facing this issue.


Remove Unnecessary code from React-D3-Graph

Clean up react-d3-graph so we only have the minimum amount of code for our visualization to work.

[ ] Move Graph components into a single "Graph" folder
[ ] Remove unnecessary files

No longer using react-d3-graph.


XamlTypeInfo.g.cpp adds providers for project references, but doesn't #include needed headers

(See discussion started here: https://github.com/microsoft/ProjectReunion/discussions/763)

Create a blank WinUI app (App1)
Add a WinUI Runtime Component (Controls1)
Using the template, add a UserControl to the Runtime Component (Controls1)
Add a project reference in the app to the component (App1 references Controls1).

Building the project after this results in a build error in XamlTypeInfo.g.cpp:
std::vector<::winrt::Microsoft::UI::Xaml::Markup::IXamlMetadataProvider> const& XamlTypeInfoProvider::OtherProviders()
{
    if (_otherProviders.empty())
    {
        _otherProviders.push_back(::winrt::Controls1::XamlMetaDataProvider()); // <-- ERROR
        _otherProviders.push_back(::winrt::Microsoft::UI::Xaml::XamlTypeInfo::XamlControlsXamlMetaDataProvider());
    }
    return _otherProviders;
}

This breaks because the header for Controls1 wasn't included. XamlTypeInfo.g.cpp should have this added:
#include <winrt/Controls1.h>

It's possible to work around this by adding the missing #include to the precompiled header (pch.h), but XamlTypeInfo.g.cpp really should be self-sufficient.

@alwu-msft FYI

@RealTommyKlein I remember this coming up before around the Preview 1 timeframe, but I don't recall why we left it the way it was.

@alwu-msft - IIRC that was a slightly different self-sufficiency issue (some of the compiler's generated code relied on the default pch.h - if the default #includes were removed, we'd get errors similar to this bug).  For this issue in particular, the compiler needs to dynamically determine which headers it needs to include.
I don't think that would be too difficult for XamlTypeInfo.g.cpp since we know all the types we're generating for, and can determine the header name to include by the types' namespace (e.g. if we're generating type info a Controls1.UserControl, we need to include the <winrt/Controls1.h> header).  We should also do the same thing for our generated per-page files like MainPage.xaml.g.hpp that gets generated for a MainPage.xaml.  For them, we'd need to associate which pages use which types so we know which headers to include for each page, which would also lay the foundation for future incremental build improvements by only reparsing .xaml files which we know contain changed types.

Fixed in 1.4.0. @bpulliam please close this issue as I cannot. :)


I am having trouble using the z module in PowerShell. Can you help me identify and fix the problems?

Hi @epenflow - Thanks for your report.
I can see you've got a heavily customized shell which can potentially conflict with this module. Can you please try stock standard PowerShell session and then perform a Import-Module z to see if it works? We can go from there.

Hi, thanks for the response. I'm already disable all my powershell configurations but still the issue persits

1, Was working previously up until your crash?
2. Instead of z someFolder like in your screenshot, are you able to cd someOtherFolder? If you can then check the .cdHistory file to see if the entry has been made.
Without being able to remote into your machine to debug, the only thing I can suggest is to:

Delete the .cdHistory file
Delete z.psm1 module and the module folder it is within and then re-install z using Install-Module z -AllowClobber'

Let me know how you get on.

Actually the cd and z command work but whenever i'm using z command it always thrown that error. I'm already try to reinstall it but still this issue persists maybe i'll try to delete cd history as you said.

Thanks @badmotorfinger. Deleting .cdHistory resolved the issue

I'm glad it worked in the end, I was starting to get worried :)


Add balancemode split one chevs

Fixes #218

Is there a reason why there are so many seemingly unrelated changes?

@badosu I can clean it up to only have the minimal required changes. I'll get back to you. Here's the state so far:
Split_one_chevs.ex : Required
balance_lib.ex  : Required
Consul_commands.ex : Required
Consul_server.ex : Not required; but required for Hailstorm test
Cache_user.ex : Not required
Teiserver_configs.ex : Required to match production. Currently in production you use "Role" to determine chev level
Fake_data.ex : Not required; I just made this to make it easier to add spadsbot
Hailstorm_controller.ex : Not required, but required for Hailstorm test
Balancer_data.ex : Not required, but without it, it's hard to test. The database needs to be setup with multiple users at specific OS and chev level
Balancer_util.ex : As above
Since you are experienced with Elixir do you have suggestions on how to get the database with some fake users that have these settings:
Chev 1, OS 17
Chev 1, OS 17
Chev 2, OS 20
Chev 2, OS 15
Effectively the files in test_util are runnable to allow you to do that but maybe you know a better way.

I'll try setting up and running the tests in a manageable timeframe.
Meanwhile this should help you: https://hexdocs.pm/ecto/Ecto.Repo.html#c:insert/2
I wasn't able to find a schema dump in /priv or a file structure I'm familiar with, meanwhile it seems you want to insert an account and a last rating record for that user id.

Closing pull request
Use instead:
https://github.com/beyond-all-reason/teiserver/pull/235
which has minimal changes


how to remove  Controls(ToolBar)

Want to clear the tool in the red box,
Not shown on map

Remove this in your code
ap.pm.addControls({                 position: 'topleft',             });

Remove this from your code
map.pm.addControls({                 position: 'topleft',             });

The toolbar is used in the previous module. I don't want to delete the next module

map.pm.removeControls();


remove depency restriction

Remove >=0.55.0

To prevent https://github.com/lukasalexanderweber/stitching/issues/16

Closed with https://github.com/lukasalexanderweber/lir/commit/7ecfadaf1c08b8aa732bd5aa989218e874f73231


Add Missing API: HttpContext.ClearError

Summary
When I try the IHttpModule and HttpApplication in the adapter, I found that HttpContext.ClearError is used in my module(in Sharepoint Online) but it is not supported.
Motivation and goals
HttpContext.ClearError is used in my module(in Sharepoint Online) but it is not supported. I wonder if there is plan to support the API.
In scope
HttpContext.ClearError
Usage example:
context.Response.Clear();
context.ClearError();
context.Response.Output.Write("
error
" )
context.Response.End();

Discussed during triage, seems like we could either make this one be a no-op


Fix a typo in the docs

This fixes the comment by pointing it at the correct part of the spec (as of current 1.2 version of the spec).

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Pull access denied for flame

sudo docker run -p 5005:5005 -v /home//flame:/app/data -e PASSWORD=flame_password flame
Unable to find image 'flame:latest' locally
docker: Error response from daemon: pull access denied for flame, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.
sudo docker pull pawelmalak/flame
Using default tag: latest
latest: Pulling from pawelmalak/flame
Digest: sha256:ccdfec957cadad538b7fbb4b32647cffb1c8d3f6de93f211a497e5d4121d1b18
Status: Image is up to date for pawelmalak/flame:latest
docker.io/pawelmalak/flame:latest
I feel like I'm missing something silly here

You are pulling image from pawelmalak/flame but in your run command you are only passing flame as an image name.
You also have double // in your volume path.

Oh, I was just following the Installation from the readme. I'm somewhat new with docker. Thanks for the quick reply!

That's ok. Did you get it working?

Yes. Thanks again! You might want to edit to make a bit more n00b friendly. You could also add a note about using -d so it runs in the background :)


Postgres uint32 uint64 and Test imports

Hey, so I am having issues when using models with fields of type uint32, uint64 and my postgresql database.
I read the code and found that go uint32 fields are treated just like regular 32 bit signed integers and assigned an a column type integer.
This poses problems when I want to store an actual unsigned int with a value that is greater than the max signed int.
I forked and did some changes and would love to PR this code, however:

changes could be considered API changing since types for columns in existing code will change but I'm not sure.
To test out if I had indeed broken anything, I changed the import structure for local tests from import "github.com/jinzhu/gorm" to relative style import "../gorm" so I could run tests against my local repo. I guess you hadn't done this for a reason, but I don't know what it is.

Upon further testing and inspection of Postgres, I see now why things are done as they were..
Sorry for bringing this up.


refactor: use macros to dedup code

merge without approval given this change is small, and I have another PR pending...


test_torture.sh wrapper for CI

we probably should automate test_torture.sh but we might not be able to run it in GH actions w/ meaningful results

@jayunit100 what is that test_torture.sh you are mentioning? If this is something you want to be added, can you give some details?


Fix overflow bug exposed by Hypothesis failures

NumPy's prod() function uses np.int64 types which cause overflow for some Hypothesis tests (see #41). Python 3.8 has a new math.prod() function which does not suffer from this problem, since it uses Python ints.
The fix here introduces a local implementation of prod() that uses Python ints, making the behaviour the same for all versions of Python.
Fixes #41

Thanks @shoyer. I've made your suggested changes.

Thanks!


Wrap subprocess so as to enable testing failure error messages

First this moves from subprocess.check_call to subprocess.check_output guided by subprocess documentation: https://docs.python.org/3/library/subprocess.html#subprocess.check_call (done on main)
Next moved from using sys.exit(returncode) to sys.exit(msg) in order to be able to easily test the error message (but have to accept always return code 1).
Sample command for testing:
$ python -c "from pyani_plus.utils import check_output; check_output(['blastn', '-task','undefined'])"; echo "Return code $?"

Note the first commit, pytest capsys was not working for me to test the error message by looking in stderr instead (and I don't understand why - I thought this was working before).
Type of change

[ ] Bug fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality not to work as expected)
[ ] This change requires a documentation update
[ ] This is a documentation update

Action Checklist

[x] Work on a single issue/concept (if there are multiple separate issues to address, please use a separate pull request for each)
[ ] Fork the pyani-plus repository under your own account (please allow write access for repository maintainers)
[x] Set up an appropriate development environment (please see CONTRIBUTING.md for this repository)
[x] Create a new branch with a short, descriptive name
[x] Work on this branch

[x] style guidelines have been followed (please see CONTRIBUTING.md for this repository)
[x] new code is commented, especially in hard-to-understand areas
[x] corresponding changes to documentation have been made
[x] tests for the change have been added that demonstrate the fix or feature works

[x] Test locally with pytest-plus -v non-passing code will not be merged
[x] Rebase against origin/master
[x] Check changes with linting/formatting tools before submission (please see CONTRIBUTING.md for this repository)
[x] Commit branch
[x] Submit pull request, describing the content and intent of the pull request
[x] Request a code review
[x] Continue the discussion at Pull requests section in the pyan-plus repository

Merge now?


Fix GitThisAssemblyMetadata

Fix #108 by explicitly declaring property before used. Default behavior is preserved by defaulting to false. Attached sample program and NuGet
Environment
$ dotnet --version
3.1.300-preview-015048
$ dotnet msbuild --help
Microsoft (R) Build Engine version 16.6.0-preview-20162-03+00781ad13 for .NET Core

CSharp.zip

I don't fully understand how this could make a difference, but it's harmless to declare it :)

Me neither :) Thanks for merging


Table-row-after and Table-column-after missing in 2.x?

Issue Type (delete the irrelevant ones)

[x] Question
I have used Table-row-after in the 1.x and now i have upgraded to 2.x and its now working. Cant find the documentation either

Specs
What version are you using?
vue-good-table 1.x
What browser?
Chrome

hey, @shahzadcacf custom rows have been simplified a lot in 2.0. You no longer need to specify each td for custom template, just the ones that need to be custom, relevant documentation:
https://github.com/xaksis/vue-good-table/wiki/Guide-to-upgrade-from-1.x-to-v2.0#custom-tdrow-now-works-differently
To see a working example of how you'd create before and after columns, you can look at this jsfiddle:
https://jsfiddle.net/aks9800/hsf0sqf8/
closing.


Snippets show in inline suggestions even though they are turned off

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: Windows 11
OS Version: 1.75.1

Steps to Reproduce:
Using the following settings:

open a typescript file
type fo within a method/function
the following gets output (might have to navigate through some of the suggestions) even though snippets are off:

Thanks for the patience. I cannot reproduce, please share you more settings that might influence this. Also share data in a copy-paste friendly way (text over images)

@jrieken Here are the minimum settings that I am using to reproduce (all extensions disabled):
{
    "editor.inlineSuggest.enabled": true,
    "editor.snippetSuggestions": "none",
    "editor.quickSuggestions": {
        "other": "inline",
        "comments": "inline",
        "strings": "inline"
    },
    "editor.inlineSuggest.showToolbar": "always"
}

Once typing fo and going to the 3rd suggestion, I get this as a suggestion:

I can't figure out how to get that ghost text to show up for suggestions to verify this. I've never seen that ghost text for anything but copilot completions
Do I need a suggestion provider extension?

You are right. I made a refactoring after this fix and that broke this feature 😨 Thanks for the diligence on this one!

To verify, use the steps from https://github.com/microsoft/vscode/issues/175190#issuecomment-1845534585. Make sure no snippets completions are ghost-texted with "editor.snippetSuggestions": "none" and that they are when the setting is set accordingly

I still cannot get snippet completions to show up @jrieken

@meganrogge You need to say what you are trying because I do see them working just fine

This works correctly for me now, no snippets with "editor.snippetSuggestions": "none",, and they do show up without it.

Bang on. The whole point is that the editor.snippetSuggestions  is honored also for ghost suggestions

editor.snippetSuggestions:inline

@meganrogge this is about ghost test, please see https://github.com/microsoft/vscode/issues/175190#issuecomment-1911676841 and the comment linked from there

🤦🏼♀ there was a syntax error in my settings.json file, so the settings did not get applied. Now it works 👍🏼


Adding new components after creation

Potentially out of scope but it would be good to add in other bits after creating the initial package.
Things that would be nice to add

a new node cpp or python
new msg/service or action

It would be a nice addition, but leaving it in the too hard basket for now.
I do some pretty blunt things to the directory where a template is initialised, and would have to proceed extremely cautiously to ensure I don't clobber any existing files.


Using animated WebP when optimising GIF

Codecov Report

Merging #23 (13440b9) into master (f7588b7) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
+ Coverage   78.70%   78.76%   +0.05%
==========================================
  Files           5        5
  Lines         371      372       +1
==========================================
+ Hits          292      293       +1
  Misses         45       45
  Partials       34       34

Impacted Files
Coverage Δ

img/processor/imagemagick.go
73.75% <100.00%> (+0.16%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f7588b7...13440b9. Read the comment docs.

Codecov Report

Merging #23 (13440b9) into master (f7588b7) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #23      +/-   ##
==========================================
+ Coverage   78.70%   78.76%   +0.05%
==========================================
  Files           5        5
  Lines         371      372       +1
==========================================
+ Hits          292      293       +1
  Misses         45       45
  Partials       34       34

Impacted Files
Coverage Δ

img/processor/imagemagick.go
73.75% <100.00%> (+0.16%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f7588b7...13440b9. Read the comment docs.


Expose formatting via a command

Right now extension does not expose a formatting command. It should implement that

Actually this is already handled by the language server, I just need to add some docs.


OCPBUGS-13946: do not use one second timeout when asserting a webhook connection

Previously the dial timeout to a webook was set to one second which seems to be very aggressive and could cause failures which could put the operator into degraded state.
This PR reads the timeout value for a webhook from the spec or uses a default value of 10 seconds if it wasn't specified

Is this a good time to add test coverage for dial timeouts?

Is this a good time to add test coverage for dial timeouts?

It turns out that unit test for dial timeouts would complicated, we would need to start a web server, a fake dns server and we would need to measure duration of the test.
I was also thinking about refactoring the code just to validate if a timeout value is applied but i don’t see a huge gain here.
I would like to merge this PR without timeout coverage.

/lgtm


fix: update supported tf version to have < 0.14.0

modules fails to destroy EKS cluster in 0.14.5 because destroys don't refresh.
PR o'clock
Description

In terraform 0.14+ destroy command no loner refreshes the state of resources before generating execution plan (like it did in 0.13.X). terraform apply still does the refresh, that's why this issue is more frequent the more time elapses after applying.

https://github.com/terraform-aws-modules/terraform-aws-eks/issues/1162#issuecomment-767700530
As a result, the module will fail to destroy all of the resources it manages.
I should say that there is a workaround in 0.14.5. The user will be required to run terraform refresh then terraform destroy.
Checklist

[x] CI tests are passing
[x] README.md has been updated after any changes to variables and outputs. See https://github.com/terraform-aws-modules/terraform-aws-eks/#doc-generation

I dont think does limiting terraform version is good approach. I would rather try to solve a root cause than limiting terraform updates, especially that 0.14 is considered now as desired and stable version

@daroga0002 I agree, let's fix it because this problem isn't going away. But this module claims to support 0.14.0 when that is not entirely true. Perhaps we should add a note to the README that says:

If you are using a terraform version greater than 0.14.0, you will need to run terraform refresh prior to running terraform destroy.

I just thought something like this would save people the 30 minutes of head scratching when the terraform destroy fails.

@aidanmelen can you describe a issue more (where it is failing, does those are only some module inputs required)?

@daroga0002 The error can be reproduced by running the basic example on terraform 0.14.X.
The specific resource that the module fails to delete is:

Error: Unauthorized

module.kubernetes_cluster.module.eks.kubernetes_config_map.aws_auth[0] will be destroyed

There is a lot more context in this related issue #1162 than I can provide here on my own. This seems to be causing confusion for a number of people.

Prior to Terraform version 0.14, data sources would be refreshed before destroy. This functionality has been added back to Terraform 0.15. It's an issue with Terraform core. Unless they decide to backport that fix to 0.14, it makes sense to limit the versions that are used with this module.

It looks like the fix will be too difficult to backport to 0.14. https://github.com/hashicorp/terraform/issues/28179#issuecomment-805797078

We don't have to restrict the max version of the Terraform in the module.
Btw, v15.1.0 has been just released where Terraform 0.15 is supported and the minimum version of Terraform is updated to be 0.13.1.


Permission handling in playstore

Actually, I am developing an e-commerce application using this great library. I want to upload my app to the play store. Then should I mention the permissions (camera and storage) in my play console as the library is handling the permissions automatically?
I have not any experience with the play console, please help me.

no need .

@sitamadex11 ImagePicker doesn't require any permission so you won't face any issue with the google play store.


Fixes a (very unlikely to be hit) bug that'll cause a failure to up…

Time partially sponsored by DealerInspire, the innovative, scrappy disruptor building unprecedented technologies for dealerships to sell and service more cars.

Fixes a (very unlikely to be hit) bug that'll cause a failure to upload if the passed in resource is the exact same length as the chunk size
Fixes a bug where chunk size wasn't being detected as a multiple of 262,144B (256KB), causing a failure to upload
Fixes a bug where out of memory errors are likely when working with larger files due to chunk size being based on the memory limit, rather than the remaining available memory

@DynamoGeek When applying this PR, it seems that it will fail if you upload chunks to the root folder while specifying an arbitrary folder ID for the root directory. However, uploading to subfolders is not a problem. I have not found the cause yet.
Thanks!

@DynamoGeek Thanks! 👍

@nao-pon Thank YOU! I appreciate the quick and careful review. This'll help us get the memory usage in one of our jobs under control. 😄


Optimize DOM object reuse

import DOM from '@mojojs/dom';

const html = new DOM('
Test 1

Test 2
');
const div = new DOM('
Hello World!
', {fragment: true});
html.at('p').replace(div);

It would be nice if the case above was optimized, so that replace didn't have to stringify and re-parse the div snippet. Since our node tree is made up of classes, a simple deep clone on it won't work, but we could add clone methods to all the node classes, so that const clone = div.currentNode.clone() would simply give us a proper deep cloned version with classes in tact. Then all the modification methods of the DOM object could rely on that.

Added with https://github.com/mojolicious/dom.js/commit/4d34d31d64a1c3b926aad0bea1ab393213c00242.


Add star history

This PR adds star history like this:

The quality of Julia package should be measured not by the number of stars it has, but by its functionality, ease of use, and the correctness of its design. Additionally, it's important to recognize that the objectives of packages are not always identical and often involve trade-offs.
On the other hand, in situations where the comparison of packages is not sufficiently clear and well-documented, the history of stars can be useful.
When generating documentation with Franklin.jl, it would be more beneficial and of higher priority to create a system that actually runs the package's code for comparison. This would be truly useful to people. However, since implementing star history was easy, I decided to give it a try.

Big fan of the star history! It really gives some depth about the relative standing and long-term stability of the packages. Really good comparison material!

Thanks for the review!


flutter run failed with error “Could not resolve the package 'characters' in 'package:characters/characters.dart'.”

Flutter run command
Output
Could not resolve the package 'characters' in 'package:characters/characters.dart'.
flutter doctor
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.47.2)
[✓] Connected device (3 available)

I just resolved with https://github.com/flutter/flutter/issues/59645#issuecomment-645236663


mac-6, mac-24 and mac-9 lost external connection phone device.

Type of Request
bug
Infrastructure Environment
LUCI, Github, Cocoon scheduler, Autosubmit, etc...
What is happening?
mac-6, mac-24 and mac-9 lost external connection phone device.

Steps to reproduce
Step 1:
Step 2:
..
Step n:
Expected results
I expect to see X when Y is finished.

Rebooting all three machines to restore all connections.


Document creation fails on fresh clone due to missing dist directory

>> pandoc: dist/essential-scala.pdf: openBinaryFile: does not exist (No such file or directory)
>> Shell command exited with code 1
Warning: Task "pandoc:pdf" failed. Use --force to continue.

Aborted due to warnings.

I experiment just the same problem...

I solved this by creating the dist directory inside the container and then running the command:
mkdir dist
sbt pdf # (or grunt pdf)


[AIRFLOW-1712] Log SSHOperator output

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1712

Description

[x] Here are some details about my PR, including screenshots of any UI changes:

After commiting AIRFLOW-756 and AIRFLOW-751, SSHOperator does not log stdout like SSHExecutor did. This commit logs SSHOperator stdout again.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:

There are already SSHOperator tests to assert that do_xcom_push keeps saving output.

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Codecov Report

Merging #2686 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2686   +/-   ##
=======================================
  Coverage   71.68%   71.68%
=======================================
  Files         154      154
  Lines       11814    11814
=======================================
  Hits         8469     8469
  Misses       3345     3345

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9f2c16a...83c2610. Read the comment docs.

I think this is superseded by https://github.com/apache/incubator-airflow/pull/2745 can you confirm?

Hi. No, its not superseded. Just deployed #2745 and SSHOperator doesn't log stdout.
For example, for a simple SSHOperator task with the command command = 'for x in {1..5}; do export randnum=$(($RANDOM % 10 + 5)); echo "$x: $randnum"; sleep "$randnum"; done '  all the log I get is:
[2017-11-02 09:00:16,270] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:00:16,269] {__init__.py} INFO - Using executor LocalExecutor
[2017-11-02 09:00:16,693] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:00:16,692] {models.py} INFO - Filling up the DagBag from /Users/opringao/airflow/dags/test_ssh.py
[2017-11-02 09:00:17,222] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:00:17,222] {base_hook.py} INFO - Using connection to: XXX.XXX.XXX.XXX
[2017-11-02 09:00:17,401] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:00:17,400] {transport.py} INFO - Connected (version 2.0, client OpenSSH_5.3p1)
[2017-11-02 09:00:18,407] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:00:18,407] {transport.py} INFO - Authentication (publickey) successful!

While, with the change I suggest the log is:
[2017-11-02 09:10:06,666] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:10:06,665] {__init__.py} INFO - Using executor LocalExecutor
[2017-11-02 09:10:06,726] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:10:06,725] {models.py} INFO - Filling up the DagBag from /Users/opringao/airflow/dags/test_ssh.py
[2017-11-02 09:10:06,864] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:10:06,864] {base_hook.py} INFO - Using connection to: XXX.XXX.XXX.XXX
[2017-11-02 09:10:08,382] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:10:08,381] {ssh_operator.py} INFO - 1: 5
[2017-11-02 09:10:13,336] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:10:13,336] {ssh_operator.py} INFO - 2: 14
[2017-11-02 09:10:27,344] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:10:27,343] {ssh_operator.py} INFO - 3: 14
[2017-11-02 09:10:41,355] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:10:41,354] {ssh_operator.py} INFO - 4: 11
[2017-11-02 09:10:52,356] {base_task_runner.py} INFO - Subtask: [2017-11-02 09:10:52,355] {ssh_operator.py} INFO - 5: 8

AH makes sense, paramiko redirects its stdout, stderr itself.


Add tests for some commands

Add tests for:

AddNoteCommand
DeleteNoteCommand
AddParticipationCommand
AddTaskCommand
All 3 Mark commands
All 3 Unmark commands
Parsers for commands listed above

Codecov Report

Merging #165 (b7dc3ba) into master (e8d72a7) will increase coverage by 14.36%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##             master     #165       +/-   ##
=============================================
+ Coverage     36.55%   50.92%   +14.36%
- Complexity      525      735      +210
=============================================
  Files           155      155
  Lines          3173     3181        +8
  Branches        388      388
=============================================
+ Hits           1160     1620      +460
+ Misses         1956     1473      -483
- Partials         57       88       +31

Impacted Files
Coverage Δ

.../java/jarvis/logic/commands/MarkLessonCommand.java
100.00% <100.00%> (+100.00%)
:arrow_up:

...in/java/jarvis/logic/commands/MarkTaskCommand.java
100.00% <100.00%> (+100.00%)
:arrow_up:

...ava/jarvis/logic/commands/UnmarkLessonCommand.java
100.00% <100.00%> (+100.00%)
:arrow_up:

src/main/java/jarvis/model/Lesson.java
63.95% <100.00%> (+23.95%)
:arrow_up:

src/main/java/jarvis/model/UniqueLessonList.java
48.21% <100.00%> (+28.21%)
:arrow_up:

src/main/java/jarvis/model/UniqueStudentList.java
93.75% <100.00%> (+0.13%)
:arrow_up:

src/main/java/jarvis/model/UniqueTaskList.java
51.06% <100.00%> (+29.32%)
:arrow_up:

src/main/java/jarvis/model/Studio.java
64.86% <0.00%> (+2.70%)
:arrow_up:

src/main/java/jarvis/model/TimePeriod.java
89.28% <0.00%> (+3.57%)
:arrow_up:

src/main/java/jarvis/model/Consult.java
70.00% <0.00%> (+5.00%)
:arrow_up:

... and 33 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Code First: Infer FK required-ness when introducing FKs by convention

Given:
modelBuilder
       .Entity<ExpenseLine>(e =>
       {
           e.ManyToOne(el => el.ExpenseCategory);
       });

public class ExpenseLine
    {
        public int Id { get; set; }
        public int ExpenseCategoryId { get; set; }
        public ExpenseCategory ExpenseCategory { get; set; }
    }

I expected the introduced FK to be required because the CLR property was non nullable.

@smitpatel this is now assigned to you. Please talk to @AndriySvyryd about the details of what needs to be done.

This was already fixed and verified by ForeignKeyPropertyDiscoveryConventionTest


chore: Add a specialized statefulMap internal implement.

Motivation:
In https://github.com/apache/incubator-pekko-http/issues/395 , @jrudolph said the current change may hurt performance, additional allocation for (State, A), So I submit this, a simpler but still with the drawback for internal usage.
Result:
Performance keeped.

@Roiocam would you like give this a look,thanks.

do we need this now that statefulMap has not been deprected?

I think we can close this


Updated link to documentation

Original README file had a wrong link to the documentation, updated

/ok-to-test

/approve
/lgtm


Ability to customize the quick access menu

Description of the new feature / enhancement
I would like to customize the quick access menu to add or remove items that I commonly use.

Scenario when this would be used?
This would allow me to be able to access the powertoy tools that I use with a right-click of my mouse.
Supporting information
No response

Any workarounds?

Any workarounds?

Not customizable so there are no work-arounds.
/dup #24283


[FLINK-6776] [runtime] Use skip instead of seek for small forward rep…

…ositioning in DFS streams
Reading checkpoint meta data and finding key-groups in restores sometimes require to seek in input streams. Currently, we always use a seek, even for small position changes. As small true seeks are far more expensive than small reads/skips, we should just skip over small gaps instead of performing the seek.

Updated with comments.

Merged in 9141379f6d.


pglite-sync not working with electric >=0.8

Things seem to work against the 0.7.7 image but stop after that. My understanding is that the URL format changed recently, and that doesn't appear to have been included in pglite-sync yet. I tried doing both (/v1/shape/todo?table=todo) which seem to emit a query but it still borks.

Fixed by https://github.com/electric-sql/pglite/pull/435. Thanks


MSCRM Pack Solution - Allow Extract

When automating the build package process it's required that the solution be extracted with the solutionpackager.exe app prior to packing it with MSCRM Pack Solution. It would be better if we were able to do the extraction as part of the build process prior to the pack in order to align versioning from the DEV instance of CRM.
I have a build job which does the following:
-Pulls the solution nightly from DEV
-Stores that in VSTS
Followed by a Release process that does the following:
-Builds a package based on the source
-Stores that in VSTS
Between these I'm unable to run solutionpackager.exe with the extract in order to close the loop between the processes.
Thanks

@sporens thx for sharing your experience. As per current design principals, the unpack is best executed by the developer who is making the changes and is able to look at any conflicts and confirm what really needs to be checked-in. This is based on that source control should be golden source or all code and customisations.
What I normally do is trigger a build on every check-in that packs and promotes the changes to a stage environment.
In your current design, how do you ensure that unfinished changes are not checked-in and promoted as part of the release at night?

We have a development environment where we’re focused on adding functionality against the core entities. Thus we’re clear on the conflicts and I’m more interested in moving the code out of CRM into a package and have an easy deployment for the testing team.
From: WaelHamze<EMAIL_ADDRESS>Sent: Tuesday, August 15, 2017 12:53 PM
To: WaelHamze/xrm-ci-framework<EMAIL_ADDRESS>Cc: Steven Sporen<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [WaelHamze/xrm-ci-framework] MSCRM Pack Solution - Allow Extract (#36)
@sporenshttps://github.com/sporens thx for sharing your experience. As per current design principals, the unpack is best executed by the developer who is making the changes and is able to look at any conflicts and confirm what really needs to be checked-in. This is based on that source control should be golden source or all code and customisations.
What I normally do is trigger a build on every check-in that packs and promotes the changes to a stage environment.
In your current design, how do you ensure that unfinished changes are not checked-in and promoted as part of the release at night?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/WaelHamze/xrm-ci-framework/issues/36#issuecomment-322570544, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AP-OrJH8vcqjD_JVQgR_ETKCbwXnskzjks5sYfcugaJpZM4OjGET.

I am currently not planning to build an extract task for the below reasons:
-CRM Solution customisations are considered as part of source
-It is not recommended to check-in source as part of a build. Especially if you have a CI build.
-Ideally the pack should be run by developer upon completion of work with full control over what gets check-in and how conflicts are managed.


Vitest does not work when running from any CLI (Cannot find module @rollup)

Describe the bug
We are using Vitest in our project as a npm script.
When running from Visual Studio Code, the tests run correctly.
However, when we are trying to run the npm command that executes Vitest from a CLI outside of Visual Studio Code (for example, cmd or in a Jenkins pipeline), we get the following error:
Error: Cannot find module @rollup/rollup-win32-x64-msvc. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try npm i again after removing both package-lock.json and node_modules directory.
Reproduction
In VS Code (works):

Open a new terminal
Run command: npm run test (which runs vitest --run --no-isolate --no-file-parallelism)
Vitest works

In any other CLI (doesn't work):

Open CMD in the same directory as in VS Code
Run command: npm run test
Gives the error specified above (cannot find module @rollup)

System Info
Any

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I'm also suffering the same issue, in Gitlab pipeline on image node:20.14.0.
⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯
Error: Cannot find module @rollup/rollup-linux-x64-gnu. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
    at requireWithFriendlyError (/builds/my-super-cool/app/node_modules/rollup/dist/native.js:59:9)
    at Object.<anonymous> (/builds/my-super-cool/app/node_modules/rollup/dist/native.js:68:76)
    ... 3 lines matching cause stack trace ...
    at Module._load (node:internal/modules/cjs/loader:1024:12)
    at cjsLoader (node:internal/modules/esm/translators:348:17)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:297:7)
    at ModuleJob.run (node:internal/modules/esm/module_job:222:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:316:24) {
  [cause]: Error: Cannot find module '@rollup/rollup-linux-x64-gnu'
  Require stack:
  - /builds/my-super-cool/app/node_modules/rollup/dist/native.js
      at Module._resolveFilename (node:internal/modules/cjs/loader:1145:15)
      at Module._load (node:internal/modules/cjs/loader:986:27)
      at Module.require (node:internal/modules/cjs/loader:1233:19)
      at require (node:internal/modules/helpers:179:18)
      at requireWithFriendlyError (/builds/my-super-cool/app/node_modules/rollup/dist/native.js:41:10)
      at Object.<anonymous> (/builds/my-super-cool/app/node_modules/rollup/dist/native.js:68:76)
      at Module._compile (node:internal/modules/cjs/loader:1358:14)
      at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
      at Module.load (node:internal/modules/cjs/loader:1208:32)
      at Module._load (node:internal/modules/cjs/loader:1024:12) {
    code: 'MODULE_NOT_FOUND',
    requireStack: [
      '/builds/my-super-cool/app/node_modules/rollup/dist/native.js'
    ]
  }
}

Solved my issue by adding
`"optionalDependencies": {
    "@rollup/rollup-linux-x64-gnu": "^4.18.0"
  },


Memory effect in different queries

I observed memory effect while doing something like this:
$users = Lazer::table('users');

$limited = $users->limit(1)->findAll(); // will output limited results
$ordered = $users->orderBy('id', 'DESC')->findAll(); // will output ordered AND limited results

Solved


Nested model field id goes wrong

when I edit a model with nested models, the nested model's id in nested form value is a array consist the model id and the nested model id not an id number, like this
<input id="order_order_games_attributes_0_id" name="order[order_games_attributes][0][id]" type="hidden" value="[38689, 88]">

and when submit the form ,I get following error:
Couldn't find OrderGame with ID=[38689, 88] for Orders::StoreOrder with ID=38689

Here is my model information:
Order:
    has_many :order_games, :inverse_of => :order
    attr_accessible :id, :state, :games_count, :account_id, :subtotal, :order_games_attributes
    accepts_nested_attributes_for :order_games, :allow_destroy => true
    delegate :email, to: :account
    rails_admin do
        list do
            field :id
            field :account do
                searchable :email
                visible false
            end
            field :email
            field :state
            field :payment_method
            field :subtotal
            field :created_at
        end
    end

OrderGame:
    belongs_to :order, counter_cache: "games_count", :inverse_of => :order_games
    attr_accessible :id, :order_id, :account_id, :game_id, :price, :real_price

I guess this is caused by something you have in the model.
Pasting full model code might help.


jparera's initial implementation

Check List:

[X] Tests pass (./test.sh <username> shows no differences between expected and actual outputs)
[X] All formatting changes by the build are committed
[X] Your launch script is named calculate_average_<username>.sh (make sure to match casing of your GH user name) and is executable
[X] Output matches that of calculate_average_baseline.sh

Execution time: 7s-14s
Execution time of reference implementation: 3min 50s
System specs: 4 core i5-7600k @ 3.8GHz, 32GB RAM

Hey, something seems off with the aggregation. If you do ./create_measurements3.sh<PHONE_NUMBER>, do you get the same output as with the baseline (or any of the current leaders for a faster comparison)? I'm seeing differences there.

In addition to the rounding problem, the previous code could generate errors and was extremely slow when processing file measurements3.txt. The patch should fix all of this. The new code has been tested with measurements.txt, measurements2.txt, and measurements3.txt.

I was not satisfied with the code that solves the problem in the output, as it seems to indicate a deeper rounding error problem. So I have delved deeper into its cause.
Let's take the following temperature logs as input:
Zürich;18.6
Zürich;10.8
Zürich;11.3
Zurich;-13.6
Zurich;10.5
Zurich;19.7

If we do the sum of these 6 records the total is 57.3 which gives an average value of 9.55. If we round to get a value with a single decimal digit, resolving ties to positive infinity as the Math.round() function does, we get 9.6.
From the Javadoc of Math.round():

Returns the closest length to the argument, with ties rounding to positive infinity.

I would expect as output:
{Zürich=-13.6/9.6/19.7}

But the reference code generates:
{Zürich=-13.6/9.5/19.7}

Surely in this case, the average value was such that there was no tie to resolve. The average value that I get in my new code is 9.549999999999999, which would be rounded to 9.5 as there is no tie.

Hey, yeah, I think you are right and there's still something off with the rounding behavior of the baseline. I shouldn't have relied on double math 🤷 . FWIW, this specific situation doesn't show up in any of the tests or evaluation files, which is why it hasn't shown up so far. In that light, your implementation looks correct.

00:08.166, nice.


create schema for characters

table: character
columns: id, gameid, race, class, name, strength, dexterity, constitution, intelligence, wisdom, charisma, weapons

table: character
columns: id, gameid, race, class, name, strength, dexterity, constitution, intelligence, wisdom, charisma, weapons

This issue is complete!

This issue is complete!


Cannot find protocol declaration for 'PFVoid'

I'm trying to include the iOS SDK in my React Native app for push notifications.  I installed using CocoaPods and I get this error when trying to build:

The line above states that the code is used for testing.  If I comment it out, it builds just fine.
Any help would be appreciated.  Thanks.

Me to

Looks like this was introduced in v1.8.5.  Rolling back to v1.8.4 fixes it.

+1

:+1:

Any chance you guys are using non Xcode 7, but 6.4?
should not be a problem on Xcode 7, since we have Travis running on every commit.

Turns out I'm on 6.4.  I'll upgrade and see if that fixes the issue.

We're on Xcode 6.4, but upgrading to 7 is not a good option at this stage because we're close to launch and don't have much time to migrate all our code base to Swift 2.0...
1.8.5 is therefore not backwards compatible with 1.8.4, so consider revising the tag, as it breaks the semantic versioning that pods are supposed to adhere to.

@arielelkin @jacob-israel-turner @DmitryPashinskiy @kincade71
The fix was landed I updated the tag on the releases page, please update your Pods once again.

i still have this issue. Xcode 6.4, Parse 1.8.5

@andreykorolenko how are you including Parse in your Podfile? Does the issue go away for you if you modify your Podfile to include Parse like this:
pod 'Parse' , :head


larger cover art picture

How can I get a larger cover art picture?
I am using kitty and have played around with cover_img_scale and color_img_length etc. The image size increases but it cover the text of the playback window. Is there a way to move the text of the playback window to the right?

Have you tried color_img_width? An image's size can be tweaked with color_img_length and color_img_width.  cover_img_scale is only needed for engine that doesn't render the image nicely inside a pre-allocated rectangle like sixel.


How to validate the response that uses format: date-time?

I'm trying to understand the documentation but it doens't give too much information about this specific piece, so, what I'm doing:
const openapi = await Enforcer('./path/to/openapi.yml')

 const [ req ] = openapi.request({
   method: 'GET',
   path: '/tasks/1',
 })

 const responseData = axiosClient.execute();
 const [ res, error ] = req.response(200, responseData, ..)

I'm getting something like startDate: expected a valid date object, because responseData is returning:
{
   startDate: "2023-07-24T14:57:59.041Z"
}

and in my schema definition, I have this one as
   startDate:
      type: string
      format: date-time

but I don't know how to "deserialize" the responseData to have it properly validated in the req.response method. Is it expected?

Hello @irobson. Thanks for the the question.
Correct me if I'm misunderstanding the question, but it sounds like the const responseData = axiosClient.execute(); is returning an object that has the startDate field set to a string value. The req.response function is looking to convert a date into a string, so what is happening here is that it's receiving that startDate field and complaining that it isn't a Date object.
I think the easiest solution in this case would be to convert that property to a date prior to calling the req.response function. In your case that can be done using responseData.startDate = new Date(responseData.startDate).
I hope that helps. Let me know either way.

@Gi60s it will be a bit costly because I created a framework to call a lot of endpoints, can't handle that specifically for one or another, I thought that could be a way to do that thorugh the enforcer or deserialize the whole object. Thanks for your answer anyway.

Another possible solution is to use a schema hook. These can intercept and alter behavior for serialization/deserialization and validation. You could set up a hook that checks if a string looks like a date-time string and the schema has a format of date-time that it should assume the date is valid and skip validation.
Here is a regular expression you could use to quickly validate that the format of the string is a date-time format: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(?:\.\d+)?(?:Z|[+-]\d{2}:?\d{2})$


Unable to create nested contract router with loosing path narrowing

this works
const claims = c.router({
  getClaimsForApproval: {
    method: 'GET',
    path: `/partner/:partnerId/claims`,
    responses: { 200: c.response<{ id: string }[]>() },
    query: z.object({
      take: z.number().optional(),
      skip: z.number().optional(),
    }),
  }
});

export const claimServicePartnerApi = c.router({
  claims,
});

this doesn't work "path" becomes string
export const claimServicePartnerApi = c.router({
  claim: {
    getClaimsForApproval: {
      method: 'GET',
      path: `/partner/:partnerId/claims`,
      responses: { 200: c.response<{ id: string }[]>() },
      query: z.object({
        take: z.number().optional(),
        skip: z.number().optional(),
      }),
    }
 }
});

I think it's due to how I'm naïvely applying the Narrow helper, it probably should recursively go though the object...

Are there any updates here ?
Got the same issue when using ts-rest with nestjs.

TS2339: Property 'params' does not exist on type 'AppRouteShape{ getPost: { method: "GET"; path: "/posts/:id"; responses: { 200: ZodNullable { id: ZodString; }, "strip", ZodTypeAny, { id: string; }, { id: string; }>>; }; summary: "Get a post by id"; }; }>'
export const c = initContract();

const PostSchema = z.object({
  id: z.string(),
});

const postContract = c.router({
  getPost: {
    method: 'GET',
    path: `/posts/:id`,
    responses: {
      200: PostSchema.nullable(),
    },
    summary: 'Get a post by id',
  },
});

const contract = c.router({
  post: postContract
});

export {contract}

Maybe going to migrate to TS's 4.9 Satisfies for the 4.0 launch 🤔 Should resolve this, I want to avoid super heavy recursive TS generics as much as possible


Added DateTimeGenerators and LocalDateTimeGenerators.

@chrissalij @kylemessner

Generators for joda-time classes
Minor cleanup

LGTM

LGTM


Bounds can not always be calculated

Follow up to https://github.com/Toblerity/Fiona/pull/866 regarding OGR_L_GetExtent after writing of features.
Currently, there are two issues:

Calculation of extents can fail
Correct calculation of extents after writing a record is driver dependant: https://github.com/OSGeo/gdal/issues/2269

Regarding 1:

This PR disables the computations of bounds after records are written. They are lazy evaluated.
When a bound cannot be calculated, a DriverError is raised. This leads to failed tests.

Regarding 2:

We probably should detect cases when the calculation of bounds is not possible. ~Unfortunately, it seems as GDAL does not raise an error in this case. We could blacklist drivers.~

It looks as if when OGR_L_GetExtent returns a failure reliably detects when the extent cannot be computed, except for the Mapinfo driver. But for this driver, its special behavior regarding extents is documented: https://gdal.org/drivers/vector/mitab.html


vcpkg install lua & vcpkg install luajit conflictted.

after vcpkg install luajit, exec vcpkg install lua will generate the following error:
 D:\vcpkg> .\vcpkg.exe install lua:x86-windows-static
The following packages will be built and installed:
    lua:x86-windows-static
Building package lua:x86-windows-static...
-- CURRENT_INSTALLED_DIR=D:/vcpkg/installed/x86-windows-static
-- DOWNLOADS=D:/vcpkg/downloads
-- CURRENT_PACKAGES_DIR=D:/vcpkg/packages/lua_x86-windows-static
-- CURRENT_BUILDTREES_DIR=D:/vcpkg/buildtrees/lua
-- CURRENT_PORT_DIR=D:/vcpkg/ports/lua/.
-- Using cached D:/vcpkg/downloads/lua-5.3.4.tar.gz
-- Testing integrity of cached file...
-- Testing integrity of cached file...
The following files are already installed in D:/vcpkg/installed/x86-windows-static and are in conflict with lua:x86-windows-static

    include/lauxlib.h
    include/lua.h
    include/lua.hpp
    include/luaconf.h
    include/lualib.h

PS D:\vcpkg> .\vcpkg.exe version
Vcpkg package management program version 0.0.82-7fd5f3fe7c5589045a1e656a6289e56a20445be3

See LICENSE.txt for license information.

Unfortunately, this is the desired behavior as I understand it -- luajit and lua both provide the same headers (and perhaps even the same functions), so you can't use them both from the same application.

maybe you can put their header files in separate directories, eg: luajit -> include/luajit/xxx.h, lua -> include/lua/xxx.h.

@feicong The problem with that is that any library that depends on these headers need to have its #include directives modified.


cache rules locally to prevent additional hits into redis

We need to implement a caching layer in our application to store the rate limiting rules locally, reducing the number of frequent lookups to Redis. This approach will enhance performance, especially since the rules typically do not change often.
Requirements:

Create a data structure (e.g., a hash map) to store rate limiting rules in memory.
Implement a mechanism to refresh the rules from Redis upon user request.

Completed via https://github.com/x-sushant-x/Rate-Shield/commit/b44198549e0d4393eb6d34ff8c960882fe9d9212


timing freeze in 1.5

I notice a bug when timing tests. It seems specific to FFTW, so I report it here. If I do using Pkg; @time Pkg.test("FFTW") then the first run works fine.
Second time, freezes. Doesn't seem an issue for other packages, or on 1.4, or for testing without @time.
julia> versioninfo()
Julia Version 1.5.0-beta1.0
Commit 6443f6c95a (2020-05-28 17:42 UTC)
Platform Info:
  OS: macOS (x86_64-apple-darwin18.7.0)
  CPU: Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-9.0.1 (ORCJIT, skylake)
Environment:
  JULIA_NUM_THREADS = 4

Does it happen also when running the tests with a single Julia thread?  I'm also experiencing some deadlocks with the latest stable version.  Can you try again with the master version, which includes #151?

thanks for this, fixed on master

Ok, I'm closing this issue.  The deadlock is probably the same as #141, but setting the number of FFTW threads to 1 as in #151 should circumvent it


[AutoPR datamigration/resource-manager] add clientData properties to data migration tasks

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/4462

(message created by the CI based on PR content)


v2 Project: Motivation and path.

v2 Roadmap
The problem
Currently, the code is in spaghetti form, with clear inefficiencies regarding the use of HttpService and a dangerously soft line between fetching data from Trello and sending data to Trello.
Also, there are inconsistencies in argument checking that we need to fix.
In the end, the refactoring that would be required would be too much for a remake to be a valid option
Fundamental principles of v2

Git-like approach to the problem that sits in three basic operations:

Fetch data from Trello;

Make changes locally;

Push data to Trello.

A caching system in order to support larger-scale games;

Gracious error handling for errors that might be out of user control (404's, 429's, 500's);

Proper error messages that are easy to understand (I recommend to see this article).

Nice-to-haves:

Compatibility with Rojo;
For Roblox-TS users: An NPM package will be developed in parallel by me;
We will begin also shipping v2 modules in the Roblox Website so that you don't have to snoop in the releases page.
ADDED 29TH JULY: Module will be documented with Documentation Reader (by @ProbableAI) styling.

Versioning:
Until a version is stable, we will name dev releases of v2 2.0.0-dev.X

ADDED 29TH JULY: Module will be documented with Documentation Reader (by @ProbableAI) styling.

This was my first OOP project ever, so it is messy as heck.
v2 won't be rushed, like v1 was.

First public preview: https://github.com/HypheX/roblox-trello/releases/tag/2.0.0-dev.6
Feel free to comment on my API design choices.

Current Status
Ending 2019, while there wasn't too much time to progress on the development, there are some stuff that are already done, in particular, the constructors for our entities:

Client (renamed from Entity)
Board
List
Label

(Card couldn't make it before the new decade, sorry 😢)
Commit was renamed to Push, and I also implemented a Pull method, etc.
More info will be given when the card constructor is done and everything is properly tested.

finally they started to work on it again after a huge break(months)

Nvm it was updated 1 months ago they started to get a huge break again

I bet we will see trello api v2 in 2021

Soon:tm:
I'm currently in exam season + my laptop is going to be sent for repair so I don't have much to work with at the moment.


Add button "Complete return"

I think it would be useful to have a button with which a single click can return an item, maybe at the top of the RentalPopup? Would do the following things:

Set status on website to available
Set returned_on to today
set Pfand to full amount
Either prompt for kürzel or use recent one

That's a good idea. Maybe instead of a new Button in the popup we could also open a menu when right clicking a row for fast actions?

That's a good idea. Maybe instead of a new Button in the popup we could also open a menu when right clicking a row for fast actions?

we discussed that this should be in form of buttons, not right-click, as the second would be difficult to implement on a mobile phone, and less verbose/visible

implemented!


"yppasswd -p" is not working from a login node

After making sure yppasswdd is running on the install node - changing from a good password (upper and lowercase and a number and 8 chars) does not work. With a poor password set with "passwd testuser" on install node strace said that the password was not strong enough.
The error: crypt() call failed
Strace:
ioctl(3, SNDCTL_TMR_CONTINUE or SNDRV_TIMER_IOCTL_GPARAMS or TCSETSF, {B38400 opost isig icanon echo ...}) = 0
close(3)                                = 0
munmap(0x2b1c98af5000, 4096)            = 0
write(2, "crypt() call failed.\n", 21crypt() call failed.
)  = 21

Setting MERGE_PASSWD=True in /var/yp/Makefile the "yppasswd -p" works.
Unfortunately then the password hashes are made available to the clients.

Fix is to add "nis" to the password sufficient phase in system-auth and password-auth in /etc/pam.d

Fixed since https://github.com/CSC-IT-Center-for-Science/fgci-ansible/commit/e6a1a830de0b36c1d89e0a3d0668c17a57c4ef25


Use one space after emoji

Just a minor cosmetic tweak, there should be only one space after an emoji for consistency.

Thus won't render correctly, no? I added those intentionally...

Really? Let me generate the stubs, I forgot to do that anyway...

These emojis / messages don't appear in the stubs but in your terminal!!
There are more emojis where I added 2 spaces

These emojis / messages don't appear in the stubs but in your terminal!!

Yes, I realized that now 😄!
Only 🪣 rendered incorrectly, so I reverted that one.

Thank you!


tab group is not persisted

I am trying to use a tab group to have select at least 1 validation on my checkboxes. envelope-request.json attachment has the payload i use to create the envelope with checkbox tabs. the docusign API accepts my request but drops the checkbox tab group unless i specify documentId and pageNumber for the tab group (see tabs-response.json in the attachments). however i want the tab to be defined for all documents and all pages and not specifying document ID & page number works for all other tabs.
how can i make tab group work without having to specify documentId & pageNumber?
envelope-request.json
tabs-response.json

Hello, @furkan-bunch
Thank you for reaching out to DocuSign Support. My name is Guilherme. I'm a support engineer, member of the DEV/API team at DocuSign and I'll be working towards answering your questions today.
It is not possible to use "tabsGroups" without documentId and pageNumber.
Another user reported the same behavior, and we were informed by engineering those are required parameters in order to use "tabsGroups" along with its features.
Kind regards,
Guilherme Flores
Developer Support Engineer
Working hours: (8am-5pm) Brazilian Standard Time (São Paulo)

thanks for the answer @GuilhermeFloresDocuSign! are there any plans to support it in the future?
small feedback: Docusign API silently removing the tab is not the best behaviour, i would expect a bad request response if a tab is does not have a required field set.

Hi @furkan-bunch . There are no plans at the moment, but we can raise an improvement request to the engineering team. About the bad request, we do understand your point.
We noticed that if you don't add "documentId" and "pageNumber", the request is accepted, even though the tab rules won't be applied, however, if you add only "documentId", there will be an exception saying that "pageNumber" is a required parameter.
I'll report that behavior and see if they can improve exceptions messages and update our documentations.


querier: Discover and use topology for fun and profit

Is your proposal related to a problem?
I very much like the idea that a client can decide to sacrifice correctness to gain availability and that the query component is stateless. Unfortunately the current implementation provides neither correctness nor availability.
A brief summary of problems I noticed when exploring thanos.
Threats to correctness:

A storegw will be forgotten with a single failing Info query and then partial_response=0 succeeds.

The store-strict option assumes a store has no labels and covers no time by default (#3057). Restarting a querier while a store has issues (one of the store's QoD because of bad chunks) will result in partial_response=0 succeeding while it is not correct.

Stale stores (e.g. failing to synchronize with the bucket for a long time, longer than the overlap) leading to gaps. Today the store will log SyncBlocks failures but not action on them (send a warning, go unhealthy, expose a counter and gauge for last success).

The correctness issues make using the thanos query frontend slightly more dangerous (e.g. with large TTLs of cached results).

Threats to availability:

A single slow store will make partial_response=1 fail. It's partially mitigated with the --store.reply-timeout but that brings us to the next item.

Per query timeout smaller than --store.reply-timeout will lead to query timeouts. The store/proxy.go will wait for all streams to finish or timeout and this might be after the actual query has timed out. Let's assume the network/bucket has some form of issue then I am happy to get any (cached) result over no data at all.

Imagine we have a simple Prometheus HA setup (N+2 replicas, multiple storegw covering the timeline) but a single store/sidecar/prometheus has issues (restart, crash, IAM misconfigured) then thanos will either fail (partial_response=0) or warn prominently (partial_response=1) about the query. This seems to defeat the purpose of the HA setup that should be able to tolerate single instance failures.

(Write your answer here.)
Describe the solution you'd like
I would like to reach the point where partial_response=0 are (more) correct but can tolerate a single machine failure (because we have N+2 instances running) and that partial_response=1 honors the query timeout and gives genuine partial responses (e.g. only the cached ones).
Taking the topology into account in proxy/store.go could also be a latency (or load) improvement.

(Describe your proposed solution here.)
Describe alternatives you've considered
I have looked at cortex metric's query component but I am worried about frontend/backend having to both sync the object storage (and agree on the view) and the complexities coming from that (e.g. slow restart of a query frontend, needing to manage disk space)

(Write your answer here.)
Additional context

(Write your answer here.)

Thanks, @zecke for the detailed explanation.
The changes such as this require a proposal . We'd be happy to review proposed improvements. So help wanted and PRs are welcome.

If I understood this correctly then this could be solved by having something like promxy's server groups. But, for that we should have the ability to specify StoreAPI nodes via config files first IMHO


Bump log4j-core from 2.17.0 to 2.17.1 in /log4j2-ecs-layout

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2021-12-29T23:07:19.844+0000

Duration: 7 min 19 sec

Commit: 44444843b27c22f029de87fb0f1da50d4ba481d2

Test stats :test_tube:

Test
Results

Failed
0

Passed
171

Skipped
0

Total
171

:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


sudo_cast should not depend on default construction of T

Most probably, we will drop the default constructibility requirement of std::regular for representation types. With that, our internal casting function sudo_cast should not depend on it as well.

Was no longer the case. However, the default constructibility was required in a few other places. Now, it is no longer needed.


feat(plugin-blog): add plugin-blog

@meteorlxy The hot reload feature is not working as expected, need some help here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 48.166%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
545

Relevant Lines:
986

💛  - Coveralls


VeryPacked

This change is

#782  👈
dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Alon-Ti and the rest of your teammates on  Graphite

Codecov Report
Attention: Patch coverage is 54.90196% with 161 lines in your changes missing coverage. Please review.

Project coverage is 91.90%. Comparing base (14e41f9) to head (aacf3f6).

Files
Patch %
Lines

crates/prover/src/core/backend/simd/column.rs
20.14%
111 Missing :warning:

...es/prover/src/core/backend/simd/very_packed_m31.rs
75.00%
50 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##              dev     #782      +/-   ##
==========================================
- Coverage   93.06%   91.90%   -1.17%
==========================================
  Files          89       90       +1
  Lines       11992    12335     +343
  Branches    11992    12335     +343
==========================================
+ Hits        11160    11336     +176
- Misses        727      894     +167
  Partials      105      105

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