cfstream_test fails after c-ares was enabled

cfstream_test fails after c-ares resolver was enabled. The test passes if we set GRPC_DNS_RESOLVER=native.
[ RUN      ] CFStreamTest.NetworkTransition
<IP_ADDRESS>      grpctest
dyld: lazy symbol binding failed: Symbol not found: _ares_library_init
  Referenced from: /Volumes/BuildData/tmpfs/tmp/bazel/a002d9727939acebf422134be2d181ab/execroot/com_github_grpc_grpc/bazel-out/darwin-fastbuild/bin/test/cpp/end2end/cfstream_test.runfiles/com_github_grpc_grpc/test/cpp/end2end/../../../_solib_darwin_x86_64//liblibgrpc_Uresolver_Udns_Uares.so
  Expected in: flat namespace
dyld: Symbol not found: _ares_library_init
  Referenced from: /Volumes/BuildData/tmpfs/tmp/bazel/a002d9727939acebf422134be2d181ab/execroot/com_github_grpc_grpc/bazel-out/darwin-fastbuild/bin/test/cpp/end2end/cfstream_test.runfiles/com_github_grpc_grpc/test/cpp/end2end/../../../_solib_darwin_x86_64//liblibgrpc_Uresolver_Udns_Uares.so
  Expected in: flat namespace
*******************************
Caught signal SIGABRT
  no backtrace
Abort trap: 6

https://source.cloud.google.com/results/invocations/f5897734-9b6a-4ef9-9466-a7ab1f101749/targets/grpc%2Fcore%2Fmaster%2Fmacos%2Fgrpc_cfstream/log

CC @apolcyn

@rmstar, this is probably not related to CFStream itself but something to do with Bazel and cares symbols. Please confirm if this works without CFStream enabled.

@srini100 yes, this issue seems to be unrelated to CFStream itself. The test fails even when CFStream is disabled.

This also breaks for the https://github.com/googleapis/google-cloud-cpp project. I changed our project to use gRPC v1.19.0, then our tests on Mac OS X started failing with the same error as above. Our full error log is here:  https://source.cloud.google.com/results/invocations/9e470476-78aa-4bd2-9de9-8306722ccc82/targets/cloud-cpp%2Fgithub%2Fmacos%2Fpresubmit/log
Here's a snippet of the error:
[ RUN      ] NoexTableAsyncReadRowsTest.Simple
dyld: lazy symbol binding failed: Symbol not found: _ares_library_init
  Referenced from: /Volumes/BuildData/tmpfs/tmp/bazel/958e32d54e02d3b435828e68d1d5184e/sandbox/darwin-sandbox/2133/execroot/com_github_googleapis_google_cloud_cpp/bazel-out/darwin-fastbuild/bin/google/cloud/bigtable/bigtable_client_internal_table_async_row_reader_test.runfiles/com_github_googleapis_google_cloud_cpp/google/cloud/bigtable/../../../_solib_darwin_x86_64//libexternal_Scom_Ugithub_Ugrpc_Ugrpc_Slibgrpc_Uresolver_Udns_Uares.so
  Expected in: flat namespace
dyld: Symbol not found: _ares_library_init
  Referenced from: /Volumes/BuildData/tmpfs/tmp/bazel/958e32d54e02d3b435828e68d1d5184e/sandbox/darwin-sandbox/2133/execroot/com_github_googleapis_google_cloud_cpp/bazel-out/darwin-fastbuild/bin/google/cloud/bigtable/bigtable_client_internal_table_async_row_reader_test.runfiles/com_github_googleapis_google_cloud_cpp/google/cloud/bigtable/../../../_solib_darwin_x86_64//libexternal_Scom_Ugithub_Ugrpc_Ugrpc_Slibgrpc_Uresolver_Udns_Uares.so
  Expected in: flat namespace
Abort trap: 6
================================================================================

@devjgm, sorry we missed this issue in 1.19.0. Are you ok with pinning to 1.17.2 for now? I would like to avoid a patch release just for this issue.

