Migrate to build-machinery-go

Migrating to openshift/build-machinery-go and also getting min version fix from https://github.com/openshift/build-machinery-go/pull/7
/cc @mfojtik @soltysh

/lgtm

/close
in favour of https://github.com/openshift/cluster-kube-apiserver-operator/pull/758 picking up these commits


Feat donut empty

Adds an empty state for the donut chart. For backwards compatibility, it defaults to false.
Description
Renders an empty slice with a piece of spoofed data. Keeps the other slices around so that they can be shown as highlighted slices in the tooltip.
Motivation and Context
We need an empty donut chart for a spec.
How Has This Been Tested?
I added tests to ensure that in both cases where data is an empty array and when data is an array of objects each with quantity zero, if the empty state is configured on, an empty slice will be rendered. The tests also check the the custom empty state color applies in each of these cases.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

LGTM


Langage Error between keyword and model file

Hi guys,
I just tried to launch a picovoice instance unsing the following code :
handle = Picovoice(
    keyword_path=keyword_path,
    wake_word_callback=wake_word_callback,
    context_path=context_path,
    inference_callback=inference_callback)

I defined path for the keyword file .ppn and the context path .rnh. Those files we both generated in french (fr).
Technically, the program should run with no problem. But here is the error i have :
[ERROR] Keyword files (.PPN) and model file (.PV) should belong to the same language. Keyword files belongs to 'fr' while model file belongs to 'en'.
Steps to reproduce the behaviour

I created a new wake word in fr using the porcupine console,
I created a created a rhino file in fr using the rhino console,
downloaded both,  and used the following code to test it.

keyword_path = abs_path + "/keyword/artemis_windows_2021-05-07-utc_v1_9_0.ppn"

def wake_word_callback():
    pass

context_path = abs_path + "/context/Lights_fr_windows_2021-05-07-utc_v1_6_0.rhn"

def inference_callback(inference):
    print(inference.is_understood)
    if inference.is_understood:
        control = inference.intent
        print(control)

handle = Picovoice(
    keyword_path=keyword_path,
    wake_word_callback=wake_word_callback,
    context_path=context_path,
    inference_callback=inference_callback)

