Warnings

Hey man thanks for you package, However i deploy it on heroku it take the screenshot but it logs some error after that:
~ $ snap-tweet https://twitter.com/jack/status/20
snap-tweet https://twitter.com/jack/status/20
✔ 📸 Snapped tweet #20 by @jack
/app/.heroku/node/lib/node_modules/snap-tweet/node_modules/yoga-layout-prebuilt/yoga-layout/build/Release/nbind.js:53
        throw ex;
        ^

Error: spawn xdg-open ENOENT
    at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
    at onErrorNT (internal/child_process.js:467:16)
    at processTicksAndRejections (internal/process/task_queues.js:82:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
    at onErrorNT (internal/child_process.js:467:16)
    at processTicksAndRejections (internal/process/task_queues.js:82:21) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'spawn xdg-open',
  path: 'xdg-open',
  spawnargs: [ '/tmp/bcd1cc484539c835853116333adea229/snap-tweet-jack-20.png' ]
}

I think that's happening because snap-tweet by default saves the image to a temporary location and opens it to show you the result. I deliberately designed it to be slightly more user friendly but I guess it doesn't work a terminal-only environment.
You can specify a output directory to prevent this behavior.
snap-tweet https://twitter.com/jack/status/20 -o .


Implement cvlac plugin with yuku output

Yuku generates a mongodb with the information from a scrapping of cvlac.
Right now the plugin uses an old file. It has to support the information from mongodb

implemented in all the minciencias plugins


Composite primary keys fail in index.sql

The composite primary keys on indexes.sql are not unique and are not reliable not-null.

Could you please elaborate?

Are you seeing them fail on specific data?
What does "not reliable not-null" mean?
What kind of solution would you suggest? (automatic serial?)

Thanks!

