query_range result is not accurate when step is too large

What did you do?
Update metric "input_record_count", then uses /query_range api to query it.
query=input_record_count
start=2023-01-01T00:00:00.000Z
end=2023-01-07T00:00:00.000Z
when the step=2h, the last metric value of container "flow1-fhqyswby" is 51, timestamp is<PHONE_NUMBER>
when the step=12h, the last metric value of container "flow1-fhqyswby" is 44, timestamp is<PHONE_NUMBER>
I am wondering what causes the last metric values are different.
Thanks.
What did you expect to see?
No response
What did you see instead? Under which circumstances?
http://localhost:53718/api/v1/query_range?query=input_record_count&start=2023-01-01T00:00:00.000Z&end=2023-01-07T00:00:00.000Z&step=12h

{
"status":"success",
"data":{
"resultType":"matrix",
"result":[
{
"metric":{
"name":"input_record_count",
"container":"flow1-fhqyswby",
"endpoint":"admin-ui",
"environment":"env1",
"flowName":"Flow_1",
"instance":"<IP_ADDRESS>:8008",
"namespace":"datachannels",
"pod":"flow1-fhqyswby-0",
"username":"admin"
},
"values":[
[
1672963200,
"37"
],
[
1673006400,
"44"
]
]
},
{
"metric":{
"name":"input_record_count",
"container":"flow1-nxlicnjl",
"endpoint":"admin-ui",
"environment":"Development",
"flowName":"Flow_1",
"instance":"<IP_ADDRESS>:8008",
"namespace":"development",
"pod":"flow1-nxlicnjl-0",
"username":"admin"
},
"values":[
[
1672531200,
"2"
],
[
1672574400,
"2"
],
[
1672617600,
"2"
],
[
1672660800,
"2"
],
[
1672704000,
"2"
],
[
1672747200,
"2"
],
[
1672790400,
"2"
],
[
1672833600,
"2"
],
[
1672876800,
"2"
],
[
1672920000,
"2"
],
[
1672963200,
"2"
],
[
1673006400,
"2"
]
]
}
]
}
}

http://localhost:53718/api/v1/query_range?query=input_record_count&start=2023-01-01T00:00:00.000Z&end=2023-01-07T00:00:00.000Z&step=2h

{
"status":"success",
"data":{
"resultType":"matrix",
"result":[
{
"metric":{
"name":"input_record_count",
"container":"flow1-fhqyswby",
"endpoint":"admin-ui",
"environment":"Data-Channels",
"flowName":"Flow_1",
"instance":"<IP_ADDRESS>:8008",
"namespace":"datachannels",
"pod":"flow1-fhqyswby-0",
"username":"admin"
},
"values":[
[
1672948800,
"34"
],
[
1672956000,
"37"
],
[
1672963200,
"37"
],
[
1672970400,
"44"
],
[
1672977600,
"44"
],
[
1672984800,
"44"
],
[
1672992000,
"44"
],
[
1672999200,
"44"
],
[
1673006400,
"44"
],
[
1673013600,
"44"
],
[
1673020800,
"51"
],
[
1673028000,
"51"
],
[
1673035200,
"51"
],
[
1673042400,
"51"
]
]
},
{
"metric":{
"name":"input_record_count",
"container":"flow1-nxlicnjl",
"endpoint":"admin-ui",
"environment":"Development",
"flowName":"Flow_1",
"instance":"<IP_ADDRESS>:8008",
"namespace":"development",
"pod":"flow1-nxlicnjl-0",
"username":"admin"
},
"values":[
[
1672531200,
"2"
],
[
1672538400,
"2"
],
[
1672545600,
"2"
],
[
1672552800,
"2"
],
[
1672560000,
"2"
],
[
1672567200,
"2"
],
[
1672574400,
"2"
],
[
1672581600,
"2"
],
[
1672588800,
"2"
],
[
1672596000,
"2"
],
[
1672603200,
"2"
],
[
1672610400,
"2"
],
[
1672617600,
"2"
],
[
1672624800,
"2"
],
[
1672632000,
"2"
],
[
1672639200,
"2"
],
[
1672646400,
"2"
],
[
1672653600,
"2"
],
[
1672660800,
"2"
],
[
1672668000,
"2"
],
[
1672675200,
"2"
],
[
1672682400,
"2"
],
[
1672689600,
"2"
],
[
1672696800,
"2"
],
[
1672704000,
"2"
],
[
1672711200,
"2"
],
[
1672718400,
"2"
],
[
1672725600,
"2"
],
[
1672732800,
"2"
],
[
1672740000,
"2"
],
[
1672747200,
"2"
],
[
1672754400,
"2"
],
[
1672761600,
"2"
],
[
1672768800,
"2"
],
[
1672776000,
"2"
],
[
1672783200,
"2"
],
[
1672790400,
"2"
],
[
1672797600,
"2"
],
[
1672804800,
"2"
],
[
1672812000,
"2"
],
[
1672819200,
"2"
],
[
1672826400,
"2"
],
[
1672833600,
"2"
],
[
1672840800,
"2"
],
[
1672848000,
"2"
],
[
1672855200,
"2"
],
[
1672862400,
"2"
],
[
1672869600,
"2"
],
[
1672876800,
"2"
],
[
1672884000,
"2"
],
[
1672891200,
"2"
],
[
1672898400,
"2"
],
[
1672905600,
"2"
],
[
1672912800,
"2"
],
[
1672920000,
"2"
],
[
1672927200,
"2"
],
[
1672934400,
"2"
],
[
1672941600,
"2"
],
[
1672948800,
"2"
],
[
1672956000,
"2"
],
[
1672963200,
"2"
],
[
1672970400,
"2"
],
[
1672977600,
"2"
],
[
1672984800,
"2"
],
[
1672992000,
"2"
],
[
1672999200,
"2"
],
[
1673006400,
"2"
],
[
1673013600,
"2"
],
[
1673020800,
"2"
],
[
1673028000,
"2"
],
[
1673035200,
"2"
],
[
1673042400,
"2"
]
]
}
]
}
}

System information
Linux 5.4.0-1094-azure x86_64
Prometheus version
prometheus, version 2.32.1 (branch: HEAD, revision: 41f1a8125e664985dd30674e5bdf6b683eff5d32)
  build user:       root@54b6dbd48b97
  build date:       20211217-22:08:06
  go version:       go1.17.5
  platform:         linux/amd64

Prometheus configuration file
No response
Alertmanager version
No response
Alertmanager configuration file
No response
Logs
No response

The difference in the last metric value for the same container and time period between the two queries is due to the different step sizes used in the queries, and it is expected, not a bug.
The step parameter in a Prometheus query determines the resolution of the returned data. A smaller step size will result in a larger amount of data points being returned, each with a smaller time interval between them. A larger step size will result in fewer data points, each with a larger time interval between them.
In the first query, with a step size of 12 hours, the last metric value for the container "flow1-fhqyswby" is 44 at a timestamp of<PHONE_NUMBER>. In the second query, with a step size of 2 hours, the last metric value for the same container and time period is 51 at a timestamp of<PHONE_NUMBER>. This means that there were more input records counted for the container within the 2 hour interval leading up to<PHONE_NUMBER> compared to the 12 hour interval leading up to<PHONE_NUMBER>.
1673042400 is 10 hours after<PHONE_NUMBER>.
I hope this helps to explain the difference in the last metric values between the two queries. Let me know if you have any further questions.


rink: 0.4.5 -> 0.5.0

Motivation for this change
https://github.com/tiffany352/rink-rs/releases/tag/v0.5.0
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 93404 1

1 package built:
- rink

[x] version fits guideline
[x] commit text fits guidelines
[x] package maintainers are notified
[x] meta field information is correct
[x] code contains no typos
[x] package built / executable was run

Cool stuff, didn't know about rink. Every physics student should know about that!

Every physics student should know about that!

More experienced physicists also use it :)


Adding balance funds occurs twice

This is related to this issue, but doesn't seem to be prioritised: https://github.com/boxbilling/boxbilling/issues/426
When a balance funds invoice is generated by a customer, once a cron job is run it puts the invoice into the customer's history (even if it's not paid) and therefore puts the amount into their balance. Then if the invoice does get paid, it shows the PayPal transaction in the customer's history, therefore they get the balance TWICE.
Has anyone found or made a fix for this yet? Any help is greatly appreciated!

Don't waste your time with this, nobody will do anything. I got really fucked using boxbilling, and now I focus only on transferring accounts to whmcs...

BoxBilling is fine. It just needs a bit of development work in some places. I'm happy to pay $5/m for something that's actually open source. And I'm willing to pay anyone that is willing to fix this major issue, if BoxBilling's support team won't help.

Or if no developers out there want to help even for money, can someone at least tell me how to reproduce this issue easily so I can try to fix it myself?

@epichosts I have confirmed there are some issues with the way "Added funds" are handled.  For example, if a client has an existing balance of $75, and they add funds of $75, then a new invoice is created for the add funds transaction.  If the client does not pay the $75 right away, then the cron comes along and applies the original $75 to unpaid invoices.  This compounds the issue.
Can you get a screenshot of the client_balance table for the records associated with the customer that added the funds?  The client_balance table is used to calculate the "balance" available that can be applied to unpaid invoices.  I'd like to compare the records that are inserted into this table with those that are being inserted in my table.  I'm curious to see the pluses and minuses associated with the amount column and the descriptions.

