go/libraries/utils/argparser/parser.go: Clean up Parse and fix handling of -- passed as commit spec

I noticed this while trying to get dolt blame to support -- as a valid value for commit spec. Previously, the parser would stop parsing when it encountered a --. This led to problems when that argument was not the last argument in the list, as in
dolt blame -- some_table

This fixes that. In the process I think I simplified the logic by taking advantage of early returns and continues to avoid else blocks and the indentation that comes with them.

Okay, that spec makes sense. Yeah, if that's the intended behavior, I was seeing a bug -- the double dash and any subsequent parameters weren't being passed to the commands at all (I verified this with logging and in the debugger).

Instead, they should just be passed verbatim from the -- on, am I understanding correctly? Can have that change quickly if so.

Yeah, my understanding is that every argument appearing after -- should be passed verbatim on to the command. The -- itself should not get passed on. Right?

I think it should be, or perhaps be replaced with an empty string. Otherwise, commands which depend on the later positional arguments being at a particular index will fail.

I'm not sure I understand the issue.  Can you give an example.  I would assume that:
command -option -option2 table file

would be the same as
command -option -option2 table -- file

and the same as
command -option -option2 -- table file

in all cases table is positional arg 0, and file is positional arg 1.

In the above example if -- gets passed as one of the positional arguments, then you can no longer guarantee that table is positional arg 0 and file is positional arg 1.  In each of the 3 cases above they are at different positional locations:
["table", "file"]
["table", "--", "file"]
["--","table","file"]

The -- replaces a positional arg. In the case of, say, git checkout:
git checkout -- some/file

is equivalent (at least roughly and maybe precisely) to
git checkout HEAD some/file

Isn't that the same as
git checkout some/file

The -- stops argument parsing and gets removed from the argument list, or equivalently, gets replaced by the remaining arguments.

Okay, that's fine. The parser still needs to be fixed, because it doesn't do that.

I can make the change in a few minutes.

Actually I think there's still an issue, though it's arguably because Git is abusing --:
git checkout file1 file2 file3

will check out file2 and file3 from a branch named file1 if one exists, but you can prevent this by passing --:
git checkout -- file1 file2 file3

You can see they are not equivalent:
$ git checkout master foo.go bar.go
error: pathspec 'foo.go' did not match any file(s) known to git
error: pathspec 'bar.go' did not match any file(s) known to git

$ git checkout -- master foo.go bar.go
error: pathspec 'master' did not match any file(s) known to git
error: pathspec 'foo.go' did not match any file(s) known to git
error: pathspec 'bar.go' did not match any file(s) known to git

        /*
         * case 1: git checkout <ref> -- [<paths>]
         *
         *   <ref> must be a valid tree, everything after the '--' must be
         *   a path.
         *
         * case 2: git checkout -- [<paths>]
         *
         *   everything after the '--' must be paths.
         *
         * case 3: git checkout <something> [--]
         *
         *   (a) If <something> is a commit, that is to
         *       switch to the branch or detach HEAD at it.  As a special case,
         *       if <something> is A...B (missing A or B means HEAD but you can
         *       omit at most one side), and if there is a unique merge base
         *       between A and B, A...B names that merge base.
         *
         *   (b) If <something> is _not_ a commit, either "--" is present
         *       or <something> is not a path, no -t or -b was given, and
         *       and there is a tracking branch whose name is <something>
         *       in one and only one remote (or if the branch exists on the
         *       remote named in checkout.defaultRemote), then this is a
         *       short-hand to fork local <something> from that
         *       remote-tracking branch.
         *
         *   (c) Otherwise, if "--" is present, treat it like case (1).
         *
         *   (d) Otherwise :
         *       - if it's a reference, treat it like case (1)
         *       - else if it's a path, treat it like case (2)
         *       - else: fail.
         *
         * case 4: git checkout <something> <paths>
         *
         *   The first argument must not be ambiguous.
         *   - If it's *only* a reference, treat it like case (1).
         *   - If it's only a path, treat it like case (2).
         *   - else: fail.
         *
         */

                if (!arg[2]) { /* "--" */
                        if (!(ctx->flags & PARSE_OPT_KEEP_DASHDASH)) {
                                ctx->argc--;
                                ctx->argv++;
                        }
                        break;
                }

        if (opts->accept_pathspec && opts->accept_ref)
                parseopt_flags = PARSE_OPT_KEEP_DASHDASH;

        argc = parse_options(argc, argv, prefix, options,
                             usagestr, parseopt_flags);

git is an absolute beast. Is it important to keep this? Can't the user just pass HEAD?

That is the most incredible thing I've read all week.
No, I do not feel strongly about preserving this behavior. I've sat here for a few minutes trying to think of why we shouldn't axe it. Does -- ever mean anything other than HEAD when used that way? If not, it imposes a pretty high cost for allowing the user to save two keystrokes...

But then again, it will violate people's expectations in kind of a gnarly way if they're used to what Git does...

So where do we land on this? Should @timsehn weigh in?

I don't know enough about this to care. My default position is do what get does even if it's weird and hard to implement.

That's kind of where I'm at too.
So that said, @reltuk and @bheni, how do we want to handle this? What I've done effectively punts the -- to each individual command to decide what to do with it, but we could also do something like what Git does and actually (ugh, gross) modify the argument list based on whether one of a certain class of commands was called.


Is there a way to remove our own get fields functionality now?

I'm not sure how exactly da's getField() works, or when it got added in, but we might be able to use that on a page with variable names (of what format? how do you use x and i?) more smoothly than parsing the page ourselves. Haven't read much about it yet: https://docassemble.org/docs/functions.html#js_getField

Later findings summary: getField() and getFields() aren't enough for everything, though they may help. I'll try to add more details when I get the chance.


Consider implementing our own Json serializer

There are several issues with the serde_json:

We had to fork it to make sure it does not produce float instructions, see: https://github.com/serde-rs/json/issues/567 and https://github.com/nearprotocol/json
When trying to serialize an object not supported by json (e.g. a HashMap with has keys that are not primitive types) we are getting a runtime error instead of a compile-time error, because of serde framework restrictions. This leads to a lot of confusion and bad DevX as reported by users;
In addition to a large code foot print of serde_json it needs serde itself which is also a large piece of code. It would be nice if contract developers could use a small and simple library that they could trust because they could easily read through.
Serde_json has performance optimizations that might not make sense on Wasm.

Unfortunately implementing Json serializer is a lot of work. Here is another json library but it does not uses derive macroses: https://github.com/maciejhirsz/json-rust

When trying to serialize an object not supported by json (e.g. a HashMap with has keys that are not primitive types) we are getting a runtime error instead of a compile-time error, because of serde framework restrictions. This leads to a lot of confusion and bad DevX as reported by users;

I think, support of keys with custom types could lead to even more confusion as we taking interop with AssemblyScript contracts as a goal. It wouldn't be hard to check it with near_bindgen isn't it?

Yes, that’s why we need compile time check. It is actually not possible to
check with near-bindgen because it works on AST so a function can be
returning some type and there is no way to see whether this type has
unsupported types somewhere deep in the type structure.
On Fri, Sep 20, 2019 at 10:59 AM Alexey<EMAIL_ADDRESS>wrote:

When trying to serialize an object not supported by json (e.g. a HashMap
with has keys that are not primitive types) we are getting a runtime error
instead of a compile-time error, because of serde framework restrictions.
This leads to a lot of confusion and bad DevX as reported by users;
I think, support of keys with custom types could lead to even more
confusion as we taking interop with AssemblyScript contracts as a goal. It
wouldn't be hard to check it with near_bindgen isn't it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nearprotocol/near-bindgen/issues/24?email_source=notifications&email_token=AILKVBZYNGAT3FHKY2PEAQ3QKR7H5A5CNFSM4IYJLMT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7F5JZA#issuecomment-533452004,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AILKVB5Y6KAHNWPMACEFB4TQKR7H5ANCNFSM4IYJLMTQ
.

obsolete

@evgenykuzyakov @nearmax I'd be curious to learn with which solution or workaround you ended up with. Could you leave a little hint here? Thanks a lot!

Explained in https://t.me/wasmblockchain

At Near decided not to fork serde-json , because there are many other libraries that we would have to fork too which would degrade the DevX. Instead we canonicalize float NaNs.


ServiceBusTrigger and INameResolver

Hello,
Is it still possible to pass dynamic queue name to Service Bus trigger? Previously INameResolver was used for that, but the new extension is missing this interface.
public class QueueNameResolver : INameResolver
{
    public string Resolve(string name)
    {
        return ConfigurationManager.AppSettings[name].ToString();
    }
}

Can you share more details about your scenario?
Are you trying to programmatically set those values? This is not supported with the isolated worker, and something that would cause problems in consumption environments, so we just want to better understand your requirements. Thanks!

Hello Fabio,
In my case the queue name comes from the configuration and should be set dynamically. This is how it looked in the previous SDK:
private const string InputQueueName = "%ServiceBus:Queues:QueueName%";

        [Function(FunctionName)]
        public async Task RunAsync([ServiceBusTrigger(InputQueueName)] Message message, CancellationToken cancellationToken)
        {

Thank you for the additional details.
This is indeed a limitation with the model, currently, as you don't have the ability to inject a name resolver in the context used by the extension.
Flagging this so we can discuss an appropriate approach to meet the requirement.

@ankitkumarr FYI, this would benefit from the worker driven indexing/metadata work.

This is a blocker for us moving from Web Jobs to Azure Functions.

@dhermyt I totally agree we should be able to inject our custom NameResolver like we can with the "normal" Azure Functions (called now class library AFAIK).
https://docs.microsoft.com/en-us/azure/app-service/webjobs-sdk-how-to#version-3x-6
 var builder = new HostBuilder();
    var resolver = new CustomNameResolver();
    builder.ConfigureWebJobs(b =>
    {
        b.AddAzureStorageCoreServices();
    });
    builder.ConfigureServices(s => s.AddSingleton<INameResolver>(resolver));  // This is how to do it with "normal" azure functions and WebJobs
    var host = builder.Build();
    using (host)
    {
        await host.RunAsync();
    }

But have in mind that the Isolated mode does implement a the default NameResolver es mentioned here https://docs.microsoft.com/en-us/azure/app-service/webjobs-sdk-how-to#custom-binding-expressions
"There's a default NameResolver that takes effect if you don't provide a custom one. The default gets values from app settings or environment variables."
So, while it's not as powerful and flexible as a custom NameResolver, it may work for you as the default behaviour is reading from an appsetting/enviromentvariable.
So this:
        [Function("Function1")]
        public void Run([ServiceBusTrigger("%myqueueName%", Connection = "MyConnection")] string myQueueItem, FunctionContext context)
        {
            var logger = context.GetLogger("Function1");
            logger.LogInformation($"C# ServiceBus queue trigger function processed message: {myQueueItem}");
        }

reads the queue name from a configuration setting / enviroment variable called myqueueName. I have tested this myself both locally and in Azure.
I insist, we should be able to inject our custom NameResolver for max flexibility

This is a blocker for us moving from Web Jobs to Azure Functions.

It's the same for us, we're planning to migrate in-process functions to isolated and this is another roadblock we need to overcome.
@fabiocav is there any plan to port this feature?

Hi @fabiocav, is there any public information/github issue on worker driven indexing/metadata work?

Is there any update here?
It seems I can't even put my queue names in a separate 'queue-names.json' file
eg
    builder
        .AddJsonFile("local.settings.json", optional: true, reloadOnChange: true)
        .AddJsonFile("queue-names.json", optional: true, reloadOnChange: true)
        .AddEnvironmentVariables();

If the queue names are in queue-names.json then it simply doesn't work.
They have to be in local.settings.json

I've also tried several variations of trying to inject a custom INameResolver (with a dotnet-isolated) function before I came across this github issue. As with others, it always hits the internal name resolver first, barfs and then stops, before getting to mine, by which time it's too late.
Given that .NET 8 is forcing Functions into being isolated process (and no more in-process), it would be good if we could get this resolved ;)
Thank you 👍🏻

