Test coverage regression with const constructors

On both stable and master channels of flutter, defines two files:
// main.dart
class Foo {
  const Foo();
}

// main_test.dart
import 'package:flutter_test/flutter_test.dart';

import 'package:example/main.dart';

void main() {
  test('Counter increments smoke test', () {
    const Foo();
  });
}

Then run flutter test --coverage
This will report the constructor of Foo to not be covered by tests when it is.
It seems like this issue happens if the constructor is used only with the const keyword. Changing the test to:
test('Counter increments smoke test', () {
  Foo();
});

correctly reports the constructor has covered.

/cc @askeksa-google my guess is that this is because of constant evaluation..? Is there any story for constants and coverage?

This is working as expected. Constants are now evaluated in compile time so we don't have dynamic coverage information for them.
@a-siva I am not sure if we want to emulate old behaviour? Constant table is loaded lazily so we could actually traverse it while collecting coverage and infer from that which constants were accessed by the code that run. However constant table does not store enough information to give accurate coverage information (e.g. if class has multiple const constructors we have no way of knowing which constructor was used just by looking at the constant table - because it contains fully evaluated constants).

This is working as expected. Constants are now evaluated in compile time so we don't have dynamic coverage information for them.

It used to work though. Why is that change desired?
The only way to fix this issue from a Dart developer point of view is to voluntarily not use the const keyword in tests.
This is both unintuitive and will trigger a prefer_const lint.
And it's not that uncommon either.
On a single file example of provider, I have that issue happening 4 times.

It used to work though. Why is that change desired?

Constants used to be lazily evaluated by the VM (and other back-ends), now it is Dart front-end that handles constant evaluation logic. This consolidates the implementations, simplifies back-ends and allows front-end to properly report compilation errors that were missing (or impossible) before.
This in turn allows faster language evolution. For example, without this change it would be rather complex to support constant UI-as-code expressions (const [a, ...b, c]), with proper errors messages and semantics - and it would require work in all backends. (That is why by the way UI-as-code was first released without support for constant expressions - because constant-update-2018 was not ready yet).
It would be honest to admit that we did not consider implications on the coverage information (and we did not have tests covering this particular case) - but even if we did, we would still do the change.

This seems like a duplicate of https://github.com/flutter/flutter/issues/28542 which was fixed.

@a-siva it is not a duplicate, though it is related. flutter/flutter#28542 was just about static const fields.

Considering how --track-widget-creation, would it be possible to do the same to solve this issue?
According to that comment, that flag works by adding invisible parameters on the constructor.
Could we add an invisible parameter that tracks which constructor was used?

An invisible parameter could indeed tell you which constructor was used to produce a particular constant. However, this would break canonicalization of constants. In contrast to widgets (whose canonicalization you discussed in https://github.com/flutter/flutter/issues/44858) there are classes whose proper canonincalization are necessary for some subsystems to work.
Alternatively, a less precise form of coverage information could be provided, which only tells you whether a particular class is const instantiated somewhere in the program (and/or whether a constant expression containing such an instance was executed). I don't know to what extent such a feature is feasible in the Flutter coverage tool.

However, this would break canonicalization of constants

Really? I don't understand how. 🤔
Because two identical consts will always use the same constructor.
This would transform:
const foo = Foo();
const foo2 = Foo();

const namedFoo = Foo.named();
const namedFoo2 = Foo.named();

into:
const foo = Foo(constructor: 'default');
const foo2 = Foo(constructor: 'default');

const namedFoo = Foo.named(constructor: 'named');
const namedFoo2 = Foo.named(constructor: 'named');

So both foo and foo2 should still be "identical".

Objects constructed using different constructors can end up being identical.
class Foo {
  const Foo() : a = 0;
  const Foo.named(this.a);

  final int a;
}

main() {
  const x = Foo();
  const y = Foo.named(0);
  print(identical(x, y));
}

prints true.
If metadata about the used constructor is added to the constants, they will no longer be identical.

We have no plans to fix this. So closing this to reflect this.

Hi 👋,
unfortunately, we also facing the same issue described in this ticket. As @mraleph described there were reasons to make it that way but as it was mentioned:

we did not consider implications on the coverage information (and we did not have tests covering this particular case)

that really affects the smoothness of programming for all levels of experience. Coverage is an important metric - so it would be great if we could do something to make its collection reliable and that supports all of the Dart features.
If I may I want to bring attention to this issue for @timsneath @eseidelGoogle - hope we can have some solution.
Illia

FWIW, here are my thoughts on what it would take (at minimum) to implement this:

The Kernel format is extended such that all ConstantExpression nodes contain a list of the program locations of all expressions that were evaluated to produce that constant. This is a property of the constant expression, rather than the constant itself, since the same constant may arise through different computations.
The constant evaluator keeps track of the locations of all expressions involved when it evaluates a constant and stores these into the resulting ConstantExpression. It will require some careful design to make sure that this does not cause unacceptable overhead in the situations where the feature is not used.
When the VM reports coverage, it includes the locations associated with all executed constant expressions. This is so different from the way the VM currently tracks coverage that it essentially amounts to a separate coverage tracking mechanism on top of the existing one.

@mraleph Is there any chance of this ticket getting reopened?
I believe that the issue described by @rrousselGit is, in fact, still present and I consider the original issue a tooling problem. The explanation for the coverage report error is not trivial, and I would not consider this as "working as intended": the lines were called by the tests, so it should not be reported as "not covered".
I understand that the issue might not be the highest priority, or fixed in the next weeks, but I don't understand why it should be closed.

Just imagine you write your tests, see that some part of the code is not covered, even though your intuition would suggest otherwise. Then you spend time tracking down the issue, then introduce workarounds (not calling it with const), which in turn might require that you add exceptions to your listing rules in your test directory. Then, the same happens to your coworker: see and solve issue, continue workarounds... Then a third coworker deletes those because he/she doesn't understand why the lint exceptions were added and a const constructor is called without a const...

What I'm trying to say that it's an annoying issue and, based on @askeksa-google's comment, there might be a solution.

the lines were called by the tests, so it should not be reported as "not covered".

The lines were not really "called" by tests in the same sense the rest of your code was called. For example:
class X {
  const X();
}

void main() {
  test('a', () {
    const X();
  });

  test('b', () {
  });
}

const X() would be evaluated by the front-end whenever you parse this file - it does not matter whether you will end up running test a or b or neither or them.
In the old world const X() would actually be executed in the backend and only if you actually run test a.
So if you look at the coverage as "report which parts of the program actually executed" then not reporting the constructor as executed is absolutely correct.

What I'm trying to say that it's an annoying issue and, based on @askeksa-google's comment, there might be a solution.

Yes, there is a solution, however it is rather complex and cross cutting. We might address this at some point in the future, but currently it does not look like this is something we are going to prioritise working on.

So if you look at the coverage as "report which parts of the program actually executed" then not reporting the constructor as executed is absolutely correct.

But in that sense, since the file compiled, it was executed.
It was executed during compilation but still executed. Otherwise, the following code would run:
class Example {
  const Example(): assert(false);
}

void main( ){
  const Example();
}

but we currently get a compilation error.

Here's an idea:
What if the constant evaluator kept track of all the places it evaluated during the constant evaluation and communicated that to the VM as "pre-executed"?
This is different from before, though, as for instance code like this:
main() {
  foo(false);
}

foo(bool b) {
  if (b) bar();
}

bar() {
  print(const Baz(42));
}

class Baz {
  final x;
  const Baz(this.x);
  String toString() => "Baz[$x]";
}

would mark the Baz constructor as having run because the compiler evaluated it - even though it wouldn't have been marked as run before because the code-path was not executed.
It is technically true, though, as it was already evaluated and thus logically executed --- just by the compiler rather than the VM.
Would this satisfy your needs?

That sounds good to me

(Some) support for const constructor coverage landed about a month ago. Has anyone had a chance to try it out?

(Some) support for const constructor coverage landed about a month ago. Has anyone had a chance to try it out?

That looks like it fixed it for me.

That looks like it fixed it for me.

I'm using stable Flutter (1.22.5) and added new coverage by:
dependency_overrides:
  coverage: ^0.15.0

However, the resulting coverage is still not taking into account the const constructors of widgets. Have a look at the coverage report generated from widget tests with genhtml for one of my widget classes:
flutter test --no-pub --test-randomize-ordering-seed random --coverage
genhtml ./coverage/lcov.info -o coverage

Is there any other way to force new coverage behavior than switching to master channel?

I'm using stable Flutter (1.22.5) and added new coverage by:
dependency_overrides:
  coverage: ^0.15.0

However, the resulting coverage is still not taking into account the const constructors of widgets. Have a look at the coverage report generated from widget tests with genhtml for one of my widget classes:
flutter test --no-pub --test-randomize-ordering-seed random --coverage
genhtml ./coverage/lcov.info -o coverage

Is there any other way to force new coverage behavior than switching to master channel?

I am having the same issue. I have updated my analysis_options.yaml file to include the prefer_const lint and my CI pipeline breaks const constructors aren't recognized.

This is a screen from codecov. I haven't found a solution for this yet so I have changed the minimum coverage from 100 to 95 but I'm really waiting for a fix!

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.0.2, on Microsoft Windows [Version 10.0.19041.867], locale en-EM)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.1)
[√] Chrome - develop for the web
[√] Android Studio (version 4.1.0)
[√] IntelliJ IDEA Community Edition (version 2020.3)
[√] Connected device (2 available)

@albertodev01 as https://github.com/dart-lang/sdk/commit/6c19a8fc81f6196abb181500e6e58f312aa43e0a explains we only record enough information to mark constructor itself as executed, but not enough to mark individual initializers, so what you are seeing is expected.
@jensjoha can comment further on how realistic it is to record enough information to also mark initializers.

Unfortunately I don't think it's very realistic to add real tracing of initializers (that also works across edits).
We would have to be able to symbolically reference expressions --- the best we came up with back then was a counting scheme where we could say that the ath, bth and cth expressions (for instance) were evaluated --- but it seems rather complicated to do that and make it work consistently in both the front_end and the VM. It's not that it can't be done, it's that the investment seems unproportionally large.

