Feature/issue 1282 cpplint

Summary:
Reducing cpplint warnings from:

src/stan/common
src/stan/command
src/stan/io
src/stan/mcmc

Intended Effect:
Reduces cpplint warnings from parts of the code that haven't been changed for a while.
This should have no effect on the code. Most of it changes white space.
How to Verify:
See the code diff with the flag to ignore whitespace.
Side Effects:
Single argument constructors have been marked as explicit: http://google-styleguide.googlecode.com/svn/trunk/cppguide.html#Explicit_Constructors
This should have no effect in our code base.
Documentation:
None necessary.
Reviewer Suggestions:
Anyone.

Here's the link to see the diff ignoring whitespace:
https://github.com/stan-dev/stan/pull/1285/files?w=1
Most of the remaining changes are to keep lines under 80 columns long.

This one removes 2486 warnings, but adds 5. I just walked through it again and these changes are mostly whitespace and reordering of include files.

Stop checked -- looks good.  :+1:


Update documentation of configuration of dynamic provisioning

Add/update docs according to current code scheduled for Kubernetes 1.5

This change is

Tech changes LGTM.
If these changes are only for 1.5, then they should go in the release-1.5 branch first (once it is cut), and then be cherry-picked back to master.
CC @devin-donnelly

The changes are for kubernetes >= 1.5, I hope it won't be changed again in 1.6.

Please rebase this PR against the 1.5 release branch.

rebased to release-1.5

removing do-not-merge,I want it in 1.5

/lgtm


chore: bump gateway-api to 1.32.3

Issue
https://github.com/gravitee-io/issues/issues/7930
Description
Bump version of gateway-api to take benefits from fixes on headers (see issue)

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 1.1.2-issues-7930-fix-es-headers-reporting-3-SNAPSHOT
download it from Artifactory here

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

1.1.2
GitHub release

Your semantic-release bot :package::rocket:


Use Array.Empty

This PR replaces some new string[0] with Array.Empty<string>() for better memory management.

Closed, because those changes are in PR #48


Type issue after latest version

after updating to the latest version 6.14.0 (I was using 6.12.0), all request and response types are any

Hi, seems like this bug was caused by Typescript not being able to do a union of UserRouteHandler and MIddlewareHandler in the spreadable arguments.
A fix for this bug has been pushed in the new v6.14.1 version.


Make it possible to retain published MQTT messages

This is useful for Home Assistant users who use a long update interval (ie. a couple of minutes), allowing the tags to appear ~immediately after restarting Home Assistant. However this will also prevent automatically un-discovering tags if they are ever removed, requiring manually deleting the retained messages in such case. This should be configurable, and default to the current behavior of not using retained messages.

I just hard coded this feature in my fork test branch.


DCOS-14456: Write more thorough tests for sidebar

This PR introduces more thorough integration tests for the Sidebar component.
Checklist

[x] Did you add a JIRA issue in a commit message or as part of the branch name?
[ ] Did you add new unit tests?
[x] Did you add new integration tests?
[ ] If this is a regression, did you write a test to catch this in the future?

Can one of the admins verify this patch?

Yay!!


[5.5] Report unnecessary availability warnings independently from the deployment target

Cherry-pick of https://github.com/apple/swift/pull/37350
This change separates emission of the diagnostics like:
unnecessary check for 'Platform'; enclosing scope ensures guard will always be true

from the deployment target of the current compilation. Instead, these diagnostics will only be emitted if the enclosing scope guard is explicitly specified by the user with an #availability attribute.
This fixes cases like the following:
@available(macOS 11.0, *)
class Foo {
    func foo() {
        if #available(macOS 11.1, *) {}
    }
}

Compiling this with -target x86_64-apple-macos11.2 results in:
warning: unnecessary check for 'macOS'; enclosing scope ensures guard will always be true
        if #available(macOS 11.1, *) {}
