Shaping the future of Backends

What is your issue?
Backends in xarray are used to read and write files (or in general objects) and transform them into useful xarray Datasets.
This issue will collect ideas on how to continuously improve them.
Current state
Along the reading and writing process there are many implicit and explicit configuration possibilities. There are many backend specific options and many en-,decoder specific options. Most of them are currently difficult or even impossible to discover.
There is the infamous open_dataset method which can do everything, but there are also some specialized methods like open_zarr or to_netcdf.
The only really formalized way to extend xarray capabilities is via the BackendEntrypoint. Currently only for reading files.
This has proven to work and things are going so well that people are discussing getting rid of the special reading methods (#7495).
A major critique in this thread is again the discoverability of configuration options.
Problems
To name a few:

Discoverability of configuration options is poor
No distinction between backend and encoding options
New options are simply added as another keyword argument to open_dataset
No writing support for backends

What already improved

Adding URL and description attributes to the backends (#7000, #7200)
Add static typing
Allow creating instances of backends with their respective options (#8520)

The future
After listing all the problems, lets see how we can improve the situation and make backends an allrounder solution to reading and writing all kinds of files.
What happens behind the scenes
In general the reading and writing of Datasets in xarray is a three-step process.
                       [ done by backend.open_dataset]
Dataset < chunking   < decoding < opening_in_store < file
Dataset > validating > encoding > storing_in_store > file

Probably you could consider combining the chunking and decoding as well as validation and encoding into a single logical step in the pipeline. This view should help decide how to set up a future architecture of backends.
You can see that there is a common middle object in this process, a in-memory representation of the file on disc between en-, decoding and the abstract store. This is actually a xarray.Dataset and is internally called a "backend dataset".
write_dataset method
A quite natural extension of backends would be to implement a write_dataset method (name pending). This would allow backends to fulfill the complete right side of the pipeline.
Transformer class
Due to a lack of a common word for a class that handles "encoding" and "decoding" I will call them transformer here.
The process of en- and decoding is currently done "hardcoded" by the respective open_dataset and to_netcdf methods.
One could imagine to introduce the concept of a common class that handles both.
This class could handle the implemented CF or netcdf encoding conventions.
But it would also allow users to define their own storing conventions (Why not create a custom transformer that adds indexes based on variable attributes?)
The possibilities are endless, and an interface that fulfills all the requirements still has to be found.
This would homogenize the reading and writing process to
Dataset <> Transformer <> Backend <> file

As a bonus this would increase discoverability of the configuration options of the decoding options (then transformer arguments).
The new interface then could be
backend = Netcdf4BackendEntrypoint(group="data")
decoder = CFTransformer(cftime=True)
ds = xr.open_dataset("file.nc", engine=backend, decoder=decoder)

while of course still allowing to pass all options simply as kwarg (since this is still the easiest way of telling beginners how to open files)
The final improvement here would be to add additional entrypoints for these transformers ;)
Disclaimer
Now this issue is just a bunch of random ideas that require quite some refinement or they might even turn out to be nonsense.
So lets have a exciting discussion about these things :)
If you have something to add to the above points I will include your ideas as well. This is meant as a collection of ideas on how to improve our backends :)

see also #5954 for a previous discussion of the write_dataset idea (the name I proposed there was xr.save_dataset to be symmetric with save_mfdataset)

Due to a lack of a common word for a class that handles "encoding" and "decoding" I will call them transformer here.
The process of en- and decoding is currently done "hardcoded" by the respective open_dataset and to_netcdf methods.
One could imagine to introduce the concept of a common class that handles both.
This class could handle the implemented CF or netcdf encoding conventions.

Doesn't this already exist as xarray.coding.VariableCoder? It has .encode and .decode methods. Are we basically just taking about making it public and allowing users to pass in custom subclasses of VariableCoder, and generalizing xarray.conventions to be configurable for non-CF cases?

(Why not create a custom transformer that adds indexes based on variable attributes?)

On the other hand this suggestion seems to be something that could not be immediately handled by the current VariableCoder design.

Agree that these "transformers" are called "coders" ATM, linking this quite old proposal! https://github.com/pydata/xarray/issues/155

Can these transformers/coders just be new zarr codecs? Exposing xarray's decoding logic in a way that follows that interface would allow for zarr to become a "universal reader" - see https://github.com/zarr-developers/zarr-specs/issues/303.


unable to debug express project

VSCode Version:1.3.1
OS Version:ubuntu 16.4 , osx el capitan

Steps to Reproduce:

create a debug point
if the debug point is global get following error