Would it perhaps make sense to consider all initializers also executed if the constructor is const executed? While this is less precise than the ideal solution, it seems like the most useful interpretation given that many users are aiming for 100% coverage.

It was discussed briefly back in December, but I personally don't like it. I'd rather have coverage being conservative so that if something is claimed to be covered it actually is, rather than something being marked as covered meaning that it might be covered.
Ultimately I guess it's a VM decision though.

Here was a discussion about ignoring lines from coverage and // coverage:ignore-line did the job

Not the most beautiful solution to the problem, but anything is better than lowering the minimum coverage


Getting another MovieClip instance with Assets.getMovieClip() breaks previous instance (regression)

I use swf assets in my project (type="swflite" preload="true"), loading the entire timeline of every library:
clip = Assets.getMovieClip('libraryName:');
At some point in the last 1 or 2 public releases, the behavior of this changed: instead of being able to create multiple instances of the same clip (as expected), the previous instance now disappears from the screen and its children all become null.

This is working for me:
openfl create NyanCat DuplicateTest
cd DuplicateTest

and editing "Main.hx"
package;

import openfl.display.Sprite;
import openfl.Assets;

class Main extends Sprite {

	public function new () {

		super ();

		var cat = Assets.getMovieClip ("library:");
		cat.x = -100;
		addChild (cat);

		var cat2 = Assets.getMovieClip ("library:");
		cat2.x = 100;
		addChild (cat2);

	}

}

and running
openfl test neko

Do you know how I might replicate the problem? :smile:
Thank you!


after installing plugin i cant join the server.

https://media.discordapp.net/attachments/947782839762554890/1014105996316123196/2022-08-30_12.34.44.png?width=1089&height=612

The plugin is incompatible with bungeecord since bungeecord does exactly the same as my plugin what with multiple servers

https://media.discordapp.net/attachments/947782839762554890/1014105996316123196/2022-08-30_12.34.44.png?width=1089&height=612

The plugin is incompatible with bungeecord since bungeecord does exactly the same as my plugin what with multiple servers


Why not support 'yyyy-MM-dd'

Why not support 'yyyy-MM-dd'??

We do.  It's YYYY-MM-DD.
Moment's parsing and formatting tokens are slightly different from other platforms.  Refer to the documentation.


Conflicting Information

Two statement on this page seem to be in conflict. After initial configuration, can the device have a static IP address? Under item 2 in "Preparing Your Environment":
It must be able to receive an IP address using DHCP. (Microsoft Teams Rooms cannot be configured with a static IP address at the first unit startup, but afterwards static IP for the device could be configured on the device or on the upstream switch or router.)
But then under "Check Network Availability":
Access to a server that can provide an IP address using DHCP. Microsoft Teams Rooms cannot be configured with a static IP address.

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

ID: a711c07e-10b3-baf0-b92c-9dbcf6ab9474
Version Independent ID: 2038cd48-44b1-1ed1-6e50-48290eef5605
Content: Prepare your Environment - Microsoft Teams
Content Source: Teams/rooms/rooms-prep.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@JeffBrownTech Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@JeffBrownTech  Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


[Feature Request]Drag and drop support, different views.

First of all i want to thank you for this little gem here.
What i'd like do have added if possible would be:
-drag and drop support
-several views

Drag and drop support is on its way! It's currently in the source, but has not yet reached release.

Great. I'll wait till the next release. Thank you very much!!


"orgs create" should send "display_name" instead of "name"

Right now, it appears as if orgs create -n "some-name" requires the name attribute only.
I think this could be improved by mirroring the UI experience where we send a display_name and let the backend auto-generate a name.

Optionally, people can of course always explicitly specify a name but I think the display_name should be a required parameter in this case

Fixed in #231


Error: Building package opengl:x64-windows failed with: BUILD_FAILED

Host Environment

OS: Windows 10.0.17134

