When mindreader merges directly, it does not check block continuity

The proper way to check block continuity is implemented in the merger, using the forkDB from bstream/forkable package.
The mindreader simply writes blocks to a file when using the batch mode or when processing blocks older than mergeThresholdBlockAge.
There used to be a simple continuity checker that ensured that "new block is (last block - 1)" but it was removed because it fails in 2 cases:

geth sometimes sending an old bad block (https://github.com/streamingfast/sf-ethereum/issues/4) that should be simply ignored (or included silently, no problem there). Hard failing in this case causes more harm.
chains that do not have continuous block numbers (ex: block 50's parent is block 45)

The good approach will be to import the logic from the merger when we want to produce merged blocks directly (for reprocessing in batch mode, or catching up from far behind)

this has been implemented, the merger code is now used.


Number of friends

Hi!
According to this script ( https://github.com/ideoforms/python-twitter-examples/blob/master/twitter-friends.py ) I have 944 friends. This is right ( https://twitter.com/ADssx ). But it actually only prints 924 friends (I only added an index i then print i \ i=i+1).
Thanks for any help you can provide.

Just a thought, is it excluding private accounts? (If you use an authenticator that can only see public data, it might not see them.)

A bit late now probably (!) but I've now resolved this issue - users.lookup actually takes a comma-separated string parameter, not a list. Because of the way that Python constructed the URL, the first and last IDs in each set were ignored. Now fixed.


Console Spamming

[09:01:24] [Server thread/CRITICAL]: Could not execute task xenialdan\BossAnnouncement\SendTask: Argument 1 passed to pocketmine\utils\Binary::writeUnsignedVarLong_64() must be of the type integer, null given, called in phar:///root/Lobby/PocketMine-MP.phar/src/pocketmine/utils/Binary.php on line 689
[09:01:24] [Server thread/CRITICAL]: TypeError: "Argument 1 passed to pocketmine\utils\Binary::writeUnsignedVarLong_64() must be of the type integer, null given, called in phar:///root/Lobby/PocketMine-MP.phar/src/pocketmine/utils/Binary.php on line 689" (EXCEPTION) in "/src/pocketmine/utils/Binary" at line 728

I need an xdebug log. Please enable xdebug and set the debug level to "2".

Spoons are not supported. Only @ClearSkyTeam/PocketMine-MP and @pmmp/PocketMine-MP are supported


Update some github actions

This addresses some of our github CI deprecation warnings.
See the commits for deets.

Codecov Report

Merging #2742 (0de0b96) into main (4116413) will decrease coverage by 0.02%.
Report is 2 commits behind head on main.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2742      +/-   ##
==========================================
- Coverage   78.88%   78.87%   -0.02%
==========================================
  Files         463      463
  Lines       15866    15866
  Branches     2577     2568       -9
==========================================
- Hits        12516    12514       -2
- Misses       3350     3352       +2

see 2 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fixed '/edit write' command

I was using the plugin and i noticed that the "/edit write" wasn't working: the operator in the 252 line was inverted. When a player passed a line higher then the file lines amount, the plugin continued to execute the write action and returned a error in the console. And, when the opposite occurred, it just jumped the if without warning nothing in the chat.
So i changed the operator and added a else to that if, so, if the players pass a line higher than should, it will send the error menssage used in others parts of the code.
Also, i tested the plugin in a 1.16.5 server and it worked fine :D

Noticed bit too late, didn't show up in my notifs


Ad Support

Hi @PierfrancescoSoffritti
Thanks for your efforts. I'm aware that you are using Youtube's Iframe API as in Youtube's official iOS library. But do you know why the video Ads aren't being displayed in the videos.
Btw, I switched from the official native android API to your library to prevent black screen when it's not able to play Ads. In your library, though still not able to play Ads it's atleast not causing un-handled crashes (or) black screen.

Hi, I'm not sure why but the Iframe api is not showing ads. I can't do much about it, it's the Iframe lib's responsibility.


Bug: .cruft.json file created with trailing new line

Hi, the .cruft.json file get's created with a trailing new line at the end of the file. Which conflicts with the end-of-file-fixer
Fix End of Files.........................................................Failed
- hook id: end-of-file-fixer
- exit code: 1
- files were modified by this hook

Fixing .cruft.json

If we do a git diff:
diff --git a/.cruft.json b/.cruft.json
index 60d62c3..fa34b58 100644
--- a/.cruft.json
+++ b/.cruft.json
@@ -21,4 +21,4 @@
         }
     },
     "directory": null
-}
\ No newline at end of file
+}

It would be nice if the last line didn't have that trailing newline.
After diving into the json_dumps options, I see that with indent=None it is fixed although you probably don't want that. Adding .strip() to the json_dumps function in utils doesn't solve it either.
Thanks

I've seen that the problem is not on the json_dumps but on how Path writes to the file

It's actually the other way round: cruft does not terminate .cruft.json with a newline, which causes the pre-commit failure. Note that json.dump from the standard library does not add a final newline, even when passed indent.
I would also like to see this fixed.


internal/experimental should be moved to pkg/experimental

Hey!
I think putting a package just because it's experimental in an internal package is a bit annoying. An experimental package name is quite enough to signal that it is indeed experimental. I think it will also just force the people that want to use it to either copy paste or fork Helm.

Some of this is about trade offs. Helm follows semantic versioning. That includes the pkg directory which is a library others can import.
The experimental work does not follow semantic versioning. The current experiment of OCI registries is taking a slow path to a stable API and design due to work happening within the OCI.
This leaves the Helm project with two routes:

Have the experimental package in the pkg directory where the API and design will break
Have the experimental package in the internal directory where others will need to copy it to use it

In both cases we will hear some complaints. Some would complain if we broke semver on the API. I've personally encountered complaints from people when changing the API at a major version change. This even follows semver but there are still complaints. The other side is situations like this where someone needs access to the code and wants it exposed.
In either case we will have some complaining or asking for it to be different.
Because Helm tends to take the conservative route (because we know people run it in production where they are conservative about change) and Helm follows semver we have chosen to have it in internal while it is still being formed.
I look forward to the day it is not longer an experiment and we can expose a stable API and feature set.

Hmm okay fair enough :grin:
Looking forward to this day as well then!


refactor: upgrade azure storage factory

Use newest SDK v12.

:tada: This PR is included in version 0.25.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Run

Sorting states proved not useful so I removed it. But I did see a repeating pattern. there is a cycle in 3 states and two other states converge to another state.
I had to update a couple of things, remade some figures and that's why there are many lines changed. The figures have been updated in dropbox.

Was sorting not helpful in that it worked but didn't help with interpretation, or it didn't work?

The sorting function was based on the shape parameter that is shared among all conditions, but at every run, the maximum shape was not corresponding to the same state and it was changing. I could not figure out another good criterion to sort states based on it, and I did see a pattern repeating, so I removed it.

Ok, we can merge this without it, but could you move some of the code (in a separate PR) to a function that takes in a permutation (e.g., [1, 0, 3, 2]) and reorganizes the tHMM model. Basically this is the function you have, but without the rule on how to rearrange them. Some of this is also done by permute_states() in Analyze(), and so having this function would (1) remove some duplication, and (2) allow us to easily add a rule for permuting later.

Absolutely. Thank you.


Add telegram as an alert destination

Added telegram as an alert destination via telegram bot.
To use, get api_token from botfather on telegram.
chat_id can be found by adding rawdatabot to the chat you wish to have alerts go to if a group chat, or start a chat with rawdatabot to get your user_id which will be your chat_id for single user chat.
Can also get chat_id by reguesting https://api.telegram.org/bot<API_TOKEN>/getUpdates after starting a chat with your bot

