The compiler isn't required to define a static constructor.

In the section on static constructors, this sentence is misleading:
> If you don't provide a static constructor to initialize static fields, the C# compiler will supply a default static constructor that initializes static fields to their default value as listed in the Default Values Table.
The C# spec on default values declares that the GC or runtime may be responsible for initializing fields (static or instance) to their default value. A compiler generated static constructor is not required.
The document on type initialization exceptions should have a similar update.

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

ID: 754eaea9-3482-4a69-5b65-ebe4a5065597
Version Independent ID: 7f3cd611-9d80-4523-6ba5-17e1e9ab5c67
Content: Constructors - C# Programming Guide
Content Source: docs/csharp/programming-guide/classes-and-structs/constructors.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Thanks for following through with the issue. A few other articles with similar phrasing:
CA1810: Initialize reference type static fields inline

When all static data is initialized inline and an explicit static constructor is not declared, Microsoft intermediate language (MSIL) compilers add the beforefieldinit flag and an implicit static constructor, which initializes the static data, to the MSIL type definition.

CA2207: Initialize value type static fields inline

If all static data is initialized inline and no explicit static constructor is declared, the C# and Visual Basic compilers add the beforefieldinit flag to the MSIL class definition. The compilers also add a private static constructor that contains the static initialization code. This private static constructor is guaranteed to run before any static fields of the type are accessed.


Multiple Models in View

will mvc support multiple models in a view in next versions?
for example with alias
@model  ...User as userModel
@model  ...Role as roleModel

There are two options we recommend for this situation:

Create a new type, e.g. CombinedUserAndRoleModel that has properties for each of the sub-models.
Use ViewData to store the extra models, e.g. ViewData["User"] = new UserModel();

@Eilon I know that ways, I did not ask how to do that in mvc, I asked will mvc support multiple models.
because this way will be more elegant and does not CombinedUserAndRoleModel  break single responsibility?

@numankizilirmak there are no plans to support that in a direct fashion.


InternetAddress.lookup throws an error when runs with timeout which returns empty list in onTimeout callback

If we try lookup for a host like this
final foundAddresses =
          await InternetAddress.lookup('smth.com').timeout(
        const Duration(milliseconds: 300),
        onTimeout: () => [],
      )

We get an error:
type '() => List<InternetAddress>' is not a subtype of type '(() => FutureOr<List<_InternetAddress>>)?' of 'onTimeout'
Dart version 2.12.2, macOS 11.2.1

Thank you for reporting this problem!
https://dart-review.googlesource.com/c/sdk/+/193720 should have the fix.


MRG: add filter_path function

See the third task in #122.
Please review, @alannaiverson, @aksam-ahmad, @jcpalumbo3, @sicihuang, @togawa28

Coverage increased (+1.2%) to 51.24% when pulling e493cadf287c3ccaae1b60b7fa25a865ddbcd684 on jJasonWang:filterpath-issue122 into 58d15430ddeb09e3fb0fcd90213cc419dce5e141 on berkeley-stat222:master.

Coverage increased (+1.8%) to 43.649% when pulling 569ca01c6f4073f5b9e84d06f4ec786556ebad8a on jJasonWang:filterpath-issue122 into 7f1027ca36f1bd947c4525efed3f155dea9c0cc3 on berkeley-stat222:master.

Coverage increased (+1.6%) to 47.708% when pulling 7849375d2095844fe80a7fc08dafc5c93666bf99 on jJasonWang:filterpath-issue122 into 4a83e2dddbb63750d5fda889e2b8306ddbb4275c on berkeley-stat222:master.

Coverage increased (+1.6%) to 47.708% when pulling 4d0cd3a7b00418a434dc2f8050b8cb6ccca5702b on jJasonWang:filterpath-issue122 into 4a83e2dddbb63750d5fda889e2b8306ddbb4275c on berkeley-stat222:master.

@alannaiverson, I updated the commit. Please review again, thank you.

@jJasonWang Looks good to me, I'd say it's ready to MRG

Coverage increased (+1.4%) to 51.307% when pulling 5dcf8d45ec47d5eb77c6799c16299431d464ab8b on jJasonWang:filterpath-issue122 into 19116d4bdb0dea4f7ad02f0e8d09bfdc7cb5409a on berkeley-stat222:master.

@jJasonWang I just merged another pull request.  As soon as you rebase, ping me and I will merge this pull request next.

Coverage increased (+1.4%) to 51.307% when pulling d707d5da7840a5212c9bcb50eece50b32ca3615c on jJasonWang:filterpath-issue122 into d55d7135dafc137ed2bc4609d57579afedc74c82 on berkeley-stat222:master.

I rebased it. Please merge it, @jarrodmillman. Thanks!


Absorb some code from dwave.embedding

On #148 @arcondello brought up the idea of relocating some code from dwave.embedding into minorminer.  On review, the relevant files would be:
polynomialembedder.py
chimera.py
diagnostic.py
pegasus.py
exceptions.py

done in #170


VSCode creating several new 'Untitled.ipynb' files

Bug: VSCode creating several new 'Untitled.ipynb' files
The same issue referenced here happened to me, and as suggested I raise this issue here. Quoting the original problem:
- VSCode Version: 1.42.1
- OS Version: macOS Catalina 10.15.3

# Steps to Reproduce:

Connect to a Jupiter Notebook server with Python extension via 'Specify Jupyter server URI' running on docker server.
VS Code then creates several new 'Untitled.ipynb' files.
Is this a setting I have missed or is it a bug?

## Expected behavior

A safer option would be to create those notebooks inside a system temporary folder.

Hey @we-taper . Thanks for filing this issue. We do indeed create a couple of untitled notebooks that we clean up after. While we can't avoid creating these with our current implementation we do want to do a better job of keeping them out of the way. We have issue:
#10411
Filed for this, would that issue cover your request?

Hi @IanMatthewHuff , thanks for the reply. Yes it will solve and clearly this issue is a duplicate of #10411 .

Sounds good. I'm going to close this issue since the existing one will cover it. Just follow that issue if you want to track our progress on that.


Style/TrailingCommaInArrayLiteral: Do not check for coma if there is a square bracket

Description
I have those rules defined :
Style/TrailingCommaInArrayLiteral:
  EnforcedStyleForMultiline: consistent_comma

Style/TrailingCommaInHashLiteral:
  EnforcedStyleForMultiline: consistent_comma

And this code :
content_sources(:answers_domain_test).update(
  foreign_categories: [{
    id: "1",
    optional: false,
    item_name: "Gimme the color pnuk",
    name: "Color",
    categories: [{ id: "123", name: "Red" }, { id: "456", name: "Blue" }],
  }]
)

And I have this error message :
C: Style/TrailingCommaInArrayLiteral: Put a comma after the last item of a multi
line array.
          }]
          ^

So I have to replace the }] by },] which give :
content_sources(:answers_domain_test).update(
  foreign_categories: [{
    id: "1",
    optional: false,
    item_name: "Gimme the color pnuk",
    name: "Color",
    categories: [{ id: "123", name: "Red" }, { id: "456", name: "Blue" }],
  },]
)

I find this code ugly.
Possible solution
I suppose Rubocop can check if there is a curly brace or square bracket just after the curly brace in problem.
Other option
Disable the rule.

You could start the hash on a new line, like this:
  foreign_categories: [
    {
      id: "1",
      ...
    },
  ]

IMHO this looks a lot better than the },]


When to call useStaticRendering, and how many times?

Should useStaticRendering be called once, as part of the server application's init routine? Should it be called once for each request? Should it be called at some point in every component that is an observer? The docs explain the function and why it's needed, but I'm unclear as to when and where to call it.
Thanks!

Should be called only once :)
Op di 10 jan. 2017 om 20:19 schreef Ryan Cole<EMAIL_ADDRESS>
Should useStaticRendering be called once, as part of the server
application's init routine? Should it be called once for each request?
Should it be called at some point in every component that is an observer?
The docs explain the function and why it's needed, but I'm unclear as to
when and where to call it.
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mobxjs/mobx-react/issues/192, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABvGhNm_URZyB2cAy1MJ9m5C2Xfxp634ks5rQ9mygaJpZM4LfyrC
.

Great, thanks!


fix: Lock loki.secretfilter's mutex for reading while processing logs

PR Description
Lock the component's mutex for reading while processing logs to avoid concurrency issues when the component is updated.
Which issue(s) this PR fixes

None
Notes to the Reviewer
I initially forgot to lock the component's mutex for reading while processing the logs, so I guess that could cause issues during component updates.
The component hasn't been released yet so I suppose updating the changelog isn't needed.
PR Checklist

N/A

@grafana/grafana-alloy-maintainers hey team! Could you please have a look at this short PR when you have some time? 😄


Add synchronization between crypto3 submodules PRs

