text:
devtoys: Add version 2.0.5.0

What type of Apps related PR is this? (check all applicable)

[x] ✨ Add Manifest
[ ] ♻ Refactor
[ ] 🐛 Bug Fix
[ ] 👷 Optimization
[ ] 🚩 Other

Description
DevToys App : A Swiss Army knife for developers.
Related Tickets & Documents
None
[optional] What gif/emoji best describes this PR or how it makes you feel?
:sparkles: :package: :beers: :technologist:
Did you verify the followings
Add/Modify a description in the manifest?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Check URLs?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Update to the latest version?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Update Hashes?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Format the json manifest?

[x] 👍 yes
[ ] 🙋 yes, but I need help
[ ] 🙅 no, because they aren't needed

Did you identify extra steps
Notes in the manifest?

[ ] 👍 yes
[ ] 🙋 yes, but I need help
[x] 🙅 no, because they aren't needed

Application Dependencies?

[ ] 👍 yes
[ ] 🙋 yes, but I need help
[x] 🙅 no, because they aren't needed

Application Suggestions?

[ ] 👍 yes
[ ] 🙋 yes, but I need help
[x] 🙅 no, because they aren't needed

Pre-installation steps to perform?

[ ] 👍 yes
[ ] 🙋 yes, but I need help
[x] 🙅 no, because they aren't needed

Post-installation steps to perform?

[ ] 👍 yes
[ ] 🙋 yes, but I need help
[x] 🙅 no, because they aren't needed

File persistence to perform?

[ ] 👍 yes
[ ] 🙋 yes, but I need help
[x] 🙅 no, because they aren't needed

All changes look good.
Wait for review from human collaborators.
devtoys

[x] Description
[x] License
[x] Hashes
[x] Checkver
[x] Autoupdate

authors: BotServiceAutomation alexchapar

repo: brave-simpletons/scoop-the-business

license: Unlicense


text:
Test typescript type definitions.

Adds a typescript file that uses the type definitions, and adds the typescript compiler to the npm test command.

To address the concerns about testing in #8

Thanks!
It surprised me that you were compiling the src/index.d.ts explicitly. As this file is referenced inside the package.json, this didn't seem necessary. I changed test-typings.ts so that it requires the package root. Typescript correctly finds the type definition file by itself. I know because test-typings.ts fails to compile when I change the type to string.

Oh cool, I didn't know that would work. I guess it sees the package.json? That makes sense. Much nicer!

source: gharchive/pull-request

license: mit

license_type: permissive

license_source: bigquery


text:
2 step compilation

What is the purpose of transpling Typescript to ES6 via tsc, and then ES6 to ES5 via Babel? Why you can't use only tsc targeting ES5?

It's a personal choice I guess. I like it when my IDE compiles to es6 because it's more readable.
But I understand what you mean.

Thanks for explaining. At first I thought there are some hidden pitfals of direct compilation, that you have encountered.

source: gharchive/issue

authors: brechtbilliet nikolaymatrosov

license: MIT

license_source: github-api


text:
Type definitions for Typescript

Thank you for this plugin.
What problem are you trying to solve?
Using plugin without require.
...
Describe the feature
Can you, please, add type definitions so we can use it easier in typescript?
...

Checklist

[x] I have read the documentation and made sure this feature doesn't already exist.

closed by v1.0.1

repo: breejs/ts-worker


text:
HA w/DSM7 400: Bad Request

