gopass init --store : "Failed to initialize git"

This issue is related to #127

Context
From an updated install (with #127 fix)
mfronton@lilbox:~$ go get -u github.com/justwatchcom/gopass
mfronton@lilbox:~$ gopass version
gopass HEAD (n/a ) go1.8.3
mfronton@lilbox:/opt/go/path/src/github.com/justwatchcom/gopass$ git describe
v1.1.1-4-g905178c
mfronton@lilbox:~$ rm -rf .config/gopass/ .password-store

What I do
I try to init a store with a custom path : gopass init --store .password-store-custom
What I get
A Failed message is displayed while gopass tries to init the git repo
Please select a private key for encryption:
[0] 0xD385289FA809234F - Matthieu Fronton<EMAIL_ADDRESS>[1] 0x1F475D52C78649B1 -  <>
Please enter the number of a key (0-1) [0]:
Please select a key for signing Git Commits
[0] 0xD385289FA809234F - Matthieu Fronton<EMAIL_ADDRESS>[1] 0x1F475D52C78649B1 -  <>
Please enter the number of a key (0-1) [0]:
Failed to init git: Failed to initialize git: chdir /home/mfronton/.password-store: no such file or directory
Password store .password-store-perso initialized for:

The git init has failed on .password-store and the identity is missing
As I expected the path to be .password-store-custom I believe a first "default" store is required...
So I tried to gopass init first :
mfronton@lilbox:~$ gopass init
Please select a private key for encryption:
[0] 0xD385289FA809234F - Matthieu Fronton<EMAIL_ADDRESS>[1] 0x1F475D52C78649B1 -  <>
Please enter the number of a key (0-1) [0]: 0
Please select a key for signing Git Commits
[0] 0xD385289FA809234F - Matthieu Fronton<EMAIL_ADDRESS>[1] 0x1F475D52C78649B1 -  <>
Please enter the number of a key (0-1) [0]: 0
Initialized empty Git repository in /home/mfronton/.password-store/.git/
[master (root-commit) 2fe8ae7] Add current contents of password store.
 2 files changed, 52 insertions(+)
 create mode 100644 .gpg-id
 create mode 100644 .gpg-keys/CE46FE453E9E935CA68C81D0D385289FA809234F
[master 970cef2] Configure git repository for gpg file diff.
 1 file changed, 1 insertion(+)
 create mode 100644 .gitattributes
Git initialized
Password store /home/mfronton/.password-store initialized for:

mfronton@lilbox:~$ gopass init --store .password-store-custom
Please select a private key for encryption:
[0] 0xD385289FA809234F - Matthieu Fronton<EMAIL_ADDRESS>[1] 0x1F475D52C78649B1 -  <>
Please enter the number of a key (0-1) [0]: 0
Please select a key for signing Git Commits
[0] 0xD385289FA809234F - Matthieu Fronton<EMAIL_ADDRESS>[1] 0x1F475D52C78649B1 -  <>
Please enter the number of a key (0-1) [0]: 0
On branch master
nothing to commit, working directory clean
Failed to init git: failed to commit files to git: exit status 1
Password store .password-store-custom initialized for:
  0xD385289FA809234F - Matthieu Fronton<EMAIL_ADDRESS>
First gopass init is ok, while second one failed with a different message : Failed to init git: failed to commit files to git: exit status 1
What I expected
I first expected the gopass init --store xxx to be allowed without a previous "default" store.
Not sure if this is a bug...
Then following the 2 steps process (without then with --store) I expected the second custom store to be properly initialized.
Also the identity is missing at the end of the first gopass init with the message Password store .password-store-custom initialized for: while it is properly displayed on the second gopass init --store with the message Password store .password-store-custom initialized for:   0xD385289FA809234F - Matthieu Fronton<EMAIL_ADDRESS>

gopass updated
fix confirmed
:+1:

Thanks!

Just noticed the identity is not displayed in the first gopass init...
First rootstore (fail to echo identity):
mfronton@lilbox:~$ gopass init #--store .password-store-perso --alias personel
Please select a private key for encryption:
[0] 0xD385289FA809234F - Matthienou Fronton<EMAIL_ADDRESS>[1] 0x1F475D52C78649B1 -  <>
Please enter the number of a key (0-1) [0]:
Please select a key for signing Git Commits
[0] 0xD385289FA809234F - Matthieu Fronton<EMAIL_ADDRESS>[1] 0x1F475D52C78649B1 -  <>
Please enter the number of a key (0-1) [0]:
Initialized empty Git repository in /home/mfronton/.password-store/.git/
[master (root-commit) f1e8973] Add current contents of password store.
 2 files changed, 52 insertions(+)
 create mode 100644 .gpg-id
 create mode 100644 .gpg-keys/CE46FE453E9E935CA68C81D0D385289FA809234F
[master fd8e1e7] Configure git repository for gpg file diff.
 1 file changed, 1 insertion(+)
 create mode 100644 .gitattributes
Git initialized
Password store /home/mfronton/.password-store initialized for:

Second substore (identity is successfully echoed) :
mfronton@lilbox:~$ gopass init --store .password-store-perso --alias personel
Please select a private key for encryption:
[0] 0xD385289FA809234F - Matthieu Fronton<EMAIL_ADDRESS>[1] 0x1F475D52C78649B1 -  <>
Please enter the number of a key (0-1) [0]:
Please select a key for signing Git Commits
[0] 0xD385289FA809234F - Matthieu Fronton<EMAIL_ADDRESS>[1] 0x1F475D52C78649B1 -  <>
Please enter the number of a key (0-1) [0]:
Initialized empty Git repository in /home/mfronton/.password-store-perso/.git/
[master (root-commit) d08ad54] Add current contents of password store.
 2 files changed, 52 insertions(+)
 create mode 100644 .gpg-id
 create mode 100644 .gpg-keys/CE46FE453E9E935CA68C81D0D385289FA809234F
[master c0fcac7] Configure git repository for gpg file diff.
 1 file changed, 1 insertion(+)
 create mode 100644 .gitattributes
Git initialized
Password store .password-store-perso initialized for:
  0xD385289FA809234F - Matthieu Fronton<EMAIL_ADDRESS>

Sorry but I'm just working on step by step a tutorial for my team, that's why I'm retrying the workflow from scratch again and again...

Your detailed feedback is super helpful. Please keep it going like that!
I'll have a look at the identity issue later.


[netdata] remove duplicate prefixes in local network data

The current implementation attempts to remove existing on-mesh prefix
entry when adding an on-mesh prefix entry with the same prefix. The
same logic exists for external routes. However, the existing code does
not work properly when both on-mesh prefixes and external routes exist
with the same prefix.
This commit simply updates the logic to always remove existing entries
with the same prefix, regardless of whether they are on-mesh prefix or
external route. This is in contrast to trying to keep both on-mesh
prefix and external route with the same prefix simultaneously. There
is no obvious use case for having both the on-mesh prefix and external
route exist at the same time.
Thanks go @gabekassel for identifying this issue.

In what case would a BR adds the same prefix to both on-mesh prefixes and external routes?
One case I can think of is that a BR may learn about the OMR prefix from RA RIO and then adds it to the Extern Routes, thinking that the OMR prefix is

In what case would a BR adds the same prefix to both on-mesh prefixes and external routes?

Manual configuration through CLI or APIs.

prefix to both on-mesh prefixes and external routes?

Manual configuration through CLI or APIs.

In the case I showed Jonathan, it seemed the route was being added by learning it from RIOs sent from our radvd running on the same device. Then, I was separately attempted to configure the same prefix as on-mesh via CLI.


#221 | Wallet page header

Fixes #172
Fixes #221
Description
This PR adds the UI for the wallet page header, as well as routing to send and receive. it adds a new evm chain setting so that other evm chains can set their 'buy more tokens' link in the future
note that I tested large values for the USD amounts (100 million) on small screens, and made sure the text fits without overflowing
Test scenarios

go to https://deploy-preview-224--wallet-staging.netlify.app/
sign into evm

on the wallet page, you should see a UI to match the designs

click Send

you should be taken to a blank send page

click Receive

you should be taken to a blank receive page

click Buy

a new tab should open to the telos buy page

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have cleaned up the code in the areas my change touches
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings
[x] I have removed any unnecessary console messages
[x] I have included all english text to the translation file
[x] I have created a new issue with the required translations for the currently supported languages
[x] I have added appropriate test coverage

Open menu with spacebar or enter, it won't open fully.

Open menu with spacebar or enter, it won't open fully. Close menu with spacebar or enter, it won't.

i see what you mean. I'll make a bug issue for this since its not actually related to the PR


Issue moving elements up/down/duplicating in tree view

Description
Unable to reorder/rearrange form elements within a section
Steps to reproduce

Create new section
Add contact information element
Try to reorder component parts
Nothing happens

Details

Browser: Chrome
Operating system: Mac
Environment: Preview
Language: English
Viewport: Desktop

Expected behaviour
Move when clicked
Screenshots or videos
Private Zenhub Video

Moving elements up / down using "Move up" or "Move down" should be working now --- didn't look at duplicate

Will look at duplicate today.

PR for duplicate https://github.com/cds-snc/platform-forms-client/pull/3727

Tested! Fixed! Thanks!


Undo a Swiped card

First of all, thanks for the awesome library. It is working wonderfully, however, I didn't find any way to undo a recently dismissed card. I want the last dismissed card to be displayed back on a click of a button, if user dismissed it accidentally.
How should I do it?

Sorry, the undo animation is not implemented. If you do not require animation, you can reset elements in your adapter (reinsert discarded content ) and reload it.

Thanks for the quick reply, no animation isn't a big issue. Although, it would be cool to have it. I thought there might be a quick way in the API for this issue, anyhow, thanks again for response and a great API.

+1 would be very cool to have this feature implemented in the future


pull request for e2e test at 01/28/2017 11:56:10

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


[FLINK-3760] Fix StateDescriptor.readObject

Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the How To Contribute guide.
In addition to going through the list, please provide a meaningful description of your changes.

[x] General

The pull request references the related JIRA issue
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message

[x] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[x] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

+1

Thanks for having a look! I'll merge it...

Manually merged


sladeUnstable: unstable-2023-09-30 -> unstable-2024-02-09

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for sladeUnstable is: Doom editor
meta.homepage for sladeUnstable is: http://slade.mancubus.net/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-01-03 in filename of file in /nix/store/m1sza4g4v97jvijbzaagxmljg29fghkq-slade-unstable-2024-01-03

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
sladeUnstable

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/m1sza4g4v97jvijbzaagxmljg29fghkq-slade-unstable-2024-01-03 \
  --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 sladeUnstable https://github.com/r-ryantm/nixpkgs/archive/c78fb40a845f70bc0400e6d782220d48fb0533a9.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/c78fb40a845f70bc0400e6d782220d48fb0533a9#sladeUnstable

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/m1sza4g4v97jvijbzaagxmljg29fghkq-slade-unstable-2024-01-03
ls -la /nix/store/m1sza4g4v97jvijbzaagxmljg29fghkq-slade-unstable-2024-01-03/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 run on x86_64-linux 1

1 package built:

sladeUnstable

Maintainer pings
cc @ertes for testing.

$ /nix/store/60w47qzll0iv9pdi571sz13kymhrhd67-slade-unstable-2024-01-10/bin/slade
sh: ligne1: addr2line : commande introuvable

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for sladeUnstable is: Doom editor
meta.homepage for sladeUnstable is: http://slade.mancubus.net/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-01-13 in filename of file in /nix/store/im0jk6rvkm43lsm4l7admdc44lcc0kw9-slade-unstable-2024-01-13

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
sladeUnstable

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/im0jk6rvkm43lsm4l7admdc44lcc0kw9-slade-unstable-2024-01-13 \
  --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 sladeUnstable https://github.com/r-ryantm/nixpkgs/archive/1cd60357cb5f46230a499c69b0ff56e7c66de57e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/1cd60357cb5f46230a499c69b0ff56e7c66de57e#sladeUnstable

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/im0jk6rvkm43lsm4l7admdc44lcc0kw9-slade-unstable-2024-01-13
ls -la /nix/store/im0jk6rvkm43lsm4l7admdc44lcc0kw9-slade-unstable-2024-01-13/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 run on x86_64-linux 1

1 package built:

sladeUnstable

Maintainer pings
cc @ertes for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for sladeUnstable is: Doom editor
meta.homepage for sladeUnstable is: http://slade.mancubus.net/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found unstable-2024-02-09 in filename of file in /nix/store/zrx188kprwx5qhcn0yq0h6d5w4jwfya1-slade-unstable-2024-02-09

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
sladeUnstable

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zrx188kprwx5qhcn0yq0h6d5w4jwfya1-slade-unstable-2024-02-09 \
  --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 sladeUnstable https://github.com/r-ryantm/nixpkgs/archive/0c00f5eac6bf537308c6d203b546dcea9e6904d6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/0c00f5eac6bf537308c6d203b546dcea9e6904d6#sladeUnstable

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zrx188kprwx5qhcn0yq0h6d5w4jwfya1-slade-unstable-2024-02-09
ls -la /nix/store/zrx188kprwx5qhcn0yq0h6d5w4jwfya1-slade-unstable-2024-02-09/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.
nixpkgs-review took longer than 45m and timed out

Maintainer pings
cc @ertes for testing.

Merge conflict, please open a new PR.


[5.7] Do not emit variants for pages in article-only catalogs

Rationale: Do not emit language variants information for article-only catalogs, so that renderers don't advertise these as being available in "Swift", which not accurate.
Risk: Low
Risk Detail: This is a targeted change that only apply when building article-only catalogs.
Reward: Medium
Reward Details: This only applies to article-only catalogs.
Original PR: #241
Issue: rdar://92758192
Code Reviewed By: @ethan-kusters
Testing Details: Added an automated test to cover the new behavior.

@swift-ci please test


docs: Update getting-started guide

While setting up development environment with zulip-mobile I noticed a few issues in the getting started guide. Taking package.json as reference I've updated the documentation.
Addresses #1905

Looks good! Thanks for the contribution.


Update tools

update tools versions
tidy & vendor
always run fmt AFTER generate: avoids confusion with import aliases
make test: runs generate, manifests, bundle

ECOPROJECT-925

Makes sense to me
/lgtm


build: fix vulnerability (bump eta to 2.0.0)

:tada: This PR is included in version 1.59.1 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Issue699 part5 wake sleep

Minor fix to correctly identify the sleeplog timestamps by g.part5.wakesleepwindows when the amount of nonwear is high and the SPT window then is defined based on the sleeplog. Only occurs when dayborder != 0
Fixes #699

Checklist before merging:

[x] Existing tests still work (check by running the test suite, e.g. from RStudio).
[ ] Added tests (if you added functionality) or fixed existing test (if you fixed a bug).
[ ] Updated or expanded the documentation.
[x] Updated release notes in inst/NEWS.Rd with a user-readable summary. Please, include references to relevant issues or PR discussions.
[ ] Added your name to the contributors lists in the DESCRIPTION and CITATION.cff files.

Codecov Report

Merging #700 (ca9511e) into master (d1afd23) will decrease coverage by 0.00%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master     #700      +/-   ##
==========================================
- Coverage   73.24%   73.24%   -0.01%
==========================================
  Files          87       87
  Lines       10751    10753       +2
==========================================
+ Hits         7875     7876       +1
- Misses       2876     2877       +1

Impacted Files
Coverage Δ

R/g.part5.R
73.79% <66.66%> (-0.07%)
:arrow_down:

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


Medical imaging example

@IsaacYangSLA can you review this PR please? Thanks!

@gheinrich , you are welcome.  Yes, I will review it.

@gheinrich , thanks.  I think it's good to merge this PR.

@lukeyeager , I think we don't have to test it since it worked in the lab.  Reading Greg's codes is like reading a masterpiece, so I believe no problem on the coding side.  Should we merge it?


fix: Modal=false behaviour in FluentDialog

🐛 Bug Report
If you set Modal=false in a FluentDialog, you still cannot interact with any controls or components outside of the dialog.
💻 Repro or Code Sample
See the first example at https://www.fluentui-blazor.net/Dialog.  Clear the Modal and Trap Focus checkboxes and display the dialog.
🤔 Expected Behavior
If "Modal=false", you should be able to interact with all other controls and components on the page; same as the behaviour of a non-modal dialog in a desktop application.
😯 Current Behavior
You cannot interact with anything else on the page except the dialog.
🔦 Context
The use-case where I encountered this was: displaying a side-bar of usage hints in an editor page.  I wanted the user to be able to leave the sidebar up as reference while using the editor.  I expected DialogService.ShowPanelAsync() to do this for me.  I will probably have to re-implement the help panel as a hidden div within the editor page instead.
🌍 Your Environment
Windows 11, ASP.NET 8.0 WebAssembly application.
FluentUI 4.10.2
Chrome Version 131.0.6778.140

When 'Modal' is checked, the dialog can be dismissed by clicking outside of the dialog.
You can't use a dialog to display content while still allowing you to manipulate elements in the “layer” below. And from an ergonomic point of view, I don't think this is a good idea.


Update setdex

Some CAP analyses are now on the main Smogon dex, so those CAPs now have their sets ripped and are mixed in with the rest of the Pokemon. The CAPs still at the bottom of the list don't have analyses yet and can still be manually updated.

Can you fix the Travis error?

Sorry about that. Fixed.


Support for host:container:protocol

Marked as fixed in #158 but I still get the same error.
Definition in docker-compose file:
ports:

<IP_ADDRESS>:15000:15000/tcp
<IP_ADDRESS>:15001:15001/udp

FATA[0000] "agent" failed to load ports from compose file: invalid host port "<IP_ADDRESS>:15000:15000/tcp"
root@350035d7afc9:/compose# kompose -v
kompose version 0.1.2 (92ea047)
Let me know if I'm missing something.

@OguzPastirmaci
Yup. This looks like an error, we're testing against:
- "5000:5000/tcp"

but
- "<IP_ADDRESS>:5000:5000/tcp"

doesn't work and this:
test/fixtures/ports-with-proto  master ✗                                                                                4h34m ⚑
▶ kompose convert
FATA[0000] "web" failed to load ports from compose file: invalid host port "<IP_ADDRESS>:5000:5000/tcp"

errors out.

Hey @ngtuna @kadel
Adding IP mapping via the port makes the most sense in regards to mapping to ClusterIP / LoadBalancerIP.
Would make things awesome in regards to scenarios of specifying certain IP addressing for each service.
Here's an example:
services:
    web:
      image: tuna/docker-counter23
      ports:
        - "<IP_ADDRESS>:5000:5000/tcp"
      links:
        - redis
      networks:
        - default

Converts to:
    {
      "kind": "Service",
      "apiVersion": "v1",
      "metadata": {
        "name": "web",
        "creationTimestamp": null,
        "labels": {
          "service": "web"
        }
      },
      "spec": {
        "ports": [
          {
            "name": "5000",
            "protocol": "TCP",
            "port": 5000,
            "targetPort": 5000
          }
        ],
       "clusterIP": "<IP_ADDRESS>",
        "selector": {
          "service": "web"
        }
      },
      "status": {
        "loadBalancer": {}
      }
    },

Does this make sense?
Or should we warn the user instead that it's not supported?

@cdrage Does docker-compose have that kind of port format ? And is that a real use-case user want to have a fixed IP address for k8s service clusterIP ?

@ngtuna Yes, the definition in a Docker-Compose file uses the ip:port:port format. Fixed IP address in a cluster is necessary if you have a pool of IP addresses.

Yeah I didn't notice that format. Can we warranty reusing that IP address for k8s clusterIP will work ? I remember when setting up k8s cluster, a clusterIP range is defined. I would suggest while accepting that port format we shouldn't set the clusterIP address.

I would suggest while accepting that port format we shouldn't set the clusterIP address.

@ngtuna :+1:

Shouldn't this IP address map to hostIP in ContainerPort?

@kadel You're right. That'd be a better place to put it.


How do I set the rotation and layer thickness buttons not to show in the CrosshairsTool tool

What feature or change would you like to see made?

At present, only layer thickness can not be displayed, but the rotation configuration seems not to have?
Why should we prioritize this feature?
At present, only layer thickness can not be displayed, but the rotation configuration seems not to have?

do you mean they are off or they are invisible?

I want to control whether to use thickness and rotation
@sedghi

I want to control whether to use thickness and rotation.
But now the rotation doesn't seem to have a configuration item
@sedghi

We will revamp the crosshair tools soon and we will add this option


[Refactor][backend/core] Show direct error message for users.

What and why to refactor
caused by: Error running task 16998. (400)
        Wraps: (2) error preparing task data for jenkins (400)
        Wraps: (3) fail to get transformationRule (400)
        Wraps: (4) record not found

Now error messages are not readable for users. Because it's difficult to write more user-friendly tips in the backend. The detail message have been wrapped.
Describe the solution you'd like
show the inner message to users.
caused by: fail to get transformationRule  ← show for users
        Calls: (1) Error running task 16998. (400)
        Calls: (2) error preparing task data for jenkins (400)
        Calls: (3) -
        Calls: (4) record not found

Split wrap to 2 functions wrap and as. use as to recognize which error is. use wrap to record where errors pass by.

This sounds like the "user error" vs "developer error" feature I proposely several months ago.

Do you mean this one https://github.com/apache/incubator-devlake/issues/3068? Maybe we can close one.

@Startrekzky No, we only discussed it verbally. In the original design of the current error handling framework I was distinguishing between "user-errors" (which would make it to the UI and backend logs) and "dev-errors" (only in backend logs). It sounds like this is a use case for that.

This is a long-existing issue that needs to be tackled in the future.


Explore using a database to store the bookmarks

The current implementation simply caches the bookmarks in a flat file. This makes more complex query operations difficult to achieve, and gets in the way of adding functionality like searching by page contents, deriving additional data, etc. We should explore using something like CoreData or SQLite to store the data.

It doesn't make sense to prioritise this over some of the other usability issues (e.g., a first-run wizard, Sparkle updates, etc). Pushing to Future.

Done.


Make the build reproducible

Whilst working on the Reproducible Builds effort [0], we noticed
that node-promise could not be built reproducibly as it uses
random numbers as throwaway identifiers.
This patch uses determinstic numbers instead.
This was filed in @Debian as https://bugs.debian.org/886277
[0] https://reproducible-builds.org/
Signed-off-by: Chris Lamb<EMAIL_ADDRESS>

Making it possible to verify our build, I would support, but this doesn't do that.

Hm, I think one of us has some confusion about the goal of reproducible builds. Indeed, this change would surely make it possible to verify your build, ie. from the same sources we get the exact same outputs. :)