Not only do balance invoices get paid by current balances (as you explained in your example), but it also adds the transaction twice from the PayPal payment AND cron job (as I explained previously).
I've already deleted the records so the customer doesn't have the duplicates. But rest assured what I've explained is accurate and there really needs to be a fix for it.

Are you getting two notifications from PayPal on all invoice payments?

No I'm not.

I'll take a look and see what I can do to fix this issue.

Great stuff! Thanks a lot. Will look forward to anything you have to provide and, of course, I'll do my best to provide what information I can to assist in any way with the fix.

Does this occur with any other Gateway besides PayPal?
On Feb 23, 2017 3:35 PM, "epichosts"<EMAIL_ADDRESS>wrote:

Great stuff! Thanks a lot. Will look forward to anything you have to
provide and, of course, I'll do my best to provide what information I can
to assist in any way with the fix.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/boxbilling/boxbilling/issues/479#issuecomment-282113040,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMoDVIvRCjOJkCyydiUfjhQbo5tzsZqhks5rfe2fgaJpZM4MHkFd
.

I don't know unfortunately. PayPal is the only automated API gateway that I use.

If I understood how the coding of BoxBilling worked, I would probably be able to fix it myself. But I have a suggestion:
What if we try remove part of the balance system's part of the code that adds the funds to the customer? Meaning the balance system won't try adding a record into the client's transactions and therefore won't add to the client panel's balance, instead the cron job (or whichever the API is used for the merchant) will apply the record instead and therefore it won't be duplicated.
Do you think that would work?

Your proposal is correct.  The good news is that I know what, and where, things need to be changed.  Finding where to apply the fix in the code is the next step...

No problem at all. Hope you manage to figure it out :)

Please review and test the changes in the last commit of pull request #473

Looks good! I've implemented it and it adds the funds then removes them as expected.
It was a manually paid invoice so there's no API/PayPal transaction involved, which means I'll just have to wait until someone uses PayPal to pay for their balance invoice and will let you know of any updates :)
Thanks a ton!

Welp! It appears that after a cron job is executed, any unpaid balance invoices becomes paid with balance you already have in your account, so it's trying to pay for 'Add funds to account' invoices with funds that are already in your account (not sure if this was happening anyway, or if it only happened since using the new changes). That's now another issue I hope I can get fixed!
It only makes sense for the API/PayPal to work, I'm sure as soon as someone pays with PayPal it will show in the Payments tab, which means this issue is fixed - but I'll still try update on this ASAP once someone uses it :) Just need the above issue fixed now if possible as balance invoices appear to be getting paid with the balance now.

Here's the process when an Add Funds invoice is paid (by PayPal for example)...

Payment notification from PayPal is recorded in client_balance as a plus amount.
Cron run and adds same amount to client_balance as plus amount credit for use against unpaid invoices.
A debit record (negative amount) is added to client_balance to record that the "Add Funds" invoice was paid.

Using an "Add Funds" invoice to get funds into an account is a hokey way of doing things (and somewhat confusing to end user) but at least it works now.
The use of an Add Funds invoice is to get a positive client balance.  When the cron see that happen, and there are outstanding invoices that can be covered by that balance, then they are marked as paid, the balance is reduced, and a transaction record is created so you can see what was used to pay the invoice.

I understand how it works :) It's definitely a 'messy' way of doing it, but it does indeed work.
The only problem now is that new balance invoices get marked as paid after a cron job if you have enough funds in your balance to cover the invoice. Do you understand what I mean by this?

Hopefully my explanation will clear things up.  The whole purpose of the Add Funds option is to build up a credit balance in the user's account.  This allows a user to make payments toward an outstanding invoice (A) that has a large amount due.  Once the client adds enough funds to his account, the outstanding invoice (A) gets paid.  Unfortunately, if invoices (B) are created in the mean time that have due amounts less than the client balance, then those invoices (B) are automatically paid by the cron job.  I can see where this could get messy.  If invoice B gets paid by the client balance, and if it was set up as a PayPal subscription, those funds would still come in from PayPal and be applied to the client balance.  In this case, it works out in the end.

@epichosts Will you check something on your end for me please?  For your orders that have PayPal subscriptions, does the PayPal IPN return the same invoice number each time a subscription payment is made?  If that's the case, I'll need to make a change to the ServiceInvoiceItem page.

@KY4U Hello, please tell me, is it possible to solve somehow the problem about which @epichosts write:

The only problem now is that new balance invoices get marked as paid after a cron job if you have enough funds in your balance to cover the invoice.

?

@KO-N  Please review and test the changes made to src/bb-modules/Invoice/ServiceInvoiceItem.php in my forked repository.
Basically a debit entry is added to the client_balance table (for the recently paid Add Funds invoice).  That entry marks the Add Funds invoice with negative amount to cancel out the credit on that invoice.  What remains is the actual payment credit, which is now available in the client balance.
For example, if user adds funds of $33.00.  An invoice is created for this amount.  The user pays the invoice and the payment $33.00 is logged in the client_balance table.  In addition, a credit in the amount of $33.00 is added to the client_balance for 'Credit applied to client balance'.  That is followed by the debit amount (against the Add Funds invoice) of -$33.00 as '(Debit) Add funds to account'.
The end results is that the Add Funds invoice is marked as paid and a credit (in the amount of the Add Funds invoice) is applied to the client balance.


Update issue templates

Codecov Report

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

@@          Coverage Diff          @@
##           master     #7   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          48     48
  Branches       13     13
=====================================
  Hits           48     48

Continue to review full report at Codecov.

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


Implemented sonar fixes

Short description outlining key changes/additions
Implemented sonar fixes
JIRA Ticket Number
IDVA6-1555
Type of change

[x] Bug fix
[ ] New feature
[ ] Breaking change
[ ] Infrastructure change

Pull request checklist

[x] I have added unit tests for new code that I have added
[x] I have added/updated functional tests where appropriate
[x] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: Security warnings found!


data upsert bulk async/timeout can't be resumed with --use-most-recent

Expected result
If sf data upsert bulk ran async/timed out I should be able to resume the operation by running sf data upsert resume --use-most-recent but that doesn't work, looks like the cache file even doesn't get created.
Actual result
sf data upsert resume --use-most-recent fails because there's no cached info from the last upsert operation:
➜  plugin-data git:(cd/data-import-bulk) rm ~/.sf/bulk-data-upsert-cache.json
➜  plugin-data git:(cd/data-import-bulk) sf data upsert bulk --file test/test-files/data-project/data/bulkUpsertLarge.csv --external-id Id --sobject account --async
Running bulk upsert request... ⣯ Remaining time: -0 minutes. |  Stage: Open |  Processed 0 | Success 0 | Fail 0
Running bulk upsert request... ⣷ Remaining time: -0 minutes. |  Stage: Open |  Proc
Running bulk upsert request... ⣾ Remaining time: -0 minutes. |  Stage: Open |  Proc
Running bulk upsert request... ⣽ Remaining time: -0 minutes. |  Stage: Open |  Proc
Running bulk upsert request... ⣻ Remaining time: -0 minutes. |  Stage: Open |  Proc
Running bulk upsert request... ⢿ Remaining time: -0 minutes. |  Stage: Open |  Proc
Running bulk upsert request... ⡿ Remaining time: -0 minutes. |  Stage: Open |  Proc
Running bulk upsert request... ⣟ Remaining time: -0 minutes. |  Stage: Open |  Proc
Running bulk upsert request... ⣯ Remaining time: -0 minutes. |  Stage: Open |  Proc

Job 7507i00000833slAAA | Status In Progress | Records processed 0 | Records failed
0
Run the command "sf data upsert resume -i 7507i00000833slAAA -o<EMAIL_ADDRESS>to check the status.
Running bulk upsert request... done
%
➜  plugin-data git:(cd/data-import-bulk) sf data upsert resume --use-most-recent
Error (MissingCacheEntryError): Could not load a most recent cache entry for a bulk request. Please rerun your command with a bulk request id.

➜  plugin-data git:(cd/data-import-bulk) ll ~/.sf/bulk-data-upsert-cache.json
ls: /Users/cdominguez/.sf/bulk-data-upsert-cache.json: No such file or directory

Additional information
sf data upsert resume -i 7507i00000833slAAA  works, looking at the code it seems the cache resolver crafts an object with the ID and so it can be resumed, all without a cache file.
System Information
CLI:
@salesforce/cli/2.62.6 darwin-x64 node-v20.18.0

Plugin Version:
@cristiand391/oclif-carapace-spec-plugin 0.1.0 (user)
@cristiand391/sf-plugin-fzf-cmp 0.2.0 (user)
@oclif/plugin-autocomplete 3.2.5 (core)
@oclif/plugin-commands 4.1.3 (core)
@oclif/plugin-help 6.2.14 (core)
@oclif/plugin-not-found 3.2.22 (core)
@oclif/plugin-plugins 5.4.14 (core)
@oclif/plugin-search 1.2.11 (core)
@oclif/plugin-update 4.6.3 (core)
@oclif/plugin-version 2.2.14 (core)
@oclif/plugin-warn-if-update-available 3.1.18 (core)
@oclif/plugin-which 3.2.15 (core)
@salesforce/cli 2.62.6 (core)
apex 3.5.1 (core)
api 1.3.1 (core)
auth 3.6.65 (core)
data 3.7.0 (core)
deploy-retrieve 3.12.17 (core)
dev 2.4.2 (user)
info 3.4.9 (core)
limits 3.3.32 (core)
marketplace 1.2.26 (core)
org 4.6.0 (core)
packaging 2.8.11 (core)
schema 3.3.34 (core)
settings 2.3.23 (core)
sobject 1.4.41 (core)
source 3.5.21 (core)
telemetry 3.6.15 (core)
templates 56.3.22 (core)
trust 3.7.33 (core)
user 3.5.32 (core)