The problem
Getting a 400: Bad Request after setting up the add-on w/ configuration.yaml.
My HA is installed in DSM 7 via docker and the domain name is from Cloudflare.
So beside the
http:   use_x_forwarded_for: true   trusted_proxies:     - 172.30.33.0/24
I also added a list of Cloudflare IP range ( https://www.cloudflare.com/en-gb/ips/)
and my docker IP

following this guide (https://community.home-assistant.io/t/home-assistant-400-bad-request-docker-proxy-solution/322163/21?page=2)
What version of Cloudflared has the issue?
4.2.11
What was the last working version of Cloudflared?
No response
What type of installation are you running?
Home Assistant OS
Add-on YAML Configuration
http:
  use_x_forwarded_for: true
  trusted_proxies:
    - 172.30.33.0/24
    - 103.21.244.0/22
    - 103.22.200.0/22
    - 103.31.4.0/22
    - 104.16.0.0/13
    - 104.24.0.0/14
    - 108.162.192.0/18
    - 131.0.72.0/22
    - 141.101.64.0/18
    - 162.158.0.0/15
    - 172.64.0.0/13
    - 173.245.48.0/20
    - 188.114.96.0/20
    - 190.93.240.0/20
    - 197.234.240.0/22
    - 198.41.128.0/17
    - 170.30.32.2
    - 172.30.33.1
    - 172.17.0.0/16
    - 172.30.32.0/23
    - 172.30.32.1
    - 172.18.0.0/16
    - 172.18.0.1
    - 172.18.0.2/16
    - 172.30.32.0/23
    - 127.0.0.1
    - 10.0.0.2

# Loads default set of integrations. Do not remove.
default_config:

Anything in the logs that might be useful for us?
-----------------------------------------------------------
 Add-on: Cloudflared
 Use a Cloudflare Tunnel to remotely connect to Home Assistant without opening any ports
-----------------------------------------------------------
 Add-on version: 4.2.11
 You are running the latest version of this add-on.
 System: null  (amd64 / qemux86-64)
 Home Assistant Core: 2023.11.3
 Home Assistant Supervisor: 2023.11.6
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[02:28:38] INFO: Checking add-on config...
[02:28:38] INFO: Checking for existing certificate...
[02:28:38] INFO: Existing certificate found
[02:28:38] INFO: Checking for existing tunnel...
[02:28:38] INFO: Existing tunnel with ID ********-*****-********-*****-****** found
[02:28:38] INFO: Checking if existing tunnel matches name given in config
[02:28:39] INFO: Existing Cloudflare Tunnel name matches config, proceeding with existing tunnel file
[02:28:39] INFO: Creating config file...
[02:28:41] INFO: Validating config file...
Validating rules from /tmp/config.json
OK
[02:28:41] INFO: Creating DNS entry watchfuljiu.win...
2023-12-03T18:28:42Z INF mydomain.com is already configured to route to your tunnel tunnelID=*********-*****-********-*****-******
[02:28:42] INFO: Finished setting up the Cloudflare Tunnel
[02:28:42] INFO: Connecting Cloudflare Tunnel...
2023-12-03T18:28:42Z INF Starting tunnel tunnelID=********-*****-********-*****-******
2023-12-03T18:28:42Z INF Version 2023.10.0
2023-12-03T18:28:42Z INF GOOS: linux, GOVersion: go1.20.6, GoArch: amd64
2023-12-03T18:28:42Z INF Settings: map[config:/tmp/config.json cred-file:/data/tunnel.json credentials-file:/data/tunnel.json loglevel:info metrics:0.0.0.0:36500 no-autoupdate:true origincert:/data/cert.pem]
2023-12-03T18:28:42Z INF Generated Connector ID: ********-*****-********-*****-******
2023-12-03T18:28:42Z INF Initial protocol quic
2023-12-03T18:28:42Z INF ICMP proxy will use 172.30.33.1 as source for IPv4
2023-12-03T18:28:42Z INF ICMP proxy will use :: as source for IPv6
2023-12-03T18:28:42Z WRN The user running cloudflared process has a GID (group ID) that is not within ping_group_range. You might need to add that user to a group within that range, or instead update the range to encompass a group the user is already in by modifying /proc/sys/net/ipv4/ping_group_range. Otherwise cloudflared will not be able to ping this network error="Group ID 0 is not between ping group 1 to 0"
2023-12-03T18:28:42Z WRN ICMP proxy feature is disabled error="cannot create ICMPv4 proxy: Group ID 0 is not between ping group 1 to 0 nor ICMPv6 proxy: socket: permission denied"
2023-12-03T18:28:42Z INF Starting metrics server on [::]:36500/metrics
2023/12/04 02:28:42 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Receive-Buffer-Size for details.
2023-12-03T18:28:43Z INF Registered tunnel connection connIndex=0 connection=eca7da34-3364-4cab-9840-9a8d6cd55911 event=0 ip=198.41.200.73 location=sjc08 protocol=quic
2023-12-03T18:28:43Z INF Registered tunnel connection connIndex=1 connection=895b134f-72b1-4390-be21-5ed7a8be308f event=0 ip=198.41.192.167 location=hkg01 protocol=quic
2023-12-03T18:28:44Z INF Registered tunnel connection connIndex=2 connection=b0f7d714-f263-491e-865e-84b5a1e0efba event=0 ip=198.41.200.113 location=sjc05 protocol=quic
2023-12-03T18:28:45Z INF Registered tunnel connection connIndex=3 connection=368d8836-b40e-4451-9c19-91c814c9cf98 event=0 ip=198.41.192.227 location=hkg08 protocol=quic

Steps to reproduce the issue
Not sure is it related to installing HA using DSM7
Additional information
No response

This is definitely an issue with how you are running HA and the containers in the first place and nothing, that we can support here.
Nevertheless, I suggest you do the following:

Clean up your trusted_proxies list. You do not have to enter any IPs from Cloudflare. I suggest you enter the following:

172.30.33.0/24
172.17.0.0/16
172.30.32.0/23
172.18.0.0/16

Change the log level to "debug"
Start everything and check the logs of the add-on after requesting the hostname

Ok I figured it out. I forgot restart my HA after re-adding the proxy line described in the end of this doc
https://github.com/brenner-tobias/addon-cloudflared/blob/main/cloudflared/DOCS.md#configurationyaml

I am going to try the remote method now, and see if the problem still exist

authors: brenner-tobias derage hohaha045

repo: brenner-tobias/addon-cloudflared


text:
AttributeError for download_urls

> caniusepython3 -r requirements.txt
No handlers could be found for logger "ciu"
Finding and checking dependencies ...
[WARNING] Stale overrides: set([u'xlwt', u'jmespath'])
Traceback (most recent call last):
  File "$HOME/.local/bin/caniusepython3", line 11, in <module>
    sys.exit(main())
  File "$HOME/.local/venvs/caniusepython3/lib/python2.7/site-packages/caniusepython3/__main__.py", line 179, in main
    check(projects_from_cli(args))
  File "$HOME/.local/venvs/caniusepython3/lib/python2.7/site-packages/caniusepython3/__main__.py", line 167, in check
    blockers = dependencies.blocking_dependencies(projects, pypi.all_py3_projects())
  File "$HOME/.local/venvs/caniusepython3/lib/python2.7/site-packages/caniusepython3/dependencies.py", line 81, in blocking_dependencies
    dist = distlib.locators.locate(project)
  File "$HOME/.local/venvs/caniusepython3/lib/python2.7/site-packages/distlib/locators.py", line 361, in locate
    result.download_urls = versions.get('urls', {}).get(version, set())
AttributeError: 'dict' object has no attribute 'download_urls'

Are you using the latest release of distlib? And can you provide your requirements.txt file or figure out which project is triggering the error if you are not running the latest release of distlib?

Afraid I can't share the requirements.txt.  I'll see if I can isolate the problem line.
Here's my venv:
> pip freeze
argparse==1.3.0
caniusepython3==3.1.0
distlib==0.2.0
futures==3.0.2
wsgiref==0.1.2

I actually just remembered this was fixed as part of #87 , so it will get resolved in the next release of caniusepython3 (hopefully Friday).

authors: brettcannon kevinastone


text:
maxLifetime = 0 and idleTimeout = 0

Running performance tests on a postgres instance, we (me and my team) noticed a spike in response time during the very first requests, after the boot of the app.
The resulting plot was something like this (this is just meant to give you an idea, don't take it too seriously :)):

It shows the response time of our app under a load of 5/6 requests per second.
Setting both maxLifeTime and idleTimeout to zero, we were able to get rid of the initial spike.
Our take on that, is that creating all the connections together when the application starts up (we are using minConnection == maxConnection == 25) causes the spike.
My questions are:

Is it reasonable that creating 25 connections cause such a problem (first requests really took about 2 seconds to get back to us)? I would expect the creation of few connections to take a few milliseconds.
Is it bad to have connections open forever? (consider that my application is the only process using that database)

Exploring the history of the source code of hikari, I found this condition (that is not there anymore):
if (maxLifetime == 0 && idleTimeout == 0) {
  logger.warn("setting idleTimeout to {}ms.", IDLE_TIMEOUT);
  idleTimeout = IDLE_TIMEOUT;
}

I guess you went through this very problem :), and you decided that you didn't really like maxLifetime == 0 && idleTimeout == 0.

@calippo First question is, what version of HikariCP?
It is strange that either maxLifeTime or idleTimeout would eliminate the spike.  Neither should come into play during the first few minutes of startup.
idleTimeout is actually ignored when minimumIdle == maxConnections.
maxLifeTime similarly should not come into play until 30 minutes after startup.
ThreadLocalRandom can block the acquisition thread if enough entroy is not available.  On Linux this can be mitigated with -Djava.security.egd=file:/dev/./urandom" (yes, the /./ is necessary).
Connection creation speed varies quite a lot by database.  MySQL can typically setup a new connection in single-digit milliseconds.  Oracle over SSL can sometimes take 20-30 seconds per-connection.
I am curious why and if the spike is truly mitigated by either of the two variables you mentioned.  Certainly, setting a low minimumIdle would increase startup time -- but not if load immediately ramps up.
What does the database CPU and disk I/O look like during the spike?

Q1: First question is, what version of HikariCP?

A1: We are using slick 3.1.1, that uses hikari 2.3.7

Q2: It is strange that either maxLifeTime or idleTimeout would eliminate the spike. Neither should come into play during the first few minutes of startup.

A2: The reason why they came into play (in our opinion) is because we didn't shutdown the test setup between consecutive tests. With maxLifeTime == 0 && idleTimeout == 0, we only had the spike in the first test run 'since the connection was already opened' (at least this was our guess). The JVM was appropriately warmed up by the testing framework.

idleTimeout is actually ignored when minimumIdle == maxConnections.

:+1: I read about it but didn't manage to find it in the actual code

Connection creation speed varies quite a lot by database. MySQL can typically setup a new connection in single-digit milliseconds. Oracle over SSL can sometimes take 20-30 seconds per-connection.

Woah, didn't know about this. You have a similar estimate for postgres?

Lastly, it's not great to have connections "open forever" because something usually kills them eventually -- often databases have a maxLifeTime of their own. Better for the pool to retire and replace them in an orderly fashion rather than discovering a dead connection at the time that the application needs one.

Ok, I see your point is: "it's better to control connections rather then being controlled by connections" :)
Recap:

idleTimeout is completely ignored in our configuration. What we're doing is completely configured by maxLifeTime = 0
maxLifeTime = 0 is not a great configuration
beware connections create can take seconds
a possible solution for the problem would be -Djava.security.egd=file:/dev/./urandom"

Fortunately it looks that the performances of our app are good enough for our use case. I'm not sure we're going to test performances again (I'm likely going to set maxLifeTime to a reasonable amount of time).
The configuration consequences are now clear to me, I think you can close this issue. In case we go back testing the connection pool I'll update this with details (i.e. disk I/O CPU etc).

@brettwooldridge
hi, brettwooldridge.
I have a question about maxLifeTime and connection eviction.
My production database has 60s of wait_timeout.
HikariCP recommands maxLifeTime = wait_timeout - 30s.
so, I set up maxLifeTime 30s.
Every 30 seconds, i can get logs 'connection was evicted'.
2018-04-25 17:16:27.529 DEBUG 5501 --- [onnection adder] com.zaxxer.hikari.pool.HikariPool        : hikariPool - Added connection org.mariadb.jdbc.MariaDbConnection@4c17abf9
2018-04-25 17:16:27.938 DEBUG 5501 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase          : hikariPool - Closing connection org.mariadb.jdbc.MariaDbConnection@316bf091: (connection was evicted)
2018-04-25 17:16:27.968 DEBUG 5501 --- [onnection adder] com.zaxxer.hikari.pool.HikariPool        : hikariPool - Added connection org.mariadb.jdbc.MariaDbConnection@517ba0b8
2018-04-25 17:16:27.970 DEBUG 5501 --- [onnection adder] com.zaxxer.hikari.pool.HikariPool        : hikariPool - After adding stats (total=10, active=10, idle=0, waiting=0)
2018-04-25 17:16:28.646 DEBUG 5501 --- [nnection closer] com.zaxxer.hikari.pool.PoolBase          : hikariPool - Closing connection org.mariadb.jdbc.MariaDbConnection@4a4f19a0: (connection was evicted)
2018-04-25 17:16:28.656 DEBUG 5501 --- [onnection adder] com.zaxxer.hikari.pool.HikariPool        : hikariPool - Added connection org.mariadb.jdbc.MariaDbConnection@3db7055e
2018-04-25 17:16:29.258 DEBUG 5501 --- [ool housekeeper] com.zaxxer.hikari.pool.HikariPool        : hikariPool - Pool stats (total=30, active=15, idle=15, waiting=0)
Every 30 seconds!
Would not the load on the database?

@brettwooldridge
Thank you for your reply.!!
How much more efficient is it to create connections than the test-while-idle method?
Is there anything I can refer to?
if constantly making new connections is not expensive, there seems to be no reason to use DBCP...
Does HikariCP use a special way to create a connection?
😃

authors: brettwooldridge calippo pkgonan

repo: brettwooldridge/HikariCP


text:
when i using customImageComponent(FastImage) just show border 'red'

My ScreenShoot

My Code
<View style={{flex: 1, flexGrow: 10, marginTop: 4}}>      <Masonry        sorted        bricks={this.state.originImg}        columns={this.state.columns}        customImageComponent={FastImage}        customImageProps={FastImage} />      </View>

Did you install FastImage and run $npm link react-native-fast-image? Afterwards, you need to restart the bundler

already using react-native link
my package.json
"react": "16.0.0-alpha.12",
"react-native": "0.45.1",
"react-native-fast-image": "^1.0.0",
"react-native-masonry": "^0.4.0",
"react-native-svg": "5.2.0"

my code
export default class SVG extends Component { render() {
    return (
      <View style={styles.container}>
        <Masonry
          sorted
          column={2}
          bricks={[
            { uri: 'https://i.pinimg.com/736x/a4/b2/98/a4b298e715660b8e5b9402d21276fb88--shoes-platform-sneakers-suede-puma-shoes.jpg' },
            { uri: 'https://i.pinimg.com/736x/63/bf/51/63bf51af7b5e322329af89d795962fe0--nike-knit-shoes-tennis-shoes-womens-nike-running.jpg' },
            { uri: 'http://4.bp.blogspot.com/-wMj-artgutU/VjFZE_fuo-I/AAAAAAAAcdU/W0pluz-4Yn0/s1600/2015%2B1028%2BNike%2BFree%2B5.0%2BTR%2BFit%2B5%2BMetallic%2BBlack%253ABlue%2BLagoon%253AGlacier%2BBlue%253AMetallic%2BSilver%2B%2B.png' },
            { uri: 'https://s.aolcdn.com/hss/storage/midas/1c38860b2eafca9d23de549e74b15286/204650181/nikehyperadaptlede.jpg'},
            { uri: 'https://i.pinimg.com/736x/cf/cc/bb/cfccbbe0784bdd37084aa6ee709c31b4--mens-sneakers-fashion-sneakers-mens.jpg'}
          ]}
          customImageComponent={FastImage}
        />
      </View>
    );
  }}

@zanisis I would recommend recompiling the project, since FastImage is a native-dep module. $ react-native run-ios

i try running on ios maybe on android not supported but on ios is still same only show border red not showing image

Please run without customImageComponent and tell me if it renders properly

Closing issue, hopefully it should be working now 👯♂


text:
Add configuration for multiple pooler services and integration with nspooler

Here I've modified vmfloaty to add the following:

configuration of multiple pooler services
an API client for @McdonaldSeanp's nonstandard pooler service

I wanted to make this an unobtrusive addition, but the scale of the changes ended up being much larger than I'd hoped; If you'd rather I keep this as a fork instead of merging it into vmfloaty, that is completely okay with me!
Here's a longer description of what I've done:
Multiple service configuration
This keeps the old config file format intact for existing users, but adds another key, services, which can be filled out with a map of different pooler service url/user/token combinations.
Example:
user: 'casey.williams'
url: 'http://vmpooler.default.mycompany.net'
token: 'nzed8n6v00fc7pnsqquoapeigmt5qlcs'
services:
  alternate:
    url: 'http://vmpooler.alternate.mycompany.net'
    token: 'g32fi2mc5a3x8mxy3l48fu9vel6az7cu'

With this configuration:

floaty list would still list only the OSes on the default vmpooler instance.
floaty list --service alternate, would list only the OSes on the alternate instance. Note that the alternate instance here also has no configured username - if this is the case and the user doesn't specify a username at the command line, the default username will be used instead.

I did not include a way to interact with multiple services at once (for example, to get a list of OSes available from all services at once or show VMs running on all services at once), although that would be easy to add.
Nonstandard Pooler API
The nonstandard pooler's API is very similar to that of vmpooler, but not quite the same. I added a Service entity which gathers the right url, token, and/or username from the CLI options and the config file, then calls api methods on either the existing Pooler class or a new NonstandardPooler class. My goal with this approach was to minimize the scale of the changes I was making to Pooler, but I did end up having to change it.
To use a nonstandard pooler service, the config file above can be adjusted like this:
user: 'casey.williams'
url: 'http://vmpooler.default.mycompany.net'
token: 'nzed8n6v00fc7pnsqquoapeigmt5qlcs'
services:
  alternate:
    url: 'http://vmpooler.alternate.mycompany.net'
    token: 'g32fi2mc5a3x8mxy3l48fu9vel6az7cu'
  nonstandard:
    url: 'http://nspooler.mycompany.net'
    token: '847a4699ce6ea41206c5b220'
    type: 'nonstandard'

Including type: nonstandard in the nonstandard pooler service config tells it to use the NonstandardPooler instead of Pooler (which is the default).

Used this a bit today, seems to work for me.

Woo @caseywilliams ! This pull request looks awesome...lots of refactoring that I had been meaning to do a long time ago! Thanks for that :) Gimmie a bit to digest all the changes and provide any feedback (if needed at all) and I'll be happy to merge and cut a new release. Also thanks @MikaelSmith for testing. If there's anything that doesn't work with the nspooler just let me know since I can't test that at the moment. :)