node: ../../nan/nan_object_wrap.h:33: static T* Nan::ObjectWrap::Unwrap(v8::Local<v8::Object>) [with T = Canvas]: Assertion `object->InternalFieldCount() > 0' failed.

@NikosEfthias Pls provide concrete steps with concrete source and node and npm version numbers how to reproduce the problem so that we don't have to guess. Thanks a ton!

npm 3.9.5
node 6.2.2
the debug point is created as you see in the photo and debugger fails again as you can see in the photo

when i run app with node itself theres no problem the app runs but the vscode debugger reports error

@NikosEfthias can you provide a bit more information about what your workspace contains. npm package dependencies etc. Thanks.

@NikosEfthias the error is not reported by VS Code but by the node itself. Could you please try the same with node-inspector. Thanks.

@NikosEfthias I assume with 'debug point' you mean a 'break point', correct?
But what do you mean with 'global debug point'?

İ meant a break point that is on the goal scope in my program not in the scope of any function if I create a break point in a function I don't get this error @weinand

@NikosEfthias are you getting the node error when setting the breakpoint or when hitting the breakpoint?

@weinand there is no node error if i run app with nodejs it works without any issue .
and when i put a break point inside a fonction it still works perfect but if i put break point to somewhere in the global scope when it hits the point debugger crashes

@NikosEfthias the error message does not originate from VS Code but comes from some native code used in the 'nan' npm module. The 'nan' module is not used in the VS Code debugger, so it must be a direct or indirect dependency of your express program.
If your express program 'runs in node without problems' does not mean much if you do not run node in debug mode. So you will have to pass the '--debug' or '--debug-brk' flag to node if you want to prove that your programs 'runs without any issues'. In addition you will have to attach a different debugger than VS Code to node and hit a breakpoint successfully in order to prove that VS Code is the culprit.
That's the reason why I've suggested that you try to reproduce the problem with the 'node-inspector' debugger. If that works then we can be sure that VS Code is the culprit.
Alternatively you can do the following to help us understand the problem:

install some older node version, e.g. 5.10 and try to reproduce the problem,
make your project available and I will try to reproduce the problem on my side.

i cannot reproduce the  same issue with node inspector it just works fine

@NikosEfthias thanks, so this is a VS Code bug. But without reproducible steps I cannot investigate.

i cannot share the project i am writing but i am using canvas module it can be because of this though i am not sure
canvas is a native c++ module

seems on new vscode version no solution to this bug yet

@NikosEfthias without a reproducible case I cannot investigate.

is there any way to debug without sharing the entire code ? could you check remotely ?

I faced the same problem again, and again I am using the node-canvas module . Here is my snippet that you can reproduce the issue with:
const barc = new (require("barcode-generator"))
const fs = require("fs");
var Canvas = require('canvas')
	, Image = Canvas.Image
	, canvas = new Canvas(340.818, 226.77, 'pdf')
	, ctx = canvas.getContext('2d');
// const printer = require("printer");
let coupon = {
//someData
}
var cell = 35.008;
var margin = 11.171;
var fontSize = 22;
var draw = function () {
	data = "123456test"
	ctx.beginPath();
	ctx.textBaseline = "hanging";
	ctx.font = "18px monospace";

	ctx.strokeStyle = "#3C3C3C ";

	var img = new Image;
	var barcode = barc.code128(data, 200, 35);
	img.src = barcode;

	ctx.drawImage(img, 18.488, 172.448);

	coupon.card.numbers.map(function (r, row) {
		coupon.card.numbers[row].map(function (c, num) {
			ctx.strokeRect(margin + cell * num, margin + row * cell, cell, cell);

			if (c.number) {
				var left = c.number > 9 ? 7 : 12;
				ctx.fillText(c.number, margin + cell * num + left, margin + row * cell + 12);
			} else {
				ctx.fillRect(margin + cell * num, margin + row * cell, cell, cell);
			}

		});

	});
	const now = new Date(coupon.created_at)
	function padDate(dateObj) {
		const {getFullYear: yr, getMonth: mn, getDay: day} = now
		let date = yr.call(now) + "-"
		date += mn.call(now) < 10 ? mn.call(now).toString().split().unshift("0").join("") : mn.call(now)
		date += "-"
		date += day.call(now) < 10 ? day.call(now).toString().split().unshift("0").join("") : day.call(now)
		return date
	}
	ctx.font = "12px monospace";
	ctx.fillText("Kupon No:", margin, 138.8865);
	ctx.fillText("Fiyat   :", margin, 156.0101);
	ctx.fillText("Oyun No:", 200.6822, 138.8865);
	ctx.fillText("Tarih  :", 200.6822, 156.0101);
	ctx.fillText(coupon.cardId, 88.5042, 138.8865);
	ctx.fillText(coupon.cardPrice + ' TL', 88.5042, 156.0101);
	ctx.fillText(coupon.gameIndex, (238.3564 + 25.0), 138.8865);
	ctx.fillText(/*coupon.created_at*/padDate(), (238.3564 + 25.0), 156.0101);
}
draw();

I run into same issue with node-opencv.
Env: VSCode 1.11.2, node 7.6.0 (same issue with older ones like 6.x), npm 4.1.2
Reproduce info:
in package.json:
"dependencies": {
"opencv": "^6.0.0"
}
hello.js:
const cv = require('opencv'); //set a breakpoint here and step over to reproduce
// or set a breakpoint at any line after require()
Additional Info:

The same program runs fine from command line, even from VSCode built-in terminal.
In VSCode, run without breakpoint works fine.
VSCode attach to "node --debug-brk=5858 --nolazy hello.js" has same issue.
To launch by node-debug then step in chrome shows same issue, so that it most likely is an issue of node itself.

Well, seems we may narrow down to legacy debug protocol support. When I use "node --inspect --debug-brk face.js" (requires Node.js 6.3+), VSCode debug works.

@NikosEfthias I am not able to reproduce your problem with your code snippet from Oct 10, 2016 and VS Code 1.11.2 and node.js 6.5 and 7.4.
Setting breakpoints and hitting them works fine bot in Ubuntu 16.04 and macOS 10.12.4.
I've installed the "barcode-generator" and then the dependency "cairo" by following the steps on https://www.npmjs.com/package/canvas.
"npm install" seems to build some native code, so make sure that you run "npm install" again after installing a new version of node.js.


Re-enable PyLint

Prerequisites

[X] I checked the documentation and made sure this feature does not already exist.
[X] I checked the existing issues to make sure this feature has not already been requested.
[X] I have read the code of conduct before creating this issue.

Problem
No response
Feature / Solution
Currently PyLint is disabled in CI and running it on the code-base gives some errors. Run it, address the issues and re-enable it in CI.
Alternatives
No response
Additional Context
No response

PR: #251


Fix CI in newer Python versions

To my surprise, the CircleCI checker is still there, but then I deactivated it in https://github.com/pygae/galgebra/settings/hooks .

Notes on local testing various Python versions on my Mac:
brew install pyenv
pyenv install 3.9
pyenv init
source ~/.zprofile
pyenv shell 3.9
pip install -e .
pip install -r test_requirements.txt
pip install jupyter
jupyter notebook
pytest --nbval examples/ipython/Terminal.ipynb --current-env --sanitize-with test/.nbval_sanitize.cfg

All CI green. The code coverage drop is due to adding a conftest.py. Merging.


b key not going through

Seems like a PEBCAK (or perhaps its a practical joke?) but when I press the 'b' key into rshell, it doesn't do anything.  All other keys work fine, and b works fine everywhere else. On OSX, running rshell 0.0.6. I'm testing with an esp8266 board, but it does this even without a connection to the board.

Sounds very strange. It seems to be working fine for me.
1997 >rshell
Welcome to rshell. Use Control-D to exit.

No MicroPython boards connected - use the connect command to add one

/home/dhylands> boards
No boards connected
/home/dhylands>

I'm away from home this week, but I'll try it on my Mac when I get home.

I can confirm, have the same issue
rshell version 0.0.8
tested with tmux or without
under iTerm and Terminal
Maybe related to readline ?
What can I do to help ?

Did you disconnect any other terminal software connected to the pyboard? (just making sure because I've seen this cause all kinds of weird behaviour).
I just tried 0.0.8 on my Mac Mini (which is running OS X Yosemite - 10.10.5)
dhylands@dave-mini ~
504 >rshell --version
0.0.8
dhylands@dave-mini ~
505 >rshell
Connecting to /dev/cu.usbmodem642 ...
Welcome to rshell. Use Control-D to exit.
repl
Entering REPL. Use Control-X to exit.
>
MicroPython v1.8.6-205-g91359c8-dirty on 2016-12-19; PYBv1.0 with STM32F405RG
Type "help()" for more information.
>>>
>>> print('abc')
abc
>>>

that was ssh'ing into the mini.
Does using the --nocolor option make things behave any differently?
rshell uses python's Cmd module, so it doesn't even process the input directly. cmd.py calls sys.stdin.readline() to get its input. So this script:
import sys
print('Enter some text')
line = sys.stdin.readline()
print("Read '" + line + "'")

should be doing the same thing as rshell.
I tested using Terminal as well and everything seems to be working fine.
Do you get the same results when using the virtual keyboard (http://osxdaily.com/2013/06/21/mac-virtual-keyboard-os-x/)

When you launch rshell, there are 2 modes. The first is command mode where you type stuff like the repl command and commands to copy files. Then there is the repl mode.
Does the b key not work in both modes? Or just one? The repl mode doesn't use Cmd's input mechanism, so if it was isolated to one mode or the other that might provide useful information.

I have had strange things happen depending on hardware and which terminal app I am using. Screen with Mac and Linux seems to be the most solid.

I have had strange things happen depending on hardware and which terminal app I am using. Screen with Mac and Linux seems to be the most solid.

In this case, rshell is the terminal program, and any other teminal programs (just as screen) need to be disconnected from the pyboard.

Same issue when using Terminal in OS X 10.11.6 on Sparkfun's ESP32 Thing board

Same for me, on OSX el capitan, running rshell with robotdyn uno esp8266 (ch340 usb driver), not able to connect (no problem with screen)
With my wemos mini D1 (ch340 driver), I'm able to connect, all commands work fine except b key

Having this issue as well, thing I noticed on my system (Mac, Sierra)
-Its only lowercase 'b', Uppercase works fine.
-It's giving feedback via error sounds when pressed.
-Happens once I enter rshell, connected to a board or not. But only in command mode, once I enter shell (shell command) or repl (repl command) lowercase 'b' works fine.
Such an odd issue.

Oh,
now it gets me (i don't have this issue). But, I am using '\b' printed in python on Windows 7 to generate the bell sound (was pc speaker in the older days, now it's a windows sound).
So isn't it this kind of problem? rshell prepresenting the lower be as the \b char ?
(it's from a group of \n and \t control chars)
but now i see it's '\a' for bell. and \b for backspace.. so maybe not..
https://en.wikipedia.org/wiki/Control_character

It sounds like somebody thinks that the control key is being pressed. rshell doesn't actually do any input processing itself when in command mode, that's all done by Cmd (a library that comes with python).
When you get into this situation, does pressing and release either left and/or right control keys a few times change anything? i.e. just press and release the left control key a few times and then press the b, and then repeat with the right control key (I'm assuming that the mac keyboards have a control key).

I don't know if this is related, but on pyqt (and qt in general) on Mac,  the control modifier flag refers to the command key, and vice versa.

I just got a new MacBook Pro and was able to reproduce the problem.
The problem is related to readline. Older versions of python/OSX used libedit. Newer versions use the actual GNU readline. The libedit command to enable tab completion caused the b key to get bound incorrectly when run with readline.
I committed a fix that should work on old and new versions.

Fixed in 5f05d8b870ea91d02d33937701ac629c02dea401


Part Boxes Issue in Test_all_part.pkl  file

When I run the testing command of HICO-DET in Instance-level-detection, I check the Test_all_part.pkl file carefully. I found that all part boxes in this file are all the same. There must be something wrong when running the PaStaNet. How does this happen?
Here is the screenshot.:

This is not a bug. Please notice the previous item, which is a list of length 51. This all-zero list indicates that none of the human key points is detected by AlphaPose. Therefore, the part boxes are all assigned default value: human box.

Thanks for your replay! In this image, there are two items in the pkl file. I just made a mistake. I correct it right now. And here comes the new question: I visualize all part boxes , but it seems......bad. Is this right?

Yes. This is because the pre-defined ratio might be in-flexible. For detailed information, you could take reference from https://github.com/DirtyHarryLYL/HAKE-Action/blob/Instance-level-HAKE-Action/script/part_box_generation.py

Thanks a lot!


Display the # of Files selected in the displayed folder.

Display the # of Files selected in the displayed folder.

added in https://github.com/ganeshrvel/openmtp/issues/99


1.15 rc2 hotfix keyerror

Pull Request Checklist:

[x] Positive Test Case Written by Dev

[ ] Automated Testing

[ ] Sufficient User and Developer Documentation

[ ] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

With this branch active, visiting /hsapi/ should no longer produce a KeyError

Build finished.


Fix header

@jcenturion Is it possible to fit the "terminal" inside a standard container (like the header) and add the standard breadcrumb like other extensions?

Sure. I will modify it.

@vctrfrnndz:

@jcenturion Looks great, I think this is just missing the name of the extension before the therminal, like this example:

👌


Property $fillable & $guarded is not covariant with PHPDoc type array

Larastan Version: 1.0.2
--level used: 5
Pull request with failing test: none

Description
Standard Laravel property is throwing errors once i migrated to PHPStan 1.*
Laravel code where the issue was found
There's two locations:-

Exceptions\Handler.php

 Line   Exceptions\Handler.php
 ------ -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  15     PHPDoc type array of property App\Exceptions\Handler::$dontReport is not covariant with PHPDoc type array<string> of overridden property Illuminate\Foundation\Exceptions\Handler::$dontReport.
         💡 You can fix 3rd party PHPDoc types with stub files:
            https://phpstan.org/user-guide/stub-files
  24     PHPDoc type array of property App\Exceptions\Handler::$dontFlash is not covariant with PHPDoc type array<string> of overridden property Illuminate\Foundation\Exceptions\Handler::$dontFlash.
         💡 You can fix 3rd party PHPDoc types with stub files:
            https://phpstan.org/user-guide/stub-files

Any Eloquent models with $fillable or $guarded

 17     PHPDoc type array of property App\Models\Activation::$fillable is not covariant with PHPDoc type array<string> of overridden property Illuminate\Database\Eloquent\Model::$fillable.
         💡 You can fix 3rd party PHPDoc types with stub files:
            https://phpstan.org/user-guide/stub-files

Thank you for your report @rognales! 👋
What is Your PHP and Laravel version?

https://github.com/laravel/framework/blob/8.x/src/Illuminate/Foundation/Exceptions/Handler.php#L57
versus
https://github.com/laravel/laravel/blob/8.x/app/Exceptions/Handler.php#L13

Hi,
You need to have same PHPDoc as Laravel has. So you need to change for example $dontReport PHPDoc to string[]
Also, you can just delete it, and PHPStan will use the type from Laravel.

You can also a send a PR to Laravel to synchronize them.

 Referring to Laravel source, they typehinted as String[]. However Docs type-hinted as array
I just need to update all references at my Models

As for  Exceptions\Handler.php, i just need to pull latest version from laravel/laravel. I believe they started type-hinted everywhere.


#387 support for NoopInterval for keeping control socket alive during file transfers

Ignoring Codacy/PR Quality Review complaint in favor of conformity with existing code.
Complaint;
		private int m_noopInterval = 0;

Existing code;
		private int m_port = 0;
...
		private double m_timeDiff = 0;
...
		private uint m_uploadRateLimit = 0;
...
		private uint m_downloadRateLimit = 0;

Ignoring Codacy/PR Quality Review complaint in favor of conformity with existing code.
Complaint;
		private int m_noopInterval = 0;

Existing code;
		private int m_port = 0;
...
		private double m_timeDiff = 0;
...
		private uint m_uploadRateLimit = 0;
...
		private uint m_downloadRateLimit = 0;

This is awesome. It's been a long outstanding issue and I've literally had no idea how to fix it. I'll review it the moment I get some time. Thanks for your effort/PR. Kudos and wish you a Happy New year!

 Looking forward to the next release! Meantime we are good with the workaround of setting EnableThreadSafeDataConnections = true. Thank you!

This is very well done indeed. Thank you again kind sir :)

Can we set a default value for NoopInterval so its enabled by default? I don't see how it can hurt anything. What value should I keep? 15000?

Done. Gone live with 29.0.0:

New: Keep control socket alive during long file transfers using NOOP (thanks aliquid)
New: Add NoopInterval property to control interval of NOOP commands (thanks aliquid)

https://www.nuget.org/packages/FluentFTP/29.0.0


How to add device to cognito user?

I want to add device to my cognito user. If i set CognitoDevice to cognito user and call RememberThisDeviceAsync on CognitoDevice, i got exception:

Amazon.CognitoIdentityProvider.Model.ResourceNotFoundException: Device does not exist. ---> Amazon.Runtime.Internal.HttpErrorResponseException: Exception of type 'Amazon.Runtime.Internal.HttpErrorResponseException' was thrown.

Expected Behavior
Device must be added to user's devices?
Current Behavior
Exception with following stack trace:

at Amazon.Runtime.Internal.HttpErrorResponseExceptionHandler.HandleException(IExecutionContext executionContext, HttpErrorResponseException exception)
at Amazon.Runtime.Internal.ErrorHandler.ProcessException(IExecutionContext executionContext, Exception exception)
at Amazon.Runtime.Internal.ErrorHandler.d__51.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Amazon.Runtime.Internal.CallbackHandler.<InvokeAsync>d__91.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.Runtime.Internal.CredentialsRetriever.d__71.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Amazon.Runtime.Internal.RetryHandler.<InvokeAsync>d__101.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at Amazon.Runtime.Internal.RetryHandler.d__101.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Amazon.Runtime.Internal.CallbackHandler.<InvokeAsync>d__91.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.Runtime.Internal.CallbackHandler.d__91.MoveNext() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)    at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)    at Amazon.Runtime.Internal.ErrorCallbackHandler.<InvokeAsync>d__51.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Amazon.Runtime.Internal.MetricsHandler.d__1`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---

