dashd: 12.1.3 -> 12.2.3

Things done

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

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

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

@GrahamcOfBorg build dashd

Failure on x86_64-linux (full log)
Partial log (click to expand)
error: attribute ‘dashd’ in selection path ‘dashd’ not found

Failure on aarch64-linux (full log)
Partial log (click to expand)
error: attribute 'dashd' in selection path 'dashd' not found

Failure on x86_64-darwin (full log)
Partial log (click to expand)
error: attribute 'dashd' in selection path 'dashd' not found

@GrahamcOfBorg build altcoins.dashpay

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘util-linux-2.31.1’ in /Users/graham/nix-borg/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-ndnd/pkgs/os-specific/linux/util-linux/default.nix:71 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)
shrinking /nix/store/1plddy7v2j0s7d4pcxcjylymdxnvwhpy-dashpay-<IP_ADDRESS>/bin/dash-cli
shrinking /nix/store/1plddy7v2j0s7d4pcxcjylymdxnvwhpy-dashpay-<IP_ADDRESS>/bin/dashd
shrinking /nix/store/1plddy7v2j0s7d4pcxcjylymdxnvwhpy-dashpay-<IP_ADDRESS>/bin/bench_dash
shrinking /nix/store/1plddy7v2j0s7d4pcxcjylymdxnvwhpy-dashpay-<IP_ADDRESS>/bin/dash-tx
shrinking /nix/store/1plddy7v2j0s7d4pcxcjylymdxnvwhpy-dashpay-<IP_ADDRESS>/lib/libdashconsensus.so.0.0.0
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/1plddy7v2j0s7d4pcxcjylymdxnvwhpy-dashpay-<IP_ADDRESS>/lib  /nix/store/1plddy7v2j0s7d4pcxcjylymdxnvwhpy-dashpay-<IP_ADDRESS>/bin
patching script interpreter paths in /nix/store/1plddy7v2j0s7d4pcxcjylymdxnvwhpy-dashpay-<IP_ADDRESS>
checking for references to /tmp/nix-build-dashpay-<IP_ADDRESS>.drv-0 in /nix/store/1plddy7v2j0s7d4pcxcjylymdxnvwhpy-dashpay-<IP_ADDRESS>...
/nix/store/1plddy7v2j0s7d4pcxcjylymdxnvwhpy-dashpay-<IP_ADDRESS>

Failure on aarch64-linux (full log)
Partial log (click to expand)
Generated test/data/sighash.json.h
Generated test/data/alertTests.raw.h
  CXX      test/test_test_dash-arith_uint256_tests.o
  CXX      test/test_test_dash-addrman_tests.o
  CXX      test/test_test_dash-alert_tests.o
  CXX      test/test_test_dash-allocator_tests.o
  CXX      test/test_test_dash-base32_tests.o
  CXX      test/test_test_dash-base58_tests.o
building of '/nix/store/kzkr6m07fdwh5qi6m0ls6h7m7jf67v81-dashpay-<IP_ADDRESS>.drv' timed out after 3600 seconds
error: build of '/nix/store/kzkr6m07fdwh5qi6m0ls6h7m7jf67v81-dashpay-<IP_ADDRESS>.drv' failed


Home page not opening / Has some bug

Opening the homepage gives me this -

Maybe I'm doing something wrong. Please reply to this issue if it's okay on someone else's end

Please use '/home'. The Feature has been added.

Issue not fixed. Please create a patch ASAP

Fixed in  commit 4047956. Again use '/home'

Problems with routes still have to be resolved. Just reference this issue and close it when that is done

Closing on @vu29 's behalf  it was resolved before but you can see commit 8704771.


[cs] use short syntax for arrays

In case you don't have some reason for keeping old array, since PHP 5.4 is min version short array can be used.

We do have a reason not to do this yet.
But even if we didn't, change for the sake of change is something we don't do.
Although

What a nice tautology :D sure.


Add new recuring reservation endpoint

🛠 Changelog

Adds a new endpoint for creating a reservation series with its reservations in a since call

Validates that there are no overlapping reservations
Can optionally validate that reservations would fall within opening hours
Can skip certain dates if those dates already have a reservation where one would be created

Refactors existing recurring reservations endpoint to use new serializer and error patterns

🧪 Test plan

Automated tests

🎫 Tickets

TILA-3287

@vergama Can you define which fields for reservations should be definable, if not all?


Depend on prop-types according to docs

Fixes #88
Fixes #89

Codecov Report

Merging #90 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #90   +/-   ##
=======================================
  Coverage   91.89%   91.89%
=======================================
  Files           1        1
  Lines          37       37
  Branches        8        8
=======================================
  Hits           34       34
  Misses          3        3

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 826b01c...7e26330. Read the comment docs.


5.0: optimise installed packages

The current Swift 5.0 Dockerfiles are a continuation of the images shipped in earlier releases.
However, there have been some significant changes to the Linux toolchains in Swift 5.0 which mean we have the opportunity to optimise the system packages that are installed in the images. This will significantly reduce the size of the images, benefitting all users.
Specifically, the following major changes occurred in Swift 5:

Foundation no longer depends on the system ICU but ships its own
The compiler no longer depends on a system clang but ships its own

In addition, we can make a number of other improvements to the images by removing unnecessary packages and only installing those which are genuinely required to build and run Swift programs.
I have spent time working out the actual requirements of the toolchain. I think the following packages are required:
Runtime requirements:

libatomic1 - all Swift programs link this
libbsd0 - all Swift programs link this (for libdispatch)
libcurl4 - Foundation links this
libxml2 - Foundation links this
tzdata - Foundation

Build requirements:

libc6-dev - Compiler
binutils - for gold linker
libgcc-5-dev - Compiler
libstdc++-5-dev - Compiler/stdlib
libedit2 - Package manager
libsqlite3-0 - Package manager
git - Package manager
pkg-config - Package manager
libpython2.7 - REPL

Making these changes has the following effect to image size:

Image
Before
After

16.04
1.69GB
1.37GB

18.04
1.81GB
1.37GB

@hamin @swizzlr @shahmishal @weissi @tomerd @tanner0101 please review.

As far as I tested, produced binary depends on libicu* that installed by apt-get
$ ldd ./.build/x86_64-unknown-linux/release/sourcekitten|grep -i libicu
	libicui18nswift.so.61 => /usr/lib/swift/linux/libicui18nswift.so.61 (0x00007ff313105000)
	libicuucswift.so.61 => /usr/lib/swift/linux/libicuucswift.so.61 (0x00007ff312d2f000)
	libicudataswift.so.61 => /usr/lib/swift/linux/libicudataswift.so.61 (0x00007ff31118a000)
	libicuuc.so.55 => /usr/lib/x86_64-linux-gnu/libicuuc.so.55 (0x00007ff30efee000)
	libicudata.so.55 => /usr/lib/x86_64-linux-gnu/libicudata.so.55 (0x00007ff30b975000)

As far as I tested, produced binary depends on libicu* that installed by apt-get

Sorry, never mind. That is an indirect dependency through libxml2.

@swift-ci test

Thanks @shahmishal. Am I correct that the CI testing currently only tests that the Dockerfiles build and produce an image? It would be good to improve that to then use the image to build and run some Swift programs too. I could take a look at that next week? What do you think?

@ianpartridge Yes, currently we are just building the Docker images part of CI. However, we can easily improve this by adding additional feature to https://github.com/apple/swift-docker/blob/master/ci_test.py

Thanks for the merge 🙂
It would be good to get more confirmation that the new Dockerfiles work for people. I've done some initial Kitura testing, it would be great if @weissi or @tomerd could confirm they are a good base for SwiftNIO, and @tanner0101 for Vapor.


Dev.to in social icons

Thanks for your  beautiful Hugo theme. Can we add dev.to icon?

It's added. You can do this.
params.toml
...
[socialOptions]
  ...
  dev-to = "https://..."


🚀 Jenkins:  Explain Custom JenkinsInfoProvider for new backend system

Plugin Name
jenkins-backend
🔖 Feature description
We need a way to use Custom JenkinsProvider under the new backend system of Backstage.
🎤 Context
My jenkins is set up with scm and I can clearly see the job through the api call, but the default jenkins provider doesn't seem to be able to retrieve the information properly. I need a document that describes how to use a custom jenkins provider to resolve this and how to apply it to a new backend system.
and i want to know what type of jenkins pipeline can be used to the jenkins plugin exactly.
even i don't know how to set jenkins pipeline for viewing the jenkins plugin. this also need guide docs.
✌ Possible Implementation
No response
👀 Have you spent some time to check if this feature request has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

yep, most likely we would need to add an extension point for configuring custom providers. Marking the issue as help wanted.


feat: add examples demo

Changes the TTT example to use new dev UI, adds a README and demos playable in the docs website.

@oblador I get Page Not Found when I try to open the demo


feat: visibility modifiers for any module member

Closes #1083
Summary of Changes
All module members can now have a visibility. This is useful if, say, a class is only used internally for typing.
Pipelines must always be private, which is also the default if no visibility modifier is provided. They can never be referenced anyway, not even in the same file.

:tada: This PR is included in version 0.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
npm package (@latest dist-tag)
v0.14.0
GitHub release

Your semantic-release bot :package::rocket:


[sw/mask_rom] Device measurements for ROM_EXT image signature

It looks like we have an agreement on how to use device measurements when generating and verifying the signature of a ROM_EXT image (as a prefix according to ROM_EXT Manifest Format). We need to finalize this set of measurements and update ROM_EXT tooling and signature verification module.