SF ENV. VARS.
SF_DISABLE_TELEMETRY,true
SF_AUTOUPDATE_DISABLE,true
SF_DISABLE_AUTOUPDATE,true
SF_UPDATE_INSTRUCTIONS,Use "npm update --global @salesforce/cli" to update npm-based installations.

Windows: false
Shell: zsh
Channel: stable

Diagnostics
:white_check_mark: pass - salesforcedx plugin isn’t installed
:white_check_mark: pass - you don't have any linked plugins
:white_check_mark: pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org
:white_check_mark: pass - [@salesforce/plugin-trust] can ping: https://registry.yarnpkg.com
:white_check_mark: pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org/
:white_check_mark: pass - using latest or latest-rc CLI version
:x: warn - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches apiVersion
:white_check_mark: pass - [@salesforce/plugin-deploy-retrieve] default target DevHub max apiVersion matches default target org max apiVersion
:white_check_mark: pass - can access: https://test.salesforce.com
:white_check_mark: pass - can access: https://appexchange.salesforce.com/services/data
:white_check_mark: pass - can access: https://developer.salesforce.com/media/salesforce-cli/sf/channels/stable/sf-win32-x64-buildmanifest
:white_check_mark: pass - [@salesforce/plugin-auth] CLI supports v2 crypto

this was fixed in the PR linked above, can't repro on sf v2.69.14


Remove redundant pytest requirement and sort requirements file

Hi! I'm getting an error when trying to build the docker image (or install the requirements for that matter):
$ pip3 install -r requirements.txt
Double requirement given: pytest (from -r requirements.txt (line 20)) (already in pytest>=3.6.0 (from -r requirements.txt (line 9)), name='pytest')

pytest is declared twice in requirements.txt, this PR fixes it and sorts the requirements file so that this kind of errors is less likely to happen again.
BTW, this could be caught by building the docker image on CI, I can prepare a quick PR for that let me know WDYT.
Thanks,

Thanks @fgimenez! AFAIK the docker image is already being built on CI. Not sure why this wasn't caught earlier.


chore: qs-jx-v3 to 0.0.12

chore: Promote qs-jx-v3 to version 0.0.12

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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

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

Test name
Commit
Details
Rerun command

promotion-build
b314215ad7834fd6d416fc1595476b0e40e27414
link
/test this

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


on windows platform preview freezes

Hello.
I faced the following issue on windows8.1 -

you open barcodescanner,
switch to another app
switch back to your app with barcodescanner opened

