text:
Protocol Security Negociation Failure

Hello,
I read a lot of similar topics but I get an error trying to connect to a Windows10 host with all updates (through a SSH tunnel)  from a mageia 6 client with all updates. I choose to accept any RDP client on the Windows side (not only NLA). With the same options it works when I connect to a Windows 2008 server (without tunnel).
One year ago (no try since then), I used to work with the same host, an older version of freerdp and with the old syntax, but since then, I updated the versions and I cannot negociate any security protocol. As everything is tunneled, actually I do not need any security between my remote ssh server (mageia 6 with all updates also) and my computer as the connection is on the LAN.
Thanks for your help.
Jérôme.
xfreerdp /u:toto /v:127.0.0.1 /p:33890 /log-level:TRACE
[07:38:26:053] [15776:15777] [DEBUG][com.freerdp.channels.cliprdr.client] - VirtualChannelEntryEx
[07:38:26:053] [15776:15777] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[07:38:26:054] [15776:15777] [INFO][com.freerdp.client.x11] - Property 326 does not exist
[07:38:26:054] [15776:15777] [DEBUG][com.freerdp.client.x11] - Searching for XInput pointer device
[07:38:26:054] [15776:15777] [DEBUG][com.freerdp.client.x11] - Pointer device: 12
[07:38:26:056] [15776:15777] [DEBUG][com.freerdp.core.nego] - Enabling security layer negotiation: TRUE
[07:38:26:056] [15776:15777] [DEBUG][com.freerdp.core.nego] - Enabling restricted admin mode: FALSE
[07:38:26:056] [15776:15777] [DEBUG][com.freerdp.core.nego] - Enabling RDP security: TRUE
[07:38:26:056] [15776:15777] [DEBUG][com.freerdp.core.nego] - Enabling TLS security: TRUE
[07:38:26:056] [15776:15777] [DEBUG][com.freerdp.core.nego] - Enabling NLA security: TRUE
[07:38:26:056] [15776:15777] [DEBUG][com.freerdp.core.nego] - Enabling NLA extended security: FALSE
[07:38:26:056] [15776:15777] [DEBUG][com.freerdp.core.nego] - state: NEGO_STATE_NLA
[07:38:26:056] [15776:15777] [DEBUG][com.freerdp.core.nego] - Attempting NLA security
[07:38:26:056] [15776:15777] [DEBUG][com.freerdp.core.nego] - RequestedProtocols: 3
[07:38:26:056] [15776:15777] [ERROR][com.freerdp.core.transport] - BIO_should_retry returned a system error 32: Relais brisé (pipe)
[07:38:26:056] [15776:15777] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[07:38:26:056] [15776:15777] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
[07:38:26:056] [15776:15777] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure

Enabling TCP forwarding on your SSH server should resolve the 'Broker Pipe' error. Refer an old issue: "Pipe broken #3122"
Also, if that doesn't help, check your client and server algorithm(Ciphers, Macs and KexAlgorithms).

Thanks for the hint. How do I do that (AllowTCPForwarding yes in /etc/ssh/sshd_config ?).
I forgot to tell that the same Windows 10 (as the rdp server) through the same mageia 6 server for the tunnel works perfectly under a windows client environment (tunnel established via cygwin, and windows msttsc.exe rdp client).
My tunnel command is :
ssh -f -o ExitOnForwardFailure=yes -o ServerAliveInterval=240 -C2TNn -L 33890:192.168.2.79:3389 toto@server
It used to work with freerdp 1.x.
Now, my updated freerdp complete command is :
xfreerdp +clipboard +auto-reconnect /rfx /codec-cache:rfx -themes /f /bpp:15 /compression /compression-level:2 /gdi:hw /cert-ignore /sec:tls /u:toto /v:127.0.0.1 /p:33890

And by the way, "Pipe broken #3122" refers to port forwarding, that is obviously working on the remote server (all ssh commands work well, including shell, sftp etc.)

Just to keep you updated, I do not have the broken pipe any more (I do not know why) but still the "Error: protocol security negotiation or connection failure". It works perfectly with remmina... that uses freerdp ! (as far as I know). And remmina is in charge with establishing the ssh tunnel. Weird.

Sounds like you have a local configuration issue.
You're correct that remmina uses freerdp, specially it uses the current master, so the issue can not be in freerdp.

authors: akallabeth cogidis nishkarshjain


text:
FreeRDP fails to build on Windows 10 64-bit with errors referring winpr

Pulling my hair out here. I have been struggling with this for hours.
Describe the bug
FreeRDP fails to build with various errors about winpr includes and undefined types.
To Reproduce
Steps to reproduce the behavior:

Install requirements (OpenSSL 1.1.1d, NASM, ActiveState Perl 5.28.1, OpenH264)
Clone FreeRDP/master
Configure build with
cmake -GNinja -B -DCMAKE_C_COMPILER=path/to/gcc.exe -DCMAKE_CXX_COMPILER=path/to/g++.exe -DCMAKE_INSTALL_PREFIX=build -DOPENSSL_ROOT_DIR=path/to/openssl -DCMAKE_BUILD_TYPE=Release .
cmake --build . --target install

Expected behavior
FreeRDP should build successfully.
Screenshots
Build configure:
Configure-1
Configure-2
Attempt to build:
Build-1
(this goes on and on for a while)
Application details

FreeRDP/master
Command line: x64 Native Tools Command Prompt for VS2017

Desktop:

OS: Windows 10 64-bit

Additional context
All other lights are green, just cannot for the life of me get FreeRDP to build.

We never tried gcc on windows, use the ms compilers.

source: gharchive/issue

authors: akallabeth carsondwilber

repo: FreeRDP/FreeRDP

license_type: permissive

license_source: github-api


text:
Renaming configEMAC_TASK_STACK_SIZE to ipconfigEMAC_TASK_STACK_SIZE_WORDS

Description
As an answer to issue #380, raised by @rpcme the following change:
Rename configEMAC_TASK_STACK_SIZE to the more correct macro name ipconfigEMAC_TASK_STACK_SIZE_WORDS.
It starts with ipconfig, because the user will define it in FreeRTOSIPConfig.h
Also it has the suffix _WORDS, because it defines the stack space in number of words.
configEMAC_TASK_STACK_SIZE used to be defined locally in several versions of NetworkInterface.c. From now on, the default for this macro will be defined in FreeRTOSIPConfigDefaults.h
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run uncrustify

Closing for now as stack size is different for all network interfaces.

source: gharchive/pull-request

repo: FreeRTOS/FreeRTOS-Plus-TCP

license: MIT


text:
C_GetAttributeValue does not set the attribute length in all cases

The attribute length is only set when the pointer is NULL. It should also be set in cases where the buffer is too large or too small.
From PKCS11-base-v2.40:
For each (type, pValue, ulValueLen) triple in the template, C_GetAttributeValue performs the following algorithm:

If the specified attribute (i.e., the attribute specified by the type field) for the object cannot be revealed because the object is sensitive or unextractable, then the ulValueLen field in that triple is modified to hold the value CK_UNAVAILABLE_INFORMATION.
Otherwise, if the specified value for the object is invalid (the object does not possess such an attribute), then the ulValueLen field in that triple is modified to hold the value CK_UNAVAILABLE_INFORMATION.
Otherwise, if the pValue field has the value NULL_PTR, then the ulValueLen field is modified to hold the exact length of the specified attribute for the object.
Otherwise, if the length specified in ulValueLen is large enough to hold the value of the specified attribute for the object, then that attribute is copied into the buffer located at pValue, and the ulValueLen field is modified to hold the exact length of the attribute.
Otherwise, the ulValueLen field is modified to hold the value CK_UNAVAILABLE_INFORMATION.

@sbertin-telular Thanks for the report. I will take a look.

@sbertin-telular
I have created a pull request to address this issue, and I would like to invite you to review the proposed changes to see if they adequately resolve the issue.


text:
UI Docker build for branch and merge pipelines

UI project will need to have a Dockerfile created.
In addition to getting the Dockerfile created and building valid images, GitHub actions will need to be created to build images on each push of a branch and merge to master.

Related to FreeTAKTeam/FreeTakServer#388
Taking assignment for this as this will be completed by this effort

authors: RadioAndrea hickey

repo: FreeTAKTeam/UI


text:
~ Add doc for new shortcut for creating a new window

Doc for

https://github.com/FreeTubeApp/FreeTube/pull/2314
https://github.com/FreeTubeApp/FreeTube/pull/2306

Only merge this after those 2 are merged

Merge #27 first
I will resolve conflicts later

@absidue @efb4f5ff-1298-471a-8973-3d47447115dc @ChunkyProgrammer
Changes rebased~

repo: FreeTubeApp/FreeTube-Docs


text:
🛑 Pivot (Abid) Sekretariat-DJPb is down