I have downloaded the android telegram appli. I have created a telegram account . I have created a bot with botfather, so I have now the api_token and I have also got the chat_id.
I have amended the python code (controller.py and config.json)
To make it work, I have had to add : import urllib
Now, I get the message : “May 15 11:49:14 raspberrypi garage_controller: Sending Telegram message”
But I don’t receive any telegram msg.
Did I miss something ? (I have never used telegram messenger before)
Thanks
Gilles
From: ijaron<EMAIL_ADDRESS>Sent: jeudi 14 mai 2020 23:13
To: andrewshilliday/garage-door-controller<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: [andrewshilliday/garage-door-controller] Add telegram as an alert destination (#119)
Added telegram as an alert destination via telegram bot.
To use, get api_token from botfather on telegram.
chat_id can be found by adding rawdatabot to the chat you wish to have alerts go to if a group chat, or start a chat with rawdatabot to get your user_id which will be your chat_id for single user chat.
Can also get chat_id by reguesting https://api.telegram.org/bot<API_TOKEN>/getUpdates after starting a chat with your bot

You can view, comment on, or merge this pull request online at:
https://github.com/andrewshilliday/garage-door-controller/pull/119
Commit Summary

Add telegram as an alert destination

File Changes

M config.json https://github.com/andrewshilliday/garage-door-controller/pull/119/files#diff-06b2d3b23dce96e1619d2b53d6c947ec  (26)
M controller.py https://github.com/andrewshilliday/garage-door-controller/pull/119/files#diff-7a315c65deca2c033ce485bfa9de4f4a  (34)

Patch Links:

https://github.com/andrewshilliday/garage-door-controller/pull/119.patch
https://github.com/andrewshilliday/garage-door-controller/pull/119.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/andrewshilliday/garage-door-controller/pull/119 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AEA4RAPPXWZPC4PWC7ORPR3RRRNEVANCNFSM4NBBEJNQ .  https://github.com/notifications/beacon/AEA4RAKN4BD5WF76P5PXJ4LRRRNEVA5CNFSM4NBBEJN2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4JG6E4OA.gif

It is likely that you have to start a chat with your bot before it will send messages. I haven't tested it without starting a chat first.
To start a chat just send your bot "/start"

You were right. It works now when I have first started the chat with  “/start”.
Thanks a lot.
Regards,
Gilles
From: ijaron<EMAIL_ADDRESS>Sent: vendredi 15 mai 2020 12:28
To: andrewshilliday/garage-door-controller<EMAIL_ADDRESS>Cc: Gilles94500<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [andrewshilliday/garage-door-controller] Add telegram as an alert destination (#119)
It is likely that you have to start a chat with your bot before it will send messages. I haven't tested it without starting a chat first.
To start a chat just send your bot "/start"
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/andrewshilliday/garage-door-controller/pull/119#issuecomment-629159694 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AEA4RALRLME6KG55OG32AXLRRUKLXANCNFSM4NBBEJNQ .  https://github.com/notifications/beacon/AEA4RAPHEFWKOKVXDI4SHSTRRUKLXA5CNFSM4NBBEJN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEWADODQ.gif

Thanks for the contribution.  I will merge this in now.


Styling for market filters

@mk26071980 Please add figma link

I think this is the design

https://www.figma.com/file/A0OEqjIWy6jL4Rk4kT8ddr/UX%2FUI_Workflow?node-id=3970%3A22390&t=VZsAlSDZCYEfzZf8-0
Though, we might need to review the current categories that we're offering

@mk26071980 How does this look once we start adding more categories?

@mk26071980 How do the Currency and Status dropdowns look?

https://www.figma.com/file/A0OEqjIWy6jL4Rk4kT8ddr/UX%2FUI_Workflow?node-id=3970%3A22390&t=EKM80QDlLKSgCDGu-1


fix(debug/ios): obtain correct certificate name

Dependent on the SDK version used we need to provide the full name or the short name of the
certificate. This was done on build/package commands but not on the debug code
Fixes #166

Warnings

:warning:

src/debugger/titaniumDebugConfigurationProvider.ts#L14 - src/debugger/titaniumDebugConfigurationProvider.ts line 14 – 'token' is defined but never used. (@typescript-eslint/no-unused-vars)

:warning:

src/debugger/titaniumDebugConfigurationProvider.ts#L19 - src/debugger/titaniumDebugConfigurationProvider.ts line 19 – Rest/spread properties are not supported until Node.js 8.3.0. The configured version range is '>=8.0.0'. (node/no-unsupported-features/es-syntax)

:warning:

src/debugger/titaniumDebugConfigurationProvider.ts#L62 - src/debugger/titaniumDebugConfigurationProvider.ts line 62 – Expected catch() or return (promise/catch-or-return)

Messages

:book:

:floppy_disk: Here's the built vsix for this change.

:book:

:white_check_mark: All tests are passing
Nice one! All 32 tests are passing.

  Generated by :no_entry_sign: dangerJS against 14d7f6c6f93497e16d2f1beea87d6c427639d477


This repo (in particular the extraction ETL, which is likely to be applicable on numerous datasets) should be pip installable

Things I am confident of

[ ] The standardized extraction stages from this repo should be made runnable via CLI tools installable via pip
[ ] The pre-MEDS standardized files for MIMIC-IV and eICU should be (through separate packages, and possibly separate repos) be made installable and runnable via CLI tools from pip.
[ ] Standardized pre-processing archetype scripts (e.g., collect_code_metadata.py) should, when finished, likely be installable and runnable as one-off scripts via pip.

Things I am uncertain of and would like community input on:

Should the single-pass scripts (e.g., joint_script.sh, joint_script_slurm.sh) in the MIMIC-IV and eICU examples be made into installable tools?
Should the core mapreduce, locking, and sharding utilities be made importable via a Python API for other users developing new pipelines (likely yes)?
Should the Hydra configuration setups and custom resolvers be (somehow) made importable via a Python API for other users developing new pipelines (but how?)?
Should we provide further abstractions over building staged scripts for MEDS trasnformations over simple compute functions (likely no at this stage)?

This is now installable at pip install MEDS-transforms


HP Twain dialog appears after scanning, asking for the user to load the document feeder

We have a user that is using the 64bit DTWAIN library and the HP ScanJet Enterprise Flow N6600 fnw scanner.  After all of the paper is fed through the ADF, this dialog appears:

Do you know if there is a way to prevent the dialog from appearing?  Maybe an HP capability that can be turned on/off?  I know this is probably a question that is more suited for HP support, but I thought I would start here first.  Thank you for any help!

I would check if the pending transfer count is actually 0 on the last page.  If it isn't, then the issue is probably that the scanner thinks there are pages left, when the feeder is actually empty.
You can check this by producing a log and searching for the PENDINGXFER triplet.   You should see a Count value set to 0 after all the pages have been scanned.
But having said this, just possibly the DTWAIN_EnableIndicator can be used to turn off the scanning progress indicator, and possibly this dialog as well.  I can't promise you this will do anything, probably it will turn off the percentage dialog (if one is showing), but maybe it will affect this dialog also.

Thanks Paul.  The feeder is definitely empty when the dialog appears.  I'll check the log and try DTWAIN_EnableIndicator.  Appreciate the ideas.


CTS NPEs on relationship endpoint EntityDef lookups

Came across a number of NullPointerExceptions in the (master) CTS as follows: under the run() method of the test classes below, the endpoint definitions of a relationship are retrieved but repositoryHelper.getTypeDefByName(...) fails with an NPE when the type definition is a supertype that is not implemented by the repository being tested. (For example, ActorProfile when the repository only implements Person; Asset when the repository only implements Database; ComplexSchemaType when the repository only implements TabularSchemaType, etc.)
Seems like another case where we should be retrieving the endpoint definitions of the relationship from the open type definitions themselves -- not from the repository under test?
Seen in all of the following:

[ ] TestSupportedRelationshipLifecycle
[ ] TestSupportedRelationshipReidentify
[ ] TestSupportedRelationshipPropertySearch
[ ] TestSupportedRelationshipPropertyAdvancedSearch

There's a fair number of potential NPEs reported in the sonar scan on the CTS code also, so suggest checking those out too

Hmmm.. that's confusing. Those type checks were introduced specifically to check that the repository's reported type matches the 'known' type. It uses the same repo helper method that is used to get the properties (which also needed to come from the known type, not the repository's returned type). I was under the impression that the getTypeDefByName would return the known type, as opposed to the active type. I will take a deeper look.

I think the ones from the sonar scans might be bogus - there are lots of places in the CTS where we perform a test, then call an assertCondition method which will throw an exception if the assertion is not satisfied. The tests can continue safely after the assertion has been tested. I have discussed with Mandy adding explicit belt and braces protection to avoid the sonar scan warnings but we decided not to at the time - I will take another look when I get a moment

@cmgrote - Hi Chris - when the connector is called on verifyTypeDef does it throw TypeDefNotSupportedException? (I'm just eye-balling repo content manager code and trying to work out why the unimplemented super-types would not be in knownTypes).

On my repository, yes, it will throw TypeDefNotSupportedException for the supertypes that I have not implemented.  So, for example, if you called verifyTypeDef on my connector with the GUID of the Asset type def, you would get a TypeDefNotSupportedException.  However, if you called the same with the GUID of Database (which is a subtype of Asset) then you should get true.

I think that you are doing the right thing.
What's puzzling is that if a connector response to verifyTypeDef with a TypeDefNotSupportedException then the RCM should (from looking at the code) be caching the typedef into knownTypes (and not into activeTypes). But if that were the case then I would expect my type-checking assertion to get the type back from the repo helper when it calls getTypeDefByName (which looks in the knownTypes).


Setup a Template for Story in this Repo

User Story
As ...,
I want ...,
so that... .
Acceptance Criteria

[ ] ...

Hints / Details

...

## Tasks
- [ ] https://github.com/octo-org/octo-repo/issues/45
- [ ] Draft task

[ ]


Adds the flag to not inlude the publicPath

For some reason the indent changed complete, probably the eslint --fix.
But the key idea here is only to get the asset name, in my case, I'm going to serve then thru a CDN.

@ernestorocha 	Thanks for the PR, could you fix the test so it checks that the string appears at the beginning of the output?

Actually the test was wrong, since the whole output is being converted to string. Thanks for pointing that out!
But again, a lot of indention changed. If you prefer I can prevent the indention of those files to change.

published v3.1.0

Thanks a lot, @sporto!


ATI response cannot be parsed as String, but can as Bytes

I noticed the following when trying out atat. When defining ATI response using heapless::Bytes it parses correctly.
#[derive(Debug, Clone, AtatResp)]
pub struct ATIResponse
{
    pub info: Bytes<64>,
}

The response:
ATIResponse { info: b'Quectel\r\nEC25\r\nRevision: EC25EFAR06A09M4G' }

But when using heapless::String it results in Error::Parse.
#[derive(Debug, Clone, AtatResp)]
pub struct ATIResponse
{
    pub info: String<64>,
}

Perhaps still the same issue as in #86.

Hmm. Without any more context, it's a bit hard to tell why, but the main difference between bytes & string, is that a string reply must be quoted explicitly (So you cannot just parse a bytes response as a string response currently)

Ah so I guess this is intended behaviour then. So only when the modem returns explicit "...." including the quotes we can use String

Ah so I guess this is intended behaviour then. So only when the modem returns explicit "...." including the quotes we can use String

Currently, this is the behavior, yes.
I would have no objections against adding some sort of derive attribute option to the string implementation, that allows skipping the quotes in either end? I currently have no use cases for this myself, so I won't be adding it, but you are more than welcome to open a PR with it? :smiley:

I ran into this problem at work and came up with the following solution. I'm not particularly proud of it but it's an ok stopgap until something nicer comes along :)
/// A helper to deserialize unquoted strings in AT responses.
struct UnquotedStringVisitor<const N: usize>;

impl<'de, const N: usize> Visitor<'de> for UnquotedStringVisitor<N> {
    type Value = heapless::String<N>;

    fn expecting(&self, formatter: &mut fmt::Formatter) -> fmt::Result {
        formatter.write_str("an unquoted string")
    }

    fn visit_bytes<E>(self, v: &[u8]) -> Result<Self::Value, E>
    where
        E: de::Error,
    {
        let s = std::str::from_utf8(v).map_err(serde::de::Error::custom)?;

        if s.len() > N {
            Err(serde::de::Error::custom("Source string too long"))
        } else {
            Ok(s.into())
        }
    }
}

#[derive(Debug, Clone, PartialEq)]
pub struct UnquotedHeaplessString<const N: usize>(pub heapless::String<N>);

impl<'de, const N: usize> Deserialize<'de> for UnquotedHeaplessString<N> {
    fn deserialize<D>(deserializer: D) -> Result<Self, D::Error>
    where
        D: serde::Deserializer<'de>,
    {
        let out = deserializer.deserialize_bytes(UnquotedStringVisitor)?;

        Ok(Self(out))
    }
}

impl<const N: usize> From<&str> for UnquotedHeaplessString<N> {
    fn from(s: &str) -> Self {
        Self(s.into())
    }
}

impl<const N: usize> fmt::Display for UnquotedHeaplessString<N> {
    fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
        f.write_str(&self.0)
    }
}

Using MQTT on a Quectel,  I also see that I can't get the result of the messages, which feature two texts included in double quotes, when defining the elements in the OnReceive struct as heapless strings.
-Michael

@ijager
BTW.:
In fact I did get such a parser error, when Trying ATI but instead of trying out "Bytes" in a response struct, I avoided using the parser by not deriving the "send" - struct but implementing my own parser.
IMHO this in fact makes sense for not "true" URC (but direct on send()) responses from the modem, as here you easily can handle the response in any way you like.
-Michael

I would have no objections against adding some sort of derive attribute option to the string implementation, that allows skipping the quotes in either end? I currently have no use cases for this myself, so I won't be adding it, but you are more than welcome to open a PR with it? smiley

Are there already any derive attributes that define the behavior of the parser differently from what the main derive macro extracts from the type of the struct elements ?

I think you are mixing request/response and URCs here.
For the request response it is all handled by AtatCmd and AtatResponse that can both be derived, URC parser has nothing to do with these at all

I'm not in the office right now. I'll do more testing ASAP. (Hoping to be able to avoid the implementation of my own parser  for the response of communication as simple as ATI with non quoted strings <by means of  #[at_arg(position = 0)] or similar>. And of course to get a notification in the user code from an urc with quoted strings such as +QMTRECV.

@mschnell1 I am also implementing Quectel MQTT commands for the EC25. Just managed to connect to a broker. Next step I think is also those URC's and some state machine to progress through the necessary commands.
I did notice that other commands such as ManufacturerId (AT+CGMI) do get parsed fine into a heapless::String even though those responses are not quoted as far as I know (at least not from my Quectel EC25). So far the only difference I can see is that the ATI response is multi line instead of a single line ending in \r\n. Which I guess makes sense that it would trip up the default String parsing, because I think it is usually only reading until the first \r\n.
@MathiasKoch I am not particularly interested in the ATI response, so for me it is enough to know that Bytes + manual parsing is the way to go for those cases. If you want you can close this issue.

as far as I know
You can use the log feature of ATAT to see the complete dialog with the modem.

Yes when I turn on logging for atat it shows quotes, but when I sniff the communication with a serial - usb converter there are no quotes. So maybe the quotes are added somewhere in atat?
I will try to implement subscribing today.

Using MQTT on a Quectel,  I also see that I can't get the result of the messages, which feature two texts included in double quotes, when defining the elements in the OnReceive struct as heapless strings.
-Michael

Edit:
by some magic I now get a correct +QMTRECV notification by ATAT

Well, if you are receiving URC's that are not defined in the Urc enum, it will kinda end up as undefined behaviour, as it will become part of the next attempt to parse a known URC or response, with varying success.

@mschnell1 I got it working now, the QMTRECV parses okay. But indeed you have to define and decorate the URC enum and define the struct properly so that it matches your settings. E.g. whether it returns the length as well.
This is my Urc enum so far:
#[derive(Clone, AtatUrc, Debug)]
pub enum Urc {
    #[at_urc("+QMTOPEN")]
    MqttOpen(commands::mqtt::urc::MqttOpen),
    #[at_urc("+QMTCONN")]
    MqttConnect(commands::mqtt::urc::MqttConnect),
    #[at_urc("+QMTSUB")]
    MqttSubscribe(commands::mqtt::urc::MQTTSubscribe),
    #[at_urc("+QMTRECV")]
    MQTTReceive(commands::mqtt::urc::MQTTReceive)
}

// and the urc structs

#[derive(Clone, Debug, AtatResp)]
pub struct MqttOpen {
    pub client_idx: u8,
    pub result: u8,
}

#[derive(Clone, Debug, AtatResp)]
pub struct MqttConnect {
    pub client_idx: u8,
    pub result: u8,
    pub ret_code: u8,
}

#[derive(Clone, Debug, AtatResp)]
pub struct MQTTSubscribe {
    pub client_idx: u8,
    pub msg_id: u8,
    pub result: u8,
    pub value: u8,
}

#[derive(Clone, Debug, AtatResp)]
pub struct MQTTReceive {
    pub client_idx: u8,
    pub msg_id: u8,
    pub topic: String<32>,
    pub len: u8,
    pub payload: String<32>
}

Here is my full log output in case it helps:
14:54:35.576 DEBUG - [EC25] state: Init
14:54:35.680 DEBUG - send next cmd EchoOn(EchoOn)
14:54:35.680 DEBUG - Sending command: ""ATE1\r\n""
14:54:35.783 DEBUG - Received OK
14:54:35.864 DEBUG - send next cmd GetIdentification(IdentificationInformation)
14:54:35.864 DEBUG - Sending command: ""ATI\r\n""
14:54:35.969 DEBUG - Received response: ""Quectel\r\nEC25\r\nRevision: EC25EFAR06A09M4G""
14:54:36.071 DEBUG - send next cmd GetManufacturerId(GetManufacturerId)
14:54:36.071 DEBUG - Sending command: ""AT+CGMI\r\n""
14:54:36.172 DEBUG - Received response: ""Quectel""
14:54:36.172 DEBUG - Manufacturer: ManufacturerId { id: "Quectel" }
14:54:36.278 DEBUG - send next cmd GetModelId(GetModelId)
14:54:36.278 DEBUG - Sending command: ""AT+CGMM\r\n""
14:54:36.384 DEBUG - Received response: ""EC25""
14:54:36.384 DEBUG - Model: ModelId { id: "EC25" }
14:54:36.460 DEBUG - send next cmd GetSoftwareVersion(GetSoftwareVersion)
14:54:36.460 DEBUG - Sending command: ""AT+CGMR\r\n""
14:54:36.565 DEBUG - Received response: ""EC25EFAR06A09M4G""
14:54:36.565 DEBUG - sw version: SoftwareVersion { id: "EC25EFAR06A09M4G" }
14:54:36.668 DEBUG - send next cmd SetPDPContextDefinition(SetPDPContextDefinition { cid: ContextId(1), pdp_type: "IP", apn: "portalmmm.nl" })
14:54:36.668 DEBUG - Sending command: ""AT+CGDCONT=1,\"IP\",\"portalmmm.nl\"\r\n""
14:54:36.773 DEBUG - Received OK
14:54:36.877 DEBUG - send next cmd ActivateContext(ActivateContext { cid: ContextId(1) })
14:54:36.877 DEBUG - Sending command: ""AT+QIACT=1\r\n""
14:54:36.980 DEBUG - Received OK
14:54:37.061 DEBUG - send next cmd MQTTConfigRecvMode(ConfigRecvMode { param: "recv/mode", client_idx: ContextId(1), msg_recv_mode: 0, msg_len_enable: Some(1) })
14:54:37.061 DEBUG - Sending command: ""AT+QMTCFG=\"recv/mode\",1,0,1\r\n""
14:54:37.162 DEBUG - Received OK
14:54:37.264 DEBUG - send next cmd MQTTOpenContext(Open { client_idx: ContextId(1), host_name: "mybroker.xyz", port: 1883 })
14:54:37.264 DEBUG - Sending command: ""AT+QMTOPEN=1,\"mybroker.xyz\",1883\r\n""
14:54:37.370 DEBUG - Received OK
14:54:37.473 DEBUG - send next cmd AT(AT)
14:54:37.473 DEBUG - Sending command: ""AT\r\n""
14:54:37.579 DEBUG - Received OK
14:54:37.659 DEBUG - urc: MqttOpen(MqttOpen { client_idx: 1, result: 0 })
14:54:37.659 DEBUG - [EC25] state: Connect
14:54:37.764 DEBUG - send next cmd MQTTConnect(Connect { client_idx: ContextId(1), mqtt_client_id: "Ingmar" })
14:54:37.764 DEBUG - Sending command: ""AT+QMTCONN=1,\"Ingmar\"\r\n""
14:54:37.870 DEBUG - Received OK
14:54:37.870 DEBUG - MQTT CONNECT: NoResponse
14:54:37.976 DEBUG - urc: MqttConnect(MqttConnect { client_idx: 1, result: 0, ret_code: 0 })
14:54:37.976 DEBUG - [EC25] state: Subscribe
14:54:38.077 DEBUG - send next cmd MQTTSubscribe(Subscribe { client_idx: ContextId(1), msg_id: 1, topic: "blink", qos: 0 })
14:54:38.077 DEBUG - Sending command: ""AT+QMTSUB=1,1,\"blink\",0\r\n""
14:54:38.155 DEBUG - Received OK
14:54:38.155 DEBUG - MQTT SUB: NoResponse
14:54:38.261 DEBUG - urc: MqttSubscribe(MQTTSubscribe { client_idx: 1, msg_id: 1, result: 0, value: 0 })
14:54:38.261 DEBUG - [EC25] state: Ready
14:54:42.555 DEBUG - urc: MQTTReceive(MQTTReceive { client_idx: 1, msg_id: 0, topic: "blink", len: 5, payload: "start" })
14:54:42.555 INFO - Received "start" on topic "blink"
14:55:03.898 DEBUG - urc: MQTTReceive(MQTTReceive { client_idx: 1, msg_id: 0, topic: "blink", len: 5, payload: "hello" })
14:55:03.898 INFO - Received "hello" on topic "blink"

And this is what I see on the uart lines:
RDY
AT
OK
ATE1
OK
ATI
Quectel
EC25
Revision: EC25EFAR06A09M4G
OK
AT+CGMI
Quectel
OK
AT+CGMM
EC25
OK
AT+CGMR
EC25EFAR06A09M4G
OK
AT+CGDCONT=1,"IP","portalmmm.nl"
OK
AT+QIACT=1
OK
AT+QMTCFG="recv/mode",1,0,1
OK
AT+QMTOPEN=1,"mybroker.xyz",1883
OK
AT
OK
+QMTOPEN: 1,0
AT+QMTCONN=1,"Ingmar"
OK
+QMTCONN: 1,0,0
AT+QMTSUB=1,1,"blink",0
OK
+QMTSUB: 1,1,0,0
+QMTRECV: 1,0,"blink",5,"start"
+QMTRECV: 1,0,"blink",5,"hello"

Well, if you are receiving URC's that are not defined in the Urc enum, it will kinda end up as undefined behaviour, as it will become part of the next attempt to parse a known URC or response, with varying success.

Nasty, but supposedly unavoidable.
This seems to mean that any possible response by the modem needs to be covered in the Urc enum....

So far i haven't found a better approach, but to be fair most URC's are default disabled on most modems, and needs to be explicitly enabled. At least on the modems i have used?

@ijager
Seeminglöy you use a differet logger. in my Debug output I don't see the double double quotes. It looks like this:
DEBUG atat::ingress               > Received response (51/51): "Quectel\r\nEC25\r\nRevision: EC25EFAR06A14M4G"
I Can't fmnd the type "[Bytes](heapless::Bytes)" you use (the ATAT create does not republish is while it dose provide atat::heapless::String )
So I tried to do

#[derive(Clone, Debug, AtatResp)]
pub struct QueryModemType2Response {
    #[at_arg(position = 0)]
    pub received_modem_type: atat::heapless::Vec<u8, 300>, //String<0x100>,
}

but I still get the send() result:  Err(Parse)
Any further idea ?
Btw.: is it appropriate to do such "silly user" discussions in an "issue" thread ?
-Michael

Sorry for continuing being a PITA.....

I don't find out anything about the  #[at_arg(position = 0)]  stuff. ATAT seems somehow to dorward this to some serdes functionality. Any starters on how to find any documentation on that ?

Right now I use AT+QMTPub to bublish QMT topic content. That6 does work and easily is compatible with ATAT.
But in fact that command ios nopt even documented with the Quectel modem I use. The documentation sttes AT+QMTPUBEX. I in fact would like to use that, anyway, as it can send binary data  instead of text only.

With AT+QMTEX  the modem is expects a message length instead of the message as the 6th parameter. it then sends a >  and expects as many bytes as given as message length. After thet it sends OK .
Is such a procedure implemented ot anyhow supported in ATAT ?

when transferring binary data with QMTT, Will ATAT be able to receive such  +QMTRECV  urc messages in the normal way ?

Thanks for listening !
-Michael

at_arg is documented as part of the relevant derive macro in atat_derive; https://github.com/BlackbirdHQ/atat/blob/master/atat_derive/src/lib.rs#L141-L165

As for two this is supported and i use it multiple places, but for now it requires you to split it into two commands as
https://github.com/BlackbirdHQ/ublox-cellular-rs/blob/master/ublox-cellular/src/command/device_data_security/mod.rs#L79-L121
And then they can be used as:
https://github.com/BlackbirdHQ/ublox-cellular-rs/blob/master/ublox-cellular/src/services/data/ssl.rs#L55-L70

@ijager Seemingly you use a different logger.

I am using rtt-target in combination with log.

I Can't find the type heapless::Bytes you use

It is actually a different crate: heapless_bytes::Bytes.

Btw.: is it appropriate to do such "silly user" discussions in an "issue" thread ?

There is also the matrix chat

@MathiasKoch

As for question 3, i think that requires more knowledge about the modem than i have at present, and sounds less like an atat question?

As far as I understand,  the Modem can handle binary payload in such way:

configure the Modem to enable the optional length parameter in the +QMTRCV Urc
use AT+QMTPUBEX instead of the (not even documented but working AT+QMTPUB command to send the binary payload.
When receiving the +QMTRCV Urc contains the topic in quotes, the length as digits, and then the payload in quotes

Now the payload can contain any characters including quotes, comma, etc. Only by relying on the length parameter the receiver can know the end of the payload. The "URC parser" needs to  support this in some way.
-Michael

Ahh, yeah that is a very common way of doing it in AT commands, but it is not currently supported in ATAT :/
Contributions are welcomed.

@ijager

It is actually a different crate: heapless_bytes::Bytes.

Yep that works.
Seemingly the Derive Macro recognizes Bytes but not Vec<u8, 300> .

Ahh, yeah that is a very common way of doing it in AT commands, but it is not currently supported in ATAT :/
Contributions are welcomed.

Yep !
Once I find out how to do this and get to know more about the current options in ATAT, which I of course would not want to get in conflict with ....

Sorry for continuing being a PITA.
Trying to implement AT+QMTPUBEX , I see that ATAT successfully detects a "prompt" (>): In the log I see:
DEBUG atat::ingress               > Received prompt (4/4)
Seemingly this does release the client.send().await; with an OK result. But how to see that this in fact is a pronpt and not an "OK" from the modem  ?
And after this I need to send a  certain count of bytes as the raw payload.
How to do this ? I get close to tzhat by

#[derive(Clone, Debug, AtatCmd)]
#[at_cmd(
    "",
    NoResponseMqttSetup,
    cmd_prefix = "",
    termination = "",
    value_sep = false,
    timeout_ms = 3000
)]
pub struct MqttSend2_1 {
    pub msg: Bytes<64>,
}

``` When trying to use a string type, the serializer creates additional quotes. and with other types such as Bytes, I can't seem to be able to define the count of bytes to be sent.

-Michael

@ijager : How do you progress with MQTT ?
-Michael

@ijager : How do you progress with MQTT ?

I just implemented +QMTPUBEX by splitting it up in two parts. Seems to work as expected.

Yep. That does work fine for me, as well. I just did not find out how to be sure that the callback I get between the parts in fact is a "Prompt" (which ATAT seems to be detecting) or something else (such as an OK or Error ), which would indicate a problem.
Receiving ASCII (and supposedly UTF-2) data also works perfectly.
But In fact I would like to transfer binary data. The modem does handle this decently, but ATAT can't cope with a double quote or any bytes > 127 in the payload.
Thanks,
-Michael


Issue with Jest

Issue occuring when trying to write jest tests
I have followed the docs and added the following to setupTests.json
window.matchMedia = window.matchMedia || function() {
    return {
        matches : false,
        addListener : function() {},
        removeListener: function() {}
    };
};

I am still getting the following error:
   matchMedia not present, legacy browsers require a polyfill
Package Json:
{
  "name": "kegthat-headless",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint",
    "test": "jest"
  },
  "dependencies": {
    "@apollo/client": "^3.7.2",
    "@types/node": "18.11.15",
    "@types/react": "18.0.26",
    "@types/react-dom": "18.0.9",
    "axios": "^0.21.1",
    "eslint": "8.29.0",
    "eslint-config-next": "13.0.6",
    "jest-environment-jsdom": "^29.3.1",
    "lodash": "^4.17.21",
    "next": "13.0.6",
    "react": "18.2.0",
    "react-dom": "18.2.0",
    "react-slick": "^0.29.0",
    "slick-carousel": "^1.8.1",
    "typescript": "4.9.4"
  },
  "devDependencies": {
    "@babel/preset-env": "^7.20.2",
    "@babel/preset-typescript": "^7.18.6",
    "@testing-library/dom": "^8.19.0",
    "@testing-library/jest-dom": "^5.16.5",
    "@testing-library/react": "^13.4.0",
    "@types/react-slick": "^0.23.10",
    "autoprefixer": "^10.4.13",
    "babel-jest": "^29.3.1",
    "identity-obj-proxy": "^3.0.0",
    "jest": "^29.3.1",
    "jest-cli": "^29.3.1",
    "polyfill": "^0.1.0",
    "postcss": "^8.4.20",
    "tailwindcss": "^3.2.4",
    "ts-node": "^10.9.1"
  }
}

I cannot add a test-setup.js as there is already a jest.config.ts in the project. Is there a fix for this?
Cheers

include this in your test-setup.js

/**
 * fix: `matchMedia` not present, legacy browsers require a polyfill
 */
global.matchMedia = global.matchMedia || function() {
  return {
    matches: false,
    addListener: function() { },
    removeListener: function() { }
  }
}

Hi @BenParr64 , I'm currently facing similar issue. Have you been able to resolve it, or are you still experiencing the issue?
If you found a solution or any workarounds, I would appreciate it if you could share your insights.

Hey mate, I think I just mocked it but I can try and find the code and get back to you! Cheers
Sent from Samsung Mobile on O2
Sent from Outlook for Androidhttps://aka.ms/AAb9ysg

From: saikiranravupalli @.>
Sent: Thursday, May 25, 2023 6:22:42 AM
To: akiran/react-slick @.>
Cc: Ben Parr @.>; Mention @.>
Subject: Re: [akiran/react-slick] Issue with Jest (Issue #2202)
Hi @BenParr64https://github.com/BenParr64 , I'm currently facing similar issue. Have you been able to resolve it, or are you still experiencing the issue?
If you found a solution or any workarounds, I would appreciate it if you could share your insights.
—
Reply to this email directly, view it on GitHubhttps://github.com/akiran/react-slick/issues/2202#issuecomment-1562288470, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASYAXNNNKG5LSJJ6RNOZ5ZDXH3UCFANCNFSM6AAAAAATAAHQBE.
You are receiving this because you were mentioned.Message ID: @.***>

@saikiranravupalli You should also be able to fix it by adding this code near the top of the file containing your tests, before the tests are run:
Object.defineProperty(window, 'matchMedia', {
    value: () => {
      return {
        matches: false,
        addListener: () => {},
        removeListener: () => {}
      };
    }
})


Error 500 while raising a pull request

Gogs version (or commit ref): 0.8.10
Git version: 2.6.6
Operating system:
Database (use [x]):

[ ] PostgreSQL
[X ] MySQL
[ ] SQLite

Can you reproduce the bug at https://try.gogs.io:

[ ] Yes (provide example URL)
[ ] No
[X] Not relevant

Log gist:

Description
We are getting 500 error while raising a pull request.
Please find the  logs,
2016/08/25 20:51:56 [...routers/repo/pull.go:632 CompareAndPullRequestPost()] [E] NewPullRequest: testPatch: UpdateLocalCopy: Pull: exit status 128 - error: Pull is not possible because you have unmerged files.
hint: Fix them up in the work tree, and then use 'git add/rm '
hint: as appropriate to mark resolution and make a commit.
fatal: Exiting because of an unresolved conflict.
Can u advise on the solution.
...

Can you help on this.

Hi, your version is too old to debug, please upgrade.


@type tag does not permit a description

When including a @type tag such as:
class Foo {
    constructor() {
        /** type {string} This is a bar string */
        this.bar = "blah";
    }
}

I get the following warning from JSDoc:

WARNING: The @type tag does not permit a description; the description will be ignored.

But then the description shows up in the documentation just fine.
Should the warning be removed?

The correct syntax is:
/**
 * The is a bar string
 * @type {string}
 */

Of course, but why warn on the wrong / alternate syntax only to have it work?

@apowers313 Because often you want to let people know that what they are doing is wrong without completely exiting and failing. It is a warning, suggesting what you are doing is not really supported. It could stop working tomorrow, who knows.
Perhaps it worked that way previously, and this is in for backwards compatibility; but the author wants you to update to doing it the correct way (without breaking all the apps doing it the old way).

@englercj is correct—this syntax happens to work, but it's not officially supported, and the behavior could change in the future.
I agree that the warning is misleading, but since it would be extremely difficult to change the warning's text for this one case, I'm closing this issue.


Missing dependencies.txt (aborts if CanAdv.ash is not found)

I ran it on an account which doesn't have many scripts installed & got a failure when it tries to find canadv.ash for some reason.
Easily fixable from the mafia script manager but equally easily fixable in the repo.

looks like this issue is actually related to the workflows; there is a dependencies.txt that is simply not actually part of the release build. I'll dig into it


String Public Key

During the v24 cycle, Unity switched from a string public key to a byte array public key.
const char* public_key;
const uint8_t* public_key;

https://github.com/nneonneo/Il2CppVersions/blob/master/headers/diffs.diff

Pull Request Test Coverage Report for Build<PHONE_NUMBER>8
Details

4 of 40 (10.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 27.996%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

LibCpp2IL/ReadableClass.cs
4
5
80.0%

LibCpp2IL/Metadata/Il2CppAssemblyNameDefinition.cs
0
35
0.0%

Totals

Change from base Build<PHONE_NUMBER>3:
-0.1%

Covered Lines:
3385

Relevant Lines:
10320

💛  - Coveralls


[BUG] Error while training KNN model

I get an error saying "no handler found for uri [/_plugins/_knn/models/_train/my-model?pretty=true] and method [POST]"
when I try to train a knn model as described in https://opensearch.org/docs/latest/search-plugins/knn/approximate-knn/
POST /_plugins/_knn/models/_train/my-model
{
  "training_index": "train-index",
  "training_field": "train-field",
  "dimension": 4,
  "description": "My models description",
  "search_size": 500,
  "method": {
      "name":"hnsw",
      "engine":"faiss",
      "parameters":{
        "encoder":{
            "name":"pq",
            "parameters":{
                "code_size": 8,
                "m": 8
            }
        }
      }
  }
}

Moving to k-nn repo, thanks for submitting!

The command executed when the first line was changed to:
POST /_plugins/_knn/models/my-model/_train

But, the training status indicates the process failed:
{
  "model_id" : "my-model",
  "model_blob" : "",
  "state" : "failed",
  "timestamp" : "2022-02-05T20:39:29.638303700Z",
  "description" : "My models description",
  "error" : "Failed to execute training. May be caused by an invalid method definition or not enough memory to perform training.",
  "space_type" : "l2",
  "dimension" : 4,
  "engine" : "faiss"
}

The docker container has 4GB assigned to it, and thus, it is unlikely that is a memory issue. The issue is likely due to  invalid method definition.

The error message in the Docker compose command's logs is:
Failed to run training job for model "my-model": Error in void faiss::ProductQuantizer::set_derived_values() at /tmp/tmphrq2n5np/k-NN/jni/external/faiss/faiss/impl/ProductQuantizer.cpp:189: Error: 'd % M == 0' failed


MonadST instances

What do we think about adding a dependency on purescript-st and giving MonadST instances to all the transformers?

Seems sensible to me :+1:


Provide CloudWatch event history in Monitor compartment

We need a generic event receiver for any Media Service that emits CloudWatch events. This enhancement will capture events emitted and relate them to a cloud resource ARN. This can be displayed in an additional tabulator on the monitor tab. We should also consider adding a TTL to this table to maintain a window of past events for review.

Event capture in a new DDB table
API Gateway entry point to query based on ARN and time range (or past: min, hours, days)
UI support in the Monitor tab
CloudFormation support for installation and updates

All CWE are now being captured and saved into the CloudWatchEvents DB. UI now has a tab specifically for CWE that shows up when a node has been selected.


OpenStack derived object migration filters

Description
This adds filters to the migration to ignore the OpenStack derived WorkloadEndpoints and Profiles.
Release Note
Skip OpenStack derived WorkloadEndpoints and Profiles when migrating to the new data format.

@neiljerram I had considered and tried to make those changes to change the regex but could not come up with a satisfactory change.  I wasn't a big fan of that change myself because I don't like changing 'production' code to make a test work which is effectively what that would be doing.


[New Port Request]

Library name: netLink
Library description: Socket and Networking Library using msgpack.org[C++11]
Source repository URL: https://github.com/Lichtso/netLink
Project homepage : same as source repository

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


Simulate a web browser more effectively

When Needl requests a website (i.e. Google) it will download the requested URL only. We should make every effort to behave like a web browser by downloading any of the websites resources such as images, CSS and JavaScript files.
Should we consider using a headless browser testing framework such as PhantomJS?

Worth noting that it's now possible to run Chromium headlessly https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md
Potentially/optionally it might be worth using something like Selenium WebDriver to use real browsers - rotating those would further hurt attempts to profile based on individual asset download strategies. (Sadly a thing with HTTP2!)

@antoligy I'm late to the party here but this is great - thanks! I've got more free time now so I plan to work on Needl and implement headless Chromium.

headless Chrome now added!


Update power plant tileset

Description
When the power plant model was updated in https://github.com/CesiumGS/cesium/pull/10615 one of the batch table properties got lost. I reprocessed the data and uploaded it to ion.
Testing plan
When you click any feature in the tileset you should now see a Type property.

Author checklist

[x] I have submitted a Contributor License Agreement
[x] I have added my name to CONTRIBUTORS.md
[ ] I have updated CHANGES.md with a short summary of my change
[ ] I have added or updated unit tests to ensure consistent code coverage
[ ] I have update the inline documentation, and included code examples where relevant
[x] I have performed a self-review of my code

Thanks @lilleyse!


Add jacoco test and action

Add Jacoco to build
Add publish jacoco build to PR action
https://github.com/finos-labs/architecture-as-code/issues/189

Do not merge please - for reasons Im trying to work out - its not finding the file :(

something to come back to - i need to do some more research cos all the googling on how to solve this hasnt work :(
Ready to merge - unless you want the disabled action code removed? @rocketstack-matt @Budlee


[Bug] [WOQL] method re

There is a bug in WOQL.re, please check with JSON-LD syntex

Fixed in 1.1.3


Line 544 summary table it's not MSE it's MAE

In the "recommenders/examples/03_evaluate/evaluation.ipynb" summary table (2.1.7) of rating metrics, it's  MAE, not MSE
Description

Related Issues

Checklist:

[ ] I have followed the contribution guidelines and code style for this project.
[ ] I have added tests covering my contributions.
[ ] I have updated the documentation accordingly.
[ ] This PR is being made to staging branch and not to master branch.

thanks!

thanks!


Add comment for iterationCountKES function

iterationCountKES should return the number of times a KES signature key has already been updated

I'd be happy to rename this. Would updateCountKES be ok?

I'd be happy to rename this. Would updateCountKES be ok?

I'd prefer that, but I think better still would be for update to take an argument (which period to move forward to); if that change is made, it's less that we are counting how often we updated but rather "what is the current period" I guess..?

ok, fine with me. Then both passing a past period or a future period with too many evolutions would result in Nothing, right?

Just thinking out loud: perhaps a past period should result in an exception instead? In other words, update would take a precondition in terms of (the renamed vesion of) udpateCount? After all, doing so is a bug, whereas exceeding it's period is just something that can happen  and should be taken into account?


Add timeout parameter to invoke powerbi rest method

In the event that the server is taking longer than the default client time out (100 seconds), client will prematurely end the request before the server has finished processing.
Allow consumers of this cmdlet to optionally specify a client timeout value.
This is similar in behavior to Powershell Invoke-RestMethod.

Spoke to @CattieCat offline and decided to keep the default timeout behavior as is.


Revert suppression of touchstart to fix regressions

Details
Partially reverts https://github.com/Expensify/Expensify.cash/pull/3659/files, particularly this commit to fix two major regressions (my fault for not noticing during my testing).
Fixed Issues
$ https://github.com/Expensify/Expensify.cash/issues/3806
Tests / QA Steps

Verify that you can scroll through a chat on mobile web.
Verify that you can open the "edit chat" input, then close it too.

Tested On

[x] Web
[x] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots
Web

Mobile Web

Desktop

iOS

Android

:warning: :warning: Heads up! This pull request has the CP Staging label. :warning: :warning:
Merging it will cause it to be immediately deployed to staging, even if the open StagingDeployCash deploy checklist is locked.

This PR needs to be merged ASAP. There are more than 4 regeressions.

🚀 Cherry-picked to staging in version: 1.0.75-2🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Protege failed to open ontology file after working with OntopPro

Steps to reproduce:

Create a new ontology
Create a class, e.g., A.
Create annotation assertion for class A, e.g., rdfs:comment "This is just a testing". Add a language tag: "en".
Switch to "Ontop Mappings" tab and create a datasource (can be just dummy input parameters)
Select "Test Connection" (and ignore the error message)
Save the ontology, e.g., test.owl. OntopPro will create an extra file test.obda
Close test.owl
Re-open test.owl
Create another class, e.g., B
Save the ontology
Close test.owl
Re-open test.owl
An exception will be thrown: "The prefix "xml" cannot be bound to any namespace other than its usual namespace; neither can the namespace for "xml" be bound to any prefix other than "xml"."

This steps might look arbitrary but the purpose is to have an .obda file (step 4, 5) and then make an ontology modification after working with the plugin (step 6-12). The focus of the error is the introduction of xml:lang in the ontology (step 3).

In addition, I found inconsistency between OBDA and OWL/Protege for xml prefix label.
OBDA: xml=http://www.w3.org/XML/1998/namespace#
OWL/Protege: xml=http://www.w3.org/XML/1998/namespace
The prior is more correct (reference: https://www.w3.org/TR/xml-names11/)
The prefix xml is by definition bound to the namespace name http://www.w3.org/XML/1998/namespace.

Fixed in 3a464de6e9d9e29927f0ec2ec6ea8b730e6000e1


Requirement for accessing external public URL's from pods

We  have a huge cluster and whenever we want the deployment to communicate to the public URL's..We will have to open up proxy for all the nodes in the cluster (as we are behind a proxy)
Whenever we add a new node we need to make sure all of the rules are working as the kubernetes pods can spin anywhere in the cluster..
Can this requirement be achieved using any of the network policies in this project?(Im pretty new to this concept and I guess there can be some egress rules written)

Stackoverflow is a better forum for questions like these.


Introduce a DynamicMethodReturnTypeExtension for the DBAL QueryBuilde…

…r execute method
fixes https://github.com/phpstan/phpstan-doctrine/issues/117
As mentioned in the issue above, this is a first try to provide a solution.
I would like to write a test for this new extension, but I don't know how to start here. I already added a test class, which also contains a mock, which I would like to test.

Hi, thanks. Extensions aren't tested like this. You simply write some code under https://github.com/phpstan/phpstan-doctrine/tree/master/tests/DoctrineIntegration/ORM, verify that it has a false positive without the extension, and that the extension solves the problem and no error is reported.
It's enough to create a new .php file under data/, add it to EntityManagerIntegrationTest.php::dataTopics() and run EntityManagerIntegrationTest.php. It will update the JSON files with expectations.

Hi, thanks. Extensions aren't tested like this. You simply write some code under https://github.com/phpstan/phpstan-doctrine/tree/master/tests/DoctrineIntegration/ORM, verify that it has a false positive without the extension, and that the extension solves the problem and no error is reported.
It's enough to create a new .php file under data/, add it to EntityManagerIntegrationTest.php::dataTopics() and run EntityManagerIntegrationTest.php. It will update the JSON files with expectations.

hey @ondrejmirtes
thanks for the hints. I implemented a test case successfully and it looks quite good imo :blush:

hey @ondrejmirtes
thanks for the hints. I implemented a test case successfully and it looks quite good imo :blush:

how could this be fixed? the tests are failing on lowest dependencies
-        "message": "Cannot call method fetchAll() on Doctrine\\DBAL\\Driver\\ResultStatement|int.",
+        "message": "Cannot call method fetchAll() on Doctrine\\DBAL\\Driver\\Statement|int.",

how could this be fixed? the tests are failing on lowest dependencies
-        "message": "Cannot call method fetchAll() on Doctrine\\DBAL\\Driver\\ResultStatement|int.",
+        "message": "Cannot call method fetchAll() on Doctrine\\DBAL\\Driver\\Statement|int.",

@mitelg Two possible solutions:

Figure out why it's failing and write the code such as it works on both highest and lowest dependencies.
Bump the lowest version in require-dev so that it works without change in code.

@mitelg Two possible solutions:

Figure out why it's failing and write the code such as it works on both highest and lowest dependencies.
Bump the lowest version in require-dev so that it works without change in code.

I bumped the lowest version of the doctrin/dbal requirement. so now, everything should be fine :+1:

I bumped the lowest version of the doctrin/dbal requirement. so now, everything should be fine :+1:

hey @ondrejmirtes
I reduced the code in QueryBuilderExecuteMethodExtension to only support the first test case. I left the other test cases, to make use of them in the future.
Unfortunately I'm still in the beginning of understanding the internals of PHPStan and how things are done. If you could guide me, I will take care of the other cases in another PR

hey @ondrejmirtes
I reduced the code in QueryBuilderExecuteMethodExtension to only support the first test case. I left the other test cases, to make use of them in the future.
Unfortunately I'm still in the beginning of understanding the internals of PHPStan and how things are done. If you could guide me, I will take care of the other cases in another PR

Perfect, thank you!

Perfect, thank you!


Enable Performance Insights and Autoscaling

what

Added support for enabling performance insight
Added cluster autoscaling

caveats

not applicable for t2.small, t2.medium and t2.large.

Code needs formatting...
``
Terraform configuration needs linting. Run '/home/travis/build/cloudposse/terraform-aws-rds-cluster/build-harness/vendor/terraform fmt'

main.tf
variables.tf`

@rverma-nikiai looks like variables.tf still needs linting

Needs another rebase too =)

@rverma-nikiai going through some of the open PRs and saw this wasn't updated =)

@osterman applied all the suggestions.


updated the nuget and client packages to fix compile issues

This PR is to fix the build errors related to the "deployment error #70"

I will submit a new one


import types from the library without including it in the webpack builder

Hi team,
I changed the following line from:
import Quagga, { QuaggaJSResultObject } from '@ericblade/quagga2';

to:
import { QuaggaJSResultObject, QuaggaJSStatic } from '@ericblade/quagga2/type-definitions/quagga';

to avoid including it in the build, however it's still be included, not sure how can I avoid including it?

The reason behind doing this is because I dynamically import it separately rather bundling it within the vendor.js to reduce initial loading time and improve the apps performance.
Can you please help?

Hi!  If you're using TypeScript, recent versions add a "import type" capability
import { type QuaggaJSResultObject, type QuaggaJSStatic } from ...

which would allow you to reference it, and it would be stripped when TSC is done with it.
Otherwise, it sounds like some advanced webpack configuration that I'm afraid I know extremely little about.

Thanks @ericblade! I did that but it would be there still, so I knew I had to look somewhere else till I learned that I am using https://www.npmjs.com/package/ngx-barcode-scanner which adds it. Moving it's import to the right place helped me solving the problem.
Many thanks! Issue solved.

great to hear!


fix(orchestrator): warn "unknown format X ignored in schema at path Y"

During backstage startup there are warnings like:
unknown format "date-time" ignored in schema at path "#/oneOf/0/properties/ended"
due to a bug in OpenAPIBackend issue.
Resolves FLPATH-1045
Based on Yaron Dayagi<EMAIL_ADDRESS>work in notification plugin.

/approve


Module not found

Hey there,
Was interested in trying this out but get Module not found after installing and importing.
Steps to reproduce

yarn add figma-view

import FigmaView, { FigmaAuthenticationProvider } from "figma-view"

<FigmaAuthenticationProvider accessToken={MY_TOKEN}>
      <FigmaView url="https://figma.com/files/TR2lvISZ4PuI52bdDNxRIL?node-id=11-95"/>
</FigmaAuthenticationProvider>

Any ideas on why this would be happening?

I'm getting the same error when trying to use the module.


go build fails

I'm trying example but not compiles
acs@E5500:~/Coding/goblockᛤ go version
go version go1.5.1 linux/amd64

acs@E5500:~/Coding/goblockᛤ go build main.go
# command-line-arguments
./main.go:4: imported and not used: "github.com/alfg/blockchain"
./main.go:10: undefined: New

Sorry I missed this. Is this still an issue?
Also, did you go get github.com/alfg/blockchain first?


add 3rd party pod security options

Signed-off-by: Jim Bugwadia<EMAIL_ADDRESS>
add Kubewarden and Kyverno to match PSS docs
order projects alphabetically

/approve

/lgtm


win_secedit win32 fixes

Both win32_group and win32_useraccount would take upward of 5 minutes to complete on some systems, making it look like Nova was hanging.  I have modified both of these commands to only look at local accounts, and it has sped up the process considerably

👍


Ember 1.12 compatibility

Initializers are now split in general and instance initializers.

Thanks for the update, I'll be taking a look at getting this updated here shortly.


updated admin page

Cleaned up admin page so it does not  for models.
Refrences #153

Also...even existing code doesn't work properly, it crashed for me sometimes, so please do it seriously 🤗


chore(main): release 1.11.3

:robot: I have created a release beep boop
1.11.3 (2023-01-29)
Miscellaneous Chores

deps: bump actions/checkout to v3 (f8346dd)
deps: bump axios from 1.2.3 to 1.2.4 (9319062)
deps: bump axios from 1.2.3 to 1.2.4 (#317) (4ba7d7f)
deps: bump axios from 1.2.4 to 1.2.5 (168aeab)
deps: bump axios from 1.2.5 to 1.2.6 (403e394)
deps: bump livewire/livewire from 2.11.0 to 2.11.1 (8fe9a44)
deps: bump maatwebsite/excel from 3.1.45 to 3.1.46 (abee315)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/rotex1800/registration/releases/tag/v1.11.3 :sunflower:


help me

hi and thanks for useful repo.
why when i play the yottube playlist, bot play only 25 files from playlist?
ia a way to play whole playlist?

for the first playlist it's 25 , but it plays all the lists in the playlist, check total in LOG


Unable to withdraw from BTC Vault

Overview
When attmpting to withdraw from BTC vault it comes up with "Something went wrong" error
References and additional details

log into app.shapeshift.com and connect to wallet that supports thorchain savers
Navigate to Defi page and attempt to withdraw from BTC Thorchain Saver
Note that there is the error "Something went wrong"
*on my first attempt, it spun continuously on Continue. Clicked out of it and tried again. On second attempt could broadcast tx and thats when the error appeared.

Acceptance Criteria
Should be able to withdraw from BTC Vault
Need By Date
No response
Screenshots/Mockups
No response
Ownership

[X] If my bounty needs engineering or needs product I have added the respective labels on the right
[X] As the sponsor of this bounty I will review the changes in a preview environment (ops/product) or review the PR (engineering)

Estimated effort
No response
Sponsor / Stakeholder
No response
Bounty Hunters

Join our discord
Include an expected timeline for you to complete work in the work plan when you apply for this bounty!
Please refer to this link for some basic info
Please do not start work on this issue until you are approved in Gitcoin.

This may be for all UTXO's. same thing happened with LTC. was able to successfully withdraw from Eth vault though.

Withdraw is working but noticing the modal isnt updating once completed on the blockchain. Does this warrant a different ticket @gomesalexandre  or shall i leave this one open?

Nevermind, it did eventually. closing this ticket!


HSV: Live feed works but no events are recorded in HSV interface, even when set to Stream & Allow Recording

Describe the bug
Using HSV, camera shows up, live feed works, but nothing is recorded, even when set to Stream & Allow Recording in  Recording Options within HomeKit.  Some other people (ex. quinn2244) are having the same problem on reddit: https://www.reddit.com/r/HomeKit/comments/s2xygx/comment/hshk401/?utm_source=share&utm_medium=web2x&context=3
I've tried with and without audio.  I've waited over 24 hours.  Events show up in the Wyze app interface but not in the HomeKit interface.  The only thing that shows in the HomeKit interface is the live stream.  I have other native HKSV cameras and they work fine with events in the HSV timeline.
To Reproduce
Setup Wyze v3 RTSP camera with config file below.
Expected behavior
Recording of events in HSV timeline.
Logs
No errors in logs.
Screenshots

Environment

Node.js Version: v17.3.0
Homebridge Version: v1.4.0 beta4
Camera UI Version: v5.06
Operating System: macOS 12.1
Browser: N/A
Config file:

{
    "name": "CameraUI",
    "debug": false,
    "mqtt": {
        "active": false
    },
    "http": {
        "active": false,
        "localhttp": false
    },
    "smtp": {
        "active": false
    },
    "ftp": {
        "active": false
    },
    "ssl": {
        "active": false
    },
    "options": {
        "videoProcessor": "/opt/homebrew/bin/ffmpeg"
    },
    "cameras": [
        {
            "name": "FrontYardCam",
            "manufacturer": "Wyze",
            "model": "WyzeCam v3",
            "motion": true,
            "unbridge": true,
            "hsv": true,
            "prebufferLength": 4,
            "videoConfig": {
                "source": "-i<EMAIL_ADDRESS>                "maxStreams": 1,
                "vcodec": "copy",
                "acodec": "libfdk_aac",
                "packetSize": 188,
                "stimeout": 0,
                "audio": true
            },
            "videoanalysis": {
                "active": false
            }
        },
        {
            "prebufferLength": 4,
            "videoConfig": {
                "stimeout": 0
            },
            "videoanalysis": {
                "active": false
            }
        }
    ],
    "platform": "CameraUI"
}

You need to enable some kind of motion detection. You have several options to pass the motion info from your camera to camera.ui
Without these, camera.ui will not recognize any motion
a) However, if your camera can send am email on motion detection, so enable the SMTP server in the config, and adjust the camera email settings to camera.ui as destination (and camera name as target email adress, eg<EMAIL_ADDRESS>b) If your camera supports MQTT notification, enable the MQTT Client in the config json, in your camera block, you can add a "motionMessage" (string or a object) and a "motionTopic" (topic/suffix)
c) If your camera can upload images on motion detection via FTP, enable the FTP Server within config.json. Adjust the camera ftp settings to camera.ui as destination and add as path the camera name
TL:DR
d) If all this doesn't work, and you just want camera.ui to do everything itself, enable "videoanalysis" in config.json and restart HB

