Modify RESTClient post() to add CB-2FA-Token for SIWC transaction endpoints

With the April 2nd expansion of the CDP api keys to support SIWC urls, there is extra support needed for the /v2/accounts/:account_id/transactions endpoints.  This appears to be a holdover from the OAuth2 support, and may actually be an error in the API.  If not, support is needed for the transactions endpoints.  Specifically, posts this endpoint requires the CB-2FA-Token header.  This PR adds a cb_2fa_token argument to the RESTClient constructor to facilitate that.
Example
from requests.exceptions import HTTPError
from coinbase.rest import RESTClient

params = {
  "type": "send",
  "currency": "BTC",
  "to": "bc1qwc2203uym96u0nmq04pcgqfs9ldqz9l3mz8fpj",
  "amount": "0.00045678",
}

api_key = "organizations/{org_id}/apiKeys/{key_id}"
api_secret = "-----BEGIN EC PRIVATE KEY-----\nYOUR PRIVATE KEY\n-----END EC PRIVATE KEY-----\n"
client = RESTClient(
    api_key = api_key,
    api_secret = api_secret,
)
try:
    client.post("/v2/accounts/456789ab-cdef-0123-4567-89abcdef0123/transactions", params)
except HTTPError as e:
    if "two_factor_required" in e.args[0]:
        cb_2fa_token=input("CB-2FA-Token: ").strip()
        client = RESTClient(
            api_key = api_key,
            api_secret = api_secret,
            cb_2fa_token = cb_2fa_token,
        )
        client.post("/v2/accounts/456789ab-cdef-0123-4567-89abcdef0123/transactions", params)
    else:
        raise e

Changes

Add CB-2FA-TOKEN header when cb_2fa_token is found in instance
Add CB_2FA_TOKEN_ENV_KEY constant
Add cb_2fa_token to APIBase constructor
Add cb_2fa_token to RESTClient constructor

Thanks for reporting @brianddk ! I checked with our team and they said a fix was pushed for this. Could you check if you are able to hit this endpoint without the 2FA header now?

@brianddk Looking at the SIWC docs, it seems that it is expected for 2FA to be required for this endpoint.
Closing out this PR since we do not plan on supporting SIWC in this SDK for now.

@brianddk thank you again for flagging. This was indeed a bug in our service. A fix has now been pushed and you should not need the 2FA token header for this endpoint anymore.

A fix has now been pushed and you should not need the 2FA token header for this endpoint anymore.

Confirmed... Thanks.
You might want to let your contact in the API-dev team know that the update bugged the /v2/user/auth endpoint.  It now shows "method": null in the response JSON when CDP keys are used on it.

Thanks for that. That is now fixed as well.

Thanks for that. That is now fixed as well.

Confirmed.  Thx again.


[Bug report] Failed assertion of "raw image data is not already now!" on web

Version
8.1.0
Platforms
Web
Device Model
Chrome
flutter info
[✓] Flutter (Channel stable, 3.13.2, on macOS 13.5 22G74 darwin-arm64, locale en-GB)
    • Flutter version 3.13.2 on channel stable at /Users/douglastodd/Development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ff5b5b5fa6 (7 days ago), 2023-08-24 08:12:28 -0500
    • Engine revision b20183e040
    • Dart version 3.1.0
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
    • Android SDK at /Users/douglastodd/Library/Android/sdk
    • Platform android-33, build-tools 33.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.12.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.81.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.70.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 13.5 22G74 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 116.0.5845.140

[✓] Network resources
    • All expected network resources are available.

• No issues found!

How to reproduce?
When accessing the rawImageData from ExtendedImageEditorState the following assertion is thrown
rawImageDataMap.containsKey(provider)
"raw image data is not already now!"

This only occurs on web (works fine on Android and iOS).
This is using the ExtendedImage.network constructor with a valid editorKey and cacheRawData: true.
Logs
Assertion failed:
extended_image_provider.dart:45
rawImageDataMap.containsKey(provider)
"raw image data is not already now!"
../dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:49            throw_
../dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 35:3              assertFailed
../packages/extended_image_library/src/extended_image_provider.dart 45:43                  get rawImageData
../packages/extended_image/src/editor/editor.dart 340:33                                   get rawImageData
../packages/theme/src/widgets/images/resize_web.dart 18:34                                 editImage
../dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54                      runBody
../dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 127:5                      _async
../packages/theme/src/widgets/images/resize_web.dart 7:29                                  editImage
../packages/theme/src/widgets/images/sh_network_image.dart 151:45                          <fn>
../packages/stash_hub/presentation/uploads/logic/photo_edit_notifier.dart 25:47            editAndUpload
../dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54                      runBody
../dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 127:5                      _async
../packages/stash_hub/presentation/uploads/logic/photo_edit_notifier.dart 18:32            editAndUpload
../packages/stash_hub/presentation/uploads/widgets/full_screen_record_picture.dart 207:78  <fn>
../dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 84:54                      runBody
../dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 127:5                      _async
../packages/stash_hub/presentation/uploads/widgets/full_screen_record_picture.dart 206:40  <fn>
../packages/theme/src/widgets/images/sh_network_image.dart 151:34                          onStreamData
../dart-sdk/lib/async/zone.dart 1407:47                                                    _rootRunUnary
../dart-sdk/lib/async/zone.dart 1308:19                                                    runUnary
../dart-sdk/lib/async/zone.dart 1217:7                                                     runUnaryGuarded
../dart-sdk/lib/async/stream_impl.dart 339:11                                              [_sendData]
../dart-sdk/lib/async/stream_impl.dart 515:13                                              perform
../dart-sdk/lib/async/stream_impl.dart 620:10                                              handleNext
../dart-sdk/lib/async/stream_impl.dart 591:7                                               <fn>
../dart-sdk/lib/async/zone.dart 1391:47                                                    _rootRun
../dart-sdk/lib/async/zone.dart 1301:19                                                    run
../dart-sdk/lib/async/zone.dart 1209:7                                                     runGuarded
../dart-sdk/lib/async/zone.dart 1249:23                                                    <fn>
../dart-sdk/lib/async/zone.dart 1399:13                                                    _rootRun
../dart-sdk/lib/async/zone.dart 1301:19                                                    run
../dart-sdk/lib/async/zone.dart 1209:7                                                     runGuarded
../dart-sdk/lib/async/zone.dart 1249:23                                                    callback
../dart-sdk/lib/async/schedule_microtask.dart 40:11                                        _microtaskLoop
../dart-sdk/lib/async/schedule_microtask.dart 49:5                                         _startMicrotaskLoop
../dart-sdk/lib/_internal/js_dev_runtime/patch/async_patch.dart 181:15                     <fn>

Example code (optional)
No response
Contact
No response

not support on web

you can take a look at example

Please would you add the fact it is not supported to the documentation.

https://github.com/fluttercandies/extended_image/blob/2f0042598f932feaba869a3f6a6b6bd93ff9f76b/example/lib/common/utils/crop_editor_helper.dart#L37


Fixing power is schadenfreude

Laying cables is annoying because sometimes it lays on the tile you clicked on and sometimes it doesn't, especially if there's a SMES or the likes on the tile. If I can't lay it should tell me why.
Trying to debug power issues just requires slamming your head into a wall until it turns on. Do you have enough generation? Are the cables unplugged? No idea.
Cable terminals are unintuitive even if they need to exist, at a minimum there should be a popup or the likes.

Possible fixes:

UIs / examines saying whether something is recharging or not (so even if it's at 0% I know it's getting power at least and feeding it out)
Power alerts console, possibly with a drawing of the station like RadarControl that has a list of HV / MV nodes.
Anything else anyone can think of.

Step 1: point people to the wiki till we get books in game for power devices.
That aside, I had a thought about drawing HV circuits on a console, pretty much how real life circuits do it with a mimics board. I imagine it would be fairly easy to do by connecting the lines between entities. Display power info on them etc.

Regarding your possible fix #1:
In case something is connected but currently not charging (due to a lack of supply), would you show that data in the examine? (i.e "Connected to powernet, but not charging")
Or would it just say "Recharging" even though it's currently NOT being recharged, as it's not being supplied?

we have swag power ui console


Upgrading from HC to HAP

Hello!
First I would like to thank you for the amazing work on this library, it's really fun to play with Go and Homekit accessories!
I'm trying to migrate from HC to HAP in the most idiomatic way, but I'm not sure to understand what's the equivalent of OnValueRemoteGet of a characteristic in HAP, to allow Homekit to update the current real value of the characteristic (in my case, it's an air conditioner controlled via a remote API in the cloud, which I can also control using a remote)
If someone could help me on that, it would really help me!
Thank you :)

The best alternative is ValueRequestFunc. This function is called when client reads the value of a characteristic.
c.ValueRequestFunc = func(*http.Request) (interface{}, int) {
	// Make an HTTP call to the API and return
	// the value of the characteristic.
	return ...
}

If you want to get notified when a characteristic is updated by a client, you have to use OnSetRemoteValue. This function is defined by the bool, int, float, bytes types.
c.OnSetRemoteValue(func(v bool) error {
	// Make an HTTP call to the API.
	// If the HTTP request fails, you can return an error.
	// Otherwise return nil.
	return nil
})


Remove gh-pages branch to avoid confusion

This is just an announcement. I'll delete it later today or tomorrow. It's all my code in it and you shouldn't worry.

Closing as done


fix(floating-toc): css problems + remove env variable

[x] floating TOC now displayed properly on all devices
[x] remove env variable, use css class macro from confluence instead

