This fixes the bug that erroneously reported a deployment as failed

Bug was that the "TasksStarting" state was treated as final

Codecov Report

Merging #342 into master will increase coverage by 0.05%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #342      +/-   ##
==========================================
+ Coverage    61.6%   61.66%   +0.05%
==========================================
  Files         162      162
  Lines        8738     8741       +3
==========================================
+ Hits         5383     5390       +7
+ Misses       2914     2912       -2
+ Partials      441      439       -2

Impacted Files
Coverage Δ

lib/status_poller.go
83.01% <100%> (+0.24%)
:white_check_mark:

ext/docker/image_mapping.go
73.51% <0%> (+0.91%)
:white_check_mark:

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 b690dab...feccd5d. Read the comment docs.


Update exceptions bounds >= 0.8 && < 0.11

@sestrella LGTM!

@sestrella It failed in the last build. Would you mind taking a look?

@sestrella Seem to be ok now. I'm going to upload the package to hackage.

@sestrella Thanks!!!


How do I close the debugger

How can I close the debugger when debugging a cell?

@AllanLRH You need to click on the resume toolbar menu (the one in orange background). You may need to do it multiple times if there are other breakpoints set. You'll know that the debugger is closed when the source editor is gone and the kernel busy indicator (on the top right) is idle.
Note: we're working on a feature to make it more apparent that the debugger is running so that users will not accidentally try to run another cell.
Thanks


Add wavelength range checks to utility functions

As per title. Return arrays of NaNs if the desired quantities cannot be computed due to the wavelength range covered by the input wavelength arrays.

[x] continuum.compute_d4000
[ ] continuum.compute_continuum_intensity
[ ] dqcut.compute_measured_HALPHA_amplitude_to_noise

Also, figure out which function is replacing NaNs in the stellar velocity map with zeros...

The above NaN issue was being caused by velocity.get_slices_in_velocity_range. I've fixed it by making a copy of v_map within the function.

New to do: figure out what fixing this bug has affected...

I ran sami_regression_test.py on the recom/default test DataFrames, which showed the following columns to be affected:

v_grad (component 1)
Beam smearing flag (component 1)
HALPHA A/N (measured)

These changed because:

In sami.py, v_map[0] (the narrow gas velocity component) was being passed to compute_continuum_intensity() (line 638).
In compute_continuum_intensity(), we called get_slices_in_velocity_range() on v_map[0], which was overwriting NaNs with zeros.
We then called compute_v_grad() on v_map, which was incorrectly computing v_grad (component 1) which relies on v_map[0] (and therefore affecting Beam smearing flag (component 1)), creating non-NaN entries where there should have been NaNs.
Next we called compute_measured_HALPHA_amplitude_to_noise() which uses v_map[0]. In this function as originally written, NaNs in v_map[0] should propagate to NaNs in HALPHA A/N (measured) because they are used to get wavelength values via get_wavelength_from_velocity() (which does NOT replace NaNs with zeros). However, because we had inadvertently replaced NaNs with zeros in v_map, we were basically adopting LOS velocities of 0 when calculating the wavelength range over which to evaluate the A/N, which is actually desired behaviour!!

This means that this bug only affected v_grad measurements (which have not been used in any science so far) and that the A/N measurements have "accidentally" been correct this whole time.
Fixes/TODOs:

[ ] In compute_measured_HALPHA_amplitude_to_noise(), create a copy of v_map and replace NaNs with zeros.

Merged into hector, will merge hector into dev when complete.


caqe: init at 4.0.2

Description of changes
Add the package.
Closes: #273874
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Hi @viraptor. Thanks for packaging this!
Minor comment: I think most other automated theorem provers are in [pkgs/applications/science/logic/](https://github.com/NixOS/nixpkgs/tree/master/pkgs/applications/science/logic).

The old structure is going away https://github.com/NixOS/nixpkgs/issues/258650
I'm still fighting with the linux build for this, but should be ready at some point... It's already usable on darwin.

The old structure is going away #258650
I'm still fighting with the linux build for this, but should be ready at some point... It's already usable on darwin.

How about just merging it for darwin?


{width: null} will not unset the width property

{width: null} will not unset the width property, it works like "0".
If you set an element to Width 100% and later want to set it back to Width "auto", then unfortunately this is currently not possible.

Hi, width: null should not be used, but width:'auto' is supported.. check this code
`import React from 'react';
import {Pressable, StyleSheet, Text, View} from 'react-native';
import {AutoKillTweens, Elastic, gsap} from 'gsap-rn';
export const SimpleAnimation = () => {
const boxRef = React.createRef();
const tweens = {};
const animate = () => {
tweens.ani1 = gsap.timeline();
tweens.ani1.set(boxRef.current, {style: {width: '10%'}});
tweens.ani1.to(boxRef.current, { duration: 1, style: {width: '80%'}, ease: Elastic.easeInOut,});
tweens.ani1.set(boxRef.current, {style: {width: 'auto'}});
};
return (
<>

<Pressable onPress={animate} style={[style.button, {marginTop: 20}]}>
Click

</>
);
};
export const style = StyleSheet.create({
box: {
padding: 20,
width: '50%',
height: 100,
justifyContent: 'center',
alignItems: 'center',
backgroundColor: 'red',
},
button: {
padding: 20,
justifyContent: 'center',
alignItems: 'center',
width: 'auto',
backgroundColor: '#dddddd',
},
});
`

OK,

with "10%" > "auto" it works,
with 100 > "auto" it dos not work,

JSON value '10.0266' of type NSString cannot be converted to a YGValue. Did you forget the % or pt suffix?

Yes, in reactNative you can’t mix % with Numbers, if you will do an animation with % just use % value, or if your animation will be Number  just use number, remember too that you need to set the initial values (from) values, due is not easy retrieve that information automatically…
You can use gsap.fromTo or gsap.set before start your animation…

I have found a way to animate the height without having to give a fixed value. This has the advantage that the animation does not jump!
`
const [bodyHeight, setBodyHeight] = useState(0);
useLayoutEffect(() => {
    checkBodyHeight();
}, []);

const checkBodyHeight = () => {
    setTimeout(() => {
        animationViewRef.current?.measure((x, y, width, height, pageX, pageY) => {
            if (height > 0) {
                setBodyHeight(height);
            }
        })
    }, 0)
}

const playOpenAnimation = () => {
    animationTimeLine.set(animationViewRef.current, {
        style: {
            height: 0,
        },
    });

    animationTimeLine.to(animationViewRef.current, {
        style: {
            height: bodyHeight,
            opacity: 1
        },
        duration: 1,
        ease: Power4.easeOut,
    })

    animationTimeLine.set(animationViewRef.current, {
        style: {
            height: 'auto'
        },
        onComplete: () => {
            checkBodyHeight();
        }
    });
}

const playCloseAnimation = () => {
    animationTimeLine.set(animationViewRef.current, {
        style: {
            height: bodyHeight,
        },
    });

    animationTimeLine.to(animationViewRef.current, {
        style: {
            height: 0,
            opacity: 0
        },
        duration: 1,
        ease: Power4.easeOut,
    })
}

`


Warn the user about not enough available free space

Syncing takes a significant amount of space. We are working towards fixing that. Until then, we want to let users know that we don't consider there's enough space to continue syncing.
The goal is to not let the wallet paint itself to a corner and be proactive towards detecting this denial-of-service situation where the wallet occupies space that can't be claimed back.
Scenario:
When the app goes to foreground it will attempt to sync. Before doing so, the wallet should check whether there's enough space to continue safely.
use case A: there's enough space. the wallet proceeds to start syncing.
use case B: theres is not enough space. The wallet should not proceed to sync.  Instead it should show a warning as the design below.

Preconditions:

this free space check happens only after the users has created a new wallet and backed up the keys successfully or restored from backup.

implementation details:

the amount of space required should be easily modifiable on code.
create mocks to trigger this scenario
add snapshot test with the corresponding screenshot.
implement light and dark mode.

I implemented what is requested in this issue. I am just not sure if this logic will work in all cases. It will probably in case of full sync. This is just some food for thoughts how to improve this check.
But for example in this case it probably won't work:

User has 2 GB of free space on device and user does full sync on Monday.
On Tuesday user has only 500 MB of free space and runs the app. Now app says there isn't enough space. But user just needs to sync blocks mined only in last 24 hours. And 500 MB is probably enough for that. So in this case app does false positive detection of not enough free disk space.

This is a really good insight @Chlup.
@ccjernigan shall the wallet estimate by linearly multiplying a size per block  by the delta between birthday and latest height?

How can we keep this really simple?
The amount of disk usage will decrease in a few weeks when we move to storing blocks as files and doing download/scan in parallel.  That reduces the disk space needed, thus making the size difference between states that @Chlup points out much smaller.  I think this sort of solves itself at that time.
I think we can document this limitation and circle back once the SDK changes are made.


I have a question about JSON code in lists

My apologies if this isn't the right place to post this question. If I should redirect it, please let me know where it should be. Thanks.
I work in a smaller organization and for whatever reason PowerApps has been disabled. I am trying to create a ticket tracking system that allows users to submit data (MS Form?), automatically take that data and put it into a MS List ticket tracking system, and use a MS Teams channel to collaborate with the user on the issue. Is this even possible without PowerApps, and if so, where do I begin?
Again, not specific to MS Lists formatting - just don't know where else to ask this question. Any help on where I can begin (without PowerApps) would be greatly appreciated. Thank you!

Hi @UndefinedUser101 !
As you mentioned, this question may not seem to be directly related to List Formatting. Therefore, it may not be appropriate to discuss it in this repository.
Hmmm... How about asking your question in the Microsoft Tech Community? I believe this site allows questions and discussions about SharePoint in general. (My apologies if my perception is incorrect.)
https://techcommunity.microsoft.com/t5/sharepoint/bd-p/SharePoint_General

I'll give that a try. Thank you!


Removed field Property from ResourceOperation

Implements #1087
Signed-off-by: Joan Duran<EMAIL_ADDRESS>

LGTM. If you're can, give this a quick rebase and I'll pull it in.

Rebased


Exposing zero-copy serialization threshold through configuration option

this adds a new configuration option hpx.parcel.zero_copy_serialization_threshold
flyby: rename hpx.max_backgroud_threads to hpx.parcel.max_background_threads,
expose parcelport specific hpx.parcel.<pptype>.max_background_threads and hpx.parcel.<pptype>.zero_copy_serialization_threshold
added missing documentation for both

@diehlpk please note that this changes the name for the configuration option you've been using before (as discussed)

Thanks for that!


update boolean attributes link

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
https://github.com/yiisoft/yii2/issues/19215

👍🏻


Support mods that aren't located in the Steam Workshop mods folder structure

We currently hard-code the mod path, which isn't strictly necessary. You can get by perfectly well by creating a folder in the Conan Exiles game directory for your mods and using relative paths in modlist.txt, completely bypassing the Steam Workshop folder structure.
We should allow config JSON authors to indicate a custom mods base folder rather than just going straight to the Steam Workshop folder.

Done and implemented


[FEATURE] Match Statement

Describe Your Feature
Add a match statement, which matches a given value against different possible values using the match trait.
Provide a Code Snippet Using Your Feature
fn test() {
    match 3 {
        1 => return false;
        2 => return false;
        3..=10 => return true;
    }
}

Prerequisites
The match trait: #9
Additional Information
Look at how for-loops call the Iter trait from inside them to figure out how to implement this.

I will try to do this one


Auto logging on teardown

The existing tests framework in eventing has the nice feature
of logging resources that are tracked during a test and that's
helpful for debugging test issues.
This PR is adding support for the same feature, by automatically
prepending logging steps to the teardown phase of every feature.
Signed-off-by: Pierangelo Di Pilato<EMAIL_ADDRESS>/hold this PR is based on https://github.com/knative-sandbox/reconciler-test/pull/288

/hold cancel


[DOCFIX] Fix example for the complete function

PR Description
Please describe the changes proposed in the pull request:

Fixed an example block that was not properly formatted.

**This PR has no pending issue.

Merging in!


Fixes Reanimated 2 detection

fixes #961
The issue is that Snack is using its own packaging magic and react-native-reanimated/lib/reanimated2/core will always return undefined.

we will have a e2e test for it 100%


Clean up: stimulus

MINOR changes:

improved instructions
establish correct order within property

MAJOR changes:
none
SPECIAL ATTENTION:
none

Before merging this please merge #7


hyprland-activewindow: 1.0.1 -> 1.0.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/FieldOfClay/hyprland-activewindow/releases.
meta.description for hyprland-activewindow is: A multi-monitor-aware Hyprland workspace widget helper
meta.homepage for hyprland-activewindow is: https://github.com/FieldofClay/hyprland-activewindow
Updates performed

Rust version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.0.2 with grep in /nix/store/mv384rlh9r32g09nnzm3j26s37f8h2yg-hyprland-activewindow-1.0.2
found 1.0.2 in filename of file in /nix/store/mv384rlh9r32g09nnzm3j26s37f8h2yg-hyprland-activewindow-1.0.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

hyprland-activewindow

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mv384rlh9r32g09nnzm3j26s37f8h2yg-hyprland-activewindow-1.0.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A hyprland-activewindow https://github.com/r-ryantm/nixpkgs/archive/2676356c2accb7c2fc3f9bfa97c87bfefdd6c238.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2676356c2accb7c2fc3f9bfa97c87bfefdd6c238#hyprland-activewindow

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mv384rlh9r32g09nnzm3j26s37f8h2yg-hyprland-activewindow-1.0.2
ls -la /nix/store/mv384rlh9r32g09nnzm3j26s37f8h2yg-hyprland-activewindow-1.0.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

1 package built:

hyprland-activewindow

Maintainer pings
cc @kiike @donovanglover for testing.

@NixOS/nixpkgs-merge-bot merge

Awesome! Beat me to it! Thanks @donovanglover!


Keep objects' original system

Hello!
I have 2 systems: A and B.
Whatever is developed in A is transported to B.
But whatever is developed in B is not transported anywhere.
Currently, when I use abapGit to send things from A to B... all the objects are created as if they were originally developed in B.
This is dangerous because abapGit is not the norm to keep the systems in sync and so it is possible (I'd say probable) that someone will make changes in system B to objects originally transported from system A. These changes will never be sent to system A.
This is dangerous.
It would be great if abapGit could read the original system of an object and then force into the objects created in other systems.
This could be an option at repository level.
Thanks,
Nuno

Actually, losing the information of the original system is one of the main concerns people in my project have on adopting abapGit...

Suggestion:
Add a setting on repository level where the source system can be defined, and whenever doing a pull then make sure the source system is set for the updated objects.

this will also warn developers if they are trying to mess with something they are not supposed to, ie. choice to have the vanilla open source program implemented

What do you mean? Not even 7 years! ;-)
Thanks <3

You can always sponsor me to speed things up 🤭


Multiple new records at the same time

If you create a new record, fill it in, then click on creating another new record you lose all the data from the previous ones.  The only way you can do this is, is to save after each record, click Edit, click + again.  Or click the + the amount of records you require and fill all of them in and hit save.

hm interesting. I will fix it this week.

I detected this issue too. If you click to add more rows and didn't save it yet, you gonna lose your unsaved data.


Proposal: NFT drop round 2

Do the second round of distribution for qualified lobsters (based on the spreadsheet) who missed the initial one
By going through the discussions, there are a lot of motivated lobsters who want to be engaged but missed the initial drop due to various dumb reasons (were not online for a few days, were busy with other stuff etc)
IMO will widen the community in a good way and make it generally happier

it would be fair if the drop round 2 is for diamond hands (never sold a lob) - excluding treasury etc. as well, otherwise they just got diluted. I.e. adopting ve(3,3) spirit is better ;)


