awscli2: 2.2.39 -> 2.2.40

Motivation for this change
awscli2 is broken on master due to 6b43ab7b901e54fdce74e7e08652a3cf80144182.
I'm updating the package version & freezing s3transfer until it is supported in awscli2.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

awscli2


After rancher upgrade, scaling up a workload creates new pods as part of scale up

Rancher versions:
rancher/server or rancher/rancher:v2.0.2 to v2.0.3-rc2
Steps to Reproduce:

Create a cluster in v2.0.2.
Create workloads wk1 with scale 2
Upgrade rancher to v2.0.3-rc2
Scale up the workload from 2 to 3

Three new pods are created and the original two are removed.
New pods are created and the old ones are deleted.

@StrongMonkey happens because in 2.0.3 we started adding affinity with empty value on update:
"spec": {
                "affinity": {},
                "containers": [
                    {

If inserting affinity is absolutely necessary fix, then we should document the fact that any update for workload created prior to 2.0.3, will result in pods recreation.

This is a design change that we need to implement to be able to change scheduling rules on workloads, so we will release note it.

@deniseschannon  Hi. Rancher v2.0.5、v2.0.6,  There are similar problems when configuring multiple environment variables.


EscapeUtils: fix escape result in case an address is stored

This unusual situation can happen if an address is converted to a raw pointer and that pointer is stored to a memory location. In this case the walkers need to follow load instructions even if the visitor and current projection path don't say so.
Fixes a miscompile
rdar://122805546

@swift-ci test

@swift-ci benchmark


Slow response times for submission requests on local server

Hello,
I'm experiencing an issue where response times for making submission requests are very slow. Each request takes about a second to complete, here's the output.
[17/Oct/2018:16:57:25 +0000] "GET /submission/28191881.json HTTP/1.1" 200 1096 0.9489
[17/Oct/2018:16:57:26 +0000] "GET /submission/27737463.json HTTP/1.1" 200 1085 0.9656
[17/Oct/2018:16:57:27 +0000] "GET /submission/27737441.json HTTP/1.1" 200 1168 0.9720
[17/Oct/2018:16:57:28 +0000] "GET /submission/26505248.json HTTP/1.1" 200 1188 0.9796
[17/Oct/2018:16:57:29 +0000] "GET /submission/26505213.json HTTP/1.1" 200 1162 0.9602
[17/Oct/2018:16:57:30 +0000] "GET /submission/26015495.json HTTP/1.1" 200 1113 0.9771
[17/Oct/2018:16:57:31 +0000] "GET /submission/25835173.json HTTP/1.1" 200 1219 0.9949
[17/Oct/2018:16:57:32 +0000] "GET /submission/25135350.json HTTP/1.1" 200 1235 0.9902
[17/Oct/2018:16:57:33 +0000] "GET /submission/25060895.json HTTP/1.1" 200 1261 0.9377
[17/Oct/2018:16:57:34 +0000] "GET /submission/25049362.json HTTP/1.1" 200 1352 1.0004
[17/Oct/2018:16:57:35 +0000] "GET /submission/24880819.json HTTP/1.1" 200 1023 0.9701
[17/Oct/2018:16:57:36 +0000] "GET /submission/24078853.json HTTP/1.1" 200 1270 1.0597
[17/Oct/2018:16:57:37 +0000] "GET /submission/24068126.json HTTP/1.1" 200 1137 0.8902
[17/Oct/2018:16:57:38 +0000] "GET /submission/23544162.json HTTP/1.1" 200 1126 0.9866

I made a little project just for testing submission requests from the API, the code can be found here. (excuse the sloppiness)
Also, I must add that response times from the API improve significantly when it's done through a web browser. I have absolutely no idea why this is.  Any help would be greatly appreciated!

  FAExport isn't the slowdown, it's Furaffinity throttling the requests.
Just to check, I tried changing the user agent (found at lib/faexport/scraper.rb:38) to the latest Firefox user agent string.  The requests sped up drastically but after 20 requests, came back with a 503 Service Temporarily Unavailable due to hitting FA's rate limiting.  You can mess around with the user agent and the speed that you do this but FA is not very friendly to mass scraping from a single machine.


bug: swift_format doesn't respect .swift-format file

Neovim version (nvim -v)
NVIM v0.9.4
Operating system/version
macOS 14.1.1 (23B81)
Add the debug logs

[X] I have set log_level = vim.log.levels.DEBUG and pasted the log contents below.

Log file
Log file: /Users/garrett/dev/scrap/conform-swift/.repro//state/nvim/conform.log
          22:37:11[DEBUG] Run command: { "swift-format" }
          22:37:11[DEBUG] swift_format exited with code 0
          22:38:05[DEBUG] Running formatters on /Users/garrett/dev/scrap/conform-swift/Package.swift: { "swift_format" }
          22:38:05[INFO] Run swift_format on /Users/garrett/dev/scrap/conform-swift/Package.swift
          22:38:05[DEBUG] Run command: { "swift-format" }
          22:38:05[DEBUG] swift_format exited with code 0
          22:39:40[DEBUG] Running formatters on /Users/garrett/dev/scrap/conform-swift/Package.swift: { "swift_format" }
          22:39:40[INFO] Run swift_format on /Users/garrett/dev/scrap/conform-swift/Package.swift
          22:39:40[DEBUG] Run command: { "swift-format", "--configuration", ".swift-format" }
          22:39:40[DEBUG] swift_format exited with code 0
          22:40:05[DEBUG] Running formatters on /Users/garrett/dev/scrap/conform-swift/Package.swift: { "swift_format" }
          22:40:05[INFO] Run swift_format on /Users/garrett/dev/scrap/conform-swift/Package.swift
          22:40:05[DEBUG] Run command: { "swift-format" }
          22:40:05[DEBUG] swift_format exited with code 0

Formatters for this buffer:
swift_format ready (swift)

Other formatters:

Describe the bug
When using the configuration of swift-format included in conform.nvim (listed as swift_format), the presence of a .swift-format file is not respected when formatting Swift code. Running swift-format from the command line does respect the .swift-format file by default.
Adding prepend_args = { "--configuration", ".swift-format" } to the swift_format configuration does resolve the issue, but doesn't explain why the configuration file isn't respected by default.
Steps To Reproduce

mkdir conform-swift && cd conform-swift
swift package init --type executable
echo '{ "indentation": { "tabs": 1 } }' > .swift-format
nvim -u repro.lua Package.swift
:lua require("conform").format()
Uncomment the line in repro.lua that adds the prepend_args property
Repeat steps 4 and 5

Expected Behavior
The spaces used for indentation in the Package.swift file would be replaced with tabs, as configured in the .swift-format file.
It only works after adding the prepend_args property as detailed above.
Minimal example file
swift package init --type executable will create the Package.swift file I'm using to reproduce the issue, but I'll include it here also:
// swift-tools-version: 5.9
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
    name: "conform-swift",
    targets: [
        // Targets are the basic building blocks of a package, defining a module or a test suite.
        // Targets can depend on other targets in this package and products from dependencies.
        .executableTarget(
            name: "conform-swift")
    ]
)

Minimal init.lua
-- DO NOT change the paths and don't remove the colorscheme
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "cache" }) do
	vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/lazy.nvim"
if not vim.loop.fs_stat(lazypath) then
	vim.fn.system({
		"git",
		"clone",
		"--filter=blob:none",
		"--single-branch",
		"https://github.com/folke/lazy.nvim.git",
		lazypath,
	})
end
vim.opt.runtimepath:prepend(lazypath)

