Improve UI of About Page

Issue description
Currently, About Us page on the website is very simple and feels incomplete.
Enhancements proposed

Increase readability and attractiveness of text
Improve images on the page
Add a footer section on the page
Enhance utility of page by adding more buttons and links.

### Tech stack used

HTML
CSS
JavaScript

I am a GSSOC 2022 contributor,
Kindly assign me this issue.

Hi @khushigupta123  I'm a GSSoC'22 contributor.I want to improve the UI of the page .Kindly assign this issue to me.

Hello, I would like to work on this. The About Page can be made more interactive using HTML, CSS and JS.
Please assign this issue to me.

I'm a GSSoC'22 contributor. I want to improve the UI of the page .Kindly assign this issue to me. @SahityaRoy

since whole UI of website is changed I am closing this issue


Version 0.5.0

Avoid publishing unneeded files to npm package.

Landed in https://github.com/metarhia/globalstorage/commit/e33f7f33affbc6d0249840fe6858acd15fc5161c.


Allow the initial phase of a bode plot to be specified

The output of the bode_plot function is bounded to between -180 degrees and 180 degrees and doesn't account for conditions when the phase should leave these ranges. For example a phase angle of -270 degrees will be represented as 90 degrees on the bode plot. To illustrate this, I've got a simple example below:
import control as ct

m = 2
k = 100_000
Wci = 2*np.pi*500

G1 = ct.TransferFunction([1],[m, 0, -k])
G2 = ct.TransferFunction([1], [1/Wci, 1])
G3 = G1*G2

ct.bode_plot([G1, G2, G3], dB = True, Hz = True)

-G1 (blue curve) contains two poles and a DC gain and has a phase angle of -180 degrees.
-G2 (orange curve) is a simple pole with no DC gain and thus has a phase that starts at 0 degrees and goes to -90 degrees
-G3 (green curve) is the product of the two transfer functions which on the bode plot corresponds to adding of the curves. We should see the green curve start at a phase of -180 degrees and go to -270 degrees but it does not do this because of the way that the phase angle is computed.

This has been fixed in PR #494 (currently pending).

This has been fixed in PR #494 (currently pending).

It has already been merged 2 days ago.

It has already been merged 2 days ago.


Feature Request: Option for Silent Output

Kobold has the flag "--quiet" to hide responses in the log. I think Tavern should also have this option, or something similar. As it stands now any computer in the local network can access the TavernAI server and see your chats. Unless you do some firewall shenanigans that 99% of users won't know about. This would also make it easier to run TavernAI on any computer since privacy won't be as much of a  concern.

Planned solution:

Whitelist of ip addresses for server.js functions.
localhost is whitelisted by default.
Ability to disable-enable the whitelist

Commit: https://github.com/TavernAI/TavernAI/commit/0a13b2da5339af33cf602de5d2feef2386608a6d The discussion is transferred here: https://github.com/TavernAI/TavernAI/issues/40


The shape of the minmax.npy file

Hi， I have a few questions.
Is the test_minmax.npy data only containing the maximum and minimum values of the depth map？
could you tell me what its shape is？

Yes, this .npy file saves the maximum and minimum values.


feat: add pod acknowledged time metric

Fixes #N/A
Description
This emits a metric when we consider a pod for scheduling. This will give an accurate representation of when Karpenter actually first considers the pod for scheduling. Currently this would emit for every pod for every scheduling loop, so if a pod fails to schedule, it would be considered again.
How was this change tested?
havent yet
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

4 of 4 (100.0%)  changed or added relevant lines in 2 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.005%) to 80.931%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/disruption/consolidation.go
4
87.25%

Totals

Change from base Build<PHONE_NUMBER>3:
0.005%

Covered Lines:
8518

Relevant Lines:
10525

💛  - Coveralls


Identifying Issue in code with functioning code

Type: Bug
highleting working code with red underline and previously it was working absolutly fine
Extension version: 2022.10.20
VS Code version: Code 1.72.0 (64bbfbf67ada9953918d72e1df2f4d8e537d340e, 2022-10-04T23:20:47.539Z)
OS version: Linux x64 5.15.0-50-generic snap
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 5 3450U with Radeon Vega Mobile Gfx (8 x 2395)

GPU Status
2d_canvas: unavailable_softwarecanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onopengl: disabled_offrasterization: disabled_softwareraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_softwarewebgpu: disabled_off

Load (avg)
2, 2, 2

Memory (System)
5.68GB (1.65GB free)

Process Argv
--no-sandbox --force-user-env --unity-launch --crash-reporter-id aaecdb52-cac3-4267-b866-dfe5941ec134

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
wayland

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pylantcb52:30590119
i497e931:30553904
pyindex848:30577860
nodejswelcome1:30587005
40g7c324:30573242

@ancrahul, can you please provide the error that you are seeing and a code snippet that reproduces the issue?

Same here.. the error varies from case to case. Sometimes a variable i which is part of a for loop (Python) will be red underlined saying i is unbound.

This is one of the examples and this started coming since today. I am connected to my SSH via VSCode.

Same issue here, all my code is was okay 2 days ago, now it shows a lot highlighted errors (that are not actually errors, the code works just fine and they were not highlighted before).

Are you also running the code on SSH?

Same issue here, all my code is was okay 2 days ago, now it shows a lot highlighted errors (that are not actually errors, the code works just fine and they were not highlighted before).

it's not the best fix but I was having the same problem here so I went back to PyLance version 2021.12.2 and the problem was "solved"

Same issue here, all my code is was okay 2 days ago, now it shows a lot highlighted errors (that are not actually errors, the code works just fine and they were not highlighted before).

downgrade to PyLance v2022.8.10

@ReiDoBrega, @williamzerner, @ancrahul, @GonzaloVich, thanks for the reports. The reason you are seeing this is because, we started to roll out a setting change: making the type checking basic by default. Previously, it was off. Type checking helps you find bugs that you might typically miss if you did not have type checking.
To turn it off, if you hover over the {} Python in the toolbar and click Switch to off as shown below.

Based on your feedback we are reviewing whether or not to continue rolling this out. If you have more feedback or questions, please let me know.


please provide updated tutorial for angular 2 final release with modularity

please provide updated tutorial for angular 2 final release with modularity

Done
Urigo/meteor-angular2.0-socially@db14ce0

and deployed - https://www.angular-meteor.com/


fix: Ensure parity of behavior between testing with/without --test-alembic.

Fixes https://github.com/schireson/pytest-alembic/issues/79

Installed with pip install git+https://github.com/schireson/pytest-alembic.git@dc/manual-vs-automatic-parity and ran test with an additional model (so failure guaranteed): Worked and looks nice, thank you!


Client-side scalability across hundreds of devices on same IP address

I'd love to be able to use is-online in my application, however I want to ask a question to  make sure that it will be a good fit with regards to scalability.
Please consider the following use case:

This package runs on an IoT device. When the device starts up the application, it runs a check to determine if the internet is reachable. The way I understand this package to work is that it runs 3 http requests and returns true if any of the requests succeed. Now imagine that at any given  physical location, there are 100 devices that all start the application at the same time every morning.

I'm worried that any of those 3 urls could see 100 requests coming from the same IP and treat the traffic as a DDoS attack and blacklist said IP address. Then this package would, understandably, return a false negative.
Have there been any reports of this kind of issue happening in similar environments?

I assume you're going to use it in Node.js/Electron. There are actually 5 checks, and all of them would have to fail to cause a false negative. One of the checks uses the same endpoint as iOS, which means it should be scalable as there are millions of iOS devices. I doubt the Apple captive check nor the DNS checks would blacklist the devices, as they're used to handling a huge amount of requests.
However, if this is still not good enough for you:

You could assign a unique IP to each device.
You could fix https://github.com/sindresorhus/is-online/issues/61
You could do your own backup check using https://github.com/sindresorhus/public-ip#fallbackurls, even host your own https://github.com/rdegges/ipify-api server.


Operation cannot be fulfilled on gitrepos.fleet.cattle.io

What kind of request is this (question/bug/enhancement/feature request): Bug
Steps to reproduce (least amount of steps as possible):

Create a cluster
Access to Explorer and then Continuous Delivery
Configure a git Repo with watch to a branch or a revision and save
edit the git Repo configuration editing the branche name or the revision

Result:
Operation cannot be fulfilled on gitrepos.fleet.cattle.io "project-name": the object has been modified; please apply your changes to the latest version and try again
Other details that may be helpful:

I just ran into this same issue.  The problem seems be intermittent and browser specific.
I am using Rancher 2.5.8 and browser Firefox 89.0.2 on OpenSUSE Tumbleweed.  When I tried this same operation on Vivaldi 4.0.2312.38, the issue was not there.

I a running into the same issue, I am running on MacOS Big Sur, Firefox 89.0.2 and Chrome 91.0.4472.114.  Safari is un-useable for Rancher (just get a blank screen).  I also got the error on Vivaldi 4.0.2312.38 on MacOS.

This should be resolved by https://github.com/rancher/dashboard/issues/1324

Still getting an error if i'm too slow
Adding the pollingInterval in this case... which works if im fast enough...
After adding the higher pollingInterval i can edit the repo without problems...
So it seems this is not resolved by https://github.com/rancher/dashboard/issues/1324
Rancher 2.6.3-patch1


Terraform show doesn't show

Describe the bug
When running Terraform show via a Devops release pipeline, no output is produced, past generic warnings.
As an example, the below output is received - I can see a destroy will occur, but where is the actual output from terraform show?
To Reproduce
Steps to reproduce the behavior:

Setup pipeline as
Execute pipeline
See logs below

