MacOS build fails after merge into master

After merging, the MacOS Release build fails during tests. Same thing happens on my Mac if I run tests for the 'Release' build.

From the build log:
EXEC : error : /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: no LC_RPATH load command with path: /usr/local/lib found in: /Users/runner/work/1/s/src/Native/../../bin/x64.Release/Native/./libLibTorchSharp.dylib (for architecture x86_64), required for specified option "-delete_rpath /usr/local/lib" [/Users/runner/work/1/s/src/Native/build.proj]
EXEC : error : /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: no LC_RPATH load command with path: /usr/local/opt/llvm/lib found in: /Users/runner/work/1/s/src/Native/../../bin/x64.Release/Native/./libLibTorchSharp.dylib (for architecture x86_64), required for specified option "-delete_rpath /usr/local/opt/llvm/lib" [/Users/runner/work/1/s/src/Native/build.proj]
EXEC : error : /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: no LC_RPATH load command with path: /Users/runner/work/1/s/bin/obj/AnyCPU.Release/libtorch-cpu/libtorch-macos-1.8.0cpu/libtorch/lib found in: /Users/runner/work/1/s/src/Native/../../bin/x64.Release/Native/./libLibTorchSharp.dylib (for architecture x86_64), required for specified option "-delete_rpath /Users/runner/work/1/s/bin/obj/AnyCPU.Release/libtorch-cpu/libtorch-macos-1.8.0cpu/libtorch/lib" [/Users/runner/work/1/s/src/Native/build.proj]
EXEC : error : /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: for: /Users/runner/work/1/s/src/Native/../../bin/x64.Release/Native/./libLibTorchSharp.dylib (for architecture x86_64) option "-add_rpath @loader_path" would duplicate path, file already has LC_RPATH for: @loader_path [/Users/runner/work/1/s/src/Native/build.proj]
EXEC : error : /Applications/Xcode_12.4.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: for: /Users/runner/work/1/s/src/Native/../../bin/x64.Release/Native/./libLibTorchSharp.dylib (for architecture x86_64) option "-add_rpath @executable_path" would duplicate path, file already has LC_RPATH for: @executable_path [/Users/runner/work/1/s/src/Native/build.proj]
/Users/runner/work/1/s/src/Native/build.proj(40,5): error MSB3073: The command ""/Users/runner/work/1/s/src/Native/build.sh" --configuration Release --arch x64  --libtorchpath /Users/runner/work/1/s/bin/obj/AnyCPU.Release/libtorch-cpu/libtorch-macos-1.8.0cpu/libtorch/share/cmake/Torch" exited with code -1.

Hmmm ok, yes I only ran tests debug.  I wonder why CI passes tests
On master build, I'm fixing the package build, see direct commits like https://github.com/xamarin/TorchSharp/commit/33a690609cd2255257da6e172a57bec799d7b3a9

Yes, it is very curious that it works on the PR build, but not on the master build or on my machine.

Master build passed MacOS release tests, it failed later in the package build

Release tests run on my machine, now.


Configure release binaries

Right now the only way to install is to build go yourself.
Binaries in release assets will allow to use easyp in devbox  and other tools.
Or just install, for example, by eget

of course not bug, just a miss...


Resolved deployment user issue for az hack

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/GeekTrainer/azure-cli-extensions.git@master#subdirectory=src/$EXT&egg=$EXT"

@zikalino A couple of simple updates, and the whl is pushed. Last change for the year. Thank you!!


Renaming tunnelIdentifier to tunnelName in SC examples

Description

Following https://github.com/saucelabs/sauce-docs/pull/1414.
SC CLI flag --tunnel-name is fully supported in SC versions 4.7.x/4.8.x and the corresponding capability tunnelName is supported by all Sauce Labs testing platforms. Those are preferred options. This MR updates code snippets in all docs from --tunnel-identifier to --tunnel-name and, also, most of tunnelIdentifier/parentTunnel in test capabilities examples.
Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[ ] I have read the contributing document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

@waggledans Thank you!!


Dropped frames when transitioning in between app states

Noticed that transitioning in between app states produces dropped frames that are noticeable.
Wonder if it's not too bad of a lift to add handling for this.
https://github.com/user-attachments/assets/e987b7c5-a0da-4471-976f-79ffa37dd29a

What would the handling look like?
Do you expect the orb to...

Option 1: Continue animating seamlessly. I imagine it takes a few milliseconds for the app to come to life and for these events to restart. There may be technical limitations here.
Option 2: Turn the orb gray, and reduce speed to 0. Then animate it back up?
Option 3: Leave it to the app developers to figure out how to handle app backgrounding/foregrounding states.

I'm leaning toward Option 3. I'd be curious to hear of a use case for this before polishing it up.

Looking at it, there does seem to be a technical limitation since we are already animating continuously across scene phase changes.
To make it smoother, I'm thinking we can pause the animation and restart it where it left off when the scenePhase changes to active. This way we reduce the perception of it stuttering. I can get a PR together.


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


mpd: 0.23.13 -> 0.23.14

https://www.musicpd.org/news/2023/10/mpd-0-23-14-released/
Description of changes

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 259763 run on x86_64-linux 1

5 packages built:

mpd
mpd-small
mpd-small.doc
mpd.doc
mpd.man


micro-spring-boot enhancements, plugin and module use JDK interfaces

Spring Boot version bump
Spring version bump

Fix for https://github.com/aol/micro-server/issues/183


It works for me also. Thank you

adjusting the line in question to this: "renderer.material.SetTexture("_MainTex", new Texture2D(0,0));"
fixed the issue for me : )
I will keep an eye open for an update to  VRTK that works with 2018.2 +
Originally posted by @treendy in https://github.com/thestonefox/VRTK/issues/1796#issuecomment-410544794

This has been fixed already in v3.3.0


Add finite types support for jballerina

Purpose
Add finite types support for jballerina
Resolves #14764
Samples
type State "on"|"off";

function finiteAssignmentStateType() returns State {
    State p = "on";
    State comparator = "on";
    if (p == comparator) {
       p = "off";
    }
    return p;
}

Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[x] Added necessary documentation

[x] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #15183 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master   #15183      +/-   ##
============================================
- Coverage     23.26%   23.25%   -0.01%
  Complexity     4996     4996
============================================
  Files          1304     1304
  Lines         65825    65852      +27
  Branches       8913     8917       +4
============================================
  Hits          15311    15311
- Misses        48826    48853      +27
  Partials       1688     1688

Impacted Files
Coverage Δ
Complexity Δ

...erinalang/compiler/bir/writer/BIRBinaryWriter.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

...llerinalang/compiler/bir/writer/BIRTypeWriter.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...lerinalang/compiler/bir/model/InstructionKind.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...va/org/wso2/ballerinalang/compiler/bir/BIRGen.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Update Pусский.json

Update RU translate 2/2.
For line 7, please make the button wider.

Also, I would suggest that you update your readme.md file. add at least a description of the program and how it works.
of course in all available languages in the program.
(this is a very big plus for those who google this kind of program)

And also, make the columns a little wider in excel.


ALPhpRunner use problem

Hello,
ALPhpRunner how to call the following this type of URL:
http://localhost/index.php/hello/world
Best regards

No ALPhpRunner can be use only to run local php code (like myscript.php) and get the output. The url http://localhost/index.php/hello/world is a webpage and you can only download the result via http (using TalHttpClient or indy for exemple). It's the webserver who will run the php script
please don't forget to star (like) this project of ghitub if you like it

Is a local call, but need to pass QUERY_STRING parameters, I don't really understand how do you pass this parameter?
Such as:
QUERY_STRING = goto = newpost&t = 1
My index.php file URL is called "index.php/hello = world", also may be "index.php/hello/world", such parameters how to pass?

Did you already star (like) this project of ghitub (like I kindly asked you) ? Why i will spend time to help people (And I even not count the time to build the code that I gave for free) if those people can not even spend 1 ms to click on a "star" button ??

try to see the demo ALPhpRunner to find out how to execute PHP script ...


Promotions are not applied anymore when a position is added to the order and the max. uses per customer is reached

Description:
When a promotion which has a maximum number of uses per customer is applied to an order, and this maximum number is reached for that customer, the promotion is no longer applied when an additional item is added to the order afterwards. This results in the wrong total for the order.
Environment:
On-Premises
Steps to reproduce:

Create a promotion with a discount (e.g. 20%) that can only be applied once per customer.
Create an order that uses this promotion (e.g. using a fixed promotion code)
The discount is applied to the order and order total is correct
Edit the order and add a new product or custom item.
The discount is no longer applied to the order, but remains as a line item in the order.

Expected result:
The original discount should still be applied to the order total.
Actual result:
The original discount is no longer applied to the order total, but remains as a line item.

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-37593.
[created from NEXT-37593, comment 485105]

[public]

FixVersion Change: <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>

This issue will be / was solved in Shopware version <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>.
[created from NEXT-37593, comment 510422]

[public]

FixVersion Change: <IP_ADDRESS>, <IP_ADDRESS>

This issue will be / was solved in Shopware version <IP_ADDRESS>, <IP_ADDRESS>.
[created from NEXT-37593, comment 510462]


Incorrect(?) documentation for override_lens

the README, currently, describes override_lens as:
@param bufnr (number) buffer number
@param splist (table) (1,1)-indexed position
@param nearest (boolean) whether nearest lens
@param idx (number) nearest index in the plist
@param relIdx (number) relative index, negative means before current position, positive means after

