text:
fix(security): vulnerabilities found in corda-4-6-all-in-one

List of vulnerabilities found in corda-4-6-all-in-one image during Azure Container scan.

VULNERABILITY ID
PACKAGE NAME
SEVERITY

CVE-2021-36159
apk-tools
CRITICAL

CVE-2021-30139
apk-tools
HIGH

CVE-2022-28391
busybox
CRITICAL

CVE-2021-28831
busybox
HIGH

CVE-2021-42378
busybox
HIGH

CVE-2021-42379
busybox
HIGH

CVE-2021-42380
busybox
HIGH

CVE-2021-42381
busybox
HIGH

CVE-2021-42382
busybox
HIGH

CVE-2021-42383
busybox
HIGH

CVE-2021-42384
busybox
HIGH

CVE-2021-42385
busybox
HIGH

CVE-2021-42386
busybox
HIGH

CVE-2021-36222
krb5-libs
HIGH

CVE-2021-39537
ncurses-libs
HIGH

CVE-2021-39537
ncurses-terminfo-base
HIGH

CVE-2021-28041
openssh-client
HIGH

CVE-2021-41617
openssh-client
HIGH

CVE-2021-28041
openssh-keygen
HIGH

CVE-2021-41617
openssh-keygen
HIGH

CVE-2021-3711
openssl
CRITICAL

CVE-2021-23840
openssl
HIGH

CVE-2021-3450
openssl
HIGH

CVE-2021-3712
openssl
HIGH

CVE-2022-0778
openssl
HIGH

CVE-2022-28391
ssl_client
CRITICAL

CVE-2021-28831
ssl_client
HIGH

CVE-2021-42378
ssl_client
HIGH

CVE-2021-42379
ssl_client
HIGH

CVE-2021-42380
ssl_client
HIGH

CVE-2021-42381
ssl_client
HIGH

CVE-2021-42382
ssl_client
HIGH

CVE-2021-42383
ssl_client
HIGH

CVE-2021-42384
ssl_client
HIGH

CVE-2021-42385
ssl_client
HIGH

CVE-2021-42386
ssl_client
HIGH

CVE-2022-1271
xz
HIGH

CVE-2022-1271
xz-libs
HIGH

CVE-2018-25032
zlib
HIGH

CVE-2018-19360
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2018-19361
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2018-19362
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-14379
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-14540
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-14892
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-14893
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-16335
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-16942
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-16943
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-17267
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-17531
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-20330
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2020-8840
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2020-9546
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2020-9547
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2020-9548
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-12086
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2019-14439
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-10672
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-10673
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-10968
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-10969
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-11111
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-11112
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-11113
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-11619
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-11620
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-14060
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-14061
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-14062
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-14195
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-24616
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-24750
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-25649
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-35490
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-35491
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-35728
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36179
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36180
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36181
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36182
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36183
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36184
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36185
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36186
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36187
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36188
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36189
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36518
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2021-20190
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2019-14379
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-14540
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-14892
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-14893
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-16335
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-16942
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-16943
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-17267
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-17531
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-20330
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2020-8840
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2020-9546
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2020-9547
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2020-9548
com.fasterxml.jackson.core:jackson-databind
CRITICAL

CVE-2019-12086
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2019-14439
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-10672
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-10673
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-10968
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-10969
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-11111
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-11112
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-11113
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-11619
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-11620
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-14060
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-14061
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-14062
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-14195
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-24616
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-24750
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-25649
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-35490
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-35491
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-35728
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36179
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36180
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36181
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36182
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36183
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36184
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36185
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36186
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36187
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36188
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36189
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2020-36518
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2021-20190
com.fasterxml.jackson.core:jackson-databind
HIGH

CVE-2022-25647
com.google.code.gson:gson
HIGH

CVE-2020-7692
com.google.oauth-client:google-oauth-client
CRITICAL

CVE-2021-23463
com.h2database:h2
CRITICAL

CVE-2021-42392
com.h2database:h2
CRITICAL

CVE-2022-23221
com.h2database:h2
CRITICAL

CVE-2021-37136
io.netty:netty-codec
HIGH

CVE-2021-37137
io.netty:netty-codec
HIGH

CVE-2019-17571
log4j:log4j
CRITICAL

CVE-2022-23305
log4j:log4j
CRITICAL

CVE-2022-23302
log4j:log4j
HIGH

CVE-2022-23307
log4j:log4j
HIGH

CVE-2022-23913
org.apache.activemq:artemis-commons
HIGH

CVE-2019-12402
org.apache.commons:commons-compress
HIGH

CVE-2021-35515
org.apache.commons:common-compresss
HIGH

CVE-2021-35516
org.apache.commons:commons-compress
HIGH

CVE-2021-35517
org.apache.commons:commons-compress
HIGH

CVE-2021-36090
org.apache.commons:commons-compress
HIGH

CVE-2021-44228
org.apache.logging.log4j:log4j-core
CRITICAL

CVE-2021-45046
org.apache.logging.log4j:log4j-core
CRITICAL

CVE-2021-45105
org.apache.logging.log4j:log4j-core
HIGH

CVE-2020-11989
org.apache.shiro:shiro-core
CRITICAL

CVE-2020-1957
org.apache.shiro:shiro-core
CRITICAL

CVE-2021-41303
org.apache.shiro:shiro-core
CRITICAL

CVE-2019-12422
org.apache.shiro:shiro-core
HIGH

CVE-2020-13933
org.apache.shiro:shiro-core
HIGH

CVE-2021-30129
org.apache.sshd:sshd-core
HIGH

CVE-2018-8014
org.apache.tomcat.embed:tomcat-embed-core
CRITICAL

CVE-2020-1938
org.apache.tomcat.embed:tomcat-embed-core
CRITICAL

CVE-2018-8034
org.apache.tomcat.embed:tomcat-embed-core
HIGH

CVE-2019-0199
org.apache.tomcat.embed:tomcat-embed-core
HIGH

CVE-2019-0232
org.apache.tomcat.embed:tomcat-embed-core
HIGH

CVE-2019-10072
org.apache.tomcat.embed:tomcat-embed-core
HIGH

CVE-2019-12418
org.apache.tomcat.embed:tomcat-embed-core
HIGH

CVE-2019-17563
org.apache.tomcat.embed:tomcat-embed-core
HIGH

CVE-2020-13934
org.apache.tomcat.embed:tomcat-embed-core
HIGH

CVE-2020-17527
org.apache.tomcat.embed:tomcat-embed-core
HIGH

CVE-2020-9484
org.apache.tomcat.embed:tomcat-embed-core
HIGH

CVE-2021-25122
org.apache.tomcat.embed:tomcat-embed-core
HIGH

CVE-2021-25329
org.apache.tomcat.embed:tomcat-embed-core
HIGH

CVE-2020-13935
org.apache.tomcat.embed:tomcat-embed-websocket
HIGH

CVE-2020-28052
org.bouncycastle:bcprov-jdk15on
HIGH

CVE-2015-3253
org.codehaus.groovy:groovy-all
CRITICAL

CVE-2020-10683
org.dom4j:dom4j
CRITICAL

CVE-2020-27216
org.eclipse.jetty:jetty-http
HIGH

CVE-2021-28165
org.eclipse.jetty:jetty-http
HIGH

CVE-2021-28165
org.eclipse.jetty:jetty-io
HIGH

CVE-2020-27216
org.eclipse.jetty:jetty-server
HIGH

CVE-2021-28165
org.eclipse.jetty:jetty-server
HIGH

CVE-2020-27216
org.eclipse.jetty:jetty-util
HIGH

CVE-2021-28165
org.eclipse.jetty:jetty-util
HIGH

CVE-2020-27216
org.eclipse.jetty:jetty-webapp
HIGH

CVE-2020-25638
org.hibernate:hibernate-core
HIGH

CVE-2016-2141
org.jgroups:jgroups
CRITICAL

CVE-2022-0839
org.liquibase:liquibase-core
CRITICAL

CVE-2022-21724
org.postgresql:postgresql
CRITICAL

CVE-2022-27772
org.springframework.boot:spring-boot
HIGH

CVE-2022-22965
org.springframework.boot:spring-boot-starter-web
CRITICAL

CVE-2022-22965
org.springframework:spring-beans
CRITICAL

CVE-2018-15756
org.springframework:spring-core
HIGH

CVE-2022-22970
org.springframework:spring-core
HIGH

CVE-2022-22965
org.springframework:spring-webmvc
CRITICAL

CVE-2020-5398
org.springframework:spring-webmvc
HIGH

CVE-2017-18640
org.yaml:snakeyaml
HIGH

CVE-2017-18640
org.yaml:snakeyaml
HIGH

CVE-2017-18640
org.yaml:snakeyaml
HIGH

CVE-2017-18640
org.yaml:snakeyaml
HIGH

@petermetz I would love to tackle this issue!

authors: alec-p-hong zondervancalvez

repo: hyperledger/cactus


text:
test: jestify get-node-jws-endpoint-v1 test

Migrated test from Tap to Jest.
File Path:
packages/cactus-plugin-consortium-manual/src/test/
typescript/unit/consortium/get-node-jws-endpoint-v1.test.ts
This is a PARTIAL resolution to issue #238
Signed-off-by: awadhana awadhana0825@gmail.com

@awadhana LGTM, thank you very much!

No problemo!

source: gharchive/pull-request

license_type: permissive

license_source: github-api


text:
Fail to run asset-transfer-private-data sample on Apple ARM

Hi, I try to run this :
https://github.com/hyperledger/fabric-samples/blob/main/asset-transfer-private-data/README.md#running-the-sample
but it's failed :
$ ./network.sh up createChannel -c mychannel -ca
Using docker and docker-compose
Creating channel 'mychannel'.
If network is not up, starting nodes with CLI timeout of '5' tries and CLI delay of '3' seconds and using database 'leveldb with crypto from 'Certificate Authorities'
Bringing up network
Unable to find image 'hyperledger/fabric-tools:latest' locally
docker: Error response from daemon: manifest for hyperledger/fabric-tools:latest not found: manifest unknown: manifest unknown.
See 'docker run --help'.
LOCAL_VERSION=2.4.7
DOCKER_IMAGE_VERSION=
Local fabric binaries and docker images are out of  sync. This may cause problems.
Unable to find image 'hyperledger/fabric-ca:latest' locally
latest: Pulling from hyperledger/fabric-ca
docker: no matching manifest for linux/arm64/v8 in the manifest list entries.
See 'docker run --help'.
CA_LOCAL_VERSION=1.5.5
CA_DOCKER_IMAGE_VERSION=
Local fabric-ca binaries and docker images are out of sync. This may cause problems.
Generating certificates using Fabric CA
[+] Running 0/3
 ⠿ ca_orderer Error                                                                                3.0s
 ⠿ ca_org2 Error                                                                                3.0s
 ⠋ ca_org1 Pulling                                                                                3.0s
