command 'vscode-samples.wasm-component-model.run' not found

Extension sample
wasm-component-model
VS Code version
1.94.2 384ff7382de624fb94dbaf6da11977bba1ecd427 arm64
What went wrong?
To reproduce this issue just clone the repo
npm install on vscode-extension-samples/wasm-component-model
then
npm run build
then npm run serve
visit vscode.dev
install extension extension from location
type: https://localhost:5000
press CMD + SHIFT + P
type Samples: Run Calc Service
it should have output:
Running calculator example
Add 3
Sub 2
Mul 21
Div 5
Division by zero not allowed

but got error see below screenshot

Did you run npm run esbuild as mentioned in the readme?

yes
Uriah Galang
On Wed, Oct 30, 2024 at 16:44 Dirk Bäumer @.***> wrote:

Did you run npm run esbuild as mentioned in the readme?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-extension-samples/issues/1120#issuecomment-2446201600,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG33KMUZS3WJSLTIPHNMV3LZ6CL5XAVCNFSM6AAAAABQZWVQ7KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBWGIYDCNRQGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Mediapipe error in hand tracking

I was using the mediapipe hand tracking and noticed two instances where the estimated motion doesn't match the actual motion. Any idea on what causes this? What can I do to get better results?
Instance 1: https://youtu.be/-BFybUdPpK0
Instance 2: https://youtu.be/KNZbXx9hPzo

Hi @EigenSpiral,  Which platform are you referring the above. Thanks!

Hi, what do you mean by platform? The youtube videos show the mediapipe tracking of the hands, but as shown in the above clips it is not matching the actual motion of the hand -- while the finger is folding mediapipe is showing a straight finger

@EigenSpiral, Is it implemented through python, javascript or others? .Could you please help me in reproducing the same with complete steps at our end. Thanks!


ND4J: Remove Nd4j.trueScalar/trueVector

What changes were proposed in this pull request?
Fix eclipse#8087
How was this patch tested?
Code compiles and unit test run with same results as SkymindIO/master.

Merged after DM on slack.


Add global imagePullSecrets setting

Add support for a global imagePullSecrets setting to allow all images and khchecks to pull from private registries using an externally created secret.
This can be helpful for #1006

Noting that this PR supplements my PR (#1082) to pass imagePullSecrets to child containers of the deployment check nicely, which is also waiting for review.

@integrii  any chance that you could review? Thanks.

@thebridge90 there were build fixes in master.  Can you merge the latest master and push it to your branch please?  That should make builds pass on this branch...

@thebridge90 there were build fixes in master. Can you merge the latest master and push it to your branch please? That should make builds pass on this branch...

Merged latest master. Thanks.


Return X509_CRLs from PKCS12_parse

The PKCS12_parse function should support returning a stack of X509_CRLs for PKCS12 files that contain CRL bags.
https://tools.ietf.org/html/rfc7292#section-4.2.4
Proposed Function Prototype:
PKCS12_parse(PKCS12 *p12, const char *pass, EVP_PKEY **pkey, X509 **cert, STACK_OF(X509) **ca, STACK_OF(X509_CRL)**crl);

Marking as inactive, to be closed at the end of 3.4 dev barring further input


Cherrypick RebatchDataset performance fix

[tf.data] Add a new RebatchDatasetV2 op that does rebatching (instead of rebatching via graph rewrites) for performance and correctness.

PiperOrigin-RevId: 268544896

Note that this changes the behavior of some tf.data.Dataset + distribution strategy code; as such, it may break things that rely on the old (less correct) behavior. I'm not sure what all code exists in 1.15 that this might affect, but thought I should give a heads up, given @tfboyd's comment here:
https://github.com/tensorflow/tensorflow/pull/32245#issuecomment-536658498

Will defer to @goldiegadde as to whether this should be cherry picked.


Queue doesn't work on iOS

When the app is in background the queue stop executing when the current episode ends.

Thanks for bringing this to my attention.

This has been fixed in the 1.3.2 release.


Chart Editor Additions/Fixes

Adds a key count variable into the charter, and swaps out the necessary numbers for it to work properly with different key counts. Also adds 2 new buttons in the "View" drop down to increase/decrease the grid width / key count

Made some changes to how icons on strumlines are positioned/scaled to fix issues with too many characters on one strumline,
This is what it used to look like

This is what it looks like now

Also added the ability to scroll on large drop down menus, mainly to fix a bug with having too many note types breaking the menu
https://github.com/user-attachments/assets/003c69c9-4bf2-4dfe-be1b-4f8135aaf53c

i might marry you

what i'm really going to want is the ability to change key count mid song, and for the editor to account for that.

he is  c o o k i n g

what i'm really going to want is the ability to change key count mid song, and for the chart editor to account for that by changing width of available note slots horizontally.

@TheZoroForce240  think that can happen? an event to change keycount midsong, and for the editor to account for that?

not happening, we are not gonna support keycount changes midsong, if people want that they will have to softcode it

not happening, we are not gonna support keycount changes midsong, if people want that they will have to softcode it

well will the editor at least be more softcoded so that more edits can be made to it?

not happening, we are not gonna support keycount changes midsong, if people want that they will have to softcode it

well will the editor at least be more softcoded so that more edits can be made to it?

we will see

Any progress on this..?

Its been merged internally

well will the editor at least be more softcoded so that more edits can be made to it?

we will see

huh
well, i never really thought of that, but it would genuinely be awesome if this were the case
i don't wanna force anything though, you guys get to decide on that
after all, it's not my engine


Cloudflare bypass?

How to bypass piratesbay cloudflare protection with this module? I see a lot of cloudflare bypassing modules but not sure how to integrate them with thepiratebay. Or should I just use 'Parser' part, executing queries by myself?
Asking because here is what I'm getting on attempt to query for recent torrents:  https://gist.github.com/ElderOrb/6e54c83714f2bd9e201c3e36913284d3

This is creating errors.

You may skip this using a tor proxy.


HassGetWeather first draft

Since it was mentioned in Chapter 4, I don't see why not :D

I see you are using the forecast attribute, which is depreciated. So this will not work in 2024.3 anymore

I am aware it's deprecated and I've tried another way around, but I haven't been able to do so.
It's not an entity state per se, it's whatever data the intent handler in HA decides to send back to compose a response. As such, the handler could pass the forecast as an attribute or as something else, although I'm not sure how to define that data in fixtures and access it in responses

Maybe there should be 2 intents: one for the current state and one for the forecast. From an implementation standpoint, they do differ very much.


React optimization

I fixed the react component lifecycles, the entire page loads twice on page load and only updates once when necessary. You don't need to test the lifecycles, just make sure nothing is broken.

#434


Connect Disqus so we are notified of comments on posts

Disqus is connected to coeisg<EMAIL_ADDRESS>and we aren't getting notifications of new comments on posts. We need to see them!

Correction: Disqus is currently associated with tdpcoe<EMAIL_ADDRESS>

Created a group coe-isg-grp<EMAIL_ADDRESS>created a filter in tdpcoe<EMAIL_ADDRESS>to fwd all disqus notification messages to group. Tested, works!


Add support for specifying a namespace for the resource to be created in

Description
Creation of resources in other namespaces was not possible. This PR adds a new optional property namespace to be able to specify a specific target namespace.
Fixes #55
Type of change
Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

Environment

Based on comment https://github.com/KohlsTechnology/eunomia/issues/55#issuecomment-505649886 from @sanbornick we will need to discuss this further before merging.

I think I had must have had something misconfigured last time I tried this. I got it working now with the existing functionality. Let me close this issue.


Use gRPC to communicate data from app host to dashboard

Includes PR #1415, with feedback from that PR addressed here.
This is another step towards #1003. Ultimately the dashboard will run in a separate process to the app host. That will require a network connection between the processes for data.
This PR splits the front and back end to use separate types, with a gRPC channel between them.
The .proto defined in #1274 is used here, with some modifications following the integration.
Microsoft Reviewers: Open in CodeFlow

@JamesNK PTAL

I got your branch and ran the app. Project's aren't displaying PID or project file on resources page:

Projects aren't displaying a PID or project file on resources page

Fixed:

Excellent work everyone!


Plotter background image not working when N>3

It may just be my inexperience, but I am unable to get a background image to work properly for a plotter when N is greater than 3 or if the plotter shape is more than 1 row. I plan to eventually use the plotter to randomly place an actor on top of the image and save a screenshot so the ability to have more than one row is a major plus.
The below code will produce the desired output of the background image (N is less than 3).

from vtkplotter import *

vp = Plotter(N=2, axes=0, size=(600,800), bg=datadir+"images/tropical.jpg")

vp.show(interactive=1)

However, after running the following code, you see that rows of the plotter just turn black instead of displaying the background image.

from vtkplotter import *

vp = Plotter(N=9, axes=0, size=(600,800), bg=datadir+"images/tropical.jpg")

vp.show(interactive=1)

Any help is greatly appreciated!

Hi @ebc0007
this should be fixed in the latest commit, try:
git clone https://github.com/marcomusy/vtkplotter.git
cd vtkplotter/examples/basic
python bgImage.py

note that you can also use Plotter(shape=(3,4), ..) to define the window geometry.

Thanks for such a quick response!


Compile user_dir for all Unix & Redox targets

This change broadens the list of targets which will conditionally
compile the user_dir and user_dirs functions. Prior to this change,
only the Linux and Redox OS targets will compile an implementation
meaning that other Unix derivatives such as Android, FreeBSD, NetBSD,
Darwin, etc. would not have a compiled implementation of these
functions. Once paired and consumed by the upstream dirs crate this
would lead to a compilation failure on these "extra" targets. This
change allows all Unix family targets in addition to the Redox OS target
to compile the same implementation.
Closes #1
Signed-off-by: Fletcher Nichol<EMAIL_ADDRESS>

Thank you!
Fixed in https://github.com/soc/dirs-sys-rs/commit/51b0e46b89a76abf9ba9b2551f369a009927f11b, I credited you as the author, hope that's fine.


includes several fixes

performance fix #10
empty string crash fix
code simplification #12

Hi @nitehogg
Could you review the PR?
Thanks)