-- install plugins
local plugins = {
	"folke/tokyonight.nvim",
	{
		"stevearc/conform.nvim",
		config = function()
			require("conform").setup({
				log_level = vim.log.levels.DEBUG,
				-- add your config here
				formatters_by_ft = { swift = { "swift_format" } },
				formatters = {
					swift_format = {
						-- Uncomment this line to see the .swift-format file respected
						-- prepend_args = { "--configuration", ".swift-format" },
					},
				},
			})
		end,
	},
	-- add any other plugins here
}
require("lazy").setup(plugins, {
	root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here
vim.o.list = true

Additional context
I don't know if this is an issue with swift-format itself, but I can only reproduce it with conform.nvim

@stevearc I've actually had a similar issue and I think using stdin is the problem. When you run <Package.swift swift-format it also doesn't respect the config (at least with my setup), whereas swift-format Package.swift does. I think using stdin = false and args = { '$FILENAME' } might work.

@heygarrett can you confirm if the suggestion from @isaacthefallenapple works?

The suggestion from @isaacthefallenapple doesn't work for me, unfortunately.

I unfortunately don't have a great way to reproduce this. Happy to provide pointers, but I think I'll need someone else to make a PR for this one.

@heygarrett I had similar issues, this the config that works for me:
formatters = {
  swift_format = {
    stdin = false,
    args = { "$FILENAME", "--in-place" },
  },
},
formatters_by_ft = {
  swift = { "swift_format" },
},

This is very similar to what @isaacthefallenapple suggested, just need to add --in-place.
apple/swift-format/README.md

-i/--in-place: Overwrites the input files when formatting instead of
printing the results to standard output. No backup of the original file is
made before it is overwritten.

Here's the log I have with my config
10:14:17[DEBUG] Running formatters on /Users/haosong/Developer/apple/test-conform-swift-format/Package.swift: { "swift_format" }
10:14:17[INFO] Run swift_format on /Users/haosong/Developer/apple/test-conform-swift-format/Package.swift
10:14:17[DEBUG] Creating temp file /Users/haosong/Developer/apple/test-conform-swift-format/.conform.9683855.Package.swift
10:14:17[DEBUG] Run command: { "swift-format", "/Users/haosong/Developer/apple/test-conform-swift-format/.conform.9683855.Package.swift", "--in-place" }
10:14:17[DEBUG] swift_format exited with code 0
10:14:17[DEBUG] Cleaning up temp file /Users/haosong/Developer/apple/test-conform-swift-format/.conform.9683855.Package.swift

@stevearc I created a PR to add the extra args in the config file for swift_format: https://github.com/stevearc/conform.nvim/pull/283
Not sure if this is the best way to fix or not.

Fixed for me! Thanks!


pr 3hr xmls needed to begin work on diurnal cycle

@durack1  Not needed to be run weekly.   Just once would do on the historical runs...

@gleckler1 take a peek at crunch:/work/cmip5/make_cmip5_xmls_da.py You'll need to edit your destination path to your HOME and then you should be close to a daily -> 3hr tweak and you're off

@durack1 could use your help with both 3hr and daily pr for historical and picontrol.  Does not need to be in cron job.

@gleckler1 what's the milestone on this - are we a 1.2 nexter?

@durack1 what is needed asap is some xmls for historical 3hr and daily "pr".... ok if its only 1 realization/model ... this will enable us to get started on a series of high freq analysis

@gleckler1, so I think there should be a bunch of 3hr and day files for pr building in:
crunch:/work/durack1/cmip5/

Take a peek on Monday and see what has been built.. You should have multiple experiments and most of the current data indexed on the local systems.. However it is cobbled together, so may require some iteration

@durack1   thanks, but still no can read... permissions need to be set recursively

@gleckler1 should be fixed now, however it's still building so will need to redo once it completes..

@gleckler1 ok seems to be complete - wanna close this if you can read the xmls?


Install Plugin provides no feedback

Problem/Motivation
After running a Composer install or update there is nothing in the command output to show what was changed (or not changed) by this installer plugin.
Expected behaviour
Composer will output the PHP CodeSniffer configuration key and value that it has set or changed.
Actual behaviour
Nothing is shown to even indicate whether this Composer Plugin for PHP CodeSniffer was executed or not. If a PHP CodeSniffer configuration is changed, Composer does not say so.
Steps to reproduce

Require this package with a supported standards package as per the README instructions.
Execute composer install or composer update

Proposed changes
Use the Composer IO to write to output:

Something to say the Plugin has started or is being run.
The config key and value to be set in PHP CodeSniffer.
(Optional) The results of the PHP CodeSniffer command to set a configuration key (ie. result from vendor/bin/phpcs --config-set key value)

I'm in favour of this.

This is a major improvement! Thanks for creating this issue and even more thanks for the PR!
For the future it would be even more awesome if we could display the actual ruleset names instead of paths.

Merged, thank you for this PR!


Headphone controls testing from PR #450

https://github.com/radiant-player/radiant-player-mac/pull/450
@jacobwgillespie
I tested the build provided in the above PR and found that the - & + volume controls work on my RHA MA-750i's, however, the play/pause button on my headphones seem to still open up iTunes and play/pause iTunes.

Yep, I'm seeing that as well - I'll take a look at this shortly

:+1:

Just a new guy here but it looks like nothing has been done with DDHidAppleRemote objects. Now given the current usage of DDHid* stuff. We could possible want to look at ripping out the DDHid* stuff in favor of MPRemoteCommandCenter since that seems to be the prefered method according to what I have seen in the dev docs. Feel free to set me straight since I am new to desktop apps and this project.

So MPRemoteCommandCenter is for iOS not OSX. My bad!!! I sure there has to be a similar vehicle for OSX though, but I could very very wrong.

So after reviewing a few things, I am completely barking up the wrong tree. DDHidappleRemotes stuff is not linked to BT controls at all. So not sure on how to contribute on this one. Sorry.


Combine Checkbox and RadioButton?

<Checkbox> and <RadioButton> both use the <SelectorButton> component.
Both files are literally identical, save for the selector prop specifying whether it's radio or checkbox.
// ...

const Checkbox = ({ checked, onClick, children, type, ...rest }) => (
  <SelectorButton
    selector="checkbox"
    checked={checked}
    onClick={onClick}
    type={type}
    {...rest}
  >
    {children}
  </SelectorButton>
);

Might it make sense to have one component in which you just specify the selector?

 Convert Option Button component


Add password field method to TextBox struct

I'm trying to get password boxes to appear as little stars in my druid app. Is there a way for me to do this in the current version of Druid?

Also, if it is not possible to do this in it's current state, could I make a pull request?

We had discussion on zulip about password input

I've put together something simple in #1839, that you can try out if you like?

@cmyr I tested it out, it works great!


publish statistics regarding cask popularity

I think that it would be of great help to publish statistics regarding cask popularity as we already have lots of casks and we would like to discover what else people are using. Now we reached a point where is impossible to browser all casks in order to see them but if we would know how many installs each one has we could look for the more popular ones.

We don’t intend to become a discoverability service. Similar requests have been discussed and refused multiple times, as it is not part of the goals of homebrew-cask. Amongst other things, the logistics are unsustainable.
This particular request has also been made.
The answer is a final “no”.


Buttons on create view

Should we default to having three buttons [Save, Save and continue editing, Cancel] on the default create model view?
Thanks @rochacbruno
https://github.com/flask-admin/flask-admin/pull/831#issuecomment-105062373

I'm for it. Seems like majority likes to have three buttons.

:+1:

As per https://github.com/flask-admin/flask-admin/pull/831#issuecomment-115265197
It looks like the concensus is for three buttons on both the 'add' and 'edit' views:
Save, Save and continue, Save and add.
Furthermore, in stead of having an explicit cancel button, we'll display the same tabs from the 'add' view on the 'edit' view.

Hello, I wonder how can I change the name of these buttons, the application for which I am now developing staff wish it had another name. I thank you.


Set Access Policy

Corrected formatting of start and expiry time. Fixes #18712

[x] The purpose of this PR is explained in this or a referenced issue.
[x] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[x] Tests are included and/or updated for code changes.
[x] Updates to CHANGELOG.md are included.
[x] MIT license headers are included in each file.

This should be described in the swagger. Please be sure to follow up about that as this would impact all languages.

I checked this API in Java and Python SDK. In Java SDK, start and expiry time are of the type OffsetDateTime which is in the required ISO 8061 format. Python SDK explicitly formats the start and expiry time, like what we are doing.


Issue with k8s.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-11/

This is a...

[x] Bug Report

Problem:
Documentation says that --feature-flags=CoreDNS=false should be applied if one wishes to keep kube-dns. But the option available is --feature-gates=CoreDNS=false
Proposed Solution:
Fix documentation
Page to Update:
k8s.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-11/

1.11.1

@desdic
thanks for the report.
/assign


Add CI for OpenVINO backend on Windows platform.

Please have a preview on the link.
This new badge is .

Depend on #95.
@huningxin PTAL, thanks.

The next PR of CI for Node Binding with WebNN native by OpenVINO backend on Windows platform will submit after this PR merged.

@BruceDai , could you please look at the failure of the OpenVINO backend (Windows)?

Hi @huningxin, the failure was due to #95 script unmerged. Should I re-trigger CI with an empty commit?   Thanks.

@huningxin  I retriggered the CI, please wait a while to see the CI status, thanks.

All checks PASS by rerunning CI. @huningxin Please take another look, thanks.


add BufferedTokenizer size limit safety

a large amount of data without newlines can currently OOM logstash. we should add a safety limit on the FileWatch::BufferedTokenizer and log the buffer full exception.

This is due to a mismatch between some inputs and this codec.
Event Mills should remove this problem - coming in 5.X


HashLocation does "pop" with transition.redirect()

I'm building a hybrid (phonegap) app at the moment using react and react-router. From what i gathered (https://github.com/rackt/react-router/issues/310), this means, that I need to use Router.HashLocation, because the app runs on the filesystem.
Is that still correct?
If so, I think I found a problem with the redirect-handling of HashLocation.
The use-case:
A simple auth-flow, where the user is redirected to the login page using the willTransitionTo hook.
willTransitionTo(transition) {
    let nextPath = transition.path;
    if (!transition.context.getActionContext().getStore(AuthStore).isLoggedIn()) {
        transition.redirect('/login', {}, {'nextPath': nextPath});
    }
},

Now, the problem is, that HashLocation internally does a push first, and then a replace, same as HistoryLocation, but it does so using window.location.replace, which is then handled via the onHashChange event, which is asynchronous.
Because of this, there seems to be a race-condition, where the _actionType gets set to null for the "push" here, right before the "replace"'s notifychange gets triggered, which results in the replace getting propagated as a "pop" here, which is wrong and makes back-handling almost impossible, as it is a faulty pop-event.
I fixed this locally by resetting the _actionType to null asynchronously in the next tick. This works in all the cases relevant for my app. Can you think of any situations, where this could cause problems?
regards,
mario

Thanks for the detailed report :+1:
The way I understand it, this should be a more reliable solution:
function onHashChange() {
  if (ensureSlash()) {
    var curActionType = _actionType;
    _actionType = null;
    notifyChange(curActionType || LocationActions.POP);
  }
}

Can you try and see if that fixes your issues as well?

@taurose Ah, ya. That should work. :)
@zupzup Can you give it a go and see if it resolves your issue? Thanks!

@mjackson @taurose: works like a charm :)

Awesome. Anyone wanna put up a PR?

I'd be happy to if @taurose isn't already on it :)

I'm not; feel free to :smile:

alrighty


Firefox and Chrome generation differ

I'm sorry but generating a fiddle is really hard since this library require imports etc.
The following
        let buffer = qr.imageSync("hello", {
            ec_level: 'H',
            margin: 1,
            type: 'png'
        })

generate 2 different results in firefox and chrome. The problem seems only related fo FF 48 (and 49 beta) on mac.

This library was never supposed to work in browsers.

I would probably add this information in the readme, it worked great in browser :)

How did you make it work in browser? Browserify? Webpack? Something else?

Webpack

What versions of qr-image and pako do you have?

"qr-image": "3.1.0"
pako I don't know, I guess is linked by qr-image


progress writer for validation digest

FWIW, I wrote some generic Reader/Writer wrappers for progress tracking a few years ago when I was at CDL working on a cloud storage testing tool Merritt — see progress*.go here: https://github.com/dmolesUC/cos/tree/master/internal/logging
The Reader/Writer wrappers just update a ProgressReporter on every read, which stores progress in an int64 that's read and updated via sync/atomic so a Ticker can poll it on its own schedule and report. Right now the way ProgressReporter reports is hard-coded, but it'd be easy enough to refactor to take a handler function.
Anyway, IDK whether it's any use, but if so, feel free to steal it; or I could have a go at extracting it into a separate module.

I really appreciate the tip, @dmolesUC -- thank you! The way I've settled on implementing progress writers (for now) is to pass an optional io.Writer and then use io.MultiWriter in the function. I've been using a mutex for sync, but after digging into this more, I will probably switch to atomics.

closing in favor of #27


Upgrade from v1.9 -> Enter email(s) for Notifications Renewal Exception

Was using v<IP_ADDRESS>.  Got the "Update your client software to continue using Let's Encrypt" email from letsencrypt.org.
Installed v<IP_ADDRESS>1
Ran with the "Import renewals from LEWS/WACS 1.9.x" option
All renewals fail with error:
(Exception): User input 'Enter email(s) for notifications about problems and abuse (comma seperated)' should not be needed in --renew mode.
Setting up email notifications in settings.json did not fix the issue.
Do I need to "delete your Signer and Registration files" as mentioned in #845 ?  I don't have anything in %programdata%/win-acme other than the .renewal files and the log.