I've also tried several variations of trying to inject a custom INameResolver (with a dotnet-isolated) function before I came across this github issue. As with others, it always hits the internal name resolver first, barfs and then stops, before getting to mine, by which time it's too late.
Given that .NET 8 is forcing Functions into being isolated process (and no more in-process), it would be good if we could get this resolved ;)
Thank you 👍🏻

I agree -
I'm going to try and do a blog post on how I worked around this - but it's convoluted, build step, generate local.settings.json for each user.
Honestly, such a lot of work for something that should be so simple!

I've also tried several variations of trying to inject a custom INameResolver (with a dotnet-isolated) function before I came across this github issue. As with others, it always hits the internal name resolver first, barfs and then stops, before getting to mine, by which time it's too late.
Given that .NET 8 is forcing Functions into being isolated process (and no more in-process), it would be good if we could get this resolved ;)
Thank you 👍🏻

I agree - I'm going to try and do a blog post on how I worked around this - but it's convoluted, build step, generate local.settings.json for each user. Honestly, such a lot of work for something that should be so simple!

what is the solution that you have implemented? I am pretty much stuck with the same issue. I am unable to resolve the name for the expression from appSettings

I just ran into this today. At least I'm not alone.
My scenario is pretty simple. I have a TimerTrigger with a CRON time. I know I can add that to the environment variables and it will work. What I want(ed) was to be a little smarter about it and provide a default.
builder.Configuration["SCHEDULER_CRON_TIME"] = builder.Configuration["SCHEDULER_CRON_TIME"] ?? "*/1 * * * * *";
However, that doesn't work, because the internal Function logic doesn't seem to be playing off the same configuration.
Like others I tracked this down to the name resolver, in my case, TimerSchedule.cs:
string resolvedExpression = nameResolver.ResolveWholeString(attribute.ScheduleExpression);
This seems like a really basic thing. As far as I can tell the Azure Function stuff has it's own internal service registration, because I don't even see DefaultNameResolver in the service collection.

I also ran into this issue. I sthere any change planned ?

Hi there,
I ran into this problem yesterday and dug into it.

From what I can see the resolving of the %token% value from Environment variables is done in Func.exe / the Host in Azure Functions.
The Metadata that is needed for the runner to register with all the queue etc is sent across via a GRPC call on start up.
This metadata is generated at design time by a Code Generator and is in a class which implements IFunctionMetadataProvider.

I have been able to create a new class internal class ConfigurableFunctionMetadataProvider(IFunctionMetadataProvider baseProvider, IConfiguration configuration, ILogger<ConfigurableFunctionMetadataProvider> logger) : IFunctionMetadataProvider { .... }
which then decorates the existing entry in the ServiceCollection and walks the metadata coming back and replacing the tokens from what is configured in IConfiguration before passing it on.
I would just paste the code here but it is entwined in a customer project and I would have to rewrite it afresh if others were going to use it.  If people need it let me know and I will invest the time to do that for you.  Or ask on SO and link the question after this message and I will update there for you (and others).
Jonathan

@ac931274 I am also interested in seeing your workaround to this. This issue is blocking our migration to isolated worker, which is a little scary since they're saying in process isn't going to be updated anymore.

I have added my code to Stack Overflow here : https://stackoverflow.com/questions/78897966/azure-functions-trigger-variables-isolated-functions/78897967#78897967
Please upvote, question and answer, if useful.

I'm looking for clarification. With ServiceBusTrigger, the value given to Connection is used to get the connection string from IConfiguration. This works as documented.
However, if you use the % % syntax for topicName and subscriptionName, it only pulls those values from the environment variables, NOT from IConfiguration. I have seen several statements in documentation (and in issues of this repo) that state these values are pulled from configuration when the value begins and ends with %, but based on my testing, that isn't true.
Please let me know if I'm incorrect and if anyone has been able to set these values from IConfiguration. FYI, if you set the values in local.settings.json when running locally, those become environment variables at runtime.


Added testing related globals to standard configuration

When trying to commit I kept getting errors from standard that 'describe, it, expect and beforeEach' were not defined. Since these keywords are defined globally, i added them to the globals property so they would be ignored.

Thank you @gavin771 !


Does not support numpy 2

Solution to issue cannot be found in the documentation.

[x] I checked the documentation.

Issue
Since 1.0.0, gymnasium supports Python 3.12 and Numpy 2.0. Specifically, the dependency says "numpy >=1.21.0",.
However, the following command fails to resolve dependencies:
$ mamba create -n gym -c conda-forge "python>=3.12" "numpy>=2.0" "gymnasium>=1.0"

Looking for: ["python[version='>=3.12']", "numpy[version='>=2.0']", "gymnasium[version='>=1.0']"]

conda-forge/linux-64                                        Using cache
conda-forge/noarch                                          Using cache
pkgs/main/noarch                                              No change
pkgs/r/linux-64                                               No change
pkgs/main/linux-64                                            No change
pkgs/r/noarch                                                 No change
Could not solve for environment specs
The following packages are incompatible
├─ gymnasium >=1.0  is installable with the potential options
│  ├─ gymnasium 1.0.0 would require
│  │  ├─ python >=3.10,<3.11.0a0 , which can be installed;
│  │  └─ python_abi 3.10.* *_cp310, which can be installed;
│  ├─ gymnasium 1.0.0 would require
│  │  ├─ python >=3.11,<3.12.0a0 , which can be installed;
│  │  └─ python_abi 3.11.* *_cp311, which can be installed;
│  ├─ gymnasium 1.0.0 would require
│  │  ├─ numpy >=1.26.4,<2.0a0  with the potential options
│  │  │  ├─ numpy [1.26.4|2.0.0|...|2.1.3] would require
│  │  │  │  └─ python_abi 3.10.* *_cp310, which can be installed;
│  │  │  ├─ numpy [1.26.4|2.0.0|...|2.1.3] would require
│  │  │  │  └─ python_abi 3.11.* *_cp311, which can be installed;
│  │  │  ├─ numpy 1.26.4, which can be installed;
│  │  │  ├─ numpy [1.26.4|2.0.0|2.0.1|2.0.2] would require
│  │  │  │  └─ python_abi 3.9.* *_cp39, which can be installed;
│  │  │  ├─ numpy 1.26.4 would require
│  │  │  │  └─ pypy3.9 >=7.3.15 , which can be installed;
│  │  │  ├─ numpy [1.26.4|2.0.0|2.0.1|2.1.1|2.1.3] would require
│  │  │  │  └─ python >=3.10,<3.11.0a0 , which can be installed;
│  │  │  ├─ numpy [1.26.4|2.0.0|2.0.1|2.1.1|2.1.3] would require
│  │  │  │  └─ python >=3.11,<3.12.0a0 , which can be installed;
│  │  │  └─ numpy [1.26.4|2.0.0|2.0.1] would require
│  │  │     └─ python >=3.9,<3.10.0a0 , which can be installed;
│  │  ├─ python >=3.12,<3.13.0a0  but there are no viable options
│  │  │  ├─ python [3.12.0|3.12.1|...|3.12.7] conflicts with any installable versions previously reported;
│  │  │  └─ python [3.12.0|3.12.1|...|3.12.7] would require
│  │  │     └─ python_abi 3.12.* *_cp312, which conflicts with any installable versions previously reported;
│  │  └─ python_abi 3.12.* *_cp312, which requires
│  │     └─ python 3.12.* *_cpython, which can be installed;
│  └─ gymnasium 1.0.0 would require
│     ├─ python >=3.9,<3.10.0a0 , which can be installed;
│     └─ python_abi 3.9.* *_cp39, which can be installed;
├─ numpy >=2.0  is installable with the potential options
│  ├─ numpy [1.26.4|2.0.0|...|2.1.3], which can be installed (as previously explained);
│  ├─ numpy [1.26.4|2.0.0|...|2.1.3], which can be installed (as previously explained);
│  ├─ numpy [1.26.4|2.0.0|2.0.1|2.0.2], which can be installed (as previously explained);
│  ├─ numpy [1.26.4|2.0.0|2.0.1|2.1.1|2.1.3], which can be installed (as previously explained);
│  ├─ numpy [1.26.4|2.0.0|2.0.1|2.1.1|2.1.3], which can be installed (as previously explained);
│  ├─ numpy [1.26.4|2.0.0|2.0.1], which can be installed (as previously explained);
│  ├─ numpy [2.0.0|2.0.1|...|2.1.3] conflicts with any installable versions previously reported;
│  ├─ numpy [2.1.0|2.1.1|2.1.2|2.1.3] would require
│  │  └─ python_abi 3.13.* *_cp313, which can be installed;
│  ├─ numpy 2.1.0rc1 would require
│  │  └─ _numpy_rc, which does not exist (perhaps a missing channel);
│  └─ numpy [2.1.2|2.1.3] would require
│     └─ python_abi 3.13.* *_cp313t, which can be installed;
└─ python >=3.12  is not installable because there are no viable options
   ├─ python [3.12.0|3.12.1|...|3.12.7] conflicts with any installable versions previously reported;
   ├─ python [3.12.0|3.12.1|...|3.12.7], which cannot be installed (as previously explained);
   ├─ python 3.13.0 conflicts with any installable versions previously reported;
   └─ python [3.13.0rc1|3.13.0rc2|3.13.0rc3] would require
      └─ _python_rc, which does not exist (perhaps a missing channel).