Error: preview is frozen. Though you can click on cancel button
Expected result: preview is not frozen.
Problem is that I am not very familiar with WinJS, so I don`t know how to fix this issue by myself.
So please either fix it or tell me how to do that and I will create a pull request.
Thanks,
VLad

Probably this is related to application's lifetime events. For more details see MSDN article, section "Handle app lifetime and page navigation events".
In terms of Cordova it appears that you'll need to subscribe to document's pause and resume events - shutdown scanner's preview on pause event and restore it on resume.


chore: Replace hashers of hashmaps in dfg with fxhashes

Description

Problem*

Resolves https://github.com/noir-lang/noir/issues/2487
Summary*
very small speedup https://github.com/noir-lang/noir/issues/2487#issuecomment-1699464142

Additional Context

PR Checklist*

[X] I have tested the changes locally.
[X] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Might as well replace HashMaps all throughout SSA I suppose

bit shift test failing after changing the hasher

bit_shifts_comptime is failing on master as well. CI only tests on release mode and it is only failing in debug so it wasn't caught before


Does not connect with defaults

After setup with all defaults (pressing enter for all questions), ping or traceroute to google.com  just times out.  This happens with other options selected, like selecting a specific country server, disabling IPv6, with or without PIA dns.
I want to connect to a specific country server, no IPv6, no port forwarding, Wireguard and PIA dns. After several tries and a couple of reinstalls, I decided to try the defaults with no success.
Using Ubuntu Server 20.04 with latest updates.

Thank you for the report. We will test it out to see if we an reproduce the behavior.

@compinche please git pull and try again.

It is now working for the defaults and my use case. Thank you!


(PUP-7616) Fix acceptance tests for the zone provider

@Magisus, you work fast! Sorry about the mistake.


Lookups fail for autofield when the base id is zero

In hashid_field/hashid.py I think it should read like:
        value = self.decode(id)
        # NB value could be zero
        if value is not None:
            self._id = value
            self._hashid = id

else if value=0 like it would be for an AutoField starting from zero, then decode appears to fail and it leads to valueerror even though the decode actually returned a non-null value

Thanks! I added a test and merged your PR. Fixed in version 2.1.5.


Update Update.php

Wondering if it would cause issues if $this->syncPivot() gets called just before $item->update?
Background: I'm using Algolia Search and their Laravel integration. If this is used with n:n relations, the updated attributes on a relation are ignored (or outdated) as they are refer to the current Model attributes (in $this) which has not yet "received" the updated attributes.
https://www.algolia.com/doc/api-client/laravel/relationships#relationships

Yup, works like a charm, thank you! Sorry to be so late to merge it.
Cheers, keep 'em coming!


*bsdCross: Remove these package sets

Description of changes
I realized what @rhelmot did in 61202561d92cf1cd74532fcbd8b9d6662c5bc57b (specify what packages just need stdenvNoLibc) is definitely the right approach for this, and adjusted NetBSD and OpenBSD to likewise use it. With that change, we don't need these confusing and ugly *bsdCross package sets at all!
We can get rid of a lot more libc-related *Cross, and I will do so soon, but this is the first step.
(adapted from commit 51f1ecaa59a3b7c182b24e71a3176c83d6cd601e)
Part of take 2 of https://github.com/NixOS/nixpkgs/pull/320852, without the infra changes. This, unlike the other, is safer to backport.
(They are still kept as deprecated aliases.)
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

No more stdenv rebuild, and for what it's worth, most of the darwin changes are actually things that are marked unsupported on darwin.


Don't overwrite existing trailing comma for elements in Result Builders

@swift-ci Please test

@ahoppen @kimdv could you please merge? I don't have permissions to merge myself


Deno Astro Adapter appears to fail with Astro 5.0

I haven't looked into the details yet, but trying to upate my website with Deno and the Deno Astro Adaper to Astro 5.0 is leading to errors. Adding the --verbose flag to the Astro build shows this:
  astro:Failed to load config with Node TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for /Users/irbull/git/toro/node_modules/.deno/@deno+astro-adapter<EMAIL_ADDRESS>  astro:Failed to load config with Node     at Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:218:9)
  astro:Failed to load config with Node     at defaultGetFormat (node:internal/modules/esm/get_format:244:36)
  astro:Failed to load config with Node     at defaultLoad (node:internal/modules/esm/load:122:22)
  astro:Failed to load config with Node     at async ModuleLoader.load (node:internal/modules/esm/loader:570:7)
  astro:Failed to load config with Node     at async ModuleLoader.moduleProvider (node:internal/modules/esm/loader:443:45) +0ms

I think that's coming from the vite compiler and it's not liking the explicit extensions we use.
I'll try and get a reproducible example (small) example that we can work from.

Turns out this was a breaking change in Astro wrt output: hybrid. This error wasn't related. Following the migration guide, and things are working fine with Astro 5.0, Deno Deploy, Deno and the Deno-Astro-Adapter.


review the reading project

the "lets get students to fill in promise" project is specified in https://github.com/txt/mase/blob/master/READING.md
feedback please. still amazed you are willing to do this. the collegiality at this uni.., amazing
fyi, if you want, i could come into your class to brief your students on this
the project has 2 parts

part2 is a big essay
part1 has a seed paper then students work backwards exploring reading one prior paper per week for 8 weeks
the actual "lets add data to promise" exercise is at the end of that sequence. so we dont ask them to do real work that effects promise until after we've trained them in paper reading
for your subject, you could

not do part2
don't walk over 8 papers, but over 4

Update: a missing bit of the current spec is a glossary: the top dozen terms that seem to be key themes in the papers being reviewed.

[ ] should add
[ ] also, for the ASE students (and not emerson's SE students) i would add that that glossary is the seed that grows into the lit reviews

Also, need to add these notes from Swales (which is a standard text). So the spec should start saying thee things experts know that allow them to read papers faster

context (prior and subsequent papers)
parts (tim & emeron's 6 + 5)
terms (glossary, background knowledge on the words)
goals (the swale 3)

Swales’ Three-Move Model for Introductions
With Revisions and Adaptation for Classroom Use by James Luberda
The following is based upon an empirically-derived model of how “real-world” research article introductions commonly proceed. Note that it is not a set of rules, but rather something of a guide as to what readers of research articles and academic essays are likely to expect (and find), a set of patterns in introductions that facilitate their reading and comprehension. You might think of each “move” below as a kind of verbal action—a “move” a writer will make to have a particular effect on the reader. By constructing an introduction more or less along these lines, you ensure your reader has enough information to follow your essay and make use of the information it contains.
Move 1    Establishing a territory

In this opening move, the writer may do one or more of the following to broadly sketch out where the subject of his/her essay falls—the “big picture”
+ Point out the importance of the general subject
+ Make generalizations about the subject
+ Review items of previous research

Move 2    Establishing a niche

In this move, the writer then indicates to the reader the particular area of the broader subject that the essay will deal with. This can be done using one or more of the following:
+   Make a counter-claim, i.e. assert something contrary to expectations
+ Indicate a gap in the existing research/thinking
+  Raise a question about existing research/thinking
+  Suggest the essay is continuing a tradition, i.e. it is following in the footsteps of previous research/thinking

Move 3    Occupying the niche

In this move, the writer then sketches out exactly what this particular essay will accomplish in relation to move2, and gives the reader a sense of how the essay will proceed. In general, each of the steps below will appear in this move, in order:

Step 1: Outline the purpose of the essay, or state the research that was pursued
Step 2: State the principal findings of the essay—what the reader can expect the essay/research will have accomplished for them by the time they get to the end
Step 3: Indicate, roughly, the structure of the essay—what will appear in it and in what order

Some issues/questions with the current document:

I don't see the PROMISE part at the end
It looks like it's dual use for both 510 and your course. Can you make a branch just for 510? In it, you can condense it to a 1 or 2 week project, with 4 papers, etc.
Do you own the copyright to the images?

A suggestion for how to read papers

Managed to make it all one page.
The se stuff is now the "Fast path" assignment specified at top of page.
And I found some good stuff from PSU
Over to you. Need any more structuring?
t

Looks good. I think it's doable. Tentatively, I'll have you come in on 8/25 at 8:05AM to talk to my students about it.

er.... actually, i'm going pass on the 8am visit. happy to leave the experiment to you... which is appropriate since i need to know if you have troubles before i ship to finland and montreal

mei:
3471632a52a90a644e0549f6d5f624d82207dc8f

@CaptainEmerson
fyi- video on the reading assignment: https://vimeo.com/136412506


Dependency updates

This update is only for high risk dependency updates that do not cause any breaking changes  - part of a longer term project to bring all dependencies up to their most recent versions

 Update vulnerable packages in react-ions and ambassador-app

Closing this PR as another one was created that involved less config changes


Changed from keystrokes to a virtual controller and added whammy and tilt support

For more details, you can checkout the descriptions in the first 2 commits. With this, there should be enough functionality for the general public to use without needing modification of the script.

Awesome work! Been pretty busy lately, will try to take a look soon.

turns out most of this is useless bcuz clone hero and linux both have native support for wiimotes, but using thisis better bcuz of whammy and tilt. whammy is more responsive using this, and afaik tilt just doesnt work.


Add support for default section when creating a list

Summary
We should add the support for a default section, when creating a list. This is useful when the list we're creating doesn't need multiple section.
Proposed behaviour
When creating a list, we could have a section called "default", and in this default section, we would be able to add elements.

Fixed in 1.6.0


Add an endpoint for converting texture url to isometric cube

When base64 decoding a skull's texture string, you get out a texture url, which looks like this:
http://textures.minecraft.net/texture/9336d7cc95cbf6689f5e8c954294ec8d1efc494a4031325bb427bc81d56a484d
Would you be able to add an endpoint which takes the data after texture and returns an isometric cube, exactly like
https://crafatar.com/renders/head/uuid does? Just instead of uuid, it takes the texture's id of
9336d7cc95cbf6689f5e8c954294ec8d1efc494a4031325bb427bc81d56a484d

#54


Cdpt 18 fum q4 onwards add a hyperlink within the csv download

Last column in each row added link to account details.

Be careful copying from JIRA as you may add details that are irrelevant to the PR like fum q4 onwards


Styles no longer work from Google maps output

Not sure about other sources but Google maps at least has added the  tag, which has the id that the data nodes map to, instead of the

@p-somers submitted a pull request to fix this in #73.

Closing; no test case was found and no standard exists.


feat: Sync from noir

Automated pull of development from the noir programming language, a dependency of Aztec.
BEGIN_COMMIT_OVERRIDE
feat: Sync from aztec-packages (https://github.com/noir-lang/noir/pull/5971)
feat: LSP completion function detail (https://github.com/noir-lang/noir/pull/5993)
feat: add TypedExpr::get_type (https://github.com/noir-lang/noir/pull/5992)
feat: better error message for misplaced doc comments (https://github.com/noir-lang/noir/pull/5990)
fix: Error when comptime types are used in runtime code (https://github.com/noir-lang/noir/pull/5987)
END_COMMIT_OVERRIDE

Benchmark results
Metrics with a significant change:

proof_construction_time_poseidon_hash_ms (4): 48.0 (+41%)
protocol_circuit_simulation_time_in_ms (private-kernel-tail-to-public): 1,238 (+56%)
public_db_access_time_ms (get-nullifier-index): 0.263 (+57%)
avm_simulation_time_ms (FeeJuice:_increase_public_balance): 166 (+248%)
avm_simulation_time_ms (Token:assert_minter_and_mint): 55.5 (-84%)
node_history_sync_time_in_ms (3): 3,343 (-16%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Proof generation
Each column represents the number of threads used in proof generation.

Metric
1 threads
4 threads
16 threads
32 threads
64 threads

proof_construction_time_sha256_ms
5,757
1,549
704 (-1%)
781 (+3%)
776

proof_construction_time_sha256_30_ms
11,883
3,147
1,392 (-1%)
1,436
1,478

proof_construction_time_sha256_100_ms
44,011
11,793
5,361 (-2%)
5,700 (-3%)
5,426 (+1%)

proof_construction_time_poseidon_hash_ms
78.0
:warning: 48.0 (+41%)
34.0
58.0 (+2%)
88.0 (-1%)

proof_construction_time_poseidon_hash_30_ms
1,538 (+1%)
420
200 (-1%)
225 (-2%)
275 (+3%)

proof_construction_time_poseidon_hash_100_ms
5,659
1,514
668 (-2%)
723 (+1%)
750 (+1%)

L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
4 txs
8 txs
16 txs

l1_rollup_calldata_size_in_bytes
4,420
7,940
14,948

l1_rollup_calldata_gas
50,512
93,272
178,556

l1_rollup_execution_gas
843,645
1,577,301
3,362,642

l2_block_processing_time_in_ms
251 (-1%)
444 (-7%)
813 (+3%)

l2_block_building_time_in_ms
11,403
22,587 (+1%)
44,706 (-1%)

l2_block_rollup_simulation_time_in_ms
11,403
22,587 (+1%)
44,706 (-1%)

l2_block_public_tx_process_time_in_ms
9,738
20,875 (+1%)
42,971 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 8 txs.

Metric
3 blocks
5 blocks

node_history_sync_time_in_ms
:warning: 3,343 (-16%)
4,218 (+2%)

node_database_size_in_bytes
14,221,552
18,227,440

pxe_database_size_in_bytes
16,258
26,818

Circuits stats
Stats on running time and I/O sizes collected for every kernel circuit run across all benchmarks.

Circuit
simulation_time_in_ms
witness_generation_time_in_ms
input_size_in_bytes
output_size_in_bytes
proving_time_in_ms

private-kernel-init
74.5 (+5%)
414 (+10%)
21,027
44,933
N/A

private-kernel-inner
141 (+2%)
700 (+4%)
71,803
45,067
N/A

private-kernel-reset-tiny
291 (-1%)
689 (+3%)
64,669
44,922
N/A

private-kernel-tail
152 (+1%)
130 (+3%)
50,553
57,178
N/A

base-parity
5.66 (+2%)
N/A
160
96.0
N/A

root-parity
35.7 (+1%)
N/A
73,964
96.0
N/A

base-rollup
2,588 (+1%)
N/A
189,128
664
N/A

block-root-rollup
41.4 (+1%)
N/A
58,217
2,448
N/A

public-kernel-setup
85.9 (+3%)
N/A
114,433
79,670
N/A

public-kernel-app-logic
98.3 (+1%)
N/A
114,251
79,670
N/A

public-kernel-tail
846 (+1%)
N/A
487,098
16,414
N/A

private-kernel-reset-small
269 (+1%)
N/A
66,345
45,629
N/A

private-kernel-tail-to-public
:warning: 1,238 (+56%)
616 (+5%)
449,631
1,825
N/A

public-kernel-teardown
84.7 (+2%)
N/A
114,697
79,670
N/A

merge-rollup
20.1
N/A
38,182
664
N/A

undefined
N/A
N/A
N/A
N/A
98,951 (-6%)

Stats on running time collected for app circuits

Function
input_size_in_bytes
output_size_in_bytes
witness_generation_time_in_ms

ContractClassRegisterer:register
1,344
11,731
343 (+2%)

ContractInstanceDeployer:deploy
1,408
11,731
18.3 (+2%)

MultiCallEntrypoint:entrypoint
1,920
11,731
421 (+1%)

FeeJuice:deploy
1,376
11,731
390 (+2%)

SchnorrAccount:constructor
1,312
11,731
61.1 (+1%)

SchnorrAccount:entrypoint
2,336
11,731
372 (+2%)

FeeJuice:claim
1,344
11,731
38.5 (+12%)

Token:privately_mint_private_note
1,280
11,731
74.3 (+14%)

FPC:fee_entrypoint_public
1,344
11,731
26.9 (+10%)

Token:transfer
1,312
11,731
213 (+2%)

Benchmarking:create_note
1,344
11,731
74.9 (+2%)

SchnorrAccount:verify_private_authwit
1,280
11,731
26.4

Token:unshield
1,376
11,731
490 (+2%)

FPC:fee_entrypoint_private
1,376
11,731
649 (+2%)

AVM Simulation
Time to simulate various public functions in the AVM.

Function
time_ms
bytecode_size_in_bytes

FeeJuice:_increase_public_balance
:warning: 166 (+248%)
1,322

FeeJuice:set_portal
9.27 (-6%)
1,332

Token:constructor
267 (+2%)
13,702

FPC:constructor
77.6 (-1%)
10,797

FeeJuice:check_balance
36.3 (+2%)
1,153

Token:mint_public
315 (+2%)
2,487

Token:assert_minter_and_mint
:warning: 55.5 (-84%)
1,687

AuthRegistry:set_authorized
45.9 (+1%)
531

FPC:prepare_fee
95.0 (-9%)
1,822

Token:transfer_public
27.5 (+26%)
11,517

FPC:pay_refund
46.4 (-7%)
2,314

Benchmarking:increment_balance
1,225
1,573

Token:_increase_public_balance
37.6 (+3%)
1,299

FPC:pay_refund_with_shielded_rebate
50.5 (+4%)
2,314

Public DB Access
Time to access various public DBs.

Function
time_ms

get-nullifier-index
:warning: 0.263 (+57%)

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
256 leaves
512 leaves
1024 leaves

batch_insert_into_append_only_tree_16_depth_ms
2.15 (-2%)
3.90 (+2%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.7
31.8
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.113
0.110 (+2%)
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
11.4 (+2%)
17.7 (+1%)
30.8 (+1%)
60.2 (+3%)
113 (-1%)

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
95.9
159
287
543
1,055

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.109 (+3%)
0.102 (+1%)
0.100 (+1%)
0.103 (+2%)
0.101 (-1%)

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
14.4 (+2%)
25.9 (+1%)
44.2
82.9 (+2%)
161 (-2%)

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
109
207
357
691
1,363

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.109 (+2%)
0.105 (+2%)
0.107 (+1%)
0.103 (+2%)
0.103

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
16.2 (+1%)
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
129
N/A
N/A
N/A
N/A

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
0.107 (+1%)
N/A
N/A
N/A
N/A

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
72,417
668,302

Transaction size based on fee payment method
| Metric |  |
| - |  |


Move website over to gohugo

Adding and managing content on the website is a mess. Move to a tool that lets me template and manage everything easily and programmatically.

done.


ENH: improve precision of median calculation by default

Increasing the default number of bins from 20 to 256 significantly improves
the precision of median calculation. Histogram itself is off by default.
See discussion:
https://discourse.itk.org/t/connected-component-image-filter-example/1390/

@blowekamp While splitting the commit, I realized that assumption there is always at least one pixel has to be fulfilled. So no functional changes there are needed. Thanks!


Updated max message size of premium tier

I think there is a typo in the maximum message size for premium tier. It stated 100 MB but should be 1 MB.

#label:"aq-pr-triaged"

#please-close

That is good news. When i was looking into the quotas there was a mismatch in the size for premium on different pages. We actually need more then 1MB file size so this update is perfect :)


Why does NTR require a proprietary blob to run?

BootNTR's cia is entirely free and open for anyone to modify or use yet the actual binary it reads off is a blob which cannot be changed, why not free up the blob or open up the software? I would love to try using this but I wont start unless it's fully free'd up or open.
Not to mention the debugger and video stream is also closed up and is exclusive to the Windows OS, what about people on GNU (Linux) ?

Please stop opening issues like this, I am tired to close them.
The Issue Tracker on Github is generally tracking bugs or new features for developers, I think it is probably not a place for arguing your opinions.

I'm not a huge fan of closed source myself but for example if it would be open source we had online cheaters long before Brickway all over the place. NTR CFW disables WiFi intentional so you can only cheat offline.
Besides that it is the authors decision to make it open source or not but this is just my 2 cents. Not gonna comment further because this is really not the place to argue.

@profi200 Because there aren't already cheaters online?

There is only Brickway users right now.  Otherwise there is only NTR CFW which disables online if you use per game plugins and i think that was the right decision to do.
Unless there is an alternative to it which can change memory of every process while online i think it is still a valid reason to keep it closed source for exactly this. And then it is still the decision of the author if he wants to make it open source. If he uses no GPL'd source or libs in any form there is no way to force it.

@profi200  Except online cheating does work with NTR, there was literally a thread about MK7 where the guy made Speed codes up to 1000CC  and they were used online they shortly got taken down by OP.
Its not the case the cheats dont work online its more of the case people dont make them or still believe they dont or the fact its so minimal so one notices.


Canvas paste image error

Hi,
When plugin is turned on, then I cant paste an image from buffer into canvas.
But when plugin is turned off, then an image form buffer could be pasted.
What should I do?

I will look into it in the next days. I did not test canvas since I don't use them myself. Once fixed, I will write back to you.

I have implemented a fix that allows you for the moment to work with canvas and the plugin for importing files. More support will be implemented in the future, but you should already be able to resume your workflow.
I close this issue because a similar one was recently opened under this link. You are welcome to post there your comments.


Added: SystemUIcons, Iconoir, Material design icons

Hi. PLease read the contribution guidelines. Thanks!


MEM #1: Linear Decoder Functions

Using the equation for functional decoders and L2 regression, calculate the ideal functional decoders mapping spikes to acceleration (or velocity) in x and y (accounting for a small amount of noise). Verify that these decoders provide a (more or less) reasonable estimate.
Example Functional Decoder Calculation (Note: we use the normally distributed noise to regularize the decoders and make them more resilient to the impacts of noise but it could be omitted):
# n:= number of neurons, N:= number of sample points, A := nxN activity matrix, Y := dxN ideal output matrix
# @ := numpy matrix multiplication operator
D = np.linalg.lstsq(A @ A.T, A @ Y.T, rcond=None)[0].T
D_reg = np.linalg.lstsq(A @ A.T + A.shape[1] * np.square(np.random.normal(0,20,1)) * np.eye(n), A @ Y.T, rcond=None)[0].T
Y_hat = D @ A
Y_hat_reg = D_reg @ A

For MM_S1, I was able to calculate RMSE values for functional decoders and L2 regression.
For Functional Decoders:
X Velocity RMSE: 6.416302933793741
Y Velocity RMSE: 6.355657912855544
X Acceleration RMSE: 43.82823510693504
Y Acceleration RMSE: 50.83319516862542
For L2 Regression:
X Velocity RMSE: 6.599472849958744
Y Velocity RMSE: 6.565052549502841
X Acceleration RMSE: 44.399326077287
Y Acceleration RMSE: 51.2782400205911
Source code can be found here: https://github.com/WAT-ai/BCI-Signal-Decoding/tree/LeftBrainIssue1/src/LinearDecoderFunctions

Thanks for all the analysis!
Notes from last meeting relevant to this:

Normalization of velocity/accel (accounting for outliers -- Thomas' distributions)

a = a / np.max(np.abs(a)) # Where a is x,y accel or velocities concatenated

Functional and Regularized Functional, both are L2 but RF accounts for some intrinsic noise

Adjust noise factor to be more reflective of values (10% of expected max, maybe 0.4?)

Test generalizability (Train/Test 60/40 split of data)
Consider looking at Raw TimeSeries data (see NengoSpikesEx.ipynb in the repo)


Change all views.py strings to unicode

I've been getting an error in line 48 when it calls the logger because
of files uploaded having accented letters.
I modified all string to be unicode just in case.

Thank you, but this patch is redundant. The file has a "# -- coding: utf-8 --" comment in the first line which means that every string is already in utf-8.


fix: Remove dangling table references in unparser

Which issue does this PR close?

Closes #13027
Rationale for this change

This change ensures that table references which don't exist at their current level are removed. For example, SELECT ta.j1_id FROM (SELECT j1_id FROM j1 ta) is invalid because the subquery is un-aliased so ta is not a valid reference at the top-level projection.
This is usually caused by derived subqueries, both un-aliased and aliased.
What changes are included in this PR?

For each select_to_sql_expr, collects the available table identifiers at that level from the projection and table joins.
Iterates over the projection and order by and compares them to the list of collected identifiers. For identifiers that are not found, strips their table reference leaving just the bare column (e.g. ta.j1_id -> j1_id).

Are these changes tested?

Yes. A collection of new plan-to-SQL roundtrip tests to validate the changes.
Are there any user-facing changes?

No

Maybe @sgrebnov or @phillipleblanc  can offer some advice about how to proceed with this PR -- I feel like it adds significantly complexity and I am not sure it doesn't also introduce some hard to understand subtle bugs with indentifiers

Maybe @sgrebnov or @phillipleblanc can offer some advice about how to proceed with this PR -- I feel like it adds significantly complexity and I am not sure it doesn't also introduce some hard to understand subtle bugs with indentifiers

I plan to take a shot at preventing the identifiers from getting introduced in the first place and/or adding subquery alias nodes as appropriate. I spent a little time on it this weekend and was able to get the bare aggregation + table scan working.
@peasee let's close this PR for now.


Add Sanctuary Watch Theme Details

So, if we look at the current "Theme Details" for Sanctuary Watch in the WordPress Appearance screen, it looks a little bare:

Compare this to the Theme Details for the WordPress theme Twenty Twenty Four:

Let's go ahead and add an image as well as some additional text for the Theme Details for Sanctuary Watch:

[x] Adding an image. Let's use a screenshot from the existing Sanctuary Watch site - maybe a modal window over a scene? To add this image, here are instructions.

[x] Adding text. To add text to the Theme Details, that all gets added to the header section of the style.css file. as follows.

added screenshot.png for image, modified style.css for other text details


Writing Character Tags

Hi @ags131
Thanks for adding the character code. Just wanted to double check my findings. You can't write a character to a vehicle tag or overwrite a character tag can you? I can't manage to do either using just the lego dimensions portal.
I'm guessing I need an RFID writer. Is it a simple case of turning the byte in page 0x27 into 00 instead of 1 for a character? (my character starts at page 0x25)

If I'm not mistaken 0x27 is actually locked readonly, characters also have more locked pages, it wouldn't surprise me if those are 0x25 & 0x26, I haven't looked at the lock bits lately so don't remember the exact ones. Vehicles however, can be overwritten very easily with other vehicles. 0x24 & 0x26 is upgrade data with 0x25 being vehicle ID (See the vehicle json file for a list of most of the IDs)

I thought so. I couldn't get a character tag to work on a a vehicle tag. I'm going to try and create one on a blank NTAG2013 tomorrow as I've not got my reader currently. I'll update when I've tried it.
I managed to get the vehicles updating easily. Thanks again for all the hard work.

Looking at dumps, the static lock bytes for both characters and vehicles are 1F 00 (BL CC, 9-4, 15-10 & L CC, 4). However, the dynamic lock bytes for vehicles are 60 08 3F, while characters have 60 0C 3F, which additionally locks pages 36 & 37, that contain character data. Both tags lock pages 38 & 39, so you can't change the tag type byte.
I don't fully understand dynamic lock bits on these tags to know if the lock is permanent.

You can only write dynamic lock bits, any further writes are 'or'ed with the existing value.

Would cloning an existing character disc onto an NTAG213 then updating the neccrssary pages work? Or would cloning clone the locked bytes? I'm fairly new to NFC so I'm not sure if cloning just clones the data or the protection also.

You should be fine as long as you only write the data pages. You will have to set the PWD calculated from the new UID using something other than the portal (Such as an android phone). the Character ID would need encrypted with the new key derived from UID

That's what I was thinking, shouldn't be too difficult.
Would you use something other than the portal to clone an existing character disc onto an NTAG213 then update the PWD and encrypted pages  0x25 & 0x26 using the new UID. That should be all that's needed?
Or, could I just write pages 0x25 & 0x26 data onto a blank disc after I have set the PWD and used the UID to encrypt the data for 0x25 and 0x26.
Just trying to work out what the bare minimum for a character required is.

I think you have to set the PWD first, but yes, 0x25 and 0x26 is all thats needed on a character (With 0x27 being 0)
The portal isn't able to set the PWD, so that has to be done seperately, but after that point the portal would be easiest to use since you can abuse the existing functions for the encryption ;)

Brilliant. Thanks for the info. I've got some NTAG213 arriving tomorrow so I'll give it a go. Brilliant work on the PWD and encryption.

Technically, the game only ever sees the UID in the placement events. The game ignores UID
When a token is placed it does the following:
0. Portal calculates PWD and auths token

Game reads 0x24 (Returns 4 pages so 0x24,0x25,0x26,0x27)
if(0x27 == 0) process character otherwise its vehicle (0x24,0x25,0x26 are IGNORED on characters)
3a. if character do D4 to get ID
portal decrypts token using UID key, then encrypts using static TEA key
3b. if vehicle 0x25 == ID and 0x24,0x26 are upgrades (uint64) (No encryption)

Those 4 pages are the only important ones on the tag, the rest are ignored for gameplay

That makes sense. Only thing I'm not sure on is D4 - is that a memory address?
So far I've seen the encrypted ID + uID on pages 0x25 and 0x26.

0xD4 is part of the USB protocol, its the command ID
The game sends a D4 packet containing a nfc index to read, the portal decrypts the character data on that tag, reencrypts it with the static key, and sends it back to the game.

Before we knew the decryption for the tags, I spoofed the data by encrypting my own ID and sending it to the game, thats why D4 in ToyPadEmu is so wonky

I'm with you now. Does it use TEA also to encrypt the data on the tag, with a key comprised using the UID?
Much easier to spoof the data to the game using the static key :)

Yes, its a key derived from the UID used with TEA on the tag. see CharCrypto for how that key is actually generated and how the data is stored. (charid is saved twice into a 8 byte chunk then encrypted ex: [01 00 00 00 01 00 00 00])

Thanks @ags131. The genKey function must be the function that runs on the toypads hardware. I've learnt so much from this conversation.

Any recommendations for software? struggling to find anything to write the PWD and PACK pages. I found one but I don't trust it as it's returning bytes different to what the toypad is saying on pages 24,25 and 26. Any operating system (inc android) is fine :)

I have used this app with other tags, haven't tried with ld since PWD gen
was discovered, but should work fine.
https://play.google.com/store/apps/details?id=com.wakdev.nfctools.pro
On Wed, Jan 27, 2016, 17:04 withgallantry<EMAIL_ADDRESS>wrote:

Any recommendations for software? struggling to find anything to write the
PWD and PACK pages. I found one but I don't trust it as it's returning
bytes different to what the toypad is saying on pages 24,25 and 26. Any
operating system (inc android) is fine :)
—
Reply to this email directly or view it on GitHub
https://github.com/ags131/node-ld/issues/3#issuecomment-175903913.

Thanks. I gave that a go and it worked. I've also finally found a way to use the acs acr122u from my mac to write the tags now without using the toypad.

Got NFC Tools pro app and can't see pages. Only a basic text string is visable. Wondering how to use it for vehicle id swapping.

Has anyone actually successfully written characters they don't have onto a vehicle tag or new blank tag and can they tell me how to do it? I have no experience with all this NFC stuff, but I downloaded NFC Tools.


When you use touch event the mouse stops working

Hi,
I've upgraded to the latest nightly of ionic and I've noticed an interesting issue on touch-enabled laptops. When the app first loads you can use your mouse to click around etc., but as soon as you use touch to scroll or tap then mouse clicks no longer do anything.
I've replicated the problem in a Plunkr here: http://plnkr.co/edit/fyFolTNeTXfeKg7wZJit?p=preview
Thanks

This should be fixed now: https://github.com/driftyco/ionic/commit/be0943360850ad99a84bfd7bebb8a77b905e6483


Inclusion of  Format/style of resume and option to select background, Direct Upload to social media channels, Upload and take picture,  Magnifier tool and Font size as well as Interview recorder on Resume Builder

Hello!!! i am one the lover of your project and i have been using the app for quite sometimes now and i would love to see some improvement on the project.
I propose the

Ability to select Format and style of resume and option to select background.

Direct Upload to social media channels

Upload and take picture

Magnifier tool and Font size

Interview recorder

Ability to select format/style of the resume and option to select background
This function is also known as appearance whereby users will be able to select the way which the resume will be printed out in terms of designs depending on user's interest and as required by the prospective employer, this will also have a function to select how the furthest/background part of the resume will look like in terms of color.
I believe this can be realised by providing options for users to pick as how they would like the finishing of their resume should look like.
Direct upload to social media channels
After inputting all necessary information and user previewed the resume there is a icon to save the resume into mobile storage memory/SDcard or google-drive so any further procedure has to to be from the device, I am suggesting a smart way of sending resume directly from the app to other social media platform this feature will be on the preview
There will be a icon whereby users will be able to send/upload their organized resume directly to social media platforms directly.
Upload and take picture
There are some advanced resume that requires adding of picture to suit the requirement of the employer's so addition of this feature will be useful for this  reason, There will be upload button and take picture at the Personal Info page of the app so users can decide to use this features if entailed.
Magnifier tools and Font size
These features are needed majorly at the preview page of the resume, magnifier is a lens that is used to make something more larger in appearance in another word to zoom in and out of a page to enable better view for users depending on their visual  capability as the page does not allow pinch to zoom
Font is a type of different sizes of text which can be selected and use, user can easily select font size that they would like to use to save their resume.
Interview recorder
Interview recorder is a feature whereby all submitted or sent resume possibly for job or any other purpose can be tracked, there will be a section within the app where user can input all the necessary information's got from the prospective employer such as Company name, date and time for interview, all necessary document to submit, Location/venue.
Mock ups
Pictorial illustrations of my suggestions

https://cdn.discordapp.com/attachments/413700596785348608/465242958296514584/20180707_204713.gif

Benefits
Pragmatically all the suggested features and sections enhancement will be of added advantage for users of the application.
With the ability to select format/style of resume users will be able to select the type of resume format they want, depending on the design that will suit their purpose, definitely these will make the application to be more advance and more useful.
Upload icon to social media platforms will make the project to be more flexible because it will be very easy to send resume directly to anyone within all installed social media platforms available on the user's device and the recipient can easily download the file on their device and this will perfect a specific extent of good enhancement.
Upload and take picture will also be of a brilliant  feature as user will be able to add picture to their resume if required.
Instead of using another application to add picture RESUME BUILDER will perfect it and their won't be need for searching else where to add picture to resume.
Magnifier tools, Apparently this feature is meant majorly for people with sight issue and the preview page text might be kinda smaller in text, the inclusion of the feature will enable users to zoom in to see all the text properly as the page does not work on pinch to zoom.
As for now the save available is only in PDF and might involve additional application to convert PDF to Ms doc or other editable format,
Font size before saving resume will be of good feature so that the printed copy will have a suitable font size to eradicate all sort of limitation on the printed copy of the resume as user can select font size that will be nice
Interview recorder
This feature has lots of benefits.
Users will be able to track all the resume submitted to companies, it will be of more value for people searching for job and are submitting their resume's to different companies, they will be able to input all the response relating to interviews, the app will manage anything that has to do with the resume as well as interview and it will save users of the application from forgetting any necessary information that are essential
If all the above suggested features are added on the application it will improve users experience.
Thank you

Hello @tykees Thanks for your interest in my project. I am planning a major update and sure I will use your suggestions. Thanks for your very insightful notes and suggestions.

You welcome bro! I will look forward to seeing that

Hello!!! i am one the lover of your project and i have been using the app for quite sometimes now and i would love to see some improvement on the project.
I propose the

Ability to select Format and style of resume and option to select background.
Direct Upload to social media channels
Upload and take picture
Magnifier tool and Font size
Interview recorder

Ability to select format/style of the resume and option to select background
This function is also known as appearance whereby users will be able to select the way which the resume will be printed out in terms of designs depending on user's interest and as required by the prospective employer, this will also have a function to select how the furthest/background part of the resume will look like in terms of color.
I believe this can be realised by providing options for users to pick as how they would like the finishing of their resume should look like.
Direct upload to social media channels
After inputting all necessary information and user previewed the resume there is a icon to save the resume into mobile storage memory/SDcard or google-drive so any further procedure has to to be from the device, I am suggesting a smart way of sending resume directly from the app to other social media platform this feature will be on the preview
There will be a icon whereby users will be able to send/upload their organized resume directly to social media platforms directly.
Upload and take picture
There are some advanced resume that requires adding of picture to suit the requirement of the employer's so addition of this feature will be useful for this reason, There will be upload button and take picture at the Personal Info page of the app so users can decide to use this features if entailed.
Magnifier tools and Font size
These features are needed majorly at the preview page of the resume, magnifier is a lens that is used to make something more larger in appearance in another word to zoom in and out of a page to enable better view for users depending on their visual capability as the page does not allow pinch to zoom
Font is a type of different sizes of text which can be selected and use, user can easily select font size that they would like to use to save their resume.
Interview recorder
Interview recorder is a feature whereby all submitted or sent resume possibly for job or any other purpose can be tracked, there will be a section within the app where user can input all the necessary information's got from the prospective employer such as Company name, date and time for interview, all necessary document to submit, Location/venue.
Mock ups
Pictorial illustrations of my suggestions

https://cdn.discordapp.com/attachments/413700596785348608/465242958296514584/20180707_204713.gif

Benefits
Pragmatically all the suggested features and sections enhancement will be of added advantage for users of the application.
With the ability to select format/style of resume users will be able to select the type of resume format they want, depending on the design that will suit their purpose, definitely these will make the application to be more advance and more useful.
Upload icon to social media platforms will make the project to be more flexible because it will be very easy to send resume directly to anyone within all installed social media platforms available on the user's device and the recipient can easily download the file on their device and this will perfect a specific extent of good enhancement.
Upload and take picture will also be of a brilliant feature as user will be able to add picture to their resume if required.
Instead of using another application to add picture RESUME BUILDER will perfect it and their won't be need for searching else where to add picture to resume.
Magnifier tools, Apparently this feature is meant majorly for people with sight issue and the preview page text might be kinda smaller in text, the inclusion of the feature will enable users to zoom in to see all the text properly as the page does not work on pinch to zoom.
As for now the save available is only in PDF and might involve additional application to convert PDF to Ms doc or other editable format,
Font size before saving resume will be of good feature so that the printed copy will have a suitable font size to eradicate all sort of limitation on the printed copy of the resume as user can select font size that will be nice
Interview recorder
This feature has lots of benefits.
Users will be able to track all the resume submitted to companies, it will be of more value for people searching for job and are submitting their resume's to different companies, they will be able to input all the response relating to interviews, the app will manage anything that has to do with the resume as well as interview and it will save users of the application from forgetting any necessary information that are essential
If all the above suggested features are added on the application it will improve users experience.
Thank you

sir please send me the link of your  resume project.


#17 Fail gracefully when no network connection

In fact you really need to rebase against main -- the npo branch is now historical.


fix for aws-provider 3.0

what

handles breaking change for terraform provider 3.0 https://registry.terraform.io/providers/hashicorp/aws/latest/docs/guides/version-3-upgrade#domain_validation_options-changed-from-list-to-set

why

support aws provider 3.0

notes
This does not recreate the cert, but will recreate the DNS validation records. This is ok, because the route53 record resource already had allow_overwrite set to true. No outputs or variables were changed.
references
closes #26

/test all

@geota This seems to break tests and doesn't seem to update the aws provider pinning. Have you used this on a project successfully? Any thoughts on the broken tests or not changing the aws provider pin?

@Gowiem  yes, we are using this in production and is working fine. It did not destroy our existing certs but did require manually working through the linked terraform 3 upgrade notes for this.

TestExamplesComplete 2020-08-12T01:45:19Z command.go:121: Error: Invalid for_each argument
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121:
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121:   on ../../main.tf line 26, in resource "aws_route53_record" "default":
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121:   26:   for_each = {
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121:   27:     for dvo in local.domain_validation_options_list : dvo.domain_name => {
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121:   28:       name   = dvo.resource_record_name
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121:   29:       record = dvo.resource_record_value
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121:   30:       type   = dvo.resource_record_type
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121:   31:     }
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121:   32:   }
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121:
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121: The "for_each" value depends on resource attributes that cannot be determined
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121: until apply, so Terraform cannot predict how many instances will be created.
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121: To work around this, use the -target argument to first apply only the
TestExamplesComplete 2020-08-12T01:45:19Z command.go:121: resources that the for_each depends on.

I tested this successfully on Terraform 0.13 and AWS Provider 3.0 on an existing already applied module.
My guess is the above issue is related to the for_each depending on local.domain_validation_options_list which in the module depends on aws_acm_certificate.default.0.domain_validation_option and on a clean apply fails because of the dependency and terraform not able to resolve it until runtime.
  domain_validation_options_list    = local.process_domain_validation_options ? aws_acm_certificate.default.0.domain_validation_options : []

The real fix is probably reverting this and translating the terraform aws-provider 3.0 upgrade notes into the count structure that this module was using. TBH, I do not have time to pick this up and was mainly just fixing a production issue that we hit when upgrading to 3.0. Feel free to close this out.

/rebuild-readme

@geota master is pinned to ~> 2.0 of the aws provider. Like @Gowiem says, this doesn't pin to 3.0, so it can't possibly be verified against the 3.0 provider.

/test all

@geota We just merged #29, which addresses the provider 2.x lock and passed tests. Can you revaluate this PR and describe why these changes are needed as I'm confused on that front.


Increase build + test timeout

With the additional test languages being added the test task is pushing the limits of the default 60min timeout.

https://github.com/Azure/azure-functions-sql-extension/issues/562


More helpful errors

This PR improves the errors a user may see when building a project with Model Compiler.

@armiol, PTAL.


Heroku - "Whoops, looks like something went wrong."

After deploying to Heroku I keep getting Whoops, looks like something went wrong..
This was after running the recommended commands via Heroku CLI.
I did verify my API_SECRET and SECRET_TOKEN are set.

So besides that I'm out of luck?

I'm not sure why you're still having a problem. I deployed a new build just now and was able to set the key using a local instance, then saving the generated value using the official Heroku docs that I quoted above.

@luckyrabbitllc
I have tried to fresh install multiple times I just don't get what I am doing wrong -
I generate a fresh APP_KEY

Then I run the following commands using Heroku run console
php artisan migrate:refresh --seed --force

php artisan passport:install

php artisan command:SyncGit reset

They all run and I go to the site and still an error, I have tried to restart the dyno after and still same error.

Do you get an error when going to yourapp.herokuapp.com/login ? If so, can you post the error?

I got that finally working - I ended fresh installing -> Add APP_KEY -> Restart -> Perform Commands -> Restart and it works.
However - when I edit a users password it doesn't work and I can't add/change permission.

Also getting a Whoops, looks like something went wrong when going to app/packages
`

