remove removeAllKeysUnless from interfaces and its implemntation

fix issue #861

If you click on the failing unit tests, you'll see that we have a check to ensure that public-facing apis aren't broken by commits. It's fine in this case because it's a public facing commit so you'll need to grab the updated hash in the failing unit test log and replace that in the build.gradle for the plugin api. Otherwise it looks good!

@yehia67 Let me know if you have any confusion about what to do next

@RatanRSur I am trying to figure out how to the hash is calculated on the build.gradel  file.

I check this line
checkPluginAPIChanges.dependsOn(':plugin-api:checkAPIChanges')
but I am not sure yet as I am not familiar with gradel.

found it found it sorry. I checked the wrong build.gradel file I will commit it now

Cool, just for reference, this is the message:
Execution failed for task ':plugin-api:checkAPIChanges'.
> For the Plugin APIs the checksum of the project did not match what was expected.

  If this is a deliberate change where you have thought through backwards compatibility,
  then update "Expected" for "Calculated" in the appropriate build.gradle as the knownHash for this task.
  Expected   : x6hLH75JBKLM8mNFz7n0ALRw4TWiDONJuum53da4jTY=
  Calculated : d2HD6T1USSbVL9OftLuNlmJO25d1WscqrxCIimdhtgM=

@RatanRSur  yes I replaced this hash but I don't understand this error
c2cc993041352da0db37935cd939cda333d4ec26 is missing Signed-off-by line.
Do I need to update branch?

If you go to the details on the DCO action failure, you'll see the steps to take. Your most recent commit wasn't DCO signed I suppose.

yes I use this command to fix the problem
git push --force-with-lease origin 861-Remove-unneeded-removeAllKeysUnless-method-from-key-value-storage-interfaces

@yehia67 There's another contributors commit in the PR, would you mind removing that and force pushing?

No, I don't mind at all.

Could you please give me detailed instructions as I am new at open-source contribution and I am afraid I will cause a bug.

Sure thing!
I can always give you the fish eventually but I'll try teaching you to fish first so you can carry this knowledge onto your future contributions. You'll want to use git rebase. Here is a guide about it
https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History
You want to use rebase to get rid of the commit you don't recognize and that post should show how you might do that.

Thank you! I should remove the last commit I had done then force push right?

