Improve arrow animation

Hi,
your card is perfect from functionality point of view, but the arrow animation (jumping arrows) is not really nice (my opinion).
I could successfully modify your card to suggest an improvement, you can see it in the video (in attached zip).
I can't offer you a pull request, because I have no idea how to build your project. So I modified just the resulting .js-file. But I attached the js-file I modified, so you can see in a diff the few changes I made. Probably you like it and can inlude it in your card.
power-distribution-card.zip
Regards, Waldemar

I will add it as a new animation type i think and maybe change the disable_animation to animation with the 3 options: none, fluent, jumpy(maybe i can come up with a better word...)
The current animation (the jumpy one) is similar to E3DC so i want to still have it included.
Thanks alot for the contribution 👍
Additionally i wanted to say i really like your idea of replacing the ratio with the battery percentage. 💯
Maybe this is a better way of displaying the battery SOC then what i had previously planned.
And regarding how the project is structured:
Typescript is just like Javascript with the difference being you have fixed Types(String, Int etc...)
So in the Source folder here you will find all the files. THey are split up into different files to make it easier to work with.
To compile the JS file you'll need to have NodeJS installed and then just run npm run-script build in the project directory.
You will see if all checks passed and if so, find the compiled JS in the dist folder.

@mumpf Feel free to write down some improvement ideas if you want 👍

I have a few ideas...

user can choose the color of the arrows, ideally per entity. I.e.

solar:
...
color_arrow_left: red
color_arrow_right:; green
home:
...
color_arrow_left: blue
color_arrow_right: blue

as an alternative, you could offer a color_template property per entity...
If the output unit is Watt (W), I would format the output value to integer.
for 'unit_of_display' I would suggest a third value "mixed", which displays values <1000W as integer Watt values (i.e. 672 W), but values >= 1000W as float in kW (i.e. 1.23 kW)

Regarding the battery soc display: My "misuse" of the ratio bar is not really my favorite.... somehow funny that you like it. An alternative idea:

allow additional information for each entity, displayed in a small font directly next to the icon of the entity.
this can be used for any information, like battery soc, or windspeed or pool temperature or car soc.

Regards,
Waldemar

I finished the animation change here: https://github.com/JonahKr/power-distribution-card/commit/1c97b1638cd727a61f32356d324c52880f86e827
Its now Vector based instead of Border based.
Coloring is not yet included but i will work on all the coloring stuff for the objects in the near future to get everything standardized.


Is is possible to add a validation method after document.ready has fired?

I have a script that calls $.validator.addMethod after document.ready has been invoked. This plugin doesn't appear to pick up the method added in this way. Is there any way to get this to work? Is there some sort of "rebind" method I can call to force this plugin to wire itself up again after I've added my validation method?

@IanKemp
Can you upload a simple and reproducible code？that maybe help.
Did you turn on asynchronous loading, so your code was loaded earlier than the jquery-validation, and the registration failed。


What does sameAs point to in LabProtocol?

Uri propery of ISA protocol is already covered by url field from schema.org thing

I'm not sure about this and can't remember why we added both. Could be that one is meant to point to a file within an ARC that describes the protocol whereas the other points to a true external resource like a website? Do you remember, @stuzart? Is it even a realistic scenario that both exist?

So are you saying that sameAs is necessary and something else than url? Because your description "an actual file documenting the protocol" basically matches what the description of url in the profile says. I'm a bit confused.
@stuzart

The problem with url is that in an RO-Crate if you are including an actual file, it needs to referenced as a File (an alias for MediaObject) which wouldn't be compatible with url, but would be with hasPart. url could be used if pointing to something elsewhere, e.g. protocols.io but not if you just want to include a doc or pdf file.
It may even be clearer if we just remove url and use hasPart for both cases. The RO-Crate docs describe using File for both files or web based entities https://www.researchobject.org/ro-crate/1.1/data-entities.html