@PiiXiieeS Can you give it a try on local before merging ?
NOTE: I used the class name konviw-float-TOC (I found it's more explicit), so maybe you need to change the macro on confluence

Very good, it works well on my local tests.
We just need to be careful on the fact that it is case sensitive and the class must be exactly "konviw-float-TOC" (with TOC is capitals).


Pressing outside the next button, triggers back button

I've tried implementing this and i'm wondering if the expected behavior of pressing the empty space between back and the next button should trigger a back button?

Thanks for pointing this out. This is indeed not intended behavior.  I will fix it

I fixed this. You can check one of the fiddles from readme/docs and see if it's ok now. I will also publish a new npm version soon

Released on npm under 0.4.2 -> https://github.com/cristijora/vue-form-wizard/releases/tag/v0.4.2


Hiding overview costs of electricity production chart

The BECC(U)S project introduced a lot of negative costs to the model.
2 graphs show errors because of this.
This PR hides the broken graph "Total cost of electricity production".
TO-DO:
In addition it fixes the graph "Overview of yearly costs".

@mabijkerk Good spot! I changed it to the costs_overview_detailed chart


python311Packages.phx-class-registry: 4.0.6 -> 4.1.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.phx-class-registry is: Factory and registry pattern for Python classes
meta.homepage for python311Packages.phx-class-registry is: https://class-registry.readthedocs.io/en/latest/
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.1.0 with grep in /nix/store/8dvw4dlhk9lgnc5g16bg8d8xwhgafmph-python3.11-class-registry-4.1.0
found 4.1.0 in filename of file in /nix/store/8dvw4dlhk9lgnc5g16bg8d8xwhgafmph-python3.11-class-registry-4.1.0

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
backblaze-b2
python311Packages.phx-class-registry
python312Packages.phx-class-registry

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8dvw4dlhk9lgnc5g16bg8d8xwhgafmph-python3.11-class-registry-4.1.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.phx-class-registry https://github.com/r-ryantm/nixpkgs/archive/080716f284ed28ac8be36bb4cf676bea035f3b87.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/080716f284ed28ac8be36bb4cf676bea035f3b87#python311Packages.phx-class-registry

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8dvw4dlhk9lgnc5g16bg8d8xwhgafmph-python3.11-class-registry-4.1.0
ls -la /nix/store/8dvw4dlhk9lgnc5g16bg8d8xwhgafmph-python3.11-class-registry-4.1.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

backblaze-b2
python311Packages.phx-class-registry
python312Packages.phx-class-registry

Maintainer pings
cc @kevincox for testing.

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

6 packages built:

backblaze-b2
backblaze-b2.dist
python311Packages.phx-class-registry
python311Packages.phx-class-registry.dist
python312Packages.phx-class-registry
python312Packages.phx-class-registry.dist


use jupyterbook

docs: use consistent capitalisation - FHIRflat
docs(mapping): fix headers
docs: use jupyter-book

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

Project coverage is 96.64%. Comparing base (474a7f1) to head (da468bc).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #55   +/-   ##
=======================================
  Coverage   96.64%   96.64%
=======================================
  Files          39       39
  Lines        1756     1756
=======================================
  Hits         1697     1697
  Misses         59       59

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


Taiko-rollup

Describe the feature request
Description of the feature request here.
Describe alternatives you've considered
Description of the alternatives you've considered here.
Additional context
Additional context here.

started keep joinus


No Files found for tomcat9.service

Hey,
recently I am trying to install guacamole in my self hosted server. i was facing some issues
###Issue :
No Files found for tomcat9.service
head: can not open '/etc/ssl/certs/java/cacerts' for  reading: no such file or derectory

Server info :-
OS : Debian 10 (64-bit)
Yunohost version : <IP_ADDRESS>
How can i sove this issue?

Fixed.


Use the same tab navigator UI buttons as for Questionnaire/Answers

don't forget to add the PROM/PREM legend

I don't see any PROM/PREM legend

I see too many duplicated code. methods like
getPossibleProms getPossiblePrems -> getPossibleQuestion(questionType)
getAnswersForEachProm, getAnswersForEachPrem -> getAnswersForQuestion(questionType)
getCheckboxOptionsForEachProm,getCheckboxOptionsForEachPrem ->getCheckboxOptionsForQuestion(questionType)
getSliderOptionsForEachProm, getSliderOptionsForEachPrem -> getSliderOptionsForEachQuestion(questionType)
getSliderOptionsForEachProm,


Program source directory can be removed

The following command,
sb2gs project.sb3 PATH_TO_SB2GS
removes every file in the same directory in which sb2gs is ran from.
You would expect that this command easily could be accidentally run by the user when first testing the program.

not a bug

not a bug

not good


Case

Best case that holds a stylus?

https://makerworld.com/en/models/203834#profileId-223976

=]


UNDER CONSTRUCTION

Building the card.

Fixes: #186

I've rebased this PR to the latest master for you.  I also added our basic commonTests, see here.  I've added the .only() call to the Card-test.js as well so they are the only the tests that run.
It's been a while since you've hacked on this, so I'd blow away and reinstall node modules.  You should then be able to run npm run test:watch and see only the common card tests.  This should get you going as there are many well defined tests to get passing:

Cheers!

:fallen_leaf: sounds good man! Thanks!

Yo @eanplatter, I know you've been busy.  Thanks to @jamiehill and a few others we're getting a lot of momentum.  If we come up on this component, shall we ping you or hop on it?
Let me know what your plans are.  Thanks.

Bump.  Noted the new CONTRIBUTING.md docs.  We need to spec out this component's API.

@levithomason I'd be great to pair on this one of these evenings! I'd like to get a feel for the workflow so I can make contributions whenever I've got time, I've been doing react native lately so my need for stardust hasn't been as present, but as soon as I move back to web stuff I'll be using it.

I'm game for some pairing for sure.  Busy tonight with 3SC, but hit me up on Slack to get a time set.

Closing in light of #387


Guidelines for operation tags

Problem description
Current API DG says that for each HTTP method (i.e operation) definition should include:

Tag list to classify methods.

Expected action
More detailed guidelines on usage and style of operation tags:

Definition of tags in a top-level tags element
Adding a tag to each operation

Additional context
tags element is not required by OAS:
https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.2.md#fixed-fields

A list of tags used by the specification with additional metadata. The order of the tags can be used to reflect on their order by the parsing tools. Not all tags that are used by the Operation Object must be declared. The tags that are not declared MAY be organized randomly or based on the tools' logic. Each tag name in the list MUST be unique.

The need for guidelines was indicated in the discussion in https://github.com/camaraproject/QualityOnDemand/pull/227
Explanation of tags in blog post.

My view is that tags should be optional for a given API, but if they are used then they should follow a common style.
My preference for the tag style is Title Case.


<EMAIL_ADDRESS>incompatible with graphql-request v6.0.0+ when using graphql-request as the fetcher

Which packages are impacted by your issue?
@graphql-codegen/typescript-react-query
Describe the bug
This ticket is essentially the same as https://github.com/dotansimha/graphql-code-generator-community/issues/331, except it also applies to the package<EMAIL_ADDRESS>when used with graphql-request as the fetcher.
Your Example Website or App
n/a
Steps to Reproduce the Bug or Issue

Update graphql-request to 6.0.0
Generate typings

Expected behavior
Not to get any type errors.
Screenshots or Videos
No response
Platform

OS: macOS
NodeJS: 18.16.0
graphql version: 16.7.1
@graphql-codegen/cli: 4.0.0,
@graphql-codegen/near-operation-file-preset: 2.5.0,
@graphql-codegen/typescript: 4.0.1,
@graphql-codegen/typescript-operations: 4.0.1,
@graphql-codegen/typescript-react-query: ^4.1.0,

Codegen Config File
No response
Additional context
No response

I have made a pull request to fix this. @saihaj Would you help comment/review on the PR?


Poll: New straw poll page for taking a quick vote

What's your idea?
Board members create a new straw poll (custom or generated ID) via HTTP request, initializing a new straw poll to reach a decision amongst those who received the link to the straw poll.
Use cases

Determining a fair vote having to do with a club meeting activity.
Determining a fair vote for deciding a motion during a board meeting.

Should this remain or will we eventually replace this in form?


[libb2] Fix using absolute install name in arm64-osx-dynamic triple

Fix #31719:

[ x] Changes comply with the maintainer guide
[ x] SHA512s are updated for each updated download
[ x] The "supports" clause reflects platforms that may be fixed by this new version
[ x] Any fixed CI baseline entries are removed from that file.
[x ] Any patches that are no longer applied are deleted from the port's directory.
[ x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[ x] Only one version is added to each modified port's versions file.

Thank you for mentioning this PR, our ci does not have a corresponding machine to test this change, so please make sure that the local test is ok.

You're welcome. I understand that CI may not be able to test this particular change. Here're some test steps, if anyone has arm64-osx machine. Feel free to expand upon it:
vcpkg remove libb2:arm64-osx-dynamic
vcpkg install libb2 --host-triplet=arm64-osx-dynamic --triplet=arm64-osx-dynamic --no-binarycaching

Expected Result:
❯ otool -L /opt/vcpkg/packages/libb2_arm64-osx-dynamic/lib/libb2.dylib
/opt/vcpkg/packages/libb2_arm64-osx-dynamic/lib/libb2.dylib:
	@rpath/libb2.1.dylib (compatibility version 2.0.0, current version 2.4.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)

and includes @loader_path as its @rpath.
❯ otool -l /opt/vcpkg/packages/libb2_arm64-osx-dynamic/lib/libb2.dylib | grep -A5 LC_RPATH
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)

Before adding so much osx rpath code to a single port, it should be checked if this is a general problem, i.e. if it needs a general hook. The situation reminds me of what z_vcpkg_fixup_rpath_in_dir does for the x64-linux-dynamic triplet.

Related: #31681.

CMake project, like QT, has already set such @rpath when install. I found these issues when installing QT in arm64 osx, other dependencies *.dylib have @rpath as expected.
It's good to have a general hook function(like fixup_bundle() from cmake) to fix the @rpath when install.
Thanks for your mentions. I'll look for what z_vcpkg_fixup_rpath_in_dir does.

Thanks for your mentions. I'll look for what z_vcpkg_fixup_rpath_in_dir does.