I ended fresh installing -> Add APP_KEY -> Restart -> Perform Commands -> Restart and it works.

Glad you got it working though.  Just FYI, the first restart was unnecessary, because Heroku restarts the server after you change the environment variable. I'll be adding documentation to the website soon with step by step images to make this part more clear.

However - when I edit a users password it doesn't work

Are you still having this problem? If so, can you make a new issue with more detailed info? Same with the permissions issue. Currently permissions are only editable via command line, which you can do like so:
command:EditUserRoles<EMAIL_ADDRESS>admin,user,staff,developer,writer,editor,executive
The logic for editing permissions with GUI is about 80% done. If you need that functionality sooner than later, please feel free to finish it up and make a PR.

Also getting a Whoops, looks like something went wrong when going to app/packages

Would you mind making a new issue for this and posting a more detailed error response? You'll need to add APP_DEBUG = true to your environment variables to get more output.


Common type replacement for Compute

See this document. Compute has its own common type. We should decide whether to replace its own common type to the one in our arm library.
Current decision: we only replace Resource, ResourceWithOptionalLocation, userAssignedIdentities, SystemData

@allenjzhang Please clarify any work for the TypeSpec team


Too many redirects

Issue Type: Bug
Getting an error while trying to check for updates and getting Too many http redirect errors.
VS Code version: Code 1.44.2 (ff915844119ce9485abfe8aa9076ec76b5300ddd, 2020-04-16T17:07:18.473Z)
OS version: Darwin x64 19.4.0

