Installation on debian 8

I have no idea how to install it. I used pip3 to install it but nothing works, there is no config file, the autoxtrabackup command is non existent etc...
I don't even know how to clean what I just installed :(

@BarbzYHOOL Hi,
What is the exact installation problem?
You can refer the doc:
http://mysql-autoxtrabackup.readthedocs.io/en/latest/installation.html

Your installation is for centos or smthg like that.
I installed it with
pip3 install mysql-autoxtrabackup
And it said "install successful" but then nothing works, the command doesn't exist.

Again you can install it from source.
Clone the repo go to the cloned folder and run sudo python3 setup.py install

running install
Checking .pth file support in /usr/local/lib/python3.4/dist-packages/
/usr/bin/python3 -E -c pass
TEST PASSED: /usr/local/lib/python3.4/dist-packages/ appears to support .pth files
running bdist_egg
running egg_info
creating mysql_autoxtrabackup.egg-info
writing dependency_links to mysql_autoxtrabackup.egg-info/dependency_links.txt
writing mysql_autoxtrabackup.egg-info/PKG-INFO
writing top-level names to mysql_autoxtrabackup.egg-info/top_level.txt
writing requirements to mysql_autoxtrabackup.egg-info/requires.txt
writing entry points to mysql_autoxtrabackup.egg-info/entry_points.txt
writing manifest file 'mysql_autoxtrabackup.egg-info/SOURCES.txt'
reading manifest file 'mysql_autoxtrabackup.egg-info/SOURCES.txt'
writing manifest file 'mysql_autoxtrabackup.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build
creating build/lib
copying autoxtrabackup.py -> build/lib
creating build/lib/general_conf
copying general_conf/__init__.py -> build/lib/general_conf
copying general_conf/generalops.py -> build/lib/general_conf
copying general_conf/check_env.py -> build/lib/general_conf
creating build/lib/backup_prepare
copying backup_prepare/__init__.py -> build/lib/backup_prepare
copying backup_prepare/prepare.py -> build/lib/backup_prepare
creating build/lib/partial_recovery
copying partial_recovery/__init__.py -> build/lib/partial_recovery
copying partial_recovery/partial.py -> build/lib/partial_recovery
creating build/lib/master_backup_script
copying master_backup_script/__init__.py -> build/lib/master_backup_script
copying master_backup_script/backuper.py -> build/lib/master_backup_script
creating build/lib/prepare_env_test_mode
copying prepare_env_test_mode/__init__.py -> build/lib/prepare_env_test_mode
copying prepare_env_test_mode/prepare_backup.py -> build/lib/prepare_env_test_mode
copying prepare_env_test_mode/test_check_env.py -> build/lib/prepare_env_test_mode
copying prepare_env_test_mode/clone_build_start_server.py -> build/lib/prepare_env_test_mode
copying prepare_env_test_mode/run_benchmark.py -> build/lib/prepare_env_test_mode
copying prepare_env_test_mode/take_backup.py -> build/lib/prepare_env_test_mode
copying prepare_env_test_mode/runner_test_mode.py -> build/lib/prepare_env_test_mode
copying prepare_env_test_mode/config_generator.py -> build/lib/prepare_env_test_mode
copying prepare_env_test_mode/run_sql_queries.sh -> build/lib/prepare_env_test_mode
copying prepare_env_test_mode/build_2.3_pxb.sh -> build/lib/prepare_env_test_mode
copying prepare_env_test_mode/build_2.4_pxb.sh -> build/lib/prepare_env_test_mode
copying prepare_env_test_mode/start_dynamic.sh -> build/lib/prepare_env_test_mode
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/general_conf
copying build/lib/general_conf/__init__.py -> build/bdist.linux-x86_64/egg/general_conf
copying build/lib/general_conf/generalops.py -> build/bdist.linux-x86_64/egg/general_conf
copying build/lib/general_conf/check_env.py -> build/bdist.linux-x86_64/egg/general_conf
copying build/lib/autoxtrabackup.py -> build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/partial_recovery
copying build/lib/partial_recovery/__init__.py -> build/bdist.linux-x86_64/egg/partial_recovery
copying build/lib/partial_recovery/partial.py -> build/bdist.linux-x86_64/egg/partial_recovery
creating build/bdist.linux-x86_64/egg/prepare_env_test_mode
copying build/lib/prepare_env_test_mode/__init__.py -> build/bdist.linux-x86_64/egg/prepare_env_test_mode
copying build/lib/prepare_env_test_mode/prepare_backup.py -> build/bdist.linux-x86_64/egg/prepare_env_test_mode
copying build/lib/prepare_env_test_mode/test_check_env.py -> build/bdist.linux-x86_64/egg/prepare_env_test_mode
copying build/lib/prepare_env_test_mode/run_sql_queries.sh -> build/bdist.linux-x86_64/egg/prepare_env_test_mode
copying build/lib/prepare_env_test_mode/clone_build_start_server.py -> build/bdist.linux-x86_64/egg/prepare_env_test_mode
copying build/lib/prepare_env_test_mode/build_2.3_pxb.sh -> build/bdist.linux-x86_64/egg/prepare_env_test_mode
copying build/lib/prepare_env_test_mode/build_2.4_pxb.sh -> build/bdist.linux-x86_64/egg/prepare_env_test_mode
copying build/lib/prepare_env_test_mode/run_benchmark.py -> build/bdist.linux-x86_64/egg/prepare_env_test_mode
copying build/lib/prepare_env_test_mode/take_backup.py -> build/bdist.linux-x86_64/egg/prepare_env_test_mode
copying build/lib/prepare_env_test_mode/runner_test_mode.py -> build/bdist.linux-x86_64/egg/prepare_env_test_mode
copying build/lib/prepare_env_test_mode/start_dynamic.sh -> build/bdist.linux-x86_64/egg/prepare_env_test_mode
copying build/lib/prepare_env_test_mode/config_generator.py -> build/bdist.linux-x86_64/egg/prepare_env_test_mode
creating build/bdist.linux-x86_64/egg/backup_prepare
copying build/lib/backup_prepare/__init__.py -> build/bdist.linux-x86_64/egg/backup_prepare
copying build/lib/backup_prepare/prepare.py -> build/bdist.linux-x86_64/egg/backup_prepare
creating build/bdist.linux-x86_64/egg/master_backup_script
byte-compiling build/bdist.linux-x86_64/egg/general_conf/__init__.py to __init__.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/general_conf/generalops.py to generalops.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/general_conf/check_env.py to check_env.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/autoxtrabackup.py to autoxtrabackup.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/partial_recovery/__init__.py to __init__.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/partial_recovery/partial.py to partial.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/prepare_env_test_mode/__init__.py to __init__.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/prepare_env_test_mode/prepare_backup.py to prepare_backup.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/prepare_env_test_mode/test_check_env.py to test_check_env.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/prepare_env_test_mode/clone_build_start_server.py to clone_build_start_server.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/prepare_env_test_mode/run_benchmark.py to run_benchmark.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/prepare_env_test_mode/take_backup.py to take_backup.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/prepare_env_test_mode/runner_test_mode.py to runner_test_mode.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/prepare_env_test_mode/config_generator.py to config_generator.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/backup_prepare/__init__.py to __init__.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/backup_prepare/prepare.py to prepare.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/master_backup_script/__init__.py to __init__.cpython-34.pyc
byte-compiling build/bdist.linux-x86_64/egg/master_backup_script/backuper.py to backuper.cpython-34.pyc
installing package data to build/bdist.linux-x86_64/egg
running install_data
copying general_conf/bck.conf -> //etc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying mysql_autoxtrabackup.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mysql_autoxtrabackup.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mysql_autoxtrabackup.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mysql_autoxtrabackup.egg-info/entry_points.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mysql_autoxtrabackup.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mysql_autoxtrabackup.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
prepare_env_test_mode.__pycache__.take_backup.cpython-34: module references __file__
prepare_env_test_mode.__pycache__.clone_build_start_server.cpython-34: module references __file__
creating dist
creating 'dist/mysql_autoxtrabackup-1.5.1-py3.4.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing mysql_autoxtrabackup-1.5.1-py3.4.egg
creating /usr/local/lib/python3.4/dist-packages/mysql_autoxtrabackup-1.5.1-py3.4.egg
Extracting mysql_autoxtrabackup-1.5.1-py3.4.egg to /usr/local/lib/python3.4/dist-packages
Adding mysql-autoxtrabackup 1.5.1 to easy-install.pth file
Installing autoxtrabackup script to /usr/local/bin

Installed /usr/local/lib/python3.4/dist-packages/mysql_autoxtrabackup-1.5.1-py3.4.egg
Processing dependencies for mysql-autoxtrabackup==1.5.1
Searching for pytest==3.4.0
Best match: pytest 3.4.0
Adding pytest 3.4.0 to easy-install.pth file
Installing py.test script to /usr/local/bin
Installing pytest script to /usr/local/bin

Using /usr/local/lib/python3.4/dist-packages
Searching for humanfriendly==4.8
Best match: humanfriendly 4.8
humanfriendly 4.8 is already the active version in easy-install.pth
Installing humanfriendly script to /usr/local/bin

Using /usr/local/lib/python3.4/dist-packages
Searching for pid==2.1.1
Best match: pid 2.1.1
pid 2.1.1 is already the active version in easy-install.pth

Using /usr/local/lib/python3.4/dist-packages
Searching for mysql-connector==2.1.4
Best match: mysql-connector 2.1.4
mysql-connector 2.1.4 is already the active version in easy-install.pth

Using /usr/local/lib/python3.4/dist-packages
Searching for click==6.7
Best match: click 6.7
click 6.7 is already the active version in easy-install.pth

Using /usr/local/lib/python3.4/dist-packages
Searching for attrs==17.4.0
Best match: attrs 17.4.0
attrs 17.4.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.4/dist-packages
Searching for setuptools==5.5.1
Best match: setuptools 5.5.1
Adding setuptools 5.5.1 to easy-install.pth file
Installing easy_install script to /usr/local/bin
Installing easy_install-3.4 script to /usr/local/bin

Using /usr/lib/python3/dist-packages
Searching for six==1.11.0
Best match: six 1.11.0
six 1.11.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.4/dist-packages
Searching for py==1.5.2
Best match: py 1.5.2
py 1.5.2 is already the active version in easy-install.pth

Using /usr/local/lib/python3.4/dist-packages
Searching for pluggy==0.6.0
Best match: pluggy 0.6.0
pluggy 0.6.0 is already the active version in easy-install.pth

Using /usr/local/lib/python3.4/dist-packages
Finished processing dependencies for mysql-autoxtrabackup==1.5.1

Same result:
$ autoxtrabackup
bash: autoxtrabackup: command not found

And there is no autoxtrabackup under /usr/local/bin
What is the result of?
$ ls /usr/local/bin

Yes, autoxtrabackup is there and I can run it with /usr/local/bin/autoxtrabackup
So it means the shortcut to the command hasn't been created ?

I think No, it means the /usr/local/bin is not in your PATH.
Maybe you can check it to include this path to your PATH, or just use it with full path as you did.

"Maybe you can check it to include this path to your PATH, "
how? and why it happened?