We want to implement CI/CD pipeline, where different submodules of crypto3 will be tested with respect to each other PRs, if all those PRs are linked to the same issue using [SyncWith org/repo#issue] syntax in PR's title.
Current issue will be used for testing of this functionality

Related PR: NilFoundation/crypto3-multiprecision-marshalling#14 (SHA: 2e80c30b04da954a52197eb2625bdcfc11deb530)

Related PR: NilFoundation/crypto3-multiprecision-marshalling#14 (SHA: b8dea5eb8203605fa508addf7580fc81318c09f5)

Related PR: NilFoundation/crypto3-multiprecision-marshalling#14 (SHA: 43a95b2c9b807a6980c036f4d68a0b676798802d)

Related PRs:

Related PRs:

Related PRs:
Note: Please do not edit this comment; it's generated automatically.

:[{"repo": "NilFoundation/crypto3-multiprecision-marshalling", "number": 14, "sha": "e21e4f2bcef19fa217e62fb30e53114211381ac7", "url": "https://github.com/NilFoundation/crypto3-multiprecision-marshalling/pull/14"}] -->
Related PRs:

[NilFoundation/crypto3-multiprecision-marshalling#14](https://github.com/NilFoundation/crypto3-multiprecision-marshalling/pull/14) (SHA: e21e4f2bcef19fa217e62fb30e53114211381ac7)

Note: Please do not edit this comment; it's generated automatically.

Related PRs:

[NilFoundation/crypto3-multiprecision-marshalling#14](https://github.com/NilFoundation/crypto3-multiprecision-marshalling/pull/14) (SHA: e21e4f2bcef19fa217e62fb30e53114211381ac7)

Note: Please do not edit this comment; it's generated automatically.

Related PRs:

NilFoundation/crypto3-multiprecision-marshalling#14 (SHA: e21e4f2bcef19fa217e62fb30e53114211381ac7)

Note: Please do not edit this comment; it's generated automatically.

PRs, synced with the current issue:

NilFoundation/crypto3-multiprecision-marshalling#14 (SHA: e21e4f2bcef19fa217e62fb30e53114211381ac7)

Note: Please do not edit this comment; it's generated automatically.

PRs, synced with the current issue:

NilFoundation/crypto3-multiprecision-marshalling#14 (SHA: e21e4f2bcef19fa217e62fb30e53114211381ac7)

Note: Please do not edit this comment; it's generated automatically.

Related PRs:

Related PRs:

Related PRs:

Related PRs:


Environment variable support for configuration

thank. :heart:
cc @daurnimator

Hmm, as in an environment variable setting the location of the config file, or specific config entries being populated with env variables? If the latter, there may be a way to do that already via yaml's weird builtins

The second. I think kodah might have mentioned something relevant?

Yeah if we can make it clean and simple then coolcool. Having a separate blah-env-variable entry in the config file is uuugly and probably confusing.
If we don't find a nice clean yaml way to do this and still want to support it: Rather than e.g. what we did for the secret cloak key env var, if we do end up supporting this we can just skip the config file altogether and have ora just load the ORAGONO_BLAH env vars if they exist and ignore those entries in the config file. have a really obvious warning message on startup, e.g. BLAH, BLAH, and BLAH are being loaded from ENVIRONMENT VARIABLES and NOT the config file.. If we want to we could even add a command line flag like --ignore-env-vars to force us to just ignore all of them.

if we do end up supporting this we can just skip the config file altogether and have ora just load the ORAGONO_BLAH env vars if they exist and ignore those entries in the config file.

That would be ideal for most things. However, I do see one issue where this becomes a bit difficult, which is the list/dict variables, like the opers config. It might also be useful to allow multiple configuration files (or an "include" option) instead of env vars. The reason this came about was because we have a Kubernetes setup, and I'd like to have one file which is the base config (i.e. allow from local traffic, configure where to load TLS certs from, base amount of connections, etc.), and I'd like to have another file which is instance-specific, such as the network/server name, allowed origins for websockets, IP cloaking address, and oper classes/oper blocks.
This would mean users would only have make a ConfigMap for the things they want to override, like the above variables.
I realize that this may also complicate things, but I think this may be a cleaner solution given you'd otherwise have to deal with how to load lists/maps from environment variables.

Sounds like you could do this externally with templating/scripting?

A real-world example: our integration test suite can modify the config programmatically from Python, then dump it as JSON for consumption by Oragono (since valid JSON is valid YAML).

Sounds like you could do this externally with templating/scripting?

I would like to avoid overriding the entrypoint of the oragono container, and there's not really a way to automatically template or script configs without adding all the necessary components into the Docker container.

Anyway the docker-compose.yml file should be at the root of the project with environment variables defining the important variables of the server. Currently, it is not obvious how to launch the project with docker-compose.

I'm a fan of twelve-factor apps -- I think configuration is the only facet of that where Ora really falls down.
Using something like https://github.com/caarlos0/env it could be fairly straight-forward to add some extra tags to the config struct and some parsing logic. I'm not sure how it should interact with the yaml config if it exists - the easiest way is probably to just have a flag to switch entirely between them. Then the docker entrypoint can default to using that flag and the compose file can include the necessary vars.
If there were strong objections to doing that then it could be done in the existing entrypoint script which already does some config munging to set the oper password. I feel like that would get very messy very quickly, but it'd be nicer than end-users trying to do their own versions and having to override the entrypoint and keep it up-to-date. (I'd much rather get rid of that shell script entirely rather than make it more important, so we can avoid having a shell and all its accoutrements in the container).

This looks like a templating problem to me, tbh
Just my 2c

I'll think more about this; I'm not really up to date on best practices with Docker at all.
In particular, I don't understand the tradeoffs between putting things "inside" and "outside" the container. The ircd.yaml file ends up on a "volume" outside the container, right? So in principle, couldn't it be templated using tools that exist outside of the container? What's the role of the entrypoint in all this?
My main concern is that environment variables don't seem like they can be as expressive as YAML, or at least not without sacrificing cleanliness and visibility. If I squint, I can see a solution where we have environment variables like ORAGONO_config.server.websockets.allowed-origins, and then the value that variable takes is YAML or JSON that gets deserialized into Config.Server.Websockets.AllowedOrigins (there are some implementation challenges here). But it's hard for me to see this as a full replacement for the current YAML config file; it seems really cumbersome and unmaintainable to do a line-by-line translation of a fully functional oragono config into environment variables.

Oh, by the way, any thoughts on the narrow issue of moving docker-compose.yml to the root of the project?

In particular, I don't understand the tradeoffs between putting things "inside" and "outside" the container. [...]

 You can maintain plain text config files outside of that, and you can write some tooling to automate that, but the more you go that way the more you're going against the grain and losing benefits.
e.g. you can get ora running right now by doing docker run -p 6697:6697 oragono/oragono. If you then wanted to change the server name from "oragono.test" to "irc.example.com" and ora supported env vars it'd be something like:
docker stop $CONTAINER
docker run -p 6697:6697 -e SERVER_NAME=irc.example.com oragono/oragono

whereas with a config file it's:
docker cp $CONTAINER:/some/path/I/don't/remember/config.yml .
docker stop $CONTAINER
vi config.yml
// Edit the config, hope you don't make yaml syntax errors, etc
docker run -p 6697:6697 -v ./config.yml:/some/path/etc/config.yml oragono/oragono

Running multiple instances with small differences (e.g. different hostnames) is obviously a lot easier with env vars, as is keeping track of state (I can see exactly what env vars each container is running with, whereas I can only see the current state of the config file and hope the instances have been rehashed since it last changed). Finally, upgrading feels a lot nicer with env vars (the base image defines some new defaults, I override them if I want) vs config files (I have to manually merge the new config fields, or start from a new default config, or bury my head in the sand and ignore them; if the config file has incompatible changes I need to manage the editing and the upgrading of the containers in sync, etc).

My main concern is that environment variables don't seem like they can be as expressive as YAML, or at least not without sacrificing cleanliness and visibility

Yes, for sure. I wouldn't try and configure, say, haproxy using env vars, but I think Ora's config is not actually that complex? If you flatten all the namespacing I think there's only a few bits that wouldn't fit straight into a KEY=value or KEY="value1 value2 value3" structure. I'm having a hard time deciding how messy that would make the current config code without actually giving it a try...

What's the role of the entrypoint in all this?

The entrypoint is just the executable that's started when the container starts. Ideally for a go app it'd just be the statically compiled binary, and the image would have almost nothing else in it.
In practice, we have a small script as the entrypoint that (if needed) installs a default config, generates a random oper password, creates self-signed certs, then launches oragono itself. If we didn't want Ora itself to worry about environment variables, this script could potentially edit the config if there are env vars present, but that brings its own world of mess (and would probably be better done in python not shell script, which then drags python into the image as well...)

Oh, by the way, any thoughts on the narrow issue of moving docker-compose.yml to the root of the project?

I'm personally ambivalent. I'd usually put it at the root for my projects, but it's no skin off my nose if it's elsewhere and pointed at by the README (as it is now for Ora). Some software has example compose files inline in the docs or on the website, it's not a hard and fast rule that it should exist in the root of the repo.
(Thank you for attending my TED talk on environment variables.)

Thanks for this very detailed analysis, I learned a lot :-)
This side-by-side comparison (for changing the server name) seems to be eliding details that would be necessary for actual productionization. You wouldn't actually have important configuration data floating around on a command line somewhere, you'd have it in some kind of versioned file (I think this is the ConfigMap concept in k8s?) So in the end the workflows are going to look much more similar than in this example.

Finally, upgrading feels a lot nicer with env vars (the base image defines some new defaults, I override them if I want) vs config files (I have to manually merge the new config fields, or start from a new default config, or bury my head in the sand and ignore them; if the config file has incompatible changes I need to manage the editing and the upgrading of the containers in sync, etc).

I don't think this accurately reflects real-world issues with upgrading Oragono. In particular:

The forwards and backwards compatibility guarantees for config files are fairly strong; most releases do not require any changes
Typically, when a new section of the config is added, it gates new functionality that operators may not want to enable by default. The idea is that upgrades should be as safe and nondisruptive as possible.
When the proper way to minimize disruption is to enable the field when unset, or to give it a default value, we have the capability to do this as well (e..g, recover-from-errors and force-trailing)
On the rare occasions when we ship genuinely backwards-incompatible changes (for example, the transition from server.listen to server.listeners), it seems likely that the compatibility issues would affect environment variables as well, except in the case where the user has not modified that section of the config

Anyway, as long as I can get it to work in a reasonably clean way with reflect, I'm OK with implementing the scheme described earlier (where ORAGONO_config.server.websockets.allowed-origins contains actual YAML that can be deserialized into the relevant field). Would that be sufficient?

I think Ora's config is not actually that complex? If you flatten all the namespacing I think there's only a few bits that wouldn't fit straight into a KEY=value or KEY="value1 value2 value3" structure.

Oper blocks (which came up earlier as part of hashbang's use case) are a good example of something that doesn't fit neatly into this framework --- hence Ryan's interest in "include" directives or the equivalent.

@csmith: just wanted to get your opinion on the proposal (ORAGONO_config.server.websockets.allowed-origins contains YAML that can be deserialized into the relevant field)

@csmith: just wanted to get your opinion on the proposal (ORAGONO_config.server.websockets.allowed-origins contains YAML that can be deserialized into the relevant field)

I don't think this is a good idea. Usually you'd see e.g. comma separated values; or perhaps JSON; or they're left out of env var support.

All valid JSON is valid YAML, so that seems fine, no?

I'd like more feedback on above proposal if this is going to make it into 2.4 :-)

TL;DR: Sounds great! :+1:
Sorry for not replying earlier. I was completely swamped with work at the time and then, well, forgot about it :)

This side-by-side comparison (for changing the server name) seems to be eliding details that would be necessary for actual productionization.

Yes, fair point, it's slightly more complex, but it still basically comes down to something like "configure things via a standard key/value method" vs "figure out whatever particular config format this app is using, where it needs to be placed on the file system, etc".

I don't think this accurately reflects real-world issues with upgrading Oragono.

Again, fair points. I was speaking in mostly hypotheticals and you've taken good care to avoid the problems there.

Anyway, as long as I can get it to work in a reasonably clean way with reflect, I'm OK with implementing the scheme described earlier (where ORAGONO_config.server.websockets.allowed-origins contains actual YAML that can be deserialized into the relevant field). Would that be sufficient?

As a minor point, I'd much prefer if they could be styled like ORAGONO_SERVER_WEBSOCKETS_ALLOWED_ORIGINS (as in, uppercase and with underscores instead of other punctuation).
Using YAML values seems fine to me. I believe most of the simple options will "just work" because plain strings/numbers/bools are all valid YAML? e.g. ORAGONO_SERVER_STS_ENABLED=true or ORAGONO_SERVER_NAME=irc.example.com.
If you do want to put the more complicated stuff in environment variables it's not actually that inelegant if it's yaml on both ends (which is true for docker-compose and k8s). You can do something like:
  environment:
    ORAGONO_OPERS: |
      chris:
        class: "server-admin"
        whois-line: "etc"
      slingamn:
        class: "etc"
    ORAGONO_SOMETHING_ELSE: "..."

(Where the | operator makes everything under it into a scalar. YAML is such a weird beast sometimes...)
Obviously that's pushing what's sensible and personally I'd probably be reaching for the proper config at that point, but it works and isn't hideous.

I don't think this is a good idea. Usually you'd see e.g. comma separated values; or perhaps JSON; or they're left out of env var support.

I think it's fine to have the option. The stuff on the more complex-end of the spectrum like oper blocks won't be everyone's cup of tea, but strings/bools/ints/etc will just work, and lists using the JSON-esque syntax of [foo, bar, baz] aren't a big deal IMO.

Thanks!

As a minor point, I'd much prefer if they could be styled like ORAGONO_SERVER_WEBSOCKETS_ALLOWED_ORIGINS (as in, uppercase and with underscores instead of other punctuation).

The motivation for the other syntax was that it would be easier to parse --- in particular, you could split on ., whereas with your example syntax it's hard to tell whether a _ indicates a new field access or is just a replacement for a space in a field name.

Ah, yeah, I wasn't sure if you were planning to iterate the env vars and map them onto the config struct, or iterate the config struct and look for matching env vars. . isn't a deal breaker, it's just a bit unusual (most shells won't let you easily export an env var with a . in it, but it is doable and technically valid so shouldn't be an issue when configuring via docker/k8s/etc).
Alternatively what about dropping dashes entirely, then _ becomes your splitable divider? e.g. ORAGONO_CHANNELS_DEFAULTMODES. Makes the matching a bit more fiddly than using dots, but a lot easier than the quoted example where you can't tell where to split.

Ah, good point about .. It looks like bash doesn't like - either.
I'm looking for a solution where no special casing is required at all, and the config handling code can process environment variables based only on the preexisting struct tags and the reflect package.
I think this would work for me: ORAGONO__SERVER__WEBSOCKETS__ALLOWED_ORIGINS , i.e., two underscores is the field separator, and then the field names just have to be converted from "screaming snake case" to "kebab case" (ALLOWED_ORIGINS to allowed-origins).


[OpenCV] Looking for installed/include/libpng/, but installed contains include/libpng16 only

On Windows 10 (1709 / 16299), VS2017, latest vcpkg from git -
Building OpenCV x64-windows - I have repeatedly observed an error where includes are looking for libpng/libpng.h, but the files are located in libpng16 after the libpng package is built.
For example,
D:\vcpkg\buildtrees\opencv\x64-windows-v140-dbg\CMakeFiles\CMakeTmp\CheckIncludeFile.c(1): fatal error C1083: Cannot open include file: 'D:/vcpkg/installed/x64-windows-v140/include/libpng/png.h': No such file or directory [D:\vcpkg\buildtrees\opencv\x64-windows-v140-dbg\CMakeFiles\CMakeTmp\cmTC_cd014.vcxproj]
I can solve this by manually copying libpng16 to just installed/include/libpng, but a more permanent fix would be preferred...

it's not a problem for OpenCV. Inside the building scripts, it looks for that header first, but if not it looks into another position, which is the one used by vcpkg, and it succeeds!

Hi @themikem  @cenit , this bug has been fixed, plz update vcpkg and reinstall opencv with command:
vcpkg remove opencv
vcpkg install opencv[png]:x64-windows
Thx.

Hi @themikem , thanks for reporting this issue!
I cannot repro on my WM, do you?
Please open a new issue if this is still a problem for you.
Thx.

+1 having same issue

@peererror please open an new issue.
Thanks.

Having the same issue..


Adding -mjs.js build to support polymer-cli

Coverage remained the same at 94.309% when pulling 151b7456c35417c5602c7731cf4f163edfc96b2c on cloudily:feature-polyer_cli_support_for_mjs into f67d5c2ccedae5f23605286cf513525396c1eb18 on pladaria:master.

Hi, thank you for this PR
Before accepting it I need some more context. Why do you need this?
How does polymer-cli know about the newly created artifact? It is not listed in package.json.
It is this following some kind of naming convention?
Thanks

Hi @pladaria,
The mjs extension has not been formalized yet.  It is currently recognized by node, but not by some build tools.  For example, the polymer-cli throws an error with the unrecognized mjs extension.  This is to provide build tools a way to interpret these files as they relate to ES imports.  Please let me know if you have any further questions.

All clear! Thank you for your explanation

published 4.1.10 with that change

Thanks, @pladaria


THRIFT-5230: Fix connection leak and CancelledKeyException when handl…

please refer to https://issues.apache.org/jira/browse/THRIFT-5230

Seems not needed then ...


Repositioning of pills Navigation bar

Early Years:

In the breadcrumbs, "Overview" should say "Life stage overview"
-In the pills and breadcrumbs, "Early Years Provision" should say "Educational provision"
-Spacing between breadcrumbs, contents drop-down, title and content is a bit tight on mobile. See image

@tkeburia @cameronramsay @carinapope13 @rjkerrison @sjltaylor


Adds slice loop mode

Slice sample from C-2 up to the number of slices set in instrument

@democloid I'd say it's extensively tested and stable, I've used it in many projects.

@djdiskmachine now that you have a picotracker to test on, did you still want to keep going with this PR? I think it currently just needs to merge in from main and resolve a conflicts in SampleInstrument.cpp

@djdiskmachine now that you have a picotracker to test on, did you still want to keep going with this PR? I think it currently just needs to merge in from main and resolve a conflicts in SampleInstrument.cpp

Yeah I can try to take a look at it this evening =)