Did you review the information at https://code.visualstudio.com/docs/setup/network ?

I also encountered this problem, click Check for updates, and then prompt for too many HTTP redirections

[2020-06-29 20:32:37.315] [main] [info] update#ctor - startup checks only; automatic updates are disabled by user preference
[2020-06-29 20:33:07.319] [main] [info] update#setState checking for updates
[2020-06-29 20:33:07.335] [main] [error] UpdateService error: 太多的HTTP重定向
[2020-06-29 20:33:07.335] [main] [info] update#setState idle


fix(deep): fix Path.update not updating values correctly

Fixes #79

Codecov Report

Merging #80 (8534f71) into main (b87eb80) will increase coverage by 2.48%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #80      +/-   ##
==========================================
+ Coverage   85.70%   88.19%   +2.48%
==========================================
  Files          56      211     +155
  Lines        4492    13259    +8767
  Branches      475     2710    +2235
==========================================
+ Hits         3850    11694    +7844
- Misses        554     1388     +834
- Partials       88      177      +89

Impacted Files
Coverage Δ

packages/base/src/plain-object.ts
14.28% <ø> (ø)

packages/deep/src/protected.ts
50.00% <ø> (ø)

packages/reactor/src/hooks/useActorState.ts
100.00% <ø> (ø)