.../test.swift:2:7: note: enclosing scope here
class Foo {

Even though in source-code the enclosing scope (Foo) of this guard does not ensure it will always be true.
This happens because availability range is propagated by intersecting ranges top-down from the root TypeRefinementContext, which is defined by the deployment target, causing the availability range on class Foo to become 11.2.
Users may be sharing the same piece of source-code across different projects with their own respective deployment targets which makes such target-dependent warnings confusing at some times, and not-useful at others.
We should rather have the warning simply reflect what is in the source.
Resolves rdar://77607488

@swift-ci please test


[IK-20] Adds a database backup get task.

This PR adds a utility task to allow a database backup on sites that have backups configured using the caktus-hosting backups.
This changes internal behavior of get_ansible_vars and renames it to print_ansible_vars, but other than that the process is fairly straightforward.
NOTE: The extraction of filenames is tied fairly tightly to filename definitions found in caktus-hosting, so this could cause problems when/if changes are made to caktus-hosting.
closes #20

I've been thinking about this a bit today. Some discoveries:

Since caktus-website doesn't have a cluster.yml, I don't think this would work as-is on that project
Also, this assumes cluster.yaml, but many of our projects use .yml, so we should probably at least support both options.

Are you all up for a quick cross-team brainstorm @JeremyGibson @vkurup ?


Implement an option to prevent feature generation on time index column for time series problems

If a user has previously used Featuretools to generate feature values for a time series problem, including features created from the time index column (year, month, day, etc), EvalML should provide a mechanism to prevent additional datetime features from being generated by the DatetimeFeaturizer component.
Since the time index is required as part of the data input, if EvalML uses this time index to create new features, there can be duplication of features, with the some of the same features generated by both Featuretools and EvalML. There should be some mechanism for users to instruct EvalML to skip generating new features on datetime columns in this scenario.

@chukarsten @jeremyliweishih How large of a lift would this be? Would it be possible to get it in next sprint?
@asniyaz FYI


Intending to fork & update; link to fork in README?

Howdy 👋
We (Pelotech) have recently started using Nidhogg. Our use-case is to manage taints to control pod scheduling while using Multus (along with other CNI plugins). We've encountered an issue or two related to outdated APIs (resulting in noisy warnings in logs), and have found some flakiness (seems to be due to an issue with the logic used to detect DaemonSet readiness). We also have thoughts about updating the config approach (to eliminate the ConfigMap).
From the unanswered issues and time since last commit, it seems like this project is more-or-less done/complete (and/or abandoned). Our intention is to update the code to current idiomatic Golang (e.g., Go modules, etc), to update the dependencies (esp. Kubernetes client), and update the readiness check.
In addition, we plan to update the API to remove everything related to NodeSelector and DaemonSet name, and to move that functionality into annotations/labels on the relevant DaemonSet. This approach would move all scheduling logic to the monitored DaemonSet, as well as which taint is related to which DaemonSet (instead of the current fixed taint naming: nidhogg.uswitch.com/$DS_NAMESPACE.$DS_NAME). This change, in particular, will be a major breaking, API change. In our view it will increase the flexibility and generality of Nidhogg.
If in fact USwitch is not continuing development of Nidhogg, once we've released an updated version, we'd be glad if you were willing to point to the new version in the README here. There are many places that link to uswitch/nidhogg and it would be ideal to ease discovery of a new iteration.
Will you accept a PR to direct future users to an updated and actively maintained fork?

As a Nidhogg user that would like to see some changes (namely, and ARM version) I would support a forked version of this repo.

@emmanuel If you do a fork, can you post it as a comment here? I would be happy to contribute. I'm still waiting for this feature :-P https://github.com/uswitch/nidhogg/issues/20

@giorgia-amici awesome, thanks for confirming.
@SQUIDwarrior — no promises on timelines, but we (Pelotech) do plan to take on this fork. I'll comment here when we get things up and running (the build pipeline). I imagine adding ARM images will be pretty straightforward.

I just took a quick pass on starting the fork - https://github.com/pelotech/nidhogg
@SQUIDwarrior ghcr.io/pelotech/nidhogg:latest (pinned ghcr.io/pelotech/nidhogg:v0.5.0) - should have amd64 and arm64, as well as a few other updates we'd made in the last while.
@giorgia-amici Thanks a ton on confirming! - I had a quick question on if you all are using something else now for this problem space, or just didn't need it? Just wondering the history :) - also have any thoughts on if forking would be better vs transferring to keep PRs, Issues, existing forks? Either one works for us although transferring might make it cleaner.


Blazor DynamicComponent

Good morning,
I'm not sure your timeline in documenting the DynamicComponent released with .NET 6 Preview 1, but I can lend a hand if you'd like (I wrote about it just now and it seems to be straightforward).

We usually hold off a bit on new coverage because ...

PU churn in the past has caused problems: Before features settle into a close-to-final form, we end up having to revise docs (sometimes more than once) during the preview/RC phase. It's generally been less costly 💰 to wait a bit longer. Things don't change much at or after RC1 ... usually 🤞.
I've been very busy with UE passes, so it's just as well. If I had to sweat a lot of 6.0 coverage right now, it would have radically slowed down the UE passes, which are desperately needed imo.
Also, we haven't had major time crunches documenting a release when starting most of the coverage just before or at RC1's release. It's especially been the case because PU engineers provide a lot of the content, so I have material to edit and polish up for the coverage. I haven't had to draft a lot of content from scratch each release. We usually get ... er ... say 90% (or more) in place for the GA.

Yes ... AFAIK, you're welcome to provide the content. Let me get back to you later today on location for it. I'm ⛏⛰😅 right at the moment. I'll get back to u soon. 🏃

Still buried in work ... let me get back to you @daveabrock early next week. 🏃🏃🏃🏃🏃🏃😅

Appreciate the follow-up ... no rush on my end. Just putting it out there, and makes sense with the timing as it's still early. It can wait.

Ok ... I'm BACK. There are two ways to go ...

Section in the Components overview topic: It would have to be considerably shorter (text and example) than what's in your post. The example would probably roll both with and without params. It would probably be more bare bones, similar to what DR did in the blog post ... minimal example code ... quick explanation.
New topic: Could be long and written out similar to your post with the larger example and separate section for optional params. You can use your post text as the basis of the whole thing if you like.

I don't have a preference between those two options. I'll leave it up to you.
WRT sample code, I'll leave it up to you on whether or not it goes into the topic (triple backtick code blocks) or into the new snippet sample apps. I can always roll the code from the topic into those apps later, which would simplify what you need to do. I'll provide more guidance depending on your decision.
WRT metadata and whatnot, let me know which approach you prefer for coverage :point_up:. I'll provide more guidance based on your decision.

btw - I'm going to ping Artak and DR offline to ask about location for this. If they don't respond, we'll go with your preference.

We'll also get an answer on https://github.com/dotnet/aspnetcore/issues/31754 before proceeding here.

Personally, I would prefer the second approach. I've already got most of the content and I think the parameters section should help iron out some lingering questions.

Fine with me. I pinged them offline. Let's give them a few days to react. I'll get back to you .... errrrrrrrr 🤔 ... Friday ... probably 🤞.
It will be called DynamicComponent, so the doc text will appear as ".... DynamicComponent component ..." ("... `DynamicComponent` component ..."). Steve isn't keen on "Dynamic" alone (or a substitute word). I understand his reasoning for keeping it the way that it is. It's just good to confirm that they're happy with the naming before both framework GA and the doc content is created.
I'll put the rest of the nitbits on metadata and whatnot here on Friday.

Ok ....... I'm BACK! 🏃
Let's discuss further where needed. Here are my off-the-top-of-my-head 🧠 ideas ...

Physical location and filename: blazor/components/dynamic-component.md

ToC (toc.yml): Place it between Component virtualization and Templated components ...
- name: Dynamic component
  uid: blazor/components/dynamic-component

Metadata: I recommend that we try to avoid localization problems (i.e., having to code-fence things) as much as possible in the title and description ...
---
title: ASP.NET Core Blazor dynamic component rendering
author: daveabrock
description: Learn how to dynamically render components in ASP.NET Core Blazor apps.
monikerRange: '>= aspnetcore-6.0'
ms.author: riande
ms.custom: mvc
ms.date: 04/16/2021
no-loc: [appsettings.json, "ASP.NET Core Identity", cookie, Cookie, Blazor, "Blazor Server", "Blazor WebAssembly", "Identity", "Let's Encrypt", Razor, SignalR]
uid: blazor/components/dynamic-component
---

If you want me to get the pings on it, put guardrex in as the author.

We won't be able to cross-link to the API docs until GA, so use inline code-fencing for now. The API is here ...
https://github.com/dotnet/aspnetcore/blob/main/src/Components/Components/src/DynamicComponent.cs
... and there are some tidbits in the API comments of interest.

They're going to go with DynamicComponent, but it's painful to see a noun repeated as it's own adjective. Yuck! 😄 ... but let's have your examples not use the word "Component" in their names. For example, use Rent (Shared/Rent.razor ... but I understand that you won't need to use the path/filename in the topic) over RentComponent and refer to it as "... the `Rent` component ..." ("... the Rent component ...") in the text. Otherwise, docs end up with the 🙈 phrasing "... the RentComponent component ..." for localization purposes (i.e., the word "component" should be in text and translated). I've been avoiding the word "Component" in component type names for a while now with success. :+1:

Because this is a reference doc, I recommend reducing the blog's introduction down to just the key points: What is it? What problem(s) does it solve?

WRT sample code, use code blocks in the doc. Although we might start building snippets for preview, I kind'a think that's a bit much right now to roll into this. I'll possibly circle around later after GA and update the topic by moving the sample code into the snippets apps. If I do that, I'll ping u on it.

WRT to images, we generally avoid them: They're too time-consuming to keep up with 🏃😅 and in light of possible Blazor style changes for UI shots. They aren't accessible for screen readers. I've had success in a few spots just showing the rendered HTML in code block. It makes the point well enough and is super easy to change when needed.

I think that's about it. Let me know if you have any ❓. Thanks again for helping with this, @daveabrock! 🎷

What, you don't want it to be called "Dynamically render components with the DynamicComponent component"?
This all sounds good. I imagine there's no rush on your end, as it's still early-ish preview days. I should be able to get to this in the next month or two (maaaybe three).

Yes ... unless DR/Artak ask for early coverage. In the meantime, I can always respond to a community ask with "Yo! Check out this killer blog post by Dave!"

@daveabrock  👌 Ok! Ready for this one. 👌
I think the notes that I provided above ☝ https://github.com/dotnet/AspNetCore.Docs/issues/22005#issuecomment-821130971 are good. Let me know if any of that seems off or if u have any ❓.
Confirm that the no-loc metadata is up-to-date ... that gets updated occasionally. Any topic on the repo will have the latest.
You can go ahead when ready. There's no giant rush ... we have several weeks.
Feel free to use as much of your blog content as you like. I like your example there.
BTW ... I've been thinking and working on hybrid reference-tutorial style topics and improving my approaches in general. The hybrid approach seems to be working well with readers.
I've adopted either of two approaches ...

The topic describes the objects, members, and approaches (the reference content) as it also offers the reader the option of dropping example code directly into a sample app on more of a per-section basis. This works best when there isn't a lot of demo code for the subject ... a single, short example component does the trick ... the reader click-copies from the doc into their local test app ... it runs ... it works ,.. they get it ... all good.

The other approach is for where there's a lengthy setup with several interacting parts or where the whole topic is describing the feature. The opening sections only have (generic) reference material on the framework aspects (C#, Razor, components, etc.) and then have a Complete example section that's like a mini-tutorial that the dev can run down step-by-step for a live experience. With this Complete example approach, the earlier reference content can make liberal use of placeholders ... like ......

The `@typeparam` directive blah blah blah. The following example blah blah blah.
```razor
@typeparam {TYPE}
```
The {TYPE} placeholder is the generic type parameter to apply to the component.

... and then the Complete example section would have a fully working example ... the type would be specified ... the locations of things are specified ...

The following example blah blah blah.
`Shared/TypeParamExample.razor`:
```razor
@typeparam TItem
...
```

I haven't thought too much about this particular subject on DynamicComponent. It kind'a looks like the initial part of your blog post is reference content ... and the end piece on Pass in parameters is also reference material (maybe). Those might be the opening reference sections with placeholders ({...}). There then might be a Complete example section with the rest. Anywho ... I'll yield to you to see what you want to do with it.

@daveabrock ... There's a big shakeup in Blazor docs going to version-by-files (groups) from whole-topic-versioning. Signal me here when you're ready to start working on this.
Alternatively if you won't have time to address this issue, I can take your blog content, turn it into a doc, and give you full credit. Let me know ... I'd try to work it up in a week or so ... maybe 🏃🏃🏃🏃🏃🏃🏃😅.

@daveabrock ... Did you still want to make a topic out of your blog post? ... or do you want to permit me to make a topic out of it and slap your name on it? The version-by-file setup is in place. We're still wringing the final bugs out of it, but it's 90% working. I can provide the easy guidance now for setting up the topic if you plan to do it. :ear:

Hey @guardrex - I apologize for the delay. I am incredibly swamped for the next month or so, so if you'd like it done by then I sadly won't be able to get to it by then, sorry. No issues with you making a topic out of my post, if you wish.

Great ... I'll take care of it. You can have the credit. I'll put you on there as author in text. Do you also want the the topic pings (as author in metadata)? If not, do you want to remain on the CSS isolation topic for pings ... you are currently author on that one?

Hey Rex, no issues on having the pings.

Ok ... I'll update that on the next commit.


Mutate table values?

Is it possible to load a toml file, edit a table value, and write the resulting data with the edit?
This is for the scenario where a component knows only the parts of the configuration it wants to edit; and the rest of the file should be preserved.
It looks to me like you can't find a table, modify a value.
And adding a new table of the same name basically destroys the old table (I tried it)

Forget it, I realized you can just do get_table(), and insert, and it will replace just that item :)


Responsiveness v2

closes #

fixes #15
What all changes are included in this PR?
I have reduced the margin of the header.

@devshiva619 Nice work on the margin but now it's not responsive.
This is what I see on my screen.


polybar doesn't display in i3wm, gentoo

Describe the issue
polybar doesn't display in X in gentoo amd64, i3-gaps and default config.
Expected behavior:
polybar would display
Actual behavior:
patrick96 also mentioned this seems similar to https://github.com/jaagr/polybar/issues/939
polybar doesn't display.  debugging with gdb it appears to be an xcb issue?:
renderer.cpp:83 cw_flush(true) is not returning in gdb
xcb_request_check(std::forward(c), cookie); seems to be returning an error object
{response_type = 0 '\000', error_code = 8 '\b', sequence = 85, resource_id = 383, minor_code = 0, major_code = 1 '\001', pad0 = 0 '\000', pad = {0, 0, 0, 0, 0}, full_sequence = 85}
Error code 8 seems to mean BadMatch from what I googled.
setting cw_flush(false) progresses further but nothing is displayed.
This branch is being taken: polybar/lib/xpp/include/xpp/proto/../generic/request.hpp:37
What's also interesting is I see my monitor disconnecting then reconnecting in /var/log/Xorg.0.log when I start polybar:
[  2061.192] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  2061.192] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[  2061.192] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[  2061.192] (--) NVIDIA(GPU-0):
[  2061.192] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  2061.192] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  2061.192] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  2061.192] (--) NVIDIA(GPU-0):
[  2061.192] (--) NVIDIA(GPU-0): LG Electronics LG Ultra HD (DFP-2): connected
[  2061.192] (--) NVIDIA(GPU-0): LG Electronics LG Ultra HD (DFP-2): Internal DisplayPort
[  2061.192] (--) NVIDIA(GPU-0): LG Electronics LG Ultra HD (DFP-2): 1440.0 MHz maximum pixel clock
[  2061.192] (--) NVIDIA(GPU-0):
[  2061.195] (--) NVIDIA(GPU-0): DFP-3: disconnected
[  2061.195] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[  2061.195] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[  2061.195] (--) NVIDIA(GPU-0):
[  2061.195] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  2061.195] (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
[  2061.195] (--) NVIDIA(GPU-0): DFP-4: 1440.0 MHz maximum pixel clock
[  2061.195] (--) NVIDIA(GPU-0):
[  2061.195] (--) NVIDIA(GPU-0): DFP-5: disconnected
[  2061.195] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[  2061.195] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[  2061.195] (--) NVIDIA(GPU-0):
[  2088.288] (--) NVIDIA(GPU-0): DFP-0: disconnected
[  2088.288] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[  2088.288] (--) NVIDIA(GPU-0): DFP-0: 165.0 MHz maximum pixel clock
[  2088.288] (--) NVIDIA(GPU-0):
[  2088.288] (--) NVIDIA(GPU-0): DFP-1: disconnected
[  2088.288] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[  2088.288] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[  2088.288] (--) NVIDIA(GPU-0):
[  2088.288] (--) NVIDIA(GPU-0): LG Electronics LG Ultra HD (DFP-2): connected
[  2088.288] (--) NVIDIA(GPU-0): LG Electronics LG Ultra HD (DFP-2): Internal DisplayPort
[  2088.288] (--) NVIDIA(GPU-0): LG Electronics LG Ultra HD (DFP-2): 1440.0 MHz maximum pixel clock
[  2088.288] (--) NVIDIA(GPU-0):
[  2088.291] (--) NVIDIA(GPU-0): DFP-3: disconnected
[  2088.291] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[  2088.291] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[  2088.291] (--) NVIDIA(GPU-0):
[  2088.291] (--) NVIDIA(GPU-0): DFP-4: disconnected
[  2088.291] (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
[  2088.291] (--) NVIDIA(GPU-0): DFP-4: 1440.0 MHz maximum pixel clock
[  2088.291] (--) NVIDIA(GPU-0):
[  2088.291] (--) NVIDIA(GPU-0): DFP-5: disconnected
[  2088.291] (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
[  2088.291] (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
[  2088.291] (--) NVIDIA(GPU-0):

To Reproduce
A minimal but complete config with which the problem occurs:
polybar 3.2.1 compiled from gentoo emerge.  Same thing happens with git version.
The example ini with battery and a few modules removed.

List any other steps needed to reproduce the issue besides starting polybar with the config you posted above.
Polybar Log
Post everything polybar outputs to the terminal when you run it and the issue occurs below
* Loading config: /home/uno/.config/polybar/config
- config: Copying missing params (sub="module/backlight-acpi", base="module/xbacklight")
- config: Current bar section: [bar/example]
* Loaded monitor DP-0 (3840x2160+0+0)
* Bar geometry: 3840x35+0+0
- bar: Attach X event sink
- bar: Attach signal receiver
- controller: Install signal handler
- controller: Setup user-defined modules
- module/powermenu: Creating menu level 0
- module/powermenu: Creating menu level item 0
- module/powermenu: Creating menu level item 1
- module/powermenu: Creating menu level 1
- module/powermenu: Creating menu level item 0
- module/powermenu: Creating menu level item 1
- module/powermenu: Creating menu level 2
- module/powermenu: Creating menu level item 0
- module/powermenu: Creating menu level item 1
* Starting application
- controller: Main thread id = 1
* Starting module/i3
* Starting module/filesystem
* Starting module/alsa
- module/i3: Thread id = 2
* Starting module/xkeyboard
- module/filesystem: Thread id = 3
* Starting module/memory
- module/alsa: Thread id = 4
- module/xkeyboard: Thread id = 5
* Starting module/cpu
* Starting module/temperature
- module/cpu: Thread id = 6
* Starting module/date
- module/temperature: Thread id = 7
* Starting module/powermenu
- module/memory: Thread id = 8
* Entering event loop (thread-id=1)
- module/date: Thread id = 9
- module/powermenu: Thread id = 10
* Eventqueue worker (thread-id=11)
- bar: Create renderer
- renderer: Get TrueColor visual
- renderer: Allocate colormap
- renderer: Allocate output window
# this is where cw_flush(true) is presumably failing

Screenshots
If applicable, add screenshots to help explain your problem.
Environment:

WM: i3-gaps
Output of polybar -vvv:

Features: +alsa -curl +i3 -mpd -network +pulseaudio +xkeyboard

X extensions: +randr (+monitors) -render -damage -sync -composite +xkb +xrm +xcursor

Build type: Gentoo
Compiler: /usr/bin/x86_64-pc-linux-gnu-g++
Compiler flags: -march=native -pipe -Wall -Wextra -Werror -Wno-noexcept-type -O2 -pedantic -pedantic-errors
Linker flags: -Wl,-O1 -Wl,--as-needed```

## Additional context
*Add any other context that you think is necessary about the problem here.*

It seems like it can't create the X window for some reason. "BadMatch" is defined as "Some argument or pair of arguments has the correct type and range but fails to match in some other way required by the request" here, which means that one of the arguments (cw_*()) is incorrect.
Some blind debugging suggestions:

Try fiddling around with each cw_*() and see what happens (depth to 24, etc.)
Track when the monitor issue occurs when polybar loads, if possible.

This seems like a depth issue, are you running any compositors?
The font errors are because you don't have the proper font installed, you can either replace those with fonts from other characters or install it. They don't have anything to do with this issue.

no compositors.. I installed siji font but it's still not being picked up by polybar.  Also the window appears to still be black with no other rendering.

Could you try running with compton and also check the image produced by the png export (-p output.png)?

Could you also continue your testing with the following minimal config. This would make totally sure that the error is independent from the config and also would reduce much of the unuseful noise in the logs.
[bar/example]
modules-left = text

[module/text]
type = custom/text
content = Text

Thanks for the compton advice.  I installed it (I don't use it) and it warned me that composition wasn't enabled in my nvidia setup.  My /etc/X11/xorg.conf had Composite disabled and once I removed that line and bounced X, polybar worked fully even with the default config/example and with compton not running.
Sorry for the trouble - I'm not entirely sure how Composite false and DAMAGE true extensions slipped in there (they aren't in my other Archlinux setup) but at least this is taken care of.
I imagine since compton was able to warn that desktop composition was disabled that something in the xcb error dump I provided above might be able to be used to detect a misconfigured system?

There's already support for checking the composite extension, but WITH_XCOMPOSITE is off by default. If you disable Composite and set https://github.com/jaagr/polybar/blob/a881d49d9d6c173e394d790b308d11fb421327d7/cmake/02-opts.cmake#L48
to ON, it should throw an error now. Could you confirm this?

With
        Option "Composite" "Disable"
EndSection```

I confirm polybar doesn't display and doesn't warn and the output is:

% polybar example
warn: No monitor specified, using "DP-0"
error: module/xbacklight: Could not get data (err: XCB_NAME (15))
error: Disabling module "xbacklight" (reason: Not supported for "DP-0")

Whoops, I missed the #if 0 in the composite checking. Could you apply this diff:
diff --git a/src/x11/extensions/composite.cpp b/src/x11/extensions/composite.cpp
index 09a2bb6..d008ee5 100644
--- a/src/x11/extensions/composite.cpp
+++ b/src/x11/extensions/composite.cpp
@@ -8,14 +8,12 @@ namespace composite_util {
   /**
    * Query for the XCOMPOSITE extension
    */
-  void query_extension(connection&) {
-#if 0
+  void query_extension(connection& conn) {
     conn.composite().query_version(XCB_COMPOSITE_MAJOR_VERSION, XCB_COMPOSITE_MINOR_VERSION);

     if (!conn.extension<xpp::composite::extension>()->present) {
       throw application_error("Missing X extension: Composite");
     }
-#endif
   }
 }

That got it:  error: Missing X extension: Composite
Here's the final diff:
diff --git a/cmake/02-opts.cmake b/cmake/02-opts.cmake
index a044c4f..4a2e1cb 100644
--- a/cmake/02-opts.cmake
+++ b/cmake/02-opts.cmake
@@ -45,7 +45,7 @@ option(WITH_XRANDR_MONITORS "xcb-randr monitor support" ON)
 option(WITH_XRENDER "xcb-render support" OFF)
 option(WITH_XDAMAGE "xcb-damage support" OFF)
 option(WITH_XSYNC "xcb-sync support" OFF)
-option(WITH_XCOMPOSITE "xcb-composite support" OFF)
+option(WITH_XCOMPOSITE "xcb-composite support" ON)
 option(WITH_XKB "xcb-xkb support" ON)
 option(WITH_XRM "xcb-xrm support" ON)
 option(WITH_XCURSOR "xcb-cursor support" ON)
diff --git a/src/x11/extensions/composite.cpp b/src/x11/extensions/composite.cpp
index 09a2bb6..d008ee5 100644
--- a/src/x11/extensions/composite.cpp
+++ b/src/x11/extensions/composite.cpp
@@ -8,14 +8,12 @@ namespace composite_util {
   /**
    * Query for the XCOMPOSITE extension
    */
-  void query_extension(connection&) {
-#if 0
+  void query_extension(connection& conn) {
     conn.composite().query_version(XCB_COMPOSITE_MAJOR_VERSION, XCB_COMPOSITE_MINOR_VERSION);

     if (!conn.extension<xpp::composite::extension>()->present) {
       throw application_error("Missing X extension: Composite");
     }
-#endif
   }
 }


Action: Definition of Done

Description
This PR introduces a new Action which verifies that the Definition of Done Checklist exists in the Description of the PR, and will fail until all tasks are checked.
Completes: AB#33717

It would be cool if the Description of a Feature and its UAC are copied into the description of a the PR when linked to the appropriate AB# item.... avoid double work.

add this
Verify that a valid Azure Board Work Item Type Story exists
name: ab-story-validation
on:
pull_request:
types: [opened, edited, reopened]
jobs:
ab-storyid:
runs-on: ubuntu-latest
name: 'Validate Azure Board StoryID'
steps:
- name: ab-story-validation
uses<EMAIL_ADDRESS>with:
GITHUB_TOKEN: '${{secrets.GITHUB_TOKEN}}'

add this

Verify that a valid Azure Board Work Item Type Story exists
name: ab-story-validation
on:
pull_request:
types: [opened, edited, reopened]
jobs:
ab-storyid:
runs-on: ubuntu-latest
name: 'Validate Azure Board StoryID'
steps:
- name: ab-story-validation
uses<EMAIL_ADDRESS>with:
GITHUB_TOKEN: '${{secrets.GITHUB_TOKEN}}'
Will do - on a new PR


[Examples Browser] Controls for Post effect / lights examples

This PR moves control of the post effects and lights examples from the keyboard to the control panel. The control panel has been updated to support scrolling and will no longer extend past 100% of the screen. Also made a few other minor visual tweaks to the control panel.

I confirm I have read the contributing guidelines and signed the Contributor License Agreement.

fantastic. Could we keep keyboard shortcuts in place as well somehow for both examples? That is really fast way to do when working on lights / shadows and similar.

And just double checking, does it work (fit on the screen) on mobile?

fantastic. Could we keep keyboard shortcuts in place as well somehow for both examples? That is really fast way to do when working on lights / shadows and similar.

With the text elements on screen too or just the keyboard inputs? It looked pretty cluttered with that text.

And just double checking, does it work (fit on the screen) on mobile?

Tested and working on mobile. Large collections of controls will be scrollable.

With the text elements on screen too or just the keyboard inputs?

Maybe change the header names somehow? instead of "Bloom", have "Bloom [Key_5]" or something like that.

With the text elements on screen too or just the keyboard inputs?

Maybe change the header names somehow? instead of "Bloom", have "Bloom [Key_5]" or something like that.

This works 👍  Added they key controls back in with updated header texts in the control panel.


Are these activities (create an I) Auditable\ restrictable

Activities that can be restricted on macOS
Once a macOS device is onboarded into Microsoft Purview solutions, you can monitor and restrict these actions with data loss prevention (DLP) policies.
Copy to a USB removable media – when enforced, this action blocks, warns or audits the copying or moving of protected files from an endpoint device to USB removable media
Copy to network shares – when enforced, this action blocks, warns, or audits the copying or moving of protected files from an endpoint device to any network share
Print – when enforced, this action blocks, warns, or audits when protected files are printed from an endpoint device
Copy to clipboard – when enforced, this action blocks, warns, or audits data in protected file that is being copied to a clipboard on an endpoint device
Upload to cloud – this action blocks, warns, or audits when protected files are prevented from or allowed to be uploaded to cloud services based on the allow/unallowed domains list in global settings. When this action is set to warn or block, other browsers (defined on unallowed browsers list under Global settings) are blocked from accessing the file.
Accessed by unallowed apps – when enforced, this action prevents applications that are on the unallowed apps list (as defined in Global settings) from accessing protected files on an endpoint device. Sample scenarios
  | Onboarding devices into device management

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

ID: 07fe1d95-0032-b21b-1bd2-735c1e0f7d76
Version Independent ID: 07fe1d95-0032-b21b-1bd2-735c1e0f7d76
Content: Onboard macOS devices into Microsoft 365 overview - Microsoft Purview (compliance)
Content Source: microsoft-365/compliance/device-onboarding-macos-overview.md
Service: o365-seccomp
GitHub Login: @chrfox
Microsoft Alias: chrfox

Thank you for reviewing and replying to my request.
I am waiting for the changes to be reflected in the document.

@msbemba Thank you very much for the contribution and updating the documentation with PR. @koike-a Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


The sum should exclude the diagonal term

https://github.com/DavisThuillier/Ludwig.jl/blob/ae410e2cd2960b22efeb5ac8ca592a9f3aa514e0/scripts/Sr2RuO4_analysis.jl#L33
This formula is only ok if L[i,i] is initially zero, but this is not guaranteed: for electron_electron, as far as I can tell it looks like L[i,i] gets calculated and assigned

I disagree here. If the formula were L[i,i] = - sum(L[i, :]) we would require that L[i,i] = 0. However, because the assignment subtracts off the entire row sum, it also subtracts any erroneous part calculated for L[i,i] initially. The existence of the zero-eigenvalue mode supports this.

You're right sorry I did not see it was -= and not = -


Regularized Gaussian extension: ADMM and TV

Closes CUQI-DTU/CUQIpy-admin#24
Sub PR from CUQI-DTU/CUQIpy#424

Added ADMM solver
Added Total Variation regularization for Regularized Gaussians

I considered separating the two, but together they provides a tangible feature for CUQIpy.
To-do:

[x] Tests

@jeverink Anything left from this PR that was not in the two merged PRs?

@nabriis , This PR also contains some code to do nonnegativity constraints and TV regularization at the same time. This has yet to be merged in the previous two PRs and is on the list in #585.

@nabriis , This PR also contains some code to do nonnegativity constraints and TV regularization at the same time. This has yet to be merged in the previous two PRs and is on the list in #585.

Ah very excellent! Let me know when it is ready for review :)


Test the Valid Moves Generation

Create a Perft Function, compare it with the Expected Results and fix any errors that might occur.

After the latest commit (Perft Test Implementation), there are still some things that do not work. Currently, I've found that some of the issues on the start position and depth 5 are most likely produced by en passant moves. Another bottleneck could be promotion moves.


Make post excerption more flexible

For example, if I ask Ghost to cut first 50 symbols then it will do so. I think that it will be more logical to excerpt 50 +- to the nearest end of the nearest phrase.
Because I, for example, use MailChimp to send emails when it checks my RSS. It takes this excerpted part. If it ends with "," then the last symbol in my letter will be ",". That's not very good.

There's already an issue out for this: #5060.


some comments

https://github.com/gSulpizio/isotherm-analysis/blob/7ff9243f06472539a53a28af52af709bd9856a81/src/BETFitWeighted.ts#L12

Du you want the first weight to always be 1? According to Fig 2 in the paper it is not light that in the original implementation. You might just take two points that you would not consider for the fit (w=0) at the boundaries
did you console.log the weights? How are they distributed? Did you try to set them uniformly for debugging?
please also note https://github.com/pauliacomi/pyGAPS/blob/69f0037aa8a64b49f0e5b036a83d67f463e5743f/src/pygaps/characterisation/area_bet.py#L320-L345

I would add docstrings with reference to the original paper and equation, in this case eq. 11. You would at some point also need to think about how you want to deal with the units. Or at least give the user a clue what dimensionality the result will have.

https://github.com/gSulpizio/isotherm-analysis/blob/7ff9243f06472539a53a28af52af709bd9856a81/src/modelFunctions.ts#L19 what do you mean with the comment? When shouldn't p be a number?

So the weights are around 1 (+/-, with some variation after the 5th decimal) except for the 2 first numbers that are around 2 and 1.1. The first and last weight have been set to 0. setting them uniformly for debuggng did not really help.
For 3, indeed, just it was weird that it threw an error if the type is any, no?

But setting all weights to 1 is per definition just simple plain normal linear regression which used to work for you
On May 13, 2021 at 01:13, gSulpizio<EMAIL_ADDRESS>wrote:
So the weights are around 1 (+/-, with some variation after the 5th decimal) except for the 2 first numbers that are around 2 and 1.1. The first and last weight have been set to 0. setting them uniformly for debuggng did not really help.
For 3, indeed, just it was weird that it threw an error if the type is any, no?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/gSulpizio/isotherm-analysis/issues/1#issuecomment-840152064, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH3I2QIS4N4SU43G3J3IPWTTNMDP5ANCNFSM432I5KZQ.


squid configuration re-assessment

squid is mostly running on default configuration values. Cache size seems to be small. The fitness of its configurations should be re-assessed and if necessary fixed.

For example the disk cache is not configured - it only stores the cache in memory.
https://github.com/CSC-IT-Center-for-Science/ansible-role-squid/blob/master/templates/squid.conf.j2#L72

cache_dir gets added but still something isn't optimal with these confs

You're right.

a)
Maybe having two cache_dirs is bad (for a small cluster) - as the requests are load-balanced between the caches (based on load by default). I took the smaller/default cache away and on the second reinstall of a compute node the cache was used quite a lot. Maybe we can remove the 100MB 1 cache? https://github.com/CSC-IT-Center-for-Science/ansible-role-squid/blob/master/templates/squid.conf.j2#L87
b) the extra cache is 100000 (100GB) - but / is only 50GB on all the clusters.
cache_dir ufs /squid/cache 100000 16 256

Putting this in review. Let's review in a few weeks (when this change hopefully has propagated to the clusters).

Adding to requirements - closing. Let's open a new issue if we want to improve more.


Fix constraint index bug in critical region generator

The critical region generator includes a step which eliminates constraints that have zero vectors.  This eliminates the constraint vector and scalar from consideration for inclusion in the region, however the associated constraint index is not eliminated.  This would cause misalignment between the constraint index arrays "lambda_set" and "regular_set" and the boundary hyperplane array in such cases.  This update will synchronize the indexes with the constraints during the zero vector elimination.

I tried to cherry-pick out just the bug-fix, but some other stuff made it in like typo correction and .gitignore preference.  I thought you actually might like those changes, so I didn't bother to remove them.  I will take them out if you prefer.


DummyView animates child view with strange animation

The group and child layout are almost identical (except the group expand/collapse indicator). But when group expands or collapses, DummyView animate the children with strange pop in animation from right side (See gif below).
What could have cause this behavior?

I have the same problem with a textview.
Have you find a solution for this issue?

Nope. We went kept it invisible until animation ended.


San Diego Chapter not listed on the main site

Meetup URL: http://www.meetup.com/Girl-Develop-It-San-Diego/
Twitter: https://twitter.com/GDISD
Facebook: https://www.facebook.com/GDIInSD
[Please remove April from Chapter Leader. She left GDI last year.]
Chapter Leader:
Full Name: Jyoti Wadhwani
GDI email address<EMAIL_ADDRESS>Twitter: @wadhwanijyoti
Github: jwala1506
Bio: She is passionate about technology and wants to bring more women closer to money through tech. She received her Masters degree from UC San Diego in Computer Engineering and has been working in Qualcomm as a Software Engineer since then. At Qualcomm she develops secure kernel drivers for Mobile Operating Systems. For few months at UC San Diego, she taught small kids Scratch programming language and she loved the experience. As the next step to pursue her passion in teaching, she wants to teach coding skills to women from diverse backgrounds. At Girl Develop It she wants to combat all stereotype threats that women face by disproving them. Other than teaching and coding, she enjoys hiking and swimming.

@jwala1506 I've updated you page with the above request: https://girl-develop-it.herokuapp.com/chapters/san-diego Please verify that the changes have been made and everything looks good! :+1:

Hey! the website looks good. thank you @juliaelman :+1:

Approved and closed.


Custom dataset runtime error

Hello
I am trying to retrain yolact on Pascal Part a variation of Pascal VOC where each classes has many sub-classes.
To simplify everything I make every sub-classes a class in addition with the 20 original one which give me a set 316 classes.
I generated three JSON files for each case.
When I start training I encouter the following error:
RuntimeError: cannot perform reduction function max on tensor with no elements because the operation does not have an identity
Which happen here:
losses = criterion(out, wrapper, wrapper.make_mask())
train.py around line 262 (I had some print in my file so my line number is different)
Here:
https://github.com/eriklindernoren/PyTorch-YOLOv3/issues/110
I read it might be a path issue however I rechecked the image path are correct.
Also I am able to train Pascal Voc using the same image path without issues.
I try to investigate the forward method of the loss function looking for an empty tensor but I did not find any.

Hmm it'd be helpful if you could get the exact line that the error happens on (inside of the loss forward function), but for now can you send over your dataset and model configs? Maybe there's an issue with those.

Hello
From the file train.py it happen line 256.
It is after the declaration of the variable criterion, exactly its happen when the forward method is implicitly called.

I meant the line in multi_box.py, but it looks like the stack trace isn't printing that line out for you? The only call to max that I can see that would get triggered in multi_box.py is when computing the semantic segmentation loss--i.e., would have to do with classes.
Can you send over your dataset and model configs so I can check if you set up the classes properly?

I'll try to investigate more deeply the structuratoin of the dataset.

I just realized I misread you last response.
The issue appear in the function match from the class box_utils.py  which is called in the method forward of the class Multibox:
Here the error message:
(Note the prints after begin training are mine)
%run train.py --config=yolact_base_config
loading annotations into memory...
Done (t=4.22s)
creating index...
index created!
loading annotations into memory...
Done (t=4.58s)
creating index...
index created!
Initializing weights...
NB CLASSES: 317
NB IMAGES TO LOAD: 625
Begin training!

<class 'dict'> dict_keys(['loc', 'conf', 'mask', 'priors', 'proto', 'segm']) <class '__main__.ScatterWrapper'> <class 'torch.Tensor'> torch.Size([8])
BEFORE MATCH:  0.5 0.4 torch.Size([0, 4]) torch.Size([19248, 4]) 0
BOX UTILS: torch.Size([0, 19248])
BEFORE MATCH:  0.5 0.4 torch.Size([0, 4]) torch.Size([19248, 4]) 0
BOX UTILS: torch.Size([0, 19248])
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
/hdd1/prog/yolact/train.py in <module>()
    520                 tmask = wrapper.make_mask()
    521                 print(type(out), out.keys(), type(wrapper), type(wrapper.make_mask()), tmask.shape)
--> 522                 losses = criterion(out, wrapper, wrapper.make_mask())
    523
    524                 losses = { k: v.mean() for k,v in losses.items() } # Mean here because Dataparallel

~/anaconda3/lib/python3.6/site-packages/torch/nn/modules/module.py in __call__(self, *input, **kwargs)
    487             result = self._slow_forward(*input, **kwargs)
    488         else:
--> 489             result = self.forward(*input, **kwargs)
    490         for hook in self._forward_hooks.values():
    491             hook_result = hook(self, input, result)

~/anaconda3/lib/python3.6/site-packages/torch/nn/parallel/data_parallel.py in forward(self, *inputs, **kwargs)
    141             return self.module(*inputs[0], **kwargs[0])
    142         replicas = self.replicate(self.module, self.device_ids[:len(inputs)])
--> 143         outputs = self.parallel_apply(replicas, inputs, kwargs)
    144         return self.gather(outputs, self.output_device)
    145

~/anaconda3/lib/python3.6/site-packages/torch/nn/parallel/data_parallel.py in parallel_apply(self, replicas, inputs, kwargs)
    151
    152     def parallel_apply(self, replicas, inputs, kwargs):
--> 153         return parallel_apply(replicas, inputs, kwargs, self.device_ids[:len(replicas)])
    154
    155     def gather(self, outputs, output_device):

~/anaconda3/lib/python3.6/site-packages/torch/nn/parallel/parallel_apply.py in parallel_apply(modules, inputs, kwargs_tup, devices)
     81         output = results[i]
     82         if isinstance(output, Exception):
---> 83             raise output
     84         outputs.append(output)
     85     return outputs

~/anaconda3/lib/python3.6/site-packages/torch/nn/parallel/parallel_apply.py in _worker(i, module, input, kwargs, device)
     57                 if not isinstance(input, (list, tuple)):
     58                     input = (input,)
---> 59                 output = module(*input, **kwargs)
     60             with lock:
     61                 results[i] = output

~/anaconda3/lib/python3.6/site-packages/torch/nn/modules/module.py in __call__(self, *input, **kwargs)
    487             result = self._slow_forward(*input, **kwargs)
    488         else:
--> 489             result = self.forward(*input, **kwargs)
    490         for hook in self._forward_hooks.values():
    491             hook_result = hook(self, input, result)

/hdd1/prog/yolact/layers/modules/multibox_loss.py in forward(self, predictions, wrapper, wrapper_mask)
    138             match(self.pos_threshold, self.neg_threshold,
    139                   truths, defaults, labels[idx], crowd_boxes,
--> 140                   loc_t, conf_t, idx_t, idx, loc_data[idx])
    141
    142             gt_box_t[idx, :, :] = truths[idx_t[idx]]

/hdd1/prog/yolact/layers/box_utils.py in match(pos_thresh, neg_thresh, truths, priors, labels, crowd_boxes, loc_t, conf_t, idx_t, idx, loc_data)
    138
    139     # Size [num_objects] best prior for each ground truth
--> 140     best_prior_overlap, best_prior_idx = overlaps.max(1)
    141     # Size [num_priors] best ground truth for each prior
    142     best_truth_overlap, best_truth_idx = overlaps.max(0)

RuntimeError: cannot perform reduction function max on tensor with no elements because the operation does not have an identity

As visible in my prints I identify that some tensors are empty but I am still investigating the reason why they are empty.
It seem to be linked to the JSON files however when I investigate it with pycocotools every thing seem  normal in the sens that I did not encounter any error nor issues.
I was able to work with the data access the mask and annotations and everything the way I used to do.

Can you show me the dataset and model configs you set up in config.py? Looking at that line, it seems one of truths and decoded_priors is empty. If decoded_priors is empty that means something with your model config is wrong and the config produced no anchor boxes. If truths is empty, then that means something with your dataset isn't configured properly (truths should never be empty because I ignore images without GT).
I have a feeling this is a simple mistake in one of your configs (not the COCO annotations, but the config.py configs).

I evaluated with Pascal-Voc that just setting in yolact_base_config the fields dataset and num_classes refering to the dataset was enough.
I reached also during the week end that some issues should come from my settings.
I am investigating it looking for whats wrong.
Just by curiosity what would happen if this error would be ignore ?

Ignoring the error will just lead to another one down the line since something (and by looking at your settings I thin truths) is empty when it shouldn't be.
Is there any annotation in the dataset with segmentation but no bounding box or with a bounding box but no segmentation?
Or are there any images with "iscrowd" set to 1 for all annotations for that image?

I setted "iscrowd" to one for every annotation.
My reason is because I have classes and subclasses in the initial annotations so the classes and subclasses are connex some are very close and may be slightly overlapped.
In addition all overlap the category (i.e. dog_leye overlap dog_whole).
For this reason I set the flag "iscrowd" to true for every annotation.
The original annotations where made from  binary masks store in a set of mat files.
So every annotation is made from a binary mask.
But pycococreator in the process of creation of the json files as store the bounding box as well as the segmentations.
I processed every file the same way and I try to paid attention to the two errors you mentioned but I may made a mistake.
I actually regenerate the json files yesterday trying to recheck if an empty mask could have not been ignored.
I am starting an investigation of the annotations and bounding box right now.
If an empty mask has been process maybe I can find it first and then figure out whats happen.
I am also preparing to do the same thing using a micro dataset (5 categories, 20 images: 6 trains, 4 val, 10 tests) from COCO.
Generate a json from the one of COCO make it work, generete 3 jsons files from the masks for each category check if it works.

Well there's your problem. "iscrowd" tells COCO to ignore every detection that overlaps with it. It's not used for training, it's used to give the model a break when there's a crowd of people and each person isn't individually annotated.
Do not use iscrowd for data you actually want to train on. Like every other method and like COCO does in evaluation, I completely ignore all detections that overlap with an "iscrowd" detection.

Ok I'll try.
I start the regeneration right now.

I have a great news it works !!! The issue came from the parameter iscrowd.
Thanks very much for all the time you spent helping me really thank you very much.

@JSharp4273 Hi Julien, I have a similar problem. All of my images have many overlapping instances.. so iscrowd=1 in the coco.json file. How can I train YOLACT with this data? I am able to train MaskRCNN with it but I would rather use YOLACT.
Regards, Sam @dbolya


Dynamically created DropZones with for loop are not working as expected.

Bug type
Component
Component name
MudDropZone
What happened?
MudDropZones that are created inside MudDropZoneContainer using for loop will render:
@for (int i = 0; i < 3; i++)
{
    <MudDropZone Class="drop-zone" T="string" ItemsSelector="@((item) => item.Contains(i.ToString()))" />
}

Creating exact same drop zones one by one will work flawlessly:
<MudDropZone Class="drop-zone" T="string" ItemsSelector="@(item => item.Contains("0"))" />
<MudDropZone Class="drop-zone" T="string" ItemsSelector="@(item => item.Contains("1"))" />
<MudDropZone Class="drop-zone" T="string" ItemsSelector="@(item => item.Contains("2"))" />

Expected behavior
In the example link, both DropZoneContainers should work just like each other.
Reproduction link
https://try.mudblazor.com/snippet/ckQwbYFKTnjByZfe
Reproduction steps
Click on the update items button the right drop zone will update, but the left one won't.
Relevant log output
No response
Version (bug)
6.0.16
Version (working)
No response
What browsers are you seeing the problem on?
Microsoft Edge
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

It has something to do with capturing of variables in a loop, there are some good explanations out there.
But most of all, it's certainly is not a MudBlazor bug.


Configuration Help

Describe your desired configuration
Hey,
i switched from alpha 9 to alpha 10, but sadly i cant use my old config... All the fans are not lighting, did you change something so i have to adopt my config?
Also i wanted to try something like this https://youtu.be/0jXurJMYQYk?t=120 but i cant get the aurora effect to work like the one in the video i've linked
Thanks in advance
Hardware info
Info
-------------------------------
»
»        OS: Windows 10 Enterprise 1909 [18362.1.amd64fre.19h1_release.190318-1202]
»        Build: 0.10.0-alpha+Branch.master.Sha.a826afd7df70a522c78f4785f357baa124b6a937
»
-------------------------------
Controllers
-------------------------------
»
»  Name: Riing Trio
»        VendorId: 9802
»        ProductId: 8502
»        Ports:
»                1:
»                        Data: [PortId: 1, Speed: 0, Rpm: 553, Unknown: 255]
»                        Identifier: [9802, 8502, 1]
»                2:
»                        Data: [PortId: 2, Speed: 0, Rpm: 557, Unknown: 255]
»                        Identifier: [9802, 8502, 2]
»                3:
»                        Data: [PortId: 3, Speed: 0, Rpm: 549, Unknown: 255]
»                        Identifier: [9802, 8502, 3]
»                4:
»                        Data: [PortId: 4, Speed: 35, Rpm: 552, Unknown: 255]
»                        Identifier: [9802, 8502, 4]
»                5:
»                        Data: [PortId: 5, Speed: 60, Rpm: 0, Unknown: 255]
»                        Identifier: [9802, 8502, 5]
»        Available effect types: PerLed
»  Name: Riing Trio
»        VendorId: 9802
»        ProductId: 8501
»        Ports:
»                1:
»                        Data: [PortId: 1, Speed: 35, Rpm: 396, Unknown: 255]
»                        Identifier: [9802, 8501, 1]
»                2:
»                        Data: [PortId: 2, Speed: 35, Rpm: 379, Unknown: 255]
»                        Identifier: [9802, 8501, 2]
»                3:
»                        Data: [PortId: 3, Speed: 35, Rpm: 456, Unknown: 255]
»                        Identifier: [9802, 8501, 3]
»                4:
»                        Data: [PortId: 4, Speed: 0, Rpm: 534, Unknown: 255]
»                        Identifier: [9802, 8501, 4]
»                5:
»                        Data: [PortId: 5, Speed: 0, Rpm: 454, Unknown: 255]
»                        Identifier: [9802, 8501, 5]
»        Available effect types: PerLed
»
-------------------------------
Sensors
-------------------------------
»
»  Nuvoton NCT6793D:
»        Temperature:
»                CPU Core (/lpc/nct6793d/temperature/0): 51,5 °C
»                Temperature #2 (/lpc/nct6793d/temperature/2): 39,0 °C
»                Temperature #3 (/lpc/nct6793d/temperature/3): 12,0 °C
»                Temperature #4 (/lpc/nct6793d/temperature/4): 11,0 °C
»                Temperature #6 (/lpc/nct6793d/temperature/6): -1,0 °C
»
»  Intel Core i7-6700K:
»        Temperature:
»                CPU Core #1 (/intelcpu/0/temperature/0): 41,0 °C
»                CPU Core #2 (/intelcpu/0/temperature/1): 46,0 °C
»                CPU Core #3 (/intelcpu/0/temperature/2): 37,0 °C
»                CPU Core #4 (/intelcpu/0/temperature/3): 45,0 °C
»                CPU Package (/intelcpu/0/temperature/4): 48,0 °C
»                CPU Core #1 Distance to TjMax (/intelcpu/0/temperature/5): 59,0 °C
»                CPU Core #2 Distance to TjMax (/intelcpu/0/temperature/6): 54,0 °C
»                CPU Core #3 Distance to TjMax (/intelcpu/0/temperature/7): 63,0 °C
»                CPU Core #4 Distance to TjMax (/intelcpu/0/temperature/8): 55,0 °C
»                Core Max (/intelcpu/0/temperature/9): 46,0 °C
»                Core Average (/intelcpu/0/temperature/10): 42,3 °C
»
»  NVIDIA GeForce RTX 2080:
»        Temperature:
»                GPU Core (/gpu/0/temperature/0): 47,0 °C
»
»  Samsung SSD 970 EVO 500GB:
»        Temperature:
»                Temperature (/nvme/1/temperature/0): 56,0 °C
»                Temperature 1 (/nvme/1/temperature/6): 56,0 °C
»                Temperature 2 (/nvme/1/temperature/7): 72,0 °C
»

Current configuration
   "Profiles": [
    {
      "Name": "GPU",
      "Ports": [
        [9802, 8501, 4],
        [9802, 8501, 5],
        [9802, 8502, 1],
        [9802, 8502, 2],
        [9802, 8502, 3],

      ],
      "SpeedControllers": [
        {
          "Type": "PwmSpeedController",
          "Config": {
            "CurvePoints": [
              [50, 0],
              [55, 25],
              [65, 45],
              [70, 60],
              [75, 65]
            ],
            "Sensors": ["/gpu/0/temperature/0"],
            "Trigger": {
              "Type": "AlwaysTrigger"
            }
          }
        }
      ],
      "Effects": [
        {
          "Type": "WaveEffect",
          "Config": {
            "Colors": [
                [255, 0, 0],
                [255, 0, 51],
                [255, 0, 102],
                [255, 0, 153],
                [255, 0, 204],
                [255, 0, 255],
                [204, 0, 255],
                [154, 0, 255],
                [104, 0, 255],
                [54, 0, 255],
                [0, 0, 255],
                [0, 46, 255],
                [0, 93, 255],
                [0, 140, 255],
                [0, 187, 255],
                [0, 234, 255],
                [0, 238, 212],
                [0, 242, 170],
                [0, 246, 127],
                [0, 250, 85],
                [0, 255, 43],
                [51, 251, 34],
                [102, 248, 25],
                [153, 244, 17],
                [204, 241, 8],
                [255, 238, 0],
                [255, 199, 0],
                [255, 161, 0],
                [255, 123, 0],
                [255, 85, 0]
            ],
            "TickInterval": 3,
            "Trigger": {
              "Type": "AlwaysTrigger"
            }
          }
        }
      ]
    },
    {
      "Name": "CPU",
      "Ports": [
        [9802, 8501, 1],
        [9802, 8501, 2],
        [9802, 8501, 3],
        [9802, 8502, 4]
      ],
      "SpeedControllers": [
        {
          "Type": "PwmSpeedController",
          "Config": {
            "CurvePoints": [
              [30, 15],
              [45, 35],
              [55, 50],
              [65, 55],
              [75, 60]
            ],
            "Sensors": ["/intelcpu/0/temperature/4"],
            "Trigger": {
              "Type": "AlwaysTrigger"
            }
          }
        }
      ],
      "Effects": [
        {
          "Type": "WaveEffect",
          "Config": {
            "Colors": [
                [255, 0, 0],
                [255, 0, 51],
                [255, 0, 102],
                [255, 0, 153],
                [255, 0, 204],
                [255, 0, 255],
                [204, 0, 255],
                [154, 0, 255],
                [104, 0, 255],
                [54, 0, 255],
                [0, 0, 255],
                [0, 46, 255],
                [0, 93, 255],
                [0, 140, 255],
                [0, 187, 255],
                [0, 234, 255],
                [0, 238, 212],
                [0, 242, 170],
                [0, 246, 127],
                [0, 250, 85],
                [0, 255, 43],
                [51, 251, 34],
                [102, 248, 25],
                [153, 244, 17],
                [204, 241, 8],
                [255, 238, 0],
                [255, 199, 0],
                [255, 161, 0],
                [255, 123, 0],
                [255, 85, 0]
            ],
            "TickInterval": 3,
            "Trigger": {
              "Type": "AlwaysTrigger"
            }
          }
        }
      ]
    }
  ],
  "PortConfigs": [
    {
      "Ports": [
        [9802, 8501, 1],
        [9802, 8501, 2],
        [9802, 8501, 3],
        [9802, 8501, 4],
        [9802, 8501, 5],
        [9802, 8502, 1],
        [9802, 8502, 2],
        [9802, 8502, 3],
        [9802, 8502, 4]
      ],
      "Config": {
        "DeviceType": "RiingTrio"
      }
    }
  ]
}

Yes all effects now use color providers
So:
        {
          "Type": "WaveEffect",
          "Config": {
            "Color": {
                "PerLed": [
                    [255, 0, 0],
                    [255, 0, 51],
                    [255, 0, 102],
                    [255, 0, 153],
                    [255, 0, 204],
                    [255, 0, 255],
                    [204, 0, 255],
                    [154, 0, 255],
                    [104, 0, 255],
                    [54, 0, 255],
                    [0, 0, 255],
                    [0, 46, 255],
                    [0, 93, 255],
                    [0, 140, 255],
                    [0, 187, 255],
                    [0, 234, 255],
                    [0, 238, 212],
                    [0, 242, 170],
                    [0, 246, 127],
                    [0, 250, 85],
                    [0, 255, 43],
                    [51, 251, 34],
                    [102, 248, 25],
                    [153, 244, 17],
                    [204, 241, 8],
                    [255, 238, 0],
                    [255, 199, 0],
                    [255, 161, 0],
                    [255, 123, 0],
                    [255, 85, 0]
                ]
            },
            "TickInterval": 3,
            "Trigger": {
              "Type": "AlwaysTrigger"
            }
          }
        }

I dont see anything special in that video so you should be able to tweak the effect to almost match it.
I think what is happening is that the aurora effect does not handle multiple zones at the moment.
I have proper multi zone support planned but I have not figured out a nice way to do that.

Thanks for your fast answer!
Made my WaveEffekt work again, thanks!
About the Aurora:
i cant get a grip on how i manage to go "full rainbow" and color change per Fan. (if that makes any sense to you)
In the video you can see the color changes per fan and not the fan-stack.
Currently only the color of all fans change at the same time, i reckon i messed up somewhere in the config. Took the effekt from an other issue that i found:
{
"Profiles": [
{
"Name": "GPU",
"Ports": [
[9802, 8501, 4],
[9802, 8501, 5],
[9802, 8502, 1],
[9802, 8502, 2],
[9802, 8502, 3],
  ],
  "SpeedControllers": [
    {
      "Type": "PwmSpeedController",
      "Config": {
        "CurvePoints": [
          [50, 0],
          [55, 25],
          [65, 45],
          [70, 60],
          [75, 65]
        ],
        "Sensors": ["/gpu/0/temperature/0"],
        "Trigger": {
          "Type": "AlwaysTrigger"
        }
      }
    }
  ],
   "Effects": [
    {
      "Type": "AuroraEffect",
      "Config": {
        "Gradient": [
            [0.0, [220, 0, 0]],
            [0.1, [215, 5, 0]],
            [0.2, [200, 10, 0]],
            [0.3, [140, 80, 0]],
            [0.4, [20, 255, 30]],
            [0.5, [0, 140, 170]],
            [0.6, [0, 80, 200]],
            [0.7, [55, 60, 160]],
            [0.8, [180, 30, 60]],
            [0.9, [200, 2, 4]],
            [1.00, [220, 0, 1]]

        ],
        "Step": 0.009,
        "Length": 256,
        "Mirror": false,
        "Brightness": 1,
        "Saturation": 1,

        "Trigger": {
          "Type": "AlwaysTrigger"
        }
      }
    }
  ]
},
{
  "Name": "CPU",
  "Ports": [
    [9802, 8501, 1],
    [9802, 8501, 2],
    [9802, 8501, 3],
    [9802, 8502, 4]
  ],
  "SpeedControllers": [
    {
      "Type": "PwmSpeedController",
      "Config": {
        "CurvePoints": [
          [30, 15],
          [45, 35],
          [55, 50],
          [65, 55],
          [75, 60]
        ],
        "Sensors": ["/intelcpu/0/temperature/4"],
        "Trigger": {
          "Type": "AlwaysTrigger"
        }
      }
    }
  ],
   "Effects": [
    {
      "Type": "AuroraEffect",
      "Config": {
        "Gradient": [
            [0.0, [220, 0, 0]],
            [0.1, [215, 5, 0]],
            [0.2, [200, 10, 0]],
            [0.3, [140, 80, 0]],
            [0.4, [20, 255, 30]],
            [0.5, [0, 140, 170]],
            [0.6, [0, 80, 200]],
            [0.7, [55, 60, 160]],
            [0.8, [180, 30, 60]],
            [0.9, [200, 2, 4]],
            [1.00, [220, 0, 1]]

        ],
        "Step": 0.009,
        "Length": 256,
        "Mirror": false,
        "Brightness": 1,
        "Saturation": 1,

        "Trigger": {
          "Type": "AlwaysTrigger"

        }
      }
    }
  ]
}

],
"PortConfigs": [
{
"Ports": [
[9802, 8501, 1],
[9802, 8501, 2],
[9802, 8501, 3],
[9802, 8501, 4],
[9802, 8501, 5],
[9802, 8502, 1],
[9802, 8502, 2],
[9802, 8502, 3],
[9802, 8502, 4]
],
"Config": {
"DeviceType": "RiingTrio"
}
}
]
}
if tried leaving the "gradient" part away, as it says in the docs it will go rainbow, but saldy i'm far off the color fidelity of the video...

Try this:
    {
      "Type": "AuroraEffect",
      "Config": {
        "ColorGenerationMethod": "SpanPorts",
        "Step": 0.009,
        "Length": 60,
        "Mirror": true,
        "Brightness": 1,
        "Saturation": 1,
        "Trigger": {
          "Type": "AlwaysTrigger"
        }
      }
    }

By tweaking the "Length" you will get different behaviors.
If its equals to total led count in profile then it will create a perfectly looping gradient.
If its larger then you will only see a portion of the gradient at a time, this smoothes the gradient.
If its smaller then you will see the gradient loop multiple times.
Note that when using "Mirror": true the "Length" should be halved (because the other half is mirrored).
So for perfectly looping gradient: Length = 4 ports in profile * 30 leds (Riing Trio) = 120, if mirror is enabled then you have to halve it to 60.
But like I said AuroraEffect does not know how to handle multiple zones so it might look weird.

thank you so much!
I'll play around with it for some time.
Thanks again, love your work


convergence tracker for netpol

convergencetracker image is used in network policy scale testing. These files are taken from Nadia's convergence tracker[1]. It moniots OVS flows and measures when OVS flows gets stabilized and report this as a metric.
[1] https://github.com/npinaeva/k8s-netpol-scale/tree/main/kube-burner-workload/openshift/openflow-tracker

@venkataanil , there're some conflicts


Add pixels for exclusion list

Task/Issue URL: https://app.asana.com/0/0/1204651089273625/f
Description
See description https://app.asana.com/0/0/1204651089273625/f
Steps to test this PR
See task: https://app.asana.com/0/0/1204651089273625/f

Current dependencies on/for this PR:

develop

PR #3232

PR #3267   👈
PR #3233

This comment was auto-generated by Graphite.


report timestamps in a consistent format in data export

Currently, the science data timings are exported in a mixture of formats:
  "timeBatchInitialized": "2023-12-26T01:57:29.126Z",
  "timeArrived": "2023-12-26T01:57:35.218Z",
  "timeEnteredCountdown":<PHONE_NUMBER>175,
  "timeIntroDone":<PHONE_NUMBER>303,
  "timeStarted": "2023-12-26T01:57:49.167Z",
  "timeComplete":<PHONE_NUMBER>908,

we should standardize these to all be in the human-readable format. Not sure if this can happen at the point where they are saved in the code, or if it needs to happen in the export file.

The epoch times above seem to be only used in reporting, so setting them to new Date(Date.now()).toISOString()


704 document quick start removal

Checklist:

[x] Read the Code of Conduct and Contributing Guidelines.

[x] Followed the commit message guidelines.

[x] Stack adheres to Appsody stack structure.

Modifying an existing stack:

[x] Updated the stack version in stack.yaml

Contributing a new stack:

Describe how application dependencies are managed:

Explain how Appsody file watcher is utilized:

Describe other Appsody environment variables defined by the stack image:

Describe any limitations and known issues:

Related Issues:

#704

@skoh7645 @Kamran64 we have one more when you get a chance.
This would be:
java-microprofile:

echo informational message about quick-start-security.xml during appsody build

java-openliberty:

echo informational message about quick-start-security.xml during appsody build
Update stack description.

Thank you again.

Fixes #704

@uberskigeek @scottkurz This PR LGTM, but we need to split this PR to do releases for both the java-microprofile and java-openliberty stacks


Rewrite in uwp

Rewrite RGBMaster in UWP, fix Music and Pointer Sync modes.
fixed Yeelight WiFi bug.
Implemented logos for devices and providers.

LGTM

Merging is bugged, opening new pull request.


Messages, Checks, admin panel

I see, its more subtle that way

@UjjwalAggarwal-1 Let me know if you would like to contribute more!


Fix for serializing DnsSeedMasterFile

Fix for 3163.

Move the Seed method into DnsSeedMasterFile so that it is responsible for managing its own state.
Remove the Add method to prevent the collection being modified externally.
Seed the new masterfile before swapping it. As this is only time the entries are modified, this should fix the serialization issue.
Defensively, only serialize a copy of the entries.

@StratisIain will run one of his dns seeders with this branch if all is ok we push


fix: show stx transfers from contract call

Try out this version of the Hiro Wallet - download extension builds.

Fixes #1713.
Shows all internal STX transfers triggered within contracts.
Those transfers txs are reconstructed from the contract events info and fetched from the api endpoint /transactions_with_transfers
and then merged with existing confirmed transactions. Those STX transfers are sorted to appear after the contract call (above the contract call row in the activity list)

cc/ @aulneau @kyranjamie @fbwoolf

Perhaps we can replace use of the /transaction endpoint altogether, as all the information we need is in the transaction_with_transfers one anyway.
This way, we could avoid adding a new query, and any logic to try and merge transactions together. Instead updating the store to save the different response type (which includes the whole tx in addition to the transfers).

LGTM @beguene. Good work.
Please investigate the react query comment. Other comments relate to consistency.
Interested to get your and @fbwoolf's input on how we can keep component definitions consistent. I'd promote that we follow the rule where components are always defined in this format, rather than mixing different styles.
interface ComponentNameProps extends BoxProps {
  prop: string;
}
export const ComponentName: FC<ComponentNameProps> = () => {};
export const ComponentName = (props: ComponentNameProps) => {};

The second variant might be better as using FC assumes there will be children, when there might not be.

Yes this makes sense, let's try keeping this naming convention. I agree let's keep it simple, without the FC.

@beguene Will test and keep you posted on my findings.


"Gradle sync failed: Cause: peer not authenticated"

I couldn't find Android Studio 1.0 only 2.3.3. During initial sync I get this gradle error, any suggestion on how to overcome this?

I couldn't find Android Studio 1.0

https://archive.org/details/android-studio-1.0v


Suggest logging in when unauthenticated users get rate-limited

Short explanation of the proposed change:
This commit changes Cloud Controller's rate limiting middleware to suggest that unauthenticated users log in.
Explanation of the use cases your change solves
This change helps users navigate the rate limits themselves rather than getting stuck and needing support. Without this change we've seen an awkward series of events:

A user was running something periodically against Cloud Controller;
They suspended their laptop overnight;
The next morning their login session had expired;
They hit our unauthenticated rate limit;
Other users on the same IP address got errors from cf that they did not know how to solve:Unexpected Response
Response code: 429
CC code:       10013
CC error code: CF-RateLimitExceeded
Request ID:    9cd9b261-9e4b-44d9-6edc-50ecee164f60::d3aeee04-32aa-4cb8-8d12-4ae2a19d4e11
Description:   Rate Limit Exceeded

Those users came to us confused;
We eventually figured out they were logged out or their own login session had expired, so they had hit the IP-based rate limit;
They ran cf login and all was fine.

If this PR is merged, the error message users got would be a little more helpful:
Unexpected Response
Response code: 429
CC code:       10014
CC error code: CF-IPBasedRateLimitExceeded
Request ID:    9cd9b261-9e4b-44d9-6edc-50ecee164f60::d3aeee04-32aa-4cb8-8d12-4ae2a19d4e11
Description:   Rate Limit Exceeded: please log in again

That message prompts users to log in again, and suggests the rate limit is IP-based, giving them ways to solve their own issue. Without this change we wouldn't feel confident setting a low unauthenticated rate limit.
Tickboxes

[x] I have reviewed the contributing guide

[x] I have viewed, signed, and submitted the Contributor License Agreement

[x] I have made this pull request to the master branch

[ ] I have run all the unit tests using bundle exec rake

[ ] I have run CF Acceptance Tests

Thanks for submitting this PR, @46bit! I can see how the inability to distinguish between the unauthenticated IP-based rate limiting and the individual user token-based rate limiting could be confusing and think this could help improve that UX.
@ssisil do you have any thoughts/concerns about this or suggestions for the error message?

Looks like a good UX improvement. 👍

@46bit was there a reason you have this as a draft still or would you like for us to start reviewing it?

Thanks @tcdowney :) I was having trouble running some of the tests locally, and then got distracted. I'll fix the things that Codeclimate has highlighted tomorrow and move it into Ready for review :)

@tcdowney @ssisil This is ready for review now :-) bundle exec rake is passing, but I don't have the CF Acceptance Tests set up to test it further.