Hello. I had the same issue back when I was indexing. (don't remember the exact error message, though).
I remember I had to remove all duplicate rows from all intermediate tables to make indexing possible.

Hey! This was a bug and I fixed it a time ago.

Hello. I have a similar issue with index creation: ALTER TABLE ERROR:  could not create unique index "master_artist_pkey" DETAIL:  Key (master_id, artist_id)=(59474, 1355202) is duplicated.

Hi, this is a different thing though. But let me see, you can always drop the unique constraint and have the performance improvement of the index anyway.

So yeah indexes were quite broken 😂 I'll be doing a release soon.


fix: NPE issue while copying in git-theming migration

Description

Fix the NPE issue in theming while copying the properties.

Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Locally

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

/ok-to-test sha=64a53c8


Update "Continue Move"  button to redirect to last page not completed

Description
The "Continue Move" button was not redirecting to the last part completed in the HHG flow. Update to redirect to the last page that the user did not completed in the flow.
Setup
make client_test
make e2e_test

Login to the system as a new service member
Create a profile
Create an HHG move and complete at least one part the flow (i.e through pickup address).
Log out
Log back in and click "Continue Move". You should be taken to the last page in flow that is not complete.

Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story

Added e2e test. Let me know what you think.

@lynzt thanks for taking a look. I'm not seeing the local failure auth/logout issue. I tried just running that one test and it looked ok (it's a completely separate move, so shouldn't depend on the prev shipment test). Also, like you suggested, i added a cmd in cypress/support/commands.js to remove window.fetch for a single test.
I wanted to make sure to address the "NOTE". I ran the tests locally in addition to on ci? Is there anything else that you'd suggest?


Certificate recognition fails with dashed domain

My container keeps generating snakeoil certificates for my XMPP domain, even though I have supplied the correct environment variable.
The reason might be that in the 01_write_certifiates_from_env.sh script, it is checked if the variable is set, however it fails due to bash not recognizing variables with dashes in their names. Maybe dashes could simply be replaced with nothing or another character.

Hi, this should be fixed in 563e57a8 and on docker hub :latest. Just replace dashes with underscores like the dots, i.E EJABBERD_SSLCERT_WWW_EXAMPLE_DOMAIN_COM for www.example-domain.com.

Unfortunately, it seems that there is another error, that prevents dashed domains from working. I tried it with underscores instead of the dashes with your latest version and it did recognize it correctly and jumped into the write_file_from_env() function as I could see the output in my log, however the generated certificate (/opt/ejabberd/ssl/example-domain.com.pem) did not contain the certificate data, but rather the path that I set the env variable EJABBERD_SSLCERT_WWW_EXAMPLE_DOMAIN_COM to.
I'm not sure whether or not this worked at some point, I'm getting an error though.
I think changing the echo in scripts/pre/01_write_certifiates_from_env.sh line 17 to a cat would fix this.

The environment variables for passing sslcerts to the container should include the cert & key and not a path to a local file. The script runs in container on startup an can not look outside of the container. But you can mount a local ssl directory into the container with your ssl certificates.
In example with docker-compose.yml:
ejabberd:
  image: rroemhild/ejabberd
  ports:
    - 5222:5222
    - 5269:5269
    - 5280:5280
  environment:
    - ERLANG_NODE=localhost
    - XMPP_DOMAIN=example-domain.com
    -<EMAIL_ADDRESS>
    -<EMAIL_ADDRESS>:password4321
    - EJABBERD_AUTH_METHOD=internal
    - "EJABBERD_SSLCERT_EXAMPLE_DOMAIN_COM=-----BEGIN CERTIFICATE-----
MIIFAzCCAuugAwIBAgIJAJoO+f1lEf0rMA0GCSqGSIb3DQEBCwUAMBgxFjAUBgNV
BAMMDWxvY2FsLWhvc3QuZGUwHhcNMTYwNTE3MjAzNjI5WhcNMTcwNTE3MjAzNjI5
WjAYMRYwFAYDVQQDDA1sb2NhbC1ob3N0LmRlMIICIjANBgkqhkiG9w0BAQEFAAOC
...
-----END CERTIFICATE-----
-----BEGIN PRIVATE KEY-----
MIIJRAIBADANBgkqhkiG9w0BAQEFAASCCS4wggkqAgEAAoICAQCcCPEU+PuD+zyk
xN4icj9LNpzWZnckYbiYG/94IQCv7Uj/H0j6vH5BTMwSJeppjT0neVgrdDPYWrCb
...
-----END PRIVATE KEY-----"

Ah ok, then I misunderstood how it is supposed to work. I mounted a volume on a local directory and wrote the path to this file in the variable. All good then, thank you!


Creation of a "Map Project Resource" that stores a map project file generated by the HydroShare GIS app

As discussed briefly in the weekly HydroShare call yesterday, the HydroShare GIS app has now been programmed to generate a map project file that essentially saves the current state of the app (this is documented in Issue #1079). Now, it is necessary to come up with the best way to enable this map project file to be stored as or connected to an official HydroShare resource type.
Some ideas that were presented yesterday are:

Create a Map Project Resource based off of the Generic Resource

Stores the map project file
Stores as metadata a reference to the resources that the map project consists of

Create a Map Project Resource based off of the Collection Resource

This is essentially the same as a collection, but with the additional, required map project file

Just leave it as a Generic Resource

It can then be added to a collection whose current resources are part of the map project

What would be the best implementation? This is now open to discussion. I'm calling out a few people specifically to get the discussion going. Please reference others who may have useful and/or authoritative input. @danames @zhiyuli @horsburgh @dtarb @selimnairb

I'd suggest going with the Map Project resource type. We can use it for
this app and for other apps that need a group of data resources with
symbology.
On Fri, Mar 25, 2016 at 2:53 PM shawncrawley<EMAIL_ADDRESS>wrote:

As discussed briefly in the weekly HydroShare call yesterday, the
HydroShare GIS app has now been programmed to generate a map project file
that essentially saves the current state of the app (this is documented in
Issue #1079 https://github.com/hydroshare/hydroshare/issues/1079). Now,
it is necessary to come up with the best way to enable this map project
file to be stored as or connected to an official HydroShare resource type.
Some ideas that were presented yesterday are:

Create a Map Project Resource based off of the Generic Resource

Stores the map project file
Stores as metadata a reference to the resources that the map
project consists of

Create a Map Project Resource based off of the Collection Resource

This is essentially the same as a collection, but with the
additional, required map project file

Just leave it as a Generic Resource

It can then be added to a collection whose current resources are
part of the map project

This is now open to discussion. What would be the best implementation? I'm
calling out a few people specifically to get the discussion going. Please
reference others who may have useful and/or authoritative input. @danames
https://github.com/danames @zhiyuli https://github.com/zhiyuli
@horsburgh https://github.com/horsburgh @dtarb
https://github.com/dtarb @selimnairb https://github.com/selimnairb
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/hydroshare/hydroshare/issues/1080

I have not received any feedback other than from Dr. Ames, so I have decided to move forward with what both him and I have discussed. I am going to create the Map Project Resource based off of the Generic Resource. Though I will create it to only hold a '.map' file, I have decided that I will not add the Map Project Resource to the "Create New" options, since it doesn't make sense that someone creates a '.map' file themselves and generates the resource themselves. This will protect the creation of a Map Project Resource by limiting its creation solely to the HydroShare GIS app.
For metadata, I will start off by having only a list of the resources that are part of the map project, likely made into a link that redirects to each resource's landing page.

@shawncrawley I am a little confused with "Map Project Resource based off of the Generic Resource." Do you mean you create a different resource type like MapProjectResource or just create a Generic Resource which holds the .map file? Note that you cannot add additional metadata elements as of now for generic resource type, so you probably meant the former, i.e., create a different resource type. @pkdash I am thinking if we can add a HStore field to BaseResource class which could hold some arbitrary key-value pair attributes for the resource, Generic Resource can probably serve this Map Project Resource use case well without requiring creation of a new resource type.

@hyi Sorry for the confusion. I guess I mean just created a completely resource type called MapProjectResource. I guess I just meant that it will be most similar to a Generic Resource, since there will not be much resource specific metadata associated with it, but there will be some. So yeah, creating a new resource type. But if we can all come to agreement on the HStore stuff, then I suppose I will not move forward in creating a new resource type quite yet.

@shawncrawley Got it. Thanks for the explanation. @pkdash @zhiyuli As part of collection resource type implementation, a collections ManyToManyField is added into BaseResource class. I think this collections field can be leveraged here for this MapProjectResource to hold a collection of all existing resources. Since collection resource type does not contain any content files, this MapProjectResource can be implemented as a GenericResource so it can contain the .map file while in the meantime use the collections field that was already added into BaseResource class as part of collection resource type work. This way, no new resource type is needed for this map project resource. What do you think?

Would the MapProjectResource contain any other files besides the .map file?

@pkdash No. At least not as we are currently envisioning this resource.

Since GenericResource takes any file, how we going to prevent someone adding other files to MapProjectResource?

If there as any additional metadata requirements or special file type requirements then may have to create a new resource type

@shawncrawley Is there requirement that this map project resource has to include only one .map file? If the map project resource can only be created programatically as part of HydroShare GIS app, this .map file will be included in the resource, and which can be consulted and used by GIS apps. Perhaps if owners of this resource want to add additional files such as a readme file, etc., into this resource, it is a good thing if we allow it.

@hyi Actually that is a good point. In fact, one feature that will likely soon be added to the HydroShare GIS app is the ability to export the map to a PDF or png image. It would be nice if that file could also be stored in the resource.

So I was just talking to @zhiyuli in person, and he was showing me how he leverages the ManyToMany field that was added to the BaseResource in the Collection Resource. Yet, in his case, he is leveraging that capability from his non-generic resource. That enables him to modify the landing page to display the associated resources as he dictates. If I understand correctly, @hyi, you are suggesting that I leverage the ManyToMany field, but not from a new resource type, but as a generic resource. How would that implementation look? I couldn't modify the landing page to reflect the associated resource types, could I? Does that make sense? Am I understanding this correctly?

@shawncrawley Yes, that was what I meant, to leverage that field as a generic resource. You map project generic resource model will have that collections/resources field which you can use to add all resources you want to include in this map project resource. Then you can modify resource landing page to check if this collections/resources field for generic resources is not empty, then you show the links to those contained resources. I think this should be doable without much issue.

@hyi Alright, that makes sense. I am thankful for the ideas and discussion. At this point, it would be good to hear any thoughts from @danames. However, since I believe he is out of town until Monday we can postpone this discussion until then.

If there is no need to list the map file within Hydroshare, one could store the json data in Hstore field once we add the HStore to BaseResource

The present approach for apps associates an app with a resource type. We
need to be able to launch the GIS App from a GIS Map resource. Hence we
need to create a new resource type (not just use Generic).
Also, let's consider if we can override the  "Create New" button to launch
the GIS app so a user can still create a new map in a natural way (hit
create new, get a blank map, add data to it, save it to a resource.)
On Fri, Apr 8, 2016 at 5:09 PM Pabitra Dash<EMAIL_ADDRESS>wrote:

If there is no need to list the map file within Hydroshare, one could
store the json data in Hstore field once we add the HStore to BaseResource
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/hydroshare/hydroshare/issues/1080#issuecomment-207642681

Soon apps can be associated with file types. I am working with @zhiyuli on this.

In the mean time, let's go with a new resource type for Map Projects.
On Mon, Apr 11, 2016 at 9:27 PM Pabitra Dash<EMAIL_ADDRESS>wrote:

Soon apps can be associated with file types. I am working with @zhiyuli
https://github.com/zhiyuli on this.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/hydroshare/hydroshare/issues/1080#issuecomment-208686806

It seems like this functionality is already in place with Generic Resource holding map project.  So @shawncrawley please close if you agree.

@dtarb Agreed. Though as you pointed out in our meeting, it might be best to implement the "Map Project Resource" as a Composite resource once that functionality is integrated into the hs_restclient. But for all current intents and purposes, this issue can be closed.


Fix reject of color hex that contains uppercase letters

Motivation and context

Encountered an error when inserting raw labels with colors. Even though CVAT itself produces color HEXes with uppercase letters, they are not accepted when manually put in the "raw" field. This gives the error: "Label "xxxx". Type of label color must be only a valid color string. Got value #2B7D70"".
By adding uppercase letters as a possibility in
How has this been tested?

Checklist

[ ] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Hi @abaart , do you have any plans about the PR? Why it is a draft?

Hi @abaart , do you have any plans about the PR? Why it is a draft?

Hi @abaart , do you have any plans about the PR? Why it is a draft?

Hey, I was a bit daunted by all the items on the checklist (such as writing tests etc), and had other priorities at the time. That's all ;)

Hi @abaart , do you have any plans about the PR? Why it is a draft?

Hey, I was a bit daunted by all the items on the checklist (such as writing tests etc), and had other priorities at the time. That's all ;)

BTW, the CI build failed because of a timeout.
The job exceeded the maximum time limit for jobs, and has been terminated.

BTW, the CI build failed because of a timeout.
The job exceeded the maximum time limit for jobs, and has been terminated.

BTW, the CI build failed because of a timeout.

There were some issues with travis. Now we've migrated to GitHub actions
Thx :)

BTW, the CI build failed because of a timeout.

There were some issues with travis. Now we've migrated to GitHub actions
Thx :)


Napsat články na blog

[ ] Meeting 1
[ ] Meeting 2
[ ] Meeting 3
[ ] Meeting 4
[ ] Meeting 5
[ ] Meeting 6
[ ] Meeting 7
[ ] Meeting 8
[ ] Meeting 9
[ ] Meeting 10
[ ] Meeting 11
[ ] Meeting 12
[ ] Meeting 13
[ ] Meeting 14
[ ] Meeting 15
[ ] Meeting 16
[ ] Meeting 17

Rozpracované články jsou zde https://github.com/encukou/freezeyt/pull/94


Incorrect WSL MSI installation via CMD and Psexec

Windows Version
Microsoft Windows [version 10.0.22631.3296]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[x] WSL 2
[ ] WSL 1

Kernel Version
Irrelevant
Distro Version
Irrelevant
Other Software
No response
Repro Steps

Become admin
Start CMD as admin
Start powershell with Psexec:

Psexec -e -s -i powershell.exe

In the 2nd window, execute install.cmd which installs the MSI

Here are the install scripts:
File install.cmd
@call powershell .\installMsiWSL2.ps1

File installMsiWSL.ps1
#Requires -RunAsAdministrator

# Variables
$MsiFile = "wsl.<IP_ADDRESS>.x64.msi"
$MsiLogFile = "C:\theLogDirectory"

$RC = (Start-Process -FilePath "msiexec.exe" -ArgumentList "/I $MsiFile /L*vx ${MsiLogFile} /qn" -Wait -PassThru).ExitCode

if (-not ($RC -eq 0 -or $RC -eq 3010)) {
    Write-Output "The msi has returned an error: ${RC}"
    Exit 1
}

Expected Behavior
MSI should be installed correctly
The command wsl --version should display the installed version
Actual Behavior
The MSI is not installed: the command wsl --version returns the help instead of the currently installed version
I have to launch the .cmd twice in a row otherwise the MSI is not installed.
For some reason, in the logs it seems like the installation was successfull, no error whatsoever.
But the MSI is clearly not installed
Diagnostic Logs
install.txt

WslLogs-2024-04-06_22-37-28.zip

For some reason, in the logs it seems like the installation was successful, no error whatsoever indeed, the installation is successful. However, if you run any wsl command, beside wsl --version which returns the help output, from within that window (In the 2nd window, execute install.cmd which installs the MSI) it returns Access is denied. Open a new terminal window and run wsl --version and you'll see that the package was installed.

Thank you @soragXYZ.
Looking at the logs, it looks like the registry part of the MSI is missing.
Can you try to fully installing WSL by running: C:\Program Files\WSL\wsl.exe" --uninstall, and reinstall the latest MSI and see if that solves the issue ?

Thank you @OneBlue
I tried with the latest version of the MSI, ie <IP_ADDRESS>, I still have the same issue

Interesting. I'd be interested to look the MSI logs for that.
Can you run wsl --uninstall, and then share the msiexec logs of a new installation ?

After more testing, it seems like the command powershell wsl --uninstall partially solved my issue:
When I start a new installation by calling install.cmd in the 2nd window opened by PsExec, the MSI is correctly installed because I can successfully run the command powershell wsl --version in a 3rd powershell window and get the expected output.
However, the command powershell wsl --version in the 2nd window opened by PsExec still returns the help.
Am I missing something here ? Why do I need to open a 3rd window ?
Do I have to update env var or something in the 2nd window ?
Concerning my first tests and the error, it seems like I had to install the MSI twice only because I didn't uninstall it correctly at first.
I have an another script used for uninstallation which basically run the command powershell Start-Process -FilePath "msiexec.exe" -ArgumentList "/X $MsiFile /L*V ${MsiLogFile} /qn" -Wait -PassThru
Do you recommend using powershell wsl --uninstall over powershell Start-Process -FilePath "msiexec.exe" -ArgumentList "/X $MsiFile /L*V ${MsiLogFile} /qn" -Wait -PassThru for the uninstallation ?
Thanks for your answers and your time

@soragXYZ: There is unfortunately a delay for the WSL installation to complete even after msiexec returns successfully.
This issue is fixed in insider builds, but it's not fixed on older builds yet. This is most likely what you're experiencing

@OneBlue thanks for the answer
Do we have a release date planned ?

Unfortunately not yet. Most likely in the coming months.

This should be now available on all recent Windows builds. Closing for now.
Please reopen if the issue still reproduces with the latest windows builds.


Callback in embedded object is not triggered if parent is saved after adding a new instance of the embedded object to latter

Leaving aside the slight chance this is expected behavior, this seems to be a bug. See attached spec.
http://github.com/papercavalier/mongoid/blob/deep/spec/integration/mongoid/deep_spec.rb

+1 to adding this to documentation.
also, i have a question.
i need to trigger an after_save on an embedded document. How should I do this from the parent? Because I'd like for after_save to run on embedded only if the embedded actualy needs saving, not everytime even if it didn't change

@dwaynemac You can add the :cascade_callbacks => true option on the embedded macro:
embeds_many :addresses, :cascade_callbacks => true

@durran GREAT tool, thx


add unit test for backend (half day declaration)

Context
As a developer,
I want to test tmy halfday declaration,
In order to see if it works properly.
Expected Behavior
Add unit test for halfday declaration.
Acceptance Criteria
It must pass the new test

#564 too much isolated test tickets, will be grouped into one


Improvement: Apply correct formatting on code with multiple lines

While it works perfectly on a one line function, if you already have code like this:
func foobar(_ foo: Foo,
                       bar: Bar)

and you apply multiliner, the result will be:
func foobar(
        _ foo: Foo,

                       bar: Bar
    )

which is not great. It would be awesome if it already detected new lines, and didn't apply new indentation. For the latter I don't know if it could re-use Xcode's reindent command for each line maybe, so you don't have to implement it yourself.

Hmm, I think I can fix this by stripping newlines before piecing it back together. I'll get back to this tomorrow, thanks for the suggestion!

@jdev7 fixed in 1.1! https://github.com/aheze/Multiliner/releases/tag/1.1.0

Works perfect! Thanks :)


Missing form values in case of registration failure

When the registration of a team fails, the displayed registration page does not contain the custom fields (see screenshot below)