Same problem here.
Windows 2016 Standard Edition
Used Version <IP_ADDRESS>1  (no installation, just unzipped into new folder)
Added SMTP credentials and receive error mails.
Startet Renewal manual on commandline within unzip directory:
wacs.exe --verbose --renew --baseuri "https://acme-v02.api.letsencrypt.org/"
Received:
[VERB] Verbose mode logging enabled
[VERB] Looking for settings.json in C:\Admin\LetsEncriptV2
[DBUG] Config folder: C:\ProgramData\win-acme\acme-v02.api.letsencrypt.org
[DBUG] Log path: C:\ProgramData\win-acme\acme-v02.api.letsencrypt.org\Log
[DBUG] Cache path: C:\ProgramData\win-acme\acme-v02.api.letsencrypt.org\Certificates
[INFO] A simple Windows ACMEv2 client (WACS)
[INFO] Software version <IP_ADDRESS>1 (RELEASE, PLUGGABLE)
[INFO] IIS version 10.0
[INFO] Running with administrator credentials
[INFO] Scheduled task looks healthy
[INFO] Please report issues at https://github.com/PKISharp/win-acme
[VERB] Test for international support: 語言 язык لغة
[VERB] Arguments: --verbose --renew --baseuri https://acme-v02.api.letsencrypt.org/
[DBUG] Renewal period: 55 days
[VERB] Checking renewals
[VERB] Sending e-mails True
[VERB] Adding <IP_ADDRESS> as DNS server
[VERB] Adding <IP_ADDRESS> as DNS server
[VERB] Adding <IP_ADDRESS> as DNS server
[VERB] Checking buch-metadaten.de
[INFO] Renewing certificate for buch-metadaten.de
[VERB] Loading ACME account signer...
[VERB] Constructing ACME protocol client...
[DBUG] Send GET request to https://acme-v02.api.letsencrypt.org/directory
[VERB] Request completed with status OK
[DBUG] Send HEAD request to https://acme-v02.api.letsencrypt.org/acme/new-nonce
[VERB] Request completed with status OK
[EROR] (Exception): User input 'Enter email(s) for notifications about problems and abuse (comma seperated)' should not be needed in --renew mode.
[DBUG] Exception details: Exception {TargetSite=Void Validate(System.String), StackTrace="   at PKISharp.WACS.Services.InputService.Validate(String what)\r\n   at PKISharp.WACS.Services.InputService.RequestString(String what)\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.GetContacts()\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.LoadAccount(AcmeProtocolClient client, IJwsTool signer)\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.ConfigureAcmeClient()\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.GetClient()\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.CreateOrder(IEnumerable1 identifiers)\r\n   at PKISharp.WACS.RenewalExecutor.Renew(Renewal renewal, RunLevel runLevel)\r\n   at PKISharp.WACS.RenewalManager.ProcessRenewal(Renewal renewal, RunLevel runLevel)", Message="User input 'Enter email(s) for notifications about problems and abuse (comma seperated)' should not be needed in --renew mode.", Data=[], InnerException=null, HelpLink=null, Source="wacs.lib", HResult=-2146233088}  [EROR] Renewal for buch-metadaten.de failed, will retry on next run  [INFO] Sending e-mail with subject Error processing certificate renewal to<EMAIL_ADDRESS>[VERB] Checking onixtools.de  [INFO] Renewing certificate for onixtools.de  [VERB] Loading ACME account signer...  [VERB] Constructing ACME protocol client...  [DBUG] Send GET request to https://acme-v02.api.letsencrypt.org/directory  [VERB] Request completed with status OK  [DBUG] Send HEAD request to https://acme-v02.api.letsencrypt.org/acme/new-nonce  [VERB] Request completed with status OK  [EROR] (Exception): User input 'Enter email(s) for notifications about problems and abuse (comma seperated)' should not be needed in --renew mode.  [DBUG] Exception details: Exception {TargetSite=Void Validate(System.String), StackTrace="   at PKISharp.WACS.Services.InputService.Validate(String what)\r\n   at PKISharp.WACS.Services.InputService.RequestString(String what)\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.GetContacts()\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.LoadAccount(AcmeProtocolClient client, IJwsTool signer)\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.ConfigureAcmeClient()\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.GetClient()\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.CreateOrder(IEnumerable1 identifiers)\r\n   at PKISharp.WACS.RenewalExecutor.Renew(Renewal renewal, RunLevel runLevel)\r\n   at PKISharp.WACS.RenewalManager.ProcessRenewal(Renewal renewal, RunLevel runLevel)", Message="User input 'Enter email(s) for notifications about problems and abuse (comma seperated)' should not be needed in --renew mode.", Data=[], InnerException=null, HelpLink=null, Source="wacs.lib", HResult=-2146233088}
[EROR] Renewal for onixtools.de failed, will retry on next run
[INFO] Sending e-mail with subject Error processing certificate renewal to<EMAIL_ADDRESS>[VERB] Checking tantra-experience.de
[INFO] Renewing certificate for tantra-experience.de
[VERB] Loading ACME account signer...
[VERB] Constructing ACME protocol client...
[DBUG] Send GET request to https://acme-v02.api.letsencrypt.org/directory
[VERB] Request completed with status OK
[DBUG] Send HEAD request to https://acme-v02.api.letsencrypt.org/acme/new-nonce
[VERB] Request completed with status OK
[EROR] (Exception): User input 'Enter email(s) for notifications about problems and abuse (comma seperated)' should not be needed in --renew mode.
[DBUG] Exception details: Exception {TargetSite=Void Validate(System.String), StackTrace="   at PKISharp.WACS.Services.InputService.Validate(String what)\r\n   at PKISharp.WACS.Services.InputService.RequestString(String what)\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.GetContacts()\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.LoadAccount(AcmeProtocolClient client, IJwsTool signer)\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.ConfigureAcmeClient()\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.GetClient()\r\n   at PKISharp.WACS.Clients.Acme.AcmeClient.CreateOrder(IEnumerable`1 identifiers)\r\n   at PKISharp.WACS.RenewalExecutor.Renew(Renewal renewal, RunLevel runLevel)\r\n   at PKISharp.WACS.RenewalManager.ProcessRenewal(Renewal renewal, RunLevel runLevel)", Message="User input 'Enter email(s) for notifications about problems and abuse (comma seperated)' should not be needed in --renew mode.", Data=[], InnerException=null, HelpLink=null, Source="wacs.lib", HResult=-2146233088}
[EROR] Renewal for tantra-experience.de failed, will retry on next run
[INFO] Sending e-mail with subject Error processing certificate renewal to<EMAIL_ADDRESS>[VERB] Exiting with status code -2146233088

The problem is that the "Import" function only copies the old renewals from 1.9.x to the new location and format used by 2.x.x. It doesn't do anything else, such as registering an account with the new ACMEv2 server (which you will need to renew).
If you don't manually renew the first time and don't provide the input the program needs to create an account in unattended mode (i.e. --emailaddress and --accepttos) then you'll run into this error. I realize that this is all not very obvious so I'll improve docs and make the importer create the new ACME account in the next release.
Thanks for sharing your experiences!

I encountered the same thing too - having gotten an email from Letsencrypt about updating to acme v2.
Could I ask what the fix or workaround is? It's not an awfully long time before my cert expires :)

Inspired by Wouter Tinus earlier comment I did set up the ACME account details using WACS.exe.
Option "O", then "A", then enter email address. After this has been done, the "Renew scheduled" function (called manually) works and does the renewal. The scheduled task using the command
"wacs --renew --baseuri "https://acme-v02.api.letsencrypt.org/" no longer throws an error.

Worked perfectly, thanks

Inspired by Wouter Tinus earlier comment I did set up the ACME account details using WACS.exe.
Option "O", then "A", then enter email address. After this has been done, the "Renew scheduled" function (called manually) works and does the renewal. The scheduled task using the command
"wacs --renew --baseuri "https://acme-v02.api.letsencrypt.org/" no longer throws an error.

