Add data on PEPs in Chile

Closes #502 (continuing #503).
@jbothma you wrote that:

We will create position names like CONCEJAL, MUNICIPALIDAD DE PENCO by concatenating values later, but categorising positions with all these combinations might be impractical, so consider maintaining an allow list or deny list in code. The answer might be that all these people are politically-exposed persons - we haven't dug into it, so consider that. Propose a draft list if that is the suggested approach.

Indeed not everyone in the original dataset is a PEP. One example are inspectors[^1] but there are several others.
I can take a closer look when I'm filling the dataset metadata, but for now I could use some feedback about the approach for the allow/deny list.
I opted for explicitly classifying the 511 unique positions (without organizations) in datasets/cl/info_probidad/cl_info_probidad.yml as pep or not so that it's easy to flag for review if (more when actually) the domain of the positions changes and the classification must be reviewed.
[^1]: There is a published manual about law 20.880 with information about who needs to provide the declarations. One example are inspectors
> Sujetos obligados a efectuar declaraciones de intereses y patrimonio
>
> [...]
>
> i) Los funcionarios que cumplan funciones directas de fiscalización. Se entenderá que un funcionario cumple funciones directa de fiscalización cuando dentro de sus funciones permanentes contemplen actividades de inspección directa o le competa intervenir directamente en procedimientos administrativos sancionatorios que no correspondan a procedimientos disciplinarios internos (artículo 2°, N° 9) del Reglamento).

which are not considered PEPs neither by [OpenSanctions](https://www.opensanctions.org/docs/pep/methodology/) nor [Chile](https://www.uaf.cl/legislacion/politica.aspx).

Thank you! This looks great.
I didn't link to this PR yet because it's not merged so I didn't want to make it part of the task yet, but then I forgot that it might help with this case which wasn't in the original advertised task - sorry!
What I would propose is that you keep the ones that are categorised is_pep: true and call categorise(...) on them with is_pep=True, while calling it with is_pep=None for the rest. It looks like there are some that might well be PEPs but you don't need to get too bogged down in that - it's just handy that you'll have a number of probable PEPs to see in your output data.
Please bear with me, this categorise stuff is newish and I'm still figuring out how to make it part of the process for other crawler authors!

What I would propose is that you keep the ones that are categorised is_pep: true and call categorise(...) on them with is_pep=True, while calling it with is_pep=None for the rest. It looks like there are some that might well be PEPs but you don't need to get too bogged down in that - it's just handy that you'll have a number of probable PEPs to see in your output data.

I've changed this in https://github.com/opensanctions/opensanctions/pull/512/commits/2b64a00f6f95e445f69e3ee638f0044cd11e60c5, but when we start creating the positions by concatenating Cargo and Institucion we will go to 2417 combinations and if I understand correctly they will all end up in the database. Wasn't the ideia to categorise only by Cargo? Or should I send the positions to the database without the organization?

Got it now! Thanks for the explanation. I have one small question but after then that this is ready for review.
In terms of the data priorities  in the csv that we used as source there is not information about relatives or close associates, but they are likely to be available in the other serialization formats (they are timing out).

I think relatives and close associated would be very helpful. Not needed right now, but I'll add it to the backlog so we can dig into it when it's a priority.
Generally, we aim for crawlers not to take more than 6 hours, but ideally less than 4 hours of effrort. So if RCAs and/or financial interests which fit our data model can be included within that time, that's awesome.


Local Authentication for IPsec Mobile Client VPN with EAP-MSCHAPV2 Fails

Note: This issue may be similar to 4438, but I have more information.
Describe the bug
I have created an and set up an IPsec VPN for mobile clients with EAP-MSCHAPV2 authentication. Authentication fails for local users who appear like they should have access.
To Reproduce

Create a local user in OPNsense user with a PSK defined, make them a member of a group called 'vpn'.
Enable IPsec Mobile Client Support and set Enforce local group to the 'vpn' group.
Set up an IPsec tunnel for the mobile clients to use, with EAP-MSCHAPV2 for authentication on Phase 1.
Attempt to connect and authentication will fail. Something akin to this will be logged in the IPsec Log File:
2021-01-17T21:54:00 | charon[56124] | 09[IKE] <con1\|19> no EAP key found for hosts 'CN=blah.example.com' - 'username'

Expected behavior
I would expect that a user in the 'vpn' group would have access to the IPsec Mobile Client connection using its password via EAP-MSCHAPV2.
Additional context
In /usr/local/etc/ipsec.secrets I found the username listed, but with a PSK. This appears to be why EAP was failing. If I manually add an entry (eg: username : EAP "password") and reload the secrets (ipsec reload) then authentication succeeds.
If I delete the user from OPNsense and create Pre-Shared Key under IPsec with the username as Identifier, password as Pre-Shared Key and Type as EAP then authentication will succeed.
A few extra notes:

After deleting the user from OPNsense, and before adding it as a standalone PSK, the PSK for this user was still present in /usr/local/etc/ipsec.secrets.)
If the user is created without a PSK, there will be no PSK (nor EAP entry) in /usr/local/etc/ipsec.secrets and authentication will still fail.

Environment
OPNsense 20.7.7_1-amd64
FreeBSD 12.1-RELEASE-p11-HBSD
OpenSSL 1.1.1i 8 Dec 2020

