Fix #3127 redirect trailing slash using 301 statuscode

Fixes:
#3127
https://github.com/getgrav/grav-plugin-sitemap/issues/87

This should be already fixed in Grav 1.7: https://github.com/getgrav/grav/blob/1.7/system/src/Grav/Common/Processors/InitializeProcessor.php#L422

This should be already fixed in Grav 1.7: https://github.com/getgrav/grav/blob/1.7/system/src/Grav/Common/Processors/InitializeProcessor.php#L422

This is also not fixed in 1.7
The redirect still uses 302 instead of 301. I have no solution for this yet.

This is also not fixed in 1.7
The redirect still uses 302 instead of 301. I have no solution for this yet.

I mean that the code does not redirect from the server root, which fixes the redirect loop.
I don't want to use 301 for redirects ever, especially on development sites. I've broken my sites so often with 301 and the only way is to clear all the cache from your browser. That itself isn't bad, but I've also wasted my time trying to locate a bug that isn't there.
I can work with a configurable redirect code, though.

I mean that the code does not redirect from the server root, which fixes the redirect loop.
I don't want to use 301 for redirects ever, especially on development sites. I've broken my sites so often with 301 and the only way is to clear all the cache from your browser. That itself isn't bad, but I've also wasted my time trying to locate a bug that isn't there.
I can work with a configurable redirect code, though.

I do not understand the problem with the redirect code. But it is a fact, that 302 is wrong here and will cause bad SEO results.

I do not understand the problem with the redirect code. But it is a fact, that 302 is wrong here and will cause bad SEO results.

Manually added the fix.


 If you are implementing more than one, separate them with the ~ operator, I did it like this to divide and create an array.
Example: https://localhost:3000~https://localhost:8080 or https://localhost:3000

https://i.imgur.com/c6Rww0f.png Its throwing this error any solution ?

check the server and verify that the environment variables do not have an undefined value.
You can do a console.log in src/utils/.env.ts and see what happens


Update Chapter Card Descriptions for Better Alignment with Titles and enhancing the total page !!

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]
Fixes:  #4823
Description
This PR introduces a hover effect for the chapter cards, improving user interaction and visual engagement. The following changes have been made:

Card Background on Hover:

The background color of the cards changes to a light pink (#ffb6b9) when hovered.

Title Hover Effect:

The card title becomes larger (2em), bold, and transitions to a darker shade of pink (#b36b6b) on hover for better visibility.

Text and Subtitle Color:

The subtitle and content text color changes to white when the card is hovered, improving contrast against the background.

Smooth Transitions:

All color and size transitions occur smoothly for a better user experience.

Changes Include:

Updated CSS to apply the hover effect to .chapter-card and .card-title.
Adjusted the transition properties for smooth color and size changes.
Updated the descriptions of the chapter cards for a more cohesive theme. Each card now features content that ties in better
with the title and explores concepts of greatness, heroism, and discovery.

Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
BEFORE:

AFTER:
Added cursor effect , hovering effect and rechanged the cards styling and added content to the cards !!

Checklist:

[x] I have made this change from my own.
[x] I have taken help from some online resources.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

Resolve conflicts @SrijaVuppala295

@sailaja-adapa , resolved

@sailaja-adapa , please add level 3

@abhi03ruchi , @atmajaa , please add level 3 label


Accessibility update - Mostly Semantic

Rearrange the block layout for better semantic:

Header [Include Navigation] -> Main -> Footer
Navigation is now a list of links
Minor changes to focus color on nav links for better distinction from blue background.

Rearrange the block layout for better semantic:

Header [Include Navigation] -> Main -> Footer
Navigation is now a list of links
Minor changes to focus color on nav links for better distinction from blue background.

Also added Home link to navigation and removed the background link.

Also one of the test failed but I don't know why... Does the rerun happen automatically?


Implement timeout to align with client's socket read timeout of 3 seconds

Currently the websocket read timeout used by XRPL clients is 3 seconds and if server doesn't response within the 3 seconds, client will receive socket timeout, however the Clio server side doesn't have such timeout guarded and would continue its processing and return the respond even though the underline connection had already been abandoned by the client. We need a mechanism to stop this silent errors by implementing mechanism to keep track of request's connection duration to align  with client's timeout and raise exception/error when the processing exceeds the timeout value.
Alternatively we need to look into the XRPL client implementation to see if it's possible to negotiate the timeout value since if client is requesting large amount of data, there's a chance that the 3 seconds is not sufficient for server to fulfill.

See if we can get timeout from the request header

The "fix" that was attempted and later discarded was only applicable to WebSocket but not to normal HTTP due to protocol limitations. There isn't much we can do about this without introducing some artificial timeouts etc. which still are not a real solution either. Also we have fixed some other problems that could have caused this kind of behaviour but never heard back if this problem was reproduced again or not. Closing due to inactivity. Please re-open if the problem persists.


Error when creating wallet - TypeError: Cannot perform %TypedArray%.prototype.set on a detached ArrayBuffer

Describe the bug

Lodestar throws the following error when attempting to create a wallet using the yarn run cli account wallet create command:
TypeError: Cannot perform %TypedArray%.prototype.set on a detached ArrayBuffer

Expected behavior

A wallet should be successfully created
Steps to Reproduce

Install yarn

curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
sudo apt upgrade
sudo apt install yarn

Compile Lodestar

git clone https://github.com/chainsafe/lodestar.git
cd lodestar
yarn install
yarn run build

Attempt to create wallet

yarn run cli account wallet create --name myLodestarWallet --passphraseFile ~/eth2/myLodestarWallet.pass --rootDir ~/.lodestar

This gives the following error:
yarn run v1.22.4
$ node --trace-deprecation ./packages/lodestar-cli/bin/lodestar account wallet create --name myLodestarWallet --passphraseFile /home/larry/eth2/myLodestarWallet.pass --rootDir /home/larry/.lodestar
 ✖ TypeError: Cannot perform %TypedArray%.prototype.set on a detached ArrayBuffer
    at Buffer.set (<anonymous>)
    at _copyActual (buffer.js:261:10)
    at Function.concat (buffer.js:573:12)
    at Function.encrypt (/home/larry/eth2/lodestar/node_modules/@chainsafe/bls-keystore/lib/keystore.js:73:38)
    at Function.fromMnemonic (/home/larry/eth2/lodestar/packages/lodestar-cli/lib/wallet/Wallet.js:59:25)
    at WalletManager.createWallet (/home/larry/eth2/lodestar/packages/lodestar-cli/lib/wallet/WalletManager.js:109:35)
    at Object.handler (/home/larry/eth2/lodestar/packages/lodestar-cli/lib/cmds/account/cmds/wallet/create.js:83:32)
    at Object.runCommand (/home/larry/eth2/lodestar/packages/lodestar-cli/node_modules/yargs/lib/command.js:240:40)
    at Object.parseArgs [as _parseArgs] (/home/larry/eth2/lodestar/packages/lodestar-cli/node_modules/yargs/yargs.js:1154:41)
    at Object.runCommand (/home/larry/eth2/lodestar/packages/lodestar-cli/node_modules/yargs/lib/command.js:198:30)

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Screenshots

Desktop (please complete the following information):

OS:  Ubuntu
Version:  20.04
Branch:  master
Commit hash:  d07c3f3

Software versions:
larry@bacon:~$ uname -a
Linux bacon 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
larry@bacon:~$ nvm --version
0.35.3
larry@bacon:~$ node --version
v14.7.0
larry@bacon:~$ npm --version
6.14.7
larry@bacon:~$ yarn --version
1.22.4

This issue is resolved by downgrading Node.js to v12.18.3 and re-compile Lodestar.

@wemeetagain The error comes from @chainsafe/bls-keystore. We should make sure Lodestar is using it's latest version. Also, it would be nice to add a broad NodeJS version matrix in @chainsafe/bls-keystore tests to be sure.

Closing in favor of #1370


grpc: adding limits to outbound buffered data for google-gRPC access logs

Risk Level: Medium (changes by default)
Testing: new unit tests, new guard also tested
Docs Changes: n/a
Release Notes: yes
Optional Runtime guard: envoy.reloadable_features.allow_unbounded_access_logs
[Optional Fixes #Issue]
Fixes #10764

Should be merged up again.  PTAL when you get a chance.


Reference update to clean up the Other page

This is initial draft.
Discussion put it here:
https://github.com/Azure/azure-sdk-for-java/issues/15904

Docs Build status updates of commit 682ed51:
:clock10: Full build: the average full build time is 107 min(s) 28 sec(s), this is based on the last 846 build(s) for this repository.

Docs Build status updates of commit 682ed51:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

preview/docs-ref-autogen/overview/Core.yml
:x:Error

Details

docs-ref-services/core-serializer-json-gson-readme-pre.md
:warning:Warning

Details

preview/docs-ref-autogen/overview/Core.yml

[Error-ApplyTemplatePreprocessorError] Error transforming model "W:\4l0d-o-unknown\raw-\pcocix0c.aei\rawmodel\preview\api\overview\azure\Core.raw.json" generated from "preview/docs-ref-autogen/overview/Core.yml" using "ManagedReference.html.primary.js". Error running Transform function inside template preprocessor: type is undefined

docs-ref-services/core-serializer-json-gson-readme-pre.md

[Warning-DuplicateUids] Uid(azure.java.sdk.landingpage.services.sdk.core.GsonSerializer) has already been defined in docs-ref-services/core-serializer-json-jackson-readme-pre.md.
[Warning-DuplicateUids] Uid(azure.java.sdk.landingpage.services.sdk.core.GsonSerializer) has already been defined in docs-ref-services/core-serializer-json-jackson-readme-pre.md.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit fc56192:
:clock10: Full build: the average full build time is 141 min(s) 56 sec(s), this is based on the last 860 build(s) for this repository.

Docs Build status updates of commit fc56192:
:warning: Validation status: warnings

File
Status
Preview URL
Details

legacy/docs-ref-autogen/overview/EventHubs/Client.yml
:warning:Warning
View (azure-java-legacy)
Details

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

package.json
:white_check_mark:Succeeded

legacy/docs-ref-autogen/overview/EventHubs/Client.yml

[Warning-DuplicateUids] Uid(azure.java.sdk.landingpage.services.eventhub.Client) has already been defined in docs-ref-services/messaging-eventhubs-readme.md.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 48776bc:
:clock10: Pending: waiting for processors (57 builds ahead of you)
:warning: Docs Build is busy, currently there are 57 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 48776bc:
:clock10: Full build: the average full build time is 257 min(s) 30 sec(s), this is based on the last 881 build(s) for this repository.

I don't believe you called the script properly. Your preview is populated with WAY more namespaces than it actually has.  Not only that, it populated in the wrong folder. Did you pull the appropriate commands from the CI job?

Docs Build status updates of commit ee11658:
:clock10: Pending: waiting for processors (48 builds ahead of you)
:warning: Docs Build is busy, currently there are 48 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Put a wrong path parameter for preview. Regenerate again

Docs Build status updates of commit 48776bc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-mapping/reference-latest.yml
:white_check_mark:Succeeded

docs-ref-mapping/reference-preview.yml
:white_check_mark:Succeeded

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

package.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit ee11658:
:clock10: Full build: the average full build time is 261 min(s) 23 sec(s), this is based on the last 887 build(s) for this repository.

Docs Build status updates of commit ee11658:
:clock10: Full build: the average full build time is 261 min(s) 23 sec(s), this is based on the last 887 build(s) for this repository.

Docs Build status updates of commit ee11658:
:clock10: Full build: the average full build time is 261 min(s) 23 sec(s), this is based on the last 887 build(s) for this repository.

Docs Build status updates of commit ee11658:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-mapping/reference-latest.yml
:white_check_mark:Succeeded

docs-ref-mapping/reference-unified.yml
:white_check_mark:Succeeded

package.json
:white_check_mark:Succeeded

preview/docs-ref-mapping/reference-preview.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Your app(s) are vulnerable to Intent Redirection

Hello Google Play Developer,
We reviewed Dr Fitness Plus, with package name com.nikswebnapp.drfitnesspls, and found that your app uses software that contains security vulnerabilities for users. Apps with these vulnerabilities can expose user information or damage a user’s device, and may be considered to be in violation of our Malicious Behavior policy.
Below is the list of issues and the corresponding APK versions that were detected in your recent submission. Please migrate your apps to use the updated software as soon as possible and increment the version number of the upgraded APK.
Fulleter doctor
[√] Flutter (Channel stable, 1.22.4, on Microsoft Windows [Version 10.0.19042.685], locale en-IN)
• Flutter version 1.22.4 at C:\flutter
• Framework revision 1aafb3a8b9 (6 weeks ago), 2020-11-13 09:59:28 -0800
• Engine revision 2c956a31c0
• Dart version 2.10.4
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at F:\sakshi\Sdk
• Platform android-30, build-tools 30.0.3
• ANDROID_HOME = C:\Android\android-sdk
• Java binary at: C:\Program Files\AdoptOpenJDK\jdk8u192-b12\bin\java
• Java version OpenJDK Runtime Environment (AdoptOpenJDK)(build 1.8.0_192-b12)
! Some Android licenses not accepted.  To resolve this, run: flutter doctor --android-licenses
[!] Android Studio (not installed)
• Android Studio not found; download from https://developer.android.com/studio/index.html
(or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).
[!] VS Code (version 1.52.1)
• VS Code at C:\Users\S.N.Chawla\AppData\Local\Programs\Microsoft VS Code
X Flutter extension not installed; install from
https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[√] Connected device (1 available)
• Mi A2 (mobile) • 477b029 • android-arm64 • Android 10 (API 29)
! Doctor found issues in 3 categories.
pubsspec.yaml
version: 1.0.1+2
environment:
sdk: ">=2.7.0 <3.0.0"
dependencies:
flutter:
sdk: flutter
The following adds the Cupertino Icons font to your application.
Use with the CupertinoIcons class for iOS style icons.
cupertino_icons: ^1.0.0
http: ^0.12.2
dio: ^3.0.10
carousel_pro: ^1.0.0
image_ink_well: ^0.1.0
path_provider: ^1.5.1
image_picker: ^0.6.3+1
image_cropper: ^1.3.1
gx_file_picker: ^1.9.0+2
fluttertoast: ^3.1.0
permission_handler: ^5.0.1+1
geolocator: ^5.1.3
location: ^3.0.2
shared_preferences: ^0.5.7+1
youtube_player_flutter: ^7.0.0+7
gallery_view: ^0.0.4
flutter_html: ^1.0.2
introduction_screen: ^1.0.9
#cashfree: ^0.1.1
cashfree_pg: ^0.0.4+9
firebase_core: ^0.5.0
firebase_database: ^4.1.1
cloud_firestore:
firebase_messaging: 7.0.0 #6.0.13
flutter_local_notifications: 1.4.4+4 #1.4.0
#new_version: ^0.0.5
grouped_checkbox: ^1.0.0
url_launcher: ^5.7.2
change_app_package_name: ^0.1.2
file_picker: ^2.0.12

Please give me solutions

Hey @snchawla ,
This issue tracker is used for tracking bugs and feature requests for the flutter framework, engine and the flutter tool.
Please see https://flutter.dev/community for resources and asking queries doubts and assistance on personal code. You may get some help if you post it on StackOverflow and if you need help with your code, please check https://www.reddit.com/r/flutterhelp/.
Thanks

Hi @snchawla
This is not an issue with Flutter, please see https://github.com/flutter/flutter/issues/66901#issuecomment-707006823.
Closing as invalid.


Fanbox: Getting 'compression method is not supported' error for certain zip files

Prerequisites

[Y] Did you read FAQ section in readme.md?
[Y] Did you test with the latest releases or commit ?
[Y] Did you search for existing issues in Issues?

Description
When going over certain zip files in fanbox, getting a 'That compression method is not supported' error for them.
I can only find one example right now though, but I'm not sure if I'm allowed to upload it. It's one of the files in this post: https://dikko.fanbox.cc/posts/4069313
Steps to Reproduce

Do a fanbox download for a post with the offending zip file, in my case I do f2 (by artist) -> and then name, no limit on pages (download everything)
Attempt to download zip file

Expected behavior: Zip file should download properly
Actual behavior: Retry happens 20 times, but all with 'coimpression method is not suppored error', never proceeds to next posts and program is forced exited.
Log file: [Attach the pixivutil.log file in the application folder, recommended to delete the old file, reproduce the issue, and upload the newly generated file here]
pixivutil.log
Versions
20220825
You can get this information from executing PixivUtil2.py --help.
Latest version available in https://github.com/Nandaka/PixivUtil2/releases

try to set verifyImage=False in config.ini. Looks like python library cannot read the zip file format.

try to set verifyImage=False in config.ini. Looks like python library cannot read the zip file format.

Yeah looks like setting that to false worked.

fyi, the latest version will skip the checking automatically if it encounter format  not supported/NotImplementedError even with verifyImage=True

fyi, the latest version will skip the checking automatically if it encounter format not supported/NotImplementedError even with verifyImage=True

Nice, I'll be sure to grab it when I can, thanks for the update!


Cache-Control is not respecting private requests on Android

React Native version:

  React Native Environment Info:
    System:
      OS: Linux 4.4 Ubuntu 18.04.2 LTS (Bionic Beaver)
      CPU: (8) x64 Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz
      Memory: 5.87 GB / 15.90 GB
      Shell: 4.4.19 - /bin/bash
    Binaries:
      Node: 10.15.3 - /usr/bin/node
      Yarn: 1.15.2 - ~/.npm-global/bin/yarn
      npm: 6.9.0 - ~/.npm-global/bin/npm
    npmPackages:
      react: 16.8.6 => 16.8.6
      react-native: https://github.com/expo/react-native/archive/sdk-33.0.0.tar.gz => 0.59.8
    npmGlobalPackages:
      react-native-cli: 2.0.1

Steps To Reproduce
Make a request to any API using the header Cache-Control: 'private'`. (Examples below use Fetch and Axios.)

Describe what you expected to happen:
Proper response in iOS:

FETCH c {
  "map": Object {
    "accept-ranges": "bytes",
    "access-control-allow-origin": "*",
    "allow": "GET,POST,PUT,PATCH,DELETE",
    "cache-control": "private",
    "connection": "keep-alive",
    "content-encoding": "gzip",
    "content-type": "application/json; charset=utf-8",
    "date": "Mon, 17 Jun 2019 07:20:15 GMT",
    "etag": "W/\"2c97-UiFwSZGHPZo8ybrKAarwVn0BPtU\"",
    "server": "Cowboy",
    "strict-transport-security": "max-age=900",
    "transfer-encoding": "Identity",
    "vary": "Accept, Accept-Encoding",
    "via": "1.1 vegur, 1.1 varnish",
    "x-cache": "MISS",
    "x-cache-hits": "0",
    "x-powered-by": "Express",
    "x-served-by": "cache-dfw18621-DFW",
    "x-timer": "S1560756015.121943,VS0,VE52",
  },
}

AXIOS Object {
  "accept-ranges": "bytes",
  "access-control-allow-origin": "*",
  "allow": "GET,POST,PUT,PATCH,DELETE",
  "cache-control": "private",
  "connection": "keep-alive",
  "content-encoding": "gzip",
  "content-type": "application/json; charset=utf-8",
  "date": "Mon, 17 Jun 2019 07:20:15 GMT",
  "etag": "W/\"2c97-UiFwSZGHPZo8ybrKAarwVn0BPtU\"",
  "server": "Cowboy",
  "strict-transport-security": "max-age=900",
  "transfer-encoding": "Identity",
  "vary": "Accept, Accept-Encoding",
  "via": "1.1 vegur, 1.1 varnish",
  "x-cache": "MISS",
  "x-cache-hits": "0",
  "x-powered-by": "Express",
  "x-served-by": "cache-dfw18621-DFW",
  "x-timer": "S1560756015.028437,VS0,VE52",
}

Proper response in Postman:

Incorrect response in Android (notice the different Cache-Control value).

FETCH c {
  "map": Object {
    "accept-ranges": "bytes",
    "access-control-allow-origin": "*",
    "age": "593",
    "allow": "GET,POST,PUT,PATCH,DELETE",
    "cache-control": "public, max-age=0",
    "connection": "keep-alive",
    "content-type": "application/json; charset=utf-8",
    "date": "Mon, 17 Jun 2019 07:20:46 GMT",
    "etag": "W/\"2c97-a+gngb0DFAIxK7psQvBD89inpZM\"",
    "server": "Cowboy",
    "strict-transport-security": "max-age=900",
    "vary": "Accept, Accept-Encoding",
    "via": "1.1 varnish",
    "x-cache": "HIT",
    "x-cache-hits": "1",
    "x-powered-by": "Express",
    "x-served-by": "cache-dfw18634-DFW",
    "x-timer": "S1560756046.196560,VS0,VE0",
  },
}

AXIOS Object {
  "accept-ranges": "bytes",
  "access-control-allow-origin": "*",
  "age": "593",
  "allow": "GET,POST,PUT,PATCH,DELETE",
  "cache-control": "public, max-age=0",
  "connection": "keep-alive",
  "content-type": "application/json; charset=utf-8",
  "date": "Mon, 17 Jun 2019 07:20:46 GMT",
  "etag": "W/\"2c97-a+gngb0DFAIxK7psQvBD89inpZM\"",
  "server": "Cowboy",
  "strict-transport-security": "max-age=900",
  "vary": "Accept, Accept-Encoding",
  "via": "1.1 varnish",
  "x-cache": "HIT",
  "x-cache-hits": "1",
  "x-powered-by": "Express",
  "x-served-by": "cache-dfw18634-DFW",
  "x-timer": "S1560756046.164569,VS0,VE0",
}

Snack, code example, or link to a repository:
// testUrl should be hitting any service with Caching enabled.
// I don't want to publicize my specific API endpoint, but feel
// free to DM me if you need help replicating the issue

// With Fetch
const headers = new Headers()
headers.set('Cache-Control', 'private')

const fr = await fetch(testUrl, {
  method: 'GET',
  headers,
})

console.log('FETCH', fr.headers)

// With Axios
const ar = await axios.get(testUrl, {
  headers: {
    'Cache-Control': 'private',
  },
})

console.log('AXIOS', ar.headers)

This is a updated version of this issue: https://github.com/facebook/react-native/issues/16795
And related to this Expo issue: https://github.com/expo/expo/issues/1639
I'm relying on the Cache-Control header for specific user auth data and requests which should not be cached.

Value private in cache-control header is invalid, please see https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control.


b. music plugin

Just asking about the b. music plugin.

Not sure if those work on anything other than Linux/X11. @sjaehn can you comment?

Yes they are X11 only, yet. One little single file would break the compatibility. It's screen.c which you can find in the src folder of each plugin.
This file contains two simple functions to get the screen size to find an acceptable ui size and is called upon plugin instantiation. Till now, I only implemented an X11 version. I have Windows and Mac on my TODO list. For a wile. But I didn't find time yet. And I'm busy with sth. else at the moment. So, if somebody else wants to take hands on ... :-)
Then at least all plugins without BWidgets::FileChooser (uses POSIX) should work: B.Slizr, B.Choppr, B.Shapr, B.Angr, and B.Schaffl. But no guarantees - as I didn't test it.

doing a round of cleanup, closing and leaving it to others to do the non-linux porting if they so choose.
I am sure they would appreciate contributions too, but I have enough on my plate already so closing as wont-fix.


Made all implicit 'any' types explicit and fixed issue with (ev:null)

Fix for issue https://github.com/IdentityModel/oidc-client-js/issues/112
Also added explicit any type specifications for all places where it was previously implicit so that it is possible to use the definitions file while having the noImplicitAny" option set to true in the tsconfig.json file.

thanks. are you using npm or bower?

I'm using npm myself.

I pushed 1.2.0-beta.3 to npm


SSAPI token refresh failed, request blocked (rate limit?).

Hi,
I have the plugin running and it works perfectly for around 30 minutes, then I am getting this error.
[9/10/2020, 12:04:55 PM] [Home Alarm] SSAPI token refresh failed, request blocked (rate limit?).
Killing the homberidge process and restarting it helps for around 30 minutes.
Thank you for the help.

Hi @TheTherminator . How long have you had the plugin installed? Your description sounds a lot like rate-limiting which is something SS servers seem to do somewhat aggressively. Can you think of any reason why you would be hitting this (the default plugin configuration shouldn't) such as running multiple instances, etc? Does the plugin ever recover if you wait?

Hi Shamoon - wow what a fast reply :)
I have it installed since at least March. I've only one instance running and it never recoveres unless I kill and restart homebridge.
Just looked through my log and found this entry as well ... (sorry total noob here at this end)
[9/10/2020, 11:15:02 AM] [Home Alarm] Error while setting alarm state: RateLimitError: Blocking request: rate limited
at SimpliSafe3.request (/usr/lib/node_modules/homebridge-simplisafe3/simplisafe.js:389:17)
at SimpliSafe3.setAlarmState (/usr/lib/node_modules/homebridge-simplisafe3/simplisafe.js:579:27)
at SS3Alarm.setTargetState (/usr/lib/node_modules/homebridge-simplisafe3/accessories/alarm.js:134:40)
at Characteristic. (/usr/lib/node_modules/homebridge-simplisafe3/accessories/alarm.js:67:109)
at Characteristic.emit (events.js:315:20)
at Characteristic.EventEmitter.emit (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/EventEmitter.ts:42:22)
at Characteristic._this.setValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:652:12)
at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1439:24
at Array.forEach ()
at Bridge.Accessory._this._handleSetCharacteristics (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1281:10)
at HAPServer.emit (events.js:315:20)
at HAPServer.EventEmitter.emit (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/EventEmitter.ts:42:22)
at HAPServer._this._handleCharacteristics (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/HAPServer.ts:812:12)
at IncomingMessage. (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/HAPServer.ts:280:24)
at IncomingMessage.emit (events.js:315:20)
at endReadableNT (_stream_readable.js:1201:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)

Ultimately we cant really prevent this but the plugin should be recovering (it should space-out requests to SS to "wait" until you are unblocked) after rate-limiting on its own. Can you enable the debug option (for both this plugin and Homebridge) and then provide log output for the next couple of hours after you get blocked?

will do and report back - thank you in advance

I just looked at my config to enable debug ... is it maybe because I have the sensorrefresh on 15?
{
"name": "Home Alarm",
"auth": {
"username": "",
"password": ""
},
"cameras": true,
"sensorRefresh": 15,
"persistAccessories": false,
"resetSimpliSafeId": false,
"cameraOptions": {
"enableHwaccelRpi": false
},
"platform": "homebridge-simplisafe3.SimpliSafe 3"
},

Shouldn't be, thats the default and Im assuming you haven't changed it recently. I have mine set to 10 which I tested at first but has been stable for a months. But yea as a fallback you can increase that since its the only thing "pinging" SS on a regular basis but obviously it affects your sensor responsiveness (in HomeKit).

I have debug activated and will chage it to a higher number - I am not really using the sensors in homekit anyway - I have Xiaomi senseors in all rooms ;)

Hi, the other thing which may be causing it is if you’re using the SimpliSafe app on one or more phones connected to the same WiFi network.. if that’s the case, those api calls trigger the rate limit as well.
Is that the case by any chance?

On Sep 10, 2020, at 7:18 PM, TheTherminator<EMAIL_ADDRESS>wrote:

I have debug activated and will chage it to a higher number - I am not really using the sensors in homekit anyway - I have Xiaomi senseors in all rooms ;)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Good morning,
I've left the debug running now for almost 12 hours. Around every 30 minutes I am getting the message below and also sporadically the other one with SSAP token refresh.
We have two phones connected to simplysafe, but hardly ever open the app. Should I uninstall on one phone and test it?
Thank you so so much for your help - you guys are awesome!!!
Error 1 (sporadically)
[9/11/2020, 8:11:38 AM] [Home Alarm] SSAPI token refresh failed, request blocked (rate limit?).
Error 2 (around every 30 minutes)
[9/11/2020, 9:30:00 AM] [Home Alarm] Setting target state to OFF, 3
[9/11/2020, 9:30:00 AM] [Home Alarm] Error while setting alarm state: RateLimitError: Blocking request: rate limited
at SimpliSafe3.request (/usr/lib/node_modules/homebridge-simplisafe3/simplisafe.js:389:17)
at SimpliSafe3.setAlarmState (/usr/lib/node_modules/homebridge-simplisafe3/simplisafe.js:579:27)
at SS3Alarm.setTargetState (/usr/lib/node_modules/homebridge-simplisafe3/accessories/alarm.js:134:40)
at Characteristic. (/usr/lib/node_modules/homebridge-simplisafe3/accessories/alarm.js:67:109)
at Characteristic.emit (events.js:315:20)
at Characteristic.EventEmitter.emit (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/EventEmitter.ts:42:22)
at Characteristic._this.setValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:652:12)
at /usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1439:24
at Array.forEach ()
at Bridge.Accessory._this._handleSetCharacteristics (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Accessory.ts:1281:10)
at HAPServer.emit (events.js:315:20)
at HAPServer.EventEmitter.emit (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/EventEmitter.ts:42:22)
at HAPServer._this._handleCharacteristics (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/HAPServer.ts:812:12)
at IncomingMessage. (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/HAPServer.ts:280:24)
at IncomingMessage.emit (events.js:315:20)
at endReadableNT (_stream_readable.js:1201:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21)

There’s gotta be something else going on, with sensorRefresh at 30 seconds I really don’t think you should be getting rate-limited. Btw, did you enable debug mode (-D) for homebridge too? This will give more detailed logs. And I’m assuming you restarted homebridge after changing settings?
That second error makes sense if you’re already blocked but look at it, it says you’re trying to set the alarm to “OFF”. Why would that be happening every 30 minutes?!? Do you have an automation or something running that’s doing it? That’s pretty suspicious

that was my bad .... i just checked again and it only reports that when I try to disarm over homeapp. I have only two Automations for SimplySafe - disarm in the morning and arm at nights.
here is the startup log:
[9/11/2020, 11:27:44 AM] [Home Alarm] {
staleSettingsTypes: [],
upgradeWhitelisted: false,
model: 'SS001',
uuid: '',
uid: ,
sid: ,
cameraSettings: {
cameraName: 'Living Room',
pictureQuality: '720p',
nightVision: 'auto',
statusLight: 'on',
micSensitivity: 100,
micEnable: true,
speakerVolume: 75,
motionSensitivity: 50,
shutterHome: 'closedAlarmOnly',
shutterAway: 'open',
shutterOff: 'closedAlarmOnly',
wifiSsid: 'GoDawgs',
canStream: false,
canRecord: false,
pirEnable: false,
vaEnable: false,
notificationsEnable: false,
enableDoorbellNotification: true,
doorbellChimeVolume: 'off',
privacyEnable: false,
hdr: false,
vaZoningEnable: false,
vaZoningRows: 6,
vaZoningCols: 6,
vaZoningMask: [
false, false, false, false, false,
false, false, false, false, false,
false, false, false, false, false,
false, false, false, false, false,
false, false, false, false, false,
false, false, false, false, false,
false, false, false, false, false,
false
],
maxDigitalZoom: 10,
supportedResolutions: [ '480p', '720p' ],
admin: {
IRLED: 0,
pirSens: 0,
statusLEDState: 1,
lux: 'lowLux',
motionDetectionEnabled: false,
motionThresholdZero: 0,
motionThresholdOne: 10000,
levelChangeDelayZero: 30,
levelChangeDelayOne: 10,
audioDetectionEnabled: false,
audioChannelNum: 2,
audioSampleRate: 16000,
audioChunkBytes: 2048,
audioSampleFormat: 3,
audioSensitivity: 50,
audioThreshold: 50,
audioDirection: 0,
bitRate: 284,
longPress: 2000,
kframe: 1,
gopLength: 50,
idr: 1,
fps: 20,
firmwareVersion: '<IP_ADDRESS>',
netConfigVersion: '',
camAgentVersion: '',
lastLogin:<PHONE_NUMBER>,
lastLogout:<PHONE_NUMBER>,
pirSampleRateMs: 800,
pirHysteresisHigh: 2,
pirHysteresisLow: 10,
pirFilterCoefficient: 1,
logEnabled: true,
logLevel: 3,
logQDepth: 20,
firmwareGroup: 'public',
irOpenThreshold: 445,
irCloseThreshold: 840,
irOpenDelay: 3,
irCloseDelay: 3,
irThreshold1x: 388,
irThreshold2x: 335,
irThreshold3x: 260,
dbm: 0,
vmUse: 154452,
resSet: 11616,
uptime: 525637.48,
wifiDisconnects: 0,
wifiDriverReloads: 0,
statsPeriod: 3600000,
sarlaccDebugLogTypes: 0,
odProcessingFps: 8,
odObjectMinWidthPercent: 6,
odObjectMinHeightPercent: 24,
odEnableObjectDetection: true,
odClassificationMask: 2,
odClassificationConfidenceThreshold: 0.95,
odEnableOverlay: false,
odAnalyticsLib: 1,
odSensitivity: 85,
odEventObjectMask: 2,
odLuxThreshold: 445,
odLuxHysteresisHigh: 4,
odLuxHysteresisLow: 4,
odLuxSamplingFrequency: 30,
odFGExtractorMode: 2,
odVideoScaleFactor: 1,
odSceneType: 1,
odCameraView: 3,
odCameraFOV: 2,
odBackgroundLearnStationary: true,
odBackgroundLearnStationarySpeed: 15,
odClassifierQualityProfile: 1,
odEnableVideoAnalyticsWhileStreaming: false,
wlanMac: '',
region: 'us-east-1',
enableWifiAnalyticsLib: false,
ivLicense: ''
},
pirLevel: 'medium',
odLevel: 'medium'
},
cameraStatus: {
firmwareVersion: '<IP_ADDRESS>',
netConfigVersion: '',
camAgentVersion: '',
lastLogin:<PHONE_NUMBER>,
lastLogout:<PHONE_NUMBER>,
wlanMac: '',
fwDownloadVersion: '',
fwDownloadPercentage: 0,
recovered: false,
recoveredFromVersion: '',
_id: '',
initErrors: [],
speedTestTokenCreated:<PHONE_NUMBER>
},
__v: 0,
supportedFeatures: {
providers: { webrtc: 'none', recording: 'simplisafe', live: 'simplisafe' },
audioEncodings: [ 'speex' ],
resolutions: [ '480p', '720p' ],
_id: '***',
pir: true,
videoAnalytics: false,
privacyShutter: true,
microphone: true,
fullDuplexAudio: false,
wired: true,
networkSpeedTest: false,
videoEncoding: 'h264'
},
subscription: {
enabled: true,
freeTrialActive: false,
freeTrialUsed: true,
freeTrialEnds: 0,
freeTrialExpires: 0,
planSku: 'SSVM1',
price: 0,
expires:<PHONE_NUMBER>,
storageDays: 30,
trialUsed: true,
trialActive: false,
trialExpires: 0
},
status: 'online'
}

Ok, let’s see what it looks like with the verbose logging enabled. By the way, we should have suggested this earlier, but often turning off homebridge for a few hours seems to allow things to completely reset (on the SS servers)

Oh okay ... i never shut my homebridge down for a coulple of hours, but I can certainly try that.
I disabled the cameras ... still dead after 30 min :(
[9/11/2020, 4:31:54 PM] [Home Alarm] SSAPI token refresh failed, request blocked (rate limit?).
Here the log:
[9/11/2020, 3:22:53 PM] [Home Alarm] Alarm not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] SSAPI socket connected
[9/11/2020, 3:22:53 PM] [Home Alarm] Alarm now listening for real time events.
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Garage Door' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: { autoLock: 0, away: 1, home: 1, awayToOff: 1, homeToOff: 1 },
bootVersion: '1.0.1',
firmwareVersion: '1.1.1',
deviceGroupID: 2,
name: 'Garage Door',
status: {
pinPadState: 0,
lockState: 2,
pinPadOffline: false,
pinPadLowBattery: false,
lockDisabled: false,
lockLowBattery: false,
calibrationErrDelta: 0,
calibrationErrZero: 0,
lockJamState: 0
},
type: 16,
serial: '01014b4f',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Patio Door' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: { autoLock: 0, away: 1, home: 1, awayToOff: 1, homeToOff: 1 },
bootVersion: '1.0.1',
firmwareVersion: '1.1.1',
deviceGroupID: 1,
name: 'Patio Door',
status: {
pinPadState: 0,
lockState: 2,
pinPadOffline: false,
pinPadLowBattery: false,
lockDisabled: false,
lockLowBattery: false,
calibrationErrDelta: 0,
calibrationErrZero: 0,
lockJamState: 0
},
type: 16,
serial: '010149db',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Garage Door' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {},
deviceGroupID: 2,
name: 'Garage Door',
status: {},
type: 253,
serial: '0101aeab',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Patio Door' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {},
deviceGroupID: 1,
name: 'Patio Door',
status: {},
type: 253,
serial: '0101a9d0',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor '' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: { lowPowerMode: false, alarm: 1 },
deviceGroupID: 0,
name: '',
status: {},
type: 1,
serial: '00862980',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor '' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: { disarmEnabled: true, alarm: 1 },
deviceGroupID: 0,
name: '',
status: {},
type: 2,
serial: '005b7241',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Dining Room' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: false,
away2: 0,
away: 1,
home2: 0,
home: 0,
off: 0
},
deviceGroupID: 0,
name: 'Dining Room',
status: {},
type: 4,
serial: '00a1beb1',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Motion Sensor 'Dining Room' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Garage' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Garage',
status: {},
type: 4,
serial: '007d4df1',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Motion Sensor 'Garage' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Living Room' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: false,
away2: 0,
away: 1,
home2: 0,
home: 0,
off: 0
},
deviceGroupID: 0,
name: 'Living Room',
status: {},
type: 4,
serial: '007d4734',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Motion Sensor 'Living Room' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Upstairs 1' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Upstairs 1',
status: {},
type: 4,
serial: '007d552a',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Motion Sensor 'Upstairs 1' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Upstairs 2' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Upstairs 2',
status: {},
type: 4,
serial: '00a80e1f',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Motion Sensor 'Upstairs 2' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Front Door' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Front Door',
status: { triggered: false },
type: 5,
serial: '008e3347',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Entry Sensor 'Front Door' not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Kitchen  1' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Kitchen  1',
status: { triggered: false },
type: 5,
serial: '004ffa77',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Entry Sensor 'Kitchen  1' not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Kitchen 2' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Kitchen 2',
status: { triggered: false },
type: 5,
serial: '005497ca',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Entry Sensor 'Kitchen 2' not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Kitchen 3' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Kitchen 3',
status: { triggered: false },
type: 5,
serial: '005129db',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Entry Sensor 'Kitchen 3' not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Kitchen 4' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Kitchen 4',
status: { triggered: false },
type: 5,
serial: '009046a4',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Entry Sensor 'Kitchen 4' not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Kitchen 5' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Kitchen 5',
status: { triggered: false },
type: 5,
serial: '0051a6e5',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Entry Sensor 'Kitchen 5' not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Living Room 1' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Living Room 1',
status: { triggered: false },
type: 5,
serial: '0051a384',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Entry Sensor 'Living Room 1' not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Living Room 2' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Living Room 2',
status: { triggered: false },
type: 5,
serial: '004ffacc',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Entry Sensor 'Living Room 2' not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Master BR' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Master BR',
status: { triggered: false },
type: 5,
serial: '00900fcc',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Entry Sensor 'Master BR' not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Patio Door' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 1,
name: 'Patio Door',
status: { triggered: false },
type: 5,
serial: '008e32eb',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Entry Sensor 'Patio Door' not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor '3D Printer ' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: {},
deviceGroupID: 0,
name: '3D Printer ',
status: { test: false, tamper: false, malfunction: false, triggered: false },
type: 8,
serial: '00844eb1',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Smoke Detector '3D Printer ' not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Laundry' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: { alarm: 1 },
deviceGroupID: 0,
name: 'Laundry',
status: { triggered: false },
type: 9,
serial: '0098aa63',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Water Sensor 'Laundry' not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered sensor 'Bedroom' from SimpliSafe.
[9/11/2020, 3:22:53 PM] [Home Alarm] {
setting: { alarmVolume: 3, doorChime: 0, exitBeeps: 3, entryBeeps: 3 },
deviceGroupID: 0,
name: 'Bedroom',
status: {},
type: 13,
serial: '0070a08c',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:53 PM] [Config] Homebridge Config UI X v4.27.1 is listening on :: port 8080
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered door lock 'Patio Door' from SimpliSafe
[9/11/2020, 3:22:53 PM] [Home Alarm] {
sid: 2784234,
serial: '010149db',
name: 'Patio Door',
mode: 'sensor',
status: {
lastUpdated: '2020-09-11T15:54:47.147Z',
calibrationErrZero: 0,
calibrationErrDelta: 0,
lockLowBattery: false,
lockDisabled: false,
pinPadLowBattery: false,
pinPadOffline: false,
lockState: 2,
pinPadState: 0,
lockJamState: 0
},
flags: { offline: false, lowBattery: false, swingerShutdown: false },
firmwareVersion: '1.1.1',
bootVersion: '1.0.1',
otaPriority: 'general'
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Lock Patio Door not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Patio Door lock now listening for real time events.
[9/11/2020, 3:22:53 PM] [Home Alarm] Discovered door lock 'Garage Door' from SimpliSafe
[9/11/2020, 3:22:53 PM] [Home Alarm] {
sid: 2784234,
serial: '01014b4f',
name: 'Garage Door',
mode: 'sensor',
status: {
lastUpdated: '2020-09-11T15:54:47.147Z',
calibrationErrZero: 0,
calibrationErrDelta: 0,
lockLowBattery: false,
lockDisabled: false,
pinPadLowBattery: false,
pinPadOffline: false,
lockState: 2,
pinPadState: 0,
lockJamState: 0
},
flags: { offline: false, lowBattery: false, swingerShutdown: false },
firmwareVersion: '1.1.1',
bootVersion: '1.0.1',
otaPriority: 'general'
}
[9/11/2020, 3:22:53 PM] [Home Alarm] Lock Garage Door not found, adding...
[9/11/2020, 3:22:53 PM] [Home Alarm] Garage Door lock now listening for real time events.
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'SimpliSafe 3'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing alarm state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Front Door'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing sensor state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Kitchen  1'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing sensor state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Kitchen 2'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing sensor state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Kitchen 3'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing sensor state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Kitchen 4'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing sensor state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Kitchen 5'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing sensor state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Living Room 1'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing sensor state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Living Room 2'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing sensor state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Master BR'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing sensor state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Patio Door'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing sensor state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device '3D Printer '
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing sensor state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Laundry'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing sensor state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Garage Door'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing door lock state
[9/11/2020, 3:22:53 PM] [Home Alarm] Found device 'Patio Door'
[9/11/2020, 3:22:53 PM] [Home Alarm] Refreshing door lock state
[9/11/2020, 3:22:53 PM] [Home Alarm] Device not found 34c7308d-99b4-43b5-8eef-57777ca22fc7
[9/11/2020, 3:22:53 PM] [Home Alarm] Remove accessory
[9/11/2020, 3:22:54 PM] [Home Alarm] Device not found 611b057e-2f16-4566-8a35-95a4f84d3e7b
[9/11/2020, 3:22:54 PM] [Home Alarm] Remove accessory
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for SimpliSafe 3: OFF
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for Front Door: false, false
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for Kitchen  1: false, false
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for Kitchen 2: false, false
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for Kitchen 3: false, false
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for Kitchen 4: false, false
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for Kitchen 5: false, false
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for Living Room 1: false, false
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for Living Room 2: false, false
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for Master BR: false, false
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for Patio Door: false, false
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for 3D Printer : false, false, false, false
[9/11/2020, 3:22:54 PM] [Home Alarm] Updated current state for Laundry: false, false
[9/11/2020, 3:22:54 PM] [Home Alarm] Refreshing accessories (add and remove: true)
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Garage Door' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: { autoLock: 0, away: 1, home: 1, awayToOff: 1, homeToOff: 1 },
bootVersion: '1.0.1',
firmwareVersion: '1.1.1',
deviceGroupID: 2,
name: 'Garage Door',
status: {
pinPadState: 0,
lockState: 2,
pinPadOffline: false,
pinPadLowBattery: false,
lockDisabled: false,
lockLowBattery: false,
calibrationErrDelta: 0,
calibrationErrZero: 0,
lockJamState: 0
},
type: 16,
serial: '01014b4f',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Patio Door' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: { autoLock: 0, away: 1, home: 1, awayToOff: 1, homeToOff: 1 },
bootVersion: '1.0.1',
firmwareVersion: '1.1.1',
deviceGroupID: 1,
name: 'Patio Door',
status: {
pinPadState: 0,
lockState: 2,
pinPadOffline: false,
pinPadLowBattery: false,
lockDisabled: false,
lockLowBattery: false,
calibrationErrDelta: 0,
calibrationErrZero: 0,
lockJamState: 0
},
type: 16,
serial: '010149db',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Garage Door' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {},
deviceGroupID: 2,
name: 'Garage Door',
status: {},
type: 253,
serial: '0101aeab',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Patio Door' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {},
deviceGroupID: 1,
name: 'Patio Door',
status: {},
type: 253,
serial: '0101a9d0',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor '' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: { lowPowerMode: false, alarm: 1 },
deviceGroupID: 0,
name: '',
status: {},
type: 1,
serial: '00862980',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor '' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: { disarmEnabled: true, alarm: 1 },
deviceGroupID: 0,
name: '',
status: {},
type: 2,
serial: '005b7241',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Dining Room' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: false,
away2: 0,
away: 1,
home2: 0,
home: 0,
off: 0
},
deviceGroupID: 0,
name: 'Dining Room',
status: {},
type: 4,
serial: '00a1beb1',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Motion Sensor 'Dining Room' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Garage' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Garage',
status: {},
type: 4,
serial: '007d4df1',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Motion Sensor 'Garage' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Living Room' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: false,
away2: 0,
away: 1,
home2: 0,
home: 0,
off: 0
},
deviceGroupID: 0,
name: 'Living Room',
status: {},
type: 4,
serial: '007d4734',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Motion Sensor 'Living Room' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Upstairs 1' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Upstairs 1',
status: {},
type: 4,
serial: '007d552a',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Motion Sensor 'Upstairs 1' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Upstairs 2' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Upstairs 2',
status: {},
type: 4,
serial: '00a80e1f',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Motion Sensor 'Upstairs 2' requires secret alerts to be enabled in SimpliSafe before you can add it to Homebridge.
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Front Door' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Front Door',
status: { triggered: false },
type: 5,
serial: '008e3347',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Kitchen  1' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Kitchen  1',
status: { triggered: false },
type: 5,
serial: '004ffa77',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Kitchen 2' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Kitchen 2',
status: { triggered: false },
type: 5,
serial: '005497ca',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Kitchen 3' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Kitchen 3',
status: { triggered: false },
type: 5,
serial: '005129db',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Kitchen 4' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Kitchen 4',
status: { triggered: false },
type: 5,
serial: '009046a4',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Kitchen 5' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Kitchen 5',
status: { triggered: false },
type: 5,
serial: '0051a6e5',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Living Room 1' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Living Room 1',
status: { triggered: false },
type: 5,
serial: '0051a384',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Living Room 2' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Living Room 2',
status: { triggered: false },
type: 5,
serial: '004ffacc',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Master BR' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 0,
name: 'Master BR',
status: { triggered: false },
type: 5,
serial: '00900fcc',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Patio Door' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {
instantTrigger: true,
away2: 0,
away: 1,
home2: 0,
home: 1,
off: 0
},
deviceGroupID: 1,
name: 'Patio Door',
status: { triggered: false },
type: 5,
serial: '008e32eb',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor '3D Printer ' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: {},
deviceGroupID: 0,
name: '3D Printer ',
status: { test: false, tamper: false, malfunction: false, triggered: false },
type: 8,
serial: '00844eb1',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Laundry' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: { alarm: 1 },
deviceGroupID: 0,
name: 'Laundry',
status: { triggered: false },
type: 9,
serial: '0098aa63',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered sensor 'Bedroom' from SimpliSafe.
[9/11/2020, 3:22:54 PM] [Home Alarm] {
setting: { alarmVolume: 3, doorChime: 0, exitBeeps: 3, entryBeeps: 3 },
deviceGroupID: 0,
name: 'Bedroom',
status: {},
type: 13,
serial: '0070a08c',
flags: { swingerShutdown: false, lowBattery: false, offline: false }
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered door lock 'Patio Door' from SimpliSafe
[9/11/2020, 3:22:54 PM] [Home Alarm] {
sid: 2784234,
serial: '010149db',
name: 'Patio Door',
mode: 'sensor',
status: {
lastUpdated: '2020-09-11T15:54:47.147Z',
calibrationErrZero: 0,
calibrationErrDelta: 0,
lockLowBattery: false,
lockDisabled: false,
pinPadLowBattery: false,
pinPadOffline: false,
lockState: 2,
pinPadState: 0,
lockJamState: 0
},
flags: { offline: false, lowBattery: false, swingerShutdown: false },
firmwareVersion: '1.1.1',
bootVersion: '1.0.1',
otaPriority: 'general'
}
[9/11/2020, 3:22:54 PM] [Home Alarm] Discovered door lock 'Garage Door' from SimpliSafe
[9/11/2020, 3:22:54 PM] [Home Alarm] {
sid: 2784234,
serial: '01014b4f',
name: 'Garage Door',
mode: 'sensor',
status: {
lastUpdated: '2020-09-11T15:54:47.147Z',
calibrationErrZero: 0,
calibrationErrDelta: 0,
lockLowBattery: false,
lockDisabled: false,
pinPadLowBattery: false,
pinPadOffline: false,
lockState: 2,
pinPadState: 0,
lockJamState: 0
},
flags: { offline: false, lowBattery: false, swingerShutdown: false },
firmwareVersion: '1.1.1',
bootVersion: '1.0.1',

I disabled the cameras ... still dead after 30 min :(

Did you mean you shutdown homebridge, not sure what you mean "disabled the cameras", that shouldn't matter. From your last logs it looks like you started up the plugin at 3:22 and then got the error at ~4:30, but Id be looking for the logs around the 4:30 mark, when the lockout first started happening again.

Ive set the camarea options to false - see below.
nothing really happened around 4:30 ... I've disabled all automations that could talk to simplysafe ... I am trying it again now - shutting down homebridge for a couple of hours and will report back.
{
"name": "Home Alarm",
"auth": {
"username": "#####",
"password": "#####"
},
"cameras": false, (I CHANGED THIS TO FALSE)
"debug": true,
"sensorRefresh": 90,
"persistAccessories": false,
"resetSimpliSafeId": false,
"cameraOptions": {
"enableHwaccelRpi": false
},
"platform": "homebridge-simplisafe3.SimpliSafe 3"
},

Yea that’s why I asked, cameras shouldn’t have any effect, they won’t increase the number of times your system is pinging SS etc. Especially  since it seems they use different servers for their api and media.
Anyway, up to you. Yea give it a long while turned off and let’s see.

I left my homebridge disabled for 4 hours yesterday. After restart - again 30 Min and then the same error. I am trying something esle now: I had an additional Xiaomi Gateway in my home which identified also as Home Alarm. I deleted that device to see if that cahnges anything.

Nope - same ...this time even after 5 minutes of running
###@###:~$ homebridge -I -D
[9/15/2020, 2:52:40 PM] Loaded config.json with 5 accessories and 6 platforms.
[9/15/2020, 2:57:14 PM] [Home Alarm] SSAPI token refresh failed, request blocked (rate limit?).

Something doesn’t add up. Never seen anyone else having this issue so much. Can you upload the entire log from when you restarted after the 4h off through when it gets blocked?

Add me to the list, was using an old simplisafe plugin on ym server, thats been shut down and moved to my main system instead (since its on backup power etc) and I cant get mine to run either.  I keep getting the same errors.
[9/18/2020, 12:06:05 PM] [Home Alarm] Log in failed due to rate limiting or connectivity, trying again later
[9/18/2020, 12:06:05 PM] [Home Alarm] Accessory refresh failed due to rate limiting or connectivity
[9/18/2020, 12:07:05 PM] [Home Alarm] Log in attempt failed, still rate limited
Ill report back if anything changes but yeah cant even get it to start up.

Hi @shamoon I just set this up for the first time today and am having the same issue. I've not yet got it working due to the rate limit. It seems like SimpliSafe is blocking all requests? I do have the app on my phone on the same wifi from when I set it up, but I killed it and still no change.
[10/7/2020, 11:29:40 PM] [Home Alarm3] Logged in!
[10/7/2020, 11:29:40 PM] [Home Alarm3] Refreshing accessories (add and remove: false)
[10/7/2020, 11:29:42 PM] [Home Alarm3] Alarm not found, adding...
[10/7/2020, 11:29:42 PM] [Home Alarm3] SSAPI request failed, request blocked (rate limit?).
[10/7/2020, 11:29:42 PM] [Home Alarm3] Accessory refresh failed due to rate limiting or connectivity
[10/7/2020, 11:29:42 PM] [Home Alarm3] Refreshing accessories (add and remove: true)
[10/7/2020, 11:29:42 PM] [Home Alarm3] Alarm not found, adding...
[10/7/2020, 11:29:42 PM] [Home Alarm3] Refreshing alarm state
[10/7/2020, 11:29:42 PM] [Home Alarm3] Add accessory
[10/7/2020, 11:29:42 PM] [Home Alarm3] SimpliSafe 3 alarm caught RateLimitError, waiting 1s to retry...
[10/7/2020, 11:29:42 PM] [Home Alarm3] Accessory refresh failed due to rate limiting or connectivity
[10/7/2020, 11:29:42 PM] [Home Alarm3] Updated current state for SimpliSafe 3: HOME
[10/7/2020, 11:29:42 PM] [Home Alarm3] SSAPI socket connected
[10/7/2020, 11:29:42 PM] [Home Alarm3] Alarm now listening for real time events.
[10/7/2020, 11:29:43 PM] [Home Alarm3] Alarm now listening for real time events.
[10/7/2020, 11:29:43 PM] [Home Alarm3] SimpliSafe 3 alarm caught RateLimitError, waiting 2s to retry...
[10/7/2020, 11:29:45 PM] [Home Alarm3] Alarm now listening for real time events.
[10/7/2020, 11:29:45 PM] [Home Alarm3] SimpliSafe 3 alarm caught RateLimitError, waiting 4s to retry...
[10/7/2020, 11:29:49 PM] [Home Alarm3] Alarm now listening for real time events.
[10/7/2020, 11:29:49 PM] [Home Alarm3] SimpliSafe 3 alarm caught RateLimitError, waiting 8s to retry...
[10/7/2020, 11:29:57 PM] [Home Alarm3] Alarm now listening for real time events.
[10/7/2020, 11:29:57 PM] [Home Alarm3] SimpliSafe 3 alarm caught RateLimitError, waiting 16s to retry...
[10/7/2020, 11:30:13 PM] [Home Alarm3] Alarm now listening for real time events.
[10/7/2020, 11:30:13 PM] [Home Alarm3] SimpliSafe 3 alarm caught RateLimitError, waiting 32s to retry...
[10/7/2020, 11:30:45 PM] [Home Alarm3] Alarm now listening for real time events.
[10/7/2020, 11:31:01 PM] [Home Alarm3] Setting target state to OFF, 3
[10/7/2020, 11:31:02 PM] [Home Alarm3] SSAPI request failed, request blocked (rate limit?).
[10/7/2020, 11:31:02 PM] [Home Alarm3] Error while setting alarm state: RateLimitError: [object Object]
at SimpliSafe3.request (/usr/local/lib/node_modules/homebridge-simplisafe3/simplisafe.js:447:15)
at processTicksAndRejections (internal/process/task_queues.js:97:5)

Hi @zooplibob Sometimes people hit the SS servers a lot when trying to get the plugin setup. From you logs it looks like it did recover and successfully connect a couple times. Did you try leaving the plugin off for a few hours (a day even) and trying again? And when you are getting blocked, check if you can login to the website. We dont have much control over getting blocked except to lower the sensorRefresh time but the default 15 seconds is usually enough to prevent this.

Hi Shamoon, yes I can still log into the website when its giving errors. I left it off all day and tried again, and same thing. Heres the log from the start:
[10/8/2020, 10:21:24 PM] Homebridge is running on port 51718.
[10/8/2020, 10:21:24 PM] [Home Alarm3] Logged in!
[10/8/2020, 10:21:24 PM] [Home Alarm3] Refreshing accessories (add and remove: false)
[10/8/2020, 10:21:26 PM] [Home Alarm3] Alarm not found, adding...
[10/8/2020, 10:21:27 PM] [Home Alarm3] SSAPI request failed, request blocked (rate limit?).
[10/8/2020, 10:21:27 PM] [Home Alarm3] Accessory refresh failed due to rate limiting or connectivity
[10/8/2020, 10:21:27 PM] [Home Alarm3] Refreshing accessories (add and remove: true)
[10/8/2020, 10:21:27 PM] [Home Alarm3] Alarm not found, adding...
[10/8/2020, 10:21:27 PM] [Home Alarm3] Refreshing alarm state
[10/8/2020, 10:21:27 PM] [Home Alarm3] Add accessory
[10/8/2020, 10:21:27 PM] [Home Alarm3] SimpliSafe 3 alarm caught RateLimitError, waiting 1s to retry...
[10/8/2020, 10:21:27 PM] [Home Alarm3] Accessory refresh failed due to rate limiting or connectivity
[10/8/2020, 10:21:27 PM] [Home Alarm3] Updated current state for SimpliSafe 3: OFF
[10/8/2020, 10:21:27 PM] [Home Alarm3] SSAPI socket connected
[10/8/2020, 10:21:27 PM] [Home Alarm3] Alarm now listening for real time events.
[10/8/2020, 10:21:28 PM] [Home Alarm3] Alarm now listening for real time events.
[10/8/2020, 10:21:28 PM] [Home Alarm3] SimpliSafe 3 alarm caught RateLimitError, waiting 2s to retry...
[10/8/2020, 10:21:30 PM] [Home Alarm3] Alarm now listening for real time events.
[10/8/2020, 10:21:30 PM] [Home Alarm3] SimpliSafe 3 alarm caught RateLimitError, waiting 4s to retry...
[10/8/2020, 10:21:34 PM] [Home Alarm3] Alarm now listening for real time events.
[10/8/2020, 10:21:34 PM] [Home Alarm3] SimpliSafe 3 alarm caught RateLimitError, waiting 8s to retry...
Does this mean it connected and then immediately hit some limit? I have my refresh set to 150. Do you think Simplisafe has learned how to detect Homebridge connections and block them?

@zooplibob It's odd, your logs show you are logging but then cant refresh. I just released a new version of the plugin that primarily is designed to give even more log output to see if there's an issue to track down here. When you do see the new version please update and post your logs here. Thanks!

Hi Shamoon, it turns out I didn't sign up for the monitoring subscription, just the basic one which doesnt have app integration. Now its working and I do not get RateLimitErrors!
Maybe if theres a way for the debug messages to remind users they need that subscription level when getting requests blocked would help others! Thank you for your support!

That is in the readme but perhaps would be useful to remind people again...


[Win] VM can not start after cloning and Installation stuck on "Cloning VM" stage.

Need to manage situation - at least inform user
2016-12-05_Subutai_install_log.txt
VM cannot start due to network settings
After that:
Uploading 2016-12-05_Subutai_install_log (1).txt…
Installation failed because of snappy was not removed properly, need to delete snappy files

Every stage with VM start need to be checked.


Swipe right gesture opens 4 drawers in mobile device

Expected Behavior
When I swipe to the right on this page: https://lusaxweb.github.io/vuesax/components/sideBar.html I expect to only open the global drawer instead of any other drawer.
Current Behavior
Four drawers are open when you swipe to the right in the page mentioned above. They open like a stack.
Steps to reproduce

In a mobile device, go to the following website: https://lusaxweb.github.io/vuesax/components/sideBar.html

Do a right swipe and notice all the drawers open.

Environment
Mobile Device:  Samsung Galaxy S9+
OS: Android 8.0.0
Browser: Samsung Internet <IP_ADDRESS>

Well that is something expected because each drawer has that clear functionality is that in an application are not going to put as many as one maximum and will come out only but that happens only for documents thanks for the contribution


Bootstrapping after git clone?

Hi, I'm trying to run bundle install on my local clone of https://github.com/mbj/unparser, a project that uses devtools. I'm running into the problem that this fetches current devtools master and then bombs out because unparser depends on older versions of rake, etc. than devtools. From devtools' README, I gather that the update process involves bundle exec devtools sync. However, since bundle install won't run, I'm left hand-modifying Gemfile.devtools.
Is there a better way, and if so, what is it?

We totally changed installation, do not need the Gemfile.devtools anymore etc. Also devtools now has a gem release. Closing this issue.


Sequencer genesis update

Changes:

Update prefunded accounts balances to 100 ETH

The genesis file has been updated in a different PR, closing as this is no longer relevant


Reaction Schema

Reaction (SCHEMA ONLY)
reactionId
Use Mongoose's ObjectId data type
Default value is set to a new ObjectId
reactionBody
String
Required
280 character maximum
username
String
Required
createdAt
Date
Set default value to the current timestamp
Use a getter method to format the timestamp on query
Schema Settings
not a model. used as the reaction field's subdocument schema in the Thought model.

DONE!


fix: phased training fixes

set the defaults in pydantic for effective batch size set the click flag range for save samples to be > -1 rather than > 1

Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the
conventional commits.
[ ] Changelog updated with breaking and/or notable changes for the next minor release.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.
[ ] Integration tests have been added, if necessary.

if samples_per_save: -> if samples_per_save is not None: in _run_training_phase @cdoern

The commit message is vague on the reasoning for these changes. I assume some other team members may have more details to justify it, but these should be shared in the commit message and/or in an issue that is linked to the patch. Without it, it's impossible to assess if these changes are the right thing to do.
The commit message is probably incorrect when it says that "set the click flag range for save samples to be > 0 rather than > 1" (because the ">=" operator should be used I think.)


querySelector fails on class selector

How to reproduce:

Create jsdom:

global.document = jsdom.jsdom(`<!doctype html>
<html style="margin-top:10px;">
  <head>
    <meta charset="utf-8">
  </head>
  <body style="margin-top:20px;" class="ui-page">
  </body>
</html>`);

Retrieve .ui-page:

let page = document.querySelector('.ui-page');

What happens:
page is null.
What should happen:
page should equal
let page = document.querySelector('body');

which is not null.
Version: 9.2.1.

I can't reproduce on jsdom 9.3.0.
const jsdom = require('jsdom');

global.document = jsdom.jsdom(`<!doctype html>
<html style="margin-top:10px;">
  <head>
    <meta charset="utf-8">
  </head>
  <body style="margin-top:20px;" class="ui-page">
  </body>
</html>`);

console.log(document.querySelector('.ui-page'));

HTMLBodyElement {}

Cannot reproduce here either. Going to close, but happy to reopen if we got something wrong. Thanks for the nice issue template with very small repro case!

No luck here. Tested both 9.3.0 and 9.4.0.
Class-based query on any other element than body succeeds, but not the body.

Maybe the class has been removed by the time you try to retrieve the element? Try logging jsdom.serializeDocument(document) and see if it still contains the class.

Yup, had the same idea, must be implementation error, otherwise wouldn't make sense.

Confirmed, implementation error. document.write had killed the classes on body element.
Sorry for the noise, hopefully it'll prove useful for someone having an hiccup on the same topic.


Upgraded openjdk version to fix broken builds

Should contain this fix https://bugs.openjdk.java.net/browse/JDK-8213202

@birdayz was faster than me


chore(main): release 1.4.5

:robot: I have created a release beep boop
1.4.5 (2024-03-26)
Bug Fixes

main: Added link to readthedocs (dee37d9)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/CoreySpohn/lod_unit/releases/tag/v1.4.5 :sunflower:


Fix readme

Current coverage is 98.97% (diff: 100%)

Merging #9 into master will not change coverage

@@             master         #9   diff @@
==========================================
  Files            25         25
  Lines           195        195
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            193        193
  Misses            2          2
  Partials          0          0

Powered by Codecov. Last update 19a8243...a1b8fcc

thanks for that


Upload FAB Missing Padding in Nearby

Summary:
Upload FAB Button is Missing Padding in Nearby
Screenshot

Would you like to work on the issue?
Yes

This UI change is necessary, thanks for pointing it out @madhurgupta10 .


Allow non-numeric data in Table panel

Please help me how to display data in table_pannel (http://docs.grafana.org/reference/table_panel/) correctly
In Grafana:
query:

result:

In Create:

We need to implement table mode for queries, otherwise grafana considers that data is time series and has numeric values.

@buom closed by your PR.


Totem of Undying animation

First of all, massive props. I did not know anyone had continued EF. That is one of my favorite mods.
Second of all: I'm impressed you got the totem to function.
Someone tells me that your totem lacks its characteristic animation.
If it helps, I backported the Guardian in my own mod, and I suspect the elder curse animation functions very similarly. Maybe you can glean some clues from there:
https://gitgud.io/AstroTibs/VillageNames/tree/1.7.10/src/main/java/astrotibs/villagenames/prismarine/guardian/particle

Supporting this.
Would be nice to have the animation :)


Dilato: Core: Windows Only: After upgrade the build to the latest 1.12 build from the defective 1.12 build, the default language is English and two brackets icon in uninstall program panel

Steps

Install 1.12 build (containing the OS language bug). Launch Brackets, app language is English.
Install latest 1.12 build (containing the fix).

Result:

Launching Brackets still launches it in English.
There are two brackets icon on uninstall program panel

Expected:
1.) Launch in Local language
2.) Only one brackets icon on uninstall program panel

why not just uninstall the buggy version and install fixed version?

This is fixed now!


Build Presto server RPM in an OS-agnostic way

Use redlinerpm-maven-plugin --
https://github.com/spaulg/redlinerpm-maven-plugin/ -- to build the
Presto server RPM, so that it can be built by both Linux and OSX with
no additional libraries. This plugin uses the redline library
(https://github.com/craigwblake/redline), a pure Java RPM building
library.
Change the Maven profile so that the RPM builds every time.
Test Plan: mvn clean install, on both Linux and Mac OSX

Merged, thanks!

Thanks!  Could you all add the RPM to the artifacts put up on Maven?

They should be included automatically in the next release


Initialize DAO (community pool) with tokens on genesis

Fixes #372
Overview
Created a new module that takes in params for how to initialize the DAO. On init genesis, it populates the community pool with the defaults. This requires creating a genesis account with enough funds to cover funding the DAO, which is created in the Makefile init target. Since it's a module account, it doesn't need a private key and is owned by the chain. The key only has to be created with pubkey starspub1addwnpepqfqzrt4mzg8e6w0ltk557ysys3dl6vf40lfkqrlpmz0m83xs5fgjy42tt8y.
NOTE: Used the new Tendermint Starport scaffolding tool which adds a bunch of comments everywhere. Keeping them in for now so the module can be extended in the future.
I know creating a whole module for funding the DAO seems excessive, but the goal is to wrap the Cosmos distribution and gov modules to provide Stargaze-specific functionality in the future.
Before chain starts
When make init (or make reset) is run, this genesis account for funding the DAO is created:
        {
          "@type": "/cosmos.auth.v1beta1.BaseAccount",
          "address": "stars1czlu4tvr3dg3ksuf8zak87eafztr2u004zyh5a",
          "pub_key": null,
          "account_number": "0",
          "sequence": "0"
        }

A balance is added to the bank module:
        {
          "address": "stars1czlu4tvr3dg3ksuf8zak87eafztr2u004zyh5a",
          "coins": [
            {
              "denom": "ustarx",
              "amount": "300000000000000"
            }
          ]
        }

The dao module is generated with these defaults:
    "dao": {
      "params": {
        "genesis_allocation": {
          "denom": "ustarx",
          "amount": "300000000000000"
        },
        "genesis_sender": "stars1czlu4tvr3dg3ksuf8zak87eafztr2u004zyh5a"
      }
    },

After chain starts
After the chain starts, the funding account is drained:
        {
          "address": "stars1czlu4tvr3dg3ksuf8zak87eafztr2u004zyh5a",
          "coins": []
        },

The supply is updated:
      "supply": [
        { "amount": "10000000000000", "denom": "uatom" },
        { "amount": "10010000000000000", "denom": "ucredits" },
        { "amount": "10331000851161412", "denom": "ustarx" }
      ]

The community pool is updated with funds in the distribution module:
      "fee_pool": {
        "community_pool": [
          { "amount": "300000007447662.640000000000000000", "denom": "ustarx" }
        ]
      },

Not really sure if the account is necessary? can we just directly use the minter and transfer  ?
I agree that a entire module for this might seem too much for now but I can see in the future other functionality being added not really sure how tho since the community pool is already handled by governance and might overlap in functionality.

@jhernandezb Should be able to create a module account and mint to it, eliminating the need to create an account. But the advantage of using an external account is that it gets drained so there's no chance minting accidentally happens twice. Is it possible for InitGenesis to run again after an upgrade for example?

thats a good point, I think it might if we just export/import, but the export can always  dump initial_allocation=0 or remove it after an upgrade.


RecursionError on OpenAi python client inside a docker container

Hello,
My code worked well on native configuration, but I got these traceback in a docker container :
2023-12-13 17:25:46 Traceback (most recent call last):
2023-12-13 17:25:46   File "main.py", line 59, in <module>
2023-12-13 17:25:46     openai_client = OpenAI(api_key="<myAPIkey>" ,base_url="http://<openchat_server_url>/v1")
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/site-packages/openai/_client.py", line 106, in __init__
2023-12-13 17:25:46     super().__init__(
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/site-packages/openai/_base_client.py", line 758, in __init__
2023-12-13 17:25:46     self._client = http_client or SyncHttpxClientWrapper(
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/site-packages/httpx/_client.py", line 672, in __init__
2023-12-13 17:25:46     self._transport = self._init_transport(
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/site-packages/httpx/_client.py", line 720, in _init_transport
2023-12-13 17:25:46     return HTTPTransport(
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/site-packages/httpx/_transports/default.py", line 133, in __init__
2023-12-13 17:25:46     ssl_context = create_ssl_context(verify=verify, cert=cert, trust_env=trust_env)
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/site-packages/httpx/_config.py", line 51, in create_ssl_context
2023-12-13 17:25:46     return SSLConfig(
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/site-packages/httpx/_config.py", line 75, in __init__
2023-12-13 17:25:46     self.ssl_context = self.load_ssl_context()
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/site-packages/httpx/_config.py", line 87, in load_ssl_context
2023-12-13 17:25:46     return self.load_ssl_context_verify()
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/site-packages/httpx/_config.py", line 124, in load_ssl_context_verify
2023-12-13 17:25:46     context = self._create_default_ssl_context()
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/site-packages/httpx/_config.py", line 161, in _create_default_ssl_context
2023-12-13 17:25:46     set_minimum_tls_version_1_2(context)
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/site-packages/httpx/_compat.py", line 28, in set_minimum_tls_version_1_2
2023-12-13 17:25:46     context.minimum_version = ssl.TLSVersion.TLSv1_2
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/site-packages/eventlet/green/ssl.py", line 476, in minimum_version
2023-12-13 17:25:46     super(_original_sslcontext, _original_sslcontext).minimum_version.__set__(self, value)
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/ssl.py", line 586, in minimum_version
2023-12-13 17:25:46     super(SSLContext, SSLContext).minimum_version.__set__(self, value)
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/ssl.py", line 586, in minimum_version
2023-12-13 17:25:46     super(SSLContext, SSLContext).minimum_version.__set__(self, value)
2023-12-13 17:25:46   File "/usr/local/lib/python3.8/ssl.py", line 586, in minimum_version
2023-12-13 17:25:46     super(SSLContext, SSLContext).minimum_version.__set__(self, value)
2023-12-13 17:25:46   [Previous line repeated 488 more times]
2023-12-13 17:25:46 RecursionError: maximum recursion depth exceeded

I'm not sure if it is an OpenAI or openchat related issue, but maybe SSL verification can cause some troubles ? I tried to use openai.verify_ssl_certs=False but it didn't change anything...

I found what was wrong : it seems eventlet was installed on the docker and not on native configuration. Removing it from the docker requirements solved the problem.


[RN-306]: allow delete keys without backup

going to hold on this Id like to add some extra messaging - ill post it here


Live-update narrow filters on stream renames.

Let's say Denmark is stream id 42, and you're narrowed to stream Denmark, and then somebody renames the stream to Denmark2.  The app will update stream names in some places in the UI, but it doesn't actually update your narrow parameters, and this leads to ugly things like the following:

you'll be told you're unsubscribed from Denmark (when in reality you're still subscribed to stream 42)
when you reply to a message, you'll be told that you sent a message outside the narrow (which is sort of correct, but also confusing)

There are two approaches we can take here:

hacky: On live updates, patch up the narrow by finding all stream operators of "Denmark" and renaming them to "Denmark2", and possibly do things like update the internal filter function
deep fix: Make narrow operators be id-aware.

The "deep fix" is preferable here, and it's pretty advanced, so only folks who have experience with our narrowing code should grab this.

#4713 is essentially a superset of this bug, so I'm closing this for now.
It turns out that making the stream filters be stream-id-aware is fairly straightforward, and I have a PR coming to fix that.  There are still thorny issues in terms of the URLs (aka hashes) still having stream names.


Update minification support

There are three issues about minification:

Add minifiers for more formats
Add options to disable/enable minifiers
Document minification

With minify included it would also be easy to add minification for other formats. It also comes with support for CSS, HTML, JS, JSON, SVG and XML.
Personally I think it's currently a little bit tricky to find out about minification though.
It is definitely reasonable that files in static remain unchanged. Still, this would be the first place for be to put assets like CSS files.
If you want your styles minified you need to put them in the contents folder, which - as far as I could figure out - is not documented anywhere. The docs don't mention minification in an way.
Also, it would probably be good if users can disable/enable minifcation for the different file types.
What are your thoughts about adding further minifiers? And, is there existing documentation I didn't find?
These issues might also affect https://github.com/gohugoio/hugo/issues/621.

Minification out-of-the box is super useful in my opinion. Overall whitespace is wasting bandwidth and minified websites potentially load faster, especially if pages get "big". After all the "raw" HTML need to be transferred to the client so the smaller it can be the better.
I'd gladly welcome this feature and help test / document it if needed.

I'm currently working on "page bundles", which involves "redoing" the handler implementations; the current CSS minification I think was put in there kind of as a proof of concept, and I think I'm going to remove it in its current form. It will need some rethinking in a bigger picture.

@bep sorry, didn't see the work on page bundles. Feel free to close this issue if all above points are have been already covered before.

@jorinvo it is in my repo, so I would be surprised if you saw it.

Hi!  Now that Page Bundles have been implemented, I was wondering if there is interest in implementing minification support again?
I was reminded of this when I noticed that a new upstream version of golang-github-tdewolff-minify became available[1], and then I wondered why I packaged it in the first place[2].

https://qa.debian.org/developer.php?login=foka%40debian.org&comaint=yes
https://bugs.debian.org/870594

and I was led back here.  :-)

See also #4446

Hugo 0.43 added minification. I think this issue can be closed.

thanks for the hard work on this :)


Event interface

This PR changes the base event abstract class (EgoEvent) to an interface (IEgoEvent).
Doing so allows custom event types to inherit from other classes such as Unity3D's ScriptableObject, allowing them to be created and used efficiently in the editor.
This PR also allows, at a small performance cost, to call EgoEvents.AddEvent(IEgoEvent e) and still have the event dispatched to the proper queue.
Example use case:
// ScriptableEgoEvent.cs

public class ScriptableEgoEvent : UnityEngine.ScriptableObject, IEgoEvent {}

// CustomEvent1.cs

using UnityEngine;

[CreateAssetMenu( fileName = "CustomEvent1", menuName = "EgoEvents/CustomEvent1" )]
public class CustomEven1t : ScriptableEgoEvent
{
    public string param;
}

// CustomEvent2.cs

using UnityEngine;

[CreateAssetMenu( fileName = "CustomEvent2", menuName = "EgoEvents/CustomEvent2" )]
public class CustomEven1t : ScriptableEgoEvent
{
    public int param;
}

// SomeComponent.cs

using UnityEngine;

[DisallowMultipleComponent]
public class SomeComponent: MonoBehaviour
{
    public ScriptableEgoEvent egoEvent;
}

// SomeSystem.cs
    ...
    public override void Start()
    {
        EgoEvents<CustomEvent2>.AddHandler( Handle );
    }
    ...

Events created using those menus can be dragged and dropped to components' public fields of type ScriptableEgoEvent and dispatched later on using EgoEvents.AddEvent( component.egoEvent ) to the proper queues.

Congrats! You've submitted the first pull request for EgoCS! However, I do not think I will accept it:
EgoEvents are essentially bundles of runtime-only data and references: These objects collided, this player won and was going this fast, etc. They don't own anything themselves and is why I recommend using a suitable OO-style constructor when creating them. Following this, I don't see how an EgoEvent could or even should be setup in the editor / inspector.
You could use data in whatever ScriptableObjects to determine what gets passed into an EgoEvent's constructor, or pass in the entire ScriptableObject instance, but these should solely be done at runtime.
EgoEvents definitely should never be members of another class, especially a member of a Component or MonoBehaviour. Systems construct EgoEvents exactly when and where they happen, with whatever data they require.

Thank you for your feedback.
It seems that the example use case I've provided has masked the real content of the PR:

use an interface instead of abstract base class for EgoEvent
allow dispatching of events without specifying the type of the event in the call (EgoEvents.AddEvent(IEgoEvent e) vs EgoEvents<MyEvent>.AddEvent(MyEvent e))

Nothing more than that... and I could/should have split the 2 features into 2 separate PRs as they are orthogonal.
The example I've provided is based on a problem I encountered in a toy project I'm using to evaluate EgoCS but remains only one example of what these changes allow. Here is a small summary of what I was trying to achieve.
I have implemented a waypoint system (using DOTween internally) based on a waypoint follower component. This component holds a list of waypoints (transform + extra parameters for timing, ease function, ...). I want a designer (not a coder) to be able to optionally attach events to each waypoint to be emitted whenever it is reached by the entity (e.g. emit sound event, shoot bullet event, ...). I could of course go with a factory to create those events from user parameters but using a scriptable object asset (or instantiating a copy) seemed to make sense to me and avoids having to write specific editor code to adapt the GUI depending on the chosen event type.
Nevertheless, what is more important to me is that I would like to be able to dispatch the created event easily, using a base class/interface reference (EgoEvents.AddEvent(IEgoEvent e) vs EgoEvents<MyEvent>.AddEvent(MyEvent e)).
What would be the recommended way of handling this in EgoCS?

EgoEvents should not be used to pass arbitrary messages between systems?

They pass messages and data, but not "arbitrary" or "generic" data. An EgoEvent should be very specific and EgoEvent types should be discrete and explicit.

If so, I guess another way of handling my problem could then be based on enabling components dynamically when waypoints are reached...

Yes, that's what I was going to suggest. Upon reaching the waypoint, you could destroy the
"Waypoint follower" Component, and attach different Component(s) (that correspond to appropriate Systems) to get the new behaviour you want.
I do agree that EgoEvents<MyEvent>.AddEvent(new MyEvent())) has some redundant type info. I'll look into it this weekend.