[Bug] Lifetime difference in the extra accounts and normal account

Description
Currently, we cannot use extra acconts  in combinations with normal accounts to create for example a CpiContext to perform a CPI due to lifetime conflicts.
Notes
Modify how extra accounts macro inject the helpers and set proper lifetimes: https://github.com/magicblock-labs/bolt/blob/main/crates/bolt-lang/attribute/extra-accounts/src/lib.rs#L80

Hi, @GabrielePicco , sorry for leaving comment here without your agreement and respecting the team rule. Because I wanna contribute to MagicBlock team's development and join your team, so I am going to solve issues. So could you give me some issue to be solved quickly as test task?


Issue 123: Specify the project main module

Set the sync-function-loader module as the primary entry point (aka the main module) for the npm project so that a dependent project can generate a sync function programmatically by invoking require('synctos').load('/path/to/my-doc-definitions.js').
Addresses issue #123.

Ready for another review.

Looks good! 👍


@mzikherman => Artwork Brick Middleware

Went down a couple different routes but this turned out to be the simplest. This is a first step for the global artwork brick; subsequent PR's will start swapping out brick code with this implementation. Whats going on:

Middleware is mounted and for every request attach a renderArtworkBrick function to locals
From template code call that function with props
Inside renderArtworkBrick, import Reaction's artwork brick and passes props to it, and then run ReactDOM.renderToString to output a mountable interface

