Resize D3D11Texture2D from AcquireNextFrame

Hello,
I'm posting there an issue I'm facing from a long time.. There is no documentation. Hope you will help me heartily as I am stuck for a long time now.
I would like to scale a D3D11Texture2D to make it smaller.
I'm using AcquireNextFrame to get an output of my desktop but it's on FullHD resolution. I just want to scale the texture because I need then to send the buffer over network.
I'm on MFC Application and C++. Here is my code :
if (mRealTexture == nullptr) {
			D3D11_TEXTURE2D_DESC description;
			texture2D->GetDesc(&description);
			description.BindFlags = 0;
			description.CPUAccessFlags = D3D11_CPU_ACCESS_READ | D3D11_CPU_ACCESS_WRITE;
			description.Usage = D3D11_USAGE_STAGING;
			description.MiscFlags = 0;
			hr = mDevice->CreateTexture2D(&description, NULL, &mRealTexture);
			if (FAILED(hr)) {
				if (mRealTexture) {
					mRealTexture->Release();
					mRealTexture = nullptr;
				}
				return NULL;
			}
		}
		mImmediateContext->CopyResource(mRealTexture, texture2D);

		if (mScaledTexture == nullptr) {
			D3D11_TEXTURE2D_DESC description;
			texture2D->GetDesc(&description);
			description.CPUAccessFlags = D3D11_CPU_ACCESS_READ | D3D11_CPU_ACCESS_WRITE;
			description.BindFlags = D3D11_BIND_RENDER_TARGET | D3D11_BIND_SHADER_RESOURCE;
			description.Width = 1440;
			description.Height = 585;
			description.MipLevels = 4;
			description.ArraySize = 1;
			description.SampleDesc.Count = 1;
			description.SampleDesc.Quality = 0;
			description.Usage = D3D11_USAGE_DEFAULT;
			hr = mDevice->CreateTexture2D(&description, NULL, &mScaledTexture);
			if (FAILED(hr)) {
				if (mScaledTexture) {
					mScaledTexture->Release();
					mScaledTexture = nullptr;
				}
				return NULL;
			}
		} //How to copy the mRealTexture to the mScaledTexture and get the new buffer ?

		D3D11_MAPPED_SUBRESOURCE mapped;
		hr = mImmediateContext->Map(mRealTexture, 0, D3D11_MAP_READ_WRITE, 0, &mapped);
		if (FAILED(hr)) {
			mRealTexture->Release();
			mRealTexture = NULL;
			return NULL;
		}
		unsigned char *source = static_cast<unsigned char *>(mapped.pData);

Thank you very much for your help.

This is not a good place to ask question about the Direct3D API. You should try either on https://www.gamedev.net/forum/10-directx-and-xna/  or https://gamedev.stackexchange.com/
But bear in mind that if you are trying to use such a low level API, you will need to learn a bit more the Direct3D API and/or how to perform image manipulation in memory and/or use an existing library to do this, otherwise it is going to be difficult to get any help on a forum.


Hide tax forms/banking info from staff, only showing finance/admins

Today finance had requested that sensitive forms like tax forms & banking info when uploaded in the project documents only be visible to them. It would be nice if PMs and other staff could still see that status (uploaded/not uploaded), just not the document itself.

Make sense. We should add a setting for this. By default I think staff should see it but with the setting it can be hidden.
Most organisations are far smaller than OTF and the same person does many roles.

Or we add a optional setting to the contract document categories to restrict permissions.

Add a CONTRACT_DOCUMENT_VIEW_ACCESS_STAFF, default to True.

@wes-otf Contract and Finance always need access to these documents I assume? Finance has no access today but should I think, if it is banking info e.g.?


New version: foxglove.studio version 1.13.1

Result: Installation Successful

Manifest
Add/Remove Programs

Name
Foxglove Studio
Foxglove Studio 1.13.1

Version
1.13.1
1.13.1

Publisher
Foxglove Technologies
Foxglove Technologies

ProductCode

b1a22fb8-f6f3-5e1f-b388-958085c08782

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 1856
Microsoft Reviewers: Open in CodeFlow

@wingetbot run


[BugFix] fix lake primary key update state leak

Fix update state leak when latest tablet_metadata not in cache.
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

@Mergifyio backport branch-3.1


Optional live server start

As per #33.

[x] Add options to prevent live_server from starting
[x] Test --start-live-server/--no-start-live-server options
[x] Add note into documenation about available options.

@EliRibble new release is available on pypi :tada:


Build Test against sample repos: CloudFormation

Description
As a dev on the seCureLI team, I want the build pipeline to check the tool against known ‘bad state’ repos, to ensure that the tool is not only passing unit tests and ‘not failing others’, but also that it is actively catching security issues, to ensure that the project is doing what it was designed to do.
Technical Details

Will require finding, or creating git repos that the pipeline can access that have secrets embedded in them.
create repo as part of the Secure Build project
Language Supported: CloudFormation
Should only cover detect-secrets errors

Acceptance Criteria

Repo identified or created with the supporting language with 1+ secrets saved to it (fake secrets, of course)
When the tool runs and successfully throws and error (expected behavior) the build does not fail.
If the tool runs and does NOT throw an error (unexpected behavior) the build fails, as the tool did not properly detect the error.

Closing out as this will be addressed in https://github.com/slalombuild/secureli/issues/129.


TextBox InputValidationKind="Inline" not properly aligned

Describe the bug

When applying InputValidationKind="Inline" on a TextBox, the error message is right-aligned and cut off
Steps to reproduce the bug

Steps to reproduce the behavior:
Xaml:
<TextBox InputValidationKind="Inline" Header="Test" Text="{x:Bind ViewModel.Test1, Mode=TwoWay}" HorizontalAlignment="Left" MaxWidth="200" />
ViewModel property:
[Required]
[EmailAddress(ErrorMessage = "Invalid email address")]
public string Test1
{
    get => _Test1;
    set { SetField(ref _Test1, value); Validate(value); }
}

Implement INotifyDataErrorInfo on ViewModel
Expected behavior

Left aligned error text
Screenshots

Version Info

NuGet package version:

Windows app type:

UWP
Win32

Yes

Windows 10 version
Saw the problem?

Insider Build (xxxxx)

October 2020 Update (19042)
Yes

May 2020 Update (19041)

November 2019 Update (18363)

May 2019 Update (18362)

October 2018 Update (17763)

April 2018 Update (17134)

Fall Creators Update (16299)

Creators Update (15063)

Device form factor
Saw the problem?

Desktop
Yes

Xbox

Surface Hub

IoT

Additional context

InputValidation ErrorTemplate option is missing for customization

I was actually under the impression that input validation wasn't supported in winui3, but it seems to be working albeit with this bug.  @MikeHillberg @Austin-Lamb @ryandemopoulos

I was actually under the impression that input validation wasn't supported in winui3, but it seems to be working albeit with this bug. @MikeHillberg @Austin-Lamb @ryandemopoulos

I think there may be limited support at first, with fuller support post 3.0 release

Yes, it's still in preview, not in release yet.

I updated to the 0.5 official release.   The InputValidationXXXX properties have been removed, so I'll close this for now

@omnilogix the input validation api's are preview, so they are not included in release builds, only prerelease. hence why they are not in the 0.5 official release.

Any progress on this item?

Tied to Parent Issue: https://github.com/microsoft/microsoft-ui-xaml/issues/179


Update README of github action sechub scan #2102

closes #2102

Had the same issue following the current documentation. This fixed it
Thanks!


feat: #check tactic

This provides a tactic version of the #check command. The term provided to #check may refer to local variables in the proof.
This is similar to how #find is both a command and a tactic.

bors merge


MADS: improvements on the state machine

MADS Lateral Control: All Critical States
1. Final Output Truth Table (mads_is_lateral_control_allowed_by_mads)

system_enabled
controls_allowed_lat
Is lat allowed?

false
false
NO - System disabled

false
true
NO - Invalid state, cannot occur

true
false
NO - Controls not permitted

true
true
YES - Active lateral control

2. Control Permission State (m_can_allow_controls_lat) - When system_enabled = true

current_disengage.reason
is_braking
disengage_lateral_on_brake
Is lat allowed?

NONE
*
*
YES - No disengagement active

LAG
*
*
YES - LAG doesn't prevent control

BUTTON
*
*
YES - BUTTON doesn't prevent control

ACC_MAIN_OFF
*
*
YES - ACC_MAIN_OFF doesn't prevent control

BRAKE
true
true
NO - Active brake blocking

BRAKE
false
true
YES - Brake released

BRAKE
true
false
YES - Brake blocking disabled

BRAKE
false
false
YES - Both brake conditions inactive

3. Button Control Request States and Transitions
From m_update_button_state():
if (button.transition == MADS_EDGE_RISING) {
  const bool acc_active = *m_mads_state.acc_main.current;
  m_mads_state.controls_requested_lat = !m_mads_state.controls_allowed_lat;

  if (!m_mads_state.controls_requested_lat && !acc_active) {
    mads_exit_controls(MADS_DISENGAGE_REASON_BUTTON);
  }
}

button_transition
controls_allowed_lat
acc_active
Result
Action Taken

NOT_RISING_EDGE
any
any
NO CHANGE
None - Only rising edge matters

RISING_EDGE
false
true
REQUEST
controls_requested_lat = true

RISING_EDGE
false
false
REQUEST
controls_requested_lat = true

RISING_EDGE
true
true
NO CHANGE
controls_requested_lat = false, but no disengage

RISING_EDGE
true
false
DISENGAGE
controls_requested_lat = false AND mads_exit_controls(BUTTON)

4. ACC Main State Changes
From m_update_binary_state():
static void m_update_binary_state(BinaryStateTracking *state) {
  EdgeTransition transition = m_get_edge_transition(*state->current, state->previous);
  if (transition == MADS_EDGE_RISING) {
    m_mads_state.controls_requested_lat = true;
  } else if (transition == MADS_EDGE_FALLING) {
    m_mads_state.controls_requested_lat = false;
    mads_exit_controls(MADS_DISENGAGE_REASON_ACC_MAIN_OFF);
  }

  state->previous = *state->current;
}