eap-mschapv2 authentication has no direct relation with user management as far as I know (it needs the raw password to work), see https://docs.opnsense.org/manual/how-tos/ipsec-rw-srv-mschapv2.html#step-4-add-ipsec-users
At a first glance the system works as described in this case. (only confusing part is that you can still set a psk under the user, we should probably migrate those into the psk option at some time to avoid confusion.

eap-mschapv2 authentication has no direct relation with user management as far as I know (it needs the raw password to work), see https://docs.opnsense.org/manual/how-tos/ipsec-rw-srv-mschapv2.html#step-4-add-ipsec-users
At a first glance the system works as described in this case. (only confusing part is that you can still set a psk under the user, we should probably migrate those into the psk option at some time to avoid confusion.

Ahhhhh, got it. Because of how things were listed it looked like it should work, especially as many clients consider the EAP-MSCHAPV2 credentials a username/password and not a PSK. But I can also see how it is that.
Sounds like if I want something more traditional username/password then I need to use RADIUS as an intermediary.
Thanks!

Ahhhhh, got it. Because of how things were listed it looked like it should work, especially as many clients consider the EAP-MSCHAPV2 credentials a username/password and not a PSK. But I can also see how it is that.
Sounds like if I want something more traditional username/password then I need to use RADIUS as an intermediary.
Thanks!

close issue?

close issue?

Sorry! Sure, closed.

Sorry! Sure, closed.


ionic -v now also reports version of the current project (if applicable)

ionic -v and ionic --version now also return the name and version of the current project (if there's a package.json in the current directory.
Example repsonse is
Ionic: 1.6.1
Current project (MyLovelyAppName) : 0.1.1

After discussing with the team, the ionic info command handles exactly what you're asking for, and with a lot less effort to get it. The ionic -v is following most CLI conventions of simply providing the version only.
For now, we've decided to put this one on the back burner and focus on more pressing matters.
Thank you for the contribution.


Group required properties at the top of property tables

Currently, we list properties alphabetically, which can make it harder to see the required ones -- for example:
https://www.pulumi.com/docs/reference/pkg/aws/cognito/userpool/#userpoolschema

We should group all required properties together at the top of property tables, and keep them sorted alphabetically within their groups.

@sean1588 can this be closed now?

@sean1588 can this be closed now?

yes we can close.


Show DroidKaigi logo instead of Toolbar text

Kind (Required)

Improvement

Overview (Required)

Links

https://www.figma.com/file/IFlrbfmBSdYvUz7VmSzfLV/DroidKaigi_2021_official_app?node-id=0%3A1

I'll try this issue :raising_hand:

Thanks! Assigned 👍


[REVERT][REVERRT] Add group and user in dockerfile to run container as unprivileged

PR to re-apply @Singebob's changes originally released in #495.
There was an issue that caused breaking changes for users, as raised in #498 and #499
Before merging, I need to either fix this, or update the documentation appropriately.

In my testing to run Dashy in my Kubernetes cluster, I can't get the app to run as a non-root user.  There are two main issues:

Default port is 80, which is not usable by a non-root user.  Easy to fix by setting the PORT variable to a higher number (8080 works).
Part of the startup process does an rmdir /app/dist.  If I run the code as a non-root user, it doesn't have the permissions to do this and the startup fails.  I don't have a workaround for this one.

I'm not sure the changes in this PR would fix #2.

In my testing to run Dashy in my Kubernetes cluster, I can't get the app to run as a non-root user. There are two main issues:

Default port is 80, which is not usable by a non-root user.  Easy to fix by setting the PORT variable to a higher number (8080 works).
Part of the startup process does an rmdir /app/dist.  If I run the code as a non-root user, it doesn't have the permissions to do this and the startup fails.  I don't have a workaround for this one.

I'm not sure the changes in this PR would fix the second issue.

Did your 2nd point ever get resolved? I have this same behavior on 3.1.1 when setting runAsNonRoot
@bmonty


EdiSegment with list of EdiElement

Hi,
I have issue with Segment exist list of values.
Example:
ATR+NEW+PRIO:N'
ATR+NEW+TGIC:465+TGNO:716073+TGPC:SVX'
ATR+NEW+ACCS:A+BGCL:Y+BRDP:KBP+OFFP:TSE+PRIL:N'

I want get List of values like:
[EdiSegment, EdiPath("ATR")]
public class Main
{
     List<Information> Informations { get; set; }
}

Attention edivalue exist n counter
public class Information
{
    [EdiValue("X(4)", Path = "ATR/n/0")]
    public string Code{ get; set; }

    [EdiValue("X(256)", Path = "ATR/n/1")]
    public string Value{ get; set; }
}

1st Main:
Information[0].Code = PRIO
2nd Main:
Information[0].Code = TGIC
Information[0].Code = TGNO
Information[0].Code = TGPC
3rd Main:
Information[0].Code = ACCS
Information[0].Code = BGCL
Information[0].Code = BRDP
Information[0].Code = PRIL

If I understand this correctly you need to bind a repeating Element to a list of elements.
This feature is not supported yet. As a workaround you can make multiple subclass of Information or multiple properties of Code and Value inside the Main class (ATR).
[EdiSegment, EdiPath("ATR")]
public class Main
{
     [EdiElement, EdiPath("ATR/0")]
     Information Information { get; set; }
     [EdiElement, EdiPath("ATR/1")]
     Information1 Information1 { get; set; }
     [EdiElement, EdiPath("ATR/2")]
     Information2 Information2 { get; set; }
}
public class Information
{
    [EdiValue("X(4)", Path = "ATR/0/0")]
    public virtual string Code{ get; set; }

    [EdiValue("X(256)", Path = "ATR/0/1")]
    public virtual string Value { get; set; }
}
public class Information1 : Information
{
    [EdiValue("X(4)", Path = "ATR/1/0")]
    public virtual string Code{ get; set; }

    [EdiValue("X(256)", Path = "ATR/1/1")]
    public virtual string Value { get; set; }
}
public class Information2 : Information
{
    [EdiValue("X(4)", Path = "ATR/2/0")]
    public virtual string Code{ get; set; }

    [EdiValue("X(256)", Path = "ATR/2/1")]
    public virtual string Value { get; set; }
}

Related to #105

Checkout this example https://github.com/indice-co/EDI.Net/blob/master/test/indice.Edi.Tests/Models/EdiFact_Issue121_ElementList.cs
and I will be posting a beta release 1.9 soon

Hi,
Thank you works good. When you release new version?

Just published 1.9 to nuget

I used in project. And have problem.
ATR+NEW+BRDC:J+BRDS;B+BRDT:S+BRDY:DGR
[EdiSegment, EdiPath( "ATR")]
public class Main
{
[EdiPath("ATR/*")]
public List Informations { get; set; }
}
[EdiElement]
public class Information
{
    [EdiValue("X(4)", Path = "*/*/0")]
    public string Code { get; set; }

    [EdiValue("X(4)", Path = "*/*/1")]
    public string Value{ get; set; }
}

I Have error.
First item can't get. And the latest not show and some values is incorrect.
I think because, first element doesn't exist a value

You have to give me a complete sample and a model. Because for this transmission the feature works as expected and binds everything.
UNB+UNOD'
UNH+000001'
ATR+NEW+PRIO:N'
ATR+NEW+TGIC:465+TGNO:716073+TGPC:SVX'
ATR+NEW+ACCS:A+BGCL:Y+BRDP:KBP+OFFP:TSE+PRIL:N'
UNT+3'
UNZ+1'

Here is the test
https://github.com/indice-co/EDI.Net/blob/ff3d9ee2dc32b93ac801de4fee0304a424257da6/test/indice.Edi.Tests/EdiTextReaderTests.cs#L923

I saw. Try use that.
public class EdiFact_Issue121_ElementList
{
public Message Msg { get; set; }
    [EdiMessage]
    public class Message
    {
        [EdiCondition("NEW", CheckFor = EdiConditionCheckType.Equal, Path = "ATR/0/0")]
        public List<Attribute> Attributes { get; set; }

        [EdiCondition("V", CheckFor = EdiConditionCheckType.Equal, Path = "ATR/1/0")]
        public List<Criteria> Attributes1 { get; set; }
    }

    [EdiSegment, EdiPath("ATR")]
    public class Attribute
    {
        [EdiPath("ATR/*")]
        public List<Information> Infos { get; set; }
    }

    [EdiElement]
    public class Information
    {
        [EdiValue("X(4)", Path = "*/*/0")]
        public string Code { get; set; }

        [EdiValue("X(256)", Path = "*/*/1")]
        public string Value { get; set; }
    }

    [EdiSegmentGroup("ATR")]
    public class Criteria
    {
        [EdiValue("X(100)", Path = "LTS/0", Mandatory = true)]
        public string Value { get; set; }
    }
}

UNB+UNOD'
UNH+000001'
ATR+NEW+PRIO:N'
ATR+NEW+TGIC:465+TGNO:716073+TGPC:SVX'
ATR+NEW+ACCS:A+BGCL:Y+BRDP:KBP+OFFP:TSE+PRIL:N'
ATR++V'
LTS+2'
UNT+3'
UNZ+1'

@dinmukhamed09 I have revisited the case and finally figured this out!! Now the deserializer can work even the last case! check the Test here

I will post a new version v1.9.4


Escape # such that solutions don't render it as headings

Comments get rendered as headings, so we'll need to escape them and modify the notebook preprocessor to search the regex \* and replace with *

No regex necessary, s.replace('\\*', '*') should be enough.


Improving the cards design

resolved the issue #21 and #23
made it like:

Is it fine now?

Let's Merge

Yeah I will be resolving the dark mode implementation issue #23  in a separate PR. You can merge and close this PR @soumali28 .


Added new diagnostics message to clarify error for type guards

Fixes #6540
New diagnostics message "A type guard's type must be assignable to its parameter's type." number 2677
is now using in chain report to clarify vague error message for type guards.

Hi @Vinatorul, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

:+1: after Dan's comments

This looks great @Vinatorul. I just had a few style suggestions. We think you should change the error message as I've brought up above.

@DanielRosenwasser thank you! After tests finish I will amend all changes.

@DanielRosenwasser done


Publisher API

AFAICS, the routing key is derived from the ?queue query-param.
This means you need one publisher per routing key, while my design has a very dynamic routing key that is unlikely to repeat more than a few times per week.
I would like to introduce the routing key to publish(). I can create a PR, but I was debating with myself over semantics:
->publish('body',%headers,'routing_key') vs
->publish('body', { headers => %headers, routing_key => 'some.routing.key' })
The second one opens up for more flexibility for other options needed.

I'll opt for following signature:
publish($body!, \%headers?, *@params)

which will allow to call it like this:
->publish($body, { header => 'value' }, routing_key => 'something',
                                        mandatory => 1, immediate => 0);
->publish($body, routing_key => 'something');
->publish($body, { header => 'value' });
->publish($body);

With following rules:

if $body is hashref default content_type is set to application/json and $body is encoded to JSON string, otherwise it will be passed as-is,
if second argument is hashref it will be merged with default headers, replacing any pre-existing values, if it's defined but not a hashref it will be treated as below,
any other (slurpy) arguments will be treated as key/value pairs and merged with AMQP publish method default parameters

What do you think?

I'm fine with that!

If you can, please write a PR - I don't have much spare time lately

The signature needs more work. I like the easy approach of using URL parameters, however they are not sufficient for a publisher as it can, for instance, publish to multiple exchanges.
Hows this for an API, straight from Net::AMQP::RabbitMQ:

URL parameters for exchange and routing key are defaults (if we are to keep them)
publish($body, $routing_key, %options, %props)

Query params could still be used for defaults, but they are just as easily added with a helper.
I'm a bit time constrained as well, but I have started working on the code.

@tyldum Just make it flexible.

In a5e148fc9c24a3612c6d37cf5d34dc1845200f62 I've changed publisher code to use ?routing_key= query parameter instead of ?queue=

Resolved in 5a7cf91


Rotate globe on web

Tried to use controller.setAutoRotation(...) but got an error in my console saying that the function doesn't exist. Are there any changes to the original rotation API when moving from v1.x to v2.x?
I'd really like a rotation function to add to the globe. Any help appreciated :)
Thank you!

@rish-16 Auto rotate is added in v2.2.2. I will update build/ folder. In the meantime, can you try the one from CDN<EMAIL_ADDRESS>and let me know how it works? Thanks.

Great, thanks! Will check it out :)


PS: Push cert chain to local CS

Fixes #2056

This change is

go/lib/infra/modules/trust/trust.go, line 356 at r1 (raw file):

}

func (store *Store) newChainValidatorForwarding(validator *trc.TRC) ValidateChainFunc {

Please add the comment specifying the limitation of this solution that we discussed offline (or reference an issue stating it).


Dictionary order influences parseability

Hello everyone,
I'm currently using rustpython to embed an existing python library into a piece of software and I think I might have found a bug.
The goal is to create a dictionary with String keys and Callable entries somewhat like this:
new_dict = {
    **{x: lambda y: y + 2 for x in ["a", "b", "c"]},
    "d": lambda x: x +1,
}

If I try to run this code through the rustpython executable, I get the error message:
thread 'main' panicked at /home/valentinbuck/.cargo/registry/src/index.crates.io-6f17d22bba15001f/rustpython-codegen-0.3.0/src/compile.rs:311:9:
assertion failed: table.sub_tables.is_empty()
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

This differs from the error I get when I  run this code through a VM I constructed myself:
thread 'main' panicked at /home/valentinbuck/.cargo/git/checkouts/rustpython-f8ef4d934ac33cd8/e6c6f96/compiler/codegen/src/compile.rs:481:57:
The symbol must be present in the symbol table, even when it is undefined in python.

However, when I swap the two lines in the dict, it compiles and runs fine:
new_dict = {
    "d": lambda x: x +1,
    **{x: lambda y: y + 2 for x in ["a", "b", "c"]},
}

I tried looking through the parser to find the place where this happens but had no luck.
Do you have an idea where I could start or what is going wrong?
Thanks a lot for your project!

Almost forgot: Both variants compile fine through CPython.

Thank you for the report!
Somehow, x in "d": lambda x: x +1, doesn't exist in symbol table. How about starting comparing how the symbol put in or not put in by the order?


physicalRootPath in multiple configurations being overwritten

Do you want to request a feature or report a bug?
I think it's a bug, unless it was intended, in which case I'd like it added as a feature.
What is the current behavior?
I have two Unicorn.Configs in my Include/Unicorn directory, each with a different physicalRootPath, but all the serialization is done to only one of the paths.
If the current behavior is a bug, please provide the steps to reproduce.

Create two different copies of Unicorn.Configs.Default.example

e.g.:
Unicorn.Configs.A.config
Unicorn.Configs.B.config

Set the name to two different names
e.g.:
in config A:  "FolderA"
in config B:  "FolderB"
Set the targetDataStore physicalRootPath to a different folder for each configuration.

e.g:
in config A:  C:\FolderA
in config B:  C:\FolderB

Chose a different Sitecore path to sync in each
e.g.:
in config A:
in config B:
Sync.

All serialization files turn up in FolderB!
What is the expected behavior?
That everything included in A goes to FolderA and everything included in B goes to FolderB.
Please mention your Sitecore version and Unicorn version.
Sitecore 8.2, Unicorn <IP_ADDRESS>

I wanted to give some more information.
I thought I could get around this by putting the targetDataStore physicalRootPath in one place, and then not specifying it in the other configuration files. But this made it use the default physicalRootPath that was specified in the Unicorn.config, which is expected. This leads me to believe that this is a bug, because if it falls back to the path in  when not specified, then one configuration should not have any affect on another.

Can you share the exact configurations you're using, so I can inspect them?

As I was attaching my configs I retested one more time and noticed that the problem may not be what I originally thought. I think that it only looked that way. I had not realized there were multiple "Initial Serialization" buttons, so I was only hitting the first one. I don't know why I didn't notice that the items of the second configuration file weren't being written at all and assumed that they were all being written to the same place. Also, the fact that one configuration had a physicalRootPath that was a parent of the other two didn't help.


RuntimeError: [Error thrown at core/conversion/conversionctx/ConversionCtx.cpp:149] Building TensorRT engine failed

🐛 Bug
RuntimeError: [Error thrown at core/conversion/conversionctx/ConversionCtx.cpp:149] Building TensorRT engine failed

While exporting a torchscript'd (traced) model to TensorRT, the above error is thrown.
I am trying to convert the model from PyTorch --> Torchscript --> TensorRT using TRTorch.  The model is capable of being torchscripted via tracing and scripting (using torch.jit.script and torch.jit.trace).  Tracing vs scripting does not seem to matter as I've tried both with TRTorch, but I think I got "further" by using the traced model.  I've chosen to "fallback" on all Pytorch operations that are unsupported.  After adding every unsupported operation to the fallback, I eventually get the highly ambiguous error: Building TensorRT engine failed.
To Reproduce
Steps to reproduce the behavior:

Using rwightman-efficientdet repo: https://github.com/rwightman/efficientdet-pytorch/tree/master/
Run

import torch
from effdet import create_model

with set_layer_config(scriptable=True):
      model = create_model(
                      'tf_efficientdet_d4',
                      bench_task='predict',
                      ...,
                  )
model = model.cuda()
model = model.eval()
model.model.toggle_head_bn_level_first() # must toggle heads to make torchscript happy
samples = torch.rand([1, 3, 1024, 1024])
traced  = torch.jit.trace(model, (samples))

compile_settings = {
    "input_shapes": [(1, 3, 1024, 1024)],
    "truncate_long_and_double": True,
    "torch_fallback": {
        "enabled": True, # Turn on or turn off falling back to PyTorch if operations are not supported in TensorRT
        "force_fallback_ops": [
            "aten::ceil",
            "aten::Int",
            "prim::Param",
            "IValue::type",
        ],
        "min_block_size": 1 # Minimum number of ops an engine must incapsulate to be run in TensorRT
    },
}

trt_module = trtorch.compile(traced, compile_settings)

results in the below stack trace:
-----------------------------------------------------------------------
RuntimeError                          Traceback (most recent call last)
<ipython-input-22-c33a73bf6119> in <module>
     15 }
     16
---> 17 trt_ts_module = trtorch.compile(traced_no_img_info, compile_settings)

/opt/conda/lib/python3.8/site-packages/trtorch/_compiler.py in compile(module, compile_spec)
     71             "torch.jit.ScriptFunction currently is not directly supported, wrap the function in a module to compile")
     72