Thanks for looking!
I think the crux of this issue is that we never really should have added osx-dynamic for the same reason we resisted adding linux-dynamic for a long time: that we can build the thing but we know the resulting output won't run. We added linux-dynamic only at the same time z_vcpkg_fixup_rpath_in_dir made that triplet function in the vast majority of cases. Notably, what z_vcpkg_fixup_rpath_in_dir does is applied to all ports, not on a per-port basis.
@liviaerxin I think we have 3 paths forward here:

Please take a look at how z_vcpkg_fixup_rpath_in_dir works, and let us know that:
a. the same strategy works for macos, so we should do that, or
b. the same strategy does not work for macos, for ~reasons~
Indicate that you are not interested in investigating that for us :)

I setting this to draft status to mark that the ball's in your court. :) Please mark ready for review when you've chosen 1a, 1b, or 2.

Thanks for your mentions. I'll look for what z_vcpkg_fixup_rpath_in_dir does.

Thanks for looking!
I think the crux of this issue is that we never really should have added osx-dynamic for the same reason we resisted adding linux-dynamic for a long time: that we can build the thing but we know the resulting output won't run. We added linux-dynamic only at the same time z_vcpkg_fixup_rpath_in_dir made that triplet function in the vast majority of cases. Notably, what z_vcpkg_fixup_rpath_in_dir does is applied to all ports, not on a per-port basis.
@liviaerxin I think we have 3 paths forward here:

Please take a look at how z_vcpkg_fixup_rpath_in_dir works, and let us know that:
a. the same strategy works for macos, so we should do that, or
b. the same strategy does not work for macos, for ~reasons~
Indicate that you are not interested in investigating that for us :)

I setting this to draft status to mark that the ball's in your court. :) Please mark ready for review when you've chosen 1a, 1b, or 2.