Handled with pre-release 1.6.5, not exists anymore.


Ability to have responsive .container padding

Briefly mentioned via Twitter about this: https://twitter.com/OwenMelbz/status/1232404123041107975
This expands the ability of the padding option on the container plugin.
Before you had to option to set a global padding on the container via
theme: {
  container: {
    padding: '2rem',
  },
},

This allows you the option to provide an object of screen names which represent breakpoints and allows a different padding per breakpoint instead e.g.
theme: {
  container: {
    padding: {
      default: '1rem',
      sm: '2rem',
      lg: '4rem',
      xl: '5rem',
    },
  },
},

A side note around this, I'm not massively familiar with creating tailwind/postcss plugins so I appreciate that the way the logic has been written may not be what you'd consider as "best" for Tailwind, I may have even recreated the wheel for certain functionality - so more than happy for it to be refactored into a more satisfactory style.
Thanks!

Thanks 👍🏻


F OpenNebula/packages#70 Fix snap path

Merge this or https://github.com/OpenNebula/packages/pull/78

Don't know why gitcop fails


feat: improve Bitcoin depositor fee so Zeta hub can easily tell if a incoming tx failed or not (now it's a silent failure)

Describe the Issue
When Zetahub user sends a small amount of Bitcoin to TSS address, the deposit could fail due to less than depositor fee error, and currently in ZetaHub UI, we don't have any way of knowing if the deposit will be registered or not in a timely manner. The reason is that the protocol is using average fee rate in the block to calculate the deposit fee and Zetahub UI has to wait up to 1 Bitcoin block to be able to tell if the incoming deposit will be registered in zetacore or not.
A potential solution can be investigated:
It also makes sense for the zetaclient to use individual (the deposit tx) transaction's fee rate to charge deposit fee. For example, a user sends out his transaction with a very low gas rate (as long as he like waiting for a long time to finalize his transaction). Statistically, most users won't do that and we are still collecting a reasonable number of fees to cover our cost (of sending transactions out), but we might see a little bit liability due to those lower-than-market-fee transactions.
This might be a trade off of correctness for UX.
Example failed deposit: https://blockstream.info/tx/ed5f3f8a1110b9a0239875ca5d1a0f88fc88353a499de12ea06ec99faad4c486
Expected Outcome
A description of what outcome you are seeking.

I reported this issue for @fadeev today.
Using the same sat/vB as in the transaction is crucial for both the flow and security. The current approach in ZetaCore, which uses the block average, is incorrect, insecure, and unfair. It can lead to excessively high depositor fees, increase the minimum required deposit, and potentially result in user loss.
Additionally, as @ws4charlie mentioned, we are unaware when a transaction is declined, which can result in users losing their BTC.
For instance, in Block 2818648 :
1019 × 68 × 2 / 100000000 = 0.00138584 BTC (This is excessively high for a minimum value, approximately $93. Without verification, users could lose their BTC if they send less than this high amount.)
I implemented the function correctly in my app to check if users are sending low amounts before the transaction is sent, using the correct formula, based on the sats per byte used in the current transaction (the deposit tx):
satsPerByte of current transaction * 68 * 2 / 100 000 000
However, the implementation in Zetaside is different...
Using the current transaction (the deposit tx) is the best option because if users select a low sats/vB, the minimum amount can follow it. This is the UI on ECOIN Wallet for users to select the network speed before sending:
https://github.com/zeta-chain/node/assets/18597639/6b1e8a08-874c-4081-85ae-31c5e2afc90f
Is there any deadline to fix this?
This is necessary and must be a priority in my point of view.

Deadline for this? @ws4charlie @lumtis

@lumtis @brewmaster012 do you think we can prioritize this?

I believe this is important enhance for developer experience and partner integration.

Is it done?

@ronaldoguedess The modification is in PR https://github.com/zeta-chain/node/pull/2765


Fetch ACL file from Link Headers

It would be very nice if there was a way to fetch ACLs for a file according to the Link Headers, as specified in the Solid Spec: https://github.com/solid/web-access-control-spec#acl-resource-location-discovery
Right now I do not believe there's a way to get this information using LDFlex directly, as it is part of the response header which is not exposed to the users.

How could the interface for this look like?
data["https://pod.example/document"].acl()

Other proposals?

@angelo-v I like that actually!

Is this the correct repo to implement it? Or are upstream packages (ldflex, communica, ...) involved? Where do we have access to the headers?

Is this the correct repo

It's Solid-specific, so this is the one!

Where do we have access to the headers?

We'd have to tap into the fetcher. So basically, when the .acl() is called, it should fetch the document, inspect the headers, and then fetch the ACL document and take it from there.


Only symbol clickable in split view and theme buttons

As in title. Windows 10 Pro x64 Redstone
https://gfycat.com/AdmiredBewitchedCooter

This is actually a bug in NW.js. There's no way I can fix it.

Beware, if frame is set to false in fullscreen it will prevent the mouse from being captured on the very edges of the screen. You should avoid activate it if fullscreen is also set to true.
NW.js Documentation


Using the synchronous client produces exceptions

Describe the bug
Using the synchronous client produces exceptions
I'm trying to synchronously consume events from EventHub. EVents are not consumed, but after a couple of minutes I'm starting to get the exceptions below. "After a couple of minutes" means that the client has been open and closed multiple times - instead of streaming the events, we do batch consumption, just as documented here https://azuresdkdocs.blob.core.windows.net/$web/java/azure-messaging-eventhubs/5.10.1/index.html at "Consuming events with EventHubConsumerClient.
Exception or Stack Trace
2021-10-07 10:38:51,043  WARN c.a.c.a.i.ReactorDispatcher:381 - connectionId[MF_6830a6_1633603060368] signalWorkQueue failed before reactor closed.
2021-10-07 10:38:51,043  WARN c.a.c.a.i.ReactorDispatcher:381 - connectionId[MF_6830a6_1633603060368] signalWorkQueue failed before reactor closed.
2021-10-07 10:38:51,044 ERROR r.c.p.Operators:314 - Operator called default onErrorDropped
java.lang.RuntimeException: connectionId[MF_6830a6_1633603060368] IO Sink was interrupted before reactor closed.
at com.azure.core.amqp.implementation.ReactorDispatcher.signalWorkQueue(ReactorDispatcher.java:130)
at com.azure.core.amqp.implementation.ReactorDispatcher.invoke(ReactorDispatcher.java:94)
at com.azure.core.amqp.implementation.RequestResponseChannel.(RequestResponseChannel.java:186)
at com.azure.core.amqp.implementation.ReactorConnection.lambda$createRequestResponseChannel$16(ReactorConnection.java:389)
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:113)
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:127)
at reactor.core.publisher.Operators$MonoSubscriber.request(Operators.java:1905)
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.request(FluxMapFuseable.java:169)
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.request(FluxMapFuseable.java:169)
at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.request(FluxPeekFuseable.java:144)
at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.request(Operators.java:2157)
at com.azure.core.amqp.implementation.AmqpChannelProcessor.requestUpstream(AmqpChannelProcessor.java:308)
at com.azure.core.amqp.implementation.AmqpChannelProcessor.lambda$onNext$3(AmqpChannelProcessor.java:119)
at reactor.core.publisher.LambdaSubscriber.onComplete(LambdaSubscriber.java:132)
at reactor.core.publisher.EmitterProcessor.checkTerminated(EmitterProcessor.java:554)
at reactor.core.publisher.EmitterProcessor.drain(EmitterProcessor.java:415)
at reactor.core.publisher.EmitterProcessor.tryEmitComplete(EmitterProcessor.java:234)
at reactor.core.publisher.SinkManySerialized.tryEmitComplete(SinkManySerialized.java:61)
at reactor.core.publisher.InternalManySink.emitComplete(InternalManySink.java:68)
at com.azure.core.amqp.implementation.RequestResponseChannel.onTerminalState(RequestResponseChannel.java:401)
at com.azure.core.amqp.implementation.RequestResponseChannel.lambda$new$3(RequestResponseChannel.java:161)
at reactor.core.publisher.LambdaSubscriber.onComplete(LambdaSubscriber.java:132)
at reactor.core.publisher.FluxDistinctUntilChanged$DistinctUntilChangedSubscriber.onComplete(FluxDistinctUntilChanged.java:172)
at reactor.core.publisher.FluxReplay$SizeBoundReplayBuffer.replayNormal(FluxReplay.java:805)
at reactor.core.publisher.FluxReplay$SizeBoundReplayBuffer.replay(FluxReplay.java:898)
at reactor.core.publisher.ReplayProcessor.tryEmitComplete(ReplayProcessor.java:465)
at reactor.core.publisher.SinkManySerialized.tryEmitComplete(SinkManySerialized.java:61)
at reactor.core.publisher.InternalManySink.emitComplete(InternalManySink.java:68)
at com.azure.core.amqp.implementation.handler.Handler.close(Handler.java:132)
at com.azure.core.amqp.implementation.handler.ReceiveLinkHandler.onLinkLocalClose(ReceiveLinkHandler.java:185)
at org.apache.qpid.proton.engine.BaseHandler.handle(BaseHandler.java:173)
at org.apache.qpid.proton.engine.impl.EventImpl.dispatch(EventImpl.java:108)
at org.apache.qpid.proton.reactor.impl.ReactorImpl.dispatch(ReactorImpl.java:324)
at org.apache.qpid.proton.reactor.impl.ReactorImpl.process(ReactorImpl.java:291)
at com.azure.core.amqp.implementation.ReactorExecutor.run(ReactorExecutor.java:86)
at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:68)
at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:28)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.nio.channels.AsynchronousCloseException: null
at java.base/java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202)
at java.base/sun.nio.ch.SocketChannelImpl.endWrite(SocketChannelImpl.java:447)
at java.base/sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:469)
at java.base/sun.nio.ch.SinkChannelImpl.write(SinkChannelImpl.java:114)
at com.azure.core.amqp.implementation.ReactorDispatcher.signalWorkQueue(ReactorDispatcher.java:123)
... 41 common frames omitted
2021-10-07 10:38:51,046 ERROR c.a.c.a.i.ReactorDispatcher:387 - ReactorDispatcher instance is closed.
2021-10-07 10:38:51,044  WARN c.a.c.a.i.ReactorDispatcher:381 - connectionId[MF_6830a6_1633603060368] signalWorkQueue failed before reactor closed.
To Reproduce

Create an event hub
Configure the event hub for Azure AD log collection
Launch a scheduled job every 10 seconds to fetch all accumulated events in the event hub.