It is common thing in Linux to not find executable because it is some path which is not included to your environment PATH.
You can check it as:
$ env | grep PATH
Or
$ echo $PATH
For eg, let's create a situation where our executable is missing:
shako@shako-localhost:~$ pwd
/home/shako
shako@shako-localhost:~$ touch test_executable
shako@shako-localhost:~$ chmod +x test_executable

Adding some echo into this file:
$ echo 'echo "Hello World"' > test_executable

Now let's try to run it with non-relative call:
$ test_executable
test_executable: command not found

To fix this I am going to add my path(/home/shako) to PATH:
shako@shako-localhost:~$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
shako@shako-localhost:~$ export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/shako
shako@shako-localhost:~$ echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/home/shako

Now trying to run again:
shako@shako-localhost:~$ test_executable
Hello World

As you see now it found the executable.

@BarbzYHOOL any other questions here?

Ok, I added it to my bashrc, thank you very much.
I think this issue is solved, now I must try the script in itself!

But how would I have find that the file was in that directory without your help?

@BarbzYHOOL Actually I read the path from output which you have pasted:
.
.
Adding mysql-autoxtrabackup 1.5.1 to easy-install.pth file
Installing autoxtrabackup script to /usr/local/bin
.
.

Ok, ty :)

:) Feel free to open new issues.
Thanks.


The Calculator is accepting alphanumeric keys(A-Z) along with numeric input. To disable alphanumeric key inputs.

ok i will

I remove the logic expression that check the user input and it's work. Because, the ASCII code for the number is only in the first logic expression. I think the second expression (after or) is unnecessary.

Let me check your work @chanunegi @purenaturalism

Is the issue still open or fixed? @MohitChattlani

I was looking to start work on this issue but I notice PR #9 claims to have fixed it. Is that the case and if so should it be merged?

it has been fixed @bhatiatanish @PhyscoKillerMonkey


A question about parameters update

In the following code, it seems that the parameter 'c' is never used.
`
        lstm_preactive = tf.matmul(h, self.lstm_U) + x_t + tf.matmul(weighted_context,self.image_encode_W)

        i, f, o, new_c = tf.split(1, 4, lstm_preactive)

        i = tf.nn.sigmoid(i)
        f = tf.nn.sigmoid(f)
        o = tf.nn.sigmoid(o)
        new_c = tf.nn.tanh(new_c)
        c = f * c + i * new_c
        h = o * tf.nn.tanh(new_c)`

Why the parameter 'h' depends on 'new_c' rather than 'c'?
In my opinion, i think the updating procedures should be
c(t) = f(t) * c(t−1) + i(t) * new_c(t)
h(t) = o(t) *  tanh(c(t))

Yeah, I also think that the update should be h=otan(c) instead of h=otan(g)

Hello, I don't quite understand the meaning of x_t . Could you give me some hints? Thank you!

Yes,the author in this package was wrong, @automan000  you are right!

I use the author's original model （didn't change the h(t) = o(t) *  tanh(c(t)) ）after 12 epoch ,the current loss only reduced to 2.96379992 ，is it right ？the loss is so big that the generated words only  have one item that can not join into a sentence
@Wind-Ward Could I ask how many epoch did you use to train a model that the result is satisfactory after change the mistake you point ？
or without changing the mistake ，can I train a model that is satisfactory？
I would appreciate it if you can give me apply.I am a student from China ,not being good at English,sorry if I don't express well.


Port the StarAlgebraMixin from Nature and Add TensorMixin

Summary
Port the StarAlgebraMixin from Nature to core.
Related to Qiskit/qiskit-nature#117.
I also added TensorMixin in a similar way with StarAlgebraMixin.
Details and comments
StarAlgebraMixin is a mixin class originally designed for Nature, but it can be used in opflow as well, so I'm moving it here.
When I port it, I refactored it for opflow, so the specification has changed a bit. For example, add with 0 only supported the right side, but this PR supports both. I splitted __power__, made power(), and it's argument name is changed from power to exponent. I've also added docs.

Should we have reno describing these new mixins as new/ported from Nature

Thank you . I did not know reno is needed to update.

Thank you . I did not know reno is needed to upgrade.

I was thinking more that we have introduced the mixins themselves that can be used by new code etc. The internal change to use them is of course an aspect.


target image file name is fixed to "page-"

Hi,
Thank you for this great conversion utility.
I just like to ask if it is possible to pass a "target file name for the converted images" maybe in the next version?
example:
 function convert($filename); // without extension

       $image_path = $this->output_path."/".$filename."-%d.".$this->imageExtention;

       $fileArray[] = $filename."-$i.".$this->imageExtention;

Thanks in advance

@mablae @ahfeel @joshbmarshall guys can you please see this something we should implement ?

it would be a nice enhancement.
However it needs to be done in a BC secure way or implies new major Version with this approach. (New param would break BC)
Instead introducing an new parameter it could be done with a new Constructor param called filenamePattern which defaults to the current one maintaining BC
It also needs to be checked to contain page parameter and then use sprintf to fill the page number later on. This way we could have 01-page.pdf, too.
Let me know what you think.

You'd definitely do it in the way you currently set resolution - by adding as a setter method. So the default would be page- and the function would let you override. No BC issues then as @mablae suggested. That should be fairly straightforward to implement and use.
Going on conventions of other software I doubt we need to have the page number configurable in the image file name.
Do you want a pull request?

I think I agree with @mablae too, it is the way to go! @joshbmarshall please go ahead if you have time

pull request has been submitted #14

Can anyone review @joshbmarshall 's code and merge it and create tag for release version 1.2.2, if all are busy I'll have a look at this tonight and probably merge it.. please make sure Tests are passing

I just added to the pull request, some PHPDoc and add method chaining to allow end users have cleaner code.

@joshbmarshall thanks for the great work!!!

@imalhasaranga there is one test not passing on the current master with Ghostscript v9.26 on linux - PDFLibTest::testImageToPdf

hmm! we should find the root case and fix it, I mean tests are the only way we know that nothing has broken.. probably this may be an issue existed from the begining and no one noticed it

sorry release should be v1.2.3

I have found the issue with the gs on linux, putting in a fix now will add to the pull request

Done, please check tests pass on windows. They all pass on Alpine Linux with PHP7.3.2

Thank you for fixing this issue. I really needed the fix.
If it is okay to ask, when would it be the next release for version 1.2.3 be available?
Thanks again and more power to you guys who made this amazing conversion utility.

Since this is a new feature I would release as v1.3.0

@vtsoft v1.3.0 is released, @mablae agreed!! @joshbmarshall awesome work mate!!! cheers

@imalhasaranga, @mablae, @joshbmarshall,
Guys, Thanks for the quick release of the new version. It's really a great help.
So far, I'm starting to test/apply on the ff. platforms:
was able to test it in windows 10 pro, and it works like a charm.
no issue encountered so far.
will test it in CentOs 6.8.
but still looking for the right package and version to use on Ghostscript.
If not too much to ask,
I just like to know the link to which version of Ghostscript did you use in CentOs 6.8 during your testing.
Thanks again and more power to you guys.
I know for sure that this is the right place to ask.

@vtsoft I have not used CentOS 6 for over 4 years. Even CentOS 7 has too old a version. You just need gs version 9.16 or newer. I tested with v9.26. Maybe you can use the GPL linux binaries from https://ghostscript.com/download/gsdnld.html

@joshbmarshall Thank you for your help.
PDFlib using Ghostscript is now running in CentOs server.
and Thanks again all of you guys.


Support public accounts by using transaction builder in wallet::withdraw_delegate_pay

Delegate pay withdrawal does a TITAN transaction even when targeted to a public account.  The wallet::withdraw_delegate_pay function currently creates a transaction directly.  We should instead create the transaction with a transaction builder, which contains logic to check whether the recipient is public or TITAN.

Was fixed in #1319 and related.


Route parameter value with an encoded '?' as %3F not decoded in params

Version
4.1.1
Test Case
https://codesandbox.io/s/zqj6wvk7m3
Steps to reproduce
click on the  Topic Example ?
Expected Behavior
topic example %3F should be displayed as topic example ?
Actual Behavior
the param is displayed as topic example %3F

This is ultimately caused by history. Here's the issue open to track the bug: ReactTraining/history#505

I would say that if you have characters that need to be encoded using encodeURIComponent, you should expect to have to call decodeURIComponent to decode them.

I don't think this workaround is generally safe, due to the fact that decodeURI and decodeURIComponent have overlapping reserved character sets, so calling decodeURIComponent on a string that has already been decoded by decodeURI runs the risk of double-decoding. Consider this example:
> encodedPathComponent = '%2520%2F'
'%2520%2F'
> correctDecodedValue = '%20/'
'%20/'
> decodeURIComponent(encodedPathComponent) == correctDecodedValue
true
> decodeURI(encodedPathComponent) == correctDecodedValue
false
> decodeURIComponent(decodeURI(encodedPathComponent)) == correctDecodedValue
false

I fear the above example might not be the clearest, but the intention is to show that there are validly-encoded URL path components that cannot be correctly decoded once decodeURI is called on them. If react-router offered a way to opt-out of the automatic decoding that could be an acceptable workaround.


WIP investigate missing RWX_ACCESS_TOKEN_STAGING

I removed my user from the staging org earlier this morning. I don’t suspect that’s related, but I wanted to call it out just in case.

looks like this is resolved, right?


Support git commit?

It looked like it worked only for git to display Aborting commit due to empty commit message. when I toggled the terminal back on (using ToggleTerm).
Is this already supported and I misconfigured something, or is it not? I assume it's not because in the readme it's mentioned as an example where you might want to turn unception off: https://github.com/samjwill/nvim-unception/blob/0422fa9bc16d0bedeab7cb3880063a6bd8631067/README.md?plain=1#L52

That's correct. It is not currently supported.
The issue is that git will proceed as if editing for the commit file has been completed as soon as the editor command returns. Basically, what happens is:

Git launches nested Neovim
Nested neovim sends command to the server (host) session and exits
Git sees that nested session that it launched has exited and moves forward with the commit (which is empty)
Server edits file that the nested session told it to

I'm not sure of an elegant way to handle this, though I'd definitely be interested in ideas if anyone has some. You might be able to get clever by updating your .gitconfig to set the editor to run a --remote-send command to the Neovim server to get it to open the git commit message buffer, and keep somehow it alive while it's still being edited by the host.

Ok that makes a lot of sense, thanks for the detailed response!
If an elegant solution is not found maybe it should be out-of-scope imo. Keeping this issue open for future reference.

Actually, it looks like this might be pretty easy to do once --remote-wait is implemented into Neovim Core.

While --remote-wait isn't yet implemented in neovim core, I've known neovim-remote for a while now which enables you to use the remote wait functionality as expected.
@samjwill what are your thoughts on using this project as a workaround until --remote-wait gets merged in?

That'd definitely be an option. An environment variable containing the named pipe path that the Neovim host session is using is accessible from within the terminal emulator, so I think it would simply be a matter of aliasing your git command in your .bashrc.
I glanced at Neovim's RPC doc, and it actually looks like I could probably leverage that to implement my own --remote-wait directly without necessitating any third party tools, or even Python. I'm unsure of how well it would work. I'll probably tinker with it a bit more :)