Hello @BillyONeal, I've used an approach as 1a does to try to fix install_name and rpath problems for triplet osx-dynamic on all ports generally. And I have done tests on some shared libraries with that kind of known issue. Here is one test on icu:
Before fix(vcpkg of commit idafbb37cfd648335fd980f6fb7dbc2d0c84c009cf):
❯ otool -L /opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/*dylib
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicudata.72.1.dylib:
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicudata.72.dylib:
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicudata.dylib:
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicui18n.72.1.dylib:
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicui18n.72.dylib:
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicui18n.dylib:
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuio.72.1.dylib:
	@rpath/libicuio.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuio.72.dylib:
	@rpath/libicuio.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuio.dylib:
	@rpath/libicuio.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicutu.72.1.dylib:
	@rpath/libicutu.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicutu.72.dylib:
	@rpath/libicutu.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicutu.dylib:
	@rpath/libicutu.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.72.1.dylib:
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.72.dylib:
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.dylib:
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)

❯ otool -l /opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/*dylib | grep -A3 LC_RPATH

❯ ~/Documents/dlopen_test.out /opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.72.dylib
dlopen(/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.72.dylib, 0x0001): Library not loaded: @rpath/libicudata.72.dylib
  Referenced from: <4A737B11-73EC-33E2-87E3-8AA577A9EDD3> /opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.72.1.dylib
  Reason: tried<EMAIL_ADDRESS>(no such file), '/usr/local/lib/libicudata.72.dylib' (no such file), '/usr/lib/libicudata.72.dylib' (no such file, not in dyld cache)
dlopen sample%

Here we see /opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicutu.72.dylib has flaws on its dependent libicuuc.72.dylib and libicudata.72.dylib.
After fix:
❯ otool -L /opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/*dylib
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicudata.72.1.dylib:
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicudata.72.dylib:
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicudata.dylib:
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicui18n.72.1.dylib:
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicui18n.72.dylib:
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicui18n.dylib:
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuio.72.1.dylib:
	@rpath/libicuio.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuio.72.dylib:
	@rpath/libicuio.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuio.dylib:
	@rpath/libicuio.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicutu.72.1.dylib:
	@rpath/libicutu.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicutu.72.dylib:
	@rpath/libicutu.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicutu.dylib:
	@rpath/libicutu.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicui18n.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.72.1.dylib:
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.72.dylib:
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.dylib:
	@rpath/libicuuc.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	@rpath/libicudata.72.dylib (compatibility version 72.0.0, current version 72.1.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.36.0)

❯ otool -l /opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/*dylib | grep -A3 LC_RPATH
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicudata.72.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicudata.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicui18n.72.1.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicui18n.72.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicui18n.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuio.72.1.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuio.72.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuio.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicutu.72.1.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicutu.72.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicutu.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.72.1.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.72.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)
/opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.dylib:
--
          cmd LC_RPATH
      cmdsize 32
         path @loader_path (offset 12)

❯ ~/Documents/dlopen_test.out /opt/vcpkg/packages/icu_arm64-osx-dynamic/lib/libicuuc.72.dylib
dlopen sample%

Need I open a new PR for this general fix?

Thanks for the suggestions!
I've submitted PR: #32200 (method 1a)to solve these issues generally that can be applied to all ports by taking ideas from z_vcpkg_fixup_rpath_in_dir .
Hope arm64-osx-dynamic can be introduced into official triplets upon this fixup.

Note: I will be converting your PR to draft status. When your submitted PR 32200 is merged, please revert to "ready for review". That way, I will mark this PR as reviewed.

Note: I will be converting your PR to draft status. When your submitted PR 32200 is merged, please revert to "ready for review". That way, I will mark this PR as reviewed.

Thanks!

@liviaerxin Thanks for your PR, Is work still being done for this PR?

Still in progress, as #32200 gets some feedback nowadays.

@liviaerxin Thanks for your PR, Is work still being done for this PR?

Closing this PR since it seems that no progress is being made. Please ping us to reopen if work is still being done.


[PROPOSAL] Add CHANGELOG

What/Why
What are you proposing?
Add CHANGELOG enforced with a GHA.
What users have asked for this feature?
I'd like every PR to come with an entry in CHANGELOG so we know what's changing with every release without having to manually collect release notes. See https://github.com/opensearch-project/OpenSearch/issues/1868 for more details.

Maybe a good idea will be to adopt a release-drafter for the changelog purposec, which is connected with release.

@piotrooo We've been having the hardest time making those humanly readable :(


Next release

Is there a time frame for the next release? I'm interested in using the new dirname, basename, extname features.

@travisperson I can cut a minor release right now

0.5.0


moment diff and subtract in one equation is giving unpredictable results.

Description of the Issue and Steps to Reproduce:
We have the below line of code to calculate 31 (as of today):
Math.ceil(moment().diff(moment().subtract(2, 'months'), 'days') / 2)
It gives 30 sometimes and 31 sometimes. Absolutely unpredictable.
I could see consistency with below code.
moment()
Math.ceil(moment().diff(moment().subtract(2, 'months'), 'days') / 2)
So calling moment() once, just before problematic code, kind of resolved my issue so there is some unpredictable nature.
Please look into it.
Please include the values of all variables used.
Environment:
OS: Ubuntu 16.04 LTS, Chrome: 52.0.2743.116 (64-bit), Node: 6.3.1
Other information that may be helpful:

The time zone setting of the machine the code is running on
Los Angeles Timezone
The time and date at which the code was run
Run the code between Oct/4/2016, 11:30 -- Oct/4/2016, 13:00
Other libraries in use (TypeScript, Immutable.js, etc)
Mocha

If you are reporting an issue, please run the following code in the environment you are using and include the output:
console.log( (new Date()).toString())
Tue Oct 04 2016 13:09:57 GMT-0700 (PDT)

console.log((new Date()).toLocaleString())
10/4/2016, 1:09:57 PM

console.log( (new Date()).getTimezoneOffset())
420

#console.log( navigator.userAgent)

console.log(moment.version)
2.14.1

Ensure your issue is isolated to moment. Issues involving third party tools will be closed unless submitted by the tool's author/maintainer.
I do believe that issue is within moment library.

Also running into the same error on Mac OS X 10.11.6, Node 6.2.2, Moment 2.14.1. Adding moment() to the line above also fixed it for me.

I could reproduce this issue in the latest version of moment i.e. 2.15.1

I think, I pressed the trigger little early.
A small brain-storm session with my colleagues revealed the solution to be:
now = moment()
Math.ceil(moment(now).diff(moment(now).subtract(2, 'months'), 'days') / 2)
Closing this bug.
If you have invested anytime into this then thanks a lot.


change the warnings in cqr predictions

Description
Fixes a bug in two warnings in the MapieQuantileRegressor predictions
Type of change
Please remove options that are irrelevant.

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

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

[ ] Test A
[ ] Test B

Checklist

[x] I have read the contributing guidelines
[x] I have updated the HISTORY.rst and AUTHORS.rst files
[x] Linting passes successfully : make lint
[x] Typing passes successfully : make type-check
[x] Unit tests pass successfully : make tests
[x] Coverage is 100% : make coverage
[x] Documentation builds successfully : make doc

Codecov Report
Base: 99.89% // Head: 99.89% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (8f1cabf) compared to base (e476f7f).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #253   +/-   ##
=======================================
  Coverage   99.89%   99.89%
=======================================
  Files          26       26
  Lines        2850     2852    +2
  Branches      306      306
=======================================
+ Hits         2847     2849    +2
  Misses          3        3

Impacted Files
Coverage Δ

mapie/quantile_regression.py
100.00% <100.00%> (ø)

mapie/tests/test_utils.py
100.00% <100.00%> (ø)

mapie/utils.py
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[Feature] Support to set the table option by dynamic global job configuration

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
When using Flink to query the Paimon table, supporting overwriting the catalog table option by SET syntax will be more convenient. The dynamic options can only take effect in the current session.
Solution
No response
Anything else?
No response
Are you willing to submit a PR?

[X] I'm willing to submit a PR!

In my current implementation, we inject the options with the specific prefix in flink config to the table option. So the requirements like #1943 can also be done without introducing more new configs.
WDYT @JingsongLi

Sounds good to me, actually, I think it is good to introduce this mechanism in reviewing for #1943


Nginx only -- unexpected end of file, expecting ";" or "}" in /etc/nginx/conf.d/vesta.conf:4 nginx:

Ubuntu 14.04  vanilla install
Nginx only for vesta configuration

Restarting nginx nginx                                                                                nginx: [emerg] unexpected end of file, expecting ";" or "}" in /etc/nginx/conf.d/vesta.conf:4
nginx: configuration file /etc/nginx/nginx.conf test failed

Easy to fix.  The generated vesta.conf looks like this
include /home/admin/conf/web/nginx.conf;
Include /home/admin/conf/web/snginx.conf

Just make the I in Include on the second line lower case and add ; to end of second line then
service nginx restart

This is the same as one of the posts in issue #5.  It's actually a bug in one of the Vesta command line tools.  I've linked to a couple of open issues in Vesta's bug tracker in issue 5.  {There is a fix available here.](https://bugs.vestacp.com/issues/21)


(ForumsTeam) Fixes MicrosoftDocs/azure-docs#5817

(ForumsTeam) Fixes MicrosoftDocs/azure-docs#5817

Hi @MarkusVi, would you please review the proposed changes. Thanks.

#sign-off

Closing this PR with the author's OK.


[FLOC-2640] Display debug information to help diagnose yum network problems

This PR makes yum display details about low-level network operations while building the CentOS Dockerfile. This additional information might be useful next time FLOC-2452 shows up, or for other network problems.  The additional information is sent to stderr, and gets logged near the top of the flocker-omnibus-centos-7 build-package step.

Yay more logs, I guess? Merge when buildbot is green (I'll restart a cuople of builds). I suggest moving parent issue out of sprint until it reoccurs.


OIDC4VC other party metadata : if security level is high and metdata not available , wallet does not engage the process

metadata for verifier -> registration paramtere
medatada for issuer -> open id configuration

to be explained in details


Sign form

add margin-bottom propertie Sign form

@Mansi168

hello I want to work on this issue.
Can you pls assign this to me.
The form will be with a good ui.

@BTANISHA11 No because I already assigned

hey @BTANISHA11 look for unassigned issues or make ur own issue :)

okk


[New chain]: Swisstronik testnet

Chain Name
Swisstronik testnet
RPC URL
https://json-rpc.testnet.swisstronik.com/unencrypted/
The chain must be added to https://chainlist.org/

[X] I confirm that the chain is added to chainlist

After creating the issue, a bot will estimate the required pre-fund and post it in the comments. Please check this checkbox after you send the pre-fund.

[x] I sent the pre-fund in accordance with Github Action's comment

Relevant information
Block explorer: https://explorer-evm.testnet.swisstronik.com/

I tried deploying on this chain and the deployment simulation is not successful. In particular, when we simulate the deployment transaction, it is returning that the contract will be deployed with the empty byte code instead of the expected one.
curl -s https://json-rpc.testnet.swisstronik.com -H 'content-type: application/json' --data '{"jsonrpc":"2.0","id":0,"meth
od":"eth_call","params":[{"data":"0x604580600e600039806000f350fe7fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffe03601600081602082378035828234f58015156039578
182fd5b8082525050506014600cf3"},"latest"]}'

Returns
{"jsonrpc":"2.0","id":0,"result":"0x"}

Hi @nlordell , I changed the RPC to use the unencrypted version, it should be ok.
Can you try one more time ?
https://json-rpc.testnet.swisstronik.com/unencrypted/

I still run into the same error with the deployment script. It looks like its an issue with the node not simulating contract creation eth_calls as others do (notably GETH) in that it does not return the bytecode that will be deployed.

Hi @nlordell , we've done a chain upgrade which should fix issues mentioned above.
Now your request:
curl --location 'https://json-rpc.testnet.swisstronik.com/unencrypted/' \
--header 'Content-Type: application/json' \
--data '{
    "jsonrpc":"2.0",
    "id":0,
    "method":"eth_call",
    "params":[{
        "data":"0x604580600e600039806000f350fe7fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffe03601600081602082378035828234f58015156039578182fd5b8082525050506014600cf3"
        },
    "latest"]}'

returns:
{
  "jsonrpc": "2.0",
  "id": 0,
  "result": "0x7fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffe03601600081602082378035828234f58015156039578182fd5b8082525050506014600cf3"
}

Could you please try one more time to deploy contracts?


cacert problem is fixed with certifi

We need to include this new python package in requirements.txt files.


report to monika-hq and update config periodically

This PR is the second part of #121
Monika should be able to send saved data to Symon server if configured.

[x] Add a new key in the configuration file to specify the URL or IP address of Symon and the API Key to connect to Symon.
[x] If Symon server is specified, Monika first performs handshake with Symon. See this doc.
[x] After handshake, Monika performs the report flow in interval.
[ ] On incident/recovery, Monika also performs the report flow.

rebased to main branch


SCAN_FAILED after 4 scans

Prerequisites
Check all boxes if you have done the following:

[x] Checked that your issue isn't already filed: https://github.com/tripflex/wifiwizard2/issues
[x] Make sure you fill out the Issue Type below

Issue type
Select all that apply

[x] Bug
[ ] Enhancement
[ ] Task
[ ] Question
[ ] Other

Description
I have a button that triggers scan on click. When I try to scan for 5th time it fails with an error message 'SCAN_FAILED'. Every time after 4 successful scans it fails for no reason.
Steps to Reproduce

Fresh cordova instalation
Install this package and run WifiWizard2.scan().then((res) => { }).catch(() => { })
Try it out on Android 9 (In my case Samsung S8)

Expected behavior: To get scan results.
Actual behavior: Get an error message 'SCAN_FAILED' after 4 successful scans. It always fails at 5th scan.
Reproduces how often: Every 5th scan.
Versions
Please include the plugin version that you are using and also include the OS, version and device you are using.
Plugin version: 3.1.1
Android: 9
Cordova: 9.0.0
EDIT:
Maybe it has to do something with calling it too often and throttling of WiFi happens and the OS is blocking it? If someone more experienced can clarify this in more details I would appreciate it.

I just googled your assumption regarding throttling and found the following:

Android 9:
Each foreground app can scan four times in a 2-minute period. This allows for a burst of scans in a short time.
All background apps combined can scan one time in a 30-minute period.
Android 10 and higher:
The same throttling limits from Android 9 apply. There is a new developer option to toggle the throttling off for local testing (under Developer Options > Networking > Wi-Fi scan throttling).

See: https://developer.android.com/guide/topics/connectivity/wifi-scan#wifi-scan-throttling
I guess we can close this then.
/cc: @tripflex


COOK-35 Allow setting limits.d via attributes

Set limits for hdfs/mapred/yarn and hbase, as set by CDH and HDP prior to 2.2... This brings HDP 2.2 in line with the rest of the distributions.

LGTM


Migrate to ionic 7

What is the motivation for adding/enhancing this feature?
Migrating to ionic 7.x will help in using some latest features in the components and will also solve some issues that were present in ionic 6.
What are the acceptance criteria?

[ ] Update to ionic 7
[ ] Migrate all the dependent package to a version that supports ionic 7
[ ] Update the components as per the migration guide
[ ] Test the components so that there is no breaking change

Can you complete this feature request by yourself?

[ ] YES
[ ] NO

Additional information

It has been observed that on refresh of users page the scrollbar is not working properly which is causing difficulty in searching the user.
Checked the same in production and found that it is working fine there.
Maybe it is occurring because of ionic upgrade.
Hence, reopening this ticket.
https://jam.dev/c/d6ea92f6-f249-429e-ba97-5cf475095712

It has been observed that on refresh of users page the scrollbar is not working properly which is causing difficulty in searching the user. Also the security group of logged in user is not properly aligned. Checked the same in production and found that it is working fine there. Maybe it is occurring because of ionic upgrade. Hence, reopening this ticket. https://jam.dev/c/d6ea92f6-f249-429e-ba97-5cf475095712 https://jam.dev/c/448b2ad2-0529-4a15-b73d-3e2052403426

Verified and working fine in release v1.10.0. Hence, closing this ticket.
https://jam.dev/c/d509ea47-26c1-469b-881b-a3db84a1ec9a


React Can't resolve 'react/jsx-runtime'

Module not found: Error: Can't resolve 'react/jsx-runtime'
react: 17.02
typescript
alias: {
'react/jsx-runtime': 'react/jsx-runtime'
}

Hi @MadikMayCry!
I tried to use the library with 17th react and everything works well.
I installed it with create-react-app an used this instruction to revert react version from 18 to 17.
Can you provide more information about your problem?

we are using custom ssr & webpack

Did you try to use this alias?
alias: {
'react/jsx-runtime': 'react'
}

I am going to close this as the necessary debugging information hasn't been provided in over a year and the library now officially requires React 18 or higher.
Let me know if the problem is still relevant and I can reopen the issue, cheers.


Push error (docker registry v2 storage with oss)

HI,
Dear all.
In my home , i  use nginx+registry v2 + oss(storage) to do the docker registry .
Nginx config like https://github.com/docker/distribution/tree/master/contrib/compose/nginx .
oss config : https://github.com/docker/distribution/blob/master/docs/storage-drivers/oss.md
When i use docker client (1.9) to push the image to the registry v2. With the long time,
client error with this:
# docker push *******/ccms/web-component:1.0-qa-d11271653
The push refers to a repository [xxxxxxx/ccms/web-component] (len: 1)
186204fee35e: Image already exists
6e55de418fa5: Image already exists
602077ec9218: Pushing [==================================================>] 530.4 MB
####more more time ...
Received unexpected HTTP status: 502 Bad Gateway