No. This change would make it possible to verify a build, but not our build. We wouldn't be setting the SOURCE_DATE_EPOCH environment variable, so you wouldn't be able to reproduce our build. What you're asking for is the ability to create a build that can be verified, which is pointless unless we are going to create a verifiable build. There's never any point being able to verify your own build in this way.

This change would make it possible to verify a build, but not our build

True, and apologies as I now see you already wrote that. However I would disagree with

There's never any point being able to verify your own build in this way.

.. in that downstreams (eg. Debian) are building this library and distributing binaries/builds of it. There is great value in being able to reproduce this result.

Debian should not be building this library from source. It is a waste of electricity and time. I am happy to make a firm commitment to never helping them do something that wasteful.

Debian should not be building this library from source

Please could you elaborate why in more detail? Debian is a free software distribution - simply using upstream's provided artefacts as-is does not align with our goals of letting our users (or downstream distributions) make modifications to the code which — naturally — requires that binaries are built from their sources.

@ForbesLindesay how can someone be sure that the build he has is from you and not altered by a third party if it's not reproducible from sources?

@P-EB Exactly, if @lamby was asking us to make our build reproducible, that would be fine. That would allow him to verify our published build against our sources. What @lamby is asking for does not let him reproduce our build. It lets him create a separate, reproducible build. This has no value.

