Uncaught BadMethodCallException: Object->__call(): the method 'TableTitle' does not exist on 'SilverShop\Model\Modifiers\Tax\FlatTax'

Looks like the function in Model/OrderAttribute.php has changed from "TableTitle" to "getTableTitle", but Model/Modifiers/Tax/Base.php still calls parent::TableTitle().

Cheers!

@wilr same issue on SilverShop\Model\Modifiers\Shipping\Simple.

Updated @joshdillner 👍

Cheers.


Async client

It looks like the e2e tests fail because your PR is not allow to make use of project secrets. I will run this locally and check it out.

It would also be nice to see a usage test:
Like
async_dune.refresh(query1, query2, query3)  <- Did you provide an interface to query many?

and also some test that demonstrates the maximum number of parallel execution limitations.

I have read the CLA Document and I hereby sign the CLA

recheck

Fixed the issue with the tests failing -- forgot that ClientResponse().json() outputs the coroutine itself. I still have issues testing this locally as I don't have the Dune API key (and this key can't be easily acquired).
Didn't add any new functionality so far. I think it's better to leave it for future updates (as this PR already is kinda big).

async_dune.refresh(query1, query2, query3)  <- Did you provide an interface to query many?

as for this issue. I think the more convenient way would be for the consumer to do something like
asyncio.gather(*[async_dune.refresh(query) for query in queries])
This way the consumer has all the control around executing and limitations

Here is the failing assertion error details:
            assert (
                self._base_url.origin() == self._base_url
            ), "Only absolute URLs without path part are supported"

and the values are:
> self._base_url
https://api.dune.com/api/v1
> self._base_url.origin()
https://api.dune.com

I have also fixed all the lint, format and type errors on my side. Not sure if I can push them here (or if you even want me to)

I have also fixed all the lint, format and type errors on my side. Not sure if I can push them here (or if you even want me to)

Thanks a lot for helping! Fixing the mistakes. Sorry that you have to manually run the pipeline, I just can not test this locally, so such mistakes occur... I would push code formatting together with tests fixes

I think I could separate the pipeline a bit (partition lint format type instead of having them run sequentially so you can at least see all of the issues from a single push). Note that you should be able to run all but e2e checks on from your own side (i.e. without an API_KEY)

Hows this going @eliseygusev - Have you seen the PR with Fixes to make this pass CI?
https://github.com/eliseygusev/dune-client/pull/1
Would love to get this merged!

Yeah, I’ve seen the PR. Would update the code either today in the evening
or tomorrow. Thanks for your support!
On Mon, 7 Nov 2022 at 15:18, Benjamin Smith @.***>
wrote:

Hows this going @eliseygusev https://github.com/eliseygusev - Have you
seen the PR with Fixes to make this pass CI?
eliseygusev#1 https://github.com/eliseygusev/dune-client/pull/1
Would love to get this merged!
—
Reply to this email directly, view it on GitHub
https://github.com/cowprotocol/dune-client/pull/31#issuecomment-1305684131,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBEHL6IQGHRB6YDZVRDXQLWHEFRXANCNFSM6AAAAAARV6GMTA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ok, so merged your request. Thanks a lot for it! But i'm kind of lost about whether there is something left to fix before merging?

Fixed the linters but not sure whats happening with the tests. Is it permissions' things or something is failing in the code?

I think its all good. We can merge and publish a beta release from there. I won't have time to test it out this week though, but at least it will be available.

It is a permission thing, your branch does not have access to our secrets.

but you can also run these lint checks on your own side before pushing:
black ./ && pylint dune_client && mypy dune_client --strict

but you can also run these lint checks on your own side before pushing:

black ./ && pylint dune_client && mypy dune_client --strict
yeah, sorry, my bad. always forget about it. can I add Makefile with commands for linters and tests so that one can just
make lint to make the code pass linters?

yeah, sorry, my bad. always forget about it. can I add Makefile with commands for linters and tests so that one can just
make lint to make the code pass linters?

That's great, but in a separate PR.

That's great, but in a separate PR.

Ok, will add it soon. Is there anything else in this PR left to do on my side? Or you will just merge and publish by yourself?

Is there anything else in this PR left to do on my side?

Fix the failing lint! I will do the rest.

Fix the failing lint! I will do the rest.

I wasn't sure why mypy failed in CI. I didnt touch interface.py and locally mypy --strict works. However, I think I did fix it with the addition of abc.abstract_method should be good now

Has been published under https://pypi.org/project/dune-client/0.2.0b0/
Thanks very much for your contribution!

I am trying to use this async client and keep running into these errors

RuntimeError: Timeout context manager should be used inside a task
2022-11-16 00:49:21,368 ERROR asyncio Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x106ba64a0>

I have tried putting a close session after the refresh call, like so
response = await self.dune.refresh(query, ping_frequency=10)
await self.dune.close_session()

but still get them. Would love if you could show me how to use this from an external package and maybe make it somehow more convenient for external users.


HTML in source?

i found this: https://github.com/courtois-neuromod/anat-processing-book/blob/main/source/results/new-fig-2.html
i thought the HTML material was only in the built (not source) folder?

Hi @jcohenadad, this is the output that is seen inside the cell. The plotly plot function from the ploty.offline save outputs as HTML and we store that in the notebook.

Isn't that something that we can generate on the fly before shipping all the content to the server hosting the book? related to #15


[watch_connectivity_garmin] Android not receiving messages

I am trying to send a message from the watch to the android app when the user presses a button on the watch.
The connection to the simulator through adb works. But when I click a button the only thing I get inside the console is:
D/ConnectIQ-AdbConnection( 7611): Received 25 from simulator
D/ConnectIQ-AdbConnection( 7611): Looking for input from simulator.

watch.isReachable, isPaired, isSupported all are true
I am listening to the messages like this:
watch.messageStream.listen(
  (message) {
    print('Received message: $message');
  },
  onError: (e) {
    print("message error $e");
  },
  onDone: () {
    print("done message");
  },
);

And sending from the watch like this:
Communications.transmit("test", null, listener);