registy error(some ip domain info i did it):
level=error
msg="client disconnected during blob PATCH"
auth.user.name=admin
environment=staging
go.version=go1.5.2
http.request.host=******
http.request.id=f9adae66-91d4-4d12-9a0f-4a2332471652
http.request.method=PATCH http.request.remoteaddr=****
http.request.uri="/v2/ccms/web-component/blobs/uploads/25ac7aed-a501-406f-ad30-fc2d92e5e5e1?_state=9eALFNBf624Qx7LPqti6DFbKP9W4qdDu1llM_sJkkK57Ik5hbWUiOiJjY21zL3dlYi1jb21wb25lbnQiLCJVVUlEIjoiMjVhYzdhZWQtYTUwMS00MDZmLWFkMzAtZmMyZDkyZTVlNWUxIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDE1LTEyLTE2VDAxOjU2OjA0LjgxOTM0MDQ0NloifQ%3D%3D"
http.request.useragent="docker/1.9.0 go/go1.4.2
git-commit/76d6bc9 kernel/3.10.0-123.el7.x86_64
os/linux arch/amd64"
instance.id=0d962bf3-b611-48cf-8e0c-49c924ff7632
service=registry vars.name="ccms/web-component"
vars.uuid=25ac7aed-a501-406f-ad30-fc2d92e5e5e1
version=v2.2.1

nginx error:
31442#0: *194289 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: xxxxxx, server: xxxx, request: "PATCH /v2/ccms/web-component/blobs/uploads/25ac7aed-a501-406f-ad30-fc2d92e5e5e1?_state=9eALFNBf624Qx7LPqti6DFbKP9W4qdDu1llM_sJkkK57Ik5hbWUiOiJjY21zL3dlYi1jb21wb25lbnQiLCJVVUlEIjoiMjVhYzdhZWQtYTUwMS00MDZmLWFkMzAtZmMyZDkyZTVlNWUxIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDE1LTEyLTE2VDAxOjU2OjA0LjgxOTM0MDQ0NloifQ%3D%3D HTTP/1.1", upstream: "http://<IP_ADDRESS>:5000/v2/ccms/web-component/blobs/uploads/25ac7aed-a501-406f-ad30-fc2d92e5e5e1?_state=9eALFNBf624Qx7LPqti6DFbKP9W4qdDu1llM_sJkkK57Ik5hbWUiOiJjY21zL3dlYi1jb21wb25lbnQiLCJVVUlEIjoiMjVhYzdhZWQtYTUwMS00MDZmLWFkMzAtZmMyZDkyZTVlNWUxIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDE1LTEyLTE2VDAxOjU2OjA0LjgxOTM0MDQ0NloifQ%3D%3D", host: "xxxxxxx"
2015/12/16 09:59:18 [error] 31442#0: *194289 connect() failed (111: Connection refused) while connecting to upstream, client: xxxx, server:xxxxx, request: "PATCH /v2/ccms/web-component/blobs/uploads/25ac7aed-a501-406f-ad30-fc2d92e5e5e1?_state=9eALFNBf624Qx7LPqti6DFbKP9W4qdDu1llM_sJkkK57Ik5hbWUiOiJjY21zL3dlYi1jb21wb25lbnQiLCJVVUlEIjoiMjVhYzdhZWQtYTUwMS00MDZmLWFkMzAtZmMyZDkyZTVlNWUxIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDE1LTEyLTE2VDAxOjU2OjA0LjgxOTM0MDQ0NloifQ%3D%3D HTTP/1.1", upstream: "http://xxxxxx:5000/v2/ccms/web-component/blobs/uploads/25ac7aed-a501-406f-ad30-fc2d92e5e5e1?_state=9eALFNBf624Qx7LPqti6DFbKP9W4qdDu1llM_sJkkK57Ik5hbWUiOiJjY21zL3dlYi1jb21wb25lbnQiLCJVVUlEIjoiMjVhYzdhZWQtYTUwMS00MDZmLWFkMzAtZmMyZDkyZTVlNWUxIiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDE1LTEyLTE2VDAxOjU2OjA0LjgxOTM0MDQ0NloifQ%3D%3D", host: "xxxxxx"

nginx -V
nginx version: nginx/1.9.9
built by gcc 4.4.7 20120313 (Red Hat 4.4.7-16) (GCC)
built with OpenSSL 1.0.1e-fips 11 Feb 2013
TLS SNI support enabled
configure arguments: --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --pid-path=/var/run/nginx.pid --lock-path=/var/run/nginx.lock --http-client-body-temp-path=/var/cache/nginx/client_temp --http-proxy-temp-path=/var/cache/nginx/proxy_temp --http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp --http-uwsgi-temp-path=/var/cache/nginx/uwsgi_temp --http-scgi-temp-path=/var/cache/nginx/scgi_temp --user=nginx --group=nginx --with-http_ssl_module --with-http_realip_module --with-http_addition_module --with-http_sub_module --with-http_dav_module --with-http_flv_module --with-http_mp4_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_random_index_module --with-http_secure_link_module --with-http_stub_status_module --with-mail --with-mail_ssl_module --with-file-aio --with-ipv6 --with-cc-opt='-O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic'

##docker registry version:
registry:2.2.1
#docker version
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:25:01 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:25:01 UTC 2015
 OS/Arch:      linux/amd64

##docker client version:
Client:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   76d6bc9
 Built:        Tue Nov  3 18:00:05 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.0
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   76d6bc9
 Built:        Tue Nov  3 18:00:05 UTC 2015
 OS/Arch:      linux/amd64

nginx config
    upstream registry {
      ip_hash;
      server xxxx1:5000 weight=2;
      server xxxx2:5000 weight=2;
    }

server
        listen       443;
        server_name  xxxxx ;

        ssl                  on;
        ssl_certificate      certs/new/new_ssl_certificate.crt;
        ssl_certificate_key  certs/new/new.key;
        ssl_trusted_certificate certs/new/new_IntermediateCA.crt;
        client_max_body_size 0;  # disable any limits to avoid HTTP 413 for large image uploads
        chunked_transfer_encoding on; # required to avoid HTTP 411: see Issue #1486 (https://github.com/docker/docker/issues/1486)

        access_log  /data/log/nginx/xxxx.access.log  main;
        error_log   /data/log/nginx/xxxxx.error.log ;

        location /v2/ {
            if ($http_user_agent ~ "^(docker\/1\.(3|4|5(?!\.[0-9]-dev))|Go ).*\$" ) {
              return 404;
            }

            proxy_pass http://registry;
            proxy_set_header Host $http_host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_read_timeout                  900;
        }

And i see the push workflow.
For example:
When i push a small image. It have no error stdout, but it .. look like this
7a21760c41c7: Pushed
98783644cfab: Pushing [==================================================>]   202 MB
###This place take more than 2 minutes.
98783644cfab: Pushed

And docker registry logs is this:
time="2015-12-16T06:28:24.715955379Z" level=debug msg="oss.Stat(\"/docker/registry/v2/repositories/test/centos/_uploads/7271b63a-192d-49e8-8e90-e08d23beba40/data\")" auth.user.name=admin environment=staging go.version=go1.5.2 http.request.host=xxxxxxx http.request.id=b01f1e4e-ef1a-44b7-afb6-edb14e6a4a21 http.request.method=PATCH http.request.remoteaddr=xxxxx http.request.uri="/v2/test/centos/blobs/uploads/7271b63a-192d-49e8-8e90-e08d23beba40?_state=pUOFWMoFUbILAMMP-pKqqSkwCL3Qr016jThfmxL-AW57Ik5hbWUiOiJ0ZXN0L2NlbnRvcyIsIlVVSUQiOiI3MjcxYjYzYS0xOTJkLTQ5ZTgtOGU5MC1lMDhkMjNiZWJhNDAiLCJPZmZzZXQiOjAsIlN0YXJ0ZWRBdCI6IjIwMTUtMTItMTZUMDY6MTk6NTguNTk2NTA1ODY2WiJ9" http.request.useragent="docker/1.9.0 go/go1.4.2 git-commit/76d6bc9 kernel/3.10.0-123.9.3.el7.x86_64 os/linux arch/amd64" instance.id=1f809574-bc64-4c7b-9822-e5d780717ce7 service=registry trace.duration=19.953063ms trace.file="/go/src/github.com/docker/distribution/registry/storage/driver/base/base.go" trace.func="github.com/docker/distribution/registry/storage/driver/base.(*Base).Stat" trace.id=ba24be0a-a3d5-48d8-a960-de03af8a1005 trace.line=141 vars.name="test/centos" vars.uuid=7271b63a-192d-49e8-8e90-e08d23beba40 version=v2.2.1

####