In 9caaf17, Pivot (Abid) Sekretariat-DJPb (https://pivot.setditjen-djpb.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pivot (Abid) Sekretariat-DJPb is back up in d5f705f.

repo: FrideyAlpha/uptime-setditjen


text:
🛑 API (DF) Sekretariat-DJPb is down

In cef9c51, API (DF) Sekretariat-DJPb (https://df1.setditjen-djpb.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: API (DF) Sekretariat-DJPb is back up in ca8655c.


text:
🛑 Network is down

In bbf0db0, Network (https://mycloud-jkt.zettagrid.id/tenant/Org_cloud60988) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Network is back up in fbb1d95.


text:
move fixer classes from level subdirs to thematic subdirs

Do we want to remove the level subdirs (contrib/psr1/psr2/symfony)?

:-1:
I don't want to have 100 fixers on one level.
Instead of it I would prefer to have dirs per type of changes, like dir for PhpDoc fixers, dir for phpunit fixers and so on.

Instead of it I would prefer to have dirs per type of changes, like dir for PhpDoc fixers, dir for phpunit fixers and so on.

:+1:

:-1: for this as is

current state: https://github.com/gharlan/PHP-CS-Fixer/tree/remove-level-subdirs/src/Fixer
is this the right direction?

I assume that *_ are not-moved-yet fixers.
I like that direction.

Also, at the end, I would move FixerInterface and Abstract*Fixer into Fixer dir as well.

I assume that *_ are not-moved-yet fixers.

yes

all classes are moved now: https://github.com/gharlan/PHP-CS-Fixer/tree/remove-level-subdirs/src/Fixer
please discuss.. :)

Can we not get away with Return rather than ReturnNotation since php surely only reserves the class Return, not the namespace?

Same for the others, like Array.

Could we move the abstract phpdoc fixers into the phpdoc namespace?

I'm :+1: on the way this PR is moving btw.

Can we not get away with Return rather than ReturnNotation since php surely only reserves the class Return, not the namespace?

https://3v4l.org/1RWsD

Sigh. I guess I didn't think about how tokenization would work.

Maybe some new namespace like BlankLine, with:

NoBlankLinesAfterPhpdocFixer (ReturnNotation)
BlankLineBeforeReturnFixer.php (ReturnNotation)
?

Also, 3 of 4 Fixers from Semicolon are more about whitespaces, not semicolon.

:+1:

Thank you @gharlan.

:+1:  very nice :)

authors: GrahamCampbell SpacePossum gharlan keradus

repo: FriendsOfPHP/PHP-CS-Fixer


text:
NoBlankLinesAfterPhpdocFixer — Do not strip newline between docblock and use statements

When a docblock is followed by a use statement, it is most likely a file-level docblock. File-level docblocks should be followed by a newline as per the phpDoc standard: https://docs.phpdoc.org/getting-started/your-first-set-of-documentation.html
Example:
<?php
/**
 * Some license info.
 */

use Foo\Bar;

/**
 * My class.
 */
class MyClass
...

Thanks for creating the PR @mollierobbert  :+1:
Could you target your PR to 2.15? that is the lowest supported branch ATM and since we merge upstream from it your fix will end up by as many releases/users as possible

Thanks @SpacePossum. I wouldn't know how to do that in GitHub. I created a new PR targeted to 2.15: #4712

authors: SpacePossum mollierobbert


text:
[DOCUMENTATION] Issue on tag name for custom sorter

I think that there is a typo issue in the documentation :
https://github.com/FriendsOfSymfony/FOSCommentBundle/blob/master/Resources/doc/14-customizing_tree_sorting.md
At the end of the actual doc :
services:
    acme_comment.sorter.my_sort:
        class: Acme\CommentBundle\Sorting\AcmeOrderSorting
        tags:
            - { name: acme_comment.sorter, alias: my_sort }

I think the last line should be :
            - { name: fos_comment.sorter, alias: my_sort }

Can you send a PR fixing things ? This way you will get attribution for the fix

OK, will do that

Fixed in https://github.com/FriendsOfSymfony/FOSCommentBundle/pull/485

authors: XWB jmaquet stof

repo: FriendsOfSymfony/FOSCommentBundle


text:
Adds localization

Introduced the "sharpsite_" prefix for the translations of the engine itself. Think this might come in handy as soon as people can start developing plugins.

i think the html-tag in the app.razor and others should perhaps also be adapted to the localization so that the pages are correctly captured by a crawler. here is an example for a german page:
<html xml:lang="de" lang="de" dir="ltr">

No clue on how to do that, but go for it if you like

Let's open a secondary issue to attach the xml:lang and dir attributes.  With the server-side rendered capabilities of the framework, we probably need a varyBy to ensure that the localized versions of the pages are cached independently of each other

authors: MdeBruin93 csharpfritz deepx

repo: FritzAndFriends/SharpSite


text:
B2B-1281 upgrade to link token usage

fixes: https://front-finance.atlassian.net/browse/B2B-1281

@afzalahmad-front Seems like this change would not maintain backwards compatibility, since the url parameter is taking the linkToken value.
We should implement this so, that both of them can be used, but the url property is marked as obsolete.

authors: afzalahmad-front balint-front


text:
https://nix.fuel.network/ doesn't work

the link in here https://github.com/FuelLabs/fuel.nix doesn't work

Thanks for the report 👌

It is now operational.

authors: andreolf kayagokalp


text:
chore: simplify E2E test

The purpose of the E2E test is to ensure compatibility with the current live testnet. IMO the real value here is testing that the transaction format is valid, not the encoding format of the call data. If that was the case, we should be testing for all types, rather than the struct vec setup we currently have.
Therefore, as we are currently facing issues with running out of funds on our test address, we should simplify this test to minimise it's fund consumption.
This PR reduces gas consumption of the E2E test from 51326 to 1226.

[...] IMO the real value here is testing that the transaction format is valid...

I agree. Should we then have (simple) e2e tests involving all transaction types with all types of programs? It can be a follow-up PR but can be done in this PR as well, afaic.

@nedsalk agreed however more txs will mean more gas, and part of the reason here is to reduce gas consumption for the e2e wallet 😬  Will do as follow up once we've resolved the wallet draining with the bridge or something.

@danielbate yeah, but it'll still be significantly less than what we spend now given that the tests will be simple. We'll get more tests while spending 5-10x less gas in the end.

authors: danielbate nedsalk

repo: FuelLabs/fuels-ts


text:
fix: make the second param in produceBlocks optional, add docs for block production

Summary

The second param timeParameters in the produceBlocks helper was required until now. This is now an optional param, in line with the GQL API and the Rust SDK.
Added a page for block production to our docs.

Closes #912

@arboleya My rationale behind putting this new page under Testing and choosing that title was consistency with the Rust SDK: https://rust.fuel.network/v0.41.0/testing/chains.html
That aside, I do feel like this section should fall under Testing because it covers a feature that lets people force-produce blocks which is something someone would only usually do when testing things out. This is not something they can do on a 'real' network.
I do feel like Producing Blocks would be a better title than Tweaking the Blockchain, though - at least until we have more features related to tweaking the blockchain.

@Dhaiwat10 Make sense, and thanks for the explanations.


text:
Bump all applications

Type of change

Improvement (refactoring, restructuring repository, cleaning tech debt, ...)

Changes
The following apps have been updated to forc 0.60.0, fuel core 0.26.0, fuels 0.62.0

[x] airdrop
[x] AMM
[x] counter-script
[x] DAO
[x] english-auction
[x] escrow
[x] fractional-NFT
[x] fundraiser
[ ] multisig-wallet (this will be updated in a different pr)
[x] name-registry
[x] native-asset
[x] NFT
[x] oracle
[x] OTC-swap-predicate
[x] TicTacToe
[x] timelock

Re-running CI as the DAO app was skipped, otherwise lgtm

repo: FuelLabs/sway-applications


text:
memcpyopt is removing store and not updating subsequent opcodes

We found a case where memcpyopt removes a store but it does not updates subsequent instructions, for example, using the ir_generation tests:
script;

pub trait Power {
    fn pow(self, exponent: u32) -> Self;
}

impl Power for u256 {
    fn pow(self, exponent: u32) -> Self {
        let one = 0x0000000000000000000000000000000000000000000000000000000000000001u256;

        if exponent == 0 {
            return one;
        }

        let mut exp = exponent;
        let mut base = self;
        let mut acc = one;

        while exp > 1 {
            if (exp & 1) == 1 {
                acc = acc * base;
            }
            exp = exp >> 1;
            base = base * base;
        }

        acc * base
    }
}

fn main(a: u256) -> u256 {
    0x00000000000000000000000000000000000000000000000000000000u256.pow(10);
    a % 0x00000000000000000000000000000000000000000000000000000001u256
}

// ::check-ir::
// check: main

// ::check-ir-optimized::
// pass: o1
// pass: fuel
// check: main

This will enable all "o1" and "fuel" optimization passes.
Just before memcpyopt we have the below IR which is running the "wide mod" instruction on u256s and returning its result.
>         wide mod v44, v45, v46 to v47, !49
>         v48 = load v47, !49
>         store v48 to v0
>         ret ptr u256 v0

after memcpyopt we have
>         wide mod a, v45, v46 to v47, !44
>         v48 = load v47, !44
>         ret ptr u256 v0

The store is gone, but we are still returning v0 and not v48.
see https://github.com/FuelLabs/sway/tree/xunilrj/memcpyopt-bug for the reproducing code.

The store is gone, but we are still returning v0 and not v48.

This is because v0 has now been changed to v0 = get_local ptr u256, __wide_result1 and v47 also is v47 = get_local ptr u256, __wide_result1, !45, i.e., the same variable.
So we're returning a pointer to the source of what was load+store., thus eliminating the copy.
Are you seeing an actual issue with the result value?

The fact that we're returning a pointer to a local stack variable seems odd to me. Let me dig in.

The fact that we're returning a pointer to a local stack variable seems odd to me. Let me dig in.

And this seems to be explained by this:
https://github.com/FuelLabs/sway/blob/910e33bd015e2ea4571e042a856a0cd5c910b93a/sway-ir/src/optimize/ret_demotion.rs#L40
so overall seems like "not a bug" to me.

I will take a look at this again, because we have a very strange behavior happening in one version, but not on another.

I will take a look at this again, because we have a very strange behavior happening in one version, but not on another.

@xunilrj any update on this?

None. I will ask who reported the bug to try again. In the meantime let us close this.

authors: vaivaswatha xunilrj

repo: FuelLabs/sway


text:
__log outputting encoded values

Description
This PR changes the output of __log to encoded values (see https://github.com/FuelLabs/sway/issues/4769). A quick example of what that means is
struct S {
    a: u64,
    b: u32,
    c: u16,
    d: u8,
    e: Vec<u64>,
    f: str,
    g: u256
}

let mut e = Vec::new();
e.push(1);
e.push(2);
e.push(3);

__log(S{
    a: 1,
    b: 2,
    c: 3,
    d: 4,
    e,
    f: "sway",
    g: u256::max()
});

will output
 [0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 2, 0, 3, 4, 0, 0, 0, 0, 0, 0, 0, 3, 0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 2, 0, 0, 0, 0, 0, 0, 0, 3, 0, 0, 0, 0, 0, 0, 0, 4,    115,   119,    97,   121, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255, 255]
  ^^^^^^^^^^^^^^^^^^^^^^  ^^^^^^^^^^  ^^^^  ^  ^^^^^^^^^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^^^^^^^^     ^^^    ^^^     ^^    ^^^  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                     s.a         s.b   s.c s.d              s.e.len()                  s.e[0]                  s.e[1]                  s.e[2]               s.f.len()  s.f[0] s.f[1] s.f[2] s.f[3]  s.g

This works in two steps:
1 - __log(s) is desugared into __log(encode(s));
2 - call encode. Its impl can be found at https://github.com/FuelLabs/sway/pull/5306/files#diff-ee5cebc963e841e8af05f3986de17dd266ee6e9b49dbe089a5eb64764f3b802eR307
It simply creates an append-only buffer and call abi_encode from a special trait named AbiEncode.
To be encodable, a type must implement AbiEncode. In the example above, S is auto-implemented by the compiler because all its fields are AbiEncode. But we can also have custom impl like Vec here: https://github.com/FuelLabs/sway/pull/5306/files#diff-b5d9688741fea479477f26ca44cd1d1ecbd2f003f3875292abb23df7fad85c58
Issues
1 - Currently is needed to import core::codec::* everywhere, which is painful, but at least, the error message is nice:
error: Trait is not imported
  --> /home/xunilrj/github/sway/examples/identity/src/main.sw:57:9
   |
...
57 |         require(
   |         ^^^^^^^ Trait "AbiEncode" is not imported into "main.sw" when calling "require".
   |         ------- help: This import is needed because "require" requires "AbiEncode" in one of its trait constraints.
   |         ------- help: Import the "AbiEncode" trait into "main.sw" by using: `use core::codec::AbiEncode;`.
   |
  ::: /home/xunilrj/github/sway/sway-lib-std/src/revert.sw:59:8
   |
...
59 |     T: AbiEncode
   |        --------- info: In the definition of "require", "AbiEncode" is used in this trait constraint.
   |
____

2 - Arrays, string arrays and tuples will have limited implementations. Currently up to five items.
3 - Some unrelated functions now demand arguments to implement AbiEncode because they call log under the hood: assert_eq, require, etc...
Relevant code changes

sway-core/src/asm_generation/fuel/fuel_asm_builder.rs

After encoding the object, we are going to log a slice to the generated buffer. Now the slice arrives at the ASM generation as ptr slice because of a demotion pass. Which, in the end, was being treated as  ptr and was being logged with LOGD(ptr, len).
Now I correctly identify that a slice was logged and LOGD(...) the data of the slice.

sway-core/src/semantic_analysis/ast_node/declaration/declaration.rs

The fn auto_impl_abi_encode is where auto implementation happens. The current implementation just call abi_encode on each field following declaration order.

sway-lib-core/src/codec.sw

This is the implementation needed to encode objects. We have a general fn encode that can encode anything that can be encoded. This is the fn that will be called auto-magically where we decide to use the encoding.
This file also contains all the default implementation for abi_encode. Currently, just for u64, but we will have impl for all standard data types here.
The Buffer is a ultra-simplified version of Bytes. The idea is just a simple append-only dynamic array.

test/src/e2e_vm_tests/test_programs/should_pass/language/logging/src/main.sw

Is the example of the user actually using the encoding:
__log( encode(s));

is the desugared version of log (done here: https://github.com/FuelLabs/sway/pull/5306/files#diff-dd8f23cc5406f8b442080cbce96df8616c62d1a4ec57ce2a37d6125651edf09aR1776)
Checklist

[ ] I have linked to any relevant issues.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have updated the documentation where relevant (API docs, the reference, and the Sway book).
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
[ ] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[ ] I have requested a review from the relevant team or maintainers.

Some tests are breaking because of https://github.com/FuelLabs/sway/issues/5383. The problem is that when we generate the auto impl, it ends up  resolving to the wrong types.

The task to test std-lib does not work, because it depends on the SDK parsing the log correctly. Something we still need to do.

I'm not sufficiently familiar with most of the code being touched here, so I don't feel comfortable giving a review a such.
I did want to raise the issue of whether it's possible to go from the log output back to the data? The type of the data doesn't seem to be part of the encoding, so to map the log back to the data it came from you would need to supply the types separately.

whether it's possible to go from the log output back to the data?

Only look at the bytes... no.
For that, and specifically for logging, you will have to look ate the ABI JSON.
"loggedTypes": [
    {
      "logId": 0,
      "loggedType": {
        "name": "",
        "type": 5,
        "typeArguments": []
      }
    },
    ...

The test that test this is the one broken because we need to update the Rust SDK. What we do in that test is we run a macro on top on this JSON that "recreate" all the types and give you easy access to typed logged data.

authors: jjcnn xunilrj


text:
chore: fix some comments

Description
fix some comments
Checklist

[ ] I have linked to any relevant issues.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have updated the documentation where relevant (API docs, the reference, and the Sway book).

[ ] If my change requires substantial documentation changes, I have requested support from the DevRel team

[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
[ ] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[ ] I have requested a review from the relevant team or maintainers.

Thanks

authors: sdankel toofooboo


text:
🛑 Home Assistant is down

In 3fa2141, Home Assistant (https://ha.fussel.tv) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Home Assistant is back up in e236eb9 after 12 minutes.

repo: FusselTV/status


text:
ISSUE: Adding additional locks but no Status in the Overview Lock Dashboard

Describe the bug
I am unable to view the locked status of any of the child locks added to Keymaster in the overview dashboard. The necessary entities do not seem to exist in ymal in order to add them to the dashboard.
Environment (please complete the following information):

OS: [e.g. HassOS13.1 / HACore 2024.8.3]
Type of system that HA is running on: NUC / Oracle VM VirtualBox
Home Assistant version: [e.g. 0.105.5]
Hassio/Docker/Core? No
Component version: 0.98 ?
Z-Wave integration name: zwave_js
Lock make and model: Kwikset Home Connect 620

Logs
2024-09-01 08:18:06.059 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration keymaster which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-01 08:18:06.062 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-01 08:18:06.064 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration blueiris which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2024-09-01 08:18:20.350 WARNING (MainThread) [homeassistant.components.heos] 10.0.0.33 is not logged in to a HEOS account and will be unable to retrieve HEOS favorites: Use the 'heos.sign_in' service to sign-in to a HEOS account
2024-09-01 08:18:21.535 WARNING (MainThread) [homeassistant.helpers.frame] Detected that custom integration 'blueiris' calls async_forward_entry_setup for integration, blueiris with title: Coventry and entry_id: XXXXXXXXXXXXXXXXX, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/blueiris/managers/home_assistant.py, line 121: await load(self._config_manager.config_entry, domain), please create a bug report at https://github.com/elad-bar/ha-blueiris/issues
2024-09-01 08:18:23.892 WARNING (MainThread) [slixmpp.stringprep] Using slower stringprep, consider compiling the faster cython/libidn one.
2024-09-01 08:18:24.503 ERROR (MainThread) [homeassistant.components.device_tracker] Platform mobile_app does not generate unique IDs. ID XXXXXXXXXXXXXXXXXXXXX already exists - ignoring device_tracker.teds_13_pro
2024-09-01 08:18:25.123 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Backyard TV' for androidtv_remote integration could not authenticate: Need to pair again
2024-09-01 08:18:30.397 ERROR (MainThread) [custom_components.keymaster.binary_sensor] Z-Wave integration not found
2024-09-01 08:18:30.397 WARNING (MainThread) [homeassistant.components.binary_sensor] Platform keymaster not ready yet: None; Retrying in background in 30 seconds

... truncated a bunch of issues with blueiris not of concern here ...
Screenshots
As seen here for the first and parent lock, the entity: lock.front_door_lock shows the status.

Not only does it not show in the child locks, the entity doesn't seem to even exist. In other words, I cannot find an entity called lock.laundry_room_door_lock or lock.master_bedroom_lock

Additional context
Add any other context about the problem here.
Please add emails in plain/text format if possible and applicable.

Make sure the files have generated in your packages directory.

The Package is there:

Which I copy/pasted to here:

`title: master_bedroom_door Codes and Configuration
path: keypad-master_bedroom_door
icon: mdi:lock-smart
panel: false
badges:

input_text.master_bedroom_door_lockname
input_text.master_bedroom_door_front_door_parent
input_boolean.master_bedroom_door_lock_notifications
input_boolean.master_bedroom_door_dooraccess_notifications
input_boolean.master_bedroom_door_garageacess_notifications
type: entity
entity: lock.boltchecked_master_bedroom_door_lock
entity: binary_sensor.fake
entity: input_text.keymaster_master_bedroom_door_autolock_door_time_day
entity: input_text.keymaster_master_bedroom_door_autolock_door_time_night
entity: input_boolean.keymaster_master_bedroom_door_autolock
entity: timer.keymaster_master_bedroom_door_autolock
cards:
type: vertical-stack
cards:

content: |
Code 1
type: markdown
type: entities
show_header_toggle: false
entities:

entity: input_text.master_bedroom_door_name_1
entity: input_text.master_bedroom_door_pin_1
entity: input_boolean.enabled_master_bedroom_door_1
entity: input_boolean.notify_master_bedroom_door_1
type: divider
entity: input_boolean.override_parent_master_bedroom_door_1
type: divider
entity: sensor.connected_master_bedroom_door_1
state_color: true
entity: binary_sensor.active_master_bedroom_door_1
state_color: true
type: custom:fold-entity-row
head:
type: section
label: Advanced Options
entities:

entity: input_boolean.reset_codeslot_master_bedroom_door_1
type: divider
entity: input_boolean.accesslimit_master_bedroom_door_1
entity: input_number.accesscount_master_bedroom_door_1
type: custom:numberbox-card
icon: mdi:key-variant
speed: 250
type: divider
entity: input_boolean.daterange_master_bedroom_door_1
entity: input_datetime.start_date_master_bedroom_door_1
entity: input_datetime.end_date_master_bedroom_door_1
type: custom:fold-entity-row
head:
type: section
label: Custom Weekdays
entities:

input_boolean.sun_master_bedroom_door_1
input_boolean.sun_inc_master_bedroom_door_1
input_datetime.sun_start_date_master_bedroom_door_1
input_datetime.sun_end_date_master_bedroom_door_1
type: divider
input_boolean.mon_master_bedroom_door_1
input_boolean.mon_inc_master_bedroom_door_1
input_datetime.mon_start_date_master_bedroom_door_1
input_datetime.mon_end_date_master_bedroom_door_1
type: divider
input_boolean.tue_master_bedroom_door_1
input_boolean.tue_inc_master_bedroom_door_1
input_datetime.tue_start_date_master_bedroom_door_1
input_datetime.tue_end_date_master_bedroom_door_1
type: divider
input_boolean.wed_master_bedroom_door_1
input_boolean.wed_inc_master_bedroom_door_1
input_datetime.wed_start_date_master_bedroom_door_1
input_datetime.wed_end_date_master_bedroom_door_1
type: divider
input_boolean.thu_master_bedroom_door_1
input_boolean.thu_inc_master_bedroom_door_1
input_datetime.thu_start_date_master_bedroom_door_1
input_datetime.thu_end_date_master_bedroom_door_1
type: divider
input_boolean.fri_master_bedroom_door_1
input_boolean.fri_inc_master_bedroom_door_1
input_datetime.fri_start_date_master_bedroom_door_1
input_datetime.fri_end_date_master_bedroom_door_1
type: divider
input_boolean.sat_master_bedroom_door_1
input_boolean.sat_inc_master_bedroom_door_1
input_datetime.sat_start_date_master_bedroom_door_1
input_datetime.sat_end_date_master_bedroom_door_1

type: vertical-stack
cards:

content: |
Code 2
type: markdown
type: entities
show_header_toggle: false
entities:

entity: input_text.master_bedroom_door_name_2
entity: input_text.master_bedroom_door_pin_2
entity: input_boolean.enabled_master_bedroom_door_2
entity: input_boolean.notify_master_bedroom_door_2
type: divider
entity: input_boolean.override_parent_master_bedroom_door_2
type: divider
entity: sensor.connected_master_bedroom_door_2
state_color: true
entity: binary_sensor.active_master_bedroom_door_2
state_color: true
type: custom:fold-entity-row
head:
type: section
label: Advanced Options
entities:

entity: input_boolean.reset_codeslot_master_bedroom_door_2
type: divider
entity: input_boolean.accesslimit_master_bedroom_door_2
entity: input_number.accesscount_master_bedroom_door_2
type: custom:numberbox-card
icon: mdi:key-variant
speed: 250
type: divider
entity: input_boolean.daterange_master_bedroom_door_2
entity: input_datetime.start_date_master_bedroom_door_2
entity: input_datetime.end_date_master_bedroom_door_2
type: custom:fold-entity-row
head:
type: section
label: Custom Weekdays
entities:

input_boolean.sun_master_bedroom_door_2
input_boolean.sun_inc_master_bedroom_door_2
input_datetime.sun_start_date_master_bedroom_door_2
input_datetime.sun_end_date_master_bedroom_door_2
type: divider
input_boolean.mon_master_bedroom_door_2
input_boolean.mon_inc_master_bedroom_door_2
input_datetime.mon_start_date_master_bedroom_door_2
input_datetime.mon_end_date_master_bedroom_door_2
type: divider
input_boolean.tue_master_bedroom_door_2
input_boolean.tue_inc_master_bedroom_door_2
input_datetime.tue_start_date_master_bedroom_door_2
input_datetime.tue_end_date_master_bedroom_door_2
type: divider
input_boolean.wed_master_bedroom_door_2
input_boolean.wed_inc_master_bedroom_door_2
input_datetime.wed_start_date_master_bedroom_door_2
input_datetime.wed_end_date_master_bedroom_door_2
type: divider
input_boolean.thu_master_bedroom_door_2
input_boolean.thu_inc_master_bedroom_door_2
input_datetime.thu_start_date_master_bedroom_door_2
input_datetime.thu_end_date_master_bedroom_door_2
type: divider
input_boolean.fri_master_bedroom_door_2
input_boolean.fri_inc_master_bedroom_door_2
input_datetime.fri_start_date_master_bedroom_door_2
input_datetime.fri_end_date_master_bedroom_door_2
type: divider
input_boolean.sat_master_bedroom_door_2
input_boolean.sat_inc_master_bedroom_door_2
input_datetime.sat_start_date_master_bedroom_door_2
input_datetime.sat_end_date_master_bedroom_door_2

type: vertical-stack
cards:

content: |
Code 3
type: markdown
type: entities
show_header_toggle: false
entities:

entity: input_text.master_bedroom_door_name_3
entity: input_text.master_bedroom_door_pin_3
entity: input_boolean.enabled_master_bedroom_door_3
entity: input_boolean.notify_master_bedroom_door_3
type: divider
entity: input_boolean.override_parent_master_bedroom_door_3
type: divider
entity: sensor.connected_master_bedroom_door_3
state_color: true
entity: binary_sensor.active_master_bedroom_door_3
state_color: true
type: custom:fold-entity-row
head:
type: section
label: Advanced Options
entities:

entity: input_boolean.reset_codeslot_master_bedroom_door_3
type: divider
entity: input_boolean.accesslimit_master_bedroom_door_3
entity: input_number.accesscount_master_bedroom_door_3
type: custom:numberbox-card
icon: mdi:key-variant
speed: 250
type: divider
entity: input_boolean.daterange_master_bedroom_door_3
entity: input_datetime.start_date_master_bedroom_door_3
entity: input_datetime.end_date_master_bedroom_door_3
type: custom:fold-entity-row
head:
type: section
label: Custom Weekdays
entities:

input_boolean.sun_master_bedroom_door_3
input_boolean.sun_inc_master_bedroom_door_3
input_datetime.sun_start_date_master_bedroom_door_3
input_datetime.sun_end_date_master_bedroom_door_3
type: divider
input_boolean.mon_master_bedroom_door_3
input_boolean.mon_inc_master_bedroom_door_3
input_datetime.mon_start_date_master_bedroom_door_3
input_datetime.mon_end_date_master_bedroom_door_3
type: divider
input_boolean.tue_master_bedroom_door_3
input_boolean.tue_inc_master_bedroom_door_3
input_datetime.tue_start_date_master_bedroom_door_3
input_datetime.tue_end_date_master_bedroom_door_3
type: divider
input_boolean.wed_master_bedroom_door_3
input_boolean.wed_inc_master_bedroom_door_3
input_datetime.wed_start_date_master_bedroom_door_3
input_datetime.wed_end_date_master_bedroom_door_3
type: divider
input_boolean.thu_master_bedroom_door_3
input_boolean.thu_inc_master_bedroom_door_3
input_datetime.thu_start_date_master_bedroom_door_3
input_datetime.thu_end_date_master_bedroom_door_3
type: divider
input_boolean.fri_master_bedroom_door_3
input_boolean.fri_inc_master_bedroom_door_3
input_datetime.fri_start_date_master_bedroom_door_3
input_datetime.fri_end_date_master_bedroom_door_3
type: divider
input_boolean.sat_master_bedroom_door_3
input_boolean.sat_inc_master_bedroom_door_3
input_datetime.sat_start_date_master_bedroom_door_3
input_datetime.sat_end_date_master_bedroom_door_3

type: vertical-stack
cards:

content: |
Code 4
type: markdown
type: entities
show_header_toggle: false
entities:

entity: input_text.master_bedroom_door_name_4
entity: input_text.master_bedroom_door_pin_4
entity: input_boolean.enabled_master_bedroom_door_4
entity: input_boolean.notify_master_bedroom_door_4
type: divider
entity: input_boolean.override_parent_master_bedroom_door_4
type: divider
entity: sensor.connected_master_bedroom_door_4
state_color: true
entity: binary_sensor.active_master_bedroom_door_4
state_color: true
type: custom:fold-entity-row
head:
type: section
label: Advanced Options
entities:

entity: input_boolean.reset_codeslot_master_bedroom_door_4
type: divider
entity: input_boolean.accesslimit_master_bedroom_door_4
entity: input_number.accesscount_master_bedroom_door_4
type: custom:numberbox-card
icon: mdi:key-variant
speed: 250
type: divider
entity: input_boolean.daterange_master_bedroom_door_4
entity: input_datetime.start_date_master_bedroom_door_4
entity: input_datetime.end_date_master_bedroom_door_4
type: custom:fold-entity-row
head:
type: section
label: Custom Weekdays
entities:

input_boolean.sun_master_bedroom_door_4
input_boolean.sun_inc_master_bedroom_door_4
input_datetime.sun_start_date_master_bedroom_door_4
input_datetime.sun_end_date_master_bedroom_door_4
type: divider
input_boolean.mon_master_bedroom_door_4
input_boolean.mon_inc_master_bedroom_door_4
input_datetime.mon_start_date_master_bedroom_door_4
input_datetime.mon_end_date_master_bedroom_door_4
type: divider
input_boolean.tue_master_bedroom_door_4
input_boolean.tue_inc_master_bedroom_door_4
input_datetime.tue_start_date_master_bedroom_door_4
input_datetime.tue_end_date_master_bedroom_door_4
type: divider
input_boolean.wed_master_bedroom_door_4
input_boolean.wed_inc_master_bedroom_door_4
input_datetime.wed_start_date_master_bedroom_door_4
input_datetime.wed_end_date_master_bedroom_door_4
type: divider
input_boolean.thu_master_bedroom_door_4
input_boolean.thu_inc_master_bedroom_door_4
input_datetime.thu_start_date_master_bedroom_door_4
input_datetime.thu_end_date_master_bedroom_door_4
type: divider
input_boolean.fri_master_bedroom_door_4
input_boolean.fri_inc_master_bedroom_door_4
input_datetime.fri_start_date_master_bedroom_door_4
input_datetime.fri_end_date_master_bedroom_door_4
type: divider
input_boolean.sat_master_bedroom_door_4
input_boolean.sat_inc_master_bedroom_door_4
input_datetime.sat_start_date_master_bedroom_door_4
input_datetime.sat_end_date_master_bedroom_door_4

type: vertical-stack
cards:

content: |
Code 5
type: markdown
type: entities
show_header_toggle: false
entities:

entity: input_text.master_bedroom_door_name_5
entity: input_text.master_bedroom_door_pin_5
entity: input_boolean.enabled_master_bedroom_door_5
entity: input_boolean.notify_master_bedroom_door_5
type: divider
entity: input_boolean.override_parent_master_bedroom_door_5
type: divider
entity: sensor.connected_master_bedroom_door_5
state_color: true
entity: binary_sensor.active_master_bedroom_door_5
state_color: true
type: custom:fold-entity-row
head:
type: section
label: Advanced Options
entities:

entity: input_boolean.reset_codeslot_master_bedroom_door_5
type: divider
entity: input_boolean.accesslimit_master_bedroom_door_5
entity: input_number.accesscount_master_bedroom_door_5
type: custom:numberbox-card
icon: mdi:key-variant
speed: 250
type: divider
entity: input_boolean.daterange_master_bedroom_door_5
entity: input_datetime.start_date_master_bedroom_door_5
entity: input_datetime.end_date_master_bedroom_door_5
type: custom:fold-entity-row
head:
type: section
label: Custom Weekdays
entities:

input_boolean.sun_master_bedroom_door_5
input_boolean.sun_inc_master_bedroom_door_5
input_datetime.sun_start_date_master_bedroom_door_5
input_datetime.sun_end_date_master_bedroom_door_5
type: divider
input_boolean.mon_master_bedroom_door_5
input_boolean.mon_inc_master_bedroom_door_5
input_datetime.mon_start_date_master_bedroom_door_5
input_datetime.mon_end_date_master_bedroom_door_5
type: divider
input_boolean.tue_master_bedroom_door_5
input_boolean.tue_inc_master_bedroom_door_5
input_datetime.tue_start_date_master_bedroom_door_5
input_datetime.tue_end_date_master_bedroom_door_5
type: divider
input_boolean.wed_master_bedroom_door_5
input_boolean.wed_inc_master_bedroom_door_5
input_datetime.wed_start_date_master_bedroom_door_5
input_datetime.wed_end_date_master_bedroom_door_5
type: divider
input_boolean.thu_master_bedroom_door_5
input_boolean.thu_inc_master_bedroom_door_5
input_datetime.thu_start_date_master_bedroom_door_5
input_datetime.thu_end_date_master_bedroom_door_5
type: divider
input_boolean.fri_master_bedroom_door_5
input_boolean.fri_inc_master_bedroom_door_5
input_datetime.fri_start_date_master_bedroom_door_5
input_datetime.fri_end_date_master_bedroom_door_5
type: divider
input_boolean.sat_master_bedroom_door_5
input_boolean.sat_inc_master_bedroom_door_5
input_datetime.sat_start_date_master_bedroom_door_5
input_datetime.sat_end_date_master_bedroom_door_5
`

Repairs in Notifications:

Example of what one of them says:

But I think that is because I haven't completed the setup of Pushover but am not sure.

Well, the Master Bedroom Door Lock seems to be set up correctly but somehow I borked the Laundry Room Door Lock. I may exclude it and start over but does the configuration.ymal need to be manually edited to completely remove it?

nothing needs to be edited to remove it

I added another kwikset and I can't get the damn thing to set the handing and it won't stay connected to the network. It is closer than the front door but maybe there's intference. I put in a plug in Zooz zen07 up high centrally located and told Z-Wave js to reconfigure the network. Still no connection to two locks. I suppose I need more nodes but am using a Zooz 800 series lr usb stick?

If all you have are the locks, then you don't actually have a mesh for routing. More powered nodes the better.

If all you have are the locks, then you don't actually have a mesh for routing. More powered nodes the better.

True dat!
I'll get more installed. I know this is an issue for sure, especially for the Laundry Room Lock because there's a 2 foot thick solid masonry fireplace along the entire wall between the family room and the laundry room and nothing is getting through that so I have to route around it.
I have a new issue. I removed the lock called Guest Bathroom Door from Z-Wave JS but it showed back up as "Node 6" with no information. I'm not sure how to properly exclude it and include it again. It should connect though because the Hub is in a room across the hall and it is closer than the Front Door Lock. There is, however, a tile shower in between. I'll put a powered node in between today and see what that does.

Not sure what I've done now but need to restore from a saved backup.. How to do that? Or is there another thing I should do?

Your addon isn't running.

Talk to me like I'm stupid! 😂
I'm brand noob to HA from Vera.
How do I make it run?

I don't know, I don't use HAOS, you'll need to ask on their Discord.

I will do that. Thank you for your help so far!

I don't know, I don't use HAOS, you'll need to ask on their Discord.

I got it cleared out. Adding ZUI over J-Wave JS is a process and I didn't read the instructions. In case anybody else comes across this issue, the solution is here:
https://community.home-assistant.io/t/cannot-connect-to-host-core-zwave-js-3000-ssl-default/376164/31?u=sammy2

Now that that's fixed back to the original programming..
One of my Z-Wave Locks is non responsive.  I suspect it is due to its location in the Laundry Room which is behind a massive masonry fireplace which is the width of the family room and full height of the wall too. I think this log tells the story but am not sure.
2024-09-03T18:04:42.550Z DRIVER   all queues idle 2024-09-03T18:05:12.495Z DRIVER   all queues busy 2024-09-03T18:05:12.503Z SERIAL » 0x0103003bc7                                                         (5 bytes) 2024-09-03T18:05:12.509Z DRIVER » [REQ] [GetBackgroundRSSI] 2024-09-03T18:05:12.528Z SERIAL « [ACK]                                                                   (0x06) 2024-09-03T18:05:12.539Z SERIAL « 0x0107013ba3a1a1a6c7                                                 (9 bytes) 2024-09-03T18:05:12.543Z SERIAL » [ACK]                                                                   (0x06) 2024-09-03T18:05:12.560Z DRIVER « [RES] [GetBackgroundRSSI]                                     channel 0: -93 dBm                                     channel 1: -95 dBm                                     channel 2: -95 dBm                                     channel 3: -90 dBm 2024-09-03T18:05:12.571Z DRIVER   all queues idle 2024-09-03T18:05:42.500Z DRIVER   all queues busy 2024-09-03T18:05:42.508Z SERIAL » 0x0103003bc7                                                         (5 bytes) 2024-09-03T18:05:42.510Z DRIVER » [REQ] [GetBackgroundRSSI] 2024-09-03T18:05:42.534Z SERIAL « [ACK]                                                                   (0x06) 2024-09-03T18:05:42.540Z SERIAL « 0x0107013ba4a3a3a9cf                                                 (9 bytes) 2024-09-03T18:05:42.543Z SERIAL » [ACK]                                                                   (0x06) 2024-09-03T18:05:42.545Z DRIVER « [RES] [GetBackgroundRSSI]                                     channel 0: -92 dBm                                     channel 1: -93 dBm                                     channel 2: -93 dBm                                     channel 3: -87 dBm 2024-09-03T18:05:42.551Z DRIVER   all queues idle 2024-09-03T18:06:12.500Z DRIVER   all queues busy 2024-09-03T18:06:12.507Z SERIAL » 0x0103003bc7                                                         (5 bytes) 2024-09-03T18:06:12.510Z DRIVER » [REQ] [GetBackgroundRSSI] 2024-09-03T18:06:12.527Z SERIAL « [ACK]                                                                   (0x06) 2024-09-03T18:06:12.533Z SERIAL « 0x0107013ba3a1a1a6c7                                                 (9 bytes) 2024-09-03T18:06:12.538Z SERIAL » [ACK]                                                                   (0x06) 2024-09-03T18:06:12.542Z DRIVER « [RES] [GetBackgroundRSSI]                                     channel 0: -93 dBm                                     channel 1: -95 dBm                                     channel 2: -95 dBm                                     channel 3: -90 dBm 2024-09-03T18:06:12.548Z DRIVER   all queues idle 2024-09-03T18:06:23.582Z CNTRLR » [Node 004] pinging the node... 2024-09-03T18:06:23.591Z DRIVER   all queues busy 2024-09-03T18:06:23.609Z SERIAL » 0x010f00a90001000401002500000000a3db                                (17 bytes) 2024-09-03T18:06:23.630Z DRIVER » [Node 004] [REQ] [SendDataBridge]                                   │ source node id:   1                                   │ transmit options: 0x25                                   │ callback id:      163                                   └─[NoOperationCC] 2024-09-03T18:06:23.654Z SERIAL « [ACK]                                                                   (0x06) 2024-09-03T18:06:23.657Z SERIAL « 0x010401a90152                                                       (6 bytes) 2024-09-03T18:06:23.661Z SERIAL » [ACK]                                                                   (0x06) 2024-09-03T18:06:23.666Z DRIVER « [RES] [SendDataBridge]                                     was sent: true 2024-09-03T18:06:34.618Z SERIAL « 0x011d00a9a301044c007f7f7f7f7f00010600000000420702047f7f7f7f7fe5    (31 bytes) 2024-09-03T18:06:34.622Z SERIAL » [ACK]                                                                   (0x06) 2024-09-03T18:06:34.631Z DRIVER « [REQ] [SendDataBridge]                                     callback id:            163                                     transmit status:        NoAck, took 11000 ms                                     routing attempts:       7                                     protocol & route speed: Z-Wave, 40 kbit/s                                     routing scheme:         Resort to Direct                                     TX channel no.:         1                                     beam:                   1000 ms                                     route failed here:      2 -> 4 2024-09-03T18:06:34.645Z CNTRLR   [Node 004] The node did not respond after 1 attempts, it is presumed dead 2024-09-03T18:06:34.653Z CNTRLR   [Node 004] ping failed: The node did not acknowledge the command (ZW0204) 2024-09-03T18:06:34.656Z CNTRLR   [Node 004] Cannot rebuild routes because the node is not responding. 2024-09-03T18:06:34.659Z DRIVER   all queues idle 2024-09-03T18:06:42.503Z DRIVER   all queues busy 2024-09-03T18:06:42.520Z SERIAL » 0x0103003bc7                                                         (5 bytes) 2024-09-03T18:06:42.522Z DRIVER » [REQ] [GetBackgroundRSSI] 2024-09-03T18:06:42.545Z SERIAL « [ACK]                                                                   (0x06) 2024-09-03T18:06:42.549Z SERIAL « 0x0107013ba6a5a5abcf                                                 (9 bytes) 2024-09-03T18:06:42.554Z SERIAL » [ACK]                                                                   (0x06) 2024-09-03T18:06:42.556Z DRIVER « [RES] [GetBackgroundRSSI]                                     channel 0: -90 dBm                                     channel 1: -91 dBm                                     channel 2: -91 dBm                                     channel 3: -85 dBm 2024-09-03T18:06:42.561Z DRIVER   all queues idle 2024-09-03T18:07:12.503Z DRIVER   all queues busy 2024-09-03T18:07:12.509Z SERIAL » 0x0103003bc7                                                         (5 bytes) 2024-09-03T18:07:12.511Z DRIVER » [REQ] [GetBackgroundRSSI] 2024-09-03T18:07:12.521Z SERIAL « [ACK]                                                                   (0x06) 2024-09-03T18:07:12.528Z SERIAL « 0x0107013ba3a0a0a6c7                                                 (9 bytes) 2024-09-03T18:07:12.536Z SERIAL » [ACK]                                                                   (0x06) 2024-09-03T18:07:12.538Z DRIVER « [RES] [GetBackgroundRSSI]                                     channel 0: -93 dBm                                     channel 1: -96 dBm                                     channel 2: -96 dBm                                     channel 3: -90 dBm 2024-09-03T18:07:12.544Z DRIVER   all queues idle 2024-09-03T18:07:42.504Z DRIVER   all queues busy 2024-09-03T18:07:42.512Z SERIAL » 0x0103003bc7                                                         (5 bytes) 2024-09-03T18:07:42.514Z DRIVER » [REQ] [GetBackgroundRSSI] 2024-09-03T18:07:42.551Z SERIAL « [ACK]                                                                   (0x06) 2024-09-03T18:07:42.557Z SERIAL « 0x0107013ba7a2a2a8cd                                                 (9 bytes) 2024-09-03T18:07:42.561Z SERIAL » [ACK]                                                                   (0x06) 2024-09-03T18:07:42.563Z DRIVER « [RES] [GetBackgroundRSSI]                                     channel 0: -89 dBm                                     channel 1: -94 dBm                                     channel 2: -94 dBm                                     channel 3: -88 dBm 2024-09-03T18:07:42.569Z DRIVER   all queues idle
I will work towards more house-powered nodes to get the signal there but in the meantime what is this log telling me? It is from right after attempting to rebuild the routes the in this devices page in HA.

2024-09-03T18:06:34.645Z CNTRLR   [Node 004] The node did not respond after 1 attempts, it is presumed dead
2024-09-03T18:06:34.653Z CNTRLR   [Node 004] ping failed: The node did not acknowledge the command (ZW0204)
2024-09-03T18:06:34.656Z CNTRLR   [Node 004] Cannot rebuild routes because the node is not responding.

Your node isn't on the network there for no commands can be sent to it, you'll have to fix your mesh before HA/ZwaveJS can talk to the lock.

Circling Back to report my locks are all set up and working. I had to move my NUC / Controller to a high location more central in my house and put in a wired repeater to help route around a massive masonry fireplace that goes from the floor to above the roof and is about 2 or more feet thick and the full width of the wall separating the Family Room from the Laundry Room to get the lock between the laundry room and garage to show up on the network.
Very pleased thus far with Keymaster and now I need to set up notifications so I know when certain people are coming through the locks and into my house.

repo: FutureTense/keymaster


text:
Pi 3 Display Issues with HDMI to RGB adapter

Describe the bug or issue
When using a HDMI to rgb adapter, the initial setup display is illegible. nothing can be made out
Describe your setup

RPi 3b
Chromium r92r1
hdmi to rgb adapter

Closed per TL:DR;:

You are asking about issues about a 3rd-party app, a non-standard peripheral device or a special setup that does not benefit the general community

authors: fydeos-alpha ghostyroasty


text:
model-viewer HTML Component for 3D and AR

Google spent a lot of time on the topic of augmented reality and mentioned the upcoming <model-viewer> HTML element. It does not appear to be supported in even Chrome Canary yet, but as it gains support it'd be nice to see where it can be used.
https://developers.google.com/web/updates/2019/02/model-viewer
https://developers.google.com/web/updates/2019/05/model-viewer-ar

As mentioned in that article, the model-viewer element is a custom element (you can tell based on the hyphen). So no native browser support, it requires support for Custom Elements. Looks like it also requires a few other things listed here: https://googlewebcomponents.github.io/model-viewer/#section-browser-support

TIL, thanks.

authors: Fyrd chrisblakley

repo: Fyrd/caniuse


text:
Fix code coverage

#22 (again)
First commit has no tests working.

mhm... I'm going to close this one and re-do the same idea on master instead.


text:
Atualizar Rails para versão 5.2.1

Atualizar Rails para versão 5.2.1
Esta mudança traz as funcionalidades do ActiveStorage, que permite o upload de arquivos sem o uso de gems.

Issue desnecessária


text:
Fixed bug with hanging loading screen when a couchDbView model is used.

Bug was caused by an out of scope variable being de-incremented.
fix #880

This pull request is related to issue #871

repo: GCRC/nunaliit


text:
Roles should be stripped from layer JSON

Roles should be stripped from locale and or layer JSON.
I have updated the the utility method docs.

The notIncludesNegatedRole should be unnested and documented.
https://github.com/GEOLYTIX/xyz/pull/1708/commits/234f709528ba76732d0ae43fe00988274ab98d57

repo: GEOLYTIX/xyz


text:
Fixes #32 - Add option to pass in lm to ArrDescrInit

I create an ArrDescr in my NUOPC code and need to pass lm to it

There is only one other place in the code that uses this routine; restart_interp.F90 uses it in FVDyCoreCubed/. And I think having lm is the right decision because lm_world exists in the structure but isn't filled by this subroutine.

repo: GEOS-ESM/MAPL


text:
Feature/jedi var bc sprint update

Description
Updated atmospheric observational configurations and the script to create new satellite and aircraft bias correction coefficient files. All tests in swell-ufo_testing pass when geoval files are generated  on-the-fly.
Note: All archived satbias and geoval files need to be re-generated by SWELL, or tests in other Swell test suites fail because of those files are out of date once the JEDI team merge updates made within VarBC-sprint.
Dependencies on JEDI various feature/VarBC-sprint PRs in UFO, IODA, and IODACONV

[x] waiting on https://github.com/JCSDA-internal/ufo/pull/3015
[x] waiting on https://github.com/JCSDA-internal/ioda-converters/pull/1357
[x] waiting on https://github.com/JCSDA-internal/ioda/pull/1092

Impact:
Other Swell test suits need new satbias, and likely new geoval, files.

I only had to update the satbias files, geovals are up-to-date already. Tier 1 tests pass with the new JEDI version and this branch.
@rtodling FYI, files in R2D2/Shared/gsi/bc are updated, might break some of your workflows.

repo: GEOS-ESM/swell


text:
Default case ordering and implicit fallthrough in switch statements in vk_mem_alloc.h

In vk_mem_alloc.h, the out-of-order positioning of the default case in switch statements triggers an implicit fallthrough static error in addition to being, in my opinion, less readable and intuitive. These cases are:

Line 11269
Line 11765
Line 13011
Line 13314
Line 13353
Line 13426
Line 13515
Line 13562
Line 13649
Line 13740
Line 13781
Line 13819
Line 13843
Line 13926

Thank you for these suggestions. I refactored some of the switch statements you mentioned.
However, for more complex control flow, I don't think that making the code longer and more complicated is worth it. Implicit fallthrough is an error only if you treat warnings as errors, while documentation of this library clearly states in chapter "Features not supported":

Code free of any compiler warnings. Maintaining the library to compile and work correctly on so many different platforms is hard enough. Being free of any warnings, on any version of any compiler, is simply not feasible. There are many preprocessor macros that make some variables unused, function parameters unreferenced, or conditional expressions constant in some configurations. The code of this library should not be bigger or more complicated just to silence these warnings. It is recommended to disable such warnings instead.

authors: adam-sawicki-a jeremy-cowham

license: mit

license_source: bigquery


text:
New OS Support

Currently MIVisionX is supported only for CentOS 7.8 and below. Latest CentOS 8.0 release support required.

Currently MIVisionX is supported only for Ubuntu 18.04 and below. Latest Ubuntu 20.04 LTS release support required.

Dockers Created

Ubuntu 20.04 - https://hub.docker.com/r/kiritigowda/ubuntu-20.04

CentOS 8.1 - https://hub.docker.com/r/kiritigowda/centos-8.1

Ubuntu 20.04 - Supported with warnings with TOT MIVisionX

MIVisionX is now supported on Ubuntu 20.04 & CentOS 8 with a few compilation warnings. See issue #292

@paveltc & @LakshmiKumar23 can you verify this issue with above-provided dockers.

New OS supported with a few warnings, Bugs are open for the warnings.


text:
Register Parameter names in Gpflow

Feature request
When creating a Parameter, e.g an Inducing Point, gpflow sets tf.Variable( value, name = None) name to None. In this way we cannot track parameters later on by looping over model.trainable_variables.
This is clearly a tensorflow problem, since in my opinion it should define a name automatically. For example in pytorch if name is not specified then Pytorch uses class name (nn.Module) to set a name for parameters.
Motivation
Track parameters. An example could be the case in which you want to use two different optimizers for different parameters. For example in Deep Kernel Learning we might wanna use SGD for the Neural Network (since SGD usually performs better on these models) and then use Adam for the GP part.
Also another motivation would be to use different learning rates or optimization schedulings ( for example natural gradients for variational parameters and LBGFS for hyperparameters)
Another motivation could be for setting parameters to be non trainable without having to reference them directly (i.e can be done in a loop filtering by name).
The only way we can do this at the moment is by directly adding the parameters to a list manually, i.e variable_list.append( model.kernel.trainable_variables ), which in my opinion is tedious as we filtering by name in a loop seems easier and more dynamic.
Solution:
The solution is quite simple. For example in the svgp code we can just replace:
q_mu = np.zeros((num_inducing, self.num_latent_gps)) if q_mu is None else q_mu
        self.q_mu = Parameter(q_mu, dtype=default_float())  # [M, P]

        if q_sqrt is None:
            if self.q_diag:
                ones = np.ones((num_inducing, self.num_latent_gps), dtype=default_float())
                self.q_sqrt = Parameter(ones, transform=positive())  # [M, P]
            else:
                q_sqrt = [
                    np.eye(num_inducing, dtype=default_float()) for _ in range(self.num_latent_gps)
                ]
                q_sqrt = np.array(q_sqrt)
                self.q_sqrt = Parameter(q_sqrt, transform=triangular())  # [P, M, M]
        else:
            if q_diag:
                assert q_sqrt.ndim == 2
                self.num_latent_gps = q_sqrt.shape[1]
                self.q_sqrt = Parameter(q_sqrt, transform=positive())  # [M, L|P]
            else:
                assert q_sqrt.ndim == 3
                self.num_latent_gps = q_sqrt.shape[0]
                num_inducing = q_sqrt.shape[1]
                self.q_sqrt = Parameter(q_sqrt, transform=triangular())  # [L|P, M, M]

to
q_mu = np.zeros((num_inducing, self.num_latent_gps)) if q_mu is None else q_mu
        self.q_mu = Parameter(q_mu, dtype=default_float(), name = 'svgp_variational_mean')  # [M, P]

        if q_sqrt is None:
            if self.q_diag:
                ones = np.ones((num_inducing, self.num_latent_gps), dtype=default_float())
                self.q_sqrt = Parameter(ones, transform=positive(), name = 'svgp_variational_covariance')  # [M, P]
            else:
                q_sqrt = [
                    np.eye(num_inducing, dtype=default_float()) for _ in range(self.num_latent_gps)
                ]
                q_sqrt = np.array(q_sqrt)
                self.q_sqrt = Parameter(q_sqrt, transform=triangular(),  name = 'svgp_variational_covariance')  # [P, M, M]
        else:
            if q_diag:
                assert q_sqrt.ndim == 2
                self.num_latent_gps = q_sqrt.shape[1]
                self.q_sqrt = Parameter(q_sqrt, transform=positive(),  name = 'svgp_variational_covariance')  # [M, L|P]
            else:
                assert q_sqrt.ndim == 3
                self.num_latent_gps = q_sqrt.shape[0]
                num_inducing = q_sqrt.shape[1]
                self.q_sqrt = Parameter(q_sqrt, transform=triangular(), name = 'svgp_variational_covariance')  # [L|P, M, M]

Note that at the moment Gpflow allows the user to pass in a name argument when creating different instances like kernels, or inducing points. But then these names are not use to register the parameters, which in my opinion is something we could fix for a better usage of Gpflow.

This would be great, and in fact GPflow 1 had its own parameter-tracking system that did give names by default, but I think it'd be a significant amount of work to get this working in a consistent way across all of GPflow... would probably require a bit of upfront discussion how to actually do it.

authors: jmaronas st--

repo: GPflow/GPflow


text:
Dimension dismatch

#when input dimension is 2 or larger, the following error comes up. why the input dimension can not be larger than 1?

return func(*args, **kwargs)
File "D:\Anaconda111\lib\site-packages\gpflow\utilities\ops.py", line 122, in square_distance  *
dist = -2 * tf.tensordot(X, X2, [[-1], [-1]])
ValueError: Dimensions must be equal, but are 1 and 2 for '{{node Tensordot/MatMul}} = MatMul[T=DT_DOUBLE, transpose_a=false, transpose_b=false](truediv_1, Tensordot/transpose)' with input shapes: [15,1], [2,100].

Tensor shape mismatch.
Function: GPR_deprecated.init
Declared: D:\Anaconda111\lib\site-packages\gpflow\models\gpr.py:57
Argument: data
Index: [0]
Expected: [N, D]
Actual:   [15, 2]
Index: [1]
Expected: [N, P]
Actual:   [15]
Argument: noise_variance
Expected: []
Actual:
)


text:
fillAllDiagnosticsGhosts fails for NUM_DIAGNOSTIC_VARS > NUM_VARS

m_patcher is defined with NUM_VARS vars and can be reused for the diagnostics provided NUM_DIAGNOSTIC_VARS < NUM_VARS.
Since in some fixed background simulations this is not the case it we should create a specific m_patcher for the diagnostics, otherwise fillAllDiagnosticsGhosts (called in the AMRInterpolator) fails with an angry error message about accessing too many vars.

Would you be able to provide the file and line number of the failed assertion?

It is :
Chombo/lib/src/BoxTools/BaseFabImplem.H:392: Assertion `a_destcomp >= 0 &     & a_destcomp+a_numcomp <= m_nvar' failed. !!!

authors: KAClough mirenradia

repo: GRChombo/GRChombo


text:
Wrong volume displayed

Currently only displays the volume up to 25 and no higher

duplicated #37

authors: Hurstiii Songkeys


text:
🛑 beSIGN is down

In 0d6ce06, beSIGN (https://rst.besign.app) was down:

HTTP code: 502
Response time: 291 ms

Resolved: beSIGN is back up in 39775cd after 9 minutes.

repo: GSoftbiz/upptime


text:
Fix Last visit time column ordering

I'm not quite sure this is working correctly, kind of confusing right now so it's probably wrong :)
could be related to #3 too.

When opening "History Browser" for the first time the ordering is correctly sorted by Last Visit Time.
However when clicking on another column to change to another ordering and then selecting Last Visit Time the ordering is broken.

authors: GabLeRoux jrobichaud

repo: GabLeRoux/webextensions-history-browser


text:
Can't resolve module

Using Expo 51
Solved changing package.json to:
"main": "./dist/module/index.js"

Ok I will look the problem


text:
[BUG] MA crops and Farmer w/bonemeal

you can use bonemeal in the farmer to grow MA crops. should only be able to use fertilizer on MA crops.

Fixed as of 1.9.15 which will be released shortly, thanks for reporting!

repo: GabrielOlvH/Industrial-Revolution


text:
Feature Request: Auto generate the graphQL string including the API key for BTC Pay Server Integration

Is your feature request related to a problem? Please describe.
When creating a link between BTC Pay Server and Blink via graphQL to setup a lightning node; copying and pasting the API
key into the network configuration is a huzzle considering the string needs to be manualy adjust to get the correct format and it's easy to make a mistake or have a typo.
You have to recreate this:

and then add the API key:

Describe the solution you'd like
My suggestion would be to add a button that auto generate the graphQL string including the API key that can just be copied from the Blink Dashboard and Pasted on the BTC Server Side... This will make it a one step process and eliminate possible mistakes...

that can then just be pasted here in the correct string format:

Describe alternatives you've considered
///...
Additional context
///...

the copy graphql string would be for btcpay server only, right? so it should be more a copy settings for btcpay server?

probably need to be on the previous screen, because we don't show the key anymore on the screen you have screenshoted @ThinusXpressed

the copy graphql string would be for btcpay server only, right? so it should be more a copy settings for btcpay server?

Correct!

probably need to be on the previous screen, because we don't show the key anymore on the screen you have screenshoted @ThinusXpressed

This would be fine as long as the correctly combined graphQL + API Key is generated and copied to the clipboard.

this has been deployed

authors: ThinusXpressed nicolasburtey

repo: GaloyMoney/galoy


text:
[mood] ability to strip moods from the binary at build time

I'm not 100% sure how i'd want it to be impl the interface for it, but some people are concerned about the more spicy mood strings being in the binary, so it would be nice to have a way to maybe do like --no-default-features and have only chill mode.
The only place that really needs to change is here:
https://github.com/Gankra/cargo-mommy/blob/aa7801b3a69d789d52a72436c94cfdd8c6fe6e12/build.rs#L40C15-L56
break up the string formatting into several iterative steps, then disable the ones you don't want in the binary (forget if build.rs makes reading features messy).

I'll look into this, from what I can tell you can just use cfg! inside a build.rs (https://stackoverflow.com/a/66843072), so I'm thinking having
[features]
# This affects if a given response is *supported* in the built binary,
# not if it's enabled by default
default = ["chill", "thirsty", "yikes"]

chill = []
thirsty = []
yikes = []

Haven't tested if cfg! works to read features, but they're definitely at least exposed as envars, which wouldn't be too bad to read, and the installation method would be like cargo install cargo-mommy --no-default-features -F chill. (nixpkgs could probably just expose it as overridable options? not entirely sure how package config works there).

I think we should just always have chill on (it's the default mode, stuff assumes it exists) although "mommy has no chill build" is extremely funny as a premise.

Makes sense, yeah. Simply not emitting the yikes/thirsty moods into the binary works except for DENIGRATING_TERMS_DEFAULT/MOMMYS_PARTS_DEFAULT, which are only used in thirsty/yikes (and show up in the binary).
Two options I can see are to either just have them exist but be blank strings, so anything that tries to use them should just panic (but that would be a responses.json or library bug), or cfg out the parsing code. I'm leaning towards the latter, so DENIGRATING_TERM showing up in a chill template string would simply not be replaced, as if it wasn't a placeholder.
Though it does seem somewhat fragile, better tests to make sure that placeholders aren't used in the wrong moods can be future work IMO.
I'll make the error message for an unknown mood say which moods cargo-mommy was installed with, to help track down "why isn't thirsty working, did I typo it or was it just not packaged with it?" Maybe stick it in --version too.

repo: Gankra/cargo-mommy


text:
#174 Update styles.css

Issues Identification
Closes: #(issue number)
Description
Summary
Provide a brief description of what this pull request does and why it is needed.
Details
Include any detailed information about the changes in this pull request.
Types of Changes
Please check the boxes that apply

[ ] Bugfix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Please check the boxes that apply

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] My changes do not break the current system and pass all existing test cases
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Screenshots
If applicable, please attach screenshots of the changes made to the user interface.
Additional Information
Please provide any other information that is relevant to this pull request.

closes #174

@Piyushsahu99 write pr properly this is the last time Im explaining i cant explain every individual You dont have to copy paste any templet write what you do add ss and issue no

@Piyushsahu99 refer this https://github.com/GarimaSingh0109/Resum-Resume/pull/362


text:
Use compiler_error on nightly

On stable it leaves the usual non-friendly random compiler error.

Coverage remained the same at 87.824% when pulling 887ba19dc0a777aa50bd1b4a2121462c46969466 on lu-zero:master into 091129df1a90b9c4aff45e456c7b7ba10c766652 on Geal:master.

authors: coveralls lu-zero

repo: Geal/nom


text:
🛑 Bitwarden is down

In 8148cfa, Bitwarden ($BITWARDEN_URL) was down:

HTTP code: 530
Response time: 225 ms

Resolved: Bitwarden is back up in 0d6fb9e.

repo: GeekCornerGH/status-page


text:
Change letter spacing inside input

Hi! Is this possible to do?

Can you explain more on this

@SupriyaKalghatgi Inside of a TextInput, is it possible to increase the spacing in between the letters?

@rostyys Yes

authors: SupriyaKalghatgi rostyys

repo: GeekyAnts/NativeBase


text:
make transcript writes enabled off be "sticky"

Every time I login, I see markedly slow performance with the first browser I try to open.  So I have to wait for it to finish, go back to the transcript, and unset the make transcript writes enabled option.
I'd like this setting to be remembered or have some way to set it to default to off.

I've added two ways to do this.  In theory this could be a way to hold client & server post login preferences.
Client:

In the Jadeite working directory, add a file called Jadeite.prefs with contents transcriptEnabled false  That should turn off your transcripts by default. fyi - this is the only command understood in this file right now.
Server:
As part of the work for #132 I added a server post login hook. Commit a block as such then login:
UserGlobals at: #JadeitePreferences put: [RowanAnsweringService new turnOffTranscriptWrites]

In theory, we need to have both client & server post login execution available, so that's why I added both.
Added in Oscar 3.0.26

The Jadeite.prefs doesn't work. Verified working directory: is the syntax correct?

The UserGlobals key system does work as expected.

@LisaAlmarode  It appears that the method in JadeitePreferences was stripped out - a perpetual frustration with Dolphin. But I added a sender to the method and it seemed to stick around in the .exe. Fixed in 3.0.27.

authors: LisaAlmarode ericwinger

repo: GemTalk/Jadeite


text:
All my forms still expire

I have set my 'drip-interval' => 59000 and my sessions 'lifetime' => env('SESSION_LIFETIME', 1),
but my form still expires. I have a search box on every page.
How can I properly test this. I am not that experienced with phpunit so I do not know how to test using your tests.
Expected Behavior
Not expire
Acutal Behavior
Expire
Environment

PHP Version: 7.1
Laravel Version: 5.5
LaravelCaffeine Version:0.6.2

Stack Trace
No stack trace. I don't know how to debug this

+1, been using this package up to last week with no issues, today, in a new clean install, it doesn't inject the JS in the website, just doesn't work

Thanks for reporting! Have either of you published the configuration file prior to updating to 0.6? The conf settings have changed, which might account for this problem. I will take a look and see what else might be affecting this. @MarcosBL can you provide all the version info as well (os, PHP, Laravel, package) to help give a better understanding? Thanks!

Mine was a fresh 5.5 install yesterday. I had the issue before generating the config file. I only generated it so I could change the milliseconds for testing, but got the same result.

Try setting the drip interval to 5000 for testing, instead of 59000. Let me know how that goes.

Same here, fresh 5.5 Laravel install, issue before publishing, tried to publish to debug, saw the new format. I have a meta with the csrf token, had no forms, but inyected an empty one in the layout just to be sure: same thing, no JS inyected at all before , no matter wich interval in config file.
As soon as I downgrade to 0.5.0, everything starts working fine
Sys info: Linux Mint 18.3 / Laravel 5.5 / PHP 7.0.22 / Apache 2.4.18

@MarcosBL can you post the page code that you are testing on? I want to see if I can replicate your exact situation. Thanks :)

Is your page continuously refreshing, instead of dripping?

I have tested it on my end in a brand new blank laravel project, and it is continuously dripping. Here is my blade file that I used to test:
@extends('layouts.app')

@section('content')
    <form method="post">
        {{ csrf_field() }}
        <input type="hidden" name="success" value="true">
        <input type="submit" value="Test Form Submit">
    </form>
@endsection

It is important that your session lifetime is greater than your drip interval, otherwise it wont work.

Also, are you still registering the package in the providers array of your app config? If so, it needs to be removed in L5.5 and up, as it will auto-register.

I just set 'drip-interval' => 5000 and 'lifetime' => env('SESSION_LIFETIME', 1) and it appears to be working now. I'm not sure if Chrome was caching anything?
Can you tell me how I can see this in console? Should it be seen in the network tab? Or is there any other way to monitor it firing?

I would recommend keeping the session at the default 120 (or something larger than 5). setting it to 1 is not a realistic (only useful for testing) value and can result in strange behavior.
To inspect the drips, I look at the resources tab. You should see a new drip request every 5 seconds with your current setup.

No I wont be using those settings. I was just testing.
I am sorry but had a hectic day yesterday. I can no longer confirm I have it working. I am uninstalling to test without now.
I cannot see the resources tab in chrome. Where is that hidden? I thought it may be the network tab?

So sorry for my mistake yesterday. It's still not working for me. I tried to make it expire, but for some reason I couldn't. I don't know if laravel or chrome was caching anything or what was going on, but today after uninstalling, I finally for it to expire (very confusing) After a fresh install of caffeine just now, I confirm it is not working for me.
I am looking in the network tab for the drip every 5 seconds but am not seeing it. Where exactly do I see the drip and what does it say? is it a js file? an url? I have no idea what to look for?

Here are the other packages installed in Laravel. Maybe there is a conflict?

"require": {
    "php": ">=7.0.0",
    "barryvdh/laravel-debugbar": "^3.1",
    "barryvdh/laravel-ide-helper": "^2.4",
    "barryvdh/laravel-snappy": "^0.4.0",
    "fideloper/proxy": "~3.3",
    "genealabs/laravel-caffeine": "^0.6.2",
    "gloudemans/shoppingcart": "^2.4",
    "guzzlehttp/guzzle": "^6.3",
    "h4cc/wkhtmltopdf-amd64": "^0.12.3",
    "intervention/image": "^2.4",
    "laravel/framework": "5.5.*",
    "laravel/tinker": "~1.0",
    "maatwebsite/excel": "~2.1.0",
    "rydurham/sentinel": "^2.7",
    "sentry/sentry-laravel": "^0.8.0",
    "snowfire/beautymail": "^1.0",
    "spatie/laravel-backup": "^5.1"
},

Im having difficulties debugging this. Now when I set my session value back to 120 it still expires within the minute. Is this a chrome issue? I've noticed lately that I need to clear my cache more often when editing CSS. And even sometimes clearing the cache does not work, I have open the css file in the browser and then click refresh for the new css rules to be seen.

Are you checking for the drip on pages that have form? It will only drip if there is a form on the page, and the csrf-token is also on the page (either as meta tag or hidden field).

Sorry for the late response, made a fast debug and found shouldRegisterGlobalMiddleware function returning false in my app.
All checks pass, but php_sapi_name (apache2handler in my situation) and app('env') (local in my situation. I think that's the problem, the logic in that function, that didn't exists in the previous release. Does this help ?
My session lifetime is the default 120, and muy config is:
return [
    'drip-interval' => 300000,
    'domain' => null,
    'route' => 'genealabs/laravel-caffeine/drip',
    'outdated-drip-check-interval' => 2000,
    'use-route-middleware' => false,
];

A simple return true; in that line injects the JS correctly in my template, so I assume the problem is on those checks. Injected code:

<script>
    let lastCheck = new Date();
    const caffeineSendDrip = function () {
        const ajax = window.XMLHttpRequest
            ? new XMLHttpRequest
            : new ActiveXObject('Microsoft.XMLHTTP');

        ajax.onreadystatechange = function () {
            if (ajax.readyState === 4 && ajax.status === 204) {
                lastCheck = new Date();
            }
        };

        ajax.open('GET', '/genealabs/laravel-caffeine/drip');
        ajax.setRequestHeader('X-Requested-With', 'XMLHttpRequest');
        ajax.send();
    }

    setInterval(function () {
        caffeineSendDrip();
    }, 300000);

    if (2000 > 0) {
        setInterval(function () {
            if (new Date() - lastCheck >= 7082000) {
                location.reload(true);
            }
        }, 2000);
    }
</script>

Just my 2 cents

Ah!!!!! That's the missing link, I completely forgot to handle Apache. Could you try version 0.6.3 to see if the fix works?
Thanks!

Composer-updated and working fine, first try :+1:
Thanks !

@warmwhisky did this fix it for you as well?

Sorry I was busy... Yep all sorted now. I can see the drip!
Thanks so much!

Awesome, sorry I forgot about Apache use-case. Thanks for sticking with the debugging and helping get it sorted out :)

authors: MarcosBL mikebronner warmwhisky

repo: GeneaLabs/laravel-caffeine


text:
Problem with Halo Sky Tools

There's a bug in Halo Sky Tools that says it's looking for a list of floats and finding a color instead.  I'm using Blender 2.93 on Windows 10, and I'm using the default scene with no unit measurement.
You can replicate this by using the default scene and clicking on Generate Sky.

Well that's embarrassing. Should be fixed by the time tools drop.

@DLDrago Is this an issue with the latest tools?


text:
Exporting a list of features that go into the .h5 file after munging

Please make sure that this is a feature request.
System information

GenoML version (you are using): v1.5
Are you willing to contribute it (Yes/No): Yes

Suggested by @h-leonard (thanks, Hampton!)
Describe the feature and the current behavior/state.
Currently, when munging, only a file with features and approximate relative importance is exported. This is only exported when using the --feature_selection flag, and features that contribute nothing are reported at the bottom with a score of 0.
...But what if you just wanted a list of features that made it to the *.dataForML.h5 file without having to open Python to read in and print out column names that remain in the final munged file?
Suggested feature request would output a list of features to a text file that is made automatically when munging, and updated when/if the --feature_selection flag is present
Will this change the current api? How?
Nope!
Who will benefit with this feature?
Everyone who needs to go through and make sure the right features are being used.
Any Other info.
N/A

Moved issue to new repo for completeness and consistency


text:
🛑 AI flowise is down

In 43e1364, AI flowise (https://aiflow.crushing.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AI flowise is back up in 4c42e4f after 18 minutes.

repo: GentlemanHu/own-status


text:
🛑 AI flowise is down

In 486b66d, AI flowise (https://aiflow.crushing.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: AI flowise is back up in 1622311 after 7 minutes.


text:
🛑 WWWW xyz is down

In 729d7a0, WWWW xyz (https://www.crushing.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: WWWW xyz is back up in f9fd020.


text:
Wifi connection issue: No connection could be made because the target machine actively refused it.

Since few days I get this error when trying to connect via wifi. It was working earlier with same setup.
Connection via usb works fine but I want to use wifi connection.
Trying to use following steps
1. Connect the device to the same Wi-Fi as your computer.
2. Get your device IP address (in Settings → About phone → Status).
3. Enable adb over TCP/IP on your device: adb tcpip 5555.
4. Unplug your device.
5. Connect to your device: adb connect 192.168.2.104:555 (replace DEVICE_IP).

step 3 gives "* daemon started successfully                                                                                restarting in TCP mode port: 555  "
step 5 gives this error "cannot connect to 192.168.2.104:555: No connection could be made because the target machine actively refused it. (10061)"

https://stackoverflow.com/questions/37267335/android-studio-wireless-adb-error-10061
I don't know if this is a rypo, but in your message, you connected to port 555 instead of 5555.

my bad. you are right. since 3 days I was making same typo :(.. It is working now. closing

repo: Genymobile/scrcpy


text:
Scrcpy not working wirelessly

I'm pretty sure I did everything right, but on my Windows device (which is connected to Ethernet), when I enter the command scrcpy the command-line just closes without anything happening.

Scrcpy not working wirelessly

on my Windows device (which is connected to Ethernet)

So does it work over USB?
What is the result of adb devices?

Yes, it works over USB.
adb devices comes up with two devices. One is the IP of the device, and the other is a string with numbers and letters.

OK. What happens when you execute:
scrcpy -s 192.168.0.1:5555

? (if the ip is 192.168.0.1)

adb: error: failed to get feature set: no devices/emulators found
ERROR: "adb push" returned with value 1
Press any key to continue...

adb: error: failed to get feature set: no devices/emulators found
ERROR: "adb push" returned with value 1
Press any key to continue...

No, it's just that your device is not detected by adb. See https://github.com/Genymobile/scrcpy/blob/master/FAQ.md#adb-issues

Any updates on this? Facing the same error with my Huawei P30 Pro after updating scrcpy to the latest version

@s3hMC

adb: error: failed to get feature set: no devices/emulators found

If it's over wifi, then you did not adb connect correctly.

Could it be because of my VPN?

what kind of vpn you use ? is it possible to use vpn like portmap ?


text:
Compile failure on AArch64 - undefined reference to `drmModeGetFB2'

[x] I have read the FAQ.
[x] I have searched in existing issues.

Environment

OS: Arch Linux ARM
scrcpy version: master/1.18
installation method: AUR/manual build
device model: N/A
Android version: N/A

Describe the bug
Build on Jetson Nano/Nintendo Switch with these package versions gives two undefined references
ffmpeg 2:4.4-4
libdrm 2.4.106-1
+ exec meson setup --prefix /usr --libexecdir lib --sbindir bin --buildtype plain --auto-features enabled --wrap-mode nodownload -D b_lto=false -D b_pie=true -D prebuilt_server=/home/parker/.cache/paru/clone/scrcpy-git/src/scrcpy-server-v1.18 build
The Meson build system
Version: 0.58.1
Source dir: /home/parker/.cache/paru/clone/scrcpy-git/src/scrcpy
Build dir: /home/parker/.cache/paru/clone/scrcpy-git/src/scrcpy/build
Build type: native build
Project name: scrcpy
Project version: 1.18
C compiler for the host machine: cc (gcc 10.2.0 "cc (GCC) 10.2.0")
C linker for the host machine: cc ld.bfd 2.35
Host machine cpu family: aarch64
Host machine cpu: aarch64
Found pkg-config: /usr/bin/pkg-config (1.7.3)
Run-time dependency libavformat found: YES 58.76.100
Run-time dependency libavcodec found: YES 58.134.100
Run-time dependency libavutil found: YES 56.70.100
Run-time dependency sdl2 found: YES 2.0.14
Run-time dependency libavdevice found: YES 58.13.100
Checking for function "strdup" : YES
Configuring config.h using configuration
Program cp found: YES (/usr/bin/cp)
Program scripts/run-scrcpy.sh found: YES (/home/parker/.cache/paru/clone/scrcpy-git/src/scrcpy/scripts/run-scrcpy.sh)
Build targets in project: 3

Found ninja-1.10.2 at /usr/bin/ninja
ninja: Entering directory `build'
[30/30] Linking target app/scrcpy
FAILED: app/scrcpy
cc  -o app/scrcpy app/scrcpy.p/src_main.c.o app/scrcpy.p/src_adb.c.o app/scrcpy.p/src_cli.c.o app/scrcpy.p/src_compat.c.o app/scrcpy.p/src_control_msg.c.o app/scrcpy.p/src_controller.c.o app/scrcpy.p/src_decoder.c.o app/scrcpy.p/src_device_msg.c.o app/scrcpy.p/src_event_converter.c.o app/scrcpy.p/src_file_handler.c.o app/scrcpy.p/src_fps_counter.c.o app/scrcpy.p/src_input_manager.c.o app/scrcpy.p/src_opengl.c.o app/scrcpy.p/src_receiver.c.o app/scrcpy.p/src_recorder.c.o app/scrcpy.p/src_scrcpy.c.o app/scrcpy.p/src_screen.c.o app/scrcpy.p/src_server.c.o app/scrcpy.p/src_stream.c.o app/scrcpy.p/src_tiny_xpm.c.o app/scrcpy.p/src_video_buffer.c.o app/scrcpy.p/src_util_log.c.o app/scrcpy.p/src_util_net.c.o app/scrcpy.p/src_util_process.c.o app/scrcpy.p/src_util_str_util.c.o app/scrcpy.p/src_util_thread.c.o app/scrcpy.p/src_sys_unix_process.c.o app/scrcpy.p/src_v4l2_sink.c.o -Wl,--as-needed -Wl,--no-undefined -pie -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -march=armv8-a -O2 -pipe -fstack-protector-strong -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -Wl,--start-group /usr/lib/libavformat.so /usr/lib/libavcodec.so /usr/lib/libavutil.so -pthread /usr/lib/libSDL2.so /usr/lib/libavdevice.so -Wl,--end-group
/usr/bin/ld: /usr/lib/libavdevice.so: undefined reference to `drmModeGetFB2'
/usr/bin/ld: /usr/lib/libavdevice.so: undefined reference to `drmModeFreeFB2'
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

How did you compile/install libavdevice.so?
Scrcpy never references drmModeGetFB2 or drmModeFreeFB2.

Ok strange. I had checked that and noticed the same thing.
These are both from the main Arch Linux ARM repos so I may have to file a bug over there. Thanks

So including ldrm in the cflags works. Maybe a problem with the ffmpeg pkgconfig definition? Thanks for the great software by the way!
export CFLAGS=-ldrm

Oh that lets the linking complete but that leads to runtime error
[parker@nintendoswitch ~]$ scrcpy -m 720
scrcpy: symbol lookup error: /usr/lib/libavdevice.so.58: undefined symbol: drmModeFreeFB2

Is your link-time library the same as runtime?

As far as I'm aware yeah. I ended up replacing the repo ffmpeg with a build without libdrm and everything is working now (Wouldn't work on this system anyways)
I'm thinking there's just some mismatch on the versioning and will see if it clears up in the repo soon enough.


text:
[question] control phone while locked

Hello.
I would like to know if it could be possible to control the phone while it is in "sleep" mode.
It could be really useful if you have your phone in your pocket and you want to control it without having false positive touch events or using a lot of battery with the screen on.
Thank you!

Unfortunately, no :(
See https://github.com/Genymobile/scrcpy/issues/175.

Now you can.