To Reproduce
Steps to reproduce the behavior:
`./vcpkg install tesseract:x64-windows
Failure logs
The following packages will be built and installed:

leptonica[core]:x64-windows
libwebp[core]:x64-windows
opengl[core]:x64-windows
tesseract[core]:x64-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/4: opengl:x64-windows
Building package opengl[core]:x64-windows...
CMake Error at ports/opengl/portfile.cmake:20 (message):
Cannot find Windows 10.0.18362.0 SDK.  File does not exist: C:\Program
Files (x86)\Windows Kits\10\Lib\10.0.18362.0\um\x64\OpenGL32.Lib
Call Stack (most recent call first):
scripts/ports.cmake:91 (include)

Error: Building package opengl:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: opengl:x64-windows
Vcpkg version: 2019.09.12-nohash
Additionally, attach any relevant sections from the log files above.
Additional context
I used Visual Studio 2019 but I could not find the low version Windows 10.0.18362.0 SDK in Visual Studio Installer.  Windows 10.0.18362.0 SDK should be embedded in VS 2017 rather than VS2019 .

Thanks for posting this issue. Closed as duplicate of #5495. Please pay attention to the progress of issue #5495.


Issue 45375: Add index to speed common queries against core.notifications

Rationale
There are a handful of reasonably frequent queries against core.notifications that are taking >20ms to complete. An index should help.
Changes

Add index on UserId column, which is a common WHERE clause filter on all the queries

I've introduced a core script with the same versions in my Signing PR. I can bump mine to the next increment, but there will likely be timing problems given that you're merging to 22.8 and I'm merging to develop. Is it important that your change targets 22.8?


Support running disabled tests in testList

remove detailed logic from TestTarget class
create class TestList and TestCategory to handle each case
added logic to handle disabled tests in testList
keep status inside Variation class for precise control of sub test
adjust parallel list logic to handle disabled situation

Signed-off-by: renfeiw<EMAIL_ADDRESS>

Build
target
jdk version
platform
dynamic compile
dynamic parallel
branch

1547
disabled.sanity
11
x86-64_windows
yes
no
disabled

1525
disabled.sanity
11
x86-64_windows
yes
no
adoptium:master

1550
testList with disabled
11
x86-64_windows
yes
no
disabled

1527
testList with disabled
11
x86-64_windows
yes
no
adoptium:master

1551
sanity.openjdk
11
x86-64_linux
no
no
disabled

1529
sanity.openjdk
11
x86-64_linux
no
no
adoptium:master

1552
sanity.regular
8
x86-64_mac
no
yes
disabled

1535
sanity.regular
8
x86-64_mac
no
yes
adoptium:master

1553
native
11
x86-64_linux
yes
no
disabled

1537
native
11
x86-64_linux
yes
no
adoptium:master

1554
testList TESTLIST=disabled.abc
11
x86-64_linux
yes
no
disabled

1545
testList TESTLIST=SCURLClassLoaderTests,disabled.SCURLClassLoaderTests
11
aarch64_linux
yes
no
disabled

1555
testList TESTLIST=SCURLClassLoaderTests,disabled.SCURLClassLoaderTests_0
11
aarch64_linux
yes
no
disabled

1541
testList TESTLIST=SCURLClassLoaderTests_0,disabled.SCURLClassLoaderTests_0
11
aarch64_linux
yes
no
disabled

1549
testList TESTLIST=echo.disabled.SCURLClassLoaderTests_0,disabled.SCURLClassLoaderTests_0
11
aarch64_linux
yes
no
disabled

1548
testList TESTLIST=SCURLClassLoaderTests_0
11
aarch64_linux
yes
no
disabled

1546
SCURLClassLoaderTests
11
aarch64_linux
yes
no
disabled

As discussed we can review this, but will wait to merge it until after we tag AQAvit repos (which will come after 1 enhancement issue / archiving AQAcert.log file when running in parallel), expected later this week.


WAMP server stops responding after a while

Maybe this issue is related to this crate too?
https://github.com/dyule/wamp-rs/issues/5
Not sure if the cause is in mio or ws-rs or wamp-rs but I'm trying to figure it out..

I'm not sure what the relevant action is here, so I'm going to close the issue. If you have a minimal failing test case illustrating a bug w/ Mio, please create a new issue and include the test case.


'add-on appears to be corrupt'

After downloading the xpi, it fails to install, and firefox pops up '...add-on... appears to be corrupt'. The problem persists across firefox and chromium, on two different laptops. I'm running linux mint 20.2. Sorry, I don't know how to include a support log ID.
Alongside a description of your problem/question/feature suggestion, please also include a support log ID for this.

https://retorque.re/zotero-better-bibtex/support/faq/#add-on-could-not-be-installed-because-it-appears-to-be-corrupt

Thank you, my bad for not checking the faq. Sorted now.

no problem


libsForQt5.kimageformats: fix CVE-2021-36083

Motivation for this change
Fix CVE-2021-36083.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase 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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review run on x86_64-linux 1

1 package marked as broken and skipped:

libsForQt512.kimageformats

3 packages built:

libsForQt5.kimageformats
libsForQt514.kimageformats
photoqt

Result of nixpkgs-review pr 130115 at d860d5e8 run on x86_64-linux 1

1 package failed to build:

libsForQt512.kimageformats

3 packages built successfully:

libsForQt5.kimageformats (libsForQt515.kimageformats ,plasma5Packages.kimageformats)
libsForQt514.kimageformats
photoqt

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.


Relax constraint on dune to support dune 3

The project seems to build fine on my machine with dune 3. I had some test failures that seemed unrelated (incompatible grep CLI used in cram tests)

It's entirely possible. I added this upper bound a little while ago when some dependencies would not build with dune 3.


Add typings for AROptions & Echo flags

Paired on this with @brainbicycle during knowledge share 🎓

Awesome stuff, thanks to you both!


Removed test dependencies outside of Pkg.build.

Not setting PLAYGROUND_INSTALL before Pkg.build would cause tests to fail on a clean environment.
Tests shouldn't depend on having all possible shells installed.

Codecov Report

Merging #72 into master will decrease coverage by 6.83%.
The diff coverage is 85.71%.

@@            Coverage Diff             @@
##           master      #72      +/-   ##
==========================================
- Coverage   91.64%   84.81%   -6.84%
==========================================
  Files          17       17
  Lines         455      461       +6
==========================================
- Hits          417      391      -26
- Misses         38       70      +32


Reolink Duo 2 is only a single "lens" stream

Describe the bug
I believe the duo 2 is being incorrectly polled for two lenses per stream. Unlike the duo (1) the duo 2 is a stitched image and cannot be viewed as a left and right stream. There is simply a main and sub stream, no lens 1 or 2 streams.
I think this is the cause of the below errors.
The RTSP error is also related as its looking at a url that doesnt exist. Preview_02.
The GetEnc error is occuring despite me disabling all streams in the integration. (I do not want to view the streams as i have frigate for this, I only want the other entities for use in automations (lights, motion sensors etc) Hope this is an acceptable use case.
Source: components/reolink/host.py:193
First occurred: 19:55:25 (10 occurrences)
Last logged: 20:04:25

Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1

2023-04-10 19:53:25.591 ERROR (MainThread) [reolink_aio.api] Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1
2023-04-10 19:54:25.565 ERROR (MainThread) [reolink_aio.api] Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1
2023-04-10 19:55:25.567 ERROR (MainThread) [reolink_aio.api] Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1
2023-04-10 19:56:25.611 ERROR (MainThread) [reolink_aio.api] Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1
2023-04-10 19:57:25.572 ERROR (MainThread) [reolink_aio.api] Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1
2023-04-10 19:58:25.634 ERROR (MainThread) [reolink_aio.api] Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1
2023-04-10 19:59:25.605 ERROR (MainThread) [reolink_aio.api] Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1
2023-04-10 19:59:52.432 ERROR (stream_worker) [homeassistant.components.stream.stream.camera.front_sub_lens_1] Error from stream worker: Error opening stream (HTTP_NOT_FOUND, Server returned 404 Not Found) rtsp://****:****@<IP_ADDRESS>:554/h264Preview_02_sub
2023-04-10 20:00:25.617 ERROR (MainThread) [reolink_aio.api] Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1
2023-04-10 20:01:25.564 ERROR (MainThread) [reolink_aio.api] Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1
2023-04-10 20:02:25.625 ERROR (MainThread) [reolink_aio.api] Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1
2023-04-10 20:03:25.607 ERROR (MainThread) [reolink_aio.api] Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1
2023-04-10 20:04:25.628 ERROR (MainThread) [reolink_aio.api] Host <IP_ADDRESS>:443: command GetEnc response channel 0 does not equal requested channel 1

To Reproduce
Add reolink duo 2 poe to the HA integration.
Expected behavior
No errors
Screenshots

Environment:
No NVR other than frigate. Reolink Duo 2 Poe
Model
Reolink Duo 2 PoE
UID
95270004FG80D5TV
Build No.
build 23031700
Hardware No.
IPC_529B17B8MP
Config Version
v<IP_ADDRESS>
Firmware Version
v<IP_ADDRESS>9_23031700
Details
IPC_529B17B8MPS10E1W01100000001

Additional context
Add any other context about the problem here.

This commit should resolve the issue: https://github.com/starkillerOG/reolink_aio/commit/130fb099b74076c260c09f746bffebeb1f98cbfa.
I will publish a new reolink-aio version within a few days and bump the HomeAssistant dependancy.
After that is schould be fixed in a patch release of HomeAssistant.
I will let you know when the fix is available in HomeAssistant.

If you appreciate the reolink integration and want to support its development, please consider sponsering the upstream library.


Possible error in VCF reader (dev branch)

Shouldn't there be an else statement at line 130 in seqdata/_io/readers/vcf.py (dev branch)?

Thanks for the catch! Fixed in b4ea3f6.


field_evaluation/grid_test9.py grid hierarchy not working

grid hierarchy is not not working
examples/grids_tutorial/field_evaluation/grid_test9.py

We would need a AgGrid enterprise key to test this example

Or remove the example if it doesn't work without an enterprise key.

see #685


Fix incorrect check for "$NVM_DIR/nvm.sh"

Should be using -f if checking for a file.

This appears to be failing every "without curl" installation test.

That's odd. Though I'm pretty sure those failures have nothing to do with this 1-liner, seeing as how it's an isolated if/else where echo is the only thing performed.
-  if [ -d "$NVM_DIR/nvm.sh" ]; then
+  if [ -f "$NVM_DIR/nvm.sh" ]; then
     echo "=> nvm is already installed in $NVM_DIR, trying to update the script"
   else
     echo "=> Downloading nvm as script to '$NVM_DIR'"
   fi

That is a very good point.

Oh, hey- my bad. Sorry I didn't see the rest of your comment requesting a rebase. Thanks for taking care of this!


README updated

@Soumirai @SJD1882 @MoonBiz @bodinierthomas @olpig @MaximeBo @marcellomak @thofour @Yinglr @Arthurim
I've added a link to the slides in the README, and a short cheatsheet for command lines.
I've also created a gitter channel, you can join and ask questions whenever you want if you're stuck.
Could you please forward to students not in this list?  It would be nice that they post a reply here so I know everyone's github account.

For Windows users, once you've installed Visual Studio, search for "Outils Natifs" in the search bar or in the Windows Menu (under the Visual Studio folder) and launch it.
Then type cl.exe to see if it can find the compiler. If you get an error message "cannot find cl.exe" or "cl.exe is not a valid command", something is wrong. Let us know so we can help you fixing it before next the course.


[WIP] New gh-pages website

This is a new gh-pages website.
Live demo can be found https://matthewma7.github.io/geojs/
This is paired with the changes on this branch https://github.com/OpenGeoscience/geojs/tree/website_examples
I started with as gh-pages supported Jekyll project but later found out the existing custom site generating with pug/jade. The previous building is still needed, but it is used for building individual example pages only. So, the ph-pages site building involves two different technology at this moment.
(All old example url should still work)
To build or the develop the website, follow the steps in the readme file.
There are tasks needs to be completed before merging this PR. (publish the website)
Below are the items I can think of. More items are welcomed.  Once related information is gathered, I can make the changes or changes can be committed directly to this branch.

Fill all text placeholder

The highlight section of the welcome page
The description in "get started" section
Example and tutorial page description

Review all text content
Determine the order of examples
There is a requirement that we want to order the examples not just alphabetically, now the order is controlled by the https://github.com/OpenGeoscience/geojs/blob/website/_data/examples.yml file, it also controls what shows on the examples page.
Review the download page
https://matthewma7.github.io/geojs/download
I put together an initial download page, but because my unfamiliarity with GeoJS, the content of the page needs to be reviewed. Especially, the part about geo.js and geo.ext.js.
The two WMS examples need to be updated. It seems there is a CORS issue with the WMS server.
Potentially update the jsdocs template to follow the new website design
We want to have some tutorials, the website has a placeholder for them, but the tutorials are pending implementation.

@aashish24 @manthey This PR is the website itself.
I put in the changes we talked about earlier. I didn't get the landing page logo transition animation working right, so the implement is a basic transition effect.
@aashish24, You could add content to this branch directly. I have invited you both as collaborate of my repo https://github.com/matthewma7/geojs, so you should be able to push to its master branch to view changes.

okay thanks @matthewma7

Initial set of tutorial added

In the title bar, the Hub, in GitHub should be capitalized.


opnode,l2os: Better lifecycle management

Description
This changes the order of shutdowns to be correct (rollup nodes prior to clients) as well as making sure that all ethclients are shut down.
Metadata
Fixes https://github.com/ethereum-optimism/optimistic-specs/pull/319

Not 100% sure of the whole codebase in depth to know if anything is missing but this generally looks good to me

Codecov Report

Merging #358 (e0d77ce) into main (72d6735) will increase coverage by 0.60%.
The diff coverage is 73.85%.

:exclamation: Current head e0d77ce differs from pull request most recent head f202db1. Consider uploading reports for the commit f202db1 to get more accurate results

@@            Coverage Diff             @@
##             main     #358      +/-   ##
==========================================
+ Coverage   55.76%   56.36%   +0.60%
==========================================
  Files          46       46
  Lines        3967     3896      -71
==========================================
- Hits         2212     2196      -16
+ Misses       1491     1446      -45
+ Partials      264      254      -10

Impacted Files
Coverage Δ

opnode/test/setup.go
77.82% <65.11%> (ø)

opnode/node/node.go
71.06% <66.66%> (-0.77%)
:arrow_down:

opnode/test/geth.go
60.49% <76.59%> (ø)

opnode/internal/testutils/fake_chain.go
79.13% <94.73%> (ø)

l2os/service.go
77.02% <100.00%> (-1.64%)
:arrow_down:

opnode/l1/request_sema.go
100.00% <100.00%> (ø)

opnode/rollup/driver/state.go
68.88% <100.00%> (+0.34%)
:arrow_up:

opnode/rollup/derive/invert.go
68.42% <0.00%> (-31.58%)
:arrow_down:

opnode/internal/testlog/testlog.go
67.69% <0.00%> (-9.24%)
:arrow_down:

... and 8 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 72d6735...f202db1. Read the comment docs.

OK to merge, failing tests are related to an unrelated issue.


"events" method does not return events "description" for recurring events

The events method of the icalevents class does not return the "description" parameter of events for occurences of a recurring event.
See attached files:
1/ The calendar
2/ The code used for testing
3/ The output of the code
MyCal1.txt
essai2.txt
output2.txt

Glad you mentioned that. The description is lost when creating recurring copies of the master event. An additional line in the copy_to method did fix it for me.

Doesn't 8572fafa15eb3fff4a1ae1971205d98f0a910bc4 fix it?

should be fixed, closing old issue


Antennas

update homepage
update license

https://forum.kerbalspaceprogram.com/index.php?/topic/207329-1123antennas-ants-v14990-adoption-17-mar-2022/

https://spacedock.info/mod/98

https://forum.kerbalspaceprogram.com/index.php?/topic/113109-112antennas-additional-antennas-for-remote-tech-telemachus-and-antenna-rangev1412-may-16/

I assume the license change has been explicitly allowed by the original author? Because it was CC-BY-NC-SA-4.0, now it is CC-BY-SA-4.0. And the SA part of the license means it must be kept the same (only the original copyright holder can change it).
Also are you sure about "ksp_version_min": "1.0.0"? That's a very broad range.

all is good. why the hold up on all my addon listings? starting to feel very subjectively personal.

Did you not read my comment?

Did you not read my comment?

did you not read mine?

that is what I thought. a personal attack.

Are you a lawyer? Admitted to a Bar Association somewhere? @DasSkelett
Cannot index it on ckan? because the license changed? That is certainly going to break games.
While I appreciate the whole CKAN thing, I do not appreciate the harassments and discrimination.
I don't do things I don't have the legal authority to do.
So kindly update and unfreeze this.

You can direct message me on the forums, the username is obvious.


Core clr platform detection

I have kept the current behavior that Linux and Mac are seen as Unix based runtimes.

Thanks!

Ignore the Travis errors. Couldn't get Travis running with dotnet

Good change!


ViewAlias is not working with ornament views on visionOS

the default body is always used.
struct SomeAlias: ViewAlias {

    var defaultBody: some View {
        Text("Not working 🥲")
    }
}

struct ContentView: View {
    var body: some View {
        ZStack {
            Text("Test")
                .ornament(attachmentAnchor: .scene(.bottom)) {
                    SomeAlias()
                }
        }
        .viewAlias(SomeAlias.self) {
            Text("It works! 😎")
        }
    }

Thanks for you reply.
Any chance we can implement a ViewAlias reader to read the view from AttributeGraph and used manually like below?
struct ContentView: View {
    var body: some View {
        ZStack {
            ViewAliasReader(SomeAlias.self) { view in
                Text("Test")
                    .ornament(attachmentAnchor: .scene(.bottom)) {
                        view
                    }
            }
        }
        .viewAlias(SomeAlias.self) {
            Text("It works! 😎")
        }
    }
}

Unfortunately a ViewAliasReader is not possible, I did attempt such a workaround.


Use 2xlarge resource for CircleCI

Test for 2xlarge resource

Nope. We are not approved:

Resource class 2xlarge for docker is not available for your project. This message will often appear if the pricing plan for this project does not support 2xlarge use. Default class medium will be used. Please contact your CSM person or our support team to whitelist your project.

Closing!


Rename methods

For example, load_from_vl_json should be load_query_from_json

Rename class static methods for Task, Query, and Data:
load_from_vl_json ==> load_from_json
load_from_vl_obj  ==> load_from_obj.


Dropout in SwinTransformer unable to set training=False

🐛 Describe the bug
https://github.com/pytorch/vision/blob/93df9a50885d0345e31bba691576c83d5cee7737/torchvision/models/swin_transformer.py#L209-L214
training argument is not used here, so training=True (by default) even when model.training=False.
Versions
Collecting environment information...
PyTorch version: 1.13.1+cu117
Is debug build: False
CUDA used to build PyTorch: 11.7
ROCM used to build PyTorch: N/A
OS: Ubuntu 22.04.1 LTS (x86_64)
GCC version: (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Clang version: Could not collect
CMake version: version 3.22.4
Libc version: glibc-2.35
Python version: 3.10.6 (main, Nov 14 2022, 16:10:14) [GCC 11.3.0] (64-bit runtime)
Python platform: Linux-5.15.0-56-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 3070 Ti
Nvidia driver version: 525.60.13
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.7.0
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.7.0
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
Versions of relevant libraries:
[pip3] numpy==1.24.1
[pip3] torch==1.13.1
[pip3] torchaudio==0.13.1
[pip3] torchtext==0.14.1
[pip3] torchvision==0.14.1
[conda] Could not collect

Hi @nagadomi ,
I'm not sure I understand what the problem might be.
(Is the model.training = True pattern related to tensorflow?)
I'll assume that you're worried about the fact that dropout will always be applied, even during eval: that's won't be a problem as long as you call model.eval() when you're not training.

model.eval() sets self.training=False, but the above code does not use that flag in forward() path, so F.dropout() is not in eval mode, I think.
The code below is a proper code in my opinion.
diff --git a/torchvision/models/swin_transformer.py b/torchvision/models/swin_transformer.py
index 0d3ab9ad32..c0d107facb 100644
--- a/torchvision/models/swin_transformer.py
+++ b/torchvision/models/swin_transformer.py
@@ -126,6 +126,7 @@ def shifted_window_attention(
     qkv_bias: Optional[Tensor] = None,
     proj_bias: Optional[Tensor] = None,
     logit_scale: Optional[torch.Tensor] = None,
+    training: bool = True,
 ):
     """
     Window based multi-head self attention (W-MSA) module with relative position bias.
@@ -207,11 +208,11 @@ def shifted_window_attention(
         attn = attn.view(-1, num_heads, x.size(1), x.size(1))

     attn = F.softmax(attn, dim=-1)
-    attn = F.dropout(attn, p=attention_dropout)
+    attn = F.dropout(attn, p=attention_dropout, training=training)

     x = attn.matmul(v).transpose(1, 2).reshape(x.size(0), x.size(1), C)
     x = F.linear(x, proj_weight, proj_bias)
-    x = F.dropout(x, p=dropout)
+    x = F.dropout(x, p=dropout, training=training)

     # reverse windows
     x = x.view(B, pad_H // window_size[0], pad_W // window_size[1], window_size[0], window_size[1], C)
@@ -306,6 +307,7 @@ class ShiftedWindowAttention(nn.Module):
             dropout=self.dropout,
             qkv_bias=self.qkv.bias,
             proj_bias=self.proj.bias,
+            training=self.training,
         )

Thanks for correcting me @nagadomi , you're right!
Would you like to submit a PR with your proposed fix?
One minor positive note here is that all the Swin transformers where trained with the default dropout=0, so this bug isn't affecting the accuracy of our current pre-trained weights (and so we don't need to re-train all these models).

I am not familiar with the manner of this codebase.
I would be glad to have this problem fixed by a maintainer.

I found this issue when I tried to export my trained model to ONNX.
The model is exported in training mode due to training=True of F.dropout.

Ok Let me check this. I will submit a PR for this.

Thanks @oke-aditya , looking forward for your PR!

Extremely sorry for the delay. 2023 has come really hard here. Lot of unplanned events occurring.
So, coming back to this. I did validate that self.training needs to be set when we are using F.dropout. While if we use nn.Dropout PyTorch automatically sets these parameters based on the model.eval()
I also validated that our codebase in general uses nn.Dropout and only a few cases uses F.dropout where self.training was set to correctly. Hence this problem had not occurred before for all the models.
Since I remember adding the code for SwinTransformer3d (unreleased before 0.15) the bug had propelled there too. I am fixing that as well :smile:
Reference
https://stackoverflow.com/questions/53419474/pytorch-nn-dropout-vs-f-dropout


Skip copying of android.jar if it is the same on build

currently android.jar is always copied to project/lib dir on build even if it is the same

This is part of this task and will be completed with it #86

Ignored cause no better solution found


don't send "did rename" if the title didn't change

We can spare the client from figuring out if users double-clicked a tab and then just clicked away this way.

Closed by 87eade29bdbdf17069f1630d7b7c12a28e4a463e


Need to figure out exactly why we have failed txs on GnosisHubConnector

Describe the bug
We have several failed txs on GnosisHubConnector which costed about $20.
The reason why it happened is because the root has been processed already.
IMO, it estimates gas before submitting a tx through the relayer. Gas estimation doesn't work properly???
We might need to dig into this so we will not lose tx fee for failed txs.
To Reproduce

this was the closed thread https://discord.com/channels/992549151134982234/1065341508330459246

gnosis hub connector with failed txs: https://etherscan.io/address/0x245F757d660C3ec65416168690431076d58d6413

looks like it's already relayed message hash:

tenderly link: https://dashboard.tenderly.co/tx/mainnet/0x04f413043890022a59f6e1df04a852c0cdeded169e3a2a34135bf3399893635c/debugger?trace=<IP_ADDRESS>.3

Going to close this for now, this was likely due to the issue Gnosis reported with their AMB.


WIP Smtp authentication

An attempt to resolve #735

Pull Request Test Coverage Report for Build 2150

0 of 36 (0.0%)  changed or added relevant lines in 6 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 52.14%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/pipeline/Launcher.java
0
4
0.0%

repairnator/repairnator-realtime/src/main/java/fr/inria/spirals/repairnator/realtime/RTLauncher.java
0
4
0.0%

repairnator/repairnator-scanner/src/main/java/fr/inria/spirals/repairnator/scanner/Launcher.java
0
4
0.0%

repairnator/repairnator-core/src/main/java/fr/inria/spirals/repairnator/notifier/engines/EmailNotifierEngine.java
0
5
0.0%

repairnator/repairnator-core/src/main/java/fr/inria/spirals/repairnator/config/RepairnatorConfig.java
0
6
0.0%

repairnator/repairnator-core/src/main/java/fr/inria/spirals/repairnator/LauncherUtils.java
0
13
0.0%

Files with Coverage Reduction
New Missed Lines
%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/pipeline/Launcher.java
1
0.0%

Totals

Change from base Build 2139:
-0.3%

Covered Lines:
2753

Relevant Lines:
5280

💛  - Coveralls


Update uv actiona and pin uv version to 0.5.11

Remember to remove the pinned version once this issue: https://github.com/astral-sh/uv/issues/10183 is resolved.


Lot of mess to clean up

Platform: IBM Cloud Private
# helm version --tls
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1+icp", GitCommit:"843201eceab24e7102ebb87cb00d82bc973d84a7", GitTreeState:"clean"}

kubectl version
# kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.1", GitCommit:"b1b29978270dc22fecc592ac55d903350454310a", GitTreeState:"clean", BuildDate:"2018-07-17T18:53:20Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.1+icp-ee", GitCommit:"5803c3b1f9422c43a963e0610b3a4cad565e127e", GitTreeState:"clean", BuildDate:"2018-09-04T09:29:02Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

I am trying to install a big chart. The command is:
helm upgrade --tls --install --force --timeout=600 --namespace=metoo -f metoo.yaml metoo metoo.tgz

The problem is that it fails and the chart is not created in any failed state with a result that lots of orphan artifacts are created, which I have to clean-up manually. The problem is that it starts 100s of PVCc creation and those I have to delete manually and as we all know Gluster / Heketi are very sensitive and I need to spend more than 30 minutes to clean them. Start the install again and then it fails.
I thought that the --force is supposed to remove orphan objects this does not seem to be the case.
For example: I cleaned all orphan and I get the error:
helm upgrade --tls --install --force --timeout=600 --namespace=metoo -f metoo.yaml metoo metoo.tgz
Release "metoo" does not exist. Installing it now.
Error: release metoo failed: clusterroles.rbac.authorization.k8s.io "metoo-role" already exists

I am looking for this --force which is like a cop who does nothing. How can I make to work?

Hey, I can't seem to verify that the version of Tiller you're testing came from something we support. From your helm version output, I see this:
Server: &version.Version{SemVer:"v2.9.1+icp", GitCommit:"843201eceab24e7102ebb87cb00d82bc973d84a7", GitTreeState:"clean"}

And I can't find any information on commit 843201eceab24e7102ebb87cb00d82bc973d84a7, and v2.9.1+icp seems like there's custom build metadata so I'm assuming this is a private fork of Helm from IBM Private Cloud. Because it's a fork, we can't really help you out here with specific questions.
Can you please try again with an official release of Tiller?
To answer your particular question:

I thought that the --force is supposed to remove orphan objects this does not seem to be the case.

If this is the first time a release is being installed (as shown in your output), it will not delete resources that are not under Tiller's control. If an upgrade fails, however, it will delete those resources.
This was an intentional design decision where we did not want Tiller to take ownership of resources it did not create. After a resource has been created through a release, Tiller assumes ownership over the object and upgrades it accordingly.

closing as intended via https://github.com/helm/helm/issues/4423#issuecomment-410402213

Thank you for the explanation. It helps to know why it was not deleting. One thing that I was observing that when helm upgrade --tls --install failed (the chart is really big), the objects that it created - they did not get reused with --force even though they were created by the tiller. That is where the time was spent in manual clean-up and especially PVCs - that is the painful part - just to make sure that Gluster / Heketi are still happy. But that is OK - lots of thoughts much have gone into the design.
Finally - after I deleted every objects (that I did not know before like role, cluster binding etc.), - the chart finally did not complain for any existing objects but it did not succeed. The objects are being created and I do not see chart release in helm ls --tls. This was the output -
# helm upgrade --tls --install --force --timeout=600 --namespace=metoo --version 2.7.3 -f metoo.yaml metoo metoo.tgz
Release "metoo" does not exist. Installing it now.
NAME:   metoo
E0919 15:36:20.949488   28890 portforward.go:303] error copying from remote stream to local connection: readfrom tcp4 <IP_ADDRESS>:38069-><IP_ADDRESS>:37560: write tcp4 <IP_ADDRESS>:38069-><IP_ADDRESS>:37560: write: broken pipe
Error: getting deployed release "metoo": release: "metoo" not found

But the installation is going on - it takes several hours to complete.
I guess that since this is the private fork - so you may not have an answer. I will circle back with the folks in IBM. Thank you being very responsive.


Invalid invitation

If I invite a user who has not signed up yet, they get an email okay.
Then I go and follow the link, and I am brought to a login form. I go and register and once I have done everything (signed charter, filled out profile), I revisit the invite link but get an invalid invitation.
Makes sense that this works for newly registered users as well as existing.

Requested by myself

Bug still present, had the exact same issue. Is it linked to the fact I didnt use the same email address?

Will test if it is due to using a different email address.

Confirmed this was the issue - @Aryess got an invite sent to email A, but had already created an account with email B, and then invite did not work.
This seems to be a big blocker for people signing up so it is high priority now.

Just received an invite on the same email address I used to register, and it worked. So it's definitly linked to the email address

The reason we did it this way was for security reasons, and it was suggested that we make the hash limited (expire in 2-3 days) rather than restricted by email.
I'd tend to agree with this... Adding the "request for comments" label as I'd like to hear other views.

We just had another complaint that the invite didn't work for someone who wanted to sign up with a different email address.

Same issue on events

We had the same issue when our mentors registered with all lowercase emails<EMAIL_ADDRESS>and we invited them with emails that contained an uppercase letter<EMAIL_ADDRESS>

We can technically convert all email addresses to lower case before sending
invites but I wouldn't recommend this as some email providers would see the
email as two separate addresses. See
https://github.com/CoderDojo/community-platform/issues/625 for more info
On Monday, December 14, 2015, lochlannach-beag<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

We had the same issue when our mentors registered with all lowercase
emails<EMAIL_ADDRESS>and we invited them with emails that contained
an uppercase letter<EMAIL_ADDRESS>—
Reply to this email directly or view it on GitHub
https://github.com/CoderDojo/community-platform/issues/440#issuecomment-164383464
.

--
Ursula Clarke Everett
Technical Lead @ CoderDojo Foundation
S: tangentfairy | T: @CoderDojo | @tangentfairy
--
Volunteer at your local Dojo and inspire the next generation of digital
creators!

Pledge to start a Dojo https://coderdojo.com/pledge-a-dojo/
How to volunteer at your local CoderDojo
https://coderdojo.com/get-involved/volunteer/
Read the CoderDojo Foundation Strategy
https://coderdojo.com/news/2015/08/07/the-coderdojo-foundation-strategy-20152016/

--
Hello World Foundation operating as the CoderDojo Foundation is a company
limited by guarantee not having a share capital with charitable status, CHY
20812. Registered in Dublin, Ireland, No 524255. Registered Office:
Dogpatch Labs, Unit 1, CHQ Building, Custom House Quay, Dublin 1, Ireland.

I think the issue is kinda different : it seems the token are consumed even when you're not the right user. I've ran into it this week with dojo invitation

@Wardormeur is this still a bug/issue or have we done anything about it since you encountered?

Nothing that I remember, may still be an issue.


General Accounting Unit Customizable Rollups Reset to 0 If Subsequent GAUs Have Allocations Only Tied to Non-Opportunities

Issue
Running the Customizable Rollups batch job for General Accounting Units (CRLP_GAU_BATCH) via the nightly scheduled job or the Bulk Data Process may zero out the rollup fields on a General Accounting Unit depending on the order of how it falls within the batch execution and what types of Allocations are associated with the GAUs following it. These records do calculate properly if a customer clicks the Recalculate Rollups button on an affected record.
Root Cause
Customizable Rollups for GAUs are always processed in Skew Mode via the Skew Dispatcher (which gathers GAUs, 300 at a time by default) and CRLP_GAU_BATCH (which then processes those 300 GAUs’ Allocations, 1000 at a time), which work in tandem until there are no more GAUs to process. When CRLP_GAU_BATCH executes over the Allocations, there’s no guarantee that all of a GAU’s Allocations are processed in the same execution. They may span multiple executions of the batch. So, we save the rollup values for the first and lastId processed in a batch execution and commit any updates in the finish() method of the batch, where all of their Allocations should have been processed at that point.
When we call saveFirstAndLastParentIdData() in CRLP_Batch_Base_Skew, we pass in the batch execution’s firstParentId and lastParentId and then we get the lastParentIdProcessed from CRLP_Processor.getLastParentIdProcessed(). If the last GAU Id in the batch had Allocations tied to Opportunities, the lastParentId should match the lastParentIdProcessed. In that case, we update the stateful values for the first/last GAU and commit the data in the finish() method. The issue occurs when the last GAU in the batch only has Allocations that are tied to non-Opportunities (i.e. Campaigns, Recurring Donations, Payments). In that case, we don’t set the lastParentIdProcessed to that final GAU. So, we hit the 3rd if() block in saveFirstAndLastParentIdData():
if (lastParentIdProcessed != lastParentId && lastParentIdProcessed != null && 	processor.getRollupDefsForParent(lastParentIdProcessed) != null) {
            updateStatefulCollections(processor, lastParentIdProcessed);
}

processor.getRollupDefsForParent() does not return null because it looks for that Id in rollupsDefsByParentId. If it doesn’t find it, it instantiates a whole new List<CRLP_Rollup> for that ID (i.e. all 0s and blanks). So the stateful collection for that middle GAU now includes all 0s/blanks.
Steps to Repeat
I will try to create a Snowfakery file that does all of this for you… but batch order is not guaranteed.

Create 10 General Accounting Units
Create 10 Accounts
Create a Campaign
Go to NPSP Settings and enable Customizable Rollups.
In NPSP Settings —> Bulk Data Processes —> Batch Process Settings, set the GAU Batch Size to 10 (mainly so that we don’t have to create thousands of records as test data).
This is where things get tricky… order is not guaranteed in a batch job. You need to create enough Opportunities (Closed Won) that have GAU Allocations of 100% the Opportunity Amount that one batch execution of CRLP_GAU has at least 3 GAUs being processed. To determine which GAUs are being captured in which batch execution, run the Rollup Allocations Batch in NPSP Settings and then you’ll need to download the debug logs, open them in VS Code and search for the following string:
[440]|parentId|"a0d
[note, the 3 characters at the end of that string represent the first 3 characters of the GAU object. I’ve seen it vary widely in orgs, so verify what yours is before doing the search]
Confirm all rollup values are correct on your GAUs.
Once you’ve created enough Allocations so that the batch has at least 3 GAUs, switch the Allocations for the GAU immediately following that middle GAU so that they are no longer associated with Opportunities and are instead associated with Campaigns.
For good measure, set all the values of the middle GAU to a negative number (i.e. -1 or -$1). Leave the dates blank.
Go to NPSP Settings —> Bulk Data Processes —> Rollup Allocations Batch.
When the job finishes, navigate to the GAU record for the middle GAU. Its rollup values will be reset to 0. (Clicking Recalculate Rollups will bring the correct values back).

Workaround
Clicking on the Recalculate Rollups button of an affected General Accounting Unit will reset the rollup fields to their correct values. However, they may be reset to 0s or blanks when the nightly job runs.

W-8818353

W-8818353


Start shared containers in beforeAll callback (Jupiter)

I've probably missed some edge cases, but all current tests are green.
We also explicitly don't support parallel test execution at this point.
Fixes #1019.

I took the freedom to have a look at the extensions. Reads good from my point of view.
What I didn't try out: How is the behaviour in regard to AfterAll? The closing of the containers is left to JUnit itself, right?
I probably would expect the container still being running in "my" after all methods.

So we are storing all containers inside the ExtensionContext.Store and wrap them in a CloseableResource, so Jupiter will stop them automatically.
Not really sure about the specific point in time this will occur though.

@jrehwaldt Thanks, sounds great.
I'll ping the others for having a look at it and then we can probably merge it.

@bsideup Yeah, I will add another ignored test and check it by hand.

So I don't really know a way to force the exception, I kind of think, it can't happen for a user.
I tried to following code:
class WrongExtensionUsageTests {

    @Testcontainers
    enum myEnum {
        FOOBAR
    }

    @Test
    void extension_throws_exception() {
        assert true;
    }

}

This won't execute the TestcontainersExtension class, I wonder why?

Released in 1.10.4!


bitcoin core dont install because  sha 256 doesnt matches

The pgp key that will be used to verify the SHA256 file list is:
            Michael Ford: E777299FC265DD04793070EB944D35F9AC3DB76A

but I get:33930d432593e49d58a9bff4c30078823e9af5d98594d2935862788ce8a20aec
the pharmanode says : Please wait a moment for gpg verification...
gpg: key 944D35F9AC3DB76A: 2 duplicate signatures removed
gpg: 944D35F9AC3DB76A key: "Michael Ford (bitcoin-otc<EMAIL_ADDRESS>no change
gpg: Total amount processed: 1
gpg:no change:1
GPG verification failed. aborting.

Hmm, thanks for that.
I'll have to investigate.
There might have been an update to the download file or signature file.
What computer and OS are you using?
Arman
On Sun, 9 July 2023, 6:49 pm miguepollo, @.***> wrote:

The pgp key that will be used to verify the SHA256 file list is:
        Michael Ford: E777299FC265DD04793070EB944D35F9AC3DB76A

but I get:33930d432593e49d58a9bff4c30078823e9af5d98594d2935862788ce8a20aec
the pharmanode says : Please wait a moment for gpg verification...
gpg: key 944D35F9AC3DB76A: 2 duplicate signatures removed
gpg: 944D35F9AC3DB76A key: "Michael Ford (bitcoin-otc) @.***"
no change
gpg: Total amount processed: 1
gpg:no change:1
GPG verification failed. aborting.
—
Reply to this email directly, view it on GitHub
https://github.com/ArmanTheParman/Parmanode/issues/20, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASQCCXYQDX2HVTIZ7RV5ZNTXPJWA3ANCNFSM6AAAAAA2DLVAJA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I installed bitcoin fine on my computer.
But I did make some small edits to the code.
Can you try again?
Arman
On Sun, 9 July 2023, 6:49 pm miguepollo, @.***> wrote:

The pgp key that will be used to verify the SHA256 file list is:
        Michael Ford: E777299FC265DD04793070EB944D35F9AC3DB76A

but I get:33930d432593e49d58a9bff4c30078823e9af5d98594d2935862788ce8a20aec
the pharmanode says : Please wait a moment for gpg verification...
gpg: key 944D35F9AC3DB76A: 2 duplicate signatures removed
gpg: 944D35F9AC3DB76A key: "Michael Ford (bitcoin-otc) @.***"
no change
gpg: Total amount processed: 1
gpg:no change:1
GPG verification failed. aborting.
—
Reply to this email directly, view it on GitHub
https://github.com/ArmanTheParman/Parmanode/issues/20, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASQCCXYQDX2HVTIZ7RV5ZNTXPJWA3ANCNFSM6AAAAAA2DLVAJA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

0k

i use kubuntu and says me again: Please wait a moment for gpg verification...
gpg: key 944D35F9AC3DB76A: 2 duplicate signatures removed
gpg: 944D35F9AC3DB76A key: "Michael Ford (bitcoin-otc<EMAIL_ADDRESS>no change
gpg: Total amount processed: 1
gpg:no change:1
GPG verification failed. aborting.
Hit  to continue.


[logzio-k8s-telemetry] Migrate from spanmetrics processor to the spanmetrics connector

As of OpenTelemetry Collector 0.74.0, spanmetrics processor was deprecated in favor of the spanmetrics  connector.
The connector simplifies the config by being both an exporter an a receiver.
The latest chart version (0.2.1) for logzio-k8s-telemetry uses OpenTelemetry Collector 0.73.0, so an upgrade would be required.
Links:

Deprecation notice
Connector documentation
Span Metrics Connector documentation

Hi @Matroxt, version 2.2.0+ uses the spanmetrics connector :)


developer installation guide included

Updated installation guide for Ubuntu.

@dankaiser1808 Thanks for the contribution!
Please note that our CI system does some additional style checks on markdown files and failed because of:
The command "(cd docs/guides/user && mkdocs build)" exited with 0.
1.33s$ (cd docs/guides && grunt)
Running "markdownlint:full" (markdownlint) task
Warning:
./developer/docs/installation/source-linux.md: 83: MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 4]
./developer/docs/installation/source-linux.md: 95: MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 4]
./developer/docs/installation/source-linux.md: 86: MD013/line-length Line length [Expected: 120; Actual: 132]
./developer/docs/installation/source-linux.md: 96: MD013/line-length Line length [Expected: 120; Actual: 143]
./developer/docs/installation/source-linux.md: 107: MD013/line-length Line length [Expected: 120; Actual: 173]
 Use --force to continue.
Aborted due to warnings.

Could you please fix those problems?

This page also does not appear to be linked to from the rest of the documentation, making it an orphan.  Don't forget to add the relevant links into it!

@dankaiser1808, thanks for your work so far.  Another suggestion: Add a section on how to work on/build/run the docs.  This is currently filed here.

@dankaiser1808, overall, this looks really good now and I guess we are now mostly nitpicking instead of having real complaints. It would still be nice if you could make a last run through this.
The only real problem is the package-lock.json. @gregorydlogan's suggestion of doing a git rebase would be the best option for this but you will also have to look a bit closer at git magic. Feel free to grab one of the devs at Osna if you want to go that way. If not, just change the file back to what it originally was and we can just squash-merge this. That will work just fine.
About MH-12251, unless you really want to work on it, leave it to your new collegue. That's probably a nice first contribution for him.

Thanks for all your suggestions! :) I will go for the changes today after university.

I'm closing this since Daniel accidentally deleted his fork and cannot update this anymore.
Pull request #542 contains an updated version of this.


feat: optimized env shim & support object.keys

🔗 Linked issue

resolves #118
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

@pi0 how can i help to move this forward ?

Thanks for PR. It looks nice but too many changes in one PR that I need to carefully review. (https://github.com/pi0/tired-maintainer)

@pi0 you are very welcome ☺✌. I know you have much on your plate. This pr is also not urgent. So if I can help you any further or should adjust something, please let me know (ping me).


Web workers cannot have imports or exports without the type: "module" option.

When trying to use the module with Parcel, the compilation fails:
@parcel/transformer-js: Web workers cannot have imports or exports without the `type: "module"` option.

  proj/node_modules/react-py/dist/hooks/usePython.js:80:41
    79 |     var createWorker = function () {
  > 80 |         var worker = new Worker(new URL('../workers/python-worker', import.meta.url));
  >    |                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^ The environment was originally created here
    81 |         workerRef.current = worker;
    82 |     };

  💡 Add {type: 'module'} as a second argument to the Worker constructor.
  📝 Learn more: https://parceljs.org/languages/javascript/#classic-scripts

This is triggered by this import in worker.js:
import { expose } from 'comlink';

Replacing this line with these 2 makes the error go away:
importScripts('https://cdn.jsdelivr.net/npm/comlink@4.3.1/dist/umd/comlink.min.js');
const expose = Comlink.expose;

According to this StackOverflow answer, the {type: 'module'} will soon be accepted by all modern browsers as the second parameter to new Worker(). A (better?) alternative is to configure the builder to inline the comlink dependency.

I've created a minimal reproduction using Parcel and React. Adding the {type: 'module'} argument does not solve this issue and adding Comlink as a cdn should not be necessary, as it is already a dependency of the project.
I'm not sure what you mean by "configure the builder to inline the comlink dependency"? I'll try to look into this further, but if you have any suggestions regarding what I can change in react-py to support your use case, please let me know.

After reviewing related issues on the Parcel repo, it seems that this may be a bug on their end. If you have any additional information or details about this issue that you'd like to share, please do update this issue and let us know.
In the meantime, we will go ahead and close this issue for now. However, please don't hesitate to reach out again if you have any other questions or concerns.


Add --withPermissions option to spo folder get command 🔐

🎯 Aim
The aim is to add --withPermissions option to spo folder get command.
When used CLI should return associated roles and permissions of the file.
🤔 Example
Similar functionality was already developed in  spo list get command so we may use it as an example.
🔍 What might be used to achieve this
list permissions on item level (file, folder)
.../_api/web/lists/getbytitle('test1')/items(1)/RoleAssignments?$expand=Member,RoleDefinitionBindings

Parent issue
#3972

@pnp/cli-for-microsoft-365-maintainers  👉 2x👀🔍🙏

Please assign to me to start working on it.

Please assign to me to start working on it.

All yours 👍💪


Fix ONNX export of stable diffusion models

Solution integrated by @eaidova in https://github.com/huggingface/optimum-intel/pull/342 to fix the ONNX export of stable diffusion models as the aten::scaled_dot_product_attention is not registered for export.  Beforehand the scaled dot-product attention was disabled by default even for torch > v2.0 before exporting the model. See https://github.com/huggingface/diffusers/pull/3273, disabled in https://github.com/huggingface/diffusers/pull/3387

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Input Accessory View is not visible

I have an input accessory view on the center controller that doesn't seem to be on screen.

fixed this by adding the center controller in a navigation controller.


Task/arxivng 138

Added in the user menu and search bar - these are not yet connected to their respective services, to make it more obvious that this requires some code to interface with the classic system.
CSS/sass structure has also been refactored to make better use of the Bulma framework.

Ah nuts, that was supposed to be a request to merge into develop.


ThemeData.operator== didn't check platform

Turns out this is missing the hashCode update.  Lack of something like https://github.com/dart-lang/sdk/issues/26703 is such a footgun, sadly. :/


label-and-name-inputs.html feedback: method=post mention is incorrect

Auto-complete only works when the form method is post.

AFAIK this isn't true.
Forked from internal bug 89647407
We can check with thestig to confirm, but I think this is unnecessary.
@petele

I believe we tested this with a get and it didn't work... Happy to check
again and correct if needed.
On Thu, 26 Mar 2015 23:43 Paul Irish<EMAIL_ADDRESS>wrote:

Auto-complete only works when the form method is post.
AFAIK this isn't true.
Forked from internal bug 89647407
We can check with thestig to confirm, but I think this is unnecessary.
@petele https://github.com/petele
—
Reply to this email directly or view it on GitHub
https://github.com/google/WebFundamentals/issues/1183.

GET forms are probably blacklisted, but a parent form element isn't mandatory.
The internal bug was concerning a form without a form element.

Did a quick test with http://jsbin.com/mufozevami/1/edit?html and it looks like they're not required any more. thanks for the update!

Fixed in a1f0c1fe454691c370e16038858b47921ba86f5a


Test sensitive term index against user reported sensitive media

This is a little experiment I've had in my notes that I am moving here to keep track of. Basically, the idea would be to pull a list of all media which has been reported as sensitive in Openverse and see what % of it is also caught by the sensitive text feature. This could give us a very rough, imperfect estimate of the efficacy of the sensitive text filter at finding sensitive media.

@sarayourfriend I am considering closing this issue on the basis of its lack of usefulness. I wanted to check for your thoughts beforehand since you've thought a far deal about the sensitive indices but also things like result caching and analysis.

I'm fine closing it. For it to be a useful analysis I think we'd want to know which reports were for sensitive textual content, sensitive content in the work itself (image or audio), or both. It's no big surprise if our sensitive text analysis finds works that have sensitive text, so it's more useful and interesting if it's reliably matching sensitive works as well, by some correlative feature of the textual content and the work (which is a fundamental but untested assumption).
It could be interesting, but I think our sensitive text approach is useful even if it only finds sensitive text, so the outcome of this analysis wouldn't necessarily influence whether we continued using this approach, at least from my perspective. It would be a lot of work though.


Major version bump

In the changelog you state: "Note: Going forward, protobuf-ts will bump the major version for all releases that add features. Minor releases will be used for releases that only contain bug fixes.". Why?

Ah, my bad. Looks like I didn't have my coffee when I wrote that note. Thanks for the bringing this up.
In the past, we didn't do minor releases, only patches and major. We added features in patch releases, which should have been minor releases. Going forward, we are going to do minor releases, too. That's it.

Ah, my bad. Looks like I didn't have my coffee when I wrote that note. Thanks for the bringing this up.
In the past, we didn't do minor releases, only patches and major. We added features in patch releases, which should have been minor releases. Going forward, we are going to do minor releases, too. That's it.

Ah, that makes more sense :) Thanks.

Ah, that makes more sense :) Thanks.


Added a C script on single linked list

I've added a simple C script that creates by taking user input and then displays a single linked list.

PR accepted @Praneesh-Sharma
Successfully merged to HacktoberFest_22 repo.
🚀🚀👍


OnClusterClickListener doesn't always work with satellite map

Hello,
I created an OnClusterClickListener for a cluster of size 6. It works fine when the map is on "mapbox_style_satellite_streets" mode. However, when I change the map type to "mapbox_style_satellite", taps on the cluster don't work unless I'm at certain zoom levels (all the way out, and some random levels of zoom in).

Hey @Li-Eric, we are looking into actually deprecating and removing the cluster plugin. See https://github.com/mapbox/mapbox-plugins-android/issues/522 for further explanation. I'd recommend following the same method explained in #518 and for the "onClickListener", using querying map features (explain extensively in this doc). Please drop a comment on #522 if you find any reason for keeping the cluster plugin around.
cc: @zugaldia


Domain activation is Failed - Unable to set up a custom domain

App Id: d21d0l8v98v7tf
Region: ap-south-1
Step: Domain activation
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
I'm unable to setup a custom domain using amplify. I was using the same domain on a different amplify project earlier but have deleted the domain from there

Hi @neildcruz , it seems like you have already deleted this app. Do you still face this issue?

I might have struggled with the same issue. Does https://github.com/aws-amplify/amplify-console/issues/512#issuecomment-639892355 help?

Thanks, was able to resolve this.


feat(sink): set default_sink_decouple = true for all sink

su
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
https://github.com/risingwavelabs/risingwave/issues/17095

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
after this pr,
all sink sink_decouple default is true
And starrocks clickhouse iceberg deltalake 's default commit_checkpoint_interval is 1

Why not change the sink test as well? This PR changes the default behavior of all sinks to decouple. We should make the test compatible with this change. BTW, what if we set sink_decouple = false? It would cause an error
config `commit_checkpoint_interval` larger than 1, which means that sink decouple must be enabled, but session config sink_decouple is disabled.


fix(format-to-jsx): shouldnt format when no args were passed

Formatting function will no longer try to format templates when no arguments were passed to it.
fix #17

Pull Request Test Coverage Report for Build 153

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 149:
0.0%

Covered Lines:
90

Relevant Lines:
90

💛  - Coveralls

:tada: This PR is included in version 1.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


gtest linking warnings with static builds on cray systems

../../lib/libgtest.a(gtest-all.cc.o): In function `testing::internal::StreamingListener::SocketWriter::MakeConnection()':
gtest-all.cc:(.text+0x3af47): warning: Using 'getaddrinfo' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