Code Snippet
    EventHubClientBuilder clientBuilder = new EventHubClientBuilder()
            .connectionString(connectionString)
            .clientOptions(new ClientOptions().setApplicationId("custom-consumer"))
            .prefetchCount(FETCH_SIZE)
            .consumerGroup(EventHubClientBuilder.DEFAULT_CONSUMER_GROUP_NAME);

    try (EventHubConsumerClient client = clientBuilder.buildConsumerClient()) {
        logger.info("Created Azure client {} with partitions {}", client.getConsumerGroup(),
                client.getPartitionIds().stream().collect(Collectors.joining(", ")));

        List<Entry> entries = new ArrayList<>();

        for (String partitionId : client.getPartitionIds()) {
            var events = client.receiveFromPartition(partitionId, FETCH_SIZE,
                    EventPosition.fromEnqueuedTime(details.getLastFetchedTime().toInstant(ZoneOffset.UTC)),
                    Duration.ofSeconds(RECEIVE_TIMEOUT_SECONDS), RECEIVE_OPTIONS);

            for (PartitionEvent event : events) {
                entries.addAll(toEntry(event.getData(), event.getPartitionContext()));
            }
        }

Expected behavior
Events should be consumed and there should be no stacktraces
Screenshots
Setup (please complete the following information):

OS: Windows
IDE: IntelliJ
Library/Libraries: com.azure:azure-messaging-eventhubs:5.10.1
Java version: 11
App Server/Environment: Undertow
Frameworks: Spring Boot

@conniey could you please follow up with @Glamdring on their github issue?

Apologies for dropping the ball on this. I'll take a look at it now.
Every time receiveFromPartition is called, it creates a new receive link, receives x number of events, then closes that receive link. It may not be as performant as you want using the async client and then calling receive will give you potentially an infinite stream of events where you an apply Reactor operators to have back-pressure etc.

For reasons outside the scope of the issue, we can't work with an infinite stream and a reactor; it has to be a batch "fetch and close" repeatedly.

the client has been open and closed multiple times

@Glamdring Does this mean that you are creating a new client after receiving a batch of events from each partition?

the client has been open and closed multiple times

@Glamdring Does this mean that you are creating a new client after receiving a batch of events from each partition?

Yes, that's correct. It is a session-less batch process, so leaving a client open is hardly an option.

Hi @Glamdring , I just go through this issue,
Sorry for that I didn't repro this issue, I need more details:

Could you provide more logs and turn on the DEBUG log level? From the error message, the reactor is closed, there could be some other error cause the reactor closed I assumed. So I guess here is not the whole error logs. We fixed a client-closed related issue in July's release. Not sure this issue is related with the one we fixed before . But we highly recommand upgrade to the latest version. So could you please upgrade the SDK to latest version which is v5.13.0 now.
I want to know how you trigger the batch process task. Do you set up a timer to do this process every 10s? Each process task is on a new thread?

PS:

It is a session-less batch process, so leaving a client open is hardly an option.

I'm curious about why leaving a client open is hardly an option. Actually our customers have similar scenario, they also do some session-less batch process tasks. they keep the client opening in the server side and trigger the task by http request. The time between every request is random. It also works.

Hello @ZejiaJiang
I'm not longer involved with the issue, but I'll let the team know they should upgrade and try again. Will get back with results.
The batch task is triggered by spring's @Scheduled mechanism, which means a thread pool is executing the tasks. The issue with leaving a session open is that the application is stateless and 1runs in a cluster of several machines, so it's not guaranteed that the next run will happen on the same machine (we have a distributed lock mechanism to make sure there are no race conditions). So each time the task runs, we have to assume it doesn't have rely on any application state (we store some state in the database).

I did some tests to repro this issue, but all I got is two exception we fixed before, https://github.com/Azure/azure-sdk-for-java/pull/27400 and https://github.com/Azure/azure-sdk-for-java/pull/27512 . In the latest verion of SDK, all work well.
I created two eventhub instance, one has 1 partition and the another one has 32 partitions, I wrote some code just like given code snippet. failed to repro this issue. So if the issue still remains in latest version of SDK, could you please provide some more information:

Turn on the DEBUG log level? here is the configure step Enable and configure logging
More detail of parameters, how many partitions in you eventhubs instance? how many events (FETCH_SIZE) to fetch in each batch task? How long each task take?


Reference to a incorrect module functions

on version 0.4.2 of the pdk, there seems to be a reference to the wrong msgpack module
https://github.com/Kong/kong-js-pdk/blob/fa6b3002bcdc320ad93b209bc44cbc3cd58a66b1/bin/kong-js-pluginserver#L21-L24
The pack function is a member of the top level msgpack module, but this is using the @msgpack/msgpack which only has encode / decode functions
/usr/local/bin/kong-js-pluginserver --dump-plugin-info fake -d /home/kong/plugins
UnhandledPromiseRejectionWarning: TypeError: msgpack.pack is not a function
    at /usr/local/lib/node_modules/kong-pdk/bin/kong-js-pluginserver:23:36
    at processTicksAndRejections (internal/process/task_queues.js:95:5)

@fffonion possible to publish a patch release?


How do I provision a writer from one instance class and 3 replicas from another instance class.

Description
Thank you the module, it's quite handy.
This is more of a question and/or a documentation request. I've noticed that this module automatically creates 3 db instances in regions where there are availability zones. I have a use case where I want to create a cluster of 4 instances with the writer being a db.m5d.4xlarge instance and the 3 read replicas being db.m5d.large instances.
I tried passing several different permutations of the instances map but I couldn't figure out how to do this ☝
Is this possible?

[x] ✋ I have searched the open/closed issues and my issue is not listed.

Versions

Module version [Required]: 8.3.0

Terraform version: 1.2.6

Provider version(s):

Reproduction Code [Required]
Doc request and/or question.

its possible, but this is not how clusters are managed. if you have a failover event, your writer endpoint is going to a reader which in your scenario, will be much smaller than what it was. it is always highly recommended to use a homogeneous set of instances in these clusters

OK, great. That makes sense, thanks @bryantbiggs. Not sure if it's worth adding a comment to this effect somewhere or a note in the ReadMe but I have an existing (non-Aurora/RDS) cluster which is set up exactly this way: 1 large-ish writer with 3 smaller readers. I will adjust my AWS setup accordingly.

Reopened for my follow up question ☝

again, I said its possible but not recommended - especially since you are inquiring about it here. if you wish to learn more, I would suggest diving into the Aurora docs first


Gentoo package

Could a gentoo package be created?

I have not done any Linux packaging myself yet, but I definitely plan to package it individually for every major distro


Proposed Format Changes (Jekyll, Markdown, etc)

Introduction
A topic up for consideration is the future format. It is better to have this plan @now than to do it later when there is more content.
Current Proposed Options

GitHub pages using Jekyll/Markdown
Read The Docs (RTD)

Requirements

Git version control and collaboration using a public repo (such as this Github)
must generate static content
Content must be usable when pulled offline, without using any form of tools (note, this precludes link based pages unless a full archive that is always updated is readily available)

Timeline
Ideally this decision should be made by June, so contributions for the upcoming DC can be made.

Points for GH Pages using Jekyll/Markdown:

Produces a perfect archive: WYSIWYG in terms of content, from what I understand.
Clone a repo = get the content
GitHub does the work for you -- Mostly.

Points for RTD:

Uses Markdown or ReStructuredText, with RST being default.
Uses the well-established Sphinx engine
Produces [ HTML, PDF, EPUB ] versions as artifacts from each build
click to edit in GitHub
RTD does the work for you. Mostly.

Downsides to Jekyll:

Two independent branches. One is a direct artifact of the other, but it looks funny.
Only one artifact produced
Only supports Markdown (from my understanding)
great for a blog, not so great for a book.

Downsides to RtD:

Cloning repo = get only sources, not final content
works best with ReStructuredText
Some people are anti-scalie haters not a fan of python.
Uses someone else's infrastructure.

Cloning repo = get only sources, not final content

I think that enough is problematic. So reading through RTD's background for using ReStructuredText as the default is that Markdown doesn't have as much extensible. We don't need that much here, as this isn't intended to be hundreds of pages long (that would default the point of being n00b friendly)
However, at the same time the Markdown used by Github is technically a "flavour" of MD since there is no official standard. However, our MD usage would be fairly basic as we do not have code in this repo. Hence, no having to handle code snippets along the lines of:
import math

versus
~~~python
import math
~~~

as a flavour variant
This still leaves some details such as whether or not we have these differences in markdown interpretation
# Heading 1
#Heading 1

However, I think the majority of users will either A) be using Github, B) the information will still be human readable even without a Markdown viewer, or C) the very few markdown descriptors we actually will end up using will be easy enough to automate converting.
Any thoughts on those points? I doubt most people would run their own jekyll, but they will like the option. My super-secret employer for example would maybe want to run their own, with guidelines for employees that are internal only.
Or maybe it would just be a good idea to not place our eggs in one basket (I certainly don''t with Github).
Cheers,
~H

I would prefer a move towards Markdown/Github Pages for the sake of simplicity with markdown. It is fairly straight forward to convert and yet still would provide the required format if someone wanted to clone and run pandoc or similar for document conversion to a preferred format. Even though GH technically uses a "flavor" of markdown, the required syntax for this repos use case should be pretty basic and be supported by the majority of markdown readers when cloning or if this ever needs to move towards a different platform for hosting. Also, I do agree that the majority of users are likely to be Github user and we may benefit from a little search engine preference that way (not a validated statement).

I think Markdown is the best move as well. I've talked with several others on different channels (though getting them to move that discussion here has been... trying). I'll set a milestone to move to a GH page eventually, but for now everything is in a Markdown format for the mast part.

This thread can be used for suggestions regarding the style guide as well. It will be closed when the first step in the project is complete.

Markdown it was.


Can I get Uploaded file Instagram URL path?

hi there is there any way I can have  Instagram URL of Uploaded pic ?

From v0.0.7 the upload function return the response from instagram, and you can get all information you want there.
🥂


[DUOS-228] Handle invalid dar ids better

Addresses
https://broadinstitute.atlassian.net/browse/DUOS-228
Changes

Handle the lookup of the dar by document id better. If we can't find it, or if it is not an id we can look up, return a 404.
Added tests.

Manual Testing

Spin up and go to the dar lookup page which is Data_Access_Request/get_api_dar_id
Try entering gibberish into the id field and ensure that you get a 404.
Enter a real id (look one up from duos dev) and ensure that you still get a valid document.

Coverage decreased (-1.5%) to 60.411% when pulling 1882d16e7888d5c80bf07359c5985ae7e6cda885 on DUOS-228 into 18303a9f0daa2eab85ea87f614f16f9714b6abdb on develop.


