[FR/question]

Is your feature request related to a problem? Please describe.
I have an array of youtube links and currently i have to add them all with queue.play() wich is extremely slow
is there a faster way to do this?
Describe the solution you'd like
I would like a way to add an array of 100 youtube links to the queue in about 5 seconds instead of 100
I need to do this because of a loadqueue feature in my bot wich loads a saved playlist to the queue

Fix loads in v10.


!str Logging error instead of failing the keepAlive operator.

refs: https://github.com/akka/akka/issues/30333

Thanks for the detail review, I will update tomorrow, house moving day:)

Rebased on to current main

Awesome, lets not merge this right now because its altering the behaviour of Pekko so it should be merged only into the 1.1.x branch when its created.

@mdedetrich Create a milestone?

Sure, @pjfanning can do this I believe

I don't seem to have the ability to create milestones. I created a label - 'not-for-initial-release' as a temp approach.

@He-Pin You need to rebase this

Yes, I will do all these this weekend. @mdedetrich

will close I think.

@mdedetrich @pjfanning I have rebased this.

lgtm - seems ok to me if everyone else is happy with it

I encountered this once in production  and have to do a reboot


Clarification of value of mask_prob for HuBERT replication.

❓ Questions and Help
Thank you for providing the code for the pretraining of the HuBERT model, I had a clarification on a potential inconsitency between the paper and the codebase:
The HuBERT paper states that 8% of the the waveform encoder output frames are randomly selected as mask:

However the config (e.g. here implies that the actual value is 80%. Which is the correct value to use? I am guessing the repo is correct and the paper is wrong but would like to double check, thank you.

Clozing as I see that you divide the mask_prob by mask span length, so 8% and 80% are consistent.


Default url_format of "/:job/:name" is problematic.

The new default url_format of "/:job/:name" has been causing me all sorts of heartache and woe since upgrading to 1.0.2.
The two concerns I have are:

I think the default should come with a prefix as any route with two parts is subject to being incorrectly interpreted as being a dragonfly request. When this happens you will get a JSON parse error in the middleware which instead of doing a 'X-Cascade' => 'pass' fails and 404s.

When you name an app it creates an instance of the app. So even if you change the url_format in that instance, you still need to set it in the base config or dragonfly will try to consume routes it should no longer be interested in.

Since this has the potential to break apps out there if there is a change I think the best option is to instead change the rails config script to add a comment to alert a user of these two pitfalls and set a default that is not /:job/:name say /media/:job/:name for example.
I think the documentation (and maybe the read me) should get updates to remind the user of this default and that changing it on a named instance still won't solve the problem.
If this makes sense I will submit a pull request that makes these changes.

closing this now as it was an upgrade problem


Cleanup LFS data

Hey @christophe-kamphaus-jemmic,
GitHub reported that your repository drains and exceeds the entire LFS quota for the jenkinsci organization:

According to https://github.com/jenkinsci/opentelemetry-agent-metrics-plugin/blob/7743ac9c0c70ad5815b917acf0c409964ec1df7e/.gitattributes#L5-L19, you store various large files in LFS.
Could you clean up the files from the git history please?
Thanks in advance!

GitHub reported that your repository drains and exceeds the entire LFS quota for the jenkinsci organization

Sorry about that.

Could you clean up the files from the git history please?

Done, I've rewritten the history to remove all LFS files, which was quite painful.
Unfortunately according to https://docs.github.com/en/repositories/working-with-files/managing-large-files/removing-files-from-git-large-file-storage#git-lfs-objects-in-your-repository this might not be enough to remove these files from Github LFS remote storage.
If the repository needs to be recreated what would be the best way forward?

Done, I've rewritten the history (including all tags) to remove all LFS files, which was quite painful.

Thanks for your swift response! Unfortunately, GitHub updates LFS quotas every 30 days only, and we don't see an immediate effect.
With your permissions, I'd recreate the GitHub repository if that's needed to completely wipe the LFS data from GitHub's end. That should lead to great avail, given you've rewritten the history already.

With your permissions, I'd recreate the GitHub repository if that's needed to completely wipe the LFS data from GitHub's end. That should lead to great avail, given you've rewritten the history already.

Fine with me. Go ahead.


Analyzer does not report "Method 'X' cannot be called on 'O' because it is potentially null"

Code sample:
class A {
  A();
  void f() {}
}

A? a;

void main() {
  final f = a != null
      ? Future.value(a)
      : Future<A?>.delayed(const Duration(seconds: 1)).then((_) => A());
  f.then((value) => value.f());
}

IDE (VS Code) does not report errors, but trying to run the app gives the error:
Error: Method 'f' cannot be called on 'A?' because it is potentially null.
package:testapp37/main.dart:14
- 'A' is from 'package:testapp37/main.dart' ('lib/main.dart').
package:testapp37/main.dart:1
Try calling using ?. instead.
  f.then((value) => value.f());

Expected behavior is that I should see the error in IDE (VS Code Problems-tab) while editing the code.
This modified code works in IDE as expected:
class A {
  A();
  void f() {}
}

A? a;

void main() {
  final f = a != null
      ? Future<A?>.value(a)
      : Future<A?>.delayed(const Duration(seconds: 1)).then((_) => A());
  f.then((value) => value.f());
}

Dart SDK version: 2.19.0 (stable) on "windows_x64"

Same lack of error in dartpad.dev, seems like a missing error from the analyzer.

Still no error from the analyzer. :(

It's a type inference difference, caused by the constructor Future<T>.value([FutureOr<T>? value]) inferring different T values from a nullable argument type in analyzer and CFE.
I can't say which is correct, maybe @stereotype441 can. I'm pretty sure I've seen the issue before, though.
A more direct example:
import "dart:async";
class C<T> {
   C([FutureOr<T>? value]); // Inference disagrees on this one.
   C.notOpt(FutureOr<T>? value); // Inference disagrees on this one.
   C.plain([T? value]); // No problem with this one.
}
// Not just constructors.
C<T> funcOpt<T>([FutureOr<T>? value]) => C<T>(value);
C<T> func<T>(FutureOr<T>? value) => C<T>(value);

void main() {
  int? a;
  var c1 = C(a); // C<int?> in CFE, C<int> in analyzer.
  // c1.st<E<C<int>>>(); // Fails in CFE, OK in analyzer.
  c1.st<E<C<int?>>>(); // Fails in analyzer

  var c2 = C(a); // C<int?> in CFE, C<int> in analyzer.
  // c2.st<E<C<int>>>(); // Fails in CFE, OK in analyzer.
  c2.st<E<C<int?>>>(); // Fails in analyzer

  var c3 = C.plain(a); // C<int> everywhere
  c3.st<E<C<int>>>();

  var c4 = funcOpt(a); // C<int?> in CFE, C<int> in analyzer.
  // c4.st<E<C<int>>>(); // Fails in CFE, OK in analyzer.
  c4.st<E<C<int?>>>(); // Fails in analyzer

  var c5 = func(a); // C<int?> in CFE, C<int> in analyzer.
  // c5.st<E<C<int>>>(); // Fails in CFE, OK in analyzer.
  c5.st<E<C<int?>>>(); // Fails in analyzer
}

// Static type helpers.
extension <T> on T {
  void st<X extends E<T>>() { print("$this:$runtimeType @ $T"); }
}
typedef E<T> = T Function(T);

So it's a question of how a constraint of int? <: FutureOr<T>? solves for T.
Doesn't matter if it's optional, does matter that FutureOr is involved, without it int? <: T? does solve T = int.
I think the analyzer might be doing the right thing here, or at least the consistent thing.
If int? <: T? makes T be int, why does int? <: (T? | Future<T>) not see that int? is never a Future<T>, and solve the same way for the remeaining int? <: T??
(Is it the usual mistake of not checking for nullability before whether it's a FutureOr type, and using the FutureOr<T> type inference for a FutureOr<T>? type?)
If we have to decide who's right, I don't want to decide by what works best for Future.value, because it's a badly designed API for Dart 2. Here int? actually does work better. That suggests that a change could be breaking, but if the analyzer already rejects the program, we should be OK with changing behavior.

Is it the usual mistake of not checking for nullability ... ?

I think it is. Attempted fix: https://dart-review.googlesource.com/c/sdk/+/370642
There may still be a difference when the FutureOr<T>? occurs on the smaller side of the constraints:
import "dart:async";

void main() {
  FutureOr<T>? bar<T extends num>([Object? value]) => value as dynamic;
  FutureOr<Object>? o = Future<int>.value(0) as dynamic;
  if (o is FutureOr<int>) {
    // Both FutureOr<int> and FutureOr<int>? are types of interest.
    o = bar(o)
       ..st<E<FutureOr<int>?>>() // CFE OK
      // ..st<E<FutureOr<Object>?>>() // Analyzer OK
      ;
  }
}

// Static type helpers.
extension<T> on T {
  void st<X extends E<T>>() {
    print("$this:$runtimeType @ $T");
  }
}

typedef E<T> = T Function(T);

This gives different types after assignment to o in Analyzer and CFE:

Analyzer: FutureOr<num>? (which is T instantiated to bounds).
CFE: FutureOr<int>?.

That suggests that the CFE ignores the ? and solves FutureOr<T> <: FutureOr<int>, then substitutes int back in and sees that FutureOr<int>? is not assignable.
The Analyzer probably looks at FutureOr<T>? <: FutureOr<int> and gives up, because a nullable type cannot be a subtype of a non-nullable type. With no solution to bind to T, it instantiates to bounds.
So, most likely one more missing nullability test. (Took a little to find a case which wasn't an error either way.)

Ok, let me rephrase what you're saying to make sure I understand it.
Future.value is defined like this:
abstract interface class Future<T> {
  factory Future.value([FutureOr<T>? value]) { ... }
  ...
}

Which means that if x has static type A?, then both Future.value<A>(x) and Future.value<A?>(x) are accepted by the type checker. But if the user writes Future.value(x), then what they want is almost certainly Future.value<A?>(x) (because Future.value<A>(x) would throw an exception if x is null).
Today, things mostly work out ok, because of a previously unknown (at least to me) difference between CFE and analyzer type inference, which causes the CFE to treat Future.value(x) as Future<A?>.value(x), while the analyzer treats it as Future<A>.value(x). The crux of the issue is this line from https://github.com/dart-lang/language/blob/main/resources/type-system/inference.md#subtype-constraint-generation:

If Q is FutureOr<Q0> the match holds under constraint set C:

The CFE is failing to check the nullability of Q, so it's effectively treating this as:

If Q is FutureOr<Q0> or FutureOr<Q0>?, the match holds under constraint set C:

This interpretation is clearly not what the spec text intends, so it's tempting to change the CFE to match the spec, but that means that any use of Future.value(...) applied to a nullable argument is going to start throwing exceptions if its argument is null. Which would be a very bad breakage indeed.
Do I have that about right?
I think it's crucial that we not break existing code that uses Future.value. I can see a few ideas for how to proceed:

Change the analyzer (and the spec) to match what was implemented in the CFE. This is very tempting because it's easy and non-breaking. But I don't like it, because it feels like the story here is: "we came up with a bad API for Future.value before we had null safety, and then when we added null safety, instead of fixing it, we added a hack to the type system to avoid that bad API leading to bad type inference and subtle bugs. Sorry, users!"

Leave the CFE's type inference behavior as is for now, but deprecate the ability to pass zero arguments to Future.value. Immediately put out a lint and quick fix to encourage users to replace Future.value() with Future.value(null) and Future<T>.value() with Future<T>.value(null). Then, in a future release, once users have had a chance to add explicit nulls to their Future.value() calls, change the definition of Future.value to factory Future.value(FutureOr<T> value) { ... }. I like this approach because it fixes the bad API for Future.value, but I don't like the fact that it postpones the fix to CFE type inference until later; once we do get around to making that fix, we might find out that there's some other serious reason we can't make the fix, and then we'll be back to square one.

Fix the CFE's type inference behavior now, but at the same time, add a special case type inference rule to both the CFE and analyzer that causes Future.value with one argument to type infer as though it's declared factory Future.value(FutureOr<T> value) { ... }, and Future.value with zero arguments to type infer as though there's an invisible null argument. Then, in a future release, once users have had a chance to add explicit nulls to their Future.value() calls, change the definition of Future.value to factory Future.value(FutureOr<T> value) { ... }, and drop the special case type inference rule. I like this approach because it fixes the bad API for Future.value, and it fixes the bad type inference behavior, and it gives us immediate feedback on whether this approach is going to work out in the long run. But it's also the most work of all three approaches.

I'm happy to consider other ideas too.

Do I have that about right?

Yep, precisely.
I'd prefer option 2, because it fixed the bad API sooner, but we've lived with it so far, so we can probably take the time to do this correctly.
I'd be perfectly happy to do a language versioned hack that makes Future.value  behave like a parameter type of FutureOr<T> (no ?, not optional) for code that has language version 3.next and forward.
There will be migration, so a release first where it's only a warning may give a smoother transition.
We could perhaps make the fix language versioned too, to introduce it sooner.
(And we should check for more issues of this kind. As I wrote, there is at least one more.)


update documentation for SQL API

Codecov Report

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

@@          Coverage Diff           @@
##           master     #22   +/-   ##
======================================
  Coverage    46.5%   46.5%
======================================
  Files         162     162
  Lines        5991    5991
  Branches     1006    1006
======================================
  Hits         2786    2786
  Misses       2783    2783
  Partials      422     422

Continue to review full report at Codecov.

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


Implemented sequence builder

PR for #29

Coverage increased (+0.5%) to 90.086% when pulling fde7b398ec3bbccc6d7165f29a8a6b90e4c5ba63 on salikjan:29 into e3024a5a4944f128f40ecbb27b0031474d6ad677 on decorators-squad:master.

@salikjan looks ok, just please change the PR title and description. Title should be something like: "Implemented sequence builder" and in the description, say something like: "PR for #29"

@amihaiemil done

@rultor merge pls

@rultor merge pls

@amihaiemil OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge pls

@amihaiemil Done! FYI, the full log is here (took me 1min)


add roadmap.sh roadmaps as course content

What does this PR do?
Add resource(s)
For resources
Description
I've added roadmap.sh roadmaps in every en course section that they exist for.
Why is this valuable (or not)?
roadmap.sh is #6 on GitHub and it is widely regarded as a great free resource for all developer topics.
How do we know it's really free?
You can access all roadmap without even needing to create an account.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

I think a single entry for this site belongs in https://github.com/EbookFoundation/free-programming-books/blob/main/books/free-programming-books-subjects.md#0---meta-lists
Does roadmaps.sh link to free-programming-books?

I think a single entry for this site belongs in https://github.com/EbookFoundation/free-programming-books/blob/main/books/free-programming-books-subjects.md#0---meta-lists
Does roadmaps.sh link to free-programming-books?

I see why you say that, although various other creators like FreeCodeCamp feature in the majority of sections rather than in one location?
If you can find a logical place for Roadmap.sh to link to free-programming-books then we would be happy to!

To take python as an example. We get submissions for websites about python, blogs about python, articles about python, etc. We don't accept those. Scope creep. We take books, courses, interactive tutorials, cheatsheets and playgrounds. I would describe roadmap.sh as being akin to a nonlinear course syllabus; we don't accept syllabi. The section I suggested has a number of other hard-to categorize resources that don't quite fit in our other lists.
F-P-B organizes resources in an outline. I can imagine some sort of overlay map that folks would find really useful.

Ok that makes perfect sense now thanks! I'm happy to go from the 30 additions to the one in the meta section 😅
Happy to work with you in regards to what roadmap.sh can do, just let me know! 🙏

@eshellman I've removed all additions of roadmap.sh and only added it to the MOOC section 👍

Thanks, and welcome to free-programming-books!


daemon wont start with Could not open sound card! Error: ALSA function 'snd_ctl_open' failed with error 'ENODEV: No such device'

Feb 08 12:19:35 alarm systemd[1]: Started Speaker Protection Daemon.
Feb 08 12:19:35 alarm speakersafetyd[595]: INFO  [speakersafetyd] Starting up
Feb 08 12:19:35 alarm speakersafetyd[595]: INFO  [speakersafetyd] Config base: "/usr/share/speakersafetyd/"
Feb 08 12:19:35 alarm speakersafetyd[595]: INFO  [speakersafetyd] Machine: apple,j313
Feb 08 12:19:35 alarm speakersafetyd[595]: INFO  [speakersafetyd] Config file: "/usr/share/speakersafetyd/apple/j313.conf"
Feb 08 12:19:35 alarm speakersafetyd[595]: INFO  [speakersafetyd] Device: hw:AppleJ313
Feb 08 12:19:35 alarm speakersafetyd[595]: WARN  [speakersafetyd::uclamp] Failed to set uclamp
Feb 08 12:19:35 alarm speakersafetyd[595]: INFO  [speakersafetyd] Enabling blackbox, path: "/var/lib/speakersafetyd/blackbox"
Feb 08 12:19:35 alarm speakersafetyd[595]: INFO  [speakersafetyd] Found 2 speakers
Feb 08 12:19:35 alarm speakersafetyd[595]: INFO  [speakersafetyd] Opening control device
Feb 08 12:19:35 alarm speakersafetyd[595]: ALSA lib confmisc.c:165:(snd_config_get_card) Cannot get card index for AppleJ313
Feb 08 12:19:35 alarm speakersafetyd[595]: thread 'main' panicked at src/helpers.rs:12:13:
Feb 08 12:19:35 alarm speakersafetyd[595]: hw:AppleJ313: Could not open sound card! Error: ALSA function 'snd_ctl_open' failed with error 'ENODEV: No such device'
Feb 08 12:19:35 alarm speakersafetyd[595]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Feb 08 12:19:35 alarm speakersafetyd[595]: WARN  [speakersafetyd] Panic!
Feb 08 12:19:35 alarm speakersafetyd[595]: WARN  [speakersafetyd::blackbox] Blackbox is empty, nothing to save
Feb 08 12:19:35 alarm systemd[1]: speakersafetyd.service: Main process exited, code=exited, status=101/n/a

I'm trying to install this thing on my journey to getting my speakers to work, don't know if I'm missing something. Please help.
My lsp-plugins version is on 1.2.14

The ALARM repo is extremely incomplete as bandwidth to maintain it sorta fell away while we worked to get Fedora out the door. You need a newer kernel, newer UCM conf files, and the Pipewire/Wireplumber DSP files for this to work at all.

Shame. So I need to change to the Fedora version?

Yup, works on the Fedora version. Thank you for the quick reply.

The ALARM repo is extremely incomplete as bandwidth to maintain it sorta fell away while we worked to get Fedora out the door.

Just to let you know, with the pull requests from joske (https://github.com/AsahiLinux/PKGBUILDs/pulls/joske) Asahi ALARM works like a charm now.


HTTP Transport/RoundTripper?

Hi all,
I'm trying to call an NTLM-authenticated HTTP service in Go. I'm running on a Windows host and the default user credentials accessible via SSPI have access to this service.
I've tried using the following related modules:

Azure/go-ntlmssp: Provides a RoundTripper for NTLM auth, but appears to expect explicit credentials
dpotapov/go-spnego: Provides an SPNEGO RoundTripper (and depends on this package!), but appears to only support Kerberos itself (not NTLM)

I tried reading through the tests as described in #6 (comment), but I'm not well-versed in Go and didn't understand how to chain this into existing HTTP client calls. I have to provide an NTLMSSP_NEGOTIATE message to the server before getting an NTLMSSP_CHALLENGE, and I'm not sure how to build one of these using the methods provided in sspi or sspi/negotiate.
Is there some documentation available for using this package to do NTLM negotiation?

Is there some documentation available for using this package to do NTLM negotiation?

If you need to call a NTLM protected http server from Windows client, try this test
https://github.com/alexbrainman/sspi/blob/1a75b4708caa219fd8d8261cd37c923ff6710a32/ntlm/http_test.go#L121-L155
This is very old code that have not been tested for a long time. So I would not be surprised that it does not work.
Alex

Thanks for the context! I was able to write a RoundTripper based on this and the one from Azure/go-ntlmssp.


Add listReportingSets and unit tests.

This change is

Current dependencies on/for this PR:

main

PR #985

PR #992   👈

This comment was auto-generated by Graphite.


Pretrained model and minifrance dataset

@Apiquet ,Is there a file where we can use pre-trained weights for the model you developed? If there is no such file, I couldn't decide which files in the minifrance dataset I should download for training?

Hello, there are no pre-trained weights available but you can run the training script on the labeled training partition (10.37GB)


Use %r in the TextNode repr to show newlines better.

If the TextNode contains a newline, the old %s code will look like this:
<Text Node: '
Last
'>

With %r, it will look like this:
<Text Node: u'\nLast\n'>

buildbot, add to whitelist.

I guess a test would be useful.

@timgraham added a test.

merged in 3b81dbe844b750c05bda6ae1ad15c889d1dc39e5, thanks!


Node.js new model - id is required

Can the id property not be required or default to the invocation Id instead of having to set it? Cosmos doesn't natively require an id property, and sets it for you if you don't include one.

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

ID: 28aac762-b154-1d0e-9afc-67889fdf9762
Version Independent ID: 9a406f60-6c72-d3d9-2bc9-8d8e8c1922ae
Content: Azure Cosmos DB trigger for Functions 2.x and higher
Content Source: articles/azure-functions/functions-bindings-cosmosdb-v2-trigger.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@core-dev-out
Thanks for your feedback! We will investigate and update as appropriate.


Discussion for further sensor filtering and algorithmic improvements

A continuation of the fruitful chat with @jaymunro in #99 which lead up to the v0.5.0 release today.
I've been finding the elimination of peaks to be pretty promising thus far.

Sorry, been caught up with various matters. But I do now have some metrics with the change in filtering.
As we see here, the outliers with Max (tesla) are greatly reduced after the Mar 18 update but area resolution is only mildly improved.

However the Suma (Microtik beacon) seems changed but still has quite a few outliers and area resolution is only mildly better if at all.

I think this needs a bit more of a detailed look which I hope to get to over the next few days.

As per the screenshot in #144 (also below), we see Zoe bouncing back and forth between the kitchen and dining room. Where she was sitting at the time was fairly equidistant between both proxies. However due to the nature of the proxies (they're Shellys in the light switches) they tend to be on one side of a room and not in the centre, so this may become quite a common occurrence. But location accuracy is a subject for another time.
To mitigate the bouncy times, I was thinking if we could determine the person is stationary and we are seeing this behaviour, then we could make the proxies a bit 'stickier', as in the area entity would require a higher difference in distance before switching back to the other.
I think this could be done by:

Recording the previous 3 proxies [A, B, C]
If the current proxy [B] or the previous proxy [A] is the same as the one just it is just about to switch to [A] or [C], then turn on a flag with those two or three proxies as attributes.
If the flag is on and an proxy switch is about to occur into an proxy not in the flag attributes, clear the flag
If the flag is on and an proxy switch is about to occur into an proxy in the flag attributes then incorporate the interval since the last switch into a stickiness attribute. The method of incorporating it may be an average or similar that would result in a value in metres that would increase with swaps and would be added to the distance of any proxy about to be switched to that is in the stickiness attributes.

The idea being that if swapping is frequent the stickiness goes up and as the frequency decreases, the stickiness average would decrease, kinda an inverse to the time * the average distance to the proxies * a fudge factor.
That way stationariness (gee, I didn't know that was a word) is determined by the frequency of swapping and the stickiness attribute auto regulates the swapping without interfering with moving to another proxy (area) nor interfering with actually moving closer to one of the proxies in the stickiness flag.

Hmmm that's an interesting approach. It makes sense that entities that are "flapping" between areas could benefit from some damping to their ability to switch.
I've been thinking about this in the back of my mind while doing the filtering stuff, too. I'll give your idea some time to percolate. My current thinking is that a lot of this switching is (probably?) caused by the current proxy receiving occluded signals or missing packets, rather than the usurper proxy actually reading closer (I'll need some more data to confirm that) or at least, not reading much closer than it was previously.
I'm thinking it might work to compare the velocities implied by the two proxies (mathematically this might be exactly what you're suggesting, since we're integrating distance over time). If the challenging proxy implies a low "approaching" velocity, then we can assume it's probably stationary and the two proxies are reasonably equidistant or the incumbent proxy is giving poor quality readings right now. However if the usurper proxy is indicating a "high" "approach velocity" (as opposed to the "retreat velocity" that max_velocity enforces) then we can assume it really is getting closer to that area, and we should switch.
I think this might give more stability but without compromising on responsiveness, based on the plots I've seen while testing.
Does that sound like a decent approach to you? I'm leaning somewhat toward trying to model things more... Newtonianly(?!) as my previous area-deciding logic got pretty confusing to debug once I was several levels deep in comparing proxies using more "reasoning-based" approaches.
For what it's worth, I think the long-goal of trilateration will inherently assist with this, as it will start to "understand" the relative relation between proxies/areas, rather than treating them as a binary/ternary/(n-ary?) choice.
Could you gather some graphs of Suma's "distance to" measurements for the proxy's it tends to switch between, along with the "Area" sensor? So similar to the below, without the final "distance" sensor or any of the "unfiltered" sensors, and at a fine-enough timescale that I can see the per-interval updates during some of the decisions.
Here's a beacon I carried to and left on a table, roughly equidistant from kitchen and dining proxies. I left the area, and even with no motion nearby (there was someone a few metres the other side of the lounge proxy) we still get a fair amount of variability. (my rssi figures aren't well-calibrated at the moment, our dining/kitchen is rather significantly less than 100sqm!)

Interesting points:

the "kitchen gap" is a long drink between packets. I can't see any evidence of the proxy going offline during that time, so it's a bit odd. It is running esphome 2023.9.1 so perhaps it's an older ble issue.
A, B and C all resulted in (initial for A/C) area switches due to kitchen getting a a reading at a time that dining's reading was over 2 seconds old. There are cases where switching would be valid in that case, but I think the fact that Kitchen's "velocity" is zero for that and many prior readings should prevent the switch - even though dining's velocity is up, it's "retreating" which means less reliable, so Kitchen having an "approach velocity" less-than-or-equal-to nearly zero should prevent an area switch.
A and C's second area switches are a little different, while their first switch seems to be based on "freshness" (ie stale readings from incumbents), but the second switches at A & C are "valid" (but not valid) case of kitchen now having a closer (or perhaps equal, for C?) range. But if we used the same velocity-based filter again, we would ignore the change because the usurping proxy still has a near-zero-or-negative "approach" velocity.
D is tricky. It was caused by someone moving around in the adjacent room(!) We see the range on Kitchen still being very steady, while dining reads the beacon as retreating. I don't know what an ideal outcome should look like for D. The kitchen range is strong evidence for the beacon not moving (a stable signal is statistically less likely than a noisy signal, so it deserves extra trust), so should we try to conclude that the other readings are erroneous from noise (which is "relatively" true) or should we conclude the beacon was circling the dining beacon in an ideal (ie, impossible, but relevant) way? Once the kitchen reading is longer it's hard to make a case for "it hasn't moved" but the rock-solid range from dining really does imply that it hasn't - a device that really is moving should probably cause reasonable perturbation to all proxies readings due to reflections etc - unless it's super-close.

I think that similarly to how we have a max_(retreat)velocity for deciding if a retreating reading is valid for the incumbent proxy, a min_approach_velocity could decide if a proxy should win the area contest even if it is now the closest. I think it would have to be tempered with a timeframe limit of how long it can have the closest reading and a low velocity before it wins the contest.
At any rate, D is an issue, since it's hard to distinguish between "stationary beacon, gradual noise effects on proxies" versus "beacon circling a proxy" - I think I lean toward the former, for the most part.
Multiple proxies in each area really does solidify things though - with two proxies in my studio I basically never get spurious area switches for my watch, even though it is particularly prone to signal variations based on wrist position and orientation. Again, trilateration would also solve a certain amount of this, since it doesn't suffer from having to treat areas as being defined only by proxies "in" that area.
I'll be interested to see if my observations here line up with what you're seeing as well.

Could you gather some graphs of Suma's "distance to" measurements for the proxy's it tends to switch between, along with the "Area" sensor? So similar to the below, without the final "distance" sensor or any of the "unfiltered" sensors, and at a fine-enough timescale that I can see the per-interval updates during some of the decisions.

Suma is not switching much at all any more. Unless it is leaving there is only one proxy close by (the garage door opener). The next closest is the back garden esp32 (M5Stack) which is a bit temperamental. It seems to only want to communicate to one HA at a time, sometimes my production, sometimes my dev, whereas the Shellys will quite happily communicate to both.
I think this screen shows what you're looking for, but it also shows that sometimes the Shelly's reception will have unfiltered distances between 1.26m - 3.16m (left side of the graph) for many hours, and then when the other car leaves (4:42) it will swap to distances between 1.26 and 6.81 (right side of the graph), and when the other car returns it will change again (1.26-5.01m in the case of last night). I'm just mentioning this to give an example of how much things can change with a change in environment, but yet while everything is static (no one in garage and nothing moving) there are still huge variations in the signal.

Also note that the M5Stack esp32 is connected via WiFi but it is still monitoring Bluetooth. I believe the default settings in ESPHome (below) mean that every 320ms it will scan for bluetooth signals for only 30ms. This naturally results in many missed packets, hence the gaps in the 'back garden' graph. The Shellys don't seem to suffer from this, likely because they have multiple radios.
https://esphome.io/components/esp32_ble_tracker.html
esp32_ble_tracker:
  scan_parameters:
    interval: 320ms
    window: 30ms

Now that Private BLE is connected though, I can also add my watch or phone. In this graph I'm stationary in the office with both the hallway sensor (M5Stack) and Office ceiling light are right next to the office door (same horizontal distance but switch is about 30cm higher up. The bathroom heater switch is in the next room through an interior wall (but about same distance).

As the start to a spawning idea, in this case the average between ceiling light and hallway sensor should give a clearer signal. Might be interesting to see.

(oh, also - I'm stoked about the code you pulled together for trilateration and I'm itching to get it integration as soon as I can!)

Hey, I was wondering if you had to do much work to set up your shelly's, or what settings you are using on them? On the community thread, lazmo88 is seeing a lot of big gaps in packet reception, so I'm wondering if its the script setup on the shelly side that's giving them grief. In particular, looking at hist_interval in the dump_devices output shows gaps upwards of a minute at times - have you seen anything similar with yours?

https://community.home-assistant.io/t/bermuda-bluetooth-ble-room-presence-and-tracking-custom-integration/625780/84?u=hjm
That's all I did. Just 10 seconds beyond setting up the Shelly's on the WiFi and accepting the prompt to add the Shelly's inside HA. (Plus about 1-2 hours of investigation on the difference between the Shelly WebUI setting 'Enable Bluetooth gateway' and the HA setting 'Bluetooth scanner mode').
Once I figured it out though, adding a Shelly and setting it up as a "Bluetooth scanner" is just seconds per device. Additionally, they are super reliable and push updates immediately into HA. I have about 13 now and will be adding the new Shelly Mini PM into all power sockets just to monitor whole house power usage. That'll be about another 15 Shellys @ 12 euros each.

(oh, also - I'm stoked about the code you pulled together for trilateration and I'm itching to get it integration as soon as I can!)

Yep, me too Ashley. Might be starting some new work soon so free time may go down a bit till I get up to speed.
All the same, that code just took one late night to pull together. I was surprised how easy it was.


13 add cli help flag

Description

Added -h/--help flags to display help information at the CLI - Closes #13.
Also added -v/--version flags to display version details.
Motivation and Context

As described above.
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

Tested locally and in CI - working as expected. Core parts of help message are also covered by a unit test.
Test configuration details:

OS: macOS
rustc version: rustc 1.74.1 (a28077b28 2023-12-04)
cargo version: cargo 1.74.1 (ecb9851af 2023-10-18)

Advice for reviewer

None
Checklist:

[x] My code follows the intended structure of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] Change log has been updated

Additional comments

None

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.98%. Comparing base (d11fcbd) to head (bbd4e27).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #14      +/-   ##
==========================================
+ Coverage   90.71%   90.98%   +0.26%
==========================================
  Files           4        4
  Lines         237      244       +7
==========================================
+ Hits          215      222       +7
  Misses         22       22

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


feature request: toggling without losing the state

Current behavior

toggle plugin on
go to deployment (or any other)
toggle plugin off
toggle plugin on
the initial pod window shows

Better behavior

toggle plugin on
go to deployment (or any other)
toggle plugin off
toggle plugin on
the view from step 2 should show up

Bonus
Partial render the plugin e.g. load the UI first and then start fetching resources. This will boost the start-up and navigation time.

I do like the idea of saving state, not sure how I would fit that in with multiple sessions but I'll give it a shot.
The bonus one is nice as well, I noticed that k9s does it like that and it does feel faster.

Maybe we could save it to local file on the users side and pull from that? Gitpad.nvim is doing something like that

I'll take a look and see what we can do!

Solved by #164


Error downloading weights in ComfyUI/models/ultralytics/segm

I am getting the following error when I run a json file. What could be the issue here?
Prediction failed.
Command '['pget', '--log-level', 'warn', '-xf', 'https://weights.replicate.delivery/default/comfy-ui/ultralytics/segm/hair_yolov8n-seg_60.pt.tar', 'ComfyUI/models/ultralytics/segm']' returned non-zero exit status 1.
Traceback:
Error: unexpected http status http://storagecache-ch-las1-3.storagecache-ch-las1.tenant-replicate-prdsvcs.svc.cluster.local/weights.replicate.delivery/default/comfy-ui/ultralytics/segm/hair_yolov8n-seg_60.pt.tar: 404 Not Found
Traceback (most recent call last):
File "/root/.pyenv/versions/3.10.6/lib/python3.10/site-packages/cog/server/worker.py", line 221, in _predict
result = predict(**payload)
File "/src/predict.py", line 105, in predict
wf = self.comfyUI.load_workflow(workflow_json or EXAMPLE_WORKFLOW_JSON)
File "/src/comfyui.py", line 216, in load_workflow
self.handle_weights(wf)
File "/src/comfyui.py", line 92, in handle_weights
self.weights_downloader.download_weights(weight)
File "/src/weights_downloader.py", line 39, in download_weights
self.download_if_not_exists(
File "/src/weights_downloader.py", line 60, in download_if_not_exists
WeightsDownloader.download(weight_str, url, dest)
File "/src/weights_downloader.py", line 71, in download
subprocess.check_call(
File "/root/.pyenv/versions/3.10.6/lib/python3.10/subprocess.py", line 369, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['pget', '--log-level', 'warn', '-xf', 'https://weights.replicate.delivery/default/comfy-ui/ultralytics/segm/hair_yolov8n-seg_60.pt.tar', 'ComfyUI/models/ultralytics/segm']' returned non-zero exit status 1.

Same error appearing after version update today:
Checking weights
⏳ Downloading segm/hair_yolov8n-seg_60.pt to ComfyUI/models/ultralytics/segm
Error: unexpected http status http://storagecache-ch-ord1-3.storagecache-ch-ord1.tenant-replicate-prdsvcs.svc.cluster.local/weights.replicate.delivery/default/comfy-ui/ultralytics/segm/hair_yolov8n-seg_60.pt.tar: 404 Not Found

This should be working now, I've just pushed a fix:
https://weights.replicate.delivery/default/comfy-ui/ultralytics/segm/hair_yolov8n-seg_60.pt.tar

Great! Thanks for the quick resolution.
I have another question. I would like to pass the input images in base64 format from my application. However comfyui does not seem to accept this _(Failed to validate prompt for output 144: * LoadImage 134:

Custom validation failed for node: image - Invalid image file: http://data:image/jpeg;base64,/9j/4AAQSkZJRgABAQEBLAEsAAD/4Y5WRXhpZgAATU0AKgAAAAgACg......)_

Is there any way that it can accept the image without hosting the image somewhere? I know for sure that replicate api accepts base64 image format as it accepts for other models. It would be great if the replicate interface has option for 2 input images instead of only one. Since sending images as zip file from my app through api does not seem feasible.  Therefore I use base64 embedded inside the url to send image through api.

If you pass in the image as file in the API call, and in your workflow refer to input.jpeg that should work.

Closing this issue now as it is fixed, but feel free to reply/open another issue.


Error decoding Elasticsearch 6 output

I have built a Docker image using the most recent commit (6101e75) and run it like this
docker run --network=host --rm justwatch/elasticsearch_exporter:my-branch -es.uri=https://localhost:2006 -es.ssl-skip-verify -es.all -es.indices

where https://localhost:2006 is an ssh tunnel to an instance in my AWS VPC that can access my AWS ES instance
when I request the Prometheus metrics I have this logs on the exporter
level=info ts=2018-03-20T10:50:31.247196875Z caller=main.go:78 msg="starting elasticsearch_exporter" addr=:9108
level=warn ts=2018-03-20T10:50:34.808472329Z caller=cluster_health.go:258 msg="failed to fetch and decode cluster health" err="failed to get cluster health from https://localhost:2006/_cluster/health: Get https://localhost:2006/_cluster/health: x509: certificate is valid for *.amazonaws.com, not localhost"
level=warn ts=2018-03-20T10:50:34.808551908Z caller=nodes.go:1383 msg="failed to fetch and decode node stats" err="failed to get cluster health from https://localhost:2006/_nodes/stats: Get https://localhost:2006/_nodes/stats: x509: certificate is valid for *.amazonaws.com, not localhost"
level=warn ts=2018-03-20T10:50:34.816269535Z caller=indices.go:409 msg="failed to fetch and decode index stats" err="failed to get index stats from https://localhost:2006/_all/_stats: Get https://localhost:2006/_all/_stats: x509: certificate is valid for *.amazonaws.com, not localhost"

I did send the http requests manually and this is the output
https://gist.github.com/carlosjgp/6e6a6d74eda703b93e9067734ff4618c
I can try to create a PR to add a parameter to configure the ES version... maybe is not that easy. I would like to start doing some GoLang coding, so I'm quite keen to try it

Hi Carlos,
thanks for bringing this up and thanks for the helpful gist. I need to have a closer look at it. Until now we tried to avoid explicitly setting an ES version. If possible we'd like to stick with an version agnostic elasticsearch_exporter. To avoid creating an unnecessaryPR, we should finish this discussion about setting an ES version first.
As far as I know, ES supports POST and GET requests for some queries. So maybe a possible solution is to add a method flag. I need to evaluate this. If it is the way to go, I'll happily help you with creating the code/PR.

I've just looked into this, and the errors above are purely SSL verification errors - I tested the project with ES version 6 and it still works perfectly :+1:

Hi @carlosjgp, I've just merged a es.ssl-skip-verify fix PR. Can you try the latest master again with -es.ssl-skip-verify flag set?!

closing this issue as I think it's resolved. Feel free to re-open if the problem isn't solved for you, @carlosjgp

I am still facing this issue. Getting 401 error,
bash-4.1$./elasticsearch_exporter -es.all=true -es.indices=true -es.shards=true  -es.ssl-skip-verify -es.uri="http://localhost:9200" level=info ts=2018-07-03T08:14:46.113926062Z caller=main.go:81 msg="starting elasticsearch_exporter" addr=:9108 level=warn ts=2018-07-03T08:14:54.129103043Z caller=nodes.go:1383 msg="failed to fetch and decode node stats" err="HTTP Request failed with code 401" level=warn ts=2018-07-03T08:14:54.129136234Z caller=indices.go:458 msg="failed to fetch and decode index stats" err="HTTP Request failed with code 401"
due to which I am not able to get all the metrics supported by the elasticsearch exporter.

Hi sammit20,
using -es.ssl-skip-verify with a non-https es.uri doesn't make sense. So your either getting the 401 because TLS is required (thus using a https es.uri) or basic auth is required. In the latter case you can specify the credentials like so -es.uri=http://username:password@localhost:9200

Thanks zwopir for the quick response. However my cluster doesn't have any authentication specified.  Its a test one for checking the elasticsearch exporter metrics. I can easily access the apis like http://localhost:9200, http://localhost:9200//_nodes/stats,http:/localhost:9200/_nodes/stats, http://localhost:9200/_all/_stats without any authentication. So in that case what value I need to pass in the ES.URI parameter to get the nodes and indices metrics?

Hi sammit20,
I tried to reproduce your issue with the latest ES docker image. Started the image as described in https://www.elastic.co/guide/en/elasticsearch/reference/6.3/docker.html and then the exporter with
./elasticsearch_exporter -es.all=true -es.indices=true -es.shards=true

I was not able to reproduce your issue. The es.uri Parameter defaults to http://localhost:9200, so you don't need to specify it, if you are running the exporter on one of the ES cluster nodes

Thanks Zwopir for checking on that. Can you check the same from Binary as well? As I've downloaded the binary"elasticsearch_exporter_1.0.3rc1.linux_amd64-v1.0.3rc1" and executing with that.

I did check it with the binary. The ES (not the elasticsearch_exporter) was running in the container

Thanks zwopir for your help. The issue was with my cookie which was not letting me to access metrics page. Is there any way to include the cookie while executing the exporter?


Add missed needs to release flow

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


chore: [FX-4133] remove Quilll editor

FX-4133
Description
Remove all occurrences of Quill from rich-text-editor
How to test

temploy works as expected
no quill dependencies in yarn.lock file
documentation is updated

Development checks

[ ] Ensure that deployed demo has expected results and good examples
[ ] Self reviewed

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-anvil ping reviewers


DDPB-3291: Mark public services or inject them

Purpose
In Symfony v4, all services are treated as private by default and cannot be retrieved with Container::get(). That means that services will either need to be marked as public in configuration, or dependency injected.
Dependency injection is preferable, as it means that Symfony only instantiates the classes necessary. Any public services are loaded on every request (which slows down the application).
To get ahead of this, we want to implement more dependency injection and identify services which should be public.
Fixes DDPB-3291
Approach
I searched for usages of Container::get() and replaced them with dependency injection. In a few places this wasn't possible so I explicitly made the service public (e.g. RestClient is loaded dynamically in far too many places to reasonably rewrite right in one PR).
I also tidied up some configuration files, and more or less completely rewrote ManageController because it was leaning really heavily on dynamic service loading.
I briefly tried to upgrade to Symfony v4 to check if the changes worked, but there are too many differences to reasonably test against. The application built successfully though, which suggests the configuration is fully compatible.
Learning

There's way more we can do to tidy up the config files; I think a lot of it is unnecessary now
I've mostly done away with aliases and instead use class names (e.g. ->get(AuthService::class) rather than ->get('auth_service')) to make dependencies more explicit (in the few instances of public services)
A couple of v4 things I noted to be aware of:

In unit tests, we can't just use Container::set() to replace a service with a mock (because the service will be private). To allow this, we just need to add AppBundle\Service\SomeService: { public: true } to each service that needs to be overwritten in config_unittest.
I saw some issues with the AppKernel and container tags. I hope the changes in DDPB-3290 will help with this, but undoubtedly we'll have some follow-up work at the point of upgrade.

Checklist

[x] I have performed a self-review of my own code
[x] I have updated documentation (Confluence/ADR/tech debt doc) where relevant

N/A

[x] I have added tests to prove my work

I've tried to make minimal test changes to demonstrate this work hasn't actually changed anything

[ ] The product team have approved these changes

Great job. Seems like a huge part of the upgrade has been addressed here. Just one question to address


TaskQueue is not a constructor

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.20
Platform / OS version: Ubuntu 16.04
URLs (if applicable):
Node.js version: 10.6

What steps will reproduce the problem?
After an npm update puppeteer does not start anymore.

Please include code that reproduces the issue.
const browser = await puppeteer.launch()
What is the expected result?
Puppeteer should work as before
What happens instead?
Throws error in line 51

console.log says TaskQueue is undefined, what is odd because it is required in lib/Browser.js

And there is the file:

lib/TaskQueue.js

Looking closer the curly braces were missing. https://github.com/puppeteer/puppeteer/blob/v1.20.0/lib/TaskQueue.js#L17
No idea how I am ended up with this version, but npm i again solved it.


Delete a number of old unused refresh parsers

There are a few refresh parsers left in core which are now unused and can be deleted.
Cross Repo Tests: https://github.com/ManageIQ/manageiq-cross_repo-tests/pull/93

Travis https://travis-ci.org/github/ManageIQ/manageiq/builds/665905584 and cross-repo tests https://travis-ci.com/github/ManageIQ/manageiq-cross_repo-tests/builds/154645181 are green


RGBW/RGBWW support, general fixes

Adds RGBW/RGBWW support thanks to @DanGunvald (originally proposed in #1). Also includes the following:

MQTT last will and testament
move configuration into its own file
output unknown IR codes to serial/telnet
some more general fixes

Closes #5

@DanGunvald @robbiet480 Thanks for your amazing work!

@mertenats Don't go anywhere quite yet, got some more stuff coming in the next 10-20 minutes. :)

@mertenats Can you try out this latest code when you have a moment, specifically test out the color stuff? I think that color changing may have broken with this PR because it seems RGB is now reversed...

@robbiet480 You must hold the record for greatest number of contributions to HA related firmware / software surely by now LOL

@robbiet480 Thanks again for the amazing work! I'm currently not at home until the end of the month, so I can't test it.

@mertenats Okay, will test more myself and try to figure out what went wrong...

@mertenats Fixed in 7596a4123f03ed2dd5f8a4f2fc51af254214a303. Wondering if the RGBWW pins are wrong too, I don't have one of those boards to test with :(

I can verify the WW pins tonight, as I am using the lc08. I dont recall whether I am using the latest code.

Pin setup for lc-08 is correct in current code(cloned 2017-03-07). RGBW needs to be defined for RGBWW to work.
"#ifdef RGBW" in Arilux.cpp should be replaced with "#if defined(RGBW) || defined (RGBWW)" on order to remove the dependency og RGBW when choosing RGBWW.

I have a white led strip.
There is only + and - output.
Can I use LC04 (RGBW + IR).
Which channel I have to use. W? or R?

It doesnt matter what you use if you set all channels to the desired level. LC04 should work.

Thank you @DanGunvald
I bought LC04.
I will try.


Add examples to all functions supported across languages

We'll need to add an example per R function for #1851, so we might as well do this for all functions that are supported across Scala, Java, Python, and R.

Closing as WontFix


The status indicators are not visible on mobile if the keyboard (on mobile device) is shown.

Won't fix.
The keyboard on mobile devices is supposed to overlap with the browser area.


[Request] Dataset terms of use / Licence

Hi,
Thank you for your work compiling this data and making it available to the community.
I was not able to find any licence or terms of use for this data, are there any ? and if so would it be possible to add this detail to the repo ?
This would greatly simplify the process of getting approval for its use in my company.
Thank you again.

Hi,
Really sorry for the delayed response. I've added the license file (CC-BY-4.0). Free to use it however you see fit with attribution.
Best,
Sean
---- On Tue, 19 May 2020 17:34:27 +0100 Brian Maguire<EMAIL_ADDRESS>wrote ----
Hi,
Thank you for your work compiling this data and making it available to the community.
I was not able to find any licence or terms of use for this data, are there any ? and if so would it be possible to add this detail to the repo ?
This would greatly simplify the process of getting approval for its use in my company.
Thank you again.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, https://github.com/ProPrivacy/covid-19/issues/1, or https://github.com/notifications/unsubscribe-auth/APDQQNWNQTUW5WS32ZYC63DRSKYJHANCNFSM4NFFE3BQ.

That's brilliant! thanks for your help with this.


Build and deploy inaturalist-notebook Docker image for new pyinaturalist releases

Image repo: https://github.com/JWCook/inaturalist-notebook
I believe this can be triggered using the repository_dispatch event.

It works! It's pretty slick once it's set up.

Test trigger: https://github.com/niconoe/pyinaturalist/runs/2052379668?check_suite_focus=true
Test deployment:
Trigger CI config: https://github.com/niconoe/pyinaturalist/blob/a955355d97a974552d8c82a5eac7b8f2053d8939/.github/workflows/build.yml#L100-L107
Deployment CI config: https://github.com/JWCook/inaturalist-notebook/blob/main/.github/workflows/deploy.yml
Image on Docker Hub: https://hub.docker.com/repository/docker/jwcook9/inaturalist-notebook/tags#110

@niconoe FYI ^^^


Upgrade from 3.1.1 to 3.4

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
3.1.1
Current Behavior
Has anyone done upgrade from 3.1.1 to 3.4?
Kong upgrade path recommendation at https://docs.konghq.com/gateway/3.4.x/upgrade/#preparation-review-upgrade-paths:~:text=to 3.4.x.-,3.1.0.x-<IP_ADDRESS>,-Hybrid suggests the following upgrade path:

3.1.1 - > <IP_ADDRESS>
<IP_ADDRESS> - > 3.2.x
3.2.x - > 3.3.x
3.3.x -> 3.4.x

However there is no <IP_ADDRESS> release at all for OSS https://cloudsmith.io/~kong/repos/gateway-31/packages/?q=format%3Arpm
Has anyone upgraded from 3.1.1 to 3.4 successfully? If yes, would appreciate if you could share the upgrade path chosen.
Expected Behavior
Requesting Kong to release <IP_ADDRESS> as per the upgrade path suggested https://docs.konghq.com/gateway/3.4.x/upgrade/#preparation-review-upgrade-paths:~:text=to 3.4.x.-,3.1.0.x-<IP_ADDRESS>,-Hybrid
OR
Kong to provide graceful upgrade path from 3.1.1 to 3.4
Steps To Reproduce
Refer the upgrade path doc at https://docs.konghq.com/gateway/3.4.x/upgrade/#preparation-review-upgrade-paths:~:text=to 3.4.x.-,3.1.0.x-<IP_ADDRESS>,-Hybrid
There is no <IP_ADDRESS> release of OSS at https://cloudsmith.io/~kong/repos/gateway-31/packages/?q=format%3Arpm
Anything else?
Refer to the above doc

Duplicated with https://github.com/Kong/kong/discussions/13785
My suggestion is upgrading to 3.2.x then follow up to 3.4

Thank you very much for your response, I was thinking of the same.


Corpus for LM

I found this file: all_corpora_filtered_maryfied.txt.gz .
Does a version before applying "mary" (and/or filtering) exist somewhere?

You can now find the non-filtered and non-maryfied file here: http://dialogplus.lt.informatik.tu-darmstadt.de/downloads/speechdata/German_sentences_8mil.tar.bz2


How to process pathological images?

Hello! Thank you for your wonderful work！I want to know what to do when I need to process a large scale pathology image.
I ran gui.py and circled the required section, but it identified the normal cells and ignored the cells I needed the label for. What's more, I need to circle plenty of times on the images since it's scale. I wonder if I need to get patches and then splice them together.

Thank you for your effort again！

Hi @Leelinw ,
What is your segmentation target?
If it is the gland, you may need to cut the WSI into patches before feeding it to medsam.

Hi @Leelinw ,
What is your segmentation target? If it is the gland, you may need to cut the WSI into patches before feeding it to medsam.

Thank you so much for your reply! What you said really makes sense, I'll try to cut my WSI and reprocessing them.
Best Wishes!


add Chang'an University domain

create chd.txt ;
add Chang'an University ,her domain it's chd.edu.cn ;

@CRISzzz Pull request merged. Thank you!


Will there be an installation package that supports Python django

RT.

Since SQLite3 Multiple Ciphers can easily replace the original SQLite3 library, because all additional API functions can be used via SQL functions or pragmas and URI paramaters, it should be quite straight forward to create such an installation package based on an existing SQLite package.
However, this is currently not on my to-do list and will therefore not happen in the near future. If someone else wants to undertake this task, I will give support, if necessary.

谢谢您的回复。我是Python的初学者，也许可以自学


deal with string gum constraints

var vgaConstraints = {
  video: {width: {exact: "640"}, height: {exact: "480"}}
};

navigator.mediaDevices.getUserMedia(vgaConstraints).then(function(stream) { console.log('yay'); }).catch(function(err) { console.log(err); })

Both Firefox and Edge deal with this, but the shim does not. I think this should cover the relevant cases. wdyt @jan-ivar?

travis failure seems to be related to bad webdriver version?

LGTM, anything else needed here?

Do we care about { video: { width: "640", height: "480" } }? Because I don't think that's working.

given that this is more complicated than it looks (thanks @jan-ivar) do we want to bother before the native constraints roll out?

Also, wont this convert { video: { facingMode: { exact: "environment" } } to { video: { mandatory: { facingMode: 0 } } ? That's wrong.

Is anyone really passing strings here?

@chadwallacehart did and asked me when it did not work :-)

ah... lets not do this. bigger harm than benefits, also since iiuc the new constraints will be available natively soon


DCOS-40158: remove left-padding for left filter bar

Removes the left padding for left filter bar.
Closes DCOS-40158
Testing

Go to Nodes page
Filter bar should be aligned

Result
Before

After

Made the change, thank you @Poltergeist @weblancaster for suggestion.

Looks great @tnguyen0!

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


Prevent error when scanning a large range of ports

When scanning hundreds of ports asynchronously, an error would occur when trying to use one of the ports that returned with status 'closed'. The problem goes away when 50 or so ports are scanned at a time.

Thanks for a nice module.
Is there a reliable chunk I can scan at a time to make sure I won't get errors? Do you know what the limit is and what it depends on?

Hi @jacobrask, are you getting the errors currently? If so, do you have some sample code that gets the error?
I was getting the error when using findAPortNotInUse with a large range (> 500), so I switched to a port range of 50 (portscanner.findAPortNotInUse(9000, 9050, hostname, function(error, port) {})) for my batch size and it's been working.
However, I just tried reproducing the issue by modifying the example code like so:
  // Finds a port no service is listening on
  portscanner.findAPortNotInUse(3000, 100000, 'localhost', function(error, port) {
    // The order is unknown as the port status checks are asynchronous.
    console.log('Found a closed port at ' + port)
  })

and could not reproduce this error.
The issue may have been from something else in my actual project code (not the sample). I'll test my project code tonight with the larger ranges to see if I can reproduce it there.

I got
Error: EMFILE, Too many open files

when specifying a range of 1018 ports or more on my workstation.
portscanner.findAPortNotInUse 49200, 50218, address, (err, port) ->
    throw err if err
    server.listen port, address, ->
        console.log "Web server listening on #{address}:#{port}"
        callback null, { port: port, address: address }

I don't really need that big of a range obviously, but it's still a limitation, and if it depends on something unknown maybe the error will trigger on fewer under some other circumstances...

Originally the scanner checked every port in the range at once and the first port to return with a matching status was returned in the find a port functions. The problem with that approach was too many socket connections seemed to cause errors that depended on a number of things, including the host.
I switched the scanner to use the async library and check one port at a time. This prevented the too many open socket error for me locally. Does this resolve your error @jacobrask?


dApp: introduce automatic propery type check

Description
At the moment we need to declare the type of a components property twice. Once for the type check of the component and another time for TypeScript itself. This looks like that:
@Prop({ type: String })
myProp!: string;

There is a nice library called reflect-metadata that allows decorators to extract metadata from TypeScript. This is supported by the vue-property-decorator library we are already using for our vue-class-components. The resulting code would then look just like this:
@Prop
myProp!: string;

The feature that reflect-metadata provides is already discussed to be supported natively.
This makes all properties type-safe per default and saves the developer annoying code to write and maintain. I use it already privately and it works fine. :upside_down_face:
Acceptance criteria

Tasks

[ ]

Vue3 gets advanced typechecking on all properties ootb, and with it I think it's good to also ditch our classes for composition API documents, which will make these decorators not needed. I think we should go on that direction when we need to touch this.


fix: product page bottom bar not full width when side bar collapsed

product page bottom bar not full width when side bar collapsed
before

after

Thanks for this @wychoong I didn't see you did this PR until I did mine, the issue with this one (after I tried w-full) was that the bar goes over the menu, also it needed some tweaks to other views. Please see #805


unix: Include fdatasync(2) on non-Apple systems

The function is defined in POSIX [0], but according to Gnulib docs [1],
it is missing or not declared on at least some versions of OS X. On
Solaris, it is not a system call but is present as fdatasync(3) [2].
[0] http://www.opengroup.org/onlinepubs/9699919799/functions/fdatasync.html
[1] https://www.gnu.org/software/gnulib/manual/html_node/fdatasync.html
[2] http://docs.oracle.com/cd/E36784_01/html/E36874/fdatasync-3c.html

Looks like this may not exist on FreeBSD?

Urgh sorry, I was sure I'd checked.
I need to figure out how to run these tests locally!

I think the windows failure is spurious. The failing job has no log: https://ci.appveyor.com/project/alexcrichton/libc/build/1.0.762/job/q46jx47ua7exb5ec


Boundary Provider is outdated

Thank you for reporting an issue.
The boundary provider has not been updated since 2023-09-19 and is on version 1.1.9 instead of the current version 1.2.0
OpenTofu Version
OpenTofu v1.8.6
on linux_amd64

OpenTofu Configuration Files
// Snippet of HCL that can be used to help reproduce this problem

Looks like the windows build is busted: https://github.com/opentofu/terraform-provider-boundary/actions/runs/12139635535/job/33847716801

More specifically, it does not provide windows arm packages for plugins/kms/assets:
https://github.com/opentofu/terraform-provider-boundary/tree/main/plugins/kms/assets/windows

Should be resolved @devlsc, thanks for the heads up!


Create docker-compose that will enable the KIC Integrated app, AMQ-Streams, MySQL and Postgres to be started within it.

Completed


firewall: NAT rule logging improvements

Important notices
Our forum is located at https://forum.opnsense.org , please consider joining discussions there in stead of using GitHub for these matters.
Before you ask a new question, we ask you kindly to acknowledge the following:

[YES] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[YES] I have searched the existing issues and I am convinced that mine is new.

Hello,
I tried asking my question on the forum, but nobody knows the answer.
https://forum.opnsense.org/index.php?topic=23192.0
Im happy to either continue on the forum or here depending on your preference, but I dont know how to get this information from the logs.
Please let me know your preferred method to proceed and I will do my best to accommodate as you require :)
I believe this information should be exposed because it has security implications, being able to monitor what external addresses internal IP's are accessing.
Looking forward to your insight :) Hope you are having a good day so far :)
Kind regards
Peter

Hi,
If you need any further info please let me know :)
Kind regards
Pete

Additional information from KeyHand here:
https://forum.opnsense.org/index.php?topic=23192.msg112811#msg112811

Hi Peter,
This is a fun one. ;)
When using port forwards and using Filter rule association "pass" with logging enabled will pop up the traffic in the firewall log:

The problem here is as described a limitation of the filterlog output. However, a state is being created for this redirect rule:

And you can see the NAT origin...
There are two TODO's here:

Try to emulate this with an associated filter pass rule (logging enabled correctly? I couldn't tell from first test as it wasn't working).

Tie states listing closer to port forward rules. One of the issues is that rdr/nat/binat rules do not support labels as far as I understand so tracking is more difficult. We also do not dump the state ID in the filterlog. ;(

Cheers,
Franco

Hello Franco,
Thank you for your reply.
I tried to follow your screenshots but I do not have a "Firewall:Diagnostics:States" page. I only have States dump, States reset, or States summary. This page you have accessed I cannot find.
In addition, if you would like me to check anything please let me know and I will do so :)
Kind regards,
Pete

Hi Pete,
The page I showed is from the upcoming 21.7 release. It sort of replaces the states dump page, although the NAT information is on that older page as well.
With an associated pass rule, using inspect on the development version allows to directly fetch the associated states. Though the logging is incorrect IMO as rdr is no longer logged (not the final action I suppose):

Cheers,
Franco

Hi Pete,
With https://github.com/opnsense/src/commit/bdb244c37d and a separate firewall pass rule it looks like this now:

I suppose seeing NAT log pre-NAT and firewall rule post-NAT is the desired result? :)
Cheers,
Franco

Hi Franco,
This is very interesting. how did you manage to achieve this result?
I do not use the dev version... is there any way I can test this to check what happens my side? It looks like it is showing both the original destination and the destination after the rewrite occurs in your screenshot which is excellent.
Kind regards
Peter

The snapshot kernel to try is:
# opnsense-update -zkr 21.7.r1_1
# opnsense-shell reboot

Cheers,
Franco

Hi Franco,
Thank you for your reply. Apologies for bothering you further but I was not able to complete this. This is the output:
Enter an option: 8
root@OPNsense:~ # opnsense-update -zkr 21.7.r1_1
Fetching kernel-21.7.r1_1-amd64.txz: .. failed, no signature found
root@OPNsense:~ #
Kind regards
Peter

Hi Pete,
Which mirror are you using? The default mirror should be good. The file was only published today.
Cheers,
Franco

Apologies again. It must be something my side. I cannot get it to work.
My settings are:
Mirror: Default
Flavour: Libressl
Type: Community.
Could it be because I am using libressl (not a default setting).
Sorry I feel bad wasting your time. This is most likely due to my specific config its not working so apologies again in advance.
Kind regards
Pete

Sorry, my fault... it's actually:
# opnsense-update -kr 21.7.r_1

Sorry, my fault... it's actually:
# opnsense-update -kr 21.7.r_1

No problem, actually it was opnsense-update -zkr 21.7.r_1 but I managed to guess that myself so it has installed. I will test and come back to you in a little while :)

I can confirm that the new patch indeed fixes it - see below:

All info is now exposed as requested in the OP.
Thank you very much for this. Can I ask how you managed to add this functionality into OpnSense? It seems like it would have been a nightmare to add.
Kind regards,
Peter

Hi Peter,
It was a mix of reading a bit of source code and remembering that logging already worked somehow. Glad we could put the pieces together.
This will likely end up in OPNsense 21.7, but not the RC1 to be released next week.
To keep the code in place lock "kernel" package from the firmware packages tab.
Close then? :)
Cheers,
Franco

Yes please. Thank you for your time. It is appreciated.
Kind regards
Peter.


Enable index.html on GCS so repository status is readable

This already works on preprod (https://sigstore.github.io/root-signing/) but the GCS bucket does not have "main page" set yet

first part is here: https://github.com/sigstore/root-signing/issues/1358
(this scaffolding still needs to be used in the environments before this is fixed)

https://tuf-repo-cdn.sigstore.dev/ works now - without styling but still #1360


structuralcodes - Repository examples

This draft pull request has been linked to the main repository to work on the examples 👍 . This pull request is not intended to be merged with the dev branch; it is solely for notifications and tracking purposes.
Contributors
@MestreCarlos : Main contributor, working on examples proposed by @aperezcaldentey .
@DanielGMorenaFhecor : Reviewer, providing suggestions to improve the repository's usability from an end-user perspective.
Initial Plan
We initially planned to create a separate repository for these examples and use pip install git+[...] to install the dev branch. However, this was not possible due to the missing setup.py file (correct me if I am wrong). Although adding the repo as a submodule was considered, we decided to continue working in the same repository. We will migrate to a different repository when the first version is released.
Next Steps and Contributions

Develop More Examples: We have created some examples, but additional examples are welcome. These can be based on our experience, meetings with fib-TG10.3, or basic getting started examples. A bullet list of current examples will be posted in the comments with the current developed ones—please feel free to suggest more.

Improving Usability: @MestreCarlos and I have been discussing how to enhance the repository's usability from an end-user perspective. Notes from our discussions will be posted in the comments. Your feedback and contributions are welcome.

Feel free to comment, add, or discard any suggestions provided.

Current state of the examples

[X] Instant and long-term deflections in a concrete beam (EC2-2004)
[X] Crack width computation in a concrete beam (EC2-2004)
[X] Shear calculations in a concrete beam (EC2-2004)
[ ] Longitudinal shear reinforcement sizing (EC2-2004)
[ ] Sizing of slender concrete elements (EC2-2004)
[ ] Feel free to add..

Usability Suggestions and Issues Detected
During the development of the examples, @MestreCarlos and I noticed some issues and approaches to improve usability.
Feel free to add, comment, discard, or ask for clarification:

[X] The abstract signature of the constitutive law is get_tangent(self, eps: float) -> float: but all implementations are get_tangent(self, eps: ArrayLike) -> ArrayLike: The same applies to get_stress. Consider changing the abstract class signature for clarity.
[ ] We cannot access the properties of the materials in an instance of a GenericSection. Could we create an attribute for storing the material(s) and not just the constitutive laws?
[ ] As creating rectangular reinforced concrete sections is a common task, it would be convenient to have a utility method and your _._add_._ operator to create something like this: section.rectangular(b, h, mat) + steel_reinf(…) + steel_reinf(…) + …
[ ] When using the set_design_code method to configure my global code standard, I incorrectly passed ‘ec2_2024’, and the rest of the code was not working because this method uses get to get the standard from the dictionary, but None was set. It would be useful to raise a warning or an error if the code does not exist.
[ ] We missed a calculate_cracking_moment method in the section class, so we had to implement it outside for the sake of the example.
[ ] In one example, we needed to compute the elastic modulus taking into consideration the creep coefficient phi. We needed to extract this computation from the ConcreteEC2_2004. How are we finally going to deal with this time-dependency in the concrete classes?
[ ] In the GrossProperties attributes from the GenericSection class, we can obtain the reinforcement area, but what about the possibility of querying these areas by the position of the reinforcement or by the diameter used? This may also apply to other properties inside the GrossProperties class.
[ ] There is no possibility of computing the inertia of a homogenized cross section. In this case, we have used a "concrete reinforcement" with the steel areas multiplied by Es/Ec.
[ ] It would be useful to add new methods to the Section classes. In this case, we needed to compute the crack width in a concrete section, so wrapping all the calculations behind section.wk(M,…) would be very convenient. Of course, this implementation depends on the material of the cross section and the structural code to be used, so whether to use inheritance or conditional checking inside the method is to be discussed.
[ ] Feel free to add more suggestions…

Also, @MestreCarlos has developed some methods that were needed to compute the results. These functions would be helpful to include them at some point in the package (as utility classes or new methods in the current classes is to be discussed). These functions are:

def calculate_strain_profile_batch(sec: GenericSection, n_ed, my_ed) : Get the moment curvature diagram. Then interpolate to get curvature for my_d
def calculate_strain_profile(section: GenericSection, n_ed=0, m_ed=0): Get the stress in a given point (y,z) inside the cross section.
def calculate_cracking_moment(section: GenericSection, n=0, plot=False): Calculate the cracking moment of a R.C section in N*mm.
def calculate_width_at_z(geometry: CompoundGeometry | GenericSection, z): Calculate the width of a section or a section part at a certain level of z
def effective_depth(section: GenericSection, neg_bending: bool = False): Calculate the width of a section or a section part at a certain level of z.


HDDS-7575. Correct showing of RATIS-THREE icon in Recon UI

What changes were proposed in this pull request?
This bug in introduced in HDDS-6308, which updates the type of "replicationFactor" from "number" to "string".
This ticket is to fix this issue.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-7575
How was this patch tested?

Thanks @symious for the fix.

@kaijchen Thanks for the review.


[Event Request] Table 5093 "Opportunity Entry".FinishWizard

Describe the request
Please remove scope OnPrem for function FinishWizard. We do not see reason why it should be only for onprem.
[Scope('OnPrem')]
  procedure FinishWizard()
  var
      OppEntry: Record "Opportunity Entry";
  begin
      UpdateEstimates();
      OppEntry := Rec;
      InsertEntry(OppEntry, "Cancel Old To Do", false);
      OnFinishWizardOnAfterInsertEntry(OppEntry);
      Delete();
  end;

Additional context
We do not see reason why it should be only for onprem.
Internal work item: AB#561117

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


Add Pentanomial LLR and use nelo bounds for SPRT

Overloaded the LLR function to provide pentanomial LLR when called with pentanomial results. This allows for pentanomial SPRT's. Also made the elo0 and elo1 bounds for SPRT use normalized elo instead of logistic elo to be consistent with Fishtest and Openbench.

gonna trust you on the maths on this one :D Probably in the future the llr should just take a Stats object https://github.com/Disservin/fast-chess/blob/master/src/types/stats.hpp.
Btw did fishtest have any tests associated with these functions, would make sense to add them.

for the penta llr i didn't take them from fishtest instead i used my own 5-nomial distribution code combined with the cpw llr formula that i used on my python elo and SPRT simulator here:
pentanomial_elo_model.txt
the results are exactly the same as the fishtest one tho :)


yugatool: Added report header [43]

Added "Reportinfo" header to tablet report .
This includes rn-date, hostname, and yb tools version + Build date.
tablet_report_parser.pl updated to parse this new info.

LGTM


render nodes and links using bfs

I'm curious about this one. What would be the advantage of rendering with a BFS strategy? We still need to render all the nodes, there's no apparent performance gain on doing so right. Unless you're aiming to have the nodes in the DOM in a different order for whatever purpose I can't see the benefits of the BFS render. @callmedhh

I'm curious about this one. What would be the advantage of rendering with a BFS strategy? We still need to render all the nodes, there's no apparent performance gain on doing so right. Unless you're aiming to have the nodes in the DOM in a different order for whatever purpose I can't see the benefits of the BFS render. @callmedhh

Hi, this is for the Accessibility requirement of our product. We want to focus on the node and link in the order of bfs. But eventually, we think it is not good to update these code in a public library.


Initial OrderOutput review

@rezarokni  while looking at the OrderOutput I thought I'd split it into multiple methods, so that the logic is easier to follow. Other changes here are mostly minor checkstyle and similar fixes.
Do you think this refactor makes sense?


Movies Example not working

Description

Clone and run Example/Movies/Movies.xcodeproj
Movie API responds with no data, the JS context crashes and error screen appears.

Is API token still valid?
I can submit a PR for the JS crash.
Additional Information

React Native version: master (fea874584)
Platform:iOS
Operating System: macOS Sierra 10.12.3

Sure feel free to send a PR to fix it, we don't run that example often so it is likely it is broken :)

The movies sample has been removed from the core RN repo. Feel free to publish standalone example apps, and we can curate a list of them for the website.


Odd Errors in Log

I am seeing weird errors in the logs about the Cloudwatch regarding timestamps of the metrics. The only metrics currently running are from https://github.com/aws-robotics/health-metrics-collector-ros1.
The error is:
[ WARN] [1593088848.837626459,<PHONE_NUMBER>00]: [AWSErrorMarshaller] Encountered AWSError 'InvalidParameterValue': The
parameter MetricData.member.1.Timestamp must specify a time within the past two weeks.
The parameter MetricData.member.2.Timestamp must specify a time within the past two weeks.
The parameter MetricData.member.3.Timestamp must specify a time within the past two weeks.
The parameter MetricData.member.4.Timestamp must specify a time within the past two weeks.
The parameter MetricData.member.5.Timestamp must specify a time within the past two weeks.
The parameter MetricData.member.6.Timestamp must specify a time within the past two weeks.
[ERROR] [1593088848.837759364,<PHONE_NUMBER>00]: [AWSClient] HTTP response code: 400
Exception name: InvalidParameterValue
Error message: The parameter MetricData.member.1.Timestamp must specify a time within the past two weeks.
The parameter MetricData.member.2.Timestamp must specify a time within the past two weeks.
The parameter MetricData.member.3.Timestamp must specify a time within the past two weeks.
The parameter MetricData.member.4.Timestamp must specify a time within the past two weeks.
The parameter MetricData.member.5.Timestamp must specify a time within the past two weeks.
The parameter MetricData.member.6.Timestamp must specify a time within the past two weeks.
5 response headers:
connection : close
content-length : 804
content-type : text/xml
date : Thu, 25 Jun 2020 12:40:48 GMT
x-amzn-requestid : 71391052-b267-4f7e-ac62-138315b23fa4
[ WARN] [1593088848.837841133,<PHONE_NUMBER>00]: [AWSClient] If the signature check failed. This could be because of a $ime skew. Attempting to adjust the signer.

Here is a single metric from the metrics topic. The time_stamp is live and current and not skewed at all.
 -
    header:
      seq: 0
      stamp:
        secs:<PHONE_NUMBER>
        nsecs: 394534588
      frame_id: ''
    metric_name: "cpu_usage_core_2"
    unit: "percent"
    value: 90.9923629761
    time_stamp:
      secs:<PHONE_NUMBER>
      nsecs: 394534588
    dimensions:
      -
        name: "robot_id"
        value: "4a54bac8-efb7-47a4-9ee5-493d928ae446"
      -
        name: "category"
        value: "RobotHealth"

Another odd behavior is we do get metrics in CW

Running version: Version: 2.2.1-1xenial-20200330-153748+0000

As an aside I do think the node is storing the metrics since from the node perspective the call has failed. After running for several minutes with a publish_frequency of 60s we'll get the above error message 10 or 20 times spamming our logs.

Also a related error in other RoboMaker ROS node that is seems to be related to time if it helps. https://github.com/aws-robotics/cloudwatchlogs-ros1/issues/61

Hi @mr337,
Thanks for filing this behavior. If possible could you please share any more logs? I'm wondering if your system experienced intermittent network connectivity issues, so metric data was stored on disk. It's then possible that this data on disk was attempted to be uploaded, even if stale. You could verify if these logs exist by checking the folder ~/.ros/cwmetrics/.

Wow, I def got some logs in there. As you can probably tell it has been an ongoing issue :)
$ ls ~/.ros/cwmetrics
cwmetric2020-04-16_23-46-01-0.log  cwmetric2020-05-12_23-31-40-0.log  cwmetric2020-06-25_07-21-28-0.log
cwmetric2020-05-12_22-33-25-0.log  cwmetric2020-05-12_23-38-10-0.log  cwmetric2020-06-25_08-33-11-0.log
cwmetric2020-05-12_22-34-42-0.log  cwmetric2020-05-13_00-00-54-0.log  cwmetric2020-06-25_08-41-16-0.log
cwmetric2020-05-12_22-37-03-0.log  cwmetric2020-05-14_22-13-05-0.log  cwmetric2020-06-25_08-42-32-0.log
cwmetric2020-05-12_22-40-28-0.log  cwmetric2020-06-07_05-56-07-0.log  token_store.info
cwmetric2020-05-12_22-48-51-0.log  cwmetric2020-06-17_20-04-32-0.log
cwmetric2020-05-12_23-26-03-0.log  cwmetric2020-06-23_08-29-05-0.log

So I'm guessing I'll need to dump those are CW won't accept metrics that old. Our machines are intermittent so they may be ran everyday for weeks and then parked idle for a couple of months etc. I'm guessing the way moving forward is on startup purge these logs on boot older than two weeks?
Does that sounds reasonable?

Yes, to workaround I would do what you have proposed, i.e., clearing out stale logs that were never uploaded.

Awesome and ty for the prompt response.


[ASK] problems in test

Description
When adding test files in model.fit(), the evaluation results are the same between validate file and testing file. Is it possible that there is a problem in initing behaviors?
Other Comments

can you provide more detail on where this happens / which model is affected?

I think he is talking about this result. I have the same problem.

I think #192 has similar problems. And after look into my prediction.txt file(generated by the code below). I think its because the model.run_eval() seemed considered valid_news_file and valid_behaviors_file as test_news_file and test_behaviors_file. So the prediction.txt is actually the result of model.run_eval(valid_news_file, valid_behaviors_file).
But I don't know why.
group_impr_indexes, group_labels, group_preds = model.run_fast_eval(test_news_file, test_behaviors_file) with open(os.path.join(data_path+'/nrms', 'prediction.txt'), 'w') as f:     for impr_index, preds in tqdm(zip(group_impr_indexes, group_preds)):         impr_index += 1         pred_rank = (np.argsort(np.argsort(preds)[::-1]) + 1).tolist()         pred_rank = '[' + ','.join([str(i) for i in pred_rank]) + ']'         f.write(' '.join([str(impr_index), pred_rank])+ '\n')

Closing since there hasn't been interaction for a while


Plugin throwing errors with L530

This one happens occasionally and it seems to be related to not getting bulb status although there are no outages, sometimes it happens 10x in a row:
[30/08/2021, 19:28:11] [Tapo Smart Platform] 371 Error: Request failed with status code 429
This happened when I clicked "no response" in apple home app and then bulbs turned off (they were on before with no response status) after this status was updated and above error disappeared.
[30/08/2021, 19:28:14] [Tapo Smart Platform] 364 Error Code: -1301, undefined

This error occurs when the plugin gets an error response from the bulb, when getting the device info. This could be due to network issues. If you have the Home app open and the bulb does not respond this error may come up often as the Home app tries to get the status of the bulb in intervals.


Add awesome-repo automagically

As mentioned here: https://github.com/osmosis-labs/osmosis/pull/781

This is done, we have issue #7  to track improvements to awesome repo.


Summary page throws "KeyError: 'calories'" after migration to 0.24

After migration to 0.24.1everything seem working except  http://localhost:5000/summary/ which shows a blank page and the following message in the terminal:
[2024-07-28 09:40:09,394] ERROR in app: Exception on /summary/ [GET]
Traceback (most recent call last):
  File "/home/user/.local/pipx/venvs/geo-activity-playground/lib/python3.12/site-packages/pandas/core/indexes/base.py", line 3805, in get_loc
    return self._engine.get_loc(casted_key)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "index.pyx", line 167, in pandas._libs.index.IndexEngine.get_loc
  File "index.pyx", line 196, in pandas._libs.index.IndexEngine.get_loc
  File "pandas/_libs/hashtable_class_helper.pxi", line 7081, in pandas._libs.hashtable.PyObjectHashTable.get_item
  File "pandas/_libs/hashtable_class_helper.pxi", line 7089, in pandas._libs.hashtable.PyObjectHashTable.get_item
KeyError: 'calories'

I suspect this due to the fact that I have calories nowhere in ma activities.

This error happens when metadata["calories"] and/or metadata["steps"] never get assigned a value. When I set both to 0 by default in core/activity_parsers.py::read_activity the summary page displays well.

I think I what the issue is, I've set up a fix for 0.24.2.

The same problem also appears while generating the sharepics on the activity pages.
https://github.com/martin-ueding/geo-activity-playground/blob/f893407be0fb33f5d006471f6c6ad750e5d13474/geo_activity_playground/webui/activity/controller.py#L457
This line is where it fails for me. Summary page works fine for me after the release of 0.24.2.

Oh yes, I see the issue. I've fixed it and will upload it with the next release.


RFC: TypeScript plugin

The TypeScript plugin now has a preliminary implementation here with:

ts-loader
fork-ts-checker-webpack-plugin
tslint

TODOs

[x] Make the npm run lint script work with *.vue files
[x] Ensure compatibility with other plugins (PWA and test plugins)
[x] Offer options to use TS alongside Babel

Trying it Out
npm install -g @vue/cli
vue create ts-project
# select manual mode, pick TypeScript

For background on how plugins work in the new vue-cli, see here
Feedback welcome!
/cc @DanielRosenwasser @ktsn @HerringtonDarkholme @octref @kaorun343 @Igogrek @prograhammer @Toilal

Hi,
great work ! I don't know if it the right place but here is my tests
npx @vue/cli create vue-ts-test

Vue CLI v3.0.0-alpha.5
? Please pick a preset: Manually select features
? Check the features needed for your project: TS, PWA, Router, Vuex, CSS Pre-processors, Linter, Unit, E2E
? Use class-style component syntax? Yes
? Use Babel alongside TypeScript for auto-detected polyfills? No
? Pick a CSS pre-processor (PostCSS, Autoprefixer and CSS Modules are supported by default): LESS
? Pick additional lint features:
? Pick a unit testing solution: Jest
? Pick a E2E testing solution: Cypress
? Where do you prefer placing config for Babel, PostCSS, ESLint, etc.? In dedicated config files
? Save this as a preset for future projects? No

If I run npm run serve it show errors like below but i can browse and hot reload works
ERROR in<EMAIL_ADDRESS>18:13 Duplicate identifier 'beforeEach'.
    16 |
    17 | declare var beforeAll: jest.Lifecycle;
  > 18 | declare var beforeEach: jest.Lifecycle;
       |             ^
    19 | declare var afterAll: jest.Lifecycle;
    20 | declare var afterEach: jest.Lifecycle;
    21 | declare var describe: jest.Describe;

̀npm run build fails

@franxois looks like a type conflict between Cypress and Jest. We will need explicit tsconfig.json inside test directories.

Hi, i just try with v3.0.0-alpha.6, it's ok now ! :)

@DanielRosenwasser I think we are more or less stable now, would love to get your feedback on this before we move to beta :)