Fix google tag manager

thanks to @stephanpavlovic

@stephanpavlovic what was the final result of your test? did it work for you?


How to freeze/function_stop; in midSong?

Describe your problem here.
I wanna freeze song when i press the button
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

Look on how the PauseMenuSubstate class works


Improve the footer

Is your feature request related to a problem? Please describe.
There is a footer on some pages and not on some others. I am not sure that the footer is helpful.
Describe the solution you'd like
Do we need a footer ? If yes to show what ? (not sure the github logo is really helpful there) How to show it ? (Sticky footer ?)

Usually, legal notices, privacy and CGU are linked in the footer. I agree that big github logo is not really helpful for people who want to sign or create petitions.
Next question is, if we add legal notices and CGU (which are required), how could they be updated by admin of the pytition instance ?

I would allow admin to set the content of those pages via an HTML file path that can be set in settings.
Maybe we can provide default (with blanks to fill? or generic ?) ones also.

You would use a static HTML page, or a django HTML template to keep header and footer ?

Hmmm I would use a Django template that would inherit from the base one, to have the less possible boilerplate code in it. Just the "real content".
Provide a default one.
Let users provide their own in a variable in settings.
Or any other idea?

What has been done:
No footer at all by default.
If administrator wants a footer with GDPR / TOS / legal notice links, (s)he can set "TEMPLATE_FOOTER" variable in settings to a template path containing the footer template.
For the petition page, footer is configurable by the petition owner.


Create grouping terms for histone-specific histone deacetylase activity

'histone H3K14 deacetylase activity'
'histone H3K4 deacetylase activity'
'histone H3K9 deacetylase activity'
->> Need a parent 'histone H3K deacetylase activity'
'histone H4K12 deacetylase activity'
'histone H4K16 deacetylase activity'
->> Need a parent 'histone H4K deacetylase activity'
PMID:12590135
@RLovering

+[Term]
+id: GO:0141050
+name: histone H3K deacetylase activity
+namespace: molecular_function
+def: "Catalysis of the reaction: histone H3 N6-acetyl-L-lysine + H2O = histone L-lysine + acetate. This reaction represents the removal of an acetyl group from a histone H3." [PMID:12590135]
+is_a: GO:0004407 ! histone deacetylase activity
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25508" xsd:anyURI
+created_by: pg
+creation_date: 2023-06-07T09:13:49Z
+
+[Term]
+id: GO:0141051
+name: histone H4K deacetylase activity
+namespace: molecular_function
+def: "Catalysis of the reaction: histone H3 N6-acetyl-L-lysine + H2O = histone L-lysine + acetate. This reaction represents the removal of an acetyl group from a histone H3." [PMID:12590135]
+is_a: GO:0004407 ! histone deacetylase activity
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25508" xsd:anyURI
+created_by: pg
+creation_date: 2023-06-07T09:15:53Z

+[Term]
+id: GO:0141052
+name: histone H3 demethylase activity
+namespace: molecular_function
+def: "Catalysis of the removal of a methyl group from a modified lysine residue of the histone H3 protein. This is a dioxygenase reaction that is dependent on Fe(II) and 2-oxoglutarate." [] {comment="PMID:17947579"}
+is_a: GO:0032452 ! histone demethylase activity
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25508" xsd:anyURI
+created_by: pg
+creation_date: 2023-06-07T09:22:57Z
+
+[Term]
+id: GO:0141053
+name: histone H2A ubiquitin ligase activity
+namespace: molecular_function
+def: "Catalysis of the transfer of ubiquitin to a histone H2A substrate." [PMID:25303536]
+is_a: GO:0140852 ! histone ubiquitin ligase activity
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25508" xsd:anyURI
+created_by: pg
+creation_date: 2023-06-07T09:27:23Z
+
+[Term]
+id: GO:0141054
+name: histone H2B ubiquitin ligase activity
+namespace: molecular_function
+def: "Catalysis of the transfer of ubiquitin to a histone H2B substrate." [PMID:25303536]
+is_a: GO:0140852 ! histone ubiquitin ligase activity
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25508" xsd:anyURI
+created_by: pg
+creation_date: 2023-06-07T09:33:02Z
+[Term]
+id: GO:0141055
+name: histone H3 ubiquitin ligase activity
+namespace: molecular_function
+def: "Catalysis of the transfer of ubiquitin to a histone H3 substrate." [PMID:25303536]
+is_a: GO:0140852 ! histone ubiquitin ligase activity
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25508" xsd:anyURI
+created_by: pg
+creation_date: 2023-06-07T09:33:34Z
+
+[Term]
+id: GO:0141056
+name: histone H4 ubiquitin ligase activity
+namespace: molecular_function
+def: "Catalysis of the transfer of ubiquitin to a histone H4 substrate." [PMID:25303536]
+is_a: GO:0140852 ! histone ubiquitin ligase activity
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25508" xsd:anyURI
+created_by: pg
+creation_date: 2023-06-07T09:34:00Z
+
+[Term]
+id: GO:0141057
+name: histone H3 arginine deiminase activity
+namespace: molecular_function
+def: "Catalysis of the reaction: H2O + histone H3 L-arginyl = histone H3 L-citrullyl + NH4+, resulting in histone H3 citrullination." [PMID:25303536]
+is_a: GO:0140794 ! histone arginine deiminase activity
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25508" xsd:anyURI
+created_by: pg
+creation_date: 2023-06-07T09:35:46Z

+[Term]
+id: GO:0141058
+name: histone H4 demethylase activity
+namespace: molecular_function
+def: "Catalysis of the removal of a methyl group from a modified lysine residue of the histone 4 protein. This is a dioxygenase reaction that is dependent on Fe(II) and 2-oxoglutarate." [] {comment="PMID:17947579"}
+is_a: GO:0032452 ! histone demethylase activity
+property_value: term_tracker_item "https://github.com/geneontology/go-ontology/issues/25508" xsd:anyURI
+created_by: pg
+creation_date: 2023-06-07T09:47:52Z


Missing option to convert Python script to Jupyter notebook.

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:

Version: 1.78.2 (Universal)
Commit: b3e4e68a0bc097f0ae7907b217c1119af9e03435
Date: 2023-05-10T14:44:45.204Z

OS Version: Darwin arm64 22.2.0

Steps to Reproduce:

Open the command palette (Cmd + Shift + P)
Type 'Export'

I'm just following the instruction here. This option existed in previous versions of VSCode but it's now missing.

@xquyvu Thank you for filing this issue, looks like the Jupyter extension is either not installed or has failed to activate.
Please could you check your developer logs to see whether the extension has failed to activate

Open the command palette and select the command Toggle Developer Tools
Check if there are any errors there.

Thank you
Please could you open a python file and then  check the logs again

I've just tried again now:

Oh and it seems I can convert notebooks to python scripts just fine.

Thank you for getting back to us
Will close this issue as it’s resolved
Please feel free to create a new issue if you run into other issues

Sorry it's not resolved. I can convert notebooks to python scripts, but not the other way around 😬


typo: manully -> manually

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

MicrosoftCollaboratePortal/troubleshooting.md
:white_check_mark:Succeeded

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


Added non-changeable options to rke2-cluster-configuration