@eperitus try this config
{
    "name": "CameraUI",
    "debug": false,
    "mqtt": {
        "active": false
    },
    "http": {
        "active": false,
        "localhttp": false
    },
    "smtp": {
        "active": false
    },
    "ftp": {
        "active": false
    },
    "ssl": {
        "active": false
    },
    "options": {
        "videoProcessor": "/opt/homebrew/bin/ffmpeg"
    },
    "cameras": [
        {
            "name": "FrontYardCam",
            "manufacturer": "Wyze",
            "model": "WyzeCam v3",
            "motion": true,
            "unbridge": true,
            "hsv": true,
            "prebufferLength": 4,
            "videoConfig": {
                "source": "-i<EMAIL_ADDRESS>                "maxStreams": 1,
                "vcodec": "copy",
                "acodec": "libfdk_aac",
                "stimeout": 10,
                "audio": true
            },
            "videoanalysis": {
                "active": true
            }
        }
    ],
    "platform": "CameraUI"
}

Thanks very much @seydx , with the config you suggested, I now get this in the log:
[1/13/2022, 7:30:07 PM] [CameraUI] FrontYardCam: Videoanalysis scheduled for restart at 3AM: 450 minutes
This sounds promising.  I'll check again tomorrow to see if any events are recorded in HomeKit.
Where is the video stored while it is awaiting analysis?  Some path on my computer?  Or does it stay on the camera's SD card until camera.ui needs it?  I'm wondering how big it can get at 1080p, if it gets cleaned up (on the computer) after analysis + upload to iCloud, and if I have enough space locally ...