@briancain I think I've finally got this updated now - Thank you so much for your review!

@caseywilliams yay! thanks again. I should have some time this weekend to do another once over on the changes to make sure it's all good (just some simple smoke tests to make sure nothing is broken) but I'm hoping to get this merged and released by next week! :)

Ok @caseywilliams - this should now be released in version 0.8.0!

Woohoo! Thanks so much @briancain! 😄  🙌

authors: MikaelSmith briancain caseywilliams

repo: briancain/vmfloaty


text:
[core] Add the TimeSeriesWorkload class, a new type of workload that …

…uses
the existing YCSB API to generate time series data (numeric values associated
with timestamps).
See the TimeSeriesWorkload.java class Javadocs for details on how to use it
with a client and workloads/tsworkload_template for parameters.
Also add the BasicTSDB instance for printing/debugging the workloads.

Hi folks!
This is a new type of workload for testing time series databases. We've seen a ton of work around time series lately with IoT, monitoring, etc and it would be nice to get a common framework for benching.
Please take a look and let me know what you think of this framework. Particularly:

Help suggest standard workloads similar to the K/V A through F configs. Right now I just a tiny tsworkloada.
Try implementing some clients and see if parsing is acceptable.
Let me know if any of the TODOs or other features are really needed to adequately bench our DBs.

Thanks!

@jasontedor If you still have cycles, I know Elastic is working hard on time series data. Would you mind taking a look at this and give me your feedback? Thanks!

repo: brianfrankcooper/YCSB


text:
Update the user dashboard to support content management

As described in #70 the community page functionality is moving more towards discovery / collaborations.  Since every user is now a content creator the dashboard should be main place to manage that.
So should the content creator dashboard be the user dashboard?
This ticket follows the development of the new user dashboard to support resources and goal / topic creation. (and tags / discussions?)

Decision: The actual user "dashboard" the page loaded when you click on the user icon if you are the user should stay the same with the goal of managing the users profile and preferences
This page should be a "Dashboard" along the top menu in addition to About and Community that is the new version of the CC creator panel.
Next step is to design out the "Dashboard" page.  Since all users are creators it should not need to be different based on role just show the best options to the user given the context.

Early render to work off.  Left column are filters for the middle (and the right as that will suggest based off the filters as well).
User can select multiple filters, so if they select a goal and then a tag the tag will filter within the goal.  "x"'s besides the filters will allow them to be removed. Same for text search will filter with other filters, an "x" next to the search term can remove it.

Mostly complete but out of date. New design will be implemented, closing.

repo: briangormanly/agora


text:
Where is the Result Prikey

When i ran the command in my Laptop...
clBitCrack.exe --keyspace 80000000:ffffffff 1FshYsUh3mqgsG29XpZ23eLjWV8Ur3VwH
It is finished .... Last 2 lines are .....
[Info] Done
[Info] Reached end of keyspace

So where is the Result ??? I am struggling to find.

OK. Corrected after compiling the code by fixing opencl bug.
Thanks


text:
Material type/definition is not defined in the system for Genbrug

Describe the issue
This error originated from a custom integration.
Logger: pyaffalddk.api
Source: custom_components/affalddk/init.py:123
integration: Affaldshåndtering DK (documentation, issues)
First occurred: April 28, 2024 at 16:55:21 (138 occurrences)
Last logged: 08:55:26
Material type [Papir, 660 liter (3 stk.)] is not defined in the system for Genbrug. Please notify the developer. Municipality: Lyngby-taarbæk, Address ID: 55180
Material type [Plast, 660 liter (2 stk.)] is not defined in the system for Genbrug. Please notify the developer. Municipality: Lyngby-taarbæk, Address ID: 55180
Material type [Metal, 660 liter (1 stk.)] is not defined in the system for Genbrug. Please notify the developer. Municipality: Lyngby-taarbæk, Address ID: 55180
Material type [Glas, 660 liter (2 stk.)] is not defined in the system for Genbrug. Please notify the developer. Municipality: Lyngby-taarbæk, Address ID: 55180
Material type [Pap, 660 liter (3 stk.)] is not defined in the system for Genbrug. Please notify the developer. Municipality: Lyngby-taarbæk, Address ID: 55180
What version of Home Assistant Core has the issue?
core-2024.4.4
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
What version of the integration are you using?
v2.1.6
Diagnostics information
See "Describe the issue" field
Anything in the logs that might be useful for us?
No response
Additional information
No response

Jeg fixer det i weekenden

authors: PTRSC briis

repo: briis/affalddk


text:
Suggestion: using EvaluationDose

Hi,
very nice and good to understand script.
I was wondering why you use DICOM for the conversion. If you use:
ExternalPlanSetup plan = course.AddExternalPlanSetup(ss);
EvaluationDose eDose = plan.CreateEvaluationDose();
You can modify the DoseVoxels with ESAPIs SetVoxel(slice, doseplane [,]) function
Hopefully this is helpful.

@Kiragroh Wow, for some reason github didn't tell me about this comment.
Anyway, thanks for the comment! I was sure you can't do that, but it looks like i was wrong. I will fix this, most definitely!
Thanks!

@Kiragroh it worked! Thank you very much for the suggestion.

I Know.^^ I implemented it the day after my suggestion. Very nice. Two other suggestions:

in your code all DVH for all selected structures will be calculated again when a new structure is selected. This makes the program very slow after selecting one big structure. I changed some things in the RemoveDVH class and now it is fine
I programmed to autoselect the structures with alphaBeta value in the preview window.

authors: Kiragroh brjdenis


text:
ReturnButton type not showing up in iOS for keyboardType telephone

ReturnButton type not showing up in iOS for keyboardType telephone. Android does display the returnType button.

Same issue is occurring here.
I am implementing EntryCustomReturnPlugin through the Effect method in XAML file.

@nielscup Can you elaborate more about the feature you're seeking?
The default iOS Numeric Keyboard doesn't have a return button.

@nielscup Can you elaborate further about the feature you're looking for?
The default UIKeyboardType.phonePad doesn't include a return button.

Closing pending follow up information

authors: brminnick nielscup zwilkin

repo: brminnick/EntryCustomReturnPlugin


text:
Include variants with AC=0 (no variant called but covered in coverage table) in Joint Metrics

Message from Patricia Sullivan, a colleague and analyst and regular gnomAD user:
"[Daniel my good friend at the Broad Institute, I hope you've been well]. I know you're not in charge of this, but you work with the team ;)
[Curious question for you and your team - why] does a variant's allele frequency not get updated in the total if it is present only in exomes/genomes yet is covered by the other? Surely that's an oversight since it adds more 'control' variants to the allele number."

thanks for opening this ticket! migrating to production repo


text:
mapWithIndex, filterWithIndex

On Iterators and Views at least.

Not needed.

repo: broadinstitute/hail


text:
Log messages to a custom location

Maybe load a config file that tells the application what path to write its logs to.

@dtolnay do you consider this issue closed or did you need me to do anything more with it?

Thanks, you completed this one. Next time if you put "fixes #97" in the comment when you open the PR, it will auto-close the issue when the PR is merged.

repo: brson/rust-cookbook


text:
rsp-4: Added README and LICENSE

Changelog

adds README.md
adds MIT LICENSE
adds all-contributors integration

https://github.com/all-contributors please add @e3stpavel for code,doc,bug,design

repo: bruxemburg/reshop


text:
building debian dockerfile has problems

Hello,
The key has expired in this line:
RUN apt-key adv --keyserver keys.gnupg.net --recv-keys 9E3E53F19C7DE460

https://github.com/aptly-dev/aptly/issues/717 has the new key:
RUN apt-key adv --keyserver keys.gnupg.net --recv-keys ED75B5A4483DA07C

Also the Aptly Bash completions fails.  I didn't bother debugging and just commented it out to continue.
converted 'https://github.com/smira/aptly/raw/master/bash_completion.d/aptly' (ANSI_X3.4-1968) -> 'https://github.com/smira/aptly/raw/master/bash_completion.d/aptly' (UTF-8)
--2020-07-18 02:52:16--  https://github.com/smira/aptly/raw/master/bash_completion.d/aptly
Resolving github.com (github.com)... 140.82.113.3
Connecting to github.com (github.com)|140.82.113.3|:443... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://github.com/smira/aptly-fork/raw/master/bash_completion.d/aptly [following]
converted 'https://github.com/smira/aptly-fork/raw/master/bash_completion.d/aptly' (ANSI_X3.4-1968) -> 'https://github.com/smira/aptly-fork/raw/master/bash_completion.d/aptly' (UTF-8)
--2020-07-18 02:52:16--  https://github.com/smira/aptly-fork/raw/master/bash_completion.d/aptly
Reusing existing connection to github.com:443.
HTTP request sent, awaiting response... 404 Not Found
2020-07-18 02:52:16 ERROR 404: Not Found.

FYI, apparently a lot of the forked repos already have been fixing this and other issues.

Hi @m-fonseca, thanks for pointing out these issues. I just merged some changes to address these issues and hopefully this repo is still useful to those who find it: https://github.com/bryanhong/docker-aptly/pull/6

authors: bryanhong m-fonseca

repo: bryanhong/docker-aptly


text:
Idea: Highest/Lowest temperature of today

Idea: To implement in the maintile of the temperature sensor the highest and lowest temperature of the current day?

Right 24 hours is impossible as once maxtemp is 24 hours old you wont know what the next maxtemp time is as you haven't stored all the temps for last 24 hours.
So that leaves max temp for the day as you store the highest temp for that day till midnight and it resets
so basic idea is

if(temp > maxtemp)
maxtemp = temp
if(temp < mintemp)
mintemp = temp

schedule("60 0 0 * * ?", tempReset) //reset within 60 seconds (this is to not kill ST servers) of midnight