Not the last commit you did but the commit named: Expose price bump to a CLI flag. (#930)

Actually, I just remembered that this is going to be squashed into one commit so I don't think it matters.

Okay, thank you @RatanRSur  I really appreciate your help.

Feel free to peruse the other good first issues and see if there's anything else you want to help with.


Headlines behaving strangely

Headline 1 works fine but headline 2 behaves strangely...

This looks like an issue with bullets to me. Can you confirm that the issue still persists without the bullets plugin enabled?

nope on removing my org-bullets it still remains the same

I might be mistaken, but it looks a bit similar to this issue: https://github.com/lukas-reineke/headlines.nvim/issues/41.

yes seems like the issue thanks


geonkick: 2.9.1 -> 2.10.2

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

3.0.1 has been released
https://geonkick.org/2023/12/03/geonkick-version-3-0-1-has-been-released.html

@luzpaz Thanks for the heads up!
I haven't set it up to build vst3 yet, I'm hoping upstream will include the vst3 sdk in the source, see https://github.com/Geonkick-Synthesizer/geonkick/issues/9

v3.3.1 released https://github.com/Geonkick-Synthesizer/geonkick/blob/main/CHANGELOG.md#331

@luzpaz Again, thanks for the heads up.
Upstream does not want to include the vst3 sdk.
I don't have time at the moment to make the vst3 work.
Maybe we should merge without it for now and if someone needs it they can add it themselves.

Anyone care to take a look at this again?

Result of nixpkgs-review pr 267887 run on x86_64-linux 1

1 package built:

geonkick


Update README.md

Fix typo for authorized-https-endpoint folder

Are you sure that's the right folder name? https://github.com/firebase/functions-samples/tree/master/authorized-https-endpoint

@morganchen12 well, yes. I've just cloned the repo, tried to change dir into the authenticated-https-endpoint and so spotted that the directory is actually called authorized-https-endpoint.
Or am I missing something?

Whoops, I misread your diff. Thanks!


Extend coverage of this repo to Server 2019?

The readme for the MicrosoftDocs/windowsserverdocs (https://github.com/MicrosoftDocs/windowsserverdocs/blob/master/README.md) says if covers explicitly Server 2016.
With the launch of Windows Server 2019, I'd like to see this page, and the repo, be extended to cover 2019. From my work with 2019. existing 2016 content is still valid except possibly in a few minor cases.

Thanks for pointing this out - hadn't looked at the readme for a long time. I've cleaned it up and added reference to 2019.

I ask this because I want to start adding some 2019 content to some of these pages...

Fantastic!


mautrix-telegram: 0.9.0 -> 0.10.0

Motivation for this change
ChangeLog: https://github.com/tulir/mautrix-telegram/releases/tag/v0.10.0
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 126872 at 3ca4e7a5 run on x86_64-linux 1

1 package failed to build:

mautrix-signal

5 packages built successfully:

mautrix-telegram
python38Packages.mautrix (python38Packages.mautrix-appservice)
python38Packages.telethon
python39Packages.mautrix (python39Packages.mautrix-appservice)
python39Packages.telethon

5 suggestions:

warning: unused-argument
Unused argument: async_generator.
Near pkgs/development/python-modules/telethon/default.nix:1:48:
  |
1 | { lib, buildPythonPackage, fetchPypi, openssl, async_generator, rsa, pyaes, pythonOlder }:
  |                                                ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/servers/mautrix-telegram/default.nix:70:0:
   |
70 |     description = "A Matrix-Telegram hybrid puppeting/relaybot bridge";
   | ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/servers/mautrix-telegram/default.nix:24:15:
   |
24 |   patches = [ ./0001-Re-add-entrypoint.patch ./0002-Don-t-depend-on-pytest-runner.patch ];
   |               ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/servers/mautrix-telegram/default.nix:24:46:
   |
24 |   patches = [ ./0001-Re-add-entrypoint.patch ./0002-Don-t-depend-on-pytest-runner.patch ];
   |                                              ^

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/development/python-modules/telethon/default.nix:30:0:
   |
30 |     description = "Full-featured Telegram client library for Python 3";
   | ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

Oh I wasn't aware of mautrix-signal... I guess we'll just keep it open then.

Oh I wasn't aware of mautrix-signal... I guess we'll just keep it open then.

Maybe we can widen the version range if it still works with the new one?

I neither use signal nor mautrix-signal, so I don't have a reasonable way to test it. But is there anything wrong with adding mautrix_0_8 & mautrix_0_9 here for now and remove _0_8 when the new mautrix-signal is out? These are applications that are incompatible with the other version, so a mix-up seems rather unlikely to me or am I missing some other issue with this approach?

Mautrix-signal should override the mautrix version.
This needs to be merged however because we have a version of ruamel.yaml in python-unstable that's only supported by mautrix-telegram 0.10.0.

Can someone who uses mautrix-signal please test this?
cc @expipiplus1

Result of nixpkgs-review pr 126872 run on x86_64-linux 1

6 packages built:

mautrix-signal
mautrix-telegram
python38Packages.mautrix
python38Packages.telethon
python39Packages.mautrix
python39Packages.telethon


Upload Symbols Failed The archive did not include a dSYM for the librealm_dart.dylib Ensure that the archive's dSYM folder includes a DWARF file for librealm_dart.dylib with the expected UUIDs.

What happened?
Upload Symbols Failed The archive did not include a dSYM for the librealm_dart.dylib Ensure that the archive's dSYM folder includes a DWARF file for librealm_dart.dylib with the expected UUIDs. Xcoce 18
Repro steps
Upload Symbols Failed The archive did not include a dSYM for the librealm_dart.dylib Ensure that the archive's dSYM folder includes a DWARF file for librealm_dart.dylib with the expected UUIDs.
Version
3.24
What Atlas Services are you using?
Local Database only
What type of application is this?
Flutter Application
Client OS and version
MACOS
Code snippets
realm: ^20.0.0
Stacktrace of the exception/crash you're getting
realm: ^20.0.0

Relevant log output
realm: ^20.0.0

Same problem


Revert "Fix windows CI"

This reverts commit 806ac6b62bdd5a5cebedd6fb41a7d7800c1d19ec (#700).
That PR did not fix the problem correctly.

bors r+


CASMCMS-7703 Update jobs access pool to be customer-management

Summary and Scope
Update the default access pool for IMS jobs to be customer-management from customer-access. This change is in support of the work for the bifurcated-CAN and moves the IMS jobs to the management network. Essentially, this means that IMS Job pods are accessible to administrators only via the customer-management network. According to @johren-hpe this should not change any pod to pod communication, so it should not affect CFS communicating with IMS jobs.
Is this change backwards incompatible, backwards compatible, or a backwards compatible bugfix? backwards compatible
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Resolves CASMCMS-7703

Testing
List the environments in which these changes were tested.
Tested on:

<development system>
Local development environment
Virtual Shasta

Test description:
How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
Were continuous integration tests run? If not, why?
Was upgrade tested? If not, why?
Was downgrade tested? If not, why?
Were new tests (or test issues/Jiras) created for this change?

Risks and Mitigations
Are there known issues with these changes? Any other special considerations? None
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] CHANGELOG.md updated
[ ] Testing is appropriate and complete, if applicable
[x] HPC Product Announcement prepared, if applicable

ncn-m001:~/ecozzi # i logs cray-ims-cca7bd3e-97d3-4d8a-a2d0-b3b49705c30e-customize-s5gqc -c buildenv-sidecar -f
Copying SMS CA Public Certificate to target image root
Running user shell for customize action
IMS SSH shell environment is ready.
To mark this shell as successful, touch the file "/mnt/image/complete".
To mark this shell as failed, touch the file "/mnt/image/failed".
Waiting for User to mark this shell as either successful or failed.

{
    "ims_job_record": {
        "artifact_id": "65ff2efc-2422-417e-bbf9-4a97963354c0",
        "build_env_size": 10,
        "created": "2021-12-17T21:23:23.674059+00:00",
        "enable_debug": false,
        "id": "cca7bd3e-97d3-4d8a-a2d0-b3b49705c30e",
        "image_root_archive_name": "ecozzi-test",
        "initrd_file_name": "initrd",
        "job_type": "customize",
        "kernel_file_name": "vmlinuz",
        "kernel_parameters_file_name": "kernel-parameters",
        "kubernetes_configmap": "cray-ims-cca7bd3e-97d3-4d8a-a2d0-b3b49705c30e-configmap",
        "kubernetes_job": "cray-ims-cca7bd3e-97d3-4d8a-a2d0-b3b49705c30e-customize",
        "kubernetes_namespace": "ims",
        "kubernetes_service": "cray-ims-cca7bd3e-97d3-4d8a-a2d0-b3b49705c30e-service",
        "public_key_id": "5e8fbb82-af93-4265-8c61-ef474aa1ea6b",
        "resultant_image_id": null,
        "ssh_containers": [
            {
                "connection_info": {
                    "cluster.local": {
                        "host": "cray-ims-cca7bd3e-97d3-4d8a-a2d0-b3b49705c30e-service.ims.svc.cluster.local",
                        "port": 22
                    },
                    "customer_access": {
                        "host": "cca7bd3e-97d3-4d8a-a2d0-b3b49705c30e.ims.cmn.wasp.dev.cray.com",
                        "port": 22
                    }
                },
                "jail": false,
                "name": "customize",
                "status": "pending"
            }
        ],
        "status": "waiting_on_user"
    },
    "result": "success"
}
Waiting for SSH container to set /mnt/image/exiting flag
ssh cca7bd3e-97d3-4d8a-a2d0-b3b49705c30e.ims.cmn.wasp.dev.cray.c^C
ncn-m001:~/ecozzi # ssh cca7bd3e-97d3-4d8a-a2d0-b3b49705c30e.ims.cmn.wasp.dev.cray.com
The authenticity of host 'cca7bd3e-97d3-4d8a-a2d0-b3b49705c30e.ims.cmn.wasp.dev.cray.com (<IP_ADDRESS>)' can't be established.
ECDSA key fingerprint is SHA256:t8ACQkIqBaLv7TpBbi4uiC0/lo7/mNLKwr0CNcy9BA0.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'cca7bd3e-97d3-4d8a-a2d0-b3b49705c30e.ims.cmn.wasp.dev.cray.com,<IP_ADDRESS>' (ECDSA) to the list of known hosts.
Have a lot of fun...


deployment().properties.templateLink does not exist

Unable to process template language expressions for resource '/subscriptions/XX/resourceGroups/test/providers/Microsoft.Resources/deployments/linkedTemplate' at line '1' and column '868'. 'The language expression property 'templateLink' doesn't exist, available properties are 'template, parameters, mode, provisioningState'.'"
Now what?

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

ID: 6ec87df7-43e5-2d11-3546-9f338534e560
Version Independent ID: c5319e4e-7d0c-6c94-b53e-6689f2d041c2
Content: Link templates for Azure deployment
Content Source: articles/azure-resource-manager/resource-group-linked-templates.md
Service: azure-resource-manager
Product: unspecified
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@sabbour - template, parameters, mode, and provisioningState are the properties returned from the deployment() function. Do you have that expression somewhere in your template?

Sorry, I think I misinterpreted your question. Let me double-check the values returned when used to construct URIs for linked templates.

@sabbour - templateLink is returned when you have passed in a URI for the template. If you use a local template, the templateLink property is not returned. Were you using a URI or local template?

@sabbour - I had exactly the same error, when you try to link a local path C:\temp\mytemplate.json or if you use a local url http://localhost/mytemplate.json. This will lead to a returned object of a local template, which does not unclude the "templateLink" property. You have to have the linked template somewhere available with a valid url. Either you upload it to a storage account or on a public place.
Refer to the following document for that: https://github.com/Azure/azure-quickstart-templates/blob/master/1-CONTRIBUTION-GUIDE/best-practices.md#deployment-artifacts-nested-templates-scripts

@sabbour - I added a couple of sentences that clarify when templateLink is available. Thanks for bringing up this issue.
#please-close

@sabbour We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

@maniankara - that is interesting. I am not sure what is happening here, but perhaps the portal creates a local copy when deploying from that interface. The easiest option is use PowerShell or CLI to deploy and directly reference the external template. If you really need to use the Portal interface, your best option might be to replace the use of that expression with hard-coded values that point to your script folder.

in the line
  "uri": "[concat(uri(deployment().properties.templateLink.uri, 'helloworld.json'), parameters('containerSasToken'))]"

shouldn't it be
  "uri": "[concat(uri(deployment().properties.templateLink.uri, 'helloworld.json?'), parameters('containerSasToken'))]"


Using 'getgrgid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

==> 正在开始 build()...
*** Setting version to '2.41-1' from user.
# github.com/snapcore/snapd/cmd/snap-update-ns
/usr/bin/ld: /tmp/go-link-492287047/000017.o: in function `_cgo_3298b262a8f6_Cfunc_mygetgrouplist':
getgrouplist_unix.cgo2.c:(.text+0x24): 警告：Using 'getgrouplist' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-492287047/000016.o: in function `_cgo_3298b262a8f6_Cfunc_mygetgrgid_r':
cgo_lookup_unix.cgo2.c:(.text+0x34): 警告：Using 'getgrgid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-492287047/000016.o: in function `_cgo_3298b262a8f6_Cfunc_mygetgrnam_r':
cgo_lookup_unix.cgo2.c:(.text+0x94): 警告：Using 'getgrnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-492287047/000016.o: in function `_cgo_3298b262a8f6_Cfunc_mygetpwnam_r':
cgo_lookup_unix.cgo2.c:(.text+0xf4): 警告：Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
/usr/bin/ld: /tmp/go-link-492287047/000016.o: in function `_cgo_3298b262a8f6_Cfunc_mygetpwuid_r':
cgo_lookup_unix.cgo2.c:(.text+0x154): 警告：Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
# github.com/snapcore/snapd/cmd/snap-exec
/usr/bin/ld: /tmp/go-link-866071934/000002.o: in function `_cgo_3298b262a8f6_Cfunc_mygetgrouplist':
getgrouplist_unix.cgo2.c:(.text+0x24): 警告：Using 'getgrouplist' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking

Could you provide an example of the code that produced the error, or re-file this issue with the issue template filled out? It's not clear to me if this is a bug report, a question, or how this message was triggered.


Fix for StatefulWriter.check_acked_status [5270]

Not calling onWriterChangeReceivedByAll twice for the same sequence number.

Build status:

Linux
Mac
Windows


P2P sharing of certificates

Brainstorming:

How can peer to peer communication be enabled? How would a certificate sharing via EDC look like?
Analyze impact on digital twin, aspect model, EDC asset creation.

Closing issue to enable archiving of repository bpdm-certificate-management.


Google Calendar intergration

Dup Cal entry on time edit, Cal entry only starts on day it was created.

Fixed calendar entry starting on same day as course creation in commit 44b45f88564c4fa8d1d59ed5e3291a0cdd47ab32

Further fixed entry starting on same day (PM was set to AM, now fixed) and editing existing cal events now working in commit d794aef99f593d5461b84e4c85654a16a6395baa


Manual 2.4.0 upgrade not restarting/Stopping UI

Just installed the 2.4.0 ZDEW client by manually downloading and installing.  It appears to not stop the UI/(services?) during the upgrade.  Therefore when finished, and you open the ZDEW it is still showing as the previous version.

I would expect the installer to stop the UI and service prior to installing the new components.

It definitely should be doing that. I've seen this happen rarely, but it's not common. The installer software we use IS supposed to close all the components.
I always test the automatic upgrade functionality and the manual upgrade functionality but if it fails, unfortunately it's never been something we could fix and has always been "something Windows"... 🫤
Does the problem persist if you quit the UI? If it's able to be reproduce we could attempt to get installer logs and I could analyze them and submit them to advanced installer if need be.

I sent to be able to reproduce as I did out twice to capture the output. Let me know how to generate the logs and I will see what I can do

I have attached installer logs.  Does not terminate the apps at all.   They remain open through out install.
MSIDA4C.LOG
These are some interesting lines:
MSI (s) (94:3C) [12:16:15:816]: PROPERTY CHANGE: Adding PrimaryVolumePath property. Its value is 'C:'.
Info 1603. The file C:\Program Files (x86)\NetFoundry Inc\Ziti Desktop Edge\ZitiDesktopEdge.exe is being held in use by the following process: Name: ZitiDesktopEdge, Id: 36552, Window Title: '(not determined yet)'.  Close that application and retry.
Info 1603. The file C:\Program Files (x86)\NetFoundry Inc\Ziti Desktop Edge\ZitiUpdateService.exe is being held in use by the following process: Name: ZitiUpdateService, Id: 19848, Window Title: '(not determined yet)'.  Close that application and retry.
Info 1603. The file C:\Program Files (x86)\NetFoundry Inc\Ziti Desktop Edge\ziti-edge-tunnel.exe is being held in use by the following process: Name: ziti-edge-tunnel, Id: 22536, Window Title: '(not determined yet)'.  Close that application and retry.
MSI (s) (94:3C) [12:17:31:470]: 3 application(s) had been reported to have files in use.
MSI (c) (AC:0C) [12:17:31:476]: File In Use: -ZitiDesktopEdge- Window could not be found. Process ID: 36552
MSI (c) (AC:0C) [12:17:31:477]: File In Use: -ZitiUpdateService- Window could not be found. Process ID: 19848
MSI (c) (AC:0C) [12:17:31:478]: File In Use: -ziti-edge-tunnel- Window could not be found. Process ID: 22536
MSI (c) (AC:0C) [12:17:31:478]: No window with title could be found for FilesInUse
MSI (s) (94:3C) [12:17:31:481]: PROPERTY CHANGE: Modifying PrimaryVolumeSpaceAvailable property. Its current value is '128823808'. Its new value: '128540872'.
MSI (s) (94:3C) [12:17:31:481]: PROPERTY CHANGE: Modifying PrimaryVolumeSpaceRemaining property. Its current value is '128795380'. Its new value: '128512444'.
Action ended 12:17:31: InstallValidate. Return value 1.

Not sure if the return value of 1 is good or bad.

I installed Advanced Installer and started to have a poke around.  Looks fine (from what I have seen), but I wonder if the *Include maximum version in range" needs to be checked as well as per https://www.advancedinstaller.com/forums/viewtopic.php?t=35614.
The .aip file from GitHub, is showing 2.3.1 as the product version.  This is probably fine as this is a beta and hasn't been submitted to GitHub yet.

The 2.4.0 install file has the correct info on the file (at least in the details section)

I'm sorry i've lost sight of this. Circling back to it, you have decided to install updates manually instead of using the automatic update facility, correct? What version were you coming from - do you recall? If you reinstalled that older version, does this still happen during upgrade?
As for the .aip difference, that ends up getting set at build time by https://github.com/openziti/desktop-edge-win/blob/release-next/Installer/build.ps1#L89 so the difference in source and release is not uncommon

closing for now. if this issue happens again we can open this back up and diagnose


missing SRP_A in Cognito ChallengeNameType

Describe the feature
"SRP_A" challenge type is missing, one can only handle it via Unknown(crate::types::UnknownVariantValue)
Use Case
cognito custom auth flow lambda triggers implementation
Proposed Solution
add "SRP_A" SrpA to ChallengeNameType
Other Information
aws-sdk-cognitoidentityprovider = "0.22"
Acknowledgements

[X] I may be able to implement this feature request
[ ] This feature might incur a breaking change

A note for the community

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment

thanks for filing this issue! this appears to be an issue in the upstream CognitoIdentity model. Assigning to @jmklix to triage and move to aws-sdk

Opened new issues here. Closing this one


chore: update trpc to use server caller

moves server caller to use createCaller now that we've added the ability to pass it a createContext function
will wait for PR (https://github.com/trpc/trpc/pull/5244) to be merged then revert to using the next tag

cc @RhysSullivan iirc you preffered the server caller approach so I think you'll like this change. Reason I didn't like this before was the nested awaits required when you had async context (see https://github.com/trpc/trpc/pull/5244#issue-2058751912) , but that's fixed by allowing the createCaller function be passed a function


Is anyone working on updates for new version of API?

Etsy is pushing out a brand new version of their API in early February. Is anyone working on amending this gem so that it is compatible with the new version? I do not want to reinvent the wheel if the work is already being done. Otherwise I will begin working on adjustments ASAP

@iyerushalmi There was some work done 3 years ago in the faraday branch that looks at implementing a query builder:
https://github.com/kytrinyx/etsy/blob/faraday/lib/etsy/query.rb
That would make the gem much more flexible, and it might be a lot easier to handle the new API.

Is anyone doing current work on this? Deprecated endpoints are set to be removed August 30th 2017.

@cHaden I'm not sure if anyone is doing current work on this—there have been a few contributions in the past few months, but I don't know if anyone has been actively keeping up to date with new and deprecated endpoints.
If you outline the suggested work that needs to be done, and/or submit PRs I'd be happy to review, however I don't have the bandwidth to do any of the development work myself at the time.


I218 move technical

@daren-thomas would you merge this bitte?

this changes the reference case, right? has that already been changed?

waiting for this, to do the modifications in the reference case

done!

can you please delete the branch if you don't need it anymore?


Instaloader no longer downloads. Failed to parse

Describe the bug
Instaloader no longer downloads posts, stories or any other Instagram content.
To Reproduce
e.g. instaloader joebiden
Expected behavior
Download all posts from user joebiden feed.
Error messages and tracebacks
JSON Query to joebiden/feed/: Failed to parse: https://www.instagram.com/joebiden/feed/ [retrying; skip with ^C]
JSON Query to joebiden/feed/: Failed to parse: https://www.instagram.com/joebiden/feed/ [retrying; skip with ^C]
joebiden: JSON Query to joebiden/feed/: Failed to parse: https://www.instagram.com/joebiden/feed/
Errors or warnings occurred:
joebiden: JSON Query to joebiden/feed/: Failed to parse: https://www.instagram.com/joebiden/feed/
Instaloader version
4.6.2
Additional context
Everything worked fine before, but today without changing anything stopped working. I'm running on Ubuntu 20.10. I tried reinstalling instaloader, I tried rebooting pc, I tried to use another user-agent, I tried removing instagram account from instaloader (~/.config/instaloader/) but nothing helps. Tested on another machine (Linux Mint 20.1) and on that machine works fine. Don't know what happened on Ubuntu :(

I just tried Instaloader on a fresh Ubuntu 20.10 and it works just fine. We cannot give any support for problems related to your system setup here.


How should GUI display hashes?

At the moment outputs are displayed as raw tuples of (name, hash) - this should be improved (with hover-over?)

You are either interested in runs from the same script that produced the exact same files or different files. Perhaps we should add tabs (or something else that can show or hide information on a website) for listing runs generated by the same script with the same hash for the output file and listing runs generated by the same script with a different hash.
And some functionality that somehow compares two runs would be also useful, I think

I think the way we're displaying hashes works well at the moment, particularly as you can click on a hash to search for it - so I'm going to close this and we can reopen if we run into problems with the way they are displayed.


Couchpotato: imdbid = sys.argv[1] IndexError: list index out of range

Having trouble w/the automation using the script on my Synology NAS.  It was working fine previously - but I updated to your most recent release and now I can't seem to get it working with Couchpotato (Sickrage works fine!).
My log from Couchpotato below:
11-04 00:18:02 INFO
[ PostProcess] MP4 Automator - Post processing script initialized
11-04 00:18:02 INFO
[ PostProcess] Executing post processing on file /volume1/DiskStation/Movies/Movie.mkv
11-04 00:18:03 INFO
[ PostProcess] 2015-11-04 00:18:03 - CouchPotatoPostConversion - INFO - MP4 Automator - Post processing script initialized 2015-11-04 00:18:03 - readSettings - WARNING - Audio bitrate was invalid, defaulting to 256 per channel.
11-04 00:18:03 INFO
[ PostProcess] Traceback (most recent call last): File "/usr/local/couchpotatoserver/scripts/sickbeard_mp4_automator/postCouchPotato.py", line 21, in  imdbid = sys.argv[1] IndexError: list index out of range
11-04 00:18:03 INFO
[ PostProcess] Return code: 1
Is there something wrong with postCouchPotato.py?

Seems like the command line parameters aren't being received by postCouchPotato.py for some reason. I don't have a synology to test on but I know on windows sometimes there's issues with python and command line parameters not being recognized by Python, but I'll to do some investigating to see if that's a problem on synology

Also what movie are you trying to process there? Looks like the file is named "Movie.mkv". I'm just wondering if that's modified or you were processing some unidentified movie in CouchPotato.

Thanks for looking into it - I modified the filename.  :)

Shouldn't make a difference honestly I was just curious. If you run a python script with command line variables does that normally work? Like if you run manual.py with command line parameters does it acknowledge those?
On Wed, Nov 4, 2015 at 7:57 AM, M4X-StL<EMAIL_ADDRESS>wrote:

Thanks for looking into it - I modified the filename.  :)
Reply to this email directly or view it on GitHub:
https://github.com/mdhiggins/sickbeard_mp4_automator/issues/359#issuecomment-153713063

Admittably, I haven't attempted to run the process manually.  However, I was forcing post-processing in CP - but I believe that also shouldn't matter.  I will report back this afternoon/evening on any further progress, as I'm unable to further troubleshoot right now.

What do you mean forcing post-processing in CP?

Restarting CP to allow for the post-processing/execution of your script.

Wasn't aware that would trigger post-processing. As far as I know the only trigger should be when a renamer.scan is run but I guess it may depend on how CP is setup, if you're using the blackhole method maybe? I only ask cause I'm wondering if that maybe has something to do with why its not working.

Appreciate the back-and-forth - so I triggered a download via NZBGet and push to CP earlier this AM - but didn't get a chance to see if it completed the process before work.  I'll certainly report back w/my findings late this afternoon/evening.  And yes, if you've already downloaded via CP, you can throw the file back into its original downloaded directory and restart/reload CP and it will trigger any post-processing scripts are setup in the custom_scripts folder.

Investigated the logs again - same issue.  Do you think my Python build is potentially corrupt (grasping at straws here...)?  Permissions are set to 0777 for both the root folder (and sub-folders) of the main script location - in addition to the PostProcess folder in custom_scripts.

I don't think its a permissions issue since both scripts appear to be executing themselves as they should. For whatever reason, the command line parameters that should be getting passed from the main.py file to the postCouchPotato.py file aren't being seen. That being said I'm not sure why that would be.
A couple things you could try:

see if command line parameters work with manual.py and let me know
in main.py try setting shell=True on line 41 (and make sure you shutdown CP, delete any .pyc files, and relaunch CP after you've made the changes) and try again

mdhiggins - appreciate your continued engagement on this issue.  I will attempt to run manual.py this evening in addition to your recommended changes to main.py (although I think I tried that as well while burning the midnight oil last night).  Talk soon.

You could also try removing the env={} from line 41 as well and see if that makes any difference

Sooo... progress, but now encountering a new issue mdhiggins.  :(
11-04 19:03:54 INFO
[ PostProcess] Executing post processing on file /volume1/DiskStation/Movies/Insurgent.2015.1080p.BluRay.x264/pMHMRx8ALFURMyAeFYsgg.mkv
11-04 19:03:55 INFO
[ PostProcess]
11-04 19:03:55 INFO
[ PostProcess] Traceback (most recent call last): File "/usr/local/couchpotatoserver/scripts/sickbeard_mp4_automator/postCouchPotato.py", line 6, in  from readSettings import ReadSettings File<EMAIL_ADDRESS>line 11, in  from babelfish import Language ImportError: No module named babelfish
11-04 19:03:55 INFO
[ PostProcess] Return code: 1
I changed made the recommended changes to line 41 - shell=True & removed env={}.  Additionally, I installed babelfish last night to get the script working again w/Sickrage, by evidence below:
Server> pip install babelfish
Requirement already satisfied (use --upgrade to upgrade): babelfish in /lib/python2.7/site-packages
Cleaning up...
Server> pip install babelfish --upgrade
Requirement already up-to-date: babelfish in /lib/python2.7/site-packages
Cleaning up...
Server>
I'm up for ideas at this point!  Be back in approximately an hour.  :+1:

Alright so that new error is coming from deleting the env={} part of the script. I would put that back and try it with just Shell=True and see where that gets you.
On Wed, Nov 4, 2015 at 8:08 PM, M4X-StL<EMAIL_ADDRESS>wrote:

Sooo... progress, but now encountering a new issue mdhiggins.  :(
11-04 19:03:54 INFO
[ PostProcess] Executing post processing on file /volume1/DiskStation/Movies/Insurgent.2015.1080p.BluRay.x264/pMHMRx8ALFURMyAeFYsgg.mkv
11-04 19:03:55 INFO
[ PostProcess]
11-04 19:03:55 INFO
[ PostProcess] Traceback (most recent call last): File "/usr/local/couchpotatoserver/scripts/sickbeard_mp4_automator/postCouchPotato.py", line 6, in  from readSettings import ReadSettings File<EMAIL_ADDRESS>line 11, in  from babelfish import Language ImportError: No module named babelfish
11-04 19:03:55 INFO
[ PostProcess] Return code: 1
I changed made the recommended changes to line 41 - shell=True & removed env={}.  Additionally, I installed babelfish last night to get the script working again w/Sickrage, by evidence below:
Server> pip install babelfish
Requirement already satisfied (use --upgrade to upgrade): babelfish in /lib/python2.7/site-packages
Cleaning up...
Server> pip install babelfish --upgrade
Requirement already up-to-date: babelfish in /lib/python2.7/site-packages
Cleaning up...
Server>
I'm up for ideas at this point!  Be back in approximately an hour.  :+1:
Reply to this email directly or view it on GitHub:
https://github.com/mdhiggins/sickbeard_mp4_automator/issues/359#issuecomment-153920797

Back to where we were...
11-04 19:45:57 INFO
[ PostProcess] Executing post processing on file /volume1/DiskStation/Movies/Movie.mkv
11-04 19:45:57 INFO
[ PostProcess] 2015-11-04 19:45:57 - CouchPotatoPostConversion - INFO - MP4 Automator - Post processing script initialized 2015-11-04 19:45:57 - readSettings - WARNING - Audio bitrate was invalid, defaulting to 256 per channel.
11-04 19:45:57 INFO
[ PostProcess] Traceback (most recent call last): File "/usr/local/couchpotatoserver/scripts/sickbeard_mp4_automator/postCouchPotato.py", line 21, in  imdbid = sys.argv[1] IndexError: list index out of range
11-04 19:45:57 INFO
[ PostProcess] Return code: 1
I need about another 20 mins then I can try the manual.py method.

Manual.py worked fine - still getting the same error.  :-1:

Did you specifically try to pass it command line variables? I suspect it will launch but I’m just wondering if it will obey command line parameters.
On Wed, Nov 4, 2015 at 9:25 PM, M4X-StL<EMAIL_ADDRESS>wrote:

Manual.py worked fine - still getting the same error.  :-1:
Reply to this email directly or view it on GitHub:
https://github.com/mdhiggins/sickbeard_mp4_automator/issues/359#issuecomment-153933559


Added new 'Simple searchable' template

Hi,
I added a new template named 'simple-searchable'. Has some different styles and a simple js search field for navigation contents. Reran tests to generate sample docs...

Instead of creating a third template, can this be integrated into the angular-template?

I thought the point was to offer people more choice! Styling changes are a personal preference, didn't want to make any assumptions...

I guess the final decision is made by the person that merges the pull request. But having three templates, let alone two is going to cause unbelievable head ache when it comes to making feature or bug fixes to the templates.

Looks nice. I like the filter as well.
What do you think about putting the navigation on the right side? I see a couple of advantages for having it on the right side. It wouldn’t require so much space. It could just be on the right side and have an infinite width. It wouldn’t ever need to wrap any Angular component name and it doesn’t take as much space.
I agree with @reloaded. A single template that we focus on is probably more efficient.

As a matter of fact the default template doesn’t even work for me. This is a blocker for other PRs and issues right now, so we should quickly find an agreement here.
//cc @allenhwkim

@Zemke Actually, in my Angular project my module names are namespaced using the period separator and right now the navigation headers are line wrapping.
I prefer the navigation headers to be 15px instead of 30px and I prefer the navigation to be on the left side. I've never seen a navigation on the right side before, it feels like I'm reading documentation in RTL format. :)

I agree with @Zemke
I prefer the navigation on the right side, and it has its advantage
If it goes to the left side, I believe that the template must be responsive, RWD, which isn't now.
Reference aboout right-side vs left-side navigation.
http://ux.stackexchange.com/questions/31031/how-to-choose-the-better-placement-for-sidebar-left-or-right
https://www.quora.com/How-do-UI-designers-decide-when-to-put-the-navigation-menu-on-the-right-Twitter-Quora-vs-the-left-Google-Reader-Facebook
I will leave to @Zemke to remove default template or not.
For the maintenance sake, I want to keep one template only and I prefer angular-template, angular-like-template actually.
Thank you so much @reloaded and @Zemke to make this improved.

We have three templates: default, angular-template and simple-searchable.
@allenhwkim, what do you mean with “angular-like”?
I’d remove default as it doesn’t work and it’s also many features behind the other two. Between the other two I’d pick simple-searchable because it has a clean look and the filter is a nice feature. But I’d definitely want the nav tone on the right.
So, what are your votes?

Not a big issue to put the navigation left or right...I can do that. Didn't bother to make the template responsive, because I didn't see too much of a use case for it, but I guess some support could be added for different screen sizes. Let me know if we want this, and I'll make the changes! Personally I much prefer the cleaner look, which is why I changed the styling.

@Zemkeangular-like means the template I made is html template not the exact angular template. e.g. ht-repeat, not ng-repeat.
I would leave @Zemke to pick one template and abandon others for easy maintenance.
about menu, I prefer right-side navigation

Ah okay. I’m also a fan of angular-template. 😉
Fine, simple-searchable is built using angular-template. So, let’s pick this, but with nav on the right side.
@zxuwen, would you mind updating your PR with the nav on the right side? We’d then love to use it as the sole template of allenhwkim/angular-jsdoc.
Once this is merged, I’d love @reloaded to update his open PRs to apply to the simple-searchable template and then we can have a new nice release. 👍

Ok! Will do, over the weekend.

Hi, made a new pull request here:
https://github.com/allenhwkim/angular-jsdoc/pull/82
In the new PR, angular-template has been completely replaced and simple-searchable removed. Please take a look.
Updated to have navbar on the right, removed the scrollable div within the navigation (to prevent double scrollable when both nav and contents overflow).


Entity interaction events API

Set up a file structure for the quilt equivalent of the FAPI events interaction module.

I'm marking this as a draft--feel free to mark it as ready to review when you have the code ready!


Upgrade doesn't upgrade all architectures

Please confirm these before moving forward

[X] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
[X] I have not been informed if the issue is resolved in a preview version of the winget client.

Category of the issue
Installation issue.
Brief description of your issue
When I execute "winget upgrade --all" it doesn't download the x86 version of the Microsoft.DotNet.DesktopRuntime.6 package which is installed side-by-side on x64-based installations.
Steps to reproduce
Execute "winget upgrade --all".
Actual behavior
It downloads the x64 version when it should be downloading the x86 version since both need to be updated.
Expected behavior
It should be downloading both the x86 and the x64 versions.
Environment
Windows Package Manager (Preview) v1.3.1391-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22000.739
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.18.1391.0

Logs: %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Screenshots and Logs
No response

@trparky
As a workaround you can specify the "--architecture" to get the x86 variations

The same feature need to be added to winget uninstall command. For example, I can not uninstall Oracle.JavaRuntimeEnvironment because I have both x86 and x64 versions.

Simple repro that shows that winget upgrade with --architecture does not work either, originally posted to #4810.
PS > winget install --silent --id Microsoft.DotNet.DesktopRuntime.6 --version 6.0.31 --architecture x64
Installs successfully.

PS > winget install --silent --id Microsoft.DotNet.DesktopRuntime.6 --version 6.0.33 --architecture x86
Installs successfully.

Now try to either upgrade or uninstall just x64.


Microsoft.UI.Xaml.dll calls an unsupported API

Submitted my app using Windows UI Library for certification. But certification failed saying that "API CoIncrementMTAUsage in ole32.dll is not supported for this application type. Microsoft.UI.Xaml.dll calls this API". Is there anything I missed? I saw the doc says the library is ready for store submission.

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

ID: 4a36d9da-7510-64b5-f937-cc3d9f0c2325
Version Independent ID: 43badf5d-f042-1bad-6e50-7a42100dbada
Content: Windows UI library - UWP app developer
Content Source: winrt-related-src/toolkits/winui/index.md
Product: windows
GitHub Login: @mijacobs
Microsoft Alias: mijacobs

Hi @DL444,
Thank you for letting us know about this issue--our development team is working on a fix.

@DL444, Thanks for reporting the issue. We've fixed this problem and published an updated package: 2.0.180724003-prerelease. If you pick up the new version you should no longer see this error.


Tillerless RBAC

Hi
I am using Tiller in production now for our internal webservices, but I want to move to a tillerless infra, as recommended now in the doc, and rely on our RBAC infra.
The goal is to execute tiller locally from our Gitlab CI runner, and use kube config to connect to the API. This would mimick as best as possible the future behavior with helm v3.
Would like to know if this is something you would like to advocate to prepare to helm v3.
The RBAC part is not met with my solution, but at least we can use a token stored in a private variable in the project to identy the caller.
Here is what I have:

CI provides the following information: authentication authority ca.pem, service account token as $TILLER_TOKEN.
export KUBECONFIG=${KUBECONFIG:-/etc/deploy/config}
ca.pem is created inside /etc/deploy/ca.pem, and the config is set with:

kubectl config set-cluster     sa-cluster --server=$CLUSTER_URL --certificate-authority=/etc/deploy/ca.pem
kubectl config set-credentials sa-user    --token=${TILLER_TOKEN}
kubectl config set-context     sa-context --user=sa-user --cluster sa-cluster --namespace ${TARGET_NAMESPACE}
kubectl config use-context     sa-context

Tiller is run locally:

export HELM_HOST=localhost:44134
tiller --storage=secret --history-max 20 --logtostderr &

one could use tillerless plugin if wanted
helm is then initialized in client only mode:

helm init \
      --client-only \
      --debug \
      --history-max 20 \
      --stable-repo-url http://ourinternal.chart/repository

helm repo update

helm dep build Chart/

helm upgrade \
      --install \
      --force \
      ... \
     myappname \
      Chart/

Seems pretty cool, do not require to generate self-authenticated certificates, and rely on the service account token like the good old tiller-helm. For me this look like the same among of security, no more, no less, but less complex to setup.
Do you think this might help for preparing migration to helm 3?

hey there, we at Jfrog use local tiller for all our kubernetes clusters deployments and happy with the results we have.
If you really want to prep for helm v3 you could set tiller namespace to the same as your app gets released, that will mimic v3 setup, but that needs redeployment of your app.

yes that's what we do :)

so you all good there then :)

Hi, @gsemet - it sounds like you were well on the path to a successful Helm 3 upgrade. Please take a look at https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/ and let us know if you have further need of support. Thanks!


Short README

@naggingant very short usage and install sample

Thanks!
Let me make a few more changes myself (like the masking functionality is within format() in fact)
This one might have a chance to be published to NPM registry


please reduce the log level of rate limit warnings

currently, the AsyncRateLimitExecutor logs an error whenever a response is rate limited.  however, rate limiting is not terminal, as the request will be retried after the delay.  as such, the situation warrants at most a warning.  we have various systems which track error messages and the rate limit messages can be quite noisy (and are not something we usually need to act on).  we don't want to completely disable error messages from the slack sdk as there are others that are more important (actual failures).  it would be ideal if the rate limit logging were reduced to at least a warning message.
Category (place an x in each of the [ ])

[ ] bolt (Bolt for Java)
[ ] bolt-{sub modules} (Bolt for Java - optional modules)
[x] slack-api-client (Slack API Clients)
[ ] slack-api-model (Slack API Data Models)
[ ] slack-api-*-kotlin-extension (Kotlin Extensions for Slack API Clients)
[ ] slack-app-backend (The primitive layer of Bolt for Java)

Requirements
Please make sure if this topic is specific to this SDK. For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. :bow:
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to the those rules.

Hi @jahlbornG, thanks for taking the time to share this feedback!
Are you mentioning the error log here? https://github.com/slackapi/java-slack-sdk/blob/v1.20.0/slack-api-client/src/main/java/com/slack/api/methods/impl/AsyncRateLimitExecutor.java#L190-L197

Got a rate-limited response from {} API (team: {}, error: {}, retry-after: {})

If so, changing the log level from ERROR to WARNING would be fine.
INFO level does not sound reasonable to me. Receiving 429 HTTP status in async clients is not a normal situation. As long as you use the smart rate limiter in the async API client with proper settings, the situation cannot easily happen.
What do you think?

yep, that's the line i am referring to, and yes, warning seems perfectly reasonable to me.

awesome, thanks!


Error with dapr init

In what area(s)?

/area runtime

/area operator
/area placement
/area docs
/area test-and-release

What version of Dapr?

1.1.x

1.0.x
edge: output of git describe --dirty

Expected Behavior

Fresh new install on a Mac OS Big Sur (Intel cpu) with docker desktop installed.
Versions:
MacOS: Big Sur 11.3.1
Docker Desktop: 3.3.3 (engine 20.10.6)
Dapr cli: 1.1.0
Dapr runtime: 1.1.2
Right after the command "dapr init"
dapr init
⌛  Making the jump to hyperspace...
→  Downloading binaries and setting up components...
Dapr runtime installed to /Users/c0h1b4/.dapr/bin, you may run the following to add it to your path if you want to run daprd directly:
export PATH=$PATH:/Users/c0h1b4/.dapr/bin
❌  Downloading binaries and setting up components...
❌  Unable to find image 'daprio/dapr:latest' locally
docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.
Actual Behavior
I can't init a new project
Steps to Reproduce the Problem
dapr init
Release Note

RELEASE NOTE:

Can you manually run docker pull daprio/dapr:latest ?

@c0h1b4 I am seeing the error is from docker, could you try restarting Docker and see if that works as well as trying to pull the latest dapr container manually as shown in the above comment.

As an aside - @c0h1b4 - @mukundansundar and I cannot reproduce this on issue on Intel Mac with 11.2.3 and 11.3.1 respectively. I installed the latest stable version of Docker for Mac. I also cannot reproduce this on M1 ARM with 11.3.1 and latest Docker for ARM Mac.
As @mukundansundar says, this seems very specific to your installation or configuration of Docker.

@c0h1b4 I am seeing the error is from docker, could you try restarting Docker and see if that works as well as trying to pull the latest dapr container manually as shown in the above comment.

@mukundansundar I restarted the whole computer and I still have the same issue.
@berndverst
I tried the docker pull daprio/dapr:latest and got this error:
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
I can confirm that my computer and docker is downloading all other images since I didn't had the redis image and now it is downloaded and running as 'dapr_redis' after the command dapr init

I think I found the issue. It is a problem with the company proxy.
Thanks everyone for the help.


Plugin builds can now be made go-gettable with v1 and go modules \o/

Thanks for all the effort going into v1 and the final switch to go modules.
This brings a nice feature of cleaner code and making plugin builds go-gettable:
github.com/txtdirect/txtdirect <-- plugin code with setup.go files
github.com/txtdirect/txtdirect/cmd/txtdirect <-- package code as seen below:
package main

import (
	"github.com/mholt/caddy/caddy/caddymain"

	_ "github.com/txtdirect/txtdirect"
)

func main() {
	caddymain.EnableTelemetry = false
	caddymain.Run()
}

This makes it easily importable as a plugin import github.com/txtdirect/txtdirect, but also go-gettable with the correct caddy version etc. GO111MODULE=on go get github.com/txtdirect/txtdirect@master.

Bonus point of your own custom go-gettable caddy version:
package main

import (
	"github.com/mholt/caddy/caddy/caddymain"

	_ "github.com/SchumacherFM/mailout"
	_ "github.com/captncraig/caddy-realip"
	_ "github.com/miekg/caddy-prometheus"
	_ "github.com/txtdirect/txtdirect"
)

func main() {
	caddymain.EnableTelemetry = false
	caddymain.Run()
}

Now you can go get that main package and get your custom Caddy build including the imported plugins.
Sidenote: For commercial use don't hesitate to get a subscription for Caddy https://caddyserver.com/products/licenses to make it sustainable :wink:

Indeed! I'm glad you pointed this out. We updated our build instructions a few days ago to suggest that very workflow: https://github.com/mholt/caddy#build
Will probably stay this way for Caddy 2 as well.


Error when building with Snowboy

Overview -
I have the Alexa SDK 1.2 version working(with Snowboy) on a Pi 3 running Stretch.
Since there's now an updated 1.3 version, I repeated the same steps I used for 1.2 but I ran into this error when I tried to build it.
I compiled with the default cmake then when that didn't work also tried CC=gcc-4.9 CXX=g++-4.9 cmake but had the same issue.
OS and build - Raspbian Stretch - Alexa SDK 1.3
Logs - Happens at 72%
[ 71%] Building CXX object MediaPlayer/src/CMakeFiles/MediaPlayer.dir/MediaPlayer.cpp.o
In file included from /usr/include/c++/6/vector:64:0,
                 from /home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/ThirdParty/googletest-release-1.8.0/googletest/include/gtest/internal/gtest-port.h:279,
                 from /home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/ThirdParty/googletest-release-1.8.0/googletest/include/gtest/internal/gtest-linked_ptr.h:74,
                 from /home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/ThirdParty/googletest-release-1.8.0/googlemock/include/gmock/internal/gmock-port.h:53,
                 from /home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/ThirdParty/googletest-release-1.8.0/googlemock/include/gmock/internal/gmock-generated-internal-utils.h:44,
                 from /home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/ThirdParty/googletest-release-1.8.0/googlemock/include/gmock/internal/gmock-internal-utils.h:45,
                 from /home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/ThirdParty/googletest-release-1.8.0/googlemock/include/gmock/gmock-actions.h:46,
                 from /home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/ThirdParty/googletest-release-1.8.0/googlemock/include/gmock/gmock.h:58,
                 from /home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/PlaylistParser/test/PlaylistParserTest.cpp:25:
/usr/include/c++/6/bits/stl_vector.h: In constructor ‘std::vector<_Tp, _Alloc>::vector(std::initializer_list<_Tp>, const allocator_type&) [with _Tp = std::chrono::duration<long long int, std::ratio<1ll, 1000ll> >; _Alloc = std::allocator<std::chrono::duration<long long int, std::ratio<1ll, 1000ll> > >]’:
/usr/include/c++/6/bits/stl_vector.h:375:7: note: parameter passing for argument of type ‘std::initializer_list<std::chrono::duration<long long int, std::ratio<1ll, 1000ll> > >’ will change in GCC 7.1
       vector(initializer_list<value_type> __l,
       ^~~~~~
/home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/PlaylistParser/test/PlaylistParserTest.cpp: In function ‘void __static_initialization_and_destruction_0(int, int)’:
/home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/PlaylistParser/test/PlaylistParserTest.cpp:52:53: note: parameter passing for argument of type ‘std::initializer_list<std::chrono::duration<long long int, std::ratio<1ll, 1000ll> > >’ will change in GCC 7.1
 static const std::vector<std::chrono::milliseconds> TEST_M3U_DURATIONS = {std::chrono::milliseconds{-1},
                                                     ^~~~~~~~~~~~~~~~~~
/home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/PlaylistParser/test/PlaylistParserTest.cpp:129:53: note: parameter passing for argument of type ‘std::initializer_list<std::chrono::duration<long long int, std::ratio<1ll, 1000ll> > >’ will change in GCC 7.1
 static const std::vector<std::chrono::milliseconds> TEST_HLS_DURATIONS = {std::chrono::milliseconds{10000},
                                                     ^~~~~~~~~~~~~~~~~~
/home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/PlaylistParser/test/PlaylistParserTest.cpp:222:53: note: parameter passing for argument of type ‘std::initializer_list<std::chrono::duration<long long int, std::ratio<1ll, 1000ll> > >’ will change in GCC 7.1
 static const std::vector<std::chrono::milliseconds> TEST_HLS_LIVE_STREAM_DURATIONS = {std::chrono::milliseconds{10000},
                                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ 71%] Linking CXX executable PlaylistParserTest
[ 71%] Built target PlaylistParserTest
Scanning dependencies of target KITTAI
[ 72%] Building CXX object KWD/KittAi/src/CMakeFiles/KITTAI.dir/KittAiKeyWordDetector.cpp.o
/home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/KWD/KittAi/src/KittAiKeyWordDetector.cpp: In constructor ‘alexaClientSDK::kwd::KittAiKeyWordDetector::KittAiKeyWordDetector(std::shared_ptr<alexaClientSDK::avsCommon::utils::sds::SharedDataStream<alexaClientSDK::avsCommon::utils::sds::InProcessSDSTraits> >, alexaClientSDK::avsCommon::utils::AudioFormat, std::unordered_set<std::shared_ptr<alexaClientSDK::avsCommon::sdkInterfaces::KeyWordObserverInterface> >, std::unordered_set<std::shared_ptr<alexaClientSDK::avsCommon::sdkInterfaces::KeyWordDetectorStateObserverInterface> >, const string&, std::vector<alexaClientSDK::kwd::KittAiKeyWordDetector::KittAiConfiguration>, float, bool, std::chrono::milliseconds)’:
/home/drpi1/AlexaSDK1.3/sdk-folder/sdk-source/avs-device-sdk/KWD/KittAi/src/KittAiKeyWordDetector.cpp:123:78: error: narrowing conversion of ‘(((std::chrono::duration<long long int, std::ratio<1ll, 1000ll> >::rep)(audioFormat.alexaClientSDK::avsCommon::utils::AudioFormat::sampleRateHz / 1000u)) * msToPushPerIteration.std::chrono::duration<_Rep, _Period>::count<long long int, std::ratio<1ll, 1000ll> >())’ from ‘std::chrono::duration<long long int, std::ratio<1ll, 1000ll> >::rep {aka long long int}’ to ‘size_t {aka unsigned int}’ inside { } [-Werror=narrowing]
         m_maxSamplesPerPush{(audioFormat.sampleRateHz / HERTZ_PER_KILOHERTZ) * msToPushPerIteration.count()} {
                             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[ 72%] Building CXX object MediaPlayer/src/CMakeFiles/MediaPlayer.dir/Normalizer.cpp.o
[ 73%] Linking CXX executable AbstractKeywordDetectorTest
[ 73%] Built target AbstractKeywordDetectorTest
Scanning dependencies of target AudioInputProcessorTest
[ 73%] Building CXX object CapabilityAgents/AIP/test/CMakeFiles/AudioInputProcessorTest.dir/AudioInputProcessorTest.cpp.o
cc1plus: all warnings being treated as errors
KWD/KittAi/src/CMakeFiles/KITTAI.dir/build.make:62: recipe for target 'KWD/KittAi/src/CMakeFiles/KITTAI.dir/KittAiKeyWordDetector.cpp.o' failed
make[2]: *** [KWD/KittAi/src/CMakeFiles/KITTAI.dir/KittAiKeyWordDetector.cpp.o] Error 1
CMakeFiles/Makefile2:4475: recipe for target 'KWD/KittAi/src/CMakeFiles/KITTAI.dir/all' failed
make[1]: *** [KWD/KittAi/src/CMakeFiles/KITTAI.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 74%] Building CXX object MediaPlayer/src/CMakeFiles/MediaPlayer.dir/OffsetManager.cpp.o
[ 74%] Building CXX object MediaPlayer/src/CMakeFiles/MediaPlayer.dir/UrlSource.cpp.o
[ 74%] Linking CXX shared library libMediaPlayer.so
[ 74%] Built target MediaPlayer
[ 75%] Linking CXX executable AudioInputProcessorTest
[ 75%] Built target AudioInputProcessorTest
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2

It doesn't seem to be a snowboy issue.
https://github.com/Kitt-AI/snowboy/issues/326

Hi @D3rpi,
It looks like the issue with the following line:
 m_maxSamplesPerPush{(audioFormat.sampleRateHz / HERTZ_PER_KILOHERTZ) * msToPushPerIteration.count()}
For now, could you try modifying that to:
 m_maxSamplesPerPush{(audioFormat.sampleRateHz / HERTZ_PER_KILOHERTZ) * static_cast<unsigned int>(msToPushPerIteration.count())}
?
Thanks,
Sanjay

@sanjayrd Thanks, that worked!
:)


Replace observers for spawning entities with an EntityCommand-based abstraction

An example of how the proposed API looks in practice: https://github.com/benfrankel/bevy_jam_template/blob/main/src/screen/title.rs.
Benefits:

You get an EntityCommands back immediately.
You can access SystemParams ergonomically by adding them as arguments.
You can pass in extra data (e.g. struct Projectile { lifetime, .. }).
Converting a "pure" entity spawning system to one that takes in extra data is relatively easy:

Define your data type, like struct Projectile.
Implement EntityCommand for Projectile, and delegate to the spawning system with world.run_system_once_with((id, self), projectile).
Change In(id): In<Entity> to In((id, this)): In<(Entity, Projectile)>.

Drawbacks:

Requires extension traits.
Unfamiliar approach (using observers to spawn things is unfamiliar as well).
spawn_fn and spawn_with unfortunately couldn't be merged into one method.
A few lines of boilerplate to take in data. This could use a VS Code snippet to make it easier.

I'm in favor.
Note that we went through many designs and this seems the cleanest by far imo. Bevy does not have the required answer to "How do I spawn an object composed of lots of stuff?" yet while still returning an EntityCommands, so we need to introduce an abstraction here.

I'm also in favour of this.

Blocked on upstreaming https://github.com/bevyengine/bevy/issues/14278 and maybe https://github.com/bevyengine/bevy/issues/14231


consider closures to store precalculated data

https://github.com/lumicks/py-optics/tree/robert/context-manager

https://github.com/lumicks/py-optics/pull/23


Add FileSizeTester method

good PL. but please keep below rules.

use Wandu\Validator\Contracts\Tester interface
keep PHPDoc(https://www.phpdoc.org/)
remove endline comments (/* End of file FileSizeTester.php */ ... )

:-)

whoops, i missed one more.

public function test($data, $origin = null, array $keys = []): bool

test method parameters are wrong.

Is mybad. I'm gonna ask you to rewrite it.


vendor: reactivate bitbucket tests

Fixes #452
Because of reasons bitbucket.org is not in the ssh known hosts' file in tavis.yml. This leaves two questions

why does it appear to be in the ssh hosts' file on the other CI providers
why, even though we assign /dev/null to Stdin, does mercurial still prompt for an answer

Having no good answer for both, try to work around the problem by pre-populating the known hosts file during setup.

Hahaha, this is pretty similar to the workaround I was contemplating.  Dirty indeed, but super effective. :+1:

@tianon when in doubt, sell out.

there is also http://docs.travis-ci.com/user/ssh-known-hosts/ :)


openshift: IsOpenShift and IsKubernetes

Under parts/k8s we appear to be using IsOpenShift and !IsKubernetes (and vice-versa) interchangeably.  Surely that doesn't make sense?  Can we decide on one and use it?  My leaning is that OpenShift customisations/modifications of parts/k8s should be flagged by IsOpenShift rather than !IsKubernetes?

Agreed, let's stick with IsOpenShift


rename MF terms for topoisomerase type I & II activity terms

The two relevant topoisomerase MF terms are currently named like this:

DNA topoisomerase type I activity (GO:0003917)
DNA topoisomerase type II (ATP-hydrolyzing) activity  (GO:0003918)

As described in https://github.com/geneontology/go-ontology/issues/15575, these names have actively promoted confusion, leading in part to the creation of one redundant and one completely spurious topoisomerase II activity term.  (I plan to merge one and obsolete the other as detailed here: https://github.com/geneontology/go-ontology/issues/17661).
They also clarity with respect to the distinguishing features of the two major classes of topoisomerases:

topoisomerase type I (single strand cut, ATP-independent)
topoisomerase type II (double strand cut, ATP-hydrolyzing)

However, considering the potential confusion between the two major classes (topoisomerase type I & topoisomerase type II) and specific enzymes (topoisomerase I, topoisomerase II, topoisomerase III, topoisomerase IV, etc.), I am inclined to add info to the two type terms rather than remove it.
One additional consideration is the fact that the type I topo enzymes can also have RNA topoisomerase activity ("RNA topoisomerase activity is prevalent in Type IA topoisomerases from bacteria, archaea, and eukarya" - Ahmad et al. 2016, PMID:27257063), it might be best to remove "DNA" from the term names.
Thus, I proposed to rename these terms like this:

topoisomerase type I (single strand cut, ATP-independent) activity [GO:0003917]
topoisomerase type II (double strand cut, ATP-hydrolyzing) activity [GO:0003918]

@bmeldal - Does this seem reasonable to you?

Actually, considering that there is an MF term for "RNA topoisomerase activity", these MF terms can just keep specificity for DNA.
I still think it's better to add the info that distinguishes the two major classes of topo enzymes, e.g. # strands cut and ATP utilization since it helps distinguish from the more specific individual enzyme names. Also, since we have a term named "DNA topoisomerase II" that I plan to obsolete, it avoids any issues with name versus ID conflicts.
So with this in mind, I modify my proposed new term names to these:

DNA topoisomerase type I (single strand cut, ATP-independent) activity [GO:0003917]
DNA topoisomerase type II (double strand cut, ATP-hydrolyzing) activity [GO:0003918]

Yup, sounds like a good solution - for now ;-)


Refactor all plugin contract to utilize PluginsCore.sol

I refactored our plugins architecture a little bit to inherit abstract contracts as opposed to importing libraries. This allows the abstraction of much more duplicate code and makes it much more readable to see what the child-most contract is doing.

/cib


Mouse pointer doesn't change to finger icon over hamburger menu.

Steps to reproduce:

Launch https://hub.safedev.org/
Resize browser window so top nav bar collapses to a hamburger menu:

Hover mouse over hamburger icon.

Expected:
Mouse pointer changes to finger icon (as it does hovering over links).
Actual:
Mouse pointed does not change:

Found on Firefox, reproduced on Chrome.


Revert: listener: remove the peek from the listener filters

Signed-off-by: Kuat Yessenov<EMAIL_ADDRESS>Commit Message: reverts https://github.com/envoyproxy/envoy/pull/17395 since due to breakage in HTTP inspector.
Risk Level: low
Testing:
Docs Changes:
Release Notes:

If the revert requires further fixes, it may be better to just fix in-place. It was a huge change, and it wouldn't surprise me if there are a few conflicts.

Probably needs another main merge.
/wait

Looks like it's just the config merge race.


release to nuget

Release it as nuget package. (Even as prerelease)

My guess for why this hasn't happend is because it isn't really something you can put in a nuget.
This is more like a different Project type.
If you have an idea how to solve this a PR is probably appreciated.


style: add css override

We're going to have to more aggressively reset CSS at a component level given Tina's UI is no longer isolated. Using all: unset; will reset everything for us, but it may nuke defaults we were previously relying on so it can't simply be applied universally.
This is just a start, I will continue to apply this reset (and compensate for the missing defaults after it's applied) as issues come up.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Feat/action selector

Depends on https://github.com/appsmithorg/design-system/pull/306
Description

Please include a summary of the changes and which issue has been fixed. Please also include relevant motivation
and context. List any dependencies that are required for this change
Links to Notion, Figma or any other documents that might be relevant to the PR

Add a TL;DR when description is extra long (helps content team)

Fixes # (issue)

if no issue exists, please create an issue and ask the maintainers about this first

Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Chore (housekeeping or task changes that don't impact user perception)
This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.
Delete anything that is not important

Manual
Jest
Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] 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
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/build-deploy-preview env=release

/ok-to-test sha=f1c6f10

/build-deploy-preview env=release

/ok-to-test sha=60e3769

/ok-to-test sha=33dc077

/ok-to-test sha=be1edcf

/ok-to-test sha=5d70684

/build-deploy-preview env=release

/build-deploy-preview env=release

/ok-to-test sha=623858a

/ok-to-test sha=560e154

/build-deploy-preview env=release

/ok-to-test sha=460da0c

/ok-to-test sha=bde45ae

/ok-to-test sha=38cdb57

/ok-to-test sha=7929717

/ok-to-test sha=5c96327

/ok-to-test sha=1a2dd55

/ok-to-test sha=3b8de3f

/ok-to-test sha=3a8d47b

/ok-to-test sha=af0f8d0

/ok-to-test sha=af0f8d0

/ok-to-test sha=afe189b

/build-deploy-preview

/ok-to-test sha=f8a31cb

/ok-to-test sha=5704c99

/ok-to-test sha=7818d3c

/ok-to-test sha=dac49f3

/ok-to-test sha=f9c7101

/ok-to-test sha=640438c

/build-deploy-preview env=release

/build-deploy-preview

/ok-to-test sha=7ed2c64

/ok-to-test sha=ab9cad2

/build-deploy-preview env=release

/ok-to-test sha=5e3a2d0

/ok-to-test sha=dfbcf15

/ok-to-test sha=9b10f54

/ok-to-test sha=9b10f54

/ok-to-test sha=6259d50

/ok-to-test sha=6b33d76

Re-approving the PR. ( Prev approval was lost due to conflict resolution with release branch )


Supported cloud mode and device mode events for Shopify source

Description of the change

Updated content.

Type of change

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

Related issues

Fix #1

Checklists
Development

[ ] Lint rules pass locally
[ ] The code changed/added as part of this pull request has been covered with tests
[ ] All tests related to the changed code pass in development

Code review

[ ]  This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
[ ] "Ready for review" label attached to the PR and reviewers mentioned in a comment
[ ] Changes have been reviewed by at least one other engineer
[ ] Issue from task tracker has a link to this pull request

We should add the following in the FAQ

What happens when my app is behaving unexpectedly and no event is flowing? (reinstall app)
How to track events from multiple stores? (use multiple sources) - this is an obvious one but still
@arajguha @yashasvibajpai you guys could add some to FAQ list

@utsabc For multiple stores, we can use the same source also, we just need the app installed and properly configured in each of the stores.
Should we put this question in FAQ?

@utsabc For multiple stores, we can use the same source also, we just need the app installed and properly configured in each of the stores. Should we put this question in FAQ?

Yes we can

LGTM


✨ Readonly strategy

Summary
Related issue(s)
Fixes #

/assign @clyang82 @elgnay

I am good with this fix. Thanks
Leave it to @elgnay PTAL

/lgtm


Update socket.io to 1.4.5 and use client library provided by the dependancy

Fixes #112, removes socket.io client library from the repository

:+1:

Looks good to me, :+1:. I don't know what could go wrong updating that. In theory, if it connects it pretty much works right? The branch is conflicting right now, I'll let you update and merge.

Rebased and merging.


Re-arrange sigstore docs so that they are more clear to readers

Description

The current arrangement of sigstore doc is somewhat haphazard and does not lend itself to easy understanding.  I'm proposing a new organization of the material so it flows better with user journeys.
The proposal is written up here:
https://docs.google.com/document/d/1NFxvtQu-tZ07D3aXXslQpYGhaztl6RDPw7L5HPc4-2Y/edit?usp=sharing
This issue is related to https://github.com/sigstore/docs/issues/187#issuecomment-1590055593
@haydentherapper @ltagliaferri @olivekl
This issue will be fixed with multiple pull requests:
Rearrange existing files to be in the order that is specified in the outline on a group by group level.

About sigtore
Signing (was part of cosign)
Verifying (was part of cosign)
Key management (was part of cosign)
Command line interface (new)
Certificate authority  (was fulcio)
Transparency log (was rekor)
Kubernetes policy controller

Edit files so that content matches new headers:
Move all verify information to verify sections.

One question that came up is what exactly do we want developer users to do with the software?   What information do we want to provide to people to help with the developer journey.

Thanks for this, @jonvnadelberg. I don't think the doc you linked with be accessible to all viewers. Could you copy-paste your proposal into the issue?

In case people can't access the outline, I'm posting it here.
—-----------------------------------------------SHARED EXTERNALLY---------------------------------------------
Proposed outline for sigstore docs
This outline will try to set up the left window menu item to be based on function and not names.
User Doc
Sigstore
Overview (https://docs.sigstore.dev/ ) & Main concepts (https://docs.sigstore.dev/main-concepts/)
Stability & Security (https://docs.sigstore.dev/api-stability/ & https://docs.sigstore.dev/security/)
Contributing & Community (https://docs.sigstore.dev/contributing/ & https://docs.sigstore.dev/community/)
Support (https://docs.sigstore.dev/support/)
FAQ (https://docs.sigstore.dev/faq/)
History (https://docs.sigstore.dev/history/)
Signing
Overview & Installation (https://docs.sigstore.dev/cosign/overview/ & https://docs.sigstore.dev/cosign/installation/)
OpenID connect signing (https://docs.sigstore.dev/cosign/openid_signing/)
PKCS 11 tokens signing (https://docs.sigstore.dev/cosign/pkcs11/)
Blobs (https://docs.sigstore.dev/cosign/signing_with_blobs/)
Containers (https://docs.sigstore.dev/cosign/signing_with_containers/)
Git support (https://docs.sigstore.dev/cosign/git_support/)
Gitsign (https://docs.sigstore.dev/gitsign/overview/)
Gitsign installation (https://docs.sigstore.dev/gitsign/installation/)
Gitsign usage (https://docs.sigstore.dev/gitsign/usage/)
Inspecting commit signatures (https://docs.sigstore.dev/gitsign/inspecting/)
Signing other types of artifacts (https://docs.sigstore.dev/cosign/other_types/)
Verifying
Signature verification (https://docs.sigstore.dev/cosign/verify/)
Timestamps (https://docs.sigstore.dev/cosign/timestamps/)
In-Toto Attestations (https://docs.sigstore.dev/cosign/attestation/)
Key Management
KMS support (https://docs.sigstore.dev/cosign/kms_support/)
Signing with self-managed keys (https://docs.sigstore.dev/cosign/signing_with_self-managed_keys/)
Importing a key pair (https://docs.sigstore.dev/cosign/import-keypair/)
Hardware-based tokens (https://docs.sigstore.dev/cosign/hardware-based-tokens/)
Command line interface
Cosign command line interface reference guide (this is very long. Put in link to https://github.com/sigstore/cosign/tree/main/doc)
Developer Docs
Cosign Specs
Attestation (https://github.com/sigstore/cosign/blob/main/specs/ATTESTATION_SPEC.md)
Cosign predicate (https://github.com/sigstore/cosign/blob/main/specs/COSIGN_PREDICATE_SPEC.md)
Cosign vulnerability attestation (https://github.com/sigstore/cosign/blob/main/specs/COSIGN_VULN_ATTESTATION_SPEC.md)
SBOM (https://github.com/sigstore/cosign/blob/main/specs/SBOM_SPEC.md)
Signature (https://github.com/sigstore/cosign/blob/main/specs/SBOM_SPEC.md)
Certificate Authority
Fulcio Overview (https://docs.sigstore.dev/fulcio/overview/)
Issuing certificates (https://docs.sigstore.dev/fulcio/certificate-issuing-overview/)
Using OIDC tokens (https://docs.sigstore.dev/fulcio/oidc-in-fulcio/)
Certificate specification (https://github.com/sigstore/fulcio/blob/main/docs/certificate-specification.md)
HSM support (https://github.com/sigstore/fulcio/blob/main/docs/hsm-support.md)
Transparency Log
Overview & Installation (https://docs.sigstore.dev/rekor/overview/ & https://docs.sigstore.dev/rekor/installation/)
Certificate Transparency Log Information (https://github.com/sigstore/fulcio/blob/main/docs/ctlog.md)
Public instance (https://docs.sigstore.dev/rekor/public-instance/)
Sharding (https://docs.sigstore.dev/rekor/sharding/)
Command line interface (https://docs.sigstore.dev/rekor/CLI/)
Pluggable types (https://docs.sigstore.dev/rekor/pluggable-types/)
Signing and uploading other pluggable types (https://docs.sigstore.dev/rekor/sign-upload/)
Verifying transparency log binaries (https://docs.sigstore.dev/rekor/verify-release/)
Kubernetes Policy Controller
Overview (https://docs.sigstore.dev/policy-controller/overview/)
Installation (https://docs.sigstore.dev/policy-controller/installation/)
Sample policies (https://docs.sigstore.dev/policy-controller/sample-policies/)

@olivekl @haydentherapper @ltagliaferri
Hi there.  If there are no comments on the structure and organization of the docs, I'll go ahead and start working on it this week.

Hi @jonvnadelberg, I don't have access to the doc (you can make it public), but am curious if there is any rationale behind the organization that you can provide so we can weigh in more about the why than the what?

Hi @ltagliaferri  I just granted you access to it.   You should be able to see it now.
The rationale behind this is to organize the documentation by function and not the names of modules, and also to try and place document in some semblance of an order that mirrors the user and developer experiences.
That's the idea anyway.   To try and make it easier for people to understand and learn how to use the product, depending on their role.

Hi @ltagliaferri, it looks like @jonvnadelberg copied the contents of the doc into this comment.
As for the why, the goal is to organize the docs in a way that more closely follows the primary user journeys. A user is likely to land on the docs with a goal such as "I want to verify a signature" or "I want to sign a blob," not "I want to read about Fulcio." The current organization is structured around tooling and what goes on under the hood, which makes sense from the point of view of someone developing Sigstore; most users, though, will look for information based on what it is they want to accomplish. The purpose of the proposed organization is to match those user goals more clearly.
There's more of an explanation and invitation for discussion about user journeys in the Issue #187 (comment) that's linked above.

updates merged into base closing issue.


Flag default values

Need to do a systematic check for Flags with arguments.
args > ENV > default
Should also halt if argument is missing.
How to handle a default value when followed by more flags/arguments? e.g.
cmd -f1 arg1 arg2
cmd -f1 -f2 fArg arg1 arg2

Need to keep arg1 and -f2 from being parsed as the argument to f1.
Also, something to keep in mind,  removing flags and their arguments from the cli args, so arguments can be parsed positionally.

🤔 Perhaps if a flag has a default value, and you want that default value used, then you simply don't pass the flag explicitly. E.g.
cmd arg1 arg2

and f1 default is loaded automatically. This makes stripping flags easier.
This also means that Flags with default values, (or similarly loaded from an ENV), then they cannot have conflicts with other flags, because there would be no way to "shut them off".


Hand over one complete message to the ClientHandler implementation at a time so that it doesn't have to inspect the headers and calculate how many messages are present

Sometimes multiple RPC responses arrive to the socket read buffer at once. At present, the implementation of ClientHandler and ServerHandler would have to inspect the header for the body size, then delimit the individual messages in this fashion - however, the decryption functionality has already done this so we might as well just hand over the individual message byte buffers from it so that the ClientHandler implementation can process one RPC response at a time.
At a high level, these can then be marshalled into the RPCMessage class, and then the body into an appropriate Java class / stream of classes. I will play around with this and make a separate pull request for it.

Hmm... My changes don't quite work, actually. For some reason, it seems to end up with each RPC header arriving as a message, followed by the body as a separate message (decoding into an RPC message when you join them up seems to work though)
 Bytes headerMessage = null;

    @Override
    public void receivedMessage(Bytes message) {
      System.out.println("We received a message?");
      System.out.println(new String(message.toArrayUnsafe(), UTF_8));

      if (headerMessage == null) {
        headerMessage = message;
        return;
      }

      Bytes headerAndBody = Bytes.concatenate(headerMessage, message);

      headerMessage = null;

      RPCMessage msg = new RPCMessage(headerAndBody);
      String body = msg.asString();

      System.out.println(body);

    }

On master, sometimes the first receivedMessage is just an RPC message on its own, but most of the time it's one or more full RPC header + bodies
I'll see if I can work out what the issue is / update this PR.

I've just realised from reading the protocol docs that this is because after decrypting a box stream header and body, you can end up with only part of the RPC message - so I guess I'll have to buffer these too :). I'll update this PR.

Indeed messages are chunked on top if box streams. You will need to reassemble them.

On Mar 24, 2019, at 11:11, Gordon Martin<EMAIL_ADDRESS>wrote:
I've just realised from reading the protocol docs that this is because after decrypting a box stream header and body, you can end up with only part of the RPC message - so I guess I'll have to buffer these too :). I'll update this PR.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@atoulme - I've just updated this PR with the changes to buffer up partial RPC messages, and hand over one complete one at a time to the handler. It seems to work!
Let me know if you'd like any changes.
Note: I just force pushed to the branch because I changed the approach compared to the previous PR (where I'd assumed you get full RPC messages after decrypting.)

Rebuilding. CircleCI has been capricious.

Please look at my comment on body size reading, and if you can add a commit to fix that, I can merge this tomorrow. Cheers!

Thanks @atoulme - I wasn't sure if I'd got that right - it's the first time I've done that sort of thing - when I printed it out and compared it to the body size it seemed tight but .toInt() is certainly more readable.  I'll push that change tonight / tomorrow when I'm back from my short holiday.

The change to use toInt() seems to work :). I've pushed the change


User Appsettings not generating correctly

The refactor in 5eb52dcd74866b55f31b1393784081e07ac40484 introduced a bug that causes the User Appsettings file to generate like this
{
  "TestingPlayerSlot": 0,
  "Warcraft3ExecutablePath": ""
}

instead of this
{
  "LaunchSettings": {
    "TestingPlayerSlot": 0,
    "Warcraft3ExecutablePath": ""
  }
}

resulting in an exception being thrown here
var launchSettings = config.GetRequiredSection(nameof(LaunchSettings)).Get<LaunchSettings>();

Ahh that explains so much, thank you!

Fixed by https://github.com/AzerothWarsLR/WarcraftLegacies/commit/7e4f3c9bb9496c75699ab407c9c460abc69bdf7c.


XML issue

Hi,
When I try to access the website url i am getting access denied issue. Can you please let me know where I went wrong?

Regards

Can you fill us in on the details? What page are you trying to access when the error is generated? Access Denied in this context might indicate the designer UI page is no longer or that permis are set to deny access to the designer UI.


fix mode='opencv' case in cupyx.scipy.ndimage.affine_transform

overview
Support for mode='opencv' in cupyx.scipy.ndimage.affine_transform seems to have been broken since CuPy 8.0 by the changes I introduced in gh-3166.
This PR restores the code path from CuPy 7.8 for this case.
closes #3601
additional info
This was not detected previously when testing locally because apparently @testing.with_requires('opencv-python') does not pick up the conda-forge opencv package, so this test case was always skipped on my system. If I comment out the with_requires statement, the following test completes locally after this change:
https://github.com/cupy/cupy/blob/a7766076f15cbe85036960b2faa930496c1c029b/tests/cupyx_tests/scipy_tests/ndimage_tests/test_interpolation.py#L190-L192

Jenkins, test this please

Jenkins CI test (for commit d8e2016e08ea78c09faf92637323804982c52d62, target branch master) succeeded!

I don't think any of the CI cases run these opencv tests? (otherwise we would have found the failure sooner). I did verify that all all OpenCV-related test cases pass locally (these including tests for zoom, shift and rotate as well).
mode='opencv' is an extra mode added by CuPy that does not exist in upstream SciPy, so opencv-python must be installed in order for the test cases to run.


Get map scale

HI,
is there a way to get or show the current map scale on screen?
Thank you very much.

you can calculate that based on zoomlevel check this link : https://wiki.openstreetmap.org/wiki/Zoom_levels


Is there a way I can view commanded joint torques?

Hi,
Let's say I'm using a Velocity Joint Interface. Is there any way to the joint torques that end up getting sent to the robot?
Thanks!

Any update on this @sgabl?

Hi, yes you could just check tau_J_d - there you see the desired link-side joint torque.

Yes, but if I am running joint velocity control, I would be able to see what's actually being sent.

For velocity control there is no direct way to see the commanded torque. To do that you would have to write your own velocity controller on torque basis. However, you can still view the measured torques tau_J. This could be enough for some use-cases.


Superset permissions not working for odh-env-user

When I visit this page:
https://superset-secure-odh-superset.apps.odh-cl1.apps.os-climate.org/superset/welcome/
I use GitHub as my auth mechanism, which takes me to the site, and a chain of access denials.  So I'm clearly missing some sort of authorization use SuperSet.  I have not problems using JupyterHub/Elyra/Trino.

so just a break down on how this works:

by default anyone that is in the odh-env-user can authenticate via ocp
anyone that can authenticate via ocp has the public superset role see here for what superset roles do what
anyone in the OCP group named odh-users has admin superset role. To add someone to this group, append this file here

Now I could just make it so that anyone that can authenticate against ocp has either alpha,gamma, or admin if you guys prefer. Just let me know what works best.

I think alpha as a default would be good.

Sorry to reopen.  While I can now open SuperSet and get to the main landing page without access errors (I am now a member of both Public and Alpha), I see very limited views of data I know is in trino.  When I select the wri_gppd schema, I see only the annual_gwh table, not also the plants and estimated_gwh tables.  There are many other things that seem broken due to insufficent permissions or perhaps the access I expect to see from interacting with trino via notebooks vs. interacting via SuperSet.  So, while I can access SuperSet, it's definitely not yet in a fully working state.

I don't think I need admin role.  I think something is whacky, either with the data layer or with superset.  With whom should I share my screen when I get a free minute between meetings today?

@erikerlandson would it be possible for you to meet with @MichaelTiemannOSC and identify the issues, and what permissions are needed?

Sounds to me like whenever a database is created a permission grant needs to be made to SuperSet.  Or whenever a user logs into SuperSet, trino needs to be queried as to what databases are present in the system.


adding more information section in services covid support

Can I add more information section in services covid support

Please elaborate what kind of more information section?

Adding more content like self care and communication part

Adding more content like self care and communication part

Okay go ahead but I will prefer different cards for self-care and communication. Try adding 3 cards to services section so that flow is maintained.

Can I work on this issue?

@SakshiChalke any update?


[6.x] Set Redis cluster prefix with PhpRedis

When using the PhpRedis extension, the prefix is only set when connecting to a single server. Since RedisCluster class allows to set a prefix, this PR modifies PhpRedisConnector class to set the prefix when creating a cluster instance.
This PR fixes #25619.
By the way, there are no tests that cover cluster connections. Would it be possible to modify the Travis pipeline in some way to run a cluster? Thus, it would be possible to run all Redis tests in both cases.

Won't the cache system already prefix things? If we set the prefix at the Redis level then won't the cache double-prefix?

@taylorotwell Yes for the first answer, because it is the desired behaviour, and no for the second one.
On the one hand, there is the global prefix to avoid collisions among several projects using the same Redis server. On the other hand, there is the cache prefix to avoid collisions within the project itself.
If so, PhpRedisConnector::createClient() would not set the global prefix.
Example
# REDIS_PREFIX=laravel:
# CACHE_PREFIX=cache

Redis::set('foo', 'bar');
Cache::put('foo', 'bar');

With PhpRedis/Predis and a single Redis instance:
redis:6379> keys *
1) "laravel:foo"
2) "laravel:cache:foo"

With PhpRedis and a Redis cluster:
redis:6379> keys *
1) "foo"
2) "cache:foo"

With PhpRedis and a Redis cluster, after merging this PR:
redis:6379> keys *
1) "laravel:foo"
2) "laravel:cache:foo"


🐞 反馈问题：OpenAI Translate Error While OpenAI Translate is disabled

请先确认以下事项

[X] 已仔细阅读了 README
[X] 在 issues 页面搜索过问题，但未能找到解决方法
[X] Easydict 已升级到最新版本

问题描述
The error notification pop up while OpenAI Translate is disabled, the error message the API token is not provided.

重现步骤
N/A
期望结果
If any service is disabled, the related error message should not pop up.
解决方案（可选）
No response

I believe it is due to this line https://github.com/tisfeng/Raycast-Easydict/blob/74665f7b384fe0f547eb91f05bcec44e2a873216/src/dataManager/dataManager.ts#L745
    // if (myPreferences.enableOpenAITranslate)

Thank you for your feedback. You are right. Initially, I commented out the code when testing it and forgot to uncomment it later.

I have raised one PR https://github.com/tisfeng/Raycast-Easydict/pull/37, feel free to merge it.


Exports didn't make it into Anki

everything works fine until the last step. I clicked exporting and a prompt popped up saying exporting is done. But no cards have been added into my Anki deck. Tried reinstalling Anki connect and plugin, didn't help.

I'm having this issue as well. Everything looks perfect on the Obsidian side, all my Anki deck names populate there, and it says that the export was successful. However, nothing is actually added to my Anki decks.


Updating Habitat/Planning section in RR

Proposed activity
Habitat section can be largely enhanced by highly desired sections available in Open Data
Why this is important
"Important for many reasons, there is currently no information on benthic habitat Corals and Sponges in the Reproducible Report. Construction activities, turbine foundations, and environmental pollutants can impact benthic habitat". Product Owners
Action items
The metadata spreadsheet highlight where this new info should be added (around rows 34/35)

[x] A substrate classification for the Inshore Scotian Shelf and Bay of Fundy, Maritimes Region
[x] Delineation of Coral and Sponge Significant Benthic Areas in Eastern Canada Open Data record

[x] NO DATA ON MARITIMES -- to confirm with Javier. Kernel Density Analyses of Coral and Sponge Catches from Research Vessel Survey Data for Use in Identification of Significant Benthic Areas https://open.canada.ca/data/en/dataset/fb1d1c3d-ba6e-4d0d-b629-f4f497edc10f
[x] Other effective area-based conservation measures https://open.canada.ca/data/en/dataset/44769543-7a23-4991-a53f-c2cf7c7a946f Warning: this is a new record that would impact current section titled: Draft Conservation Network Design"

"Substrate classification", "Significant coral and sponge benthic areas", and "Other effective conservation measures" sections have been added to main. Thanks Quentin for all of your guidance and help with getting me up to speed on this!!