Installed packages
# packages in environment at /home/stanley/.miniforge3:
#
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                 conda_forge    conda-forge
_openmp_mutex             4.5                       2_gnu    conda-forge
archspec                  0.2.3              pyhd8ed1ab_0    conda-forge
boltons                   24.0.0             pyhd8ed1ab_0    conda-forge
brotli-python             1.1.0           py310hf71b8c6_2    conda-forge
bzip2                     1.0.8                h4bc722e_7    conda-forge
c-ares                    1.34.3               heb4867d_0    conda-forge
ca-certificates           2024.8.30            hbcca054_0    conda-forge
certifi                   2024.8.30          pyhd8ed1ab_0    conda-forge
cffi                      1.17.1          py310h8deb56e_0    conda-forge
charset-normalizer        3.4.0              pyhd8ed1ab_0    conda-forge
colorama                  0.4.6              pyhd8ed1ab_0    conda-forge
conda                     24.9.2          py310hff52083_0    conda-forge
conda-libmamba-solver     24.9.0             pyhd8ed1ab_0    conda-forge
conda-package-handling    2.4.0              pyh7900ff3_0    conda-forge
conda-package-streaming   0.11.0             pyhd8ed1ab_0    conda-forge
distro                    1.9.0              pyhd8ed1ab_0    conda-forge
fmt                       11.0.2               h434a139_0    conda-forge
frozendict                2.4.6           py310ha75aee5_0    conda-forge
h2                        4.1.0              pyhd8ed1ab_0    conda-forge
hpack                     4.0.0              pyh9f0ad1d_0    conda-forge
hyperframe                6.0.1              pyhd8ed1ab_0    conda-forge
icu                       75.1                 he02047a_0    conda-forge
idna                      3.10               pyhd8ed1ab_0    conda-forge
jsonpatch                 1.33               pyhd8ed1ab_0    conda-forge
jsonpointer               3.0.0           py310hff52083_1    conda-forge
keyutils                  1.6.1                h166bdaf_0    conda-forge
krb5                      1.21.3               h659f571_0    conda-forge
ld_impl_linux-64          2.43                 h712a8e2_2    conda-forge
libarchive                3.7.4                hfca40fe_0    conda-forge
libcurl                   8.10.1               hbbe4b11_0    conda-forge
libedit                   3.1.20191231         he28a2e2_2    conda-forge
libev                     4.33                 hd590300_2    conda-forge
libffi                    3.4.2                h7f98852_5    conda-forge
libgcc                    14.2.0               h77fa898_1    conda-forge
libgcc-ng                 14.2.0               h69a702a_1    conda-forge
libgomp                   14.2.0               h77fa898_1    conda-forge
libiconv                  1.17                 hd590300_2    conda-forge
libmamba                  1.5.10               hf72d635_1    conda-forge
libmambapy                1.5.10          py310h6639945_1    conda-forge
libnghttp2                1.64.0               h161d5f1_0    conda-forge
libnsl                    2.0.1                hd590300_0    conda-forge
libsolv                   0.7.30               h3509ff9_0    conda-forge
libsqlite                 3.47.0               hadc24fc_1    conda-forge
libssh2                   1.11.0               h0841786_0    conda-forge
libstdcxx                 14.2.0               hc0a3c3a_1    conda-forge
libstdcxx-ng              14.2.0               h4852527_1    conda-forge
libuuid                   2.38.1               h0b41bf4_0    conda-forge
libxcrypt                 4.4.36               hd590300_1    conda-forge
libxml2                   2.13.4               hb346dea_2    conda-forge
libzlib                   1.3.1                hb9d3cd8_2    conda-forge
lz4-c                     1.9.4                hcb278e6_0    conda-forge
lzo                       2.10              hd590300_1001    conda-forge
mamba                     1.5.10          py310h51d5547_1    conda-forge
menuinst                  2.2.0           py310hff52083_0    conda-forge
ncurses                   6.5                  he02047a_1    conda-forge
openssl                   3.4.0                hb9d3cd8_0    conda-forge
packaging                 24.2               pyhd8ed1ab_0    conda-forge
pip                       24.3.1             pyh8b19718_0    conda-forge
platformdirs              4.3.6              pyhd8ed1ab_0    conda-forge
pluggy                    1.5.0              pyhd8ed1ab_0    conda-forge
pybind11-abi              4                    hd8ed1ab_3    conda-forge
pycosat                   0.6.6           py310h2372a71_0    conda-forge
pycparser                 2.22               pyhd8ed1ab_0    conda-forge
pysocks                   1.7.1              pyha2e5f31_6    conda-forge
python                    3.10.15         h4a871b0_2_cpython    conda-forge
python_abi                3.10                    5_cp310    conda-forge
readline                  8.2                  h8228510_1    conda-forge
reproc                    14.2.4.post0         hd590300_1    conda-forge
reproc-cpp                14.2.4.post0         h59595ed_1    conda-forge
requests                  2.32.3             pyhd8ed1ab_0    conda-forge
ruamel.yaml               0.18.6          py310ha75aee5_1    conda-forge
ruamel.yaml.clib          0.2.8           py310ha75aee5_1    conda-forge
setuptools                75.3.0             pyhd8ed1ab_0    conda-forge
tk                        8.6.13          noxft_h4845f30_101    conda-forge
tqdm                      4.67.0             pyhd8ed1ab_0    conda-forge
truststore                0.10.0             pyhd8ed1ab_0    conda-forge
tzdata                    2024b                hc8b5060_0    conda-forge
urllib3                   2.2.3              pyhd8ed1ab_0    conda-forge
wheel                     0.45.0             pyhd8ed1ab_0    conda-forge
xz                        5.2.6                h166bdaf_0    conda-forge
yaml-cpp                  0.8.0                h59595ed_0    conda-forge
zstandard                 0.23.0          py310ha39cb0e_1    conda-forge
zstd                      1.5.6                ha6fb4c9_0    conda-forge

Environment info
active environment : None
            shell level : 0
       user config file : /home/stanley/.condarc
 populated config files : /home/stanley/.miniforge3/.condarc
                          /home/stanley/.condarc
          conda version : 24.9.2
    conda-build version : not installed
         python version : 3.10.15.final.0
                 solver : libmamba (default)
       virtual packages : __archspec=1=skylake
                          __conda=24.9.2=0
                          __cuda=12.6=0
                          __glibc=2.39=0
                          __linux=6.8.0=0
                          __unix=0=0
       base environment : /home/stanley/.miniforge3  (writable)
      conda av data dir : /home/stanley/.miniforge3/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/linux-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/linux-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/linux-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /home/stanley/.miniforge3/pkgs
                          /home/stanley/.conda/pkgs
       envs directories : /home/stanley/.miniforge3/envs
                          /home/stanley/.conda/envs
               platform : linux-64
             user-agent : conda/24.9.2 requests/2.32.3 CPython/3.10.15 Linux/6.8.0-48-generic ubuntu/24.04.1 glibc/2.39 solver/libmamba conda-libmamba-solver/24.9.0 libmambapy/1.5.10
                UID:GID : 1000:1000
             netrc file : None
           offline mode : False

You can check the numpy 2 migrator status page to see that this is waiting for https://github.com/conda-forge/tensorstore-feedstock/pull/30


Feature: Slack notifications

As a feature, we could support Slack notifications when link checking fails.
This could be done as a webhook or alternatively, using ready-made GitHub actions or other integrations. In this case the README could include example of how to enable this integration.

If someone wants to give this a try, there are Github actions like these that we could use: https://github.com/marketplace/actions/slack-notify. I'd prefer that over bundling the Slack integration into lychee-action, because it would be more flexible to configure and it would be easier to stay up-to-date with Slack API changes.
Steps to help out here:

Add lychee and Slack action to a test pipeline
Try a test run to see if it works (e.g. it sends a Slack message on lychee failure)
Send a pull request which adds a usage example to the README.md


Re-triggering offcanvas causes infinite backdrops

PHP Version
8.2
Shopware Version
<IP_ADDRESS>
Expected behaviour
If an offcanvas is open and its trigger is clicked again, the offcavas should close.
If an offcanvas (e.g. mobile menu) is open and another offcanvas (e.g. cart) trigger is clicked, the offcanvas (mobile menu) should close and the other offcanvas (cart) should open.
Actual behaviour
If an offcanvas is open and its trigger is clicked again, it re-opens itself and another .offcanvas-backdrop div is added to the DOM.
If an offcanvas (e.g. mobile menu) is open and another offcanvas (e.g. cart) trigger is clicked, the offcanvas (mobile menu) closes and the other offcanvas (cart) opens, but another .offcanvas-backdrop div is added to the DOM.
How to reproduce
* This only concerns themes which have the offcanvas positioned below the header with the top CSS property, or in some other way that enables the trigger to be clicked after the offcanvas is initially opened.

Navigate to the homepage.
Click on the mobile menu trigger button / cart trigger button.
After the offcanvas opens, click the trigger button again.
See that the offcanvas reopens itself and another .offcanvas-backdrop is added to the DOM.

https://github.com/user-attachments/assets/cc96e5bf-d794-4cdf-880a-62050f8a0bd7

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-37789.
[created from NEXT-37789, comment 488188]


bugfix: fix upstream get unwanted /.

What type of PR is this?

What this PR does / why we need it:
when the pathMath.Prefix has suffix / but EG has removed it,
https://github.com/envoyproxy/gateway/blob/f4c53f4899b543a6461e7bf666a9bfa3b476e6b4/internal/xds/translator/route.go#L148-L153
and the urlRewrite.Path.PrefixMatchReplace suffix with / the upstream will get unwanted /
Which issue(s) this PR fixes:

Fixes #3989

can you add a test to guarantee this?

/retest

/retest

@qicz can you add an e2e for this ?


LinearResistance usage docs

Missing from https://deltares.github.io/Ribasim/core/usage.html

This has been done.


auth headers not added after sign_in on safari 5.1