def tempReset() (
maxtemp = temp
mintemp = temp
)

And someway to display the min and max

test code here
https://github.com/tmleafs/Xiaomi/blob/patch-2/devicetypes/bspranger/xiaomi-aqara-temperature-humidity-sensor.src/xiaomi-aqara-temperature-humidity-sensor.groovy
I dont have one so cant test myself, no display of information just look at your device page in IDE and see if its updating, you wont see anything till the next temp update though

We should be able to schedule the reset at midnight.  Then it is the daily high and low.
I have done this with my power meter so i can see my daily high and low watt usage.

Make a pull request.  I think this looks correct.  I would have to look into the scheduler a bit more to refresh my memory.

I guess I'm not the only one, but all my temp sensors (Inc 5 aqara) are logging to Google sheets so checking this should be relatively straight forward. I can install your fork tonight to check it. Midnight for me (Paris) is in around 2 hrs so a partial test tonight and full day(ish) this time tomorrow.

dont need to install my fork the old has been merged just isnt being displayed though there is a pull request to fix stuff

Kk. no worries. Email sent me here before I checked the code.

Can anyone with a temp device confirm my code is working?

its not being displayed yet need to look at your device in IDE and see if there is values stored for max & min temp

I have a value for maxTemp but not minTemp

I don't see any code for min/max temp in the tiles, where should it be so it can be displayed?

didnt add it as I cant see what it looks like due to not having a temp device I was just adding the code to make it possible

Looked in IDE for both my  Aqara and Original Temp Sensors  - updated last night - in both cases only seeing MaxTemp, not Min
That said - my Aqara went off line last night - but a few hours after I'd updated the DTH.  Will repair now and look again.

can you try replacing

if(temp < minTemp)
to
if(temp < minTemp || minTemp == null || minTemp == "")

Then wait for the next temp change

so it's showing in the IDE - but when I do my hot breath test on it -  and temp goes from 68.3 to 68.9 0 - both min and max go up and stay the same  (min should stay at 68.3 while max goes up to 68.9 right?)

And now is temp is going down they are both going down.

Try changing

if(temp > maxTemp)

sendEvent(name: "maxTemp", value: temp, displayed: false)
if(temp < minTemp)

sendEvent(name: "minTemp", value: temp, displayed: false)

to
if(temp > device.maxTemp)
sendEvent(name: "maxTemp", value: temp, displayed: false)

if(temp < device.minTemp)
sendEvent(name: "minTemp", value: temp, displayed: false)

They are still changing in tanded- that said I've had some pairing issues which could affect it.   Will let you know more definitely by a.m.

Hiya - for some reason every single one of my Xiaomi devices went off line yesterday pm - didn't realize until this morning  (at first pass I don't think it's a DTH thing).  Busy re-pairing so it will be a while until I can test this.

If you put your app into "add thing", you should be able to just press the button on each device a few times to get them to re-add.

Sometimes that works and sometimes it creates a new dni and I have to update the device in device list.  Hoping they'll start reporting.

Is this a difference between US and EU hubs?  I literally never get Xiaomi drops, months on end they hold strong. On the other hand I expect at least 1 samsung device to drop every month or so... usually a presence sensor.  Sorry, I assume you are US due to the ridiculous temp numbers in your screenshots. Again sorry but off topic but I am genuinely surprised farenheit still gets used anywhere... is it getting phased out in schools or is it still being pushed?

Made a silly mistakes, had a brain fart last few days. I have updated the master and should definitely work (please confirm @alecm) now just needs someone to make a nice way of displaying the information now

@foz333 - I doubt it. I have not had a single device drop from my v2 hub. Well in the 2 months I've had it, anyhow.
As for the Fahrenheit thing, I think maybe people in the US just like being able to say it's over 100 degrees when it's really hot. There's was a metric campaign back in the 1970s, and that failed miserably. Old habits never die for Americans, I guess. Me personally, I lived in Vietnam for nearly a decade and had no problem working out what the temperature in Celcius meant. It is pretty silly that we don't switch.

@tmleafs - If we don't move the last checkin information up into the main info tile, then I have found a way to combine more than one piece of information into the secondary attribute text line displayed at the bottom of the main tile. Well, I'm borrowing the idea from another DTH, but that's been the best way for me to learn how to code for these sensors.

Okay, I got @tmleafs code working with the method to display two variables together up in the main tile. Here's a screenshot from my iPad (which is still running the previous iOS version of the ST mobiel app that doesn't have the messed up UI):

I did come up with a new system of resetting the min/max temps at the end of each day to avoid using a cron schedule (which ST apparently prefers not be used if at all possible), and that's the part that really needs some testing. I didn't have it perfected by midnight local time here, and it didn't work. I'm pretty sure it should work the way I have it now. It's down the in the dateFormat() function section at the very bottom of the code. Please have a look at it in my new Pull Request and let me know what you all think. I explain how it works and my reasoning in more detail in the opening comment of my Pull Request.

Wish I could help with testing - going through minor repairing everything hell - and it’s Super Bowl...but I love seeing my humidity colors implemented - thanks !

And, btw wasn’t being flip - I still can’t get either temp sensor going reliably - and my husband made a great Super Bowl meal - and I’d be dead if I spent any more time troubleshooting HA today

Closing this because it is soon to be a reality.

authors: alecm bspranger foz333 ronvandegraaf tmleafs veeceeoh

repo: bspranger/Xiaomi


text:
输入问题

输入图片为什么固定473x473,有什么意义？

论文给的473,473，你可以改成别的

authors: bubbliiiing yyyjia

repo: bubbliiiing/pspnet-pytorch


text:
Update package.json

upgraded version of react-floater to remove the deprecated popper dependency that was in the older react-floater version.

Hey,
I'm still looking at the rest of the code, but why did you remove the @gilbarbara/eslint-config package?
Overall, I want to keep everything the same in the internals now (especially the lifecycle), as doing so would break the setup for thousands of users. There are some problems with it, but the focus for these changes should be only the react-floater upgrade.
Since the react-floater has a more narrow set of React peer dependencies, this change requires a major version bump, and I want to change some other parts for this upgrade, including the state.

Hi,
Apologies - that was not intentional to remove your linter settings. I
don't know why that got removed. I'll reinstate that on my fork.
I think I see what you're saying: anyone's code that depended on the
specific timing, frequency and content of the callback props would
potentially be scuppered by this.
Having worked on it to this point, I have a much better understanding of
your design than when I started out, so I could possibly achieve the
upgrade in other ways now. I expect you'd rather make the major version
bump in your own time, but I'd be happy to help out if you'd like?
In the meantime, if this implementation is already too big a deviation from
the main branch's API, would you mind if I publish it on npm so I can use
it easily across my other projects?
Will
On Mon, 13 May 2024, 01:55 Gil Barbara, @.***> wrote:

Hey,
I'm still looking at the rest of the code, but why did you remove the
@gilbarbara/eslint-config package?
Overall, I want to keep everything the same in the internals now
(especially the lifecycle), as doing so would break the setup for thousands
of users. There are some problems with it, but the focus for these changes
should be only the react-floater upgrade.
Since the react-floater has a more narrow set of React peer dependencies,
this change requires a major version bump, and I want to change some other
parts for this upgrade, including the state.
—
Reply to this email directly, view it on GitHub
https://github.com/buchananwill/react-joyride/pull/1#issuecomment-2106447098,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BBL2M6MKIEBAGOPHYBPAVFDZCAFPJAVCNFSM6AAAAABHEOHQKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMBWGQ2DOMBZHA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Hey,
Sure, you can publish your version on npm, preferably under your username, to avoid confusion with @buchananwill/react-joyride. You could also remove the build dirs from the .gitignore files and install directly from GitHub.
Anyway, deprecated doesn't mean broken or anything; it just means the author isn't supporting the package anymore. In the case of popper.js, the old version doesn't have any outstanding bugs or vulnerabilities.

authors: buchananwill gilbarbara

repo: buchananwill/react-joyride


text:
add a simply way for generating a html report

This commit adds a mustache template which currently only has an
iteration of the licenses. When we have the actual html template we can
move and itertion to the proper location and add additional information
required.

Landed in 1f55f36456d5097fb7b9bf0a910a85d68bce7ebc

repo: bucharest-gold/licenser


text:
DMR: Technical Design

AS A Developer
I WANT a technical design covering all the components, technologies, platforms and programming languages used within a project
SO THAT I would have a clear understanding of the technical stack within which I can operate

[ ] Client requests to Chatbot
[ ] Chatbots
[ ] CentOps
[ ] DMR
[ ] Classifier
[ ] CI
[ ] CD

Was merged to main branch as an initial draft to keep working on.

authors: shelabd turnerrainer

repo: buerokratt/DMR


text:
Equality test for Request and Response types.

Is your feature request related to a problem? Please describe.
When writing unit tests, it is relatively difficult to test for equality of Response values.
As the Response typically contains a proto.Message one cannot simply
use reflect.DeepEqual as the message might have un-exported state in its fields:
type AddRequest struct {
	state         protoimpl.MessageState
	sizeCache     protoimpl.SizeCache
	unknownFields protoimpl.UnknownFields
        //...
}

Same goes for the Response header and trailer fields:
https://github.com/bufbuild/connect-go/blob/c2104c60fbd562a73076db7b442fe2e088a9a366/connect.go#L185-L190
Describe the solution you'd like
A function or method that is capable of comparing Response (and perhaps Request) objects, just like proto.equal. However, as I see it the type arguments of Response should be limited to the proto.Message interface:
type Response[T proto.Message] struct {
	Msg T

	header  http.Header
	trailer http.Header
}

And generated code should use a pointer type instead, to fulfill the interface requirement.:
Add(context.Context, *connect_go.Request[*v1.AddRequest]) (*connect_go.Response[*v1.AddResponse], error)

After that it should be trivial to test for equality:
// Equal compares this Response to x.
// It returns true when proto.Equal returns true for r.Msg
// and both header and trailers are exactly the same.
func (r *Response[T]) Equal(x *Response[T]) bool {
	if r == nil || x == nil {
		return r == nil && x == nil
	}

	return proto.Equal(r.Msg, x.Msg) && equalHeader(r.header, x.header) && equalHeader(r.trailer, x.trailer)
}

// equalHeader compares http.Header a and b
// and returns true if each key is matched with
// the exact same slice of values.
func equalHeader(a, b http.Header) bool {
	if a == nil || b == nil {
		return a == nil && b == nil
	}

	if len(a) != len(b) {
		return false
	}
	for k, as := range a {
		bs, ok := b[k]
		if !ok {
			return false
		}

		if len(as) != len(bs) {
			return false
		}

		for i, v := range as {
			if v != bs[i] {
				return false
			}
		}
	}
	return true
}

