Dataview set/get negative index throw RangeError Fixes: #4978

Simple fix for #4978
Note the ToIndex method I used was based on the implementation in ArrayBuffer.cpp but slightly simpler as DataView.cpp has a check for lengths that are too big later on.
Could clean up the code slightly by using a consistent version of ToIndex in both places though that would be a more invasive change than this.

Thanks for fixing this - looks good to me.

I've added a separate commit to refactor this to use ArrayBuffer::ToIndex and lose the new method.
As that method include a length check I've removed the length checks from the GetValue and SetValue methods - this seemed the neatest way to implement this noting that the GetValue and SetValue methods are only used within DataView.cpp and are always now preceded immediately by a call to ToIndex.

@dotnet-bot test OSX static_osx_osx_debug please
test OSX static_osx_osx_release please
test Ubuntu static_ubuntu_linux_debug please

Assuming no one else has comments here, I can merge this today.

@jackhorton thanks, let me know if you want me to update and/or squash the two commits.
(I was keeping them separate in case anyone didn't like the way I'd refactored this)

Since we always do no-ff merges and walk first-parent history in all of our internal tooling, ive never had strong feelings on the rule about squashing. I think 2 commits is fine.

Update on this, we are having internal infra issues. Haven't forgotten about it!


Decouple Sparkle from AutoFolio

