text:
Performance Issue introduced in v0.30.1

🍐 @keeganstreet
Overview
When updating Sharp to the latest version from v0.29.3, we noticed a marked increase in transaction time when processing images. We have investigated and narrowed it down to it being introduced in v0.30.1. We ran some isolated tests where we processed 1000 images and recorded the duration it took. See here for the repo used.
Sharp 0.29.3 : 13,328 ms
Sharp 0.30.1 : 21,489 ms
Do you have any idea what could have caused this?

Thank you for the clear question and steps to reproduce.
The changelog for v0.30.1 includes https://github.com/lovell/sharp/issues/3066, which is relevant here.
There was a potential quality issue for JPEG input in versions < 0.31.1 where over reliance on shrink-on-load could result in unwanted pixel shifts and moire patterns when resizing. Version 0.31.0 tried to improve this as part of the work to support multi-page (animated) resizing, but this made things worse for the specific case where one dimension was exactly halved. We agreed for version 0.31.1 that the simplest solution was to use (almost) the same approach that libvips uses for its thumbnail operation, which improves quality at a performance cost.
Things you can do now to improve performance:

The forthcoming version 0.32.0 will switch to using sequential read by default, which is faster when resizing without rotation, and you can enable this in current versions via sharp(input, { sequentialRead: true })...
If you're running Linux then please ensure a suitable memory allocator is used (anything but the stock glibc allocator).
Does this question relate to code running at REA? Are you using still using AWS Graviton 2 CPUs? If so, see https://mastodon.social/@lovell/109546531190912845 for why upgrading to Graviton 3 is a very good idea.

Thanks for the explanation and suggestions @lovell ! We tried out the steps you outlined and have achieved some improvements by using sequentialRead. We are working on code running at REA (how did you know? 😆) and are still on a 3rd gen Intel Xeon instance because we found that Graviton 2 was not performing as well as the Intel. Graviton 3 is still not available in the aws regions our system runs on, but definitely something that we could look into in the future when it becomes available. Thanks again for your assistance! :)

Once we've upgraded to 0.31 and implemented some of these changes, we'll benchmark sharp/libvips on c6i vs Graviton 2 cores again.
I haven't been following libvips closely for a while, but I presume there have been some significant performance improvements on arm64 over the last little while.
Hopefully the 7g instances types will become available in more regions soon, though, as that would be a huge win.

Thanks for the updates, good to hear sequentialRead helped. Upgrading should reduce the likelihood of moire patterns appearing when resizing photos of things like tiled roofs and patterned wallpaper.
In terms of ARM64 improvements, liborc recently added support for aarch64 so the prebuilt binaries provided by sharp will now use NEON intrinsics for resizing. Performance results are now published for ARM64 as part of the docs at https://sharp.pixelplumbing.com/performance
I'll close, but please feel free to re-open with more details if further assistance is required.

authors: grantbeattie jian-ong lovell

repo: lovell/sharp


text:
[chip-test] chip_sw_otp_ctrl_lc_signals

Test point name
chip_sw_otp_ctrl_lc_signals
Host side component
Unknown
OpenTitanTool infrastructure implemented
No response
Contact person
@msfschaffner
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.

[x] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
[x] Device-side (C) component developed
[x] Bazel build rules developed
[x] Host-side component developed
[x] HJSON test plan updated with test name (so it shows up in the dashboard)
[x] Test added to dvsim nightly regression (and passing at time of checking)

This is related to #14169.

Note: there already exist tests for lc_dft_en_i and lc_check_byp_en_i, but we still need to develop a test for the access control signals lc_creator_seed_sw_rw_en_i and lc_seed_hw_rd_en_i.

This has been added to the regressions and is passing now.

source: gharchive/issue

repo: lowRISC/opentitan

license_type: permissive

license_source: github-api


text:
[reggen/doc] Fix broken multireg links

If multiregs are broken up into multiple registers, the naming changes from FOO to FOO_0, FOO_1 etc which can lead to broken links in the documentation and Hjson if the IP is templated and the number of registers top-level dependent (e.g. alert_handler, PLIC).
There are a couple of ways to fix this:

We can enforce that even degenerate multiregs have the _0 suffix.
This may be a bit ugly, but it would make the naming consistent and fix the linking issue.

We can fix the documentation generation logic to recognize these cases.
This is a bit more difficult to do.
I have attempted to implement something like this in #9236 for the IP Hjson link rendering function (it infers this multireg situation by looking at the name and checking whether FOO_0 and FOO_1 exist if FOO cannot be found).
However, the HUGO shortcode replacement logic does not have this context (it basically can only do an isolated string operation on the name provided in the shortcode).

So it looks like the first option might be the more convenient (and less brittle way forward).
What do you think?
Btwy, we've had related discussions about this format in the past, see e.g. #3006.

For more confusion about this topic, see #5216.
Could we do (2) "the other way", by adding an anchor for FOO in the same place as FOO_0? That's probably easier for the shortcodes and the resulting text might look nicer: a multi-reg that breaks into FOO_0, FOO_1, FOO_2 (say) could still be referred to as "FOO" in the documentation.

@msfschaffner with "degenerate multireg" you mean a multireg with a count just 1? If yes, it sounds perfectly fine to me to just append the _0 suffix also there.
Also @rswarbrick 's version of option (2) sounds good to me.

This has now been addressed.

authors: msfschaffner rswarbrick vogelpi


text:
[syn/otbn/aes] Add block-level OTBN synthesis and fix AES synthesis

This fixes the AES block-level synthesis environment and adds a block-level synthesis environment for OTBN.
Signed-off-by: Michael Schaffner msf@google.com

Indeed, there is nothing special to these constraints at the moment.

source: gharchive/pull-request


text:
[sw] Deny K&R Declarations in C

C functions that take no arguments have to specify void between the
parentheses in the function declaration. If this is omitted, then the
compiler assumes it is a K&R style declaration, which are not type safe.

Noticed when touching some other code. I thought we denied K&R declarations in our style guide, but apparently not. This is an improvement nonetheless.

This seems like a positive change to me (and as @mcy says, good catch!) - are you planning to propose a patch to the style guide in a separate PR? Personally I think it might be worth adding that change to this PR too.

@asb I'll add something to the style guide, this felt like a good step to see the impact first, but I'll amend this change with a style guide update too.

authors: asb lenary


text:
[top, ast] Generate open source ast registers in topgen

generate open source ast registers as part of topgen
remove the need for xbar_peri to hardcode ast address
introduce different module attributes to distinguish
between normal modules, templated modules, and top specific
modules like sensor_ctrl and ast

My names for module attributes are...horrendous... if anyone has suggestions for better names.. do let me know.

LGTM, thanks

authors: msfschaffner tjaychen


text:
[otbn] Rewrite case in bignum ALU to make all branches reachable

operation_i.sel_flag has type flag_e, which has 4 possible values (the
four different flags: C, M, L and Z). The default case is only
reachable in simulation if the operation_i.sel_flag is 'x, which
doesn't happen and gives a coverage hole.
In other situations, there might be non-X situations where the case
statement might have picked the default. For example, the enum might
have had 5 items, so there would be 3 invalid bit patterns. In this
case, we'd have to be careful about changing the behaviour of the
default case. That doesn't apply here.
Also, reorder the case items to match the ordering of the
enum (originally, there was disagreement in the code about whether M
or L came first: apparently, this file supported the losing side!)

Though uncertain if a blank default will still be seen as an unreachable branch.

It will. We could waive it but, in that case, I suggest just keeping your original code. It seems a pity, though: we've got a case statement that switches on a 2 bit value with 4 possible results. Waiving a spurious 5th case seems a bit silly! :-)

I'd prefer to leave the FlagZ: selection_flag_o = selected_flags.Z line in (so there's a nice uniform enum value to mux output rather than relying on seeing default must mean FlagZ).

How about a comment in the default case, explaining that sel_flag must be FlagZ?


text:
Add  defintion of table value functions

Is your feature request related to a problem? Please describe.
Unfortunately, the definitions of table value functions are currently missing
Describe the solution you'd like
inlcude table value functions (both inline and multi-statement)
Describe alternatives you've considered
none

Hey @ozz-project, thanks for the issue! I don't have a ton of time to do feature work on this right now, but if you want to open a PR I am happy to work through it with you!

I have unfortunately fixed it in a local repro. So I can't send it as a PR. Therefore as a screenshot. There are only a few characters in the sp_doc.sql

authors: lowlydba ozz-project

repo: lowlydba/dba-multitool

license: MIT


text:
Publish to npmjs.org

Tried to rely on this package by using npm install --save-dev git+https://github.com/lpelypenko/axe-html-reporter but this doesn't really work all that well.

Thank you very much for your interest in this package.
I am preparing to publish it in a couple days.

Update:
library was published
Please use TestCafe + axe-core + this html library example.
Please let me know if you have any issue with the demo repository https://github.com/lpelypenko/axe-testcafe-demo and do you still have type problem.

authors: lpelypenko rkettelerij

repo: lpelypenko/axe-html-reporter


text:
Cannot install Error: sodium@2.0.3

I was trying to get this plugin installed on my home bridge docker, but I am hitting some issues with installing sodium. I am using the oznu home bridge docker and this is my startup.sh
apk add libtool
apk add autoconf
apk add automake
apk add libsodium
apk add g++
npm rebuild

verbose stack Error: sodium@2.0.3 install: `node install.js --install`
verbose stack Exit status 1
verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
verbose stack     at EventEmitter.emit (events.js:182:13)
verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
verbose stack     at ChildProcess.emit (events.js:182:13)
verbose stack     at maybeClose (internal/child_process.js:962:16)
verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:251:5)
verbose pkgid sodium@2.0.3
verbose cwd /homebridge
verbose Linux 4.18.17-unRAID
verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "-g" "homebridge-apple-tv" "--unsafe-perm"
verbose node v10.13.0
verbose npm  v6.4.1
error code ELIFECYCLE
error errno 1
error sodium@2.0.3 install: `node install.js --install`
error Exit status 1
error Failed at the sodium@2.0.3 install script.
error This is probably not a problem with npm. There is likely additional logging output above.
6656 verbose exit [ 1, true ]

I ran into the same problem on Ubuntu 18.0.3. The 2.0.3 dependency come from a dependency of this project which is node-apple-tv. I have not figured out a workaround.

I have the same problem on my Banana PI M2 Berry with Raspbian Strech. So far, haven't found a solution.
`/usr/local/lib/node_modules/homebridge-apple-tv/node_modules/sodium/install.js:287
throw new Error(cmdLine + ' exited with code ' + code);
^
Error: make nodesodium exited with code null
at ChildProcess. (/usr/local/lib/node_modules/homebridge-apple-tv/node_modules/sodium/install.js:287:19)
at ChildProcess.emit (events.js:182:13)
at Process.ChildProcess._handle.onexit (internal/child_process.js:254:12)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sodium@2.0.3 install: node install.js --install
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sodium@2.0.3 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!  /root/.npm/_logs/2018-11-26T20_19_37_007Z-debug.log`

same problem here