---> 73     compiled_cpp_mod = trtorch._C.compile_graph(module._c, _parse_compile_spec(compile_spec))
     74     compiled_module = torch.jit._recursive.wrap_cpp_module(compiled_cpp_mod)
     75     return compiled_module

RuntimeError: [Error thrown at core/conversion/conversionctx/ConversionCtx.cpp:149] Building TensorRT engine failed

Expected behavior
Export model to TensorRT.  To confirm my environment and installs were working, I successfully exported a simple resnet:
# Test with resnet
import torchvision
import torch
import trtorch

resnet = torchvision.models.resnet18()
resnet.to(0)
traced_res = torch.jit.trace(resnet, samples)

compile_settings = {
    "input_shapes": [(1, 3, 1024, 1024)],
}
trt_traced_module = trtorch.compile(traced_res, compile_settings)
print("Traced Resnet to TRT: Success")

successfully exports.

Environment
Collecting environment information...
PyTorch version: 1.9.0a0+df837d0
Is debug build: False
CUDA used to build PyTorch: 11.2
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.1 LTS (x86_64)
GCC version: (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Clang version: Could not collect
CMake version: version 3.19.6

Python version: 3.8 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: 11.2.142
GPU models and configuration:
GPU 0: Tesla V100-SXM2-32GB
GPU 1: Tesla V100-SXM2-32GB
GPU 2: Tesla V100-SXM2-32GB
GPU 3: Tesla V100-SXM2-32GB
GPU 4: Tesla V100-SXM2-32GB
GPU 5: Tesla V100-SXM2-32GB
GPU 6: Tesla V100-SXM2-32GB
GPU 7: Tesla V100-SXM2-32GB

Nvidia driver version: 418.181.07
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.1.1
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.1.1
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.1.1
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.1.1
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.1.1
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.1.1
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.1.1
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.19.2
[pip3] nvidia-dlprof-pytorch-nvtx==1.0.0
[pip3] pytorch-quantization==2.1.0
[pip3] pytorch-transformers==1.1.0
[pip3] torch==1.9.0a0+df837d0
[pip3] torchtext==0.9.0a0
[pip3] torchvision==0.9.0a0
[pip3] trtorch==0.4.0a0
[conda] magma-cuda110             2.5.2                         5    local
[conda] mkl                       2019.4                      243
[conda] mkl-include               2019.4                      243
[conda] nomkl                     3.0                           0
[conda] numpy                     1.19.2           py38h6163131_0
[conda] numpy-base                1.19.2           py38h75fe3a5_0
[conda] nvidia-dlprof-pytorch-nvtx 1.0.0                    pypi_0    pypi
[conda] pytorch-quantization      2.1.0                    pypi_0    pypi
[conda] pytorch-transformers      1.1.0                    pypi_0    pypi
[conda] torch                     1.9.0a0+df837d0          pypi_0    pypi
[conda] torchtext                 0.9.0a0                  pypi_0    pypi
[conda] torchvision               0.9.0a0                  pypi_0    pypi
[conda] trtorch                   0.4.0a0                  pypi_0    pypi

Additional context
If it helps, I am using the NVIDIA trtorch container built from Dockerfile.21.03.  As an aside - converting Pytorch --> ONNX did not work, either.

Can you enable debugging level log messages and share the log?
        trtorch.logging.set_reportable_log_level(trtorch.logging.Level.Error)

I am facing the same issue ? Any idea to solve it ?
or @narendasan did you get any fix around it ?


[scan] derivedDataPath getting added to xcodebuild command twice, causing error

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

Once I updated to the latest release (2.149.0), I have noticed that fastlane scan is appending -derivedDataPath to the xcodebuild command twice, which causes it to fail.
This is the lane I use in my Fastfile to run scan:
  lane :build_for_ci do
    scan(
      clean: false,
      scheme: $scheme,
      workspace: $workspace,
      configuration: "UnitTest",
      build_for_testing: true,
      buildlog_path: "build_logs",
      skip_build: true,
      devices: $devices
    )
  end

This only appears to be affecting scan - my gym actions are operating as expected.
Command executed

bundle exec fastlane build_for_ci (see Issue Description, this is a custom lane in my Fastfile that wraps the scan action)
Complete output when running fastlane, including the stack trace and command used

    +--------------------------------------------+---------+-------------------------------------------------+
|                                              Used plugins                                              |
+--------------------------------------------+---------+-------------------------------------------------+
| Plugin                                     | Version | Action                                          |
+--------------------------------------------+---------+-------------------------------------------------+
| fastlane-plugin-update_project_codesigning | 0.2.0   | update_project_codesigning                      |
| fastlane-plugin-trainer                    | 0.4.1   | trainer                                         |
| fastlane-plugin-firebase_app_distribution  | 0.1.4   | firebase_app_distribution                       |
| fastlane-plugin-bugsnag                    | 1.4.2   | upload_symbols_to_bugsnag send_build_to_bugsnag |
+--------------------------------------------+---------+-------------------------------------------------+
[12:00:28]: ----------------------------------------
[12:00:28]: --- Step: Verifying fastlane version ---
[12:00:28]: ----------------------------------------
[12:00:28]: Your fastlane version 2.149.0 matches the minimum requirement of 2.121.1  ✅
[12:00:28]: ------------------------------
[12:00:28]: --- Step: default_platform ---
[12:00:28]: ------------------------------
[12:00:28]: Driving the lane 'ios build_for_ci' 🚀
[12:00:29]: ------------------
[12:00:29]: --- Step: scan ---
[12:00:29]: ------------------
[12:00:29]: Resolving Swift Package Manager dependencies...
[12:00:29]: $ xcodebuild -resolvePackageDependencies -workspace [REDACTED].xcworkspace -scheme [REDACTED] -configuration UnitTest
[12:00:29]: ▸ Command line invocation:
[12:00:29]: ▸     /Applications/Xcode11.4.1.app/Contents/Developer/usr/bin/xcodebuild -resolvePackageDependencies -workspace [REDACTED].xcworkspace -scheme [REDACTED] -configuration UnitTest
[12:00:31]: ▸ resolved source packages:
[12:00:31]: $ xcodebuild -showBuildSettings -workspace [REDACTED].xcworkspace -scheme [REDACTED] -configuration UnitTest
[12:00:34]: Command timed out after 3 seconds on try 1 of 4, trying again with a 6 second timeout...
+------------------------------------------------+---------------------------------------------------------------------------------------------+
|                                                           Summary for scan 2.149.0                                                           |
+------------------------------------------------+---------------------------------------------------------------------------------------------+
| clean                                          | false                                                                                |
| scheme                                         | [REDACTED]                                                                                |
| workspace                                      | [REDACTED].xcworkspace                                                                       |
| configuration                                  | UnitTest                                                                                |
| build_for_testing                              | true                                                                                |
| buildlog_path                                  | build_logs                                                                                |
| skip_build                                     | true                                                                                |
| devices                                        | ["iPhone 11 Pro Max (13.4.1)"]                                                              |
| derived_data_path                              | /Users/jhagglund/Library/Developer/Xcode/DerivedData/[REDACTED]-gfbwubeiqylhpkgygoaujpvefsux |
| skip_detect_devices                            | false                                                                                |
| force_quit_simulator                           | false                                                                                |
| reset_simulator                                | false                                                                                |
| disable_slide_to_type                          | true                                                                                |
| reinstall_app                                  | false                                                                                |
| app_identifier                                 | [REDACTED]                                                                   |
| open_report                                    | false                                                                                |
| output_directory                               | ./fastlane/test_output                                                                      |
| output_types                                   | html,junit                                                                                |
| include_simulator_logs                         | false                                                                                |
| should_zip_build_products                      | false                                                                                |
| result_bundle                                  | false                                                                                |
| use_clang_report_name                          | false                                                                                |
| disable_concurrent_testing                     | false                                                                                |
| slack_use_webhook_configured_username_and_icon | false                                                                                |
| slack_username                                 | fastlane                                                                                |
| slack_icon_url                                 | https://fastlane.tools/assets/img/fastlane_icon.png                                         |
| skip_slack                                     | false                                                                                |
| slack_only_on_failure                          | false                                                                                |
| xcodebuild_command                             | env NSUnbufferedIO=YES xcodebuild                                                           |
| fail_build                                     | true                                                                                |
| xcode_path                                     | /Applications/Xcode11.4.1.app                                                               |
+------------------------------------------------+---------------------------------------------------------------------------------------------+
[12:00:40]: Disabling 'Slide to Type' iPhone 11 Pro Max
[12:00:40]: $ /usr/libexec/PlistBuddy -c "Add :KeyboardContinuousPathEnabled bool false" /Users/jhagglund/Library/Developer/CoreSimulator/Devices/3B0AAC9C-C5C6-4C86-9282-2C8B965D35A3/data/Library/Preferences/com.apple.keyboard.ContinuousPath.plist >/dev/null 2>&1
[12:00:40]: $ set -o pipefail && env NSUnbufferedIO=YES xcodebuild -workspace [REDACTED].xcworkspace -scheme [REDACTED] -configuration UnitTest -derivedDataPath /Users/jhagglund/Library/Developer/Xcode/DerivedData/[REDACTED]-gfbwubeiqylhpkgygoaujpvefsux -destination 'platform=iOS Simulator,id=3B0AAC9C-C5C6-4C86-9282-2C8B965D35A3' -derivedDataPath '/Users/jhagglund/Library/Developer/Xcode/DerivedData/[REDACTED]-gfbwubeiqylhpkgygoaujpvefsux' build-for-testing | tee '/Users/jhagglund/dev/[REDACTED]/build_logs/[REDACTED]-[REDACTED].log' | xcpretty  --report html --output '/Users/jhagglund/dev/[REDACTED]/fastlane/test_output/report.html' --report junit --output '/Users/jhagglund/dev/[REDACTED]/fastlane/test_output/report.junit' --report junit --output '/var/folders/c1/1nyddphd64x2jbzx1mgv7wlw0000gn/T/junit_report20200603-12600-1ah5yjr'
[12:00:40]: ▸ Loading...
[12:00:40]: ▸ xcodebuild: error: option '-derivedDataPath' may only be provided once
[12:00:40]: ▸ Usage: xcodebuild [-project ] [[-target ]...|-alltargets] [-configuration ] [-arch ]... [-sdk [|]] [-showBuildSettings [-json]] [=]... []...
[12:00:40]: ▸        xcodebuild [-project ] -scheme  [-destination ]... [-configuration ] [-arch ]... [-sdk [|]] [-showBuildSettings [-json]] [-showdestinations] [=]... []...
[12:00:40]: ▸        xcodebuild -workspace  -scheme  [-destination ]... [-configuration ] [-arch ]... [-sdk [|]] [-showBuildSettings] [-showdestinations] [=]... []...
[12:00:40]: ▸        xcodebuild -version [-sdk [|] [-json] [] ]
[12:00:40]: ▸        xcodebuild -list [[-project ]|[-workspace ]] [-json]
[12:00:40]: ▸        xcodebuild -showsdks [-json]
[12:00:40]: ▸        xcodebuild -exportArchive -archivePath  [-exportPath ] -exportOptionsPlist
[12:00:40]: ▸        xcodebuild -exportNotarizedApp -archivePath  -exportPath
[12:00:40]: ▸        xcodebuild -exportLocalizations -localizationPath  -project  [-exportLanguage ...[-includeScreenshots]]
[12:00:40]: ▸        xcodebuild -importLocalizations -localizationPath  -project
[12:00:40]: ▸        xcodebuild -resolvePackageDependencies [-project |-workspace ] -clonedSourcePackagesDirPath
[12:00:40]: ▸        xcodebuild -create-xcframework [-help] [-framework ] [-library  [-headers ]] -output
[12:00:40]: ▸ Options:
[12:00:40]: ▸     -usage                                                   print brief usage
[12:00:40]: ▸     -help                                                    print complete usage
[12:00:40]: ▸     -verbose                                                 provide additional status output
[12:00:40]: ▸     -license                                                 show the Xcode and SDK license agreements
[12:00:40]: ▸     -checkFirstLaunchStatus                                  Check if any First Launch tasks need to be performed
[12:00:40]: ▸     -runFirstLaunch                                          install packages and agree to the license
[12:00:40]: ▸     -project NAME                                            build the project NAME
[12:00:40]: ▸     -target NAME                                             build the target NAME
[12:00:40]: ▸     -alltargets                                              build all targets
[12:00:40]: ▸     -workspace NAME                                          build the workspace NAME
[12:00:40]: ▸     -scheme NAME                                             build the scheme NAME
[12:00:40]: ▸     -configuration NAME                                      use the build configuration NAME for building each target
[12:00:40]: ▸     -xcconfig PATH                                           apply the build settings defined in the file at PATH as overrides
[12:00:40]: ▸     -arch ARCH                                               build each target for the architecture ARCH; this will override architectures defined in the project
[12:00:40]: ▸     -sdk SDK                                                 use SDK as the name or path of the base SDK when building the project
[12:00:40]: ▸     -toolchain NAME                                          use the toolchain with identifier or name NAME
[12:00:40]: ▸     -destination DESTINATIONSPECIFIER                        use the destination described by DESTINATIONSPECIFIER (a comma-separated set of key=value pairs describing the destination to use)
[12:00:40]: ▸     -destination-timeout TIMEOUT                             wait for TIMEOUT seconds while searching for the destination device
[12:00:40]: ▸     -parallelizeTargets                                      build independent targets in parallel
[12:00:40]: ▸     -jobs NUMBER                                             specify the maximum number of concurrent build operations
[12:00:40]: ▸     -maximum-concurrent-test-device-destinations NUMBER      the maximum number of device destinations to test on concurrently
[12:00:40]: ▸     -maximum-concurrent-test-simulator-destinations NUMBER   the maximum number of simulator destinations to test on concurrently
[12:00:40]: ▸     -parallel-testing-enabled YES|NO                         overrides the per-target setting in the scheme
[12:00:40]: ▸     -parallel-testing-worker-count NUMBER                    the exact number of test runners that will be spawned during parallel testing
[12:00:40]: ▸     -maximum-parallel-testing-workers NUMBER                 the maximum number of test runners that will be spawned during parallel testing
[12:00:40]: ▸     -dry-run                                                 do everything except actually running the commands
[12:00:40]: ▸     -quiet                                                   do not print any output except for warnings and errors
[12:00:40]: ▸     -hideShellScriptEnvironment                              don't show shell script environment variables in build log
[12:00:40]: ▸     -showsdks                                                display a compact list of the installed SDKs
[12:00:40]: ▸     -showdestinations                                        display a list of destinations
[12:00:40]: ▸     -showTestPlans                                           display a list of test plans
[12:00:40]: ▸     -showBuildSettings                                       display a list of build settings and values
[12:00:40]: ▸     -showBuildSettingsForIndex                               display build settings for the index service
[12:00:40]: ▸     -list                                                    lists the targets and configurations in a project, or the schemes in a workspace
[12:00:40]: ▸     -find-executable NAME                                    display the full path to executable NAME in the provided SDK and toolchain
[12:00:40]: ▸     -find-library NAME                                       display the full path to library NAME in the provided SDK and toolchain
[12:00:40]: ▸     -version                                                 display the version of Xcode; with -sdk will display info about one or all installed SDKs
[12:00:40]: ▸     -enableAddressSanitizer YES|NO                           turn the address sanitizer on or off
[12:00:40]: ▸     -enableThreadSanitizer YES|NO                            turn the thread sanitizer on or off
[12:00:40]: ▸     -enableUndefinedBehaviorSanitizer YES|NO                 turn the undefined behavior sanitizer on or off
[12:00:40]: ▸     -resultBundlePath PATH                                   specifies the directory where a result bundle describing what occurred will be placed
[12:00:40]: ▸     -resultStreamPath PATH                                   specifies the file where a result stream will be written to (the file must already exist)
[12:00:40]: ▸     -resultBundleVersion 3 [default]                         specifies which result bundle version should be used
[12:00:40]: ▸     -clonedSourcePackagesDirPath PATH                        specifies the directory to which remote source packages are fetch or expected to be found
[12:00:40]: ▸     -derivedDataPath PATH                                    specifies the directory where build products and other derived data will go
[12:00:40]: ▸     -archivePath PATH                                        specifies the directory where any created archives will be placed, or the archive that should be exported
[12:00:40]: ▸     -exportArchive                                           specifies that an archive should be exported
[12:00:40]: ▸     -exportNotarizedApp                                      export an archive that has been notarized by Apple
[12:00:40]: ▸     -exportOptionsPlist PATH                                 specifies a path to a plist file that configures archive exporting
[12:00:40]: ▸     -enableCodeCoverage YES|NO                               turn code coverage on or off when testing
[12:00:40]: ▸     -exportPath PATH                                         specifies the destination for the product exported from an archive
[12:00:40]: ▸     -skipUnavailableActions                                  specifies that scheme actions that cannot be performed should be skipped instead of causing a failure
[12:00:40]: ▸     -exportLocalizations                                     exports completed and outstanding project localizations
[12:00:40]: ▸     -importLocalizations                                     imports localizations for a project, assuming any necessary localized resources have been created in Xcode
[12:00:40]: ▸     -localizationPath                                        specifies a path to XLIFF localization files
[12:00:40]: ▸     -exportLanguage                                          specifies multiple optional ISO 639-1 languages included in a localization export
[12:00:40]: ▸     -xcroot                                                  specifies a path to a .xcroot to use for building and/or testing
[12:00:40]: ▸     -xctestrun                                               specifies a path to a test run specification
[12:00:40]: ▸     -testPlan                                                specifies the name of the test plan associated with the scheme to use for testing
[12:00:40]: ▸     -only-testing                                            constrains testing by specifying tests to include, and excluding other tests
[12:00:40]: ▸     -only-testing:TEST-IDENTIFIER                            constrains testing by specifying tests to include, and excluding other tests
[12:00:40]: ▸     -skip-testing                                            constrains testing by specifying tests to exclude, but including other tests
[12:00:40]: ▸     -skip-testing:TEST-IDENTIFIER                            constrains testing by specifying tests to exclude, but including other tests
[12:00:40]: ▸     -test-timeouts-enabled YES|NO                            enable or disable test timeout behavior
[12:00:40]: ▸     -default-test-execution-time-allowance                   the default execution time an individual test is given to execute, if test timeouts are enabled
[12:00:40]: ▸     -maximum-test-execution-time-allowance                   the maximum execution time an individual test is given to execute, regardless of the test's preferred allowance
[12:00:40]: ▸     -only-test-configuration                                 constrains testing by specifying test configurations to include, and excluding other test configurations
[12:00:40]: ▸     -skip-test-configuration                                 constrains testing by specifying test configurations to exclude, but including other test configurations
[12:00:40]: ▸     -testLanguage                                            constrains testing by specifying ISO 639-1 language in which to run the tests
[12:00:40]: ▸     -testRegion                                              constrains testing by specifying ISO 3166-1 region in which to run the tests
[12:00:40]: ▸     -resolvePackageDependencies                              resolves any Swift package dependencies referenced by the project or workspace
[12:00:40]: ▸     -disableAutomaticPackageResolution                       prevents packages from automatically being resolved to versions other than those recorded in the Package.resolved file
[12:00:40]: ▸     -json                                                    output as JSON (note: -json implies -quiet)
[12:00:40]: ▸     -allowProvisioningUpdates                                Allow xcodebuild to communicate with the Apple Developer website. For automatically signed targets, xcodebuild will create and update profiles, app IDs, and certificates. For manually signed targets, xcodebuild will download missing or updated provisioning profiles. Requires a developer account to have been added in Xcode's Accounts preference pane.
[12:00:40]: ▸     -allowProvisioningDeviceRegistration                     Allow xcodebuild to register your destination device on the developer portal if necessary. This flag only takes effect if -allowProvisioningUpdates is also passed.
[12:00:40]: ▸     -showBuildTimingSummary                                  display a report of the timings of all the commands invoked during the build
[12:00:40]: ▸     -create-xcframework                                      create an xcframework from prebuilt libraries; -help for more information.
xcodebuild: error: option '-derivedDataPath' may only be provided once
Usage: xcodebuild [-project ] [[-target ]...|-alltargets] [-configuration ] [-arch ]... [-sdk [|]] [-showBuildSettings [-json]] [=]... []...
xcodebuild [-project ] -scheme  [-destination ]... [-configuration ] [-arch ]... [-sdk [|]] [-showBuildSettings [-json]] [-showdestinations] [=]... []...
xcodebuild -workspace  -scheme  [-destination ]... [-configuration ] [-arch ]... [-sdk [|]] [-showBuildSettings] [-showdestinations] [=]... []...
xcodebuild -version [-sdk [|] [-json] [] ]
xcodebuild -list [[-project ]|[-workspace ]] [-json]
xcodebuild -showsdks [-json]
xcodebuild -exportArchive -archivePath  [-exportPath ] -exportOptionsPlist
xcodebuild -exportNotarizedApp -archivePath  -exportPath
xcodebuild -exportLocalizations -localizationPath  -project  [-exportLanguage ...[-includeScreenshots]]
xcodebuild -importLocalizations -localizationPath  -project
xcodebuild -resolvePackageDependencies [-project |-workspace ] -clonedSourcePackagesDirPath
xcodebuild -create-xcframework [-help] [-framework ] [-library  [-headers ]] -output
Options:
-usage                                                   print brief usage
-help                                                    print complete usage
-verbose                                                 provide additional status output
-license                                                 show the Xcode and SDK license agreements
-checkFirstLaunchStatus                                  Check if any First Launch tasks need to be performed
-runFirstLaunch                                          install packages and agree to the license
-project NAME                                            build the project NAME
-target NAME                                             build the target NAME
-alltargets                                              build all targets
-workspace NAME                                          build the workspace NAME
-scheme NAME                                             build the scheme NAME
-configuration NAME                                      use the build configuration NAME for building each target
-xcconfig PATH                                           apply the build settings defined in the file at PATH as overrides
-arch ARCH                                               build each target for the architecture ARCH; this will override architectures defined in the project
-sdk SDK                                                 use SDK as the name or path of the base SDK when building the project
-toolchain NAME                                          use the toolchain with identifier or name NAME
-destination DESTINATIONSPECIFIER                        use the destination described by DESTINATIONSPECIFIER (a comma-separated set of key=value pairs describing the destination to use)
-destination-timeout TIMEOUT                             wait for TIMEOUT seconds while searching for the destination device
-parallelizeTargets                                      build independent targets in parallel
-jobs NUMBER                                             specify the maximum number of concurrent build operations
-maximum-concurrent-test-device-destinations NUMBER      the maximum number of device destinations to test on concurrently
-maximum-concurrent-test-simulator-destinations NUMBER   the maximum number of simulator destinations to test on concurrently
-parallel-testing-enabled YES|NO                         overrides the per-target setting in the scheme
-parallel-testing-worker-count NUMBER                    the exact number of test runners that will be spawned during parallel testing
-maximum-parallel-testing-workers NUMBER                 the maximum number of test runners that will be spawned during parallel testing
-dry-run                                                 do everything except actually running the commands
-quiet                                                   do not print any output except for warnings and errors
-hideShellScriptEnvironment                              don't show shell script environment variables in build log
-showsdks                                                display a compact list of the installed SDKs
-showdestinations                                        display a list of destinations
-showTestPlans                                           display a list of test plans
-showBuildSettings                                       display a list of build settings and values
-showBuildSettingsForIndex                               display build settings for the index service
-list                                                    lists the targets and configurations in a project, or the schemes in a workspace
-find-executable NAME                                    display the full path to executable NAME in the provided SDK and toolchain
-find-library NAME                                       display the full path to library NAME in the provided SDK and toolchain
-version                                                 display the version of Xcode; with -sdk will display info about one or all installed SDKs
-enableAddressSanitizer YES|NO                           turn the address sanitizer on or off
-enableThreadSanitizer YES|NO                            turn the thread sanitizer on or off
-enableUndefinedBehaviorSanitizer YES|NO                 turn the undefined behavior sanitizer on or off
-resultBundlePath PATH                                   specifies the directory where a result bundle describing what occurred will be placed
-resultStreamPath PATH                                   specifies the file where a result stream will be written to (the file must already exist)
-resultBundleVersion 3 [default]                         specifies which result bundle version should be used
-clonedSourcePackagesDirPath PATH                        specifies the directory to which remote source packages are fetch or expected to be found
-derivedDataPath PATH                                    specifies the directory where build products and other derived data will go
-archivePath PATH                                        specifies the directory where any created archives will be placed, or the archive that should be exported
-exportArchive                                           specifies that an archive should be exported
-exportNotarizedApp                                      export an archive that has been notarized by Apple
-exportOptionsPlist PATH                                 specifies a path to a plist file that configures archive exporting
-enableCodeCoverage YES|NO                               turn code coverage on or off when testing
-exportPath PATH                                         specifies the destination for the product exported from an archive
-skipUnavailableActions                                  specifies that scheme actions that cannot be performed should be skipped instead of causing a failure
-exportLocalizations                                     exports completed and outstanding project localizations
-importLocalizations                                     imports localizations for a project, assuming any necessary localized resources have been created in Xcode
-localizationPath                                        specifies a path to XLIFF localization files
-exportLanguage                                          specifies multiple optional ISO 639-1 languages included in a localization export
-xcroot                                                  specifies a path to a .xcroot to use for building and/or testing
-xctestrun                                               specifies a path to a test run specification
-testPlan                                                specifies the name of the test plan associated with the scheme to use for testing
-only-testing                                            constrains testing by specifying tests to include, and excluding other tests
-only-testing:TEST-IDENTIFIER                            constrains testing by specifying tests to include, and excluding other tests
-skip-testing                                            constrains testing by specifying tests to exclude, but including other tests
-skip-testing:TEST-IDENTIFIER                            constrains testing by specifying tests to exclude, but including other tests
-test-timeouts-enabled YES|NO                            enable or disable test timeout behavior
-default-test-execution-time-allowance                   the default execution time an individual test is given to execute, if test timeouts are enabled
-maximum-test-execution-time-allowance                   the maximum execution time an individual test is given to execute, regardless of the test's preferred allowance
-only-test-configuration                                 constrains testing by specifying test configurations to include, and excluding other test configurations
-skip-test-configuration                                 constrains testing by specifying test configurations to exclude, but including other test configurations
-testLanguage                                            constrains testing by specifying ISO 639-1 language in which to run the tests
-testRegion                                              constrains testing by specifying ISO 3166-1 region in which to run the tests
-resolvePackageDependencies                              resolves any Swift package dependencies referenced by the project or workspace
-disableAutomaticPackageResolution                       prevents packages from automatically being resolved to versions other than those recorded in the Package.resolved file
-json                                                    output as JSON (note: -json implies -quiet)
-allowProvisioningUpdates                                Allow xcodebuild to communicate with the Apple Developer website. For automatically signed targets, xcodebuild will create and update profiles, app IDs, and certificates. For manually signed targets, xcodebuild will download missing or updated provisioning profiles. Requires a developer account to have been added in Xcode's Accounts preference pane.
-allowProvisioningDeviceRegistration                     Allow xcodebuild to register your destination device on the developer portal if necessary. This flag only takes effect if -allowProvisioningUpdates is also passed.
-showBuildTimingSummary                                  display a report of the timings of all the commands invoked during the build
-create-xcframework                                      create an xcframework from prebuilt libraries; -help for more information.
[12:00:41]: Exit status: 64
+----------------------------+---------------------------------------------------------------------------------------------+
|                                                       Lane Context                                                       |
+----------------------------+---------------------------------------------------------------------------------------------+
| DEFAULT_PLATFORM           | ios                                                                                |
| PLATFORM_NAME              | ios                                                                                |
| LANE_NAME                  | ios build_for_ci                                                                            |
| SCAN_DERIVED_DATA_PATH     | /Users/jhagglund/Library/Developer/Xcode/DerivedData/[REDACTED]-gfbwubeiqylhpkgygoaujpvefsux |
| SCAN_GENERATED_PLIST_FILES | []                                                                                |
| SCAN_GENERATED_PLIST_FILE  |                                                                                |
+----------------------------+---------------------------------------------------------------------------------------------+
[12:00:41]: Error building/testing the application. See the log above.
+------+----------------------------+-------------+
|                fastlane summary                 |
+------+----------------------------+-------------+
| Step | Action                     | Time (in s) |
+------+----------------------------+-------------+
| 1    | Verifying fastlane version | 0           |
| 2    | default_platform           | 0           |
| 💥   | scan                       | 12          |
+------+----------------------------+-------------+
[12:00:41]: fastlane finished with errors

Environment

 ✅ fastlane environment ✅
Stack

Key
Value

OS
10.15.5

Ruby
2.6.6

Bundler?
true

Git
git version 2.27.0

Installation Source
~/.rbenv/versions/2.6.6/bin/fastlane

Host
Mac OS X 10.15.5 (19F101)

Ruby Lib Dir
~/.rbenv/versions/2.6.6/lib

OpenSSL Version
OpenSSL 1.1.1d  10 Sep 2019

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode11.4.1.app/Contents/Developer/

Xcode Version
11.4.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# Customise this file, documentation can be found here:
# https://github.com/fastlane/fastlane/tree/master/fastlane/docs
# All available actions: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md
# can also be listed using the `fastlane actions` command

# Change the syntax highlighting to Ruby
# All lines starting with a # are ignored when running `fastlane`

# If you want to automatically update fastlane if a new version is available:
# update_fastlane

# This is the minimum version number required.
# Update this, if you use features of a newer version
fastlane_version "2.121.1"

default_platform :ios

[REDACTED]

platform :ios do
  before_all do
    if ENV['CI']
      # Necessary because CircleCI has multiple XCode versions
      xcode_select "/Applications/Xcode-11.4.1.app"
    end
  end

  [REDACTED]

  desc "Performs a build for CI setup purposes, using the UnitTest configuration"
  lane :build_for_ci do
    scan(
      clean: false,
      scheme: $scheme,
      workspace: $workspace,
      configuration: "UnitTest",
      build_for_testing: true,
      buildlog_path: "build_logs",
      skip_build: true,
      devices: $devices
    )
  end

  [REDACTED]

  after_all do |lane|
    # This block is called, only if the executed lane was successful
    if ENV["CI"]
      slack(
        message: [REDACTED],
        success: true,
        fail_on_error: false,
        default_payloads: [:lane, :test_result, :git_branch, :git_author]
      )
    end
  end

  error do |lane, exception|
    if ENV["CI"]
      slack(
        message: exception.message,
        success: false,
        fail_on_error: false
      )
    end
  end
end

# More information about multiple platforms in fastlane: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Platforms.md
# All available actions: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Actions.md

# fastlane reports which actions are used
# No personal data is recorded. Learn more at https://github.com/fastlane/enhancer

`./fastlane/Appfile`
app_identifier [REDACTED] # The bundle identifier of your app

team_id [REDACTED]  # Developer Portal Team ID

# you can even provide different app identifiers, Apple IDs and team names per lane:
# More information: https://github.com/fastlane/fastlane/blob/master/fastlane/docs/Appfile.md

fastlane gems

Gem
Version
Update-Status

fastlane
2.149.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-update_project_codesigning
0.2.0
✅ Up-To-Date

fastlane-plugin-trainer
0.4.1
✅ Up-To-Date

fastlane-plugin-firebase_app_distribution
0.1.4
✅ Up-To-Date

fastlane-plugin-bugsnag
1.4.2
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.3.0

bundler
2.1.4

CFPropertyList
3.0.2

ZenTest
4.12.0

RubyInline
3.12.5

concurrent-ruby
1.1.6

i18n
0.9.5

minitest
5.14.1

thread_safe
0.3.6

tzinfo
1.2.7

activesupport
<IP_ADDRESS>

public_suffix
2.0.5

addressable
2.7.0

httpclient
2.8.3

json
2.3.0

algoliasearch
1.27.3

atomos
0.1.3

aws-eventstream
1.1.0

aws-partitions
1.323.0

aws-sigv4
1.1.4

jmespath
1.4.0

aws-sdk-core
3.97.1

aws-sdk-kms
1.33.0

aws-sdk-s3
1.67.1

babosa
1.0.3

circleci
2.0.3

highline
1.7.10

commander-fastlane
4.4.6

down
5.1.1

mini_portile2
2.4.0

nokogiri
1.10.9

http-accept
1.7.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

mime-types-data
3.2020.0512

mime-types
3.3.1

netrc
0.11.0

rest-client
2.1.0

safe_shell
1.1.0

circle-ci-utils
1.7.1

claide
1.0.3

fuzzy_match
2.0.4

nap
1.1.0

cocoapods-core
1.8.4

cocoapods-deintegrate
1.0.4

cocoapods-downloader
1.3.0

cocoapods-plugins
1.0.0

cocoapods-search
1.0.0

cocoapods-stats
1.1.0

cocoapods-trunk
1.5.0

cocoapods-try
1.2.0

colored2
3.1.2

escape
0.0.4

fourflusher
2.3.1

gh_inspector
1.1.3

molinillo
0.6.6

ruby-macho
1.4.0

nanaimo
0.2.6

xcodeproj
1.16.0

cocoapods
1.8.4

rouge
2.0.7

xcpretty
0.3.0

cocoapods-binary
0.4.4

dotenv
2.7.5

osx_keychain
1.0.2

cocoapods-keys
2.1.0

colored
1.2

ruby-terminfo
0.1.1

console_table
0.3.0

declarative
0.0.10

declarative-option
0.1.0

descendants_tracker
0.0.4

digest-crc
0.5.1

emoji_regex
1.0.1

excon
0.73.0

multipart-post
2.0.0

faraday
0.17.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.14.0

fastimage
2.1.7

jwt
2.1.0

memoist
0.16.2

multi_json
1.14.1

os
1.1.0

signet
0.14.0

googleauth
0.12.0

mini_mime
1.0.2

uber
0.1.0

representable
3.0.4

retriable
3.1.2

google-api-client
0.38.0

google-cloud-env
1.3.2

google-cloud-errors
1.0.1

google-cloud-core
1.5.0

google-cloud-storage
1.26.2

mini_magick
4.10.1

multi_xml
0.6.0

plist
3.5.0

rubyzip
1.3.0

security
0.1.3

naturally
2.2.0

simctl
1.6.8

slack-notifier
2.3.2

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

tty-screen
0.8.0

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

xcpretty-travis-formatter
1.0.0

rchardet
1.8.0

git
1.7.0

xml-simple
1.1.5

fastlane-plugin-bugsnag
1.4.2

fastlane-plugin-firebase_app_distribution
0.1.4

trainer
0.9.1

fastlane-plugin-trainer
0.4.1

fastlane-plugin-update_project_codesigning
0.2.0

ffi
1.13.0

frontkick
0.5.7

hashie
3.6.0

rack
2.2.2

oauth2
1.4.4

github_api
0.18.2

mustache
1.1.1

open4
1.3.4

redcarpet
3.5.0

sassc
2.4.0

sqlite3
1.4.2

liferaft
0.0.6

xcinvoke
0.3.0

jazzy
0.13.4

xcresult
0.2.1

xcov
1.7.3

generated on: 2020-06-03

I started having this same problem with 2.149.0, too.

Same. Builds yesterday using 2.148.1 worked perfectly with only a single -derivedDataPath being set. Today it is being added twice on 2.149.0

+1

+1

+1

Also experiencing this issue, a recently merged and released PR that seems related: https://github.com/fastlane/fastlane/pull/16534

@jhandguy That's my suspicion too but it had a unit test that past with a strict equality assertion (meaning in that case it was just the one -derivedData flag). But stands to reason we're missing a test somewhere. I planned to dig in sometime today unless someone beats me to it.

This unit test only tests project.rb, my guess is that the error only occurs with scan which most probably uses project.rb under the hood.

+1

+1

+1

Can confirm this is happening with (at least) scan. Started after updating to 2.149.

+1 getting the same error in 2.149.0 in our CI builds.

+1

1

+1

This is a pretty serious regression that is breaking builds that run automated tests.  It's affecting an enormous number of users.  Can someone just revert PR #16534, put out an emergency release, and then fix it properly later?
CC @sudachi808 @janpio

https://github.com/fastlane/fastlane/pull/16559 illustrates where I think the problem is happening and provides a potential fix. It'll be several hours before I can fully vet it, but wanted to get something up to at least kickstart a potential solution. I'll spend a bit more time on it this evening.

Thank you @TheMetalCode!

Sorry about this! Will get that fix in a new build pushed out in a in an hour or so

Going to revert #16559 and ship a new build. I think that PR needs to be looked into a little bit more and I’d like to get a fix for this out sooner rather than later 🤷♂

Things should be back to normal now when you update to 2.149.1! Sorry again about these issues. I should have been better about catching the side effects from that PR. Hope this didn’t cause you all too much trouble 😔 Will try to harder to prevent these things from happening going forward.

Thanks for fixing this, updating to 2.149.1 fixed this issue for me


Replace use with loader

keyword use throws error with webpack 3.

Hmmm, are you sure you're on the right version of webpack? Can you share a screenshot of your configuration and output? I'm pretty sure we wanted to stick with use going forward...
cc @webpack/documentation-team @sokra

That would be a big breaking change and I don't see it mentioned in the changelog. If it was changed this may actually be a bug in the v3 release.

Closing... I tested this out and was not able to replicate. Please share more details if this is still an issue for you.

Look at here https://webpack.js.org/configuration/module/#useentry It's using loader for single, non-array loaders. So why it is here?

@morajabi I agree it is a bit confusing, however we are trying to at least be consistent with the recommended usage in the docs (see #569). The basic premise is that for the top level rule objects, use is recommended. Within nested UseEntry objects, e.g. when you need to specify options, loader is used. I think the old keys like loader, which currently still exist for compatibility, will be phased out in upcoming releases.
cc @webpack/core-team -- we've heard about this a few times now in this repo alone... just a heads up as maybe it's a sign we should start phasing these old properties out.


Update zio-sbt-website to 0.1.5+17-bb02fef9-SNAPSHOT

Updates dev.zio:zio-sbt-website from 0.1.5+10-49adf3d7-SNAPSHOT to 0.1.5+17-bb02fef9-SNAPSHOT.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio", artifactId = "zio-sbt-website" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "dev.zio", artifactId = "zio-sbt-website" }
}]