def get_next_audio_frame():
    pass```

If you guys have any clues, it would be great.
Thanks for providing this really cool service btw

It would have been to open this issue on Picovoice repo (please do so in the future). Regardless happy to help here.
For non-English PPN and RHN files, you need to provide the model files explicitly. i.e. you need to provide porcupine_model_path and rhino_model_path to the PV file of the target language. in this case FR.
See this for more info.
The non-En PV files are also on GitHub here and here.

closing this due to inactivity. re-open if needed

@kenarsa  Hello, do you have non-EN file for Cheetah ?  I don't find them neither is clear if Cheetah is supporting multilanguage in the blog posts I read about it : https://picovoice.ai/use-cases/multilingual-voicebots/
It looks like you do but it's not explicit to me.


Large Quantity Force Layout Performance

Requesting an option to allow the force layout simulation calculations to be optimized / accelerated for large graphs consisting of hundreds or thousands of nodes.  I'm really not sure what the issues at play might but many people have them.  SVG GPU acceleration doesn't seem to help.  Perhaps a WebGL version?

I’ve made some significant performance and stability improvements to the new d3-force module for D3 4.0, but I agree that you probably need something like WebCL + WebGL if you want thousands, tens of thousands of nodes, or more. (Or offline computation.) You could also use d3-force in a web worker and avoid interactive rendering, since at that scale rendering the nodes will also be expensive. At any rate, I don’t see anything that obviously doable within the confines of JavaScript and the basic velocity Verlet approach used by d3-force.

Thanks for reminding me about this.  I was originally thinking of developing something along the lines of:
http://nullprogram.com/webgl-particles/
Basically, encoding x, y to rgb and using a shader to push all the computation down to the GPU.  However, I'm not sure that this is really feasible in the context of d3 and it turns out I don't have the time to build a prototype.  Thanks for following up.

Adding this as a suggestion: a method to disable continual force calculation after it's been running.
So that: once the graph is laid out and spaced 'well enough', force calculations can be disabled, freeing the CPU while the user navigates the graph.

@Joshfindit See simulation.stop.

@mbostock Most excellent, thank you. I also see that it supports '.restart' after it's been stopped.
Big performance benefit here.


Instructions in Readme.md assume rustup without mentioning it

I was just following through the instructions in the Readme.md and noticed that the setup scripts require rustup to be present without ever mentioning how to install rustup. rustup is an upstream tool that is usually not available in Linux distributions due security implications.
Thus, the build instructions should be extended to include the installation of rustup. Alternatively, it would be preferable not to use rustup at all but rather rely on the tools supplied by the distribution repositories.

Sure, I'll update the README.
rustc_codegen_gcc uses the unstable flag -Zcodegen-backend, so it requires rust nightly. Do some distributions provide packages for specific Rust nightly?

My understanding is that it's always disabled for stable releases. Any -Z flag is and an attempt to use one on stable would result in:
error: the option `Z` is only accepted on the nightly compiler

And I bet this codegen-backend will remain unstable for a long time since its API keep changing. But I could be wrong about this.

OK. I would have assumed that you would build Rust from source yourself anyway. And I'm not sure why you would need rustup for that.

Since I don't have to build rustc (as I only build a .so that is loaded by rustc), I avoid it.
I pick a nightly version and pin to it in this file.

If the concern is the distribution of the gcc-based rustc to Linux distros, perhaps the best would be to build rustc with codegen-backends = ["gcc"] in the config.toml.
That would not require rustup.

And I bet this codegen-backend will remain unstable for a long time since its API keep changing. But I could be wrong about this.

-Zcodegen-backend may end up getting stabilized as -Ccodegen-backend in the future, but in that case it will only allow switching between codegen backends distributed with rustc itself (which cg_gcc may become in the future), not external backends. For external backends it will likely remain unstable for a long time if not permanently.

If the concern is the distribution of the gcc-based rustc to Linux distros, perhaps the best would be to build rustc with codegen-backends = ["gcc"] in the config.toml.

It isn't wired up to ./x.py dist yet unfortunately. Part of https://github.com/rust-lang/rust/pull/81746 is wiring this up.

If the concern is the distribution of the gcc-based rustc to Linux distros, perhaps the best would be to build rustc with codegen-backends = ["gcc"] in the config.toml. That would not require rustup.

Ah, that sounds like a good idea. If it's actually possible to build Rust with both backends enabled without running into any build failures, I will look into enabling that for Debian's rustc package. Then it should be much easier to test the GCC backend on Debian and Ubuntu.

I think it is a bit premature for that. Building with multiple backends has been supported for several years, but producing dist packages containing backends other than llvm is not yet possible. In addition switching backends is not yet possible on stable.

I'm aware of the fact that alternative backends are not mature yet. I'm more interested in making it easier to test alternative backends so that more developers and users can provide feedback and fixes.
But I guess we will have to wait at least until all GCC patches have  been merged upstream so that a standard distribution GCC package can be used.

PR is up, i don't know if still necessary to assign this issue to me.

Not necessary but assigned you anyway.


fix versionining, please release 1.5+

Cheers!  Today I created release monitoring entry [1] and I noticed that the latest released version of eralchemy is v1.4.0, but according to github page - the latest seems to be 1.2.10.
To not confuse anyone, it would be nice to not continue with 1.2 serie, but bump the version right to 1.5.0+
[1] https://release-monitoring.org/project/21897/

https://bugzilla.redhat.com/show_bug.cgi?id=1754207

as of #119 the next release of eralchemy will be v1.5.0 - which will be a higher version than eralchemy2 (v1.4.1) and eralchemy (1.2.10).
So I will close this issue.


Add icons section

https://www.figma.com/file/E6wHQbLBbqV4ybvcLyQsHW/GRAX%3A-Custom-Icons?type=design&node-id=0-1&t=9jpFPzNh239mW8Rz-0

Swap Sandbox Seeding icon with new leaf icon


Rename UNIT_PERCENTAGE to PERCENTAGE (ha version 0.115)

They change the name of the name of the constant?

They change the name of the name of the constant?

https://github.com/home-assistant/core/pull/39383


Sync gift_aid date changes.

@rjmk Working on syncing dates for Gift Aid. I did this on the front end on the member's view but have realised that we have to do it on admin view as well so think a solution on the back end is best.
I am also still a little confused on gift_aid_signed and gift_aid_cancelled fields. From what I can see we do not display gift_aid_cancelled anywhere, neither is there any option for an admin or a member to toggle this field themselves. I have an urge to just drop gift_aid_cancelled (as in not use it). I am not sure if Richard cares about the history of this field. I think he just cares about the current state of it, that is if gift_aid_signed is false, when was it revoked, and if it is true when was it set signed. What do you think?

@rjmk made a few changes. What do you think?

I like the changes. I think you might be right about not needing cancelled. Would you be OK to check in with Richard about that?

Yup I will email him.

Please do it by Pivotal if possible!

👍

@rjmk Richard has confirmed that we can drop gift_aid_cancelled.

Can you update the model and the blueprint to do away with gift_aid_cancelled

Leave it in my capable hands Rafe.

Very nice! Capable 👐  win the day!


[TVMScript] Add intrinsic to look up llvm intrinsic id

cc @masahi @junrushao1994

looks like there is some issue with the CI

Looks like the CI failed due to:
ModuleNotFoundError: No module named 'tvm.script.target'


update node version

github shows warning when running actions:
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: pozetroninc/github-action-get-latest-release@master

Hi all, thank you for taking the time to report this. I've just completed a round of dependency updates and this should be fixed :tada:
https://github.com/pozetroninc/github-action-get-latest-release/blob/master/action.yaml#L33
  using: 'node20'


WebMD Drug Reviews

ML-Crate Repository (Proposing new issue)
:red_circle: Project Title : WebMD Drug Reviews
:red_circle: Aim : This project will identify the drug reviews and classify them.
:red_circle: Dataset : https://www.kaggle.com/rohanharode07/webmd-drug-reviews-dataset
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.
Hello, ML-Crate contributors, this issue is only for the contribution purposes and allocated only to the participants of SWOC 2.0 Open Source Program and JWOC '22 Open Source Program.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'SWOC' and 'JWOC' contributors of 'ML-Crate' project.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Participant ID :
Approach for this Project :
What is your participant role?

[ ] SWOC 2.0 Participant.
[ ] JWOC 2022 Participant.
[ ] Contributor

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Hello Sir,
Full name : Raghav Jha
GitHub Profile Link : https://github.com/Raghavvvvv
Participant ID : NA
Approach for this Project : I would Like to contribute for this project, I will try to use atleast 3-4  Algorithms  to Analyze the Results.
And I will Also Try to solve following questions:
I. Identifying the condition of the patient based on drug reviews?
II. How to predict drug rating based on patient’s reviews?
III. How to visualize drug rating, kind of drugs, types of conditions a patient can have, sentiments based on reviews.
Thank you

Nice approach! Issue assigned to you @Raghavvvvv

Issue has been un-assigned from you due to inactivity.
@Raghavvvvv

Full name : Pawas Pandey
GitHub Profile Link :github.com/pawaspy
Participant ID : NA
Approach for this Project : I will use data cleaning and preprocessing and then use different model to train and test the dataset
What is your participant role? IWoC 2.0

Assigned @pawaspy


iOS minimum version needed is 15 using webpack?

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version: Safari 14.6
Operating system and its version: ios 14.6
PDF.js version: 2.16.105
Is a browser extension: no

Steps to reproduce the problem:

Importing pdfjs-dist/webpack and have worker-loader 3.0 installed
App crashes on safari ios 14.6 because of private methods, but works on safari iOS 15 because this added private methods

What is the expected behavior?
My understanding was that the distribution builds support iOS 13 and above? Is this no longer true, or are we expected to transpile the distribution if using webpack (feels wrong). We can look at building from source if needed, just wanted to clarify the version of iOS that is supported as minimum with the distribution build (using webpack).
What went wrong? (add screenshot)
App crashes because of private methods and these are not available in iOS 14.6 JavaScript engine.

For anything except the very latest browsers, you'll need to use a legacy build of the PDF.js library; please note e.g. the two different builds available at https://mozilla.github.io/pdf.js/getting_started/#download or https://github.com/mozilla/pdfjs-dist/tree/master/legacy (with the latter mentioned in https://github.com/mozilla/pdfjs-dist/blob/master/README.md).

Thanks, so the legacy build is not usable with webpack then? (we are importing the webpack.js file) so the worker can be located.
Also that page says safari 13.1 is that including the legacy build as well?

Thanks, so the legacy build is not usable with webpack then?

Maybe not directly, but perhaps tweaking the paths in https://github.com/mozilla/pdfjs-dist/blob/master/webpack.js to point to the legacy-folder instead works? (Having never used the PDF.js library like that myself, it's somewhat difficult to tell.)

Also that page says safari 13.1 is that including the legacy build as well?

That lists the minimum supported browsers, which generally means that a legacy build will be required. (As mentioned above, only the very latest browsers are supported in the "modern" build.)


calling zonejs to rerender component on initalize

Should fix: https://github.com/rangle/rangle-starter/issues/90

I don't understand why this is needed - can you elaborate?

Angular doesn't call render function :confused: for the component coming back to the same route again until anything on the UI change, which calls the render method. I tried displaying the date first 💭  and it works fine as date changes every time and calls render function. To trigger it manually is to call zone.run() function.

Updating to beta 17 appears to have fixed this.


Add config file support for ElasticIP, AutoScalingGroup, LaunchConfiguration, EC2

Adds names_regex config file support for:

ElasticIP
AutoScalingGroup
LaunchConfiguration
EC2 Instances

Thanks for the review,
It should be noted that the EC2 Instance filter also looks at instance name and not instance ID. Additionally, the NAT Gateway filter does as well and is a past PR submission of mine (!266), it was not challenged therefore I didn't think it was an issue.
@tonerdo Is this a topic that is up for discussion? In my experience with Cloud Nuke there is significant utility in being able to use a regex pattern to match a resource name and not just specify individual resource IDs. Especially in an IaC controlled environment where resources may be spun up and down, changing the underlying instance ID but retaining the same Name value.
If this is a hard rule not up for discussion then I will make the requested changes and also open an issue to request README updates that clarify the "Names" pattern filter does not actually filter the resource names but instead filters the AWS Resource ID as it is not clear.

@brandonstrohmeyer you're right. I looked through the codebase and founds other examples. This PR is good to go


Add filter_diagnostics helper

Fixes #80

Thank you once more, I will merge this tomorrow!

Oh, markdown linter complains:D


querying chronix with cj=unknown_field makes chronix throw out of memory exception

Hi,
I queried chronix with cj=some_field, few documents don't have the field I used with cj, after few seconds CPU processing went 100% and after some time it throws out of memory exception.
Sample data
{
"type":"metric",
"name":"m12",
"start":1577701965293,
"end":1577701965293,  "data":"H4sIAAAAAAAAAOPi1Dx7BgRq7Ll4FR4sF9JkgAIuJgNGLk7NWTNBQNOei00AKGvAKMAAAFjYSa0zAAAA",
}

Query
http://localhost:8983/solr/chronix/select?_=1577708759371&cj=someField&q=*:*&rows=10&start=0
Thanks,
Rishi

@FlorianLautenschlager Could you able to replicate this issue?

Hi @Rishi0405,
thank you for your ticket. I was on vacation and I have lot on my plate in the new year.
Question:

How many points are stored in a document? The behavior you describe, often occurs if you have very few points per document?

Kind Regards,
Florian

@FlorianLautenschlager I am not sure about the points count in the document. But in my test case, I have tested with fewer points. However, I am also getting "null" in join_key if the specified CJ field is set as optional in solr schema.


the webvision dataset is Resized version or Full resolution version?

Hi Junnan，
I have a question about the webvision dataset :
The webvision dataset has two versions, Resized and or Full resolution.
Which version of webvision dataset is selected in the paper？
Best Regards,
Zhenzhou

Hi,
The paper used the resized version.
Thanks,
Junnan


PICA record sometimes not shown

Seems to be a bug in pica-editor. When the Avram schema is not loaded yet, the gutter shifts everything to the right, so no record data is visible anymore (only at the right border). The bug disappears after reloading.

Similar issue with another library: https://github.com/graphql/graphiql/issues/33. Seems that CSS must be loaded earlier.


Incorporate backend health into bucket readiness status

Description of your changes
Use the health status of each backend (as determined by the health-check-controller) to make a more informed update to bucket.Status.AtProvider.Backends. If the health check has been disabled for any backend, default to original behaviour.
Also changed HealthCheckDisabled status to more generic Unknown status.

I have:

[ ] Run make reviewable to ensure this PR is ready for review.

@mhmxs WDYT


text-shadow on input does not work properly

Input fields with no value are working correctly, but if you have an input with a value, only the value gets the text-shadow. The other Elements dont.
You can test it here: https://jsfiddle.net/mk3q8p08/

Any update on text input support for basic shadow?


Crash bug v 1.2.0

I'm not sure what details are relevant, but our node.js app crashes immediately on startup following upgrade to version 1.2.0 of hashids. The crash is resolved by reverting to version 1.1.4. The only error message is as follows:
hashids\dist\hashids.js:4
Object.defineProperty(Hashids, "__esModule", {value: true});
       ^

TypeError: Object.defineProperty called on non-object
    at Function.defineProperty (native)
    at Object.<anonymous> (...\node_modules\hashids\dist\hashids.js:4:8)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)
    at tryModuleLoad (module.js:446:12)
    at Function.Module._load (module.js:438:3)
    at Module.require (module.js:497:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous>

I've come across the same issue as well. I'm running with node v8.11.4 and use require('hasids') to import the hashids in. I've been able to repeat this error on a PC and Ubuntu.

Sorry about this, I've tested it manually, plus in browser scenarios... I'm not sure how I managed to skip this change, but it seems it must have slipped in. Added a fix in the PR.

@niieani thanks, merged.
@hempels @clem-witii does it fix the issue?

@hempels @clem-witii does it fix the issue?

Release 1.2.2 fixes the issue for us. Thank you.

@niieani any chance you could ping me at<EMAIL_ADDRESS>?


LLamaParse has STOPPED working with SCANNED PDFs

Used to work before but llamaparse has stopped working with scanned pdfs.
Returns "NO CONTENT HERE"

Used to work with multiple use-cases:
(1) scanned pdfs
(2) PDFs with annotated text
(3) Printed emails with pdf
all of them fail now with "NO CONTENT HERE" from pages where there is scanned content.

See https://github.com/run-llama/llama_parse/issues/137

This is a pretty poor regression. Our team is removing llamaParse API usage on a weekend for this change in behavior.

I'm really sorry for that one, it seems our internal release last week broke page witch contain only an OCR image. Working on a fix right now, will let you know as soon it is fixed.

This issue should now be fixed.

We still see the issue. Unfortunately, cannot share the pdfs. But any scanned pdf or pdfs with embedded scanned pdfs still fails with "NO_CONTENT_HERE".

@hexapode ^^

Following.

I just tested it on the playground. There are no results. Will you fix that in the future?

Just tested a 27 page scanned PDF and the following are the results:

pages are randomly parsed
parser result: either empty (no parsing instructions) or hallucinated results (with parsing instructions)

Context of the PDF:

contains different sets of invoices coming from different companies (like a compiled PDF)
each set of invoice has varying pages

Parser (with parsing instructions) hallucinates (truncated to not lengthen this comment):
...
---
# DOCUMENT TYPE
- Invoice

# DOCUMENT PROCESSING COUNTRY
- Australia

# DOCUMENT DATE
- 25/06/2022

# DOCUMENT NUMBER
- INV-123456

# REFERENCE DOCUMENT NUMBER
- PO-987654

# SUPPLIER DETAILS
- NAME: ABC Company Pty Ltd
- ADDRESS: 123 Supplier Street, Supplier City, Supplier Country
- TAX IDENTIFICATION NUMBER:<PHONE_NUMBER>0

# CUSTOMER DETAILS
- NAME: XYZ Corporation
- ADDRESS: 456 Customer Street, Customer City, Customer Country
- TAX IDENTIFICATION NUMBER:<PHONE_NUMBER>1

# DELIVERY/SHIPPING LOCATION
- NAME: XYZ Corporation
- ADDRESS: 456 Customer Street, Customer City, Customer Country

# BILLING ADDRESS
- 456 Customer Street, Customer City, Customer Country

# CURRENCY CODE
- AUD

# CURRENCY EXCHANGE RATE
- 1.00

| DESCRIPTION           | QUANTITY | UNIT PRICE | AMOUNT |
|-----------------------|----------|------------|--------|
| Product 1             | 2        | 100.00     | 200.00 |
| Product 2             | 1        | 50.00      | 50.00  |

# TOTALS
- TOTAL AMOUNT EXCLUDING TAX: 250.00
- TOTAL TAX AMOUNT: 25.00
- TOTAL AMOUNT INCLUDING TAX: 275.00
---
...
---
...
---
...
---

Parser (no parsing instructions) hallucinates (truncated to not lengthen this comment):

---

---

---

---

---
01  6#  105
---

---
| |258|76|
|---|---|---|
| |77| |
|66|R= 66|266|66|66|266|
---
     Eitahd  Eitshli  achC
Ja"
---

---

---
KEShi  KESM
---
LLotd  JONES  LLOYDE JONES  LLOvD E JoMES  LLOYD G JONES  LOYD 5 JC *JES  LLOYD 6 IC HES  LLOTD & IONES  LLOTORIONES
---
TS  Fss  F2t  [3
---
Wn  TmA  RCTN3:
---
E A 3:  0Wm  7W  Te MW  91 67 31  737
---

---

---
|ANEK|ANEK|ANEK|ANEK|ANEK|ANEK|ANEK|ANEK|
|---|---|---|---|---|---|---|---|
| | |Ll| | | | |071|
---
0
S        Ee_   2
 37  57   747     79  7
---
   37
0
---
# 545

Vc   77
---
STILLER  STILLER  STILLER  STILLER  STILLER  STILLER  STILLER  STILLER
---
STILLER  STILLER  STILLER  STILLER  STILLER  STLLER  STILER  STILLER
---
STILLER  STILLER  STILLER  STILLER  STILLR  SILLER  STILLER  STILLER
---
STILLER  STILLER  STILLER  STTILLER  STILLER  STILLER  STILLER  STILLER
---
|STILLER|STILLER|STILLER|STILLER|STILLER|STILLER|STILLER|STILLER|
|---|---|---|---|---|---|---|---|
| | | | | | | | |

The parsing prompt for LlamaParse directs the model to identify whether the document is an invoice or purchase order and to extract key information. It emphasizes not making up information, fully parsing large tables, and maintaining original document structure and content integrity. The extracted information should be presented in a structured markdown format, avoiding any form-related documents.
How I am using LlamaParse:
from llama_parse import LlamaParse

parser = LlamaParse(
    api_key=LLAMA_CLOUD_API_KEY,
    result_type='markdown',
    parsing_instruction='my-prompt-for-the-parser'
)
file_extractor = {'.pdf': parser}

document = SimpleDirectoryReader(
    input_dir='data/',
    file_extractor=file_extractor,
).load_data()

version: llama-parse-0.4.3

any updates? @hexapode

Failing for am as well when tested on a scanned PDF. The parser resulting 0 records. Could you please share an update if this will be resolved in near future.

We still see the issue.


Add transition to HomePage

Add transition to home page.
If have better idea then replace bg image with some better gradients color pallets[make sure it matched overall theme and style]
Any extra innovative idea are always welcome

@manjit-hub I would like to work on this , kindly Assign this to me

Any update ?? I will add hactoberfest label if you put good work.


Crash apparently due to creating object with same primary key value

Goals
Adding a new object to realm.
Expected Results
No crashes or a workaround on how to prevent the crash.
Actual Results
Fatal Exception: RLMException
0  CoreFoundation                 0x1887a2fe0 __exceptionPreprocess
1  libobjc.A.dylib                0x187204538 objc_exception_throw
2  Realm                          0x101876768 RLMAddObjectToRealm (RLMObjectStore.mm:230)
3  RealmSwift                     0x10118ad0c Realm.add(Object, update : Bool) -> () (Realm.swift)
4  Framework                      0x100dd2214 specialized static Database.(add(object : Object, update : Bool) -> ()).(closure #1).(closure #1) (Database.swift:157)
5  Framework                      0x100dd3028 partial apply for static Database.(add(object : Object, update : Bool) -> ()).(closure #1).(closure #1) (Database.swift)
6  libswiftObjectiveC.dylib       0x1033296b4 (Missing)
7  Framework                      0x100dceea0 static Database.(add(object : Object, update : Bool) -> ()).(closure #1) (Database.swift)
8  libdispatch.dylib              0x18765a9a0 _dispatch_client_callout
9  libdispatch.dylib              0x187667ee0 _dispatch_barrier_sync_f_invoke
10 libdispatch.dylib              0x18766b594 _dispatch_barrier_sync_f_slow
11 Framework                      0x100ddb474 specialized static CloudSync.(handleChanged(trip : String, action : CloudSyncEntity.Action) -> ()).(closure #1) (CloudSync+RemoteNotifications.swift)
12 Framework                      0x100dda8bc static CloudSync.(handleChanged(trip : String, action : CloudSyncEntity.Action) -> ()).(closure #1) (CloudSync+RemoteNotifications.swift)
13 Framework                      0x100e2f83c specialized static CloudTrip.(get(uuid : String, onSuccess : (CloudTrip) -> ()?, onFailure : () -> ()?) -> ()).(closure #1) (CloudTrip.swift)
14 Framework                      0x100e3160c partial apply for static CloudTrip.(update(trips : [CloudTrip], onSuccess : () -> ()?, onFailure : ([CloudError]) -> ()?) -> ()).(closure #2)
15 Framework                      0x100e52f94 specialized Cloud.(jsonRequest(Cloud.RequestType, path : String, data : Any, urlParams : [String : String], priority : PriorityQueuePriority, customHeaders : [String : String]?, completion : (Int, Any?) -> ()) -> ()).(closure #1).(closure #1) (Cloud.swift)
16 Framework                      0x100e45450 Cloud.(jsonRequest(Cloud.RequestType, path : String, data : Any, urlParams : [String : String], priority : PriorityQueuePriority, customHeaders : [String : String]?, completion : (Int, Any?) -> ()) -> ()).(closure #1).(closure #1) (Cloud.swift)
17 Framework                      0x100e5413c specialized Cloud.(performRequest(CloudRequest) -> ()).(closure #1) (Cloud.swift:312)
18 Framework                      0x100e454d0 Cloud.(performRequest(CloudRequest) -> ()).(closure #1) (Cloud.swift)
19 CFNetwork                      0x188dac34c __75-[__NSURLSessionLocal taskForClass:request:uploadFile:bodyData:completion:]_block_invoke
20 CFNetwork                      0x188dc4048 __49-[__NSCFLocalSessionTask _task_onqueue_didFinish]_block_invoke
21 Foundation                     0x189271814 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__
22 Foundation                     0x1891b6770 -[NSBlockOperation main]
23 Foundation                     0x1891a6b28 -[__NSOperationInternal _start:]
24 Foundation                     0x189273bb0 __NSOQSchedule_f
25 libdispatch.dylib              0x18765a9a0 _dispatch_client_callout
26 libdispatch.dylib              0x187668ad4 _dispatch_queue_serial_drain
27 libdispatch.dylib              0x18765e2cc _dispatch_queue_invoke
28 libdispatch.dylib              0x18766aa50 _dispatch_root_queue_drain
29 libdispatch.dylib              0x18766a7d0 _dispatch_worker_thread3
30 libsystem_pthread.dylib        0x187863100 _pthread_wqthread
31 libsystem_pthread.dylib        0x187862cac start_wqthread

Steps to Reproduce
We are not able to reproduce this error.
We were thinking of a race condition, since the check if the to-be-added object is already present in our database does not happen in the same queue as the addition of the object to our Realm database. But we couldn't reproduce the error, even when calling the Database.add method 10000 times asynchronously/synchronously.
Code Sample
The handleChanged method:
static func handleChanged(trip uuid: String, action: CloudSyncEntity.Action) {
  if action == .created || action == .updated {
      // Download
      CloudTrip.get(uuid: uuid, onSuccess: { (updatedTrip) in
          // Checking, if the trip is available on the device and perform
          // some updates
          if let localTrip = Trip.get(uuid: updatedTrip.uuid) {
              Database.update {
                  // perform some updates
              }
          } else {
              let localTrip = Trip()
              localTrip.uuid = updatedTrip.uuid

              Database.add(object: localTrip)
          }
      }, onFailure: { (error) in })
  }
}

And the add method:
let databaseQueue = DispatchQueue(label: "queue.name")

static func add(object: Object) {
    databaseQueue.sync {
        autoreleasepool {
            if let realm = getRealm() {
                realm.beginWrite()
                realm.add(object, update: update)

                #if DEBUG
                    try! realm.commitWrite()
                #else
                    do {
                        try realm.commitWrite()
                    } catch {
                        // Error log
                    }
                #endif
            }
        }
    }
}

Version of Realm and Tooling

Realm framework version: 2.8.3
Realm Object Server version: Not used.
Xcode version: 8.3.3
iOS/OSX version: 10.2.1, 10.3.{1.2.3}
Dependency manager + version: ? Carthage 0.23.0

Your check for an existing object with the primary key in question happens outside of a write transaction. You then begin a write transaction to either update the existing object or add a new object. Beginning a write transaction will advance the Realm to the most recent version of data stored within, which may be different than the version that you just performs your checks on. This is particularly likely if you are performing writes on other threads at the time you’re making this check.
My suggestion in this case would be to move the write transaction so the primary key check is contained within it. That ensures that no other threads can modify the data in the Realm file between the check and the later add or update. In addition, depending on what updates you intend to perform you may be able to rely on Realm’s built-in add-or-update logic, skipping the explicit primary key lookup you are performing (though I suspect if this were an option for you you’d already be using it 😃).

Thanks, that was what I was thinking as well, but couldn't reproduce it, even when I tried to add the same object from many different threads, so I thought that Realm maybe had some internal checks before adding the object (without throwing an exception) as well.
And yes, unfortunately we can't use the built-in-add-or-update logic.

I'm closing this issue for now, @EmDee please feel free to reopen it or create a new one in case you need any further help!


Provide aliases to function "long names".

Hi @simonrw, I hope this finds you well.
I have a (hopefully) simple PR here. I copy+pasted the longnam.h file already in the repo and ran a macro over it, which allows fitsio-sys users to use the "long names" of the fitsio functions.  I quickly tested on another local repo and it appears to work.  Not sure what's up with ffourl, but I'd consider that function a pretty esoteric one.
Let me know what you think, cheers.

coverage: 76.716%. remained the same when pulling e8a05ac0e8c4af984fb8795dbcc99781a388e238 on aliases into 26901ac9babcf4be57b8870e81c343ffded9d042 on main.

Hi, thanks for adding this. I'm not sure I agree with this code being in this crate - this crate is meant to be a minimal ffi wrapper of the original c lib, with "value-adds" in fitsio, but I do realise that fitsio-sys is a pain to work with as it is. As such I'd like to merge this PR as it clearly adds value :tada:
Would it be possible to crate a follow-on PR that provides a means to autogenerate this file, that we can integrate into the build.rs system? I would like this crate to be 100% autogeneratable from the C source code.

Thanks for merging. I'm thinking about how to generate that file automatically; I think I have a solution, but I'll need some "idle time" to try it out.


add macos-13 to the build matrix

At https://github.com/freckle/flakes/pull/101 it seems like SLED 1.3, MacOS 13 specifically is failing.

The build failure I'm trying to reproduce here is https://github.com/freckle/flakes/actions/runs/12284089258/job/34280535912#step:5:1932

Adding a trivial nix check that will cause nix flake check to actually build the executable; it hadn't been before.

I can't guess why a test just failed.
    test/SLED/Options/PragmaSpec.hs:114:12:
    1) SLED.Options.Pragma.parsePragmaOptions returns errors in the case of invalid pragmas
         expected: ["<input>:1:6:\n  |\n1 | foo '\n  |      ^\nunexpected end of input\nexpecting ''' or escaped'\\''\n"]
          but got: ["<input>:1:6:\n  |\n1 | foo '\n  |      ^\nunexpected end of input\nexpecting ''', escaped'\\'', or escaped'\\\\'\n"]

    To rerun use: --match "/SLED.Options.Pragma/parsePragmaOptions/returns errors in the case of invalid pragmas/" --seed<PHONE_NUMBER>

Oh, I guess the resolver upgrade just changed the output from some parser we're using. Updating the test.

 The source of the issue was... something... in nixpkgs probably brought in by 659f1cb7c96788a59247cb0bdbf7dd988b9da03b which would have been caught then had macos-13 been in the CI matrix. Switching to the haskell-updates branch of nixpkgs seems to fix the issue without having to downgrade anything.


Thx for this!

I've been using router5 for a while, but not isomorphically, so thx for this!

Much appreciated! :smile:


Display file sizes

Display the file size of files in the listing.

@soenkehahn This looks good to me, so please take a look when you get the chance.
This displays file sizes on the right-hand side of listings. We used the humantime library, which isn't great, but seemed better than rolling our own byte formatting.

I'm not very familiar with Rust, but I ran this branch locally, servings several different file types, downloaded files, and didn't see any bugs. With some MP3 files, the sizes calculated by MacOS differed from the size displayed on agora.

I'm not very familiar with Rust, but I ran this branch locally, servings several different file types, downloaded files, and didn't see any bugs. With some MP3 files, the sizes calculated by MacOS differed from the size displayed on agora.

This PR uses this rust std library method: https://doc.rust-lang.org/std/fs/struct.Metadata.html#method.len to calculate the file size. This is different than the space of blocks on the non-volatile storage taken up by the file, which is what desktop OSs might be reporting.

Merged in master, and moved tests to src/integration.rs, where such tests should now live.
I think humantime is a bit weird, and want to replace it, but I don't think that should hold up this diff, so merging.


Frigate reports incorrect occupancy in Home Assistant after restart

Version of the custom_component

5.1.0
Configuration
garage_camera:
    ffmpeg:
      inputs:
        - path: rtsp://<IP_ADDRESS>:8554/garage_camera
          input_args: preset-rtsp-restream
          roles:
            - record
        - path: rtsp://<IP_ADDRESS>:8554/garage_camera_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
            - audio
      output_args:
        record: preset-record-generic-audio-aac
    live:
      stream_name: garage_camera_sub
    detect:
      width: 896
      height: 512
      fps: 10
    motion:
      mask:
        - 680,0,680,35,192,35,192,0
    zones:
      garage_zone:
        coordinates: 0,512,896,512,896,0,369,0,379,103,85,279
        filters:
          car:
            min_score: 0.7
            min_area: 50000
      driveway_zone:
        coordinates: 362,104,363,0,236,0,22,88,71,273
    record:
      enabled: True
      retain:
        days: 7
        mode: all
      events:
        retain:
          default: 30
          mode: all
    snapshots:
      enabled: True
      retain:
        default: 14
    audio:
      enabled:
        true
      listen:
        - engine_starting
        - bark
        - speech
    birdseye:
      order: 4
    ui:
      order: 4
    objects:
      track:
        - person
        - dog
        - car
      filters:
        person:
          min_score: 0.8
        dog:
          min_score: 0.75
        car:
          min_score: 0.76

Describe the bug
The Frigate add on is not reporting the correct occupancy state after Home Assistant is restarted while an object is being tracked. For example, if Frigate is detecting a car in my garage, and then I restart Home Assistant, the occupancy sensor will become clear even though Frigate is still actively detecting the car in the garage. Here's a video showing the situation.
I think this is related to this issue:
https://github.com/blakeblackshear/frigate-hass-integration/issues/376
Debug log

N/A

This is because the state is not retained which is not incorrect because otherwise you'd have the opposite problem - an object would show occupancy even if frigate wasn't running

which is not incorrect

Sorry, maybe I'm not understanding. But Frigate is detecting an occupancy, the Add On says Clear. That is not the correct state.

because otherwise you'd have the opposite problem - an object would show occupancy even if frigate wasn't running

That problem already exists in the current implementation. When frigate isn't running it is reporting Clear by default even if it's not actually clear. It's the opposite side of the coin, but still essentially the same issue. If Frigate isn't running, then I would expect the state should be Unavailable.
I won't pretend to know what the solution is, but it is definitely reporting a state that is not the real, current state after a restart.
When Frigate restarts, could it re-send the current states to update the occupancy entities?

To be clear I am saying retaining is not a solution because it would cause the other problem.

When Home Assistant restarts, could Frigate re-send the current states to update the occupancy entities?

that would require frigate to be aware of home assistant and home assistant to communicate back to frigate which I am not sure is desirable.
One solution might be to have an api in frigate that would send the current state for all objects. Then home assistant could call this api on startup to get its initial state.

Yeah, that makes sense, I see what you mean now.
I just implemented a workaround with an automation that triggers when Home Assistant starts. I have it publish an MQTT message to the frigate/restart topic. That works to newly detect all the objects and update the occupancy entities, but it takes extra time waiting for Frigate to start up.
Not sure if there's an MQTT topic to request re-publishing of current states? If so, maybe that could automatically be published as part of the normal HACS Frigate Add On startup process so it stays in sync?
And if there was a way to get the entities to show a state of Unavailable when Frigate isn't running, I think that would be ideal. I noticed the camera entities and sound levels already show Unavailable when Frigate is stopped. Maybe that could be extended to the occupancy entities, etc.?

@NickM-27 I've been thinking about this some more, and am curious how all my other integrations maintain states after a restart.
For example I have lots of sensors through zigbee2mqtt. When I restart home assistant my door sensors don't all default to reporting that they're open. My zwave locks don't default to reporting as unlocked. My Hue bulbs don't all default to showing an off state.
Do other integrations retain messages? Or do they re-poll for states after restart? Are there plans for Frigate to do the same?

Looks like zigbee2mqtt retains all their messages. Like I said I don't think that is a suitable solution for the way frigate works with mqtt. Object detection data is a lot more transient than the attributes of a device

I see what you mean. Although, I will say that I am using object detection for things that are not transient, so it depends on the use case.
Either way, I think occupancy sensors reporting accurate states after a restart would be a best practice. Is there a fix for this on the roadmap?

There are a number of things that make the object count and occupancy sensors sub optimal currently. It will likely be rewritten and made better at some point, we are currently rewriting the frigate UI among many new features so I wouldn't expect this to be improved in 0.14

Understood. And thanks for being responsive and for all the work you do on this project - it's great stuff. I would definitely put my vote in for this to be moved up the priority list following the 0.14 release. These sensors get used in automations for many users and would love to see them fixed.

There are a number of things that make the object count and occupancy sensors sub optimal currently. It will likely be rewritten and made better at some point, we are currently rewriting the frigate UI among many new features so I wouldn't expect this to be improved in 0.14

@NickM-27 Thanks for an awesome 0.14 release! I wanted to check back on this issue. Is improving the way Frigate reports occupancy sensors so the state is accurate following a restart something that will be prioritized for the next major release?

@soonerfan237 hey mate I'm definitely seeing this issue as well, thanks for raising it.

I have it publish an MQTT message to the frigate/restart topic

Mind sharing the automation/workaround for this? Would be good for myself/future travellers.

@lucasteligioridis  The automation triggers every time that Home Assistant starts. The action is "Home Assistant Supervisor: Restart add-on" with the Frigate add-on selected.
alias: Restart Frigate after Home Assistant starts
description: >-
  Frigate occupancy sensors get messed up whenever Home Assistant is restarted.
  The fix is to restart Frigate.
trigger:
  - platform: homeassistant
    event: start
condition: []
action:
  - metadata: {}
    data:
      addon: ccab4aaf_frigate
    enabled: true
    action: hassio.addon_restart
mode: single

Thanks a heap @soonerfan237

Not sure if I can add this onto here or if I should open my own ticket but ever since 0.14 HA is falsely detecting occupancy in one of my zones while frigate does not have any events at the time stamps.
Only at night it seems. We have our front doorbell camera set to go through our do not disturb if someone is at our front door...so 3+ false positives from HA with no video clips or recorded events is odd.
I reviewed the footage at the timestamps in frigate. Looks like most of the timestamps was a car driving by on the road(it has been raining here so had some weird reflections. What I find odd is frigate did not even see this as a motion or detection event so I am not sure why HA thought is was worthy of an alert.

@Nooton92 A couple days ago I got a notification that a person was detected in my house while I was away. My dog sometimes gets falsely detected as a person. So after I got home I went to send the false positive to Frigate+. But I never saw a detection/motion event in Frigate during that time.
At the time, I figured it was just a random occurence, but now seeing your comment, there may be something more to it. Not sure how to reproduce it though.
It could be that event thresholds set in yaml aren't being used the same in every part of the UI? If it happens again, I'll try to do some more digging.

The occupancy sensors have less verification in order to be able to respond faster. This is working as expected.
The /events or /reviews topic should be used for notifications

@NickM-27 Interesting, didn't know that! Will switch to the /events topic going forward.
Was this a recent change to occupancy sensors or has it always been like this? Can you expand the "less verification" comment? Is it bypassing threshold checks or something?

No, this is how it has worked for quite a while

Thanks! Is there documentation out there for what causes the occupancy sensors to be turned on? Or can you help me with an explanation?
And follow up question - is the occupancy sensor behavior configurable?

Good morning. I have also noticed that with the latest version of Frigate 0.14 and the version 5.3.0 of the integration, sometimes the "Occupancy Sensor" is activated but there is no recorded snapshot nor clip. With version 0.13 I had not experienced anything similar. Maybe it's just coincidence (?) but I see that other users report the same problem above. Inside the yard where the cameras are operating there is a big dog and sometimes Frigate recognizes him as a "person". But I don't have a snapshot to see exactly what has happened.

There are a number of things that are different:

frigate events require that the object has moved at some point after it was detected. The occupancy sensor does not.
Frigate events required that either the snapshot or the recordings config be met (0.13) or the review config be met (0.14) to show in the UI, but this is not the case for the occupancy sensor

Hi everyone, going back to the original problem, i have a similar one.
If i stop the frigate add-on from HA while is detecting one or more persons, when i start frigate again, the person count and occupancy sensors in HA are not cleared and retain the previous values.
On the other hand, the "all count" and "all occupancy" are cleared.
I'm using Frigate 0.14.0.
Frigate is stopped by a script as follow (and started in the same way):
service: hassio.addon_stop
data:
  addon: ccab4aaf_frigate-fa-beta

In the attached picture an example of how the HA integration is showing frigate sensors of a clean scene.
Particularly Frigate was stopped while detecting 2 persons, and started it afterwards when the scene was empty.
Note the "all" sensors cleared, while "person" sensor with incorrect retained value .

@NickM-27 following up on this topic.

The occupancy sensors have less verification in order to be able to respond faster. This is working as expected.
The /events or /reviews topic should be used for notifications

I have switched my automations to use the /events topic, but I'm still getting notifications even when there are no detections seen in the Frigate UI. And I can confirm there was not actually a person within view of the camera.
Here is my automation yaml. The trigger is an mqtt message on frigate/events. Then I have conditions to specify that it is a new detection. The object is a person. And the score is >=0.8.
Am I making any errors here? My guess is that it's something to do with the minimum detection score, but I can't see what I'm missing.
alias: House - Notify when back porch camera detects person while alarm is armed
description: ""
trigger:
  - platform: mqtt
    topic: frigate/events
    id: frigate-event
    payload: back_porch_camera
    value_template: "{{ value_json['after']['camera'] }}"
    variables:
      after_zones: "{{ trigger.payload_json['after']['entered_zones'] }}"
      before_zones: "{{ trigger.payload_json['before']['entered_zones'] }}"
      camera: "{{ trigger.payload_json['after']['camera'] }}"
      id: "{{ trigger.payload_json['after']['id'] }}"
      label: "{{ trigger.payload_json['after']['label'] }}"
      score: "{{ trigger.payload_json['after']['score'] }}"
      time_clip_start: "{{ trigger.payload_json['after']['start_time'] - 10.0 }}"
      after_attributes: "{{ trigger.payload_json['after']['current_attributes'] }}"
    alias: Back Porch Camera MQTT message received
condition:
  - condition: or
    conditions:
      - condition: template
        value_template: "{{ trigger.payload_json['type'] == 'new' }}"
      - condition: template
        value_template: "{{ trigger.payload_json['type'] == 'update' }}"
      - condition: template
        value_template: "{{ before_zones | length == 0 }}"
    alias: New detection
    enabled: true
  - condition: template
    value_template: "{{ trigger.payload_json[\"after\"][\"label\"] == \"person\" }}"
    alias: Object is a person
  - alias: Min score for detection
    condition: template
    value_template: "{{ trigger.payload_json[\"after\"][\"score\"] >= 0.8 }}"
action:
  - data:
      filename: /config/www/back_porch_camera_snapshot.jpg
    target:
      entity_id:
        - camera.back_porch
    action: camera.snapshot
  - data:
      message: Person detected
      title: Back Porch Camera
      data:
        push:
          sound:
            name: default
            critical: 1
            volume: 1
        image: >-
         REDACTED/back_porch_camera_snapshot.jpg
        actions:
          - action: URI
            title: View Cameras
            url: /lovelace/home
    action: notify.notify
mode: single

we need to see the mqtt payload that triggered it to know why, but if I had to guess the object never moved which is a requirement for a snapshot, clip, review item to be saved

I don't have the mqtt message saved. But my guess is that a shadow or something is getting detected and so its probably not moving.
Is there an additional condition I can add to my automation to prevent it from triggering?

you can check position_changes > 0

Thanks! I'll give that a shot.

I came here looking for a bug and I think I found it 😅 Definitely there is something going on, today this issue happened to me (twice in 2 minutes, 7.13pm and 7.15pm), I got occupancy triggered in HA but nothing in Frigate's Review tab, this triggered the siren
Running latest version of everything (HA and Frigate v0.14), I didn't run into this issue before. I couldn't collect any MQTT log, I'll see if using /events I could fix it, wondering what position_changes > 0 does, btw!
Thanks!

Wondering if there is a quick way to add a binary_sensor like person occupancy based on /events or /reviews for a specific zone (because I need a binary_sensor entity for Alarmo).

I just wanted to jump back in this thread to say that I haven't had any more false triggers since adding the position_changes>0 condition to my automation. Although I agree with @gvillo that a simple binary_sensor that follows /events or /reviews would be the cleanest solution in the future.
Here's my current automation yaml in case anyone wants to implement it on their side.
alias: House - Notify when back porch camera detects person
description: ""
trigger:
  - platform: mqtt
    topic: frigate/events
    id: frigate-event
    payload: back_porch_camera
    value_template: "{{ value_json['after']['camera'] }}"
    variables:
      after_zones: "{{ trigger.payload_json['after']['entered_zones'] }}"
      before_zones: "{{ trigger.payload_json['before']['entered_zones'] }}"
      camera: "{{ trigger.payload_json['after']['camera'] }}"
      id: "{{ trigger.payload_json['after']['id'] }}"
      label: "{{ trigger.payload_json['after']['label'] }}"
      score: "{{ trigger.payload_json['after']['score'] }}"
      position_changes: "{{ trigger.payload_json['after']['position_changes'] }}"
      time_clip_start: "{{ trigger.payload_json['after']['start_time'] - 10.0 }}"
      after_attributes: "{{ trigger.payload_json['after']['current_attributes'] }}"
    alias: Back Porch Camera MQTT message received
condition:
  - alias: Prevent multiple, consecutive notifications
    condition: template
    value_template: >-
      {{ (now().timestamp() -
      state_attr('automation.house_notify_when_back_porch_camera_detects_person',
      'last_triggered').timestamp()) / 60 > 5 }}
    enabled: true
  - condition: or
    conditions:
      - condition: template
        value_template: "{{ trigger.payload_json['type'] == 'new' }}"
      - condition: template
        value_template: "{{ trigger.payload_json['type'] == 'update' }}"
      - condition: template
        value_template: "{{ before_zones | length == 0 }}"
    alias: New detection
    enabled: true
  - condition: template
    value_template: "{{ trigger.payload_json[\"after\"][\"label\"] == \"person\" }}"
    alias: Object is a person
  - alias: Min score for detection
    condition: template
    value_template: "{{ trigger.payload_json[\"after\"][\"score\"] >= 0.8 }}"
  - alias: Objected has moved
    condition: template
    value_template: "{{ trigger.payload_json[\"after\"][\"position_changes\"] > 0 }}"
action:
  - data:
      filename: /config/www/back_porch_camera_snapshot.jpg
    target:
      entity_id:
        - camera.back_porch
    action: camera.snapshot
  - data:
      message: Person detected
      title: Back Porch Camera
      data:
        push:
          sound:
            name: default
            critical: 1
            volume: 1
        image: >-
          REDACTED/back_porch_camera_snapshot.jpg
        actions:
          - action: URI
            title: View Cameras
            url: /lovelace/home
    action: notify.notify
mode: single

I would agree 100% with that: "a simple binary_sensor that follows /events or /reviews would be the cleanest solution in the future".
In my case I take a different approach. I don't use the "position_changes>0" option but I look into the MQTT messages to see if Frigate has created a snapshot. So far it seems to be working οκ, but if anyone knows better I would like their opinion on the automation I am using:

id: '.....'
alias: ALARM Front Garden Person Detected - MQTT
description: ''
trigger:

platform: mqtt
topic: frigate/events
id: frigate-event
payload: front-garden
value_template: '{{ value_json[''after''][''camera''] }}'
variables:
camera: '{{ trigger.payload_json[''after''][''camera''] }}'
id: '{{ trigger.payload_json[''after''][''id''] }}'
label: '{{ trigger.payload_json[''after''][''label''] }}'
has_snapshot: '{{ trigger.payload_json[''after''][''has_snapshot''] }}'

condition:

condition: or
conditions:

condition: and
conditions:

condition: device
device_id: .....
domain: alarm_control_panel
entity_id: .....
type: is_armed_home
condition: template
value_template: '{{ trigger.payload_json[''after''][''has_snapshot''] == true }}'

condition: and
conditions:

condition: device
device_id: ....
domain: alarm_control_panel
entity_id: ....
type: is_triggered
condition: template
value_template: '{{ trigger.payload_json[''after''][''has_snapshot''] == true }}'

action:

device_id: ....
domain: alarm_control_panel
entity_id: ....
type: trigger
action: media_player.volume_set
metadata: {}
data:
volume_level: 0.8
target:
device_id: ....
enabled: true
action: tts.speak
metadata: {}
data:
cache: true
media_player_entity_id: media_player.vlc_telnet
language: el
message: ....
target:
entity_id: tts.google_en_com
enabled: true
mode: single

Hi everyone, going back to the original problem, i have a similar one. If i stop the frigate add-on from HA while is detecting one or more persons, when i start frigate again, the person count and occupancy sensors in HA are not cleared and retain the previous values. On the other hand, the "all count" and "all occupancy" are cleared. I'm using Frigate 0.14.0. Frigate is stopped by a script as follow (and started in the same way):

I have exactly the same issue, anybody found a solution?

I was trying to create my custom binary sensor but I couldn't make it work ok, hmmm wondering if Frigate can expose them based on mqtt events

I once built a sensor as a template. In a quick test it worked.
template:
  - trigger:
      platform: mqtt
      topic: frigate/events
      payload: garage
      value_template: '{{ value_json[''after''][''camera''] }}'
      variables:
        label: '{{ trigger.payload_json[''after''][''label''] }}'
        position_changes: '{{ trigger.payload_json[''after''][''position_changes''] }}'
        has_snapshot: '{{ trigger.payload_json[''after''][''has_snapshot''] }}'
        type: '{{ trigger.payload_json[''type''] }}'
    condition:
      - '{{ label == ''person'' }}'
      - '{{ position_changes > 0 }}'
      - '{{ has_snapshot == true }}'
    binary_sensor:
      - name: Kamera Garage Person erkannt
        icon: mdi:motion-sensor
        state: >
          {% if type != 'end' %}
            true
          {% else %}
            false
          {% endif %}

Following because I just realized why my occupancy sensor was wrong so often as every restart of HA from a config change is clearing all of these.
These object occupancy and object count sensors are useful but very unreliable.

Change the status messages to be retained in MQTT, this will allow Home Assistant to pick up the correct state even if it misses the initial message, it could just re-check MQTT occasionally.

I don't think this makes sense because while they can be retained, they are still not necessarily correct if it is Frigate that changed not home assistant. It is just shifting the problem to a separate scenario.

This will allow the integration to properly mark the entities as unavailable if Frigate crashes without being able to update the frigate/available topic.

Frigate does not update this topic when it stops, that is done by MQTT itself as a LWOT

Have Frigate re-publish all of it's statuses on startup BEFORE updating the frigate/available topic. This will ensure that the integration has all of the current statuses on startup before it marks the entities as available.

this is already the case except it is not done before /available though I don't think that is important as /available is not used as the source of truth for all of the sensors availability.

Either add an API endpoint to Frigate to request re-publishing all of the current statuses which the integration could then hit occasionally to make sure everything is up-to-date

this already exists in Frigate as part of the recent UI rewrite and is most likely the solution that will be implemented as it will follow what the Frigate webUI already has implemented.

Change the status messages to be retained in MQTT, this will allow Home Assistant to pick up the correct state even if it misses the initial message, it could just re-check MQTT occasionally.

I don't think this makes sense because while they can be retained, they are still not necessarily correct if it is Frigate that changed not home assistant. It is just shifting the problem to a separate scenario.

This wouldn't fix things on it's own, but it would have to be done in conjunction with the other ideas to deal with the issue of the values being out of sync with reality.

This will allow the integration to properly mark the entities as unavailable if Frigate crashes without being able to update the frigate/available topic.

Frigate does not update this topic when it stops, that is done by MQTT itself as a LWOT

That makes more sense! I forgot about MQTT LWOTs.

Have Frigate re-publish all of it's statuses on startup BEFORE updating the frigate/available topic. This will ensure that the integration has all of the current statuses on startup before it marks the entities as available.

this is already the case except it is not done before /available though I don't think that is important as /available is not used as the source of truth for all of the sensors availability. This would also not help the issue being discussed here where home assistant is restarted but Frigate is not

If the statuses are not being retained, then they don't need to be published before /available is updated, there is nothing there, so it's impossible for Home Assistant to have incorrect data at startup. As far as it being for when Frigate is restarted rather than when Home Assistant is restarted, that is true, but I was looking for ways to improve the overall reliability, not just one specific case.

Either add an API endpoint to Frigate to request re-publishing all of the current statuses which the integration could then hit occasionally to make sure everything is up-to-date

this already exists in Frigate as part of the recent UI rewrite and is most likely the solution that will be implemented as it will follow what the Frigate webUI already has implemented.

This would be an easier solution, especially if that API endpoint already exists in Frigate.  When this is implemented, can we have the interval that things are re-polled be configurable please?


[QUERY] How can I create (or mock) a Pageable to use in my unit tests?

Query/Question
I'm trying to create mocks to unit test a filter I use into a Pageable list resulted from a call to BlobContainerClient.GetBlobs() (see bellow the method logic I'm trying to test and the method I'm using from the BlobContainerClient class).

As I could see in your github, the Pageable is created throught the StorageAsyncPageable class, which is a private class (bellow, the classes I've followed to get into this conclusion).

Is there another way to create (or mock) a Pageable that I could use to test my .Where clause?
Thank you!
Environment:

.Net Version: Full Framework 4.8
New version: Azure.Storage.Blobs v12.8.0
IDE and version : Visual Studio 16.8.5

https://github.com/Azure/azure-sdk-for-net/issues/20091#issuecomment-813619200
You can use Azure.Core.PageResponseEnumerator.  An example of this is here - https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/storage/Azure.Storage.Blobs.ChangeFeed/tests/ChangeFeedTests.cs#L73


Fixes #250 by adding --offline option to pcli balance

Now we can check what the balance is in the currently cached wallet.

LGTM


Eynollah

Maybe we should create (yet another) new category for "reading order detection" since that will become more important the more we move towards complex layouts.

Problematic as long as all these processors do not expose RO detection as separate step. You could do it with ocrd-cis-ocropy-segment already (because it allows running incrementally, i.e. not touch existing segments, just re-order them). But this would only confuse users ATM IMHO.


Wrong Command with Volumes

After running mkdir -p /opt/vestacp/{vesta,home,backup}, user made backup folder, but the next command it said:
docker run -d --restart=always -p 2222:22 -p 80:80 -p 443:443 -p 3306:3306 -p 5432:5432 -p 8083:8083 -v /opt/vestacp/vesta:/vesta -v /opt/vestacp/home:/home -v /opt/vestacp/data:/backup niiknow/vestacp
But user did not create /opt/vestacp/data before, so I think the /opt/vestacp/data:/backup should be /opt/vestacp/backup:/backup.
But even I change the command as /opt/vestacp/backup:/backup, Vesta still said there is not backup file but I am sure I put it right. Any idea about this?

Yes, it should be /opt/vestacp/backup.  I'll update the doc/README.   Did you successfully create the folders in /opt/vestacp/?
I'm just using /opt/vestacp as example.  You can use ~/vestadata/{vesta,home,backup} if you don't have access to /opt folder.  It's up to you.
Also, where are you getting the there's not a backup file message?  Are you trying to do restore?

I tried to rebuild the image and container, then the problem is solved.


[Refactor][Build] Unify common parts of CI and Prod Dockerfile into base images and automate Prod image builds

What and why to refactor
The prod Dockerfile (devlake) and CI Dockerfile (lake-builder) share a lot of dependencies, and are built on top of a Go (Alpine) and Python (Debian) base image. This, as a result, leads to quite a bit of duplicate code between these two.
Describe the solution you'd like

Create two Dockerfiles for each of the base images mentioned above to install the common dependencies into each of them. The Prod and CI Dockerfiles should then inherit from these images instead.
Move the Prod Dockerfile to the devops directory to be consistent with the other Dockerfiles.
Create a Github workflow to trigger pushing it to Dockerhub and support the "latest" tag. , I suggest versioned images be only based on pushed tags similar to CI, and "latest" for both that and main branch builds. Update Readme accordingly.

@keon94 we should update the latest tag only for formal releases, e.g. v0.16.1/0.17.0 those without suffixes.

@klesh Should we use a custom tag then? Like dev?

@klesh Should we use a custom tag then? Like dev?

When will we update the dev tag?

@klesh I was thinking after every merge to main we run the job on the main branch.

@keon94 I see, who would be using this dev for what purposes?


Unnecessarily required groups in Product creation

The groups parameter should not be required in the apimcreateorupdateproduct task.
Groups are not available in the Consumption tier and the task fails when ran against such a tier.

Hi Michal,
Note that the extension has never been tested with the consumption tier which has its own way of working. For the time being, I don't plan to take it into account but feel free to contribute :)
Best Regards


ImportError: No module named pdfminer.pdfdocument

No go. Module is installed.

It's a python version issue. I've now ported the repo to python3 and pdfminer.six.


Pull request webhook ext

[ ] All tests passed. If this feature is not already covered by the tests, I added new tests.
[x] I used go fmt ./... for formatting the code before submitting the pull request.
[x] This feature is included on all supported VCS providers - GitHub, Bitbucket cloud, Bitbucket server, and GitLab.

@pavelmemory,
Will you be able to add a clear description to the PR's body?


FS-1464: add Target field when creating a condition

It looks we are missing the Target field when creating a condition.
Target remains 00000000-0000-0000-0000-000000000000 which causes error

I was working on this as well and have a slightly different approach - https://github.com/metal-toolbox/conditionorc/pull/208
mind if we close this issue in favour of the one linked?


eda-logo.svg file broken

https://github.com/ansible/ansible-ui/blob/main/frontend/eda/eda-logo.svg seems to be broken. It cannot be rendered in github and when downloaded, different tools say the file is broken.
Imageviewer on Pop!OS shows errormessage "XML parse error: Error domain 1 code 64 on line 2 column 6 of data: XML declaration allowed only at the start of the document"

sorry for the noise, this seemed to be a local issue


[v2] add minimal metadata endpointg for entities

try to request full vikenna first and see how performant that is


dad.animation.curAnim.name not working if character is a Atlas

Describe your bug here.
If the character is a atlas, scripts that use "dad.animation.curAnim.name" don't work.
if its a spritesheet however, it works fine.
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
no, source code is not edited.

for the people wondering what u gotta use, it's dad.atlas.anim.lastPlayedAnim


Add ClassificationTask Enum

What does this PR do?
Fixes #1478
Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

We also need to import EnumStr instead of StrEnum as we're using an older version of lightning utilities.

We also need to import EnumStr instead of StrEnum as we're using an older version of lightning utilities.

Just set the min version to 0.5.0


"Live Preview was cancelled ..." pop-up (balloon) leaves an unclickable area after it disappears

Steps to trigger the problem:

Open browser using the lightning bolt button.
Close browser (and see the "Live Preview was cancelled..." message next to button)
Try to click in the area where the message was.

The text-entry mouse-pointer turns into an arrow pointer when hovering over that area. Expected to be able to click that side area to move cursor to the end of the second line of text.
Brackets version:
Release 1.1 build 1.1.0-15558 (release ea908cae5)
build timestamp: Thu Dec 18 2014 10:23:10 GMT-0800
OS version:
Windows 8
Tried reloading without extensions and it still occurs.

He's not kidding, I have this problem on both my Mac and Windows computer.

@sebaslv @busykai git bisect points to https://github.com/adobe/brackets/commit/235c551.
Notice though that this happens with livedev.multibrowser: false, too.

Thanks for the info, @MarcelGerber! It helps!

Reviewed - marking medium since this is a regression.

This was fixed in eef9c68a1fdff372b9ea6352cacb5e2506e55be9.

Closing as fixed. (see above)


Design

If I understand correctly, mutations and subscriptions in GraphQL are also queries (special queries).
So what about the only single one universal web component instead of 3 (<apollo-query>, <apollo-mutation>, <apollo-subscription>)?

Can you show me an example of a document you'd like to build with these elements? How would It look, what would the APIs be like? I want to get a better idea of your use case.

Since web components are interoperable, they can be used in a Polymer project, despite the fact that they themselves are written using lit-element.
Something like:
If I use apollo web components in <my-view> written using Polymer:
import {PolymerElement, html} from<EMAIL_ADDRESS>import<EMAIL_ADDRESS>// import apollo web components

class MyView extends PolymerElement {

  static get properties() {
    return {
      searchId: {
        type: String
      },
      data: {
        type: Object
      }
    }
  }

  static get template() {
    return html`
      <paper-input value="{{searchId}}"></paper-input>

      <apollo-config uri="https://graphql.endpoint/graphql"></apollo-config>

      <apollo-client
          query='{
            post(id: "[[searchId]]") {
              id
              title
              content
              published
            }
          }'
          data="{{data}}">
      </apollo-client>

      Post title: [[data.post.title]]
      Post content: [[data.post.content]]
    `;
  }

}

customElements.define('my-view', MyView);

If I use apollo web components in <my-view> written using lit-element (there is no two-way data binding in lit-element):
import {LitElement, html} from<EMAIL_ADDRESS>import<EMAIL_ADDRESS>// import apollo web components

export class MyView extends LitElement {

  static get properties() {
    return {
      searchId: String,
      data: Object
    }
  }

  onValueChanged(e) {
    this.searchId = e.detail.value;
  }

  onDataChanged(e) {
    this.data = e.detail.value;
  }

  _render({searchId, data}) {
    return html`
      <paper-input on-value-changed="${this.onValueChanged.bind(this)}"></paper-input>

      <apollo-config uri="https://graphql.endpoint/graphql"></apollo-config>

      <apollo-client
          query='{
            post(id: "${searchId}") {
              id
              title
              content
              published
            }
          }'
          on-data-changed="${this.onDataChanged.bind(this)}">
      </apollo-client>

      Post title: ${data.post.title}
      Post content: ${data.post.content}
    `;
  }

}

customElements.define('my-view', MyView);

GraphQL varibles
When the searchId variable change, the query gets automatically re-fetched.
We can dinamically change searchId variable value using Polymer data binding.
GraphQL real-time subscriptions (updates)
<apollo-client
    subscription='{
      post(published: true) {
        id
        title
        content
        published
      }
    }'
    data="{{data}}">
</apollo-client>

When published posts (posts with published: true) change (added or deleted), data automatically changes.
Desing questions
First variant — one single universal <apollo-client> web component for queries, mutations and subscriptions (query, mutation, subscription are attributes (properties) of the web component):
<apollo-client
    query=""
    data="">
</apollo-client>

<apollo-client
    mutation=""
    data="">
</apollo-client>

<apollo-client
    subscription=""
    data="">
</apollo-client>

Second variant — one single universal <apollo-client> web component for queries, mutations and subscriptions (query, mutation, subscription are keywords that used inside query):
<apollo-client
    query='
      query {
        users {
          id
          name
          email
          isAdmin
        }
      }'
    data="">
</apollo-client>

<apollo-client
    query='
      mutation {
        createUser(data: {
          name: "Alice"
          email<EMAIL_ADDRESS>        }) {
          id
        }
      }'
    data="">
</apollo-client>

<apollo-client
    query='
      subscription {
        post(published: true) {
          id
          title
          content
          published
        }
      }'
    data="">
</apollo-client>

Variables in GraphQL uses $name syntax: http://facebook.github.io/graphql/October2016/#sec-Language.Variables
Is it possible to use (Polymer) data binding and GraphQL $name syntax (not ${name}, not [[name]]) in queries (automatically associate name property value with $name GraphQL variable value?

Looks like it is possible to write queries in the body of web component, not in query property. Something like:
<apollo-client result="{{data}}">
  query Pagination($skip: Int!) {
    allStarships(first: 5, skip: $skip) {
      name
      class
    }
  }
</apollo-client>

or
<apollo-client result="{{data}}">
  <script type="application/graphql">
    query {
      allStarships(first: 5, filter: {pilots_some: {name_not: ""}}) {
        name
        class
        pilots {
          name
          homeworld {
            name
          }
        }
      }
    }
  </script>
</apollo-client>

What is better?
Is it possible to use varibles if the query placed in the body of web component (not in query property)? Is it possible to use Polymer data binding in this case to dinamically change values of variables? Something like:
static get template() {
  return html`
    <apollo-client data="{{data}}">
      query {
        post(id: [[searchId]]) {
          id
          title
          content
          published
        }
      }
    </apollo-client>
  `;
}

or
_render({searchId}) {
  return html`
    <apollo-client on-data-changed="${this.onDataChanged.bind(this)}">
      query {
        post(id: ${searchId}) {
          id
          title
          content
          published
        }
      }
    </apollo-client>
  `;
}

Will it work inside <script type="application/graphql">? Something like:
static get template() {
  return html`
    <apollo-client data="{{data}}">
      <script type="application/graphql">
        query {
          post(id: [[searchId]]) {
            id
            title
            content
            published
          }
        }
      </script>
    </apollo-client>
  `;
}

or
_render({searchId}) {
  return html`
    <apollo-client on-data-changed="${this.onDataChanged.bind(this)}">
      <script type="application/graphql">
        query {
          post(id: ${searchId}) {
            id
            title
            content
            published
          }
        }
      </script>
    </apollo-client>
  `;
}

Should I escape " symbols inside the query? Something like:
<apollo-client
  query="{ repository(owner: \"bennypowers\", name:\"lit-apollo\") { url } }"
  last-response="{{response}}">
</apollo-client>

Seems if I use ', I shouldn't?
<apollo-client
  query='{ repository(owner: "bennypowers", name: "lit-apollo") { url } }'
  last-response="{{response}}">
</apollo-client>

Should I wrap string variables in double quotes?
I.e.
<apollo-client
    query='{
      post(id: "[[searchId]]") {
        id
        title
      }
    }'
    data="{{data}}">
</apollo-client>

insted of
<apollo-client
    query='{
      post(id: [[searchId]]) {
        id
        title
      }
    }'
    data="{{data}}">
</apollo-client>

or
<apollo-client
    query='{
      post(id: "${searchId}") {
        id
        title
      }
    }'
    on-data-changed="${this.onDataChanged.bind(this)}">
</apollo-client>

instead of
<apollo-client
    query='{
      post(id: ${searchId}) {
        id
        title
      }
    }'
    on-data-changed="${this.onDataChanged.bind(this)}">
</apollo-client>

First of all thank you for the detailed descriptions.
There are a few things I think we need to consider here:

The polymer templating system, though not deprecated, will not be developed in the future. As such, view components that alter their own data are not preferred, rather, events should be exposed to some central state container. This isn't the only design out there, but it is by a large margin the most popular.
I reached out to the apollo client developers, and they have no plans yet to support apps that do not use a bundler. Until they come around, I think it would be misleading to insinuate that we can provide drop-in, work-anywhere components based on apollo-client. The ticket price is a commonjs bundler.
To support legacy polymer3 apps, it should be simple enough to:

customElements.define("apollo-query", class ApolloQueryElement extends ApolloQuery {
 _propertiesChanged(props, changedProps, oldProps) {
    super._propertiesChanged(props, changedProps, oldProps);
    (changedProps.data) && this.dispatchEvent(new CustomEvent("data-changed", {
       bubbles: true,
       composed: true,
       detail: { value: data },
     })
   })
   // error, loading, networkStatus
 }
})

That would provide a similar API to the currently available polymer2 Apollo components.
Would that, and perhaps some guidance around bundling in the README, would that cover your case?

I'd be happy to provide such a component under lit-apollo/legacy/apollo-query.js, likewise for mutation.

It would be very great.

I reached out to the apollo client developers, and they have no plans yet to support apps that do not use a bundler. Until they come around, I think it would be misleading to insinuate that we can provide drop-in, work-anywhere components based on apollo-client. The ticket price is a commonjs bundler.

Look like it's possible to bundle only apollo-client (not the whole app). See e.g.:
https://github.com/matteo-hertel/polymer-graphql/blob/master/polymer/libs/apollo-client.html
https://github.com/reach-digital/polymer-apollo-client/blob/master/build/apollo-client.js

It's not that simple if you want to use custom authentication, subscription transport, etc. I think the apollo developers are set in their ways about requiring (and encouraging) a build step, and until that changes, I'd rather not let on that it's easy to just plug in some pre-made components and get a fully-functional apollo client

@unicodeveloper PTAL, need your help.

@bennypowers

in our library, we're not providing web-components per se, instead we're making base classes which authors are meant to extend

It seems that apollo-mutation is in fact a web component (custom element): https://github.com/bennypowers/lit-apollo/blob/master/apollo-mutation.js#L106, but apollo-query is not. Why?

typo :)
Slightly more legit answer: The design for ApolloMutation is still a WIP. I'm not amazingly happy with the way it is now - you may have to define a new component for each type of mutation. So if your app has 20 kinds of text property mutations, that could potentially be 20 different mutations.

Version 0.1.0 updates the readme to include the example p3-compatible component. Is that enough to close this issue?

I’ve been considering making <apollo-mutation> a decorator element, so you could
<apollo-mutation mutation="${mutation}" mutate-on="input">
  <input slot="mutator"/>
</apollo-mutation>

where mutate-on accepts an event name, which it would listen for on the element in the mutator slot.
I think the pros to this approach would be DX - not having to create a new one-off class with its own _render method for each mutating element.
What would be the implications for styling/dom?

Closing in favour of #11


Correct typo in CLI exception message.

Description

Corrected small spelling error in the catchall exception for the CLI's invoke function.
GitHub Issues

Coverage decreased (-15.3%) to 58.565% when pulling 21f90a6503c99ed6e0c19e429bcf8b55eef3e90b on mihow:patch-2 into 12ac82e71deeffcb03dbb6549be4f6f60d537382 on Miserlou:master.


getLastBlock throws "[FORMAT ERROR] Confirmed transaction object is invalid."

Query: const block = await iconService.getLastBlock().execute();
Throws error: [FORMAT ERROR] Confirmed transaction object is invalid.
While RPC query works well: curl -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method": "icx_getLastBlock"}' https://btp.net.solidwallet.io/api/v3 | jq
icon-sdk-js v1.1.0
I also found several closed issues with same this error but they happened in 2019 with old releases.

Interestingly I found it only happens on our BTP testnet at https://btp.net.solidwallet.io/api/v3 and doesn't happen on public testnet (in SDK docs) at https://bicon.net.solidwallet.io/api/v3.

ICON dev team is testing SDK js on BTP.net

@tiendq We have released fixed version(1.1.2) and it will work on btp-net

@tiendq We have released fixed version(1.1.2) and it will work on btp-net

I still got same error on btp.net
I also noticed you changed back from:
1.1.0 const IconService = require('icon-sdk-js').default;
to 1.1.2 const IconService = require('icon-sdk-js');

@tiendq We have released fixed version(1.1.2) and it will work on btp-net

Never mind, it was my mistake with a nested project.
It's fixed, no error with btp.net now.
Thank you.


6th license activation

I thought the behavior changed, where upon the 6th license activation, O365 will automatically remove the license from the device that is the oldest activated in the list. Please confirm.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f3c236da-c63a-f789-f1b6-7aeb41f16c1f
Version Independent ID: 35319bac-d94f-832c-ce79-41bffe5c8d25
Content: Overview of licensing and activation in Office 365 ProPlus
Content Source: DeployOffice/overview-of-licensing-and-activation-in-office-365-proplus.md
Service: o365-proplus-itpro
GitHub Login: @DHB-MSFT
Microsoft Alias: danbrown

@SLeuthold -- are you referring to the "Automatic sign out" capability mentioned in this recent blog post?  If so, the blog post does say it will be a gradual roll out process, so it might not be available yet for you:
In August, we’ll start slowly rolling out these changes to commercial customers on Monthly Channel. The roll-out will continue to Semi-Annual Channel (Targeted) in January 2020.
Hope that helps.

Yes, thank you!
[cid:InvokeV2_320x123_a1057048-27ef-466c-97e5-e700c239d335.png]http://www.InvokeLLC.com
[cid:Twitter_b17288c0-c42e-4e7b-bc77-033c4322b063.png]   https://twitter.com/InvokeLLC  [cid:Facebook_df83b2d8-63dc-4240-81e8-612606d7af58.png]    https://www.facebook.com/InvokeLLC/  [cid:LinkedIn_c54ffc3c-9f7d-485b-81ad-8b3c147d5a66.png]  https://www.linkedin.com/company/7798865/
Stephen Leuthold / Principal Consultant
Stephen.Leuthold<EMAIL_ADDRESS>+1<PHONE_NUMBER>
Invoke, LLC
+1<PHONE_NUMBER>
118 Vintage Park Blvd. #W
Houston, Texas 77070
https://InvokeLLC.com

Invoke is a 6x Microsoft Gold Partner
[cid:MicrosoftPartner_Logo_6x_300x109_1d6dcca0-33f8-4dee-bfcf-c81cd5db20d3.png]
From: Daniel H. Brown<EMAIL_ADDRESS>Sent: Wednesday, September 25, 2019 12:22 PM
To: MicrosoftDocs/OfficeDocs-DeployOffice<EMAIL_ADDRESS>Cc: Stephen Leuthold<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/OfficeDocs-DeployOffice] 6th license activation (#458)
@SLeutholdhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSLeuthold&data=02|01|Stephen.Leuthold%40InvokeLLC.com|499cbb5b8d1b41f7eda308d741dce293|17883ba725274dc98ed1140f5bb047b9|1|0|637050289262064088&sdata=z5HVkVr0gaWO9B4layCLv04VugcJr150VBrQ7GNwhTg%3D&reserved=0 -- are you referring to the "Automatic sign out" capability mentioned in this recent blog posthttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FOffice-365-Blog%2FOffice-365-Client-Licensing-and-Activation-Improvements%2Fba-p%2F763694&data=02|01|Stephen.Leuthold%40InvokeLLC.com|499cbb5b8d1b41f7eda308d741dce293|17883ba725274dc98ed1140f5bb047b9|1|0|637050289262064088&sdata=EZTNDYSAQg6OKBvdKkzZdsfTgyeFDyC42%2Bmlzz2coVA%3D&reserved=0? If so, the blog post does say it will be a gradual roll out process, so it might not be available yet for you:
In August, we’ll start slowly rolling out these changes to commercial customers on Monthly Channel. The roll-out will continue to Semi-Annual Channel (Targeted) in January 2020.
Hope that helps.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-DeployOffice%2Fissues%2F458%3Femail_source%3Dnotifications%26email_token%3DAJYHABM3BPGWXJWRSS5DZLTQLOM3ZA5CNFSM4I2CKZ72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7SVXOA%23issuecomment-535124920&data=02|01|Stephen.Leuthold%40InvokeLLC.com|499cbb5b8d1b41f7eda308d741dce293|17883ba725274dc98ed1140f5bb047b9|1|0|637050289262074084&sdata=9pafMG8Gf0Pm6eCXB%2B5lRDCt43riowqcNxSFjh%2FTa3g%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJYHABJGSHZBHGR4EOZ6KETQLOM3ZANCNFSM4I2CKZ7Q&data=02|01|Stephen.Leuthold%40InvokeLLC.com|499cbb5b8d1b41f7eda308d741dce293|17883ba725274dc98ed1140f5bb047b9|1|0|637050289262074084&sdata=9Mp7C45enQLOLa1Uz4XwmJ4%2BJ203gh4HTwdFyD4YAZI%3D&reserved=0.


[bicoeff apass] not working on ms-windows

When opening "apass~help.pd" i get:
else/bicoeff apass 750 1
... couldn't create

hi, what version do you have? In beta6 you shouldn't have the "apass~-help.pd" file as this object has been renamed to allpass.2nd~ in beta3 (see release notes: https://github.com/porres/pd-else/releases/tag/v1.0-beta3 )
It seems you have an old version of else, or perhaps mixed/different versions of else combined together. Please do a fresh re-install. Delete whatever you got and download the latest one (beta6: https://github.com/porres/pd-else/releases/tag/v1.0-beta6 ). You can also get it from deken.

I think i had a mixed old and new else library, not intenionally, just using Deken (seems it dont delete, it overwrites.)
Anyway with beta6 I can create [else/bicoeff eq] but not [else/bicoeff apass]. apass is mentioned in the help file.

Seems just a bug in the [bicoeff] help file, as i can create [else/bicoeff allpass], allpass, not apass.
: - )

just using Deken (seems it dont delete, it overwrites.)

yep, it should have an update procedure but it doesnt

Seems just a bug in the [bicoeff] help file, as i can create [else/bicoeff allpass], allpass, not apass.
: - )

Seems you havent done what I told you yet, which is to have a fresh install of beta 6 ;)

I mean, you should be able to create [else/bicoeff allpass] and not "apass", that's what the new help file says

See https://github.com/porres/pd-else/blob/master/help/bicoeff-help.pd line 265.
inlets: <apass, lowpass, highpass, bandpass, resonant, bandstop, eq, lowshelf, highs.....

oh, ok, I missed that then. I thought you mentioned it had a [else/bicoeff allpass] object.
Anyway, fixed! Thanks


[Code Style] IterableExtension

The loop in the take method should be replaced with a while loop.
Also change logic block style in skip

Why should it be done with a while loop?

@stevemasta34 The code fits better with a while. You are abusing the for loop.

I would argue that the memory constraints and scope imposed by the for-construct is actually "fully utilizing" the native language


Webpack 3 + Karma browserselection

Add an option to choose which browser should be used for Karma unit tests
Edit: Webpack is updated to version 3.

I've removed the ModuleConcatentionPlugin from development config as its of course not needed there.
I also updated webpack to version 3. Yes, the title of the PR doesn't indicate that. Should I open another PR or just update the title of this PR?

@c0defre4k webpack 3 support is going to be a significant change and definitely should be handled in a separate PR. There's an issue with some background info: https://github.com/vuejs-templates/webpack/issues/751

@MaxMilton I see - thanks. I've updated the PR to focus on Karma browserselection

We will deprecate the karma setup in the forseeable future in favor of jest.
For that reason, I don't think it's  very useful to extend the questionaire with further options, so I have to close this PR.
Thanks for the efforts nontheless!


feat: use try_into in sqlx::query_as! conversions

closes #2648

This is a breaking change.

should the blanket TryFrom where From impl not prevent this from being breaking?

If I'm honest, it's mostly a gut feeling that a sweeping change like this should not sneak into a minor release. Even if it seems like it should be backward-compatible, there may be some subtle detail that we're not seeing that comes back to bite us later.
We should also be considerate of forward compatibility. If this change goes out in a minor release and someone updates their code to rely on it, then has to downgrade for whatever reason (e.g. to work around a bug), they're going to have a huge headache.
In all, my gut is telling me this is something that should be reserved for 0.8.0.

Separately from the question of whether it's a breaking change, is this really the right thing to do? It would allow querying a table with an INTEGER column into a struct that has a field of type u8. While I guess it is convenient that it allows you to use unsigned types with postgres without extensions if you don't exceed i64::MAX and such, I really worry about this masking bugs where the types are unintentionally different. IMHO try_into decoding should be opt-in per query, not the default, if supported at all.

That is a fair concern as well. It has a lot of potential to turn compile-time errors into runtime errors, which is exactly the opposite of what we want.

Would a try_query_*! set of macros make more sense to solve this issue?

I think it would be better to be able to opt into this on a per-field basis, and require the user to explicitly specify the type to decode to ensure type-safety.
Ultimately, we want query_as!() to be able to work with #[derive(FromRow)], and I think that would be the best place to do this, e.g. #[sqlx(try_from = "<type to decode from>")]. That feature is being discussed in https://github.com/launchbadge/sqlx/issues/514. It theoretically doesn't have any blockers but as I explain in my latest comments there, the support from the language is not quite where I want it to be yet.
I have an alternative, more immediately actionable idea which I'll elaborate on in the motivating issue, #2648. I'm going to close this PR as I'm not prepared to merge it as written because of the problems we've discussed.


Link points to .NET 5 for page displayed for .NET 6.

The permalink under section "Direct download (current version)" points to .NET 5 - should by .NET 6 by now!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 65973393-2cb9-a656-01b8-7963a7a40b39
Version Independent ID: 22e2323b-18c3-ad2b-174c-84fbf642715e
Content: Hosting Bundle
Content Source: aspnetcore/host-and-deploy/iis/hosting-bundle.md
Product: aspnet-core
Technology: aspnetcore-hostdeploy
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Hello @biilmanndk ... This is a dup of https://github.com/dotnet/AspNetCore.Docs/issues/23934. We'll get the link updated.

btw --- It's one of those permalink deals. It should work out that no matter where this link is, it's destination will get updated internally so that the link URL in the doc won't need a change. They just need to make the update internally to make it point to latest.


Handling multiple ML label probabilities for the same source

Since we generate separate feature sets from each ZTF light curve for a single source, in many cases we will have multiple ML labels for one source with different probabilities. We will need to decide how to combine these probabilities into a single classification/probability to post to Fritz. We could take a simple mean of repeated label probabilities, or @reed0824 suggested we could take a weighted mean based on the SNR of each light curve.

scope.py select_al_sample currently supports mean, median and max (default mean).


Upload MAS image

Token: MasterNet
Symbol: MAS
Total Supply: 200,000,000
Smart contract: https://etherscan.io/address/0x0dce40212e3c689ad502739e283d9c3ac79727bc#readContract
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[x] Filename in the lowercase format
[x] Image format: png
[x] Image size: 256 by 256 px

Also, you can use these graphics to say that your ERC20 token fully compatible with Trust Wallet (https://trustwalletapp.com/logo-assets). Tokens will show up automatically once the user receives them.
Feel free to share this on social media and tag Trust Wallet:
Twitter: @TrustWalletApp
Facebook: @TrustWalletApp


Extended debug mode

load the original src block in debug mode.

nice, I like it

merged via f3da50a


Update types-abstract-operator-overloading.md

Added underlying type op example.
https://groups.google.com/d/msg/haxelang/NDnuMEAifE8/O_0MkYsV5CsJ

Thanks, but the markdown files are generated from the .tex source. I'll integrate it there instead.