Is the bufnr annotation correct? The override function seems to be passed the entire render object:
https://github.com/kevinhwang91/nvim-hlslens/blob/6cd78e73b28af4618cf67a470e53e13d59899914/lua/hlslens/render.lua#L103-L106

Thanks, have corrected it.


update

Codecov Report

Merging #25 (1586105) into master (ea1251a) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #25   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          403       403
=========================================
  Hits           403       403

Continue to review full report at Codecov.

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


[tests] Maybe fix flakey test by increasing timeout

Bump the timeout for the agent test TestSessionRestartedOnNodeDescriptionChange in order to avoid spurious test failures.  Also include a little more info on why the test failed, if it fails.
Signed-off-by: cyli<EMAIL_ADDRESS>Hopefully this may fix #2122.

LGTM


(BOLT-1318) Warn when case-insensitive modulepath exists

This commit adds a warning that displays when a specified modulepath does not exist but a case-insensitive version does. The case-insensitive version of the modulepath is displayed with the warning. Previously, if the modulepath's case was incorrect then Bolt would not be able to locate the modules.
The reason for this change is that some Bolt users may be expecting case-insensitivity when specifying a modulepath, but not know that Bolt is case-sensitive.

CLA signed by all contributors.


Alerting on AD assessments

Can you provide some guidance on alerting on AD assessment data? I'd like to be able to fire an alert if a critical recommendation is encountered, but not seeing a field corresponding to severity in the schema for assessment records.

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

ID: 9fe28c1b-e0f3-b558-e58c-ad32c455cd21
Version Independent ID: ee336116-b3ec-4e0e-d6e8-b11f6022115e
Content: Optimize your Active Directory environment with Azure Log Analytics
Content Source: articles/log-analytics/log-analytics-ad-assessment.md
Service: log-analytics
Product: unspecified
GitHub Login: @MGoedtel
Microsoft Alias: magoedte

@bmilbauer Thanks for the feedback. We are actively investigating and will get back to you soon.

@bmilbauer Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@vasivara-MSFT - since this isn't a documentation issue but a "how-to", suggesting you remove the doc-enhancement label.

