Buybox filter in product request

Hi,
Keepa recently added a buybox parameter for product requests, as shown below. Would it be possible to add it to the code?
✜ buybox
Additional token cost: 2 per product
Boolean value (0 = false, 1 = true). If specified and has the value 1 the product and statistics object will include all available buy box related data:
Thanks a lot!

Could you please point me to the buy box documentation on keepa?

Sure, see the last option in the following link:
https://keepa.com/#!discuss/t/request-products/110
Thanks a lot!
On Wed, May 6, 2020 at 5:16 PM Alex Kaszynski<EMAIL_ADDRESS>wrote:

Could you please point me to the buy box documentation on keepa?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/akaszynski/keepa/issues/59#issuecomment-624895361,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMOKBU352IO3WGSRKA5QBRTRQHHRNANCNFSM4M2ZBGMQ
.

This feature will be out in 0.20.1 on https://pypi.org/project/keepa/ shortly.

thanks a lot!
On Mon, May 18, 2020 at 2:06 PM Alex Kaszynski<EMAIL_ADDRESS>wrote:

This feature will be out in 0.20.1 on https://pypi.org/project/keepa/
shortly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/akaszynski/keepa/issues/59#issuecomment-630348215,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMOKBUZGJTO6MRPGB43K6P3RSF2MBANCNFSM4M2ZBGMQ
.


Revert "Revert "node compatibility typescript infrastructure""

Third time's the charm. No changes, just rebased on top of fresh capnp revision.
This reverts commit e88bae5f3817d5d40c06a7b988fd284be1a96b98.

Is there a corresponding internal PR with a good CI run?


Connection with remote client - Certificate already in trust store

Hi all,
I was trying to connect to a remote LXD server using a certificate, but when calling authenticate I got 'pylxd.exceptions.LXDAPIException: Certificate already in trust store'
Here the simple python code I'm using.
$ python3
Python 3.7.3 (default, Dec 20 2019, 18:57:59)
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from pylxd import Client
>>> key = '/etc/fos/plugins/plugin-fdu-lxd/templates/lxd.key'
>>> cert = '/etc/fos/plugins/plugin-fdu-lxd/templates/lxd.crt'
>>> c = Client(endpoint='https://<IP_ADDRESS>:8443',verify=False, cert=(cert,key))
/usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#ssl-warnings
  InsecureRequestWarning)
>>> c.authenticate('fos')
/usr/lib/python3/dist-packages/urllib3/connectionpool.py:849: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised.
I remember I was using the same code without issue [1], there was some change in LXD?
[1] https://github.com/lxc/pylxd/issues/315#issue-338532164

I solved this, seems that I was using an old certificate that was no more valid, my bad.
I'm closing this


Improve wordlist

Improve the existing wordlist with better/more-known words, as some of the words in the existing wordlist can't be used in the game because they are too hard to guess.

Hi there! I'd like to work on this issue.

I would add some more words

Hello, @kirkland-signature, @jsvigneshkanna start working and send a PR my way.


feat: Endpoint to request an invite to an organization's Slack channel by user ID - API spec update

Spec update for #207
Update the API spec to replace email based invitation mechanism with one based upon IMS user ID, as read from the IMS user token.

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

v1.28.0
GitHub release

Your semantic-release bot :package::rocket:


Rename overwrote a file

I renamed
file-old.txt -> file.txt
file.txt -> file.new.txt
and it overwrote the new file with the old one and renamed the old one to .new
Workaround is to do it in two steps until we have fixed this.

The file I overwrote was my autocomplete rewrite, but backups saved us.

Fixed in 735f1c832fcb9d42bf19233ce150f56fa7fda6b7, will be seen in next release.


generateOEMolFromTopologyResidue sometimes fails on osx due to non-UTF-8 character

Sometimes, generateOEMolFromTopologyResidue fails on osx due to the following error:
Traceback (most recent call last):
  File "/Users/choderaj/miniconda/lib/python3.6/site-packages/perses-0.1-py3.6.egg/perses/rjmc/topology_proposal.py", line 1236, in build_system
    system = self._forcefield.createSystem(new_topology, **self._forcefield_kwargs)
  File "/Users/choderaj/miniconda/lib/python3.6/site-packages/simtk/openmm/app/forcefield.py", line 1123, in createSystem
    if generator(self, res):
  File "/Users/choderaj/miniconda/lib/python3.6/site-packages/openmoltools/forcefield_generators.py", line 504, in gaffTemplateGenerator
    molecule = generateOEMolFromTopologyResidue(residue)
  File "/Users/choderaj/miniconda/lib/python3.6/site-packages/openmoltools/forcefield_generators.py", line 139, in generateOEMolFromTopologyResidue
    [status, output] = getstatusoutput(command)
  File "/Users/choderaj/miniconda/lib/python3.6/subprocess.py", line 517, in getstatusoutput
    data = check_output(cmd, shell=True, universal_newlines=True, stderr=STDOUT)
  File "/Users/choderaj/miniconda/lib/python3.6/subprocess.py", line 336, in check_output
    **kwargs).stdout
  File "/Users/choderaj/miniconda/lib/python3.6/subprocess.py", line 405, in run
    stdout, stderr = process.communicate(input, timeout=timeout)
  File "/Users/choderaj/miniconda/lib/python3.6/subprocess.py", line 830, in communicate
    stdout = self.stdout.read()
  File "/Users/choderaj/miniconda/lib/python3.6/codecs.py", line 321, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xf0 in position 34: invalid continuation byte

It seems that, on osx, this particular file was producing unprintable output that was not UTF-8, causing trouble for the subprocess.getstatusoutput() call:
antechamber -i /var/folders/m1/wl3ptzqx2csf2r_q2bfy78n0h7kcfv/T/tmpn1iljb3r/molecule-before-bond-perception.mol2 -fi mol2 -o /var/folders/m1/wl3ptzqx2csf2r_q2bfy78n0h7kcfv/T/tmpn1iljb3r/molecule-after-bond-perception.ac -fo ac -j 2

Unknown bond type for BOND(C1-N1:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C1-N4:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C1-N5:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C2-N2:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C2-N3:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C2-H1:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C3-C4:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C3-O1:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C3-H2:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C3-H3:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C4-C5:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C4-C9:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C4-H4:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C5-C6:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C5-H5:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C5-H6:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C6-C7:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C6-H7:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C6-H8:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C7-C8:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C7-H9:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C7-H10:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C8-C9:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C8-H11:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C8-H12:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C9-H13:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C9-H14:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C10-C11:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C10-C18:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C10-H15:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C11-C12:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C11-H16:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C12-C13:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C12-H17:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C13-C17:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C13-H18:??TZ?), assuming it is a single bond
Unknown bond type for BOND(N1-C14:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C14-O1:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C14-C15:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C15-N2:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C15-C16:??TZ?), assuming it is a single bond
Unknown bond type for BOND(N3-C16:??TZ?), assuming it is a single bond
Unknown bond type for BOND(N3-H19:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C16-N4:??TZ?), assuming it is a single bond
Unknown bond type for BOND(N5-C17:??TZ?), assuming it is a single bond
Unknown bond type for BOND(N5-H20:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C17-C18:??TZ?), assuming it is a single bond
Unknown bond type for BOND(C18-H21:??TZ?), assuming it is a single bond

@jchodera  I'm getting the unicode decode error when I call generateOEMolFromTopologyResidue...but it seems like this issue has been resolved?

I'm not entirely sure we solved this. Do you have ambermini installed or ambertools?
If you have ambermini, try swapping it out for ambertools:
conda remove --force --yes ambermini
conda install --yes ambertools

@jchodera I think it might be the other way around? Your comment reminds me that you were using ambertools and getting this error, while I was avoiding it with ambermini.