Thanks again @46bit, I tested this out a bit locally and it looks good. Gonna merge it soon.

That message prompts users to log in again, and suggests the rate limit is IP-based, giving them ways to solve their own issue.

Just to make it really clear for end users, I'm going to put out a quick follow up commit to tweak the message slightly to be: Rate Limit Exceeded: Unauthenticated requests from this IP address have exceeded the limit. Please log in.

@tcdowney Wonderful, thanks for the review. And that's a great rewording.

Thank you for taking the time to submit this PR!


Add support for UA Client Hints

See https://wicg.github.io/ua-client-hints/.

My understanding of Client Hints is that everything happens through HTTP headers and there's really no space for JavaScript library to get involved in it? I saw the announcement by Chromium team that UA reduction is rolling out eventually which reminded me of this issue. If you have an idea supporting Client Hints somehow please do let me know and I might be able to help with needed changes, thanks a lot!
cf. User-Agent Reduction Origin Trial and Dates

Interested too: https://blog.chromium.org/2021/05/update-on-user-agent-string-reduction.html > "If your site, service, library or application relies on certain bits of information being present in the User Agent string such as Chrome minor version, OS version number, or Android device model, you will need to begin the migration to use the User Agent Client Hints API instead."


Readable rule names

This was originally discussed in https://github.com/mivok/markdownlint/issues/47 and rejected. However, the request was made again at https://github.com/DavidAnson/markdownlint/issues/1 for the javascript version of markdownlint, and upon revisiting that issue, the reasons for rejecting the idea don't seem valid.
We should support referring to rules by a human-readable name as well as by the numeric ID in all cases.
The following names will be used for rules:
MD001 - header-indent                - Header levels should only increment by one level at a time
MD002 - first-header-h1              - First header should be a h1 header
MD003 - header-style                 - Header style
MD004 - ul-style                     - Unordered list style
MD005 - list-indent                  - Inconsistent indentation for list items at the same level
MD006 - ul-start-left                - Consider starting bulleted lists at the beginning of the line
MD007 - ul-indent                    - Unordered list indentation
MD009 - no-trailing-spaces           - Trailing spaces
MD010 - no-hard-tabs                 - Hard tabs
MD011 - no-reversed-links            - Reversed link syntax
MD012 - no-multiple-blanks           - Multiple consecutive blank lines
MD013 - line-length                  - Line length
MD014 - commands-show-output         - Dollar signs used before commands without showing output
MD018 - no-missing-space-atx         - No space after hash on atx style header
MD019 - no-multiple-space-atx        - Multiple spaces after hash on atx style header
MD020 - no-missing-space-closed-atx  - No space inside hashes on closed atx style header
MD021 - no-multiple-space-closed-atx - Multiple spaces inside hashes on closed atx style header
MD022 - blanks-around-headers        - Headers should be surrounded by blank lines
MD023 - header-start-left            - Headers must start at the beginning of the line
MD024 - no-duplicate-header          - Multiple headers with the same content
MD025 - single-h1                    - Multiple top level headers in the same document
MD026 - no-trailing-punctuation      - Trailing punctuation in header
MD027 - no-multiple-space-blockquote - Multiple spaces after blockquote symbol
MD028 - no-blanks-blockquote         - Blank line inside blockquote
MD029 - ol-prefix                    - Ordered list item prefix
MD030 - list-marker-space            - Spaces after list markers
MD031 - blanks-around-fences         - Fenced code blocks should be surrounded by blank lines
MD032 - blanks-around-lists          - Lists should be surrounded by blank lines
MD033 - no-inline-html               - Inline HTML
MD034 - no-bare-urls                 - Bare URL used
MD035 - hr-style                     - Horizontal rule style
MD036 - no-emphasis-as-header        - Emphasis used instead of a header
MD037 - no-space-in-emphasis         - Spaces inside emphasis markers
MD038 - no-space-in-code             - Spaces inside code span elements
MD039 - no-space-in-links            - Spaces inside link text
MD040 - fenced-code-language         - Fenced code blocks should have a language specified
MD041 - first-line-h1                - First line in file should be a top level header