Is there a way to test on master branch? The fix (https://github.com/grpc/grpc/pull/18201) is now on master branch

The problem is that I can't currently build grpc with the current bazel due to an old protobuf dependency. Specifically, I need a version of grpc with https://github.com/grpc/grpc/commit/7a814e2597fbda08e06034717324d8e5b423b93a#diff-5952172e3b803ed640371cda4cddf13d I believe 1.19.0 has this, which is why I need to upgrade.
Regarding avoiding a patch release: isn't the 1.19.0 build broken on some OS X builds? If so, shouldn't that be fixed? Thanks.

@devjgm, is there a way for you to confirm the fix in #18201. We'll target to release a patch next week. This affects bazel but not make builds on MacOS.

Sure. I tried building against grpc @ commit 046e3e4ab5cdb867bda7a5c40fd9b0ac84ad0ff8. The tarball bazel fetched was https://github.com/grpc/grpc/archive/046e3e4ab5cdb867bda7a5c40fd9b0ac84ad0ff8.tar.gz
When I use this grpc snapshot, I get the following error:
DEBUG: Rule 'com_google_absl' modified arguments {"sha256": "5fe2a3a8f8378e81d4d3db6541f48030e04233ccd2d6c7e9d981ed577b314ae8"}
ERROR: /home/jgm/github/devjgm/google-cloud-cpp/google/cloud/bigtable/examples/opencensus/BUILD:19:1: error loading package '@io_opencensus_cpp//opencensus/exporters/trace/stdout': in /home/jgm/.cache/bazel/_bazel_jgm/bd671f688e1f702fab062681330ab451/external/io_opencensus_cpp/opencensus/copts.bzl: Unable to load file '@com_google_absl//absl:copts.bzl': file doesn't exist and referenced by '//google/cloud/bigtable/examples/opencensus:bigtable_opencensus'
ERROR: Analysis of target '//google/cloud/bigtable/examples/opencensus:bigtable_opencensus' failed; build aborted: error loading package '@io_opencensus_cpp//opencensus/exporters/trace/stdout': in /home/jgm/.cache/bazel/_bazel_jgm/bd671f688e1f702fab062681330ab451/external/io_opencensus_cpp/opencensus/copts.bzl: Unable to load file '@com_google_absl//absl:copts.bzl': file doesn't exist
INFO: Elapsed time: 0.286s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (0 packages loaded, 0 targets configured)
    currently loading: @io_opencensus_cpp//opencensus/exporters/trace/stdout

So it looks like I'm picking up so other commits between the 1.19.0 release and the commit from #18201 that is changing something that may be causing that breakage.
Pointers?

@devjgm the error you pointed out seems to be related to a package dependency on abseil. I don't think it's caused by the c-ares linking issue.
I noticed that commit 046e3e4 and v1.19.0 pull in different abseil-cpp tarballs. Not sure if that's causing the breakage.
v.19.0

    if "com_google_absl" not in native.existing_rules():
        http_archive(
            name = "com_google_absl",
            strip_prefix = "abseil-cpp-cd95e71df6eaf8f2a282b1da556c2cf1c9b09207",
            url = "https://github.com/abseil/abseil-cpp/archive/cd95e71df6eaf8f2a282b1da556c2cf1c9b09207.tar.gz",
        )

commit 046e3e4

    if "com_google_absl" not in native.existing_rules():
        http_archive(
            name = "com_google_absl",
            strip_prefix = "abseil-cpp-308ce31528a7edfa39f5f6d36142278a0ae1bf45",
            url = "https://github.com/abseil/abseil-cpp/archive/308ce31528a7edfa39f5f6d36142278a0ae1bf45.tar.gz",
        )

Reopening since there is active discussion going on.

abseil moved the location of configure_copts.bzl to copts.bzl. The version of io_opencensus_cpp that google-cloud-cpp loads is probably trying to find the old location. I will open a PR for google-cloud-cpp updating the dependency and see if it fixes the issue.

@devjgm, @remyabel, are you able to verify the original fix in your local build? We want to do an RC for 1.19.1 patch this week.

Yes the original fix works. Thanks @srini100.

There is some delay in rolling this patch out. Python bazel on macos seems to have similar issue. See https://github.com/grpc/grpc/issues/18267. Would like to get that resolved too.

Note the error in #18267 is Symbol not found: __Z31grpc_set_default_iomgr_platformv
That might be a similar issue to the one fixed by #18201, but it's definitely unrelated to c-ares

@devjgm, @remyabel, I have tagged the release v1.19.1. Do you need any pkgs to be released or source is sufficient?


Shelly i3 has no components to add.

First,
many thanks! great and appreciated project
one of my Shelly's is i3, use to activate broadlink commands to my ceiling fan.
unfortunately i cant manage to add it.
Matterbridge v1.4.1, from HA, i3 is connected to HA with unicast setting.
info - [09:38:49.694] [Gaya Shelly-i3 fans]: Shelly added Gaya Shelly-i3 fans gen 1 device id shellyix3-E8DB84D6FE11 host <IP_ADDRESS>
info - [09:38:49.694] [Gaya Shelly-i3 fans]: - mac: E8DB84D6FE11
info - [09:38:49.694] [Gaya Shelly-i3 fans]: - model: SHIX3-1
info - [09:38:49.694] [Gaya Shelly-i3 fans]: - firmware: v1.14.0-gcb84623
info - [09:38:49.694] [Gaya Shelly-i3 fans]: - components:
info - [09:38:49.694] [Gaya Shelly-i3 fans]: - wifi_ap (WiFi)
info - [09:38:49.695] [Gaya Shelly-i3 fans]: - wifi_sta (WiFi)
info - [09:38:49.695] [Gaya Shelly-i3 fans]: - wifi_sta1 (WiFi)
info - [09:38:49.695] [Gaya Shelly-i3 fans]: - mqtt (MQTT)
info - [09:38:49.695] [Gaya Shelly-i3 fans]: - coiot (CoIoT)
info - [09:38:49.695] [Gaya Shelly-i3 fans]: - sntp (Sntp)
info - [09:38:49.695] [Gaya Shelly-i3 fans]: - cloud (Cloud)
warn - [09:38:49.702] [Matterbridge shelly plugin]: Device gen 1 device shellyix3-E8DB84D6FE11 host <IP_ADDRESS> has no components to add.
info - [09:39:49.553] [ShellyMdnsDiscover]: Sent mDNS query for shelly devices.
info - [09:40:49.555] [ShellyMdnsDiscover]: Sent mDNS query for shelly devices.
info - [09:41:49.555] [ShellyMdnsDiscover]: Sent mDNS query for shelly devices.

Hi,
thanks for your appreciation.
We don't have this device.
Can you send me please the files you find in HOME/Matterbridge/matterbridge-shelly: they are all json files.
I can add it if I have that files.

matterbridge-shelly.zip
matterbridge-shelly.config.json
from Homeassistant addon_configs\

Hi,
thanks but I need Matterbridge\matterbridge-shelly not .matterbridge\matterbridge-shelly

those are the only ones i see in \addon_configs\a1b84aa7_matterbridge\ related to matterbridge-shelly
the zip is the entire matterbridge-shelly folder inside
is there another place?

Hi,
I just want to follow up.
I didn't forget this.
The next release should solve this.
I added a configuration for Input events...

With the new version the i3 module is added in matterbridge.
in HomeKit it expose as 1 switch with 3 buttons.
applying the actions on each button doesnt work, not getting any visual feedback also.
in other room i have same module with mongoose FW, added to HK as 3 seperate switches instead of buttons.
maybe this is necessary?

Hi,
so it shows up. Good!
The 3 button are correct cause there were 3 Inputs. On HomeKit do you see them like a momentary button with the usual single, double long press actions?
Can you enable the debug in the plugin config and send me a copy paste of the entire log (hope you don't have hundreds device).

just to update, it was an issue with the Home assistant matterbridge addon
once installed on debian lxc all worked perfectly!
many thanks!!!!

Hi,
I'm glad you sorted it out.
That plugin is not working correctly and the author doesn't want to collaborate with me so... almost all issues come from there.
My best.


[✨]  Added info app / "canResize" option for WM

[✨]  Changes:

Info App Added
"canResize" option (Controls if a window can be resized or not)

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


No hidden input type

Laravel Version: 5.4.12
Voyager Version: 0.11.2
PHP Version: 5.6.28
Database Driver & Version: MySQL  5.7.16

Description:
In some of the demos and in the official documentation hidden field type is showed and mentioned. There is no option hidden when selecting Input Type in the latest version. Was this feature removed?
Steps To Reproduce:
Fresh install of Laravel and Voyager

The whole database section was rewrote in v0.11. And therefor some things might have been forgotten, we will however get this back sooner or later.

/ping @abdgad, we should maybe add a form field for this.

I think @Codebreaker101 is referring to Hidden Input type for BREAD?

Ohh, I see.

That is correct @abdgad. I got it working for the most part. I will make a PR when ready.
Also, I got an idea for custom input types that would be defined in the voyager config. It would make it a bit easier to customize the apprentice using partial views. Has this been considered previously?

Pull request: https://github.com/the-control-group/voyager/pull/866

@marktopper This one is resolved.

Thanks @sikhub.
// Closed


With Two Factor enabled,  need ability to determine if the user is only password authenticated

Is your feature request related to a problem? Please describe.
The Authorize attribute is either on or off but we would like the ability to control access to endpoints based on whether the user is password authenticated only, or has also verified their second factor.
Describe the solution you'd like
There are several possibilities.  One could be a separate Authorize attribute or some parameter that could be passed to the Authorize attribute.  If that isn't possible, at least a simple function in the SignInManager that would let us know how far the user has gotten in the authentication process.

This is what the AuthenticationType property (and ctor arg) is for on ClaimsIdentity:
https://referencesource.microsoft.com/#mscorlib/system/security/claims/ClaimsIdentity.cs,451

I may not have explained the scenario very well.  The scenario I am referring to is when a user has 2fa enabled and comes to the site to login.  We first call PasswordSignInAsync.  At this point, I would like to be able to know that this user has "Password Signed In".  Unfortunately, if I look at the ClaimsIdentity or the ClaimPrinciple, nothing has been set yet.  The auth provider must know from that the state we are in, otherwise the next step of calling TwoFactorAuthenticatorSignInAsync would not work correctly.  I would like to have some way of knowing  that a user with 2fa enabled has password signed in, but not yet verified their authenticator code.

@HaoK is there a way to do this?

Just a follow up and explain what I am trying to accomplish.  We would like to restrict the endpoints for verifying the authenticator code, using a recovery code, etc to users that have signed in with their password but not yet finished the 2FA process.  We also have some endpoints during the registration process that we would also like to restrict to users that have completed the password sign in process.  The reference implementation leaves those endpoints as allowing anonymous and we would like to prevent that.

Hey @nauticalcoder
Behind the scenes, Identity uses several cookies to differentiate users that:

signed in with password only;
signed in with password but need to complete MFA;
signed in with password, completed MFA and checked the "Remember me" checkbox.

Each of those cookies is registered in the authentication system with different scheme names. See the IdentityConstants class.
If you want to restrict endpoints for people who signed in with passwords but still need to complete MFA, you can decorate the controllers and/or actions with an [Authorize(AuthenticationSchemes = IdentityConstants.TwoFactorUserIdScheme)] attribute.

Dupe of https://github.com/aspnet/AspNetCore/issues/5783 where we will get the amr claim on a user


ServiceDiscoveryManager LookupCache configured with single threaded ServiceEventExecutorService can report less than the required service added events.

Occurs when running the following test:
org.apache.river.test.impl.servicediscovery.event.LookupTaskServiceIdMapRace

Work around:
Use at least two threads when configuring ServiceDiscoveryManager's ServiceEventExecutorService.

Example test failure:
The LookupCache should notify that 6000 services are added.
In one instance the LookupCache only notified that 5999 services were added.
RegisterListenerTask, which is normally responsible for approximately 4500 service added notifications, while HandleServiceEventTask is usually responsible for the remaining 1500 service added notifications.
RegisterListenerTask, after registering to receive events calls lookup(ProxyReg) which populates the LookupCache and notifies of services added.  The lookup method eventually calls newOldService, which in turn calls filterMaybeDiscard.
When HandleServiceEventTask is run, for each contiguous ServiceEvent received from the lookup service (no non contiguous events occur in a single threaded executor), it too calls newOldService, which in turn either calls filterMaybeDiscard or itemMatchMatchChange.
In the test failure above, newOldService was called 6007 times, while filterMaybeDiscard was called 5999 times and itemMatchMatchChange was called 6 times. filterMaybeDiscard + itemMatchMatchChange calls should = the total # of newOldService calls. In this case RegisterListenerTask was responsible for reporting 4507 service added events and HandleServiceEventTask responsible for 1492.

lookup cache - failure with concurrent logger - 1 SDM with wrong number of events.txt

lookup cache - with concurrent logger - what passing looks like.txt

ServiceDiscoveryManager and LookupCacheImpl have been modified to use a single threaded ExecutorService for logging, otherwise logging interferes with the concurrency of LookupCacheImpl and the test failures cannot be observed.

This test failure can be observed in occasionally, in 2% of test runs with a single threaded ServiceEventExecutorService.

This was caused by a ServiceEvent notification being received as soon as a new service was registered with the ServiceRegistrar, but prior to the service's join state receiving the ServiceRegistration, thus the ServiceIDAccessor didn't yet know the ServiceID.  Recommend changing the impl to use the ServiceEvent's reported ServiceID instead of using the ServiceIDAccessor api of the bootstrap proxy.

NullPointerException that caused the test failures.
 [java] Oct 31, 2016 9:15:03 AM net.jini.lookup.ServiceDiscoveryManager lambda$log$0
 [java] FINE: Runtime exception thrown in newOldService call
 [java] java.lang.NullPointerException
 [java] 	at java.util.concurrent.ConcurrentHashMap.get(ConcurrentHashMap.java:936)
 [java] 	at net.jini.lookup.LookupCacheImpl.newOldService(LookupCacheImpl.java:1313)
 [java] 	at net.jini.lookup.LookupCacheImpl.notifyServiceMap(LookupCacheImpl.java:1188)
 [java] 	at net.jini.lookup.LookupCacheImpl.access$1700(LookupCacheImpl.java:93)
 [java] 	at net.jini.lookup.LookupCacheImpl$HandleServiceEventTask.run(LookupCacheImpl.java:1084)
 [java] 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
 [java] 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
 [java] 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 [java] 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 [java] 	at java.lang.Thread.run(Thread.java:745)
 [java]


Synced with raylib latest, and fixed build

Fixes: #40 #39 #37
It doesn't however fix the parsing, which in the end might cause crashes if raylib is changed significantly.

now it does

are you sure that #40 is fixed with that? because it seems that I still get it

are you sure that #40 is fixed with that? because it seems that I still get it

just do:
raylib.addTo(b, exe, target.query, optimize, .{});

are you sure that #40 is fixed with that? because it seems that I still get it

just do:
raylib.addTo(b, exe, target.query, optimize, .{});

I guess this PR should also change the README to avoid confusions then.
Btw, I keep seeing the same error as #40 even when using your fork, zig 0.11.0 and this particular snippet. Maybe I'm doing something wrong.

are you sure that #40 is fixed with that? because it seems that I still get it

just do:
raylib.addTo(b, exe, target.query, optimize, .{});

I guess this PR should also change the README to avoid confusions then.
Btw, I keep seeing the same error as #40 even when using your fork, zig 0.11.0 and this particular snippet. Maybe I'm doing something wrong.

Changing:

std.Target.Query -> std.Build.ResolvedTarget
b.resolveTargetQuery(target), -> target,

fixes for me (I'm using latest zig)
It seems like even the official raylib repo is having to use some workarounds to deal with these API breakages (see the anytype).

When using LoadTexture getting:
INFO: IMAGE: Data loaded successfully (96x96 | R8G8B8A8 | 1 mipmaps)
Segmentation fault at address 0x0
???:?:?: 0x0 in ??? (???)

Tested with latest zig 0.12.0, working as expected

Tried it and i still get:
file paths added with 'addCSourceFiles' must be relative.
// game/ext/raylib/raylib/src/build.zig:51
    addCSourceFilesVersioned(raylib, &.{
        srcdir ++ "/rcore.c",
        srcdir ++ "/utils.c",
    }, raylib_flags_arr.items);

Thank you @ProIcons so much for the PR. I finally able to build with Zig 0.12!
Here's my process:

Clone the fork

cd $YOUR_SRC_FOLDER
git submodule add https://github.com/ryupold/raylib.zig raylib
git submodule update --init --recursive

zig init
Edit main.zig to:

const std = @import("std");
const raylib = @import("raylib");

pub fn main() !void {
    raylib.SetConfigFlags(raylib.ConfigFlags{ .FLAG_WINDOW_RESIZABLE = true });
    raylib.InitWindow(800, 800, "hello world!");
    raylib.SetTargetFPS(60);

    defer raylib.CloseWindow();

    while (!raylib.WindowShouldClose()) {
        raylib.BeginDrawing();
        defer raylib.EndDrawing();

        raylib.ClearBackground(raylib.BLACK);
        raylib.DrawFPS(10, 10);

        raylib.DrawText("hello world!", 100, 100, 20, raylib.YELLOW);
    }
}

Edit build.zig to:
const raylib = @import("raylib/build.zig");
const std = @import("std");

pub fn build(b: *std.Build) void {
    const target = b.standardTargetOptions(.{});
    const optimize = b.standardOptimizeOption(.{});
    const lib = b.addStaticLibrary(.{
        .name = "rayray",
        .root_source_file = b.path("src/root.zig"),
        .target = target,
        .optimize = optimize,
    });

    b.installArtifact(lib);

    const exe = b.addExecutable(.{
        .name = "rayray",
        .root_source_file = b.path("src/main.zig"),
        .target = target,
        .optimize = optimize,
    });

    raylib.addTo(b, exe, target.query, optimize, .{});

    b.installArtifact(exe);

    const run_cmd = b.addRunArtifact(exe);

    run_cmd.step.dependOn(b.getInstallStep());

    if (b.args) |args| {
        run_cmd.addArgs(args);
    }

    const run_step = b.step("run", "Run the app");
    run_step.dependOn(&run_cmd.step);

    const lib_unit_tests = b.addTest(.{
        .root_source_file = b.path("src/root.zig"),
        .target = target,
        .optimize = optimize,
    });

    const run_lib_unit_tests = b.addRunArtifact(lib_unit_tests);

    const exe_unit_tests = b.addTest(.{
        .root_source_file = b.path("src/main.zig"),
        .target = target,
        .optimize = optimize,
    });

    const run_exe_unit_tests = b.addRunArtifact(exe_unit_tests);

    const test_step = b.step("test", "Run unit tests");
    test_step.dependOn(&run_lib_unit_tests.step);
    test_step.dependOn(&run_exe_unit_tests.step);
}

zig build run
Profit.

I'm on Arch Linux, Zig 0.12.


Text component doesn't re-render on value change

Description
Using a translate value (i.e. i18n) doesn't update the text component.
The Skia component is rendered before the translate value is retrieved, so the render box is empty.
Right now to make it work is by using x or y with useDerivedValue and putting the t(namespace) function in the dependency list.
const x = useDerivedValue(() => preX, [i18n.t('today')])
Version
0.1.241
Steps to reproduce
const preX = useSharedValue(0)
const x = useDerivedValue(() => preX.value, [t('today')])

...
<Text x={x.value y={0} text={t('today')} color='white' font={font} />

Snack, code example, screenshot, or link to a repository
Without useDerivedValue

Wit useDerivedValue

x.value won't rerender but x={x} will.

Could you share a small reproducible example?

I will close it for now but let's reopen it as soon as we have an example. Also we can add it to the example app at https://github.com/Shopify/react-native-skia/tree/main/example if there is an issue to be test there.


no_std

Is there a demand for no_std feature?

I'd find that useful!

I would also find this useful. Happy to put some of my time towards it as well, but I could use some direction.

If effort is put into no_std support, please make sure no_alloc and heapless is a part of that solution :)

Are there any Rust protobufs that are heapless/noalloc? Basically, the nanopb equivalent?
I'm investigating just embedding nanopb into my embedded app at this point.

I believe tokio/prost  supports nostd

Yep, they do support no_std. I was testing it out the other day.
They do require alloc though.
My (hopefully temporary) solution is to create nanopb bindings using bindgen and so far, so good 🤷🏽
A first party, Rust-native, heapless would be much nicer though.


docs: Update produce/mdx

produce function operates on baseState and produces nextState. Everywhere in this docs original state called baseState, but in the first snippet it's called currentState. I'm renaming it for consistency.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.553%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
786

Relevant Lines:
794

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.553%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
786

Relevant Lines:
794

💛  - Coveralls


E117: Unknown function: plug#begin

I recently installed vim-plug using the following settings
mkdir -p ~/.vim/autoload
curl -fLo ~/.vim/autoload/plug.vim --create-dirs
https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
and my vimrc file has following content
call plug#begin('~/.vim/plugged')
" Make sure you use single quotes
Plug 'junegunn/seoul256.vim'
Plug 'junegunn/vim-easy-align'
" Group dependencies, vim-snippets depends on ultisnips
Plug 'SirVer/ultisnips' | Plug 'honza/vim-snippets'
" On-demand loading
Plug 'scrooloose/nerdtree', { 'on':  'NERDTreeToggle' }
Plug 'tpope/vim-fireplace', { 'for': 'clojure' }
" Using git URL
Plug 'https://github.com/junegunn/vim-github-dashboard.git'
" Plugin options
Plug 'nsf/gocode', { 'tag': 'v.20150303', 'rtp': 'vim' }
" Plugin outside ~/.vim/plugged with post-update hook
Plug 'junegunn/fzf', { 'dir': '~/.fzf', 'do': 'yes | ./install' }
" Unmanaged plugin (manually installed and updated)
Plug '~/my-prototype-plugin'
call plug#end()
i am getting this error when i try to restart my vim
Error detected while processing C:\Users\hp_vimrc:
line   59:
E117: Unknown function: plug#begin
line   62:
E492: Not an editor command: Plug 'junegunn/seoul256.vim'
line   63:
E492: Not an editor command: Plug 'junegunn/vim-easy-alig
n'
line   66:
E492: Not an editor command: Plug 'SirVer/ultisnips' | Plug
'honza/vim-snippets'
line   69:
E492: Not an editor command: Plug 'scrooloose/nerdtree', {
'on':  'NERDTreeToggle' }
line   70:
E492: Not an editor command: Plug 'tpope/vim-fireplace', {
'for': 'clojure' }
line   73:
E492: Not an editor command: Plug 'https://github.com/june
gunn/vim-github-dashboard.git'
line   76:
E492: Not an editor command: Plug 'nsf/gocode', { 'tag':
'v.20150303', 'rtp': 'vim' }
line   79:
E492: Not an editor command: Plug 'junegunn/fzf', { 'dir':
'~/.fzf', 'do': 'yes | ./install' }
line   82:
E492: Not an editor command: Plug '~/my-prototype-plugin
'
line   84:
E117: Unknown function: plug#end
Please tell me what is the solution??? how can i make it work?

Looks like you're on windows, then you'll have to download plug.vim inside ~/vimfiles/autoload. Also you might want to pass ~/vimfiles/plugged to plug#begin().
And please note that all the Plug commands you copied from the readme page are just examples and you don't need them.

wow amazing i rename .vim folder to vimfiles and now i just got 1 error that the error
git executable not found. vim-plug requires git.
I installed git but still getting this error..

Plug is working i just add path of git in my environment variables of windows 7... thanks for your reply but can you tell me why we can't use vim with .vim instead of vimfiles....?

See :help vimfiles for the details.

@junegunn  I have same case, windows xp , rename .vim to vimfiles. It been ok.

I had the same problem, error E117. I solved changing permissions to .vim/autoload. I did
sudo chmod 777 autoload
No more errors on unknown function plug#begin  and plug#end


Added new template by bh6erk

Hi there!
I have added a new email template to the project with some material style.
Cheers!

@vinitshahdeo thank you for your feedback, I have selected a new user avatar image and the source is now an URL.

@bh6erk Awesome:) 👍

@bh6erk You may also look into a few more issues here!


TypeError: Cannot read properties of undefined (reading 'percentMovementChangeForTokenAtPoint')

I'm getting this error when I move any token with this module enabled. Someone know anything about this?
TypeError: Cannot read properties of undefined (reading 'percentMovementChangeForTokenAtPoint')
at TerrainMovePenaltyCenterGrid.moveMultiplier (MovePenalty.js:1007:25)
at MovePenalty.js:1060:48
at Array.reduce ()
at MovePenalty.js:1060:22
at MoveDistanceGridded.measure (MoveDistance.js:161:21)
at MoveDistance.measure (MoveDistance.js:29:15)
at _measureSegment (Ruler.js:362:28)
at Ruler._computeSegmentDistances (Ruler.js:343:23)
at Ruler._computeDistance (Ruler.js:284:28)
at 🎁CONFIG.Canvas.rulerClass.prototype._computeDistance#0 (libWrapper-wrapper.js:187:52)
at Ruler.measure (foundry.js:35790:10)
at 🎁call_wrapped [as call_wrapped] (libWrapper-wrapper.js:507:22)
at 🎁CONFIG.Canvas.rulerClass.prototype.measure#aedifs-tactical-grid (settings.js:515:22)
at 🎁CONFIG.Canvas.rulerClass.prototype.measure#0 (libWrapper-wrapper.js:187:52)
at Ruler._onMouseMove (foundry.js:36402:10)
at TokenPF2e._onDragLeftMove (Token.js:54:33)
at 🎁CONFIG.Token.objectClass.prototype._onDragLeftMove#0 (libWrapper-wrapper.js:187:52)
at MouseInteractionManager.callback (foundry.js:30532:17)
at #handleDragMove (foundry.js:30911:26)
at #handlePointerMove (foundry.js:30876:64)
at vh.notifyListeners (EventBoundary.ts:1464:33)
at vh.notifyTarget (EventBoundary.ts:658:14)
at vh.propagate (EventBoundary.ts:310:18)
at vh.dispatchEvent (EventBoundary.ts:210:14)
at vh.mapPointerMove (EventBoundary.ts:815:64)
at vh.mapEvent (EventBoundary.ts:231:28)
at ra.onPointerMove (EventSystem.ts:396:31)

I had this issue while Terrain Mapper was enabled.  The two don't seem to work together just yet.

Thanks. Should be addressed in Terrain Mapper v0.3.2 along with Elevation Ruler v0.9.5.


import: Fix has_link and has_attachment mapping for slack and gitter import.

In the conversion of data in slack and gitter imports, the Message objects is being built in import_util. There, the current mapping of has_link and has_attachment is incorrect, which has to fixed.

@hackerkid can you test whether we end up setting these attributes properly after data import?  I think #12912 might have automatically fixed this by having those attributes be set during message rendering, but it's possible we didn't hook up the plumbing properly.


AsDateTimeOffset return wrong offset for America/mexico_city time zone

I get the nextOccurent which is of type IDateTime by following code:
var occurrences = calendar.GetOccurrences(searchStartTime, searchEndTime);
var nextOccurence = occurrences.First().Period.StartTime;

It has value "4/30/2023 9:00:00 PM america/mexico_city", but AsDateTimeOffset return wrong offset (It return -07:00, but it should be -06:00)
{4/30/2023 9:00:00 PM america/mexico_city}
    AsDateTimeOffset: {4/30/2023 9:00:00 PM -07:00}
    AsSystemLocal: {4/30/2023 9:00:00 PM}
    AsUtc: {5/1/2023 4:00:00 AM}
    AssociatedObject: Component: "VEVENT"
    Calendar: Component: "VCALENDAR"
    Date: {4/30/2023 12:00:00 AM}
    Day: 30
    DayOfWeek: Sunday
    DayOfYear: 120
    Encoding: null
    HasDate: true
    HasTime: true
    Hour: 21
    IsUtc: false
    Language: null
    Millisecond: 0
    Minute: 0
    Month: 4
    Parameters: {Ical.Net.Proxies.ParameterCollectionProxy}
    Second: 0
    Ticks:<PHONE_NUMBER>00000000
    TimeOfDay: {21:00:00}
    TimeZoneName: "america/mexico_city"
    TzId: "america/mexico_city"
    Value: {4/30/2023 9:00:00 PM}
    Year: 2023
    _AssociatedObject: Component: "VEVENT"

Not sure if it due to mexico_city no longer use DST starting from this year

Please double-check the new version merged with #595


Loss is Nan

Hi,
I'm trying to reproduce your training result for CCPs dataset. I tried setting up the batch size for DFCAN to 4 and batch size for DFGAN to 2 but during training at around 9000 epochs or so the loss is Nan. I'm just wondering what parameters do you use to train CCPs dataset and how can I avoid getting Nan for my loss? I tried to google this and most people said to check if the preprocessing dataset is corrupted. I then checked this but did not see any corrupted data in my dataset.
Thank you in advance.

Hi,
you can try to use a smaller initial learning rate, such as 1e-5.

Hi,
The mini batch iteration was select empirically but not by calculation to ensure that the models were trained properly.

How do you calculate the minibatch in the plot you showed in the supplementary materials for CCPs dataset? As far as I know the code you provided only give epochs in this case it’s iterations

The 'epoch' in the codes actually should be 'minibatch iteration'. I have modified this error just now.
This 'minibatch iteration' corresponds to the plot showed in the supplementary materials.
You can change the argument 'iteration' to apply this minibatch to the training.

Thank you for the clarification. I also run the preprocessing using my own dataset. After training the model with my dataset the output of the image appears to be stacked in the corner of the image. It looks like there are multiple borders stacked in the corner of the image. Do you know what this could possibly be? have you seen this before?
Thank you.

I haven't seen this before. Can you show me some output images here?

for sure. I've attached the images below along with the ground truth image and low-resolution image.

I didn't notice artifacts like these in my experiments, but I think maybe it is caused by the usage of the pixel shuffle layer. Maybe you can try replacing pixel shuffle layer with upsampling layer to fix it.

In supplementary Figure 13 e you have Training loss , mini batch iteration and validation NRMSE plotted for DFCAN. For the training loss is it calculated using MSE + lambda x (1 - SSIM) ?

Yes, the training loss shown in Supp. Fig. 13e is calculated using MSE + 0.1 * (1-SSIM).

for sure. I've attached the images below along with the ground truth image and low-resolution image.

About this problem, I wonder if you use the original low resolution images as network inputs or use the upsampling images (e.g. by bicubic interpolation) as sampling.

I believe I use the original low-resolution images as network input.

Thank you so much for taking the time to respond to me.

I believe I use the original low-resolution images as network input.

I wonder what's the upscaling factor in your task.
And the low-resolution image you showed here seems a bicubic-interpolated form of the original LR image. I don't know whether this was caused by the image compression on the website or other reasons.

The upscaling factor is 2. As for my low-resolution image, I have shown below how I acquired the image.

Which interpolation methods did you use to generate your LR images? Nearest?

No interpolation was used to generate the LR images. I only use cropping method to generate the LR images and use the provided matlab code to generate the training dataset.

Hi there, I just wanted to double check in your paper CCPs dataset was trained up to 500000 iterations for DFCAN?

Hi, actually 250,000~30,0000 iterations were enough. Then the model with the least validation loss was used for evaluation.


Register-PSRepository invalid Web Uri

Steps to reproduce
Register-PSRepository -Name internalRepo -SourceLocation= https://adepot:8625/nuget/PSGet

Expected behavior
repo registered

Actual behavior
ScriptStackTrace:
at ThrowError, C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\2.2.5\PSModule.psm1: line 7115
at Resolve-Location, C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\2.2.5\PSModule.psm1: line 6123
at Register-PSRepository<Process>, C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\2.2.5\PSModule.psm1: line 11481
at <ScriptBlock>, <No file>: line 146

System.ArgumentException: The specified Uri 'https://adepot:8625/nuget/PSGet/' for parameter 'SourceLocation' is an invalid Web Uri. Please ensure that it meets the Web Uri requirements.
   at System.Management.Automation.MshCommandRuntime.ThrowTerminatingError(ErrorRecord errorRecord)
fatal: [stnoy090.redacted.local]: FAILED! => {
    "changed": false,
    "msg": "Unhandled exception while executing module: The specified Uri 'https://adepot:8625/nuget/PSGet/' for parameter 'SourceLocation' is an invalid Web Uri. Please ensure that it meets the Web Uri requirements."
}

This command works fine:
 Invoke-WebRequest -Uri "https://adepot:8625/nuget/PSGet" -Verbose -Credential $(Get-Credential)

StatusCode        : 200
StatusDescription : OK
Content           : <?xml version="1.0" encoding="utf-8"?><service
                    xmlns="http://www.w3.org/2007/app"><workspace><title
                    xmlns="http://www.w3.org/2005/Atom">Default</title><collection href="Packages"><title
                    xmlns="http://...
RawContent        : HTTP/1.1 200 OK
                    X-ProGet-Version: <IP_ADDRESS>
                    Persistent-Auth: true
                    Content-Length: 273
                    Cache-Control: no-cache, no-store, must-revalidate
                    Content-Type: text/xml
                    Date: Wed, 11 Nov 2020 21:11:42 GMT...
Forms             : {}
Headers           : {[X-ProGet-Version, <IP_ADDRESS>], [Persistent-Auth, true], [Content-Length, 273], [Cache-Control,
                    no-cache, no-store, must-revalidate]...}
Images            : {}
InputFields       : {}
Links             : {}
ParsedHtml        : System.__ComObject
RawContentLength  : 273

Environment data

> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.14393.3866
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.3866
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

```powershell
> Get-PackageProvider -ListAvailable
Name                     Version          DynamicOptions
----                     -------          --------------
msi                      <IP_ADDRESS>          AdditionalArguments
msu                      <IP_ADDRESS>
nuget                    <IP_ADDRESS>
NuGet                    <IP_ADDRESS>          Destination, ExcludeVersion, Scope, SkipDependencies, Headers, FilterOnTag...
PowerShellGet            <IP_ADDRESS>          PackageManagementProvider, Type, Scope, AllowClobber, SkipPublisherCheck, ...
PowerShellGet            <IP_ADDRESS>
Programs                 <IP_ADDRESS>          IncludeWindowsInstaller, IncludeSystemComponent

And to give my personal feedback on powershellget, nuget and al.:  It's a complete failure.  First, we cannot register a repository with the default powershellget 1.0 that comes on a fresh OS install(windows 2016) So, we need to update poewrshellget, but our servers do not have internet access, so the smart, automated way, would be to register our internal proget depot and update from there, but we can't since it fails.  Great!  So let's copy it manually.  Oh, but first we need to install nuget offline.  Just do a search on how to install nuget offline, if you are lucky you will find the article that mentions you have to.. get it from an machine where it is installed and copy the folder manually!  Wow, a manual copy, GREAT!
This is a complete mess.  Trying to automate this for a new server installation is a nightmare.  And to end it all, even when you copy manually nuget, powershelget 2.2.5, packagemanagement 1.47, it STILL fails to register the internal repo. throw hands in air

Thanks @kinwolfqc we have been working on PowerShellGet 3.0 to solve many of the frustrating challenges with the current package management situation, it would be great if you could check that out and give us feedback to make sure we are meeting your requirements as we finish building the module: https://github.com/PowerShell/PowerShellGet


Update fake_thread.yml

Description
Better account for forwards and tags in the subject.
Associated hunts
New matching messages:

Hunt 1

going to combine with other related work into a single PR


Enhancement: Logging system

Currently, Orion's logs are mixed with application logs which leads to incomprehensions from users / developers.
I propose that we use which provides a good isolation as well as levels: https://atmospherejs.com/jag/pince.
I've used it on an app and it behaves properly with Orion separating my app logs from the one of Orion.

Logging is a big deal are your proposing core makes this a dependent?

Yep. Currently, there console.log everywhere. They mix with developper's log. Thus, they can't understand if stuff is going badly owing to them or Orion.

Do a PR

PR done #271
:smile:


[BUG] DST shift issue for expect_row_values_to_have_data_for_every_n_datepart

Is this a new bug in dbt-expectations?

[x] I believe this is a new bug in dbt-expectations
[x] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
The expect_row_values_to_have_data_for_every_n_datepart test when using date_part set to hour has test failures during the DST spring forward shifts, such as 2022-03-13T02:00:00. This isn't an actual hour for the America/New_York time zone. This hour is skipped as the time zone shifts, going from 2022-03-13T01:00:00-05:00 to 2022-03-13T03:00:00-04:00.
I suspect this is because the UTC offset isn't being used for timestamp_tz date columns.
Expected Behavior
This test shouldn't fail on DST shifts, as long as each hour when converted to UTC or a single offset is there.
Steps To Reproduce

Create a new model, test_model as:

select
  dateadd(hour, seq4(), '2022-01-01 05:00:00 +0000'::timestamp_tz) as timestamp_utc,
  convert_timezone('America/New_York', timestamp_utc) as timestamp_et
from
  table
    (generator(rowcount => 8760))

Add a test to this model using:

  - name: test_model
    tests:
      - dbt_expectations.expect_row_values_to_have_data_for_every_n_datepart:
          date_col: timestamp_et
          date_part: hour

Run and test the new model using dbt build -s test_model. The test should fail with 1 result. After inspecting, the row should be 2022-03-13T02:00:00.

Relevant log output
Environment
- OS: Windows 10
- Python: 3.9.13
- dbt: 1.3.1
- dbt-expectations: 0.8.2

Which database adapter are you using with dbt?
Snowflake: 1.3.0
Note: dbt-expectations currently does not support database adapters other than the ones listed below.

Postgres
Snowflake
BigQuery

Additional Context

Thanks for opening this issue. I have a feeling this belongs over in dbt-date since that's where the date math is actually being done, but try to I'll take a look next week. These sorts of things are typically hard to track down.
In the meantime, you could use row_condition to filter out the offending hour.


BC30002	Type 'BluetoothListener' is not defined.	Chat2DesktopVb

Hi,
I'm working on a vb.net PC program that hopefully will connect to a few Bluetooth modules and will exchange data back and forth with them. This program Chat2DesktopVb looks like a good start for my project. I am trying to compile this program in ..\32feet-master\Samples\BluetoothChat2\Chat2Desktop, but I'm getting a bunch of these BC30002 errors. I'm sure this is an easy question for you guys. Any help is greatly appreciated.
Thank you,
Robert

Well, I resolved this problem with the txt help files that are included in the package.


what is "Example1" supposed to mean?

What is Example1 supposed to mean? It wasn't very clear to me:
Perhaps the sample should be be small, and self contained, with clarifying details added?

See it under the "Attributes" section:

Beginning with C# 10, you can add attributes to a lambda expression and its parameters. The following example shows how to add attributes to a lambda expression:

rgds
Ben
(side note: Bill i am envious of your display photo. one day I hope to make it to the otherside of the world and stand on the very same bridge.)

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

ID: a6b8daf7-c244-5d1c-e43b-7fe654f378e1
Version Independent ID: 5142bc3b-2d71-b98e-190a-aa51f28f46e4
Content: Lambda expressions - C# reference
Content Source: docs/csharp/language-reference/operators/lambda-expressions.md
Product: dotnet-csharp
Technology: csharp-language-reference
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

That's a good point @benkoshy
I'll get this one updated.

This was addressed in a prior PR.


Bug in FewShotDataset module when accessing TextClassificationProcessor

Hi, there is a bug in this line. For the text classification datasets (mr, sst-5, subj, trec, cr, mpqa), the processor module requires the task name as input. Right now the above line throws error.

Hi thanks for the report. I remember that it has been fixed in a previous commit and I didn't encounter the problem using the latest one. Can you pull the latest commit and try again?

Oh sorry for that... It seems that I forgot to push the commit. It should work now.

Thanks.


Can not close Modal when click on overlay (Please update the note in readme)

Summary: Can not close Modal when click on overlay
└─┬<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>Steps to reproduce:

Remove shouldCloseOnOverlayClick prop --> Click on overlay --> nothing happen.
Add shouldCloseOnOverlayClick={true} --> Click on overlay --> nothing happen.
Add shouldCloseOnOverlayClick={false} --> Click on overlay --> nothing happen.

Expected behavior:

Remove shouldCloseOnOverlayClick prop --> Click on overlay --> close modal.
Add shouldCloseOnOverlayClick={true} --> Click on overlay --> close modal.
Add shouldCloseOnOverlayClick={false} --> Click on overlay --> nothing happen.

Additional notes:

I read source code, and found:

Then it checks ownerHandlesClose and it needs onRequestClose prop. Then I have to pass manual function to change state for open or close modal.
Please put the note to Readme please.

@SLyHuy Can you add this note to the readme?
It's required to pass a function to control the state of the modal.

@diasbruno Here is pull request https://github.com/reactjs/react-modal/pull/352

#352 closed this issue.


[PRODUCT]: SNODAS:  2004-2010

SNODAS: 2004-2010 raw grids and compute interpolated version
ftp://sidads.colorado.edu/DATASETS/NOAA/G02158/legacy

Backloading DAG for Airflow merged into USACE/airflow-config develop.  Geo-processor updated to handle SNODAS files from 2004 - 2010.  Testing to continue on develop-cumulus.corps.cloud.

Nice @jeffsuperglide! Good work!  Setting-up a Draft PR from develop --> stable pending confirmation of manual testing.  USACE/cumulus-api#330

@adamscarberry, can you put this through a few QA paces in develop?

[ ] Test results look ok in develop
[ ] Merge to stable

@brettpalmberg  Trying to acquire file with airflow, but they are either slow or failing.  Either source server is struggling or I'm being rate limited.  Will try again in the morning.

👍🏻 Sounds good. Thanks @adamscarberry.

@jeffsuperglide SNODAS SNOWTEMP 24hr has no data for the test period of Jan 2004.  Does this sound right?  Do we expect it to come and go?
cc @brettpalmberg

That sounds right. I think 2004 is touch and go for SNODAS data, but 2005 should be solid coverage if I remember correctly.

SNOW MELT has records as 0500 while SNOW MELT INTERPOLATED has records as 0600

I know exactly why that is.
interpolate.py line 178

@adamscarberry, @jeffsuperglide, 0600 is the correct timestamp for SNODAS (0500 is incorrect). Here is a note from the SNODAS documentation on NSIDC: https://nsidc.org/sites/default/files/nsidc_special_report_11.pdf

Example: us_ssmv11034tS__T0001TTNATS2003102305HP001.grz is modeled snow
water equivalent (ssmv11034) summed for all the layers of the snow model (tS__). It is
the output from just one hour (T0001), representing the time step starting at 2003-10-23
0500h (TS2003102305), is potentially generated for every hour of the day (H) and
represents the snow an hour after the start of the time step (P001). E.g. SWE at 0600h

We will want to check if this is impacting current realtime processing for SNODAS as well.

Not sure if it should have, but many of the interpolated products visually fill the missing holes.  In the image above, snow melt interpolated looks the same as original snomelt record.

Cold Content Sample output from develop:

Snow Depth sample output from develop

@jeffsuperglide  and @brettpalmberg, if you don't see any issues with the above sample from develop (Jan 2006), the snodas backload dag is in stable turned off (set to run for WY2004 at the moment...of course can be adjusted for whole period.)

https://github.com/USACE/cumulus-api/blob/ca44c1b3017e68de9fdbfadcdb56b7c2ece642b8/async_geoprocess/src/cumulus_geoproc/geoprocess/snodas/interpolate.py#L169-L174

Backload of 2004 - 2010 in progress...

Backload done.
Masked = 2004 - 16Feb2010
Unmasked = 17Feb2010 - present
SWE visual example:

complete


regression: missing number of positions in election list

OS 2.1 kindly displayed also the number of positions in the election list:

This helped a lot to keep the overview.
In OS 2.2b2 this information does no longer appear:

Please bring it back.

This was a design decision while we redesign all list tables.
The number of posts is mostly obviously (normally "1", or you can read it in title, e.g. "5 Beisitzer/innen").
If the posts is not reached the badge number is marked orange. If candidates >= posts the badge is grey. Sould be enough.
=> Won't fix.

If the posts is not reached the badge number is marked orange. If candidates >= posts the badge is grey.

But nobody in the audience knows that. Of course one can add the number of posts to the title. The OS staff persons might forget this and my experience is that the audience is permanently asking "How many persons can be elected?" Therefore the number of posts should appear automatically. If you don't agree please add a setting to get this. This way admins like me can enable this while others are not bothered.

The number of posts is mostly obviously (normally "1"

Ehm, no. For my next assembly we have for example to elect 2 chairman/woman, 4 vice chairman/woman, 2 revisors, 16 members of the managing board, 3 members of the arbitration committee, 12 members of the "Antragskommission", ...

This will be remodeled with the new client. If this issue still persists there. Reopen the issue.


feat(window): Implement basic custom-title-bar support

[x] ~Load a scene and display it in the custom-title-bar area~ (not so far)

it's time to draw somethings in the custom title bar area

fix maximize and fullscreen functions

create a preset scene in coding

draw somethings


Hotfix csv client

Features

Including aggregate settlement report csv api call

Delivers #134525555

@EvanBarbour3

Happy with this, @wnowicki


Added azcli extension only

Added functionality in extensions/azcli to be compatible with latest Azure CLI and Azure CLI Arc Extension 1.0.0. In this PR, Azure CLI has not been hooked up to other parts of ADS such as extensions/arc or extensions/resource-deployment.
How azcli differs from azdata extension:

Does not automatically update Azure CLI or the Azure CLI Arc Extension if version is not the latest
Does not automatically install Azure CLI or the Azure CLI Arc Extension if not installed
Notifies user if either is not installed or Azure CLI Arc Extension is not updated and gives a link to download the latest
Uses new parameters for Azure CLI Arc Extension such as --use-k8s flag and --k8s-namespace instead of --namespace
Parameter flag --k8s-namespace is required for most commands

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.002%) to 42.446%

Totals

Change from base Build<PHONE_NUMBER>:
-0.002%

Covered Lines:
26739

Relevant Lines:
57061

💛  - Coveralls


Debugger

Description
As you probably have read the issue https://github.com/dop251/goja/issues/294, this PR adds support for a debugger and exposes some APIs. The PR adds a bare minimum debugger that can control execution and wait for the commands from any frontend, like goja_debugger as a CLI frontend, and possibly DAP and other possible frontends.
Currently these commands, interfaces and utility functions are implemented:
// Compile script in debug mode
func CompileASTDebug(*js_ast.Program, bool) (*Program, error)

// Attach/detach a debugger
func (*Runtime) AttachDebugger() *Debugger
func (*Debugger) Detach()

// Resume running the script until the next debugger statement or breakpoint
func (*Debugger) Continue() ActivationReason

// Breakpoints (add, remove, list)
func (*Debugger) SetBreakpoint(string, int) error
func (*Debugger) ClearBreakpoint(string, int) error
func (*Debugger) Breakpoints() (map[string][]int, error)

func (*Debugger) StepIn() error
func (*Debugger) Next() error
func (*Debugger) Continue() error
func (*Debugger) Exec(string) (Value, error)
func (*Debugger) Print(string) (string, error)
func (*Debugger) List() ([]string, error)

// Return current values of the current script
func (*Debugger) Line() int
func (*Debugger) Filename() string
func (*Debugger) PC() int

Tests
Currently only three tests are written and clearly more tests are needed. These tests actually show failures in different parts, from failing to report correct line number to local variable retrieval issue in exec and print commands. Other tests will be added.
The ultimate "E2E" test is the CLI frontend: goja_debugger.
Discussion

For the local variable resolution, I found that dbg.vm.stack[dbg.vm.sb+dbg.vm.args+n] returns the correct value on the stack, but it isn't mapped to anything, which is understandable in terms of optimizations. How can we figure out the n from the varName?
It seems that having sourcemap reference in the code helps greatly with pinpointing lines in the source code, so I added sourcemap generation on-the-fly using esbuild (suggested by @nwidger) in goja_debugger project. Why does vm.prg.src.Position(vm.prg.sourceOffset(vm.pc)).Line sometime report the incorrect line, mostly the next line instead of the current line?

Contributors

@mostafa (original POC and further developments)
@MStoykov (new design of API and further developments)
@nwidger (lots of great feedback on the original issue)

@nwidger , currently one of the big questions is whether we can fix the print and exec to work in a useful manner. That definitely depends on @dop251 being happy with even more internal changes and hopefully helping at least guidance on what will be needed to be done, if not with actually doing it ;). Without fixing those problems I see very little reason to continue fixing something that can actually tell me less stuff than a console.log(a) ;).
The current problem with print and exec as I see it:

due to how js name resolution works and goja trying to do some optimizations it is not easy/possible currently to know if a is a variable in the local scope, an argument to the list, a global, defined in the calling function to a lambda etc ... All of those things basically change where the variable is stored and effectively how to retrieve it. While goja compiles code it knows this stuff and if there is a simple variable that will never leave the scope it just gets put somewhere on the stack (for example). Here for example the solution IMO will be for goja to be able to emit some debug information, possibly by just recompiling the source code with some flag, so that we don't add additional work for a normal compilation if the debugger will never be attached. That debug information can then be used to know that a on line 15, character 12 is defined as a stack variable in this place, but at character 15 it's redefined and is now in this stack (for example if there are multiple scopes).
exec, IMO, will be "a bit" harder even conceptually as it's basically "execute me this code as if it was written in exactly the place I'm currently". "The place" the debugger is currently can be midline for example and as the above example have a difference as it will need to resolve a from a different place depending on whether it's a bit later or not. This also likely has even more implications than I can think of. I would expect things such as v8 to just move from very optimized code to very not optimized code at this point that just expects that you can run eval with all variables everywhere. This can possibly be done in goja as well but it will mean that something like the debug information above will need to be used to move variables between the two stacks(and more) as that will definitely change if we compile the code in such a way.

Given the above two and the complexity I envision, I really do want @dop251 to confirm or deny if there is any interest on their side to help or even merge something that will make print and exec actually used within a local scope.
For the record I did try to:

run exec without making a new function and looked at what ended up on the stack, but this still did not help in any way as the new program has no idea what a is so it just tries to load it as global(or something like that).
I was thinking of trying to recompile the original code with the added one, but I very quickly realized that this will likely move stuff around and it will be really hard to do any surgery such that I can go back and forth between the two programs while saving the current state.

@mostafa I wonder if it might not be a good idea to have Debugger.Breakpoints return a struct type for each breakpoint. I could totally see wanting to, say, add the ability to temporarily disable a breakpoint without actually deleting it, or to include a count indicating how many times a breakpoint has been hit. The current signature of the method would make future extensions like that difficult without breaking the API, which I assume isn't something we'd want to do.
I still also think that if it's not too difficult a Debugger method to get the current call stack would probably be good to include in an MVP like this. At least when I've used gdb in the past, bt was the first command I'd run.

@MStoykov I agree that getting some feedback/guidance from @dop251 sooner rather than later is probably a good idea.  At this point finding out whether he has any interest in merging a debugger API in the first place, and also how willing he'd be for more internal changes to make the debugger interface more useful would probably be a good idea.  I don't have any specific feedback regarding the current issues with print or exec (it sounds like you have a far deeper knowledge of the goja internals in this area than me), but your idea of asking the compiler to optionally include extra debugging information or perform fewer optimizations certainly sounds reasonable to me.
On a separate topic, has any thought been given to activating the debugger when an exception/panic occurs?  I believe in some JS debuggers this is an option that can be toggled on/off.  At least for JS exceptions, you may not want the debugger to activate for every exception, but I'd assume the debugger should probably activate if a Go panic is otherwise going to make the debugger itself explode.  For example, I this most people would want the debugger to activate when it hits line 5 of this script:
function test(val) {
    return val + 1;
}
console.log(test(0));
console.log(tes(1));
console.log(test(2));

But instead a just get a nasty panic causing the debugger to terminate:
debug[10]> l
  1     function test(val) {
  2       return val + 1;
  3     }
  4     console.log(test(0));
> 5     console.log(tes(1));
  6     console.log(test(2));
  7     //# sourceMappingURL=data:application/json;base64,ewogICJ2ZXJzaW9uIjogMywKICAic291cmNlcyI6IFsic2NyaXB0cy9kZWxtZS5qcyJdLAogICJzb3VyY2VzQ29udGVudCI6IFsiZnVuY3Rpb24gdGVzdCh2YWwpIHtcbiAgICByZXR1cm4gdmFsICsgMTtcbn1cbmNvbnNvbGUubG9nKHRlc3QoMCkpO1xuY29uc29sZS5sb2codGVzKDEpKTtcbmNvbnNvbGUubG9nKHRlc3QoMikpO1xuIl0sCiAgIm1hcHBpbmdzIjogIkFBQUEsY0FBYyxLQUFLO0FBQ2YsU0FBTyxNQUFNO0FBQUE7QUFFakIsUUFBUSxJQUFJLEtBQUs7QUFDakIsUUFBUSxJQUFJLElBQUk7QUFDaEIsUUFBUSxJQUFJLEtBQUs7IiwKICAibmFtZXMiOiBbXQp9Cg==

debug[10]> n
panic: ReferenceError: tes is not defined

goroutine 34 [running]:
github.com/dop251/goja.(*Runtime).throwReferenceError(...)
	/home/niels/projects/goja/runtime.go:409
github.com/dop251/goja.valueUnresolved.throw(...)
	/home/niels/projects/goja/value.go:903
github.com/dop251/goja.(*vm).toCallee(0xc000296480, 0xadfb58, 0xc0002230e0, 0x10)
	/home/niels/projects/goja/vm.go:633 +0x2cd
github.com/dop251/goja.call.exec(0x1, 0xc000296480)
	/home/niels/projects/goja/vm.go:2379 +0x7a
github.com/dop251/goja.(*Debugger).Next(0xc0002c9050, 0x1, 0xa207bd)
	/home/niels/projects/goja/debugger.go:123 +0xc6
main.repl(0xc0001ead12, 0x1, 0xa496e0)
	/home/niels/projects/goja_debugger/repl.go:86 +0xf65
main.main.func3(0x1, 0xa20929, 0x2)
	/home/niels/projects/goja_debugger/main.go:97 +0x2be
created by main.main
	/home/niels/projects/goja_debugger/main.go:86 +0x3e5

Perhaps a new ActivationReason like panic/exception for when this occurs would make sense?  I understand that this is all a work in progress, so I'm just curious if this is on the roadmap at all. :)

@nwidger

While experimenting with DAP, I found that some things are left for the frontend to implement, like breakpoint counting or maybe enable/disable of breakpoints, but I'll try to have a stable API with tests before merging anything.
I think implementing a command to see the current call stack is feasible.
I am not sure about jumping into debugger if an error/panic/exception happens because the program should have debugMode enabled on the runtime, otherwise it won't even bother. Yet I see that the current frontend panics on such issues. I'll see if I can fix that.

Sorry, I haven't got the chance to review the code yet, but I would merge it assuming good maintainability and minimum performance impact when debugging is not enabled.
As for resolving variables, I think there is an easier approach: variable names are kept at runtime when (and only when) there is a possibility of a dynamic lookup (i.e. lookup by name that is not known at compile time). This can happen when at least one nested scope has a direct eval(). In this case scope.dynLookup is set to true. If you change the compiler so that in debug mode it always sets this flag, it should do the trick. Thinking further ahead, in order to be able to run code in the current scope, the compiler should assume each scope contains a direct eval, so scope.dynamic should always be set to true, rather than scope.dynLookup.
While there definitely should be a debug mode for compiling, there is a problem that a Program could be compiled externally (using goja.Compile() or goja.MustCompile()). The source code may not be available (e.g. it was compiled from a dynamically generated AST). This should be handled somehow.
The use of sourcemaps looks strange to me, there should be no need for that. If you could give me some examples where is skips lines I could take a look.

As for resolving variables, I think there is an easier approach: variable names are kept at runtime when (and only when) there is a possibility of a dynamic lookup (i.e. lookup by name that is not known at compile time). This can happen when at least one nested scope has a direct eval(). In this case scope.dynLookup is set to true. If you change the compiler so that in debug mode it always sets this flag, it should do the trick. Thinking further ahead, in order to be able to run code in the current scope, the compiler should assume each scope contains a direct eval, so scope.dynamic should always be set to true, rather than scope.dynLookup.

I did try just making compiler.isDynamic() return true, but apparently, I either tested something for which this wasn't enough or tested print not exec, as print currently tries to find stuff on the stack(somehow).
But one of our tests now works :tada: , so this seems like it will work at least for some of the cases, and it probably works even better if I do what you suggested instead of changing the function ;). Thanks @dop251
Unfortunately, this has a (small) downside that you need to enable debug mode in the very begging and compile your source code with debug mode, which might mean that it will be less useful, but definitely a lot better than not working at all :).
I will try to get this change made and fix exec and print accordingly, before doing any other API changes like that will probably necessitate some.

@dop251 @MStoykov
I found one of the nasty bugs I used to run into, which reported incorrect lines while testing step-in command:
While inside a function, the vm.pc and hence the dbg.vm.prg.src.Position(dbg.vm.prg.sourceOffset(dbg.vm.pc)).Line is reset. Inside a function the vm.pc equals 0 and thus the line number is reported based on that, yet I assumed that the function declarations are part of the vm.prg.code, yet they behave differently. I'll add more tests and try to see if I can find a way to fix this issue in debugger. Actually I can detect if we're inside a function, but the question remains: how should we calculate the line number and reflect it in the rest of the functions, so we don't jump lines.

@mostafa @MStoykov Would it make sense to enable debugging with something like an optional WithDebugMode option to Compile/CompileAST/MustCompile instead of adding a whole new CompileASTDebug function?  This would be similar to what was done for the WithSourceMapLoader option in the parser package.

Current problems from my "integration" with k6:

next/stepin either don't work very well or not at all. They sometimes just don't do anything and then they jump ... or don't :shrug: .
k6 has a lot of cases where you will call into k6/go and then it will call a js function like in
group("name", func() { //code here })
where group is implemented in go and it does some stuff and then calls the provided function. As far as I can test (in the limited time I tried) this completely breaks the line detection and I can't really do anything useful within the group if I just stepin/next to any code from outside to inside a group. It clearly executes the instructions at some point as I can see side-effects of it, but I can't actually execute in the context unless I put a breakpoint/debugger statement inside and continue to it. This might be a problem with how k6 runs this functions and how the debugger works.
As a whole the feedback on what just got executed is ... bad/nonexistent which leads to you not really being certain what stepin will did and because of 1 sometimes I can't really be certain if it just did nothing or did it do something that didn't change anything visible.
There is no step command but it will probably suffer even more heavily from the above
I do think that between 3 and 4 it's very likely that the current Next and Stepin implementation will need to be redone ;)
List is another function that works strangely. In the case of k6 (and possibly other users needing debugger) we do have transpilers in a lot of the cases( babel ) which can generate sourcemaps and k6 now has PoC support to actually use them. This still does mean that List will return the actual code goja execute, but other parts(Line) will return according to the original code that was transformed, which is arguably the correct behaviour. This gets really confusing and it seems to mostly work, except when it doesn/t Which is why k6 just gets the original code itself. Also of note is that even without source maps the stepin/next work funky, so that isn't because of that :(.
Again in the case of k6, babel may rename identifiers, for example transpiling import http from "k6/http" will not lead to having an http identifier but _http(it obviously changes it everywhere) which also is super confusing and is likely just a very small of such changes. So if you don't know about those things it seems like exec doesn't work. I expect this might be even more prevalent in other transpilers like the typescript compiler or a minimizer of any sort. This can probably be fixed through just sourcemaps ?

A lot of the above seem to me like things that proper use of sourcemaps is already fixing somewhat and the debugger(and probably also goja) needs to get a bit better support for them. And as I want to actually get sourcemap support in k6 and 80% of the work is done, I will likely try to see if I can fix some of them or at least diagnose them more accurately.
For the rest I think this is due to the hackish nature of some of the things that were done in order to get something working and likely with a bit more understanding of goja it will be possible to stabilize them.
Things that I definitely think should be dropped from this PoC are:

List - it practically should be provided by the debugger/application as is the case in k6 PoC
Print - it was an early try at getting variables somehow but it in practice is the same as exec for that use case so I see no reason to have Print (especially as it doesn't work ;) ).

I also think that likely Next and StepIn have some (subtle) bug that makes them behave as said above.
Thank you @mostafa for starting the work on this.
Also thanks to @nwidger for the suggestions and review and of course thanks to @dop251 for goja as a whole and the help so far to get this working. :tada:

@mostafa @MStoykov Would it make sense to enable debugging with something like an optional WithDebugMode option to Compile/CompileAST/MustCompile instead of adding a whole new CompileASTDebug function? This would be similar to what was done for the WithSourceMapLoader option in the parser package.

It makes sense, but it will be a breaking change and as I mention above there are still things to change so the API is definitely not final.
I guess we can add a variadic parameter on the current ones without breaking changes :thinking:

@MStoykov Yes sorry I should been a little clearer, I meant changing the signatures to look something like:
type CompileOption func(*compileOptions)
func WithDebugMode() CompileOption

func Compile(name, src string, strict bool, options ...CompileOption) (*Program, error)
func CompileAST(prg *js_ast.Program, strict bool, options ...CompileOption) (*Program, error)
func MustCompile(name, src string, strict bool, options ...CompileOption) *Program

which I believe for the majority of people would not be a breaking change.

Thanks @MStoykov for taking time and fixing lots of my erroneous Go code. You know I am a Python developer by nature. :wink:
Thanks @nwidger for your great feedback, comments and suggestions along the way. I tried your proposed changes as parser options and it didn't turn well. Probably @MStoykov and I could have a look after we find deeper issues we currently have.
@dop251
What @MStoykov described as issues in k6 are actually mostly implementation issues in the debugger or goja_debugger application, mostly because of lack of understanding of how Goja works internally. I tried multiple ways to step through lines using delve, but it still needs your attention. As @MStoykov also mentioned, the API needs more work to become stable, but the current PR just works, until you have a look and guide us in the correct direction and point us any issues you see in the code, especially in Next and StepIn. Thanks in advance! :slightly_smiling_face:

The changes in this PR is outdated, and the whole project is in limbo. So, let's close this PR until we have time to fix it.


use of a single collector to scrape 1337x target

#42 I have now implemented the use of a single collector now, Let me know if you have any questions regarding it.

@ash-kamrip  I have tested the changes locally, the code is working fine and the stream is starting without any issues. Other than minor variable name changes, we are good to go

One more structural change i think is we should not have a interface for collector object , but then since we taken input a collector alredy was a little confused as to how to achieve it. I wanted to code this with parallel threads but that is something we can think about later i guess.

@qascade required changes are done now.

Collector is a part of the Scraper struct which is not an interface. Collector in itself is whether an interface or not is not our concern as it is a design decision of Go-Colly peeps. If you want to work to further optimize this using concurrency. You are free to do that. We can do that in this PR itself. Other than that Looks good to merge. If you are planning to work on further optimization, do let me know otherwise I will merge the PR. Thanks for your contribution.

I am browsing other repos for hacktoberfest as of now , would not be able to optimize this further at the moment. Kindly merge this PR as of now.


[Feature Request] : Are you working on integrating the test runs on cloud device providers like Sauce Labs , Browser Stack.

As an automation engineers, we would always run automation scripts on real devices.
So it would be easy if you can provide us a way to integrate our scripts with cloud testing providers like Sauce Labs, and Browser Stack, at least for Android as iOS is still in the development stage to run on real devices.

Hello, following @BharathSaraswathi's question, is there the possibility of expanding the service for testing on multiple real devices

Support for running on multiple device in parallel was contributed in #1732 and will be released in the next stable version.
Currently we don't have plans to add explicit support 3rd party testing platforms. As long as you can run an emulator and have shell access, you can run Maestro yourself.
Could you clarify the request exactly here?
PS Before you ask for support of a fully-managed service like Firebase Test Lab - it's not possible with Maestro's architecture (heavy usage of adb and xcrun simctl, which is not possible on Firebase Test Lab and similar).


python310Packages.fakeredis: 2.4.0 -> 2.5.0

Diff: https://github.com/dsoftwareinc/fakeredis-py/compare/refs/tags/v2.4.0...v2.5.0
Changelog: https://github.com/cunla/fakeredis-py/releases/tag/v2.5.0
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.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.

Result of nixpkgs-review pr 212377 run on x86_64-linux 1

2 packages failed to build:

python311Packages.celery-redbeat
python311Packages.fastapi-mail

5 packages built:

baserow
python310Packages.celery-redbeat
python310Packages.fakeredis
python310Packages.fastapi-mail
python311Packages.fakeredis

Result of nixpkgs-review pr 212377 run on x86_64-linux 1

1 package marked as broken and skipped:

python311Packages.celery-redbeat

1 package failed to build:

python311Packages.fastapi-mail

5 packages built:

baserow
python310Packages.celery-redbeat
python310Packages.fakeredis
python310Packages.fastapi-mail
python311Packages.fakeredis


[StreetCode page] [Chronology] The selected square under the year becomes darker and moves

Environment: Mobile (Samsung Galaxy S9)
Reproducible: Always
Build found: daea670
Preconditions

The site is open.
At least one StreetCode with a 'Chronology' block has been created.

Steps to reproduce

Open the StreetCode page.
Scroll down to the 'Chronology' block.
Click on the grew square.
Using the camera film, scroll to either the right or left side.

Actual result
The dark square stays in the same place and moves.
https://github.com/ita-social-projects/StreetCode/assets/135108144/4188ea70-bc29-4386-bbf2-fd404ebdaa5e
Expected result
The square in the middle is always the same.
Mockup
User story and test case links
User story #39
[Test case] #345

Not reproducible.


cmake: make install path configurable

Making CMake install locations configurable.
I also  changed the default for the CMake Target files to share instead of libdir as the library is header-only and arch-independent.

@junghans Thank you for the contribution!
I'm not really familiar with GNUInstallDirs. When is it useful? Was the current state insufficient for your needs?
Not sure about share/, as my understanding is that it is mostly where documentation, fonts, etc go. For a library, I would not expect it to be found there. Otherwise, it looks fine to me.

I'm not really familiar with GNUInstallDirs. When is it useful? Was the current state insufficient for your needs?

The issue was that things got installed in lib and not lib64, which should be the default for 64-bit system, using GNUInstallDirs instead of a hard-coded lib will fix that.

Not sure about share/, as my understanding is that it is mostly where documentation, fonts, etc go. For a library, I would not expect it to be found there.

CMake is looking into <prefix>/(lib/<arch>|lib*|share)/cmake/<name>*/
(See https://cmake.org/cmake/help/latest/command/find_package.html) so it shouldn't matter much and as your target files are architecture independent share seems the better place.

it shouldn't matter much and as your target files are architecture independent share seems the better place.

The way I read the Filesystem Hierarchy Standard, share is for non-modifiable data files only, not code:
The /usr/share hierarchy is for all read-only architecture independent data files.

Is there an example of a library that installs headers in /usr/share or similar?

it shouldn't matter much and as your target files are architecture independent share seems the better place.

The way I read the Filesystem Hierarchy Standard, share is for non-modifiable data files only, not code:
The /usr/share hierarchy is for all read-only architecture independent data files.

Is there an example of a library that installs code headers in /usr/share or similar?

Sorry, it is not about the headers, I only want to change the default for the CMake files from lib to share. Headers go into include by default, are configurable now.

@aprokop I went for the minimal version, as ${CMAKE_INSTALL_DATADIR} is only used for the CMake Modules, one can always just change that default.

This last change goes against what @dalg24 wanted, I think, in that the default location for the cmake/ is now share instead of lib.

@aprokop I went for the minimal version, as ${CMAKE_INSTALL_DATADIR} is only used for the CMake Modules, one can always just change that default.

This last change goes against what @dalg24 wanted, I think, in that the default location for the cmake/ is now share instead of lib.

@dalg24 Does https://discourse.cmake.org/t/what-should-the-destination-be-for-a-header-only-librarys-cmake-config-file/8473 convince you to go with share as a default?

I don't care too much as long as it is the search paths constructed for both Windows and Unix which both lib* and share are

Build errors are unlreated.

@junghans Thank you for your contribution and patience.


executor refactor

Codecov Report
Patch coverage: 54.92% and project coverage change: -0.28 :warning:

Comparison is base (7f4d6c6) 77.16% compared to head (0a255e8) 76.88%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #131      +/-   ##
==========================================
- Coverage   77.16%   76.88%   -0.28%
==========================================
  Files         122      124       +2
  Lines       15859    15902      +43
==========================================
- Hits        12237    12226      -11
- Misses       3622     3676      +54

Impacted Files
Coverage Δ

xngin-compute/src/eval/builder.rs
90.75% <ø> (ø)

xngin-compute/src/eval/mod.rs
93.33% <ø> (ø)

xngin-plan/src/digraph.rs
94.73% <ø> (ø)

xngin-plan/src/explain.rs
85.76% <ø> (ø)

xngin-server/src/exec/builder.rs
0.00% <0.00%> (ø)

xngin-server/src/mysql/session.rs
25.00% <0.00%> (ø)

xngin-server/src/exec/mod.rs
29.78% <33.33%> (-50.86%)
:arrow_down:

xngin-plan/src/phy/mod.rs
75.00% <50.00%> (-12.50%)
:arrow_down:

xngin-server/src/exec/proj.rs
65.38% <56.25%> (-20.98%)
:arrow_down:

xngin-plan/src/phy/builder.rs
75.47% <75.47%> (ø)

... and 6 more

... and 6 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


feat: add MAD sample on website

/azp run

Codecov Report

Merging #1323 (6c99727) into master (1804204) will decrease coverage by 5.14%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1323      +/-   ##
==========================================
- Coverage   84.71%   79.57%   -5.15%
==========================================
  Files         284      283       -1
  Lines       13911    13887      -24
  Branches      682      673       -9
==========================================
- Hits        11785    11050     -735
- Misses       2126     2837     +711

Impacted Files
Coverage Δ

...se/ml/cognitive/MultivariateAnomalyDetection.scala
88.37% <100.00%> (+0.27%)
:arrow_up:

...m/src/main/scala/com/microsoft/lightgbm/SWIG.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...soft/azure/synapse/ml/cognitive/AudioStreams.scala
0.00% <0.00%> (-87.88%)
:arrow_down:

...ft/azure/synapse/ml/cognitive/AzureSearchAPI.scala
2.59% <0.00%> (-87.02%)
:arrow_down:

...azure/synapse/ml/lightgbm/LightGBMClassifier.scala
11.11% <0.00%> (-80.00%)
:arrow_down:

...osoft/azure/synapse/ml/cognitive/AzureSearch.scala
9.35% <0.00%> (-78.42%)
:arrow_down:

...t/azure/synapse/ml/cognitive/SpeechToTextSDK.scala
18.43% <0.00%> (-72.16%)
:arrow_down:

...crosoft/azure/synapse/ml/cognitive/SpeechAPI.scala
0.00% <0.00%> (-70.00%)
:arrow_down:

...t/azure/synapse/ml/lightgbm/LightGBMDelegate.scala
0.00% <0.00%> (-50.00%)
:arrow_down:

...soft/azure/synapse/ml/cognitive/SpeechToText.scala
44.23% <0.00%> (-40.39%)
:arrow_down:

... and 24 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 1804204...6c99727. Read the comment docs.

/azp run


LuCI: Realtime graphs buggy after changing browser windows size

Is there an existing issue for this?

[X] I have searched the existing issues

screenshots or captures
Hello and good day!
I've installed the newest OpenWrt Release Candidate RC-4 and have discovered a visual bug by accident.
When opening up any realtime graph on a small browser window and then expanding said window, the displayed info of graph will end up being stuck relative to the bast window size on the "coordinate system". This basically means it ends up staying in the middle and "spawning" new data from there instead of the most right side of the graph.
This ONLY works if you open up any graph in a very narrow browser window and then expand that window. It does NOT work when you open up the graph in a fully sized window and then make it small. In that case you have to reload the winow or switch to a different graph and reload!
This is the graph after opening it up small and then expanding the browser window:

This is the graph after doing the step above and waiting for a while:

This is how it should actually look like (always start on the most right side of the "coordinate system"):

Actual behaviour
As described on the "screenshots or captures" section
Expected behaviour
The graph should always start at the most right part of the coordinate system regardless of window size.
Steps to reproduce
Open up chrome in a very narrow window. Got to Status > Realtime Graphs and wait a couple seconds to fill up the graph.
After that expand the browser window and make it wide.
Additional Information
NAME="OpenWrt"
VERSION="24.10.0-rc4"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 24.10.0-rc4"
VERSION_ID="24.10.0-rc4"
HOME_URL="https://openwrt.org/"
BUG_URL="https://bugs.openwrt.org/"
SUPPORT_URL="https://forum.openwrt.org/"
BUILD_ID="r28211-d55754ce0d"
OPENWRT_BOARD="ramips/mt76x8"
OPENWRT_ARCH="mipsel_24kc"
OPENWRT_TAINTS=""
OPENWRT_DEVICE_MANUFACTURER="OpenWrt"
OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/"
OPENWRT_DEVICE_PRODUCT="Generic"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="OpenWrt 24.10.0-rc4 r28211-d55754ce0d"
OPENWRT_BUILD_DATE="1734915335"

What browsers do you see the problem on?
Chrome
Relevant log output
No response

The graph window, and most other windows have a fixed size, which I think is based in the CSS. So this is more of a universal thing. Resizing the window will not affect the graph size (but viewing from a mobile device might).