labels: sbt-plugin-update, early-semver-build-metadata, semver-spec-build-metadata, commit-count:1

Superseded by #798.


Google Sign-in to Apps - Browser or App may not be secure

I just downloaded the app today but unfortunately I've not been able to login to Slack or Trello using Google sign-in. An error is displayed saying
"
Couldn't sign you in
This browser or app may not be secure.
Try using a different browser. If you’re already using a supported browser, you can refresh your screen and try again to sign in.
"
Replication Steps

Open Station
Add in either Trello or Slack
Select to login using Google sign in
Enter your email address
Actual - Error presented
Expected - Able to enter password to sign in

It may be related to https://github.com/getstation/desktop-app/issues/2 but I think its sufficiently different to warrant a separate issue.

This Issue is already known: https://github.com/getstation/desktop-app/issues/2 || https://github.com/getstation/desktop-app/issues/9

Thanks @sven-ahrens , I close this


fetch only tags for release when needed

need to wait for https://github.com/actions/checkout/pull/579 to be resolved

i think right now we pull all tags when cloning for release, but only need latest
this is minor but could cause slowdown in the far future


Accepting opponent surrender

Sometimes a message pops up saying "A.I. wishes to surrender, do you accept?" and then by clicking yes the game is ended with a Victory.
Is it possible to accept this surrender from code?
It would be useful to end the games more quickly.