Todo in separate PRs:

Ensure that Reaction artwork brick can be used without Relay. Right now harmless warnings are being thrown in the console due to a hack component parent wrapper I wrote a while back to get around the Relay network layer requirement (see https://artsy.slack.com/files/U3UNN0FQT/FA7QQJ12P/screen_shot_2018-04-16_at_7.32.52_pm.png)
Ensure Reaction artwork brick utils like favoriting can be used without relay
Swap out bricks where encountered in code

(Merging from offline convo with @mzikherman 👍)

This looks like a fantastic approach/start to me! 🍾


ARM template name field is generated with invalid value for API Management named value

Bicep version
Bicep CLI version 0.12.1 (e43d137c2d)
Describe the bug
When deploying an Azure API Management named value, the name that is produced by the ARM template does not pass ARM validation.
To Reproduce

Create an API Management instance (any instance will do - Consumption tier takes the shortest amount of time)
Use the following bicep file:

@description('The name of the API Management service instance')
param apimServiceName string = 'apim${uniqueString(resourceGroup().id)}'

resource apimService 'Microsoft.ApiManagement/service@2021-12-01-preview' existing = {
  name: apimServiceName
}

resource namedValue 'Microsoft.ApiManagement/service/namedValues@2021-12-01-preview' = {
  name: 'cosmoscontainer'
  parent: apimService
  properties: {
    displayName: 'Named Value cosmos-container'
    secret: false
    value: 'default'
  }
}

Apply to the API Management instance that you created.  (I used az deployment group create -g test --template-file ./named-value-test.bicep)
Additional context
Add any other context about the problem here.
You will get the following validation error:
{
    "status": "Failed",
    "error": {
        "code": "DeploymentFailed",
        "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
        "details": [
            {
                "code": "BadRequest",
                "message": "{\r\n  \"error\": {\r\n    \"code\": \"ValidationError\",\r\n    \"message\": \"One or more fields contain incorrect values:\",\r\n    \"details\": [\r\n      {\r\n        \"code\": \"ValidationError\",\r\n        \"target\": \"name\",\r\n        \"message\": \"Invalid NamedValue name may contain only letters, digits, periods, dashes and underscores.\"\r\n      }\r\n    ]\r\n  }\r\n}"
            }
        ]
    }
}

That's because the ARM template that is defined is this:

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
    "contentVersion": "<IP_ADDRESS>",
    "parameters": {
        "apimServiceName": {
            "defaultValue": "[format('apim{0}', uniqueString(resourceGroup().id))]",
            "type": "String",
            "metadata": {
                "description": "The name of the API Management service instance"
            }
        }
    },
    "resources": [
        {
            "type": "Microsoft.ApiManagement/service/namedValues",
            "apiVersion": "2021-12-01-preview",
            "name": "[format('{0}/{1}', parameters('apimServiceName'), 'cosmoscontainer')]",
            "properties": {
                "displayName": "Named Value cosmos-container",
                "secret": false,
                "value": "default"
            }
        }
    ]
}

The name property contains a / because bicep adds <servicename>/ to the front of the name, which makes it invalid according to the validation rules in ARM.

Try this:
@description('The name of the API Management service instance')
param apimServiceName string = 'apim${uniqueString(resourceGroup().id)}'

resource apimService 'Microsoft.ApiManagement/service@2021-12-01-preview' existing = {
  name: apimServiceName
}

resource namedValue 'Microsoft.ApiManagement/service/namedValues@2021-12-01-preview' = {
  parent: apimService

  name: 'cosmoscontainer'
  properties: {
    displayName: 'Named Value cosmos-container'
    secret: false
    value: 'default'
  }
}

By using the parent keyword, we will automatically handle the segmented naming requirements.

The original posted bicep file already has the parent keyword, just immediately after the name.  Also, I posted the wrong thing (I posted one with a format command in it which I was testing with to see if bicep just passed through formats un-adjusted.
I've updated the original comment, and I copy/pasted your example (in case ordering was an issue).  Same error message occurs.

Removing pre-flight validation with the following definition:
resource namedValue 'Microsoft.ApiManagement/service/namedValues@2021-12-01-preview' = {
  name: 'apim4i7mlnacygmho/cosmoscontainer'
  properties: {
    displayName: 'Named Value cosmos-container'
    secret: false
    value: 'default'
  }
}

And my command line az deployment group create -g test --template-file ./named-value-test.bicep - still produces the same error.

Following up on this, the problem was in the provider.  Although the error message says that "name" is wrong, it's actually "displayName" that is failing validation.  Service team is correcting the error message in a future release, but deploying (after I corrected the displayName) is now working.

wow what a red herring :) Glad we got it resolved!


Update automation-create-runas-account.md

This is stated:
"You create an Automation account but decline to create the Run As account."
As far as I can figure out this is only true for the Portal. New-AzureRmAutomationAccount does not allow you to create a Run As Account.

@theheatDK : Thanks for your contribution! The author, @georgewallace, has been notified to review your proposed change.

@theheatDK Thank you for your contribution.  I agree the initial sentence can be confusing. I would suggest instead though we change it to "You create an Automation account but do not create the Run As account."  This covers the scenario of the portal as well as someone doing it through PowerShell and not creating a run as account afterwards.  If you could modify your PR with this verbiage I would be happy to sign off and get this merged.

@theheatDK : Thanks for your contribution! The author, @georgewallace, has been notified to review your proposed change.

Thanks @georgewallace, I have made the change.

#sign-off Thanks!


Automated Latest Dependency Updates

This is an auto-generated PR with latest dependency updates.

Out of date


How to use in Angular & Ionic

Thank you for your contribution.
I currently need to use your component in my Angular & Ionic application to transform * .png images to * .webp. The problem is that I cannot install it because it is not compatible. I'm something new in this, but since your library doesn't have the types, that's why it doesn't recognize it.
I appreciate any help.

Hi Henry,
I too face the same issue with Angular compatibility. Is there any other package or option available for webp conversion on angular. Thanks in advance for the help.


ui: token scopes label fix

Signed-off-by: Krzysztof Nowak<EMAIL_ADDRESS>

Before:

After:

Deprecated by #103