acc_main_transition
controls_allowed_lat
Result
Action Taken

NO_CHANGE
any
NO CHANGE
None - Only edges matter

RISING_EDGE
false
REQUEST
controls_requested_lat = true

RISING_EDGE
true
NO CHANGE
controls_requested_lat = true (redundant)

FALLING_EDGE
false
NO CHANGE
controls_requested_lat = false

FALLING_EDGE
true
DISENGAGE
controls_requested_lat = false AND mads_exit_controls(ACC_MAIN_OFF)

5. Complete Control Request Resolution

controls_requested_lat
m_can_allow_controls_lat
already_allowed
Will controls be allowed?

false
false
false
NO - Not requested

false
true
false
NO - Not requested

true
false
false
NO - Cannot allow yet

true
true
false
YES - New control granted

false
any
true
NO - Will lose control

true
false
true
YES - Maintains existing control

true
true
true
YES - Maintains control

6. Brake Impact States

is_braking
was_braking
vehicle_moving
disengage_lateral_on_brake
Will controls be lost?

false
any
any
any
NO

true
true
false
true
NO - Already handled

true
true
true
true
YES - Moving with brake

true
false
any
true
YES - New brake press

true
any
any
false
NO - Brake blocking disabled

7. Disengage Reason State Machine
7.1 Setting Disengage Reasons
if (m_mads_state.controls_allowed_lat) {
  m_mads_state.previous_disengage = m_mads_state.current_disengage;
  m_mads_state.current_disengage.reason = reason;
  m_mads_state.controls_allowed_lat = false;
}

7.2 Clearing Disengage Reasons
if (m_mads_state.controls_requested_lat && !m_mads_state.controls_allowed_lat && m_can_allow_controls_lat()) {
  m_mads_state.controls_allowed_lat = true;
  m_mads_state.previous_disengage = m_mads_state.current_disengage;
  m_mads_state.current_disengage.reason = MADS_DISENGAGE_REASON_NONE;
}

7.3 Disengage Reason Transitions

Current Reason
Event
New Reason
Controls Allowed?
Notes

NONE
Button press when !acc_active
BUTTON
NO
From m_update_button_state

NONE
ACC main off
ACC_MAIN_OFF
NO
From m_update_binary_state

NONE
Brake press when disengage_lateral_on_brake=true
BRAKE
NO
From m_mads_check_braking

NONE
Brake press when disengage_lateral_on_brake=false
NONE
YES
Braking doesn't affect control

BRAKE
Brake release when disengage_lateral_on_brake=true
NONE
YES
Auto-restores when brake released

BUTTON
ACC turns on + new request
NONE
YES
Via m_can_allow_controls_lat

ACC_MAIN_OFF
ACC turns on + new request
NONE
YES
Via m_can_allow_controls_lat

Any
New disengage event
New Reason
NO
Previous reason saved

Key behavior differences:

With disengage_lateral_on_brake = false:

Braking never causes disengagement
BRAKE reason never gets set

With disengage_lateral_on_brake = true:

Braking causes immediate disengagement
Controls auto-restore when brake is released
No explicit re-request needed

8. mads_state_update() Full Sequence
8.1 Function Input Parameters
void mads_state_update(
    const bool *op_vehicle_moving,
    const bool *op_acc_main,
    bool is_braking,
    bool cruise_engaged  // Currently unused
)

8.2 Initialization Steps
m_mads_state.is_vehicle_moving_ptr = op_vehicle_moving;
m_mads_state.acc_main.current = op_acc_main;
m_mads_state.main_button.current = &main_button_press;
m_mads_state.lkas_button.current = &lkas_button_press;

8.3 Button State Flag Updates
if (!(m_mads_state.state_flags & MADS_STATE_FLAG_MAIN_BUTTON_AVAILABLE) &&
    (main_button_press != MADS_BUTTON_UNAVAILABLE)) {
    m_mads_state.state_flags |= MADS_STATE_FLAG_MAIN_BUTTON_AVAILABLE;
}

if (!(m_mads_state.state_flags & MADS_STATE_FLAG_LKAS_BUTTON_AVAILABLE) &&
    (lkas_button_press != MADS_BUTTON_UNAVAILABLE)) {
    m_mads_state.state_flags |= MADS_STATE_FLAG_LKAS_BUTTON_AVAILABLE;
}

8.4 Update Sequence (in order of execution)

Button State Updates:

m_update_button_state(&m_mads_state.main_button);
m_update_button_state(&m_mads_state.lkas_button);

Effects:

Can set controls_requested_lat true/false
Can trigger BUTTON disengage
Button transitions only processed if RISING edge

ACC Main Update:

m_update_binary_state(&m_mads_state.acc_main);

Effects:

RISING edge sets controls_requested_lat true
FALLING edge forces controls_requested_lat false and disengages with ACC_MAIN_OFF

Brake Check:

m_mads_check_braking(is_braking);

Effects:

If disengage_lateral_on_brake true:

New brake OR moving vehicle causes BRAKE disengage

Updates is_braking state

Control Permission Check:

m_mads_try_allow_controls_lat();

Effects:

If controls requested AND not allowed AND can allow:

Grants control permission
Clears disengage reason to NONE

8.5 Critical Timing Dependencies

Button handling occurs first:

Can request OR cancel controls before other checks
Button disengage takes precedence over ACC state

ACC main processed second:

Can override button's control request
FALLING edge always disengages regardless of button state

Brake check third:

Can disengage even if buttons/ACC just requested control
Only matters if disengage_lateral_on_brake true

Final permission check last:

Only proceeds if all previous steps allow it
Auto-restores control if conditions permit

This sequence means:

ACC main off always wins over button requests
Brake (if enabled) can override both button and ACC
Control permission only granted if all conditions remain satisfied after all updates

Updated version in https://github.com/sunnypilot/panda/pull/52


badge-danger showing on icon to the right