packages/deep/src/path.ts
100.00% <100.00%> (ø)

packages/reactor/src/controls/ObsStream.ts
100.00% <100.00%> (ø)

packages/reactor/src/hooks/useActor.ts
100.00% <100.00%> (ø)

packages/table/test-utils/table-standard-test.ts

packages/multiset/test/multiset-test-standard.ts

packages/graph/test/arrow-graph-test-standard.ts

packages/list/test/setupTests.ts

... and 170 more

Continue to review full report at Codecov.

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


Add pry-rails and pry-byebug to gem file

Solving issue #108

Please clean this branch. It should have ONLY the single commit in this. Please see https://github.com/emerald-rubies/guides/blob/master/git/keep-feature-branches-up-to-date.md

Closing in favor of https://github.com/emerald-rubies/tenacious/pull/122


CPOL-44 Adds filtering to the Policy table

Moved to insight's PrimaryToolbar component to match look and feel
Changing the way the Insights var was being obtained

Depends on https://github.com/RedHatInsights/custom-policies-ui-backend/pull/39
Depends on #44

Should we prevent this combination, as this would always result in no output?

Should we prevent this combination, as this would always result in no output?

We can prevent that (changing to a radio button), but i'm interpreting it as "Active or Inactive", effectively removing the filter on the query (can be verified by checking the network tab)