[  4%] Built target blt_gtest_smoke

On Cray, setting the following env var:
export CRAYPE_LINK_TYPE=dynamic
Eliminates these warnings.
I think this might be a good-enough solution.

It may achieve the same effect, but the wrappers (cc, CC, ftn) also accept a -dynamic flag. It may have an identical effect.

awesome, we can try to provide those as defaults for cray compiler wrappers.  Although I don't think we identify the cray compiler wrappers yet.

Just FYI, Cray typically prefers to compile things statically (in my
experience) so there should probably be some control left to the user as to
whether or not to pass -dynamic
On Wed, Nov 15, 2017 at 5:36 PM Cyrus Harrison<EMAIL_ADDRESS>wrote:

awesome, we can try to provide those as defaults for cray compiler
wrappers. Although I don't think we identify the cray compiler wrappers yet.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/LLNL/blt/issues/94#issuecomment-344776563, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAREPAZ3dLrfoKwPMezHAXGUCg3b4zMDks5s24OPgaJpZM4PeMPl
.

Good point -- these cases are actually where we want to create static libs, but some of the deps (gtest in this case, and things like hdf5 in others) have dlopens, etc that we can't avoid, so we have to link to the shared runtime.
So I agree --  maybe we don't default to adding the flag, but if we could direct the compiler wrappers (or even the just that we are on a cray) it would make it easier for projects to add them when necessary.