In the demo ( https://startbootstrap.com/previews/sb-admin/ ) , the badge-danger for "9+" shows for the mail icon. However that should be showing up next to the bell: https://github.com/BlackrockDigital/startbootstrap-sb-admin/blob/35a0cb5b69fd7630a2b587bd6b063b75f17f3721/index.html#L52
The "7" badge is defined under mail and shows on the user portrait. So all of them are offset by one to the right.

(Tested on latest Chrome -- Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/76.0.3809.62 Safari/537.36 -- Also Safari with same behavior)

Same happening here, any updates on this?
Different browsers make no difference, and it used to work fine.


Own search function as an alternative to fuse.js

Es wäre cool, eigene Suchfunktion zu verwenden anstatt fuse.js zu nutzen. Ein großes Problem ist z.B. folgendes
const list = [{ product: "Nike Trail Running Shoes" }]
const options = {
includeScore: true,
ignoreLocation: true,
keys: ["product"],
};
const fuse = new Fuse(list, options);
return fuse.search(pattern);
If pattern = "Nike" score will be 0.03
But if pattern = "Nike shoes" score will be 0.655
I want "Nike shoes" to get a better score than "Nike", since it contains both Nike and shoes
https://stackoverflow.com/questions/74776336/how-to-split-the-pattern-with-fuse-js

The search backend can be completely replaced by setting instance._searcher in the callbackOnInit method. You probably can just monkey patch instance._searcher.search() method
The fuse search implementation is found in this file:
https://github.com/Choices-js/Choices/blob/5fa376b2f902594bc75de268d545c70d11ce8d51/src/scripts/search/fuse.ts


deps: Update to streams3 API

Changed

BREAKING: Consolidate on streams API v3. All streams are now using and expecting compatibility with<EMAIL_ADDRESS>
https://www.npmjs.com/package/readable-stream#version-3xx

Update extension-port-stream from ^2.1.1 to ^3.0.0

CHANGELOG

Update json-rpc-middleware-stream from ^4.2.3 to ^5.0.1

CHANGELOG

Update @metamask/object-multiplex from ^1.3.0 to ^2.0.0

CHANGELOG

Add direct dependency on<EMAIL_ADDRESS>
The package is previously mixing usage of readable-stream@2, readable-stream@3 and Node.js native streams (the API and behavior of which differ depending on Node.js version). This consolidates all internal streams on portable readable-stream.

I mean, the tests pass. We probably want to test this locally in extension and see what happens. I imagine it'll just work though

Tested locally. Seems to work fine


Fix variables binding

fix #76

Coverage remained the same at 98.039% when pulling a857b6c1c9f785acf052be8ffdb9e48626de0936 on fix-variables-binding into 24eaadcced86bc7bcb1fe68d460e2cdfebe2e3d4 on master.


New version: Fossil.Fossil version 2.23

Pull request has been created with komac v2.1.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Packages\Fossil.Fossil__DefaultSource\fossil.exe returned exit code: 1
Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\fossil.exe returned exit code: 1
Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Packages\Fossil.Fossil__DefaultSource\fossil.exe returned exit code: 1
Executable C:\Users\Validator\AppData\Local\Microsoft\WinGet\Links\fossil.exe returned exit code: 1

(Automated response - build 870.)

Enter a pull request number: 145592

Manifest validation succeeded.
Found Fossil [Fossil.Fossil] Version 2.23
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://fossil-scm.org/home/uv/fossil-w64-2.23.zip
  ██████████████████████████████  3.22 MB / 3.22 MB
Successfully verified installer hash
Extracting archive...
Successfully extracted archive
Starting package install...
Command line alias added: "fossil"
Path environment variable modified; restart your shell to use the new value.
Successfully installed

Name          : Fossil
Publisher     : D. Richard Hipp
Version       : 2.23
ProductCode   : Fossil.Fossil__DefaultSource
Registry Path : Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\Fossil.Fossil__DefaultSource
Uninstall     : winget uninstall --id "Fossil.Fossil__DefaultSource"

Press any key to continue . . .

Nothing does indeed happen when you execute fossil.exe

Yes -

Many applications have a non-zero exit code, for one reason or another. Especially CLI applications when run without an argument. These are so common that I've had an auto-waiver system to keep them going, and I need to set it up again.
SmartScreen prompts aren't blockers. They're disabled in the pipeline and I click through them in my VMs.

@wingetbot waivers Add Validation-Executable-Error

The exe is not supposed to be launched, use fossil in cmd.


Support operations without operationId

We always assume each operation has an operationId. However, according to the OAS spec, it's not actually required. We should provide a fallback for these cases.

+1

Still relevant


HBASE-28898. Use reflection to access recoverLease(), setSafeMode() APIs. (#6342)

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 44s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
hbaseanti
0m  0s

Patch does not have any anti-patterns.

_ branch-2.6 Compile Tests _

+0 :ok:
mvndep
0m 14s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 18s

branch-2.6 passed

+1 :green_heart:
compile
3m 15s

branch-2.6 passed

+1 :green_heart:
checkstyle
0m 48s

branch-2.6 passed

+1 :green_heart:
spotbugs
2m  0s

branch-2.6 passed

+1 :green_heart:
spotless
0m 48s

branch has no errors when running spotless:check.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m  1s

the patch passed

+1 :green_heart:
compile
3m 15s

the patch passed

+1 :green_heart:
javac
3m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m  8s

The patch passed checkstyle in hbase-asyncfs

+1 :green_heart:
checkstyle
0m 37s

hbase-server: The patch generated 0 new + 11 unchanged - 1 fixed = 11 total (was 12)

+1 :green_heart:
spotbugs
2m 13s

the patch passed

+1 :green_heart:
hadoopcheck
16m 30s

Patch does not cause any errors with Hadoop 2.10.2 or 3.3.6 3.4.0.

+1 :green_heart:
spotless
0m 46s

patch has no errors when running spotless:check.

_ Other Tests _

+1 :green_heart:
asflicense
0m 18s

The patch does not generate ASF License warnings.

39m 59s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6392/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6392

Optional Tests
dupname asflicense javac spotbugs checkstyle codespell detsecrets compile hadoopcheck hbaseanti spotless

uname
Linux ec0f93c8d696 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.6 / 5db43f798664dc2ee70ae2c5f3434c0790cff219

Default Java
Eclipse Adoptium-11.0.23+9

Max. process+thread count
79 (vs. ulimit of 30000)

modules
C: hbase-asyncfs hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6392/1/console

versions
git=2.34.1 maven=3.9.8 spotbugs=4.7.3

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 47s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2.6 Compile Tests _

+0 :ok:
mvndep
0m 10s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 10s

branch-2.6 passed

+1 :green_heart:
compile
1m 10s

branch-2.6 passed

+1 :green_heart:
javadoc
0m 38s

branch-2.6 passed

+1 :green_heart:
shadedjars
5m 50s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 15s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 57s

the patch passed

+1 :green_heart:
compile
1m  9s

the patch passed

+1 :green_heart:
javac
1m  9s

the patch passed

+1 :green_heart:
javadoc
0m 37s

the patch passed

+1 :green_heart:
shadedjars
5m 47s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 59s

hbase-asyncfs in the patch passed.

+1 :green_heart:
unit
199m 45s

hbase-server in the patch passed.

227m 12s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6392/1/artifact/yetus-jdk17-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6392

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux e0df25e9b187 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.6 / 5db43f798664dc2ee70ae2c5f3434c0790cff219

Default Java
Eclipse Adoptium-17.0.11+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6392/1/testReport/

Max. process+thread count
4523 (vs. ulimit of 30000)

modules
C: hbase-asyncfs hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6392/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 47s

Docker mode activated.

-0 :warning:
yetus
0m  4s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2.6 Compile Tests _

+0 :ok:
mvndep
0m 10s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
2m 30s

branch-2.6 passed

+1 :green_heart:
compile
0m 54s

branch-2.6 passed

+1 :green_heart:
javadoc
0m 35s

branch-2.6 passed

+1 :green_heart:
shadedjars
5m 15s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 22s

the patch passed

+1 :green_heart:
compile
0m 54s

the patch passed

+1 :green_heart:
javac
0m 54s

the patch passed

+1 :green_heart:
javadoc
0m 34s

the patch passed

+1 :green_heart:
shadedjars
5m 13s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m 12s

hbase-asyncfs in the patch passed.

+1 :green_heart:
unit
212m 49s

hbase-server in the patch passed.

237m 50s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6392/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6392

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux f71b19e71ce8 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.6 / 5db43f798664dc2ee70ae2c5f3434c0790cff219

Default Java
Temurin-1.8.0_412-b08

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6392/1/testReport/

Max. process+thread count
4174 (vs. ulimit of 30000)

modules
C: hbase-asyncfs hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6392/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 45s

Docker mode activated.

-0 :warning:
yetus
0m  5s

Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --author-ignore-list --blanks-eol-ignore-file --blanks-tabs-ignore-file --quick-hadoopcheck

_ Prechecks _

_ branch-2.6 Compile Tests _

+0 :ok:
mvndep
0m 12s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m  5s

branch-2.6 passed

+1 :green_heart:
compile
1m  4s

branch-2.6 passed

+1 :green_heart:
javadoc
0m 39s

branch-2.6 passed

+1 :green_heart:
shadedjars
5m 50s

branch has no errors when building our shaded downstream artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 48s

the patch passed

+1 :green_heart:
compile
1m  3s

the patch passed

+1 :green_heart:
javac
1m  3s

the patch passed

+1 :green_heart:
javadoc
0m 37s

the patch passed

+1 :green_heart:
shadedjars
5m 47s

patch has no errors when building our shaded downstream artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m  8s

hbase-asyncfs in the patch passed.

+1 :green_heart:
unit
212m 54s

hbase-server in the patch passed.

240m 17s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6392/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/6392

Optional Tests
javac javadoc unit compile shadedjars

uname
Linux 2f627e81bd5d 5.4.0-1103-aws #111~18.04.1-Ubuntu SMP Tue May 23 20:04:10 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2.6 / 5db43f798664dc2ee70ae2c5f3434c0790cff219

Default Java
Eclipse Adoptium-11.0.23+9

Test Results
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6392/1/testReport/

Max. process+thread count
4405 (vs. ulimit of 30000)

modules
C: hbase-asyncfs hbase-server U: .

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-6392/1/console

versions
git=2.34.1 maven=3.9.8

Powered by
Apache Yetus 0.15.0 https://yetus.apache.org

This message was automatically generated.


Replaced activity diagram in implementation section

Coverage remained the same at 57.438% when pulling 56e12dad08cd3eb0551dec627906bb2a50e95d0d on tristyxxnana:v1.4implementation into 221880a9bc1460ecfe7e722235e577754805f01d on CS2113-AY1819S1-T16-1:master.


Stadia Controller Support

Input device?
Stadia Controller
Input device ID?
DInput/0/Stadia Controller rev. A
Operating System?
Windows 11
What is the key assignment.
I'm quite a big fan of Stadia and the controller itself. It'd be pretty nice to see it as an option for within this project. Here's a general look and layout of the entire controller:

This is the what the buttons correspond to within Windows and Dolphin:
"Button 0" = A
"Button 1" = B
"Button 2" = X
"Button 3" = Y
"Button 4" = L1
"Button 5" = R1
"Button 6" = L3
"Button 7" = R3
"Button 8" = Options
"Button 9" = Menu
"Button 10" = Stadia Button (Guide Button)
"Button 11" = R2
"Button 12" = L2
"Button 13" = Google Assistant Button
"Button 14" = Screenshot Button
"Button 15" = N/A
"Hat 0 N" = D-Pad Up
"Hat 0 E" = D-Pad Right
"Hat 0 S" = D-Pad Down
"Hat 0 W" = D-Pad Left
"Axis Zr-" = Right Stick Up
"Axis Zr+" = Right Stick Down
"Axis Z+" = Right Stick Right
"Axis Z-" = Right Stick Left
"Axis X-" = Left Stick Left
"Axis X+" = Left Stick Right
"Axis Y+" = Left Stick Down
"Axis Y-" = Left Stick Up

A few note worthy issues:
-Windows Recognizes L2 and R2 as digital buttons despite being fully analog.
-There is no vibration detected in Dolphin
(On https://gamepad-tester.com/ it recognizes the triggers as analog and even offers vibration. Genuinely not sure why or how.)
Here are some super basic glyphs:
Google Stadia.zip
If you'd like some additional testing, I'm more than willing to do so. Thanks!

that looks very understandable. 👍
I do not know yet how I have time so I expect a few weeks.

-Windows Recognizes L2 and R2 as digital buttons despite being fully analog.
-There is no vibration detected in Dolphin

these errors will come from the drivers used in windows.


mdp: 1.0.12 -> 1.0.13

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/mdp/versions.
meta.description for mdp is: '"A command-line based markdown presentation tool"'.
Compare changes on GitHub

Checks done (click to expand)

built on NixOS
/nix/store/8z8hgiwnavd342x3gy86vmr2q074lxmd-mdp-1.0.13/bin/mdp passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
directory tree listing: https://gist.github.com/980fd55a364bcdedcef7d414348793a6
du listing: https://gist.github.com/174eba2c38fd3a15435f023c6642757a

Test this build with Cachix (click to expand)

One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout 0a959bd8280be08b5553496a506fec257c8bda74 && nix-shell --pure -I nixpkgs=. -p mdp

cc @vrthra for testing.

Success on x86_64-linux (full log)
Attempted: mdp
Partial log (click to expand)
install -m 644 mdp.1 /nix/store/8z8hgiwnavd342x3gy86vmr2q074lxmd-mdp-1.0.13/share/man/man1/mdp.1
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/8z8hgiwnavd342x3gy86vmr2q074lxmd-mdp-1.0.13
shrinking /nix/store/8z8hgiwnavd342x3gy86vmr2q074lxmd-mdp-1.0.13/bin/mdp
gzipping man pages under /nix/store/8z8hgiwnavd342x3gy86vmr2q074lxmd-mdp-1.0.13/share/man/
strip is /nix/store/1hi76hr87bd1y1q1qjk0lv8nmcjip1c8-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/8z8hgiwnavd342x3gy86vmr2q074lxmd-mdp-1.0.13/bin
patching script interpreter paths in /nix/store/8z8hgiwnavd342x3gy86vmr2q074lxmd-mdp-1.0.13
checking for references to /build in /nix/store/8z8hgiwnavd342x3gy86vmr2q074lxmd-mdp-1.0.13...
/nix/store/8z8hgiwnavd342x3gy86vmr2q074lxmd-mdp-1.0.13

Success on x86_64-darwin (full log)
Attempted: mdp
Partial log (click to expand)
install -d /nix/store/6a8g3qisc9gy3c4w153vgahj1i2isfqp-mdp-1.0.13/bin
install -m 755 mdp /nix/store/6a8g3qisc9gy3c4w153vgahj1i2isfqp-mdp-1.0.13/bin/mdp
install -d /nix/store/6a8g3qisc9gy3c4w153vgahj1i2isfqp-mdp-1.0.13/share/man/man1
install -m 644 mdp.1 /nix/store/6a8g3qisc9gy3c4w153vgahj1i2isfqp-mdp-1.0.13/share/man/man1/mdp.1
post-installation fixup
gzipping man pages under /nix/store/6a8g3qisc9gy3c4w153vgahj1i2isfqp-mdp-1.0.13/share/man/
strip is /nix/store/qfxcr8c4fg7lkybrny9n2sb77bmippdx-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/6a8g3qisc9gy3c4w153vgahj1i2isfqp-mdp-1.0.13/bin
patching script interpreter paths in /nix/store/6a8g3qisc9gy3c4w153vgahj1i2isfqp-mdp-1.0.13
/nix/store/6a8g3qisc9gy3c4w153vgahj1i2isfqp-mdp-1.0.13

Success on aarch64-linux (full log)
Attempted: mdp
Partial log (click to expand)
install -m 644 mdp.1 /nix/store/1k0347n227bfrfhdq2k6f714hxcdsw0z-mdp-1.0.13/share/man/man1/mdp.1
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/1k0347n227bfrfhdq2k6f714hxcdsw0z-mdp-1.0.13
shrinking /nix/store/1k0347n227bfrfhdq2k6f714hxcdsw0z-mdp-1.0.13/bin/mdp
gzipping man pages under /nix/store/1k0347n227bfrfhdq2k6f714hxcdsw0z-mdp-1.0.13/share/man/
strip is /nix/store/zrs21zqcchgyabjf4xfimncdq16njizc-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/1k0347n227bfrfhdq2k6f714hxcdsw0z-mdp-1.0.13/bin
patching script interpreter paths in /nix/store/1k0347n227bfrfhdq2k6f714hxcdsw0z-mdp-1.0.13
checking for references to /build in /nix/store/1k0347n227bfrfhdq2k6f714hxcdsw0z-mdp-1.0.13...
/nix/store/1k0347n227bfrfhdq2k6f714hxcdsw0z-mdp-1.0.13


Fix Swift Compiler Error in handlePacUrl Function

This PR addresses a Swift compiler error in the handlePacUrl function within the SwiftFlutterSystemProxyPlugin.swift file. The error was caused by the inability to convert an Unmanaged<CFRunLoopSource> to the expected argument type CFRunLoopSource?.
Changes:

Updated the handlePacUrl function to correctly convert the Unmanaged<CFRunLoopSource> to CFRunLoopSource? using the takeUnretainedValue() method.

This fix ensures that the code compiles successfully and the proxy configuration is handled correctly.

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


Purpose of tf.identity

Why is tf.identity necessary in some cases in your code, such as here
https://github.com/affinelayer/pix2pix-tensorflow/blob/master/pix2pix.py#L119

Well, as explained in the comment above it I assume it is so that the Graph is correctly generated (you can try commenting that line and use Tensorboard to see if the Graph changes).

Can you explain why the graph would change though? Shouldn't an identity not have aany effect?


Update release checklists

Can do further iterations + move some items to the new T-5 checklist that will be added via https://github.com/mattermost/docs/pull/3415 in a follow-up PR once these both are merged.
This is to help accountability and that all checklist items are done on time.

Experience. Some items get normally done earlier or later in the process so I moved them accordingly. A few minor items are invalid so I removed them. This way items will get marked as done on time.
Done.
Hard to add since there's 5 or more different repos and they are different each release.

@amyblais Not merging, as I wasn't sure if you wanted to have anyone else review prior to merge,


Update terminology

Purpose
Removal of terms and unclear terminology that would only confuse the user.
Changes

Updated terminology and removed some terms from the Ledger display that the user did not have a chance of verifying.
Export of private key seeds (PRF key and IdCredSec seeds) have been refactored so that either the PRF key can be exported, or both of them in one command. This means that old versions of the desktop wallet will be incompatible with this version of the Ledger application.

Checklist

[x] My code follows the style of this project.
[x] The code compiles without warnings.
[x] I have performed a self-review of the changes.
[x] I have documented my code, in particular the intent of the
hard-to-understand areas.
[x] (If necessary) I have updated the CHANGELOG.

Added export of prf key for recovery.


QdtViz Barchart tooltip

I am using QdtViz for a barchart using ID.  When I have multiple dimension the tool tip is showing some functions as in image attached. I am using a Feb 2019 Release Qlik sense. I have tried using the same chart on simple mashup in Dev hub and is working fine

@fkabinoff  @yianni-ververis  Sorry guys I am not sure if this is the right way to seek help. Can you please help me on this issue

This seems to be a Qlik Sense issue from the Capability API since all QdtComponent does is use the getObject method.
TBH I have never seen that before

Yeah I checked the same objectid via mashup editor and its working fine. I have problem only when using qdt and that function is displayed when i have more than one dimension. Can you advice how can i confirm or is there any chance of version issues

Take that mashup from the editor and run it on a different server

i ran mashup on my laptop and its working good except for the styling

Is there any chance of version issues between Qdt and our Qlik

or I think it could be any of the package on our internal application conflicting


Bold Styling in Script Not Working

Describe the bug
In some sections of the script, the bold styling tag arere shown and is not making text bold.
What I have found so far is below in the screenshots / logs section but there could be more.
To Reproduce
Run the scriptand scrape a model's profile.
Expected behavior
That text should be bold where those bold tags exist and are not shown back to the user.
Screenshots/Logs
[bold] starting script [/bold]
[bold]Model Name Here[/bold] (Download Size) (x downloads total [x videos, x audios, x photos]  x skipped, x failed)
[bold]Subscription Active:[/bold] True
[bold] Script Finished [/bold]
Run Time:  [bold]Time Here/bold]
Desktop (please complete the following information):

OS: Windows 11
Version: 3.6.6
Python
Pipx

Additional context
N/A

This is a good reminder to remove them from discord

The bold would only work on the console since it is processed through rich

This is using powershell not discord though

Okay I'll have to look into it

@datawhores Don't know if you pushed a fix for this in the latest version but in 3.6.8 the bold text is working as intended.


version of jaxb-xjc

could you please upgrade:
jaxb-xjc:3.0.0-M4
to:
jaxb-xjc:3.0.0
?
I think the jaxb-xjc:3.0.0 is more official than 3.0.0-M4. And it contain some feature I need.

https://github.com/unbroken-dome/gradle-xjc-plugin/blob/82c1d69e0de91d11a61ae6153f89491adafa3a84/build.gradle.kts#L65
https://github.com/unbroken-dome/gradle-xjc-plugin/blob/82c1d69e0de91d11a61ae6153f89491adafa3a84/src/main/kotlin/org/unbrokendome/gradle/plugins/xjc/XjcPlugin.kt#L42
And It is not configurable.

Attempted and failed using the xjcTool
xjcTool 'com.sun.xml.bind:jaxb-xjc:4.0.1'
Caused by: java.lang.IllegalStateException: Cannot handle XJC version: 4.0
at org.unbrokendome.gradle.plugins.xjc.XjcGenerate.generate(XjcGenerate.kt:199)

At this time (version 2.0.0), I can generate and compile JAXB for newer versions with:
xjc.xjcTool=com.sun.xml.bind:jaxb-xjc:3.0.2
xjc.xjcVersion=3.0
xjc.targetVersion=3.0

Also you can do:
xjc.xjcTool=com.sun.xml.bind:jaxb-xjc:4.0.2
xjc.xjcVersion=3.0
xjc.targetVersion=4.0

Use of xjc.xjcVersion appears required to get the jakarta package namespace output, even if the documentation indicates when specifying xjc.xjcTool that use of xjcVersion is not needed.  I also have in Gradle implementation classPath jakarta.xml.bind:jakarta.xml.bind-api:3.0.1  or 4.0.0 accordingly.
HTH

All the matters reported here should be addresses in PR #47  (XJC tool version compatibility with 3.x and 4.x in the jarkarta era)

I have migrated from this repository to writing my own jaxb code how it is described in this old repository https://roytuts.com/generating-jaxb-classes-from-xsd-using-gradle/
I have full controll over the jaxb version I am using and I am not depending on this project.
It feels like this repository is no longer maintened. (last commit 3 years ago)
The solution described in the tutorial is simple and works with spring boot 3 and java 17.


Rename internal property to remove any possible confusion with RawRepresentable.

Since enums can conform to RawRepresentable which has a rawValue property, this was renamed to pathComponent which is also a better description.

Looks great :ship:


Add "Fork us" button to home webpage

Right now gh-pages branch has the web documentation of scikit-api. It's better if we can add a "Fork Us" button at the top of the web page as most of the documentation websites do these days.
That button will redirect the user to a new tab with this repository on github

@dilumn Working on it

Kindly Test and look at
https://github.com/99xt/scikit-api/pull/54

@denzelwamburu Could you please add that button Right aligned on top of the Home page as well?

@dilumn  okay great.


Added more languages in historical events

#21 #102

Added seven languages in historical events category.
Added a pro tip in historical events category.

Thank you for expanding that section, merged!


[BUG] Force delete volume make SPDK disk unschedule

Describe the bug (🐛 if you encounter this issue)
When a SPDK volume is stuck at deleting state, force delete that volume(remove finalizers) will cause SPDK block disk unschedule
To Reproduce
Steps to reproduce the behavior:

Setup SPDK environment following steps
Create storage class longhorn-spdk
Create deployment by below manifest

deployment manifest
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
 name: vol1
 namespace: default
spec:
 accessModes:
   - ReadWriteOnce
 storageClassName: longhorn-spdk
 resources:
   requests:
     storage: 1Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
 name: test-deployment
 labels:
   name: test-deployment
spec:
 replicas: 1
 selector:
   matchLabels:
     name: test-deployment
 template:
   metadata:
     labels:
       name: test-deployment
   spec:
     containers:
       - name: test-deployment
         image: ubuntu:20.04
         stdin: true
         stdinOnce: false
         tty: true
         volumeMounts:
           - name: vol1
             mountPath: /mnt/data
     volumes:
       - name: vol1
         persistentVolumeClaim:
           claimName: vol1

Block the network traffic on a node which contain replica but not contain engine by command nohup <script name> 150

Block traffic script
#!/bin/bash

print_usage() {
    echo "Usage: nohup ./${0} [|-h|--help]  seconds"
    echo "Description: disconnect network for defined number of seconds"
    echo ""
    exit 0
}

check_sighup_ignored() {
    SIG_ING_HEX=`grep "SigIgn:.*$" /proc/$$/status | awk '{print $2}'`
    SIG_ING_BIN=`echo "obase=2; ibase=16; ${SIG_ING_HEX}" | bc`
    NOHUB_BIT=${SIG_ING_BIN: -1}

    if [[ ${NOHUB_BIT} -eq 1 ]]; then
        echo true
    else
        echo false
    fi
}

drop_network_traffic() {
    iptables -P INPUT DROP
    iptables -P FORWARD DROP
    iptables -P OUTPUT DROP
}

accept_network_traffic() {
    iptables -P INPUT ACCEPT
    iptables -P FORWARD ACCEPT
    iptables -P OUTPUT ACCEPT
}

SIGHUP_IGNORED=`"check_sighup_ignored"`
if [[ ${SIGHUP_IGNORED} = false ]] ; then
	echo "Err: script must be used with nohup to prevent being locked out by iptables"
	exit 1
fi

ARG=$1
case $ARG in
    "" | "-h" | "--help")
        print_usage
        ;;

    *)
	SLEEP_SEC=${ARG}
        if [[ ${SLEEP_SEC} == "" ]]; then
            print_usage
            exit 0
        fi
	drop_network_traffic
	sleep ${SLEEP_SEC}
	accept_network_traffic
        ;;