@silvestrst @asb for visibility.

Closing as obsolete.


False negative "PERCENTAGELAYOUT"

Issue description: In production version of our web, the PERCENTAGELAYOUT is set to false in IE 11. But in development, this value is true. This results in incorrectly set tns-no-subpixel class and broken styles of a carousel in this browser. The function percentageLayout returns different values even though these environments should be same. No other browser has this inconsistency.
The reported width od outer (class .tns-t-ct) from getComputedStyle is 7233.33px, which is clearly subpixel (and same as in Chrome). The problem is, that children has computed width 102.71px in production, but in development, they have 103.33px (again, nearly the same as in Chrome's 103.328px). I have no idea where this inconsistency comes from. As a result, the difference is well over 2 thus returning false.
Although the styles for no subpixel carousel doesn't work correctly, only the first item of carousel can be seen. That is probably caused by flexbox beeing used, so the margins are not processed as expected.
Demo link/slider setting: Settings doesn't affect this bug, since the method percentageLayout doesn't depend on any specific carousel.
Tiny-slider version: 2.8.8, but this code doesn't change in newer versions.
Browser name && version: IE11
OS name && version: Windows 10

Moreover, when I'm looking into this, setting font-size as 0px and then in the child setting to px value is not clean at all 😞 Font zooming in older browsers might get broken with this technique...

I'm having the same issue.
on Localhost tns-subpixel is set. On production environment tns-no-subpixel is set, which also results in an uncorrect layout (IE11 only). Maybe something gets broken during compiling?

same here ... can You please fix this or show a workaround?

@zipper Could you make a demo for this issue? I can't reproduce it on my end.

Moreover, when I'm looking into this, setting font-size as 0px and then in the child setting to px value is not clean at all 😞 Font zooming in older browsers might get broken with this technique...

Which browsers?
Do you have a better solution for this?

I'm having the same issue.
on Localhost tns-subpixel is set. On production environment tns-no-subpixel is set, which also results in an uncorrect layout (IE11 only). Maybe something gets broken during compiling?

We have the same issue. Spinning up a dev environment with typescript, webpack, blablala everything works fine in IE11 and it uses tns-subpixel class.
After building it for production the slider gets rendered in IE11 with tns-no-subpixel.
Nothing fancy. Just a simple ts file doing import { tns } from 'tiny-slider/src/tiny-slider'. Settings as mentioned above have no effect for this bug.
We use the following webpack config if it helps:
const config = {
    mode: isProduction ? 'production' : 'development',
    entry: {
      app: `./${project.appDir}/scripts/main.ts`,
    },
    output: {
      path: path.resolve(__dirname, './.tmp/scripts/'),
      publicPath: 'scripts/',
      filename: '[name].bundle.js',
    },
    module: {
      rules: [
        {
          test: /\.js$/,
          exclude: /node_modules\/(?!(dom7|ssr-window|swiper)\/).*/,
          use: ['babel-loader'],
        },
        {
          test: /\.vue$/,
          loader: 'vue-loader'
        },
        {
          test: /\.ts$/,
          use: [
            {
              loader: 'babel-loader'
            },
            {
              loader: 'ts-loader',
              options: {
                transpileOnly: true,
                appendTsSuffixTo: [
                  '\\.vue$'
                ],
                happyPackMode: false
              }
            }
          ]
        }
      ],
    },
    resolve: {
      extensions: [ '.ts', '.js' ],
      plugins: [
        new TsconfigPathsPlugin()
      ],
      alias: {
        vue$: 'vue/dist/vue.runtime.esm.js'
      }
    },
    plugins: [
      new VueLoaderPlugin(),
      new webpack.ProvidePlugin({
        $: 'jquery'
      }),
      // new BundleAnalyzerPlugin(),
    ]
  };

And this is our simple slider.ts file
import { tns } from 'tiny-slider/src/tiny-slider';

export const sliderControlsText = [
  '',
  '',
];

const offerNewsSliderEl = document.querySelector('.offerNewsSlider');

if (offerNewsSliderEl) {
  const offerNewsSlider = tns({
    container: offerNewsSliderEl,
    controlsText: sliderControlsText,
    items: 1,
    slideBy: 1,
    loop: false,
    nav: true,
    // @ts-ignore
    navPosition: 'bottom',
    gutter: 20,
    responsive: {
      768: {
        items: 2,
        slideBy: 2,
      },
    },
  });
}

I've tried to put together a barebones repo to make it easy to reproduce... But here it gets weird...
If I simply build the sources in our clickdummy in production context and serve them locally from the dist folder everything works as expected.
But when I copy the same built sources (which currently is our "workflow"...) to our CMS (local running VM) the mentioned issue appears.
The HTML of the slides is the same. The md5 hashes of files, the production bundle from the clickdummy and the copied version, match each other.
So there is currently nothing I can do, to provide a reproducable example, because I don't have any clue what could be the difference that causes wrong behaviour.

Hi, @tpinne, we were having the same issue.
I fixed it doing this, when no-subpixel is set:
.tns-horizontal.tns-no-subpixel > .tns-item:not(:first-child){ 	position: absolute; 	top:0; 	left:0; 	bottom:0; }
that seems to fix this issue.

I can confirm all of the above. Is minification of the JS/CSS somehow breaking whatever that subpixel class is using the decide which it uses?


Unit tests for dev-server

Currently, there are absolutely no tests for dev-server. We do test build function which dev-server uses internally but there are other things like looking for changes when a file is changed which are not tested on npm test

We will explore this in #72


Animations from @legendapp/motion throwing error after migrating to nativewind (v2) from tailwindcss-react-native (v1)

Describe the bug
After migrating to nativewind from taildwindcss-react-native, animations from @legendapp/motion seems to still work but now throwing error:

styleq: transform typeof [object Object] is not "string".

To Reproduce
Steps to reproduce the behavior:

add @legendapp/motion library and configure nativewind library (https://www.nativewind.dev/quick-starts/expo)
add  a basic Motion.View component
See error in browser console.

Expected behavior
No error in browser console.
Screenshots

Additional context
Maybe due to @legendapp/motion library still relying on   "tailwindcss-react-native": "^1.3.1" as peerDependencies

Thanks! Yes, it's because of the dependency on the old version. I will try to fix that up this weekend.

Updated in the latest 2.2.0. Let me know if that works better for you?

Updated in the latest 2.2.0. Let me know if that works better for you?

Not sure why,  but I still get the error after updating to latest 2.2.0
Appreciate your help.

@ammarfaris I was never actually able to reproduce the error, just guessed that was the cause. Are you able to share a repo with the error that I can look at? That would help a lot to help me figure out the problem.

I no longer use nativewind for now and i am waiting for nativewind v3 to be released in the future (hopefully) ; then i will try this again. thanks. will close this issue for now.


gradient check of the implementation

Hi @csyben , quick question, did you have a chance to do gradient check using numerical method? Does it pass within certain accuracy?
Best,
Daiqing

Hi,
we did a gradient check at the beginning with the tensorflow methods, and they passed. Currently we are preparing the update towards Tensorflow 2.0 and eager execution support. It is planned to provide the gradient checks with the update.
best,
Christopher

Hey Christopher,
Thank you for your reply! It did not pass when I first test it but later I found out it is the issue of requirement of precisions. Thanks!
Daiqing


validation method is broken when validation is not required

Description
https://github.com/terraform-aws-modules/terraform-aws-acm/commit/a9a3c2394df74de5235f6bbba260f186194c27f8 made validation_method a mandatory variable via variable validation: https://github.com/terraform-aws-modules/terraform-aws-acm/blob/a9a3c2394df74de5235f6bbba260f186194c27f8/variables.tf#L48-L51
We have certificates which were imported into Terraform therfor we didn't have validation_method defined until now.
With the new changes, when setting validation_method = "NONE" the following plan is generated:
Terraform will perform the following actions:

  # module.acm.aws_acm_certificate.this[0] must be replaced
+/- resource "aws_acm_certificate" "this" {
      ~ arn                       = "arn:aws:acm:eu-central-1:xxxx:certificate/xxxx" -> (known after apply)
      ~ domain_validation_options = [] -> (known after apply)
      ~ id                        = "arn:aws:acm:eu-central-1:xxxx:certificate/xxxx" -> (known after apply)
      ~ status                    = "ISSUED" -> (known after apply)
      ~ subject_alternative_names = [] -> (known after apply)
      ~ validation_emails         = [
          -<EMAIL_ADDRESS>        ] -> (known after apply)
      ~ validation_method         = "EMAIL" -> "NONE" # forces replacement
        # (2 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 1 to add, 0 to change, 1 to destroy.

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

Versions

Module version [Required]: 3.4.0

Terraform version: 1.1.7

Provider version(s): AWS 3.64.2

Reproduction Code [Required]
provider "aws" {
  region = var.region
}

module "acm" {
  source  = "terraform-aws-modules/acm/aws"
  version = "3.4.0"

  domain_name               = var.domain_name
  subject_alternative_names = var.subject_alternative_names
  zone_id                   = var.route53_zone_id

  validation_method                  = var.validate_certificate ? "DNS" : "NONE"
  wait_for_validation                = false
  validation_allow_overwrite_records = false

  tags = {
    Name        = var.name
    Provisioner = "terraform"
  }
}

Thanks for reporting this issue!
Email validation is usually happening outside of Terraform and thus it was not implemented by this module. I have updated the module now and verified that it works by running the code in examples/complete-email-validation and by importing created certificate.
validation_method should be set to "EMAIL" to match the imported value.
Fixed in #104

This issue has been resolved in version 3.4.1 :tada:

Hi @antonbabenko,
I think there was a misunderstanding of the issue, I do not want to manage the validation method via terraform, I didn't import it as well.
So my exception when setting validation_method = "NONE" is for no diff in the plan.
As I've mentioned before, we didn't have validation_method defined at all until now because we don't want to manage the validation via terraform.
Using the new release still shows the same diff when setting validation_method = "NONE".

The ACM certificate you have was validated using email. In the plan there is:
~ validation_method         = "EMAIL" -> "NONE" # forces replacement
You need to set validation_method to "EMAIL" to prevent the plan from diffing.

@antonbabenko some of our certificates have DNS validation and the validation was done outside of terraform, in that case the plan will show a diff:
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # module.acm.aws_route53_record.validation[0] will be created
  + resource "aws_route53_record" "validation" {
      + allow_overwrite = false
      + fqdn            = (known after apply)
      + id              = (known after apply)
      + name            = "xxxx"
      + records         = [
          + "xxxx",
        ]
      + ttl             = 60
      + type            = "CNAME"
      + zone_id         = "xxxx"
    }

Plan: 1 to add, 0 to change, 0 to destroy.

In addition, even if there wouldn't be a diff for the DNS validation, it would still require us to go over all of our certificates and add validation_method with the correct value (DNS/EMAIL).
I think a more proper solution would be to revert to the previous behavior which allows not to specify validation_method, either by removing the variable validation for validation_method or by somehow allowing it to be null:
https://github.com/terraform-aws-modules/terraform-aws-acm/blob/a9a3c2394df74de5235f6bbba260f186194c27f8/variables.tf#L48-L51


CON-2260-Update-Available-Mocked-Identifiers-For-Performance-Testing

https://crowncommercialservice.atlassian.net/browse/CON-2260

The failing test (-0.1%, codeclimate), is because I have added a 'Test Identifier' to most endpoints, which is a reusable organisation that users can access with the ID '1111111111', and any valid Scheme, e.g. GB-COH.
This is only for testing purposes and will not be going into production. It will also be being removed, once version 1.0 is released after beta testing. As a result, I do not want to waste time writing tests for something that will be removed and is not going into production.
Thanks


[ISSUE #7340] Abstract Duplicate code into a method in TopicConfigManager

Which Issue(s) This PR Fixes

Fixes #7340
Brief Description

Abstract Duplicate code into a method in TopicConfigManager
How Did You Test This Change?

could you please review this pr? :) @RongtongJin

LGTM.

Codecov Report

Merging #7341 (7cbc96d) into develop (a9e3532) will decrease coverage by 0.01%.
Report is 1 commits behind head on develop.
The diff coverage is 50.00%.

@@              Coverage Diff              @@
##             develop    #7341      +/-   ##
=============================================
- Coverage      42.66%   42.65%   -0.01%
- Complexity      9469     9477       +8
=============================================
  Files           1150     1150
  Lines          82754    82746       -8
  Branches       10789    10783       -6
=============================================
- Hits           35305    35299       -6
- Misses         43035    43038       +3
+ Partials        4414     4409       -5

Files Changed
Coverage Δ

...ache/rocketmq/broker/topic/TopicConfigManager.java
57.06% <50.00%> (+1.81%)
:arrow_up:

... and 16 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Reworking the store implementation

This pull request addresses the issue #5 as well as required features and some cleanups:

move PKCS#11 object lookup from open to load
get rid of the session handle in store context
if the URI does not specify a pin, use the passphrase call-back

This PR will close issue #5.

changes in the force push:

add reporter tag for the first patch
add slot-specific message for the passphrase callback

changes in the force push:

rework the pin callback (token label and slot id in the message)
additional patch info helpers

@ifranzki pls review info helpers and the changes in passphrase-cb.


Setup a pre-commit hook to run ./gradlew sA

The pre-commit hook needs to be setup manually in the local repo.
Check out my version here.


twint.run.Followers() returns "list index out of range [x] feed.Follow" errors before terminating

Initial Check

If the issue is a request please specify that it is a request in the title (Example: [REQUEST] more features). If this is a question regarding 'twint' please specify that it's a question in the title (Example: [QUESTION] What is x?). Please only submit issues related to 'twint'. Thanks.

Make sure you've checked the following:

[x] Python version is 3.6;
[x] Updated Twint with pip3 install --upgrade -e git+https://github.com/twintproject/twint.git@origin/master#egg=twint;
[x] I have searched the issues and there are no duplicates of this issue/question/request.

Command Ran

Please provide the exact command ran including the username/search/code so I may reproduce the issue.

import twint
c = twint.Config()
c.Username = "mseiler1"
twint.run.Followers(c)

Description of Issue
Running the above, a bunch of followers are dispayed, before the program terminates with this:
BickersKnickers
soldiagrl269
list index out of range [x] feed.Follow
ndouthat
hirecube
ScrimpleCoupons
Zoudini
idanbeck
CROTTY
CrottyFarmRepor
cowinkidink
maui2010
kellyhotta
ms_shuangmeng
entryboard
nycbonnie
wiggio
anrahman
BobbyKen
list index out of range [x] feed.Follow

Environment Details
Ubuntu 16.04 LTS

Please check before reporting an issue, thank you for your cooperation!

so, you're saying throwing list index out of range [x] feed.Follow twice is the expected mode of operation?

it sounds like: a) you should not display this error b) you should display a message for successful completion c) you should at least not display it 2 times or some combination of (a), (b), (c).