Expected behavior
A human-readable output in the logs for the terraform show step
Pipeline Logs
2021-06-23T10:17:49.8546136Z ##[debug]Evaluating condition for step: 'terraform show'
2021-06-23T10:17:49.8548074Z ##[debug]Evaluating: succeeded()
2021-06-23T10:17:49.8548578Z ##[debug]Evaluating succeeded:
2021-06-23T10:17:49.8549696Z ##[debug]=> True
2021-06-23T10:17:49.8550348Z ##[debug]Result: True
2021-06-23T10:17:49.8551093Z ##[section]Starting: terraform show
2021-06-23T10:17:49.8664654Z ==============================================================================
2021-06-23T10:17:49.8664964Z Task         : Terraform CLI
2021-06-23T10:17:49.8665228Z Description  : Execute terraform cli commands
2021-06-23T10:17:49.8665454Z Version      : 0.6.25
2021-06-23T10:17:49.8665662Z Author       : Charles Zipp
2021-06-23T10:17:49.8665862Z Help         :
2021-06-23T10:17:49.8666138Z ==============================================================================
2021-06-23T10:17:49.8720848Z ##[debug]Using node path: C:\agents\2.187.2\externals\node\bin\node.exe
2021-06-23T10:17:50.0733662Z ##[debug]agent.TempDirectory=D:\a\_temp
2021-06-23T10:17:50.1088397Z ##[debug]loading inputs and endpoints
2021-06-23T10:17:50.1095139Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2021-06-23T10:17:50.1095814Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2021-06-23T10:17:50.1128665Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2021-06-23T10:17:50.1129331Z ##[debug]loading INPUT_AIINSTRUMENTATIONKEY
2021-06-23T10:17:50.1137317Z ##[debug]loading INPUT_ALLOWTELEMETRYCOLLECTION
2021-06-23T10:17:50.1138430Z ##[debug]loading INPUT_BACKENDAZURERMSTORAGEACCOUNTSKU
2021-06-23T10:17:50.1139449Z ##[debug]loading INPUT_BACKENDTYPE
2021-06-23T10:17:50.1139956Z ##[debug]loading INPUT_COMMAND
2021-06-23T10:17:50.1150959Z ##[debug]loading INPUT_COMMANDOPTIONS
2021-06-23T10:17:50.1151534Z ##[debug]loading INPUT_ENSUREBACKEND
2021-06-23T10:17:50.1152546Z ##[debug]loading INPUT_INPUTTARGETPLANORSTATEFILEPATH
2021-06-23T10:17:50.1153188Z ##[debug]loading INPUT_RUNAZLOGIN
2021-06-23T10:17:50.1154988Z ##[debug]loading INPUT_WORKINGDIRECTORY
2021-06-23T10:17:50.1155680Z ##[debug]loading INPUT_WORKSPACESUBCOMMAND
2021-06-23T10:17:50.1156561Z ##[debug]loaded 14
2021-06-23T10:17:50.1157033Z ##[debug]Agent.ProxyUrl=undefined
2021-06-23T10:17:50.1157927Z ##[debug]Agent.CAInfo=undefined
2021-06-23T10:17:50.1158550Z ##[debug]Agent.ClientCert=undefined
2021-06-23T10:17:50.1168185Z ##[debug]Agent.SkipCertValidation=undefined
2021-06-23T10:17:50.3865447Z ##[debug]allowTelemetryCollection=false
2021-06-23T10:17:50.3866945Z ##[debug]System.TeamFoundationCollectionUri=https://dev.azure.com/medicalprotection/
2021-06-23T10:17:50.3872770Z ##[debug]SYSTEMVSSCONNECTION auth param ACCESSTOKEN = ***
2021-06-23T10:17:50.3873511Z ##[debug]Agent.ProxyUrl=undefined
2021-06-23T10:17:50.3909472Z ##[debug]command=show
2021-06-23T10:17:50.3911466Z ##[debug]command=show
2021-06-23T10:17:50.3917463Z ##[debug]workingDirectory=D:\a\r1\a\Terraform-Recovery-Services-Composition\drop
2021-06-23T10:17:50.3924036Z ##[debug]which 'terraform'
2021-06-23T10:17:50.3932065Z ##[debug]found: 'C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe'
2021-06-23T10:17:50.3933757Z ##[debug]which 'C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe'
2021-06-23T10:17:50.3936420Z ##[debug]found: 'C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe'
2021-06-23T10:17:50.3938875Z ##[debug]C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe arg: version
2021-06-23T10:17:50.3943689Z ##[debug]exec tool: C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe
2021-06-23T10:17:50.3944373Z ##[debug]arguments:
2021-06-23T10:17:50.3944921Z ##[debug]   version
2021-06-23T10:17:50.3951189Z [command]C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe version
2021-06-23T10:17:50.5199712Z Terraform v1.0.0
2021-06-23T10:17:50.5208403Z on windows_amd64
2021-06-23T10:17:50.5250496Z + provider registry.terraform.io/hashicorp/azurerm v2.64.0
2021-06-23T10:17:50.5251977Z + provider registry.terraform.io/hashicorp/random v3.1.0
2021-06-23T10:17:50.5253397Z
2021-06-23T10:17:50.5254132Z ##[debug]Exit code 0 received from tool 'C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe'
2021-06-23T10:17:50.5407482Z ##[debug]STDIO streams have closed for tool 'C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe'
2021-06-23T10:17:50.5408999Z ##[debug]command=show
2021-06-23T10:17:50.5540842Z ##[debug]secureVarsFile=undefined
2021-06-23T10:17:50.5543211Z ##[debug]secureVarsFile=undefined
2021-06-23T10:17:50.5544161Z ##[debug]secure file name for id undefined = undefined
2021-06-23T10:17:50.5573128Z ##[debug]commandOptions=-no-color
2021-06-23T10:17:50.5574198Z ##[debug]commandOptions=-no-color
2021-06-23T10:17:50.5576157Z ##[debug]inputTargetPlanOrStateFilePath=D:\a\r1\a/Terraform-Recovery-Services-Composition/drop/plan.tfplan
2021-06-23T10:17:50.5577157Z ##[debug]command=show
2021-06-23T10:17:50.5577921Z ##[debug]workingDirectory=D:\a\r1\a\Terraform-Recovery-Services-Composition\drop
2021-06-23T10:17:50.5578751Z ##[debug]which 'terraform'
2021-06-23T10:17:50.5579545Z ##[debug]found: 'C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe'
2021-06-23T10:17:50.5580365Z ##[debug]which 'C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe'
2021-06-23T10:17:50.5581140Z ##[debug]found: 'C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe'
2021-06-23T10:17:50.5582031Z ##[debug]C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe arg: show
2021-06-23T10:17:50.5584633Z ##[debug]C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe arg: -json
2021-06-23T10:17:50.5587280Z ##[debug]C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe arg: -no-color
2021-06-23T10:17:50.5588284Z ##[debug]C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe arg: D:\a\r1\a/Terraform-Recovery-Services-Composition/drop/plan.tfplan
2021-06-23T10:17:50.5589216Z ##[debug]exec tool: C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe
2021-06-23T10:17:50.5589949Z ##[debug]arguments:
2021-06-23T10:17:50.5590613Z ##[debug]   show
2021-06-23T10:17:50.5591249Z ##[debug]   -json
2021-06-23T10:17:50.5592202Z ##[debug]   -no-color
2021-06-23T10:17:50.5593007Z ##[debug]   D:\a\r1\a/Terraform-Recovery-Services-Composition/drop/plan.tfplan
2021-06-23T10:17:52.4319311Z ##[debug]Exit code 0 received from tool 'C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe'
2021-06-23T10:17:52.4324808Z ##[debug]STDIO streams have closed for tool 'C:\hostedtoolcache\windows\terraform\1.0.0\x64\terraform.exe'
2021-06-23T10:17:52.4332854Z ##[debug]inputTargetPlanOrStateFilePath=D:\a\r1\a/Terraform-Recovery-Services-Composition/drop/plan.tfplan
2021-06-23T10:17:52.4334402Z ##[debug]inputTargetPlanOrStateFilePath=D:\a\r1\a/Terraform-Recovery-Services-Composition/drop/plan.tfplan
2021-06-23T10:17:52.4370694Z ##[debug]set TERRAFORM_PLAN_HAS_DESTROY_CHANGES=true
2021-06-23T10:17:52.4373275Z ##[debug]Processed: ##vso[task.setvariable variable=TERRAFORM_PLAN_HAS_DESTROY_CHANGES;isOutput=false;issecret=false;]true
2021-06-23T10:17:52.4374224Z ##[debug]set vso[task.setvariable variable=TERRAFORM_PLAN_HAS_DESTROY_CHANGES] to true
2021-06-23T10:17:52.4402396Z ##[warning]Destroy detected!
2021-06-23T10:17:52.4411444Z ##[debug]Processed: ##vso[task.issue type=warning;]Destroy detected!
2021-06-23T10:17:52.4413970Z ##[debug]allowTelemetryCollection=false
2021-06-23T10:17:52.4415111Z ##[debug]command=show
2021-06-23T10:17:52.4415680Z ##[debug]command=show
2021-06-23T10:17:52.4416238Z ##[debug]executed command 'show'
2021-06-23T10:17:52.4417018Z ##[debug]set TERRAFORM_LAST_EXITCODE=0
2021-06-23T10:17:52.4420641Z ##[debug]Processed: ##vso[task.setvariable variable=TERRAFORM_LAST_EXITCODE;isOutput=false;issecret=false;]0
2021-06-23T10:17:52.4453426Z ##[section]Finishing: terraform show

Agent Configuration

OS: vs2017-win2016
Hosted
Terraform version used: 1.0.0
AzureCLI version used: default

Additional context
Our plan files are being produced at build phase - the file is then contained in an artifact and released via a release pipeline - I want a manual intervention in the release pipeline to check the output of terraform show.

@GeorgePalacios, show was never intended to display the plan file in a human readable format. It was only implemented to detect destroy operations. Therefore, all that it currently does is run silently (nothing written to stdout) and set a pipeline variable. At the time this was implemented, it was decided to run show silently due to the risk of exposing secrets/sensitive values in the build logs. This behavior is by design.
I would be willing to reconsider this if the human readable output can be access controlled  and deleted. See also #60. The build logs will likely not redact secrets or sensitive values given the fact its coming from a third party binary. Would you be ok with show revealing secrets or are there some conditions where you would believe this to be ok?

https://www.hashicorp.com/blog/terraform-0-14-adds-the-ability-to-redact-sensitive-values-in-console-output
I assumed this could be used.
On Wed, Jul 21, 2021 at 2:43 PM Charles Zipp @.***>
wrote:

@GeorgePalacios https://github.com/GeorgePalacios, show was never
intended to display the plan file in a human readable format. It was only
implemented to detect destroy operations. Therefore, all that it currently
does is run silently (nothing written to stdout) and set a pipeline
variable. At the time this was implemented, it was decided to run show
silently due to the risk of exposing secrets/sensitive values in the build
logs. This behavior is by design.
I would be willing to reconsider this if the human readable output can be
access controlled and deleted. See also #60
https://github.com/charleszipp/azure-pipelines-tasks-terraform/issues/60.
The build logs will likely not redact secrets or sensitive values given the
fact its coming from a third party binary. Would you be ok with show
revealing secrets or are there some conditions where you would believe this
to be ok?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/charleszipp/azure-pipelines-tasks-terraform/issues/59#issuecomment-884200361,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHHCHM6IEGZCH3U3HDFOS3DTY3FG3ANCNFSM47FP7WXA
.

terraform show is for processing plan files.  The plan command already shows this output and if publishPlanResult will cause the same to be written to a tab on the build summary.


Add chai matchers for Solidity 0.8.4 custom errors

Yes, please!

+1

Hardhat added support for custom errors in the v2.4.0 release. Thus an interrim solution for Waffle users is the following:
await expect(myContract.myFunction()).to.be.revertedWith("MyCustomError");

I would expect a more idiosyncratic chai matcher if Waffle is to implement this, but the above should be good enough for now.

Hardhat added support for custom errors in the v2.4.0 release. Thus an interrim solution for Waffle users is the following:
await expect(myContract.myFunction()).to.be.revertedWith("MyCustomError");

I would expect a more idiosyncratic chai matcher if Waffle is to implement this, but the above should be good enough for now. This is the full string that Hardhat emits:

Error: VM Exception while processing transaction: reverted with custom error 'MyCustomError()'

@marekkirejczyk Is this already in the roadmap for 4.0?

that would be amazing!