Please could you elaborate why in more detail

This is already open source software. If people want to modify our promise implementation, they can fork it here, publish a new package, and build a fork of debian that points at that forked promise implementation. This is already how the entire node ecosystem works.
Modifications require that it is possible to go and build something from source, doing so if you're not making modifications is pointless.

I grant the distinction between your builds and the builds of others, but putting aside the issue of validating  that your published build matches its sources, I'm afraid I simply don't follow why you think reproducing a separate build is of no value. :)

It lets him create a separate, reproducible build. This has no value.

Should your build be reproducible then this question wouldn't exist at all. The fact that it isn't also means that someone taking your blobs and your codebase can't verify that everything went well.
So, may we agree that there is an issue in the current situation of your codebase that requires to be fixed by putting deterministic identifiers (the fact that they change across releases is something simple to achieve)?

@P-EB Yes, as I've always maintained, I'm happy to accept a pull request that has this outcome. I have rejected this one because it does not.
@lamby I'm tired of trying to explain this. The burden of proof is on you to provide an example of a benefit that results from being able to create a reproducible build of a library, but not being able to reproduce the official build. It is not an end unto itself; you must provide an example of a positive benefit to this.  I cannot conclusively prove it is useless, because there could always be a use case that I have yet to think of, but I haven't been able to come up with one, and you've had plenty of time and opportunity to provide one. You are asking me to review, and then maintain, code that does something that I see no evidence needs doing.

I'm missing something then as, to me, the use case has been explicit and implicit throughout the PR - Debian is shipping this library, building it from source. (Not that it makes much difference but FYI you certainly hold the minority opinion in the free software community on this :p.)

you certainly hold the minority opinion

I doubt it: npm had 753,071,751 downloads in the last day and almost no npm packages are set up to build from source on download.
This package alone had 586,003 downloads in the last day, none of those will be building from source, because if they were they would get it from GitHub.
As I've said:

Debian should not be building this from source.
The reason for wanting Debian builds to be reproducible is the same as the reason for wanting Promise builds to be reproducible - i.e. it lets people verify that you're not sneaking backdoors in by building from different source to the open source code. Despite this, you don't seem interested in solving that issue for the Promise library. You seem only to be interested in your very narrow use case, that could be better solved by simply using the pre-built code like 99.99% of users or this package.

I will accept a well written pull request to make our build reproducible, but I'm going to lock this issue as debating with you is not a productive use of anyone's time.

I feel decently sure that we're not going to get Debian to change their policy (nor do I feel they should), and we could quite reasonably derive SOURCE_DATE_EPOCH ourselves if we wished to — I work on nixpkgs myself, and we set and rely on SOURCE_DATE_EPOCH since it is a de-facto standard for reproducible builds. On the nixpkgs end, we have no particular interest in reproducing anyone else's build either, just ensuring that running the same build twice always produces the same output.

Verifying our build has broad benefits, it lets you verify that the build everyone is using is correct. Building from source for yourself only verifies your own personal build.
Re changing Debian's policy - just because I can't fix what they're doing doesn't mean I have to support it. They're not paying me so I have no obligation to help them and I believe the approach they are taking is wasting people's time and computing power.
If this pull request included code to set SOURCE_DATE_EPOCH then I probably would have accepted it.


scanner: correct the autoProvision mechanism

- we should not set both `Spec.Filesystem.Provisioned` and
  `Spec.Provision` or the remove operation would be blocked if
  we only change one of these to false.

This is a side-effect that comes from 1877a4ef1743e4bb01b81179aacfe5b32da059ed.
For now, we will remove one of these two fields to ensure the delete operation
work. We still need mutator to help convert these two fields.

Problem:
The removal operation would be blocked if we only changed one of these to false.
Solution:
For now, we will remove one of these two fields to ensure the delete operation work.
Related Issue:
Test plan:

The CI will fail because the autoProvisioned behavior will be called on the current master code.

Shouldn't we remove bd.Spec.FileSystem.Provisioned = true and keep bd.Spec.Provision instead?
Also, there's another instance of this where we set both to true in updateDeviceStatus() in pkg/controller/blockdevice/controller.go

Shouldn't we remove bd.Spec.FileSystem.Provisioned = true and keep bd.Spec.Provision instead?

Both are ok to me.
I would like to keep bd.Spec.FileSystem.Provisioned = true because I want to align with the test case.
The current integration test still targets this field.
I am working on the mutator. After that, we can move the whole Spec.FileSystem.Provisioned to Spec.Provision
WDYT?

Also, there's another instance of this where we set both to true in updateDeviceStatus() in pkg/controller/blockdevice/controller.go

Nice catch, updated!

I am working on the mutator. After that, we can move the whole Spec.FileSystem.Provisioned to Spec.Provision
WDYT?

Cool, makes sense.

@mergifyio backport v0.7.x


Accessibility

The platform specific changes basically tell the OS that the GestureFrame is a button. So the OS will then treat it as a button from an accessibility POV.
New property added called AccessibleName, this allows the user to manually set the accessible name, if not set it will default to the Text property value
Haven't done UWP, sorry

Hi @IeuanWalker, thanks a lot for that addition! Will review ASAP. One question: Did you actually change anything in the .xaml and .csproj and .sln files? Looks like you are using a different formatter and there are A LOT of code changes in these files. Would be easier to review, if I knew, what ACTUALLY changed!

No prob, ye sorry about that.
I never touched the  '.csproj' and '.sl' files.
The only .xaml file i changed was the FlexDemoPage on line 83 i added AccessibleName="Light bulb" to test the new property.

Released in 0.14.0. Thanks for the meaningful addition!


Microsoft SQL Server (MSSQL) scaler implementation