time="2015-12-16T06:30:08.789014073Z" level=debug msg="oss.WriteStream(\"/docker/registry/v2/repositories/test/centos/_uploads/7271b63a-192d-49e8-8e90-e08d23beba40/data\", 0)" auth.user.name=admin environment=staging go.version=go1.5.2 http.request.host=xxxxxxxxx http.request.id=b01f1e4e-ef1a-44b7-afb6-edb14e6a4a21 http.request.method=PATCH http.request.remoteaddr=xxxxx http.request.uri="/v2/test/centos/blobs/uploads/7271b63a-192d-49e8-8e90-e08d23beba40?_state=pUOFWMoFUbILAMMP-pKqqSkwCL3Qr016jThfmxL-AW57Ik5hbWUiOiJ0ZXN0L2NlbnRvcyIsIlVVSUQiOiI3MjcxYjYzYS0xOTJkLTQ5ZTgtOGU5MC1lMDhkMjNiZWJhNDAiLCJPZmZzZXQiOjAsIlN0YXJ0ZWRBdCI6IjIwMTUtMTItMTZUMDY6MTk6NTguNTk2NTA1ODY2WiJ9" http.request.useragent="docker/1.9.0 go/go1.4.2 git-commit/76d6bc9 kernel/3.10.0-123.9.3.el7.x86_64 os/linux arch/amd64" instance.id=1f809574-bc64-4c7b-9822-e5d780717ce7 service=registry trace.duration=1m44.069712214s trace.file="/go/src/github.com/docker/distribution/registry/storage/driver/base/base.go" trace.func="github.com/docker/distribution/registry/storage/driver/base.(*Base).WriteStream" trace.id=7c219557-c782-4503-956d-5a362e7b92be trace.line=124 vars.name="test/centos" vars.uuid=7271b63a-192d-49e8-8e90-e08d23beba40 version=v2.2.1
time="2015-12-16T06:30:08.810890861Z" level=debug msg="oss.PutContent(\"/docker/registry/v2/repositories/test/centos/_uploads/7271b63a-192d-49e8-8e90-e08d23beba40/hashstates/sha256/69891299\")" auth.user.name=admin environment=staging go.version=go1.5.2 http.request.host=xxxxxx http.request.id=b01f1e4e-ef1a-44b7-afb6-edb14e6a4a21 http.request.method=PATCH http.request.remoteaddr=xxxxxxx http.request.uri="/v2/test/centos/blobs/uploads/7271b63a-192d-49e8-8e90-e08d23beba40?_state=pUOFWMoFUbILAMMP-pKqqSkwCL3Qr016jThfmxL-AW57Ik5hbWUiOiJ0ZXN0L2NlbnRvcyIsIlVVSUQiOiI3MjcxYjYzYS0xOTJkLTQ5ZTgtOGU5MC1lMDhkMjNiZWJhNDAiLCJPZmZzZXQiOjAsIlN0YXJ0ZWRBdCI6IjIwMTUtMTItMTZUMDY6MTk6NTguNTk2NTA1ODY2WiJ9" http.request.useragent="docker/1.9.0 go/go1.4.2 git-commit/76d6bc9 kernel/3.10.0-123.9.3.el7.x86_64 os/linux arch/amd64" instance.id=1f809574-bc64-4c7b-9822-e5d780717ce7 service=registry trace.duration=21.315531ms trace.file="/go/src/github.com/docker/distribution/registry/storage/driver/base/base.go" trace.func="github.com/docker/distribution/registry/storage/driver/base.(*Base).PutContent" trace.id=1acc164d-e159-4df3-b0ed-65fa16af3557 trace.line=95 vars.name="test/centos" vars.uuid=7271b63a-192d-49e8-8e90-e08d23beba40 version=v2.2.1
time="2015-12-16T06:30:08.811088643Z" level=info msg="response completed" environment=staging go.version=go1.5.2 http.request.host=xxxxxx http.request.id=b01f1e4e-ef1a-44b7-afb6-edb14e6a4a21 http.request.method=PATCH http.request.remoteaddr=xxxxxx http.request.uri="/v2/test/centos/blobs/uploads/7271b63a-192d-49e8-8e90-e08d23beba40?_state=pUOFWMoFUbILAMMP-pKqqSkwCL3Qr016jThfmxL-AW57Ik5hbWUiOiJ0ZXN0L2NlbnRvcyIsIlVVSUQiOiI3MjcxYjYzYS0xOTJkLTQ5ZTgtOGU5MC1lMDhkMjNiZWJhNDAiLCJPZmZzZXQiOjAsIlN0YXJ0ZWRBdCI6IjIwMTUtMTItMTZUMDY6MTk6NTguNTk2NTA1ODY2WiJ9" http.request.useragent="docker/1.9.0 go/go1.4.2 git-commit/76d6bc9 kernel/3.10.0-123.9.3.el7.x86_64 os/linux arch/amd64" http.response.duration=1m44.152749717s http.response.status=202 http.response.written=0 instance.id=1f809574-bc64-4c7b-9822-e5d780717ce7 service=registry version=v2.2.1
<IP_ADDRESS> - - [16/Dec/2015:06:28:24 +0000] "PATCH /v2/test/centos/blobs/uploads/7271b63a-192d-49e8-8e90-e08d23beba40?_state=pUOFWMoFUbILAMMP-pKqqSkwCL3Qr016jThfmxL-AW57Ik5hbWUiOiJ0ZXN0L2NlbnRvcyIsIlVVSUQiOiI3MjcxYjYzYS0xOTJkLTQ5ZTgtOGU5MC1lMDhkMjNiZWJhNDAiLCJPZmZzZXQiOjAsIlN0YXJ0ZWRBdCI6IjIwMTUtMTItMTZUMDY6MTk6NTguNTk2NTA1ODY2WiJ9 HTTP/1.0" 202 0 "" "docker/1.9.0 go/go1.4.2 git-commit/76d6bc9 kernel/3.10.0-123.9.3.el7.x86_64 os/linux arch/amd64"

I don't know at this place . Do you have any idea?

And i try to do this:
[root@xxxx ~]# docker push xxx/ccms/passport:8.2-stage-r10
The push refers to a repository [xxx/ccms/passport] (len: 1)
811c8f125552: Image already exists
b69cd941d720: Pushed
6bf8e9376ba0: Pushed
12c2653c0321: Pushed
2552a96c4679: Pushed
4c970c2e95d9: Pushed
562ef7a97dfa: Pushed
21bca2378e2f: Pushed
6148f4e10592: Pushing [==================================================>] 343.5 MB
####this place i wait long time , So i kill this.
^C
####And i try to do this again:
[root@xxxxx ~]# docker push xxxxx/ccms/passport:8.2-stage-r10
The push refers to a repository [xxxxxx/ccms/passport] (len: 1)
push or pull xxxxxx/ccms/passport is already in progress
####Yes,this place it told me "already in progress",so i think (registry is connect to the oss, and
verify the one of image's layer is ok?). So i wait a moment.

[root@xxxx ~]# docker push xxxxx/ccms/passport:8.2-stage-r10
The push refers to a repository [xxxxxx/ccms/passport] (len: 1)
811c8f125552: Image already exists
b69cd941d720: Image already exists
2552a96c4679: Image already exists
4c970c2e95d9: Image already exists
562ef7a97dfa: Image already exists
21bca2378e2f: Image already exists
6148f4e10592: Pushing [====================================>              ] 250.6 MB/342.1 MB
6148f4e10592: Pushing [====================================>              ] 251.1 MB/342.1 MB
6148f4e10592: Pushing [====================================>              ] 252.2 MB/342.1 MB
6148f4e10592: Pushed
b08b88c6d82a: Pushing [==================================================>] 152.2 MB
##This place , pleace see the “6148f4e10592”. It pushing at 250.6MB. But last action told me it have pushing 343.5MB . So I don't know "registry-->oss" this place have some problem.

cc @denverdino @tg123 @farmerworking

@chendoubao,
From the Nginx configuration, the Nginx will buffer the whole upload request, and then send it to OSS for uploading. That is why you see the uploading progress bar is almost 100% but still need some time to finish the uploading.
From the 502 Bad Gateway,  that means the timeout during nginx -> registry -> OSS,  so in your Nginx configuration, you can add following line to set 15mins timeout setting for uploading
proxy_send_timeout                  900s

One more suggestion is to check the registry version you are using, in 2.2/2.2.1, there are some performance enhancement for uploading the image.
And the OSS driver performance is highly impacted by your networking configurations. If you want to have better performance, it is suggest to setup registry in Aliyun ECS and config the OSS driver to use the intranet mode for access. That will be faster than using the internet.
And FYI, I just submitted one PR #1276  to make the OSS driver support the large image layer over than 1G bytes.
Thanks

@denverdino
Thanks very much.
Later I will test your particular methods.
And i am use the ECS in "聚石塔",  and oss so.
Do you have some like "wangwang qun" to communicate with this?
Haha.

@chendoubao, I sent a email to you for my contact info, pls check. thanks

Dear all,
@stevvooe , I am very sorry to @denverdino , because when i take oss out, only use filesystem, the error also happen. Maybe I wasted a lot of denverdino time .
And here are some stange:
First ,  all linux in an environment.
And i have 2 registry server, here i stop one, and now we called the running one RA, and stoped one RS. Docker version is 1.9.1.
And i have one client, we call it CA.
When i push images on RA or RB , it ok .
Received unexpected HTTP status: 502 Bad Gateway