I also want to know the answer. Anybody could give us a hand?


Calling get_edited_object() in an EditorProperty deletes the target object on editor exiting the tree

Godot version
fcba87e696d58912838d8a4a6987b10efa28e78f
System information
Gentoo Linux
Issue description
When  get_edited_object() is called in a custom EditorProperty, the target object will be deleted when the editor is switched to something else, or even if you just click on the same resource again to re-select it. If I do not assign the get_edited_object() to anything, like in the example project, it happens after two times.
Steps to reproduce

In the attached project, double click the Test.tres resource.
Expand "Reply Next', in "Next Line" create a new "DialogueReplyNext"
Double click the Test.tres again, maybe several times.
The "Next Line" becomes empty

See addons/train_plugin/DialogueReplyNextEditor.gd for EditorProperty code. It's stripped down to just get_edited_object, since that seems to be enough.
Minimal reproduction project
bug.zip

Same as #70311, reverting 6141ce2cb8ae54965190257a1ffd6a6abd02aaea fixes the issue. Perhaps this is another argument to do so.

Seems this was fixed in beta 16, since I see the code changed to what it was before, so I'm closing this.


Linear Search Algorithm in Kotlin

💥 Proposal
(A clear and concise description of what the proposal is.)
I would like to implement an algorithm that searches for a given number in a given list of numbers in linear time.
Have you read the Contributing Guidelines on Pull Requests?
Yes
(Write your answer here.)
@HarshCasper, please assign this issue to me under GSSoC'21.