Trying to wrap my head around the proper upgrade 1.9.x to 2.1 procedure (seems like there have been a few issues #1383, #1382). Can you enumerate the exact steps and order to upgrade used to upgrade from 1.9.x to 2.1?
Thanks &
Cheers,
Toby

@Toby:
I'll try but it really was a matter of trial and error ...
I first did the obvious, importing the "old" renewals using wacs.
It did create a new scheduled task. I deleted the old one and tried to run the new one from within the scheduler. It failed. I did run the renewal task from the command line and received the error as documented above. I did set the email credentials within the settings file - no change.
Today I just did the account settings as decribed above and Voila - things work.

That's what I was afraid of ... it seems the documentation has gotten REALLY scattered (github wiki, additional instructions listed in issues, incomplete or not up-to-date docs at https://pkisharp.github.io/win-acme ... It's hard to find the correct procedure. Not to mention the fact that we are using custom Serilog logging and I'd like to investigate using the Route53 plugin but cannot find the plugin docs either.

With one of our servers, here's what I did (that mostly worked):

Unzipped everything from downloaded 2.1.x pluggable release.
From administrative command prompt, ran wacs.exe and selected Q simply to create settings.json
Edited settings.json adding SMTP settings so we can get emails.
Ran wacs.exe again, selected "O" and "I" to import the renewals, then "Q" to quit.
Ran wacs.exe again, selected "O" and "A" to add the email, then "Q" to quit.
Ran a manual renewall using wacs.exe --verbose --renew --baseuri "https://acme-v02.api.letsencrypt.org/" which was successful.

Still cannot get verbose logs through the Serilog "disk" sink but I'll open another issue for that. YMMV.

Release 2.1.4 just make things a bit easier (mainly by ensuring the ACMEv2 account exists) and improved documentation also. All you absolutely must to do now is hit that "Import" switch.

I already upgraded on 15th January, but how can we fix the issue with the missing ACMEv2 account now? I guess I cannot import again and I also renewed all certs on 15th. But on 31 January I got an email that my request from 15th is using ACMEdotNET/<IP_ADDRESS> (ACME 1.0)  ACMEdotNET/<IP_ADDRESS> (ACME 1.0)

Just hit the Renew option in the main menu and an account will be created if required.

Should this work with v2.1.2, too?

Yes, any 2.x version in fact


Masking separate attachments

Hello, in the old plugin for spine runtimes @pixi-spine all the attachments were placed inside of a containers which gave us the chance to mask different attachments with different masks, or apply mask from Pixi Graphic. Will this be added here ?
Also when clipping mask is applied from the spine file, not only the selected attachments are clipped but all above, I couldn't manage to figure a workaround, can you give me some tips ?
Cheers, Kaloyan.
P.S.: I've managed to create mixins for loading atlases from already loaded images (it was possible in the old plugin). If it's considered to be added I may provide PR so you have look around and merge it ?

P.S.: I've managed to create mixins for loading atlases from already loaded images (it was possible in the old plugin). If it's considered to be added I may provide PR so you have look around and merge it ?

Also would like to create TextureAtlas from Pixi textures already loaded from spritesheet.

Yea, that's what i meant. We can call empty constructor TextureAtlas new TextureAtlas() and then pass textures to it, like the version in the pixi-spine extension. I may create PR.

Yea, that's what i meant. We can call empty constructor TextureAtlas new TextureAtlas() and then pass textures to it, like the version in the pixi-spine extension. I may create PR.

Would be great to see your mixin code! I need to do the same thing

Yea, that's what i meant. We can call empty constructor TextureAtlas new TextureAtlas() and then pass textures to it, like the version in the pixi-spine extension. I may create PR.

Would be great to see your mixin code! I need to do the same thing

I wll make PR this weekend or maybe next week.

Hi, don't know how to make PR here so...
mixins:
`const p = TextureAtlas.prototype;
p.addTextureHash = function(textures: Map<string, Texture>, stripExtension: boolean) {
for (const key in textures) {
if (textures.hasOwnProperty(key)) {
this.addTexture(stripExtension && key.indexOf('.') !== -1 ? key.substring(0, key.lastIndexOf('.')) : key, textures[key]);
}
}
};
p.addTexture = function(name: string, texture: Texture) {
let page: TextureAtlasPage = this.pages.find((page: TextureAtlasPage) => page.baseTexture === texture.baseTexture) || null;
// Sets the atlas page
if (!page) {
	page = new TextureAtlasPage(name);

	const baseTexture = texture.baseTexture;

	page.baseTexture = baseTexture;
	page.width = baseTexture.width;
	page.height = baseTexture.height;

	page.minFilter = filterFromString(baseTexture.minFilter);
	page.magFilter = filterFromString(baseTexture.magFilter);
	page.uWrap = page.vWrap = wrapFromString(baseTexture.repeatMode);

	this.pages.push(page);
}

// Sets the region for the atlas page
const region = new TextureAtlasRegion(page, name);

region.index = -1;
region.width = page.width;
region.height = page.height;
region.u = region.v = 0;
region.u2 = region.v2 = 1;

if (region.originalWidth == 0 && region.originalHeight == 0) {
	region.originalWidth = region.width;
	region.originalHeight = region.height;
}

this.regions.push(region);

// Attaches the texture for each region
const spineTexture = new SpineTexture(texture.baseTexture);
page.setTexture(spineTexture);

return region;

};`
loading
`  async load(images) {
const spineAtlas = new TextureAtlas('');
spineAtlas.addTextureHash(images, true);
	const skeletonAsset = await resource; // This may be json or skel
	const attachmentLoader = new AtlasAttachmentLoader(spineAtlas);

	const parser = skeletonAsset instanceof Uint8Array ? new SkeletonBinary(attachmentLoader) : new SkeletonJson(attachmentLoader);
	const skeletonData = parser.readSkeletonData(skeletonAsset);

	return new Spine({ skeletonData });

}`

Hi
We have now moved this project to the official Esoteric Software repo for them to maintain. As a result we will be archiving this repo and closing all issues. If you still are having this issue please feel free to open an issue over on the new repo!

New Repo

As for migrating between the projects it should be as simple as swapping out the imports from @pxi/spine-pixi to @esotericsoftware/spine-pixi-v8


Write unit tests for initcontainer

We should write unit tests for initcontainer and have them run on the CI pipeline as well. We should be careful to cleanup after the tests finish, since the initcontainer creates a GsdkConfig.json file. We should also add that file to a .gitignore in the folder.

fixed on #58


Add static_dirs site configuration to disable PHP handling

A site can then define static_dirs that don't get passed to PHP
and instead by default get treated as static files even
if 404ing.
It also means code can't be maliciously uploaded and executed.

Tested on default seed :+1:


Linkage conflict with libcasper on FreeBSD 14

In #12 I forced libnv-sys to always link to libnv.so.0, even if a newer one were present.  I thought that would provide good backwards-compatibility and also cross-compilability.  However, I failed to consider interactions with other native libraries.  For example, on FreeBSD 14 libcasper.so.1 is already linked to libnv.so.1.  Trying to build a Rust program that uses both libcasper-sys (not yet published) and libnv-sys will result in linking to both libnv.so.1 and libnv.so.0.  That's obviously not good.  We don't want to for example allocate an NVList using one library and destroy it using the other.
I'll need to rethink this.  Right now I can only think of two solutions:

Run bindgen at build time, which breaks cross-compiling and pulls in extra dependencies, or
Drop support for libnv.so.0, which means all stable releases of FreeBSD.

I'm fine with dropping support for libnv.so.0. When I started on this, I always planned only to support latest releases. If someone need older version - they can grab older libnv.
@asomers you've already started on the solution?

Once the solution is implemented, I will cut a new release for all crates related.

Do you realize that FreeBSD 14 hasn't been released yet?  13.1 is the latest stable release, and it has libnv.so.0.  I think the best solution is to generate bindings at build-time.  I'm already working on it.

My bad, I've confused it with Ruby that had release every xmas.
I prefer to keep cross-compiling possible and easy, but since you're have
already started, I guess it fine to do build time bindings.
On Fri, Dec 23, 2022, 7:53 PM Alan Somers @.***> wrote:

Do you realize that FreeBSD 14 hasn't been released yet? 13.1 is the
latest stable release, and it has libnv.so.0. I think the best solution is
to generate bindings at build-time. I'm already working on it.
—
Reply to this email directly, view it on GitHub
https://github.com/Inner-Heaven/libnv-rs/issues/16#issuecomment-1364453919,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABEFG3CQI2JS4NRKH3S4ITWOZXT7ANCNFSM6AAAAAATF6LY6E
.
You are receiving this because you commented.Message ID:
@.***>


Notify users their sync is denied

If should_sync returns false (see https://github.com/lbryio/internal-apis/issues/1167), the channel does not qualify for youtube sync because it doesn't have 100 subs or content within the last 2 months. We should notify the user their channel will not sync but they still may be considered for the rewards program (I review these and make a determination based on channel / account).

This is being done via automated email now.


[HUDI-1029] In inline compaction mode, previously failed compactions …

…needs to be retried before new compactions

Prevents failed compactions from causing issues with future commits
Need to add tests

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@bvaradar ready for review.


(PE-27037) Use redhatfips-7-x86_64 for fips platform

Now that we have a redhatfips7 tarball, this changes hostgenerator to use the redhatfips-7-x86_64 platform rather than el-7-x86_64.

DNM until test completes

Merge https://github.com/puppetlabs/beaker/pull/1596 first

With both of these PRs, the right tarball is pulled down and installed (which currently fails, unrelated to these PRs).
[nick@ncc-1701-d pe_acceptance_tests]$ bundle exec beaker-hostgenerator redhatfips7-64mcd-64fa --pe_dir="http://enterprise.delivery.puppetlabs.net/2019.2/ci-ready" --pe_ver=`curl "http://enterprise.delivery.puppetlabs.net/2019.2/ci-ready/LATEST"` > hosts.cfg
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    26  100    26    0     0   4600      0 --:--:-- --:--:-- --:--:--  5200
[nick@ncc-1701-d pe_acceptance_tests]$ cat hosts.cfg
---
HOSTS:
  redhatfips7-64-1:
    pe_dir: http://enterprise.delivery.puppetlabs.net/2019.2/ci-ready
    pe_ver: 2019.2.0-rc6-124-gbccce88
    pe_upgrade_dir:
    pe_upgrade_ver:
    platform: redhatfips-7-x86_64
    packaging_platform: redhatfips-7-x86_64
    template: redhat-fips-7-x86_64
    hypervisor: vmpooler
    roles:
    - agent
    - master
    - dashboard
    - database
  redhatfips7-64-2:
    pe_dir: http://enterprise.delivery.puppetlabs.net/2019.2/ci-ready
    pe_ver: 2019.2.0-rc6-124-gbccce88
    pe_upgrade_dir:
    pe_upgrade_ver:
    platform: redhatfips-7-x86_64
    packaging_platform: redhatfips-7-x86_64
    template: redhat-fips-7-x86_64
    hypervisor: vmpooler
    roles:
    - agent
    - frictionless
CONFIG:
  nfs_server: none
  consoleport: 443
  pooling_api: http://vmpooler.delivery.puppetlabs.net/
[nick@ncc-1701-d pe_acceptance_tests]$ bundle exec beaker --helper lib/beaker_helper.rb --debug --keyfile ~/.ssh/id_rsa-acceptance --provision --hosts=hosts.cfg --pre-suite=setup/install.rb
Hypervisor for redhatfips7-64-1 is vmpooler
Hypervisor for redhatfips7-64-2 is vmpooler
Beaker::Hypervisor, found some vmpooler boxes to create
Warning: Invalid credentials file:
(ArgumentError) Failed loading credentials from .fog file '/home/nick/.fog'.Reason: (Errno::ENOENT) No such file or directory @ rb_sysopen - /home/nick/.fog
Proceeding without authentication
Requesting VM set from vmpooler
Using available host 'gfvhb18xmvneeyr.delivery.puppetlabs.net' (redhatfips7-64-1)
Using available host 'ojenuxolzo1orkc.delivery.puppetlabs.net' (redhatfips7-64-2)
Spent 0.05 seconds grabbing VMs
Tagging vmpooler VMs
Spent 0.08 seconds tagging VMs
...
gfvhb18xmvneeyr.delivery.puppetlabs.net (redhatfips7-64-1) 18:25:58$ cd /tmp/2019-08-13_<IP_ADDRESS>Hc8X5; curl http://enterprise.delivery.puppetlabs.net/2019.2/ci-ready/puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64.tar | tar -xvf -
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
      0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/VERSION
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/LICENSE.txt
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/puppet-enterprise-installer
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/puppet-enterprise-uninstaller
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/README.markdown
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/packages/bootstrap-metadata
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/packages/redhatfips-7-x86_64-package-versions.json
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/packages/redhatfips-7-x86_64/pe-ace-server-2019.2.1-1.redhatfips7.x86_64.rpm
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/packages/redhatfips-7-x86_64/pe-backup-tools-2<IP_ADDRESS>.1.g09b7119-1.redhatfips7.x86_64.rpm
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/packages/redhatfips-7-x86_64/pe-bolt-server-2<IP_ADDRESS>.78.g8882a8b-1.redhatfips7.x86_64.rpm
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/packages/redhatfips-7-x86_64/pe-client-tools-<IP_ADDRESS>.g1ab24ca-1.redhatfips7.x86_64.rpm
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/packages/redhatfips-7-x86_64/pe-console-services-2<IP_ADDRESS>-1.redhatfips7.noarch.rpm
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/packages/redhatfips-7-x86_64/pe-console-services-termini-2<IP_ADDRESS>-1.redhatfips7.noarch.rpm
    puppet-enterprise-2019.2.0-rc6-124-gbccce88-redhatfips-7-x86_64/packages/redhatfips-7-x86_64/pe-installer-2<IP_ADDRESS>.72.g27a6458-1.redhatfips7.x86_64.rpm
...

@nmburgan looks like there are some spec failures

Yeah, I think https://github.com/puppetlabs/beaker/pull/1596 needs to go in first

Test fixtures updated


Fix loading of Hashie.logger and set it to Rails.logger when in Rails

The auto-load is never triggered because there is no Hashie::Logger
constant to trigger it. We need to require the file in the top level
hashie.rb and anywhere else that uses it (in case someone just loads a
single file).
At the moment, this is only used in Mash, so we're covered.
In addition, try to be smarter about the default logger by setting it to the
Rails logger when we're in a Rails environment.

Ah, interesting. Exclude spec/integration/rails/log/test.log and this is good to go I think.

D'oh! Totally missed that. It's so important to have more than one set of eyes on something.


Req.: New PyPi Packages...

I need https://github.com/nephila/djangocms-blog/commit/58373c1586394615ec4bebf2d97524059b0b82a8 in my project.
@yakky can you submit a new release to PyPi, please?

I plan to release a 0.4.b1 version this weekend

Great :+1:

Version 0.4.0.b1 released!


default arguments dont work for anon args

function say(anon text: String = "WHF") {
    println("{}", text)
}
function main() {
    say()
}

doesnt work, but works without the anon

They're not supposed to, arguments with defaults must not be anon (perhaps we should make that an explicit error)

whats the reasoning for that? the only functional reason I can see is ambiguity when there are multiple anon args, but then one could simply mandate that defaults are applied back to front, pretty much how it works in c++.
where this annoyed me was that in the parser there is the peekfunction taking as argument the number of steps and it seems very natural to me to have a default of 1 there (i.e. peek "just ahead") but thats not possible...

and yes, if there should be concensus to not allow defaults on anon args (though I cannot see why) then it should not be allowed to specify them

This issue no longer reproduces :)


REL: update Paver file to ensure sdist contents are OK for releases.

Closes gh-5195 (missing Sphinx theme for 0.16.0 tarballs).
Also remove release.sh - we're not using it anymore.  Instead, we'll be using numpy-vendor/fabfile.py
[ci skip]

Alright, the identical numpy change is merged and I need to backport this, so in it goes.

backported in e437297


Upgrade to Faster-Whisper 1.0.1

It would be great if they updated the integration with Faster-Whisper 1.0.1

It would be better to use the latest version.
The problem is, if users are using CUDA versions below 12, then it causes errors like #102.
But the migration has to be done, because the latest version would definitely be better.
I made #106 for this, and it should definitely be merged soon.

merged #106 and closing this


feat: added Semantic PR Title app file

Checklist

[x] If you're adding a listing for your app, be sure your app is in the /_apps/ folder before opening this Pull Request.

[ ] All comments in frontmatter need to be removed.

frontmatter?

[x] Performs a useful action through the GitHub API that solves an existing problem for developers: {explain the action here}

[x] Is original: for example, it does something not already done by an existing Probot app

There's another app that does something similar, but I could not get it to work for my org/private repo. Mine works differently, as it only focuses on the PR title and uses a regex instead of commit lint. It's more flexible in that way since it could be used for anything that can be validated with a regex.

[x] Has tests
[x] Has documentation
[x] Is open source
[x] Has a license
[x] Has a code of conduct
[x] Has someone willing to at least minimally maintain them for the near future: coleHafner

View rendered _apps/semantic-pr-title.md

There's another app that does something similar, but I could not get it to work for my org/private repo. Mine works differently, as it only focuses on the PR title and uses a regex instead of commit lint. It's more flexible in that way since it could be used for anything that can be validated with a regex.

It sounds like it would be better to collaborate with the authors on the other app? @zeke is the other app yours?

@gr2m I did file an issue, but haven't got much traction so far.

I agree that this app is very similar to the existing https://github.com/probot/semantic-pull-requests app. Based on the conversation in https://github.com/probot/semantic-pull-requests/issues/70, it appears that the desired functionality is not working on private repos, though it works on public repos. It seems like it might be a scope/permissions issue with the app. I don't have time to prioritize fixing that issue, but I will happily review, merge, and deploy a pull request that solves the problem.

actually I'd consider the usecase you've added as a duplicate of semantic-pull-requests, can you add a config where there's something else,? because semantic-pull-request app already exists :)

Go ahead and close it.
On Fri, Jan 31, 2020, 22:45 stale[bot]<EMAIL_ADDRESS>wrote:

Is this still relevant? If so, what is blocking it? Is there anything you
can do to help move it forward?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/probot/probot.github.io/pull/314?email_source=notifications&email_token=AAC47I3GL6CTDAOAYTHCWILRAULA5A5CNFSM4IZN43EKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKQV6IY#issuecomment-581000995,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAC47I4I4AZ4V3MWJ62PGMLRAULA5ANCNFSM4IZN43EA
.


CNN Model

Need to train a CNN model using Data set

@patrickbrawley @lorcanmcd  lets get on this please.


The model from checkpoint is not match for current model

Thank you for your work!
Before running run.py, I changed the "batch_size" from 64 to 32, getting a checkpoint named "ckpt.pth".

Now, when I try to run eval.py, some errors happened with state_dict just as belows:
"RuntimeError: Error(s) in loading state_dict for DinoFeaturizer:
size mismatch for model.cls_token: copying a param with shape torch.Size([1, 1, 768]) from checkpoint, the shape in current model is torch.Size([1, 1, 384]).
size mismatch for model.pos_embed: copying a param with shape torch.Size([1, 785, 768]) from checkpoint, the shape in current model is torch.Size([1, 785, 384]).
size mismatch for model.patch_embed.proj.weight: copying a param with shape torch.Size([768, 3, 8, 8]) from checkpoint, the shape in current model is torch.Size([384, 3, 8, 8]).
size mismatch for model.patch_embed.proj.bias: copying a param with shape torch.Size([768]) from checkpoint, the shape in current model is torch.Size([384]).
size mismatch for model.blocks.0.norm1.weight: copying a param with shape torch.Size([768]) from checkpoint, the shape in current model is torch.Size([384])."
There is also a capture:

Hope for your help, thank you very much !

Hello,
I suppose that you set the 'model_type' in json file to 'vit_base' before running run.py.
If you trained with 'vit_base,' you should also set the 'model_type' in cocostuff_eval.json to 'vit_base.'
Thank you.

I'm really grateful to your reply, thank you very much!


Bindings - Export Functions for FFI

With #16 we are building the recipe for our libraries but nothing is exported. The task is to handle exports within gpu.h directly for the varying platforms or to provide an additional file with the exports.

Better to allow end users to wrap this themselves, may be hard to find a universal wrapper that works for all. You can see my WIP towards a wrapper for dart here.
https://github.com/MichealReed/minigpu/tree/master/minigpu_ffi/src


chore: migrate to cli-table3

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


Proposal: Add a devcontainer config for VS Code / Github Codespaces

I did not find a way to effectively integrate devbox with vscode. As the broad majority of devs are using this editor these days, this is a concern for adoption in large teams.
You can start a devbox shell in the vscode terminal, but it does not set the env of all other vscode process (tasks, debugger, extensions...)
I feel like writing a devcontainer could be a great way to fix this (and free user for the required nix dependency), but I was not successful in implementing it.

Hey @pomdtr, we'll look into this feature. Is this something you use to develop locally on your own machine as well? Or is it for remote development?

I use this workflow both on my local machine and my remote workspaces

@pomdtr We recently published the first version of devbox VSCode extension. We'll try to see if we can have the environment for the whole IDE (debugger & path to binaries and dependencies) be updated by the extension. Devcontainer seems like a possible solution as well. We'll update under this issue once we have a solution to move forward on this.

Cool ! Here is an interesting read on the devcontainer / nix interaction: https://levelup.gitconnected.com/vs-code-remote-containers-with-nix-2a6f230d1e4e

I've got a draft version working for devbox. Please take a look at it: https://github.com/pomdtr/devbox-devcontainer

@pomdtr Thanks for sharing this. I don't have codespaces enabled on my github account but I tested it locally with Docker desktop and Dev Containers extension on VSCode and it woks great. Although, it runs vscode from inside a Docker container with a shared volume between the host machine and Docker. That means in a non-Linux OS there might be a performance hit.
That said, I really liked the Dev Containers extension when it detects a .devcontainer it prompts with "Reopen this in devcontainers". Maybe we can add a similar functionality to Devbox's extension. Because if we open vscode from inside a devbox shell, the language binaries and interpreter settings in vscode will be set to devbox's shell environment.

I think the performance hit should be quite minimal since the bind mount only contains the workspace folder. There are way to mitigate the performance penalty (see : https://code.visualstudio.com/remote/advancedcontainers/improve-performance)

Ah interesting!
@pomdtr I've shared your example on devcontainer setup with Devbox with the team. Are you ok if we add it to our docs/guides?

Go ahead !

I have made some improvements on the template. The dependencies are now populated during the build, and the .devbox dir is no longer in the workspace directory (since the symlinks only work in the container).
The only issue is that the devbox cli is no longer working in the container. It would be cool to add support for setting the .devbox dir path via config.
Ex:
devbox --config .devcontainer/devbox.json --cache /devbox/.devbox

Ideally I would also like to be able to set these options using environment variable since it would allow me set them in the dockerfile
ENV DEVBOX_CONFIG=.decontainer/.devbox.json
ENV DEVBOX_CACHE=/devbox/.devbox

Thanks a ton for improving the templates! to summarize you suggestions are:

"add support for setting the .devbox/ dir path via config"
setting --config  and --cache flags using env variables
adding a devbox install command as alternative to devbox shell --config /devbox/devbox.json -- echo "Devbox Store Populated"

I'll make separate issues for them to track each independently.

Thanks a lot ! If you have some time, it would loke to get some feedback on the dockerfile. I tried to use the buildkit cache feature to reduce the build time on successive builds, but I was not successful.

@pomdtr I looked at the Dockerfile, there is not much feedback I have on making it faster. Nix installation takes some time and also first time running devbox shell after a new installation also takes time due to Nix copying stuff to /nix/store. So One idea is to have everything before calling devbox shell and publish it as a public Docker image. That way Nix and devbox get cached as a layer and subsequent runs won't install nix and devbox. Other than that, the Dockerfile looks ok imo.
For moving .devbox/ out of the workspace dir, I don't think it is supported as of now. But if there is a reason other than preference for it, we can prioritize implementing it similar to --config for custom devbox.json path.

@pomdtr we have added a feature to the VSCode extension that can generate a .devcontainer.json file and Dockerfile that works with your Devbox project. If you have a chance to try it out, we'd love your feedback on how it works! Closing this comment for now, but can reopen if there are any issues with the Extension


How can I use the capabilities of some third-party packages

I want to use cypress-mochawesome-reporter in cypress, but when I installed the npm package and configured it according to the document, running lambdatest-cypress-cli run reported an error.

my cypress.config.js
const { defineConfig } = require('cypress');

module.exports = defineConfig({
  reporter: 'cypress-mochawesome-reporter',
  e2e: {
    setupNodeEvents(on, config) {
      require('cypress-mochawesome-reporter/plugin')(on);
    },
  },
});

my package.json
{
    "name": "cypress-demo",
    "version": "1.0.0",
    "description": "",
    "main": "index.js",
    "scripts": {
        "test": "cypress run --headed"
    },
    "author": "",
    "license": "ISC",
    "devDependencies": {
        "cypress": "^12.14.0",
        "lambdatest-cypress-cli": "^3.0.15"
    },
    "dependencies": {
        "cypress-mochawesome-reporter": "^3.5.1"
    }
}

How do I install some toolkits before running the tests

I tested the lambdatest-config.json  run_settings configuration and it doesn't work
 "run_settings": {
        "reporter_config_file": "base_reporter_config.json",
        "build_name": "test-16",
        "parallels": 1,
        "specs": "./cypress/e2e/*.cy.js",
        "ignore_files": "",
        "network": false,
        "headless": false,
        "npm_dependencies": {
            "cypress": "10",
            "cypress-mochawesome-reporter": "^3.5.1"
        }
    },

I repeated the test, configuring npm_dependencies is ok


GWT build issue with Pixmap.createFromFrameBuffer

Issue details
It isn't possible to compile following code on GWT (required for taking screenshots):
Pixmap pixmap = Pixmap.createFromFrameBuffer(0, 0, Gdx.graphics.getBackBufferWidth(), Gdx.graphics.getBackBufferHeight());
ByteBuffer pixels = pixmap.getPixels();

It gives following error when compiling: Type mismatch: cannot convert from Buffer to ByteBuffer
And seems to be caused by this line, with IDE showing the line as syntax error.
It shows also this and this line as syntax error with message Cannot resolve symbol 'pixmap', but I have no idea why and it isn't causing any problems for me (most likely because I am not calling those functions).
Version of libGDX and/or relevant dependencies
1.11.0
Please select the affected platforms

[ ] Android
[ ] iOS
[x] HTML/GWT
[ ] Windows
[ ] Linux
[ ] macOS

The issue is actually with getPixels(), but it's... complicated. On all platforms except GWT, getPixels() returns a ByteBuffer. On GWT, it returns a Buffer, backed by an IntBuffer. There's some reason for this relating to how WebGL works, but I don't know the specifics. GWT has to use different sources for Pixmap and its backing data, because desktop and Android (plus more, probably) can use C++ code with JNI, while GWT cannot, and so has to use JS code to implement Pixmap operations. You can see the relevant sources used by GWT here. Ideally, we would have some way of converting the IntBuffer of pixels to a ByteBuffer like all other platforms use, but it's been a challenge so far.


[Suggestion/Question] Simplifying generation of URL's

Q
A

Bug?
no

New Feature?
yes

Framework
Laravel

Framework version
5.x.y

Package version
1.x.y

PHP version
7.x.y

Could the generation of URL's not be simplified using a Facade?
Currently we need to use:
app('Dingo\Api\Routing\UrlGenerator')->version('v1')->route('users.index');
This feels lengthly, from:
route('api.v1.users.index');
I'm thinking that something like this could be better:
DingoRoute('users.index') - Uses config.api.version to find the correct route in this case, or you could be more specific:
DingoRoute('users.index', 'v1')

Hi, I've made this PR to implement this suggestion;
https://github.com/dingo/api/pull/1641
Basically so long as you have your Dingo API facade set up in your app config, eg:
        'API' => Dingo\Api\Facade\API::class,

You can write code like this:
API::route('users.index');

Noting to import API into your file.


Customizing inputProps onBlur and onFocus on TextField

I am using react-final-form to create forms (I do not want to use redux form because I am using apollo).
The problem is that react-final-form requires inputProps onBlur and onFocus function to be injected to set meta.touched. If I inject the custom functions into inputProps, TextField loses focus animation (border color change, ripple effect, etc). Is there a way I can integrate external onBlur and onFocus functions with the material ui native onBlur and onFocus functions?
The code looks like below
    render() {
        const {
            classes, fullWidth, input: {
                name, onChange, value, ...restInput
            }, meta, label, InputProps, ...rest
        } = this.props;

        console.log(restInput);

        return (
            <MuiThemeProvider theme={theme}>
                <TextField
                    {...rest}
                    id="standard-name"
                    label={label}
                    value={value}
                    name={name}
                    fullWidth={fullWidth}
                    onChange={onChange}
                    helperText={meta.touched ? meta.error : undefined}
                    margin="normal"
                    variant="outlined"
                    inputProps={restInput}    //restInput has two functions 'onBlur' and 'onFocus'
                    error={meta.error && meta.touched}
                    InputProps={InputProps}
                />
            </MuiThemeProvider>
        );
    }

Did you check https://github.com/Deadly0/final-form-material-ui out? I'm using the following integration:
import React from 'react'
import PropTypes from 'prop-types'
import TextField from 'web/modules/components/TextField'

function RFTextField(props) {
  const {
    autoComplete,
    helperText,
    input: { name, ...input },
    InputProps,
    meta: { dirty, error, submitError, submitFailed },
    ...other
  } = props

  return (
    <TextField
      error={Boolean((dirty || submitFailed) && (error || submitError))}
      {...input}
      {...other}
      id={name}
      name={name}
      InputProps={{
        inputProps: {
          autoComplete,
        },
        ...InputProps,
      }}
      helperText={dirty || submitFailed ? error || submitError : helperText}
    />
  )
}

RFTextField.displayName = 'RFTextField'

RFTextField.propTypes = {
  autoComplete: PropTypes.string,
  helperText: PropTypes.node,
  input: PropTypes.shape({
    name: PropTypes.string.isRequired,
  }).isRequired,
  InputProps: PropTypes.object,
  meta: PropTypes.shape({
    dirty: PropTypes.bool.isRequired,
    error: PropTypes.string,
    submitError: PropTypes.string,
    submitFailed: PropTypes.bool.isRequired,
  }).isRequired,
}

export default RFTextField

I guess the component should handle chaining event handlers.

@eps1lon Don't we already handle chaining?

@serendipity1004 Do you have a reproduction we can have a look at?

I guess the component should handle chaining event handlers.

@eps1lon Don't we already handle chaining?

From the component props but not from the inputProps which is what I expected. It's weird since we clearly document that props are spread to the div but then we handle on(blur|focus|change|keydown) on the input and not on the div which is not how it's documented.
Í understand the confusion of @serendipity1004. Just spread restInput to the TextField and not inputProps.

@eps1lon Oh right.

@eps1lon you are right, if I spread over TextField it works perfect. @oliviertassinari sorry for late reply but reproduction is here https://codesandbox.io/s/4jz452p450 the first field has no hover or focus animation but the second does

@oliviertassinari  @eps1lon For checking when to log the warning is checking inputProps for an array of the props that will be overridden the most efficient way?

With a propTypes validator, yes.
But I would also like to remove the @ignore from the on* handlers that are not spread to the div. The current behavior is not documented. Usually we skip the documentation because it's inherent to react and just adds noise. I don't see it that way in this cause. Thoughts  @oliviertassinari ?

I have fixed the chaining in #17037.


Update fossa.yaml

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

trigger on push request


rename db creator script in readme to reflect current name

Oops, forgot to update the readme file when I renamed the script. Nice catch!


Installation / GUI issue - No module named 'PyQt5.sip'

Hello,
I'm very impressed by all the progress that's been made, well done!
I'm on macOS. With the latest changes, when I try to start the GUI using python -m pyleecan, having installed pyleecan in a python3 virtual environment using python setup.py install I get a ModuleNotFoundError:
 File "/Users/till/Documents/pyleecan/pyleecan/pyleecan/run_GUI.py", line 6, in <module>     from PyQt5.QtCore import QTranslator ModuleNotFoundError: No module named 'PyQt5.sip’
$pip list shows PyQt5              5.14.1      PyQt5-sip          12.7.1   as being installed. Uninstalling those two packages with pip uninstall and re-installing the required versions seems to have done the trick (I can load the GUI). Do you have any idea what could be causing this?
On another note: The current setup tries to install pyFemm, which requires pywin32, which - for obvious reasons - doesn't exist for a mac install...
Best regards,
Till

Hello,
Thank you very much for your feedback, we are currently working on making sure that pyleecan is accessible for everyone so your issue is very interesting.
Regarding the PyQt issue, can you try to install the packages on a blank python ? Another explanation could be the version of the module that are in the requirements.txt. They were set with the current version at the moment without further thought since we didn't know how we can find which is the minimum version of the module to make it work. Can you check the current version of PyQt you are using ? Do you think you can investigate these two ideas ? Unfortunately, most of us are working on Windows so for now it is complicated for us to test on other OS.
Regarding FEMM, this is an interesting case that we were discussing few weeks ago. FEMM, gmsh and deap are non-mandatory dependencies and we were wandering if we should put them in the requirements.txt file. We chose to put them to ease the use of the full package. To solve that we have two possibilities: My colleague Cedric propose that we check if it is possible to have some OS related conditions in the requirements.txt file. The other possibility could be to provide several requirements.txt with proper names and documentation headers and to develop the "How to install" page on pyleecan.org to address this issue.
Best regards,
Pierre

Hi Pierre,
the installation was done in a 'fresh' python3 virtual environment. The PyQt version initially installed (and not working) was the same as the version I re-installed, which then worked. That's why I found it strange. I'll do some more searching on the issue.
Regarding your second comment, I would think that the latter option you suggested makes sense from a practical point of view (several requirements.txt files depending on what the user wants, e.g. requirements-base/common.txt, requirements-femm.txt etc.)
Best regards,
Till

Hello,
Did you found an explanation for your error ?
At the end for the release Cédric fond the following syntax: "platform_system=="Windows" to avoid installing femm on other platform. Then FEMM and GMSH are addressed on https://pyleecan.org/get.pyleecan.html
Best regards,
Pierre

Hello Everyone,
I am having a problem in launching Pyleecan GUI.
The error message is: (This application failed to start because no Qt platform plugin could be initialized. Reinstalling the program may fix this problem).
If anyone is familiar with some solution, please let me know.
Thank you.

Hello,
What version of python / pyleecan are you using ? How did you install pyleecan (pip or git clone ?)
If you are using Anaconda, you need to set the following windows environment variables:
name: QT_QPA_PLATFORM_PLUGIN_PATH
value: "path_to_anaconda"\anaconda3\Lib\site-packages\PySide2\plugins\platforms
Best regards,
Pierre Bonneel

Hello Pierre Bonneel. Thank you for your response.
I am using Python 3.8.3 and Pyleecan 1.0.2 version. Aslo Anaconda latest version. When I try to lauch GUI using notebook it was gives this error.(This application failed to start because no Qt platform plugin could be initialized. Reinstalling the program may fix this problem).
But when I tried to launch using shell it worked. Thanks again.
I am exploring Pyleecan and I think its very good open source project. In my PhD, I am working on the design of LSPM(Line Start Permanent Magnet) Motors. And I am looking to contribute in Pyleecan for LSPM module.

Hello Pierre Bonneel. Thank you for your response.
I am using Python 3.8.3 and Pyleecan 1.0.2 version. And also Anaconda latest version. When I try to lauch GUI using notebook it was gives this error.(This application failed to start because no Qt platform plugin could be initialized. Reinstalling the program may fix this problem).
But when I tried to launch using shell it worked.
I am exploring Pyleecan and I think its very good open source project. In my PhD, I am working on the design, vibro-acoustic analysis and Optimization of LSPM(Line Start Permanent Magnet) Motors. And I am looking to contribute in Pyleecan for LSPM module. Thanks again.

Great news :) Feel free to open an issue to talk about LSPM. We are looking for topologies, reference machine and publications to structure our thought. Maybe you can start by sharing pictures/schematics of the machines you want to simulate. The further the discussion will go, the easiest it will be to start contributing on LSPM ;)
Best regards,
Pierre