Understood re: the field. Thanks for the workaround suggestion.
[cid:sig_logo_f5171a6d-0aac-4537-8cf7-f3b2a514406a.png] https://ivision.com/
Bradley Milbauer
Senior Consultant | Consulting Services | Infrastructure Services
M: +1<PHONE_NUMBER>tel:+1<PHONE_NUMBER> | O: +1<PHONE_NUMBER>tel:+1<PHONE_NUMBER>
[cid:sig_facebook_4c7b99a3-311c-468d-9c74-683eb2595d6a.png] https://facebook.com/iVisionATL   [cid:sig_twitter_279e5bfb-73c9-4ff9-83d8-1e2f5d52b2d1.png]  https://twitter.com/iVisionATL    [cid:sig_linkedin_2cd731a6-1916-4c38-b3ef-e44eb606a501.png]  https://www.linkedin.com/company/ivision
Client Engagement Value
I am passionate about learning and growth.
[cid:btn_how_are_we_doing_1eba60b4-37b4-4524-bcbb-70cdc7358682.png] https://www.surveymonkey.com/r/VC7FZ22
From: Matt Goedtel<EMAIL_ADDRESS>Sent: Monday, May 21, 2018 2:39 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Bradley Milbauer<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Alerting on AD assessments (#8803)
@vasivara-MSFThttps://github.com/vasivara-MSFT - since this isn't a documentation issue but a "how-to", suggesting you remove the doc-enhancement label.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/8803#issuecomment-390744083, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AT1o9KCh0EBonLUV0yYm7je_91o74319ks5t0wnGgaJpZM4UDuP1.

@MGoedtel  Done
@bmilbauer  We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Fix user story table

Codecov Report

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

@@            Coverage Diff            @@
##             master      #41   +/-   ##
=========================================
  Coverage     61.60%   61.60%
  Complexity      412      412
=========================================
  Files            85       85
  Lines          1521     1521
  Branches        149      149
=========================================
  Hits            937      937
  Misses          551      551
  Partials         33       33

Continue to review full report at Codecov.

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


added proper context support

closes #12

Pull Request Test Coverage Report for Build 190

52 of 60 (86.67%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.07%) to 90.0%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

include/crow/crow.hpp
52
60
86.67%

Totals

Change from base Build 185:
-0.07%

Covered Lines:
162

Relevant Lines:
180

💛  - Coveralls


Odd value accepted by Marathon API, and not explanatory error message.

ℹ Related to this issue: https://github.com/mesosphere/marathon/issues/5077

Marathon version: 1.4.0-RC9
When I submit this app config:
{
  "id": "/mlunoe/constraints",
  "cmd": "sleep 9999",
  "instances": 1,
  "cpus": 0.1,
  "constraints": [
    [
      "five",
      "MAX_PER"
      "foo"
    ]
  ]
}

I receive this API response:
{
  "message": "Object is not valid",
  "details": [
    {
      "path": "/constraints",
      "errors": [
        "Value was specified but is not a number"
      ]
    }
  ]
}

Expected a more explanatory error message like: "Must only contain characters between 0-9 for operator MAX_PER" (or GROUP_BY for that matter).
I also would expect to be able to provide the number 2, which the API does not accept at this point.

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-4284. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


[Task #2036786] Get default runtime based on compile level in maven plugin config goal

What does this implement/fix? Explain your changes.

Get default runtime based on project compile level for spring/webapp maven plugin
Change to select runtime in spring maven plugin config goal

Does this close any currently open issues?
AB#2036786

Any relevant logs, screenshots, error output, etc.?

Any other comments?
…
Has this been tested?

[ ] Tested

Move to PR #2247


Create entry point for Mesos executor (resolves #232)

Build hung. Probably because the Mesos slave was not able to find the executor entry point due to the fact that the venv wasn't active.

Yep.
sh: 1: mesos-toil-executor: not found


Does detectSingleFace returns a Promise or a Class???

Here it returns a promise:
const detection = await faceapi.detectSingleFace(input)
But in typing it returns DetectSingleFaceTask class, and only its run() method returns a Promise.
https://github.com/justadudewhohacks/face-api.js/blob/c66dbbde9bcfa4fe67e65d818c698597ed2825a0/build/es6/globalApi/detectFaces.d.ts#L4

It's not directly a Promise, but it's a custom class, which is awaitable.

Clear. Cheers.


Upcoming protobuf 5 contains breaking changes, restrict to 4 for now.

Relates to #9566
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[x] I have run changie new to create a changelog entry

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

Project coverage is 54.04%. Comparing base (9a1f20a) to head (6ffef7b).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #81   +/-   ##
=======================================
  Coverage   54.04%   54.04%
=======================================
  Files          49       49
  Lines        2866     2866
=======================================
  Hits         1549     1549
  Misses       1317     1317

Flag
Coverage Δ

unit
54.04% <ø> (ø)

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

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


Stopwatch, added total elapsed time

I tried to mess with the interface.html but unfamiliar with HTML, reverted to the current one on main repo.
Changes:
Added total elapsed time
Changed display so total time is the main display with lap time underneath
The final lap that is left when the start/stop button is now saved into the array
Total run time now appends to first entry in the array
Could you please help me with the HTML to display the total time and make it only read laps from the 2nd entry of the array? Thanks!

So just to be clear on this - you're adding an extra field to the JSON at the start, and realistically you just want what would have been:
0 : ...
1 : ...
2 : ...
3 : ...
...

to read:
Elapsed time : ...
0 : ...
1 : ...
2 : ...
...

?

So just to be clear on this - you're adding an extra field to the JSON at the start, and realistically you just want what would have been:
0 : ...
1 : ...
2 : ...
3 : ...
...

to read:
Elapsed time : ...
0 : ...
1 : ...
2 : ...
...

?

Heya, yeah, in the main app code I appended it to the array before the function call to map the array in reverse and return, I figured the total time would have been easier to handle if it was at the start of the array.
I've probably been making a mountain out of a molehill or done it in some roundabout way, sorry for that, saw the improvements you made to the earlier code, thanks! Has helped me learn. First time doing javascript, I wanted to use the bangle as a means to learn how to use js.
Would it be better to have it under the lap table, or have it put in as an entry above the lap table?
eg.
Elapsed time | 0:20:34
Lap                  | Timing
1                      | 0:05:20
2                      | 0:05:15
3...
etc...

Ok, just added - I stuck it in next to the lap list

Thank you!


Google hangouts is unsupported

Hello and thanks for the fantastic extension,
After toying around with it in a bunch of places I have found that it does not work with Google hangouts. Here is an example of the DOM element where text is edited in GH:

I might give this a look during the weekend, but I'm creating an issue for reference purposes.

Thanks for this report — I really appreciate it! I've added Google Hangouts to the wiki here.
If you want to take a look this weekend, I'd be happy to provide backup :D

Like I said, I started taking a look into this today. I figured out that the hangouts input is inside an iframe, such as this one:

Since this iframe points to hangouts.google.com, I think this makes it impossible to interact with the input from mail.google.com, due to CORS issues.
If I go to hangouts.google.com, I also get a similar iframe, but one whose DOM I can actually interact with, seeing as there are no CORS issues.
I'm now gonna look into ContentEditable.js and the the contenteditable standard. If you've got any good links to explain those, I'd greatly appreciate it.

Awesome, good research! I don't have any really great resources on contenteditable, but I'm happy to answer any questions you have may about ContentEditable.js.!

@jessepollak @JSFernandes Here's some links with dev info and things you can do with it:
https://developer.mozilla.org/en-US/docs/Web/Guide/HTML/Content_Editable
http://www.w3schools.com/tags/att_global_contenteditable.asp
https://medium.com/medium-eng/why-contenteditable-is-terrible-122d8a40e480
http://lifehacker.com/5980134/turn-any-browser-window-into-a-quick-edit-notepad
http://www.labnol.org/internet/design/edit-web-pages-like-wiki/3832/

It's a long shot but I wanted to bump this


error  in run visualizer in the bin directory

(suma) jyzhang@sumig-System-Product-Name:~/catkin_ws/src/SuMa/bin$ ./visualizer 段错误 (核心已转储)
GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./visualizer...done.
(gdb) run
Starting program: /home/jyzhang/catkin_ws/src/SuMa/bin/visualizer
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
__GI___libc_free (mem=0x20) at malloc.c:3113
3113	malloc.c: 没有那个文件或目录.
(gdb)

I have solve this by download gtsam-4.0.0-alpha2,and build it


Timepicker arrow icons are missing

I noted icons of up and down arrow keys of links/buttons in timepicker widget are not appearing properly. They are functioning properly as intended, but icons seems to be misplaced, transparent arrow seems appearing above
. I checked in chrome.
Please see the screenshot attached.

The same problem occurred with me.


SGR 4 sub-parameters are treated as normal parameters

Describe the bug
Sub-parameters for an SGR sequence are treated as additional SGR parameters.
Setup
Replicated in standard Ubuntu 24.04 container with sequin 0.1.1 amd64 installed.
To Reproduce
Steps to reproduce the behavior:

Execute echo -e '\e[4:1mUnderlined text, but no bold\e[m\n\e[4;1mBold AND underlined\e[m'
Compare real terminal emulator output with the sequin ouput:

$ echo -e '\e[4:1mUnderlined text, but no bold\e[m\n\e[4;1mBold AND underlined\e[m' | sequin
 CSI 4:1m: Underline (Single), Bold
Text Underlined text, but no bold
 CSI m: Reset style
Ctrl \n: Line feed
 CSI 4;1m: Underline, Bold
Text Bold AND underlined
 CSI m: Reset style
Ctrl \n: Line feed

Source Code
To fix the issue, i index in SGR handling code at https://github.com/charmbracelet/sequin/blob/main/sgr.go#L39 needs to be incremented after the param.HasMore() check.
At least one .golden file also contains this error and also needs to be adjusted.
Expected behavior
Sub-parameters are checked for only once.
Expected:
$ echo -e '\e[4:1mUnderlined text, but no bold\e[m\n\e[4;1mBold AND underlined\e[m' | ./sequin
 CSI 4:1m: Underline (Single)
Text Underlined text, but no bold
 CSI m: Reset style
Ctrl \n: Line feed
 CSI 4;1m: Underline, Bold
Text Bold AND underlined
 CSI m: Reset style
Ctrl \n: Line feed

Screenshots

Additional context

Sub-parameter 0 needs additional consideration as it has effect of disabling the underline effect, but is currently reported as just "Underline"

To see proposed changes: https://github.com/charmbracelet/sequin/compare/main...mkotowski:sequin:fix/sgr4subparam?expand=1

Thank you, @mkotowski, for reporting this. It will be fixed in the next release 🙂

You're a beast @mkotowski. I'm very impressed.


Toggle button to expand and collapse categories missing

I have seen many people with the toggle option to open and close categories but I have searched the Toolkit and don't see that option anywhere. Any suggestions on where to find it or how to get it added to my toolkit?

Very perceptive of you.
I believe what you are looking for is called "Expands/Collapses Master Categories'' when you hover over it.
To enable this:

Menu-> Budget Screen
Tool-> "Category Solo Mode and Toggle Master Category Categories"
Select ''enable both'' from the dropdown menu offering.
press green save button within the toolkit chrome extension
Back on your YNAB web login, remember to 'refresh' to see it take instant effect.

Other YouTube resources for this toolkit usage:

Nick True - Mapped out Money:  https://www.youtube.com/watch?v=x4-igXQLEkw
He's great and user friendly (and very much great for showing the principle and varied applications)
Elizabeth Starr Harden:  https://www.youtube.com/channel/UCl0xsfiFlBnT6Qj9lIxWdcQ
Her video is compact, targeted and great for newbies.  Nick gives her a shout out in his video.

Let us know if that 'does the trick' once you've had a chance to tried it out.  I'm sure other would love to get your feedback; I'm a newbie too.
Two (2) pics to follow for reference:

toolkit link (chrome webstore):
https://chrome.google.com/webstore/detail/toolkit-for-ynab/lmhdkkhepllpnondndgpgclfjnlofgjl?hl=en
I hope this helps.
Nettie

Nettie, I can't thank you enough! I had watched Nick True's video and still for some reason couldn't find what I was looking for. I followed your steps and went right to it. Thank you also for including the images and being so thorough.
I appreciate the support from a fellow newbie!!!!
Kendria

Excellent news Kendria.  Glad I could help.
I’ll only made all my selections on the toolkit the other week so, it was somewhat ‘fresh in my mind’.
With, your question + my pics + your confirmation, hopefully this tread might also help some other Newbies (like us) 😉

Sounds like you guys got this one figured out! Going to close the issue. Please reopen if you have any other issues.


Migrate to .net core 2.0; Migrate to xUnit; Cleanup;

Migrate to .net core 2.0; Migrate to xUnit; Cleanup;

Thanks for this PR.
Will review.


Fix the recent problem in the CUDA test.

This is done by using cudaDeviceReset() only when the last executor on
the device is being deleted.

Some more information:
The problem is that cudaDeviceReset for some reason corrupts all the memory cuBLAS handles on the device. Interestingly, this does not happen for the cuSPARSE handles...
The fix proposes to count for each device how many executor are allocated. Only when the amount of executor on a device reaches 0 the memory is removed.
I did this count through a static array of ints and fixed the total number of devices on one node to 64 maximum. A better solution would be to template the CudaExecutor to have as parameter the device Id.  Then each template instance would have a separate static counter. The problem is this would imply to change quite a lot of code to template most CudaExecutor call.


Uninstalling

How to uninstall it?

You can just right click and press, "Uninstall" and then in your documents
you can remove the folder WSA
On Fri, Apr 28, 2023 at 2:24 PM notndricim @.***> wrote:

How to uninstall it?
—
Reply to this email directly, view it on GitHub
https://github.com/JimDude7404/WSA-Windows-10/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP72HFU2PPAGJQNHAJ2GA2DXDQDN5ANCNFSM6AAAAAAXPSAKCM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

You can just right click and press, "Uninstall" and then in your documents you can remove the folder WSA

Right click on what? It didn't make any kind of shortcut or icon, and nothing shows in programs and features.


Create the concept of objects and the guard on the square

This is an issue for creating the concept of objects (both animate and inanimate ones).

Create the IObject interface and the Guard class (inherits from IObject).
The Guard object should stand on the square and it should produce a random phrase if talked to.
Create the look around command that shows all the objects on current location.
Create the look at <object> command that prints the description of the object on current location.
Create the talk to <object> command. For now it can only talk to the guard. If talked to, the guard says a random phrase.

PR #16 closes this issue.


split the eval into multiple steps

Summary
address #159
Details and comments
See the eval method in operator.py for details.

this PR might fail without the PR in terra (has merged in the terra master) https://github.com/Qiskit/qiskit-terra/pull/1118
Failure case:
running VQE with statevector and pauli mode


Making nuxt-icon work?

Details
Is there a way to make the <Icon /> component from nuxt-icon work with the 'browser' rendering mode? That would be super epic!

Will investigate, would be good to support it

Maybe it's also an issue with the islands?
You can see the problem here: https://github.com/toniengelhardt/webapicheck
It's a simple component with some Uno classes and some icons in components/og/Default.island.vue.

Seems to be a core Nuxt issue with islands https://github.com/nuxt-modules/icon/issues/52
As a workaround, you can find the svg data on https://icones.js.org/ and paste it directly into the component

Perfect, thanks!
It's not super urgent, I'll wait for the fix in Nuxt.

Seems to be working correctly with the latest version of things, going to close this off.

Thanks 🙏🏽


Feature Request: way to edit systems' config

Operation System: all
Beaker Version: 0.3.0
Would be great to be able to modify the config of various tools (to change things like ports). Of course, most users should not have to do this, but while we're getting everything built, devs should be able to do this to run local nodes + beaker simultaneously.

And, yes, found the configs in
/Users/jbenet/Library/Application\ Support/Beaker\ Browser/IPFS/config

thanks to the path to beaker browser user data notice on the settings page.
but would be nice to either:

document that's the preferred way
or let it happen via the browser (probably harder, maybe dont even bother yet)
consider having a button that calls $EDITOR /path/to/system/config


Timers still not updating reliably after 4.6.5 fix

IMPORTANT: Please search the issues, including closed issues, and the FAQ before opening a new issue. The template is mandatory; failure to use it will result in issue closure.
Describe the bug

Alexa timers not being updated in HA reliably, even after the fix to the previous reports of this in 4.6.5
To Reproduce

Set an alexa timer, look at HA sensors.
Expected behavior
Timers should appear, count down, and get reset at end, or if the timer is cancelled.
Screenshots

System details

Home-assistant (version): 2023.6.3
alexa_media (version from const.py or HA startup): 4.6.5
alexapy (version from pip show alexapy or HA startup):
Amazon 2FA is enabled (y/n). <!---We will not debug login issues if unanswered--->: Y

Logs
Please provide logs.
I have a debug log but am not sure all sensitive info is removed? Serial numbers are mostly obscured but still appear in some URLs logged
Additional context

I have been waiting on this fix as I have some automations which rely on timers (for example, if a cooking timer on my kitchen echo ends, I send a TTS alert to other echoes in case we can't hear the kitchen). I installed 4.6.5 straight away this morning and tested. First time I set a timer, it wasn't picked up in HA at all. I then enabled debug log and set another timer, it also was not picked up in HA for around 30 seconds, so I then cancelled the timer, at which point it WAS then picked up in HA. So I then had the situation where HA had an active timer sensor, but there was no actual live timer on the alexa device. The only way out of this was to reload the integration.
I have the debug log for this, but as noted above, I am not sure that all sensitive info is blocked out of the log? I can see most occurrences of serial number are blocked out, but there are still some visible in URLs that are logged. Is this an exposure?

I'm also having this issue too.

I see in the discussion here - https://github.com/custom-components/alexa_media_player/pull/1974 - that this fix is probably the best that can be done right now considering that Amazon have stopped (temporarily? who knows) the call that the code previously relied upon to update the timer sensors. I can completely understand that, but putting that info in the fix and/or the original issue before closing that would be useful. As the timers are working right now, I can no longer use them in the automations I was previously using. Right now, setting a timer seems to get reflected in HA most of the time (sometimes after 30 seconds or more, sometimes just never), timers ending also get reflected most of the time, but cancelling a timer part way through hardly ever gets sent through to HA. The new mechanism might be the best available at the moment, but for whatever reason, on my system it just isn't reliable.

I have about 20 Alexa devices, and the timers have never worked at all in the roughly 1 year that I have been using Home Assistant, always showing "Unknown".  With this 4.6.5 release, they have started working for the first time. There is an inconsistent delay, usually a minute or two, but the timers work consistently except for a short timer that expires before the entity gets updated.

Dont know if we are facing the same issue.
I am using _next_alarm to automate blinds and so on and sadly they also get's not updated since about a month (~HA 2023/06).
Does _next_alarm entities works for you guys?

I have been testing this timer problem and I am fairly certain it is a timing issue to do with when the push_activity gets sent compared to when the previous command that is no longer being sent was. Sometimes setting a timer and then cancelling it updates HA as expected, sometimes the set never gets picked up, and then the cancel actually causes the HA sensor to update with the timer that was originally set. A subsequent voice interaction (anything, even just "alexa" with no command) then causes the sensor to revert to "Unknown" as it should have after the cancel. This behaviour led me to thinking that the information that is being fetched from Amazon when this push_activity is seen has (sometimes) not yet been updated with the timer info (either being set, or cancelled/stopped).
I started work in mainframe IT over 40 years ago, don't know python, don't know GIT and don't know the API details so forgive me if this is complete nonsense, but after this testing and looking through the code changes in the 4.6.5 fix I have found that putting a delay in at the point in __init__.py where the command is handled has completely eradicated the problem for me. With this in place, setting and cancelling timers, or stopping them when they expire, works every time (so far!), in that the HA sensor is always updated as expected. I have used 5 seconds, I started at a completely arbitrary 4 but for whatever reason that didn't always pick up a "stop" when a timer ends. This is clearly a bit of a bodge, it may cause problems or may be fixed better another way, but it doesn't seem to cause any problems elsewhere that I can see:
if command == "PUSH_ACTIVITY":
                if (
                    datetime.now().timestamp() * 1000
                    - hass.data[DATA_ALEXAMEDIA]["accounts"][email][
                        "last_push_activity"
                    ]
                    > 100
                ):
                    #  Last_Alexa Updated
                    last_called = {
                        "serialNumber": serial,
                        "timestamp": json_payload["timestamp"],
                    }
                    try:
                        _LOGGER.debug("timing fix - SLEEPING 5 SECS")     <===============
                        await asyncio.sleep(5)                            <===============
                        await coord.async_request_refresh()
                        if serial and serial in existing_serials:
                            await update_last_called(login_obj, last_called)
                        async_dispatcher_send(
                            hass,
                            f"{DOMAIN}_{hide_email(email)}"[0:32],
                            {"push_activity": json_payload},
                        )
                    except AlexapyConnectionError:
                        # Catch case where activities doesn't report valid json
                        pass
                else:

The result is a delay between the push coming in and the various API calls as seen here (edited):
2023-07-03 08:44:20.563 DEBUG (MainThread) [custom_components.alexa_media] d****p@p******m: Received websocket command: PUSH_ACTIVITY : ********
2023-07-03 08:44:20.563 DEBUG (MainThread) [custom_components.alexa_media] timing fix - SLEEPING 5 SECS
2023-07-03 08:44:25.867 DEBUG (MainThread) [alexapy.alexaapi] d****p@p******m: static GET: https://alexa.amazon.co.uk/api/dnd/device-status-list returned 200:OK:application/json
2023-07-03 08:44:25.923 DEBUG (MainThread) [alexapy.alexaapi] d****p@p******m: static POST: https://alexa.amazon.co.uk/api/phoenix/state returned 200:OK:application/json
2023-07-03 08:44:25.924 DEBUG (MainThread) [alexapy.alexaapi] d****p@p******m: get_entity_state response: {'deviceStates': *********
2023-07-03 08:44:26.157 DEBUG (MainThread) [alexapy.alexaapi] d****p@p******m: static GET: https://alexa.amazon.co.uk/api/devices-v2/device returned 200:OK:application/json
2023-07-03 08:44:26.361 DEBUG (MainThread) [alexapy.alexaapi] d****p@p******m: static GET: https://alexa.amazon.co.uk/api/bluetooth?cached=false returned 200:OK:application/json
2023-07-03 08:44:26.440 DEBUG (MainThread) [alexapy.alexaapi] d****p@p******m: static GET: https://alexa.amazon.co.uk/api/device-preferences returned 200:OK:application/json
2023-07-03 08:44:30.774 DEBUG (MainThread) [alexapy.alexaapi] d****p@p******m: static GET: https://alexa.amazon.co.uk/api/notifications returned 200:OK:application/json
2023-07-03 08:44:30.775 DEBUG (MainThread) [custom_components.alexa_media] d****p@p******m: Updated 7 notifications for 3 devices at 2023-07-03 08:44:30.775655+01:00

Someone has mentioned elsewhere that snoozing a timer still does not update HA with the extended time, I have found that with this delay in place that seems to work too.
Solving a timing problem with an arbitrary pause is obviously not a guaranteed 100% solution, there may well be occasions when 5 seconds is not enough, but it certainly seems good enough on my system for my needs now. Without it, it is far too hit and miss.

@dpgh947 nice find's!
Does ..._next_alarm entities also works for you?
In my case since HA 2023/06 it doesnt work, also not with 4.6.5.
When HA is restarted the correct ...next_alarm entities are read from the API, but when you enable/disable/change an alarm, the change is not picked up.

@dpgh947 nice find!
Does ..._next_alarm entities also works for you?
In my case since HA 2023/06 it doesnt work, also not with 4.6.5. When HA is restarted the correct ...next_alarm entities are read from the API, but when you enable/disable/change an alarm, the change is not picked up.

I don't use alexa alarms in HA but looking at the entities I can see that the relevant one was updated when I set an alarm last night for getting up this morning.

OK, hold your horses... this delay is sometimes causing the update of last_alexa to get delayed too...

@dpgh947 nice find!
Does ..._next_alarm entities also works for you?
In my case since HA 2023/06 it doesnt work, also not with 4.6.5. When HA is restarted the correct ...next_alarm entities are read from the API, but when you enable/disable/change an alarm, the change is not picked up.

I don't use alexa alarms in HA but looking at the entities I can see that the relevant one was updated when I set an alarm last night for getting up this morning.

EDIT - this edit update works on a raspberry pi install using HAOS, don't know about other platforms...

Have patched the file manually and restarted HA.
As before alarms got updated/loaded once HA was restarted but sadly not if i change the alarm time/day/repeat... in the alexa app. Will revert it for now.

It would be so nice if the alexa data (alarm/timers/...) would be reliable again.

I have also observed that alarms stopped updating with the 4.6.5 update reliably. With debug logging enabled, I noticed that I was seeing between 2 and 3 PUSH_ACTIVITY messages after setting or clearing an alarm and the duplicate suppression added in 4.6.5 (enforces a minimum of 100 second delay between subsequent PUSH_ACTIVITY being processed) was firing for the second and third occurrence of the PUSH_ACTIVITY message. I eliminated the duplicate suppression check and now find that the alarms are being processed reliably.
Incidentally, I've also observed that my Alexa routine that is set to fire when an alarm is dismissed also broke around the same time, so I suspect that Amazon's change may have unintentionally broke something in their own stack in addition to affecting this component. This gives me some hope they may revert the change.

I have also observed that alarms stopped updating with the 4.6.5 update reliably. With debug logging enabled, I noticed that I was seeing between 2 and 3 PUSH_ACTIVITY messages after setting or clearing an alarm and the duplicate suppression added in 4.6.5 (enforces a minimum of 100 second delay between subsequent PUSH_ACTIVITY being processed) was firing for the second and third occurrence of the PUSH_ACTIVITY message. I eliminated the duplicate suppression check and now find that the alarms are being processed reliably.
Incidentally, I've also observed that my Alexa routine that is set to fire when an alarm is dismissed also broke around the same time, so I suspect that Amazon's change may have unintentionally broke something in their own stack in addition to affecting this component. This gives me some hope they may revert the change.

Can you please give us details what to revert/change in the code to get alarms working reliable again?

I had also experimented with taking out that check for double PUSH_ACTIVITY calls, but couldn't see it making any consistent difference - but I don't use alarms in HA so wasn't looking at them then.
Trying to figure out what this code is actually doing, and what the intention is, when I don't know python or the way all this asynchronous handling of the push commands and the API hangs together is making my brain hurt, but here is what I have now done, which might be complete garbage but might point someone who does know what they are doing in the right direction:
The routine that handles(handled) PUSH_NOTIFICATION_CHANGE, and which I believe is therefore no longer being used at all, calls "process_notifications". That has code handling alarms, so I added a call to that to the PUSH_ACTIVITY routine where I had tried the delay,
if command == "PUSH_ACTIVITY":
                if (
                    datetime.now().timestamp() * 1000
                    - hass.data[DATA_ALEXAMEDIA]["accounts"][email][
                        "last_push_activity"
                    ]
                    > 100
                ):
                    #  Last_Alexa Updated
                    last_called = {
                        "serialNumber": serial,
                        "timestamp": json_payload["timestamp"],
                    }
                    try:
                        await coord.async_request_refresh()
                        #
                        await process_notifications(login_obj)            <================
                        #
                        if serial and serial etc........

I found this was also causing a delay in last_alexa getting updated like my first delay bodge did, because there is a sleep(4) in the process_notifications routine, so I took that out too,
async def process_notifications(login_obj, raw_notifications=None):
        """Process raw notifications json."""
        if not raw_notifications:
            #await asyncio.sleep(4)                                      <================ commented out
            raw_notifications = await AlexaAPI.get_notifications(login_obj)
        email: str = login_obj.email
        previous = hass.data[DATA_ALEXAMEDIA]["accounts"][email].get(
            "notifications", {}
        )

Having last_alexa updated promptly is important to me because I have lots of node red stuff that responds to custom alexa phrases and responds to the device spoken to using TTS.
With these changes (note check for double calls still in place), I have found that last_alexa gets updated promptly, my alarm entities are getting updated when I set/cancel alarms, and timers work completely reliably, with one exception that I have found so far - if you set a timer on one echo, and then cancel it from another, that change is never picked up in HA, due to the fact (I think) that there is no push seen coming from the original device in that situation. The only way to clear it is to speak something - anything - to the original device. Clearly it would be possible to update all timer sensors rather than just the ones for the device that is being dealt with because the info is there in the "notifications" API call result, but that is beyond my so-far-few-hours-worth of python experience....

I found a horrid work around for now.   When the current timer goes off in the kitchen. I send
service: media_player.play_media data:   media_content_id: go ding   media_content_type: custom target:   entity_id: media_player.kitchen_sonos
Which makes the Alexa go ding and the timer information is updated on the integration.

I found a horrid work around for now. When the current timer goes off in the kitchen. I send
service: media_player.play_media data: media_content_id: go ding media_content_type: custom target: entity_id: media_player.kitchen_sonos
Which makes the Alexa go ding and the timer information is updated on the integration.

That's clever, not horrid. What do you trigger that off?

When the current timer time is reached I trigger it.  It is not perfect but it helps.

Well it's not perfect, but I'm running with those changes above still. On the latest code I'd say timers work about 60% of the time, either not starting or not picking up when they are stopped or cancelled, and with the changes I've made it's about 98%. Very occasionally when I "stop" a timer that's going off, it doesn't update HA until I speak to it again.

Well it's not perfect, but I'm running with those changes above still.

@dpgh947 which changes, exactly? You have two comments here which different code changes.
I made all your suggested edits and my timer is more of a mess than it was with the vanilla 4.6.5 code.
Are you able to post a gist or full file of what you have working? Maybe I misunderstood your changes/which file to make them in. Thanks.

Ok I made that change (only those two changes) and snoozing is working GREAT. But now stopping the timer is impossible.
When the timer rings, I say "Alexa, stop timer" and the noise stops. However, HA's sensor datetime just updates to a new value, instead of returning to "unknown" which is what is expected.
I tried @jane-t 's service call and it also bumps the datetime - the the current time (time I made the call).
I tried reloading AMP, and same behavior. The datetime just changes from "12 seconds ago" to "now" (in datetime format of  course).
I tried talking to the Echo Dot and same behavior - it just keeps increasing the timer sensor time to the current time, causing infinite loops in my automations.

I have never seen anything like that, all I can think is the echo is screwed up somehow, try unplugging it and see if that clears it.

Well it's not perfect, but I'm running with those changes above still.

@dpgh947 which changes, exactly? You have two comments here which different code changes.
I made all your suggested edits and my timer is more of a mess than it was with the vanilla 4.6.5 code.
Are you able to post a gist or full file of what you have working? Maybe I misunderstood your changes/which file to make them in. Thanks.

Sorry if I caused confusion... it's just the updates in my latest post, forget my first attempt, so only adding the
await process_notifications(login_obj)

call at around line 927 and removing the sleep(4) at around line 677 (which was only put there in 4.6.5 but not explained), both these in __init__.py
EDIT - snoozing a timer that's going off works for me too.

thx for the hints.
I have changed the code and restarted HA.
Sadly alarms doesnt update, as it was before the amazon API changes.
Does alarms update for you?
thx

I found a horrid work around for now. When the current timer goes off in the kitchen. I send
service: media_player.play_media data: media_content_id: go ding media_content_type: custom target: entity_id: media_player.kitchen_sonos
Which makes the Alexa go ding and the timer information is updated on the integration.

This works perfectly for me on my daily alarm.  Thanks!

thx for the hints. I have changed the code and restarted HA. Sadly alarms doesnt update, as it was before the amazon API changes.
Does alarms update for you?
thx

I do see alarm entities updating when I set and clear alarms, yes, but I don't use them in ha so I can't say if they were working without my update anyway.

Nice to see that you are also facing these problems with alarms not updating. Sad that it's officially not working for ages anymore.
I did try the workarounds mentioned here and many thanks @popy2k14 for providing so many details.
I did try your code changes but cannot confirm that it's working for me sadly enough.
When changing it the whole integration won't start anymore. I guess it's because I'm running HA with Docker in a container.
I will follow the discussion further hoping to find a solution for me as well as it's annoying to restart HA every time I change the alarm in the Alex app :)

Well since yesterday, timers are completely broken for me, any changes only get picked up on integration reload, AND last_called is not being reliably updated either. Calling the alexa_media_update_last_called service does cause the last_called attribute to get updated, but just speaking to a device no longer does, although an update might randomly come through several minutes later... so either something is broken at amazon's end, or it's another deliberate change from them which is further breaking the api link to HA.

@dpgh947  How often are you reloading? I have had a daily reload set up for a while to address intermittent push notification failures but have considered implementing a more frequent reload to address the loss of push notifications that has manifested in the past few days. I'm concerned about hitting Alexa API throttle limits. My main use case is getting the next alarm time from the bedroom echos to schedule various wake up aiming
I've also been digging through the code base to figure out how to deactivate the old polling code. It appears to be controlled by a SCAN_INTERVAL configuration setting * 10 if web sockets is enabled, but I'm seeing no evidence that the polling is happening.

Well since yesterday, timers are completely broken for me, any changes only get picked up on integration reload, AND last_called is not being reliably updated either. Calling the alexa_media_update_last_called service does cause the last_called attribute to get updated, but just speaking to a device no longer does, although an update might randomly come through several minutes later... so either something is broken at amazon's end, or it's another deliberate change from them which is further breaking the api link to HA.

I've noticed starting yesterday the same awful behavior. Things were working well enough with that workaround code change until today. Maybe servers are messed up again.

@dpgh947 How often are you reloading? I have had a daily reload set up for a while to address intermittent push notification failures but have considered implementing a more frequent reload to address the loss of push notifications that has manifested in the past few days. I'm concerned about hitting Alexa API throttle limits. My main use case is getting the next alarm time from the bedroom echos to schedule various wake up aiming
I've also been digging through the code base to figure out how to reactivate the old polling code. It appears to be controlled by a SCAN_INTERVAL configuration setting * 10 if web sockets is enabled, but I'm seeing no evidence that the polling is happening.

How do you "reload" to get timers working again?
Can you please guide me in the right direction, so timers would get updated (at least once a day).
Thx

@dpgh947 How often are you reloading? I have had a daily reload set up for a while to address intermittent push notification failures but have considered implementing a more frequent reload to address the loss of push notifications that has manifested in the past few days. I'm concerned about hitting Alexa API throttle limits. My main use case is getting the next alarm time from the bedroom echos to schedule various wake up aiming
I've also been digging through the code base to figure out how to reactivate the old polling code. It appears to be controlled by a SCAN_INTERVAL configuration setting * 10 if web sockets is enabled, but I'm seeing no evidence that the polling is happening.

I am not doing a regular reload, it's a bit pointless for timers unless you do it say every 10 seconds, which would certainly break something. What I have done for now is update my node red flow that maintains the last_alexa sensor that I use in my TTS routines. I have added to that so that when it sees ANY change for a media player that ISN'T currently marked as the last_called,  it calls the update_last_called service. This has at least solved (for now) the last_called problem. Timers and alarms, well, they're just broken. Obviously something the integration does during startup is retrieving the info, so it should be possible to make that same call triggered off something (I don't know what) for the info to be updated on the fly like it used to, but I have not managed to figure that out.

@dpgh947 How often are you reloading? I have had a daily reload set up for a while to address intermittent push notification failures but have considered implementing a more frequent reload to address the loss of push notifications that has manifested in the past few days. I'm concerned about hitting Alexa API throttle limits. My main use case is getting the next alarm time from the bedroom echos to schedule various wake up aiming
I've also been digging through the code base to figure out how to reactivate the old polling code. It appears to be controlled by a SCAN_INTERVAL configuration setting * 10 if web sockets is enabled, but I'm seeing no evidence that the polling is happening.

How do you "reload" to get wakeup alarms working again in my bedroom? Can you please guide me in the right direction, so wakeup alarms would get updated (at least once a day).
Thx

You can reload any integration by calling the service homeassistant.reload_config_entry and give it the entity of anything that the integration controls. So in this case, any media_player.xxx  entity. Try it from the developer tools "services" tab. Then you can call it from an automation, or from a node red flow.

For those that actually understand how this code works (I certainly don't), this is what I have found in debug traces.
The timer updates used to get handled when a PUSH_NOTIFICATION_CHANGE command was seen. The last update to fix timers a few weeks ago was to alter this to when PUSH_ACTIVITY was seen, because for whatever reason amazon stopped sending the PUSH_NOTIFICATION_CHANGE.
Now, when I speak to a device, all I see coming in are PUSH_EQUALIZER_STATE_CHANGE and PUSH_VOLUME_CHANGE, so now it isn't sending PUSH_ACTIVITY either.

@dpgh947 How often are you reloading? I have had a daily reload set up for a while to address intermittent push notification failures but have considered implementing a more frequent reload to address the loss of push notifications that has manifested in the past few days. I'm concerned about hitting Alexa API throttle limits. My main use case is getting the next alarm time from the bedroom echos to schedule various wake up aiming
I've also been digging through the code base to figure out how to reactivate the old polling code. It appears to be controlled by a SCAN_INTERVAL configuration setting * 10 if web sockets is enabled, but I'm seeing no evidence that the polling is happening.

How do you "reload" to get wakeup alarms working again in my bedroom? Can you please guide me in the right direction, so wakeup alarms would get updated (at least once a day).
Thx

You can reload any integration by calling the service homeassistant.reload_config_entry and give it the entity of anything that the integration controls. So in this case, any media_player.xxx entity. Try it from the developer tools "services" tab. Then you can call it from an automation, or from a node red flow.

thx a lot. triggering the reload now every 10 minutes and the wakeup alarm times get's updated!
The intervall of 10 minutes suffice for my use case scenario.
Above you mentoned an API throttle limit, will 10 minutes work well and dont trip the limit?
In other words, how fast can i go without tripping it?
Are there any disadvantages to reload the config in an intervall?
PS.: I dont have looked at the code, so dont understand it either, but would polling get back most of the functionallity. Sure with delays, but maybe with this we can use the addon again?
thx

@popy2k14  That wasn't me commenting about the throttle limit and polling... I've seen that code, but I don't understand that either.

Oh, sorry :-)
PS.: Polling with homeassistant.reload_config_entry does not work reliable when calling every 10 minutes.
Now the error pops up:
[139733845156112] Error handling message: The config entry<EMAIL_ADDRESS>- amazon.de (alexa_media) with entry_id 54f659544acf0f0e10c8032069970908 cannot be unloaded because it is not in a recoverable state (ConfigEntryState.FAILED_UNLOAD)
And alexa media.player doesnt work anymore.
All entities are unavailable!

For my echo dot 5th the update never works.
The only way is reinitialize the complete integration.

As a workaround for wakeup alarms I have now created virtual lights for every bedroom and exposed them in emulated hue.
Alexa can use an wakeup light for all alarms, which is now set to the individual virtual light. So I can react in HA's automations again.
This way it's better than using Alexa's wakeup routine, because you can set an wakeup light per Alexa device and they also stick on new alarms for reach device.
So a family member can not mess the alarms up so quickly or forget to add an routine 😉
Hope this helps

Not sure if this is related but I have noticed that the total_active attribute is not getting updated. I use this to determine whether a timer has been started and then display an actual timer on a dashboard. For me the total_active won't update unless I reload the integration.

Now, when I speak to a device, all I see coming in are PUSH_EQUALIZER_STATE_CHANGE and PUSH_VOLUME_CHANGE, so now it isn't sending PUSH_ACTIVITY either.

This is a key point. If Amazon has disabled this, then there will be no updates possible without going the polling route.

Above you mentoned an API throttle limit, will 10 minutes work well and dont trip the limit? In other words, how fast can i go without tripping it?

You'll know you've hit the limit when your account gets blocked or all of us who use the API get blocked. Amazon doesn't publish that type of info.

has anyone found a work around for this? I know reloading the integration gets the timers to show up but theres no way to automate a reload of an integration (as far as I am aware?)

has anyone found a work around for this? I know reloading the integration gets the timers to show up but theres no way to automate a reload of an integration (as far as I am aware?)

You can do this: https://github.com/custom-components/alexa_media_player/issues/1992#issuecomment-1662908144
But don't run it too frequently or your developer account will get locked out. This means it is only really useful for Alarms which don't require real time updates.

has anyone found a work around for this? I know reloading the integration gets the timers to show up but theres no way to automate a reload of an integration (as far as I am aware?)

You can do this: #1992 (comment)
But don't run it too frequently or your developer account will get locked out. This means it is only really useful for Alarms which don't require real time updates.

thanks for this - I thought I could activate it with "last_call" to reload the integration when I said the word "timer" but last_called does not update anymore either without a reload so I am fresh out of ideas

I used to use IFTTT before I really got in to HA, and I remembered that had a trigger for when an alexa timer goes off. I just looked and that trigger is still there, and interestingly it still works, so there's a mechanism of sorts somewhere that is still in place...

I think what we are seeing is the gradual complete shutdown of this api by amazon (just about). I am now not seeing ANY updates to media player entities coming through at all. I have had to completely change the way I handle the "last alexa" - I now cannot maintain this based off the activity that used to be seen whenever any device was spoken to. The only way it will work now is to call the update_last_called service whenever I am about to send a TTS announcement and I have not specified a target (in other words, I want it sent to the device spoken to). That service still works at the moment...

Any updates on this?
None of my automations work properly, lack of entity updates from the integration.
Can we have an "workround" version which just polls, until the notification method work again (or is shutdown completly :-( )
thx

I have no update but a workaround for alarms that I have tested for a while and that I'm using now.
(sorry if the code section is not working fine I tried)
Information
Workaround works for:

Trigger an automation at the time the alarm goes off

Workaround does not work for:

Trigger an event before the alarm goes off

Description

Create a boolean trigger helper switch via settings / devices / helpers
Add the "Emulated Hue" integration via editor and configuring the configuration.yaml (example):

emulated_hue:     type: alexa     host_ip: your_home_assistant_ip     listen_port: 80     expose_by_default: false     entities:       input_boolean.you_alarm_trigger_helper_name:         name: "Alarm trigger“ helper         hidden: false

Save configuration.yaml and restart HomeAssistant
After reload has finished open your Alexa app and ask her to detect new devices
After a while she will announce to have found new devices
Within section "lamps" you will find a lamp called like your trigger alarm helper
Within alarm settings set a new alarm as you wish and activate a "wake-up light"
Within general alarm settings you can select the wake-up light for each Amazon device separately
Here select the "lamp" named like your alarm trigger helper
You can adjust the time before the alarm but this has no effect on the trigger
If everything works fine you can see a little star next to your set alarm

Now when the alarm goes off the trigger will be switched "on" within HomeAssistant.
Within HomeAssistant now you can set up an automation when the helper is switched "on" and react on this and after going through your steps deactivate the trigger again so that it works again next time.
Hope that helps some of you to achieve something independent from Amazon API.

I've implemented a similar solution to @NivaBarCar above, however I have it able to trigger up to an hour before the scheduled alarm.
Instead of using Emulated Hue, I'm exposing my device to Alexa using the standard Alexa Skill/Home Assistant Cloud integration. In addition, I'm using a virtual "light" entity instead of the input_boolean. The virtual light entity is created by the Virtual Components custom component:
https://github.com/twrecked/hass-virtual
By exposing a dimable light to Alexa instead of an on/off switch, the wake-up light before alarm setting in Alexa works. You can specify up to an hour before the alarm time. Alexa will start with the "light" set to low brightness and gradually increase it to 100% by the time alarm time is reached. With a switch, that setting is ignored and she simply turns on the light at the alarm time.
My automations don't care about the dimming level. They simply trigger when the "light" transitions to on, so they fire as soon as Alexa starts the wake up lighting sequence.

I've implemented a similar solution to @NivaBarCar above, however I have it able to trigger up to an hour before the scheduled alarm.

Thanks for sharing @elarsson1. You are right by mentioning that in case you use the cloud integration this works "better".
My solution is based on not having the integration and not paying anything additional to use the Nabu Casa Service.
But very nice that you are sharing your solution as well!

Did anyone figure out a way to fix the timer/last called feature. I just want the timers to show without spamming the API

@NivaBarCar I suspect you could get this to work with Emulated Hue just as well, rather than relying on the Alexa skill and the HA Cloud subscription. The key, I believe, is using a light entity instead of an input_boolean (which shows up in Alexa as an on/off switch) as the trigger. You could create a virtual light, that is dimmable, using the Virtual Components and expose that via Emulated Hue instead of the input_boolean and then Alexa would be able to turn it on at low brightness before your schedule alarm time.

I have no update but a workaround for alarms that I have tested for a while and that I'm using now. (sorry if the code section is not working fine I tried)
Information Workaround works for:

Trigger an automation at the time the alarm goes off

Workaround does not work for:

Trigger an event before the alarm goes off

Description

Create a boolean trigger helper switch via settings / devices / helpers
Add the "Emulated Hue" integration via editor and configuring the configuration.yaml (example - exchange - with spaces please):

emulated_hue: --type: alexa --host_ip: your_home_assistant_ip --listen_port: 80 --expose_by_default: false --entities: ----input_boolean.your_alarm_trigger_helper_name: ----name: "Alarm trigger helper" ----hidden: false

Save configuration.yaml and restart HomeAssistant
After reload has finished open your Alexa app and ask her to detect new devices
After a while she will announce to have found new devices
Within section "lamps" you will find a lamp called like your trigger alarm helper
Within alarm settings set a new alarm as you wish and activate a "wake-up light"
Within general alarm settings you can select the wake-up light for each Amazon device separately
Here select the "lamp" named like your alarm trigger helper
You can adjust the time before the alarm but this has no effect on the trigger
If everything works fine you can see a little star next to your set alarm within Alexa app

Now when the alarm goes off the trigger will be switched "on" within HomeAssistant. Within HomeAssistant now you can set up an automation when the helper is switched "on" and react on this and after going through your steps deactivate the trigger again so that it works again next time.
Hope that helps some of you to achieve something independent from Amazon API.

:-)
that's the exact workaround i have implemented for all my wakup light's and the work reliable!
But i have automations which checks if something is playing and if not play something.
That does'nt work because the integration has no current play status.
Is there also an workaround?

Now, when I speak to a device, all I see coming in are PUSH_EQUALIZER_STATE_CHANGE and PUSH_VOLUME_CHANGE, so now it isn't sending PUSH_ACTIVITY either.

This is a key point. If Amazon has disabled this, then there will be no updates possible without going the polling route.

Above you mentoned an API throttle limit, will 10 minutes work well and dont trip the limit? In other words, how fast can i go without tripping it?

You'll know you've hit the limit when your account gets blocked or all of us who use the API get blocked. Amazon doesn't publish that type of info.

Any chance to get volume updates working?
Thx

I was going to implement @elarsson1 's idea but found out Timers (which I used for tons of cool automations) don't provide any Alexa-side routine or trigger effects like the wake-up lighting. So i'm still looking for a better way to workaround this for timers. I suppose I can create a routine that creates an alarm when asked a certain way, which might be the way to do it for now.
As of now, I've increased my "completely reload the Alexa integration" automation from every 12 hours to every hour, and even that is fairly useless for timers, since A) it doesn't capture snooze command changes and B) many timers are created on the fly and expire within the hour.
I could increase the integration reload frequency more but I read I will start getting throttled...

Issue still exist for newest update 4.7.0

@alandtse
Is it possible to get an poll feature and/or poll service?
So if users automations are using data from Alexa (timers, alarms, volume, ...) are working again?
I know we can't poll too often, but maybe some automations can work again.
Thx a lot

Updated to 4.7.1 and still not working for timers.

Same for me 4.7.1 is still broken.

Please review the release notes. Neither of the releases that came out recently promise or describe any fixes to this situation. Do not expect it to be magically fixed when the number goes up.

The only thing that will fix timers is Amazon reverting the api changes they made which broke them in the first place. The only dependency I had on timers in HA was an automation that announced in the lounge if a kitchen timer went off. It was pretty useful when I was cooking and wandering about, it's a shame it's gone, but I've quickly learned to do without it.

Follow #1953 for update since it's the same root cause now. Closing dupe.


Wrapping and Implementing Syncfusion (Or Other) Controls

Hey guys! AMAZING work on this project so far! I saw the conference on this and got so excited I had to leave the room for a moment 😆. The question is though, so I'm playing around with this and I'm absolutely LOVING how logical this all feels to me and how it just "makes sense," but the one thing I'm struggling with is figuring out how to get something like, for example, a Syncfusion SfPicker in the frontend. I can create the control programmatically, but I'm not sure how to access it from the non-code portion of the Razor page. I've also tried (admittedly not long) to figure out how to wrap them like I saw the PancakeView was wrapped, but I can't figure out what the element (Calling it the "SyncPicker") should inherit from. I know the SfPicker itself inherits from View (among other things), but if I use View to inherit from with my SyncPicker, I can't register the element handler. I'll admit this is probably a little out of my skill set but this is just so intriguing to me I can't help but ask! Thank you guys again for all of your time and hard work to make people like myself's lives easier! 😄

Hi @CtrlAltNoot thank you for the kind words! Making it easier to integrate with 3rd party components is definitely one of the goals of this project because we know there are a ton of super popular components out there.
Looking at the PancakeView sample, or even any of the built-in components (+ handlers) is probably the best way to get started. In general, everything in the Mobile Blazor Bindings wrappers mirrors the Xamarin.Forms world. So if you have a Xamarin.Forms control that derives from Xamarin.Forms.View, then your Mobile Blazor Bindings wrapper would derive from Microsoft.MobileBlazorBindings.Element.View (and its handler would derive from Microsoft.MobileBlazorBindings.Element.Handlers.ViewHandler).
If you can share what you've got started I'd be happy to walk you through the steps!

@inject ILotMasterService lotMasterService
@using Syncfusion.SfDataGrid

@if (glotmasterfields == null)
{
    <Label Text="Click Fetch Data Button" FontSize="20" />
}
else
{
    <syncfusion:SfDataGrid ItemsSource="{Binding glotmasterfields}">

        <syncfusion:SfDataGrid.Columns x:TypeArguments="syncfusion:Columns">

            <syncfusion:GridTextColumn HeaderText="Yard Number" MappingName="YardNumber" />

            <syncfusion:GridTextColumn HeaderText="Lot Number" MappingName="LotNumber" />

            <syncfusion:GridTextColumn HeaderText="Pen Number" MappingName="PenNumber" />

            <syncfusion:GridTextColumn HeaderText="Lot Name" MappingName="LotName" />

            <syncfusion:GridTextColumn HeaderText="Weight Pay Tot" MappingName="WeightPayTot" />

            <syncfusion:GridTextColumn HeaderText="Weight Off truckAvg" MappingName="WeightOfftruckAvg" />

            <syncfusion:GridTextColumn HeaderText="BreedCode" MappingName="BreedCode" />

        </syncfusion:SfDataGrid.Columns>

    </syncfusion:SfDataGrid>

}

@code {
[Parameter]
public IList<Lotmasterfields> glotmasterfields { get; set; }

}


Update default Julia environment and SymbolServer versions

The Julia version (1.0 -> 1.2) is for convenience (latest stable release). The SymbolServer version is the most recent (0.2.4 -> 0.2.5) due to the previous version throwing errors for me.

As I already had updated LanguageServer.jl independently, I am just going to close this. I still think there should be done something about lsp-julia-default-environment, but for now, I think it is better if a Julia 1.2 language server gets the Julia 1.0 environment than the other way round.

No worries!


Complete code hygiene, use best practices for javascript

From Tamas:
Due to fast prototyping (as I know) the code is now a spaghetti code. Lets add some structure to it. Use Javascript Design Patterns like the revealing module patternto create a strong code foundation for this project! There could be private or public modules depending on where we'd like to use the function in question. For a well structured application with revealing module pattern see http://harbourstudios.com/fulfillment/brookfield_locator/ from my portfolio

Totally agree here. I'll defer to you on best practice. I think a revealing module pattern could work. Something easy to maintain and for other folks to jump into. I'd say this is top priority for me as it'll set the codebase up to be easier to maintain in the long run.

@searoutefinder - saw you started this and it's much better now than before 👍

This is addressed by #20


Nvss 653 bfdr update

Summary

ran scripts to pull in terminology and CM changes from BFDR + VRCL
updated examples and references to updated valuesets/codesystems where errors arose
incorporated BFDR changes (adding FJI extension, removing old codesystems)

Should be a pull request for fetal-death-feature not main


Fix markdown in readme

the enmity link just links recursively to catppuccin/enmity, it should link to the enmity site or github
if this is for a reason feel free to ignore

Changed to Enmity’s GitHub


Better mesh grid generation

Hi,
In siren_pytorch.py, the coordinate mesh grid is generated by the following codes:
tensors = [torch.linspace(-1, 1, steps = image_width), torch.linspace(-1, 1, steps = image_height)]
mgrid = torch.stack(torch.meshgrid(*tensors), dim=-1)
mgrid = rearrange(mgrid, 'h w c -> (h w) c')
self.register_buffer('grid', mgrid)
However, the shape of the mesh grid generated by the first two lines of code is (w, h, c). Thus, the output shape of the following codes should be ((w, h), c) (not ((h, w), c) ):
out = self.net(coords, mods)
It would be better to modify the original codes into:
tensors = tensors = [torch.linspace(-1, 1, steps = image_height), torch.linspace(-1, 1, steps = image_width)]
mgrid = torch.stack(torch.meshgrid(*tensors), dim=-1)
mgrid = rearrange(mgrid, 'h w c -> (h w) c')
self.register_buffer('grid', mgrid)
Several experiments have been conducted to verify the effectiveness of the modification.

@OctoberKat oh hey! crap, i believe you are right! can you let me know if the latest version fixes things? :pray:

oh my! i really hope this was the source of a maddening inability to get something to work in my project that uses this!! definitely looks like the culprit!  everything worked with square output, but broke and gave poor strange distorted results for anything where w != h ... i spent countless nights trying to find the cause or mistake, but eventually gave it a rest for a while. can't wait to get home and test the update.


Watch mode does not auto re-run tests

it does.

I uninstall watchman and install it again, the problem is solved.


Service Interruption: suspected OOM

(investigate today)

Seems that when there's too many (we are saying actually just 10-ish) connections to the Postgres DB, due to the fact that database/sql.DB is pooled by default, the connections are persisted and reused by the pool and each connection could elapse for an indefinite of time.
This created an issue on Postgres but the actual root cause is still unknown, as it sounds just not right to persist transaction data in the whole connection lifetime rather than just throw it away after the transaction completed. More investigation required.
A workaround (ada2b921c88c2e7b064ae8eb1726b63eaf0f45bc) has been implemented as it limits the connection pool size on the backend size to reduce the ram impact, but the root cause is still remain to be solved.

What actually happened on the server? Was the service killed by OOM killer or panicked?
However, it's quite interesting and puzzling...

My opinion would be to check the pg_stat_activity first. If there are more idle than active connections, pgBouncer or similar tools can be a big benefit.


Problem with fingerprint

        () => reject(new Error(`Timed out while calling the "${name}" method.`)),
                     ^

Error: Timed out while calling the "fetch" method.
at Timeout._onTimeout (C:\Users\indep\microsoft-account-creator\node_modules\browser-with-fingerprints\src\plugin\connector\index.js:48:26)
at listOnTimeout (node:internal/timers:581:17)
at process.processTimers (node:internal/timers:519:7)

dude, how did you solve this problem?


Improve typings and README

Adds some improvements to the types on task constructors to enforce the context is treated as read-only by the effect and action functions. This ensures tasks can only modify the state referenced by their lens.
This also fixes some errors on the README
Change-type: minor

I self-certify!


Imported computed variable mixin not working in Safari

Versions

nuxt: v2.15.8
node: v15.8.0

Reproduction
https://deploy-preview-3--wild-co.netlify.app/styleguide/

Additional Details

Steps to reproduce
This is my first ever issue so forgive me if I'm not sharing enough of the scenario.
So basically I created a matchMedia mixin because I was reusing the computed property a lot. Here it is:
import { theme } from<EMAIL_ADDRESS>
export default {
  computed: {
    isSmBreakpoint() {
      return window.matchMedia(`(min-width: ${theme.screens.sm}`)
    },
  },
}

What is Expected?
Once I imported the mixin into a file, I use it as normal in methods across the file e.g.
addScrollLockListener() {
    this.setScrollLock()

    // Fallback for Safari 13 support
    if (this.isSmBreakpoint.addEventListener) this.isSmBreakpoint.addEventListener('change', this.setScrollLock)
    else this.isSmBreakpoint.addListener(this.setScrollLock)
},

setScrollLock() {
  this.$toggleScroll(this.isSmBreakpoint.matches ? false : this.isMenuOpen)
},

What is actually happening?
On Safari v13, 14 & 15, it's suddenly stopped working. No clicks fired at all when this.isSmBreakpoint.matches is used until I commented them all out on the file I imported the mixin into. However, when I commented the machMedia computed property
back into the file directly instead, it works again! Really not sure what's going on as Chrome and FF seem to have no issues.

return window.matchMedia((min-width: ${theme.screens.sm}) missing a bracket...jesus wept


nixos/thinkfan: rewrite for 1.2 update

Motivation for this change
nixos/thinkfan: rewrite for 1.2 update
Thinkfan underwent some major changes and the config file
is now based on YAML. This commit contains a number of changes:

rewrite the module to output the new format;
add a settings option, following RFC 00421;
add fancy type-checking for the most critical options
use upstream systemd units (which fix the resume issue)

Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS)
Built on platform(s)

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

[x] Tested services.thinkfan.enable on my machine with NixOS 20.09
[x] Built NixOS manual
[x] Tested compilation of all pkgs that depend on this change (thinkfan)
[x] Tested execution of all binary files
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc: @domenkozar (are you still using thinkfan?)

Note: I may have gone a bit too far with all the type-checking, but given thinkfan can literally melt your computer if you make a mistake, I'm not so keen on removing it.

Sucessfully tested the module with
  services.thinkfan = {
    enable = true;
    sensors = [
      { type = "hwmon";
        query = "/sys/class/hwmon";
      name = "coretemp";
      indices = [ 1 2 3 ];
    } ];
  };

Works even after suspend resume.
The fact that sensors does not fully respect the structure of the original yaml file is a bit disturbing, but after reading carefully the option descriptions I could get it to work.

The fact that sensors does not fully respect the structure of the original yaml file is a bit disturbing, but after reading carefully the option descriptions I could get it to work.

I agree it would be better to stick to the original structure. I did it this way in order to check the sensor type, which is a key (not a value). I guess I could use assertions instead of a typed option, what do you think?

Maybe just add to the documentation of the settings option an example, and what it corresponds to in upstream documentation?
Adding an option per type would be confusing in the option search.

Maybe just add to the documentation of the settings option an example, and what it corresponds to in upstream documentation?

If you mean settings literally, then the syntax is identical to upstream: the Nix value is converted to YAML 1:1. Otherwise, yes, I could write an example for thinkfan.sensors.

Yes sorry, I meant the documentation of the sensors option, not settings.

I added an extraArgs option because there is no way pass an option without also loosing the -c thinkfan.conf. I needed this to change the bias, which can't be done from the configuration.


chore: clean vite-local

Summary
The TGPTController is responsible for returning the connection information for beaker - e.g. the websocket address, jupyter-token ... etc. Currently instead of returning these information, the server returns the client address with dummy-routes, and then the client routes again based on the running configuration. This creates a weird circular double-proxy situation where the client needs to know the server and the server needs to know the client.

client asks server how to connect to beaker
server returns dummy client routes
client connects through these routes
the routes are intercepted by the client and rerouted to actual beaker host

This can be simplified by just getting the client to connect directly, so

client asks server how to connect to beaker
client connects through these routes

Will revisit later


CB-8031: Update pillar configuration when starting cluster

Co-authored-by: Brian Towles<EMAIL_ADDRESS>When a datalake or datahub is started, update the pillar
configuration. This ensures that if the FreeIPA IP addresses changed
while the datalake was stopped then cloudbreak will update the FreeIPA
IP addresses when starting the stopped instances.
This was tested manually by ensuring the pillar configuration was
called on a local instance of cloudbreak.
See detailed description in the commit message.

I checked the changes, the flow modifications look ok. But I believe this pillar refresh should happen earlier in the start flow. Because now it would refresh the pillars and configs via HighState after the start of CM server, agent and all the services.
I think the services couldn't be started if a config change is necessary in the Freeipa related configs especially if the server address has been changed then they are not able to gather new auth tokens from Freeipa.
cc @lacikaaa

I updated the start flow to update the DNS IP addresses at the first step in the flow.

@wonderslug wanted me to check 1 more thing in regards to ensuring the node is fully online when doing the pillar update so I am marking it DO_NOT_MERGE until that is manually validated.

StartFlowEventChainFactory has a chain with STACK_START_EVENT and CLUSTER_START_EVENT. The stack will always be started before the pillar update starts.
This can be committed after @lacikaaa reviews it.


Option to change position of Arrow Points

This is something that I was thinking when implementing multi point arrows. I suggest to add a UI to the panel for arrows that can set the position of each arrow. There are going to be four modes: At Start, At End, In Both Sides, and Nothing. If we implement this, we won't even need the line shape anymore because lines will be arrows with "Nothing" selected as arrow points.
Since I have set up migration from old arrow spec to a new one in the app, I can extend that logic for line shapes to convert them to arrows.
Naming shouldn't matter -- we can call the shape arrow or line; plus we can also use the last value stored for the arrows to change the tool's icon.

We should definitely keep the line and arrow as separate icons without extra configuration, regardless of how they implemented underneath.

I've discussed this with @vjeux previously a we decided to keep the line and arrow separate tools, as @lipis mentions.

I am already working on making lines and arrows the same (#660). If the first part of this issue is desirable (e.g we can enable arrow position tool only for arrows and keep lines as is), I will work on it after line PR is finished.

Yes, the part about changing arrow ends is fine. In time we'll also want to support other types of ends such as https://github.com/excalidraw/excalidraw/issues/616, I reckon.
The ability to switch arrow ends may seem not that important, but one use case could be that someone draw some complicated arrow diagram and decides the relationships should be swapped, in which case it would be cool to simply switch the arrow end instead of trying to rotate the arrow.

Duplicate of #616


feat: new aapt1/aap2 binaries for mac (static)

fixes #2477 for real
https://github.com/iBotPeaches/platform_frameworks_base/pull/12

➜  macosx git:(aapt1-static-mac) otool -L *
aapt2_64:
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1292.100.5)
aapt_64:
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1292.100.5)
➜  macosx git:(aapt1-static-mac)

Only failure was a one-off on Windows, so ignoring.


Add LWE/CGGI parameters and passes to set defaults

After our chat, I had to add two more things:

convert function signatures in the LWE default setting pass
support adding the default LWE params attribute on lwe.trivial_encrypt ops

Due to an issue with copybara integration, this was merged squashed with https://github.com/google/heir/commit/5b025b1b2d8786a15867ea8ff7ca7894108ee279