README.md: Fix paths after doc->docs move

Adjust doc paths in README.md after the doc->docs move in 3cd9b9a

Coverage remained the same at 34.194% when pulling 22901290ce3ca43babb903a666a8ce3503f7d183 on tklauser:patch-1 into 13b66d38f5d4280bdf7a3c5352b4369d8357de36 on slackhq:master.

Thanks for catching this!


Allow href in Links to be a string

Since Next allows href to be a string in Links, it would be nice to also offer this more compact syntax (e.g.: Allow users to write href="/" instead of href={{ pathname: '/' }}). We can still make this typed so that only the corresponding string literals are allowed.
If this sounds like a good idea, I can create the PR with the implementation :)

Hey @MariaSolOs I had this in an early version of nextjs-routes but the TypeScript error messages had poorer DX. Any typos in routes would present an error message using the first member of the routes union rather than the most similar member. This was several months ago so if the TS inference has improved in more recent versions or if you can find a way to express the type differently that helps TS yield a better error message (maybe a conditional type with the string and object variants instead of a single union?) I’m open to it. Also happy to support this via a config option if we can’t overcome the error messaging DX.

@tatethurston so changing href: RouteOrQuery; to href: Route["pathname"] | RouteOrQuery; results in this error message, which I think is clear enough. What do you think?

Yeah that error message seems clear enough. Is it roughly similar with a a bad RouteOrQuery object?

Hmmm no, in that case we have the error message that you described:

However, this seems to be the case with and without my type change.

Hmm even with a route closer to a valid defined route? I wonder if we regressed with the introduction of RouteOrQuery.

It seems like the error always shows the same route.
Given that this regression isn't caused by my proposed change, are you okay with me continuing with the implementation, or would you like to first fix this?
I'm okay either way :)

Yes continuing with the implementation sounds great, thanks

Implemented in #84 :)


adds broadcasting test cases

refs: #80, #90, #104, #105

Is the ((5,13,24,16), (5,1,24,1)) case really important in practice? If we decide implement only 1s on the start or end (which is simpler to implement without complicating the kernel), the test should already contain only these easy cases

Is the ((5,13,24,16), (5,1,24,1)) case really important in practice? If we decide implement only 1s on the start or end (which is simpler to implement without complicating the kernel), the test should already contain only these easy cases

Thanks for the review. No it’s probably not important in practice. I added a few cases that I thought would test for generality. If the consensus is that we don’t want/need general broadcasting on GPU, the test cases can be modified. If that decision is made, we will be fragmenting the cpu and GPU capabilities of the library.
Either way, this PR is designed to get make more broadcasting tests available. The content of the tests can and should be discussed, and modified, just like we are doing now — so thanks again for weighing in.

Please take a look at https://github.com/geohot/tinygrad/pull/108/ . With
it the important GPU test cases should be covered probably (I'm not sure
though).
On Thu, Nov 12, 2020 at 11:30 AM Ryan Neph<EMAIL_ADDRESS>wrote:

Is the ((5,13,24,16), (5,1,24,1)) case really important in practice? If we
decide implement only 1s on the start or end (which is simpler to implement
without complicating the kernel), the test should already contain only
these easy cases
Thanks for the review. No it’s probably not important in practice. I added
a few cases that I thought would test for generality. If the consensus is
that we don’t want/need general broadcasting on GPU, the test cases can be
modified. If that decision is made, we will be fragmenting the cpu and GPU
capabilities of the library.
Either way, this PR is designed to get make more broadcasting tests
available. The content of the tests can and should be discussed, and
modified, just like we are doing now — so thanks again for weighing in.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/geohot/tinygrad/pull/106#issuecomment-726021051, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AN5SWAFCTRISAVGDZU653FLSPPBMRANCNFSM4TS53ZKQ
.


cherry-pick the fix for PDB issue of cert-manager

Cherry-pick https://github.com/istio/istio/pull/14509 to release-1.2

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: morvencao
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [morvencao]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@morvencao: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
52ed32063bbe73e2fb539145fbb57de265d56f32
link
/test integ-mixer-k8s-presubmit-tests-release-1.2

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: linsun, morvencao
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [linsun,morvencao]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Return address at the bottom of stack should be 0

We have 0xdeadbeef as our final return address. The unwinder expects to see 0 here afaict.