Remove end of line comments (#US-SOUTH) from .env in multi-bot

Can you please remove end of line comments (#US-SOUTH) from .env in multi-bot as well

You can edit the file yourself and make a pull request: https://github.com/watson-developer-cloud/botkit-middleware/edit/master/examples/multi-bot/.env


Increase the validation of the Manifest content

I think it is also necessary to validate these two fixed values in the Manifest
Signed-off-by: zhouhao<EMAIL_ADDRESS>

On Thu, Oct 20, 2016 at 01:19:42AM -0700, Zhou Hao wrote:

I think it is also necessary to validate these two fixed values in
the Manifest

I agree.  But @stevvooe has been working to keep all intra-blob JSON
validation in image-spec 1, and you can perform this check in JSON
Schema.  I've just filed opencontainers/image-spec#404 with the JSON
Schema analog of this PR.

This validation belongs upstream.


UI: Android a11y "select to speak" reads "video video"

Turn on "select to speak" in Android a11y settings
Open the demo with the new UI
Touch the floating "select to speak" button
Touch an element of the video controls, such as the mute button

Result:
The screen reader says "video video", then reads the mute button.  It seems to be reading out all overlapping elements at that point on the screen.
Expected:
Only the touched element (such as mute button) would be read aloud.

I have used VoiceOver on macOS and I no longer experience this issue.


[DOCFIX] Add docs Deploy-Alluxio-Fuse-for-Deep-Learning.md

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10402/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10433/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10436/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10437/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-PR-Builder/10438/
Test PASSed.

/lgtm
/approve

alluxio-bot, merge this please


Not comparing Minecraft versions accurately

I've updated my server to 1.9. In MSCS there is a part of the script that decides what to display when I run the map command (both before and after I run it). Here's one of those parts so you know what I'm talking about:
    if [ $(compareMinecraftVersions $(getServerVersion $1) 1.7) -ge 0 ]; then
        sendCommand $WORLD 'tellraw @a {
          "text" : "",
          "extra" : [
            {
              "text" : "[Server] Mapping is complete. You can access the maps "
            },
            {
              "text" : "here",
              "color" : "aqua",
              "clickEvent" : {
                "action" : "open_url",
                "value" : "'$MAPS_URL'/'$WORLD'"
              }
            },
            {
              "text" : "."
            }
          ]
        }'
    else
        sendCommand $1 "say Mapping is complete.  You can access the maps at:"
        sendCommand $1 "say $MAPS_URL/$WORLD"
    fi
  fi

For some reason, it's not going to the first if block and instead is going to the else block (I tested this by printing out something in the else block and it indeed printed) even though it should since the server is greater than 1.7.
I think this might be an issue with how it's checking versions--perhaps something changed? (Relevant Issue #117

This block only compares the version so it can use the enhanced say command found in versions 1.7 and higher

This is a duplicate of #117. The versions.json file at the old location does not have a version 1.9, so there is no time value for the algorithm to work with.  The new location has 1.9, so simply updating the url should fix this.  However, my perl regex that handles the file may no longer be sophisticated enough, and may need some work.  I'll take a closer look at this tomorrow.

I just downloaded the old versions.json and it does have a listing for 1.9

Huh, I must have looked at a cached copy.  You are right, 1.9 is listed in the old location

I wonder what the issue is, and if it happens on my servers.  Again, I'll take a closer look tomorrow.

I don't have a fix yet, but I can confirm that it is not working for me either.  I'll take a closer look at the code that does this over the next couple of days and come up with a fix.

The code was failing because version 1.7 is not listed in the file.  I assume it used to be, because this code used to work.  Anyway, the fix was just changing the version compared to 1.7.2 with commit b02423dbe814cb866cffddf7dbc0efe51e72ca9d.


LogIn

Subject: LogIn
Description:
Tried to login
Results:
Just signed up, received the welcoming email. When I tried to log in, it says "username not found".
Backend version: develop-b3cee755
Frontend version: develop-b3cee755
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36
Page: https://couchers.org/login
User:

not enough info or can't reproduce


Fixes the following issues: #982, #986, #989

OPS Build status updates of commit 6692b2b:
:clock10: Full build: the average full build time is 34 min(s) 24 sec(s), this is based on the last 59 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

OPS Build status updates of commit 6692b2b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-1.5.0/create-azure-service-principal-azureps.md
:white_check_mark:Succeeded
View (azps-1.5.0)

docs-conceptual/azps-1.5.0/using-psjobs.md
:white_check_mark:Succeeded
View (azps-1.5.0)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


User/role permissions for using slash commands

Hello, I've implemented slash commands successfully in a bot but haven't found permissions implemented in this library yet, as described in https://discord.com/developers/docs/interactions/slash-commands#permissions and the four subsections describing the API calls for those permissions (get guild permissions for all commands in a guild, get permissions of a single command in a guild, edit a single command in a guild, bulk edit permissions in a guild)
I've already taken steps to add this functionality myself in the following pull request #943. Feedback is welcomed in either location

One thing I've noticed in the docs under the permissions part is the default_permissions, which can optionally be sent on creating and editing a command. If set to false, it means the command is disabled until a permissions overwrite exists on that command.
It's a little vague on how best to implement this as the default boolean value is 'false' which could be fatal for many commands made that assume that creating a command without special intervention enables it for everyone. This is also what's implied via the discord API docs since the field is optional.

Merged in d5bacb5401a6652f48edfbf133fd55a159b95b18


Fix test workflows

next.js for some reason does not build the application in github workflow. Just after running the build command, next finish it immediately. Need to understand why.
Locally (Windows) all tests work correctly

Next.js issue: https://github.com/vercel/next.js/issues/64468


Reminder: This lib requires base64 encoded fonts in order to guarantee font availability

Should probably be documented
Should the library include these fonts? Not sure yet.
Instructions on how to test: In order to test this, you must open font book and disable Inter, Inter UI and Source Code Pro or any fonts this library uses.
The HTML test environment should be updated to test for this.

resolved in #70


Error while running make BUILD_CUDA=1

Getting an error while compiling with "BUILD_CUDA" flag.
hostnamectl output:

Static hostname: n/a
Transient hostname: --------------
Icon name: computer-vm
Chassis: vm
Machine ID: -------------------
Boot ID: ----------------
Virtualization: kvm
Operating System: Debian GNU/Linux 9 (stretch)
Kernel: Linux 4.9.0-11-amd64
Architecture: x86-64

nvcc --version  output:

nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2018 NVIDIA Corporation
Built on Sat_Aug_25_21:08:01_CDT_2018
Cuda compilation tools, release 10.0, V10.0.130

Error I'm getting:

home/XXXXXX/BitCrack/Logger  -I/home/XXXXXX/BitCrack/embedcl -I/usr/local/cuda-9.2/include -O2 -std=c++11;
done
In file included from cudaUtil.cpp:1:0:
cudaUtil.h:4:18: fatal error: cuda.h: No such file or directory
#include <cuda.h>
^
compilation terminated.
Makefile:6: recipe for target 'all' failed

Any recommendation how to address this issue?

Seems that you do not have CUDA devel libraries installed.

Edit Makefile
For exemple with my config :
**:~$ nvcc --version** nvcc: NVIDIA (R) Cuda compiler driver Copyright (c) 2005-2019 NVIDIA Corporation Built on Sun_Jul_28_19:07:16_PDT_2019 Cuda compilation tools, release 10.1, V10.1.243
i write :
CUDA_HOME=/usr/local/cuda-10.1

@ByLamacq  thank you!!!
It worked!!!
BTW is this output valid for K80 getting about 53.16 MKey per second
[2019-11-06.12:34:34] [Info] Compression: compressed
[2019-11-06.12:34:34] [Info] Starting at:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000001
[2019-11-06.12:34:34] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-11-06.12:34:34] [Info] Counting by:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000001
[2019-11-06.12:34:34] [Info] Initializing Tesla K80
[2019-11-06.12:34:34] [Info] Generating 262,144 starting points (10.0MB)
[2019-11-06.12:34:35] [Info] 10.0%
[2019-11-06.12:34:35] [Info] 20.0%
[2019-11-06.12:34:35] [Info] 30.0%
[2019-11-06.12:34:35] [Info] 40.0%
[2019-11-06.12:34:35] [Info] 50.0%
[2019-11-06.12:34:35] [Info] 60.0%
[2019-11-06.12:34:35] [Info] 70.0%
[2019-11-06.12:34:35] [Info] 80.0%
[2019-11-06.12:34:35] [Info] 90.0%
[2019-11-06.12:34:35] [Info] 100.0%
[2019-11-06.12:34:35] [Info] Done
Tesla K80        95 / 11441MB | 1 target 53.16 MKey/s (1,728,315,392 total) [00:00:30]

I managed to twike it to about 120MKeys per second
./cuBitCrack -b 64 -t 256 -p 512 1FshYsUh3mqgsG29XpZ23eLjWV8Ur3VwH
[2019-11-06.12:45:01] [Info] Compression: compressed
[2019-11-06.12:45:01] [Info] Starting at:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000001
[2019-11-06.12:45:01] [Info] Ending at:   FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364140
[2019-11-06.12:45:01] [Info] Counting by:<PHONE_NUMBER>000000000000000000000000000000000000000000000000000001
[2019-11-06.12:45:01] [Info] Initializing Tesla K80
[2019-11-06.12:45:01] [Info] Generating 8,388,608 starting points (320.0MB)
[2019-11-06.12:45:03] [Info] 10.0%
[2019-11-06.12:45:03] [Info] 20.0%
[2019-11-06.12:45:04] [Info] 30.0%
[2019-11-06.12:45:04] [Info] 40.0%
[2019-11-06.12:45:04] [Info] 50.0%
[2019-11-06.12:45:04] [Info] 60.0%
[2019-11-06.12:45:05] [Info] 70.0%
[2019-11-06.12:45:05] [Info] 80.0%
[2019-11-06.12:45:05] [Info] 90.0%
[2019-11-06.12:45:05] [Info] 100.0%
[2019-11-06.12:45:05] [Info] Done
Tesla K80        839 / 11441MB | 1 target 120.04 MKey/s (1,744,830,464 total) [00:00:12]
How can I know what is the maximum and what is the best parameters for my GPU?

I have on RTX-2060 around 130MKey/s so play around with -b -t -p parameters. For my experience it works way faster if you fill as much memory as possible. On your example you used only 839 MB out of 11 GB so there should be definitelly room to improve.

You can go on bitcointalk :
BitCrack - A tool for brute-forcing private keys -> https://bitcointalk.org/index.php?topic=4453897.0
Bitcoin puzzle transaction ~32 BTC prize to who solves it -> https://bitcointalk.org/index.php?topic=1306983.0
Bitcoin challenge transaction: ~100 BTC total bounty to solvers! -> https://bitcointalk.org/index.php?topic=5166284.0
or faster with google "Tesla K80 bitcrack"

For exemple with a 1050 ti : -b 500 -t 128 -p 128 -> 70-71 MKey/s
It's depend on your graphic card architecture.

Great thanks guys.
closing this issue :)

For exemple with a 1050 ti : -b 500 -t 128 -p 128 -> 70-71 MKey/s
It's depend on your graphic card architecture.

I want to run the program on my gtx 1050 ti but this happens https://drive.google.com/file/d/1gwEMuUztlYyRe3tz2SFVr3QfRfguuT-Y/view?usp=sharing

For exemple with a 1050 ti : -b 500 -t 128 -p 128 -> 70-71 MKey/s
It's depend on your graphic card architecture.

I want to run the program on my gtx 1050 ti but this happens https://drive.google.com/file/d/1gwEMuUztlYyRe3tz2SFVr3QfRfguuT-Y/view?usp=sharing

Try running on a command line on black screen
On Wed, Jan 6, 2021 at 11:29 PM aprenminer<EMAIL_ADDRESS>wrote:

For exemple with a 1050 ti : -b 500 -t 128 -p 128 -> 70-71 MKey/s
It's depend on your graphic card architecture.
I want to run the program on my gtx 1050 ti but this happens
https://drive.google.com/file/d/1gwEMuUztlYyRe3tz2SFVr3QfRfguuT-Y/view?usp=sharing
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/brichard19/BitCrack/issues/200#issuecomment-755756549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWRFWNI4USDI3IFVFWUNO3SYTP5PANCNFSM4JFRVESA
.

Try running on a command line on black screen
On Wed, Jan 6, 2021 at 11:29 PM aprenminer<EMAIL_ADDRESS>wrote:

For exemple with a 1050 ti : -b 500 -t 128 -p 128 -> 70-71 MKey/s
It's depend on your graphic card architecture.
I want to run the program on my gtx 1050 ti but this happens
https://drive.google.com/file/d/1gwEMuUztlYyRe3tz2SFVr3QfRfguuT-Y/view?usp=sharing
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/brichard19/BitCrack/issues/200#issuecomment-755756549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWRFWNI4USDI3IFVFWUNO3SYTP5PANCNFSM4JFRVESA
.


Give compareWith object mapping for SelectionModel same that of Select

Feature Description
It's hard to map the object's other properties in the select something in the list using SelectionModel
Please give a option to map the object's unique key to the selection like we have it for Mat Select using compareWith
Use Case
No response

Could you give a code example of what you are trying to do?

Could you give a code example of what you are trying to do?

I am trying to map the whole mat table row(not just id) within the selection model
Issue i am facing if i map it with only id based on that then again i have to filter the array and get other properties to send it to the backend
And sometimes it does not show the proper selection as i have mapping with the whole object
Solution
Provide the same functionality that we have for mat select with compareWith property we can map with the object key