esac

During replica node have no internet access, delete deployment,  and delete volume
Volume stuck at deleting state even after the replica node have internet connection back
Force delete volume by remove finalizers
After volume remove, SPDK block disk on volume attached node become unscheduleable

Expected behavior
SPDK disk should still scheduleable
Log or Support bundle
describe node
    Spdk - Test:
      Conditions:
        Last Probe Time:
        Last Transition Time:  2023-06-13T01:45:24Z
        Message:               Disk spdk-test(/dev/loop5) on node ip-172-31-94-72 is not ready: failed to get disk config: error: rpc error: code = DeadlineExceeded desc = context deadline exceeded
        Reason:                NoDiskInfo
        Status:                False
        Type:                  Ready
        Last Probe Time:
        Last Transition Time:  2023-06-13T01:45:24Z
        Message:               the disk spdk-test(/dev/loop5) on the node ip-172-31-94-72 is not ready
        Reason:                DiskNotReady
        Status:                False
        Type:                  Schedulable
      Disk Type:               block
      Disk UUID:               7a1dc990-1867-435f-aa71-46061a743f3f

longhorn-manager
time="2023-06-13T01:58:12Z" level=info msg="Event(v1.ObjectReference{Kind:\"Node\", Namespace:\"longhorn-system\", Name:\"ip-172-31-94-72\", UID:\"22e8e2c0-2f16-4d63-ab6d-5c9e884f9dc0\", APIVersion:\"longhorn.io/v1beta2\", ResourceVersion:\"6261\", FieldPath:\"\"}): type: 'Warning' reason: 'Ready' Node ip-172-31-94-72 is down: the manager pod longhorn-manager-g95th is not running"
E0613 01:58:12.701997       1 volume_controller.go:4212] failed to get volume pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2 of replica pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-df235648 when enqueuing node ip-172-31-94-72: volume.longhorn.io "pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2" not found