This PR adds a built-in scaler that uses a Microsoft SQL Server (MSSQL) database as the event source. It's very similar to both the existing mysql and postgresql scalers and is intended to work with both self-hosted SQL Server databases and SQL Server databases hosted in managed clouds.
Documentation PR: https://github.com/kedacore/keda-docs/pull/367
There is still more work to do on this PR, which is tracked in the checklist below. This also includes end-to-end testing. However, I wanted to open it early to hopefully get some early feedback since this is both my first contribution to KEDA and my first time writing code in Go (besides hello world). Feedback is greatly appreciated. 🙏🏽
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Unit tests have been added
[ ] End-to-end tests have been added
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[x] A PR is opened to update the documentation on (repo) (if applicable)
[x] Changelog has been updated

Fixes #674

@cgillum Can we mark the PR as ready for review or is there any upen work?

@tomkerkhove still working on putting together end-to-end tests for this one. I'm learning as I go (first time deploying a real k8s cluster), so apologies for the delay.

Oh no worries at all! I was just checking if you were waiting on us or not!

@cgillum can't help you but you have my moral support to finish your e2e test :) this scaler would be great to have

@tomkerkhove and @ahmelsayed, I was able to complete my e2e testing successfully and I think this PR is ready to go. Would it be okay to defer the authoring of the e2e test for another PR or should that also be part of this PR?

@cgillum yes that's fine, e2e test can come in a separate PR

I ended up getting an end-to-end test working sooner than I thought, so I went ahead and added it to this PR in my latest iteration. It's basically the same as the mysql test with a few tweaks and simplifications. Please let me know if the way that it is written is acceptable, especially regarding the dependency on my docker hub test container image.

If you have a test container, we could host it on our test container repo if you want?

It probably makes more sense to eventually host it in a KEDA-specific container repo so that I don't accidentally break anything in the future. That said, this doesn't have to happen right away. We could move it as part of a separate PR once we know that the nightly tests are stable.

Sure thing, no worries! Will wait for @ahmelsayed his review.
Thanks!


In some cases, Netbeauty2 may cause the same dll to be loaded multiple times

https://user-images.githubusercontent.com/9072328/223904381-0b1528ea-b4c7-4959-9d3f-31783faa25ae.mp4
MyTests.zip
1.TestLibs is a public library that is referenced by other projects.
2.TestPlugin, simulation plug-in dll, dynamic loading, direct reference to TestLibs
3. TestConsoleWithRef directly references TestLibs and uses NetBeauty for directory optimization
4.TestConsole, load TestLibs through Assembly.LoadFile and call its methods.
When running with TestConsole, you will see TestLibs.dll loaded twice.
It's not clear to me if this is expected, if Assembly.LoadFile must be used to briefly reference TestLibs, is there a solution to this problem?

i can't reproduce it even do everything exactly the same as the video, but after analyzing the project structure, but i guess here should be what things happened

TestConsole and TestConsoleWithRef are one with NetBeauty and one without NetBeauty
after building entire solution, both two projects files are mixed into the same output folder
running the ncbeauty post build task, it will search every single *.deps.json and *.runtimeconfig[.dev].json and process them, so TestConsole is beauty unexcpedly too.
ncbeauty injects a STARTUP_HOOK calls nbloader which will add a resolver to the default AssemblyLoadContext.
TestLibs also adds a resolver to the current AppDomain
TestLibs was loaded twice in somehow

btw:
the project structure is kind of wired, TestConsole is trying to load the TestLibs and TestLibs is trying to load the TestPlugin and TestPlugin is referencing the TestLibs.
ps:
NetBeauty has the concept of project since it is a msbuild task, but ncbeauty hasn't unless treats every different *.deps.json as a different project, but this behaviour should treat as a BUG.

you can post a copy of debug build bins with pdb so i can have a deep look.


fix all json syntax error in error api spec

You need to sign your commits as per the contribution guide.

Codecov Report
Base: 57.43% // Head: 57.38% // Decreases project coverage by -0.04% :warning:

Coverage data is based on head (0bd498a) compared to base (3413bf8).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3724      +/-   ##
==========================================
- Coverage   57.43%   57.38%   -0.05%
==========================================
  Files         105      105
  Lines       10839    10839
==========================================
- Hits         6225     6220       -5
- Misses       3930     3934       +4
- Partials      684      685       +1

Impacted Files
Coverage Δ

registry/handlers/app.go
47.65% <0.00%> (-0.69%)
:arrow_down:

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

You need to sign your commits as per the contribution guide.

done


Delete note

Per PM<EMAIL_ADDRESS>we need to delete the Note near the top of the page that states "This cmdlet is being replaced by the Get-MyAnalyticsFeatureConfig cmdlet." We'll need the same change in the Set-UserBriefingConfig topic (https://docs.microsoft.com/en-us/powershell/module/exchange/set-userbriefingconfig?view=exchange-ps).

Docs Build status updates of commit e4d18ef:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit e4d18ef:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 658fae1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 658fae1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-UserBriefingConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Implement recurring reminders

Every day, week, month etc

DueDate and DueTime should be looked over, or rather there should be a better representation of the "Next Notification" for recurring reminders. If the reminder is recurring but the first DueDate is passed, it should not show as such in the list.
The list should show frequency/interval of reminders, and the next time it occurs.


react-native init  error

node-gyp rebuild

CXX(target) Release/obj.target/validation/src/validation.o
SOLINK_MODULE(target) Release/validation.node
ld: library not found for -lgcc_s.10.5
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [Release/validation.node] Error 1
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:269:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1074:12)
gyp ERR! System Darwin 14.5.0
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"

Hi there, check this issue out: https://github.com/nodejs/node-gyp/issues/675
The important line is: ld: library not found for -lgcc_s.10.5
Make sure you have the proper version of Command line tools installed from Xcode


Add support for in clause

Is it possible to add support for in clause so that following queries can be executed
select * from some_table where some_column in (@ColumnValues)

select * from some_table where some_column = any(@ColumnValues)

I guess first question is whether ado.net supports it?  If the underlying driver can somit, should be possible with the type provider
Darren

Am 09.09.2019 um 08:05 schrieb kerams<EMAIL_ADDRESS>select * from some_table where some_column = any(@ColumnValues)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@kerams - =any works. Thanks, will close this ticket.


Accepting input character "e" for numeric values

Actual Results
The system allows to enter character "e" for the numeric vital information but does not allow to proceed and doesn't show any message.
Expected results
The system should allow only numeric values and display a message when the validation fails.
Steps to reproduce
Login to POC-> Select the vitals module-> search for a patient-> Clicck Add under clinical services
Screenshot/Attachment (Optional)
A visual description of the unexpected behaviour.

 Accepting input character "e" for numeric values


Add Prism as an NPM module

I've been using this snippet to get it working with Node on Windows:
prism.js
var exec = require('child_process').exec;

// Get the swagger json/yaml file passed in as an arg
var swaggerEndPoint = process.argv[2];

if(!swaggerEndPoint){
    console.error("No swagger endpoint given");
    return;
}

var prism = exec('prism_windows_386.exe run --mock --list --spec ' + swaggerEndPoint);

prism.stdout.on('data', function(data) {
    console.log(data);
});

and they use it with node like: C:\>node prism http://petstore.swagger.io/v2/swagger.json
Which works fine but I obviously need prism_windows_386.exe checked into source control. It would make this infinitely more usable if prism could just be installed via npm and used like a regular module.

Hmm, interesting!  Do you actually want to use Prism in a project, or do you want to just install it easier on windows? If you want to use it in projects, what for?

I'd like to be able to use it in project, specifically for mocking a not-yet-ready endpoint and for day-to-day development and testing.
E.g. a Swagger spec is created by the back-end team asap; with an actual, usable API endpoint based on said spec to come at a later date.
The front-end team takes the swagger spec and builds the various models and services they need and use Prism to run a mock server for dev work and running integration/e2e tests against.
Having Prism as an installable npm module would make this process easier for the front-end guys, as node and npm are the foundation for everything front-end related these days e.g. dev dependences, package management, build etc.

@pytlesk4 great stuff. Look forward to seeing what you guys come up with.

Hey, sorry this hasn't been updated for so long! The Prism v3 JavaScript (TypeScript) rewrite has been underway for a good amount of time now, and is approaching an alpha release.

Click this for updates!

So assuming that means installing via npm will also be included?

Yup!


Minor incongruences

When you create a paste:

no matter if you specify public or private, it always goes to the private pastes