Thoughts on how to implement this:

add an alias method to the rule class, which can be called more than once, and adds the alias to a list of aliases for the rule.
Add an option to print out the alias as well as the rule ID when printing out rules
Alternatively, add an option to print out the alias instead of the rule ID when printing out rule names using -l and when printing errors.
When looking up rules, keep an alias -> rule mapping (separate from the regular mapping) and look it up whenever a key isn't found when looking up a rule by ID (assuming there are points in the code where a rule is looked up directly by ID). For filtering, just check the alias in addition to the rule ID.

This has been implemented.


1

Would close this as well, already has opened 4 other spam ones as referenced in comments by myself and @IEvangelist in #23113 and #23206


Added Typescript type definitions

Hey, I created typescript definitions file for this module. The changes include a new index.d.ts which includes the typescript type definitions, and a change in package.json to link to the typescript typings file.
Thank you.

Sorry, I'm not interested in having type definitions since I don't use TypeScript myself and don't have time maintaining them. I suggest adding them to https://github.com/DefinitelyTyped/DefinitelyTyped instead.


Swift PM support ?

Would be nice to be able to use this project as a Swift Package Dependency :)

Already done.


Allow disabled menu items to be focused

Feature Request
Currently, any menu items that are disabled cannot be focused. This does not match most native implementation of menus, at least in Windows (I'm not sure what the standard behaviour is in Apple's OSs).
I propose that an option like allowDisabledFocus = false be added somewhere that allows this. I am willing to submit a pull request with the changes if they're agreeable.
Expected Behavior
That disabled menu items are focus-able and not skipped when using the arrow keys, and attempting to select them will do nothing (including keeping the menu open).
Current Behavior
Currently, as per the documentation, disabled items