Every follower has been successfully scraped so, I guess, that there are not "concrete" errors.
Hiding exceptions is not a practice that I think should be implemented (at least not everywhere).
In details, this issue is happening because Twitter is returning 20 users at a time and less are returned when, instead, the same quantity is expected (not on Twint side)


CustomRank admin level will return 0, disallowing kicking/banning regular players

CustomRanks will always return 0, whereas normal players are also 0 so they can not kick or ban regular players.
Regular print = Individual who is given CustomRank attempting to kick
Warn = Target individual, who is a regular player

Need to provide information on how you're applying custom ranks.

CustomRanks are applied through the settings module.
settings.CustomRanks = { 		Government = { 			-- FIRESTONE 			"Group:2803360:150"; -- CCJ 			-- HOMELAND SECURITY 			"Group:2803370:100";  			-- STATE LEGISLATURE 			"Group:2840943:40"; -- SPT 			"Group:2840943:50"; -- PPT 			"Group:2840943:60"; -- PPT 			"Group:2840943:90"; -- LTGOV 			"Group:2840943:100"; -- GOV 			"GetEnveloped" 		} 	};
Then permissions are applied for the new CustomRank:
settings.Permissions = {":s:Creators",":ls:Creators",":gear:Admins",":pm:Government",":n:Government",":m:Government",":h:Government",":setmessage:Government",":kick:Government",":ban:Government",":unban:Government",":tp:Government",":re:Government",":team:Government",":to:Government",":bring:Government",":logs:Government",':sm:Government',":cmds:Government",":admins:Government",":alert:Government",":notify:Government",":slock:Government",":unslock:Government",":shutdown:Government",":age:Government",":view:Government",":unview:Government",":track:Government",":untrack:Government",":refresh:Government",":chatlogs:Government"}

Ah so that's why that was happening.

Just pushed an update. Should resolve this. Reopen if it doesn't.