failed to fetch https://charts.jetstack.io/index.yaml : 403 Forbidden

We are getting below error while deploying terraform helm(v2.3.0)cert-manager v1.6.1.  It was working fine before azure k8s is redeployed.
It is also working when it is deployed manually from local system
Error: looks like "[https://charts.jetstack.io"](https://charts.jetstack.io%22/) is not a valid chart repository or cannot be reached: failed to fetch https://charts.jetstack.io/index.yaml : 403 Forbidden │  │   with module.helm.helm_release.cert_manager, │   on modules/helm/main.tf line 279, in resource "helm_release" "cert_manager": │  279: resource "helm_release" "cert_manager" {
when i try to curl the url https://charts.jetstack.io/index.yaml
curl -iL https://charts.jetstack.io/index.yaml HTTP/2 403 date: Tue, 03 Jan 2023 14:14:22 GMT content-type: text/html; charset=UTF-8 cf-chl-bypass: 1 permissions-policy: accelerometer=(),autoplay=(),camera=(),clipboard-read=(),clipboard-write=(),fullscreen=(),geolocation=(),gyroscope=(),hid=(),interest-cohort=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=() referrer-policy: same-origin x-frame-options: SAMEORIGIN cache-control: private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0 expires: Thu, 01 Jan 1970 00:00:01 GMT report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=qcA6RrEski1T%2Bu%2BpofahchMYEHPQkQ7orsq%2BzablOrw5xNS07AVKsFkhJykU7hXnNftH7GTrEBIUc7uSEQ62B6CNzN%2FueIzrw8PcBig4b%2FKmtE5WW5beoQbQYZOgUZ0wC3v%2BTTc%3D"}],"group":"cf-nel","max_age":604800} nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800} server: cloudflare cf-ray: 783c5723c99f0e33-AMS alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
Below screenshot suggest an review for network connection. What shall be done from our end?

We use a CloudFlare feature called proxied DNS records, which enables DDOS protections by default and we can't find a way to turn them off right now.
Are you still experiencing this problem? To my knowledge no other users have encountered this, so perhaps there is something unique to your client that is triggering the DDOS protections. Do you have any idea what that might be?

I'll close this issue, but please re-open if you still encounter this error or if you have more information about what might be causing it.


Helper method to determine whether an account has enough flow to receive an item

I belive FlowFees has some code to do this


Add dataset example Hugo_CATI

I tried to create a BIDS hierarchy for our main PET preprocess pipeline at CATI, named AMETHYST. Nifti files are empty files, as it focuses more on organization, to avoid issues sharing not defaced imaging data publically.
In this example, I did not detail JSON for MRI preprocessing, nor "rois" preprocessing.
I do not know how to handle transformation files, I saw that some discussions were started in a BEP, but I was not sure how to do it in my case. As this is more focus on PET data, I thought it unnecessary.

@mnoergaard  After looking back to what I pushed, I was making some adjustments to simplify some parts. If it is ok, I will push that updates on the main project :wink:

Of course! Feel free to update all you want. Looking forward to discuss these efforts tomorrow!

It seems that I don't have permissions to push on openneuropet/pet-bids-derivatives-data

@Hboni you should have received an invite to become a collaborator on this with write access


Maybe just wrong display infos

When I launch with the correct parameters it shows
Hoppingcodes: 0x00000000 0x00000000 0x00000000
Startkey: 0xc01108f4dc2baaf
Is it normal that it shows "Hoppingcodes: 0x00000000 0x00000000 0x00000000" ?

Try to Start this way: kelloq.exe 0x11223344 0x55667788 0x99aabbcc So you have to enter 3 hopping Codes that are captured in sequence.

It's exactly what I'm doing:
KeeLoq.exe 0xDC3BD2C9 0x3F21F56A 0xE92A6DE3
But the output is:
Hoppingcodes: 0x00000000 0x00000000 0x00000000
Startkey: 0x46fa6ec69e5113d8

ok, but...can it be a problem the fact that i'm not using a cuda system? (i know it could take days...i don't have a cuda system right now)
Have you ever tryed another bruteforcer?

Without a cuda card it wont work. This is why you get 0x00000000... The Software does copy the hopping Codes into cuda RAM and back to Display on Screen. If you dont have any cuda card, this wont work. An other bruteforcer doesnt make sense, because of the huge keyspace of 64bit. Which System Do you try to brute force?

My FAAC garage door, recorded with my flipper zero the keys and trying with your utility.
I'll try with a cuda system (not powerful) when I'll arrive at my office.

Can you provide a serial number, so i can check, if i have the manufacturer Key already...

Can you provide a serial number, so i can check, if i have the manufacturer Key already...

Hello, there is a huuuge misunderstanding here, he talks about FAAC SLH that requires seed(unique for each receiver) to clone a remote
he already asked about this in telegram, discord, official, unofficial, everywhere, and he didn’t read my message in discord
He thinks that he can bruteforce seed using your project without any changes (this will not work)
that was made for manufacturer code bruteforcing, not for FAAC

he already asked about this in telegram, discord, official, unofficial, everywhere, and he didn’t read my message in discord

You're really wrong my friend, I've only asked you with via PM infos,and  i've read all your messages and replyed (except the latest one).
I wanna understand how things are working instead of paying. So I'm looking for infos everywhere. That's all.

Great code! Would it be 32 faster using the bit-slicing approach from Giovanni Agosta? He an his team use bit-slicing and work at the same time in 32 Registers.

My cuda Code works on 8192 independend keys in parallel, so i dont know if bitslicing would make it any faster.


more buffers then expected