Hardhat added support for custom errors in the v2.4.0 release. Thus an interrim solution for Waffle users is the following:
await expect(myContract.myFunction()).to.be.revertedWith("MyCustomError");

I would expect a more idiosyncratic chai matcher if Waffle is to implement this, but the above should be good enough for now. This is the full string that Hardhat emits:

Error: VM Exception while processing transaction: reverted with custom error 'MyCustomError()'

Is there a way to check the value for the error if you are returning?
AssertionError: Expected transaction to be reverted with Unauthorized("!ADMIN"),
but other exception was thrown: Error:
VM Exception while processing transaction: reverted with custom error 'Unauthorized("!ADMIN")'

// where the assert is:
....method..to.be.revertedWith('Unauthorized("!ADMIN")');

Just doing the error name on its own is fine, but you might want some more fine grained checks in place. Errors seem great but its not great if you wanted to make the errors a little more descriptive, rather than throwing in loads of specific error types for each scenario.

Hey @michaeljohnbennett, does it work if you escape the double quotes?
....method..to.be.revertedWith("Unauthorized(\"!ADMIN\")");

ok I see. so you would have a multitude of error types for all those cases and 0 strings?
I can understand gas efficiency but then your going to have to have some kind of mapping in external code to understand or give you users some meaningful message, don't you think thats an added complexity?
I thought the whole purpose of an error object was to tell someone an error had occurred and some meaningful text/message to tell them more or less what happened.
Strangely after further testing this afternoon on a hardhat-deploy templated project it does work for the message value being emitted and not picking up the error wrapper. But this behaviour seems to change sometimes, randomly.
I will clean my node_modules down and try fresh and see how I go.
Thanks again for the reply @paulrberg , appreciated as always. 👍🏻

ok I see. so you would have a multitude of error types for all those cases and 0 strings?

Yes, that is what I do. Here's  a list of projects I built or contributed to that use 100% only custom errors:

https://github.com/hifi-finance/prb-math
https://github.com/paulrberg/contracts (see Ownable and Erc20)
https://github.com/hifi-finance/hifi (in particular see the protocol package)

I can understand gas efficiency but then your going to have to have some kind of mapping in external code to understand or give you users some meaningful message, don't you think thats an added complexity?

It's not. The Ethereum ecosystem will sooner or later support custom errors across the board. For instance, I know that Etherscan is working on decoding custom errors and displaying the actual error name when a transaction fails.

I thought the whole purpose of an error object was to tell someone an error had occurred and some meaningful text/message to tell them more or less what happened.

Now the custom error themselves is the "text/message" that tells the user what happened. Did you read the announcement post?
Though custom errors need not have zero arguments. Sometimes you may want to log the function inputs, but usually those are uint256. See the projects referenced above.

I agree with @paulrberg. Custom errors will soon be widely used across the Ethereum smart contracts and Dapp ecosystem.
I have found a current work around to make sure the parameters inside the custom error match, until Waffle implement this.
MyCustomError(address _address, string _string);

const customRevertErrorMessage =
      "VM Exception while processing transaction: reverted with custom error";

it("should revert with MyCustomError and correct parameters", async () => {
    const expectedErrorParam1 = "0xcafecafecafecafecafecafecafecafecafecafe";
    const expectedErrorParam2 = "Some String";

    try {
        await myContract.myFunction()
    } catch (error) {
        expect(error.message).toMatch(
            `${customRevertErrorMessage} 'MyCustomError("${expectedErrorParam1}", "${expectedErrorParam2}")'`
        )
    }
})

NB: don't forget the single quotes between MyCustomError in the message inside .toMatch().
So ✅
VM Exception while processing transaction: reverted with custom error 'MyCustomErrror(...)'

Not ❌
VM Exception while processing transaction: reverted with custom error MyCustom(...)

You could also make a fixture like so to use in your code:
Using the promises chaining API you can add something like this that would pass/fail and catch both possibilities in call.
async function assertErrorMessage(
      p: Promise<ContractTransaction>,
      message: string
    ): Promise<void> {
      return p.then(
        (value) => {
          expect.fail(`Found value instead of error: ${value}`);
        },
        (reason) => {
          expect(reason.message).to.contain(message);
        }
      );
    }

// and call it like so:
await assertErrorMessage(
  myTypechainContractInstance.someMethod(3, 2, 1, 4),
  'SomeMethod_ErrorWithParams(0, 3)'
);

I'm using hardhat and typechain here for this example in typescript but its easy enough to remove the types and using plain JS too. And you can use your interpolated strings too if you like in the function call or add some lambda func to build that up for you as a helper.
This way you can put it in a helper import or similar for your tests and not have them littered with try/catch blocks.

Almost a year later, there is no progress on this particular topic. However, is this something to expect in future or was it skipped at all?

Added support for the feature when using with hardhat in the latest alpha release. Available on npm under the alpha tag.
Not supported for now by @ethereum-waffle/provider as it internally uses ganache. Although the feature can be added to @ethereum-waffle/provider as well - but would require a few manual steps from user such as manually registering contract's ABI. Would love to hear your feedback on that.

It seems to be working, i.e. I can no longer match an error Unauthorized(address) with just revertedWith("Unauthorized"), and it does include the error argument in the diag output. What's the proper way to match these, though? I was thinking something along the lines of how emit operates, emit(contract, 'EventName').withArgs(...), but doesn't look like anything of the sort is there?
Should it be a regex match instead?

The custom errors arguments should definitely be testable via withArgs, just like event arguments are.

Custom errors are now available in Waffle 4 - you can match against a custom error, including the custom error arguments.
Example usage:
await expect(matchers.doRevertWithOne()).to.be.revertedWith('One');

await expect(matchers.doRevertWithOne())
  .to.be.revertedWith('One')
  .withArgs(
    0,
    'message',
    '0x00cfbbaf7ddb3a1476767101c12a0162e241fbad2a0162e2410cfbbaf7162123'
);

Note that this only works in a setup with hardhat, with contracts compiled with hardhat.


an alternate "indirect" way to find "stack_sizes" is necessary for xip

the CI failure looks unrelated
Err:1 http://azure.archive.ubuntu.com/ubuntu jammy/universe amd64 kconfig-frontends-nox amd64 <IP_ADDRESS>+dfsg-6
  Could not connect to azure.archive.ubuntu.com:80 (<IP_ADDRESS>), connection timed out [IP: <IP_ADDRESS> 80]
Err:2 http://azure.archive.ubuntu.com/ubuntu jammy/universe amd64 genromfs amd64 0.5.2-4
  Unable to connect to azure.archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]
E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/universe/k/kconfig-frontends/kconfig-frontends-nox_<IP_ADDRESS>%2bdfsg-6_amd64.deb  Could not connect to azure.archive.ubuntu.com:80 (<IP_ADDRESS>), connection timed out [IP: <IP_ADDRESS> 80]
E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/universe/g/genromfs/genromfs_0.5.2-4_amd64.deb  Unable to connect to azure.archive.ubuntu.com:http: [IP: <IP_ADDRESS> 80]

"spec test on nuttx" seems still failing. @wenyongh can you reopen this?

============> run br_table failed with a non-zero return code 101

==================== LAST LOG of br_table ====================

  expected: 'SystemExit(1)'
  got: 'iwasm --heap-size=0 -v=0 --repl /tmp/tmprdma9ep7.aot
AOT module load failed: cannot apply relocation to text section for aot file generated with "--enable-indirect-mode" flag

br_table test case has a large br_table, which happens to be translated into relocations like:
000003dc R_RISCV_HI20             .Lswitch.table.aot_func_internal#15
000003e0 R_RISCV_LO12_I           .Lswitch.table.aot_func_internal#15

i'm not sure why it was not a problem in the previous code.
i'm not sure how to fix either.
maybe we can disable switch lowering as a workaround?
any idea?

Maybe it is due to some passes added for XIP mode don't work again with LLVM-15.0, as issue #2328 reported by @no1wudi, I think we can wait until the PR is merged.

i'm not sure how to fix either. maybe we can disable switch lowering as a workaround?

We should enable switch lowering to fix this problem, as @wenyongh mentioned, LowerSwitch pass is not actually working now with LLVM 15.
I'll fix it in #2334.

i'm not sure how to fix either. maybe we can disable switch lowering as a workaround?

We should enable switch lowering to fix this problem, as @wenyongh mentioned, LowerSwitch pass is not actually working now with LLVM 15.
I'll fix it in #2334.

i meant something like https://github.com/bytecodealliance/wasm-micro-runtime/pull/2339
i understand your approach can fix it too.
i'm not sure which is a better approach.

Maybe we should try #2339, LowerSwitch is alwasy convert switch to if ... else group, but not all switch will create jump table, this attribute seems keep small switch, which has less impact for performance and code size.

So let's merge #2339 first and then #2334?

So let's merge #2339 first and then #2334?

Yes, I guess it's OK.

the test is now green. https://github.com/bytecodealliance/wasm-micro-runtime/actions/workflows/spec_test_on_nuttx.yml


[QBO] Tax toggle should be locked to disabled for QBO entities with country set to USA

New feature missed in Design Doc:
Tax toggle should be locked to disabled for QBO entities with country set to USA.
Secondly --  the country is set to USA, we should not show the taxes row in the import page

Lmk when you want me to retest @hayata-suenaga @aldo-expensify @dangrous

Just to clarify your description above - do we want to disable it, or fully remove it?

@zanyrenney, the PR was deployed to staging. We can test it now 😄

Or are you talking about two different things (the toggle vs. the import menu)?

@dangrous, we're talking about two different screens.
One is about the toggle button for enabling tax tracking feature on the More Features screen. We want to lock this feature when the workspace is connected to QBO whose entity is US
The other one is about the toggle import menu on the import page. We don't want to display this menu under the same condition I described above.

Note: there was no C+ review of the PR for this issue. No payment is needed.

Closing as no C+ review / payment due.


Update README.md

Adding instructions to development.

@jschuler Since you've been recently experimenting with this repo, I requested your review as well :)

@domhanak @jschuler Thanks for the review guys!


Refactor /config for API 1.0 stability

*Note: This PR is a diff to https://github.com/cilium/cilium/pull/3389. Please don't merge.
See https://github.com/cilium/cilium/issues/3280 for background
Summary of changes:

Refactor the daemon config to be declarative.

How to test (optional):
all tests should pass.

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

Yeah, the autogeneration commits will be squashed, it was just easier to look at the changes locally if I kept them separate. Each PR can me merged separately (and nothing should break) but I can also squash all API changes if you prefer, but that commit will be larger.

Also, @tgraf, the PRs are chained so you might want to start with https://github.com/cilium/cilium/pull/3388

@raybejjani So you suggest to merge #3388 first?

@tgraf Yes. I'd then switch this PR to be against cilium:master. It's a little tedious. If you prefer, we can approve all the API PRs and I can make a combo PR that holds all the commits and we would merge that in one go.

In any case, however, #3388 hasn't passed tests yet :/ but I've seen failures with K8sValidatedPolicyTestAcrossNamespaces Policies Across Namespaces, RuntimeValidatedPolicyImportTests [It] Check Endpoint PolicyMap Generation and RuntimeValidatedMonitorTest With Sample Containers [It] cilium monitor check --from which I hope are unrelated

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please