with the config above, the hsv recordings will be 20-22s, a video with 1920x1080 will be 2-3mb
To save the hsv recordings also locally, you need to enable recording in the interface
The default port (when not set in config) is 8081 for the interface
So, open http://localhost:8081 (maybe change localhost with ip where camera.ui is running)
Default credentials are:
username: master
password: master
if successfully logged in, go to Settings > Recordings, there you can adjust everything

Just got my first motion event in HSV!  It was about 15 seconds.  A little late capturing a vehicle but it came through.
I don't need to save the recordings locally, just in HSV is fine.  Just wondering if they were analyzed locally and if they were cleaned up.
Didn't know about the 8081 interface - thanks!

Enable prebuffering if you want the event before motion has triggered
{
    "name": "CameraUI",
    "debug": false,
    "mqtt": {
        "active": false
    },
    "http": {
        "active": false,
        "localhttp": false
    },
    "smtp": {
        "active": false
    },
    "ftp": {
        "active": false
    },
    "ssl": {
        "active": false
    },
    "options": {
        "videoProcessor": "/opt/homebrew/bin/ffmpeg"
    },
    "cameras": [
        {
            "name": "FrontYardCam",
            "manufacturer": "Wyze",
            "model": "WyzeCam v3",
            "motion": true,
            "unbridge": true,
            "hsv": true,
            "prebuffering": true,
            "prebufferLength": 4,
            "videoConfig": {
                "source": "-i<EMAIL_ADDRESS>                "maxStreams": 1,
                "vcodec": "copy",
                "acodec": "libfdk_aac",
                "stimeout": 10,
                "audio": true
            },
            "videoanalysis": {
                "active": true
            }
        }
    ],
    "platform": "CameraUI"
}