no matter if you specify "burn" true or false, it always returns "false" (although I'm not sure what difference there should be)

the title you specify is ignored

Audit log is mostly empty

All of these were fixed in version 1.2.3. :1st_place_medal: to you for reporting these.
As a token of appreciation, I added a new section of contributors/thank you and listed you under it.
https://github.com/dolevf/Damn-Vulnerable-GraphQL-Application#contributors


Depth and color frames have different resolutions

Required Info

Camera Model
D435

Operating System & Version
Win 10

Language
C++

Hello,
I am trying to save depth and color image separately. To do so I first get the depth and color frame, and retrieve their intrinsic information (depth, width, bit per sample...)
		rs2::pipeline p;
		rs2::config c;
		c.enable_device(serial_number);
		// Start the pipeline with the configuration
		rs2::pipeline_profile profile = p.start(c);
		auto frames = p.wait_for_frames();
		auto depth = frames.get_depth_frame();
		auto color = frames.get_color_frame();
		int widthC = color.get_width();
		int heightC = color.get_width();
		int widthD = depth .get_width();
		int heightD = depth.get_width();

I noticed that the depth resolution is 1280 * 720, which seems normal and coherent with what we get with realsense viewer, but the color one is 640 * 480. How could I do so that depth and color have the same resolution? Could I have the color frame in 1280 * 720?
Thanks and regards,
Emmanuel

You can select resolution via c.enable_stream(RS2_STREAM_COLOR, w, h, RS2_FORMAT_RGB8, 30)

Ok thank you. Is it the instrinsit resolution of the RGB camera, or in this case the image would have been resized by the lib?
Thank you,
Emmanuel

This would re-configure the hardware (not a software resize)


Looping sounds are crashing on iOS

More details:
http://community.openfl.org/t/ios-audio-loop-crash/8796/2

Fixed by https://github.com/openfl/lime/commit/a02382d7ba46b99c224c90e80d847101dcbd487b


Re-enable power-assert

power-assert is disabled in https://github.com/almin/almin/commit/2aa3d804e3081a6e82783621417bb5196ebafee0 to port src/ to TypeScript quickly.
At now, we can try to re-enable it.

related issues

https://github.com/almin/almin/pull/68

Remove babel from the packages/almin.
This issue will be closed.


Combine source maps.

So, if one were to run a preprocessor and generate many source maps, it's trivial to concat and minify the generated css files into a single file. Due to the data structures involved in working with source maps, on the other hand, doing the same for source maps is an entirely different story.
We have a couple options-- that I am aware of-- for combining source maps.

combine-source-map is a likely well-put-together solution for combining source maps, with a nice API. It just needs to be configured correctly, especially with regards to offsets.

There's also the sections property of the native source map specification. To my knowledge, it's not compatible with all browsers. More investigation of this option might be warranted.

There's the additional complication of the API. We need to be able to pass .css/.map pairs to the library. I think that takes place here?
In addition, we may want to include some API property for providing a means of altering the paths delivered in the final sourcemap.
Is anyone currently investigating this, and does anyone have any suggestions or input?

Just for the record: I'm interested into a solution for this as well.

@tobiastom stay tuned for updates!

@cryptoquick @tobiastom It turned out to be easily doable when passing a hash to minify method - see the last example https://github.com/jakubpawlowicz/clean-css/blob/master/README.md#using-api
Please feel free to give it a try!

That's awesome! We'll be needing this feature again soon, so I'm glad it's here now. When we go to implement it, I'll let you know how it works. :+1:

Great, looking forward to any feedback.


feat: Transaction sender bot

Adds a new package @aztec/bot that sends txs at regular intervals. The bot idempotently deploys a schnorr account contract and a token contract and mints funds to its own account, and sends a tx with a configurable number of private and public transfers.
Next steps are wiring this to aztec start and exposing a simple http interface for management.
See #7562

Benchmark results
Metrics with a significant change:

avm_simulation_time_ms (Token:assert_minter_and_mint): 86.1 (+63%)
avm_simulation_time_ms (Token:_increase_public_balance): 15.7 (-53%)
protocol_circuit_witness_generation_time_in_ms (base-parity): 306 (-57%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,715
1,551
708
737 (-3%)
767 (-1%)

proof_construction_time_sha256_30_ms
11,719 (-1%)
3,151 (-1%)
1,411
1,438
1,459 (-1%)

proof_construction_time_sha256_100_ms
43,630 (-1%)
12,014 (+1%)
5,434
5,397
5,356

proof_construction_time_poseidon_hash_ms
78.0
34.0
35.0 (+3%)
58.0 (-2%)
88.0

proof_construction_time_poseidon_hash_30_ms
1,517 (-1%)
416
200
219 (-6%)
269 (-1%)

proof_construction_time_poseidon_hash_100_ms
5,611 (-1%)
1,511 (-1%)
681
746 (+1%)
739 (-2%)

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
708
708
708

l1_rollup_calldata_gas
6,588
6,584
6,600

l1_rollup_execution_gas
583,050
583,197
583,364

l2_block_processing_time_in_ms
760
1,408 (-2%)
2,718

l2_block_building_time_in_ms
10,270 (-1%)
20,457 (+2%)
39,447 (-1%)

l2_block_rollup_simulation_time_in_ms
10,269 (-1%)
20,457 (+2%)
39,447 (-1%)

l2_block_public_tx_process_time_in_ms
8,579
18,523 (+2%)
37,475 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
6,970 (-3%)
9,860 (-1%)

node_database_size_in_bytes
12,759,120
16,908,368

pxe_database_size_in_bytes
16,254
26,813

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Function
time_ms
bytecode_size_in_bytes

GasToken:_increase_public_balance
99.4
13,790

GasToken:set_portal
11.3 (+6%)
3,339

Token:constructor
123
23,692

FPC:constructor
93.8
13,592

GasToken:mint_public
82.1
10,158

Token:mint_public
267
19,034

Token:assert_minter_and_mint
:warning: 86.1 (+63%)
12,925

AuthRegistry:set_authorized
47.7 (+2%)
7,812

FPC:prepare_fee
258 (-9%)
11,068

Token:transfer_public
39.1 (+2%)
44,012

FPC:pay_refund
75.3 (-28%)
15,961

Benchmarking:increment_balance
1,009 (+1%)
11,281

Token:_increase_public_balance
:warning: 15.7 (-53%)
15,006

FPC:pay_refund_with_shielded_rebate
130 (-2%)
17,056

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
0.154 (-3%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.5
16.8 (-1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.7
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.607
0.517 (-1%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
48.5
76.1
131 (+1%)
245 (-2%)
471

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.496
0.467
0.451
0.444 (-1%)
0.440

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
60.2
111 (-1%)
183
352 (-1%)
695

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
355
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.509
0.499 (-1%)
0.484
0.477 (-1%)
0.476

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
73.1
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
133
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.520
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
77,362
668,542

Transaction size based on fee payment method
| Metric |  |
| - |  |

How does this wire up to the devnet?

I was planning on adding it to the tf templates as a next step!


arm: nxp: mpu: Consolidate k64 mpu regions

Reduces the number of mpu regions statically reserved at boot time by
one, giving a total of five. We originally sought to reduce the total to
three: 1 background region with lowest precendence for supervisor r/w, 1
flash region, and 1 sram region. However, the nxp mpu hardware does not
give precedence to any region over another, and thus we cannot revoke
access from the background region with a higher priority region. This
means we cannot support hardware stack protection with a single
background region.
Instead, create two background regions that cover the entire address
space, except for sram.
Signed-off-by: Maureen Helm<EMAIL_ADDRESS>Fixes #7705

Codecov Report

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

@@           Coverage Diff           @@
##           master    #8809   +/-   ##
=======================================
  Coverage   52.34%   52.34%
=======================================
  Files         195      195
  Lines       24723    24723
  Branches     5139     5139
=======================================
  Hits        12941    12941
  Misses       9708     9708
  Partials     2074     2074

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 0aedf8d...651cf16. Read the comment docs.


Add @belfz to the team! \o/

:tada: :balloon: :tada:

🎉

🥥

Yay, hi guys! 🦀
Let me introduce myself briefly: I'm primarily a JavaScript/TypeScript developer, currently working at SoftwareMill, which is polish, 100% remote, flat-structure, ~40 people company. I've been playing around with Rust for over a year now & in the meantime I already had a small contribution to the community - I created the VSC search crates.io plugin!
See you around!

Awesome! Welcome to the team :)

Welcome @belfz

I think there's a little table layout issue on the page - I fixed it in #379 :)


run java .class file with external library .jar in golang os/exec

What version of Go are you using (go version)?

$ go version is go1.13.4 windows/amd64

Does this issue reproduce with the latest release?
i'm not sure if it's an issue or not,
i just need to know if i can run this command

java -cp .;"lib/calc.jar" Hello
it is working just fine with cmd or bash

What operating system and processor architecture are you using (go env)?
windows 10  64
go env Output
$ go env

What did you do?
func command(arg ...string) (string, error) {
out, err := exec.Command("C:/Program Files/Java/jdk-13.0.1/bin/javaw.exe", "-cp .;"lib/calc.jar" Hello", arg[0]).Output()
if err != nil {
return "", err
}
return string(out), nil
}
this is were i got an error
out, err := exec.Command("C:/Program Files/Java/jdk-13.0.1/bin/javaw.exe", "-cp .;"lib/calc.jar" Hello", arg[0]).Output()
this line is working fine but without icluding extrnal library in java code
out, err := exec.Command("C:/Program Files/Java/jdk-13.0.1/bin/javaw.exe", "Hello", arg[0]).Output()
What did you expect to see?
i expet it run
What did you see instead?
command:  exit status 1

The Go project doesn't use the issue tracker for questions. See https://golang.org/wiki/Questions.


Proposed rewrite of edit history migration

This pull request effectively restructures https://github.com/zulip/zulip/pull/21122 to drop the JSONB migration, which I think adds too much complexity. A few pieces are substantially rewritten. Notable changes include:

Trying to use edit_history_event consistently as our loop variables for edit history events.
Avoiding database queries in a loop in the migration by fetching the Recipient data in the original Message queries.
Introducing an APIEditHistoryEvent type; not sure if this is worth it but it helped me think through the changes clearly.
Creating a clear set of checkpoint commits which if applied in production in series should avoid there ever being a state where the application isn't fully functional.

@laurynmm it'd be great if you can review this, reintroduce the tests I didn't copy over (I think I moved almost every other block of code, but it's unfortunately probably pretty annoying to do diffs because I renamed a lot of variables), and fix all the bugs that I likely introduced.  I think the commit structure/approach here should work and feel good about the plan of doing this sort of migration separate from the JSONB change, but it's essentially untested and probably some commits fix mypy too.

This was merged via #21309.


[Enhancement] When UTM Crashes, the next time the user launches it, a message box about UTM crashing.

So, I've often heard crash problems in the issues section, so I came up with an idea, when UTM crashes, the next time the user launches UTM, a neat message box will be displayed to the user similar to this:

or if it's impossible to view the crash log, then here's the message box instead:

(sorry if the way I draw the message box looks bad, I don't know how else I can draw it.)
"How can the crash log be sent?" you may ask,
once the "Send anonymous crash log" button is clicked, a github bot (may be created by you) will create an issue in a separate repo that no one has access to but you and the bot.

bot's crash log sender issue
Title of the issue: [crash log file name here]
issue poster:
[crash log here]

You may be like: "but sometimes, utm always crashes or doesn't start when clicking on the icon"
well then, unfortunately users have to manually create an issue about that crash.
I know this may be impossible, but this is just an idea maybe you can implement later, thanks.

This may be possible with testkit but I don’t know if it works for side loaded apps.

UtmAppIsACommentDeleter

UtmAppIsACommentDeleter

and @IIWare your such a šêx êâtêr go have šêx with osy NOW 8====D sucker!!!!!! >:( >:(

and @IIWare your such a šêx êâtêr go have šêx with osy NOW 8====D sucker!!!!!! >:( >:(

@cuj Actually I think a Discord Bot would be wayyyy better if the developers know how to code JS/NodeJS


Select element by name

I'd like to select all elements named apple. Doesn't seem to be possible with the current dasel.
...
<food>
  <tart>
    <apple color="yellow"/>
  </tart>
  <pie>
    <crust quality="flaky"/>
    <filling>
      <apple color="red"/>
    </filling>
  </pie>
  <apple color="green"/>
</food>
...

In XPath it would be .//apple
https://stackoverflow.com/questions/15077462/xpath-to-select-all-elements-with-a-specified-name

Hi @abitrolly,
Thanks for your question.
You are correct in saying this isn't currently possible with dasel. It is however a feature I've been thinking about and this gives me the motivation to push forward and implement it.
I've created a more detailed feature request for a more generic search selector here: https://github.com/TomWright/dasel/issues/40
Please review it and provide any feedback you may have. I'll start implementing it soon and expect to have a first working version in the next couple of days.


build error

/node_modules/vite-plugin-monaco-editor/dist/index.js:94
throw err;
^
[Error: EEXIST: file already exists, mkdir '../dist/monacoeditorwork'] {
errno: -17,
code: 'EEXIST',
syscall: 'mkdir',
path: '../dist/monacoeditorwork'
}
npm run build error

#18

Thanks for you pull request. The version v1.0.9 has update your fix!


Request content missing

Problem Description
I've look through the web without finding a working solution (including stackoverflow). I've try to increase body_size_limit and stream_large_bodies to 10gb but nothing has changed. Any ideas ?
Steps to reproduce the behavior:

Throw a request with "big body"
Get "Request content missing." or "Response content missing."

System Information
mitmdumb.exe --version (can't find mitmproxy) :
Mitmproxy: 5.3.0 binary
Python:    3.7.9
OpenSSL:   OpenSSL 1.1.1h  22 Sep 2020
Platform:  Windows-10-10.0.18362-SP0

You didn't really include clear steps to reproduce it. So I'm throwing this one out: are you waiting long enough? Mitmproxy needs to download the full body before you can see/use it. Depending on your connection and the file size this might take multiple minutes.

@Forium777 curious, did you ever resolve this? I'm having the same issue


fix make file to run unit tests

I am a bit confused about the need of this PR. I was under the impression that: "tensorflow and not (integration or example)” would take care of ignoring the integration-tests? We automatically mark the integration tests as integration using pytest-markers here. Is this not working?

Yeah, the integration tests were running on all PRs for a bit. Not sure if that's still the case though.

rerun tests

rerun tests

rerun tests

rerun tests

rerun tests

Looks like the markers are not correctly configured for the integration tests.
I've created a change here to simplify the marker creation and fix the integration test marking. #510

@jperez999 I don't think this is necessary after @oliverholworthy's fix in #510


Electron Process doesn't close on X in windows

This was done on Windows 10 64-bit.
I downloaded the latest binary (1.2.3) and started up yakyak.  I then closed it via the 'X' at the top when the sign in with your google account screen came up.  After that, I tried to open it again and it complained that a lock file was currently in use by another electron process.
After some digging, I found that the Electron process was still running in the background.  After killing the processes, I was able to launch yakyak again.
It should be noted, that going to the menu and hitting quit does close the process correctly, it is only when the X is hit.
After logging in fully, it looks like the app correctly closes upon hitting X, so this may only be an issue when doing the oauth via google.

I am not sure about your last paragraph because you say that x closes correctly + some oauth thing.
Anyway. We have 0 windows developers / contributors at the moment therefore it's difficult for us to fix window-specific bugs. I mark this as 'help wanted'. If i find the time to fire up a vm i will have a look but it's possible i won't do it :P

The last paragraph oauth thing is in reference to the login.coffee script.  Specifically you can see the oauth reference here: https://github.com/yakyak/yakyak/blob/master/src/login.coffee#L18
When I say after the X works correctly, I mean it only works correctly after you've logged into google and are in the app proper.  While you are performing the oauth login to google, the electron process does not close if you hit X (and actually locks you out of the app until you are able to kill the process).
I understand you may not have current windows contributors, but it never helps to get these things documented as known issues :)

I think i got it. While you log-in you use a separate window. The main window is "hidden". If you manage to close the login window the app sits in the background because there is still a hidden window that is never closed. I may be able to work with this even if i don't have windows.

... Clearly you can see I was having a rough time with my repo. Pull request created to fix this issue.


mr show: Fix --no-color-diff help

The help for '--no-color-diff' is exactly wrong.
Fix --no-color-diff so that it outputs the correct message.
Reported by: Lenny Szubowicz<EMAIL_ADDRESS>Signed-off-by: Prarit Bhargava<EMAIL_ADDRESS>

Fixes #625


Upgrade Swift 5 & fix warnings

Description

Upgrade Swift version to 5

Fix warnings related to Swift 5

Motivation and Context

We will be compatible with the Swift 5,

We will solve warnings

after this pull-request merge.
What kind of change does this PR introduce?

[ ]  Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ]  File changes for improvement
[x] This change requires a documentation update
[x] I have run tests

🚀 PTAL @gcharita

any update on this?

If you rebase this to get CI passing I will approve and merge


Query not returning sorted results

I am using the ruby gem for hellosign and trying to search through the signature requests. I can't, no matter what parameters I give, sort through and find one by title.

What endpoint are you using, and how are you searching through them?
You should be able to pull down an array of your requests and iterate on them to find one...

That was a customer submission. I'll ask her to clarify, but her reason for even doing it is screwed up. She said "the signature id isn't saved anywhere" so she's searching by title to retrieve the sign url. My mind was blown, but I took her seriously and still submitted the GitHub issue. I also asked her to clarify what in the world she meant, as the signature id is stored on our side like a mofo.
Sent from my iPhone

On Dec 4, 2015, at 5:44 PM, Derek Barncard<EMAIL_ADDRESS>wrote:
What endpoint are you using, and how are you searching through them?
You should be able to pull down an array of your requests and iterate on them to find one...
—
Reply to this email directly or view it on GitHub.

So, looks like the Ruby SDK doesn't currently provide access to the search portion of the signature list api:
https://www.hellosign.com/api/reference#Search
Right now client.get_signature_requests will only accept
query = create_query_string(opts, [:page, :page_size, :ux_version])
# from signature_request.rb

This should be updated to accept a query as well.
It's on the list; thanks for the report!

@radhack just fixed this and pushed the gem.
If you update you should be able to use something like :query => "from<EMAIL_ADDRESS>AND to<EMAIL_ADDRESS>CC: @desmondw


OpenSSL seems no longer present on Windows runners

Description
In spite of or because of cd9413ee05db8f0e3f05402091cedf54e060542a, my builds that use runner version 20230918.1.0 can't find OpenSSL anymore: see, for example: https://github.com/open-quantum-safe/liboqs-rust/actions/runs/6249790685/job/16968399712
The previous build, which used runner version 20230910.1.0 did pass: https://github.com/open-quantum-safe/liboqs-rust/actions/runs/6249784193/job/16967229587
Platforms affected

[ ] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] macOS 13
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
20230918.1.0
https://github.com/open-quantum-safe/liboqs-rust/actions/runs/6249790685/job/16968399712
Is it regression?
20230910.1.0
Expected behavior
Find OpenSSL in C:\Program Files\OpenSSL
Actual behavior
Can't find OpenSSL
Repro steps

don't change anything
github breaks your CI

Hey @thomwiggers!
It's a bit another issue to fix. OpenSSL is on the correct place. Your build failures is more related to the OpenSSL version. Accidentally we got light but not regular.
We'll fix it in the next release.

Oh god I wasted 2 days on this thinking it was an internal configuration change, I'm an enterprise customer.
This makes me loose trust in GitHub provider runners, when will the fix be available?

BTW the known workaround is to add this step into your Windows job:
      - name: Install OpenSSL
        run: powershell.exe ./.github/workflows/Install-OpenSSL.ps1

where ./.github/workflows/Install-OpenSSL.ps1 is a copy of https://github.com/ilia-shipitsin/runner-images/blob/b0381c354e34a74b8a62cc07ffbcbddae01a0ca0/images/win/scripts/Installers/Install-OpenSSL.ps1

Ok thank you I will fix I am not a bot signing @codybak4 / GitHub / mobile
Mac OS
On Sun, Sep 24, 2023 at 2:52 AM Jordan Singh @.***>
wrote:

Oh god I wasted 2 days on this thinking it was an internal configuration
change, I'm an enterprise customer.
This makes me loose trust in GitHub provider runners, when will the fix be
available?
—
Reply to this email directly, view it on GitHub
https://github.com/actions/runner-images/issues/8344#issuecomment-1732523378,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7IVAOQY3J5UF4X6JQGPAWDX37YEZANCNFSM6AAAAAA5ABUS4Q
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

In my Windows CI, I use this step. I wonder if this can be included in the image?
      - name: Install OpenSSL (Windows)
        if: runner.os == 'Windows'
        shell: powershell
        run: |
          echo "VCPKG_ROOT=$env:VCPKG_INSTALLATION_ROOT" | Out-File -FilePath $env:GITHUB_ENV -Append
          vcpkg install openssl:x64-windows-static-md

@nyurik , can you please elaborate how your issue is related to openssl package type "full" vs "light"

Full openssl distribution should be back!

In my Windows CI, I use this step. I wonder if this can be included in the image? (note that it takes 9 minutes to run this step in CI!)
- name: Install OpenSSL (Windows)
  if: runner.os == 'Windows'
  shell: powershell
  run: |
    echo "VCPKG_ROOT=$env:VCPKG_INSTALLATION_ROOT" | Out-File -FilePath $env:GITHUB_ENV -Append
    vcpkg install openssl:x64-windows-static-md

You saved my day, @nyurik.


[Exact search grid for gamma1 and gamma2]

As title, I'm wondering how did you set the search grid or your search method for the hyperparameters, the paper provide only the scope, which is a bit confusing when I tried to reproduce the result.

Thank you for your interest in our paper.
Basically, we adjusted the gamma1 and gamma2 depending on the datasets.

Beauty: [0, 2] with step size 0.1
Gowalla: [0, 5] with step size 0.4
Yelp2018: [0, 2] with step size 0.3

If you have any questions, please feel free to contact me.
Thank you.


Added PrestaShop CMS

Looking at the hardcoded list, I 've found Sylius which is a good eCommerce project. But there is a thing:

PrestaShop use Symfony 3.3 and we'll use 3.4 really soon.
depends on Symfony fullstack framework, Twig and Doctrine
almost 400k active websites, probably more than 500k websites since the creation of PrestaShop

Also, we may think about add Akeneo :)

Being in the list is needed only if other repositories in the GitHub organization can be used without the main repository. I quickly checked and this doesn't seem the case. As such, the main repo will already get the stars it deserves, isn't it?
We can actually remove entries from the list of this reasoning applies to prelisted ones.

Being in the list is needed only if other repositories in the GitHub organization can be used without the main repository.

awww, yeah it's rarely the case with PrestaShop! Got it, sorry for the noise :+1:


[Bug]: Veeam.Backup.PowerShell 12 or higher is required to run the Veeam VBR As Built Report.

Veeam Backup & Replication version
12
Bug description
Running from within the Veeam Powershell console, I get the error:
Report generation fails with the error: New-AsBuiltReport : Veeam.Backup.PowerShell 12 or higher is required to run the Veeam VBR As Built Report. Update the Veeam Backup & Replication console that provide the required modules.
Command-line input
New-AsBuiltReport -Report Veeam.VBR -Target server.example.com -Username<EMAIL_ADDRESS>-Password 'securepass' -Format Text,Html -OutputFolderPath 'C:\Support\AsBuiltReports' -AsBuiltConfigFilePath 'C:\Support\AsBuiltReports\report.json' -ReportConfigFilePath 'C:\Support\AsBuiltReports\AsBuiltReport.Veeam.VBR.json' -Verbose -EnableHealthCheck
Steps to reproduce
Find-Module -Name 'AsBuiltReport.*' -Repository 'PSGallery'
Install-Module -Name 'AsBuiltReport.Core'
Install-Module -Name 'AsBuiltReport.Veeam.VBR'
New-AsBuiltReport -Report Veeam.VBR -Target server.example.com -Username<EMAIL_ADDRESS>-Password 'securepass' -Format Text,Html -OutputFolderPath 'C:\Support\AsBuiltReports' -AsBuiltConfigFilePath 'C:\Support\AsBuiltReports\report.json' -ReportConfigFilePath 'C:\Support\AsBuiltReports\AsBuiltReport.Veeam.VBR.json' -Verbose -EnableHealthCheck

VERBOSE: Loading As Built Report configuration from 'C:\Support\AsBuiltReports\report.json'.
VERBOSE: Populating RepositorySourceLocation property for module AsBuiltReport.Core.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\AsBuiltReport.Core\1.4.0\AsBuiltReport.Core.psm1'.
VERBOSE: Populating RepositorySourceLocation property for module AsBuiltReport.Veeam.VBR.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\AsBuiltReport.Veeam.VBR\0.8.11\AsBuiltReport.Veeam.VBR.psm1'.
VERBOSE: Loading AsBuiltReport.Veeam.VBR report configuration file from path 'C:\Support\AsBuiltReports\AsBuiltReport.Veeam.VBR.json'.
VERBOSE: Setting report filename to 'Veeam Backup & Replication As Built Report'.
VERBOSE: Populating RepositorySourceLocation property for module AsBuiltReport.Core.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\AsBuiltReport.Core\1.4.0\AsBuiltReport.Core.psm1'.
WARNING: [ 12:40:45:204 ] [  Module  ] - AsBuiltReport.Core 1.4.0 is currently installed.
VERBOSE: [ 12:40:45:768 ] [ Document ] - Document 'Veeam Backup & Replication As Built Report' processing started.
VERBOSE: [ 12:40:45:800 ] [ Document ] - Please wait while the Veeam VBR As Built Report is being generated.
VERBOSE: [ 12:40:45:800 ] [ Document ] - Executing report style script from path 'C:\Program Files\WindowsPowerShell\Modules\AsBuiltReport.Core\1.4.0\AsBuiltReport.Core.Style.ps1'.
VERBOSE: [ 12:40:45:833 ] [ Document ] - Setting global document options.
VERBOSE: [ 12:40:45:836 ] [ Document ] - Enabling section/heading numbering.
[...]Loads of text settings things up[...]
VERBOSE: [ 12:42:32:047 ] [ Document ] - Trying to import Veeam B&R modules.
VERBOSE: [ 12:42:32:062 ] [ Document ] - Identifying Veeam Powershell module version.
VERBOSE: [ 12:42:32:293 ] [ Document ] - Using Veeam Powershell module version 1.0.
New-AsBuiltReport : Veeam.Backup.PowerShell 12 or higher is required to run the Veeam VBR As Built Report. Update the
Veeam Backup & Replication console that provide the required modules.
At line:1 char:1
+ New-AsBuiltReport -Report Veeam.VBR -Target server.example.com  ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,New-AsBuiltReport

Expected behaviour
Report generation happens
Screenshots
PS C:\Support\AsBuiltReports> Get-Module -Name Veeam.Backup.PowerShell -ListAvailable

    Directory: C:\Program Files\Veeam\Backup and Replication\Console

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Manifest   1.0        Veeam.Backup.PowerShell             {Add-VBRBackupCopyJob, Get-VBRBackupCopyJob, Set-VBRBackupCopyJob, Copy-VBRBackupCopyJob...}

PS C:\Support\AsBuiltReports> (Get-Item "C:\Program Files\Veeam\Backup and Replication\Console\Veeam.Backup.PowerShell.dll").VersionInfo.ProductVersion
<IP_ADDRESS>0

Operating System
systeminfo | Select-String "OS Name", "OS Version", "OS Build"

OS Name:                   Microsoft Windows Server 2016 Standard
OS Version:                10.0.14393 N/A Build 14393
OS Build Type:             Multiprocessor Free
BIOS Version:              VMware, Inc. VMW71.00V.18227214.B64.2106252220, 6/25/2021

PowerShell Version
$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.14393.7426
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.7426
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

PowerShell Modules
Name                    Version
----                    -------
AsBuiltReport.Core      1.4.0
AsBuiltReport.Veeam.VBR 0.8.11
PScribo                 0.10.0

Additional Context
No response
Before submitting

[X] I have read and followed the bug reporting guidelines.

What is your veeam version?

Thanks, fix is scheduled for next release (v0.8.12).
If you need to generate the report urgently, you can perform the manual installation of the module.
https://github.com/AsBuiltReport/AsBuiltReport.Veeam.VBR#github


Duplicate Data Resulting from Custom Tags

CustomTags are parsed in twice when using DecodeWith. This happens because both decodeLineOfMasterPlaylist and  decodeLineOfMediaPlaylist are called in decode, and both parse the CustomTags seperatley.
This issue can be observed using the Master Manifest, https://devstreaming-cdn.apple.com/videos/streaming/examples/img_bipbop_adv_example_fmp4/master.m3u8, and CustomTag example in Issue #160 detailed by @slugalisk.
The Master Manifest includes 5 #EXT-X-MEDIA tags, but DecodeWith produces 10 Values for the CustomTag.
The go-playground link below duplicates the issue as of 9/20/2023 with v0.12.0
https://goplay.tools/snippet/e_p-kLnpqco

As a workaround to the issue, I filter out duplicates in the Custom Tag Decode function.
Using the example from Issue #160, I modified the Decode function to be:
`
func (tag *ExtXMediaTag) Decode(line string) (m3u8.CustomTag, error) {
val := &ExtXMediaTagValue{}
for k, v := range m3u8.DecodeAttributeList(line) {
	switch k {
	case "TYPE":
		val.Type = v
	case "GROUP-ID":
		val.GroupID = v
	case "CHANNELS":
		val.Channels = v
	case "NAME":
		val.Name = v
	case "LANGUAGE":
		val.Language = v
	case "DEFAULT":
		val.Default = v == "YES"
	case "AUTOSELECT":
		val.AutoSelect = v == "YES"
	case "FORCED":
		val.Forced = v == "YES"
	case "URI":
		val.URI = v
	}
}

//prevent duplication - ref: https://github.com/grafov/m3u8/issues/201
dup := false
for _, t := range tag.Values {
	if *t == *val {
		dup = true
		break
	}
}

if !dup {
	tag.Values = append(tag.Values, val)
}

return tag, nil

}
`

Alternatively, if the playlist type is known, the CustomTags can be added to the playlist itself before decoding.
https://goplay.tools/snippet/COz0f_dEbA9


Optimize imports to conform checkstyle

Motivation
Some packages build fail due to ImportOrder check fail by checkstyle.  Although these packages are excluded in suppressions.xml but still got ImportOrder check fail in my environment.
Modifications
Optimize imports for these package by IDEA using the Imports setting mentioned in #8556

Remove the blank line between imports.
Reorder imports in  ascending
Remove exclude pacakge in suppressions.xml

/pulsarbot run-failure-checks

@wangjialing218 Can you rebase it to the latest master?


Rule doesn't apply when calling external service

Istio 1.2.3 (EKS)
I'm developing an attribute generating adapter which works perfectly fine with Rules that match ingress and/or mesh traffic, but not so much with egress (even when applied with match: "true").
Not sure if this is a bug, or if Mixer's check API call doesn't occur when a service in the mesh is calling external services.

Can anybody help with this? We are facing the same issue in our team, this will help us alot with the adoption of istio inside our cluster

Closing issue for now. Please feel free to reopen.
For questions about policy checking, please use the forums.


Final fixes sumedh

fix_patch_1

removed setwd, as the relative path is already set when running the file
fixed column names issue in clustering plots 3,4 and 5
Changed summary landing page to About and added short description
removed some comments from the code that were written during development
fixed path of GeneticAlg3

fix_patch_2

Update readme.md

Looks great Sumedh! I tested it as well.


Provide information on utilizing restore.tgz / GCS_RESTORE_URL

Looking in the replication controller definition I find reference to the variable GCS_RESTORE_URL. Digging further into the start.sh script reveals that the script will attempt to pull down a "backup" from GCS and prime jenkins with this information.
Looking back through the RC I don't see a pod with the capability of performing the backup operation nor any documentation about how to perform the initial setup of the container.  I would assume this means a user should stand up jenkins on their own and tar up JENKINS_HOME and place it on GCS noting the URL.
Finally, when looking through the container further I find that there is a rather old version of Jenkins:
root@45885ae19873:/usr/share/jenkins# java -jar jenkins.war --version
Running from: /usr/share/jenkins/jenkins.war
webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
1.609.2

I understand that this is the LTS release of Jenkins, but even still it's (as of this issue being filed) 234 days old with 7 LTS releases since then 3 batches of security advisories:
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-02-24
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-12-09
https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2015-11-11

Hey there @brianredbeard!!
Sorry for the delayed response. The backup/restore steps can be found here.
I have taken a pass at updating this for using the latest version of Jenkins and utilizing some of the Kubernetes 1.2 features over in this branch:
https://github.com/viglesiasce/continuous-deployment-on-kubernetes/tree/1.2-update
It's still a WIP but should be merged in by the end of the week. Feel free to provide feedback here:
https://github.com/GoogleCloudPlatform/continuous-deployment-on-kubernetes/pull/8

Closing as 1.2 update has been merged and no longer leverages the previous backup/restore steps. Link to more info on that backup/restore methodology is here:
https://cloud.google.com/solutions/automated-build-images-with-jenkins-kubernetes#jenkins_backup_and_restore


Hello, could you please tell me how I can run the Fun Model with Tora?

I noticed that the latest update supports the Tora model, but I can't figure out how to make it work.

i don't understand either the Tora Xfun support.
TORA doesnt work with Xfun models, only 5B_I2V.
Maybe i'm missing a TORA XFUN model released somewere that i'm not aware about.
sooo much confusion with all this Cogs 😂

It does work, it's just clumsy to use because the Fun sampler resizes the input to the closest bucket resolution (which is something I want to get rid of, but that's more work to do properly than I have time currently), you can see what that is in the log, and also with this node:

All the resolutions and frame counts need to match for it to work.
https://github.com/user-attachments/assets/0d7c5fda-7874-4353-9fc7-b04dbdf2e713
It can even be used with vid2vid as extra guidance:
https://github.com/user-attachments/assets/4d91fa41-0f33-45fd-a19a-da017b7215dd

Error while processing rearrange-reduction pattern "B (T H W) C -> (B T) C H W".
Input tensor shape: torch.Size([2, 3724, 3072]). Additional info: {'H': 52, 'W': 78}.
Shape mismatch, can't divide axis of length 3724 in chunks of 4056

spent half day, i'm unable to make it work even with the "closest bucket" node.
i'm using    alibaba-pai cogvideoXfun 1.1 5b Inp  ,
trying ake this work in image to video

spent half day, i'm unable to make it work even with the "closest bucket" node.
got this:
Error while processing rearrange-reduction pattern "B (T H W) C -> (B T) C H W".
Input tensor shape: torch.Size([2, 3724, 3072]). Additional info: {'H': 52, 'W': 78}.
Shape mismatch, can't divide axis of length 3724 in chunks of 4056

i'm using    alibaba-pai cogvideoXfun 1.1 5b Inp  ,
trying ake this work in image to video

Some dimension do not match, try with a simple 512x512 input because that will not get resized. The spline editor has to be set to same size, along with everything else.

thanks for your time and your incredible work on all this.
I got it to work finally.
Sadly there's no 2B tora version .. my 3090 is suffering with 5B😁
anyway, already got few really nice results, gonna show some on reddit. People need to know!

any plans on 2B tora?
also is there a way to add more splines to move different objects in different direction?
i saw some examples of tora around doing that,   can't find a way to do this

thanks for your time and your incredible work on all this. I got it to work finally. any plans on 2B tora? also, is there a way to add more splines to move different objects in different direction? i saw some examples of tora around doing that, can't find a way to do this

It doesn't seem to work with the 2b models because the embed sizes don't match, I don't know if it can work, probably not.
For multiple trajectories you can use multiple spline editors and join the coordinates with this (node is in KJNodes):

It doesn't seem to work with the 2b models because the embed sizes don't match, I don't know if it can work, probably not.

It's very sad... I really wanted it to work together with the "NimVideo/cogvideox-2b-img2vid" model, because in my opinion this is the best ratio of speed and quality for local i2v generation right now. And "Tora" would make it even better.

It doesn't seem to work with the 2b models because the embed sizes don't match, I don't know if it can work, probably not.

It's very sad... I really wanted it to work together with the "NimVideo/cogvideox-2b-img2vid" model, because in my opinion this is the best ratio of speed, quality and low VRAM consumption for local i2v generation right now. And "Tora" would make it even better.

i'm honestly way more interested in making this works with xfun 2b model out than that NimVideo, wich is an incredible model don't get me wrong... but the ability to pick a "start" and "end" image in Xfun provide way more possibilities.
this workflow here for example use Xfun i2v and i love it.

It's just not going to work with 2b, it would require training new Tora model for 2b.
The GGUF version of 5b doesn't use that much memory and it can work with really small resolutions, smaller than what 2b can do. At 512x512 the 5b model with Tora fits under 12GB.

It's just not going to work with 2b, it would require training new Tora model for 2b.
The GGUF version of 5b doesn't use that much memory and it can work with really small resolutions, smaller than what 2b can do. At 512x512 the 5b model with Tora fits under 12GB.

It’s not a matter of memory🙂 (i'm on 3090) it’s that the new 2B model has been released and claims to be as good as version 5B while also being much faster.. is not really like that in my opinion but is really impressive what 2B can do now.
Additionally, there are some workflows for creating animations that are based on the FunX 2B as a strength for speed.
Despite being less accurate, 2b’s high speed often makes it very useful for some tasks.
Personally, if I had a Tora that works with 2B, I’d probably be the happiest person in the world.
A bunch of nvidia H100 would help the happiness too 😁

It's just not going to work with 2b, it would require training new Tora model for 2b.
The GGUF version of 5b doesn't use that much memory and it can work with really small resolutions, smaller than what 2b can do. At 512x512 the 5b model with Tora fits under 12GB.

It’s not a matter of memory🙂 (i'm on 3090) it’s that the new 2B model has been released and claims to be as good as version 5B while also being much faster.. is not really like that in my opinion but is really impressive what 2B can do now. Additionally, there are some workflows for creating animations that are based on the FunX 2B as a strength for speed. Despite being less accurate, 2b’s high speed often makes it very useful for some tasks. Personally, if I had a Tora that works with 2B, I’d probably be the happiest person in the world. A bunch of nvidia H100 would help the happiness too 😁

In my experience the 5B I2V is still lot better quality. Also the Fun- models are more interesting because the resolution and frame count is not locked like the I2V models are.
Anyway it's just not going to work without re-training, nothing I can do about Tora + 2B.

yes agree as i sayd already, 5B is superior🙂
but If only God existed, he’d probably know how many tests I’ve done on both models.
I can assure you there are plenty of useful applications for the 2B models specifically because of their speed.
I can only hope they release TORA 2b at some point.
It’s always good to have more options when it comes to creating videos, where every second saved is welcome,
and having more choices is always better.
I know it’s hard with all the amazing work you’re doing, but whenever you have a couple of minutes, I recommend trying out this workflow. [https://civitai.com/models/866210?modelVersionId=1020506]

yes agree 100%, 5B is superior, no doubts 🙂
but If only God existed, he’d probably know how many tests I’ve done on both models.
I've found plenty of useful applications for the 2B models specifically because of their speed so let's hope they release TORA 2b at some point.
I know it’s hard with all the amazing work you’re doing,
but whenever you have a couple of minutes, I’d love to hear your opinion on this workflow,
but maybe that’s asking too much😁 https://civitai.com/models/866210?modelVersionId=1020506


ASCII Extended Spanish (+126)

This program is limited to "ascii(32) and ascii(126)"
In spanish we use some extended ASCCI

Thanks for your remark.
Almost any language from western europe, except english uses extended ascii.
This software is specifically limited to this subset for 3 reasons:

ascii(0) to ascii(31) are non-printable, except 3 keys which are hardcoded in the application, namely backspace (ascii(8)), tab (ascii(9)) and enter (ascii(10)). ascii(127) is non printable too (this one i guess i could map it properly)
the flipper zero (which remains the target machine) at the moment does absolutely NOT support characters outside ascii(0) ascii(127). it is the way the badusb application has been designed. there may be plans to extend that range later, but it will require a more thoughtful work, see next point.
ascii(128) to ascii(255) are not standardized and vary across countries. an "é" is not mapped to the same key depending on the system settings. before the advent of unicode, that part was called a code page. we could specifically require a known code page, but it would not work well on some middle eastern computer natively using another codepage. keep in mind that for extended ascii to work, we need support from the hid emulator inside flipper zero, but we also need to support it in the way we read the script .txt file. we could also specifically ask for script encoded in utf-8, but we would then have to support a far greater range of characters, which would require a complete rework of the badusb emulation part.

so, it is possible to support more ascii, but that's for later. let's already see how those mapping work with the current state of the device.