[API] Create different actions for HTTP status codes

Description:
At the moment we only support below actions
caller->ok()
caller->created()
caller->accepted()
We need to continue adding more actions like,
caller->noContent();
caller -> badRequest();
caller -> internalServerError();
This would help improve the readability of the code and make the language more expressive.

Will be adding caller -> notFound(); as well

Fixed by #22522, hence closing the issue


libpod/container_internal: Make all errors loading explicitly configured hook dirs fatal

Remove this IsNotExist out which was added along with the rest of this block in f6a2b6bf2b (#1830).  Besides the obvious "hook directory does not exist", it was swallowing the less-obvious "hook command does not exist".  And either way, folks are likely going to want non-zero podman exits when we fail to load a hook directory they explicitly pointed us towards.

LGTM

/approve
/lgtm
/hold

@rhatdan are you ok cancelling the hold here and allowing for a merge?

/hold cancel
@baude Always.  Whenever I do the lgtm followed by the hold, it is just because we have the bug where tests can fail, and the PR gets merged,  If tests pass, then just to the cancel.


Add missing boilerplate key/value

Boilerplate created with ignite plugin new my-plugin should have a "boilerplate" key/value.
{
  "createdWith": "<%= props.igniteVersion %>",
  "boilerplate": "<%= props.name %>"
}

https://github.com/infinitered/ignite/blob/master/src/templates/plugin/boilerplate/ignite/ignite.json
https://github.com/infinitered/ignite/issues/829
https://github.com/infinitered/ignite/issues/1267

@JulienMalige Thank you! Appreciate the contribution.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Bug] Adding data source shows "type: undefined"

Describe the bug
When trying to add a new data source using the infinity plug in, the data source adding page looks broken and shows "type: undefined"
Steps to reproduce
Install the plugin, latest version. (2.11.4).
Go to connections -> Data Sources and select 'add new data source'.  Select 'infinity'.  Data source added success message shows but screen looks broken with no settings able to be set.
Note: bugs will be fixed only if enough information provided to reproduce the issue
Sample Data
n/a
Screenshots

Version Details:

Grafana version : Current grafana cloud version (11.3?)
Plugin version : 2.11.4

Additional context
Add any other context about the problem here.

Please check your grafana logs. This is not an error of the plugin but something with your environment and how you installed it.


Fixes several resource leaks listed on coverity

Fixes resource leaks in:

gdscript (CID#269851)
gdscript compiler  (CID#269423)
regex  (CID#269571 &  CID#269860)
android/export  (CID#269470)
gles3/rasterizer scene (CID#269848)
gles3/rasterizer storage (CID#269660)

Thanks a lot!


Combined duplicate style declarations

font-weight: bold and overflow: auto had 2 style declarations through the document. By combining these, we can make normalize.css smaller :)

easier not to group unrelated tags, even if they share the same declarations. makes no difference to the output either.


Image - Python2 + Python3 Helm Chart - create

Currently, there is only a python-ckandatapusher, this should be made more generic for python in general, the ckandatapusher image could just be deployed as lagoon.type: python, as it is really only changes in the image itself that are needed, not the template

fixed now


Always use active version for DOCU CL

Currently the latest version is used to read class documentation and raw (saved but inactive) is used for saving. This change makes read and write access always use the active version.
SDOC_CONSTANTS:

Might fix #5196, pending feedback
I couldn't find a test case for this in abapGit-tests. I'll create one.

https://github.com/abapGit-tests/CLAS_docu/pull/1
Seems like pull to delete local documentation doesn't work either here like #5202
Probably missed here
https://github.com/abapGit/abapGit/blob/3fa3323b2e21d9ef5c97ae98af6a682dce17303d/src/objects/zcl_abapgit_object_clas.clas.abap#L191
and here
https://github.com/abapGit/abapGit/blob/3fa3323b2e21d9ef5c97ae98af6a682dce17303d/src/objects/zcl_abapgit_object_intf.clas.abap#L90
zif_abapgit_oo_object_fnc needs a delete_documentation method calling DOCU_DEL I think for this

FYI, we have methods in the superclass for the documentation. I'm not sure, why those aren't used for clas/intf:
ZCL_ABAPGIT_OBJECTS_SUPER
  SERIALIZE_LONGTEXTS
  DESERIALIZE_LONGTEXTS
  DELETE_LONGTEXTS

Thanks! I saw there were other usages of the function module but didn't realize those were directly accessible. I'll refactor it.

Hmm actually not sure. There's quite a bit more logic in ZCL_ABAPGIT_LONGTEXTS than the direct calls to DOCU_* and the formats in the serialized data are not identical. I think that's for a separate PR to solve.


tests/eas/acceptance: increase accuracy of little cpus test in the Offload Migration testcase

The window for test_little_cpus_run_tasks() was loosely defined as just the migrator delay, which doesn't take into account the time it takes for rt-app to spawn and create its tasks.  After fa4bce7359ec ("tests/eas/acceptance: Increase required busy time for idle pull test"), the test is more strict, so increase the accuracy of the window to meet the new restrictions.

Should be enough to just rename it without BIG, right? If yes, can we do it in this PR?

Sure, just added a commit that does it.


port: 1 -> 2

➡ Forward port
Port ign-plugin1 to gz-plugin2
Branch comparison: https://github.com/gazebosim/gz-plugin/compare/gz-plugin2...ign-plugin1
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

Have there been consistent ABI checker issues here or is this something that I have introduced?

I think since we have already published debs from this branch with the ignition detail headers, we shouldn't remove them now

Restored.

this has many more changes than I would have expected from a forward-port

The remaining diff is mostly copyright years, I'm not sure what the best way to handle these is?  Just bring them all up to 2022?

We don't need to constantly update the copyright year in each file.. This looks fine.


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 658 ms

Resolved: ClamAV performance has improved in e758293 after 7 minutes.


Provide friendly notice when the property of spring.application.name is missing.

fix #217

Pull Request Test Coverage Report for Build 487

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
52 unchanged lines in 16 files lost coverage.
Overall coverage decreased (-0.5%) to 71.228%

Files with Coverage Reduction
New Missed Lines
%

infra-sofa-boot-starter/src/main/java/com/alipay/sofa/infra/endpoint/SofaBootVersionEndpoint.java
1
87.5%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/spring/callback/CloseApplicationContextCallBack.java
1
75.0%

isle-sofa-boot-starter/src/main/java/com/alipay/sofa/isle/spring/listener/SofaModuleContextRefreshedListener.java
1
86.21%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/integration/activator/SofaRuntimeActivator.java
1
0.0%

healthcheck-sofa-boot-starter/src/main/java/com/alipay/sofa/healthcheck/core/HealthIndicatorProcessor.java
1
90.57%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/spring/factory/ServiceFactoryBean.java
2
66.67%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/spring/health/MultiApplicationHealthIndicator.java
2
68.75%

infra-sofa-boot-starter/src/main/java/com/alipay/sofa/infra/config/spring/namespace/handler/SofaBootNamespaceHandler.java
3
0.0%

runtime-sofa-boot-starter/src/main/java/com/alipay/sofa/runtime/service/helper/ReferenceRegisterHelper.java
3
72.73%

test-sofa-boot-starter/src/main/java/com/alipay/sofa/test/runner/SofaJUnit4Runner.java
3
56.67%

Totals

Change from base Build 468:
-0.5%

Covered Lines:
1572

Relevant Lines:
2207

💛  - Coveralls


Modernize all pages and forms (proposing one page change first)

New look to pages overall

Modernized look to pages (less boxiness, improve attractiveness to pages)
i.e., Colors; new Icon (will need to move icon location as well);
Thank you boxes – need to match this look
Review ADA updates/current UNO website
Look of forms (see updated fields for projects)

CPI Review 2019-10-11_UCOMM.docx


Basic video stream completed

I thought I had edited public/index.js however it seems that was only because I had edited the input interval sometimes.  So that is a recommit, whops.

I believe addressed the fatal flaw.  Have also taken note of all your other comments and will address them when I am done with more exciting stuff :)


Rewrite messages.xml in integration to support overriding and deduplication

Description
Add integration process to rewrite messages.xml to

allow overriding messages in part or completely
remove duplicates.

Motivation and Context
Allows plug-ins to override messages completely or only override part of the message configuration.
Relates to #4086
How Has This Been Tested?
Manual testing
Type of Changes

New feature (non-breaking change which adds functionality)

Documentation and Compatibility
For example we have a built-in message
<message id="DOTX029I" type="INFO">
    <reason>The @type attribute on a <%1> element was set to '%3', but the reference is to a more specific '%4' '%2'.</reason>
    <response>This may cause links to sort incorrectly in the output.</response>
</message>

A custom plug-in can use the old extension point to add a new messages file that would change the severity level
<message id="DOTX029I" type="WARN">
</message>

or replace the response text
<message id="DOTX029I" >
    <response>Complain to person X who handles all reltables.</response>
</message> response

The only required info is the @id attribute. You can omit @type, <reason>, or <response> in which case the previous declaration of the message will provide that value.

@jelovirt - in this discussion post, I explored a promising way of overriding a message's severity via the dita.xsl.messages extension point. In a later point, I found that this plugin-based severity override could work but it would need an update in MessageUtils.java.
Does this update possibly have anything to do with that?

@chrispy-snps it's closely related - you could bump an info message up to an error, for example. If you're running in strict mode, and the build is correctly stopping the build for an error, that would stop publishing. (The only reason I don't directly say "this solves the issue" is that I haven't tested lately to verify Error messages from all of Java + XSLT + Ant stop the build in strict mode.)


Feature description
suppose we have a 5D tensor, with shape [3,4,5,6,7]. Then indexing the tensor[index] gives me a 4D tensor with shape [4,5,6,7].
(Optional) Suggest a Solution

It would be slice and unqueez operation.

It would be slice and unqueez operation.

Thank you for your quick reply. Can you give me an example, please?

Since const expressions aren't supported in Rust yet, all indexing operations are keeping the same rank (similar to how Python does it using keep_dim=True). When const expressions land on stable, we could consider having another API where the rank is modified based on the indexing operation.


Include FDO in MOD1.5

FAIR Digital Object specification will provide a fdo:hasMetadata property we have not found anywhere

Check out: https://fairdigitalobjectframework.org/


[Question] Which code is the Loss of the llava model? I didn't find it?

Question
No response

same quation. Have you solved it?


Fix references to formula.json and cask.json

These would be stranded after formula.jws.json.

Review period skipped due to critical label.


feat(workflows/pull-request-check): improve for more projects

Similar changes are done here https://github.com/Kordrad/ng-zen/pull/53


video slugguish/freezes for unmaximized windows

Hi,
Compile the latest master with cmake DCMAKE_BUILD_TYPE=RelWithDebInfo -DWITH_HWDEC=1 -DWITH_GLES2=0 ..
It seems that videos play a lot smoother in fullscreen than otherwise.  For example, on this site fullscreen works smoothly (sort of)  but small screen video practically freezes (only audio remains) cp24.com
Ubuntu 15.04 amd graphic card with open source driver (vdpau enabled)

Guessing this is somehow related to X server interaction. In a fullscreen mode freshwrapper uses own window, but in embedded mode it has to interact with browser to either obtain window, or connect own window via Xembed protocol, or pass rendered pictures to browser to draw. This is quite complicated for me even if when I can reproduce the bug. But if I can't, I can't fix it.


connect hdfs error

when i use pyarrow to connect my hdfs, I meet error
I use
from pyarrow import fs
print(fs.FileSystem.from_uri("hdfs://"))
the error shows loadFileSystems error:
(unable to get root cause for java.lang.NoClassDefFoundError)
(unable to get stack trace for java.lang.NoClassDefFoundError)
hdfsBuilderConnect(forceNewInstance=1, nn=hdfs://, port=0, kerbTicketCachePath=(NULL), userName=(NULL)) error:
(unable to get root cause for java.lang.NoClassDefFoundError)
(unable to get stack trace for java.lang.NoClassDefFoundError)
/arrow/cpp/src/arrow/filesystem/hdfs.cc:51: Failed to disconnect hdfs client: IOError: HDFS hdfsFS::Disconnect failed, errno: 9 (Bad file descriptor)
Traceback (most recent call last):
File "/home/tdops/fucheng.pan/ray-code/read.py", line 15, in
print(fs.FileSystem.from_uri("hdfs:"))
File "pyarrow/_fs.pyx", line 347, in pyarrow._fs.FileSystem.from_uri
File "pyarrow/error.pxi", line 122, in pyarrow.lib.pyarrow_internal_check_status
File "pyarrow/error.pxi", line 99, in pyarrow.lib.check_status
OSError: HDFS connection failed
Reporter: cheng pan
Note: This issue was originally created as ARROW-13535. Please see the migration documentation for further details.

Any updates?

The Arrow HDFS filesystem is a pretty thin wrapper around a vendored copy of libhdfs.  I'm afraid that many of the maintainers here aren't very familiar with how libhdfs works.

need configure CLASSPATH for libjvm.so
add command:
export CLASSPATH=$($HADOOP_HOME/bin/hadoop classpath --glob)


Turn on GZip compression by default

Fixes #810.
Changes proposed in this pull request:

Turn on GZip compression by default for all requests by all Providers.

Thanks for accepting this!
Just so you know, the reason I made "url" a named parameter was in case they changed the method signature in the future... the way I had it made it more resilient to changes originating from outside this codebase.


Zebra's block template can contain duplicate transactions

Motivation
When I use zebra-utils/zcash-rpc-block-template-to-proposal from PR #5944 to send a block proposal from Zebra to both zcashd and Zebra, I see these errors in Zebra's block template:
Node said proposal was invalid, error response from /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.CurTime.8232.json:
bad-txns-inputs-missingorspent
Node said proposal was invalid, error response from /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.CurTime.28232.json:
{
  "reject_reason": "rejected",
  "capabilities": [
    "proposal"
  ]
}

The template in template-getblocktemplate-template.json contains two copies of transaction f7b68748b40a49bf7cb0ce8b9565a29bfd65cd917c68d0ee18feaf2614055608. This is incorrect and breaks a consensus rule.
Both Zebra and zcashd agree that this block proposal is invalid.
This bug is a blocker for mining pools using Zebra, because it produces invalid blocks.
Specifications
Duplicate transactions are invalid because of the consensus rules that prevent:

double-spending a transparent input
revealing a shielded spend nullifier that has already been revealed

Complex Code or Requirements
It is difficult to reproduce this bug, because it depends on the mempool's state at the time, and the chain tips of both nodes.
But the bug isn't happening due to a chain fork or a concurrent block commit, that would be a previous block hash error.
Testing
We might need to re-test with the same script a few times to reproduce this error, and make sure it is gone.
Tasks

[ ] Fix the consensus bug in the block proposal or mempool code

The full script logs are:

Checking getblocktemplate node release info...
Connected to zebrad (port 28232) for getblocktemplate { "mode": "template"  }

Checking proposal nodes release info...
Connected to zcashd (port 8232) for getblocktemplate { "mode": "proposal", "data": "..."  }
Connected to zebrad (port 28232) for getblocktemplate { "mode": "proposal", "data": "..."  }

Checking zebrad template network and tip height...
Checking proposal nodes network and tip height...

getblocktemplate template request (zebrad port 28232):
getblocktemplate { "mode": "template"  }

Querying zebrad main chain at height >=1951401...
0.00user 0.00system 0:00.00elapsed 71%CPU (0avgtext+0avgdata 5636maxresident)k
289inputs+0outputs (0major+880minor)pagefaults 0swaps
Block template data is in /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/template-getblocktemplate-template.json

Turning the template into block proposal data using block-template-to-proposal...
Block proposal data is in /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-data*

getblocktemplate proposal submissions:
getblocktemplate { "mode": "proposal", "data": "..."  }

0.00user 0.00system 0:00.00elapsed 62%CPU (0avgtext+0avgdata 5628maxresident)k
289inputs+0outputs (0major+886minor)pagefaults 0swaps
0.00user 0.00system 0:00.00elapsed 85%CPU (0avgtext+0avgdata 5640maxresident)k
289inputs+0outputs (0major+885minor)pagefaults 0swaps
0.00user 0.00system 0:00.00elapsed 71%CPU (0avgtext+0avgdata 5640maxresident)k
289inputs+0outputs (0major+887minor)pagefaults 0swaps
0.00user 0.00system 0:00.00elapsed 85%CPU (0avgtext+0avgdata 5632maxresident)k
289inputs+0outputs (0major+881minor)pagefaults 0swaps
0.00user 0.00system 0:00.00elapsed 100%CPU (0avgtext+0avgdata 5656maxresident)k
289inputs+0outputs (0major+884minor)pagefaults 0swaps
0.00user 0.00system 0:00.00elapsed 83%CPU (0avgtext+0avgdata 5644maxresident)k
289inputs+0outputs (0major+890minor)pagefaults 0swaps
0.00user 0.00system 0:00.00elapsed 100%CPU (0avgtext+0avgdata 5636maxresident)k
289inputs+0outputs (0major+890minor)pagefaults 0swaps
0.00user 0.00system 0:00.00elapsed 100%CPU (0avgtext+0avgdata 5632maxresident)k
289inputs+0outputs (0major+886minor)pagefaults 0swaps

Proposal response diffs between ports  8232 28232 and time sources CurTime MinTime MaxTime ClampedNow:
--- /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.CurTime.8232.json    2023-01-17 17:21:06.894854936 +1000
+++ /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.CurTime.28232.json   2023-01-17 17:21:06.903854839 +1000
@@ -1 +1,6 @@
-bad-txns-inputs-missingorspent
+{
+  "reject_reason": "rejected",
+  "capabilities": [
+    "proposal"
+  ]
+}
--- /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.CurTime.8232.json    2023-01-17 17:21:06.894854936 +1000
+++ /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.MinTime.28232.json   2023-01-17 17:21:06.919854667 +1000
@@ -1 +1,6 @@
-bad-txns-inputs-missingorspent
+{
+  "reject_reason": "rejected",
+  "capabilities": [
+    "proposal"
+  ]
+}
--- /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.CurTime.8232.json    2023-01-17 17:21:06.894854936 +1000
+++ /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.MaxTime.28232.json   2023-01-17 17:21:06.935854496 +1000
@@ -1 +1,6 @@
-bad-txns-inputs-missingorspent
+{
+  "reject_reason": "rejected",
+  "capabilities": [
+    "proposal"
+  ]
+}
--- /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.CurTime.8232.json    2023-01-17 17:21:06.894854936 +1000
+++ /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.ClampedNow.28232.json        2023-01-17 17:21:06.950854334 +1000
@@ -1 +1,6 @@
-bad-txns-inputs-missingorspent
+{
+  "reject_reason": "rejected",
+  "capabilities": [
+    "proposal"
+  ]
+}

Node said proposal was invalid, error response from /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.CurTime.8232.json:
bad-txns-inputs-missingorspent
Node said proposal was invalid, error response from /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.CurTime.28232.json:
{
  "reject_reason": "rejected",
  "capabilities": [
    "proposal"
  ]
}
Node said proposal was invalid, error response from /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.MinTime.8232.json:
bad-txns-inputs-missingorspent
Node said proposal was invalid, error response from /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.MinTime.28232.json:
{
  "reject_reason": "rejected",
  "capabilities": [
    "proposal"
  ]
}
Node said proposal was invalid, error response from /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.MaxTime.8232.json:
bad-txns-inputs-missingorspent
Node said proposal was invalid, error response from /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.MaxTime.28232.json:
{
  "reject_reason": "rejected",
  "capabilities": [
    "proposal"
  ]
}
Node said proposal was invalid, error response from /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.ClampedNow.8232.json:
bad-txns-inputs-missingorspent
Node said proposal was invalid, error response from /run/user/1000/tmp.Kr4uDEHYbz.block-template-proposal/proposal-check-getblocktemplate-proposal.ClampedNow.28232.json:
{
  "reject_reason": "rejected",
  "capabilities": [
    "proposal"
  ]
}

template-getblocktemplate-template.json contains:

{
  "capabilities": [
    "proposal"
  ],
  "version": 4,
  "previousblockhash": "000000000041c7a3fe3c2e557d6011adc139c1b3ef5f24b9c0374a6bca854ecc",
  "blockcommitmentshash": "60991b55423d2d056d3e981c067c527a30d9950584705927d6329238d2378095",
  "lightclientroothash": "60991b55423d2d056d3e981c067c527a30d9950584705927d6329238d2378095",
  "finalsaplingroothash": "60991b55423d2d056d3e981c067c527a30d9950584705927d6329238d2378095",
  "defaultroots": {
    "merkleroot": "3319b2f5e04f03bb0e69e7ae2b24e0607e442e5362b5670beda38dbe604173a2",
    "chainhistoryroot": "b0f3d31b9dbc3efdd16497ef569eaf961b12d44c1140618cef49caee72ffa90a",
    "authdataroot": "d4ac15b68ab2a886d18bb2e155bb5e2f8135201ca391a3ea03c61eb833c14fff",
    "blockcommitmentshash": "60991b55423d2d056d3e981c067c527a30d9950584705927d6329238d2378095"
  },
  "transactions": [
    {
      "data": "0400008085202f89024093c6f339fa0948d5276a7593862940154def5dd15b82e5c36017e0dffe752a010000006a473044022015122d43e051e9b8e37b85bcba422caa5ff6f8f3c7e03f17571ae4eca10275a202204338a01fe79634fb9e6c5a38e76423d6564d0d62c252adc272dcbddd58a5068601210301749fd242a0b3bdd3f7083c98fd6fc9c4e101491b1a49e7b75d74cce6586b21feffffffd55fff7d49f537ebf492e059b63cd187f8485a8d73904b9bfc2d86b8733ce546000000006b483045022100f679efe9ef9a4c3ac7d3d54af2eea0a7b61a7ec3d8f3b24c1be50685163b59e402207ccc3ff1dd3006b4690a15c6d271ec53433f352c127e8f22a3742237a58e9fcf01210285b79d685ccfd14acc06ecccbefd176b997389c951007ab652afecfe7d80c6ddfeffffff021cd9b459010000001976a9147eb1eda601eb6ebbaa0995e58ee643d57817546088aca5080000000000001976a9142fbbabfefa713333c3a4bb37b9b3f884d6cd9aad88ac7cc61d00d2c61d000000000000000000000000",
      "hash": "f7b68748b40a49bf7cb0ce8b9565a29bfd65cd917c68d0ee18feaf2614055608",
      "authdigest": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
      "depends": [
      ],
      "fee": 785,
      "sigops": 2,
      "required": false
    },
    {
      "data": "0400008085202f89024093c6f339fa0948d5276a7593862940154def5dd15b82e5c36017e0dffe752a010000006a473044022015122d43e051e9b8e37b85bcba422caa5ff6f8f3c7e03f17571ae4eca10275a202204338a01fe79634fb9e6c5a38e76423d6564d0d62c252adc272dcbddd58a5068601210301749fd242a0b3bdd3f7083c98fd6fc9c4e101491b1a49e7b75d74cce6586b21feffffffd55fff7d49f537ebf492e059b63cd187f8485a8d73904b9bfc2d86b8733ce546000000006b483045022100f679efe9ef9a4c3ac7d3d54af2eea0a7b61a7ec3d8f3b24c1be50685163b59e402207ccc3ff1dd3006b4690a15c6d271ec53433f352c127e8f22a3742237a58e9fcf01210285b79d685ccfd14acc06ecccbefd176b997389c951007ab652afecfe7d80c6ddfeffffff021cd9b459010000001976a9147eb1eda601eb6ebbaa0995e58ee643d57817546088aca5080000000000001976a9142fbbabfefa713333c3a4bb37b9b3f884d6cd9aad88ac7cc61d00d2c61d000000000000000000000000",
      "hash": "f7b68748b40a49bf7cb0ce8b9565a29bfd65cd917c68d0ee18feaf2614055608",
      "authdigest": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
      "depends": [
      ],
      "fee": 785,
      "sigops": 2,
      "required": false
    }
  ],
  "coinbasetxn": {
    "data": "0400008085202f89010000000000000000000000000000000000000000000000000000000000000000ffffffff0503aac61d00ffffffff04a2b8e60e000000001976a914be3a9e1d9af0ec5dbe67271284c9cf53b79aa74f88ac38c94d010000000017a9142e1fff58b8ec78077b50b7ffa2144267512b32bf8740787d010000000017a914931fec54c1fea86e574462cc32013f5400b8912987286bee000000000017a914d45cb1adffb5215a42720532a076f02c7c778c908700000000aac61d000000000000000000000000",
    "hash": "11a90fc04e6fd1361e4272fe0789ddce2b1edf19a16aa9dec90368a88611061d",
    "authdigest": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
    "depends": [
    ],
    "fee": -1570,
    "sigops": 1,
    "required": true
  },
  "longpollid": "0001951401a7c919f6167394521000000000027fefa9c9",
  "target": "0000000001ad6700000000000000000000000000000000000000000000000000",
  "mintime":<PHONE_NUMBER>,
  "mutable": [
    "time",
    "transactions",
    "prevblock"
  ],
  "noncerange": "00000000ffffffff",
  "sigoplimit": 20000,
  "sizelimit": 2000000,
  "curtime":<PHONE_NUMBER>,
  "bits": "1c01ad67",
  "height": 1951402,
  "maxtime":<PHONE_NUMBER>
}

proposal-data.CurTime.json contains:

{ "mode": "proposal", "data": "[encoded data, 4954 characters]" }

proposal-data.CurTime.debug contains:

{
  "capabilities": [
    "proposal"
  ],
  "version": 4,
  "previousblockhash": "000000000041c7a3fe3c2e557d6011adc139c1b3ef5f24b9c0374a6bca854ecc",
  "blockcommitmentshash": "60991b55423d2d056d3e981c067c527a30d9950584705927d6329238d2378095",
  "lightclientroothash": "60991b55423d2d056d3e981c067c527a30d9950584705927d6329238d2378095",
  "finalsaplingroothash": "60991b55423d2d056d3e981c067c527a30d9950584705927d6329238d2378095",
  "defaultroots": {
    "merkleroot": "3319b2f5e04f03bb0e69e7ae2b24e0607e442e5362b5670beda38dbe604173a2",
    "chainhistoryroot": "b0f3d31b9dbc3efdd16497ef569eaf961b12d44c1140618cef49caee72ffa90a",
    "authdataroot": "d4ac15b68ab2a886d18bb2e155bb5e2f8135201ca391a3ea03c61eb833c14fff",
    "blockcommitmentshash": "60991b55423d2d056d3e981c067c527a30d9950584705927d6329238d2378095"
  },
  "transactions": [
    {
      "data": "0400008085202f89024093c6f339fa0948d5276a7593862940154def5dd15b82e5c36017e0dffe752a010000006a473044022015122d43e051e9b8e37b85bcba422caa5ff6f8f3c7e03f17571ae4eca10275a202204338a01fe79634fb9e6c5a38e76423d6564d0d62c252adc272dcbddd58a5068601210301749fd242a0b3bdd3f7083c98fd6fc9c4e101491b1a49e7b75d74cce6586b21feffffffd55fff7d49f537ebf492e059b63cd187f8485a8d73904b9bfc2d86b8733ce546000000006b483045022100f679efe9ef9a4c3ac7d3d54af2eea0a7b61a7ec3d8f3b24c1be50685163b59e402207ccc3ff1dd3006b4690a15c6d271ec53433f352c127e8f22a3742237a58e9fcf01210285b79d685ccfd14acc06ecccbefd176b997389c951007ab652afecfe7d80c6ddfeffffff021cd9b459010000001976a9147eb1eda601eb6ebbaa0995e58ee643d57817546088aca5080000000000001976a9142fbbabfefa713333c3a4bb37b9b3f884d6cd9aad88ac7cc61d00d2c61d000000000000000000000000",
      "hash": "f7b68748b40a49bf7cb0ce8b9565a29bfd65cd917c68d0ee18feaf2614055608",
      "authdigest": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
      "depends": [],
      "fee": 785,
      "sigops": 2,
      "required": false
    },
    {
      "data": "0400008085202f89024093c6f339fa0948d5276a7593862940154def5dd15b82e5c36017e0dffe752a010000006a473044022015122d43e051e9b8e37b85bcba422caa5ff6f8f3c7e03f17571ae4eca10275a202204338a01fe79634fb9e6c5a38e76423d6564d0d62c252adc272dcbddd58a5068601210301749fd242a0b3bdd3f7083c98fd6fc9c4e101491b1a49e7b75d74cce6586b21feffffffd55fff7d49f537ebf492e059b63cd187f8485a8d73904b9bfc2d86b8733ce546000000006b483045022100f679efe9ef9a4c3ac7d3d54af2eea0a7b61a7ec3d8f3b24c1be50685163b59e402207ccc3ff1dd3006b4690a15c6d271ec53433f352c127e8f22a3742237a58e9fcf01210285b79d685ccfd14acc06ecccbefd176b997389c951007ab652afecfe7d80c6ddfeffffff021cd9b459010000001976a9147eb1eda601eb6ebbaa0995e58ee643d57817546088aca5080000000000001976a9142fbbabfefa713333c3a4bb37b9b3f884d6cd9aad88ac7cc61d00d2c61d000000000000000000000000",
      "hash": "f7b68748b40a49bf7cb0ce8b9565a29bfd65cd917c68d0ee18feaf2614055608",
      "authdigest": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
      "depends": [],
      "fee": 785,
      "sigops": 2,
      "required": false
    }
  ],
  "coinbasetxn": {
    "data": "0400008085202f89010000000000000000000000000000000000000000000000000000000000000000ffffffff0503aac61d00ffffffff04a2b8e60e000000001976a914be3a9e1d9af0ec5dbe67271284c9cf53b79aa74f88ac38c94d010000000017a9142e1fff58b8ec78077b50b7ffa2144267512b32bf8740787d010000000017a914931fec54c1fea86e574462cc32013f5400b8912987286bee000000000017a914d45cb1adffb5215a42720532a076f02c7c778c908700000000aac61d000000000000000000000000",
    "hash": "11a90fc04e6fd1361e4272fe0789ddce2b1edf19a16aa9dec90368a88611061d",
    "authdigest": "ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff",
    "depends": [],
    "fee": -1570,
    "sigops": 1,
    "required": true
  },
  "longpollid": "0001951401a7c919f6167394521000000000027fefa9c9",
  "target": "0000000001ad6700000000000000000000000000000000000000000000000000",
  "mintime":<PHONE_NUMBER>,
  "mutable": [
    "time",
    "transactions",
    "prevblock"
  ],
  "noncerange": "00000000ffffffff",
  "sigoplimit": 20000,
  "sizelimit": 2000000,
  "curtime":<PHONE_NUMBER>,
  "bits": "1c01ad67",
  "height": 1951402,
  "maxtime":<PHONE_NUMBER>
}
Block {
    header: Header {
        version: 4,
        previous_block_hash: block::Hash(
            "000000000041c7a3fe3c2e557d6011adc139c1b3ef5f24b9c0374a6bca854ecc",
        ),
        merkle_root: Root(
            "a2734160be8da3ed0b67b562532e447e60e0242baee7690ebb034fe0f5b21933",
        ),
        commitment_bytes: [u8; 32](
            "958037d2389232d6275970840595d9307a527c061c983e6d052d3d42551b9960",
        ),
        time: 2023-01-17T07:21:06Z,
        difficulty_threshold: CompactDifficulty(
            0x1c01ad67,
            Some(ExpandedDifficulty("0000000001ad6700000000000000000000000000000000000000000000000000")),
        ),
        nonce: [u8; 32](
            "0000000000000000000000000000000000000000000000000000000000000000",
        ),
        solution: EquihashSolution(
            "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
        ),
    },
    transactions: [
        V4 {
            inputs: [
                Coinbase {
                    height: Height(
                        1951402,
                    ),
                    data: CoinbaseData(
                        "\\x00",
                    ),
                    sequence:<PHONE_NUMBER>,
                },
            ],
            outputs: [
                Output {
                    value: Amount<zebra_chain::amount::NonNegative>(
                        250001570,
                    ),
                    lock_script: Script(
                        "76a914be3a9e1d9af0ec5dbe67271284c9cf53b79aa74f88ac",
                    ),
                },
                Output {
                    value: Amount<zebra_chain::amount::NonNegative>(
                        21875000,
                    ),
                    lock_script: Script(
                        "a9142e1fff58b8ec78077b50b7ffa2144267512b32bf87",
                    ),
                },
                Output {
                    value: Amount<zebra_chain::amount::NonNegative>(
                        25000000,
                    ),
                    lock_script: Script(
                        "a914931fec54c1fea86e574462cc32013f5400b8912987",
                    ),
                },
                Output {
                    value: Amount<zebra_chain::amount::NonNegative>(
                        15625000,
                    ),
                    lock_script: Script(
                        "a914d45cb1adffb5215a42720532a076f02c7c778c9087",
                    ),
                },
            ],
            lock_time: Height(
                Height(
                    0,
                ),
            ),
            expiry_height: Height(
                1951402,
            ),
            joinsplit_data: None,
            sapling_shielded_data: None,
        },
        V4 {
            inputs: [
                PrevOut {
                    outpoint: OutPoint {
                        hash: transaction::Hash(
                            "2a75fedfe01760c3e5825bd15def4d1540298693756a27d54809fa39f3c69340",
                        ),
                        index: 1,
                    },
                    unlock_script: Script(
                        "473044022015122d43e051e9b8e37b85bcba422caa5ff6f8f3c7e03f17571ae4eca10275a202204338a01fe79634fb9e6c5a38e76423d6564d0d62c252adc272dcbddd58a5068601210301749fd242a0b3bdd3f7083c98fd6fc9c4e101491b1a49e7b75d74cce6586b21",
                    ),
                    sequence:<PHONE_NUMBER>,
                },
                PrevOut {
                    outpoint: OutPoint {
                        hash: transaction::Hash(
                            "46e53c73b8862dfc9b4b90738d5a48f887d13cb659e092f4eb37f5497dff5fd5",
                        ),
                        index: 0,
                    },
                    unlock_script: Script(
                        "483045022100f679efe9ef9a4c3ac7d3d54af2eea0a7b61a7ec3d8f3b24c1be50685163b59e402207ccc3ff1dd3006b4690a15c6d271ec53433f352c127e8f22a3742237a58e9fcf01210285b79d685ccfd14acc06ecccbefd176b997389c951007ab652afecfe7d80c6dd",
                    ),
                    sequence:<PHONE_NUMBER>,
                },
            ],
            outputs: [
                Output {
                    value: Amount<zebra_chain::amount::NonNegative>(
<PHONE_NUMBER>,
                    ),
                    lock_script: Script(
                        "76a9147eb1eda601eb6ebbaa0995e58ee643d57817546088ac",
                    ),
                },
                Output {
                    value: Amount<zebra_chain::amount::NonNegative>(
                        2213,
                    ),
                    lock_script: Script(
                        "76a9142fbbabfefa713333c3a4bb37b9b3f884d6cd9aad88ac",
                    ),
                },
            ],
            lock_time: Height(
                Height(
                    1951356,
                ),
            ),
            expiry_height: Height(
                1951442,
            ),
            joinsplit_data: None,
            sapling_shielded_data: None,
        },
        V4 {
            inputs: [
                PrevOut {
                    outpoint: OutPoint {
                        hash: transaction::Hash(
                            "2a75fedfe01760c3e5825bd15def4d1540298693756a27d54809fa39f3c69340",
                        ),
                        index: 1,
                    },
                    unlock_script: Script(
                        "473044022015122d43e051e9b8e37b85bcba422caa5ff6f8f3c7e03f17571ae4eca10275a202204338a01fe79634fb9e6c5a38e76423d6564d0d62c252adc272dcbddd58a5068601210301749fd242a0b3bdd3f7083c98fd6fc9c4e101491b1a49e7b75d74cce6586b21",
                    ),
                    sequence:<PHONE_NUMBER>,
                },
                PrevOut {
                    outpoint: OutPoint {
                        hash: transaction::Hash(
                            "46e53c73b8862dfc9b4b90738d5a48f887d13cb659e092f4eb37f5497dff5fd5",
                        ),
                        index: 0,
                    },
                    unlock_script: Script(
                        "483045022100f679efe9ef9a4c3ac7d3d54af2eea0a7b61a7ec3d8f3b24c1be50685163b59e402207ccc3ff1dd3006b4690a15c6d271ec53433f352c127e8f22a3742237a58e9fcf01210285b79d685ccfd14acc06ecccbefd176b997389c951007ab652afecfe7d80c6dd",
                    ),
                    sequence:<PHONE_NUMBER>,
                },
            ],
            outputs: [
                Output {
                    value: Amount<zebra_chain::amount::NonNegative>(
<PHONE_NUMBER>,
                    ),
                    lock_script: Script(
                        "76a9147eb1eda601eb6ebbaa0995e58ee643d57817546088ac",
                    ),
                },
                Output {
                    value: Amount<zebra_chain::amount::NonNegative>(
                        2213,
                    ),
                    lock_script: Script(
                        "76a9142fbbabfefa713333c3a4bb37b9b3f884d6cd9aad88ac",
                    ),
                },
            ],
            lock_time: Height(
                Height(
                    1951356,
                ),
            ),
            expiry_height: Height(
                1951442,
            ),
            joinsplit_data: None,
            sapling_shielded_data: None,
        },
    ],
}

@mpguerra can we schedule this fix in this sprint, it is blocking further testing?

Hey team! Please add your planning poker estimate with Zenhub @arya2 @conradoplg @dconnolly @oxarbitrage @teor2345 @upbqdn

@arya2 unfortunately the PR was merged before the planning poker result was set. Can you please add an estimate here?


HTTP Client Middleware not working

Laravel Version: 9.39.0
PHP Version: 8.0.24
Database Driver & Version:8.0.31

Description:
I am trying to execute the sample code provided here https://laravel.com/docs/9.x/http-client#guzzle-middleware
$response = Http::withMiddleware(
        GuzzleHttp\Middleware::mapRequest(function (Psr\Http\Message\RequestInterface $request) {
            $request->withHeader('X-Example', 'Value');
            return $request;
        })
    )->get('https://example.com');

But when I check the request inside of laravel telescope it seems that the request is not getting modified using this middleware.

I even tried changing the request method to post but that also did not seem to work

Unfortunately, because of the way Guzzle works, it's not possible to gather headers set this way. They're populated after Laravel already instructed Guzzle to send the request and thus there's no way to gather them for Telescope. We'd appreciate a PR if someone ever figures out how to do this.

@driesvints Does this means that the request is actually sent along with the headers and only not showing inside laravel telescope?

Yes I think so.


When "viewed" event trigged, how can I know which img click?

When "viewed" event trigged, how can I know which img click?

const instance = $('#images').data('viewer');

console.log(instance.$images); // All the images in the viewer.
console.log(instance.index); // This is the index of the current viewed image.


Flush last writes in the host queue when the queue is closed

cc @robskillington @cw9 @prateek @ben-lerner
This PR fixes an issue that causes the writes to be lost when a queue is closed. In particular, the current implementation throws away the writes queued if the flush goroutine sees that the queue is closed, which is wrong. This issue was further exacerbated by the fact that during a node removal, multiple versions would be written, which means multiple iterations of tearing down and setting up host queues, which means quite a few writes could be lost without us noticing any errors whatsoever.
This PR forces the writes queued up to be flushed on queue close. Additionally, it also holds the write lock when rotating ops during a flush so we don't accidentally dequeue writes right before a queue is closed.
All in all it's a subtle bug.

Coverage increased (+0.001%) to 76.026% when pulling 18390e6a0fc587e7187e51da5ac47fe54cc6b55c on xichen-flush-last-writes-on-close into 3d1c61958b68e0456c6d4936abb8176c9d710ba5 on master.

Coverage decreased (-0.02%) to 76.003% when pulling 122b427103e3c0c2f831d562839fe467d3be2fd5 on xichen-flush-last-writes-on-close into 3d1c61958b68e0456c6d4936abb8176c9d710ba5 on master.

Coverage increased (+0.05%) to 76.079% when pulling 122b427103e3c0c2f831d562839fe467d3be2fd5 on xichen-flush-last-writes-on-close into 3d1c61958b68e0456c6d4936abb8176c9d710ba5 on master.

Coverage increased (+0.05%) to 76.079% when pulling 122b427103e3c0c2f831d562839fe467d3be2fd5 on xichen-flush-last-writes-on-close into 3d1c61958b68e0456c6d4936abb8176c9d710ba5 on master.


Issue with Rotation on iPad

I am a novice programmer and I would fix this on a fork if I could. But it seems like constraints to its superview are not being set within the control.
I did get the control working in Storyboard. But when I use it in the detail view controller for a UISplitViewController, then rotate the view from portrait to landscape, the width of the control does not resize. I set the constraints from the MXSegmentedPager to its superview, but within the MXSegmentedPager itself, it doesn't seem like there are constraints set for the various components.
Again, I would do it if I knew how. Just learning all of this.
Thanks again for this great control.

Hi,
Well its not very clear... I do not use constraints in the MXSegmentedPager, but I manually layout subviews. Which mean that you dont have do worry about subviews layout, you shouldn't add constraints   to the segmented-control, container or pages.
To see what is going wrong, you could add a breakpoint in the layoutSubviews method of the MXSegmentedPager and check when its getting called. If it doesn't get called when you rotate, it means that your constraints are not properly set to the MXSegmentedPager.
Also, on what ios version do you test ?

I have a UISplitView with a master controller and a Detail Controller. I am using MXSegmentedPager in the detail controller. I set up the Detail Controller in storyboard. I use a regular view controller and add a subview to the main view. I designate this subview as MXSegmentedPager. I hook it up via IB. I start the app in Portrait orientation (both side of the UISplitview are always visible, in both orientations). It looks fine. I rotate the app to landscape. The MXSegmentedPager remains the same width as it was in portrait orientation (doesn't stretch all the way to the right), although it looks like the HMSegmentedControl has spaced out as if to accommodate the wider width. But it is only about 60% visible (left side, since the view has not stretched to the right). Sorry if I don't have the correct lingo. Does that make sense though?

Also, if there is content, that gets skewed on the rotation, and the header image view is the wrong size. I am sorry if I don't understand, but I thought you needed to add actual NSLayoutConstraints if using auto layout, either programmatically or via IB. I added the constraints between the control and my own view, but it does not seem to me that the control has NSLayoutConstraints? Since the control itself is not laid out in IB (subviews are added via code), I thought this had to be done programmatically? As I said, I am a novice, but this was my understanding.

I think auto layout is used by almost all controls these days, even when they are laid our manually? In the case when the control is laid out manually, the NSLayoutConstraints are just added programmatically, I believe. Because of the many different size/orientations of devices, I think that this is necessary. Again, the novice disclaimer, but this is what I have seen in many controls on this site and on CocoaControls.com, and from my own research. But please tell me if I am wrong!

Auto layout is a very good storyboard and nib tool to automatically add constraints. Constraints are only use to compute subviews's frame when it comes to layoutSubviews. In the MXSegmentedPager case, subviews frame are compute by layoutWithHeight: and layoutContainer when reloadData is called so It doesn't need to add any NSLayoutConstraint.
Adding constraints is not a necessary thing, it's just a way to layout your subviews.
Typically, you just have to add the MXSegmentedPager to your view, add your constraints and thats it. Thats working in my test.
Did you try with a breakpoint ?

Is that the issue you are facing when you rotate your ipad ?

Mine doesn't look exactly the same but that is the general idea of what is happening when I use the example app in your repository. I think both could be solved by adding constraints? I didn't try setting a breakpoint because I don't know where I would set it or what I would be looking for (sorry).

I did figure out how to set the breakpoint as you said. Layout subviews is being called upon rotation. Still the problem persists.

Actually, I don't think this is your issue. I've just it using the ParallaxHeader category, and your description makes sense now! I thought you were using the standard class.
For the explanation, the parallax category add a scrolling subview which is not handled when layoutSubviews is called. Adding constraints may be the right choice. I will fix it asap...

First commit was a mistake, second one should fix the bug.

@maxep Thanks for all of your hard work on this. Your change did solve the issue with you example app, and it did go a long way towards solving my issues as well. Yet two issues remain:

On rotation from Portrait to landscape, the Header and the Segmented control now seem to rotate fine. But the content in the page seems to shift to a different page or an overlap between two pages on rotation.

For a view such as a webview, the frames are being set too wide. When I use the parallax controller as the detail controller of my splitview, the width of the webview seems to be always the entire width of the screen (in portrait), no matter which rotation.

It should be noted, probably for both issues, that for my split view, I always show both the detail and the master. So the detail view, which I am using this for, is never the entire width of the screen. The webview in MXSegmentedPager does not seem to realize this. I'm not sure the other views do either given issue 1? But I can't say for sure that both of the problems are related in this way. Though they both are definitely problems.
I tried adding constraints programmatically and failed. I only know how to do it in Storyboard. Sorry or I would fix this myself. Thanks again.

You are welcome.
Could you provide a sample code or send me project that reproduce these issues. English is not my native language and its a bit hard for me to understand the described behavior.

Okay. Issue #1 was because I didn't properly update all of my files from your changes. Sorry.
Issue #2 remains. I have altered your example app to show you but not sure how to get it to you. I added a UISplitViewController to the Storyboard and set it as the initial controller. I made MXSimpleViewController the Master and MSParallaxViewController the Detail. I added this code to viewDidLoad of MXSimpleViewController to make sure master would always show:
if ([self.splitViewController respondsToSelector:@selector(setPreferredDisplayMode:)]) {
    [self.splitViewController setPreferredDisplayMode:UISplitViewControllerDisplayModeAllVisible];
}
self.splitViewController.delegate = self;

Maybe you can do this yourself or tell me how to send you the sample project.
If you run this you will see the issue above:
"For a view such as a webview, the frames are being set too wide. When I use the parallax controller as the detail controller of my splitview, the width of the webview seems to be always the entire width of the screen (in portrait), no matter which rotation."
You will look at Webview in Portrait mode.
Hope this helps.

Just sent the two changed files (storyboard and MXSimpleViewController) to your email. Hope it helps.

OK I see now! This is not a issue, it depend on your UIWebView configuration and content. You should have a look on scalesPageToFit property .
But I'm more worried about the pages' contentOffset which wrongly goes to top when the parallax category rotates..

Oh yeah. Do you know how that can be fixed?

I am back working on this again and experiencing this problem right now. The contentOffset changes when the iPad rotates, which sets off this sequence
-[MXPagerView observeValueForKeyPath:ofObject:change:context:]
-[MXPagerView didScrollFromPosition:ToPosition:]
-[MXPagerView setIndex:]
-[MXSegmentedPager pagerView:didMoveToPageAtIndex:]
which calls:
[self.segmentedControl setSelectedSegmentIndex:index animated:NO];
So when I rotate the iPad, a different segment of the segmentedControl is selected.


Mouse autoclick on the context menu

Does this issue occur when all extensions are disabled?: Yes

Commit:<PHONE_NUMBER>f055b99068d3688932416f2346dd3b
Date: 2022-11-09T03:54:53.913Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.10.0-19-amd64
Sandboxed: No
Steps to Reproduce:

Move activity bar to right.
Try to left and right click settings button (gear)

/duplicate of #167941

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


fix: rollback dry run mode on upgrader

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 3.0.4-fix-refactor-dry-run-SNAPSHOT
download it from Artifactory here

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

3.0.4
GitHub release

Your semantic-release bot :package::rocket:


Unable to get dot installed properly on Mac Mojave (10.14.4)

Hi,
I'm following the instructions on your github page to get dtreeviz working for a school project but it doesn't seem to be updating dot properly. I've ran your instructions multiple times. Also, found this thread and tried everything in there as well:
https://github.com/parrt/dtreeviz/issues/33
I've followed all the instructions to install on github page:
(including uninstalling python-graphviz and graphviz and brew uninstall packages and downloading their package and doing a make install)
https://github.com/parrt/dtreeviz
I'm on a MacBook Pro 13" 2018 Mojave (10.14.4)
Was wondering if you might be able to help?
brew upgrade pango librsvg
Error: pango 1.42.4_1 already installed
Error: librsvg 2.44.13 already installed

My system is still finding dot from /usr/local/bin/dot
It also doesn't know anything about a ../Cellar/graphviz/2.40.1/bin/dot directory
I also saw bunch of warnings when I did the make but didn't find any errors:
✔ /tmp/graphviz-2.40.1
20:34 $ which dot
/usr/local/bin/dot
✔ /tmp/graphviz-2.40.1
20:34 $ dot -Tsvg:cairo
Format: "svg:cairo" not recognized. Use one of: svg:svg:core
✘-1 /tmp/graphviz-2.40.1
20:35 $ lw -l
-bash: lw: command not found
✘-127 /tmp/graphviz-2.40.1
20:35 $ ls -l ../Cellar/graphviz/2.40.1/bin/dot
ls: ../Cellar/graphviz/2.40.1/bin/dot: No such file or directory
✘-1 /tmp/graphviz-2.40.1

here is a history of my commands for the install:
589  brew uninstall graphviz
 590  brew reinstall pango librsvg --build-from-source # even if already there, please reinstall
 591  brew reinstall cairo --build-from-source
 592  brew install graphviz --build-from-source
 593  brew info graphviz
 594  #./configure --includedir=/usr/local/include/graphviz --with-pangocairo=yes --with-rsvg=yes
 595  history
 596  make uninstall
 597  ./configure --includedir=/usr/local/include/graphviz --with-pangocairo=yes --with-rsvg=yes
 598  rm -rf /usr/local/lib/graphviz
 599  ./configure --includedir=/usr/local/include/graphviz --with-pangocairo=yes --with-rsvg=yes | tee make.log 2>&1
 600  #make -j 8 | tee
 601  mv make.log configure.log
 602  make -j 8 | tee make.log 2>&1
 603  make install | tee install.log 2>&1
 604  history

Hmm... sorry to hear that. We are working on a new solution that does not require all those fancy libraries. See https://github.com/parrt/dtreeviz/pull/36

If you pull latest master, install is now super simple / easy!


change HttpServletResponse to HttpServletRequest in SendResponseFilter

to check Servlet API 3.1 supported is wrong.
i saw same bug in https://github.com/spring-cloud/spring-cloud-netflix/pull/1907

@shuiky Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


For contact information block download icons

For contact information block download icons. Add links to social networks (LinkedIn, Facebook, Instagram), phone number, email, Telegram username, etc.

Can be downloaded here https://www.iconfinder.com/

Thank you


Relax CI pin on Numpy < 1.25

The release of Numpy 1.26.1 included an upstream patch to fix a bug in the compiled SIMD versions of complex multiplication loops on macOS, and we have fixed the deprecation warnings and new CI flakiness on our side caused by it, so it should now be safe to relax the pin.

Summary
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

0 of 0   changed or added relevant lines in 0 files are covered.
19 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.004%) to 86.439%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
7
91.16%

crates/qasm2/src/parse.rs
12
97.13%

Totals

Change from base Build<PHONE_NUMBER>:
-0.004%

Covered Lines:
66280

Relevant Lines:
76678

💛  - Coveralls

@Mergifyio backport stable/0.46


Fix #849. Optimize performance for encoding/decoding when using custom transformations of member names or constructor

Remove calling transformMemberName and transformConstructorNames of Configuration on every encoding, decoding to/from json

Codecov Report

Merging #860 into master will decrease coverage by 0.08%.
The diff coverage is 86.36%.

@@            Coverage Diff             @@
##           master     #860      +/-   ##
==========================================
- Coverage   87.03%   86.94%   -0.09%
==========================================
  Files          71       71
  Lines        2330     2337       +7
  Branches      172      167       -5
==========================================
+ Hits         2028     2032       +4
- Misses        302      305       +3

Impacted Files
Coverage Δ

...ce/generic/extras/decoding/ConfiguredDecoder.scala
89.18% <84.61%> (-2.24%)
:arrow_down:

...eric/extras/encoding/ConfiguredObjectEncoder.scala
90.47% <88.88%> (-3.28%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
90.55% <0%> (-0.66%)
:arrow_down:

...d/src/main/scala/io/circe/NonEmptySeqDecoder.scala
100% <0%> (+8.33%)
:arrow_up:

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 f89f48f...895a3d9. Read the comment docs.

This looks great, thanks @vndzzz!

Just to confirm—this is okay to merge? (Asking because of the "WIP" on the last commit.)

@travisbrown yes it is okay to merge it.


iroh tag list doesn't check if you have a running iroh node

we should check each command to ensure we have the proper checks!

I gave this a try and I got:
Error: Iroh node is not running

Caused by:
    deadline has elapsed

what are you seeing/ how are you getting it?

this happened during a dogfooding, the command just hung. Could have been some other interaction, or maybe it was fixed already!


What to put into LOADBALANCER_SOURCE_RANGES in ansible-vars.yaml

I am confused by the instructions ... in the file, /home/jumpuser/viya4-deployment/ansible-vars.yaml which was copied from /home/jumpuser/viya4-deployment/examples/ansible-vars-iac.yaml
Should I put the value from the IAC tf apply command output:
nat_ip = 52.188.xxx.xxx
into line 6:
LOADBALANCER_SOURCE_RANGES: ['52.188.xxx.xxx/32']

The file states that you should. Listed here in the sample file: https://github.com/sassoftware/viya4-deployment/blob/main/examples/ansible-vars-iac.yaml#L4-L6

Thanks for clarification.  It was not clear to me before.  I'll probably suggest a clarification via a PR to make it a tad easier for others.

can you explain why i must set  to the nat ip from the tf output? shouldn't i put the service cidr that is showing in the aks overview ?

The nat_ip value gets set in the valid CIDR ranges for your security group, firewall, etc. depending on your provider to allow north/south traffic back into the cluster.

However this approach still exposes the service to public IP because of nginx ingress controller, i want to find new approach that uses azure VPN maybe and to set the IP to be private, what changes i need to do any advice?


Change bazel_deps from a git_repository to an http_file

This way, we can split the files to separate targets and not necessarily download all of them every time (and all their previous versions, as they're stored in the git repo).

This is done.


Jupyterhub launch email

Summary
Draw up an email to announce the launch of our Jupyterhub and give starter information about how to use it.
Motivation
Since the VM is now running, we may as well make people aware that the service is there. (addendum: please turn off the VM until the email is sent? :)
Additional context
Add any other context or screenshots about the feature request here.

VM can now be turned back on - azure account is on a monthly subscription

Can we now send out a launch email, or is it best to wait for the workshop?

I don't think we need jupyter hub now that google colab is working

Closing this issue. Have we turned off the jupyter hub?