@jchodera @pgrinaway I've tried both ways and I still get an error (although when I do patrick's way, the error come earlier is related to amber min not including a package called parmed).
Is line 139 [status, output] = getstatusoutput(command) essential? Maybe we could try switching to getstatus() and getoutput() (https://docs.python.org/2/library/commands.html) instead? Or try catching the errror?

I realize I fixed this issue in https://github.com/choderalab/openmoltools/pull/272 but nobody ever merged it.
@pgrinaway : Can you review that PR and merge if OK?


Add DigitalOcean

https://github.com/jonleibowitz/awesome-digitalocean
This is a curated list of resources for users of the cloud service DigitalOcean.
By submitting this pull request I confirm I've read and complied with the below requirements.
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title.For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:

Include a short description about the project/theme of the list. It should not describe the list itself.Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.

The list I'm submitting complies with these requirements:

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme. (Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.

Placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.
Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of sub-lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
If you use a license badge, it should be SVG, not PNG.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

Each link description starts with an uppercase character and ends with a period.Example: - [AVA](…) - JavaScript test runner.
Drop all the A / An prefixes in the descriptions.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.

Go to the top and read it again.

Please read the guidelines more closely. Multiple points not followed from it. Try going through the list point for point and check that you follow it. :)

Thank you, I'm reviewing the guidelines again for items that I may have missed or where improvements can be made. Feel free to close this in the meantime.

@jonleibowitz You can ignore the Marker style should be -   errors, but the rest are valid.

Thank you for the review @DanailMinchev @sindresorhus, I've used awesome-lint and made the necessary fixes to the repo.

Tweet: https://twitter.com/awesome__re/status/1042112986725269504


Document OPAL_WRITE_OPPANEL_ASYNC

OPAL_WRITE_OPPANEL_ASYNC is undocumented

https://open-power.github.io/skiboot/doc/opal-api/opal-write-oppanel-async-95.html#opal-write-oppanel-async fixed in https://github.com/open-power/skiboot/commit/d69e78b29d4269b63426c9a60641295fcef1a827


Feature: Put the FPS and quality in advanced

I think that like for audio and echo cancelling and so on you have the advanced section, this should be also for FPS and quality. No normal user will know what to do with this.
Also I think that changing resolution for Screen Sharing is a bad idea. Before it was auto set by the browser depending on the resolution of the window. Now, if I change in options, the content is cut off, as the lower resolutions are 4:3 , but most screens are 16:9. I would let the browser take care of the resolution of screen sharing and NOT let the user change it. Now the user by setting medium destroys the screen sharing. The browser stops to auto scale the resolution if I resize the window being shared.

What about that a user can now destroy screen sharing when choosing a resolution and stops the browser from auto setting the resolution based on the actual size of the shared window?

Ah, forgot about that, yes, we might want to remove this option.

Also removed video frame rate. Should be enough with screen sharing frame rate.


CPP GPU test running too long

URL:
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-gpu/detail/PR-13914/3/pipeline/278
Currently CPP GPU takes around 72 minutes to finish all its trainning tasks and it is not ideal for a PR CI test to handle that. Essentially the CI to verify the PR is to ensure the functionalities didn't have any problems. The performance test ideally should be placed under the nightly tests. As @leleamol recommended, some improvement can be taken in here such as the number of epoch to be set to 1. This would bring down the runtime for this test to under 30 minutes and save time.
@marcoabreu

Close this issue since problem fixed. Thanks @leleamol for his contribution!


Scenario buttons not resizing

Hi @tblanke
I noticed that, whenever one puts in a long scenario name, the buttons above do not resize as espected.

Perhaps this issue is already solved in ScenarioGUI, but I noticed it in GHEtool v2.1.2.
Best,
Wouter

This is indeed a bug. I will create a fix.


Questions about the code of adversarial training

Hi, thanks for your benchmark work and the open source code. I have a question about the AT part of the code.
In your paper, the section on adversarial training references the paper 'Extending adversarial attacks and defenses to deep 3D point cloud classifiers.', in which adversarial examples are progressively updated during the model training process and original point clouds are used both for clean training and for generating adversarial examples.
However, in the AT part of the code, the adversarial examples are fixed, and the adversarial and clean examples come from different original point cloud data. I would like to know which method are used for adversarial training in the benchmark leaderboard and if the two methods will lead to different defense effect.
I‘d appreciate it if you could answer my question. Thanks again for your work.

Hi @Link-world. You are right. In my benchmark, I used fixed adversarial training, and the same method is also used in hybrid training. Using progressively updated adversarial training would indeed make the model training more robust, but due to time constraints, I did not use progressively updated adversarial training in my benchmark. You are welcome to try this training method to improve and comprehensively enhance the benchmark.

OK, thanks for your answer.


feat: impl Iterator for Transport

Blocked on https://github.com/1c3t3a/rust-socketio/pull/79 transports needs to be clonable


Add support for fees and UTxO reuse to the tx-generator

This PR adds support for fees and UTxO reuse to the tx-generator.

bors r+


Consistent version number and fixed duplicate number in steps.

Current coverage is 85.71% (diff: 100%)

Merging #15 into master will not change coverage

@@             master        #15   diff @@
==========================================
  Files             2          2
  Lines            21         21
  Methods           5          5
  Messages          0          0
  Branches          0          0
==========================================
  Hits             18         18
  Misses            3          3
  Partials          0          0

Powered by Codecov. Last update d38a829...11eeba2


Include addPractitioner API call

Medplum supports both createPatient and createProject API calls. I believe it would be useful to include a addPractitioner.
In my use case I want doctors to register in my app when they are invited by patients.
More details: https://discordapp.com/channels/905144809105260605/905144809105260608/1027056044419055626
Thanks,
Bruno

With the updated "invite" flow, you can now create a Patient, Practitioner, or RelatedPerson.  This is a single API that handles configuring AccessPolicy and UserConfiguration.
The API is available at /admin/invite

Docs: https://www.medplum.com/docs/tutorials/app/invite
PR: https://github.com/medplum/medplum/pull/1057


Half float checkpoint

added half cpp backend, half tensor conversion, half tensor math operations, added half to linear, softmax layer, cnn layers, opt module. tested examples naive, module, train_cnn on mlp and cnn, refactored broadcast, added benchmark for fp16 vs fp32

Usage example:
root@1c6aaef3db53:~/singa-hpmerge# PYTHONPATH=build/python/ python3 examples/cnn/train_cnn.py cnn mnist -m3 -pfloat16 -i 7
Starting Epoch 0:
Training loss = 0.061211, training accuracy = 0.752235
Evaluation accuracy = 0.944912, Elapsed Time = 6.867703s
Starting Epoch 1:
Training loss = 237.194122, training accuracy = 0.920124
Evaluation accuracy = 0.957131, Elapsed Time = 6.740274s
Starting Epoch 2:
Training loss = 167.028595, training accuracy = 0.944337
Evaluation accuracy = 0.970353, Elapsed Time = 6.833484s
root@1c6aaef3db53:~/singa-hpmerge# PYTHONPATH=build/python/ python3 examples/cnn/train_cnn.py cnn mnist -m3 -pfloat32 -i 7
Starting Epoch 0:
Training loss = 596.964600, training accuracy = 0.789421
Evaluation accuracy = 0.943209, Elapsed Time = 5.502895s
Starting Epoch 1:
Training loss = 234.664322, training accuracy = 0.920758
Evaluation accuracy = 0.960036, Elapsed Time = 5.506354s
Starting Epoch 2:
Training loss = 165.501694, training accuracy = 0.944454
Evaluation accuracy = 0.971254, Elapsed Time = 5.482749s


Large font size cuts off author

I use a large font size (20). When I open git blame it shows up with just ... for the author. When I try to drag the git blame area to make it bigger, it won't move at all. If I could adjust the column by dragging then I could see the author fine. Is the column suppose to drag? It shows the slider/draggable cursor when I hover over the right side, but does nothing for me.

I tested turning my font size down and it does show the author then, but I'm kind of partial to that setting. :) Any ideas for how to work around or fix this?

Disabling Shadow DOM shows the author, but messes up styling. See also #64

dupe of #64 we're going to get this resolved soon.


Add member functions with functional way

How should "member" functions should be implemented with the functional way?

As the project walks to have a powerful type system that could infer parameters, call functions by pattern, etc...
I think that can be used this pattern for these declarations:

import io;

type User = { name: *Char, surname: *Char };

fun (user: User).sayHello(): Void {
  println("Hello, I am " ++ user.name ++ " " ++ user.surname);
}

fun main(argc: Int, argv: **Char): Void {
  let user = User {name: "Some", surname: "Name"};

  user.sayHello();
}

As the project walks to have a powerful type system that could infer parameters, call functions by pattern, etc...
I think that can be used this pattern for these declarations:

import io;

type User = { name: *Char, surname: *Char };

fun (user: User).sayHello(): Void {
  println("Hello, I am " ++ user.name ++ " " ++ user.surname);
}

fun main(argc: Int, argv: **Char): Void {
  let user = User {name: "Some", surname: "Name"};

  user.sayHello();
}

Using member functions is useless when you have currying functions with macros, like this case:
PS: this code is not valid.

let list = list!(1, 2, 3, 4, 5);

list
|> map(x -> x + 5)
|> filter(x -> x > 4)
|> foreach(x -> {
  println(x);
});


Window Border expands when showTabsInTitlebar is enabled

Environment
Windows build number: 10.0.18362.239
Windows Terminal version: 0.3.2171.0

Steps to reproduce
Set showTabsInTitlebar to true.
Expected behavior

Actual behavior

When showTabsInTitlebar is false

Wow! This is hilarious/terrible.
What does your display topology look like? Multiple monitors? different scaling factors?

It was a pretty unpleasant surprise
I'm running 3 Displays, one laptop and 2 external. All are at 1080 with 100% scaling.

This is actually #2057 which should be fixed by #2150. IIRC we decided that it didn't make the cut for 0.3, but it should be in the next release.


Try harder by looking for a bool magic method when extracing bool values from Python objects.

I decided to not implement the full protocol for truth value testing as it seems confusing in the context of function arguments if basically any instance of custom classes or non-empty collections turns into true.
Closes #3637

I don't think it is good to single out objects that define __bool__. It's one of several equally valid ways to define truth conversion, on the Python side it absolutely doesn't matter which one you use. For example, when implementing a collection class I might give it an explicit __bool__ or not, depending on if I can be bothered to look up how the behavior is otherwise.
Contrary to something like __int__, __bool__ isn't reserved for object that "feel like a bool" (e.g. numpy bools).
I.e. my recommendation is, either keep being strict here, or just use PyAny::is_true().

While I can see the argument for being consistent in one way or the other, i.e. either strict insofar a function argument is sort of type specification for the Python API or loose where we try as hard as possible to convert any incoming value into a the target type, I think that we cannot solve this issue as long as the single FromPyObject trait is doing double duty for both approaches.
There is also precedent for this middle ground approach in other implementations, e.g. Vec accepts only implementors of the Sequence ABC even the implementation to convert the Python iterable into a Vec does not require it at all.
So while I would prefer a principled approach, the practicalities of ergonomic usage of PyO3 based on a single trait prevent this for now as far I can see.

I can see that, but my argument is that the approach in this PR is worse than either. It happens to work for numpy bools, fixing the original issue, but also allows conversion for a whole host of other types, none of which have to be "bool-like", and arbitrarily excludes others which are no less "bool-like".

but also allows conversion for a whole host of other types, none of which have to be "bool-like", and arbitrarily excludes others which are no less "bool-like".

But does this have any concrete usability consequences or is it merely an uncomfortably inconsistent design?

Maybe as a data point that this can work, pybind11 seems have run into the same problem, i.e. https://github.com/pybind/pybind11/pull/925 [^1] and solved it in similar manner albeit optimized to avoid the cost of lookup_special (which could do here as well).
Admittedly, they are in the advantageous position of having the pyarg().noconvert() modifier so that the author can explicit request stricter or looser conversions. But then again, they even special-cased the loose behaviour to always apply to numpy.bool_ (which is also something we could do here).
[^1]: I was not aware of that PR went starting to implement this one.

But they certainly also had a long discussion before settling on the final approach. 😅

This reminds me a lot of https://github.com/python/cpython/pull/15609 - in Python 3.12 they changed all C functions to accept any object and check using equivalent of PyAny::is_true.
Slight aside, what do you think of renaming PyAny::is_true to PyAny::is_truthy? I keep intuitively thinking x.is_true() would map to the python x is True :)

Slight aside, what do you think of renaming PyAny::is_true to PyAny::is_truthy? I keep intuitively thinking x.is_true() would map to the python x is True :)

This I like.

This reminds me a lot of python/cpython#15609 - in Python 3.12 they changed all C functions to accept any object and check using equivalent of PyAny::is_true.