cannot be selected, focused, or otherwise interacted with.

Context
I'm trying to match the behaviour of native menus, which allow disabled menu items to be focus-able, but there's no way to easily add this behaviour without re-implementing parts of React Aria myself. Since there's plenty of precedent for allowing disabled items to be focus-able (see example screenshots), in my opinion it should be supported.
The WAI-ARIA recommendations leave it up to the implementation:

Disabled elements might not receive focus from the tab order. For some disabled elements, applications might choose not to support navigation to descendants.

From a user experience point-of-view, for static menus it can confusing when disabled items change the number of keypresses it takes to reach a particular option.
Possible Solutions
Depending on what it should affect, an option called allowDisabledFocus (or similar) with a default value of false could go in a couple of different places.
Adding it to the ListKeyboardDelegate class would automatically extend the allowDisabledFocus capability to everything that uses it (useComboBox, useSelect, and useSelectableList).
Alternatively, if only SelectableLists (listboxes and menus) should have that capability, then useSelectableList could be modified to pass an empty Set of disabledKeys to the ListKeyboardDelegate constructor if the option allowDisabledFocus = true.
Testing with the above modifications shows that disabled items correctly can't be selected with the keyboard, but I'm not sure if that's always the case, and if this change would have other far-reaching effects.
Examples
Adobe Illustrator:

Adobe Acrobat:

Firefox:

Android:

other disabled controls like inputs and buttons are not focusable

If they're disabled with the disabled attribute in HTML, they're not, but if the aria-disabled attribute is used, focus-ability is dependent on the implementation. And WAI-ARIA only states that disabled items might not receive focus, not that they shouldn't. And that's just on the Web. Natively, disabled controls are often focus-able, such as in Microsoft Office's Ribbon, although form-style dialogues usually disallow focusing disabled controls.

Is there a UX reason...?

Yes, consistency with native Windows menus where disabled options are almost always focus-able (MacOS is not the target), and muscle memory. This is dependent on individuals and the application in question, obviously, but I for one prefer it when the number of keypresses to reach an otherwise static thing doesn't change. Random example: in Adobe Illustrator, I can reach the Tile Windows command with Alt+W, ↓↓→↓, and this never changes whether the menu options above or below it are disabled. There are other ways of reaching it (Alt+W, A, T), but the method I landed on over time is with the arrow keys.
If it's not something that Adobe is interested in including in the React Aria project, that's fine, but I noticed the discrepancy and wanted to see if I could change it.
In any case, I've just discovered that I can pass in a custom KeyboardDelegate with the preferred behaviour directly into useMenu, which is good enough for me.

Thanks for the examples. We will bring this up to the design and accessibility teams. This would be handled holistically for all components. It looks like you have a workaround with the KeyboardDelegate.