On 18 Feb 2020, at 15:59, Josejulio Martínez wrote:

We can prevent that (changing to a radio button), but i'm interpreting
it as "Active or Inactive", effectively removing the filter on the
query (can be verified by checking the network tab)

Hm. This confuses me even more, that both checked == none checked.
Perhaps we ask Katie

Should we prevent this combination, as this would always result in no output?

This should have an output, it will have the entire list.

This filter is similar to the "rule status" filter in rules.

By default on open, only "Enabled" things are shown, so there is a filter chip (because the default is to show a subset). Since we are showing the entire list, we don't need the chip and "All" would be preselected.
Check out this behavior in CI


Execution failed for task ':react-native-vision-camera:compileDebugKotlin'🔧

How were you trying to build the app?
I tried to build on android simulator and real device but its not working. always giving a build error. Please suggest me whats going wrong with android version
iOS is working smoothly.
Full build logs
Duplicate class com.facebook.yoga.YogaPositionType found in modules jetified-react-android-0.74.0-rc-debug.5-debug-runtime (com.facebook.react:react-android:0.74.0-rc.5) and jetified-react-native-0.70-debug.14-debug-runtime (com.facebook.react:react-native:0.70.14)
     Duplicate class com.facebook.yoga.YogaProps found in modules jetified-react-android-0.74.0-rc-debug.5-debug-runtime (com.facebook.react:react-android:0.74.0-rc.5) and jetified-react-native-0.70-debug.14-debug-runtime (com.facebook.react:react-native:0.70.14)
     Duplicate class com.facebook.yoga.YogaStyleInputs found in modules jetified-react-android-0.74.0-rc-debug.5-debug-runtime (com.facebook.react:react-android:0.74.0-rc.5) and jetified-react-native-0.70-debug.14-debug-runtime (com.facebook.react:react-native:0.70.14)
     Duplicate class com.facebook.yoga.YogaUnit found in modules jetified-react-android-0.74.0-rc-debug.5-debug-runtime (com.facebook.react:react-android:0.74.0-rc.5) and jetified-react-native-0.70-debug.14-debug-runtime (com.facebook.react:react-native:0.70.14)
     Duplicate class com.facebook.yoga.YogaValue found in modules jetified-react-android-0.74.0-rc-debug.5-debug-runtime (com.facebook.react:react-android:0.74.0-rc.5) and jetified-react-native-0.70-debug.14-debug-runtime (com.facebook.react:react-native:0.70.14)
     Duplicate class com.facebook.yoga.YogaValue$1 found in modules jetified-react-android-0.74.0-rc-debug.5-debug-runtime (com.facebook.react:react-android:0.74.0-rc.5) and jetified-react-native-0.70-debug.14-debug-runtime (com.facebook.react:react-native:0.70.14)
     Duplicate class com.facebook.yoga.YogaWrap found in modules jetified-react-android-0.74.0-rc-debug.5-debug-runtime (com.facebook.react:react-android:0.74.0-rc.5) and jetified-react-native-0.70-debug.14-debug-runtime (com.facebook.react:react-native:0.70.14)

     Go to the documentation to learn how to Fix dependency resolution errors.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':react-native-vision-camera:compileDebugKotlin'.
> A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
   > Compilation error. See log for more details

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================

* Get more help at https://help.gradle.org

BUILD FAILED in 1m 2s

    at makeError (/Users/vinod/workspace/vino/sk/Vinod/source_code/Vinod/node_modules/execa/index.js:174:9)
    at /Users/vinod/workspace/vino/sk/Vinod/source_code/Vinod/node_modules/execa/index.js:278:16
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async runOnAllDevices (/Users/vinod/workspace/vino/sk/Vinod/source_code/Vinod/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:109:5)
    at async Command.handleAction (/Users/vinod/workspace/vino/sk/Vinod/source_code/Vinod/node_modules/@react-native-community/cli/build/index.js:142:9)

Project dependencies
buildToolsVersion = "31.0.0"
minSdkVersion = 24
compileSdk = 33
targetSdkVersion = 33

kotlinVersion = "1.7.0"

"dependencies": {
    "react": "18.1.0",
    "react-native": "0.70.14",
    "react-native-reanimated": "^3.7.0",
    "react-native-vision-camera": "^3.9.2",
}

VisionCamera Version
3.9.2
Target platforms
Android
Operating system
MacOS
Can you build the VisionCamera Example app?
I didn't try (⚠ your issue might get ignored & closed if you don't try this)
Additional information

[ ] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

This doesn't look like a VisionCamera error, but rather a react-native issue. Clean your cache and try again. Also, maybe you need to upgrade to RN 0.71.

@mrousavy Which version is supported for RN 0.70.14.
Can you please tell the react native vision camera version compatibility for RN 0.70.14

I don't remember - maybe an old V3 version. Either way, I'd recommend you to upgrade to RN 0.71 either way

@mrousavy
I am getting the below error when using the RN 0.71 and camera vision version 3.0.2
Duplicate class com.facebook.yoga.YogaValue$1 found in modules jetified-react-android-0.74.0-rc-debug.6-debug-runtime (com.facebook.react:react-android:0.74.0-rc.6) and jetified-react-native-0.70-debug.14-debug-runtime (com.facebook.react:react-native:0.70.14)
 Duplicate class com.facebook.yoga.YogaWrap found in modules jetified-react-android-0.74.0-rc-debug.6-debug-runtime (com.facebook.react:react-android:0.74.0-rc.6) and jetified-react-native-0.70-debug.14-debug-runtime (com.facebook.react:react-native:0.70.14)

Go to the documentation to learn how to Fix dependency resolution errors.

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

2: Task failed with an exception.

What went wrong:
Execution failed for task ':react-native-vision-camera:compileDebugKotlin'.

A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleCompilerRunnerWithWorkers$GradleKotlinCompilerWorkAction
Compilation error. See log for more details

Try:

Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.
==============================================================================

Get more help at https://help.gradle.org

BUILD FAILED in 5m 37s


add cachelib multi-tier example

Starting this pull request as WIP for adding multi-tier cachelib example

This change is

Thanks @lukaszstolarczuk I fixed these typos