Just got my first motion event in HSV! It was about 15 seconds. A little late capturing a vehicle but it came through.
Did you have to modify any of the cam settings w/ in the Wyze app?

Just got my first motion event in HSV! It was about 15 seconds. A little late capturing a vehicle but it came through.
Did you have to modify any of the cam settings w/ in the Wyze app?

enable "prebuffering" in your config

Appologies!
I do have it.
        {
            "name": "CameraUI",
            "debug": false,
            "mqtt": {
                "active": false
            },
            "http": {
                "active": false,
                "localhttp": false
            },
            "smtp": {
                "active": false
            },
            "ftp": {
                "active": false
            },
            "ssl": {
                "active": false
            },
            "cameras": [
                {
                    "name": "ToWn3r-WyzeCamv3",
                    "manufacturer": "Wyze Labs, Inc.",
                    "model": "WyzeCam v3",
                    "motion": true,
                    "unbridge": true,
                    "hsv": true,
                    "prebuffering": true,
                    "prebufferLength": 4,
                    "videoConfig": {
                        "source": "-i<EMAIL_ADDRESS>                        "maxStreams": 1,
                        "vcodec": "copy",
                        "acodec": "libfdk_aac",
                        "stimeout": 10,
                        "audio": false
                    },
                    "videoanalysis": {
                        "active": true
                    }
                }
            ],
            "platform": "CameraUI"

Appologies! I do have it.
        {
            "name": "CameraUI",
            "debug": false,
            "mqtt": {
                "active": false
            },
            "http": {
                "active": false,
                "localhttp": false
            },
            "smtp": {
                "active": false
            },
            "ftp": {
                "active": false
            },
            "ssl": {
                "active": false
            },
            "cameras": [
                {
                    "name": "ToWn3r-WyzeCamv3",
                    "manufacturer": "Wyze Labs, Inc.",
                    "model": "WyzeCam v3",
                    "motion": true,
                    "unbridge": true,
                    "hsv": true,
                    "prebuffering": true,
                    "prebufferLength": 4,
                    "videoConfig": {
                        "source": "-i<EMAIL_ADDRESS>                        "maxStreams": 1,
                        "vcodec": "copy",
                        "acodec": "libfdk_aac",
                        "stimeout": 10,
                        "audio": false
                    },
                    "videoanalysis": {
                        "active": true
                    }
                }
            ],
            "platform": "CameraUI"

What does not work with it?

I enabled prebuffering and didn't modify any settings in the Wyze app.  I am using the rest of the config above but the HSV interface is showing fewer events than the Wyze camera app.
For example, I have 3 events total in HSV in the past 24 hours, and well over 30 events in Wyze.
I see a lot of this in the log:
[1/14/2022, 2:00:31 PM] [CameraUI] FrontYardCam: Skip saving the recording, the file might be corrupted because the recording process was cancelled by HSV
[1/14/2022, 2:00:38 PM] [CameraUI] FrontYardCam: Motion OFF - Motion handler timeout.
[1/14/2022, 2:03:19 PM] [CameraUI] FrontYardCam: Motion OFF
[1/14/2022, 2:10:05 PM] [CameraUI] FrontYardCam: Motion ON
[1/14/2022, 2:10:12 PM] [CameraUI] FrontYardCam: Closing recording process
I also see "Camera Not Available - Wait until someone else in this home stops viewing this camera and try again" in the Home app for the Wyze camera - but nobody else is viewing it.
Should I open a new issue for this or is OK to keep it in this thread?

No motion is detected so nothing is recorded to HSV
tried adding and removing the camera from homekit being i originally had it added via Homebridge Camera FFmpeg and just copied it's config values over to Homebridge Camera Ui followed by removing it from Camera FFmpeg.
Didn't have to re-add it. So i did just to be safe.

I enabled prebuffering and didn't modify any settings in the Wyze app. I am using the rest of the config above but the HSV interface is showing fewer events than the Wyze camera app.
For example, I have 3 events total in HSV in the past 24 hours, and well over 30 events in Wyze.
I see a lot of this in the log: [1/14/2022, 2:00:31 PM] [CameraUI] FrontYardCam: Skip saving the recording, the file might be corrupted because the recording process was cancelled by HSV [1/14/2022, 2:00:38 PM] [CameraUI] FrontYardCam: Motion OFF - Motion handler timeout. [1/14/2022, 2:03:19 PM] [CameraUI] FrontYardCam: Motion OFF [1/14/2022, 2:10:05 PM] [CameraUI] FrontYardCam: Motion ON [1/14/2022, 2:10:12 PM] [CameraUI] FrontYardCam: Closing recording process
I also see "Camera Not Available - Wait until someone else in this home stops viewing this camera and try again" in the Home app for the Wyze camera - but nobody else is viewing it.
Should I open a new issue for this or is OK to keep it in this thread?

Open Interface > Settings > Cameras > Select Camera > Videoanalysis > Adjust sensitivity (lower should result in more events
camera.ui has a "persistent" connection to the camera (when prebuffering is active), I assume that is what is meant by this

No motion is detected so nothing is recorded to HSV
tried adding and removing the camera from homekit being i originally had it added via Homebridge Camera FFmpeg and just copied it's config values over to Homebridge Camera Ui followed by removing it from Camera FFmpeg.
Didn't have to re-add it. So i did just to be safe.

Restart HB, trigger motion, post the log here pls

I disabled prebuffering (this worked to alleviate the camera not available problem) and decreased the sensitivity from 50 down to 20.  No new events yet but I'll keep checking.  Thanks again seydx!

I disabled prebuffering (this worked to alleviate the camera not available problem) and decreased the sensitivity from 50 down to 20. No new events yet but I'll keep checking. Thanks again seydx!

The next version v5.0.7 (still under development) will let you to customize the videoanalysis process more through the ui, and also the timer for retrigger a new motion is lower, may this will fix it for you
but till then keep checking your log

No motion is detected so nothing is recorded to HSV
tried adding and removing the camera from homekit being i originally had it added via Homebridge Camera FFmpeg and just copied it's config values over to Homebridge Camera Ui followed by removing it from Camera FFmpeg.
Didn't have to re-add it. So i did just to be safe.

Restart HB, trigger motion, post the log here pls

By Trigger Motion do you mean just dance in front of the camera and see if i get something like:
I don't get anything liek this: [1/14/2022, 2:10:05 PM] [CameraUI] FrontYardCam: Motion ON
[14/01/2022, 16:44:20] [CameraUI] ToWn3r-WyzeCamv3: Prebuffering scheduled for restart at 2AM: 556 minutes
[14/01/2022, 16:44:20] [CameraUI] ToWn3r-WyzeCamv3: Incoming ping request for<EMAIL_ADDRESS>- Timeout: 1s
[14/01/2022, 16:44:20] [CameraUI] ToWn3r-WyzeCamv3: Pinging <IP_ADDRESS>:80
[14/01/2022, 16:44:20] [CameraUI] ToWn3r-WyzeCamv3: Pinging <IP_ADDRESS>:80 - successful
[14/01/2022, 16:44:20] [CameraUI] ToWn3r-WyzeCamv3: Start videoanalysis...
[14/01/2022, 16:44:20] [CameraUI] ToWn3r-WyzeCamv3: Videoanalysis command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel error -hwaccel auto -analyzeduration 0 -probesize 500000 -f mpegts -i tcp://<IP_ADDRESS>:27064 -an -vcodec pam -pix_fmt rgb24 -f image2pipe -vf fps=2,scale=640:360 pipe:1
[14/01/2022, 16:44:20] [CameraUI] ToWn3r-WyzeCamv3: Videoanalysis: Sensitivity: 25 - Active zones: []
[14/01/2022, 16:44:20] [CameraUI] ToWn3r-WyzeCamv3: Videoanalysis scheduled for restart at 3AM: 616 minutes
[14/01/2022, 16:44:20] [CameraUI] ToWn3r-WyzeCamv3: Configuring unbridged accessory...
[14/01/2022, 16:44:20] [CameraUI] ToWn3r-WyzeCamv3: Setting up accessory...
[14/01/2022, 16:44:20] [CameraUI] ToWn3r-WyzeCamv3: Adding motion sensor service
[14/01/2022, 16:44:20] [CameraUI] ToWn3r-WyzeCamv3: Initializing HomeKit Secure Video
[14/01/2022, 16:44:20] [CameraUI] camera.ui v5.0.6 is listening on port 8081 (http)
[14/01/2022, 16:44:20] ToWn3r-WyzeCamv3 8736 is running on port 46689.

[14/01/2022, 16:46:49] [CameraUI] ToWn3r-WyzeCamv3: Snapshot requested: 1280 x 720 [14/01/2022, 16:46:49] [CameraUI] ToWn3r-WyzeCamv3: Snapshot command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel error -analyzeduration 0 -probesize 731696 -f mpegts -i tcp://<IP_ADDRESS>:33782 -frames:v 1 -f image2 - [14/01/2022, 16:46:50] [CameraUI] ToWn3r-WyzeCamv3: Prebuffer request ended [14/01/2022, 16:46:50] [CameraUI] ToWn3r-WyzeCamv3: Fetching snapshot took 1.465 seconds. [14/01/2022, 16:46:50] [CameraUI] ToWn3r-WyzeCamv3: Sending snapshot: 1280x720 [14/01/2022, 16:46:50] [CameraUI] ToWn3r-WyzeCamv3: Resize command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -i pipe: -frames:v 1 -filter:v scale='min(1280,iw)':'min(720,ih)':force_original_aspect_ratio=decrease -f image2 - [14/01/2022, 16:46:51] [CameraUI] ToWn3r-WyzeCamv3: Start stream requested: 1280x720, 30 fps, 299 kbps [14/01/2022, 16:46:51] [CameraUI] ToWn3r-WyzeCamv3: Incoming ping request for<EMAIL_ADDRESS>- Timeout: 1s [14/01/2022, 16:46:51] [CameraUI] ToWn3r-WyzeCamv3: Pinging <IP_ADDRESS>:80 [14/01/2022, 16:46:51] [CameraUI] ToWn3r-WyzeCamv3: Pinging <IP_ADDRESS>:80 - successful [14/01/2022, 16:46:51] [CameraUI] ToWn3r-WyzeCamv3: Setting prebuffer stream as input [14/01/2022, 16:46:51] [CameraUI] ToWn3r-WyzeCamv3: Starting video stream: native [14/01/2022, 16:46:51] [CameraUI] ToWn3r-WyzeCamv3: Stream command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel level -analyzeduration 0 -probesize 740156 -f mpegts -i tcp://<IP_ADDRESS>:32596 -an -sn -dn -vcodec copy -pix_fmt yuv420p -color_range mpeg -f rawvideo -payload_type 99 -ssrc 2148188 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params qRsOnxhpyC1Cu4BXdoqNWBqRojl08Od9nKgaaBoO srtp://<IP_ADDRESS>:59192?rtcpport=59192&pkt_size=1318 -progress pipe:1 [14/01/2022, 16:46:52] [CameraUI] ToWn3r-WyzeCamv3: Getting the first frames took 1.545 seconds. [14/01/2022, 16:46:55] [CameraUI] ToWn3r-WyzeCamv3: Stop stream requested [14/01/2022, 16:46:55] [CameraUI] ToWn3r-WyzeCamv3: Stopped video stream. [14/01/2022, 16:46:55] [CameraUI] ToWn3r-WyzeCamv3: Prebuffer request ended [14/01/2022, 16:46:55] [CameraUI] ToWn3r-WyzeCamv3: FFmpeg exited with code: null and signal: SIGKILL (Expected) [14/01/2022, 16:47:42] [CameraUI] ToWn3r-WyzeCamv3: Motion detected via Videoanalysis: {"name":"all","diffs":206637,"total":230400,"percent":89.68619537353516} [14/01/2022, 16:47:42] [CameraUI] ToWn3r-WyzeCamv3: Motion ON [14/01/2022, 16:47:42] [CameraUI] ToWn3r-WyzeCamv3: Handling through extern controller.. [14/01/2022, 16:47:42] [CameraUI] ToWn3r-WyzeCamv3: Video fragments requested from HSV [14/01/2022, 16:47:42] [CameraUI] ToWn3r-WyzeCamv3: Setting prebuffer stream as input [14/01/2022, 16:47:42] [CameraUI] ToWn3r-WyzeCamv3: Prebuffer requested with a duration of -4s [14/01/2022, 16:47:42] [CameraUI] ToWn3r-WyzeCamv3: Start recording... [14/01/2022, 16:47:42] [CameraUI] ToWn3r-WyzeCamv3: Recording command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -analyzeduration 0 -probesize 500000 -f mp4 -i tcp://<IP_ADDRESS>:23801 -f mp4 -vcodec copy -an -movflags frag_keyframe+empty_moov+default_base_moof -max_muxing_queue_size 1024 tcp://<IP_ADDRESS>:12982 [14/01/2022, 16:47:42] [CameraUI] ToWn3r-WyzeCamv3: Recording started [14/01/2022, 16:47:57] [CameraUI] ToWn3r-WyzeCamv3: Motion OFF - Motion handler timeout. [14/01/2022, 16:48:00] [CameraUI] ToWn3r-WyzeCamv3: Recording completed (HSV) [14/01/2022, 16:48:00] [CameraUI] ToWn3r-WyzeCamv3: New custom alert [14/01/2022, 16:48:00] [CameraUI] ToWn3r-WyzeCamv3: Notifications not enabled, skip Webhook.. [14/01/2022, 16:48:00] [CameraUI] ToWn3r-WyzeCamv3: Notifications not enabled, skip Alexa.. [14/01/2022, 16:48:00] [CameraUI] ToWn3r-WyzeCamv3: Recording not enabled, skip recording.. [14/01/2022, 16:48:00] [CameraUI] ToWn3r-WyzeCamv3: Recording skipped. Notification skipped. [14/01/2022, 16:48:01] [CameraUI] ToWn3r-WyzeCamv3: Closing recording process [14/01/2022, 16:48:01] [CameraUI] ToWn3r-WyzeCamv3: Prebuffer request ended [14/01/2022, 16:48:01] [CameraUI] ToWn3r-WyzeCamv3: FFmpeg recording process exited (expected) [14/01/2022, 16:49:12] [CameraUI] ToWn3r-WyzeCamv3: Motion OFF [14/01/2022, 16:49:12] [CameraUI] ToWn3r-WyzeCamv3: Handling through extern controller.. [14/01/2022, 16:53:53] [CameraUI] ToWn3r-WyzeCamv3: Snapshot requested: 1280 x 720 [14/01/2022, 16:53:53] [CameraUI] ToWn3r-WyzeCamv3: Snapshot command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel error -analyzeduration 0 -probesize 599156 -f mpegts -i tcp://<IP_ADDRESS>:31980 -frames:v 1 -f image2 - [14/01/2022, 16:53:54] [CameraUI] ToWn3r-WyzeCamv3: Prebuffer request ended [14/01/2022, 16:53:54] [CameraUI] ToWn3r-WyzeCamv3: Fetching snapshot took 0.618 seconds. [14/01/2022, 16:53:54] [CameraUI] ToWn3r-WyzeCamv3: Sending snapshot: 1280x720 [14/01/2022, 16:53:54] [CameraUI] ToWn3r-WyzeCamv3: Resize command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -i pipe: -frames:v 1 -filter:v scale='min(1280,iw)':'min(720,ih)':force_original_aspect_ratio=decrease -f image2 - [14/01/2022, 16:54:04] [CameraUI] ToWn3r-WyzeCamv3: Snapshot requested: 1280 x 720 [14/01/2022, 16:54:04] [CameraUI] ToWn3r-WyzeCamv3: Snapshot command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -hide_banner -loglevel error -analyzeduration 0 -probesize 561180 -f mpegts -i tcp://<IP_ADDRESS>:25931 -frames:v 1 -f image2 - [14/01/2022, 16:54:06] [CameraUI] ToWn3r-WyzeCamv3: Prebuffer request ended [14/01/2022, 16:54:06] [CameraUI] ToWn3r-WyzeCamv3: Fetching snapshot took 1.39 seconds. [14/01/2022, 16:54:06] [CameraUI] ToWn3r-WyzeCamv3: Sending snapshot: 1280x720 [14/01/2022, 16:54:06] [CameraUI] ToWn3r-WyzeCamv3: Resize command: /usr/local/lib/node_modules/homebridge-camera-ui/node_modules/ffmpeg-for-homebridge/ffmpeg -i pipe: -frames:v 1 -filter:v scale='min(1280,iw)':'min(720,ih)':force_original_aspect_ratio=decrease -f image2 -

ohh! looks like its starting to record things

@eperitus did the home app notify you of motion?
is it detecting people or animals yet?

Not yet, and I walked by it 3 different times.  HSV detected 3 vehicles overnight but nothing since this morning or afternoon, and there have been plenty of people and vehicles going by.  So I'm not sure the sensitivity setting is working.  Meanwhile, the Wyze app is showing all of the events, and my other native HomeKit cameras are reporting events in HSV.
I just restarted homebridge and will see if any new events occur.

Videoanalysis is all done locally correct? it's not being sent to like your server, right? 😅

Videoanalysis is all done locally correct? it's not being sent to like your server, right? 😅

everything is done locally, also your database for camera.ui which contains all information like user credentials, recordings etc stored locally

Figured as much. :) Thanks for confirming.
Installing the v5.0.7 beta 1.....jk
`USER: pi
DIR: /usr/local
CMD: sudo -E -n npm install -g<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm ERR! code ERR_SSL_DECRYPTION_FAILED_OR_BAD_RECORD_MAC
npm ERR!<PHONE_NUMBER>:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:../deps/openssl/openssl/ssl/record/ssl3_record.c:677:
npm ERR!
npm ERR!  Please review log for details.`

Figured as much. :) Thanks for confirming.
Installing the v5.0.7 beta 1.....jk
USER: pi
DIR: /usr/local
CMD: sudo -E -n npm install -g<EMAIL_ADDRESS>
npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm ERR! code ERR_SSL_DECRYPTION_FAILED_OR_BAD_RECORD_MAC
npm ERR!<PHONE_NUMBER>:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:../deps/openssl/openssl/ssl/record/ssl3_record.c:677:
npm ERR!

npm ERR!  Please review log for details.

Oh, were you running v5.0.6 before without any problems? Which node version?

Node v16.13.2
Npm v8.3.1

False alarm.
Third attempt seems to have worked.

v5.0.7-beta.3 is online with better videoanalysis and several bugfixes
sudo npm i -g<EMAIL_ADDRESS>

I'm getting this message but recordings still don't show up. I've tried hsv and with the interface. This is the output with recording using the interface, but there are no recordings when I go to find them.
VIDEOANALYSIS: New message: Data: [{"zone":"region0","percent":49.54426956176758,"sensitivity":51,"dwell":60,"forceClose":3}] - Motion: detected - Camera: Office Cam [1/24/2023, 10:24:42 AM] [CameraUI] Office Cam: Skip motion trigger. At Home is active and Office Cam is not excluded! [1/24/2023, 10:24:44 AM] [CameraUI] Office Cam: New motion detected, resetting motion in 60s.. [1/24/2023, 10:24:44 AM] [CameraUI] Office Cam: Motion data: [{"zone":"region0","percent":42.17881774902344,"sensitivity":59,"dwell":60,"forceClose":3}]} [1/24/2023, 10:24:46 AM] [CameraUI] Office Cam: New motion detected, resetting motion in 60s.. [1/24/2023, 10:24:46 AM] [CameraUI] Office Cam: Motion data: [{"zone":"region0","percent":46.7890625,"sensitivity":54,"dwell":60,"forceClose":3}]} [1/24/2023, 10:25:00 AM] [Home Alarm] SSAPI socket heartbeat [1/24/2023, 10:25:03 AM] [CameraUI] VIDEOANALYSIS: New message: Data: {"time":"2023-01-24T16:25:03.762Z","event":"dwellTime (60s)"} - Motion: resetted - Camera: Kitty Cam [1/24/2023, 10:25:03 AM] [CameraUI] Kitty Cam: Skip motion trigger. At Home is active and Kitty Cam is not excluded!


