Custom Assertion Messages

This pull request adds the possibility to add custom assertion messages when using assert. This allows to give better feedback when running a test suite. A simple example for that might be the following:
test "failed custom assertion" do
  assert(string.empty?, "not empty")
end

This gives better feedback, because it gives a reason for the failure.
It also makes the step to a custom assertion very easy when we find that we need this kind of assertion multiple times:
def assert_empty(string)
  assert(string.empty?, "not empty")
end

test "failed custom assertion" do
  assert_empty "foo"
end

Background
This arose from a discussion with @tonchis. We talked about his assert-url library. He told me that his library is agnostic of test frameworks, and he explained to me how he managed to do that. It has a drawback though: As it doesn't use flunk and success, it can't do the same kind of reporting that a built-in or cutest-specific assert_* can do (e.g. put a dot onto the command line when it succeeds). And it can't use flunk and success, because this is very specific to cutest. So we discussed the following:
[13:33:47]  <moonglum>	My gut reaction would say that if you write a lib that's providing assert_* methods there's one thing you can assume: The person that is using your lib uses assert_* methods (so not Rspec's expect for example).
[13:34:02]  <moonglum>	So I guess it would be save to assume that there's a `assert` method available?
[13:34:09]  <tonchis>	it's a reasonable assumption, yes
[13:35:04]  <moonglum>	So if your lib can break everything down to an `assert` it would be fine, right? In the sense of `assert` can be used as the building block for all assertions
[13:35:40]  <tonchis>	also true
[13:35:42]  <moonglum>	But the problem I see here is that cutest doesn't offer an 'explanation string' in its assert as many frameworks do
[13:36:00]  <tonchis>	yeap
[13:36:04]  <moonglum>	assert false, "EXPLAIN EXPLAIN"
[13:36:33]  <tonchis>	that's useful, may be you can propose it to jano and see what he thinks of it
[13:36:58]  <tonchis>	it wouldn't be hard to implement either, I think

Example for custom assertions with the "new assert"
@tonchis' assert_schema_equal:
def assert_scheme_equal(expected, value)
  value = urify(value).scheme

  assert(expected.to_s == value, "Expected #{value} to have the following scheme: #{expected}"
end

In my opinion: Better error reporting with the same amount of understandable code.
Impact

Add optional message argument to assert
Reimplemented assert_equal and assert_raise with assert
Totally backwards compatible as the new argument is optional
Adds little to no complexity, and even removes two lines of code
Introduces a way to add custom assertions in a straight forward way (without using flunk and success)

Ping @djanowski :smile:

On it.

I added a commit to make the test work, but it currently fails.
The problem is that the reported line is not the line in your test, but the line that calls assert.

  test: failed custom assertion
  line: assert(string.empty?, "not empty")
  file: test/fixtures/fail_custom_assertion.rb +2

Cutest::AssertionFailed: not empty

When it should be:

  test: failed custom assertion
  line: assert_empty "foo"
  file: test/fixtures/fail_custom_assertion.rb +6

Cutest::AssertionFailed: not empty

Any ideas?

@moonglum If you want you can cherry pick 1c5dc22c3dd6876fe1661253bbb96067f5b22b58 so that it appears on this PR.

Thanks for your feedback :smile: I rebased and cherry-picked your commit! Let me investigate!

Wait, I think there's something wrong in your commit:
test "output of an assertion with custom message" do
   expected = "\n" +
              "  test: failed custom assertion\n" +
              "  line: assert_empty \"foo\"\n" +
              "  file: test/fixtures/fail_custom_message.rb +7\n\n" +
              "Cutest::AssertionFailed: not empty\n\n"

   # you deleted this line:
   # out = %x{./bin/cutest test/fixtures/fail_custom_message.rb}
   # and added this line instead:
   out = %x{./bin/cutest test/fixtures/fail_custom_assertion.rb}

   assert_equal(expected, out)
end

You can see in the expected message that the file is test/fixtures/fail_custom_message.rb and that's the file I executed beforehand. You changed it to execute a different file. Can you check that again?

Ok, I adjusted the PR. Now I can see the test failure you described. The problem is that in this case the correct line would entry in the caller array would be at position 2, not 1. Phew, tricky.

Proposal for a solution:
Commit b05a7ea satisfies all tests. In addition it gets rid of a magical number (the 1 in the backtrace). It changes the way that cutest determines the correct line of the backtrace. What do you think, @djanowski? :smile:

Thank you, @moonglum.

Thank you so much :smile:


Unhelpful type error using Converter where StreamTransformer expected

This error message repeats itself. I'm also not sure what I could do about it.
149: [ERROR] Type check failed: new Utf8Decoder() (Utf8Decoder) is not of type StreamTransformer<List<int>, dynamic> because new Utf8Decoder() cannot be typed as StreamTransformer<List<int>, dynamic> [STRONG_MODE_STATIC_TYPE_ERROR]

The code seems pretty straightforward:
    _process.stdout
        .transform(new Utf8Decoder())
        .transform(new LineSplitter())
        .listen((String line) { .. }

Could swear we had a bug for this, but I can't find it. In any case, yeah we need to fix that message. @munificent might be able to take a look?

The error message can definitely be improved, but it also appears fish. A simpler standalone repro is:
import 'dart:async';
import 'dart:convert';

main(Stream<List<int>> stream) {
  stream.transform(new Utf8Decoder());
}

Let's walk through the types:

Stream<T>.transform() expects a StreamTransformer<T, dynamic>.

Utf8Decoder extends Converter<List<int>, String>.

Converter<S, T> implements StreamTransformer without any type parameters. Shouldn't it implement StreamTransformer<T, S>?

If I cobble together a synthetic example that fixes that:
class MyTransformer<S, T> {}
class MyConverter<S, T> implements MyTransformer<S, T> {} // <--
class MyDecoder extends MyConverter<List<int>, String> {}
class MyStream<T> {
  void transform(MyTransformer<T, dynamic> transformer) {}
}

main(MyStream<List<int>> stream) {
  stream.transform(new MyDecoder());
}

Then indeed the error goes away. @lrhn or @floitschG, is the core library wrong? Can I fix it?

cc @vsmenon @leafpetersen

This was a deliberate choice. The stream-transformer doesn't always use the same source and output type.
(See https://codereview.chromium.org/1698563002/ )
There is no way to fix this, without adding more generic types to codecs, which we decided not to do when we designed the API.

The stream-transformer doesn't always use the same source and output type.

Yes, I see that, but Converter is one-way anyway, so that doesn't seem like a problem to me. I would expect bind() to be Stream<T> bind(Stream<S> source) in Converter, but it isn't. What am I missing?

There is no way to fix this, without adding more generic types to codecs

Is this because of fuse()?

which we decided not to do when we designed the API.

Time to revisit that decision?

Let me rephrase: The stream-transformer doesn't always use the same source and output type as the codec.
You just LGTMed a CL where that's not the case.

The stream-transformer doesn't always use the same source and output type as the codec.

I'm not sure what you mean by "the stream-transformer" and "the codec".  Are these the same objects? There are no Codecs mentioned by this issue, just Converter.

You just LGTMed a CL where that's not the case.

Yes, though I admit I didn't fully understand the change. :-/
Let me try asking this a different way. With generic methods, can we make this API type safe? Should we?
I don't know streams very well, but my expectation is that the classes in question would look something like:
class Stream<S> {
  Stream<T> transform<T>(StreamTransformer<S, T> transformer) {
    return streamTransformer.bind(this);
  }
}

abstract class StreamTransformer<S, T> {
  Stream<T> bind(Stream<S> source);
}

abstract class Converter<S, T> implements StreamTransformer<S, T> {
  Stream<T> bind(Stream<S> source) => source.map(convert);

  T convert(S input);

  Converter<S, U> fuse<U>(Converter<T, U> other) { ... }
}

class LineSplitter implements Converter<String, List<String>> {
  List<String> convert(String input) => input.split("\n");
}

Does this look right?

It is simply not true that abstract class Converter<S, T> implements StreamTransformer<S, T>
For LineSplitter it would be:
class LineSplitter implements Converter<String, List<String>>, StreamTransformer<String, String>
Therefore Converter can not set the generic types of StreamTransformer. A subclass of Converter inherits StreamTransformer from Converter and can't update the type anymore. It can "only" update the type of the bind method (which is, what we do).

It looks like the simplest fix here is to have:
class Converter<S, T> implements StreamTransformer<S, dynamic>

Converter<S,T>.bind takes the same input type - and we can validate that - but does not promise to return the same return type as StreamTransformer<S,T>.bind.
Is that true in general?

No. It isn't.
It's not the best example, but a LineConcatenater would take List<String> for convert, but take simple Strings otherwise.

It's not the best example, but a LineConcatenater would take List for convert, but take simple Strings otherwise.

Given these cases, why does Converter claim that it implements StreamTransformer at all? Or, if it's going to, why not provide distinct type parameters for them?
What's the type safe way for us to untangle this?

I agree with Bob.  If we want to support that sort of example, Converter should not implement StreamTransformer.
Much cleaner to say:
LineConcatenater implements  Converter<List<String>, String>, StreamTransformer<String, String>

if that is the intent.  Why not make this change?

Because a converter has a chunkedConversion (which is basically the synchronous version of the StreamTransformer). The chunkedConversion is not part of the StreamTransformer interface, but the Converter interface.

If it's not in StreamTransformer how does it affect this?

Because the Baseclass of Converter provides a default-implementation of StreamTransformer based on chunkedConversion. Since there is a default-implementation, it only makes sense that it also advertises that capability.

Because the baseclass of Converter provides a default-implementation of StreamTransformer based on chunkedConversion.

That makes sense.

Since there is a default-implementation, it only makes sense that it also advertises that capability.

In that case, it would be great if it advertised the correct types that capability provides and requires. Should we add more type parameters to Converter so it can distinguish between its bind() interface and its convert() one? Treating them as having the same type is obviously wrong, but treating them as completely untyped isn't very helpful either.

I don't see a chunkedConversion method on Converter:
https://github.com/dart-lang/sdk/blob/master/sdk/lib/convert/converter.dart
There is a similarly named method, but it just throws.

Yes. It's startChunkedConversion.

It just throws ... why do we need to advertise that capability?  I'm not following you.

The Converter class is an abstract class. The startChunkedConversion function should be implemented by the converter if it supports chunked conversions (and thus stream transformations). If it doesn't it will throw at runtime. (This is similar to some lists not supporting changing their size).
If implemented, startChunkedConversion will be used by the base-implementation of the StreamTransformer functionality. This means that the synchronous startChunkedConversion is used by the asynchronous StreamTransformer, and since there is a default implementation of the StreamTransformer functions, Converter implements StreamTransformer.
The type-wise sound thing would be to pass 4 generic types to a Converter: 2 for the non-chunked conversion, and 2 for the chunked conversion.
Initially, we implemented converters this way, but soon discovered that the additional 2 arguments are too cumbersome. Not only do users generally think of Converters going from S to T (and not going from S to T, but also from S2 to T2), the additional arguments also don't apply to converters that don't implement the chunked conversion. Given our experience with the 4 generic arguments, we made the deliberate change to go to 2 generic types and setting the (static) type of the StreamTransformer to dynamic->dynamic.
Although we did remove the 2 generic types for the chunked conversion, we encourage implementers to override the bind method to give it a more precise type. This means that, dynamically, most bad uses of transformers are caught.
I would have prefered if subclasses can tighten their generic types (so that the analyzer could more easily see what's going on), but dart2js doesn't support multiple implements of the same type. Also, according to the semantics the interface types would be combined and not tightened.
class A<T> {}
class B extends A {}
class C extends B implements A<int> {}

main() {
  print(new C() is A<int>);  // => true.
  print(new C() is A<String>);  // => true.
}

In any case, even if I wanted to change the code it's not something we could do. Adding 2 more type-arguments to the Converter class is a breaking change, as would be removing the StreamTransformer interface from Converter.

It sounds like the strong mode type system needs to special-case stream converters (to preserve backward compatibility).

Yes, we'll need to either:

Expand the type system to capture this example.
Find a minimal & acceptable breaking change to type this.

We'll explore option 1 first and update here.  Longer term, we may want to find a better typing regardless.

OK, I've made the error message better here, which is all I plan to do right now, so I'm going to unassign myself and update the title.

Thanks. In the meantime, is there a workaround? Some other way of writing the code?

I'm not sure, but this feels to me like high priority. I believe @vsmenon was looking into some type system workarounds.

@skybrian : This should suppress the static warning for now.
    _process.stdout
        .transform(new Utf8Decoder() as StreamTransformer<List<int>, dynamic>)
        .transform(new LineSplitter() as StreamTransformer<String, dynamic>)
        .listen((String line) { .. }

This is blocking making the crypto package strong-mode clean. We have several APIs like the following:
abstract class Hash extends Converter<List<int>, Digest> {
  ByteConversionSink startChunkedConversion(Sink<Digest> sink);
}

This fails in strong mode because (Sink<Digest>) → ByteConversionSink is not a subtype of (Sink<dynamic>) → ChunkedConversionSink<dynamic>.

As for the larger issue: as far as I can tell, LineSplitter is the only instance where we have a Converter<S, T> that isn't also a StreamTransformer<S, T>. And the only reason there's a difference there is so that LineSplitter.convert() can return a List<String>—and as far as I know, that method is entirely redundant with the LineSplitter.split() static method anyway. So it looks like we don't actually get any concrete value from having Converter<S, T> not implement StreamTransformer<S, T>.
I propose that we make LineSplitter.convert() return a single string—either the first line, or the lines split and rejoined in a more normalized way, whatever—and make Converter<S, T> implement StreamTransformer<S, T> which makes the rest of the world much simpler.

Removing analyzer labels on this issue. I think the analyzer is doing the right thing here – we need to revisit this API design

My understanding was that the analyzer-strong-mode label was being used in part to track issues that are blocking strong mode adoption, which this is.

yeah. I wonder if we should rename analyzer-strong-mode to just strong-mode?

@floitschG any updates?

@floitschG update please?

With 50bdab3841dafd9b056b1dd013c103ce6a566f60 the converters can have full type information.
The patch is a transitional patch to give users time to adjust their code (since it's a breaking change).
The existing converters (of the core libraries) are adapted.

@floitschG Why doesn't ChunkedConverter implement StreamTransformer<S2, T2>?

@nex3: that is where we want to get to. However, we can't just break everyone in a dot-release.
The conversion library is now set up in a way that users can migrate their code. In a future release we will then do the breaking change and make Converter not extend StreamTransformer (and instead make ChunkedConverter extend it).
I will send out a migration mail when 1.16 is released.

@floitschG I think this is fixed in the latest dev release, is that correct?

Just verified this is fixed:
import 'dart:io';
import 'dart:convert';

main() async {
  var p = await Process.start('ls', ['-l']);
  p.stdout
        .transform(new Utf8Decoder())
        .transform(new LineSplitter())
        .listen((String line) { print(line); });
  await p.exitCode;
}

$ dartanalyzer --strong test.dart
Analyzing test.dart...
No issues found!


[Command] "Start" button shows above file drop overlay

When dragging a file to drop it in the command form, any buttons show above the overlay.

Requirements

[ ] Make sure overlay is showing above all elements (add z-index)

Fixed in 96c9defed1652707026849e43a90306f08d8aee4.


Fix coordinates for Pillow>9.4.0

As of Pillow 9.5.0, it is required that x1 >=x- and y1>=y0. See this PR for discussion. Pillow docs state that for ImageDraw.rectangle, xy is a

Sequence of either [(x0, y0), (x1, y1)] or [x0, y0, x1, y1], where x1 >= x0 and y1 >= y0. The bounding box is inclusive of both endpoints.

Simply switching the order of y1 and y2 fixes the following error for all subsequent versions of Pillow:

ValueError: y1 must be greater than or equal to y0

Looks goods to me, thanks!


added env file, api base file, http example for event and fixed cors errors

in /src/components/API.ts there are two exported variables:

apiUrl: a string value contains the backend api url
http: an axios (js library to call rest apis) instance that can be used to call backend apis

/src/components/events/EventsService.ts contains the api calls for events (can be used as an example).

FYI:
@bestksl i added cors configuration to springboot app.
@RobertZSun i added backend http call example.

i think i have created my current branch from the previous one (that was rejected).
i will try to exclude the previous pull request from this one.

i am closing this one (and create new one) to fix the issue.


fix: zk registry bug

close https://github.com/alipay/sofa-rpc-node/issues/33

wait https://github.com/node-modules/zookeeper-cluster-client/pull/10

<EMAIL_ADDRESS>


When run zookeeper-server-start.bat, always get the error: The filename, directory name, or volume label syntax is incorrect.

To start zookeeper, I used the following command in Windows:
kafka>.\bin\windows\zookeeper-server-start.bat .\config\zookeeper.properties
But I got the follow error:
The filename, directory name, or volume label syntax is incorrect.
What is wrong with that?
Thanks!

to start zookeeper the "zookeeper-server-start.bat " file have to run with "zookeeper.properties" and generally  "zookeeper-server-start.bat" file stored in "kafka/bin/zookeeper-server-start.bat" and "zookeeper.properties" stored in "kafka/config/zookeeper.properties".
and for running zookeeper run this command:
bin/zookeeper-server-start.sh config/zookeeper.properties

Hi @kelvingao2020 did you get any solution for the above error?


b2sum: init at 20160619

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

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

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Note that b2sum is already part of coreutils since release 8.26
root@link> readlink $(which b2sum)
/nix/store/jd2j5s966bwhgvrj9fw1jjrxr8m0m33r-coreutils-8.29/bin/b2sum

Since this is in stdenv, I don't think there's any need for this package I'm afraid?

I'm not really sure I buy argument 1 that having multiple hash functions is necessarily worth adding this package. People always think they can choose something better because of their particular know-how, but the actual users who can do this are relatively small -- to the detriment and confusion of other, more ordinary users. BLAKE2b is a perfectly fine and robust hash function for the use-cases b2sum is intended for (file hashes, more or less), and it should already be faster than MD5 or sha1sum which I'd consider unsafe, not to mention SHA2 variants:
root@link> dd if=/dev/urandom of=test bs=1024 count=$((1024*1024))du -sh test
1048576+0 records in
1048576+0 records out
1073741824 bytes (1.1 GB, 1.0 GiB) copied, 17.3029 s, 62.1 MB/s
root@link> cat test > /dev/null # prewarm disk cache
root@link> time md5sum test
e99888c6e9ace85a6bd5716e10355526  test
md5sum test  1.48s user 0.08s system 99% cpu 1.556 total
root@link> time b2sum test
e02d2c9dfe6b6216a5c81d155f75875c15ca51ffdcfea8ae1e984d6862f449212b4eb2e6bc8506d4162a1a254753327df7cc58510a4474b9d8887c8afb06ac7a  test
b2sum test  1.30s user 0.09s system 99% cpu 1.389 total
root@link> time sha1sum test
f449d243faec4e432e69b6d36114b9d6bf9d1407  test
sha1sum test  1.53s user 0.12s system 99% cpu 1.654 total
root@link> time sha256sum test
55d0fffd7e5b9377be427f1ef82557ab4d5a37bb3098c428a831dc51cdfcf163  test
sha256sum test  3.75s user 0.10s system 99% cpu 3.855 total

Personally, I consider "algorithm flexibility" for things like this -- that are mostly inconsequential and confusing to non-familiar/'crypto' users -- to be anti-features.
While blake2b is a 64-bit only hash function, I don't think our (relatively small) 32-bit userbase should really worry about having multiple hash functions for e.g. blake2s. Having multiple hash functions also makes it unclear which one you used, and which package people should use for doing their hash comparisons (especially because any use or installation of b2sum will conflict with/override coreutils' installation), though BLAKE2b is already the default for the original b2sum as well.
There's an argument the parallel versions might be worth having, but frankly I don't find that super convincing as an argument for duplicating an already existing utility that seems perfectly adequate on its own, although I admit some people may disagree.

I also don't buy argument 2: MacOS already has coreutils in stdenv, does it not? And it comes with b2sum (I verified this by looking at Hydra closures, as I have no macOS machines). And "future BSDs" are not a good argument for adding packages and/or increasing the footprint of nixpkgs, in my opinion (Actually, I consider Nix-on-not-Linux a misguided 'feature' that largely penalizes the vast majority of users who are on Linux by complexifying build expressions -- though I accept macOS as a valid target -- but that's neither here nor there).
Tentatively adding features that are based on potential future users (that historically have fallen to bitrot very quickly) for relatively minor reasons seems like a bad idea, and can always be rectified in the future if needed.

I generally don't (and haven't, I think) put hard rejections on package additions, but I'm rather inclined to not accept this, personally. I can't say that my opinion weighs more heavily than anyone elses, though (I'm just an average maintainer).

I understand your arguments and agree with them for the most part, just not your conclusion.
Nixpkgs has always been very friendly to new packages, we regularly accept packages with virtually no users, or packages that have better counterparts. The policy so far was to let the end-user make the decision, and just be a collection of build instructions with nearly no moderation.
Since this is a different implementation of b2sum, one that is created by BLAKE2 upstream, and is different in its capabilities (algorithms) and dependencies from the rest, I don't think we can decline it without reconsidering acceptance policy at larger scale.

algorithm flexibility

I don’t think that the “crypto algorithm flexibility is bad” argument can be used in this case. This sort of tools most of the time is used for hash verification, not generation and when a user has to verify a hash, they have no choice which algorithm to use. In this specific case it is not an issue at all, simply because the tool does not explicitly ask the user to pick an algorithm, it has the right one as the default.

coreutils in stdenv

The fact that coreutils is in stdenv doesn’t mean that it is in the user’s profile. If I need to compute b2sum frequently and want it in my path, you are essentially suggesting that I replace all my core command line tools with the ones from Linux (or use some tricks to add only one binary from coreutils to path).
Let me explain how this PR happened. I needed to compute a blake2 hash of a file, so I check that shasum that I have doesn’t support it, google shasum blake and all the link I found were to this implementation. Obviously, I became happy that there exists not just some third-party utility, but an actual reference implementation, so naturally I decided I will use it, so I checked whether it was in nixpkgs and created an expression myself. I can easily imagine other users following the same path. I should say that when looking for this tool I couldn’t even imagine that it was reimplemented in coreutils and I have to make a confession: even now, when I know that it is there, I have really hard time trying to imagine a reason for reimplementing it in coreutils instead of using this small reference implementation.


Allow disabling of pty for 'wheelhouse', 'adminserver', and 'apiserver' tasks [OSF-7057]

Purpose
Optionally disable the allocation of a pty when using invoke using the --no-pty flag.
Changes
Adds a pty argument which defaults to True to the apiserver, adminserver, and wheelhouse tasks.
Side effects
None.  The new flag defaults to True which maintains existing behavior.  Supplying --no-pty is optional.
Discussion
See https://github.com/CenterForOpenScience/waterbutler/pull/167

Accidentally pushed a commit to this PR that didn't belong.  The PR should contain one commit, 5dd548417a9.

@brianjgeiger rebased!


Fluxstore issue in v1.7.5 when I run flutter run

↳
** BUILD FAILED **
Xcode's output:
↳
/Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/rate_my_app-0.6.1+3/ios/Classes/RateMyAppPlugin.m:15:30: warning: 'requestReview' is only available on iOS 10.3
or newer [-Wunguarded-availability]
[SKStoreReviewController requestReview];
^~~~~~~~~~~~~~
In module 'StoreKit' imported from /Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/rate_my_app-0.6.1+3/ios/Classes/RateMyAppPlugin.m:2:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.1.sdk/System/Library/Frameworks/StoreKit.framework/Headers/
SKStoreReviewController.h:27:1: note: 'requestReview' has been marked as being introduced in iOS 10.3 here, but the deployment target is iOS 9.0.0
+ (void)requestReview API_AVAILABLE(macos(10.14)) API_DEPRECATED_WITH_REPLACEMENT("-[SKStoreReviewController requestReviewInScene:]", ios(10.3, 14.0))
API_UNAVAILABLE(watchos) __TVOS_PROHIBITED;
^
/Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/rate_my_app-0.6.1+3/ios/Classes/RateMyAppPlugin.m:15:30: note: enclose 'requestReview' in an @available check to
silence this warning
[SKStoreReviewController requestReview];
^~~~~~~~~~~~~~
/Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/rate_my_app-0.6.1+3/ios/Classes/RateMyAppPlugin.m:15:6: warning: 'SKStoreReviewController' is only available on
iOS 10.3 or newer [-Wunguarded-availability]
[SKStoreReviewController requestReview];
^~~~~~~~~~~~~~~~~~~~~~~
In module 'StoreKit' imported from /Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/rate_my_app-0.6.1+3/ios/Classes/RateMyAppPlugin.m:2:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.1.sdk/System/Library/Frameworks/StoreKit.framework/Headers/
SKStoreReviewController.h:17:110: note: 'SKStoreReviewController' has been marked as being introduced in iOS 10.3 here, but the deployment target is iOS 9.0.0
SK_EXTERN_CLASS API_AVAILABLE(ios(10.3), macos(10.14)) API_UNAVAILABLE(watchos) __TVOS_PROHIBITED @interface SKStoreReviewController : NSObject
^
/Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/rate_my_app-0.6.1+3/ios/Classes/RateMyAppPlugin.m:15:6: note: enclose 'SKStoreReviewController' in an @available
check to silence this warning
[SKStoreReviewController requestReview];
^~~~~~~~~~~~~~~~~~~~~~~
2 warnings generated.
While building module 'OneSignal' imported from /Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/onesignal_flutter-2.4.1/ios/Classes/OneSignalPlugin.h:29:
In file included from :1:
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:484:4: warning:
'UNMutableNotificationContent' is only available on iOS 10.0 or newer [-Wunguarded-availability]
+ (UNMutableNotificationContent*)didReceiveNotificationExtensionRequest:(UNNotificationRequest*)request
withMutableNotificationContent:(UNMutableNotificationContent*)replacementContent;
^
In module 'UserNotifications' imported from
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:45:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.1.sdk/System/Library/Frameworks/UserNotifications.framework
/Headers/UNNotificationContent.h:63:12: note: 'UNMutableNotificationContent' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
@interface UNMutableNotificationContent : UNNotificationContent
^
While building module 'OneSignal' imported from /Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/onesignal_flutter-2.4.1/ios/Classes/OneSignalPlugin.h:29:
In file included from :1:
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:484:1: note: annotate
'didReceiveNotificationExtensionRequest:withMutableNotificationContent:' with an availability attribute to silence this warning
+ (UNMutableNotificationContent*)didReceiveNotificationExtensionRequest:(UNNotificationRequest*)request
withMutableNotificationContent:(UNMutableNotificationContent*)replacementContent;
^
API_AVAILA
BLE(ios(10
.0))
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:484:74: warning:
'UNNotificationRequest' is only available on iOS 10.0 or newer [-Wunguarded-availability]
+ (UNMutableNotificationContent*)didReceiveNotificationExtensionRequest:(UNNotificationRequest*)request
withMutableNotificationContent:(UNMutableNotificationContent*)replacementContent;
^
In module 'UserNotifications' imported from
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:45:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.1.sdk/System/Library/Frameworks/UserNotifications.framework
/Headers/UNNotificationRequest.h:16:12: note: 'UNNotificationRequest' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
@interface UNNotificationRequest : NSObject <NSCopying, NSSecureCoding>
^
While building module 'OneSignal' imported from /Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/onesignal_flutter-2.4.1/ios/Classes/OneSignalPlugin.h:29:
In file included from :1:
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:484:1: note: annotate
'didReceiveNotificationExtensionRequest:withMutableNotificationContent:' with an availability attribute to silence this warning
+ (UNMutableNotificationContent*)didReceiveNotificationExtensionRequest:(UNNotificationRequest*)request
withMutableNotificationContent:(UNMutableNotificationContent*)replacementContent;
^
API_AVAILA
BLE(ios(10
.0))
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:484:137: warning:
'UNMutableNotificationContent' is only available on iOS 10.0 or newer [-Wunguarded-availability]
+ (UNMutableNotificationContent*)didReceiveNotificationExtensionRequest:(UNNotificationRequest*)request
withMutableNotificationContent:(UNMutableNotificationContent*)replacementContent;
^
In module 'UserNotifications' imported from
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:45:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.1.sdk/System/Library/Frameworks/UserNotifications.framework
/Headers/UNNotificationContent.h:63:12: note: 'UNMutableNotificationContent' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
@interface UNMutableNotificationContent : UNNotificationContent
^
While building module 'OneSignal' imported from /Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/onesignal_flutter-2.4.1/ios/Classes/OneSignalPlugin.h:29:
In file included from :1:
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:484:1: note: annotate
'didReceiveNotificationExtensionRequest:withMutableNotificationContent:' with an availability attribute to silence this warning
+ (UNMutableNotificationContent*)didReceiveNotificationExtensionRequest:(UNNotificationRequest*)request
withMutableNotificationContent:(UNMutableNotificationContent*)replacementContent;
^
API_AVAILA
BLE(ios(10
.0))
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:485:4: warning:
'UNMutableNotificationContent' is only available on iOS 10.0 or newer [-Wunguarded-availability]
+ (UNMutableNotificationContent*)serviceExtensionTimeWillExpireRequest:(UNNotificationRequest*)request
withMutableNotificationContent:(UNMutableNotificationContent*)replacementContent;
^
In module 'UserNotifications' imported from
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:45:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.1.sdk/System/Library/Frameworks/UserNotifications.framework
/Headers/UNNotificationContent.h:63:12: note: 'UNMutableNotificationContent' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
@interface UNMutableNotificationContent : UNNotificationContent
^
While building module 'OneSignal' imported from /Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/onesignal_flutter-2.4.1/ios/Classes/OneSignalPlugin.h:29:
In file included from :1:
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:485:1: note: annotate
'serviceExtensionTimeWillExpireRequest:withMutableNotificationContent:' with an availability attribute to silence this warning
+ (UNMutableNotificationContent*)serviceExtensionTimeWillExpireRequest:(UNNotificationRequest*)request
withMutableNotificationContent:(UNMutableNotificationContent*)replacementContent;
^
API_AVAILA
BLE(ios(10
.0))
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:485:73: warning:
'UNNotificationRequest' is only available on iOS 10.0 or newer [-Wunguarded-availability]
+ (UNMutableNotificationContent*)serviceExtensionTimeWillExpireRequest:(UNNotificationRequest*)request
withMutableNotificationContent:(UNMutableNotificationContent*)replacementContent;
^
In module 'UserNotifications' imported from
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:45:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.1.sdk/System/Library/Frameworks/UserNotifications.framework
/Headers/UNNotificationRequest.h:16:12: note: 'UNNotificationRequest' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
@interface UNNotificationRequest : NSObject <NSCopying, NSSecureCoding>
^
While building module 'OneSignal' imported from /Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/onesignal_flutter-2.4.1/ios/Classes/OneSignalPlugin.h:29:
In file included from :1:
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:485:1: note: annotate
'serviceExtensionTimeWillExpireRequest:withMutableNotificationContent:' with an availability attribute to silence this warning
+ (UNMutableNotificationContent*)serviceExtensionTimeWillExpireRequest:(UNNotificationRequest*)request
withMutableNotificationContent:(UNMutableNotificationContent*)replacementContent;
^
API_AVAILA
BLE(ios(10
.0))
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:485:136: warning:
'UNMutableNotificationContent' is only available on iOS 10.0 or newer [-Wunguarded-availability]
+ (UNMutableNotificationContent*)serviceExtensionTimeWillExpireRequest:(UNNotificationRequest*)request
withMutableNotificationContent:(UNMutableNotificationContent*)replacementContent;
^
In module 'UserNotifications' imported from
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:45:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.1.sdk/System/Library/Frameworks/UserNotifications.framework
/Headers/UNNotificationContent.h:63:12: note: 'UNMutableNotificationContent' has been marked as being introduced in iOS 10.0 here, but the deployment target is iOS 9.0.0
@interface UNMutableNotificationContent : UNNotificationContent
^
While building module 'OneSignal' imported from /Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/onesignal_flutter-2.4.1/ios/Classes/OneSignalPlugin.h:29:
In file included from :1:
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/OneSignal/iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/Headers/OneSignal.h:485:1: note: annotate
'serviceExtensionTimeWillExpireRequest:withMutableNotificationContent:' with an availability attribute to silence this warning
+ (UNMutableNotificationContent*)serviceExtensionTimeWillExpireRequest:(UNNotificationRequest*)request
withMutableNotificationContent:(UNMutableNotificationContent*)replacementContent;
^
API_AVAILA
BLE(ios(10
.0))
6 warnings generated.
6 warnings generated.
Command CompileSwift failed with a nonzero exit code
/Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/location-3.0.2/ios/Classes/LocationPlugin.m:148:13: warning: 'UIAlertView' is deprecated: first deprecated in iOS
9.0 - UIAlertView is deprecated. Use UIAlertController with a preferredStyle of UIAlertControllerStyleAlert instead [-Wdeprecated-declarations]
UIAlertView *alert = [[UIAlertView alloc] initWithTitle:@"Location is Disabled"
^
In module 'UIKit' imported from /Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/Target Support Files/location/location-prefix.pch:2:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.1.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIA
lertView.h:27:12: note: 'UIAlertView' has been explicitly marked deprecated here
@interface UIAlertView : UIView
^
/Users/omkar.vilankar/.pub-cache/hosted/pub.dartlang.org/location-3.0.2/ios/Classes/LocationPlugin.m:148:48: warning: 'UIAlertView' is deprecated: first deprecated in iOS
9.0 - UIAlertView is deprecated. Use UIAlertController with a preferredStyle of UIAlertControllerStyleAlert instead [-Wdeprecated-declarations]
UIAlertView *alert = [[UIAlertView alloc] initWithTitle:@"Location is Disabled"
^
In module 'UIKit' imported from /Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/Pods/Target Support Files/location/location-prefix.pch:2:
/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.1.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIA
lertView.h:27:12: note: 'UIAlertView' has been explicitly marked deprecated here
@interface UIAlertView : UIView
^
2 warnings generated.
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/OneSignalNotificationServiceExtension/NotificationService.swift:17:13: error: cannot find 'OneSignal' in
scope
OneSignal.didReceiveNotificationExtensionRequest(self.receivedRequest, with: self.bestAttemptContent)
^~~~~~~~~
/Users/omkar.vilankar/Downloads/nni/nin/flutter-app/source/ios/OneSignalNotificationServiceExtension/NotificationService.swift:26:13: error: cannot find 'OneSignal' in
scope
OneSignal.serviceExtensionTimeWillExpireRequest(self.receivedRequest, with: self.bestAttemptContent)

I worked with fluxstore, This is not a flutter issue ..
you need to setup one signal properly..

I did still this issue persists, my flutter version is 1.24.0-8.0.pre.74 can that be an issue?

@vashisth00
Not sure what fluxstore is, but from your logs, I see you are using OneSignal sdk for Flutter. You may need to open this issue in their repo as it idoesn't seem to be an issue with Flutter.
Closing. If you disagree, write in comments and I'll reopen.
Thanks.


Update Composer dependencies (2022-02-06-00-09)

Visual regression test passed!
View the visual regression test report


chaosplt-211: reject notBefore triggers in the past

What does this PR do?

[ ] Adds new functionality
[ ] Alters existing functionality
[ ] Fixes a bug
[ ] Improves documentation or testing

Please briefly describe your changes as well as the motivation behind them:

reject any notBefore triggers set in the past during ValidateCreate, as there's no valid reason to specify those (they'd just be ignored, at best), so it indicates probably a user mistake

Code Quality Checklist

[ ] The documentation is up to date.
[ ] My code is sufficiently commented and passes continuous integration checks.
[ ] I have signed my commit (see Contributing Docs).

Testing

[ ] I leveraged continuous integration testing

[ ] by depending on existing unit tests or end-to-end tests.
[ ] by adding new unit tests or end-to-end tests.

[ ] I manually tested the following steps:

x
[ ] locally.
[ ] as a canary deployment to a cluster.

Does the controller make the final decision on when something will happen? I'm curious what happens in the event the controller and the node are in different timezones~

Does the controller make the final decision on when something will happen? I'm curious what happens in the event the controller and the node are in different timezones~

Well, the decision on createPods is made by the controller, but inject is evaluated by the injector pods. It's a time.Time that's passed from the controller to those injectors, so clock drift would certainly result in a discrepancy between the controller's expectations and when the injector pods actually start. But I believe time.Time embeds timezone information in its string form, and all computers are hopefully using UTC anyway?


Implementation of Propagator interface

Closes #26

This is supplemented by

https://github.com/JuliaQuantumControl/QuantumControlBase.jl/pull/30
https://github.com/JuliaQuantumControl/GRAPELinesearchAnalysis.jl/pull/1
https://github.com/JuliaQuantumControl/GRAPE.jl/pull/25
https://github.com/JuliaQuantumControl/Krotov.jl/pull/13

Codecov Report

Merging #27 (64857fb) into master (bce7bee) will decrease coverage by 3.92%.
The diff coverage is 71.82%.

@@            Coverage Diff             @@
##           master      #27      +/-   ##
==========================================
- Coverage   83.14%   79.21%   -3.93%
==========================================
  Files           7       14       +7
  Lines         522      818     +296
==========================================
+ Hits          434      648     +214
- Misses         88      170      +82

Impacted Files
Coverage Δ

src/expprop.jl
70.00% <ø> (+16.15%)
:arrow_up:

src/ode_propagator.jl
0.00% <0.00%> (ø)

src/specrad.jl
97.18% <ø> (+1.40%)
:arrow_up:

src/newton.jl
91.85% <25.00%> (-2.05%)
:arrow_down:

src/cheby_propagator.jl
55.17% <55.17%> (ø)

src/propagator.jl
58.82% <58.82%> (ø)

src/newton_propagator.jl
75.00% <75.00%> (ø)

src/controls.jl
80.35% <80.35%> (ø)

src/exp_propagator.jl
90.69% <90.69%> (ø)

src/propagate.jl
92.85% <92.85%> (+15.73%)
:arrow_up:

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[issue]: AttributeError: module 'jtorch.cuda' has no attribute 'amp' after running collection = chroma_client.create_collection(name="my_collection")

What happened?
from .adam import Adam
File "/opt/homebrew/Caskroom/miniforge/base/lib/python3.10/site-packages/torch/optim/adam.py", line 35, in
grad_scaler: Optional[torch.cuda.amp.GradScaler] = None,
AttributeError: module 'jtorch.cuda' has no attribute 'amp'
Versions
chroma 0.3.21
macos
Relevant log output
No response

This PR will remove the torch dep https://github.com/chroma-core/chroma/pull/267


[REF] Add major classes/functions to parent namespaces

Closes #388.

Changes proposed in this pull request:

Add major classes and functions to parent module namespaces.

The Sphinx interlinking issue is still there (and apparently has been for a while without me noticing), but the circular import issue seems to be resolved, so I'm going to merge this.


[SPARK-8867][SQL][WIP] Support list / describe function usage

As Hive does, we need to list all of the registered UDF and its usage for user.
We add the annotation to describe a UDF, so we can get the literal description info while registering the UDF.
e.g.
@ExpressionDescription(
    usage = "_FUNC_(expr) - Returns the absolute value of the numeric value",
    extended = """> SELECT _FUNC_('-1')
                  1""")
 case class Abs(child: Expression) extends UnaryArithmetic {
...

Add WIP for collecting the earlier feedback.

Merged build triggered.

Merged build started.

Test build #36657 has started for   PR 7259 at commit 629d350.

Test build #36657 has finished for   PR 7259 at commit 629d350.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class DescribeFunction(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #36774 has started for   PR 7259 at commit 17841ce.

Test build #36774 has finished for   PR 7259 at commit 17841ce.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class DescribeFunction(

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #36783 has started for   PR 7259 at commit 17841ce.

Test build #36783 has finished for   PR 7259 at commit 17841ce.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class DescribeFunction(

Merged build finished. Test FAILed.

I really like this idea. What else is needed to get this in?

Merged build triggered.

Merged build started.

Test build #37805 has started for   PR 7259 at commit 48ee4b3.

Test build #37805 has finished for   PR 7259 at commit 48ee4b3.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class DescribeFunction(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Merged build finished. Test FAILed.

retest this please

Merged build triggered.

Merged build started.

Test build #59 has started for   PR 7259 at commit 78d40f1.

Test build #59 has finished for   PR 7259 at commit 78d40f1.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class DescribeFunction(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38074 has started for   PR 7259 at commit 78d40f1.

Test build #38074 has finished for   PR 7259 at commit 78d40f1.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class DescribeFunction(

Merged build finished. Test FAILed.

Test build #1168 has started for   PR 7259 at commit 78d40f1.

Jenkins, retest this please.

retest this please

Merged build triggered.

Merged build started.

Test build #73 has started for   PR 7259 at commit 78d40f1.

Merged build triggered.

Merged build started.

Test build #38163 has started for   PR 7259 at commit 78d40f1.

Test build #38163 has finished for   PR 7259 at commit 78d40f1.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class DescribeFunction(

Merged build finished. Test FAILed.

Test build #73 has finished for   PR 7259 at commit 78d40f1.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class DescribeFunction(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38177 has started for   PR 7259 at commit c645a6b.

Test build #38177 has finished for   PR 7259 at commit c645a6b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class DescribeFunction(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38311 has started for   PR 7259 at commit 5193855.

Test build #38311 has finished for   PR 7259 at commit 5193855.

This patch fails to build.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class ShowFunctions(db: Option[String], pattern: Option[String]) extends RunnableCommand
case class DescribeFunction(

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #38314 has started for   PR 7259 at commit cf29bba.

Test build #38314 has finished for   PR 7259 at commit cf29bba.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class ShowFunctions(db: Option[String], pattern: Option[String]) extends RunnableCommand
case class DescribeFunction(

Merged build finished. Test FAILed.

That's weird, seems not unrelated error, and it did passed the unit test locally.

retest this please

Merged build triggered.

Merged build started.

Test build #89 has started for   PR 7259 at commit cf29bba.

Merged build triggered.

Merged build started.

Test build #38339 has started for   PR 7259 at commit cf29bba.

Test build #38339 has finished for   PR 7259 at commit cf29bba.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class ShowFunctions(db: Option[String], pattern: Option[String]) extends RunnableCommand
case class DescribeFunction(

Merged build finished. Test FAILed.

Test build #89 has finished for   PR 7259 at commit cf29bba.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class ShowFunctions(db: Option[String], pattern: Option[String]) extends RunnableCommand
case class DescribeFunction(

Merged build finished. Test FAILed.

This patch's very useful for users :))
I leave some comments;
I think we can add a function name together in ExpressionDescription according to Hive Description as follows;
@ExpressionDescription(
    name="abs",
    usage = "_FUNC_(expr) - Returns the absolute value of the numeric value",
    extended = """> SELECT _FUNC_('-1')
                  1""")
 case class Abs(child: Expression) extends UnaryArithmetic {

This change removes hard-coded function names in FunctionRegistry#expressions and function names are derived from their annotations.
Getting name, usage, and implementation together might make developers easily understood.
However, not sure which is better.

@maropu it makes it slightly harder to create aliases though, unless we pass in an array.

@chenghao-intel  what's still WIP about this patch?

Test build #1202 has started for   PR 7259 at commit cf29bba.

Test build #1202 has finished for   PR 7259 at commit cf29bba.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public class ExpressionInfo
case class ShowFunctions(db: Option[String], pattern: Option[String]) extends RunnableCommand
case class DescribeFunction(

Thank you all for the review and suggestion, I removed the WIP, I think that's ready to be merged if you don't have any further comments.

Thanks - I've merged this.

Ok, thanks.


Fix duplicate data returned in queries

Required for all non-trivial PRs

[x] Rebased/mergable
[x] Tests pass
[x] CHANGELOG.md updated

This fixes a race in the meta index for adding series to measurements that can cause duplicate data to be returned at query time.  The issue was that the series would get added more than once to a measurement because we did not check for the series under a write lock after releasing the read lock.
This also fixes a panic in Shard.FieldDimensions that happened while testing this fix.
Fixes #6946

LGTM 👍


Avoid verification code emails when the user is not registered in Azure AD B2C

Azure B2C is gives a false impression that the user is in the directory when they try to reset their password.
Following is steps in reset password: 1) User clicks the Reset Password link

B2C presents a page with “Email Address” field and says “Verification is necessary. Please click Send button.”

User enters his email address and clicks “Send Verification Code”

B2C sends the verification code this that email address (Even if no user is associated with that email address. This is where the user thinks he is registered with the system)

Now the user enters the verification code he received and click “Verify Code”

B2C validated the code and says “E-mail address verified. You can now continue” (This is the step where they become confident that they exist in the system)

Now when the users click “Continue” they get the error “An account could not be found for the provided user ID.” As given in the screenshot.

Confirming an email that is not associated with a user completely confuses them. kindly give a solution

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

ID: 33489541-1210-69d0-4a45-5ba306d254fc
Version Independent ID: 4dd79b67-4004-f7d0-d59d-d3c94677b36e
Content: Azure Active Directory B2C custom policies
Content Source: articles/active-directory-b2c/custom-policy-overview.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@rohitchouhan08
Thanks for your feedback! We will investigate and update as appropriate.

@JasSuri  has published the Password Reset OTP only sent if Email is registered solution, which is based on the new Display control feature.

#please-close


[BUG] - queryTip breaks with MuxError (writev/recv) failure still exists in 1.30.1

The issue that was marked as solved is not solved in 1.30.1, please reopen
https://github.com/input-output-hk/cardano-node/issues/3042
We still see broken mux/pipe errors with the latest release 1.30.1 here.

this should be fixed in the next release - 1.31.0 - https://github.com/input-output-hk/cardano-node/issues/3042#issuecomment-960553159

yes, looking promising: https://github.com/input-output-hk/cardano-node/issues/3042#issuecomment-960562013

can we close this ticket?

can we close this ticket?

yes.


tracing: Deprecate Opencensus (@2.10)

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

cc @kyessenov


Reactive observable-ish broken

Since updating to the new version of Flutter Stable 2.8, the tutorial and code files for single / double counter updates, no longer reflect as expected.
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 2.8.0, on Microsoft Windows [Version 10.0.19044.1415], locale en-ZA)
[√] Android toolchain - develop for Android devices (Android SDK version 32.0.0-rc1)
[√] Chrome - develop for the web
[√] Android Studio (version 3.6)
[√] VS Code (version 1.63.2)
[√] Connected device (3 available)

Issue wasnt with Flutter version, but rather I needed to add "NotifiyListeners()" to the service method. This step was not in the tutorials.


SAM with prior knowledge graph and customly set hyperparameters always returns "All solutions contain NaNs" assertion error.

Hi,
I have done some hp optimization for SAM and it did yield an increase in performance. I wanted to go further and introduced prior knowledge graph (pkg later). However, when I am trying to run SAM with pkg and optimized hp, it always yields AssertionError: "All solutions contains NaNs" and AttributeError: "'Tensor' object has no attribute 'astype'". I have tried to experiment running SAM with different set of hp and pkg and find out that when hp "nruns=1" is set, the errors are arising. I have fed the pck as networkx.DiGraph and networkx.Graph objects -- in both cases it seems to yield the same assertion errors. What could be the reason for such behavior?
Best,
Anton

Hello,
This issue often arises when the GAN does not converge, I think you may need to tweak the parameters of the GAN to make the optimization more smooth. what are the
Thing is, we are utilizing multiprocessing to optimize the compute-time so the issues raises only when n_jobs=1 or n_runs=1.
The Attribute error is concerning however, do you have the full error trace of that error ?
Thanks for the help,
Best,
Diviyan

hello Diviyan:
When I was inputting parameters, I also encountered this type of problem. The following is my running code and specific error information.

Looking forward to your reply very much!
Best
Christopher

Hello @Christopher7622 , I think your problem arises with package versions, could you try using the docker image to execute the code?
Best,
Diviyan

Hello @Christopher7622 , I think your problem arises with package versions, could you try using the docker image to execute the code?
Best, Diviyan

thanks a lot,An hour ago, I ran the program again according to the example provided in the official document. Although an error occurred, the program continued to run on the server. What is the reason for this?


⚠ Bofrost.de has degraded performance

In f744e3f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1482 ms

Resolved: Bofrost.de performance has improved in 007e64a after 53 minutes.


Add updated tool to consolidate and preprocess data from simulation results

Starting from run description in input JSON file:
    "1": {
        "JOBID": 1,
        "directory": "RUN0",
        "end": 0,
        "end_pIC50": "5.44251008457101",
        "end_smiles": "Cc1ccncc1NC(=O)Cc2cc(cc(c2)Cl)O[C@@H]3CC(=O)N3",
        "end_title": "TRY-UNI-2eddb1ff-7",
        "ff": "openff-1.2.0",
        "ligand": "nucleophilic_displacement_enumeration_for_FEP-sorted-x10789.sdf",
        "protein": "../receptors/monomer/Mpro-x2646_0_bound-protein-thiolate.pdb",
        "start": 2,
        "start_smiles": "Cc1ccncc1NC(=O)Cc2cc(cc(c2)Cl)OCS(=O)(=O)N[C@H]3C[C@H]4C[C@@H](C3)[NH2+]C4",
        "start_title": "EN300-784608",
        "target": "SARS-CoV-2 Mpro"
    },

Extract work values from simulation data (globals.csv). See example on server at /home/server/server2/projects/available/covid-moonshot/consolidate-work-to-pandas-13420.py. Create work.json files with extracted data (at run/clone/gen level).

Map free energy analysis over run/clone/gens. Produce the following values

delta_f
ddelta_f (BAR error estimate)
delta_f_low
delta_f_high
bar_overlap
number of samples (if we eliminate forward work, should we eliminate corresponding reverse?)

Collect results into an augmented version of the input JSON, with the following additional schema:

    "1": {
        "complex_phase": {
              "delta_f" : -2.345,
              "ddelta_f" : 0.012,
              "delta_f_low" : -2.567,
              "delta_f_high" : -2.1,
              "delta_f_bootstrap" : [-2.452, -2.23],
              "nwork" : 105,
              "bar_overlap" : 0.984,
           },
        "solvent_phase" : {
              "delta_f" : -2.345,
              "ddelta_f" : 0.012,
              "delta_f_low" : -2.567,
              "delta_f_high" : -2.1,
              "nwork" : 105,
              "bar_overlap" : 0.984,
           },
        "binding" : {
              "delta_f" : -2.345,
              "ddelta_f" : 0.024,
        }
    },

These fields are optional, and can come later:

delta_f_low, delta_f_high are 95% CI for bootstrapping
delta_f_bootstrap can hold bootstrap replicates if we add bootstrapping later
bar_overlap can hold the BAR overlap (0 = bad, 1 = good) once we figure this out, as a separate measure of quality control

I propose we also add core_rmsd as an optional metric to complex_phase where we can later add a step that computes the RMSD of the core atoms after protein alignment. A low number (e..g < 2.0A) would indicate the scaffold interactions are not disrupted, and can be used as additional quality control.
We can break these optional steps into separate issues to remind us to add these features later as quality control measures:

bootstrapping BAR uncertainties
BAR overlap
core RMSD


How to add additional Twilio numbers to one BOT???

I used these instructions to add 1 Twilio Phone Number to my BOT.
https://docs.microsoft.com/en-us/azure/bot-service/bot-service-channel-connect-twilio?view=azure-bot-service-4.0#connect-a-bot-to-twilio-using-the-twilio-adapter
I currently have hundreds of phone numbers and I need to add more and more, as needed. How do I override the Activity to use a different From number when sending an Activity?
Any help is much appreciated! Thanks!

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

ID: d0b76e08-962a-2a8e-2453-87fb917d68ec
Version Independent ID: 937798fb-8f76-683c-e146-55dcd79622e1
Content: Connect a bot to Twilio - Bot Service
Content Source: articles/bot-service-channel-connect-twilio.md
Service: bot-service
GitHub Login: @RobStand
Microsoft Alias: kamrani

This is a good question for Stack Overflow. Use the botframework tag. Please note that Stack Overflow has guidelines such as requiring a descriptive title, a complete and concise problem statement, and sufficient details to reproduce your issue. New users should visit the Stack Overflow Help Center for more details.


Symbol not found OSX SDK 10.10 - Beta 6.1

I followed the installation steps, but I keep getting the following error:
dyld: Symbol not found: _NSURLAuthenticationMethodHTTPBasic
  Referenced from: /Library/Developer/Xcode/DerivedData/Sync-dqwtdopmwaheyjheaabinsggoynp/Build/Products/Debug/Alamofire.framework/Versions/A/Alamofire
  Expected in: /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
 in/Library/Developer/Xcode/DerivedData/Sync-dqwtdopmwaheyjheaabinsggoynp/Build/Products/Debug/Alamofire.framework/Versions/A/Alamofire
(lldb)

The solutions listed in previous issues don't seem to work.
Steps

Create blank project
Add & checkout submodule at 6.1 branch
Drag and drop Alamofire.xcodeproj in Project navigator
Link Binary With Libraries -> Alamofire.framework
Copy Frameworks -> Destination -> Frameworks -> Alamofire.framework

Changing the deployment target of the Alamofire project has no effect.
Any idea what else this could be?
Thanks in advanced! :+1:

@Dschee Thanks a ton for this; just getting started on swift and am thrilled to have a nice http abstraction now working.


Input Event action match returns false positives

Godot version:
4.0 master
3.2.3 stable
OS/device including version:
Win 10
Issue description:
Action match gives the wrong result, it completely ignores modifiers.
Originated from #9002, and @volzhs seemed to notice this same issue about a year later.
Steps to reproduce:
Set up an input action called "test" and give it an event of Alt+Shift+Enter.
In a script, create and InputEventKey with scancode/keycode = KEY_ENTER.
Print the result of InputMap.event_is_action(event, "test")
Note that the result is TRUE. It is comparing KEY_ENTER and SHIFT+ALT+KEY_ENTER. This should NOT return true!

Problem lines:
https://github.com/godotengine/godot/blob/a84ad91280dabed66f786504dc2b796468bc742c/core/input/input_event.cpp#L386-L396
The actual problem is (!key->is_pressed() || (code & event_code) == code);
Minimal reproduction project:
For 3.2
InputEventActionMatch.zip

Note this also totally messes with InputMap::_find_event(), which is relied upon for InputMap::action_add_event, InputMap::action_has_event andInputMap::action_erase_event


Proposal: backport migration

I've created a pattern to support backporting certain migrations. As an example, I've backported #10617.
Important: This PR is not pointing to master but release/v1.11
I've labeled this PR kind/proposal for the system and kind/bug for the migration I've included.

But then the same migrations may be executed twice?

But then the same migrations may be executed twice?

Yes, that's a requisite. Only migrations that can be executed twice, like the one backported here. I've wrote it down right before the declaration, just in case:
// Backports are only applied after latest version in 'migrations'.
// This list must be **empty** in master, but can contain items in release branches.
// Backported migrations must conform to the following criteria:
//    * The function must support being executed multiple times (e.g. when updating to the next
//      minor revision and when the actual migration is executed again on the next major upgrade).
//    * The function must not rely on data structures that might not be present in the branch
//      it is backported to, unless its safe that it will add the column itself.

Not bad but the 117.1.go is a weared naming concept. Why not name bakports like bachport_<number>.go?

Not bad but the 117.1.go is a weared naming concept. Why not name bakports like bachport_<number>.go?

I wanted it to follow the version/subversion number in the version table.

We could also use a tool such as xormigrate which keeps track of all the migrations that are run, instead of just the latest, and would be able to handle the case of backporting a migration.


organizeImports without the reordering ("remove unused imports" being its own option)

Suggestion
I was originally using the organizeImports in my "editor.codeActionsOnSave" block on VSCode.  The issue with this feature is it also does the sorting which we don't want.
It's currently not possible to switch the sorting off without losing the "remove unused imports".
According to VSCode documentation "addMissingImports" is offered as an "on save" option, but not "removeUnusedImports".
⭐ Suggestion
As some projects already use tools which handle ordering it would be nice to just add/remove imports without changing the order.
Then have a separate command which handles ordering.
💻 Use Cases
My team are happy with the ordering of imports and don't want changes. However by keeping the ordering I lose the ability to remove unused imports.
Example
    "editor.codeActionsOnSave": {
      "source.organizeImports": false,
      "source.fixAll": true,
    },

Another use is when you are using a code formatter such as prettier that sorts the imports (with an appropriate prettiert plugin) but  doesn't have enough knowledge to find and remove unused imports. It would be great if the IDE would remove the unused imports, and prettier could format them.

Hey @RyanCavanaugh so you still need more feedback for this?
It seems like this would be an easy win, as you already implement both features, this is just asking you to separate them out.

Another reason why these command should be separated is due to the fact that some projects like to use ESLint for organising imports but still want TypeScript to bring in imports which are being used.
Sadly at the moment you can't do that without conflicting with ESLint.

For anyone waiting for this, you can use this extension: https://marketplace.visualstudio.com/items?itemName=kuscamara.remove-unused-imports

We have a code fix for removing all unused declarations that I think would be trivial to expose to codeActionsOnSave. I actually thought it already was exposed, but it looks like surprisingly little is exposed. Would that satisfy this request, or does it need to be specific to imports?

Yes exposing that would be great @andrewbranch, it would be great if VSCode offered this as an "on save" action via the extension, but just exposing it would be a win here

I want the remove without organizing feature too...

I think this slipped through the cracks, @jasonwilliams. Bringing it up with the VS Code team tomorrow. Looking back at my last comment, I’m not sure offering the remove-all-unused-stuff on save is a workable alternative after all, since that could delete entire local function and class declarations, which is probably not what anyone wants 😅

@jasonwilliams your original post showed an example code snippet with "source.fixAll": true. Do you actually use that, or was it just for context?

@jasonwilliams your original post showed an example code snippet with "source.fixAll": true. Do you actually use that, or was it just for context?

Yes I used to use that also but I can’t remember specifically what for. It may have been to remove imports I wasn’t using.

Thanks so much for this @andrewbranch can't wait to try it

Once https://github.com/microsoft/vscode/pull/161654 lands you’ll be able to try it in nightly/Insiders. I’m working on exposing Sort Imports and Remove Unused Imports from the command palette as well.

Wil remove unused imports map to VSCode’s “source.fixAll” option on save? And sort imports maps to “source.organizeImports” then I guess these will “just work” for people who have that set

I haven’t made any changes to source.fixAll in https://github.com/microsoft/vscode/pull/161654. I’ll take a look at what it currently does and see if it makes sense to include it.


Zeus branch compilation issue due to GitHub's deprecation of git:// protocol

As stated in Improving Git protocol security on GitHub, after March 15th, 2023 the git:// protocol is no longer supported. Because of this I was getting an error when bitbaking my Digi Embedded Yocto custom image (or any yocto image including meta-aws layer).
In my particular case, the issue was with aws-iot-device-sdk-python-v1. Even if commit 55b20c1d78687fbd0232adc09f3fcc0aec364a3f addresses this issue, I was still getting errors. So I had to manually change  file /usr/local/dey-3.0/sources/meta-aws/recipes-sdk/aws-iot-device-sdk-python-v1/aws-iot-device-sdk-python-v1.inc as follows:
Where it said:
SRC_URI = "https://github.com/aws/aws-iot-device-sdk-python.git;branch=${BRANCH};name=aws-iot-device-sdk-python-v1"
I wrote:
SRC_URI = "git://github.com/aws/aws-iot-device-sdk-python.git;protocol=https;branch=${BRANCH};name=aws-iot-device-sdk-python-v1"
And the bitbake fetch operation finally worked.
I advise you check other recipes that may suffer from this issue as well. I hope this helps others.

Hi Sergio,
I am able to build the python device sdk v1 with the https:// url using poky's current zeus release. We will assess the URLs in this release, but the https:// url scheme should be preferred now with github.

If you are able to share your layer SHAs, we can try to recreate issue.

Hello nateglims,
Yes, I understand that it should work with the https://, in fact changing from the git:// to the https:// for GitHub repos is what solved many other issues. However, I have just reverted meta-aws to commit 1cea10e5f237f547d9b186f237c9936951f69384 (current zeus HEAD), bitbaked only aws-iot-device-sdk-python-v1, and I'm getting the following error:
bitbake aws-iot-device-sdk-python-v1
(...)
Build Configuration:
BB_VERSION           = "1.44.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "aarch64-dey-linux"
MACHINE              = "ccimx8mn-dvk"
DISTRO               = "dey"
DISTRO_VERSION       = "3.0-r3"
TUNE_FEATURES        = "aarch64"
TARGET_FPU           = ""
meta
meta-poky
meta-yocto-bsp       = "HEAD:d88d62c20d7d8da85f02edb170dae0280624ad7e"
meta-oe
meta-python
meta-networking
meta-webserver       = "zeus:2b5dd1eb81cd08bc065bc76125f2856e9383e98b"
meta-qt5             = "zeus:91e6e3b1f5aebd17f895caac3dee32a14630da99"
meta-qt5-extra       = "zeus:8b53b092e0f0425f97197a698124191b26d4f280"
meta-multimedia
meta-gnome           = "zeus:2b5dd1eb81cd08bc065bc76125f2856e9383e98b"
meta-aws             = "zeus:1cea10e5f237f547d9b186f237c9936951f69384"
meta-swupdate        = "HEAD:8ad6a75e1778cdda671b3d6aea2a9692613020ec"
meta-freescale       = "zeus:14f1a630a47375432f93c556927b879b51d84c4e"
meta-fsl-demos       = "zeus:ca27d12e4964d1336e662bcc60184bbff526c857"
meta-python2         = "zeus:4400f9155ec193d028208cf0c66aeed2ba2b00ab"
meta-webkit          = "zeus:ab4c99d825ed99901e7bd86870312f6c70865f2e"
meta-ml              = "zeus-5.4.70-2.3.1:75a2feb2d90cdab5361e544280d1f183f04b8911"
meta-digi-arm
meta-digi-dey        = "meta-digi-overture:451aab2269f7291ed81e73ef162a87397c527b35"
meta-overture        = "main:9c849d8debda3b32c0db06f0771b5fad14df7d6a"

Initialising tasks: 100% |######################################################################################################################################################| Time: 0:00:00
Sstate summary: Wanted 6 Found 0 Missed 6 Current 200 (0% match, 97% complete)
NOTE: Executing Tasks
NOTE: Setscene tasks completed
ERROR: aws-iot-device-sdk-python-v1-git-r0 do_fetch: No checksum specified for /home/metabolomics/DEY/workspace/2023-03_08-ccimx8mn-dvk-zeus-0.3.2/../downloads/aws-iot-device-sdk-python.git, please add at least one to the recipe:
SRC_URI[aws-iot-device-sdk-python-v1.md5sum] = "b42d99138f3a404a96a2bc1e815d8835"
SRC_URI[aws-iot-device-sdk-python-v1.sha256sum] = "e29445cbfc724dda95d925537a8febcc7a87247a61b90583c35bb7631f1a29e0"
ERROR: aws-iot-device-sdk-python-v1-git-r0 do_fetch: Fetcher failure for URL: 'https://github.com/aws/aws-iot-device-sdk-python.git;branch=master;name=aws-iot-device-sdk-python-v1'. Missing SRC_URI checksum
ERROR: Logfile of failure stored in: /home/metabolomics/DEY/workspace/2023-03_08-ccimx8mn-dvk-zeus-0.3.2/tmp/work/aarch64-dey-linux/aws-iot-device-sdk-python-v1/git-r0/temp/log.do_fetch.50023
ERROR: Task (/usr/local/dey-3.0/sources/meta-aws/recipes-sdk/aws-iot-device-sdk-python-v1/aws-iot-device-sdk-python-v1_git.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 884 tasks of which 883 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /usr/local/dey-3.0/sources/meta-aws/recipes-sdk/aws-iot-device-sdk-python-v1/aws-iot-device-sdk-python-v1_git.bb:do_fetch
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

As you can see, it seems to be an issue within the do_fetch step with the checksums. If we check the generated tmp/work/aarch64-dey-linux/aws-iot-device-sdk-python-v1/git-r0/temp/log.do_fetch.50023:
DEBUG: Executing python function extend_recipe_sysroot
NOTE: Direct dependencies are []
NOTE: Installed into sysroot: []
NOTE: Skipping as already exists in sysroot: []
DEBUG: Python function extend_recipe_sysroot finished
DEBUG: Executing python function do_fetch
DEBUG: Executing python function base_do_fetch
ERROR: No checksum specified for /home/metabolomics/DEY/workspace/2023-03_08-ccimx8mn-dvk-zeus-0.3.2/../downloads/aws-iot-device-sdk-python.git, please add at least one to the recipe:
SRC_URI[aws-iot-device-sdk-python-v1.md5sum] = "b42d99138f3a404a96a2bc1e815d8835"
SRC_URI[aws-iot-device-sdk-python-v1.sha256sum] = "e29445cbfc724dda95d925537a8febcc7a87247a61b90583c35bb7631f1a29e0"
ERROR: Fetcher failure for URL: 'https://github.com/aws/aws-iot-device-sdk-python.git;branch=master;name=aws-iot-device-sdk-python-v1'. Missing SRC_URI checksum
DEBUG: Python function base_do_fetch finished
DEBUG: Python function do_fetch finished

So, I only managed to get it to work once I changed aws-iot-device-sdk-python-v1.inc to :
SRC_URI = "git://github.com/aws/aws-iot-device-sdk-python.git;protocol=https;branch=${BRANCH};name=aws-iot-device-sdk-python-v1"

I was starting from an incorrect version 🤦
You are absolutely correct, it appears for zeus that the fix was applied differently and the git:// form is correct: https://git.yoctoproject.org/poky/commit/?h=zeus&id=daf096e295121ea49ebf21f8070e9a6e28f5d46c
I will revert and test the layer shortly.
Thanks!

This pull request should solve this issue: https://github.com/aws4embeddedlinux/meta-aws/pull/3307


Add STAT Workbook to Sentinel Workbooks list

⛔ Will not fix
📝 Summary of our discussion
To show up in the workbooks blade we need the following two pre-requisites:

The workbook has to be deployed in the same resource group as the Log Analytics workspace on which Sentinel is deployed. Since the workbook is deployed at the same time as the rest of the solution, we can't require the user to scope the Sentinel RG as it might be too limited.
Even if in certain case the condition 1 is met, we still need to define the sourceId parameter in the ARM template with the identifier of the workspace where Sentinel is deplopyed. Although that could be asked during the solution deployement, it becomes to uncertain that all the conditions would be met for the workbook to finally show up in the My template section in the workbooks blade.

🙅 As a result, we won't fix this.
We can however update the documentation of the workbook to reflect what would be the manual steps one may follow to make the workbook appear in the blade. Issue #254 will address this instead.


[Idea] Add animationIn and animationOut

Hi!
I found this library and I'm happy how it works but I miss the option to set classes for animationIn and animationOut instead of animation.
It would be great if such an option appeared :)
Regards
Matt

+1


Expanding groups in Table resets the scroll bar

Whenever I expand something in the Table the scroll bar goes to the top. It gets quite annoying when there are too many groups and runs. Kindly take a look at it.

Hi Rahul thanks for letting me know about this!

@rahulvigneswaran could you share a few more details— is this on a report page or a project page? What browser and operating system are you using?

@cvphelps I am using Windows 10 with Google Chrome. This happens in the project page -> Table -> Tree View of the Runs.

Hey @rahulvigneswaran
In the past year we've majorly reworked the CLI and UI for Weights & Biases. We're closing issues older than 6 months. Please comment to reopen.


cache: Sort HTTP Settings and Backend Pool slices

While digging into https://github.com/Azure/application-gateway-kubernetes-ingress/issues/317 I realized we still had redundant writes to ARM.
This seems to be coming from an unstable sort (or lack of sort) of the Backend Pool and HTTP Settings structs.
This PR adds sorters:

sorter.BySettingsName
sorter.ByBackendPoolName

and applies these to the final data structures.

@akshaysngupta Thanks!  PTAL


feat: create UI components text area

Overview

Add text area component in the components/ui folder based on the design on Figma.
Changes

Install button component from shadcn/ui (https://ui.shadcn.com/docs/components/textarea)
style the design

Review points

The styling matches the Figma design

Screenshots or videos

The images of icons in Figma

text area components

Assignee Checklist:

[x] The base branch is correct (no accidental merges)
[x] The branch name follows our branch naming rules
[x] The PR title follows our PR title rules
[x] My code follows our coding style
[x] I have commented on my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings or errors in the console

Reviewer Checklist:

[ ] Code readability and simplicity
[ ] Follows best practices and coding standards
[ ] Understandable and maintainable code

could you please check the figma and adjust margin?

could you please check the figma and adjust margin?

I adjust the design based on Figma!


flet pack command doesn't include web folder into flet folder of standalone executable

Description
Hello! When I'm trying to run Flet app package created using flet pack main.py --add-data "fonts;fonts" command, I'm getting the next error message window:
Traceback (most recent call last):
  File "main.py", line 466, in <module>
  File "flet_runtime\app.py", line 81, in app
  File "asyncio\base_events.py", line 650, in run_until_complete
  File "flet_runtime\app.py", line 223, in app_async
  File "flet_runtime\app.py", line 416, in __connect_internal_async
  File "flet_runtime\app.py", line 537, in __start_flet_server
Exception: Web root path not found: C:\Users\user\AppData\Local\Temp\_MEI260322\flet\web

Code example to reproduce the issue:
import flet

async def main(page: flet.Page):
    """
    My app code here
    """
    pass

flet.app(target=main, view=flet.AppView.WEB_BROWSER)

Describe the results you received:
Error window of an unhandled exception with the message above.

Describe the results you expected:
I expect the flet pack to simply create a functioning standalone web application : )

Additional information you deem important (e.g. issue happens only occasionally):
When I packed my application with flet pack main.py -D --add-data "fonts;fonts" and added the folder venv/Lib/site-packages/flet/web to the dist/main/flet folder, my application successfully deployed)
Flet version (pip show flet):
Name: flet
Version: 0.8.1
Summary: Flet for Python - easily build interactive multi-platform apps in Python
Home-page:
Author: Appveyor Systems Inc.
Author-email<EMAIL_ADDRESS>License: Apache-2.0
Location: D:\MyWorkingDirHere\venv\Lib\site-packages
Requires: copier, flet-runtime, packaging, pydantic, qrcode, watchdog, websocket-client, websockets
Required-by:

PyInstaller version (pip show pyinstaller):
Name: pyinstaller
Version: 5.13.0
Summary: PyInstaller bundles a Python application and all its dependencies into a single package.
Home-page: https://www.pyinstaller.org/
Author: Hartmut Goebel, Giovanni Bajo, David Vierra, David Cortesi, Martin Zibricky
Author-email:
License: GPLv2-or-later with a special exception which allows to use PyInstaller to build and distribute non-free programs (including commercial ones)
Location: D:\MyWorkingDirHere\venv\Lib\site-packages
Requires: altgraph, pefile, pyinstaller-hooks-contrib, pywin32-ctypes, setuptools
Required-by:

Operating system:
Windows 10

Additional environment details:
I am using a venv created by PyCharm Community edition.

Additionally, modifying main.spec after flet pack main.py --add-data "fonts;fonts" and running pyinstaller main.spec helps to create functioning standalone .exe:
main.spec after modification:
...
a = Analysis(
    datas=[('fonts', 'fonts'), ('venv/Lib/site-packages/flet/web', 'flet/web')],
    ...
)
...

Heh, flet pack has been made for packaging desktop apps, not web. So your issue is more a request rather than a bug :)

Oh, it seems to me a very useful and important feature. I searched for information about this in the documentation but did not find if it is possible or not. By the way, I only found that even if the application is running in desktop application mode, it is still a web application that has a server running in the background. But how does my solution work stable enough / should it work stable, I don't know something?

[flet pack](https://flet.dev/docs/cli/pack) is used for packaging desktop applications
[flet publish](https://flet.dev/docs/cli/publish) is used for creating static sites.

Try the new flet build too...


iRep for long reads

Hi,
I have some metgenomics samples with long reads and also the complete genomes of the microbes that I want the replication rates for.
I am wondering if iRep/bPTR could be applied to metagenomics data obtained via long read sequencing technologies (PacBio and Nanopore). If yes, then would there be any bias introduced in the results because of the high error rates?

In principle both methods should work with long reads. However, you bring up a good point with regards to the error rate, which will be especially important if there are multiple closely related strains that you need to distinguish based on only a few SNPs. If that is not the case, then it should actually work quite well as the longer reads should be less likely to map to the wrong genome (i.e. genome from different species), which is the largest source of error with these methods.
Since you have complete genomes bPTR may be easier to analyze. After running iRep/bPTR you can probably get a sense of the quality of the analysis from the plots produced by both scripts.

On May 24, 2019, at 6:50 AM, mdrishti<EMAIL_ADDRESS>wrote:
Hi,
I have some metgenomics samples with long reads and also the complete genomes of the microbes that I want the replication rates for.
I am wondering if iRep/bPTR could be applied to metagenomics data obtained via long read sequencing technologies (PacBio and Nanopore). If yes, then would there be any bias introduced in the results because of the high error rates?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Bootstrap Version Update

Updated bootstrap to 3.3.6
No issues noted

Seeing the two commits at the end cancel each other out, you should just reset the branch to the bootstrap update commit and then force-push here again. That'll keep things clean

They don't entirely cancel each other out, the changes to partners.php in the second commit persist on through. I can go back to the first commit and make a new commit only changing that if preferred.

Oh, I didn't  see that. Yeah it's probably easier to git commit --amend the first commit and  force push. Although, a git rebase -i is really what is correct here, but that's pretty advanced git stuff so I wouldn't expect it lol

Alright, the commit history should be cleaned up to merge now.


Feature/task 2

@swati-RP  do not use !important in scss and also write scss according to BEM methodology and you didn't add conditions in your markup, add conditions in your markup

@swati-RP  you are not using classes name in ul while styling you are targetting directly ul tag that is not good style them by targetting the classs name and also I didn't see any media query is it compatible to mobile devices too ?


Implement aidpackage img link edit functionality

Purpose

Admin portal part of #479
I'm not proud of the way this was implemented. The code needs to be refactored to make use of reusable components.
Banner image update works. Waiting on backend updates to support thumbnail image #479

Banner image update works. Waiting on backend updates to support thumbnail image

Thumbnail image upload works.

@nshamit Is it necessary to display the thumbnail image inside the package details page (where the banner is shown) of the donor portal? If so, where should I place it?


Add Jetbrains Webinar Event (Temporary)

Adds a temporary badge to the README.md that showcases the upcoming Jetbrains Webinar on Ruff.
Extra Thoughts:

We could create a banner to more publicly advertise this

Thanks :)


Sub-processes profile does not provide any useful information

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When I use memray to profile the memory of a multi-processed application, the resulting profile does not provide any useful information.
Expected Behavior
I expect the profile of a multi-processed application to provide similar information to the profile of a single process application.
Steps To Reproduce
Consider the following simple script, using multiprocessing :
import os
import multiprocessing as mp

def heavy_stuff(i):
    x = [i] * 100000
    return len(x)

def job(i):
    return heavy_stuff(i)

if __name__ == "__main__":
    with mp.Pool(2) as pool:
        for result in pool.imap_unordered(job, range(10)):
            print(result)

Now, if I monitor what each process is doing :
import os
import multiprocessing as mp
import memray

def heavy_stuff(i):
    x = [i] * 100000
    return len(x)

def job(i):
    with memray.Tracker(f"mem.bin.{i}", native_traces=True):
        return heavy_stuff(i)

if __name__ == "__main__":
    with mp.Pool(2) as pool:
        for result in pool.imap_unordered(job, range(10)):
            print(result)

(This generates one trace per job)
But when I visualize it, I have the result I expect :

A clear memory trace of the heavy_stuff() function.

Now, the issue with the approach above is that it generates a lot of traces, and if the job are small enough, writing one trace per job makes everything extremely slow.
So instead, I try to monitor the memory from the main process, with follow_fork set to True :
import os
import multiprocessing as mp
import memray

def heavy_stuff(i):
    x = [i] * 100000
    return len(x)

def job(i):
    return heavy_stuff(i)

if __name__ == "__main__":
    with memray.Tracker("mem.bin", native_traces=True, follow_fork=True):
        with mp.Pool(2) as pool:
            for result in pool.imap_unordered(job, range(10)):
                print(result)

For the main process I have this :

Which just show the Pool creation.
For the child processes, I have this :

Which shows nothing useful (I can't see how much memory the call to heavy_stuff() consumes).

I expected the child process to display the same thing as the first approach (or at least something more useful that what's given currently). What am I doing wrong ?
Memray Version
1.3.1
Python Version
3.8
Operative System
macOS
Anything else?
No response

Hi @astariul,
Thanks for opening the issue. Notice this is covered in the docs:

We support tracking across forks, but can’t track across an exec, so if the tracked child process calls an os.exec function, even to start a new Python interpreter, we will not be able to report the allocations performed in the new process. Notably, the default multiprocessing start method on macOS is “spawn”, which leverages exec.

https://bloomberg.github.io/memray/supported_environments.html#known-issues-and-limitations
In macOS, the default start method for multiprocessing is not fork but exec. As exec resets the whole process, we cannot track across it (notice the option is called follow_fork). You can change the start method by calling:
import multiprocessing
multiprocessing.set_start_method('fork')

I am closing the issue, but please, feel free to reopen if we missed anything.


what is the latest version of dynamic trees in 1.12.2 that uses forge <IP_ADDRESS>59

i'd just bring my modpack up to 2860 but the other mods need 2859

never mind I tested it and its 0.9.25

Are you really certain they need 2859? There's literally one minor change in 2860 that shouldn't be breaking for any mods.


JUnit WiremockExtension with sticky random port for @Nested tests in combination with @SpringBootTest

Proposal
I recently stumbled upon this issue with some nested test classes.
When you have a test that consists of several nested test classes (Annotated with @Nested) the wiremock server stops and starts after each test class.
Spring test context is able to reload the context properly to update the new port in the environment in that case. For example @DynamicPropertySource didn't run and update the context. You can achieve that by adding @DirtiesContext but this also increases runtime by a significant bit.
It would be great if there's a way to stick to a port once the wiremock server was started once. Unfortunately that's not possible with overwriting the WiremockExtension with a custom implementation.
References
public class WireMockExtension extends DslWrapper
...
 private void stopServerIfRunning() {
    if (wireMockServer.isRunning()) {
      if(options.isStickyPort()}
        options.port(wireMockServer.port());
      }
      wireMockServer.stop();
    }
  }
...
}

public class TestSomething{

  @RegisterExtension
  static WireMockExtension wireMockExtension = WireMockExtension.newInstance()
     .options(WireMockConfiguration.wireMockConfig().dynamicPort().stickyPort())
    .build();
...
}

have exactly same problem... when I have more than single class anotated by @nested, first run good, but other can't connect on declared port

After exploring the article, I identified an issue related to the Netty server experiencing network stop/start problems when Wiremock is used in conjunction with the @Nested annotation across multiple classes.
Implementing the solution suggested in the provided GitHub comment effectively resolves the issue.
.withHeader(HttpHeaders.CONNECTION, "close")

In my case, using WireMockTest annotation on the main test class (top-most one) and injecting the WiremockRuntimeInfo into BeforeEach method on that same top most test class solved the issue but I am not sure why or whether it is a permanant fix or an intermittent one. My test class is similar to this in Kotlin:
@WireMockTest(httpPort=9090)
class MainTestClass {
private lateinit var wireMockRuntime: WireMockRuntimeInfo

@BeforeEach
fun beforeEach(wireMockRuntime: WireMockRuntimeInfo) {
    this.wireMockRuntime = wireMockRuntime
    ....
}

@Nested
inner class Nested1 { ..... }

@Nested
inner class Nested2 { ..... }

}


feat: Unix domain sockets with serde transports

Picks up where #369 apparently stalled. Funny fact I didn't look at existing PRs when doing this, so we just happened to pick almost identical impls since it's basically just copying the tcp module.
All tests are passing locally, I've also run this through a local application I have using unix sockets and it appears to work as desired.
The unix sockets are behind the feature flag unix and in the unix module to keep modules similar to those in Tokio and std. They are also gated by the target OS being a unix flavor as well.
There's one minor additional tag along commit of a UI test that was failing on master.

Thanks so much! I'm away this week, will hopefully review next week

@tikue any chance of a release? I would love to start using this.

Sorry for the delay! I'll get it released this week.

It is now released, thank you for your patience! 🙏

thank you!