Fix Poloniex minimum order calculations (issue #1811)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix

What is the current behavior? (You can also link to an open issue here)
Issue #1811 - Running live trading on Poloniex will cause the bot to be stuck in a buy or sell loop without the funds necessary to execute a trade when consecutive buy or sell signals are sent.

What is the new behavior (if this is a feature change)?
Implemented getLotSize to calculate minimum order amount based off of asset minimum and currency minimum
Moved markets object into a seperate file poloniex-markets.json to reduce bloat inside of poloniex.js

Other information:

I will merge this for now, but note that I already have another poloniex implementation working here: https://github.com/askmike/gekko/blob/gekko-trader/exchange/wrappers/poloniex.js
That will be merged as part of 0.6 in a few weeks.


Fallback font for the legend is not consistant with the rest of the fonts in the visuals

Legends don't have fall back fonts

This problem was fixed in #416.


[question] Will this work with typeorm >=0.3

Regarding the brand new version of typeorm: https://github.com/typeorm/typeorm/releases/tag/0.3.0 did you know if it would be easy to upgrade typeorm-seeding to support that last version? I'm not sure if something will break as that version is covered by the semver range
https://github.com/jorgebodega/typeorm-seeding/blob/3a9e3d30231356e7892b1e141fe1e7566b04730c/package.json#L73-L75
I'm asking this because I won't upgrade typeorm if I can't use typeorm-seeding (and few other packages that rely on typeorm)
Thanks.

I want to try the new version, but as far as I know there are so many breaking changes, so this new version will probably take some time.

do you plan to change that semver range on typeorm peer dep?

Yes, probably I will try to maintain support to 0.2 as much as I can, in other case there will be probably another major version to avoid breaking changes

I just tried this with "typeorm": "^0.3.6" and it works fine with the exception of script hanging on completion.


fix typo in readme

I should probably be taken off the reviewers list as I'm no longer co-leading the sig. cc/ @ant31

/lgtm

/approved


ElasticSearrchRequests.java - updated request

changed index to create to support datastream indexes

fixes #123

Made a PR  over at undera/jmeter-plugins with the latest version.


Unable to resolve module 'url'

I installed the library with npm i --save nubank, and imported it on my react-native project. Other than that's my code (it runs when the app starts):
NuBank.getLoginToken({
      password: 'mypass',
      login: 'mycpf', // no dashes nor dots!
    }).then(response => console.log(`I'm in!`))

      NuBank
    .getWholeFeed()
    .then(history => {console.warn(history)});

My app doesn't compile sucessfully, the terminal gives me this error:
error: bundling failed: Error: Unable to resolve module `url` from `node_modules/nubank/node_modules/node-fetch/index.js`: url could not be found within the project.

I tried running npm install, with no success.
How should I proceed? Thanks in advance.

Tried installing url and http with npm i url and npm i http. Didn't work, here's what I got:
error: bundling failed: Error: While trying to resolve module `http` from file `/home/saulo/Projetos/PersonalProjects/monyie-react/node_modules/nubank/node_modules/node-fetch/index.js`, the package `/home/saulo/Projetos/PersonalProjects/monyie-react/node_modules/http/package.json` was successfully found. However, this package itself specifies a `main` module field that could not be resolved (`/home/saulo/Projetos/PersonalProjects/monyie-react/node_modules/http/index.js`. Indeed, none of these files exist:

  * /home/saulo/Projetos/PersonalProjects/monyie-react/node_modules/http/index.js(.native|.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)
  * /home/saulo/Projetos/PersonalProjects/monyie-react/node_modules/http/index.js/index(.native|.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)

Hey there!
This is not a project we are giving support anymore :/ NuBank has changed a lot how the API is accessed since we first released the wrappers

Oh, I see... That's sad, do you know any alternatives?

python guys are working hard on it. https://github.com/andreroggeri/pynubank


YARN-7898. [FederationStateStore] Create a proxy chain for FederationStateStore API in the Router.

Description of PR
JIRA: YARN-7898. [FederationStateStore] Create a proxy chain for FederationStateStore API in the Router.
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 49s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 51s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
23m 15s

trunk passed

+1 :green_heart:
compile
7m 49s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
6m 58s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 54s

trunk passed

+1 :green_heart:
mvnsite
1m 41s

trunk passed

+1 :green_heart:
javadoc
1m 35s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
1m 23s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
3m 55s

trunk passed

+1 :green_heart:
shadedclient
26m  0s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 27s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 14s

the patch passed

+1 :green_heart:
compile
7m 21s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
7m 21s

the patch passed

+1 :green_heart:
compile
7m  7s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
7m  7s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 41s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn-project/hadoop-yarn: The patch generated 1 new + 164 unchanged - 0 fixed = 165 total (was 164)

+1 :green_heart:
mvnsite
1m 33s

the patch passed

+1 :green_heart:
javadoc
1m 23s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
1m 15s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
3m 56s

the patch passed

+1 :green_heart:
shadedclient
24m 56s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
1m  3s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
3m 18s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
asflicense
0m 49s

The patch does not generate ASF License warnings.

150m 39s

Reason
Tests

Failed junit tests
hadoop.yarn.conf.TestYarnConfigurationFields

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5682/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5682

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux d1418d219d1c 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 045f45ebc018df6ce8f2ef4a953b56f0dac10276

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5682/1/testReport/

Max. process+thread count
537 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5682/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
22m 56s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
16m 14s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
36m  1s

trunk passed

+1 :green_heart:
compile
7m 57s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
7m 11s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
1m 59s

trunk passed

+1 :green_heart:
mvnsite
1m 43s

trunk passed

+1 :green_heart:
javadoc
1m 43s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 30s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 46s

trunk passed

+1 :green_heart:
shadedclient
39m 24s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 28s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m  8s

the patch passed

+1 :green_heart:
compile
7m 11s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
7m 11s

the patch passed

+1 :green_heart:
compile
7m  8s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
7m  8s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 48s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn.txt
hadoop-yarn-project/hadoop-yarn: The patch generated 1 new + 164 unchanged - 0 fixed = 165 total (was 164)

+1 :green_heart:
mvnsite
1m 36s

the patch passed

+1 :green_heart:
javadoc
1m 30s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
1m 22s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
3m 58s

the patch passed

+1 :green_heart:
shadedclient
39m 15s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
1m  6s
/patch-unit-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-api.txt
hadoop-yarn-api in the patch passed.

+1 :green_heart:
unit
3m 30s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
asflicense
0m 53s

The patch does not generate ASF License warnings.

216m 49s

Reason
Tests

Failed junit tests
hadoop.yarn.conf.TestYarnConfigurationFields

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5682/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5682

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 40e3171a4d2d 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b002af4d9ae562e95bdd4e0751f888bd9eef2477

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5682/2/testReport/

Max. process+thread count
581 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-api hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common U: hadoop-yarn-project/hadoop-yarn

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5682/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Visual issue on "business-coronavirus-support-finder"

Problem
There is a line-height visual issue found on this page.
https://www.gov.uk/business-coronavirus-support-finder
Visuals
(Problem: Left, Ideal Solution: Right)

Investigation
The rendering element appears here:
https://github.com/alphagov/smart-answers/blob/cc59055d1876d8dd4526050515a46cc0c82cf880/app/views/smart_answers/landing.html.erb#L23
This issue appears to come from using the the deprecated govuk_template. Should relevant files be removed this resolves the issue. However the knock on impact would need review.
https://github.com/alphagov/govuk_template/blob/master/source/assets/stylesheets/_basic.scss
Anything else?
Initially it was thought this was related a11y team work, this doesn't appear to be the case. A temporary fix was raised here as a PR however this needs further investigation.

@chris-gds did this get resolved?

Fixed in https://github.com/alphagov/govuk_publishing_components/pull/2273


Cant install quick.db on Ubuntu 18 using pterodactyl panel

Hi, Ive been using quick.db on my pc for a while to store data in my bot. Ive recently bought a vps and installed pterodactyl to host my bot. It never installs so i try and adding the quickdb module in my node_module directory but then it says theres no better_sqlite3 even though its in node_modules. If you could please help me, thanks.

Hi. Can you state the error that's being returned?

If you still have this error try npm install better_sqlite3

Closed due to inactivity


new update to hello

Issue # (if applicable)
Closes #.
Reason for this change

Description of changes

Description of how you validated changes

Checklist

[ ] My code adheres to the CONTRIBUTING GUIDE and DESIGN GUIDELINES

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

:arrow_right: PR build request submitted to test-main-pipeline :arrow_left:
A maintainer must now check the pipeline and add the pr-linter/cli-integ-tested label once the pipeline succeeds.

:arrow_right: PR build request submitted to test-main-pipeline :arrow_left:
A maintainer must now check the pipeline and add the pr-linter/cli-integ-tested label once the pipeline succeeds.

:arrow_right: PR build request submitted to test-main-pipeline :arrow_left:
A maintainer must now check the pipeline and add the pr-linter/cli-integ-tested label once the pipeline succeeds.


Not compiled with python 3.9 or 3.10

Overview of issue:
The tool does not compile with python 3.9 or 3.10.
Steps to reproduce the issue:

Using python 3.9 or 3.10
pip install .

Describe the results you received:
datadog-sync ModuleNotFoundError: No module named 'pyimod02_importers'
Describe the results you expected:
Successfully installed and working properly.

Hi,
Can you describe your environment a bit more? This looks like a pyinstaller problem, but you don't mention using it. What's OS, are you using a git checkout, a tarball? Thanks.

Hi @therve , my OS: MacBook Pro (16-inch, 2021).
I installed python 3.9 and 3.10 with pyenv, and both of them got that issue, but the docker version works fine, whose python is python 3.11.4, so I install python 3.11.0 with pyenv, and it works good, so I thought that is the problem.

Can you try to upgrade pip to the latest version?

Upgrading pip works, interesting. Thanks

No problem, thank yoiu!


Tests: minor refactor for dryness of base64 and cat tests

remove extraneous uses of run or run_piped_stdin
remove extraneous uses of vec!
remove extraneous uses of as_bytes (run_piped_stdin and pipe_in both now use Into<Vec<u8>>)
remove an extraneous use of >2 arg calls for the same command instead of args

@nathanross not sure if we should allow mingw faults on windows atm


Resume filetype tooltip not opening

The file format tooltip at the applying form is not working
Current behavior
If I click on the tooltip icon (question mark), nothing happens.
Expected behavior
If I click on the tooltip icon, the tooltip opens.
Steps to replicate behavior

Go to http://pragmatica.ch/career-portal/#/jobs (It's version 2.0.1)
Select a job and click "apply"
Click on the question mark button next to "Resume File"

Fixed in v2.5.0


Accessibility issue

Hi there,
I'm using the library with sticky header enabled. It's awesome and our client likes it too. Now, however, there comes up an issue in terms of the accessibility. Once it's enabled, I found that the accessibility focus first goes to the first WrapperView item that consists of one FrameLayout, one LinearLayout. It only reads out the content from the item view, i.e. LinearLayout. The FrameLayout, the one that wraps a section header, looks ignored at this moment. If keep moving the accessibility focus, the focus jumps back to the FrameLayout and reads out the section header. Then next focus will jump to the second item LinearLayout on the StickyHeaderList.
Can the owner help me solve the issue? I appreciate.

Hi,
I came up with the fix for this issue, the fix is in pull request #473.
Hopefully it gets approved soon :)


Use SnakeYAML's safe constructor for Bool parsing

In YAML yes, no, on, and off are also Boolean values. SnakeYAML's SafeConstructor provides the facility to perform the conversion to java.lang.Boolean.

Codecov Report

Merging #44 into master will decrease coverage by 0.91%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master      #44      +/-   ##
==========================================
- Coverage     100%   99.08%   -0.92%
==========================================
  Files           4        4
  Lines         106      109       +3
  Branches        3        5       +2
==========================================
+ Hits          106      108       +2
- Misses          0        1       +1

Impacted Files
Coverage Δ

src/main/scala/io/circe/yaml/parser/package.scala
97.5% <75%> (-2.5%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 30618fa...bc57b21. Read the comment docs.

Looks reasonable to me, thanks!


Automations to synchronize source files from Node.js core repo

We may need automation setups to help us reduce the labor works on synchronizing source files in this project that shared with the Node.js core repo.

Automation would be good, but we only need to sync when there is a new version of Node-API. For example the next time will be when we introduce version 9. We remove the experimental functions, so that is the only time we should need to change the files.
It might be something like a few times a year.

We discussed in the 10 June Node API meeting that it various approaches to automation to update the exported symbols as well as the header file.
Updating the header file:

[Simpler] Have some command in the package that would update the headers and then update the symbols file manually.
[Harder] Use a github action to check if the header has changed on core and create a PR for updating the header file. Someone would need to manually update the PR to change the symbols file with new symbols added

In discussions, it sounds like solution 1 is a simpler approach that we should take.
Updating the symbols file:

parse the header file and create the new symbols JavaScript file
look at the ability for the compiler to parse the header and provide some output that can be used to create the new symbols JavaScript file. Clang compiler / tools can generate ASTs of the source

In discussions, since this is not something that occurs frequently, it may not be super beneficial to have an automated process to update the symbols.

Hi everybody,
I'll take care ofi this issue. I started to investigate if its possible to list the symbols using the preprocessor output. I wanto to try to navigate the results and discover if they are usefult o produce the list of symbols that we need.

Thank you @NickNaso for taking on this work. Nevertheless, I'm ok with the conclusion above to manually update the table as we can see that the node-api is not updated in a so frequent manner.

I am new to finding this repo which is a life saver! But in tracking all the history with past GH Issues discussing the issues of the node_api.h being removed from the node-addon-api package, I am wondering if currently this repository is the newest/correct files? I see there hasn't been an update to the releases in the last year. Thanks!

I answered my own question but want to post back here for others in the future :) As of today, Node-API is at version 8 (which this repository supports) and Node-API versioning is independent of Node.js (see screenshot).
See here: https://nodejs.org/api/n-api.html#node-api-version-matrix
Below is the current version matrix showing Node-API v8 as indeed the current version.

While hte api version hasn't changed, this library could do with an update. There have been some backwards compatible changes made to the headers that would be useful to expose https://github.com/nodejs/node/commit/09ae62b9a869ff19d634b0fd1f5a17f198cd1ae7

Done in https://github.com/nodejs/node-api-headers/pull/7.


timeout: produce usage error on invalid signal

Produce a usage error on an invalid signal argument. For example,
$ timeout --signal=invalid 1 sleep 0
timeout: 'invalid': invalid signal
Try 'timeout --help' for more information.

Style errors are due to clippy finding new issues in unrelated files. Pull request #3299 should fix it.


[core|rule] Rule to clear border for certain windows

I have vim always fullscreen on desktop 1. It'd be nice to have a rule to remove the border for it permanently.

One of my gripes with the border is the fact that sometimes after you close a window, the border remains in the place where the windows was for a about a couple of seconds - much like dead guy's outline in a crime scene.

To add my two cents, I have a Chrome plugin I use for sending text messages that I'd also like to disable the border on as the window is not a perfect square which makes the border look odd.

I posted this as a comment in the PR, but will post it here as well:
I'm not sure if I like the idea of having rules for the border plugin.
I think it may be more appropriate to offer a setting that disables the border for monocle desktops, and also for bsp-desktops that only contain a single window.
There is already an option to make the border not be drawn on floating windows, and this should probably be extended to have the border not be drawn for desktops in floating mode.


Tobin gh605 mem valid per range

This moves memory allocation valid tracking to be per-range instead of per allocation. Also improves alias tracking but lots more work to do in that department. It does fix a couple of errors in how invalid alias cases were being flagged.
This should fix #605 with current changes, but still need to fix the failing test.
Noted various holes with TODOs.

Pushed some changes to address @chrisforbes feedback and also fixed the test issue that was causing crash on one test. This branch is now clean on the farm so I'd like to merge it if I can get an "all-clear" review.

@tobine I'd consider squashing some of this down as the intermediate states I made a bunch of noise about early in the series are /really/ busted.
Other than that, :+1: from me.


Support new FlutterFire "pure Dart" Firebase packages

This is by and large blocked by https://github.com/FirebaseExtended/flutterfire/issues/3962.
We don't include a JS preamble with the app configuration, so we hit the above issue. Are there ways around this?
CC @puf, @RedBrogdon

@puf it turns out I cannot put a dummy JS configuration in; it needs to have functional values. :(

For allowing us to test, can you use the values from https://dartpad.dev/?null_safety=true&id=c21e00325f9269f0730a28df473f841c?
Firestore in that project is pretty well locked down with security rules anyway.

Hey @srawlins, @puf - with the FlutterFire release that's just shipped this should no longer be blocked: web Dart implementation across all FlutterFire plugins has been refactored to lazy initialize and default Firebase App initialization from Dart is also now supported. Let me know if any other issues come up, thanks.
https://github.com/FirebaseExtended/flutterfire/blob/master/CHANGELOG.md#2021-11-06

Thanks so much! I'll try out the new packages ASAP

Confirmed this is working great now!


Bug: You can't have underscores in model attributes

https://gist.github.com/1712145
Background: I'd like to use serenade to render some data that I get as a hash (json parsed into js-obj), I've gotten everything to work just fine except that the hash contains attributes with underscores which serenade does not like.

Ah, I just saw in the readme about serialize. Not exactly what I want, but it'll do.


Services should be able to be pegged to a specific commit

Right now we attach a service to a branch, and it will get killed and have it's data auto-updated whenever the branch changes. We can approximate pegging a service to a specific commit by creating a new branch that points at current master's head commit on each input repo, and then using that in our service's pipeline spec, but this not ideal for a few reasons:

it's a hassle to create all these branches, and remember to clean them up if/when we delete the service
it pollutes the repos' branch list. annoying for an individual user, more confusing for multiple users
it requires having write access to the input repo, which would not otherwise be required

2 & 3 could be worked around by creating your own personal/private copy of the input repo(s) using a copy pipeline, but that feels like a pretty kludgey hack

What's the use case for pegging a service to a commit?

If you've got a jupyter service you dont want it getting restarted every time new input data comes in. You might want to just lock in a commit so you can explore that data.
User have asked for both versions of this -- auto updating services versus fixing to a commit. That's exactly what branches versus commitIDs do.


*: speedup shutdown

When shutting down, tikv-server can safely exit without stopping all the workers. This can reduce the waiting time when doing gracefully shutdown.
@siddontang @zhangjinpeng1987 @disksing @hhkbp2 PTAL

LGTM

LGTM

Can we support cancelling the running job and exit the work when stopping later?
I prefer graceful shutdown.

This will require all Runners to detect if it's stopping at runtime, which is not necessary.

LGTM
PTAL @hhkbp2

LGTM then.


Unable to get convco check to check a single commit

Describe the bug
Based on my understanding of the tool/project it should be possible to run convco check to check either a range of commits or a single commit. While checking a range of commits appears functional I have yet to be able to get the tool to be able to check a single commit, regardless of what type of commit-ish is used.
To Reproduce
Steps to reproduce the behavior:

run convco check commit-ish-here
get the given reference name 'commit-ish-here' is not valid; class=Reference (4)

Expected behavior
Expected behavior is that the tool would verify the commit message of the specified commit-ish
System (please complete the following information):

OS: MacOS
Version: 11.4

Indeed, if no range is given it takes the range ..{commit-ish}.
To check a single commit you could make a range from it convco check {commit-ish}^..{commit-ish}.
This is the expected coded behaviour, see: https://github.com/convco/convco/blob/master/src/cmd/check.rs#L29
It is true however, that this is not documented.

I could add a --no-traversal or --no-walk flag to change the behaviour in case a sinlge commit is given

Any specific reason for masquerading the single provided commit-ish as ..{commit-ish}? Just from the perspective of someone coming upon the tool it seems that doing the opposite would be more intuitive. For example, if a single commit-ish is provided it checks that commit and only that commit. If --traversal or --walk is provided it instead does the range ..{commit-ish}

I added a max number option to limit the number of commits to check.
This is similar to the behaviour of git log.


UPTM-13 - Dashboard Display on vertical 4K screen

Here is the GitStart Ticket for this pull request: UPTM-13

Please mark your PR as "ready for review" when you have completed all requirements.
Please ensure that your PR is reviewed by at least 2 people after you have completed it.
Comments for review or requested changes from the upstream client will be notified to you by email and will also show on the ticket page.
After the PR is merged on the upstream, please merge this PR.
If there exist merge conflicts on your current PR and you have to close the PR instead of merging it, please go to the ticket page to manually finish the task that is related to this PR.

Loom video
https://www.loom.com/share/6fd4a2d46b18430c832ea7b67a6070f5
Happy hacking! 🎉

This code was written and reviewed by GitStart Community. Growing great engineers, one PR at a time.

Rebase and force push as it contained some commits which were not belong to this pr.

I am appreciated that the @gitstart team have made several pull requests for Uptime Kuma. Unfortunately, I agree with @CommanderStorm. It is not something I want to add.
Since it didn't follow the pr template, I hope your team have read our rules. I really don't want to waste anyone's time, so better ask me first next time.
⚠⚠⚠ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

I have read and understand the pull request rules.


fix issue #17

this should fix my described issue (17)
with sending a copy of the original list.
the for each don't run into the problem that the ontouch event removes one path from the inProgressPaths dictionary and add it to the completePaths

@andimairitsch I have the same problem... thanks for fixing it. Since your pullrequest is still open, I have to use your code but I don't know how to build the .nupkg. Could you help me with that?

could you PR to this one?
https://github.com/RajneeshSingh007/BitooBitImageEditor/tree/new_branch
it's an active branch with a nuget.


2.1.0

Updated bs-platform from 3.1.5 to 4.0.1.
Added jest.config.js file because tests were not passing without it.

Thanks! I’m AFK today but I’ll handle this tomorrow 👍

All looks great, thanks!


Add le and lt to BatchedArray

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (11ee67f) 100.00% compared to head (b1ca2e3) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #341   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           14        14
  Lines         1443      1447    +4
  Branches       158       158
=========================================
+ Hits          1443      1447    +4

Files Changed
Coverage Δ

src/redcat/array.py
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Relax Elixir version requirement

Since Elixir 1.1 is now out, specifying elixir: "~> 1.0.0" in your Mixfile
will yield a warning for anyone depending on sweet_xml running on Elixir 1.1 or
later.
Elixir versioning follows semantic versioning, so the only effect of this change
will be to eliminate some compile warnings.

:+1:


renderToStringWithClear

Or something like that. Why clear must be called manually?

Why would you want to clear in general? You only need it for the Apollo use-case as they're pre-rendering the whole tree once

Aka every SSR. serverRenderToString()?

OK. Forget about.


Custom Cache Key for images

Added parameter customCacheKey in af_setImage in UIImageView+AlamofireImage, UIButton+AlamofireImage.
Added parameter customCacheKey in ImageDownloader.download
Added test testThatImageCanBeCachedWithACustomCacheKey
Goals :soccer:
Ability to cache images based on other factors than the url, which could be necessary if the backend hosting the image has a misconfigured cache management or provides images through REST-endpoints.
Implementation Details :construction:
Added an optional cache key parameter to af_setImage-functions.
Testing Details :mag:
Added testThatImageCanBeCachedWithACustomCacheKey in UIImageViewTests .

@cnoon Any updates on this?

Not yet @graphiclife, right now we're very focused on the AF5 release and keeping AFI in sync with that. I'm not sure right now if this change will make it into AFI 4 or not.

Hi guys, just wondering, do you have a timeline to get into master? I am having the same issue, and this approach would suffice. Is there anything I or someone could do to bring this to master?

Hi @graphiclife, I have squashed these changes with a few edits and added tests in deff2079 and pushed the change into master. This will be released shortly as part of the 4.0.0 release. Thank you for all your hard work here and apologies for the poor turnaround time here.
Cheers. 🍻

@cnoon Excellent news, thanks!


Use aot-test-generators to generate test files

This makes it possible to use Mocha tests out of the box.

I'll release tonight.


New version cadence?

Noticed the packages have fallen behind the source icon versions. Is there an automated process for building and publishing new versions?

No, currently there is no automated process to update the versions. You can either create a issue for the icon package or you can fork the repo, update the icon package version and create a pull request.


Add auto-generated 3rd party notices file

Generated via https://opensource.microsoft.com/notice

Merging this ahead of talking with CELA


Make it possible for profiles to 'comment' on concepts from other profiles

Right now, profiles can use other profiles' concepts in their statement templates by specifying the identifiers in various slots, but can't provide additional/suggested metadata. For example: Verb X might only have a prefLabel in English and no altLabels in its original profile, so Profile B might want to 'comment' with altLabels in traditional and simplified Chinese to supplement the lack of multilingual labels.
Do we allow this?

The list of allowed 'commentary' metadata would be limited

Some interest in: single owner, but for non actively maintained profiles allow successor profiles (that can then add additional languages).

Single ownership is preferred, with transfer of ownership for profiles not sufficiently updated.
Side issue: profile server will likely want to require open licensing of profiles.

This issue should be replaced by one describing the needed changes to the spec (largely descriptive) around how new languages for concepts should be handled.

Jason Haag would like to reopen discussion on this, citing AcrossX profile activity in particular and suggesting that profile owners may be slow to incorporate other languages than the ones they include to start with.

"ADL is building a profile server and will allow for community curation and management of profiles."  I think this server will solve these language concerns.
Echoing Jason's commented during the call, as long as there is an interface for someone to suggest an addition to a given profile and a way for an admin to review said suggestion before adding it to the profile, we would only run into outdated profiles if they are not hosted on the community server.  This encourages people to use the community server which has many benefits for the community as a whole (reliable source of up-to-date profiles, the ability to easily update profiles, greater sense of community, continuous growth of "official" profiles).
There is obviously the discussion of what the review process looks like for an admin updating profiles or what qualifies you to be an admin but that can be tabled for now.

I also agree with Jason's concern. If the location of the profile was centralized per @FeLungs comment, it may not be as much of an issue. I think this may be a concern even beyond the language issue for modifications to profiles. If the "owner" of a profile is not responsive enough, this may lead to duplication of efforts and confusion.

Maintaining earlier consensus; new issue opened