This, not so much.

👍 I will open an is_truthy PR hopefully later in the week.
Regarding the Python 3.12 change, I agree it's not my favourite behaviour either (and PyO3 being principled about the difference between 1 and True helped me isolate a bug in the past). Despite that I sort of think if we're making this conversion more lax it might be best if we match CPython behaviour to minimise surprises to users. But I'll try to review this PR in detail as soon as I get a moment.

(Sorry I was a little slow on review here, ended up getting excited by the Py2 work...)
Hmmm, it's hard to make a judgement on the right solution for this. I am definitely in favour of us trying to fix the numpy case.
Overall, we've definitely been trending slowly towards being more lax on these Python -> Rust conversions, e.g. #3374, #3197, as this seems to be what users want.

they are in the advantageous position of having the pyarg().noconvert() modifier

Yes, I definitely think there is room for something like this; I called it "strict" mode in https://github.com/PyO3/pyo3/issues/3226#issue-1751584990, we could have #[pyo3(noconvert)] as an annotation on function arguments, for example.

Overall, I think that pybind11 prior art is a reasonable one to follow here, and I like consistency in the ecosystem (if we think the CPython choice is too lax). I also think it's less breaking for future users if we chose to go more lax again to match CPython than it would be to get stricter.
I definitely think that where we're at is that FromPyObject is at the moment a lax conversion. We allowed str to ip address in #3197, after all.
So perhaps the road ahead is to proceed with the implementation of this as is currently written in this PR, and then if users want to opt-out, we should add a #[pyo3(noconvert)] attribute? I think that could be supported by a separate trait, so we can implement it on-demand starting with bool. The hardest thing might be naming that trait :)
All this said, would let x: bool = any.extract()?; being roughly equivalent to Python bool(any) be a good thing? My Rust brain says no but my Python brain says yes 😖
I think I need to sleep on this and see how I feel in the morning...

With fresh eyes I've come around to this solution, I think the shaker behaviour change is preferable.
If users want to have the stricter method again I suggest we explore the #[pyo3(noconvert)] option.

@birkenfeld I would be quite unhappy to merge this over you direct objection. I wonder if you can be placated by the suggestion of adding a #[pyo3(noconvert)] attribute to put these decisions into our user's hands eventually? Also maybe the pybind11 precedent suggests that this is tenable? I think we all agree that this is messy and inconsistent and from that perspective it can be said that "the approach in this PR is worse than either", but I also think that this is an remedy for an actual pain point felt by our users working in a messy and inconsistent ecosystem.

I'm all in favor of the noconvert annotation. However, it doesn't touch my core objection: that considering __bool__ but not __len__ is simply inconsistent. The availability of a way to opt out of broad boolean conversion makes this inconsistency even more glaring since there is no justification for limiting the scope in search of a compromise.
Just think about the user's perspective. If I can pass in None and objects like winreg.HKEYs or gdbm.gdbms, but not others that Python considers bool-convertible just fine in other circumstances, does that really make sense?

The availability of a way to opt out of broad boolean conversion makes this inconsistency even more glaring since there is no justification for limiting the scope in search of a compromise.

Yes, if we had noconvert today, using the full truth value testing procedure might be a better choice for the "broad/loose" setting. But we do not have that and hence the compromise.

Just think about the user's perspective. If I can pass in None and objects like winreg.HKEYs or gdbm.gdbms, but not others that Python considers bool-convertible just fine in other circumstances, does that really make sense?

I think there is a difference "bool-convertible" and "truthy". The truth value testing which includes __len__ is about what is "truthy" and does not say anything about being "bool-convertible" which I would argue is something that duck-typed Python does not care about at all, but statically notionally typed Rust and C++ do. And while I think considering a non-empty collection or a not-None class instance true-like for an if statement works, I don't think it works for a boolean function argument because it just looses too much information.

I think there is a difference between "bool-convertible" and "truthy". The truth value testing which includes len is about what is "truthy" and does not say anything about being "bool-convertible" which I would argue is something that duck-typed Python does not care about at all, but statically notionally typed Rust and C++ do.

This is my feeling too when I was reflecting on let x: bool = any.extract()?; above, I think our intention there has always been for that to be book conversion and not truth testing.

My point is that __bool__ is not a method for "bool conversion". It is specifically for defining truthiness, as done by bool(x) or if x.
Just check out https://github.com/search?type=code&auto_enroll=true&q="def+bool%22 - many of the objects defining __bool__ are far from "objects similar to a bool that should be convertible to it". (Just like my example of HKEY and gdbm, which are from the stdlib.)

I see what you mean, that "bool conversion" isn't separable from truth testing on the Python side.
Given the strength of @birkenfeld's conviction, maybe we should slow down for now and just take the route pybind11 did for their strict pathway, i.e. special case for numpy bools?

Given the strength of @birkenfeld's conviction, maybe we should slow down for now and just take the route pybind11 did for their strict pathway, i.e. special case for numpy bools?

Yes, if only to resolve the issue at hand. I do see some types in the above list would be good candidates as well, like pytorch's BoxedBool, but I guess it is better to solve some issues than none at all. Will push the change as a separate commit...

Uff, it seems __qualname__ on PyPy is bool_ instead of numpy.bool_? Do would just skip the test on PyPy or loosen the name check to numpy.bool_ or bool_? Should I use something other than get_type().name()?

I wonder if this changes based on version, e.g. maybe 3.9 or 3.10 change?
It could be worth adding PyPy 3.10 on Ubuntu to the pr ci to get a hint what might work before the full merge queue runs?

I tested this locally using pyenv and it does seem independent of the PyPy version, i.e. the behaviour is the same for 3.8, 3.9 and 3.10 and name() always yields "bool_" without the module.

But reading https://peps.python.org/pep-3155/ and testing this in the CPython REPL, __qualname__ is not intended to include the module name. I wonder if it is really a full replacement for tp_name as used by us?

From reading https://docs.python.org/3/c-api/typeobj.html#c.PyTypeObject.tp_name, I think we should use __module__.__name__ instead of __qualname__ as the abi3 fallback?

So, I think ideally, this would be rebased on #3660 and made use of PyType::full_name if that one is accepted

Rebased this onto main now that the full name is available on PyType and used this to limit the scope of the looser conversion.


Review and implement more sane schema

The current schema was put together in a hurry, when experimenting with Airtable years ago.
We have a better idea how it's being used, now, and know more, so the task is to clean up the schema, so we can:

[ ] avoid errors related to poorly used types in columns/fields
[ ] allow for exporting to more sensible open source database, like PostgresSQL
[ ] make changes easier in future
[ ] support people removing their own data from constellate without leaving hanging references

The link below shows the schema in use right now:
https://airtable.com/tblEVkEBQIWYpQtj2/viwyk63XIiNezSzyg

Thanks for chattng just now @rmparr,
I'm gonna summarise the key ideas here from our chat.
I've updated the schema now, but we can make the import schema quite a bit simpler.

column
notes

admin
actual boolean this time

visible
actual boolean this time too

tags
comma separated strings – we keep the original version, but downcase, convert special characters internally

photo
If this added, it’s now just a url for a public photo. We import so we can serve different sized versions server-side

email
Required. Users have the option to use it for looking up a gravatar image in-app, and if when we integrate with anything using email addresses like mailchimp, slack, by default we'd use this link users.

phone
assumed to be a mobile. Like for Whatsapp/Signal

twitter
just the username, not the full url

linkedin
again, the name on linkedin. Not the full url

facebook
vanity name again. We add

bio
For long form text. We’d likely try to render this a markdown, to support links and the rest

Below, is what this might look like. We this as a basis for any csv import, and generate linked tag objects for users as part of the import process

name
admin
visible
tags
photo
email
phone
website
twitter
linkedin
facebook
bio

Bart Simpson
FALSE
TRUE
policy, government

<EMAIL_ADDRESS>

Sideshow Bob
FALSE
TRUE
design, creative

<EMAIL_ADDRESS>

Montgomery Burns
TRUE
TRUE
Non-exec director, entrepreneur

<EMAIL_ADDRESS>

Barney Gumble
FALSE
TRUE

<EMAIL_ADDRESS>

Lisa Simpson
FALSE
TRUE
tech, Music, Live Coding

<EMAIL_ADDRESS>

Gavin Starks
TRUE
TRUE
writing, environment, climate change

<EMAIL_ADDRESS>

Christopher Adams
TRUE
FALSE
climate change

<EMAIL_ADDRESS>

mrchrisadams
mrchrisadams

If you're interested in finding a way to get the entire internet to run on renewable power, I'd like to talk to you.I'm building bits of this constellate thing here, in my spare time, and if you're interested in contributing I'd love to hear even more.

Another Chris Adams
FALSE
TRUE
writing

<EMAIL_ADDRESS>

I'm gonna park this here - based on on the use case with IB1, and the idea of 'clusters' of users, there's a couple of ways we might do it.
The top one means we end up with a really simple, easy to deploy version of constellate, where you have one deployment per cluster.
This keeps data for each one entirely separate. It means that admins would need to manage each one separately.
If we used oauth or some email-based passwordless system as the primary ways of logging in, then users could exist in multiple separate constellations without too much faffing with passwords. I can imagine this being a single button deploy with Heroku, for example.
The second option models the notion of clusters inside a single deployed app, and a single database. This is slightly more centralised, and

Something to keep in mind with OAuth and multiple deployments is that, due to the callback URL, OAuth would have to be set up for each individual cluster.
In this context, cluster1.ib1.cl8.io cluster2.ib1.cl8.io are separate applications with separate databases, requiring a separate dev keys to authorize. This makes the 'spin up another cluster' scenario more complicated.


Fix information in user delete dialog

fixes https://github.com/OpenSlides/openslides-client/issues/2636

fixed wording: "account" vs. "participant"
fixed header in case of participant removal
hid left column in case of single user removal/deletion


[Docs] Dataset download links

Branch
1.x branch https://mmediting.readthedocs.io/en/1.x/
📚 The doc issue
Hi, I'd like to try out training the SwinIR Lightweight Image Super-Resolution config. This references the datasets DIV2K, Set5 and Set14. It links to where I can download DIV2K, but doesn't mention anything about where to get Set5 or Set14. So I'm currently missing the following:
│   ├── Set5
│   │   ├── GTmod12
│   │   ├── LRbicx2
│   │   ├── LRbicx3
│   │   ├── LRbicx4
│   ├── Set14
│   │   ├── GTmod12
│   │   ├── LRbicx2
│   │   ├── LRbicx3
│   │   ├── LRbicx4