supportbundle_b6a66181-9e96-4021-a773-b67644038572_2023-06-13T01-47-51Z.zip
Environment

Longhorn version: master, 1.5.x
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: 1.27

Number of management node in the cluster:
Number of worker node in the cluster:

Node config

OS type and version: ubuntu 22.02

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): AWS

Additional context
N/A

It seems caused by spdk_tgt.
2023-06-13T01:42:03.694752865Z [longhorn-instance-manager] time="2023-06-13T01:42:03Z" level=info msg="Deleting instance" backendStoreDriver=spdk cleanupRequired=true diskUuid=7a1dc990-1867-435f-aa71-46061a743f3f name=pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-df235648 type=replica
2023-06-13T01:42:13.482555524Z [2023-06-13 01:42:13.482256] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:42:23.482563819Z [2023-06-13 01:42:23.482226] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:42:24.122318177Z [longhorn-instance-manager] time="2023-06-13T01:42:24Z" level=info msg="Getting disk info" diskName=spdk-test diskPath=/dev/loop5 diskType=block
2023-06-13T01:42:33.482504974Z [2023-06-13 01:42:33.482202] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:42:43.482488971Z [2023-06-13 01:42:43.482176] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:42:53.482460977Z [2023-06-13 01:42:53.482157] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:43:03.482398470Z [2023-06-13 01:43:03.482116] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:43:13.482326090Z [2023-06-13 01:43:13.482086] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:43:23.482313062Z [2023-06-13 01:43:23.482058] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:43:33.482299866Z [2023-06-13 01:43:33.482036] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:43:43.482269902Z [2023-06-13 01:43:43.481995] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:43:53.482206937Z [2023-06-13 01:43:53.481965] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:44:03.482221569Z [2023-06-13 01:44:03.481939] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:44:13.482288432Z [2023-06-13 01:44:13.481911] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:44:23.482144521Z [2023-06-13 01:44:23.481886] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:44:33.482150970Z [2023-06-13 01:44:33.481848] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:44:43.482094843Z [2023-06-13 01:44:43.481822] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:44:53.481993330Z [2023-06-13 01:44:53.481794] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:45:03.482090288Z [2023-06-13 01:45:03.481766] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:45:03.688873884Z [longhorn-instance-manager] time="2023-06-13T01:45:03Z" level=info msg="Deleting instance" backendStoreDriver=spdk cleanupRequired=true diskUuid= name=pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 type=engine
2023-06-13T01:45:03.698327208Z [longhorn-instance-manager] time="2023-06-13T01:45:03Z" level=info msg="Deleting instance" backendStoreDriver=spdk cleanupRequired=true diskUuid=7a1dc990-1867-435f-aa71-46061a743f3f name=pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-df235648 type=replica
2023-06-13T01:45:13.482057446Z [2023-06-13 01:45:13.481739] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:45:16.237830636Z [2023-06-13 01:45:16.237514] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: ASYNC EVENT REQUEST (0c) qid:0 cid:0 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.237852613Z [2023-06-13 01:45:16.237595] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.237858295Z [2023-06-13 01:45:16.237614] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: ASYNC EVENT REQUEST (0c) qid:0 cid:1 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.237863116Z [2023-06-13 01:45:16.237629] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.237867592Z [2023-06-13 01:45:16.237658] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: ASYNC EVENT REQUEST (0c) qid:0 cid:2 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.237872034Z [2023-06-13 01:45:16.237673] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.237876349Z [2023-06-13 01:45:16.237690] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: ASYNC EVENT REQUEST (0c) qid:0 cid:3 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.237893126Z [2023-06-13 01:45:16.237705] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.237897632Z [2023-06-13 01:45:16.237736] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:4 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.237922666Z [2023-06-13 01:45:16.237752] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.237928069Z [2023-06-13 01:45:16.237777] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:5 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.237932213Z [2023-06-13 01:45:16.237794] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.237936444Z [2023-06-13 01:45:16.237810] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:6 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.237940746Z [2023-06-13 01:45:16.237827] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.237961752Z [2023-06-13 01:45:16.237843] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:7 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.237966315Z [2023-06-13 01:45:16.237868] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.237970735Z [2023-06-13 01:45:16.237884] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:8 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.237985494Z [2023-06-13 01:45:16.237901] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.237990347Z [2023-06-13 01:45:16.237927] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:9 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.237997996Z [2023-06-13 01:45:16.237942] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238038100Z [2023-06-13 01:45:16.237967] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:10 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238058644Z [2023-06-13 01:45:16.237992] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238064759Z [2023-06-13 01:45:16.238017] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:11 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238069346Z [2023-06-13 01:45:16.238042] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238154816Z [2023-06-13 01:45:16.238059] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:12 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238161287Z [2023-06-13 01:45:16.238083] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238168267Z [2023-06-13 01:45:16.238107] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:13 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238181175Z [2023-06-13 01:45:16.238124] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238230372Z [2023-06-13 01:45:16.238145] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:14 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238234776Z [2023-06-13 01:45:16.238174] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238251642Z [2023-06-13 01:45:16.238191] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:15 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238257675Z [2023-06-13 01:45:16.238217] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238312362Z [2023-06-13 01:45:16.238234] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:16 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238325530Z [2023-06-13 01:45:16.238258] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238333214Z [2023-06-13 01:45:16.238275] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:17 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238349785Z [2023-06-13 01:45:16.238293] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238354867Z [2023-06-13 01:45:16.238316] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:18 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238397136Z [2023-06-13 01:45:16.238332] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238404020Z [2023-06-13 01:45:16.238356] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:19 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238423984Z [2023-06-13 01:45:16.238373] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238431938Z [2023-06-13 01:45:16.238396] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:20 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238543040Z [2023-06-13 01:45:16.238413] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238558339Z [2023-06-13 01:45:16.238437] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:21 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238565562Z [2023-06-13 01:45:16.238453] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238568978Z [2023-06-13 01:45:16.238477] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:22 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238574728Z [2023-06-13 01:45:16.238500] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238615976Z [2023-06-13 01:45:16.238518] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:23 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238623161Z [2023-06-13 01:45:16.238541] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238636706Z [2023-06-13 01:45:16.238558] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:24 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238649506Z [2023-06-13 01:45:16.238582] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238679902Z [2023-06-13 01:45:16.238606] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:25 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238688611Z [2023-06-13 01:45:16.238629] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238697903Z [2023-06-13 01:45:16.238646] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:26 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238718951Z [2023-06-13 01:45:16.238669] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238724251Z [2023-06-13 01:45:16.238694] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:27 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238770826Z [2023-06-13 01:45:16.238712] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238776438Z [2023-06-13 01:45:16.238735] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:28 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238834892Z [2023-06-13 01:45:16.238752] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238841336Z [2023-06-13 01:45:16.238777] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:29 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238851754Z [2023-06-13 01:45:16.238793] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238856301Z [2023-06-13 01:45:16.238816] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:30 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238896751Z [2023-06-13 01:45:16.238833] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238903370Z [2023-06-13 01:45:16.238857] nvme_qpair.c: 580:nvme_qpair_abort_queued_reqs: *ERROR*: aborting queued i/o
2023-06-13T01:45:16.238918063Z [2023-06-13 01:45:16.238873] nvme_qpair.c: 558:nvme_qpair_manual_complete_request: *NOTICE*: Command completed manually:
2023-06-13T01:45:16.238922819Z [2023-06-13 01:45:16.238897] nvme_qpair.c: 225:nvme_admin_qpair_print_command: *NOTICE*: KEEP ALIVE (18) qid:0 cid:0 nsid:0 cdw10:00000000 cdw11:00000000
2023-06-13T01:45:16.238991298Z [2023-06-13 01:45:16.238914] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:0 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.238997586Z [2023-06-13 01:45:16.238941] nvme_qpair.c: 798:spdk_nvme_qpair_process_completions: *ERROR*: CQ transport error -6 (No such device or address) on qpair id 0
2023-06-13T01:45:16.239018852Z [2023-06-13 01:45:16.238966] nvme_ctrlr.c:1022:nvme_ctrlr_fail: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] in failed state.
2023-06-13T01:45:16.239298297Z [2023-06-13 01:45:16.239171] nvme_qpair.c: 247:nvme_io_qpair_print_command: *NOTICE*: WRITE sqid:2 cid:126 nsid:1 lba:131072 len:1 SGL DATA BLOCK OFFSET 0x0 len:0x1000
2023-06-13T01:45:16.239310727Z [2023-06-13 01:45:16.239209] nvme_qpair.c: 477:spdk_nvme_print_completion: *NOTICE*: ABORTED - SQ DELETION (00/08) qid:2 cid:0 cdw0:0 sqhd:0000 p:0 m:0 dnr:0
2023-06-13T01:45:16.239372551Z [2023-06-13 01:45:16.239298] nvme_ctrlr.c:1624:nvme_ctrlr_disconnect: *NOTICE*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] resetting controller
2023-06-13T01:45:16.239935353Z [2023-06-13 01:45:16.239819] posix.c: 937:posix_sock_create: *ERROR*: connect() failed, errno = 111
2023-06-13T01:45:16.240472330Z [2023-06-13 01:45:16.240308] posix.c: 937:posix_sock_create: *ERROR*: connect() failed, errno = 111
2023-06-13T01:45:16.240487746Z [2023-06-13 01:45:16.240358] nvme_tcp.c:1958:nvme_tcp_qpair_connect_sock: *ERROR*: sock connection error of tqpair=0x1a3dab0 with addr=<IP_ADDRESS>, port=20001
2023-06-13T01:45:16.240493475Z [2023-06-13 01:45:16.240381] nvme_ctrlr.c:4016:nvme_ctrlr_process_init: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] Ctrlr operation failed with error: -1, ctrlr state: 51 (error)
2023-06-13T01:45:16.240495876Z [2023-06-13 01:45:16.240406] nvme_ctrlr.c:1695:spdk_nvme_ctrlr_reconnect_poll_async: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] controller reinitialization failed
2023-06-13T01:45:16.240508028Z [2023-06-13 01:45:16.240430] nvme_ctrlr.c:1022:nvme_ctrlr_fail: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] in failed state.
2023-06-13T01:45:16.240527092Z [2023-06-13 01:45:16.240469] bdev_nvme.c:1921:_bdev_nvme_reset_complete: *ERROR*: Resetting controller failed.
2023-06-13T01:45:16.240535546Z [2023-06-13 01:45:16.240495] nvme_ctrlr.c:1624:nvme_ctrlr_disconnect: *NOTICE*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] resetting controller
2023-06-13T01:45:21.241581949Z [2023-06-13 01:45:21.241311] posix.c: 937:posix_sock_create: *ERROR*: connect() failed, errno = 111
2023-06-13T01:45:21.242077444Z [2023-06-13 01:45:21.241881] posix.c: 937:posix_sock_create: *ERROR*: connect() failed, errno = 111
2023-06-13T01:45:21.242087828Z [2023-06-13 01:45:21.241935] nvme_tcp.c:1958:nvme_tcp_qpair_connect_sock: *ERROR*: sock connection error of tqpair=0x1a3dab0 with addr=<IP_ADDRESS>, port=20001
2023-06-13T01:45:21.242091670Z [2023-06-13 01:45:21.241958] nvme_ctrlr.c:4016:nvme_ctrlr_process_init: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] Ctrlr operation failed with error: -1, ctrlr state: 51 (error)
2023-06-13T01:45:21.242095598Z [2023-06-13 01:45:21.241978] nvme_ctrlr.c:1695:spdk_nvme_ctrlr_reconnect_poll_async: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] controller reinitialization failed
2023-06-13T01:45:21.242101465Z [2023-06-13 01:45:21.241994] nvme_ctrlr.c:1022:nvme_ctrlr_fail: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] in failed state.
2023-06-13T01:45:21.242107874Z [2023-06-13 01:45:21.242031] bdev_nvme.c:1921:_bdev_nvme_reset_complete: *ERROR*: Resetting controller failed.
2023-06-13T01:45:21.242116693Z [2023-06-13 01:45:21.242051] nvme_ctrlr.c:1624:nvme_ctrlr_disconnect: *NOTICE*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] resetting controller
2023-06-13T01:45:23.482010483Z [2023-06-13 01:45:23.481706] ctrlr.c: 178:nvmf_ctrlr_keep_alive_poll: *NOTICE*: Disconnecting host nqn.2014-08.org.nvmexpress:uuid:27bc6f87-4ea1-4980-b970-4871ddee0dde from subsystem nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-e-bed7da64 due to keep alive timeout.
2023-06-13T01:45:26.243191358Z [2023-06-13 01:45:26.242886] posix.c: 937:posix_sock_create: *ERROR*: connect() failed, errno = 111
2023-06-13T01:45:26.243658579Z [2023-06-13 01:45:26.243474] posix.c: 937:posix_sock_create: *ERROR*: connect() failed, errno = 111
2023-06-13T01:45:26.243667286Z [2023-06-13 01:45:26.243521] nvme_tcp.c:1958:nvme_tcp_qpair_connect_sock: *ERROR*: sock connection error of tqpair=0x1a3dab0 with addr=<IP_ADDRESS>, port=20001
2023-06-13T01:45:26.243673488Z [2023-06-13 01:45:26.243547] nvme_ctrlr.c:4016:nvme_ctrlr_process_init: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] Ctrlr operation failed with error: -1, ctrlr state: 51 (error)
2023-06-13T01:45:26.243681765Z [2023-06-13 01:45:26.243567] nvme_ctrlr.c:1695:spdk_nvme_ctrlr_reconnect_poll_async: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] controller reinitialization failed
2023-06-13T01:45:26.243691757Z [2023-06-13 01:45:26.243592] nvme_ctrlr.c:1022:nvme_ctrlr_fail: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] in failed state.
2023-06-13T01:45:26.243749076Z [2023-06-13 01:45:26.243631] bdev_nvme.c:1921:_bdev_nvme_reset_complete: *ERROR*: Resetting controller failed.
2023-06-13T01:45:26.243755691Z [2023-06-13 01:45:26.243658] nvme_ctrlr.c:1624:nvme_ctrlr_disconnect: *NOTICE*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] resetting controller
2023-06-13T01:45:31.244875714Z [2023-06-13 01:45:31.244550] posix.c: 937:posix_sock_create: *ERROR*: connect() failed, errno = 111
2023-06-13T01:45:31.245447849Z [2023-06-13 01:45:31.245266] posix.c: 937:posix_sock_create: *ERROR*: connect() failed, errno = 111
2023-06-13T01:45:31.245455229Z [2023-06-13 01:45:31.245308] nvme_tcp.c:1958:nvme_tcp_qpair_connect_sock: *ERROR*: sock connection error of tqpair=0x1a3dab0 with addr=<IP_ADDRESS>, port=20001
2023-06-13T01:45:31.245462025Z [2023-06-13 01:45:31.245334] nvme_ctrlr.c:4016:nvme_ctrlr_process_init: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] Ctrlr operation failed with error: -1, ctrlr state: 51 (error)
2023-06-13T01:45:31.245466799Z [2023-06-13 01:45:31.245356] nvme_ctrlr.c:1695:spdk_nvme_ctrlr_reconnect_poll_async: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] controller reinitialization failed
2023-06-13T01:45:31.245471800Z [2023-06-13 01:45:31.245382] nvme_ctrlr.c:1022:nvme_ctrlr_fail: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] in failed state.
2023-06-13T01:45:31.245548617Z [2023-06-13 01:45:31.245419] bdev_nvme.c:1921:_bdev_nvme_reset_complete: *ERROR*: Resetting controller failed.
2023-06-13T01:45:31.245557510Z [2023-06-13 01:45:31.245447] nvme_ctrlr.c:1624:nvme_ctrlr_disconnect: *NOTICE*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] resetting controller
2023-06-13T01:45:36.246574345Z [2023-06-13 01:45:36.246341] posix.c: 937:posix_sock_create: *ERROR*: connect() failed, errno = 111
2023-06-13T01:45:36.247169586Z [2023-06-13 01:45:36.246960] posix.c: 937:posix_sock_create: *ERROR*: connect() failed, errno = 111
2023-06-13T01:45:36.247182468Z [2023-06-13 01:45:36.247013] nvme_tcp.c:1958:nvme_tcp_qpair_connect_sock: *ERROR*: sock connection error of tqpair=0x1a3dab0 with addr=<IP_ADDRESS>, port=20001
2023-06-13T01:45:36.247189668Z [2023-06-13 01:45:36.247040] nvme_ctrlr.c:4016:nvme_ctrlr_process_init: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] Ctrlr operation failed with error: -1, ctrlr state: 51 (error)
2023-06-13T01:45:36.247195483Z [2023-06-13 01:45:36.247058] nvme_ctrlr.c:1695:spdk_nvme_ctrlr_reconnect_poll_async: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] controller reinitialization failed
2023-06-13T01:45:36.247200935Z [2023-06-13 01:45:36.247075] nvme_ctrlr.c:1022:nvme_ctrlr_fail: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] in failed state.
2023-06-13T01:45:36.247280510Z [2023-06-13 01:45:36.247124] bdev_nvme.c:1921:_bdev_nvme_reset_complete: *ERROR*: Resetting controller failed.
2023-06-13T01:45:36.247288287Z [2023-06-13 01:45:36.247154] nvme_ctrlr.c:1624:nvme_ctrlr_disconnect: *NOTICE*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] resetting controller
2023-06-13T01:45:41.248296894Z [2023-06-13 01:45:41.247981] posix.c: 937:posix_sock_create: *ERROR*: connect() failed, errno = 111
2023-06-13T01:45:41.248996429Z [2023-06-13 01:45:41.248803] posix.c: 937:posix_sock_create: *ERROR*: connect() failed, errno = 111
2023-06-13T01:45:41.249005811Z [2023-06-13 01:45:41.248856] nvme_tcp.c:1958:nvme_tcp_qpair_connect_sock: *ERROR*: sock connection error of tqpair=0x1a3dab0 with addr=<IP_ADDRESS>, port=20001
2023-06-13T01:45:41.249012360Z [2023-06-13 01:45:41.248882] nvme_ctrlr.c:4016:nvme_ctrlr_process_init: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] Ctrlr operation failed with error: -1, ctrlr state: 51 (error)
2023-06-13T01:45:41.249023968Z [2023-06-13 01:45:41.248901] nvme_ctrlr.c:1695:spdk_nvme_ctrlr_reconnect_poll_async: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] controller reinitialization failed
2023-06-13T01:45:41.249029324Z [2023-06-13 01:45:41.248928] nvme_ctrlr.c:1022:nvme_ctrlr_fail: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] in failed state.
2023-06-13T01:45:41.249074321Z [2023-06-13 01:45:41.248973] bdev_nvme.c:1921:_bdev_nvme_reset_complete: *ERROR*: Resetting controller failed.
2023-06-13T01:45:41.249078446Z [2023-06-13 01:45:41.249002] nvme_ctrlr.c:1624:nvme_ctrlr_disconnect: *NOTICE*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] resetting controller
2023-06-13T01:45:46.249322949Z [2023-06-13 01:45:46.249052] bdev_nvme.c:1921:_bdev_nvme_reset_complete: *ERROR*: Resetting controller failed.
2023-06-13T01:45:46.249344972Z [2023-06-13 01:45:46.249212] nvme_fabric.c: 214:nvme_fabric_prop_get_cmd_async: *ERROR*: Failed to send Property Get fabrics command
2023-06-13T01:45:46.249360027Z [2023-06-13 01:45:46.249255] nvme_ctrlr.c:1122:nvme_ctrlr_shutdown_async: *ERROR*: [nqn.2023-01.io.longhorn.spdk:pvc-72244fe3-9fea-4c1a-8977-dbb0079112f2-r-ac78975f] Failed to read the CC register