How to use multiple forces at once?

I'm interested in playing with custom forces, as well as combining in some other graph layout techniques for minimizing edge crossings (stuff like this tabu search layout idea).
Is there a suggested way of combining multiple forces?  Should I create multiple Simulations and step through them in a custom event loop?  Or is there a shortcut for doing this kind of thing?

I've been checking out the changes in the dev branch and I really like the API.  It's clean and straightforward.  I used it to create an edge-crossing minimizing optimization force that swaps positions of nearby nodes in search of an optimal permutation: https://github.com/micahscopes/cobwebs-2024/blob/main/src/grid_wanderer.rs#L25
The only thing that was a little tricky was that I needed to add a lot of type constraints for the node and edge types in order to get the position swapping to work.
(As far as layout goes, it sort of works but it's not very flexible. It only searches the node position permutation space.  I think it'd be good to actually move the nodes themselves around on a grid and search that space instead as well.)


Add security policy

Codecov Report

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

@@           Coverage Diff            @@
##             master      #6   +/-   ##
========================================
  Coverage      87.5%   87.5%
  Complexity       12      12
========================================
  Files             5       5
  Lines            32      32
  Branches          4       4
========================================
  Hits             28      28
  Misses            2       2
  Partials          2       2

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 83b9684...09fd727. Read the comment docs.