I managed to implement this in a branch. Definitely needs a decent amount of testing before merging into main, since I'm not sure if it works perfectly, there's still some code cleanup to do, and some of the stuff I did to get it to work seems a bit hacky. But hey, it seems to work at first glance! Here's what it looks like:
https://user-images.githubusercontent.com/25990267/198911868-a7a20c7a-7281-44ad-87d4-bfbe1204e124.mp4

Okay, merged. Please see the updated section of the README if you would like ti give it a shot!

Just wanted to add that this is working great!

@cultab Super happy to hear it! It's the first time I've worked with RPCs in Lua so I was a bit worried that it might be a sorta janky.
Don't hesitate to let me know if you run into issues!


how to set exe icon on windows?

how to set exe icon on windows?
BTW, i can using Chinese and emoji on windows without pain, but on linux, emoji can not be used.

I'll close this issue because it's exactly the same as #510


[GetAllAssetAdministrationShellsByAssetId] Intended Use Case?

What?
GetAllAssetAdministrationShellsByAssetId (i.e., /shells?assetIds=XYZ) is providing functionality similar to the AAS Discovery (GetAllAssetAdministrationShellIdsByAssetLink), however, limited to a single AAS Repository.
In a fully distributed deployment it may not behave as expected because the AAS it is looking for may be in a different repository. As a result, using this endpoint in an application may become an obstacle to later changes in the architecture when an AAS is redeployed (similar to the superpaths discussed in other tickets). As a result, from my understanding, this endpoint ties the application using it to the architectural decision to use a centralised approach, and I would not use it to avoid changes in applications due to possible future redeployments.
Is there another intended use for this endpoint that I'm not aware of were it would provide value?

[x] I have signed the required Developer Certificate of Origin (DCO) already.

Hello Frank,

this endpoint ties the application using it to the architectural decision to use a centralised approach

Why would that be the case? Given that the result of this call would be an empty array, the only conclusion the client can make is that "This repository does not contain the AAS for my Asset" but not "No AAS exists for my Asset".
It's the general topic of open world vs. closed world views, isn't it?

We discussed this topic in the meeting today. While we all share the general view that an empty response from any AAS service must not be interpreted in a way that a respective AAS, Submodel, Asset etc. does not exist, we agree that this has not yet been clearly communicated.
Therefore, the proposal is to add a statement explaining the topic into the AAS API (Part 2) document.

The AAS Specification Workstream supports the proposal, therefore, an explaining statement will be added in the next publication.

The underlying point of my question was about the centralized vs. a decentralized way to build the AAS infrastructure. The components are described as highly distributed and scalable infrastructure consisting of various microservices (e.g., separate Discovery, Registries, Repositories). This infrastructure has a clear interaction pattern for finding AAS belonging to an asset, i.e., query the AAS Discovery, then query the AAS Registry, and finally query the AAS Repository. Some endpoints, such as the GetAllAssetAdministrationShellsByAssetId endpoint break this decentralized view by introducing endpoints that covers some of the responsibilities of other components (here: the AAS Discovery), resulting in a monolithic component that covers multiple responsibilities – but with limited scope. Thus, any application using this endpoint assumes a centralized system where the referenced AAS Repository contains the AAS being searched for.  However, this locks the application to the centralized approach where there are no truely distributed (and independent) microservices, and consequently makes it difficult to change the architecture later when scalability issues may arise.
In my opinion, the reason or use case for using this endpoint instead of the AAS Discovery is not clear. Is it just convenience? If so, it should be labelled to indicate that this is a “shortcut” for demonstration purposes and should not be used for real-world deployments where scalability might become relevant.


resizing under glos needs a bit better logic

needs further investigation: doesn't really update render during resizing but does resquish contents using Draw function  -- probably getting a lot of redundant post-resize events that could be more efficiently processed.
also commented out glw.SetRefreshCallback due to excessive flickering but that could be important for Bug #270

also resizing larger needs a blank event pushed -- currently leaves extra size region black until next event (mouse move) comes through.

yes getting all those events but not clear that there is a more efficient way to filter than what is already there.
also not clear how to fix the lack of recognizing the end of the stream for the larger size -- maybe just a timing issue or something?

not really fixable I think and working fine -- main issue now is textview.


Docker compose up/down not working due to misconfigured depends_on at docker-compose.yml

Bug Report
Problematic behavior
Using docker compose down after the bootstrap and docker compose up to start the project again will lead to the following error:
impress-nginx-1          | 2024/10/15 08:35:13 [emerg] 1#1: host not found in upstream "app-dev" in /etc/nginx/conf.d/default.conf:25
impress-nginx-1          | nginx: [emerg] host not found in upstream "app-dev" in /etc/nginx/conf.d/default.conf:25
impress-nginx-1 exited with code 1
This behavior makes sense as the docker-compose file appears to be configured wrong. At the app-dev: section, we have a depends_on -nginx, but vise versa nginx cannot work without app-dev ... To resolve this, nginx should get removed from depends_on at app-dev, and instead we should make nginx depend_on app-dev.
Expected behavior/code
I would expect to stop and restart the project using docker compose up/down
Steps to Reproduce
Spin up a fresh deployment from the main branch, after that use docker compose down and right after that docker compose up again, this will output the error mentioned above, and the development environment cannot be used as not all services coming up (nginx breaks right after start).
Environment

Impress version: main
Platform: Linux

Possible Solution
  app-dev:
    build:
      context: .
      target: backend-development
      args:
        DOCKER_USER: ${DOCKER_USER:-1000}
    user: ${DOCKER_USER:-1000}
    image: impress:backend-development
    environment:
      - PYLINTHOME=/app/.pylint.d
      - DJANGO_CONFIGURATION=Development
    env_file:
      - env.d/development/common
      - env.d/development/postgresql
    ports:
      - "8071:8000"
    volumes:
      - ./src/backend:/app
      - ./data/static:/data/static
    depends_on:
        - postgresql
        - mailcatcher
        - redis
        - createbuckets
        - nginx # Needs to be removed

  nginx:
    image: nginx:1.25
    ports:
      - "8083:8083"
    volumes:
      - ./docker/files/etc/nginx/conf.d:/etc/nginx/conf.d:ro
    depends_on:
      - keycloak
      - app-dev # Needs to be added

Solution available here:
https://github.com/numerique-gouv/impress/pull/340


Remove "Manual" alias for some content-types

Feature request
Summary
Hello.
Now that we can disable URL-Alias for some content-type, I think we could benefit from having certains content-type alias not bein editable (ie, only generated).
Why is it needed?
The base idea of using URL-Alias is to be able to have your frontend router agnotic about URI, giving more power to the adminitrator to create pages. It also mean using a single endpoint to retrieve all (or almost all)your content-type
Sometimes though, for specific pages, it could be useful to enforce a specific layout on router side, while maintaining the single endpoint. This would also give the strapi administrator the information about the URL on frontend.
Ex: Having a list of tag with generated URL only (/tags/[slug]) would correspond on frontend side to a specific component (/tags/[slug].vue using nuxt 3 for instance) which would do some more complex behavior than a single page, displaying several articles related to the tag.
Suggested solution(s)
Adding another checkbox on content-type options to prevent Alias edition.
Disclosure
I used to maintain the "custom-link" plugin available on strapi marketplace but I don't have enough time right now to work on it right now. I guess I should focus on trying to improve this one instead.

I guess this would be most easily solved by using admin permissions to revoke the right of editing the URL alias.
Then you could just revoke those rights for the editor role and we've achieved what you describe here.

Hi @Norbz, I reviewed your request, and I can confirm that this can be achieved using the plugin settings. If you leave the checkbox blank the user will not have the url alias sidebar.

If you can confirm that this resolves your issue, I'll close this issue.
Thank you for your time.

Hi @TMSchipper
This is perfect, and a great use for some use cases. Thank you for the update =)


Allow authentication by environment IAM credentials

Driver version
v2.0.872
Redshift version
PostgreSQL 8.0.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3), Redshift 1.0.22169
Client Operating System
Amazon Linux 2 for Python 3.8 Lambda
Python version
Python 3.8
Problem description
I would like the driver to authenticate via the environment IAM credentials(for examples in AWS Lambda environment with IAM Role with sufficient permissions for get_cluster_credentials).
I should be able to execute the following code in an environment with IAM credentials with sufficient permissions:
import redshift_connector
conn = redshift_connector.connect(
    cluster_identifier='examplecluster,
    database='dev',
    user='awsuser',
    iam=True,
    credentials_provider='IAMProvider', # proposed.
 )

Expected behaviour: Should work
Actual behaviour: Doesn't work.
Error message/stack trace: Invalid connection property setting. password must be specified
Any other details that can be helpful:

The driver can already authenticate via get_cluster_credentials method: https://github.com/aws/amazon-redshift-python-driver/blob/77a9c1de1f6ce54266ff67bc6aa894d3b4910240/redshift_connector/iam_helper.py#L246-L265
The code just needs the following some small adjustments to achieve this:

The connection validation logic should allow password not being specified in the case iam == True and credentials_provider == 'IAMProvider'
an IAMProvider as a credential provider is created, which would return None for access key, secret and session token.

I would be happy to make a pull request to do above, in case someone from the project agrees with the changes.
Our use case
We always use get_cluster_credentials so we don't have to care about rotating secrets, since our code is already running in AWS managed compute environment(Lambda, Fargate, Glue Python Shell), the IAM credentials are already present in the environment. Since this driver already contains the code for get_cluster_credentials it would be shame that we would have to duplicate that code everywhere.
Reproduction code
import redshift_connector
conn = redshift_connector.connect(
    cluster_identifier='examplecluster,
    database='dev',
    user='awsuser',
    iam=True,
    provider='iam'
 )

Hey @FaridNeshat-TomTom ,
Thank you for reaching out regarding IAM authentication. My team and I are currently working to add support for this functionality. We plan to support IAM authentication via AWS profile or directly passing IAM credentials to the redshift_connector.connect(...) method.
Please see here for information on how our JDBC and ODBC drivers support IAM authentication. We plan to do something similar for redshift_connector.
This would allow you to authenticate using environment variable like:
import os
import redshift_connector

conn = redshift_connector.connect(
  ...
  access_key_id=os.environ.get('my_access_key_id'),
  secret_access_key=os.environ.get('my_secret_access_key'),
  session_token=os.environ.get('my_session_token') # can be included optionally
)

Would this satisfy your use case?

Yes, that'd be great. I assume if they are not provided, boto3 default logic for acquiring the credentials will kick in(from environment, or ~/.aws/credentials or IAM roles: https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html#guide-credentials), which would make it as seamless as using boto3 or AWS CLI.

Yes, that'd be great. I assume if they are not provided, boto3 default logic for acquiring the credentials will kick in(from environment, or ~/.aws/credentials or IAM roles: https://boto3.amazonaws.com/v1/documentation/api/latest/guide/credentials.html#guide-credentials), which would make it as seamless as using boto3 or AWS CLI.

Hey @FaridNeshat-TomTom ,
Thanks for your patience, we've added support for this in our latest release, v2.0.873.
Yes, if credentials are not provided the default boto3 logic kicks in. A region must be provided either in AWS config file (which will be picked up by boto3) or be passed as an argument to redshift_connector.connect(...)