@chriscchien Will the disk be back to normal after a while?

@derekbit , After 10 minutes, the disk not back, and nodes.longhorn.io status is down

A disk unschedulable issue is not observed after applying https://github.com/longhorn/longhorn-manager/pull/1970. @chriscchien Can you helper check it again?
Another issue

Volume stuck at deleting state even after the replica node have internet connection back

This stuck is caused by the spdk's keep alive mechanism. Checking if there is any setting for the issue.
Currently, the workaround to delete the volume by manual.

Volume stuck at deleting state even after the replica node have internet connection back

This stuck is caused by the spdk's keep alive mechanism. Checking if there is any setting for the issue. Currently, the workaround to delete the volume by manual.

@derekbit can you explain more about the keep-alive mechanism? I thought the volume deletion will create engine & replica instance deletion, so eventually the downstream lvol and controller will be deleted, right?
cc @shuo-wu

@innobead
spdk_tgt has its own keep alive mechanism that tries to reconnect disconnected controller. The retry period doesn't respect ctrlr_loss_timeout_sec (30 seconds). It leads to an issue that volume cannot be deleted in an expected period.
For disk schedulable issue, it is caused by the deadlock which we are addressing in replica rebuilding PR.

It leads to an issue that volume cannot be deleted in an expected period.

Do you mean that this may get stuck (then the server lock cannot be released without the fix in the rebuilding PR)?