French model not working

docker run -p "<IP_ADDRESS>:8080:80" jgontrum/spacyapi:fr
http://localhost:8080/ui
UI loads correctly, however any requests from the sentence entry simply do not return. The loading icon spins and nothing else happens.
I have tried en and en_v2. Both work as they should.
When testing this no other containers were running.
edit: curl commands fail as well.
curl -s localhost:80/dep -d '{"text":"Bonjour Justin Trudeau.", "model":"fr"}'
{"title":"Dependency parsing failed","description":"'NoneType' object is not callable"}

I just upgraded the API to use the current stable version of spaCy and the French model works now. Can you please try starting spacyapi:fr_v2 ?

It works now :)
thank you for the quick turn around!


Default Fileicons are not loading anymore (v1.96.0)

v1.96.0 Mac
v1.96.0 Ubuntu 24.10

Seems like default file themes have been moved or restructured.
User installed themes still seem to work at least.

Related: https://github.com/microsoft/vscode/issues/235942


ci: add check for up-to-date olm versions

Description of the change:
Add a check to CI that will check for the OLM versions to be up to date with the 3 latest minor releases.
The check is implemented as a shell script so that the check can also be run locally outside of CI.
The script will check the following files for the most up to date OLM versions:

Makefile
internal/bindata/olm/versions.go
internal/testutils/olm.go
website/content/en/docs/overview/_index.md