When using safari 5.1, after registering a new user, I login my user, to post data to the backend.
The post request that is being sent does not contain the auth header.
it works fine for other more recent browser.
     $auth.submitRegistration($scope.user)
      .then((resp) ->
        # We auth user
        $auth.submitLogin({
          email: $scope.user.email,
          password: $scope.user.password
        }).then((resp) ->
          $http.post(ENV.apiEndpoint + "/api/v1/addresses", $scope.address)

Can reproduce this issue too. Any suggestion for a potential fix?

One piece of advice to solve this issue:
log all the response headers coming from your server with a http interceptor in Angular. See if you correctly log the access-token property after sign-in. Are you using Ionic? (see #255 )
Otherwise, check if your app store the access-token in the local-storage (or cookie) with the dev console in your browser.

@gouroujo @spolom @mikew75 hey guys, I have the same issue. First time when submitting signin tokens not getting saved.
Number($auth.getExpiry()); from
tokenIsCurrent = function($auth, headers) {
    var newTokenExpiry, oldTokenExpiry;
    oldTokenExpiry = Number($auth.getExpiry());
    newTokenExpiry = Number($auth.getConfig().parseExpiry(headers || {}));
    return newTokenExpiry >= oldTokenExpiry;
};

return NaN first time, then null. Even if you set breakpoint in this function and invoke  oldTokenExpiry = Number($auth.getExpiry()); manually twice first time will be NaN and then null. And in this case it saves token immediately.
Any ideas?


[client] KeepAlive option is ignored

Hi,
This is how looks init for client.
void
Client::init(const Client::Options& options) {
    pool.init(options.maxConnectionsPerHost_);
    transport_.reset(new Transport);
    reactor_->init(Aio::AsyncContext(options.threads_));
    transportKey = reactor_->addHandler(transport_);
    reactor_->run();
}

but options has also KeepAlive Parameter part that is ignored in settings

Is there a movement on this one? Thanks for working on this. :)

Does not appear to be.  Feel free to submit a PR; I will review it.  Please include unit tests.

I don't use pistache anymore. So you can close issue if u don;t have a problem with keep alive.

Yes it is hard coded at src/common/http.cc#L662.
https://github.com/oktal/pistache/blob/bc52382d9de1b2bd180a40a1889ba0ef4dd37545/src/common/http.cc#L640-L683

This is a critical bug in this source. Not handling connections that doesn't keep alive makes this code really weak and can lead your service to a simple shutdown just by not closing connection with server. That is, this library just let client control connection closing and there is absolutely no control from server.

Someone let a comment that were disabling this feature to improove speed. But I think this could lead to a really big problem in the reliability of this library.


Comment:Step-Basic-About-Hooks-2

Just want to be sure about syntax. For service and method-level hooks, the config uses parentheses after the hook method name. For app and app-level error config, you did NOT use parentheses after the hook method name. i.e.
// service/method-level hooks
const myHooks = {
  before: {
    all: hook01()  // uses parentheses!
  }
};
const svc = app.service('svc');
svc.hooks(myHooks);

// app-level error/app hooks
app.hooks({
  before: {
    all: hook02 // does NOT use parentheses!
  },
  error: {
    all: hook00e // does NOT use parentheses!
  }
});

Why the difference?

The service call handler expects the hooks it calls to have the signature context => {}. So if you have such a hook you would code all: myHook.
You however commonly want to pass params to the hook, such as which field in the record to delete. So you need a signature like params => context => {} and code all: myHook().
The common hooks and the Feathers community tend to use the latter signature for consistency. So ity would be best to havd () everywhere in the examples.

Docs have been updated.


Update uuid to version 3.0.0

Version 3.0.0 of uuid just got published.
Hi there,
This week a new version of the uuid module got released. The old module which was available by the name node-uuid got deprecated and will show error message upon every install of the module.
To get rid of those install errors I've created this automated pull request. I've run some checks against your code base to test whether you're using one of the deprecated apis, but this isn't the case.
Please test the changes against your code. I didn't run any tests and therefore can't guarantee that it isn't breaking. You can also just close this pr if you don't want to update your module.
In case there's already another pr open to upgrade uuid, I'm sorry for the effort I'm causing.

Coverage remained the same at 95.683% when pulling be8b06b3cfc35b9c6434a0c3fddbc7b09e3c6b70 on marcbachmann:update-uuid into 6c5d06c51b39699985650a9597e9a791087d38a6 on open-trail:master.


Add an option to select the start view

Problem
My camera is a bit slow and i have to wait for a few seconds every time i start the app.
Solution
As the title says, i'd like this app to have the option to select the start view.
I don't always want to scan something, so it would be more efficient for me to start the app on the history or the create fragment.
Pull request
I have implemented this functionality on my branch and will submit it shortly.
(I don't have much experience with commits and pull request so please be nice and feel free to correct me on my errors ^^ )

ok, i submitted a pull request now but i don't know how to mention it here :(


Fix code style and re-enabled IWYU

Updates the fix_all.sh script to take an optional IGNORE_GIT_DIFF environment variable
This allows fix_all.sh to run on all files, not just changes in this PR. Use with IGNORE_GIT_DIFF=1 ./ci/scripts/fix_all.sh
Updates the copyright.py to be better organized
Updates ci/scripts/common.sh with updated path regexes
Runs fil_all.sh on the repo and commited changes

Should go in after #719
Related to #713
Closes #732

/merge


[Docu]: Admonitions Readme 1.0

I am request a change on the...

[X] Readme
[ ] Publish Documentation

Located...
Entire Thing
The issue is...
It is Outdated now :)
In the case of needing more clarity, do you have any suggestions on what would make it clearer to you?
I have a write-up below. Of note, the final section does not specify TTRPG but instead suggests complementary plugins, which happens to be ttrpg plugins.

Writeup

🥇 Our documentation has moved here.

The Admonition plugin for Obsidian is a tool that allows you to create attention-grabbing callouts, tips, warnings, and other informative blocks within your notes. These blocks can be customized and styled to fit your specific needs, and can be easily added using the .callout and .admonition syntax. The plugin provides a range of pre-defined icons to choose from, as well as the ability to create your own custom styles using CSS.
Features

Supports a variety of built-in admonition types such as tip, warning, caution, note, and more.
Customizable styles with the ability to use Markdown attributes in callouts, or stylize directly with CSS.
Supports nesting of blockquotes and code-blocks.
It can be used in combination with other plugins such as Obsidian Templates or @SilentVoid13's Templater.
Supports import and export of custom admonitions via .json files.

Quickstart

Install the Admonition plugin from the Community Plugins pane in Obsidian.
Callout Version: In the editor, type out the name of an admonition type (such as > [!tip]) followed by your content.
Admonition Version: In the editor, type out the name of an admonition type in a code block (such as ```ad-tip) followed by your content on the subsequent lines
Preview your note to see the formatted admonition.

Check out the plugin documentation for more detailed instructions and examples.
Support
If you encounter any issues, want to give back and help out, or have suggestions for new features, please file an issue on the GitHub repository.
Complementary Plugins by Javalent
While we think all of our plugins are pretty awesome, we think these are especially awesome and work well with this plugin:

Obsidian Leaflet - Add interactive maps to Obsidian notes
Dice Roller - Inline dice rolling for Obsidian
Fantasy Statblocks - Format Statblocks inside Obsidian
Initiative Tracker - Track initiative and turns in Obsidian

Going to go ahead and add a few more tweaks and push this.


Add new regions and new instance types

High Level Description
What features does this change enable? What bugs does this change fix? High-Level description of how things changed.
Related Issues

DCOS- Foo the Bar so it stops Bazzing.
DCOS- TRACKING: dcosjira-123 Foo the Bar

Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@spahl @BenWhitehead @mellenburg defaulting to c4.xlarge instead of m3.
Any additional test coverage apart from the defaults? ( I am already testing the new regions )

Looks good to me and the @dcos/velocity-team!

@amitaekbote , the PR template needs an update to reflect the issue/state.

@amitaekbote here's the complete list of regions and AMIs I build yesterday:
CentOS 7.3.1611 with Docker 1.13
ap-northeast-1:ami-d93d69be
ap-northeast-2:ami-542efe3a
ap-south-1:ami-6b0b7b04
ap-southeast-1:ami-68da6a0b
ap-southeast-2:ami-21fefd42
ca-central-1:ami-266ed342
eu-central-1:ami-e80bde87
eu-west-1:ami-68dcf20e
eu-west-2:ami-22cedb46
sa-east-1:ami-5c9cfa30
us-east-1:ami-b4f128a2
us-east-2:ami-ff82a79a
us-west-1:ami-d4b3edb4
us-west-2:ami-b863e1d8
us-gov-west-1:ami-b91ba1d8

And latest CoreOS 1235.12.0 from https://stable.release.core-os.net/amd64-usr/1235.12.0/coreos_production_ami_all.txt
ap-northeast-1=ami-86f1b9e1
ap-northeast-2=ami-0c15c562
ap-south-1=ami-4530402a
ap-southeast-1=ami-27cc7d44
ap-southeast-2=ami-5baeae38
ca-central-1=ami-a97bc6cd
eu-central-1=ami-4733f928
eu-west-1=ami-89f6dbef
eu-west-2=ami-052b3e61
sa-east-1=ami-c51573a9
us-east-1=ami-42ad7d54
us-east-2=ami-69a3860c
us-west-1=ami-1a1b457a
us-west-2=ami-2551d145
us-gov-west-1=ami-a846fcc9

An issue I ran into was that the latest 2016 natami from https://aws.amazon.com/amazon-linux-ami/
wouldn't run out of the box with our CF templates.


⚠ PrivateHD has degraded performance

In c636b07, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 3237 ms

Resolved: PrivateHD performance has improved in fdc520b.


Update dependency xunit to v2.5.3

This PR contains the following updates:

Package
Type
Update
Change

xunit
nuget
patch
2.5.2 -> 2.5.3

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Investigate all UploadedFileHandler classes Django may use, and add to Gallery

Django apparently changes what handler-classes it uses based off of some criteria (like a threshold file size limit). The Gallery upload handler only takes InMemoryUploadedFile into account per now, and this must be changed to also include TemporaryFile and perhaps others that might be used.
Needs some extra research and thought, so it can follow the already implemented approach.

This was fixed in f2ca71d260450676e9de1eba012ffe97fc9c066a


Missing 0.1.56 pypi release

Describe the bug
There is no 0.1.56 release on pypi but there is a 0.1.56 tag on github.
Expected behavior
I should see a 0.1.56 release on pypi.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
python version
redis-py version
full requirements.txt?

Additional context
I can work around this by specifying the github repo and tag in my dependencies.
I couldn't find a way to remove the bug label but I think this is more of an operational thing than a bug.

thanks for notify me ,
fixed
https://github.com/alm0ra/mockafka-py/releases/tag/v0.1.57
https://pypi.org/project/mockafka-py/0.1.57/


Fix broken sky shader

Fix https://github.com/godotengine/godot/issues/96890

This fixes the sky shader, but it breaks the shader used to draw the origin lines:
This PR

Before this PR

4.4-dev2

@clayjohn Fixed, try again

Tested locally and confirmed that this works now


rust-client: Prepare v0.2.1

Follow-up patch release to https://github.com/libp2p/punchr/pull/64.
//CC @thomaseizinger and @elenaf9

Has someone looked into why the current release binary identifies itself as version 0.1.0?

Has someone looked into why the current release binary identifies itself as version 0.1.0?

Code looks okay, perhaps the binaries attached to the release have been built before the manifest was bumped?
What do other people's dashboards say? Mine says 0.1.0.

Has someone looked into why the current release binary identifies itself as version 0.1.0?

Code looks okay, perhaps the binaries attached to the release have been built before the manifest was bumped?
What do other people's dashboards say? Mine says 0.1.0.

Which binary are you using?

The x86 one attached to the last release.


[Feature Request] WebGL Support

As Mono supports WebAssembly now, and Veldrid supports OpenGL ES now, it seems to me that WebGL should be doable (right?), and it would be super useful (you'll be able to show live samples on you website, for example).
Based on the comment here: https://github.com/mono/mono/issues/7662#issuecomment-386653213, WebGL bindings will be developed in this repo: https://github.com/kjpou1/wasm-dom

WebGL support would be fantastic, and I would love to add it when the time comes. Right now, though, I'm not sure that we are close to having a .NET runtime that reliably works on wasm. I have been following the work on mono and CoreRT, and both of them still feel very early and experimental. Mono is further along, but as far as I know it is still running all IL through an interpreter, which makes it extremely slow. I'd be surprised if real-time 3D graphics work very well (if at all) under those conditions. That's not to say that we couldn't start building out a WebGL backend, but realistically you couldn't do much with it at the moment.
A couple of additional things I'm worried about:

CoreRT is being developed at the same time, and is probably a better technology in the long run. I don't want to develop against mono-specific WebGL bindings if we'd have to throw that out to run on CoreRT.
I want to keep Veldrid as a pure .NET Standard 2.0 library, and not rely on any mono-specific dependencies. Ideally, I can just write my own WebGL bindings and avoid this problem.

It certainly doesn't hurt to plan for the future, though, and I think we will eventually get to a point where targeting wasm with .NET is well-supported.
As for the implementation details, I haven't thought about it a ton, but a few things come to mind:

I don't think wasm supports multiple threads, at least not at the moment. I think there should be something like bool GraphicsDeviceOptions.SingleThreaded -- a switch that communicates that a GraphicsDevice will only be used from a single thread. I've wanted to add this for a while, because all of the backends incur a small amount of overhead dealing with thread safety. The OpenGL backend incurs even more overhead.
Related to the above: we won't need to do any lazy-construction of GL objects if you are in single-threaded mode.
I'm not sure exactly how creating a WebGL GraphicsDevice will work. I guess you will pass in some sort of WebGL context handle, but I haven't used WebGL before.
WebGL will probably need to be a separate GraphicsBackend value.
WebGL 2.0 will be required, since it's roughly on the level of OpenGL ES 3.0.

I implemented the "single-threaded mode" on this branch. I will likely merge it into master at some point. It removes at least one of the blockers above for WebGL support.

Thanks for information! I am very hopeful to Veldrid lives to wasm. I think who can helps your project - I am very excited to move to wasm. And we don't need to worry who doesn't like to download and install - Just wasm loads simple into browser. It looks like easy without plugin.
You know WebGL is pad performance. wasm is best like it is "embedded plugin" without installation like Flash Player or Silver Light or Media Player etc... Now we are using wasm because we don't need to merge plugins to all operating systems.
Since Death of Flash Player will be soon 2020. But Flash Player was great for gaming like Away3D and Pinball etc flash-based games were working. And HTML5 / WebGL 1 / 2 are maybe laggy. Now Webassembly has great solution like Quake into Webassembly and it works high powerful and has not problem with performance with browser like Android, iOS, PalmOS, Linux, MacOS and Windows and more..
 I know - I will help you if you are ready and to fix and prepare embedding sdl2-webassembly into Marshal function ( no DLL-Import )
I have tried to compile:
Download SDL2 from download of SDL2'S website
Unpack to build directory
Type :
emconfigure ./configure
emmake make
It seems successful but no SDL2.wasm or SDL2.pc only SDL2.a ( library of Linux )
Or
Mono's wasm should merge USE_SDL2=1 with SDL2 library - If we use SDL2-like frameworks like OpenTK, MonoGame, Veldrid or DeltaEngine etc...
Good luck for next development's build

I've started working on this now, potentially for the next release of Veldrid. It should be possible to get the WebGL backend roughly on-par with the existing OpenGL ES backend.

There's still quite a lot to figure out for this, but mono's wasm support seems to be viable enough to get things up and running now. I hope that the sample gallery (still in development on the side...) will also be able to run on WebGL.

Hello, any update on this?

Any updates in 2021?

Any updates in 2021?

Here is a native WebGL example. Seems nice.
https://github.com/AshleighAdams/dotnet6-webgl-sample


Fix ColumnUnknownException due to missing quotes in a subscript expression

..where the root column contains upper cases.
Example:
CREATE TABLE t ("OBJ" OBJECT AS (intarray int[]), firstElement AS "OBJ"['intarray'][1]);
ColumnUnknownException[Column obj['intarray'] unknown]

Summary of the changes / Why this improves CrateDB
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

retest this please
testKillUpdateByQuery
java.lang.AssertionError:
Expected: (an instance of io.crate.exceptions.JobKilledException or an instance of java.lang.InterruptedException or an instance of java.util.concurrent.CancellationException or an instance of io.crate.exceptions.TaskMissing)
     but: was <java.lang.RuntimeException: java.lang.InterruptedException>
	at __randomizedtesting.SeedInfo.seed([A76EEF85E33DC667:B02655F7E7095B5F]:0)
	at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
	at org.junit.Assert.assertThat(Assert.java:964)
	at org.junit.Assert.assertThat(Assert.java:930)
	at io.crate.integrationtests.KillIntegrationTest.assertGotCancelled(KillIntegrationTest.java:102)
	at io.crate.integrationtests.KillIntegrationTest.testKillUpdateByQuery(KillIntegrationTest.java:143)
	at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
	at java.base/java.lang.reflect.Method.invoke(Method.java:578)
	at com.carrotsearch.randomizedtesting.RandomizedRunner.invoke(RandomizedRunner.java:1758)
	at com.carrotsearch.randomizedtesting.RandomizedRunner$8.evaluate(RandomizedRunner.java:946)
	at com.carrotsearch.randomizedtesting.RandomizedRunner$9.evaluate(RandomizedRunner.java:982)
	at com.carrotsearch.randomizedtesting.RandomizedRunner$10.evaluate(RandomizedRunner.java:996)
	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
	at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
	at java.base/java.lang.Thread.run(Thread.java:1589)
```


Create a Portal Site

Tutorials: https://developers.sap.com/tutorials/cp-portal-cloud-foundry-create-site.html
Hi there, not sure if it's a problem on my end but I don't see the "Pages" tab in step 3.1 (see below screen shot). I do have the Portal_Admin role assigned to my user. Any idea why that is?

Hi sorry for not replying earlier - I was on vacation and missed the notification.  The Portal tutorials have been replaced by the Launchpad tutorials.  Please try this mission instead: https://developers.sap.com/mission.launchpad-cf.html
Thanks
Lindsay

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.

Thanks a lot @LindsayBert, but the UI theme designer documentation is still linking to this tutorial, so you might want to replace that link, too.

Hi - thanks for letting me know.
I'm not the author of the UI theme designer documentation but I will try and find out who it is.

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


Disable printing by default for DebugReducer when running SwiftUI Previews

I had a case where one of my features was lagging a lot without any apparent reason in a SwiftUI Preview. The motive became immediately clear when I launched a dedicated app and saw the console filled by a very large amount of data from a _printChanges() that I forgot.
I've added a preliminary check to the default _ReducerPrinter so they don't generate any output when running SwiftUI Previews. As this only affects the default printers, this behavior can be overridden by users willing to provide their own _ReducerPrinter implementation (for example with variants capable of displaying this information in SwiftUI Previews like experimented in #1234).
This should make SwiftUI Previews a little snappier when a ._printChanges() has been forgotten.
Please let me know what you think!

Good to know! We typically don't use this modifier outside the app entry point, but know it's common enough for folks to do, so avoiding pitfalls like this sounds good to us!

I refactored to use @Dependency(\.context) as a source of truth. This is indeed much nicer!

Is it possible to model _ReducerPrinter as a dependency?

@iampatbrown I think it was implemented as such at some point during the beta. But I'm not certain why it was rescinded. Likely because it wasn't worth the complexity at this stage.

@tgrapperon Ah k. That makes sense :)


build: enable gpu in dev-docker-compose

Summary
https://github.com/Lilypad-Tech/internal/issues/271

this is no longer required.


Traversable.[last]indexOfSlice(Iterable[,int])

Many thanks, great addition! It is good to have a fresh mind looking over the / and adding new functionality.

it's typical for me to forget <? extends T>

Me too!


Multiple btn-group's that include a submit do not align

The follow case where link buttons and input type=submit (or type=button) result in btn-group's not aligning within the btn-toolbar in all major browsers.

          Remove

      Cancel

My work around was to set chained .btn-group to margin-bottom the same value as .btn-toolbar, which isn't getting picked up by any chained .btn-group's. Here's the css override:
.btn-group + .btn-group {
margin-bottom: 9px;
}
Here's the original bootstrap 2.0 css:
.btn-group + .btn-group {
margin-left: 5px;
}
.btn-toolbar {
margin-top: 9px;
margin-bottom: 9px;
}

Dupe


Turn samples into challenge templates

I removed:

bash
apache-php

Renamed:

apache-others to web
challenge-skeleton to pwn (and made it a chal.c)

You can choose the template using kctf chal create --template foo (default is pwn since pwn is best challenge ;) )

ah this isnt gonna work
https://github.com/google/kctf/blob/beta/.github/workflows/update-images.yaml#L161

ah this isnt gonna work
https://github.com/google/kctf/blob/beta/.github/workflows/update-images.yaml#L161

ah this isnt gonna work
https://github.com/google/kctf/blob/beta/.github/workflows/update-images.yaml#L161

What do you mean?

ah this isnt gonna work
https://github.com/google/kctf/blob/beta/.github/workflows/update-images.yaml#L161

What do you mean?

oh, I missed you moved them to /tmp

oh, I missed you moved them to /tmp


Implemented tracksViewChanges for Android

Does any other open PR do the same thing?
No
What issue is this PR fixing?
This is related to the following issues:
#1870 #2105 #2048 #2082
How did you test this PR?
In my own project, with a progressing pie animation inside the marker.
I've also made sure that tracking stops when the marker is removed from the map etc.
Some background and explanation
iOS has the tracksViewChanges property which causes re-renders of the markers all the time, and slows down performance of the map greatly.
Still, it is very handy especially given the async nature of React.
As many times the first images cached is of a blank component, it is very useful to use tracksViewChanges=true and then set it to false when componentDidUpdate is hit.
Another issue is loading images. Assuming the image loading issue will be fixed one day - we will still want tracksViewChanges and disabled that when onLoadEnd hits.
We could even start with it as a false value, and then turn it on and off when the loading is done.
Now some people use several hacks for the image issue on Android, like actual changes to Fesco code and usage of SVG images inside the Marker. But in those cases it is still slightly unstable and sometimes blank - but just because of the asyncronisity of react. This will also solve that.
I've set a default fps of 25, which seemed reasonable to me. But based on user feedback this could be easily adjusted.

@alvelig LGTM but this is android , could you 🐽

LGTM


Performance improvements for isQuantifier

I created benchmark, please take look  https://github.com/bd82/regexp-to-ast/issues/17

o.k. this is very interesting.
It looks as though using a try/catch in a productive flow to signal failure of backtracking.
but not total failure of parsing results in almost 2 orders of magnitude performance hit.
This must be some edge case V8 is not optimizing

Thank you, when should we expect this changes to be released to chevrotain?

Today


Copy of #398: Add support for customization of validation error messages

This is https://github.com/envoyproxy/protoc-gen-validate/pull/398 but with the latest changes merged.
DISCLAIMER: NOT TESTED MANUALLY

I'm not sure where this error is coming from [error] failed post-processing: 820:39: missing ',' in argument list (and 10 more errors)

Hey @codyaray @rmichela @akonradi, would you happen to know the reason for the error above? I'm not familiar with Bazel :(

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

noooo

Not stale

@elliotmjackson would you mind explaining why this has been closed? Saying that bufbuild isn't interested in pursuing this would be at least good to know, if that's the reason, but the silence on this PR for almost a year (I know the ownership changed during this period) and then closing it without saying anything is a bit weird.

@Kernald  protovalidate, the next generation of this tool, supports custom validation using CEL expressions :)


keystone_authtoken parameters changed in Newton release

admin_user -> username
admin_password -> password
ad min_tenant_name -> project_name
identity_uri -> N/A

Fixed


Tc (traffic control) support in kernel

I'm trying to use tc in my C1 images, but some of the necessary kernel options are not active in any of the available kernel.
Would it be possible to enable them in the official images?
the required options are:
CONFIG_NET_SCH_CSZ=m
CONFIG_NET_QOS=y
CONFIG_NET_ESTIMATOR=y
CONFIG_NET_CLS_POLICE=y

Original issue: https://community.scaleway.com/t/tc-traffic-control-support-in-kernel/889

Hello, this is critical for me, the ticket was opened more than 3 months ago on scaleway's internal support.
When can I expect resolution?

Hi @Edzilla2000, we are sorry, we prioritize issues depending of the amount of concerned users
@QuentinPerez can you increase the priority of this issue ?

Hi @Edzilla2000, sorry I will do it tomorrow 😉

Hi @Edzilla2000,
Today I tried to add your configuration but all modules are obsolete.
Also I tried to run tc on (4.1.6/3.2.34) and it works fine.

Hi @QuentinPerez
I tried to run it on a recent kernel and it does indeed work.
I had tried on several kernels since the report was made to scaleway's internal support and it didn't work.
Thank you for pointing it out to me!
You can close the ticket I think.

Perfect, thanks


Configurable QUIRK_SET_ADDRESS_BEFORE_STATUS

The LPC55S69-EVK also requires this quirk to be set (messy + bugged WIP: https://github.com/nickray/lpc55s6x-hal/blob/towards-usbfsd/examples/usb.rs). I think currently it's not configurable, but it could/should be a feature?
Tangentially, what's the plan with the endpoint-trait branch? Trying to figure out if I should early-adopt or stick with master.

I believe you can override the default value here: https://github.com/nickray/lpc55s6x-hal/blob/c2b4a857c0f02f325025ba19f7ef0bf96f91b948/src/usbfs/bus.rs#L86

Oh I didn't know this was possible, this works. Thanks!


Release v2.1.0 (into master)

@kcw-grunt Merge conflicts fixed!

Card disclaimer added @mosadialiou ?

Card disclaimer added @mosadialiou ?

Sorry, not yet! I will add it by tomorrow.
In the meantime tet's roll out this release ASAP since it fixes some major crashes.

Card disclaimer added @mosadialiou ?

Sorry, not yet! I will add it by tomorrow.
In the meantime tet's roll out this release ASAP since it fixes some major crashes.

@mosadialiou No, we need both platforms to release at the same time so the marketing/messaging matches. Let me know when you can get it done.  This was the goal for the disclaimer.  And most of the Card customers wanted information are Android users.


Python 3 port

Here are the patches from the Debian package of geneagrapher which port it from Python 2 to Python 3:
https://salsa.debian.org/science-team/geneagrapher/-/tree/master/debian/patches
The patches were based on aad59e9, so I took a little time to rebase them on top of the current head of the master branch.
I also added an additional patch I wrote for the Debian package which copies the test data to the build directory.
Note that a number of the tests are failing.  Most of them because the Mathematics Genealogy Project is currently down.  (Hopefully that gets fixed soon or this is all pointless!)  But there's also several related to cache lengths, e.g.:
======================================================================
FAIL: test_close (tests.geneagrapher.test_cache_grabber.TestCacheGrabberMethods)
Test the close method.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/profzoom/src/geneagrapher/geneagrapher/tests/geneagrapher/test_cache_grabber.py", line 63, in test_close
    self.assertEqual(len(cache.cache), 0)
AssertionError: 2 != 0

Closes: #22

Thank you for the PR, @d-torrance! It looks like there will be more work to do (like updating the base URL, overcoming the SSL verification issue mentioned in #22, and getting tests passing), but this helps a lot.


msvc warnings

Warning	C26439	This kind of function may not throw. Declare it 'noexcept' (f.6).		src\entt\meta\meta.hpp	403
Warning	C26495	Variable 'entt::basic_registry<enum entt::entity>::pool_data::type_id' is uninitialized. Always initialize a member variable (type.6).		src\entt\entity\registry.hpp	118
Warning	C26495	Variable 'entt::basic_registry<enum entt::entity>::pool_data::stamp' is uninitialized. Always initialize a member variable (type.6).		src\entt\entity\registry.hpp	118
Warning	C26495	Variable 'entt::basic_registry<enum entt::entity>::pool_data::remove' is uninitialized. Always initialize a member variable (type.6).		src\entt\entity\registry.hpp	118
Warning	C26495	Variable 'entt::basic_registry<enum entt::entity>::pool_data::assure' is uninitialized. Always initialize a member variable (type.6).		src\entt\entity\registry.hpp	118

I've suppressed the warnings on the registry. On the other side, the one for meta_any is a false positive.
meta_any works with raw storage (literally a bunch of bytes) in which it constructs objects using a placement new.
The move constructor may or may not invoke the move constructor for the underlying object and therefore the noexcept-ness of the swap is conditionally valid. However, since one of the functions it uses is erased (in particular steal_fn), we lose the information about is noexcept-ness. Because of this, the move constructor cannot be declared as 'noexcept` as well.
I've no idea on how to suppress it but making the move constructor noexcept would be wrong.


Prettier error messages if package.json is missing

Change %f into %s because strings are not floats (doh!)
Make fs.stat async, because async
If package.json is missing, assume no plugins and display a warning

Change %f into %

Wonder what happened there.
LGTM
@lukeed

Not sure ¯_(ツ)_/¯
Looks good to me. Eventually we'll want to emit the package.json error, so that everything is consistently being caught & displayed by the reporter, but that can't be done right now without binding plugins.js into the Fly instance, which isn't something I want to do for the time being...
Thanks @IvanSanchez !

Releasing as v1.2.3

Thanks @IvanSanchez! 👍


When creating the dockerfile, you should be able to pass environment variables to the file

For various reasons, I need to be able to pass the ENV parameter into the Dockerfile created by kitchen docker in order to get SystemD running as outlined at https://rhatdan.wordpress.com/2014/04/30/running-systemd-within-a-docker-container/
It would be good to see the option to provide ENV along side the current RUN and CMD sections of the file.

Probably overkill to support this via the Yaml, just provide your own Dockerfile template.

In my use-case you're probably right, however assuming that people still develop 12-factor applications or similar and want to test those here too, I suspect setting the ENV in the default config would be useful.
More than anything else, I didn't want to have to replicate the majority of the default Dockerfile as a template when I only really want to change a couple of lines! :)

Closing, no longer required.


Bump rustc to 1.61

For the old code, I would have used the https://doc.rust-lang.org/std/thread/struct.JoinHandle.html#method.is_finished method to cancel the initial
timeline logical size calculation.
Now that makes less sense due to async rewrite, but generally bumping rustc is beneficial to keep up with the pace and to catch oddities earlier.


No contract in SimpleCollectible ContractContainer :(

Followed the exact steps in README but I get the following. Does anyone know what I'm doing wrong?
lucascheon@Lucass-MacBook-Pro nft % brownie run scripts/simple_collectible/create_collectible.py
Brownie v1.14.6 - Python development framework for Ethereum

NftProject is the active project.

Launching 'ganache-cli --port 8545 --gasLimit 12000000 --accounts 10 --hardfork istanbul --mnemonic brownie'...

Running 'scripts/simple_collectible/create_collectible.py::main'...
development
  File "brownie/_cli/run.py", line 49, in main
    return_value, frame = run(
  File "brownie/project/scripts.py", line 103, in run
    return_value = f_locals[method_name](*args, **kwargs)
  File "./scripts/simple_collectible/create_collectible.py", line 11, in main
    simple_collectible = SimpleCollectible[len(SimpleCollectible) - 1]
  File "brownie/network/contract.py", line 158, in __getitem__
    return self._contracts[i]
IndexError: list index out of range
Terminating local RPC client...

Thanks for making this! You're not using a --network rinkeby on your command.
When you don't use a network flag, it will default to a local network. This will deploy an NFT based on a contract that has already been deployed. On a local ganache that brownie spins up, no contract has been deployed yet.
You'll have to run the script in order on a persistent blockchain. The built-in brownie network doesn't persist the blockchain.
Closing for now, but feel free to follow up.

Hey Patrick. Thanks for the quick response. I'm new to blockchain in general so my questions might be very n00b-ish.
I ran the simple deploy script first and then ran the create script next. Is this what you meant by "running script in order"?
In general, could you elaborate more on what I should be doing to deploy a contract on my local ganache?

If you want to deploy to your local ganache, you'll have to run the scripts in order as you mentioned, and add a persistent ganache chain to your list of networks.
brownie networks add Ethereum ganache host=http://localhost:8545 chainid=1337

Then run the 2 scripts with a --network ganache flag


error TS2339: Property 'setupInterceptor' does not exist on type 'BrowserObject'.

Hello,
It looks like the service is not working with typescript, is their a way to fix it ?
steps to reproduce :
# clone a typescript boilerplate
$ git clone git@github.com:jpolley/WebdriverIO_v5_TypeScript.git
$ cd WebdriverIO_v5_TypeScript

# install dependencies
$ npm i

# check this spec is working
$ npm test -- --spec dropdown.spec.ts

# install intercept service
$ npm i --save-dev wdio-intercept-service

# add intercept to wdio conf, ie. `services: ['selenium-standalone', 'intercept']`
$ sed -i.bak -E "s/(services: \['selenium-standalone')\]/\1, 'intercept'\]/" wdio.conf.js
# add an intercept step to a spec ie. `return browser.url('/dropdown').setupInterceptor();`
$ sed -i.bak -E "s/(return browser.url\('/dropdown'\));/\1.setupInterceptor();/" src/pages/DropdownPage.ts

# run it, it's not working :(
$ npm test -- --spec dropdown.spec.ts
npm info it worked if it ends with ok
npm verb cli [
npm verb cli   '/usr/local/Cellar/node/12.8.0/bin/node',
npm verb cli   '/usr/local/bin/npm',
npm verb cli   'test',
npm verb cli   '--',
npm verb cli   '--spec',
npm verb cli   'src/pages/DropdownPage.ts'
npm verb cli ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm verb run-script [ 'pretest', 'test', 'posttest' ]
npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>npm info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>
><EMAIL_ADDRESS>test /Users/user/WebdriverIO_v5_TypeScript
> wdio "--spec" "src/pages/DropdownPage.ts"

Execution of 1 spec files started at 2020-01-20T22:36:48.267Z

2020-01-20T22:36:48.269Z DEBUG @wdio/utils:initialiseServices: initialise wdio service "selenium-standalone"
2020-01-20T22:36:48.304Z DEBUG @wdio/utils:initialiseServices: initialise wdio service "intercept"
2020-01-20T22:36:48.306Z INFO @wdio/cli:launcher: Run onPrepare hook
2020-01-20T22:36:49.568Z INFO @wdio/local-runner: Start worker 0-0 with arg: --spec,src/pages/DropdownPage.ts
[0-0] 2020-01-20T22:36:49.779Z INFO @wdio/local-runner: Run worker command: run
[0-0] RUNNING in chrome - /src/pages/DropdownPage.ts
[0-0] 2020-01-20T22:36:49.947Z DEBUG @wdio/utils:initialiseServices: initialise wdio service "intercept"
[0-0] 2020-01-20T22:36:49.948Z DEBUG @wdio/local-runner:utils: init remote session
[0-0] 2020-01-20T22:36:49.949Z INFO webdriverio: Initiate new session using the webdriver protocol
[0-0] 2020-01-20T22:36:49.950Z INFO webdriver: [POST] http://<IP_ADDRESS>:4444/wd/hub/session
[0-0] 2020-01-20T22:36:49.950Z INFO webdriver: DATA {
  capabilities: { alwaysMatch: { browserName: 'chrome' }, firstMatch: [ {} ] },
  desiredCapabilities: { browserName: 'chrome' }
}
[0-0] 2020-01-20T22:36:52.350Z ERROR @wdio/runner: TSError: ⨯ Unable to compile TypeScript:
src/pages/DropdownPage.ts(5,41): error TS2339: Property 'setupInterceptor' does not exist on type 'void'.

    at createTSError (/Users/user/WebdriverIO_v5_TypeScript/node_modules/ts-node/src/index.ts:261:12)
    at getOutput (/Users/user/WebdriverIO_v5_TypeScript/node_modules/ts-node/src/index.ts:367:40)
    at Object.compile (/Users/user/WebdriverIO_v5_TypeScript/node_modules/ts-node/src/index.ts:558:11)
    at Module.m._compile (/Users/user/WebdriverIO_v5_TypeScript/node_modules/ts-node/src/index.ts:439:43)
    at Module._extensions..js (internal/modules/cjs/loader.js:879:10)
    at Object.require.extensions.<computed> [as .ts] (/Users/user/WebdriverIO_v5_TypeScript/node_modules/ts-node/src/index.ts:442:12)
    at Module.load (internal/modules/cjs/loader.js:731:32)
    at Function.Module._load (internal/modules/cjs/loader.js:644:12)
    at Module.require (internal/modules/cjs/loader.js:771:19)
    at require (internal/modules/cjs/helpers.js:68:18)
[0-0] Error: ⨯ Unable to compile TypeScript:
src/pages/DropdownPage.ts(5,41): error TS2339: Property 'setupInterceptor' does not exist on type 'void'.

[0-0] 2020-01-20T22:36:52.373Z INFO webdriver: COMMAND deleteSession()
[0-0] 2020-01-20T22:36:52.373Z INFO webdriver: [DELETE] http://<IP_ADDRESS>:4444/wd/hub/session/f3c1a49088665b5cb89c5ce92b87383d
2020-01-20T22:36:52.553Z DEBUG @wdio/local-runner: Runner 0-0 finished with exit code 1
[0-0] FAILED in chrome - /src/pages/DropdownPage.ts
2020-01-20T22:36:52.554Z INFO @wdio/cli:launcher: Run onComplete hook
2020-01-20T22:36:52.554Z INFO @wdio/selenium-standalone-service: shutting down all browsers

Spec Files:      0 passed, 1 failed, 1 total (100% completed) in 00:00:04

2020-01-20T22:36:52.555Z INFO @wdio/local-runner: Shutting down spawned worker
2020-01-20T22:36:52.807Z INFO @wdio/local-runner: Waiting for 0 to shut down gracefully
2020-01-20T22:36:52.808Z INFO @wdio/local-runner: shutting down
npm verb lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
npm verb lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/user/WebdriverIO_v5_TypeScript/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands
npm verb lifecycle<EMAIL_ADDRESS>CWD: /Users/user/WebdriverIO_v5_TypeScript
npm info lifecycle<EMAIL_ADDRESS>Failed to exec test script
npm ERR! Test failed.  See above for more details.
npm verb exit [ 1, true ]
npm timing npm Completed in 5456ms
npm verb code 1

Thanks for any help.

Hello,
@chmanie
I'm running into this same issue
Property 'setupInterceptor' does not exist on type 'BrowserObject'.ts(2339)
on
"wdio-intercept-service": "^4.1.3",
"_from"<EMAIL_ADDRESS>What's the fix here?
Thank you

https://stackoverflow.com/questions/59132068/property-setupinterceptor-does-not-exist-on-type-browserobject
this seems a fix.
Add wdio-intercept-service in your tsconfig.json's types section

Happy you could resolve it!
The Readme also has an example 😉


Add support docker -e option

Add new configuration setting "environments" that enable to set the environment variable(s) to the executed process by run_command.

Environment variable support was added as part of PR #340 and included in the 2.10 release. Please submit a new PR if updates are still needed. Thanks!


Use of undefined constant INTL_IDNA_VARIANT_UTS46 in 2.10 release

Using PHP 5.6.24:
/vendor/zendframework/zend-validator/src/EmailAddress.php:557 Use of undefined constant INTL_IDNA_VARIANT_UTS46 - assumed 'INTL_IDNA_VARIANT_UTS46'
In PHP 5.6.28 the constant is defined.

According to https://3v4l.org/elX65, the constant is available in PHP 5.4.0. I'm guessing the intl extension uses the ICU system lib and your server has a really old version of the ICU lib. Support for UTS #46 Unicode IDNA Compatibility Processing was added in ICU 4.6 and released on 2010-12-02.

Thank you for your assistance @xtreamwayz. We were running a very old ICU lib version.


WIP,MNT: Migrate to ipyvtklink

Starting from 0.30.0, pyvista uses ipyvtklink instead of ipyvtk_simple.
In server_environment.yml, ipyvtk_simple is still installed so I expect the CIs to come back green with 71792d6 but after the release, it will fail because show() will return a static image instead of the expected Viewer widget.
It's an item of https://github.com/mne-tools/mne-python/issues/8704

Related to https://github.com/pyvista/pyvista/pull/1257

There might be a way to fail sooner if for example PyVista throws (ValueError?) when the requested backend is not available/does not exist.

Finally, I'll remind that although ipyvtk is fully included in our environment and codebase, it's still experimental. From the README.md:

This is an early prototype of creating a Jupyter interface to VTK. This toolkit is a proof of concept and a more polished tool will be available as ipyvtk in the future.

A simple way to address this is to bump the requirements to pyvista>=0.30.0 altogether.

Probably same treatment for pyvistaqt>=0.4.0

pip-pre is green, it's a good sign :)

This should be updated after https://github.com/mne-tools/mne-python/pull/8741 is merged because plotter.iren.FindPokedRenderer is not valid anymore starting pyvista 0.30.0.


Name or service not known errors are not retried

The _hc_retry_on_exception function only retries ConnectionError when the underlying exception is BadStatusLine. In this case, we got a socket.gaierror('Name or service not known'). See the full traceback below:
ConnectionError: ('Connection aborted.', gaierror(-2, 'Name or service not known'))
  File "sh_scrapy/crawl.py", line 127, in _run_usercode
    _run(args, settings)
  File "sh_scrapy/crawl.py", line 89, in _run
    _run_pkgscript(args)
  File "sh_scrapy/crawl.py", line 110, in _run_pkgscript
    d.run_script(scriptname, {'__name__': '__main__'})
  File "dist-packages/pkg_resources.py", line 1235, in run_script
    execfile(script_filename, namespace, namespace)
  File "scrapy/tmp/eggs-cJgpCT/__main__.egg/EGG-INFO/scripts/run-script.py", line 55, in <module>
    maybe_capture_errors(main, settings)(settings)
  File "usr/lib/python2.7/dist-packages/raven/base.py", line 681, in wrapper
    return func(*funcargs, **funckwargs)
  File "scrapy/tmp/eggs-cJgpCT/__main__.egg/EGG-INFO/scripts/run-script.py", line 50, in main
    target(**kwargs)
  File "ompostprocess/cli.py", line 192, in main
    spider_name = hs_job.metadata['spider']
  File "hubstorage/resourcetype.py", line 202, in __getitem__
    return self._data[key]
  File "hubstorage/resourcetype.py", line 178, in _data
    r = self.apiget()
  File "hubstorage/resourcetype.py", line 39, in apiget
    return self.apirequest(_path, method='GET', **kwargs)
  File "hubstorage/resourcetype.py" line 32, in apirequest
    return jldecode(self._iter_lines(_path, **kwargs))
  File "hubstorage/resourcetype.py", line 27, in _iter_lines
    r = self.client.request(**kwargs)
  File "hubstorage/client.py", line 100, in request
    return self.retrier.call(invoke_request)
  File "dist-packages/retrying.py", line 206, in call
    return attempt.get(self._wrap_exception)
  File "dist-packages/retrying.py", line 247, in get
    six.reraise(self.value[0], self.value[1], self.value[2])
  File "dist-packages/retrying.py", line 200, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "hubstorage/client.py", line 92, in invoke_request
    r = self.session.request(**kwargs)
  File "usr/lib/python2.7/dist-packages/requests/sessions.py", line 461, in request
    resp = self.send(prep, **send_kwargs)
  File "usr/lib/python2.7/dist-packages/requests/sessions.py", line 573, in send
    r = adapter.send(request, **kwargs)
  File "usr/lib/python2.7/dist-packages/requests/adapters.py", line 415, in send
    raise ConnectionError(err, request=request)

Another exception candidate to be retried:
Traceback (most recent call last):
  File "/tmp/eggs-IKoTZB/__main__.egg/ompostprocess/cli.py", line 212, in main
    db = runner.run()
  File "/tmp/eggs-IKoTZB/__main__.egg/ompostprocess/core.py", line 202, in run
    db = pipe.run(self, db)
  File "/tmp/eggs-IKoTZB/__main__.egg/ompostprocess/pipelines/__init__.py", line 163, in run
    return self.process(db)
  File "/tmp/eggs-IKoTZB/__main__.egg/ompostprocess/pipelines/mongo.py", line 167, in process
    or not self.is_within_instock_thresholds()
  File "/tmp/eggs-IKoTZB/__main__.egg/ompostprocess/pipelines/mongo.py", line 327, in is_within_instock_thresholds
    last_stats = self.get_last_stats()
  File "/tmp/eggs-IKoTZB/__main__.egg/ompostprocess/pipelines/mongo.py", line 380, in get_last_stats
    return self.hs_statscol.get(_key=self.spider.name)['last_stats']
  File "/usr/lib/python2.7/dist-packages/hubstorage/collectionsrt.py", line 103, in get
    return self._collections.get(self.coltype, self.colname, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/hubstorage/collectionsrt.py", line 12, in get
    r = self.apiget((_type, _name, _key), params=params)
  File "/usr/lib/python2.7/dist-packages/hubstorage/resourcetype.py", line 39, in apiget
    return self.apirequest(_path, method='GET', **kwargs)
  File "/usr/lib/python2.7/dist-packages/hubstorage/resourcetype.py", line 32, in apirequest
    return jldecode(self._iter_lines(_path, **kwargs))
  File "/usr/lib/python2.7/dist-packages/hubstorage/resourcetype.py", line 27, in _iter_lines
    r = self.client.request(**kwargs)
  File "/usr/lib/python2.7/dist-packages/hubstorage/client.py", line 100, in request
    return self.retrier.call(invoke_request)
  File "/usr/lib/python2.7/dist-packages/retrying.py", line 206, in call
    return attempt.get(self._wrap_exception)
  File "/usr/lib/python2.7/dist-packages/retrying.py", line 247, in get
    six.reraise(self.value[0], self.value[1], self.value[2])
  File "/usr/lib/python2.7/dist-packages/retrying.py", line 200, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "/usr/lib/python2.7/dist-packages/hubstorage/client.py", line 92, in invoke_request
    r = self.session.request(**kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 461, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 573, in send
    r = adapter.send(request, **kwargs)
  File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 415, in send
    raise ConnectionError(err, request=request)
ConnectionError: ('Connection aborted.', error(104, 'Connection reset by peer'))

Other unhandled exception when reading metadata:
ConnectionError: ('Connection aborted.', error(110, 'Connection timed out'))
  File "sh_scrapy/crawl.py", line 127, in _run_usercode
    _run(args, settings)
  File "sh_scrapy/crawl.py", line 89, in _run
    _run_pkgscript(args)
  File "sh_scrapy/crawl.py", line 110, in _run_pkgscript
    d.run_script(scriptname, {'__name__': '__main__'})
  File "dist-packages/pkg_resources.py", line 1235, in run_script
    execfile(script_filename, namespace, namespace)
  File "scrapy/tmp/eggs-Ue3TjE/__main__.egg/EGG-INFO/scripts/run-script.py", line 55, in <module>
    maybe_capture_errors(main, settings)(settings)
  File "usr/lib/python2.7/dist-packages/raven/base.py", line 681, in wrapper
    return func(*funcargs, **funckwargs)
  File "scrapy/tmp/eggs-Ue3TjE/__main__.egg/EGG-INFO/scripts/run-script.py", line 50, in main
    target(**kwargs)
  File "ompostprocess/cli.py", line 192, in main
    spider_name = hs_job.metadata['spider']
  File "hubstorage/resourcetype.py", line 202, in __getitem__
    return self._data[key]
  File "hubstorage/resourcetype.py", line 178, in _data
    r = self.apiget()
  File "hubstorage/resourcetype.py", line 39, in apiget
    return self.apirequest(_path, method='GET', **kwargs)
  File "hubstorage/resourcetype.py", line 32, in apirequest
    return jldecode(self._iter_lines(_path, **kwargs))
  File "hubstorage/resourcetype.py", line 27, in _iter_lines
    r = self.client.request(**kwargs)
  File "hubstorage/client.py", line 100, in request
    return self.retrier.call(invoke_request)
  File "dist-packages/retrying.py", line 206, in call
    return attempt.get(self._wrap_exception)
  File "dist-packages/retrying.py", line 247, in get
    six.reraise(self.value[0], self.value[1], self.value[2])
  File "dist-packages/retrying.py", line 200, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "hubstorage/client.py", line 92, in invoke_request
    r = self.session.request(**kwargs)
  File "usr/lib/python2.7/dist-packages/requests/sessions.py", line 461, in request
    resp = self.send(prep, **send_kwargs)
  File "usr/lib/python2.7/dist-packages/requests/sessions.py", line 573, in send
    r = adapter.send(request, **kwargs)
  File "usr/lib/python2.7/dist-packages/requests/adapters.py", line 415, in send
    raise ConnectionError(err, request=request)


Invalid section type

Hi,
Trying to install the plugin. Yet getting the error you can see with the attached screenshot. I installed through composer and here's the blueprint file which just shows I've used the example from the installation docs. Probably a really easy fix but I can't understand why it's not working.
sections:       seo: seo/site       albums: sections/albums       clients: sections/clients       statements: sections/statements
Thanks.

It's not a section but a tab. Please read the docs again


⚠ Samsung has degraded performance

In d3ff19f, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2700 ms

Resolved: Samsung performance has improved in 07ace76.


Allow parameter matching in arg of decorator on

Allows parameter matching of non #-route args for the on-decorator:
@on('button_{id}')
async def button_clicked(q: Q, id):

Predicates and value arguments also work, e.g.
@on('button_{id}', lambda x: True)
async def button_clicked(q: Q, arg_value, id):

Type conversion:
@on('button_{id:int}')
async def button_clicked(q: Q, id):

Multiple params:
@on('button_{id1}:{id2}')
async def button_clicked(q: Q, id1, id2):

Fixes #1008

Thanks for the PR @Far0n! Changes look good. Maybe we can push this out in 0.23? The routing docs need an update as well.

Happy to help with the documentation. Guess starter would be to update the doc-string of def on, but what are other places?


Specto favourites are gone

Hi, since the last update 2<IP_ADDRESS> all the tv shows that i put in favourites are gone. When i try to search the tv shows not all off them are found... i can find Narcos but the blacklist, hawaii five 0 and Zoo for example are not found.
What is wrong?

You have a couple choices at this time.
1 - Uninstall the filmkodi repository then go to the link below and get
specto plugin
2<IP_ADDRESS> install this and all you favorites will come back. Hopefully a
new update
may fix the problem. wait for few days and install the repository.
http://kodi.filmkodi.com/plugin.video.specto/
2 - Add all your favorites all over again. You will first have to remove an
item from favorites and then add it again as all your shows are still
technically in your favorites, they just don't show up.
On Sep 19, 2016 3:48 AM, "Zalinas"<EMAIL_ADDRESS>wrote:
Hi, since the last update 2<IP_ADDRESS> all the tv shows that i put in
favourites are gone. When i try to search the tv shows not all off them are
found... i can find Narcos but the blacklist, hawaii five 0 and Zoo for
example are not found.
What is wrong?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/492, or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7A5_7D0t6pOTsSI6JvQiUMR5WzYTks5qrj5NgaJpZM4KANtr
.

If you choose #1, this means you need to turn off auto-update as this fix
just rolls you back to an earlier update and any new update applied will
wipe it. It's unclear when or if there will be an official fix from Mr.
Know.
On Sep 19, 2016 3:48 AM, "Zalinas"<EMAIL_ADDRESS>wrote:

Hi, since the last update 2<IP_ADDRESS> all the tv shows that i put in
favourites are gone. When i try to search the tv shows not all off them are
found... i can find Narcos but the blacklist, hawaii five 0 and Zoo for
example are not found.
What is wrong?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/492, or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7A5_7D0t6pOTsSI6JvQiUMR5WzYTks5qrj5NgaJpZM4KANtr
.

Should also add that fix #1 is courtesy of user mageorge. This topic was
already gone over in a previous post where mageorge came through with it.
On Sep 19, 2016 3:48 AM, "Zalinas"<EMAIL_ADDRESS>wrote:

Hi, since the last update 2<IP_ADDRESS> all the tv shows that i put in
favourites are gone. When i try to search the tv shows not all off them are
found... i can find Narcos but the blacklist, hawaii five 0 and Zoo for
example are not found.
What is wrong?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/492, or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7A5_7D0t6pOTsSI6JvQiUMR5WzYTks5qrj5NgaJpZM4KANtr
.

BakruptEd thnx for your reply.
I will try this today and let you know if it works.

If u do it correctly it will work. It's been proven many times over
already. What I don't like is you can't get any future updates until an
official fix comes through. I've decided to go the tedious way and simply
reenter my favorites. I just hope  I don't have to do this regularly. I had
lots of fav's. Big hassle even remembering half of them.
On Sep 20, 2016 2:10 AM, "Zalinas"<EMAIL_ADDRESS>wrote:

BakruptEd thnx for your reply.
I will try this today and let you know if it works.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/492#issuecomment-248210844,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7BKUbwItJSB-o-6o0KX8XyZyc1ABks5qr3jYgaJpZM4KANtr
.

It works!  Too bad that we have to waut now for an officialfix.  But thnx for the help!

No worries. Just trying to pay back the help I've received. Peace
On Sep 21, 2016 3:25 AM, "Zalinas"<EMAIL_ADDRESS>wrote:

It works! Too bad that we have to waut now for an officialfix. But thnx
for the help!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/mrknow/filmkodi/issues/492#issuecomment-248532274,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUPc7ByDSpBehoUEyaKAhlcsNPtb9_yQks5qsNvdgaJpZM4KANtr
.

update add-on. And manualy re create favorites


Temperature decimal correction and other features

Tado (Connect) is displaying correct temperature from thermostat on mobile smartthings application.
However, it is not properly set as decimal type, since ActionTiles can not pickup decimals (only integer) from current temperature sensor. So this needs to  be fixed.
Also, it will be good to be able to have sensor/button way, that ActionTiles can send info about setting back to auto - Tado scheduled temperature, and not manual.
I believe this all is related to Tado (connect) smartthings app, that does not expose "the correct" value and datatypes.
Btw, great app :)

@hkusulja This project is now discontinued, i no longer have access to the smartthings platform which is undertaking a large amount of change. please create a pull request with the required changes and i will merge


[WIP] Optimization/space cleanup

Pull Request Test Coverage Report for Build 682

2 of 4 (50.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 93.587%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

hyperparameter_hunter/optimization/backends/skopt/engine.py
0
1
0.0%

hyperparameter_hunter/space/dimensions.py
1
2
50.0%

Totals

Change from base Build 680:
-0.04%

Covered Lines:
4524

Relevant Lines:
4834

💛  - Coveralls