The function from public function onComplete() as Void { triggers (on the watch).
The messageStream onData doesn't trigger.
Does the transmitted data has to be in a certain format? Or is there something else that could cause this issue?

Both the watch and phone apps mush have the same bundle identifier. Also the data is supposed to be a map.

Thanks for the quick reply. For Garmin apps there is no bundle identifier as far as I know?
I only have the app uuid which is the same as the applicationId.
I also tried with a dict as data but that doesn't work either:
Communications.transmit({"data"=>count}, null, listener);

Oh whoops I didn't see that you were using the Garmin plugin. Yeah I don't think there is a bundle identifier restriction there.

Unfortunately I created the Garmin plugin in collaboration with a company that I no longer work with, so I don't have a Garmin app to test with. Can you open the plugin example project in Xcode or Android Studio and set a breakpoint where the message is supposed to come in? If you need help with that, we could have a call on Discord to debug this.

Any updates on this?

Any updates on this?

Unfortunately not yet. I didn't have time to look into this more.


Adding support for Solr Json queries

This MRs brings basic Solr Json query support to splainer-search.
To pull this off, given the current codebase, we have the following options:

Do a POST with JSON body that is not jsonp (https://stackoverflow.com/a/4508215)
Do a GET with JSON body - not sure if it will work with jsonp;
Preserve the current way of doing things, and do a GET with json request parameter in the query string (see https://lucene.apache.org/solr/guide/8_1/json-request-api.html#building-json-requests)

For simplicity sake, we are going with the latter in this PR.
I wasn't able to test this - would love your help with testing and validating the solution.

From a splainer / splainer-search perspective, so long as we treat "Solr JSON" as a kind of different 'search engine' than classic Solr API, I'm all for adding it. In this way, in splainer we could make sure to use the right JSON ACE UI editor, etc. I wouldn't want to try to Frankenstein them together too much. Just my 2 cents...

@softwaredoug @epugh how would you want to proceed? can you provide some concrete guidance / feedback?
We are looking to implement JSON queries support for Solr in Quepid and need to complete the work on this PR first. Will be happy to drive this to completion but will need your guidance here.

Let me play w the patch tomorrow and get some more feedback.
In order to support a richer UI and eventually more validations, I am
wondering if now is the time to have a second solr implementation for json?
I want to get us to being able to support search APIs as well..,
On Wed, Jan 1, 2020 at 3:33 AM moshebla<EMAIL_ADDRESS>wrote:

@softwaredoug https://github.com/softwaredoug @epugh
https://github.com/epugh how would you want to proceed? can you provide
some concrete guidance / feedback?
We are looking to implement JSON queries support for Solr in Quepid and
need to complete the work on this PR first. Will be happy to drive this to
completion but will need your guidance here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/o19s/splainer-search/pull/73?email_source=notifications&email_token=AAAFO63BHRBXB56O6AEKC4LQ3RIOVA5CNFSM4J5BZZE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEH5APEQ#issuecomment-570034066,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAFO64DGVIYRMC5V3EDSIDQ3RIOVANCNFSM4J5BZZEQ
.

We are all in for more search backends (e.g. https://github.com/o19s/splainer-search/tree/custom_backend_support). Will wait for your guidance on how to best support this. I wasn't able to test this - would love your help with testing and validating the solution.
On a related note - is splainer-search benefits from being stand-alone? seems like it adds a lot of work for making search-related changes to quepid.

Good question on splainer-search being a libary.  I assume you are faimilar with http://splainer.io ???    The traffic on that site is actually about double what we get in Quepid...   It addresses the "let me understand a single query"....       And enhancements like what we are talkign about here, are also needed in splainer.io.       Having said that, I do wonder if in the future Quepid has multiple "perspectives", (i.e a view for doc raters, a view for search engineers, a view for "tell me about this query") and we could fold the splainer.io use case into Quepid itself.

That makes sense, thanks.
How would you like to proceed here?

@moshebla - I had a long conversation with @softwaredoug about the direction of splainer, and we'd like to go ahead and and split out the JSON API support from the old query version in Solr.
The thinking here is that

We need to bite the bullet and accept that we need to support multiple search api's, so going from two to three will get that process going.
Let's encourage the Solr community to move away from the old queryparams approach!  I think we should just support the JSON syntax in the body of the POST, and not support the odd blended "mix some query params and some json".
We can start optimizing the UI around the JSON format.
At some point, we're going to see debug output from Solr that is specific to the Solr V2 api, so this way we can optimize for it.

Should we start a new PR for this?

I wanted to follow up and see if you'd had a chance to think about adding a new version of Solr, versus modifying the existing one?    I'm going to close this PR as there are conflicts.   Please do ping me if you need help or want to talk about what the Solr Classic versus Solr JSON could look like!


Added --redirect option to bin/polymer-bundler.

Adds the --redirect option from vulcanize 1.0 to polymer-bundler 2.0
[x] CHANGELOG.md has been updated

@danbeam @freshp86

@usergenic  Thanks. I'll try to test this soon and report back with whether it works for Chromium's purposes.


Fix: relation widget performance

Fixes https://github.com/netlify/netlify-cms/issues/3810
Fixes https://github.com/netlify/netlify-cms/issues/3908

Fixes the search for file collections by using expandPath inside backend.ts (moved to a shared lib).
Virtualises the select dropdown.
Passes options length as a limit to backend.ts to avoid saving all results in the redux store.

@magomimmo I would appreciate if you could do some testing on this.
@barthc same, especially for the approach on searching via wildcards.

@magomimmo I would appreciate if you could do some testing on this.
@barthc same, especially for the approach on searching via wildcards.

Hi @erezrokah, sure. I'll do tomorrow. Thanks so much

Hi @erezrokah, Just to be sure to do the right thing to test the fix.

Checkout into the fix/widget-relation-performance branch, build and start it to test that is still working as expexted;
Go to my project and remove the previously added netlify-cms-app package
Then add netlify-cms with the following yarn command: `yarn add /netlify-cms/packages/netlify-cms'
clean, rebuild and start my project

Is this the right way to test the branch fixing the performance issue with the relation-widget? Should I test both the folder-to-folder relation and the folder-to-file relation as well?

Sorry for not being clear enough with the instructions.
git clone https://github.com/netlify/netlify-cms
cd netlify-cms
git checkout fix/widget-relation-performance
yarn
yarn bootstrap

Copy the relevant backend files from ./dev-test/<backend> to ./dev-test.
Update the config.yml accordingly.
yarn start
You should be able to access just the CMS via http://localhost:8080 without any changes to your project (you could also change your project like you mentioned).

Should I test both the folder-to-folder relation and the folder-to-file relation as well?

Both would be great.

Hi @erezrokah, the folder to files relation is now really quick. I tested it with my cities.json containing 8k cities. The only problem is that the search gives very strange result as you can see in the attached video recording.
In the mean time I'm going to the folder to folder relation.
netlifycms.zip

Hi @erezrokah , even the folder to folder relation is now very fast and the search works as expected as well. So, aside from the unexpected search results in the folder-to-file relation, the widget relation is now really really good in terms of performance.

@erezrokah doing
 f.startsWith(`${path}.${index}.`)

here should fix the search bug. Based on the search, for folder collections relation, the value field would not work doing something like so:
 displayFields: ['list.1.title']
 searchFields: ['list.1.title']
 valueField: 'list.0.title'

seems to be a valid use case  WDYT?

seems to be a valid use case WDYT?

Can you share a full config with this use case? Not sure I understand it.
If a user references a specific item from a list, maybe a list widget is not the best option for specifying the relation.

Can you share a full config with this use case? Not sure I understand it.
If a user references a specific item from a list, maybe a list widget is not the best option for specifying the relation.

Here is an issue with the use case https://github.com/netlify/netlify-cms/issues/473

Here is an issue with the use case #473

I think in that case you would either use the wild card for both searchFields and valueField or use the same index
name: product_id
widget: relation
collection: catalog
searchFields: [product.*.name, product.*.author]
valueField: product.*.id

@magomimmo I pushed a fix to the search bug.

@magomimmo I pushed a fix to the search bug.

Hi @erezrokah the fix works as expected. Thanks so much for your hard work!

@erezrokah  accessing a single list item other than 0 index doesn't work anymore for valueField after resetting index in mergeExpandedEntries function.

@erezrokah accessing a single list item other than 0 index doesn't work anymore for valueField after resetting index in mergeExpandedEntries function.

Can you share a config.yml for this use case? I can't think of a reason for someone to reference a list field without a wildcard for both searchFields and valueField.

@erezrokah accessing a single list item other than 0 index doesn't work anymore for valueField after resetting index in mergeExpandedEntries function.

Can you share a config.yml for this use case? I can't think of a reason for someone to reference a list field without a wildcard for both searchFields and valueField.

me too @barthc At the moment in all my use cases I always need the wildcard only.

me too @barthc At the moment in all my use cases I always need the wildcard only.

Alright then, maybe update the doc to discourage users from doing so. I think it suggested some reference.


Start time always to 00:00 to (24:00 or 00:00)

I want to show time row 0-24 hrs format. It is always showing current time onwards. please, let me know how to stop this. I just want 0-24 hrs in row. please let me know asap.

Hou need to to set show24hours to true and comment the scrolltocurrenttime function, cant remeber exactly since im not at computer
To show one day just set daystoshow and daystoshowonscreen to 1
Enviat des del meu iPhone
El 9 nov 2016, a les 6:09, sanojKashyap<EMAIL_ADDRESS>va escriure:

I want to show time row 0-24 hrs format. It is always showing current time onwards. please, let me know how to stop this. I just want 0-24 hrs in row. please let me know asap.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

is it possible to implement without using pod? I am missing many files.
On Wed, Nov 9, 2016 at 12:32 PM, Jordi Puigdellívol <
<EMAIL_ADDRESS>wrote:

Hou need to to set show24hours to true and comment the scrolltocurrenttime
function, cant remeber exactly since im not at computer
To show one day just set daystoshow and daystoshowonscreen to 1
Enviat des del meu iPhone
El 9 nov 2016, a les 6:09, sanojKashyap<EMAIL_ADDRESS>va
escriure:

I want to show time row 0-24 hrs format. It is always showing current
time onwards. please, let me know how to stop this. I just want 0-24 hrs in
row. please let me know asap.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/erichoracek/MSCollectionViewCalendarLayout/issues/81#issuecomment-259346640,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADBzyqDBcg17NSfZHOgjCkUMgrAfsADbks5q8W_8gaJpZM4KtMDc
.

--
Thanks & Regards
Sanoj Kashyap
iOS Developer
Skype - sanoj.kashyap
Mob - +91-9590399725

Yes sure, but you will need to use the dependencies as well (easyDate and Collection)
You will just need to copy the files to you project

I can't user you project ,Both pod and import the demo files inside.Can you tell me the usage?Urgent urgent！


chore: git-action: enable golang-ci-lint checks on git action

changes:

enable golang-cli-lint on git action.
pass golang-cli-lint checks.
remove duplicate go test ...

would resolve https://github.com/filecoin-project/venus/issues/5081

Codecov Report

Merging #208 (c451e98) into main (df5e882) will increase coverage by 0.08%.
The diff coverage is 24.48%.

@@            Coverage Diff             @@
##             main     #208      +/-   ##
==========================================
+ Coverage   16.14%   16.22%   +0.08%
==========================================
  Files          53       53
  Lines        5184     5183       -1
==========================================
+ Hits          837      841       +4
+ Misses       4263     4258       -5
  Partials       84       84

Flag
Coverage Δ

unittests
16.22% <24.48%> (+0.08%)
:arrow_up:

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


praetor-based provider 0.1.0 removed the deployment after lease query failed ... err=(MISSING) message

praetor-based provider-services: 0.1.0
provider address: akash1tweev0k42guyv3a2jtgphmgfrl2h5y2884vh9d
A provider owner SGC#3172 reported the j0asgbmq1a6p4s7ii0tlvuoco.ingress.dcnorse.ddns.net ingress host resource (for the DSEQ 9562948) started to return 404 and other deployments disappeared from his k8s cluster.
What's interesting is that I can see in the provider logs providerleasedips CRD does not exist messages, which is part of the praetor-based provider starting script check (you can see it below).
Which means that there is some condition where K8s cluster does not seem to be fully initialized or so.. which is causing the provider think it's got no leases (lease query failed ... err=(MISSING) leading to the lease removal; though, it does not close them on the blockchain [bid, lease, order, deployment staying in the active/open state]).
leases are still active from the blockchain point of view

lease, order, bid, deployment for the dseq 9562948 are all open/active

$ export PROVIDER=akash1tweev0k42guyv3a2jtgphmgfrl2h5y2884vh9d; HEIGHT=$(akash query block | jq -r '.block.header.height'); provider-services query market lease list --height $HEIGHT --provider $PROVIDER --gseq 0 --oseq 0 --page 1 --limit 10000 --state active -o json | jq --argjson h $HEIGHT -r '["owner","dseq/gseq/oseq","rate","monthly","withdrawn","consumed","days"], (.leases[] | [(.lease.lease_id | .owner, (.dseq|tostring) + "/" + (.gseq|tostring) + "/" + (.oseq|tostring)), (.escrow_payment | (.rate.amount|tonumber), (.rate.amount|tonumber), (.withdrawn.amount|tonumber)), (($h-(.lease.created_at|tonumber))*(.escrow_payment.rate.amount|tonumber)/pow(10;6)), (($h-(.lease.created_at|tonumber))/((60/6)*60*24))]) | @csv' | awk -F ',' '{if (NR==1) {$1=$1; printf $0"\n"} else {block_time=6; rate_akt=(($4*((60/block_time)*60*24*30.436875))/10^6); $4=rate_akt; withdrawn_akt=($5/10^6); $5=withdrawn_akt; $6; $7; print $0}}' | column -t ; TZ=UTC date
"owner"                                         "dseq/gseq/oseq"  "rate"            "monthly"  "withdrawn"  "consumed"           "days"
"akash1gx5cmx7c8tm7vw0mlgq2gk5mj0d85lm6p5cf46"  "9574619/1/1"     1.2406            0.543744   0.102863     0.126342704          7.072222222222222
"akash1a2hukwlndnz7svs08z290dm67rjmtuhkq7tq5g"  "9534122/1/1"     3.31814697265625  1.45431    0.043895     0.4722652223242187   9.883888888888889
"akash17fqxak4kprh2rlatjlv9w04s9ugl7mn32ckut3"  "9610985/1/1"     6.3312            2.77491    0.294692     0.41452265759999996  4.5467361111111115
"akash17582ja9fw6k0m0gf9tm9g64w2ks6c7aqdntyst"  "9562948/1/1"     6.3312            2.77491    0.598817     0.718654512          7.882638888888889

Provider logs
See more complete logs for the past 7 days here (90Mi) => https://transfer.sh/Fg7vTc/logs.txt
After about 3 hours from the provider start, the following lines started to appear in the logs:
I[2023-02-07|10:03:45.939] using kube config file                       cmp=provider path=/home/akash/.kube/config
I[2023-02-07|10:03:48.058] using kube config file                       cmp=provider path=/home/akash/.kube/config
D[2023-02-07|10:03:48.078] service being found via autodetection        cmp=provider service=hostname-operator
D[2023-02-07|10:03:48.090] satisfying pending requests                  cmp=provider cmp=service-discovery-agent qty=1
...
...
I[2023-02-07|13:11:51.697] CRD manifest not found                       cmp=provider client=kube lease-ns=uvtrenbt6bch737mf10geqjbl3dmhb85pml2pkugogche
I[2023-02-07|13:11:52.797] CRD manifest not found                       cmp=provider client=kube lease-ns=uvtrenbt6bch737mf10geqjbl3dmhb85pml2pkugogche
...

grep MISSING logs.txt

Feb 06 05:21:36 akash0001 start-provider.sh[10130]: E[2023-02-06|05:21:36.010] lease query failed                           module=provider-cluster cmp=provider cmp=service cmp=deployment-manager lease=akash1gx5cmx7c8tm7vw0mlgq2gk5mj0d85lm6p5cf46/9574619/1/1/akash1tweev0k42guyv3a2jtgphmgfrl2h5y2884vh9d manifest-group=akash err=(MISSING)
Feb 06 05:21:36 akash0001 start-provider.sh[10130]: E[2023-02-06|05:21:36.014] lease query failed                           module=provider-cluster cmp=provider cmp=service cmp=deployment-manager lease=akash17582ja9fw6k0m0gf9tm9g64w2ks6c7aqdntyst/9562948/1/1/akash1tweev0k42guyv3a2jtgphmgfrl2h5y2884vh9d manifest-group=dcloud err=(MISSING)
Feb 06 05:21:36 akash0001 start-provider.sh[10130]: E[2023-02-06|05:21:36.020] lease query failed                           module=provider-cluster cmp=provider cmp=service cmp=deployment-manager lease=akash17fqxak4kprh2rlatjlv9w04s9ugl7mn32ckut3/9610985/1/1/akash1tweev0k42guyv3a2jtgphmgfrl2h5y2884vh9d manifest-group=dcloud err=(MISSING)

Additional information
$ kubectl get crd |grep akash
providerhosts.akash.network       2022-11-08T10:23:32Z
manifests.akash.network           2022-11-08T10:23:32Z
providerleasedips.akash.network   2022-11-18T19:05:32Z

$ kubectl get ing -A
NAMESPACE        NAME                      CLASS                 HOSTS                               ADDRESS     PORTS   AGE
akash-services   akash-hostname-operator   akash-ingress-class   akash-hostname-operator.localhost   localhost   80      91d

# provider-services show-cluster-ns --provider akash1tweev0k42guyv3a2jtgphmgfrl2h5y2884vh9d --dseq 9562948 --owner akash17582ja9fw6k0m0gf9tm9g64w2ks6c7aqdntyst
uvtrenbt6bch737mf10geqjbl3dmhb85pml2pkugogche

# kubectl -n uvtrenbt6bch737mf10geqjbl3dmhb85pml2pkugogche get all -o wide
No resources found in uvtrenbt6bch737mf10geqjbl3dmhb85pml2pkugogche namespace.

for i in manifests providerhosts providerleasedips; do echo === $i ===; kubectl get $i -A; done
=== manifests ===
No resources found
=== providerhosts ===
No resources found
=== providerleasedips ===
No resources found

$ kubectl get nodes -o wide --show-labels
NAME    STATUS   ROLES                  AGE   VERSION        INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME         LABELS
node1   Ready    control-plane,master   91d   v1.25.3+k3s1   <IP_ADDRESS>      <none>        Ubuntu 22.04.1 LTS   5.15.0-58-generic   containerd://1.6.8-k3s1   akash.network/role=ingress,beta.kubernetes.io/arch=amd64,beta.kubernetes.io/instance-type=k3s,beta.kubernetes.io/os=linux,egress.k3s.io/cluster=true,ingress-ready=true,kubernetes.io/arch=amd64,kubernetes.io/hostname=node1,kubernetes.io/os=linux,node-role.kubernetes.io/control-plane=true,node-role.kubernetes.io/master=true,node.kubernetes.io/instance-type=k3s

$ kubectl describe nodes
Name:               node1
Roles:              control-plane,master
Labels:             akash.network/role=ingress
                    beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/instance-type=k3s
                    beta.kubernetes.io/os=linux
                    egress.k3s.io/cluster=true
                    ingress-ready=true
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=node1
                    kubernetes.io/os=linux
                    node-role.kubernetes.io/control-plane=true
                    node-role.kubernetes.io/master=true
                    node.kubernetes.io/instance-type=k3s
Annotations:        flannel.alpha.coreos.com/backend-data: {"VNI":1,"VtepMAC":"0e:bf:9f:21:a8:32"}
                    flannel.alpha.coreos.com/backend-type: vxlan
                    flannel.alpha.coreos.com/kube-subnet-manager: true
                    flannel.alpha.coreos.com/public-ip: <IP_ADDRESS>
                    k3s.io/hostname: node1
                    k3s.io/internal-ip: <IP_ADDRESS>
                    k3s.io/node-args: ["server","--node-name","node1","--disable","traefik","--write-kubeconfig-mode","644"]
                    k3s.io/node-config-hash: DPLMREDACTED
                    k3s.io/node-env: {"K3S_DATA_DIR":"/var/lib/rancher/k3s/data/2ef87ff954adbb390309ce4dc07500f29c319f84feec1719bfb5059c8808ec6a"}
                    node.alpha.kubernetes.io/ttl: 0
                    volumes.kubernetes.io/controller-managed-attach-detach: true
CreationTimestamp:  Tue, 08 Nov 2022 10:22:21 +0000
Taints:             <none>
Unschedulable:      false
Lease:
  HolderIdentity:  node1
  AcquireTime:     <unset>
  RenewTime:       Tue, 07 Feb 2023 13:58:42 +0000
Conditions:
  Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message
  ----             ------  -----------------                 ------------------                ------                       -------
  MemoryPressure   False   Tue, 07 Feb 2023 13:58:10 +0000   Tue, 20 Dec 2022 15:19:44 +0000   KubeletHasSufficientMemory   kubelet has sufficient memory available
  DiskPressure     False   Tue, 07 Feb 2023 13:58:10 +0000   Tue, 20 Dec 2022 15:19:44 +0000   KubeletHasNoDiskPressure     kubelet has no disk pressure
  PIDPressure      False   Tue, 07 Feb 2023 13:58:10 +0000   Tue, 20 Dec 2022 15:19:44 +0000   KubeletHasSufficientPID      kubelet has sufficient PID available
  Ready            True    Tue, 07 Feb 2023 13:58:10 +0000   Tue, 20 Dec 2022 15:19:44 +0000   KubeletReady                 kubelet is posting ready status. AppArmor enabled
Addresses:
  InternalIP:  <IP_ADDRESS>
  Hostname:    node1
Capacity:
  cpu:                128
  ephemeral-storage:  559269800Ki
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             65920684Ki
  pods:               110
Allocatable:
  cpu:                128
  ephemeral-storage:<PHONE_NUMBER>14
  hugepages-1Gi:      0
  hugepages-2Mi:      0
  memory:             65920684Ki
  pods:               110
System Info:
  Machine ID:                 95c3f7828aed407aae0d5e325974c7b2
  System UUID:                95c3f782-8aed-407a-ae0d-5e325974c7b2
  Boot ID:                    131d6385-3504-4933-afe2-0b77d98a0fa2
  Kernel Version:             5.15.0-58-generic
  OS Image:                   Ubuntu 22.04.1 LTS
  Operating System:           linux
  Architecture:               amd64
  Container Runtime Version:  containerd://1.6.8-k3s1
  Kubelet Version:            v1.25.3+k3s1
  Kube-Proxy Version:         v1.25.3+k3s1
PodCIDR:                      <IP_ADDRESS>/24
PodCIDRs:                     <IP_ADDRESS>/24
ProviderID:                   k3s://node1
Non-terminated Pods:          (6 in total)
  Namespace                   Name                                         CPU Requests  CPU Limits  Memory Requests  Memory Limits  Age
  ---------                   ----                                         ------------  ----------  ---------------  -------------  ---
  akash-services              akash-hostname-operator-6b774d7b45-8c8lx     0 (0%)        0 (0%)      0 (0%)           0 (0%)         80d
  kube-system                 local-path-provisioner-5b5579c644-7rfp2      0 (0%)        0 (0%)      0 (0%)           0 (0%)         91d
  kube-system                 coredns-75fc8f8fff-thqqn                     100m (0%)     0 (0%)      70Mi (0%)        170Mi (0%)     91d
  kube-system                 metrics-server-5c8978b444-7wd4g              100m (0%)     0 (0%)      70Mi (0%)        0 (0%)         91d
  akash-services              akash-node-1-0                               0 (0%)        0 (0%)      0 (0%)           0 (0%)         15d
  ingress-nginx               ingress-nginx-controller-6898f4d494-4gs4k    100m (0%)     0 (0%)      90Mi (0%)        0 (0%)         80d
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests    Limits
  --------           --------    ------
  cpu                300m (0%)   0 (0%)
  memory             230Mi (0%)  170Mi (0%)
  ephemeral-storage  0 (0%)      0 (0%)
  hugepages-1Gi      0 (0%)      0 (0%)
  hugepages-2Mi      0 (0%)      0 (0%)
Events:              <none>

$ ps -ef|grep -E 'akash|provider'
akash       4053    3780  1 10:03 ?        00:02:40 /metrics-server --cert-dir=/tmp --secure-port=10250 --kubelet-preferred-address-types=InternalIP,ExternalIP,Hostname --kubelet-use-node-status-port --metric-resolution=15s
root        4223    4002  0 10:03 ?        00:00:00 /usr/bin/tini -- provider-services hostname-operator
root        4255    4223  0 10:03 ?        00:00:05 provider-services hostname-operator
root        9198    3671 79 10:03 ?        02:56:12 /bin/akash start
akash       9371       1  0 10:03 ?        00:00:00 bash /home/akash/.praetor/start-provider.sh
akash       9444    9371  1 10:03 ?        00:02:45 /home/akash/bin/provider-services run --home /home/akash/.akash --chain-id akashnet-2 --withdrawal-period 1h30m0s --minimum-balance 500000 --keyring-backend=file --from akash1tweev0k42guyv3a2jtgphmgfrl2h5y2884vh9d --gas auto --gas-prices 0.025uakt --gas-adjustment 1.30 --kubeconfig /home/akash/.kube/config --cluster-k8s true --deployment-ingress-domain ingress.dcnorse.ddns.net --deployment-ingress-static-hosts true --deployment-runtime-class none --bid-price-strategy scale --bid-price-cpu-scale 0.01 --bid-price-memory-scale 0.0025 --bid-price-storage-scale 0.0001 --bid-deposit 5000000uakt --cluster-node-port-quantity 1000 --cluster-public-hostname praetor.ingress.dcnorse.ddns.net
root       13260    2190  0 13:06 ?        00:00:00 sshd: akash [priv]
akash      13263       1  0 13:06 ?        00:00:00 /lib/systemd/systemd --user
akash      13264   13263  0 13:06 ?        00:00:00 (sd-pam)
akash      13366   13260  0 13:06 ?        00:00:03 sshd: akash@pts/0
akash      13367   13366  0 13:06 pts/0    00:00:00 -bash
akash      14453   13367  0 13:46 pts/0    00:00:00 ps -ef
akash      14454   13367  0 13:46 pts/0    00:00:00 grep --color=auto -E akash|provider

$ /home/akash/bin/provider-services version
v0.1.0

start-script that gets started by akash-provider.service (systemd service):

$ cat /etc/systemd/system/akash-provider.service
[Unit]
Description=Akash Provider
After=network.target

[Service]
User=akash
ExecStart=/home/akash/.praetor/start-provider.sh
KillSignal=SIGINT
Restart=always
RestartSec=15
StartLimitInterval=200
StartLimitBurst=10
#LimitNOFILE=65535

[Install]
WantedBy=multi-user.target

akash@akash0001:~$ cat /home/akash/.praetor/start-provider.sh
#!/usr/bin/env bash

cd ~/.praetor

#maps ip of local RPC node
export AKASH_NODE="http://$(kubectl -n akash-services get ep akash-node-1 -o jsonpath='{.subsets[0].addresses[0].ip}'):26657"

# Check if the providerleasedips CRD exists
if kubectl get crd | grep -q providerleasedips; then
  # Command to execute if the CRD exists
  (
    sleep 2s
    cat key-pass.txt
    cat key-pass.txt
  ) | ~/bin/provider-services run \
    --home ~/.akash \
    --chain-id akashnet-2 \
    --withdrawal-period 1h30m0s \
    --minimum-balance 500000 \
    --keyring-backend=file \
    --from akash1tweev0k42guyv3a2jtgphmgfrl2h5y2884vh9d \
    --gas auto \
    --gas-prices 0.025uakt \
    --gas-adjustment 1.30 \
    --kubeconfig ~/.kube/config \
    --cluster-k8s true \
    --deployment-ingress-domain ingress.dcnorse.ddns.net \
    --deployment-ingress-static-hosts true \
    --deployment-runtime-class none \
    --bid-price-strategy scale \
    --bid-price-cpu-scale 0.01 \
    --bid-price-memory-scale 0.0025 \
    --bid-price-storage-scale 0.0001 \
    --bid-deposit 5000000uakt \
    --cluster-node-port-quantity 1000 \
    --cluster-public-hostname praetor.ingress.dcnorse.ddns.net
else
  echo "providerleasedips CRD does not exist."
fi

RPC data

akash@akash0001:~$ export AKASH_NODE="http://$(kubectl -n akash-services get ep akash-node-1 -o jsonpath='{.subsets[0].addresses[0].ip}'):26657"
akash@akash0001:~$ akash status | jq
{
  "NodeInfo": {
    "protocol_version": {
      "p2p": "8",
      "block": "11",
      "app": "0"
    },
    "id": "a5a3681d5b0eb4113fb7f0e49c232d3b5bf9ac15",
    "listen_addr": "tcp://<IP_ADDRESS>:26656",
    "network": "akashnet-2",
    "version": "0.34.21",
    "channels": "40202122233038606100",
    "moniker": "mynode-1",
    "other": {
      "tx_index": "on",
      "rpc_address": "tcp://<IP_ADDRESS>:26657"
    }
  },
  "SyncInfo": {
    "latest_block_hash": "AC7F21DF7E475AF024032B33560923BF7A9167D123404EBB0EE0A7AC23A76CE9",
    "latest_app_hash": "02458E4AD6AED6A0053CF140F0127F5529201726D2A50B640969EFD16A6A8689",
    "latest_block_height": "9677225",
    "latest_block_time": "2023-02-07T14:20:09.753680427Z",
    "earliest_block_hash": "CA92F75948827E514D164759437916D2D0E95D232D28C2806C74A6760B6E6200",
    "earliest_app_hash": "EE69204214E2FD9DD3E42B58E22DF190E51611DC59B575E22E46BBAB71044948",
    "earliest_block_height": "9446251",
    "earliest_block_time": "2023-01-22T08:28:50.740942432Z",
    "catching_up": false
  },
  "ValidatorInfo": {
    "Address": "9247B0A73F6EAEF75F81945725A6D03119E5036C",
    "PubKey": {
      "type": "tendermint/PubKeyEd25519",
      "value": "J0c9H4w9KfEs6cBiGt4CoIb2so8d7CqH0K6GvQC8Tc8="
    },
    "VotingPower": "0"
  }
}

I've tmate-ed to his provider, have tried deploying my app there (dseq 9677551) and restarting akash-provider after that => no issues. :man_shrugging:

Issue Overview:
This issue reoccurred on the Hurricane provider, running akash-provider 0.6.5-rc6.
A total of 44 leases (worth noting - not all of them) were closed simultaneously. For detailed analysis, let's focus on dseq 18728134.
Relevant Logs:

Error: lease query failed followed by err=(MISSING)

Explore-logs-2024-11-25 11_45_41.txt

Deployment was removed at 2024-11-25|01:05:55.661:
2024-11-25 02:05:55.720 {"log":"2024-11-25T01:05:55.703] shutting down module=provider-cluster cmp=deployment-manager lease=akash1z6ql9vzhsumpvumj4zs8juv7l5u2zyr5yax2ys/18728134/1/1/akash15tl6v6gd0nte0syyxnv57zmmspgju4c3xfmdhk"}
2024-11-25 02:05:55.661 {"log":"2024-11-25T01:05:55.661] lease query failed module=provider-cluster cmp=deployment-manager err=(MISSING)"}

More logs for this lease: Explore-logs-2024-11-25 11_21_30.txt

Pod Restart Analysis:

NOTE: During the initial line of logs (provider-services in provider mode), the message using in cluster kube config was noted consistently as expected after the akash-provider pod restart.

Third Provider Pod Restart: Triggered by an account sequence mismatch error.

Only one restart of this kind occurred within the past 24 hours.

Two Other Restarts: Reason unknown, occurred approximately 40 minutes prior to the third restart.

Both were closely timed, with minimal intervals between them.

Error Context:

Error Leading to Deployments Shutdown:
couldn't check lease balance. retrying in 1m module=provider cmp=balance-checker leaseId=akash1qh0f0h7jlq4x5gpxghrxvps5l09y7uuvcumcyd/18084950/1/1/akash15tl6v6gd0nte0syyxnv57zmmspgju4c3xfmdhk

Subsequent logs indicate failed attempts to query open orders and deployments shutdown cascade:

Example:2024-11-25 01:05:55.703 finding existing orders err="post failed: Post \"http://akash-node-1:26657\": EOF"
2024-11-25 01:05:55.703 shutting down module=provider cmp=balance-checker

Impact:

Akash Provider entered shutdown mode.
All Akash deployments in Kubernetes were removed.
However, no lease close actions (on the Akash Blockchain) were triggered for any of the affected leases.

Logs by Restart Timing:

First Provider Pod Restart (leading to deployment removals):

2024-11-25|01:05:4
2024-11-25|01:05:5

Second Provider Pod Restart (no issues such as deployments being closed observed):

2024-11-25|01:06:3

Preliminary Conclusion:
The root cause appears to stem from the cascading effects of:

lease query failed: Leading to missing lease information.
Balance Checker Errors: Resulting in unfulfilled balance checks and retrials.
Deployments Shutdown Cascade: Akash Provider erroneously removed Akash deployments (from K8s) without issuing lease close transactions on the Akash Blockchain.

Further investigation is required to determine:

The reason for the err=(MISSING) in lease queries.
The root cause of the unexpected pod restarts ~40 minutes before the critical shutdown. So far there

Further investigation is required to determine:

The reason for the err=(MISSING) in lease queries. (My guess based on the logs, the reason is likely the intermittent communication issues of akash-provider with akash-node (via RPC)).
The root cause of the unexpected pod restarts ~40 minutes before the critical shutdown. (This potentially could be caused by the intermittent issues with the RPC pod where the health check would trigger provider pod restart)

I can confirm my earlier assumption: there was indeed an intermittent issue with the RPC. Upon searching for relevant error messages, I found RPC node sync check failed in the provider logs.

The logs: Explore-logs-2024-11-25 12_45_42.txt

@troian The Akash Provider should not assume deployments are absent simply due to RPC query failures or issues with the RPC itself. It should be designed to handle intermittent communication or RPC disruptions more resiliently without removing the existing deployments from K8s.

The same issue occurred again on the Hurricane provider :/
Logs 2.log

Side note: I've opened a discussion to what might be a potential contributor (not the root cause) to this issue https://github.com/orgs/akash-network/discussions/760


Internal server error in you new version !!!! :-(((

I'm just updated to your new version and my site is dead :-(
Class 'CSSmin' not found
I returned to version 1.14.4 and all ok

Update dependencies. Package mrclay/minify should be upgraded to version 3.0

in my composer.json
...
"rmrevin/yii2-minify-view": "^1.15"
...

composer update
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 8 installs, 2 updates, 0 removals

Installing tubalmartin/cssmin (v3.3.1): Loading from cache
Installing pimple/pimple (dev-master 93ec38f): Cloning 93ec38f1df from cache
Installing psr/container (dev-master b7ce3b1): Cloning b7ce3b1764 from cache
Installing container-interop/container-interop (1.2.0): Loading from cache
Installing mrclay/props-dic (2.2.0): Loading from cache
Installing monolog/monolog (1.x-dev 35c07a8): Cloning 35c07a81de from cache
Installing intervention/httpauth (2.0.2): Loading from cache
Installing mrclay/jsmin-php (2.3.2): Loading from cache
Updating mrclay/minify (2.x-dev a36e201 => dev-master 79e5a22):  Checking out 79e5a22321
Updating rmrevin/yii2-minify-view (1.14.4 => 1.15.0): Loading from cache
monolog/monolog suggests installing aws/aws-sdk-php (Allow sending log messages to AWS services like DynamoDB)
monolog/monolog suggests installing doctrine/couchdb (Allow sending log messages to a CouchDB server)
monolog/monolog suggests installing ext-amqp (Allow sending log messages to an AMQP server (1.0+ required))
monolog/monolog suggests installing graylog2/gelf-php (Allow sending log messages to a GrayLog2 server)
monolog/monolog suggests installing mongodb/mongodb (Allow sending log messages to a MongoDB server via PHP Driver)
monolog/monolog suggests installing php-amqplib/php-amqplib (Allow sending log messages to an AMQP server using php-amqplib)
monolog/monolog suggests installing php-console/php-console (Allow sending log messages to Google Chrome)
monolog/monolog suggests installing rollbar/rollbar (Allow sending log messages to Rollbar)
monolog/monolog suggests installing ruflin/elastica (Allow sending log messages to an Elastic Search server)
monolog/monolog suggests installing sentry/sentry (Allow sending log messages to a Sentry server)
Package rubaxa/fileapi is abandoned, you should avoid using it. No replacement was suggested.
Writing lock file

So,  mrclay/minify updated

But you are using an unstable version of the package. In production projects, you should use only stable versions. Add the line "minimum-stability": "stable" to composer.json

Thank you !!!

I'm glad I could help. Good luck.


Fix potential unused-parameter error in GCC code generated by fastrtp…

Generated serializeKey() functions that have an empty body could produce the error.

Hey @scherererer !
Thanks for this, but we already did it on commit 4724e919d7b19b5b5e5448ffb559eaab514c45c7

Thanks, closing because of fix in 4d5f197


ScopeParamShapeError incorrect order of value and initializer shapes

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 20.04
Flax, jax, jaxlib versions (obtain with pip show flax jax jaxlib: jax==0.4.5, jaxlib==0.4.4, flax==0.6.6
Python version: 3.10
GPU/TPU model and memory: N/A
CUDA version (if applicable): N/A

Problem you have encountered:
I was getting a ScopeParamShapeError and it took me awhile to figure out my bug because I got confused by the order of the shapes in the error message. Based on both the wording of the error and the source code, it is implied that the value shape comes first and the initializer shape second:
'Inconsistent shapes between value and initializer for parameter "{param_name}" in "{scope_path}": {value_shape}, {init_shape}.'

However, based on this minimal example, it seems that the opposite happens:
import jax
import jax.numpy as jnp
import flax.linen as nn

class Model(nn.Module):
    @nn.compact
    def __call__(self, x):
        return nn.Dense(1)(x)

model = Model()
params = model.init(jax.random.PRNGKey(0), jnp.ones(5))["params"]
model.apply({"params": params}, jnp.ones(3))

# ScopeParamShapeError: Inconsistent shapes between value and initializer for parameter "kernel" in "/Dense_0": (5, 1), (3, 1).

Unless I've got this completely wrong somehow, it really seems like (5, 1) is the initializer shape and (3, 1) is the value shape.

Generally all Flax layers are "batch agnostic", meaning you can pass 0 or more batch dimensions. If it helps, imagine you are passing the shapes (1, 5) and (1, 3).

Generally all Flax layers are "batch agnostic", meaning you can pass 0 or more batch dimensions. If it helps, imagine you are passing the shapes (1, 5) and (1, 3), Dense only cares about the last dimensionh

Yes, but I'm passing 0 batch dimensions in both cases. The dense layer kernel has shape (n, 1) where n is determined at initialization time by looking at the last dimension of the example input. In this example, n=5 at initialization time and n=3 at "apply" time, but the error message reports the opposite.

Here is how the error is generated:
super().__init__('Inconsistent shapes between value and initializer ' f'for parameter "{param_name}" in "{scope_path}": ' f'{value_shape}, {init_shape}.')

We can improve the error message to make it a bit more clear which shape is expected (init_shape) and which shape was produced (value_shape).

After looking at the code, you are right! It's reporting the opposite. I think we should improve the error message altogether to make it very clear what shape is expected and what shape was produced.

@chiamp you want to take a loot at this?

Let me know if #2947 works!


Upload failed, TypeError: Espruino.transform is not a function

After updating to espruino_2v05.82_banglejs.zip uploading any app to the Bangle.js via the AppLoader fails with the error message Upload failed, TypeError: Espruino.transform is not a function. This makes the Bangle.js effectively unusable.
Steps to reproduce:

Flash espruino_2v05.82_banglejs.zip
Afterwards, Connect via the AppLoader
Choose About -> Install Default Apps
This will fails with "Unknown Error"
The Bangle.js now contains 0 Apps
Attempt to upload any App from the Library
Observe error message noted above

It's not 2v05.82 specific. I'm seeing the same on 2v05.73, although I haven't installed Default Apps. I just wanted to update the bootloader to v0.17.

@gfwilliams I am getting the same error as OP.
"Removing all apps" works, but then the process fails with the "Espruino.transform" error.

Checking espruinotools.js and it seems the function "Espruino.transform()" is added all the way at the end of the file. This seems to make it miss being included in the final Espruino object. The function declaration looks out of place; could something have gone wrong with the compilation?

This could be related to the fixes done for https://github.com/espruino/BangleApps/issues/416

Damn, sorry - that'll teach me for pushing 'minor' changes at night. I'll get it sorted now

Just fixed. Please can you try now?

I have just tested uploading apps on the dev version of BangleApps and the issue persists.
I did not perform any firmware update or anything else.

What about https://banglejs.com/apps/ ? Sometimes GitHub tends to cache things for a while.

Just to add - you shouldn't need a firmware update or anything - it was purely an app loader issue

"Install Default Apps" finished without error and the Bangle works again.
Is there any functional difference between the app loader on github.io and on banglejs.com?

Phew, that's great - thanks!

Is there any functional difference between the app loader on github.io and on banglejs.com?

The one on banglejs.com can sort by newest/recently updated, but that's it.
Supposedly the github.io one is the newest, but because I can control banglejs.com and I disable caching, if I've pushed some code change right out to both at the same time, chances are it'll hit banglejs.com first - but only by a few minutes

Confirming with a quick test in the console of https://banglejs.com/apps/ that "Espruino.transform()" is back. Thank you @gfwilliams


In Linux, ps -e used in make stop task produces only the process name…

… without the argument. Should use ps -ef.
Summary
In Linux, ps -e used in make stop task produces only the process name without the argument. Should use ps -ef.
Ticket Link
Resolves #1359
Checklist
N/A
Device Information
N/A
Screenshots
N/A

On my side still not working. When I ran make build-android command.

@kumarrahul-rkv you are using a very old version of npm please upgrade and try again.
In the docs you’ll find the recommended version


How to map the DSN during authentication and the serialnumber on the Alexa APP

Hi,
As you know, we provided the DSN(device serial number) during LWA authentication, But when we check the device on the alexa app, there is another serial number displayed.  These 2 serial numbers are totally different.
But the problem is when our customers report issue, they always report the serial number that displayed on the alexa app. We need to find a way to translate this serialnumber into the DSN we provided, so that we can locate the real device.
So is it possible for provide the mapping method to us?
Thanks

Hello subjectxbj,
That is a very good question.  I do not know off-hand of a way to do that but will see if there is a way for us to do it.  Do you need this for just one instance - or are you looking for a tool you can use on an as needed basis?
Thank you,
-SWH

I need a tool or a script, that take the serialnumber as input and output the DSN. Or you can give me a link on how this should do, then I can write a script to implement that.
Thanks,
Arthman

Could I also get an update on this?

Hello subjectxbj and sey2kim,
I have asked around, and I am sorry to say that there is no public interface or tool with which to perform this mapping.
This sounds like a great feature request.  You can post such feature requests here: https://www.amazon.com/forms/231ff404-261e-454c-917d-97208d9ea268
Thank you,
-SWH


Secrets do not reflect their new value after being updated in KeyVault

Secrets do not reflect their new value after being updated in KeyVault

@Lucasfernandez19 sorry for late reply. This will be the new future. Do you have any contribution ?
Best.

@Lucasfernandez19 sorry for late response. It is now supported with 1.0.7 version.


"Resource not accessible by integration" (OSOE-407)

We have this PR where the "Resource not accessible by integration" error comes up.

Maybe this could be related to the issue listed here: https://github.com/actions/first-interaction/issues/10#:~:text=this happens as soon as the person creating the pr does not have permission to the repository
Jira issue

Did anybody see this happening more than once?

We'll get back to this once it happens more than once.

So, this happens if you open a PR from a fork. Then, if the workflow was triggered by pull_request (and not pull_request_target) the run won't have write access to the PR, thus it won't be able to comment or label it either. This fails the Test Report step. I'll look into adding a permission check, so the step is not executed if the current run only has read permissions.
pull_request_target could be used but that gives blanket write access to the run, which has its own issues.
https://github.com/actions/labeler/issues/12 also has a lot of useful info.

Am stuck on this: https://github.com/orgs/community/discussions/37395 I'll also check out if there's a way to detect if the run is for a fork PR, since that's the same thing for us.

FYI @DAud-IcI OCC will get this once merged.

In a nutshell:

pull_request_target is a bad boy because of its execution context related security risk
some actions, where the given action requires an elevated access level (this is the problem with the forked repo and the root cause of "Resource not accessible by integration") are started conditionally if the PR event is not triggered from a forked repo. Finally, eg. the Merge conflict label does not come up in a PR of a forked repo.

Right? Or I’m in the wrong direction.

Yes, except for “Finally, eg. the Merge conflict label not comes up in a PR of a forked repo.” Even if you submit a PR for a branch in a fork, if it becomes conflicted, the notifying comment and label will be added (since that runs in the context of a push to the target branch, not the fork, so it has write permissions, just as PRs opened for branches within the repo). What won’t happen is the removal of the label when the merge conflict is resolved.


Some methods of slave.go are implemented

Some methods of slave.go are implemented

Don't use nil when err occurs. GRPC communication will cause a bug when use nil. It can be changed into an empty structure

Don't use nil when err occurs. GRPC communication will cause a bug when use nil. It can be changed into an empty structure↳

corrected


[WinAppSDK 1.5] Roll back build image to VS 17.9

Our build image recently got updated to VS 17.10, which caused some changes and broke a few unit tests. This change rolls our image back to a previous version, that contains VS 17.9.
This is the "1.0.02629.40" image, described on this page:
https://eng.ms/docs/products/onebranch/infrastructureandimages/buildinfrastructureandimages/containerimages/windowsimages/windows2019vse2022/releasenotes

/azp run

Public PR is failing but it is validated here
https://microsoft.visualstudio.com/ProjectReunion/_build/results?buildId=107553706&view=results


add user passthrough column to users model and update dependencies

PR Overview
This PR will address the following Issue/Feature:
https://github.com/fivetran/dbt_iterable/issues/43
and internal ticket
This PR will result in the following new package version: v0.11.1

Non breaking as the default config for event_extension is still true so existing users won't see any changes. And the passthrough columns only add columns, instead of deleting or modifying existing ones.
Please provide the finalized CHANGELOG entry which details the relevant changes included in this PR:

Bug Fixes

Introduces variable iterable__using_event_extension to disable the event_extension table and exclude its fields from persisting downstream. This allows the downstream models to run even if the source event_extension table does not exist. For more information on how to configure the iterable__using_event_extension variable, refer to the README.
Persists user_history passthrough columns as stipulated via the iterable_user_history_pass_through_columns variable through to the iterable__users model. For more information on how to configure the iterable_user_history_pass_through_columns variable, refer to the README.

Under the Hood

Addition of integrity and consistency validation tests within integration tests pertaining to the iterable__user_unsubscriptions model.
Updated seed data to ensure proper testing of the latest v0.8.1 dbt_iterable_source release.
Updated pull request and issue templates.
Included auto-releaser GitHub Actions workflow to automate future releases.

PR Checklist
Basic Validation
Please acknowledge that you have successfully performed the following commands locally:

[x] dbt run –full-refresh && dbt test
[x] dbt run (if incremental models are present) && dbt test

Before marking this PR as "ready for review" the following have been applied:

[x] The appropriate issue has been linked, tagged, and properly assigned
[x] All necessary documentation and version upgrades have been applied
[x] docs were regenerated (unless this PR does not include any code or yml updates)
[x] BuildKite integration tests are passing
[x] Detailed validation steps have been provided below

Detailed Validation
Please share any and all of your validation steps:

Variables tried:
    iterable_user_history_pass_through_columns:
      - name: phone_number_line_type
        alias: phone_digits
      - name: additional_properties
    iterable_event_extension_pass_through_columns:
      - name: browser_token
    iterable__using_event_extension: true
#    iterable__using_event_extension: false

If you had to summarize this PR in an emoji, which would it be?

:dancer:

will regen docs upon approval

Hi @fivetran-reneeli ! Thanks for addressing all the additional comments! This looks good to go.
 My initial recommendation was to add the additional incremental run script after the full refresh. But my last suggestion in Github did indeed remove it. Sorry, that line should remain unchanegd.
Can you test this configuration in Buildkite that runs a full-refresh, then an incremental run, and see if this works:
dbt run --vars '{iterable__using_campaign_label_history: false, iterable__using_user_unsubscribed_message_type_history: false, iterable__using_campaign_suppression_list_history: false, iterable__using_event_extension: false}' --target "$db" —full-refresh

dbt run --vars '{iterable__using_campaign_label_history: false, iterable__using_user_unsubscribed_message_type_history: false, iterable__using_campaign_suppression_list_history: false, iterable__using_event_extension: false}' --target "$db"

Thanks @fivetran-avinash yeah I had figured this was what you meant and I tried that in this commit, while it failed I think it's because I didn't add the vars the second time around. Just pushed this and should be good. Appreciate your review!!

@fivetran-reneeli thanks for working through these changes. Please see my comments below to address before this will be ready for release approval.
Additionally, I noticed that dbt test fails if you have set iterable__using_event_extension to false. This is because in the yml where we define the tests we are still including experiment_id and not catching if the variable is turned on/off.

I recommend it would probably be best to create a surrogate key in the model that defines the uniqueness of the end model (like here in our netsuite model) and make that surrogate key dynamic so we can then test that field in the yml (like we have done here for the same netsuite model).
Lastly, I know this is out of scope for this task, but would you be able to create an issue for us to explore the iterable__events incremental logic. I did an integrity test on our internal data (albeit our internal data may be incomplete and not emulate a customer environment) and found that the row count for the iterable__events model does not match the row count of the stg_iterable__event model following an incremental run (this is present in both dev and prod). It would be great for us to proactively create a ticket for us to explore this in a future update.

Thanks @fivetran-joemarkiewicz  for catching-- I removed experiment_id from anywhere it was included in a unique test and instead created a surrogate key in those models (iterable__user_campaign and iterable__campaigns).
Hmm strange about the row counts-- will make issue for that


Update manifestival to 0.4.0

/lint
Proposed Changes

Dependency update for manifestival to 0.4.0

Release Note
NONE

/assign @n3wscott

/approve
/lgtm

/retest

/check-cla


sdk creates trade but transaction doesn't happen

it seems to retrieve tokens successfully and my balance from kovan testnet. but I can't see the transaction in my metamask wallet.

Is there an additional function that I need to use to confirm the transaction?

Hey yes you need to send the transaction using web3 or ethers have you used those frameworks before? Within the trade it has a transaction object which you need to send to execute the trade. Also you need to make sure the approvalTransaction if defined is set first to be able to approve uniswap to move your tokens on your behalf. I was thinking maybe in the readme if I did an example of how you could do this with web3 and ethers it may help people understand a bit more.

This isn’t a bug so will close the issue as your not executing the trade using your own web3 or ethers instance. Can carry on the chat and I can help you understand what your missing.

Thanks a lot for your quick reply and your efforts on creating this module Josh. You are right this is not really a bug, I am just willing for discovering this sdk. I am using ethers.js instance and what I want to do is swap tokens like swapExactTokensForTokens contract of uniswap. This code below doesn't raise an error but it also doesn't do the job.
const { UniswapPair, ChainId, UniswapVersion, UniswapPairSettings,  TokenFactoryPublic } = require('simple-uniswap-sdk');
const ethers = require('ethers');
const uniswapPair = new UniswapPair({
// the contract address of the token you want to convert FROM
fromTokenContractAddress: '0x4f96fe3b7a6cf9725f59d353f723c1bdb64ca6aa',
// the contract address of the token you want to convert TO
toTokenContractAddress: '0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984',
// the ethereum address of the user using this part of the dApp
ethereumAddress: '0xe1878181fBb2B38492a06246875d507895Eb5bb7',
chainId: ChainId.KOVAN,
providerUrl: 'https://kovan.infura.io/v3/INFURA_ID',
settings: new UniswapPairSettings({
slippage: 0.005,
deadlineMinutes: 20,
disableMultihops: false,
uniswapVersions: [UniswapVersion.v2, UniswapVersion.v3],
}),
});
// now to create the factory you just do
async function calis(){
const uniswapPairFactory = await uniswapPair.createFactory();
const trade = await uniswapPairFactory.trade('0.00005');
const provider = new ethers.providers.JsonRpcProvider('https://kovan.infura.io/v3/INFURA_ID');
const wallet1 = new ethers.Wallet(PRIVATE_KEY, provider);
trade.transaction.gasLimit = 600000;
trade.transaction.gasPrice = ethers.utils.parseUnits(10, 'gwei');
console.log(trade);
wallet1.sendTransaction(tx);
trade.destroy();
};
calis();
const { UniswapPair, ChainId, UniswapVersion, UniswapPairSettings,  TokenFactoryPublic } = require('simple-uniswap-sdk');
const ethers = require('ethers');
const uniswapPair = new UniswapPair({
// the contract address of the token you want to convert FROM
fromTokenContractAddress: '0x4f96fe3b7a6cf9725f59d353f723c1bdb64ca6aa',
// the contract address of the token you want to convert TO
toTokenContractAddress: '0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984',
// the ethereum address of the user using this part of the dApp
ethereumAddress: '0xe1878181fBb2B38492a06246875d507895Eb5bb7',
chainId: ChainId.KOVAN,
providerUrl: 'https://kovan.infura.io/v3/INFURA_ID',
settings: new UniswapPairSettings({
slippage: 0.005,
deadlineMinutes: 20,
disableMultihops: false,
uniswapVersions: [UniswapVersion.v2, UniswapVersion.v3],
}),
});
// now to create the factory you just do
async function calis(){
const uniswapPairFactory = await uniswapPair.createFactory();
const trade = await uniswapPairFactory.trade('0.00005');
const provider = new ethers.providers.JsonRpcProvider('https://kovan.infura.io/v3/INFURA_ID');
const wallet1 = new ethers.Wallet(PRIVATE_KEY, provider);
trade.transaction.gasLimit = 600000;
trade.transaction.gasPrice = ethers.utils.parseUnits(10, 'gwei');
console.log(trade);
wallet1.sendTransaction(tx);
trade.destroy();
};
calis();

Thanks a lot for your quick reply and your efforts on creating this module Josh. You are right this is not really a bug, I am just willing for discovering this sdk. I am using ethers.js instance and what I want to do is swap tokens like swapExactTokensForTokens contract of uniswap. This code below doesn't raise an error but it also doesn't do the job.
const { UniswapPair, ChainId, UniswapVersion, UniswapPairSettings,  TokenFactoryPublic } = require('simple-uniswap-sdk');
const ethers = require('ethers');
const uniswapPair = new UniswapPair({
// the contract address of the token you want to convert FROM
fromTokenContractAddress: '0x4f96fe3b7a6cf9725f59d353f723c1bdb64ca6aa',
// the contract address of the token you want to convert TO
toTokenContractAddress: '0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984',
// the ethereum address of the user using this part of the dApp
ethereumAddress: '0xe1878181fBb2B38492a06246875d507895Eb5bb7',
chainId: ChainId.KOVAN,
providerUrl: 'https://kovan.infura.io/v3/INFURA_ID',
settings: new UniswapPairSettings({
slippage: 0.005,
deadlineMinutes: 20,
disableMultihops: false,
uniswapVersions: [UniswapVersion.v2, UniswapVersion.v3],
}),
});
// now to create the factory you just do
async function calis(){
const uniswapPairFactory = await uniswapPair.createFactory();
const trade = await uniswapPairFactory.trade('0.00005');
const provider = new ethers.providers.JsonRpcProvider('https://kovan.infura.io/v3/INFURA_ID');
const wallet1 = new ethers.Wallet(PRIVATE_KEY, provider);
trade.transaction.gasLimit = 600000;
trade.transaction.gasPrice = ethers.utils.parseUnits(10, 'gwei');
console.log(trade);
wallet1.sendTransaction(tx);
trade.destroy();
};
calis();

Hey do you get any errors? wallet1.sendTransaction is a promise so you should await it to not swallow any errors? ethers normally tell you what is wrong? I will extend the docs to include ethers + web3 examples of usage but your code looks fine. This looks more of an issue with your ethers awaiting stuff. If you give me some more details il happy to look at you.

you also need to make sure you check that uniswap can move your tokens on your when using erc20 > eth/erc20! il update the readme with full examples which hopefully makes it clearer!

I have added some docs inline with ethers and web3 showing how you would hook it in - https://github.com/uniswap-integration/simple-uniswap-sdk#ethers-example hope this clear any issues up!

Hey thanks a lot for adding this example into documentation.
I am using your setup on Rinkeby provider forked by ganache-cli. Trade function raises <UnhandledPromiseRejectionWarning: Unhandled promise rejection.>  error even tough I am using await, as you have suggested.

Can you remove your provider url and see if it works. I’m not sure if ganache rinkeby local had the same uniswap contract addresses


After 7.22.32 upgrade, the application enters an infinite loop and constantly performs sw unregister and register.

Issue and Steps to Reproduce
After the latest version, the application enters an infinite loop and constantly performs sw unregister and register.
I guess this bug related with this commit: https://github.com/AxaFrance/oidc-client/commit/cc731c15f1d72ce4d21a7958ca15128ae1dcdd89
@guillaume-chervet  please help for this, thanks.
Versions
7.22.32

Hi @ozanmanav , did you update the service worker file to synchronize you app version?
This version is in production on my side whithout any problem.

It seems resolved with latest version, thanks!


chore: add snapshots for toggle type widgets

/ok-to-test<EMAIL_ADDRESS>

[!CAUTION]
🔴 🔴 🔴 Some tests have failed.
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/9692797550
Commit: c5bba8fc4a8550ed82cadff05b1789c4517c9739
Cypress dashboard.
Tags: @tag.Anvil
The following are new failures, please fix them before merging the PR:
cypress/e2e/Regression/ClientSide/Anvil/Widgets/AnvilCheckboxGroupWidgetSnapshot_spec.ts
cypress/e2e/Regression/ClientSide/Anvil/Widgets/AnvilCheckboxWidgetSnapshot_spec.ts
cypress/e2e/Regression/ClientSide/Anvil/Widgets/AnvilCurrencyInputWidgetSnapshot_spec.ts
cypress/e2e/Regression/ClientSide/Anvil/Widgets/AnvilInputWidgetSnapshot_spec.ts
cypress/e2e/Regression/ClientSide/Anvil/Widgets/AnvilPhoneInputWidgetSnapshot_spec.ts
cypress/e2e/Regression/ClientSide/Anvil/Widgets/AnvilRadioGroupWidgetSnapshot_spec.ts
cypress/e2e/Regression/ClientSide/Anvil/Widgets/AnvilSwitchGroupWidgetSnapshot_spec.ts
cypress/e2e/Regression/ClientSide/Anvil/Widgets/AnvilSwitchWidgetSnapshot_spec.ts
List of identified flaky tests.

Summary by CodeRabbit

New Features

Introduced snapshot tests for various Anvil widgets (Checkbox, Checkbox Group, Radio Group, Switch, Switch Group) in different modes (Canvas, Preview, Deploy).

Enhancements

Added a lineClamp prop to the Label component, improving text display behavior.
Added an isSelected prop to the WDSSwitchWidget, enhancing widget rendering logic.

Tests

Implemented new test cases for Anvil widgets to ensure functionality and state consistency across different modes.

/build-deploy-preview skip-tests=true

Merged here.


[Update Request]: Voidtool's Everything Lite

What type of update are you requesting?
A new locale, architecture, or installer type of an existing version
Current Package Identifier
voidtools.Everything.Lite
Package Version
<IP_ADDRESS>6
Please describe the changes you would like to see
The wrong installer is linked to Everything Lite. The correct installer should have "Lite" in the file name.
Link: https://www.voidtools.com/Everything-<IP_ADDRESS>6.x64.Lite-Setup.exe
SHA256: 2f3e5c06bf84845ad1e9b2626fbe1217dc08301f2c853c9485d09f20272e0e84

Close with reason: Resolved by #166062;


Fix folder deletion in blob containers so all files get deleted

Fixes #1028 and potentially #982

@motm32 can you reproduce #982 before making this change? And does this change seem to fix it?

@alexweininger I can only reproduce #982 before making this change if there are more than 50 files in the folder. Once the change is made the folder disappears as expected once the blob container is refreshed after deleting the folder completely.


Measure not exporting nested Symbols (including typography, buttons etc)

A lot of nested symbols (including varying typography, buttons etc) aren't showing up in the measure export.
Is there something I'm doing wrong here?

Duplicated with #400 fixed with update 2.7.2

I still have this problem - I need to detach all symbols to get them measurable in html preview.
Sketch version: 49.3, MacOS: HighSierra 10.13.3 (17D47)


Issue connecting gazebo in SITL

Hi all,
I'm trying to install a gazebo simulation on a new computer. I've got it running on a laptop without problems, other than it's quite heavy. I tried to copy the setup to the new pc:
ubuntu 14.04
ros jade
gazebo 6.6
I'm using the manual start of the firmware, "no_sim=1 make posix_sitl_default gazebo", this shows the correct output. When i then launch gazebo with the copter, the px4 terminal starts outputting:
"INFO  [platforms__posix__px4_layer] simulator is slow. Delay added: 193687 us"
multiple times a second.
On the laptop I'm running a slightly old version of the firmware, I tried both that version as well as the newest version of the firmware (editing my .bashrc file accordingly), both resulting in the same behaviour.
Whereas on the laptop the gazebo simulation is slowed down to around 0.8, it shows 1.0 on the pc, so computer power doesn't seem to be the problem. I've seen a couple of similar problems, but none of the suggested fixes apply. Any ideas I could try?

I'm assuming make posix gazebo works for you?

Hi Lorenz,
Running the standard simulation does indeed work. Its when running the modified sdf model that it doesn't. Undoubtly it has something to do with the setup of either plugins or dependencies on the desktop. Gazebo does load the correct model, and gives the same terminal output as on the working laptop (showing the sitl plugins are loaded and supposedly publishing).
Thanks for your help.

For anyone running into this issue as well:
I found the fix by renaming imuSubTopic from "imu" to "/imu", apperently "imu" does not always work.


Remove cpf mask from moip form

This pr aim to remove cpf mask from moip form.

Coverage remained the same at 81.355% when pulling 992deff4421f20c4e99cb4d9deaec8c465dee76a on cpf-mask into ae221d21cafb729172da9cf1e701fc320cd558cd on master.

Não entendi pra que replicar esse form gerado pelo moip?

@andrezacm Tentei escrever em JS pra mudar a mask do campo, porém a gem ia e reescrevia esse JS. Dessa forma tenho liberdade pra alterar qualquer coisa nesse formulário, pq ele sobrescreve o form da gem, com isso a proxima task de retirar esse campo de cpf vai ficar bem mais facil, não vai precisar fazer o fork da gem e altera-la posso ir direto nesse form.

Coverage remained the same at 81.355% when pulling e598f05d40547ced5fc9cf3a7716273de56a0793 on cpf-mask into 9613e57b1a337f5b23826a497e1237a4ed2e4dc9 on master.

Coverage remained the same at 81.355% when pulling 6c8bb3c0709a07e7cbfab7a352daf4bd66550220 on cpf-mask into 9613e57b1a337f5b23826a497e1237a4ed2e4dc9 on master.

Coverage remained the same at 81.355% when pulling 303db60dbce9d456e2f1ef556fa97a8fef70faa8 on cpf-mask into 9613e57b1a337f5b23826a497e1237a4ed2e4dc9 on master.

Coverage remained the same at 81.435% when pulling 616e4dac6de1d613629867d5d739577c3162160a on cpf-mask into 1dd0ed576f56948eb5f7d65ace5f55108f58d8d2 on master.

Coverage remained the same at 81.435% when pulling 616e4dac6de1d613629867d5d739577c3162160a on cpf-mask into 1dd0ed576f56948eb5f7d65ace5f55108f58d8d2 on master.

Coverage remained the same at 81.435% when pulling 0c16281d589713272e16ea16bc27bd897a355e42 on cpf-mask into 1dd0ed576f56948eb5f7d65ace5f55108f58d8d2 on master.

Coverage remained the same at 81.435% when pulling 93cd0f123c9bc531822684513be976b5888beaf9 on cpf-mask into 1dd0ed576f56948eb5f7d65ace5f55108f58d8d2 on master.

Coverage remained the same at 81.435% when pulling c0e29e455a57519faeec0c22728d22551669a4fc on cpf-mask into 1dd0ed576f56948eb5f7d65ace5f55108f58d8d2 on master.

Coverage remained the same at 81.435% when pulling 958b1a9331e3df33dd974e39b36f44115ba006f0 on cpf-mask into 1dd0ed576f56948eb5f7d65ace5f55108f58d8d2 on master.

Coverage remained the same at 81.435% when pulling 8cfe8468dc2513271e1fa2633443971302625e91 on cpf-mask into 1dd0ed576f56948eb5f7d65ace5f55108f58d8d2 on master.

Coverage remained the same at 81.435% when pulling 021f42f2cb5715ad881741967c113663056dc07c on cpf-mask into 1dd0ed576f56948eb5f7d65ace5f55108f58d8d2 on master.

Coverage remained the same at 81.435% when pulling 09d74dce76eb2f4e275140f449551c193a8299a1 on cpf-mask into 1dd0ed576f56948eb5f7d65ace5f55108f58d8d2 on master.

Coverage remained the same at 81.435% when pulling 5f28ff20034c7cfe985cd3d102b4658cbacb6c9c on cpf-mask into 1dd0ed576f56948eb5f7d65ace5f55108f58d8d2 on master.

Coverage remained the same at 81.435% when pulling 2ccd2455e00284a2de5f83288f4fc3ba11122531 on cpf-mask into 1dd0ed576f56948eb5f7d65ace5f55108f58d8d2 on master.


A tensor field that specifies hnsw index parameters must also specify…

… 'index' in 'indexing'.
@bratseth please review
@jobergum FYI

No, we are not sure about that. But without this validation, you can deploy an application thinking you are using an hnsw index when you are not. So it is better to fail at deploy time so the application can be fixed.

I will have a go at existing apps

Yes, I agree that this needs to be validated at deploy time. The problem is that if there are existing apps with this issue the rollout to production will be blocked and we cannot get new releases out until the customer has fixed the application or we have rolled back infrastructure to previous version manually.
There is an internal ticket 'Allow for "warn-only" config validations' that is related to this.


HLL allocator

Pull Request Test Coverage Report for Build 532130414

214 of 244 (87.7%)  changed or added relevant lines in 25 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.5%) to 94.334%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

hll/include/HllSketch-internal.hpp
2
3
66.67%

hll/include/HllUnion-internal.hpp
2
3
66.67%

tuple/include/tuple_sketch_impl.hpp
0
2
0.0%

theta/include/theta_sketch_impl.hpp
50
76
65.79%

Files with Coverage Reduction
New Missed Lines
%

theta/include/theta_sketch_impl.hpp
1
31.25%

common/include/conditional_back_inserter.hpp
3
53.85%

Totals

Change from base Build 521644039:
0.5%

Covered Lines:
4462

Relevant Lines:
4730

💛  - Coveralls


test: [NPM] Make Cyclonus Profiles Independent

Also adds non-truncated logs for every NPM pod

https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration#usage-limits
We will need to keep these limits in mind

https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration#usage-limits
We will need to keep these limits in mind

I think this limit is the only relevant one for the PR:
"Workflow run queue - No more than 500 workflow runs can be queued in a 10 second interval per repository. If a workflow run reaches this limit, the workflow run is terminated and fails to complete."
Worst case, 5 cyclonus workflows will be triggered now instead of 1.

Closing because GitHub now has a feature to rerun individual failed jobs


Porting LittleFS to internal Data flash on MCU

Background

I have an NXP MCU that uses a flash module called FlexNVM. FlexNVM can be configure for Data Flash, this Data Flash is internal to MCU.

I currently have my own file system that uses a simplistic approach to wear leavering and data storage but as the project is becoming more demanding I think LittleFS will offer greater benefit for future expansion.

Question

I want to know how I could go about porting LittleFS to work with this Data Flash?

What is the best way to come up with the optimal configuration for the parameters in lfs_configstructure?

Data Flash Specification

Size 256KBytes

Sector size 4KBytes (I can only earse a sector at a time)

The only thing you have to do is to port a block device implementation compatible with your hardware, there is no work needed on Little FS side. You can check for example https://github.com/ARMmbed/spif-driver that implements block device for SPI flash. If you remove the SPI related functions, you'll notice that it basically comes down to implement three functions : read , program and erase

Hello @umanayana ,
have u found answer of your question?
I am also going through the same thing. Please share me some reference if u got  it solved.
Thanks in adv.

@techNiv1 just found a project based on STM32F1XX. The git history is in Chinese however I think it's pretty straightforward to understand the code hierarchy. Hope it helps you to clear your thoughts.
https://github.com/hanjhu328/LittleFSForSTM32F103


always #1

Should we have a counter that counts the generated excuses and displays "The #x Programmer Excuse" instead of always writing #1 ?

I had some similar thoughts, but more in the direction of having it as an optional param...
One possibility of course would be to have the counter as default and then have the 1 (for #1) as an option.


Row locking support in Find queries

Problem
I just migrated from Sequelize and was quite a fan of Prisma for being type safe. Would Prisma be able to support SELECT FOR UPDATE row locking like Sequelize supports? Understand that Optimistic locking is preferred by Prisma but it would be great if we have the row locking mechanism too.
My problem: When multiple requests call this function concurrently, while first transaction is still processing, the subsequent transaction will see that the user is still active and do the processing again. If we could avoid it by locking the row, that would be great.
function deactivate() {
  const user = await prisma.$transaction(async tx => {
   const user = await tx.user.findUnique({ where: { id: user.id } });
   if (user.status !== 'ACTIVE') {
     throw new Error('User not active ...');
  }
  // some business processing (not long transaction)
  return tx.user.update({ where: { id: user.id } }, data: {  status: 'DELETED' });
 });

   await doAfterCommitProcessing(user);
}

Suggested solution
const user = await tx.user.findUnique({ where: { id: user.id }, lock: FOR_UPDATE });
So, the user record with specific id is locked till the transaction is completed.
Alternatives

Additional context

Yes, I too have a use case where I want racing reads to block.

Is this a duplicate of  #5983?

Yep, sounds similar but a bit ore specific maybe. Will clean up when we look at the issue in depth.

Same here.
  await prisma.$transaction(
      async (tx) => {
        let user = await tx.user.findFirst({
          where: {
            id: req.auth.userId,
          },
        });

        // update the user
        if (user) {
          const userWorkspace = await tx.userWorkspace.findFirstOrThrow({
            where: {
              userId: req.auth.userId,
              id: user.defaultWorkspaceId,
            },
          });

          workspaceId = userWorkspace.workspaceId;

          var updateUser = await tx.user.update({
            where: {
              id: req.auth.userId,
            },
            data: {
              fullName: req.body.fullName,
              email: req.body.primaryEmailAddress.emailAddress,
              auth_json: JSON.stringify(req.body),
            },
          });
        } else {
          workspaceId = "Personal";
          var userWorkspace = await tx.userWorkspace.create({
            data: {
              userId: req.auth.userId,
              label: "Personal",
              workspaceId: "Personal",
            },
          });

          let newUser = await tx.user.create({
            data: {
              id: req.auth.userId,
              fullName: req.body.fullName,
              email: req.body.primaryEmailAddress.emailAddress,
              auth_json: JSON.stringify(req.body),
              defaultWorkspaceId: userWorkspace.id,
            },
          });
        }
      },
      {
        isolationLevel: Prisma.Prisma.TransactionIsolationLevel.Serializable,
      }

Getting this error when two threads are inserting the same user, the read should to see if the user exists if another transaction is working on it.

The current work-around is to either use $rawQuery to place FOR UPDATE. Or artificially place a mutex field (typically a boolean) and select via updating the field to true (lock it) where it is false (not locked).
This is important if the activities before updating the row involves other side effects that we definitely don't want to happen if the transaction would fail.

Any news / plans regarding this feature?

Another friendly ping. I have that exact user create error. But also am trying to avoid accruing interest on a loan multiple times in the same day on a background job that might retry randomly.

Is there any plan to add "lock for update" feature to Prisma transactions?

yes, I have the same requirement, when deleting a record another request can access it which should not happen.

Potentially related:
https://github.com/prisma/prisma/issues/8580
https://github.com/prisma/prisma/issues/5983

Is there any plan to add "lock" (shared, exclusive, update... etc lock) to findXXX method?

this would be lovely

Has somebody found a work around for that while this feature is not supported yet in Prisma?

From other issues I was part of, the roadmap of Prisma is not open, and we can dream about this for years, like people are dreaming for ears about enums in litesql.


What is the use of hoodie.meta.sync.metadata_file_listing

How to use hoodie.meta.sync.metadata_file_listing? If I enable this whether get the file list from metadata for reducing s3 file list ? is it the same as variable DEFAULT_METADATA_ENABLE_FOR_READERS in HoodieMetadataConfig?  How do I enable useFileListingMetadata in HudiWriteConfig

@njalan Yes, Your understanding is correct, While doing the metadata sync it needs to list the partitions. For that it can just use the metadata table instead of file listing. When we have a large number of partitions, this can reduce the S3 file list by great instant.
During writes, as metadata table is enable by default it should use metadata table only for most of the file listing operations.

@ad1happy2go  What do you mean for  only for most of the file listing operations. is there any threshold ?

@njalan I meant there are some code paths which can still do file operations but most of them uses metadata table for that,.

@ad1happy2go  I have enabled metadata but list operation is not reduced.


New Configmaps needs to have configmapType: Parameter to be usable

Checklist

[x] Double-checked my configuration.
[ ] Tested using the latest version.
[x] Used the Emissary executor.

Summary
What happened/what you expected to happen?

I have configmaps from before 3.2.9
I can reference them in my input parameters though they lack configmap-type
New Configmaps without workflows.argoproj.io/configmap-type: Parameter don't interpolate.

What version are you running?
v3.2.9
Emissary Executor
Diagnostics

Paste the smallest workflow that reproduces the bug. We must be able to run the workflow.
Configmap
apiVersion: v1
kind: ConfigMap
metadata:
  name: retry-sample
data:
  dummy: "{}"
  dummy1: ""

Workflow
apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: retry-sample
spec:
  entrypoint: main
  templates:
    - name: main
      inputs:
        parameters:
          - name: message
            valueFrom:
              default: "hello"
              configMapKeyRef:
                name: retry-sample
                key: dummy
                optional: true
      container:
        image: docker/whalesay
        command: [cowsay]
        args: ["{{inputs.parameters.message}}"]

Referencing older configmaps that were created before 3.2.9 works but not new ones unless they have the label workflows.argoproj.io/configmap-type: Parameter
# Logs from the workflow controller:
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

# If the workflow's pods have not been created, you can skip the rest of the diagnostics.

# The workflow's pods that are problematic:
kubectl get pod -o yaml -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

# Logs from in your workflow's wait container, something like:
kubectl logs -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

Message from the maintainers:
Impacted by this regression? Give it a 👍. We prioritise the issues with the most 👍.

Non issue, this has always been required


I need to add to a multi coins

I need to add to a multi coins
Originally posted by @Jillgrand in https://github.com/Uniswap/token-list-bridge-utils/issues/12
Originally posted by @GWLTd in https://github.com/Uniswap/token-list-bridge-utils/issues/16

Grt


Add context menu support (from olga-zhuk87)

This will make it possible to integrate:
https://github.com/Templarian/ui.bootstrap.contextMenu
via template:
context-menu="options.menuOptions"

It is possible to work around by adding the menu options object as a property to the tree nodes themselves. This is especially useful if you need different context menus for different nodes, or types of nodes.


Remove all endpoints that allow to list everything (#1427)

Removed the endpoint to list all work item links. Other endpoints to list all elements are under the /<space> scope which is fine, or are about work item types/link types, which may be changed in the future. Another concern is about some redirects, which may be addressed in another issue.
Fixes #1427
Signed-off-by: Xavier Coulon<EMAIL_ADDRESS>

Codecov Report

Merging #1432 into master will decrease coverage by 0.06%.
The diff coverage is 75%.

@@            Coverage Diff             @@
##           master    #1432      +/-   ##
==========================================
- Coverage   60.32%   60.26%   -0.07%
==========================================
  Files         119      119
  Lines       11134    11123      -11
==========================================
- Hits         6717     6703      -14
- Misses       3762     3767       +5
+ Partials      655      653       -2

Impacted Files
Coverage Δ

controller/work_item_link.go
79.22% <ø> (-0.07%)
:arrow_down:

controller/work_item_relationships_links.go
66.66% <75%> (+3.03%)
:arrow_up:

workitem/link/link_repository.go
70.3% <0%> (-1.71%)
:arrow_down:

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 a5b95d8...7a3ab6f. Read the comment docs.

Is this still valid? - https://api.openshift.io/api/spaces/5188ae4d-9c27-4bc4-98bb-5c1de2dc4178/workitems/{id}/relationships/links

@sanbornsen yes, I only removed the /workitemlinks endpoint here, indeed.

That's some impressive refactoring ;)

thanks, @hectorj2f !


Offline Mode: Active 'verify' button on offline mode

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to settings then profile
Go to the contact method
Click New Contact Method then enter a new contact
Click the new account you entered to verify
now Be Offline
Notice that the Verify button is active

Expected Result:
On offline mode Verify button should not be active
Actual Result:
On offline mode Verify button is active
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number:
Reproducible in staging?: unable to reproduce by applause
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/c134f044-e3b2-4ee5-8535-cfd851cfd48a
Expensify/Expensify Issue URL:
Issue reported by: @daveSeife
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1687380769632719
View all open jobs on GitHub

@Beamanator @cristipaval is this one also intentional or is this a bug?

IIRC this was also intentional, yes - because we thought it was very likely that the user correctly entered the magic code so we would optimistically assume it was entered correctly

Okay, so is this one we should confirm is in TestRail or close out?

Yes please, I think we should also confirm this is in TestRail before closing 🙏

Done!