Maybe @lprhodes can give some advice on this one.
I know the issue lies with trying to install node-apple-tv plugin to Homebridge, so maybe I can create an issue there as well. I was trying to troubleshoot this past weekend, but just kept seeing the same error with multiple "fix attempts"

Based on the logs, I'm guessing something is going on with the directories it is looking for in node_modules
8623 warn rollback Rolling back sodium@2.0.3 failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/homebridge/node_modules/node-appletv/node_modules/sodium'
8624 warn rollback Rolling back homebridge-apple-tv@1.0.2 failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/homebridge/node_modules/homebridge-apple-tv/node_modules/homebridge-platform-helper'
8625 warn rollback Rolling back node-appletv@1.0.10 failed (this is probably harmless): ENOTEMPTY: directory not empty, rmdir '/homebridge/node_modules/node-appletv/node_modules/sodium'

Is the developer still active? Or did anyone else achieve any progress?

Same issue here.

Same for me, can't install

try pponce/homebridge-apple-tv

try pponce/homebridge-apple-tv

Tried to install from this package, got the same problem with for bot global and local types of installation:
Static libsodium was not found at /root/.npm/_cacache/tmp/git-clone-77f03c40/node_modules/sodium/deps/build/lib/libsodium so compiling libsodium from source.

Same here on a Synology NAS (node.js v10.13)...

My change in pponce/homebridge-apple-tv
was to make homebridge-apple-tv depend on a fork of node-appletv (https://github.com/socalrds/node-appletv).
That forked version of node-appletv updates its dependency to sodium 3.0.1 which in theory solves the build issue with sodium version 2.0.3.
I'm running on an rpi 3 with LTS 10.14.2 version of node js.
After you received this error:
Static libsodium was not found at /root/.npm/_cacache/tmp/git-clone-77f03c40/node_modules/sodium/deps/build/lib/libsodium so compiling libsodium from source.
Was it able to compile libsodium from source?
Can you try
apt-get install autoconf automake g++ libtool
prior to installing pponce/homebridge-apple-tv

try pponce/homebridge-apple-tv

Sorry, I'm new, how do i specifically install from pponce/? All the homebridge plugins I've installed so far I use npm install -f <plugin-name>, so how do I install this one? Thanks.

Didn't find the way how to fix it for docker container, but by installing 'sudo apt-get install libtool' and 'sudo apt-get install autoconf' successfully installed the plugin w/o docker :) solution was found here

npm install -g git+https://git@github.com/pponce/homebridge-apple-tv.git

I deleted the accessories folder and tried again and now it works, hallelujah! :) Thanks for your help and Merry Christmas!

Glad you figured that last one out.  I was stumped..
Merry Christmas!

@dornadeluxe
Hi there,
I had the same issue with "./accessories" module.
As you did, I deleted the accessories folder.
That didn't help.
Here's what I did:
I checked the original repo, folder "accessories". I manually created all 4 .js files on the same folder on my raspberry and copied the code from original repo. It worked for me. Now works perfectly.

npm install -g git+https://git@github.com/pponce/homebridge-apple-tv.git
but i think this should work as well
npm install -g pponce/homebridge-apple-tv

Thanks for that. I tried to install, but I get this error:
root@kali:~/.pm2/logs# npm install -g git+https://git@github.com/pponce/homebridge-apple-tv.git

sodium@3.0.2 preinstall /usr/local/lib/node_modules/homebridge-apple-tv/node_modules/sodium
node install.js --preinstall

Static libsodium was not found at /usr/local/lib/node_modules/homebridge-apple-tv/node_modules/sodium/deps/build/lib/libsodium so compiling libsodium from source.
libtoolize:   error: Failed to create 'build-aux'
make: *** [Makefile:62: libsodium] Error 1
/usr/local/lib/node_modules/homebridge-apple-tv/node_modules/sodium/install.js:293
throw new Error(cmdLine + ' exited with code ' + code);
^
Error: make libsodium exited with code 2
at ChildProcess. (/usr/local/lib/node_modules/homebridge-apple-tv/node_modules/sodium/install.js:293:19)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sodium@3.0.2 preinstall: node install.js --preinstall
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sodium@3.0.2 preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-12-26T20_36_06_544Z-debug.log
root@kali:~/.pm2/logs#
Any idea how to fix this? Thanks.

Sorry I've not encountered your issue.
Do you have auticonf automake g++ and libtool installe?
Run:
sudo apt-get install autoconf automake g++ libtool
then try and install again.

Sorry I've not encountered your issue.
Do you have auticonf automake g++ and libtool installe?
Run:
sudo apt-get install autoconf automake g++ libtool
then try and install again.

Yes I already did sudo apt-get install autoconf automake g++ libtool before install and that's what I get... To be very sure, i just ran that command again, followed by the npm install command again, and i get the same error.. as below. Help?
root@kali:~/.pm2/logs# sudo apt-get install autoconf automake g++ libtool
Reading package lists... Done
Building dependency tree
Reading state information... Done
autoconf is already the newest version (2.69-11).
automake is already the newest version (1:1.16.1-4).
g++ is already the newest version (4:8.2.0-2).
libtool is already the newest version (2.4.6-6).
0 upgraded, 0 newly installed, 0 to remove and 243 not upgraded.
root@kali:~/.pm2/logs# npm install -g git+https://git@github.com/pponce/homebridge-apple-tv.git

sodium@3.0.2 preinstall /usr/local/lib/node_modules/homebridge-apple-tv/node_modules/sodium
node install.js --preinstall

Static libsodium was not found at /usr/local/lib/node_modules/homebridge-apple-tv/node_modules/sodium/deps/build/lib/libsodium so compiling libsodium from source.
libtoolize:   error: Failed to create 'build-aux'
make: *** [Makefile:62: libsodium] Error 1
/usr/local/lib/node_modules/homebridge-apple-tv/node_modules/sodium/install.js:293
throw new Error(cmdLine + ' exited with code ' + code);
^
Error: make libsodium exited with code 2
at ChildProcess. (/usr/local/lib/node_modules/homebridge-apple-tv/node_modules/sodium/install.js:293:19)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! sodium@3.0.2 preinstall: node install.js --preinstall
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the sodium@3.0.2 preinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-12-27T02_48_09_871Z-debug.log
root@kali:~/.pm2/logs#
Any ideas please? Thanks.

I am having similar issues with sodium as well -- can anyone assist me?
Currently running node: 11.6.0, raspberry 3
Installed plugin successfully using: sudo npm install -g homebridge-apple-tv --unsafe-perm
When I attempt to run homebridge, I receive the following error. Also, I am attempting to run this plugin with the Nest plugin (which is active and working).
[1/4/2019, 8:32:37 AM] ==================== [1/4/2019, 8:32:37 AM] ERROR LOADING PLUGIN homebridge-apple-tv: [1/4/2019, 8:32:37 AM] Error: Cannot find module '../build/Release/sodium'     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:603:15)     at Function.Module._load (internal/modules/cjs/loader.js:529:25)     at Module.require (internal/modules/cjs/loader.js:657:17)     at require (internal/modules/cjs/helpers.js:22:18)     at Object.<anonymous> (/usr/local/lib/node_modules/homebridge-apple-tv/node_modules/sodium/lib/sodium.js:16:15)     at Module._compile (internal/modules/cjs/loader.js:721:30)     at Object.Module._extensions..js (internal/modules/cjs/loader.js:732:10)     at Module.load (internal/modules/cjs/loader.js:620:32)     at tryModuleLoad (internal/modules/cjs/loader.js:560:12)     at Function.Module._load (internal/modules/cjs/loader.js:552:3) [1/4/2019, 8:32:37 AM] ====================
Any ideas on how to resolve this? I tried updating and following the intructions above, but no luck. Thanks!

@nibty how did you do it. I read article but its for MacOs. im running on Rasbian Stretch Last build.

For anyone who doesn't want to wait for @lprhodes to update his repo, you can install a clone with the fixes using GioCirque's fixed version with the following command:
npm install -g -save git+https://github.com/GioCirque/homebridge-apple-tv.git
NOTE: if @lprhodes ends up updating his repo and homebridge plugin, and if @GioCirque doesn't continue to maintain his package, you won't see any upgrades and miss out on new features should there be any.

@mkormendy @GioCirque thanks. Lets try this one then. :) Its Better then nothing!
In meanwhile of writing this post. I see for very long time this line:
fetchMetadata: sill resolveWhiteNewModule homebridge-apple-tv@1.0.2 checking installable status
then nothing happen...

here the
/root/.npm/_logs/2019-02-28T19_59_49_989Z-debug.log
2019-02-28T19_59_49_989Z-debug.log

I don't have a raspberrypi to try this on. I'd suggest using the --unsafe-perm argument, and be sure the there are two dashes in the --save argument.
npm install -g --save --unsafe-perm git+https://github.com/GioCirque/homebridge-apple-tv.git

I got this repo to install last night after initially having this issue with sodium.
I manually installed automake and sodium and apt-get libtool then retried this install via homebridge-config-ui-x. I believe that's what fixed it, since it will see the latest install of sodium already on device and skip over it.

Yeah, just install libsodium before installing the plugin

Wow, @GioCirque after almost an hour on my PI it finally worked, tks

What worked for me
So, after a long (long) night with the infamous error "Failed at the sodium@2.0.3 preinstall script" - I was finally able to get this plugin up and running (works very nice)
I don't know exactly what I did that made the trick, I must be honest.  But in order to (maybe) help others that come here, I decided to go back to the logs, extract (most of) my "sudo" commands, and list them here.  Listed in brackets are outputs worth mentioning:
pi@raspberrypi:~ $ sudo npm i -g npm
pi@raspberrypi:~/.homebridge $ sudo apt-get update
pi@raspberrypi:~/.homebridge $ sudo apt-get clean
pi@raspberrypi:~/.homebridge $ sudo apt-get autoremove
pi@raspberrypi:~/.homebridge $ sudo apt-get --reinstall install autoconf automake g++ libtool
pi@raspberrypi:~/.homebridge $ sudo apt-get --purge remove autoconf automake g++ libtool
pi@raspberrypi:~/.homebridge $ sudo apt-get install autoconf automake g++ libtool
pi@raspberrypi:~/.homebridge $ sudo npm install -g libsodium
pi@raspberrypi:~/.homebridge $ sudo apt-get update -y && sudo apt-get upgrade -y && sudo npm i -g npm
pi@raspberrypi:~/.homebridge $ sudo npm install -g homebridge-apple-tv --unsafe-perm
pi@raspberrypi:~/.homebridge $ sudo apt-get update
pi@raspberrypi:~/.homebridge $ sudo apt-get dist-upgrade
pi@raspberrypi:~/.homebridge $ sudo npm rebuild
(libsodium@0.7.4 /home/pi/.homebridge/node_modules/libsodium)
pi@raspberrypi:~/.homebridge $ sudo npm install -g homebridge-apple-tv --unsafe-perm
(+ homebridge-apple-tv@1.0.2)
(updated 1 package in 102.573s)
pi@raspberrypi:~/.homebridge $ pm2 restart  homebridge
pi@raspberrypi:~/.homebridge $ sudo npm install -g homebridge-apple-tv --unsafe-perm
(+ homebridge-apple-tv@1.0.2)
(added 259 packages from 215 contributors in 3334.2s)