Possible Solution

Steps to Reproduce (for bugs)
Try this code
var currentUser = m_cognitoUserPool.GetUser("user_email");
var authRequest = new InitiateSrpAuthRequest {
    Password = password
};

var authResponse = await CurrentUser.StartWithSrpAuthAsync(authRequest);

CurrentUser.Device = new CognitoDevice("win_234124", new Dictionary<string, string>(), DateTime.Now, DateTime.Now, DateTime.Now, CurrentUser);
await CurrentUser.Device.RememberThisDeviceAsync();

Your Environment

AWSSDK.Core: <IP_ADDRESS>
AWSSDK.Extensions.CognitoAuthentication: 0.9.4
Operating System and version: Windows 10 17134.165
Visual Studio version: Community 2017 15.7.6
Targeted .NET platform: Microsoft.NETCore.UniversalWindowsPlatform 5.4.0

Hi, We are currently investigating this issue with the Cognito team.

@assyadh any update on this issue? thanks!

what API generates Salt and PasswordVerifier?

@assyadh what API generates Salt and PasswordVerifier?

Hi @dmitriy-proskurin,
Could you please check Amazon.Extensions.CognitoAuthentication 2.0.3 and see if that works for you? We implemented some device authentication fixes as part of https://github.com/aws/aws-sdk-net-extensions-cognito/commit/7dc118c8101829354411e556dc1d510996459337. Please verify and confirm.
Thanks,
Ashish

Hi @dmitriy-proskurin,
Could you please check Amazon.Extensions.CognitoAuthentication 2.0.3 and see if that works for you? We implemented some device authentication fixes as part of https://github.com/aws/aws-sdk-net-extensions-cognito/commit/7dc118c8101829354411e556dc1d510996459337. Please verify and confirm.
Thanks,
Ashish


ZAP: Funding tx cannot be found; hanging in pending open

ZAP case: https://github.com/LN-Zap/zap-desktop/issues/2531
Autopilot enabled !
Problem:
Open a channel to ln1.satoshilabs.com which hangs in pending open since weeks !
0279c22ed7a068d10dc1a38ae66d2d6461e269226c60258c021b1ddcdfe4b00bc4
The Funding tx cannot be found
https://blockstream.info/tx/db94d2ffd17c166686d291f56f64d665ff4d0f1a13462200483d3f0ae17de821
lncli --lnddir=C:\Users\wdey\AppData\Roaming\Zap\lnd\bitcoin\mainnet\wallet-3 --rpcserver=<IP_ADDRESS>:11009 pendingchannels
{
"total_limbo_balance": "0",
"pending_open_channels": [
{
"channel": {
"remote_node_pub": "0279c22ed7a068d10dc1a38ae66d2d6461e269226c60258c021b1ddcdfe4b00bc4",
"channel_point": "db94d2ffd17c166686d291f56f64d665ff4d0f1a13462200483d3f0ae17de821:1",
"capacity": "250052",
"local_balance": "241002",
"remote_balance": "0"
},
"confirmation_height": 0,
"commit_fee": "9050",
"commit_weight": "600",
"fee_per_kw": "12500"
}
],
"pending_closing_channels": [
],
"pending_force_closing_channels": [
],
"waiting_close_channels": [
]
}

I appear to be having the same problem..
https://github.com/lightningnetwork/lnd/issues/3341

See resolution in #3341.


Go support

There's a lexer for Go listed in the documentation but the language Go (or "Golang") is not listed in the supported languages section. Also, when using Pygments 2.3.1 (through Sphinx) I get no lexer errors when lexing a Go source file, but the output is un-highlighted as though it were plain text - although the lexer claims to have been added in 1.2.
So is Go supported? It ought to be.

Nvm, I was confused because I was using the include directive - which had worked for me before just because of my default highlighting settings - but using literalinclude caused highlighting to work, which means the bug is in Sphinx if anywhere.


url 404 for php-vim/phpcd.vim

@lvht hi, the old org has been deleted? so the main url of this plugin is lvht/phpcd.vim?  and I just found a vim-php, is that for people who use vim when program php?

php-vim has been deleted. please use lvht/phpcd.vim. Thank you.

ok, got it.


About websocket.http.HttpException

I accidentally used latest API and found a whole module(websocket.http) has been removed, will it break old programs? It seems that API reference didn't say it's internal
By the way, there is a bug in autobahn.asyncio.websocket.WebSocketServerProtocol#_onConnect: it used that module

yes, that has been replaced with https://github.com/crossbario/autobahn-python/blob/master/autobahn/websocket/types.py#L189
there is no bug: https://github.com/crossbario/autobahn-python/blob/master/autobahn/websocket/types.py#L220

@oberstet my description was wrong, but the bug do exists: hereConnectionDeny.http.INTERNAL_SERVER_ERROR) will raise AttributeError

@krrr ah, right. sorry. yes, bug.


Reuse probabilities from previous frame

Reference frame structure captures YUV data and probabilities
of a previously decoded frame.
Symbol counts are reset and not carried from one frame to the next.
Error resilient mode is disabled to support this feature.

PSNR
PSNR Cb
PSNR Cr
PSNR HVS
SSIM
MS SSIM
CIEDE 2000

-2.5635
-1.7975
-1.7969
-2.6936
-2.8068
-3.1602
-2.8160

Thank you :)

Confirm that the reported decoder failures are fixed with "Fix indices in counter reset function".
LGTM.

With bug fix:

PSNR
PSNR Cb
PSNR Cr
PSNR HVS
SSIM
MS SSIM
CIEDE 2000

-2.5794
-1.7644
-1.7641
-2.7124
-2.8311
-3.1702
-2.8306

@lu_zero
No- I just think random pixels would work for certain case, but there are cases where
it does not cover, like real world images that can be well intra-predicted and inter-predicted, which random pixels are not.

I mean, random pixels should still catch this, the very first mode would break it.

I think not likely. What I expect will happen is that the very 1st mode is always used during RDO but it is possible that it is not the final RDO chosen mode so the counter for that CDF is still zero so no breakage even fbossen's patch mistakenly has not init it as zero for use in the next frame.


test plan for v3 stroage

v3 storage is a more complicated than v2 one.
We should have a test plan to cover most of the basic functionalities and corner cases.

I have finished ~70%. The storage/backend has not been covered, and version-related stuffs have not been fully tested yet. Move it to 2.2 to complete all of them.


Made setup.py more colorful and detected python 3

Colorized terminal output for setup and made it check if it was run with python 3, so people running
python setup.py
Where the default interpreter is not 2.x will be warned they need to run using verison 2.

can you pull latest commit and resend?


Property 'parent' in type 'SuperTabs' is not assignable to the same property in base type

Updating Typescript to 2.9.1 throws this Error
Going back to Typescript 2.8.1 or 2.8.3 super-tabs works as expected
[20:34:33]  typescript: node_modules/ionic2-super-tabs/dist/components/super-tabs.d.ts, line: 153
            Property 'parent' in type 'SuperTabs' is not assignable to the same property in base type
            'NavigationContainer'. Type 'NavControllerBase' is not assignable to type 'NavController'. Types of property
            'config' are incompatible. Type
            'import("/home/mdev/_projects/myspaeti/web/html/source-new-marek/node_modules/ionic-angular/umd/co...' is
            not assignable to type
            'import("/home/mdev/_projects/myspaeti/web/html/source-new-marek/node_modules/ionic-angular/config...'.
            Types have separate declarations of a private property '_c'.

     L153:  parent: NavControllerBase;
     L154:  constructor(parent: NavController, viewCtrl: ViewController, _app: App, el: ElementRef, rnd: Renderer2, superTabsCtrl: SuperTabsController, linker: DeepLinker, domCtrl: DomController, _plt: Platform);

It worked. Thanks @magic-77

I am getting the same with Ionic 3.9.2...
Cheers
-jo