Update
We're moving in the direction of this design https://spectrum.adobe.com/page/menu/#Unavailable, this will be released for React Spectrum components in the near future.

Unavailable menu items have been released fro React Spectrum. Please open a new issue to express interest in this feature in React Aria Components.


Supporting Dark Mode for callout style

I really like the boxes :) But in dark mode they stay white.

https://docsify-darklight-theme.boopathikumar.me (I use this)
https://github.com/Plugin-contrib/docsify-plugin/tree/master/packages/docsify-dark-mode

Regards,
Tim

@tied: Is this what you expect in dark mode?

@fzankl exactly!

Fixed in Release 1.1.0 of this plugin.


feat: use new table

What does this PR do?
Use new table in sf-plugins-core v12
What issues does this PR fix or reference?
@W-16736188@

QA Notes

✅ : verified a handful of commands and table output
✅ : NUTs 🔩


Failed to show Tech Stack

Hi, thanks for your great work. Currently I faced an issue that the Tech Stack cannot show the GitHub Tech Stack information on Chrome (Version 130.0.6723.59 (Official Build) (arm64)). Could anyone help me solve it? The screenshot of bug is attached, thanks in advance!

Thanks for your feedback, it has been fixed


Add pool.close and pool.join statements to ingest

The pool as currently written causes SIGTERMS to be thrown on child processes if a certain race condition is lost, which can happen when using the default ubuntu subprocess starting method. To fix this, add in a pool.close and pool.join call inside of the pools with block.