%rbp should also be 0. Looks like it is not.


add a flag to test if webhook secrets are set.

Changes

:bug: Fixing an issue where we are not allowed to test github secrets in the if blocks of steps.

/kind bug
Fixes https://github.com/knative-sandbox/.github/issues/84

Tested here: https://github.com/n3wscott/eventing/runs/1657604011?check_suite_focus=true

Tested here: https://github.com/n3wscott/eventing/runs/1657604011?check_suite_focus=true

/lgtm
Thank you!

/lgtm
Thank you!


Simple test fails with expectBlock when adding second set of transactions

diff --git a/source/agora/test/Simple.d b/source/agora/test/Simple.d
index 8d88f8d7b..d77c01104 100644
--- a/source/agora/test/Simple.d
+++ b/source/agora/test/Simple.d
@@ -41,4 +41,8 @@ unittest
     auto txes = genesisSpendable().map!(txb => txb.sign()).array();
     txes.each!(tx => node_1.putTransaction(tx));
     network.expectBlock(Height(1));
+
+    txes = txes.map!(tx => TxBuilder(tx).sign(TxType.Payment)).array();
+    txes.each!(tx => node_1.putTransaction(tx));
+    network.expectBlock(Height(2));
 }

dtest=agora.test.simple dub test

This fails with exceptions about missing preimages. It seems that some overloads of expectBlock call waitForPreimages, while others do not.

Workaround:
network.expectBlock(Height(2), network.blocks[0].header);

Also, I would not be surprised if this is the cause of the CI failures. The existing call in master for network.expectBlock(Height(1)); can also fail based on timing.

I think network.expectBlock(Height(1)); never fails because an enrollment already has a commitment which is used for a distance of 0 which is for a height of 1 like this case.

You're right. Then it's only a problem with all the future heights.

I think only the function having the block header as a parameter should remain. Please use the workaround first. I will take this issue later and I will remove the unnecessary function.

In the meantime the simple test was change to use generateBlocks(Height), so it's fine now.


TestGrid dev dashboard in apps.wso2 is pointing to the wrong URL