And i found if the push image  (id like 0bf056161913) is bigger. The 502 error is often happen.
@denverdino said it maybe the nginx's config error, So  now i take the nginx.conf and server.conf here:
###nginx.conf
user  nginx;
worker_processes  2;
error_log  /var/log/nginx/error.log warn;
pid        /var/run/nginx.pid;
worker_rlimit_nofile 51200; # 指定文件描述符数量
events {
   # 使用的网络I/O模型,Linux推荐epoll;FreeBSD推荐kqueue
   use epoll;
   # 允许的最大连接数
   worker_connections  51200;
   multi_accept on;
}
http {
    include       /etc/nginx/mime.types;
    default_type  application/octet-stream;
    log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';
    access_log  /var/log/nginx/access.log  main;
    # 服务器名称哈希表的桶大小,该默认值取决于CPU缓存
    server_names_hash_bucket_size 128;
    # 客户端请求的Header头缓冲区大小
    client_header_buffer_size 32k;
    large_client_header_buffers 4 32k;
    sendfile        on;
    tcp_nopush     on;
    tcp_nodelay     on;
    keepalive_timeout  65;
    #gzip  on;
    #client_max_body_size 3000m;
    #client_body_buffer_size 1024k;
    upstream registry {
      ip_hash;
      server xxxxxxx1:5000 weight=2;
      #server xxxxxxx2:5000 weight=2;
    }
    upstream docker_auth {
      ip_hash;
      server xxxxxxx1:5001 weight=2;
      #server xxxxxxx2:5001 weight=2;
    }
    include /etc/nginx/conf.d/*.conf;
}

#server.conf
    server {
        listen       443;
        server_name  xxxxx ;
        ssl                  on;
        ssl_certificate      certs/new/new_ssl_certificate.crt;
        ssl_certificate_key  certs/new/new.key;
        ssl_trusted_certificate certs/new/new_IntermediateCA.crt;
        client_max_body_size 0;  # disable any limits to avoid HTTP 413 for large image uploads
        chunked_transfer_encoding on; # required to avoid HTTP 411: see Issue #1486 (https://github.com/docker/docker/issues/1486)
        access_log  /data/log/nginx/xxxx.access.log  main;
        error_log   /data/log/nginx/xxxx.error.log ;
        location /v2/ {
            if ($http_user_agent ~ "^(docker\/1\.(3|4|5(?!\.[0-9]-dev))|Go ).*\$" ) {
              return 404;
            }
            proxy_pass http://registry;
            proxy_set_header Host $http_host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_read_timeout                  900s;
            proxy_send_timeout                  900s;
        }
        location /auth {
            proxy_pass https://docker_auth;
            proxy_set_header Host $http_host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
            proxy_read_timeout                  900;
        }
    }

And nginx error log
 [error] 16331#0: *498048 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: <IP_ADDRESS>, server: xxxxx, request: "PATCH /v2/shuyun/registry/blobs/uploads/9a5674d2-919d-44eb-af4e-adadaf3e1976?_state=nXFqde_lIUTw42a1NT2ku2OvRpNXyl4zwULkQyX2xV17Ik5hbWUiOiJzaHV5dW4vcmVnaXN0cnkiLCJVVUlEIjoiOWE1Njc0ZDItOTE5ZC00NGViLWFmNGUtYWRhZGFmM2UxOTc2IiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDE1LTEyLTE3VDA4OjEzOjM4LjYwNTA5ODU3MloifQ%3D%3D HTTP/1.1", upstream: "http://xxxxx:5000/v2/shuyun/registry/blobs/uploads/9a5674d2-919d-44eb-af4e-adadaf3e1976?_state=nXFqde_lIUTw42a1NT2ku2OvRpNXyl4zwULkQyX2xV17Ik5hbWUiOiJzaHV5dW4vcmVnaXN0cnkiLCJVVUlEIjoiOWE1Njc0ZDItOTE5ZC00NGViLWFmNGUtYWRhZGFmM2UxOTc2IiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDE1LTEyLTE3VDA4OjEzOjM4LjYwNTA5ODU3MloifQ%3D%3D", host: "xxxxx"

registry error:
 level=error msg="client disconnected during blob PATCH" auth.user.name=admin environment=staging go.version=go1.5.2 http.request.host=xxx http.request.id=ce8782fb-5be1-4707-acfd-8faa09d297e2 http.request.method=PATCH http.request.remoteaddr=xxxxx http.request.uri="/v2/shuyun/registry/blobs/uploads/9a5674d2-919d-44eb-af4e-adadaf3e1976?_state=nXFqde_lIUTw42a1NT2ku2OvRpNXyl4zwULkQyX2xV17Ik5hbWUiOiJzaHV5dW4vcmVnaXN0cnkiLCJVVUlEIjoiOWE1Njc0ZDItOTE5ZC00NGViLWFmNGUtYWRhZGFmM2UxOTc2IiwiT2Zmc2V0IjowLCJTdGFydGVkQXQiOiIyMDE1LTEyLTE3VDA4OjEzOjM4LjYwNTA5ODU3MloifQ%3D%3D" http.request.useragent="docker/1.9.1 go/go1.4.2 git-commit/a34a1d5 kernel/3.10.0-123.9.3.el7.x86_64 os/linux arch/amd64" instance.id=7b34462d-34f4-4804-88d1-df25d930fe29 service=registry vars.name="shuyun/registry" vars.uuid=9a5674d2-919d-44eb-af4e-adadaf3e1976 version=v2.2.1

Do you have some idea?

Hello, I modify the registry's config: use the tls , So i can make sure the proxy don't modify https-->https.
But the nginx error with this:
[error] 22449#0: *509501 upstream prematurely closed connection while reading response header from upstream

do you have same problem without using nginx as a proxy?

@tg123
HI,I do not understand what you mean.
For denverdino views, he think the problem maybe the nginx proxy configrathon.
And more info, could i contact you by e-mail or other? Because i think maybe we can use chinease. My english level is so bad.

@chendoubao, I also had a lot of problems when using NGINX to do TLS termination.
Have you tried using a TCP stream rather than https? You can TCP stream port 443 to the registry, then configure the registry container to perform the TLS termination. Then you don't have to worry about any of that complex nginx configuration.
Heres a simple example:
stream {
    upstream registry {
        server xxxxxxx1:5000 weight=2;
    }

    server {
        listen 443;
        proxy_pass registry;
    }
}

note: this is outside the http block: stream.

Also, i see you're using an authentication server for token authentication. Do the same thing for that, TCP stream with a vserver listening on 5001, proxy passing to the authentication servers.

@djenriquez
very thanks!!
And i am very sorry,because my company organized an outreach activities . So this two days I have not the Internet . I will test as soon as you approach, very grateful.
@all, thanks

@djenriquez
very thanks, i use TCP stream with nginx, and i think it's ok now.
@tg123 @denverdino I try to use registry without nginx or any proxy , and problem won't have.  At least, i try to push 3 large images , they do not have a problem. And  i will try it tomorrow. thanks!
@stevvooe HI,because i use nginx tcp healthcheck. So my registry have some error like this:
2015/12/21 12:01:17 http: TLS handshake error from xxx:21221: EOF

I don't think the "EOF" what mean. And with the document (https://github.com/docker/distribution/blob/master/docs/configuration.md)， i can't find which can config the log to  stored in some where. And how to config the "EOF" to show full.
Now my config file like this:
version: 0.1
log:
  level: debug
  formatter: json
  fields:
    service: registry
    environment: staging

To other people:
You can config the TCP stream like this:
http://nginx.org/en/docs/stream/ngx_stream_upstream_module.html
When I first started, generating a lot of mistakes. So I think you can config use it. Haha, "stream" and "http" is equal.
And tomorrow I will continue to reply to this post, and will ensure that this test complete.
Thanks.

@chendoubao
From the exception, the problem happens in the Niginx configuration of SSL handshake with registry. It is not related to registry or OSS driver.
For you don't config the SSL certs in registry. Do you configure nginx with SSL termination properly?
Thanks

@denverdino
yes, i think this issue's title is wrong for this problem.
So i am very sorry to OSS.
To your question, i am sure that (nginx_proxy + reigstry's config) config is ok, and when i push large images or at slow network environment, it will have 502 or other error.
 Now when i use (SLB+registry "tcp proxy") or (SLB+nginx+registry "tcp proxy"), it's ok . To errors "2015/12/21 12:01:17 http: TLS handshake error from xxx:21221: EOF" ,i know that's the nginx or slb healthcheck's requests. And that have no error with OSS or other storages.

And i think i must to modify this issue's title. Do you have an idea?

@djenriquez
use tcp proxy ,will have some healthcheck action, and so will have many errors like this:
2015/12/22 02:42:57 http: TLS handshake error from <IP_ADDRESS>:48525: read tcp <IP_ADDRESS>:5000-><IP_ADDRESS>:48525: read: connection reset by peer

How do you solve this?

@chendoubao
Actually, it is logged by go HTTP server impl, and you can provide your logging filter to filter it out.
Thanks

@chendoubao hi, I met the same problem as you have, and I am trying the TCP stream method you mentioned above. However, other than the nginx stream, did you make changes on registry setting? I am asking so, because TCP stream method do not allow the server name part, so I don't know how to visit the registry address by the TCP stream. Thanks.

@chendoubao I just tried TCP stream method with setting auth and tsl inside of the docker config.yml, but I am getting same result as before, stuck at the pushing...

@zzclynn  Have you solved this problem？ How did you do it.

@djenriquez use tcp proxy ,will have some healthcheck action, and so will have many errors like this:
2015/12/22 02:42:57 http: TLS handshake error from <IP_ADDRESS>:48525: read tcp <IP_ADDRESS>:5000-><IP_ADDRESS>:48525: read: connection reset by peer

How do you solve this?

I had the the same problem "502 Bad Gateway" while push image to Harbor with Registy api.
I use Harbor V2.8.0, with its default Registry container "goharbor/registry-photon:v2.8.0",and default Nginx container "goharbor/nginx-photon:v2.8.0" with timeout settings.
When I used use "okhttp3" to request Registry api "/v2/image/blob/upload"(in a Java code snippet), the "502 Bad Gateway" error occured,full response error as follow:

502 Bad Gateway

502 Bad Gateway
nginx

And nginx logs :
2023/04/24 01:49:30 [error] 7#0: *4111 writev() failed (104: Connection reset by peer) while sending request to upstream, client: 172.20.*.*, server: , request: "PATCH /v2/project_name/nginx/blobs/uploads/2c16bfda-12c9-4292-ba85-398b10544a8d?_state=B4vQ64tL8x4tgwzVcDvuW5cBRuW5AdC_-VSFvcGrszN7Ik5hbWUiOiJ3YW5nY2hlbi9uZ2lueCIsIlVVSUQiOiIyYzE2YmZkYS0xMmM5LTQyOTItYmE4NS0zOThiMTA1NDRhOGQiLCJPZmZzZXQiOjMxNDU3MjgwLCJTdGFydGVkQXQiOiIyMDIzLTA0LTI0VDAxOjQ5OjIyWiJ9 HTTP/1.1", upstream: "http://172.21.*.*:8080/v2/project_name/nginx/blobs/uploads/2c16bfda-12c9-4292-ba85-398b10544a8d?_state=B4vQ64tL8x4tgwzVcDvuW5cBRuW5AdC_-VSFvcGrszN7Ik5hbWUiOiJ3YW5nY2hlbi9uZ2lueCIsIlVVSUQiOiIyYzE2YmZkYS0xMmM5LTQyOTItYmE4NS0zOThiMTA1NDRhOGQiLCJPZmZzZXQiOjMxNDU3MjgwLCJTdGFydGVkQXQiOiIyMDIzLTA0LTI0VDAxOjQ5OjIyWiJ9", host: "172.20.*.*"
As the nginx.cnf maybe some sample from docker deploy harbor sample,so i only show part of it.
upstream core {
server core:8080;
}
upstream portal {
server portal:8080;
}
location /v2/ {
proxy_pass http://core/v2/;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $x_forwarded_proto;
proxy_buffering off;
proxy_request_buffering off;
  proxy_connect_timeout 900s;
  proxy_send_timeout 900s;
  proxy_read_timeout 900s;
}

how to solve this problem,someone can help? ＞﹏＜

Closing as oss driver has been deprecated and is no longer supported.


Better documentation

I'm submitting a ...
[ ] bug report
[x] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary
It goes without saying

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

Hi. Interesting project!
I see that it was inspired by ditox, but it would be interesting to know the differences/advantages of this solution.

Hey! Ill include that in the docs but I want it to be here as well.
Ditox is great, but basically the idea was to implement a library that mimics the DI systems of Angular/Nest/Tramvai. So I might consider this as a wrapper around ditox`s system.
The main differences compared to ditox package are:

Different API, it is more constrained overall compared to ditox. In ditox you have to bind everything manually and one-after-another, which I find pretty risky sometimes. @fridgefm/inverter has more constraints when it comes to resolving/providing values.
In inverter you have no ability to dynamically add/remove providers. It is debatable, but for me it is rather a pro - all your providers are either resolved at start or the program simply wont work. In my opinion, in ditox it might come as an unpleasant surprise one day.
Inverter identifies cyclic dependecies and shows you a nice stack. Ditox goes to maximum call stack exceeded error instead.
Conception of modules is different. In inverter it is an entity that adds providers to the container, but in ditox it is rather yet another provider itself.
Inverter does not have react bindings(yet), ditox does.

 There might be some other differences but thats what came to my mind first.


Which version of ASA should be used here?

It looks like the minimum version of ASA is 2.7.0. Is that the version that I should be using?

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

ID: 8d172218-934f-1431-be92-4ad6897a31e9
Version Independent ID: 124f517a-9531-838d-3834-a21f94da9fdb
Content: Install Azure Spatial Anchors for Unity - Azure Spatial Anchors
Content Source: articles/spatial-anchors/how-tos/setup-unity-project.md
Service: azure-spatial-anchors
GitHub Login: @msftradford
Microsoft Alias: parkerra

Related to https://github.com/microsoftdocs/azure-docs/issues/72192
https://github.com/microsoftdocs/azure-docs/issues/72194


Adding rollup 3.15.0 version

 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.Krishna Tejam seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@alexeagle @gregmagolan . Does this look ok?

The addition of the new version looks right but looks like there were breaking changing in this version of rollup that is breaking test cases. By default the rule set tests against the latest version available in versions.bzl.

Sure, I can take a crack at it! Thanks

I need to reopen the PR since my git config is messed up for the first commit and can't sign CLA. Sorry about the trouble.

https://github.com/aspect-build/rules_rollup/pull/71


Currencies under wallet transactions not descriptive

Hi there, the wallet transaction class has a currencies property that returns a map containing all the currencies in that transaction. The key of this map is a string which I believe is the asset id and its value is the quantity. How am I supposed to know what asset this actually is(ticker, actual name) using just this asset id provided?
https://pub.dev/documentation/cardano_wallet_sdk/latest/cardano_wallet_sdk/WalletTransaction/currencies.html

Yes,  the Asset code is somewhat of a half-baked implementation, but there is an implementation. Here is how it works: Every wallet has two tables:
  /// balances of native tokens indexed by assetId
  Map<AssetId, Coin> get currencies;

 /// assets present in this wallet indexed by assetId
  Map<AssetId, CurrencyAsset> get assets;

Whenever a unique native asset is encountered, its CurrencyAsset will be loaded and stored in the assets map. In theory, everything you need to know about a native asset, including its name, ticker, policyId and even the number of decimal places to use when converting it to a floating point number, can be found in the CurrencyAsset. However, in practice, many of the fields are optional, so you may have to supply some of your own metadata in order to create a good user experience.
As far as I'm aware, there is no official CurrencyAsset for ADA, so I just made one up:
///
/// Pseudo ADA asset instance allows principal asset to be treated like other native tokens.
/// Blockfrost returns 'lovelace' as the currency unit, whereas all other native tokens are identified by their assetId, a hex string.
/// For consistency, 'lovelace' unit values must be converted to lovelaceHex strings.
///
final lovelacePseudoAsset = CurrencyAsset(
  policyId: '',
  assetName: lovelaceHex,
  quantity: '45000000000', //max
  initialMintTxHash: '',
  metadata: CurrencyAssetMetadata(
    name: 'Cardano',
    description: 'Principal currency of Cardano',
    ticker: 'ADA',
    url: 'https://cardano.org',
    logo: null,
    decimals: 6,
  ),
);

This is always loaded into the assets map under the lovelaceAssetId constant key, so programmatically you can treat ADA like any other asset. If you need to know if its a native asset or not, there are two CurrencyAsset  properties you can use:
  bool get isNativeToken => assetId != lovelaceAssetId;
  bool get isADA => assetId == lovelaceAssetId;

To be honest, I'm a bit confused as to weather I should just be using 'lovelace' instead of the hex encoded version (used for both lovelaceHex and lovelaceAssetId constants), but if you use the lovelaceAssetId, your code shouldn't break, if I make a change.

I understand what you're saying but we don't have this assets map implemented for transactions. The wallet itself has this and thus I can get all the info I need about assets in said wallet but when it comes to transactions we have just this
/// balances of native tokens indexed by assetId
Map<AssetId, Coin> get currencies;
but I this is needed as well
Map<AssetId, CurrencyAsset> get assets;

No. The framework automatically loads the CurrencyAsset for each native token found in your transactions. You just have to grab it out of the assets map. However, because many of the properties of the CurrencyAsset data structure are optional, you may not have a lot to work with, but I'm giving you everything the blockchain has to give.

But there is no asset map. Here is the API reference https://pub.dev/documentation/cardano_wallet_sdk/latest/cardano_wallet_sdk/WalletTransaction-class.html#instance-properties

The assets property is in the Wallet class:
https://pub.dev/documentation/cardano_wallet_sdk/latest/cardano_wallet_sdk/ReadOnlyWallet-class.html

Yes, it is but i don't think it helps me in my case.For example, let's say i sent 100 ADA and 500 WMT Tokens and 1000 WWW Tokens in a transaction. When I pull up that transaction I have no way of knowing what I sent because I only get an asset id and the quantity(currencies map). This is not the case with just assets that are in my wallet because the Wallet class has the assets property so I can get some metadata(ticker, name) but I'm completely in the dark with transactions. Maybe I'll just have to query blockfrost to get info on these assets.

I guess I'm having trouble understanding your use-case. Barring a bug, if you send WMT or WWW these native tokens will be in your wallet's assets property.  If you're not seeing WMT or WWW metadata, then there is probably a bug in the SDK. If you're expecting to see an assets property in a Transaction, it's not the correct context for this API, transactions are low-level blockchain data.
If I'm still not getting the issue, you're welcome to send me a code example or better yet a unit test. And this does raise a good point, in that the blockchain API needs to be more accessible.

so you're saying If I have a wallet
ReadOnlyWallet? currentWallet;

and I need to get the assets, in the first transaction I can do this?
final assets = currentWallet?.transactions[index].assets;

Because I can't, that's the problem


Center all images for all lists.

We need to center all images for all list. Also we need to change sizes of images all images must be the same size.

@deadcoder0904 Can you do this for JS list?

Can't do it now as I'm working on another project which might take atleast a month's time

@deadcoder0904 Oh, sorry. It's not a problem. Thank you!


Change "Reactive Pure Data" to "Reactive Patch Definition"

Since implementing Pure Data is not the main direction anymore

The result of #61

In new docs, it is done. There are just not yet deployed.


 It includes simple unit tests that are to be fleshed out later on.
Signed-off-by: Steven Bellock<EMAIL_ADDRESS>

@jyao1 I'll follow up this pull request with the Responder's SUPPORTED_EVENT_TYPES.

It seems good to me.


Error message showed in sign in oauth card

Hi team,
We are using
return await stepContext.BeginDialogAsync(nameof(OAuthPrompt), null, cancellationToken); method to use sign in feature for user authentication.
In Waterfall dialog, we start the oauth prompt, in next step validating the token response and send the success message and call the next async method to go to the next dialog to fetch the details. But by the time it fetches the data, error message shows up in the sign in card.
How we can resolve the error message which we get in adaptive card because of the bot delay in fetching the data.

could you provide more details. Still Are you getting the same issue? in which sample you are getting the issue.
Created SignInCard Under resources in AdaptiveCardBot to check the issue. Could you please provide more details?

@Aiswarya1794 Could you provide more details? Are you still experiencing the same issue? If so, which sample is causing the problem?


Bug/callback not on main thread

This PR fixes the following 2 things:

The test cases were not getting compiled due to a linker issue in the Nimble pod
The test cases were getting failed randomly due to concurrent behavior in the RemoteFileWatcher protocol
It not only fixes the test cases but also the expected behaviour from a networking library to get a callback on the main thread.

Code Changes
The callback was executed on the main thread in Remote.swift
The Podfile was updated to have a post-installation script which fixes the linker issue

awesome, thanks for contributing!


CI generated documentation

Documenting the C++ API is possible and currently working, better API documentation is needed but the infrastructure to automatically build and deploy is working.
Generating Julia documentation is not possible at the moment, because there is no libcuda in the CI and is therefore impossible to load the Julia module CompasToolkit and use Documenter.jl.


I forgot the build command

Hi @ronnieoverby,
I discovered that my repository wasn't deploying correctly, because I had forgotten to configure a netlify.toml file with the proper build command and publish directory. If you haven't been able to deploy, that's probably why. This Pull Request includes the changes you need to fix that.
Feel free to create an issue on my repository if it still doesn't work for you.

Thanks for the heads up!