I am using vim-fetch like following:
vim `grep pattern -Irn . | awk '{print $1}'
So vim invoked like
vim file1:12 file1:23 file2:33 ...
Turns out following:

When vim started it open file1 at line 12
After first :n it  open file1 at line:23 (as expected)
After second :n instead of opening file2 at line 33 it again opened file1 at line:23
Third :n open file2 at line 33 (expected after second :n)

Huh, that is odd. Could you please deactivate vim-fetch and repeat the experience? You will get a bunch of spurious empty buffers called file1:12 etc. I am interested in learning if the buffers are duplicated as above without fetch resolving them too.

I deactivated vim-fetch and run
vim file1:12 file1:23
I got empty file (file1:12).
After :n I got empty file (file1:23)
After second :n I got "E165: Cannot go beyond last file"
Everything as expected

Something new here? Do you need more info from me?

Yes and no, sorry for the delay: I meant to test why you consider E165 “normal” by checking if (and  how) it also happens on my system, but I have precious little time for Vimming ATM.

Possible duplicate of #17.

Fixed in ef8a8e78f9bb724ca0fd2bd0b4e39d3e12487832.


Rails' ActiveRecord::Encryption on User attributes (email and/or id) prevents the error message from being returned (when values empty)

Environment

Ruby: ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x86_64-linux]
Rails: Rails 7.0.4
Devise: devise 4.8.1

Current behavior
When the User model has attributes (email and/or id) encrypted (using Rails' Active Record Encryption) and then, an empty "Sign up" form is submitted, the server returns a 500 Internal Server Error, due to ActiveRecord::Encryption::Errors::Decryption (ActiveRecord::Encryption::Errors::Decryption) being triggered by the line resource.save in Devise's RegistrationsController.
Expected behavior
Instead, a validation error should be returned (i.e. "Email is required").
Trace
activerecord (7.0.4) lib/active_record/encryption/encryptor.rb:58:in `rescue in decrypt'
activerecord (7.0.4) lib/active_record/encryption/encryptor.rb:52:in `decrypt'
activerecord (7.0.4) lib/active_record/encryption/encrypted_attribute_type.rb:73:in `block in decrypt'
activerecord (7.0.4) lib/active_record/encryption/scheme.rb:67:in `with_context'
activerecord (7.0.4) lib/active_record/encryption/encrypted_attribute_type.rb:15:in `with_context'
activerecord (7.0.4) lib/active_record/encryption/encrypted_attribute_type.rb:72:in `decrypt'
activerecord (7.0.4) lib/active_record/encryption/encrypted_attribute_type.rb:31:in `deserialize'
activemodel (7.0.4) lib/active_model/attribute.rb:168:in `type_cast'
activemodel (7.0.4) lib/active_model/attribute.rb:43:in `value'
activemodel (7.0.4) lib/active_model/attribute_set.rb:46:in `fetch_value'
activerecord (7.0.4) lib/active_record/transactions.rb:403:in `block in restore_transaction_record_state'
activemodel (7.0.4) lib/active_model/attribute_set.rb:93:in `transform_values'
activemodel (7.0.4) lib/active_model/attribute_set.rb:93:in `map'
activerecord (7.0.4) lib/active_record/transactions.rb:402:in `restore_transaction_record_state'
activerecord (7.0.4) lib/active_record/transactions.rb:334:in `rolledback!'
activerecord (7.0.4) lib/active_record/connection_adapters/abstract/transaction.rb:134:in `rollback_records'
activerecord (7.0.4) lib/active_record/connection_adapters/abstract/transaction.rb:312:in `block in rollback_transaction'
activesupport (7.0.4) lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
activesupport (7.0.4) lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize'
activesupport (7.0.4) lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
activesupport (7.0.4) lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
activerecord (7.0.4) lib/active_record/connection_adapters/abstract/transaction.rb:309:in `rollback_transaction'
activerecord (7.0.4) lib/active_record/connection_adapters/abstract/transaction.rb:325:in `rescue in block in within_new_transaction'
activerecord (7.0.4) lib/active_record/connection_adapters/abstract/transaction.rb:322:in `block in within_new_transaction'
activesupport (7.0.4) lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
activesupport (7.0.4) lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize'
activesupport (7.0.4) lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
activesupport (7.0.4) lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
activerecord (7.0.4) lib/active_record/connection_adapters/abstract/transaction.rb:317:in `within_new_transaction'
activerecord (7.0.4) lib/active_record/connection_adapters/abstract/database_statements.rb:316:in `transaction'
activerecord (7.0.4) lib/active_record/transactions.rb:350:in `with_transaction_returning_status'
activerecord (7.0.4) lib/active_record/transactions.rb:298:in `save'
activerecord (7.0.4) lib/active_record/suppressor.rb:50:in `save'
app/controllers/users/registrations_controller.rb:96:in `create'
actionpack (7.0.4) lib/action_controller/metal/basic_implicit_render.rb:6:in `send_action'
actionpack (7.0.4) lib/abstract_controller/base.rb:215:in `process_action'
actionpack (7.0.4) lib/action_controller/metal/rendering.rb:53:in `process_action'
actionpack (7.0.4) lib/abstract_controller/callbacks.rb:234:in `block in process_action'
activesupport (7.0.4) lib/active_support/callbacks.rb:118:in `block in run_callbacks'
actiontext (7.0.4) lib/action_text/rendering.rb:20:in `with_renderer'
actiontext (7.0.4) lib/action_text/engine.rb:69:in `block (4 levels) in <class:Engine>'
activesupport (7.0.4) lib/active_support/callbacks.rb:127:in `instance_exec'
activesupport (7.0.4) lib/active_support/callbacks.rb:127:in `block in run_callbacks'
activesupport (7.0.4) lib/active_support/callbacks.rb:138:in `run_callbacks'
actionpack (7.0.4) lib/abstract_controller/callbacks.rb:233:in `process_action'
actionpack (7.0.4) lib/action_controller/metal/rescue.rb:22:in `process_action'
actionpack (7.0.4) lib/action_controller/metal/instrumentation.rb:67:in `block in process_action'
activesupport (7.0.4) lib/active_support/notifications.rb:206:in `block in instrument'
activesupport (7.0.4) lib/active_support/notifications/instrumenter.rb:24:in `instrument'
activesupport (7.0.4) lib/active_support/notifications.rb:206:in `instrument'
actionpack (7.0.4) lib/action_controller/metal/instrumentation.rb:66:in `process_action'
actionpack (7.0.4) lib/action_controller/metal/params_wrapper.rb:259:in `process_action'
activerecord (7.0.4) lib/active_record/railties/controller_runtime.rb:27:in `process_action'
actionpack (7.0.4) lib/abstract_controller/base.rb:151:in `process'
actionview (7.0.4) lib/action_view/rendering.rb:39:in `process'
actionpack (7.0.4) lib/action_controller/metal.rb:188:in `dispatch'
actionpack (7.0.4) lib/action_controller/metal.rb:251:in `dispatch'
actionpack (7.0.4) lib/action_dispatch/routing/route_set.rb:49:in `dispatch'
actionpack (7.0.4) lib/action_dispatch/routing/route_set.rb:32:in `serve'
actionpack (7.0.4) lib/action_dispatch/routing/mapper.rb:18:in `block in <class:Constraints>'
actionpack (7.0.4) lib/action_dispatch/routing/mapper.rb:48:in `serve'
actionpack (7.0.4) lib/action_dispatch/journey/router.rb:50:in `block in serve'
actionpack (7.0.4) lib/action_dispatch/journey/router.rb:32:in `each'
actionpack (7.0.4) lib/action_dispatch/journey/router.rb:32:in `serve'
actionpack (7.0.4) lib/action_dispatch/routing/route_set.rb:852:in `call'
http_accept_language (2.1.1) lib/http_accept_language/middleware.rb:14:in `call'
warden (1.2.9) lib/warden/manager.rb:36:in `block in call'
warden (1.2.9) lib/warden/manager.rb:34:in `catch'
warden (1.2.9) lib/warden/manager.rb:34:in `call'
rack (2.2.5) lib/rack/tempfile_reaper.rb:15:in `call'
rack (2.2.5) lib/rack/etag.rb:27:in `call'
rack (2.2.5) lib/rack/conditional_get.rb:40:in `call'
rack (2.2.5) lib/rack/head.rb:12:in `call'
actionpack (7.0.4) lib/action_dispatch/http/permissions_policy.rb:38:in `call'
actionpack (7.0.4) lib/action_dispatch/http/content_security_policy.rb:36:in `call'
rack (2.2.5) lib/rack/session/abstract/id.rb:266:in `context'
rack (2.2.5) lib/rack/session/abstract/id.rb:260:in `call'
actionpack (7.0.4) lib/action_dispatch/middleware/cookies.rb:696:in `call'
activerecord (7.0.4) lib/active_record/migration.rb:603:in `call'
actionpack (7.0.4) lib/action_dispatch/middleware/callbacks.rb:27:in `block in call'
activesupport (7.0.4) lib/active_support/callbacks.rb:99:in `run_callbacks'
actionpack (7.0.4) lib/action_dispatch/middleware/callbacks.rb:26:in `call'
actionpack (7.0.4) lib/action_dispatch/middleware/executor.rb:14:in `call'
actionpack (7.0.4) lib/action_dispatch/middleware/actionable_exceptions.rb:17:in `call'
actionpack (7.0.4) lib/action_dispatch/middleware/debug_exceptions.rb:28:in `call'
web-console (4.2.0) lib/web_console/middleware.rb:132:in `call_app'
web-console (4.2.0) lib/web_console/middleware.rb:28:in `block in call'
web-console (4.2.0) lib/web_console/middleware.rb:17:in `catch'
web-console (4.2.0) lib/web_console/middleware.rb:17:in `call'
actionpack (7.0.4) lib/action_dispatch/middleware/show_exceptions.rb:26:in `call'
railties (7.0.4) lib/rails/rack/logger.rb:40:in `call_app'
railties (7.0.4) lib/rails/rack/logger.rb:25:in `block in call'
activesupport (7.0.4) lib/active_support/tagged_logging.rb:99:in `block in tagged'
activesupport (7.0.4) lib/active_support/tagged_logging.rb:37:in `tagged'
activesupport (7.0.4) lib/active_support/tagged_logging.rb:99:in `tagged'
railties (7.0.4) lib/rails/rack/logger.rb:25:in `call'
sprockets-rails (3.4.2) lib/sprockets/rails/quiet_assets.rb:13:in `call'
actionpack (7.0.4) lib/action_dispatch/middleware/remote_ip.rb:93:in `call'
request_store (1.5.1) lib/request_store/middleware.rb:19:in `call'
actionpack (7.0.4) lib/action_dispatch/middleware/request_id.rb:26:in `call'
rack (2.2.5) lib/rack/method_override.rb:24:in `call'
rack (2.2.5) lib/rack/runtime.rb:22:in `call'
activesupport (7.0.4) lib/active_support/cache/strategy/local_cache_middleware.rb:29:in `call'
actionpack (7.0.4) lib/action_dispatch/middleware/server_timing.rb:61:in `block in call'
actionpack (7.0.4) lib/action_dispatch/middleware/server_timing.rb:26:in `collect_events'
actionpack (7.0.4) lib/action_dispatch/middleware/server_timing.rb:60:in `call'
actionpack (7.0.4) lib/action_dispatch/middleware/executor.rb:14:in `call'
actionpack (7.0.4) lib/action_dispatch/middleware/static.rb:23:in `call'
rack (2.2.5) lib/rack/sendfile.rb:110:in `call'
actionpack (7.0.4) lib/action_dispatch/middleware/host_authorization.rb:137:in `call'
railties (7.0.4) lib/rails/engine.rb:530:in `call'
puma (5.6.5) lib/puma/configuration.rb:252:in `call'
puma (5.6.5) lib/puma/request.rb:77:in `block in handle_request'
puma (5.6.5) lib/puma/thread_pool.rb:340:in `with_force_shutdown'
puma (5.6.5) lib/puma/request.rb:76:in `handle_request'
puma (5.6.5) lib/puma/server.rb:443:in `process_client'
puma (5.6.5) lib/puma/thread_pool.rb:147:in `block in spawn_thread'