I got the error when compiling in Sublime Text. It had the TypeScript plugin v3.0.1 installed. Whilst the Ionic project had TypeScript 2.6.2.
After installing TypeScript globally (npm install -g typescript@2.6.2), and adding this line to Sublie Text Settings -~ User, the error is gone in Sublime Text:
"typescript_tsdk": "/usr/local/lib/node_modules/typescript/lib"
The plugin version settings is described here:
https://packagecontrol.io/packages/TypeScript

Note: Using different versions of TypeScript
This plugin can be configured to load an alternate version of TypeScript. This is typically useful for trying out nightly builds, or prototyping with custom builds. To do that, update the Settings - User file with the following:
"typescript_tsdk": "/node_modules/typescript/lib"
Cheers
-jo

+1
typescript 2.8.3 is ok, however 2.9.2 get this error message.


fzf: 0.24.0 -> 0.24.1

https://github.com/junegunn/fzf/releases/tag/0.24.1

Motivation for this change
Things done

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

[x] NixOS
[x] macOS
[ ] other Linux distributions

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

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

1 package marked as broken and skipped:

fontpreview

7 packages built:

fzf
fzf-zsh
haskellPackages.neuron
navi
neuron-notes
xmloscopy
zoxide


Update configure-end-user-spam-notifications-in-eop.md

updating to reflect the new ESN behavior

@nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@MSFTTracyP - PR has been copy edited and is ready for final review.
Thank you.
cc: @kenwith


feat: import changes checkbox

Description
Update ds package
Delete file, exports
Change imports
Fixes #15492
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?
By running the builds on local

/ok-to-test sha=87a05cc

/ok-to-test sha=0a7138e

/ok-to-test sha=f597b4c


Create a version of this project in Python

Create a version of this project written in Python using the redis-py Redis client.  Your code should live in a new folder named python which should also contain a requirements.txt and README.md that tells people how to install dependencies and run the code.
You'll want to leave the input data file moby_dick_just_words.txt where it is and point to it in your data loading code.  You'll also want to move the existing Node.js project files: .nvmrc, package.json, package-lock.json and index.js into their own folder called nodejs, adding a README.md in there that tells people how to set up and use the Node code (use the text in the existing repo README.md file).
This is part of our participation in Hacktoberfest 2022. Learn how to complete this issue here: https://redis.io/community/hacktoberfest/
Need help or want to talk to us? Join us on Discord where we have a dedicated Hacktoberfest channel: https://discord.gg/ueQwKUh5Z3
If you're interested in taking this issue on, please mention @simonprickett and @SuzeShardlow in the comments and ask to be assigned.

Hi  @simonprickett @SuzeShardlow I am new to open source with Hacktoberfest. I am well versed in Python and Java. Please let me know which project is to be converted to python and what all are your requirements other than the ones mentioned above.
Kindly assign the work to me.

Hi @divyansh-ag-03, thanks for your interest and welcome to Hacktoberfest :)  The project is this one, which is written in JavaScript
and we are looking for someone to create

@SuzeShardlow @simonprickett May I please work on this issue. I went through the JS Repo and I am confident I will be able to make a Python version of the same.

Hi @radioactive11, I've assigned this to you, looking forward to seeing your PR in the next couple of days. Have fun and please check out our guidelines:
https://redis.io/community/hacktoberfest/

Thank you @SuzeShardlow for assigning this issue. I will start working on this right away 😃

Cool, have fun 🙌🏽


How to not write to log but append to the log file.

Hi, i am new to pytest and also python. I am trying out the example you gave.
Example which i following, here
During run my test, logs are always write to my generated log files but not append to end of file. Any how to change to append instead of writing?

Hello @boonyao1122, sorry for keeping you waiting. Files are written to a new directory, which is by default a pytest session's tempdir:
https://docs.pytest.org/en/latest/tmpdir.html
Each pytest run (i.e. "session") logs are written anew to a different dir.
$ pytest > /dev/null ; ll logs
lrwxrwxrwx 1 aurzenligl aurzenligl 39 Jun 18 02:39 logs -> /tmp/pytest-of-aurzenligl/pytest-3/logs
$ pytest > /dev/null ; ll logs
lrwxrwxrwx 1 aurzenligl aurzenligl 39 Jun 18 02:39 logs -> /tmp/pytest-of-aurzenligl/pytest-4/logs

If user chooses own dir, which is the same during each run, files will get overwritten. It doesn't seem to make sense to append to them, as output would get mixed in a way making it difficult to figure out which run given log line comes from.
Does that answer the question?

Closed due to inactivity.


Helm 3 upgrade overwrite the patched value for endpoint resource.

Output of helm version:
version.BuildInfo{Version:"v3.1.1", GitCommit:"afe70585407b420d0097d07b21c47dc511525ac8", GitTreeState:"clean", GoVersion:"go1.13.8"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.3", GitCommit:"435f92c719f279a3a67808c80521ea17d5715c66", GitTreeState:"clean", BuildDate:"2018-11-26T12:57:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"16", GitVersion:"v1.16.2", GitCommit:"c97fe5036ef3df2967d086711e6c0c405941e14b", GitTreeState:"clean", BuildDate:"2019-10-16T08:00:38Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Issue description:

Helm install use the following yaml. And the subsets is set null list.

#####################################
apiVersion: v1
kind: Endpoints
metadata:
name: database-pg
labels:
app.kubernetes.io/version: "xxx"
app.kubernetes.io/instance: "ft3"
annotations:
product-name: " Database PG"
subsets: []
#####################################

After install, do the patch as following.

#####################################
apiVersion: v1
kind: Endpoints
metadata:
name: database-pg
labels:
app.kubernetes.io/version: "xxx"
app.kubernetes.io/instance: "ft3"
annotations:
product-name: " Database PG"
subsets:
- addresses:
- ip: <IP_ADDRESS>
ports:
- name: metrics
port: 9187
protocol: TCP
- name: postgresql
port: 5432
protocol: TCP
#####################################

Take the helm upgrade with following chart.

#####################################
apiVersion: v1
kind: Endpoints
metadata:
name: database-pg
labels:
app.kubernetes.io/version: "xxx"
app.kubernetes.io/instance: "ft3"
annotations:
product-name: " Database PG"
subsets: []
#####################################
After upgrade, the subsets of endpoint overwrite to patched value with null list as above yaml. Could you confirm if this behavior is right. According to helm3 new feature about 3-way Strategic Merge Patches, it should keep the patched value after upgrade.

The behaviour described above is correct.


Confusion with dest param in SonicBoomOpts type

The type SonicBoomOpts defines dest as a string: https://github.com/pinojs/sonic-boom/blob/master/types/index.d.ts#L11, however it seems like you can also pass a number to it. As can be seen here within the pino-pretty/ library: https://github.com/pinojs/pino-pretty/blob/master/index.js#L192.
Should the type be updated to string|Number to allow for passing 1 to indicate stdout and a string if passing a path to a file?
I noticed that it's also possible to do this: SonicBoom({ fd: process.stdout.fd }) how does this differ from SonicBoom({ dest: 1 })? Or do both achieve exactly that same in piping the stream to stdout?

I think the type should be updated.
cc @kibertoad

I can open a PR to correct the type, so it should be string|Number?
The readme for SonicBoom should also change to reflect this, specifically here, how about changing this:

fd: a file descriptor, something that is returned by fs.open or fs.openSync.

to:

fd: a file descriptor, something that is returned by fs.open or fs.openSync, or a number (1: stdout, 2: stderr).

Or do both achieve exactly that same in piping the stream to stdout?

They both achieve the exact same thing.


Unescape non-ascii characters for re2

Error from a regex in https://www.npmjs.com/package/entities: (error parsing regexp: invalid escape sequence: `\⩓`)

Thanks for reporting.


Add support for nested functions and resolve any unit test failures.

Added functionality to support new feature request: https://github.com/SAP/open-ux-odata/issues/253
All existing unit tests are passing, but didn't have enough time to write new tests. I'll be away on vacation and am hoping to use the functionality when I return. Hoping someone else can pick it up.

Thanks for your contribution, i'll have a look and use this as a starting point to provide this functionality :)

Closing this one and taking over in a PR directly on this repo :)


cli::tests::init_args_before_cmd fails on windows

Clean checkout on Windows 11 pro. Running cargo test and cli::tests::init_args_before_cmd fails.
I think CLI tests are not being run under CI.
Test run output

