external/jenkins failed with 'Unable to find image 'adoptopenjdk-jenkins-test:11-jdk-ubuntu-hotspot-full' locally

It's intermittent. Happened to openj9 and hotspot:
Unable to find image 'adoptopenjdk-jenkins-test:11-jdk-ubuntu-hotspot-full' locally
https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_extended.external_x86-64_linux_jenkins/26/console
https://ci.adoptopenjdk.net/job/Test_openjdk11_hs_extended.external_x86-64_linux_jenkins/29/console
00:57:30  jenkins_test_0_FAILED
00:57:30
00:57:30  Error: No such image: adoptopenjdk-jenkins-test:8-jdk-ubuntu-openj9-full
00:57:30  "/home/jenkins/workspace/Test_openjdk8_j9_extended.external_x86-64_linux_jenkins/openjdkbinary/j2sdk-image/bin/java" -Xshareclasses:destroyAll; "/home/jenkins/workspace/Test_openjdk8_j9_extended.external_x86-64_linux_jenkins/openjdkbinary/j2sdk-image/bin/java" -Xshareclasses:groupAccess,destroyAll; echo "cache cleanup done";

The reason is image is not built successfully and marked as successful.
06:39:12       [exec] Step 8/21 : RUN apt-get update 	&& apt-get install -y --no-install-recommends git maven 	&& rm -rf /var/lib/apt/lists/*
06:39:12       [exec]  ---> Running in 1a20d5e5b650
06:39:12       [exec] no status provided on response: unknown
06:39:12       [exec] Result: 1
06:39:12
06:39:12  dist:
06:39:12       [copy] Copying 2 files to /home/jenkins/workspace/Test_openjdk11_hs_extended.external_x86-64_linux_jenkins/jvmtest/external/jenkins
06:39:12
06:39:12  BUILD SUCCESSFUL
06:39:12  Total time: 46 seconds
06:39:12  0

Probably need to update if build_image can't be built successfully exit with error code and message. So build will stop to continue run to test stage.

Probably need to update if build_image can't be built successfully exit with error code and message. So build will stop to continue run to test stage.

I think all external projects need their build files updated to fail immediately, I am seeing this same issue with netty tests and their are likely others.
01:06:21       [exec] Step 8/22 : RUN apt-get update 	&& apt-get install -y --no-install-recommends git maven autoconf automake libtool make tar gcc-multilib libaio-dev 	&& rm -rf /var/lib/apt/lists/*
01:06:21       [exec]  ---> Running in 9ad6556f649d
01:06:24       [exec] Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB]
01:06:25       [exec] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB]
01:06:25       [exec] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [101 kB]
01:06:25       [exec] Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [109 kB]
01:06:25       [exec] Get:5 http://ports.ubuntu.com/ubuntu-ports focal/universe ppc64el Packages [11.0 MB]
01:06:26       [exec] Get:6 http://ports.ubuntu.com/ubuntu-ports focal/restricted ppc64el Packages [1,317 B]
01:06:26       [exec] Get:7 http://ports.ubuntu.com/ubuntu-ports focal/main ppc64el Packages [1,229 kB]
01:06:27       [exec] Get:8 http://ports.ubuntu.com/ubuntu-ports focal/multiverse ppc64el Packages [146 kB]
01:06:27       [exec] Get:9 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse ppc64el Packages [3,592 B]
01:06:27       [exec] Get:10 http://ports.ubuntu.com/ubuntu-ports focal-updates/restricted ppc64el Packages [2,467 B]
01:06:27       [exec] Get:11 http://ports.ubuntu.com/ubuntu-ports focal-updates/main ppc64el Packages [720 kB]
01:06:27       [exec] Get:12 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe ppc64el Packages [842 kB]
01:06:27       [exec] Get:13 http://ports.ubuntu.com/ubuntu-ports focal-backports/universe ppc64el Packages [4,304 B]
01:06:27       [exec] Get:14 http://ports.ubuntu.com/ubuntu-ports focal-security/universe ppc64el Packages [599 kB]
01:06:27       [exec] Get:15 http://ports.ubuntu.com/ubuntu-ports focal-security/main ppc64el Packages [345 kB]
01:06:27       [exec] Get:16 http://ports.ubuntu.com/ubuntu-ports focal-security/restricted ppc64el Packages [2,010 B]
01:06:28       [exec] Fetched 15.5 MB in 4s (4,307 kB/s)
01:06:29       [exec] Reading package lists...
01:06:30       [exec] Reading package lists...
01:06:30       [exec] Building dependency tree...
01:06:30       [exec] Reading state information...
01:06:30       [exec] Package gcc-multilib is not available, but is referred to by another package.
01:06:30       [exec] This may mean that the package is missing, has been obsoleted, or
01:06:30       [exec] is only available from another source
01:06:30       [exec]
01:06:30       [exec] E: Package 'gcc-multilib' has no installation candidate
01:06:51       [exec] The command '/bin/sh -c apt-get update 	&& apt-get install -y --no-install-recommends git maven autoconf automake libtool make tar gcc-multilib libaio-dev 	&& rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
01:06:51       [exec]
01:06:51       [exec] Result: 100
01:06:51
01:06:51  dist:
01:06:51       [copy] Copying 2 files to /home/jenkins/workspace/Test_openjdk11_hs_extended.external_ppc64le_linux_netty/jvmtest/external/netty
01:06:51
01:06:51  BUILD SUCCESSFUL

I think all external projects need their build files updated to fail immediately, I am seeing this same issue with netty tests and their are likely others.
01:06:21       [exec] Step 8/22 : RUN apt-get update 	&& apt-get install -y --no-install-recommends git maven autoconf automake libtool make tar gcc-multilib libaio-dev 	&& rm -rf /var/lib/apt/lists/*
01:06:21       [exec]  ---> Running in 9ad6556f649d
01:06:24       [exec] Get:1 http://ports.ubuntu.com/ubuntu-ports focal InRelease [265 kB]
01:06:25       [exec] Get:2 http://ports.ubuntu.com/ubuntu-ports focal-updates InRelease [114 kB]
01:06:25       [exec] Get:3 http://ports.ubuntu.com/ubuntu-ports focal-backports InRelease [101 kB]
01:06:25       [exec] Get:4 http://ports.ubuntu.com/ubuntu-ports focal-security InRelease [109 kB]
01:06:25       [exec] Get:5 http://ports.ubuntu.com/ubuntu-ports focal/universe ppc64el Packages [11.0 MB]
01:06:26       [exec] Get:6 http://ports.ubuntu.com/ubuntu-ports focal/restricted ppc64el Packages [1,317 B]
01:06:26       [exec] Get:7 http://ports.ubuntu.com/ubuntu-ports focal/main ppc64el Packages [1,229 kB]
01:06:27       [exec] Get:8 http://ports.ubuntu.com/ubuntu-ports focal/multiverse ppc64el Packages [146 kB]
01:06:27       [exec] Get:9 http://ports.ubuntu.com/ubuntu-ports focal-updates/multiverse ppc64el Packages [3,592 B]
01:06:27       [exec] Get:10 http://ports.ubuntu.com/ubuntu-ports focal-updates/restricted ppc64el Packages [2,467 B]
01:06:27       [exec] Get:11 http://ports.ubuntu.com/ubuntu-ports focal-updates/main ppc64el Packages [720 kB]
01:06:27       [exec] Get:12 http://ports.ubuntu.com/ubuntu-ports focal-updates/universe ppc64el Packages [842 kB]
01:06:27       [exec] Get:13 http://ports.ubuntu.com/ubuntu-ports focal-backports/universe ppc64el Packages [4,304 B]
01:06:27       [exec] Get:14 http://ports.ubuntu.com/ubuntu-ports focal-security/universe ppc64el Packages [599 kB]
01:06:27       [exec] Get:15 http://ports.ubuntu.com/ubuntu-ports focal-security/main ppc64el Packages [345 kB]
01:06:27       [exec] Get:16 http://ports.ubuntu.com/ubuntu-ports focal-security/restricted ppc64el Packages [2,010 B]
01:06:28       [exec] Fetched 15.5 MB in 4s (4,307 kB/s)
01:06:29       [exec] Reading package lists...
01:06:30       [exec] Reading package lists...
01:06:30       [exec] Building dependency tree...
01:06:30       [exec] Reading state information...
01:06:30       [exec] Package gcc-multilib is not available, but is referred to by another package.
01:06:30       [exec] This may mean that the package is missing, has been obsoleted, or
01:06:30       [exec] is only available from another source
01:06:30       [exec]
01:06:30       [exec] E: Package 'gcc-multilib' has no installation candidate
01:06:51       [exec] The command '/bin/sh -c apt-get update 	&& apt-get install -y --no-install-recommends git maven autoconf automake libtool make tar gcc-multilib libaio-dev 	&& rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
01:06:51       [exec]
01:06:51       [exec] Result: 100
01:06:51
01:06:51  dist:
01:06:51       [copy] Copying 2 files to /home/jenkins/workspace/Test_openjdk11_hs_extended.external_ppc64le_linux_netty/jvmtest/external/netty
01:06:51
01:06:51  BUILD SUCCESSFUL

Correct. All external projects use build_image() to generate the image.

Correct. All external projects use build_image() to generate the image.


XY grid - grid frame, full height issue

There's an issue with .grid-frame and .cell-block-y which don't get height: 100% (they only have the max-height: 100% set), which kinda defeats the point of a grid frame/app frame. The issue is that if the content within .cell-block-y doesn't overflow then it never hits the 100% height, which, if you have background applied results in columns that are too short and gives weird look.
The issue can be demonstrated if you delete some paragraphs from the official docs grid frame example. I'm attaching the photo for you to visualize what I mean:

Imho most users will require those columns to take up 100%, especially when background is applied.

I don't know if it's just me but I'm having huge issues with nesting those XY grids and keeping everything in line, especially full height but not having overflows cut off
see https://github.com/zurb/foundation-sites/issues/10571, it has a lot in common with this issue

It's still required to manually put height: 100% to the .cell-block-y cells when you want them to be 100% height when there's not enough content in the cells. So this issue remains open even though I closed the related issue.

Hmm... I think you're probably right that cell blocks should naturally expand to get to 100%, but would love to get some more opinions. What do you think @oxyc @JeremyEnglert @brettsmason @rafibomb?

I actually subscribed to this issue as it hit me as well and I thought it was a bug.

Yeah - that's right, first child nested .medium-cell-block-container > .grid-x - merged PR!

I guess https://github.com/zurb/foundation-sites/issues/10766 is about the same.

Yeah - that's right, first child nested .medium-cell-block-container > .grid-x - merged PR!

This did not really fix anything as far as we can see.

This issue has been mentioned on Foundation Open Source Community. There might be relevant details there:
https://foundation.discourse.group/t/challenge-getting-a-full-height-sidebar/2391/3

This is why I mentioned / linked it @davewsmith.

Adding that a manual style of height: 100% does not achieve the desired result. height: 100vw does.

100vw is 100% of the viewport width, that is probably not correct. The 100% worked in my cases. I also linked an issue by me regarding such a helper class.

Bizarre as it sounds, 100vw makes my example work (on Chrome 81.0.4044.113). 100vh works as well. But 100% causes the sidebar and content area to collapse vertically to the maximum of their respective content sizes. Happy to send a complete, 'working' example.

Same odd behavior on Firefox 75.0

100% may be different in your case depending on your box model (paddings) so max-height: 100% should work. Please let's continue in the forum.


NullAway interprets type parameters differently from the checker framework (TCF)

In TCF, a type parameter that has no annotations is assumed to have a nullable upper bound. For example,
interface List {
T add(T t);
}
I think T is assumed to be nullable.
Based on my experience with NullAway, the method parameter of add(T) is assumed to be @NonNull.
Please correct me if I am wrong.

This is correct.  Currently NullAway has no special support for generic types.  See #54 for some initial ideas for how we could add some support for checking clients of generic types.  Checking implementations of generic types would require further work.

Thanks, Manu, for the clarification.
If allowed, can I ask how your team manages false positives given this feature not implemented?
I am trying to annotate guava. However as the majority of guava is collection classes which extensively use generics, it is somehow difficult to annotate the code in a right way to pass NullAway.

I don't think we've run into a situation where we had to annotate a library like Guava, with so many generic collection classes.  We do have some internal generic collection classes, but we generally don't want to allow null values in them, so the default of @NonNull is fine.
I'd love to help find a good solution for Guava.  Thinking out loud, maybe we can add a way to annotate a class such that NullAway uses @Nullable as the default annotation for that class rather than @NonNull?  Maybe even just for generic type parameters?  I don't think this would affect NullAway performance too much, though we'd have to test it out.

Thank you, Manu. Let me dig into that further, and get back to you.
I believe the right solution is also the support for generics. How much work is it going to be?

Proper support for generics in the presence of subtyping is fairly non-trivial.  Plus I really do not want to compromise the performance of NullAway on non-generic code, so some care is required.  If I had to guess, I'd say that design + implementation + testing would take 4-6 weeks.  I'd be very happy to help out if someone is willing to take this on, but I can't promise to do this personally anytime soon.

I also tried TCF, and it is indeed slow. Can you shed some lights on why TCF is slow? I know that NullAway supports a subset. Is it the Java generics that makes TCF slow?

TCF's nullness checker is far more powerful (and sound) than NullAway.  The framework is also general and not specialized to nullness checking, which probably has a performance cost.  I think generics could be handled in NullAway without a significant performance cost.  We would just want to be very careful about performance while implementing, as NullAway runs on every build of our code.

@msridhar would it be possible to turn on expensive nullaway features on demand via some flags? We could make it possible for projects that use generics heavily to opt in to it as long as they understand some build time impact would be there.

@kageiit my concern is that users of an annotated generic library get sensible behavior from NullAway no matter the configuration.  Users may be confused if they need to opt in to more expensive checking to get safety when using the library.  But yes, you could imagine ways that we could do this if we are careful.
@chengniansun to clarify, would an intermediate step of allowing for type parameters to be @Nullable by default (via opt in) be useful to you?  Or is some kind of proper generics support required to handle Guava?  I'm still thinking of whether we can do some kind of basic generics support that wouldn't be too much work.
Another question: are type use annotations allowed with D8, as long as they are CLASS retention and not RUNTIME?  @kageiit?

In TCF, a type parameter that has no annotations is assumed to have a nullable upper bound. For example,
interface List {
T add(T t);
}
I think T is assumed to be nullable.

@chengniansun are you sure about this?  Look at TCF model for ArrayDeque.  There is no annotation on the type parameter, but TCF gives a compile error when trying to stick null in an ArrayDeque (as it should).  OTOH LinkedList, which does allow nulls, is written as class LinkedList<E extends @Nullable Object>.

From the documentation:

The most important annotations supported by the Nullness Checker are @NonNull and @Nullable. @NonNull is rarely written, because it is the default.

Thank you for your reply. Let me get back to you this afternoon.

@msridhar
I write the following code with ArrayDeque, and TCF emits no warnings.
public static void main(String[] args) {
ArrayDeque<@Nullable  String> q = new ArrayDeque<>();
q.add(null);
q.offer(null);
}

Hi Manu,
Please refer to $23.1.2 in the manual (https://checkerframework.org/manual/#polymorphism)
"Defaults
If the extends clause is omitted, then the upper bound defaults to @TopType Object. If no type annotation is written on the type parameter name, then the lower bound defaults to @BottomType void. If the extends clause is written but contains no type qualifier, then the normal defaulting rules apply to the type in the extends clause (see Section 24.3.2).
These rules mean that even though in Java the following two declarations are equivalent:
class MyClass
class MyClass
they may specify different type qualifiers on the upper bound, depending on the type system’s defaulting rules."

@chengniansun ok, the CF nullness type system is a bit complex :smile:  I think a brief summary is that if you just have class Foo<T>, then a client can write Foo<@Nullable String> and CF allows it and type checks the client code appropriately.  So I think your original statement is correct.
When NullAway supports generics, this might be a reasonable default.  On the one hand, it'd be good to match what CF does.  On the other hand, it might be safer to block client code from writing Foo<@Nullable String> unless there is some specific opt-in in class Foo.  At the least, there should be a way to explicitly prohibit writing Foo<@Nullable String> (e.g., ArrayDeque<@Nullable String> should be prohibited).
Is your work on annotating Guava for NullAway still blocked without proper generics support?  As I mentioned, adding that support will take us some time, but if there's any intermediate step you think we could take, please let us know.

Regarding ArrayDeque, I filed a bug at https://github.com/typetools/checker-framework/issues/1714#issuecomment-353184393

Thank you, Manu. I would vote to match CF's behavior, just for the sake of consistency, after all CF is also used here.
Yes, I am blocked, but it is okay. Currently, I am just evaluating NullAway and CF to see whether we can enable them by default. If we decide to use NullAway, I can contribute code too.


Date select button

(Is it possible to add a date selection button later? )
Also, can it support adaptive dates like 1d (1 day) or 2w (2 weeks) instead of entering a fixed date?
Originally posted by @Moyf in https://github.com/decaf-dev/obsidian-vault-explorer/issues/65#issuecomment-2159995384

@Moyf Added in 1.9.0. I copied Notion's date filtering. There is also a custom field now.

Great! Thanks! <3


regression: early custom events do not work

Regression in Insiders:
bug https://github.com/Microsoft/vscode/issues/57641#issuecomment-417714767 is back!
Just check out the old branch https://github.com/Microsoft/vscode-mock-debug/commit/16ab549f99662c4b074e37f492a759fb2399ac54 and launch mock-debug with F5.
Starting a mock debug session results in this error:

The debug session cannot be found.
It looks like the assertion that looking up a session ID must work as soon as the session ID is handed out, no longer works. I had fixed this for the September release.

The issue here was that previosuly we had a large session collection in the debugService which duplicated the model information and contained sessions while they were still initialising.
With the multiple repl work I have cleaned this up and allowed debug model to have sessions which are inactive and initialising and removed this duplication from the debugService.
However I was still only adding the session to the model only when fully initialisied. With this commit I have changed that, and I am immedaitly adding the session to the model even before it is fully initialised.
This should not have any regressions on other features, since the session will appear as inactive (not yet connected).
I have tested with the mock sample and now it works just fine for me.


Fixing Histogram race condition

What's the Bug?
Very rarely, a race condition can occur that will cause calculated tail percentiles of a histogram (> 99th percentile) to report Int.MaxValue.
The bug is due to a race condition that can happen when a value is added to the histogram at the same time the percentiles are being calculated in another thread.  What ends up happening is that the calculated number of added values is 1 higher than the actual number of added values in the histogram's buckets.  At high percentiles, it ends up searching through all the buckets for the missing value, and stops at the end, resulting in the "infinity" value of Int.MaxValue.
How did I fix it?
The percentile calculation function will now keep track of the last bucket with a non-zero count, and use that bucket instead of the last one when such a situation occurs.  This also ends up slightly changing how percentiles are calculated, but this change is only apparent when relatively few values have been added to the histogram.
This does not resolve the fact that the count is still one off from the actual total count, but generally that will have little to no effect, especially when hundreds to thousands of values are added per second.  Fixing that race condition would require doing some kind of atomic locking, which is probably not worth it.
How is it tested?
I added test that successfully and consistently reproduced the race condition.
Before merging, I am going to do a bit more testing to make sure that calculated percentiles are not significantly changed.

Codecov Report

Merging #509 into develop will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #509      +/-   ##
===========================================
+ Coverage    84.74%   84.75%   +<.01%
===========================================
  Files           98       98
  Lines         4288     4290       +2
  Branches       348      350       +2
===========================================
+ Hits          3634     3636       +2
  Misses         654      654

Impacted Files
Coverage Δ

.../scala/colossus/metrics/collectors/Histogram.scala
91.91% <100%> (+0.12%)
:arrow_up:

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 2d3610e...a21ce41. Read the comment docs.

Is this related to https://github.com/tumblr/colossus/pull/503 ?

@benblack86 no, that was due to the approximation algorithm we are using

Is it not possible to take a copy of the values before calculating the percentiles, that way you know they can't change?

@benblack86 that would actually end up leading to the same race condition, since the same off-by-one can occur while generating the snapshot.  Another option is to put all of the atomic longs inside a class behind an atomic reference, so that we swap out all the counters at once, however I decided against that for now as it would double the number of atomic operations needed to add each value.
I can investigate that possibility further though and try to get some measurements,

Yeah, I'm just thinking it would be better to have a complete solution where the count is also correct so anyone looking really hard at the numbers wouldn't find the error. We can go with this as a solution, but you should probably add to the comment that this isn't a complete solution.

@DanSimon you happy for me to merge this?

Yeah it should be good to go.


chore: add initial github ci workflow

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Angular 1.3.2

Hello please does the library work with this version  Angularjs 1.3.2

Hi @NanaPhil, could you please tell me the issues with this version of Angular? Do you have any feature that is not working to you?

Ok. I'm working on a project which i included this package . and the
controls seems to be disabled when i try to use it.
On Thu, Oct 13, 2016 at 8:42 PM, indrimuska<EMAIL_ADDRESS>wrote:

Hi @NanaPhil https://github.com/NanaPhil, could you please tell me the
issues with this version of Angular? Do you have any feature that is not
working to you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/indrimuska/angular-moment-picker/issues/68#issuecomment-253632568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMRbGbfq_aaBEXT0B0QJvI1v6hod6fJvks5qzpezgaJpZM4KRpy8
.

Also having this issue.

Thank you guys, could you please provide me a little plunker so I can work for a solution? :)
Thanks!

https://plnkr.co/edit/PozXQeW0eHdVxxIfgpeT?p=preview

Also having this issue with angularjs v1.3.15

Well, got it! The problem is due to how Angular sets scopes variables, in particular them used with fn binding. Indeed even if you haven't set the Moment Picker property selectable, you'll get that property set in the controller.
The fix is very simple, I'm going to pack a solution and a new release as soon as I can. :)
Thank you all for reporting this.

I've just released v0.6.7 that contains this fix for Angular 1.3.
Thank you guys, good work! :)

Looks like this is still an issue with the latest version of moment picker and Angular 1.3.*
https://plnkr.co/zCpgQK
If you bump the angular version to 1.4 it starts working.

Thank you @ghostrydr for reporting this, I"ll look into this.

Ok, got it! Angular 1.3 returns handles function binding properties using angular.noop function when no values are provided. In this case, selectable is always fired returning an undefined value (noop does nothing). Since it's not returning true, you see no cell is selectable.

Fixed in v0.9.9.


ER: @_ephemeral for variables with scoped lifetimes

Motivation

We have various functions in the stdlib (and other libraries) that take a closure and pass a value to it, with the expectation that the value will die when the closure and function return. Things like withUnsafePointer(to:_:) or String.withCString(_:). These functions do not currently guard against their temporary values escaping the closure, e.g. with something like this:
let badness = withUnsafePointer(to: 0) { $0 }

Although we tell developers not to do that in documentation and comments, there's no compile-time diagnostic for it.
Solution

We should consider adding some attribute that the compiler can recognize and use as a hint for performing escape analysis. Escape analysis is inherently imperfect and is unsolvable in the general case, but it doesn't mean we can't catch at least some misuses. I've termed this attribute @_ephemeral to mirror the existing @_nonEphemeral attribute used when a temporary pointer is unsafe to pass into a function.
Example usage:
func withUnsafePointer<T, R>(to value: T, _ body: (@_ephemeral UnsafePointer<T>) throws -> R) rethrows -> R {
  ...
}

let badness = withUnsafePointer(to: 0) { $0 } // 🛑 Error: ephemeral pointer $0 is escaping the context in which it is valid

@_ephemeral may or may not imply that a value is unsafe to pass to a @_nonEphemeral argument. It would be safe to pass $0 above to various pointer-casting initializers and functions. So a different name may be appropriate.
Move-only types don't solve this problem because the common type here is a pointer of some flavour, and pointers are not move-only.
Alternatives considered

N/A

I think this is mooted by non-escaping types.


jasync encapsulates exceptions with CompletionException

Version: 3.5.2
Module: quill-jasync
Database: postgresql (it probably happens with mysql too)
Expected behavior
When jasync completes the future with a failure, the exception should not be encapsulated
Actual behavior
Jasync fails the future using CompletionException, encapsulating the real exception
Steps to reproduce the behavior
Any constraint error should be enough to simulate the issue
Workaround
Instead of:
run(insertion)
  .recoverWith {
    case e: GenericDatabaseException if e.getErrorMessage.getMessage == "duplicate key" =>
      Future.failed(...)
   }

It's possible to do this:
run(insertion)
  .recoverWith {
    case e: CompletionException if e.getCause != null  =>
      Future.failed(e.getCause)
  }
  .recoverWith {
    case e: GenericDatabaseException if e.getErrorMessage.getMessage == "duplicate key" =>
      Future.failed(...)
   }

@getquill/maintainers

@gabfssilva Please read and comment if needed https://github.com/zio/zio-quill/issues/2881

JAsync support as been dropped


Local Prefilter index format (idea)

sequence_file: (maybe human readable)
  filename: reference.fasta
  sequences

ibf_file: (binary)
  filename: index.ibf
  kmer_size
  window_size
  ibf_data

reference_metadata_file: (human readable) [needed for split]
  filename: reference_metadata.txt
  two_columns:
  	reference_id: fasta.id, e.g. chr1 some=metadata,
  	reference_length: 1506

reference_segments_file: (human readable) [needed for ibf]
  filename: reference_segments.txt
  segments: (4 columns)
        bin_number: 0...max_bins-1
        reference_id: fasta.id, e.g. chr1 some=metadata
        start_position: relative to current reference sequence
        length: length of the segment (max: reference sequence length)

local_prefilter_index_file: (binary)
  filename: index.local_prefilter_index  .lpidx
  ibf: same as ibf_file above
  file_names:
  	all the input fasta files "./reference.fasta" (emit warning like: "<absolute_path>/reference.fasta is missing")
  mapping of segments to bin: std::map, std::undered_map<bin_number, segments>
  	bin_number: 0...max_bins-1
  	file_name: (as an index into file_names)
  	reference_id: fasta.id, e.g. chr1 some=metadata (maybe record_id is better? this should be a number)
        start_position: relative to current reference sequence
        length: length of the segment (max: reference sequence length)

ibf_metadata.txt:
	bin,file_name,      reference_id, start_pos , length
	(0, "refrence1.fa", "chr1",       15004,      150)
	(0, "refrence1.fa", "chr1",       1504,       150)
	(0, "refrence1.fa", "chr2",       154,        150)
	(0, "refrence1.fa", "chr3",       1504,       150)
	(0, "refrence1.fa", "chr4",       3004,       150)
	(2, "refrence1.fa", "chr4",       304,        150)

./sliding_window split {parametes} -> reference_metadata.txt, reference_segments.txt
./sliding_window split {parametes} -> ibf_metadata.txt (NEW)

./sliding_window build --from_segments reference_metadata.txt reference_segments.txt -> index.ibf
./sliding_window build --from_segments ibf_metadata.txt (NEW) -> database.lpidx

./sliding_window search index.ibf [database.fa] query.fa [reference_segments_file]
./sliding_window search database.lpidx query.fa (NEW)

.lpidx might also need to encode the overlap_length


Adds the setting to denote that we open files in place

There's a new validator on iTunes connect, and we have to include that we open .artsy files which are used to pass links when sharing between phones.

merge on green

          1 Warning

:warning:
Needs testing on a Phone if change is non-trivial

  Generated by :no_entry_sign: Danger


The app won't project results on discord

Recently me and my friends were trying to use the app in one of our dnd sessions but when we rolled dices in dnd beyond, it didn't show results in discord channel.
If it can be fixed, please let me know, if not, thanks in advance.

Thank you for bringing this to my attention. I was aware of the issue, but I wasn't sure if it was just local on my machine or not. The extension worked fine a week ago, so dndbeyond must have changed something on their website in the last 7 days that broke the extension. I'm currently looking into it.

A fixed version (version 1.2.0) has been submitted to google for review, it will be available for installation soon. I will leave this issue open until it's verified that version 1.2.0 fixes this issue.
As a side note, firefox support has been dropped for the foreseeable future due to limitations with the firefox extension API.

A fixed version (version 1.2.0) is now available. Please update to the latest version :smile:

Thank you for fixing and making app that's really nice.


NuScenes Evaluation

Hello and thanks for the release of this code!
I would like to evaluate the tracking results using the NuScenes evaluation. I noticed that this code currently only evaluates one sequence at a time, and produces a single JSON file for each sequence. Would you recommend I just evaluate all sequences and combine them in a single JSON file for evaluation?

Hi, thanks for checking out our work!
The code outputs sequence-level evaluations for KITTI, but for NuScenes it produces only one final JSON file after processing the whole data split - you can trace the call of this function. The final result's format should be perfect for NuScenes Devkit evaluation. I am not aware of an easy way to do sequence-level evaluations.
When running on NuScenes script does produce .txt files for each sequence, but they are empty. This functionality is a by-product of KITTI-specific code that I wrote, which I did not remove because it was useful to see how far the run has gone without ssh-ing into the session :). I also attempted to use those .txt files to save progress for each sequence by it became too cumbersome.
Perhaps this led you to this confusion, but those files are completely empty, so you can remove them if you'd like.

Hello!
So currently the code only produces one JSON file for one sequence, I believe what was happening was due to the break here, which would exit the loop after processing a single sequence. I was able to remove this break and get the functionality that I needed.
Thanks for the help!

Oops, I must have left it there after a recent test run.
Thanks for the flag! Fixed it and gave you a shoutout in the commit message :)


Flag to allow for graceful exit on hanging process

Clear and concise description of the problem
There are a few threads where people are describing having issues with hanging process in Vitest. I'm convinced that the vast majority of the time it is because of some sort of issue with a tests and not Vitest, however in some cases when one is moving a large codebase from another testing framework such as Jest where this issue did not surface due to different archectecture it can be a major blocker to adoption. I have this issue now where I am considering migrating back to Jest after a lot of work to move the codebase from CRA to vite wholesale because we simply cannot figure out what the cause is in our 10k+ tests.
This was not an issue in Jest.
Suggested solution
Allow for a flag such as --ignore-open-handles or something that allows users to opt into ignoring the open handles. I'm not sure if this is actually feasible but it would solve the problem for us as our tests are passing just fine, but they fail around 75% due to haning process which seems to be very hard to pin down.
Ideally this would happen as soon as all the tests are reported as passing as currently the test step in our CI/CD will eventually exit and fail with this issue, but it takes about 30mins before that happens. Is it technically feasible to go "oh look at the tests have passed, force exit process and exit with success code" or is there some technical reason why this is not possible?
I know ideally people would fix the root cause but sometimes this is not feasible and I would like to stay on Vitest but at this point it's becoming a terrible drain on our productivity and I don't know how much more time I can justify on trying to diagnose the issue, if we could simply ignore it (as I assume we were doing with Jest) then that would be preferable.
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Anything that helps preventing process hanging sounds good but what would this flag do in practice? Vitest already calls process.exit() but the process just won't terminate:
https://github.com/vitest-dev/vitest/blob/f4e6e99fa3a81fd7a97fb9b435da367dddba7fa4/packages/vitest/src/node/core.ts#L771

That is what I don't know and just thought I'd propose in case someone has any better ideas. I don't really understand the process of spawning processes and why the spawner can't force close them so thought I'd just suggest and see if anyone else had any ideas.

Having a quick look at Jest the way the do it is by going Worker.terminate() and they have an explicit flag for this:
https://github.com/jestjs/jest/blob/25a8785584c9d54a05887001ee7f498d489a5441/packages/jest-worker/src/workers/NodeThreadsWorker.ts#L283
https://jestjs.io/docs/cli#--forceexit

Jest doesn't use that src/workers/NodeThreadsWorker.ts by default. It has to be manually enabled by https://jestjs.io/docs/configuration#workerthreads. Are you sure your test cases don't get stuck when that flag is enabled?
There are cases where NodeJS worker_threads get stuck without Vitest. I would expect Jest to get stuck too. https://github.com/vitest-dev/vitest/issues/3077#issuecomment-1484093141

Yeah fair enough that's probably true. I'm just brainstorming on ways to make it so that someone can come from Jest where the hanging issue doesn't occur by default. To Vitest where hanging is an issue. Perhaps that is impossible I'm not sure.

New ideas to solve hanging process issues are always welcome but unfortunately this one doesn't really offer any solutions.
One thing that could help is to provide a reproduction case that makes Vitest hang. As far as I know, we have not received any reproduction cases that we could look into. The #2008 has plenty of discussion but no reproduction cases.
In #3077 there was a clear reproduction case and root cause was identified to be NodeJS issue related to compatibility with native fetch and worker_threads.

Thanks @AriPerkkio I agree, my understanding was not complete enough! I will close this comment unless I have something more actionable for you.


JMeter cannot start when -JBuildNumber command-line parameter is not integer

JMeter cannot start when -JBuildNumber command-line parameter is not integer.
I tried
-JBuildNumber=8.2.54     - failed to start
-JBuildNumber=8_2_54   - failed to start
-JBuildNumber=54          - succeeded

Hey there,
What CI environment are you using that's providing that kind of build numbers?
Thanks,

This is NOT CI :-)
This is just build number of the application I test.
I want to use -JBuildNumber parameter to distinguish between different
builds in grafana
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
08/29/19,
03:42:47 PM
чт, 29 авг. 2019 г. в 15:40, Anthony Gauthier<EMAIL_ADDRESS>
Hey there,
What CI environment are you using that's providing that kind of build
numbers?
Thanks,
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/delirius325/jmeter-elasticsearch-backend-listener/issues/65?email_source=notifications&email_token=AGPDKTWFQVGEF2ZPXKEUXR3QG67VPA5CNFSM4ISBY2O2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5OKVQY#issuecomment-526166723,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGPDKTUNPVQ2OPHEOJ4KPITQG67VPANCNFSM4ISBY2OQ
.

--
Regards,
Leon Sery.

Hi delirius325!
Can you provide the fix for the issue?
Leon

Hi Leon,
It will come; that's for sure! I cannot give an exact date however. Pretty busy these days and I've been working on another plugin a lot.
It should be out by the end of next week though :smile:
Cheers,

After careful thinking, this parameter (BuildNumber) will be left as it is. If you have any issues, please feel free to use custom variables to be able to compare in Grafana afterwards.


[LiveComponent] please give full examples

This seems interesting
But your example here
https://ux.symfony.com/live-component#demo
Uses a loop to show items (ok, i got this working)
But your example here
https://ux.symfony.com/live-component/demos/voting
Simply shows a template snippet with zero looping ..so how it this working ?
because when i try to implement it, i get
An exception has been thrown during the rendering of a template ("The property "App\Components\LiveUserComponent::$user" is not readable because it is typed "App\Entity\User". You should initialize it or declare a default value instead.").
I've used the exact same entity in both examples i tried to implement
Would strongly appreciate full source code to the examples shown on ux.symfony.com
It's already complicated enough that example code, and documentation code do not align and need adaptation ;-)
Thank you !

The code shows the food_vote component source. Each row is its own component, which is rendered in a loop.
The full source is in this repository (in the ux.symfony.com/ directory). E.g. the loop you're looking for is: https://github.com/symfony/ux/blob/2.x/ux.symfony.com/templates/live_component_demo/voting.html.twig
But I'm not involved much in the UX initiative, so I let others decide on what to improve in the rendered example/docs here :)

Thanks, that makes it a little easier to navigate the examples !
Should probably link this on the ux.symfony.com page with the examples, as most ppl (me included) will just copy-paste the example code (with a few adaptations) and expect it to work ;-)

Hi!

Ideally, i'd suggest making a full blown symfony project with ALL the examples (in working condition), and just allow users to download that and play with it. This could also double as as test ground for the devs, to make sure their examples actually still work, as progress on the code goes forward.

That is kind of what I was thinking for ux.symfony.com - it's a site to demo things, but you can also use it locally.
However, I can see 2 problems immediately:
A) The ux.symfony.com sub-directory doesn't have a README about how to set it up. Plus, we don't link or mention it anywhere as a demo project.
B) On https://ux.symfony.com/live-component/demos/voting, that's a really good point that we're zooming in too much, and so you can't really see the full picture. The full picture would include:

The original controller https://github.com/symfony/ux/blob/2.x/ux.symfony.com/src/Controller/LiveComponentDemoController.php#L61-L68
The template that renders the component https://github.com/symfony/ux/blob/2.x/ux.symfony.com/templates/live_component_demo/voting.html.twig#L20-L26
Then also the component class and its template

Basically, I think we should have some sort of a "See the code" link somewhere on that page that takes you directly to GH so you can browse around. Maybe a "See the code" link directly below the 2 code blocks. On click, it rolls down to show a list of files, each which is a link to GH.
Thanks for the convo - ux.symfony.com is a great demo resource... let's leverage it better!

Maybe you could move the site to a different repository and like that it would be easier to clone.

That's a pretty good idea - it would increase visibility as well.


Add support for managing client-policies

What this PR does / why we need it:
Adds support for managing client-profiles.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
fixes #863
Special notes for your reviewer:
Some executors such as secret-rotation  in client-policies are only available in recent Keycloak versions.
PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[X] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR
[X] add tests for client-policy profiles referencing profiles
[X]  add tests for client-policy policies referencing profiles
[X]  document client-policy support

@st3v0rr I think the current CI build failures are unrelated to this PR, would you mind taking a look?
All test runs fail with this test:
...
Error: org.jboss.resteasy.client.jaxrs.internal.proxy.extractors.BodyEntityExtractor#extractEntity: HTTP 404 Not Found
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.498 s <<< FAILURE! - in de.adorsys.keycloak.config.mock.CookieMockIT
[ERROR] de.adorsys.keycloak.config.mock.CookieMockIT.run  Time elapsed: 0.239 s  <<< ERROR!
javax.ws.rs.NotFoundException: HTTP 404 Not Found
	at de.adorsys.keycloak.config.mock.CookieMockIT.run(CookieMockIT.java:77)
...
	````

@st3v0rr I think this PR is ready now for review, would you mind taking a look?

@st3v0rr once #861 is merged (with the fix for the build errors) we can rebase and add this PR too.

@st3v0rr I just noticed that I forgot to click "ready for review". I just updated the PR. Could you take a look?

Rebased on current main


AudioRateSubsampler needs to be updated to standard format

I think this fixed it: https://github.com/iejMac/video2dataset/pull/271


Removing while iterating over array in VRTK_BasePointerRenderer.MakeRenderersVisible

I believe this is a buggy, some renderers in the array will be skipped over: https://github.com/thestonefox/VRTK/blob/7f19760c259185459b02e4b943070027fe482b19/Assets/VRTK/Scripts/Pointers/PointerRenderers/VRTK_BasePointerRenderer.cs#L411-L414

Raise a proper bug report or a pull request otherwise this issue will be closed


Popover events not working

Are the popover event's supported
I want to set a custom position relative to the last css calculation and I cannot achieve that as .on('shown.bs.popover' ....) doesn't work

An example http://plnkr.co/edit/QMTxCXMkmKJuIYUCk6dK?p=preview

If I understand what you are trying to do here, I would argue that what you're trying to do is well outside the scope of this library.  Can you please explain what you are trying to accomplish and why?
You might be interested in the new feature we have slated for 1.0 (currently in master) where we allow positional placement similar to Bootstrap core.
At this point, please explain what you want to do (from a high level) and we'll proceed from there.   Thanks.

We do not support event APIs from Bootstrap, and do not intend to.
We do need more detail though, as your use case is not clear as to why it must be done this way.

I'm trying to align the start of the popover in x-axis with the start of the button and move the popover arrow in the right side and not in the middle, and because the button that triggers popover change places i cannot put this inside CSS but must do this dynamically.

@epnikolop, I'm still not sure what you're trying to do.  It sounds like you are trying to do custom popover placement via CSS via a wrapping directive?  If that's the case, I'm not sure there's much we can do here since you're doing something outside of the functionality the API provides.
As I mentioned, please pull the latest from master and see if the new, positional placement, is something that will work for you.  Please let us know.

You could close it thanks

Closing as requested.

@icfantv @epnikolop : I know this is an old thread but I could not find any other place to ask the question. I have a requirement, "whenever popover is opened, put the focus on first input field, if available".
For this, I would require an event .on('shown.bs.popover' ....) . So, that I can put the focus on the input field (for e.g.: as show in this answer)
Kindly let me know if it is possible now, or is there a better way to achieve the objective.
Thanks in advance.


Promote | partnership with Rovel Stars!

Hey devs, I'm the owner of Rovel Stars, a team on Discord, which has some awesome projects like:-

URL shortener
Rovel Paste
Rovel Bot List
Rovel Blog
I want your services (chat room) integration with my projects (using iframe of course).
So, do you all accept my invitation to partner?

Hi feel free to link out to Darkwire for your specific purpose, but we are not looking for partnerships at the moment.


Reward can be negative when transaction fees exceed 2× the coinbase

Summary
When the block’s transaction fees approach 2× the block’s coinbase reward, the formulas for computing the rewards break down.
Details
For common class, reward is proportional to effectiveCommonPoolWeighting: https://github.com/jrwashburn/mina-pool-payout/blob/05dcebcc977591a0de7c00f7a46a9b60727e3789/src/core/payoutCalculator/PayoutCalculator.ts#L94-L96
Which is the quotient of the staker’s commonStake and the sum of all staker’s commonStake: https://github.com/jrwashburn/mina-pool-payout/blob/05dcebcc977591a0de7c00f7a46a9b60727e3789/src/core/payoutCalculator/PayoutCalculator.ts#L84-L85
https://github.com/jrwashburn/mina-pool-payout/blob/05dcebcc977591a0de7c00f7a46a9b60727e3789/src/core/payoutCalculator/PayoutCalculator.ts#L66
For non-locked stake, the commonStake is stakingBalance times a factor 2 - superChargedWeightingDiscount: https://github.com/jrwashburn/mina-pool-payout/blob/05dcebcc977591a0de7c00f7a46a9b60727e3789/src/core/payoutCalculator/PayoutCalculator.ts#L60-L62
This means that if superChargedWeightingDiscount > 2, commonStake turns negative.
The superChargedWeightingDiscount is set to the block’s user transaction fees divided by the block’s coinbase: https://github.com/jrwashburn/mina-pool-payout/blob/05dcebcc977591a0de7c00f7a46a9b60727e3789/src/core/payoutCalculator/PayoutCalculator.ts#L51
https://github.com/jrwashburn/mina-pool-payout/blob/05dcebcc977591a0de7c00f7a46a9b60727e3789/src/core/payoutCalculator/PayoutCalculator.ts#L43
usercommandtransactionfees is controlled by user input, it depends on transactions that users submit. If one malicious user is willing to spend twice the coinbase on transaction fees, it would cause this script to compute rewards for common shares as negative. Which rewards turn negative depends on the ratio of locked to non-locked stake:

If there is sufficient locked stake to make sumEffectiveCommonPoolStakes come out positive, then the quotient effectivePoolStakes[staker.publicKey].commonStake / sumEffectiveCommonPoolStakes is negative for non-locked stakes but positive for locked stakes.
If there is insufficient locked stake, sumEffectiveCommonPoolStakes will itself be negative. Then the negatives cancel for non-locked stake, and non-locked stakes get a positive reward, but now locked stakes get a negative reward.
If the ratio between locked and non-locked stake is just right, sumEffectiveCommonPoolStakes could come out to zero, making the entire computation invalid due to division by zero.

One might argue that transaction fees in practice are much lower than the coinbase so this is a hypothetical problem, but to me this demonstrates a deeper problem with the formulas. If the block has a positive coinbase reward, and we have to distribute that among stakers, there should not be any point in the parameter space where a staker gets a negative reward.

Thanks for the very detailed issue!
By default, the payout runs with isolated supercharged pool: https://github.com/jrwashburn/mina-pool-payout/blob/main/src/core/payoutCalculator/PayoutCalculatorIsolateSuperCharge.ts
That said, some of the details of the issue are relevant.
I don't think it is possible in the protocol for transaction fees to exceed the coinbase; instead, an empty block would be created. So I don't think this is a valid issue; however, it would make good sense to add additional guards to fail on the scenarios you note. I think the best behavior would be to fail since I don't understand how this situation could arise, or what the calculation should be if it does.

transaction fees are received by the block producer so are effectively unbounded to the upside. We've already seen massive transaction fee blocks on the KuCoin launch.
Snark fees can't exceed coinbase + tx fees, as those are paid out.
This is how I defined the supercharged weighting. The idea was as tx fees become larger, a larger share should go to non-supercharged holders. https://docs.minaexplorer.com/minaexplorer/calculating-payments#defining-the-supercharged-weighting

Examples where tx fees > 2x coinbase are really hard to find but here's one for a long time ago that could be used to test this https://minaexplorer.com/block/3NLFAaRj1HWSZSWVYqihUiHpkznFzcwh6uLvM2ytxwphuBV9ZWaX

I guess my cold / snark fee obsession has gone to my head. Transaction fees, not snark fees. Sorry. Will correct this when I can - probably week after next. Open for PR's as well obviously.

Open for PR's as well obviously.

It’s not clear to me what a proper solution would be; I don’t understand why superchargedWeightingDiscount is in there in the first place and why transaction fees should affect how the coinbase is distributed among stakers. The formulas would make more sense to me without superchargedWeightingDiscount, but presumably it was put in place for a reason?

The supercharged weight smooths out the impact of locked vs. unlocked accounts, and is intended to give unlocked accounts a higher proportional share of each block, whether supercharged or not. This was based on Gareth's original design and he referenced above: https://docs.minaexplorer.com/minaexplorer/calculating-payments. It looks like I took a shortcut in implementing it along the way leading to the vulnerability you have pointed out.
The alternative approach, which is the default now, only shares the supercharged portion of any block with unlocked accounts. My reasoning for the alternative implementation has been that for smaller pools, the smoothing hurts locked accounts in epochs where the unlocked accounts are unlucky, and it's cleaner/simpler to just let unlocked accounts share in the supercharged portion exclusively. The default implementation doesn't have any superchargedWeightingDiscount.
I don't know if/how many people use the weighted calculator, but I think the fix for the weighted approach is straightforward and think I'll just implement Gareth's formula for those that want that approach.


328 GRC bounty: notify user in the wallet about important issues (new mandatory version, ...)

 Issue by Erkan-Yilmaz
Wednesday Sep 13, 2017 at 10:47 GMT
Originally opened as https://github.com/Erkan-Yilmaz/Gridcoin-tasks/issues/161

We've an open issue since 13 months (August 2016) :-(

This is a feature we need with each update/upgrade for Gridcoin:

currently we do this - manually - over the existing communication media, but:

this is slow
may not reach everyone

Current discussed approaches are:

monitoring a burn address
making an "alert"
in case none of the mentioned/coming ideas work:

think about an option that is "unsafe" but works (e.g. activate in options, but tells clearly: "some of your data may leak for this feature to work correctly" or so) :-(

If you would like to sponsor this issue, please send your GRCs to address (this resides in my wallet):

SF5s9HZBYc3fTPLRsVQtETfGktz6gR4mjK

As public sponsor your name will be listed in all related announcements:

e.g. you could also come to IRC  and tell me in private beforehand how much you will donate, it might be hard to get your details otherwise. My IRC nick is: Erkan_Yilmaz
You can of course also donate anonymously.

The bounty will be paid out to that person that:

sends a merge request to the offical repo that works AND
is implemented in Gridcoin also:

about 2.: e.g. option3 ("unsafe impl.") above might not be accepted?

needs discussion: security of network vs. security of individual (personally, "security of individual" is more important to me: I added option3 only so we can "move forward" with the issue. Also, I link to the fork warning which seems so far to prevent the issue going forward?)
if option3 would be selected: after discussion also needs voting on community? but if it is per default off AND gives user clear info about consequences when enabling: then probably not...

Thanks

 Comment by Erkan-Yilmaz
Wednesday Sep 13, 2017 at 14:08 GMT

see also comments here

Current sponsors:

150 GRC (by @personthingman2)
100 GRC (anonym)
78.04 GRC (by @tomasbrod)

monitoring a burn address

If an user is on a fork, they'll never see a transaction hitting this burn address unless it was sent ahead of time (or if the messenger forced themselves to join a forked chain to send the message) - the problem then becomes who would be authorized to send notices to this burn address? A spam problem would likely occur.

making an "alert"

Emergency alerts are already possible, not utilized by Rob (only person capable of doing so).
We could implement something simple like:
If (Difficulty < 0.5) { alert("You may need to upgrade your client!");}

think about an option that is "unsafe" but works (e.g. activate in options, but tells clearly: "some of your data may leak for this feature to work correctly" or so) :-(

Yeah, let's not implement 'unsafe' functionality if we can avoid it..

security of network vs. security of individual (personally, "security of individual" is more important to me: I added option3 only so we can "move forward" with the issue. Also, I link to the fork warning which seems so far to prevent the issue going forward?)

The security of the network is the absolute priority, without it the security of the individual is irrelevant.

If you would like to sponsor this issue, please send your GRCs to address (this resides in my wallet):

I feel that this kind of fundraising is inappropriate and borderline begging. If you desire a feature to be implemented then either program it or fund its development yourself; if you lack both the programming capabilities and the funding to pay devs, then creating a foundation poll within the Gridcoin client as it's the established process for requesting funds to be paid to developers for a feature (rather than requesting users send you funds for a feature which may never be implemented).

My PR https://github.com/gridcoin/Gridcoin-Research/pull/693 applies to this task. #177 would be better, but this is all I got.

What is going on with this issue?
It will be closed in 7 days if there is no update.

@iFoggz is working on a PR that willl address this issue.

This is possibly fulfilled with the new update check

I believe it has.

Can someone confirm who the bounty should go to? I'd like to see if we can close another one.

Bounty paid:
TX ID: 56b549ca8617e7be98e45bc1353081282b59721071ae775b0b5b2d56b0dabca0
TX ID: ddf6c2d00cef29e9a97ed9cf1a64d6e707f48ff652dba8f62e86e4f6afd80bf9
Can this be closed?

Yep. Thanks!


Setting initial window size

I am building a MFA-type application.
How does one go about setting the initial height and width of the application window ? It should be something trivial to do I'd imagine and yet, no luck. I looked at all the examples and they all start with the very same window dimensions.
I can change the width and height of the widgets themselves. Just not the window (other than using the mouse of course)
Am I being blind here ?
I am running on Linux (arch linux) if that makes a difference for this problem.
Great lib otherwise, still learning how to use it.
Thanks

You should be able to use the window field in Settings when calling Application::run.

Thanks a lot @hecrj . I was pulling my hair on such a trivial goal ;-)
In case anyone else is also wondering:
use iced::{Settings, window};

let settings = Settings {
        window: window::Settings {
            size: (300,500),
            resizable: true,
            decorations: true,
        },
        ..Default::default()
    };

@gr211  Thanks, for asking this and showing the solution :)

@gr211  Thanks, for asking this and showing the solution :)


Update whitelist

knockout has now it's own types
I'm working on https://github.com/DefinitelyTyped/DefinitelyTyped/issues/37490

It's now in the production branch, so Definitely Typed's CI will get the new whitelist next time it runs.


Migrate DBeaver navigators to Eclipse Common Navigator Framework

There is a standard eclipse framework to build "Navigator" or "Explorer" view
https://help.eclipse.org/oxygen/index.jsp?topic=%2Forg.eclipse.platform.doc.isv%2Fguide%2Fcnf.htm

#2659


Simplify repository contents

Get jupyter-remote-desktop from pip, rather than ship it
as part of the repo
jupyter-remote-desktop ships with a version of tigervnc,
no need to install it separately
The Dockerfile was overriding apt.txt, and is no longer needed
anyway. The default repo2docker setup works
We don't explicitly turn off the screensaver, which might be
problem now. Not sure though, maybe it's ok? :)
Adds a desktop qgis launcher icon

I also made a template repo that can be used to generate these kinda repos in the future https://github.com/yuvipanda/binder-desktop-app-template

You can try this out on https://mybinder.org/v2/gh/yuvipanda/jupyter-desktop-server/qgis?urlpath=desktop

Sorry for the delay. This PR slipped through me.

yay, thanks for the merge @giswqs


CORS configuration too much

Describe the bug
As of now some CORS parameters are configurable via env vars e.g. OCIS_CORS_ALLOW_METHODS, OCIS_CORS_ALLOW_HEADERS (and OCIS_CORS_EXPOSE_HEADERS - see upcoming PR by @butonic )
Besides the fact that different services require different methods and headers and need to be configured on service level - changing the working default to anything different will most probably break some services partially.
Proposal
Do not configure allow methods, allow headers, expose headers and max ago but leave this to the individual services.

I agree, the only 'global' CORS config should be the allowed origin. the rest should IMO be hardcoded. At least we sohuld drop the OCIS_CORS* env vars (save OCIS_CORS_ALLOW_ORIGINS)

At least we should drop the OCIS_CORS* env vars (save OCIS_CORS_ALLOW_ORIGINS)
I agree generally, but on a higher level we need to really change our attitude towards config.

We are getting more and more feedback, that our todays practise leads to broken deployments on every release.
The reality is, nobody reads the docs.
The biggest problem is exactly what we have here: Removals of config which was working before.

The Helm Chart currently only exposes the CORS allow origins setting:
https://github.com/owncloud/ocis-charts/blob/d43e44276efffc37cc8e62621d99a255da7c4cb5/charts/ocis/values.yaml#L57-L61

For me, the ENV var which is exposed is not fully working on a fresh install.
I am trying to integrate a new installation of OwnCloud Infinite Scale (Community Edition) with the Janssen Authorization Server, an open-source OIDC provider. The authentication workflow almost succeeds:

OwnCloud redirects to the SSO sign-in page
Authentication Credentials are accepted and the requested OIDC scopes for OwnCloud (profile, mail, etc.) are presented to the user for acceptance
Browser redirects to the OIDC callback page on OwnCloud (https://oc.[my domain].io/oidc-callback)

However, when the landing page on OwnCloud attempts to fetch the authorization token via Javascript (a request to https://[my domain]/jans-auth/restv1/token) , a CORS violation occurs and the browser blocks the request.
https://sso.[my domain].io/jans-auth/restv1/token
Request Method:
POST
Status Code:
401 Unauthorized
Referrer Policy:
strict-origin-when-cross-origin

It seems that https://sso.[my domain].io/ needs to be added to the CORS configuration for the OwnCloud frontend. I believe I have done this correctly, but it's still not working.
I'm deploying OCIS using the Helm charts, and the CORS-related configuration values do seem to be making it into the containers...
❯ kubectl get pod frontend-5d7bfd6fdf-mkc5m -o yaml |\
  grep -C 2 OCIS_CORS_ALLOW_ORIGINS

...
    - name: OCIS_CORS_ALLOW_ORIGINS
      value: '*,https://sso.[my domain].io,https://oc.[my domain].io,https://[my domain].io'
    image: owncloud/ocis:4.0.1

also...
❯ kubectl exec frontend-5d7bfd6fdf-mkc5m -- sh -c 'echo $OCIS_CORS_ALLOW_ORIGINS'

*,https://sso.[my domain].io,https://oc.[my domain].io,https://[my domain].io

So the config values have made it at least as far as ENV vars inside the containers. But it seems not all the way to the browser? Seems like I'm missing something obvious.
Any help or tips debugging this will be greatly appreciated.
Thanks in advance,
-b

The OIDC server is hosted at: https://sso.[my domain].io
OCIS is hosted at: https://oc.[my domain].io
Steps to reproduce

Establish OIDC provider at https://sso.[some domain].io/
Deploy OCIS from the Helm charts to   https://oc.[some domain].io, using the following overrides:

externalDomain: oc.[some domain].io

# HTTP settings for oCIS services.
http:
  #-- CORS settings for oCIS services.
  cors:
    #-- allow_origins is a list of origins a cross-domain request can be executed from.
    # If the special "*" value is present in the list, all origins will be allowed.
    allow_origins: ["*", "https://sso.[some domain].io", "https://oc.[some domain].io", "https://[some domain].io"]
...
features:
  basicAuthentication: false
  externalUserManagement:
    enabled: true

Attempt to login

Expected behaviour
Browser Javascript requests to https://sso.[some domain].io should be allowed from OwnCloud
Actual behaviour
Browser Javascript requests to https://sso.[some domain].io are blocked by CORS configuration. :(
Server configuration
Operating system: Ubuntu 22.04 LTS + microk8s
Web server: Whatever is packaged into OCIS Community edition 04.0.1 containers
Database: Whatever is packaged into OCIS Community edition 04.0.1 containers
PHP version: I think it's none? Isn't OCIS composed of golang microservices?
ownCloud version: 4.0.1
Updated from an older ownCloud or fresh install: fresh install
Where did you install ownCloud from: Helm charts
The content of config/config.php: Hopefully all CORS-related config is posted above...
List of activated apps: default set for OCIS 4.0.1
Are you using external storage: No
Are you using encryption: no
Are you using an external user-backend: Janssen Authorization Server
LDAP configuration (delete this part if not used)
    ldap:
      writeable: true
      readOnlyAttributes:
      uri: ldaps://ldap.[my domain].io:1636
      certTrusted: true
      insecure: false
      bindDN: cn=Directory Manager
      refintEnabled: false
      passwordModifyExOpEnabled: false
      useServerUUID: true
      user:
        schema:
          id: inum
          idIsOctetString: false
          mail: mail
          displayName: displayName
          userName: uid
          userType: ownCloudUserType
        baseDN: ou=people,o=jans
        scope: sub
        substringFilterType: any
        objectClass: jansPerson
      group:
        schema:
          id: inum
          idIsOctetString: false
          mail: mail
          displayName: displayName
          groupName: inum
          member: member
        baseDN: ou=groups,o=jans
        createBaseDN: ""
        scope: sub
        filter:
        objectClass: jansGrp
      using an ldap attribute.
      disableUsers:
        disableMechanism: attribute
        userEnabledAttribute: ownCloudUserEnabled
        disabledUsersGroupDN: "cn=DisabledUsersGroup,ou=groups,o=libregraph-idm"

Client configuration
Browser: Chrome, Firefox, Safari (all tested - same results)
Operating system: Windows, Mac, Linux (all tested - same results)

The OIDC server is hosted at: https://sso.[my domain].io
OCIS is hosted at: https://oc.[my domain].io

Expected behaviour
Browser Javascript requests to https://sso.[some domain].io should be allowed from OwnCloud
Actual behaviour
Browser Javascript requests to https://sso.[some domain].io are blocked by CORS configuration. :(

Actually you need to configure CORS on your SSO for this to work.

Thanks for the clarification, @wkloucek . Disregard the above


Replace all non-fatal error!s with warn!s

Right now, we use error!("blah blah") to log a bunch of errors that are non-fatal: we know something is fishy, but not fishy enough to give up on generating bindings completely. These get logged by default and show up as
ERROR:bindgen::foo::bar: blah blah blah

on our users' terminals. This can be scary to users, and make them think something has gone horribly wrong, when probably everything is OK-ish if we generated bindings successfully.
We should replace all non-fatal error!s with warn!s to make them less scary.
Would love to mentor someone on this good first bug.
Steps to fixing are basically:

Evaluate each use of the error! macro

If it is followed by returning an Err(...), then leave it as-is (it is logging for some error that made us give up whatever we were doing)
Otherwise, replace it with a warn! instead

Please make a comment here if you intend to work on this issue. Thank you!

Can I take this?

Sure thing! Let me know if you have any questions!


Cannot install dependencies

It's not possible to install depdencies, when running yarn install, the following error occurs:
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "^10.13.0 || ^12.13.0 || ^14.15.0 || >=15.0.0". Got "14.4.0"
error Found incompatible module.

Make sure to have the correct node version running in your shell.

@emmenko I was using the right node version as indicated in the .nvmrc file.
I retested this morning and the problem is gone now that Yarn v3 is being used.


Vulnerability fix for task ContainerBuildV0

Task name: ContainerBuildV0
Description: Fixed latest vulnerability for task ContainerBuildV0
Documentation changes required: (Y/N)
Added unit tests: (Y/N)
Attached related issue: (Y/N) https://dev.azure.com/mseng/PipelineTools/_componentGovernance/184/alert/83629?typeId=12858
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected
[x] node make.js build --task ContainerBuildV0
[x] node make.js test --task ContainerBuildV0

/azp run

/azp run

/azp run


The photo size is different from camera preview

Steps to Reproduce
Set the photo 3.264x2.448, but the camera preview is in aspect ratio 9:16
Expected results
The photo in preview size
About your device

Brand
Model
OS

Samsung
A-10S
Android 11

You can now choose the preview size correctly from the builder of the new version 1.0.0
By default it's on cover mode.
Don't hesitate to open another issue if you need any help.


Library docs

Any source or docs, ideally Javadoc, available for the cloudhsm library?  For example, I want to do the equivalent of 'findKey -t key_type', which I assume can be done with the Util.findKeys(String, int, int, int, byte[], Vector) method or similar but it's impossible to know what those parameters actually are although one of those ints is presumably the type.  Similarly with other parts of the API, it's not clear what some of the methods do and what they take.
Specific points I'm trying to figure out:

How to find keys based on type (AES, EC etc.), class etc..
How to find all keys (Util.findAllKeys(null) does that return everything?).

Hi @mc-sunw , sorry for the long wait on this one. We have Javadocs available for download on our main client download page.
We have a sample available which could help you locate keys by label and by key type.
At this time, our JCE does not have an option to load all keys however.


cmake: Omit if statement that is always true

We had an if-statement around policy 79 because we used to need to
support CMake versions before 3.13.0. But now 3.13.1 is the minimum
required version so the if statement always evaluates to true and can
be omitted.
Also, drop some comments that are either redundant or wrong.

Codecov Report

Merging #13816 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #13816   +/-   ##
=======================================
  Coverage   52.26%   52.26%
=======================================
  Files         307      307
  Lines       45410    45410
  Branches    10504    10504
=======================================
  Hits        23734    23734
  Misses      16887    16887
  Partials     4789     4789

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 2810b88...a9d41e7. Read the comment docs.


Add capacity features to multi-peer

This targets multi-peer as a base - reviewing this way so we can review just my changes in isolation, before blending with the already large multi-peer changeset

@phongcao correct, by default there is an infinite number of peers

@bengreenier We should document that max_peers setting somewhere so that people are aware of the cool feature that you've just added.

https://github.com/CatalystCode/3dtoolkit/wiki/Multi-peer


fix: cart action button

PR Type

[x] Bugfix

Needs Design check

@exezbcz please review

Context

[x] Closes #7769

Screenshot 📸

[x] My fix has changed UI

could you please apply the same style to the mass list button?

thanks a lot!

could you please apply the same style to the mass list button? ![image](https://user-

✅ Done

or what if we use at least once size prop on button (medium or large)
if it's still not the right size you can try to tweak --oruga-button-font-size-*

OK. It also works.


xargo does not work with dependency "path"

Trying to build steed project with that contains following Xargo.toml
[dependencies.collections]  # `steed` depends on collections
[dependencies.rand]  # and rand

[dependencies.std]
path = "/home/foo/sources/steed"
stage = 1

And it fails
$ cross run --target x86_64-unknown-linux-steed
   Compiling core v0.0.0 (file:///rust/lib/rustlib/src/rust/src/libcore)
   Compiling std_unicode v0.0.0 (file:///rust/lib/rustlib/src/rust/src/libstd_unicode)
   Compiling alloc v0.0.0 (file:///rust/lib/rustlib/src/rust/src/liballoc)
   Compiling collections v0.0.0 (file:///rust/lib/rustlib/src/rust/src/libcollections)
    Finished release [optimized] target(s) in 12.46 secs
   Compiling rand v0.0.0 (file:///rust/lib/rustlib/src/rust/src/librand)
    Finished release [optimized] target(s) in 1.9 secs
error: failed to load source for a dependency on `std`

Caused by:
  Unable to update file:///home/foo/sources/steed

Caused by:
  failed to read `/home/foo/sources/steed/Cargo.toml`

Caused by:
  No such file or directory (os error 2)
error: `"cargo" "build" "--release" "--manifest-path" "/tmp/xargo.Bbhmazhxjks2/Cargo.toml" "--target" "x86_64-unknown-linux-steed" "-p" "std"` failed with exit code: Some(101)
note: run with `RUST_BACKTRACE=1` for a backtrace

But file /home/foo/sources/steed/Cargo.toml definitely exists.

cross run --target x86_64-unknown-linux-steed

Cross uses a docker container and only mounts the Cargo project. IOW, the container doesn't have access to the whole filesystem. Thus, absolute paths won't work; only relative paths that point within the Cargo project will work.
This is not a Xargo bug so closing.


Roll back core-js version

Related to #465

Angular CLI 7.x supports only<EMAIL_ADDRESS>

Seems the travis CI won't be happy unless node-sass release native bindings for node 12 :/
Let's just wait it will solve itself anyways, I will force merge this.


Installing on Cygwin

I am having an issue installing rainbowstream due to python on Cygwin using cp1252 as default encoder:

Complete output from command python setup.py egg_info:

Traceback (most recent call last):
  File "<string>", line 20, in <module>
  File "E:\cygwin\tmp\pip-build-68cao31c\rainbowstream\setup.py", line 31, in <module>
    long_description=open("./README.rst", "r").read(),
  File "c:\python\python35-32\lib\encodings\cp1252.py", line 23, in decode
    return codecs.charmap_decode(input,self.errors,decoding_table)[0]
UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 2898: character maps to <undefined>

I know I need to change it to utf-8 but can't find any easy explanations for how to do this - any help with this much appreciated.

this does install on cygwin, but you probably need more packages than you think. try doing a full cygwin install (if need be, you can leave out gnome, KDE, and the window managers). i had this issue too but after installing more packages it worked. sorry i can't be of more help and tell you which one actually fixed it though.

Thanks for the reply. Tried a full cygwin install on both PC and laptop the latter still can't install it and provides the same error and the former can install it but provides following error when trying to run:

The system cannot find the path specified.
Traceback (most recent call last):
File "c:\python27\lib\runpy.py", line 162, in run_module_as_main
"main", fname, loader, pkg_name)
File "c:\python27\lib\runpy.py", line 72, in run_code
exec code in run_globals
File "C:\Python27\Scripts\rainbowstream.exe_main.py", line 5, in
File "c:\python27\lib\site-packages\rainbowstream\rainbow.py", line 22, in
from .draw import *
File "c:\python27\lib\site-packages\rainbowstream\draw.py", line 15, in
from .c_image import *
File "c:\python27\lib\site-packages\rainbowstream\c_image.py", line 25, in
rgb2short = call_c()
File "c:\python27\lib\site-packages\rainbowstream\c_image.py", line 21, in call_c
image_c = ctypes.cdll.LoadLibrary(library)
File "c:\python27\lib\ctypes_init.py", line 443, in LoadLibrary
return self.dlltype(name)
File "c:\python27\lib\ctypes_init.py", line 365, in init
self._handle = _dlopen(self._name, mode)
WindowsError: [Error 126] The specified module could not be found

do you have python3 and if so have you tried doing 'pip3 install rainbowstream' ?

On PC I unstalled rainbowstream and tried pip3 instead. Unfortunately, it doesn't install providing similar error message to trying to install it via pip & pip3 on the laptop:

Collecting rainbowstream
Using cached rainbowstream-1.3.3.tar.gz
Complete output from command python setup.py egg_info:
cp: failed to access 'E:Programs\cygwin64\home\Alasdair.rainbow_config.json': Bad address
chmod: cannot access 'E:Programs\cygwin64\home\Alasdair.rainbow_config.json': Bad address
Traceback (most recent call last):
File "", line 20, in
File "E:\Programs\cygwin64\tmp\pip-build-73h0laue\rainbowstream\setup.py", line 31, in
long_description=open("./README.rst", "r").read(),
File "c:\users\alasdair\appdata\local\programs\python\python35-32\lib\encodings\cp1252.py", line 23, in decode
return codecs.charmap_decode(input,self.errors,decoding_table)[0]
UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 2898: character maps to
Command "python setup.py egg_info" failed with error code 1 in E:\Programs\cygwin64\tmp\pip-build-73h0laue\rainbowstream

I'm sorry RS is not officially support Window environment, even inside Cygwin. I'm not sure if people made it worked or not, but i highly recommend using a Linux/Mac environment so you can save all the headache

No problem, I thought that was the case but wasn't sure if someone had unofficially figured out a way to get it to work. From what I've found searching about there are folk like urbster1 where its worked after installing other packages, but not sure which exact ones, and then folk like me where it just doesn't seen to work, even after a full install. Managed to install it easy enough on my raspberry pi, and can always ssh into it from PC and laptop.


AudioStreamSample: Don't crash when writing to file fails

AudioStreamSample::save_to_wav would crash Godot if you tried to save to a path that didn't exist or where it had no write access. I also changed it to return Error so the developer can react in such cases, this shouldn't be a BC break as the method didn't return anything previously but maybe this PR can also still slip into 3.1 :)
Docs for the method were added as well.

Note: The CI report is messed up due to GitHub's oops from half an hour ago, it's tracking the wrong PR. This branch did build fine on Travis.

Thanks!


fix stderr for monitoring

Minor fixes for stderr for monitoring
partially for #987
[Discussion?] Issue #987 mentions only File type inputs/outputs should be logged. But currently, the monitoring logs any types of inputs, and only the outputs that are already specified when the app is submitted (actually only str type as a file path I think).
Do you think the monitoring should be kept in current version right now?

If we're logging stdout/stderr paths, we should also log stdin paths as before - that is, it is OK for this PR to add in a capture for stderr path, but it is not OK for this PR to remove the capture of the stdin path.

[Discussion?] Issue #987 mentions only File type inputs/outputs should be logged. But currently, the monitoring logs any types of inputs, and only the outputs that are already specified when the app is submitted (actually only str type as a file path I think).

The input/output file types are a little informal. If a user passes in a File object, staging behaviour can happen. However, they can pass in arbitrary other python objects without error (I think), and staging will not happen (and is not even defined). #1016 contains some discussion on this.

don't remove stdin

Fixed now.


Workflow status definition

Hi @danblah ,
Here is Todd's document which outlines:

the current statuses within the system including their intended usage and behaviour
our proposed changes/additions to the statuses

Please review these statuses and proposed changes with the team and feedback to us whether you think these proposed changes would fit your workflow or whether any further discussion is needed. Please feed back to us by end of Monday next week.
There are also two associated tasks which we describe in the document:

applicant friendly statuses
automated transitions between statuses

Once we agree on the internal OTF statuses I suggest we then tackle these points.
Thanks,
Maya

Yep, we're all good here as well.


Minimize/remove occurrence of widows while still showing all the images

Is there a way to minimize the occurrence of widows in the image gallery, but still showing all of the images?
For example, the Unite library never has widow images, but it also never crops the images (and shows all images), and it seems like that is all done without adjusting the images' heights too much.
I really like your library (minimal UI, small size, implementation up to me), but I won't be able to use it until there aren't widow items.

The doc indicates that you can set option showWindows to false.
http://flickr.github.io/justified-layout/

Yes, we recommend using showWindows to suppress them if you need to guarantee a clean bottom edge.
Beyond that, justification is an intricate process between individual photo sizes and your requested display parameters. There are many tools available to engines to create a layout between vertical/horizontal cropping, row geometry tolerances, enlargement, rearrangement, and a few other characteristics. Our engine prefers to avoid cropping wherever possible at the cost of incomplete trailing rows.


Mixpanel using legacy support libs in reflection calls - can't drop jetifier due to this

See https://github.com/dipien/bye-bye-jetifier/discussions/15 and specifically the comment https://github.com/dipien/bye-bye-jetifier/discussions/15#discussioncomment-186714.
Jetifier is used on android to make old code that uses legacy android support libraries work with newer androidx libraries. Mixpanel seems to use android.support.v4.content.LocalBroadcastManager inside https://github.com/mixpanel/mixpanel-android/blob/master/src/main/java/com/mixpanel/android/mpmetrics/MixpanelAPI.java via reflections for something.
You should probably straight up either remove the old one and use androidx, or do like AppCenter and attempt the reflection calls with either the old or the new package/class. See https://github.com/microsoft/AppCenter-Test-Espresso-Extensions/blob/master/src/main/java/com/microsoft/appcenter/espresso/Factory.java for that.

I could probably drop jetifier without this change/fix, as it's probably not checked at compile-time whether reflection calls will succeed. But then I am at risk of runtime crashes when Mixpanel calls that code.


Enhanced readme

Resolves #1
Added a CONTRUBUTING.md to /docs
Updated README.md

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@867d0ae). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             dev       #5   +/-   ##
======================================
  Coverage       ?   11.42%
======================================
  Files          ?       13
  Lines          ?      315
  Branches       ?       37
======================================
  Hits           ?       36
  Misses         ?      279
  Partials       ?        0

Flag
Coverage Δ

#unittests
11.42% <0.00%> (?)

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

Continue to review full report at Codecov.

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

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@867d0ae). Click here to learn what that means.
The diff coverage is n/a.

@@          Coverage Diff           @@
##             dev       #5   +/-   ##
======================================
  Coverage       ?   11.11%
======================================
  Files          ?       13
  Lines          ?      306
  Branches       ?       37
======================================
  Hits           ?       34
  Misses         ?      272
  Partials       ?        0

Flag
Coverage Δ

#unittests
11.11% <0.00%> (?)

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

Continue to review full report at Codecov.

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


cutted way filled in route in oposite direction

We have lots of errors in bus-route relations from iD-Editor-users. The editor seems to look sensible for the way to paste the cutted way, but then uses the oposite direction to paste.
Example: way/334914447 relation/1732028 (going east) and relation/1732029 (going west)
changeset/105406069  I cut the way in two ways way/334914447 and way/947627779
In result both relations are sorted in the wrong order of ways at way/334914447 and way/947627779.

If you think this can be tackled by a beginner, i'd love to do it. How do I start?

How do I start?

I would start by reading all the comments about relations in this Repo - especially from the maintainers / core committer – especially about ordering member. This will likely show that routes in general and in ID are not an easy topic.

#8839 will fix this regression.


[14.0] ISPN-14738 RESP endpoint commands don't require previous value

Add IGNORE_RETURN_VALUES flag as well

https://issues.redhat.com/browse/ISPN-14738

This fixes the wrong commits in https://github.com/infinispan/infinispan/pull/10776


Ability to replay google searches

When making a google search, Google adds random gibberish to the end of the URL. So when you webrecord a google search, you won't be able to replay the search - hitting the button will generate a new string of gibberish, and it will show as page not found. is there a way that webrecorder could ignore the random parts of the url, and give you the recorded results page when you reperform the search in replay mode? This has come up for me more than 1x -
recent example
Google search page:
https://webrecorder.io/michaeleatsfood/google-searches/20180612145914/https://www.google.com/?gws_rd=ssl
Trying to reproduce my search ("hello") yields:
The url https://www.google.com/search?source=hp&ei=wt8fW6DlLsyTzwKtt4y4BQ&q=hello&oq=hello&gs_l=psy-ab.3..0l4j0i131k1j0j0i131k1j0l3.886.1371.0.16<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>....0...1.1.64.psy-ab..1.4.166....0.VznbaPErFFU was not found in the archive.
archived results page:
https://webrecorder.io/michaeleatsfood/google-searches/20180612145957/https://www.google.com/search?source=hp&ei=wt8fW6DlLsyTzwKtt4y4BQ&q=hello&oq=hello&gs_l=psy-ab.12...<IP_ADDRESS><IP_ADDRESS>.<IP_ADDRESS>.0..0.0....0...1..64.psy-ab..0.0.0....0.AqahdaLaFYc
Basically everything after gs_l seems like gibberish.
here is an old example, I seem to recall that this once worked:
Google Search page:
https://webrecorder.io/michaeleatsfood/juliaweistreach/list/bookmarks/b9/20150709131257/https://www.google.com/webhp?hl=en#hl=en
Trying to recreate my recorded search ("parbunkells") lands me on
https://webrecorder.io/michaeleatsfood/juliaweistreach/list/bookmarks/b9/20150709131257/https://www.google.com/webhp?hl=en#hl=en&q=parbunkells
https://webrecorder.io/michaeleatsfood/juliaweistreach/20150617150801/https://www.google.com/search?q=parbunkells

This would be specifically helpful for archiving Therevolvinginternet.com - the proposal is to make a webrecorder recording of various google searches, and then embed the webrecorder recording within the rotating iframe :-/

Relevant parameters:
?q=boop (I searched boop)
Optional params If people use search tools:
&tbs=qdr:h (past hour)
&tbs=qdr:d (past day)
&tbs=qdr:w (past week)
&tbs=qdr:m (past month)
&tbs=qdr:y (past year)
&tbs=cdr%3A1%2Ccd_min%3AYYYY%2Ccd_max%3AYYYY (from YYYY to YYYY)
&tbas=0 is default, but this param seems unecessary.
&tbm=isch IMAGES
&tbm=vid VIDEO
&tbm=shop Guess
I couldnt figure out a parameter for language - it seems to have to do with cookies.

Other params:
PARAMS THAT SHOW WHEN LOGGEDOUT
&oq=boop (ORIGINAL QUERY?)
&aqs=chrome.0.69i59j69i61l2j69i60.1228j0j1
&sourceid=chrome
&ie=UTF-8
PARAMS THAT SHOW FOR A LOGGED IN USER ONLY
&tbas= - probably a token thing - ignore
&source= surveillance gibberish
&sa - gibberish
&ved - seems like gibberish
&biw - only when logged in, for me it's always 1098
&bih=639
&dpr=2.5

so in summary, definitely don't ignore &tbm, and &tbas is relevant if not 0

@ikreymer im sorry to bother - i need to know if this is likely to/possible to happen soon (like in the next few days?), otherwise i'll plan to proceed without it!


[4.2] Fix linux s390x build (pr36694)

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@327379 91177308-0d34-0410-b5e6-96231b3b80d8
(cherry picked from commit d768f36b02dce5d9b2d58de886bf76646bb79925)
Was waiting for the merge from stable branch but it's been failing for almost a week so I'm opening a PR for 4.2.
Same PR as https://github.com/apple/swift-lldb/pull/380

Ping?  Would like to bring the 4.2 build on s390x back to green again.  Thanks.

Fix is now in 4.2 branch.  Will close this.


create header

On it.....

Created the header for the plugin "company sales"
Test Link: https://sales.zuri.chat
PR Link: https://github.com/zurichat/zc_plugin_company_sales_prospect/pull/227
Slack Username: jamil


Tilbakemelding
Should not the HelpText Popover have role tooltip?
https://www.w3.org/WAI/ARIA/apg/patterns/tooltip/

Hi 👋 Since our <HelpText /> does not show on hover or focus and is not connected to anchor with aria-describedby we think the role tooltip could be misleading in this case.
In some cases the HelpText could contain quite a bit of information, so to avoid screen readers automatically getting presented this, they can opt to navigate inside the popover if needed.

The element that triggers the tooltip references the tooltip element with aria-describedby.

element when the element receives keyboard focus or the mouse hovers over it

Good point! :)


Add stub template for Community Experience WG

TODO before merge:

Identify leads for WG
Identify initial goals and scope for WG
List main technical assets for WG

This PR supersedes #144: the content is identical, but it pulls from the wg-community-experience branch on the CF-org community repo instead of the one on my personal fork so that the other TOC members can revise it.

As an alternative to forming this working group, we could instead put the existing docs repos under the governance of the most relevant technical working group. The Foundational Infrastructure WG has already done this with most of the docs repos for BOSH and CredHub (namely, docs-bbr, docs-bosh, and docs-credhub), and the App Runtime Interfaces WG has also done this for docs-buildpacks.
This would require some existing WGs to take on more scope and to add active contributors to these repos (such as @mjgutermuth, @animatedmax, and @jncd) as Approvers to ensure their ongoing access, likely in a new area of the WG.
Here's my pass at how the remaining docs repos would get placed within the current WGs:

Repo
Site
Candidate WG
Notes

api-docs
apidocs.cloudfoundry.org
AR Interfaces

credhub-api-docs
docs.cloudfoundry.org/api/credhub
Foundational Infrastructure
Move from cf-incubator org

cf-for-k8s-docs
cf-for-k8s.io
None
Archive as not maintained

docs-book-cloudfoundry
docs.cloudfoundry.org
AR Platform

docs-cf-admin
docs.cloudfoundry.org/adminguide
AR Platform

docs-cf-cli
docs.cloudfoundry.org/cf-cli
AR Interfaces

docs-cfcr
docs.cloudfoundry.org/cfcr
None
Archive as not maintained

docs-cloudfoundry-concepts
docs.cloudfoundry.org/concepts
AR Interfaces

docs-dev-guide
docs.cloudfoundry.org/devguide
AR Interfaces

docs-dotnet-core-tutorial
None?
None
Archive as not maintained

docs-loggregator
docs.cloudfoundry.org/loggregator/architecture.html
AR Platform

docs-routing
None
None
Archive as obsolete

docs-running-cf
docs.cloudfoundry.org/running
AR Platform

docs-services
docs.cloudfoundry.org/services
AR Interfaces

docs-uaa
docs.cloudfoundry.org/uaa
Foundational Infrastructure

@rkoster @beyhan @ameowlia @Gerg, as the leads for the WGs that would take on these docs repos, could you please provide feedback on this proposal? Thanks!

@Gerg @ameowlia: I'd still like your feedback on the proposal above to move some CF docs repos into the scope of your working groups. Thanks!

As it currently stands, most of the docs.cloudfoundry.org/* repos are managed by a different set of people than are currently in the existing working groups. I think it makes sense to have a Community Experience WG to reflect this current reality. If we want to transition to a model where these docs are maintained by the other WGs, then we can do that as its own initiative.
That said, there are some (generally API) docs that are maintained by existing WG teams:

https://apidocs.cloudfoundry.org
https://v3-apidocs.cloudfoundry.org/
https://cli.cloudfoundry.org/en-US/v8/
https://docs.cloudfoundry.org/api/uaa
etc

I think it makes sense for those to fall into the associated WG. Of the repos you listed, I think this only applies to https://github.com/cloudfoundry/api-docs.

I had a follow up discussion with Eric. There probably aren't enough people currently contributing to the docs repos to support an entire working group. As an alternative, we can add a "Documentation" (or Community Experience") team to each of the existing working groups.

I like @Gerg's alternative mentioned above. I wish there was enough contributors to justify a docs working group, but here we are. @emalm your mapping of docs to WG makes sense for ARP.

@Gerg @ameowlia Thank you both! Generated https://github.com/cloudfoundry/community/pull/190 to propose these additions to the existing working groups. I will close this PR as obsolete now, and we can proceed from the new one.


Deprecate nltk.usage(obj) in favor of help(obj)

Fixes #2807
Hello!
Pull request overview

Started deprecation of nltk.usage(obj). In this PR, it throws a warning and then calls help(obj).
Removed tests for nltk.usage.
Removed a classify.doctest test that used nltk.usage, and reworded the documentation there.

See #2807 for discussion on the deprecation.

Changes
My idea is to roll out a somewhat smooth deprecation. Rather than simply removing the function in the next version, it'll start throwing a warning indicating the pending deprecation. Then, because nltk.usage() was broken for certain classes (e.g. nltk.FreqDict), it now calls help(obj) instead.
If this is merged, then another PR can be created some time in the future, for a future version, which fully removes this function.
Please post any discussion regarding whether nltk.usage ought to be deprecated or not in #2807, and feel free to comment here on any suggestions about how the deprecation should be rolled out.
Note
The warning will only be displayed if Python is ran with e.g. a -Wd or -Wall flag, indicating that warnings must be shown.

Tom Aarsen

@tomaarsen good idea

Would it make sense to use logging.warning here to display the message without expecting the user to pass flags to Python?

warnings.warn is used some 34 times in the codebase, while logging.warn is never used.
That said, using logging does mean that all users are shown the warning, unless they change the logging settings.
I'm up for either warnings or logging.

I'd say let's stay consistent in this case and use warnings. I wonder how many people actually know that the output of that module is suppressed by default. I was definitely surprised to learn this.

It definitely surprised me too. I wouldn't have expected it.

It seems that one place in the codebase use this sneaky workaround to ensure that the warning is thrown:
https://github.com/nltk/nltk/blob/d21646dbd547cdd02d0c60f8e23d1d28a9fd1266/nltk/tokenize/stanford_segmenter.py#L71-L82
However, I'm definitely not a fan of exactly how it is done, as people often have reasons for their warning filtering, and this just sets it back to "ignore" afterwards, even if users set it to "always" themselves.

But, perhaps gathering the current filter(s), setting to "always", raising the DeprecationWarning, and resetting the filter to what it was previously might be smart. I'm not sure if that's "proper" though.
Oh, and regarding the StanfordSegmenter snippet, I'll have a look at that.

Ah, good find! Use that :)
One thing to check for the future is if functools.wraps can be used to update the meta-data of the function being decorated. My guess is yes, but maybe there's some backwards-compatibility issue I'm not aware of.

@iliakur I was under the impression that functools.wraps has issues preserving the docstring and signature of functions of wrapped methods. At least, that was my conclusion when I attempted to use it a few years back.
I managed to find the commit that described my issue: https://github.com/tomaarsen/TheNounProjectAPI/commit/d338927f62ee43995c51cb4fc28a8355ba93276d.
When using @wraps on a method, the signatures of wrapped functions into *args, **kwargs, i.e. the signature of the wrapper. That said, I might have just used it wrong.
And I will simply start using @deprecated.

Ah, I'll have to look into this, it's something new to me. I don't actually use wraps that often myself. We could consider adding wrapt as a dependency. Or the decorator package?

I've made the update - it now uses @deprecated (Also, apologies to the GitHub user who has that as their username, I didn't mean to tag you in my commit message)
The output is now as follows:
>>> import nltk
>>> nltk.usage(nltk.tokenize.NLTKWordTokenizer)
<stdin>:1: DeprecationWarning:
  Function usage() has been deprecated.  Use help(obj) instead.
NLTKWordTokenizer supports the following operations:
  - self.span_tokenize(s)
  - self.span_tokenize_sents(strings)
  - self.tokenize(text, convert_parentheses=False, return_str=False)
  - self.tokenize_sents(strings)

Thanks @tomaarsen, @iliakur