Android - Scan - Uploading corrupt pdf as scan receipt, error not shown under preview

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

Version Number: 1.4.67
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/runs/view/20905&group_by=cases:section_id&group_order=asc&group_id=294998
**Issue reported by:**Applause - Internal Team
Action Performed:

Launch app
Tap on a workspace report
Tap plus icon -- submit expense -- scan
Upload a corrupt pdf
Tap submit expense

Expected Result:
Error message "Receipt didn't upload, download the file or dismiss this error" under preview must be shown in conversation page
Actual Result:
Error message "Receipt didn't upload, download the file or dismiss this error" under preview not shown in conversation page
Workaround:
Unknown
Platforms:

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

[x] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/194662d4-138a-4d02-833f-c878d1edcfc2

View all open jobs on GitHub

@puneetlath  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

We think that this bug might be related to #vip-vsp

Proposal
Please re-state the problem that we are trying to solve in this issue.
The scan request error in transaction thread shows a generic error message instead of "Receipt didn't upload, download the file or dismiss this error".
What is the root cause of that problem?
When we create a new scan request, we set a generic error to the transaction when fails.
https://github.com/Expensify/App/blob/2a1c2cb16b9b5234ad05518be46d95d6bcaa2f56/src/libs/actions/IOU.ts#L737-L739
But for the report action, we set the receipt error correctly.
https://github.com/Expensify/App/blob/2a1c2cb16b9b5234ad05518be46d95d6bcaa2f56/src/libs/actions/IOU.ts#L753
What changes do you think we should make in order to solve the problem?