Hey @FaridNeshat-TomTom ,
Thanks for your patience, we've added support for this in our latest release, v2.0.873.
Yes, if credentials are not provided the default boto3 logic kicks in. A region must be provided either in AWS config file (which will be picked up by boto3) or be passed as an argument to redshift_connector.connect(...)

Hi @Brooke-white
Thanks for taking care of this. I guess this can be closed now.
One thing caught my eye looking at the documentation, is that the usage with the IAM credentials is a little bit awkward because user and password has to be passed but their value is ignored and then one has to care db_user has to be passed as well.

Hi @Brooke-white
Thanks for taking care of this. I guess this can be closed now.
One thing caught my eye looking at the documentation, is that the usage with the IAM credentials is a little bit awkward because user and password has to be passed but their value is ignored and then one has to care db_user has to be passed as well.

Thank you for the feedback -- I'l pass it along to my team and see what we can do there :)

Thank you for the feedback -- I'l pass it along to my team and see what we can do there :)

Yes, if credentials are not provided the default boto3 logic kicks in. A region must be provided either in AWS config file (which will be picked up by boto3) or be passed as an argument to redshift_connector.connect(...)

@Brooke-white this doesn't seem to be the case with 2.0.900 - I have to explicitly pass access_key_id, secret_access_key and session_token - boto doesn't pick them up from the environment:
>>> conn = redshift_connector.connect(
...     iam=True,
...     database='xxx',
...     db_user='xxx',
...     cluster_identifier='myredshift',
...     region="us-west-2",
...  )
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/tmp/venv/lib/python3.8/site-packages/redshift_connector/__init__.py", line 327, in connect
    IamHelper.set_iam_properties(info)
  File "/tmp/venv/lib/python3.8/site-packages/redshift_connector/iam_helper.py", line 123, in set_iam_properties
    raise InterfaceError(
redshift_connector.error.InterfaceError: Invalid connection property setting. Credentials provider, AWS credentials, Redshift auth profile or AWS profile must be provided when IAM is enabled

@rectalogic -- thank you for the heads up, this will be resolved in our next release.


Add support for 4d.rtvslo.si archive

I have:

[x] I've verified and I assure that I'm running youtube-dl 2018.02.11
[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Site support request (request for adding support for a new site)

example URLs:

Single video: http://4d.rtvslo.si/arhiv/arsov-art-atelje/174514670
Single video: http://4d.rtvslo.si/arhiv/olimpijske-igre-2018-pyeongchang-oi2018/174519820
Single video: http://4d.rtvslo.si/arhiv/1968/174519493
Singel video: http://4d.rtvslo.si/arhiv/study-abroad/174518718

Description of your issue, suggested solution and other information
Please add support for the archive of shows on slovenian national radio-television's online portal. They provide actual archive video clips from TV but also radio programs which also take form of a video - audio with a still image.

I've done some reverse-engineering and it looks like it's standard HLS with some trivial DRM scheme slapped on top.
Here are my notes, which should be enough to implement this: https://gist.github.com/franga2000/688d6062b3006c3703d0bfb2d7dd626d#file-rtv_4d_download_spec-md
I can't spare the time at the moment, but am happy to implement it once I do (unless someone beats me to it).
If anyone comes across this more than a month from now and I haven't made a PR yet, please ping me because I probably just forgot :sweat_smile:.
Any pointers from the maintainers in terms of the convention for handling M3U8 URLs are also appreciated. I imagine there's some shared function every HLS-based extractor calls since it's so common?


fix: set db, collection and network tags only once for stream requests

The db, collection and network tags were re-calculated for every document in the result of a read request unnecessarily. This PR fixes that. Yesterday's fix also broke the db and collection name reporting for reads, fixed that as well.

Wonder how we could best test these


Added capability to remove existing conflicting module versions to PSGalleryModule

Resolves #107
Added a 'Clean' switch to PSGalleryModule. When specified via parameters:
@{
PSDependOptions = @{
Target = 'C:\temp'
}
Pester = @{
    DependencyType = 'PSGalleryModule'
    Name = 'Pester'
    Parameters = @{ Clean = $true }
    Version = '4.8.0'
    AddToPath = 'C:\temp'
}

}
the script will clean out any existing versions of the same module, located within any of the paths defined in $env:PSModulePath. Had to refactor a good amount of the code to accommodate this feature.

bump


ngx-admin using Microsoft visual studio 2017

I am trying to build and launch the application using Microsoft Visual Studio 2017. I am able to download all the dependencies and build the code successfully. However once the application is launched in the default browser( Chrome), only the loader is getting displayed and its failing to navigate to the dashboard.
Please help me to resolve this issue.
I've made the index.html inside the /src folder as the 'Set as start page' under the solution explorer.

Please share the commands to start the application after loading the application in visual studio 2017. Is it the right method to run the npm commands to launch the application?

If you cannot load at all, and you keep being stuck on the loader, you should have an error in the console.
What is it ?

@Tenmak There is no error in the browser console. In fact its loading only the index.html file. No other files are loaded in the source tab.

I installed the latest angular-cli project and copied the akveo/ngx/admin project files to the workspace. I am able to run the application with IIS express after building the application with ng-build command. I am closing this as my issue is resolved. Thanks All.

Anish, how did you integrate with .net core?

I managed to integrate ngx-admin into asp.net core mvc project.
https://github.com/ttma1046/asp.net-core-ngx-admin


Create first public version for autocomplete client

Makes autocomplete a public package and provides its first version

bors merge


Is this project active

Hey @azach :) Nice project. Are you actively developing this? Can you share the status of this? Thanks!!

Thanks for saying so! There are no features I'm actively working on releasing but definitely happy to take pull requests.


Refactor 'find' command to search for keywords in Transaction's description and remark fields

Resolves #23


Fix strain device in ASE calculator

Fixes a small bug: the device wasn't chosen properly for the strain in the ASE calculator. The strain was also called "scaling", I've renamed it to strain for consistency within our codes
Contributor (creator of pull-request) checklist

[ ] Tests updated (for new features and bugfixes)?
[ ] Documentation updated (for new features)?
[ ] Issue referenced (for PRs that solve an issue)?

Reviewer checklist

[ ] CHANGELOG updated with public API or any other important changes?

📚 Download documentation preview for this pull-request

Happy to merge once the linter is fixed!


Add ability to decode any network type wanted

Fixes #19 by passing a second arg to decode with { bech32: 'sb' }

This feature is compatible with the BitcoinJS Network format. Since network objects' bech32 headers are placed under the bech32 attribute.


How to build UI and web components using Maverick.js? Are there any documentation available?

Unfortunately not right at this time @mdsohelmia. I plan on doing it when after our player 1.0 so I know Maverick is stable. What were you hoping to use the library for?

@mihar-22  Thanks for your reply.
We are developing an improved player UI for the Shaka player.


Math expr param tag

Changes

update math expression schema
use asdf default pattern matching for tag validation
deprecate old pattern matching code

Related Issues
Closes #273
Checks

[x] updated CHANGELOG.md

"deprecating" an asdf validation function triggers a warning which is thrown as an exception for the asdf schema tests


Updates dependencies

I haven't had too much time to look into the breaking issues for the next major version of these packages. I can have a look at it next week if needed.

Please do. I'll process this PR as-is, but let's see if we can move to the latest versions to stay up to date.

Merged manually 🚀


refactor(webpack.config): restrict cssnano to only safe minification

see issue #38 @andrewjensen

+1


Assertion when concurrently using multiple LockedConnection

When using a MySQLPool locked connection concurrently using Vibed HTTP server (using the following code), I randomly end up with an assertion in mysql-native/source/mysql/protocol/sockets.d:
Code:
import vibe.vibe;
import mysql;

MySQLPool connPool;

void main()
{
	connPool = new MySQLPool("host=localhost;port=3306;user=yourname;pwd=pass123;db=mysqln_testdb");

	auto settings = new HTTPServerSettings;
	settings.port = 8080;
	settings.bindAddresses = ["::1", "<IP_ADDRESS>"];

	auto router = new URLRouter;
	router.registerWebInterface(new WebInterface);

	listenHTTP(settings, router);

	logInfo("Please open http://<IP_ADDRESS>:8080/ in your browser.");
	runApplication();
}

class WebInterface {

	void index(HTTPServerResponse res)
	{
		auto conn = connPool.lockConnection();

		auto queryRes = conn.query("SELECT SLEEP(1)");
		queryRes.close();

		res.writeJsonBody("Success !");
	}
}

Full repo ready to compile: test-connpool.tar.gz
Result:
When stressed using simply curl <IP_ADDRESS>:8080 &; curl <IP_ADDRESS>:8080 & few times, it produces the following assertion:
core.exception.AssertError@../../.dub/packages/mysql-native-2.2.0/mysql-native/source/mysql/protocol/sockets.d(121): Assertion failure
----------------
??:? _d_assertp [0xd482e4bd]
??:? const void mysql.protocol.sockets.MySQLSocketVibeD.__invariant7() [0xd4601fc9]
??:? const void mysql.protocol.sockets.MySQLSocketVibeD.__invariant() [0xd4602180]
??:? const @property bool mysql.protocol.sockets.MySQLSocketVibeD.connected() [0xd4602010]
??:? void mysql.connection.Connection.kill() [0xd45f8f16]
??:? bool mysql.protocol.comms.execQueryImpl(mysql.connection.Connection, mysql.protocol.comms.ExecQueryImplInfo, out ulong) [0xd45fcd75]
??:? mysql.result.ResultRange mysql.commands.queryImpl(mysql.commands.ColumnSpecialization[], mysql.connection.Connection, mysql.protocol.comms.ExecQueryImplInfo) [0xd45f81da]
??:? mysql.result.ResultRange mysql.commands.query(mysql.connection.Connection, const(char[]), mysql.commands.ColumnSpecialization[]) [0xd45f815d]
??:? void app.WebInterface.index(vibe.http.server.HTTPServerResponse) [0xd45dd202]
... continues over vibed http stack

I honestly don't know why this happens, wether if it's

bad mysql-native usage
related to vibed 0.8.3
related to dmd v2.079.0

Don't call queryRes.close();

I tried removing it, but it didn't solve the issue.
I noticed noticed that the assert always occurs when launching the double curl command the second time. Something must go wrong when destroying/cleaning LockedConnections that have been used concurrently.

First, thanks for the excellent test case. That's a huge help.
Your code looks correct to me, so I did a little digging. So far, it looks like there's two parts to the problem here:
The immediate failure, the AssertError your getting, is from an invariant contract check in mysql-native. But the check itself (assert(!!socket)) seems to be going wrong somehow. I think it was intended to ensure the socket isn't null, but...well, something seems to be very weird there, as if it opened a portal to Alice's Wonderland or something...Still digging on that.
But, that AssertError is only a secondary failure. It's just an additional problem that's triggered while the stack is already unwinding from a different failure. If I remove that assert, the original problem is shown:
core.exception.AssertError@../../../.dub/packages/eventcore-0.8.29/eventcore/source/eventcore/drivers/posix/driver.d(243): Overwriting notification callback.
----------------
??:? _d_assert_msg [0x4cbb24ba]
??:? nothrow @nogc @safe void eventcore.drivers.posix.driver.PosixEventLoop.setNotifyCallback!(0).setNotifyCallback(eventcore.driver.Handle!("fd", ulong, -1uL).Handle, void delegate(eventcore.driver.Handle!("fd", ulong, -1uL).Handle) nothrow @safe) [0x4cb85b15]
??:? _D9eventcore7drivers5posix7sockets__T23PosixEventDriverSocketsHTCQClQCeQBz5epoll14EpollEventLoopZQCi4readMFNbNfSQEg6driver__T6HandleVAyaa12_73747265616d536f636b6574TSQGiQCc__TQByVQBua6_736f636b6574TSQHpQDj__TQDfVQDba2_6664TmVmN1ZQEaVQBjS1N1ZQEmVQDcS1S1N1ZQFaAhEQJzQFt6IOModeDFNbNfQGnEQKwQGq8IOStatusmZvZv [0x4cb73e01]
??:? _D4vibe4core3net13TCPConnection11waitForDataMFNfSQBq4time8DurationZ__T9__lambda2TDFNbNfS9eventcore6driver__T6HandleVAyaa12_73747265616d536f636b6574TSQCjQCc__TQByVQBua6_736f636b6574TSQDqQDj__TQDfVQDba2_6664TmVmN1ZQEaVQBjS1N1ZQEmVQDcS1S1N1ZQFaEQFyQFr8IOStatusmZvZQHjMFNbNfQHhZv [0x4cb679ae]
??:? _D4vibe8internal5async__T13asyncAwaitAnyVbi1SQBrQBpQBj__T8WaitableTDFNbNfS9eventcore6driver__T6HandleVAyaa12_73747265616d536f636b6574TSQCjQCc__TQByVQBua6_736f636b6574TSQDqQDj__TQDfVQDba2_6664TmVmN1ZQEaVQBjS1N1ZQEmVQDcS1S1N1ZQFaEQFyQFr8IOStatusmZvSQJl4core3net13TCPConnection11waitForDataMFNfSQBq4time8DurationZ9__lambda2SQMhQCwQCuQCtQChMFNfQBxZ9__lambda3SQNpQEeQEcQEbQDpMFNfQDfZ9__lambda4ZZQObMFNfQLjZv [0x4cb3913d]
??:? _D4vibe8internal5async__T13asyncAwaitAnyVbi1SQBrQBpQBj__T8WaitableTDFNbNfS9eventcore6driver__T6HandleVAyaa12_73747265616d536f636b6574TSQCjQCc__TQByVQBua6_736f636b6574TSQDqQDj__TQDfVQDba2_6664TmVmN1ZQEaVQBjS1N1ZQEmVQDcS1S1N1ZQFaEQFyQFr8IOStatusmZvSQJl4core3net13TCPConnection11waitForDataMFNfSQBq4time8DurationZ9__lambda2SQMhQCwQCuQCtQChMFNfQBxZ9__lambda3SQNpQEeQEcQEbQDpMFNfQDfZ9__lambda4ZZQObMFNfQEcQLmZv [0x4cb38fbd]
??:? @safe bool vibe.core.net.TCPConnection.waitForData(core.time.Duration) [0x4cb3804d]
??:? @safe bool vibe.core.net.TCPConnection.read(scope ubyte[], eventcore.driver.IOMode).__lambda3!(core.time.Duration).__lambda3(core.time.Duration) [0x4cb397b9]
??:? @safe void vibe.core.net.loopWithTimeout!(vibe.core.net.TCPConnection.read(scope ubyte[], eventcore.driver.IOMode).__lambda3, Exception).loopWithTimeout(core.time.Duration) [0x4cb3965e]
??:? @safe ulong vibe.core.net.TCPConnection.read(scope ubyte[], eventcore.driver.IOMode) [0x4cb3825a]
??:? @safe void vibe.core.net.TCPConnection.read(scope ubyte[]) [0x4cb38298]
??:? void mysql.protocol.sockets.MySQLSocketVibeD.read(ubyte[]) [0x4c985228]
??:? ubyte[] mysql.protocol.comms.getPacket(mysql.connection.Connection) [0x4c98013e]
??:? bool mysql.protocol.comms.execQueryImpl(mysql.connection.Connection, mysql.protocol.comms.ExecQueryImplInfo, out ulong) [0x4c97fdaa]
??:? mysql.result.ResultRange mysql.commands.queryImpl(mysql.commands.ColumnSpecialization[], mysql.connection.Connection, mysql.protocol.comms.ExecQueryImplInfo) [0x4c97b46a]
??:? mysql.result.ResultRange mysql.commands.query(mysql.connection.Connection, const(char[]), mysql.commands.ColumnSpecialization[]) [0x4c97b3ed]
??:? void app.WebInterface.index(vibe.http.server.HTTPServerResponse) [0x4c960492]
??:? void vibe.web.web.handleRequest!("index", app.WebInterface.index(vibe.http.server.HTTPServerResponse), app.WebInterface).handleRequest(vibe.http.server.HTTPServerRequest, vibe.http.server.HTTPServerResponse, app.WebInterface, vibe.web.web.WebInterfaceSettings) [0x4c96b111]
??:? @trusted void vibe.web.web.registerWebInterface!(app.WebInterface, 5).registerWebInterface(vibe.http.router.URLRouter, app.WebInterface, vibe.web.web.WebInterfaceSettings).__lambda4(vibe.http.server.HTTPServerRequest, vibe.http.server.HTTPServerResponse) [0x4c96a608]
??:? @safe bool vibe.http.router.URLRouter.handleRequest(vibe.http.server.HTTPServerRequest, vibe.http.server.HTTPServerResponse).__lambda4!(ulong, immutable(char)[][]).__lambda4(ulong, scope immutable(char)[][]) [0x4ca4a4a7]
??:? const @safe bool vibe.http.router.MatchTree!(vibe.http.router.Route).MatchTree.doMatch(immutable(char)[], scope bool delegate(ulong, scope immutable(char)[][]) @safe) [0x4ca4cbd5]
??:? @safe bool vibe.http.router.MatchTree!(vibe.http.router.Route).MatchTree.match(immutable(char)[], scope bool delegate(ulong, scope immutable(char)[][]) @safe) [0x4ca4c4d7]
??:? @safe void vibe.http.router.URLRouter.handleRequest(vibe.http.server.HTTPServerRequest, vibe.http.server.HTTPServerResponse) [0x4ca4a168]
??:? @safe bool vibe.http.server.handleRequest(vibe.internal.interfaceproxy.InterfaceProxy!(vibe.core.stream.Stream).InterfaceProxy, vibe.core.net.TCPConnection, vibe.http.server.HTTPServerContext, ref vibe.http.server.HTTPServerSettings, ref bool, scope stdx.allocator.IAllocator) [0x4cad024d]
??:? @trusted void vibe.http.server.handleHTTPConnection(vibe.core.net.TCPConnection, vibe.http.server.HTTPServerContext).__lambda3() [0x4cace7d0]
??:? @safe void vibe.http.server.handleHTTPConnection(vibe.core.net.TCPConnection, vibe.http.server.HTTPServerContext) [0x4cace57b]
??:? nothrow @safe void vibe.http.server.listenHTTPPlain(vibe.http.server.HTTPServerSettings, void delegate(vibe.http.server.HTTPServerRequest, vibe.http.server.HTTPServerResponse) @safe).doListen(vibe.http.server.HTTPServerContext, bool, bool).__lambda4(vibe.core.net.TCPConnection) [0x4ca56771]
??:? void vibe.core.task.TaskFuncInfo.set!(void delegate(vibe.core.net.TCPConnection) @safe, vibe.core.net.TCPConnection).set(ref void delegate(vibe.core.net.TCPConnection) @safe, ref vibe.core.net.TCPConnection).callDelegate(ref vibe.core.task.TaskFuncInfo) [0x4cb69a64]
??:? void vibe.core.task.TaskFuncInfo.call() [0x4cb4b3d9]
??:? nothrow void vibe.core.task.TaskFiber.run() [0x4cb4a9e1]
??:? void core.thread.Fiber.run() [0x4cc041c3]
??:? fiber_entryPoint [0x4cc04092]
??:? [0xffffffff]
Program exited with code -6

Appears to be something going wrong in vibe-d/eventcore (maybe due to something mysql-native is doing?). I will file a ticket there and hopefully we can get this resolved.

Interesting. On vibe.d v0.8.2, this results in neither mysql/protocol/sockets.d(121): Assertion failure nor eventcore/drivers/posix/driver.d(243): Overwriting notification callback. Instead, it just results in the old spectre: vibe/core/drivers/libevent2_tcp.d(414): Acquiring reader of already owned connection:
core.exception.AssertError@../../../.dub/packages/vibe-d-0.8.2/vibe-d/core/vibe/core/drivers/libevent2_tcp.d(414): Acquiring reader of already owned connection.
----------------
??:? _d_assert_msg [0x94e47c62]
??:? @safe void vibe.core.drivers.libevent2_tcp.Libevent2TCPConnection.checkReader() [0x94dc60e7]
??:? @safe void vibe.core.drivers.libevent2_tcp.Libevent2TCPConnection.acquireReader() [0x94dc6104]
??:? @safe ulong vibe.core.drivers.libevent2_tcp.Libevent2TCPConnection.read(scope ubyte[], vibe.core.stream.IOMode) [0x94dc5632]
??:? @safe void vibe.core.stream.InputStream.read(scope ubyte[]) [0x94de26ea]
??:? void mysql.protocol.sockets.MySQLSocketVibeD.read(ubyte[]) [0x94c42735]
??:? ubyte[] mysql.protocol.comms.getPacket(mysql.connection.Connection) [0x94c3d6fe]
??:? bool mysql.protocol.comms.execQueryImpl(mysql.connection.Connection, mysql.protocol.comms.ExecQueryImplInfo, out ulong) [0x94c3d36c]
??:? mysql.result.ResultRange mysql.commands.queryImpl(mysql.commands.ColumnSpecialization[], mysql.connection.Connection, mysql.protocol.comms.ExecQueryImplInfo) [0x94c3862c]
??:? mysql.result.ResultRange mysql.commands.query(mysql.connection.Connection, const(char[]), mysql.commands.ColumnSpecialization[]) [0x94c385b3]
??:? void app.WebInterface.index(vibe.http.server.HTTPServerResponse) [0x94c20642]
??:? void vibe.web.web.handleRequest!("index", app.WebInterface.index(vibe.http.server.HTTPServerResponse), app.WebInterface).handleRequest(vibe.http.server.HTTPServerRequest, vibe.http.server.HTTPServerResponse, app.WebInterface, vibe.web.web.WebInterfaceSettings) [0x94c2aabb]
??:? @trusted void vibe.web.web.registerWebInterface!(app.WebInterface, 5).registerWebInterface(vibe.http.router.URLRouter, app.WebInterface, vibe.web.web.WebInterfaceSettings).__lambda4(vibe.http.server.HTTPServerRequest, vibe.http.server.HTTPServerResponse) [0x94c29d38]
??:? @safe bool vibe.http.router.URLRouter.handleRequest(vibe.http.server.HTTPServerRequest, vibe.http.server.HTTPServerResponse).__lambda4!(ulong, immutable(char)[][]).__lambda4(ulong, scope immutable(char)[][]) [0x94d17fab]
??:? const @safe bool vibe.http.router.MatchTree!(vibe.http.router.Route).MatchTree.doMatch(immutable(char)[], scope bool delegate(ulong, scope immutable(char)[][]) @safe) [0x94d18a82]
??:? @safe bool vibe.http.router.MatchTree!(vibe.http.router.Route).MatchTree.match(immutable(char)[], scope bool delegate(ulong, scope immutable(char)[][]) @safe) [0x94d18367]
??:? @safe void vibe.http.router.URLRouter.handleRequest(vibe.http.server.HTTPServerRequest, vibe.http.server.HTTPServerResponse) [0x94d17c6d]
??:? @safe bool vibe.http.server.handleRequest(vibe.core.stream.Stream, vibe.core.net.TCPConnection, vibe.http.server.HTTPServerContext, ref vibe.http.server.HTTPServerSettings, ref bool, scope std.experimental.allocator.IAllocator) [0x94d5f33c]
??:? @trusted void vibe.http.server.handleHTTPConnection(vibe.core.net.TCPConnection, vibe.http.server.HTTPServerContext).__lambda3() [0x94d5dc58]
??:? @safe void vibe.http.server.handleHTTPConnection(vibe.core.net.TCPConnection, vibe.http.server.HTTPServerContext) [0x94d5daf9]
??:? nothrow @safe void vibe.http.server.listenHTTPPlain(vibe.http.server.HTTPServerSettings, void delegate(vibe.http.server.HTTPServerRequest, vibe.http.server.HTTPServerResponse) @safe).doListen(vibe.http.server.HTTPServerContext, bool, bool).__lambda4(vibe.core.net.TCPConnection) [0x94d1e83c]
??:? void vibe.core.drivers.libevent2_tcp.ClientTask.execute() [0x94e11feb]
??:? void vibe.core.core.makeTaskFuncInfo!(void delegate()).makeTaskFuncInfo(ref void delegate()).callDelegate(vibe.core.core.TaskFuncInfo*) [0x94dba2af]
??:? void vibe.core.core.CoreTask.run() [0x94db6b3e]
??:? void core.thread.Fiber.run() [0x94e8d97f]
??:? fiber_entryPoint [0x94e8d6d2]
??:? [0xffffffff]
Program exited with code 1

By adding this to the test case's WebInterface.index function:
import std.stdio;
writeln("*cast(void**)&conn: ", *cast(void**)&conn);

I can see that ConnectionPool is handing out the same connection to two different tasks before the first task has completed.

Both, the old "aquiring reader" and the new "overwriting notification callback" assertions, have the same cause - reading or writing concurrently on the same connection. I had a look at the source and I think the bug lies here: https://github.com/mysql-d/mysql-native/blob/249c122d641ad9e01e8f663009a31b79d6d1132b/source/mysql/pool.d#L174
Due to the (awful) implicit casting that is possibly through the alias this in LockedConnection!T, it is possible to silently extract the underlying connection object. Changing the variable declaration to LockedConnection!Connection or auto should fix the issue.

Maybe LockedConnection should simply use opDot instead of alias this for now. With DIP1000 it could annotate the __conn getter as scope.

Thanks a ton! That does indeed fix it! A stupid mistake in mysql-native and clearly I was just spinning in circles with it (and my code to output the address of the Connection object must've been wrong too.)
Expect a fix and new release after I get some sleep, fading fast here...
(BTW, one unfortunate problem I've found with opDot in the past is that it conflicts pretty badly with...uhh, one other major D feature...I think it might've been UFCS, IIRC).

Speaking of this, mysql-native may need updated to optionally support LockedConnection!Connection throughout. Currently, it just assumes a connection object is always Connection, which clearly isn't the case when using the connection pool. One little problem though is how to handle ResultRange/Row: Currently, they're the only remaining part of mysql-native that still holds a reference to a connection. Not real clear what I can do to eliminate that while still being able to detect a ResultRange being invalidated though, and I wouldn't want stored references to a ResultsRange to prevent connections from being reclaimed back to the pool.

Putting together a fix, regression test, and new release right now.
Summary:
Ultimately, MySQLPool.lockConnection was returning a connection that was already in use.
How it happened:
After a change made for v2.1.0, MySQLPool.lockConnection was accidentally returning a Connection instead of a LockedConnection!Connection. This meant the LockedConnection went out-of-scope and returned the connection to the pool as soon as MySQLPool.lockConnection returned. So the Connection returned was no longer locked and got handed out again to the next fiber which requested it, even if the first fiber was still using it.

Also, the other part of this issue is that mysql-native's socket wrappers had an invariant check that was incompatible with vibe-core (as opposed to vibe-d:core), used by vibe v0.8.3.


Add support to new flag ignoreDeprecationWarning from esri-leaflet > v3.0.2

Added a deprecation warning when using L.esri.BasemapLayer (info).
This warning can be disabled by setting the ignoreDeprecationWarning option to true. (https://github.com/Esri/esri-leaflet/pull/1293).
I think it would be interesting to forward that flag on react-esri-leaflet.

I haven't had a chance to see what's new in the new patch of esri-leaflet or esri-leaflet-geocoder, or how its going to affect this wrapper.  I'll take a look when I get a chance.

Thank you @slutske22

This is implemented in version 2, which is currently in a @next version.  You can try it out here: https://www.npmjs.com/package/react-esri-leaflet/v/2.0.0.  Will publish as official version soon.

Sorry for the dumb question, but how do I use this option? I'm using react-esri-leaflet version 2.0.1.
Inside a MapContainer my code instantiates a BasemapLayer as follows
<BasemapLayer key={mapType} name={mapType}  />`.

Sorry for the dumb question, but how do I use this option? I'm using react-esri-leaflet version 2.0.1.
Inside a MapContainer my code instantiates a BasemapLayer as follows
<BasemapLayer key={mapType} name={mapType}  />

That code should work fine...is there an issue?  It should just give you fancy intellisense for the fact that the underlying L.esri.basemapLayer is deprecated.

Sorry, I did a poor job of explaining my question.
How do I enable the ignoreDeprecationWarning option that is in esri-leaflet? Is it a prop for BasemapLayer? If so, I can't get it to work.

Sorry, that was the piece I was missing.
This is my lack of familiarity with React... I had the mistaken impression that props were always key/value pairs. I tried ignoreDeprecationWarning={true} and many other variations thereof to no avail.
Thanks so much for your help.


MAINT: Add ds001771 to the smoke-tests battery

Revise the organization of the CircleCI config to leverage the new flag --fs-subjects-dir.

Alright, this is working (as in, the new smoke test is up and running).
I'm going to merge this, and therefore break master to put some load on @josephmje (#90) and @dPys (#82). Please let me know if you need any help guys.

Revise the organization of the CircleCI config to leverage the new flag --fs-subjects-dir.

I don't see the --fs-subjects-dir flag in the CLI


Update gateway after service already started

Closing https://github.com/spacemeshos/poet/issues/84.
Changes
Introducing new RPC method: UpdateGateway, which has a similar request message as Start, but can be used after the service already started.
Open issue
Same like Start, this new RPC method is admin-only. We didn't introduce authentication to Start because it wasn't critical enough, since it was supposed to be called quickly and adversarial consecutive calls would fail anyway. But with UpdateGateway it isn't the case, so we need to protect it.
Simplest option would be to add a configurable password to the server (with a default value which need to be changed on production), and add a password field to the admin-only requests to match it (this will also require to enable TLS for the gRPC connection).
Any thoughts? @noamnelke @y0sher

cc: @ilans ☝
Please confirm that I'm not talking nonsense and that this would be easy to configure.

We'll want to have the production server sitting behind a gateway anyway, so I tend to agree with you.
@ilans please advise.

I think you should just merge and we'll figure it out later


add cook_all function

if we have a lot of ducks, we must cook them one by one, add a cook_all function to cook them all at one time.

Heyyo @Root-lee,
This is a fine addition and something I wanted to do for some time.
But do you think we could re-use the cook() function so theres no code duplication?
Maybe something like:
    while (#M.ducks_list > 0) do
        M.cook()
    end

Epic change! Thanks for the PR ❤


Fixed #19538 -- Removed window.admin_media_prefix from admin templates.

https://code.djangoproject.com/ticket/19538

Looks good in Chrome and IE8.


IConfigurationListener* methods are invoked several time per configuration method

IConfigurationListener/IConfigurationListener2 methods are called several times per configuration method invocation if the class also implements ISuiteListener or IInvokedMethodListener AND there is more than one  entry in the suite AND the listener is attached via @Listeners annotation (as opposed to  tag in XML).
public class MyListener implements IConfigurationListener2, ISuiteListener {
    @Override public void onConfigurationFailure(ITestResult paramITestResult) {}
    @Override public void onConfigurationSkip(ITestResult paramITestResult) {}
    @Override public void onConfigurationSuccess(ITestResult paramITestResult) {
        System.out.println("onConfigurationSuccess called");
    }
    @Override public void beforeConfiguration(ITestResult paramITestResult) {
        System.out.println("beforeConfiguration called");
    }
    @Override public void onStart(ISuite paramISuite) {}
    @Override public void onFinish(ISuite paramISuite) {}
}

@Listeners(MyListener.class)
public class MyTest {
    @BeforeMethod
    public void before() {
        System.out.println("in before method");
    }

    @Test
    public void test() {

    }
}

<suite name="Test Suite" parallel="false">
    <test name="Test1">
        <classes>
            <class name="MyTest">
            </class>
        </classes>
    </test>

    <test name="Test2">
        <classes>
            <class name="MyTest">
            </class>
        </classes>
    </test>

    <test name="Test3">
        <classes>
            <class name="MyTest">
            </class>
        </classes>
    </test>
</suite>

Running this suite produces the following output:
beforeConfiguration called
in before method
onConfigurationSuccess called
beforeConfiguration called
beforeConfiguration called
in before method
onConfigurationSuccess called
onConfigurationSuccess called
beforeConfiguration called
beforeConfiguration called
beforeConfiguration called
in before method
onConfigurationSuccess called
onConfigurationSuccess called
onConfigurationSuccess called
i.e. the number of repeated calls is increased with each new  entry. Same behaviour is observed if ISuiteListener is replaced with IInvokedMethodListener in MyListener class.
If @Listeners annotation is removed and the  tag is added, everything works as expected. For some reason that I did not bother investigating this issue is not reproduced when the suite is executed from Eclipse (even though I do have "Use project TestNG.jar" checkbox checked). Might be due to the fact that Eclipse plugin uses RemoteTestNG and not plain TestNG.
Seeing this issue in testng-6.9.10. Might be related to https://github.com/cbeust/testng/issues/940 and https://github.com/cbeust/testng/issues/339.

Attempted at recreating it using TestNG 6.12. Cannot reproduce the problem
Below is the samples that I used
Test class
import org.testng.annotations.BeforeMethod;
import org.testng.annotations.Listeners;
import org.testng.annotations.Test;

@Listeners(Issue968MyListener.class)
public class Issue968MyTest {
    @BeforeMethod
    public void before() {
        System.out.println("Issue968MyTest.before()");
    }

    @Test
    public void test() {
        System.out.println("Issue968MyTest.test()");
    }
}

Listener used
import org.testng.IConfigurationListener2;
import org.testng.ISuite;
import org.testng.ISuiteListener;
import org.testng.ITestResult;

import java.util.ArrayList;
import java.util.List;

public class Issue968MyListener implements IConfigurationListener2, ISuiteListener {
    public static List<String> messages = new ArrayList<>();
    @Override
    public void onConfigurationFailure(ITestResult paramITestResult) {
    }

    @Override
    public void onConfigurationSkip(ITestResult paramITestResult) {
    }

    @Override
    public void onConfigurationSuccess(ITestResult paramITestResult) {
        messages.add("onConfigurationSuccess():<" + paramITestResult.getTestContext().getName() + ">");
    }

    @Override
    public void beforeConfiguration(ITestResult paramITestResult) {
        messages.add("beforeConfiguration():<" + paramITestResult.getTestContext().getName() + ">");
    }

    @Override
    public void onStart(ISuite paramISuite) {
    }

    @Override
    public void onFinish(ISuite paramISuite) {
    }
}

Test method that tests this issue
import org.assertj.core.api.Assertions;
import org.testng.TestNG;
import org.testng.annotations.Test;
import org.testng.xml.XmlClass;
import org.testng.xml.XmlSuite;
import org.testng.xml.XmlTest;

import java.util.ArrayList;
import java.util.Arrays;
import java.util.Collections;
import java.util.List;

public class Issue968TestRunner {
    @Test
    public void testMethod() {
        TestNG testng = new TestNG();
        XmlSuite xmlSuite = new XmlSuite();
        xmlSuite.setName("suite");
        xmlSuite.setTests(Arrays.asList(
                createXmlTest(xmlSuite, "test1"),
                createXmlTest(xmlSuite, "test2"),
                createXmlTest(xmlSuite, "test3")
        ));
        testng.setXmlSuites(Collections.singletonList(xmlSuite));
        testng.run();
        System.err.println(Issue968MyListener.messages);
        List<String> expected = new ArrayList<>();
        String[] events = new String[] {"beforeConfiguration()", "onConfigurationSuccess()"};
        String[] tests = new String[] {"<test1>", "<test2>", "<test3>"};
        for (String event : events) {
            for (String test: tests) {
                String msg = event + ":" + test;
                expected.add(msg);
            }
        }
        Assertions.assertThat(Issue968MyListener.messages).containsExactlyInAnyOrder(expected.toArray(new String[expected.size()]));

    }

    private static XmlTest createXmlTest(XmlSuite suite, String name) {
        XmlTest xmlTest = new XmlTest(suite);
        xmlTest.setName(name);
        xmlTest.setClasses(Collections.singletonList(new XmlClass(Issue968MyTest.class)));
        return xmlTest;
    }
}


ROTATION OF POINTS

Hello, i was looking in older issues because i´m upgrading Openseadragon.  I upgraded anyways the part of the WSI, navigator and overlays rotation. All works fine, but i have overlays that are simple points on the viewer and don´t rotate. Squares, ellipsis works fine. I ask if i should works for points because reading older issues i found that there is that problem.
Let me know for trying to solve it.

I upgraded anyways the part of the WSI, navigator and overlays rotation.

What is WSI?
Could you make a small example reproducing the bug?
Is it related to #729 and #791 ?

WSI may stand for Whole Slide Imaging (in microscopy).
See this example:
http://www.lekarski.katowice.pl/preparat.php?szkielko_guid=EA8AB491C67B479280E6C20E421619D0
vs
http://www.lekarski.katowice.pl/rotate.php?szkielko_guid=EA8AB491C67B479280E6C20E421619D0
I don't use rotation (yet) but I'd expect to have everything rotated.
Current result is: point annotations move as there is no rotation at all (at 90 deg they move vertically when slide panned horizontally)
non-point annotations follow their location, they are properly anchored, although the shape is not rotated. (more or less like this?)

Thanks for the clarification and the example.
@selko Is that the bug you were experiencing?
Hopefully, this shouldn't be too hard to fix with the latest work on rotation.
Is either one of you willing to look at it?

@avandecreme I really doubt I can deal with the issue, my skills seem insufficient here : (
On the other hand - https://github.com/openseadragon/openseadragon/issues/791 was opened to make clear whether it will be expected behavior. In my case it's pretty obvious that It should, but I can imagine that other may expect to stay where they put them no matter the rotation is.

Like @boskar example, i have these dots and rectangles or circular areas. With areas works really fine. But the dots remains still when i rotate

I make the rotate implementation reading these issues starting from #88 , #185 . I have the rotateLeft and rotateRight functions implemented and working, but with that issue that i mentioned. I'm really interested in collaborate in Opensedragon but firstly, i need upgrade many things like these to be with yours and working fine with same versions. Kind regards!

@avandecreme , it's exactly the same bug as @boskar have. Kind regards!

@avandecreme Is this still an issue on master? @dwrogers seems to think it may not be.

I don't know actually but it looks like it is indeed working on @dwrogers codepen.
Great :)

Okay, closing this. Please reopen if it pops up again!

Just to confirm here: it now works properly
http://www.lekarski.katowice.pl/notworking/rotate.php?szkielko_guid=40D0E84BCE094A619BFBC3066BCBABAE
http://www.lekarski.katowice.pl/notworking/rotate90.php?szkielko_guid=40D0E84BCE094A619BFBC3066BCBABAE

Thanks for testing! NO_ROTATE should be what you are looking for. I will update the overlays examples on the web site to show the differents modes.

Now it's working there. Great! I have to take a look into the code. Actually, im with the same problem with rotation of points.

With areas works fine for me.

There is some place where i can find new modifications? Kind regards!

This is the related PR: https://github.com/openseadragon/openseadragon/pull/896/files
To setup a non-rotating overlay you need to do:
    var overlay = {
        id: 'right-arrow-overlay',
        x: 0.2008,
        y: 0.4778,
        placement: 'RIGHT',
        rotationMode: OpenSeadragon.OverlayRotationMode.NO_ROTATION
    };


Force light mode for notebook outputs

If you compare the following screenshots, you will find that the some of the Xarray output is invisible in dark mode.

Xarray light mode
Xarray dark mode

This PR makes a stronger attempt at forcing notebook outputs into light mode by resetting all of the color variables on the notebook output element to light mode.

Switching to draft mode while I work out the merge conflicts

Should there be an upstream issue in xarray as well ? I'm going to guess this also affect Lab users using dark theme doesn't it

No, it doesn't affect JupyterLab users using dark theme.
I think this is because JupyterLab's dark mode CSS is more robust for various widgets than our CSS.
See:

https://github.com/pydata/pydata-sphinx-theme/pull/1757#issuecomment-2057824216
https://github.com/pydata/pydata-sphinx-theme/issues/1740#issuecomment-2043547802

Should there be an upstream issue in xarray

That said, there are some Xarray CSS rules that are not friendly in dark mode. Here's a screenshot from JupyterLab:

The color of the numbers "10 20" and the file icon is way too dark to contrast well with a dark background.


2FA not supported

Describe the bug
My eufy account has 2FA activated. The adapter only provides fields für User and password.
Screenshots & Logfiles
log.log
Versions:

Adapter version: 0.0.1
JS-Controller version: 3.1.6
Node version: 12.18.3
Operating system: linux (Doker)

Hi ubieberich,
2FA is almost implemented. The login is already working as well as trusting ioBroker as "Trusted Device". I'm currently working on the token renewal.
As soon as it is stable enough i will release it.

Hi ubieberich,
2FA is almost implemented. The login is already working as well as trusting ioBroker as "Trusted Device". I'm currently working on the token renewal.
As soon as it is stable enough i will release it.

In the meantime the push notifications aren't working anymore. The push notifications are the only way I have found to renew the token without human intervention.
I'm investigating the issue with @JanLoebel here.

@ubieberich 2FA is supported with version 0.0.2, but it still misses the renewal of the authentication token. This means that when the authentication token expires the verification code will be sent again and it must be entered again in the adapter to continue wo work.

#response_container_BBPPID{font-family: initial; font-size:initial; color: initial;}  Can one get Version 0.02 already?                                                                                Von<EMAIL_ADDRESS>16. November 2020 13:47An<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Re: [bropat/ioBroker.eufy-security] 2FA not supported (#1)
@ubieberich 2FA is supported with version 0.0.2, but it still misses the renewal of the authentication token. This means that when the authentication token expires the verification code will be sent again and it must be entered again in the adapter to continue wo work.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.

@linuxq Version 0.0.2 isn't released. It will be published in the next days.

Version 0.0.2 with 2FA support was published.
Note: After successful authentication the token expires after 1 month and the renewal process is not implemented, so manual intervention is required!

Adapter works fine for me. No problem with the first 2FA login. Great job. Thanks.
Waiting till the token expires. Will then test the manual re-login.


A better README.md

I have made some changes to the readme! I hope you like it.

@shiffman Do you like it??...

Thank you! I definitely want to improve the README to have more info about Logo, the videos, and features related to this project. Now that I have #24 I don't think that I want to do voting at the moment, however. Thank you for thinking of this! ❤


[KYUUBI #5108][Flink] Fix FileNotFoundException during Flink engine bootstrap

Why are the changes needed?
As titled.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

Codecov Report

Merging #5109 (318199f) into master (998b5d5) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #5109   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         564     564
  Lines       31293   31293
  Branches     4095    4095
======================================
  Misses      31293   31293

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

Thanks, merged to master


[Feature] WYSIWYG Mode

Problem
In apps like Typora you can work in WYSIWYG mode
Solution
Introduce WYSIWYG mode

WYSIWYG is a feature I specifically do not want for this app.

Can we have a slightly different thing. The page is fully rendered except for the line/element which the focus is on which would be the underlying Markdown. This is not essentially WYSIWYG but as you move the cursor from element/line to line you see the underlying markdown of the new focus element/line and the rendering of the old focus area.


Use asset's content hash instead of the hash of its file path

Currently in the production build, the hash of an asset is calculated from its file path. If the file's content changed, the generated file name won't change. This will cause the browser to use the old cached file if cache-control: max-age header is set and is not expired.
https://github.com/vitejs/vite/blob/24336f471f4abe2933100ee570fa8e238d1e1658/src/node/build/buildPluginAsset.ts#L59
Besides, remove the ${baseName} part is better for long term caching. If we change the filename but not change the content, the output filename won't change, so the browser can reuse the cache. And if we have assets with different file names but the same content (In a large project, I prefer putting assets into their related components' folder), they will have the same output filename.

I think this would be an important improvement.
The hash-sum package currently used by buildPluginAssed.ts is not suitable for content hashing (https://github.com/bevacqua/hash-sum/issues/4)
Switching to something like xxhash (this one looks promising https://github.com/ktrongnhan/xxhash-addon ) or metrohash would be safer.
here is a very rough prototype https://github.com/dominikg/vite/blob/feat/asset-hash/src/node/build/buildPluginAsset.ts of how it could work.
Not saying this is the best way to do it. There may be others.


Not Working buildLabels in chart doughnut

In buildLabels function, after generateLabels, legendItems array return undefined elements,
If the graphic is generated with new data and one of the subtitles is disabled.
Generate Chart.

Console Log in 'buildLabels' , variable 'me.chart'

Disable legend

And apply new datasets and generate new chart.
After, log variable 'me.chart'

This bug generate 'cache chart'.
Similar to gif
https://cloud.githubusercontent.com/assets/1019478/9472840/766a4942-4b0c-11e5-96a9-cd6cf476fbc4.gif
For solution, change function 'generateLabels' in 'defaults.doughnut' for code:

Do you have a fiddle that reproduces this?
I'm also happy to look at a PR that fixes this. In general though, when charts flash like that it means that the canvas was reused with destroy() being called on the old chart

@etimberg please, close this bugs. The bug actually happens in the angular-chart.js library.

@matheustoseto in case you opened an issue on the angular-chart.js project, can you link it to this one?

@simonbrunel  Yes. https://github.com/jtblin/angular-chart.js/issues/621

Thanks!


There was an error trusting HTTPS developer certificate

I installed the dotnet-dev-certs v2.1.1 tool and it generates an error when trying to trust the certificate:

When I tried trusting it via the certificate manager, it returns this error:

Take a look at CLI cert instructions: dotnet dev-certs https --trust #6066


More deterministic windowing

As part of debugging what was going on with windowing in the
possibly-buggy recovery example, I found some issues with how clocks
and windowers were implemented. This was basically a week of
continually finding more and more obscure off-by-one errors.
First start_at is renamed to align_to. That former name
incorrectly implied that there were no windows before that time, but
that is not true; windows extend (almost) infinitely in both
directions in time from that alignment point. What determines if an
item is late for a window is not the windowing definition, but the
watermark of the clock.
Next, both {Sliding,Tumbling}Window are required to take
align_to. Previously, this was filled with the timestamp of the
start of the dataflow, but we did not persist it as the recovery
state, nor can we actually properly persist it because recovery state
is per-state-key but at that point we don't have any key. I didn't
want to work on figuring out a way to store "dataflow global" recovery
state, so to make it easier we require you to pick a fixed alignment
time. If you don't ensure align_to is consistent across executions,
you have window boundaries jumping around even when you are using
event time.
Then fixes up and adds additional tests for event time watermarking. I
don't belive we were properly advancing the watermark, preventing it
from going backwards, and handling the extreme no data and EOF cases.
Also does a fix for system time watermarking. Once the data has
completed, we should forever return the watermark as "end of time",
not just when there is an item being processed. I don't believe this
causes any difference in behavior with the way our operators are
currently written, but if we didn't process all available data on each
awakening, this is needed.
Then writes a ton more tests for sliding windowing. I believe we were
improperly mixing in the watermark time into the window
definitions. The definition of the window boundaries is a function of
the arguments to the config, not the current item time or
watermark. The watermark is just used to determine if an item is late.

If this description is too confusing, look at the unit tests I added and see if the semantics match up with what you expect. We can discuss that here.

@whoahbot Have any thoughts on the mysterious process didn't exit successfully: /Users/gha/actions-runner/_work/bytewax/bytewax/target/aarch64-apple-darwin/debug/deps/bytewax-99769e2d4f978c9f (signal: 11, SIGSEGV: invalid memory reference) failure on the Mac ARM build but nowhere else? From comparing the lists of test that do run, something is fishy with window::clock::event_time_clock::tests::test_watermark since that one is not in the CI output but is in my local test output. I have no idea what is malformed about it, though...

First start_at is renamed to align_to. That former name
incorrectly implied that there were no windows before that time, but
that is not true; windows extend (almost) infinitely in both
directions in time from that alignment point. What determines if an
item is late for a window is not the windowing definition, but the
watermark of the clock.

Yep, that makes perfect sense, looking at the previous implementation now I see the problem.

Next, both {Sliding,Tumbling}Window are required to take
align_to. Previously, this was filled with the timestamp of the
start of the dataflow, but we did not persist it as the recovery
state, nor can we actually properly persist it because recovery state
is per-state-key but at that point we don't have any key. I didn't
want to work on figuring out a way to store "dataflow global" recovery
state, so to make it easier we require you to pick a fixed alignment
time. If you don't ensure align_to is consistent across executions,
you have window boundaries jumping around even when you are using
event time.

Sounds good, we'll probably want to add a line about this in the getting started guide, to make it clear that the align_to has to be consistent across executions.
We should clearly say that it's not ok to just align the window to the beginning of the hour using now as a reference if you want proper recovery.

Then fixes up and adds additional tests for event time watermarking. I
don't belive we were properly advancing the watermark, preventing it
from going backwards, and handling the extreme no data and EOF cases.
Also does a fix for system time watermarking. Once the data has
completed, we should forever return the watermark as "end of time",
not just when there is an item being processed. I don't believe this
causes any difference in behavior with the way our operators are
currently written, but if we didn't process all available data on each
awakening, this is needed.

:+1:

Then writes a ton more tests for sliding windowing. I believe we were
improperly mixing in the watermark time into the window
definitions. The definition of the window boundaries is a function of
the arguments to the config, not the current item time or
watermark. The watermark is just used to determine if an item is late.

Thanks for that, the tests made things clearer.
Overall looks good to me, thank you for the good work, this must not have been nice :smile:
Only one note about the PR, unless the changes to the CI and pyo3 update are needed for this PR to work, I'd keep them separate so we can fix the issues arising from there without adding unrelated thing to this PR.
PS: If we bump rust version to 1.68, note that Option::unzip is stable since 1.66, so you can already use it

Only one note about the PR, unless the changes to the CI and pyo3 update are needed for this PR to work, I'd keep them separate so we can fix the issues arising from there without adding unrelated thing to this PR.

I don't want to include them but something about my changes to Rust tests was causing a segfault. Very mysterious. So I was trying to debug that here. I'm going to back out those changes and try to get this building by commenting out some of the tests. I do want to do a "bump all the versions" PR soon too, though.


Fix: Remove beta label from Ksearch API, add Insomnia link

Remove beta label from Ksearch API.
Uncomments insomnia link.

@acgoldsmith That change is from the sync, it looks like the search team changed it in Konnect and the sync wasn't run.

Merging


Implement Relevant Order edge case, Scenario 8 by Legal

We have learned about another edge case around relevant orders, so far our understanding was that a relevant order would be ignored when comparing convictions.
Although, when a relevant order is the sentence with the longest period within it's own conviction AND is the longest when comparing with another conviction, it remains the longest in it's own conviction, and does not affect the external conviction.
For a better understanding, I've created and added a new graph, this can be seen in:
docs/results/08_relevant_order_3.png
Before

After

Video
https://user-images.githubusercontent.com/136777/112712242-0a281580-8ec6-11eb-8cc4-850bf5f5e78b.mov
Story: https://trello.com/c/ycbp7CgU

 [DC] Scenario 8: Relevant Order (by Legal)


trueseeing: 2.1.4 -> 2.1.5

Description of changes

Upgrade trueseeing: 2.1.4 -> 2.1.5

Release notes: https://github.com/alterakey/trueseeing/releases/tag/v2.1.5

Things done

Built on platform(s)

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

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 190672 run on x86_64-linux 1

1 package built:

trueseeing


Developer must be signed in to create a profile

Use devise for user authentication.

I ended up pulling the trigger on this since it was blocking a few other issues/PRs.
The current implementation is a basic devise installation with a User model. Accounts and roles can come later.


COR-410: Lazy load @zxcvbn-ts chunks with dynamic import

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[x] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[x] npm test runs as expected.
[x] npm run build runs as expected.

Instead of loading the zxcvbn library from the cdn, we can create different chunks for zxcvbn packages and serve those from our configurations.This is considered a DX improvement for CSP

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


RightLink Utilization Data Collector

Collects RL utilization data from TSS and populates a CSV. If a parent account ID is passed, it will iterate through all child accounts.

Ready for review.


User Interface Systems and Tab System

Adds the concept of systems to the user interface.

Adds the tab system.

Added a new text validator that the tab system utilizes to ignore certain key presses.

Tab System
Add a list of entities to the tab system, and you can then press tab to cycle through them.
Reason
I was making a personal project and added something that didn't exist, according to the documentation. I'm not entirely sure of the implementation, but it works from what I can tell. It might have some unwanted side effects, but I thought I'd add a pull request, just in case you like the look of it so far.

Hi @Rixium , thank you for this PR!
Just wondering, what did you mean by this:

"It might have some unwanted side effects"

Also can you please provide a minimal example so it will be easier for me to test / understand how to use it?
Thanks!

Hi @Rixium , thank you for this PR!
Just wondering, what did you mean by this:

"It might have some unwanted side effects"

Also can you please provide a minimal usage example so it will be easier for me to test / understand how to use it?
Thanks!

Basically, I don't know the full extent of your library, so I'm not sure if changing things such as ActiveEntity will have an unwanted effect elsewhere.
I created it so I could tab through input fields and buttons on a form. Below I create a tab list and pass in the desired entities that can be tabbed through. The color defines the color of the entity when it's the active tabbed entity.
TabList tabList = new TabList(new Entity[] { inputField, inputField2, loginButton }, Color.Yellow * 0.9f);
You then add the tab list to the user interfaces systems, which are updated every update.
UserInterface.Active.AddSystem(tabList);


Conditionally load core_ext/blank depending on AS

This eliminates a warning when running in Rails.
/usr/local/var/rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/tracker_api-0.2.10/lib/core_ext/object/blank.rb:103:warning: already initialized constant String::BLANK_RE
/usr/local/var/rbenv/versions/2.2.2/lib/ruby/gems/2.2.0/gems/activesupport-4.2.3/lib/active_support/core_ext/object/blank.rb:102:warning: previous definition of BLANK_RE was here

:+1:


Create Sakura.md

Hi @plickoff!
Thanks for wanting to contribute to Bootstrap by sending this pull request!
Unfortunately, your pull request seems to have some problems:

The title of this pull request strongly suggests that you were using Bootstrap to test out Git or GitHub, rather than proposing a legitimate change. If that's accurate, please DON'T do that again! Instead, use your own personal repositories to experiment with how to use Git or GitHub. Using the repos of public projects (such as Bootstrap) for such experiments wastes the time of those projects' maintainers and is thus considered rude.

You'll need to fix these mistakes and revise your pull request before we can proceed further.
Once you've fixed these problems, you can either ask the maintainers to re-open this pull request, or you can create a new pull request.
Thanks!
(Please note that this is a fully automated comment.)

Just some test

@plickoff I think you must have two accounts github or more to learn how it works.


This PR is for issue#1041

The PR has the following changes done:

A new case in core.js for JSON and JSONB

A fix in if condition to look for null value

A condition to check for string values and return values enclosed in double quotes to be displayed in the UI.

A formatJSONpresentation() function to return string appended with pre tag to show the pre-formatted string in the UI.

And if condition to call the formatJSONpresentation() function based on the type of the columns.

PrintJSON() function to stringify the JSON and pass a prettiness factor

New PR#436 has been raised for these changes, closing this PR as it was showing some old commits which have already been pushed to master.