/assign

@nagasrihith608! kindly finish you existing issues before you open up a new one. Thank you

@anushkrishnav, sure actually there were other issues I opened and they didn't assign me. thank you


Remove key from object after delete object.key

Suggestion
🔍 Search Terms
delete
delete key
narrowing
narrowing delete
✅ Viability Checklist

My suggestion meets these guidelines:

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
In TypeScript, it's already possible to have objects add keys to their types using if ("key" in object) // object: { key: unknown }. It is not currently possible to do the exact opposite: deleting a key off of an object.
This could be achieved in two ways:

Guaranteed: type { key: string }; delete object.key; type { }.
Optional: type { key?: string | undefined }; if (object.key === undefined) delete object.key; type { key?: string }.

The guaranteed way is pretty straight forward: it removes the key entirely.
The optional way is slightly more tricky: it should only remove the type information checked in the if statement. Remaining type options should still exist after the if statement. If the last remaining type option is removed, then it should function the same as the guaranteed way.
Naturally, if the key didn't exist on the object in the first place, the type information should remain the exact same as before.
📃 Motivating Example
I'm using the zod library, with which I set a value on object user as { givenName: string; infix?: string | undefined; surname: string; }.
I wrote a factory function toUser({ givenName, infix, surname }: { givenName: string; infix?: string; surname: string; }): User { ... }.
The type infix?: string | undefined is not compatible with type infix?: string.