Set the receipt error for the transaction too.
errors: getReceiptError(transaction.receipt, transaction.filename || transaction.receipt?.filename, isScanRequest, errorKey),

We need to do this for other request too such as invoice/track.

PR is ready
cc: @fedirjh

@fedirjh offer: https://www.upwork.com/nx/wm/offer/102440614
@bernhardoj offer: https://www.upwork.com/nx/wm/offer/102440609
Please ping me here when you've accepted

@puneetlath thanks, accepted


Enabler: ServiceBus Communication - 2 - Implementing ServiceBus Channel

As a develop
I want to make a ServiceBus implementation of GreenEnergyHub.Messaging.Transport.Channel using the AMQP-protocol
So that I can use the communication method used by the rest of the ART
For now, it is out of scope to move the changes to shared code, that is, we keep it locally in our domain.
The purpose of this story is to implement a class that is capable of transmitting a byte array onto the ServiceBus using the AMQP protocol. This class be inherit from the abstract class Channel which is part of the messaging communication strategy for outgoing messages.
A diagram of the outgoing classes can be seen below, including the Channel class which we will make a specialization of.
ACs:
AC1: An implementation of GreenEnergyHub.Messaging.Transport.Channel using AMQP to talk to the the ServiceBus has been made.
AC2: We must be able to demonstrate that a bytearray passed to the channel ends up on the ServiceBus

AC1: Has been added as part of https://github.com/Energinet-DataHub/geh-charges/pull/181
AC2:
Since we are currently not using the code, I added a test that can be manually run to send to a servicebus.
As can be seen in this screenshot, the message appeared as expected

The test is called WriteAsync_WhenManuallyRun_EndsUpOnServiceBus.

As a tester I tested the issue by executing the mentioned unit test manually and seeing the message ending up in the service bus topic as expected.


feat: update wallet stardust alpha

Summary
Update wallet to 1.0.14
Changelog
- update @iota/wallet
- added @iota/types

Relevant Issues
closes: https://github.com/iotaledger/firefly/issues/3295
Type of Change
Please select any type below that is applicable to your changes, and delete those that are not.

[ ] Breaking - any change that would cause existing functionality to not work as expected
[ ] Chore - refactoring, build scripts or anything else that isn't user-facing
[ ] Docs - changes to the documentation
[ ] Fix - a change which fixes an issue
[ ] New - a change which implements a new feature
[x] Update - a change which updates existing functionality

Testing
Platforms
Please select any platforms where your changes have been tested.

Desktop

[ ] MacOS
[x] Linux
[ ] Windows

Mobile

[ ] iOS
[ ] Android

Instructions
Please describe the specific instructions, configurations, and/or test cases necessary to test and verify that your changes work as intended.
Checklist
Please tick all of the following boxes that are relevant to your changes, and delete those that are not.

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or modified tests that prove my changes work as intended
[ ] I have verified that new and existing unit tests pass locally with my changes
[ ] I have verified that my latest changes pass CI workflows for testing and linting
[ ] I have made corresponding changes to the documentation

The code looks good, but I am still getting the same error with the validator errors.


Meter version in Getting Started = Library version - does this makes sense?

What needs to be changed?
The Getting Started section says:

In order to create traces or metrics, you’ll need to first create a tracer and/or meter provider. In general, we recommend that the SDK should provide a single default provider for these objects. You’ll then get a tracer or meter instance from that provider, and give it a name and version. The name you choose here should identify what exactly is being instrumented – if you’re writing a library, for example, then you should name it after your library (for example com.legitimatebusiness.myLibrary) as this name will namespace all spans or metric events produced. It is also recommended that you supply a version string (i.e., semver:1.0.0) that corresponds to the current version of your library or service.

I was under the impression that you shouldn’t place the version of the library or the version of your app in the meter version name.
I thought it signified the version of the metrics in some way.
What is correct?
What is the name + path of the page that needs changed?
https://github.com/open-telemetry/opentelemetry.io/blob/main/content/en/docs/concepts/instrumentation/manual.md#configure-the-opentelemetry-api
Additional context:
Related Slack threads with @trask https://cloud-native.slack.com/archives/C014L2KCTE3/p1706822636127569?thread_ts=1706796820.799869&cid=C014L2KCTE3

Thanks for raising this issue @asafm
We follow the suggestions from the specification here, see the following:
https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/api.md?plain=1#L133

version: Specifies the version of the instrumentation scope if the scope
has a version (e.g. a library version). Example value: 1.0.0.