Sparkle only supports AutoFolio for algorithm selection. The AutoFolio configuration is also constant.
The goal is to decouple Sparkle from AutoFolio and allow the user to use different algorithm selectors (such as ASAP https://gitlab.com/francois.gonard/asap-v2-stable)

This has now partially been solved by the OO-fication of Sparkle's selector implementation


Fix keyword argument passing in Ruby 3

In Ruby 3, keyword arguments has to be splat into its own using double splat.
See https://www.ruby-lang.org/en/news/2019/12/12/separation-of-positional-and-keyword-arguments-in-ruby-3-0/
This fixes the following error:
in `initialize': wrong number of arguments (given 2, expected 1; required keyword: foo) (ArgumentError)

Sorry I am still yet to write test for this, don't merge just yet.


preserve reading order

test fails bcs the target tree is not updated (does not contain readingOrder)

I recommend adding a CLI option which controls this behaviour (e.g. a flag --line-regions or a choice option --dummy-region=[line,page]).

Maybe we should rather add the TextRegions for each line in any case and give an option --preserve-textract-reading-order, which defaults to True. If recursive regions are not a thing, I don't see the point in a page-encompassing region.

Yes, maybe so. Recursive regions are obligatory in the presence of tables, though. When we start supporting these, we will get two additional structural levels from Textract (TABLE and CELL), corresponding to TableRegion and (recursive) TextRegion. So there will not be a need for artificial text regions inside tables. Similar for forms.
So agreed – let's just drop the page-encompassing region unconditionally.


Incorrect syntax in the documentation?

I may just not understand something but this syntax seems to be incorrect:
// As parameter in handleAction:
handleAction(increment, {
  next(state, action) {...}
  throw(state, action) {...}
});

The second argument is not a legal object in any way I can figure out. I am having a very difficult time understanding how handleAction works to begin with, and this makes it more confusing. Is this a pseudo-code shorthand I just do not recognize? Actual syntax? Future syntax?
I will just add to this, it is fairly clear how you would use createAction and handleActions, but the purpose of handleAction is completely opaque to me. Even if there is some further reading I need to do to understand this, it would be helpful if more of the basic assumptions were outlined in the documentation.

The syntax is correct, it is part of ES6, Enhanced Object Literals.

But you need a comma after the first method declaration, yes?
Should I file another bug about providing more documentation context for the purpose behind handleAction?

But you need a comma after the first method declaration, yes?

Yes.


[Provider Audit]  provider.ttox.online

Discord: ttoX1

Hi @ttoX1 :wave:
Your provider did not bid to my deployment order request... (dseq 15800371)
Please try testing your provider by deploying something to it yourself first.
Provider attributes & info fields
I've noticed you've added the email as the provider audit.
Please use the info fields instead, to do so, simply update your provider.yaml file with the following lines:
email<EMAIL_ADDRESS>website: yourweb.com

Omit the website if you don't have one.
Please also correct your host attribute. It should be akash.
$ provider-services query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text
attributes:
...
- key: host
  value: ttox.online

And please add tier attribute, it should be set to community:
- key: tier
  value: community

Refs.
https://akash.network/docs/providers/akash-audites-atributes/#attribute-auditors

Thank you @andy108369
My fault for the duplicate post, I thought this process was possibly automated and that I was triggering the audit by re-creating this.  I added the "Community" tier and verified my host line in the provider.yaml file.  I was able to bid on my own machine successfully so I think I am ready now.  Let me know if I need to do anything else, I appreciate you!

Sorry I misunderstood the host part last time, I think I had an attribute
of "host" last time which I removed.  How does this look now?
On Tue, Apr 16, 2024 at 8:46 AM Andrey Arapov @.***>
wrote:

Hey @ttoX1 https://github.com/ttoX1 👋
Please:

remove the email provider attribute; only keep the email as info
field (which you already have);
correct the host provider attribute, it should be set to akash as
previously
https://github.com/akash-network/community/issues/533#issuecomment-2044659467
mentioned;
rename Tier into tier provider attribute

$ provider-services query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text
attributes:

key: organization
value: ttoX
key: capabilities/gpu/vendor/nvidia/model/3060ti
value: "true"
key: email
value: @.***
key: capabilities/storage
value: nvme
key: network-speed-down
value: "1000"
key: network-speed-up
value: "500"
key: arch
value: amd64
key: Tier
value: community
host_uri: https://provider.ttox.online:8443
info:
email: @.***
website: ""
owner: akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s

—
Reply to this email directly, view it on GitHub
https://github.com/akash-network/community/issues/533#issuecomment-2059135028,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHKQPYZ2G4ZA5H42DOXVM5TY5UTSFAVCNFSM6AAAAABFVQRWA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJZGEZTKMBSHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Sorry I misunderstood the host part last time, I think I had an attribute of "host" last time which I removed. How does this look now?
…
On Tue, Apr 16, 2024 at 8:46 AM Andrey Arapov @.> wrote: Hey @ttoX1 https://github.com/ttoX1 👋 Please: - remove the email provider attribute; only keep the email as info field (which you already have); - correct the host provider attribute, it should be set to akash as previously <#533 (comment)> mentioned; - rename Tier into tier provider attribute $ provider-services query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text attributes: - key: organization value: ttoX - key: capabilities/gpu/vendor/nvidia/model/3060ti value: "true" - key: email value: @. - key: capabilities/storage value: nvme - key: network-speed-down value: "1000" - key: network-speed-up value: "500" - key: arch value: amd64 - key: Tier value: community host_uri: https://provider.ttox.online:8443 info: email: @.*** website: "" owner: akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s — Reply to this email directly, view it on GitHub <#533 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHKQPYZ2G4ZA5H42DOXVM5TY5UTSFAVCNFSM6AAAAABFVQRWA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJZGEZTKMBSHA . You are receiving this because you were mentioned.Message ID: @.***>

Hi @ttoX1 , your provider is missing the host attribute.
It should be set to akash, i.e.
host: akash

As have previously requested
Currently your provider only has these attributes:
$ provider-services query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text
attributes:
- key: organization
  value: ttoX
- key: capabilities/gpu/vendor/nvidia/model/3060ti
  value: "true"
- key: capabilities/storage
  value: nvme
- key: network-speed-down
  value: "1000"
- key: network-speed-up
  value: "500"
- key: arch
  value: amd64
- key: tier
  value: community
host_uri: https://provider.ttox.online:8443
info:
  email<EMAIL_ADDRESS>  website: ""
owner: akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s

You also need to expose more GPU related provider attributes - capabilities.
- key: capabilities/gpu/vendor/nvidia/model/3060ti
  value: "true"

Also, the GPU has to go with rtx, i.e. rtx3060ti, here is the working example:

it comes from the gpus.json config; you can also use kubectl get nodes --show-labels to see the rtx3060ti is there.

attributes:
- key: host
  value: akash
- key: tier
  value: community
...
...
- key: capabilities/gpu
  value: nvidia
- key: capabilities/gpu/vendor/nvidia/model/rtx3060ti
  value: "true"
- key: capabilities/gpu/vendor/nvidia/model/rtx3060ti/ram/8Gi
  value: "true"
- key: capabilities/gpu/vendor/nvidia/model/rtx3060ti/ram/8Gi/interface/pcie
  value: "true"
- key: capabilities/gpu/vendor/nvidia/model/rtx3060ti/interface/pcie
  value: "true"

I have made the adjustments as requested, should be all set now, thanks for
the help!
On Mon, May 6, 2024 at 6:12 AM Andrey Arapov @.***>
wrote:

Sorry I misunderstood the host part last time, I think I had an attribute
of "host" last time which I removed. How does this look now?
… <#m_269378651920823628_>
On Tue, Apr 16, 2024 at 8:46 AM Andrey Arapov @.> wrote: Hey @ttoX1
https://github.com/ttoX1 https://github.com/ttoX1
https://github.com/ttoX1 👋 Please: - remove the email provider
attribute; only keep the email as info field (which you already have); -
correct the host provider attribute, it should be set to akash as
previously <#533 (comment)
https://github.com/akash-network/community/issues/533#issuecomment-2044659467>
mentioned; - rename Tier into tier provider attribute $ provider-services
query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text
attributes: - key: organization value: ttoX - key:
capabilities/gpu/vendor/nvidia/model/3060ti value: "true" - key: email
value: @. - key: capabilities/storage value: nvme - key:
network-speed-down value: "1000" - key: network-speed-up value: "500" -
key: arch value: amd64 - key: Tier value: community host_uri:
https://provider.ttox.online:8443 info: email: @.*** website: "" owner:
akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s — Reply to this email
directly, view it on GitHub <#533 (comment)
https://github.com/akash-network/community/issues/533#issuecomment-2059135028>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHKQPYZ2G4ZA5H42DOXVM5TY5UTSFAVCNFSM6AAAAABFVQRWA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJZGEZTKMBSHA
. You are receiving this because you were mentioned.Message ID: @.***>
Hi @ttoX1 https://github.com/ttoX1 , your provider is missing the host
attribute.
It should be set to akash, i.e.
host: akash
As have previously requested
https://github.com/akash-network/community/issues/533#issuecomment-2059135028
Currently your provider only has these attributes:
$ provider-services query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text
attributes:

key: organization
value: ttoX
key: capabilities/gpu/vendor/nvidia/model/3060ti
value: "true"
key: capabilities/storage
value: nvme
key: network-speed-down
value: "1000"
key: network-speed-up
value: "500"
key: arch
value: amd64
key: tier
value: community
host_uri: https://provider.ttox.online:8443
info:
email: @.***
website: ""
owner: akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s

You also need to expose more GPU related provider attributes -
capabilities.

key: capabilities/gpu/vendor/nvidia/model/3060ti
value: "true"

Also, the GPU has to go with rtx, i.e. rtx3060ti, here is the working
example:
it comes from the gpus.json
https://github.com/akash-network/provider-configs/blob/4277ecfa6473835bf39b1bbe7486b95cd90893b1/devices/pcie/gpus.json#L51C18-L51C27
config; you can also use kubectl get nodes --show-labels to see the
rtx3060ti is there.
attributes:

key: host
value: akash
key: tier
value: community
...
...
key: capabilities/gpu
value: nvidia
key: capabilities/gpu/vendor/nvidia/model/rtx3060ti
value: "true"
key: capabilities/gpu/vendor/nvidia/model/rtx3060ti/ram/8Gi
value: "true"
key: capabilities/gpu/vendor/nvidia/model/rtx3060ti/ram/8Gi/interface/pcie
value: "true"
key: capabilities/gpu/vendor/nvidia/model/rtx3060ti/interface/pcie
value: "true"

—
Reply to this email directly, view it on GitHub
https://github.com/akash-network/community/issues/533#issuecomment-2095767599,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHKQPY3ENLB3XK46Z2EVOZ3ZA5QSBAVCNFSM6AAAAABFVQRWA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVG43DONJZHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

I have made the adjustments as requested, should be all set now, thanks for the help! On Mon, May 6, 2024 at 6:12 AM Andrey Arapov @.> wrote:
…
Sorry I misunderstood the host part last time, I think I had an attribute of "host" last time which I removed. How does this look now? … <#m_269378651920823628_> On Tue, Apr 16, 2024 at 8:46 AM Andrey Arapov @.> wrote: Hey @ttoX1 https://github.com/ttoX1 https://github.com/ttoX1 https://github.com/ttoX1 👋 Please: - remove the email provider attribute; only keep the email as info field (which you already have); - correct the host provider attribute, it should be set to akash as previously <#533 (comment) <#533 (comment)>> mentioned; - rename Tier into tier provider attribute $ provider-services query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text attributes: - key: organization value: ttoX - key: capabilities/gpu/vendor/nvidia/model/3060ti value: "true" - key: email value: @. - key: capabilities/storage value: nvme - key: network-speed-down value: "1000" - key: network-speed-up value: "500" - key: arch value: amd64 - key: Tier value: community host_uri: https://provider.ttox.online:8443 info: email: @.** website: "" owner: akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s — Reply to this email directly, view it on GitHub <#533 (comment) <#533 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHKQPYZ2G4ZA5H42DOXVM5TY5UTSFAVCNFSM6AAAAABFVQRWA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJZGEZTKMBSHA . You are receiving this because you were mentioned.Message ID: @.> Hi @ttoX1 https://github.com/ttoX1 , your provider is missing the host attribute. It should be set to akash, i.e. host: akash As have previously requested <#533 (comment)> Currently your provider only has these attributes: $ provider-services query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text attributes: - key: organization value: ttoX - key: capabilities/gpu/vendor/nvidia/model/3060ti value: "true" - key: capabilities/storage value: nvme - key: network-speed-down value: "1000" - key: network-speed-up value: "500" - key: arch value: amd64 - key: tier value: community host_uri: https://provider.ttox.online:8443 info: email: @. website: "" owner: akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s You also need to expose more GPU related provider attributes - capabilities. - key: capabilities/gpu/vendor/nvidia/model/3060ti value: "true" Also, the GPU has to go with rtx, i.e. rtx3060ti, here is the working example: it comes from the gpus.json https://github.com/akash-network/provider-configs/blob/4277ecfa6473835bf39b1bbe7486b95cd90893b1/devices/pcie/gpus.json#L51C18-L51C27 config; you can also use kubectl get nodes --show-labels to see the rtx3060ti is there. attributes: - key: host value: akash - key: tier value: community ... ... - key: capabilities/gpu value: nvidia - key: capabilities/gpu/vendor/nvidia/model/rtx3060ti value: "true" - key: capabilities/gpu/vendor/nvidia/model/rtx3060ti/ram/8Gi value: "true" - key: capabilities/gpu/vendor/nvidia/model/rtx3060ti/ram/8Gi/interface/pcie value: "true" - key: capabilities/gpu/vendor/nvidia/model/rtx3060ti/interface/pcie value: "true" — Reply to this email directly, view it on GitHub <#533 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BHKQPY3ENLB3XK46Z2EVOZ3ZA5QSBAVCNFSM6AAAAABFVQRWA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVG43DONJZHE . You are receiving this because you were mentioned.Message ID: @.***>

Hi @ttoX1 :wave:
I still cannot see any updates:
$ provider-services query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text
attributes:
- key: organization
  value: ttoX
- key: capabilities/gpu/vendor/nvidia/model/3060ti
  value: "true"
- key: capabilities/storage
  value: nvme
- key: network-speed-down
  value: "1000"
- key: network-speed-up
  value: "500"
- key: arch
  value: amd64
- key: tier
  value: community
host_uri: https://provider.ttox.online:8443
info:
  email<EMAIL_ADDRESS>  website: ""
owner: akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s

Have you applied your provider.yaml config after you've updated it?
Basically you'd need to:
cd /provider
mv price_script_generic.sh price_script_generic.sh.1
wget https://raw.githubusercontent.com/akash-network/helm-charts/main/charts/akash-provider/scripts/price_script_generic.sh
helm upgrade akash-provider akash/provider -n akash-services -f provider.yaml --set bidpricescript="$(cat price_script_generic.sh | openssl base64 -A)"

Ahh yes that was it, I use Praetor and wasn't aware I had to do anything
after updating the file manually in this case.  Should be good now, thanks
again!
On Tue, May 7, 2024 at 4:54 AM Andrey Arapov @.***>
wrote:

I have made the adjustments as requested, should be all set now, thanks
for the help! On Mon, May 6, 2024 at 6:12 AM Andrey Arapov @.
*> wrote: … <#m_1871186585702285329_> Sorry I misunderstood the host part
last time, I think I had an attribute of "host" last time which I removed.
How does this look now? … <#m_269378651920823628_> On Tue, Apr 16, 2024 at
8:46 AM Andrey Arapov @.> wrote: Hey @ttoX1 https://github.com/ttoX1
https://github.com/ttoX1 https://github.com/ttoX1
https://github.com/ttoX1 https://github.com/ttoX1
https://github.com/ttoX1 https://github.com/ttoX1 👋 Please: - remove the
email provider attribute; only keep the email as info field (which you
already have); - correct the host provider attribute, it should be set to
akash as previously <#533
https://github.com/akash-network/community/issues/533 (comment) <#533
(comment)
https://github.com/akash-network/community/issues/533#issuecomment-2044659467>>
mentioned; - rename Tier into tier provider attribute $ provider-services
query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text
attributes: - key: organization value: ttoX - key:
capabilities/gpu/vendor/nvidia/model/3060ti value: "true" - key: email
value: @. - key: capabilities/storage value: nvme - key: network-speed-down
value: "1000" - key: network-speed-up value: "500" - key: arch value: amd64

key: Tier value: community host_uri: https://provider.ttox.online:8443
https://provider.ttox.online:8443 info: email: @.*** website: "" owner:
akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s — Reply to this email
directly, view it on GitHub <#533
https://github.com/akash-network/community/issues/533 (comment) <#533
(comment)
https://github.com/akash-network/community/issues/533#issuecomment-2059135028>>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHKQPYZ2G4ZA5H42DOXVM5TY5UTSFAVCNFSM6AAAAABFVQRWA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJZGEZTKMBSHA
. You are receiving this because you were mentioned.Message ID: @.> Hi
@ttoX1 https://github.com/ttoX1 https://github.com/ttoX1
https://github.com/ttoX1 , your provider is missing the host attribute.
It should be set to akash, i.e. host: akash As have previously requested
<#533 (comment)
https://github.com/akash-network/community/issues/533#issuecomment-2059135028>
Currently your provider only has these attributes: $ provider-services
query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text
attributes: - key: organization value: ttoX - key:
capabilities/gpu/vendor/nvidia/model/3060ti value: "true" - key:
capabilities/storage value: nvme - key: network-speed-down value: "1000" -
key: network-speed-up value: "500" - key: arch value: amd64 - key: tier
value: community host_uri: https://provider.ttox.online:8443
https://provider.ttox.online:8443 info: email: @. website: "" owner:
akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s You also need to expose more
GPU related provider attributes - capabilities. - key:
capabilities/gpu/vendor/nvidia/model/3060ti value: "true" Also, the GPU has
to go with rtx, i.e. rtx3060ti, here is the working example: it comes from
the gpus.json
https://github.com/akash-network/provider-configs/blob/4277ecfa6473835bf39b1bbe7486b95cd90893b1/devices/pcie/gpus.json#L51C18-L51C27
config; you can also use kubectl get nodes --show-labels to see the
rtx3060ti is there. attributes: - key: host value: akash - key: tier value:
community ... ... - key: capabilities/gpu value: nvidia - key:
capabilities/gpu/vendor/nvidia/model/rtx3060ti value: "true" - key:
capabilities/gpu/vendor/nvidia/model/rtx3060ti/ram/8Gi value: "true" - key:
capabilities/gpu/vendor/nvidia/model/rtx3060ti/ram/8Gi/interface/pcie
value: "true" - key:
capabilities/gpu/vendor/nvidia/model/rtx3060ti/interface/pcie value: "true"
— Reply to this email directly, view it on GitHub <#533 (comment)
https://github.com/akash-network/community/issues/533#issuecomment-2095767599>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHKQPY3ENLB3XK46Z2EVOZ3ZA5QSBAVCNFSM6AAAAABFVQRWA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVG43DONJZHE
. You are receiving this because you were mentioned.Message ID: @.***>

Hi @ttoX1 https://github.com/ttoX1 👋
I still cannot see any updates:
$ provider-services query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text
attributes:

key: organization
value: ttoX
key: capabilities/gpu/vendor/nvidia/model/3060ti
value: "true"
key: capabilities/storage
value: nvme
key: network-speed-down
value: "1000"
key: network-speed-up
value: "500"
key: arch
value: amd64
key: tier
value: community
host_uri: https://provider.ttox.online:8443
info:
email: @.***
website: ""
owner: akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s

Have you applied your provider.yaml config after you've updated it?
Basically you'd need to:
cd /provider
mv price_script_generic.sh price_script_generic.sh.1
wget https://raw.githubusercontent.com/akash-network/helm-charts/main/charts/akash-provider/scripts/price_script_generic.sh
helm upgrade akash-provider akash/provider -n akash-services -f provider.yaml --set bidpricescript="$(cat price_script_generic.sh | openssl base64 -A)"
—
Reply to this email directly, view it on GitHub
https://github.com/akash-network/community/issues/533#issuecomment-2097908016,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHKQPY36LZKZT6NYEF4BEN3ZBCQE5AVCNFSM6AAAAABFVQRWA2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJXHEYDQMBRGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Any updates on this?  Im almost out of Akash tokens and was hoping to get a full feel for everything before putting more in if possible.  I appreciate anything we can do to expedite the request, thanks in advance as well.

Hi @ttoX1
Apologies for the delay.
You have the inconsistency between the GPU model names - 3060ti vs rtx3060ti.
It should be the latter - rtx3060ti.
Please correct your provider.yaml file and update the akash-provider pod for the changes to reflect:
$ provider-services query provider get akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s -o text
attributes:
- key: organization
  value: ttoX
- key: host
  value: akash
- key: capabilities/gpu
  value: nvidia
- key: capabilities/gpu/vendor/nvidia/model/3060ti
  value: "true"
- key: capabilities/gpu/vendor/nvidia/model/rtx3060ti/ram/8Gi
  value: "true"
- key: capabilities/gpu/vendor/nvidia/model/rtx3060ti/ram/8Gi/interface/pcie
  value: "true"
- key: capabilities/gpu/vendor/nvidia/model/3060ti/interface/pcie
  value: "true"
- key: capabilities/storage
  value: nvme
- key: network-speed-down
  value: "1000"
- key: network-speed-up
  value: "500"
- key: arch
  value: amd64
- key: tier
  value: community
host_uri: https://provider.ttox.online:8443
info:
  email<EMAIL_ADDRESS>  website: ""
owner: akash1t0gd2uv44xh8sm5mutmj2reslvm58ss3ld7z9s


[SMALLFIX] Fix meta master master service version

Simple bug, causes
2018-06-15 13:20:36,902 WARN  alluxio.AbstractClient (AbstractClient.java:connect) - Failed to connect (1) with MetaMasterMaster @ <IP_ADDRESS>/<IP_ADDRESS>:53018: MetaMasterMaster client version 1 is not compatible with server version 2
in the logs

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20185/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.client.rest.S3ClientRestApiTest.getObjectMetadata
Test FAILed.

jenkins, test this please

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20191/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.server.configuration.ConfigCheckerIntegrationTest.unsetVsSet
Test FAILed.


Allow to specify custom annotations for the service helm template

#sre

Thanks for this PR, sounds good to me. But Kubernetes service has not test yet, can I ask you to add the 2 following changes:

Create configs/helm/tests/values/with_service.yaml that will be used to set an annotation in tests:

service:
  annotations:
    annotation1: value1

Create configs/helm/tests/service_test.yaml to test the Kubernetes service

# yaml-language-server: $schema=https://raw.githubusercontent.com/helm-unittest/helm-unittest/main/schema/helm-testsuite.json
---
suite: grafana dashboard tests
templates:
  - service.yaml
tests:
  - it: render default service
    asserts:
      - isKind:
          of: Service
      - hasDocuments:
          count: 1
  - it: with custom service
    values:
      - ./values/with_service.yaml
    asserts:
      - equal:
          path: metadata.annotations.annotation1
          value: value1

With this configuration, we'll test in the CI that Kubernetes service return is valid according to the Kubernetes api.

@vmercierfr wow, i haven't noticed the tests for helm chart. since it is MIT licensed repository it is definitely something i will be looking to "steal" into my OS repos 😄
i will update the code in a moment

i modified it, but i have trouble running unit tests on my local machine. i've installed the unittest plugin but it is throwing errors:

In order to merge the PR, @kuskoman  can you sign all your commits (git rebase HEAD~3 --signoff) ?

ahh, i signed 3rd part commits by mistake, lemme fix that

@vmercierfr since i started from your current head with just a single commit, could you rerun the tests just to make sure? now the branch should be in the correct state

Tests are ok:
helm unittest configs/helm
2024/06/28 15:49:17 found symbolic link in path: /Users/vincent.mercier/Documents/github/kuskoman/prometheus-rds-exporter/configs/helm/LICENSE resolves to /Users/vincent.mercier/Documents/github/kuskoman/prometheus-rds-exporter/LICENSE. Contents of linked file included and used
2024/06/28 15:49:17 found symbolic link in path: /Users/vincent.mercier/Documents/github/kuskoman/prometheus-rds-exporter/configs/helm/grafana_dashboards resolves to /Users/vincent.mercier/Documents/github/kuskoman/prometheus-rds-exporter/configs/grafana/public. Contents of linked file included and used

### Chart [ prometheus-rds-exporter-chart ] configs/helm

 PASS  deployment tests	configs/helm/tests/deployment_test.yaml
 PASS  grafana dashboard tests	configs/helm/tests/grafanadashboard_test.yaml
 PASS  service tests	configs/helm/tests/service_test.yaml
 PASS  service account tests	configs/helm/tests/serviceaccount_test.yaml
 PASS  service monitor tests	configs/helm/tests/servicemonitor_test.yaml

Charts:      1 passed, 1 total
Test Suites: 5 passed, 5 total
Tests:       16 passed, 16 total
Snapshot:    0 passed, 0 total
Time:        85.865375ms

But git commits are not correctly signed; you should have a verified icon of your commits.
Can you check your commits signature?

https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits
https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work


Feature/add coverage thershold & workflow

update documentations
add badge coverage (codecov)
test init
75% of thershold

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (e956641) 100.00% compared to head (9e9c09e) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@              Coverage Diff              @@
##           development        #2   +/-   ##
=============================================
  Coverage       100.00%   100.00%
=============================================
  Files                1         1
  Lines                1         2    +1
=============================================
+ Hits                 1         2    +1

Files
Coverage Δ

src/function-test.js
100.00% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Does not respect dark theme

If you select the dark theme in Firefox, the urlbar and tabs still look "light" in normal browsing windows.
There should be a way to detect the current theme by lwthemetextcolor="bright" or "dark".

@muckSponge Thanks for the quick fix. 👍


KEYGEN sometimes giving 63byte instead of 64byte

To derive keys for ethereum we need the x and y coordinates to be 64byte long. Sometimes keygen is outputing 63byte.
pk := ecdsa.PublicKey{
	Curve: tss.S256(),
	X:     save.ECDSAPub.X(),
	Y:     save.ECDSAPub.Y(),
}
pubKey = pk.X.String() + pk.Y.String()
//After hex:(I have added `0x04. You can ignore`)
`0x0416c762ed0e6c96cbc284ccfdcad9b4d918201acc4e440ee5f35cc746ea9c818812f952d93fe3f769b8e0100f6afb1e7900ec9bdb42476d5798d0a0074be71f1a9`

This cannot go though hashing and slicing to provide a valid ethereum address,because of public key. Kindly assist

Issue was how i was converting. Pubkey is okay!


Conflict with Perfect-Vision module

With only Perfect-Vision and Walled-Templates enabled (and libWrapper) I've encountered some visual rendering issues. I'm not a techy person so I'm sorry I can't really give more than that. I can do my best if you need me to send any more info.
"Canvas drawing failed for the SightLayer" seems to occur all the time, but things still render
"Canvas drawing failed for the LightingLayer" only seems to occur if there is a light source (on/off doesn't matter), but then this makes the whole scene visually disappear.
Info:
Foundry: v 9 Build 269
DnD5e: v 1.6.1
Walled Templates: v 0.2.0
Perfect-Vision: v 3.9.4
libWrapper: v <IP_ADDRESS>

Some overlap:

Overlaps with  Incompatibility with Perfect Vision module #2  but this also includes error with LightingLayer which is not included in #2

Fixed in v 0.2.2.


[OTHER]

What would you like to share?
DOES MY LOCATION WORK NOW???
Additional information
No response

COMMENT


Context addition

testcontext
WIP send event at start and end of reconcile loop

/lgtm

Merging since the last commit is a trivial typo fix


Fix pythonInterpreters.pypy27_prebuilt, pythonInterpreters.pypy36_prebuilt

Motivation for this change
pythonInterpreters.pypy27_prebuilt and pythonInterpreters.pypy36_prebuilt were broken by #105155 and #110591. Fix them.
Things done

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

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

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

Thanks!


Feature: Node Network

Feature: Node Network
TODO List

Plan deployment of The Relay Network - Not Started
Publishing a list of Relay Servers used by all clients to connect to the network

Help is wanted with setting up, deploying, and maintaining The Relay Network. Server admin skills required.


⚠ ClamAV has degraded performance

In adce972, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 52 ms

Resolved: ClamAV performance has improved in cab834f after 23 minutes.


Unable to create new Amplify app in console because of CORS error

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
na
Region
us-east-2
Amplify Hosting feature
Not applicable
Describe the bug
I'm trying to create a new Amplify app connected to a repo on GitHub. At the final step of the setup wizard, I get this error:

Looking in the javascript console, I see these:
Access to XMLHttpRequest at 'https://amplify.us-east-2.amazonaws.com/apps' from origin 'https://us-east-2.console.aws.amazon.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.

POST https://amplify.us-east-2.amazonaws.com/apps net::ERR_FAILED 403

GET https://aws-amplify-prod-us-east-2-artifacts.s3.us-east-2.amazonaws.com/dpjyrelzm51lv/develop/SCREENSHOTS/thumbnail.png?X-Amz-Security-Token=IQoJb3JpZ2luX2VjENv%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEaCXVzLWVhc3QtMiJGMEQCIDGac8r5sgw9pCKMRtB9bQ5AIv%2BP8til5DRmF60IhoDcAiAiaTYvtZK2Bhc7bqvCpPNQ4XmkLDfJ3HIRcZ3u2HrUfyq6AghkEAMaDDI2NDc0ODIwMDYyMSIM4hNjaP445n1s53hdKpcC%2FW5L0L%2BvbqR5NkL%2Bp0yD%2BwJU7TjBCswOrkVU6tW8Cg4AGbQrG9cuSpmoGCRl4YDvo%2Fow3yVwjklbZmZAiIUkZauS15hqqU9f53nSpdWpfKkJJ5bbjwJuQV%2FPDONuI50cD%2FZV5ckcBwiOCtRY%2FXYavqmjsQONTkp67BHkDWbBSfa28qg8fq8gjRTDCEjhHyWFlhM4wSOoXJ9WpryBkmGdc50MqNjLX54kbYFW9%2F%2FXmWp%2BU5jM%2B0MRugR%2BjTJVqTM57kkvRcmtUB53vNdzHkL%2BgFbOiEXj89V53osaIytgcHCbvZ72r%2B0kN1r56OunE1mPbHWUFOZ5t30H0sPZ6oPRnu8nPN8eJJFTxuTFLe3W4eB%2F8Vqk0BFAMOP38pEGOpsBUiQOl8%2BH38Nt%2BdZ8XDpZloyc0t4TCc6oXEGsLShT5T5xoKHaqjAOi0HBsdVteni%2FfTCBzSa8Qxoh0XfSjrxsg1cDhBLsR7CTzQQGMXwp3405E0yGM1Cvvt%2B2B88ONU92Jn6yAvBPwj8DfUEtc9db%2BnH4%2FphfYXPowi%2FS5tDM%2FibDlPq3cf9cVVaSp0jAEEO5TkAe%2BqWOxawhw%2BM%3D&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20220324T201341Z&X-Amz-SignedHeaders=host&X-Amz-Expires=3600&X-Amz-Credential=ASIAT3JBY6KW5SO7UKUJ%2F20220324%2Fus-east-2%2Fs3%2Faws4_request&X-Amz-Signature=1468ef5ee8b08ed8b138c9af62c5aba3feb0f76a67dbe6a358ed90202882e616 404 (Not Found)

Expected behavior
App should deploy
Reproduction steps
Click "Host your web app" in Amplify
Connect to a Github repo
Click "Save and Deploy"
Build Settings
No response
Additional information
No response

It turns out this was caused by insufficient user privs in our SSO setup 😰
I feel like the error could be more informative though!

Hi @jayKayEss 👋🏽 glad to see you were able to resolve this. I will close this issue but we are working on improving the logging and I will add this feedback for the team as well. Thank you!


⚠ SceneTime has degraded performance

In a9aa155, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 5491 ms

Resolved: SceneTime performance has improved in 8b8dacf after 19 minutes.


Building on BackTrack 5R3 fails to find libevent 2.x

I'm running BackTrack 5 R3 and trying to compile it.
I'm having an error about libevent. I tried updating it and currently libevent is in the newest version (apt-get).
When trying to compile SSLSplit I get the following error:
root@bt:~/sslsplit# make
GNUmakefile:175: *** dependency 'libevent 2.x' not found; install it or point LIBEVENT_BASE to base path.  Stop.
libevent is at '/usr/lib/libevent.a', and I have no idea how to set LIBEVENT_BASE appropriately. I tried this:
root@bt:~/sslsplit# LIBEVENT_BASE=/usr/lib/libevent.a
root@bt:~/sslsplit# make
GNUmakefile:175: *** dependency 'libevent 2.x' not found; install it or point LIBEVENT_BASE to base path.  Stop.
any idea what I am doing wrong?

FYI: yum install libevent-devel.i686 made me happy.


Make sure minimap error indicators follow the scrolling

Fixes an issue reported by @laymonage with the minimap’s error indicator, which were stuck to their initial rendering position and not following along as the minimap scrolls. This was due to usage of absolute positioning based on the position of the parent.
position: absolute; usage was only so the indicators would overflow their parent – so I removed it, and changed where the left-edge external padding of the minimap is defined, so the error indicators technically aren’t overflowing their parent element.
Please check the following:

[x] Do the tests still pass?[^1]
[x] Does the code comply with the style guide?
[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[x] Please list the exact browser and operating system versions you tested: Chrome 106, Firefox 104, Safari 15.6 on macOS. Safari 16 on iOS
[x] Please list which assistive technologies [^3] you tested: Full-page zoom, keyboard.

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
Make a long page where the minimap would overflow the viewport, create validation errors, save as draft. Then upon reviewing the validation errors, scroll the minimap, and observe the error indicators keep their position next to the correct field label.

Cherry-picked, tested, merged on stable/4.1.x.


Added OS Generated Files

.gitignore Operation System Garbage

These are covered in the Global/OSX.gitignore and Global/Windows.gitignore...


Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

I ran the command ~/work/pav-monitoring/jenkins_dashboard$ bundle
Instead, what actually happened was...
Error details
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

/usr/bin/ruby2.1 extconf.rb

rake 10.1.0 not found in GEM_PATH
/home/jov/.rvm/rubies/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/executable-hooks-1.3.2/lib/executable-hooks/regenerate_binstubs_command.rb:71:in initialize': Permission denied @ rb_sysopen - /usr/bin/rdoc (Errno::EACCES)         from /home/jov/.rvm/rubies/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/executable-hooks-1.3.2/lib/executable-hooks/regenerate_binstubs_command.rb:71:inopen'
from /home/jov/.rvm/rubies/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/executable-hooks-1.3.2/lib/executable-hooks/regenerate_binstubs_command.rb:71:in block in try_to_fix_binstubs'         from /home/jov/.rvm/rubies/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/executable-hooks-1.3.2/lib/executable-hooks/regenerate_binstubs_command.rb:69:inmap'
from /home/jov/.rvm/rubies/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/executable-hooks-1.3.2/lib/executable-hooks/regenerate_binstubs_command.rb:69:in try_to_fix_binstubs'         from /home/jov/.rvm/rubies/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/executable-hooks-1.3.2/lib/executable-hooks/regenerate_binstubs_command.rb:46:inblock in execute_no_wrapper'
from /home/jov/.rvm/rubies/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/executable-hooks-1.3.2/lib/executable-hooks/regenerate_binstubs_command.rb:44:in each'         from /home/jov/.rvm/rubies/ruby-2.2.1/lib/ruby/gems/2.2.0/gems/executable-hooks-1.3.2/lib/executable-hooks/regenerate_binstubs_command.rb:44:inexecute_no_wrapper'
from extconf.rb:19:in `'
bundler 1.10.5
dashing 1.3.4
executable-hooks 1.3.2
rack 1.5.5
rdoc 4.1.0
extconf failed, exit code 1
Gem files will remain installed in<EMAIL_ADDRESS>for inspection.
Results logged to<EMAIL_ADDRESS>  /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:89:in `run'
  /usr/lib/ruby/2.1.0/rubygems/ext/ext_conf_builder.rb:38:in `block in build'
  /usr/lib/ruby/2.1.0/tempfile.rb:324:in `open'
  /usr/lib/ruby/2.1.0/rubygems/ext/ext_conf_builder.rb:17:in `build'
  /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:161:in `block (2 levels) in build_extension'
  /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:160:in `chdir'
  /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:160:in `block in build_extension'
  /usr/lib/ruby/2.1.0/monitor.rb:211:in `mon_synchronize'
  /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:159:in `build_extension'
  /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:198:in `block in build_extensions'
  /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:195:in `each'
  /usr/lib/ruby/2.1.0/rubygems/ext/builder.rb:195:in `build_extensions'
  /usr/lib/ruby/2.1.0/rubygems/specification.rb:1436:in `block in build_extensions'
  /usr/lib/ruby/2.1.0/rubygems/user_interaction.rb:45:in `use_ui'
  /usr/lib/ruby/2.1.0/rubygems/specification.rb:1434:in `build_extensions'
  /usr/lib/ruby/2.1.0/rubygems/stub_specification.rb:60:in `build_extensions'
  /usr/lib/ruby/2.1.0/rubygems/basic_specification.rb:56:in `contains_requirable_file?'
  /usr/lib/ruby/2.1.0/rubygems/specification.rb:925:in `block in find_inactive_by_path'
  /usr/lib/ruby/2.1.0/rubygems/specification.rb:924:in `each'
  /usr/lib/ruby/2.1.0/rubygems/specification.rb:924:in `find'
  /usr/lib/ruby/2.1.0/rubygems/specification.rb:924:in `find_inactive_by_path'
  /usr/lib/ruby/2.1.0/rubygems.rb:185:in `try_activate'
  /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:132:in `rescue in require'
  /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:144:in `require'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/lib/bundler/vendor/net/http/persistent.rb:12:in `<top (required)>'
  /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/lib/bundler/vendored_persistent.rb:11:in `<top (required)>'
  /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  /usr/lib/ruby/2.1.0/rubygems/core_ext/kernel_require.rb:55:in `require'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/lib/bundler/fetcher.rb:1:in `<top (required)>'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/lib/bundler/cli/install.rb:98:in `run'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/lib/bundler/cli.rb:162:in `install'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/lib/bundler/vendor/thor/lib/thor.rb:359:in `dispatch'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/lib/bundler/vendor/thor/lib/thor/base.rb:440:in `start'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/lib/bundler/cli.rb:10:in `start'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/bin/bundle:20:in `block in <top (required)>'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/lib/bundler/friendly_errors.rb:7:in `with_friendly_errors'
  /home/jov/.rvm/gems/ruby-2.2.1/gems/bundler-1.10.5/bin/bundle:18:in `<top (required)>'
  /usr/local/bin/bundle:23:in `load'
  /usr/local/bin/bundle:23:in `<main>'

Environment
Bundler   1.10.5
Rubygems  2.2.2
Ruby      2.1.2p95 (2014-05-08 revision 0) [x86_64-linux-gnu]
GEM_HOME  /home/jov/.rvm/gems/ruby-2.2.1
GEM_PATH  /home/jov/.rvm/gems/ruby-2.2.1:/home/jov/.rvm/gems/ruby-2.2.1@global
RVM       1.26.11 (latest)
Git       2.1.4
rubygems-bundler (1.4.4)

sudo bundle worked.

I have had this same issue on a OS X 10.10, but sudo bundle doesn't work. :)

I have a very same problem on Ubuntu 15.04 , and sudo bundle does not work , but gem install bundler habe been solved my problem .

I have same issue and solve with this https://github.com/flori/json/issues/253

Just ran into the same problem on debian after updating to ruby 2.2.3. Unfortunately https://github.com/flori/json/issues/253 did not help.

rvm how to di in error

GianFF thank you man!

I run bundle install
Don't run Bundler as root. Bundler can ask for sudo if it is needed, and installing
your bundle as root will break this application for all non-root users on this
machine.
Fetching gem metadata from https://rubygems.org/..........
Fetching version metadata from https://rubygems.org/..
Fetching dependency metadata from https://rubygems.org/.
Resolving dependencies...
Using rake 12.0.0
Using concurrent-ruby 1.0.4
Using i18n 0.7.0
Using minitest 5.10.1
Using thread_safe 0.3.5
Using builder 3.2.2
Using erubis 2.7.0
Using mini_portile2 2.1.0
Using rack 2.0.1
Installing nio4r 1.2.1 with native extensions
Using websocket-extensions 0.1.2
Using mime-types-data 3.2016.0521
Using arel 7.1.4
Installing debug_inspector 0.0.2 with native extensions
Using bundler 1.13.7
Installing byebug 9.0.6 with native extensions
Using coffee-script-source 1.12.2
Using execjs 2.7.0
Using method_source 0.8.2
Using thor 0.19.4
Using multi_json 1.12.1
Using json 1.8.3
Installing mysql2 0.4.5 with native extensions
Using rdoc 4.3.0
Using sass 3.4.23
Using tilt 2.0.5
Using turbolinks-source 5.0.0
Using tzinfo 1.2.2
Installing nokogiri <IP_ADDRESS> with native extensions
Using rack-test 0.6.3
Using sprockets 3.7.1
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
current directory: /var/lib/gems/2.3.0/gems/nio4r-1.2.1/ext/nio4r

/usr/bin/ruby2.3 -r ./siteconf20170109-3150-tw7km1.rb extconf.rb
--with-cflags=-std=c99
mkmf.rb can't find header files for ruby at /usr/lib/ruby/include/ruby.h
extconf failed, exit code 1
Gem files will remain installed in /var/lib/gems/2.3.0/gems/nio4r-1.2.1 for
inspection.
Results logged to
/var/lib/gems/2.3.0/extensions/x86_64-linux/2.3.0/nio4r-1.2.1/gem_make.out
An error occurred while installing nio4r (1.2.1), and Bundler cannot
continue.
Make sure that gem install nio4r -v '1.2.1' succeeds before bundling.

GianFF thanks a lot that worked for me as well

My Case
Mac
in mkmf.log
Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo.

After Update macOS, this log message shown.
Open Xcode, and agree license. I can install this gem.


[Discussion] Getting started guide

Hey, wanted to start the discussion on what everyone would like to see in a "getting started" guide.
So first of all, do you think this would be something useful to beginners?
I felt a bit lost in the beginning with just the api docs and the examples, so I think a guided getting started section that explains how to set everything up would be helpful to get more people in.
Would probably start picking up right from installation:

Setting up accessToken
showing specific map area
showing user location
using rasterLayer to render different tiles

Feedback welcome!

I would add something about the offline management. The packs can actually be paused and resumed in a way, but that is not in the docs. You can see it in the examples tho.
Also I feel a lot of people have questions or problems regarding custom styles. It should be clear to everyone what native SDK version the repo is using at that time so they can adapt accordingly.

Yes, I think it would be useful and I agree with the topics already brought up.
Assuming the docs are for v7, it should also include something on expressions and how to use them.
@ferdicus Were you planning on writing these, or have you already started?  I can take on this task if nobody else has staked claim to it yet 👍

thanks for the feedback!
@bigsassy: I was planning on tackling this, bit by bit and concentrate on adding value to the readme as fast as possible. So I would start tomorrow, and see where it goes from there.
However feel free to join in, expression guides would be more than appreciated!
As for v7, I would want to wait till it has properly landed and then adjust/ add guides afterwards.

what's the eta on this package being published to the new namespace? after v7 is finished?

So I would start tomorrow, and see where it goes from there.

Works for me 👍

what's the eta on this package being published to the new namespace? after v7 is finished?
sorry, no clue..

Hey, wanted to start the discussion on what everyone would like to see in a "getting started" guide.
So first of all, do you think this would be something useful to beginners?
I felt a bit lost in the beginning with just the api docs and the examples, so I think a guided getting started section that explains how to set everything up would be helpful to get more people in.
Would probably start picking up right from installation:

Setting up accessToken
showing specific map area
showing user location
using rasterLayer to render different tiles

Feedback welcome!

I’d love to contribute.  I have gone through this process a number of times and may be able to add content.  However my understanding is much will change so I’m waiting to confirm any new changes.

I’d love to contribute. I have gone through this process a number of times and may be able to add content. However my understanding is much will change so I’m waiting to confirm any new changes.

True, however documentation is always in a state of flux, so why not have a baseline which we can edit later, instead of not helping newbies at all?

I’d love to contribute. I have gone through this process a number of times and may be able to add content. However my understanding is much will change so I’m waiting to confirm any new changes.

True, however documentation is always in a state of flux, so why not have a baseline which we can edit later, instead of not helping newbies at all?

It’s a valid point. My understanding was that these changes are coming out fairly soon. Perhaps that’s not the case?  My only concern was that these changes were around the corner.

It’s a valid point. My understanding was that these changes are coming out fairly soon. Perhaps that’s not the case? My only concern was that these changes were around the corner.

Not sure when and even so, I would assume that some things will stay the way they are.
The things that change can be adjusted in the guides. Just like they have to be adjusted in the Docs.

iOS Installation Docs updated and enhanced as part of this effort.  Feedback welcome on #9

@kristfal @nitaliano When you guys get a min check out the new docs updates by @ferdicus and #9 .
Also, it looks like there is some activity going on at the nitaliano/react-native-mapbox-gl repository.  Should we make it more clear on that repo to encourage moving to this one? Maybe? There might be some confusion as to which repository is intended to be the "official" unofficial repo for the react-native-mapbox-gl efforts?

@systemlevel thanks for your contributions, it is now merged. I haven't heard anything from Nick in a while. As soon as we get the V7 rebase into master here and battle test it a bit, we'll do an "official" unofficial migration of the repo (unless Nick gets back and objects for any reason).
I'll keep this issue open for now in case of more Doc improvements are wanted

Docs are better than ever, thanks for your contributions. I'll close this issue, but feel free to open issues for specific topics. PRs are more than welcome.


Also exclude omitted dependencies

What's changed?

What's your motivation?
When conflicts occur dependencies are omitted; when we then exclude from the conflict, the omitted dependency can resurface. The goal of ExcludeDependency is to fully exclude a dependency, not to see the omitted conflict being used. We should then also add <exclusion> where dependencies are omitted.
Anything in particular you'd like reviewers to focus on?

Anyone you would like to review specifically?

Have you considered any alternatives or workarounds?

Any additional context

Checklist

[ ] I've added unit tests to cover both positive and negative cases
[ ] I've read and applied the recipe conventions and best practices
[ ] I've used the IntelliJ IDEA auto-formatter on affected files

Replaced by https://github.com/openrewrite/rewrite/pull/4563


add microtx listener and refactor live queries to use it

We went to another direction, closing this, not needed anymore


Write a TypeScript program to convert seconds to days

Description
Write a TypeScript program to convert seconds to days
1 day = 24 hours = 1440 minutes = 86400 seconds
Input  : 432000
Output : 5

How to contribute

Save the solution in program/ConvertSecondsToDays.ts file
Add ConvertSecondsToDays.ts file in convert-seconds-to-days folder

!assign


May provide M1 support SDK?

Hi naver development team,
May provide M1 support SDK? our project is blocked to do development on M1 machine.
Currently naveridlogin-sdk-ios SDK lack of architecture for arm64 simulator, so it's unable to do development with M1 macBook.
Please help to release your SDK with M1 architecture machine, the SDK should auto contain arm64 simulator.
Thanks and regards,
Allen

Hello any body here can give response for issues?
@ksmail13
@beanmilk
@mydamyda
@reflect87
@HanBin-Kim

@LeePoHsien
Hello,
m1 architecture support is being prepared.
Before that, please use Rosetta.
It will be distributed during this month.
Thanks

please update this library …

많은 SDK 들 중에 정말 딱 이거 하나만 M1 지원을 안하고 있습니다. M1 대응을 언제로 생각하고 있으신지 궁금해요.

@HanbinKim @beanmilk
M1 대응 언제 될까요 ㅠㅠㅠ xcode simulator 에서 작동이 안되네요 ㅠ,ㅠ


Access Denied Nextjs : No solution seems to work

Before opening, please confirm:

[X] I have checked to see if my question is addressed in the FAQ.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
No response
Region
No response
Amplify Console feature
Not applicable
Describe the bug
I get the following error
AccessDenied: Access Denied
at Request.extractError (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/services/s3.js:699:35)
at Request.callListeners (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/request.js:688:12)
at Request.callListeners (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
at Request.emit (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/request.js:688:12)
at Request.callListeners (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
at callNextListener (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/sequential_executor.js:96:12)
at IncomingMessage.onEnd (/root/.//node_modules/@sls-next/aws-s3/node_modules/aws-sdk/lib/event_listeners.js:335:13)
at IncomingMessage.emit (events.js:326:22)
at IncomingMessage.EventEmitter.emit (domain.js:483:12)
at endReadableNT (_stream_readable.js:1241:12)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
code: 'AccessDenied',
region: null,
time: 2021-11-29T07:36:37.023Z,
requestId: 'FP66RQBNXGJJK7K0',
extendedRequestId: 'Hwt6vz2mu8pc3pyipBngfXRbd/eeVyw8XYUZWPNhF4fkX4f+2aSBP8XvwryEWNQ+vsxz+oITfw4=',
cfId: undefined,
statusCode: 403,
retryable: false,
retryDelay: 22.001353601658803
}
Expected behavior
The app should build
Reproduction steps
Deploy any sample nextjs app through aws amplify console.
Build Settings
version: 1
frontend:
  phases:
    preBuild:
      commands:
        - npm ci
    build:
      commands:
        - npm run build
  artifacts:
    baseDirectory: .next
    files:
      - '**/*'
  cache:
    paths:
      - node_modules/**/*

Additional information
I have tried all the solutions including:

extending permissions to admin
Adding inline policies
Adding individual policies
Nextjs version check

I had this issue three times and all times for different reasons.
Initially it was because of permissions issues, but seems like you already tried that.
Second reason was that for some unknown reason my root account did not have permissions to enable "enable transfer acceleration" on the deployment bucket. I have contacted support and they gave permissions to my account to enable this feature.
Third reason happened after some limitations were set on my account because of suspicious activity. Most of the limitations were lifted but somehow I still did not have access to cloud front distribution.

Hi @BahauddinAziz can you provide your AppID and the region you're trying to deploy your app in?

I've been having the same issue for the past day. Just started happening out of nowhere.
AppID: dwfmevspagm4e
Region: eu-central-1

@sananbintahir can you make sure the IAM role associated with your app has the right permissions? Please see reference: [ERROR] AccessDenied: Access Denied

@sananbintahir can you make sure the IAM role associated with your app has the right permissions? Please see reference: [ERROR] AccessDenied: Access Denied

Yes, the IAM role has admin permissions, so that’s not the problem. The issue is only happening with newly connected branches, the ones that were already connected from more than a day ago are building fine

Hi @sananbintahir, I was able to successfully build my SSR app on new branches. Can you provide reproduction steps so we can understand this behavior?

@hloriana I had to contact aws support yesterday to resolve the issue. According to support, “The reason behind that behavior was a trust level issue on your AWS account.”
After support increased the trust level on my account, my builds started working again. Still not sure what caused this trust issue, will follow it up with support to figure it out. Weirdly enough, every AWS service, besides the SSR deployment on amplify was working fine for me.

Hi @sananbintahir okay glad to hear AWS Support was able to unblock you. I'm going to close this issue but if you run into anything else or have a question feel free to open a new issue. Thanks!


Use the android Work version of the connector

Required changes to use the connector library with the Android Work implementation

Closing like the connector PR


Set names of Locust classes to run from web or from master to slaves

Summary
Set the names of Locust classes to run, either from the web interface or from the master command line.
This change means that slaves can be started without specifying which Locust classes they will run. Instead they are instructed to hatch only certain Locust classes by the master. The list of classes can come from the master command line or from the web interface.
Web mode
A set of slaves is started with a locustfile that contains a number of Locust classes. The master is started in web mode with the same locustfile. The web form includes a text box with a comma-separated list of available class names.
If a subset of Locust class names is entered in the box, only those classes are run by all the slaves. Unrecognised strings are ignored.
A subset of Locust classes can also be run in local mode.
Non-web mode
In non-web mode, slaves quit when the master quits.
But slaves are instructed which Locust classes to run by the master so they can be started with the same command line. For example, a slave can be started with:
locust --slave --master-host=$MASTER_HOST -f locustfile.py

and will run different Locust classes in these two cases:
locust --master --host=$TARGET_HOST -c 10 -r 1 -t 20m -f locustfile.py Locust1
locust --master --host=$TARGET_HOST -c 10 -r 1 -t 20m -f locustfile.py Locust2

This makes it possible to have self-restarting slaves (e.g. in a script loop).

Hi!
Thanks for your contribution! Unfortunately this seems to me like a too narrow/rare use case, especially since the slaves will still need to be aware of all the locust classes at startup.
I'm -1 for this, it just doesn't motivate the increased complexity.
If you need an easy way to spawn slaves with the correct locust then maybe have a look at https://github.com/SvenskaSpel/locust-swarm

Interesting that this is considered a rare use case.
In our usage, we create one master and 20 slaves in AWS Fargate. They all load the same locustfile with a set of 5 different Locust classes. We can use this same setup to select different load scenarios based on Locust classes, without having to redeploy masters and slaves. We will continue doing this using our own fork of the code.
I had not heard of locust-swarm or locust-plugins before. Perhaps you could add links to the Locust README.


How to solve the problem that "persist "does not exist?

Environment: vue3.2.25+pinia2.0.13+vite2.9.7+ts4.5.7
export const useUserStore = defineStore({     id: 'user',     state: () => {         return {}     },     persist: true //  'persist' is not in type 'DefineStoreOptions<"user", {}, {}, {}>" })
A parameter of type "{ id: "user"; state: () => {}; persist: boolean; }" cannot be assigned to a parameter of type "DefineStoreOptions<"user", {}, {}, {}>".
Object literals can specify only known properties and 'persist' is not in type 'DefineStoreOptions<"user", {}, {}, {}>"
Thanks for any reply

Hii @prazdevs , I am having this same issue. any idea how i could solve this problem?
Environment: vue3.2.39+pinia2.0.22+pinia-plugin-persistedstate2.2.0+vite3.0.9+vite-plugin-ssr0.4.38
Thaks beforehand!

Hi,
I have try with all possible configurations (see docs on usage), including the one you mentioned in this thread, and I still have a "persist does not exist" error.
Config:

vue 3.2.43
pinia 2.0.23
vite3.2.3
ts 4.8.4
pinia-plugin-persistedstate 3.1.0

Any idea why?

Hi @Kagigz could you provide a simple reproduction repo so i can look into it ?

@prazdevs I just created the reproduction repo, and saw I didn't have the error there.
I guess it was just a vscode thing, because after restarting the editor on my previous project, I didn't have the error anymore.
Sorry for bothering you!

👍 glad it's fixed


rotated lighthouse crematorium by 180deg

About the PR
Fixes https://github.com/space-wizards/space-station-14/issues/10160
I did it properly this time. Sorry for having to open a second PR.
Screenshots

Changelog

:cl:

fix: lighthouse crematorium now opens properly

Closing this in favor of #10229, as it will definitely cause conflicts. Sorry!

Apologies for that by the way; I've properly credited you in #10229 !


functional: fix path to user_data to /var/lib/coreos-install

Since CoreOS alpha (1000), coreos-cloudinit doesn't seem to watch
on /media/configdrive/openstack/latest/user_data. That's why
functional tests haven't been running, as systemd-nspawn container
runs without any configurations.
Fix it by changing into /var/lib/coreos-install/user_data.
Fixes: https://github.com/coreos/fleet/issues/1532
/cc @kayrus

I don't really understand how https://github.com/coreos/coreos-cloudinit/pull/419 is supposed to have affected this.. but if this change works, then lgtm

I also don't know how fleet's functional test was originally written. Just for trying to understand the reason in the background:

coreos-cloudinit had been watching for 2 different paths: /var/lib/coreos-install/user_data (a single file), and /media/configdrive (a non-empty directory). According to a comment, the latter seemed to have existed only for backward compatibility.
On the other hand, for some reason, fleet has been relying on the mechanism of writing yaml config into /media/configdrive/openstack/latest/user_data, which could be then processed by user-configdrive.path. IMO this was a wrong approach to begin with, because inside the systemd-nspawn container, /media/configdrive is not mounted at all. Writing anything into a non-mounted directory seems to be a flaky mechanism after all.
Then the user-configdrive.path was removed via https://github.com/coreos/coreos-cloudinit/pull/419 , so that the unit didn't get conflicted with the new behavior of systemd v229. Now coreos-cloudinit is only able to watch for /var/lib/coreos-install/user_data. This change makes sense, although it suddenly broke the original expectation of fleet.

So the right fix is to change the path to user_data to the correct one, /var/lib/coreos-install/user_data. I suppose, it should have been like that in the first place.
I'm going to merge it soon.

SGTM


Agree on whether or how to handle "official" charts in hub

@prydonius Wow somehow missed your reply. I believe this was from a charts chat meeting, and related to charts hosted by orgs who also maintain the application installed by the chart.

I think the question raised in this issue is important.
Once the stable repo is no longer available, how will a user choose between multiple charts for the same product.  For example, if a user wants to install Grafana, as of today, HelmHub provides:

bitnami/grafana
incubator/grafana (I assume this will go away)
flagger/grafana
cloudposse/grafana
stable/grafana (I assume this will go away)

What criteria should a user base themselves on to choose between these?
I think this likens to choosing an image on Dockerhub.  But Dockerhub has official images https://docs.docker.com/docker-hub/official_images/. Then again, there is no official image for Grafana on DockerHub, but there is a grafana/grafana.  As a user I assume that the grafana user is legit and therefore that I can trust their image (maybe I'm wrong?)
I guess this comes down to: will there be some kind of vetting process for big name charts?

The grafana/grafana image is real - so it is "official", i.e. produced by grafana-project. Choosing the most attractive chart could depend on how it is designed - but it would be very interesting to have statistics for downloads of charts in order to be able to quantify their popularity.

I just posted this comment and figured it's probably more of a decision for the Helm Hub owners than the stable repository owners.
I think @marckhouzam makes a very valid point, but as of today stable looks official, so as a user I would choose stable/grafana. The real problem will emerge once the stable repository is de-listed. Unless you're familiar with one of the vendors, it will be quite hard to decide which chart to use.
I think official charts would be immensely valuable for the Helm community. It would give the charts and Helm itself more credibility. If you're also able to decide on some strict standards for official charts that make it easy to reuse configuration between different charts, that would improve the user experience even further. (Most stable charts are already following some standards. It's generally possible to copy ingress configuration between charts and persistence always looks very similar. However, there are more things that could be standardised.)

On Docker Hub it is very easy to identify official images. I think a similar system needs to be established on Helm Hub, before de-listing the stable repository. There should also be a clear migration path for chart owners in this repository, to convert their charts to official Helm charts. On Docker Hub, official images are in the root of the repository. I don't know how easy that would be to implement for Helm Hub, but it seems advantageous to use the same pattern as Docker Hub.

As mentioned in the comment, I made on the issue in the charts repository, I think it's critical that we have such a system in place on the Helm Hub before the stable repository is de-listed. I don't know what governance you have in place for managing this kind of decision, but I'm willing to get involved to make this happen.

I think @marckhouzam makes a very valid point, but as of today stable looks official, so as a user I would choose stable/grafana. The real problem will emerge once the stable repository is de-listed. Unless you're familiar with one of the vendors, it will be quite hard to decide which chart to use.

There is actually ongoing efforts to make some chart hosted in their upstream project repository as much as possible (for my parts, kubernetes-dashboard, elasticsearch for now, probably oauth2-proxy or others in the near future, and I've seen discussions about grafana / prometheus-* as well).
This solves the problem of trust and make them really official, even in the case that they are maintained by community like kubernetes-dashboard, or prometheus-operator in its future home.
About the "officialness" of a chart, I suppose an "official" label for charts would be a good idea.

@desaintmartin I think that is great and it does help making charts look more credible. Although I still think that a curated list of official charts managed centrally by the Helm Hub would be great. They would still be maintained by their respective projects, but vouched for by the Helm Hub.
Compliance with standards could be verified by automated testing. So the only work, for the central team, would be to maintain those automated tests and add/remove charts from the official list, based on compliance and other criteria.
I do agree that https://github.com/helm/charts should be deprecated and de-listed, since it's not a great way of managing a list of official charts, but we need to make sure that there is something there to replace it. New chart repositories may be created organically, but without anything to denote them as official, it may be hard for the community to know which one to use and which one to focus development efforts on.
One of the things I dislike the most about Ansible is how hard it is (impossible?) to find official looking roles on Ansible Galaxy. Everything looks like it's just written by some random guy on the Internet and nothing looks quite official (I suppose there might be exceptions). Often times you end up writing your own custom roles, because you didn't find anything that looked trustworthy enough. (Disclaimer: I have very limited experience with Ansible and Ansible Galaxy. Perhaps it's not as bad as my impression.) Regardless of whether that is just my shallow first impression of Ansible Galaxy, I don't want anyone to have such a first impression of the Helm Hub.

We are looking at migrating from the Helm Hub to the Artifact Hub. This issue has already been file there at https://github.com/artifacthub/hub/issues/542

Closing as the Helm Hub now redirects to the Artifact Hub. The Artifact Hub has an issue for this.


Add thermal reading capabilities for CPU in kernel

Note before merging: to verify if we want to bump PR manually or not.


Conflict between multiple driver instances on the same page with distinct configurations

I'm encountering an issue while attempting to create two separate driver instances on a single page, each with its unique configuration set. However, it seems that the settings for the second instance are overwriting those of the first one.
For instance, if I create the first instance with config such as overlayColor: red, animate: true, the second instance with overlayColor: blue, animate: false. Both instances use overlayColor: blue, animate: false instead of the configs I passed to each one of them.
Is there any recommended approach or workaround to ensure that each driver instance maintains its unique configurations without interfering with others?

did you find a solution to this ?

did you find a solution to this ?

A solution to this is to always initialize the driver inside the eventListener callback.
Instead of this:
const driver1 = driver({
  steps: [
    {
      element: '#counter',
      popover: {
        title: "Welcome to the tour",
        description: "Welcome to the tour",
        align: 'end',
        side: 'bottom'
      }
    },
    {
      element: '.icon-toggle-right',
      popover: {
        title: "Welcome to the second tour",
        description: "Holla la tour",
        align: 'end',
        side: 'left'
      }
    }
  ]
});

const driver2 = driver({
  overlayColor: 'yellow',
  overlayOpacity: 0.2,
  steps: [
    {
      element: "#vite-logo",
      popover: {
        title: "Here is Vite",
        description: "A tool for building web applications",
      }
    },
    {
      element: ".vanilla",
      popover: {
        title: "Here is JavaScript",
        description: "A programming language for the web",
      }
    }
  ]
});

document.querySelector('#tour').addEventListener('click', () => {
  driver2.drive();
});

driver1.drive();

Do this:
const driver1 = driver({
  steps: [
    {
      element: '#counter',
      popover: {
        title: "Welcome to the tour",
        description: "Welcome to the tour",
        align: 'end',
        side: 'bottom'
      }
    },
    {
      element: '.icon-toggle-right',
      popover: {
        title: "Welcome to the second tour",
        description: "Holla la tour",
        align: 'end',
        side: 'left'
      }
    }
  ]
});

document.querySelector('#tour').addEventListener('click', () => {
  const driver2 = driver({
    overlayColor: 'yellow',
    overlayOpacity: 0.2,
    steps: [
      {
        element: "#vite-logo",
        popover: {
          title: "Here is Vite",
          description: "A tool for building web applications",
        }
      },
      {
        element: ".vanilla",
        popover: {
          title: "Here is JavaScript",
          description: "A programming language for the web",
        }
      }
    ]
  });
  driver2.drive();
});

driver1.drive();

This way the driver2 object doesn't overwrite the first one. I think this is worth mentioning somewhere in the documentation.

I actually used the setConfig instead of initializing a new driver. I had a global driver and a bunch of configs that I set whenever I need them.

I actually used the setConfig instead of initializing a new driver. I had a global driver and a bunch of configs that I set whenever I need them.

Do you get the ability to call driver's methods individually(per config)?

Do you get the ability to call driver's methods individually(per config)?

I'm not following. I just call the functions from the driver() instance after I set the config. so far I haven't faced any issues with that. is this what you meant ?

Do you get the ability to call driver's methods individually(per config)?

I'm not following. I just call the functions from the driver() instance after I set the config. so far I haven't faced any issues with that. is this what you meant ?

Oh I see, by invoking the functions from driver() after setting the config, the newly set configuration takes precedence over the previous ones. Then what you're suggesting is an alternative way to achieve the desired result.

what I suggested was the only way I found that worked for my situation. but depending on the use case, it can be an alternate implementation.


#25 Hopefully fixing problem that caused process.…

…exit not being properly called.

Codecov Report

Merging #26 (c79ce1a) into main (b50bcc9) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #26   +/-   ##
=======================================
  Coverage   99.60%   99.60%
=======================================
  Files          14       14
  Lines        1021     1021
  Branches      162      162
=======================================
  Hits         1017     1017
  Misses          4        4

Flag
Coverage Δ

config
100.00% <ø> (ø)

main
100.00% <100.00%> (ø)

resource-pool
100.00% <ø> (ø)

state
100.00% <ø> (ø)

typed-sql
98.77% <ø> (ø)

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

Impacted Files
Coverage Δ

main/src/main.ts
100.00% <100.00%> (ø)


Bug in handling name change

On ME screen the user can change his name. If he enters an empty string Guest is being assigned automatically. So far so good. But now if he clicks the 'Guest' to change it again, the input is not editable anymore and the user cannot change the name. Tested with https://letsmeet.no/.

I think it is something to due with the store.

@Astagor  Can you retest it.
It seems it is working now on letsmeet.no

I will close I see this is fixed..

Yes, this has been fixed.


Search result corrupts HTML page

You revoke the corruption when search text changes and Esc pressed. But, Esc pressing just closes the popup and does not revoke the match results in my case. I have to enter some text into the search bar to remove it before closing.

I have debugged a little and noticed that you catch the messages in content.js. The code
chrome.runtime.onMessage.addListener(function (request, sender, sendResponse) {

receives cleanup message when you type some search string but nothing arrives on Esc, despite you send the clean.

The easiest solution that worked for me was to

stop doing anything on Esc
add a Close button to the popup with the following event

        closeButton.addEventListener("click", function () {
            clear(); setTimeout(function(){window.close()}, 0)
        })

where clear() is
		function clear() {
//            if (tabStates.isSearching(id)) {
                setSearching(id, false, tabStates);
                Utils.sendCommand("clear");
//            }
		}

start using it whenever you need setSearching(false);send('clear'); instead of duplicating your code.

The working alternative that would automatically clean the search one popup closed is to use a timer instead of the Close button. You send the ping messages periodically from popup.js to the content.js. When "search" is received, content.js starts a timer, which runs clear() on timeout. The timer is restarted on arrival of ping. This will postpone the clean until popup is really closed. Content.js will detect this by the timeout monitor and clean up the search. I did, it, works.

So when the search bar is focused and I hit Esc, the search clears as expected. When I click the "Next" button and then hit escape, only the popup closes, and the search stays. I think the solution here would just be to add a keypress handler on both buttons that clears when Esc is pressed.

At first, it is false. I hit enter to search, focus stays in the input input. I also mouse click there to ensure that and hit Esc. Only popup but no search results disappear. Secondly, your desire to close on Esc or keydown suggests that you want to clean up whenever popup disappears. However, popup disappears without any Esc or button click. It is just Chrome design. Popup disappears when another window gets the focus. It is therefore makes no sense to use keydown or esc to cleanup. The only reliable keydown is a special Close button that will both clear the result and close the popup window.

If we decide to clear the search on any close of the popup, then we should probably do something like this.

If we decide to clear the search on any close of the popup, then we should probably do something like this.

Chrome generates on window.unload event when popup is closed
We must use ports and polling instead

This is actually the workaround that I used. My timeout solution uses both polling (ping) and ports (send message).


"You can easily extend the application with new data readers to support other data sources. See app.data.readers"

I am sorry but I am not well versed with Scala.
Can you please elaborate on how should one go about to use this project to generalise on their own documents.
First and foremost, since the V1 dataset is easier to understand, I went with that.
I have augmented the vocabulary with new words of my documents' vocabulary (that was not present in the original vocabulary).
Moreover I trained the Candidate Ranking on the V1 dataset with the augmented vocabulary and the answers.label.token_idx augmented with my documents as possible answers.
Further, I made the necessary changes in the Ranking and Retrieval configuration files.
On typing phrases copy pasted from my own documents, the model is not able to pin point the text from my documents but rather produces results not so relevant to the phrase searched.
What am I doing wrong??

In this case, I would first recommend testing the candidate retrieval on its own:
http://<candidate-retrieval-url>/query?q=<yourquery>&n=10

If this already does not return you desired documents when entering the document itself as a query, there might be something wrong with indexing (old index etc.).

Hi @arueckle
Thank you so much for the response. The json that appears in the URL you mentioned, helped me a lot. I finally got it working on my own documents. The code is in this project is beautifully written. Cheers!!


Update create_and_invoke_agent_with_kb.ipynb

To create S3 bucket outside of us-east-1 region
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Fixed in latest PR merge, therefore, closing this one.


cleanup(scap): remove platform handle from scap_t

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup
/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area API-version

/area build

/area CI

/area driver-kmod

/area driver-bpf

/area driver-modern-bpf

/area libscap-engine-bpf

/area libscap-engine-gvisor

/area libscap-engine-kmod

/area libscap-engine-modern-bpf

/area libscap-engine-nodriver

/area libscap-engine-noop

/area libscap-engine-source-plugin

/area libscap-engine-savefile

/area libscap-engine-udig

/area libscap

/area libpman

/area libsinsp

/area tests

/area proposals

Does this PR require a change in the driver versions?

/version driver-API-version-major

/version driver-API-version-minor

/version driver-API-version-patch

/version driver-SCHEMA-version-major

/version driver-SCHEMA-version-minor

/version driver-SCHEMA-version-patch

What this PR does / why we need it:
Another small step towards untangling platforms from libscap: remove the platform handle from scap_t and move it to the sinsp object. This is a fairly large PR as it touches a lot of places but the changes are basically:

take the platform handle directly in all scap_platform_api wrapper functions
explicitly pass the platform pointer to the savefile engine
move platform initialization/cleanup to sinsp (which now owns the scap_platform pointer)

see https://github.com/falcosecurity/libs/pull/1401 for the somewhat bigger picture
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

BREAKING CHANGE: all scap_platform_api functions now take a `scap_platform*` rather than `scap_t*`
BREAKING CHANGE: scap_open no longer takes a `scap_platform*`
BREAKING CHANGE: m_h->m_platform is no longer valid inside sinsp, use scap_get_platform() instead

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gnosek
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [gnosek]

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

/milestone 0.14.0

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, gnosek
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,gnosek]

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

LGTM label has been added.  Git tree hash: 21786e052dd043c4fd362e17d18025f3337fafc3

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, gnosek
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,gnosek]

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


Google Pay OR_BIBED_07

Describe the bug
When completing a purchase through Google Pay, a small modal with the following error pops up:
Request Failed. An unexpected error has occurred.. Please try again later. [OR_BIBED_07]
It might be parallel to this issue which shows the same err, and references a "payment configuration JSON". Is this something the lib creates?
Viewing the logs from adb logcat shows the following logs being executed with each click of the GooglePayButton and the throwing of the err:
11-22 14:24:56.392 10666 10666 I GoogleInputMethodService: GoogleInputMethodService.onFinishInput():3293
11-22 14:24:56.392 10487 31503 I GCM.HTTP: Last HTTP status code for blocked entry: 500
11-22 14:24:56.392 10487 31503 W GCM.HTTP: HTTP request blocked due to automatic backoff: https://payments-pa.googleapis.com/payments/apis-secure/ui2/buyflowservice/initialize
11-22 14:24:56.392  4006  7313 W GoogleURLConnFactory: Blocked by temporary_blocked2: https://payments-pa.googleapis.com/payments/apis-secure/ui2/buyflowservice/initialize
11-22 14:24:56.392 10666 10666 I GoogleInputMethodService: GoogleInputMethodService.onStartInput():1981
11-22 14:24:56.393 10666 10666 I DeviceUnlockedTag: DeviceUnlockedTag.notifyDeviceLockStatusChanged():79 Notify device unlocked.
11-22 14:24:56.394  4006 20227 E O2NetworkAction: Network Error: java.util.concurrent.ExecutionException: com.android.volley.NoConnectionError: xzl: Blocked by rule: temporary_blocked2
11-22 14:24:56.807 16973 17007 D OpenGLRenderer: endAllActiveAnimators on 0xb400007c7489fcf0 (RippleDrawable) with handle 0xb400007b848a45f0
11-22 14:24:56.808  1792  4606 W InputManager-JNI: Input channel object 'de73e91 com.google.android.gms/com.google.android.gms.wallet.activity.GenericDelegatorInternalActivity (client)' was disposed without first being removed with the input manager!
1

To Reproduce
Reproducing the err is difficult, as different devices we have tested with reported different errs, all using the same builds and similar versions of android.
We have implemented a google play button exactly as outlined in the docs: initialising stripe appropriately, creating a GooglePayButton, and presenting google pay when the button is clicked. We deployed our app to the app store for beta testing.
Expected behavior
Google Play Button initiates and completes the payment.
Screenshots

Smartphone:

Device: Google Pixel 5
OS: Android 12

Additional context
The payment flow works fine when running the app on the Android Emulator (API Version 30), however once deployed to the app store, throws the err.

Hi @SamKomesarook, do you get any WalletMerchantError entries in the logs? These contain more details about the issue.

Hey @JlUgia, I've run the log command listed in the link you sent, reproduced the error, and no logging appears in my console :(

Turned out this issue was related to not initialising the Google Pay API for this app. Strange that the message was not clearer to reflect that, as some other tests showed a different err with more specific wording.

Turned out this issue was related to not initialising the Google Pay API for this app. Strange that the message was not clearer to reflect that, as some other tests showed a different err with more specific wording.

Hi, I'm having very simillar issue, what exactly do you mean by "not initialising the Google Pay Api for this app"? I went thorugh the official guide, added all the dependencies and edited the manifest file. Are there any extra steps?

@weeks6 Yeah I used this guide, specifically initialising it in the console. I kinda think this stuff should be added to the docs, as it isn't mentioned anywhere I could find either in this lib or in generic stripe docs...

Hey guys!, Im having the same issue and I don't know if the documentation changed or I'm doing something wrong. But could you explain here what are the steps to take please.
I've tried adding my stripe public key to the "Encryption Keys" y the direct "integration section" in business console and I get and error that it is not coded the right way.
I must be doing something wrong but can't find how to set up this. Thanks a lot for time and effort

@Flucadetena can you post the err you get in the business console? You mean the encryption keys you created were not valid?

Hi @SamKomesarook of course!
This is the error (I have erase the name sensitive data):

The key I pasted was the pubishable key from stripe. I've you need me to explain anything else let me know.

@Flucadetena have you encoded the API key in base64 and tried saving that? Try openssl base64 -in <infile> -out <outfile> from the command line, and copy the contents of the outfile as your public key.

Guys, just want to confirm - even if my company already uses Stripe to Apple Pay and now we are adding Google Pay, do we still need to do Google Business Console set up?

Hi!
If you are operating in PRODUCTION you need to add a merchantId that is valid and has been approved in Google Pay's Business Console in your configuration.

Hi! If you are operating in PRODUCTION you need to add a merchantId that is valid and has been approved in Google Pay's Business Console in your configuration.

Hi, I have added a valid merchantId in my app, where do I put the merchant id for approval in the Google Pay Business Console? Kindly assist

@samcampisi Where did you upload your AAB/APK, did you upload it to the Closed Testing Track? Or do you have to do it to the Releases?

If anyone still having this issue. I got resolved by creating a singned APK instedad of using ADB.
After your app has been approved, test your integration in production by setting the environment to GooglePayEnvironment.Production, and launching Google Pay from a signed, release build of your app. Remember to use your live mode [API keys](https://stripe.com/docs/keys).

My app is not yet approved in Google Pay Console.  Am I able to test using ENVIRONMENT_TEST = 3?
Or also need to wait for approval to test this?

For TEST environmnt, you don't need an approval.
Please read this documentation. https://stripe.com/docs/google-pay


pin period to top of menu + readme fixes

Love your work!! This is mostly a quick fix for my buddy, feel free to use or to not.
Thanks so much for making this and making this open source, its super rad!

Hey, thanks for the contribution! This is actually how it worked initially but it turned out that it really wasn't great when playing on smaller screens (phones, tablets and even some smaller laptops). So I probably won't merge this as is but I'll see if I can make it work like that on larger screens :+1:


Very slow keyboard on iOS

Details
Hello,
We have an app on the store, currently on Flutter 3.0.0, which seems to have severe keyboard lag on iOS.
I'm not sure if it is an iOS issue, or an app issue. Sometimes restarting the app solves the issue temporarily.
I have attached videos showing the issue.
Does anyone else have this issue, or knows what could cause it?
Thanks
Target Platform: iOS
Target OS version/browser: 15
Devices: iPhone 13
https://user-images.githubusercontent.com/3032294/175525574-ce657962-5c8c-41cb-81a6-74a3f61433fc.mp4
https://user-images.githubusercontent.com/3032294/175525586-4f840d80-18a3-4ca1-b589-67e44b3bc1b9.MP4

That's odd. I've just published an iOS app on 3.0.0 and was not facing such issue.
I'm kindda new on Flutter, but my application extensivelly uses the keyboard... Have you tried it on another iOS device? Heve you tried it on MacOS? Are you doing something that forces the layout to be rebuild every frame/time?
I had similar problems with other widgets when I accidentally managed to force redraws/rebuilds every frame, or even setStates that I didn't manage correctly. Could this also be your issue?

Hello @vixez. Are you running code in onChange that might be blocking the thread? Also, please provide a minimal, reproducible example so that we can verify this issue.