feat: Share profile feature (#34)

Fixes Issue
resolves #34
Changes proposed
Implemented the feature to share profile
Screenshots

Thank you for the contribution ✨  @Sid-80 and the new features are accepted if they Align with open Grame


perf(utils): utilize axel for faster, multi-threaded downloads (#92)

currently, when I download snapshot from Cloudflare, I have an unstable connection and can't download it at full speed, and I use axel can mitigate the issue.
download progress command changed to du -b because axel will generate a .st file for continue download the file

axel looks good, but very verbosibe.
[ 24%]  .......... .......... .......... .......... ..........  [48311.5KB/s]
[ 24%]  .......... .......... .......... .......... ..........  [48312.6KB/s]
[ 24%]  .......... .......... .......... .......... ..........  [48313.8KB/s]
[ 24%]  .......... .......... .......... .......... ..........  [48313.2KB/s]

While only this should report about progress.
while true ; do sleep 60; echo...

Merged another fix that uses aria2c. Can you see if that works well? If it's good enough then I'll use that, otherwise will explore using a multi-threaded downloader.

close due to already switch to snap sync and arid2c


Added endpoint invocation for revoke handler

We are using Flask-OAuthlib as an OAuth2 provided in our infrastructure. To reduce the weight of hitting our authorization service, we have added caching for user information in other service. However, when a user logs out/revokes their token, we would like to remove the cached information immediately.
To perform this cache bust, we would like to add logic into the revoke_handler endpoint (e.g. send a webhook to other services). Unfortunately, the current implementation doesn't invoke the revoke_handler contents at all. This PR remedies that.
In this PR:

Added endpoint invocation for revoke handler

After some trial/error, we have realized that this approach was flawed for our needs. The revoke_handler will not perform any validation against client_id/client_secret.
On top of that, we attempted to overwrite revoke_handler in OAuth2RequestValidator. However, we yielded a chicken/egg issue with super or would have to copy/paste everything.
Eventually we found that adding our functionality to Token.delete was ideal for our scenario. Sorry for the noisy PR.


README proposal

What do you think about this version of the readme?
I further iteration in my option could be on the documentation of the widget and it's parameters. Do you think we could use tables to show the widgetParams available - personally I find those more visual?

Prop
Type
Default
Description

container
string or HTMLElement
250
The width of the menu and off-canvas transition.

transitionDuration
number
250
The time in ms for the transition.

isMenuOpened
bool
false
Is the menu opened or not.

position
string
"left"
Position the menu to the "left" or "right".

effect
string
"push"
Choose menu effect. "push", "overlay" or "parallax".

Also, should we suggest users to remove the Connector section, or at least keep it minimal here as we use the following one, and don't really create a new one. WDYT?
import { connectSortBy } from 'instantsearch.js/es/connectors';

A table for widgetParams seems clear. IMO we could have a table, and then another section for each param with code examples.

I like what you suggest here.
https://www.algolia.com/
http://twitter.com/alexandrecollin
https://www.linkedin.com/in/alexandrecollin http://github.com/seafoox
Alexandre COLLIN
Data & Program Manager
Solutions GTM & Customer Success
Website: algolia.com https://www.algolia.com/#millisecond-matter
https://www.algolia.com/?utm_campaign=emailsignature_homepage&utm_medium=email_signature&utm_source=email
On Wed, Jun 16, 2021 at 1:44 PM Eunjae Lee @.***> wrote:

A table for widgetParams seems clear. IMO we could have a table, and then
another section for each param with code examples.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/eunjae-lee/js-sort-by/pull/2#issuecomment-862309907,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIM3JAVDGDLVKBHGHKLIZLTTCFAZANCNFSM46ZAPJSQ
.


Unused Schema: shows fields that are used, if at least one argument is unused

Problem Statement
Hello! I have some questions around Unused Schema and the intention. It seems like some of it is a bit misleading from our perspective, because fields that are used are showing up in the list. The intention of the page seems to be a true list of unused schema fields, which isn't true at the moment.
I want to see if it's worth making a fix for it (I am willing to contribute to code+tests).
Let's say we have this in our schema:
Query {
  users(ids: [ID!], email: String!): [User!]!

  type User {
    names: Names!
  }

  type Names {
    name: String!
    nickname: String!
  }
}

And our usages are as follows:
query {
  users(ids: ["1"]) {
    names {
      name
    }
  }
}

From the above, I would expect that users would show as used, but in our data today, since argument email: String! is not used, the line item shows up in the "Unused schema" section:
Query.users(email: String!): [User!]!

Which is I am assuming is saying that email is unused, and though ids is used since it doesn't show up there.
Contributions
I have this PR which I think is on the right track, but I just want to make sure before I proceed further. First PR draft so I want to make sure it's not too far off, or that we agree to the goals listed above!
DRAFT PR: https://github.com/kamilkisiela/graphql-hive/pull/3048
Open Question

Am I understanding the way the "Unused Schema" section works?
Should the fields that are used (with unused arguments) actually be showing up?

Hi, thanks for creating this issues.

Should the fields that are used (with unused arguments) actually be showing up?

I know it’s confusing but how would you show an unused argument without the field?
I did thought about it when implementing this view.
If we don’t display a field the we can’t display an argument, but we could use some form of visual representation of unused field (the field could be of gray colour, or have a line through).
The thing is that we need to show unused arguments otherwise we show only part of the story and detecting unused arguments would be impossible.

how would you show an unused argument without the field?

I was thinking about this too. I think unfortunately it might require a UI change as well to make that a clear distinction.
Potentially, we can somehow make this functionality more clear by each row mentioning which part is unused?
Whether it's the arguments or it's the actual field definition.

A schema coordinate for a field argument would be Query.users(email:).
See https://github.com/graphql/graphql-spec/pull/794/files#diff-be72f083146e025cf29fd9dec772a7f903f50345ef472f451d51af0e6e44f78c

@n1ru4l we're talking about visual representation (the unused schema view).


geconfigurefusionvolume does not exist

The program geconfigurefusionvolume does not seem to exist. In searching the github repo it only ever shows up in this help document for how to add an additional volume to Fusion.
https://www.opengee.org/geedocs/5.3.4/answer/fusionAdministration/manageFusionDiskSpace.html?highlight=geconfigurefusionvolume
I'm guessing the command changed and it should now be
geconfigureassetroot --addvolume  <volume_name>:<dir>  [--assetroot <dir>]

And then on https://www.opengee.org/geedocs/5.3.4/answer/fusionAdministration/commandReference.html?highlight=geconfigureassetroot
the --addvolume text is wrong, its a copy/paste of the --fixmasterhost description

Current release of GEE is 5.3.5
Reference to 5.3.5 docs: http://www.opengee.org/geedocs/5.3.5/answer/fusionAdministration/commandReference.html

Current version of GEE is 5.3.5, although it seems that these issues occur on the newer docs:
https://www.opengee.org/geedocs/5.3.5/answer/fusionAdministration/manageFusionDiskSpace.html?highlight=geconfigurefusionvolume
https://www.opengee.org/geedocs/5.3.5/answer/fusionAdministration/commandReference.html?highlight=geconfigureassetroot

And then on https://www.opengee.org/geedocs/5.3.5/answer/fusionAdministration/confTaskRulesForFusionPerf.html#defining_volumes
It recommends you define a volume using
geconfigureassetroot -- editvolumes


Change "reset setting" to setting-specific action

This PR fixes #122544

Disable workspace trust
View trust-specific settings (Manage trust -> click on the part that says "N workspace settings are not applied")
Click on the gear icon next to any of those settings
✅ The reset action is disabled.

Closing based on offline feedback a while ago.


Fix encoding steps for grid digits

The correct calculation for the least-significant digits is:
4*(latitude % 5) + (longitude % 4)
The previous instructions were:
(latitude % 5) * (longitude % 4)

Hi,
Could you give some advise on how I could implement that into my issue #364 using MSAccess VBA, please?
Many thanks

Hi,
Furthermore, https://github.com/google/open-location-code/blob/master/docs/specification.md still refers to multiplying together, whereas you say it should be added together.
Many thanks

RiverMersey,
You may have had the wrong idea from this pull request. I'm not changing the OLC spec, I'm just fixing the documentation, which was wrong.
I'm also not particularly experienced with Open Location Code. I was looking around this project after following links from a reddit thread. When I read this part of the spec I noticed I was confused; the instructions didn't make sense. So I looked at some of the implementations, and all of them did the same computation, and it wasn't what the instructions said.
The public page is still wrong because my pull hasn't been merged yet.
I can't help you with your MSAccess script, as I know nothing whatsoever about MSAccess. I can suggest that you trust the existing code over the specification document. I updated my earlier comment with links. Your best bet is probably to find a language you're familiar with and translate that code into whatever language your script is in.

@NetworkNode many thanks for your reply!
My only source of reference has been this github. You are entirely correct that the specifications/instructions here for the least significant bytes doesn't make sense - as I suggested in my #364 issue!
My MSAccess VBA code posted there was written by me based on what I've understood from the most significant bytes instructions here.
My hope was to find help in completing that script correctly in MSAccess VBA to include the least significant byte too!
Regards, @RiverMersey


Confusing behavior / sometimes failing validators for semantically equivalent changes.

Area
[?] Plutus Foundation Related to the GHC plugin, Haskell-to-Plutus compiler, on-chain code
[?] Plutus Application Framework Related to the Plutus application backend (PAB), emulator, Plutus libraries
[] Marlowe Related to Marlowe
[] Other Any other topic (Playgrounds, etc.)
Summary
History

We had a working contract and test suite.
Then, we upgraded Plutus to the most recent commit hash 35b1e41b162a5bae87955a86e5eea33535130ff9 (at the time):
Our test suite was then failing (without any change) after the upgrade: input-output-hk/hydra-poc@6255012450728062dbbc13b3fbef49a48385fd49
We upgraded some other parts, and then gave a shot at fixing this test suite starting from:  input-output-hk/hydra-poc@ce6e38c4d7cf70c0e6131ab75b23b238bb334d4a

Making what should be semantically equivalent changes (replacing a truthy expression with True, or changing from and [a,b] to a && b) do change the behavior of the validator in an unpredictable but deterministic way (see below for details).
Some changes made the test suite pass, some made it fail again but without clear reason. This is confusing :/
Steps to reproduce
Starting point
To the reproduce the initial failure, please follow these steps:
$ git clone https://github.com/input-output-hk/hydra-poc/tree/ce6e38c4d7cf70c0e6131ab75b23b238bb334d4a
$ cd hydra-poc
$ nix-shell
$ cabal test hydra-plutus --test-options '-p "Can CollectCom"

1. and -> &&
From there the fun begins... The following diff, makes the test suite pass. Notice that the only change is removing the use of and in favor of multiple inlined &&.  Conditions are still the same and it is fully reproducible. Switching back to and makes the test fail again, and vice-versa.
input-output-hk/hydra-poc@ab45e9e62d2ba5d78720bc828a01a11361a873e8
See here the diff with the contract PIR https://github.com/input-output-hk/hydra-poc/commit/15b43ca975e6064c814b1350bfaef84982de09f1
2. Alternative (equivalent) implementation
That second diff, reverts the previous one but, changes the implementation of our mustForwardParty predicate to (what should be) an equivalent implementation. That is, we are inlining the internals of checkScriptContext with the corresponding code handling the MustSpendAtLeast and MustProduceAtLeast data-constructors.
Changing this makes the test pass.
input-output-hk/hydra-poc@847e72a0a17706543671e46f7848c926ed802eb3
See here the diff with the contract PIR https://github.com/input-output-hk/hydra-poc/commit/66ba442c1350cb43892ad1788a05673ff32fc216
3. Removing a (truthy) predicate

This one is our favorite.

On this diff, we removed one of the predicate on a conjunction. What led us here was the absence of trace ("PT not produced") in the failure from the Emulator. This changes... makes the passing test now fail... ?!?
input-output-hk/hydra-poc@da605c60307d5d75ca5b2e0a71cd8bf2ef3a8929
See here the diff with the contract PIR https://github.com/input-output-hk/hydra-poc/commit/149a8418391a5ba39bebb2b03990e76ac4caa8ff
4. Changing unrelated code
This is even better. Changing an unrelated case in the validator (according to diff (1)) makes the test pass again. Please do notice that the diff is about the Abort branch, which is not executed in the test (which fails on the CollectCom). Changing this was actually a mistake of ours as we intended to change the CollectCom branch, but the results were surprising, if not mind-blowing.
input-output-hk/hydra-poc@e0797accdda4d327a733574664445c7534d3d428
See here the diff with the contract PIR https://github.com/input-output-hk/hydra-poc/commit/43727bfa3052121b6f4dd38cce9c5fc7a427f4c3
Expected behavior
None of these changes should result in different validator behavior (observed from the tests). They are semantically equivalent.
System info (please complete the following information):

OS: NixOS, Ubuntu, Manjaro (everywhere we could try it out).
Version: 21.5, 20-04
Plutus version: 35b1e41b162a5bae87955a86e5eea33535130ff9

Screenshots and attachments

Additional context
Might be related to #3488 & #3601
(cc @ch1bo @abailly-iohk)
Thanks for the help :pray:

When you say the tests pass/fail, do the failures come from script failures, or otherwise? Maybe @j-mueller can help us track this down? Because the scripts don't look too bad right now.

It would be helpful to have the trace log for the script that we expect to pass/fail in each case...

Another useful thing: I have a vague hypothesis that this could be due to differing strictnesses of && and all. We could verify this by putting some trace statements around each of the conditions and seeing whether we get all of them in the log in both cases.
If one of the conditions actually throws an error, but one of && or all is lazy enough not to evaluate it, then that could explain the difference.

When you say the tests pass/fail, do the failures come from script failures, or otherwise?

According to the emulator, the failures comes from the validator which fails to validate the transaction produced by the offchain code.

I have a vague hypothesis that this could be due to differing strictnesses of && and all

How come though? For a conjunction, I'd expect a lazy evaluation to stop at the first falsy value. And, the validator would actually fail on every call no matter what (because one of the element is falsy). But here, we have sometimes passing validators, and sometimes failing ones; To have a validator being evaluated to True, then surely all branches of the conjunction must evaluate to True :thinking:

It would be helpful to have the trace log for the script that we expect to pass/fail in each case...

Here's an example of the (end of the) trace log for the base contract, which fails because of some evaluation error for one of the script output. It complains about pretty much all conditions present in the validator.
Contracts tests
  Hydra Scenarios
    Init > Commit > Commit > CollectCom: Can CollectCom when all parties have submitted: FAIL (0.25s)

[...]

[INFO] Slot 6: 00000000-0000-4000-8000-000000000000 {Contract instance for wallet 1}:
                 Receive endpoint call on 'collectCom' for Object (fromList [("contents",Array [Object (fromList [("getEndpointDescription",String "collectCom")]),Object (fromList [("unEndpointValue",Array [Object (fromList [("getPubKeyHash",String "35dedd2982a03cf39e7dce03c839994ffdec2ec6b04f1cf2d40e61a3")]),Array [Object (fromList [("txOutAddress",Object (fromList [("addressCredential",Object (fromList [("contents",Object (fromList [("getPubKeyHash",String "35dedd2982a03cf39e7dce03c839994ffdec2ec6b04f1cf2d40e61a3")])),("tag",String "PubKeyCredential")])),("addressStakingCredential",Null)])),("txOutDatumHash",Null),("txOutValue",Object (fromList [("getValue",Array [Array [Object (fromList [("unCurrencySymbol",String "")]),Array [Array [Object (fromList [("unTokenName",String "")]),Number 1000.0]]]])]))]),Object (fromList [("txOutAddress",Object (fromList [("addressCredential",Object (fromList [("contents",Object (fromList [("getPubKeyHash",String "977efb35ab621d39dbeb7274ec7795a34708ff4d25a01a1df04c1f27")])),("tag",String "PubKeyCredential")])),("addressStakingCredential",Null)])),("txOutDatumHash",Null),("txOutValue",Object (fromList [("getValue",Array [Array [Object (fromList [("unCurrencySymbol",String "")]),Array [Array [Object (fromList [("unTokenName",String "")]),Number 1000.0]]]])]))])]])])]),("tag",String "ExposeEndpointResp")])
[INFO] Slot 6: W1: Balancing an unbalanced transaction:
                     Tx:
                       Tx 1765d66cf878d1740a43e7fb1f750714e7691a2c07c93deb85c36881fed0034a:
                         {inputs:
                            - 22d479018f5cfeb6255e5f74769958691c6de75fabf00dc84b34f90ad3b4b907!1
                              <>
                            - e6556d453e86605eda29c0a221259cd831a91c1ad18c60f13a12142cb9964074!1
                              <>
                            - ebb0589a32f986407a2b2934a78b02fd03cfba5d289fde7c44a00222621f58cb!1
                              <>
                         collateral inputs:
                         outputs:
                           - Value (Map [(,Map [("",2000)]),(7823198bf3fa55a923f349eda13874c12deb28fa799b604b77430a82,Map [(0x35dedd2982a03cf39e7dce03c839994ffdec2ec6b04f1cf2d40e61a3,1),(0x977efb35ab621d39dbeb7274ec7795a34708ff4d25a01a1df04c1f27,1)])]) addressed to
                             addressed to ScriptCredential: 0d13999069c55537f3bb43f96040182c761c2d93d4b4fb031b9e6cff (no staking credential)
                         mint: Value (Map [])
                         fee: Value (Map [])
                         mps:
                         signatures:
                         validity range: Interval {ivFrom = LowerBound NegInf True, ivTo = UpperBound PosInf True}
                         data:
                           <>
                           <[<<<"\151~\251\&5\171b\GS9\219\235rt\236w\149\163G\b\255M%\160\SUB\GS\240L\US'">,
                           <>>,
                           [<"", [<"", 1000>]>],
                           <>>,
                           <<<"5\222\221)\130\160<\243\158}\206\ETX\200\&9\153O\253\236.\198\176O\FS\242\212\SOa\163">,
                           <>>,
                           [<"", [<"", 1000>]>],
                           <>>]>
                           <<<"\151~\251\&5\171b\GS9\219\235rt\236w\149\163G\b\255M%\160\SUB\GS\240L\US'">,
                           <>>,
                           [<"", [<"", 1000>]>],
                           <>>
                           <<<"5\222\221)\130\160<\243\158}\206\ETX\200\&9\153O\253\236.\198\176O\FS\242\212\SOa\163">,
                           <>>,
                           [<"", [<"", 1000>]>],
                           <>>}
                     Requires signatures:
                       35dedd2982a03cf39e7dce03c839994ffdec2ec6b04f1cf2d40e61a3
                     Utxo index:
                       ( 22d479018f5cfeb6255e5f74769958691c6de75fabf00dc84b34f90ad3b4b907!1
                       , - Value (Map [(,Map [("",1000)]),(7823198bf3fa55a923f349eda13874c12deb28fa799b604b77430a82,Map [(0x35dedd2982a03cf39e7dce03c839994ffdec2ec6b04f1cf2d40e61a3,1)])]) addressed to
                           addressed to ScriptCredential: be5719fcd50b32b8c5b37224c9165f84b881aeb99704ffb183358d1b (no staking credential) )
                       ( e6556d453e86605eda29c0a221259cd831a91c1ad18c60f13a12142cb9964074!1
                       , - Value (Map []) addressed to
                           addressed to ScriptCredential: 0d13999069c55537f3bb43f96040182c761c2d93d4b4fb031b9e6cff (no staking credential) )
                       ( ebb0589a32f986407a2b2934a78b02fd03cfba5d289fde7c44a00222621f58cb!1
                       , - Value (Map [(,Map [("",1000)]),(7823198bf3fa55a923f349eda13874c12deb28fa799b604b77430a82,Map [(0x977efb35ab621d39dbeb7274ec7795a34708ff4d25a01a1df04c1f27,1)])]) addressed to
                           addressed to ScriptCredential: be5719fcd50b32b8c5b37224c9165f84b881aeb99704ffb183358d1b (no staking credential) )
[WARNING] Slot 6: W1: Validation error: Phase2 1765d66cf878d1740a43e7fb1f750714e7691a2c07c93deb85c36881fed0034a: ScriptFailure (EvaluationError ["Missing signature","checkScriptContext failed","Missing datum","checkScriptContext failed","Check has failed"])
[WARNING] Slot 6: 00000000-0000-4000-8000-000000000000 {Contract instance for wallet 1}:
                    Contract instance stopped with error: WalletError (ValidationError (ScriptFailure (EvaluationError ["Missing signature","checkScriptContext failed","Missing datum","checkScriptContext failed","Check has failed"])))
  src/Plutus/Contract/Test.hs:243:
  Init > Commit > Commit > CollectCom: Can CollectCom when all parties have submitted

Changing from and to multiple inlined && makes the test pass:
Contracts tests
  Hydra Scenarios
    Init > Commit > Commit > CollectCom: Can CollectCom when all parties have submitted: OK (0.34s)

Changing it back to and but, inlining of the checkScriptContext in the validator branch makes it fail again with a similar error:
Contracts tests
  Hydra Scenarios
    Init > Commit > Commit > CollectCom: Can CollectCom when all parties have submitted: FAIL (0.24s)

[...]

      [WARNING] Slot 6: W1: Validation error: Phase2 df90f713608a4db280c74edba6be533305cbf72e7ea60b3d05bbdfe4bd12b610: ScriptFailure (EvaluationError ["Missing signature","checkScriptContext failed","Missing datum","checkScriptContext failed","Check has failed"])
      [WARNING] Slot 6: 00000000-0000-4000-8000-000000000000 {Contract instance for wallet 1}:
                          Contract instance stopped with error: WalletError (ValidationError (ScriptFailure (EvaluationError ["Missing signature","checkScriptContext failed","Missing datum","checkScriptContext failed","Check has failed"])))
        src/Plutus/Contract/Test.hs:243:
        Init > Commit > Commit > CollectCom: Can CollectCom when all parties have submitted

After updating plutus to f174d2700e3a4ae9378870b1968521a88f0f2801 (master from yesterday) I do get now a bit more info about errors on our test failures:
      [WARNING] Slot 6: W1: Validation error: Phase2 69e0b9baf815d4316ec26ad97131847d8eb1d8550b2aa46df5a7915c53f40409: ScriptFailure (EvaluationError ["L4","Ld","L2","Ld","Pd"] "CekEvaluationFailure")
      [WARNING] Slot 6: 00000000-0000-4000-8000-000000000000 {Contract instance for wallet 1}:
                          Contract instance stopped with error: WalletError (ValidationError (ScriptFailure (EvaluationError ["L4","Ld","L2","Ld","Pd"] "CekEvaluationFailure")))
        src/Plutus/Contract/Test.hs:241:
        Init > Commit > Commit > CollectCom: Can CollectCom when all parties have submitted

1 out of 1 tests failed (0.19s)
Test suite hydra-plutus-test: FAIL

But what was passing before is not anymore and what was not passing before does work now. For example before rebase, this diff https://github.com/input-output-hk/hydra-poc/commit/4bad81ab3199707c65c9fb62b19f869120970acd was making it pass, but now (rebased) this commit https://github.com/input-output-hk/hydra-poc/commit/a268d573d74b64fed3571f3b343cfa8c141b5a55 does make it fail, i.e. on the previous version True was failing and 1 == 1 was passing, but now it's the other way around.
Working hypothesis of the plutus team: could be ordering issues.

i.e. on the previous version True was failing and 1 == 1 was passing, but now it's the other way around.

WAT?
@KtorZ @ch1bo Did you guys figure out what was going on in the end?

This is really old and given we have had our contracts written and running for a year and half, and we ditched use of trace emulator, PAB, Contract monad, etc. I would suggest to close this issue but @KtorZ might know better.

I've completely lost context of this by now. I believe it was an issue with the emulator and not with the on-chain code.

No clue either. If there is a problem with the plutus core or plutus-tx, we would have ran into this again. Which did not happen.. so I suggest we just close this.

Thanks everyone!


[Bug]: order_list error for functioncall

Check Before Asking

[X] Please check the issue list and confirm this bug is encountered for the first time.
[X] Please try full text in English and attach precise description.

Environment
v0.1.0

Fast Reproduce Steps
select department_id ,  count ( * ),max(gid)  from staff_department_assignments group by department_id order by count ( * )  desc,max(gid)
Actual Behavior
order_list has no gid column
Expected Behavior
No response
Other Information
No response

Thank you for your feedback, but this sql will use count(*) to sort first, and the subsequent gid will not be used. Even if it is order by max(gid), since the gid after group by is unordered, the gid column will not be used for sorting

Yes,you are right, gid must be in projection_column_list?

Yes，projection_column_list = ['department_id', 'count(*)', 'gid']


[feature] more log output option

Is your feature request related to a problem? Please describe.
I want to view the logs in the browser, so I need to write the logs to the mysql database, but the logs in teler-waf can only be output to files. Can you provide more output methods ?
Describe the solution you'd like
provide more output methods
Describe alternatives you've considered
teler.Options Provider custom log output field, like LogOutput, It needs to implement the io.Writer interface
Additional context
no

Are you aware that there's an FalcoSidekickURL option available? Falco Sidekick provides support for various output channels to facilitate the forwarding of teler WAF alerts. See here.

I know this option, but it is not the optimal solution for log output. This requires listening to a new port to process logs. If you provide a log output option and let the user decide how to output, such as outputting to a database, file, syslog, or others (kafka, etc.), this will have a better user experience. Of course, this is just an optional suggestion, teler-waf is already very good

Our decision to utilize Falco Sidekick as an events forwarder, in addition to considering maintenance considerations^1, is grounded in our commitment to prioritizing the in-depth analysis of the http.Request itself, thus enhancing overall performance.
Nevertheless, we are open to exploring the alternative solutions you have suggested for log output. Please submit a proposal for consideration.

I will try to use it


Support Decimal fields

Currently they are being generated as string fields.

I added support for inserting number values into decimal fields.
However, the MySQL driver does return a string for decimal fields, presumably to prevent floating point errors, so there's nothing I can easily do in kysely-codegen. The typing is correct, considering that.


BUG: made behavior of operator equal for CategoricalIndex consistent,…

… improved unit tests
this is a follow-up to https://github.com/pydata/pandas/pull/9947
@jreback

pls add this issue number (the PR) to the same place as in #9947 (just list it in the whatsnew after)

sure, just updated the whatsnew

couple of doc fixes

thanks, updated

@jreback it's green now, please take a look

ty!


Workspace Folders

Description
Users sometimes load multiple projects into the same editor instance, which requires the use of workspace folders to make it work well.
TODO

[ ] credo-language-server
[ ] elixir-tools.nvim support
[ ] elixir-tools.vscode support
[ ] check with @wkirschbaum that it works in emacs

I started looking into it: https://github.com/elixir-tools/credo-language-server/pull/65, but not sure how quickly it will happen.
Some ideas:
We probably want to spin up one runtime per workspace: https://github.com/elixir-tools/credo-language-server/blob/main/lib/credo_language_server.ex#L158 and then use a Registry like next-ls's extensions.


Testing of features and branches

Definitions of Done

[ ] Testing APIs
[ ] Testing Each route

You can test routes by the return codes
You can test the apis by sending requests to the api routes and checking those return codes


Port fix for #112013 to 1.52 release

Ports #112015 to our release branch

After discussion, we decided to hold off on the fix


hides ripples animation in overview mode.

just a simple css fix for hiding ripple animation in overview mode.

Cool! thanks


x/tools/gopls: strange preselected completion for unimported package

gopls version
golang.org/x/tools/gopls v0.13.2
<EMAIL_ADDRESS>h1:Pyvx6MKvatbX3zzZmdGiFRfQZl0ohPlt2sFxO/5j6Ro=

go env
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/icholy/.cache/go-build'
GOENV='/home/icholy/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/icholy/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/icholy/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.21.0'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/tmp/scratch/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build4199407928=/tmp/go-build -gno-record-gcc-switches'

What did you do?
package main

import _ "github.com/aws/aws-sdk-go-v2/service/codebuild"

func main() {
	json.U // <- trigger completion here
}

What did you expect to see?
Suggest json.Unmarshal as pre-selected completion.
What did you see instead?
json.InvalidUTF8Error as pre-selected completion.

Editor and settings
I'm using neovim's built-in lsp client. However, I was able to reproduce this in a vanilla VSCode install with only the Go plugin installed.
Here's the completion response neovim is getting:
{
    id = 10,
    jsonrpc = "2.0",
    result = {
        isIncomplete = true,
        items = {
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"encoding/json',
                        range = {["end"] = {character = 9, line = 3}, start = {character = 9, line = 3}}
                    }
                },
                detail = 'type (from "encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "InvalidUTF8Error",
                insertTextFormat = 2,
                kind = 7,
                label = "InvalidUTF8Error",
                preselect = true,
                sortText = "00000",
                textEdit = {
                    newText = "InvalidUTF8Error",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"encoding/json',
                        range = {["end"] = {character = 9, line = 3}, start = {character = 9, line = 3}}
                    }
                },
                detail = 'type (from "encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "InvalidUnmarshalError",
                insertTextFormat = 2,
                kind = 7,
                label = "InvalidUnmarshalError",
                sortText = "00001",
                textEdit = {
                    newText = "InvalidUnmarshalError",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"encoding/json',
                        range = {["end"] = {character = 9, line = 3}, start = {character = 9, line = 3}}
                    }
                },
                detail = 'func (from "encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "Unmarshal",
                insertTextFormat = 2,
                kind = 3,
                label = "Unmarshal",
                sortText = "00002",
                textEdit = {
                    newText = "Unmarshal(data, v)",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"encoding/json',
                        range = {["end"] = {character = 9, line = 3}, start = {character = 9, line = 3}}
                    }
                },
                detail = 'type (from "encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "UnmarshalFieldError",
                insertTextFormat = 2,
                kind = 7,
                label = "UnmarshalFieldError",
                sortText = "00003",
                textEdit = {
                    newText = "UnmarshalFieldError",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"encoding/json',
                        range = {["end"] = {character = 9, line = 3}, start = {character = 9, line = 3}}
                    }
                },
                detail = 'type (from "encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "UnmarshalTypeError",
                insertTextFormat = 2,
                kind = 7,
                label = "UnmarshalTypeError",
                sortText = "00004",
                textEdit = {
                    newText = "UnmarshalTypeError",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"encoding/json',
                        range = {["end"] = {character = 9, line = 3}, start = {character = 9, line = 3}}
                    }
                },
                detail = 'type (from "encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "Unmarshaler",
                insertTextFormat = 2,
                kind = 7,
                label = "Unmarshaler",
                sortText = "00005",
                textEdit = {
                    newText = "Unmarshaler",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"encoding/json',
                        range = {["end"] = {character = 9, line = 3}, start = {character = 9, line = 3}}
                    }
                },
                detail = 'type (from "encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "UnsupportedTypeError",
                insertTextFormat = 2,
                kind = 7,
                label = "UnsupportedTypeError",
                sortText = "00006",
                textEdit = {
                    newText = "UnsupportedTypeError",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"encoding/json',
                        range = {["end"] = {character = 9, line = 3}, start = {character = 9, line = 3}}
                    }
                },
                detail = 'type (from "encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "UnsupportedValueError",
                insertTextFormat = 2,
                kind = 7,
                label = "UnsupportedValueError",
                sortText = "00007",
                textEdit = {
                    newText = "UnsupportedValueError",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/aws/smithy-go/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = 'func (from "github.com/aws/smithy-go/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "CollectUnknownField",
                insertTextFormat = 2,
                kind = 3,
                label = "CollectUnknownField",
                sortText = "00008",
                textEdit = {
                    newText = "CollectUnknownField(decoder)",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/aws/smithy-go/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = 'func (from "github.com/aws/smithy-go/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "DiscardUnknownField",
                insertTextFormat = 2,
                kind = 3,
                label = "DiscardUnknownField",
                sortText = "00009",
                textEdit = {
                    newText = "DiscardUnknownField(decoder)",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "Uint",
                insertTextFormat = 2,
                kind = 6,
                label = "Uint",
                sortText = "00010",
                textEdit = {
                    newText = "Uint",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "Undefined",
                insertTextFormat = 2,
                kind = 6,
                label = "Undefined",
                sortText = "00011",
                textEdit = {
                    newText = "Undefined",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "Unescape",
                insertTextFormat = 2,
                kind = 6,
                label = "Unescape",
                sortText = "00012",
                textEdit = {
                    newText = "Unescape",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "Unescaped",
                insertTextFormat = 2,
                kind = 6,
                label = "Unescaped",
                sortText = "00013",
                textEdit = {
                    newText = "Unescaped",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "Unmarshal",
                insertTextFormat = 2,
                kind = 6,
                label = "Unmarshal",
                sortText = "00014",
                textEdit = {
                    newText = "Unmarshal",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "UnmarshalFieldError",
                insertTextFormat = 2,
                kind = 6,
                label = "UnmarshalFieldError",
                sortText = "00015",
                textEdit = {
                    newText = "UnmarshalFieldError",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "UnmarshalTypeError",
                insertTextFormat = 2,
                kind = 6,
                label = "UnmarshalTypeError",
                sortText = "00016",
                textEdit = {
                    newText = "UnmarshalTypeError",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "Unmarshaler",
                insertTextFormat = 2,
                kind = 6,
                label = "Unmarshaler",
                sortText = "00017",
                textEdit = {
                    newText = "Unmarshaler",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "UnsupportedTypeError",
                insertTextFormat = 2,
                kind = 6,
                label = "UnsupportedTypeError",
                sortText = "00018",
                textEdit = {
                    newText = "UnsupportedTypeError",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "UnsupportedValueError",
                insertTextFormat = 2,
                kind = 6,
                label = "UnsupportedValueError",
                sortText = "00019",
                textEdit = {
                    newText = "UnsupportedValueError",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "UseNumber",
                insertTextFormat = 2,
                kind = 6,
                label = "UseNumber",
                sortText = "00020",
                textEdit = {
                    newText = "UseNumber",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "AppendUnescape",
                insertTextFormat = 2,
                kind = 6,
                label = "AppendUnescape",
                sortText = "00021",
                textEdit = {
                    newText = "AppendUnescape",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "DisallowUnknownFields",
                insertTextFormat = 2,
                kind = 6,
                label = "DisallowUnknownFields",
                sortText = "00022",
                textEdit = {
                    newText = "DisallowUnknownFields",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "InvalidUTF8Error",
                insertTextFormat = 2,
                kind = 6,
                label = "InvalidUTF8Error",
                sortText = "00023",
                textEdit = {
                    newText = "InvalidUTF8Error",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            },
            {
                additionalTextEdits = {
                    {
                        newText = '"\n\t"github.com/segmentio/encoding/json',
                        range = {["end"] = {character = 51, line = 9}, start = {character = 51, line = 9}}
                    }
                },
                detail = '(from "github.com/segmentio/encoding/json")',
                documentation = {kind = "markdown", value = ""},
                filterText = "InvalidUnmarshalError",
                insertTextFormat = 2,
                kind = 6,
                label = "InvalidUnmarshalError",
                sortText = "00024",
                textEdit = {
                    newText = "InvalidUnmarshalError",
                    range = {["end"] = {character = 7, line = 20}, start = {character = 6, line = 20}}
                }
            }
        }
    }
}

Thanks for the report. I agree this is not correct, and will fix it. Coincidentally, I plan to work on unimported completion this week for https://github.com/golang/go/issues/62665#issuecomment-1722253032. I expect that there is also missing scoring logic, causing this bug, and I'll fix that if I can.


Zoom Level

How do I change the zoom level by the code?

There is nothing like a zoom level. You can zoom to a specified Radius. For example zoom to 200m on the current center:
MapSpan newRegion = MapSpan.FromCenterAndRadius(MapRegion.Center, Distance.FromMeters(200));
And then either set the MapRegion or call MoveToMapRegion.

This may help if you need the zoomlevel:
http://stackoverflow.com/a/21034310
However I find the radius approach more convenient.
Zoom++ should correspond to Radius*=2

Sorry to reply to a closed thread, but I am having some trouble getting this to work is it possible you could provide a more complete example?

That should bring you to Vancouvert, however 200 is very low for a distance, you should try a higher value (like several kilometers to start).

Regardless of what I set it to it too the map moves to near Africa just less zoomed in, is this perhaps a bug?

Maybe you could try that:
var loc = await Plugin.Geolocator.CrossGeolocator.Current.GetPositionAsync(3000);
MainMap.MoveToRegion(MapSpan.FromCenterAndRadius(new Xamarin.Forms.Maps.Position(loc.Latitude, loc.Longitude),
Distance.FromKilometers(10))
);
With the relevant nugget package.
It works fine for me

Stilll does the same thing, when I use stock maps that function worked fine though.


adding wizard steps programmatically

This PR should add the ability to add wizard steps programmatically. Currently it works. However - there is a display error after the TabSheet.Tab has been added: The icon & name is not used (it is blank).

please ignore 8d4bec1 - it is already in master...


[docs][quality]: SDK Reference and API Reference

SDK Reference and API Reference better UI and page structure. Also, the API Reference is absent as of now.

#575 makes sdk reference divided instead of all in a single file as it was previously

#577


Error mappings in currency cells

Error detected in sheet_to_csv and sheet_to_json methods when cells have currency values.
Cells with values like $3.0 are mapped to $2.10 in output of sheet_to_csv and sheet_to_json methods
Attaching test project to reply bug.
currency-problem.zip

I believe that we addressed the problem at some point, the file appears to be properly processed in the web browser and the node script:


v0.1.7

Changes introduced

Upgraded dependencies
Removed leftover console.log
Changed emoji text color from white to black

🎉


Recommend using match instead of let for autoref specialization

The problem with a macro definition such as:
macro_rules! anyhow {
    ($err:expr) => ({
        #[allow(unused_imports)]
        use $crate::{DisplayKind, StdErrorKind};
        let error = $err;
        (&error).anyhow_kind().new(error)
    });
}

Is that it won't work if $err relies on temporaries (e.g. it is format_args!). However, the following will work:
macro_rules! anyhow {
    ($err:expr) => ({
        #[allow(unused_imports)]
        use $crate::{DisplayKind, StdErrorKind};
        match $err {
            error => (&error).anyhow_kind().new(error),
        }
    });
}

as it's just one expression.

Good call, fixed. The reason this didn't come up in the real-world case in anyhow is that anyhow::Error requires a 'static argument for other reasons anyway.


Add support for inherited param handlers

This is a first cut at inherited param handlers. Likely this comes with corner cases, as I'm not an express internals expert, but it appears to work in straightforward cases. An additional parameter for Router is introduced to control this behavior:
var router = express.Router({ inheritParamHandlers: true });

app.param('user', function (req, res, next, id) {
  User.findOne(id, function (err, user) {
    if (err) return next(err);
    req.params.user = user;
    next();
  });
});

router.param('photo', function (req, res, next, id) {
  Photo.findOne(id, function (err, photo) {
    if (err) return next(err);
    req.params.photo = photo;
    next();
  });
});

router.post('/update-tags/:photo', function (req, res) {
  // Error: contrived example
  req.params.user.update(req.params.photo, req.body, function (err) {
    if (err) return res.status(500).json({ status: 'error', error: err.message });
    return res.status(200).json({ status: 'updated' });
  });
});

app.use('/users/:user', router);

I've made it separate from mergeParams, as this may cause unexpected behavior for users if enabled via that option. However, it does enable mergeParams implicitly if used. A case could be made to consolidate the two into a single option which always does both as mergeParams was only publicly documented recently so perhaps the exposure is small.
The parameter handlers are kept in the Router but now follow the request throughout the _router.handle() path. This should allow different behavior if a router is attached to different apps or paths.
This would address issue #2151.

I know this is old, but reviewing the conversation, it was just a question of there is a lack of an API to communicate between routers and this added an internal secret property to do so. Ultimately the implementation of the router has moved to the following repo if anyone is interested in picking this back up there: https://github.com/pillarjs/router
This closure is just cleaning up PRs that are against the moved router implementation.

I have to get going in a moment here... but I was able to functionally extend the Router's constructor and instantiate an extended router here...
Now that I'm re-reading this post, it seems the focus was primarily on the parameters inheritability. While this example
doesn't necessarily include request parameters, I do have access to change and/or inherit from them I think -- when I get back online, I'll take a gander. I believe we're on to something :D
const HTTP = require("http");
const Utility = require("util");

const Framework = require("express");
const Application = Framework();
const Router = Framework.Router;

function extend(source, target) {
    target.prototype = Object.create(source.prototype);
    target.prototype.constructor = new Proxy(target, {
        construct: function (instance, properties) {
            const $ = Object.create(target.prototype);
            this.apply(instance, $, properties);
            return $;
        },
        apply: function (instance, composite, args) {
            source.apply(composite, args);
            instance.apply(composite, args);
        }
    });

    return target.prototype.constructor;
}

const Base = Router();

Base.get("/", async function (request, response, callback = null) {
    const $ = {
        Status: 200,
        Message: "Online",
        Type: "Application/JSON"
    };

    response.type($.Type);
    response.status($.Status);
    response.contentType($.Type);
    response.statusMessage = $.Message;

    (callback) ? await callback() : await response.send();
});

const Inspection = Utility.inspect(Base.prototype, {
    showHidden: true,
    showProxy: true,
    getters: true,
    sorted: true,
    colors: true,

    depth: Infinity
});

console.log("Base Inspection" + ":", Inspection, "\n");

/***
 *
 * @param instance {Router}
 * @param properties {*}
 * @return {import("express").Router}
 *
 * @constructor
 *
 */

const Abstract = (instance, properties) => {
    const $ = extend(instance, async function (request, response) {
        $.prototype = { ... instance, ... properties };
        $.prototype.inspection = Utility.inspect($.prototype, {
            showHidden: true,
            showProxy: true,
            getters: true,
            sorted: true,
            colors: true,

            depth: Infinity
        });

        console.log("Router, Extended Inspection" + ":", $.prototype.inspection, "\n");

        response.send(
            JSON.stringify({
                Data: [ "Attribute-1", "Attribute-2", "Attribute-3" ]
            }, null, 4)
        );
    });

    return $;
};

const Controller = Abstract(Base, {
    Key: "Value",
    Name: "Abstract-Instance",
    Method: () => { return "..."; }
});

Controller.inspection = Utility.inspect(Controller, {
    showHidden: true,
    showProxy: true,
    getters: true,
    sorted: true,
    colors: true,

    depth: Infinity
});

console.log("Proxy Inspection" + ":", Controller.inspection, "\n");

Application.use(Controller);

HTTP.createServer(Application).listen(3000);

Update: I know understand the reference to router - https://github.com/pillarjs/router/tree/2.0. I was looking through recent additions/changes to express, and yeah, that's a dependency.
Sweet. I can imagine you'd like to see merge_params used in some capacity, but more so in an inheritable or composable way.
We'll see what we can do :D

Update: I know understand the reference to router - https://github.com/pillarjs/router/tree/2.0. I was looking through recent additions/changes to express, and yeah, that's a dependency.
Sweet. I can imagine you'd like to see merge_params used in some capacity, but more so in an inheritable or composable way.
We'll see what we can do :D


FABGW-6 Use concurrent go routines for endorsement

Replace the current sequential logic for getting multiple endorsements with concurrent fan-out/fan-in using go routines
Add configurable endorsement timeout option to the global config and pass through to gateway
Signed-off-by: andrew-coleman<EMAIL_ADDRESS>

/ci-run


Add license texts for contents of ecosystem/

Summary

While the contents of ecosystem/ are “merely” pyproject.toml files and one trivial Python script, they are still covered by the licenses of the projects from which they are copied. Not only is maintaining license/copyright statements good practice, but it’s generally specifically required by the particular licenses involved here.
Even though these files are for integration testing only – and therefore do not contribute to the license of the compiled uv executable – they are nevertheless part of the source archive, so distributors and integrators need to consider their license status. For example, I maintain the uv package in Fedora Linux, and I need to consider these licenses because the files would be redistributed in the source RPMs.
Test Plan

N/A – validated by examination of the diff.

I am not sure what to do about prettier complaining about ecosystem/home-assistant-core/LICENSE.md. The license is copied from home-assistant-core upstream, so it should not be modified or reformatted. Maybe I should rename it to ecosystem/home-assistant-core/LICENSE, dropping the somewhat dubious .md extension? That seems safe enough.

There's an ignore file at: https://github.com/astral-sh/uv/blob/main/.prettierignore

Thanks for taking the time to do this. I'll have @BurntSushi review since he added the tests :)

There's an ignore file at: https://github.com/astral-sh/uv/blob/main/.prettierignore

Good suggestion – thanks! I added ecosystem/home-assistant-core/LICENSE.md to .prettierignore.

(I submitted the pretix license – the AGPL-3.0-only portion of which includes a custom exception – for review by Fedora Legal. I’ll follow up in a separate issue if it’s found to be problematic.)

For example, I maintain the uv package in Fedora Linux, and I need to consider these licenses because the files would be redistributed in the source RPMs.

Can you why you're including them in the source RPMs? Why not exclude them?

Can you why you're including them in the source RPMs? Why not exclude them?

The source RPM includes the .spec file that controls how the package is built, the original upstream source archive, and any patches or ancillary files. The original source archive is, e.g., https://github.com/astral-sh/uv/archive/0.2.37/uv-0.2.37.tar.gz (plus three more archives corresponding to the async_zip, pubgrub, and reqwest_middleware forks referenced by git hash in Cargo.toml), and so anything that’s in the git repository is in the source RPM. Note that we do run all of the tests that don’t require network access.
If I wanted to avoid distributing the ecosystem/ directory, I would need to use a script to download the source archive from GitHub, remove ecosystem/, and then repack the source archive. Then, I would need to make sure I skipped running the tests that rely on those files; fortunately, those seem to be contained to crates/uv/tests/ecosystem.rs. All of this is perfectly feasible, and I maintain other packages in Fedora where this approach is necessary, but seems to be a bit of a heavyweight workaround for missing license texts. Alternatively, I might be able to switch to using the PyPI sdist, if it isn’t missing anything else I need.
While I doubt anyone is going to get upset about copying a pyproject.toml file in practice, in principle, maintaining the correct license texts for files copied from other projects and redistributed via GitHub would seem to be something that should matter to the uv project too, regardless of what downstream distribution packagers are doing.

I think any tests involving things in the ecosystem directory are going to involve some kind of network I/O. At least, all extant tests do.

While I doubt anyone is going to get upset about copying a pyproject.toml file in practice, in principle, maintaining the correct license texts for files copied from other projects and redistributed via GitHub would seem to be something that should matter to the uv project too, regardless of what downstream distribution packagers are doing.

I'm not a lawyer, so I'm not going to try to get into legal stuff here, but my mind is more headed in the direction of whether it's worth putting these tests in a different repository. Like, you really should not need to be getting AGPL license exemptions from lawyers in order to package uv. I don't want that to be a hurdle that folks feel like they need to cross, and if putting these tests in this repository provokes that hurdle, it might be something to rethink.
I suppose this is orthogonal to putting the license files in the repo. Since the legal aspect of this doesn't really change if we put them in another repo.

I think your analysis in https://github.com/astral-sh/uv/pull/6181#issuecomment-2296538198 is very reasonable.

If I wanted to avoid distributing the ecosystem/ directory, I would need to use a script to download the source archive from GitHub, remove ecosystem/, and then repack the source archive. Then, I would need to make sure I skipped running the tests that rely on those files; fortunately, those seem to be contained to crates/uv/tests/ecosystem.rs. All of this is perfectly feasible, and I maintain other packages in Fedora where this approach is necessary, but it seems to be a bit of a heavyweight workaround for missing license texts. […]

This – combined with applying this PR as a patch – is the approach I’m using to move forward for now, although I hope it won’t be permanent – either because the pretix license is found to be acceptable for Fedora, or because the contents of ecosystem/ end up being moved out of this repository.

(I submitted the pretix license – the AGPL-3.0-only portion of which includes a custom exception – for review by Fedora Legal. I’ll follow up in a separate issue if it’s found to be problematic.)

Just following up to say that the replacement of pretix with saleor in https://github.com/astral-sh/uv/pull/7567 due to https://github.com/astral-sh/uv/issues/7566 is really helpful, as now everything in ecosystem/ has standard licenses.


Minus sign after decimal point in overview tab and transactions tab

Description
Minus sign shown after decimal point in amounts (tx overview tab and transactions tab). Seems to happen only for very low amounts. Attached screenshot
Screenshot
In overview tab:

In transactions tab:

Version
<IP_ADDRESS> aff772d
Machine specs:

OS: macos 10.14

Fixed in a2ff55af59f25f1bf11c5f3bb7ee257872132d9d