no matching manifest for linux/arm64/v8 in the manifest list entries

os:
$ sw_vers
ProductName:		macOS
ProductVersion:		13.1
BuildVersion:		22C65

$ uname -a
Darwin xxx 22.2.0 Darwin Kernel Version 22.2.0: Fri Nov 11 02:03:51 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T6000 arm64

i didn't try this:
build docker image of ca with  --platform=linux/arm64 and run
thanks

On compose-test-net.yaml file change docker image version to hyperledger/fabric-peer:2.5.0-alpha3, hyperledger/fabric-tools:2.5.0-alpha3, hyperledger/fabric-orderer:2.5.0-alpha3.
And change fabric-ca version to hyperledger/fabric-ca:1.5.6-beta3 on compose-ca.yaml then it work on apple arm.

source: gharchive/issue

repo: hyperledger/fabric-samples


text:
Fix test network tutorial to deploy go smart contract

Add missing options to the test network tutorial to deploy go smart contract
Type of change

Documentation update

Description
In test-network, deployCC command requires the language and path
of the Chaincode. However, the tutorial does not specify anything
and the script fails to deploy Chaincode.
This PR fixes the command in the tutorial to deploy chaincode.
Additional details
Related issues

@mergifyio backport release-2.3

@mergifyio backport release-2.3

repo: hyperledger/fabric

license_source: bigquery


text:
[Suggestion]: generate API and wrappers from specification file