Description:
TestGrid dev dashboard in apps.wso2 is pointing to the wrong URL (https://testgrid-live-dev.private.wso2.com/testgrid/dashboard/api/acs). This should be (https://testgrid-live-dev.private.wso2.com/testgrid/dashboard/)

This is done now.


New Release

Hey Everyone,
So I noticed that in commit: ddd0ee2 the model changed the name of session to session_key. I think this will break anyones install that had the tables built previous to this commit. I think that we should ship migrations with the upcoming release and provide documentation on how to run them. I think I have a little bit of time to try and put this together if people think it is worth the effort.
If we do not want to provide migrations, I think the name should be changed back to session to avoid having to edit the database by hand.

I fact you can just delete the old tables in database as it only contain temporary data and perform and ./manage.py syncdb.

Very true, maybe we should add a note somewhere? I don't think it would make sense in the readme as the models have only existed for a short period of time, so this change probably will not effect many people. Any thoughts?

It is already in the README :

Run ./manage.py syncdb to create Single Sign On and Proxy Granting Ticket tables. On update you  can just delete the django_cas_ng_sessionticket table and the django_cas_ng_proxygrantingticket
before calling ./manage.py syncdb

maybe should it be somewhere more visible like and UPDATE or CHANGELOG file ?

Ah I see. Maybe adding a CHANELOG file would be useful. I just see people that are not particularly technical updating to 3.4.2 running syncdb, then updating to 3.4.3 (or whatever it may be called), and then their application crashes and they don't know why.

There is changelog file to document changes for every release. https://github.com/mingchen/django-cas-ng/blob/master/docs/changelog.rst Could you some body update it for up coming release ?

OK I will have a pull request done today. nitmir, could you look at 36681601c3715574cbf22cf24054bb9abc629db9 to make sure I did not break the callback code for single sign out?

I think 3668160 is ok.


Manual promotion stays Pending in a Stage

Description
I have a Stage (~which has auto-promotion enabled~), where a Pending promo will not run. I started a manual promotion, but that promo remains in Pending.
Screenshots

Steps to Reproduce
Based on the logs, I think to reproduce this:

~have a Failed promotion for the existing Freight.~ See screenshot. In my case, the previous promotion was aborted.
Try to promote the same freight again
~I also believe that autopromotion may be a second requirement.~ I will try disabling auto-promotion to see if I'm correct.

EDIT: I disabled auto-promotion but it remains Pending, so auto-promotion is not a factor.
EDIT2: I also deleted the previously failed promotions but it still remains Pending
Version
v1.2.0-unstable-20241203

Logs
The following is the output when refreshing the stage with a Pending promotion:
time="2024-12-04T00:39:03Z" level=debug msg="reconciling Stage" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:39:03Z" level=debug msg="syncing Promotions" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:39:03Z" level=debug msg="current Freight needs to be verified before allowing new promotions to start" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:39:03Z" level=debug msg="assessing health" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:39:03Z" level=debug msg="Last promotion did not succeed: no health checks to perform" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:39:03Z" level=debug msg="verifying Stage Freight" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:39:03Z" level=debug msg="Stage has not passed health checks: skipping verification" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:39:03Z" level=debug msg="verifying Freight for Stage" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:39:03Z" level=debug msg="auto-promoting Freight" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:39:03Z" level=debug msg="found PromotionPolicy associated with Stage" autoPromotionEnabled=true controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:39:03Z" level=debug msg="Promotion already exists for Freight" controlFlow=false freight=072a46be6f4cb218ac3ed730a9bf502d76e46be2 namespace=guestbook origin=Warehouse/guestbook stage=test
time="2024-12-04T00:39:03Z" level=debug msg="done reconciling Stage" controlFlow=false namespace=guestbook stage=test```

I disabled auto-promote on the stage, but it did not help. Updated logs after disabling auto-promotion:
time="2024-12-04T00:52:06Z" level=debug msg="reconciling Stage" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:52:06Z" level=debug msg="syncing Promotions" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:52:06Z" level=debug msg="current Freight needs to be verified before allowing new promotions to start" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:52:06Z" level=debug msg="assessing health" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:52:06Z" level=debug msg="Last promotion did not succeed: no health checks to perform" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:52:06Z" level=debug msg="verifying Stage Freight" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:52:06Z" level=debug msg="Stage has not passed health checks: skipping verification" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:52:06Z" level=debug msg="verifying Freight for Stage" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:52:06Z" level=debug msg="auto-promoting Freight" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:52:06Z" level=debug msg="found no PromotionPolicy associated with Stage" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T00:52:06Z" level=debug msg="done reconciling Stage" controlFlow=false namespace=guestbook stage=test

Here is the Stage:
metadata:
  name: test
  namespace: guestbook
  uid: 652ac91b-5bc2-4377-aede-c119c63ba4a3
  resourceVersion: "47321597"
  generation: "10"
  creationTimestamp: 2024-01-31T20:58:23Z
  annotations:
    kargo.akuity.io/color: green
    kargo.akuity.io/refresh: 2024-12-04T00:52:06Z
  finalizers:
    - kargo.akuity.io/finalizer
spec:
  requestedFreight:
    - origin:
        kind: Warehouse
        name: guestbook
      sources:
        direct: true
  promotionTemplate:
    spec:
      steps:
        - uses: git-clone
          config:
            checkout:
              - branch: main
                path: ./src
            repoURL: https://github.com/example/guestbook-deploy.git
        - uses: kustomize-set-image
          as: update-image
          config:
            images:
              - image: example/guestbook
            path: ./src/env/test/aws/guestbook
        - uses: git-commit
          as: commit
          config:
            messageFromSteps:
              - update-image
            path: ./src
        - uses: git-push
          config:
            path: ./src
        - uses: argocd-update
          config:
            apps:
              - name: 04-test-aws.guestbook
                sources:
                  - desiredCommitFromStep: commit
                    repoURL: https://github.com/example/guestbook-deploy.git
status:
  phase: Failed
  freightHistory:
    - items:
        Warehouse/guestbook:
          name: 4f542faecd126b7455a48a1a563d9685bf6cfce7
          images:
            - repoURL: example/guestbook
              tag: 1.2.3-0.20241108164846-dac4683cb14b
              digest: sha256:9135a154681db547ed5aa8c066fcddcdc41dbd627a975d898003b8cda8daa7be
          origin:
            kind: Warehouse
            name: guestbook
      id: b54972c4759c39bbb70ea88277078348fdfffa6b
    - items:
        Warehouse/guestbook:
          name: 3b70770551f455e1e6785f9bd6ca7f8788bf20d8
          images:
            - repoURL: example/guestbook
              tag: 1.2.3-0.20241108081213-f6839f0132b8
              digest: sha256:301f73160bef898c858bfa6a63d128abde8aa8fe60cd2329b464d6812276156a
          origin:
            kind: Warehouse
            name: guestbook
      id: 5d0d57e0ae54ceb5f98146ce99f2fd98ee4e9ee9
    - items:
        Warehouse/guestbook:
          name: d50782a91dfd1303e9e03401363a05b8c179d42d
          images:
            - repoURL: example/guestbook
              tag: 1.2.3-0.20241108064929-a2563adc0fa9
              digest: sha256:6d86c70388aeb7beeadda9f943992c7da9d698ba6e73b1703e76e9fcce11556b
          origin:
            kind: Warehouse
            name: guestbook
      id: 4203c9532bf2aaf3454d9987ad45c7b12fb4159e
    - items:
        Warehouse/guestbook:
          name: b3704c0f145f4bc29206a7e4471c1c35e217c0dc
          images:
            - repoURL: example/guestbook
              tag: 1.2.3-0.20241108060100-2e66ff12e650
              digest: sha256:b1007321a856c03a6dc49840d46b3a517bc7465ef932160aeb60cdffa53e4db8
          origin:
            kind: Warehouse
            name: guestbook
      id: 0864d948b43e9090d989c5a3c4a3ad4a5683cfd1
    - items:
        Warehouse/guestbook:
          name: a2e363701d1992d310813c2732b3371bac9bccbe
          images:
            - repoURL: example/guestbook
              tag: 1.2.3-0.20241107192251-e1c081e94f8e
              digest: sha256:08a6d2588ba66c1c1be6dfb6be50caa52f545ab39dd062f7d4295d360b0e35f1
          origin:
            kind: Warehouse
            name: guestbook
      id: fea8c464d2d319f65ccadb005bac113ae02fd318
    - items:
        Warehouse/guestbook:
          name: 4bf8786072f8ea71ad230c92449401b55f404b76
          images:
            - repoURL: example/guestbook
              tag: 1.2.3-0.20241107180347-9fdbd0986a8d
              digest: sha256:080b306b65a66ce6faa3992079db7e111da21f2b5c70cf0bc16aca1e92e2bf77
          origin:
            kind: Warehouse
            name: guestbook
      id: 4719ff3099a3dfac537481c73f1a47082a2b5337
    - items:
        Warehouse/guestbook:
          name: 7f84a7efe9eb93820c6a7663fd88adbbb1166a3e
          images:
            - repoURL: example/guestbook
              tag: 1.2.3-0.20241107153607-db9652ce8524
              digest: sha256:dda0dad13e96dfd1a3082cb34eb69b68e534a9787528cf56e5eb332e1c383af6
          origin:
            kind: Warehouse
            name: guestbook
      id: 022dad6bea1110fb7365dd9985eda098b1d7a275
    - items:
        Warehouse/guestbook:
          name: 3923c754e083de3a58b2efedc4554e67d32b3e85
          images:
            - repoURL: example/guestbook
              tag: 1.2.3-0.20241107140545-342f7d838339
              digest: sha256:d83335855623b3b48fbc3bc448776886831bf65ee9feef0b6a8ed0ad176f4084
          origin:
            kind: Warehouse
            name: guestbook
      id: 1fdc8c893224f5d28842a80a6b0d83d0a09ce8e2
    - items:
        Warehouse/guestbook:
          name: 48bcd1501f6cbd0594bedad18a0ae40dbd891602
          images:
            - repoURL: example/guestbook
              tag: 1.2.3-0.20241107090702-ca30cdcbe7ae
              digest: sha256:c397759c7b5b32338a8a95752b0562797f85ec9faa2ff8c9d3d3a37956e740fb
          origin:
            kind: Warehouse
            name: guestbook
      id: 1320dc14bae5ad06975cb16741b06d4021d93416
    - items:
        Warehouse/guestbook:
          name: 452748c0953f1c2fda523931fc71d94ba7f4d1f4
          images:
            - repoURL: example/guestbook
              tag: 1.2.3-0.20241107000248-4c51b26ccced
              digest: sha256:26d3f7606a8a955d8916d86b6a29d6eabafb5fe7dce1c1416606284517fa45a7
          origin:
            kind: Warehouse
            name: guestbook
      id: f3df7736a8232559cfaf5cedbb0ab22c2d3cad7c
  observedGeneration: "10"
  lastPromotion:
    name: test.01jdmpk1c1zsfha65pnt4mmx9f.127829a
    status:
      phase: Aborted
      message: Promotion terminated by<EMAIL_ADDRESS>      finishedAt: 2024-11-26T20:14:11Z
      currentStep: "0"
      currentStepAttempt: "0"
    finishedAt: 2024-11-26T20:14:11Z
  lastHandledRefresh: 2024-12-04T00:52:06Z
  freightSummary: 4f542faecd126b7455a48a1a563d9685bf6cfce7
  conditions:
    - type: Ready
      status: "False"
      observedGeneration: "10"
      lastTransitionTime: 2024-11-26T19:49:14Z
      reason: LastPromotionAborted
      message: Promotion terminated by<EMAIL_ADDRESS>    - type: Healthy
      status: Unknown
      observedGeneration: "10"
      lastTransitionTime: 2024-11-26T19:49:14Z
      reason: LastPromotionAborted
      message: No health checks to perform for unsuccessful Promotion

I deleted the previously failed/aborted Promotions so that only the Pending one remains:

Then I refreshed the Stage, but the newest one still remains Pending. Logs of refresh:
time="2024-12-04T01:07:12Z" level=debug msg="reconciling Stage" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T01:07:12Z" level=debug msg="syncing Promotions" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T01:07:12Z" level=debug msg="current Freight needs to be verified before allowing new promotions to start" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T01:07:12Z" level=debug msg="assessing health" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T01:07:12Z" level=debug msg="Last promotion did not succeed: no health checks to perform" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T01:07:12Z" level=debug msg="verifying Stage Freight" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T01:07:12Z" level=debug msg="Stage has not passed health checks: skipping verification" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T01:07:12Z" level=debug msg="verifying Freight for Stage" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T01:07:12Z" level=debug msg="auto-promoting Freight" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T01:07:12Z" level=debug msg="found no PromotionPolicy associated with Stage" controlFlow=false namespace=guestbook stage=test
time="2024-12-04T01:07:12Z" level=debug msg="done reconciling Stage" controlFlow=false namespace=guestbook stage=test

I guess root cause is this message: current Freight needs to be verified before allowing new promotions to start

current Freight needs to be verified before allowing new promotions to start

Yes. That's by design since 1.0 because users were reporting new promotions not waiting for running verifications to complete.
A Stage needs to become healthy before verification starts. If there is no verification defined, then the Stage is implicitly verified the first time it reaches a healthy state following a promotion.
From the logs, it looks to me like the previous promotion failed, so no health check is being performed. It seems this might be interfering with the implicit verification that takes place upon becoming healthy.

Actually, this might be an edge case precipitated by an upgrade.
Since your current Freight (from the last Promotion that succeeded) seems to be lacking any verification history, I'm inferring that the last successful Promotion occurred with a nightly build that didn't include #2905. Since #2905 the implicit verification, which has always occurred upon reaching a healthy state in the absence of a user-defined verification process, now leaves behind an entry in the current Freight's verification history.
Had such an entry existed in the current Freight's verification history, the existing logic probably would have worked, but in this edge case, we need to ignore the outstanding verification of the current Freight because it was verified ages ago and there's just no record of it.
I think the fix still lies in checking the state of the last Promotion.

Here's the key:
If your last Promotion failed, the current Freight did not arrive via the last Promotion. It's old news and we shouldn't be waiting for it to be verified.
Fix incoming.


Haddock renders ambiguous type/value names strangely

(Originally observed in https://github.com/ekmett/lens/pull/1042.)
Here is a stripped-down version of Haddocks that you'd find in a typical lens module:
-- Bug.hs
module Bug where

data ReifiedLens = Lens

type Lens = ()

-- | A 'Lens'.
f :: Lens
f = ()

Note that the 'Lens' reference in f's Haddocks is ambiguous, as there is both a type and a data constructor named Lens. My reading of this section of the Haddock readthedocs is that when such ambiguities arise, Haddock will default to the type name:

Since values and types live in different namespaces in Haskell, it is possible for a reference such as 'X' to be ambiguous. In such a case, Haddock defaults to pointing to the type.

This is not what I observe in practice, however. If you render the Haddocks for this module by running the following command:
$ haddock Bug.hs -o bug --html
Warning: 'Lens' is ambiguous. It is defined
    * at Bug.hs:4:20
    * at Bug.hs:6:1
    You may be able to disambiguate the identifier by qualifying it or
    by specifying the type/value namespace explicitly.
    Defaulting to the one defined at Bug.hs:4:1
  25% (  1 /  4) in 'Bug'
  Missing documentation for:
    Module header
    ReifiedLens (Bug.hs:4)
    Lens (Bug.hs:6)

You will end up with the following HTML page:

I believe there are two bugs here:

The rendered Haddocks say "RenderedLens", which is completely different from the original "'Lens'". I'm not sure why this happens.
Moreover, RenderedLens refers to the value-level version of Lens, not the type-level Lens. If I understood the readthedocs correctly, it should be the other way around.

Note that I can't reproduce this bug on the ghc-9.6 branch of this repo, so presumably https://github.com/haskell/haddock/pull/1597 helped (cc @FinleyMcIlwaine).
Regarding the buggy code though, this comment looks suspicious to me...

Hi, thank you for this ticket, but Haddock now lives full-time in the GHC repository!
Read more at https://discourse.haskell.org/t/haddock-now-lives-in-the-ghc-repository/9576.
Let me know if you feel it is still needed, and I'll migrate it. :)


fix(transformer/class-properties): no raw for generated StringLiteral

Follow-on after #7815. Generated StringLiterals should have raw: None.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#7825  👈 (View in Graphite)
#7815
main

How to use the Graphite Merge Queue
Add either label to this PR to merge it via the merge queue:

0-merge - adds this PR to the back of the merge queue
hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

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

Merge activity

Dec 12, 9:33 PM EST: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


Update version.go

Fix reference to nonexisting URL at justwatch.coim

Codecov Report

Merging #1571 into master will not change coverage.
The diff coverage is 50.00%.

@@           Coverage Diff           @@
##           master    #1571   +/-   ##
=======================================
  Coverage   60.31%   60.31%
=======================================
  Files         218      218
  Lines       11843    11843
=======================================
  Hits         7142     7142
  Misses       3941     3941
  Partials      760      760

Impacted Files
Coverage Δ

internal/action/version.go
42.86% <0.00%> (ø)

cmd/gopass-jsonapi/jsonapi.go
31.43% <100.00%> (ø)

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 194199c...8d7e3f6. Read the comment docs.


new line

how do i go to new line?
I tried \ \ \n \newline but nothing.
thanks

Hi!
Sorry, I am not really sure what you mean.
A new line in obsidian simply needs to press enter.
or do your require a newline in any specific place?
for multi-line latex, use double dollar sign to enclose the expression:
$$
your latex
it can have multi-line, just press enter
$$
might this be what you need?

there is no multiline in latex math. You'd need an environment for that. Like \begin{matrix}\end{matrix} or array or cases.
But this is not related to this plugin.


[enhancement]: Enable Delete button while generating.

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
No response
What should this feature add?
My usual workflow starts with generating multiple pictures and then deleting most of them. If I set "Display In-Progress Images" setting to none, I can view the previous image while the next is generating. Often this time is enough to determine that the image is to be deleted, especially if I get unrequested NSFW. But the delete button is greyed out and I have to wait till the end of generation and then browse all the images again.
Please unblock the delete hotkey while generating. It should delete the image that is currently displayed on screen. Then ideally it should switch display to pre-previous image, but simply staying empty is OK too (until the next image is ready).
If you have concerns about image getting switched right before the Del button is pressed, and the wrong image being deleted, then I think the progress bar is a good enough warning against it, but disabling the button when progress is above 90% can be a solution.
Alternatives
No response
Aditional Content
No response

Still needed.

Bump, you bot.


Fix Reference to Undeclared Variable

what

Correct variable name for var.auto_tune.cron_schedule

why

cron_expression_for_recurrence referred to the wrong variable name, with _ not .

references

👍

/terratest

this depends on #167 and #168. We'll get these prioritized internally

/terratest


Limit the number of Elastic queries in the vue-storefront-api per each catalog request

What is the motivation for adding / enhancing this feature?

Currently, per each catalog request, we're executing at least 2 Elastic queries:

getting the products,
getting the tax rates to calc the taxes.

The rates can be stored in Redis/local memory as they're changing extremely rarely!
Where to start:

https://github.com/DivanteLtd/vue-storefront-api/blob/d7b6fe516eeb214615f54726fb382e72ff2cc34b/src/platform/magento2/tax.js#L80
https://github.com/DivanteLtd/vue-storefront-api/blob/d7b6fe516eeb214615f54726fb382e72ff2cc34b/src/platform/magento1/tax.js#L80

Related to: #3367
What are the acceptance criteria

[ ] tax rates are being stored in the local cache and each api/catalog request engages Elastic just for single query

Can you complete this feature request by yourself?

[ ] YES
[ ] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[x] This is a normal feature request. This should be available on https://test.storefrontcloud.io and then after tests this can be added to next Vue Storefront version. In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] (Pick this option only if you're sure) This is an important improvement request for current Release Candidate version on https://next.storefrontcloud.io and should be placed in next RC version. In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] (Pick this option only if you're sure) This is a critical improvement request for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version. In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Additional information

closed becuase #3367 solves this issue as well


Network target not working with AutoFlushWrapper and BufferingWrapper

Hello! Thank you for supporting NLog!
NLog version: 5.2.2
Platform: .Net 4.6.2
Current NLog config (xml or C#, if relevant)
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	  autoReload="true"
	  internalLogToConsole="true"
	  internalLogLevel="Info">
	<targets>
		<target name="Logstash" xsi:type="AutoFlushWrapper" condition="level >= LogLevel.Error" flushOnConditionOnly="true">
			<target xsi:type="BufferingWrapper" bufferSize="5" overflowAction="Discard">
				<!--<target xsi:type="Console" layout="${message}"/>-->
				<!--<target xsi:type="File" layout="${message}" fileName="log.txt"/>-->
				<target name="Network" xsi:type="Network" layout="${message}" address="tcp://localhost:9045" newLine="true" />
			</target>
		</target>
	</targets>
	<rules>
		<logger name="*" minlevel="Info" writeTo="Logstash" />
	</rules>
</nlog>

Program.cs:
var logger = LogManager.GetCurrentClassLogger();

for (int i = 0; i < 10; i++)
{
    logger.Info($"I'm {i}");
}

logger.Error("Error");

This config works as expected with Console or File targets, but seems not working with Network target. Unwrapped Network target with the same settings works as expected. Internal log show no errors or something suspicious .

Thanks, @snakefoot. How can I make sure if it has enough time? I tried to add LogManager.Flush, but I guess AutoFlushWrapper is instructed to ignore it.

Yes when AutoFlushWrapper has flushOnConditionOnly="true", then it will ignore explicit flush / shutdown.
I guess one could extend AutoFlushWrapper, so instead of ignoring explicit flush, then explicit flush will "wait" for any pending flush.

Yes NLog InternalLogger usually only produces output when something interesting happens. Maybe if you change to internalLogLevel="Trace", then you will get more output.

Created pull-request #5308 that tries to improve AutoFlushWrapper handling of explicit-flush when using flushOnConditionOnly="true". The explicit-flush will await any pending async-flush-operations, before signaling completion.

NLog v5.2.3 has been released - https://www.nuget.org/packages/NLog

Thanks @snakefoot, new version works! So it was a bug really? Because I was plying with network-tracing and I saw that NLog was sending network requests. I thought that problem was with "batching" of requests (with possible breaking of message struct) or with a receiving party.

Excellent. Happy that I guessed correctly about what the issue was. I guess you felt it was a bug,  but flushOnConditionOnly="true" means ignore explict flush, and that was exactly what it did :)
Have now changed to so explicit flush is not completely ignored, and hopefully this gives a better behavior when using flushOnConditionOnly="true" together with async-targets (Like the network-target).

Thanks again! May be I didn't understand the Idea behind this config, I took it from from the documentation... The problem that I'm trying to solve is the following:.. We have classic desktop application (we have to) that is installed on hundreds of stations and it's really over logging as we may don't know what may help us to understand the issue of particular user. So I want NLog to collect last X of log messages and push them only when first error occurs.

Then the combination of AutoFlushWrapper and BufferingWrapper with discard should give that behavior. And with NLog v5.2.3 then it has better support for asyn-targets like the NetworkTarget.


Add aten::mv support

This adds support for matrix vector product when importing from PyTorch by decomposing into nn.dense and munging with the shapes so it looks like an ordinary matrix multiply.
Note for reviewers: This is stacked on #9893, please use this diff for reviewing

please resolve the conflict (also hit an CI issue).


add dropdown select component

add dropdown select component

Coverage decreased (-0.04%) to 1.147% when pulling 092e7a48a2b223b61333b9e98e06f93a4487aee8 on embbnux:feature-dropdown-select into 19dbeca5598c32dab015da42ef415803c274cd27 on ringcentral:master.


ARK implementation TrustWallet

Description
Added ARK implementation.
Testing instructions
./tools/tests
WARNING: will generate different private key with BIP44 than their official wallet. Official wallet just hashes the mnemonic instead of using BIP44.

Can you add copyright header for new files?
// Copyright © 2017-2019 Trust Wallet.
//
// This file is part of Trust. The full Trust copyright notice, including
// terms governing use, modification, and redistribution, is contained in the
// file LICENSE at the root of the source code distribution tree.

can you rebase master and fix the CI? thanks


Test extending alphanumerics

Hello! I'd be interested in understanding the context/plans for this PR. We have several tables containing a period in their PK string column, so these currently can't be diffed.

The plans are to ensure that this change doesn't break or significantly reduces performance for regular alphanumeric columns.
Once we verify this, ideally through our own tests, but I would also be satisfied by accounts of several users who tried it and reported back, I'll feel comfortable merging it in.


Make css from sphinx_book_theme inheritable

Despite specifying this inheritance in theme.conf
https://github.com/pangeo-forge/pangeo-sphinx-book-theme/blob/787b3d7f80ed55cee636a301b668c0b2b0d42365/pangeo_sphinx_book_theme/theme.conf#L1-L2
... I still needed to manually add the sphinx_book_theme css styles to the top of the custom css for this theme:
https://github.com/pangeo-forge/pangeo-sphinx-book-theme/blob/787b3d7f80ed55cee636a301b668c0b2b0d42365/pangeo_sphinx_book_theme/static/custom.css#L1-L5
(Without this direct copy-and-paste from the sphinx_book_theme, the styles did not work correctly.)
It seems like this should not be necessary, but I am not sure how (or if) it is possible to get the styles properly loaded without it.

Can you use a css import rule to import the "upstream" stylesheet from sphinx_book_theme?

Good thought; that would certainly be a cleaner way of implementing the same notion.
Perhaps I've misunderstood the idea of sphinx inheritance, but somehow I'd imagined that inheriting from the theme would automatically result in the parent theme's styles being passed to the child theme. So it was odd to me that this copy-and-paste (or a more graceful @import) would be required at all.
Not really a big deal I suppose, if it works, but I'll be curious to learn more about this as time goes on.

I'm sure the folks over at https://github.com/executablebooks/sphinx-book-theme would be happy to help. @choldgraf is one the the lead devs and a very close collaborator.

hmmm, indeed it is strange, I'd assume that all of the CSS would be inherited as well 🤔 did the CSS make it into your site's generated HTML files?
(also out of curiosity why are you creating a new sub-theme? you might be able to accomplish your goal by just including your own custom CSS etc)

also out of curiosity why are you creating a new sub-theme?

We want to use the same styling on many different sites. See https://github.com/pangeo-forge/pangeo-forge-recipes/issues/126.

did the CSS make it into your site's generated HTML files?

As far as I could tell, they were not passing through to the generated HTML files. I ultimately figured this out by diffing  two _build/html/ directories (one from before packaging, and one from after). I wish I had a more productive snapshot of this to share here, but the evidence was ultimately lost in a frenzy of trial-and-error. 😅 (Note to self: keep records next time.)

you might be able to accomplish your goal by just including your own custom CSS etc

Yes, I realized about 3/4 of the way through, that this is basically all we are doing at this point: i.e. making a single CSS file pip-installable alongside the parent theme. Admittedly the overhead-to-benefit ratio may be a bit high, but given the large number of sites which may eventually use this color scheme, perhaps it is worth it to be able to keep any future stylistic changes in sync.

We want to use the same styling on many different sites

Ah cool - though one thought, couldn't you just define one CSS file (e.g., in a github repository) and then link to it in the sphinx setup with
def setup(app):
  app.add_css_file(url-for-your-css-file)

?
That might be a bit simpler than defining your own sub-theme.

link to it in the sphinx setup with

Forgive the n00b question, but I'm not clear what you mean by "sphinx setup" here. Is there a setup.py that I'm overlooking somewhere?
We previously included the custom styles in the sphinx conf.py with
html_css_files = ["custom.css",]

...but of course this required keeping custom.css in the project repo.
This is not an urgent item, but will so appreciate your feedback as time allows.


Minor documentation fixes

A few minor issues with the documentation I noticed while setting up acmed.

Thank you! :)


Tracking: binary format bugs and unimplemented features

[ ] #8041
[ ] #7949

Might be higher priority, if users query with parameters (requires extended query mode -> uses binary format) or some integrations require binary format (cr: @jon-chuang ).
https://www.postgresql.org/docs/current/protocol-overview.html#PROTOCOL-QUERY-CONCEPTS


Note that we flag the java 6 and 7 versions as vulnerable

Fixes #43

Note: It's 2.12.2+ instead of 2.12.3+ and there is a discrepancy because 2.3.2 is not being detected althouht 2.3.1 is being detected.

Thanks! I'll take a look at that discrepancy to see whether it makes sense to try to fix it. Removed the version ranges from this PR.


Remove usage of deprecated jackson property

Description of changes:
PropertyNamingStrategy.CAMEL_CASE_TO_LOWER_CASE_WITH_UNDERSCORES is deprecated since Jackson 2.7 (2.12 is used). This was done to help potentially unblock https://github.com/quarkusio/quarkus/pull/37295
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

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

Comparison is base (398ec05) 28.08% compared to head (c9a103b) 24.27%.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #391      +/-   ##
============================================
- Coverage     28.08%   24.27%   -3.81%
+ Complexity      574      498      -76
============================================
  Files           138      138
  Lines          5256     5256
  Branches        635      635
============================================
- Hits           1476     1276     -200
- Misses         3578     3797     +219
+ Partials        202      183      -19

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

LGTM
For future note, I see we are testing the EntityImpl serialization here.
https://github.com/aws/aws-xray-sdk-java/blob/398ec0542964b4d9b38c901385eda4d98da07cd4/aws-xray-recorder-sdk-core/src/test/java/com/amazonaws/xray/entities/EntityTest.java#L48


Receive screen changes.

-On clicking QR or link, the modal should come up just below the contact details.
-The contact details will move up a little as we don’t need to change the account.
-The background should go grey like when loading.

-Don’t need anything above this line.
-The modal that opens up should be short and the rest is visible on the parent screen anyway.

-Don’t need above this line.

-When coming from a certain account, this is selected and not editable.
-Need a non editable version here. Only when generated from outside the accounts.

-The link Getting cut.

-In the text "Receving To",the T should be small t.

-we can’t change it on this "Receive via QR" screen.

Need a UX that shows this as uneditable.

-On receive screen,the Note should be like:
-Sharing options. Use any of the methods shown to share the request link or Bitcoin address.

-Remove this line from "Receive via Link" modal.

As per discussed,

Change the top headline to be only ‘Receive’
On the action buttons at the bottom, it should be ‘Share’ and ‘QR’
On the link modal, the heading should be ‘Share’
The second line should be ‘Share with your contact’ if it is a link. or ‘Share bitcoin address’ if it is an address. (this can be decided based on the checkbox selection on the main screen.
For QR model, the headline should be ‘QR’. Second line should be what is there now.


Investigate MPC

Start building a wiki page about current team approaches and how we might approach model predictive control.

https://qutms.wiki/wiki/index.php/Model_Predictive_Controller


Token limit?

How does this handle really long documents?
(fabric) xxx@xxxx-MBA client % cat /Users/xxxx/Downloads/xxx\ xxx\ Story\ Building\ Contents/Synthesis_Report.md | fabric --pattern write_essay
Error: Error code: 429 - {'error': {'message': 'Request too large for gpt-4 in organization org-xVSxxxxxbU on tokens per min (TPM): Limit 40000, Requested 40939. The input or output tokens must be reduced in order to run successfully. Visit https://platform.openai.com/account/rate-limits to learn more.', 'type': 'tokens', 'param': None, 'code': 'rate_limit_exceeded'}}
Error code: 429 - {'error': {'message': 'Request too large for gpt-4 in organization org-xVxxxxxxxxxxx on tokens per min (TPM): Limit 40000, Requested 40939. The input or output tokens must be reduced in order to run successfully. Visit https://platform.openai.com/account/rate-limits to learn more.', 'type': 'tokens', 'param': None, 'code': 'rate_limit_exceeded'}}

The curent max is 128,000, so you will need to summarize it or break it into pieces to get it below that.


Expose the expiration date of Flickr Pro subscriptions (if applicable)

This is part of https://github.com/Flickr-Foundation/commons.flickr.org/issues/233
Every Flickr Commons member gets free Flickr Pro, and we want to know if that's about to expire soon so we can get it renewed. This patch exposes that expiration date through this API.

I'm also adding the basic config for interrogate here, which is a tool for checking docstring coverage (see https://github.com/alexwlchan/alexwlchan/issues/18).
Adding it to this library in one go is quite a big task and liable to create conflicts if I have a long-running branch, so I'm just going to ratchet it up gradually – for example, all the code in this patch has 100% docstring coverage. As I edit more files, I'll continue to backfill docstrings and crank up that number.


Recreate scheduled notification by same id

When used scheduling with same notificationId will be shown only last created notification
Example:
AwesomeNotifications().createNotification(
      content: NotificationContent(
        id: 1,
        channelKey: 'alerts',
        title: 'title',
        body: 'body',
        payload: {'notificationId': '1234567890'},
      ),
      schedule: NotificationCalendar.fromDate(date: DateTime.now().add(const Duration(seconds: 20))),
    );

AwesomeNotifications().createNotification(
    content: NotificationContent(
      id: 1,
      channelKey: 'alerts',
      title: 'title2',
      body: 'body2',
      payload: {'notificationId': '1234567890'},
    ),
    schedule: NotificationCalendar.fromDate(date: DateTime.now().add(const Duration(seconds: 40))),
  );

As result the first notification (title: 'title', body: 'body') won't shown
Expectation:  Add the field in NotificationSchedule, for example, "notificationId", that for default null save current logic but for   int value perform override id from NotificationContent
This logic will allow show notifications within one unit. Old logic create many notifications without opportunity cancel previous notification.

And how it should behave in case both notifications had being created, but not fired, and:

You wanna to cancel only one of the schedules.
You wanna to update only one of the schedules.

I'm sorry. Schedules should be with different NotificationContent.id:
await AwesomeNotifications().createNotification(
      content: NotificationContent(
        id: 1,
        channelKey: 'alerts',
        title: 'title',
        body: 'body',
        payload: {'notificationId': '1234567890'},
      ),
      schedule: NotificationCalendar.fromDate(date: DateTime.now().add(const Duration(seconds: 20))),
    );

await AwesomeNotifications().createNotification(
    content: NotificationContent(
      id: 2,
      channelKey: 'alerts',
      title: 'title2',
      body: 'body2',
      payload: {'notificationId': '1234567890'},
    ),
    schedule: NotificationCalendar.fromDate(date: DateTime.now().add(const Duration(seconds: 40))),
  );

And how it should behave in case both notifications had being created, but not fired, and:
You wanna to cancel only one of the schedules.

In this case canceling will being by NotificationContent.id. Due to notification had being created, but not fired, it won't shown  after canceling schedule

You wanna to update only one of the schedules.

Also by NotificationContent.id
Only if notifications had being fired, it will can be cancelled by NotificationSchedule.notificationId

And how it should behave in case both notifications had being created, but not fired, and:
You wanna to cancel only one of the schedules.

In this case canceling will being by NotificationContent.id. Due to notification had being created, but not fired, it won't shown after canceling schedule

You wanna to update only one of the schedules.

Also by NotificationContent.id
Only if notifications had being fired, it will can be cancelled by NotificationSchedule.notificationId

Doing all this using different IDs is already covered by the plugin.

Doing all this using different IDs is already covered by the plugin.

Now not opportunity for creating several scheduler process  that will be send in one notification with same id.
Best way probably to do for NotificationContent own notificationId, but for NotificationSchedule own scheduleId
the schedule will be cancelled by cancelSchedule(scheduleId:...)
the notification will be cancelled by cancelNotification(notificationId:...)
if this logic will embed in the lib it is good due to the result is the best variation


Remove --simpleresolution from other flags

The current NetSDK targets sets the otherflags to contain --simpleresolution.    NetSDK projects must always have this flag set.  The coreclr compiler only allows it to be true.  The desktop compiler, allows it to be true or false and defaults to false.
Anyway, we don't really want to expose this on our properties page.  So we have added a property in the targets file, which allows us to surface other flags as empty by default.
/cc @TIHan

There is one failure in CI now.


Roll Flutter Engine from 9c3f66d822e4 to a393d2e114f7 (4 revisions)

https://github.com/flutter/engine/compare/9c3f66d822e4...a393d2e114f7
2024-08-30<EMAIL_ADDRESS>Roll Fuchsia Test Scripts from NWpblL_DFACOx_Spi... to DtxLvjJOVzo_oZGui... (flutter/engine#54891)
2024-08-30<EMAIL_ADDRESS>Roll Skia from c23d19fdf117 to 2b633f7626ea (1 revision) (flutter/engine#54890)
2024-08-30<EMAIL_ADDRESS>Roll Skia from 9ce15f8b2c7e to c23d19fdf117 (2 revisions) (flutter/engine#54889)
2024-08-30<EMAIL_ADDRESS>Roll Dart SDK from 139867e57ba9 to 88d311c9a531 (1 revision) (flutter/engine#54886)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC matanl@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


stack-buffer-overflow in sixel_encoder_encode_bytes at encoder.c:1788

Version Libsixel :1.8.6
Ubuntu 20.04 LTS
I fuzzed the sixelapi
#include <stdio.h>
#include <stdlib.h>
#include <stdint.h>
#include <string.h>

#include "sixel.h"

int main(){

    sixel_encoder_t *encoder=NULL;
    int ncolors=16;
    char opt[256]={0};
    SIXELSTATUS status;
    unsigned char data[4096]={0xa,0xa,0xa,0xa,0xc7,0xc7,0xc7,0xc7,0xc7,0xc7,0xc7,
                             0xc7,0xc7,0xa,0xc7,0xc7,0xf2,0x60,0xa,0x60,0x60,0x60,
                             0x60,0xa,0x60,0x60,0x60,0x60,0x60,0x60,0x60,0x60,0x60,
                             0x60,0x60,0x60,0x60,0x60,0x60,0xa,0x60,0x60,0xa,0x60,
                             0x60,0x60,0x60,0x60,0x60,0x60,0x60,0xa,0x60,0x60,0x60,
                             0x60,0x60,0x60,0x60,0x60,0x60,0x60,0x60,0x60,0x60,0x60,
                             0x60,0x60,0x60,0x60,0x60,0xa,0x60,0x60,0x60,0x60,0x60,
                             0x60,0x60,0x60,0x0,0xa,0x0,0xa,0xa,0x0,0x0,0xa,0xa,0x0,
                             0x0,0xa,0xa,0x0,0xa,0xa,0x0,0x0,0x0,0x0,0x0,0x0,0x0,0x0};

    status = sixel_encoder_new(&encoder,NULL);
	if(SIXEL_FAILED(status))
		return 0;

	sprintf(opt, "%d", ncolors);
	status = sixel_encoder_setopt(encoder,SIXEL_OPTFLAG_COLORS,opt);
	if(SIXEL_FAILED(status))
		return 0;

	status = sixel_encoder_encode_bytes(encoder,(unsigned char*)data,400,300,SIXEL_PIXELFORMAT_RGBA8888,NULL,(-1));
	if(SIXEL_FAILED(status))
		return 0;

	printf("[+] end\n");
	sixel_encoder_unref(encoder);

    return 0;

}

Please use the following method to compile the attached cc file and run
clang++ -g -fsanitize=address -I/usr/local/include -L/usr/local/lib -lsixel poc.cc -o poc

poc
Because uploading the zip failed,I switched to a txt file,please download the attachment and modify the suffix to cc
==344010==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7fff79a6ae60 at pc 0x7f2d3c751a0c bp 0x7fff79a68d00 sp 0x7fff79a68cf8
READ of size 1 at 0x7fff79a6ae60 thread T0
    #0 0x7f2d3c751a0b in get_rgb /home/hx/userData/tools/libsixel/src/pixelformat.c:50:18
    #1 0x7f2d3c750fe9 in expand_rgb /home/hx/userData/tools/libsixel/src/pixelformat.c:186:13
    #2 0x7f2d3c750a8d in sixel_helper_normalize_pixelformat /home/hx/userData/tools/libsixel/src/pixelformat.c:294:9
    #3 0x7f2d3c74712a in sixel_dither_initialize /home/hx/userData/tools/libsixel/src/dither.c:559:18
    #4 0x7f2d3c7cf3c6 in sixel_encoder_prepare_palette /home/hx/userData/tools/libsixel/src/encoder.c:575:14
    #5 0x7f2d3c7cc367 in sixel_encoder_encode_frame /home/hx/userData/tools/libsixel/src/encoder.c:981:14
    #6 0x7f2d3c7cbea2 in sixel_encoder_encode_bytes /home/hx/userData/tools/libsixel/src/encoder.c:1816:14
    #7 0x4c6dbb in main /home/hx/userData/tools/libsixel/demo2.cc:34:11
    #8 0x7f2d3c1650b2 in __libc_start_main /build/glibc-ZN95T4/glibc-2.31/csu/../csu/libc-start.c:308:16
    #9 0x41c31d in _start (/home/hx/userData/tools/libsixel/demo2+0x41c31d)

Address 0x7fff79a6ae60 is located in stack of thread T0 at offset 4480 in frame
    #0 0x4c6abf in main /home/hx/userData/tools/libsixel/demo2.cc:8

  This frame has 3 object(s):
    [32, 40) 'encoder' (line 10)
    [64, 320) 'opt' (line 12)
    [384, 4480) 'data' (line 14) <== Memory access at offset 4480 overflows this variable
HINT: this may be a false positive if your program uses some custom stack unwind mechanism, swapcontext or vfork
      (longjmp and C++ exceptions *are* supported)
SUMMARY: AddressSanitizer: stack-buffer-overflow /home/hx/userData/tools/libsixel/src/pixelformat.c:50:18 in get_rgb
Shadow bytes around the buggy address:
  0x10006f345570: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10006f345580: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10006f345590: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10006f3455a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10006f3455b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x10006f3455c0: 00 00 00 00 00 00 00 00 00 00 00 00[f3]f3 f3 f3
  0x10006f3455d0: f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 f3 00 00 00 00
  0x10006f3455e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10006f3455f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10006f345600: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x10006f345610: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Shadow byte legend (one shadow byte represents 8 application bytes):
  Addressable:           00
  Partially addressable: 01 02 03 04 05 06 07
  Heap left redzone:       fa
  Freed heap region:       fd
  Stack left redzone:      f1
  Stack mid redzone:       f2
  Stack right redzone:     f3
  Stack after return:      f5
  Stack use after scope:   f8
  Global redzone:          f9
  Global init order:       f6
  Poisoned by user:        f7
  Container overflow:      fc
  Array cookie:            ac
  Intra object redzone:    bb
  ASan internal:           fe
  Left alloca redzone:     ca
  Right alloca redzone:    cb
  Shadow gap:              cc
==344010==ABORTING

It appears that CVE-2020-36120 was assigned to this issue.
This issue was closed in https://github.com/saitoha/libsixel/issues/143#event-4221391513, was it fixed in master branch?

@saitoha what is status of this bug report? Is this fixed in some commit? Do you have plans to keep maintaining libsixel?


Memory allocating issue

Hi, great work, but you have allocation issue
you should create a new Rect field, and set bounds after that draw reference to this variable

It's my mistake. I fixed it right now. Thank you so mach :-)


[Tracking] rustdocs for public functions of libazureinit

Description
Public functions/structs/variables of libazureinit should have own rustdocs. Ideally they should also include example code.

error (https://github.com/Azure/azure-init/pull/129)

[x] Error

goalstate (https://github.com/Azure/azure-init/pull/129)

[x] Goalstate
[x] Container
[x] RoleInstanceList
[x] RoleInstance
[x] get_goalstate
[x] report_health

http (https://github.com/Azure/azure-init/pull/129)

[x] RETRY_CODES
[x] HARDFAIL_CODES
[x] IMDS_HTTP_TIMEOUT_SEC
[x] WIRESERVER_HTTP_TIMEOUT_SEC

imds (https://github.com/Azure/azure-init/pull/129)

[x] InstanceMetadata
[x] Compute
[x] OsProfile
[x] PublicKeys
[x] string_bool
[x] query

media (https://github.com/Azure/azure-init/pull/144 by @John15321)

[x] Environment
[x] ProvisioningSection
[x] LinuxProvisioningConfigurationSet
[x] PlatformSettingsSection
[x] PlatformSettings
[x] PATH_MOUNT_DEVICE
[x] PATH_MOUNT_POINT
[x] get_mount_device
[x] Mounted
[x] Unmounted
[x] Media
[x] parse_ovf_env
[x] mount_parse_ovf_env

provision/hostname

[x] Provisioner

provision/mod

[x] Provision
[x] Provision::hostname_provisioners
[x] Provision::user_provisioners
[x] Provision::password_provisioners
[x] Provision::provision

provision/password

[x] Provisioner

provision/ssh

[ ] provision_ssh

provision/user

[x] User
[x] User::new
[x] User::with_password
[x] User::with_groups
[x] Provisioner
[ ] Provisioner::create

unittest (https://github.com/Azure/azure-init/pull/129)

[x] get_http_response_payload
[x] serve_requests

https://github.com/Azure/azure-init/pull/147
Here is a PR (a draft, but soon ready) for the ssh.rs module @dongsupark


Fix the data retrieved by pull_issues.py

[x] Restore the assignees that were removed from issue_info.
[x] Add creation and closing timestamps, as they could be useful for future development and are provided for free.

issue_info = {
                "github_id": issue.number,
                "title": issue.title,
                "body": issue.body,
                "assignee": issue.assignee.login, # Restore
                "created_at": issue.created_at, # Add
                "closed_at": issue.closed_at, # Add
            }

Why are the created_at and closed_at useful for us?


How to inset X Y Scatter Chart to excel document with FastExcel?

Hi
I want to inset X Y scatter chart to plot x and y data to excel. Can I do it with FastExcel?

Hi VahedCivil
FastExcel is a too basic for this, have a go at https://github.com/JanKallman/EPPlus
Cheers
mrjono1


Release 0.29.0

Signed-off-by: Miroslav Kovar<EMAIL_ADDRESS>

Codecov Report

Merging #431 (6308f2f) into main (e24a188) will decrease coverage by 19.18%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main     #431       +/-   ##
===========================================
- Coverage   66.39%   47.21%   -19.19%
===========================================
  Files         152      151        -1
  Lines       14050    12736     -1314
  Branches     2736     2548      -188
===========================================
- Hits         9329     6013     -3316
- Misses       2522     5254     +2732
+ Partials     2199     1469      -730

Flag
Coverage Δ

integration-aries-vcx
?

unittests-agency-client
22.30% <ø> (ø)

unittests-aries-vcx
49.56% <ø> (-0.07%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ndlers/proof_presentation/prover/states/initial.rs
0.00% <0.00%> (-100.00%)
:arrow_down:

aries_vcx/tests/utils/devsetup_agent.rs
0.00% <0.00%> (-77.68%)
:arrow_down:

aries_vcx/tests/test_integration.rs
6.01% <0.00%> (-76.50%)
:arrow_down:

aries_vcx/src/libindy/utils/anoncreds.rs
8.81% <0.00%> (-67.41%)
:arrow_down:

...x/src/handlers/proof_presentation/prover/prover.rs
15.66% <0.00%> (-62.01%)
:arrow_down:

..._vcx/src/handlers/proof_presentation/prover/mod.rs
21.42% <0.00%> (-57.15%)
:arrow_down:

aries_vcx/src/libindy/utils/signus.rs
33.33% <0.00%> (-55.56%)
:arrow_down:

aries_vcx/src/libindy/utils/pool.rs
9.27% <0.00%> (-54.09%)
:arrow_down:

...es_vcx/src/handlers/issuance/credential_def/mod.rs
0.00% <0.00%> (-52.36%)
:arrow_down:

aries_vcx/src/utils/provision.rs
0.00% <0.00%> (-50.00%)
:arrow_down:

... and 71 more

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 e24a188...6308f2f. Read the comment docs.


Add support for providing storage uri as model_dir

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #3423
Type of changes
Please delete options that are not relevant.

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

Feature/Issue validation/testing:
Please describe the tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

[ ] Test A

[ ] Test B

Logs

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Checklist:

[ ] Have you added unit/e2e tests that prove your fix is effective or that this feature works?
[ ] Has code been commented, particularly in hard-to-understand areas?
[ ] Have you made corresponding changes to the documentation?

Release note:

Add support for providing storage uri as model_dir

Thanks for this change, we should get this in quickly

Is this fixing the same issue in other runtimes as the one I fixed in #3424 for HF?

Yep.

Discussed with @yuzisun and we decided that --model_dir should be a local path and to download models from storage providers, users should leverage the storage-initializer.


Fixed #31268 -- Updated Algerian Arabic (ar_DZ) locale formats.

@infosrabah Apart from you support question, Should we update formats for Algerian Arabic?
(\cc @claudep).

It's very important that the format settings represent the real way date and time is presented in your country in Arabic. It should absolutely have nothing to do with any technical problem you may have with bootstrap or any other tool.
For example, on Wikipedia (https://en.wikipedia.org/wiki/Algeria), the documented date format is dd/mm/yyyy (d/m/Y).

Yues update the format Felix, please.
Hi claude,
I agree about what you said,
But we do have 2 major languages in Algeria(French and Arabic), the date that your are refering to is for fr-DZ wich is dd/mm/yyyy (d/m/Y). but I chere we are talking about ar-DZ wich is completly the RTL way (opposite) : yyyy/mm/dd (Y/m/d). I may in the future create a fr-DZ formats.py wich is almost the same as fr-FR.
And beside of that I do not witness any technical problem you mentioned about bootstrap or any other tool. I just asked Felix about the way to get the actual coutry format that has been applied to a date. just to convert that and pass it to front-end tool. So there will be some consistency between the two world (front-end and backend), and that makes your life much easier when it comes about (Validation).
Thank you Claude

As I can see, the current format of RTL languages like Arabic, Hebrew and others are still using the d/m/Y syntax in format settings. Maybe something to ask on the django-i18n mailing list?

Hi Claude,
Here's as examples of some local news paper online website and even a lcoal TV website formats used : (dates are surrounded green)
1 - News paper 1 https://ibb.co/d6Cyshd
2 - News paper 2 (Sport) https://ibb.co/frrd9fP
3 - Local TV https://ibb.co/85Bh53R
Now if most RTL other countries are using or still using 'd/m/Y ' as you said, my country is not. as you said you have to make it reflect as in real life (that's what I'm trying to do).
For every date on any ressource (News, Official communications, News papper) that using Arabic as a language, the Date format is 'Y/m/d'.
About the wikipedia that you posted about Algeria and the Date format used 'dd/mm/yyyy' (d/m/Y). This applies for the French language in Algeria (fr-DZ) LTR, not the arabic (ar-DZ) that we are talking about here.
Hope I shed more light on this post and gave you more reasons to convice you that the Date format for Arabic Algeria (ar-DZ) is 'Y/m/d'.
Thank you.

That's very precious data, thanks! Now may I ask you to create a ticket and provide the information you just wrote to that ticket? Ticket data is supposed to be kept long term, contrary to pull request comments.
Are you also able to confirm that what you said is only for short dates, and that the "normal" date format is still "day month year" (j F Y)?

Hi claude,
Thank's for the quick answer.
For the nomal date the format is the same as you said. ( j F Y ) I confirm it. I used this format ( j F Y ) and the date rendred well in djkango tempalte for RTL, you can refer to the news paper number 1 in the top of the page surrounded green. so far so good.
Now do you want me to go to "Django's bug tracker and wiki" and create a new ticket ??
If so, what do you want me to say out-there ???, this is not a bug/issue, this is settings country format for a specific language. !!
Hope to hear from you soon.

@infosrabah I'm also confused, TBH :smile: Please create a new ticket and describe what is incorrect/missing in the current Algerian Arabic (ar_DZ) locale formats. Should we update only SHORT_DATE_FORMAT? or maybe all change from this PR are required.
This is still an issue in Django even if it's only in a country specific format.

HI Felix,
All change from this PR are required.
Now for the "SHORT_DATE_FORMAT" is little bit different when it comes about arabic, to be specific there's isn't, meaning we do not have Short version of month like "Jan","Fev"... "Dec", We do have a whole Month names "January" in Arabic, Month can't be can't trunc to get a Short version.
I made a second pull request wich fix everrrrrrything, So yes Update all changes.
I'm gonna create a new ticket sure.
Thank you Felix

@infosrabah Thanks :+1: I changed SHORT_DATETIME_FORMAT = 'j N Y H:i' to 'Y/m/d H:i', because if abbreviations of months don't exist in Algerian Arabic we shouldn't use N in formats. Can you confirm the current form?

Ticket created at : https://code.djangoproject.com/ticket/31268
thank you

Yes I confirm it Felix,
I have a lots in mind, so it's kind of hard to follow, LoL.
Thank you

But What about (DATE_INPUT_FORMATS, TIME_INPUT_FORMATS, DATETIME_INPUT_FORMATS) ????,
really interesting about inputs format to be reflected to django forms.

I'm not really understand what's the question? Please approve this PR if these changes work for you and if something should be changed you can push changes.


Switch React state management to Redux

React state management is getting pretty complex in Template Studio, with a lot of callback handlers. We should consider switching to Redux:
https://redux.js.org/introduction/getting-started
https://react-redux.js.org

Closing due to the established use of Redux (with sagas) currently in use. This will be an ongoing practice for TSv2.


⛓ Add arbitrum reddit test chain

Tests written by you do not pass, try to fix that and run pnpm test before pushing changes.

@mj426382 thanks for your comment, I have resolved all of them, and the tests are passing on my end. Could you review it again?

Can you verify multicall contracts code on https://testnet.redditspace.com/ There is only this small thing to merge this PR :)

They both are verified.

Multicall:   https://testnet.redditspace.com/address/0x722db82dea58c880D03b87885053F206f1B37136/contracts
Multicall2: https://testnet.redditspace.com/address/0xD4D664D419A6A845C98Cc366ae1c4b24592BD5CE/contracts

@mj426382 btw I was trying to resolve this error by this PR:
UnsupportedChainIdError: Unsupported chain id: 5391184. Supported chain ids are: 1337,31337,43114,43113,42161,421611,1313161554,1313161555,1,3,4,5,42,56,97,25,338,250,4002,100,1666600000,1088,588,1285,1287,1284,11297108109,11297108099,137,80001,42262,42261,19,361,365,108,18,69,10,106,111,280.
    at useEthers (useEthers.ts:67)
    at Component (HeaderWarning.js:10)
    at renderWithHooks (react-dom.development.js:14985)
    at updateFunctionComponent (react-dom.development.js:17356)
    at beginWork (react-dom.development.js:19063)
    at beginWork$1 (react-dom.development.js:23940)
    at performUnitOfWork (react-dom.development.js:22776)
    at workLoopSync (react-dom.development.js:22707)
    at renderRootSync (react-dom.development.js:22670)
    at performSyncWorkOnRoot (react-dom.development.js:22293)
    at react-dom.development.js:11327
    at unstable_runWithPriority (scheduler.development.js:468)
    at runWithPriority$1 (react-dom.development.js:11276)
    at flushSyncCallbackQueueImpl (react-dom.development.js:11322)
    at flushSyncCallbackQueue (react-dom.development.js:11309)
    at flushSync (react-dom.development.js:22467)
    at Object.scheduleRefresh (react-dom.development.js:24429)
    at react-refresh-runtime.development.js:304
    at Set.forEach (<anonymous>)
    at Object.performReactRefresh (react-refresh-runtime.development.js:293)
    at RefreshUtils.js:62 5391184 "ERROR!!!!!!!!!!"

Everything looks fine, please run pnpm lint:fix in core folder and update changes.
@mj426382 done.

@mj426382 please which test you mean is failing, I checked the testing logs here for the ArbitrumReddit test script and it appears that it's working successfully.

@mj426382 do you mean this failing test?
 |   408 passing (1m)
 |   2 pending
 |   1 failing
 |
 |   1) useConfig
 |        default testing config:
 |
 |       AssertionError: expected 43 to equal 42
 |       + expected - actual
 |
 |       -43
 |       +42
 |
 |       at Context.<anonymous> (src/hooks/useConfig.test.tsx:47:112)
 |       at runMicrotasks (<anonymous>)
 |       at processTicksAndRejections (node:internal/process/task_queues:96:5)
 |
 |
 |
 | error Command failed with exit code 1.
 | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
 | `yarn test -- --timeout 0` failed with exit code 1
Stopping 3 active children

@mj426382 do you mean this failing test?
 |   408 passing (1m)
 |   2 pending
 |   1 failing
 |
 |   1) useConfig
 |        default testing config:
 |
 |       AssertionError: expected 43 to equal 42
 |       + expected - actual
 |
 |       -43
 |       +42
 |
 |       at Context.<anonymous> (src/hooks/useConfig.test.tsx:47:112)
 |       at runMicrotasks (<anonymous>)
 |       at processTicksAndRejections (node:internal/process/task_queues:96:5)
 |
 |
 |
 | error Command failed with exit code 1.
 | info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
 | `yarn test -- --timeout 0` failed with exit code 1
Stopping 3 active children

yes, because you added reddis chain to supported, so the number was increased by 1