I believe this comment can help https://github.com/heartcombo/devise/issues/5436#issuecomment-1014152052
If you want to raise an error from the request, you can edit the permitted params to make email required (yet it's not recommended in rails community to do so)


fill in further reading sections

[x] ahn2
[x] eecology
[x] esalsa
[x] ewatercycle
[x] summerinthecity
[x] viaappia
[x] wetenschapsagenda

According to this format:

Project [website] on esciencecenter.nl
Project [video] on vimeo.com
A screencast [video] of the demo on vimeo.com
Browse [the code] on github.com
Pitch presentations on [sharepoint]
Follow-up project [THE_PROJECT]
other item

Format is now part of the template. Closing this issue.


[ML] Apply black to ml

Description
Related to #28742
Related to #28782
This PR runs black on the azure-ai-ml in preparation for #28756 which is scheduled to be merged on 2023-02-15.
Methodology: black -l 120 sdk/ml, which is the command run in CI to validate formatting:
https://github.com/Azure/azure-sdk-for-python/blob/d0f6d33c7e1b954f76f207a43eefc2d6115a45cb/scripts/devops_tasks/validate_formatting.py#L31
cc: @scbedd
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run python - ml - ci

API change check
API changes are not detected in this pull request.

PR looks good, but I'm wondering if we should skip _restclient? It's anyways autogenerated code, so I don't think we need to worry about formatting it. However, if the PR check doesn't allow for exclusions, then I guess we have no choice.

PR looks good, but I'm wondering if we should skip _restclient? It's anyways autogenerated code, so I don't think we need to worry about formatting it. However, if the PR check doesn't allow for exclusions, then I guess we have no choice.

Is there any harm in keeping _restclient included? There's a one-time cost every time the restclient is regenerated to run black, but otherwise it's not obvious to me what the negative is.

From what I've seen of the CI infrastructure for formatting, there isn't currently a mechanism for a package to specify formatting exclusions. So if we really wanted to exclude _restclient, this PR would be blocked until that's implemented.

Is there any harm in keeping _restclient included? There's a one-time cost every time the restclient is regenerated to run black, but otherwise it's not obvious to me what the negative is.

These days, our partners are usually the ones to onboard new API versions, and there tends to be quite a bit of churn in _restclient code until the API is finalized. I'm not sure if expecting them to run black every time they regenerate something is too much to ask, so maybe we should have a quick internal discussion about it. If we decide that _restclient will be included (since it was excluded from any formatting in the internal repo), we should make it clear in our documentation so that partners aren't confused about the change in rules.

Made a PR ( #28835 ) that should configure black to exclude the _restclient from formatting. That PR needs to be merged before this one, but I've already re-run black with those exemptions.


play

study play
Sent from PPHub

Done with https://github.com/peng051410/today_i_learn/commit/b9c239bfe28e15c4391e034c315ed5cb48817388


Support for left and right on digital joysticks such as dfRobot

Support for left / back button that:
When not in edit mode, goes back one level towards root.
When in edit mode for multi items, goes back one part
When in edit mode more generally, leaves edit mode.
Support for right / next button that:
When not in edit mode, goes into edit mode
When in edit mode for regular items, does nothing
When in edit mode for multi-items, goes to the next part.

This has been implemented as the ability to add a back and next button which generally have the same meaning as the left and right keys in df robot shields / joystick.
It is possible to add them independently.


Rename public traits

Found at https://github.com/automerge/spanreed/blob/02daef359296fac46db351223909e2005811024f/src/interfaces.rs#L65
It seems we could just pass the traits directly as generic arguments.

Rename to Storage, and make network simply a Sink + Stream.

Done in https://github.com/automerge/spanreed/pull/17


Revert "fix($parse): standardize one-time literal vs non-literal and interceptors"

Reverts 189461f9bf6fda18ddbd16c42f2e959cf939c3da to fix #15905 in 1.6. Currently plan is to NOT revert in 1.7.
Fixes #15905

Created #15960

Note that fixing https://github.com/angular/angular.js/issues/15964 should actually fix the issue in 1.6, so it might still be possible to fix this in 1.6 without reverting anything...

What's the status of this now that https://github.com/angular/angular.js/issues/15964 has been fixed?

#15964 fixed filters, #16018 does the same for interceptors (like the one in ng-class).  I'm leaning toward still reverting the ng-class part of https://github.com/angular/angular.js/commit/189461f9bf6fda18ddbd16c42f2e959cf939c3da in 1.6 just to avoid unexpected changes in 1.6 (no longer deep watching one-time bindings in ng-class), but that's debatable...

This looks like the last PR needed to get 1.6.5 out of the door, ist thart right?

Note that #15905 was properly fixed in 1.6, so this revert now only restores the "deep watch of one-time bindings in ng-class".  I keep trying to find a way revert that without reverting the parse.js changes, but that isn't proving easy. So yeah I think we should just revert this in 1.6. Feel free to merge if you agree...

Ok now that I've found #16059 we have to do this revert (or #16015!) in 1.6...

So what you are saying is, to restore " "deep watch of one-time bindings in ng-class" we can either merge

this PR (#15958)

or both of

#16015
#16009

(their respective 1.6 versions)
I assume by reverting we err on the safe side? Because we want to remove the deep watch in master anyway

It's actually

#16015 (which now has 2 commits)

or both of

#15958 (this pr)
#16059

While I really don't like reverting things, we should probably go the revert route for 1.6...  If you're ok with #16059 in 1.6 I can merge those 2 this weekend.

LGTM. Please revert and  merge #16059 too


Use StringIO in revcomp.cr

Hi!
In Crystal Strings are immutable. If you want to build a String you can use String#+ but that's slow because many intermediary strings will be created. Instead, the recommended way is to use a StringIO. So, I guess this is not "cheating" the benchmark.
Additionally, STDIN is not buffered so each_line is slow. Instead, you can do:
BufferedIO.new(STDIN).each_line do |line|
  ...
end

That brings speed and memory closer to that of C and Ruby. But, maybe this last thing is cheating. I think the best thing to do is either to make STDIN buffered by default (we would wrap it with a BufferedIO) or to document this too very well.
I'm pretty satisfied with the other benchmarks. Crystal might not be the fastest, but it has a good balance between readable/writeable code and efficiency :-)

thanks, pidgins also not the fastest

Yes, C is fast because it's reusing gmp objects as accumulators. Both Ruby and Crystal, when you do a + b, create a new object. We could add methods to BigInt that mutate self, saying that these are provided when you need more efficiency, but that you have to be careful with mutable structs (as always). Maybe we can call these methods 'add!', 'sub!', 'mul!', etc. What do you think?

when 0.6.2 planned?


Demo Integration Tests

Since the demos have been moved to another repo, we do not have an automated way to ensure new releases of the tool-chain don't break them.
We should add automated build & test of all projects in the demos repo to the monorepo's CI workflow.

I don't like the idea of having tests for integrations running in monorepo CI, It would be like React testing all the websites using React before releasing new version. We should have CI for that in integrations repo and test those there whenever we make new release for any of our integrations.

Yes I agree, this is a great point. This should instead live inside of the Demo repo's workflows.


Support "Code/Commit/Issues" Search

Hi,
I love your tool, very modern and intuitive, but it misses few things, like searching for code, commits, issues, users, etc...
I'm currently using this one for searching code, very similar to your tool, but nodejs: https://github.com/feinoujc/gh-search-cli

Hi, good morning and thank your for your suggestion! Let me provide some context: this extension calls the GitHub endpoint search/repositories/ as described here, which means that anything (or rather, any argument) indicated in the details here can in principle be added for search.
However, search for commits/issues/users call different endpoints (see /search/commits and links therein), implying in turn that the grammar, the arguments and the parsing follow other logic. Whilst it can technically be done (one could add a sub-command for a different endpoint) I would say this falls outside the scope of this extension (imagine users having to remember that maybe this flag works with /commits, this other flag works only with /issues/ and so forth).
However, since this project is gaining good traction, one idea could be to just implement another extension which more or less works as copy and paste of this one (same logic, same ui) only calling a different endpoint (which will be whatever you like of /issues/code/users and so on). What do you think? I am open to suggestions :)

I agree, very good idea.
Adding another sub-command, or extension, can be useful to swich between searching repos, codes, commits or issues.
If you implement this feature anytime soon, do I need to use my github_personal_token to search codes or issues ?

@jJit0 I have prepared a draft of what we discussed in a new extension gh-i: it searches for issues providing a range of flags to narrow down the search by title, body, label and so forth. It is obviously unpolished and quick, would you like to test it locally to see if this is along the lines of what you intended? Since there is no release yet you would have to clone the repository and gh extension install ..

The first release of gh-i is out. This should (at least partially) address the topic at hand here :)


[FEATURE] backend for the quote reply feature

Description
The frontend part of this issue is done, the original issue is #246 and the PR for that issue is #252.
Tasks (the main things to be accomplished):

the schema for the message should change to an object, one key should be the new message and the other key should be the quote message (which should be a reference to the message to be quoted)
if a new message doesn't have a quote reply, the value should be null.

This PR is open for discussion on the discord server (link in the readme) on a better way to do this, don't want to overcrowd this issue.
Screenshots
No response
Additional information
No response
👀 Have you checked if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

[X] I have read and understood the rules in the Contributing Guidelines

Are you willing to work on this issue ?
None

I've already started working on this. Can you please assign me this issue?

Hey @Dun-sin , Can you assign this to me ?

Hey @Dun-sin , Can you assign this to me ?

Definitely, thanks for wanting to contribute, Make sure you follow the rules 👉🏽here👈🏽, else your PR will not be accepted and will be closed. Good Luck

Hey @Dun-sin , Can you assign this to me ?

Definitely, thanks for wanting to contribute, Make sure you follow the rules 👉🏽here👈🏽, else your PR will not be accepted and will be closed. Good Luck

@karthikeyanvelusamy please do the backend based on the structure of the changes in this issue -> #169, it hasn't been merged yet because of the backend wasn't complete

hi @karthikeyanvelusamy are you still working on this? I need to close this Issue because with the use of Markdown it's not needed any more and markdown adds a better way to do this. I'm sorry for wasting your time after so long.


Link not accurate in docs.onflow.org/staking - pls fix

Instructions
Please fill out the template below to the best of your ability and include a label indicating which tool/service you were working with when you encountered the problem.
Problem
Search of the following txt in the file ...
If you created your account using the Flow Port, you can also stake and earn rewards using the Flow Port. Follow this step-by-step guide to stake using the Flow Port. Flow Port currently supports staking, delegation and reward withdrawal using Blocto and Ledger accounts / wallets.
The step-by-step guide link in now current/accurate - pls fix
Steps to Reproduce
bring up the url docs.onflow.org/staking and find the link - u'll know its wrong
Acceptance Criteria
fix the link
Context
learning Flow

The link seems fine. Could you add some detail about why you think it's not accurate?

the "step-by-step" internal link was wrong - it now works - thanks


enhancement Filter partition by hasData in pruner

To reduce unnecessary rpc invocation
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

XX

run buildall

run buildall


Emoji expression path problem

Because I am in China, your emoji components may not work well because they are not easily accessible in China: https://cdn.jsdelivr.net
So, what should I do? All emoticons report an error: https://cdn.jsdelivr.net/npm/emoji-datasource-apple @6.0.1/img/apple/64/1f62a. png net:: ERR-CONNECTION-TIMEd_OUT

I really like your component and hope you can update this error.


Localization for Spotify and lastfm

ups was for development...

Just a heads up that it's worth looking at https://github.com/jaedb/spotmop/blob/master/spotmop.php as the $localStorage.spotify array will be overwritten by the authentication process. I might look to nest this as $localStorage.spotify.auth.

Ah ok :) What about a new storage field just for localization?

The Spotify authentication process didn't ask for the scope user-read-private. So the Spotify API request https://api.spotify.com/v1/me din't return the country of the user.


Package not working for bare workflow apps

It seems this library uses the expo-constants package and reads values from the Constants.manifest object. Constants.manifest is null on bare apps so the package throws errors.  Not sure if this should be addressed here or in the expo-constants library.

@beaurushton if you're using a version of the Expo SDK that is 32 or lower, try pinning your package.json to import v1.0.8 of this package. It seems likely that the problem you're reporting is due to changes in #35 to support SDK33+

You could use this package instead. Seems the API is identical: https://github.com/ryanvanderpol/react-native-googleanalytics

@ryanvanderpol this is valid issue;

create expo project
add expo-anaylitics
eject

The manifest comes as empty, maybe we can check if manifest is empty at analytics.js and ask user to pass the data used from manifest, (name, slug, version) via additionalParameters, and fallback to it.
We can put a warning in the console everytime screenhit or hit is called. What do you think? i can send a pr.

Hi, any updates on this ? using this package for expo only and another one for ejected (bare react-native) is the only solution ?

Happy to accept a PR on this one! I've abandoned Expo and have just been using bare RN for all my recent projects so I haven't had a good opportunity to reproduce this one.


Bb 24 react router refactor

Refactored code to implement nav using React Router. Added 2 routes for Home and Payment pages. Refactored header code with Links. No changes to CSS file names.

Thanks for the note. It was an accidental removal. The Strict Mode is added back in


PHPLIB-858: Adding tests against MongoDB 6.0

https://jira.mongodb.org/browse/PHPLIB-858

There was one test failure, but it appears to be unrelated. Likely just another flaky change stream test for sharded clusters:
MongoDB.Tests.Operation.WatchFunctionalTest.testNextAdvancesKey
 [2022/05/23 22:32:34.665] FAILURE:  (PHPUnit\Framework\ExpectationFailedException)
 [2022/05/23 22:32:34.665] MongoDB\Tests\Operation\WatchFunctionalTest::testNextAdvancesKey
 [2022/05/23 22:32:34.665] Failed asserting that null is identical to 1.
 [2022/05/23 22:32:34.665] /data/mci/cafef06d16c376cb3e1ba9a9592540e1/src/tests/Operation/WatchFunctionalTest.php:1079