Also, the glossary states the following (https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/glossary.md?plain=1#L155):

A logical unit of the application code with which the emitted telemetry can be
associated. It is typically the developer's choice to decide what denotes a
reasonable instrumentation scope. The most common approach is to use the
instrumentation library as the scope, however other
scopes are also common, e.g. a module, a package, or a class can be chosen as
the instrumentation scope.

If the unit of code has a version then the instrumentation scope is defined by
the (name,version) pair otherwise the version is omitted and only the name is
used. The name or (name,version) pair uniquely identify the logical unit of the
code that emits the telemetry. A typical approach to ensure uniqueness is to use
fully qualified name of the emitting code (e.g. fully qualified library name or
fully qualified class name).

This is fairly broad, but to me this sounds that the version & name of the library is a possible choice.

Yeah, my personal take here is that you probably don't actually need a version in code:

It really ought to be a best practices that your telemetry is a part of your application, which means that as your app changes versions, so does your telemetry, and these two things are one and the same. A resource with service version is probably the better way to track this
If you need to version how you instrument separately from your application you're in confuse-o-tron complexity happy fun time land, sorry to say
Some languages don't have a good way to pull in the version of what you're doing into code in a way that lets you bump a version once

also I may have written some of the docs that say you should add a version, or at least supplied the code samples that imply it, so mea culpa

@cartermp Was the initial motivation to help expose the version of the app or perhaps the used-libraries version, when browsing the metrics?

I think things are different for an instrumentation scope within an app (or a library) and for an instrumentation scope that marks the entry into an (external) library/into the instrumentation library.
Imagine the following scenario: I have a service of version 2.3 deployed 10 times. Now for whatever reason 2 of those instances use a depending library "mylibo" in version 1.3, although the other 8 ones use version 1.4, which has an important fix, or creates telemetry differently, then that version becomes very helpful.

Maybe we should clarify - version should be used for libraries mostly?

Maybe we should clarify - version should be used for libraries mostly?

Yes, or more broadly "with things that have a version, like libraries and applications"

So I'm a bit confused. If I'm using OTel to instrument an application, should I use the service or meter versions?
For libraries, it seems clear, at least to me, that the library version should be used.

@asafm I'd still recommend that for your own application instrumentation (i.e., instantiating your own Meter or Tracer for your app internals only), then I wouldn't include a version.
However, any other time - including libraries that are only internal to your application - then a version makes sense.
That's just my recommendation/opinion, though. I think that for an application, code and instrumentation changes all the time without tying to a specific version, and so trying to include one would just make things harder in the long run.

I'm trying to figure out what is agreed upon, so we can update the getting started page text.

sorry all, I misread the original question and thought it was about encoding a version into the instrumentation scope name, e.g. mylib:1.0.0.
my only recommendation for the docs would be to change the example version from semver:1.0.0 to 1.0.0 (I think my brain told me that semver was a library name 😭).

Was the initial motivation to help expose the version of the app or perhaps the used-libraries version, when browsing the metrics?

the motivation is so that you can identify changes in the telemetry caused by changes to the instrumentation library

If I'm using OTel to instrument an application, should I use the service or meter versions?

I'm not sure what is the meter version?

I'm not sure what is the meter version?

In Meter version I meant the Instrumentation Scope version (Defined as version in getMeter at https://opentelemetry.io/docs/specs/otel/metrics/api/#get-a-meter)
Regarding service version - Meant this https://opentelemetry.io/docs/specs/semconv/resource/#service. The semantic resource.
Should an application (not a library) avoid using the meter version, but place the version using the service version?

The application version and the instrumentation scope version may be the same if the instrumentation scope is the "application". I am not really sure if this is good/bad practice.

Should an application (not a library) avoid using the meter version, but place the version using the service version?

I'd personally choose to err on the side of sending both (at least for an OSS application like Apache Pulsar which will have many different telemetry consumers, and so hard to know which version metadata will be useful/used or not).

Ok guys, thanks a lot for this discussion. It made me understand we should use meter version which should match the library version or the application version.
This means the original getting started guide text matches that, hence I can close this issue.


Add #[reflect(Serialize, Deserialize)] with serialize feature

Objective
The serialize feature adds serde support and derives Serialize and Deserialize for some types, but those types don't have Bevy's ReflectSerialize/ReflectDeserialize.
Solution
Add #[reflect(Serialize, Deserialize)] to reflected types when the serialize feature is enabled.

Closing in favor of #395, which has been merged already.


General improvements to the request handling stability

I've added the following changes...

Handles cases where request requires multiple reads of
the socket.
Added ability to specify a request timeout to mitigate DOS
situations. The connection is simply closed after the timeout
elapses.
Encountering an invalid HTTP token now just causes the connection
to be closed instead of panicking.
The server will now return a "413 Payload too large" if the request
exceeds the maximum request buffer size instead of panicking.

I realise it's quite a big commit and may be overreaching slightly but I've found a genuine use case for this library and all the above are required.

Looks like my rustfmt settings conflict with the CI's 🤷♀

i've only briefly read this but it looks great. will take a closer look in a bit but wanted to say thank for the contrib!

Looks like my rustfmt settings conflict with the CI's 🤷♀

Are you using rustfmt or rustfmt-nightly?

@steveklabnik I was using rustfmt-nightly, yeah. I guess nightly has a different code style!

I've rebased this, @ashleygwilliams is gonna give it another look-over shortly


Feat (bpdm-certificate-management) - Addition of Authentication (OAuth2)

Description
To enhance the security of the BPDM Certificate Management application by implementing OAuth 2.0 authentication for endpoint access with significant enhancements to the security of our API endpoints by implementing Role-Based Access Control (RBAC) using JWT claims and Spring Security. Configuration has a base on the main bpdm app.
Contributes to #25
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[x] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[x] Copyright and license header are present on all affected files

The out folder has been committed as well by accident. This should be removed from the pull request and also entered into the git ignored list.

Removed and added to gitignore file too

Looks good except the autonfiguration class. I don't think it's needed here and at least should be renamed but better just removed

Removed autoconfiguration class.


Ablation study on the MOT17 validation set

Hello, in the ablation experiment part of the paper, MOTA can reach 77.66 of your reproduced ByteTrack (Baseline), while the official ByteTrack Only 76.6 is in the same validation set. When I use tracking threshold of 0.6, new track threshold of 0.7 and, ﬁrst association matching threshold of 0.8 pointed out in your paper ， the official byteTrack can only reach 76.2. Can you tell me how to get ByteTrack (Baseline) results in the ablation experiment part of your paper.

Hello, The difference is that ByteTrack calculated the MOTA within their code while I used TrackEval for evaluation - refer to TrackEval/issues#75.

Hello, in the ablation experiment part of the paper, MOTA can reach 77.66 of your reproduced ByteTrack (Baseline), while the official ByteTrack Only 76.6 is in the same validation set. When I use tracking threshold of 0.6, new track threshold of 0.7 and, ﬁrst association matching threshold of 0.8 pointed out in your paper ， the official byteTrack can only reach 76.2. Can you tell me how to get ByteTrack (Baseline) results in the ablation experiment part of your paper.

Hello, in the ablation experiment part of the paper, MOTA can reach 77.66 of your reproduced ByteTrack (Baseline), while the official ByteTrack Only 76.6 is in the same validation set. When I use tracking threshold of 0.6, new track threshold of 0.7 and, ﬁrst association matching threshold of 0.8 pointed out in your paper ， the official byteTrack can only reach 76.2. Can you tell me how to get ByteTrack (Baseline) results in the ablation experiment part of your paper.
hoew you get the result like 77.66?


somebody help me pls

Describe your problem here.
idk how fix this error
source/flixel/system/FlxSound.hx:3: characters 1-8 : Unexpected package
please help me :(
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
no

what is your version of haxe?

Haxe 4.2.5
Flixel 4.11.0
Flixel-addons 2.11.0


Missing Icons

Hi Ankurk91,
My trumbowyg icons appear to be missing.
I have installed via npm in laravel 5.6.7:
"trumbowyg": {
"version": "2.9.4",
"vue-trumbowyg": {
"version": "3.1.2",

Webpack file:
mix.autoload({
    'jquery': ['$', 'window.jQuery', 'jQuery'],
    'vue': ['Vue','window.Vue'],
})

mix.js('resources/assets/js/app.js', 'public/js')
   .sass('resources/assets/sass/app.scss', 'public/css');

mix.copyDirectory('node_modules/trumbowyg', 'public/trumbowyg');

vue component:
<template>
    <div>
        <trumbowyg v-model="content"></trumbowyg>
    </div>
</template>

<script>
    // Import this component
    import trumbowyg from 'vue-trumbowyg';

    // Import editor css
    import 'trumbowyg/dist/ui/trumbowyg.css';

    import svgIcons from 'trumbowyg/dist/ui/icons.svg';

    export default {
        data () {
            return {
                content: '',
            }
        },
        components: {
            trumbowyg
        }
    }
</script>

Still nothing, any ideas?
Thanks,
Tom

May in know your Laravel mix version, i think you are using v2.x ?

Yup,
"laravel-mix": {
"version": "2.0.0",

I am looking into it.
Just to let you know, you no need to import  svg icons, the component is already doing this for you.

Thanks 👍

And make sure you have jquery installed

To be honest i have not tested it with Laravel mix v2.0
v2.0 handles svg files differently now.
https://github.com/JeffreyWay/laravel-mix/pull/1367
Do you see any errors in console ?
Everything else in editor is loading properly and just icons are missing ?

No errors in console,
But looking at the icons.svg the file looks small/empty, should there be data inside?

Ok,
A quick workaround is to pass your custom svg icon file path via prop.
 <trumbowyg
              v-model="form.content"
              class="form-control"
<EMAIL_ADDRESS>              :config="configs.basic"></trumbowyg>

Also can you try disabling image optimization by Laravel mix
// webpack.mix.js
mix.options({
  imgLoaderOptions: {
    enable: false
  },
});

Hmmm, getting a vue error in console when adding ,

Don't copy my code blindly. All you need to do is add this prop to your component
<EMAIL_ADDRESS>

My Apologies, I misunderstood.
Yup - icons are now loading correctly with the workaround. :)
This should be fine as I don't need the icons locally.
Many thanks for your help Ankurk, it's greatly appreciated.

Glad to know.
I will test it with Laravel mix v2.x soon and will post back here.

I can confirm that this is img-loader issue in Laravel-mix.
Disabling image loader fixes this issue.
Here is how to fix this issue:
// webpack.mix.js
mix.options({
  imgLoaderOptions: {
    enabled: false
  },
});


bug: css on mobile view

Awesome theme 👍🏾  I love it. Thanks for releasing v2.0.0 shortly. I am stumbling over some minor bugs, such as follows:
The element wrapping of the reading time and word count could be fixed to wrap correctly the the new line. See the screenshot

@mavogel This has been addressed

Awesome :) Thanks for the fast fix


Optimize Backend::Simple#available_locales

Previously available_locales was a little bit slow. For each locale in translations it would:

build a new array of all the top-level keys in that locale
build a second array of those keys except :i18n
add that locale to the list if the second array was not empty

For locales with many translations this can build somewhat sizeable arrays.
Instead we can perform the same operation, rejecting locales with either no keys or only :i18n without allocating any new objects. We reject based on the condition:
data.size <= 1 && (data.empty? || data.has_key?(:i18n))

This ends up being about 4x faster (though this of course depends on the exact locales being used):
Benchmark.ips do |x|
  x.report("I18n.available_locales") do
    I18n.available_locales
  end
end

Before:
11.447k (± 2.9%) i/s -     57.869k in   5.059738s

After:
47.810k (± 2.8%) i/s -    242.060k in   5.067332s

Many thanks @jhawthorn :) Glad to see you're still alive and kicking!

I should also mention: this change will go out in 0.9.4. I am waiting on #407 to be confirmed before doing that release.