running 13 tests
test proc::reader::format::tests::message_format_new ... ok
test proc::reader::format::tests::message_format_old_a ... ok
test proc::reader::format::tests::message_format_old_b ... ok
test proc::reader::format::tests::msg_message_format_old ... ok
test cli::tests::args_global ... ok
test init::tests::full_metadata_is_valid ... ok
test cli::tests::args_commands_not_missed ... ok
test cli::tests::args_build ... ok
test cli::tests::args_new ... ok
test cli::tests::args ... ok
test cli::tests::init_args_before_cmd ... FAILED
test cli::tests::init_cargo ... ok
test cli::tests::init_standalone ... ok
failures:
---- cli::tests::init_args_before_cmd stdout ----
PWD: C:\Users\peter\source\playdate\cargo\tests\crates\simple\no-cfg\tests/crates/simple/no-cfg
Error: The system cannot find the path specified. (os error 3)
Stack backtrace:
0: std::backtrace_rs::backtrace::dbghelp64::trace
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\std\src....\backtrace\src\backtrace\dbghelp64.rs:91
1: std::backtrace_rs::backtrace::trace_unsynchronized
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\std\src....\backtrace\src\backtrace\mod.rs:66
2: std::backtrace::Backtrace::create
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\std\src\backtrace.rs:331
3: std::backtrace::Backtrace::capture
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\std\src\backtrace.rs:296
4: anyhow::error::impl$1::fromstd::io::error::Error
at C:\Users\peter.cargo\registry\src\index.crates.io-6f17d22bba15001f\anyhow-1.0.82\src\backtrace.rs:27
5: core::result::impl$27::from_residual<tuple$<>,std::io::error::Error,anyhow::Error>
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af\library\core\src\result.rs:1964
6: cargo_playdate::cli::tests::init_args_before_cmd
at C:\Users\peter\source\playdate\cargo\src\cli\mod.rs:834
7: cargo_playdate::cli::tests::init_args_before_cmd::closure$0
at C:\Users\peter\source\playdate\cargo\src\cli\mod.rs:831
8: core::ops::function::FnOnce::call_once<cargo_playdate::cli::tests::init_args_before_cmd::closure_env$0,tuple$<> >
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af\library\core\src\ops\function.rs:250
9: core::ops::function::FnOnce::call_once
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\core\src\ops\function.rs:250
10: test::_rust_begin_short_backtrace<enum2$<core::result::Result<tuple$<>,alloc::string::String> >,enum2$<core::result::Result<tuple$<>,alloc::string::String> > (*)()>
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\test\src\lib.rs:625
11: test::run_test::closure$0
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\test\src\lib.rs:569
12: test::run_test::closure$1
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\test\src\lib.rs:599
13: std::sys_common::backtrace::rust_begin_short_backtrace<test::run_test::closure_env$1,tuple$<> >
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\std\src\sys_common\backtrace.rs:155
14: std::thread::impl$0::spawn_unchecked::closure$2::closure$0
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\std\src\thread\mod.rs:542
15: core::panic::unwind_safe::impl$25::call_once
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\core\src\panic\unwind_safe.rs:272
16: std::panicking::try::do_call
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\std\src\panicking.rs:559
17: std::panicking::try
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\std\src\panicking.rs:523
18: std::panic::catch_unwind
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\std\src\panic.rs:149
19: std::thread::impl$0::spawn_unchecked::closure$2
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\std\src\thread\mod.rs:541
20: core::ops::function::FnOnce::call_once<std::thread::impl$0::spawn_unchecked::closure_env$2<test::run_test::closure_env$1,tuple$<> >,tuple$<> >
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\core\src\ops\function.rs:250
21: alloc::boxed::impl$48::call_once
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\alloc\src\boxed.rs:2022
22: alloc::boxed::impl$48::call_once
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\alloc\src\boxed.rs:2022
23: std::sys::pal::windows::thread::impl$0::new::thread_start
at /rustc/faefc618cf48bd794cbc808448df1bf3f59f36af/library\std\src\sys\pal\windows\thread.rs:52
24: BaseThreadInitThunk
25: RtlUserThreadStart
failures:
cli::tests::init_args_before_cmd
test result: FAILED. 12 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.27s

Thank you!

I think CLI tests are not being run under CI.

That's strange, I'll check it out.


npm install not --save-dev

Hey,
working with gatsby. I saved the package like in the readme documented as a dev dependency but got the error that it should  be saved as a normal dependency, which makes sense I guess?
Or might that be just an error cause I'm working with Gatsby?
Would be crazy if I would be the only one that ran into that issue. Maybe update the Readme.md? I could send a quick PR :)

Thank you for the feedback, addressed in commit https://github.com/jaketrent/react-social-icons/commit/a79657def25e31694ccb95c1ad609617209b9962


feat: add support for base-ocp in SLZ

Description
Issue: https://github.ibm.com/GoldenEye/issues/issues/10566
integrating base OCP to landing zone, and creating a new major version release without support for an upgrade path initially. We would include in the release notes for consumers not to upgrade yet, but at latest new consumers will deploy with base OCP in it.

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[x] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

Ran a mock upgrade test

terraform apply roks pattern in local setup. The apply was successful.
created a new branch and made some changes which adds new feature to the base-ocp code.
Ran terraform plan on the new branch show resource which will be added.

/run pipeline

/run pipeline

/run pipeline

Same error again.
=== NAME  TestRunVSIQuickStartPatternSchematics
    schematics.go:305: [SCHEMATICS] RETRY PlanWorkspaceCommand, status code: 429
    tests.go:123:
        	Error Trace:	/go/pkg/mod/github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper@v1.38.2/testschematic/tests.go:123
        	            				/__w/terraform-ibm-landing-zone/terraform-ibm-landing-zone/tests/pr_test.go:539
        	Error:      	Received unexpected error:
        	            	Too Many Requests
        	Test:       	TestRunVSIQuickStartPatternSchematics
        	Messages:   	error creating PLAN - [ qs-sc-khu6em (us-south.workspace.qs-sc-khu6em.04b943b4) ]
--- FAIL: TestRunVSIQuickStartPatternSchematics (161.50s)

429 - Too Many Requests - we are getting rate limited. I have temporarily updated the apikey in the tests for this repo as a workaround. Todd is also going to reduce the polling frequency in the tests to help here

/run pipeline

2024-09-19T14:58:44.1218581Z === NAME  TestRunVPCPatternSchematics
2024-09-19T14:58:44.1219687Z     schematics.go:305: [SCHEMATICS] RETRY PlanWorkspaceCommand, status code: 429
2024-09-19T14:58:44.1345487Z     tests.go:123:
2024-09-19T14:58:44.1347799Z         	Error Trace:	/go/pkg/mod/github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper@v1.38.2/testschematic/tests.go:123
2024-09-19T14:58:44.1350387Z         	            				/__w/terraform-ibm-landing-zone/terraform-ibm-landing-zone/tests/pr_test.go:624
2024-09-19T14:58:44.1351625Z         	Error:      	Received unexpected error:
2024-09-19T14:58:44.1352295Z         	            	Too Many Requests
2024-09-19T14:58:44.1352944Z         	Test:       	TestRunVPCPatternSchematics
2024-09-19T14:58:44.1354216Z         	Messages:   	error creating PLAN - [ vpc-sc-bpkpjq (us-south.workspace.vpc-sc-bpkpjq.c58f5156) ]
2024-09-19T14:58:44.1355397Z --- FAIL: TestRunVPCPatternSchematics (185.14s)

Still the same error

Oh dear - I think we need to update the test wrapper here to poll less frequently, and then update this PR with new wrapper version @toddgiguere

/run pipeline

Schematics is still having issues. Looking at the logs, none of the test threads are even making one iteration of polling. Some of the tests do not even get to the polling for status, the plan or apply is failing right away. All with the return code of 429 - Too Many Requests.

/run pipeline

/run pipeline

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

GitHub release
v6.0.0

Your semantic-release bot :package::rocket:


Add add-on for clean-up after command completion

Add a new add-on which handles cleanup of completed processes.
If added, it should despawn the entity of the process.
Later on, we can also add different options, like only removing the Process component, in case that the user has other components on the entity which they still need.
There is a bit of a trade-off here, having this in a separate component.
I assume that in most cases it is the desired behavior, so the user would often need to add this component.
However, I think it offers a nice consistency if add-on functionality is additive, i.e. we only add new functionality and don't remove stuff that already exists.

I have a working implementation of this, just waiting on #16 to be merged in.


Fix/15544 bank account pages disable text input within wrong data on main device

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/15544
PROPOSAL: https://github.com/Expensify/App/issues/15544#issuecomment-1452191560
Tests

Log in with the same account in 2 different environment (2 different devices or 2 different browsers)
In the main testing device, navigate to Settings -> Workspace -> Open any workspace -> Connect bank account
Type the wrong routing number and account number
In the second device, navigate to the connect bank account page too
Complete 2 first steps to reach step 3
Refresh the page in the main device and verify that the inputs in step 1 and step 2 are the same as what we filled in the second device and some of the inputs ("Routing number", "Account number", "Legal business name", and "Tax ID number") are disabled as expected.

[x] Verify that no errors appear in the JS console

Offline tests

To connect bank account, we need a internet connection.
QA Steps

Log in with the same account in 2 different environment (2 different devices or 2 different browsers)
In the main testing device, navigate to Settings -> Workspace -> Open any workspace -> Connect bank account
Type the wrong routing number and account number
In the second device, navigate to the connect bank account page too
Complete 2 first steps to reach step 3
Refresh the page in the main device and verify that the inputs in step 1 and step 2 are the same as what we filled in the second device and some of the inputs ("Routing number", "Account number", "Legal business name", and "Tax ID number") are disabled as expected.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://user-images.githubusercontent.com/113963320/224072245-da8d4076-9816-4d88-9d26-8d1d02f088bb.mp4

Mobile Web - Chrome

https://user-images.githubusercontent.com/113963320/224073331-7db3d606-6507-45fd-a6ec-c2099a912757.mp4

Mobile Web - Safari

https://user-images.githubusercontent.com/113963320/224072423-3addd82a-0bd7-486d-9ce3-18bc29153086.mp4

Desktop

https://user-images.githubusercontent.com/113963320/224072294-c14ea8cb-c9e5-4026-8312-7a703720fb77.mp4

iOS

https://user-images.githubusercontent.com/113963320/224073093-3b28cc56-87bb-4b39-bcbe-e29e4853bdb9.mp4

Android

https://user-images.githubusercontent.com/113963320/224073600-4c52fcc7-7d24-4240-a539-5aa3dca4e5cf.mp4

Hey! I see that you made changes to our Form component. Make sure to update the docs in FORMS.md accordingly. Cheers!

@tylerkaraszewski @mollfpr One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@tylerkaraszewski Yes! Sorry, I miss this PR! I thought that already reviewed a PR from @tienifr , but that’s another PR 😅

@mollfpr I have resolved the comments. Please help me check it. Thank you!

Hi @mollfpr, please help me check the updated code. Thank you!

I have updated the code. Please help me review it @mollfpr. Thank you!

@tylerkaraszewski It seems that because of an accident made by me, you're not being requested to review this PR. Can you add yourself again?

@tienifr Thanks for the update! I'll review it within hours.

@tylerkaraszewski Whenever you have time to review this.

🚀 Deployed to staging by https://github.com/tylerkaraszewski in version: 1.2.90-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/luacmartins in version: 1.2.90-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Add primitive type classes to support type refinements

This PR adds separate classes for Bicep's built-in types in order to support type-specific refinement metadata, such as a minimum and maximum value for integers and a minimum and maximum value for strings. The generic BuiltInType is retained for backwards compatibility, but using it will generate deprecation notices.

Codecov Report

Merging #155 (646381c) into main (0f77932) will increase coverage by 0.98%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #155      +/-   ##
==========================================
+ Coverage   94.31%   95.30%   +0.98%
==========================================
  Files          18       23       +5
  Lines         299      362      +63
==========================================
+ Hits          282      345      +63
  Misses         17       17

Flag
Coverage Δ

dotnet
95.30% <100.00%> (+0.98%)
:arrow_up:

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

Impacted Files
Coverage Δ

src/Bicep.Types/Concrete/BuiltInType.cs
100.00% <ø> (ø)