As the Indy SDK is evolving quickly, its API changes very frequently.
Currently, as no automation is in place, the boilerplate code for each function in libindy/src/api/*.rs needs to be manually written. This is sub-optimal not only in principle (all those functions look exactly the same, so they should be automated), but also in practice, as developers might forget some pieces (e.g. some checks) and the addition of new features (e.g. more detailed logging or more runtime checks) becomes a huge task.
The absence of automation also means that all the wrappers need to be manually synced with every change. Currently only the NodeJS wrapper uses automation, but the source of that automation still needs to be synced with the API implementation.
It might be worth exploring the possibility of defining the names of all functions, their categories (e.g. anoncreds, wallet, ledger, ...), the names and types of their parameters and returned values, in a single specification file, both machine-readable and human-readable (e.g. YAML), and then generate the libindy/src/api folder and all wrappers by merging this file with some templates (e.g. mustache). Thus, this spec file would act as the single source of truth for the API declarations, removing the burden of keeping everything in sync.
This would benefit not only the maintenance of the official API and wrappers, but also the maintenance of unofficial and internal bindings that products developed on top of the Indy SDK might need. These unofficial bindings could be generated from the official spec file in the same way as official wrappers are.
A further improvement would be the documentation: if the spec file also contained the documentation associated with each function, parameter and return value, this documentation could then not only be automatically embedded in the source code of each wrapper using the most proper way (e.g. Javadoc for Java, docstrings for Python), but also used to generate some nice language-agnostic (or even language-specific, if deemed necessary) HTML documentation, which would be always up to date and could be hosted on GitHub Pages or somewhere else. Currently, no comprehensive and up-to-date documentation of all Indy SDK functions exists.
If this approach happens to work well, it can later be extended by adding additional features. One could be declaring all error codes and messages and associating each function with the codes that it might generate. Another could be refining the type declarations for JSON-serialized parameter and return values, associating them with their internal structure, which would benefit the bindings in typed languages.
What follows is an example of the YAML specification for the function indy_create_and_store_my_did. It is just an example, the actual structure might be different.
- category: did
  name: create_and_store_my_did
  description: >
    Creates keys (signing and encryption keys) for a new
    DID (owned by the caller of the library).
    ... more documentation here ...
  parameters:
  - name: wallet
    type: handle
    description: wallet handle (created by open_wallet)
  - name: did_info
    type: json
    subtype: MyDidInfo
    description: identity information
  returns:
  - name: did
    type: did
    description: DID generated and stored in the wallet
  - name: verkey
    type: verkey
    description: the verkey associated with the generated DID

We are using Jira to track issues now, please use this Jira IS-980 ticket for any further discussion.

repo: hyperledger/indy-sdk


text:
Send "catch-up" State Delta Events on Subscribe

When a state delta export subscriber registers with a known block id that is older than the current chain head, send the subscriber all the events that have occurred in the interim.   This allows the subscriber to behave as if it received all the correct events.
Additionally:

Add a Predecessor Iterator on block store

Rebased on master for the shutdown test ignores

Rebased before merging

Added a new change that may require more review.

repo: hyperledger/sawtooth-core


text:
[Bug] race graph dithers heavily at beginning of every month (2k+ data)

Version
1.9.3
Current Behavior
https://github.com/godotengine/godot-docs/pulse?redirect=perceptor
Watch this repo's animation, and it seems glitching in the gap of months.
Expected Behavior
No response
Environment
- OS: Ubuntu
- Browser: Edge

Any additional comments?
Am I the only one having this problem? pls let me know.

Pinging @tyn1998 @wxharry

I did not see the glitch, can you give the animated segment of the glitch.

repo: hypertrons/hypertrons-crx


text:
Add AUR mention to Readme

This pull request adds a mention of the unofficial AUR package to the readme alongside basic instructions. This is my first time dealing with pull requests so sorry in advance for any mistakes.

@LynHyper thanks for this PR! I'm sorry it's taken me this long to review it. I'm slightly worried about promoting a 3rd party distribution we don't have any control over but I think the way you word it in the README is good. Do you happen to know of any other projects which link to the AUR officially?

Can't think of any project from the top of my head, it's pretty common for smaller projects to link to AUR packages with a warning included as far as I know

Now that Hyprspace has an install script, the AUR mention isn't quite as necessary, I also need to rebase this pull request to the newest version of this repo. I'll close this pull request for now.

authors: LynHyper alecbcs

repo: hyprspace/hyprspace


text:
[HOWTO] Screen sharing in Hyprland with Firefox & Brave

Great project btw!!
So I had to invest a lot of time to make this work so I think it would be helpful to add this info to the documentation.
The steps I had to take on Fedora 36 to make screen sharing to work were:.

Install portal package for wlroots in fedora:
sudo dnf install xdg-desktop-portal-wlr
Add 'hyprland' to 'UseIn' at /usr/share/xdg-desktop-portal/portals/wlr.portal:
Add to hyperland configfile:
exec-once=systemctl --user import-environment DISPLAY WAYLAND_DISPLAY SWAYSOCK
exec-once=hash dbus-update-activation-environment 2>/dev/null && dbus-update-activation-environment --systemd DISPLAY WAYLAND_ DISPLAY SWAYSOCK

Maybe there is some "extra command" to add (or remove) to this
Keep rocking! Thanks!
PD: In chromium does not work :D

chromium runs in XWayland by default, you have to launch it with ozone wayland platform, but that has issues with rendering (blame chromium)

furthermore, that info is already in the FAQ.

ouch! i really did not found it. Sorry

added the execs to the wiki doe as i forgot them.

Shouldn't only one of those execs be needed? (either the systemctl or the dbus one)

You're right. The dbus one is recommended.

Is there some special step on nixos to achieve this? I'm currently having my browsers (chromium and firefox) crash when trying to screen share. Obs works fine.

Also getting this issue on NixOS. After days of setting up hyprland, I've spent all day today banging my head against this issue of screensharing...
I get the tab/window/screen dialog that pops up, then a secondary pop up asking to either share Screen, window, or region. I can select either of those, but the only one that shows a "preview" back on the Brave browser dialog screen is window share, but then no matter what I select, after I share the window or entire screen, nothing shows up and Brave crashes.
Did not realize something like screen sharing would be such a pain on wayland (well, hyprland) + nixOS
Has anyone made any progress with this or got it working?
Thanks

authors: GustavoPeredo Overbuffer PowerBall253 fufexan truvatech vaxerski

repo: hyprwm/Hyprland


text:
Cannot start Hyprland in VM

it looks like this

cool. https://wiki.hyprland.org/Getting-Started/Master-Tutorial/#vm


text:
update example hyprland.conf

#6479 replace master:new_is_master with master:new_status

https://github.com/hyprwm/Hyprland/blob/main/src/config/defaultConfig.hpp#L141 should also be updated.

What is the point except break config ?

I don't mind such changes, but a heads up in the changelog about a breaking config update would be nice.

What is the point except break config ?

not much, it seems

authors: TSmigielski fufexan memchr noahfraiture onyasumi


text:
Doesn't build on Ubuntu 12.04 any more

The latest freshplayerplugin from Git can't be built on Ubuntu 12.04 any more - here's the error I get:
/«BUILDDIR»/freshplayerplugin-0.3.2+git20150831~webupd8~precise/src/config.c: In function 'fpp_config_initialize':
/«BUILDDIR»/freshplayerplugin-0.3.2+git20150831~webupd8~precise/src/config.c:151:9: error: implicit declaration of function 'config_error_type' [-Werror=implicit-function-declaration]
/«BUILDDIR»/freshplayerplugin-0.3.2+git20150831~webupd8~precise/src/config.c:151:40: error: 'CONFIG_ERR_PARSE' undeclared (first use in this function)
/«BUILDDIR»/freshplayerplugin-0.3.2+git20150831~webupd8~precise/src/config.c:151:40: note: each undeclared identifier is reported only once for each function it appears in

The complete build log can be found here: https://launchpadlibrarian.net/215966001/buildlog_ubuntu-precise-amd64.freshplayerplugin_0.3.2%2Bgit20150831~webupd8~precise_BUILDING.txt.gz
It used to work the last time I built it in my PPA, on August 21st.

Patches 1daa36a55bd4d3900b0487ddccf7c252c8e49052...9d987e2f88dd5eecc77a8d38220919871e1e0925 adds libconfuse to source tree, and change configuration file processing to use it, thus eliminating dependence on libconfig. Since there is no libconfig-dev in dependencies list, its different ABI shouldn't interfere compilation anymore. (I didn't try to build on Ubuntu 12, though).

It now builds successfully on Ubuntu 12.04, thanks!

authors: hotice i-rinat

repo: i-rinat/freshplayerplugin

license: MIT


text:
Unable to build in Ubuntu 14.04

I think it's due to 14.04 shipped with libav instead of ffmpeg. Since 14.04 is a LTS version this should be fixed.
-- Performing Test HAVE_AVPixelFormat
-- Performing Test HAVE_AVPixelFormat - Success
-- Performing Test HAVE_AV_PIX_FMT_VDPAU
-- Performing Test HAVE_AV_PIX_FMT_VDPAU - Failed
-- Performing Test HAVE_AVCodecID
-- Performing Test HAVE_AVCodecID - Success
-- Performing Test HAVE_AVCodecContext_get_buffer2
-- Performing Test HAVE_AVCodecContext_get_buffer2 - Failed
-- Performing Test HAVE_AVVDPAUContext
-- Performing Test HAVE_AVVDPAUContext - Failed
-- Looking for av_frame_alloc
-- Looking for av_frame_alloc - not found
-- Looking for av_frame_free
-- Looking for av_frame_free - not found
-- Looking for avcodec_free_context
-- Looking for avcodec_free_context - not found

Those are configuration tests, their successes or failures are equally expected. I have workarounds in code, which for example, defines structure AVPixelFormat if it wasn't defined.
Are there any errors during build?

Hmm... I made a mistake. After installing all necessary packages as indicated in the README.md file I can successfully build the plugin now.

authors: i-rinat yegle


text:
Broken video with hwdec enabled

ppb_video_decoder_decode() is feeded sometimes with bitstream buffers in a wrong order (i.e. 5, 6, 1, 2, 3, 4, 7, 8 and so on). Could be related to task reordering in a message loop.

I'm also experiencing this issue. Is there anything I could do to help? The video dies seemingly every time with hwdec enabled. For now i've just disabled hwdec but I would really like to use it.

It would be nice if someone fixed that instead of me :-)
Aside from that, there are not so much to do. I've done some debugging, and the cause is task reordering indeed. There is a trick in nested loop handling, where a task with a specified depth level is expected. To make that work, tasks with lower levels are rescheduled to "now + 10 ms". That effectively breaks their order.
I think solution is to figure out other way of task queue handling, which won't break other things. A subtle place.

Should be fixed by 7ba5f2de0e7a8b6f6bbb1e66abab86300dcc4db9.

It seems to be fixed. Thanks alot!

I still get a black screen and <...>

Try to dump bitstream with code from dump-bitstream branch. It will save raw video data to files in /tmp. When you find a video which triggers the bug, try to play it with mpv or mplayer, with software decoder. What under test is: will it be decoded without glitches or not.
There are two cases. It could be freshwrapper breaking the video. Or it could be that hw decoder can't decode it.

Ok, I have the video. If i play it with mpv with --hwdec=vdpau --vo=vpdau, the video looks correct and I get no errors. If i play with just mpv (software), it also looks fine. So, i cannot reproduce the errors and black screen without freshplayerplugin. does this mean its a freshplayerplugin bug? thanks

does this mean its a freshplayerplugin bug?

Yeah, most probably.
So, just to reiterate. You've seen visual glitch in Flash-based video player, which caused mentioned error messages. Then found corresponding .bitstream dump in /tmp, and tried to play it in a player with both software and hardware decoding modes. And both tries were decoded correctly. Right?
In that case there is something with freshplayerplugin, but I can't say what exactly causes it. Previous issues were due to reordering of bytes in bitstream, which resulted in a broken H.264 data.

Yes, but it is not really visual glitches, the screen just goes black while the sound continues.

but it is not really visual glitches, the screen just goes black

Then it's a different issue.
I've also read again error message you posted. "Invalid UVD handle 0xc2800013!" looks very strange. It's not like an error in data, but an error in metadata. UVD handle is low-level stuff. Neither ffmpeg, nor freshwrapper uses it. Perhaps, there were some stream shift, or some bytes were lost, which caused misinterpretation of data. I have no idea what causes it, and how to fix it.

Ok, thanks for looking. Let me know if I can do anything to help.

@sarnex, does that still happen?

Sorry about the super late reply, it looks like it's fixed. Thanks.

it looks like it's fixed

Cool.
"If you wait by the river long enough, the fixes of the bugs will float by..."

authors: i-rinat sarnex


text:
public.xml id changes when recompile apk

Original issue 458 created by email.pl74 on 2013-05-12T14:20:45.000Z:

What steps will reproduce the problem?

apktool if framework-res.apk (create 1.apk)
apktool if oppo-framework-res.apk (create 12.apk)
apktool d oppo-framework-res.apk
Don't change anything
apktool b oppo-framework-res oppo-new.apk
apktool d oppo-new.apk

What is the expected output? What do you see instead?
When i compare public.xml from original apk and recompiled apk the id are changed. Ex. in original public.xml i find the line:
<public type="attr" name="Dialog_Title_textAppearance" id="0x0c010000" />
in the recompiled public.xml same line became:
<public type="attr" name="Dialog_Title_textAppearance" id="0x02010000" />
So if i try to pull new apk to the phone i obtain rebooting system.
What version of the product are you using? On what operating system?
APKTool 1.5.2
aapt from apktool project site (i tried also aapt from latest android sdk)
Windows 7 Home Premium 64bit
Please provide any additional information below.
Here can find apks and two public.xml: http://d-h.st/A1K

Did you found any solution on this issue???

I found solution by using this software: xdaAutoAPKTool_V5.0.0b
The oppo-framework-res.apk file is finally compiled without this error in the public.xml file
The APP is WORKING !!! Tested!
The other problem with the KeKeThemeSpace_W20140729_V2.5.1.apk is gone too!!!
Only you have to modify the default_splash_bg.png image in the drawable-xxhdpi folder and the app will be compiled and working!

authors: Fancyfree iBotPeaches

repo: iBotPeaches/Apktool


text:
🛑 OBEC Academy is down

In 7172ac3, OBEC Academy (https://dlp.obec.go.th) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OBEC Academy is back up in 9cee41a after 9 minutes.


text:
chore: promote react-spring to version 0.0.32

this commit will trigger a pipeline to generate the actual kubernetes resources to perform the promotion which will create a second commit on this Pull Request before it can merge

react-spring
Changes in version 0.0.32
Chores

release 0.0.32 (jenkins-x-bot)
add variables (jenkins-x-bot)

Other Changes
These commits did not use Conventional Commits formatted messages:

change App.js (iMckify)

[jx-info] Hi, we've detected that the pipelines in this repository are using a syntax that will soon be deprecated.
We'll continue to update you through PRs as we progress. Please check #8589 for further information.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign
You can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@iMckify: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

verify
632cd006f601c3fd0baa12c7123a3b2351c34b26
link
/test verify

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

repo: iMckify/pipeline-cluster


text:
Add support for Hitachi RASM3-VNE Heat PumpAirToWaterMainComponent (modbus:YutakiMainComponent)

[x] I have read the README, including the advanced section regarding debugging.

The device is a Hitachi Heat Pump Model: RASM 3 VNE . It is an air to water heat pump used for heat only. The device is controlled by Hi_Kumo app by Hitachi and powered by moduloTech.

Device information
The Hi Ku-Mo App allows remote activation, deactivation of the Heat Pump, temperature setup and weekly timer setup for space heating. Also you can setup the Domestic Hot Water temperature setpoint and activate/deactivate it. Aslo the app shows outside temperature , Set temperature and current hot water and room temperature. These would be nice to be able to be  sensor entities in home assistant. Options for Holiday settings and ECO Mode is also available in the app. App screenshots attached.

Device details

Hub: Hitachi ATW-TAG-02 Home Automation Gateway and Smart Hi-Box Model: AHP-SMB-01

Device commands

Please find attached a word document. This includes the executed commands from the Hi Kumo App ( In RED Color) and the result in the home assistant log file from the tahoma.get_execution_history. Some duplicates exist.
home assistant hitachi hi-kumo log.docx

Thanks for reporting @stavrosso and great to hear that Hi-Kumo works!
In order to gather more information, you can use the tahoma.get_execution_history service in Home Assistant which will print your execution history to the Home Assistant log.
Run the all available commands via the Hi-Kumo app and write down what you called. Now go to Developer Tools -> Services and execute tahoma.get_execution_history. This will print the last execution history in your logbook, which you can paste here.

Good Morning @iMicknl ,
I have run the commands in the Hi-Kumo App and registered all the log entries in a word document. The actual log file is so long because I was trying command since last night. If you want I can paste it here but IT IS long. I think the word file I uploaded on the bottom of my initial Issue (above) will be more helpful. Please let me know if this is not the case. Thank you

@stavrosso your Word document is very extensive, thank you. Unfortunately this is not the output which mentions the command name, thus I am not able to use it for the development.
The command history should look like:
2021-02-04 10:45:34 INFO (MainThread) [custom_components.tahoma] 2021-02-02 15:06:10: setVentilationConfigurationMode executed via Android 2.4.8#220 Set device mode : AUTO on io://xxxx-xxxx-xxxx/xxxxxxxxxx#1, with ['comfort'].

(see https://github.com/iMicknl/ha-tahoma/issues/376 as an example)
It is possible that this execution history is not supported on Hi-Kumo, but that would be hard to check. If you are willing to share your credentials with me sometime, we can have a chat on Discord -> iMick#1903. You can change your password to a temporary one when I am testing some stuff, and we can work together on retrieving this information.
Otherwise, we need to see if I can develop a basic version using the device definition, however this can take quite some time.

Good morning Mick.
Thank you for the message.
I would be happy to share my credentials with you in order to get this sorted out.Just let me know when you want to do that.
I have sent a friend request on Discord . Mine is Stavros#8220.
Have a nice day.
Regards
Stavros

Here are some commands I copied from Home assistant log
Set Room temperature to 21°
2021-02-12 18:56:27 INFO (MainThread) [custom_components.tahoma] 2021-02-12 18:55:28: globalControl executed via Room focus : set air to water heat pump state on modbus://0810-9263-3428/5608763/1#2, with ['manu', 'heat', 21]. 2021-02-12 18:56:27 INFO (MainThread) [custom_components.tahoma] 2021-02-12 18:55:28: setAutoManuMode executed via Room focus : set air to water heat pump state on modbus://0810-9263-3428/5608763/1#2, with ['manu']. 2021-02-12 18:56:27 INFO (MainThread) [custom_components.tahoma] 2021-02-12 18:55:28: setHolidayMode executed via Room focus : set air to water heat pump state on modbus://0810-9263-3428/5608763/1#2, with ['off'].
Turn OFF Room Heating
2021-02-12 19:02:16 INFO (MainThread) [custom_components.tahoma] 2021-02-12 19:00:58: globalControl executed via devices list : set air to water heat pump to OFF on modbus://0810-9263-3428/5608763/1#2, with ['off', 'heat', 21]. 2021-02-12 19:02:16 INFO (MainThread) [custom_components.tahoma] 2021-02-12 19:00:58: setAutoManuMode executed via devices list : set air to water heat pump to OFF on modbus://0810-9263-3428/5608763/1#2, with ['manu']. 2021-02-12 19:02:16 INFO (MainThread) [custom_components.tahoma] 2021-02-12 19:00:58: setHolidayMode executed via devices list : set air to water heat pump to OFF on modbus://0810-9263-3428/5608763/1#2, with ['off'].
Turn ON Room Heating
2021-02-12 19:11:31 INFO (MainThread) [custom_components.tahoma] 2021-02-12 19:10:06: globalControl executed via devices list : set air to water heat pump to ON on modbus://0810-9263-3428/5608763/1#2, with ['manu', 'heat', 20]. 2021-02-12 19:11:31 INFO (MainThread) [custom_components.tahoma] 2021-02-12 19:10:06: setAutoManuMode executed via devices list : set air to water heat pump to ON on modbus://0810-9263-3428/5608763/1#2, with ['manu']. 2021-02-12 19:11:31 INFO (MainThread) [custom_components.tahoma] 2021-02-12 19:10:06: setHolidayMode executed via devices list : set air to water heat pump to ON on modbus://0810-9263-3428/5608763/1#2, with ['off'].
Turn On the DHW Switch in the App main Welcome Screen
2021-02-12 19:17:19 INFO (MainThread) [custom_components.tahoma] 2021-02-12 19:15:51: setControlDHW executed via devices list : set domestic hot water tank to ON on modbus://0810-9263-3428/5608763/1#4, with ['run']. 2021-02-12 21:01:09 INFO (MainThread) [custom_components.tahoma] 2021-02-12 21:00:38: setControlDHW executed via devices list : set domestic hot water tank to ON on modbus://0810-9263-3428/5608763/1#4, with ['run'].
Turn OFF the DHW Switch in the App main Welcome Screen
2021-02-12 20:46:14 INFO (MainThread) [custom_components.tahoma] 2021-02-12 20:09:38: setControlDHW executed via devices list : set domestic hot water tank to OFF on modbus://0810-9263-3428/5608763/1#4, with ['stop'].
Turn OFF the DHW via the YUTAKI DHW Screen (Accessible if you click the YUTAKI DHW from the Main Welcome Screen)
2021-02-12 20:58:26 INFO (MainThread) [custom_components.tahoma] 2021-02-12 20:56:56: setControlDHW executed via Room focus : set domestic hot water tank state on modbus://0810-9263-3428/5608763/1#4, with ['stop'].
Set DHW water temperature to 37 Degrees
2021-02-12 20:53:15 INFO (MainThread) [custom_components.tahoma] 2021-02-12 20:52:46: globalControlDHW executed via Room focus : set domestic hot water tank state on modbus://0810-9263-3428/5608763/1#4, with ['run', 'standard', 37].
Set Water Temperature to 40 Degrees
2021-02-12 19:20:59 INFO (MainThread) [custom_components.tahoma] 2021-02-12 19:20:21: globalControlDHW executed via Room focus : set domestic hot water tank state on modbus://0810-9263-3428/5608763/1#4, with ['run', 'standard', 40].
Set Water Mode to High Demand and 37 Degrees via the YUTAKI DHW Screen (Accessible if you click the YUTAKI DHW from the Main Welcome Screen)
2021-02-12 21:02:50 INFO (MainThread) [custom_components.tahoma] 2021-02-12 21:02:25: globalControlDHW executed via Room focus : set domestic hot water tank state on modbus://0810-9263-3428/5608763/1#4, with ['run', 'high demand', 37]
Set Water Mode to Standard and 37 Degrees via the YUTAKI DHW Screen (Accessible if you click the YUTAKI DHW from the Main Welcome Screen)
2021-02-12 21:04:54 INFO (MainThread) [custom_components.tahoma] 2021-02-12 21:04:18: globalControlDHW executed via Room focus : set domestic hot water tank state on modbus://0810-9263-3428/5608763/1#4, with ['run', 'standard', 37].
Changed temperature on Weekly Timer Friday  05:30-11:00 from 20 to 21 Degrees
No Record in Log
Change Room Heating mode from Manual to Weekly Timer
2021-02-12 19:31:30 INFO (MainThread) [custom_components.tahoma] 2021-02-12 19:31:13: globalControl executed via Room focus : set air to water heat pump state on modbus://0810-9263-3428/5608763/1#2, with ['auto', 'heat', 21]. 2021-02-12 19:31:30 INFO (MainThread) [custom_components.tahoma] 2021-02-12 19:31:13: setAutoManuMode executed via Room focus : set air to water heat pump state on modbus://0810-9263-3428/5608763/1#2, with ['auto']. 2021-02-12 19:31:30 INFO (MainThread) [custom_components.tahoma] 2021-02-12 19:31:13: setHolidayMode executed via Room focus : set air to water heat pump state on modbus://0810-9263-3428/5608763/1#2, with ['off'].
Change Room Heating mode from Weekly Timer to Manual
2021-02-12 21:17:47 INFO (MainThread) [custom_components.tahoma] 2021-02-12 21:17:29: globalControl executed via Room focus : set air to water heat pump state on modbus://0810-9263-3428/5608763/1#2, with ['manu', 'heat', 21]. 2021-02-12 21:17:47 INFO (MainThread) [custom_components.tahoma] 2021-02-12 21:17:29: setAutoManuMode executed via Room focus : set air to water heat pump state on modbus://0810-9263-3428/5608763/1#2, with ['manu']. 2021-02-12 21:17:47 INFO (MainThread) [custom_components.tahoma] 2021-02-12 21:17:29: setHolidayMode executed via Room focus : set air to water heat pump state on modbus://0810-9263-3428/5608763/1#2, with ['off'].
Thank you @iMicknl  for your time and hard work. Your help is appreciated

@stavrosso thanks! Let me know what doesn't work in the latest test version and I will have a look at the commands :).

Hi Mick,
Here is a list of commands that work normally and others that don't for your reference
1. THERMOSTAT - Entity id:  climate.modbus_5608763_1_2
Room Heating temperature (Thermostat) can’t be set from home assistant. The value changes if you use the thermostat slider but the app is not updated.
At some point I got this error
Logger: custom_components.tahoma.tahoma_device
Source: custom_components/tahoma/tahoma_device.py:163
Integration: Somfy TaHoma (documentation, issues)
First occurred: 4:14:24 PM (1 occurrences)
Last logged: 4:14:24 PM
setRoomAmbientTemperatureControlZone1() : Invalid value for command parameter p1 : expected integer value but got 21.0

Is it possible for Auto to be renamed to Weekly Timer and Heat to Manual? . This is how they are referred in the app. If it is difficult it is not a big issue as long as the mode change works, which does not.
Trying to change from Auto to Heat (Weekly Timer to Manual in the app) returns the message Failed to call climate/set_hvac_mode.”heat” and does not perform the related action in the app. These are the commands if executed from the app:
globalControl executed via Room focus : set air to water heat pump state on modbus://0810-9263-3428/5608763/1#2, with ['manu', 'heat', 20].
setAutoManuMode executed via Room focus : set air to water heat pump state on modbus://0810-9263-3428/5608763/1#2, with ['manu'].
setHolidayMode executed via Room focus : set air to water heat pump state on modbus://0810-9263-3428/5608763/1#2, with ['off'].

On the other hand changing from Heat to Auto (Manual to Weekly timer) from home assistant, works and the app state is updated.This is the executed command:
setAutoManuMode executed via Home Assistant on modbus://0810-9263-3428/5608763/1#2, with ['auto'].

PRESET ECO/COMFORT does not change from Home assistant interface

If you select ECO or COMFORT from the drop down list in home assistant,  the  state does not change in the app, Something odd that I noticed is that a “circle” animates on the  icon for setting the room temperature  heating in the app (as it is trying to change the set temperature) .

WATER HEATER (DHW) Entity id: water_heater.modbus_5608763_1_4

Water heater (DHW) temperature can’t be set from home assistant. Changing the water heater temperature from home assistant interface does not update the app and reverts back to set Temperature. This is the command when executed from the app:
globalControlDHW executed via Room focus : set domestic hot water tank state on modbus://0810-9263-3428/5608763/1#4, with ['run', 'standard', 35].

AWAY MODE on home assistant works normally and switches the DHW Water OFF/ON in the app. It works fine but the name should be something like DHW (Or Water Heater) ON/OFF if possible of course.
OPERATION MODE works normally and changes DHW mode from Standard to High Demand and vice versa in the app.
If you need additional information please let me know.
Thank you

Room Heating temperature (Thermostat) can’t be set from home assistant. The value changes if you use the thermostat slider but the app is not updated.

Should be fixed in the latest version (updated this afternoon).

Is it possible for Auto to be renamed to Weekly Timer and Heat to Manual? . This is how they are referred in the app. If it is difficult it is not a big issue as long as the mode change works, which does not.

Unfortunately this is not possible. We can only choose from the following names: https://developers.home-assistant.io/docs/core/entity/climate/#hvac-modes.

Trying to change from Auto to Heat (Weekly Timer to Manual in the app) returns the message Failed to call climate/set_hvac_mode.”heat” and does not perform the related action in the app. These are the commands if executed from the app:

Should be fixed in the latest version (updated this afternoon).

If you select ECO or COMFORT from the drop down list in home assistant, the state does not change in the app, Something odd that I noticed is that a “circle” animates on the icon for setting the room temperature heating in the app (as it is trying to change the set temperature) .

Not sure about this one yet, I would need to do some more research.. The other user also reported that these didn't work.

Water heater (DHW) temperature can’t be set from home assistant. Changing the water heater temperature from home assistant interface does not update the app and reverts back to set Temperature. This is the command when executed from the app:

Ok, let me know via Discord when you have time and we can have a look together at some day. I would like to give it a try myself when developing, but would be good to discuss the moment ;-).

AWAY MODE on home assistant works normally and switches the DHW Water OFF/ON in the app. It works fine but the name should be something like DHW (Or Water Heater) ON/OFF if possible of course.

Unfortunately, water heaters don't support on/off in Home Assistant. I thought best way would be to map it to the away mode, since this is probably when you want to turn it off? :)

Great , Evrything looks fine. Just let me know a convenient time to talk on discord.

Good morning Mick,
All works perfectly after the last update. Thank you
Could you possibly add the ON/OFF mode to the Thermostat? (We currently have AUTO and HEAT Operations)
OFF Command is:
globalControl executed via devices list : set air to water heat pump to OFF on modbus://0810-9263-3428/5608763/1#2, with ['off', 'heat', 19].
setAutoManuMode executed via devices list : set air to water heat pump to OFF on modbus://0810-9263-3428/5608763/1#2, with ['manu'].
setHolidayMode executed via devices list : set air to water heat pump to OFF on modbus://0810-9263-3428/5608763/1#2, with ['off'].

ON Command is:
globalControl executed via devices list : set air to water heat pump to ON on modbus://0810-9263-3428/5608763/1#2, with ['manu', 'heat', 20].
setAutoManuMode executed via devices list : set air to water heat pump to ON on modbus://0810-9263-3428/5608763/1#2, with ['manu'].
setHolidayMode executed via devices list : set air to water heat pump to ON on modbus://0810-9263-3428/5608763/1#2, with ['off'].

Thank you

@stavrosso I will have a look for the on/off, need to have a look if this set via the same device. Not sure how climate front-end shows on/off.

Also is it possible to have 0.5 steps in thermostat temperature? ( The Hi-Kumo App does not allow 0.5 step changes but the Hitachi controller does. So the room temperature can be set to 19.5 for example on the controller but not in the app).

I understood that this is not supported in the API as well... During implementation I faced errors when passing a float (comma number) instead of an integer. We could have a look, but I am afraid that this is not supported.

Hi Mick,
If you look at the water heater entity (water_heater.modbus_5608763_1_4) you have enabled 3 modes, standard, high demand and OFF mode , I don't know if the OFF command there could help you figure out how to enable the ON/OFF command on the heating. It seems that the device triggered if I switch the Heating ON or OFF from the app is modbus://0810-9263-3428/5608763/1#2  and the commands appear on my previous post.
I am available anytime you can to try and figure this out.
Thank you again
Stavros

@stavrosso is this still an issue? In case you are missing any features in the current implementation, feel free to create a new issue.
Have a look here (https://github.com/iMicknl/ha-tahoma#device-not-working-correctly) for more details about what to add and how to receive the commands.

authors: iMicknl stavrosso

repo: iMicknl/ha-tahoma


text:
Component .scss changes don't hot load

Component level .scss file changes don't hot reload.
The server must be killed and restarted to reflect changes. We haven't touched any project configuration. Is this a bug or by design?

@spentak I've tried to reproduce this, but both the .global.scss and compontent .scss files reload flawlessly for me, so I need some more information.
Is this on a fresh project (i. e. no files altered) or have you modified some files? What node version and OS are you using?

I've been trying to find the source of the issue, but without success. Is there a way to help better debug why this is happening?
Here is what I know:

It is intermittent. At some point during a daily session of development hot loading stops working for .scss files
Perhaps it is related to how Webpack combines all the CSS files? Because another issue is that CSS classes and Sass variables in the app.global.scss file are NOT available at the module level .scss files. If I specify color-main in the global file, and try and reference that class in a module-file .scss, we get a compiler error saying main-color cannot be found. I really need to nail this particular issue down as we will be theme-ing the project, and putting theme class-names in the HTML as classNames is not realistic.
Sometimes code (TS or TSX files) get cached. Meaning, the hot loader sometimes doesn't detect changes in code, and so it references the underline compiled javascript (the old version). This happened just last night - spent an hour trying to figure out why code I was writing was undefined, to come and find out the underlying .js file had the old code.

Here is my project if you wanted to look yourself: https://www.dropbox.com/s/124rz175tzjkg1h/project.zip?dl=0
Using node v6.11.4, Using macOS High Sierra 10.12.6
The biggest issue im having of all, is getting module-based .scss files to compile after the global. I would expect global variables to be accessible in local modules. And if not sass variables, then at least being able to reference the post compiled class in names (instead of having to do it in the HTML)
Maybe you can just point me in the right direction

Regarding the theming issue:
Yes, Sass files are compiled independently. If you want to share a variable among them, you'll need to create an "include"-file of some sort (a file that contains only the variables and that you @include in every Sass file).
The way you are approaching theming will require you to compile a separate CSS file for each theme. While this is possible, a nicer approach to theming, imho, is this: https://medium.com/@dmitriy.borodiy/easy-color-theming-with-scss-bc38fd5734d1
The basic idea is that you give your body or application container a class-name which is used to switch between themes.
Regarding the caching issue
Are you getting any messages in your Electron console or on your terminal? Does webpack recompile when you save?

license: mit


text:
Update sbt-scoverage to 1.7.1

Updates org.scoverage:sbt-scoverage from 1.6.1 to 1.7.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

labels: sbt-plugin-update, semver-minor

Codecov Report

Merging #204 (85f25f2) into master (0fec237) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #204   +/-   ##
=======================================
  Coverage   97.04%   97.04%
=======================================
  Files          34       34
  Lines         169      169
  Branches        1        1
=======================================
  Hits          164      164
  Misses          5        5

Flag
Coverage Δ

unittests
97.04% <ø> (ø)

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

Continue to review full report at Codecov.

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

Superseded by #205.

authors: codecov-commenter scala-steward

repo: iRevive/fmq


text:
Update sbt to 1.3.10

Updates org.scala-sbt:sbt from 1.3.9 to 1.3.10.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, semver-patch

Codecov Report

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

@@           Coverage Diff           @@
##           master      #86   +/-   ##
=======================================
  Coverage   98.00%   98.00%
=======================================
  Files          32       32
  Lines         150      150
=======================================
  Hits          147      147
  Misses          3        3

Flag
Coverage Δ

#unittests
98.00% <ø> (ø)

Continue to review full report at Codecov.

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

authors: codecov-io scala-steward


text:
Vragen feedback aanpassen

Omschrijving:

Was de omschrijving van het spel duidelijk?
Waren de regels duidelijk?
Vonden de kinderen het leuk?

Doet dit dus ook in het CMS

repo: iSirThijs/jungle-gym


text:
fix(Dialog): Apply z-index on the wrapper

In itwinui-react 1.48.0, the Modal component uses iui-dialog-wrapper, which creates a stacking context and prevents children's z-index from being applied correctly.

So I've moved the z-index to the root. Still need to investigate if this is the correct solution, but I think it is.
After this change:

Superseded by https://github.com/iTwin/iTwinUI-react/pull/892.

Reopening this and targeting v1 branch.

repo: iTwin/iTwinUI


text:
ivhTreeviewMgr.expandTo does not work with ng-if in custom template

See: http://jsbin.com/payudu/edit?html,js,output
Hitting the Expand To Ballpoint only expands a single level at a time. Remove the ng-if from the custom template and it will correctly expand to the ballpoint node.

For posterity, the issue lies with the fact that, on creation, each treeview node sets it's expanded state by looking at the expandToDepth setting. When using ng-if in a template nodes are created and destroyed as they go in and out of view.
In the custom template example, with ng-if, after hitting Expand To Ballpoint the tree data is set correctly (i.e. node "expanded" properties are set correctly) then the view updates and the first row of new nodes become visible. When that happens, and the individual nodes get created, they look at the default expandToDepth and clobber the previously set expanded state.
Seems like we should do one of the following:

Have expandToDepth only matter when the tree is first created - then always defer to the individual node's expanded property... or...
Always let the node's expanded property override the default... or...
Any other ideas?

Should be an easy fix, just need to decide on the appropriate behavior and add some tests.

repo: iVantage/angular-ivh-treeview


text:
Make queue host response be based on request

I have test systems and for them, I'm constantly spinning up different ports and things.
So - the "baked in" port with fake_sqs is a non-starter for me.
I made these changes so that, whatever the client "thinks" the fake_sqs hostname/port is, that is what the fake_sqs will respond with.

Thanks, similar solution was merged in #44.

authors: caryfitzhugh tiwilliam


text:
Day22: Prerequistes do not contain all the tools needed

File: Prerequisites.md
Issue: It should contain HELM as prerequisite which is a miss

have fixed it and Raised a PR;  Please have a look

repo: iam-veeramalla/aws-devops-zero-to-hero


text:
Autosize Not Working

TextViewCompat.setAutoSizeTextTypeUniformWithConfiguration(tv_title, 5, 21, 1, 2); is not working how can I user autosize with this library ?

After using this library Emjoi not showing in TextView.???

authors: attaullahpro muzeitlimited

repo: iamBedant/OutlineTextView


text:
Add compatibility with Flutter 3.22.0

Fixed #204
Fixed #203
Fixed #200

I have Same problem #204 and not fixed till now.

authors: MtoagF ShafiqSadat

repo: iampawan/VelocityX


text:
Used Sources

All the sources that we use will be here

https://stackoverflow.com/questions/933613/how-do-i-use-assert-to-verify-that-an-exception-has-been-thrown

https://www.c-sharpcorner.com/UploadFile/dacca2/fundamental-of-unit-testing-don’t-test-your-private-method/

https://www.c-sharpcorner.com/UploadFile/dacca2/fundamental-of-unit-testing-understand-mock-object-in-unit/

Followers Schema

Truncate table when it is being referenced by a FOREIGN KEY constraint

Focus on other process's main window

SetForegroundWindow doesn't work with minimized process

Creating a single-instance WPF application

Checks Collection on Equality

Disable All Constraints In The Database

authors: Lenkelheit iamprovidence

repo: iamprovidence/Coursework


text:
Crash in Startup

Version 0.2 crashes on startup. Yesterdays build worked fine.
I'm willing to send log files if one is generated somewhere.

One is generated in Event Viewer (win+r "eventvwr" or type in "event viewer" to start). Is github.io blocked on your network? A new feature checks https://iamtheyammer.github.io/gam-cros-win-wrapper/releases.json to see if a new update is available.

It's crashing on my non-dev server too, so don't worry about getting logs. I've got em and I'm working on a fix right now.

For reference, the error log and stack trace is below.
Application: ChromebookGUI.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileNotFoundException
   at ChromebookGUI.Updates.IsNewestVersion()
   at ChromebookGUI.App.Application_Startup(System.Object, System.Windows.StartupEventArgs)
   at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)
   at System.Windows.Application.<.ctor>b__1_0(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run(System.Windows.Window)
   at ChromebookGUI.App.Main()

Seems like this issue is being caused by ChromebookGUI/ChromebookGUI/Updates.cs:25 because it is looking for a JSON file that does not exist. I need to add some checking code to ensure that there is JSON to convert to a dictionary. I will boot into windows in about 40 minutes and fix this.

Nope. that wasn't the issue. The issue is that necessary files are not present in the same folder. I am working on an MSI to fix this.

Exception Info: System.IO.FileNotFoundException    at ChromebookGUI.Updates.IsNewestVersion()    at ChromebookGUI.App.Application_Startup(System.Object, System.Windows.StartupEventArgs)    at System.Windows.Application.OnStartup(System.Windows.StartupEventArgs)    at System.Windows.Application.<.ctor>b__1_0(System.Object)    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)    at System.Windows.Threading.DispatcherOperation.InvokeImpl()    at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)    at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object)    at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)    at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)    at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)    at System.Windows.Threading.DispatcherOperation.Invoke()    at System.Windows.Threading.Dispatcher.ProcessQueue()    at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)    at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)    at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)    at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)    at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)    at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)    at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)    at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)    at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)    at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)    at System.Windows.Application.RunDispatcher(System.Object)    at System.Windows.Application.RunInternal(System.Windows.Window)    at System.Windows.Application.Run(System.Windows.Window)    at ChromebookGUI.App.Main()

Alrighty, so what actually happened here is I added a dependency requiring Newtonsoft.Json, and I didn't realize that that is not compiled into my exe file. So when it worked for me, it worked because in the same folder as the exe was the proper dll file for the JSON library. Now, the MSI installer puts everything in the right place and adds a Start Menu and Desktop shortcut.
Sorry for the hard time, thank you for using my software!

authors: GameEnder iamtheyammer

repo: iamtheyammer/gam-cros-win-wrapper


text:
Update - Translated to English

There were parts of answers that were in Russian. I translated them to English and edited the links to sections.

Great job, Dipeeka. Thank you!

authors: dipeekabastola iamtodor


text:
Expand dependency version support.

This change expands support for new versions Event Loop and Evenement without abandoning the versions already supported.

Thanks!

authors: bangpound ianbarber

repo: ianbarber/eep-php


text:
Bug fix for chef solo provisioner never validating

Make sure that an empty array does not become a required key.

Is this where I push follow up commits to my branch that removes the stuff you're suggesting I remove?

@diamond29 yea, you can push additional changes to the PR to make them. Would be nice to cut this down to just removing the push of the empty array and that one new spec test. The rest is unnecessary.

Reverted the type checking stuff as specified - I think this can be merged/closed?

Thanks. I'll get it merged today.

repo: ianchesal/packer-config


text:
Switch to root user

[x] Update ansible.cfg
[x] Update playbook in README
[x] Release major version

https://github.com/iancleary/ansible-role-docker/releases/tag/v2.0.0

repo: iancleary/ansible-role-docker


text:
Correct metadata path

Hello,
This is the correct path to use for app metadata.
(The one you used is for when the metadata is included directly into the fdroid repository.)

Awesome, thank you.

authors: Rudloff ianmcxa

repo: ianmcxa/Soft-Sound


text:
Markers badly handled across 180 longitude

Currently, Field Spotter uses a very Grenwich-Meridian-centric idea of the world, and the global set of markers is shown only once, between -180 and +180 longitude.
This works fine for me in the UK but for others around the world, it presents a problem. For an Australian user for example, all the spots are to the west of them, even ones in the Americas which would be better shown to the east. The great circle line also shows the "long path" rather than the short when a spot is clicked.
We need to find a way to display the spots appropriately regardless of where the user is in the world.

The Repeating Marker Layer comes up occasionally as the solution to this, however it does not interact well with the Overlapping Marker Spiderfier plugin that we use. Work is ongoing in the repeating-marker-layer branch to address this, but it is proving difficult. See #29.

Might be easiest just to manually wrap the markers' longitudes if user geolocation is known. If no geolocation is available, we keep a Greenwich-Meridian-centric view and have all markers shown as -180 to +180 longitude. Once geolocation is available, all marker icon longitudes become wrapped to 180 degrees either side of the user's longitude, even if that goes >180 or <-180.
This lets Leaflet wrap properly, and avoids the extra complications of interaction with the Spiderfier.
This won't give you the ability to scroll more than one Earth horizontally without losing the markers, but should be good enough for now.
The only bug I can see with this is the great circle line; while the distance and bearing is correctly calculated, the line itself is drawn assuming only -180<x<180 longitudes are in use:

repo: ianrenton/field-spotter

license: Unlicense


text:
Error initialising the database

Hi,
I've been using the Prompta macOS application for a few days and really liking it, thanks!
Yesterday I pasted in a good chunk of JS error message trying to solve a problem and Prompta crashed.  Since then, opening Prompta app has resulted in the below error message:

There was an error initializing the database. Please try again.  If the problem persists, please report in on GitHub.sqlite3_open_v2.

Deleting ~/Library/WebKit/com.prompta.dev got rid of the error message, but Prompta still hangs forever on opening.
Deleting ~/Library/Caches/com.prompta.dev and I had to enter my API key again but everything is working.

Hey @adamshand , I'm seeing the same error although only in the PWA-installed version. I'm guessing you're getting this directly in the browser?

eh, sorry, i see you're using the installed macos version. latest version?

Yes, I believe it's the latest version:  Version 1.1.0 (20230717.161342)

Just had it happen again when pasting JS code.

Just got it again on the web interface at chat.prompta.dev (5:37pm NZT if you want to look at logs).  Not JS code this time, just text.

What browser? I'm wondering if this is safari related, since the desktop
build is equivalent
On Thu, Jul 27, 2023 at 1:37 PM, Adam Shand @.***>
wrote:

Just got it again on the web interface at chat.prompta.dev (5:37pm NZT if
you want to look at logs). Not JS code this time, just text.
—
Reply to this email directly, view it on GitHub
https://github.com/iansinnott/prompta/issues/5#issuecomment-1652943098,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYCHMJWZNFZ4O4N5HU53VLXSH5CRANCNFSM6AAAAAA2XY7D6Q
.
You are receiving this because you commented.Message ID:
@.***>

ah i see. responded from email which didn't have the image

I'm still not able to repro this. Tried in incognito Brave and the app seems to be working. There's definitely an issue, as i've seen it before too, but i don't currently have a way to reproduce the issue.
any thoughts? it seems like you're running into this fairly often?

I upgraded the database dependencies. This is where the wasm version of sqlite we use comes from.
Not that this will resolve the problem, but you could try the latest version and see if it's any different: https://github.com/iansinnott/prompta/releases/tag/v1.1.1

Will upgrade and see how it goes, thanks!
No idea on reproducibility, seems pretty random, but often as chat logs get longer.  Could it have something to do with tokens running out?
If I spot a pattern or can reliably reproduce, will let you know!

Hello,
I encountered the following error just before the above mentioned problem while using the application:

sqlite-api.js:866 Uncaught (in promise) Error: database disk image is malformed
at check (sqlite-api.js:866:11)
at Object.step (sqlite-api.js:699:14)
at async _TX.statements (TX.ts:152:17)
check @ sqlite-api.js:866
(anonymous) @ sqlite-api.js:699
await in (anonymous) (async)
submit_handler_1 @ +page.svelte:332

This issue has happened multiple times but unfortunately I'm unable to reproduce it. I'll also try to spot a pattern!
I'm using chrome directly. Not PWA.

In a separate project I ran into a similar issue, which lead me to this: https://github.com/vlcn-io/js/issues/31
Prompta uses wa-sqlite with fts5 or search and persistence.

@iansinnott  I think there are two different problems in this thread. The one with the stack trace and "Error: database disk image is malformed" could indeed be https://github.com/vlcn-io/js/issues/31 for which the underlying problems in wa-sqlite and SQLite were recently fixed.
The one that just says "sqlite3_open_v2" doesn't match up with the above bug. There is no known wa-sqlite problem that fails within sqlite3_open_v2() like that. When this occurs, it would be helpful to check the browser Dev Tools JavaScript console for error messages.

Thanks for chiming in @rhashimoto. These may indeed be separate bugs, but when i've seen this pop up in the past they seem correlated. It usually goes like:

Disk image malformed error
(I restart the app)
open_v2 error, assumedly due to malformed database

The app code has not done a good job of surfacing full stack traces for users to post though, so I'm speculating. Looking forward to your recent fix getting merged into vlcn

Anecdotally, I replaced the use of FTS5 with LIKE '%query%' in another app where I'm using vlcn, and so far have had zero issues. When using FTS5 the database would become malformed usually within hours of resetting it.

authors: adamshand iansinnott jdahlborg rhashimoto

repo: iansinnott/prompta


text:
1.1.0 release

since there's added functionality but backwards compatible I think this should be a Semantic Versioning Minor release.

Setting a release date for next Monday in the Milestone

Overview of changes

Hide empty HTML markup

profile social media
<ul> category tags

Profile ACF repeater fields can be now be empty

affiliation
degrees
network
social networks
links

Super Admin access for Theme Options Page
Post show/hide author now ACF field instead of hard-coded
All Blocks now use native anchor functionality instead of ACF field

Legacy anchor names should still work until you update to new field. New field is in right hand menu under "Advanced" dropdown.


text:
FR: Consider adding "--scheme=path" to fzf_opts

fzf 0.33.0 recently added a --scheme argument, relevant quote from the changelog

Added --scheme=[default|path|history] option to choose scoring scheme
(Experimental)

We updated the scoring algorithm in 0.32.0, however we have learned that
this new scheme (default) is not always giving the optimal result
path: Additional bonus point is only given to the the characters after
path separator. You might want to choose this scheme if you have many
files with spaces in their paths.

history: No additional bonus points are given so that we give more
weight to the chronological ordering. This is equivalent to the scoring
scheme before 0.32.0. This also sets --tiebreak=index.

files = { fzf_opts = { ['--scheme'] = "path" } } seems to subtly produce better results in complex projects, and maybe should be default for pickers that involve files. Also, possibly, history for pickers that involve chronological order.

The scheme might be slightly better optimized but adding this to the defaults would require raising the fzf min requirement to 0.3.3. Not everyone use a rolling release or keep all their binaries updated, this is a big change from requiring 0.2.7.
Another option would be to add this conditionally when version >=0.3.3 but then you’d also need to add another option to disable the default should someone prefer not to use it (esp since defined “experimental”).
Overall I don’t think it’s worth it at this point, we can revisit once this becomes more mainstream.

Closing this issue for now as this might take a while to become relevant.

repo: ibhagwan/fzf-lua


text:
处理Webp图片有问题

原图片地址：http://78re52.com1.z0.glb.clouddn.com/resource/Ship.jpg
Webp图片地址：http://78re52.com1.z0.glb.clouddn.com/resource/Ship.jpg?imageView2/2/format/webp
我直接用 YYWebImageManager 类里面的 requestImageWithURL 方法把图片下载下来，发现下载到的Webp图片竟然比原图片大了7倍多！！！！！！
我用 yy_setImageWithURL 方法显示图片，缓存到的图片也是大了7倍多！！！
而我同样用  SDWebImageManager 里面的 downloadImageWithURL 方法下载图片，发现webp图片的大小才正常。
希望可以尽快修复

@ibireme 我看源码里面下载图片用的还是之前的 NSURLConnection, SDWebImage 已经改用NSURLSession.
        // request image from web
        [_lock lock];
        if (![self isCancelled]) {
            _connection = [[NSURLConnection alloc] initWithRequest:_request delegate:[_YYWebImageWeakProxy proxyWithTarget:self]];
            if (![_request.URL isFileURL] && (_options & YYWebImageOptionShowNetworkActivity)) {
                [YYWebImageManager incrementNetworkActivityCount];
            }
        }
        [_lock unlock];

@ibireme 可以参考一下SDWebImage里面对Webp图片的处理，我看它里面只引用了一个头文件 webp/decode.h，方法也挺简洁：
+ (UIImage *)sd_imageWithWebPData:(NSData *)data {
    WebPDecoderConfig config;
    if (!WebPInitDecoderConfig(&config)) {
        return nil;
    }

    if (WebPGetFeatures(data.bytes, data.length, &config.input) != VP8_STATUS_OK) {
        return nil;
    }

    config.output.colorspace = config.input.has_alpha ? MODE_rgbA : MODE_RGB;
    config.options.use_threads = 1;

    // Decode the WebP image data into a RGBA value array.
    if (WebPDecode(data.bytes, data.length, &config) != VP8_STATUS_OK) {
        return nil;
    }

    int width = config.input.width;
    int height = config.input.height;
    if (config.options.use_scaling) {
        width = config.options.scaled_width;
        height = config.options.scaled_height;
    }

    // Construct a UIImage from the decoded RGBA value array.
    CGDataProviderRef provider =
    CGDataProviderCreateWithData(NULL, config.output.u.RGBA.rgba, config.output.u.RGBA.size, FreeImageData);
    CGColorSpaceRef colorSpaceRef = CGColorSpaceCreateDeviceRGB();
    CGBitmapInfo bitmapInfo = config.input.has_alpha ? kCGBitmapByteOrder32Big | kCGImageAlphaPremultipliedLast : 0;
    size_t components = config.input.has_alpha ? 4 : 3;
    CGColorRenderingIntent renderingIntent = kCGRenderingIntentDefault;
    CGImageRef imageRef = CGImageCreate(width, height, 8, components * 8, components * width, colorSpaceRef, bitmapInfo, provider, NULL, NO, renderingIntent);

    CGColorSpaceRelease(colorSpaceRef);
    CGDataProviderRelease(provider);

    UIImage *image = [[UIImage alloc] initWithCGImage:imageRef];
    CGImageRelease(imageRef);

    return image;
}

@ibireme 在类 YYImageCoder 的方法 _updateSourceWebP 里面，本来 _data 的 length 只有 574090, 转化后的 webPData 的 size 也是这个大小，最后到沙盒里面去看缓存到图片竟然有 15.6M ，我觉得问题出在这里

要看缓存的是解压缩前的还是后的，sd目前目前缓存的源文件，每次使用前解压

不一定是bug，只是策略不同

@AbooJan  大神  怎么实现webp文件只播放一次

authors: AbooJan CodeLife2012 Mr-lins

repo: ibireme/YYWebImage


text:
Where to get credentials

Hi,
So I am trying to use this Object Storage in Sydney. I have setup a container but all the tutorials, including the readme here show keys and attributes I cannot seem to find in the interface.
Attributes like - ProjectId,
I have :
Public: https://syd01.objectstorage.softlayer.net/auth/v1.0/
Private: https://syd01.objectstorage.service.networklayer.com/auth/v1.0/
Username: SLOS1307 etc
API Key
xxxxxxxxx
Lots of tutorials also point to auth at https://identity.open.softlayer.com/ which is different from the urls listed above.
I also cannot seem to create storage attached to a service - it's not an option in Sydney.

I found the those attributes on the Bluemix Dashboard->App->Connections panel. Once I had connected the Object Storage service to my Bluemix instance, there's a 'View credentials' button on  the Object Storage icon.

@vespertilian https://ibm-public-cos.github.io/crs-docs/
You are using either IBM COS Cross Region or Cloud Object Storage Regional
This sdk will only work with Object Storage for IBM Bluemix Developer Services which is only available in London and Dallas. You are not seeing the right credentials because the compatible service is unavailable in Sydney

@abaruni Thanks for your answer I believe I am using the Cloud Object Storage Regional. I thought it had the same SWIFT api as Object Storage for IBM Bluemix Developer Services? Is there not a library that I can use to work with storage in Sydney?

@vespertilian they both do use the same (confusingly named) Swift API, but it looks like they use different authentication mechanisms and credentials. I don't believe there is a library that supports Object Storage in Sydney at the moment. This one was created before the introduction of the Cross Region and Regional variants

authors: abaruni rnchamberlain vespertilian


text:
Service abstraction

Initial service abstraction

defines abstract classes for service handlers
defines huggingface service handler which supports huggingface specific conventions
defines model-specific service handles (derived from above handlers) that enables model-specific features

I'll have a look at this tomorrow @wgifford, thanks.

To do items:

[ ] Assess naming, adjust as needed.
[ ] Standardize what is needed in tsfm_config.json. Identify minimum requirements, requirements for HuggingFaceHandler, etc.
[ ] Do we still need a global confing.yaml?
[ ] Allow pulling the tsfm_config.json from HF (just like normal configs).

repo: ibm-granite/granite-tsfm


text:
search controller

search controller is broken on either ios8 or ios9 - I feel best is to just replace it with 3rd party search controller ...

for now - there's an if checking for iOS8/9 and changes the search bar center accordingly

repo: icanzilb/EventBlankApp


text:
🛑 Icarephone is down

In 6deb2da, Icarephone (https://www.icarephone.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Icarephone is back up in 6eac707.

repo: icarephone/upptime


text:
🛑 Icarephone is down

In f491a57, Icarephone (https://www.icarephone.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Icarephone is back up in 44b7026.


text:
@ice/pkg 1.4.1 版本 构建报错roperty '${variables}' of exported interface has or is using private name '${internal object}'.

Describe the bug
@ice/pkg 1.4.1版本报错如下图

版本号锁定至1.4.0正常
Expected behavior
不报错
Actual behavior
No response
Version of ice.js
@ice/pkg 1.4.1
Content of build.json or ice.config.mts
No response
Additional context
No response

自行检查 TS 的类型，本质上是用 tsc 生成类型的

repo: ice-lab/icepkg


text:
add cursor position to other mouse events

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
mouse events except CursorMoved don't return cursor position, mkaing it impossible to know what exactly was clicked
What is the expected behavior?
add more data to mouse events
Version
crates.io release
Operating System
Linux
Do you have any log output?
No response

I am assuming you're writing a custom widget, if that is the case, you can simply query cursor.is_over(layout.bounds()) like so:
    fn on_event(
        &mut self,
        _tree: &mut Tree,
        event: Event,
        layout: Layout<'_>,
        cursor: mouse::Cursor,
        _renderer: &Renderer,
        _clipboard: &mut dyn Clipboard,
        shell: &mut Shell<'_, Message>,
        _viewport: &Rectangle,
    ) -> event::Status {
        match event {
            Event::Mouse(mouse::Event::ButtonPressed(mouse::Button::Left))
            | Event::Touch(touch::Event::FingerPressed { .. }) => {
                let mouse_over = cursor.is_over(layout.bounds());
                if mouse_over {
                    shell.publish((self.click)());
                    return event::Status::Captured;
                }
            }
       }
    }

repo: iced-rs/iced


text:
Gnome icon does not show in task bar

Is there an existing issue for this?

[X] I have searched the existing issues.

Is this issue related to iced?

[X] My hardware is compatible and my graphics drivers are up-to-date.

What happened?
I set the icon, but it does not show up anywhere.
What is the expected behavior?
I expect it to show up as the task bar icon, but it does not. I tried both the latest release and master.
Version
master
Operating System
Linux
Do you have any log output?
Nope. The Gnome version is 42.9.

Also, I didn't get an error.

I used a 128x128 .ico.

This is a duplicate.


text:
🛑 Cravings For Green is down

In b6da551, Cravings For Green (https://cravingsforgreen.nl/) was down:

HTTP code: 500
Response time: 10459 ms

Resolved: Cravings For Green is back up in ea19e23 after 46 minutes.

repo: icheered/uptime


text:
Is the required apache patch available in apache 2.4.33

From README.md:

The module has been backported to Apache 2.4.x branch and will be part of the next release (or is when 2.4.33 is out).

Reading the Apache release notes, I don't see any reference to the required patch for apache 2.4.33.
I see references to mod_md for apache 2.4.30: so, should the above sentence in README.md be the following?

The module has been backported to Apache 2.4.x branch (since Apache 2.4.30).

The Apache release handling is a tad bit broken there. There were interim tags 2.4.30, 2.4.31 which were never made available to the public, but the CHANGES reported did not report all this dead releases together.
And, if people never can download a 2.4.30, it might be confusing to point them there. The first real release people can get with mod_md is 2.4.33. One needs to read the release notes a bit more carefully, unfortunately.

I added some extra stuff to README. I hope it suffices.

Yes, thank you!!

authors: icing mlocati


text:
Adding gemqrt function.

Adding a gemqrt() routine, needed in RandLAPACK.
Code is initially generated via lapackpp/tools/wrapper_gen.py.

Not sure what's causing it to segfault in CI. Will need geqrt in tester, but omitting that shouldn't cause segfaults, it seems.

I was thinking that that is due to the wrong setup of the line in run_tests.py, but seems like something else is the issue.
Also, I noticed that there are no tests for gemqr.

Just tested gemqrt in RandLAPACK and the routine itself works fine.
Looks like something is off with the way I've set up tests.

Hi @mgates3
I see that there is apending change request, but I think I addressed all the issues that were there (unless github is not showing me something for whatever reason).
So just wanted to check if we can merge this PR.

@TeachRaccooon That just means I haven't approved the changes. I'll look at it probably today or tomorrow.

I noticed your fork is specific to this feature (TeachRaccooon/lapackpp-add_gemqrt) and uses the master branch in that fork. That works, but it's usually cleaner to create one fork (say, TeachRaccooon/lapackpp) and create a branch for each specific feature (say, branch gemqrt).

Can you add an empty commit to trigger the CI actions again? The "re-run jobs" button will re-run with the old master, not with the latest master, which seems odd to me.
git commit --allow-empty -m "Empty-Commit"

I'm going to squash all this into one commit when merging, so the empty commit will disappear.

repo: icl-utk-edu/lapackpp


text:
Error in 3.2.0: Typescript appearing in .js file in node_modules.

Hello all,
Our group of programmers experienced failing builds the last coupled days,
while using this library's 3.2.0 version in our dependencies.
Specifically, our error is displayed as:
/frontend/node_modules/@iconify/react/dist/iconify.js:107
  if (data.aliases?.[name2] !== void 0) {
                   ^

Clearly, the line from this iconify.js file is displaying some TypeScript syntax, such as ?. -
this seems to imply that one of the compilation steps for Iconify has been broken.
We downgraded our dependency to 3.1.4, and our build succeeds again.
Can you check your released 3.2.0 code to see if the iconify.js really does contain TS?
You may need to release a repaired 3.2.1 version, if so.
Much obliged, -c4lliope

That's not TypeScript, that's valid JavaScript code: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining
It has been supported by all major browsers for a while. Probably you are using outdated tool in your build process that doesn't handle modern JavaScript well.

Looks like unfortunately quite a lot of developers still use outdated tools, mostly Vue 2 developers that are stuck with old software that is no longer updated since everyone switched to Vue 3.
I've changed code to not use optional chaining. New versions of all icon components will be published within next few hours. To make sure optional chaining doesn't sneak back in, I've added buble in build process for SVG framework, which fails when optional chaining exists in code.
Another change in new version is in icon set validation: old validation function has been replaced with less strict function that reduces component bundle size by quite a lot.

Published new version

repo: iconify/iconify


text:
🛑 Icrop Website is down

In 9e26d39, Icrop Website (https://icrop.com.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Icrop Website is back up in 5dae905.

repo: icroptec/uptime-monitor


text:
ObjectDisposedException at BZip2OutputStream.Finalize()

Uncontrolled cleanup of lost IIS sessions causes a crash.  Finalize should not throw.
Application: w3wp.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ObjectDisposedException
Stack:
at System.IO.__Error.FileNotOpen()
at System.IO.FileStream.Write(Byte[], Int32, Int32)
at System.Security.Cryptography.CryptoStream.Write(Byte[], Int32, Int32)
at System.IO.Stream.WriteByte(Byte)
at ICSharpCode.SharpZipLib.BZip2.BZip2OutputStream.BsW(Int32, Int32)
at ICSharpCode.SharpZipLib.BZip2.BZip2OutputStream.BsPutint(Int32)
at ICSharpCode.SharpZipLib.BZip2.BZip2OutputStream.EndBlock()
at ICSharpCode.SharpZipLib.BZip2.BZip2OutputStream.Dispose(Boolean)
at ICSharpCode.SharpZipLib.BZip2.BZip2OutputStream.Finalize()

Fixed with pull request #69
-Neil

authors: McNeight tdhintz

repo: icsharpcode/SharpZipLib


text:
Add back torso pitch to the ergoCubSN000 model

Hi all, we started using again the torso pitch joint, but the model of the latest release does not have it. Is it possible to add it back to the model? Thanks a lot.
cc @GiulioRomualdi @Nicogene

@isorrentino https://github.com/icub-tech-iit/ergocub-software/pull/153 reenabled the torso_pitch

Thanks a lot @Nicogene

authors: Nicogene isorrentino

repo: icub-tech-iit/ergocub-software


text:
Jimmy fixing ga manual

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
This is related to #1614 but is not the correct solution for it. It should not close it.
What are the significant changes in functionality due to this change request?
raven escapes underscore even in mathematical envs except if there were two escape characters before the _. This is ok except if a mathematical env is expecting \\ for multiline equations. In that case, it will move to the next line and then place an underscore instead of the subscript.
A workaround has been introduced and instead of using an equation env that searches for \\ I had to break the multiline equation into two separate equations to avoid using the \\.
For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

@Jimmy-INL Could you clean up this PR? Right now it includes a lot of other changes from Diego's branch.

This PR was repeated in a cleaner manner

repo: idaholab/raven


text:
Transparency on border radius not working

There is a white background no matter what, how do I remove this?

  button: {
    width: 300,
    height: 60,
    color: '#fff',
    backgroundColor: '#49A8A2',
    borderRadius: 20
  }

try to add {overflow: 'hidden'}

authors: feisan niftylettuce

repo: ide/react-native-button


text:
[FEATURE] Add support for additional libraries

Description
This role may require some additional libraries. Currently, this is not provided.
Why is this needed?
AFAIK, when installing jdbc driver via maven repository, python lxml library is required. The role does not provide a way to install it.

Released in 1.0.1

Released in 1.0.1


text:
Possible to de-dupe a library of 100-500 photos if they are not saved locally?

All of my photos are saved on S3. Is there a way to use this library, or one like it, to identify duplicates?

Currently we don't provide such connectors.

No matter what you’ll need to do egress to read the photos so you might as well download them locally for deduplication

@Joshfindit
Let's say you have an app with 1,000 users. Each has 1,000 photos, some of which are duplicates. All are saved to S3.
How would you go about de-duping?

I probably wouldn’t end up with that because I’d likely have built the app to store files on S3 with some sort of hash (my current go-to is <SHA256>.<size in bytes>).
If I walked in to that as a project I’d:

Plan how user permissions and access will be handled for deduplicated files
Rent a server with enough storage space for all the files
Download and deduplicate in a single batch, tracking the filenames of the dupes
Update the app code
Use the dupe info to “deduplicate” directly on S3
Run confirmation tests

authors: Joshfindit jonathanrstern tanujjain

repo: idealo/imagededup


text:
Share requests session between requests

Currently, a new requests.Session object is created for every request sent. (The requests library does this behind the curtain.) Although the overhead is not too big, it still adds up for lots of repeated calls (e.g. live streaming of rapid changes to a dynamic network).
With this PR, the network client and networks  share a single, persistent requests.Session object, eliminating the overhead of instantiating a new session object for every request.
In the longer term, having a persistent Session object will also make it easier to enable persistent login, user-customized headers, cookies, etc.

@scholer  Thanks for your pull requests and sorry for the very slow response.  All changes you made looks great and will be merged in the next version.

Hi @keiono, thank you for accepting my pull requests - and thanks again for making this great little python package to communicate with Cytoscape =)  💯

authors: keiono scholer


text:
Streamline steps for testing locally

bumps our version to 0.1.1 following our tech preview
adds a new make target run-local with only the steps needed to run the controller locally against your current openshift cluster

/retest

/retest

repo: identitatem/dex-operator


text:
Klick auf Link geht  im Standrad-Browser auf

Reported by Nils:
"Link
geht bei mir die Seite im Standrad-Browser auf (das ist dann Safari)
was blöd ist, man fliegt aus der App raus"

Nils wrote:
Update zum "Link wird in Safari geöffent". Wenn ich die Spiegel App auf dem Handy habe, dann werden Links von Spiegel.de in der App geöffnet. Alle anderen Links klappen so. Ich denke das Problem können wir hinten anstellen

repo: idiomReplaceX/IdiomReplaceX-app


text:
Missing support for rt-require

I'd like to see

rt-require not marked as an unknown attribute.
The RT plugin should accept multiple rt-require divs alongside the root element.
And for extra points: Auto-complete file path parts in rt-require value.

Thanks for all the awesome work!

Sorry, I misread to documentation. Not a bug. Carry on.

repo: idok/react-templates-plugin


text:
什么时候升级到1.8.1啊？

到1.8.1版本了 什么时候升级啊

@stevenliuit 已升.

authors: idoop stevenliuit

repo: idoop/docker-apollo