I just gave a try to the new generator (alpha 7) with all options checked (including TypeScript). It runs smoothly and is zero-conf for opening the generated project in IntelliJ.
Class component option could be available without TypeScript too.
When disabling TypeScript, I have to configure the webpack configuration file in IntelliJ<EMAIL_ADDRESS>for @ import alias to be recognized, but then all is OK. I think custom configuration placed in vue.config.js won't be available to IntelliJ. Maybe the effective "merged" configuration could be written to a file so the effective configuration can be loaded by tools/editors ?
Thanks for the awesome work :+1:

@Toilal that webpack file exports the dynamically resolved config that includes your custom config as well ;)

Looks awesome!
Would it be possible to have a choice between TSLint and ESLint, even when in TypeScript mode?
I much much prefer working with ESLint even on my TypeScript Vue projects (better VSCode support, eslint-plugin-vue doesn't have a TS equivalent, etc.). Tried it both ways and I've found life to just be a lot easier with ESLint at the moment.
It's a relatively straightforward integration - if one wants TypeScript support along with ESLint rather than TSLint, it means adding the typescript-eslint-parser and eslint-plugin-typescript deps, then taking eslintOptions.js from cli-plugin-eslint and changing a few options:
  extensions: ['.js', ''.ts', .vue'],
  parserOptions: {
    parser: require.resolve('typescript-eslint-parser'),
    sourceType: 'module',
  },
  plugins: ['typescript'],

Also adding the ts extension to the webpack eslint-loader test in cli-plugin-eslint, but all else should be essentially untouched.

@dkulchenko cool, I actually didn't know you can use ESLint with TypeScript before. I think that's indeed a better setup than TSLint. Will investigate in the next release.

@yyx990803 I will try to stress test it soon!
I think one thing that would be super high-value would be a lint rule to warn Vue+TypeScript users about computed properties, where all methods and get/set accessors need to have explicit type annotations to avoid inference problems with TypeScript (https://github.com/vuejs/vue/issues/7394). Whatever linter we end up choosing, we should factor that into the starter.

@DanielRosenwasser it's possible to use either ESLint or TSLint, but I assume the implementation of the rule would be similar. I think in the long run we'd like to standardize around ESLint because that allows linting of templates inside SFCs, and the rule you proposed could be placed in https://github.com/vuejs/vue-cli/tree/dev/packages/%40vue/eslint-config-typescript
/cc @mysticatea @michalsnik

Cool.
In fact, the combination of vue-eslint-parser and typescript-eslint-parser needs more work a bit. It needs that typescript-eslint-parser supports parseResult.visitorKeys.
Currently, I'm busy on acorn and eslint to support ES2018, but I will work on it after done.

@dkulchenko @yyx990803 How would ESLint plugins support rules that use the type checker?

@prograhammer AFAIK, no. With the current setup, type checking is performed by fork-ts-checker-webpack-plugin in a separate thread, and we don't even enable type checker depending rules when using TSLint.

Ah, ok. Now I'm wondering why you wouldn't enable tslint in fork-ts-checker-webpack-plugin, but it looks like you need the ability to tslint fix files or run tslint separately from fork-ts-checker-webpack-plugin?

@prograhammer actually, when using lintOnSave: true, tslint is done via fork-ts-checker-webpack-plugin, and I think that does work with type-checker-dependent rules.

Hey @yyx990803, since you already have support for TSLint, is there a specific place we should place the rule? I know that the respective ESLint rule should probably go in https://github.com/vuejs/eslint-plugin-vue

@DanielRosenwasser currently TSLint is handled inside the TypeScript plugin itself and we are just using tslint:recommended. We don't really have a TSLint config at the moment. Maybe put it as a custom rule in a rulesDirectory for now?

@yyx990803 @DanielRosenwasser
I personally use tslint-config-standard, which requires the type-checker for some rules.

Could you please add typescript support to "vue serve MyComponent.vue" maybe with a parameter "vue serve -ts MyComponent.vue"

I also love vue serve -ts to be implemented because when I work with medium-large project that use typescript everywhere, it consume a lot of RAM 😂

I've just tried the typescript template and everything works perfect so far, except for one thing... How do I use typescript in the service worker file? I use this setting in the vue.config.js file to include the worker:
module.exports = {
pwa: {
workboxPluginMode: 'InjectManifest',
workboxOptions: {
swSrc: 'src/sw.js',
},
},
};
I would like to replace the sw.js file with a sw.ts file, but Workbox doesn't seem to allow that. I have a lot of code inside the service worker that needs to be written in typescript...
If this is the wrong forum for this question, please redirect me :-)


Test SMTP setting

Really need a SEND TEST EMAIL after adding / updating SMTP settings

Closing - no doc referenced - feature requests / suggestions are better placed in the forums


Sites cookies didn't persist after quitting the application.

System Details

OS: MacOs 14.0 (Sonoma)
Thorium Version : 116.0.5845.169

Problem
Sites cookies didn't persist after quitting the application.
It's a huge problem for some sites who uses Token based authentication. I've experience some sites that Logged in session didn't persist after quitting the application.
Additional Notes
I'm a web developer and my sites also not works fine because of cookie automatically clear after quit the browser.

Not a browser related issue! 😛