Describe alternatives you've considered
Currently I would need to write lots of boilerplate code in unit tests, that basically is similar to the above:
if tt.want == nil || got == nil {
	if tt.want != nil || got != nil {
		t.Fatalf("CountServiceHandler.add() = %v, want %v", got, tt.want)
	}
}

if tt.want != nil || got != nil {
	if !proto.Equal(got.Msg, tt.want.Msg) {
		t.Errorf("CountServiceHandler.add() = %v, want %v", got, tt.want)
	}
}

if !equalHeader(tt.wantHeader, got.Header()) {
	t.Errorf("CountServiceHandler.add() header = %v, want %v", got.Header(), tt.wantHeader)
}

if !equalHeader(tt.wantTrailer, got.Header()) {
	t.Errorf("CountServiceHandler.add() trailer = %v, want %v", got.Trailer(), tt.wantTrailer)
}

Additional context
This is one of the mayor downsides when migrating a project from gRPC to Connect. The former I could just use proto.Equal and now all tests have to expanded with this boilerplate code.

I was unaware of the portability to other generators. Thanks for the explanation and de cmp suggestions.

repo: bufbuild/connect-go


text:
Пустое окно после установки

Установил из brick-0.2.11.34-1.fc26.x86_64.rpm на Fedora 27
Ругани при установке не было
Приложение запускается, но окно пустое.
Пробовал собрать из исходников - не получилось - #75

по ldd все библиотеки есть

Solution: https://github.com/buglloc/brick/issues/67#issuecomment-350572237

As workaround, you can start brick with the following command:
brick --disable-seccomp-filter-sandbox

помогло, но появился еще вопрос: после закрытия окна приложения осталось работать аж 4 процесса brick
Почему их 4?
Что они делают?
какой смысл имеет указанный ключ?
Как правильно убить эти процессы?

repo: buglloc/brick


text:
xdai support

Changes

How to test these changes?
Tested locally
Related issues

@bugout-dev check

[ ] First merge PR https://github.com/bugout-dev/moonstream/pull/613

repo: bugout-dev/moonworm


text:
Add warning in BAGP for React Native when running via react-native CLI

Goal
Adds a warning when installRelease is run in React Native. This indicates that the user ran react-native run-android --variant=release, whereas a user should run ./gradlew assembleRelease or ./gradlew bundleRelease to generate an artifact for which sourcemaps should be uploaded. This warning is only logged when a task named 'installRelease' is created in the project and JS sourcemap upload is enabled.
Testing
Ran ./gradlew assembleRelease and react-native run-android to confirm no message was received, and that the warning was only logged for react-native run-android --variant=release

Addressed feedback, and additionally caught an exception which was failing the E2E tests.

Addressed feedback, and additionally caught an exception which was failing the E2E tests.

Addressed feedback, and additionally caught an exception which was failing the E2E tests.

Addressed feedback, and additionally caught an exception which was failing the E2E tests.

repo: bugsnag/bugsnag-android-gradle-plugin


text:
update goselect to get riscv support

This updates the goselect dependency to support riscv

thank you!

authors: cbrake cmaglie

repo: bugst/go-serial


text:
Library - Validate CBOR structs according to the cddl schema for nodes/models/portal

The ockam_api crate exchanges many structs with the Controller. Those structs are serialized using CBOR and should conform to the cddl schema.
Currently there are only a handful of structs tested for conformance to the schema:

project (and related structs)
space (and related structs)
subscription (and related structs)

The purpose of this issue is to complete the testing by:

adding more quickcheck properties similar to the ones above
adding missing schema.cddl definitions where necessary
additionally remove the lifetime annotations on structs, like this one (and replace CowStr<'a> with String)

To the following list of structs:

nodes/models/portal/CreateInlet
nodes/models/portal/CreateOutlet
nodes/models/portal/InletStatus
nodes/models/portal/OutletStatus
nodes/models/portal/InletList
nodes/models/portal/OutletList

[!NOTE]
Related epic: https://github.com/build-trust/ockam/issues/6235

We love helping new contributors! ❤
If you have questions or need help as you explore, please join us on Discord. If you're looking for other issues to contribute to, please checkout our good first issues.

@nazmulidris @mrinalwadhwa hello there!
Could you assign this issue to me? Looks pretty straightforward and simple

@wowinter13 That's awesome, this is all yours. Please let us know if you have any questions as you explore. You can also ask questions on the contributors discord https://discord.ockam.io

repo: build-trust/ockam


text:
ci: add global default shell to release-binaries workflow

Signed-off-by: murex971 nupur202000@gmail.com

Fixes : #4004
Current Behavior

Proposed Changes

Checks

[x] All commits in this Pull Request are signed and Verified by Github.
[x] All commits in this Pull Request follow the Ockam commit message convention.
[x] I accept the Ockam Community Code of Conduct.
[x] I have accepted the Ockam Contributor License Agreement by adding my Git/Github details in a row at the end of the CONTRIBUTORS.csv file in a separate pull request to the build-trust/ockam-contributors repository.

@murex971 have a look at how commit messages can be signed with GPG or SSH keys. In the previous PRs I signed them on your behalf but it would be better if you can sign them.
https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits
This is why this check is failing https://github.com/build-trust/ockam/actions/runs/4098791629/jobs/7068289870

@mrinalwadhwa  I did signoff the commit

ci: add global default shell to release-binaries workflow
Signed-off-by: murex971 <nupur202000@gmail.com>


text:
Move Bazel flags into xcodeproj.bazelrc

Besides for these flags being more discoverable now, it also removes --features from the xcodeproj transition, preventing the Starlark hash from changing when features are added or removed from the build.

Draft only because I don't want to merge #950 yet. Ready for review.


text:
Generalize build key description re: parallelized builds

This PR generalizes our language around unique build key because the exact env var will be different depending on CI (Build ID was a little Buildkite-specific, and perhaps hard to match up on the CI page).
For example:

For Buildkite, it is BUILDKITE_BUILD_ID
For Circle, it is CIRCLE_WORKFLOW_ID-$CIRCLE_BUILD_NUM
For GH Actions, it is GITHUB_ACTION-$GITHUB_RUN_NUMBER-$GITHUB_RUN_ATTEMPT
For generic CI, it is BUILDKITE_ANALYTICS_KEY

Happy for wordsmith humans to suggest better words in place of the ones I chose, should inspiration strike ⚡💡. Like, would unique build key be better than unique build identifier? 🤷🏻♂

@plaindocs @karensawrey I took another crack at that sentence, taking the lead from what @plaindocs wrote. What do you think?

@meiqimichelle I do like the expanded version 👍

@meiqimichelle let's merge ;)

authors: karensawrey meiqimichelle

repo: buildkite/docs


text: 9-3A-1204026-HARYADI YUSUF

repo: bukped/geojson


text:
🛑 VODA-DRC is down

In 7ed0fc2, VODA-DRC ($SECRET_SITE1) was down:

HTTP code: 403
Response time: 1108 ms

Resolved: VODA-DRC is back up in 27ac2a0.

repo: buluma/uptime


text:
prevent naming mistake

This is an attempt at rebasing #3123 and integrating the recommended changes mentioned in that PR’s comments.

Thanks!

:beers:

authors: BM5k indirect tonytonyjan

repo: bundler/bundler


text:
select a pre-release if it's specified in the Gemfile

What was the end-user problem that led to this PR?
The problem was #6449
Closes #6449
What was your diagnosis of the problem?
My diagnosis was that Bundler didn't select a pre-release even if one of the dependencies of a gem was specified with a pre-release version in the Gemfile.
What is your fix for the problem, implemented in this PR?
My fix is to change Bundler::Resolver#requirement_satisfied_by? so that it does not reject a pre-release if at least one of the dependencies is pre-released.
Why did you choose this fix out of the possible options?

Thanks!
@greysteil any objections to me merging this?

@akihiro17 - nice work on this! It's a thorny part of the resolution process to be digging into. I've confirmed locally that this fixes the issue and the test is 👌.
As I understand it, the logic here is "allow a pre-release version for a non-pre-release requirement if any of the sub-dependency requirements of that pre-releases version specify pre-releases".
I don't think that logic makes sense, and think this might instead be working because actually we can remove line 186-189 entirely. It was added before #6014 was, and I think #6014 should do everything required to ensure pre-releases aren't selected when another option is possible.
What do you reckon? Am I missing something in the logic here?

Thank you for your review.
I think we can remove pre-release logic(line 186-19) from requirement_satisfied_by? because #6014 seems to avoid pre-release when a non-pre-release version is possible.

Awesome - do you want to update this PR with that change? I'm then 👍. @segiddins - sound good to you?

I'll update the PR soon.
Thanks.

This seems fine? But with this sort of changes, I've learned it's hard to be 100% sure ahead of time
@bundlerbot r+

authors: akihiro17 greysteil segiddins


text:
Update config for resource

I configure authentication token for my request with:
configure("**") {     if let token = authenticationToken {         $0.headers["AUTHTOKEN"] = token     } }
This configuration is cached in the Resource. How can purge this when a user logs out and the token is updated?

The configuration docs in the user guide answer this question:
http://bustoutsolutions.github.io/siesta/guide/configuration/#configuration-that-changes

authors: mikaelbartlett pcantrell

repo: bustoutsolutions/siesta


text:
Image doesn't render in the post

Expected behavior
The image should be rendered since it is showed in the post preview.
Actual behavior
The image renders in the post preview and in the image gallery but not in the post itself. This may be caused by the incorrect format of the image (see src and alt attributes).
How to reproduce

Go to @dream.trip
Find The Big Buddha is Busy place /photography/@dream.trip/the-big-buddha-is-busy-place
See that image appears in the preview
Open the post
Image doesn't show up

Browser: Chrome
Operating system: Windows 10

This isn't a bug. If you goto https://steemd.com/photography/@dream.trip/the-big-buddha-is-busy-place and look at the original markdown text you can see he put ![![20171002_172210.jpg](https://res.cloudinary.com/hpiynhbhq/image/upload/v1507061630/rdrydpyewrhpfhx0agn7.jpg)](url) This means it should be a link with a href of "url". The reason it has a preview picture is because the parser saw the link, and added the picture link to the links array, and into the image object, in the json_metadata.

This isn't a bug. If you goto https://steemd.com/photography/@dream.trip/the-big-buddha-is-busy-place and look at the original markdown text you can see he put ![![20171002_172210.jpg](https://res.cloudinary.com/hpiynhbhq/image/upload/v1507061630/rdrydpyewrhpfhx0agn7.jpg)](url) This means it should be a link with a href of "url". The reason it has a preview picture is because the parser saw the link, and added the picture link to the links array, and into the image object, in the json_metadata.

It's not a bug, but formatting error.

authors: Kennybll Sekhmet espoem renderfiles

repo: busyorg/busy


text:
Blackbird not making trades [help wanted]

My config:
/# Program parameters
DemoMode=false
UseFullCash=false
UntouchedCash=0.01
CashForTesting=40.00
MaxExposure=100.00
MaxLength=5184000
DebugMaxIteration=3200000
Verbose=true
/# Strategy parameters
GapSec=3.0
SpreadEntry=0.0080
SpreadTarget=0.0030
PriceDeltaLimit=0.10
AggressiveVolume=true
TrailingSpreadLim=0.0010
OrderBookFactor=1.5
Few log entries:
Bitfinex/Kraken:      0.10% [target  0.80%, min -0.70%, max  0.83%]
OKCoin/Bitfinex:      0.35% [target  0.80%, min -0.51%, max  0.56%]
OKCoin/Kraken:        0.46% [target  0.80%, min -0.80%, max  1.12%]
Kraken/Bitfinex:     -0.87% [target  0.80%, min -1.15%, max  0.34%]
...
Bitfinex/Kraken:     -0.06% [target  0.80%, min -1.73%, max  0.22%]
OKCoin/Bitfinex:      0.05% [target  0.80%, min -0.47%, max  0.59%]
OKCoin/Kraken:       -0.01% [target  0.80%, min -1.66%, max  0.23%]
Kraken/Bitfinex:     -0.16% [target  0.80%, min -0.66%, max  1.34%]
Why it did not make a single trade?
I have $50 on each exchange.

Hi @j4r3kb,
Did you change KrakenCanShort to true? The API to short sell on Kraken doesn't exist yet, so it's impossible to automatically short sell on Kraken for the moment.
I will remove the canShort parameters from the config file so there won't be any more confusion.
Yes, according to this line:
Kraken/Bitfinex: -0.16% [target 0.80%, min -0.66%, max 1.34%]

you should have gotten a trade, if there were enough volume. Can you please send me your log file?
Note that the Kraken connection has never been fully tested. It's explicit in the Changelog but I'll make it more obvious in the README file. Thanks.

No, I did not change any option *CanShort to true (beside leaving default Bitfenix true).
I've attached all my logs with csv.
logs.tar.gz

Thank you. I'll take a look at it.

I just fixed the issue with KrakenCanShort

I just need to update and compile or change any settings too?

Just update and compile. You won't see Kraken on the short side anymore.

Hi @j4r3kb,
You didn't get any trade at that time because the spread between Kraken and Bitfinex went directly from 0.55% to 1.34% and back to 0.55% within 21 seconds and without triggering the trailing stop.
[ 01/07/2016 09:24:15 ]
   Kraken/Bitfinex:	 0.55% [target  0.80%, min  0.42%, max  0.87%]

[ 01/07/2016 09:24:18 ]
   Kraken/Bitfinex:	 1.34% [target  0.80%, min  0.42%, max  1.34%]

[ 01/07/2016 09:24:21 ]
   Kraken/Bitfinex:	 1.34% [target  0.80%, min  0.42%, max  1.34%] trailing 1.24%  0/2

[ 01/07/2016 09:24:24 ]
   Kraken/Bitfinex:	 1.34% [target  0.80%, min  0.42%, max  1.34%] trailing 1.24%  0/2

[ 01/07/2016 09:24:39 ]
   Kraken/Bitfinex:	 0.55% [target  0.80%, min  0.42%, max  1.34%] trailing 1.24%  0/2

[ 01/07/2016 09:24:42 ]
   Kraken/Bitfinex:	 0.55% [target  0.80%, min  0.42%, max  1.34%]

It usually happens when a small limit order arrives in front of the order book. It doesn't really represent a true discrepancy between the exchanges as the volume of that order is usually too low.
If you want to trade this kind of situation anyway it's totally possible: just set TrailingSpreadLim=0.0000.

repo: butor/blackbird


text:
Add auto-discovery for Home Assistant

hi. thank you for contributing. Your project very useful. Can you please add auto-discovery function??
here is the example of  implementation: repo
thanks

FYI, this should be available shortly, I've been putting some final tweaks to auto discovery.

Support for this has been pushed to the repo, please give it a try and report back.

working for me

great!

Hi Bus:) BIG THANKS for your hot-damn-cool code! WORKS GREAT - besides the Auto Discovery. I can't get it to work. I have it enabled in the config and HA but nothing shows up. I don't know how to troubleshoot it:(

authors: MrBigleg T-REX-XP buxtronix jascdk


text:
Added remove_delayed_with_queue and remove_delayed_job_from_timestamp_with_queue methods.

I needed those so I added them. I've added two tests for them and cleaned up whitespaces in the files I've touched.

Also made a small styling fix so that the "Queue now" button display correctly.

repo: bvandenbos/resque-scheduler


text:
🛑 Sai Gardens is down

In 935fecb, Sai Gardens (https://cloud.tymly.in/status/1066) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sai Gardens is back up in 42be2fb.

repo: bvenkysubbu/tymlymonitor


text:
🛑 Sowparnika Ananda D Block is down

In 116552d, Sowparnika Ananda D Block (https://cloud.tymly.in/status/1061) was down:

HTTP code: 521
Response time: 20243 ms

Resolved: Sowparnika Ananda D Block is back up in 368557f.


text:
🛑 SNR Silver Ripples 2 is down

In 6e1b42c, SNR Silver Ripples 2 (https://cloud.tymly.in/status/1040) was down:

HTTP code: 521
Response time: 226 ms

Resolved: SNR Silver Ripples 2 is back up in 23551f1.


text:
🛑 Sterling Villa Grande is down

In c7ba253, Sterling Villa Grande (https://cloud.tymly.in/status/1068) was down:

HTTP code: 521
Response time: 232 ms

Resolved: Sterling Villa Grande is back up in ebe387c.


text:
🛑 Hinduja Park 1 is down

In fc6dea5, Hinduja Park 1 (https://cloud.tymly.in/status/1067) was down:

HTTP code: 521
Response time: 2583 ms

Resolved: Hinduja Park 1 is back up in 9eb0e87.


text:
🛑 SMR Vinay Cascade A Block is down

In 01daed3, SMR Vinay Cascade A Block (https://cloud.tymly.in/status/1094) was down:

HTTP code: 521
Response time: 20240 ms

Resolved: SMR Vinay Cascade A Block is back up in 23647c4.


text:
🛑 Dasta Concerto Basement is down

In 758f018, Dasta Concerto Basement (https://cloud.tymly.in/status/1138) was down:

HTTP code: 521
Response time: 20230 ms

Resolved: Dasta Concerto Basement is back up in 38184f5.


text:
🛑 Prakruthi Villas Sarjapura is down

In caa1750, Prakruthi Villas Sarjapura (https://cloud.tymly.in/status/1058) was down:

HTTP code: 521
Response time: 235 ms

Resolved: Prakruthi Villas Sarjapura is back up in ca0fa2a.


text:
🛑 United Elysium 2 is down

In 1b49973, United Elysium 2 (https://cloud.tymly.in/status/1026) was down:

HTTP code: 521
Response time: 8128 ms

Resolved: United Elysium 2 is back up in c98dcd9.


text:
🛑 PSR Aster 4 C Block is down

In 551944d, PSR Aster 4 C Block (https://cloud.tymly.in/status/1065) was down:

HTTP code: 521
Response time: 216 ms

Resolved: PSR Aster 4 C Block is back up in cfbee33.


text:
🛑 SMR Vinay Cascade A Block is down

In 5d2394f, SMR Vinay Cascade A Block (https://cloud.tymly.in/status/1094) was down:

HTTP code: 521
Response time: 20221 ms

Resolved: SMR Vinay Cascade A Block is back up in cfac3e2.


text:
🛑 Prakruthi Villas Sarjapura is down

In 5f0a210, Prakruthi Villas Sarjapura (https://cloud.tymly.in/status/1058) was down:

HTTP code: 521
Response time: 227 ms

Resolved: Prakruthi Villas Sarjapura is back up in bb74a03.


text:
🛑 SMR Vinay Cascade A Block is down

In a0f3368, SMR Vinay Cascade A Block (https://cloud.tymly.in/status/1094) was down:

HTTP code: 521
Response time: 20248 ms

Resolved: SMR Vinay Cascade A Block is back up in e2db344.


text:
🛑 Trifecta Esplanade Security is down

In 361af37, Trifecta Esplanade Security (https://cloud.tymly.in/status/1168) was down:

HTTP code: 521
Response time: 20256 ms

Resolved: Trifecta Esplanade Security is back up in 825789f.


text:
🛑 Whitestone Landmark is down

In 2fe99e6, Whitestone Landmark (https://cloud.tymly.in/status/1095) was down:

HTTP code: 521
Response time: 229 ms

Resolved: Whitestone Landmark is back up in daa8e08.


text:
🛑 Nitesh Flushing Meadows Block B is down

In 6fb19aa, Nitesh Flushing Meadows Block B (https://cloud.tymly.in/status/1047) was down:

HTTP code: 521
Response time: 20241 ms

Resolved: Nitesh Flushing Meadows Block B is back up in 7db5f9f.


text:
🛑 Desai Grandeur 1 is down

In 19476b9, Desai Grandeur 1 (https://cloud.tymly.in/status/1133) was down:

HTTP code: 521
Response time: 20235 ms

Resolved: Desai Grandeur 1 is back up in 51383d6.


text:
🛑 SMD Altezz Block B is down

In ca92d4d, SMD Altezz Block B (https://cloud.tymly.in/status/1176) was down:

HTTP code: 521
Response time: 213 ms

Resolved: SMD Altezz Block B is back up in dce20c8.


text:
🛑 Desai Grandeur 1 is down

In 4f43927, Desai Grandeur 1 (https://cloud.tymly.in/status/1133) was down:

HTTP code: 521
Response time: 20222 ms

Resolved: Desai Grandeur 1 is back up in c6daa89.


text:
🛑 United Elysium is down

In b24dd16, United Elysium (https://cloud.tymly.in/status/1019) was down:

HTTP code: 521
Response time: 20216 ms

Resolved: United Elysium is back up in 6cbe584.


text:
🛑 Trifecta Esplanade P Block is down

In 5d6789f, Trifecta Esplanade P Block (https://cloud.tymly.in/status/1017) was down:

HTTP code: 521
Response time: 20219 ms

Resolved: Trifecta Esplanade P Block is back up in 97a25d6.


text:
🛑 SMD Altezz Block B is down

In 3b834e0, SMD Altezz Block B (https://cloud.tymly.in/status/1176) was down:

HTTP code: 521
Response time: 20255 ms

Resolved: SMD Altezz Block B is back up in 0c49668.


text:
🛑 SMD Altezz Block C is down

In 6dff122, SMD Altezz Block C (https://cloud.tymly.in/status/1177) was down:

HTTP code: 521
Response time: 20235 ms

Resolved: SMD Altezz Block C is back up in 00970a1.


text:
🛑 Trifecta Esplanade B Block is down

In ee1c940, Trifecta Esplanade B Block (https://cloud.tymly.in/status/1154) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Trifecta Esplanade B Block is back up in d6090db.


text:
🛑 Sowparnika Ananda is down

In 3932e7a, Sowparnika Ananda (https://cloud.tymly.in/status/1036) was down:

HTTP code: 521
Response time: 20238 ms

Resolved: Sowparnika Ananda is back up in 6677d5f.


text:
🛑 SMR Vinay Cascade A Block is down

In 929a31e, SMR Vinay Cascade A Block (https://cloud.tymly.in/status/1094) was down:

HTTP code: 521
Response time: 20236 ms

Resolved: SMR Vinay Cascade A Block is back up in aaf1070.


text:
🛑 SMR Vinay Cascade A Block is down

In e453e81, SMR Vinay Cascade A Block (https://cloud.tymly.in/status/1094) was down:

HTTP code: 521
Response time: 25578 ms

Resolved: SMR Vinay Cascade A Block is back up in 398a566.


text:
Sonoff Zigbee Motion Sensor SNZB-03

What issue do you have? Please be as thorough and explicit as possible.
While using the motion sensor, sometimes it gets stuck on “motion detected”. At first I thought it was a problem with the device or the eWeLink app, but when I restart homebridge, the sensor stays in no motion detected until I wave in front off it, it then flashes the red light but doesn’t trigger any automation, and the movement is not logged in the eWeLink app.
But after a while, and one or two attempts, everything starts working as expected.
Details of your setup.

Do you use (1) Homebridge (+ config-ui), (2) Homebridge (CLI) or (3) HOOBS?

I use homebridge+config-ui

Which version of Homebridge/HOOBS do you have?

I have homebridge 1.3.1, but it happened in previous versions.

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

I run homebridge in a Raspberry Pi, Node.js version 14.15.5 and NPM 7.5.4

Which version of this plugin (homebridge-ewelink) do you have? Has the issue started since upgrading from a previous version?

I have version 4.7.6, it happened on previous versions.

Which eWeLink devices do you have that are causing issues? Please include product models if applicable.

I have some zigbee temperature and WiFi door sensors working with no problems, theming issue is with zigbee motion sensor SNZB-03
Please paste any relevant logs below.
no relevant logs as I’m aware.

Hi @ojoaosemtil
The device sends its current status to eWeLink and eWeLink sends this information onto the plugin. The plugin doesn't and cannot create log entries for motion detected in the eWeLink app.
When motion is detected, ewelink sends a notification to the plugin which in turns sets the state of the HomeKit motion sensor. Then after 60 seconds of no further motion detected by the device, ewelink will send a notification to the plugin and the plugin will update the HomeKit motion sensor with no motion detected.
In short, the plugin completely relies on updates from ewelink for both 'motion detected' and 'no motion detected' notifications. (which is different for e.g. rf bridge motion sensors where the plugin will automatically set the sensor back to 'no motion detected' after X seconds).

sometimes it gets stuck on “motion detected”

Either:

If the sensor detects motion then it starts checking for a period of 60 seconds of no motion. If, say, the sensor detects motion 40 seconds after the first detection, then this 60 seconds will reset. The HomeKit motion sensor will say 'motion detected' during this entire time.

The plugin is not receiving the notification from eWeLink that no motion has been detected for 60 seconds.

You are correct in that, currently, if you restart Homebridge, all motion sensors will be reset to 'no motion detected'. This is in case ewelink sends a 'no motion detected' notification whilst Homebridge is restarting, in this case the notification will not be registered by the plugin and the HomeKit sensor will indefinitely say 'motion detected'.
I hope I have answered your question with the above info?
Thanks

Oh thank you so much for the explanation!
So the problem is the eWeLink server, it makes sense...
I have a firmware update available in the zigbee bridge, but everytime I try, it fails to update at 90%.
I know it has nothing to do with your plugin but I thought maybe you’re aware of this and have any work around...
Thanks in advance, and thank you for you work!

Do you use your main ewelink credentials for the plugin?

Yes, email and password are the same as the ewelink app

That's okay, I was just going to say if you use a secondary account (like some people do) sometimes (not a lot) notifications can get missed.

No, that’s not the case..but I’m searching online and started to figure that many people has some sort of issues with this motion sensor and the bridge firmware updates.

I found this in the homebridge logs:
[23/02/2021, 18:31:53] [eWeLink] [Sensor Closet] initialised and LAN mode unavailable as not supported.
[23/02/2021, 18:31:53] [eWeLink] [Sensor Office] initialised and LAN mode unavailable as not supported.
[23/02/2021, 18:31:53] [homebridge-ewelink] This plugin generated a warning from the characteristic 'Motion Detected': characteristic value expected boolean and received undefined. See https://git.io/JtMGR for more info.
[23/02/2021, 18:31:53] [eWeLink] [Sensor Cozinha] initialised and LAN mode unavailable as not supported.
[23/02/2021, 18:31:53] [eWeLink] [Janela Sala] initialised and LAN mode unavailable as not supported.
[23/02/2021, 18:31:53] [eWeLink] [Porta Escritório] initialised and LAN mode unavailable as not supported.
[23/02/2021, 18:31:53] [homebridge-ewelink] This plugin generated a warning from the characteristic 'Last Activation': characteristic was expected valid number and received NaN. See https://git.io/JtMGR for more info.
[23/02/2021, 18:31:53] [eWeLink] [Porta Quarto] initialised and LAN mode unavailable as not supported.
[23/02/2021, 18:31:53] [eWeLink] ✓ Setup complete. Have a feature request? Visit http://bit.ly/hb-ewelink-issues to ask!
“Sensor Cozinha” is the motion sensor.
This appears everytime homebridge restarts

Could you run Homebridge in DEBUG mode (not the plugin setting for debug but the main homebridge debug option)
and post the logs that that generates?

Sure, here it is ("Sensor Cozinha" is the motion sensor):
[23/02/2021, 19:01:52] [eWeLink] [Sensor Closet] initialised and LAN mode unavailable as not supported.
[23/02/2021, 19:01:52] [eWeLink] [Sensor Office] initialised and LAN mode unavailable as not supported.
[23/02/2021, 19:01:52] [homebridge-ewelink] This plugin generated a warning from the characteristic 'Motion Detected': characteristic value expected boolean and received undefined. See https://git.io/JtMGR for more info.
[23/02/2021, 19:01:52] [homebridge-ewelink] Error:
at MotionDetected.Characteristic.characteristicWarning (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2164:105)
at MotionDetected.Characteristic.validateUserInput (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1931:16)
at MotionDetected.Characteristic.updateValue (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1365:20)
at MotionSensor.Service.updateCharacteristic (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Service.ts:465:35)
at deviceZBSensorMotion.externalUpdate (/usr/local/lib/node_modules/homebridge-ewelink/lib/device/zigbee/sensor-motion.js:67:22)
at eWeLinkPlatform.initialiseDevice (/usr/local/lib/node_modules/homebridge-ewelink/lib/index.js:1093:27)
at /usr/local/lib/node_modules/homebridge-ewelink/lib/index.js:437:47
at Map.forEach ()
at eWeLinkPlatform.pluginSetup (/usr/local/lib/node_modules/homebridge-ewelink/lib/index.js:437:24)
at runMicrotasks ()
at processTicksAndRejections (internal/process/task_queues.js:93:5)
[23/02/2021, 19:01:52] [eWeLink] [Sensor Cozinha] initialised and LAN mode unavailable as not supported.
[23/02/2021, 19:01:52] [eWeLink] [Janela Sala] initialised and LAN mode unavailable as not supported.
[23/02/2021, 19:01:52] [eWeLink] [Porta Escritório] initialised and LAN mode unavailable as not supported.
[23/02/2021, 19:01:53] [eWeLink] [Porta Quarto] initialised and LAN mode unavailable as not supported.
[23/02/2021, 19:01:53] [eWeLink] ✓ Setup complete. Thanks for using this plugin, I hope you find it helpful!

Could I message you on Discord?
https://discord.gg/cMGhNtZ3tW

Ok I accepted your invite!


text:
Leak Sensor does not update after water alarm

I just installed the Homebridge-Govee plug in for Homebridge and am able to see all of the Govee H5054 leak sensors.
When I attempt to test them (water to alarm), I notice a leak alert within the Govee app, but not through HomeKit.  Then, when inspecting the HomeBridge log, I see the following:
[10/10/2022, 18:35:44] [Govee] [Bathroom] could not be refreshed as no data received from Govee server whilst obtaining devices at default.getLeakDeviceWarning (file:///var/lib/homebridge/node_modules/homebridge-govee/lib/connection/http.js:147:13).
Where Bathroom is the temporary name given to this sensor.
Here is the detailed log:
[10/10/2022, 18:40:44] [Govee] [H5054_843E] [HTTP] receiving update [{"source":"HTTP","battery":100,"leakDetected":false,"online":true}].
[10/10/2022, 18:40:44] [Govee] [Bathroom] raw data: {"online":true,"gwonline":true,"lastTime":1665440160000,"read":false,"battery":100,"openPush":true,"header":"2","gatewayVersionHard":"1.00.04","gatewayVersionSoft":"1.05.06","sku":"H5054","device":"CAC9A35F1128008491","deviceName":"Bathroom","versionHard":"1.0.0","versionSoft":"1.0.0"}.
[10/10/2022, 18:40:44] [Govee] [H5054_83F5] raw data: {"online":true,"gwonline":true,"lastTime":0,"read":false,"battery":100,"openPush":true,"header":"3","gatewayVersionHard":"1.00.04","gatewayVersionSoft":"1.05.06","sku":"H5054","device":"CAC9A35F11280083F5","deviceName":"H5054_83F5","versionHard":"1.0.0","versionSoft":"1.0.0"}.
[10/10/2022, 18:40:44] [Govee] [H5054_83F5] [HTTP] receiving update [{"source":"HTTP","battery":100,"leakDetected":false,"online":true}].
[10/10/2022, 18:40:44] [Govee] [Thermometer] [HTTP] receiving update [{"source":"HTTP","battery":100,"temperature":2050,"humidity":4350,"online":true}].
[10/10/2022, 18:40:45] [Govee] [Bathroom] could not be refreshed as no data received from Govee server whilst obtaining devices at default.getLeakDeviceWarning (file:///var/lib/homebridge/node_modules/homebridge-govee/lib/connection/http.js:147:13).

Hi @p51mustang
Please update to the beta version of the plugin you should find the leak sensors work in this version.
When you update and test the sensors, please wait up to 30 seconds for the homekit notification to come through. Then it will deactivate when you open the govee app and click “Got it” on the sensor messages page.

Thank you.  I've installed and will test today.
On Tuesday, October 11, 2022, 02:08:10 AM EDT, Ben @.***> wrote:
Hi @p51mustang
Please update to the beta version of the plugin you should find the leak sensors work in this version.
When you update and test the sensors, please wait up to 30 seconds for the homekit notification to come through. Then it will deactivate when you open the govee app and click “Got it” on the sensor messages page.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


text:
Changed switch name in Meross app, not reflected in the plug in

What issue do you have? Please be as thorough and explicit as possible.
I changed the name of a switch in the Meross app, but the "old" name has persisted on the Homebridge plugin, despite reboots, upgrades etc.
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?

Homebridge UI-X

Which version of Homebridge/HOOBS do you have?

Homebridge v1.7.0 · UI v4.54.1 · UI developed by oznu

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

Raspberry PI/Docker version,  node.js v18.19

Which version of this plugin (homebridge-meross) do you have? Has the issue started since upgrading from a previous version?

v1.1.5

Which Meross devices do you have that are causing issues? Please include product models if applicable.

mss210 switch
Please paste any relevant logs below.

It's likely that your switch's config is cached by Homebridge. In the top right of Homebridge click the 3 dots and then go to Homebridge Settings. Near the bottom is Remove Single Cached Accessory. Give that a shot, restart Homebridge, and I believe that should bring it back with the new name. Alternatively, you can just update the name in Homebridge yourself on the Accessories page.
Be warned that clearing a cached item can remove it from any automations that you might have setup through the Home or Shortcuts apps so it could force you to need to reset those automations. If you have a lot of them I would recommend just manually updating the name.

thanks, that did the trick, I did try renaming it on the accessories page, but the log still referred to it as the old name.

I don't have an ability to close your issue but if you're able to that'll help to reduce load on the maintainer from having to triage this issue at some point in the future.

authors: gileswells kitenski


text:
HTTPS setting not sticking

Trying to get HA-bridge to use HTTPS. Using Smarthings and bridging HA-bridge to control my X10 devices. Was working with Smartthings on port 8080 until a recent update to smartthings makes ST try to use HTTPS when a HUE reports V2. I added a cert file according to the instructions but when I reinitialize the system after setting HTTPS to true the setting returns to false. Is there a log I can look at to see why it is disabling? Running on Pi. (linux newbie)
The only changes I am making to enable HTTPS is setting to true, path to keyfile, and password. Is there something else I need to change? I assume the HA-bridge should be accessible on 443 if I am successful?

I have the exact same issue.  I have not been able to get the use HTTPS setting to stick either.

You need to look at your log to see if there were any errors using the cert. It there is, the bridge defaults back to HTTP so as not to lock you out.

I'm not seeing anything in the logs related to security or HTTPS. I see an entry the security settings were updated but nothing further on HTTPS. Is there specific logging entries I need to enable or set to debug to see it? I'm running 35.3.0

Looks like none of the settings from the "Bridge Control" page stick for me after clicking save.

Created this same problem for myself when I changed the "Configuration Path and File" input setting on the Bridge Control page, but didn't update the systemctl service file to match the update.

Yes, make sure your paths are correct based on the relative path of the user starting the process. If it is the system, you need to set the path on the command line as it will not find root or your directories.

Adding the config file path to the startup command in the service file allowed me to be able to save settings. I am now able to save the set HTTPS true setting and it sticks. What is strange is that the certificate path and password settings were saving just not the HTTPS true settings. Another thing to note is enabling HTTPS does not change the port to 443, that needed to be set separately.

repo: bwssytems/ha-bridge


text:
Use ngrx store for account capabilities

Now it is received in AuthService

To tests
REQ_LOGIN_001
REQ_LOGIN_004
REQ_VM_CREATE_011
REQ_VM_DTLS_013
REQ_VM_DTLS_046
REQ_STORAGE_LIST_008
REQ_STORAGE_LIST_015
REQ_VM_CREATE_010
REQ_VM_CREATE_012
Allowed to view destroyed VMs

Login, logout, and refresh (F5)
Min and max sizes of volume creation and resize everywhere (they should be loaded properly when controls appear on screen)
VM destroy and expunge (check that canExpungeOrRecoverVm in CS capabilities works correctly)

Lack: 1
The status "Destroyed" is not in the filter by VM status
The error repeats regardless of the value of the global setting "allowuserviewdestroyedvm"
Steps to reproduce:

Make sure the global setting "allowuserviewdestroyedvm" is set to "true"
Log in to the "Virtual machines" section
Open the drop-down list of the filter "Select states"

Actual result: "Destroyed" item is not on the list
Expected result: The item "Destroyed" is on the list

Tested on 1466

authors: ershovaelena rennervo wowshakhov

repo: bwsw/cloudstack-ui


text:
feat: wip stealth dark mode

Types of Changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue, please reference the issue id)
[ ] New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] All new and existing tests passed

Description
[Place a meaningful description here.]

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: bylapidist/components


text:
Bump crate versions

Release latest changes such as:

wasm-tools compose now supports -t (#1148)
The abi module is removed from the wit-parser crate (#1149, #1159)
Fix validation of lowered functions in the component model (#1150)
Fix a panic decoding WIT from a component (#1157)
Add text format and printing support for dylink.0 (#1135)
Support shared-everything linking in wasm-tools component new (#1133)
Printing a WIT document now prints comments as well (#1167)
Disallow (borrow $t) in component function results (#1162)

This was requested originally in https://github.com/bytecodealliance/wit-bindgen/pull/637

repo: bytecodealliance/wasm-tools


text:
fuzzgen: Add SIMD only mode

👋 Hey,
Feature
We should add a SIMD only mode to fuzzgen. Where every input generates at least one vector variable or maybe a vector instruction.
Benefit
This would have been really useful when developing the RISC-V SIMD backend since I was only really interested in fuzzing the newer SIMD instructions.
Implementation
An easy way to do this is to check the signature of every function generated by fuzzgen and reject it if it does not contain a vector type.
I think it would be nice to have this as an environment flag so that it would be usable during development.
Alternatives
We don't have to do this, fuzzgen will theoretically reach those inputs eventually. But in my experience it takes quite a while to generate the same coverage as doing this would.
cc: @alexcrichton

I think this is a great idea personally since the SIMD implementations have been the source of some of the more subtle bugs. One possible way to implement this is what we've done with the differential target where a Unstructured::ratio can be used to more-or-less bias one way or another. This way some of the input could be used to determine the SIMD-only mode flag if an env var isn't otherwise set. That way I think we'd still get good coverage while not needing a whole new fuzzer ideally

repo: bytecodealliance/wasmtime


text:
Wasi Tutorial Error: Invalid digit found in string

When following the tutorial here:
https://github.com/bytecodealliance/wasmtime/blob/master/docs/WASI-tutorial.md
An error is seen when attempting to run the demo.wasm example (created from demo.c) with filenames that are strings. Specifically the command:
target/debug/wasmtime --dir=. ~/wasmtime-wasi-tutorial/demo.wasm a.txt b.txt
warning: using --invoke with a function that takes arguments is experimental and may break in the future
Error: failed to run main module /home/jlbirch/wasmtime-wasi-tutorial/demo.wasm
Caused by:
invalid digit found in string
A backtrace is indicating that the error is thrown from wasmtime_cli::commands::run::RunCommand::invoke_export
where it seems there is an attempt to match against a LongLong argument type instead of a string.

I encounter the exactly same bug with the rust version code, with wasmtime 4.0.0 on windows 11:

use the rust code from the tutorial
make the function process to be pub, and #[no_mangle]
compile the project with cargo wasi build
echo hello world > test.txt
run the command and its return error:

> wasmtime --dir=. target\wasm32-wasi\debug\demo.wasm --invoke process test.txt somewhere.txt
warning: using `--invoke` with a function that takes arguments is experimental and may break in the future
Error: failed to run main module `target\wasm32-wasi\debug\demo.wasm`

Caused by:
    invalid digit found in string

and I checked out that what #858 has fixed is another bug, and its added a test for a digit param when invoking, but not for a string param, which is the bug I'm encountering now.

I find out another problem with the same bug on stackoverflow, just linking :-}


text:
Re-enable fuzzing in test-all.sh.

Also remove testing for wasmtime-wasi-c testing, which is no longer in
the tree.
Fixes #1257.
cc @tschneidereit

I don't think we actually use this script on CI, so should we remove the script? If not should we switch CI to running this script?

It's not great to run a test-all.sh script in CI, because it means the CI has to treat it like one big command with a big log output that you have to wade through.
Is there a recommend way to do the opposite -- run the CI scripts locally?

It's true yeah that it's not a great setup for CI, but if we don't actually run scripts like this on CI they inevitably break and fall out of date. In that sense if we want to keep it up to date I think we should run it on CI, otherwise I think we'll probably want to remove it since "test all" is "run ci" rather than running this script.

This is no longer relevant.

authors: alexcrichton sunfishcode


text:
x64 backend: fix a load-op merging bug with integer min/max.

The recent work in #4061 introduced a notion of "unique uses" for CLIF
values that both simplified the load-op merging rules and allowed
loads to merge in some more places.
Unfortunately there's one factor that PR didn't account for: a unique
use at the CLIF level could become a multiple-use at the VCode level,
when a lowering uses a value multiple times!
Making this less error-prone in general is hard, because we don't know
the lowering in VCode until it's emitted, so we can't ahead-of-time
know that a value will be used multiple times and prevent its
merging. But we can know in the lowerings themselves when we're
doing this. At least we get a panic from regalloc when we get this
wrong; no bad code (uninitialized register being read) should ever
come from a backend bug like this.
This is still a bit less than ideal, but for now the fix is: in
cmp_and_choose in the x64 backend (which compares values, then
picks one or the other with a cmove), explicitly put values in
registers.
Fixes #4067 (thanks @Mrmaxmeier for the report!).

One longer-term thought that occurs to me is that something like linear/affine types ("use-once values") would let us encode in the types in ISLE that a memory operand is only to be used once. That seems like the minimum language feature to actually provide full safety here. It has a lot of implications we'd have to think through though, so not a step to take lightly. Happy to talk about this more in another issue if desired.


text:
Add C# feature

This PR adds the C# feature the codegen (not complete).  With this it is possible to run
cargo run c-sharp  --string-encoding utf8 --out-dir testing-csharp tests/codegen/floats.wit

Only one feature is needed here, csharp, because there is no compilation, just c# code gen.
Runtime tests are not enabled yet.

Hi, requested a review on this one as it touches non -c# files.   Thanks

Thanks, I'll go ahead as its a blocker for other contributors.

repo: bytecodealliance/wit-bindgen


text:
Can I use ByteTransformer to train TransFormer models  on GPUs ?

Can I use ByteTransformer to train TransFormer models  on GPUs , currently  supports which models ?

No. Right now ByteTransformer only open-sources a forward pass for BERT.

repo: bytedance/ByteTransformer