@aleksandr-rudo: Please hold off on merging this. I just realized that the corresponding PHPC PR (https://github.com/mongodb/mongo-php-driver/pull/1323) encountered a build failure attempting to download http://downloads.10gen.com/linux/mongodb-linux-x86_64-enterprise-debian92-6.0.0-rc5.tgz.
Since PHPLIB does not include 6.0 in its CI matrix for PRs, we didn't see an error here. I'll dig into this a bit to see what's wrong.

GitHub CI changes look good. Let's just remove the Evergreen changes for now and merge with only GitHub. Then we can bump PHPLIB-858 back to blocked on the corresponding BUILD ticket and deal with Evergreen in a second PR.


Create nightly builds on dev branch

This will make nightly builds on the dev branch, and stable builds on the main branch. The if condition will make sure it makes the correct type of build for the correct branch.

Finally done!!! Pushing it to dev branch.


Reduce number of classical instruction edges in InstructionBlock::gra…

The ultimate goal of this PR is to simplify the InstructionBlock::graph and thereby improve the ability of a hardware scheduler to schedule a Quil program by reducing the number of edges between classical instructions and block start/end.
Two types of edges in the InstructionBlock::graph are deemed extraneous in this work:

An edge from two consecutive classical instructions that read from / write to different memory regions. Rather than insist on classical instruction execute in the particular order they are written in a Quil program, only represent ordering of classical Quil instructions based upon the memory regions they read and write to (this is already done with MemoryAccessQueue).
Edges from BlockStart, if the node has other incoming edges, or to BlockEnd, if the node has other outgoing edges. Note that while this could apply equally to InstructionRole::RfControl, this change set deliberately only impacts edges to and from classical instructions.

DECLARE params1 REAL[10]
DECLARE params2 REAL[10]
DECLARE params3 REAL[10]
DECLARE params4 REAL[10]
DECLARE integer1 INTEGER[10]

LOAD params1[0] params2 integers[0] # LOAD_1 in graphs below
SHIFT-PHASE 0 "rf" params1[0]
LOAD params3[0] params4 integers[0] # LOAD_2 in graphs below

Old representation of InstructionBlock::graph.
flowchart TD
    BlockStart --> LOAD_1
    BlockStart --> SHIFT-PHASE
    LOAD_1 --> SHIFT-PHASE
    LOAD_1 --> LOAD_2
    LOAD_1 --> BlockEnd
    LOAD_2 --> BlockEnd
    SHIFT-PHASE --> BlockEnd

In the original algorithm, there is an edge from LOAD_1 to BlockEnd because there are pending reads on params1 and integers.
New representation of InstructionBlock::graph.
flowchart TD
    BlockStart --> LOAD_1
    BlockStart --> LOAD_2
    LOAD_1 --> SHIFT-PHASE
    LOAD_2 --> BlockEnd
    SHIFT-PHASE --> BlockEnd

There are three invariants of the InstructionBlock::graph that remain unchanged:

There is always a path connecting the BlockStart to any classical node in the graph.
There is always a path connecting any classical node in the graph to the BlockEnd.
These invariants pertain to the BlockStart and BlockEnd as well. In other words, there is always a connecting path from the BlockStart to the BlockEnd regardless as to whether there are any instructions in the block.

Closing in favor of #350 with its fixes


How to connect to Byron

Hi,
I am developing a simple, albeit custom Cardano wallet using NodeJS  + Typescript. As advised by @SebastienGllmt I decided to use js-cardano-wasm to integrate with blockchain. For starters, I'd like to integrate with Byron testnet.
How do I connect to Byron instead of mainnet? Following your cardano-wallet example there is that BlockchainSettings class with its mainnet method. Digging through an implementation it seems this method provides ProtocolMagic with some arbitrary value<PHONE_NUMBER>) which, I presume, represents mainnet. That's some magic indeed!
I'd imagine I need to use from_json method of BlockchainSettings to connect to Byron instead. Can I get some info on how to do this?
Thanks,
KSS

https://github.com/Emurgo/yoroi-frontend/blob/shelley/config/testnet.json

Thanks for a quick reply, @SebastienGllmt .
I tried to connect to Byron like this: Cardano.BlockchainSettings.from_json({ "protocol_magic":<PHONE_NUMBER> }) .
Then I ran this example: https://github.com/input-output-hk/js-cardano-wasm/tree/master/cardano-wallet using mnemonics&password for an existing wallet that I created via REST API of a Byron Node. As a result I got an address which did not seem to be connected to that wallet, at least according to API&Daedalus.
Please note that I have successfully interacted with this wallet using both REST API and Daedalus GUI in the past.
I have tried to, using Daedalus, send a transaction from another wallet to an address I got using previous step. Daedalus treated this address as a valid one. Indeed, my transaction was successfully executed but it was not send to an account connected to mnemonics&password  used in previous step. Was I connected to Byron or not, then?
On top of that, I changed Cardano.BlockchainSettings.from_json({ "protocol_magic":<PHONE_NUMBER> }) to Cardano.BlockchainSettings.from_json({ "protocol_magic": some_random_int }) . I would imagine that sample code would not execute since some_random_int does not represent any known network. However, it did and I got some address. Why did it work? Has it created some fake, stubbed network?
Does Cardano.BlockchainSettings.from_json({ "protocol_magic":<PHONE_NUMBER> }) indeed connect me to Byron? If so, does it use a local Cardano node or does it hit some remote Cardano node exposed as an open service?

I can't speak to the Cardano node APi because I didn't work on that. You can generate an address with any protocol magic but only a few of them have actual networks for them. This is the Byron testnet explorer if you want to look for your transaction: https://cardano-explorer.cardano-testnet.iohkdev.io/

Yeah, I can find it there. This means I was connected to Byron. I will try to play around with and try to figure out why Cardano.Bip44RootPrivateKey.recover hasn't retrieved an exisiting wallet but instead, apparently, created a new one.
Last question then. Sorry for asking so many. Can you please explain how ProtocolMagic works undercover? Does it use a local Cardano node or does it hit some remote Cardano node exposed as an open service?

No protocol magic is just used to create addresses. Different protocol magic results in different addresses


WIP: Update Falco Sidekick Helm chart for 2.19.0

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

If this PR will release a new chart version please make sure to also uncomment the following line:

/kind chart-release

Any specific area of the project related to this PR?

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

/area falco-chart

/area falco-exporter-chart

/area falcosidekick

What this PR does / why we need it:
There are updates to falcosidekick. Need to update this Helm chart too.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign leogr after the PR has been reviewed.
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

LGTM label has been added.  Git tree hash: 7dcf7466ae6280184bcc6a6d2c57e38ed42be4e1

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif
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 [Issif]

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

I'll try to release 2.19.0 ASAP, thank you again @KeisukeYamashita

@KeisukeYamashita I release 0.1.33 of the chart few minutes ago, for fixing issues with GCP PubSub values, you have to bump the release version and rebase the changelog, thanks.

New changes are detected. LGTM label has been removed.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign issif after the PR has been reviewed.
You can assign the PR to them by writing /assign @issif in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign issif after the PR has been reviewed.
You can assign the PR to them by writing /assign @issif in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

@Issif  Thank you for your kind notice. I'm ready now for the next release 🚀

I will add the AWS Cloud Watch Log configuration too

New changes are detected. LGTM label has been removed.

@Issif  New Falco release has released, this PR is ready! PTAL when you have a chance.

LGTM label has been added.  Git tree hash: 2e15b72d55774aab6ca9fd43123f102db1c438e6

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif
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 [Issif]

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


Add Apify SDK for Python to the Python images

After the Python SDK is published, we need to have it preinstalled in the Python actor images instead of the API client.
We need:

[x] base image with just Python SDK
[x] base image with Python SDK and Selenium
[x] base image with Python SDK and Playwright

This is done by #92, #93 and #94


Accessibility Audits & Upgrades in Samvera

Kevin Kochanski
<EMAIL_ADDRESS>Federal law requires a standard of accessibility on any project that receives federal funds. Creating accessible applications is also socially responsible, and implementing these practices can help us set better expectations as community leaders. In a community dedicated to preservation and providing access to to a broad range of assets, accessibility standards should be a priority. We'll explain audits and certification levels, as well as accessibility features that could provide significant value to digital repositories. Using Hyku as an example, a developer will demonstrate practices that are easy to incorporate into the dev process, as well as demo practical examples.

8/22 Lea Ann Bradford withdrawn

Confirmed 8/23

8/27 Registered


[WIP] Add ansatz using tapered excitations to qubit tapering demo

This PR modifies the circuit ansatz in the tapering demo to now use tapered excitations. This update correction does not have any effect on the conclusion/results in the demo.

PR was closed automatically as the dev branch was recreated. Re-opened the PR and now it targets master.
If the demo does use any post-v0.26.0 features from PennyLane, the target branch should be changed again to dev.


Slyfind - a hidden malware detection

This is the initial version of the Slyfind and it has prerequisites and dependencies .
The next version will be a standalone windows applications with integration of the Java , python, node.js and wireshark

Thank you mam for reviewing the merge request and for your insightful feedback on our codebase. We greatly value your input and are committed to making the necessary enhancements to improve our project's quality and maintainability.


Add fields for city and country

I'm reasonably certain that this will be the first thing people want to search by.
We could add this to the geocoder job easily.

Good call. Seems like the Burden city/country data is also pretty clean, and it would be good to be able to import that smoothly.

@madeleineb Lmk if you want me to get this in for the mvp

@gnilekaw We're definitely gonna do it anyway, so if it's fast to add the geocoder job, while not part of that 100% bare-minimum-critical information, it will help the MVP goal of sending useful info on. Let's do it.


feat: AND/OR query filters

Enables users to execute queries with logical operators.
Query Example:
{
  musicians(where: {OR: {name: "John", id: "m2"}}) {
    name
    id
  }
}

Question:  should we limit this to only one level deep?
Closes #579

Seeing AND when everything else is lower case feels a little strange.

In the ticket and to make it more differentiable made these logical filters uppercase. Don’t have a preference so happy to do whatever you think is the best.

so you could have X OR (Y AND Z), and you could have X AND (Y OR Z) but not X OR (Y OR Z)?

@azf20 updated it so it no longer is limiting. User can make as much recursively deep AND/OR filter they if they chose to do so.

there's some test failures.

@lutter fixed the schema tests

@saihaj i think we need a rebase there, and then we are good to go in terms of code review?

Quick note on rebasing: please always rebase with git rebase master <mybranch> not by merging master into the branch since that leads to funky looking merge commits.

If we proceed with https://github.com/graphprotocol/graph-node/pull/4080 should we close this @saihaj ?