src/Bicep.Types/Serialization/TypeJsonContext.cs
100.00% <ø> (ø)

src/Bicep.Types.UnitTests/TypeSerializerTests.cs
100.00% <100.00%> (ø)

src/Bicep.Types/Concrete/AnyType.cs
100.00% <100.00%> (ø)

src/Bicep.Types/Concrete/ArrayType.cs
100.00% <100.00%> (ø)

src/Bicep.Types/Concrete/BooleanType.cs
100.00% <100.00%> (ø)

src/Bicep.Types/Concrete/IntegerType.cs
100.00% <100.00%> (ø)

src/Bicep.Types/Concrete/NullType.cs
100.00% <100.00%> (ø)

src/Bicep.Types/Concrete/ObjectType.cs
100.00% <100.00%> (ø)

src/Bicep.Types/Concrete/StringType.cs
100.00% <100.00%> (ø)

... and 1 more

This PR is blocked pending updates to the ARM template reference generator. Targeting release post Bicep 0.17


Enchanted CTA | Pause Marquee when not visible

CTA with Marquee:
Find a way to pause the marquee / metronome when the button is not in hover state.

Note: v2.1 branch had logic for document events that might make this easier.

This should be fixed in v2.5.


RANSAC Fails to Detect Model - Need More Lidar Points

I'm encountering an issue with the cam_lidar_calibration package on ROS Noetic. The package correctly detects the chessboard, but when I try to 'Capture Sample,' I get these errors:
[pcl::SampleConsensusModel::getSamples] Can not select 0 unique points out of 1!
[pcl::RandomSampleConsensus::computeModel] No samples could be selected!
[pcl::RandomSampleConsensus::computeModel] RANSAC found no model.
[pcl::SACSegmentation::segment] Error segmenting the model! No solution found.
[ERROR] [1723617562.542058090]: RANSAC unsuccessful, discarding sample - Need more lidar points on board

System Information:

OS: Ubuntu 20.04
ROS Version: Noetic (ROS1)
Branch: noetic-v2
Lidar: RSLIDAR
Camera: USB Camera

Configuration (cfg/params.yaml):
# Topics
camera_topic: "/usb_cam/image_raw"
camera_info: "/usb_cam/camera_info"
lidar_topic: "/rslidar_points"

# Feature Extraction Settings
feature_extraction:
  x_min: 1.0
  x_max: 7.0
  y_min: -3.0
  y_max: 3.0
  z_min: -1.7
  z_max: 0.0
  k: 50
  z: 1
  voxel_res: 0.4

# Chessboard Calibration Target
chessboard:
  pattern_size:
    height: 5
    width: 7
  square_length: 95
  board_dimension:
    width: 700.5
    height: 1000
  translation_error:
    x: 2
    y: 2

Troubleshooting Done:

Tried different voxel_res values.
Adjusted rqt_reconfigure bounds.
Attempted to convert RSLIDAR points to Velodyne points. This resulted in no chessboard detection from the camera image, but no RANSAC-related errors were present.

Request:
Can you provide advice on how to fix this? Is there a specific setting or adjustment needed to get enough LIDAR points for RANSAC?
Screenshots:

Please follow the instructions in the Readme file "2.1 Setup of Calibration Target"
"Rotate the chessboard such that it is in the shape of a diamond (at an angle of 45° with respect to the ground) and mount it on a stand."


IDR Private (IDRP)

Token Address
https://scan.tomochain.com/address/0xc28194b773ce7b4d74c87e551afe991bd49a1d4e
Token Symbol
IDRP
Token Name
IDR Private
Token Logo
Link Image
Token Description
IDR Private is issued by PT Rupiah Digital Indonesia, a legal company in Republic of Indonesia. IDR Private (IDRP) is a smart service using blockchain technology for asset security. The assets guarantor of IDRP is the government-appointed Margin Depositing Bank.
Website
https://idrp.io/
Social links
https://github.com/IDR-Private
https://www.instagram.com/idrp.io/
https://www.linkedin.com/company/pt-rupiah-digital-indonesia/

@khaihkd take a look this issue.

Merged.


Bluetooth: GATT: Fix bt_gatt_foreach_attr_type

This fixes bt_gatt_foreach_attr_type when num_matches is not 0.

@joerchan can you approve this one?

@joerchan done.

@jhedberg could you please push this one once you have some time.


Stack overflow

What Git revision are you using?
Git sha1: 9f587e802c74531471cfbb3fd0d3baea1a8a62b3
What operating system are you using, and which version?

[x] macOS M2

Describe what the problem is?
Aiken check works but Aiken build ends up in stack overflow.
What should be the expected behaviour?
There should not be any stack overflow on invoking Aiken build.
Branch where it can be reproduced:
https://github.com/cardano-foundation/hydra-voting-poc/tree/merkle_tree
navigate to on_chain directory and invoke Aiken build and boom.
mati@Mateuszs-MacBook-Pro on-chain % aiken build
    Compiling aiken-lang/stdlib a6bbc331fdc460e5170c4d28b48e69712752d985 (/Users/mati/Devel/OpenSource/hydra-voting-poc/on-chain/build/packages/aiken-lang-stdlib)
    Compiling cardano-foundation/hydra-voting-poc 0.0.1 (/Users/mati/Devel/OpenSource/hydra-voting-poc/on-chain)
   Generating project's blueprint (/Users/mati/Devel/OpenSource/hydra-voting-poc/on-chain/plutus.json)

thread 'main' has overflowed its stack
fatal runtime error: stack overflow
zsh: abort      aiken build

It is unclear what causes it but it is likely it has something to do with recently adding MerkleTrees as it was working before.


EDIutils links should reference rOpenSci

Currently, EDIutils resources link to their old home at the EDIorg GitHub, which in many instances return a 404 error. These should be updated to their new location at the rOpenSci GitHub.

Fixed by PASTAplus/content-x@d9ac324cf0446db6d5fedd9521d2e97e1f4b5962


Pipeline batching tracking issue

This is the pipeline batching tracking issue.

@EricLBuehler are you working on this yet? would be interested in collaborating on it

That sounds great! Perhaps you can open a PR to track development?
I will be probably making some major changes in the architecture of the ModulePipeline in the coming days, but once they are made I will let you know.

Closing this pending a rewrite of the scheduler and cache, see the scheduler branch. This task is encompassed by the scheduler, which manages the batching. A new tracking issue will be opened.


update patient form (general information) UX

🚀 Feature Proposal
Update general information form UX

Put "Unknown" checkbox under "Date of Birth" field.

Motivation
Now we have input "Date of birth" and checkbox "Unknown"

It's not clear, that checkbox "unknown" is related to field "Date of birth".  User can suggest, that this checkbox is for "Patient type", because it's under this field.
If "Unknown" is checked, "Date of Birth" field is hidden. If someone will view such patient, there is no way to find out, what field does "Unknown" belong to.

P.S. I can work on this issue if you don't mind

To close the loop on this:
I think the final requirement is merely a UI change, rather than a functionality change. The functionality we have now where checking unknown changes the input box to an integer input box for an estimate age is the desired behavior.


Telegram on Wayland doesnt use system cursor theme.

Describe the bug
On Wayland (with QT_QPA_PLATFORM=wayland), Telegram doesn't use the system cursor theme.
Steps To Reproduce
Steps to reproduce the behavior:

Open Wayland with QT_QPA_PLATFORM=wayland set
notice how the cursor doesn't use the system's cursor theme and instead uses a simple, small black cursor theme

Expected behavior
Telegram on wayland should use the system's cursor theme.
Screenshots

Here it's on wayland

Here it's on Xwayland.
Additional context
Also just noticed that it only renders like half the cursor or 75% of the cursor, but screenshots seem to make the cursor render correctly.
Notify maintainers
@oxalica
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 5.18.10-zen1, NixOS, 22.11 (Raccoon), 22.11pre390948.5f43d8b088d`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.9.1`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Same issue is encountered in xorg + i3. I currently pinned tdesktop package to commit: 0c3bf3a5c3ab6be29138b88900c417660a284fbd to workaround this issue.

Contrary to you, I found this behavior in X11, everything works fine in Wayland.

The same happens in awesome, will be good to test it on kde/gnome maybe is something qt6 is using from the desktop?

Having the same issue under KDE with Wayland too.

Having the same issues under KDE with X11. Wayland works correctly however.

Happens in XMonad too..

+1 for xmonad

Sorry I'm not really maintaining tdesktop now. cc @NickCao, seems to be an issue of Qt6?
Personally, I doesn't have cursor issue on sway.

Most likely an issue with Qt6, but I'm also at a loss what to do to fix this.

This still happens on gnome wayland, same as i reported on the original post.

I can reproduce it on gnome wayland.

Ok, so, this also affects other applications:

mpv #198192
obs-studio

Any news on this? Still facing this issue :(

I'm using qtile in x11 and hyprland in wayland and it's working fine in both.

it's still an issue, almost opened another bug report lol
@leiserfg this affects apps running on wayland mode.

It also happens to me on multiple machines.

Dug into this a bit, I can't figure out what tries to load libXcursor yet, but:

running telegram with LD_DEBUG=libs shows libXcursor being loaded; it also seems like it is in RUNPATH, but I can't see it with chrpath (most likely it's in the rpath of a dependency or something loaded by dlopen)
telegram does not seem to call into libXcursor at all (according to ltrace), so it's probably the wrong place to look (unless it's being used as a fallback or something else)

For what it's worth, I can't repro this bug (on sway).

By the way, for whoever this is still broken, it could simply be a configuration issue. Just for a sanity check, and to cross-check variables, please post the following information:

Qt theme and platform theme in use
whether the cursor is broken on eg file dialogs (if not using XDG portals, and especially if using a gtk-based platform theme)
whether the cursor is broken on another qt6 application such as syncplay
how you're configuring the cursor theme; if not using home-manager, do take a look at what it does and see whether you're missing something that would possibly fix it (https://github.com/nix-community/home-manager/blob/master/modules/config/home-cursor.nix)

I don't have this issue anymore, but I do have issues on other applications such as mpv and xwayland games :/

I also confirm the issue is gone. Cursors are working on Telegram.

I use nix as:

nixos with wayland
nixos with x11
home-manager with wayland over debian

and it does not happen to me in any of them, so I consider the issue gone a long time ago.


Fix strlit

Not sure, but it blows up when I return a JsonNode. This fixes it.

Please bump the patch version.


"include_trashed" doesn't work for models that inherit the SoftDeletes trait

The usesSoftDeleting() function now checks parent classes as well when determining if the softdeletes trait is being used

Thanks!


converting error while training

Hi, im trying to train my own dataset, and i recived the following msg:
loading annotations into memory...
Done (t=0.22s)
creating index...
index created!
loading annotations into memory...
Done (t=0.03s)
creating index...
index created!
Initializing weights...
Begin training!
Traceback (most recent call last):
File "train.py", line 382, in
train()
File "train.py", line 213, in train
for datum in data_loader:
File "/home/student/.local/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 582, in next
return self._process_next_batch(batch)
File "/home/student/.local/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 608, in _process_next_batch
raise batch.exc_type(batch.exc_msg)
TypeError: Traceback (most recent call last):
File "/home/student/.local/lib/python3.6/site-packages/torch/utils/data/_utils/worker.py", line 99, in _worker_loop
samples = collate_fn([dataset[i] for i in batch_indices])
File "/home/student/.local/lib/python3.6/site-packages/torch/utils/data/_utils/worker.py", line 99, in
samples = collate_fn([dataset[i] for i in batch_indices])
File "/home/student/sd/yolact/data/coco.py", line 88, in getitem
im, gt, masks, h, w, num_crowds = self.pull_item(index)
File "/home/student/sd/yolact/data/coco.py", line 160, in pull_item
{'num_crowds': 0, 'labels': np.array([0])})
File "/home/student/sd/yolact/utils/augmentations.py", line 661, in call
return self.augment(img, masks, boxes, labels)
File "/home/student/sd/yolact/utils/augmentations.py", line 54, in call
img, masks, boxes, labels = t(img, masks, boxes, labels)
File "/home/student/sd/yolact/utils/augmentations.py", line 179, in call
boxes[:, [0, 2]] *= (width  / img_w)
TypeError: Cannot cast ufunc multiply output from dtype('float64') to dtype('int64') with casting rule 'same_kind'
when i look into in i saw that boxes is Int. so it can't be casting to float.
i change it manualy but then another error appear...
what i did wrong?
thanks!

That's weird. Maybe you have a really old version of numpy or something? What version do you have? Mine's 1.16.2.

import numpy
numpy.version.version
'1.16.4'

Hmm okay what about your python version? It's weird because I haven't seen anyone else have this issue even though it should be pretty common.

Python 3.6.8 |Anaconda, Inc.| (default, Dec 30 2018, 01:22:34)
[GCC 7.3.0] on linux

maybe it's somthin with me json?

Python version is fine. And I thought it might be an issue with the json but then I looked and all my boxes are ints in the json as well. I'll take another look to see if there are any other instances of floats in there.

Only float in there is "area". Are your area values floats?

OK, @dbolya
Thay whas my mistake. in my JSON file, the "annotations" array was empty....
Thanks you very much :-)


Unable to set/change avatar (for the bot)

Please tick all applicable boxes.

[x] I am using Python 3.5 or higher (run python --version on the command line)
[x] I have followed the official guides to install the bot for my system
[x] I have updated my dependencies to the latest version using the appropriate update script

Which version are you using?

[x] The latest master version (1.9.7)

What type of issue are you creating?

[x] Bug

Description of issue
Unable to set/change the avatar of the bot using the -setavatar command.
I attempted to use a direct URL to the image. (http://img.sugarcookie.org/i/rnbw-paw.png)
I also tried using a smaller version of the image, as well as the same image in the jpeg format.
Steps to reproduce
Invoking setavatar, followed by a direct image URL
Ex. -setavatar http://img.sugarcookie.org/i/rnbw-paw.png

musicbot.log

Hi there,
I was unable to reproduce that bug, can you send the full unaltered musicbot.log for me?

I have no clue what I did different this time around, but the command worked for me as I went to reproduce the same error I was getting before. Bravo! Haha.. I feel silly now - Will mark as closed.


Reduce docker layers

Reducing the number of RUN commands doesn't reduce the size of the image but the number of required layers. I also did some other optimisations.

@DrMurx Thank you!


[CLI] Do not warn on minor CLI version mismatch.

Do not nag people about mismatched minor versions between CLI and the server, because these versions do not match most of the time.

:+1:


Add support for winget's uninstall command once it's available.

I've planned for this for a while, but I just want to have an issue to remind myself to do it.

Early tests show it can have just the package ID specified for things like Terminal, but packages not installed with MSIX packages need their Add/Remove Programs entry to be specified. This makes it kinda complicated unless non-MSIX manifests have an "uninstall" key specified. What would be nice is if all the packages were available in MSIX format so that this would be simple, but a lot of packages don't have a signing certificate they can use. Hopefully this'll change when the free signing service is available.

Early tests show it can have just the package ID specified for things like Terminal, but packages not installed with MSIX packages need their Add/Remove Programs entry to be specified. This makes it kinda complicated unless non-MSIX manifests have an "uninstall" key specified. What would be nice is if all the packages were available in MSIX format so that this would be simple, but a lot of packages don't have a signing certificate they can use. Hopefully this'll change when the free signing service is available.

Most of this is complete, but I need to add a way to say whether the uninstaller should take a package's version into consideration. That would be done with a checkbox in the "Options" window, and I can add a "More..." linklabel to the "Apply Changes" window that opens a small tool window with the "Apply Changes" tab checkboxes duplicated. Checking and unchecking the boxes immediately applies the setting, saves, and reloads, and there can be a "Defaults" button to reset them to default. The window will close when the "Apply Changes" window is closed by using the "closing" event, and I guess there can be a "Close" button in the bottom-right.
By default, we won't specify the version number, but it may be necessary in some cases so the option will be there.
This'll be available when upgrading, too.

There's a way to ignore versions now as of 56356be, so this can be closed.

Now there's a "Defaults" button, as that window is kinda complicated.


AEAD

Adding Authenticated Encryption with Associated Data modes of operation would be nice, looks like the building blocks to put in GCM mode (though it will require a modified ctr mode) and chacha20/poly1305

work on gcm and trying to figure out the ghash api @DaGenix am I correct that it changes type based on whether there is cipher text pressent?

That is my understanding of how it works.


Bugfix/proptype

Coverage remained the same at 36.0% when pulling 331500f9f4a356acd9078b9c825c31dbde3205bd on bugfix/proptype into 877952dbf9efc705f8e2b60f48b17fa7d76ed609 on master.

Coverage increased (+6.0%) to 42.0% when pulling 1e2dbfd103e2d78e0db94405df30ca653ddf4f22 on bugfix/proptype into 877952dbf9efc705f8e2b60f48b17fa7d76ed609 on master.


ListPicker Selection change not working properly when we set the selectedList using setState

Category
[ ] Enhancement
[X] Bug
[ ] Question
Version
Please specify what version of the library you are using: [   1.13.2   ]
Expected / Desired Behavior / Question
On selection change, selectedList should be highlighted and options should not be repeated
Observed Behavior
On ListPicker selection change, selectedList is getting highlighted but the options are binding again

Steps to Reproduce
After migrating my project from SPFx 1.6 to SPFx 1.8.2 I started seeing this issue.
If we don't set the selectionList from state then we wont have issue. But in my scenario I need to set the selectedList from state and it should be stored back to the state on selectionChanged event

After some research we think it's related to the control pushing all found lists to the _options, without checking if the item is already in this list. As this function is also called on any change done to the selected item it will duplicate all items again and again on change. It's unclear to us why this issue started after upgrading our project.
A proposed solution would be to check if the item is already in the list before pushing;
results.value.map(list => {
        if (!this.optionsContainsList(list)) {
          this._options.push({
            key: list.Id,
            text: list.Title
          });
        }
      });

This should have been fixed. You can test it out in the latest beta version and will be available in 1.14.0. More information on how you can test out a beta version can be found here: https://sharepoint.github.io/sp-dev-fx-controls-react/beta/

Thank you for providing the fix, Its working fine with beta version. Could we know the planned target date for 1.14.0 release.

Release date would be later this week or next week, depends on the other fixes that are waiting to be verified.

This is now included within the 1.14.0 release


Cherry pick query support to 6.3.x

#2871 was merged to master when it is needed on 6.3.x, this cherry picks the commits back to 6.3.x

Test PASSed


Support for iOS 10

I needed to support iOS 10 in my app but the library only supports iOS >= 12. So, I had to replace the library.
But I was curious to know why the library requires iOS 12. So I added the source code directly to a test project that targets iOS 10, and it builds successfully!
It looks like the library actually supports iOS 10 as it is now and no need for extra work. I suggest changing the requirements for the library to the minimum version of every OS to allow it to be used in a wider range of projects.

There isn't a reason for the iOS 12 limit. It was just what I needed to support at the time.
I went ahead and make a thorough check of the library's dependencies. CodableCSV minimally use Foundation; specifically it requires: CharacterSet, Data, Date, DateFormatter, Decimal, OutputStream, and URL. Technically I could set the limit at iOS 7, macOS 10.9, tvOS 9, and watchOS 2 😄
Anyways, I have made the changes on the SPM and Cocoapods files that you need and release a new fix version.

Great! 😄

By the way @MhdHejazi, good work on the CoronaTracker app, I just downloaded and I am digging it. I am sad CodableCSV couldn't be your CSV library of choice 😅

Thanks! Glad you like it 😄
It was actually my library of choice and mentioned that in the repo. But had to replace it to support iOS 10 as I said. And also because it doesn't detect the line delimiter automatically. There is an option for that (.unknown) but not implemented yet.

Yeah, that is in my todo 🗒 list. Does CSV.swift have the header inferral functionality? As far as I got, that library only provides the option to say whether the CSV has a header or not.
In any case, once I finish with the Encoder implementation, I will iron out all the missing behavior. I have some things in the pipeline that are pretty sweet 😊

I was talking about the line delimiter. Not sure about inferring the header. But I think inferring the line delimiter is more important as it's more likely to be messed up, and when that happens you find yourself dealing with things like "12\r" instead of numbers.

Oh right, sorry I misread. Yes, I agree. I will bump the priority of the line delimiter inference in my todo list.
Thank you for your input and comments.

Hey @mhdhejazi I just finished a big upgrade to CodableCSV and I was thinking on tackling the line delimiter inference you mentioned previously next.
Last time I got the impression from your comments that CSV.swift did that, but I haven't been able to find it anywhere in their codebase. Do you have any pointers or do you know anybody that does something similar?

I guess this is how CSV.swift deals with line delimiters:
https://github.com/yaslab/CSV.swift/blob/81d2874c51db364d7e1d71b0d99018a294c87ac1/Sources/CSV/CSVReader.swift#L290-L298

Yeah, that is only checking for hardcoded line delimiters: \r, n or the EOF, but it is not trying to figure out what the line delimiter is, which is the functionality I would love to include. In any case, thank you 👍
By the way, if you have some free time, do give another try to CodableCSV. Performance is better, now it supports files, and it can load huge files only partially as it is needed for decoding 😄

Well, according to the standard, line breaks (\r, \n) should be considered line delimiters unless they are enclosed in double-quotes
   6.  Fields containing line breaks (CRLF), double quotes, and commas
       should be enclosed in double-quotes.  For example:

       "aaa","b CRLF
       bb","ccc" CRLF
       zzz,yyy,xxx

So, I think detecting the line delimiters for the whole file isn't that important (nor feasible for large files). Doing line by line processing is totally fine, and I don't think you have to worry about mistakenly dropping a \r or \n character from the data as long as you're following the standard.

Well, according to the standard, line breaks (\r, \n) should be considered line delimiters unless they are enclosed in double-quotes.

Definitely, the problem is that many CSVs out there don't really follow the standard. But for most cases is definitely the best.

the problem is that many CSVs out there don't really follow the standard

I totally agree. And the same goes for using a consistent line delimiter throughout the file 😉


Practical question : how it works the "paginate-elements-by-height" property ?

Hello,
I'm not sure to understand the operation of "paginate-elements-by-height" property.
I have a page of 2424px of height containing some "<section>" :
section 1 : '121px' of height
section 2 : '495px' of height
section 3 : '311px' of height
section 4 : '84px' of height
section 5 : '156px' of height
section 6 : '553px' of height
section 7 : '455px' of height
(I had too some margins between sections ~ '250px')
My question is what value put in "paginate-elements-by-height" ?
An alternative question, is it possible to force all sections to be on a separate page ? Something like "page-break: auto" ?
Thanks for your help,
Regards

Lets say you set the value of paginate-elements-by-height to 650, that means per page you will have a maximum of  height of 650px .
The script will loop through each sections, and add their height + margin top + margin bottom.
So lets take your sample sections into the example, it will work something like this:
section 1 : '121px' of height
section 2 : '495px' of height
section 3 : '311px' of height
section 4 : '84px' of height
let currentPageHeight = 0
1st loop:
const sectionHeight = (section1 height) + (section1 margin top) + (section1 margin bottom)
// currentPageHeight = 0
// sectionHeight = 121

Check if (currentPageHeight + sectionHeight)  <= 650
If true:
1.)  currentPageHeight = currentPageHeight + sectionHeight
2.)  Add the section to page 1
3.)  Go to next loop
if false:
1.)  currentPageHeight =  sectionHeight
2.)  Add the section to page 2
3.)  Go to next loop