LGTM


App: sit positions broken

This regressed recently, probably due to massive avatar skeleton refactors.
┆Issue is synchronized with this Jira Task by Unito

The fixes were merged, this needs verification before closing the issue.

Appears to be working fine.

Thanks, I saw it working fine too.


Please add this as an example

Hello!
Based on a recent case in CSS, can you please add the following example?  Or at lease explain a bit more on the --properties and how to properly populate --name.  Also, what are the different --resource-type types that can be created.
az resource create --resource-group "[resource-group]" --resource-type "Microsoft.Web/sites/siteextensions" --name "[sitename+slot]/siteextensions/Contrast.NetCore.Azure.SiteExtension" --api-version "2018-02-01" --is-full-object --properties '{"id":"Contrast.NetCore.Azure.SiteExtension", "location":"[YourRegion]", "version": "1.9.0"}'
I found that Location was required.
Thanks!

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

ID: e76a8ad2-efd8-9e8a-9b2b-eebeb1e9d1d4
Version Independent ID: 280b7ea9-eb6c-9601-464b-09bf8e0cff5d
Content: az resource
Content Source: latest/docs-ref-autogen/resource.yml
Service: azure-resource-manager
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

ARM

@carolga  Hi, please upgrade CLI to the latest version (you can upgrade it by running az upgrade) and try again.
If this issue still can be reproduced, please feel free to let me know~

az resource create --resource-group "[resource-group]" --resource-type "Microsoft.Web/sites/siteextensions" --name "[sitename+slot]/siteextensions/Contrast.NetCore.Azure.SiteExtension" --api-version "2018-02-01" --is-full-object --properties '{"id":"Contrast.NetCore.Azure.SiteExtension", "location":"[YourRegion]", "version": "1.9.0"}'

@carolga Hi, may I ask what is the specific scenario that this example wants to explain?

Hi!
Would like to show an example of how to add a site extension to a web app.
@.***D77CBB.1D025660]
@.***D77CBB.1D025660]
Thanks!
-cg 😊
Carol Garcha
Support Escalation Engineer
Azure Rapid Response – Web Apps
+1<PHONE_NUMBER>
Working Hours: M-F 8:00 am-5:00 pm US CT
Need help outside of my working hours?
Locate an engineer<EMAIL_ADDRESS>Manager: Gail Heimann /<EMAIL_ADDRESS>@.***D77CBB.1D025660]
-------------------------------------------- 😊 --------------------------------------------
The Ultimate Guide to Running Healthy Apps in the Cloud
https://azure.github.io/AppService/2020/05/15/Robust-Apps-for-the-cloud.html
-------------------------------------------- 😊 --------------------------------------------
From: Xing Zhou @.>
Sent: Monday, July 12, 2021 4:18 AM
To: Azure/azure-cli @.>
Cc: Carol Garcha @.>; Mention @.>
Subject: Re: [Azure/azure-cli] Please add this as an example (#18341)
az resource create --resource-group "[resource-group]" --resource-type "Microsoft.Web/sites/siteextensions" --name "[sitename+slot]/siteextensions/Contrast.NetCore.Azure.SiteExtension" --api-version "2018-02-01" --is-full-object --properties '{"id":"Contrast.NetCore.Azure.SiteExtension", "location":"[YourRegion]", "version": "1.9.0"}'
@carolgahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcarolga&data=04|01|carol.garcha%40microsoft.com|ee997bfe149a4c22899d08d94516009a|72f988bf86f141af91ab2d7cd011db47|1|0|637616783087969549|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=NvXBHBmLETJhcbXCy3bRwFCuv7I5sAmTcKRrQbN7Mio%3D&reserved=0 Hi, may I ask what is the specific scenario that this example wants to explain?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-cli%2Fissues%2F18341%23issuecomment-878114944&data=04|01|carol.garcha%40microsoft.com|ee997bfe149a4c22899d08d94516009a|72f988bf86f141af91ab2d7cd011db47|1|0|637616783087979543|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=xU9RGESkftKHcuPerKaYg4jYQwfULAWZcWnFU1spe50%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAQE4DFHS5MMHBROFRNE3MGLTXKXOBANCNFSM4574Q2ZA&data=04|01|carol.garcha%40microsoft.com|ee997bfe149a4c22899d08d94516009a|72f988bf86f141af91ab2d7cd011db47|1|0|637616783087979543|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=J9by5YrNTuL79PXndDVUtfRxtwbRq97l2UUz5jQwjcY%3D&reserved=0.


module/polls

closes  #39
created poll command(module), added to index.js. At this point is understands the poll create syntax and creates a poll object, sending in back as a message

lint

Still have questions about using i18n while iterating an unknown amount of answers in response, when displaying info about a poll

still have to implement vote by text or id feature, and that should do it

today's list:

[x] implement moment js
[ ] fix can vote for anything bug
[ ] vote must understand both id and text
[ ] votes through messages monitoring
[ ] create ru locale .csv

[ ] create ticket for bug in polls
[ ] rename variables


How to start ?

In situations where documentation is extremely scarce .
I try to build environment via http://athenax.readthedocs.io/en/latest/getting_started
But can't find the com. Foo. MyCatalogProvider, I don't find this class, also does not have the detailed case can refer to .
I think detailed documentation is required for open source projects.
thank you

you are absolutely right. We are actually moving to Flink 1.5 TableSourceFactory approach as of now. many of our users do find this very confusing

close as duplicate of https://github.com/uber/AthenaX/issues/4


Improve UI

hi... i would like to work on the CSS of this project.
https://aniket1104.github.io/Frontend_templates/weather_webpage/main.html
this is the last project i have worked on.

Hi @aniket1104 are you willing to add this project in my repo?

Ok go ahead


Error in post-command-hook (selectrum--update)

When I'm calling M-x I'm getting the following error:
Error in post-command-hook (selectrum--update): (error "Invalid version syntax: ‘lsp-mode 7.0.1’ (must start with a number)")

It doesn't look related to lsp, as when I'm disabling it, I'm getting the same error with another package.
It looks like all other selectrum/consult/system commands works fine, except for M-x
I've tried to enable toggle debug on error, but it doesn't catch anything.
This is my config:
(use-package selectrum
  :config
  (setq selectrum-max-window-height 17)
  (selectrum-mode 1))

(use-package selectrum-prescient
  :after selectrum
  :config
  (selectrum-prescient-mode 1))

(use-package consult
  :hook (completion-list-mode . consult-preview-at-point-mode)
  :init
  (setq consult-find-command "fd --color=never --full-path ARG OPTS")
  (setq consult-async-refresh-delay 0.3)
  ;; Use Consult to select xref locations with preview
  (setq xref-show-xrefs-function #'consult-xref
        xref-show-definitions-function #'consult-xref)
  :config
  ;; (setq consult-preview-key (list (kbd "<S-down>") (kbd "<S-up>")))
  (setq consult-narrow-key "<")

Emacs version:
GNU Emacs 28.0.50 (build 1, x86_64-apple-darwin20.4.0, NS appkit-2022.44 Version 11.3.1 (Build 20E241)) of 2021-05-13

Thanks

This is an Emacs 28 bug, see https://debbugs.gnu.org/cgi/bugreport.cgi?bug=48404. If you upgrade your Emacs to a newer version the bug should be gone.


fix(CLI): move plugin logic to Root and pass clap error if plugin's name is close to a built-in subcommand

fixes #866
What
[TODO: Short statement about what is changing.]
Why
[TODO: Why this change is being made. Include any context required to understand the why.]
Known limitations
[TODO or N/A]

Seems like the no_path test is failing now

@tsachiherman Testing no path was difficult because unix requires it. However, I was able to test it on windows that if the path is just the plugin bin directory, it still works. But for unixes I added a failure test for if the path doesn't include the plugin.