--- EDIT: Extra example ---
After executing delete object.key, I'm expecting the type information to no longer contain this key:
  const myObject: { key1?: string | undefined, key2?: string | undefined } = { ... };
  delete myObject.key1; // Type should now become: { key2?: string | undefined}
  myObject.key1 // Should error, key was deleted

Now, if I want to remove a key under certain conditions:
  const myObject: { key1?: string | number | undefined } = { ... };
  if (typeof myObject.key1 === "number") delete myObject.key1; // Removes "number" from types. This already works.
  if (typeof myObject.key1 === "undefined") delete myObject.key1; // Removes "undefined" from type definition. This does not work yet.
  if (typeof myObject.key1 === "string") delete myObject.key1; // Removes the last type; "key1" will no longer exist on object.

In the above example, the native types "number" and "string" get stripped off as expected. The type "undefined" however, does not. This breaks the tsconfig option exactOptionalPropertyTypes as the key should now no longer be able to exist. It cannot exist with literal value undefined.
💻 Use Cases

This is purely type information, but it seems essential if the typing system is to remain correct after the delete keyword.
For the time being, I'll have to set the type to infix?: string | undefined, knowing it's not entirely accurate (key "infix" should not be permitted with value "undefined").

A more clearly-stated example would be nice

Sorry. I've added a new example with some comments after it; hope that clarifies things a bit more.

Optional: type { key?: string | undefined }; if (object.key === undefined) delete object.key; type { key?: string }.

I don't think this actually matters, regardless of exactOptionalPropertyTypes.  From the point of view of someone reading the value of obj.key, there's no meaningful difference between { key?: string } vs. { key?: string | undefined } - it only matters when you're writing to that property, in which case the declared type is all that matters and whatever narrowing has happened since then is irrelevant.

Perhaps, but what I mostly would like to see is a type update where the key is omitted after the delete statement. It's not so much about the value being string | undefined, that was mostly just an example.
It does seem to me it will need to include undefined if it is to figure the proper type. There's a very small difference between "key" in myObject and myObject.key === undefined. It's possible to have a situation where both are true, or "key" in myObject is false.
Essentially, there are two situations to consider.