The condition will be TRUE, since 0 + 121 <= 650, it will proceed with the steps in the true section
2nd loop:
const sectionHeight = (section2 height) + (section2 margin top) + (section2 margin bottom)
// currentPageHeight = 121
// sectionHeight = 495

Check if (currentPageHeight + sectionHeight)  <= 650
If true:
1.)  currentPageHeight = currentPageHeight + sectionHeight
2.)  Add the section to page 1
3.)  Go to next loop
if false:
1.)  currentPageHeight =  sectionHeight
2.)  Add the section to page 2
3.)  Go to next loop

The condition will be TRUE, since 121 + 495 <= 650, it will proceed with the steps in the true section
3rd loop:
const sectionHeight = (section3 height) + (section3 margin top) + (section3 margin bottom)
// currentPageHeight = 616
// sectionHeight = 311

Check if (currentPageHeight + sectionHeight)  <= 650
If true:
1.)  currentPageHeight = currentPageHeight + sectionHeight
2.)  Add the section to page 1
3.)  Go to next loop
if false:
1.)  currentPageHeight =  sectionHeight
2.)  Add the section to page 2
3.)  Go to next loop

The condition will be FALSE, since 616 + 311<= 650, it will proceed with the steps in the false section
4th loop:
const sectionHeight = (section4 height) + (section4 margin top) + (section4 margin bottom)
// currentPageHeight = 311
// sectionHeight = 84

Check if (currentPageHeight + sectionHeight)  <= 650
If true:
1.)  currentPageHeight = currentPageHeight + sectionHeight
2.)  Add the section to page 2
3.)  Go to next loop
if false:
1.)  currentPageHeight =  sectionHeight
2.)  Add the section to page 3
3.)  Go to next loop

The condition will be TRUE, since 311+ 84 <= 650, it will proceed with the steps in the true section
For your alternative question:
Lets say you set the value of paginate-elements-by-height to 650 again, just set all your sections to height: 650px it will let your whole section take a whole page.
I will soon make an easier way to for page breaks, same as html2pdf.js page breaks, since this package uses html2pdf.js under-the-hood

Hey, nice package has helped me use jsPDF in our project.
Having issues with page break and top/bottom margins though. Any update on the page break feature? Been playing with this for an hour and no matter what I try between sections, styles and paginate-elements-by-height, my dynamic content will sometimes get split in bad places (like a single word or sentence on the next page) and without being able to set margins, the breaks are right at the edge of the page.

Hey, im a bit busy but I might get it done within this week i presume.

Hey, The page breaks is now available on version 1.6.0
You can also disable the automatic pagination by enabling the prop manual-pagination
Here is the documentation

Great job !
the previous version (1.3) was buged, i had all tryed but sometimes the script run at infinite (100% processor activity) without render any pdf :(
This version (1.6) never bug what i seen !
It's just in console you (or html2pdf) forgot to disabled the "trace mode" 😄


Add GreenPower (242) endpoint

Add the greenPower (242) endpoint for the TS130F module
See more here about the issue : https://github.com/home-assistant/core/issues/46146#issuecomment-929584833

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 81.152%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
4172

Relevant Lines:
5141

💛  - Coveralls

And the back light added 2 :-)))
What i dont like is that the signature is not reflecting the device real clusters and EP 2 is missing with its GP cluster.
It can being good later if need adding more device or if tuya (as normal) is making one device with time cluster as out instead of in.
 {
   "1": {
      "profile_id": 260,
      "device_type": "0x0202",
      "in_clusters": [
        "0x0000",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0102"
      ],
      "out_clusters": [
        "0x000a",
        "0x0019"
      ]
    },
    "242": {
      "profile_id": 41440,
      "device_type": "0x0061",
      "in_clusters": [],
      "out_clusters": [
        "0x0021"
      ]
    }

Some quirk have only copy from one already added device and not fixing the clusters and its making it bad and is better not putting in information then false information then it making it only misleading.
Well done !!!


moq having issues with build tags

trying to use moq to mock an interface from a package that imports "github.com/garyburd/redigo/redis" elsewhere in the code...I'm getting:
# go generate
main.go:11:2: could not import github.com/garyburd/redigo/redis (/go/src/github.com/graymeta/mf2/vendor/github.com/garyburd/redigo/redis/pre_go17.go:8:6: cloneTLSClientConfig redeclared in this block)
moq [flags] destination interface [interface2 [interface3 [...]]]
  -out string
        output file (default stdout)
  -pkg string
        package name (default will infer)
log.go:3: running "moq": exit status 1

You can reproduce it with this:
package main

//go:generate moq -out mock_logger.go . Logger

import (
    "log"

    "github.com/garyburd/redigo/redis"
)

func main() {
    p := redis.Pool{
        Dial: func() (redis.Conn, error) {
            return redis.Dial("tcp", "<IP_ADDRESS>:6379")
        },
    }
    log.Printf("%v", p)
}

type Logger interface {
    SomeFunc(a int)
}

It looks like that redis package is using build tags for different versions of go: https://github.com/garyburd/redigo/blob/master/redis/go17.go#L1

https://github.com/matryer/moq/pull/45 seems to fix this.


Memberof plugin

Enable memberof plugin

@uubk Ping :)

@F1rst-Unicorn can we get this merged? :)

@lukasreichart please note that I took action for each comment I received. So I think it can be merged

@mxmo0rhuhn  / @lukasreichart / @F1rst-Unicorn This one is on me - I have two LDAP related PRs open that I need to test, which is going to take about half a day and I didn't have the time yet. Trying to squeeze that it somewhen in July/August.

@uubk is there anything we still need to do, to get this merged?

@uubk any updates on this?


Add option for discrete compounding when calculating annuities

PG has always used continuous compound rather than discrete. It's a choice that users will probably not be aware of and there is no easy way to change it.

Create separate functions for each compounding formula.
Let users select the formula in their settings file. Which formula should be the default?
Document!

@xuqingyu, any chance you can help with this?

yes, I can do that.


Feature request: Add the possibility to fix table header row

Hello,
would it be possible to implement a way in which a table's header row is 'pinned' and only the following columns are scrollable?

Hello @saadeghi, May i get assigned this issue?

@urtheaman sure

Thank You.

I'm sorry for being late sir. i'll make the pr today.

No problem! Let me know if I can help

@xvimnt There's a PR by @urtheaman (Thanks!): https://github.com/saadeghi/daisyui/pull/918
But honestly I haven't tested it yet.
The challenge:
I can't decide which way it should be.
Currently table's first column (tr>th) is sticky by default and some people asked for a non-sticky column as a default. I'm not sure about how adding these new class names pinned-row and pinned-col should affect that.

Maybe we can just remove the default sticky style and make it possible to be sticky by adding these new class names
Maybe instead of 2 new class names pinned-row and pinned-col I think it can be one pinned class. I'm not sure.
What happens if many rows and columns have that pinned class? (I haven't tested it yet)

I don't want to add a new style that might create unpredicted problems and then I after people started using it, turns out there were unpredicted issues. At this point I'm not sure which way is the safest way to handle it and I haven't invest time to explore possible downsides because I was focusing on other stuff.