Actually I've looked into it a bit more and yes, your're right, we just need url . If it is a file, we just need to give the filename as the @id , and use a @type of both File and Labprotocol e.g
{
      "@id": "my-lovely-protocol.pdf",
      "@type": [
        "File",
        "LabProtocol"
      ],
      ....
}
'''
and then reference `my-lovely-protocol.pdf` from the root entity with `hasPart`.

So from the profile we can drop `@sameAs` and don't anything to replace it.

Sorry, I keep forgetting this ro-crate convension of using the `@id` as the file reference rather than a more explicit property.

So we would have 2 distinct to reference a digital protocol resource:

If it is a file in the RO-Crate/ARC, we use @id
If it is a external web resource, we use uri

Or did I get this wrong?

it's a bit confusing and I'm trying to get to clarification. The spec itself is known to be confusing, and is trying to be improved to ro-crate 1.2. But the gist of it is that:

if its a file then in the ro-crate the @id should be the path to the file, relative to the root
if its an extenal web resource, then the @id should be the URL
if its mixed, both a file and available online then @id should be the file, and url a download link (in 1.2 changing to contentUrl for the download link)

in all cases there must be a hasPart referencing the File as root entities.
In our case, where it is an external web resource, I don't see any harm in also include url to point to it, which I think would make it fit with the bioschema profile and I'd imagine make it easier for parsers.

My suggestion is that we include url but make it none mandatory, but recommended for an external web source. At the same time, the bioschema for LabProtocol  should replace sameAs with url, (which is where it originally came from).
So in the ro-crate, for a file it would appear as:
{
      "@id": "my-lovely-protocol.pdf",
      "@type": [
        "File",
        "LabProtocol"
      ],
      ....
}

external web resource:
{
      "@id": "https://somewhere.com/my-lovely-protocol.pdf",
      "@type": [
        "File",
        "LabProtocol"
      ],
      url: "https://somewhere.com/my-lovely-protocol.pdf"
      ....
}

and if mixed, then
{
      "@id": "my-lovely-protocol.pdf",
      "@type": [
        "File",
        "LabProtocol"
      ],
      url: "https://somewhere.com/my-lovely-protocol.pdf"
      ....
}

The root ro-crate DataSet would include the following, but this isn't necessarily part of the Profile, but just part of the ro-crate spec:
"hasPart": [
        {
          "@id": "my-lovely-protocol.pdf"
        }
      ]


403 forbidden error when trying to call using sendAsync Method Instead of PostAsync

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
PR for the code
https://github.com/jayaamamidala/LogAnalytics/blob/master/ConsoleApp1/ConsoleApp1/Program.cs
unable to use sendAsync method instead of PostAsync and facing 403 error

@jayaamamidala please include the link to the document you are following.

@MarileeTurscak-MSFT  https://docs.microsoft.com/en-us/azure/azure-monitor/platform/data-collector-api#c-sample , we are using SendAsync Instead of PostAsymc Method

Hi @jayaamamidala , apologies for the delay. I am unable to reproduce your issue but did an online search and found a few forum postings that may be helpful to your scenario.
https://stackoverflow.com/questions/3272067/webclient-403-forbidden
https://stackoverflow.com/questions/2794260/webclient-the-remote-server-returned-an-error-403-forbidden
If the postings didnt resolve your issue, I recommend re-posting your question directly in our Forum channels so one of our SMEs can help investigate further. Please note this channel is reserved for feedback on Azure documentation only but we are happy to connect you with the appropriate channels to get you the best possible answer.


Update documentation to reflect self-host instructions and optional usage of MapTiler Cloud

See talk-us discussion:
https://lists.openstreetmap.org/pipermail/talk-us/2022-January/021552.html
The documentation should make the "openmaptiles server" a generic concept and provide instructions on how to run the style on extracts.

Note that tileserver-gl is fairly heavy since it has the ability to render tiles server-side. Something like https://github.com/consbio/mbtileserver meets my needs better for just serving up anbtiles.

There's also the light version of tileserver-gl which has all the server-side rendering dependencies removed.  Makes it easier to get running.
https://www.npmjs.com/package/tileserver-gl-light
https://tileserver.readthedocs.io/en/latest/installation.html#tileserver-gl-light-on-npm


Cannot for community templates on the Langflow space in huggingface

visit: https://huggingface.co/spaces/Logspace/Langflow
go to community examples
click fork on one of them
get an error

Which specific flow is causing the error? I've tested it on my machine, and everything appears to be functioning normally from my end.

The same happens to me. It happens with all the flows on the "Community Examples". Have in mind this happens when using it via HuggingFace Spaces.

Ok, have just tried it with another computer and it worked. In the machine I got the error i am under a VPN, so maybe that explains the problem

Hugging Face Spaces seems to be experiencing some difficulties with the iframe. For a smoother experience, you can access the content directly using the following link:
https://logspace-langflow.hf.space/

It works! Thanks


Update and simplify VMware docs

Fixes rancher/elemental#1557

Note most modified files are simply removed images that are no longer displayed as part of the documentation.

Nice rework, was needed indeed! Few typos, just reported on the non-versioned doc. The cmdline for downloading the ISO is wrong, we need to fix it before merging.

Thanks! Good catches, I am adapting the other versions :+1:


V0.12.0 release is mandatory but provides no estimation or date for activiation

https://github.com/OmniLayer/omnicore/releases/tag/v0.12.0 says,

This release is mandatory and changes the rules of the Omni Layer protocol. An upgrade is required.

However, it's also marked as a Pre-release, there are no binaries attached to the github release, https://www.omnilayer.org/download.html only links 0.11.0 binaries, and https://twitter.com/omni_layer says nothing about it that I can see (which I checked after seeing https://github.com/OmniLayer/omnicore/issues/1236).
Is this a real update, and if so when do we need to be updated by and will there be a normal release for it?

Hey @briancolecoinmetrics,
the 0.12 release includes new features like send-to-many. Once this feature is activated, old versions are no longer compatible.
Right now, the new release is under review and the feature hasn't been activated. Once this is the case, blog posts and more official news will follow.


fix: delta scan partition ordering bug

Description
Sometimes the order of partition columns in our delta schema does not match the order of partition columns in the deltatable metadata.
This would cause DeltaScan to provide incorrect values for partition columns.
This is fixed by having DeltaScan use the metadata as the source of truth.
Related Issue(s)

closes #1787

take

@mightyshazam @MrPowers Why is there a take on this PR? it's mostly done the only things that needs to be done is removing some unwraps.

@Blajda - sorry for the miscommunication.  @mightyshazam will help out with a review.  I assigned it to him cause I can't assign him as a reviewer, but now realize that was misleading.  So yea, let @mightyshazam know when you're done so he can take a look, thanks!!

@MrPowers
ah thanks for the clarification!

@mightyshazam this is ready for review. Thanks for taking the initiative


Bazel build of tink for Python fails

I'm attempting to use FPM to repackage the tink code into an RPM and the build is failing due to a C++ compile error:
ERROR: /root/.cache/bazel/_bazel_root/dcfda3730e42b07a275abf4fe2eeeda4/external/aws_c_common/BUILD.bazel:5:11: C++ compilation of rule '@aws_c_common//:aws_c_common' failed (Exit 1) gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 23 argument(s) skipped) {:level=>:info}  {:level=>:info} Use --sandbox_debug to see verbose messages from the sandbox {:level=>:info} external/aws_c_common/source/allocator.c: In function 'aws_mem_acquire_many': {:level=>:info} external/aws_c_common/source/allocator.c:134:5: error: 'for' loop initial declarations are only allowed in C99 mode {:level=>:info}      for (size_t i = 0; i < count; ++i) { {:level=>:info}      ^ {:level=>:info} external/aws_c_common/source/allocator.c:134:5: note: use option -std=c99 or -std=gnu99 to compile your code {:level=>:info} external/aws_c_common/source/allocator.c:156:9: error: 'for' loop initial declarations are only allowed in C99 mode {:level=>:info}          for (size_t i = 0; i < count; ++i) { {:level=>:info}          ^ {:level=>:info} Target //tink/cc/pybind:tink_bindings failed to build {:level=>:info}
This is using the 1.4.0 release code.

Hi,
Is there any update on the above?
Regards,
Jordan

Hi kste,
Thanks for the reply!
That file isn't present on my system - all I've done is download the available sources via pip. I'll try with the latest sources from here instead as I suppose it's possible the sources on pypi aren't complete.
For reference my system is CentOS 7.8.2003, using GCC 4.8.5 and Python 3.8.5

OK so adding copts=["-std=c99"] to the aws_c_common.BUILD.bazel file seems to get it a bit further sometimes, other times it thinks it's still not there. I don't really know how bazel works, but it seems to be fetching sources remotely so perhaps it's pulling that build file down from somewhere else instead of using my copy.
I also get inconsistent results using python3 setup.py install so I've tried to just use bazel for the time being.
Regardless, when it does get further, it then produces this error:
`[root@JSLinuxDev python]# bazel build ...
DEBUG: Rule 'tink_base' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "fe1c5a5bea14f92c64409f36431ae98d5002e23af38ed7c1b2d3fbebdadcfd55"
DEBUG: Repository tink_base instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
/root/.cache/bazel/_bazel_root/78833ac665c89dbc358f9103c001d7b9/external/bazel_tools/tools/build_defs/repo/http.bzl:336:16: in
DEBUG: Rule 'tink_cc' indicated that a canonical reproducible form can be obtained by modifying arguments sha256 = "fe1c5a5bea14f92c64409f36431ae98d5002e23af38ed7c1b2d3fbebdadcfd55"
DEBUG: Repository tink_cc instantiated at:
no stack (--record_rule_instantiation_callstack not enabled)
Repository rule http_archive defined at:
/root/.cache/bazel/bazel_root/78833ac665c89dbc358f9103c001d7b9/external/bazel_tools/tools/build_defs/repo/http.bzl:336:16: in
INFO: Analyzed 202 targets (106 packages loaded, 5125 targets configured).
INFO: Found 202 targets...
INFO: From ProtoCompile external/com_google_protobuf/python/google/protobuf/struct_pb2.py:
external/com_google_protobuf/python: warning: directory does not exist.
INFO: From ProtoCompile external/com_google_protobuf/python/google/protobuf/type_pb2.py:
external/com_google_protobuf/python: warning: directory does not exist.
INFO: From ProtoCompile external/com_google_protobuf/python/google/protobuf/wrappers_pb2.py:
external/com_google_protobuf/python: warning: directory does not exist.
INFO: From ProtoCompile external/com_google_protobuf/python/google/protobuf/timestamp_pb2.py:
external/com_google_protobuf/python: warning: directory does not exist.
INFO: From ProtoCompile external/com_google_protobuf/python/google/protobuf/compiler/plugin_pb2.py:
external/com_google_protobuf/python: warning: directory does not exist.
INFO: From Action external/googleapis/google/cloud/kms/v1/resources.grpc.pb.h:
bazel-out/k8-fastbuild/bin/external/googleapis/external/googleapis: warning: directory does not exist.
google/cloud/kms/v1/resources.proto:23:1: warning: Import google/api/annotations.proto is unused.
INFO: From Generating C++ proto_library @googleapis//google/cloud/kms/v1:kms_proto:
google/cloud/kms/v1/resources.proto:23:1: warning: Import google/api/annotations.proto is unused.
INFO: From Compiling external/com_google_absl/absl/status/status.cc:
In file included from external/com_google_absl/absl/strings/cord.h:84:0,
from external/com_google_absl/absl/status/status.h:21,
from external/com_google_absl/absl/status/status.cc:14:
external/com_google_absl/absl/types/optional.h:119:7: warning: unused parameter 'src' [-Wunused-parameter]
class optional : private optional_internal::optional_data,
^
external/com_google_absl/absl/status/status.cc: In lambda function:
external/com_google_absl/absl/status/status.cc:303:25: note: synthesized method 'absl::optional& absl::optional::operator=(absl::optional&&) [with T = std::basic_string]' first required here
if (printer) result = printer(type_url, payload);
^
INFO: From Compiling external/tink_cc/config/tink_fips.cc:
external/tink_cc/config/tink_fips.cc: In function 'crypto::tink::util::Status crypto::tink::ChecksFipsCompatibility(crypto::tink::FipsCompatibility)':
external/tink_cc/config/tink_fips.cc:50:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
INFO: From Compiling external/tink_cc/subtle/aes_gcm_hkdf_stream_segment_decrypter.cc:
external/tink_cc/subtle/aes_gcm_hkdf_stream_segment_decrypter.cc: In function 'crypto::tink::util::Status crypto::tink::subtle::{anonymous}::Validate(const crypto::tink::subtle::AesGcmHkdfStreamSegmentDecrypter::Params&)':
external/tink_cc/subtle/aes_gcm_hkdf_stream_segment_decrypter.cc:67:60: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (params.ikm.size() < 16 || params.ikm.size() < params.derived_key_size) {
^
external/tink_cc/subtle/aes_gcm_hkdf_stream_segment_decrypter.cc: In member function 'virtual crypto::tink::util::Status crypto::tink::subtle::AesGcmHkdfStreamSegmentDecrypter::Init(const std::vector&)':
external/tink_cc/subtle/aes_gcm_hkdf_stream_segment_decrypter.cc:113:24: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (header.size() != header_size) {
^
external/tink_cc/subtle/aes_gcm_hkdf_stream_segment_decrypter.cc: In member function 'virtual crypto::tink::util::Status crypto::tink::subtle::AesGcmHkdfStreamSegmentDecrypter::DecryptSegment(const std::vector&, int64_t, bool, std::vector*)':
external/tink_cc/subtle/aes_gcm_hkdf_stream_segment_decrypter.cc:172:55: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (ciphertext.size() > get_ciphertext_segment_size()) {
^
ERROR: /root/.cache/bazel/_bazel_root/78833ac665c89dbc358f9103c001d7b9/external/tink_cc/subtle/BUILD.bazel:349:1: C++ compilation of rule '@tink_cc//subtle:aes_gcm_hkdf_stream_segment_encrypter' failed (Exit 1) gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer '-std=c++0x' -MD -MF ... (remaining 40 argument(s) skipped)
Use --sandbox_debug to see verbose messages from the sandbox
external/tink_cc/subtle/aes_gcm_hkdf_stream_segment_encrypter.cc: In member function 'virtual crypto::tink::util::Status crypto::tink::subtle::AesGcmHkdfStreamSegmentEncrypter::EncryptSegment(const std::vector&, bool, std::vector*)':
external/tink_cc/subtle/aes_gcm_hkdf_stream_segment_encrypter.cc:137:53: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (plaintext.size() > get_plaintext_segment_size()) {
^
In file included from bazel-out/k8-fastbuild/bin/external/tink_cc/subtle/_virtual_includes/aes_gcm_hkdf_stream_segment_encrypter/tink/subtle/aes_gcm_hkdf_stream_segment_encrypter.h:27:0,
from external/tink_cc/subtle/aes_gcm_hkdf_stream_segment_encrypter.cc:17:
bazel-out/k8-fastbuild/bin/external/tink_cc/util/_virtual_includes/statusor/tink/util/statusor.h: In instantiation of 'crypto::tink::util::StatusOr::StatusOr(const T&) [with T = std::unique_ptr<evp_aead_ctx_st, bssl::internal::Deleter<evp_aead_ctx_st> >]':
external/tink_cc/subtle/aes_gcm_hkdf_stream_segment_encrypter.cc:92:10:   required from here
bazel-out/k8-fastbuild/bin/external/tink_cc/util/_virtual_includes/statusor/tink/util/statusor.h:137:60: error: use of deleted function 'std::unique_ptr<_Tp, _Dp>::unique_ptr(const std::unique_ptr<_Tp, _Dp>&) [with _Tp = evp_aead_ctx_st; Dp = bssl::internal::Deleter<evp_aead_ctx_st>]'
inline StatusOr::StatusOr(const T& value) : value(value) {
^
In file included from /usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../include/c++/4.8.5/memory:81:0,
from bazel-out/k8-fastbuild/bin/external/tink_cc/subtle/_virtual_includes/aes_gcm_hkdf_stream_segment_encrypter/tink/subtle/aes_gcm_hkdf_stream_segment_encrypter.h:20,
from external/tink_cc/subtle/aes_gcm_hkdf_stream_segment_encrypter.cc:17:
/usr/lib/gcc/x86_64-redhat-linux/4.8.5/../../../../include/c++/4.8.5/bits/unique_ptr.h:273:7: error: declared here
unique_ptr(const unique_ptr&) = delete;
^
INFO: Elapsed time: 54.907s, Critical Path: 14.91s
INFO: 202 processes: 202 processwrapper-sandbox.
FAILED: Build did NOT complete successfully`

I see! That's interesting, because I would except on that system that pip should use the available binary releases. Could you try installing the binary wheel directly: https://pypi.org/project/tink/#files (tink-1.4.0-cp38-cp38-manylinux2014_x86_64.whl)?

This issue for numpy https://github.com/numpy/numpy/issues/14182 seems to have a very similar problem with the same gcc version and CentOS. Maybe this works for you as well :-)

I see! That's interesting, because I would except on that system that pip should use the available binary releases. Could you try installing the binary wheel directly: https://pypi.org/project/tink/#files (tink-1.4.0-cp38-cp38-manylinux2014_x86_64.whl)?

Well I would've assumed that as well! I can install it directly from the wheel, but because I'm trying to package it up with fpm I need to go down this route unfortunately. I'll continue to investigate whether I can just extract the wheel and use that directly with fpm.
I've tried the CFLAGS="-std=c99" approach and that causes more problems due to some constexpr statements in other C++ code.
I've followed all the steps in the guide to try and build tink but there must either be something missing or something odd with my machine (entirely possible) - is there an ansible script or something to create a build machine that is known to work? I really just want to rule out me doing anything stupid...!

@kste OK so I've managed to get FPM to work with the wheel files, that's the first hurdle done. The issue I now have is the systems I have to deploy onto only have Python 3.6 on there, so even though I've managed to get the RPM built and installed...whenever I try to use tink it falls over because the bindings are for Python 3.8. Could you possibly build a wheel for Python 3.6 and upload it to pypi or provide some more detail on how I'd go about building this myself?

Unfortunately Tink is not fully compatible with Python 3.6, as it relies on some type hint features which are only available in 3.7+.

Closing, as it looks like the original issue was resolved.
@JordanStopford it's very unlikely that we can support 3.6, I'm sorry.


Can't compile because of "missing external type definition" ?

Hello,
I am migrating an Angular v7.1.0 project to Bazel using github.com/alexeagle/angular-bazel-example as the main inspiration.
I still didn't successfully compile my application. The problem seem to be caused by a TypeScript  or/and Angular package BUILD but I have some problems with debugging it 😨
The application:
github.com/sfeir-open-source/xlayers/tree/build/bazel
@manekinekko
Workspace

Click to expand
# The WORKSPACE file tells Bazel that this directory is a "workspace", which is like a project root.
# The content of this file specifies all the external dependencies Bazel needs to perform a build.

####################################
# ESModule imports (and TypeScript imports) can be absolute starting with the workspace name.
# The name of the workspace should match the npm package where we publish, so that these
# imports also make sense when referencing the published package.
workspace(name = "xlayers")

# The Bazel buildtools repo contains tools like the BUILD file formatter, buildifier
# This commit matches the version of buildifier in angular/ngcontainer
# If you change this, also check if it matches the version in the angular/ngcontainer
# version in /.circleci/config.yml
BAZEL_BUILDTOOLS_VERSION = "49a6c199e3fbf5d94534b2771868677d3f9c6de9"

http_archive(
    name = "com_github_bazelbuild_buildtools",
    url = "https://github.com/bazelbuild/buildtools/archive/%s.zip" % BAZEL_BUILDTOOLS_VERSION,
    strip_prefix = "buildtools-%s" % BAZEL_BUILDTOOLS_VERSION,
    sha256 = "edf39af5fc257521e4af4c40829fffe8fba6d0ebff9f4dd69a6f8f1223ae047b",
)

# The @angular repo contains rule for building Angular applications
http_archive(
    name = "angular",
    url = "https://github.com/angular/angular/archive/7.1.0.zip",
    strip_prefix = "angular-7.1.0",
)

# The @rxjs repo contains targets for building rxjs with bazel
http_archive(
    name = "rxjs",
    url = "https://registry.yarnpkg.com/rxjs/-/rxjs-6.3.3.tgz",
    strip_prefix = "package/src",
    sha256 = "72b0b4e517f43358f554c125e40e39f67688cd2738a8998b4a266981ed32f403",
)

# Angular material
# Using commit that is compatible with angular 7.0.4
# TODO(gmagolan): Update to https://github.com/angular/material2 v7.0.5 when released
http_archive(
    name = "angular_material",
    url = "https://github.com/DevVersion/material2/archive/c94e095841b063380b9d2c5611da1ff99445e516.zip",
    strip_prefix = "material2-c94e095841b063380b9d2c5611da1ff99445e516",
)

####################################
# Load and install our dependencies downloaded above.

load("@angular//packages/bazel:package.bzl", "rules_angular_dependencies")

rules_angular_dependencies()

load("@build_bazel_rules_nodejs//:defs.bzl", "check_bazel_version", "node_repositories", "yarn_install")

# The minimum bazel version to use with this example repo
# Bazel 0.19 supports the .bazelignore file
check_bazel_version("0.19.0")

node_repositories(
    node_version = "10.9.0",
    yarn_version = "1.12.1",
)

yarn_install(
    name = "npm",
    package_json = "//:package.json",
    yarn_lock = "//:yarn.lock",
)

load("@io_bazel_rules_go//go:def.bzl", "go_rules_dependencies", "go_register_toolchains")

go_rules_dependencies()
go_register_toolchains()

# Browser test
load("@io_bazel_rules_webtesting//web:repositories.bzl", "browser_repositories", "web_test_repositories")

web_test_repositories()
browser_repositories(
    chromium = True,
    firefox = True,
)

# Load TypeScript
load("@build_bazel_rules_typescript//:defs.bzl", "ts_setup_workspace")

ts_setup_workspace()

# Setup Angular
load("@angular//:index.bzl", "ng_setup_workspace")

ng_setup_workspace()

load("@angular_material//:index.bzl", "angular_material_setup_workspace")

angular_material_setup_workspace()

Build log

Click to expand
➜  lib git:(build/bazel) ✗ /opt/bazel/bazel build
INFO: Build options have changed, discarding analysis cache.
INFO: Analysed 0 targets (0 packages loaded, 0 targets configured).
INFO: Found 0 targets...
INFO: Elapsed time: 1.237s, Critical Path: 0.01s, Remote (0.00% of the time): [queue: 0.00%, setup: 0.00%, process: 0.00%]
INFO: 0 processes.
INFO: Build completed successfully, 1 total action

Run log

Click to expand
➜  lib git:(build/bazel) ✗ bazel run //src:prodserver --verbose_failures
INFO: Build options have changed, discarding analysis cache.
yarn install v1.12.1
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency "webpack@^1 || ^2 || ^3 || ^4".
warning "@angular/bazel ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS><2.10".
warning "jest-preset-angular ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^7.0.0-0".
warning "jest-preset-angular ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^24.0.0".
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[5/5] Building fresh packages...
success Saved lockfile.
Done in 75.57s.
INFO: Analysed target //src:prodserver (214 packages loaded, 15700 targets configured).
INFO: Found 1 target...
WARNING: AngularTemplateCompile worker (id 6) can no longer be used, because its files have changed on disk:
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped_bin.sh: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/xlayers/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/xlayers/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped_bin.sh: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped_bin.sh: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
WARNING: AngularTemplateCompile worker (id 7) can no longer be used, because its files have changed on disk:
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped_bin.sh: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/xlayers/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/xlayers/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped_bin.sh: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped_bin.sh: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
WARNING: AngularTemplateCompile worker (id 4) can no longer be used, because its files have changed on disk:
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc
43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped_bin.sh: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/xlayers/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/xlayers/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped_bin.sh: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped_bin.sh: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
WARNING: AngularTemplateCompile worker (id 5) can no longer be used, because its files have changed on disk:
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc
43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped_bin.sh: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/xlayers/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped.runfiles/xlayers/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped_bin.sh: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
bazel-out/host/bin/external/angular/packages/bazel/src/ngc-wrapped/ngc-wrapped_bin.sh: 0f12602f950dacad3afd9dbdbf2f7c6092185dd6acef90eaa1ff3fbc43179726 -> a8ff5124bd2d01722301edcbe8536cba53d1b3351389115bfb2703a1910a8a13
WARNING: AngularTemplateCompile worker (id 9) can no longer be used, because its files have changed on disk:
bazel-out/host/bin/external/angular/@angular/bazel/ngc-wrapped: bfddf09996d7352c4aed0e586dd3a3ead89a6ef2b411f86fb93eef68db1cfe39 -> 5060
3665ad8b71cfd7923a51323f69c0263b376e27a04243d5b13868b7240a25
bazel-out/host/bin/external/angular/@angular/bazel/ngc-wrapped.runfiles/angular/@angular/bazel/ngc-wrapped: bfddf09996d7352c4aed0e586dd3
a3ead89a6ef2b411f86fb93eef68db1cfe39 -> 50603665ad8b71cfd7923a51323f69c0263b376e27a04243d5b13868b7240a25
bazel-out/host/bin/external/angular/<EMAIL_ADDRESS>bfddf09996d7352c4aed0
e586dd3a3ead89a6ef2b411f86fb93eef68db1cfe39 -> 50603665ad8b71cfd7923a51323f69c0263b376e27a04243d5b13868b7240a25
bazel-out/host/bin/external/angular/@angular/bazel/ngc-wrapped.runfiles/xlayers/external/angular/@angular/bazel/ngc-wrapped: bfddf09996d
7352c4aed0e586dd3a3ead89a6ef2b411f86fb93eef68db1cfe39 -> 50603665ad8b71cfd7923a51323f69c0263b376e27a04243d5b13868b7240a25
bazel-out/host/bin/external/angular/<EMAIL_ADDRESS>bfddf09996d7352c4aed0e586dd3a3ead89a6ef2b411f86fb93eef68db1cfe39 -> 50603665ad8b71cfd7923a51323f69c0263b376e27a04243d5b13868b7240a25
<EMAIL_ADDRESS>bfddf09996d7352c4aed0e586dd3a3ead89a6ef2b411f86fb93eef68db1cfe39-> 50603665ad8b71cfd7923a51323f69c0263b376e27a04243d5b13868b7240a25
WARNING: AngularTemplateCompile worker (id 8) can no longer be used, because its files have changed on disk:
bazel-out/host/bin/external/angular/@angular/bazel/ngc-wrapped: bfddf09996d7352c4aed0e586dd3a3ead89a6ef2b411f86fb93eef68db1cfe39 -> 5060
3665ad8b71cfd7923a51323f69c0263b376e27a04243d5b13868b7240a25
bazel-out/host/bin/external/angular/@angular/bazel/ngc-wrapped.runfiles/angular/@angular/bazel/ngc-wrapped: bfddf09996d7352c4aed0e586dd3
a3ead89a6ef2b411f86fb93eef68db1cfe39 -> 50603665ad8b71cfd7923a51323f69c0263b376e27a04243d5b13868b7240a25
bazel-out/host/bin/external/angular/<EMAIL_ADDRESS>bfddf09996d7352c4aed0e586dd3a3ead89a6ef2b411f86fb93eef68db1cfe39 -> 50603665ad8b71cfd7923a51323f69c0263b376e27a04243d5b13868b7240a25
bazel-out/host/bin/external/angular/@angular/bazel/ngc-wrapped.runfiles/xlayers/external/angular/@angular/bazel/ngc-wrapped: bfddf09996d7352c4aed0e586dd3a3ead89a6ef2b411f86fb93eef68db1cfe39 -> 50603665ad8b71cfd7923a51323f69c0263b376e27a04243d5b13868b7240a25
bazel-out/host/bin/external/angular/<EMAIL_ADDRESS>bfddf09996d7352c4aed0e586dd3a3ead89a6ef2b411f86fb93eef68db1cfe39 -> 50603665ad8b71cfd7923a51323f69c0263b376e27a04243d5b13868b7240a25
<EMAIL_ADDRESS>bfddf09996d7352c4aed0e586dd3a3ead89a6ef2b411f86fb93eef68db1cfe39-> 50603665ad8b71cfd7923a51323f69c0263b376e27a04243d5b13868b7240a25
ERROR: /Users/williamphetsinorath/Codes/sfeir-open-source/xlayers/src/app/BUILD.bazel:5:1: Compiling Angular templates (ngc) //src/app:a
pp failed (Exit 1): ngc-wrapped failed: error executing command
(cd /private/var/tmp/_bazel_williamphetsinorath/ddc39d7215bcfeb4d52e41ea2c016537/execroot/xlayers && \
exec env - \
bazel-out/host/bin/external/angular/@angular/bazel/ngc-wrapped '--node_options=--expose-gc' @@bazel-out/darwin-fastbuild/bin/src/app/app_tsconfig.json)
error TS2688: Cannot find type definition file for 'estree'.
error TS2688: Cannot find type definition file for 'jasmine'.
error TS2688: Cannot find type definition file for 'jasminewd2'.
error TS2688: Cannot find type definition file for 'jest'.
error TS2688: Cannot find type definition file for 'node'.
error TS2688: Cannot find type definition file for 'q'.
error TS2688: Cannot find type definition file for 'selenium-webdriver'.

Target //src:prodserver failed to build
INFO: Elapsed time: 155.599s, Critical Path: 47.05s, Remote (0.00% of the time): [queue: 0.00%, setup: 0.00%, process: 0.00%]
INFO: 18 processes: 18 worker.
 I filed https://github.com/bazelbuild/bazel/issues/6811 because I can understand why you'd expect that to do something.
For your error, I'd need to see the BUILD file, but I suspect you are using fine-grained dependencies and don't have @npm//@types in the deps of the failing target (that would prevent the TypeScript compiler from being able to find the files)
Another possibility is that the files are in the deps, but the tsconfig.json has types: [] so the typescript compiler would not bother looking for typings files.

Thanks for the updates @alexeagle
@Shikanime can you try Alexe's suggestions and keep us in sync?

@alexeagle Thank for your quick reply.
Assuming that the file hierarchy of the project is a typical "ng new".
./tsconfig.json
There's my tsconfig file, I actually don't have any type fields.

Click to expand
{
  "compileOnSave": false,
  "compilerOptions": {
    "baseUrl": "./",
    "outDir": "./dist/out-tsc",
    "sourceMap": true,
    "declaration": false,
    "moduleResolution": "node",
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "target": "es5",
    "typeRoots": [
      "node_modules/@types"
    ],
    "lib": [
      "es2017",
      "dom"
    ],
    "paths": {
      "@manekinekko/ngx-sketch-viewer": [
        "dist/manekinekko/ngx-sketch-viewer"
      ]
    }
  }
}

./src/tsconfig.app.json
This tsconfig is specifically extending for the previous tsconfig used for the applications part excluding test/spec.

Click to expand
{
  "extends": "../tsconfig.json",
  "compilerOptions": {
    "outDir": "../out-tsc/app",
    "module": "es2015",
    "types": ["node"],
    "paths": {
      "@manekinekko/ngx-sketch-viewer": ["dist/manekinekko/ngx-sketch-viewer"]
    }
  },
  "exclude": ["src/test.ts", "**/*.spec.ts"]
}

./src/BUILD.bazel
For the src BUILD file i have almost the same as the example

Click to expand
package(default_visibility = ["//visibility:public"])

load("@angular//:index.bzl", "ng_module")
load("@build_bazel_rules_typescript//:defs.bzl", "ts_config", "ts_devserver")

ts_config(
    name = "tsconfig-spec",
    src = "tsconfig.spec.json",
    deps = [":tsconfig.json"],
)

ng_module(
    name = "src",
    srcs = glob(
        ["*.ts"],
        exclude = ["main.ts"],
    ),
    deps = [
        "//src/app",
        "@angular//packages/core",
        "@angular//packages/router",
    ],
)

ts_devserver(
    name = "devserver",
    additional_root_paths = [
        "npm/node_modules/zone.js/dist",
        "npm/node_modules/tslib",
        "npm/node_modules/@angular/material/prebuilt-themes",
    ],
    entry_module = "xlayers/src/main.dev",
    scripts = [
        ":require.config.js",
        ":module-id.js",
    ],
    # This is the URL we'll point our <script> tag at
    serving_path = "/bundle.min.js",
    static_files = [
        "@npm//node_modules/zone.js:dist/zone.min.js",
        "@npm//node_modules/tslib:tslib.js",
        "index.html",
    ],
    deps = ["//src"],
)

load("@build_bazel_rules_nodejs//:defs.bzl", "nodejs_binary", "rollup_bundle")

rollup_bundle(
    name = "bundle",
    additional_entry_points = [
        "src/app/home/home.module.ngfactory",
        "src/app/editor/editor.module.ngfactory",
    ],
    entry_point = "src/main.prod",
    deps = [
        "//src",
    ],
)

genrule(
    name = "copy_zonejs",
    srcs = ["@npm//node_modules/zone.js:dist/zone.min.js"],
    outs = ["zone.min.js"],
    cmd = "cp $< $@",
)

genrule(
    name = "copy_systemjs",
    srcs = ["@npm//node_modules/systemjs:dist/system.js"],
    outs = ["system.js"],
    cmd = "cp $< $@",
)

load("@build_bazel_rules_nodejs//:defs.bzl", "history_server")

history_server(
    name = "prodserver",
    data = [
        "index.html",
        ":bundle",
        ":copy_systemjs",
        ":copy_zonejs",
    ],
)

./src/app/BUILD.bazel
And the BUILD file that I suspect caused the crash.

Click to expand
package(default_visibility = ["//visibility:public"])

load("@angular//:index.bzl", "ng_module")

ng_module(
    name = "app",
    srcs = [
        "app.component.ts",
        "app.module.ts",
    ],
    deps = [
        "//src/environments",
        "@angular//packages/core",
        "@angular//packages/common/http",
        "@angular//packages/platform-browser/animations",
        "@angular//packages/service-worker",
        "@angular//packages/platform-browser",
        "@angular//packages/router",
    ],
)

Just ran into this issue also
Dropping down to typescript 2.9.0 solves this issue for the time being.
for me it's
error TS2318: Cannot find global type 'Array'.
error TS2318: Cannot find global type 'Boolean'.
error TS2318: Cannot find global type 'Function'.
error TS2318: Cannot find global type 'IArguments'.
error TS2318: Cannot find global type 'Number'.
error TS2318: Cannot find global type 'Object'.
error TS2318: Cannot find global type 'RegExp'.

even though I have this set
    "lib": ["es2017", "es2016", "es2015", "dom", "esnext"],

But the BUILD root file of the Angular sample mentions that the attribute "tsconfig" can be omitted by using it:
package(default_visibility = ["//visibility:public"])

alias(
    name = "tsconfig.json",
    actual = "//src:tsconfig.app.json",
)

@manekinekko In my case im trying to run a very simple nodejs script, no angular or any other libs.
This is our tsconfig ("//:tsconfig.json")
{
  "compileOnSave": false,
  "compilerOptions": {
    "baseUrl": "./",
    "outDir": "./dist/out-tsc",
    "sourceMap": true,
    "declaration": false,
    "moduleResolution": "node",
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "target": "esnext",
    "module": "commonjs",
    "typeRoots": ["node_modules/@types"],
    "types": ["node", "jasmine"],
    "paths": {
      "@workspace/*": ["libs/*"]
    }
  },
  "exclude": ["tmp", "dist", "bazel-out", "node_modules"],
  "bazelOptions": {
    "suppressTsconfigOverrideWarnings": false
  }
}

Since this works fine on 2.9.0 and is broken on > 3.0.0 I assume there must have been something that's changed there which needs updating in some config

I didn't re check ym rules_nodejs / rules_typescript versions, after updating those everything appears to be working again

After a long road of failure, I unfortunately have a new typing problem.
I have a "sketch.typings.ts" file in the src folder that contains all types of declarations globally but I now have an inclusion problem. I don't know how to include this file globally.
➜  xlayers git:(build/bazel) ✗ bazel run //src:prodserver
INFO: Invocation ID: ec1ca120-bf0e-4678-bef4-178a207701c7
INFO: Analysed target //src:prodserver (1 packages loaded, 16 targets configured).
INFO: Found 1 target...
ERROR: /Users/shikanime/Codes/sfeir-open-source/xlayers/src/app/core/BUILD.bazel:5:1: Compiling Angular templates (ngc) //src/app/core:core failed (Exit 1)
src/app/core/state/ui.state.ts(15,16): error TS2304: Cannot find name 'SketchData'.
src/app/core/state/ui.state.ts(16,17): error TS2304: Cannot find name 'SketchMSLayer'.
src/app/core/state/ui.state.ts(17,18): error TS2304: Cannot find name 'SketchMSLayer'.
src/app/core/state/ui.state.ts(18,19): error TS2304: Cannot find name 'SketchMSLayer'.
src/app/core/state/ui.state.ts(19,26): error TS2304: Cannot find name 'SketchMSPage'.
src/app/core/state/ui.state.ts(30,28): error TS2304: Cannot find name 'SketchData'.
src/app/core/state/ui.state.ts(39,29): error TS2304: Cannot find name 'SketchMSPage'.
src/app/core/state/ui.state.ts(44,28): error TS2304: Cannot find name 'SketchMSPage'.
src/app/core/state/ui.state.ts(49,29): error TS2304: Cannot find name 'SketchMSLayer'.
src/app/core/state/ui.state.ts(57,28): error TS2304: Cannot find name 'SketchMSLayer'.
src/app/core/state/page.state.ts(5,28): error TS2304: Cannot find name 'SketchMSPage'.
src/app/core/state/page.state.ts(8,8): error TS2304: Cannot find name 'SketchMSPage'.
src/app/core/state/page.state.ts(13,51): error TS2304: Cannot find name 'SketchMSPage'.

Target //src:prodserver failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 5.837s, Critical Path: 4.33s
INFO: 0 processes.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully

The issue was effectively due to missing "@npm//@types/node" and the "BUILD.bazel" at root project:
package(default_visibility = ["//visibility:public"])

alias(
    name = "tsconfig.json",
    actual = "//src:tsconfig.app.json",
)

actually works to omit the tsconfig attribute in each ts_library' and ng_module'.


documentation refactor

changed the docs structure to something modular and easier to maintain

Let me know if you want anything changed. I tried to update the documentation to reflect the current state of the project.


feat: add sip 10 decimal support

This isn't the most DRY implementation, but bc of how these pages/components are built, this might be the best solution until we can give the explorer more attention and remove query atoms like we have done in the web wallet. The ft/nft tokens really need to be handled separately so that the fetch for data isn't done conditionally (which breaks the rules of hooks, so can't do it). This does resolve issues with missing ft decimals for now.
Issues: #402, #506, and #604

:tada: This PR is included in version 1.18.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Failure recovery.

Failure detection and recovery, see more details in docs/Monitor_proposal.md

you can run go fmt ./... to format all the go code. (don't change go.mod)

you can run go fmt ./... to format all the go code. (don't change go.mod)


InitScripts doesn't work

Is this a request for help?:
Yes

What happened:
I want to add some command to Jenkins Master.
But no changes in my jenkins master, still no init script in my jenkins master container
What you expected to happen:
Container run the scripts every pods restart
How to reproduce it (as minimally and precisely as possible):
I added like this :
InitScripts:
- sh "apt update"
- sh "apt install vim"

You can check this code to see where the InitScripts are used:
https://github.com/helm/charts/blob/master/stable/jenkins/templates/config.yaml#L255-L258
You can only provide groovy scripts here. They are executed by Jenkins during startup.
. Post-initialization script

This repo contains some examples for init scripts: https://github.com/buildit/jenkins-startup-scripts/tree/master/scripts/scripts

@foosome  Did you switch to using Groovy for the script as @torstenwalter  mentioned?
e.g. something like
InitScript:
my-script-here: |-
import jenkins.model.*
groovy_code_here()


Feature/floating text

This Pull Request is for: (delete those that don't apply)

Adding a new feature: Floating Text

What this PR does

스크롤 위치에 따라  Fade in/out 하는 Floating Text 컴포넌트를 추가하였습니다.
적용 예시로 챕터1-2 부제목을 추가하였습니다.

Outcomes of merging this PR

How urgent is this PR

Urgent

확인했습니다~!


[Event Parameter change] table 5902 "Service Line" - OnAfterAssignGLAccountValues

    //OnAfterAssignGLAccountValues(Rec, GLAcc); A108F0025.Event.o
    OnAfterAssignGLAccountValues(Rec, ServHeader, GLAcc); //A108F0025.Event.n

Event Signature:
[IntegrationEvent(false, false)]
local procedure OnAfterAssignGLAccountValues(var ServiceLine: Record "Service Line"; ServiceHeader: Record "Service Header"; GLAccount: Record "G/L Account")
begin
    //A108F0025.Event Parameter ServiceHeader
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Rendering issues on Windows 11

Tried to run this on Python 3.10 and 3.11 on Windows 11, nothing is rendered except the walls... is there some known openGL issue on Windows 11? Also tried it inside WSLv2 with no luck - almost same issue but it's actually a bit worse...
Anyway it would be great if the readme mentioned some common issues such as this one.
Kudos for the great YouTube video though, and also the code looks really clean and approachable (except for the vertex/frag shaders, whose concept I still didn't quite grasp yet.

I just tested under Windows 11 and Python 3.11 and found no rendering issues (AMD Graphics Vega 8).

Same issue, Python 3.11 on Windows 10. Seems the translations of doors, npc and items are not working, also hud is weirdly off. See http://huelsebus-it-consulting.de/etc/debug.png for reference. This is taken by switching player collision detection off and walking straight back a bit. Debugging this for two days now, code is looking good ..

(Intel Iris XE Graphics, Nvidia RTX A2000 8GB Laptop GPU, moderngl 5.8.2, numpy 1.26.1, pygame 2.5.2, PyGLM 2.7.0)

Similar hardware here, Dell laptop with Intel Iris XE and Nvidia A2000 (though it seems the NVidia is not active)

Here's what I see in the console, right after python -m main:
pygame 2.5.1 (SDL 2.28.2, Python 3.11.6)
Hello from the pygame community. https://www.pygame.org/contribute.html
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: cHRM chunk does not match sRGB
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: cHRM chunk does not match sRGB
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: cHRM chunk does not match sRGB
...
Num level vertices:  4248

And this is what I see in the screen:

I'm having the same issue, were you able to solve this?

:( me too wouldve really loved to see this game in python

Still dosent work in 2024! Really excited to see if anyone could fix it. Im not very experienced with 3d rendering in python. I tried checking if pg.image.load was the problem. It has to do with saving the textures.

i am having the same issue too

@StanislavPetrovV hii man, got any ideas abot this problem?

Anyone have any solutions?

and this same thing is going on and on in an infinte loop in my console for as long as i am running the game.


corrected path for hash checks

changed 'ds105' to 'ds105_old' so file can run propoerly

Checks passed! Thanks.


Add basic smcl highlighting

Good idea. I was going to submit this as an issue/request. Glad it was on the mind of others too. To my knowledge there isn't an existing editor that gives smcl highlighting.

I've never had to write in it, but it seems like there's clear tags for bold, italics, bullet points, and code, so it should be easy to color those parts

I'll just go through help smcl and add some basic rules. I want to focus more time right now on stata-exec than the language though.

I rarely document my ados because of how tedious I find smcl writing. As an alternative route (and one that doesn't strictly belong on this repo), would it be possible to write a pandoc filter to do markdown <> smcl conversions? I think Sergio of reghdfe fame has written some pandoc filters, maybe that's an option?

You can start with https://github.com/michaelstepner/pandoc-smcl

Wow, didn't know this existed. Cheers!


Nuxeo harvesting error during content harvesting (401 Client Error)

28043 (UCI, collection with 50+ complex object records) and 27551 (UCSF, collection with 2 simple object records) are both experiencing errors during the "content harvesting" task in Airflow. Seems to be a 401 Client Error.
28043 logs: https://7a8067cb-3b99-477e-a883-7e311175a9b4.c3.us-west-2.airflow.amazonaws.com/dags/harvest_collection/grid?dag_run_id=manual__2024-03-04T17%3A11%3A59%2B00%3A00&task_id=content_harvesting.content_harvest
27551 logs: https://7a8067cb-3b99-477e-a883-7e311175a9b4.c3.us-west-2.airflow.amazonaws.com/dags/harvest_collection/grid?dag_run_id=manual__2024-03-04T18%3A57%3A19%2B00%3A00&task_id=content_harvesting.content_harvest

@christinklez We had the username misspelled in our MWAA config file. It should be fixed now. Can you try again?

Thank you--the authentication issue looks to be resolved! Was able to run through 27551 (and it's appearing in the stage index).
Parts of 28043 has run through successfully, though there seems to be an issue with some particular records. These errors do not seem to occur consistently.

See 49--4th attempt: https://7a8067cb-3b99-477e-a883-7e311175a9b4.c3.us-west-2.airflow.amazonaws.com/dags/harvest_collection/grid?dag_run_id=manual__2024-03-04T17%3A11%3A59%2B00%3A00&task_id=content_harvesting.content_harvest&tab=mapped_tasks&map_index=49 -- 3rd (previous) attempt ran fine
See 7---3rd attempt: https://7a8067cb-3b99-477e-a883-7e311175a9b4.c3.us-west-2.airflow.amazonaws.com/dags/harvest_collection/grid?dag_run_id=manual__2024-03-04T17%3A11%3A59%2B00%3A00&task_id=content_harvesting.content_harvest&tab=mapped_tasks&map_index=70 -- 4th & 5th (subsequent) attempts ran fine

I'm not quite clear on why the content harvester will occasionally report WARNING - State of this instance has been externally set to failed. Terminating instance - perhaps there are too many ECS containers running? Typically, I can rerun these failed tasks and they do work the second time around. This is definitely a completely different issue than the Nuxeo errors, and one I don't think is critical right at this moment.
The rest of the error messages reported in these logs are errors about trying to report the error out to SNS/SQS/ultimately the registry. I'm currently working on fixing that, actually.

Thank you! I was eventually able to run 28043 completely through, so I'm going to close this issue out for the moment!
If I come across this error again, I'll track it in a new issue. Thank you!


Add a single-node cockroachdb option, and test for same

Description of changes
CockroachDB has a separate entrypoint for use when being run in single-node mode.
This is useful for testing -- not just testing cockroachdb itself (although it does add value there, as testing clustered mode requires a paravirtualized clock), but also testing client software that uses cockroachdb.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

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

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

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

[ ] Fits CONTRIBUTING.md.

@thoughtpolice, I'm curious for your thoughts not just on the PR itself, but also the metadata -- should I set myself as maintainer for this test? Do you want to own it? Should we both be in the list?


Ensure creating of new Outlook webhook every time new connector is added to channel

We have following code that creates connector on our configuration page (essentially an excerpt from ToDo connector sample):
microsoftTeams.settings.setSettings({
	entityId: "myConnector",
	contentUrl: window.location.href,
	configName: "Connector added by msteams@user"
});

How to ensure resulting webhook url that is generated when we do getSettings later is new and unique? Should we add some guid to entityId or configName? I don't think it's documented anywhere. I've tried Jira Cloud connector, it has such feature, but it uses non-generic webhook url format that is special for Jira Cloud Connector and is handled presumably on the server-side.

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

ID: c21a27c1-d01a-6cc7-c991-73af6492aad8
Version Independent ID: b15d2142-df29-250e-9a0a-b734dcb93162
Content: Office 365 Connectors - Teams
Content Source: msteams-platform/concepts/connectors/connectors-creating.md
Product: msteams
GitHub Login: @o365devx
Microsoft Alias: o365devx

@Wajeed-msft I guess you may have some insight on the above.

@crow-ua - You get a different Webhook URL every time you configure the Connector. Could you please check it one more time if you are getting same URL? If you have manifest which we can use to repro, please send it to Microsoft Teams developer support alias mention on Feedback channel.


[18.09 backport] vendor: update buildkit to d9f75920

Backport of https://github.com/moby/moby/pull/38339
brings in fix for setuid binaries moby/buildkit#745
Signed-off-by: Tonis Tiigi<EMAIL_ADDRESS>(cherry picked from commit 32f48058158cce7a6a1f8f0d1526d8224b369cbc)

experimental failure is a flaky test https://github.com/moby/moby/issues/32673
14:25:52 FAIL: docker_api_swarm_test.go:296: DockerSwarmSuite.TestAPISwarmLeaderElection
14:25:52
14:25:52 [da1b414a33714] waiting for daemon to start
14:25:52 [da1b414a33714] daemon started
14:25:52
14:25:52 [d0b940dc53125] waiting for daemon to start
14:25:52 [d0b940dc53125] daemon started
14:25:52
14:25:52 [dfc2453d8e247] waiting for daemon to start
14:25:52 [dfc2453d8e247] daemon started
14:25:52
14:25:52 [da1b414a33714] exiting daemon
14:25:52 assertion failed: error is not nil: Error response from daemon: rpc error: code = DeadlineExceeded desc = context deadline exceeded
14:25:52 [d0b940dc53125] exiting daemon
14:25:52 [dfc2453d8e247] exiting daemon


Set key exchange explcitly

Hi there!
Thank you for the PR.
I've tried your change - does this match your expected behaviour?

Testing with username/password authentication.

Log in to FortiOS 5.4.0 and dh-group modified, set to 1024
a) Without proposed change aka current public version: Works
b) With proposed change: Works

Log in to FortiOS 5.4.0 and dh-group set to 2048 (default)
a) Without proposed change aka current public version: Does NOT work
b) With proposed change: Works

Log in to FortiOS 5.2.8 (no dh-group setting)
a) Without proposed change aka current public version: Works
b) With proposed change: Works

One more question - do you know if this (known) issue has any reference like a ticket or bug ID with Fortinet? Something that we could cross-reference maybe.
Thanks!
/Stefan

OK I just found official information on this from Fortinet, so it only affects 5.4.0:
http://kb.fortinet.com/kb/documentLink.do?externalID=FD38109
Did two more tests to verify this:

Log in to FortiOS 5.4.3 and dh-group modified, set to 1024
a) Without proposed change aka current public version: Works
b) With proposed change: Works

Log in to FortiOS 5.4.3 and dh-group set to 2048 (default)
a) Without proposed change aka current public version: Works
b) With proposed change: Works

I believe it is much more than just 5.4
From Napalm docs: http://napalm.readthedocs.io/en/latest/support/fortios.html

Beginning in FortiOS version 5.2, a Fortigate bug was introduced that generates an EOFError in paramiko/transport.py during the SSH key exchange.

The documentation you provided only states that "Fixed in the FortiOS version 5.4.1."
v5.2.5,build701 (GA) [Update]
a) Without proposed change aka current public version 0.49: Does not work
b) With proposed change: Works
That being said, perhaps it makes sense to grab the current key exchanges, and dynamically re-order them, in case paramiko adds any more in the future.
Let me know your thoughts.

Oh.
Yes, I can see someone mentioning that some behaviour was modified in 5.2.7...
https://github.com/paramiko/paramiko/issues/687#issuecomment-196577317
I think it makes sense to merge this PR anyway, since it seems to solve the versions we've encountered so far! 👍  (and doesn't seem to break anything obvious)


OF-2019 Postpone archiver creation until last possible moment

Do not create the archiver before its first use. This saves performance overhead for situations where conversation logging is not used.

Thanks Emiel!


Freeimage plugin not building

Hey!
Thanks for the great job you did here. I managed to run a test app on 13.4.0 in not much time.
However, I noticed a small issue with the freeimage plugin build option activated. Findfreeimage.cmake seems to be doing its job, and related variables look like what's expected, but the plugin DLL file is not built.
I noticed this when trying to replace your version of freeimage with the package on conancenter (it's quite new there). I observe the same behavior using theirs or yours. I thought you may want to know stuff like that. I've also found a few other issues will trying to build, so tell me whether to open other issues here (or not, or whatever else is most convenient for you). Some of them seem to be caused by Ogre itself, but it's hard to be certain without digging further.
Here's my configuration:
[settings]
arch=x86_64
arch_build=x86_64
build_type=Release
compiler=Visual Studio
compiler.runtime=MD
compiler.version=17
os=Windows
os_build=Windows

Here's my test command (after adding your remote to conan):
conan install -b missing -o ogre3d:with_freetype=True -o ogre3d:with_sdl=True -o ogre3d:with_qt=False -o ogre3d:install_samples=True -o ogre3d:install_tools=True -o ogre3d:bindings_csharp=False -o ogre3d:bindings_java=False -o ogre3d:bindings_python=False -o ogre3d:rendersystem_direct3d11=True -o ogre3d:rendersystem_direct3d9=True -o ogre3d:rendersystem_metal=False -o ogre3d:rendersystem_opengl=True -o ogre3d:rendersystem_opengl3=True -o ogre3d:rendersystem_opengles=False -o ogre3d:rendersystem_tiny=False -o ogre3d:rendersystem_vulkan=False -o ogre3d:plugin_assimp=True -o ogre3d:plugin_bsp=True -o ogre3d:plugin_dotscene=True -o ogre3d:plugin_exrcodec=True -o ogre3d:plugin_freeimage=True -o ogre3d:plugin_glslang=True -o ogre3d:plugin_octree=True -o ogre3d:plugin_particlefx=True -o ogre3d:plugin_pcz=True -o ogre3d:plugin_stbi=True -o ogre3d:component_bites=True -o ogre3d:component_meshlodgenerator=True -o ogre3d:component_overlay=True -o ogre3d:component_overlay_imgui=True -o ogre3d:component_paging=True -o ogre3d:component_property=True -o ogre3d:component_rtshadersystem=True -o ogre3d:component_terrain=True -o ogre3d:component_volume=True -o ogre3d:enable_astc=True -o ogre3d:enable_dds=True -o ogre3d:enable_double=False -o ogre3d:enable_etc=True -o ogre3d:enable_gl_state_cache_support=True -o ogre3d:enable_gles2_glsl_optimiser=True -o ogre3d:enable_meshlod=True -o ogre3d:enable_node_inherit_transform=False -o ogre3d:enable_pvrtc=True -o ogre3d:enable_quad_buffer_stereo=False -o ogre3d:enable_viewport_orientationmode=False -o ogre3d:enable_zip=True -o ogre3d:build_tests=False --require-override zlib/1.2.12 ogre3d/13.4.0@sintef/stable

Ogre's CMake output excerpts:
...

-- DEPENDENCIES_DIR: C:/Users/USER/.conan/data/ogre3d/13.4.0/sintef/stable/build/f77bbe66e72644efad0228a825032c7ddda1a46b/Dependencies
-- Conan: Using autogenerated Findfreeimage.cmake
-- Found freeimage: 3.18.0 (found version "3.18.0")
-- Library freeimage found C:/Users/USER/.conan/data/freeimage/3.18.0/sintef/stable/package/9eb03a6803e93bee466f91e08c6f86e900042f8d/lib/freeimage.lib
-- Found: C:/Users/USER/.conan/data/freeimage/3.18.0/sintef/stable/package/9eb03a6803e93bee466f91e08c6f86e900042f8d/lib/freeimage.lib

...

-- The following external packages were located on your system.
-- This installation will have the extra features provided by these packages.
+ freetype
+ OpenGL
+ OpenGL ES 2.x
+ DirectX11
+ OpenEXR
+ Python
+ pugixml
+ zlib
+ Assimp
+ Bullet
+ SDL2
-----------------------------------------------------------------------------
-- The following OPTIONAL packages could NOT be located on your system.
-- Consider installing them to enable more features from this software.
+ freeimage: Support for commonly used graphics image formats <http://freeimage.sourceforge.net>
+ DirectX9: Support for the DirectX render system <http://msdn.microsoft.com/en-us/directx/>
+ cg: C for graphics shader language <http://developer.nvidia.com/object/cg_toolkit.html>
+ Vulkan SDK: Vulkan RenderSystem, glslang Plugin. Alternatively use system packages <https://vulkan.lunarg.com/>
+ SWIG: Language bindings (Python, Java, C#) for OGRE <http://www.swig.org/>
+ Qt: optional integration with the Qt Library for window creation and input <http://www.qt.io/>
+ Doxygen: Tool for building API documentation <http://doxygen.org>
+ Softimage: Softimage SDK needed for building XSIExporter <>
-----------------------------------------------------------------------------

--
----------------------------------------------------------------------------
  FEATURE SUMMARY
----------------------------------------------------------------------------

Building components:
  + Bites
  + Bullet
  + MeshLodGenerator
  + Overlay
  + Overlay Dear Imgui
  + Paging
  + Property
  + RTShader System
  + RTShader System Shaders
  + Terrain
  + Volume
Building plugins:
  + BSP scene manager
  + Glslang (SPIRV) program manager
  + Octree scene manager
  + OpenEXR image codec
  + STBI codec (generic)
  + Portal connected zone scene manager
  + Particle FX
  + DotScene loader
  + Assimp loader (.obj, .ply, .fbx and more)
Building rendersystems:
  + Direct3D 11
  + OpenGL
  + OpenGL 3+
  + OpenGL (all) StateCacheManager
Building executables:
  + Samples
  + Tools
Building core features:
  + Mesh Lod
  + DDS image codec (.dds)
  + PVRTC image codec (.pvr)
  + ETC image codec (.pkm, .ktx)
  + ASTC image codec (.astc)
  + ZIP archives
  + Multi-threaded WorkQueue

Build type:                      shared
Use double precision:            disabled
Assert mode:                     exceptions

CMakeCache.txt excerpts:
//Details about finding freeimage
FIND_PACKAGE_MESSAGE_DETAILS_freeimage:INTERNAL=[3.18.0][v3.18.0()]

....

//Build FreeImage codec.
OGRE_BUILD_PLUGIN_FREEIMAGE:INTERNAL=True

And last, freeimage's directory is correctly filled in conanbuildinfo.txt

Thanks for letting us know! (And sorry for the late response.) Feel free to open more issues. We can't promise that they will get fixed anytime soon; we only have the capacity to fix problems when they directly affect our own work. But a bug report is useful both for us and for other users who should be aware of the issues, and it's also a good way for us to notify our users when the bugs eventually get fixed.

Thanks for the great job you did here.

Actually, I think we should be thanking you for your work. I just realised that you are the author of the package recipe we forked to create this one. :)


Weak references

weak T? should behave essentially like Optional<T&> in C++ but with the added feature that it automatically empties itself when the T is destroyed.
weak T is not allowed, since that implies it's always in a dereferenceable state.

Hmm, shouldn't weak T imply T?? Because there is no other possible state for a weak pointer, I don't really see the point of requiring additional tokens when weak provides adequate meaning regardless.

The ? token is for readability, and symmetry with other optional types.


fix(structures): Missing and incorrect guild props

This PR

adds missing property nsfw
fix typo on property  approximate_presence_count.
changes the type of welcome_screen from WelcomeScreen[] to WelcomeScreen.
makes channels and voice_states optional.

Overriding review requirements as this is a small fix


A better separation for viewing new links

Hey there.
I often come to this repo to find some great things ready to use or to take some inspiration off.
Notice the word "often".
Everytime I return in here, I have to manually go through the commits to see what's new.
That's terrible and time consuming. Not only I have to check for actual links that interest me, but I have to copy the links and paste it on the browser every time instead of copying them (because of MDX syntax).
Also, there is no easy way to tell where I stopped last time.
My suggestion is pretty simple: Add or a update note according to month or something, or in the project description separate it by putting last added items first.
It would be a far greater experience.
Overall, nice repo biro & nice work for the people that go out there mining those in the deepens of the JS weird ecossystem.

Thank you for your feedback, @guibzo!
The repository has been updated with tables to make browsing and finding links much easier. Additionally, we’ll start adding update notes moving forward to improve the overall experience and help you track what’s new more effectively.
We appreciate your suggestion and hope the updates enhance your experience! 🚀


Check for previous/existing GitHub issues/module proposals

[X] I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

[X] I have checked for that this module doesn't already exist in the module indexes.

Bicep or Terraform?
Terraform
Module Classification?
Resource Module
Module Name
avm-res-machinelearningservices-workspace
Module Details
Module to provision the Azure machine leaning workspace, together with their compute (like specified the way to do it here https://github.com/Azure/terraform/tree/master/quickstart/101-machine-learning).
https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/machine_learning_workspace
Do you want to be the owner of this module?
Yes
Module Owner's GitHub Username (handle)
Nepomuceno
(Optional) Secondary Module Owner's GitHub Username (handle)
RenSilvaAU

Hi @avm_module_owner,
Thanks for requesting/proposing to be an AVM module owner!
We just want to confirm you agree to the below pages that define what module ownership means:

Team Definitions & RACI
Shared Specification (Bicep & Terraform)
Module Support

Any questions or clarifications needed, let us know!
If you agree, please just reply to this issue with the exact sentence below (as this helps with our automation 👍):
"I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER"
Thanks,
The AVM Core Team
#RR

I CONFIRM I WISH TO OWN THIS AVM MODULE AND UNDERSTAND THE REQUIREMENTS AND DEFINITION OF A MODULE OWNER

@mbilalamjad, as this resource is Microsoft.MachineLearningServices/workspaces, its name must be avm-res-machinelearningservices-workspace. Please change the title and description of this issue accordingly. Thanks!

Note: this is the equivalent of the Bicep module [avm/res/machine-learning-services/workspace](https://github.com/Azure/Azure-Verified-Modules/issues/697).

Oh that has been changed now thanks @matebarabas

Hi @Nepomuceno,
Thanks for confirming that you wish to own this AVM module and understand the related requirements and responsibilities!
Before starting development, please ensure ALL the following requirements are met.
Please use the following values explicitly as provided in the module index page:

For your module:

ModuleName - for naming your module
TelemetryIdPrefix - for your module's telemetry

For your module's repository:

Repo name and folder path are defined in RepoURL
Create GitHub teams for module owners and contributors and grant them permissions as outlined here.
Grant permissions for the AVM core team and PG teams on your GitHub repo as described here.

Check if this module exists in the other IaC language. If so, collaborate with the other owner for consistency. 👍
You can now start the development of this module! ✅ Happy coding! 🎉
Please respond to this comment and request a review from the AVM core team once your module is ready to be published! Please include a link pointing to your PR, once available. 🙏
Any further questions or clarifications needed, let us know!
Thanks,
The AVM Core Team

Repo has been created
https://github.com/Azure/avm-res-machinelearningservices-workspace/


if I use both Dropdown and OnValueChanged, the OnValueChanged method will execute twice.

Here is my code:
public enum Mode
{
    Normal,
    Url
}

[NaughtyAttributes.Dropdown( "modeValues" )]
[NaughtyAttributes.OnValueChanged( "OnModeChange" )]
public Mode mode;

NaughtyAttributes.DropdownList<Mode> modeValues()
{
    return new NaughtyAttributes.DropdownList<Mode>() {
        { "Normal",   Mode.Normal },
        { "Url",    Mode.Url },
    };
}

void OnModeChange()
{
    print( mode );
}

I use both Dropdown and OnValueChanged.
It appears the method OnModeChange() executes twice.
I'm using Naughty Attributes 2.1.4.

This problem is not limited to DropDown. AllowNesting also reproduces it, and I'm guessing most other Naughty Attributes do too.
NaughtyEditorGUI.PropertyField_Implementation calls propertyFieldFunction.Invoke, which eventually calls PropertyDrawerBase.OnGUI, and both call PropertyUtility.CallOnValueChangedCallbacks. Is this intentional?

I also noticed this issue.


added a warning when xdebug is loaded in cli

Xdebug being loaded reduces the runtime performance considerably. inform the user about it. refs #1066.
This was also a major problem when running composer, therefore we added this warning there like we do here.
see it in action:

in case we are ok with linking a article which describes the issue further, we could add a link to https://getcomposer.org/xdebug
please tell me what you guys think

@marcj any feedback?

Yeah why not :)


Link to Programming in Lua

the Lua Programming Gems book is not freely available (apart from the second chapter and notes for some other chapters), and is not a general guide to the language; the first edition of Programming in Lua, however, is freely available, and is a guide for learning the language in general.

Really appreciate this sort of PR. Thanks.


[EFR32] Commissioning is failing at step 13 : Unsupported certificate format

Problem
While doing the commissioning using the BLE-wifi after resetting the DUT sometimes commissioning failed with an error unsupported certificate format. this is causing an interrupt in the automation testing of the test harness.
App used - lock app
Platform - Chip-tool - RPI-4, 8GB RAM
DUT - EFR32 + WF200 , EFR32 +RS9116
Network - Ble-wifi
Logs
chip-tool-step13-error.txt
device-step13-error.txt

Some initial log analysis:
[chip-tool]
[1658315004.845157][5619:5624] CHIP:CTL: Device returned status 3 on receiving the NOC
[1658315004.845228][5619:5624] CHIP:CTL: Add NOC failed with error ../../src/controller/CHIPDeviceController.cpp:1271: CHIP Error 0x00000050: Unsupported certificate format
[1658315004.845302][5619:5624] CHIP:CTL: Error on commissioning step 'SendNOC': '../../src/controller/CHIPDeviceController.cpp:1271: CHIP Error 0x00000050: Unsupported certificate format'
[1658315004.845359][5619:5624] CHIP:CTL: Failed to perform commissioning step 13
[165

NOCResponse(Status=3) is InvalidNOC from device.  I couldn't find the NOC bytes in the log.  Could you post the malformed NOC TLV hexstream to this issue?


[Opaque result types] Fix mangling issues with opaque result types.

Fix a trio of issues involving mangling for opaque result types:

Symbolic references to opaque type descriptors are not substitutions
Mangle protocol extension contexts correctly
Mangle generic arguments for opaque result types of generic functions

The (de-)serialization of generic parameter lists for opaque type
declarations is important for the last bullet, to ensure that the
mangling of generic arguments of opaque result types works across
module boundaries.
Fixes the rest of rdar://problem/50038754.

@swift-ci please smoke test and merge

Thanks Slava for finding the unnecessary change in ASTMangler.cpp. I've removed it.

@swift-ci please smoke test

@swift-ci please smoke test

17:40:20 Using 'Changelog to branch' strategy.
17:40:20 fatal: bad revision '^origin/master'

@swift-ci please smoke test macOS


suppress SA0001 for a project without suppressing in ruleset

How do I suppress SA0001 for a project without suppressing in my ruleset?  Is there some analogy to Code Analysis' GlobalSuppressions.cs?

SA0001 should never be disabled. In all cases where it is reported, the compiler is behaving incorrectly in ways that affect even the built-in IDE features.

Maybe I'm misunderstanding that rule.   I thought it warns when XML doc is turned off?  We don't turn-on XML doc in Test projects.

@SurajGupta Yes, it is frequently misunderstood. Disabling XML documentation is always a problem, even in test projects. My recommendation for test projects is the following:

Leave SA0001 enabled
Enable documentation generation
Disable SA1573 and SA1591 in one of the manners described in SA0001.md

This will fix the compiler analysis of documentation comments without reporting warnings for any cases where comments are not added.

Hi Sam - at a high level you're saying that we can achieve the same effect (not require documentation in Test projects), but enabling XML Doc and then suppressing CS1573 and CS1591 (you meant CS, not SA, right?)

Yes, that is correct (both in approach and identification of my typo).

Hi @sharwell,
could you please be more specific in which respect the compiler is behaving incorrectly on what IDE features are affected?

SA0001 should never be disabled. In all cases where it is reported, the compiler is behaving incorrectly in ways that affect even the built-in IDE features.

Is it by that meant only

Each project should be configured to include an XML documentation file with the compiled output. Otherwise, the semantics of all documentation comments are not checked and comments are likely to contain an increasing number of errors over time.

as described on SA0001.md or anything more? Thanks!

could you please be more specific in which respect the compiler is behaving incorrectly on what IDE features are affected?

The compiler is treating /// comments as if they were // comments. The most common side effect of this is having cref attributes that are incorrect and/or outdated. We also see a bunch of cases where the XML structure of the comment can't be parsed, which leaves Quick Info unable to use them.

Thanks! It means, if no /// were used in the code, it's safe to disable documentation generation, right?


Go Modules

This change will pin Open Match dependencies to predictable versions. This will allow for more reproducible builds since go get pulls code from repository HEAD, with the exception of aliased repos like gopkg.in.
After looking at go modules and vendoring it turns out the vendor/ directory is not touched if you build with go mod.
The recommended way is to just check in the go.mod and go.sum files to pin your dependencies to a known good checkout and download the dependencies one time.
The dependency output will be copied to $GOPATH/pkg/mod.
This change will set the minimum golang version for Open Match to 1.11. 1.12 is the latest version, 1.13 will turn go mod on by default.
For now you'll need to add this to your ~/.bashrc
export GO111MODULE=on

https://github.com/GoogleCloudPlatform/open-match/issues/91 is the related issue for this.


Fix an bug where the user would see the authentication screen being presented & dismissed over and over again if authorization failed.

Verified that @crousselle has signed the CLA. Thanks for the pull request!

LGTM


Integrated Onboarding

Onboarding: Application + Scheduling Interview + Team Matching + Scholarship + Payment - all one field in database

Director of Ops must be part of requirement building
Need to weigh pros/cons of solution and Airtable, which currently satisfies problems, with exception of payment
First priority here: integrating payment. Other aspects could be prioritized lower or deemed backlog until Airtable proves more difficult


Remove files that should not have been committed

Overview
Several files/folders, many/all of them in the .gitignore currently, found their way into some commit. We should purge from the commit history, or at least the latest commit.

.idea/
.DS_Store
_downloads/? (chebi.owl.gz)
data/? (several)
project/: I think this is LinkML cookie cutter stuff. Maybe we need some of it. We could potentially remove some stuff we don't need, e.g. shacl.

Addressed by:

#94 @


Megasync fails to build

Describe the bug
Megasync isn't building any more, on unstable.
To Reproduce
Steps to reproduce the behavior:

Try to install Megasync with nix-env -iA nixos.megasync
Notice that the build fails.

Expected behavior
Megasync would install correctly.
Additional context
Some of the error is this:
In file included from /nix/store/w9v6l1nacaw3gk63p3jjybrxk37jqji8-qtbase-5.14.2-dev/include/QtCore/qobject.h:47,
                 from /nix/store/w9v6l1nacaw3gk63p3jjybrxk37jqji8-qtbase-5.14.2-dev/include/QtCore/QObject:1,
                 from control/MegaDownloader.h:4,
                 from control/MegaDownloader.cpp:1:
/nix/store/w9v6l1nacaw3gk63p3jjybrxk37jqji8-qtbase-5.14.2-dev/include/QtCore/qstring.h:691:41: note: declared here
  691 |     QT_DEPRECATED static inline QString fromAscii(const char *str, int size = -1)
      |                                         ^~~~~~~~~
control/MegaDownloader.cpp:27:60: warning: 'static QString QString::fromAscii(const char*, int)' is deprecated [-Wdeprecated-declarations]
   27 |     if (!dir.exists() && !dir.mkpath(QString::fromAscii(".")))
      |                                                            ^
In file included from /nix/store/w9v6l1nacaw3gk63p3jjybrxk37jqji8-qtbase-5.14.2-dev/include/QtCore/qobject.h:47,
                 from /nix/store/w9v6l1nacaw3gk63p3jjybrxk37jqji8-qtbase-5.14.2-dev/include/QtCore/QObject:1,
                 from control/MegaDownloader.h:4,
                 from control/MegaDownloader.cpp:1:
/nix/store/w9v6l1nacaw3gk63p3jjybrxk37jqji8-qtbase-5.14.2-dev/include/QtCore/qstring.h:691:41: note: declared here
  691 |     QT_DEPRECATED static inline QString fromAscii(const char *str, int size = -1)
      |                                         ^~~~~~~~~
make[1]: Leaving directory '/build/source/src/MEGASync'
make: *** [Makefile:47: sub-MEGASync-make_first] Error 2
builder for '/nix/store/jn7ha1a71a7dcxkq9xpkssivhvd9mxm4-megasync-<IP_ADDRESS>.drv' failed with exit code 2
error: build of '/nix/store/jn7ha1a71a7dcxkq9xpkssivhvd9mxm4-megasync-<IP_ADDRESS>.drv' failed

Notify maintainers
@michojel
See also #83833?
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
these paths will be fetched (0.05 MiB download, 0.28 MiB unpacked):
  /nix/store/hfvjs6abgzadrv9f387v1ip5mr206jh9-bash-interactive-4.4-p23-dev
copying path '/nix/store/hfvjs6abgzadrv9f387v1ip5mr206jh9-bash-interactive-4.4-p23-dev' from 'https://cache.nixos.org'...
 - system: `"x86_64-linux"`
 - host os: `Linux 5.9.1, NixOS, 21.03pre249162.1dc37370c48 (Okapi)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.8`
 - channels(root): `"nixos-21.03pre249162.1dc37370c48"`
 - channels(jon): `"home-manager, nixpkgs-21.03pre250049.4b30d5601da"`
 - nixpkgs: `/home/jon/.nix-defexpr/channels/nixpkgs`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

This is the real error:
control/CrashHandler.cpp: In function 'void signal_handler(int, siginfo_t*, void*)':
control/CrashHandler.cpp:210:20: error: 'sys_siglist' was not declared in this scope; did you mean 'sys_sigdelset'?
  210 |             oss << sys_siglist[sig] << " (" << sig << ") at address " << std::showbase << std::hex << info->si_addr << std::dec << "\n";
      |                    ^~~~~~~~~~~
      |                    sys_sigdelset

Can you provide the latest NixOS version in which you had this package working? I'd like to bisect the tree and see when exactly it got broken.

Sorry for the inconvenience.
Builds fine for me on nixos-20.09
I can take a look and fix it tomorrow. Let's see if the newer upstream version makes a difference.

until resolved in nixpkgs, one should be able to use the following overlay: https://github.com/michojel/NixOS/blob/master/overlays/megasync.nix


Unable to step into inside conda env, python debugger

I am using python debugger inside conda env. I set the pythonPath to the conda env bin location. When I using python debugger step into is not working, it is not opening the file to which I want to step into.
Here I placed a breakpoint at line 46 and when I click step into it should ideally go into __call__ method inside /home/winter_soilder/anaconda3/envs/pytorch/lib/python3.8/site-packages/torch/nn/modules/module.py but it directly goes to line 22 of the forward function.

settings.json ->
{
    "python.pythonPath": "/home/winter_soilder/anaconda3/envs/pytorch/bin/python",
    "python.autoComplete.extraPaths": [
        "/home/winter_soilder/anaconda3/envs/pytorch/lib/python3.8/site-packages/torch",
        "/home/winter_soilder/anaconda3/envs/pytorch/lib/python3.8/site-packages/torchvision"
    ]
}

lauch.json ->
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal"
        }
    ]
}

@greatsharma To debug inside site-packages add "justMyCode": false to your debug configuration in launch.json.


docs(tooltip): fix multiline comment in types

Scope

[x] Patch: Bug Fix
[ ] Minor: New Feature
[ ] Major: Breaking Change

thank you @simPod 🤗


Add 5 retries when downloading the production bundle catalog manifests

Add 5 retries when downloading the production bundle catalog manifests with a delay of 10 seconds between retries.

LGTM


i.MX93: enable lpi2c and lpspi

Imporve the way we handle mmu region for i.MX93
Enable LPI2C and LPSPI on i.MX93
Add rumtime mmio capability to LPI2C driver (to demostrate the concept, see below discussion)

Need discussion:
Should we :

add runtime mmio support to all these drivers (like I did to lpi2c driver in a separate commit),
or
manually add memroy space in "mmu_regions" array (the old way, but get improved in this pr)?

also @JiafeiPan here.

@CkovMk , I see changed to the lpi2c driver. However no changes were made to the lpspi driver. Any reason this driver was not changed?

@CkovMk , I see changes to the lpi2c driver. However no changes were made to the lpspi driver. Any reason this driver was not changed?

@mmahadevan108 No. I changed lpi2c driver to show the idea, because I'm in doubt whether it will be accepted. If we decided to update most of our driver to use mmio, I will update lpspi driver as well. Otherwize, I will simply drop that commit and follow the old approach.
At first, I decided to use mmio because we want to avoid editing mmu_regions[] everytime adding or removing an instance (e.g. lpi2c8 on rpi header) in the application. However, since the mmu_regions[] array can use information from devicetree and map all status="okay" nodes that are compatiable to a driver, the initial problem has gone. So now it is only a matter of preference: do we update drivers to adopt mmio api.

@danieldegrasse patches are split to:

enable runtime mmio
add driver in soc
add driver to board
for both lpi2c and lpspi.

@carlocaione marco "MMU_REGION_DT_FLAT_ENTRY" is added to arch/arm and arch/arm64.

CI shows test failures unrelated to this pr.
There are also some format issues (use tabs for indent, etc.) will fix in next update.

rebase on main to adopt changes to lpspi driver.

LGTM for the MMU_REGION_ macro changes. You maybe want to consider pushing the MMU changes as separate PR.

split as #66869.
MMU changes have been removed from this pr.

also remove the MCUX_HAS...


Any plans to update the library to d3 v5 ?

For some other projects I do need to use d3 v5. It would be amazing to get the d3-tip library fully compatible. Unfortunately I wouldn't even know where to start.

Hi @elChapoSing, I no longer actively use this library so I likely won't update it to v5.  Sorry for that.


fix issue that sometimes there is conflict between distutils and setuptools

Description
Distutils and setuptools provide same class name for Extension, so we should carefully sort the import order to avoid this issue.
NOTE:
I cannot repro it on my mac with several version of setuptools, need the help of issue owner to double confirm with it. But it does exist, details see:
https://github.com/pypa/setuptools/issues/309
Changes:
Seems like our old import order should work for this issue, but still try to apply fix from another project to make sure it would work. https://github.com/ucgmsim/IM_calculation/pull/65
Update:
This fix use distutils.extension.Extension to override Extension from setuptools, should the type checking in build_ext method will not failed any more.
Linked issue(s)/Pull request(s)
#207
Type of Change

[ ] Non-breaking bug fix
[x] Breaking bug fix
[ ] New feature
[ ] Test
[ ] Doc update
[ ] Docker update

Related Component

[ ] Simulation toolkit
[ ] RL toolkit
[ ] Distributed toolkit

Has Been Tested

OS:

[ ] Windows
[ ] Mac OS
[ ] Linux

Python version:

[ ] 3.6
[ ] 3.7

Key information snapshot(s):

Needs Follow Up Actions

[ ] New release package
[ ] New docker image

Checklist

[ ] Add/update the related comments
[ ] Add/update the related tests
[ ] Add/update the related documentations
[ ] Update the dependent downstream modules usage

Codecov Report

Merging #208 (e44c599) into master (25642a4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #208   +/-   ##
=======================================
  Coverage   72.06%   72.06%
=======================================
  Files          86       86
  Lines        4066     4066
=======================================
  Hits         2930     2930
  Misses       1136     1136

Flag
Coverage Δ

unittests
72.06% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 25642a4...e44c599. Read the comment docs.

I need to double confirm with this fix.

A little details that still confuse me, following is the code from distutils.build_ext and setuptools.extension,  it shows that setuptools.extension inherit from distutils.extension.Extension, but isinstance may failed at some condition.
setuptools.extension:

_Extension = get_unpatched(distutils.core.Extension)

class Extension(_Extension):

distutils:

```python
        for i, ext in enumerate(extensions):
            if isinstance(ext, Extension):
                continue                # OK! (assume type-checking done
                                        # by Extension constructor)

            if not isinstance(ext, tuple) or len(ext) != 2:
                raise DistutilsSetupError(
                       "each element of 'ext_modules' option must be an "
                       "Extension instance or 2-tuple")


Check/create a list of foundation issues that need to be fixed in order to move towards OpenSCD-core

As a PO
I would like to know what needs to done in OpenSCD-core migration
So I can prioritize/plan activities and reduce frustration
Background;
During the CoMPAS open migration, @juancho0202 and others noticed that basic stuff is needed to move on.
Acceptance criteria:
Open list/project with all related (on Github)
Diagram with dependencies (if needed)
Todo: make a list of foundation issues that needs to be fixed

See: https://github.com/openscd/open-scd/discussions/1211

See: https://github.com/orgs/openscd/projects/2

First the components, migrate the plug-ins afterwards.


Update MVC dependencies

Actually, looks like CreateActionModel_RouteOnController_CreatesOneActionInfoPerRouteTemplateOnAction is failing

There are existing tests failing on the build server. About 41~.
If there are no new test failures then I want to merge this just to get MVC unbroken locally. Test fixes can come afterwards.


Correctly fetch script document for Go-to-Definition

This is more consistent with find-all-references which uses the same function.


Add AWS Secrets Manager as a configuration provider.

Add the possibility to use AWS Secrets Manager for configuration

The feature will only activate if the "BAGET_AWS_SECRETS_PATH" configuration key exists.
Requires (under most circumstances) to specify BAGET_AWS_SECRETS_REGION to know in which AWS region is the Secrets Manager of interest.

Addresses https://github.com/loic-sharma/BaGet/issues/561

@loic-sharma  Do you have any comments on my PR? I'll be happy to discuss.


git force push should check for remote changes before pushing

In effort to avoid lost commits, the force push command should check for remote changes in the branch and prompt to continue. Perhaps a -f (force) flag can be added to forgo this check.

@teeohhem Option --force-with-lease exists for this purpose.
Although I agree, the -f option is dangerous. So I have some suggestions to fix this:

bind -f to --force-with-lease and -F to --force
add an config option (e.g. push.defaultForceStrategy) which can be set to withLease or hard or something like that.

Hey, this is the issue tracker for the git-scm.com website, not Git itself. If you still want to discuss this issue, you should reach out to the community.