The check assumes that if you change the OLM_VERSIONS variable in the Makefile that you also have run make bindata to update the OLM bindata and therefore does not directly check the bindata.
The CI check will also only run on PRs from a branch prefixed with release- as to prevent the check from running on every PR.
Motivation for the change:
resolves #5682
Checklist
If the pull request includes user-facing changes, extra documentation is required:

[ ] Add a new changelog fragment in changelog/fragments (see changelog/fragments/00-template.yaml)
[ ] Add or update relevant sections of the docs website in website/content/en/docs

/hold remove


beer factories wont open

after I got the proxy upgrade for the storage I sacrificed and now I can't even open the beer factories, nor close it after it pops up it's just a blank screen so I have to refresh to play the game

Hi @luciferakathedevil, did you equip the proxy upgrade or did the issue occur directly after finishing the upgrade?
It's a display error which I try to reproduce to fix the issue.
Relevant error log:
Client Error<EMAIL_ADDRESS>TypeError: Cannot read property 'hasProjectQueue' of undefined
    at Render.<anonymous> (https://wol-soft.de/apps/beerplop/dist/js/beerplop-game-1.69.1.min.js:32:429477)
    at Array.map (<anonymous>)
    at Render.<anonymous> (https://wol-soft.de/apps/beerplop/dist/js/beerplop-game-1.69.1.min.js:32:428950)
    at Array.map (<anonymous>)
    at Render.renderFactoriesMap (https://wol-soft.de/apps/beerplop/dist/js/beerplop-game-1.69.1.min.js:32:427338)
    at Render.renderOverlay (https://wol-soft.de/apps/beerplop/dist/js/beerplop-game-1.69.1.min.js:32:423616)
    at OverlayController.openOverlay (https://wol-soft.de/apps/beerplop/dist/js/beerplop-game-1.69.1.min.js:32:250260)
    at HTMLDivElement.<anonymous> (https://wol-soft.de/apps/beerplop/dist/js/beerplop-game-1.69.1.min.js:32:249494)
    at HTMLDivElement.dispatch (https://wol-soft.de/apps/beerplop/dist/js/beerplop-game-1.69.1.min.js:2:4...',
referer: https://wol-soft.de/apps/beerplop/plop

Alright, I've reproduced and fixed the issue and patched it with version 1.69.2


[Feature]: Get entity values such as name or icon in Template card

Requirements

[X] I have updated Mushroom to the latest available version
[X] I did a search to see if there is a similar issue or if a pull request is open.

Is your feature request related to a problem?
I know that I could use {{ state_attr('switch.entity_id', 'icon') }} for icon in a template card, but this requires a request to the HA backend (which causes some rendering issues) and it doesn't return an icon reflecting the current state of the entity. It would be nice to directly reference the entity icon (and other things, such the entity's name) in the template card fields.
Describe the solution you'd like
I'm not sure how the best solution would look here. I made an implementation here for my personal use which detects if the icon value is not a template and contains a . (dot) and if it does, it uses stateIcon with that value.  I'm not primarily a TypeScript developer, but I'm willing to contribute with a solution.
Describe alternatives you've considered
No response
Additional context
No response

I have an issue that is very close, trying to built a weather mushroom card using either entity or template card (I want it bigger that the wonderful weather chip...)
I have a nice card with good icon with the entity card, but I cannot display the temperature (I would need a templated second line)
I can display all information I want with the template card, but I am not able to recover the default icon from the entity.


DB Error - Need help

Hello!
How are you ?
I hope you are fine and everything is going well,

yesterday, I did clone this repository and also upload Database SQL file
But this error are displaying on my screen

Could you please help me ?
Thank you so much

Hello!
How are you ?
I hope you are fine and everything is going well,

yesterday, I did clone this repository and also upload Database SQL file
But this error are displaying on my screen

Could you please help me ?
Thank you so much

Hello there sajeel93,
Did you fix this problem?, couse I'm in the same spot, I have the same problem.
I'm trying to run it but it dos't work...


ERROR [launcher]: Cannot start PhantomJS2

Hi,
thanks for creating this package.
When trying to run phantomjs2 via karma & karma-phantomjs2-launcher on travis, I always get the above mentioned error. The project I try to build is this. You can see the build output here.
Thanks for your help.
Best
Marc

I'll try to take look during this week. At first look there can be some problem with version of PhantomsJS, because there were build Phantom for only Win/Mac/Ubuntu. Possible karma launcher mismatch version of OS.

Ok, thanks. If you think that I can help you somehow, please let me know.

Hey @gskachkov,
any news on this?
Best
Marc

Hey @gskachkov,
hope you're alright. Any news?
Best
Marc

@mdix Ohh, sorry. I'm have been working on patch for WebKit for last 4 weeks. Now it uploaded for review so I can spend more time on another thinks.
Now I'l try to help you

@mdix I've managed to build your project, and run tests with phantomjs2
If you are using special version of the PhantomJS for travis ubuntu 12.04, you need to set path to custom PhantomJS in env variables, for instance
export PHANTOMJS_BIN=/usr/local/phantomjs/bin/phantomjs
You can add this value to configuration of travis build or add as the command to .travis.yml
See my build log of your project.

@gskachkov YAY nice, working. Thanks. I knew that but I shomehow must've missed this little detail. Thanks for your help.

Nice to hear!