Narrowing typing information (mostly working already, i.e. with "string", "number", etc.)
Deleting the key entirely

Narrowing
When narrowing, it's important to consider that it's possible for a key to exist with specific value undefined. This is displayed as myObject.key = undefined. The key exists, but has no value. The type of myObject is { key: undefined }. Note that it does not need to be optional to have value undefined.
In case of a type union, such as string | undefined, a conditional delete should turn the key optional. After all, it cannot be part of the object based on the condition. Here's an example:
  type MyObjectType = { key: string | undefined };
  const myObject: MyObjectType = { key: undefined };

  if (typeof myObject.key === "undefined") delete myObject.key; // After this, the type should be { key?: string }
  const value: string = myObject.key // Should error as "key" could be missing from the type.

If the situation is such, where "key" is optional, TypeScript will need to consider the possibility of the key being absent at the start.
  type MyObjectType = { key?: string | undefined };
  const myObject: MyObjectType = { key: undefined };

  if (typeof myObject.key === "undefined") delete myObject.key; // Type should become { key?: string }
  const value: string | undefined = myObject.key // Should be okay
  const value2: string = myObject.key // Should error; "key" may be undefined

  if ("key" in myObject) delete myObject.key; // Key is removed and type should become { }
  const value: string | undefined = myObject.key; // Should error; "key" cannot be string
  const value2: undefined = myObject.key; // Should be okay, "key" does not exist. typeof "key" is undefined.

Deleting the key entirely
Deleting entirely is simply a matter of omitting the key from the original type entirely.
  type MyObjectType = { key: string | undefined };
  const myObject: MyObjectType = { key: "Hello World!" };

  delete myObject.key // After this, the type should be { }
  const value: string = myObject.key // Should error as "key" does not exist on type of "myObject".

nice


Change chart colours to match table view

Hi @orangecoding,
I just tried out the app and it's great. Thank you for putting it together!
I found the colours on the chart a bit confusing, so I updated them to match the table view.
Here's an example:

Feel free to decline this PR, I just thought I'd share.

cool, thx


Release Tracking

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
<EMAIL_ADDRESS>Major Changes

#1514 dc789025 Thanks @colebemis! - Remove deprecated color variables by upgrading to @primer/primitives v5
Note: Install eslint-plugin-primer-react to ensure that you're not using any deprecated or removed color variables.

Patch Changes

#1512 1e5ac406 Thanks @pksjce! - Change disabled color from muted to custom primer disabled color

@jfuchs @colebemis I opened a draft PR in memex to illustrate the linting changes. Somehow I don't see any effect of the deprecated colors. Is there something I'm missing?


Useful error against multiple clauses

...because this is an easy mistake to make when the interface invites multiple clauses, and silent failure is evil.

Haha. Dimwit.


HTML5 push notifications: not all registered clients get the notification

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.33.0
Python release (python3 --version):
3.5.2
Component/platform:
HTML5 push notification
Description of problem:
Some clients (e.g. Galaxy S7) do not receive notifications after being registered while these notifications deliver to other clients.
The problem persists from earlier HASS versions, previously the problematic client could not be registered, see issue #4012.
Expected:
Receive notifications to all registered devices.
Problem-relevant configuration.yaml entries and steps to reproduce:
notify:
  - name: Push
    platform: html5
    gcm_api_key: 'redacted'
    gcm_sender_id: 'redacted'

Traceback (if applicable):

Additional info:

There is no traceback available?
Can you check the credentials and make sure you are using

„ Firebase Cloud Messaging token“ as gcm_api_key (not the server key!)
„Sender ID“ as gcm_sender_id

Do I understand this right, that you have multiple devices registered and notifications works for some of them, just not for the S7?

I believe I use the right token and id because I receive notifications on two other clients but not on the one that previously caused the issue #4012.

In addition, I wouldn't mind to double check if the "new" instructions regarding HTML5 push notifications are responsible for the issue, however, I don't know how to follow these instructions anymore, see details https://community.home-assistant.io/t/html5-getting-ready-for-chrome/6586

@mweinelt ,
After checking traceback, I've found that the messages are delivering to all registered devices.
The issue was that notifications from Chrome were blocked in settings of the device (S7).
Now everything is working as expected.
Sorry for my noise and thank you for trying clarify my issue.


chore(deps): update rust crate rstest to 0.16.0

This PR contains the following updates:

Package
Type
Update
Change

rstest
dev-dependencies
minor
0.15.0 -> 0.16.0

Release Notes

la10736/rstest
v0.16.0
Compare Source
Changed

Show TEST START banner only when trace some argument: See #158 for details.
Add values to test name: See #160 for details.

Fixed

Updated test fixtures to 1.64.0 compiler's error messages.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: Cargo.lock
Command failed: docker run --rm --name=renovate_sidecar --label=renovate_child -v "/tmp/renovate/repos/github/sarub0b0/kubetui":"/tmp/renovate/repos/github/sarub0b0/kubetui" -v "/tmp/renovate/cache":"/tmp/renovate/cache" -e BUILDPACK_CACHE_DIR -e CONTAINERBASE_CACHE_DIR -w "/tmp/renovate/repos/github/sarub0b0/kubetui" docker.io/renovate/sidecar bash -l -c "install-tool rust 1 && cargo update --manifest-path Cargo.toml --workspace"


Object's set_meta() doesn't work on inherited scenes

Operating system or device, Godot version, GPU Model and driver (if graphics related):
6277e6d40a0f0e8c84470482400959fca4ff5ad8
Issue description:
I'm writing an editor tool in which I would like to save some informations inside the scene itself. It turns out I can't save any information inside those scenes which are extending another ones.
Steps to reproduce:
Short way:

Download sample project
open InheritedScene.tscn
Save it.
Check InheritedScene.tscn  in notepad and see that there is no meta data
Additional: Repeat above steps for BaseScene.tscn and see meta is saved inside  BaseScene.tscn

Long way:

Create BaseScene.tscn
Create scene which is inheriting BaseScene.tscn save it as InheritedScene.tscn
Attach this code to InheritedScene.tscn:

tool
extends Node
func _ready():
	set_meta("Custom Meta", "Meta informations: " +  get_name() + " save time: " + str(OS.get_time()));

Reopen InheritedScene.tscn
Save it
Open InheritedScene.tscn in notepad and see that there is no meta data

Link to minimal example project:
MetaInfoSaveInInheritedSceneTool.zip

Good to see that you have isolated the issue! I was having lots of trouble reading metadata via the get_meta function a few weeks back on my game. Now I realise why I was getting all the errors :)

I also suspect this issue is related with #12838

For the reference, I checked if #32416 would fix this issue, but it did not.

2 Years later and this error still persists.

Having problems with this as well, on 3.3

A side effect of this bug is that Editor Descriptions can’t be set for inherited scenes.

I'm not able to reproduce this issue in the 3.x branch at commit a75afd61a77c58fc7daaa525e485398795221f6f

Closing per @Rubonnek's comment. Please comment if you can still reproduce this.


LL-4614 Inline installation on connectApp flows as experimental

https://ledgerhq.atlassian.net/browse/LL-4614
This functionality allows the user to install an application when, during a device flow, we detect that they don't have such application installed. This affects the Send, Receive, and Add account flows and enables the user to complete the flow without having to leave the modal/screen, go to the manager, install the application, and return.
This means that we can detach a bit more the user's awareness of what an app is, and what apps are installed on their device, minimise the friction on the flows too.
It's controlled by a new ENV variable EXPERIMENTAL_INLINE_INSTALL since we should thoroughly test this before releasing. It can also be enabled in the experimental section of the settings.
How to test this

All flows of the app should work with and without the experimental setting.
When the experimental setting is ON, it should solve app dependencies in-flow
When the experimental setting is OFF, it should refer the user to the manager

I'm flagging this as important because it's merged on LLD but not yet LLM.

Indeed it should be blocking on these steps I guess

I'm taking a look today

@Arnaud97234 after talking with @gre and since even if the user leaves mid install (device is in processing) it's not locked in that state, since this is experimental, it's not a blocker for merging. I did have to update the PR because the experimental setting wasn't working on my end. Please test again

we have to hodl the PR and merge live-common pr first because there were breaking change in live-common that needed some fixes (like shipping fees).
we can merge after it.


Use RR kv only for testing

Need a demo first.

@wolfy-j is described in readme. With a simple interface just to mock completion or failure. I see it as a proof of concept. Later can be approved with a real mocking interface. Like expect this activity to be invoked N times and return/fail with something.


Fix

Is this a regression?
No
Description
Deprecate usage of elliptic for Apollo.
https://github.com/hyperledger/identus-edge-agent-sdk-ts/actions/runs/10369060744/job/28703980597?pr=263
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in
No response
Anything else?
No response

Can you improve the title in this issue?


Add websocket

Adds a basic websocket implementation, with all authentication and timeouts that pterodactyl needs.

Looks good.


Fix filename typo in UsageWithReactRouter docs

Footer component filename is listed as containers/Footer.js in docs
Directory in the example app is components/Footer.js
Update docs to match example app

Thanks!


HIVE-23925: Flaky test TestJdbcWithMiniHS2

What changes were proposed in this pull request?

Why are the changes needed?

Does this PR introduce any user-facing change?

How was this patch tested?

@kgyrtkirk
I need small help. I got green build in hive-precommit. But when I am trying to run on http://ci.hive.apache.org/job/hive-flaky-check/279/ it is failing with "/home/jenkins/agent/workspace/hive-flaky-check/.git/m2/org/apache/hive/hive-contrib/4.0.0-SNAPSHOT/hive-contrib-4.0.0-SNAPSHOT.jar does not exist".
Then I found that "hive-contrib" is not build as part of "mvn install" command in  hive-flaky-check pipeline. How can I enable it in "hive-flaky-check" ?