MudTable row gap/height too large

Bug type
Component
Component name
MudTable MudTd
What happened?
When used on a mobile phone, the gap between rows is just too large, especially when in portrait mode.
This makes it unusable for LoB apps.
See screenshot:

Expected behavior
Enable full control of the gap - I've tried row-gap (apologies if this is not correct css):
[MudTd Style="row-gap: 0.01em;"<EMAIL_ADDRESS>[MudTd Style="row-gap: 0.01em;"<EMAIL_ADDRESS>[MudTd Style="row-gap: 0.01em;" DataLabel="Delivery<EMAIL_ADDRESS>Preferably enable a simpler row height control mechanism, without having to decode css/Style/Class elements etc.
MudTable is set to "dense" but to no effect.
Breakpoint is Xs.
Reproduction link
https://try.mudblazor.com/snippet/sorry-have-not
Reproduction steps

see screenshot above

...
Relevant log output
No response
Version (bug)
5.2.0
Version (working)
No response
What browsers are you seeing the problem on?
Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Setting the MudTable's RowTemplate MudTd Class (not Style) to Class="mt-n5 ml-n4" reduces the row gap, as per screenshot below.
But, still a problem with width sizing, as can be seen - the negative left margin helps but all of this still feels very hacky.
Would be good to have row gaps and widths automatically sized for Xs breakpoint - and some better guidelines or documentation explaining Style and Class differences, when to use with better examples, etc ...

No snippet provided. If this is still affecting anyone with tables in the latest versions please reply so we can reopen the issue.


Infer as=thrift from endpoint with ::

Allows override for JSON just in case. All other arg schemes are explicit.

r @raynos @ShanniLi @jcorbin

Lgtm


Corrected examples

https://github.com/MicrosoftDocs/office-docs-powershell/issues/4373

Docs Build status updates of commit d3a4226:
:clock10: Full build: the average full build time is 11 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit d3a4226:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Start-SPOSiteContentMove.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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

Docs Build status updates of commit b9c0415:
:clock10: Full build: the average full build time is 11 min(s) 47 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit b9c0415:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Start-SPOSiteContentMove.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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

Docs Build status updates of commit ac9ffac:
:clock10: Full build: the average full build time is 11 min(s) 50 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit ac9ffac:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-online/Start-SPOSiteContentMove.md
:white_check_mark:Succeeded
View (sharepoint-ps)

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


Prevent FullTitle string from being null in StatusCenter.cs

Fix for https://appcenter.ms/orgs/FilesApp/apps/Files/crashes/errors/3768192674u/overview:
StatusCenter_obj17_Bindings.Update_FullTitle (String obj, Int32 phase)
D:\a\1\s\Files\obj\x64\Release\UserControls\StatusCenter.g.cs at 566, line 29
System.ArgumentNullException: Null strings may not be marshaled in Windows Runtime arguments. Parameter name: sourceString

I believe the issue was caused by a null value being passed to AutomationProperties.Name, which binds to FullTitle.

Thanks this issue has been already fixed (FullTitle was not always assigned in the constructor). While this adds a welcome additional check, this would be the only property to be handled like this.. still wondering what's so special about it. Have you experienced this crash with main?

@gave92 Sorry I didn't realize it was already fixed xD.

While this adds a welcome additional check, FullTitle would be the only property to be handled like this.. still wondering what's so special about it.

AutomationProperties.Name for list view items doesn't seem to accept null values, and it binds to FullTitle but not other properties.

Should I close this?

Current fix works "by luck" since currently the status banner is always created with an empty (but not null) title. So this is good to have, thanks @winston-de


New PR to test SignCLA at 2018-03-15 12:29:33.136083764 -0700 PDT m=+5.652562726

Body of PR

indiv-pass-fork-staging: test succeeded


Graphical rendering of file

It would be nice if you could see the result of rendering a file as it happens. To my knowledge only the blender module supports incremental rendering, so that is what this issue is aimed towards. Basically we should emulate the behavior for rendering a blend file normally.

Synfig module also supports incremental rendering. ^__^


Set Up SAP Business Application Studio for Development with 'real' Global Account (no trial)

Tutorials: https://developers.sap.com/tutorials/appstudio-onboarding.html
Hi SAP Team,
while the guide looks great and we already used it for initial testing of BAS in scope of trial, we fail to use it to enable BAS in our company global account. Can you add details for use case with company global account, please? -- Thank you!

Hi,
Thank you for your feedback.
We will look into this and update you as soon as possible.
REgards,
Pao

Hi @abap-weasel ,
I apologize for the late response.
The tutorials are created and maintained with the trial environment in mind.
For productive (enterprise) accounts, one should refer to the product's documentation.
Regards - Raz


Python 3 support

Any plans of porting to python 3?

I would like to know this as well. If not, any actively maintained alternative to this library?

@meequz @manesioz use this fork from @lechup , it works well with python3 !
https://github.com/lechup/imposm-parser/tree/python3

@TimMcCauley will check it out, thanks!

Also, this package is a good, python3 supported alternative

find https://pypi.org/project/osmium/ more performant and supporting user, uid, version, timestamp, changeset attributes


Pitch

Simple elevator pitch, with minimal branding (beta)

what it is
how it differs
vision

Clobbr is a developer tool that allows you to test your api endpoints to see how well they perform under multiple requests (clobber your apis!), in sequence or parallel.
Regardless if you're testing a REST, GraphQL or cloud function Clobbr has got you covered!
Powerful, yet simple and delightful user interface.
• Make requests to multiple endpoints with ease.
• Set up request timeouts, headers, payload and much more
• Explore results as a beautiful list, summarizing your settings
• Analyse charts with response times and easily re-run tests
• Delve into key stats such as standard deviation, percentiles and more
Configure requests.
• Easily configure verb (GET, PUT, POST etc.)
• Set number of iterations
• Toggle between http/s with ease
Send data with a request.
• Set data in the built-in JSON editor
• Include in POST, PUT etc requests
• Save data settings between runs
Set headers with ease.
• Configure headers for each request
• Use scripts to get/set dynamic headers
• Save header settings between runs
Take control of the UI.
• Toggle between light or dark modes
• Clear data with ease
• Customise app behaviour with advanced settings
All data stored locally. Your privacy comes first.
• None of the request or result data is stored on a server
• No account needed
• No tracking whatsoever


An error appeared when running the demo

RuntimeError: Error deserializing object of type int

May I ask what python version you are using? I'm not sure how it's done on windows, but on linux/mac you can run python --version in terminal

Hi codeniko, I have had the same problem. I am currently running python 3.6.5
Thanks for training this model, the forehead landmarks would be really useful to me.
Out of interest, how did you create your training landmarks for the forehead region?

Ok I have managed to solve the problem. I was reading somewhere the error can happen if the file is corrupted. So git cloned the entire repository to get the file rather than downloading the individual file manually. I have no idea why this would make any difference but it seems to have fixed the issue.

If you have a spare moment would be still interested in knowing the answer to my question above:
"Out of interest, how did you create your training landmarks for the forehead region?

Awesome! Not sure why that's the case but happy that it worked


Release the Gallery on the App Store

I've spent some time trying to find it on AppStore and I couldn't. I was following the auto-build process with Fastlane and was pretty sure this was published already.
What's missing here? Can I help somehow?

Does this still a valid issue? it has been three years now without updates on this.
Unless the Gallery app will include more functionalities, right now it may get rejected on App Store accordingly to the guidelines described here: https://developer.apple.com/app-store/review/guidelines/#minimum-functionality.

@pedromassangocode that's right, it was rejected initially, and even after we added functionality (source code viewing, copying, etc.) it was still considered a demo app. As such, closing this issue.


Ignore empty attrs

According to slog-handler-guide, empty attributes should be ignored.

Next, it follows the handler rule that says that empty attributes should be ignored.

Test
using example/example.go
	// ...
	logger := slog.New(slogslack.Option{
		Level:      slog.LevelDebug,
		WebhookURL: webhook,
		Channel:    channel,
		ReplaceAttr: func(groups []string, a slog.Attr) slog.Attr {
			if a.Key == "some_hidden_key" {
				return slog.Attr{}
			}
			return a
		},
	}.NewSlackHandler())
	// ...
	logger.
		// ...
		With("some_hidden_key", "secret").
		Error("A message")

Before
Add an attribute some_hidden_key and modify with ReplaceAttr then it will print <nil>.

After
Now it prints nothing for some_hidden_key.

Hi @SogoKato and thanks for your suggestion.
I think we should implement that in slog-common.

Hi @SogoKato and thanks for your suggestion.
I think we should implement that in slog-common.

Hello @samber !
I will try to work on this.

@SogoKato Can you review it please ?
https://github.com/samber/slog-common/pull/6

@SogoKato Can you review it please ?
samber/slog-common#6

@samber
Thank you for creating a p-r. I've reviewed that and left a comment.
And, I've tested by importing slog-common locally (by adding a line replace github.com/samber/slog-common => ../../../github.com/samber/slog-common), and found it works!
https://github.com/samber/slog-slack/blob/15370ee606485fcdfdd7e8ed05af557976b1cb2e/converter.go#L22
// added this line
attrs = slogcommon.RemoveEmptyAttrs(attrs)

@samber Thank you for releasing v0.17.0 of slog-common. I reverted the previous commit and pushed new commits. Could you review it again?

I just made the update on slog-slack -> v2.6.0


Idea: TanulóSCH integration for Kiosk mode

I do not know if you accept ideas, but I have an idea.
As I understand, Kiosk mode is the whole frontend presented at the ground floor of the dorm. There, the monitor could show open rooms based on TanulóSCH data. It could be presented on a sidebar with just the level numbers on it maybe with a nice icon of tanuló.sch.
3✓
4X
5✓
6✓
etc.
18X
This would popularize tanuló SCH. It would help, because currently it seems to me that it is not famous enough to be used for reserving a room if you have an important meeting or you do not want to be interrupted even with people knocking on the door. (I've had two such meetings in the span of years, but still)
I think ground floor would not be the best place to present this data, but it could be convenient for people who just arrive from the university or shopping.

Great idea, we will look into it. In 3.0 we are planning to add customization functionality where we could remotely change displayed widgets.


WHMCS v7 Support?

Hi guys,
I know that an official Bitpay module for WHMCS v7.1 is in the making.
@pieterpoorthuis once mentioned in another issue that it's due for middle April.
Can we can a status update, please?
We'd love continuing Bitpay as our Bitcoin gateway with WHMCS.
Best wishes,

We've just committed new code that is WHMCS v7 compatible (tested against WHMCS v7.1.2)
You can download the latest code here: https://github.com/bitpay/whmcs-plugin/archive/master.zip
I will create a release next week (provided no issues are found).

@pieterpoorthuis Thanks for the exciting update.

How things looking 6-7 days after? :) Are there any issues found?
Is the plugin also WHMCS v5 compatible of WHMCS v7 only?

Bump for @pieterpoorthuis :)

There were two issues reported around creating invoices (displaying "Invalid invoice id #0"), that I could not reproduce yet.
Therefore I've created a release of the current source. Feedback/issue reports are appreciated.

Thanks, @pieterpoorthuis !

As mentioned in #42 I still experience the "Invalid invoice id #0" issue with the latest plugin version


Cannot successfully access same database with two different system users

If when logged in as user A, I initialize database, and then when I try to connect to same database using user B, no data is propagated, and no error (that would indicate that something went wrong)  is exposed.
How to reproduce:
Try to run below code on database initiated by other user. No logs will be reported, as if operation hanged. Same code will run as expected when run by user which initialized first access.
'use strict';

var level = require('level-party');
var db = level(pathToLevelDbFolder);

var stream = db.createReadStream();
stream.on('data', function () {});
stream.once('error', function (err) {
    console.log("Error", err.stack);
});
stream.once('end', function () {
    console.log("End");
});

Which platform?

Can confirm same issue on node 15.2.1 / ubuntu server 20.04.1. No errors. Switching level-party for level gives the standard LOCK error

Can confirm same issue on node 15.2.1 / ubuntu server 20.04.1. No errors. Switching level-party for level gives the standard LOCK error

Actually it looks like a permissions error, specifically:
Error [OpenError]: IO error: /{path}/LOCK: Permission denied
In my specific scenario I am running a service which creates the original database (as root). I am then attempting to access the database as another user (for manual checkup / data dump). All DB files are created with 0644 permissions. Sudoing the user script works as expected.

Actually it looks like a permissions error, specifically:
Error [OpenError]: IO error: /{path}/LOCK: Permission denied
In my specific scenario I am running a service which creates the original database (as root). I am then attempting to access the database as another user (for manual checkup / data dump). All DB files are created with 0644 permissions. Sudoing the user script works as expected.


Update chain.json

please use an appropriate title

Please return chain.json to the filename chain.json

Please return chain.json to the filename chain.json

done


ci: test on node 20.5 rather than 20.6

🔗 Linked issue
https://github.com/nuxt/nuxt/issues/23020
https://github.com/nodejs/node/issues/49497
❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[x] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
This runs our CI on node 20.5 to avoid breakage in node 20.6 (example failed run: https://github.com/nuxt/nuxt/actions/runs/6096011429/job/16540685059?pr=23040).
Upstream solution has already been merged but I imagine it will likely take a while to filter back down to GHA runners, even after a hotfix release.
📝 Checklist

[ ] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

@danielroe Node 20.6.1 seem to have fixed it: https://github.com/nodejs/node/releases/tag/v20.6.1
Maybe worth to use it?

it might take a moment before it's rolled out to github actions with node-version: 20, but I'll open a PR to check.