Afer installation, worth mentioning, I didn't see any switch to pair my AppleTV in the home app...
I needed to do the following sequence:
pi@raspberrypi:/ $ cd /usr/local/lib/node_modules/homebridge-apple-tv
(** worth mentioning: this is the location in my case where the plugin was installed... pi zero)
pi@raspberrypi:/usr/local/lib/node_modules/homebridge-apple-tv $ cd node_modules/node-appletv/bin
pi@raspberrypi:/usr/local/lib/node_modules/homebridge-apple-tv/node_modules/node-appletv/bin $ ./appletv pair

Which Apple TV would you like to pair with? Living Room (192.168.1.3:49164)
Living Room
Living Room

(here I used the arrows to choose the SECOND one)

? Enter the 4-digit pin that's currently being displayed on Living Room 6856

Then, I received the credential,  copied it, and added it as part of this block that I added to config.json:
"platform": "AppleTV",
            "name": "Omri's Apple TV",
            "showDefaultSwitches": true,
            "defaultSwitchesIncludeATVName": true,
            "showPairSwitches": false,
            "hideWelcomeMessage": true,
            "devices": [
                {
                    "id": "Omris",
                    "name": "Omris Apple TV",
                    "credentials": "pasted-credentials-here"
                }
            ],
            "accessories": [
                {
                    "deviceID": "Omris",
                    "name": "Rainbow",
                    "command": []
                }

Good luck guys!

Okay. So I had to follow the "standard" process (install automake, libtool and sodium etc. before installing the plugin) and ALSO downgrade to NodeJS V8. Using the NodeJS 8 version (8.16.0) fixed my problem!

@omriavital with which AppleTV generation are you working? Cause everything is working now but ./appletv pair tells me No Apple TVs found on the network. Try again.

@marius-se
Here the same excact problem. Before I did have it workiong here. Then I decided because of some version (node, hue) warnings to try updating homebridge, homebridge-heu. That did not work as planned.
So I devided to start from scratch, new DebianOS, new homebridge-install, the works...
The second time the installation of all went a lot faster because of the previous experiance.
But then: Same error
No Apple TVs found on the network. Try again.
Same network, same AppleTV, same Pi, same Hue Hub....
Apple TV has IP 192.182.1.13, Pi has ip 192.168.1.14.  Both work fine on the netwerk (with cable).
I have done the instlallation and also Apple TV pair via ssh.
Somebody an idea where to search for the solution?

Could the problem be that the plugins and homebridge are on different locations?
The same problem seemed to be with the version updates.
Apple TV Pair is located in this folder:
~/.nvm/versions/node/v10.16.3/lib/node_modules/homebridge-apple-tv/node_modules/node-appletv/bin $ ./appletv pair
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/blog/projects/avahi-compat.html
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/blog/projects/avahi-compat.html
No Apple TVs found on the network. Try again.
But in previous posts I see it schould be located in:
/usr/local/lib/node_modules $ cd homebridge-apple-tv
-bash: cd: homebridge-apple-tv: Bestand of map bestaat niet
But there seems to be no such folder. Is this a node version problem, should I degrade my node version? Hue wants this version...10.6.3

For people still running into this, you must use node version 8. It's the only thing that worked for me.

Is there any other chance to get this plugin running except of downgrading node? I have a lot of other plugins installed and i dont want to run in more issues after a downgrade..
omriavitals workaround didnt worked for me.

Keep getting this error when trying to install it on my Homebridge Docker on Synology install.
`USER: root
DIR: /var/lib/homebridge
CMD: npm install --save homebridge-apple-tv@1.0.2
[##################] - reify:sodium: timing reifyNode:node_modules/homebridge-apple-tv/no

sodium@3.0.2 preinstall
node install.js --preinstall

Static libsodium was not found at /homebridge/node_modules/homebridge-apple-tv/node_modules/sodium/deps/build/lib/libsodium so compiling libsodium from source.
libtool is required, but wasn't found on this system
make: *** [Makefile:62: libsodium] Error 1
/homebridge/node_modules/homebridge-apple-tv/node_modules/sodium/install.js:293
throw new Error(cmdLine + ' exited with code ' + code);
^
Error: make libsodium exited with code 2
at ChildProcess. (/homebridge/node_modules/homebridge-apple-tv/node_modules/sodium/install.js:293:19)
at ChildProcess.emit (node:events:513:28)
at ChildProcess._handle.onexit (node:internal/child_process:291:12)
Node.js v18.12.1
npm ERR! code 1
npm ERR! path /homebridge/node_modules/homebridge-apple-tv/node_modules/sodium
npm ERR! command failed
npm ERR! command sh -c -- node install.js --preinstall
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/homebridge/.npm/_logs/2022-12-24T03_37_39_383Z-debug-0.log
Operation failed. Please review log for details.`
I went ahead and installed Sodium via npm install -g libsodium which installed fine but trying to install homebridge-apple-tv keeps giving me this error. =(
Thanks in advance!

authors: Alcor72 AviatorBimmer GioCirque NorthernMan54 Screenfeed TommyCardello adidoes aveach chimai dornadeluxe goemangrunn justinrhodes marius-se mkormendy normen omriavital poudenes pponce reiterbene ronnieescorpiso rpeterson03 seackone t0xicfume

repo: lprhodes/homebridge-apple-tv


text:
Homebridge does not start anymore

it  was working fine on raspberry pi until 2 days ago.. But now it isnt starting anymore, see log. Any help would be welcome..
root@raspberrypi:~# homebridge start
*** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node>
*** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=node&f=DNSServiceRegister>
[2018-4-26 03:52:19] Loaded plugin: homebridge-broadlink-rm
[2018-4-26 03:52:19] Registering platform 'homebridge-broadlink-rm.BroadlinkRM'
[2018-4-26 03:52:19] ---
[2018-4-26 03:52:19] Loaded plugin: homebridge-homeassistant
[2018-4-26 03:52:19] Registering platform 'homebridge-homeassistant.HomeAssistant'
[2018-4-26 03:52:19] ---
[2018-4-26 03:52:20] Loaded plugin: homebridge-lgtv-2012
[2018-4-26 03:52:20] Registering accessory 'homebridge-lgtv-2012.lgtv-2012'
[2018-4-26 03:52:20] ---
[2018-4-26 03:52:20] Loaded plugin: homebridge-switcheroo
[2018-4-26 03:52:20] Registering accessory 'homebridge-switcheroo.Switcheroo'
[2018-4-26 03:52:20] ---
[2018-4-26 03:52:20] Loaded config.json with 0 accessories and 1 platforms.
[2018-4-26 03:52:20] ---
[2018-4-26 03:52:20] Loading 1 platforms...
[2018-4-26 03:52:20] [Broadlink RM] Initializing BroadlinkRM platform...
/usr/local/lib/node_modules/homebridge-broadlink-rm/node_modules/node-persist/src/local-storage.js:666
            throw Error('[PARSE-ERROR] ' + file + ' does not look like a valid storage file!');
            ^

Error: [PARSE-ERROR] /root/.homebridge/plugin-persist/homebridge-broadlink-rm/dc914ad836a7024bc1d7c33f384fa37a does not look like a valid storage file!
    at LocalStorage.parseFileSync (/usr/local/lib/node_modules/homebridge-broadlink-rm/node_modules/node-persist/src/local-storage.js:666:19)
    at LocalStorage.parseStorageDirSync (/usr/local/lib/node_modules/homebridge-broadlink-rm/node_modules/node-persist/src/local-storage.js:615:26)
    at LocalStorage.initSync (/usr/local/lib/node_modules/homebridge-broadlink-rm/node_modules/node-persist/src/local-storage.js:142:14)
    at Object.nodePersist.initSync (/usr/local/lib/node_modules/homebridge-broadlink-rm/node_modules/node-persist/src/node-persist.js:37:32)
    at Object.init (/usr/local/lib/node_modules/homebridge-broadlink-rm/node_modules/homebridge-platform-helper/helpers/persistentState.js:9:15)
    at BroadlinkRMPlatform.HomebridgePlatform (/usr/local/lib/node_modules/homebridge-broadlink-rm/node_modules/homebridge-platform-helper/platform.js:15:21)
    at BroadlinkRMPlatform (/usr/local/lib/node_modules/homebridge-broadlink-rm/platform.js:31:5)
    at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:304:32)
    at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:85:36)
    at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:569:30)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)
    at Function.Module.runMain (module.js:605:10)
    at startup (bootstrap_node.js:158:16)
    at bootstrap_node.js:575:3

root@raspberrypi:~#

Felipe, como consigo falar com você?

Por aqui mesmo.. Algo específico? Consegui resolver esse issue.. Salvei meu arquivo config e deletei os arquivos temporários.

Boa noite. Como resolver isso definitivamente? O meu homebridge volta e meia para e não inicia mais. Está rodando por systemd. Para voltar a funcionar, eu preciso remover os arquivos com o comando "rm -rf /var/lib/homebridge/plugin-persist/homebridge-broadlink-rm/" que ele volta a funcionar. Mas está um saco ter que toda hora fazer isso.

authors: JefersonSchramm felipesalomao felipetng

repo: lprhodes/homebridge-broadlink-rm


text:
Replace Jenkins with Travis CI for automated repos.yaml check (as per…

… RFC-75).

Pinging @jdswinbank to approve this quick doc fix.

“Quick”. Heh. Sorry @erykoff ; this one passed me by. Text looks fine. I think we want to fix the line breaking and rebase against master before merging — I'll just go ahead and do that.

authors: erykoff jdswinbank


text:
🛑 ZZVoice is down