Where can I download these files?
Suggest a potential alternative/fix
Download link or script for obtaining these, or if these are not readily available, possibly choosing different example datasets that are easier to obtain?
Edit: I found this link in another issue thread: https://drive.google.com/drive/folders/1IOmj0NbHQC_m7Lu-EEFOwEtVD4KsexYF
It might be good to add to dataset docs page so people don't have to hunt for it

Thanks for your suggestions！We will update dataset download links in these few days. @austinmw

Thanks!


logAsJson global value missing in the documentation

Bug description
For ops setup, we required to send logs to an external ops stack (in our case Azure Monitor, Log Analytics, App Insights). JSON messages should be used.
We followed the configurations and tried to configure it using meshConfig, k8s patches and overlays. After some time, we checked the Helm templates and figured out, that everything we have to do is to add global.logAsJson: true to the operator configuration.
[ ] Configuration Infrastructure
[ X ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
We guess it would be great to have it documented somewhere in the documentation as this is a flag that probably everyone needs to flip when running Istio in production.
https://istio.io/docs/reference/config/istio.mesh.v1alpha1/ might be a good place to put it.
Steps to reproduce the bug

Install istio

Version (include the output of istioctl version --remote and kubectl version
$ istioctl version --remote
client version: 1.5.0
control plane version: 1.5.0
data plane version: 1.5.0 (13 proxies)

How was Istio installed?
istioctl
Environment where bug was observed (cloud vendor, OS, etc)

AKS

The meshConfig works vor v1.6.1. Going to close the issue. global.logAsJson: true is the solution for v1.5.0

@MarianZoll We just upgraded from Istio 1.8 to 1.9 and in reviewing my IstioOperator config, I see we still have values.global.logAsJson: true. I just looked at the meshConfig spec and I don't see anything about configuring the mesh to log as JSON. There's an option to set the accessLogEncoding, but I assume that's only for access logging. Do you know how to configure Istio to write all logs in JSON format in the current release? And is this documented somewhere?

For what it's worth, here's the relevant snippet from my IstioOperator manifest. I'd love to get rid of any old values settings like logAsJson:
    defaultConfig:
      tracing:
        sampling: 100.0
    enablePrometheusMerge: false
    accessLogFile: /dev/stdout
    accessLogEncoding: JSON
    accessLogFormat: |
      {
        "accessLogFormat": "{\"traceId\": \"%REQ(x-b3-traceid)%\",\"protocol\": \"%PROTOCOL%\",\"upstream_service_time\": \"%REQ(x-envoy-upstream-service-time)%\",\"upstream_local_address\": \"%UPSTREAM_LOCAL_ADDRESS%\",\"duration\": \"%DURATION%\",\"upstream_transport_failure_reason\": \"%UPSTREAM_TRANSPORT_FAILURE_REASON%\",\"route_name\": \"%ROUTE_NAME%\",\"downstream_local_address\": \"%DOWNSTREAM_LOCAL_ADDRESS%\",\"user_agent\": \"%REQ(USER-AGENT)%\",\"response_code\": \"%RESPONSE_CODE%\",\"response_flags\": \"%RESPONSE_FLAGS%\",\"start_time\": \"%START_TIME%\",\"method\": \"%REQ(:METHOD)%\",\"request_id\": \"%REQ(X-REQUEST-ID)%\",\"upstream_host\": \"%UPSTREAM_HOST%\",\"x_forwarded_for\": \"%REQ(X-FORWARDED-FOR)%\",\"requested_server_name\": \"%REQUESTED_SERVER_NAME%\",\"bytes_received\": \"%BYTES_RECEIVED%\",\"istio_policy_status\": \"-\",\"bytes_sent\": \"%BYTES_SENT%\",\"upstream_cluster\": \"%UPSTREAM_CLUSTER%\",\"downstream_remote_address\": \"%DOWNSTREAM_REMOTE_ADDRESS%\",\"authority\": \"%REQ(:AUTHORITY)%\",\"path\": \"%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%\"}"
      }
  values:
    global:
      logAsJson: true
      defaultPodDisruptionBudget:
        enabled: false
      proxy:
        includeIPRanges: '<IP_ADDRESS>/16'
        resources:
          requests:
            cpu: 50m

Hm which of the components are still logging in TEXT format? Then we can also check on the source level.
https://istio.io/latest/docs/reference/config/istio.mesh.v1alpha1/ is a good starting point, but most of the settings seem to be in your snippet.

Thanks for the quick reply. The only property documented for mesh config log format is accessLogEncoding, which only affects access logs. All other logging is in plain text unless values.global.logAsJson is set. If there's another property which can tell Istio to do all logging in JSON - something outside the values section - I would love to use it.
I think there are two issues/questions:

Is there any way to configure Istio containers to log in JSON format other than values.global.logAsJson using the IstioOperator?
If the answer to #1 is yes, is it documented anywhere? Is the values.global.logAsJson property documented? I don't recall how I originally found the values.global.logAsJson property, but I can't find it anywhere in the docs now.

Here's an example of the logs from istio-ingressgateway with only accessLogEncoding configured:
  meshConfig:
    accessLogFile: /dev/stdout
    accessLogEncoding: JSON

...
2021-02-12T22:21:09.399804Z	info	cache	generated new workload certificate	latency=222.533297ms ttl=23h59m59.600204751s
2021-02-12T22:21:09.399849Z	info	cache	returned delayed workload certificate from cache	ttl=23h59m59.600153762s
2021-02-12T22:21:09.400151Z	info	sds	SDS: PUSH	resource=default
2021-02-12T22:21:09.490920Z	info	sds	SDS: PUSH	resource=ROOTCA
2021-02-12T22:21:09.491160Z	info	sds	SDS: PUSH	resource=ROOTCA
2021-02-12T22:21:11.626619Z	info	Initialization took 2.480687684s
2021-02-12T22:21:11.626637Z	info	Envoy proxy is ready
{"accessLogFormat":"{\"traceId\": \"-\",\"protocol\": \"HTTP/1.1\",\"upstream_service_time\": \"-\",\"upstream_local_address\": \"-\",\"duration\": \"0\",\"upstream_transport_failure_reason\": \"-\",\"route_name\": \"-\",\"downstream_local_address\": \"<IP_ADDRESS>:8080\",\"user_agent\": \"Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:71.0) Gecko/20100101 Firefox/71.0\",\"response_code\": \"301\",\"response_flags\": \"-\",\"start_time\": \"2021-02-12T22:33:38.354Z\",\"method\": \"POST\",\"request_id\": \"b8ac5a12-5c7a-923e-be42-1bf3c6b60c75\",\"upstream_host\": \"-\",\"x_forwarded_for\": \"<IP_ADDRESS>\",\"requested_server_name\": \"-\",\"bytes_received\": \"0\",\"istio_policy_status\": \"-\",\"bytes_sent\": \"0\",\"upstream_cluster\": \"-\",\"downstream_remote_address\": \"<IP_ADDRESS>:26135\",\"authority\": \"<IP_ADDRESS>:80\",\"path\": \"/boaform/admin/formLogin\"}"}```

And here's what you get with both `accessLogEncoding` and `values.global.logAsJson`

meshConfig:
accessLogFile: /dev/stdout
accessLogEncoding: JSON
values:
global:
logAsJson: true

...
{"level":"info","time":"2021-02-12T22:46:33.813273Z","scope":"cache","msg":"generated new workload certificate","latency":192090018,"ttl":86399186730459}
{"level":"info","time":"2021-02-12T22:46:33.813415Z","scope":"cache","msg":"returned delayed workload certificate from cache","ttl":86399186597197}
{"level":"info","time":"2021-02-12T22:46:33.813731Z","scope":"sds","msg":"SDS: PUSH","resource":"default"}
{"level":"info","time":"2021-02-12T22:46:33.925013Z","scope":"sds","msg":"SDS: PUSH","resource":"ROOTCA"}
{"level":"info","time":"2021-02-12T22:46:33.925284Z","scope":"sds","msg":"SDS: PUSH","resource":"ROOTCA"}
{"level":"info","time":"2021-02-12T22:46:35.710634Z","msg":"Initialization took 2.120093856s"}
{"level":"info","time":"2021-02-12T22:46:35.710653Z","msg":"Envoy proxy is ready"}

@Ghazgkull Sorry for replying that late. I think this property is not available in the docs, but only in the Helm values of previous versions or the Operator source code:
https://github.com/istio/operator/blob/f408beefc360a5eb4b592a0d8147f8989041ea25/data/profiles/default.yaml#L200
The configuration triggers a start up argument to be set which you might se in one of the generated manifests of the Operator which are applied to K8s.
https://github.com/istio/operator/blob/f408beefc360a5eb4b592a0d8147f8989041ea25/cmd/mesh/testdata/manifest-generate/output/pilot_k8s_settings.yaml#L953-L955
I think it would be wise to standardise the logging options as I do see this to be very valuable for day-2 ops. But I would also assume that this is a lot of effort as it touches different components, the way they log and the way SW is deployed. But might be worth to add it at least to some backlog.
In case you do agree, we can bring this up with the OSS team again.

The title of this issue is "logAsJson global value missing in the documentation" and that issue still exists... so I would suggest that this ticket be reopened. Improving the way logging is configured sounds great, but in the meantime I think the current method should at least be documented.

@howardjohn As we a couple of other people reached out regarding the setting and the documentation to questions towards the core team:

Do you see any chance to work on more standardised logging of all components including generalising the configuration,
Shall we add the values.global.logAsJson somewhere in the docs? I know this links back to some Helm configuration which is not longer updated in the docs. So maybe we want to move it to meshConfig and make it configurable.

In case you don't see any value or the team is already working on something else feel free to close the ticket again.


Fluid Navigator, Too much load

Hello,
Thank you this awesome library!
I use Fluid Navigator for our app. Our app has a full cycle use cases. For example, user goes ->
MainScreen -> A-Screen -> MainScreen -> B-Screen -> C-Screen -> MainScreen
Something like that and goes on.. After some navigations, whole app's performance goes down dramatically.. What should I do for these kinds of navigations ??
I navigate with this code :
this.props.navigation.push(path, param);
Also my main navigator is something like :
const MainNavigator = FluidNavigator(
			{
				map: MainScreen,
				aScreen: AScreen,
				bScreen: BScreen,
				cScreen: CScreen,
				example: Example
			},
			{
				navigationOptions: {
					tabBarVisible: false,
					gesturesEnabled: true
				},
				lazy: true
			}
		);

One last point, on my MainScreep has a MapView and it contains 100+ markers but on the first opening it is smooth AF. After I go to B-Screen and navigate to MainScreen.. It lags too much.
What should I do about this ? :)
Thank you!

Hi @WrathChaos - I'm currently working on a fix that will improve this behavior (#126 for a quick explanation). If you're using maps in a shared transition you will unfortunately be out of luck - the map will be recreated.

The problem is the issue you're seeing with too many controls on the screen. Would  suggest not using the FluidNavigator for setups where you complex control hierarchies.

Thank you so much :)


CSCETSIN-111: Remove unneeded search index and rabbitmq files. Along …

…with those some dependencies are their related code.

Merging to test


Add make targets infra, rabbitmq, rabbitmq_deploy to ironic-kuttle

When not using json-rpc we need the infra operator for the transporturls.rabbitmq.openstack.org CRD. We also need to deploy the rabbitmq cluster.

recheck
Failed on unrelated test "Wait for nova-edpm-compute-0-deploy-nova pod to finish"

/recheck

recheck


Add CLI flag to hide token from repository URL

Following https://github.com/o2sh/onefetch/pull/1314#issuecomment-2078259382
This PR introduces a CLI flag to enable the option of hiding the token from the repository URL, making it an opt-in mechanism rather than the default behavior.
CC @jim4067 @asciimoth @t-h2o

Yeah, it's a trade-off between security and transparency.
In my opinion, transparency combined with user control is the best option.
Transparency:  ensuring users see the raw data without any modifications.
User Control:  allowing users to opt-in to hide tokens if they wish, rather than enforcing it by default.


Improved integration in meta frameworks like Nuxt.js and Gridsome

Work on https://github.com/vuejs/vue/issues/9847
Fix potential a11y issues https://github.com/maoberlehner/vue-lazy-hydration/issues/11
Improve performance by better integration in Vue.js and its meta frameworks.

Hey, @maoberlehner.  I'm happy to share Chrome is donating $2,000 to support vue-lazy-hydration's goals around improving support for meta-frameworks like Nuxt and fixing https://github.com/vuejs/vue/issues/9847  🎉  We think this project's goals align well with helping reduce the impact of hydration on user interactivity.
Great work so far! We hope this helps!
~ signed Addy, @stubbornella and @spanicker

@addyosmani This is amazing! Thank you!

Hello @maoberlehner,
I just opened a pull request to fix this issue: https://github.com/vuejs/vue/pull/10794
Hope this helps :)

@jeanphilippeds this is amazing! I was already investigating how we can work with this in Nuxt.js and Gridsome, but unfortunately, I currently can't give this my full attention. All the more reason I appreciate your help!

I'm just worried about the fact that there was no Vue release since March, I'm wondering if we will have to wait for Vue 3 :/

@maoberlehner I forked vue-server-renderer and it's working great :)

@jeanphilippeds Not really sure what you mean. Did you manage to get lazy-hydration to work with nuxt, I would like this too. Is there a way to work around waiting for the pull request to get merged?

@jeanphilippeds Can we also use your forked vue-server-renderer to get lazy hydration in our Nuxt projects? Could you give a few instructions how to do so? Thank you! :+1:

@jeanphilippeds It would be great to use your vue-server-renderer until the pull request is processed. I see your changes here https://github.com/jeanphilippeds/vue/commits/add-option-to-render-or-not-async-scripts Are these relevant?

Hi, @maoberlehner
Does this issue related what I posted here？
If it is true. It seems, at least now, only the possible workaround will be this one
（ note, Nuxt modern mode can't workaround what we want any more）
Thanks,


(chore) Fold release 0.20 branch into master

This merges all of the changes for Ergo 0.20 into master.

Coverage decreased (-2.7%) to 96.852% when pulling faa02482f65844a1d40dc49e9204df4cb778e89d on js-release-0.20 into 47893443fd21f6ebd29671fdedc3839e1ae7c67b on master.


iOS 9: Safari cannot download this file

HI!
The pkpass file doesn't work at iphone devices. When the file is downloaded by Safary, it is showed this error: "Safari cannot download this file".  The passTypeIdentifier or teamIdentifier provided may not match your certificate, or the certificate trust chain could not be verified.
Jun 23 17:46:01 --- last message repeated 1 time ---
Jun 23 17:46:01 iMac MobileSafari[646]: PassBook Pass download failed: The pass cannot be read because it isn’t valid.
I have generated the p12 file like you say at https://github.com/tschoffelen/PHP-PKPass#requesting-the-pass-certificate.
Finally, I can install the pkpass at Android devices.
I hope that you can help me.
Thank you!

Hi! It seems that something is wrong with the certificate embedded in the pass:
The passTypeIdentifier or teamIdentifier provided may not match your certificate, or the certificate trust chain could not be verified.

A few things to try:

Retry exporting the certificate from your keychain, and make sure you enter the same password you use during the export in the example code.
Make sure you have downloaded the WWDR certificate, it is readable and in the right place.
Make sure the team identifier and the pass type identifier in the example code match the values in the developer portal.

Hi!
Thanks for your answer. But I have done every step a lot of times and pkpass doesn´t work on iphone device. I don'´t know that try...

Did you try emailing the pass to yourself and opening it from the Mail app on your iPhone?

It works now :) I have generated the p12 certificate using other mac. You can close the issue.
Thank you!


[Docker] Create a process for creating CI docker images

There are many different workflows that need preinstalled tools for build, testing, or publishing stages.  This vary from project to project, some using python, ruby, cypress etc.  We need a way to keep these changes easy to track, and update.
Acceptance Criteria

[ ] Figure out how docker images should be built/consumed, e.g. Can we use dockerfiles directly in the build job?
[ ] Figure out the release management process, e.g. Jenkins job that can only be triggered by OpenSearch-Build maintainers?
[ ] Documentation for how to onboard to docker release process
[ ] Build tools/systems/processes for releasing a docker image.
[ ] Write a guide for how to work with new workflows and docker images
[ ] After reviewing this update the documentation for how this can be done

[Triage] Moving this to product backlog. We have enough context for this one.

We need to create a proper document before we move on to the implementation.

Refocused this item for CI docker images

Closing this issue. Please see updated documentation for CI docker images https://github.com/opensearch-project/opensearch-build/tree/main/docker/ci#build-ci-runner-docker-image-from-dockerfile


No more default protocol-redirect

as more apps are implementing NWC now it does not properly work anymore to open the correct app there. the default app is no longer the requested app.
We add the option for a button to open the nostr+walletconnect link, allow users to copy the NWC string AND also fire events on window and the window.opener to allow apps to listen to those events (especially in when apps open the NWC confirmation URL or use an embedded webview.
e.g. zapplepay
Missing:

[x] better UI to copy the connection string
[x] better UI with link to open the connection string

Proposed design here: https://www.figma.com/file/98bWDLs9dRVnYwW5ZVEqos/Nostr-Wallet-Connect?type=design&node-id=598-57403&mode=design

do we need a back button?

What does the back button do? the connection is already created. The normal browser button takes you back to the create connection screen but some of the form fields are not preserved (like the connection name).
Also, the connection is already created at that point, so going back is going to leave an unused connection for the user. I don't think that's very good.

I think the buttons don't look so good stretched like that. Maybe add a div to wrap the buttons with a sensible max-width?

do we need a back button?

I also felt at first but what Roland says makes sense, but it still expects us to click "Connections" from the navbar to go back which somehow doesn't feel right.
And also if we place a back button we might also want to change the wording "Pair with app to finalize" because it doesn't look like the creation is done yet and might confuse into thinking they're aborting it (which is definitely not the case)
(Another way to do is to delete the connection when back is pressed which is unnecessarily complicated)


Can't delete exported pointer with backspace

I pressed backspace many times here:

This is expected behavior. You have to remove a pointer by hovering over it and clicking on remove pointer, backspace just empties it.

Oops didn't mean to close this.


format() don't take a tuple as argument

Execution of your plugin on collectd 4.10 produce the following traceback :
IndexError: tuple index out of range

Ah, I missed that during review. Thanks!
@wt, you made a boo-boo! :)

@guikcd Good catch. Sorry, my change was kinda a rush job to get something working for a co-worker. I just wanted to share the work as I love being able to run these plugins as scripts as well.


Updates CLI to use '@octokit/rest' instead of 'github'.

What's the advantage of octokit over github?

There is no advantage other than that the old package name is no longer updated. They simply renamed their package and continued development under the new name.

I was trying to figure out how to retrieve a branch instead of a release and noticed they had updated and couldn't find documentation for the version we were using.

See also https://github.com/octokit/rest.js/releases/tag/v14.0.0 btw


Many property-based tests are broken

If you change the associativity property to always return false, you should see every law check fail. Instead, many of them continue passing, because they are never actually doing any work. This is due to failing to mix-in the correct traits into the test classes.
To fix this, find the tests that pass under a bogus associativity check, change them all so they fail, and then revert the associativity check. The reporter recommends that all the Algebird property-checks extend a single AlgebirdProperties trait to ensure that they all have the same mix-ins, to help avoid this issue in the future.

Thanks for finding this. @johnynek this has happened before. I think we need to find a way to use our test library that prevents this case of "the tests are quietly not being executed"

@non single base trait is a good start, we should definitely standardize everything to that and use only a single scalatest "style"

Looks like we hit this a while ago: https://github.com/twitter/algebird/issues/357

Closed by #584. TopPCTCmsLaws and BatchedLaws were the remaining broken tests.


Visual Studio Regression Test

Visual Studio Regression Test
A clear and concise description of the bug.
Dear All,
I have compiled OpenFast following the instructions in the manual ( https://openfast.readthedocs.io/en/master/source/install/index.html)
I am attempting to do a regression test; however, I get the following error:

It is telling me that there is a syntax error in manualRegressionTest.py.
Any suggestions on how to solve this problem?
Many Thanks
Ben

Hi @bvumba
That script is written for python3, so switching your python executable should solve this problem. Please let me know how that works for you.
Thanks
Rafael

Hi Rafael,
Thank you for your prompt response. That solved the problem and I was able to run the regression test. Unfortunately, the results of the test show that a number of items have failed.

Do you have any suggestions on why this is the case?
Thanks Ben

These tests could have failed for a variety of reasons as they are very sensitive to your environment. For example, using a different version of the intel compiler or mkl library than the one used to generate the baseline is a common cause. My suggestion is to plot the results and visually inspect the failing cases.
Since you've already run the cases, you can just generate the plots with this command:
python3 manualRegressionTest.py ..\build\openfast_x64_Double.exe Windows Intel 1e-5 -n -p

The -n means don't run the case and -p means generate the plots. By the way, you need matplotlib installed for this to work. After it finishes successfully, you'll have a html file in openfast\build\reg_tests which you can open in any browser and navigate through the failed test cases.

I'm closing this issue, but we can continue the discussion here. Feel free to reopen the issue if needed.

Hi,
Sorry to reopen this. However, despite trying numerous things I have not been able to make much progress. When I try to generate plots using the command you provided above it simply fails and no plots are generated. I have tried starting from scratch, including recompiling with a different Intel compiler and I end up in the same situation. Any help would be much appreciated.

Can you verify that you're using python3 and you have matplotlib properly installed?

Hi,
I'm running python 3.7

Matplotlib should be installed

Hmm I don't have a good guess at the problem yet, @bvumba. The manualRegressionTest.py script has a verbose option, -v, which will tell you the system command its running:
>>eagle@~/Development/openfast_intel/reg_tests (dev)$ python3 manualRegressionTest.py ../build/glue-codes/openfast/openfast linux intel 1e-5 -case WP_VSP_ECD -v
executing WP_VSP_ECD -- Using gold standard files with machine-compiler type linux-intel
../build/glue-codes/openfast/openfast ../build/reg_tests/glue-codes/openfast/WP_VSP_ECD/WP_VSP_ECD.fst > ../build/reg_tests/glue-codes/openfast/WP_VSP_ECD/WP_VSP_ECD.log

Using that information, you can either inspect the log file where the output is piped to (thats the argument in the command above after the >) or run the command manually in your cmd prompt and see what error you get.

Thanks,
After starting from scratch and using an older version of Visual Studio (2015) I have managed to generate the plots.  11 of the tests still fail as can be seen in the image below. However, after inspecting the plots for the failed cases they are a little off but still pretty close.

Good, I'm glad to hear that you were able to generate the plots!

Hello,
I am running a regression test on Windows with Visual Studio, however, the test has failed.

Any suggestions to solve this?


Fixed home page links being unclickable

References

Fixes #2942
Related #2844

Description
In the previous PR I did not realise that the ds-themed-configuration-search-page already used the ds-page-with-sidebar. In that PR I added an extra ds-page-with-sidebar around the ds-themed-configuration-search-page causing it's empty floating content column to block clickevents on the components underneath it. This PR refactors the home page to use the ds-page-with-sidebar inside the ds-themed-configuration-search-page instead, this is done with the new content projection selector searchContentTop.
Checklist

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes ESLint validation using yarn lint
[x] My PR doesn't introduce circular dependencies (verified via yarn check-circ-deps)
[x] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[x] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[x] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
[x] If my PR fixes an issue ticket, I've linked them together.

I've tested it and it works for me. Thanks @alexandrevryghem


Revisit label service usages for memoizing results

I think recently we changed FileEditorInput to no longer cache the result of name and description but to always compute it when needed. It seems the label service has become quite complex with regards to finding the correct formatter.
My assumption is that a label will only change if more formatters get registered, so can we maybe restore the cached labels and flush them when formatters change? This could even become a utility thing that everyone can adopt that wants this kind of caching.
The rationale here is that with many editors open, there can be a lot of calls to this service and I worry we do a bit too much each time because we do not trust the previous result.

Yes, we changed the FileEditorInput to not cache the results.
Droping the cache on new formatters makes sense. Assigning to next milestone and debt week to investigate then.

Thanks!


How to run with commands instead of dragging the app?

Hi I would like to know how to run a screensaver with commands instead of dragging the icon... Thank you!

I just saw that I can just add the name of the screensaver after the program name!

Thank you!


How to get the form fields to show them in the custumisez edit page ?

Description
I need a working way to get an array (or any other way) containing the form fields (which i already added them with the bread ) of my "reservations" content type cause I will need to do a lot of modification on the edit page of the "reservations " edit page

Please use the issue-template and follow the instructions in it (...questions are better asked in our Slack group)
Also this is basic Laravel/Eloquent knowledge and can be found in our views.


[tool_crash] String: <57 characters>

Command
flutter --no-color run --machine --device-id=9bbac2f5 --profile --dart-define=flutter.inspector.structuredErrors=true lib\main.dart

Steps to Reproduce

...
...
...

Logs
String: <57 characters>

[✓] Flutter (Channel stable, 3.7.5, on Microsoft Windows [Version 10.0.19045.2604], locale en-US)
    • Flutter version 3.7.5 on channel stable at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision c07f788888 (7 days ago), 2023-02-22 17:52:33 -0600
    • Engine revision 0f359063c4
    • Dart version 2.19.2
    • DevTools version 2.20.1

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at C:\Users\Huzaifa\AppData\Local\Android\sdk
    • Platform android-33-ext4, build-tools 33.0.1
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-9505619)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files\Google\Chrome\Application\chrome.exe

[!] Visual Studio - develop for Windows (Visual Studio Community 2022 17.4.5)
    • Visual Studio at C:\Program Files\Microsoft Visual Studio\2022\Community
    • Visual Studio Community 2022 version 17.4.33403.182
    ✗ Visual Studio is missing necessary components. Please re-run the Visual Studio installer for the "Desktop development with C++" workload, and include these components:
        MSVC v142 - VS 2019 C++ x64/x86 build tools
         - If there are multiple build tool versions available, install the latest
        C++ CMake tools for Windows
        Windows 10 SDK

[✓] Android Studio (version 2022.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-9505619)

[✓] VS Code, 64-bit edition (version 1.75.0)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (5 available)
    • SM J320V (mobile)            • 9bbac2f5      • android-arm    • Android 6.0.1 (API 23)
    • AOSP on IA Emulator (mobile) • emulator-5554 • android-x86    • Android 9 (API 28) (emulator)
    • Windows (desktop)            • windows       • windows-x64    • Microsoft Windows [Version 10.0.19045.2604]
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 110.0.5481.178
    • Edge (web)                   • edge          • web-javascript • Microsoft Edge 110.0.1587.57

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Flutter Application Metadata
Type: app
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: stable
Creation framework version: ffccd96b62ee8cec7740dab303538c5fc26ac543
Plugins
connectivity-3.0.6
connectivity_for_web-0.4.0+1
connectivity_macos-0.2.1+2
file_picker-5.2.5
flutter_plugin_android_lifecycle-2.0.7
image_cropper-3.0.1
image_cropper_for_web-1.0.3
image_picker-0.8.6+2
image_picker_android-0.8.5+6
image_picker_for_web-2.1.10
image_picker_ios-0.8.6+8
path_provider-2.0.12
path_provider_android-2.0.22
path_provider_foundation-2.1.1
path_provider_linux-2.1.7
path_provider_windows-2.1.3
shared_preferences-2.0.17
shared_preferences_android-2.0.15
shared_preferences_foundation-2.1.3
shared_preferences_linux-2.1.3
shared_preferences_web-2.0.4
shared_preferences_windows-2.1.3
sqflite-2.2.4+1

Closing this as a duplicate of https://github.com/flutter/flutter/issues/108812


Module x is not listed as dependency in package.json

I just started a new project using create-react-app name --scripts-version=react-scripts-ts - everything worked fine, until I added my tslint config and tslint-eslint-rules. I played around with adding and removing tslint-eslint-rules but I ended up getting the following errors as soon as I import node modules:
Module 'react' is not listed as dependency in package.json
Module 'react-dom' is not listed as dependency in package.json
... and so on, for each module imported from node_modules.

Yet all modules are listed in dependency.
I'm a bit stuck here after debugging for an hour. I'm also not sure if this is caused by ale or any tslint module. But as I reverted my configuration - the errors stayed.
:ALEInfo
 Current Filetype: typescript
Available Linters: ['eslint', 'tslint', 'tsserver', 'typecheck']
  Enabled Linters: ['eslint', 'tslint', 'tsserver', 'typecheck']
 Linter Variables:

let g:ale_typescript_tslint_config_path = ''
let g:ale_typescript_tslint_executable = 'tslint'
let g:ale_typescript_tslint_use_global = 0
let g:ale_typescript_tsserver_config_path = ''
let g:ale_typescript_tsserver_executable = 'tsserver'
let g:ale_typescript_tsserver_use_global = 0
 Global Variables:

let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%s'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'always'
let g:ale_linter_aliases = {}
let g:ale_linters = {}
let g:ale_open_list = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '>>'
let g:ale_sign_offset = 1000000
let g:ale_sign_warning = '--'
let g:ale_statusline_format = ['%d error(s)', '%d warning(s)', 'OK']
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(started) ['/bin/bash', '-c', '/Users/lumio/projects/company/project/sub-project/node_modules/.bin/tslint --format json -c ''/Users/lumio/projects/company/project/sub-project/tslint.json'' ''/var/folders/gx/7kv7ykbj4gv6shgwnfwdpzfm0000gn/T/vRQTnEw/1/index.tsx''']
(started) ['/bin/bash', '-c', '/Users/lumio/projects/company/project/sub-project/node_modules/.bin/tsserver']
(finished - exit code 2) ['/bin/bash', '-c', '/Users/lumio/projects/company/project/sub-project/node_modules/.bin/tslint --format json -c ''/Users/lumio/projects/company/project/sub-project/tslint.json'' ''/var/folders/gx/7kv7ykbj4gv6shgwnfwdpzfm0000gn/T/vRQTnEw/2/index.tsx''']

<<<OUTPUT STARTS>>>
[{"endPosition":{"character":30,"line":0,"position":30},"failure":"Module 'react' is not listed as dependency in package.json","name":"../../../../../../var/folders/gx/7kv7ykbj4gv6shgwnfwdpzfm0000gn/T/vRQTnEw/2/index.tsx","ruleName":"no-implicit-dependencies","ruleSeverity":"ERROR","startPosition":{"character":23,"line":0,"position":23}},{"endPosition":{"character":37,"line":1,"position":69},"failure":"Module 'react-dom' is not listed as dependency in package.json","name":"../../../../../../var/folders/gx/7kv7ykbj4gv6shgwnfwdpzfm0000gn/T/vRQTnEw/2/index.tsx","ruleName":"no-implicit-dependencies","ruleSeverity":"ERROR","startPosition":{"character":26,"line":1,"position":58}},{"endPosition":{"character":26,"line":7,"position":212},"failure":"there must be a space inside this paren.","fix":{"innerStart":212,"innerLength":0,"innerText":" "},"name":"../../../../../../var/folders/gx/7kv7ykbj4gv6shgwnfwdpzfm0000gn/T/vRQTnEw/2/index.tsx","ruleName":"space-in-parens","ruleSeverity":"ERROR","startPosition":{"character":26,"line":7,"position":212}},{"endPosition":{"character":32,"line":7,"position":218},"failure":"there must be a space inside this paren.","fix":{"innerStart":218,"innerLength":0,"innerText":" "},"name":"../../../../../../var/folders/gx/7kv7ykbj4gv6shgwnfwdpzfm0000gn/T/vRQTnEw/2/index.tsx","ruleName":"space-in-parens","ruleSeverity":"ERROR","startPosition":{"character":32,"line":7,"position":218}}]
<<<OUTPUT ENDS>>>

Pull the latest code. This error is thrown away for now. See this issue: #925

Thank you so much!  I already questioned my sanity 😁


Update/replace syntax error UI

Remove syntax error history and replace it with something that occupies less space (e.g., consider a "spell-checker" UI with squiggly lines under the problematic code and an error message displayed when user clicks on the code snippet).

Fixed in #384. Thanks @eledavi!


Added autopark_request & trigger_homelink documentation

I added these two features to the docs.

Coverage remained the same at 90.598% when pulling 475583bd8ea31a2cd4fc0f7f63e6afb85b361c89 on jsgoecke:master into 3062a73faea3f60edea94fa1207d8f01d47132f9 on timdorr:master.

Neither of these are complete, unfortunately. The difficulty in documenting them comes from the session setup for and the conditions that must be met (namely, you need to trick the car into thinking the keyfob is present).

Hi Tim,
I don't understand the tricking involved.  Would this be correct if there was the caveat that the key fob must be nearby?
Is it even possible to trick the car to think the fob is nearby?

Closing since Tesla switched to Websockets.


Package doesn't support null safety.

Bro, thanks for such a cool package.
As you may know, Null safety is default now and helps to tackle so many of the annoying errors.
I would love it if you can migrate it to null safety (I would but I have just started leaning dart very recently on my own so I don't understand a lot of the stuff)

I am currently working on null safety support. if you like the plugin kindly star this repo, it would be really motivative for me. thanks.

@TejasDhanda-L11 Just a quick update, I have just added the null safety feature and uploaded the new version of this plugin. So, once review is finished it'll be available for use.

That's so great man.
Just as a student, who reviews it (some kind of cool computer code which runs code with different values for variables in environment or other developers)?

right now I am the only man who's maintaining this plugin.


[rtl] Delete writeReadyForLsu & vrfReadyToStore.

Because the response to the index load/store unit memory access request is out of order, this PR is temporarily stopped.

writeReadyForLsu & vrfReadyToStore is needed to handle conflicts between lsu and mask unit


Fix Sortable Accordion Drag Handle Position

This update fixes the positioning of the drag handle in the sortable Accordion component. The drag handle should be positioned relative to the Section Title, not relative to the entire Section.
Before
After

@plbabin This is a bug fix against v3. Targeted your v3-fix-storybook branch for the merge.

thank you!!


fix test name outputted

closes https://github.com/PrismarineJS/mineflayer-test-api/issues/10

Tests are failing but for an unrelated reason.


Migrate to 'tokio' instead of 'tokio-core'?

The tokio crate exposes a different reactor handle that is more flexible. Currently, it is not possible to use reqwest with the new tokio crate, because Client needs a tokio_core::reactor::Handle.

This depends on the upstream work in hyper to eventually move from tokio_core to tokio. It mostly works on hyper master, but there's other related work happening before it will be released. Can be tracked here: https://github.com/hyperium/hyper/milestone/4

@seanmonstar Seems like a new version of hyper was released.

What is the status of this ticket, now that hyper 0.12 was released?

Oh, I see, #304.

In #307, this was completed, and will be part of 0.9.


RFM - isoplex

I DON'T Want To Become The Maintainer

[x] I have followed the Package Triage Process and I do NOT want to become maintainer of the package;
[x] There is no existing open maintainer request for this package;

Checklist

[x] Issue title starts with 'RFM - '

Existing Package Details
Package URL: https://chocolatey.org/packages/isoplex
Package source URL: https://github.com/dtgm/chocolatey-packages
Date the maintainer was contacted (in YYYY-MM-DD): 2021-12-13
How the maintainer was contacted: Email

Hello,
@FoxInTheClouds, the package seems to be unavailable now, do you have a link to the install ?
Thank you.


Add television support

iOS 12.2 beta 1 supports new HomeKit types for television

Thanks for adding Television support. I god an basic setup working. Can you give an example how to use / configure InputSource's?

Take a look func addInputSource(...) in _example/tv/main.go to see how to add an input source to a television accessory.

There is no tv example in your tv branch.

Now it is. ;)

THX

There is an bug, I don't know if it is a bug from hc or HomeKit / Home App.
You can't add input sources to an configured / already added tv accessory.
You need to remove and readd it, to get the new input work.


[Bugfix] Remove errant import in psbt_screens.py

Commit e9ad26bea9fe05f6c69b240de63bbbf174b3a7f3 introduced an unintended lzma import (blame VSCode automatic "quick fix" and a not careful enough visual inspection of diffs on what's being committed).
This errant import currently seems to be harmless because:

Raspi OS built-in python3.7 seems to have lzma compiled in (otherwise those screens would crash on the import).
SeedSigner OS python3.10.8 also seems to have lzma compiled in.

However, with #347 we're custom-compiling python3.10 on Raspi OS. And doing so without lzma support. So the import crashes the python file.

ACK
I confirm that importing lzma anything raises ModuleNotFoundError in my custom 3.10 build too.

ACK


.NET language support?

Is there support for all .NET languages?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c790425e-da4e-9a75-6a11-f72109ce8d6a
Version Independent ID: 09298e41-8f5a-c3c3-a849-8de67f8efba1
Content: Safely update interfaces using default interface members in C#
Content Source: docs/csharp/tutorials/default-interface-members-versions.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Are you asking if a C# language feature is supported by other languages?
Just want to make sure I understand your question.

@KathleenDollard and @cartermp would have to speak to the support for default interface members in VB and F#, respectively. There are also runtime considerations with @terrajobst can discuss.
Between now and .NET Core 3.0 release, we'll fill out the full story with other articles here and in the .NET Core section.

Consuming default interface methods are in our plans for Visual Basic.NET.
At least initially, we plan to support consuming, but not creating them. There are higher priority features for Visual Basic.NET.

Are you asking if a C# language feature is supported by other languages?
Just want to make sure I understand your question.

I am referring to the "default interface methods" feature specifically.
Thanks.

Consuming default interface methods are in our plans for Visual Basic.NET.
At least initially, we plan to support consuming, but not creating them. There are higher priority features for Visual Basic.NET.

Thanks Kathleen. Please where may one find the list of the higher priority features planned for Visual Basic.NET?
Best regards!

I'm keeping this open to address the correct location for information on F# and VB support. Once we provide that info, I'll close this as the current article won't address those languages.

Closing.


Migrate setup-cfg-fmt to v2.3.0

Proposed change

This PR migrates setup cfg fmt to v2.3.0 as per done automatically with tox command.
Type of change

[ ] New country/market holidays support (thank you!)
[ ] Supported country/market holidays update (calendar discrepancy fix, localization)
[ ] Existing code/documentation/test/process quality improvement (best practice, cleanup, refactoring, optimization)
[x] Dependency upgrade (version update)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (a code change causing existing functionality to break)
[ ] New feature (new python-holidays functionality in general)

Checklist

[x] I've followed the contributing guidelines
[x] This PR is filed against beta branch of the repository
[x] This PR doesn't contain any merge conflicts and has clean commit history
[x] The code style looks good: make pre-commit
[x] All tests pass locally: make test, make tox (we strongly encourage adding tests to your code)
[x] The related documentation has been added/updated (check off the box for free if no updates is required)

coverage: 99.991%. remained the same when pulling 553125d7084fd8fb03a989f431fcd0f279d18c18 on PPsyrius:Migrate-setup-cfg-fmt-to-v2.3.0 into 3512c9b66b41a4652953c361c668d7bd6323de01 on dr-prodigy:beta.

It has been merged into beta. Thank you!


Manage localization via cooperation system

Summary
We can use a cooperation system like crowdin or transifex to cooperate with the localization of response and timeline text in raidboss module. (Or even the whole project?)
Then we can make it easier for those who cannot code well to help with the translation (without modifying the js file).
These two systems are both free for open-source projects (crowdin, transifex).
Current Progress
I have a demo project to export/import the responses/timelines from/to the js files, which is mostly designed for CN localizations:

Project: raidboss_translator
Sheet: exported sheet

Do you think it's necessary and more efficient for later maintenance?

Sorry for the delay in responding here.
I have to admit that I am a little skeptical of the overhead of this approach.  Do you feel that there are many people who would be contributing to cactbot translations but aren't because they don't know JavaScript? I would hope that it is not too hard to translate things in JavaScript files, but I am somewhat biased here because I am a programmer.  But, I think the presence of somebody like VanSlanzar who is not a programmer speaks well to other people being able to pick it up and copy surrounding code.
One very big downside to having things in a file is that there is already confusion about what a particular mechanic means, and having translations in separate sheets and projects farther away from the code will make it harder to understand what "dorito stack" or "pepperoni" mean.
I think the hard part of cactbot translations is the replacement restrictions (collisions, tests, etc) and general regex knowledge.  I don't think a separate translation sheet will help with either of these problems.
One thing that I think has helped translations is to have resources/responses.js as well as ui/raidboss/common_translation.js.  I think another thing that will help along the lines of what @MaikoTan asked for is to do something like this https://github.com/quisquous/cactbot/issues/1307#issuecomment-608283837 for common translations.  I personally don't think it's worth doing this for absolutely everything, but just things that get used multiple times.  That will just cut down on the total number of translations that are needed overall.
Sorry for the skepticism, but I am just not convinced that an approach like this solves enough problems in my mind to be worth the extra cost to do it.

Yes, this approach is more useful to translate old stuff since most of them don't have translations for cn.
Now cactbot is more frequently used by not only the EU/NA but also players & devs from other clients, so updating the translation as patch releasing is enough.

I'm in agreement with quisquous here. The solutions noted in the OP (to my mind at least) seem more geared toward projects with a constantly expanding base of content requiring translation. For cactbot, the "base translated content" is going to be relatively slow to update, and the benefit of these outside solutions would be small. In this situation, I think the solution MaikoTan and I proposed might take less overall overhead. The way such a file would be structured should be reasonably understandable even by non-programmers with a little explanation. Obviously translations that take parameters might not be so easy, but simple stuff like "Stack With Partner" ought to be doable for just about anyone.
(Additionally, if in the future we do need to convert over to a dedicated translation CMS, it should in theory be simple enough to extract the translation functions and returned objects.)

@quisquous  I want to recall this issue because I found that crowdin they are kind, and we can easy to do a free open source request. (I have sent some emails to ask them and they said only if the repo owner would complete the request form, then they could offer this service.)
At lease we can host our all the documents onto crowdin and localize it easier?

@quisquous  I want to recall this issue because I found that crowdin they are kind, and we can easy to do a free open source request. (I have sent some emails to ask them and they said only if the repo owner would complete the request form, then they could offer this service.)
At lease we can host our all the documents onto crowdin and localize it easier?

Thanks for bringing this up again.  I think I am still not sure that something like this is a good fit for raidboss translations, but doc translations are maybe a different story.  I will take another look at these, thank you!

Thanks for bringing this up again.  I think I am still not sure that something like this is a good fit for raidboss translations, but doc translations are maybe a different story.  I will take another look at these, thank you!

I also looked at gitlocalize a little bit as well.  I think that might be a better fit for what I am looking for (keeping markdown doc translations up to date, more lightweight).  crowdin and transifex seem like huge enterprise solutions that I need to look closer at to understand how they would fit well.

I also looked at gitlocalize a little bit as well.  I think that might be a better fit for what I am looking for (keeping markdown doc translations up to date, more lightweight).  crowdin and transifex seem like huge enterprise solutions that I need to look closer at to understand how they would fit well.

Just found that crowdin renewed there pricing and now you can host unlimited strings on it with a free tier.
Compared different localisation website, I still recommend crowdin for localising the documents.


import 'uno.css'  SyntaxError: Unexpected keyword 'import' in Safari

I use Vite on development mode,  and open project in my Iphone10 Safari , when I import 'unocss', Safari get Error: SyntaxError: Unexpected keyword 'import', why?
I found the reason for the error is this sentence:
import 'uno.css'

How to solve this problem

https://github.com/unocss/unocss/issues/1804#issuecomment-1298094103


Process multipart upload

In some cases, the received files must be immediately redirected to another service. For example, forward to S3. To do this, I added the ProcessMultipartUpload function, which accepts func(part *multipart.Part) error as input, where parts of formdata are transferred as they are received. Example updated accordingly.
This pool request is based on https://github.com/black-06/grpc-gateway-file/pull/18, which is currently not in the master.

@black-06 I have resolved all conflicts with the master. Can you see the changes?


create chrome extension that allows quick publish to spee.ch

this shouldnt be to difficult with the amount of plugins out that do this that we could most likely work off of to get it done fast


remove old ROS implementation

Coverage decreased (-0.1%) to 93.824% when pulling c268950174f488d9235d906422026a06e0b8b57f on phobson:remove-old-ros into b53a6a3f4bf9cf07c074bf3a800fe460ff166400 on Geosyntec:master.


Add pair_plot_focus

Talking with @daniel-saunders-phil he mentioned he often wanted to generate pair plots of a specific variable against several others. I think we could have a function that makes that easy (and paves the way with visuals and computation for plot_pair once we have the PlotMatrix manager) because as we compare multiple variables to always the same one the facetting/mapping logic is the one in PlotCollection.
I was thinking the API would be similar to a regular plot with dt, group, var_names... and then a target (or similar) name where you provide either a string (var_name in dt input) or a DataArray.

pseudo example
from arviz_base import load_arviz_data
from arviz_base.labels import BaseLabeller, NoVarLabeller
import arviz_plots as azp

azp.style.use("arviz-clean")
plt.rcParams["font.size"] = 8  # clean theme sets font too big

idata = load_arviz_data("centered_eight")
target_name = "mu"
pc = azp.PlotCollection.wrap(
    idata.posterior.ds[["theta"]],
    cols=["school"],
    col_wrap=4,
    plot_grid_kws={"figsize": (8, 3), "sharey": True},
)
pc.map(
    azp.visuals.scatter_x,
    "samples",
    y=idata.posterior[target_name],
    marker=".",
    alpha=.4,
    edgecolor="none",
)
pc.map(
    azp.visuals.labelled_title,
    "title",
    subset_info=True,
    labeller=NoVarLabeller(),
    ignore_aes={"color"},
    size=8,
)

pc.viz["chart"].item().suptitle(f"Pair plots of theta subsets vs {target_name}");

I spent some time playing with this and it's really handy. I wanted to add two features but couldn't find the path forward. How might I color different chains differently? Also, how might I flag divergences?


Clean the autoload config

Tests don't need to be autoloadable when installing the package as a dependency, only when running the testsuite

Thanks !


Couldn't find package "<EMAIL_ADDRESS>required by "<EMAIL_ADDRESS>on the "npm" registry.

Couldn't find package "@ storybook/<EMAIL_ADDRESS>required by "@ storybook/<EMAIL_ADDRESS>on the "npm" registry.
Steps to reproduce
open terminal, run yarn
yarn install v1.6.0
$ node ./preinstall-check.js
[1/4] Resolving packages...
error Couldn't find package "<EMAIL_ADDRESS>required by "<EMAIL_ADDRESS>on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this comman

storybook/react 3.4.3
storybook/addon (almost every addon) 3.4.3
Affected platforms
                          ./+o+-       jacoahmad@JKENGHA0071927
                  yyyyy- -yyyyyy+      OS: Ubuntu 16.04 xenial
               ://+//////-yyyyyyo      Kernel: x86_64 Linux 4.13.0-38-generic
           .++ .:/++++++/-.+sss/`      Uptime: 53m
         .:++o:  /++++++++/:--:/-      Packages: 2301
        o:+o+:++.`..```.-/oo+++++/     Shell: zsh 5.1.1
       .:+o:+o/.          `+sssoo+/    Resolution: 1366x768
  .++/+:+oo+o:`             /sssooo.   DE: Gnome
 /+++//+:`oo+o               /::--:.   WM: GNOME Shell
 \+/+o+++`o++o               ++////.   WM Theme: Adwaita
  .++.o+++oo+:`             /dddhhh.   GTK Theme: Arc-Dark [GTK2/3]
       .+.o+oo:.          `oddhhhh+    Icon Theme: Oranchelo
        \+.++o+o``-````.:ohdhhhhh+     Font: Cantarell 11
         `:o+++ `ohhhhhhhhyo++os:      CPU: Intel Core i7-7820HQ CPU @ 3.9GHz
           .o:`.syhhhhhhh/.oo++o`      RAM: 6344MiB / 15686MiB
               /osyyyyyyo++ooo+++/
                   ````` +oo+++o\:
                          `oo++.

Update
Downgrading to 3.4.2 fixes the issue

WHUT
The correct package name id @storybook/components.
the 3.4 package.json for addon-actions:
{
  "name": "@storybook/addon-actions",
  "version": "3.4.4",
  "description": "Action Logger addon for storybook",
  "keywords": [
    "storybook"
  ],
  "homepage": "https://github.com/storybooks/storybook/tree/master/addons/actions",
  "bugs": {
    "url": "https://github.com/storybooks/storybook/issues"
  },
  "license": "MIT",
  "main": "dist/index.js",
  "jsnext:main": "src/index.js",
  "repository": {
    "type": "git",
    "url": "https://github.com/storybooks/storybook.git"
  },
  "scripts": {
    "prepare": "node ../../scripts/prepare.js"
  },
  "dependencies": {
    "@storybook/components": "3.4.4",
    "babel-runtime": "^6.26.0",
    "deep-equal": "^1.0.1",
    "glamor": "^2.20.40",
    "glamorous": "^4.12.1",
    "global": "^4.3.2",
    "make-error": "^1.3.4",
    "prop-types": "^15.6.1",
    "react-inspector": "^2.2.2",
    "uuid": "^3.2.1"
  },
  "peerDependencies": {
    "@storybook/addons": "^3.3.0",
    "react": "*",
    "react-dom": "*"
  }
}

@Hypnosphi @shilman since you do most of the 3.x release work I think, any idea what's going on here?

@ndelangen @Hypnosphi @shilman, it happens again even with 3.4.2
error Couldn't find package "<EMAIL_ADDRESS>required by "<EMAIL_ADDRESS>on the "npm" registry.

Update:
I use 4.0.0 Alpha 6 to be able to continue on my work, seems like there's some sort of dependency typo on the mentioned version.

1 this package is failing to install from CircleCI today,

error An unexpected error occurred<EMAIL_ADDRESS>ESOCKETTIMEDOUT”.

Also trouble installing locally:
yarn add @storybook/addon-backgrounds
yarn add v1.3.2
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...

There are no network connection issues for me, or Circle, or for any other modules in a large project, just this one

@mosesoak When I try to access<EMAIL_ADDRESS>it just works, I get a tgz download.

Most likely npm had a outage

Can we close this?