A disk unschedulable issue is not observed after applying longhorn/longhorn-manager#1970. @chriscchien Can you helper check it again?

@chriscchien Can you help with this to verify this again? Thanks.

Verified pass in

longhorn master (longhorn 1bbefa, longhorn-manager b647a6, longhorn-instance-manager 4f3d40)
longhorn v1.5.x (longhorn dfcfd7, longhorn-manager 884b1b, longhorn-instance-manage bd0102)

Following steps here, the SPDK block disk unschedulable sympton no longer exist in master-head and v1.5.x
In addition, recreate the SPDK deployment again and uninstall Longhorn all worked well.


[feature]: Consider adding configuration parameters for actor channels

          These (actor channel capacities) should be config params at some point.

          Consider adding them (with defaults) to the `p2p` config proxy.

Originally posted by @appetrosyan in https://github.com/hyperledger/iroha/pull/3346#discussion_r1162608850
Currently all bounded channels of iroha have capacity of 1, without observed performance penalties. Additional benefit of smallest possible capacity is that we will find out about any communication problems sooner than later.
We should discus and consider addition of configuration params to change capacity of actor channels.

not relevant anymore


iOS purchases are not finished

Godot version:
3.0.6
OS/device including version:
All iOS platforms. Reproduced iPhone 8 / iPad Pro running iOS 12
Issue description:
When a consumable (and non-consumable) is purchased, the transaction is not finished. This breaks consumable in-app purchases. If a user attempts to purchase the same consumable a second time, iOS tells them that they have already purchased the product and will not repurchase it.
This is a major show stopper for commercial iOS games, and exactly the problem I'm struggling with.
Steps to reproduce:

Use Godot's iAppStore to make a consumable purchase on an iOS device
Purchase it a second time, iOS will warn you that you've already purchased it and will not continue

In Code:
in_app_store.mm: 227 - auto_finish_transactions equals false
in_app_store.mm: 316 - auto_finish_transaction is hard-coded to false
in_app_store.mm: 320 - intent for transaction queue, unfinished?
Minimal reproduction project:
Due to the nature of this bug, I've provided a project and template but things like ios team ID and test appstoreconnect product will have to be added manually. NOTE: I've left out the .a file that is required to run the XCode project. Please link your own, GitHub won't allow the size.
iap.zip

For this struggling with this, I've removed the conditional from the source. Until Godot has the capability to 'validate a receipt' I think the engine should automatically close transactions, state this in the documentation, and put the onus on the user to do this manually IF they require it.
Best practice states that transactions should be validated on a remote server, not in the application itself, as that will expose the Apple secret token if the application is decompiled.
For now, and until Godot has the ability to give help people validate and close a transaction, this should be automatically done.
To fix, open in_app_store.mm and comment out the conditional statements for the block on line 227. Leave in:  [[SKPaymentQueue defaultQueue] finishTransaction:transaction];

Could this be why I'm getting a "purchase" event from InAppStore.pop_pending_event() every time I start my app, not just after a successful purchase? I don't think it should be doing that.
I will try your fix. Thanks!

This issue is resolved in the latest Master (3.1) branch. There are two undocumented functions that finish the transaction:
InAppStore.set_auto_finish_transaction(true)
(basically does the same as your fix without changing Godot source)
or you can finish the transaction manually with:
InAppStore.finish_transaction(PRODUCT_ID)
This has fixed my “purchase” event happening on each invocation of the app.
I think a ticket needs to be raised to add these methods to the documentation.

Closing as per the above comment. The InAppStore singleton still needs better documentation, see godotengine/godot-docs#2715.


Repo-proxy: add doc for repo-proxy addon as README.md

This is just a doc update, and no internal data in it (like url), so I'll merge directly.


[FSDE-1084] Add E2E tests to chi-vue pagination component

[x] Added E2E tests to chi-vue pagination component
[x] Updated sort by date E2E test to chi-vue data table component

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/1/. :white_check_mark:

You can check this PRs instance in https://dabb1b091cf886556e5dee7a076b70d4b33098f5-chi-pr.enterprise.ctl.io

The CI pipeline did not run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/2/. :x:

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/3/. :white_check_mark:

You can check this PRs instance in https://6ced43e24aec30b48aa93fefda859489b405c3b3-chi-pr.enterprise.ctl.io

The CI pipeline did not run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/4/. :x:

The CI pipeline did not run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/5/. :x:

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/6/. :white_check_mark:

You can check this PRs instance in https://602d6583862dac55bc6250d1c4bf6539771607cf-chi-pr.enterprise.ctl.io

The CI pipeline did not run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/7/. :x:

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/8/. :white_check_mark:

You can check this PRs instance in https://f360b1e0d147a63719bbb3a5bb2e8a72cafdf82f-chi-pr.enterprise.ctl.io

The CI pipeline did not run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/9/. :x:

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/10/. :white_check_mark:

You can check this PRs instance in https://46383955df8478e6dd0df0a4f863176ab537d468-chi-pr.enterprise.ctl.io

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/11/. :white_check_mark:

You can check this PRs instance in https://ac2a3e869218dab7c229f9825b2850ed6a83cc97-chi-pr.enterprise.ctl.io

The CI pipeline did not run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/12/. :x:

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/13/. :white_check_mark:

You can check this PRs instance in https://24d1c4f06aba120828877a0683ed9b18f9d2d6aa-chi-pr.enterprise.ctl.io

The CI pipeline run successfully in https://jenkinsprod.corp.intranet:8443/job/UX-CHI/job/Productive/job/Chi/job/PR-98/14/. :white_check_mark:

You can check this PRs instance in https://a5ede163996ca062e5697ec8024c0e994afa6826-chi-pr.enterprise.ctl.io


Nginx subdirectory

I'm trying to run slim in a subdirectory but unfortunately slim doesn't really like not being at the document root. I have an application at /apps/project and slim at /apps/project/php/public/index.php, with the following nginx conf:
    server {
        listen       443 ssl http2 default_server;
        listen       [::]:443 ssl http2 default_server;
        server_name  _;
        root         /apps/project;

        index index.php index.html index.htm;

        location ~ \.php$ {
            try_files $uri =404;
            fastcgi_intercept_errors on;
            fastcgi_index  index.php;
            include        fastcgi_params;
            fastcgi_param  SCRIPT_FILENAME  $document_root$fastcgi_script_name;
            fastcgi_pass   php-fpm;
        }

        #main application
        location = / {
            ....
        }

        #slim application
        location /slim {
            try_files $uri /php/public/index.php$is_args$args;
        }
    }

When I call https://localhost/slim/someApi, slim runs but the uri path it sees is /slim/someApi. Is there a way for slim to route as if it were /someApi without adding /slim/ to all the route paths?

You may need to set the base path.
$app->setBasePath('/slim/someApi');

Setting the base path works:
$app->setBasePath("/slim");

Unfortunately, the path needs to be hardcoded or configuration needs to be added to get the base path. I'm guessing there's no pure nginx solution?


Child component cannot render when there is same named data.

Version
3.0.5
Reproduction link
https://codesandbox.io/s/divine-fog-7wep8?file=/src/App.vue
Steps to reproduce
Open this page
What is expected?
HelloWorld component rendered.
What is actually happening?
HelloWorld component do not render..

This is because the helloWorld is analyzed as the binding of setup(SETUP_MAYBE_REF) when compileScript analyzes the bindings. It will generate the following code:
export function render(_ctx, _cache, $props, $setup, $data, $options) {
  return (_openBlock(), _createBlock(_Fragment, null, [
    _hoisted_1,
    _createTextVNode(" " + _toDisplayString($setup.helloWorld) + " ", 1 /* TEXT */),
    _createVNode($setup["helloWorld"], { msg: "Hello Vue 3 in CodeSandbox!" })
  ], 64 /* STABLE_FRAGMENT */))
}

Here, $setup["helloWorld"] is problematic.

Workaround: As long as the component name in the template is not the same as the binding, there will be ok.

The source code clearly states that setup components take precedence over user components. Maybe it's not a bug, It's counterintuitive though. @HcySunYang
https://github.com/vuejs/vue-next/blob/58c46d77eac05ee72f17aa2669239c4d7c9a3abe/packages/compiler-core/src/transforms/transformElement.ts#L260

This is not about component priority, it is about components/directives and data name conflicts

Maybe it should be resolved in resolveComponent.

If I'm thinking right I'll adjust the test case, and close PR if I'm thinking wrong. @HcySunYang


stop and start munge when writing the munge key

stop and start munge when writing the munge key
Fixes: #24

@jamesbeedy can you fix the lint tests real quick and then I'll review? Likely just need to run tox run -e fmt


setup.py containing requires fails when run without rwt

hi @jaraco,
Here's a setup.py which defines __requires__ for use with rwt tool. It's taken straight from your README.rst for the sake of example.
#!/usr/bin/env python

__requires__ = ['setuptools', 'setuptools_scm']

from setuptools import setup

setup(
    name='test_rwt',
    use_scm_version=True,
    setup_requires=__requires__,
)

Now, if I try to run this without also invoking python -m rwt -- setup.py ..., like the usual:
$ python3 setup.py --help

I get this error from pkg_resources:
Traceback (most recent call last):
  File "setup_rwt.py", line 5, in <module>
    from setuptools import setup
  File "/usr/local/var/pyenv/versions/3.6.0/Python.framework/Versions/3.6/lib/python3.6/site-packages/setuptools/__init__.py", line 12, in <module>
    import setuptools.version
  File "/usr/local/var/pyenv/versions/3.6.0/Python.framework/Versions/3.6/lib/python3.6/site-packages/setuptools/version.py", line 1, in <module>
    import pkg_resources
  File "/usr/local/var/pyenv/versions/3.6.0/Python.framework/Versions/3.6/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3018, in <module>
    @_call_aside
  File "/usr/local/var/pyenv/versions/3.6.0/Python.framework/Versions/3.6/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3002, in _call_aside
    f(*args, **kwargs)
  File "/usr/local/var/pyenv/versions/3.6.0/Python.framework/Versions/3.6/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3031, in _initialize_master_working_set
    working_set = WorkingSet._build_master()
  File "/usr/local/var/pyenv/versions/3.6.0/Python.framework/Versions/3.6/lib/python3.6/site-packages/pkg_resources/__init__.py", line 654, in _build_master
    ws.require(__requires__)
  File "/usr/local/var/pyenv/versions/3.6.0/Python.framework/Versions/3.6/lib/python3.6/site-packages/pkg_resources/__init__.py", line 962, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/usr/local/var/pyenv/versions/3.6.0/Python.framework/Versions/3.6/lib/python3.6/site-packages/pkg_resources/__init__.py", line 848, in resolve
    raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'setuptools_scm' distribution was not found and is required by the application

The error happens when a requirement listed in __requires__ (like setuptools_scm here) is not already installed in the current environment.
It seems like pkg_resources (imported by setuptools) also attempts to use the __requires__ variable, in WorkinSet._build_master method:
https://github.com/pypa/setuptools/blob/089cdeb489a0fa94d11b7307b54210ef9aa40511/pkg_resources/__init__.py#L640-L658
This behavior is documented in the pkg_resources docs:
http://setuptools.readthedocs.io/en/latest/pkg_resources.html#workingset-objects

All distributions available directly on sys.path will be activated automatically when pkg_resources is imported. This behaviour can cause version conflicts for applications which require non-default versions of those distributions. To handle this situation, pkg_resources checks for a requires attribute in the main module when initializing the default working set, and uses this to ensure a suitable version of each affected distribution is activated. For example:

__requires__ = ["CherryPy < 3"] # Must be set before pkg_resources import
import pkg_resources

In your REAME.rst, you say that this technique:

When invoked with rwt, the dependencies will be assured before the script is run, or if run with setuptools, the dependencies will be loaded using the older technique, so the script is backward compatible.

However, it appears to me that one cannot have such a backward-compatible setup.py which also takes advantage of rwt via the __requires__ variable, because once one uses that, it fails as one tries to run it in the old-fashioned way.
Am I missing something?
Thank you for your help.
In the meantime I think I'll just use python3 -m rwt -r requirements/setup.txt -- setup.py ... instead of __requires__.

forgot to mention, I'm using python3.6 and setuptools==34.0.0 released a couple of hours ago, but the error also occurs with previous versions of setuptools/pkg_resources as well as with python2.7.

Hmm. I guess what I meant when I said the script was backward compatible is that if you were relying on __requires__ to declare your requirements before via setuptools/pkg_resources, that now they can be installed from your declaration by rwt, and that pkg_resources will continue to validate those declarations as it did before. In other words, if you had those dependencies installed using easy_install -m, pkg_resources would make those packages visible as a result of the __requires__. In that sense, the two syntaxes are compatible.
I'm not sure what you're expecting to happen beyond that. If you're using __requires__ in a script, you're declaring that the script can't run unless those distributions can be resolved, and rwt goes a step further to ensure they are.
I think you're right that if it's not your intention to require the script to be run by rwt or require the person invoking it to have installed those packages in advance, then you'll want to fall back to declaring the requirements elsewhere.
I had originally intended for rwt to be a solution to setup_requires, but it appears that rwt contradicts intentions established in PEP 518.

Does that clarify?

Yes, thanks for the clarification.
It was a misunderstanding on my part, as I am not familiar with pkg_resources API.
I'm still not sure why would rwt be in contradiction with PEP518 though.
I'll re-read that thread more carefully.
Thanks again!

I think the contradiction comes with the prescribed means of declaration. rwt uses __requires__ as a simple, embedded mechanism to solicit requirements, whereas PEP 518 declares a pyproject.toml file which requires external libraries just to parse but also requires an additional file, two uses that rwt is specifically seeking to avoid.
There's some overlap, though, and there's a good chance the core of rwt can be repurposed to implement PEP 518 after the requirements are parsed.