In 74ebc8c, ZZVoice ($ZZVOICE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ZZVoice is back up in 79e2ef9 after 7 minutes.


text:
🛑 Mirror-爬 is down

In 0bc0f71, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 678 ms

Resolved: Mirror-鱼露 is back up in f1914f2.


text:
🛑 Mirror-爬 is down

In 3f4441b, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 984 ms

Resolved: Mirror-鱼露 is back up in 62bdc04.


text:
🛑 Mirror-木生 is down

In 65ea2be, Mirror-木生 (https://t.lsy223622.com/ncov-xidian-times) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Mirror-爬 is back up in b66d8d7.


text:
🛑 Mirror-爬 is down

In 4c82d4c, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 715 ms

Resolved: Mirror-鱼露 is back up in 066d807.


text:
🛑 Mirror-爬 is down

In 4722a07, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 678 ms

Resolved: Mirror-鱼露 is back up in bf97d87.


text:
🛑 Mirror-爬 is down

In eb4cfc1, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 1243 ms

Resolved: Mirror-鱼露 is back up in 48043d0.


text:
🛑 Mirror-爬 is down

In 1412a34, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 908 ms

Resolved: Mirror-鱼露 is back up in dffb662.


text:
🛑 Mirror-爬 is down

In 08c8cce, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 1324 ms

Resolved: Mirror-鱼露 is back up in 7e3e7c5.


text:
🛑 Mirror-爬 is down

In 7e3982f, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 876 ms

Resolved: Mirror-鱼露 is back up in 82ad247.


text:
🛑 Mirror-爬 is down

In 4a9e1d4, Mirror-爬 (https://ncov.zhouym.tech/) was down:

HTTP code: 404
Response time: 849 ms

Resolved: Mirror-鱼露 is back up in 84b7334.


text:
can not read record

Why cannot php xbase read record of this file?
tes2.zip

it can read column count and column name, can not read while($record = $table->nextRecord()){}
this my code:
<?php
require 'DBFReader/XBase/Table.php';
require 'DBFReader/XBase/Column.php';
require 'DBFReader/XBase/Record.php';
require 'DBFReader/XBase/Memo.php';
require 'DBFReader/XBase/Exception/InvalidColumnException.php';
require 'DBFReader/XBase/Exception/TableException.php';

use XBase\Table;

$file = addslashes($_GET['file']);
/* buka koneksi database kita */
$user_name = "root";
$password = "";
$database = "db_sbh";
$host_name = "localhost";

$koneksi=mysqli_connect($host_name, $user_name, $password, $database);
//$disable_full_group = mysqli_query($koneksi, "SET sql_mode = ''");

$table = new Table("file/$file.dbf");
//$table = new Table("tes2.dbf");
$columns = $table->getColumns();

$jmlkolom = count($columns);
/*
echo "
";
echo "

";
foreach ($columns as $column) {
    echo "".$column->name."	";//ambil nama semua kolom
}
echo "

";
*/

$row = 0;
while($record = $table->nextRecord()){
    //$idprop = $record->prop;//ambil isi kolom id prop

    $val = "";

    for($i=0; $i<$jmlkolom; $i++){
        if($i == $jmlkolom - 1){
            $val .= "'$record[$i]'";
        }else {
            $val .= "'$record[$i]', ";
        }
    }

    $sql = "INSERT INTO $file VALUES ($val)";
    mysqli_query($koneksi, $sql);
    echo "sql= ".$sql;

    $row++;
}
echo $row;

?>

repo: luads/php-xbase


text:
new: Add play rate control feature and example

Implement #76.
Main concern:
Changing android minSdkVersion to 23.

@erickzanardo , couldn't we check in java if sdk 23, and use it if available? So the plugin would work on older versions, and only speed control would need a more up to date phone. Then expose a property on AudioPlayer to tell client dart code whether there is speed control.

Sounds good to me, just need to make sure on readme that limitation

authors: catoldcui erickzanardo yringler

repo: luanpotter/audioplayers


text:
[BUG] YAML-Files not loaded in Blueprint

The EHMTX_easy*.yaml are not loaded as Blueprints. All generate the same error.
Failed to load blueprint: mapping values are not allowed here in "/config/blueprints/automation/ehmtxv2/EHMTX_easy_color_gauge.yaml", line 198, column 74
In Home Assistant, the File Editor states:
"end of the stream or a document separator is expected (198:74)"
YAML files uploaded in /config/blueprints/automation/ehmtxv2/
Home Assistant 2023.7.1
Supervisor 2023.07.1
Operating System 10.3
To Reproduce
Upload YAML-files in folder and restart Home Assistant
Thanks!

Is there anyone that has the same issue?

Sorry, I have no idea what went wrong in the transfer process. I just recreated each YAML and copied the content from here to the blueprint and it now loads and accepts everything. The problem must have occurred with me somewhere between down- and uploading. Sorry for the hassle.

authors: clfberlin lubeda


text:
Incorrect timezone

I flashed my Ulanzi TC001 with ESPHome using the YAML from Blakadder's blog post, which seems to resemble the template in this repo.
However, it appears the time on the clock is UTC while I'm currently in UTC+2 (CEST).
My HA is set to the correct timezone.
How can I fix the time on my Ulanzi?
substitutions:
  devicename: ulanzi-tc001
  matrix_pin: GPIO32
  buzzer_pin: GPIO15
  battery_pin: GPIO34
  ldr_pin: GPIO35
  left_button_pin: GPIO26
  mid_button_pin: GPIO27
  right_button_pin: GPIO14
  scl_pin: GPIO22
  sda_pin: GPIO21

external_components:
  - source:
      type: git
      url: https://github.com/lubeda/EsphoMaTrix
    refresh: 60s
    components: [ ehmtx ]

esphome:
  comment: "Ulanzi TC001"
  name: $devicename
  on_boot:
    then:
      - ds1307.read_time:

esp32:
  board: esp32dev

ota:

wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

web_server:

font:
  # adapt the filename to your local settings
  - file: fonts/Calcium.ttf
    id: ehmtx_font
    size: 16
    glyphs:  |
      !?"%‰()+*=,-_.:°µ²³0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnÖÄÜöäüopqrstuvwxyz€$@<>/

ehmtx:
  id: rgb8x32
  time_component: ehmtx_time
  matrix_component: ehmtx_display
  clock_time: 5           # duration to display the clock after this time the date is display until next "show_screen"
  clock_interval: 60      # show the clock at least each x seconds
  screen_time: 6          # duration to display a screen or a clock/date sequence
  date_format: "%d.%m"    # defaults "%d.%m." (use "%m.%d." for the US)
  time_format: "%H:%M"    # defaults "%H:%M" (use "%I:%M%p" for the US)
  show_dow: false         # draw the day indicator on the bottom of the screen, defaults to true
  show_date: true         # show the date for show_screen - show_clock seconds otherwise only shows the clock for show_screen seconds, defaults to true
  week_start_monday: true # default monday is first day of week, false = sunday
  yoffset: 8              # the text is aligned BASELINE_LEFT, the baseline defaults to 6
  xoffset: 1              # the text is aligned BASELINE_LEFT, the left defaults to 1
  scroll_interval: 80    # the interval in ms to scroll the text (default=80), should be a multiple of the update_interval from the display (default: 16ms)
  frame_interval: 192     # the interval in ms to display the next anim frame (default=192), should be a multiple of the update_interval from the display (default: 16ms)
  font_id: ehmtx_font
  icons:
    - id: ha
      lameid: 7956
    - id: tempc
      lameid: 2422
    - id: plug
      lameid: 403
    - id: humidity
      lameid: 51764
    - id: co2
      lameid: 30662

binary_sensor:
  - platform: status
    name: "$devicename Status"
  - platform: gpio
    pin:
      number: $left_button_pin
      inverted: true
    name: "$devicename left button"
    on_press:
      then:
        - number.decrement: screen_brightness
  - platform: gpio
    pin:
      inverted: true
      number: $mid_button_pin
      mode: INPUT_PULLUP
    name: "$devicename middle button"
    on_press:
      then:
        - switch.toggle: displaycontrol
  - platform: gpio
    pin:
      number: $right_button_pin
      inverted: true
    name: "$devicename right button"
    on_press:
      then:
        - number.increment: screen_brightness
# example to switch to next screen
#        lambda: |-
#          id(rgb8x32)->skip_screen();
logger:
  level: INFO

# Enable Home Assistant API
api:
  encryption:
    key: !secret api_encryption_key
  services:
    - service: alarm
      variables:
        icon_name: string
        text: string
      then:
        lambda: |-
          id(rgb8x32)->add_screen(icon_name,text,7,20,true);
          id(rgb8x32)->force_screen(icon_name);
    - service: brightness
      variables:
        brightness: int
      then:
        lambda: |-
          id(rgb8x32)->set_brightness(brightness);
    - service: icons
      then:
        lambda: |-
          id(rgb8x32)->show_all_icons();
    - service: skip_screen
      then:
        lambda: |-
          id(rgb8x32)->skip_screen();
    - service: tuneplay
      variables:
        tune: string
      then:
        - rtttl.play:
            rtttl: !lambda 'return tune;'

number:
  - platform: template
    name: "$devicename brightness"
    id: screen_brightness
    min_value: 0
    max_value: 255
    update_interval: 1s
    step: 25
    lambda: |-
      return id(rgb8x32)->get_brightness();
    set_action:
      lambda: |-
        id(rgb8x32)->set_brightness(x);

switch:
  - platform: template
    name: "$devicename Display"
    id: displaycontrol
    icon: "mdi:power"
    restore_mode: ALWAYS_ON
    lambda: |-
      return id(rgb8x32)->show_display;
    turn_on_action:
      lambda: |-
        id(rgb8x32)->set_display_on();
    turn_off_action:
      lambda: |-
        id(rgb8x32)->set_display_off();

sensor:
  - platform: sht3xd
    temperature:
      name: "$devicename Temperature"
    humidity:
      name: "$devicename Humidity"
    update_interval: 60s
  - platform: adc
    pin: $battery_pin
    name: "$devicename Battery"
    id: battery_voltage
    update_interval: 10s
    device_class: battery
    accuracy_decimals: 0
    attenuation: auto
    filters:
      - sliding_window_moving_average:
          window_size: 15
          send_every: 15
          send_first_at: 1
      - multiply: 1.6
      - lambda: |-
          return ((x - 3) / 0.69 * 100.00);
    unit_of_measurement: '%'
  - platform: adc
    id: light_sensor
    name: "$devicename Illuminance"
    pin: $ldr_pin
    update_interval: 10s
    attenuation: auto
    unit_of_measurement: lx
    accuracy_decimals: 0
    filters:
      - lambda: |-
          return (x / 10000.0) * 2000000.0 - 15 ;

output:
  - platform: ledc
    pin: $buzzer_pin
    id: rtttl_out

rtttl:
  output: rtttl_out

i2c:
  sda: 21
  scl: 22
  scan: true
  id: bus_a

light:
  - platform: neopixelbus
    id: ehmtx_light
    type: GRB
    variant: WS2812
    pin: $matrix_pin
    num_leds: 256
    color_correct: [30%, 30%, 30%]
    name: "$devicename Light"
    restore_mode: ALWAYS_OFF
    on_turn_on:
      lambda: |-
         id(ehmtx_display)->set_enabled(false);
    on_turn_off:
       lambda: |-
         id(ehmtx_display)->set_enabled(true);

time:
  - platform: homeassistant
    on_time_sync:
      then:
        ds1307.write_time:
  - platform: ds1307
    update_interval: never
    id: ehmtx_time

display:
  - platform: addressable_light
    id: ehmtx_display
    addressable_light_id: ehmtx_light
    width: 32
    height: 8
    pixel_mapper: |-
      if (y % 2 == 0) {
        return (y * 32) + x;
      }
      return (y * 32) + (31 - x);
    rotation: 0°
    update_interval: 16ms
    auto_clear_enabled: true
    lambda: |-
      id(rgb8x32)->tick();
      id(rgb8x32)->draw();

Well if you like my work: donated me a star on github.
The solution is RTFM: https://esphome.io/components/time/index.html
esphome tries to detect your timezone if it doesn't work you have to specify it.

esphome tries to detect your timezone, if that doesn't work you have to specify it manualy.

I haven't encountered issues with that in the past.
But maybe I just got unlucky this time. Will manually set the timezone.

authors: TheGroundZero lubeda

repo: lubeda/EsphoMaTrix


text:
🛑 Národné športové centrum is down

In c0cd3af, Národné športové centrum (https://narodnesportovecentrum.sk/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Národné športové centrum is back up in c1ba4ec.

repo: lubosm/minedusk-uptime


text:
🛑 Školský šport is down

In 52782ce, Školský šport (https://skolskysport.sk/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Školský šport is back up in 9c69675.


text:
Client credentials with user id

Currently, I'm using the client_credentials grant to give access to specific clients but I need to way to associate the client id and client secret to an user of my application (REST API)
I looked for the owner_id on the oauth_sessions which can be get with Authorizer::getResourceOwnerId() but for this grant it's set up to the same client id. I looked for other options to set this up and I have two ideas but I'm not sure if there is a better way to handle this with the package.

Create a table oauth_app_client where I store the relation between the user id and the client id, and everytime I try to get the user id, I'll need to call getResourceOwnerId and then look in the table for this id but I don't think it's a good choice because I'll have to do a lot of calls everytime.

Generate a client id with my user id but hashed which it's insecure because it will be easy to decode

When the user request the access token, add the relation of client and user_id then I'll retrieve the id and get the information, but I think it's not the best way to handle this in another storage.

What it's the best way to do it with the package?
Thanks

This already works out of the box, try setting up the password grant. This grant will work for users.

@vinkla Yes, I know, but for this case, I don't want them to use their username and password to get an access token, I just want them to use their client credentials and with this they will only have access to their account just like PayPal or Twilio does with their APIs, where Ibonly need to add the client id and secret on the request and they already know which user is trying to authenticate.

The client credentials isn't connected to every specific user. The client id and secret is specific for your application. In order to login users you've to use something to check if they are valid users or not.

Yes, I think that's the issue because I don't want them to give me their username and password to authenticate.
But, if I create some sort of association between the client and a user as I mentioned in my first idea, it would be a bad idea? Or if I want to achieve the kind of authentication, what do you recommend to do using this package?

Yes, it would be a bad idea to not follow the spec. You've to authenticate the user somehow. What kind of information do you get from your users?

Just to give you some context, I want to create an API using this grant which can be used inside my clients platform without worrying for username and password, their developers will only have to put the client id and client secret and they would be able to make requests.
Currently, I'm only receiving the client id and secret but I can get the username and password, but again, I don't think it's a good idea because they will have to store somewhere their credentials to send on the request for the access token.

So you will give out client credentials to third-party apps?

Yes, the idea it's have a section in my Web application for authenticated users to create an "app"  which will generate the client id and secret,  that app will have an association with the authenticated user that create that app and every request using those credentials will be limited to that user only, in this way, it's easier for them to integrate the API, besides that, they will be in charge of securing their credentials.

Yeah, then I would suggest adding a user_id to the clients table.

Ok, the last part of the question (I hope I'm not getting out of context), which one would be a better idea?

Add the user id column and for each call of the Authorizer to getResourceOwnerId, create another call to the database to get the user id? Maybe extending the Authorizer to modify that method to get the user id on that call?

Create a custom grant which will put the user id as owner id on the oauth_sessions table?

Thanks

No, the API should work with the grants just as it does otherwise you don't follow the spec.

Ok, that sounds good, then I'll add the user_id in the oauth_clients table, and I'll extend the Authorizer to get the user_id when I call Authorizer::getResourceOwnerId, thanks a lot for your help.

Ok, sounds good, then I'll add the user_id column on the oauth_clients table, and I'll extend the Authorizer to get the user_id when I call Authorizer::getResourceOwnerId, thanks a lot for your help

Authorizer::getResourceOwnerId() method shouldn't fetch the user_id from the oauth_clients table. It should only fetch the owner ID if you use the correct access token. Modifying this is at your own risk. This won't be secure if you can fetch data with the client credentials.

Mmm ok, then it would be better to implement something else to retrieve the user_id from the table after I retrieve the owner_id with the Authorizer::getResourceOwnerId()?

Mmm ok, then it would be better to implement something else to retrieve the user_id from the table after I retrieve the owner_id with the Authorizer::getResourceOwnerId()?

Yes.

Thanks a lot @vinkla for the help, I'll do it.

Anytime!

I had the same problem and didn't manage to find something. Thank you very much @OscarRPR and @vinkla !!

authors: DanielOlarte OscarRPR hakobfromlightin vinkla

license: mit

license_source: bigquery


text:
close the connection when the client sends a TLS version < TLS 1.3

Should fix https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=25494.
In this fuzz case, the client sent a valid ClientHello that offered a TLS version different from TLS 1.3. We need to make sure that the server closes the connection in this case.

Merging this to get confirmation from OSS-Fuzz as quickly as possible.

repo: lucas-clemente/quic-go


text:
Allow use of custom port value in Alt-Svc header.

Fixes https://github.com/lucas-clemente/quic-go/issues/3262

@googlebot I signed it!


text:
🛑 CBVA-APP is down

In bf83dbf, CBVA-APP (https://admin.bomberosasuncion.org/login) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CBVA-APP is back up in a8c293b.

repo: lucasboh/upptime


text:
🛑 LDAP: honey STARTTLS is down

In 2ad3d50, LDAP: honey STARTTLS (ldap1.teapot.ovh) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LDAP: honey STARTTLS is back up in fa4b854 after 25 minutes.


text:
Criando base para arcabouço do sistema

Base do React Native + Sistema de Roteamento

Resolvido com commit https://github.com/luciannojunior/gradccc-app/commit/4c1cd229c024b92816e549b889a821112e6bc1dc

repo: luciannojunior/gradccc-app


text:
Add more music icons and another mic icon

@it-is-not: Hey, I've just noticed that you opened this PR to merge into master, but we've switched to main recently, could you open a new PR so that I can merge that and you still get properly credited?

authors: it-is-not karsa-mistmere

repo: lucide-icons/lucide

license: ISC


text:
changing to squared norm as in ref paper

also, could i become a project contributor? that way i wouldnt habve to make PRs all the time ;)

@hypnopump oh yup, you've been added!

hmm, the equivariance test seems to be failing

Rrurun tests and it worked lol. I think same error we had last week. IDK why, added a print to inspect the output if it happens again.

authors: hypnopump lucidrains

repo: lucidrains/egnn-pytorch


text:
Is this CViViT implementation causal?

Thanks for your work! We are attempting to use your code as a base for implementing an existing paper but we meet a few issues.
One of the key differences of Causal ViViT with its predecessor is the use of causal attention. However, in this implementation we cannot find which part ensures of it, as the attention itself is not causal. We do notice that there is a PEG module with a causal option (by default). We see that there is padding happening but we do not understand the purpose. Can you elaborate what this module does? If it does not ensure causal attention, is there another part that does?
So far we see proof of our trained models not to be causal, we hope to find if we are doing something incorrectly with the code.
Thanks in advance! And thanks again for the code.

Just wanted to inform that we found some serious bugs, related to reshaping. They were causing, along with other issues, the lack of causality that we noticed. For example, the reshape in the PEG module should be a rearrange instead to allow for also transposing when necessary (such transposes happen when batching spatial and then temporal). After fixing those we were able to obtain a causal and hopefully correct CViViT (currently training). As we see this repo might no longer be maintained, if you are interested about more details, let me know.

@NSavov hey, thank you for attempting to train this! i would def welcome a PR for the PEG module, if you have found that it violated causality somewhere
it has been a while, so i can't seem to spot the issue

@NSavov also, i believe another group has already trained cvivit successfully

@lucidrains thanks for the response. We have noticed and used the weights of the mentioned group. However, it shares the same problems.
The problem is this line in the PEG module. We don''t use the reshape feature now and instead we make sure to rearrange ourselves. We also enable the causal attention and with those 2 changes our causality test passes. Once we get our project running and the time allows, we can prepare a pull request. For now just wanted to point this out.
Thanks again for the code, it is very useful to have something as a base.

@NSavov you are welcome, and a PR would be great
could you let me know if this change addresses the underlying issue?

@NSavov come to think of it, could you point me to the passage in the paper where they said they used causal?

Thanks! We will check it out tomorrow. We apply PEG for spatial and temporal, so it might, but I have to confirm. For enabling causal attention, that is what we do as well.
The causal attention requirement is mentioned in the "Encoder architecture" section on page 4:

@NSavov thank you! yes you are correct then, this is a misstep on my part, my bad

@NSavov  i can add back a spatial PEG if you find it effective

think it is resolved

authors: NSavov lucidrains

repo: lucidrains/phenaki-pytorch


text:
add loader-utils as part of dependencies

Maybe I've been banging my head against the wall for too long or missing something obvious.
Yesterday everything worked fine but lately everytime I consume this in a webpack app I see an error that markdown-image-loader cannot resolve loader-utils. This kind of makes sense though and not sure how it worked before: if you have something in devDependencies it will only install if you clone the project and locally run npm i/yarn in the project so when I use this loader and webpack looks in markdown-image-loaders node_modules it doesn't have anything. That or I am going crazy and forgot how npm dependencies work
ps sorry for the multiple PRs in less than 24 hours :]

no worries for the PRs, it feels nice to see some interest in my work :slightly_smiling_face:
I removed the loader-utils dependency from the dev dependencies, since you added it to the production dependencies.
Before I accept the pull request, could you check that it still works, please?

no worries for the PRs, it feels nice to see some interest in my work 🙂
I removed the loader-utils dependency from the dev dependencies, since you added it to the production dependencies.
Before I accept the pull request, could you check that it still works, please?

Oh yes! Good call. I am lazy so just editing through the GitHub UI instead of locally. I verified on my machine that removing from devDependencies and adding to dependencies works and fixes the issue I was encountering!

Before I forget @lucsorel ! Don't forget to publish the latest 3.0.1

hello @Yahkob :slightly_smiling_face:
Thank you for the reminder, I've just published v3.0.1: https://www.npmjs.com/package/markdown-image-loader. I added you in the project's contributors in the process :wink: :pray:

authors: Yahkob lucsorel

repo: lucsorel/markdown-image-loader


text:
How to load the model

Hi @lufficc , i am trying to use 512 vgg model you provided, but after enter this command:
python test.py --config-file configs/vgg_ssd512_voc0712.yaml --ckpt outputs/vgg_ssd512_voc0712.pth
, it just download from amazon

@lufficc , i have download it and put to my outputs folder, is there any option to load from offline mode

Use --ckpt /path/to/file.pth  for local file. The auto-downloading when loading a local file maybe an unsolved issue.

I also want to load local model,what i should do?Can you help me?

I also want to load local model,what i should do?Can you help me?

--ckpt /path/to/local/file.pth

authors: ijalalfrz lufficc zzu0654

repo: lufficc/SSD


text:
Missing .env file in Android Studio

This has been working for some time, but suddenly it has stopped and i'm not sure what's going on.
We have several build variants:
/**
 * Environment configuration
 */
project.ext.envConfigFiles = [
        debug: ".env.dev",
        staging: ".env.production",
        release: ".env.production",
]

apply from: project(':react-native-config').projectDir.getPath() + "/dotenv.gradle"

if we do
react-native run-android
the project builds fine - it fetched the .env.dev file and everything is fine.
However if I start Android Studio - it immediately complains that a .env file is missing. Which is correct - we don't have this file. Since sync is not able to run because of that error, we can't do anything.
If I do add a .env file, then sync runs fine. And after that I see the Build Variants and I can change them. Then I see that the correct dotenv file is being used - either .env.dev or .env.production
I dug around the dotenv.gradle file and I see that when we try to sync our project we end up here
https://github.com/luggit/react-native-config/blob/master/android/dotenv.gradle#L33
but the flavor is empty. So our configuration doesn't match the flavor and we end up with the default .env file
if I add
project.ext.envConfigFiles = [
"":".env.dev",
debug: ".env.dev",
staging: ".env.production",
release: ".env.production",
]
then android studio picks up the .env.dev file as default, but am I supposed to do this? Or is there something else going on? The docs don't mention anything about that.

Also seeing this on gradle v4.7.
The following seems to be ignored:
project.ext.envConfigFiles = [
/* ... */
]

And when I run e.g. react-native run-android --variant=devDebug I see the following error:
Reading env from: .env
**************************
*** Missing .env file ****
**************************

Is this perhaps something to do with the deprecation of --flavor and in favour of --variant?

Hmm so for me it turned out to be misconfiguration of project.ext.envConfigFiles - the keys needed to be a combination of the flavor and buildType but in lowercase e.g.:
project.ext.envConfigFiles = [
        devdebug  : ".env.development",
        devrelease  : ".env.development",
        proddebug: ".env.production",
        prodrelease: ".env.production"
]

// ...

    flavorDimensions "environment"
    productFlavors {
        dev {
            dimension "environment"
        }
        prod {
            dimension "environment"
        }
    }
    buildTypes {
        debug {
           /* ... */
        }
        release {
            /* ... */
        }
    }

ok, but we don't use productFlavors. We have just buildTypes

The problem for me was that the installation was off, there's  PR with manual Android linking instructions, the last bit we had to add was this:
**MainApplication.java**

 import com.lugg.ReactNativeConfig.ReactNativeConfigPackage;

@Override
protected List<ReactPackage> getPackages() {
     return Arrays.asList(
            new MainReactPackage()
         new ReactNativeConfigPackage()
    );
}

Here's the PR for reference: https://github.com/luggit/react-native-config/pull/303/files

I faced this when gradle task run  except for assemble (in my case running sourceSets for debug purpose). This problem is caused by what tasks are run since gradle.getStartParameter().getTaskNames() get current task name in the process. So this would extract string buildValiantSuffix  rather than flavor. This library is fragile now because this config depends on only what tasks called and doesn't support except for flavor completely matched camel case task name and original task name string must be all lowercase because the flag on pattern determined by startsWith.
As I thought it, I want to handle additional two case,  It should be fixed by flavor.endsWith instead of startsWith. This should be worked in the case original task name has camel case even if flavor added task.
In another case, task name isn't added buildValiantSuffix but this task may call dotenv.gradle in the process like sourceSets. So, we need to avoid this, and maybe it is appropriate to enable switch defaultEnvFile even when project.ext.envConfigFiles exists.
So I'll pull request today if new version release coming. If I wrong something, please feel easy to tell me.

you need to add defaultEnvFile property
check here https://stackoverflow.com/questions/49140463/missing-env-files-when-i-use-react-native-config-for-android/60299691#60299691

I needed to add defaultEnvFile too, when running ENVFILE=xxx ./gradlew assembleRelease the env is NOT read correctly. So I had to create an intermediate script that copies my env to a temporary location read by defaultEnvFile. Lame. lame. lame.

I met this error for just have a wrong path to my env file.
Note that the path should be relative to your project folder, not to the build.gradle .
Check the source code for this error: https://github.com/luggit/react-native-config/blob/63e0e0c7c0e980a5e304f6d8dc08f17d5c19527d/android/dotenv.gradle#L44

We define
project.ext.envConfigFiles = [
    debug: ".env.development",
    release: ".env.production",
]

and all is well when running
react-native run-android --no-jetifier

But for some reason this error occurred when running
react-native run-android --no-jetifier --deviceId abcdef

without any other changes.

Should be able to just change the Run Configuration to get it to work.

https://stackoverflow.com/questions/49140463/missing-env-files-when-i-use-react-native-config-for-android/60299691#60299691

Yes, this was my issue as well. We are using a monorepo setup and this script expects env file to be at the same directory as the core app, not at the project level..

Instead of adding the defaultEnvFile which mentioned above, I had this error simply because of using a wrong path to my env file. Note that the path should be relative to your project folder, not to the build.gradle .
Check the source code for this error:
https://github.com/luggit/react-native-config/blob/63e0e0c7c0e980a5e304f6d8dc08f17d5c19527d/android/dotenv.gradle#L44

Yes, this was my issue as well. We are using a monorepo setup and this script expects env file to be at the same directory as the core app, not at the project level..

This configurations worked for me:
//react-native-config
project.ext.envConfigFiles = [
        development: ".env.development",
        staging :".env.staging",
        production:'.env.production'
]
apply from: project(':react-native-config').projectDir.getPath() + "/dotenv.gradle"
//react-native-config

            matchingFallbacks = ['debug', 'release'] //react-native-config

        //react-native-config
    flavorDimensions 'default'
    productFlavors {
        development {
            // dimension 'env'
            applicationIdSuffix ".testemployeeapp"
        }
        staging {
            // dimension 'env'
            applicationIdSuffix ".testemployeeapp"
        }
        production {
            // dimension 'env'
            applicationIdSuffix ".testemployeeapp"
        }
    }
        //react-native-config

Commands to build:
    "aos:DR-apk": "yarn setDevelopment &&  yarn aos:clean  && cd android && ./gradlew assembleDevelopmentRelease",
    "aos:PR-apk": "yarn setProduction &&  yarn aos:clean  && cd android && ./gradlew assembleProductionRelease",
    "aos:DD-apk": "yarn setDevelopment &&  yarn aos:clean  && cd android && ./gradlew assembleDevelopmentDebug",
    "aos:PD-apk": "yarn setProduction &&  yarn aos:clean  && cd android && ./gradlew assembleProductionDebug",
    "open-apk": "open ./android/app/build/outputs/apk/",
    "aos:dev-apk": "yarn aos:DD-apk && yarn open-apk",
    "aos:dev:release-apk": "yarn aos:DR-apk && yarn open-apk",
    "aos:prod-apk": "yarn aos:PD-apk && yarn open-apk",
    "aos:prod:release-apk": "yarn aos:PR-apk && yarn open-apk",

authors: Ajmal0197 SaraChicaD compojoom egadstar iledzka marnusw maulikdhameliya mtford90 nabilfreeman timerg tkow

repo: lugg/react-native-config


text:
Support Maps.

Cannot proxy a Map.
I get,
Uncaught Error: This object can't be observed.

I don't have plans to support Map or Set at this moment, but I invite you to create your own SignalMap/SignalSet library, and use it inside of other deep signals if you want:
import { SignalMap } from "your-signalmap-library";
import { deepSignal } from "deepsignal";

const state = deepSignal({
  someProp: "...",
  someMap: new SignalMap(),
});

authors: aspizu luisherranz

repo: luisherranz/deepsignal


text:
Allow to search for new version also in local cache

I made changes to a dependency and locally created a new conan package without uploading it to a conan remote. Then I tried to used conan-check-updates to batch update all packages that depend on that dependency.  However, AFAICS, conan-check-updates only looks into remotes for newer versions and does not take into account the local cache. Would it be possible to add this as an optional functionality ?

Hi @h4haase, this makes sense and can be easily added I guess.
Internally conan search -r all <package> (conan v1) or conan search <package> (conan v2) is used. What would be the equivalent search command to also search the local caches?

Thanks for considering this. For conan v1 it would be just conan search <package>, not sure what that would be for conan v2.
As I understand the conan v2 documentation the correct command would be conan list <query>, even for searching in remotes (conan search just seems to be an alias for conan list <query> -r=*)
Also I think it is not possible to search remotes and local cache at the same time, so two calls to conan would be needed.

repo: lukasberbuer/conan-check-updates


text:
No deepdark

It really is quite that simple, adding any squisher of any kind results in the deep dark not generating. I know usually it's because of some other issue or whatever but I can't find a root cause. If anyone tests it out and gets the deep dark generating with a squisher active (in series overworld biomes) then I'll send more details?

Hmm. That's interesting -- can you share the squishers you're using? It could be I'm not treating the depth dimension properly and that's leading to this issue. I'll have to poke it!

For sure yeah here's the mid slice for one of my biomes (I'm using multiple squishers for each slice of the world, but even registering the mid slice alone made the deep dakr not generate)
mid_slice.json

also been testing both biomesquisher and terrablender, does biomesquisher just not work with terrablender installed even if you're not using it? (maybe should be seperate issue but I'm not 100% sure on this)

Hmm. It in theory should work though I've not tested much; feel free to open another issue and I can poke the causes. There's nothing in terms of the conceptual stuff that should inherently conflict so if it doesn't work, it's probably fixable

I've had this same problem, and noticed that biomes are being placed vertically where they should not (eg jungle in the sky above an unrelated biome)

Example: no deep dark, snowy plains above forest

Can confirm the Deep Dark does not generate in my dev environment or a pack that I've been playing recently. In my dev environment, this is the only squisher active. I'm on version 0.4.1.

repo: lukebemishprojects/BiomeSquisher


text:
Give Router a base?: string argument

Sometimes when you publish a worker — you could mount it on a sub-path. Rather than the root. Give worktop router the ability to define an optional base (defaulted to /??).
example:
import { Router } from 'worktop';
import * as Cache from 'worktop/cache';
import { send } from 'worktop/response';

const API = new Router('/my-stuff');

API.add('GET', '/', () => send(200, 'hi'));
API.add('GET', '/foo', () => send(200, 'hi Luke'));

export default Cache.reply(API.run);

https://example.com/my-stuff 200 OK (hi as content)
https://example.com/my-stuff/foo 200 OK (hi luke as content)

Closing in favor of #29, which is the more composable and more easily understood (and familiar) way to go about this

authors: lukeed maraisr

repo: lukeed/worktop


text:
Pagination example not working with newer jQuery

Pagination example seems to be not working with Jquery 2.x or even the newest 1.x (1.12) version.
Error in Google Chrome Console:
Uncaught Error: Syntax error, unrecognized expression: a[href=#second]
Tested on the newest Chrome browser.

Temporary solution for this issue is to add the IDs for panels with the same name as data-section-name but in console we'll see some warnings from scrollify.

I've changed some code in main.js file and it's working with new jQuery:
this line: 10. $(".pagination").find("a[href=#" + ref + "]").addClass("active");
new code in this line: 10. $(".pagination").find('a[href="# + ref + "]').addClass("active");
Working whole main.js file for pagination example:
$(function () {
    $.scrollify({
        section: ".panel",
        scrollbars: false,
        before: function (i, panels) {
            var ref = panels[i].attr("data-section-name");
            $(".pagination .active").removeClass("active");
            $(".pagination").find('a[href="# + ref + "]').addClass("active");
        },
        afterRender: function () {
            var pagination = "
";
            $(".panel").each(function () {
                pagination += "
" + $(this).attr("data-section-name").charAt(0).toUpperCase() + $(this).attr("data-section-name").slice(1) + "
";
            });
            pagination += "
";
            $(".home").append(pagination);
        }
    });
    /*

     Tip: The two click events below are the same:

     $(".pagination a").on("click",function() {
     $.scrollify.move($(this).attr("href"));
     });

     */
    $(".pagination a").on("click", $.scrollify.move);

});

Thanks, I'll update the example.

I wasn't actually able to replicate the issue you described but I've updated the example anyway.

I'm not sure if this is a continuation on this issue or if it's a new one. The pagination example here isn't working again. The bullets are shown and the tooltip works as well, but when clicked on the bullet it won't scroll to the specific slide.

The actual problem in the line 10 $(".pagination").find("a[href=#" + ref + "]").addClass("active"); is that after the parameter href are missing the single (or double if is the case) quotes, so the script is looking for some attribute that doesn't exist href=#somevalue , if you add the quotes like this $(".pagination a[href='#" + ref + "']").addClass("active"); works fine. href='#somevalue'

Can someone look at my code and let me know why it isn't working for me?
I copied and pasted the above code but it just breaks my entire site.
https://nelsontest2.webflow.io/#1

authors: bartvollebregt jairoburbano lukehaas nchowred raczekm

repo: lukehaas/Scrollify


text:
Fix uncaught hash detection exception

This fixes the "Syntax error, unrecognized expression" error that might
get thrown when we test for the existence of DOM elements that correspond
to the current window location's hashbang value. This will happen when
the hash value is equal to "#!/", for instance.

@fThues thanks, this looks good.

authors: fThues lukehaas


text:
Fixed URI not being decoded

Hi @lukejacksonn,
I noticed an issue while using the server. The path was not correctly resolved when it contained spaces.
Very handy project!

Sounds sensible to me! Thanks for the PR 🙇

authors: lukejacksonn marc-ed-raffalli

repo: lukejacksonn/http-server-spa


text:
draw.io@13.9.8: hash check failed

Updating 'draw.io' (13.7.9 -> 13.9.8)
Downloading new version
Loading draw.io-13.9.8.exe from cache
Checking hash of draw.io-13.9.8.exe ... ERROR Hash check failed!
App:         extras/draw.io
URL:         https://github.com/jgraph/drawio-desktop/releases/download/v13.9.8/draw.io-13.9.8.exe#/dl.7z
First bytes: 4D 5A 90 00 03 00 00 00
Expected:    bdf01b2a8eb490d1ddd607b9bb8e8a19b7c1fb3ab7496cf09dab66955c90a5124092fab5dba6b450411e4ab7a62ad25251d764e57ac4c2f8aa04a19d1cdf80c3
Actual:      2ed2914b853d4180acf396bfcb1135faf353dc5dade4ac39b1474c86930f0ec3a8ce4c0c0271a2b3169a4b80adcf7609047c0621c8dc6684f9f6a0ca96c2591b
Please try again or create a new issue by using the following link and paste your console output:
https://github.com/lukesampson/scoop-extras/issues/new?title=draw.io%4013.9.8%3A+hash+check+failed

ad1331a0b510f5fb56bdf1448aa0cd52380674ef

repo: lukesampson/scoop-extras

license: Unlicense


text:
Add manifest for Windows Terminal Preview

This was inspired by the manifest of Windows Terminal, windows-terminal.json.
I thoroughly tested it so as to not conflict with the Windows Terminal installation. Both these can now co-exist.
Fixes #4831.

Move this PR into versions bucket

@Ash258 That's precisely why I asked in #4831 whether extras can have the preview version.
No worries, I've opened a PR there now :)


text:
cleanup for global installed apps doesn't work

I tried to cleanup my apps (I have a mix of users\global apps installed)

recently ffmpeg (global installed) got an update so I went through with the cleanup to get rid of the old version with the command sudo scoop cleanup * -g (tried also sudo scoop cleanup ffmpeg -g), but this error occurred:

PS D:\Users\pulse> sudo scoop cleanup * -g
Removing ffmpeg: 20170827-ef0c6d9gci : Cannot find path 'D:\Users\pulse\scoop\apps\ffmpeg\20170827-ef0c6d9' because it does not exist.
At D:\Users\pulse\scoop\apps\scoop\current\libexec\scoop-cleanup.ps1:42 char:9
+         gci $dir | % {
+         ~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (D:\Users\pulse\s...0170827-ef0c6d9:String) [Get-ChildItem], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

Remove-Item : Cannot find path 'D:\Users\pulse\scoop\apps\ffmpeg\20170827-ef0c6d9' because it does not exist.
At D:\Users\pulse\scoop\apps\scoop\current\libexec\scoop-cleanup.ps1:48 char:9
+         Remove-Item $dir -Recurse -Force
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (D:\Users\pulse\s...0170827-ef0c6d9:String) [Remove-Item], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.RemoveItemCommand

Everything is shiny now!
PS D:\Users\pulse>

I think something isn't working properly in scoop-cleanup.ps1 because it's not looking in the right path, it's looking inside the user\scoop folder instead of programdata\scoop where global apps are installed (in this case ffmpeg)

Yep, forgot to pass $global to versiondir() 😁

repo: lukesampson/scoop

license: unlicense


text:
How to obtain risk scores for UKBB WES data?

Hi, I am trying to obtain risk scores for different traits for every individual in the UK Biobank.
The whole exome sequencing data we have looks like this:
   - /s/raw/ukbiobank/WES_200K/ukb23156_c10_b0_v1.vcf.gz
   - /s/raw/ukbiobank/WES_200K/ukb23156_c10_b10_v1.vcf.gz
   - /s/raw/ukbiobank/WES_200K/ukb23156_c10_b11_v1.vcf.gz
   - /s/raw/ukbiobank/WES_200K/ukb23156_c10_b12_v1.vcf.gz
   - /s/raw/ukbiobank/WES_200K/ukb23156_c10_b13_v1.vcf.gz
[...]

Now I would run your tool like this:
./pgs-calc apply --ref PGS000018 --out PGS000018.scores.txt /s/raw/ukbiobank/WES_200K/*.vcf.gz --report-html PGS000018.html

Is this command correct?
In your README, you write that you need one file per chromosome. Will this also work with multiple files per chromosome as I have?
Will there be large differences compared to imputed genotypes?

Hi,

Is this command correct?

Since you are using data from whole exome sequencing you need to set --genotypes GT. Per default pgs-calc uses the dosages (DS) to calculate the score.

In your README, you write that you need one file per chromosome. Will this also work with multiple files per chromosome as I have?

yes, pgs-calc works also with multiple files per chromosome. pgs-calc fails only when multiple chromosomes are present in one file.

Will there be large differences compared to imputed genotypes?

I don't think so. In the html report you see the coverage of each score (i.e. the number of variants found in your data).

Thanks a lot for your answer, this was very helpful!

authors: Hoeze lukfor

repo: lukfor/pgs-calc


text:
Extreme CPU usage

One core is always used 100% by the program. This needs to be fixed.

The reason is that it was running at an unbounded frame rate. Enabling vsync fixes the issue, but also adds a lot of input lag. This brings CPU utilization down from ~150% to ~30% on my laptop. It can and should be close to zero percent when the user is not interacting with the app, but I'm going to wait for Bevy's official GUI before I do anything like that.
Here are a couple of issues in the Bevy repo related to bringing down input lag even with vsync enabled:

[ ] https://github.com/bevyengine/bevy/issues/1343
[ ] https://github.com/bevyengine/bevy/issues/3317

I'm leaving this issue open as the CPU usage could still be regarded as extreme (considering it should be close to zero) to track progress towards solving these issues in Bevy.

repo: lukors/kanter


text:
[sitemap plugin] lastmod is ctime

Version
No response
Platform
No response
What steps will reproduce the bug?
import sitemap from "lume/plugins/sitemap.ts";

site.use(sitemap());

How often does it reproduce? Is there a required condition?
100%
What is the expected behavior?
it should be mtime
What do you see instead?
inside sitemap.xml:
<lastmod>(ctime here)</lastmod>
Additional information
data.date is ctime i think

It makes sense.
date value is used to assign a date to a page, but and this date can mean anything. By default Lume uses the creation date, but technically it could be what do you want (you can assign the date you want in the frontmatter).
I this case, I agree that mtime makes more sense, but this value is not available automatically in the page date. Maybe Lume should have both dates, but I'm not completely sure about that.
As a workaround, you can create a preprocessor to obtain this data:
site.preprocess([".html"], (pages) => {
  for (const page of pages) {
    const info = page.src.entry?.getInfo();
    page.data.lastmod = info?.mtime;
  }
});

wouldn't what your proposed be the default for a sitemap? i assume only search engines use read a sitemap.

lastmod is not a reliable value. Sometimes in some CI environments it's the present time (the moment where the file is created after cloning the repo, instead of when this file content was modified for the last time). Another option is using Git Last Updated value, but this also doesn't work for CI like GitHub Actions, because the repository is cloned without the history (only the last commit).

well that is cursed. you should probably paste this paragraph to https://lume.land/plugins/sitemap/

Fair enough. I've updated the documentation including that.

authors: iacore oscarotero

repo: lumeland/lume


text:
Fix managing the docs Python virtualenv

It seems we've been relying on a Poetry bug (or at least on a buggy behavior)[1].
This made our documentation builds to stop working with Poetry 1.8[2]:
Running Sphinx v7.2.6
making output directory... done

Traceback (most recent call last):
  File "/home/docs/checkouts/readthedocs.org/user_builds/ts-results-es/envs/109/lib/python3.11/site-packages/sphinx/cmd/build.py", line 293, in build_main
    app = Sphinx(args.sourcedir, args.confdir, args.outputdir,
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/ts-results-es/envs/109/lib/python3.11/site-packages/sphinx/application.py", line 272, in __init__
    self._init_builder()
  File "/home/docs/checkouts/readthedocs.org/user_builds/ts-results-es/envs/109/lib/python3.11/site-packages/sphinx/application.py", line 342, in _init_builder
    self.builder.init()
  File "/home/docs/checkouts/readthedocs.org/user_builds/ts-results-es/envs/109/lib/python3.11/site-packages/sphinx/builders/html/__init__.py", line 219, in init
    self.init_templates()
  File "/home/docs/checkouts/readthedocs.org/user_builds/ts-results-es/envs/109/lib/python3.11/site-packages/sphinx/builders/html/__init__.py", line 270, in init_templates
    self.theme = theme_factory.create(themename)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/docs/checkouts/readthedocs.org/user_builds/ts-results-es/envs/109/lib/python3.11/site-packages/sphinx/theming.py", line 230, in create
    raise ThemeError(__('no theme named %r found (missing theme.conf?)') % name)
sphinx.errors.ThemeError: no theme named 'sphinx_rtd_theme' found (missing theme.conf?)

Theme error:
no theme named 'sphinx_rtd_theme' found (missing theme.conf?)

[1] https://github.com/python-poetry/poetry/issues/9025
[2] https://readthedocs.org/projects/ts-results-es/builds/23635323/

The docs build succeeded, just failed to be reported to GH: https://readthedocs.org/projects/ts-results-es/builds/23635928/

repo: lune-climate/ts-results-es


text:
Unclosed client session

#!/bin/env python3

import asyncio
from pyqqmusicapi import QQMusic

async def async_main():
    # 初始化Api，可传入musicid，musickey
    api = QQMusic()

    # 可用api：SongApi，TopApi，SearchApi，MvApi，PlaylistApi，AlbumApi，LoginApi
    result = await api.song.detail("0039MnYb0qxYhV")

    song_name = result['track_info']['info']['name']
    time_public = result['track_info']['info']['timePublic']
    album_name = result['track_info']['album']['name']
    print(f"{song_name}, album {album_name}, public {time_public}")

asyncio.run(async_main())

执行后返回错误
晴天, album 叶惠美, public 2003-07-31
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7fa8c3175950>
Unclosed connector
connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0x7fa8c238c050>, 2580.640299335)]']
connector: <aiohttp.connector.TCPConnector object at 0x7fa8c3134f50>

我看 pyqqmusicapi/qqmusic.py 有定义 def __clean().  是我代码少了 close session 吗？

原本是想要复用aiohttp.seesion，但是相关资料较少，可能出错了

目前没有问题了

authors: liuhangbin luren-dc

repo: luren-dc/PyQQMusicApi


text:
Discord Invite Invalid

Discord link in the Community and Support gives the error of Invite invalid

Hi ! please try with this link https://discord.gg/4hGT3AFPMZ

authors: gespona iamrajee

repo: luxonis/depthai-unity


text:
Python3.9 support

Fixed some minor issues from #261 : added log_system_information.json to gitignore, updated error print if depthai version is not matching
Added support for python 3.9 (thanks to https://github.com/luxonis/depthai-python/pull/65), updated requirements.txt
Fixed point cloud visualizer on windows (except for python 3.9, open3d doesn't have prebuilt wheels for it
Tested on rpi, windows (python 3.7,3.8,3.9), ubuntu 20.04 (python 3.6 .. 3.9), macos (3.8, 3.9).

Testing this with Python3 on Mac now.

Works great!

Trying on Windows (on my Mac, in Parallels) now.  The bash script is quite nice so far @VanDavv .

authors: Luxonis-Brandon szabi-luxonis

repo: luxonis/depthai


text:
Fix Issue 104

概要 / Overview
影響範囲がでかいために放置されていた修正をやりました

chmin / chmax のファイルを分割しました
type-alias を int-alias と size-alias に分割しました
int-alias に i128 と u128 を追加しました
メンバ変数の suffix に _ が入っているファイルがあったので削除しました

手を付けていない変更

rep 構造体の分割
他のサイズの整数の追加

関連 issue, PR / Related issues, PRs

#104

TODO
CI 関連項目

verify-check / verify
(cd $(git rev-parse --show-toplevel) && oj-verify all)

clang-format
(cd $(git rev-parse --show-toplevel) && clang-format -i $(find src/ test/ unit-test/ -name "*.hpp" -or -name "*.cpp"))

verify : https://github.com/luzhiled1333/comp-library/actions/runs/5699991802

すいません、この Approved というのは Approved という意味でしょうか

いいえ、これから確認するという意味です

fix #139

fixしていないんだよね
verifyが落ちてます

これ時間切れか　すみません


text:
Undocumented system: pseudo-url

https://github.com/lviggiano/owner/blob/d56ad12b63657848b0dd4aa1ea1b0dced4d96582/owner/src/main/java/org/aeonbits/owner/loaders/SystemLoader.java#L18
The system:properties and system:env are not documented in the main manual. Indeed, the manual recommends that the API client manually request the ConfigFactory to import the properties (which is much less reliable solution, as it yields the responsibility to the client, which may 'forget' to include the relevant parameter).

True. I need to update the documentation. Help is more than welcome :)

Pull request #247 added.

I'll check this asap, sorry for the delay.

authors: lviggiano ysmartin

repo: lviggiano/owner


text:
Long Delay between onPress and Finished Callback

There is an average of a 2 second delay on Android between pressing "Capture" and the data being returned from the promise. I used another package https://github.com/NorthFoxz/react-native-camera-android and there is an average of a 0.8 second delay for the same scenario (which is much better). Any ideas? I saw a closed issue from a while ago showing that the delay was related to a similar delay and it was associated with rotation of the image. So the current pull request (#232) by @rpopovici may fix the issue...?

I'm having this issue to... My app is dependent on being able to take picture after picture quickly.  My time between capture and onPress is more like 4 seconds.  I had to change my app to select "capture", create an array of the current pictures in the default camera location,  have user go to the regular camera, shoot a bunch of pictures, then go back to my app and re-press the "capture" button, selecting all images NOT in the array for processing.  This works but is cumbersome.  My normal response in the native camera are .4-.75 seconds per press.

+1

+1

+1

+1

Are these all android issues?  If so, I suspect I know what's causing it.
To test the theory, could you try my PR and set the target to anything other than cameraRoll (like Camera.constants.CaptureTarget.temp).
Then, if the delay is noticeably less, switch to CameraRoll and see if the delay comes back.

I have same issue with Nexus 7 Tab (Android 5.1.1)

authors: ArthurvS Ulydev ZekkieB cyphire java99 mnlbox npomfret sscaff1

repo: lwansbrough/react-native-camera


text:
[Android] Battery drain issue

Has anyone come across having a battery issue on their Android devices? When I'm using the camera for an extended period of time (10-30 minutes), my battery drains unexpectedly fast. I'm using the camera to scan barcodes and was wondering if there are any ways of improving camera/battery performance. Thanks!
Environment

Node.js version: 3.10.10
React Native version: 0.40
React Native platform + platform version: Android 5.0 >

react-native-camera
Version: 0.5.1

As mentionned in https://github.com/lwansbrough/react-native-camera/issues/460 , the only way is to turn off camera by not displaying the view.

@sibelius  this issue can it is being closed?

authors: cfournel enieber kevinnguy


text:
Shell linters and github action

Adds and refactors existing shell based linters and adds a github workflow to run static analysis.
Closes #10392

./main.sh: 141: test_static_analysis: not found

./main.sh: 141: test_static_analysis: not found

@tomponline I've removed this from test/main.sh now

@markylaing any ideas why the workflows dont seem to be running on github anymore?

@markylaing any ideas why the workflows dont seem to be running on github anymore?

@tomponline not a clue :unamused:

authors: markylaing tomponline

repo: lxc/lxd


text:
Network: Adds support for external subnets for OVN networks

Adds validation for OVN network's subnet that checks whether it is within the allowed uplink and project networks when disabling NAT.
Allows for instance IPs on OVN networks to be published to the external uplink network (when in no NAT mode).

@stgraber just wanted to check something with this PR, I've validated the OVN NIC's addresses against the OVN network's ipv4.routes.external and ipv6.routes.external setting to check if they should be considered for uplink publishing. This avoids mistakes by accidentally configuring an OVN network with an address in the allowed subnets list (and disabling NAT) and inadvertently creating an external network. However I wanted to check whether you had envisaged instead that in this scenario ipv{n}.routes.external wouldn't need to be set on the OVN network, and instead we would validate the OVN NIC's IPs against both the uplink network's routes and the project's restricted subnets on each instance start.

Ok, so completely doing away with ipv4.routes.external and ipv6.routes.external on OVN network and either using:

ipv4.address/ipv6.address + no-NAT to give external addressing to the network
ipv4.routes.external/ipv6.routes.external on the NIC itself

That should work fine and would remove an intermediary step, but we'll need to be careful with validation, effectively ensuring that the requested route isn't included/overlap/conflict with any of:

Networks ipv4.address/ipv6.address
Any other instance's ipv4.routes.external/ipv6.routes.external in the project

@stgraber yep that will be fine, but just want to check, as the originally design specified that an admin would delegate one or more external subnets for use with on OVN NICs (at least for their external routes).
"it's up to the user in the project to assign that entire allocation or a subset of it to one of their networks by setting the ipv4.routes.external key on the network"
Now, for the scenario this PR deals with (allocating an external subnet directly to an OVN network), this is still implicitly happening by disabling NAT and setting the ipv4.address to an external subnet.
But for the earlier scenario, where OVN NICs themselves have external routes added to them, they will now be able to mix and match between any of the subnets available on the uplink network (filtered by the project restrictions).
This is technically fine, but just want to check that the user level who will be doing this is the same as the one who will create the OVN network. I was wondering where the original feature for assigning subnets to OVN networks came from? Thanks

@stgraber based on our convo, this updates OVN networks to be validated against the uplink routes and project restricted subnets when NAT mode is disabled. It also adds support for publishing the NIC's IPs onto the uplink network when NAT is disabled.
Because the NIC static addresses are already validated that they belong in the OVN network, now that we validate that the OVN network's subnet itself is allowed in both the uplink and project, this should ensure OVN NICs cannot publish IPs they shouldn't.
I'll follow up with a PR to remove the ipv{n}.routes.external keys from OVN networks and NICs next.

Testsuite passed

Testsuite passed

authors: lxc-jenkins stgraber tomponline


text:
Device: Modifies Bridge NIC state to return IP neighbour entries in valid states first

Also excludes those in FAILED state.
Still outputs IPs in non-valid-states even when valid IPs found so as not to flap between displaying IPv4, IPv6 and link-local addresses, but orders valid entries first.

@tomponline
lxd/network/network_utils.go:799:1: comment on exported const NeighbourIPStatePermanent should be of the form "NeighbourIPStatePermanent ..."

@stgraber ah leading space fixed.

authors: stgraber tomponline


text:
cleanup and encode urls

use single quotes constantly in exchange classes
encode urls in exchange.py
update exchange.py to use rapidfuzz see this

We need to change fuzzywuzzy to rapidfuzz in setup.py.

Looks good. There are a couple of responses in course_management.py which are never used after being assigned. You can remove them in this PR if you want.

I noticed them. I will merge this for now.


text:
Add support for custom file extensions in link checking.

This adds support for overwriting extensions:
lychee . --extensions md,html,txt,json,yaml

The above would only check these extensions.
This was enabled by moving to ignore (#1500 by @thomas-zahner).
I'm not 100% convinced about the design yet. Feedback welcome!
Guess we should use whatever ignore::types::Types for file extension matching as it's well-maintained and more exhaustive. Switching this would remove some custom code we have in FileType.
Fixes #410

@mre looks good overall. Does this mean that non Markdown/HTML files are no longer checked when the new argument  isn't specified?

Yeah, good point. I think plaintext is missing to be compatible with what we had before. That's the only missing format, or? Was considering to extend it to other formats like JSON or YAML as well.

authors: mre thomas-zahner

repo: lycheeverse/lychee


text:
Question 35 and BigInt

In the answer to Question 35 ("Which of these values are falsy?"), it says that there are only six values that are falsy:

undefined
null
NaN
0
'' (empty string)
false

However, also the BigInt zero, or 0n is a falsy value.

I agree @tkalmi ,  PR awaiting approval:
https://github.com/lydiahallie/javascript-questions/pull/379

authors: leonlafa tkalmi

repo: lydiahallie/javascript-questions


text:
[reverted] convert github syntax

Converts the query syntax for Github to use the new format.
See #914

accidentally merged without review, but I've since reverted, and reopened in #916

repo: lyft/cartography