Description
This PR adds a notice about non-changeable options with the Rancher RKE2 provisioning. Users can be confused if they add supported RKE2 options to a Rancher cluster config which afterwards aren't reflected in the provisioning process.
data-dir for example is such an options that is non-changeable according to RKE2 devs: https://rancher-users.slack.com/archives/C3ASABBD1/p1704389340347459?thread_ts=1704376260.746929&cid=C3ASABBD1
For this option a new paragraph is added that describes that this option will always stay default regardless of the configured value.

@btat - thanks for the review! I added you suggestions.
Maybe we can ping @brandond on a completeness check here? I'm not sure if there are more options that can't be changed when deploying via Rancher?

I don't know what all isn't supported for modification by Rancher. On the RKE2 side, anything that has an option can be configured, it is Rancher that imposes most of the limitations on supported configurations.

@brandond - thanks for the feedback!
@btat - maybe you know someone from the Rancher team that can check this for completeness? Otherwise I'm fine with it been merge like that of course.

@danielhass I'll go ahead and merge this PR and will add a an issue to our backlog about identifying other similar options.

@danielhass I would probably defer to someone from the hostbusters team on that?


fix errors if directories with spaces is provided for 'useAPI' mode

example:
good: C:\Workspace
bad: C:\Workspace WIth Spaces\
simple fix by wrapping directories with aprostophes

Thank you for the contribution. I chose to do the same thing differently, now implemented. Closing the PR.


Missing information

When I go to the Microsoft Search in Bing page, it shows me that Microsoft Search in Bing is now availalble, but there is not a Location tab to click on . HOw can I get this fixed?

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

ID: 96809b75-c20f-bfcf-9a69-7793f51172bf
Version Independent ID: 48f803b7-3759-f040-895f-45e1b6559768
Content: Make content easy to find with Microsoft Search
Content Source: MicrosoftSearch/make-content-easy-to-find.md
Service: mssearch
GitHub Login: @adefowler
Microsoft Alias: anfowler

Hi Dean,
I think we got your fixed now, correct? If not, please follow-up up with me in the Search Forum on Tech Comm.
Cheers,
-Wendy


Validation of the configured feature gates of a shoot cluster and its k8s version

How to categorize this issue?

/area control-plane ops-productivity
/kind enhancement
/priority normal
What would you like to be added:
There should be a validation checking that the kubernetes version of a shoot cluster is compliant with the configured feature gates of the kubernetes API server, kubernetes controller manager, kubelet, kubernetes scheduler, kube-proxy. The cloud controller manager also supports custom feature gates but this validation should be executed by each provider extension, however the gardener extensions library can be enhanced with such generalized feature.
Why is this needed:
To avoid control plane components crashing with unknown feature gates. See this kube-apiserver logs for example:
Error: invalid argument "CustomResourceWebhookConversion=true,CSIMigration=true,CSIMigrationAWS=true" for "--feature-gates" flag: unrecognized feature gate: CustomResourceWebhookConversion

ℹ We have never done this on purpose (prevent the maintenance effort of duplicating all possible feature gates in our code base).

This seems to become problematic with forceful K8s version upgrades.

In a discussion round with @gardener/gardener-maintainers we decided to not introduce this validation with the main argument of @timuthy in https://github.com/gardener/gardener/issues/3140#issuecomment-724161061.
When a user configures invalid/non-existent feature gate then the logging stack can help him identify why his kube-apiserver is not starting up. All of this is only getting problematic when such a shoot is deleted because the spec is immutable after the shoot has a deletion timestamp, i.e., invalid feature gate configuration cannot be self-corrected by the end-user, hence, this results in ops effort.
We talked about options to not respect the feature gate configuration of the end-user (or, more general, any custom configuration at all) during shoot deletion, but this should probably be a conscious decision as feature gate (or other custom configuration) might change the cluster behaviour and could theoretically lead to orphaned resources. Still, there should probably be such an option, but we leave it to #3110 to tackle such scenarios and won't implement any custom logic for the feature gates now.
/close


Using InsertCols with formulas to the right breaks the workbook

Description
Using InsertCols with formulas to the right of the insert breaks the workbook if the formulas reference a column to the left of the insert.
Steps to reproduce the issue:

Create a workbook with a sheet that contains formulas in column C. The formulas were copied by dragging from the top. The formulas reference column A e.g. =A1 * 5.
Insert a column between A and C, using InsertCols e.g. xl.InsertCols("Sheet1", "B", 1)`
Save the workbook xl.SaveAs("test.xlsx")
Open the workbook in Excel

Describe the results you received:
An error saying that the workbook has been repaired (or in other versions of Excel a dialog suggesting the workbook should be repaired) with the following extra information:

Describe the results you expected:
Workbook opens with no error reported
Output of go version:
go version go1.20.2 linux/amd64

Excelize version or commit ID:
v2.7.1

Environment details (OS, Microsoft Excel™ version, physical, etc.):
Ubuntu 22.04

Thanks for your issue. This issue has been fix by pull request #1567, please try to upgrade the master branch code, and this patch will be released in the next version.


Error is raised only if the first dataset is the one containing an error

When I execute multiple statements, and there is an error in another dataset than the first, no exception is raised.
To reproduce this on MS SQL,

create a table containing a column of type int. (e.g my_table)
Connect and execute this this

statement ='''INSERT INTO eu_modeldb_l.ship_tracking.overflow_test VALUES (1);
INSERT INTO eu_modeldb_l.ship_tracking.overflow_test VALUES (2);
INSERT INTO eu_modeldb_l.ship_tracking.overflow_test VALUES<PHONE_NUMBER>00);'''
result = cursor.execute(statement)

The last statement is invalid and should raise the following error
DataError: ('22003', '[22003] [DataDirect][ODBC SQL Server Wire Protocol driver][Microsoft SQL Server]Arithmetic overflow error converting expression to data type int. (8115) (SQLExecDirectW)')

But no error is raised.
Now, if the statements would have occured in a different order, with the last statement first, the error above is raised
statement ='''INSERT INTO eu_modeldb_l.ship_tracking.overflow_test VALUES<PHONE_NUMBER>00);
INSERT INTO eu_modeldb_l.ship_tracking.overflow_test VALUES (2);
INSERT INTO eu_modeldb_l.ship_tracking.overflow_test VALUES (1);'''
result = cursor.execute(statement)

The error is reproduced in pyodbc 3.0.10 on a linux machine (using an anaconda environment)

I suspect that
statement ='''SET NOCOUNT ON;
INSERT INTO eu_modeldb_l.ship_tracking.overflow_test VALUES (1);
INSERT INTO eu_modeldb_l.ship_tracking.overflow_test VALUES (2);
INSERT INTO eu_modeldb_l.ship_tracking.overflow_test VALUES<PHONE_NUMBER>00);'''

would avoid the issue.

gordthompson is correct.  It is supposed to work like that so you can retrieve the number of updates (rowcount) for each statement, etc.


segmentation fault with broken jpeg

this tiny scripts crashes the node process both on ubuntu 14.04 and osx 10.9.5, both with libvips 7.42.1:
https://gist.github.com/bkw/5794006ac6e743a7e26e
vipsthumbnail cannot create a file from that source either, but it doesn't crash like sharp does.

It looks like the "JPEG datastream contains no image" error from libjpeg isn't correctly handled or bubbled up. This condition can be reached when end-of-file (or Buffer in this case) occurs when reading image metadata.
An extra NULL reference check in sharp's image loading code should fix this - leave it with me - thanks for reporting.
Do you know of any IP/legal reasons that would prevent me adding the truncated/corrupted 02247503-02.jpg file to sharp's test fixtures to prevent such a problem occurring again?

thanks for the quick response, lovell!
I have no idea wether there are any legal issues with copying that corrupt image, I'm neither working for them nor a lawyer. I doubt anybody would care or even notice.

This problem should now be fixed on the intake branch.
This will be included in the forthcoming v0.9.0 release. You can test this beforehand using:
npm install lovell/sharp#intake

I created an image with corrupt header for the tests via head -c 1024 good.jpg >bad.jpg

most excellent. I can confirm it works as expected for my usecase. Thanks a bunch!


Great blog post!

Just found and read your recent blog post. I love the level of detail, the clear diagrams and the deep dive into PIO (with the cool animation).
Thank you!

Wow thanks Uri! Funnily enough that blog post would never have manifested without your amazing RP2040 hackaday series. It got me started on my PIO journey :smile:!


Create a wrapper structure for different neurons and create a library for these

A simple library of differential equation based on different neuron models, as used in brian2 is provided here:
https://brian2.readthedocs.io/en/stable/introduction/brian1_to_2/library.html?highlight=izhikevich#neuron-models

Neuron models to do:

[ ] Perfect integrator

[ ] Leaky integrate-and-fire neuron

[ ] FitzHugh-Nagumo-Modell


PINTPulsar does not check for coordinate units

I am trying to read in non-nanograv and non-PTA data, where the position of the pulsar is given in equatorial coordinates (as opposed to ecliptic coordinates used in nanograv), where RA is in units of hhmmss.
Then enterprise pulsar object does not check for units, assuming they are supplied in radians, which results in an incorrect position used for these pulsars.

facepalm

Is this a PINT issue or enterprise? If PINT has these as astropy Quantity values with units, can you propose code to fix the problem?

This is fixed by #370.
However, note that we do need to pay more attention to units between tempo2 and PINT. The units of the designmatrix are not compatible yet, and it's not easy to determine the units of the tempo2 designmatrix in general. PINT does a good job of tracking units. In tempo2, the units of the designmatrix unfortunately seem to not all be equal to the corresponding units of the designmatrix (though I'd like to check this more).
I had difficulty matching the PMRA and PMDEC units between PINT and tempo2. The other astrometry parameters I managed.


ImportError: No module named magenta.models.sketch_rnn.sketch_rnn_train

I created a python file in ~/magenta/magenta/models/sketch_rnn named test.py, and there was a sentence in test.py:
from magenta.models.sketch_rnn.sketch_rnn_train import *
then I got:
Traceback (most recent call last):
File "", line 1, in
ImportError: No module named magenta.models.sketch_rnn.sketch_rnn_train
how to solve this problem?

@QianhuiWu, to import sketch_rnn_train, you'll either need to install the magenta pip package and import it as a system library, or you'll need to use our development environment and set up a new target for your test.py in the BUILD file and build it with bazel.

Thank you so much! @cghawthorne
I made it by installing the magenta pip package ~


fix: introduce ability to pick a free or paid tier of QnA

Description
Introduces an optional choice of pricing tier for the ManageService widget. This is then plumbed through for the QNA maker version of this to offer a free or paid tier for the underlying QNA services
Task Item
Fixes #6866
Screenshots

Coverage decreased (-0.02%) to 50.913% when pulling 5dbf31670e0817bac88adc19c7f2169f9dfe827b on benbrown/qnatiers into 1ec39e29d640a4906e2982cc3312fac07a6e288e on main.


werkzeug.exceptions.BadRequest: 400 Bad Request: The browser (or proxy) sent a request that this server could not understand.

I am trying to run this code segment
from flask import Flask,request
@app.route("/my_end_point",methods=['GET', 'POST', 'PUT', 'DELETE'])
def myFunctionName():
    if request.method == 'POST':
        body = request.get_json()

And I am calling the endpoint by POST method
But I am getting these errors at body = request.get_json()
werkzeug.exceptions.BadRequest: 400 Bad Request: The browser (or proxy) sent a request that this server could not understand.

Environment:
-OS version : Ubuntu 18.04.6 LTS

Python version: Python 3.9.13
Flask versions:
Flask==2.0.3
Flask-Cors==3.0.3
Werkzeug==2.1.2

Please use Stack Overflow for questions about your own code. This tracker is for issues related to the project itself. Be sure to include a minimal, complete, and verifiable example.


[BUG] should set backing image minNumberOfCopies to 1 when upgrading Longhorn

Describe the bug
When upgrading Longhorn to v1.7.x
The BackingImage will have minNumberOfCopies = 0
Need to set the default value in upgrade path.
There is no impact if the minNumberOfCopies is 0

when clean up unused backingimage, we set the minNumberOfCopies to 1 if it is 0
https://github.com/longhorn/longhorn-manager/blob/master/controller/node_controller.go#L1403
when replenish backing image, there is no way nonEvictingCount < bi.Spec.MinNumberOfCopies, so it won't replenish backing image if MinNumberOfCopies = 0. Thus it is the same behavior as MinNumberOfCopies=1
https://github.com/longhorn/longhorn-manager/blob/master/controller/backing_image_controller.go#L364

To Reproduce
.
Expected behavior
.
Support bundle for troubleshooting
.
Environment
.
Additional context
Thanks to @WebberHuang1118 's report
cc @WebberHuang1118
Workaround and Mitigation
.

Verified pass on longhorn v1.8.0-dev-20240908(https://github.com/longhorn/longhorn-manager/commit/68a4591905469a5e2c1087c2ba60e60fcfae70b1)
Tested in below steps because it is not allowed to upgrade from v1.6.3 to v1.8.0-dev:

Create backingimage with minNumberOfCopies to 0 and 3 in v1.7.1 then upgrade to v1.8.0-dev-20240908, after upgrade complete minNumberOfCopies not hanged.


A question

hey, if I want to embed the stn in a new net structure,how should I define the loss?Or Should I do that? @kevinzakka

@Sakuralala it is not needed. The paper has mentioned that there is no need for extra supervision.


Rocksdb Block Storage

Description of the Change
Implement RocksDB BlockStorage class

Benefits

Possible Drawbacks

Usage Examples or Tests [optional]

Alternate Designs [optional]

@MBoldyrev @lebdron This is a draft of the RocksDB block storage implementation. Adding tests for the class now.

@MBoldyrev @lebdron Please look and verify the "fetch" function.

Also, check that all commits are signed off.

Also, check that all commits are signed off.

I'll check and squash the commits into one

@lebdron comments were noted and pull request sent.

Similar things are implemented in #1084


Fixed bug where GeoJSON sources did not parse WFS features.

In the changed line, oSource.readFeatures is a function that does not exist.  It should be format.readFeatures. This fix will allow users to use the JSONP layer format.

Cool, could you rebase your branch to resolve the conflicts?
I'm happy to merge it in then. Also, make sure to follow the commit message guidelines from our contribution guidelines. It's important as we use it to automatically generate a changelog.
So in your case it'd be
fix(olHelpers): solve bug where GeoJSON....

Merged.


Custom feed card name retained after deleting the pending card and readding new

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @joekaufmanexpensify
Slack conversation (hyperlinked to channel name): expense
Action Performed:
Prerequisite: User added a company card and in pending state

Navigate to Company card
Click Settings > Remove card feed
Add a card again by custom feed

Expected Result:
A new feed of the same type not to retain the old feed
Actual Result:
Custom feed card name retained after deleting the pending card and readding new
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Standalone
[ ] Android: HybridApp
[ ] Android: mWeb Chrome
[ ] iOS: Standalone
[ ] iOS: HybridApp
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/1e71f1b8-37af-4a1c-9f4a-33df8b21aa94
View all open jobs on GitHub

Is this assigned to @mountiny because he will fix it, or can I make this external? cc @joekaufmanexpensify.

Do we need a C+ for review?

This is just backend fix

TY!

PR is up https://github.com/Expensify/Auth/pull/13612

We can close this one now


flash on update

Ive noticed that when adaptive lighting changes my lights settings, there is a fraction of a second where it flashes with a cold white before changing to the set white level. it is as the brightness update command is sent first which resets the color temp and then in the next instant the color is updated. This is particularly visible when the lights are updating to a dim warm colour.
I only have the 'take over control' checkbox ticked in the config settings

Please read the instructions here https://github.com/basnijholt/adaptive-lighting#having-problems

brightness dosnt change, just the colour flashes cold white before setting to the warm white. I tried the setting which seperates brightness and colour commands however my lights kept resetting when I tried that.
A couple of minutes of the log:
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: '_update_attrs_and_maybe_adapt_lights' called with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Adaptive Lighting: Sunlights: '_adapt_lights(['light.lr2', 'light.su', 'light.sl', 'light.dr', 'light.ba', 'light.lr'], None, force=False, context.id=adapt_lgt_fe0d_interval_46)' called
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr2', 'brightness': 52, 'white_value': 52, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.sl', 'brightness': 52, 'white_value': 52, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.dr', 'brightness': 52, 'white_value': 52, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr', 'brightness': 52, 'white_value': 52, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr2']')' event with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.sl']')' event with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.dr']')' event with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr']')' event with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.lr2' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 51, 'color_temp': 500, 'white_value': 54, 'effect': '4', 'friendly_name': 'LR2', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.lr2' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 51, 'color_temp': 500, 'white_value': 51, 'effect': '4', 'friendly_name': 'LR2', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] State change event of 'light.lr2' is already in 'self.last_state_change' (adapt_lgt_fe0d_interval_46) adding this state also
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.lr' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 51, 'color_temp': 500, 'white_value': 54, 'effect': '4', 'friendly_name': 'LR', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.lr' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 51, 'color_temp': 500, 'white_value': 51, 'effect': '4', 'friendly_name': 'LR', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] State change event of 'light.lr' is already in 'self.last_state_change' (adapt_lgt_fe0d_interval_46) adding this state also
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.sl' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 51, 'color_temp': 500, 'white_value': 54, 'effect': '4', 'friendly_name': 'SL', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.sl' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 51, 'color_temp': 500, 'white_value': 51, 'effect': '4', 'friendly_name': 'SL', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:47 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] State change event of 'light.sl' is already in 'self.last_state_change' (adapt_lgt_fe0d_interval_46) adding this state also
2020-11-23 23:15:48 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.dr' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 51, 'color_temp': 500, 'white_value': 54, 'effect': '0', 'friendly_name': 'DR', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:48 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.dr' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 51, 'color_temp': 500, 'white_value': 51, 'effect': '0', 'friendly_name': 'DR', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_46'
2020-11-23 23:15:48 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] State change event of 'light.dr' is already in 'self.last_state_change' (adapt_lgt_fe0d_interval_46) adding this state also
2020-11-23 23:16:03 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:16:27 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:16:51 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:17:13 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: '_update_attrs_and_maybe_adapt_lights' called with context.id='adapt_lgt_fe0d_interval_47'
2020-11-23 23:17:13 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Adaptive Lighting: Sunlights: '_adapt_lights(['light.lr2', 'light.su', 'light.sl', 'light.dr', 'light.ba', 'light.lr'], None, force=False, context.id=adapt_lgt_fe0d_interval_47)' called
2020-11-23 23:17:13 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr2', 'brightness': 51, 'white_value': 51, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_47'
2020-11-23 23:17:13 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.sl', 'brightness': 51, 'white_value': 51, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_47'
2020-11-23 23:17:13 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.dr', 'brightness': 51, 'white_value': 51, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_47'
2020-11-23 23:17:13 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr', 'brightness': 51, 'white_value': 51, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_47'
2020-11-23 23:17:13 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr2']')' event with context.id='adapt_lgt_fe0d_interval_47'
2020-11-23 23:17:13 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.sl']')' event with context.id='adapt_lgt_fe0d_interval_47'
2020-11-23 23:17:13 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.dr']')' event with context.id='adapt_lgt_fe0d_interval_47'
2020-11-23 23:17:13 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr']')' event with context.id='adapt_lgt_fe0d_interval_47'
2020-11-23 23:17:27 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:17:51 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:18:27 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:18:39 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: '_update_attrs_and_maybe_adapt_lights' called with context.id='adapt_lgt_fe0d_interval_48'
2020-11-23 23:18:39 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Adaptive Lighting: Sunlights: '_adapt_lights(['light.lr2', 'light.su', 'light.sl', 'light.dr', 'light.ba', 'light.lr'], None, force=False, context.id=adapt_lgt_fe0d_interval_48)' called
2020-11-23 23:18:39 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr2', 'brightness': 50, 'white_value': 50, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_48'
2020-11-23 23:18:39 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.sl', 'brightness': 50, 'white_value': 50, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_48'
2020-11-23 23:18:39 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.dr', 'brightness': 50, 'white_value': 50, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_48'
2020-11-23 23:18:39 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr', 'brightness': 50, 'white_value': 50, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_48'
2020-11-23 23:18:39 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr2']')' event with context.id='adapt_lgt_fe0d_interval_48'
2020-11-23 23:18:39 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.sl']')' event with context.id='adapt_lgt_fe0d_interval_48'
2020-11-23 23:18:39 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.dr']')' event with context.id='adapt_lgt_fe0d_interval_48'
2020-11-23 23:18:39 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr']')' event with context.id='adapt_lgt_fe0d_interval_48'
2020-11-23 23:18:51 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:19:03 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:19:27 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:20:03 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:20:05 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: '_update_attrs_and_maybe_adapt_lights' called with context.id='adapt_lgt_fe0d_interval_49'
2020-11-23 23:20:05 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Adaptive Lighting: Sunlights: '_adapt_lights(['light.lr2', 'light.su', 'light.sl', 'light.dr', 'light.ba', 'light.lr'], None, force=False, context.id=adapt_lgt_fe0d_interval_49)' called
2020-11-23 23:20:05 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr2', 'brightness': 50, 'white_value': 50, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_49'
2020-11-23 23:20:05 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.sl', 'brightness': 50, 'white_value': 50, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_49'
2020-11-23 23:20:05 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.dr', 'brightness': 50, 'white_value': 50, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_49'
2020-11-23 23:20:05 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr', 'brightness': 50, 'white_value': 50, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_49'
2020-11-23 23:20:05 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr2']')' event with context.id='adapt_lgt_fe0d_interval_49'
2020-11-23 23:20:05 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.sl']')' event with context.id='adapt_lgt_fe0d_interval_49'
2020-11-23 23:20:05 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.dr']')' event with context.id='adapt_lgt_fe0d_interval_49'
2020-11-23 23:20:05 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr']')' event with context.id='adapt_lgt_fe0d_interval_49'
2020-11-23 23:20:27 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:20:51 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:21:15 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: '_update_attrs_and_maybe_adapt_lights' called with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Adaptive Lighting: Sunlights: '_adapt_lights(['light.lr2', 'light.su', 'light.sl', 'light.dr', 'light.ba', 'light.lr'], None, force=False, context.id=adapt_lgt_fe0d_interval_50)' called
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr2', 'brightness': 49, 'white_value': 49, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.sl', 'brightness': 49, 'white_value': 49, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.dr', 'brightness': 49, 'white_value': 49, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr', 'brightness': 49, 'white_value': 49, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr2']')' event with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.sl']')' event with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.dr']')' event with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr']')' event with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.sl' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 48, 'color_temp': 500, 'white_value': 51, 'effect': '4', 'friendly_name': 'SL', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.sl' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 48, 'color_temp': 500, 'white_value': 48, 'effect': '4', 'friendly_name': 'SL', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] State change event of 'light.sl' is already in 'self.last_state_change' (adapt_lgt_fe0d_interval_50) adding this state also
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.lr2' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 48, 'color_temp': 500, 'white_value': 51, 'effect': '4', 'friendly_name': 'LR2', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.lr2' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 48, 'color_temp': 500, 'white_value': 48, 'effect': '4', 'friendly_name': 'LR2', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] State change event of 'light.lr2' is already in 'self.last_state_change' (adapt_lgt_fe0d_interval_50) adding this state also
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.dr' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 48, 'color_temp': 500, 'white_value': 51, 'effect': '0', 'friendly_name': 'DR', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.dr' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 48, 'color_temp': 500, 'white_value': 48, 'effect': '0', 'friendly_name': 'DR', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:31 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] State change event of 'light.dr' is already in 'self.last_state_change' (adapt_lgt_fe0d_interval_50) adding this state also
2020-11-23 23:21:32 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.lr' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 48, 'color_temp': 500, 'white_value': 51, 'effect': '4', 'friendly_name': 'LR', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:32 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.lr' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 48, 'color_temp': 500, 'white_value': 48, 'effect': '4', 'friendly_name': 'LR', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_50'
2020-11-23 23:21:32 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] State change event of 'light.lr' is already in 'self.last_state_change' (adapt_lgt_fe0d_interval_50) adding this state also
2020-11-23 23:21:39 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:22:03 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:22:27 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:22:57 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: '_update_attrs_and_maybe_adapt_lights' called with context.id='adapt_lgt_fe0d_interval_51'
2020-11-23 23:22:57 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Adaptive Lighting: Sunlights: '_adapt_lights(['light.lr2', 'light.su', 'light.sl', 'light.dr', 'light.ba', 'light.lr'], None, force=False, context.id=adapt_lgt_fe0d_interval_51)' called
2020-11-23 23:22:57 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr2', 'brightness': 48, 'white_value': 48, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_51'
2020-11-23 23:22:57 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.sl', 'brightness': 48, 'white_value': 48, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_51'
2020-11-23 23:22:57 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.dr', 'brightness': 48, 'white_value': 48, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_51'
2020-11-23 23:22:57 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr', 'brightness': 48, 'white_value': 48, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_51'
2020-11-23 23:22:57 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr2']')' event with context.id='adapt_lgt_fe0d_interval_51'
2020-11-23 23:22:57 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.sl']')' event with context.id='adapt_lgt_fe0d_interval_51'
2020-11-23 23:22:57 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.dr']')' event with context.id='adapt_lgt_fe0d_interval_51'
2020-11-23 23:22:57 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr']')' event with context.id='adapt_lgt_fe0d_interval_51'
2020-11-23 23:23:27 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:23:51 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:24:15 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:24:23 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: '_update_attrs_and_maybe_adapt_lights' called with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:23 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Adaptive Lighting: Sunlights: '_adapt_lights(['light.lr2', 'light.su', 'light.sl', 'light.dr', 'light.ba', 'light.lr'], None, force=False, context.id=adapt_lgt_fe0d_interval_52)' called
2020-11-23 23:24:23 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr2', 'brightness': 47, 'white_value': 47, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:23 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.sl', 'brightness': 47, 'white_value': 47, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:23 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.dr', 'brightness': 47, 'white_value': 47, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:23 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr', 'brightness': 47, 'white_value': 47, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:23 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr2']')' event with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:23 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.sl']')' event with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:23 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.dr']')' event with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:23 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr']')' event with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:24 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.lr2' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 46, 'color_temp': 500, 'white_value': 48, 'effect': '4', 'friendly_name': 'LR2', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:24 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.lr2' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 46, 'color_temp': 500, 'white_value': 46, 'effect': '4', 'friendly_name': 'LR2', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:24 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] State change event of 'light.lr2' is already in 'self.last_state_change' (adapt_lgt_fe0d_interval_52) adding this state also
2020-11-23 23:24:24 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.sl' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 46, 'color_temp': 500, 'white_value': 48, 'effect': '4', 'friendly_name': 'SL', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:24 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.sl' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 46, 'color_temp': 500, 'white_value': 46, 'effect': '4', 'friendly_name': 'SL', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:24 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] State change event of 'light.sl' is already in 'self.last_state_change' (adapt_lgt_fe0d_interval_52) adding this state also
2020-11-23 23:24:24 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.dr' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 46, 'color_temp': 500, 'white_value': 48, 'effect': '0', 'friendly_name': 'DR', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:24 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.dr' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 46, 'color_temp': 500, 'white_value': 46, 'effect': '0', 'friendly_name': 'DR', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:24 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] State change event of 'light.dr' is already in 'self.last_state_change' (adapt_lgt_fe0d_interval_52) adding this state also
2020-11-23 23:24:24 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.lr' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 46, 'color_temp': 500, 'white_value': 48, 'effect': '4', 'friendly_name': 'LR', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:24 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected a 'light.lr' 'state_changed' event: '{'min_mireds': 153, 'max_mireds': 500, 'effect_list': ['0', '1', '2', '3', '4'], 'brightness': 46, 'color_temp': 500, 'white_value': 46, 'effect': '4', 'friendly_name': 'LR', 'supported_features': 151}' with context.id='adapt_lgt_fe0d_interval_52'
2020-11-23 23:24:24 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] State change event of 'light.lr' is already in 'self.last_state_change' (adapt_lgt_fe0d_interval_52) adding this state also
2020-11-23 23:24:51 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:25:15 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:25:39 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:25:49 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: '_update_attrs_and_maybe_adapt_lights' called with context.id='adapt_lgt_fe0d_interval_53'
2020-11-23 23:25:49 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Adaptive Lighting: Sunlights: '_adapt_lights(['light.lr2', 'light.su', 'light.sl', 'light.dr', 'light.ba', 'light.lr'], None, force=False, context.id=adapt_lgt_fe0d_interval_53)' called
2020-11-23 23:25:49 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr2', 'brightness': 47, 'white_value': 47, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_53'
2020-11-23 23:25:49 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.sl', 'brightness': 47, 'white_value': 47, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_53'
2020-11-23 23:25:49 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.dr', 'brightness': 47, 'white_value': 47, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_53'
2020-11-23 23:25:49 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr', 'brightness': 47, 'white_value': 47, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_53'
2020-11-23 23:25:49 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr2']')' event with context.id='adapt_lgt_fe0d_interval_53'
2020-11-23 23:25:49 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.sl']')' event with context.id='adapt_lgt_fe0d_interval_53'
2020-11-23 23:25:49 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.dr']')' event with context.id='adapt_lgt_fe0d_interval_53'
2020-11-23 23:25:49 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr']')' event with context.id='adapt_lgt_fe0d_interval_53'
2020-11-23 23:26:03 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:26:27 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:26:51 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12
2020-11-23 23:27:15 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: '_update_attrs_and_maybe_adapt_lights' called with context.id='adapt_lgt_fe0d_interval_54'
2020-11-23 23:27:15 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Adaptive Lighting: Sunlights: '_adapt_lights(['light.lr2', 'light.su', 'light.sl', 'light.dr', 'light.ba', 'light.lr'], None, force=False, context.id=adapt_lgt_fe0d_interval_54)' called
2020-11-23 23:27:15 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr2', 'brightness': 46, 'white_value': 46, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_54'
2020-11-23 23:27:15 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.sl', 'brightness': 46, 'white_value': 46, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_54'
2020-11-23 23:27:15 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.dr', 'brightness': 46, 'white_value': 46, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_54'
2020-11-23 23:27:15 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Sunlights: Scheduling 'light.turn_on' with the following 'service_data': {'entity_id': 'light.lr', 'brightness': 46, 'white_value': 46, 'color_temp': 500} with context.id='adapt_lgt_fe0d_interval_54'
2020-11-23 23:27:15 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr2']')' event with context.id='adapt_lgt_fe0d_interval_54'
2020-11-23 23:27:15 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.sl']')' event with context.id='adapt_lgt_fe0d_interval_54'
2020-11-23 23:27:15 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.dr']')' event with context.id='adapt_lgt_fe0d_interval_54'
2020-11-23 23:27:15 DEBUG (MainThread) [custom_components.adaptive_lighting.switch] Detected an 'light.turn_on('['light.lr']')' event with context.id='adapt_lgt_fe0d_interval_54'
2020-11-23 23:27:15 WARNING (MainThread) [homeassistant.components.device_tracker] Updating device list from legacy took longer than the scheduled scan interval 0:00:12

Hi,
thank you for your amazing job.
Unfortunately I am experiencing the same issue.
Basically every "interval" seconds (e.g. 90 seconds) the lights flash briefly.
I am using innr gu10 bulbs only.
I will post my log as soon as possible.

 Flashing effect is now gone.
Instead of using the default group of lights (e.g. light.camera which includes light.camera_1 to light.camera_n) I specified all the single lights.
My configuration is now the following:

Hope this helps.

I am happy that it's solved for you!
Were you using a light group? As in you specified it like https://www.home-assistant.io/integrations/light.group/ ?
Or did you use a ZHA/deCONZ light group for example?

Were you using a light group? As in you specified it like https://www.home-assistant.io/integrations/light.group/ ?
Or did you use a ZHA/deCONZ light group for example?
I used the Philips Hue light group (the one I created in the Hue app and that was already present when I installed Home Assistant and linked to my Hue hub).

I have light.lr, light.lr2 and light.sl grouped as light.liv in hassio however in adaptive lighting they are already individually specified. These are the lights where I see the flashing behaviour it is most visible at low brightness.
Other lights I have set to be controlled by adaptive lighting which are not part of a group do not seem to have this behaviour now that I think about it so it does seem to be something to do with the way the groups work which causes the issue.
will keep my fingers crossed that there is a solution in future which will allow me to keep my light grouping!

watching them at a medium brightness now, there is no visible colour change but the light seems to breifly dim then bounce back each time the light updates

ive updated interval time between switch updates to 10 seconds so the flashing behaviour occurs more frequently. ive noticed that if prefer_rgb_color is checked, the lights flashes off every 10 seconds. if it is unchecked, the lights stay on but the colour flashes to white.
this seems to have stopped now, maybe because color level has now dropped below a certain threshold. If I check prefer_rgb_color again, the lights contnue to flash off every 10 seconds.

I also have this bug.
Philips hue hub and LIDL light strips. I've tried setting against individual entities as opposed to a group and still happens.
Is there anything you need to help pinpoint this down?

I also have this bug.
Philips hue hub and LIDL light strips. I've tried setting against individual entities as opposed to a group and still happens.
Is there anything you need to help pinpoint this down?

I've also experienced some flashing during updates.
Turning the detect_non_ha_changes off fixed it for me.

I've also experienced some flashing during updates.
Turning the detect_non_ha_changes off fixed it for me.

I think mine is a different issue, I've created a post in HA community - https://community.home-assistant.io/t/strip-lights-flash-once-when-turning-on-or-changing-brightness-colour-settings/269942

I think mine is a different issue, I've created a post in HA community - https://community.home-assistant.io/t/strip-lights-flash-once-when-turning-on-or-changing-brightness-colour-settings/269942

Add me to the list. I experience this quick but annoying flashing too when light settings are being changed.
I have all lights individually selected (not using deCONZ or HA light groups) in the AL config and also tested every option step by step, including turning lights off and on and reloading the AL integration between the config changes:

No config option changed this behavior.
I'm not 100 % sure but it might be possible this behavior wasn't there in the beginning.
As some users already provided debug logs and this issue stemmed to have some attention:
what can I/we do to help fixing this issue?

I hope this bug can be resolved with v2, as I have to touch the code anyway. So I'm adding this to the milestone.
Keep this ticket open until you can verify that it's properly working in the upcoming version 2.

My lights are flashed with Tasmota and from my own investigations this seemed to be related to the actual values of color, color_temp and brightness. If this integration hits on one of the dodgy combinations is causes a boot loop.
I tried taking the color/colour_temp/brightness values from a light which was seeing this effect and set another light to those values and it caused the same boot loop. A recent tasmota update seems to have mostly stopped this from happening to my lights.
I recommend if this is happening to you, find out what values the light is set to and try to set another light to the same values to see if it causes this to happen.

Good observation. But thinking it to the end: not every hardware can be flashed, there are bulbs with fixed factory firmware and there isn't even an update option nor updates available (pretty common in the ZigBee area afai experienced over the years).
So I still believe in a software based solution for this Software based bug (as the lights work flawlessly without AL).

you might be right but I thought for over a year adaptive lighting was the cause of my issues. I since discovered that it was only because adaptive lighting scrolls through many color/brightness combinations through each day and happened to hit a couple the combinations it didnt like when the light then got stuck in a boot loop.
up to you if you want to assume its not the light but it couldnt hurt to take note of the exact color, color temp and brightness settings next time it flashes and confirm on another light / adaptive lighting turned off to see if it still flashes.
As far as I know the flashing has not been linked to specifc code or log reports in adaptive lighting.

[Copy pasting this message in a few recent open issues]
I just wanted to take a moment to express my heartfelt thanks to everyone that is active in this repo. Your contributions, from answering questions to addressing issues, have been invaluable. It's amazing to see how supportive and helpful our community is!
Adaptive Lighting is all about enhancing your living spaces with smart, sunlight-responsive lighting. We've had quite a few discussions and open issues recently, and I see this as a positive sign of our community's engagement and growth. If you come across anything in the documentation that's unclear or if you have suggestions for improvement, please don't hesitate to share!. Your feedback is crucial for making Adaptive Lighting better for everyone.
On a personal note, I've recently welcomed twin boys into my family, which has been an incredible and life-changing experience. As you can imagine, my time is now more limited, and while I'm doing my best to keep up with the project, there may be delays in my responses. I appreciate your understanding and patience during this time.
Rest assured, I'm fully committed to addressing any bugs, especially those related to new Home Assistant updates, as swiftly as possible. I understand that many issues may stem from hardware limitations or misunderstandings about things like Zigbee groups. Your continued support and collaboration in helping each other out not only strengthen our community but also enhance the Adaptive Lighting experience for all.
Thank you once again for your understanding, patience, and support. Let's keep our houses well lit and adaptive for maximal enjoyment of life! 🌞🏠🌙


prediction endpoint url is wrong when using ClusterIP

/kind bug
from kubeflow.fairing import PredictionEndpoint
endpoint = PredictionEndpoint(HousingServe, input_files=['trained_ames_model.dat', "requirements.txt"],
                              docker_registry=DOCKER_REGISTRY,
                              service_type='ClusterIP',
                              backend=BackendClass(build_context_source=BuildContext))
endpoint.create()

We get endpoint results.
Deploying the endpoint.
Cluster endpoint: http://fairing-service-srwh2.kubeflow-anonymous.svc.cluster.local
Prediction endpoint: http://fairing-service-srwh2.kubeflow-anonymous.svc.cluster.local

if we run following command, it will hang there.
# Get sample data and query endpoint
(train_X, train_y), (test_X, test_y) = read_input("ames_dataset/train.csv")
endpoint.predict_nparray(test_X)

The problem is right url should be
http://fairing-service-srwh2.kubeflow-anonymous.svc.cluster.local:5000/predict
If we change to this config, prediction works well.
endpoint.url='http://fairing-service-n8qv2.kubeflow-anonymous.svc.cluster.local:5000/predict'
endpoint.predict_nparray(test_X)

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

I will file a PR to fix this issue


Add a no-collection option for rspec generator template

When you generate a no-collection task for an application using RSpec the resultant spec file assumes that the task is for collections.
Running rails g maintenance_tasks:task sing_songs --no-collection
Before
# frozen_string_literal: true

require "rails_helper"

module Maintenance
  RSpec.describe SingSongsTask do
    describe "#process" do
      subject(:process) { described_class.process(element) }
      let(:element) {
        # Object to be processed in a single iteration of this task
      }
      pending "add some examples to (or delete) #{__FILE__}"
    end
  end
end

After
# frozen_string_literal: true

require "rails_helper"

module Maintenance
  RSpec.describe SingSongsTask do
    describe "#process" do
      subject(:process) { described_class.process }
      pending "add some examples to (or delete) #{__FILE__}"
    end
  end
end

I have signed the CLA!

CI failures are unrelated so let's merge it since the change is extremely safe.


This command requires version two or greater of the GraphQL transformer.

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm i -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
v14.17.5
Amplify CLI Version
7.5.1
What operating system are you using?
Mac
Amplify Categories
auth, storage, api
Amplify Commands
status
Describe the bug
I ran the command "amplify status api -acm tablename" and got a status of auth categories as described in the docs here. I also got a message adivising to update my cli so I ran the command as described -npm i -g @aws-amplify/cli. After this I now get the message "This command requires version two or greater of the GraphQL transformer." whenever i run the command "amplify status api -acm tablename"
Expected behavior
I expect to get the same summary as I did before I updated the amplify cli.
Reproduction steps
run commands as follows

"amplify status api -acm tablename" get a list auth categories for the table
"npm i -g @aws-amplify/cli" to update to 7.5.1
"amplify status api -acm tablename"  and get message "This command requires version two or greater of the GraphQL transformer."

GraphQL schema(s)

# Put schemas below this line
type Part
  @model
  @auth(rules: [{ allow: private, provider: userPools, operations: [read] }])
  @key(name: "byPartItem", fields: ["partitemID"])
  @key(name: "byPurchasedCar", fields: ["purchasedcarID"])
  @key(name: "byAccount", fields: ["accountID"])
  @aws_iam
  @aws_cognito_user_pools {
  id: ID!
  make: String
  carmodel: String
  Listed: AWSDateTime
  purchasedcarID: ID
  accountID: ID
  Account: Account @connection(fields: ["accountID"])
}

Log output

# Put your logs below this line

Additional information
No response

see the document that I referred to in the issue description https://docs.amplify.aws/cli/graphql/authorization-rules/#field-level-authorization-rules

After some searching I found the following docs :
AWS Amplify announces the new GraphQL Transformer v2. More feature-rich, flexible, and extensible.
and GraphQL Transformer v1 to v2 migration
I ran the migration command as specified and the original issue was resolved. I'm now testing the GraphQl migrations

The migration  has now broken the admin ui . I get " Error processing @hasMany directive on Account.AccParts, @index directive with name byAccount was not found in connected model Part".  I  pushed the data schema  changes after I ran the migration  and then tried to make a change to the data model via the Amplify admin ui  but I can't save and deploy without getting this message now. I'm not sure what nis required here

Hi @matthewapps - thanks for filing the issue. I think there are two things issues here:

Command not printing your expected output

"I ran the command "amplify status api -acm tablename" and got a status of auth categories as described in the docs".
Is it possible you meant to type amplify status -v auth which gives you a verbose output of the auth category resources? We just launched amplify status api -acm tablename as part of the new GraphQL Transformer yesterday with version 7.5.0, so it's unlikely it worked before.

Admin UI not recognizing the directives properly.

" Error processing @hasmany directive on Account.AccParts, @Index directive with name byAccount was not found in connected model Part". I pushed the data schema changes after I ran the migration and then tried to make a change to the data model via the Amplify admin ui but I can't save and deploy without getting this message now. I'm not sure what nis required here
This sounds more like an Admin UI issue, and I'd be happy to transfer this issue to that repo and team.

Can you confirm that 1 is resolved. Then I'll transfer the ticket to the correct team to tackle 2.

Hi thanks for your reply. Issue 1 is resolved but I think the solution has cause the second issue. It would be great if you could transfer the second issue to the Admin UI team please. Thanks again.


Show currently playing song

Show currently playing song. Great app though.

not possible as it directly streams the radio.


Where are the connection strings??

The only reason we come here is to snag the format for the connection strings. It really isnt that helpful to just say we support AAD. Tell me how i can use it please.

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

ID: 55747c48-5caa-3234-f978-a667aed13352
Version Independent ID: c18a4db6-71e3-a539-1e7f-2f49662f4bbc
Content: Azure Active Directory auth - Azure SQL
Content Source: articles/sql-database/sql-database-aad-authentication.md
Service: sql-database
Sub-service: security
GitHub Login: @GithubMirek
Microsoft Alias: mireks

@DrewGoldsberry Thank you for your feedback! We will review and provide an update as appropriate.

@DrewGoldsberry  Thank you for the feedback.
This is documented in the configure features section here.
A reference to the above link is already provided on this page in the Next Steps section
Please let us know if you have any further questions.

@DrewGoldsberry We will proceed to close this issue now.
If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


STARPORTTECHLABRESEARCH abilities not working

I'm trying to upgrade Banshee ability from Startport TechLab.
I used below code:
if self.units(UnitTypeId.STARPORTTECHLAB).ready.exists:
    for spt in self.units(UnitTypeId.STARPORTTECHLAB).idle:
        #     self.combinedActions.append(spt(AbilityId.STARPORTTECHLABRESEARCH_RESEARCHMEDIVACENERGYUPGRADE))
        #     self.combinedActions.append(spt(AbilityId.STARPORTTECHLABRESEARCH_RESEARCHDURABLEMATERIALS))
        #     self.combinedActions.append(spt(AbilityId.STARPORTTECHLABRESEARCH_RESEARCHLIBERATORAGMODE))
        #     self.combinedActions.append(spt(AbilityId.STARPORTTECHLABRESEARCH_RAVENRESEARCHENHANCEDMUNITIONS))
        self.combinedActions.append(spt(AbilityId.STARPORTTECHLABRESEARCH_RESEARCHDURABLEMATERIALS))
await self.do_actions(self.combinedActions)

I tried each comment part, none of them work.
Now I cannot upgrade any ability from starport techlab.

Just found that at least for Banshee, I can use below Abilities:
RESEARCH_BANSHEECLOAKINGFIELD
RESEARCH_BANSHEEHYPERFLIGHTROTORS
I still don't understand why STARPORTTECHLABRESEARCH_RESEARCH*** doesn't work.
It looks much more official.

I think you are trying to research upgrades that were removed from the game but are still listed in the AbilityIds.
You can also use the .research function to let the function figure out the research ability from an UpgradeId:

idle_starport_techlabs = self.units.filter(lambda u: u.type_id == UnitTypeId.STARPORTTECHLAB and u.is_ready and u.is_idle)
for spt in idle_starport_techlabs:
    self.combinedActions.append(spt.research(UpgradeId.BANSHEECLOAK))
    self.combinedActions.append(spt.research(UpgradeId.BANSHEESPEED))
    self.combinedActions.append(spt.research(UpgradeId.MEDIVACINCREASESPEEDBOOST))
    self.combinedActions.append(spt.research(UpgradeId.RAVENCORVIDREACTOR))
    # The following requires that you have a fusion core
    self.combinedActions.append(spt.research(UpgradeId.LIBERATORMORPH))
await self.do_actions(self.combinedActions)

Here are a couple upgrades and their corresponding research abilities.

UnitTypeId.STARPORTTECHLAB: {
    UpgradeId.BANSHEECLOAK: {"ability": AbilityId.RESEARCH_BANSHEECLOAKINGFIELD},
    UpgradeId.BANSHEESPEED: {
        "ability": AbilityId.RESEARCH_BANSHEEHYPERFLIGHTROTORS
    },
    UpgradeId.LIBERATORMORPH: {
        "upgrade": UpgradeId.LIBERATORMORPH,
        "ability": AbilityId.STARPORTTECHLABRESEARCH_RESEARCHLIBERATORAGMODE,
        "requires_tech_building": UnitTypeId.FUSIONCORE,
    },
    UpgradeId.MEDIVACINCREASESPEEDBOOST: {
        "ability": AbilityId.RESEARCH_HIGHCAPACITYFUELTANKS
    },
    UpgradeId.RAVENCORVIDREACTOR: {
        "ability": AbilityId.RESEARCH_RAVENCORVIDREACTOR
    },

Thanks @BurnySc2 for pointing it out!
This is great help of understanding how does the research upgrade works in python-sc2.
I would suggest to remove the unused attributes.


API

It would be useful if htmlifier provided an API that acted as an alternative to the web UI. At the moment, I'm having to launch a headless browser to do this.
// @SheepTester

Nice Idea @Richienb
// @SheepTester


Add linuxArm64 target

Was omitted from #292.

How do you get the linuxArm64 artifact? I don't find it here: https://repo1.maven.org/maven2/org/jetbrains/kotlinx/

How do you get the linuxArm64 artifact? I don't find it here: https://repo1.maven.org/maven2/org/jetbrains/kotlinx/

oops, I didn't check it.
Indeed, there is only x64 builds of coroutines and atomicfu
https://repo1.maven.org/maven2/org/jetbrains/kotlinx/kotlinx-coroutines-core-linuxx64/
https://repo1.maven.org/maven2/org/jetbrains/kotlinx/atomicfu-linuxx64/
So it's probably the reason why it was ommited.


fix: ServerCard style

For overly long or short hostnames, the status dot will display errors.
before:

after:

For cases where the screen size is less than lg, the name section with w-28 is too short.
before:

after:

Thank you for your contribution, it's wonderful.❤


Add support for full Browserify bundle

Many projects need functionality both from core and music_rnn/ music_vae. For example, you may need to use the NoteSequence or ControlSignal libraries as well as the main model class.
Also, some projects may use both RNN and VAE.
Currently this doesnt seem possible as RNN and VAE are in separate bundles, both of which contain their own copy of core as well as Tensorflow.
Would it make sense to create a magenta-full.js bundle to easily include everything?

This is a good point. Is it not possible to import the two bundles
separately?
On Sat, Apr 14, 2018, 3:08 AM Tero Parviainen<EMAIL_ADDRESS>wrote:

Many projects need functionality both from core and music_rnn/ music_vae.
For example, you may need to use the NoteSequence or ControlSignal
libraries as well as the main model class.
Also, some projects may use both RNN and VAE.
Currently this doesnt seem possible as RNN and VAE are in separate
bundles, both of which contain their own copy of core as well as Tensorflow.
Would it make sense to create a magenta-full.js bundle to easily include
everything?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/magenta-js/issues/27, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABCa6IXcnEGMTyD0Xjs35a5xgkl-RdiYks5tocqygaJpZM4TVArz
.

It's possible if you Yarn/NPM install it and import.
But when using the browserified bundles (e.g. on Codepen) each of magenta.js, musicrnn.js, and musicvae.js has its own copy of Tensorflow causing some load errors (as well as a lot more weight)

Makes sense. Do you know how to set this up?
We could also consider making a single package instead of separating out
the models.
On Sat, Apr 14, 2018, 8:58 AM Tero Parviainen<EMAIL_ADDRESS>wrote:

It's possible if you Yarn/NPM install it and import.
But when using the browserified bundles (e.g. on Codepen) each of
magenta.js, musicrnn.js, and musicvae.js has its own copy of Tensorflow
causing some load errors (as well as a lot more weight)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/magenta-js/issues/27#issuecomment-381339111,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABCa6NOgcLOxxM5HXkqQ895eNeVy_exdks5tohyagaJpZM4TVArz
.

Yes, might make sense to add a new index.ts somewhere that pulls in everything, and then a build target that browserifies it.

I could imagine having a package called @magenta/models that combines all of the model packages. This is basically what you are suggesting. We can decide on something on Monday when @cghawthorne can also weigh in.

@teropa, do you have any objection to us just combining the full library into a single package and removing the separate core, music_rnn, and music_vae packages? We are new to the JS world, so we aren't sure how this would typically be done.

No objections at all, sounds good. I think that's a fairly typical pattern anyway.

Our current plan is to move all of our current packages into a single @magenta/music package, leaving room for future models that don't work with NoteSequences.
@cghawthorne, we should probably restructure the directories, e.g., move music_vae.ts and music_rnn.ts into a models directory. data.ts should probably be renamed to converters.ts since we have other data libs.


Changes made in GSI to assimilate all-sky ATMS

Changes to assimilate all-sky ATMS water vapor channels. The changes were made on top of x0045a.

Thanks Meta for fixing the status label!
For now, I am still not able to get over with "all checks have failed" flag.
I am sending the issue to Matt for advice.

@jing-guo The issue is that the "required" labels are:

0-diff
0-diff trivial
0-diff structural
non-0-diff

We require one of those so that gatekeepers know if a PR should change the "answer" of the model/code or not. So, I suppose this is non-zero-diff? Not sure how to label it.

After updated to the current develop HEAD, this change contains only a feature enhancement to proper processing of ATMS observation.  And it should be zero-diff, if ATMS is not in use.  Based on this, I do want to set the required label to zero-diff with enhancement.
However, this change (after synched to the current develop HEAD) does contain differences in their ATMS channel info configuration data.  With this consideration, it is also labeled with observation-configuration, to catch integrators' attention.

Jing - as it turned out this code was not at all zero-diff. The fact that this was put on develop messed me up big time.  Please next time let's review only the ticket in question. Thanks.


List non staff with stream perms

This command is useful to audit users who still have the permission to stream.
I have chosen to also sort and paginate the embed to make it easier to read.
The sorting is based on how long until the user's streaming permissions are revoked, with permanent streamers at the end.

I'm Mr. Hemlock, and this is my favorite PR on the citadel.